[Q] Problem with FauxClock - Nexus 4 Q&A, Help & Troubleshooting

Hello,
I have a problem with the Fauxclock app on my Nexus 4.
ROM is CM10.1 official nightly with faux kernel 002b5.
Everytime I reboot the phone all my settings are gone. The governor is set to ondemand and max clock speed.
I selected intellidemand and some other modifications. The "set on boot" tabs are all set inside the app.
It also takes a long time to start the app. It is recquiring root and always setting the proper permissions.
Can anybody help me solving this problem?
Thanks in advance.

Sorry I can't help with your settings not sticking. Maybe ask in his thread. One thing that I have seen mentioned in his thread is that he recommends using the supersu app as opposed to the superuser app that I believe is included in cm10.1. The app may not be getting proper root permissions.
The slow startup with setting permissions and such is normal from my experience.

http://forum.xda-developers.com/showthread.php?t=2008222

Related

SetCPU issue vs. SU

Anyone having issues with SetCPU? SetCPU doesn't seem change when I try and make changes as described in another thread. It always stays at 528 and "performance". I try and change my sliders, which do change, and select "on demand", hit refresh, but it says it is still running at 528 and when I re-open SetCPU it always has reverted back to "Performance" and is running at 528. I think it may have to do with SU Permissions as I never had to set any when I first opened SetCPU, (either time, re-installed once already). Any ideas on how to fix this so I can throttle this down a bit?
SportsPT said:
Anyone having issues with SetCPU? SetCPU doesn't seem change when I try and make changes as described in another thread. It always stays at 528 and "performance". I try and change my sliders, which do change, and select "on demand", hit refresh, but it says it is still running at 528 and when I re-open SetCPU it always has reverted back to "Performance" and is running at 528. I think it may have to do with SU Permissions as I never had to set any when I first opened SetCPU, (either time, re-installed once already). Any ideas on how to fix this so I can throttle this down a bit?
Click to expand...
Click to collapse
What kernel are you running. Stock kernel can't use setCPU its all governed for you.
SportsPT said:
Anyone having issues with SetCPU? SetCPU doesn't seem change when I try and make changes as described in another thread. It always stays at 528 and "performance". I try and change my sliders, which do change, and select "on demand", hit refresh, but it says it is still running at 528 and when I re-open SetCPU it always has reverted back to "Performance" and is running at 528. I think it may have to do with SU Permissions as I never had to set any when I first opened SetCPU, (either time, re-installed once already). Any ideas on how to fix this so I can throttle this down a bit?
Click to expand...
Click to collapse
This same thing happens to me, and I'm running Fresh 1.1 with the Gumbo kernel. Any solutions, anyone? I've tried RUU, reflash, data wipe, and reinstalling setCPU and nothing works.
Kcarpenter said:
What kernel are you running. Stock kernel can't use setCPU its all governed for you.
Click to expand...
Click to collapse
Gumbo Kernel with Fresh 1.1
I may try to re-Flash Fresh, then Gumbo kernel and see what happens. I have yet to be asked to set any SU permissions for any app, so I think the problem maybe with that.
Try the MoDaCo kernel. I am not sure if gbhill has done what he needs to his kernel to enable setCPU. I think MoDaCo has.
Kcarpenter said:
Try the MoDaCo kernel. I am not sure if gbhill has done what he needs to his kernel to enable setCPU. I think MoDaCo has.
Click to expand...
Click to collapse
You have your kernels mixed up.
theraginasian said:
You have your kernels mixed up.
Click to expand...
Click to collapse
Wouldn't be the first time.
Kcarpenter said:
What kernel are you running. Stock kernel can't use setCPU its all governed for you.
Click to expand...
Click to collapse
SetCPU does work on the stock rom as long as Busybox has been installed. Works great with Gumbo kernel.
I know it works with Fresh 1.1 and SetCPU, there are posts everywhere to that point. However, I can't get SetCPU to adjust anything.
SportsPT said:
Anyone having issues with SetCPU? SetCPU doesn't seem change when I try and make changes as described in another thread. It always stays at 528 and "performance". I try and change my sliders, which do change, and select "on demand", hit refresh, but it says it is still running at 528 and when I re-open SetCPU it always has reverted back to "Performance" and is running at 528. I think it may have to do with SU Permissions as I never had to set any when I first opened SetCPU, (either time, re-installed once already). Any ideas on how to fix this so I can throttle this down a bit?
Click to expand...
Click to collapse
For some reason setCPU doesn't have superuser permissions (exactly what you guessed). Set CPU needs to write data to /sys/devices/system/cpu/cpu0/cpufreq/ .
There should be an ondemand folder in that path, and I'll bet there isn't.
When you first ran setcpu did it ask for su and then go black? If so, hit Home key and relaunch it.
gbhil said:
For some reason setCPU doesn't have superuser permissions (exactly what you guessed). Set CPU needs to write data to /sys/devices/system/cpu/cpu0/cpufreq/ .
There should be an ondemand folder in that path, and I'll bet there isn't.
When you first ran setcpu did it ask for su and then go black? If so, hit Home key and relaunch it.
Click to expand...
Click to collapse
No, I have never been asked for SU. I have tried relaunching it, even un-install, re-install still no luck, and no request for SU permissions.
So I re-Flashed Fresh and after that SetCPU asked for SU permissions. After re-flashing Gumbo kernel I can now actually make changes to SetCPU. Either I just skipped right over the SU permission screen the first time, or it didn't ask. Anyway works now if anyone else has this issue.
i got this app but i cant go over 528 why?
xtkxhom3r said:
i got this app but i cant go over 528 why?
Click to expand...
Click to collapse
becuase right now none of the kernels support overclocking 528 is the max set through the kernel.
damn my friend is running 700 on his g1!!!! ...hes running 2.1 too if i changed to 2.1 would i be able to oc more?
xtkxhom3r said:
damn my friend is running 700 on his g1!!!! ...hes running 2.1 too if i changed to 2.1 would i be able to oc more?
Click to expand...
Click to collapse
No. It has to be modified in the kernel. The code in the kernel restricts it to 528 MHz.
I'm sure someone is working on it...but I don't think it is as big of a priority (could be wrong on this) as, say, getting 2.1 working fully on the Hero.
2.1 has a custum kernel that allows up to...660? Just not released yet.
so is there a value we can just change in the kernel or does a dev have to hack our kernel first?
Look in the 2.1 thread
SportsPT said:
No, I have never been asked for SU. I have tried relaunching it, even un-install, re-install still no luck, and no request for SU permissions.
Click to expand...
Click to collapse
Pretty much im in this boat. Running fresh 1.1 and gumbo hack. Like it will get to the screen to choose phone then after that it will say SU on the top and then nothing else. I re flashed everything and it still does that. So what am I doing wrong? Even when I go to the SU app directly its a blank screen? Is that supposed to be like that?

A few questions

what's the consensus about stability, supprot development and battery life? It seems like CM7 offers the most battery life, CM10 is still unstable and CM9 has hardware acceleration but battery drain. I am on CM9 and wondering whether I should move forward to CM10 or just keep waiting for Qarx to release better releases?
Also is there a way, on my phone, to be notified of build releases?
What is the difference (I have a Bravo) between Kobe and Qarx builds? I have been using Kobe can I just flash to Qarx?
Also if I'm upgrading from CM9 to CM10 is there a way to keep my settings, files, homscreen icons and simply flash to CM10?
I am on the KOBE build, and wanted to know will I have things like HWA with the generic CM9 build...is there any advantage of the generic CM9 builds? Also will I be able to go to settings->:system updates and update using CM9's update service?
My battery life stinks on CM9!
zetsui said:
what's the consensus about stability, supprot development and battery life? It seems like CM7 offers the most battery life, CM10 is still unstable and CM9 has hardware acceleration but battery drain. I am on CM9 and wondering whether I should move forward to CM10 or just keep waiting for Qarx to release better releases?
Also is there a way, on my phone, to be notified of build releases?
What is the difference (I have a Bravo) between Kobe and Qarx builds? I have been using Kobe can I just flash to Qarx?
Also if I'm upgrading from CM9 to CM10 is there a way to keep my settings, files, homscreen icons and simply flash to CM10?
I am on the KOBE build, and wanted to know will I have things like HWA with the generic CM9 build...is there any advantage of the generic CM9 builds? Also will I be able to go to settings->:system updates and update using CM9's update service?
My battery life stinks on CM9!
Click to expand...
Click to collapse
Cm9 was alredy left in the past, there will be no more changes to fix battery drain, you should move alredy to cm10, the problem is present but it still has support from devs.
In the lastest build from quarx for bravo, bravo rom updater is working, but the app says defy rom updater and you just need to change some things inside config to make it work
josuearisty said:
Cm9 was alredy left in the past, there will be no more changes to fix battery drain, you should move alredy to cm10, the problem is present but it still has support from devs.
In the lastest build from quarx for bravo, bravo rom updater is working, but the app says defy rom updater and you just need to change some things inside config to make it work
Click to expand...
Click to collapse
For the rom updater do you have the thread for how to change the config file? I can't seem to find it on google.
Also no way to set the number of homescreens on cm10? Any other big changes they are looking forward to? That already seemed to slow down my bravo more than cm9.
Say I want to try to flash CM7 Kobe...could I simply do what I did for upgrading CM9->CM10..wipe the cache/davlik
So I'm on CM10 right now. Can I wipe the cache/davlik and flash the CM7 nightly/gapps?
There is no smartass profile on the bravo. Can I add it somehow?
I flashed CM10 fine with CWM. Only did a cache/davlik
Some people recommend a factory reset though? Why is that? I mean why go through the hassle of changing all your settings and reinstalling all your apps? I find it that I can't titanium restore my apps because the googleapps store from cm9 has a different account id than the current google apps installation on cm10.
Much slower startup too
zetsui said:
For the rom updater do you have the thread for how to change the config file? I can't seem to find it on google.
Also no way to set the number of homescreens on cm10? Any other big changes they are looking forward to? That already seemed to slow down my bravo more than cm9.
Say I want to try to flash CM7 Kobe...could I simply do what I did for upgrading CM9->CM10..wipe the cache/davlik
So I'm on CM10 right now. Can I wipe the cache/davlik and flash the CM7 nightly/gapps?
There is no smartass profile on the bravo. Can I add it somehow?
I flashed CM10 fine with CWM. Only did a cache/davlik
Some people recommend a factory reset though? Why is that? I mean why go through the hassle of changing all your settings and reinstalling all your apps? I find it that I can't titanium restore my apps because the googleapps store from cm9 has a different account id than the current google apps installation on cm10.
Much slower startup too
Click to expand...
Click to collapse
The easiest way to check for updates is to check up on the forums where updates/changelogs are being posted.
For homescreens in cm10, I don't use trebuchet. Alternatively, apex launcher and nova allow you to change the number of homescreens.
Personally, I wipe cache/dalvik and wipe data each time I flash roms. It just seems safer that way, even though it's a pain to restore. Can you explain the app id problem you're talking about?
Governors are found in the development section of bravo forums, posted by skeevy420.
Dr. Orange said:
The easiest way to check for updates is to check up on the forums where updates/changelogs are being posted.
For homescreens in cm10, I don't use trebuchet. Alternatively, apex launcher and nova allow you to change the number of homescreens.
Personally, I wipe cache/dalvik and wipe data each time I flash roms. It just seems safer that way, even though it's a pain to restore. Can you explain the app id problem you're talking about?
Governors are found in the development section of bravo forums, posted by skeevy420.
Click to expand...
Click to collapse
So I remember from stock->cm9 when I tried to restore my apps via titanium backup (and maybe in retrospect I erred when I tried to restore google store) there was some difference in the google store id off my old phone and my new phone's google store account on cm9...the difference in the store ids between my old apps and my new apps wouldn't allow me to authenticate all my applications. That and a lot of apps failed on startup because of it. Basically I dont think there is an easy way around reinstalling everything between cm9 and cm10
zetsui said:
So I remember from stock->cm9 when I tried to restore my apps via titanium backup (and maybe in retrospect I erred when I tried to restore google store) there was some difference in the google store id off my old phone and my new phone's google store account on cm9...the difference in the store ids between my old apps and my new apps wouldn't allow me to authenticate all my applications. That and a lot of apps failed on startup because of it. Basically I dont think there is an easy way around reinstalling everything between cm9 and cm10
Click to expand...
Click to collapse
Hmmm. The only issue I've had is trying to restore system apps/data between android 2.3.x and 4.0.x/4.1.x. Never had problems with restoring various other apps. That being said, you shouldn't have an issue restoring any apps from ics to jb.
Don't restore the google play store. That's a system app and I think that's why you've had problems. Just flash gapps when you flash roms. You can then do batch restore in titanium and it will restore your missing apps/data. I think that should fix the problems you've been having.
zetsui said:
For the rom updater do you have the thread for how to change the config file? I can't seem to find it on google.
Say I want to try to flash CM7 Kobe...could I simply do what I did for upgrading CM9->CM10..wipe the cache/davlik
So I'm on CM10 right now. Can I wipe the cache/davlik and flash the CM7 nightly/gapps?
There is no smartass profile on the bravo. Can I add it somehow?
I flashed CM10 fine with CWM. Only did a cache/davlik
Some people recommend a factory reset though? Why is that? I mean why go through the hassle of changing all your settings and reinstalling all your apps? I find it that I can't titanium restore my apps because the googleapps store from cm9 has a different account id than the current google apps installation on cm10.
Much slower startup too
Click to expand...
Click to collapse
Always factory reset when switching the rom base; eg. CM7 to CM9 or CM10. The reason is that the apps use the same filenames for sqlite databases, which don't have the same values from CM7\Miui\9\10\stock\MS2. That's where all the bugs come from when you don't wipe data\factory reset.
Google "fixed" Play to make it like that. If I remember correctly, there's an option in TB Pro that allows you to change the market id to your current rom's id. Under Batch\Market, if memory serves me well.
SmartassV2 is in the DX Gov pack. A trick is to just push it to /system/lib/modules/cpufreq_smartass.ko and overwrite the default smartass module with V2, since they use the same values to be tweaked you'll be able to configure V2 this way. This trick doesn't work with boostedass to overwrite boosted; only smartassV2 over smartass works.
Smartass sucks and is bugged by not using the 2nd vsel profile. Use SmartassV2 or Boosted. Oddly enough, I've found that if I use boosted\smartassV2 in combination with the vsel settings of [email protected]\[email protected]\[email protected] I get better battery life than when using [email protected]\[email protected]\[email protected] since 700mhz can handle more crap than 600 and doesn't need to jump up to vsel3 for greater processing power. Hell, I get 24 hrs easily like that and I use a Live Wallpaper (Galaxy Pack, its awesome so go buy it; Have Planet Pack from the same dev and its awesome as well).
You can speed up the startup by disabling the boot animation, removing unused system apps, using V6 properly, using F The Logs mod. Set the Governor to Ondemand\Performance\UserSpace (performance\userspace force it to use vsel3 exclusively) in the bootmenu for booting up and use something like NoFrills\CM Performance Menu\SetCpu to change to boosted\smartassV2 once you're fully booted and in the system. Another good tweak is to modify the sio scheduler scripts. I've done plenty of posts on how I mod bootmenu scripts to fix sio and to make it work better. The sio fix will give you much faster read times for the system memory (twice as fast for some apps, literally twice).
You can use the /system/bootmenu/scripts/overclock.sh and /system/bootmenu/config/overclock.conf from my latest CM7 Kang to apply the sio tweak. Just replace them before you flash the rom or adb push with 0777 permissions.
skeevy420 said:
Always factory reset when switching the rom base; eg. CM7 to CM9 or CM10. The reason is that the apps use the same filenames for sqlite databases, which don't have the same values from CM7\Miui\9\10\stock\MS2. That's where all the bugs come from when you don't wipe data\factory reset.
Google "fixed" Play to make it like that. If I remember correctly, there's an option in TB Pro that allows you to change the market id to your current rom's id. Under Batch\Market, if memory serves me well.
SmartassV2 is in the DX Gov pack. A trick is to just push it to /system/lib/modules/cpufreq_smartass.ko and overwrite the default smartass module with V2, since they use the same values to be tweaked you'll be able to configure V2 this way. This trick doesn't work with boostedass to overwrite boosted; only smartassV2 over smartass works.
Smartass sucks and is bugged by not using the 2nd vsel profile. Use SmartassV2 or Boosted. Oddly enough, I've found that if I use boosted\smartassV2 in combination with the vsel settings of [email protected]\[email protected]\[email protected] I get better battery life than when using [email protected]\[email protected]\[email protected] since 700mhz can handle more crap than 600 and doesn't need to jump up to vsel3 for greater processing power. Hell, I get 24 hrs easily like that and I use a Live Wallpaper (Galaxy Pack, its awesome so go buy it; Have Planet Pack from the same dev and its awesome as well).
You can speed up the startup by disabling the boot animation, removing unused system apps, using V6 properly, using F The Logs mod. Set the Governor to Ondemand\Performance\UserSpace (performance\userspace force it to use vsel3 exclusively) in the bootmenu for booting up and use something like NoFrills\CM Performance Menu\SetCpu to change to boosted\smartassV2 once you're fully booted and in the system. Another good tweak is to modify the sio scheduler scripts. I've done plenty of posts on how I mod bootmenu scripts to fix sio and to make it work better. The sio fix will give you much faster read times for the system memory (twice as fast for some apps, literally twice).
You can use the /system/bootmenu/scripts/overclock.sh and /system/bootmenu/config/overclock.conf from my latest CM7 Kang to apply the sio tweak. Just replace them before you flash the rom or adb push with 0777 permissions.
Click to expand...
Click to collapse
WOW That is amazing! Do you think that range between VSEL 2 and VSEL 3 with smartass is going to be consistent across different devices?
zetsui said:
WOW That is amazing! Do you think that range between VSEL 2 and VSEL 3 with smartass is going to be consistent across different devices?
Click to expand...
Click to collapse
Most devices have 4+ vsel slots. Moto phones are screwed by the bootloader\limited Moto Kernel features.
It should be. The thing with the bravo (when tweaking governors) is trying to find the magic values that use vsel2 more than vsel3 and still provide a smooth ui. The reason that a 700mhz vsel2 works good is that the Bravo comes with a stock vsel3 of 800mhz. CM7\9 work\use resources much better than our stock Froyo making that 700mhz perform like 800mhz on a stock rom.

[Q] Problem with Franco kernel and Superuser

After a long time thinking about it, I finally decided to try to root my Nexus 4 and install the Franco kernel. I wanted to do this mainly to get some control over the audio output of my device.
The amazing Wugfresh Toolkit got me up and running as root. I then used the Cyanogen auto-installer to install Cyanogenmod 11. I was very happy, and went ahead and downloaded the paid version of the Franco Kernel Updater from the Play store.
All good, but then when I went to lauch the Franco Kernel, I got an error saying 'You're root, but Superuser seems to be denying access. Open Superuser, choose 'forget' and come back to the Franco Kernel and you will likely be asked to allow it'.
So I went to Superuser (took me a while to find it because it used to be an icon on my desktop but it seems that it went away after I installed a custom theme, and I found it only at the bottom of the settings list). I couldn't find anything about 'forgetting', but I could see a log that showed 'deny' then 'allow'. So I went back to to the Franco app and voila! It was open and allowed me to look into all the different functions.
Using the video which is up at the Franco Kernel page at the Play store as my guide., I tried to go into 'Kernel Settings' to access those audio controls... and strangely, there were only 4 items there, the vibration control and 3 others. None of the audio control choices were there.
I thought I had to flash the Kernel so I went ahead and did that. After restart, I again got the 'Superuser' access error. I opened Superuser, but this time I could not get it to 'allow' the Franco Kernel. I could see the log with lots of 'Deny' events. I then did something I probably shouldn't have - I clicked the 'trash' icon. Now, it just says 'There are currently no Superuser app policies'.
So I'm at a standstill. I'm not a huge tech guy but I thought I would give this a try because how else will I learn, right?
Can anyone help me figure out
a) How to simply get the Franco Kernel app open again (by configuring Superuser to stop denying it), and
b) Why I can't see those audio controls in Franco Kernel?
Sorry for such a long post
Nick
Wow.
I saw that there was an option to 'Disable' Superuser permissions. So I tried that, but the Franco Kernel error message still popped up.
I went back to Settings to open Superuser and reset it to where it was... and now the Superuser icon has disappeared from the list at the bottom of the Settings page!
It doesn't show up in the list of Apps either (but it never did, even when I was searching for it earlier and found it on the Settings page).
CyanogenMod has their own implementation of superuser. And as such they can put it in settings instead of in an app.
Here is how you re-enable the superuser menu http://forum.xda-developers.com/showpost.php?p=39903306&postcount=5
As for your how to allow root action, see if there is an option in the superuser menu for something like a default action and make sure that it's set to ask for permission.
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
SMillerNL said:
Here is how you re-enable the superuser menu http://forum.xda-developers.com/showpost.php?p=39903306&postcount=5
As for your how to allow root action, see if there is an option in the superuser menu for something like a default action and make sure that it's set to ask for permission.
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
Click to expand...
Click to collapse
Thanks a lot for the response. I was able to tap 7 times and get back to Develope Mode. I then clicked Developer Options and turned it 'on' as instructed. However, in the long list of items on that 'Developer Options' list, I could not find anything that says 'Root Access'.
Can you give me any indication where 'Root Access' can be found?
Thanks again, I will try to Google it in the meantime.
Unfortunately, I just cannot get Superuser to allow the Franco request. I can see the 'deny' event and I have played with everything available to me via Superuser-->Settings, but there's nothing there that says 'Forget', which the error message from Franco tells me to look for, and there's nothing that says 'Permissions' or anything else with which I can allow Franco!
tradernik said:
Unfortunately, I just cannot get Superuser to allow the Franco request. I can see the 'deny' event and I have played with everything available to me via Superuser-->Settings, but there's nothing there that says 'Forget', which the error message from Franco tells me to look for, and there's nothing that says 'Permissions' or anything else with which I can allow Franco!
Click to expand...
Click to collapse
When you open the superuser tab of the settings app, you should get a list of all allowed and denied apps. When you then long-press on one of the apps, you get another window where you should be able to deny access (to the apps that are allowed) or vice versa
Moreover, Franco kernel is not officially compatible with cm, so don't expect a bug-free experience even if you get it working.
Sent by carrier pigeon
Isn't Franco recommanded only for AOSP roms ?
laufersteppenwolf said:
When you open the superuser tab of the settings app, you should get a list of all allowed and denied apps. When you then long-press on one of the apps, you get another window where you should be able to deny access (to the apps that are allowed) or vice versa
Click to expand...
Click to collapse
Thanks for the response. Unfortunately, when I open SU, the main window is empty and there's a message saying
"There are currently no Superuser App policies".
Trying to open Franco and allowing SU to deny it doesn't populate this window - it just says the same thing. When I click on Settings or Logs in SU, I can see the logs with the denial events. Even long pressing on those doesn't pop up a box which allows me to give Franco access.
Any thoughts?
klvnhng said:
Moreover, Franco kernel is not officially compatible with cm, so don't expect a bug-free experience even if you get it working.
Click to expand...
Click to collapse
I see. Okay, I wasn't aware of that.
It looks more and more like I am going to let Wugfresh re-configure my phone. I am assuming that in its current state, I can ask Wigfresh to just re-do the root process. Everything was going great until i installed Cyanogen and then Franco.
As an aside, rooting the phone has solved a problem I was having with my Gmail app. One initial startup each day, I would have to do a restart to get the Gmail app to pull emails in. It was always exactly two starts that were necessary, and it always worked on the second start. The native Andorid app which was handling my Hotmail didn't have that problem.
So rooting has been a positive for me so far.
AndyTimE said:
Isn't Franco recommanded only for AOSP roms ?
Click to expand...
Click to collapse
Aha, okay. Well, maybe the thing for me to do is let Wugfresh re-do the root process and then try an AOSP ROM. Of course, the thing about CM is that there was that handy self-installer.
This is a slippery slope, I can see that. I have seen a few good guides here for doing this stuff manually. Maybe the time has come for me to really figure it out...
In fact the phone is definitely a bit unstable now. It's working fine but the screen is flashing at me a lot. The Swiftkey keyboard intermittently disappears when I am writing an email or a text.
I think I'll start over again. If possible, can someone confirm for me that I can just use the Wugfresh toolkit and ask it to do the root process again from the phone's current state, or do I have to do a restore back to factory and then do the root process again from there?

Uninstalled and reinstalled xposed to be able to login to snapchat, broken ex kernel

Ok well, I had xposed framework installed on my 6P. I also have ElementalX kernel installed. To login to snapchat I had to uninstall xposed, login to snapchat and then re-install xposed. After doing this the EX Kernel Manager app would not let me change a lot of settings. Cluster 2 governor would also be N/A and I couldn't change the Max CPU freq for both clusters. Also I couldn't disable/enable hexacore mode. Any help would be greatly appreciated.
Thanks.
Um, What exactly are you asking for help for?
HesThatGuy said:
Um, What exactly are you asking for help for?
Click to expand...
Click to collapse
Oh how I can fix the problem, it's stopping me from changing settings. Also something more to add, it'll automatically changed the Max CPU frequency, also it freely allows me change the min freq but not max.
The problems you have described relating to ElementalX & EX kernel manager aren't because of Xposed.
Regarding cluster 2(big cores) you weren't allowed to change the settings for those because of thermal throttling. So make sure your is phone is cool when trying to change the settings for the cores.
Side note: Also make sure that you touch the icon next to the setting so that it turns blue and will apply the setting on boot.
HesThatGuy said:
The problems you have described relating to ElementalX & EX kernel manager aren't because of Xposed.
Regarding cluster 2(big cores) you weren't allowed to change the settings for those because of thermal throttling. So make sure your is phone is cool when trying to change the settings for the cores.
Side note: Also make sure that you touch the icon next to the setting so that it turns blue and will apply the setting on boot.
Click to expand...
Click to collapse
I'm pretty sure it's not because of thermal throtlling, because I'm only at around 40C. It seems a little suspect that just after I uninstalled and re-installed xposed that it stopped functioning as it did before I did that.
Well, with a case like yours I would advise 2 things.
1.) Try to cool the phone down, change the settings, and see if they stick.
2.) Reflash the rom, login to your apps, then install xposed.
You could also try to clear all data from the ex kernel manager app, restart the phone and then try to apply your settings.
Should I restore to backup that I have? It's after I install xposed but before I root and install elementalx.
Sent from my Nexus 6P using XDA-Developers mobile app
You can try that, but I would suggest that you start completely over and clean flash.
Ok so, I flashed stock again, installed xposed, rooted and then installed elementalx, it is still being "buggy". Doesn't let me really set the max freq. Automatically changes it all of the time on both clusters too.
Sent from my Nexus 6P using XDA-Developers mobile app
Hmm, I don't understand how you could have this problem going on considering that I'm running xposed and elementalx on my phone and my settings stick. Is it possible that you aren't touching the icon so that it applies the settings on boot?
What do you mean?
Sent from my Nexus 6P using XDA-Developers mobile app

Fix lag and wifi rest on reboot problems after root

The ENGBOOT bootloader sets a couple of settings that cause extreme lag and reset of wifi settings on every boot.
You can fix them by doing the following:
.1 Install Busybox using the Busybox app from the Play Store into /system/xbin - you have to specify this install location manually or the install will fail.
.2 Download a CPU manager such as Kernel Manager or TricksterMod from the Play Store and set the CPU governor to "interactive" and set the app to set the governor on every boot -- this will fix the lag.
.3 Get the Build Prop Editor app from the Play Store and set “ro.securestorage.support” to “false” -- this will prevent your wifi settings from resetting on reboot.

Categories

Resources