Develop Bugs

Crash -> Black Screen -> Battery Pull

I'm getting a crash once every 3-4 days on average that requires a battery pull. So far I've had it happen while receiving a Whatsapp message, replying to a Google+ notification, and most recently, while listening to music.
I know I am not alone because I have seen a few other threads talking about similar issues. I am wondering how widespread this is however while I try to decide whether to return the phone or not. Are any of you running for a long period of time (1 week or more) without any instability?

I've had it happen to me a couple of times too, once when playing a movie in Diceplayer, and accidentally push the power button, causing the screen to go blank, then I couldn't turn it back on. Had to pull the battery. Had it happen to me again this morning, can't remember what I had done prior to it happening, though. Anyway, I did not have the time to pull the battery, so I just tried it again a couple of minutes later, and it woke up, all was normal again.

Happened twice only since November 25th to me.

I've had the phone now for a couple of weeks and have yet to have a crash.

My phone crashed two times in one week. Booth times when i closed a game.

Just take into consideration that most of these crashes are due to incompatibility between ICS and apps that don't officially support it yet. Not as much due to the device itself. So returning it and getting a phone running gingerbread won't solve the crashed when that phone eventually gets ICS....

I get it every few days too. Crash followed by what looks like the phone trying to reboot, but screen just goes dead and I need to pull battery to restart it.

i have had this too a few times. the screen just turns off, and won't turn back on. have to pull the battery before i can turn it back on.
this last time, i was just in the sms app, reading a message. i noticed the text was rendering strangely, with sort of colours around the edges of the letters, as if it was a low-res screen. then just as i tapped the message, to try to see if the rendering would change if i highlighted it, the screen turned off, and the phone seems to be dead, requiring a battery pull before i am able to turn it back on.
i haven't pulled the battery yet, and the phone is still sitting apparently dead. however i also notice that despite the screen being off, and it sitting here for a while doing what seems like nothing, the top half of the phone is actually pretty hot (front and back). not due to the screen having been on either, because the bottom half is cold.

Try turning off the eq in the music player. Worked for me it seems.
Sent from my Galaxy Nexus using Tapatalk

Based on the replies received so far, I think it is fair to say that these crashes are most likely related to software issues (as opposed to hardware). I guess patience is due while our bleeding edge technology stabilizes..

me too
Yes, i have also had a crash twice in the one week that I have had sgn which required a battery pull to turn the phone back on. I think the first time, I was in the settings and it looked like a few pixels were going crazy then screen went black and I had to pull battery. Then about 5 days later, I was not using the phone but when I went back to it, the screen was black and I couldn't turn it on untill battery pull. Watching this thread with interest.

Had it a few minutes ago with Facebook. Had just opened it when it turned black. No button responded. Eventually managed to get back in menu. Considered removing the app.
Sent from my Galaxy Nexus using xda premium

Didn't have a black screen so far, but had it freeze 3 times in the week that I own it (2x Google Maps, 1x in Gallery when pressing home button). Screen stays just as it is, no corruption, no dimming, no response to anything.

I had similar problems guys and horrible battery life. It is 100% an app you downloaded.
Do a complete wipe or figure out which app it is one by one. I did the second method and I only lose 1% of battery life an hour on standby.
Completely stock GN with 4.0.3 - never rooted, locked bootloader
Sent from my Galaxy Nexus using XDA App

Wifi Error, strange behaviour - continously slows down after new rom

I've got a huge problem with my Desire HD that just drives me crazy and still I don't know what to do about it - googled for hours, haven't found anything but unfinished threads.
It started a while ago, I had a ICS - Aokp installed. Some day, WiFi turned off and when I tried to turn it back on, it either remained in the "Turning WiFi on..."-state or gave me an "WiFi Error". Also, the whole OS slowed down terrible.
I installed a 2.3.7 Sense ROM. Worked for a few days, I think. Then one time, the phone froze and after reboot, the WiFi Error occured again.
Switched to Virtuous Infinity v1.31.0. Worked fine for maybe a day, froze, same error. And worst of all, it slew down more than before. Example: Unlocking Screen -> (3 Seconds) -> Displays GUI -> Whatsapp Link -> 10+ Seconds -> displays WhatsApp - but that's not even the end, try to enter text when it displays 1 sign per second. You finish typing, wait 15 seconds to hit the "send"-button.
2 hours ago i installed JellyBean (4.1.1). Without it freezing, WiFi just turned off an won't turn on again. I rebooted, while bootanimation, it froze. I took out the battery, rebooted - it doesn't run as smooth as it did before and WiFi still won't work again. I think in the next 14 days it will slow down again like it did before. It's like there would be processes in the background that need the entire CPU power, but anyway i monitored CPU usage using SystemPanel. There was no CPU usage recorded. I killed apps, no difference. I also intended to monitor the CPU speed, but it wasn't possible with the previous kernel.
Do you have any suggestions, what i could do? Right now, i just want to smash my phone.. it's not dependable. Sometimes my phone rings but won't turn on the screen cause of the stability problems .. I am through so many Android versions, I'm just tired of installing new roms every 2 weeks so i can still use my phone.

Alarm Free Date (#SAD...) bug

Hello everyone,
I know the alarm free date #SAD...# is a beta feature at the moment, but I've run into a bug with it that I thought you should know about.
I have a section on a widget where I show the next alarm date and time, but I want to also show bedtime, which would be the alarm minus 8 hours. I know for standard dates, I can do something like #D-480...# if I want to subtract 8 hours. I can even do math within the variable, such as #D-$(8*60)$...# to subtract 8 hours. When I try this same sort of thing with the alarm free date variable, I find that it compounds amount added or subtracted each minute until something causes it to reset.
To make a simple example, if my alarm is set for 3:30 on Monday, and if I want to display the alarm time with 1 minute subtracted from it, I use #SAD-1 P:mm p#, and I should get 3:29am on Monday. It works correctly for the first minute, but as soon as another minute passes, I see that the the adjusted alarm time now shows 3:28am. So every time a minute passes, the adjusted alarm time gets multiplied by the number of minutes passed since I saved the widget. If I subtract 2 minutes at a time, then I see the time drop by 2 minutes as each minute passes. If I do 8 hours, then, well, it gets very strange very quickly.
I have noticed that the adjusted alarm time will reset from time to time, going back to the correct calculation for a minute, but I'm not sure of what causes the reset. Sometimes it will go back to the correct calculation after editing the widget, and sometimes it won't. Other times it will go back to the correct calculation after my screen has been off for a little bit and then I turn the screen back on, but not every time. Also, it looks like it may not add or subtract additional increments while the screen is off. Again, with my example of subtracting 1 minute, if my screen timeout is 2 minutes, then by the time the screen turns off, I'll see 3 minutes subtracted in total. If I turn the screen back on 10 minutes later, it will still show the 3 minutes subtracted. The next minute that the screen is on, it will either reset to 1 minute being subtracted, or it will continue to 4 minutes subtracted.
FYI, I'm on a Samsung Galaxy Note 3, Android version 4.4.2, Sprint, rooted, but I am running on stock ROM and kernel.
I hope that this helps pinpoint where the bug may be. Please let me know if any other information is required.
Thanks,
Jeremy

Same problem here.

Running apps force close when in use (Runkeeper, Strava)

Hi!
Since the first (official) upgrade to Android 7, and even now with the new 7.1, I've been having this issue everytime I use any of these apps.
I always used runkeeper to track my mtb trails and it always worked perfectly. When this started to happen once, twice, etc, I decided to change to Strava, as I assumed it was an app problem.
The same thing happened on strava!
This situation happens on a random time (it happened once after 10 minutes of use, it happened other time after 2 hours of use, completely random). I have kept with strava as, after a force close, when I open the app again, it recognizes that a problem has happened and it restarts from the last recorded place.
Anyhow, this is a very annoying situation, as if I don't notice that the app closed, I will loose most of the trail.
I have disabled "Agressive doze & app hibernation".
Any other ideas?
Thanks

I have the same on 8.0. Compleate stopper for using OP.
All fitnes apps that use gps stop after 10 or 20 or 30 min of bacground work.
Also i use heart rate sensor and it does not restarts itself. It stales Bluetooth and you can not reconnect hr sensor without rebooting device
Considering to swith to Samsung)

Try turning battery optimization off in settings for those apps. I am not sure if this works but give it a try.

Basic features/functions breaking?

Over the past few months, I've noticed that some standard functions of my phone routinely fail and no longer seem to work properly until I reboot and/or wait a certain number of days until they magically start to work again (only to break again).
1) The auto-adjust sensor is waaaaay off at gauging ambient light. Whenever I'm in bright, sunny environments (like outdoors or by a window with sun coming through it), the brightness and backlight adjust to the lowest level so that it looks like my screen isn't on. The opposite happens whenever I'm in a room with low or no lighting, making it look like a supernova is in my hand and hurting my eyes. In the past, the sensor would eventually adjust to correctly accommodate the lighting, but now it just doesn't.
2) A large number of apps that are set up for fingerprint login immediately give me an error notification that I've exceeded my fingerprint login attempts whenever I open them, forcing me to instead log in with a pin number. Closing and reopening these apps doesn't fix the error, rebooting doesn't fix it, and clearing the app's cache and/or data doesn't fix it. I just have to wait it out until it works again, which is usually 2 days to 1 week after I've last used the app.
3) Holding the Power + Homes button no longer takes screenshots. I can fix this one by rebooting, but eventually this combo stops working again.
4) Several apps, specifically Google Maps and Chrome, will often crash up to 3 times before they're able to stay open and work. I also routinely hard crash out of everything whenever a foreground app I'm currently using (like Chrome) crashes, which causes everything open in the background (like my music or YouTube app that are playing) to also crash.
5) My battery level is stuck at 69% and won't drop. For the past 4 hours, Android OS, GSAM and BetterBatteryStats all show that I have 69% percent battery remaining and continue to show that percentage even though I have nearly 1 hour SoT. I can only get 2 hrs 15 min of SoT before my battery runs out, so I know this isn't right. This battery thing just started today.
Why is everything breaking?!? Since December, I've not installed any new apps, system updates or really traveled anywhere. Before I flashed the ROM I'm on (LeeDroid v5.2.3-R151) last November or so, I did a full wipe and did not restore any apps or settings so that everything was fresh.

macschwag14 said:
Over the past few months, I've noticed that some standard functions of my phone routinely fail and no longer seem to work properly until I reboot and/or wait a certain number of days until they magically start to work again (only to break again).
1) The auto-adjust sensor is waaaaay off at gauging ambient light. Whenever I'm in bright, sunny environments (like outdoors or by a window with sun coming through it), the brightness and backlight adjust to the lowest level so that it looks like my screen isn't on. The opposite happens whenever I'm in a room with low or no lighting, making it look like a supernova is in my hand and hurting my eyes. In the past, the sensor would eventually adjust to correctly accommodate the lighting, but now it just doesn't.
2) A large number of apps that are set up for fingerprint login immediately give me an error notification that I've exceeded my fingerprint login attempts whenever I open them, forcing me to instead log in with a pin number. Closing and reopening these apps doesn't fix the error, rebooting doesn't fix it, and clearing the app's cache and/or data doesn't fix it. I just have to wait it out until it works again, which is usually 2 days to 1 week after I've last used the app.
3) Holding the Power + Homes button no longer takes screenshots. I can fix this one by rebooting, but eventually this combo stops working again.
4) Several apps, specifically Google Maps and Chrome, will often crash up to 3 times before they're able to stay open and work. I also routinely hard crash out of everything whenever a foreground app I'm currently using (like Chrome) crashes, which causes everything open in the background (like my music or YouTube app that are playing) to also crash.
5) My battery level is stuck at 69% and won't drop. For the past 4 hours, Android OS, GSAM and BetterBatteryStats all show that I have 69% percent battery remaining and continue to show that percentage even though I have nearly 1 hour SoT. I can only get 2 hrs 15 min of SoT before my battery runs out, so I know this isn't right. This battery thing just started today.
Why is everything breaking?!? Since December, I've not installed any new apps, system updates or really traveled anywhere. Before I flashed the ROM I'm on (LeeDroid v5.2.3-R151) last November or so, I did a full wipe and did not restore any apps or settings so that everything was fresh.
Click to expand...
Click to collapse
Since you're having multiple, seemingly unrelated issues, there is no way for anyone to tell why it's happening in your specific case. Why don't you try dirty flashing your leedroid rom, and if that still fails, start from scratch?