Hello everyone, it turns out that took a few days testing the module in different roms listilloV2 and talondev kernels 5.2.5 and semaphore bigmem bigmem also 1.9.0. Anyway, I've noticed these last few days especially with the kernel semaphore when it is off screen not receive calls as if in deep sleep and not wake up because when I burn to the screen to get the typical message that a number has called me. Also if I try to display on call from another number if it works perfect. Trying another module as ondemand works seamlessly with screen off. Anyone else happened?
Hello again, well just wanted to say that apparently I have been testing the module and is not smartass v2, but the thunderbolt script I had. I have changed to the latest version and so far I have not had any problem receiving calls.
Sorry, but another problem arises I am intentanto googlemaps update from the market and will not let me, reads "The package file is not signed correctly." I've downloaded from a link, I tried to install and tells me that the application is not installed. Any solution? Thank you.
I think its a Market issue. Try again later. A few other people also experienced this.
ok, thanks I'll prove it.
Well continue with my research in particular. I thought it was fixed the issue I receive calls but no, because even if you upgrade to the latest version of thunderbolt is the kernel semaphore v2 smartass had it in September but was still in ondemand CPU with what was normal to receive calls, but if you switched to v2 smartass anymore. At the end change the kernel to Talondev 2.5 and 0.5 .. still doing the same smartass v2. Already that the solution is not to use this governor but was very fluid mobile behavior. Have proven to with OndemandX and InteractiveX and to come I have to put them fluids voltages not so aggressive. Which of the two recomendais? My voltages are:
1000 ---- 50
800 ------ 75
400 ---- 100
200 ---- 125
100 ---- 150
and interactiveX ondemandX or simply have removed 25 at each frequency:
1000 ---- 25
800 ---- 50
400 ----- 75
200 ----- 100
100 ----- 125
Another thing about the market. I think that ultimately goes wrong? I do not let me install the latest version of Googlemaps 6.0, and that that changing the kernel thought that maybe was solved. Today I said I have another update Spy CPU and when I upgrade just to let me open it or uninstall or because there acutalizacion. .... Not that rare.
Another thing, for more information, I have the rom Innovation V14 F1, and so far had not had any problems.
snapx said:
Well continue with my research in particular. I thought it was fixed the issue I receive calls but no, because even if you upgrade to the latest version of thunderbolt is the kernel semaphore v2 smartass had it in September but was still in ondemand CPU with what was normal to receive calls, but if you switched to v2 smartass anymore. At the end change the kernel to Talondev 2.5 and 0.5 .. still doing the same smartass v2. Already that the solution is not to use this governor but was very fluid mobile behavior. Have proven to with OndemandX and InteractiveX and to come I have to put them fluids voltages not so aggressive. Which of the two recomendais? My voltages are:
1000 ---- 50
800 ------ 75
400 ---- 100
200 ---- 125
100 ---- 150
and interactiveX ondemandX or simply have removed 25 at each frequency:
1000 ---- 25
800 ---- 50
400 ----- 75
200 ----- 100
100 ----- 125
Another thing about the market. I think that ultimately goes wrong? I do not let me install the latest version of Googlemaps 6.0, and that that changing the kernel thought that maybe was solved. Today I said I have another update Spy CPU and when I upgrade just to let me open it or uninstall or because there acutalizacion. .... Not that rare.
Click to expand...
Click to collapse
Don't understand your English. Sorry
snapx said:
Another thing, for more information, I have the rom Innovation V14 F1, and so far had not had any problems.
Click to expand...
Click to collapse
F1 includes ThunderBolt!
Sorry for my English, but I use google translator. Well because I think this solved everything. In reviewing the system folder / etc / ini.d faltavan me and S98screenstate_scaling S98system_tweak files. Perhaps without realizing it clear it but everything works normally. Rom that already incorporates thunderbol Innovation F1 but I wanted to update it if it were a problem. So far it seems that everything is resolved. Thanks anyway for everything.
Related
I didnt want to root my phone HTC WILDFIRE because I am a little noob at these things a I thought I would totally destroy my phone.
But I found out that it is not so hard to root it as I thought, so today I succesfully rooted my phone. Than I wanted to overclock my procesor from 528 Mhz to I think 768 by downloading new kernel etc... Everything went good. I succesfully installed(or what, I said I am a little noob) that new kernel and was happy that my Wildfire will be faster.
But now I can see that my phone is lagging more, sometimes it freezes what i couldnt see before when It had original kernel.
HOW IS IT POSSIBLE?
Pls help
Do you have SetCPU installed? Then turn it a bit down, till 690~710 Mhz
Maxing it totally out can make your phone unstable. Think about it like a car, when it has 100 hp's and you tune it to 150 hp's things might break.
From stock 528 to 768 isn't a walk in the park, it's +45%
Yes I have setCPU and when I set my procesor to about 710 Mhz it lags and freezes. When I set it to about 580 it is doing the same. The only one solution of this I think is to reinstal the kernel.
Now I have 2.6.32.21-HCDRJacob-ga91 e 73b- [email protected] 1.
That is the full name of it. And in setcpu info it shows me before the version ( 2.6.32.21-HCDRJacob-ga91 e 73b- [email protected] 1) Linux versio... Maybe thats the problem???
And I have to find some solution as fast as possible because sometimes when somebody calls me I cant answer because of a biiiig lag. And then I cant do anything.
Thx for help
What id the minimum speed set to? I wouldn't go below 160. And my max is 672mhz.
Are you running different profiles or just the main profile in setCPU? Mine used to lag when i had a few profiles running but i have removed them all and only using the main profile and the lag has now gone.
when i went to wildpuzzle i found whatever speed i set my processor through set cpu it froze about 4-5 times a day. after flashing the kernel to remove overclocking it has not frozen in a week. everything really responsive, checking auto detect speeds with set cpu shows max 528mhz min450mhz
I tried many options and at last its OK. firstly I had a big difference between max and min of my procesor at setCPU, so I tried to set it to min about 630 and max about 700.
Now it is OK I dont know how, but I am happy the ****y problem is somehow solved and everytjing now goes very smoothly, thx u all
ephbee said:
when i went to wildpuzzle i found whatever speed i set my processor through set cpu it froze about 4-5 times a day. after flashing the kernel to remove overclocking it has not frozen in a week. everything really responsive, checking auto detect speeds with set cpu shows max 528mhz min450mhz
Click to expand...
Click to collapse
So what kernel did you flash it to?
Hi guys,
i tried CM7 but it was really laggy at my device, a lot of you guys said it is a very fast release !? so how can i get it working smooth ? when i wanted to get into the cpu settings i had a force close every time, jit was enabled..
do i have to get setcpu ? when yes where? which frequencies run smooth and stable ?
thanks in advance
eichl0r said:
Hi guys,
i tried CM7 but it was really laggy at my device, a lot of you guys said it is a very fast release !? so how can i get it working smooth ? when i wanted to get into the cpu settings i had a force close every time, jit was enabled..
do i have to get setcpu ? when yes where? which frequencies run smooth and stable ?
thanks in advance
Click to expand...
Click to collapse
Wipe EVERYTING, install CM7 then install HCDR.Kernal 4.1 (4.2 doesn't work as well) then use another overclock program, not setcpu, it doesn't work well with CM7. Hope that helps you!
* First, try flashing Kernel v4.1. CM7 comes with Kernel 4.2 by default, and, because it is clocked at 768 max, it leads to a lot of stability problems for everyone. Look for the HCDR.Kernel Topic in Wildfire Android Development Zone
* After that, you can install SetCPU. The SetCPU Dev has a thread here on XDA where he has posted the APK of SetCPU for download. Just enter SetCPU in the search bar and you should be able to find the thread with no issues. Here, you can set the max (Upto 710 recommended) and min (upto 245 recommended)
This should solve your lag and stability issues. If it still doesn;t, two more apps which can cause lag are (Note: This affects only a small %age of members with CM7)
* SetCPU (Alternative: OverclockWidget)
* ADW.Launcher (Alternative: Any other Launcher)
Oh, and CPU Settings FC's for everyone, from the time it was implemented. Looks like it is not ready yet.
Good Luck
hey 3xeno, thanks for your tipps!
with kernel 4.1 + setcpu + adw.launcher ex it finally works good!
the only thing thats a little strange is that i couldnt use my overclock setup from the openfire rom i had before, i have your suggested settings + screen of profile (352 max 245 min)+ tmep > 46° profile (352 max 245min), with openfire it was possible to have it at 691 mhz max and 245mhz min for normal mode, now i had to put it on 614 max 245min to not get the battery too warm, but anything else works great
eichl0r said:
hey 3xeno, thanks for your tipps!
with kernel 4.1 + setcpu + adw.launcher ex it finally works good!
the only thing thats a little strange is that i couldnt use my overclock setup from the openfire rom i had before, i have your suggested settings + screen of profile (352 max 245 min)+ tmep > 46° profile (352 max 245min), with openfire it was possible to have it at 691 mhz max and 245mhz min for normal mode, now i had to put it on 614 max 245min to not get the battery too warm, but anything else works great
Click to expand...
Click to collapse
That is rather weird, because, many are keeping it at 710 MHz Max and having no issues. What is your battery temperature when you keep it at 691? (And at idle. It is normal for the phone to get warm when you continuously run a heavy app like a game on it, also, I am sure you know this, but dont measure during charging, it does get pretty warm then )
hmm i played around with the phone a little and then put it in my pants pocket, after wa while when i put it back out it has restarted i guess and i was very warm at the back...hmm ill test it a little perhaps it was a one time thing
ok guys first of all ill start by saying that none of this i mine...its all stuff that i understood from different threads.I am a complete noob so there are gonna be many things ill not be able to understand to you!
i am gonna thank these brilliant people first
-gokhanmoral
-pikachu
-droidphile
-andre
and others(who have started undervolt threads) ive missed!
ok now to the main point!
this works only on ics siyah kernels as currently GM is the only one who supports the following commands!
what you need!!
-terminal emulator
-volt tweaking app (set cpu, voltage control),i wont prefer extweak or xxtweak as you cant edit a perticular freq volt with them
-patience
ok now start by selecting the freq on which you wanna work..undervolt it to your desired volt
e.g ive undervolted my 200mhz to 925mv
now open terminal emulator
type:
su
LVL=`cat /proc/kallsyms|grep " level\."|awk '{print $3}'`;kmemhelper -n $LVL -t int 14
and press enter
ok what this command does is that it changes your touch screen freq to the number last in the command line..in this case 14 it is
you can alter these numbers as follow:
0-1600 6-1000 12-400
1-1500 7-900 13-300
2-1400 8-800 14-200
3-1300 9-700 15-100
4-1200 10-600
5-1100 11-500(stock)
so as you can see the above command line sets my touch freq to 200 mhz.
ok so as soon you press enter in the terminal emulator your touch freq is changed to the freq of your liking..(remember use the above states numbers and not the freq itself in the command line) and some how that perticular freq takes load in such a pattern which i could not recreate with any stress stability test or even mxvideo test( you can find about it in various threads) and hence if the undervolt is below the stability threshold your phone will crash,hang,reboot...but you will get to know which volt value on which freq is unstable.
After setting the touch screen freq try(you can use voltage control to confirm if your touch freq has changed or not) use your phone normally...scrolll between pages..browse..play games..and if the perticular freq volt is unstable your phone will indefinitely crash within 5-10 min..!
do this procedure for every freq and ull definitely will get yourself the most stable UV's your device can handle!
you can read much about this and other stuff in droidphiles thread
http://forum.xda-developers.com/showthread.php?t=1572937
thank me if it helped!!
Hmm... do we really need another one of these threads lol
Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
i jus tought of sharing this as it seems to me that this kinda crash which the touchscreen freq produces isnt reproduced by any stability test..hence another way for testing your stability...besides i myself was facing few crashes with my settings lately and this cured it...!
Your CAPS key is broken ...
haha not really...HERE YOU GO...i had words in caps up there aswell...dun knw what went wrong..btw...love your dp!!
Thanks for the info. I've been having a little trouble with some UV values that I believe should be stable. This might be the fix. I'll report back after I've tested it.
I didn't even know you could do that, learn something everyday.
Interesting because in Siyah I've always noticed the max frequency ALWAYS exceeds whats set in SetCPU etc.
If I set it to 500mhz, it will still jump to 800Mhz momentarily when touching the screen, loading apps, scrolling etc. I've noticed on the latest kernel it hits 1200mhz, no matter what my global max frequency is. On Abyss kernel etc, it behaves normally. Is this 'touch frequency' the reason for this?
I watch the CPU frequency using Cool Tools/CPU spy...
Tye:P said:
Thanks for the info. I've been having a little trouble with some UV values that I believe should be stable. This might be the fix. I'll report back after I've tested it.
I didn't even know you could do that, learn something everyday.
Click to expand...
Click to collapse
yeah i myself was having issues with uv's..found this way indirectly with the help of droidphile...would love to see if it helped you!
busky2k said:
Interesting because in Siyah I've always noticed the max frequency ALWAYS exceeds whats set in SetCPU etc.
If I set it to 500mhz, it will still jump to 800Mhz momentarily when touching the screen, loading apps, scrolling etc. I've noticed on the latest kernel it hits 1200mhz, no matter what my global max frequency is. On Abyss kernel etc, it behaves normally. Is this 'touch frequency' the reason for this?
I watch the CPU frequency using Cool Tools/CPU spy...
Click to expand...
Click to collapse
mate your issue can be solved simply by installing extweak and setting the smooth scaling level to your max freq..on default the level is 1200..but this issue was solved in the 3.2.7.X versions of siyah..which version are you using?
i'll try to UV with xxtweak
doesnt matter what uv tool you use...but i should be an app which uv's indivisual freq's and not all at once as then you wont be able to figure out which volt is giving error on which freq!
I have updated my M2 with cm10.
it's working well, but I'm facing some reboot some time.
I have same problem when I used MIUI, so I don't know if it's due to CM10 / lower memory (around 50Mo when reboot appears) or due to bug in my phone.
anybody facing to anormaly reboot ?
Regards,
lacolle said:
I have updated my M2 with cm10.
it's working well, but I'm facing some reboot some time.
I have same problem when I used MIUI, so I don't know if it's due to CM10 / lower memory (around 50Mo when reboot appears) or due to bug in my phone.
anybody facing to anormaly reboot ?
Regards,
Click to expand...
Click to collapse
Do you undervolt?
No
Sent from my A953 using xda app-developers app
Do you have this reboot problem on official GB or Froyo too?
Enviado desde el ñoba usando Tapatalk 2.2.8
maybe
In fact, 1 years ago, i switched from original rom to miui rom. it was work fine, but few month after some reboot appears, then more and more often.
I suspect an incompatible apps with miui, so i decided to switch to CM10 one month ago with tezet ch kernel. But reboot problem stay.
So I don't know if my problem is hardware or software.
do you have some similar problem ?
lacolle said:
maybe
In fact, 1 years ago, i switched from original rom to miui rom. it was work fine, but few month after some reboot appears, then more and more often.
I suspect an incompatible apps with miui, so i decided to switch to CM10 one month ago with tezet ch kernel. But reboot problem stay.
So I don't know if my problem is hardware or software.
do you have some similar problem ?
Click to expand...
Click to collapse
Does it reboot on high demand or low demand?
And do you use v6 supercharger?
sometimes reboot just when i unlock mobile, sometimes when I start apps, or when I connect to dock station.
so always when demand appears (low or high).
Maybe I can try to freeze clock frequency
I don't know v6 supercharger
lacolle said:
sometimes reboot just when i unlock mobile, sometimes when I start apps, or when I connect to dock station.
so always when demand appears (low or high).
Maybe I can try to freeze clock frequency
I don't know v6 supercharger
Click to expand...
Click to collapse
Than not really sure what the problem is caused by.
Can you post your vsel values and cpu frequences, may be that will give us some idea
frequency is between 300 -> 1000
Where can i found vsel ?
lacolle said:
frequency is between 300 -> 1000
Where can i found vsel ?
Click to expand...
Click to collapse
Install this app: http://forum.xda-developers.com/showpost.php?p=31502042&postcount=856
Launch, scroll down to find Overclock toolbox...open it up and it should give you your clock and vsel values, if not click on "Current" and then report back
clk1 300 vsel 30
clk2 600 vsel 46
clk3 800 vsel 54
clk4 1000 vsel 58
thanks for your help
lacolle said:
clk1 300 vsel 30
clk2 600 vsel 46
clk3 800 vsel 54
clk4 1000 vsel 58
thanks for your help
Click to expand...
Click to collapse
I am afraid I don't know what causes you problems...your vsel values seem to be alright. I am sorry for not being much of a help....
trebuchet stop regulary, so maybe memory problem
when I start mobile, I have around 100Mo but after using few apps, I have only 50Mo free
lacolle said:
sometimes reboot just when i unlock mobile, sometimes when I start apps, or when I connect to dock station.
so always when demand appears (low or high).
Maybe I can try to freeze clock frequency
I don't know v6 supercharger
Click to expand...
Click to collapse
I assume this is caused by the MIUI, which might have been ported from Defy rom (not especially developed for Milestone 2), I had similar problem when I flashed the rom ported from Defy.
I flashed official froyo before install CM9, because I want a clear base. I would suggest that before flash official froyo / GB kernel stock rom, know your current kernel version to avoid the "first screen stuck" problem. Downgrade or adjusted kernel before flashing official rom.
Hope my suggestin work. Good luck!
Peter
Sent from my A953 using xda premium
ok Peter, I will try it this weekend
I'm also having freezing and rebooting, it is usually when I switch between apps, or open one.
Is there any tracing app I can use to log the data and see what's going on before the halt?
Thanks!
I need time to to some trial, but from latest OTA update (sunday), I have no more reboot. I'm waiting to check if one occurs
Hello, I bought a Moto G 2nd generation XT1069 DSTV, and the CPU frequency not lower more than 787 MHz. I used CPU-z to verify. The first boot after removing it from the box, the frequency in idle was 300 MHz, but now is 787 MHz. It's a serious bug. I've done 5 wipe data/factory reset, but this did not solved the problem. Any solution? Someone with this problem too? Thanks. (Sorry for my bad english).
To be honest, I've never seen this before, have you tried flashing the stock firmware to see if it helps?
Y2000 said:
Hello, I bought a Moto G 2nd generation XT1069 DSTV, and the CPU frequency not lower more than 787 MHz. I used CPU-z to verify. The first boot after removing it from the box, the frequency in idle was 300 MHz, but now is 787 MHz. It's a serious bug. I've done 5 wipe data/factory reset, but this did not solved the problem. Any solution? Someone with this problem too? Thanks. (Sorry for my bad english).
Click to expand...
Click to collapse
Check the problem from a command shell over adb. Try this with the screen off and no apps running in the foreground.
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Repeat a few times to verify the cpu isn't scaling down. If you have superuser access and busybox installed, you can prefix the command with 'busybox watch -n 1' and it'll print every second until cancelled (CTRL+C). If the frequency never drops below 787200 kHz, use the 'top' command to work out which process is using most cpu time.
Y2000 said:
Hello, I bought a Moto G 2nd generation XT1069 DSTV, and the CPU frequency not lower more than 787 MHz. I used CPU-z to verify. The first boot after removing it from the box, the frequency in idle was 300 MHz, but now is 787 MHz. It's a serious bug. I've done 5 wipe data/factory reset, but this did not solved the problem. Any solution? Someone with this problem too? Thanks. (Sorry for my bad english).
Click to expand...
Click to collapse
on /etc/init.qcom.post_boot.sh scaling_min_freq is set to 787200 :
Code:
echo 1 > /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu2/online
echo 1 > /sys/devices/system/cpu/cpu3/online
echo 787200 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
chown -h system /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
# add read permission to max cpu frequency interface
try to set it yourself to 300000 after booting and see afterwards if it sticks, if it does you could just modify the script ...
Solved (or not)
After opening and close the camera app, the CPU goes down to 300 MHz. I need repeat this after each reboot. Is a kernel bug, I hope Motorola fix this. I don't have unlocked bootloader or root on my device for warranty reasons. Thank so much for the support! (again, sorry for my bad english )
Y2000 said:
After opening and close the camera app, the CPU goes down to 300 MHz. I need repeat this after each reboot. Is a kernel bug, I hope Motorola fix this. I don't have unlocked bootloader or root on my device for warranty reasons. Thank so much for the support! (again, sorry for my bad english )
Click to expand...
Click to collapse
Do you have an SD card in? I'm wondering if you still see this symptom with the card removed. I say symptom because I seriously doubt the governor has a scaling bug.
Y2000 said:
After opening and close the camera app, the CPU goes down to 300 MHz. I need repeat this after each reboot. Is a kernel bug, I hope Motorola fix this. I don't have unlocked bootloader or root on my device for warranty reasons. Thank so much for the support! (again, sorry for my bad english )
Click to expand...
Click to collapse
i just noticed i have exactly the same behaviour, thanks for pointing it out. waiting for lollipop and hope it wil fix this problem
same 787 min value
I have the same problem now cpu not going below 787 and tried your trick open camera and closing ,yes it works bt what will be cause how to solve
vaisakmct said:
I have the same problem now cpu not going below 787 and tried your trick open camera and closing ,yes it works bt what will be cause how to solve
Click to expand...
Click to collapse
In kernel ramdisk the cpu is setted to be between 787Mhz and 1.2 GHz, I don't know why opening the camera change this. BTW if you are rooted you can change it using apps like trickster mod and similar
It seems the mpdecision daemon prevents the CPU from scaling right down. Whilst playing around with the Furnace kernel, I discovered that disabling mpdecision allowed me to successfully set the minimum scaling frequency to 300MHz. The easiet way to achieve this is to use the excellent Kernel Adiutor; disable mpdecision,set the min frequency to 300MHz, but don't enable multicore power saving. Leave the governor set to interactive -- the Moto G's kernel doesn't support boostpulse for ondemand.
When set up this way, the benefits to battery life are quite dramatic.
I have unrooted new moto g .how can i underclock the cpu of this phone?
Sent from my XT1068 using XDA Free mobile app
You can't without root
Sent from my XT1028 using XDA Free mobile app
lollipop 5.02 have not solved this problem
Y2000 said:
Hello, I bought a Moto G 2nd generation XT1069 DSTV, and the CPU frequency not lower more than 787 MHz. I used CPU-z to verify. The first boot after removing it from the box, the frequency in idle was 300 MHz, but now is 787 MHz. It's a serious bug. I've done 5 wipe data/factory reset, but this did not solved the problem. Any solution? Someone with this problem too? Thanks. (Sorry for my bad english).
Click to expand...
Click to collapse
i am from india and MOTO g2 updated to lollipop 5.02 in XT1068 and this issue is not yet solved.
I also have this issue on 4.4. Good that there is a work-around. I raised a problem with Moto Support and I suggest more people go this route, so they are aware that this is something they really should fix
I get the impression that is actually by design, rather than oversight. Given the ridiculously aggressive LMK settings, the reduced number of hidden apps (12? On a phone with 1GB of RAM? Really?!) and this scaling issue, it rather looks like Motorola tuned the software for the phone to appear snappy on first use. It looks good in reviews but sucks balls during intensive/extended use.
rufflove said:
It seems the mpdecision daemon prevents the CPU from scaling right down. Whilst playing around with the Furnace kernel, I discovered that disabling mpdecision allowed me to successfully set the minimum scaling frequency to 300MHz. The easiet way to achieve this is to use the excellent Kernel Adiutor; disable mpdecision,set the min frequency to 300MHz, but don't enable multicore power saving. Leave the governor set to interactive -- the Moto G's kernel doesn't support boostpulse for ondemand.
When set up this way, the benefits to battery life are quite dramatic.
Click to expand...
Click to collapse
thanks for this tip, works well! in kernel adiutor there are other settings to change for better performance?