2850 replies to this topic

[ejtagle]

pischla, on 27 September 2012 - 10:27 AM, said:

Hi guys, just installed the Jellybean Test beta 3-1 (nvFlash) in my PoV Mobii and it seems to look very nice. 3G and Wi-Fi came right up after install.

The tablet seems to feel sluggish though after install and thought I would reboot to see if it gets better, but unfortunately it gets stuck at the boot animation upon bootup. Tried also to re-flash to no avail. Any tricks to try to resolve this?

You know the answer... Back to moddedstock and then, nvflash latest.. Don't forget to repartition SD card with gparted. All the other ways (CWM, minitool. ..) seem to cause trouble (=bootloops...)

[ejtagle]

I was thinking... Why can't we enable faceunlock in vega ? ... We have the required gapps available, and, as we are now using the sd as primary storage, this should be possible (in fact, it is possible to use the SD as a complete replacement for NAND, except the boot image itself...


Gapps with facelock support... You need to modify the install script to stop validating the herring platform is used. The package includes non-neon optimized shared libs, that are a must for Tegra2 (neon extensions not supported on vega)

http://www.mediafire...rkho0u1ms6dhtmh

Edited by ejtagle, 27 September 2012 - 04:07 PM.

[pischla]

ejtagle, on 27 September 2012 - 03:39 PM, said:

You know the answer... Back to moddedstock and then, nvflash latest.. Don't forget to repartition SD card with gparted. All the other ways (CWM, minitool. ..) seem to cause trouble (=bootloops...)

Repartition the sd-card? I think I'm out of the loop on this one...

[ejtagle]

pischla, on 28 September 2012 - 08:43 AM, said:

Repartition the sd-card? I think I'm out of the loop on this one...

Latest vegabean require3s an specially formatted sdcard, otherwise, it won't boot...

[MikhailM]

ejtagle, on 27 September 2012 - 03:39 PM, said:

You know the answer... Back to moddedstock and then, nvflash latest.. Don't forget to repartition SD card with gparted. All the other ways (CWM, minitool. ..) seem to cause trouble (=bootloops...)

Hi,Ejtagle,
I have not had any trouble partitioning my 16GB SD cards with CWM - worked each time and has not given any problems. I assume that the slower opening of apps is not a result of my partitioning using CWM.

[MikhailM]

pischla, on 28 September 2012 - 08:43 AM, said:

Repartition the sd-card? I think I'm out of the loop on this one...

To add some detail to Ejtagle's answer you need to repartition your SD card to contain a Ext4 partition (at least 1GB), you do not need a swap partition. After you have done this repartitioning, then transfer the Beta3-1 zip file to it and re-flash the rom. (You will loose all data on the Sd card when you re-partition it, so save everything you need on your PC before you re-format your card).

[DerArtem]

ejtagle, on 23 September 2012 - 08:17 PM, said:

Attached the source code of the modified ril, the compiled version of it, and also, the cleaned up radio log with just the important things to understand the problem

I have added some minor, but important changes to make it work with Huawei E169 and K3715 modems:

https://github.com/D.../commits/master

There is still one problem: when a PIN code is enabled on the SIM card then ril will fail with stuff like below. With disbaled PIN everything works well.
I will do some more tests when I get the time...

D/RILJ	(  608): [0022]> ENTER_SIM_PIN
I/RIL	 (  109): processRequest() ENTER_SIM_PIN
D/AT	  (  109): AT(12)> AT+CPIN="XXXX"
I/AT	  (  109): AT(12)< OK
D/RILJ	(  608): [0022]< ENTER_SIM_PIN {1}
D/RILJ	(  608): [0023]> GET_SIM_STATUS
I/RIL	 (  109): processRequest() GET_SIM_STATUS
D/AT	  (  109): AT(12)> AT+CPIN?
I/AT	  (  109): AT(12)< +CPIN: READY
I/AT	  (  109): AT(12)< OK
D/AT	  (  109): AT(12)> AT^CARDLOCK?
I/AT	  (  109): AT(12)< ^CARDLOCK: 2,10,0
I/AT	  (  109): AT(12)< OK
D/RIL	 (  109): Card Unlocked, times: 10
D/AT	  (  109): AT(12)> AT^CARDMODE
I/AT	  (  109): AT(12)< ^CARDMODE: 2
I/AT	  (  109): AT(12)< OK
I/RIL	 (  109): Detected card type :3
I/RIL	 (  109): [Card type discovery]: USIM
D/RILJ	(  608): [0023]< GET_SIM_STATUS IccCardState {CARDSTATE_PRESENT,PINSTATE_UNKNOWN,num_apps=1,gsm_id=0{APPTYPE_USIM,APPSTATE_READY,pin1=PINSTATE_UNKNOWN,pin2=PINSTATE_UNKNOWN},cmda_id=8,ism_id=8}
E/GSM	 (  608): [IccCard] Invalid Subscription Application index:8
E/GSM	 (  608): [IccCard] Invalid Subscription Application index:8
D/GSM	 (  608): [IccCard] USIM=READY CSIM=ABSENT
D/RILB	(  608): getLteOnCdmaMode=0 curVal=-1 product_type='' lteOnCdmaProductType=''
E/GSM	 (  608): [IccCard] Invalid Subscription Application index:8
D/GSM	 (  608): [IccCard] Broadcasting intent ACTION_SIM_STATE_CHANGED READY reason null
D/GSM	 (  608): [SIMRecords] fetchSimRecords 0
D/RILJ	(  608): [0024]> getIMSI: GET_IMSI aid: null
D/RILJ	(  608): [0025]> iccIO: SIM_IO 0xc0 0x2fe2  path: 3F00,0,0,15 aid: null
I/RIL	 (  109): processRequest() GET_IMSI
D/RILJ	(  608): [0024]< GET_IMSI error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
D/RILJ	(  608): [0026]> iccIO: SIM_IO 0xc0 0x6f40  path: 3F007F10,0,0,15 aid: null
I/RIL	 (  109): processRequest() SIM_IO
D/RILJ	(  608): [0025]< SIM_IO error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
I/RIL	 (  109): processRequest() SIM_IO
D/RILJ	(  608): [0026]< SIM_IO error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
D/RILJ	(  608): [0027]> iccIO: SIM_IO 0xc0 0x6fc9  path: 3F007F20,0,0,15 aid: null
I/RIL	 (  109): processRequest() SIM_IO
D/RILJ	(  608): [0027]< SIM_IO error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
D/RILJ	(  608): [0028]> iccIO: SIM_IO 0xc0 0x6fad  path: 3F007F20,0,0,15 aid: null
I/RIL	 (  109): processRequest() SIM_IO

[Daedric1383]

@ejtagle, did you get to see my post @TR? http://www.tabletrom....html#post72552

[ejtagle]

DerArtem, on 29 September 2012 - 02:14 PM, said:

I have added some minor, but important changes to make it work with Huawei E169 and K3715 modems:

https://github.com/D.../commits/master

There is still one problem: when a PIN code is enabled on the SIM card then ril will fail with stuff like below. With disbaled PIN everything works well.
I will do some more tests when I get the time...

D/RILJ ( 608): [0022]> ENTER_SIM_PIN
I/RIL	 ( 109): processRequest() ENTER_SIM_PIN
D/AT	 ( 109): AT(12)> AT+CPIN="XXXX"
I/AT	 ( 109): AT(12)< OK
D/RILJ ( 608): [0022]< ENTER_SIM_PIN {1}
D/RILJ ( 608): [0023]> GET_SIM_STATUS
I/RIL	 ( 109): processRequest() GET_SIM_STATUS
D/AT	 ( 109): AT(12)> AT+CPIN?
I/AT	 ( 109): AT(12)< +CPIN: READY
I/AT	 ( 109): AT(12)< OK
D/AT	 ( 109): AT(12)> AT^CARDLOCK?
I/AT	 ( 109): AT(12)< ^CARDLOCK: 2,10,0
I/AT	 ( 109): AT(12)< OK
D/RIL	 ( 109): Card Unlocked, times: 10
D/AT	 ( 109): AT(12)> AT^CARDMODE
I/AT	 ( 109): AT(12)< ^CARDMODE: 2
I/AT	 ( 109): AT(12)< OK
I/RIL	 ( 109): Detected card type :3
I/RIL	 ( 109): [Card type discovery]: USIM
D/RILJ ( 608): [0023]< GET_SIM_STATUS IccCardState {CARDSTATE_PRESENT,PINSTATE_UNKNOWN,num_apps=1,gsm_id=0{APPTYPE_USIM,APPSTATE_READY,pin1=PINSTATE_UNKNOWN,pin2=PINSTATE_UNKNOWN},cmda_id=8,ism_id=8}
E/GSM	 ( 608): [IccCard] Invalid Subscription Application index:8
E/GSM	 ( 608): [IccCard] Invalid Subscription Application index:8
D/GSM	 ( 608): [IccCard] USIM=READY CSIM=ABSENT
D/RILB ( 608): getLteOnCdmaMode=0 curVal=-1 product_type='' lteOnCdmaProductType=''
E/GSM	 ( 608): [IccCard] Invalid Subscription Application index:8
D/GSM	 ( 608): [IccCard] Broadcasting intent ACTION_SIM_STATE_CHANGED READY reason null
D/GSM	 ( 608): [SIMRecords] fetchSimRecords 0
D/RILJ ( 608): [0024]> getIMSI: GET_IMSI aid: null
D/RILJ ( 608): [0025]> iccIO: SIM_IO 0xc0 0x2fe2 path: 3F00,0,0,15 aid: null
I/RIL	 ( 109): processRequest() GET_IMSI
D/RILJ ( 608): [0024]< GET_IMSI error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
D/RILJ ( 608): [0026]> iccIO: SIM_IO 0xc0 0x6f40 path: 3F007F10,0,0,15 aid: null
I/RIL	 ( 109): processRequest() SIM_IO
D/RILJ ( 608): [0025]< SIM_IO error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
I/RIL	 ( 109): processRequest() SIM_IO
D/RILJ ( 608): [0026]< SIM_IO error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
D/RILJ ( 608): [0027]> iccIO: SIM_IO 0xc0 0x6fc9 path: 3F007F20,0,0,15 aid: null
I/RIL	 ( 109): processRequest() SIM_IO
D/RILJ ( 608): [0027]< SIM_IO error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
D/RILJ ( 608): [0028]> iccIO: SIM_IO 0xc0 0x6fad path: 3F007F20,0,0,15 aid: null
I/RIL	 ( 109): processRequest() SIM_IO

Excellent! ... Also, if you happen to have some spare time, check the audio voice capability.. Maybe i have missed something there, as i am getting corrupted audio sometimes and had to implement a filter to try to sort out the problem.. I don't have a E169 at hand... -- But i think the RIL is pretty close to be completely functional ...

I think the problem is in the getCardStatus function. It calls the getSIMStatus(), and based on that status, it fills the RIL_CardStatus_v6 struct. Don't know why, but it is returning PINSTATE_UNKNOWN, when it should not.... I checked the app_status_array, and this entry is what is returned when SIM_READY is returned by the getSIMStatus() function returns SIM_READY... ... This getCardStatus() function was taken from the mbm-300 ril... Maybe there is also a bug on that ril .

Edit2: I think i know what is happening... The processRequest() function validates, by calling the function getRadioState() that the radio has become ready before allowing the getIMSI and all the other requests to succeed... After successful PIN input, we should set the radio state to available... Otherwise, no command will be processed from that point onwards...

Edit3: Added an small change (untested) that should fix this problem. Now, the RIL should start working as soon as you enter the sim PIN... The sim should be unlocked by the RIL. There should be no need to unlock the SIM before inserting it into the tablet / 3G modem...  Please, report success / failure cases

Attached Files

•  huawei-generic-29sept.rar   105K   8 downloads

Edited by ejtagle, 30 September 2012 - 02:31 AM.

[DerArtem]

ejtagle, on 30 September 2012 - 12:39 AM, said:

... This getCardStatus() function was taken from the mbm-300 ril... Maybe there is also a bug on that ril .

Edit2: I think i know what is happening... The processRequest() function validates, by calling the function getRadioState() that the radio has become ready before allowing the getIMSI and all the other requests to succeed... After successful PIN input, we should set the radio state to available... Otherwise, no command will be processed from that point onwards...

Edit3: Added an small change (untested) that should fix this problem. Now, the RIL should start working as soon as you enter the sim PIN... The sim should be unlocked by the RIL. There should be no need to unlock the SIM before inserting it into the tablet / 3G modem...  Please, report success / failure cases

I just tried it out. Now the modem works just fine with PIN lock.

I am just recompiling android to enable voice features.

One big problem still exists: When going to suspend the 3G connection does not get terminated and the USB port keeps be powered on. The modem is still online while the CPU is in LP0. The connection is not getting reestablished when the tablet returns from suspend. I have not checked the logs yet. Will do it when I have some more time...

Update: Voice calls are working fine so far, only the volume of incoming audio is very low on the tablet.

Edited by DerArtem, 01 October 2012 - 10:07 PM.

[ejtagle]

DerArtem, on 01 October 2012 - 09:32 PM, said:

I just tried it out. Now the modem works just fine with PIN lock.

I am just recompiling android to enable voice features.

One big problem still exists: When going to suspend the 3G connection does not get terminated and the USB port keeps be powered on. The modem is still online while the CPU is in LP0. The connection is not getting reestablished when the tablet returns from suspend. I have not checked the logs yet. Will do it when I have some more time...

Update: Voice calls are working fine so far, only the volume of incoming audio is very low on the tablet.

There are reasons for both turning off the 3G modem in LP0, and to leave it on... ... If you want to receive calls, probably you want to keep the modem powered on, and use it to wake up the tablet. If you don't want that, probably we could turn off the modem... Theoretically, the 3G connection traffic should keep the tablet waking up to keep the ppp connection alive... But, if the connection drops, the pppd daemon would be terminated... and if it gets terminated, the RIL should detect that (no data call active) and inform android.
I have no way to test it, so i would appreciate if you can take a look at it...
Regarding voice, there is a automatic gain control implementation, but i don't understand why it fails to amplify the audio... :S

[DerArtem]

ejtagle, on 01 October 2012 - 11:35 PM, said:

There are reasons for both turning off the 3G modem in LP0, and to leave it on... If you want to receive calls, probably you want to keep the modem powered on, and use it to wake up the tablet. If you don't want that, probably we could turn off the modem... Theoretically, the 3G connection traffic should keep the tablet waking up to keep the ppp connection alive... But, if the connection drops, the pppd daemon would be terminated... and if it gets terminated, the RIL should detect that (no data call active) and inform android.
I have no way to test it, so i would appreciate if you can take a look at it...
Regarding voice, there is a automatic gain control implementation, but i don't understand why it fails to amplify the audio... :S

I remember the problem. I had the same in chan_datacard. After answering a call we must send "AT+CLVL=1" and then "AT+CLVL=5" to the modem. This will set the volume to maximum. In theory just sending AT+CLVL=5 should be enough, but some modems do not change the volume with just this command. So we must first set it to minimum with "AT+CLVL=1" and them to max with "AT+CLVL=5" directly after answering the call.

Edited by DerArtem, 02 October 2012 - 11:12 AM.

[ejtagle]

DerArtem, on 02 October 2012 - 11:12 AM, said:

I remember the problem. I had the same in chan_datacard. After answering a call we must send "AT+CLVL=1" and then "AT+CLVL=5" to the modem. This will set the volume to maximum. In theory just sending AT+CLVL=5 should be enough, but some modems do not change the volume with just this command. So we must first set it to minimum with "AT+CLVL=1" and them to max with "AT+CLVL=5" directly after answering the call.

Will try to implement it. Also, i will try to detect when the pppd daemon dies, but the data connection is still present... I think we should inform Android as that a Data connection is NOT present if the pppd daemon is not running. Otherwise, when resuming from suspend, the pppd daemon could be ended (by the tegra2 usb port being suspended, that means no serial port to attach pppd, and that in turn means pppd will terminate). But, the 3G modem keeps the data connection... So, we end with a non functional data connection... Its better to tell android that there is no data connection, so it is able to restart the data connection (dial+pppd)...

[ejtagle]

As DerArtem told, the previous RIL has a subtle bug: When the tablet enters sleep, and then resumes, the 3G connection is lost. The 3G modem is still connected, but the pppd daemon is not running, as the modem disappears when the USB bus is suspended... I added an small fix that also checks that the network interface is still up and running, before telling the Android framework we have a data connection. That way, android should be able to reestablish the connection after suspension.

As i have right now no way to test this, could anyone, please, try it and tell me if 3G is still working, and it recovers from suspension ? -If it does, this RIL will be recommended to be included in the next JB rom.. But we need that confirmation that things still work!

The other small change, per DerArtem recommendation, is to try to raise voice volume.. We now set the 3G modem voice volume to maximum. Let's hope it works!

Attached Files

•  huawei-generic-2oct.rar   88.16K   11 downloads
•  libhuaweigeneric-ril.rar   48.91K   9 downloads

[univall]

ejtagle, on 03 October 2012 - 01:09 AM, said:

As DerArtem told, the previous RIL has a subtle bug: When the tablet enters sleep, and then resumes, the 3G connection is lost. The 3G modem is still connected, but the pppd daemon is not running, as the modem disappears when the USB bus is suspended... I added an small fix that also checks that the network interface is still up and running, before telling the Android framework we have a data connection. That way, android should be able to reestablish the connection after suspension.

As i have right now no way to test this, could anyone, please, try it and tell me if 3G is still working, and it recovers from suspension ? -If it does, this RIL will be recommended to be included in the next JB rom.. But we need that confirmation that things still work! data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAMAAAC6V+0/AAAABGdBTUEAANbY1E9YMgAAAiJQTFRFV0AI////V0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIW0IIV0AIW0IIW0QJW0IIV0AIV0AIV0AIQzQQa0oJbEwJbVELbk4Kb0wJb1QMcVILc1cMlF8Ll2oNmXEQnn8Vo2gLpGgLpGoMpW8NpXEOp3YQq4MUrH0Rro0Xr4QUsI4XsZAYuXQNwIkSwI0VyIAOyocQyqcdy4QQzosS1Kod1rIf3ZMS3ZUT3a8c3o4Q3rcf4ZER5JUR5ZYS5ZgS5aIW55wT554U6KkZ6qQV6qUW6qYW6qcX66gW7Lsf7a0X7a0Y7a8Z7bEb7rAY7rEY7rMa7rMb77EY77Ma77QZ77cd77oc8bgb8bkb8bob8b4f8cUh8skh87wb870c88If88kk89Im9Mwl9cMd9cch9sUe9scf9sgg9skh9swi9swk98og988k99Mm+c8h+dMk+dYm+9Mh+9Mi+9Uj+9Yk+9cl+9gl+9kn+9on+9oo+9op+9so/Ncl/Ngl/Non/Nso/N0o/N0p/dkk/dok/d4o/eAp/eEp/tsk/twk/t0k/t4l/uAn/uAp/uIq/uMp/uMq/uQq/94l/94m/98l/98m/+Am/+An/+En/+Eo/+Io/+Ip/+Mo/+Mp/+Mq/+Qp/+Qq/+Qr/+Uq/+UrX/9jcQAAACd0Uk5TAAABCQoLHCYnMDY4OjuCg4WHiImKm56fx8jJys3P1Ofp6enq7/DyAdnyKAAAAUZJREFUGNNt0b9Kw1AYhvH3OzlJ2qRpiiVCIxUUdXIRdFd0cfQOvA4HF3UWr0Fw83J0VEQpaLX/myY5Od/n0FGfS/g9RPibhgBwfB00MMuqwgIgDQBelMbRLj9NRp/TEgCRKD9Jjjq+FIvy9fm7XzA5BC/dPuu00tjx0EhsubCk4Mbd03Z6DVq5TcJ4J21qaPido6BNsACaeR50J1mm4cVhXQTCAPmeG0QuFIKWH4sFiwVHNa3jOjRqG2KV3FjgikVEtA8FkvzCMphZeLZ4rARQyF8KWGZhFlsYmMpAYTEuzi8ti3A1Hz4cmlEGh5x64u3fHSjJsp/7k1H+NTBEemVrL6o9AACOx9nH27Aiktra+nboKnA5n5TDt15BGih7ZrQZaqlMVbwP+gYgEsCLVptRk6fjWX9aAkS0RHbDBmZzs0Sm/3b8Apz1nhT0ICJTAAAAAElFTkSuQmCC

The other small change, per DerArtem recommendation, is to try to raise voice volume.. We now set the 3G modem voice volume to maximum. Let's hope it works!

Hi.

- 3g works
- to airplane mode and back, no issues with 3g or phone
- suspend and back, no issues with 3g or phone
- tablet in sleep, incoming call wakes up tablet, no issues with 3g or phone
- not sure about voice volume, unable to fully test.

HTH.

[univall]

univall, on 03 October 2012 - 04:15 AM, said:

Hi.

- 3g works
- to airplane mode and back, no issues with 3g or phone
- suspend and back, no issues with 3g or phone
- tablet in sleep, incoming call wakes up tablet, no issues with 3g or phone
- not sure about voice volume, unable to fully test.

HTH.

[Edit]
Well, checked for volume increase on view pad 10s. Still very faint on the tablet. On the phone side, there is a lot of feedback/echo with some latency

[Scanno]

@Eduardo,<br />At tabletroms there is a user that has a e173. He provided the following log:<br /><br />http://dl.dropbox.co...03/radio.txt<br /><br />Can you have a look at it and see if support for the e173 can be included<br />

Edited by Scanno, 03 October 2012 - 11:09 AM.

[ejtagle]

Scanno, on 03 October 2012 - 11:06 AM, said:

@Eduardo,<br />At tabletroms there is a user that has a e173. He provided the following log:<br /><br />http://dl.dropbox.co...03/radio.txt<br /><br />Can you have a look at it and see if support for the e173 can be included<br />

I think we would really need usb_modeswitch running in the  tablet. This modem seems to be in cdrom emulation mode, and must be toggled to modem mode before the ril will see it. The mode switch can't be implemented in the RIL itself. I guess that we could recompile usb_modeswitch for android... In fact, it could even work out of the box...

[Scanno]

ejtagle, on 03 October 2012 - 02:43 PM, said:

I think we would really need usb_modeswitch running in the  tablet. This modem seems to be in cdrom emulation mode, and must be toggled to modem mode before the ril will see it. The mode switch can't be implemented in the RIL itself. I guess that we could recompile usb_modeswitch for android... In fact, it could even work out of the box...

Thanks for your answer. Figured it would be because ttyUSB2 could not be found in the radio log.

[DerArtem]

Hi,

as faar as I have testet the RIL seems to work fine now.

I will try to do some more voice-call later...