Related
My galaxy S freezes out of the blue, and i can't even turn it off. Sometimes i look to check the time, and noticed the phone is turned off. Both problems are only corrected by taking out the battery, and putting it back in...and then waiting for it to happen again!
Is this a software issue that 2.2 will fix? Should I exchange for a new one, or will all of them have the same problems, if bought from the same place? (Best Buy in Vancouver Canada)
either your battery is not good, or your got a defective phone
the new SGS out of the box works smooth
what is your firmware version?
type in
*#*#1234#*#*
Sounds like a bad phone. I got mine from one touch in delta and it has been perfect. Return asap and get yourself a working unit.
Sent from my GT-I9000M using XDA App
Thought you meant lag. Mine lags a lot (stock firmware) and sometimes "freezing" seems the word.
But no, that's not it. Perhaps you can try a hard reset and check your sdcard too, something isn't ok.
I'm actually experiencing the same issue. My phone goes black and seems to be happening more in low wireless connection areas. Like in a mall. With the the *# code I get I9000UGJG9.
if you have LAG issues, install the one click lag fix in the development area
problem solved
Its not LAG issues it a complete freeze issue. My phone goes black like standby mode and will not come out of it. The only fix is a battery pull or holding the power button for 6 seconds. The same issue as the op.
TDS1234 said:
Its not LAG issues it a complete freeze issue. My phone goes black like standby mode and will not come out of it. The only fix is a battery pull or holding the power button for 6 seconds. The same issue as the op.
Click to expand...
Click to collapse
that is a factory defect
take it back, exchange it for a good one
this latest firmware is really good, you should not see anything like that
Allright will do. I figured as much I didn't want to bring it back I already purchased some apps. Guess I'll have to wait for my store to get some.
TDS1234 said:
Allright will do. I figured as much I didn't want to bring it back I already purchased some apps. Guess I'll have to wait for my store to get some.
Click to expand...
Click to collapse
you do not lose the Apps
once you log back into your Gmail account in your new phone, when you go into Android Market, they will remain in the Download section
those apps are saved in your Gmail account, not in the phone.
that's the cool thing about the android phones
so if you ever switch to say an HTC Android, or a Nokia Android, you can still re-install those apps (assuming they are compatible)
Oh sweet I wasn't aware of that. I sold a couple of the Galaxy S and I'm the only one with this issue as of yet. Hopefully it isn't a common one. I've been trying my best to convert Iphone buyers in most cases when I'm sold out to get this phone I just hope it delievers for my customers and they won't have the same issue as me.
Are u futzing with oclocking or changing CPU mode ? This causes hangs with black screen
Sent from my GT-I9000 using XDA App
I believe this same thing just happened to me. Plug in my phone to recharge it (got it 2 days ago, so the battery still runs out quick) then tried to activate it and Lock screen wouldn't disappear when sliding.
mrfocus22 said:
I believe this same thing just happened to me. Plug in my phone to recharge it (got it 2 days ago, so the battery still runs out quick) then tried to activate it and Lock screen wouldn't disappear when sliding.
Click to expand...
Click to collapse
you do know you don't just slide
you have to move the entire picture of the "slide" out of the phone frame for it to unlock
if you say only slide it partially, it will just bounce back and remain locked.
if you have thick fingers it wont work properly
you might be better off using the 3rd party unlock screens, specially the kinds that needs no sliding.
i have that issues nowadays too. randomly "freezes" on the black screen, i can call through my phone (ringing) but there's no notification / vibration or anything or sorts.
the only way is to reboot the phone and it'll randomly happen again after some time >.> and the call that i've just missed isn't showing on the call-log either.
i hope it gets better overtime or i'll just have to reflash!
ps. was fine before i tweaked my cpu settings in sleep mode, you might wanna disable that if you're using it.
Mine has the same problem and by the looks of things a lot of people have this issue. I called customer support and after sometime the rep admitted this and said it will be fixed in next build however I doubt that
Then there are probably lots of diff units out there. The phone shouldn't freeze unless you are using a beta/alpha firmware (pretty unlikely - i've tested more than 10 different firmwares without a freeze), or set the core clock of the cpu to a higher & unstable frequency (OC). people claim that their phone can do 1.2ghz - that's nice, but each chip has a different capability.
This is not a troll posting. I swear...
I've had the AT&T flavored Nexus One since the day it was announced and I just can't suffer with it anymore. I'm running stock FRF91 with an unlocked bootloader. The only reason I unlocked the bootloader was so I could root and uninstall the apps that drained my battery or sucked resources that I never used - Twitter, Amazon-MP3, Genie-Widget, etc.
Pre-Froyo, it seemed pretty stable but the OS was very immature. Some things were just not well thought out. Activesync for example.
Post-Froyo: Turn on GPS, reboot. Talk on the phone for a long period of time, reboot. Charge the phone, reboot. Use Bluetooth, reboot. GPS is 100% useless now as after just a few minutes of use, the phone gets hot and reboots the phone. Hell, leave the phone in the sun in your car and it gets hot and reboots. Froyo offers some new features but some areas of the OS are still neglected and way behind where they should be. Can't move emails to a folder? Seriously? Can't undelete an email you accidentally deleted? That's just stupid. And there are a few other things that Windows Mobile had right for the last 10 years.
Yesterday alone, my phone rebooted several dozen times because I was trying to find a location with GPS and I was completely turned around with no idea where I was. I finally had to power off the phone, leave it off, and go ask someone at a gas station for directions. The phone reboots as soon as it gets hot and it appears everything makes the phone get hot.
Rip on Windows Mobile all you want, but I never once had a Windows Mobile device reboot on me and not do what it normally does. I'll throw CM6 on my N1 when it becomes final to see if things get better and I'll thrown on Gingerbread when that finally drops, but unless one of those solves the constant reboot issue, I'm done with Android. I've kept up with the Google forums and many, many, many people have the same issues I have so my N1 is obviously not an isolated case.
There are a lot of things I do like about Android so I'm not bashing Android. I like Android enough that if my phone didn't reboot constantly it'd be my primary platform moving forward.
/rant
-Mc
I've had my N1 since the day after they were released and it has never rebooted spontaneously. Your phone is a lemon.
Try calling HTC?
vzontini said:
I've had my N1 since the day after they were released and it has never rebooted spontaneously. Your phone is a lemon.
Click to expand...
Click to collapse
I agree, the only time my phone gets hot is when I leave it in my landscaping truck while I'm mowing, but I think any phone would have problems when it's 112 degrees outside and probably 140 in the truck.
Sounds like a bad phone. The only time my N1 rebooted was when I had an experimental rom on it.
Sounds like something is just borked, I use my phone all day it only reboots because I want to go into recovery.
Are yur using custom recovery? Wipe the cache and dalvik-cache.
Same as the above poster, mine never rebooted spontaneously even when hitting over 40C degrees. Only does so when I'm running some cutting-edge alpha kernels/ROMs, and then very rarely.
I was thinking it was specific to my device as well. I then googled "Nexus One overheating" and was overwhelmed by the number of people with the same issue. I also own over a dozen HTC devices, I've had ZERO problems with any of them. I've wiped my cache quite a few times. I've even wiped the phone and started fresh.
I've googled every specific issue I have had and found many others complaining about the same thing. Overheating/locking up the device when charging overnight - check. Rebooting/overheating when using GPS - check.
Lately, I've been uninstalling anything that runs in the background that isn't an essential part of the OS. Makes no difference. When I first got my N1, I used the GPS and Car Home app to drive an 8 hour trip. Not a single problem. The very first time I tried to use Car Home after going to Froyo it rebooted after just a few minutes and it's been that way since. I found MANY posts that confirmed this on Google's forums.
Personally, I think my device is fine. I suppose it's always possible that an app is causing the reboots. For example, the Weather Channel app is always running and that's not the most beautifully coded app I've ever seen...
Any suggestions, keep 'em coming. I'm not thrilled with Windows Mobile 7 yet.
Here's my installed apps (I love that program BTW). If you see anything as a possible suspect, let me know:
Adobe Flash Player 10.1 (v10.1.92.8)
andLess (v1.2.3)
Android Agenda Widget (v1.3.5)
AT&T myWireless Mobile (v6.0)
Audalyzer (v1.14)
Barcode Scanner (v3.4)
BlueRSS (v3.0.4)
Chrome to Phone (v2.0.0)
eBay (v1.1.2.3)
eBuddy (v1.8.1)
Ethereal Dialpad (v2.5.2)
FCC Test (v1.0.7)
Flashlight (v2)
FREEdi Video Download Helper (v1.3.1)
FrostWire (v0.3.7)
Google Translate (v1.1.1)
GPS Status (v3.2)
gStrings (v1.0.5)
HistoryEraser (v2.1.1)
HTC_IME mod (vv.27)
JScreenFix (v2.0)
Keyboard Calibration (v2.10)
Linda Manager (v1.5.12)
Listen (v1.1.3)
Log Collector (v1.1.0)
Music Junk (v3.0.4)
My Battery Status (v2.0.8)
MyAppsList (v1.4 BETA)
Network Info II (v0.3.4)
Note Pad (v1)
OSMonitor (v1.1.6)
Pandora (v1.3)
Penguin (v1.2.0)
RealCalc (v1.4.1)
Scanner Radio (v1.9.2)
Secrets (v1.9.2)
Shazam (v2.0.2-B70005)
Shopper (v1.12)
Solo Lite (v1.25)
Terminal Emulator (v1.0.12)
Tetronimo (v1.5.1)
The Weather Channel (v2.3.17)
Titanium Backup (v3.4.2)
Trapster (v1.6.3)
Tricorder (v5.11)
TTS Service Extended (v2.0)
Universal Androot (v1.5.3)
Voice Recorder (v2.0.7)
Wifi Analyzer (v2.4.8)
WiimoteController (v0.3b)
XDA (v1.2.1)
Device Summary
Device: HTC Nexus One
Android Version: 2.2
Build: FRF91
List Generated By: MyAppsList (market://search?q=com.boots.MyAppsList)
By the sound of it, it's not an app. The phone should be able to take a good amount of heat and not reboot - the only time I got it to reboot was under direct sunlight in a car, it was probably hitting 50 degrees Celsius. If yours reboots every time you do anything - it's time to nandroid, take out the battery and clean the battery contacts really well (on the battery and the phone, using alcohol), flash a bone stock FRF91 or something really close to it, try to repeat the things that made it reboot (shouldn't be very difficult), and if the reboots continue - then I'm sorry, but you have a lemon. And if they don't - change to your favorite ROM and start incrementally installing stuff in small packs, until your testing shows reboots again. Defining anything other than Google account (like Exchange account) is also considered "installing something".
E-Mail quirks are taken care of by E-Mail clients. Exchange server push might be draining the hell out of your battery and heating your phone, check the relevant thread. I really hope you find the problem in SW, but it doesn't look very much like it.
P.S. There are so many ways to get a WinMo phone stuck (my wife has one, I regularly practice using the reset button when doing something with the system) it's not even funny.
thanks for the tips. I'll give them a shot. I read in a couple different threads that HTC has been sending replacement batteries to those with overheating issues. I have a hard time believing it's the battery but what do I know?
One thing I forgot to add about WinMo, I soft reset my device every morning on the way to work. Just a habit I got into with Windows.
-Mc
Yeah sounds like you got a faulty device. If the above suggestions don't work, call HTC and they should do a swap for you
went to the Google "Device Troubleshooter" support page: http://google.com/support/android/bin/answer.py?hl=en&answer=185837
Step 1: What are you having an issue with?
selected: A hardware problem I'm having with the Nexus One
Step 2: A hardware problem i’m having with the Nexus One
selected: My device overheats
Then it said this:
It is normal for your phone to get warm after an extended period of continual usage, such as a long phone conversation. If your phone becomes so warm that you cannot hold it comfortably, please try removing the battery and waiting until the phone cools off before replacing it.
If your phone overheats to the point of shutting itself off repeatedly, there may be a hardware defect with your phone's battery. Please visit our warranty information page.
Click to expand...
Click to collapse
So I called support (open 7 days a week - nice) and they are shipping out a new battery tomorrow and if that doesn't work, I'll send it in for repair. Didn't want to replace it because it was engraved.
I really hope this fixes it. I do like Android and I love the community work. iOS blows and Windows Mobile 7 just doesn't have me wanting one.
I'll update this thread when the new battery arrives and if necessary, after the repair work...
I used to have the same problem, but i don't think it was rom specific for me. I had a black case on my phone and my car mount was a black universal one mounted on my windshield. I would use GPS nav and play music at the same time and sometimes make phone calls and it would reboot pretty frequently. Through SetCPU i noticed that the temp was somewhere between 45-50degrees C. only way i was able to use my phone was to remove the battery and stick it in my AC vent along with the phone itself.
So since then i got myself a AC mounted carmount and no longer use my case and its been fine ever since. When ever it gets hot in my car i usually have AC on and the phoen gets cooled by it also. Average temp was around 15-18degrees C while i was using GPS/Music/Calls.
lulz, sounds like your phone had a hardware issue if it was rebooting all the time like that.
I have had my phone on for literally weeks at a time with out a reboot. Android is rock solid stable.
Way to not get your issue fixed and go back to a dead mobile OS that was never developed properly in the first place. Good luck with that champ.
My phone could stab me in the balls all day long and I still wouldn't revert to the current winmo.
McHale said:
This is not a troll posting. I swear...
I've had the AT&T flavored Nexus One since the day it was announced and I just can't suffer with it anymore. I'm running stock FRF91 with an unlocked bootloader. The only reason I unlocked the bootloader was so I could root and uninstall the apps that drained my battery or sucked resources that I never used - Twitter, Amazon-MP3, Genie-Widget, etc.
Pre-Froyo, it seemed pretty stable but the OS was very immature. Some things were just not well thought out. Activesync for example.
Post-Froyo: Turn on GPS, reboot. Talk on the phone for a long period of time, reboot. Charge the phone, reboot. Use Bluetooth, reboot. GPS is 100% useless now as after just a few minutes of use, the phone gets hot and reboots the phone. Hell, leave the phone in the sun in your car and it gets hot and reboots. Froyo offers some new features but some areas of the OS are still neglected and way behind where they should be. Can't move emails to a folder? Seriously? Can't undelete an email you accidentally deleted? That's just stupid. And there are a few other things that Windows Mobile had right for the last 10 years.
Yesterday alone, my phone rebooted several dozen times because I was trying to find a location with GPS and I was completely turned around with no idea where I was. I finally had to power off the phone, leave it off, and go ask someone at a gas station for directions. The phone reboots as soon as it gets hot and it appears everything makes the phone get hot.
Rip on Windows Mobile all you want, but I never once had a Windows Mobile device reboot on me and not do what it normally does. I'll throw CM6 on my N1 when it becomes final to see if things get better and I'll thrown on Gingerbread when that finally drops, but unless one of those solves the constant reboot issue, I'm done with Android. I've kept up with the Google forums and many, many, many people have the same issues I have so my N1 is obviously not an isolated case.
There are a lot of things I do like about Android so I'm not bashing Android. I like Android enough that if my phone didn't reboot constantly it'd be my primary platform moving forward.
/rant
-Mc
Click to expand...
Click to collapse
Your phone is defective. I've NEVER experienced a spontaneous reboot.
uansari1 said:
Your phone is defective. I've NEVER experienced a spontaneous reboot.
Click to expand...
Click to collapse
Same here** (only when I played with different kernels )
GldRush98 said:
Way to not get your issue fixed and go back to a dead mobile OS that was never developed properly in the first place. Good luck with that champ.
Click to expand...
Click to collapse
you're not much of a reader, are you?
JCopernicus said:
My phone could stab me in the balls all day long and I still wouldn't revert to the current winmo.
Click to expand...
Click to collapse
Fact: Windows Mobile still does several things much better than Android. And those things are important to me on my primary device.
I get what you're saying though. Despite a few issues, Android is dominating everything in it's wake. But instead of Android spending so much time with new flashy features, they should focus their attention getting the basics right first. Their contact and email handling B L O W S. How about proper email folder handling and a basic undelete function...
I agree with the rest. To be honest, I didn't get my Nexus new, it has had two users before me. It came with Cyanogen Mod, and to be honest I find it gives better battery life and performance compared to the stock OS. If I were you I'd try it out once you get the Nexus back.
I use ROM manager to download and install ROMs, give it a try.
Hello!
I bought Nexus 10 at nearly two weeks, and since the beginning i have noticed an issue i thought would be Software related. As the device is on idle, everything works pretty well. Watching movies, web surfing, etc. Doesn't matter if it's for 5mins or 5 hours. But when it goes to sleep mode (automatically or forced by me), it just turns off consequently. I would say 90% of the times. An then Nexus just turn back to life after a long power button press, like 10 secs or more.
First i read about some people who have problems caused by autosleep function related with some cases. When i remove my tablet from the Poetic case, it keeps going off.
Then i read about Location services. It's turned off too. Such as the wi-fi in sleep mode. Didn't solve either.
Any idea?
PS: I'm from Portugal and my English is not the best. Sorry about that.
nando_pt said:
Hello!
I bought Nexus 10 at nearly two weeks, and since the beginning i have noticed an issue i thought would be Software related. As the device is on idle, everything works pretty well. Watching movies, web surfing, etc. Doesn't matter if it's for 5mins or 5 hours. But when it goes to sleep mode (automatically or forced by me), it just turns off consequently. I would say 90% of the times. An then Nexus just turn back to life after a long power button press, like 10 secs or more.
First i read about some people who have problems caused by autosleep function related with some cases. When i remove my tablet from the Poetic case, it keeps going off.
Then i read about Location services. It's turned off too. Such as the wi-fi in sleep mode. Didn't solve either.
Any idea?
PS: I'm from Portugal and my English is not the best. Sorry about that.
Click to expand...
Click to collapse
You can view my profile for my posts I've been working on that problem for over month. Sorry this is short reply - pressed for time right now.
bigmatty said:
You can view my profile for my posts I've been working on that problem for over month. Sorry this is short reply - pressed for time right now.
Click to expand...
Click to collapse
Thanks for the response anyway.
Is that thread about freezing? My Nexus is not freezing.
Hello! Yes, that is one of the threads Im talking about. I found it to hard to find people who posted with as good of detail as you did, so I had to "latch on" to the biggest group that was vocal about their problems. But mine manifests itsself almost always as sleep of death, and NOT reboot - just like yours. Here are some links:
Google: https://groups.google.com/a/googleproductforums.com/d/msg/mobile/-/GFnACv1nC0MJ
On of the XDA: http://forum.xda-developers.com/showthread.php?t=1998496&page=39
As I say on the Google thread:
My thoughts on the error:
1) The most logical explanation I've heard yet is the memory leak that B has been posting about
2) I think this memory leak/problem can manifest its self as crash, reboot, or sleep of death
Right now I am trying Stock 4.2.2, rooted, using KTmanta kernal. This is the second day Im on a non-stock kernal, too early to post any useful info.
Good luck on this,
bm
---------- Post added at 02:09 PM ---------- Previous post was at 02:05 PM ----------
say, quick question since you are in same boat as me - does your device's serial # start with R32C or R32D?
My device is R32D.
I guess i will call the seller tomorrow and figure out if it's possible to return the tablet. At this point, it's completely unusable.
nando_pt said:
My device is R32D.
I guess i will call the seller tomorrow and figure out if it's possible to return the tablet. At this point, it's completely unusable.
Click to expand...
Click to collapse
I agree that the inability of this device to reliably stay powered on is a deal breaker, at least in a work scenario.
I actually bought mine "just for games", but have been really concerned about trying to resolve this issue to verify its not a hardware issue and I miss my warranty period. I cant honestly say I think its a harware issue, so I am really trying to find a ROM/Kernal/settings combo that resolves this.
I have a lot of faith in the dev community for ROMs and kernels, but I think its absolutely scandalous and horrible that I have to click past a warning that says 'may void your warranty' to install softare on my device to make it perform AS IT SHOULD HAVE direct from Google.
If not for all these issues I would have NEVER gone custom recovery, root, and new kernel. Im glad this has forced me to do so because Ive loved finally having a justification for "risking" my expensive device, but again that learning experience is NOT what Google is taking $500 payments for here https://play.google.com/store/devices/details?id=nexus_10_32gb so Google should be SHAMED!
Thanks for the info on your serial number, that actually relieves a concern of mine that somehow the 'newer' units werent having this problem. Mine's a C.
bm
just bought my nexus 10 yesterday. it also turning off when sleepmode. but when i update it to 4.2.2 its gone.
jamir5 said:
just bought my nexus 10 yesterday. it also turning off when sleepmode. but when i update it to 4.2.2 its gone.
Click to expand...
Click to collapse
I hope it stays that way for you. It will take a few more days with the device to know for sure. If the problem comes back it'd be worth noting here for troubleshooting. :good:
I called back the seller, and they will do the return. Really bad situation...
i left my n10 in my house and its idle with 41% on battery i just got home and open the device it consume only 1% without random reboots. hope itll stay this way ill root this and install crom maybe nextweek.
So - now I am 2.5 days into testing 4.2.2 OS with a different kernel. And so far, NO sleep of death! AND I've been using the tablet a lot more than my "minimal use" in my other tests! This of course is the ultimate test - I'm posting/talking about it on the internet so certainly if its going to blow up in my face, now would be the time. But as of right now - it looks like the alternate kernal is better for my device than Google's...
I am using the KTmanta kernel.
It is important to note that the issue described in this thread does NOT involve the device turning itself off. Rather the issue is that the device is unresponsive when in sleep mode. You can tell this is the case in a few ways, but two obvious ones are that the notification light continues to function and the device requires a 10-second power button reset (the procedure for forcibly rebooting the device).
Personally, I am on CM10.1 night lies with Ktmanta kernel and still experiencing this problem.
Bigmatty, can you tell me what governor, i/o scheduler and clock settings you are using? Thanks.
neatchee said:
It is important to note that the issue described in this thread does NOT involve the device turning itself off. Rather the issue is that the device is unresponsive when in sleep mode. You can tell this is the case in a few ways, but two obvious ones are that the notification light continues to function and the device requires a 10-second power button reset (the procedure for forcibly rebooting the device).
Personally, I am on CM10.1 night lies with Ktmanta kernel and still experiencing this problem.
Bigmatty, can you tell me what governor, i/o scheduler and clock settings you are using? Thanks.
Click to expand...
Click to collapse
Well, the majority of the complaint threads do not specifically or mainly focus on the device turning its self off, but this thread actually does.
My sleep- of- death problem on my old unit persisted on any scheduler/clock settings I tried, and I tried a lot w/ KTmanta. But it was RMA my device to get a new one that fixed my SoD.
Oh, and the LED flashing does not mean the unit is actually on, you can test that by plugging in a charger before attempting a long (power on) press = if you get instant battery charge indicator your unit was actually off.
bigmatty said:
Well, the majority of the complaint threads do not specifically or mainly focus on the device turning its self off, but this thread actually does.
My sleep- of- death problem on my old unit persisted on any scheduler/click settings I tried, and I tried a lot w/ KTmanta. But it was RMA my device to get a new one that fixed my SoD.
Click to expand...
Click to collapse
That's REALLY weird, because based on a number of findings by a number of people, it turns out that this issue is related to a bug in the GPU driver that is causing a massive memory leak. You can check by opening a Terminal Emulator and running the command "ps su" This will show the memory usage for the "surfaceflinger" application, which is where the memory leak manifests. Memory usage should never go above ~70mb for that application, but on the N10 it balloons up above ~300mb before the system locks up.
Apparently we're all waiting on Samsung to fix the problem :\
neatchee said:
That's REALLY weird, because based on a number of findings by a number of people, it turns out that this issue is related to a bug in the GPU driver that is causing a massive memory leak. You can check by opening a Terminal Emulator and running the command "ps su" This will show the memory usage for the "surfaceflinger" application, which is where the memory leak manifests. Memory usage should never go above ~70mb for that application, but on the N10 it balloons up above ~300mb before the system locks up.
Apparently we're all waiting on Samsung to fix the problem :\
Click to expand...
Click to collapse
After my two months of trouble shooting I feel strongly that there are two main issues: memory leak and "something to do with power". Likely a software/driver/OS problem on the memory leak like the majority says. BUT - not everyone has the power problems. I think the power problems are hardware related.
Only a couple other users have talked about experiencing the power problems...
If I was going to place a bet, I'd say based on your description of symptoms you too have the power problem. Ask the others in threads you are following if they have the LED thing, I'm guessing they don't.
Rxnelson on these forms does. He's seen it on two physical units. For me, it didn't appear on my second physical unit.
Good luck!!
"LED thing?" The LED thing is just the notification light continuing to flash even when surfaceflinger has locked the system. Don't really see how that's related to power in any way. The way that LED notification lights work is that the system sends an "on" signal to the LED control chip which then just runs the notification light pattern in a loop until it receives the "off" signal from the system. If you don't have any notifications prior to surfaceflinger going ballistic, or if you have the notification light disabled (many people do) you'd never notice this particular symptom.
Also please note the tip I shared about diagnosing if it's off or on via the charger I posted above, handy trick another user taught me.
---------- Post added at 01:51 PM ---------- Previous post was at 01:48 PM ----------
neatchee said:
"LED thing?" The LED thing is just the notification light continuing to flash even when surfaceflinger has locked the system. Don't really see how that's related to power in any way. The way that LED notification lights work is that the system sends an "on" signal to the LED control chip which then just runs the notification light pattern in a loop until it receives the "off" signal from the system. If you don't have any notifications prior to surfaceflinger going ballistic, or if you have the notification light disabled (many people do) you'd never notice this particular symptom.
Click to expand...
Click to collapse
Not quite what it seems. If the unit was on, plugging in the charger would not instantly,w/out delay, display the powered off charging indicator.
Ahh, okay, bit of a miscommunication. I'm not referring the power-on notification light. I'm referring to the notification light flashing that occurs when you have a notification waiting (new email, new gTalk message, etc). The charging light is something different, and not what I was referencing
NOTE: This is a function of CyanogenMOD 10.1 that is not present in the stock ROM, I think, so that may be where the confusion lies. Sorry about that
neatchee said:
Ahh, okay, bit of a miscommunication. I'm not referring the power-on notification light. I'm referring to the notification light flashing that occurs when you have a notification waiting (new email, new gTalk message, etc). The charging light is something different, and not what I was referencing
NOTE: This is a function of CyanogenMOD 10.1 that is not present in the stock ROM, I think, so that may be where the confusion lies. Sorry about that
Click to expand...
Click to collapse
Yes dude, I understand. Just test what I am saying. When I saw my white gmail led flash, but then couldn't turn on I thought the exact same thing you typed. Then while discussing w/power users someone told me to try that. Next time it happened I tried it, was SHOCKED to see what happened, knew I had a problem (that was not just shell reboot.)
My tablet just started doing this as well. It's never done it before, it started about a week ago. What could be causing this? I just factory reset to see if it'll fix the problem. I'll report back in a few days to see if this fixes the issue.
Sent from my Nexus 10 using xda app-developers app
Downloading now, clocks in at 691.01 MB
Enhanced SHIELD Hub Features
Network Test capability
User Customizable " My Android Game" and "My Media Apps"
Improved Touch Performance
Misc. Stability and Localization Improvements
Will let you know how it goes.
Do you still have root after updating? That is all I want to know before I update.
SuperSu was unable to preserve root, but Towelroot still works.
technoviking said:
SuperSu was unable to preserve root, but Towelroot still works.
Click to expand...
Click to collapse
691MB means that most likely, the update is fully wiping /system and redoing everything.
The benefit of doing a full deployment instead of a delta is that while it uses up MUCH more network bandwidth, at least it is far less likely to fail.
Screen lag is no better for me, unless I use max performance.
Sent from my SHIELD Tablet using XDA Premium HD app
This update fixes the problem of embedded Youtube videos not playing in Reddit apps and things like the Play Store.
karehaq said:
This update fixes the problem of embedded Youtube videos not playing in Reddit apps and things like the Play Store.
Click to expand...
Click to collapse
This is definitely a big plus. I wonder if Tapatalk will work after this update.
I wasn't expecting much from this update to be honest, "Misc. Stability and Localization Improvements" doesn't really give any information about what has been fixed...
I can however report that it has fixed my two biggest issues so far (admittedly this is only after two days of testing).
I haven't had a single SoD since the update compared to one every time the tablet was unused for more than two hours. This was reproducible every time on my tablet; 1:59:00 tablet would turn on without needing to do a hard reboot, 2:00:01 tablet wouldn't turn on necessitating turning it off by holding the power button for 10 seconds and then switching back on. I've now been able to turn the tablet on after leaving overnight for the last two nights
It also appears to have reduced the battery drain (maybe related to the SoD who knows...) when the tablet screen is off, instead of the battery stats showing a constant downward slope it's now a pretty much flat line while not being used overnight.
Again this is obviously early days but it's definitely made a difference to my particular tablet YMMV.
Guys, is it better to update or not? I have root and alot of games , Is this update will wipe and effect on my data?
LG G Pro2 - tapatalk
How do you block/prevent OTA updates on the Shield Tablet?
You can update whit no problem, you are not going to loose any data, but you will loose root access, but use towellrot to gain access again.
Sent from my SHIELD Tablet using XDA Free mobile app
SoD still there. This problem is killing me
What exactly is this problem ( SOC)
Sent from my SHIELD Tablet using XDA Free mobile app
rene130313 said:
What exactly is this problem ( SOC)
Click to expand...
Click to collapse
I assume you mean SoD?
Sleep of Death; the tablet won't respond to any attempts to wake via the power button after it goes into deep sleep. This used to happen to my tablet after two hours every time. The update appears to have fixed my tablet I still haven't had any issues since applying it.
Still having the weak wifi issue when holding the tablet in portrait mode at the bottom, though I'm hoping when my case arrives that will resolve the issue as it did for my iPhone 4 back in the day...
Llarrinye said:
I assume you mean SoD?
Sleep of Death; the tablet won't respond to any attempts to wake via the power button after it goes into deep sleep. This used to happen to my tablet after two hours every time. The update appears to have fixed my tablet I still haven't had any issues since applying it.
Still having the weak wifi issue when holding the tablet in portrait mode at the bottom, though I'm hoping when my case arrives that will resolve the issue as it did for my iPhone 4 back in the day...
Click to expand...
Click to collapse
Adding my case definitely helped some with the wifi drop, though didn't knock it out totally. SoD occurs quite often on my LTE replacement where it didn't happen as often on my wifi only I RMA'd. Factory resets and even no apps installed doesn't change the crashes and SoD issues. Even coming out of console mode it seems to do it 70% of the time requiring reboots to fix. Its almost comical how many crazy issues this tablet as a whole is having out the gate.
I have had zero SOD since upgrading to 1.2. Stinks that it is still happening for some though.
I think it is a hardware issue they are not admitting. I finally call NVIDIA support today to describe the lag and SOD I'm still having with 1.2 and was given a RMA without asking for one.
How do you flash the image files? I just didn't get the instructions from nvidia website. Can someone clarify everything on how to install the update using PC or using recovery? Ta..
I got nexus 4, and problem is that now and then it shuts down itself... Battery is charging ok, but after working few minutes or hours (no specific time) it just shuts down (idle or working)...
Phone is not rooted, I tried factory reset, and that didn't help either...
Currently it is on 5.0.1, I got it with this version of software so I don't know did this happen earlier on 5.0 or 4.4...
I wanted to do complete root but i'm afraid that it would shutdown itself during the process..
Does anyone knows what can be the problem??
Have you tried flashing the 5.0.1 factory image through fastboot?
Even I am facing the same problem. But for me it does not show shutting down also. It just blanks out at around 40% battery.
Had the exact same problem with my phone until I rooted the phone and changed to a non-stock rom and have not had the problem since.
Hi guys don't know if this helps because mine is slightly different. Mine is reboot itself.
My suspicion is on ram, maybe the device is out ram and then reboot itself, maybe this goes the same to shut down idk (please correct me if I'm wrong). Recently I've put gravity box and I can see how much ram left when I tap the application switcher, it was mind blowing for me. I often find that when you open several application the number of ram available can reach below 500mb (especially chrome tabs, it do have a lot of ram to use) I mean it's a 2 gb ram device wow. Every few days I've checked that when the idle ram is over a gig I do reboot manually. That way my problem of random reboot vanished. Good luck
Sent from my Nexus 4 using XDA Free mobile app
Screen will not wake from sleep
The device will randomly not wake from a sleep state, and is happening more frequently. I've read that it's possibly linked to a motherboard issue. I have root, TWRP, Xposed. Will flashing a different kernel possibly resolve the issue?
I bought an N4 from eBay and it worked perfectly for months on stock rooted Lollipop. Then it suddenly started to randomly shut down - not reboot, just a sudden buzz and "Power off". I've tried Marshmallow, Chroma, and now Cyanogenmod latest dailies. Plus a new battery (an eBay special, contacts didn't align with screws, but since another suggested fix was to leave the connection screwless that's fine - it seems to hold a charge and works fine).
So my question is - even though the power button seems to be clicky and ok, is it worth trying a new one? I know that it's mainly suggested for random reboots, but maybe it's related?
Or any other bright suggestions? Any help much appreciated.
I bought a new power & volume button and the same "power off" still happens - sometimes immediately on boot, sometimes after a period when it seems to be going ok..
Anyone have any ideas at all which hardware may be responsible? I doubt it's software, since the same happens on all ROMs, rooted or not.
I had the same issue until I reformatted all partitions and installed stock 5.1.1 Now reboots are gone. Looks like my issue was software related. The only change from stock was stability mode from Root Booster
Sent from my Nexus 4 using Tapatalk
Thanks, Hjicons. I wish I were so lucky...
As I said, different ROMS, root/no root, make no difference. It occasionally runs for a day or so, but as soon as I reboot it's back to immediate "power off".
On the plus side, it's *astonishingly* strong. I treat all my phones with kid gloves - always in a completely empty pocket, no keys or coins, in a plastic bag if there's the slightest threat of rain (even my water-resistant Nexus 6), I set them down gently on surfaces, yadda yadda yadda...
So in frustration, hoping to jar whatever component into proper life, I've banged it hard, very hard, on a mousemat, all four corners, no difference. And last night in a fury of annoyance, to stop myself pointlessly wasting time trying to fix the damn thing, I tried to smash the front glass with a heavy torch and the handle of a big screwdriver, hard enough to bring my wife in from another room to find out what the banging was. Not a scratch, not a crack. Gorilla glass is as strong as they claim it is.
But still not working...