I have seen so many people facing this problem. Since they used a rom that's build with dev_harsh1998 source code (before 13April). Then, i made this Thread about how the way to fix (trick) it.
Step :
1. Go to /sys/devices/system/cpu/cpu0 , and you will find file named 'online'
2. Open it and see if there listed as 0 (mean offline) change to 1 (mean online), save. Set permission file 'online' to r-r-r (read only).
* You have to do this in every reboot
Or
You can Flash this :
Set CPU0 AlwaysOn.zip
https://drive.google.com/file/d/0B6DpzXcsAckTYzduYUY0dnNnT0k/view?usp=drivesdk tested with twrp 3.1.0
* Make sure your system rom run Init.d in every reboot or turn-on "Emulate Init.d" through KernelAdiutor.
* Some Suggest if you still in Old Builds with min_freq 800mhz.
You can add 533333:75 , in KA/CPU/CPU Gov Tunables/target_loads. Between 1 and 800000.
Then, change the min_freq to 533mhz.
## For the latest Build Rom and you still facing this freq bug. Try change to 400mhz first and look to the core. Someone told it will make the first core online again. Then, after u do it. You can freely change the freq whatever u want.
### Latest build after 20170422 doesn't have this bug. Dev already solved it.
Hit Thanks if I help you
Not a good solution if we have to do the same thing after each reboot.
Actually there are two things here we need to fix .
1. CPU0 offline issue .
2. Frequency automatically goes up . I mean when we set max frequency to 800mhz , it automatically jumps to 1200mhz.
Harsh!t already provided a simple solution. We need to flash stock lollipop first to get latest firmware & modem . Then flash other rom. It will fix these issues.
I have not tried it yet , but I am going to download stock rom because I am facing these issues in official mokee rom.
@shivdroid, you should GIVE THIS A TRY too. This has the updated firmware files.
sasukay said:
@shivdroid, you should GIVE THIS A TRY too. This has the updated firmware files.
Click to expand...
Click to collapse
Thanks for these files . I will try it in free time . I will report back after flashing.
But a little bit confusion here . Since I don't want to go back to KitKat which file should I use ?
Do you know which flashable zip contains firmware/radio of stock lollipop rom ?
shivdroid said:
Thanks for these files . I will try it in free time . I will report back after flashing.
But a little bit confusion here . Since I don't want to go back to KitKat which file should I use ?
Do you know which flashable zip contains firmware/radio of stock lollipop rom ?
Click to expand...
Click to collapse
Yeah, the KK2L one. Actually, its me who has prepared those zips.
shivdroid said:
Not a good solution if we have to do the same thing after each reboot.
Actually there are two things here we need to fix .
1. CPU0 offline issue .
2. Frequency automatically goes up . I mean when we set max frequency to 800mhz , it automatically jumps to 1200mhz.
Harsh!t already provided a simple solution. We need to flash stock lollipop first to get latest firmware & modem . Then flash other rom. It will fix these issues.
I have not tried it yet , but I am going to download stock rom because I am facing these issues in official mokee rom.
Click to expand...
Click to collapse
I've already tried it. Still didnt work. Just to let u know. Everytime before i flash a rom, i will flash a firmware.zip (by @sasukay) lollipop first. Then, the rom. It has no fix. Im also flashed firmware.zip given by hasrhit, but still no luck. So, those trick is the last option to fixed it.
Flash it, then tell here. It fixed the cpu bugs or not. So, people will know.
sasukay said:
Yeah, the KK2L one. Actually, its me who has prepared those zips.
Click to expand...
Click to collapse
Yeah, thanks bro. I've used it always before flash a rom. It's helpes me down/upgraded base firmware ? Since im A6000+ user. If i A6000 user, i better choosen firmware from rahulsnair
GuestStar said:
I've already tried it. Still didnt work. Just to let u know. Everytime before i flash a rom, i will flash a firmware.zip (by @sasukay) lollipop first. Then, the rom. It has no fix. Im also flashed firmware.zip given by hasrhit, but still no luck. So, those trick is the last option to fixed it.
Flash it, then tell here. It fixed the cpu bugs or not. So, people will know.
Click to expand...
Click to collapse
Then a script would be better which execute on every boot set the value automatically.
I flashed mokee build today....
Full wipe
Flashed Kk2L.zip
Then Rom & other things.
But the frequency and core 0 offline issue is still there .
Now Going to try the full lollipop zip ...
Deleted
sasukay said:
@GuestStar, @shivdroid - I wrote the init.d script to automate the process of setting CPU0 online. Can you please test this for me. Its a flashable zip.
Click to expand...
Click to collapse
??
shivdroid said:
?
Click to expand...
Click to collapse
Working on it.
Still couldn't understand why it isn't working.
the 01cpuon init.d scipt
Code:
#!/system/bin/sh
#Sets CPU0 online
echo "1" > /sys/devices/system/cpu/cpu0/online
#Sets permission to r--r--r--
chmod 0444 /sys/devices/system/cpu/cpu0/online
updater-script
Code:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
package_extract_file("01cpuon", "/system/etc/init.d");
set_perm(0, 0, 0755, "/system/etc/init.d/01cpuon");
unmount("/system");
Can anyone help me with it.?
sasukay said:
Working on it.
Still couldn't understand why it isn't working.
the 01cpuon init.d scipt
updater-script
Can anyone help me with it.?
Click to expand...
Click to collapse
I can try to make it works
I've remake the flashable zip
Set CPU0 AlwaysOn.zip
Here :
https://drive.google.com/file/d/0B6DpzXcsAckTYzduYUY0dnNnT0k/view?usp=drivesdk already tested using twrp 3.1.0
Thanks to me and @sasukay for the Init.d script
@GuestStar, Gg bro. So, what I did wrong was I didn't mount the system correctly. Bro, but can you point out why this didn't work.
Code:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
Actually, I'm a newbie and picked that line from some other updater-script. So, technically it should've worked.
sasukay said:
@GuestStar, Gg bro. So, what I did wrong was I didn't mount the system correctly. Bro, but can you point out why this didn't work.
Actually, I'm a newbie and picked that line from some other updater-script. So, technically it should've worked.
Click to expand...
Click to collapse
Yeah, you forgot to mount system.
Wht do you mean dint work?
GuestStar said:
Yeah, you forgot to mount system.
Wht do you mean dint work?
Click to expand...
Click to collapse
Code:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
This didn't work for me. I tried to mount system with this command but the twrp recovery still showed error 6.
sasukay said:
This didn't work for me. I tried to mount system with this command but the twrp recovery still showed error 6.
Click to expand...
Click to collapse
Those command is right as well. If still didnt work. Then, the problem could be from the update-binary files
Have u looked into my zip i made.. To mount system i better used busybox/sbin. For update-binary i get from harsh flashable zip (the zip is about copying modules). I've tried to use that, and its works
GuestStar said:
Those command is right as well. If still didnt work. Then, the problem could be from the update-binary files
Have u looked into my zip i made.. To mount system i better used busybox/sbin. For update-binary i get from harsh flashable zip (the zip is about copying modules). I've tried to use that, and its works
Click to expand...
Click to collapse
Well thanks for the info. There were two things that I saw in your zip that weren't reqd. 1) online file was not reqd. 2) setting its permission to 644 was not reqd
Anyways, it is working. That will be enough for us.
sasukay said:
Well thanks for the info. There were two things that I saw in your zip that weren't reqd. 1) online file was not reqd. 2) setting its permission to 644 was not reqd
Anyways, it is working. That will be enough for us.
Click to expand...
Click to collapse
Yeah, i know it ? forget to remove. At the first time, i just want to make sure file online listed as '1'
Related
Could someone please post a step by step on how to properly install the speedy Gonzales script for us less savvy people. Thanks in advance.
You have to be rooted with tenfars recovery and the init hack: http://forum.xda-developers.com/showthread.php?t=1223771
Download the .zip file that says flashable in the title, it located at the bottom of first post. Move it to sd card. This one: http://forum.xda-developers.com/attachment.php?attachmentid=704624&d=1314689490
Open the System Recovery app and select Recovery Mode (unsure plugged in).
Select choose zip from sd card. Navigate to the file and flash it.
What part is the issue, let me know where you have questions.
Ok I am rooted and have tenfars recovery. Do I still need the init hack installed or just go ahead and install new script through system recovery. Confused on first part.
Yes you need the init hack. Its the first link I posted. Its same thing. Download zip. Move to sd. Boot into recovery, flash. May be able to flash the speedy hack right after, but id reboot first just to make sure.
You need to go back into the /etc/init.d folder and delete the kickasskernel and S00tweaks once everything is successfully flashed.
One last question. I notice that there are 3 init.d hacks do you use all 3 or just one. That's the only think im not sure of.
Which ever one you want, but only one. Each is different and the description should describe that difference. I am on the first one. Battery saver or what ever its called.
So after I install the script using the flashable zip am I supposed to have the "zipalign-dataapp.log." in my /data file? Or is that only if you do it manually?
dust. said:
So after I install the script using the flashable zip am I supposed to have the "zipalign-dataapp.log." in my /data file? Or is that only if you do it manually?
Click to expand...
Click to collapse
That's what the instructions say in the original post for speedy.
You know what sucks is that the guy who made this got bashed so much he pulled the script and closed the thread...
This is supposed to be a community you ask and answer questions it gets to the point were people are afraid to ask anything without searching for 3-5 days for something i don't understand why people on these types of forums bash each others work so much its ridiculous...that sucks i feel really bad for the OP of this script he was just trying something and he got the crap kicked out of him....venting
im not gettintg the zipalign logfile he mentioned. hmmm
nitwit said:
im not gettintg the zipalign logfile he mentioned. hmmm
Click to expand...
Click to collapse
I didnt at first either, but I didnt follow directions proper and do the init.d thing first. after I did that I had the zip log thingy in /data
nitwit said:
im not gettintg the zipalign logfile he mentioned. hmmm
Click to expand...
Click to collapse
Same here.
Sandso9 said:
Same here.
Click to expand...
Click to collapse
Yeah you're not the first person to have this problem, it's because Naven's init hack uses the busybox applet run-parts which doesn't exist in all busybox releases. You definitely should have a zipalign log in /data.
I'll probably get flamed again for posting, but the following link is init-rehack, I created it for myself (original work by naven who discovered the hack!) when the initial hack from naven wasn't working.
http://www.sendspace.com/file/9g6ngz
Edit: Updated with new link.
Flash it in recovery and let me know if that works and you see the zipalign logs.
0vermind said:
Yeah you're not the first person to have this problem, it's because Naven's init hack uses the busybox applet run-parts which doesn't exist in all busybox releases. You definitely should have a zipalign log in /data.
I'll probably get flamed again for posting, but the following link is init-rehack, I created it for myself (original work by naven who discovered the hack!) when the initial hack from naven wasn't working.
http://www.sendspace.com/file/jmvpyf
Flash it in recovery and let me know if that works and you see the zipalign logs.
Click to expand...
Click to collapse
flash it over yours then? or before ?
Sandso9 said:
flash it over yours then?
Click to expand...
Click to collapse
Yeah. Let me know if it works or if it doesn't.
0vermind said:
Yeah. Let me know if it works or if it doesn't.
Click to expand...
Click to collapse
flashed this over yours and still no zip align log file in /data
Sandso9 said:
flashed this over yours and still no zip align log file in /data
Click to expand...
Click to collapse
Sorry, wrong link.
Blah blah blah blah, edit edit edit edit
http://www.sendspace.com/file/9g6ngz
Edit: Updated with new link.
Flashed the latest file and still no zipalign log in /data.
zetsumeikuro said:
Flashed the latest file and still no zipalign log in /data.
Click to expand...
Click to collapse
Lol same here
Sent from my OG Droid
i have made rom for my s duos using xda kitchenn but i get status 1 error when i flash the rom
i have searched a lot but i can't find satisfied answer
can any one help me solve this error?
i'm using this guide
http://forum.xda-developers.com/showthread.php?t=1801690
Vaibhav Chauhan said:
i have made rom for my s duos using xda kitchenn but i get status 1 error when i flash the rom
i have searched a lot but i can't find satisfied answer
can any one help me solve this error?
i'm using this guide
http://forum.xda-developers.com/showthread.php?t=1801690
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2230733
Status 1 Error:
"Well this is one of the most rarest error that a person can get...but with my experience I came to know that this occurs because you don't have correct permissions set. Use correct perms in updater-script and done "
Grab another rom that is the same base you are using and look at the META-INF/com/google/android folder which contains the updater script and binary to use as your reference points. Compare and contrast yours with that one.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2230733
Status 1 Error:
"Well this is one of the most rarest error that a person can get...but with my experience I came to know that this occurs because you don't have correct permissions set. Use correct perms in updater-script and done "
Grab another rom that is the same base you are using and look at the META-INF/com/google/android folder which contains the updater script and binary to use as your reference points. Compare and contrast yours with that one.
Click to expand...
Click to collapse
can i use another rom's updater script in my rom which has same base??
Should be able to. Wouldn't hurt to look at the differences though so then you can understand what things affect the install to help build knowledge.
es0tericcha0s said:
Should be able to. Wouldn't hurt to look at the differences though so then you can understand what things affect the install to help build knowledge.
Click to expand...
Click to collapse
i tried to replace updater script but not working
i also have tried to compare set perms but i am unable to find fault in it
@es0tericcha0s
please tell me what to do??
Sorry, that was my main idea. Are you getting the same error code? Did you unzip and re-zip the rom? If so, you should use an archive manager like 7zip to move the update script into the zip without needing to unzip the whole thing, otherwise you'll break the signature on the rom and have to re-sign it.
es0tericcha0s said:
Sorry, that was my main idea. Are you getting the same error code? Did you unzip and re-zip the rom? If so, you should use an archive manager like 7zip to move the update script into the zip without needing to unzip the whole thing, otherwise you'll break the signature on the rom and have to re-sign it.
Click to expand...
Click to collapse
actually i am using android kitchen to make the rom
and when i use the cosmic rom's updater script in it the status 1 error was solved
but it stuck on boot animation
@es0tericcha0s
my stuck on bootloops can you tell me how to logcat?
Vaibhav Chauhan said:
@es0tericcha0s
my stuck on bootloops can you tell me how to logcat?
Click to expand...
Click to collapse
Not all phones have adb access while in a bootloop. But to do so you would need adb set up on your computer, change directories to the adb folder (or if it's enabled globally, then where ever), and type:
adb logcat
You'll want to save it somewhere like:
http://pastebin.com/
and upload the link.
I am not skilled at reading logcats, so not sure if I can be of any more help after that.
If you don't have adb set up already, then just use this one: http://forum.xda-developers.com/showthread.php?t=2317790
i have been messing with init.d for rooted/stock rom t230/nu and i have come up with a modified version of this >> http://forum.xda-developers.com/showthread.php?t=1912504
INSTRUCTIONS:
Flash the attacthed zip in twrp and reboot...
HOW DO I KNOW IF IT WORKED?
in root browser goto /data/local/tmp/ and if there is a file 'init.d_log_test.txt' and inside is written the date, it worked.
if the file is not present something went wrong? please let me know if it went wrong for you an i will fix it..
dont forget to hit thanks and also credit the @jamesst20 in the above link...
Ill give it a go.
Sent from my SM-T230NU
BookCase said:
Ill give it a go.
Sent from my SM-T230NU
Click to expand...
Click to collapse
let me know how it goes as i have only tested on my device... thnx
This will work.....I have it baked into my ROM.
One thing....I'd rename the install-recovery.sh to install-recovery-2.sh as that will break root. SU daemon is called by install-recovery.sh on boot. just a heads up.
g_ding84 said:
This will work.....I have it baked into my ROM.
One thing....I'd rename the install-recovery.sh to install-recovery-2.sh as that will break root. SU daemon is called by install-recovery.sh on boot. just a heads up.
Click to expand...
Click to collapse
i am building a rom at the moment and could not get my head round why it was breaking root lol... cheers dude..
Inside 4ndroid said:
i am building a rom at the moment and could not get my head round why it was breaking root lol... cheers dude..
Click to expand...
Click to collapse
Let me if your still having trouble with root afterwards.
g_ding84 said:
Let me if your still having trouble with root afterwards.
Click to expand...
Click to collapse
oh and in your rom it seems we cant update the su binary and have to flash an updated binary seperetely from within recovery.. i found a work around and now when i flash my rom it says binary needs updating an now in my rom the normal method works and alakasm success
if you need me to explain further pm me an i will go through how i managed it..
In the rom that you're working on is based on CyanogenMod or this stock?
on the other hand just flash this file in Stock T230XXU0ANK3'll see that this is
If you want to enable init.d, you simply install busybox from playstore and download universal init.d, and verify ...
checks in the system / etc / init.d contained in the file 00test & 08setperm :good:
working on my phone 4 tab 7 "T231 :fingers-crossed: :fingers-crossed:
sorry for my bad english
riotaruna said:
If you want to enable init.d, you simply install busybox from playstore and download universal init.d, and verify ...
checks in the system / etc / init.d contained in the file 00test & 08setperm :good:
working on my phone 4 tab 7 "T231 :fingers-crossed: :fingers-crossed:
sorry for my bad english
Click to expand...
Click to collapse
or you could just simply flash the file file in the OP takes alot less time an is simple an staight forward lol..
File is gone
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
toknitup420 said:
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
Click to expand...
Click to collapse
It could be missing metadata. Are you starting with this fimware? I can unpack it and locate the files with unique permissions. It may help figure out what is missing. Not using sparse dat is not your issue. set_metadata will work once we track down the problem.
SuperR. said:
It could be missing metadata. Which firmware are you starting with? I can unpack it and locate the files with unique permissions. It may help figure out what is missing. Not using sparse dat is not your issue. set_metadata will work once we track down the problem.
Click to expand...
Click to collapse
Do you want a copy of the current project I have in kitchen. I can upload it to my drive. I just used the zip from the may factory image.
Edit
Wow I just realized that was a link lol. I totally misread lol. Yes I'm using that firmware.
toknitup420 said:
Do you want a copy of the current project I have in kitchen. I can upload it to my drive. I just used the zip from the may factory image.
Edit
Wow I just realized that was a link lol. I totally misread lol. Yes I'm using that firmware.
Click to expand...
Click to collapse
You did not misread, i changed it I will check it out when I get a chance. No need to upload your project.
toknitup420 said:
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
Click to expand...
Click to collapse
Can you try this updater-script to see if it fixes the issue? There are actually 2 attached, with_vendor and no_vendor in case you extracted vendor too. If you replace it in the kitchen, make sure you zip the ROM manually because the kitchen will change it before zipping based on the files you have.
SuperR. said:
Can you try this updater-script to see if it fixes the issue? There are actually 2 attached, with_vendor and no_vendor in case you extracted vendor too. If you replace it in the kitchen, make sure you zip the ROM manually because the kitchen will change it before zipping based on the files you have.
Click to expand...
Click to collapse
so i cant zip manually because i dont have perms for one file in system. heres a pic. ill just add the script into an existing zip i built from kitchen.was
update
so i was able to move the script into the correct location and zip up the file. however when it flashes the updater script is somehow becoming merged with the original instead of just the new script. it still shows the original script text when flashing.
toknitup420 said:
so i cant zip manually because i dont have perms for one file in system. heres a pic. ill just add the script into an existing zip i built from kitchen.was
update
so i was able to move the script into the correct location and zip up the file. however when it flashes the updater script is somehow becoming merged with the original instead of just the new script. it still shows the original script text when flashing.
Click to expand...
Click to collapse
I will build a rom and upload for you to try. Are you building with vendor included or without?
SuperR. said:
I will build a rom and upload for you to try. Are you building with vendor included or without?
Click to expand...
Click to collapse
I built it without. Do you recommend to build it with vendor. Should that file be root like that. The one that's in that pic I sent.
toknitup420 said:
I built it without. Do you recommend to build it with vendor. Should that file be root like that. The one that's in that pic I sent.
Click to expand...
Click to collapse
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
SuperR. said:
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
Click to expand...
Click to collapse
OK I'll try it now. Good looks.
SuperR. said:
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
Click to expand...
Click to collapse
it flashes with no errors but it wont boot past splash screen.
toknitup420 said:
it flashes with no errors but it wont boot past splash screen.
Click to expand...
Click to collapse
Please try marlin n2g47o test rom 2:
https://www.androidfilehost.com/?fid=745425885120737663
SuperR. said:
Please try marlin n2g47o test rom 2:
https://www.androidfilehost.com/?fid=745425885120737663
Click to expand...
Click to collapse
flash went through without error but still boot looping at splash screen.
toknitup420 said:
flash went through without error but still boot looping at splash screen.
Click to expand...
Click to collapse
Moved to a dedicated thread as this issue is only about Pixel.
I will do more thinking on what could be causing it. I was pretty sure the last rom would fix it but clearly I was wrong lol
SuperR. said:
Moved to a dedicated thread as this issue is only about Pixel.
I will do more thinking on what could be causing it. I was pretty sure the last rom would fix it but clearly I was wrong lol
Click to expand...
Click to collapse
Lol good stuff. Keep me posted. I'll test whatever you throw at me.
toknitup420 said:
Lol good stuff. Keep me posted. I'll test whatever you throw at me.
Click to expand...
Click to collapse
Here is a new approach so I don't have to keep uploading full roms. Use the kitchen to extract the last rom I sent into a new project. In your file manager, navigate to your project directory and delete the 00_project_files directory. Extract the attached file into your project directory. Build rom with kitchen. Test rom.
Next time, you won't need to extract the rom zip again, just replace the 00_project_files directory.
edit: forgot to mention, after replacing the 00_project_files directory with the one in the zip, change perm types to something else, then back to set_metadata. Then build your rom
SuperR. said:
Here is a new approach so I don't have to keep uploading full roms. Use the kitchen to extract the last rom I sent into a new project. In your file manager, navigate to your project directory and delete the 00_project_files directory. Extract the attached file into your project directory. Build rom with kitchen. Test rom.
Next time, you won't need to extract the rom zip again, just replace the 00_project_files directory.
edit: forgot to mention, after replacing the 00_project_files directory with the one in the zip, change perm types to something else, then back to set_metadata. Then build your rom
Click to expand...
Click to collapse
flashing seemed to hang at setting perms. but it eventually went through. still looping at splash screen though.
toknitup420 said:
flashing seemed to hang at setting perms. but it eventually went through. still looping at splash screen though.
Click to expand...
Click to collapse
Can you send the original updater script that booted but did not have bluetooth?
SuperR. said:
Can you send the original updater script that booted but did not have bluetooth?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B4VEhClrJEWpNnJNVUJTRFV4ODQ/view?usp=sharing
https://drive.google.com/file/d/0B4VEhClrJEWpTmlYWC1CQ0s3LVE/view?usp=sharing
thats the binary and the script. i converted script to binary when i was building rom. this rom boots and runs ok other than bluetooth. its not completely stock though. i have my modded framework settings and system ui apks in there. but they are all signed so i dont think they would mess with anything.
toknitup420 said:
https://drive.google.com/file/d/0B4VEhClrJEWpNnJNVUJTRFV4ODQ/view?usp=sharing
https://drive.google.com/file/d/0B4VEhClrJEWpTmlYWC1CQ0s3LVE/view?usp=sharing
thats the binary and the script. i converted script to binary when i was building rom. this rom boots and runs ok other than bluetooth. its not completely stock though. i have my modded framework settings and system ui apks in there. but they are all signed so i dont think they would mess with anything.
Click to expand...
Click to collapse
Did you convert the new one you just tried after swapping 00_project_files to update-binary? If not, try it please. If so, try without please
New magisk module to use on any stock rom : ScaleR
For those who run on stock (or custom) which do not have the option to go lower then 0.5...
Made a Magisk module called ScaleR to scale up your device (even when running any rom) on window, transition and duration up to 0.25 or when that's not fast enough a 0.15 one or a 0.10
scaling up to 0.25 : 0.25ScaleR_module
scaling up to 0.15 : 0.15ScaleR_module
scaling up to 0.10 : 0.10ScaleR_module
Should work on any device.
Tested on magisk 16.4
Just flash within Magisk or twrp and Done ! Reboot.
PREVIOUS VERSION : SnappyR
*ONLY TO USE ON A2017G N-B08 ,B09 or B10 stock AND ON A CLEAN SYSTEM FLASH+SnappyR zip
So in TWRP : wipe system + (flash bootstack) + flash (stock)system + SnappyR zip + (SuperSU 2.79 or Magisk if you're on stocksystem) + reboot
(After reboot : do not change windows animation scaling under development options because it will probably reset things )
For those on A2017G N-B08 stock, N-B08-slim³, N-B09 or B10 and want their phone to be faster (scaled 0.25) in general , just do a clean SYSTEM flash and flash your appropriate SnappyR zip. After that just reboot.
I compiled services.jar to the 0.25 scaling and you'll see the result immediately after reboot.
Scaling is max on 0.25 ( although in settings it's set on 0.5 but actualy its running on 0.25 )
A2017G-N-B08 stock : SnappyR-N-B08
A2017G-N-B08 Slim³ : SnappyR-N-B08-slim³https://androidfilehost.com/?fid=673791459329070166
A2017G-N-B09 stock : SnappyR-N-B09https://androidfilehost.com/?fid=673791459329070530
A2017G-N-B10 stock : SnappyR-N-B10https://androidfilehost.com/?fid=890129502657589434
Just try it out and you'll see your phone is much snappier !
ALSO for ppl that want to change the animation speed to a custom value afterwards. thnx @GodOfPsychos
Type this in adb:
adb shell
settings put global window_animation_scale 0.25
settings put global transition_animation_scale 0.25
settings put global animator_duration_scale 0.25
Or if you have a terminal app (material terminal for example):
su
settings put global window_animation_scale 0.25
settings put global transition_animation_scale 0.25
settings put global animator_duration_scale 0.25
HOPE YOU'll ENJOY !!!
Btw, if interested i can make this for other roms too, as long as they are stock and basicly unmodified
Thanks! Could you add it to your next rom Update?
Lycidias said:
Thanks! Could you add it to your next rom Update?
Click to expand...
Click to collapse
You mean B09-slim4? This rom is ready but not able to upload it because of holidays in Spain :laugh:
If you want I'll upload this SnappyR for B09 too, so you can test it out.
raystef66 said:
You mean B09-slim4? This rom is ready but not able to upload it because of holidays in Spain :laugh:
Click to expand...
Click to collapse
The ISP deactivate your internetconnection? Interesting ;D /sarkasm off
Spillunke said:
The ISP deactivate your internetconnection? Interesting ;D /sarkasm off
Click to expand...
Click to collapse
:laugh:yeah. Not really. Internet connection is very good. Still have enough juice to upload stuff but the weather is too good here and just relaxing in the sunshine :good:
When I'm back I'll upload it.
Uploaded it for the A2017G-N-B08-slim³
Had the be another one due to the EPM(extended power menu) that was integrated in the AROMA rom itself and uses the modified services.jar too
SnappyR-slim³
PLZ B09 SnappyR
raystef66 said:
When I'm back I'll upload it.
Click to expand...
Click to collapse
Oh yeah please. I check xda 5 times the day for B09 slim⁴ since the B09 update is released. ;D
Belpek said:
PLZ B09 SnappyR
Click to expand...
Click to collapse
Here you go :good:
https://androidfilehost.com/?fid=673791459329070530
Not sure If this is a SnppyR issue, but i think my display isnt this dark on lowest brightness like before.
EDIT: GravityBox setting was the reason.
Spillunke said:
Not sure If this is a SnppyR issue, but i think my display isnt this dark on lowest brightness like before.
Click to expand...
Click to collapse
It isn't. Just some values that are changed but nothing to do with screen brightness.
As a matter of fact, i'm always running on 0.25 and i can almost put my screen brightness so that i hardly can see text anymore.
Okay thanks. Then i have to remember what i also changed in the last days.
I don't really feel any difference in responsiveness after putting animation speed to 1x. Does it really do anything different besides accelerating animations a bunch?
Choose an username... said:
I don't really feel any difference in responsiveness after putting animation speed to 1x. Does it really do anything different besides accelerating animations a bunch?
Click to expand...
Click to collapse
Sure it does affect animation, transition and duration to 4x faster.
F.e when i open my browser, youtube or gmail f.e. , all is loaded much faster then before. Really. Thats why we compile it that way
Maybe it didn't flash correct.
Also do not alter the numbers in developer options after you flashed it or you'll have to reflash it again to have 0.25.
What rom are you on ?
Choose an username... said:
I don't really feel any difference in responsiveness after putting animation speed to 1x. Does it really do anything different besides accelerating animations a bunch?
Click to expand...
Click to collapse
Checked it and you're totaly right mate. I overlooked the fact that services.jar cant have effect when flashed afterwards.
I always did flash the mod on a clean flash, that's why it worked for me. Didn't thought about that and just made some flashable zips of those mods
I'll update the OP till i have found a possible fix for install afterwards.
So, when u want to use it, do a clean system flash (wipe system and flash stock system again) + my SnappyR zip in the same flash. Then reboot (replacing the services.jar within your running rom wont have any effect )
That should do the trick.
Perhaps you can try this out and give some feedback.
raystef66 said:
Checked it and you're totaly right mate. I overlooked the fact that services.jar cant have effect when flashed afterwards.
I always did flash the mod on a clean flash, that's why it worked for me. Didn't thought about that and just made some flashable zips of those mods
I'll update the OP till i have found a possible fix for install afterwards.
So, when u want to use it, drag the services.jar (out of my zip) into your rom zip and replace system/framework/services.jar with it.
And do a clean flash.
That should do the trick.
Perhaps you can try this out and give some feedback.
Click to expand...
Click to collapse
All right, I'll try now
Choose an username... said:
All right, I'll try now
Click to expand...
Click to collapse
EDIT : just do a clean system flash + SnappyR zip in the same flash. Then reboot.
raystef66 said:
But when you're on b09 you'll have to extract the b09 stock system to get into the framework . Perhaps you've superrkitchen too to do the necessary work.
I've not yet uploaded my B09-slim4 but it will have this baked into it.
But you can try the B08-slim3 and replace the services.jar on that rom.
Click to expand...
Click to collapse
Oh ok. I just formatted system, clean flashed the ROM, zips and your mod. Don't really see a difference besides the huge responsiveness boost while reopening an app that's already on RAM (because of .25)
I guess I'll modify the zip and do it again. It's pretty bad 'cause I have to flash around 6 or 7 zips that are all over my phone's storage (I have to get an USB OTG, not risking an SD card here; I can't get one in Argentina)
Formatted system only and flashed all my stuff with SnappyR and it worked for me (now). If i replaced the files and just restarted -> no effect.
Choose an username... said:
Oh ok. I just formatted system, clean flashed the ROM, zips and your mod. Don't really see a difference besides the huge responsiveness boost while reopening an app that's already on RAM (because of .25)
I guess I'll modify the zip and do it again. It's pretty bad 'cause I have to flash around 6 or 7 zips that are all over my phone's storage (I have to get an USB OTG, not risking an SD card here; I can't get one in Argentina)
Click to expand...
Click to collapse
No SD cards there That bad ?
Btw, if you saw that improved responsiveness, i think you're good to go.
Spillunke said:
Formatted system and flashed all my stuff with SnappyR and it worked for me (now). If i replaced the files and just restarted -> no effect.
Click to expand...
Click to collapse
Thnx Spillunke for testing.
I wasn't already awake when i wrote this topic :cyclops: but it is as you have tested out :
Just do a clean flash so wipe system + (flash bootstack) + flash system + my SnappyR zip and reboot
* do mind not to alter animation speed/duration/windows in developer options after you flashed it because i'm pretty sure it will go back to 0.5