Related
I have to say, the random reboots sucks. I am running Bamf 1.6 remix. I wiped two times, and keep getting reboots every so often. I wish someone could figure out what the heck is going on
Nobody is going to figure out what the heck is going on without any information. What are you doing when it reboots? Overclocked? If it rebooted when u are using the browser make sure you have flash installed.
dirtyfingers said:
Nobody is going to figure out what the heck is going on without any information. What are you doing when it reboots? Overclocked? If it rebooted when u are using the browser make sure you have flash installed.
Click to expand...
Click to collapse
I did over clock . Over clocking can cause that huh? I did put it back down to 1ghz and have not have any more reboots
Mine runs steady at 1.5ghz. Any higher and I get random reboot.
Sent from my rooted Bolt running VirusROM + leankernel extreme 1.92
Each phone is different. Some can handle 1.9ghz oc and others can't handle any. Also undervolting makes a processor less stable as you are running higher speeds with less power.
No, thats not a storm. Its just my Thunderbolt layin down this post.
Are you on the newest Radio? Some people are reporting that the Leaked Radio is causing the problems. I did notice that after I flashed the leaked radio. I started having random reboots.
Leaked Radio.
I for one can second that comment about the leaked radio. I've noticed a lot more reboots since flashing the new radio... especially after the 4G outage last week and changing my phone over to Rev.A. I just turned Rev.A off after the third reboot of the morning... Hopefully that will get rid of some of them. If not, I'll have to flash back. I like the better GPS locks, but they don't do much good when my phone is rebooting itself sitting on my desk.
EDIT: Didn't help. Just rebooted again. Guess I'm going back to the old radio.
herbiehusker2608 said:
I did over clock . Over clocking can cause that huh? I did put it back down to 1ghz and have not have any more reboots
Click to expand...
Click to collapse
Yes it definitely can, hopefully that fixed your problem and bamf 1.6 is a sweet ROM you should really like it.
I have had the new radio since it was released and never had a single reboot so that must not be affecting everybody. Maybe it is another factor causing reboots?
please check out my post http://forum.xda-developers.com/showthread.php?t=1094355
Not sure whats going on, it doesn't reboot and it only does it when on battery (Not plugged in) When I am using the phone, actually touching it going through menus it normally stays on but as soon as I let it sleep or anything it turns off... I have updated it and ruued it and tried different roms re-rooted.... out of ideas but currently have a phone that doesn't work as a phone as it just turns off all the time, any help would be greatly appreciated.
Sound like what many are calling the "sleep of death".
Dumb question, only having these problems when rooted and non stock ROM? So if you root, and leave it stock everything else, does it die? If you fully return to stock does it die? If so, and if it was me, Is exchange it.
If it doesn't die on the above, then:
Some phones prefer the interactiveX governor over ondemand...you can change this using speedtweak.sh on just about every kernel but ziggy's kernels. You can also try using setCPU to do it if you aren't comfortable using the terminal.
Read the thread of the ROM you are running to get more info about the kernel that its running on. The kernel devs here are usually very helpful.
courtesy of my rooted bolt
ILMF said:
Sound like what many are calling the "sleep of death".
Dumb question, only having these problems when rooted and non stock ROM? So if you root, and leave it stock everything else, does it die? If you fully return to stock does it die? If so, and if it was me, Is exchange it.
If it doesn't die on the above, then:
Some phones prefer the interactiveX governor over ondemand...you can change this using speedtweak.sh on just about every kernel but ziggy's kernels. You can also try using setCPU to do it if you aren't comfortable using the terminal.
Read the thread of the ROM you are running to get more info about the kernel that its running on. The kernel devs here are usually very helpful.
courtesy of my rooted bolt
Click to expand...
Click to collapse
I think its the opposite...I was having the same problem and a switch interactivex to ondemandx and never had a problem after that..
Sent from my ADR6400L using XDA App
Thanks for the response, and well no it always does it even on completely stock no root. The weird part is it doesn't turn off while plugged in at all... Could this be a battery issue? I have tried almost every rom on here and same thing once unplugged it will work while I'm actively using it. Then shut off as soon as I stop...
whoamanwtf said:
Thanks for the response, and well no it always does it even on completely stock no root. The weird part is it doesn't turn off while plugged in at all... Could this be a battery issue? I have tried almost every rom on here and same thing once unplugged it will work while I'm actively using it. Then shut off as soon as I stop...
Click to expand...
Click to collapse
Return your phone, it meats criteria, trying to figure it out is just going to give you a headache, your not a tech, don't try and be one. Turn it in, get a free replacement, flash away and be happy with your phone!
Sent from my TBolt using my f***king thumbs...
sonami said:
Return your phone, it meats criteria, trying to figure it out is just going to give you a headache, your not a tech, don't try and be one. Turn it in, get a free replacement, flash away and be happy with your phone!
Sent from my TBolt using my f***king thumbs...
Click to expand...
Click to collapse
It was a gifted phone purchased outright, I have no warranty through Verizon or anything, I have every intention of figuring it out.
It seems almost as if the issue is in the batter somewhere... It stays on and functions perfectly on the charger.. but once only on battery power it turns off..
sporty377 said:
I think its the opposite...I was having the same problem and a switch interactivex to ondemandx and never had a problem after that..
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
+1 You are right, got it backwards. Running a rom that I don't have to tweak finally so I'm a bit rusty.
To OP, if it does it on stock, then you might be able to get them to trade you. Unfortunately, many bolts are just bad. Good luck.
courtesy of my rooted bolt
So no thoughts on the battery thing then? These batteries do have some sort of "brain" in them right? Is there someway that could have become corrupt?
I was thinking this because it works so well on the charger, this has become a project phone for me at this point as I have acquired a G2X and get cheaper service and have 4G in my area on it anyways. So I am willing to try whatever, basically this is a very non stock phone, but atm has been RUUed to stock, and still has these issues, I have RUUed it a few times by this point.
whoamanwtf said:
So no thoughts on the battery thing then? These batteries do have some sort of "brain" in them right? Is there someway that could have become corrupt?
I was thinking this because it works so well on the charger, this has become a project phone for me at this point as I have acquired a G2X and get cheaper service and have 4G in my area on it anyways. So I am willing to try whatever, basically this is a very non stock phone, but atm has been RUUed to stock, and still has these issues, I have RUUed it a few times by this point.
Click to expand...
Click to collapse
Wipe your batt stats and find out
Sent from my TBolt using my f***king thumbs...
do you use setcpu ?
I had the same problem , so I used setcpu profiles and limitedthe CPU speed while on sleep to 3xx-4xx.
It worked for me. When it goes to 184mhz that's was my problem.
yes, wipe your batt stats.
even if it was a gift, it still has a warranty through verizon and htc that you can use. If you think the battery is bad, why not buy a cheap replacement battery on ebay/amazon?
nrfitchett4 said:
even if it was a gift, it still has a warranty through verizon and htc that you can use. If you think the battery is bad, why not buy a cheap replacement battery on ebay/amazon?
Click to expand...
Click to collapse
Well I was hoping someone else had the same issue, I am going to try and go to a vzw store today and see if I can get someone to let me use a battery for a bit to test that theory. I will post back when I find out more.
As for wiping of the battery stats for some reason clockwork just errors when I try to wipe bat stats..
whoamanwtf said:
So no thoughts on the battery thing then? These batteries do have some sort of "brain" in them right? Is there someway that could have become corrupt?
I was thinking this because it works so well on the charger, this has become a project phone for me at this point as I have acquired a G2X and get cheaper service and have 4G in my area on it anyways. So I am willing to try whatever, basically this is a very non stock phone, but atm has been RUUed to stock, and still has these issues, I have RUUed it a few times by this point.
Click to expand...
Click to collapse
I have exact same issue. I have three batteries and it does with all three. Mine too does not do it while plugged in. Tried different ROMS and Kernels and Radios to no avail. Didnt do it b4 I rooted. Started doing it when I switched to Gingerbread ROM. I am going to try going back to a Froyo and see if that helps. That is what I would suggest. I am probably going to try and put back to stock and Return. Luckily I bought at BestBuy and have warranty through them.
I'm running JT's vanilla GB [over Heimdall'ed stock EH03] on my fascinate.
I use my fascinate as my alarm clock, and I woke up this morning to a extremely choppy ringtone. < and that is is the understatement of the day.
Anyway, I try to press "dismiss" to dismiss my alarm, and it feels like the screen is not responding. I press the power button, and it takes probably like 5 seconds to complete the CRT animation. After that, I can see the screen is still on (hard to tell unless in the dark with the AMOLED), and it won't do a thing after that until I 3-button-combo or take out the battery.
As a side note, it was also doing this on my previous rom, SuperClean3 v8.1. One of the main reasons I switched back to JT's vanilla gb.
The first night the alarm worked fine. [2 days ago] Yesterday, I was watching some video files, I pressed the power button, I left for a few minutes, I came back and it was frozen. [Took foreverrrrrr for the CRT turn-on animation, and screen did not respond].
This is really really annoying, and I would really like to find out what is wrong with my phone.
One more thing I should mention.. this same kind of thing happened once in a while on the stock froyo firmware, when I bought it on craigslist. I would come to it sometimes and turn it on, and the lockscreen would show and the touchscreen wouldn't respond. I had to take the batt. out then cuz I didn't know about 3-button-combo.
The USB would only charge and not transfer files and only would charge.
So I sent it in cuz samsung said I had 1 mo. warranty left, and then they said they fixed everything in the ticked, and I got it back and it seemed to work. [the usb file transfer worked..]
So can anybody give me any advice? Like logcat? Would that tell me what is causing this problem?
Any help is appreciated!
Are your CPU settings stock? I've noticed the "sleep of death", which sounds similar to your issue, when I was undervolted too much at 100mhz.
k_nivesout said:
Are your CPU settings stock? I've noticed the "sleep of death", which sounds similar to your issue, when I was undervolted too much at 100mhz.
Click to expand...
Click to collapse
Thanks for the reply. I will look into this 'sleep of death' thing.
And I haven't edited my cpu settings. I went to superuser to be sure and the only apps listed are Superuser, Terminal Emulator, and Titanium Backup.
So I just went on a 1-hour trip, and when I got to where I was going, this happened to me again. The screen-on animation was slower than a slug on salt. 3-button-combo reset, I let it reboot, and it was fine.
I just got home 1/2 hr ago and it did it again.
Sigh.. well I only have like 2 apps that always run, 3G Watchdog and Equalizer. I've uninstalled 3G WD just to see if it does anything.
Edit: I will install ROM Manager and set the absolute minimum freq to 200mhz, and see what happens. That would make sense if it's messing up at 100mhz when the screen goes off, and then it's not able to think fast enough to up it back to 1ghz.
It sounds like it might be an issue with your phone if the problem follows you between roms and your kernel settings are stock. That is unless this is a more common issue with those roms, but I don't think they are. The sleep of death issue that I've run into before is simply the phone refusing to wake up, requiring a 3-button reset/battery pull, so I'm not sure about the slowness to respond before freezing that you've run in to.
I'd try setting the minimum frequency to 200mhz with an app like voltage control (rom manager is for rom flashing, backups/restore), maybe that would help the phone's responsiveness regarding waking up properly. I'm not sure though since when I had the sleep of death issue mentioned before, I just lessened the undervolting I had done and it seemed to resolve it. I don't have much expertise to share on your specific issue though, I'm sorry. I'd almost be inclined to believe that it might be a more phone-specific problem if you're running stock kernel settings on roms where other users haven't reported the same issue, but trying the 200mhz thing can't hurt.
k_nivesout said:
It sounds like it might be an issue with your phone if the problem follows you between roms and your kernel settings are stock. That is unless this is a more common issue with those roms, but I don't think they are. The sleep of death issue that I've run into before is simply the phone refusing to wake up, requiring a 3-button reset/battery pull, so I'm not sure about the slowness to respond before freezing that you've run in to.
I'd try setting the minimum frequency to 200mhz with an app like voltage control (rom manager is for rom flashing, backups/restore), maybe that would help the phone's responsiveness regarding waking up properly. I'm not sure though since when I had the sleep of death issue mentioned before, I just lessened the undervolting I had done and it seemed to resolve it. I don't have expertise to share on your specific issue though, I'm sorry. I'd almost be inclined to believe that it might be a more phone-specific problem if you're running stock kernel settings on roms where other users haven't reported the same issue, but trying the 200mhz thing can't hurt.
Click to expand...
Click to collapse
My bad, I meant ROM Toolbox. It has lots of apps built in including a CPU slider. Anyhow disabling 100mhz did not fix anything. So tonight I will set the minimum frequency to 800 or even 1000 mhz because I want to see if that stops the freezing up. If it does, then I'll know it's a clock speed issue.
I should also mention I sent it in for USB repair. It wouldn't connect to PC, it'd only charge. I also mentioned to Samsung it would lock up every so often from waking up. They upgraded froyo to gingerbread and said it passed all tests, sent it back, I never stayed on the firmware they gave me long enough to see if it froze up.
So on the stock roms, do they underclock the cpu frequency by default??
I don't believe that the cpu is underclocked or undervolted by default. I'd try flashing the stock firmware (EH03), and seeing if the issue happens there as well. Although I thought you mentioned it happened to you on superclean before, and I think that's just a modified stock rom? But it would be worth trying I suppose, then you could be sure it's a hardware issue and see about possibly getting a replacement. I'm assuming that you're still under warranty if you've sent the phone back recently enough for them to put gingerbread on it?
Other than that, I can't really think of anything else.. Maybe try jumping on IRC sometime and hitting up some of the people (that are generally more knowledgeable than myself) on there, they'd probably be able to give you a good idea of whether or not it's an issue with your specific phone. Although that's what it sounds like to me, I'm no expert.
k_nivesout said:
I don't believe that the cpu is underclocked or undervolted by default. I'd try flashing the stock firmware (EH03), and seeing if the issue happens there as well. Although I thought you mentioned it happened to you on superclean before, and I think that's just a modified stock rom? But it would be worth trying I suppose, then you could be sure it's a hardware issue and see about possibly getting a replacement. I'm assuming that you're still under warranty if you've sent the phone back recently enough for them to put gingerbread on it?
Other than that, I can't really think of anything else.. Maybe try jumping on IRC sometime and hitting up some of the people (that are generally more knowledgeable than myself) on there, they'd probably be able to give you a good idea of whether or not it's an issue with your specific phone. Although that's what it sounds like to me, I'm no expert.
Click to expand...
Click to collapse
Lol, when I sent it in there was like half a month or so left on the warranty, the person said it expires at the end of this month [Dec] so I figure maybe a day or two.
What's the IRC channel info? freenode?
EDIT: I forgot to ask something. So you are saying, the stock firmware [EH03 or froyo EH09] runs the cpu clock constantly at 1GHz? Even when it's sleeping? Wouldn't that give bad battery life? [lol, speaking of batteries, I just got a new one and it's charging]
I had this happen to me 6 months ago. You my friend need a replacement phone. It has nothing to do with the rom/kernal. I tried everything. Sometimes phones just take a crap. Got a replacement. Ran the same thing I ran when it was happening and haven't had a problem since. Sorry to hear. Just explain it it Verizon and see what they do.
gotsflat4love said:
I had this happen to me 6 months ago. You my friend need a replacement phone. It has nothing to do with the rom/kernal. I tried everything. Sometimes phones just take a crap. Got a replacement. Ran the same thing I ran when it was happening and haven't had a problem since. Sorry to hear. Just explain it it Verizon and see what they do.
Click to expand...
Click to collapse
This is bad news indeed, since I am not even sure how many days I have on the warranty. But I think I will Odin EH03, and then set the alarm tonight. If I wake up and it's done it again, I will call up samsung and tell them and hopefully I have warranty.
But please, tell me, when you tried to turn on the phone did the CRT animation go very slowly? and then when you pressed power, it wouldn't come on again?
Edit 2: alright! I call samsung and I have warranty until Jan 9. Woot.. So I set up an RMA with samsung, I will Odin EH03 tonight. If I wake up to a choppy alarm and a non-responsive screen, I shall send it to samsung ASAP and I hope they gimme a brand new Fascinate. that would be awesome..
Nice, glad to hear you got the warranty thing figured out. I was thinking it sounded like an issue with your phone in specific and it sounds like the other poster's experience would suggest that. Hopefully it's an issue that they can replicate and don't give you any issues getting a replacement.
To answer your question, no, the stock kernel settings wouldn't keep the processor at the highest frequency. The only way I can see that happening is if you set the screen-off profile to "performance", and I'm not sure why anyone would do that because it would indeed yield bad battery life I'd think. I'm guessing the stock kernel defaults to an "ondemand"-like profile, where it would scale the frequency according to load and favor lower frequencies or go in to a deep sleep when the screen is off.
k_nivesout said:
Nice, glad to hear you got the warranty thing figured out. I was thinking it sounded like an issue with your phone in specific and it sounds like the other poster's experience would suggest that. Hopefully it's an issue that they can replicate and don't give you any issues getting a replacement.
To answer your question, no, the stock kernel settings wouldn't keep the processor at the highest frequency. The only way I can see that happening is if you set the screen-off profile to "performance", and I'm not sure why anyone would do that because it would indeed yield bad battery life I'd think. I'm guessing the stock kernel defaults to an "ondemand"-like profile, where it would scale the frequency according to load and favor lower frequencies or go in to a deep sleep when the screen is off.
Click to expand...
Click to collapse
Oh. well the reason I asked is because you said this: I don't believe that the cpu is underclocked or undervolted by default.
So this morning, I woke up to my iPod's alarm, which I had set as a backup a few minutes after my Phone alarm should have gone off. I went to see if the phone was frozen, like I was hoping, so that it would reliably broken , but instead it was off. I turn it on, it shows the full green battery.. then it boots up like nothing was wrong. But I think that turning off randomly every night [which I assume it should do every time] is enough for Samsung to realize my phone really is screwed and that they need to do something about that.
So anyway, I printed out the label, packed my phone, and dropped my phone off at the local UPS drop off.
Hopefully I will be receiving some good news from samsung soon [i.e. that they will give me a replacement... ]
mvmacd said:
Oh. well the reason I asked is because you said this: I don't believe that the cpu is underclocked or undervolted by default.
Click to expand...
Click to collapse
Yeah, looking back on that, I misspoke. Technically, UNDERvolting/clocking is just reducing the voltage or clock speed from the "default" kernel settings. So technically, since the stock settings are the "default", they (by definition) would not be "undervolted" or "underclocked". I guess all I was trying to say is that I'm sure whatever the default settings are, they're set for a balance of performance, battery life, and stability. Just because the default max frequency is 1000mhz, doesn't mean that the CPU will stay there, that's what kernel governors are for essentially: to tell the CPU how to scale based on load (as I understand it at least).
Hopefully things go well with the replacement. Just curious, why are you dealing with Samsung directly as opposed to Verizon?
k_nivesout said:
Yeah, looking back on that, I misspoke. Technically, UNDERvolting/clocking is just reducing the voltage or clock speed from the "default" kernel settings. So technically, since the stock settings are the "default", they (by definition) would not be "undervolted" or "underclocked". I guess all I was trying to say is that I'm sure whatever the default settings are, they're set for a balance of performance, battery life, and stability. Just because the default max frequency is 1000mhz, doesn't mean that the CPU will stay there, that's what kernel governors are for essentially: to tell the CPU how to scale based on load (as I understand it at least).
Hopefully things go well with the replacement. Just curious, why are you dealing with Samsung directly as opposed to Verizon?
Click to expand...
Click to collapse
1. I'm not the original owner
2. I'm not a Verizon subscriber. PagePlus Celluar [A verizon MVNO] is my service provider. They have much better plans, including monthly, and prepaid, if you ask me.
Kernel issue.
sent from my Sensation XD
Yess..
Good news! Got an email saying my phone has been shipped:
Code:
Original Problem:
TECHNICAL INQUIRY - PHONE FREEZING / LOCKED UP - FREEZE/DELAY BETWEEN MENU FUNCTIONS
Problem found:
BAD BGA COMPONENT
Solution:
REPLACED PBA
I guess the PBA is basically the motherboard? I suppose that could have been the cause of overnight freezing, and so my phone should be fixed.
Nice.. Just 2 days left on my warranty. Cutting it kinda close, I know lol
Very well done sir
sent from my Sensation XD
I've only had this happen a few times and was wondering if anyone had this happen to them also. I'm rooted and run custom roms, it doesn't seem to be rom or kernel dependent.
For example, I had my phone on since noon and haven't really used it since then except a few times to check the time. I just pulled my phone out of my pocket and hit the power button... nothing. I held it down and it started to boot up. When this happens the battery is never dead (it was at 68% with the ext. battery this time), it just wants to turn itself off. It seems to happen when the phone is "sleeping", it's never done it when I'm actively using the phone so it's not an overheating issue.
It's not really annoying since it doesn't happen often, it just confuses me.
brando56894 said:
I've only had this happen a few times and was wondering if anyone had this happen to them also. I'm rooted and run custom roms, it doesn't seem to be rom or kernel dependent.
For example, I had my phone on since noon and haven't really used it since then except a few times to check the time. I just pulled my phone out of my pocket and hit the power button... nothing. I held it down and it started to boot up. When this happens the battery is never dead (it was at 68% with the ext. battery this time), it just wants to turn itself off. It seems to happen when the phone is "sleeping", it's never done it when I'm actively using the phone so it's not an overheating issue.
It's not really annoying since it doesn't happen often, it just confuses me.
Click to expand...
Click to collapse
still you might want to check the rom and kernel just in case, either re-flash or change.
if the problem still happens, use your warranty and get a new phone.
what rom, kernel, and recovery are you using?
I actually just happened earlier again. Got a text from a friend that she was here, so I went down and let her in, came back up and went to check my phone a few minutes later and it was off. WTF.
I'm currently using Nils newest business sense with the OC'd ICS kernel and the latest Amon Ra recovery. This used to happen on GB also so it's not a rom/kernel problem IMO.
It happens so sporadically (except for tonight apparently) that it's maybe happened 5 times since I got it on release day.
Maybe I have the governor in cpu master set too low? I have it at the lowest of 384 MHz, I've always wondered this: whats the difference between conservative and powersave?
did it happen while you were on stock GB or on a custom rom and kernel? maybe try relocking and running stock for a while and see what happens?
I honestly don't remember, it's been too long lol. It's not worth it to go back to stock and relock considering I like ICS too much.
brando56894 said:
I actually just happened earlier again.
I'm currently using the OC'd ICS kernel
Click to expand...
Click to collapse
that's the issue right there, run the stock kernel at stock speeds.
How could it be the ICS kernel when it's happened on GB also?
Which OC? I've read that the 1.8 causes random stuff like this, but 1.7 doesn't.
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
3.0.16-g4a9c8a3 SebastianFM #1 is what the kernel info says
The zip name is Overclocked_kernel_v1.20_1836_MHz_by_sebastianFM.zip
Not all phones can handle overclocking.
Mine is stable about 98% of the time, it may actually be the extended battery that is causing the issue.
brando56894 said:
Mine is stable about 98% of the time, it may actually be the extended battery that is causing the issue.
Click to expand...
Click to collapse
9x out of 10 random reboots are from either undervolting too low or overclocking too high.
I went back to the stock kernel since it seemed to be a little choppy with the oc'd kernel. That may have been the problem after all.
Sent from my Transformer TF101 using Tapatalk
I have searched our Forum for anything on this phone overheating and there is one thread that I came across, but most people did not really have this issue at all. I mean in normal usage doing pretty much nothing my phone holds at 45-50C, given that is with all four cores operating, and if I play a game the cores have reached 70C and up, I am almost certain that is simply too high for this phone to be operating at. Also, even when I use eco mode the phone still idles around 40C and will reach temps as high as 64C. I am just wondering if I am alone or people have actually tested this also and have results similar to mine. I was hoping maybe there might be potential fixes for this or would I need to get a replacement device?
Don't have a great answer for you but I can tell you the phone has some safeguards in place. One that I am aware of is the screen brightness will self-dim until the phone temp drops.
Arlington- as in TX.?
Pony Express said:
Don't have a great answer for you but I can tell you the phone has some safeguards in place. One that I am aware of is the screen brightness will self-dim until the phone temp drops.
Arlington- as in TX.?
Click to expand...
Click to collapse
Yeah, I live in Arlington, TX. Yeah, I noticed the self-dim feature, but that happens way too much, and too often, I mean I rarely get to use the phone at 100% brightness and no phone should be like that in my opinion. I am just curious if other people are dealing with similar issues, but I am checking eco mode now and my temps on idle are 36C-38C, its when I actually use my phone as a quad core phone, shocking, that it gets waaay hotter. I mean its hot on the back of the phone when I touch there and when I check the temp with an app. I feel I should be able to use my quad core as a quad core when need be, not have it get so hot its unbearable to hold, plus I don't want to do any damage with it reaching 70C temps.
Me, too in Arlington.
I would definitely say based on that it would be a good idea to exchange it, those temps are a bit much.
All og's get hot like that when playing games, etc. It is just how it is designed - like it or not / love it or leave it, lol.
I would have preferred they make the phone a little thicker with more heat sink so it could run full speed all the time when needed.
But they didn't. So, oh well. Maybe my next phone will fix that someday.
Jason
Sent from my LG-E970 using Tapatalk 2
Pony Express said:
Me, too in Arlington.
I would definitely say based on that it would be a good idea to exchange it, those temps are a bit much.
Click to expand...
Click to collapse
Darn, I was hoping for something else, ha. Oh well, guess I will be dealing with that then, meh.. By any chance could you tell me your temps you are getting? So, I know what is normal for the device?
With 5 mins. light use (wi-fi, web, phone call, 2 texts, no gameplay) 25.4 C
---------- Post added at 03:28 PM ---------- Previous post was at 03:16 PM ----------
If you are using a phone for AT&T network on T-mo, it is possible that is adding to the temp prob, not an expert here just an educated guess that the more it tries to find network signal the warmer it may get.
Pony Express said:
With 5 mins. light use (wi-fi, web, phone call, 2 texts, no gameplay) 25.4 C
---------- Post added at 03:28 PM ---------- Previous post was at 03:16 PM ----------
If you are using a phone for AT&T network on T-mo, it is possible that is adding to the temp prob, not an expert here just an educated guess that the more it tries to find network signal the warmer it may get.
Click to expand...
Click to collapse
Yes, but this happen on wifi only with data and no sim card installed, I am waiting to get an at&t sim card, lol. Shouldn't have done it online, but it cost 99 cents, instead of $15 bucks in the store.
Good call... hope it helps !!
Pony Express said:
Good call... hope it helps !!
Click to expand...
Click to collapse
Well, the strange thing is that I reverted back to stock everything, no root, or unlocked boot loader, and my overheating issue has been solved.. Weird. I only get around 35C even doing a benchmark with all four cores running at the same time. I think the Base rom and kernels still have some bugs that need to be worked out. I idle at 22C now, woot!
Glad to hear that!! Nice work.
am using the new build from Team Nocturnal with no probs. You might want to read through the thread first as some are having issues.... point is, no overheating and battery life seems good so far.
One thing I learned by testing, even going to the extent of exchanging my phone 2 days ago - if you charge your phone while it is off and unplug the charger it will drain the battery because it does not shut down the charge animation. The workaround is to simply turn the phone on and let it boot, either leave it on or then it is ok to turn off.
Pony Express said:
Glad to hear that!! Nice work.
am using the new build from Team Nocturnal with no probs. You might want to read through the thread first as some are having issues.... point is, no overheating and battery life seems good so far.
One thing I learned by testing, even going to the extent of exchanging my phone 2 days ago - if you charge your phone while it is off and unplug the charger it will drain the battery because it does not shut down the charge animation. The workaround is to simply turn the phone on and let it boot, either leave it on or then it is ok to turn off.
Click to expand...
Click to collapse
Oh wow, I did not even know that was an issue, ha, well, thanks for the heads up on that and I think I have to send my phone off to LG sadly, according to AT&T, but when I get it back I will be looking into their new base rom, I did skim the thread a little, and I am glad to hear there is no overheating. I am not sure if it was a kernel issue or the base rom itself, which is puzzling.
You may have selected Sk8's kernel during The Base's installation. I can't speak for it myself, but it's different than the stock kernel and may have been causing the problem?
Speculation at best.
No worries, Its what I am doing right now, just speculating, I mean I actually selected both kernels in the base rom, and tested them out. I was trying to figure out what the issue was. I think it might not have left me do a clean install, as I did select Sk8's Kernel first. So, I am thinking that the kernel stuck, even when I did a full wipe, before reinstalling and using the other kernel. I also was getting Kernel crashes, and it kept showing up a kernel crash screen, and asked me to go into download mode to store the dump file on my computer. I am new to android/Linux things, I am far more familiar with Windows based things, but android is the freedom OS of mobile devices. I like the customizations and things you can do with it, lol. Its sweet, and I am learning everyday, so that I can possible become a Dev later on. I have ported some things before and I know other forms of coding, just not the required programming languages for Linux.
My guess would be Sk8's kernel as well, I know it has the gpu overclocked, so if you are running graphics intensive apps it doesn't surprise me that you can be getting overheating issues.
Maybe try the bootloader unlock again to reinstall the freegee kernel...
Just a suggestion.
bleached45 said:
My guess would be Sk8's kernel as well, I know it has the gpu overclocked, so if you are running graphics intensive apps it doesn't surprise me that you can be getting overheating issues.
Maybe try the bootloader unlock again to reinstall the freegee kernel...
Just a suggestion.
Click to expand...
Click to collapse
v1:
- initial release
v2:
- added GPU OC and UV settings
v2.1
- revert GPU settings until i get them more stable
- add voltage control via sysfs (use system tuner to select your custom UV settings)
- fix the black screen issue for alot of users
v2.2
- fast_charge on usb (icon will still show as slow charge but it will actually charge faster)
- cpu tweak to enable use of all freqs in high stress times like games and benchmarks
^ That is the change log for Sk8's Kernel, the gpu isn't overclocked anymore, it was in the initial release. So, I know its not that, and as I stated in a previous post I tried both of them, but even when I wiped everything, I think that Sk8's kernel was sticking. The reason I say this is even after a fresh install and selecting Freegee Kernel during installation, when the rom booted back up it would show Sk8's Kernel, and I would get Kernel crashes, which would also lead to a Crash screen, asking me to go into download mode to save the dump file. Though even after messing with that and monitoring it for several days, its hard to tell what it was, but I do know I am not having the issues anymore when I brought everything back to stock, I can assume it was one of the kernels, a combination, the base rom, but I am not 100% sure.
Zekk98 said:
v1:
...
^ That is the change log for Sk8's Kernel, the gpu isn't overclocked anymore, it was in the initial release. So, I know its not that, and as I stated in a previous post I tried both of them, but even when I wiped everything, I think that Sk8's kernel was sticking. The reason I say this is even after a fresh install and selecting Freegee Kernel during installation, when the rom booted back up it would show Sk8's Kernel, and I would get Kernel crashes, which would also lead to a Crash screen, asking me to go into download mode to save the dump file. Though even after messing with that and monitoring it for several days, its hard to tell what it was, but I do know I am not having the issues anymore when I brought everything back to stock, I can assume it was one of the kernels, a combination, the base rom, but I am not 100% sure.
Click to expand...
Click to collapse
Shows what I know, lol.
I was going by what I read for the Base ROM Aroma installer description, maybe the Base is still using an old version, but if you installed it on your own, then you should have been the latest.
Sorry, lol.