2.0 GingerComb ROM + 3G stick

[Finless]

OK after looking at both the stock Arnova 10g2 and the philly 10g2, I found many files related to 3G missing in the philly system.img. So maybe it is not just the kernel! We shall see... I keep my fingers crossed. If this does not work then we are stuck and I will have to keep working on the old kernel 2.0 ROM which I do not want to do honestly.

OK so please follow these instructions.

1) Take my production 2.0 gingercomb rom (not the last test ROM I just made you).
2) Go into the image folder and rename system.img to systemold.img. This way you havea copy of the original system.
3) Download this new system.img. Unzip it and copy this new system.img into the image folder of ther 2.0 ROM kit.
4) Reflash the ROM erasing IDB and clicking the loader.

Here is the new system.img with all the 3G files added.

http://video.freaktab.com/?subpath=f...stem2_0_3G.zip

Man I hope this works!

[Finless]

Mr. Weelson, any luck in testing?

Bob

[MrWeelson]

Mr. Weelson, any luck in testing?

Bob

Hi Bob,

Have just this second flashed 2.0a with the revised system.img and no luck I'm afraid.
No errors, just doesn't recognise it.
I rebooted and still not working.

I noticed system.img is exactly the same size as the original version, is that as it should be?

[Finless]

System size wont change unless I grow it bigger. system has empty space.

Anyway crap.... I was hoping that would solve it.

Can you try following these instructions? It maybe you have to kick it off manually?

http://www.freaktab.com/showthread.php?329-Huawei-E180-data-stick-instructions

Other than this, I can try a few more things from Fenice's ideas and see if that works. Bottom line everything I have read, this should not be a kernel problem but some files or script I do not have.

Bob

[MrWeelson]

System size wont change unless I grow it bigger. system has empty space.

Anyway crap.... I was hoping that would solve it.

Can you try following these instructions? It maybe you have to kick it off manually?

http://www.freaktab.com/showthread.php?329-Huawei-E180-data-stick-instructions

Other than this, I can try a few more things from Fenice's ideas and see if that works. Bottom line everything I have read, this should not be a kernel problem but some files or script I do not have.

Bob

Hi Bob,

Tried again and followed the instructions, no luck.
When I try
* Select Network Operators
* Select Search Networks
I get 'Error while searching for networks'
With the test rom it all worked well, didn't have to make any manual changes.

[Finless]

Hi Bob,

Tried again and followed the instructions, no luck.
When I try
* Select Network Operators
* Select Search Networks
I get 'Error while searching for networks'
With the test rom it all worked well, didn't have to make any manual changes.

I see a few more ril lib files I can try to copy over. So I will try that next. If that still doesnt work then I will try fenice script to see if I can kick it off.

If that doesnt work... welll...... without a 3G stick and the ability to look at logcat in ADB, not sure I can fix it.

Bob

[cygnus]

Try... but not run 3G key with Huawei Chipset

Hi,
i've tested your firmware Finelss 2.0 + 3G on my Arnova 10 G2 with my Huawei 3G pen. Sorry but it don't run. This 3g Key runs correctly in the Arnova 10 G2 original firmware and in Morkamod 1.15 firmware. It don't run in your finless 2.0 and in "Philadelphia Inquirer edition" of Arnova firmware. Another thing. I've understood that 2.0 support USB Bluetooth dongle and GPS via Bluetooth. I don't find this support. Probably i don't remember well. Is possible this kind support in 2.X of finelss? In any case.... thank you for your fantastic work.
Jean-Luke

[MrWeelson]

Hi,
i've tested your firmware Finelss 2.0 + 3G on my Arnova 10 G2 with my Huawei 3G pen. Sorry but it don't run. This 3g Key runs correctly in the Arnova 10 G2 original firmware and in Morkamod 1.15 firmware. It don't run in your finless 2.0 and in "Philadelphia Inquirer edition" of Arnova firmware. Another thing. I've understood that 2.0 support USB Bluetooth dongle and GPS via Bluetooth. I don't find this support. Probably i don't remember well. Is possible this kind support in 2.X of finelss? In any case.... thank you for your fantastic work.
Jean-Luke

Hi,

That's the same problem I had with my Archos 3g stick - the 2.0 is if I recall correctly built on the Philly kernel. Bob did a test rom for me with the older kernel, which fixed the 3g issue, but seems to be having problems with the new one!
I'll try again when there's a revised 2.0 with 3g to try.

I agree with you though Bob, I think try maybe one or two more times, if can't get a resolution then don't worry. Worst case is I can buy one of those 'MiFi' gadgets that connect to 3G and give you a wifi network to connect to.

[Finless]

I have studied this a little more and am going to try a script to kick of PPP. Again everything I have read on XDA and other places, getting 3G to work does not look like a function of the kernel except maybe to auto recognize it when you plug it in.

I read on XDA that with the cyanogen mod they need a script to be run to kick off the process. I have double checked all the files and made sure theones related to 3G support are in that ROM I made you. So something is not kicking off the detection when you plug in a stick.

I wish there was a way I could get your logcat from your device on the 1.4 ROM and the 2.0 ROM and compare them.

So how much is that 3G stick you have? Also what do you have to do to use it? I assume you have to buy some data plan or something from a carrier? Verizon I hear is not supported?

Bob

[MrWeelson]

Hi,

The 3g stick was about 40GBP, not sure if it's still available in the US.
It's unlocked so accepts any sim in the UK, couldn't comment on the US. I need to buy more data for my sim but even without this the rom recognises the stick.

If you can let me know how to run/get the logcat (think I need ADB) I've no problem doing that, will reflash 1.4 if you like, or even the test 2.0 rom you posted earlier.

Thanks

[Finless]

Yes I use ADB but I think there is an APP on the market that will dump logcat to your sdcard. I just dont remember what the name is.

Also logcat is revolving so you should reboot, stick in the stick let it register (if on 1.5) and then dump logcat as soon as you can. This way we do not miss the messages if it wraps.

It would be great if I couls see whats going on between 1.5 and 2.0B (FYI I left all the 3G changes in 2.0B so that 3G version I gave you should be the same).

Bob

[MrWeelson]

Link for 2.0B system.img is dead - must be while we're waiting for 2.0C!
I'll wait for that before testing any more.

Thanks

[cybertwigg]

borrowed a 3g stick here is logcat data on 2.0 rom the origional one
Ljava/lang/String;
D/dalvikvm( 432): GREF has increased to 201
D/DfeApi ( 432): [1] DfeApiContext.getSmallestScreenWidthDp: smallestScreenWidthDp does not exist, using pre-ics hack.
D/Finsky ( 432): [8] MarketBillingService.getPreferredAccount: com.tapulous.taptaprevenge4: Account determined from library ownership.
D/dalvikvm( 432): GC_CONCURRENT freed 397K, 46% free 3532K/6535K, external 716K/1038K, paused 2ms+4ms
I/TTR_IAB ( 412): CheckBillingSupported response code: RESULT_OK
I/TTR_IAB ( 412): onBillingSupported: true
D/TTR_IAB ( 412): request id: -1
I/AirMail ( 441): Service started with intent=Intent { act=com.tapulous.taptaprevenge4.RESTART cmp=com.tapulous.taptaprevenge4/com.urbanairship.airmail.AirMailService }
W/AirMail ( 441): Attempted to initialize AirMailService, but the databaase has not finishised initializing. Waiting for DB to finish initializing, or for a heartbeat to launch the service.
D/Vold ( 58): usb, 1
D/Vold ( 58): == current usb device: 19D2/1001 ===
D/Vold ( 58): === USB Switch: /etc/usb_modeswitch.sh /etc/usb_modeswitch.d/19d2_1001 &
D/Vold ( 58): usb, 1
D/Vold ( 58): usb, 2
D/Vold ( 58): usb, 2
I/Lights ( 86): >>> Enter set_buttons_light
D/dalvikvm( 432): GC_CONCURRENT freed 455K, 47% free 3576K/6663K, external 716K/1038K, paused 4ms+5ms
D/Finsky ( 432): [1] 5.onFinished: Installation state replication succeeded.
D/Vold ( 58): usb, 1
D/Vold ( 58): == current usb device: 19D2/1003 ===
D/Vold ( 58): usb, 1
D/Vold ( 58): usb, 1
D/Vold ( 58): usb, 1
D/Vold ( 58): usb, 1
D/Vold ( 58): usb, 1
D/Vold ( 58): usb, 1
D/Vold ( 58): usb, 1
D/Vold ( 58): usb, 1
D/Vold ( 58): usb, 1
D/Vold ( 58): usb, 1
D/Vold ( 58): scsi_device, 1
D/Vold ( 58): === SCSI Switch: /etc/usb_modeswitch.sh /etc/usb_modeswitch.d/19d2_1001 &
D/Vold ( 58): scsi_device, 1
D/Vold ( 58): Volume udisk state changing 0 (No-Media) -> 1 (Idle-Unmounted)
I/MountService( 86): onEvent:: raw= 605 Volume udisk /mnt/udisk state changed from 0 (No-Media) to 1 (Idle-Unmounted) cooked = 605 Volume udisk /mnt/udisk state changed from 0 (No-Media) to 1 (Idle-Unmounted)
I/StorageNotification( 144): Media {/mnt/udisk} state changed from {removed} -> {unmounted}
D/VoldCmdListener( 58): volume shared /mnt/storage ums
W/VoldConnector( 86): doCmd(volume shared /mnt/storage ums) bypass 605
W/VoldConnector( 86): doCmd(volume shared /mnt/storage ums) bypass 630
I/MountService( 86): onEvent:: raw= 630 Volume udisk /mnt/udisk disk inserted (8:0) state 1 cooked = 630 Volume udisk /mnt/udisk disk inserted (8:0) state 1
V/MountService( 86): Volumn /mnt/udisk inserted.
D/VoldCmdListener( 58): volume mount /mnt/udisk
I/Vold ( 58): /dev/block/vold/8:0 being considered for volume udisk
D/Vold ( 58): Volume udisk state changing 1 (Idle-Unmounted) -> 3 (Checking)
E/Vold ( 58): /dev/block/vold/8:0 failed to mount via VFAT (No medium found)
D/Vold ( 58): Volume udisk state changing 3 (Checking) -> 1 (Idle-Unmounted)
W/Vold ( 58): Returning OperationFailed - no handler for errno 123
W/VoldConnector( 86): doCmd(volume mount /mnt/udisk) bypass 605
W/VoldConnector( 86): doCmd(volume mount /mnt/udisk) bypass 605
W/MountService( 86): Insertion mount failed (-1)
I/MountService( 86): onEvent:: raw= 605 Volume udisk /mnt/udisk state changed from 1 (Idle-Unmounted) to 3 (Checking) cooked = 605 Volume udisk /mnt/udisk state changed from 1 (Idle-Unmounted) to 3 (Checking)
I/MountService( 86): onEvent:: raw= 605 Volume udisk /mnt/udisk state changed from 3 (Checking) to 1 (Idle-Unmounted) cooked = 605 Volume udisk /mnt/udisk state changed from 3 (Checking) to 1 (Idle-Unmounted)
I/StorageNotification( 144): Media {/mnt/udisk} state changed from {unmounted} -> {checking}
I/AudioService( 86): AudioFocus requestAudioFocus() from android.media.AudioManager@40693020
D/AudioHardware( 63): AudioHardware pcm playback is exiting standby.
D/AudioHardware( 63): openPcmOut_l() mPcmOpenCnt: 0
W/MediaPlayer( 86): mediaplayer went away with unhandled events
D/testcompa( 144): win title: PopupWindow:405a5da8 ;support: true ;targetVersion: 9
I/StorageNotification( 144): Media {/mnt/udisk} state changed from {checking} -> {unmounted}
D/VoldCmdListener( 58): volume shared /mnt/storage ums
D/testcompa( 144): win title: PopupWindow:405b61b8 ;support: true ;targetVersion: 9
D/testcompa( 144): win title: PopupWindow:405c5c68 ;support: true ;targetVersion: 9
W/AudioFlinger( 63): write blocked for 350 msecs, 2 delayed writes, thread 0xdd68
I/AudioService( 86): AudioFocus abandonAudioFocus() from android.media.AudioManager@40693020
W/MessageQueue( 86): null sending message to a Handler on a dead thread
W/MessageQueue( 86): java.lang.RuntimeException: null sending message to a Handler on a dead thread
W/MessageQueue( 86): at android.os.MessageQueue.enqueueMessage(MessageQueu e.java:196)
W/MessageQueue( 86): at android.os.Looper.quit(Looper.java:173)
W/MessageQueue( 86): at com.android.server.NotificationPlayer.startSound(N otificationPlayer.java:133)
W/MessageQueue( 86): at com.android.server.NotificationPlayer.access$500(N otificationPlayer.java:43)
W/MessageQueue( 86): at com.android.server.NotificationPlayer$CmdThread.ru n(NotificationPlayer.java:170)
I/AudioService( 86): AudioFocus requestAudioFocus() from android.media.AudioManager@40693020
W/MediaPlayer( 86): mediaplayer went away with unhandled events
I/AudioService( 86): AudioFocus abandonAudioFocus() from android.media.AudioManager@40693020
W/MessageQueue( 86): null sending message to a Handler on a dead thread
W/MessageQueue( 86): java.lang.RuntimeException: null sending message to a Handler on a dead thread
W/MessageQueue( 86): at android.os.MessageQueue.enqueueMessage(MessageQueu e.java:196)
W/MessageQueue( 86): at android.os.Looper.quit(Looper.java:173)
W/MessageQueue( 86): at com.android.server.NotificationPlayer.startSound(N otificationPlayer.java:133)
W/MessageQueue( 86): at com.android.server.NotificationPlayer.access$500(N otificationPlayer.java:43)
W/MessageQueue( 86): at com.android.server.NotificationPlayer$CmdThread.ru n(NotificationPlayer.java:170)
I/AudioService( 86): AudioFocus requestAudioFocus() from android.media.AudioManager@40693020
I/AudioService( 86): AudioFocus abandonAudioFocus() from android.media.AudioManager@40693020
I/Process ( 362): Sending signal. PID: 362 SIG: 9
I/ActivityManager( 86): Process mobi.mgeek.TunnyBrowserolphinNotification (pid 362) has died.
D/AudioHardware( 63): AudioHardware pcm playback is going to standby.
D/AudioHardware( 63): closePcmOut_l() mPcmOpenCnt: 1
I/Lights ( 86): >>> Enter set_buttons_light
D/testcompa( 424): win title: AtchDlgrg.jtb.alogcat/org.jtb.alogcat.LogActivity ;support: true ;targetVersion: 11
the log was started just before putting the stick in and stopped after safe to remove message came up on screen

i cant test the 1.5 rom as my computer has broken this morning will try later when i have access to a computer

[Finless]

Cybertwigg... THANKS for that!

I am not seeing anything significant other than this:

E/Vold ( 58): /dev/block/vold/8:0 failed to mount via VFAT (No medium found)
D/Vold ( 58): Volume udisk state changing 3 (Checking) -> 1 (Idle-Unmounted)
W/Vold ( 58): Returning OperationFailed - no handler for errno 123


Which is interesting but I really do need to see 1.4 ROM not 1.5.

Does your 3G stick work? on 1.5 or 2.0?

Bob

[cybertwigg]

its not mine I borrowed it with the view of checking it on both 1.5 and 2.0 and comparing the logcat output but my hdd in my computer has just frozen and i am in the process of fixing it so I am unable to re flash to 1.5 to check the logcat on that as soon as i fix my computer i will re flash to 1.5 and see what happens on that from reading how the sticks work am i understanding correctly

they 1st mount as usb mass storage
the usb_modeswitch.sh then switches the mode to modem
it should then mount as modem device and work
the line
D/Vold ( 58): === USB Switch: /etc/usb_modeswitch.sh /etc/usb_modeswitch.d/19d2_1001 & does correctly link to my modem make and model
and it changes it to 19d2/1003 on this line
D/Vold ( 58): == current usb device: 19D2/1003 ===
which is correct for mode switching the stick into modem mode but then for some reason it attempts to mount as udisk witch as far as i am aware is for usb storage correct me if any thing above is wrong
is there any code to try in terminal that will mount a usb modem after the mode switch has happened to see if i can manual mount or am i barking up the wrong tree

hope this helps somehow
ricky