yashsingh1/xdaforums huggingface dataset:
[Android Software Development] gorilla p:
I'm noticing a strange issue and a couple other people are having it as well.

When using Hells Doctor and Synapse, the Core0 is getting locked in at its max frequency. It will occasionally drop to it's optimal frequency (10600) if the governor has one. However it is not ramping down.

I tried multiple settings and governors.

I have tried max CPUs boosted=0

I have tried enabling/disabling multicore power saving, I have closed, reopened, uninstalled and reinstalled Synapse and the same thing is happening.

Now the kicker is that when I removed Synapse, adjusted 1 setting with Trickster and it started working fine again. I didn't believe the person at first as it sounded unbelievable that Synapse could have this kind of effect.

I will try a different kernel as well as a previous version of Hells Doctor to see if it changes anything I will update.
[Android Software Development] apb_axel:
Weird, I left it on that screen for about 20 minutes and never got this, I'll see what i can do.
[Android Software Development] fr3quency:
Yup, Paranoid3. Sorry, I didn't know it was ROM-related. :) Will post in the specific thread.
[Android Software Development] blusydays:
Well, after checking I've found that under Performance tab of the Slimkat and Kernel Tweaker, Core 0 shows 162 Mhz, but under Synapse it is always at 1512 Mhz.

Is there any log you want me to submit to you ?
[Android Software Development] apb_axel:
Thanks, the screenshot you posted was the log I needed :o
[Android Software Development] apb_axel:
New version is up:
[Android Software Development] fr3quency:
Can anyone suggest some settings to make the phone EVEN snappier? I don't care about battery.... ok I care a little. :P
[Android Software Development] Kaotiko77:
Very nice job, the new versions works great here. Thanks so much!

Ultraspeedy n⁴ powered by PSX v4.0.4 & AK EXODUS v227
[Android Software Development] apb_axel:
Alright I'm almost finished with gamma settings with the following profiles:

Any other of your favorite profiles?
[Android Software Development] ak:
Thanks you have doing a very good job ... [emoji106]

ak
[Android Software Development] jmtjr278:
I keep getting no UCI support detected. Using Franco. Is that the problem?
[Android Software Development] apb_axel:
Check in /system/xbin if you see the uci file, if it's not there the init.d script probably didn't do it's job.
[Android Software Development] jmtjr278:
No sir. No UCI file.

I will try to download again. Perhaps something got lost during transfer
[Android Software Development] apb_axel:
Does your ROM support init.d scripts? Check in /system/etc/init.d if your see the N4UKM file.
[Android Software Development] jmtjr278:
It is in there.
[Android Software Development] apb_axel:
You can also copy manually the the uci file in \data\N4UKM and place it in /system/xbin see if that works.
[Android Software Development] apb_axel:
I recommend updating Synapse to latest version, I reported a bug to the developer that was preventing gamma settings to work. More info here:

https://github.com/AndreiLux/Synapse/issues/30
[Android Software Development] EotT:
I encountered a problem when changing the cpu governor. After changing the governor, I get this in the Governor Tunables tab;

(images are clickable)

After I force close Synapse and restart it, everything is ok.
[Android Software Development] deani77:
I also get this error when changing to interactive gov but not on other governor

Sent from my Mako running CarbonROM + Moob Kernel
[Android Software Development] blusydays:
Hi [MENTION=5658634]apb_axel[/MENTION] :)

Can you add the possibility to bulk change the cpu voltages ?
[Android Software Development] apb_axel:
This only happens when Synapse is open right? I did try HellsDoctor R12 last night and noticed it wasn't ramping down correctly (haven't tried ak's latest), it's weird because before version 2.0 it was refreshing the frequency every 1 second (on my end it was ramping down normally) and on this version I raised it to 3 seconds to see if it helped but apparently made it worse. I'll try osmosis suggestion to lower it every .5 seconds on this next version to see if it helps.
[Android Software Development] gorilla p:
Well I'm not sure because it seemed that the freq would stick in Trickster info as well until a setting change was made in Trickster.

I just tested the previous Hells Doctor version and it's working fine.
[Android Software Development] osm0sis:
Yup that's exactly what I saw on the GN. The longer the refresh rate, the higher the reported frequency. :good:
[Android Software Development] apb_axel:
So maybe it's a HellsDoctor bug? I dunno. It can't keep the polling the frequency after Synapse is closed since the app has no running/background service apart from boot.
[Android Software Development] apb_axel:
It has to be a Synapse overhead thing, I even changed the code of polling the frequency to make it as simple as possible with absolutely no calculations/overhead on the script.
[Android Software Development] ak:
I don't think kernel related

ak@n4
[Android Software Development] apb_axel:
Thanks for the pic :). I'll try installing perfmon later today to see if I can make it behave more or less the same.
[Android Software Development] gorilla p:
I asked people to confirm in HD thread and have gotten confirmations of same issue and problem stops once trickster is opened and settings applied.

It almost seems like there is a hidden setting in Synapse that is being enabled and keeps Core0 at its optimal frequency.

Now it works fine with r11 but does this in r12. So I can only assume something may have changed with the r12 to prompt this bug.
[Android Software Development] apb_axel:
Thanks for the feedback, I'm currently running perfmon and Synapse side by side to see if I can make the polling as close as possible.
[Android Software Development] apb_axel:
New version is up & loads of fixes incoming! I managed to find out what was wrong with restoring profiles, the Hells_Doctor_Battery.tgz is only 5kb and was giving errors (tar: invalid magic), so know before restoring the profile it checks to see if it contains the correct files and then restores, if it's an invalid file it will notify the user. Also I lowered the polling of the CPU frequency as [MENTION=4544860]osm0sis[/MENTION] suggested (thanks bro!) to display correct values. As always please rate the thread and don't forget the thanks button! ;)
[Android Software Development] osm0sis:
Hey P.S. How'd you make it gray? I've been hoping for that awhile now. :D
[Android Software Development] ak:
Cm11 theme dark ui by thyrus.

ak@n4
[Android Software Development] osm0sis:
Damn I'm using KitKat White Holo in Carbon ROM and Synapse still shows up blue. SuperSU correctly shows white, so it must be something odd on Synapse's side. :confused:
[Android Software Development] ak:
No ... It's related to your theme. Do you have new cm11 t engine?

ak@n4
[Android Software Development] Pollie81:
core 0 still shows high frequency after update to 2.1 but what is the best way to update? I just flashed 2.1 with cache wipes before and after.

Verstuurd vanaf mijn Nexus 4 met Tapatalk
[Android Software Development] ak:
Right steps. for now do not worry with the question of cpu0. will be fixed.
[Android Software Development] osm0sis:
It does but the default theme in Carbon removes all the holo blue and replaced it with white, so I'm not sure why Synapse is still blue. Hmm.
[Android Software Development] ak:
you have to use thyrus dark theme without dark ui.
[Android Software Development] osm0sis:
But I don't wanna! :p

I just want Synapse to not be holo blue since nothing else in my ROM is. Oh well, maybe some day we can specify color in generate and the config files to dictate the header and pane colors, respectively. :)
[Android Software Development] scarcry:
I flashed 2.1 coming from 2.0 without wiping caches (couldn't find instructions whether that's necessary in OP).

core0 freq in synapse now seems to show much more realistic behaviour :)

haven't tried a synapse profile restore yet but good to know you managed to have the .tgz actually checked before the restore attempt :good:

Keep up the awesome work!

beamed from my Google NeXuS⁴
[Android Software Development] apb_axel:
Yeah you can just flash the zip without wiping caches or dalvik. Glad everything is working as intented :)
[Android Software Development] apb_axel:
Sometimes it depends on the governor scaling properties, try another governor or change the up threshold to see actual frequencies.
[Android Software Development] M3drvr:
Synapse keeps closing on me. I've flashed the latest AK kernel with the latest UKM on Slim 5.4. Upon opening synapse it immediately closes on me. I can never get into the app. I've tried uninstalling it, clearing data and reopening it but as soon as I grant it root, it will close. Any help will be appreciated.
[Android Software Development] apb_axel:
Can you grab a logcat right after Synapse closes on you to determine your issue?
[Android Software Development] M3drvr:
Okay give me a minute.
[Android Software Development] M3drvr:
Here is a logcat.
[Android Software Development] Walterwhite007:
delete
[Android Software Development] apb_axel:
Apparently it's a bug in Synapse.

E/prepareView->createObject (11605): Failure to create dynamic class element SPane due to java.lang.reflect.InvocationTargetException
E/prepareView->createObject (11605): Failure to look up dynamic class element SLiveLabel due to java.lang.ClassNotFoundException: com.af.synapse.elements.SLiveLabel

Maybe [MENTION=4167023]AndreiLux[/MENTION] can give us a hand.
[Android Software Development] Italico:
Proximity sensor seems to work now, although randomly. I will test it. It was my fault, 'cause I mess up some values in build.prop

Thank you for the Tasker suggestion, but I don't have the app
[Android Software Development] AndreiLux:
No idea. Reinstall the app. That error should not exist and no idea how somebody can even cause it.
[Android Software Development] M3drvr:
I've already tried that, several times. Same stuff happens.
[Android Software Development] apb_axel:
Maybe a clean ROM install?
[Android Software Development] M3drvr:
I'll think about it
[Android Software Development] AndreiLux:
Try clearing cache and dalvik cache. I'm interested in how this can happen, it should be impossible.
[Android Software Development] M3drvr:
Already done that. No help.
[Android Software Development] xenyz:
What happens if you don't grant it root?
[Android Software Development] apb_axel:
Hey [MENTION=3685904]ak[/MENTION] did the newest version of the script fix your previous errors with your flo?
[Android Software Development] gorilla p:
Perhaps try deleting Synapse folder as well? Idk if its related, but that fixed one of my issues.
[Android Software Development] M3drvr:
I'm gonna do a clean install first thing in the morning baby. Of that don't fix it then I'll try your suggestion.
[Android Software Development] scarcry:
I would take a nandroid and try deleting the synapse directory instead of going for a clean install first,much less work if it works out for you.

You can always do a clean install as a last resort.

beamed from my Google NeXuS⁴
[Android Software Development] M3drvr:
Well I have very little on my phone. No gapps even. Few apps. Clean flash is very little effort on my part.
[Android Software Development] scarcry:
kk well I was more thinking of if you perhaps had made changes to lots of settings already.

Just hope the clean flash of your ROM will fix your issue :)

beamed from my Google NeXuS⁴
[Android Software Development] mperezm77:
Hi,

I have installed Hells doctor R12 kernel with TARDIS and Synapse. Do I need to install the UKM v2.1? What is it for? The reason I'm asking it's because right now Synapse seems to have all the options available.

If I need to install UKM, do I need to uninstall TARDIS first?

Thanks!

Enviado desde mi Nexus 4 mediante Tapatalk
[Android Software Development] iCangFans:
my progem gne to use this script
[Android Software Development] apb_axel:
No you don't need to unistall TARDIS, the HellsDoctor's current UKM version is 2.0 so you'd have the latest which contains a lot of fixes if you flash 2.1.
[Android Software Development] apb_axel:
Can any Nexus 5 or Nexus 7 user share if everything is working correctly?
[Android Software Development] MotoFlasher:
Although I'm using at the moment fauxclock but have tested it on my N5.

Here is the result. Everything up to the error in the screenshot works. Busybox Stericson etc installed.
[Android Software Development] apb_axel:
Great! Thanks for the screenshot, I'll start working on those fixes :)
[Android Software Development] mperezm77:
I'm not sure I understood completely. Does it means that HellsDoctor R12 already includes UKM v2.0?

Enviado desde mi Nexus 4 mediante Tapatalk
[Android Software Development] gorilla p:
No. Kernel devs have to add commits I believe so that ukm works with it. I believe he meant HD r12 has the commits to be compatible with 2.0

---------- Post added at 12:54 PM ---------- Previous post was at 12:47 PM ----------

I have a question. When looking at trickster it shows much lower frequencies than synapse. Even with both open. The freqs that synapse is reporting are higher.

This is on AK kernel.

Trickster shows core0 fluxuating between 486-918. Synapse shows 918-1350 (max). And other cores coming in for a second or two. Idk why but they're reading different frequencies
[Android Software Development] CatsAreGods:
I've been having a weird problem myself. Haven't been able to successfully flash any 2.x script at all, TWRP tells me "failed" in red and I have to keep going back to 1.7. Running stock Nexus 4 ROM, 4.4.2 with a variety of kernels, this happens with Hells Doctor, Franco, and faux.
[Android Software Development] mperezm77:
Then Synapse it's working without installing UKM because the kernel has those commits, but I still can update it manually by installing HKM v2.1?

Enviado desde mi Nexus 4 mediante Tapatalk
[Android Software Development] apb_axel:
Actually UKM is independent from kernel, kernels don't need any commits to make it work, you can flash it on any kernel and theoretically it should work. What barome has done is simply include it in his kernel zip. That's why if you flash the latest version it just overrides the one included in HellsDoctor.
[Android Software Development] apb_axel:
Yeah we believe that Synapse may have a bigger impact on CPU than trickster, Andrei already said he's looking at ways to reduce it let's hope he succeeds.
[Android Software Development] apb_axel:
Weird I didn't make any changes on the updater-script for v2.x to make it behave differently, I'll look to see if I find anything.

Can anyone else report if flashing the UKM on TWRP fails as well?
[Android Software Development] Pollie81:
nope, running latest TWRP here and never had any problems flashing UKM.

one strange thing I do have is that eveytime I open synapse I have the 'V'and 'X' on top of the screen. the one you get when you change something and can save it..

Verstuurd vanaf mijn Nexus 4 met Tapatalk
[Android Software Development] apb_axel:
That only happens when your current settings differ from the last saved values in Synapse, usually if another kernel manager is running as well or when flashing another kernel, no biggie.

Anyway thanks for your confirmation on TWRP, I installed it just to try it and it works with v2.1. Maybe bad file? Download UKMv2.1 again and check md5 checksum [MENTION=4974127]CatsAreGods[/MENTION]
[Android Software Development] Pollie81:
I understand, now I think about it.. maybe it's the inbuilt kernel manager in N5 exp ROM.

doesn't matter anyway, it doesn't change anything.. it's just showing the V and X every time.

Verstuurd vanaf mijn Nexus 4 met Tapatalk
[Android Software Development] CatsAreGods:
Checked the md5 and all was well. Wrote down the actual error this time:

set_perm: some changes failed

E: error executing updater binary

I checked out /data/UKM and it looked reasonable, but I obviously don't know all the details of what's supposed to be there. Maybe I should wipe that directory and flash again?

Thanks for taking a look at this, it's mystifying!
[Android Software Development] apb_axel:
Found something, apparently only happens in stock ROM. Can you check if you have a "install-recovery.sh" file in /system/etc
[Android Software Development] CatsAreGods:
Yes, it's 629 bytes, dated 5/22, and mode 755.
[Android Software Development] apb_axel:
Alright check this link, apparently that file has a protection to disable the ability of mounting /system which prevents flashing. Hope it helps.

http://xdaforums.com/showpost.php?p=44913304&postcount=8
[Android Software Development] apb_axel:
Alright I've fixed all your reported errors, also I noticed the Hotplug tab in your pic was empty so I did a little digging and found out your kernel (UBER kernel) uses MSM MPDecision which I already had in the script but for some reason was not detecting it, long story short a bug on my part so next version you should be all set. Let me know on version 2.2 if everything is ok.

P.S. Nice background wallpaper ;)
[Android Software Development] CatsAreGods:
Nice find, but I made the file unexecutable and then renamed it, rebooted into recovery and still having the problem. Also tried mounting system by hand, still no luck.
[Android Software Development] apb_axel:
Aww I thought that would be it :(. I'll keep digging.
[Android Software Development] osm0sis:
Recoveries have been updated to be less forgiving about setting permissions on missing files lately. I'd start look there. :)
[Android Software Development] apb_axel:
It's strange he can flash v1.7 fine but can't on v2.x and I haven't changed anything on the updater-script.
[Android Software Development] osm0sis:
I'll lend you another set of eyes and see what I can see. :)
[Android Software Development] apb_axel:
Thanks buddy :)
[Android Software Development] osm0sis:
Neither of these are in the zip, or at these locations, at least not on a fresh install:

set_perm(0, 0, 0755, "/system/etc/init.d/UKM");
set_perm(0, 0, 0755, "/system/xbin/uci");

Definitely what's throwing up the error. :good:

Edit: Nevermind, read it again and I see you're extracting them from the zip data dir. Hmm..

Edit 2: Okay my only guess is on devices with no init.d dir package_extract_file might not create parent directories so it isn't getting extracted so can't exist to have permissions set. Add lines to create the directory and hopefully it'll work:

run_program("/sbin/sh", "-c", "mkdir /system/etc/init.d");
set_perm_recursive(0, 0, 0755, 0755, "/system/etc/init.d");
[Android Software Development] apb_axel:
Cool I'll add it for my next release, strange though that he could flash it on a previous version.
[Android Software Development] apb_axel:
Ok just need confirmation if Nexus 7 is working correctly, anyone?
[Android Software Development] osm0sis:
System not getting mounted for some reason is your other possibility if that doesn't work. :)

You did it the way I do it though, so I'm not sure how that could happen.
[Android Software Development] CatsAreGods:
I had a crash a few days ago, so I might have a few differences from when I originally flashed 1.7.
[Android Software Development] ak:
N7 ok

ak@n4
[Android Software Development] apb_axel:
Great, thanks my friend! :D
[Android Software Development] apb_axel:
Ok running some tests so new version should be up soon, mainly some fixes for Nexus 5 users and a new feature. ;)
[Android Software Development] CatsAreGods:
I went through this thread more carefully. Thanks to osm0sis, I noticed that uci wasn't executable. Chmod 755, and Synapse 2.1 is working now, hurray!

I also noticed that init.d on my phone is a shell script and not a directory...not quite sure yet what to do about that one!

Thanks again to both of you for your patient efforts!
[Android Software Development] osm0sis:
So that was definitely the problem. :good:

What's in the init.d script?
[Android Software Development] CatsAreGods:
I renamed it and installed an app that enables init.d scripts. Here's what was in there:

#!/system/bin/sh

busybox mount -o remount,noatime,barrier=0,nobh /system

busybox mount -o remount,noatime /data

busybox mount -o remount,noatime,barrier=0,nobh /cache

BTW, that app (init.d toggler) installed a new version of that recovery script...go figure.
[Android Software Development] osm0sis:
Weird. So you must have gotten that script somewhere and that'd be what was interfering with the UKM install. Bizarre but good to know!
[Android Software Development] ak:
If you want, I have some new fck features implemented into new kernel, I can send you a pretest for implement it into the new UKM ... [emoji133]

PS

How I can reset synapse settings with new kernel flash?

I have see conflict sometimes with new features and tunables.

ak@n4
[Android Software Development] apb_axel:
Sure you can send me the pretest :). To reset you would need to delete the 2 files inside /data/data/com.af.synapse/databases which contain all saved values.
[Android Software Development] ak:
thanks a lot.
[Android Software Development] gorilla p:
New Synapse battery life profile for AK and Hells Doctor. I also updated the optimal battery life document with recommendation for ART rather than optimized dalvik. Latest Adreno drivers added as well.

All available on bit.ly/makostuff
[Android Software Development] apb_axel:
New version is up! :victory:, more fixes and a few new features just for you guys. In this version I hope to be confirmed that the Nexus 5 is working 100% (Nexus 7 was already confirmed), so the next few versions I will be adding a lot more features and probably more supported devices. ;)

As always please rate the thread and hit that thanks button! :D
[Android Software Development] M3drvr:
After a clean flash of Slim 5.6 +AK 268 + newest ukm I'm still having the same issue. Immediate closure of synapse. Here is the logcat. Hopefully that helps.
[Android Software Development] gorilla p:
Latest version appears to have solved the core0 issue. Everything looks normal.
[Android Software Development] karanrajpal14:
Can those SAI modules from semaphore kernel be implemented in synapse? They're really neat and handy.
[Android Software Development] ak:
no ... because synapse dont support services.
[Android Software Development] apb_axel:
So has any Nexus 5 user flashed the latest version and report if everything is working? :)
[Android Software Development] MotoFlasher:
Many many thanks for the new version. :good:

Everything works - except for "gpu governor". See Screenshots ...

Again many thanks for your effort. I look forward to use Synapse and UKM on the N5. :victory:
[Android Software Development] apb_axel:
No problem :). Can you send me your config.json file so I can have a look? It's probably a GPU governor that I don't have yet. It's located in /data/UKM.
[Android Software Development] gorilla p:
I had a few of those scroll bar error things as well, I just cleared data.
[Android Software Development] MotoFlasher:
No problem ... here is the file.

...gpu governor is ondemand ...
[Android Software Development] apb_axel:
Thanks, found out what the problem is, forgot to use a variable :p. Anyway it's fixed now, if you want I can send you the fixed file for you to replace and test.
[Android Software Development] aviz1911:
Oh man that was fast. Aren't you the fast running man from justice league :p
[Android Software Development] apb_axel:
:cool:. I imagine your kernel is having the same problems as well, it only happens when using Interactive GPU. I'll post all device files for you guys to replace but I've already included the fix for next version.
[Android Software Development] aviz1911:
Everything working fine now bro. All the tabs, and also the GPU governors. To make my kernel work perfectly with UKM I corrected all the frequencies :D and removed some that does not show up in synapse. Thanks for your work :D
[Android Software Development] apb_axel:
Cool, still if you need to add anything in your kernel that UKM doesn't have yet let me know so I can add it. ;)
[Android Software Development] aviz1911:
I should say "I'm speechless now" !! Thanks for you're offer mate xD cheers