My problem is that on any LinageOS Rom (Currently AEX Phoenix) my cpu frequency is always on max, it only drops for 1-2 seconds and then goes up again. I cannot seem to find a solution and I have been searching forever. I always did a clean flash but it's still the same. I have attached some logs so maybe someone can figure something out.
Thanks for your help.
Pharrax said:
My problem is that on any LinageOS Rom (Currently AEX Phoenix) my cpu frequency is always on max, it only drops for 1-2 seconds and then goes up again. I cannot seem to find a solution and I have been searching forever. I always did a clean flash but it's still the same. I have attached some logs so maybe someone can figure something out.
Thanks for your help.
Click to expand...
Click to collapse
Are you using performance governor or something? That would explain your symptoms.
pitrus- said:
Are you using performance governor or something? That would explain your symptoms.
Click to expand...
Click to collapse
No, shedutil but the same happens with interactive and conservative
When you clean flash do you full wipe and format data? Without formatting data some kernel settings and various other information stays on your phone. You have to wipe everything then format data. Provides the best experience when flashing
Related
so I'm on the latest CM nightly with setcpu 2.0.1 set to 1113ghz with min at 998mhz.
I noticed after every reboot and sometimes without a reboot setcpu reverts back to default (998 max 245 min).
I have set on boot checked and the only way to get it OC'd again is to go back into it.
it shows it's at 1113ghz but shows it's running at 245mhz. there any other settings to change to keep this from happening?
never happened before with any previous version.
I'm not exactly sure why you would want to set the minimum so high.... but anyhoo.
The issue is a problem with the version of superuser included with CM - it doesn't seem to hand out superuser permissions early enough for setCPU to apply settings at boottime. The workaround is to flash an older version of superuser. wildmonk posted a flashable, working copy of the older superuser appllication in his thread. Download, flash in recovery, and your troubles will be over.
codesplice said:
I'm not exactly sure why you would want to set the minimum so high.... but anyhoo.
The issue is a problem with the version of superuser included with CM - it doesn't seem to hand out superuser permissions early enough for setCPU to apply settings at boottime. The workaround is to flash an older version of superuser. wildmonk posted a flashable, working copy of the older superuser appllication in his thread. Download, flash in recovery, and your troubles will be over.
Click to expand...
Click to collapse
thanks, i'll flash it. any suggestions about what to set for min? thinking about leaving it at default.
dudebro said:
thanks, i'll flash it. any suggestions about what to set for min? thinking about leaving it at default.
Click to expand...
Click to collapse
I leave my min at the default 245. I want the processor to be able to scale all the way down if it doesn't have anything going on.
codesplice said:
I leave my min at the default 245. I want the processor to be able to scale all the way down if it doesn't have anything going on.
Click to expand...
Click to collapse
i'll probably do that as well. thanks for the help.
dudebro said:
i'll probably do that as well. thanks for the help.
Click to expand...
Click to collapse
No problem. Helps me to pass the time at work
Hi.
Latest Naa kernel on my X8. Latest Nightly(0416). Did flashed the proper way - first factory reset, wipe cache, wipe dalvik then flash latest nightly.
BUT in the latest 2 nightlies (0416 and 0328) my screen jumps randomly and the edge of the screen is sometimes at 2/3-rd of the hardware-screen... and the other part peaks in on the other side, but the touchzones are in place.
I have a singletouch device.
Any ideas or fixes?
I am not sure how to help but maybe you can try to change the theme
just a suggestion....besides that don't know how to help
sznattila said:
Hi.
Latest Naa kernel on my X8. Latest Nightly(0416). Did flashed the proper way - first factory reset, wipe cache, wipe dalvik then flash latest nightly.
BUT in the latest 2 nightlies (0416 and 0328) my screen jumps randomly and the edge of the screen is sometimes at 2/3-rd of the hardware-screen... and the other part peaks in on the other side, but the touchzones are in place.
I have a singletouch device.
Any ideas or fixes?
Click to expand...
Click to collapse
I get same on GDX + nAa 14 sometimes
Sent from my X8
sznattila said:
Hi.
Latest Naa kernel on my X8. Latest Nightly(0416). Did flashed the proper way - first factory reset, wipe cache, wipe dalvik then flash latest nightly.
BUT in the latest 2 nightlies (0416 and 0328) my screen jumps randomly and the edge of the screen is sometimes at 2/3-rd of the hardware-screen... and the other part peaks in on the other side, but the touchzones are in place.
I have a singletouch device.
Any ideas or fixes?
Click to expand...
Click to collapse
I faced this (and still)
To stop this you can lock & unlock the lockscreen(sometimes work) if dont work restart device ...
To prevent :
1-Do you use overclocking?
-if yes ,uncheck "undervolt" & "set on boot" before overclocking....
2-reflash kernel (I done before & worked :thumbup
3-(last chance) do a system wipe & reflash ROM
#i don't not how this exactly happens, these are personal experience & may work or not.
##your phone ,your risk !!!:thumbup:
Sent for xda via tapatalk
# always wear your seat belt as it saved my life...:beer:
# sorry for English
too much OC can cause this problem
CnC-ROCK said:
too much OC can cause this problem
Click to expand...
Click to collapse
Didn't happend in previus versions with the same overclock settings: min 320 max 691 sometimes 710...
sznattila said:
Didn't happend in previus versions with the same overclock settings: min 320 max 691 sometimes 710...
Click to expand...
Click to collapse
To all above:
This bug exists in every custom kernel. It is well known. It manifests itself most @ 691 Mhz so don't pick that.
Alfs9c-no-fps-cap shows this bug more than any other kernel but they all have it.
No point reflashing or changing themes - that is futile.
Either change rom & kernel to completely different base or adjust your cpu settings until it goes away.
CtrlAltDelIrl said:
To all above:
This bug exists in every custom kernel. It is well known. It manifests itself most @ 691 Mhz so don't pick that.
Alfs9c-no-fps-cap shows this bug more than any other kernel but they all have it.
No point reflashing or changing themes - that is futile.
Either change rom & kernel to completely different base or adjust your cpu settings until it goes away.
Click to expand...
Click to collapse
Thank you...
Hi there,
I have tried everything from custom roms to different kernals to scripts to try fix stutter lag in games, i even tried benchmarks and my gpu is having problems with everything, sonic dash as an example constant fps issues, benchmarks im only getting say 20 fps while other phones are around 50-60 fps. I am lost for ideas there must be something?
georgetbt said:
Hi there,
I have tried everything from custom roms to different kernals to scripts to try fix stutter lag in games, i even tried benchmarks and my gpu is having problems with everything, sonic dash as an example constant fps issues, benchmarks im only getting say 20 fps while other phones are around 50-60 fps. I am lost for ideas there must be something?
Click to expand...
Click to collapse
So have you modded your GPU UI rendering during any flashing? Might be the reason, try to re-flash your rom, or another (viper and ARHD are the ones i've used) one good luck
THeHopelessPainter said:
So have you modded your GPU UI rendering during any flashing? Might be the reason, try to re-flash your rom, or another (viper and ARHD are the ones i've used) one good luck
Click to expand...
Click to collapse
lots of things could be wrong.. did you change your GPU speed? are you running power saver mode.? do you have always draw in 2D setup in developer mode settings? have you tried a fresh wipe?
syaoran68 said:
lots of things could be wrong.. did you change your GPU speed? are you running power saver mode.? do you have always draw in 2D setup in developer mode settings? have you tried a fresh wipe?
Click to expand...
Click to collapse
This was happening before i modded my phone, i thought this would fix it, the steps i have taken are: fully factory reset, full wipe even wiped every folder there was including my OS ... oops! tried2 ROMSs, now using Viper 5.7.0
checked developer option it isn't forcing 2D. tried scripts for GPU with smanager that done nothing lol, using vipers stock that came with 5.7.0 also tried the ARHD
georgetbt said:
This was happening before i modded my phone, i thought this would fix it, the steps i have taken are: fully factory reset, full wipe even wiped every folder there was including my OS ... oops! tried2 ROMSs, now using Viper 5.7.0
checked developer option it isn't forcing 2D. tried scripts for GPU with smanager that done nothing lol, using vipers stock that came with 5.7.0 also tried the ARHD
Click to expand...
Click to collapse
your last bet is to RUU and see if that will work. then after you can reflash any rom but thats about the best i can offer you if you've flashed other roms and updated and checked of everything else.
syaoran68 said:
your last bet is to RUU and see if that will work. then after you can reflash any rom but thats about the best i can offer you if you've flashed other roms and updated and checked of everything else.
Click to expand...
Click to collapse
Yep tried the RUU, no luck my brothers iphone 4s runs games better, either this phone has a bad gpu chip or the phones faulty? very disappointed.
georgetbt said:
Yep tried the RUU, no luck my brothers iphone 4s runs games better, either this phone has a bad gpu chip or the phones faulty? very disappointed.
Click to expand...
Click to collapse
like you said the issue was there before you modded your phone, so im guessing it is a bad processor. How old is your One? And has this issue been present since you got your phone?
yea then i would totally get it replaced under warranty if you still have it. thats your last option.
syaoran68 said:
yea then i would totally get it replaced under warranty if you still have it. thats your last option.
Click to expand...
Click to collapse
ok thanks
So it seems like since i updated everything to 5.1 (radio etc) ive been having issues with my phone hot rebooting and also losing data. Ill have lte for hours and then all of a sudden i still have full bars but there is a "!" instead of 3G or LTE. Currently im on Temaseks latest nightly but it was happening on chroma also. My Baseband says "MDM9625_104446.01.02.95R". Any idea what could be causing this? (Im also not flashing anything crazy when I flash these roms. I flashed Temaseks nightly about 2 hours ago with the recommended banks gapps, and I just got a hotboot and lost datasignal).
HaiKaiDo said:
So it seems like since i updated everything to 5.1 (radio etc) ive been having issues with my phone hot rebooting and also losing data. Ill have lte for hours and then all of a sudden i still have full bars but there is a "!" instead of 3G or LTE. Currently im on Temaseks latest nightly but it was happening on chroma also. My Baseband says "MDM9625_104446.01.02.95R". Any idea what could be causing this? (Im also not flashing anything crazy when I flash these roms. I flashed Temaseks nightly about 2 hours ago with the recommended banks gapps, and I just got a hotboot and lost datasignal).
Click to expand...
Click to collapse
Did you clear cache? Clean flash or dirty?
Evolution_Freak said:
Did you clear cache? Clean flash or dirty?
Click to expand...
Click to collapse
Hey There. I'm a fan of never dirty flashing. I always wipe a few times before I flash anything. I dont do any type of titanium backup or anything either. I even deleted everything on my storage except for the TWRP backup folder and my roms folder so theres nothing weird left behind. Other than the baseband there was nothing else I needed to flash right?
HaiKaiDo said:
Hey There. I'm a fan of never dirty flashing. I always wipe a few times before I flash anything. I dont do any type of titanium backup or anything either. I even deleted everything on my storage except for the TWRP backup folder and my roms folder so theres nothing weird left behind. Other than the baseband there was nothing else I needed to flash right?
Click to expand...
Click to collapse
Thanks for clarifying that for me. No, I don't think you've missed anything. Before trying anything too drastic, I'd suggest flashing the factory image, if you can, and see if it continues to happen. I know that can be a hassle but it also could fix whatever might be broken.
Evolution_Freak said:
Thanks for clarifying that for me. No, I don't think you've missed anything. Before trying anything too drastic, I'd suggest flashing the factory image, if you can, and see if it continues to happen. I know that can be a hassle but it also could fix whatever might be broken.
Click to expand...
Click to collapse
hmm ill give it a try. Seemslike googles dev site is having problems at the moment and the download is going really slow...of course heh. ill report back when im on stock.
HaiKaiDo said:
So it seems like since i updated everything to 5.1 (radio etc) ive been having issues with my phone hot rebooting and also losing data. Ill have lte for hours and then all of a sudden i still have full bars but there is a "!" instead of 3G or LTE. Currently im on Temaseks latest nightly but it was happening on chroma also. My Baseband says "MDM9625_104446.01.02.95R". Any idea what could be causing this? (Im also not flashing anything crazy when I flash these roms. I flashed Temaseks nightly about 2 hours ago with the recommended banks gapps, and I just got a hotboot and lost datasignal).
Click to expand...
Click to collapse
adjust your voltages so that its best for your device. raise or lower your voltages until the reboots stop.
simms22 said:
adjust your voltages so that its best for your device. raise or lower your voltages until the reboots stop.
Click to expand...
Click to collapse
Wouldnt that mean theres something wrong with my phone? I havnt messed (and really dont ever) mess with OC or Voltages.
HaiKaiDo said:
Wouldnt that mean theres something wrong with my phone? I havnt messed (and really dont ever) mess with OC or Voltages.
Click to expand...
Click to collapse
no. the nexus 6 has 15 different pvc bin numbers. that means 15 different voltage charts to follow, depending on your devices bin number. and for each bin number, each individual device will vary. so, it might be alright, but most likely you would have to adjust slightly for best voltage for your personal device.
Evolution_Freak said:
Thanks for clarifying that for me. No, I don't think you've missed anything. Before trying anything too drastic, I'd suggest flashing the factory image, if you can, and see if it continues to happen. I know that can be a hassle but it also could fix whatever might be broken.
Click to expand...
Click to collapse
+1! Fastboot factory image. That's what I'd do. :thumbup:
Just what the title says. I'm not familiar with optimizing governors, so if someone with more experience has a different set of parameters that'd be better, feel free to drop recommendations. This uses the following settings (copied from elsewhere on XDA):
Governor: ondemand
up_threshold 70
sampling_rate 50000
sampling_down_factor 2
down_differential 15
freq_step 50
Performance seems quite a bit smoother than stock, especially when opening Google Assistant. Battery life has been in the vicinity of 20-25 hours.
Download: https://androidfilehost.com/?fid=673791459329059808
Installation:
Unlock bootloader and enable ADB if you haven't yet
adb reboot bootloader
fastboot flash boot boot.img
Not all heroes wear capes. I'm glad someone with the knowhow finally did it. I'm gonna try it here in just a few minutes. Been dying to get back that 4 core, 998 mhz since 2.0.
---
Edit: Alright, booted up perfectly fine, no issues. And I am already noticing its much quicker than before. Excellent job man, thanks a lot for this. My watch has been feeling so sluggish since 2.0 and this is just what it needed.
Omg huge thanks man!!! Finally
this working on Lg watch R ? 1.5 or 2.0 ?
odmetnik said:
this working on Lg watch R ? 1.5 or 2.0 ?
Click to expand...
Click to collapse
This is for the Urbane. It's plausible that it'd work on the GWR, but I don't have one to test on and won't make any guarantees. If you flash it on a GWR, make sure you're ready to flash it back to stock in case it doesn't work.
This is for the most recent 2.0 build, which is mentioned in the title. You can check your build in settings > system> about > build number. If you're on a different build, then this will most likely not work and you'll need to flash the factory boot.img in order for your watch to boot again.
Is there a noticeable decrease in battery performance? in comparison to the standard AW 2.0?
Awesome, working great, even more battery time than before.
Thanks bro!!!
HI,
My computer does not want to get along with the watch. I can not detect it. What could be the reason ? Debugging via USB have turned on in the clock.
https://ibb.co/mvPfB6 - i have this messege from ABD
PROBLEM SOLVED
mod is very goog.
Hi guys,
What's the stock CPU setup? I thought it was quad core at 1.2GHz.
Does anybody have the stock boot.img in case want to undo the mod?
ceanth said:
Hi guys,
What's the stock CPU setup? I thought it was quad core at 1.2GHz.
Does anybody have the stock boot.img in case want to undo the mod?
Click to expand...
Click to collapse
The stock setup is one core enabled at 788MHz. Most (maybe all?) watches with the SD400 did this to improve battery life.
You can get the stock boot.img from unzipping the full factory image here: https://androidfilehost.com/?fid=673368273298983957
Corrupt file
Bro.. Its say the file. img corrupt when i drag in windows
Any help?
This gave my watch new life... it's actually usable again! Thank you.
Sorry , i have a doubt. I read the entire "how to.." and still dont know, is necesary root access or twrp or is just fine with the bootloader unlocked (oem unlock)?
Psico.ext said:
Sorry , i have a doubt. I read the entire "how to.." and still dont know, is necesary root access or twrp or is just fine with the bootloader unlocked (oem unlock)?
Click to expand...
Click to collapse
You just need the bootloader unlocked.
Help me!!!!!!!
Hi everyone,
I have lg urbane watch with same build number. After I flash boot.img mod 4 cores, My watch can boot and suddenly shutdown.
I flash stock image but i have problem. My watch will suddenly shutdown if i discharge. Any one can help me. I try flash stock 1.5 but my watch can't return as normal.
:crying::crying::crying::crying:
Sorry for my bad English.
many thanks.
Adiprana1106 said:
Bro.. Its say the file. img corrupt when i drag in windows
Any help?
Click to expand...
Click to collapse
I've been stuck on this for about half an hour. I discovered that I didn't leave a space after typing "fastboot flash boot_"
So basically:
1. Type "fastboot flash boot" followed by spacekey ("fastboot flash boot_")
2. Drag boot.img before hitting enter
3. Enter
If I reset (factory reset) the watch, do I need to flash the boot image again, or does it persist?
surface13 said:
If I reset (factory reset) the watch, do I need to flash the boot image again, or does it persist?
Click to expand...
Click to collapse
I'd like to know this as well. Also, is there any way to double check to make sure this boot.img and 4 cores are in function?
Thanks
Matt174e said:
I'd like to know this as well. Also, is there any way to double check to make sure this boot.img and 4 cores are in function?
Thanks
Click to expand...
Click to collapse
My watch is overheated and consumed about 20% of charge in the first 30 mins (maybe for all the updates, app sync etc)
now i leave resting for a while. Anyone experienced this battery drain ?
REQUEST: 2 core 778MHz and 4core 778MHz
Hi thank you a lot for your work.
I flashed this, and effectively the watch became much more responsive, but after a while it started to feel significantly hotter , and from time to time the watch starts to reboot, sometimes multiple times rebooting, and becoming almost unusable, and it needs to be docked to even turn on.
Could it be that the watch's old battery is not able to deliver enough energy for the processors?
Could it be a problem with optimizing governors? No Idea. Maybe you could build a 2 core 778 / 998MHz or a 4 core 778MHz for me to test on my watch?
Phobophobia said:
Just what the title says. I'm not familiar with optimizing governors, so if someone with more experience has a different set of parameters that'd be better, feel free to drop recommendations. This uses the following settings (copied from elsewhere on XDA):
Governor: ondemand
up_threshold 70
sampling_rate 50000
sampling_down_factor 2
down_differential 15
freq_step 50
Performance seems quite a bit smoother than stock, especially when opening Google Assistant. Battery life has been in the vicinity of 20-25 hours.
Download: https://androidfilehost.com/?fid=673791459329059808
Installation:
Unlock bootloader and enable ADB if you haven't yet
adb reboot bootloader
fastboot flash boot boot.img
Click to expand...
Click to collapse