So I just went off of paranoid AOKPdroid because I was getting random reboots. But it was not the normal random custom rom reboots that you get.
When ever the device would get bumped it would reboot. So say, a small bump in the car, or the phone gets tossed onto the bed after a days work. It would do it when booting, when in CWM, and when in the rom itself.
I same issue would occur on tasks aokp rom as well. I've gone back to full stock, and unrooted the device. I was almost positive that it was hardware, thus me going back to stock for a warranty.
But now, on stock, I have not gotten the device to reboot when it gets bumped. Now I'm getting really strange behavior in stock (fcs on basic apps, Facebook, pandrow, ect.. Browser locking up, screen not always coming one) am I crazy? Can a custom rom really throw reboots when bumped? Or does this seem like a hardware issue...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Theoretically, yes it could be related to the rom and its drivers for things like the accelerometer. But since your getting the strange behaviour (even though not bump reboots) it does sound likely you may be having a hardware problem.
So you would recommend going with a warranty?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Everything you've mentioned sounds to me like its hardware related. I would get a replacement if you're able to.
task650 said:
Everything you've mentioned sounds to me like its hardware related. I would get a replacement if you're able to.
Click to expand...
Click to collapse
I have been running paranoidkangdroid a while never had anything like that happen and don't know anyone who has. Reset counter and flash stock for warranty send in. Sounds like its a problem with your phone.
AT&T SGS3
ParanoidKangDroid 1.1.0 ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter
Dankest said:
I have been running paranoidkangdroid a while never had anything like that happen and don't know anyone who has. Reset counter and flash stock for warranty send in. Sounds like its a problem with your phone.
AT&T SGS3
ParanoidKangDroid 1.1.0 ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter
Click to expand...
Click to collapse
Thanks for the help! Sadly the phone is through a corporate account. So I have to him the boss call into ATT to get a new on sent out. This is going to be fun. For now I'm still using the stock rom on the phone, and I've been reminded how horrible it is compared to all the AOKP roms I've used...
TopHATTwaffle said:
Thanks for the help! Sadly the phone is through a corporate account. So I have to him the boss call into ATT to get a new on sent out. This is going to be fun. For now I'm still using the stock rom on the phone, and I've been reminded how horrible it is compared to all the AOKP roms I've used...
Click to expand...
Click to collapse
Yikes, can't imagine being stuck with ICS stock again
AT&T SGS3
ParanoidKangDroid 1.1.0 ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter
Related
Everything has been perfect with this phone except now I've had two reboots in the past two days and I'm considering swapping it for a new handset (could be indicative of a larger problem). Yesterday it rebooted when I was browsing the internet, it had 70% battery before the reboot and then the phone was reporting 15% right after. I did a battery pull and it came up to 40% after. Weird. Anyone else have any issues like this?
Sent from my SPH-D710 using XDA App
No issues here. Phone works flawlessly for me under heavy use.
sent from my DAMN phone!
never happened to me either...fully stock, never rooted
If it happens to you again, if you are within the return window, you may want to exchange it
Yep... watch this youtube.com/watch?v=8pMLxyThxEk
what a piece. And sprint is no help. Not in person. Not "Dan Hesse's Office"
That doesn't sound right at all. I haven't had a single one..not even when messing around overclocked to 1.6
Sent from my SPH-D710 using xda premium
Happened to me every time I tried to uninstall/go into parts of the phone. Happened a Month ago, dida format stock...all okay like nothing happened.
-jr
Ps, it was after phone got easy too hot using hdmi out for over 3 hours...I believe the phone was well above the 125°, as o could not touch it.
Sent from my SPH-D710 using Tapatalk
Never had the problem when it was stock...if anything, it did drain the battery a bit. But that's expected.
tubasteve said:
Happened to me every time I tried to uninstall/go into parts of the phone. Happened a Month ago, dida format stock...all okay like nothing happened.
-jr
Ps, it was after phone got easy too hot using hdmi out for over 3 hours...I believe the phone was well above the 125°, as o could not touch it.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I have been told that the phone will shut itself down to prevent heat damage.
Sent from my SPH-D710 using xda premium
I havent had a single one since I posted this thread. I'm thinking it was a fluke. My phone runs like a champ now, especially since I rooted and used autostarts and titanium to get all the bloat under control.
Wait... people on here that don't root? I'm confused...
subcypher said:
Wait... people on here that don't root? I'm confused...
Click to expand...
Click to collapse
At the time I posted this thread I was still waiting for a way to root my current ROM, with no flashing involved. With all the problems that people were having with LOS I didn't want to risk flashing a new kernel and potentially starting to get LOS when I never had it before. I still haven't had a single one and I got this phone on release day
Well, thanks to a FUBAR with the CIQ removal script and no backup, I moved away from stock. I'm now running Calkulin's and haven't had any LOS or random reboots. At least, that's what I'm running while I patiently wait for CM9. That being said, I recommend it.
subcypher said:
Well, thanks to a FUBAR with the CIQ removal script and no backup, I moved away from stock. I'm now running Calkulin's and haven't had any LOS or random reboots. At least, that's what I'm running while I patiently wait for CM9. That being said, I recommend it.
Click to expand...
Click to collapse
Yeah I had the same FUBAR lol. I ended up using odin to go the EG31 route. I really feel no desire to go with a custom ROM. Back in the EVO days the stock ROM was always so bloated even with just Sense that you HAD to go custom to get any performance or decent battery life out of it. The stock ROM on our E4GTs just blazes and is damn near perfect already. The only thing left for me to do is get rid of CiQ and then it will be absolutely perfect. I have the odexed version of the noCiQ mod waiting to be flashed but I'm 1000 miles from home for the next few weeks and can't risk screwing up my phone. I only brought my macbook with me so using odin in case of a fowl up is not an option right now.
_MetalHead_ said:
Yeah I had the same FUBAR lol. I ended up using odin to go the EG31 route. I really feel no desire to go with a custom ROM. Back in the EVO days the stock ROM was always so bloated even with just Sense that you HAD to go custom to get any performance or decent battery life out of it. The stock ROM on our E4GTs just blazes and is damn near perfect already. The only thing left for me to do is get rid of CiQ and then it will be absolutely perfect. I have the odexed version of the noCiQ mod waiting to be flashed but I'm 1000 miles from home for the next few weeks and can't risk screwing up my phone. I only brought my macbook with me so using odin in case of a fowl up is not an option right now.
Click to expand...
Click to collapse
I know what you mean, man. But once you're rooted and have Clockwork on there, you can do Nandroid backups and flash right from your SD card! But, hey, safe journeys.
subcypher said:
I know what you mean, man. But once you're rooted and have Clockwork on there, you can do Nandroid backups and flash right from your SD card! But, hey, safe journeys.
Click to expand...
Click to collapse
Oh I'm aware. I still do nandroids just in case now but honestly, stock ROM+removed bloat + autostarts is awesome.
I used to be flash happy when I had my EVO, I flashed new ROMs all the time (and always ended up back at MIUI). With my E4GT I just want it to work with no problems and I'm happy.
I'm stock too. I did the whole flash everything under the sun with my evolution and evo 3d and other phones. Ill root and flash when cm9 is stable. I had one radom reboot once but I think it was an app issue.
Sent from my SPH-D710 using xda premium
What roms are those of you who arent crazy (aka those on ICS) using (aka those still using gingerbread roms). Having some odd problems with my rom im on currently, so im looking to see whats still good (Seeing as things havnt been updated for a while).
Check out Blazer ROM, and Calkulins ROM.
cds0699 said:
Check out Blazer ROM, and Calkulins ROM.
Click to expand...
Click to collapse
Ahh is blazer still being update? or atleast updated since the beginning of this year? and as far as calks gingerbread rom, i wasnt a fan. to many tweaks that caused random issues for me ( think it had to do with some of the powersaver scripts and whatnot). But yeah if blazer is still smooth and awesome i might give that a try.
HaiKaiDo said:
Ahh is blazer still being update? or atleast updated since the beginning of this year? and as far as calks gingerbread rom, i wasnt a fan. to many tweaks that caused random issues for me ( think it had to do with some of the powersaver scripts and whatnot). But yeah if blazer is still smooth and awesome i might give that a try.
Click to expand...
Click to collapse
Im on blazer 4.0 smooth as butter
Back from my "scotsman vacation"
Bear gri11z said:
Im on blazer 4.0 smooth as butter
Back from my "scotsman vacation"
Click to expand...
Click to collapse
holy crap blazer 4.0 DOES look awesome. Thanks guys. Totally goin to blazer
On Blazer 3.5 and FB27 modem.
HaiKaiDo said:
Ahh is blazer still being update? or atleast updated since the beginning of this year? and as far as calks gingerbread rom, i wasnt a fan. to many tweaks that caused random issues for me ( think it had to do with some of the powersaver scripts and whatnot). But yeah if blazer is still smooth and awesome i might give that a try.
Click to expand...
Click to collapse
Yep, last updated February 20th.
Blazer 4.1
Too sexy
iSaint said:
Blazer 4.1
Too sexy
Click to expand...
Click to collapse
Show off........ Lol
iSaint said:
Blazer 4.1
Too sexy
Click to expand...
Click to collapse
your old siggy was much more sexy
I didn't realize ics was bricking phones. I've been going to and from ics since the initial release. I think it's more that people are just being careless and not paying attention to what they are doing *or* they are doing something like using rom manager or touch recovery. Which if you haven't heard, DO NOT USE EITHER OF THESE ON OUR PHONES.
What I've learned through out my time flashing is:
1. Use the one-click ODIN+Root+Data Wipe for EL29 (Latest GB release).
2. If a custom recovery is required, wait for one to be created which matches the current build you have, ex. FB21 + FB21 Repack w/CWM. Usually the dev's are pretty good at getting one put together.
3. Do not restore back ups, ever. I repeat EVER.
4. Make sure all the drivers are installed before doing anything. (Samsung Kies, etc.)
5. If you need to get custom recovery for EL29, use the AutoRoot stickie, which has a 100% success rate.
6. Wipe, Wipe, Wipe, and more Wipe. I can't repeat that enough, but make sure you wipe every chance you get. Hell, wipe before flashing, after flashing, flash again, etc.
I keep the majority of my apps on Dropbox, and have my contacts synced through Exchange (Sprint server).
I have yet to brick a phone.
Strongsteve's rom. Nothing else need be said.
Up and comming Arts forum http://little-melon.com/Forum
I made a full thread on how to prevent bricking your phone when using ICS roms, it's perfectly fine to use ICS as long as you don't get careless, heres my thread
http://forum.xda-developers.com/showthread.php?t=1525495
Freeroot said:
I didn't realize ics was bricking phones. I've been going to and from ics since the initial release. I think it's more that people are just being careless and not paying attention to what they are doing *or* they are doing something like using rom manager or touch recovery. Which if you haven't heard, DO NOT USE EITHER OF THESE ON OUR PHONES.
Click to expand...
Click to collapse
Well i would have to disagree with this. I was in the dev irc when the first bricks happened. Including sbrissen, a few of his testers and then recently steadyhawking (who obviously got another phone already). Has nothing to do with carelessness, theres just some problems with the process as a whole right now.
xST4T1K said:
I made a full thread on how to prevent bricking your phone when using ICS roms, it's perfectly fine to use ICS as long as you don't get careless, heres my thread
http://forum.xda-developers.com/showthread.php?t=1525495
Click to expand...
Click to collapse
Until I hear from Steady or sbrissen that the issue is completely gone. I appreciate the effort, but since we dont know EXACTLY what it is (hell there could be even more things that we dont know that are causing it) no ICS for this guy.
PS: You should add rouge recovery to the list of bricks suspects. Thats how steady bricked his phone the other day. he was in his own recovery and it still did it.
HaiKaiDo said:
Well i would have to disagree with this. I was in the dev irc when the first bricks happened. Including sbrissen, a few of his testers and then recently steadyhawking (who obviously got another phone already). Has nothing to do with carelessness, theres just some problems with the process as a whole right now.
Until I hear from Steady or sbrissen that the issue is completely gone. I appreciate the effort, but since we dont know EXACTLY what it is (hell there could be even more things that we dont know that are causing it) no ICS for this guy.
PS: You should add rouge recovery to the list of bricks suspects. Thats how steady bricked his phone the other day. he was in his own recovery and it still did it.
Click to expand...
Click to collapse
WOAHH. I had no idea steady bricked his phone. I knew t.c.p. did. This adds a new dimension to this thing.
HaiKaiDo said:
Well i would have to disagree with this. I was in the dev irc when the first bricks happened. Including sbrissen, a few of his testers and then recently steadyhawking (who obviously got another phone already). Has nothing to do with carelessness, theres just some problems with the process as a whole right now.
Until I hear from Steady or sbrissen that the issue is completely gone. I appreciate the effort, but since we dont know EXACTLY what it is (hell there could be even more things that we dont know that are causing it) no ICS for this guy.
PS: You should add rouge recovery to the list of bricks suspects. Thats how steady bricked his phone the other day. he was in his own recovery and it still did it.
Click to expand...
Click to collapse
Completely understandable, I would add it but the only problem is there is no way of knowing what he was doing when it bricked, an action has to be done for a phone to brick and without knowing that action I can't say "don't use rogue" or people would think I'm an idiot and nobody would be on ICS if that were the case, but I've been using ICS since the leaks came out and never had an issue once following my own guide (using rogue everytime btw).
xST4T1K said:
Completely understandable, I would add it but the only problem is there is no way of knowing what he was doing when it bricked, an action has to be done for a phone to brick and without knowing that action I can't say "don't use rogue" or people would think I'm an idiot and nobody would be on ICS if that were the case, but I've been using ICS since the leaks came out and never had an issue once following my own guide (using rogue everytime btw).
Click to expand...
Click to collapse
I agree with you and I haven't had any problems either. and I mean since fb09 all the way to the current calk build. If Steady did actually brick his phone like the guy says, then there is probably some other reason that we are unaware of. Steady seems to have a pretty good grasp on what he's doing. That kinda scares me, but I have yet to find where he posted about bricking his device or a warning to stay away from ics or something along those lines :skeptical:
xST4T1K said:
Completely understandable, I would add it but the only problem is there is no way of knowing what he was doing when it bricked, an action has to be done for a phone to brick and without knowing that action I can't say "don't use rogue" or people would think I'm an idiot and nobody would be on ICS if that were the case, but I've been using ICS since the leaks came out and never had an issue once following my own guide (using rogue everytime btw).
Click to expand...
Click to collapse
lol no one would think youre an idiot. Just mention that rouge recovery also runs the risk of bricking and refer anyone that doesnt believe you to steady's bricked phone .
PS: Steady used to brag to me that he used his recovery constantly to flash back and fourth to ICS...and then bricked
After all the playing around I did with ICS, I had to switch back due to the GPS issues and needing it to work for a road trip. I have no idea what bit of flashing/odin magic I did but I have Calkulins ROM running better than I've ever seen - UI is so snappy. I know it's a stock rooted kernel, but I'm not sure about the modem. Is that under "baseband version"?
I have been using Gnex for the last 2 months flashed cm9-10 nightly since i bought it.
it was working just fine altho it got hot when playing games or on a call i didnt care since its very usual for smartphones.
but last night, i was playing a game on it and it the phone just got frozen.
and after a few seconds it rebooted itself and it got into bootloop.
i tried to connect usb and reboot into recovery mode to just have a nand backup but my pc didnt recognize the phone.
then i decided to remove the battery wait until the phone gets cool
after the phone cooled down i put the battery back and turned it on. and it just booted with no problem.
i ran the game again and it just froze again. then i had to repeat the steps above.
i was listening to music on my way to work this morning, it didnt have any problem.
and i tried the game it froze again :crying:
anyone having the same issue?
or if its just me having this issue, can i get it repaired from the official samsung repair centre since its bootloader unlocked and rooted..
-------
added: just flashed cm10-20120910 nightly while the phone as upgrading the apps it just froze again :crying:
lovegu said:
I have been using Gnex for the last 2 months flashed cm9-10 nightly since i bought it.
it was working just fine altho it got hot when playing games or on a call i didnt care since its very usual for smartphones.
but last night, i was playing a game on it and it the phone just got frozen.
and after a few seconds it rebooted itself and it got into bootloop.
i tried to connect usb and reboot into recovery mode to just have a nand backup but my pc didnt recognize the phone.
then i decided to remove the battery wait until the phone gets cool
after the phone cooled down i put the battery back and turned it on. and it just booted with no problem.
i ran the game again and it just froze again. then i had to repeat the steps above.
i was listening to music on my way to work this morning, it didnt have any problem.
and i tried the game it froze again :crying:
anyone having the same issue?
or if its just me having this issue, can i get it repaired from the official samsung repair centre since its bootloader unlocked and rooted..
-------
added: just flashed cm10-20120910 nightly while the phone as upgrading the apps it just froze again :crying:
Click to expand...
Click to collapse
What game are you exactly talking about?
kyokeun1234 said:
What game are you exactly talking about?
Click to expand...
Click to collapse
Its a game called "ani pang" like bejeweled blitz but with animals instead of jewels.
well the game is not the only thing freeze the phone but it freezes whenever it gets overheated.
just like the upgrading process after flashing ..
lovegu said:
Its a game called "ani pang" like bejeweled blitz but with animals instead of jewels.
well the game is not the only thing freeze the phone but it freezes whenever it gets overheated.
just like the upgrading process after flashing ..
Click to expand...
Click to collapse
Does any other games freeze too when it gets hot?
kyokeun1234 said:
Does any other games freeze too when it gets hot?
Click to expand...
Click to collapse
yes..
lovegu said:
yes..
Click to expand...
Click to collapse
Could you explain how hot it gets? My phone gets super hot but that never happened...
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
kyokeun1234 said:
Could you explain how hot it gets? My phone gets super hot but that never happened...
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
it doesnt get really hot, its just the temperature that the phone normally gets when you are on a phone call for few minutes
This is really odd indeed... did you try wiping, re-flashing, or trying a different Rom?
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
kyokeun1234 said:
This is really odd indeed... did you try wiping, re-flashing, or trying a different Rom?
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
im thinking its the problem with the hardware since it reboots in recovery mode..
lovegu said:
im thinking its the problem with the hardware since it reboots in recovery mode..
Click to expand...
Click to collapse
Then it's probably hardware. Send it to Samsung since this isn't what you've done and warranty will cover it. How long can recovery more last until it reboots? Since you need it to convert it to stock
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
kyokeun1234 said:
Then it's probably hardware. Send it to Samsung since this isn't what you've done and warranty will cover it. How long can recovery more last until it reboots? Since you need it to convert it to stock
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
well it depends sometimes it just reboots straight away
sometimes it allows me to flash other roms.
can i still re-lock like when i first bought it? thats the thing im worried now as im thinking of going to Samsung this weekend
lovegu said:
well it depends sometimes it just reboots straight away
sometimes it allows me to flash other roms.
can i still re-lock like when i first bought it? thats the thing im worried now as im thinking of going to Samsung this weekend
Click to expand...
Click to collapse
you can still re-lock it, but they would know that you rooted since you'll still have the custom ROM flashed on it.. Hopefully you'll have enough time to flash stock ROM, recovery, boot.img, userdata and etc..
kyokeun1234 said:
you can still re-lock it, but they would know that you rooted since you'll still have the custom ROM flashed on it.. Hopefully you'll have enough time to flash stock ROM, recovery, boot.img, userdata and etc..
Click to expand...
Click to collapse
thanks for the replies, ill update after i go to the repair center
lovegu said:
thanks for the replies, ill update after i go to the repair center
Click to expand...
Click to collapse
OK, I'll pray for you
been to samsung service center last saturday,
they are going to change the mother board and send it to me XD
hopefully everythings fixed when i get it
Happened to me too. I suggest under clocking it. Then turn the screen off for 5 mins then it will cool down.
~Sent from my Galaxy Nexus VZW
Is there a way to fix the dark spots that appear on the screen when you are in a dark room? I know it's a common issue with amoled screens but I hate how it looks.
You should Google search this there is a million threads on this topic
Sent from my Galaxy Nexus
I have but I didn't find a fix for it. I just found a lot of threads of people complaining.
Capt said:
Is there a way to fix the dark spots that appear on the screen when you are in a dark room? I know it's a common issue with amoled screens but I hate how it looks.
Click to expand...
Click to collapse
As far as I know, there is no fix, and Samsung won't take it back for warranty because its a problem across all super amoleds. they should be less noticeable as time goes on. I had a few but now I don't really notice them anymore, if you purchased your phone in the last month take it to your carrier I'm sure if you plead your case they will exchange it.
AT&T SGS3 Marble White
ParanoidKangDroid 1.4 ROM
KT747 11/13 OC'ed & UV'ed
Medical Marijuana Supporter
I just got the phone and I'm hearing that all galaxy s3 phones have this issue. I don't think it's even worth replacing it since it will have the same issue.
Capt said:
I just got the phone and I'm hearing that all galaxy s3 phones have this issue. I don't think it's even worth replacing it since it will have the same issue.
Click to expand...
Click to collapse
Yep. I have two small dots, guess I came out more lucky than some.
AT&T SGS3 Marble White
ParanoidKangDroid 1.4 ROM
KT747 11/13 OC'ed & UV'ed
Medical Marijuana Supporter
I rooted my s3 and I'm just curious when I get the ota update for jellybean that's coming around early december(I hope), what would happen if I updated it when root is installed?
You lose root, because the update isn't rooted (most likely).
Will anything bad happen? Like force closes and etc.
Shouldn't, but since it's not happened yet, it's hard to tell.
Jason_Nguyen said:
Will anything bad happen? Like force closes and etc.
Click to expand...
Click to collapse
That all depends on att they could have a hiccup like nexus devices where they forget December or something. Its all on their end as far as error and bugs. Seeing as how long its taken them to announce they are probably not going to release until jellybean is bug free.
AT&T SGS3 Marble White
Team AoCP 4.6 The Collective ROM
Medical Marijuana Supporter
In all likelihood you should be fine. As others have said here, it should be pretty bug-free. And you will lose your root, but it's not that difficult to root again. It's pretty much just what it sounds like, restoring to stock Touchwiz. At least the JellyBean update will include some tasty new features too.
I'd reccomend waiting the few hours it will take to get the root of the OTA.
£¢