I seem to be having an odd problem with my new G1.
In any Cupcake build (JF 1.51, TheDude's 1.2, Official ADP) I flash, neither the compass nor the accelerometer sensors work at all. I have flashed between them several times, with an Alt+W each time, so I know it's not a bad flash.
The strange thing is, when I jump back to an official RC29 build, both sensors work fine. I haven't tried RC30 or anything else, but I know the sensors are physically functional.
I have re-flashed the latest radio as well, as it is currently using 2.22.19.26I.
If anyone can help me with this problem, I would greatly appreciate it.
gigawatts said:
I seem to be having an odd problem with my new G1.
In any Cupcake build (JF 1.51, TheDude's 1.2, Official ADP) I flash, neither the compass nor the accelerometer sensors work at all. I have flashed between them several times, with an Alt+W each time, so I know it's not a bad flash.
The strange thing is, when I jump back to an official RC29 build, both sensors work fine. I haven't tried RC30 or anything else, but I know the sensors are physically functional.
I have re-flashed the latest radio as well, as it is currently using 2.22.19.26I.
If anyone can help me with this problem, I would greatly appreciate it.
Click to expand...
Click to collapse
I think your using the pre-cupcake apps. Did u download the apps after you updated or did you install them from a back up?
Best way to check, You should got to settings and then sounds&display and check off orientation. You phone should switch from portrait to landscape when you rotate any program (except homescreen). If that works then nothing is wrong with your phone. If it doesn't then something happened somewhere weird
any apps i have installed have been after i flashed a rom (after a wipe) and not from a backup. Plus, something as simple as Google Maps or the Browser App should just rotate without opening the keyboard.
Best way to check, You should got to settings and then sounds&display and check off orientation.
Click to expand...
Click to collapse
By that I assume you place the check mark (lit green) next to the option, not "check it off" (not lit green). I have tried both checked and unchecked in pre-installed apps like maps and browser, and still nothing.
Small update. I just flashed JF's v1.43_RC33 with root, keeping the same more recent radio, and both sensors work there, as they do in RC29. It seems to be ONLY cupcake based roms where they don't work.
Any other suggestions anyone has for me? I might try a hero build next, to see if they work there, but I'm not sure how stable they are yet.
Any help/suggestions would be greatly appreciated!
Accelerometer fix
http://forum.xda-developers.com/showpost.php?p=4081673&postcount=4885
I tried your suggestion, and it did not work. Unlike the other user reporting that the sensors would work for a short time after reflashing, mine has never worked after a cupcake flash. Only after a pre-cupcake flash.
Although ideas like that are what I am looking for, possible corrupt config files that need to be cleared or maybe a mod probe command of some sort to activate or wake up the sensors.
Upon some more inspection, I get the feeling something is wrong with my akmd process, or whatever executable generates the akmd_set.txt compass and accelerometer calibration data. I tried to follow some instuctions to purge the akmd_set.txt file to clear any bad config, but the file is no where to be found. My phone doesnt seem to generate one at all when it's booting.
The akmd process does remain running in the background, as here is its ps output:
Code:
# ps | grep akmd
compass 77 1 1320 328 c020d268 afe0c45c S /system/bin/akmd
This is the output I get from logcat when I try to manually run the /system/bin/akmd process or when it restarts automatically after being killed:
Code:
D/AKMD ( 362): akmd 1.6.4 START
D/AKMD ( 362): library version: 1.2.1.1129
D/AKMD ( 362): Compass OPEN
D/AKMD ( 362): No calibration data
D/AKMD ( 362): Can not initial compass parameters error: -5
and this is the output I get when I run a program like Orienteer:
Code:
I/ActivityManager( 90): Starting activity: Intent { action=android.intent.action.MAIN categories={android.intent.category.LAUNCHER} flags=0x10200000 comp={com.deafcode.android.Orienteer/com.deafcode.android.Orienteer.Orienteer} }
I/ActivityManager( 90): Start proc com.deafcode.android.Orienteer for activity com.deafcode.android.Orienteer/.Orienteer: pid=363 uid=10041 gids={}
D/SensorManager( 363): found sensor: AK8976A 3-axis Accelerometer, handle=0
D/SensorManager( 363): found sensor: AK8976A 3-axis Magnetic field sensor, handle=1
D/SensorManager( 363): found sensor: AK8976A Orientation sensor, handle=2
D/SensorManager( 363): found sensor: AK8976A Temperature sensor, handle=3
D/dalvikvm( 363): GC freed 920 objects / 64320 bytes in 92ms
D/LocationManager( 363): Constructor: service = [email protected]
D/Sensors ( 90): sensors=00000005, real=00000005
D/GpsLocationProvider( 90): setMinTime 2000
W/IInputConnectionWrapper( 145): showStatusIcon on inactive InputConnection
I/ActivityManager( 90): Displayed activity com.deafcode.android.Orienteer/.Orienteer: 1313 ms
D/dalvikvm( 145): GC freed 795 objects / 45896 bytes in 165ms
D/GpsLocationProvider( 90): TTFF: 7203
Maybe this will give someone some more insight as to the problem I am having.
hello,
i me french and i have the same problem.
No akmd_set.txt on my phone.
If you are a solution could you partage it ?
I think it's a driver problem but i'm not sure.
JEEP
Unfortuantly I have still not found a solution, but continue to look for one. I will let you know here if I do manage to solve it.
I am also having the same problem. Wiping does not fix it and the method stated by Cyanogen didn't work either. I don't know if this will be any help, but I do know the accelerometer issue started about 3 or 4 days ago for me. Maybe if I list things I've done to my phone in the last few days, it might help narrow down the cause if others with the same issue compare their experiences to each other.
I have a US T-Mobile G1 and I have been rooted since February. Since that time I have upgraded to (and currently use) the latest radio from HTC, Haykuro's SPL, and a class 6 4gb card. I've also been through more roms than I can count in that time, all without an accelerometer issue till now.
Now that I've got all that out of the way here's the more relevant stuff:
Within the last week I have upgraded to Cyanogen's 1.3.1 recovery boot and installed the latest JAC Hero build. I repartitioned my card into 3 partitions with the directions given in JustAnotherCrowd's thread using parted in the recovery's console.
Code:
#parted /dev/block/mmcblk0
rm 1
rm 2
mkpartfs primary fat32 0 3420
mkpartfs primary ext2 3420 3932
mkpartfs primary linux-swap 3932-3964
This is the first time I've ever used apps to sd. After using that rom for about a day, I switched to Cyanogen's build and wiped my user data without wiping the ext partition of my sd card and I continued to use the swap partition on my Cyanogen build. I'm fairly sure but not 100% certain that the accelerometer was still working at this point. Soon after installing this rom, Cyanogen released an update including the compcache modules to replace the linux-swap setup. I installed the custom userinit.sh script to system/sd to activate compcache. Then Cyanogen released another update (immediate bug fixes) almost as soon as I got this rom working. I flashed the update.zip, but then it started to boot loop. I wiped the phone (not the ext partition), still boot looped. I took out the sd, still boot looped. I put the sd card back in wiped again, reflashed, and then clicked "repair ext file system". STILL BOOT LOOPED! (Don't say I just wasn't giving it enough time to boot because I acctually watched the boot animation flicker in and out for a second and start over.) Next, I used fastboot to restore only the user data from a nandroid backup of an older Cyanogen rom. This time it worked. Next, I installed the audio resources to system/sd/media and linked them using the userinit.sh file. The next day, I realized that the accelerometer was no longer functioning.
I hope this description helps to figure this out.
I'm having the exact same issue.
testing567, can you post the userinit.sh file you are currently using, and possibly you or someone else post their userinit.sh of a phone with a working accelerometer and compass here?
I am thinking that one of my init scripts may not be calling the akmd service properly, as in not with the correct permissions or something, and thus not calibrating itself on boot. I was planning on upgrading to the latest cyanogen update today, as i am running 3.6.5 right now. I was also considering upgrading my SPL to a dev SPL so i can use nandroid to backup (getting a little tired of loosing everything when attempting different roms to fix this issue).
I got my userinit.sh from this post.
http://forum.xda-developers.com/showpost.php?p=4140826&postcount=74
I also decided to take advantage of the media symlinking already in this script and pushed the audio resources to system/sd/media/.
I've always had the same issue when upgrading to a cupcake based rom. Nobody else until recently seemed to share my misfortune (sorry for everyone else). There is an exception though, JF 1.5 (T-Mobile) build the sensors work (although miscalibrated). I haven't found any other solutions or any other way to generate the settings file. My process output appears to be the exact same as you've posted.
I'll keep trying some things but I just want to keep this alive incase anyone else needs a fix and one of us comes up with a solution.
RemoteDJ, I may actually have a solution to your miscalibrated problem. In the process of going through and trying to get my sensors working, I created an empty akmd_set.txt file with chmod 777 permissions (just so it wouldnt ***** about some user permissions when trying to edit it), and then rebooted the phone. Upon looking at the file after reboot, it was filled with calibration data.
Although this has not fixed my problem, it may help you. Also, the application "Bubble" has a calibrate sensors menu option, which may help you too. I may have to try reverting back to JF 1.5 to see if I have better luck there. Was that JF 1.51 you were using? If not, please advise.
Yes it was JF 1.51, it's funny because I just got done making a blank chmod 777 akmd_set.txt lol. Of course i'm on the latest stable cm-3.6.8.1 currently and the sensor doesn't work at all.
Just so we stay up to date with each others findings, I also pulled the akmd app from Haykuro's ION, JF 1.43, JF 1.51, Official RC33 and the current CM build. I have only tried replacing the current one with the ION app (in recovery), so far no change, but I think the only file difference I noticed out of the files I pulled was that the JF 1.43 and Official RC33 seemd to be the same (haven't hashed them to verify) and different then the others which seem to be the same but since I haven't hashed any of them to verify yet I can't say for sure.
I am calling it a night right now but will let you know if I find anything tomorrow.
Just a followup with the hash info.. looks like I was correct:
517a87a4e6caa5e66f0520c68dcb7c0e - Official RC33
517a87a4e6caa5e66f0520c68dcb7c0e - JF 1.43
c3a80124ab072f9bf12cc9e4155a0f9f - JF 1.51
c3a80124ab072f9bf12cc9e4155a0f9f - ION
c3a80124ab072f9bf12cc9e4155a0f9f - CM 3.6.8.1
Another Edit: I am apparently not good at going to sleep.. Good News! (semi).
I left the akmd_set.txt in place (it got filled with data just like yours)
replaced ion/cm akmd with jf 1.43 and now the sensor appears to be working (although still miscalibrated for me, this might be a hardware issue.. lots of drops).
step by step.
copy jf1.43 akmd to sdcard (i just pulled it out of the update zip).
reboot recovery
mount /system
rm /system/bin/akmd
mount /sdcard
cp /sdcard/jf1.43_akmd /system/bin/akmd
then umount (probably not required)
reboot.
It still didn't work, but I deleted the akmd_set.txt via adb and then rebooted and voila!
Let me know if any of that works for you
Edit: I was able to fix my calibration by reverting to the rc30 akmd, I have absolutely no idea why my device is so picky, but it only has ever had correct calibration with accelerometer on the rc29/30 builds (this includes all official t-mobile ota releases). Anyway just wanted to through that out there incase anyone else uses the jf1.43 and is miscalibrated.
RemoteDJ,
Thank you so much for that suggestion! That totally worked for me! I flashed cm-3.6.8.1 tonight and replaced its /system/bin/akmd binary with the one from jf 1.42. After messing around with some permissions (I failed to realize the akmd binary was not set as executable when i moved it over ) i was able to create a blank akmd_set.txt, chmod 777 it, and then restart the akmd service (stop akmd, followed by start akmd).
I can not thank you enough for this suggestion! Guess it just took another similar brain bashing away at the same problem to solve it. I just wonder why this is not a problem for a lot of other people out there. It's the same hardware, so you would think everyone upgrading to cupcake would have an incompatible akmd binary. Strange...
Sweet, I'm really glad it worked for you!
I can't imagine for the life of me why other people don't have similar problems, but then again I've had a few problems that seemed indivualized to my device lol. Its only recently that I discovered a few other people were having problems with the accelerometor.
Oh well, all in all just glad this worked.
Maybe we can get Cyanogen to include this in his FAQ as an alternative for sensor repair for the people like us. I might reply on the latest build thread later, anyway have a good one.
So far I haven't had any luck with this. I'm actually tempted to send my unit back to HTC with the ota 1.5 cupcake on it and see what happens. I'm not sure if it was working when they sent it to me or not. It doeswork with the rc29 though.
I'm having the same issue, no compass apps seem to work, google sky maps doesn't work , the level app doesn't work, all are froze.
How can I fix it?
As certain Pandora users on this board may know, Orbot never works on Enomther's rom, but runs fine on CM and presumably stock (haven't tested stock). Orbot cycles between "Starting Orbot" and "Could not start Tor process", does this twice, then exits.
It appears to be failing at findProcessId(TorServiceUtils.java:68).
The tor log reveals:
1. "Orbot is starting"
2. "got tor proc id: -1" (i'm guessing -1 is an error flag)
3. "Couldn't start Tor process"
It then says "checking for an existing tor process", then quits on error.
I guess it can't find the tor background service.
Edit: I think the tor service isn't starting, even though Orbot thinks it did. Might have something to do with iptables or something.
Logcat: http://pastebin.com/6GESYFmm
I'm not a dev, but is there a simple solution to this? Is there something obvious I can change in the Orbot source, maybe I can compile my own client.
Thanks guys.
You're not connected to WiFi, right? Using cellular data?
See if you receive the same warnings on CM6:
09-25 04:29:38.433 W/ORBOT ( 1990): Unable to get proc id for: /data/data/org.torproject.android/tor
09-25 04:29:38.433 W/ORBOT ( 1990): java.lang.NumberFormatException: unable to parse 'app_61' as integer
Other than that, the error dump is binary - not much to do with it...
Background:
I updated to JVB though Kies when it became available (code: XEE). Before that I was on Voodoo, but on RFS.
After the update, it ran for some time but suddenly a week or so ago I got quite a number of problems with the phone acting up (not wanting to hang up after calls -the green status bar would remain, I could not even hang up it in the notification area). Generally the phone was also using a lot of RAM.
I thought, let's do a factory reset. When I did this all my user apps did not seem to get deleted although I did get the "New phone" startup sequence. I
Finally, I booted into CWM recovery but trying to do the reset there, I got some errors
Code:
Formatting /data…
E:format_volume: rfs format failed on /dev/block/mmblk0p2
Formatting /dbdata…
E:format_volume: rfs format failed on /dev/block/stl10
Deleting Meta Data
Formatting /cache…
E:format_volume: rfs format failed on /dev/block/stl11
When this failed to work a reflashed the firmware (Code: NEE) with repartition and everything and everything was clean. I rooted via CF-Root and restored all users apps + data for these. I also restored some "system" data such as call logs, smses, etc.
After a day I started getting force closes when I used the dialler. I.e. I start typing e.g. "253" and the phone tries to match this against contacts and after 1 sec, I get a force close. OK I thought, maybe I should not have restored system data.
I restored from a Nadroid backup (that had root) and started all over with user apps. I did not touch any system data this time.
I still get the force closes often when I try to find a contact using the key pad.
From aLogCat:
Code:
5-06 16:15:51.855 E/JavaBinder( 482): !!! FAILED BINDER TRANSACTION !!!
05-06 16:15:51.859 E/InputDispatcher( 482): channel '40c41cb8 com.android.contacts/com.sec.android.app.contacts.PhoneBookTopMenuActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x8
05-06 16:15:51.859 E/InputDispatcher( 482): channel '40c41cb8 com.android.contacts/com.sec.android.app.contacts.PhoneBookTopMenuActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
05-06 16:15:51.878 E/JavaBinder( 482): !!! FAILED BINDER TRANSACTION !!!
05-06 16:15:52.871 E/libBlurEffect(23357): AndroidBitmap_getInfo() failed ! error=-1
05-06 16:15:54.562 W/FastDormancy( 585): before ======= ENTER DORMANCY =======
05-06 16:15:58.742 E/InputDispatcher( 482): channel '40dcbd58 com.sec.android.app.dialertab/com.sec.android.app.dialertab.DialerTabActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x8
05-06 16:15:58.742 E/InputDispatcher( 482): channel '40dcbd58 com.sec.android.app.dialertab/com.sec.android.app.dialertab.DialerTabActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
05-06 16:15:59.574 W/FastDormancy( 585): before ======= ENTER DORMANCY =======
05-06 16:16:04.617 W/FastDormancy( 585): before ======= ENTER DORMANCY =======
05-06 16:16:05.898 W/InputMethodManager(23566): Ignoring onBind: cur seq=987, given seq=986
05-06 16:16:09.644 W/FastDormancy( 585): before ======= ENTER DORMANCY =======
Does anybody have any idea what may be the cause of this?
BTW I use e-mail and Nitrodesk Touchdown to get contacts on my phone.
you should install another rom.. easiest solution. have you tried customs?
Well, no, but should I not be able to use the standard Samsung Rom fit for my device and area?
No clever people can help out here?
If at all prossible, I'd like to prevent sending in the phone for service since this will take at least 2 weeks.
FINALLY I have found someone having the same problem as me.
I have a Samsung Exhibit 4G and have this same issue with the contact list closing when I don't want it to. I sometimes (not always) get kicked back to the home screen when viewing a contact list, call logs, or when starting to dial a number via the keypad. The "force quitting" or whatever you call it seems to happen in relation to an activity that searches the contacts in some way.
I recently discovered aLogcat and immediately after this happening I saw the same "DialerTabActivity" error that fjelsten was seeing.
My phone was finally rooted recently, and I can't wait for a custom rom to come out so I can be rid of this B.S. stock ROM.
Some people (like me) loosing the signal to the provider. WiFi is ok, but to get back the mobile connection I had to reboot the phone (1-2 times a working day. I never had this problem over the weekend).
I could pin down this behavior to a fast switching between mobile connection and no mobile connection. If the connection is just reestablished and in the next moment it is lost again the phone hangs. I take the underground to reach the office. That is the reason why I only have this issue on working days
So the solution is clear: Stop working. Enjoy the free time
I used "How to get useful logs" from tonyp with the App: SysLog and found in the modem.log the following error: (full log attached)
( 98): dlc[12] atchannel: at_send_command_full() at handshake fails, err - 12. Restarting rild
( 98): lge-ril: handle Cp Reset (CP Reset Cause - 1, RIL recovery activated flag - 0, dlc - 12)
( 98): [0485]< DEACTIVATE_DATA_CALL fails by E_RAIDO_NOT_AVAILABLE
( 98): dlc[12]: lge-ril - requestInterface: Exiting DLC handler, thread - 22231000. s_dlc_handler_create_tracker - 0x6013f
( 759): Exception processing unsol response: 1054Exception:java.lang.RuntimeException: Unrecognized unsol response: 1054
( 759): Unrecognized RIL errno 16
Click to expand...
Click to collapse
I tried a lot of different basebands but could not fix the problem. The only difference was the RIL errno changed from 16 to 14 ???
The basebands I tried are: V30b, V30a, V30c (SU660 - because the sticker under the battery says: Made in Korea), V20m, V20s. In the end I tried different RILs but that only made the problem worse. Now I am back on the original cm10.1 RIL.
Losing the IMEI in the phone is not the problem. I already checked this.
I am pretty sure it is not ROM related because I experienced the same thing on cm7.2 and now on cm10.1 from tonyp on the old and new Boot loader
Regards
Fidi
Possible solution
Hi,
it looks like I found a solution for the loosing signal problem.
After trying all kinds of differnt basebands I switched to an old not recommended baseband. No signal lost for 4 working days in a row :fingers-crossed:
I am now on Baseband 0823-V21b and using ROM tonyp cm10.1 (04)
For the baseband have a look at the P990 Complete Baseband Overview Thread from tonyp: http://forum.xda-developers.com/showthread.php?t=1658047
Cheers
Fidi
Thanks for your informations, i think i have the same problem. Please respond if you have further informations!
I keep you updated:
Over the weekend: Everything worked fine and stable. I used the phone "normal" over the last three days. Including running with Endomondo Sports Tracker and some other parts. The phone is still stable. No reboot since the downgrade to Baseband 0823-V21b.
If I don't get any issues over the week I think that's the solution.
trampi did you downgrade your baseband too? I hope it's a working solution for you too.
Cheers
Fidi
Thank you Fidi!
I have the same logs when my data connection drops, currently with tonyp's T-Build 4 and Kowalski 125 and baseband 0725-V10d.
I will try this out, and report back.
Well I had this data drop issue but when using tonyp's T-Build I started having drops in the whole mobile connection (no voice as well). So I followed his recommendation and flashed BB V30a but that did nothing. Then I tried his Paranoid Android and it's working great!
Bad news here:
7 hours after flashing the baseband 0823-V21b (tonyp T-Build 4, kowalski kernel 125 exp), I got the same error again, and no data, no voice. And only reboot will fix it.
As soon as I see
## AT COMMAND TIMEOUT ##
in the radio log, I'm in the same situation again.
then at the moment of the connection blackout, always followed by:
E/RILJ ( 584): Exception processing unsol response: 1054Exception:java.lang.RuntimeException: Unrecognized unsol response: 1054
and
D/RIL ( 98): dlc[5]: lge-ril - requestInterface: Exiting DLC handler, thread - 7126560. s_dlc_handler_create_tracker - 0x611df
Only with this baseband I don't see this anymore:
E/GSM ( 593): Unrecognized RIL errno 16
I've found a workaround to restore the connection without rebooting:
first kill the /system/bin/rild process
then kill the com.android.phone process
They will both restart automatically.
So this looks like a problem with the ril. Is the ril not compatible with the baseband?
This is also suggested by the "Exception processing unsol response" messages: ril is not able to handle certain baseband commands, although this could also be a corruption on the baseband side...
Now creating a script to automate this workaround will at least give back the connection immediately.
Hi gios_
I am running on the same configuration: 0823-V21b (tonyp T-Build 4, kowalski kernel 125 exp)
If you could provide the script that will check for the error and kill the two services that would be gorgeous. That will solve the problem even if we don't find a "real" solution :fingers-crossed:
Here's the script to fix the connection:
Code:
#!/system/xbin/sh
ps|grep phone|cut -c10-14|xargs kill
ps|grep rild|cut -c10-14|xargs kill
To quickly execute it, you can use gscript (then leave out that first line).
do you guys already check with this solution?
Code:
http://forum.xda-developers.com/showthread.php?t=2075564
antec123 said:
do you guys already check with this solution?
Code:
http://forum.xda-developers.com/showthread.php?t=2075564
Click to expand...
Click to collapse
I did not try that solution because their problem seems to be something else: transition from wifi to data not working; whereas our problem is connection dropping (not only data) at a random moment.
Also my IMEI number is transmitted correctly, so I doubt changing it will do any good.
gios_ said:
I did not try that solution because their problem seems to be something else: transition from wifi to data not working; whereas our problem is connection dropping (not only data) at a random moment.
Also my IMEI number is transmitted correctly, so I doubt changing it will do any good.
Click to expand...
Click to collapse
i used that solution, and with kowalski kernel exp 125 i haven't gotten any data loss. up time already 4 days. using kowalski kernel exp 124, i always get data loss and need reboot.
i use bb v30b ics, and ril (default). rom is using tony bulid 4 cm10.1 newBL. and using 2G always.
Yes, I tried this. But I never lost my IMEI and the solution did not help me
At the moment I am happy with my old baseband (no drops over two weeks). But It looks like that's only a solution for my phone. Maybe we should create a script, that scans the logs for the error and if the connection drops we could restart it with the solution from gios_
FidiS said:
Yes, I tried this. But I never lost my IMEI and the solution did not help me
At the moment I am happy with my old baseband (no drops over two weeks). But It looks like that's only a solution for my phone. Maybe we should create a script, that scans the logs for the error and if the connection drops we could restart it with the solution from gios_
Click to expand...
Click to collapse
yeah i think that true. I'm also confused why some people still have data loss with kowalski exp 125 and some people don't, so wierd
I will stick with baseband 0823-V21b. Still there is no real issue.
There is only remaining thing. In the situations when I formerly lost my connection now the phone rarely heats up for a short time with can drain the battery about 3%. After that the connection is reestablished and everything works as it should
Cheers Fidi
Hi,
I'm currently running Slimkat 6.7 on my i8190, and it's fantastic. The only problem is that the system log is filling up with the following line:
E/bt_upio (31479): upio_set : open(/proc/bluetooth/sleep/btwrite) for write failed: No such file or directory (2)
I've googled it, and there doesn't appear to be much info around as to a fix - does anyone have any idea whether this bug is known/fixed?
Many thanks, Jaime
Ok, at the moment, I'm not even sure whether this is a kernel or a rom problem. I'll try flashing a different kernel or two, and I'll report back in case anyone can pitch in with some helpful advice...
J
Ok, I've tried the kernel built in to Android Andi's latest (Slim-golden-4.4.4.build.7.2.1-UNOFFICIAL-20140812-2310.zip) and that has the bug. I've also tried flashing the 2 kernels bundled into GT-I8190-ANY-Kernel_v1.6.zip (that's version 3.0.31 and 3.0.44) and they too have the same problem. Any ideas anyone?