Hi there...
Today! i had flashed every Custom Rom here in this X10 Mini Pro Android Thread.
On every ROM instead of the Stock Rom i have random reboots.
I tryed every way....back to Stock....wipe twice and reboot, different SD Card etc....etc...
The last ROM today was [ROM 16-07-2011] Andread 2.2.9 Pro v7f and still the same...
Connect my Phone to my PC and install market apps....reboot...
The Phone lies on my table....i will unlock.....reboot....
I now don't know what to do.....only one idea...use Stock ROM (no way) or sell the Phone and wait for tne X10 Mini Pro 2...
The Dev's here in this Forum make really great work! I hope i'm an exception...
same here. im back on stock for a month now. i thought i am the only one with this problem
im sick of rebooting just when you need your phone.
Sadly its a lot to do with the se kernel not being dessigned perfectly I believe (tell me if I'm wrong) as the way they link things is bad but for me on cm7 15.0 its fine had 2 since v15 came out and I flashed same day if it makes a difference i m on a.106 if that's correct bb I know its the new a one not c I can't remember full name
Sent from my U20i using XDA App
I have never ever experienced rebooting with any rom. Even though many people have reported it in many roms. I never have a single reboot.
I guess that all phones suffer different side-effects when roms are installed. For instance, my sd card doesn't work in any of the Gingerbread roms (2.3) but it works fine for everyone else. And the SD card works perfectly fine in (2.3.4). It's very very strange, it seems everyone's device acts differently.
I am truely sorry that you are experiencing this issue, maybe someone else can help you. It might be just an error for you only like with my SD card problem.
Hope you solve it
Regards
Com.Chakotey said:
Hi there...
Today! i had flashed every Custom Rom here in this X10 Mini Pro Android Thread.
On every ROM instead of the Stock Rom i have random reboots.
I tryed every way....back to Stock....wipe twice and reboot, different SD Card etc....etc...
The last ROM today was [ROM 16-07-2011] Andread 2.2.9 Pro v7f and still the same...
Connect my Phone to my PC and install market apps....reboot...
The Phone lies on my table....i will unlock.....reboot....
I now don't know what to do.....only one idea...use Stock ROM (no way) or sell the Phone and wait for tne X10 Mini Pro 2...
The Dev's here in this Forum make really great work! I hope i'm an exception...
Click to expand...
Click to collapse
check the smalband version. meybe thats it
I agree that there seems to be differing effects of installing a custom rom, device by device.
I too had the sdcard issue with gingerbread, intermittently. Sometimes following the same process when installing a rom can result in a different level of stability.
Currently i'm using froyocomb 1.3, but have not been able to get past the app install issues.
Overall my experience with custom roms has been good, but right now i'm stuck between a not working froyocomb, a sonybread or cm7 v15 with poor camera, or waiting 2 hours for 6.01 to boot and not feeling to optimistic. (though in reality i'm spoilt for choice by all the hard working devs out there)
I would suggest looking up an older cm6 i found them much more reliable (can't remember which one sorry)
batwingnz said:
or waiting 2 hours for 6.01 to boot and not feeling to optimistic
Click to expand...
Click to collapse
well in CM6 v6.01 booting is normal beacuse the bug have ben fixed.it takes max 5-10 min maybe even 2-5min.
zomfg i'm a retard, didn't see it in changelog. 6.01 here i come.
batwingnz said:
zomfg i'm a retard, didn't see it in changelog. 6.01 here i come.
Click to expand...
Click to collapse
hehe it happens and after you install rom use my qick hotfix for 123 keys posted allmost on the end of thread
I also have random reboots with ALL roms I've tried. Latest now is Cyanocomb v1.3 and I get random reboots (although this ROM is the one with LEAST reboots for me (perhaps once a week?))
Think I will buy the Motorola Droid 3 when it comes out, hopefully it will stop reboots
PTGamer said:
check the smalband version. meybe thats it
Click to expand...
Click to collapse
Mhhh my Baseband is M76XX-TSNCJOLYM-53404015
I think thats the right? Isn't it?
Com.Chakotey said:
Mhhh my Baseband is M76XX-TSNCJOLYM-53404015
I think thats the right? Isn't it?
Click to expand...
Click to collapse
Is there a debug/logging tool that can help us diagnose WHY our devices reboot?
E.g. like mini dump files and windows debug kit minidump viewer pointing to sys files that probably caused the crash?
svyr said:
Is there a debug/logging tool that can help us diagnose WHY our devices reboot?
E.g. like mini dump files and windows debug kit minidump viewer pointing to sys files that probably caused the crash?
Click to expand...
Click to collapse
thats a very good idea!!
there is 'logcat'. you can pipe the output to a file and try to force the random reboot. You possibly need a large sdcard - and I recommend to be veryvery careful when piping it into a file - if you write it into your phone memory, it may not come up ^^
there are also several apps like "alogcat". but this does not store regularily - at least every 15 minutes. - thus after the crash there is no log from the crash. But yyou can also try that. maybe you find another app. but piping may be the solution.
btw I do not provide a howto, you have to know how to do that or must look for an app that helps you - I can't really recommend one, but there are a lot
Snoopo said:
there is 'logcat'. you can pipe the output to a file and try to force the random reboot. You possibly need a large sdcard - and I recommend to be veryvery careful when piping it into a file - if you write it into your phone memory, it may not come up ^^
there are also several apps like "alogcat". but this does not store regularily - at least every 15 minutes. - thus after the crash there is no log from the crash. But yyou can also try that. maybe you find another app. but piping may be the solution.
btw I do not provide a howto, you have to know how to do that or must look for an app that helps you - I can't really recommend one, but there are a lot
Click to expand...
Click to collapse
thanks, I'll look into it when I have some spare time... Heh, it would be good if there was an existing/simple way configurable to write service and system logs bypassing the system buffering (or maybe to the console on the pc side), but I'm guessing I'm dreaming... I'll look into logcat then (possibly with a spare mini-sd card, since partial writes to fat32 partitions might not go well?), maybe it'll turn out to be easier to set up than you somewhat made it sound .
I like to add that I like using QtADB
when being USB-connected. THis tool also has a possibility to filter logcat per few clicks
otherwise you can also use all adb functionality like
"adb logcat" to see logs but you need to filter self
Snoopo said:
I like to add that I like using QtADB
when being USB-connected. THis tool also has a possibility to filter logcat per few clicks
otherwise you can also use all adb functionality like
"adb logcat" to see logs but you need to filter self
Click to expand...
Click to collapse
thanks for that. Don't really mind either it or normal ADB.
Heh, unfortunately I don't see anything interesting in the log...
Aside from maybe it being littered with messages of the sort:
... Kill com.gau.golauncherex.notification (pid 18332): provider com.android.providers.contacts.CallLogProvider in dying process android.process.acore
... Sending signal. PID: 18332 SIG: 9
...
21:06:33.451 Info ActivityManager 1908 Process gpc.myweb.hinet.net.TaskManager (pid 10187) has died.
21:06:33.451 Info ActivityManager 1908 Low Memory: No more background processes.
...
21:02:32.198 Warning ActivityManager 1908 Scheduling restart of crashed service com.google.android.apps.maps/com.google.googlenav.friend.android.LocationFriendService in 5000ms
where android seems to kill off apps and even services for a good measure. (or they crash?)
Memory fluctuates between about 60 and 30mb depending on the open processes, and it seems like having opera mobile opened with 5+ tabs and gmail and im+ and maybe market all at once ends up killing most of those to free up memory and maybe not die. That to me mostly means - tough luck your phone is sh!t and you should've bought a phone with more than 192mb (128mb?) ram? (or maybe - gee I wonder how I make it stop killing processes and services and what happens if it experiences a really low memory problem (<15-20mb) and can't kill processes and crash services.
Unfortunately I was unable to replicated a restart on my unit, if anyone has an idea of what to do to crash their phone let me know and I'll try it.
Generally mine reboots if I try to do too many things (market, opera, im+, etc), but now opera just closes instead of everything rebooting. (admittedly it's not an ideal outcome either, but somewhat better than a restart)
The worst I could get so far is (no idea what it means either):
21:33:54.832 Warning InputManagerService 1908 Window already focused, ignoring focus gain of: [email protected]
21:33:56.357 Error ATK 18965 Start manully kill! <---ehwhat?
21:33:56.357 Error ATK 18965 gpc.myweb.hinet.net.TaskManager
21:33:56.357 Warning ActivityManager 1908 Scheduling restart of crashed service net.jaqpot.netcounter/.service.NetCounterService in 5000ms
21:33:56.357 Error ATK 18965 net.jaqpot.netcounter
21:33:56.357 Warning ActivityManager 1908 Scheduling restart of crashed service com.android.music/.dl.DownloadManager$DownloadManagerService in 14988ms
21:33:56.357 Error ATK 18965 com.android.music
21:33:56.357 Error ATK 18965 com.android.mms
21:33:56.685 Warning GoWidgetManager 18272 invoke resume Widget err, widget id = -101
21:33:56.685 Warning InputManagerService 1908 Got RemoteException sending setActive(false) notification to pid 18965 uid 10092
21:33:59.306 Warning KeyCharacterMap 18272 No keyboard for id 0
21:33:59.306 Warning KeyCharacterMap 18272 Using default keymap: /system/usr/keychars/qwerty.kcm.bin
21:34:08.807 Error ConnectivityService 1908 Attempt to connect to WIFI failed.
21:34:08.807 Error ConnectivityService 1908 not failing over to mobile type 0 because Mobile Data Disabled
21:34:12.846 Warning AndroidMusic 19177 Need to wait for MusicPreferences to be created
21:34:13.066 Warning AndroidMusic 19177 MusicPreferences still not made, creating on UI thread
svyr said:
thanks for that. Don't really mind either it or normal ADB.
Heh, unfortunately I don't see anything interesting in the log...
Aside from maybe it being littered with messages of the sort:
... Kill com.gau.golauncherex.notification (pid 18332): provider com.android.providers.contacts.CallLogProvider in dying process android.process.acore
... Sending signal. PID: 18332 SIG: 9
...
21:06:33.451 Info ActivityManager 1908 Process gpc.myweb.hinet.net.TaskManager (pid 10187) has died.
21:06:33.451 Info ActivityManager 1908 Low Memory: No more background processes.
...
21:02:32.198 Warning ActivityManager 1908 Scheduling restart of crashed service com.google.android.apps.maps/com.google.googlenav.friend.android.LocationFriendService in 5000ms
where android seems to kill off apps and even services for a good measure. (or they crash?)
Memory fluctuates between about 60 and 30mb depending on the open processes, and it seems like having opera mobile opened with 5+ tabs and gmail and im+ and maybe market all at once ends up killing most of those to free up memory and maybe not die. That to me mostly means - tough luck your phone is sh!t and you should've bought a phone with more than 192mb ram? (or maybe - gee I wonder how I make it stop killing processes and services and what happens if it experiences a really low memory problem (<15-20mb) and can't kill processes and crash services.
Unfortunately I was unable to replicated a restart on my unit, if anyone has an idea of what to do to crash their phone let me know and I'll try it.
Generally mine reboots if I try to do too many things (market, opera, im+, etc), but now opera just closes instead of everything rebooting. (admittedly it's not an ideal outcome either, but somewhat better than a restart)
The worst I could get so far is (no idea what it means either):
21:33:54.832 Warning InputManagerService 1908 Window already focused, ignoring focus gain of: [email protected]
21:33:56.357 Error ATK 18965 Start manully kill! <---ehwhat?
21:33:56.357 Error ATK 18965 gpc.myweb.hinet.net.TaskManager
21:33:56.357 Warning ActivityManager 1908 Scheduling restart of crashed service net.jaqpot.netcounter/.service.NetCounterService in 5000ms
21:33:56.357 Error ATK 18965 net.jaqpot.netcounter
21:33:56.357 Warning ActivityManager 1908 Scheduling restart of crashed service com.android.music/.dl.DownloadManager$DownloadManagerService in 14988ms
21:33:56.357 Error ATK 18965 com.android.music
21:33:56.357 Error ATK 18965 com.android.mms
21:33:56.685 Warning GoWidgetManager 18272 invoke resume Widget err, widget id = -101
21:33:56.685 Warning InputManagerService 1908 Got RemoteException sending setActive(false) notification to pid 18965 uid 10092
21:33:59.306 Warning KeyCharacterMap 18272 No keyboard for id 0
21:33:59.306 Warning KeyCharacterMap 18272 Using default keymap: /system/usr/keychars/qwerty.kcm.bin
21:34:08.807 Error ConnectivityService 1908 Attempt to connect to WIFI failed.
21:34:08.807 Error ConnectivityService 1908 not failing over to mobile type 0 because Mobile Data Disabled
21:34:12.846 Warning AndroidMusic 19177 Need to wait for MusicPreferences to be created
21:34:13.066 Warning AndroidMusic 19177 MusicPreferences still not made, creating on UI thread
Click to expand...
Click to collapse
ps this is a bit ridiculous... Instead of rebooting, it seems after upgrading to sonybread4 rom, it now keeps killing all non-foreground processes. It's more or less a single task OS now
Related
Hey people.
ami304d is one of the process's that wastes more battery on my LG P500.
Does anyone know what that is?
from googling i think its activity manager..
It's compass deamon. I think it's a bug. There are some apps that when you open make that process eat always 5 , 6 % cpu until you restart phone.
I can't post in kernel threads else I would have warned the devs there to this case.
I'm trying to deal with it for long !
Sensors ami304d driver. Try replacing driver (maybe it's possible by replacing bin driver and replacing some lines on thunderg.rc).
ciaox said:
Sensors ami304d driver. Try replacing driver (maybe it's possible by replacing bin driver and replacing some lines on thunderg.rc).
Click to expand...
Click to collapse
Humm, and you know how to do that? XD
Thanks in advance
Vonpire said:
Humm, and you know how to do that? XD
Click to expand...
Click to collapse
Maybe post which ROM and kernel are you using? Never seen this eating any battery, are you using some crazy monitoring widget or what?
Hi dr.notor.
I have [email protected]_2.3.3_V1.2 ROM and last kernel from Franco franco.Kernel |.v1-16082011| 2.6.35.14
I see this bug(?) in various other kernels (paolo v3 v4 v5 v6 (in v6 i only found this once in other it's everyday until reboot...) )
And yes I use the only one app that I found that monitors all your system processes - OS Monitor (available on market and very nice)
Really hoping for a solution to this.
Thank you.
P.S. - If it helps it appears randomly but on some kernels the way to accurate reproduce this constant cpu usage was opening google sky map...
And even if i killed the system process (ami304d) it would be relaunched again using the same amount of cpu. After rebooting no more cpu use for this until it happens again. It can be in a simple hours on even 1 day after. The truth is that it always happen no matter what. One time even happened that i checked processes and ami304d was using 0% cpu and in morning after, without any phone use it was already eating constantly 4/5 % cpu.
In practice this takes out 1/2 fps in every game, for example in quadrant. It's really annoying to have to reboot phone every day
So I don't know if it's kernel or rom bug but I guess it's kernel.
Code:
# top | grep ami304d
PID CPU% S #THR VSS RSS PCY UID Name
2119 0% S 1 1100K 464K fg root /system/bin/ami304d
Sorry, it uses no CPU here. Google Sky Map sucking for you is not a kernel bug.
dr.notor said:
Code:
# top | grep ami304d
PID CPU% S #THR VSS RSS PCY UID Name
2119 0% S 1 1100K 464K fg root /system/bin/ami304d
Sorry, it uses no CPU here. Google Sky Map sucking for you is not a kernel bug.
Click to expand...
Click to collapse
As I said it happens everyday here, using or no using google sky maps
Sometimes I don't even use any compass/gps app and it happens anyway.
Just keep checking it, if you can after 1 or two days of use without reboot.
But I see a difference here ... my ami304d owner is compass user and not root like yours...
Maybe this is the problem? Should I change the owner of ami304d?
# top | grep ami304d
PID CPU% S #THR VSS RSS PCY UID Name
1459 4% S 1 1124K 440K fg compass /system/bin/ami304d
After reboot...
# top | grep ami304d
PID CPU% S #THR VSS RSS PCY UID Name
1460 0% S 1 1124K 448K fg compass /system/bin/ami304d
Damn
Thanks anyway.
Vonpire said:
Maybe this is the problem? Should I change the owner of ami304d?
# top | grep ami304d
PID CPU% S #THR VSS RSS PCY UID Name
1459 4% S 1 1124K 440K fg compass /system/bin/ami304d
Click to expand...
Click to collapse
Oh uh, no... do not mess with the filesystem permissions. UID of the process has nothing to do with that. Clearly something that runs with compass UID launches its own instance of this stuff and fails to terminate it.
I have found a way of reproducing this behavior and the cause of it...
Any app that uses that ami driver and is exited through an exit command (for example androsensor from market) causes this behavior. If is left running in background the process goes back to no cpu use. Please who can test this.
Thanks
Well... I can say that when I was using Paolo's LOL 1.4.2 ROM I would always see ami304d popping up on the battery history screen as one of the process that had consumed CPU, most of the times it would be the one on the top position.
Now that I've switched to Mik's CM7 6.5.7 with FK 19.1(BFS) I can still see the process under the "CPU Usage" category on Battery History, but it's consuming very little of the CPU, to give you an idea:
Right now after 6 hours after latest charge the ami304d process is being reported as:
CPU usage details for ami304d:
User time: 49s
System time: 5s
Total time: 54s
Starts: 0
I have the impression that depending on the ROM/Kernel (or apps) the ami304d might misbehave.
I've gotta say that since I moved recently to CM7 I haven't yet installed all the apps that I had with LOL 1.4.2, but I must say that one of those that I've indeed installed is Google Skymap. I haven't installed Google Maps yet (and probably I won't this time hehe)
Ok I am doing testing right now and so far I found two apps that cause this behaviour if exiting through own application "exit option". I'm going to update that as I do more testing, hopefully someone will test this and see if it happens also on other roms / kernels with new baseband (that means based on official LG gg).
Keep always terminal running the command top | grep ami304d and then watch the behaviour
- Androsensor - Exited through exit button on app - 1% cpu use forever until reboot. Exit with back button and then stopped through app manager - 0% cpu use
- Screenshot - Same as up
- Uno by gameloft - Exit through button on app - 4% cpu use forever until reboot. Exit with back button and then stopped through app manager - 0% cpu use
- South Park Mega Millionaire - Same as up
So appears it is application bug not closing the calls to ami304d when exited.
Well at least appears to me
Vonpire said:
So appears it is application bug not closing the calls to ami304d when exited.
Well at least appears to me
Click to expand...
Click to collapse
Yes, exactly. Apps need to clean up after themselves and terminate the **** they have launched on exit. If they do not, you have lingering processes running until reboot. Report to the authors of the apps.
I have new info.
I have a friend with aga rom 1.3.5 and same kernel as I and that behaviour does not apply. So I guess it's rom related...
Gonna install that aga rom and I'll check it after.
Ok.
This is getting weirder and weirder...
I wipped everything, installed aga-rom and make the same test with androsensor...
On my the bad behaviour (cpu use after exit) continues on his it don't happen, cpu goes down to 0% ??? grrrrrrrrrrrrr
The only difference between mine and his, is sd card...
So I can only guess two things...
ami304 firmware...
or
sd card (?) does not make much sense to me...
I am really f***** with this!
Any suggestion??? Please?
That ami **** is a sensor like ciaox said. Try not to install apps that use that **** and you won't have that problem as I never ever had.
That I get it, what I don't get is why that happen with my lg p500 and not with my friend one? Where's the logic in that?
Thanks anyway FF
NEW INFO : I finally found one difference between my phone and my friend one.
Mine was bought on optimus PT and unlocked(any gsm) by optimus one week later
My friend was bought on vodafone PT
With the application to download official LG firmware directly from LG servers i puth both IMEIS - http://forum.xda-developers.com/showthread.php?t=1073827 HERE
MY IMEI - 35404304173***
MY FRIEND IMEI - 35404300175***
Mine returns - V10R_00.kdz
His returns - V20G_00.kdz
So I have to possible reasons for this :
Vodafone PT already updated it and gave away V20G_00.kdz and ****ty Optimus PT is still putting all those crap they putted on their official froyo rom and is still delaying the new release. I guess this is the most probable explanation, Time will tell.
OR
Maybe are the two phones using different baseband? Anyone thinks is a probability of this happening since my phone is older than his?
Can that ami304d **** on my phone happen because I flashed the baseband for V20G and MAYBE my phone had previous baseband different from his?
Maybe silly questions (I admit) but it gives a little to think about.
P.S. - dr.notor you can call me noob if you want . Peace Bro . Just give me your opinion on it. Maybe the cause of many weird things? Or maybe just nothing and we'll never know why the different behavior on two apparently equal phones... That's the most probable.
Baseband has nothing to do with the ****ty sensors. It deals with GSM/2G/3G.
Downloaded the new Google Maps update praying it would fix the FC's no dice. Are all Cyanogen ROM users having this problem? Having one more problem, my phone will notify me of E-mail; but when I go to my email it isn't showing my latest email. I have to refresh it to have it show up. Not Gmail but my Comcast account? Any help would be most appreciated.
Thanks
Just FYI to anyone with this same problem, I just rooted my eris for the first time 2 days ago. Maps nav was freezing on my non-rooted 2.1 in the same exact way. Something seems to be wrong with maps in general...but I'm not sure if it's just with the eris. But I do know that maps worked within the 3-4 previous updates. Can anyone provide a way to "downgrade" maps to an update that is a little older? I think this might provide everyone with a temp solution until they provide us with an update that works with the eris...just an idea
i think i read somewhere that some people tried to downgrade maps but it still FC'd on them...
Macrodroid just posted that he had success with downgrading his maps, check his EverVolv or Macrom thread.
Sent from my MacRom MR7 using Tapatalk
The only issue I've had is when i received a call during navigation. While it was rerouting, I received a FC. Starting it again and didn't have any issues.
Downloaded the apk that Mac posted last night. I drive 50 miles to work every morning. It force closed and rebooted my phone after 20 minutes. This occurs while driving down the interstate (not while making lots of turns). Going on a trip soon, might just have to download Zach's xtr rom. I've used it in the past month and navigation worked fine.
If anybody finds a way to deterministically crash the Eris using Maps/Nav, let us know; it would be very helpful for testing purposes. Note that you don't need to be driving around for a crash to occur (although it is conceivable that will help cause the bug to occur) - the Nav app will cause a crash sometimes with your Eris just sitting motionless on a desk.
I've observed a couple of full Android restarts so far (phone connected to the PC with Nav running and "logcat" running), and so far the things I've noticed are:
- the problem is hard to reproduce. Sometimes a crash will happen in 10 minutes, sometimes in 1 hour... sometimes not after several hours. (This is the the problem with "I tried Nav for 30 minutes and everything seemed fine" reports - it isn't easy to prove that a specific fix has actually worked, 'cuz it might be hours before the bug rears it's ugly head).
- All the cases where I've seen an (Android) crash so far (v5713/gapps 20110613), I saw a SIGSEGV (null pointer fault) of the "system_server" process - the same "null string passed to strlen() via libdvm.so" error that has been previously noted elsewhere (e.g. in Tazz' thread and some time ago in other CM7 ROMs (Hero CDMA) ). This obviously will cause a full Android layer restart, but strictly speaking is not exactly a Maps/Nav issue... but probably something about the way that the new Maps/Nav behaves that makes the occurrence of this bug favorable.
I'm still looking at this, but not making much progress. The only thing that I (seem) to have noticed is that turning on checkJNI in the zygote causes Nav to hang (ANR) so that Android offers a FC to the user. I suppose this could be a completely separate bug - the main thread seems to hang waiting for something in the GL.
e.g.
Code:
adb shell stop
adb shell setprop dalvik.vm.checkjni true
adb shell start
... then do your testing.
My mothers Eris was experiencing a similar issue as was my TB. a full wipe did the trick for me using the latest available CM versions and gapps for both phones. No issues thus far... fingers crossed.
Rick
bftb0,
Back when I was trying to figure out the Maps/Nav issues, I had requested people get the kernel log of a crash. I posted here what was interesting to me from someone that had posted one and then later decided to look at the source code and follow the routines mentioned. I remember looking it over but don't think I ever posted what I'd found or was thinking and can't find any notes about it right now. Might look into that again to see if the source holds any clues.
MongooseHelix said:
bftb0,
Back when I was trying to figure out the Maps/Nav issues, I had requested people get the kernel log of a crash. I posted here what was interesting to me from someone that had posted one and then later decided to look at the source code and follow the routines mentioned. I remember looking it over but don't think I ever posted what I'd found or was thinking and can't find any notes about it right now. Might look into that again to see if the source holds any clues.
Click to expand...
Click to collapse
I looked at the link you provided - if you thought that somehow the kernel module for WiFi was a source of trouble, you could certainly just move /system/lib/modules/wlan.ko out of the modules folder and reboot (for testing purposes - obviously in the long run you want to have WiFi capability).
My own testing is moving me in a different direction, though. So far, all the Android crashes that I have seen so far have been segfaults of the "system_server" process. I just watched one a couple of minutes ago, using both logcat and strace simultaneously.
The stack trace at the segfault of system_server in the logcat (if it is actually to be believed) looks something like
Code:
strlen() [libc.so] <- segfault here
??? [libdvm.so]
??? [libdvm.so]
??? [libdvm.so]
dvmLockObject() [libdvm.so]
??? [libdvm.so]
dvmMterpStd() [libdvm.so]
dvmInterpret() [libdvm.so]
dvmCallMethodV() [libdvm.so]
libdvm is the Dalvik VM parser - which you would think/hope would be extremely robust code (and thus makes me wonder if the stack backtrace above the strlen() call is just nonsense - the debugger is not guaranteed to get it correct).
here's the last couple of lines from an strace of system_server as it was crashing:
Code:
11:51:40 sched_setscheduler(157, SCHED_OTHER, { 0 }) = 0
11:51:40 ioctl(10, 0xc0186201, 0xbedce340) = 0
11:51:48 sched_setscheduler(157, SCHED_OTHER, { 0 }) = 0
11:51:48 getpriority(PRIO_PROCESS, 157) = 20
11:51:48 recv(606568, 0x81, 1, MSG_CTRUNC|MSG_EOR|MSG_WAITALL|MSG_ERRQUEUE|MSG_DONTWAIT|MSG_FIN|0xfffb0000) = 1
11:51:48 sched_setscheduler(157, SCHED_OTHER, { 0 }) = 0
11:51:48 ioctl(10, 0xc0186201 <unfinished ...>
11:52:04 +++ killed by SIGSEGV +++
Ugh... not very informative, frankly.
This might be a fairly difficult thing to pin down - after a little bit of testing, I've noticed that it is easier to cause this particular type of crash with a phone experiencing a decent (but reasonable) load than a lightly loaded phone - as if it is more likely to occur during a low resource condition, or is due to a timing/timeout issue. I have some difficulty getting it to occur on a "stripped" GSB 3.7 (Odex) ROM, where I removed almost everything non-essential, and didn't load any apps; but on my GSB 3.7 (Odex) "daily driver" ROM, it happens more frequently, and especially if I try and make the phone jump through other hoops while Maps/Nav is running.
... still looking...
bftb0
[ Edit ] 10 minutes after I made this post I flashed my "stripped down" GSB v3.7 Odex ROM, and set it up to watch it with Nav running. It crashed about 24 minutes later. I guess I should recant what I said above about load dependencies.
Just for kicks I reinstalled 2.1 (ota version) it didn't force close but the map quit updating my location. I had the latest maps installed and once again it crashed/stopped responding after ~20 minutes.
Just for kicks I restored a fairly old version of maps - v5127 a.k.a. "5.1.0" to my GSB v3.7 Odex ROM.
It crashed my phone (an Android restart, rather than a kernel reboot) within 10 minutes of starting up Nav.
Because all of these "crashes" seem to be in the system_server process, rather than the Maps/Nav app, I'm not convinced that the problems are due to the Maps app - we certainly were not experiencing restarts on older versions of GSB way back when maps 5.1.0 came on the scene. (Although we were experiencing the "GPS signal lost" after 20 minutes bug)
I don't know what to think at this time; maybe there is more than one bug involved. Perhaps I should try the non-odexed GSB version to see if it behaves any differently.
bftb0
I went driving around yesterday and was using navigation and had it crap out a few times. One time it said that acore had crashed. Two other times it just locked up for about 30 seconds and then I saw the cyanogen animation. Sort of like a partial reboot because it was really fast.
Sent from my GSB v3.6 ODEXed using XDA App
bftb0 said:
Because all of these "crashes" seem to be in the system_server process, rather than the Maps/Nav app, I'm not convinced that the problems are due to the Maps app ...
bftb0
Click to expand...
Click to collapse
I see what you're getting at but if the crashes are not Maps related why would non-CM7 phones also freeze up? Since this is happening on xtr and stock ROMs also is it possible that something in Maps is causing the system_server process to crash?
PieceKeepr said:
I see what you're getting at but if the crashes are not Maps related why would non-CM7 phones also freeze up? Since this is happening on xtr and stock ROMs also is it possible that something in Maps is causing the system_server process to crash?
Click to expand...
Click to collapse
My best guess is that there is more than one bug involved. Personally, I've observed three different behaviors, from most frequent to least frequent:
1- Android layer restart (always a system_server segmentation fault)
2- Full reboot (kernel restart)
3- Maps ANR (App Not Responding)
#1 is absolutely, positively a bug in the system_server code; plainly stated, native code should never segfault. What is odd about this is that having Maps running seems to cause this fault to occur - it doesn't seem to happen when Maps/Nav is not running. What is extremely challenging about diagnosing this is that (if the debuggerd stack traces are to be believed) it appears that it is the Dalvik VM code itself (libdvm.so) that makes the fatal call into libc.so - a simple strlen() call that gets a null pointer. That seems to imply that figuring this out requires understanding:
- how an unrelated app (Maps/Nav) is affecting java code of the system_server
- how the Dalvik compiler/optimizer/interpreter could possibly have a bug
Note that (again, if the debuggerd stack traces of the system_server crash appearing in the logcat are to be believed) if there really is a Dalvik VM bug involved, I suppose that also means that occurence of the bug could be dependent on:
- JIT on vs. off
- Optimizer settings (and odex'ed vs. non-odex'ed ROMs)
Perhaps this explains some of the variability in the various reports; most of my experiences with the bug(s) have been with the GSB 3.7 Odex ROM (JIT on, no compcache or dithering, various VM heap sizes).
I full-wipe installed GSB 3.7 non-odexed yesterday, and am going to do some more testing.
As for crash cases #2 and #3 - I haven't experienced enough of them to say anything meaningful.
bftb0
PS Over the weekend, I drove about 3 hours on both Sat and Sun, and I didn't want my phone blowing up on me, so I rolled back my phone to celb 4.1 (Froyo) and used Nav continously. The version of Maps in that celb backup was 5127 (aka "5.1.0"). I experienced the "GPS Signal Lost after 20 minutes" bug - which I expected - but using GPS status would allow Nav to re-acquire signal. But, no other trouble. The reason that I mention this is that this same *very old* version of Maps (5127) can readily cause the system_server process to crash in GSB v3.7 Odex. This kind of data is what leads me to believe that (at least for the "Android soft-restart" bug expression) while Maps/Nav can *cause the problem to occur*, this particular bug actually is not in the Maps app itself.
Anyway, that's a few of my observations; no solutions unfortunately.
More testing to come.
I have experienced all of those, but not in that order. Rearranged by frequency for me they would be ...
3- Maps ANR (App Not Responding)
1- Android layer restart
2- Full reboot (kernel restart)
I am on GSB 3.6 ODEXed (3.7 was sluggish for me and I was getting odd and random app force closes so I rolled back).
Settings:
CPU - Ondemand, 710/245
Compcache - disabled
JIT - off
Surface dithering - off
Purging of assets - off
Lock home in memory - off
VM heap size - 32mb (default)
V6 Supercharger - multitasking or sometimes Balanced 1 with launcher HTK
By far the most common problem for me was the Maps ANR. I did get the Full reboot, and several Android layer restarts before I started playing with settings. Unfortunately I don't remember what I started with and can't say what all I did. I was running Maps 3.6.2 (I'm pretty sure) at the time and I kept getting the Maps ANR. I found a copy of Maps 5.5.0 I had forgot about in MyBackup Pro so I wiped Maps data, then uninstalled before restoring just the Maps 5.5.0 apk.
Since then I have only had one problem, which happened two days ago. I had been using Navigation for about an hour and a half, maybe approaching two hours, by the time I reached my third destination. It showed me I had reached my destination but it froze. None of the app buttons were responsive so I tried the phone soft buttons and found they were unresponsive as well. Then the phone did an Android layer restart. At the time the phone was VERY HOT to the point of being uncomfortable to hold in your hand. I have never seen my phone that hot before. It was plugged in at the time because the battery had gotten low so I was charging it.
My wife's Eris is running xtrSense 5.0.1 and I took it out and tried it a while back. It never did a full reboot or an Android layer restart but Maps ANR occurred within five minutes. I tried several times and got the same result each time.
Hopefully some others who have experienced problems will see this and chime in. Maybe if we can narrow down specific occurrences with stock and other ROMs it will help decipher this. Thanks bftb0 for breaking this down into categories and for your work on the problem. If there is any data I can capture and provide let me know.
All -
I've been testing latest map version on a number of roms as of late and offer a few observations:
I have consistently experienced Android layer restart and full reboot on GSB roms, stock settings, versions 3.4 through current. I experienced a reboot on Condemned soul's version 14 rom only once. I have not ever experienced a navigation reboot on OMGB 1.1, Evervolv,3, or 666th Sense (March OTA based rom).
The only ROM I have run that has not resulted in a map ANR is OMGB 1.1, but GPS signal is lost within a minute on that rom. Navigation continues to wait for a signal but does not force close.
Condemned soul's v14, Evervolv 3, and 666th Sense all display the same behavior: navigation runs for between 2-10 minutes and map display freezes while voice navigation continues running as a separate service. Eventually a FC is offered and navigation can be easily resumed from the notification bar. It will FC within another 10-20 minutes.
I've been doing some testing and trying a few tweaks - all dead ends and none of them have worked, but I'll repeat them here in case they are of any use to this group:
First, I tried flashing old versions of gapps to roll back the com.google.android.maps.jar file to see if there was anything there affecting navigation. At first I thought it was working differently, but alas the old jar (if they are actually even different) files really behaved the same -- they locked up the navigation moving map while partially allowing the navigation voice(s) to continue.
After repeated testing, It *seems* that the moving map is hanging up for me in the SAME PLACES. Now this is all very subjective since I cannot pay all that much attention while driving, but when I leave my office for home it seems that the maps hangs at the first right turn, 1/2 mile or 2 minutes away. If I restart it, it will continue for another 10 minutes or so until after a major highway merge.
So, I began to notice the dual-voice navigation some others have mentioned and deduced that one voice is TTS and one is google's backup non-TTS navigation sounds. I suspected, perhaps, that TTS might be crashing or being force closed by the system. A little routing around and I found that if you uninstall TTS that navigation simply will not load but will FC immediately. I also found that you can disable TTS by removing/renaming the libttspico.so file. This way, you can actually force the second navigation voice - its rather pleasant but does not pronounce street names, just says "turn left" etc.
This did not fix the problem either. But it did allow me to rule out that the phone was temporarily losing GPS signal leading to the FC. Without TTS, navigation alerts you that GPS signal was lost with a chime sound. Maps was not hanging on a lost GPS signal. since voice directions continue despite visual map hanging.
So this leads me to my next observation. Without the distracting TTS voice I notice that the maps seems to hang precisely at a point where I am supposed to be alerted to an upcoming change. For instance, after making my first right leaving the office, it hangs when (1) I turn right forcing the map to pan and draw the route for the next leg AND SIMULTANEOUSLY (2) when the GPS wants to tell me the next direction "In a half mile, turn right on to the ramp"
I also thought that there may be a memory problem - like GB is trying to kill one of the Navigation related processes. As far as I can tell, navigation requires that the navigation map, a separate navigation voice service, and PICO TTS all be running at the same time on top of a launcher, maps, email, and other services. I tried tweaking V6 supercharger to gaming settings with no luck.
klobkelosh said:
...First, I tried flashing old versions of gapps to roll back the com.google.android.maps.jar file to see if there was anything there affecting navigation. At first I thought it was working differently, but alas the old jar (if they are actually even different) files really behaved the same -- they locked up the navigation moving map while partially allowing the navigation voice(s) to continue...
Click to expand...
Click to collapse
If the jar files are the same, they should have the same md5sum so it might be worthwhile to compare them and see if each jar has matching checksums.
*POSSIBLE* Navigation Fix
I may have found a fix. I was able to navigate on my daily commute without a FC or reboot (that's not happened in a while). BUT I need your help in testing it more to be sure it is not a fluke. I'll also be testing over coming days
The attached file is NOT a flashable zip. Extract the com.google.android.maps.jar file and push it to /system/framework replacing the gapps gb version. If you use root explorer/es file manager be sure to set permissions to rwrr.
This jar version is from the May 2011 MDPI gapps package. It is nearly double the filesize of the gb version so clearly not the usual framework.
Hope this works in the long run....
I'm driving from Paducah, KY to Oscoda, MI. Should be a good test, I hope this works
All, I'm currently still having issues where the phone is awake quite a lot of the time when screen is off (Stock 4.3.91 ATT). Logcat constantly is showing e/netlinkevent (UDEV_LOG not found) , and e/netlinklistener ignoring non-kernal netlink multicast message constantly popping up. A few people have asked regarding this before but no answers have been submitted yet - are there ANY rom's (GB) out there that do not have this issue?
Thanks for your time.
alien ROM, never seen it before or its way down the list
note I have NOT signed into motoblur.
you can confirm whats going on by using betterbatterymanager (on XDA not market), it will give you stats of what proc is taking up how much wakelock
Thanks - I do use Better battery Stats also and shows alarm manager as being main culprit. Any chance I could get you to look at the logcat for alien confirm that you dont have the netlistener in red popping up every 1-10 seconds?
don't see it for 30 seconds
i used the filter 'netlinkevent' (no quotation marks) nothing as well.
I bet you its some motoblur thing
alarmmanager is a catch-all service that other programs can use as a timer, its not just for alarms, so it could be anything you've installed that wants to auto update or check data
ok have tried the following roms: alien v3 (Stock no theme, stock kernal) This still had the same netlink messages. I did try aura's latest rom (blurred version) - this was also the same. However when I ran the deblurred version one of the 2 messages disappeared - I still have the e/netlinkevent coming up, but the e/netlinklistener was gone. All of these roms are fresh installs after wipes and the only apps installed/configured are android system info (to see the log). Any that still have blur on have not had the blur account signed into...
So any ideas? Whathe best rom/kernal configuration for battery life/performance outthere.
I'm just getting started on learning how to develop Android applications and noticed the same thing. I setup my IDE while the phone was running 2.2, and I don't remember seeing anything like this... but I can't say for certain. I'm runing the recently released ATT / Moto Android 2.3.4 (4.5.91.MB860.ATT.en.us). The messages never stop... have to believe it is affecting battery life.
See the image for a SS of LogCat. I killed every running application / service I could to no avail.
spiritofsaron.org/jason/udev_log_logcat.png
i think its because we are using android system info to look at the log - if you use alogcat to view the log in real time - no messages - annoying as i have spent DAYS flashing roms trying to get one without it as opposed to changing my log program...
benchallenger said:
All, I'm currently still having issues where the phone is awake quite a lot of the time when screen is off (Stock 4.3.91 ATT). Logcat constantly is showing e/netlinkevent (UDEV_LOG not found) , and e/netlinklistener ignoring non-kernal netlink multicast message constantly popping up. A few people have asked regarding this before but no answers have been submitted yet - are there ANY rom's (GB) out there that do not have this issue?
Thanks for your time.
Click to expand...
Click to collapse
Came accross http://forum.xda-developers.com/showthread.php?t=1200536 which covers the same issue.
Runs nonstop VIA adb logcat on alien 3 here.
Sent from my Inspire 4G
In short: send a text message, and the whole OpenGL system (including the live wallpaper) freezes and cannot be restored until reboot.
In long: rooted Optimus One, using the OC Gingerbread Kernel and dr.notor's ROM posted a while ago. About once a day it so happens that a game or live wallpaper (and even the default Gallery, which I since froze with TB) causes some sort of bug that freezes the whole OpenGL graphics system. As a result, no games, LWP or anything similar work until after a reboot. It does not seem to be a RAM issue, as it even happened with >150 MB free RAM. Until now I can only assume it is because of an exception named EGL_BAD_ALLOC, which (I noticed) caused the same effect on HTC devices. Logcat is not helpful at all, apart from the following warning, spat out whenever trying to open something using OGL after the freeze:
W/SharedBufferStack (xxxx): waitForCondition(LockCondition) timed out (identity=yy, status=0). CPU may be pegged, trying again.
[where x and y are numbers depending on the app]
Now, this is one thing. But recently I noticed sending a mere text message or getting a delivery report for one triggers the OpenGL freeze!
So what gives?! Please help, I feel like throwing the phone at the nearest wall each time it happens.
Bump, doesn't anyone know?
Note: this is another issue reporting thread. In case of duplicate or forum location problem, consider (re)moving my post.
Hello,
Months ago I noticed a weird issue in the internal browsing system of the SM-G361F
When I browse to a website using the WebGL integrated API (for exemple: https://get.webgl.org/ ) the displayed shape gets glitchy. Nothing really strange first, just some random blink or short frame flashbacks. But after a time (generally above 30 seconds) the shape become more and more glitchy until the kiss of death: the whole phone process freezes, as nothing respond anymore, then the screen gets shady on some parts and bright on the other, until a kind of bar come across the screen and the phone make a complete reboot without any transition.
I already experienced such thing a year ago, but that was due to a bad root flash that triggered the freeze on any root access request.
The other strange thing is that I discovered it when I ran a web code displaying an "holographic" shape: however, the code worked fine the first times, and I did it long ago; so would this be due to a bad firmware flash or a system harm?
If you own like me a SM-G361F device and are not easily scared (this issue normally doesn't harm the device, it will just freeze and reboot) you can test it by opening the link to the WebGL official website.
Sharing experience about this potential issue would be appreciated.
I also had this issue. I experienced severe jitter in videos, and gifs in the web browser. It seemed to occur randomly, and would sometimes stop after a little while.
I didn't experience the device crashes though, but fixed the video by downgrading "android webview"
Sorry for late reply.
Atronid said:
Note: this is another issue reporting thread. In case of duplicate or forum location problem, consider (re)moving my post.
Hello,
Months ago I noticed a weird issue in the internal browsing system of the SM-G361F
When I browse to a website using the WebGL integrated API (for exemple: https://get.webgl.org/ ) the displayed shape gets glitchy. Nothing really strange first, just some random blink or short frame flashbacks. But after a time (generally above 30 seconds) the shape become more and more glitchy until the kiss of death: the whole phone process freezes, as nothing respond anymore, then the screen gets shady on some parts and bright on the other, until a kind of bar come across the screen and the phone make a complete reboot without any transition.
I already experienced such thing a year ago, but that was due to a bad root flash that triggered the freeze on any root access request.
The other strange thing is that I discovered it when I ran a web code displaying an "holographic" shape: however, the code worked fine the first times, and I did it long ago; so would this be due to a bad firmware flash or a system harm?
If you own like me a SM-G361F device and are not easily scared (this issue normally doesn't harm the device, it will just freeze and reboot) you can test it by opening the link to the WebGL official website.
Sharing experience about this potential issue would be appreciated.
Click to expand...
Click to collapse
Hello mate!
I must tell you that this happens not only on your device but on SM-G360H Varient too.
In the last 2-3 days i figured it also happens due to high CPU usage and the Kernel goes into panic mode.
Try disabling Kernel panic from apps like LSpeed and see if it helps!
Thanks!
SnapDrag910 said:
Hello mate!
I must tell you that this happens not only on your device but on SM-G360H Varient too.
In the last 2-3 days i figured it also happens due to high CPU usage and the Kernel goes into panic mode.
Try disabling Kernel panic from apps like LSpeed and see if it helps!
Thanks!
Click to expand...
Click to collapse
Thanks for your advise ^^
Atronid said:
Thanks for your advise ^^
Click to expand...
Click to collapse
1 more.
If you are on a custom ROM, then remove the AOSP webview for root -> system -> apps -> Webview. And then install Google webview from the playstore and convert to system app(optional).
It may fix the random crashes and freezes. It does freeze but no more crashes