Related
I've had my note for almost two weeks now. This afternoon, I was using it as I always do, mostly mail, some web stuff and music - thus no extended gaming, etc to overheat the GPU.
I put it in my pocket, removed it several minutes later and it was completely dead - and I couldn't even turn it back on. It wasn't banged around or anything, and there was at least 50% charge in the battery. I opened the back, removed and replaced the battery. Still nothing. I tried again about 20 minutes later, and it powered up as normal. And it has been since.
Is this weirdness that happens occasionally to current gen android phones? Anyone else have similar issues? Should I try to exchange it?
baaj said:
I've had my note for almost two weeks now. This afternoon, I was using it as I always do, mostly mail, some web stuff and music - thus no extended gaming, etc to overheat the GPU.
I put it in my pocket, removed it several minutes later and it was completely dead - and I couldn't even turn it back on. It wasn't banged around or anything, and there was at least 50% charge in the battery. I opened the back, removed and replaced the battery. Still nothing. I tried again about 20 minutes later, and it powered up as normal. And it has been since.
Is this weirdness that happens occasionally to current gen android phones? Anyone else have similar issues? Should I try to exchange it?
Click to expand...
Click to collapse
thats odd. is it stock? if not, you should list everything you did to the phone. If you had it overclocked, maybe it overheated and shut down so as not to fry the chips?
Yeah, all's still stock. I've not even rooted yet.
Same thing happened to me with a skyrocket that I had. Except I did have it rooted running sky ics rom. And I had it plugged into the charger. So...maybe not quite the same thing...sorry. lol
I just went to the store and swapped it out for a new one. No questions asked within 30 days.
Sent from my SAMSUNG-SGH-I717 using xda premium
baaj said:
I've had my note for almost two weeks now. This afternoon, I was using it as I always do, mostly mail, some web stuff and music - thus no extended gaming, etc to overheat the GPU.
I put it in my pocket, removed it several minutes later and it was completely dead - and I couldn't even turn it back on. It wasn't banged around or anything, and there was at least 50% charge in the battery. I opened the back, removed and replaced the battery. Still nothing. I tried again about 20 minutes later, and it powered up as normal. And it has been since.
Is this weirdness that happens occasionally to current gen android phones? Anyone else have similar issues? Should I try to exchange it?
Click to expand...
Click to collapse
my note did the exact same thing yesterday or day befor,, i keep it in my locker at work , any how looked at it had over 50% battery life and when i came back a few hours later , it was dead , i got it to come on but battery was way way down , no life ,, dont know what the deal was ,, but has been running fine now.
i
Just happend to me, after testing out the mhl adapter at my parents place i restarted the phone. Then once all was booted up i put it to sleep to make the drive home only 15 min away i did notice the the phone was hot in my pocket but screen wasnt on. Pulled out my phone and it didnt turn on. I pluged in the the usb and it powered up normal.
Well its a new toy, they will have bugs and they will fix them. So far so good. I did get the juice defender app, seams to be.working.out.great went all day and still had 75% power when I got home.
tapatalk ~ Samsung galaxy note
My phone does get warm from time to time (on the back right below the camera lens), though I didn't notice it before the crash. Is this heat normal?
Only thing i did have is a random reboot once...thats about it.
Galaxy Note
My only odd experience is after unplayable Asphalt 6HD for a little while, and phone does get warm. After I close the game I get nothing. Blank screen and take a few minutes to come back to life and when it does it as if it went through a soft reboot.
Sent from my SAMSUNG-SGH-I717 using XDA App
UPDATE - problem has not gone away. It seems to be (at least partially) related to a malformed battery contact. Exchanging for a new one tomorrow.
I'm a light user throughout the day. Charged my phone to 100% before I left for work today. On my way home, I used my phone a lot. I visited websites that had a lot of content. I was pinching and zooming and the phone crashed/restarted on me. Same thing happen 10 minutes later. I was using the phone for about 20 minutes non stop prior to this to happening. The phone was in the upper 50s (56%-59%). The phone was getting noticeably warm on the back cover, but not to point where it was burning hot.
This doesn't happen to me during my lunch when I use the phone non-stop for a full hour. My phone is stock, not rooted. Had for about 1 1/2 week now.
Ok. So I was at work and at the end of my shift I went to unlock my phone and nothing happeneD. I had to hold the power buttllon for like 10 seconds to get the boot screen up. Does anyone else have this problem? I'm on saurom rc4
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Do you have a min underclock frequency set? Try increasing it.
Sent from my SAMSUNG-SGH-I717 using XDA
I don't mess with clock speed at all
Sent from my SAMSUNG-SGH-I717 using Tapatalk
This sounds similar to what happened to me yesterday. Was heading to dinner, before I finished getting ready I had my phone start navigating to the restaurant and put it in my pocket. When I got in the car the screen wouldn't wake up from sleep until I pulled the battery and turned the phone back on.
markpoke1 said:
This sounds similar to what happened to me yesterday. Was heading to dinner, before I finished getting ready I had my phone start navigating to the restaurant and put it in my pocket. When I got in the car the screen wouldn't wake up from sleep until I pulled the battery and turned the phone back on.
Click to expand...
Click to collapse
That's what happens to mine except just holding the power button a couple times will reboot it. The n7000 group has the same issues I discovered after a quick google
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Mine did that too last night (saturday march 24th) I am wondering if there was an update going on because when It finally turned on (after much panic) a few programs had updated I should mention im on stock rom with no root
Mine has been doing this too. It was fine for 3 weeks, then all of a sudden it started. For me, it will happen very frequently if I use the on demand or lagfree governors (haven't tried others though). If I use smartassv2 it has only happened once in ~2 weeks. In contrast, with on demand, even with a min of 384, it happens within 10-15 locks every time now. Crazy because I ran on demand with 192 min for ~3 weeks without a single hiccup, but now it can't go 10 minutes without the sleep of death if I use those same settings. FWIW I'm on stock rom, Da G OC kernel version 0.2 now (0.1 was when 192 min was stable with on demand, though no positive the version numbers are related?). Smartassv2 seems to all but solve the issue for me, but it's not the best for battery because it runs full clock or deep sleep only, there is no in between. I really don't know the best way to try to solve the issue. I'm just staying on smartass for now. It's really a big deal for me because I use the phone as my alarm, and if it decides to do a sleep of death overnight, the alarm doesn't go off, and I won't wake up for work...
Hi, this happen to me before on my white note. I been to 3 att notes so far. First it was very laggy and screen was not that bright. i was getting 1800 in quadrant even on clean install. Took it to att store and they compare to their demos and they gave me a new one. My new white was awesome, screen was perfect and i was getting quadrant scores of 3400 almost close to my international Note which is sold for the LTE. Then after 1 week i started getting the sleep of death. it hapeen 2 times a day and then it got worse to 20 times a day. no matter what i do, stock room no app for 2 days same thing after a day it will start doing it again. I took it to att store swapped for new one. It has been 2 weeks an no screen of death, but again my phone is laggy on this new one and the screen is a bit bright, not as bright as the previous one. If you compare brightness between note ATT and note international on full brightness, the international version is beautiful on vivid colors. You can see the difference right away. it is a huge difference. I guess att disable the screen mode for vivid color on ATT note. Take it to a store and get a new one.
Oh one of the att reps on the store told me one customer had a similar issue and it was related to the sd card. He said they replace his phone 2 times and at third phone it happen again and they told him to remove the sd card and it fix itself. Now that is not the case for me. I still using my same 32GB Scandisk sd card and no sleep of death.
I'm currently running Resurrection Remix JB v3.0.9 ROM on my galaxy S2 with the 3.0.15-Siyah-s2-v4.1.5+ kernel. The performance is fine until I have been using the phone for a few hours, after which it becomes progressively slower, almost to a point where it is unusable. Eventually the screen starts to flicker and the phone switches off. I've not tweaked any performance settings. The available RAM is being maintained at a normal level throughout. I would appreciate any ideas regarding the cause of this...
I wonder if it has anything to do with the memory leak that CM10 suffers. However, it only becomes unbearable after a few days, not a few hours. Have you done the usual cache and dalvik cache wipes and fix permissions in recovery?
Sent from my GT-I9100 using xda app-developers app
I did do that when I installed the ROM yes, I had the exact same problem when I used Jelly Bam AOKP build 4 ROM. I don't recall this happening with cm10 nightlies, that used to just freeze and crash randomly instead.
Well I believe it is because of the memory leaks linked with JellyBean. Perhaps when we get source code it will be fixed.
Sent from my GT-I9100 using xda app-developers app
I've had similar flicker issues but only in my browsers book marks. I'm running the same version too, but then I had this in the previous build also.
Can't say I've had any real issues with it other than that. In fact this build has performed better than the last one fixing a few camera issues I had previously.
On the scale of things the flicker issue in my book marks is fairly small. It's otherwise running well with the rest of the management holding out quite well.
Lemontang said:
I've had similar flicker issues but only in my browsers book marks. I'm running the same version too, but then I had this in the previous build also.
Can't say I've had any real issues with it other than that. In fact this build has performed better than the last one fixing a few camera issues I had previously.
On the scale of things the flicker issue in my book marks is fairly small. It's otherwise running well with the rest of the management holding out quite well.
Click to expand...
Click to collapse
I too had flicker issue while playing videos
I decided to change to a different ROM in case this was a factor, this time ICS rather than JB so I flashed 7comp 1.3.2. The phone has been working perfectly fine but the flickering/switching off issue has just returned (1st time in 2 days, phone has been rebooted in this period), no slowing down this time, just a rapid screen flicker/dimming for a few seconds then off. When I rebooted, the battery level had fallen from 85% to 9% (common S2 issue I believe), and the flickering/switch off occured again almost immediately. Could it be related to a cpu governor or undervoltage setting? The phone is set to -50mV across the range, although I did do an extensive bench test on both cpu and gpu last night and it passed no problem. It doesn't seem to occur when doing a particular task either. Any ideas on this one would be appreciated?
elfrider said:
...the battery level had fallen from 85% to 9% (common S2 issue I believe), and the flickering/switch off occured again almost immediately. Could it be related to a cpu governor or undervoltage setting...
Click to expand...
Click to collapse
I had a brief issue with this when I 1st installed JB, (battery measurement), I just reset the battery monitoring in JB and it's been reading fine since.
Just out of curiosity, have you tried adjusting the voltage to see if this makes any difference with the flickering? I never used the ICS Resurrection version so unsure if this option is available in it.
I've reset the voltage levels to default in case this was a factor but the problem is still present. It's following a very distinct pattern now- the phone will switch off randomly without any clues that there's something wrong (no flicker or lag), it only happens when I'm using it but not when I'm doing anything in particular. I'll then reboot it, the battery will be showing near empty and the screen will then flicker within seconds of me doing something and the phone will switch off. It will keep following this pattern forever, the only way to stop it is to plug the phone in, the phone will then be perfect until I unplug it, then the screen will soon flicker and it switches off. The only way to cure it is to leave it switched off for a substantial period, then it will be fine for about a day, sometimes two. Very weird, and very annoying.
Sent from my GT-I9100 using xda app-developers app
So, Here's a little back story on my TB.
I've been rooted for over 1.5 yrs and have had no issues until this past month or so.
Running Froyo 2.2 on stock HTC. No ROMs.
Haven't changed anything and haven't loaded any games since I got my Nexus 7.
At work I leave the phone in the cradle on charge, especially when I try to use Wifi.
So the issue at hand.
It does not matter what app I use, OpenGarden, Camera, Video maybe a game or 2. Seems to be the more high end apps that cause the problem.
When I start these apps, not together, it will work for a while (on full battery) then the phone will shut down.
I'll restart and the battery will show as 1/8 to 1/5 charge.
I have changed batteries and it will still do the same shut down.
I haven't tried a restore or a re-root. Haven't touched in a long time and don't want to mess it up. I originally rooted the long method then went through the Revolutionary Easy Root and have been there ever since.
Any general ideas as to why these apps are sucking my battery dry? It is just a weird scenario and haven't found similar issues with a rooted phone.
Or should I take the plunge and get the Samsung Galaxy S III (and root with ICS)?
I really love the TB, but it is getting slow, especially compared to running apps on the Nexus 7.
Try updating to the latest ruu.
Sent from my ThunderBolt using Tapatalk 2
Thanks.
Can you point to the latest RUU and instructions?
http://www.androidpolice.com/2012/0...t-no-its-not-ics-but-it-does-fix-some-things/
Try this site. I don't know if it works or not.
Sent from my ThunderBolt using Tapatalk 2
Also can try cleaning battery terms and making sure they're all out and straight. When battery amp draw goes higher, I could see that causing the phone to freeze or reboot from amps/volts being too low. Just something to try before unrooting with an ruu...
Already checked the terminals. Happened with several batteries.
OK. So I noticed the anomalous shutdown recently and actually found what the problem was. I had installed Ninja Royale and Blood Brothers, but never actually ran them since I've been running them on my Nexus7.
On the N7 I was noticing short jumps to the start splash screen of these games during game play. So I decided to UnInstall them from the TB and now no longer have any random shutdowns or battery crunch and reboots.
Might be a combination of Froyo on the TB and a newer game, but this seems to have worked.
The N7 seems to be able to handle the load and the jumpi-ness of the splash screen and the battery holds up as well.
So, my fix was to uninstall Ninja Royale and Blood Brothers from the TB to fix the reboot issue.
I was having similar problems. Ended up replacing the battery.
Earlier i mentioned about random restarts on my desire x. The unusual thing about these restarts was that they never occurred when i was looking at screen, instead they occured ONLY when phone was idle. NEVER occured while watching youtube, browsing, playing games etc even for prolonged sessions. These restarts ALWAYS happen 100% times on using wifi hot spot within 30 minutes.
Now here is the thing i did this morning, I downloaded "aLogcat" and let it run continuously in background. And now i am using hot spot since last 4 hours and voila. No restarts . I guess whenever CPU found itself idle it would restart or freeze?(dunno, strange behavior)
I would rule out hardware malfunction here for two reasons? -
1) The phone worked perfectly fine for 5 months after purchase.
2) These restarts started happening few days after i updated to latest software.
What do you guys think.?
have you tried to setup minimum cpu frequency via for example no frills control to some higher one?
mindlesSheep said:
have you tried to setup minimum cpu frequency via for example no frills control to some higher one?
Click to expand...
Click to collapse
No, my phone is not rooted. will it work on unrooted.
Update- its been 7 hours without a restart. touchwood.
no it wont... and id recomend not to root it while its suffering from random rebooting, try warranty service
mindlesSheep said:
no it wont... and id recomend not to root it while its suffering from random rebooting, try warranty service
Click to expand...
Click to collapse
Yeah i would not