I don't know if anyone else tried and ran into the same issue...
After installing Android N (NPC56W build) on my 6P I wanted to have Viper4Android working, so I enabled permissive mode.
Booom. The phone rebooted itself, I needed a few seconds to realize, it was in "safe mode", and looked like after the first boot (after flashing the rom). I was wondering what the hell went wrong. After a reboot everything went back to normal. I thought it is because the kernel doesn't support permissive mode. So I tried 3 other kernels, always the same result. Then I started to look deeper, and found out, that there is a "system integrity check", which reboots the phone into safe mode on selinux mode change.
I found the part in the source code, and disabled it. After two days of compiling, I finally got the that little binary called "logd".
I replaced the original in /system/bin in recovery and rebooted and in a root shell ran "setenforce 0". And it worked! This time no reboot, and the command "getenforce" returns "Permissive". I'm a happy person now that Viper is working.!
It was damn straight worth the 2 days of s**ing!
I didn't test it for more than an hour yet, so use it at your own risk! I'm not responsible if you phone get's damaged, or broken....
If any of you know a better solution, I'm open for it!
Otherwise: enjoy it!
This worked for me. Although it doesn't seem permissive stays through a reboot. But it's easy enough to change back. And viper works. Thanks.
bamfsig45 said:
This worked for me. Although it doesn't seem permissive stays through a reboot. But it's easy enough to change back. And viper works. Thanks.
Click to expand...
Click to collapse
Yes, the setting resets on reboot. You could put a one liner shell script in /system/etc/init.d. Then it would be set during boot.
I'm glad it worked for you too!
Is this a flashable zip?
Hmm....I also noticed this, because restoring of apps in Titanium Backup on Dev Preview only work if the phone in permissive.
Will this work in the Dev Preview 2????
EDIT: Thanks, it works for Dev Preview 2 as well
duminduweera said:
Hmm....I also noticed this, because restoring of apps in Titanium Backup on Dev Preview only work if the phone in permissive.
Will this work in the Dev Preview 2????
Click to expand...
Click to collapse
Just tested it on preview 2 and it works
TBU now able to restore my apps
hermes2xgreat said:
Is this a flashable zip?
Click to expand...
Click to collapse
I made a flashable zip to make it easier for most. Thank @gubacsek for the logd file.
This one will copy the original logd to the root of your sdcard in case you want to restore it: http://www.mediafire.com/download/6i2rrgr4f5wc4ty/copy_logd_backup.zip
MD5Sum: 800b86bb130f7cc0f558944569d62891
This one will replace the current logd with the modified logd: http://www.mediafire.com/download/9uo1j6h88x8o8z0/logd_replacement_permissive.zip
MD5Sum: f0f219552ace44e5f12297403f5fc8e3
Side Note: If you want Permissive to survive a reboot you will have to run a script in /su/su.d to make it persist.
Side Note 2: Don't forget to go into terminal and type su for root acces, then type setenforce 0 to set as permissive. You could also do this in an adb shell. You can test to see if it's in Permissive mode by typing getenforce in terminal (this info. is in the OP, but people tend to skip OP's).
EDIT: If you guys want to add a script so that SELinux boots up as Permissive every time you reboot, then flash this file: http://www.mediafire.com/download/6klkabmpa5h5xbf/add_permissive_boot.zip
MD5Ssum: ab3584c4044659653d3ec30f9732a50f
bouchigo said:
I made a flashable zip to make it easier for most. Thank gubacsek for the logd file.
This one will copy the original logd to the root of your sdcard in case you want to restore it: http://www.mediafire.com/download/6i2rrgr4f5wc4ty/copy_logd_backup.zip
MD5Sum: 800b86bb130f7cc0f558944569d62891
This one will replace the current logd with the modified logd: http://www.mediafire.com/download/9uo1j6h88x8o8z0/logd_replacement_permissive.zip
MD5Sum: f0f219552ace44e5f12297403f5fc8e3
Side Note: If you want permissive to survive you will have to run a script in /su/su.d to make it persist.
Click to expand...
Click to collapse
You're welcome! I was too lazy to create a zip file.
I will update the thread title to say it works on npc91k build too.
And I didn't even notice that TB works in permissive. I always install the app from playstore and restore only the data afterwards, because that was working. Thanks for the tip!
This is awesome. Thanks guys
This work great with my Preview 2 build.:laugh::laugh::laugh:
bouchigo said:
I made a flashable zip to make it easier for most. Thank @gubacsek for the logd file.
This one will copy the original logd to the root of your sdcard in case you want to restore it: http://www.mediafire.com/download/6i2rrgr4f5wc4ty/copy_logd_backup.zip
MD5Sum: 800b86bb130f7cc0f558944569d62891
This one will replace the current logd with the modified logd: http://www.mediafire.com/download/9uo1j6h88x8o8z0/logd_replacement_permissive.zip
MD5Sum: f0f219552ace44e5f12297403f5fc8e3
Side Note: If you want Permissive to survive a reboot you will have to run a script in /su/su.d to make it persist.
Side Note 2: Don't forget to go into terminal and type su for root acces, then type setenforce 0 to set as permissive. You could also do this in an adb shell. You can test to see if it's in Permissive mode by typing getenforce in terminal (this info. is in the OP, but people tend to skip OP's).
EDIT: If you guys want to add a script so that SELinux boots up as Permissive every time you reboot, then flash this file: http://www.mediafire.com/download/6klkabmpa5h5xbf/add_permissive_boot.zip
MD5Ssum: ab3584c4044659653d3ec30f9732a50f
Click to expand...
Click to collapse
Thanks soo much. This is a great tool to get done what I need without all the frikkin hassle
Work well on NPC91K build. Thanks
@gubacsek
I was browsing the supersu forums earlier and you should be able to type this in terminal or adb shell:
Code:
stop logd
setenforce 0
This will allow you set as permissive without replacing logd, and without rebooting into safemode.
So, we can have a script with those lines in init.d or /su/su.d to run at boot without messing with logd...this is probably good since the logd you complied may not work on Preview 3, etc.
EDIT: Just wanted to let everyone know it works. Fastboot flashed system.img to make sure logd was working as intended, meaning that it will send you to safemode when attempting to change SELinux. Once I made sure it was working properly I applied the commands mentioned earlier, and...
Success :good:
bouchigo said:
@gubacsek
I was browsing the supersu forums earlier and you should be able to type this in terminal or adb shell:
Code:
stop logd
setenforce 0
This will allow you set as permissive without replacing logd, and without rebooting into safemode.
So, we can have a script with those lines in init.d or /su/su.d to run at boot without messing with logd...this is probably good since the logd you complied may not work on Preview 3, etc.
EDIT: Just wanted to let everyone know it works. Fastboot flashed system.img to make sure logd was working as intended, meaning that it will send you to safemode when attempting to change SELinux. Once I made sure it was working properly I applied the commands mentioned earlier, and...
Success :good:
Click to expand...
Click to collapse
Nice! There is only one question left... What the f* is this logd doing? What happens if you stop it?
Anyway! Nice out of the box thinking I didn't even think about stopping it...
A very very big thanks for your great work @gubacsek and @bouchigo
With your work now I've got ViperMod and OK Google working at my N6 with preview 2 at http://forum.xda-developers.com/nexus-6/development/rom-stock-flashables-t3348657
Gesendet von meinem Nexus 6
spevil07 said:
A very very big thanks for your great work @gubacsek and @bouchigo
With your work now I've got ViperMod and OK Google working at my N6 with preview 2 at http://forum.xda-developers.com/nexus-6/development/rom-stock-flashables-t3348657
Gesendet von meinem Nexus 6
Click to expand...
Click to collapse
You are welcome! I'm happy I could help!
And I know the feeling I was also damn happy when it worked. Viper is the most important mod for me. Once heard the music through it, I can't live without it anymore...
YEAEEEEAAAAAHHH its absolutly that what i need!!!!
With this music its absolutly obligation
https://soundcloud.com/toxic-sickness/doctor-terror-exclusive-guest-mix-on-toxic-sickness-april-2016
https://soundcloud.com/eargasmpodcastofficial/eargasm-podcast-2-by-unproven
spevil07 said:
A very very big thanks for your great work @gubacsek and @bouchigo
With your work now I've got ViperMod and OK Google working at my N6 with preview 2 at http://forum.xda-developers.com/nexus-6/development/rom-stock-flashables-t3348657
Gesendet von meinem Nexus 6
Click to expand...
Click to collapse
It works without any crashes and with the screen off?
gubacsek said:
Nice! There is only one question left... What the f* is this logd doing? What happens if you stop it?
Anyway! Nice out of the box thinking I didn't even think about stopping it...
Click to expand...
Click to collapse
It looks like logd is just a logging binary; it seems like logd monitors for changes to the system that Google wants to keep track of, be it for informational purposes or, to stop people from messing with SELinux like we are seeing in this case. In this case logAudit.cpp and logAudit.h look for changes specifically to SELinux, and if one is detected it will either boot you to SafeMode, or to recovery depending on how the change comes about.
Does logd really need to be running? I'm not sure the answer to that, but I've had it shut off for the past couple of days so far with no ill effects that I have noticed.
EDIT: I compiled a new logd with preview2 source, and though it's a bit smaller in size than the one you compiled for preview 1, the result is the same as the one you compiled. It should be easy enough to compile a new logd for preview 3 in case your current one stops working for preview 3...as long as the preview 3 source is released quickly...or still use the stop logd command to completely stop it from running :good:
bouchigo said:
It seems like logd is just a logging binary; it seems like logd monitors for changes to the system that Google wants to keep track of, be it for informational purposes or, to stop people from messing with SELinux like we are seeing in this case. In this case logAudit.cpp and logAudit.h look for changes specifically to SELinux, and if one is detected it will either boot you to SafeMode, or to recovery depending on how the change comes about.
Does logd really need to be running? I'm not sure the answer to that, but I've had it shut off for the past couple of days so far with no ill effects that I have noticed.
EDIT: I compiled a new logd with preview2 source, and though it's a bit smaller in size than the one you compiled for preview 1, the result is the same as the one you compiled. It should be easy enough to compile a new logd for preview 3 in case your current one stops working for preview 3...as long as the preview 3 source is released quickly...or still use the stop logd command to completely stop it from running :good:
Click to expand...
Click to collapse
sighs... I know security and all, but it is just exhausting to try and get around new restrictions google is building into android all the time. I know it is okay for the masses, but seriously, there should be a master switch in android, or a special developer version which allows us to do what ever we want with our devices.
Anyway. Android is still by far the best and "developer friendly" OS in my opinion, so I'm just shutting up.
Yes, I also compiled a new logd already, but there is no change in the source, so of course it is working with both N builds. And I hope it will stay so in future releases
Related
This is not a thread to say ‘thanks’ to developers. Only post here if you have some input in this development progress, by either fixing bugs, or coming up with ideas (and ideally, try your idea and report what happens).
Having that said, let’s move on to where we are at the moment. Currently, we have a build which is based upon Ice Cold Sandwich 6.2 Test Edition for the HTC Desire HD. This build boots up by flashing my custom kernel on it, based on Flyer HC Original Kernel Source, with some patches:
-Quota2 Support
-Genlock Support
-Updated KGSL driver by applying Lord Clockans patches from his kernel
The ZIP we are working on now, can be downloaded here:http://w728685.open.ge.tt/1/files/9iI3CbF/0/blob?download
This ZIP contains a build which is mainly Lord Clockans ICS, with essential changes in the ROM to get it booting (we used LeeDroid’s Flyer HC as the donor ROM). This ROM is made for a HoneyComb HBOOT!
After you have flashed that ZIP, this is the kernel you need: http://ge.tt/9iI3CbF/v/1
You MUST flash this kernel to get it up and running, or it’ll just loop in the logcat complaining about unsupported stuff.
This set should do the following:
-Boot up (bootanimation resets after some time, it’s ok, it will boot within 5 minutes).
-Touchscreen works after you did this: open ADB Shell (by entering ‘adb shell’ on your pc,), and send the command “echo ‘1’> /sys/android_touch/event_google”. Now touchscreen should be working. (For some reason the file 90flyerhacks in /system/etc/init.d doesn’t do its job. If anyone has a clue > say so!) Also, the ntrig.c file in /drivers/input/touchscreen/ is modified in the kernel, don’t know if it helped though.
-Full Hardware Accceleration
-Screen is bugged at certain moments (seems to happen especially during things concering wallpapers. Rendering a wallpaper, showing a heavy LWP, etc.). The build.prop file contains some lines such as:
ro.fb.mode=1
debug.composition.type=gpu/mdp
debug.fb.rgb565=0
Perhaps we have to change these lines to get it running without issues (strange thing is, logcat doesn’t seem to make an issue about this). We can also try a recompile of the kernel using the entire driver folder from Lord Clockans kernel (it’s in /drivers/gpu/msm/ in his kernel, and /drivers/video/msm/gpu/kgsl_adreno205_hc in ours, moving the folder to where it should be causes issues, so we keep it like this for the time being).
-Sound is working
-Backcamera seems to be working fine, haven’t tested frontcamera.
-Hardware buttons under the screen aren’t working, and this should be a low
priority for now. It isn’t ideal to use them in ICS anyway (different button functions in comparison with the softbuttons), and I think we shouldn’t focus on this for now.
-GPS switch can be enabled, haven’t tested whether it works.
-Bluetooth switch can be enabled, but turns off automatically after about ten seconds.
-WiFi switch can’t be changed, logcat tells us that it can’t connect with /dev/rfkill, applying this patch in the ramdisk could fix it:
https://github.com/OpenSensation/an...mmit/da09360d70888a7e126871ab2ae5b218514cad18
-Power button and Volume buttons work fine.
-Pen works after we send the event_google command mentioned before.
If the ROM immediately reboots within 10 seconds and it seems like it’s looping, and you can’t even logcat, hold down Power and Volume Down until you get to HBOOT, select FASTBOOT, and enter ‘fastboot erase cache’ in the CMD/Terminal, and reboot, and it should work.
And that’s about it for the current things we know I think. If you manage to fix something, please write down and report what you did to fix it, so we can keep a list. I will work on a vendor folder using the known information, so we can compile a ROM from source, made for our device.
And last, but not least: don’t post here asking for release dates. We will do our utmost best to bring ICS experience to the Flyer, but do not bug us. Thanks.
Now let’s get this up and running guys! I will keep a log of what is fixed and what is not, so we can keep the thread organized. Else we’ll have 50 ZIPs around, not knowing which one is the right one et cetera.
Source code of kernel: http://github.com/Chaosz-X
Ramdisk will be uploaded tomorrow.
Donations are much appreciated, as I'm developing and building atm on a 1.67GHz Dual core...
Donations can me made to [email protected] using Paypal.
i suggest creating two repos... one for ROM and one for kernel... that way single file changes can be tracked even on ROM front, not just kernel...
willing devs can fork those repo and send pull requests to main repo when they get stuff working
I'm not a developer, and I have nothing but love for all the great devs that worked so hard to bring ICS to the Flyer.
Might I suggest, however, that instead of pursuing CM9 builds, the next effort be centered around porting the Android Open Kang Project (AOKP) ROM? In terms of features and customizations, it's considerably ahead of CM9, with numerous supported devices to boot.
I think this ROM, versus CM9, would give users the most flexible and dynamic ICS experience for their Flyer.
Chaosz-X said:
-Touchscreen works after you did this: open ADB Shell (by entering ‘adb shell’ on your pc,), and send the command “echo ‘1’> /sys/android_touch/event_google”. Now touchscreen should be working. (For some reason the file 90flyerhacks in /system/etc/init.d doesn’t do its job. If anyone has a clue > say so!)
Click to expand...
Click to collapse
Does it work if you add
write /sys/android_touch/event_google 1
to the init.rc file?
Could you post the init.rc file where you trigger the init.d scripts?
nickiberli said:
Does it work if you add
write /sys/android_touch/event_google 1
to the init.rc file?
Could you post the init.rc file where you trigger the init.d scripts?
Click to expand...
Click to collapse
yes that should work correctly
No, I didn't add that. I'll try it tomorrow (or one of you, if you have a Linux machine ready. Laptop with Ubuntu is having some issues atm, can fix it tomorrow).
So, assuming that's working, let's get to the display. We know that it causes issues, but how?
-Logcat doesn't error (except for HtcEbdLog, saying something about rotation, which seems to happen when glitches occur. Perhaps we need to swap the files?)
-At the very beginning, it does tell that initOverlay failed. This overlay-thing is baked in the ROM, and can be disabled in the ROM itself by setting an option to 'false' in the vendor setup. We don't know if it fixes the issue, but since the attempts to add this functionality to the kernel failed, it could be a better idea to fix it in the ROM to get rid of the error.
Any other suggestions?
Edit: and before I forget, tomorrow I'll check the ZIP for what is changed in comparison with the ROM it is based upon, so we know what we have to add in to a new build too.
Chaosz-X said:
No, I didn't add that. I'll try it tomorrow (or one of you, if you have a Linux machine ready. Laptop with Ubuntu is having some issues atm, can fix it tomorrow).
So, assuming that's working, let's get to the display. We know that it causes issues, but how?
-Logcat doesn't error (except for HtcEbdLog, saying something about rotation, which seems to happen when glitches occur. Perhaps we need to swap the files?)
-At the very beginning, it does tell that initOverlay failed. This overlay-thing is baked in the ROM, and can be disabled in the ROM itself by setting an option to 'false' in the vendor setup. We don't know if it fixes the issue, but since the attempts to add this functionality to the kernel failed, it could be a better idea to fix it in the ROM to get rid of the error.
Any other suggestions?
Edit: and before I forget, tomorrow I'll check the ZIP for what is changed in comparison with the ROM it is based upon, so we know what we have to add in to a new build too.
Click to expand...
Click to collapse
u want me to add stuff to that ramdisk?
start a github repo for the ramdisk and ROM too... trust me... its VERY helpful...
I'll start installing Ubuntu within 30 minutes, and will add everything to a GitHub by tonight within about 3 hours I think.
Chaosz-X said:
I'll start installing Ubuntu within 30 minutes, and will add everything to a GitHub by tonight within about 3 hours I think.
Click to expand...
Click to collapse
thats great... it should make keeping track of changes much easier and other interested devs can contribute if they want...
Hello, all.
Attempting to help by working on the build.prop settings. I'm S-OFF with revolutionary and have my device fully configured with the Honeycomb HBOOT/radio/bootloader/etc.
After flashing the ROM and the kernel, the device would immediately reboot upon attempting to return to the main recovery menu. I had to fastboot oem rebootRUU and reflash Globatron's PG41IMG-WIFI-light-B10 zip to get recovery back.
The device never proceeded to the boot animation.
Thracks said:
Hello, all.
Attempting to help by working on the build.prop settings. I'm S-OFF with revolutionary and have my device fully configured with the Honeycomb HBOOT/radio/bootloader/etc.
After flashing the ROM and the kernel, the device would immediately reboot upon attempting to return to the main recovery menu. I had to fastboot oem rebootRUU and reflash Globatron's PG41IMG-WIFI-light-B10 zip to get recovery back.
The device never proceeded to the boot animation.
Click to expand...
Click to collapse
I can confirm this happened to me also. The only difference is that I was using the kernel for a port of mine, and it did the same thing.
Yes, it is known that for some reason, Go Back already reboots the device. It's no problem though, it works fine anyway. If it is really looping the bootanimation every ten seconds, keep Vol Down and Power pressed, until you get to HBOOT. Select FASTBOOT, and enter 'fastboot erase cache' in the terminal. Then reboot on the device, and it should boot up fine.
Also, kernel won't work on Honeycomb, haven't checked why it doesn't though (and I won't btw, our goal is not to make a new kernel for Honeycomb, but for ICS, where it does its job fine).
Kernel source is uploaded to my Github: http://github.com/Chaosz-X
Edit the CROSS_COMPILE for your toolchain, and it should compile fine (it does here).
Will add the link to the OP within 5 minutes, ramdisk will be uploaded tomorrow.
If chaos has a device tree set up for the Flyer/View, no build prop editing should be necessary, can just submit requests - but I don't notice it on the git.
Thanks for uploading, I'll have a look and see what has changed so far. It's a little difficult to keep track of the changes since there are no commits that document the patches applied over time, but I'll try to make do with what you've got.
Is this straight from flyer HC kernel source?
I may be doing this wrong, but the touch screen commands do not seem to be working for me
Cimer said:
I may be doing this wrong, but the touch screen commands do not seem to be working for me
Click to expand...
Click to collapse
You have to type it in manually. Copying and pasting does not work, at least it did not for me. I think the issue is with the '
lawguy said:
You have to type it in manually. Copying and pasting does not work, at least it did not for me. I think the issue is with the '
Click to expand...
Click to collapse
It may just be me, I tried manual too. I had to use http://forum.xda-developers.com/showthread.php?t=1379875 since I'm stuck on Windows 8..maybe something is up with that. I guess I will just need to sit and wait =/
Cimer said:
It may just be me, I tried manual too. I had to use http://forum.xda-developers.com/showthread.php?t=1379875 since I'm stuck on Windows 8..maybe something is up with that. I guess I will just need to sit and wait =/
Click to expand...
Click to collapse
Hang tight for now. Wifi Does not work and the screen freaks out. I'm sure that these things will be fixed soon.
Going to upload ramdisk source within an hour, and try to apply a fix for WiFi, and try to fix the touchscreen by using the command in init.rc mentioned here earlier.
The new modem arrived, I have Internet again, so we have remote access to our Linux machine and can start compiling etc again
Indeed, we're grabbing AOKP source code now. Within about 2 hours we think, we'll start compiling the ROM for the HTC Flyer. Don't know if it will work out, but we have to start somewhere
[UPDATE FOR JB.15][Custom Build Prop] Increase Performance & Battery Life of PRIME
MAJOR UPDATE: U.S. & WW. MODDED BUILD.PROP FOR NEW. 15 JELLYBEAN RELEASE ADDED. here are edited build.prop files for both the US & WW 10.4.2.15 Jelly Bean. Tweaks are listed as to what they are within the build.prop and to install just copy over using Root Explorer or similar app and then ensure permissions are set correctly. MUCH LOVE AND THANKX GO TO MR.WOOKIE FOR THIS and his constant contributions to making the prime a better device to own. I know I haven't been around as much as I don't own a prime anymore. But I can continue to update this thread as needed. Its very important that if issues arise, PLEASE TRY TO HELP ONE ANOTHER OUT. I can try to help out when I can. As always, make sure to set permissions correctly. JB build.prop Modding should be no different than previous versions. so most of the instructions in this OP/thread still apply. please post up how this mods are working for you on new JB firmware. if you notice any particular mod or line is causing problems with JB, please let us know. so it can be modified again. HAVE FUN...PRIME WILL ALWAYS BE HOME FOR ME
With the permission of the Original Developer, Seanzscreams, we bring a modified version of his mod for the 300 that now works on the Prime also. This is a custom modified build prop, that Brings Overall Performance & Battery life Improvements to the Transformer Prime. This will make your device feel more snappy and responsive overall. It should improve battery life. Other performance tweaks also will improve everyday use of Prime.Your device has to be on the latest U.S. .21 or U.S..28 firmware and rooted. If you on a ww version or other, you may need to tweak the build.prop to reflect your region version. Take a look inside the modded build.prop & see before you try it out. If you know how to edit it, give it a shot. just make sure to back up your original build.prop. If unsure, hit the link & ask the developer. It is possible to not be rooted and push this through ADB but being rooted makes it ALOT easier.
UPDATE: U.S. & WW .28 MODDED BUILD.PROP ADDED. EVERYTHING EXCEPT power collapse & wifi scanning added. some users reported issues that could be linked. same instructions on implementing this. MAKE SURE TO MAKE BACKUP OF YOUR ORIGINAL FILE. MIGHT BE BEST TO SEND IT TO SOMEPLACE OUTSIDE INTERNAL MEMORY OF PRIME. JUST TO BE ON THE SAFE SIDE.
*Users on region versions other than the US .21 or U.S. .28, read the tips at the end of this post before you attempt this. Putting this US version of build.prop in your device can cause issues if not properly edited to reflect your region.
*If you running Androwoki rom, no need to apply this tweak. the developer already added these tweaks to his ROM/build.prop.
-UPDATE: fellow member Mekrel made a .21 WW version of this for those who wish to try out. or you go the other route like mentioned in this post. the WW version is attached to this thread also.
Thanks to Hairdex for making a making a version for people running Team EOS Cornerstone build #9. only those on build #9 can use it.
-added De .21 version also
PLEASE READ IMPORTANT INFO & TIPS AT THE BOTTOM OF THIS POST IN CASE ANY POSSIBLE ISSUES ARISE.
Method described below is for rooted users as I don't really know how to do it the stock(not rooted) method through ADB. You can go to original thread and ask developer on how to push it through ADB method
Quote from developer, Seanzscreams:
" This is a modified build.prop to include all the latest ics tweaks
(from a build.prop standpoint)
forced 60fps
faster wifi connect and suplicant scan set at 100 (battery saver as well)
added deep sleep mode
added screen dithering
removed checkin back to base
kernel tweaked
dalvik mins and max set higher than stock
increased over-all fling velocity min and max now set
min at 8000 and max at 12000
a few nvidia specific graphics tweaks as well
. power collapse disable enabled
-and just a few i dont feel like explaining google is your friend"
Link to his original thread: http://forum.xda-developers.com/showthread.php?t=1641219
DISCLAIMER: I nor the original developer take responsibility if you don't follow instructions or researched first. USE AT YOUR OWN RISK. It should be a fast n simple mod. Works great on my prime. If you run into issues, we will help you the best we can. Please read the important info & tips at the bottom of this post. It could eliminate possible issues from arising.
USE ROOT EXPLORER:
this modded build.prop, which is attached to this thread, goes in /system. Make sure to back up your original build prop or add .bak to the end of it(.bak). I sent a copy of my original file to my drop box. just an extra safety precaution... You will need to change root explorer to mount as RW. after you back up the original file, paste the new modded build prop into /system. then long click on it and press permissions. the permissions need to be exactly like the original file. which is rw-r--r-- after you properly set the permissions, change root explorer back to Read only. then power down and reboot, then profit. You can reboot twice to make sure everything sticks, if you want. If you don't notice anything initially, let it cache(kind of like letting a car warm up before you drive off) just like with roms. just start using tab so it can cache.
CLARIFICATION ON SETTING PERMISSIONS IF UNSURE. your permissions for this mod build.prop should look like this: rw-r--r--
...........Read. Write
Owner. X .......... X
Group. X
Others. X
I would suggest before even applying this, open the mod build prop up in root explorer. then just take a look at it all. Then cross reference the new tweak lines added with the links I will provide now. These links show all the build prop tweaks and what they do. This is to get a better understanding of what will be improved on your device Performance & Battery Savings wise. It won't hurt for you to become more familiar with what the different lines do and it might eliminate some questions concerning what each does.
http://forum.xda-developers.com/showthread.php?t=1639104
http://forum.xda-developers.com/showthread.php?t=1510652
EXAMPLES OF SOME OF THE TWEAKS SEEN IN THIS MODDED BUILD.PROP & WHAT THEY DO OR AFFECT: Thankx to TheFrankenstain & H M Judge threads for Reference
- Allows the tablet to sleep better: This setting puts your tablet into a deeper sleep when on standby
ro.ril.disable.power.collapse=1
- Allows your wifi to scan less frequently, saving more battery
wifi.supplicant_scan_interval=100
- Increase overall touch responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
-Increases Scrolling responsiveness
windowsmgr.max_events_per_sec=300
- Faster Scrolling
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
-Increases quality of photo/Increases the memory cap when decoding JPEGs
ro.media.dec.jpeg.memcap=8000000
-Raises quality of JPEG images: makes JPEG Higher Quality
ro.media.enc.jpeg.quality=100
-Enable Surface dithering:Improves image quality
persist.sys.use_dithering=1
-System tweaks:
Change the Dalvik VM heap size
-dalvik.vm.heapsize=256m
-dalvik.vm.startheapsize = 8м
-makes apps load faster and frees more ram.
dalvik.vm.dexopt-flags=m=y
-Use Jit (Dalvik just-in-time compiler): faster better caching system
dalvik.vm.execution-mode=int:jit
-Disable error checking (Should speed things up a bit)
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
this has been running great for me so far. battery life seems improved and the responsiveness of the touch screen is unbelievable. it scrolls so fast n fluid it crazy. this is with the regular UI & within browsers. It also increases quality of your JPEG pictures. Im really impressed with it so far.
Do note though, once OTA update comes, it will knock all this out and a new custom build prop will have to be made. this is even if you accept the new OTA.
I will keep this thread updated to stay current with the developers original thread. As new updates come out, he will be modifying the newer build props within the update. So I will add those here as they come.
Make sure to click on the developer, Seanzscreams, original thread(http://forum.xda-developers.com/showthread.php?t=1641219) and give him thanks. You can leave feedback in this thread and original thread, if you wish. Feedback is encouraged as it will lead to better future results on this mod.
THANKS TO: Seanzscreams for Modding my Prime build prop. Now we have this MOD available to all prime owners on latest .21 firmware and rooted.
Attached to this post is a zip file with the custom build prop inside of it. The U.S. and WW version
*IMPORTANT:
If you come across a difficulty, you can ask in this thread or even better would be to ask in the developer original thread. He would know more on possible issues that may arise.
If you run into issues or caught in a bootloop or something here is how to use adb and push back your original build.prop file: Thanks to Mekrel
in regards to being for locked/unlocked users, I posted two sets of commands. Technically three scenarios exist:
Being locked
If you're locked, you're not going to have any third party kernel installed and therefore WILL have a secure kernel and therefore not able to push files to /system. That's why you need the command that involves pushing to the /sdcard and then using su via shell to copy from the /sdcard and then to /system.
Unlocked but with a kernel installed that's still secure
As above
Unlocked but with a kernel installed that's insecure
You can push directly to /system, so you don't have to push to the /sdcard first
If you're unlocked you're going to be running a secure kernel which means you're not going to be able to run adb as root, so even with root and the /system partition mount as r/w; you're not going to be able to push to system:
Code:
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
exit
exit
adb push build.prop /sdcard/
adb shell
su
cp /sdcard/build.prop /system
chmod 644 /system/build.prop
rm /sdcard/build.prop
exit
exit
Unlocked and with an insecure kernel:
Code:
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
exit
exit
adb push build.prop /system
adb shell
su
chmod 644 /system/build.prop
exit
exit
In regards to remounting to read only once finished, you don't have to as you can simply reboot and the commands executed in ramdisk will remount every partition with the relevant flags. Or you could:
Code:
adb shell
su
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
exit
exit
you should be good to go after this.
*TIPS for users that are not on US .21 but instead on a WW or other version: thnkx to Buxtahuda & Gage_Hero
- instead of editing this build.prop with your information, edit your build.prop with any missing lines from this one. That's going to cut down on error a lot, and even if you get the right characters and spacing, the build.prop can be finnicky as all hell.
- IF you edit the build.prop use the right tool which would be notepad++ (download) not the standard windows note pad. if you use the standard windows notepad you could end up with format and character issues
*CAUTION:
We had a user who was unlocked, boot to a black screen. He got his prime back running by doing a restore from recovery. For unlocked users who want to try this, make sure to do a full backup, including the original build.prop file. Unlock users could even edit their own build.prop & add the lines one by one until it breaks. You can download notepad + yes it is +(plus). then you can edit the build prop (properly with out screwing up the format) on the pc and move it to the tablet. I'm not sure if being unlocked conflicts with this mod. just make sure you on latest .21 or .28 firmware and rooted. Then follow instructions carefully. you can even click on the original developer link for assurance on how to install if unsure how to install or if you have any possible conflicting issues. It would be best to ask developer if this is safe for unlocked users also. Unlocked users should proceed with caution and make sure you will be OK using this.
update:Developer said being unlocked shouldn't matter. I'm still waiting to hear back on what if people are on a different version like WW or something.
You can feel free to Hit my Thanks also, if you want. For putting this guide together on my Prime solely. The Prime is my PC Make sure to give feedback here & to OG developer, Seanzscreamz and his OG thread http://forum.xda-developers.com/showthread.php?t=1641219 . He made this all work for our Primes when he didn't have to. Much thanks to him & other members who contributed critical info, tips, & feedback.
Thanks to Texstar & Andromorphone for editing U.S. .28 buildprop.
That is the one I am looking for so long. Thanks for sharing.
Sent from my HTC Desire HD using xda premium
Could you please explain how to do this without root?
okay okay.. I will try it and report back
1SiK1500 said:
Could you please explain how to do this without root?
Click to expand...
Click to collapse
you actually dont need root
but this is way easier if you do
you could adb push /system/build.prop
or you could just paste it into root explorer replacing your existing
(back up existing or rename it to build.prop.bak just for safe keeping )
then reboot
or
when it reboots and adb comes alive you may be able to push it to /system with: adb push build.prop /system
not really much more was explained. you can click on his original thread link to get more details or ask him about it. most seem to be doing this the rooted method. I haven't seen anyone confirm doing this adb way yet.
I get an error..
"There was not enough free disk space to complete the paste operation" when I tried to paste this into /system with the original .bak there
I had to remove the original file to make room
Also, I think you better expand on what -RW, -R, -R means for people - like exactly what boxes to check and uncheck
I forgot to add:
If you don't notice anything initially, let it cache(kind of like letting a car warm up before you drive off) just like with roms. just start using tab so it can cache. it'll take to the changes.
Lock-N-Load said:
I get an error..
"There was not enough free disk space to complete the paste operation" when I tried to paste this into /system with the original .bak there
I had to remove the original file to make room
Click to expand...
Click to collapse
that's strange. I still have my original file in there renamed. I never got that error. Do you still have all those modded wifi files in there also?
edit: I saw the other part you added, I gotcha
demandarin said:
that's strange. I still have my original file in there renamed. I never got that error. Do you still have all those modded wifi files in there also?
edit: I saw the other part you added, I gotcha
Click to expand...
Click to collapse
Yes I do in /bin which is in /system - suppose i should delete those.
But this implies /system looks for and checks the size of that directory and pukes if it is beyond xx size - which is kind of interesting
Also, technically speaking, aren't permissions rw-r--r-- not -RW, -R, -R
Well, I did this and it just goes to a black screen and does nothing else.
How can I get back into the system and restore the old file?
Lock-N-Load said:
Yes I do in /bin which is in /system - suppose i should delete those.
But this implies /system looks for and checks the size of that directory and pukes if it is beyond xx size - which is kind of interesting
Also, technically speaking, aren't permissions rw-r--r-- not -RW, -R, -R
Click to expand...
Click to collapse
I edited OP to reflect that.
acdcking12345 said:
Well, I did this and it just goes to a black screen and does nothing else.
How can I get back into the system and restore the old file?
Click to expand...
Click to collapse
were you rooted and on .21 firmware?
did you put the modded file into /system & set its permissions to rw-r--r--? & rename the old file? so it won't be confused with 2 files try to be activated.
demandarin said:
I edited OP to reflect that.
were you rooted and on .21 firmware?
did you put the modded file into /system & set its permissions to rw-r--r--? & rename the old file? so it won't be confused with 2 files try to be activated.
Click to expand...
Click to collapse
I did exactly that..It was also unlocked...
Not sure how to go back to the old file..
Works great! Wow I can see a big speed difference! I can't wait to see how much longer the battery lasts.. Thanks man!
Sent from my Transformer Prime TF201 using XDA Premium App
jjdevega said:
Works great! Wow I can see a big speed difference! I can't wait to see how much longer the battery lasts.. Thanks man!
Sent from my Transformer Prime TF201 using XDA Premium App
Click to expand...
Click to collapse
you see changes that quick?? guess I will test mine more tonight.
my install went fine and reboot went fine.
I believe in this mod type as I did similar mods to my OG Droid
Lock-N-Load said:
you see changes that quick?? guess I will test mine more tonight.
my install went fine and reboot went fine.
I believe in this mod type as I did similar mods to my OG Droid
Click to expand...
Click to collapse
Surprisingly did. I didn't think I would see much of a difference that quick. As soon as it rebooted and right after the lock screen swiping was fast and opening closing apps are much quicker load times
Edit: overall loading speeds are improved quite a bit
Sent from my Transformer Prime TF201 using XDA Premium App
At work and don't have my Prime with me at the moment.
I will try tonight and report to you guys.
Good to hear positive feedback.
acdcking12345 said:
I did exactly that..It was also unlocked...
Not sure how to go back to the old file..
Click to expand...
Click to collapse
I'm wondering if being unlocked messes with things. Did you make a backup of your original file? if so. you can try to adb push it in there. you should go to original developer thread and post this up. As I'm not exactly sure on the adb method on getting the prime to use the original file.
ill make sure to add to the OP that being unlocked may conflict with this. As this is the only difference between yours n mines.
so you rebooting and it just went to a black screen? any Asus logo or anything? can you get into recovery and reflash your rom or restore a backup?
Anyone with insight into how he get back using the old file from state he is in now?
I don't see a wifi scan interval on either the original or this build prop. That was one I changed from 30 seconds to 100 on my phone to cut down on the power used by wifi to go out and ping and search for signals.
On my phone is it wifi.supplicant_scan_interval = 30
A bit surprised this does not exist as it can be a good battery saver
I also see some telephony stuff in this prop that seems of no value as we dont have phones
demandarin said:
I'm wondering if being unlocked messes with things. Did you make a backup of your original file? if so. you can try to adb push it in there. you should go to original developer thread and post this up. As I'm not exactly sure on the adb method on getting the prime to use the original file.
ill make sure to add to the OP that being unlocked may conflict with this. As this is the only difference between yours n mines.
so you rebooting and it just went to a black screen? any Asus logo or anything? can you get into recovery and reflash your rom or restore a backup?
Anyone with insight into how he get back using the old file from state he is in now?
Click to expand...
Click to collapse
I just went into recovery and restoring from a 3 old backup..
Lock-N-Load said:
I don't see a wifi scan interval on either the original or this build prop. That was one I changed from 30 seconds to 100 on my phone to cut down on the power used by wifi to go out and ping and search for signals.
On my phone is it wifi.supplicant_scan_interval = 30
A bit surprised this does not exist as it can be a good battery saver
I also see some telephony stuff in this prop that seems of no value as we dont have phones
Click to expand...
Click to collapse
it there is one actual in there. you have to look closely. its set to 100. I just looked in saw it. its like the 4th line above the additional build properties. I believe this scan is lower than in stock configuration.
I noticed the phone stuff also. he said once he updates, he has more tweaks he will add. ill update this thread with the changes also.
I know there are a couple posts out there on how to fix this, but this is one of the most legitimate ways to fix the multitasking issue we have all come to know and hate on Android devices running Sense. If you don't want to install a whole new ROM, such as MEANROM, you don't have to! This is a small guide to using the V6 SuperCharger script by Zeppelinrox. I know the amount of steps seems like a lot, but it's really not that many. Most of the steps will be followed by just reading what you see on the screen and accepting the recommended option!
Zeppelinrox said:
What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
The problem with using minfree tweakers like AMM or AKMO is that it doesn't work the same on all roms.
Secondary apps may be in slot 3 on some roms but in slot 5 in others!
That's why you hear people comment "I tried AKMO but it didn't do anything..."
Most likely it didn't do anything because the apps weren't sitting where they were expected to be.
So fasten your seat belts and enjoy the ride!
Click to expand...
Click to collapse
So, everything you need to know or want to know can be found at Zep's original thread here. There is a lot of information, and because he is so technical, I think that sometimes his instructions can be hard to read for some, so I thought I would put together a VERY SIMPLE GUIDE to give you guys a hand. You can find the best instructions from him under Installing/Using.
http://forum.xda-developers.com/showthread.php?t=991276
On to the instructions...
How To Use Supercharger
Please only proceed if you are rooted and have busybox
Download script manager from the market: https://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=en
Download zep's latest V6 Script (V6_SuperCharger_for_Android-Update9_RC11_Test_6.sh.pdf): http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
remove the .pdf extension (should now end in .sh) and place on your phone /sdcard (you can use rom tool box or estrongs to rename the file)
At this point, I highly recommend you make a nandroid through TWRP or CWM. The script has a built-in undo feature, which works well, but I still think we all know this is best.
Open up Script manager on your phone. Make sure to check 'Browse as Root' Option
Navigate to the location wher you placed the V6 .sh script
Click the Skull/Crossbones to run as root. This should turn green. NOTE: DON'T USE THE BOOT OPTION
Hit Run
At this point, get ready for an onslaught of text. Don't be afraid and try your best to read even though much of it may not make sense!
You may be asked about your launcher. Answer the question correctly for your setup.
Any time you are asked to press Enter, go ahead and proceed. This is the last time I will tell you to hit Enter for most occasions.
Pick your scrolling speed. I recommend slow or normal the first time you do this, so you can keep up.
On the kernel panic screen, I recommend choosing the Rock(H)ard Option, so hit H and then enter
Accept the Misc and 3G tweaks by hitting Y
Feel free to keep or disable the annoying animation (the scrolling V6 at the beginning of the script)
Hit Y(es) for SuperMinFree Calculator settings. This is an automatic calculation. You can change this later when you get more confident. Many will choose the 1000HP option for our phone (based on available memory)
It will now backup your build.prop and some other system files.
ICS and newer Android services store a lot of the memory tweaks in services.jar. This script will now take you through an ICS patcher. Accept the Automatic Transmission. This will upload services.jar, and download the patched one.
It will eventually tell you that it needs to wipe your caches and restart. You will definitely want to do this. You will need to wait 4-5 minutes while it rebuilds your Dalvik Cache
Almost done! After your phone boots up and stabilizes, go back into Script Manager. Navigate to /data/99Supercharger script. Check the SU (skull/crossbones) and check the boot option.
Zepelinrox said:
- Stock ROMs - It also creates /data/99SuperCharger.sh which you can load up on boot (run as root) with Script Manager. The OOM groupings work as well since it happens on boot in local.prop or build.prop (18 entries added)
Click to expand...
Click to collapse
Reboot your phone and now your phone will run the supercharger script on startup. If you ever want to verify that your script is working, or if you want to mess with any of the extra options (including removal), run the original V6 shell script you downloaded as root, just like we did at the beginning. This will tell you if you are 100% optimized and give you a whole menu of options to play with!
I can actually open multiple apps now and go back to the first one without it having to reload. Waze is the best example. If I ever switched out and then back, it always had to reload...not anymore! Again, this all seems like a lot, but it's really pretty easy once you give it a shot!
Let me know if anything is unclear so that I can adjust this OP to help others.
Make sure to give Zep a 5 Star Rating in his OP and also give him thanks, he is the man!
Reserved just in case.
ok i need to correct you on one of your steps...DO NOT SELECT THE BOOT OPTION FOR THE SCRIPT. IT COULD CAUSE YOUR PHONE TO BOOT LOOP. only select run as root. it even tells you that on the guide that zeppelinx put in his thread.
edit: sorry for caps but i wanted to point this out before someone made this mistake
bog3nator said:
ok i need to correct you on one of your steps...DO NOT SELECT THE BOOT OPTION FOR THE SCRIPT. IT COULD CAUSE YOUR PHONE TO BOOT LOOP. only select run as root. it even tells you that on the guide that zeppelinx put in his thread.
edit: sorry for caps but i wanted to point this out before someone made this mistake
Click to expand...
Click to collapse
You have to run /data/99Supercharger as root and give it boot option or it won't be applied at boot. But you are right, if you are worried, you could just run it as root the first few times. I personally always set this one to boot as well. If you had to, you could always adb in recovery, and remove /data/Supercharger if you are having problems.
*EDIT
This is mostly a concern for ROMS/Kernels that utilize /etc/init.d but I will add this caveat to the OP
adma84 said:
You have to run /data/99Supercharger as root and give it boot option or it won't be applied at boot. But you are right, if you are worried, you could just run it as root the first few times. I personally always set this one to boot as well. If you had to, you could always adb in recovery, and remove /data/Supercharger if you are having problems.
*EDIT
This is mostly a concern for ROMS/Kernels that utilize /etc/init.d but I will add this caveat to the OP
Click to expand...
Click to collapse
if the rom uses init.d then the script will install a service to the init folder and it will auto load when then phone is restarted, no need to try and force it to run. also if it is a stock rom (with the script manager program) you can set the 99supercharger to run after boot as a task.
bog3nator said:
if the rom uses init.d then the script will install a service to the init folder and it will auto load when then phone is restarted, no need to try and force it to run. also if it is a stock rom (with the script manager program) you can set the 99supercharger to run after boot as a task.
Click to expand...
Click to collapse
What you are saying is exactly the point I made in the OP. Is this unclear? You should only ever run 99Supercharger on boot, not the original V6Supercharge Script. And yes, this is geared mostly towards stock users, who do not have init.d support and therefore need SManager to run the boot script for them.
adma84 said:
What you are saying is exactly the point I made in the OP. Is this unclear? You should only ever run 99Supercharger on boot, not the original V6Supercharge Script. And yes, this is geared mostly towards stock users, who do not have init.d support and therefore need SManager to run the boot script for them.
Click to expand...
Click to collapse
i understand what you are saying but the boot symbol next to the run ass root symbol in the script should not be checked. if you need it to run at boot the script manager program can do that for you, by setting up a scheduler when you reboot. after boot it will run the script but not during
p.s. let me re-read what you put so i am just not looking stupid lol. i think i need a nap
edit: yea if you need it to run at boot do it through the script manager program and set it up to schedule it to load the script after your phone is already booted to avoid any potential boot loops (but dont check the boot logo at the top left hang corner of the actual script itself
bog3nator said:
i understand what you are saying but the boot symbol next to the run ass root symbol in the script should not be checked. if you need it to run at boot the script manager program can do that for you, by setting up a scheduler when you reboot. after boot it will run the script but not during
p.s. let me re-read what you put so i am just not looking stupid lol. i think i need a nap
edit: yea if you need it to run at boot do it through the script manager program and set it up to schedule it to load the script after your phone is already booted to avoid any potential boot loops (but dont check the boot logo at the top left hang corner of the actual script itself
Click to expand...
Click to collapse
Can you post the steps to describe how you personally do boot scripts with SManager?
After Android starts up, it will send a boot intent to all apps registered to receive such an intent. This is where SManager is allowed to execute any scripts you have marked with the boot option. This happens much later than a traditional /etc/init.d start script, but is no less effective. Please let me know how you mark scripts as bootable and I can add that recommendation as well. Thanks.
adma84 said:
Can you post the steps to describe how you personally do boot scripts with SManager?
After Android starts up, it will send a boot intent to all apps registered to receive such an intent. This is where SManager is allowed to execute any scripts you have marked with the boot option. This happens much later than a traditional /etc/init.d start script, but is no less effective. Please let me know how you mark scripts as bootable and I can add that recommendation as well. Thanks.
Click to expand...
Click to collapse
1. open script manager
2. click menu
3. click more
4. click advanced options
5. click scheduler
6. click add new task
7. click select file
8. navigate to 99supercarger file the script created and click on it
9.you can from there click on boot (inside the file you just clicked on)
10. click save
it will boot the script after the phone is done booting, to prevent the possibility of boot looping. you can also create an event to do an engine flush however often you want (i do one at midnight everyday)
This gets executed at the same time during system boot as the method I mentioned. Both are valid. Thanks for the feedback!
Sent from my Nexus 7 using xda app-developers app
adma84 said:
This gets executed at the same time during system boot as the method I mentioned. Both are valid. Thanks for the feedback!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i thought you were saying click the boot thing during install ....i am sorry haha i got really tired all of a sudden and stuff wass getting jumbled together...
v6 works awesome though i have been using it for about 1 year now on this phone and my old evo
Also, for anyone that gives this a shot, please post back with your results!
Not to be "that guy" buuuut the effects of v6 at least from my experience with this phone (again fresh frombcustoms preorder release) the day i got it i was rooted and installed v6 because ive used it on all my prior evos since i found it probably right around when zep released lol...anyways on this phone its a strictly placebo effect and actually created more lag and launcher reloads...i was running the 1000hp option and tried the i believe 750hp whatever the one down from 1000 is anyways both of them gave me same results and once i removed the script all was good in the hood as they say lol...but if its working for yall then maybe zep fixed some ish for this problem and i didnt know about it...well this epic runon sentence is finished sorry for the length and useless points
Sent from the depths of hell
yea i also used it on my og evo and i just put it on last night again on this one, tried the 750 option and 1000 option. today at school my memory got so low it locked my phone, that never happened with mean rom and the tweaks he puts in. undoing the supercharge now.
Sorry everyone.
Sent from my Nexus 7 using xda app-developers app
adma84 said:
Sorry everyone.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
no thanks man for helping out, i just think this phone doesnt do well with it, and that may be because of how HTC changed the multitasking settings themselves. it may conflict with v6
Theres something up with it because its def just this phone because nothing solves it at all
Sent from the depths of hell
wileout said:
Theres something up with it because its def just this phone because nothing solves it at all
Sent from the depths of hell
Click to expand...
Click to collapse
I wonder if it's hard coded into sense somewhere
Sent from my EVO using xda app-developers app
bog3nator said:
I wonder if it's hard coded into sense somewhere
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Im thinking its sonething stupid like a character in the code is supposed to be one way and its mirrored the other way lol
Sent from the depths of hell
It's definitely helps with multitasking. I can keep apps open in the background much easier. Problem is that it chokes out the available ram for running apps, so it can make it feel sluggish. I think it's overtweaking the mem settings.
**does not yet work for 7.1.1**
Using a PC to root seems like moving backwards compaired to a 'one click' apk. but we're already at the PC to flash eng_boot, plus this new method is so much faster...so here we go
Features:
SuperSU 2.82
Init.d
Wifi fix
Flashlight fix
Issues:
For the wifi fix I just copied an edited J320a build.prop
So J320AZ users will see J320A in about device, and will have to reassign notification sounds. (Hope to fix it in the future)
Needed Files:
Odin
Root_J320A.zip
Procedure:
1. Unzip both files.
2. Run Odin click the 'AP' button.
3. Navigate to Root_J320A/bin and select sm-j320a_Engroot_601PJ2.tar and press "Start" (make sure NOT to check re-partition)
4. After it completes sucessfully, leave the phone hooked to the pc... and then wait, wait a good 2 or 3 minutes after its booted.
5. Once 2 or 3 minutes has gone by you can navigate to the Root_J320A folder.
6. There you'll see root.bat, double click that let it do its thing.
6a. If at any time during the script you see "adb out of date. killing..." hit the x to close the window and restart the script.
*This may work on J320AG models but make sure you check oem unlock from dev settings first... and let us know how it goes
Enjoy
- D
Credits:
@ashyx - eng_boot
@Sh$llNinjA - eng_root
@sjowns - flashlight fix
@Chainfire - SuperSU
@Ryuinferno - init.d script
Excellent! This works perfectly! Thank you so much for posting this.
J320A PC9 worked perfectly!
March security patch
Hi man, this method support the march security patch, or are still in january security patch
I tested on AQD2 so it'll work on AQC1 too.
I assume it'll work for all 6.0 updates we get.
I tested on AQD2 so it'll work on AQC1 too.
I assume it'll work for all 6.0 updates we get.
This works perfectly. Thank you!
I suggest you put 'root' in the tile, otherwise google cannot find it.
I googled 'j320a root', google only links to ashyx's post which doesn't... well maybe only mine phone.
I am new to this root bit.
Possibly I have done something wrong. I read your instructions carefully and quit didn't understand where the unzipped files should go. Do any of these have to be placed in the phone's directory?
Failed on my AT&T SM-J320A
I wonder if it has anything to do with the new update pushed out recently
@JeffF73
Run Odin and Click ap.
Navigate to the directory where you unzipped root_j320a.zip.
In that folder you'll see a bin folder, inside that is sm-j320a_Engroot_601PJ2.tar, which needs flashed to the phone.
Once that's complete, let it boot and wait.
Then run root.bat
DamienMc said:
@JeffF73
Run Odin and Click ap.
Navigate to the directory where you unzipped root_j320a.zip.
In that folder you'll see a bin folder, inside that is sm-j320a_Engroot_601PJ2.tar, which needs flashed to the phone.
Once that's complete, let it boot and wait.
Then run root.bat
Click to expand...
Click to collapse
Hello DamienMc Thank you for your reply and help. I figured it out. I had to put my phone in "Download Mode" by holding down Volume Down, Home Button and Power button while booting. Then I was able to use Odin without failing. This solved all my problems thank you
Is it safe to flash this after doing this?
https://mega.nz/#!D8hSzLaa!pDugFwQ0NyGBLy36j1643bI3e4f9xog7US8UTTkZ8SU
sonic0504 said:
Is it safe to flash this after doing this?
https://mega.nz/#!D8hSzLaa!pDugFwQ0NyGBLy36j1643bI3e4f9xog7US8UTTkZ8SU
Click to expand...
Click to collapse
Yes, that has selinux set to permissive as well, although there's no real difference. The build.prop differences are noticable tho...I plan on doing an update to this, just have to figure out how to tell if it's A or AZ from adb
Ragheb Alama said:
Hi man, this method support the march security patch, or are still in january security patch
Click to expand...
Click to collapse
Yes, it works for QC1. However, you may need to replace build.prop in /bin from QC1 with WiFi fix before root.
I did notice that after root, the contents of /Android/data folders in both internal storage and external sd card are hidden from PC. Before root, both are visible from PC. Any thoughts about what cause the changes?
Will this work on July security patch?
DamienMc said:
Yes, that has selinux set to permissive as well, although there's no real difference. The build.prop differences are "noticeable" tho...I plan on doing an update to this, just have to figure out how to tell if it's A or AZ from adb
Click to expand...
Click to collapse
Thanks, I just needed to install this to use adb to uninstall an update I did to System UI because it would continuously crash.
SBCarr said:
Yes, it works for QC1. However, you may need to replace build.prop in /bin from QC1 with WiFi fix before root.
I did notice that after root, the contents of /Android/data folders in both internal storage and external sd card are hidden from PC. Before root, both are visible from PC. Any thoughts about what cause the changes?
Will this work on July security patch?
Click to expand...
Click to collapse
Probably the eng_boot we use, it breaks the flashlight and wifi passwords too... it does work on j320a July update, so I assume it'll work on j320az update too
@DamienMc Dude, thanks for ur post, but i tried 2 times and fail, i got stuck at logo, i had to reflash to stock but now my build.prop is gone or corrupted, my phone says model unknow, i cant even use hidden menus like *#06, etc, i need the original file to fix it please. model SM-J320A RUNING QC1
ScSoluciones said:
@DamienMc Dude, thanks for ur post, but i tried 2 times and fail, i got stuck at logo, i had to reflash to stock but now my build.prop is gone or corrupted, my phone says model unknow, i cant even use hidden menus like *#06, etc, i need the original file to fix it please. model SM-J320A RUNING QC1
Click to expand...
Click to collapse
Reflash CSC as well, that'll wipe your device but fix your problem.
Are you sure you waited long enough after the phone booted before rooting?
If at any time during the script you see it say "adb server out of date. Killing..." something is wrong. You can x the command prompt and do root.bat again.
DamienMc said:
Using a PC to root seems like moving backwards compaired to a 'one click' apk. but we're already at the PC to flash eng_boot, plus this new method is so much faster...so here we go
Features:
SuperSU 2.82
Init.d
Wifi fix
Flashlight fix
Issues:
For the wifi fix I just copied an edited J320a build.prop
So J320AZ users will see J320A in about device, and will have to reassign notification sounds. (Hope to fix it in the future)
Needed Files:
Odin
Root_J320A.zip
Procedure:
1. Unzip both files.
2. Run Odin click the 'AP' button.
3. Navigate to Root_J320A/bin and select sm-j320a_Engroot_601PJ2.tar and press "Start" (make sure NOT to check re-partition)
4. After it completes sucessfully, leave the phone hooked to the pc... and then wait, wait a good 2 or 3 minutes after its booted.
5. Once 2 or 3 minutes has gone by you can navigate to the Root_J320A folder.
6. There you'll see root.bat, double click that let it do its thing.
6a. If at any time during the script you see "adb out of date. killing..." hit the x to close the window and restart the script.
*This may work on J320AG models but make sure you check oem unlock from dev settings first... and let us know how it goes
Enjoy
- D
Credits:
@ashyx - eng_boot
@Sh$llNinjA - eng_root
@sjowns - flashlight fix
@Chainfire - SuperSU
@Ryuinferno - init.d script
Click to expand...
Click to collapse
This was the first time i ever tried to root my phone and i followed the instructions located here:
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628
Well my wifi wouldnt save any passwords , flashlight was broken and my ATT J320A would always want to boot in to recovery mode. I thought i was screwed!!!! Then i seen one link in the thread to this thread where Kingroot was not needed.
I opened Odin and gave a shot and then ran Root.bat file, and the device rebooted wifi and flashlight were fixed and best of all my J3 was now rooted!!!!!
Still working on getting rid of that annoying pop up but all is good, thanks so much for this root and fix from the other thread.
james2ya said:
This was the first time i ever tried to root my phone and i followed the instructions located here:
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628
Well my wifi wouldnt save any passwords , flashlight was broken and my ATT J320A would always want to boot in to recovery mode. I thought i was screwed!!!! Then i seen one link in the thread to this thread where Kingroot was not needed.
I opened Odin and gave a shot and then ran Root.bat file, and the device rebooted wifi and flashlight were fixed and best of all my J3 was now rooted!!!!!
Still working on getting rid of that annoying pop up but all is good, thanks so much for this root and fix from the other thread.
Click to expand...
Click to collapse
@james2ya If you are talking about the pop that either says something in the order of "Unathorized activities where made" go to the play store, download and install SecurityLogAgent Fix, Open it up and click "Disable Securitylogagent" then restart phone when it asks. This should help get rid of that popup.
works great for me! now i just need a custom rom. is it possible to install trwp on j320a?
Hello all, I got my Amazfit Pace a few days ago and the first thing that I wanted to do after flashing PACEified was get proper on-device root, as you know right now PACEified comes with adb root shell so we can modify the watch however we want from and adb shell but that means we're always dependent on another device for doing so, apps on the watch have no way of getting root access.
I am actually amazed that no one else even seemed to have any interest in achieving this as it was somewhat easy for me to figure it out and now I'm sharing it with y'all.
Requirements: being on a ROM that has adb root (ex: PACEified) or ability to boot the temproot kernel.
WARNING: If the stock kernel has dm-verity the temproot then install SuperSU method will lead to the device refusing to boot, I do not know whether it does or not.
Disclaimer: I am in no way responsible for any damage this can or will cause to your watch and/or phone, you are the only one responsible for your own actions.
Anyway here's the steps to getting SuperSU 2.79 fully working on your watch:
Download the attached zip file.
Copy the zip file to the watch.
Open a terminal/cmd/powershell in the folder where your adb binary is located.
Run the following commands in order:
Code:
adb root
Code:
adb remount
Code:
adb shell
Now you are running shell commands on the watch itself so do:
Code:
busybox unzip /sdcard/SuperSU-2.79-amazfit.zip
Code:
cd /sdcard/supersu/
Code:
sh root_amazfit.sh
Done, reboot and enjoy!
I hope this helps others as it did help me and I do hope I didn't make any mistake.
Credits:
Chainfire for SuperSU
Neuer_User for PACEified
KevinX8 for the SuperSU 2.79 zip for Android Wear (I used that one cause it already is setup to allow all by default)
Everyone else that I can't remember right now
List of useful root apps for the Amazfit:
MiXplorer-useful file manager with addons and root file management options: https://forum.xda-developers.com/showthread.php?t=1523691
Kernel Adiutor 4 Wear-very popular kernel options management app, won't give too many options since the stock kernel is actually quite limited but still allows tweaking a few things like changing the schedulers and their options, enabling init.d and other such stuff: https://forum.xda-developers.com/android-wear/development/app-kernel-audiutor-4-wear-t3126122 (I only tested this version but the latest normal Kernel Adiutor version might also work perfectly since the interface seems pretty friendly with low resolutions)
Advanced Settings for Watch-provides a plethora of options like Bluetooth and WiFi settings management, reboot menu and most importantly PACKAGE MANAGEMENT and by that I mean it doesn't just have the normal app settings menu that allows you to clear data/cache, force stop or disable/uninstall apps but ALSO INCLUDES A PACKAGE INSTALLER for installing apks straight on the watch: https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings&hl=en (get the wear apk from inside the main apk, it is located in /res/raw just open the phone apk as an archive also WARNING: many menus/options make it crash cause this is not Android Wear)
Another one.
Wich are the benefits of doing that?
jmpcarceles said:
Wich are the benefits of doing that?
Click to expand...
Click to collapse
Same as on any other rooted Android device.
A few apps I have on the watch that use root are:
MiXplorer-file manager
Kernel Adiutor-can improve battery life/performance by messing around with it a bit
Root Essentials (the wear part sent from inside the phone apk)-it's great for uninstalling apps and such
Hello. Stock ROMs can boot "temproot kernel"? Could you please like to where it's explained? Thanks.
Ranomez said:
Same as on any other rooted Android device.
A few apps I have on the watch that use root are:
MiXplorer-file manager
Kernel Adiutor-can improve battery life/performance by messing around with it a bit
Root Essentials (the wear part sent from inside the phone apk)-it's great for uninstalling apps and such
Click to expand...
Click to collapse
Nice.
MiXplorer is my mobile favourite Android explorer.
I don't know the other apps, i must learn about it.
Any suggestions about them, Kernel auditor seems very interesting. I have very much problems with my Amazfit battery, last month suddenly i don't get more than 2 days of autonomy
Thx.
lfom said:
Hello. Stock ROMs can boot "temproot kernel"? Could you please like to where it's explained? Thanks.
Click to expand...
Click to collapse
Stock ROM can boot temproot kernel only if old enough version to not have the bootloader locked OR you unlocked the bootloader after, to get the temproot kernel go to the PACEified thread and read the install instructions, it has you booting the temproot kernel on order to flash it and it might be possible to just boot it, root and reboot but I am not entirely sure, if the Amazfit has dm-verity it will refuse to boot after altering the system, I actually didn't think about that when I wrote this guide cause it was 5AM so would recommend flashing a custom ROM.
@Neuer_User does the Amazfit have dm-verity?
Also would you consider adding SuperSU to PACEified in the future?
Double post cause mobile XDA is messed up, delete.
jmpcarceles said:
Nice.
MiXplorer is my mobile favourite Android explorer.
I don't know the other apps, i must learn about it.
Any suggestions about them, Kernel auditor seems very interesting. I have very much problems with my Amazfit battery, last month suddenly i don't get more than 2 days of autonomy
Thx.
Click to expand...
Click to collapse
To be honest MiXplorer just about works but isn't really 100% usable cause things don't fit on screen, looking for a better root file explorer for the watch.
The stock kernel doesn't really allow you to control much cause the stock kernel doesn't seem to have too many features but can still change governor and a few other stuff and if nothing else it can enable init.d if you don't already have it enabled, I use the Kernel Adiutor 4 Wear version but TBH I think the normal one should be just as usable.
For your battery problem you could try deleting some unneeded apps like the Mi Home or the Chinese radio one (if on Chinese ROM/PACEified) and maybe Greenify will also work but wouldn't really put my bets on it, perhaps try using some battery saving scripts?
Right now I'm looking for an apk installer...I have a solution already but it's probably the worst one possible: a init.d script that checks if there are apps in a folder on the internal storage then installs all of them and deletes the apk files but that means you need to reboot in order to install apps, could make crond run the script every hour or so but that would also not be too convenient so either a script runner or a apk installer would be best.
BTW after uninstalling apps from the watch using a root app you need to crash the launcher or it will still show the icons for the uninstalled apps.
Also I'm working on improving the script to add safety checks (if someone tries to run it without the other files in the same folder right now it would most certainly end up in a mighty bootloop, fortunately a bootloop with adb access so easy to fix but still not great, I made that script in like 5-10 min after I manually did it on my own watch) and add more features like installing a newer busybox version and linking missing applets (unzip for example).
Updated 2nd post with a few useful apps, one of them finally giving us the power to install apps straight on the device, will publish the new version of my script in a few days, have been working on adding A LOT of new features and now I kinda need to concentrate on the project for my Android class for a bit, sorry for the delay.
Ranomez said:
Updated 2nd post with a few useful apps, one of them finally giving us the power to install apps straight on the device, will publish the new version of my script in a few days, have been working on adding A LOT of new features and now I kinda need to concentrate on the project for my Android class for a bit, sorry for the delay.
Click to expand...
Click to collapse
Hi Ranomez,
When do you plan to publish the new script for local root?
Thx in advance.
Merry Xmas.
jmpcarceles said:
Hi Ranomez,
When do you plan to publish the new script for local root?
Thx in advance.
Merry Xmas.
Click to expand...
Click to collapse
Most probably next week, haven't really had time to work on it with the last week of college before the holidays and the fact that I bought Xenoblade Chronicles 2 on launch day and it's been eating most of my free hours, lol, sorry for the delay, anyways the current script still works for simply rooting but will give a no such file or directory error if init.d isn't already enabled, just ignore that.
Thank you @Ranomez
I've just tried your local root using the temproot kernel on the latest stock rom, and it worked great. So, I can say my pace doesn't have dm-verity enabled?
btw, SU was added to Stockfied, Pacefied and Stratosfied, just needs to be enabled.