Problem with the phone, when i go to unlock it sometimes, the screen will stay black and then just suddenly do a hard boot quite annoying! Sometimes it happens once a day or sometimes everytime you unlock it.
Any suggestions?
Using cyangen 7 mod
Thanks
Well these problems are always hard to solve, but I have a few suggestions. First of all, try running 1 GHz with performance governor for a while. It is not good for daily use because of big battery drain, but if it solves your problem, then the issue is in your kernel.
Transitions from low power state to fully awake state in a CPU require good stability, as the voltage jumps nearly at the same time as frequency. If your CPU struggles when you use your current voltages, it might just be unstable enough to cause a fatal error when you unlock your device.
Related
Hey there every one. When I am unlocking my phone I notice that it will flash the lock screen and then disappear and then immediately re appear. When you try to lock the phone sometimes it wont lock and the buttons will stay lit and will display the lock screen but the display wont sleep unless it times out.
This happens on all ROM's that I flash except CyanogenMod
I used both of the over clock methods but the results are the same.
Please Advise
macfan74318
macfan74318 said:
Hey there every one. When I am unlocking my phone I notice that it will flash the lock screen and then disappear and then immediately re appear. When you try to lock the phone sometimes it wont lock and the buttons will stay lit and will display the lock screen but the display wont sleep unless it times out.
This happens on all ROM's that I flash except CyanogenMod
I used both of the over clock methods but the results are the same.
Please Advise
macfan74318
Click to expand...
Click to collapse
Yeah, it sucks. Theres no real way around this but disabling the lock screen helps it from happening less frequently. But then you end up draining the battery & others by the screen coming on easily by trackpad, volume keys, and power button. Its a lose/lose situation really...
sino8r said:
Yeah, it sucks. Theres no real way around this but disabling the lock screen helps it from happening less frequently. But then you end up draining the battery & others by the screen coming on easily by trackpad, volume keys, and power button. Its a lose/lose situation really...
Click to expand...
Click to collapse
I bumped my minimum clock speed to 368 MHz, and I don't have this problem anymore. YMMV
seancneal said:
I bumped my minimum clock speed to 368 MHz, and I don't have this problem anymore. YMMV
Click to expand...
Click to collapse
Still happens to me when I try that. It occurs when you press the power button twice in succession.
Hi there,
anything new on this topic? I'm currently experiencing this annoying problem as described.
I've already tried to set the minimum clock to 368 Mhz but the bug still exists. Even setting CPU to standard clock (Max/Min @800) didn't solve the problem.
Is it possible that the reason is located already inside the overclocking kernel?
Greets
dktnecro
Generally if you're overclocking and you have lockscreen issues that are not present @ stock speeds, then it sounds to me like the overclock is too much and your system probably isn't stable.
Based on my experience overclocking computers, things can very well appear stable but if you do stress testing (8+ hours straight) things often crop up and show you that it is in fact not stable. This sounds like one of those things. And that's not good. Who knows what other corruption could occur during your use at that speed? I had the same lockscreen issues myself, and once I realized it was due to overclocking too much I ended up solving another issue I had where half of the calls I received were garbled to the person on the other end. No more lockscreen issues or garbled calls since backing off the o/c a bit.
If the issue doesn't happen at stock speeds then maybe it's just the kernel, and hopefully that isn't putting you at risk of any kind of corruption, either.
Keep in mind I really can't be 100% if overclocking will cause corruption on a phone, but based on a lot of time spend overclocking pc's I would have to guess that it can. I'm surprised that this isn't brought up more often on device forums.
Okay does any one have this same problem or am i just doing something wrong?
Every time i let my kindle sit with the screen off after about 30 minutes or so, and I assume it keeps going and getting stuck in sleep mode but the only way for me to get it turned back on is to do the whole power button for 20 seconds and then reboot. Am I not being patient enough with it or is there some trick to getting the screen back on that i haven't found yet? Because I've tried multiple different things and there isn't a disable sleep mode option in my rom just the option to extend the time, even though its pretty much useless. But can anyone help me with this?
what rom are you on?
Right now I'm on Hell Fire 1.1 but last week i was running CM9 Reloaded and it did the same exact thing.
I was going to give a long speech about how people need to READ before installing any new roms but considering the Hellfire thread doesn't list what works and what doesn't, I guess it's not entirely your fault
It's called "sleep of death" (SOD). Some ICS roms have problems with it and some don't. The same could be said about certain individual devices. You could boost your minimum CPU usage to 600Mhz or more, or try a different rom. Though, it should be noted that changing your CPU settings will affect battery life.
okay that makes sense i had no idea that most of the new roms have problems with it. but I'll probably try to up the min cpu usage i suppose the difference between 600 MHz and 300 MHz isn't going to be a true killer for the amount i use it but which rom or roms would you recommend? That don't have this problem I'd really like to try barebones but every time i try to flash it my Kindle goes crazy so i gave up on trying with it.
this happens after i overclocked my xperia arc s to 1.8ghz., 2.3,4 arconium rom, doom kernel v22, now after booting the device and when the menu shows up my phone turns to black and then restart. i already flashed the 2.3.4 rom. i dont know what to do. -_- please help.
and when i run sus it says the phone contains modified software that cannot be updated.
Too high OC.
1.8 GHz is obviously way too high for our phones, excessive clock setting causes the restart. Be happy, that it only started to do restarts. Otherwise the CPU could have melted and the phone would have been hard bricked due to hardware damage.
Flash stock kernel, should make the OC impossible, thereby no restart should occur.
I already flashed stock rom. but everytime the menu shows my phone restarts. -_- this sucks
yeah.. i think the oc was too high.. maybe it's the hardware issue..
i fixed it. i think the battery was loose a little so i tried putting paper to make it tighter. now it doesnt reboot everytime i open the phone, but i still experience random reboots. maybe 5-10x a day. -_- this phone sucks
bruts12 said:
i fixed it. i think the battery was loose a little so i tried putting paper to make it tighter. now it doesnt reboot everytime i open the phone, but i still experience random reboots. maybe 5-10x a day. -_- this phone sucks
Click to expand...
Click to collapse
This phone doesn't suks, your way to do things suks ! How could you think to maintain a stable overclock so high! Our phone cpu max tollerance in overclock is 1,6ghz stable. At least you could try to undervolt a little bit before to do that. Thinking mind is always the most important requisite.
^^ He's right
Maybe you didnt do a propper flash (wipe everything) and still are some scripts running and overclocking it again every boot
If not, then yes, you had probably damaged your phone.
my phone doesnt reboot now, putting paper on the battery fixed it. no more random reboot. running 1.7ghz stable oc.
I've had my G3 since launch and it's always lagged really bad when I've been using more than 1 app at once e.g., listening to music and web browsing. The device reaches 95c and then shuts down so I've had to downclock the CPU to 1.9ghz to stop the shutdowns. With it underclocked, it lags even worse now and still reaches quite high temps (75c~) I'm still on a rooted Kitkat as I haven't had time to upgrade the ROM. Do the new 5.xx ROM's fix the lag? Does it still over heat when doing really simple things?
Hi,
When i was on the stock 5.0 (20h) i had a bit of overheating but never reached the point of a shutdown.
Now I'm on a custom Rom (cloudy 2.5) and i have no heating issues, and a very good battery life.
You can try flashing the latest KDZ for your device and test it. You should also check that you don't have a process eating resources running in the background.
For me the only application that lags is the phone/agenda. It is bad lagging when you have many contacts.
I hope it helps.
Regards
Sent from my phone
lag
flash new rom clougyg3 v2.5...works wonders ....avoid task killers ...use system ui with expose installer if you want some customization...
Fahim92 said:
I've had my G3 since launch and it's always lagged really bad when I've been using more than 1 app at once e.g., listening to music and web browsing. The device reaches 95c and then shuts down so I've had to downclock the CPU to 1.9ghz to stop the shutdowns. With it underclocked, it lags even worse now and still reaches quite high temps (75c~) I'm still on a rooted Kitkat as I haven't had time to upgrade the ROM. Do the new 5.xx ROM's fix the lag? Does it still over heat when doing really simple things?
Click to expand...
Click to collapse
95c? thats frying hot and not safe at all. I guess since you have had it since launch you cant return it. try custom roms and kernels and if it doesnt still fix, i d say go for another device.
assuming you are rooted and have twrp, you can try the ctt mod: http://forum.xda-developers.com/lg-g3/development/thermal-mod-t2907363
worked for me and im on stock rom stock kernel kitkat(vs985). i just got on opera browser for about 6 minutes and the temp just sat at 55c and the power button is not even warm. before flashing the ctt mod i would start blowing at the back of my phone after 2 minutes of web browsing alone.
Hello,
http://forum.xda-developers.com/lg-g3/help/100-solution-wifi-bootloop-issue-t3503534
I used to use SETCPU. HERE IS WHY IT DOESN'T HELP:
set cpu only begins after your system is turned on. and lowering the CPU clock to 1728mhz doesnt help me. i still have restarts. and sometimes it goes into bootloop.
USE the https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en
Turn off the CPU2 and CPU3...
Let the max clock be 2497 or what ever that clock is. it fixed the loop so far. It starts on boot(it really does)
my prev score 4 cores full capactiy: 62k
6.0 STOCK rooted
now with DUAL CORE ONLY: 55k
better batterly life. less heat. no boot loops...
it is clear i have a hardware degraded phone...
log:
day 1 no restarts no boot loops. wifi works great
I kindly ask you to stop spaming and keep on creating the same topic as before.
And what's the point of creating a topic again and again and again?
Will you win something?
Surely a big NO mate.
If you keep on creating the same topic you'll make me report you mate
Have a nice day