Develop Bugs

Random Restart

So far today, my Evo has reset itself about 4 times. That is within the past hour and a half. I've had it since Monday and had no other issues with it doing this until today. The only app that was added in the past 24hrs was the Wireless Tether for Root app. I don't know what or why this is happening. I've just uninstalled Unrevoked, Superuser Permissions, the Overclock Widget, and the Wireless Tether to see if that is causing the issues. Anyone else have anything similar to this happening?
Also, I changed the "always on mobile data" setting to off yesterday. That increased my battery life dramatically. I was able to leave the phone on for a solid 11hrs with it still having 60% charge left. Then today, before I changed any settings at all, unplugging the phone from the charger for about 2hrs has resulted me in being down to 45% battery. Could mobile data always on being off cause the rebooting issue?

Same thing was happening to me when I unchecked that. Checked it back and all rebooting issues went away.

admorris said:
Same thing was happening to me when I unchecked that. Checked it back and all rebooting issues went away.
Click to expand...
Click to collapse
Since I posted that message I had two more reboots. Just ticked always on mobile data back on and am waiting to see if that stops it...
EDIT: No more reboots since reenabling mobile data always on...weird

I've had the always on data feature turned off since day one to conserve battery life and i had not experienced the random shut offs until yesterday. Since yesterday however my phone has restarted itself no less than 20 times. Several times while I was sleeping so this is defiantly a real problem but I dont think its related to settings. ill be contacting HTC tonight

I have had always data off, ticked it on this morn. And started getting the reset issue...
-------------------------------------
Sent via the XDA Tapatalk App

Random restarts are often indicative of the battery not sitting in properly.
Remove the battery. Scratch up the contacts. Insert back firmly...

I am also having this same issue. I turned my phone off this morning because i wouldn't be using it and then i turned it back on in the afternoon and then my phone just started randomly restarting itself. There is no rhyme or reason to it. It has just been happening all by itself. It has probably happened 10 times in the last 4.5 hours.
I took the battery out for a minute and put it back in to see if it will stop the issue, but i'll have to wait and see. However, when i did turn the phone back on i got a weird pop-up message on the main screen that said something to the effect of, "Operational failure, please use su command." Then it faded away. Anyone know what that means?

As mentioned above, turning always-on mobile back on, took care of my restart issue.

heed316 said:
So far today, my Evo has reset itself about 4 times. That is within the past hour and a half. I've had it since Monday and had no other issues with it doing this until today. The only app that was added in the past 24hrs was the Wireless Tether for Root app. I don't know what or why this is happening. I've just uninstalled Unrevoked, Superuser Permissions, the Overclock Widget, and the Wireless Tether to see if that is causing the issues. Anyone else have anything similar to this happening?
Also, I changed the "always on mobile data" setting to off yesterday. That increased my battery life dramatically. I was able to leave the phone on for a solid 11hrs with it still having 60% charge left. Then today, before I changed any settings at all, unplugging the phone from the charger for about 2hrs has resulted me in being down to 45% battery. Could mobile data always on being off cause the rebooting issue?
Click to expand...
Click to collapse
I'm getting the same issue. At first i thought it was ATK, so i uninstalled that. Then I though it was lookout, so I disabled that. But it still keeps happening. I have mobile data off too, but for days, and it hasn't affected it one way or the other.
The odd thing is, I was running xiiLive Lite last night streaming the radio all night, and my phone stayed up the whole time, while plugged in (at least 8 hours).
I don't know what the deal is, but my phone goes about 24-48 hours without a spontaneous reboot, and then it will start doing it 4-6 times a day. Anyone have a good logging tool would be nice, as I'm somewhat new to Android.
Thanks!
Tigger

tigger2u said:
I'm getting the same issue. At first i thought it was ATK, so i uninstalled that. Then I though it was lookout, so I disabled that. But it still keeps happening. I have mobile data off too, but for days, and it hasn't affected it one way or the other.
The odd thing is, I was running xiiLive Lite last night streaming the radio all night, and my phone stayed up the whole time, while plugged in (at least 8 hours).
I don't know what the deal is, but my phone goes about 24-48 hours without a spontaneous reboot, and then it will start doing it 4-6 times a day. Anyone have a good logging tool would be nice, as I'm somewhat new to Android.
Thanks!
Tigger
Click to expand...
Click to collapse
I had mobile data off for a few days with no reset issues. Then I installed a few apps from the market (not the ones you mentioned) and then the resets started. I uninstalled the newest apps but the resets kept happening. Then I turned mobile data back on and no more resets in the last 24 hours.

my evo is randomly rebooting and I never modified the settings that some of you are talking about. My also gives me random issues where when i try to open an app it will open for a split second and close? I am also having my phone lock up on me several times a day and i have to pull the battery to reboot it! I took it back to the sprint store and they insisted on reloading the software on the phone and it made no difference.... does anyone have any suggestions or similar issues?

rooder said:
my evo is randomly rebooting and I never modified the settings that some of you are talking about. My also gives me random issues where when i try to open an app it will open for a split second and close? I am also having my phone lock up on me several times a day and i have to pull the battery to reboot it! I took it back to the sprint store and they insisted on reloading the software on the phone and it made no difference.... does anyone have any suggestions or similar issues?
Click to expand...
Click to collapse
I had the apps closing after a split sec too but I found out that it was for apps that didn't play nice with the snapdragon cpu; like the Gameloft game Nova and a few of their other titles.

for me its stock apps like the navigator, video player etc. I am thinking i might have a defective unit.

rooder said:
for me its stock apps like the navigator, video player etc. I am thinking i might have a defective unit.
Click to expand...
Click to collapse
Yup! That does sound strange! Did you root your phone? I'm rooted and all the stock apps that I've tried, seem to open and work fine.

nope! not rooted, 100% how it was out of the box. Luckily my pre was still active so i video taped it freezing up and stuff so im going to show the tech at the sprint store so hopefully they can order my replacement.

I also have a fully stock phone, some apps installed, but none recently, and yesterday it rebooted itself, twice more today.
I haven't changed the settings mentioned earlier, and haven't done anything I can think of that would cause the rebooting.
I am also having issues where I can't get an IP address on my wireless network, but I'm not sure it's related. I just noticed these 2 problems in the last 2 days, and it's the only thing I can think of that's out of the ordinary from the weeks prior to this happening.
I think I'll take it to Sprint tomorrow and see what they have to say.

Keep us updated on what happens. It seems to take a day or two for symptoms to start, but when they do it goes crazy rebooting!
...more discussion on this issue has been going on here too: http://forum.xda-developers.com/showthread.php?t=702379

I'm not a professional android user and don't know much about it yet, but mine's rebooted a few times as well. I haven't rooted my phone but the ONE thing that seemed to have resolved the continuing issue is doing a hard reboot:
Menu > Settings > Privacy > Factory data reset
It's been 4 days and hasn't rebooted since.
EDIT: It's been 6 days now and still no reboots.

Angry Apps Eating my RAM!
I think what everyone is missing here that maybe the root of the problem is low memory.
I'm not talking about storage on the SD card. I"m talking about the memory the OS has to run.
I've fought long and hard with this low memory problem seeing as I have owned a g1 for almost 2 years.
THERE IS NO REASON THE EVO SHOULD EVER GET DOWN TO UNDER 30MB OF SYSTEM RAM!
I equate this issue to the same issue many people had with Windows computers and applications that start up in the system tray! We don't need most apps to run in the back ground on start up just in case I want to use it. The few seconds of time it shaves off of starting up the app is not worth the slower OS boot up (applies to Windows mainly) or the major slow downs they cause the OS's to have.
I don't need Sprint TV running on boot!
When I used a clean slate scene I still have all of these same issues. Random reboots, slow OS and apps, ect.
I have no idea why Android would allow that much RAM to be used for background apps. I don't understand why we have no way to see what programs run on boot unless using a 3rd party app.
Most apps are so crappy that they run in the background all the time and have no way to toggle if they run on boot and I'm not talking about apps that modify something all the time I"m talking about apps that ONLY need to be running once you open them. An example would be Swipe, I understand the need for that app to run on boot. It modifies the OS keyboard and would need to be running in order to work correctly when ever you enter any text field that pops up the keyboard for input.
An example of programs that don't need to be running on boot or should at least give you an option to toggle boot start up are; Sprint Navigation, Sprint Updater (No idea what this is for), Updater (Android?), Sprint Zone, doubletwist, SprintTV Widget (I'm on the clean slate profile with NO Widgets), VoiceMail (I use Google Voice, is this needed?), Sprint Football Live (It's not even Football season!), MP3 Store (I have yet to use on the EVO but is running just in case, thx), as well as many others.
I have 35 apps running in the back ground! WTF? Thanks ****ty app devs and bloatware Sprint!
Have fun try to find options for each app and figuring out each service to know what it's tied to so that you can have a phone that it powerful and run smoothly.
It really shouldn't be this hard or as much of a pain...

Reeves360 said:
I think what everyone is missing here that maybe the root of the problem is low memory.
I'm not talking about storage on the SD card. I"m talking about the memory the OS has to run.
I've fought long and hard with this low memory problem seeing as I have owned a g1 for almost 2 years.
THERE IS NO REASON THE EVO SHOULD EVER GET DOWN TO UNDER 30MB OF SYSTEM RAM!
I equate this issue to the same issue many people had with Windows computers and applications that start up in the system tray! We don't need most apps to run in the back ground on start up just in case I want to use it. The few seconds of time it shaves off of starting up the app is not worth the slower OS boot up (applies to Windows mainly) or the major slow downs they cause the OS's to have.
I don't need Sprint TV running on boot!
When I used a clean slate scene I still have all of these same issues. Random reboots, slow OS and apps, ect.
I have no idea why Android would allow that much RAM to be used for background apps. I don't understand why we have no way to see what programs run on boot unless using a 3rd party app.
Most apps are so crappy that they run in the background all the time and have no way to toggle if they run on boot and I'm not talking about apps that modify something all the time I"m talking about apps that ONLY need to be running once you open them. An example would be Swipe, I understand the need for that app to run on boot. It modifies the OS keyboard and would need to be running in order to work correctly when ever you enter any text field that pops up the keyboard for input.
An example of programs that don't need to be running on boot or should at least give you an option to toggle boot start up are; Sprint Navigation, Sprint Updater (No idea what this is for), Updater (Android?), Sprint Zone, doubletwist, SprintTV Widget (I'm on the clean slate profile with NO Widgets), VoiceMail (I use Google Voice, is this needed?), Sprint Football Live (It's not even Football season!), MP3 Store (I have yet to use on the EVO but is running just in case, thx), as well as many others.
I have 35 apps running in the back ground! WTF? Thanks ****ty app devs and bloatware Sprint!
Have fun try to find options for each app and figuring out each service to know what it's tied to so that you can have a phone that it powerful and run smoothly.
It really shouldn't be this hard or as much of a pain...
Click to expand...
Click to collapse
This is where I am so lost with Android. I read many blogs saying Android does not need a task killer and using one will only make your system slow down. Well I tried one anyway because it's in my Windows Mobile nature to do so (old habits....). I noticed that I too had 35 or so apps running in the background and I thought that doesn't sound good, I wanna kill them all. But then what Android pros keep telling me is to let them be and that the OS will kill them as needed. But from what you're saying, it sounds like the OS doesn't always do a good enough job. So my confusion and learning process of Android continues......

[Q] Sense 2.1/3.0 Rom common issues

So I've tried out MikG 2.2, Synergy nightlies and 6/27 RC1, Kingdom Revolution and Synergy-Kingdom and I seem to have the same two prevalent issues I could use some help with.
1.) I use the desk clock feature of my EVO in night mode. Problem is all these roms share a common problem, that being that for some reason the World Clock service will crash and take it out of night mode. Also not sure why but with standard EVO sense roms it immediately goes to the clock whereas with the sense 2.1/3.0 roms the screen dims but doesn't go to the night clock for somewhere around 10 minutes like on an aosp rom.
2.) I use google nav heavily. I make about 10-15 stops a day for work and need it always running. Problem is with sense 2.1/3.0 roms that for some reason I haven't been able to identify, the screen will dim randomly and ultimately shut off during navigation sessions. I have tried setting the screen to always on while charging, messed around with spare parts and set the brightness to manual and auto, disabled power saving features on the phone, all to no avail. The phone is constantly plugged in and mounted on my dash, so its always charging.
I keep no personal info on my phone, so when I wipe it for a rom, EVERYTHING is wiped. SDCard, Rotation and battery stats, data, cache, system, boot, everything. I do that once over, then mount it, format the sdcard with my computer, then copy vr_superwipe and flash that to wipe it all again, then remount, format again on computer, unmount and go through the wipe list again, then remount and copy over whatever rom I am installing and start the flashing process. I use AmonRa 2.3 as I have had issues in the past with clockwork not wiping properly. I never punch in my google account until I can disable restore features. I have tried the desktop clock and google nav on a freshly installed version of each of those roms with touching nothing else and also with full profile and all that, they still do what they do.
So my question is to the community, am I overlooking something or does anyone have any ideas for me? I wanted to hit up this forum first before going to the respective dev forums. Thanks.

I use the desktop clock every night too, on my night stand.
You know, the button next to the "night" button takes it right to the clock screen.
As for Nav, I rarely use it, living in a small town, so I haven't had that problem

Watcher07 said:
So I've tried out MikG 2.2, Synergy nightlies and 6/27 RC1, Kingdom Revolution and Synergy-Kingdom and I seem to have the same two prevalent issues I could use some help with.
1.) I use the desk clock feature of my EVO in night mode. Problem is all these roms share a common problem, that being that for some reason the World Clock service will crash and take it out of night mode. Also not sure why but with standard EVO sense roms it immediately goes to the clock whereas with the sense 2.1/3.0 roms the screen dims but doesn't go to the night clock for somewhere around 10 minutes like on an aosp rom.
2.) I use google nav heavily. I make about 10-15 stops a day for work and need it always running. Problem is with sense 2.1/3.0 roms that for some reason I haven't been able to identify, the screen will dim randomly and ultimately shut off during navigation sessions. I have tried setting the screen to always on while charging, messed around with spare parts and set the brightness to manual and auto, disabled power saving features on the phone, all to no avail. The phone is constantly plugged in and mounted on my dash, so its always charging.
I keep no personal info on my phone, so when I wipe it for a rom, EVERYTHING is wiped. SDCard, Rotation and battery stats, data, cache, system, boot, everything. I do that once over, then mount it, format the sdcard with my computer, then copy vr_superwipe and flash that to wipe it all again, then remount, format again on computer, unmount and go through the wipe list again, then remount and copy over whatever rom I am installing and start the flashing process. I use AmonRa 2.3 as I have had issues in the past with clockwork not wiping properly. I never punch in my google account until I can disable restore features. I have tried the desktop clock and google nav on a freshly installed version of each of those roms with touching nothing else and also with full profile and all that, they still do what they do.
So my question is to the community, am I overlooking something or does anyone have any ideas for me? I wanted to hit up this forum first before going to the respective dev forums. Thanks.
Click to expand...
Click to collapse
I haven't noticed any of those problems in regard to the navigation app and I use both Google & the Sprint TelNav app often. My device's display stays lit when I'm using the apps. I haven't noticed the thing in regard to the clock either, but I'll experiment with it later and sew what I CA cone up with. Finally, your method of wiping is suffice. You really don't need a superwipe or format-all zip when yo have RA v2.3 and you wipe EVERYTHING in the wipe menu except the card. If you have the time, flash Warm 2.2 RLS-5 and see if you still experience the things you referenced above.
posting & replying from my EVO 4G

HipKat said:
I use the desktop clock every night too, on my night stand.
You know, the button next to the "night" button takes it right to the clock screen.
As for Nav, I rarely use it, living in a small town, so I haven't had that problem
Click to expand...
Click to collapse
Not so much worried about the screen not dimming, more dealing with the entire app crashing. Might be worth mentioning I'm on a hw0004 evo as well. I've also used Calkulins latest radios combo pack to make sure I'm at the latest of all radios.

Something new about the nav issue, the screen doesn't shut off fully, I let it go today to see what would happen and the screen stayed dim until the voice needed to prompt me for a turn in which the screen returned to normal brightness. So it would appear that for some reason the screen will dim after a couple minutes if you're on a straight leg of a trip but will bring the screen back up to normal brightness when it needs to communicate to turn or whatnot. Not sure what to make of that but I was able to confirm it multiple times.
**UPDATE**
Well, apprently a few other people have been seeing this issue from the google maps 5.7 update, so it looks like it might not be ROM related.

"New" problem? Sleep of Death?

Hi everyone!
So far for the past 2 years I have been running various builds of Android on various Kaisers (yes, I have 4 of them now).
For the past 6 months or so I have stuck with the 2.2.2 build from SourceForge (system_froyo_us_odex) and never had any issues... until now.
All of a sudden, for the past 2 weeks I have been getting that dreadful "sleep of death" problem, sometimes upwards of ten times a day!
Current installation is as follows:
Scoot cache kernel, 15mb cache, 500mhz, ext4, 1500mah battery.
Froyo 2.2.2 US Odexed from SF with all the stock apps, extras listed below
ADW EX Launcher ver. 1.2.2
Beautiful Widgets ver 3.3.4 with the animation package (Super clock 4x2)
Rogue tools
Root explorer
Scanner radio (barely use due to constant data usage)
Pandora (again, data usage can be high so barely used)
Facebook ver 1.8.2 or current build
Foursquare ver 2012.02.27
I have looked at dmesg on the SD and compared to one from a backup SD but cannot find anything extraordinary, nor is there anything wierd in /system/sysinit.rc. Performed a complete wipe and reinstall from stock with all the same apk's and even changed to the brand new (turned on once) Kaiser after unlock/SPL install.
If anyone sees anything out of line (except the BW 3.3.4, I like my flip clock), please do let me know. If there is any files you may need from either the phone or SD card I can paste them accordingly.

Okay, made some line entries in build.prop via root explorer's text editor and added the line "ro.ril.disable.power.collapse" with the argument set to 1, which should have turned off any sleep mode, and also added the line "pm.sleep_mode" with the argument set to 1. This after doing a search on google for build.prop tweaks (there's a bunch).
Battery life has suffered a little but it seems to have helped somewhat. It will still hard lock in sleep mode and be unresponsive until a stylus reset or battery pull.

I got an equal issue after inserting pm.sleep_mode= in my startup.txt for haret. Sometimes the 'sleep of death' and sometimes never ending boot circles. The only argument working is the default value '1'

What I ended up doing was to go back to scratch. This happened on 2 separate phones by the way so the spare was the guinea pig.
I started with the kernel first, rebuilt it and reinstalled it, then installed a clean froyo build, which would still hard-lock.
I went back even further and reflashed the SPL, then rebuilt the kernel as before and another new froyo install, which seemed to work. I then copied what I did on the spare and refreshed the newer phone and synced my accounts to it, then reinstalled all of the apps, one at a time, to make sure there wasn't one causing this.
So far so good, no SOD or hard locks.
Went in and re-edited the build.prop to add some performance mods (dalvik.vm.startheapsize=4m, dalvik.vm.heapsize=32m, etc)... seems to be better, smoother and doesn't FC apps as much.
We shall see what happens...

Well, since you can't find this post on the front page, I'll have to put up a new post about my build.prop changes that really help with speeds and FCs'.
Look for it on the front page...

[Q] Maps/Navigation force closing on custom ROM/Kernel - HELP Please!

Hi all,
Hopefully someone can shed some light on this and help a tortured soul. By no means am I an Android expert, but I definitely am not a noob. I had an S2 in the past and done plenty of flashing there, and now own a Bell SGH-I747M S3... my precious...
First off I tried a whole bunch of different ROMs, of all flavors (AOSP, AOKP, CM10, PARANOID, and some TW), and a lot of them are awesome. However, I found that after having done so much flashing and customizing using other people's work, it was now time for me and attempt to make my own ROM. I feel I now have the knowledge to do so. Don't get me wrong, I am far from a Dev, and I don't do much coding at all. I found this great suite called Android Kitchen, which pretty much guides you through the steps for making your own ROM, and it's great for learning.
In the end, I was able to come up with a final working version of my own ROM, built from scratch using the original official Bell JB 4.1.1 update file. and I have to say I am quite proud of it, as it has all the apps, features and theming that I want, and works quite well I might add. I get great results performance and battery wise (for my taste and needs) when using my ROM with KToonsez kernel.
BUT!!... as good as I think the ROM is, it is unfortunately not flawless. I do have an issue (the only one I could find so far after 2 weeks using it), and for me it is a BIG issue. Maps/Navigation does not seem to like the ROM/kernel combo on MY phone. I say MY phone because I have setup a friend with pretty much the same thing, and he is not experiencing the same issue.
Here is a description of the problem I get. Let's say I go to my contacts and select one with an address. I will touch the address, then Maps opens no problem, and finds the place, and I also get fast GPS lock, no issues there either. Then I will select Navigate to get a voice turn by turn description while driving. The Nav app starts OK as well and seems to work fine. Then after a few minutes (sometimes 2 sometimes 10), Navigation will shutdown, and I get a pop-up saying "Unfortunately Maps has stopped working...". When I OK that, after a few seconds, Navigation starts talking to me again, although not on screen. Also a Navigation icon will appear in the notification area, and if I hit that it resumes Nav, as if nothing had happened. Another few minutes like that, and then I get the same message again, but this time it crashes for good. ALWAYS!!
Troubleshooting:
- Flashed the ROM/Kernel 3 times now. Always wiping and formatting ALL!
- Cleared cache and data from Android Settings/Applications
- Cleared cache from Maps settings.
- Re-installed Maps
- Wiped phone cache, dalvik cache and fixed permissions from recovery.
- Changed kernel back to stock (that seems to work fine btw,, but I do not want stock kernel, plus the setup I want works well on my friend's S3, same as mine, which I setup myself for him (he's a total noob)).
- Changed kernel again from stock to KToonsez (that also works fine after that, however I get other things that start not working well... too many).
- I always wipe cache, dalvik cache and fix permissions after changing kernels.
I have been poking at this for about a week now, and I am tired! I was hoping someone would have a suggestion, maybe from past experience. The only thing I can think of that is different on his phone and mine is the apps that we restore after installing the ROM and kernel (Titanium Backup, user apps and data only, nothing related to system is touched). I am guessing one of my apps could cause a conflict, but pardon my laziness, but I really do not feel like testing / installing my apps one by one to hopefully without guarantee find a culprit... way too many apps for that So I am testing my luck here on XDA... there are a lot of smart people here
I appologize for the lenghty post, but this way, there is less chance I left anything out... PLEASE HELP!!!
Raz...

Sorry for the bump guys... I was really hoping someone can give some input here. Desperate for a solution here!!
Thanks

Note 2 defaults after reboot

Hello xda community, utter n00bie here, but I have done a lot of reading/searching/researching for quite some time.
Last night finally broke loose and rooted my AT&T i317 Note 2, flashed Scott's Clean ROM 1.5 SE, and Andrey's Perseus kernel for some overclocking.
I was hoping this would get fixed with the new Clean ROM, but it hasn't so that's why I need your guys help.
I searched the forum and found some other ppl having similar (yet different) issues but haven't really found a solution or cause for this issue on the forum.
Things that I've noticed revert back to defaults every time I reboot the phone:
SwiftKey reverts back to stock Samsung keyboard (Extremely annoying.. but I've found on forums that some ppl got around this by "freezing" the Samsung keyboard using Titanium... don't know if that's a solution or a temp fix =/ )
System Options -> Developer Options -> Limit background processes -> goes back to "Standard Limit" from "4 processes at most" I have found by keeping "4 processes at most" keeps my battery alive A LOT longer and does not negatively affect phone's stability. But every time I reboot the phone its annoying how this settings reverts back to the default "Standard Limit" which allows all apps to run in background.
My Camera and Video recorder shortcuts go back to defaults. In Camera Mode, there is an Option "Edit Shortcuts" and you can change Scene Mode, ISO, Metering...well all these go back to defaults when I reboot. Also very annoying.
Anybody know why this is happening? A way to fix this?
Thanks guys

ditto here..
i have the same issue with my droid charge.. camera "review" setting gets checked.. notification goes to "droid" default.. i have to resign in to outlook.. crap.. utter crap..
i haven't found any technical explanation yet.. i'm guessing a wipe and re-rom.