Hi friends. I am using nadia kernel and I flashed your 18000mhz 633mhz script. My questions are.
Must I uninstall synapse apk which come with nadia kernel? Because when I open it I think script options changing am I wrong?
And second question charging current is about 2100mA is it cause any problem?
And last one how can I check cpu voltage hertz etc.
Sorry for this silly questions. Thanks so much for this great work :good:
Must I uninstall synapse apk which come with nadia kernel? Because when I open it I think script options changing am I wrong?
And second question charging current is about 2100mA is it cause any problem?
And last one how can I check cpu voltage hertz etc.
Sorry for this silly questions. Thanks so much for this great work :good:
Generally, synapse should not be used along the scripts as it MAY alter my settings. Synapse remembers settings after reboot and when you start the app it asks what to do with them. You may also disable it's set_on_boot option, but then why use the program at all.
As to the charging - unless your charger is broken, you should have no problem.
CPUTableau from OP will let you check frequencies, active cores and temperature in realtime. I don't know any app that displays it in realtime, but you can use various apps to just check voltage table, trickstermod being one of them.
I use 1800 script first its working at 1800mhz but few minutes later otomaticly change to 1600mhz where am i wrong?
You probably have another app or script changing it after boot. Matt's scripts runs during boot it'll not be able to control anything after.
Try to reflash latest Nadia kernel and after reboot flash my script again.
Remove any other software that alters cpu frequencies, if you are uncertain if you have any, provide your apps list or screenshots from app drawer.
The problem is in the /sbin/Nadia.sh shell script executed post boot after the init.d scripts, one has to use SManager or ROM toolbox to run those after a minute or 2 of boot completed flag.
Fired from my RPG with auto targeting
Maybe one could also edit the script and add a sleep delay of 120 for example
Edit: this could also delay the scripts executed after the edited one. Then one would need to create another script, which executes the original script by adding an & at the end of the call. The original script should be moved outside of init.d then
Last edited:
That isn't helping there, the problem was that the shell script ran after init.d scripts finished, the developer has acknowledged and solved it, but due to being busy, just is having a bit of delay with Release.
Edit : that your method seems useful, maybe someone using a Touchwiz ROM for now can a give a try to it. I remember @ph03n!x is using Touchwiz ROM+Nadia kernel for now, so maybe he can test.
Fired from my RPG with auto targeting
Last edited:
Ah
I thought that he already released the fixed kernel version. My bad then.My script has the 60s delay but it's useless in this case. Smanager is the temporary answer and it is easy for everyone to use - I will not release new script version just to get around that bug, just to do it all over again when fixed kernel is released
Thank you @DerTeufel1980 for taking time to answer here in my thread
I wish you would release a kernel for Note3 I would be happy to test it for you
@DerTeufel1980 - the 'bug' with the Nadia kernel is that run-parts is called from a script called nadia.sh (in /sbin), and after running run-parts for init.d, the nadia.sh script sets default values for cpu frequency, governor, mDNIE, GPU voltages, and a few other parameters. So even if a script in init.d has a sleep of 120 or is executed with &, the values set from init.d will be overwritten by the default values in nadia.sh because after run-parts (and hence the whole init.d and scripts called through it) nadia.sh will still set the defaults before exiting itself. I had manually edited the initrd.gz and removed the default values from nadia.sh for my use (my post in the Nadia thread)...Ah
My script has the 60s delay but it's useless in this case. Smanager is the temporary answer and it is easy for everyone to use - I will not release new script version just to get around that bug, just to do it all over again when fixed kernel is released
Thank you @DerTeufel1980 for taking time to answer here in my thread
I would be happy to test it for you
Pafcholini had said that this has been modified for a future version that is still being tested, and the next release will not have this default value bug.
Last edited:
Before flash the scripts go to system/etc/init.d and delete 08nadia and 09nadia. Then go to Synapse/Settings and uncheck set on boot. Now go to recovery flash the scripts and enjoy it.
Powered by ET
LOL
Hey @Pafcholini,
Mate, can r7, in any way have a reason for "Ultra Power Saving Mode" not working? Or is DVFS disabler a culprit?
I've disabled MDNIE hijack. UPSM gets activated correctly but gives me a battery drain of 1% per hour for totally idle phone in night time. That is too much as it used to give me approx 2% drain in 24 hours earlier when I was on Phoenix 18.8 + Nadia r4.
Right now I am on DN3v5.5+update1 with Nadia r7. I've asked the same on DN3 thread but no response yet.
Any suggestion?
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone