yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] wase4711:
Are all these settings available in Kernel Manager, or are you using Synapse or something else?

thanks
[Nexus 6 Android Development] Psych0t1c20:
Will do. Stay tuned.
[Nexus 6 Android Development] jcrompton:
I have some observations and questions

I have been running the VRToxin ROM mentioned above with this ROM -- I think that ROM shows some promise (I have not had the loss of LTE, cellular data like I had with RR)

Unfortunately I still have the Synapse app not sticking so I have been trying to run a script which I have attached. The script works if I run from SManager but the device will sometimes be a little quirky after it runs - but I have shown a screenshot that shows that it is working.

The last screenshot shows how I place it in the system/etc/init.d folder (and changed permissions) ----- ANY time I do this for RR or VRToxin ROMs I get a boot loop upon reboot. What's wrong with my method or my script ? It is identical to the one in the OP except for some minor changes in CPU max and min)
[Nexus 6 Android Development] str8str:
If you have greenify installed unchecked gsm push option. 2. If you have power nap installed make sure gps and framework are whitelist. These will cause random reboots. Something to check if valid

Straight Shooter
[Nexus 6 Android Development] apophis9283:
There seems to be a solution that a user posted back a page or so. I should be able to implement it and make Synapse stick. Like I said. I doubt any development gets done until after the new year
[Nexus 6 Android Development] str8str:
Was looking and the ukm busy box is like twice the size of my busy box in xbin which is busy box x. Wonder why but gonna try x version in both and see

Straight Shooter

---------- Post added 20-12-2015 at 00:03 ---------- Previous post was 19-12-2015 at 23:17 ----------

Installed busy box x in both and still won't stick on reboot

Straight Shooter
[Nexus 6 Android Development] apophis9283:
You only need UKM if you are using Synapse app to control kernel settings
[Nexus 6 Android Development] klabit87:
Ok thanks! I thought so just wanted to be sure.

Thanks for the kernel! It is perfect for my daily use
[Nexus 6 Android Development] apophis9283:
I tried as well. Was not able to get anything going. It will be looked into after christmas break
[Nexus 6 Android Development] apophis9283:
Glad to hear. :) let me know if you need anything
[Nexus 6 Android Development] apophis9283:
If you get a chance you should checkout vrtoxin
[Nexus 6 Android Development] :
There is no reason really to replace UKM's busybox. Unless it begins to cause issues because the commands it uses begin to fail (this would be a universal problem).

The reason that UKM includes it's own busybox is to ensure that it is available. This makes UKM not depend on the user having busybox installed.

The other reason is that UKM use busybox heavily to perform it's work. There's no way for a script to directly access anything without using shell commands. To this end, the script relies on the output to be in a specific format. If that formatting changes, it often breaks the script. This means that the script is only really reliable when the shell commands have a constant/known output format. Hence, a known version gets bundled with the script.

Everytime that someone replaces the busybox binary or suggests deleting it, modifying it etc etc etc... I die a little inside.

I always assume that it's becuase they don't actually understand how/why it works or is setup like it is.... Unfortunately, these are forums and once someone posts something it has a way of turning into the gospel... even if the person originally posting it really didn't understand what they were talking about.

As to why they're different sizes... you can open a shell, cd to each one's directory and just run "busybox". This will output all of the available commands that can be passed to that particular busybox binary ie:'busybox echo' 'busybox chmod'. I'd put money on the smaller version having less commands, I think that busybox calls them applets or cmdlets or something catchy.

Almost every shell command that you have access to in android (besides the ones that are packed into the ramdisk) are provided by the busybox binary. The majority of the /*bin directories are just symlinks to busybox. When busybox is passed a token on the command line, it executes that command (if it's built-in to the binary). When it's called from a symlink, it checks the symlink name and executes the command based on that.

No real magic happening there.

---------- Post added at 08:23 AM ---------- Previous post was at 08:11 AM ----------

I can't download files right now as I'm deployed. If you put the script in a set of hide and code blocks in a reply here I'll take a look at it. If you go into a shell and run your script, it probably throws an error.

However, Don't use init.d if you can avoid it. It's deprecated and was always just kind of a hack on android. The way that it runs the scripts can cause the boot to hang as it doesn't run them in a seperate thread... It just hooked the init process, so any failures cause the init process to hang. If that makes sense.

If you have supersu installed, use su.d. It's automatic, you don't have to do anything. Just toss your scripts into /system/su.d if the su.d folder doesnt exist, create it and put your script there.

This will probably fix your issue.
[Nexus 6 Android Development] :
I can't download files right now as I'm deployed. If you put the script in a set of hide and code blocks in a reply here I'll take a look at it. If you go into a shell and run your script, it probably throws an error.

However, Don't use init.d if you can avoid it. It's deprecated and was always just kind of a hack on android. The way that it runs the scripts can cause the boot to hang as it doesn't run them in a seperate thread... It just hooked the init process, so any failures cause the init process to hang. If that makes sense.

If you have supersu installed, use su.d. It's automatic, you don't have to do anything. Just toss your scripts into /system/su.d if the su.d folder doesnt exist, create it and put your script there.

This will probably fix your issue.
[Nexus 6 Android Development] :
Just reading over it, I don't see anything wrong.

The su.d shouldn't cause a bootloop. It runs the scripts programatically based on intents. IF it's causing a bootloop, there's something being set in the script that is causing it.

Try opening a terminal emulator or using adb. Navigate to where you have that script and execute it there.

./script.sh

If yours is named sing.sh, do ./sing.sh

See if it causes any errors to be displayed, or if the terminal runs opens (never shows the echo at the end of the file)

Using an application like Smanager or the like can often supress errors.
[Nexus 6 Android Development] jcrompton:
Thank you and [MENTION=4392154]apophis9283[/MENTION]

Here is where the problem happened ---- not sure why but the latter one had a simple change that caused the crash ???

Initial (Works):

# Choose Hotplug. Only set one of the following to 1. All others must be 0.

echo 0 > /sys/kernel/intelli_plug/intelli_plug_active

echo 1 > /sys/module/blu_plug/parameters/enabled

echo 0 > /sys/devices/virtual/misc/mako_hotplug_control/enabled

echo 0 > /sys/module/autosmp/parameters/enabled

echo 0 > /sys/kernel/zen_decision/enabled

Latter (Crashes):

# Choose Hotplug. Only set one of the following to 1. All others must be 0.

echo 0 > /sys/kernel/intelli_plug/intelli_plug_active

echo 0 > /sys/module/blu_plug/parameters/enabled

echo 0 > /sys/devices/virtual/misc/mako_hotplug_control/enabled

echo 0 > /sys/module/autosmp/parameters/enabled

echo 1 > /sys/kernel/zen_decision/enabled

I was just trying to use Zen instead of BluPlug
[Nexus 6 Android Development] apophis9283:
Maybe theres an issue because I have zen as default anyway? Just woke up, busy day. I promise ill try and take a peek

Edit, you didnt change anything else?

# Choose Hotplug. Only set one of the following to 1. All others must be 0.

echo 0 > /sys/kernel/intelli_plug/intelli_plug_active

echo 0 > /sys/module/blu_plug/parameters/enabled

echo 0 > /sys/devices/virtual/misc/mako_hotplug_control/enabled

echo 0 > /sys/module/autosmp/parameters/enabled

echo 1 > /sys/kernel/zen_decision/enabled
[Nexus 6 Android Development] jcrompton:
That one change alone cause my phone to reboot if I run the script from terminal emulator or from ScriptManager.

Also [MENTION=4231562]Yoinx[/MENTION] One other notation ...... I have SuperSU 2.52 installed on VRToxin. There is not system/su/su.d folder thus I created and gave the entire folder 0755 permission. If I place my working script (the one where I haven't made changes in the Hotplug settings) nothing happens when I boot -- in other words the script doesn't run on boot up
[Nexus 6 Android Development] apophis9283:
Got my Resurrection Remix build to work. Im happy
[Nexus 6 Android Development] KonoeKyon:
The permissions needed for su.d is 0700, not 0755 according to the documentation from chainfire. Also the directory is /system/su.d/ not /system/su/su.d/
[Nexus 6 Android Development] jcrompton:
Thank you

Oh well, made charges, but still the script doesn't run
[Nexus 6 Android Development] apophis9283:
Ill get back to Singularity kernel after Christmas. Right now Im messing with an android powered box, using it for kodi. I have kernel source so I am gonna oc cpu and gpu and add a governor or two but because Im oc'ing I worried about heat. So I took 2 case fans and tied the wires together, then tied them to a usb end so I could plug it into the box. Then used pieces of cardboard to lift it up so the bottom fan could push air into the android box. Thats what Ive been doing all day
[Nexus 6 Android Development] Abaddon:
cool! what android box do you have? by the way does singularity work on the latest RR by andrew? :angel:
[Nexus 6 Android Development] apophis9283:
I have the MXQ s805. Im running my own build of RR, so yeah, should work perfectly.
[Nexus 6 Android Development] apophis9283:
Heres a picture of my creation. I call him CYCLOPS.
[Nexus 6 Android Development] dannycellestio:
LOL :D
[Nexus 6 Android Development] arifqur:
HaHa!

That's really some kit. Looks like it is turbocharged
[Nexus 6 Android Development] str8str:
Lol, someone has way too much time on their hands

Straight Shooter
[Nexus 6 Android Development] DreamFX:
I do the same thing. Whatevers lying around I make it work. I never liked android for kodi. I personally I like openelec. Runs like a champ on my raspberry pi 2.

---------- Post added at 09:30 AM ---------- Previous post was at 09:29 AM ----------

That thing looks like it's ready to take off and then land in water lol.
[Nexus 6 Android Development] apophis9283:
They dont have openelec thats official for my device. So 1) by running it as an app instead of an os, Ill be able to update :) and 2, im working on a kernel for it, android specific
[Nexus 6 Android Development] :
That's what I'm looking at getting for christmas. Pi2, case etc. Then running Kodi or Openelec on it.

I've had good experiences in the past with kodi/xmbc. Why do you prefer Openelec? Better performance? Better support?
[Nexus 6 Android Development] apophis9283:
Openelec is just Kodi running as the OS. Using kodi through Android its an app. So openelec would tend to be better, because you dont have all the android processes running in the background
[Nexus 6 Android Development] DreamFX:
Like Apop said it's a full kodi os. Performance is amazing if you only need kodi. I felt after trying all the other razp os's that kodi just didn't perform as well as an app. I can throw any file at it. I really enjoy it.
[Nexus 6 Android Development] jcrompton:
This has been a weird experience .... I had some problems trying to get this to work before in the init.d folder

Bottom line finally got my script to work with the system/su.d method .... BUT ... here is what I had to do to get it to work:

None of the older SuperSU's would work - 2.46.2.52, or 2.56

I had to install Chainfire's SuperSU 2.64 -- yeah I know it's part of the new systemless root idea -- but the result was getting my /su.d script to run correctly

Here is what is written about 2.64 in one place I read:

Whats New in SuperSU 2.62

– Installer adjustments

– Fixed some su.d scripts not running because of logwrapper bug

– Fix native NPE in username resolution

– Fixed several binary update issues

– LD_PRELOAD sanitization

– Improved dumpstate work-around

– Improved killing dead per-uid daemonsu

– Backuptool support for Lollipop, /system/su.d

– CM12 policy adjustments

– supolicy timing adjustment (Motorola Lollipop)

– rootfs remount issue fixed (HTC)

– Remove more competing leftover binaries

– Updated language files

– (C) 2015

This is what is in the XDA thread about this version:

http://xdaforums.com/showpost.php?p=64161125&postcount=3

Notes on 2.64+

There have been a lot of changes to the ZIP installer. Hopefully they won't break a lot of installs. If 2.64 works well, it is likely to be promoted to the "main beta" in place of 2.52, and the How-To SU document will be updated with the relevant information.

A major change in setup is that the ZIP installer will try to detect 6.0 firmwares that can be rooted without doing a systemless install. In other words, a root that modifies only /system, but not the boot image. If this is possible, the installer will install into /system (unless you override via "echo SYSTEMLESS=true>>/data/.supersu").

This may catch (a) firmwares that allow sepolicy reloading from /data but have a locked bootloader and (b) custom firmwares setup to handle this. Regarding the latter, while it is not as clean as systemless, those running custom firmwares are more likely to want to modify /system anyway, it is less likely to mess with updates to those firmwares, and it prevents the necessity of reflashing the ZIP after each kernel switch. Of course, the kernel's SELinux policies must support this! See this thread for details for devs.
[Nexus 6 Android Development] apophis9283:
Guess what guys. THERE IS AN UPDATE FOR SYNAPSE IN THE MARKET! I havent tried it yet but im about to

Still not holding settings. So we can rule out the app, either kernel or rom. If you update and it works, please list kernel/rom
[Nexus 6 Android Development] :
So an update (which may or may not have been aimed at fixing this issue) rules out the app?

That's a pretty weird thought process.
[Nexus 6 Android Development] apophis9283:
Actually with the other knowledge i have, i.e. i had it working perfectly awhile back before the update had already proven to me its not the app. Only if you were testing and trying things out. Yeah i guess it is weird

I even posted a video of me setting the settings and rebooting and settings stuck perfect, guess you missed that too

im actually leaning to the ROM as being the issue
[Nexus 6 Android Development] str8str:
Yes so am I kind of cause you were on a different rom when you had this working and I was on RR and it wouldn't but, being a kernel app it should be working with any really. I know some kernel apps are customized to work with certain kernels but generally work with any. Any roms I've used despair, RR, pure, synapse does not work. I haven't tried a different kernel thou I was on this one every time. You should try restoring the rom you had it working with and if it works try it again with that rom and a different kernel to rule that out. Some have said it was a busy box/su issue and to use your roms super user only but that didn't work for me either I have four super su versions and tried them all but no go. My guess is the app.

Straight Shooter
[Nexus 6 Android Development] chopt51:
Did you two break up? Hard to follow the team
[Nexus 6 Android Development] apophis9283:
No, and why does it matter?
[Nexus 6 Android Development] jcrompton:
Clearly!!! It's the app.... The app is supposed to be designed to hold settings and it doesn't , at least with most ROMs and in most people's hands. Even if "we" are breaking it's functionality ..... it shouldn't be so easy to break.

So to say it's anything but the app makes no sense at all to me

PS. Your video only showed that you had settings holding ... But did not go through the how
[Nexus 6 Android Development] apophis9283:
Then why was it working for me awhile back? Before the update? I rebooted several times and it kept the settings. Even made a video.

Need proof its NOT the app. Watch the video

https://www.youtube.com/watch?v=Jc3j3C-mlO0

I didnt do anything different. I think I had just switched to that rom. Point is it doesnt matter. You all can think its the app all you want.
[Nexus 6 Android Development] clothednblack:
Settings are holding while using a different kernel mod app, I believe that in its self points to the other app as not working properly. Just my opinion though.
[Nexus 6 Android Development] jcrompton:
Man no disrespect ..... I certainly appreciate your work BUT

Did you even read my post? I have used your kernel and tried to use Synapse for months and months, on probably 20 different ROMs. Synapse had never once held settings for me and I've only read one other poison comment that it did work, as far as holding settings.

Furthermore, I could watch your video 50 times and it still doesn't show HOW you got the app to work as it clearly is "supposed" to work but just plain ole doesn't
[Nexus 6 Android Development] apophis9283:
Trying to add 2 new governors, ELECTROACTIVE AND ELECTRODEMAND. Stupid -Werror-implicit-function-declaration error
[Nexus 6 Android Development] apophis9283:
I just flashed the ROM. It worked. The weird thing is after a few days, it would hold the settings but then you had to hit x. Then I switched ROMs. I am re downloading Chroma now. Im gonna test my theory.
[Nexus 6 Android Development] apophis9283:
I have proof positive now its the rom. Running resurrection remix, I NEVER GOT MY SETTINGS TO STICK.

BUT

Using chroma I set my settings rebooted and even though, it did not "entirely" keep my settings. All I had to do was hit X. Proving me right. As far as what I did. I flashed chroma, it started rebooting and what not so I went intop recovery wiped cache/ dalvik cache and fixed permissions. Then flashed ukm then kernel again. Rebotted into the rom and all I had to do was hit x. ONLY THING TO CHANGE was the ROM

Im pretty sure, if I hadnt wiped caches. It would have kept my setting properly

If you all absolutely want me to, I will get my wife to record the whole process, from wiping everything to flashing everything. The whole setup, and the reboot and finally the dramatic end where my settings stick :)
[Nexus 6 Android Development] Abaddon:
yeah I had the same issue with RR. settings won't stick. on other roms it does :fingers-crossed:
[Nexus 6 Android Development] apophis9283:
Thank you! Now people will take me seriously. Its the ROM.
[Nexus 6 Android Development] str8str:
I always took you serious but.. Why don't it work for others including myself on other roms? I've tried it on every rom I told you earlier using difference kernels settings etc even different android versions and would not hold settings. This is f....d

Straight Shooter
[Nexus 6 Android Development] jcrompton:
Like I keep saying .... I appreciate your work ..... Your work on Bliss, you kernel, and even ask the countless times you've helped me directly

But you are wrong here

I've tried ROM after ROM with many kernels. I have never once gotten synapse to stick, on most ROMs. So just because you got it to work on one ROM and not another (true statement) that does not make the statement that "it's not the app but, it's the ROM" a true statement. You can't make the assumption.

The app is designed to work .... Not just one ROM but not another

That's like saying that tires that fail on one car but not another ..... Oh it must for sure be the cars fault just because maybe it weighed more or cornered differently. Still could be poorly designed tires
[Nexus 6 Android Development] apophis9283:
Maybe its something in the rom. You cant assume its the app. I was using the same app on both ROMs. Yet one works and one doesnt. The only thing that changes for me is the ROM. How else am I to digest this information? As far as why it works for me and not others, its beyond me. I wish I knew, I would fix it. In the mean time. I have 2 new governors coming (hopefully) ELECTRODEMAND and ELECTROACTIVE.

Make sure you go into apps, find Synapse, click on it. Then go to permissions. Make sure storage is checked
[Nexus 6 Android Development] jcrompton:
I love you man !!!! You are like the ever ready bunny lol

Any chance you'd send me a link to your RR Build .... Someday I gotta learn how to do this myself so I can contribute more

---------- Post added at 12:14 AM ---------- Previous post was at 12:11 AM ----------

BTW. What did you mean when you said I hit "x" in the above explanation?
[Nexus 6 Android Development] apophis9283:
I plan on making a build tomorrow. If all goes well, I will upload it to a secret location and PM you the link, I like the guys over at RR and dont want any issues with them. Ill probably release a kernel tomorrow. Honestly it has 3 commits more than the last build but they are important. Basically

1 and 2 are the new governors. (If you are like me, I love new toys to play with). The third is important because it deals with how your phone deals with charging (overnight). As seen here.

https://github.com/team-vortex/Singularity/commit/1b2b5760551548fc44a5f0bfeadc284e7f3a1695

I just flashed a test build with the new governors and all seems well. I may even update the kernel tonight so I can do the rom tomorrow
[Nexus 6 Android Development] apophis9283:
Merry Christmas. Singularity V-1.5 is up. Enjoy the new governors.

[MENTION=230362]jcrompton[/MENTION] Sometime tomorrow. I will send you a link to my RR build in a message on XDA
[Nexus 6 Android Development] apophis9283:
Sorry duplicate post ignore
[Nexus 6 Android Development] apophis9283:
electroactive is causing reboots. BE AWARE. Ill fix it tomrrow.

Also, I will be rejoining TEAM BLISS. :)
[Nexus 6 Android Development] str8str:
Can I get version 1.3 with brick plug? Or if you want can you add it back to your built tomorrow? Either ways fine

Straight Shooter
[Nexus 6 Android Development] apophis9283:
Bricked should still be there
[Nexus 6 Android Development] jcrompton:
Hey thanks again for your work. I don't know if you celebrate holidays this time of year but I hope that you have a great season.

You rejoining bliss is only good news for those of us that have used this in the past.

I'd still like to try your RR build
[Nexus 6 Android Development] apophis9283:
:) Thanks

I have to fix this governor first. Its being a pita

I just dont get it. Why its rebooting. Driving me insane
[Nexus 6 Android Development] apophis9283:
I think the reason its rebooting is because it was missing some code, like elementalx electroactive has gpu boost. But in the kgsl.h it didnt define it, causing the kernel to panic and causing a reboot. Thats my theory anyway. Testing it now
[Nexus 6 Android Development] EvilDobe:
Oh forget about that lamesville electroactive. Everyone knows Alucard is where it's at. :)
[Nexus 6 Android Development] apophis9283:
We have that too :)
[Nexus 6 Android Development] EvilDobe:
I knows! I don't know why I like it so much. Probably goes back to my Castlevania days.
[Nexus 6 Android Development] apophis9283:
He also has a Hotplug I may bring it over if you wish
[Nexus 6 Android Development] EvilDobe:
If you want. I use blu_plug a lot but it would be interesting to use the duo as intended.
[Nexus 6 Android Development] apophis9283:
I took a break from electroactive and added it
[Nexus 6 Android Development] EvilDobe:
Maybe it's me but alucard doesn't show up in v1.5. In 1.4 it's below barry_allen but now it's gone. Flashed back to (stock rom first) then 1.4 just to make sure nothing funky happened & it's there on 1.4 but not 1.5. Do you see it?
[Nexus 6 Android Development] apophis9283:
I borked the code. Its fixed now. Release later today