Hi. My phone often turns off since I flashed official Gingerbread (2.3.3) ROM.
When it turns off, I'm usually using it. Till now it never turned off at stand-by mode. Does anyone know, what causes this?
Other things:
1. When I played FIFA 10, the football field's textures weren't showing, but everything with field's players was fine.
2. When I ran Quadrant Advanced, at "3D Corridor" and "Planets" there were no textures. When I run the Standard version of this app, there are no problems.
Maybe gpu is cooked?
For starters, tune down your overclocking.
Ok, I'll try it and then I'll say, did it work or not.
You are probably going to seriously eff up your phone at that high overclock. It might even burn/damage the inside circuits if you're not in a really cold country.
Siddhesh222 said:
You are probably going to seriously eff up your phone at that high overclock. It might even burn/damage the inside circuits if you're not in a really cold country.
Click to expand...
Click to collapse
I just clocked CPU to 245/710 MHz, I had 787 MHz max. But anyway, before I flashed official 2.3.3 ROM, there wasn't a problem like that.
EDIT: I installed NFS Shift game to see, how are the 3D graphics working. When I tried to enter this game, I couldn't get further than EA Games logo - the game powered down and I had brought to the homescreen.
I can't fix this issue by installing another ROM, right? ... It's related with hardware.
You can always brick ur phone and replace the hardware with warranty..
ccdreadcc said:
You can always brick ur phone and replace the hardware with warranty..
Click to expand...
Click to collapse
Yeah,LG replaces your PCB circuit in 1/2 days AFAIK so I would like to risk too and flash new baseband but I'm going away in about 4 days (@ the beach ) can't risk
Thank you, guys. I'll go to the shop where I bought this phone and will ask about warranty.
Thanks again.
UP!
So, I didn't repair my phone with warranty, I only flashed stock Froyo with KDZ updater and everything was solved.. but.. I still have this problem with ROMs that are based on official Gingerbread (also with official GB, that's not modified) and with CM7 by mik (only with build 6.6.1)..
Can someone try to play NFS Shift on official GB (or a ROM, based on it) and answer here - is it working or not.
(for me it crashes after EA logo)
well, I count it as a .35 kernel issue..
What do you think?
I've tried it a while back (when it was €0.99) on stock firmware and couldn't get any further either. Got a refund, so I can't retest it on the CM7/mik I'm running now, but it could very well be a general issue.
Hans Schmucker said:
I've tried it a while back (when it was €0.99) on stock firmware and couldn't get any further either. Got a refund, so I can't retest it on the CM7/mik I'm running now, but it could very well be a general issue.
Click to expand...
Click to collapse
I see...
So, currently for me the best choice is mik's CM7 build6.5.7 (uses .32 kernels) + fk v18.
I leave that entirely up to you... I just want to protect you from trying different ROMs in search of one that is able to run NFS, when it may very well impossible
Hans Schmucker said:
I leave that entirely up to you... I just want to protect you from trying different ROMs in search of one that is able to run NFS, when it may very well impossible
Click to expand...
Click to collapse
yeah, so ROMs that are based on froyo (or .32 kernel) are the most stable.
never got NFS Shift to work on 2.3.3 ROMs.
(actually I don't play this game, but with it I can see, how is the ROM working)
that's my conclusion.
btw, haven't your phone have the problem with automatic turning off in GB?
thank you for responsiveness.
Sorry, the only screen-turning-off phenomenon I see on CM7 is the one I see when I use Skype... hate that darn proximity sensor
As for stability... well, it could just mean that NFS works on a bug-assumption that has been fixed in the meantime. Wouldn't be the first time.
Hans Schmucker said:
Sorry, the only screen-turning-off phenomenon I see on CM7 is the one I see when I use Skype... hate that darn proximity sensor
As for stability... well, it could just mean that NFS works on a bug-assumption that has been fixed in the meantime. Wouldn't be the first time.
Click to expand...
Click to collapse
sry, but i didn't mean screen turning off - phone is turning off.. it just immediately turns off, but this happens only when I use it.
Ah! ... sorry, no idea aside from the usual: Do you overclock? Do you have a lot of applications on SD? Do you use a task killer that may be over-eager? Have you checked your memory stats?
droidaem said:
sry, but i didn't mean screen turning off - phone is turning off.. it just immediately turns off, but this happens only when I use it.
Click to expand...
Click to collapse
too much oveclocking indeed..
yeah, the phone was overclocked always. at beginning @787 mhz, then 729,and after that 768
on sd I move applications only then if they are bigger than 10 Mb (sometimes I don't if there is enough free space in phone's memory).
don't use task killer anymore. I used it earlier, but understood that there's no point of this.
I don't check my memory stats, but do I have to?
You shouldn't have to ... but if the phone crashes then at least something isn't working like it's supposed to, meaning anything is possible. You can get your memory stats with cat /proc/meminfo .
Have you tried running the fix permissions function in ClockworkRecovery? It never worked with any of the issues I had, but it's worth a shot.
Related
I love this phone, its really the best phone money can buy @its price.
But like allways, there must be something there that must drive us/me crazy.
This phone losses 30% of its "beauty" because of the "touchscreen pushed makes CPU go to 100%" , losses another 40% for the "buttons working but the touchscreen freezes" bug and It wont unfreeze until you do a "lock and swipe unlock" .
So untill this phone gets an official update that fixes all the problems above (2.3, or 2.2 or 2.2.1, really dont care", I'm using this beauty just as a phone (30% calls and sms).
Additional notes: till now i've tried Pimev2 and now runing void (Thanks for your work Noejn).
What do you guys think about this ?
Kel_Sceptic said:
I love this phone, its really the best phone money can buy @its price.
But like allways, there must be something there that must drive us/me crazy.
This phone losses 30% of its "beauty" because of the "touchscreen pushed makes CPU go to 100%" , losses another 40% for the "buttons working but the touchscreen freezes" bug and It wont unfreeze until you do a "lock and swipe unlock" .
So untill this phone gets an official update that fixes all the problems above (2.3, or 2.2 or 2.2.1, really dont care", I'm using this beauty just as a phone (30% calls and sms).
Additional notes: till now i've tried Pimev2 and now runing void (Thanks for your work Noejn).
What do you guys think about this ?
Click to expand...
Click to collapse
About touch-100%-CPU-problem - this problem have many devices, but unfortunately, as other phones have about 50% CPU when screen is touched, optimus have 100%. Anyway, this main problem should be fixed in 2.3 android release.
About buttons-working-but-the-touchscreen-freezes problem I have to say, sorry. I didn't notice this problem at all.
And at the end I would like to add ARMv6-CPU, which brings too many limitations, one of the worst is Flash player support, which we will never see
who needs flash for phone, flash lite is enough...
The_ERROR said:
And at the end I would like to add ARMv6-CPU, which brings too many limitations, one of the worst is Flash player support, which we will never see
Click to expand...
Click to collapse
Some of the guys working/testing on the CM7 port say that flash works. Have you tried it?
I tested the ROM, but I can't seem to get an IP address from the router, so I can't install Dolphin to test flash
EDIT: And oh. So I could be of any help to this thread, I checked to see if the touchscreen cpu thing still exists, and yes, it's still there. Sorry :/
How could you figure that out since there are no 3d drivers and everything is supported by CPU ? I really hate it when somebody talks crap..
Sent from my LG-P500 using XDA App
The_ERROR said:
About touch-100%-CPU-problem - this problem have many devices, but unfortunately, as other phones have about 50% CPU when screen is touched, optimus have 100%. Anyway, this main problem should be fixed in 2.3 android release.
Click to expand...
Click to collapse
This has been fixed thanks to mok_os and his fine work
The_ERROR said:
About buttons-working-but-the-touchscreen-freezes problem I have to say, sorry. I didn't notice this problem at all.
Click to expand...
Click to collapse
I've made a video with how my touchscreen reacts when its stressed with multi touched
Kel_Sceptic said:
This has been fixed thanks to mok_os and his fine work
I've made a video with how my touchscreen reacts when its stressed with multi touched
Click to expand...
Click to collapse
why are expecting so much from a budget phone??
be satisfied with wat u have, its jst a phone :|
OK, so I'm on GSB 3.4 (though this issue began with 3.3), and I'm having a problem with my phone rebooting (screen cuts off after about a second, and the phone immediately reboots to the skateboard screen) at the following times:
1. Whenever I attempt to wake the phone from sleep.
2. Whenever I hang up a phone call.
3. Whenever I get a phone call while the phone is asleep.
4. Whenever I plug the phone in to charge while the phone is asleep (be it a wall socket or PC) [see below].
These problems only occur when the phone is NOT plugged into a charging source; the problem appears to be nonexistent in this scenario. But as soon as I unplug, all 4 become auto-crash scenarios.
I tried going back to GSB 3.2, but no dice. I then resorted to the stock-ish XTRsense ROM, which fixed the issue, but going back to Froyo just was too big a downgrade for me.
Throughout this process, I full-wiped multiple times, hoping to track the issue to an app or setting, but even before restoring anything through TBU (I think I may have just let the phone go to sleep at the "Touch the Android" initial setup screen once), the problem persisted, eliminating apps, settings, or CM7 CPU modifications as possible culprits.
I've continued to play with CM7 CPU settings even up till now, but I'm not getting much of anywhere. I've now resorted to the "Caffeine" app, which just never lets the phone go to sleep, and I just turn the brightness down or activate the "Desk Clock" mode in the default Clock app to save battery.
HELP?
Have you tried Tazz's ROM or CondemnedSoul's ROM, just to see what happens with those? CS's ROM uses ADW as the default launcher (not sure about Tazz's) - perhaps it's something with LauncherPro?
Had this happen once
Sent from my Aosp Gin-Tazz using XDA App
My phones use to freeze on the unlock screen, it happened in multiple roms. i switched back to the "ondemand" governor and it hasn't happened since. not sure if it the same issue but it might help.
My last name is also Schultz ....
Sent from my Aosp-Gin-Tazz using XDA Premium App
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
scary alien said:
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
Click to expand...
Click to collapse
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
I'll try the changing the max, but I know I've tried as low as 604 max (19 min) with the problem persisting, and as high as 710 or 768 before GSB 3.3 (when the problem started) with no major issues. And I had already been using Ondemand when the problem started, having stopped using Smartass when I thought it slowing the performance down a bit. Any other governors I should try?
And does the overclocking issue not apply when a phone is charging?
doogald said:
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
Click to expand...
Click to collapse
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
natemup said:
And does the overclocking issue not apply when a phone is charging?
Click to expand...
Click to collapse
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
scary alien said:
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
Click to expand...
Click to collapse
You would have only seen that if you had seen the post in the GSB thread, of course.
I am still going to suggest trying Tazz or Condemned. From what the OP says, he should be able to see that it's having the same issue pretty quickly.
But, just to rule out the OC issue, you could try setting the max to stock 528 and see if it still happens.
doogald said:
You would have only seen that if you had seen the post in the GSB thread, of course.
Click to expand...
Click to collapse
lol...that post was on the 519th page of (currently) 530 pages! (I read the first page, does that count? )
Still crashing on 528 max / 19 min...
natemup said:
Still crashing on 528 max / 19 min...
Click to expand...
Click to collapse
How about on Tazz or Condemned? And, 19.2 is too slow for a minimum for this kernel. 245 should be the minimum.
scary alien said:
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
Click to expand...
Click to collapse
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
One more thing: if, right after the phone reboots itself, I unlock it before the screen goes off and manually put it to sleep and quickly wake it back up, the issue usually doesn't occur (and I can keep doing this, putting it to sleep and waking it back up again, with no issue). But if I unlock it and let it sit and reach the screen timeout itself (or never unlock it after it reboots, then let it sit for a while), the problem reoccurs.
natemup said:
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
Click to expand...
Click to collapse
I have used both GSB and Condemned and you will not be missing anything. I stopped using GSB because I could not get market updates to stick reliably. I do not have that issue at all with Condemned.
Right now the only issue with the latest Condemned is apparently a GPS issue, so I would go with V6 or V7 rather than V8 for now until CondemnedSoul gets an update. Or, if you don't navigate, go ahead with V8. It's just fine.
You're obviously having a stability issue with GSB now, so you have nothing to lose but about 45 minutes of time and a Nandroid Restore to go back to GSB if you don't like it.
So, I had a minor issue that was fixed by switching to a different ROM. It's worth a try.
I wish you luck finding a solution.
natemup said:
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
Click to expand...
Click to collapse
Nate,
Sorry about that ...I was confused from where you asked in post #8 about whether or not overclocking was in effect while charging (it can/could be, depending on the overclocking monitor/govenor I suppose) and I had lost that point from your original post.
I would say take doogald's advice and switch to at least some other ROM since that would help indicate if it is indeed a software issue or a hardware issue. Its sounding like its not clock-speed related given the things you've already tried. If you've still got issues on other ROMs, that would tend to point to some hardware issue (our Erii are getting a little long in the tooth at this point, after all).
You could even flash back to stock and see if the phone is still stable there since you can always re-root and re-restore your Nandroid backups.
Good luck...I hope you figure something out.
Problem is alive and well on Condemned GB. *sigh*
XTRsense was fine and flawless, but going back to Froyo after months on gingerbread was just too depressing for me...
Sent from my ERIS using XDA App
I'm going to make one more suggestion - not sure if you have tried this yet, but try flashing GSB from a full wipe. When you go through the setup, DO NOT LOG IN TO YOUR GOOGLE ACCOUNT. After the launcher starts, go into the market, let it log you in to your Google account then, and then install all of your apps and change all of your settings from scratch.
When you log in with your Google account when installing a CM ROM, it tries to restore your apps and settings from your last CM ROM install. It may be that you have some weird setting or app that is causing this that you just keep reinstalling when you flash the ROM and log in with your account.
If you've already tried this, then try running xtrSENSE or xtrROM instead. They are both excellent ROMs and clearly your phone likes them better.
[edit] Oh, and try leaving your min at 245 MHz for a while. See if that helps your phone run better. It should, and it should have the exact same battery life as 19.2, as nonsensical as that sounds.
It is literally happening as soon as I boot the phone after a fresh GB install. I four-corner the Android setup screen, let the screen time out, and boom I'm screwed.
hey guys. im pretty new to this android thing im an ex iphone user.
i use this task-killer app to show me how much RAM i got left and it always
show something between 250-100 mb of ram left out of 1024.
when i try the Antutu Benchmark i only get a 6000 score when
i saw ppl get 11000+.
the GPU score is fine and the I\O is fine the RAM is way low then others and the CPU score is low too.
what may be causing this problem?
oh btw when i play games like NOVA 3 and Gangstar Rio it laggs as hell.
Ty.
No games should lag the S3.
Firstly what firmware are you on?
Sent from my GT-I9300 using xda premium
stierney said:
No games should lag the S3.
Firstly what firmware are you on?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
im on 4.0.4.
yea it seems wierd to see souch a powerfull device lags.
i guess it has something to do with this low benchmark score i get..
Ok I was after the exact firmware revision and if you were using a custom Rom or not. Once that is established may be able to help a little more.
Sent from my GT-I9300 using xda premium
You need to provide more info before any of us can help out. Provide which ROM & kernel you are using & if it's stock. do you freeze or uninstall bloatware? what apps do you have running or are there any running while the games are running?
Your total RAM is around 700ish since the OS uses the rest after that, so having 250 or lower is normal. I have yet to experience lag when running games like the ones you've listed & the only time I ever have experienced lag is when the home screen redraws.
stierney said:
Ok I was after the exact firmware revision and if you were using a custom Rom or not. Once that is established may be able to help a little more.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
oh i see, im sorry
amm i ain't using any custom rom. though i know that my rom got some changes to get it to fit to my country.
what do u mean by firmware revision other than 4.0.4?
Did you flash any custom kernels? Only stock kernel seems to run right with heavy 3D games (ie, NOVA3), custom kernels always lag, then crash and reboot on me.
ishaycc said:
hey guys. im pretty new to this android thing im an ex iphone user.
i use this task-killer app to show me how much RAM i got left and it always
show something between 250-100 mb of ram left out of 1024.
when i try the Antutu Benchmark i only get a 6000 score when
i saw ppl get 11000+.
the GPU score is fine and the I\O is fine the RAM is way low then others and the CPU score is low too.
what may be causing this problem?
oh btw when i play games like NOVA 3 and Gangstar Rio it laggs as hell.
Ty.
Click to expand...
Click to collapse
This might be stupid, but where did you get your SGS3 at?
Honestly, Flash a stock ROM with Odin. I don't know if there are any one click master clear ones, but if you have the international there should have been any hacking needed to get it to work in your country.
Goto settings / about
Latest UK firmware ends lf2
Also check settings power savings and check cpu throttleing isn't on. Even with it on 6000 is real low. I hit 9000 with cup throttle on and my phone hasn't been rebooted in over a week.
Sent from my GT-I9300 using xda premium
i havn't flashed anything and i got it from a licensed Samsung seller in Israel.
the problem is i know they do some modification to get it to work right
with their langauge.
and they install their own rom.
i only download games and apps never to touch rom/root.
it's the international version with quad core.
when i compare the result's i get on the Antutu Benchmark it show
i have half the score on the ram and processors then i saw on Youtube.
ishaycc said:
the problem is i know they do some modification to get it to work right with their langauge. and they install their own rom.
Click to expand...
Click to collapse
Oh hell naw. XXALF2, flash that... NOW.
Never heard of an international phone not working in Israel without a modification. Personally I'd connect it up to kies and see if there's an update available.
Sent from my GT-I9300 using xda premium
Just thought I'd add that kies is the official Samsung application for updating your phone and won't break warranty etc.
Sent from my GT-I9300 using xda premium
cmd512 said:
Did you flash any custom kernels? Only stock kernel seems to run right with heavy 3D games (ie, NOVA3), custom kernels always lag, then crash and reboot on me.
Click to expand...
Click to collapse
Umm, just from the way he replied indicates he has no clue about flashing custom kernels. You can definitely scratch that off the list.
cmd512 said:
Oh hell naw. XXALF2, flash that... NOW.
Click to expand...
Click to collapse
lol mayble ill sound naive but won't i lose my warranty?
i remember when i first took the benchmark test when the phone was
just out of the box it showed me 11500.
now 2 weeks after it gone in half.
is there a way to root without lossing warranty cuz i know their rom is not
out on the market yet.
the phone will work in israel without the modification but it will have some bugs with the langauge
stierney said:
Just thought I'd add that kies is the official Samsung application for updating your phone and won't break warranty etc.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
that was my next questions
lol mayble ill sound naive but won't i lose my warranty?
Click to expand...
Click to collapse
Yes and no. Odin uses the same update mechanism ('Download mode') as the official Samsung Kies (which btw is a grotesk, slow and painful-to-use application) so the phone won't be able to tell _WHAT_ updated it.
The phone is only capable of telling whether the ROM (=firmware) you're flashing is Samsung-official or some aftermarked custom ROM.
When it detects the ROM not to be official it will display a corresponding notice (and counter) in the Download mode. However there exists an app (which requires a rooted phone... which you usually got on custom roms) called 'Triangle Away' capable of resetting that counter to 0.
Now of course the store could still boot up the device and check if you're on the original ROM, so you'll have to flash a Samsung-official ROM corresponding to your location before bringing it back. There is no need to reset the counter afterwards since, as said, official ROM's don't trigger it to increment.
What if your phone is so damaged that you can't get it to go to download mode (more or less hardware-bricked)? Well in that case the store won't be able to check if the phone is (was) running non-official firmware. Samsung could but they don't always do since it requires dismantling the device and dumping the storage chip (provinding it still works). In case software caused it to brick (not boot) and it's unrecoverable, there are stores and send-in services around that for a couple of bucks revive your phone through JTAG flashing.
is there a way to root without lossing warranty cuz i know their rom is not out on the market yet.
Click to expand...
Click to collapse
No.
the phone will work in israel without the modification but it will have some bugs with the langauge
Click to expand...
Click to collapse
just out of the box it showed me 11500. now 2 weeks after it gone in half.
Click to expand...
Click to collapse
The reason for your scores dropping might have several causes.
Please install 'Task Manager' by 'Houmiak', reboot your phone and open the Task Manager. Then kill all processes of programs you've installed which might have autostarted. (Note that some auto-restart as soon as they're killed, so you can't really get rid of them). If there are a lot of such apps,
try installing 'Autorun Manager' by 'Andrs Studio'.
Then run the benchmark again; is it significantly higher? If so, the reason most probably is that your app(s) are causing the issue.
d4fseeker said:
Yes and no. Odin uses the same update mechanism ('Download mode') as the official Samsung Kies (which btw is a grotesk, slow and painful-to-use application) so the phone won't be able to tell _WHAT_ updated it.
The phone is only capable of telling whether the ROM (=firmware) you're flashing is Samsung-official or some aftermarked custom ROM.
When it detects the ROM not to be official it will display a corresponding notice (and counter) in the Download mode. However there exists an app (which requires a rooted phone... which you usually got on custom roms) called 'Triangle Away' capable of resetting that counter to 0.
Now of course the store could still boot up the device and check if you're on the original ROM, so you'll have to flash a Samsung-official ROM corresponding to your location before bringing it back. There is no need to reset the counter afterwards since, as said, official ROM's don't trigger it to increment.
What if your phone is so damaged that you can't get it to go to download mode (more or less hardware-bricked)? Well in that case the store won't be able to check if the phone is (was) running non-official firmware. Samsung could but they don't always do since it requires dismantling the device and dumping the storage chip (provinding it still works). In case software caused it to brick (not boot) and it's unrecoverable, there are stores and send-in services around that for a couple of bucks revive your phone through JTAG flashing.
No.
The reason for your scores dropping might have several causes.
Please install 'Task Manager' by 'Houmiak', reboot your phone and open the Task Manager. Then kill all processes of programs you've installed which might have autostarted. (Note that some auto-restart as soon as they're killed, so you can't really get rid of them). If there are a lot of such apps,
try installing 'Autorun Manager' by 'Andrs Studio'.
Then run the benchmark again; is it significantly higher? If so, the reason most probably is that your app(s) are causing the issue.
Click to expand...
Click to collapse
ty for the helpful reply.
i already use Task manager. ill try the other thing u said.
the wierd thing the benchmark isnt stable it can show me 6000 and on the next one it shows 8000.
UPDATE: it made it to 12000 once and i tried it again and it went below 10000
Another update:
It seems that the low score appears when the phone i hot like after
Playing a heavy game or after taking the antutu few times in a row.
Its getting lower and lower each test.
If someone please can try taking the test 4-5 time in a row
And publish the scores here ill be gratefull.
Then ill know for sure if my device is factory defected.
make sure you dont run the benchmark with the power saving mod on
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.
Hey guys. I have had my EVO LTE since it was released last year and all of a sudden this past week the phone gets really hot and then will reboot itself. It does this sometimes when I am playing a game and sometimes even when I am not doing anything. The phone also seems to die faster than it used to. Is maybe the battery going in it? Any thing I should try?
I have not done any changes to the phone in months. I am still running MeanRom 6.5.2 and stock kernel.
sharky17 said:
Hey guys. I have had my EVO LTE since it was released last year and all of a sudden this past week the phone gets really hot and then will reboot itself. It does this sometimes when I am playing a game and sometimes even when I am not doing anything. The phone also seems to die faster than it used to. Is maybe the battery going in it? Any thing I should try?
I have not done any changes to the phone in months. I am still running MeanRom 6.5.2 and stock kernel.
Click to expand...
Click to collapse
I recently had the same problem. It would overheat constantly, especially when playing a game, and if you charged the phone and tried to use it at the same time, it would only overheat faster. I got my phone when it first came out as well. The tech made up something about a short in the power button, but they did end up replacing the phone for me. You'll have to go back to complete stock of course before bringing it into the sprint store. If you need any assistance getting your phone backed up or back to stock, shoot me a message.
Thanks for the info! Yeah I know I will bring i have to put it back to stock before bringing it in. I'm good with doing all that.
sharky17 said:
Thanks for the info! Yeah I know I will bring i have to put it back to stock before bringing it in. I'm good with doing all that.
Click to expand...
Click to collapse
If you do any overclocking, that may be the issue. Try to set it to a much lower value. The processor in this phone runs at an approved max. of 1.5GHz. Try to throttle it back to 1.0GHz and see what that gets you. I know the meanROM has a few versions that automatically overclock and that may be the issue as well. If you don't overclock,(speed up the natural CPU clock) then I would bring it back to Sprint. It seems like it may be a manufacturer's defect.
Hope that helped,
Chris C.
chris674 said:
If you do any overclocking, that may be the issue. Try to set it to a much lower value. The processor in this phone runs at an approved max. of 1.5GHz. Try to throttle it back to 1.0GHz and see what that gets you. I know the meanROM has a few versions that automatically overclock and that may be the issue as well. If you don't overclock,(speed up the natural CPU clock) then I would bring it back to Sprint. It seems like it may be a manufacturer's defect.
Hope that helped,
Chris C.
Click to expand...
Click to collapse
It is set at 1.3GHz but as I have said I haven't changed anything in months on it. Do you still think I should change it? I will plan to do some backups this weekend so I can return to stock for Sprint to look at.
sharky17 said:
It is set at 1.3GHz but as I have said I haven't changed anything in months on it. Do you still think I should change it? I will plan to do some backups this weekend so I can return to stock for Sprint to look at.
Click to expand...
Click to collapse
When I first noticed the heat problems, my phone was on MeanBean 3.09 and underclocked. I tried underclocking it more, I even tried removing the case to see if it would cool off. I decided to flash it all back to stock and see if that was the problem, and the phone still overheated on stock. Out of curiosity, have you dropped the phone or damaged it in any way?
DXtremz said:
When I first noticed the heat problems, my phone was on MeanBean 3.09 and underclocked. I tried underclocking it more, I even tried removing the case to see if it would cool off. I decided to flash it all back to stock and see if that was the problem, and the phone still overheated on stock. Out of curiosity, have you dropped the phone or damaged it in any way?
Click to expand...
Click to collapse
I would flash with the stock Rom and bring it back to Sprint. If u guys underclocked it and it still overheats, then I would think it is a manufacturer's defect. It doesn't make sense that the phone will still overheat with the cpu being underclocked.
Chris