Database Info

minfreemanager, must have app for the X10

Chillaxed posted this in the 2.1 optimize thread:
im suprised you guys all use task managers, i use minfree manager. it uses android's default task killing service, except i raise the last 3 values to 150,200,and 250 and the phone hardly ever dips below less than 100mb of free ram, if i run a game or something for a long time it will kill everything in the background for me (android's doing it, minfree just uses root access to change android's default values alot higher)
Click to expand...
Click to collapse
I downloaded this app, used the above settings and voila! All my system slowdowns are gone, my phone would always become unusable when my free RAM dropped below 30, now it never drops below 40, smooth as silk! With JIT enabled and this app my phone feels incredible.

So you say you put 150 in Hidden App, 200 in Content Provider and 250 in Empty App ?

zyryck said:
So you say you put 150 in Hidden App, 200 in Content Provider and 250 in Empty App ?
Click to expand...
Click to collapse
Yup, then hit apply and then also set it to run on startup. Let me know if your results are similar.

yeah, I read that post as well and installed it... works like a charm.... masterpiece.

Every time i reboot it gets the defaults values.

jpl69 said:
Every time i reboot it gets the defaults values.
Click to expand...
Click to collapse
In minfreemanager go to presets and click "save as custom" then hit apply and then hit apply at boot, should work.

jpl69 said:
Every time i reboot it gets the defaults values.
Click to expand...
Click to collapse
You need to have Rooted Phone. Isnt 150,200,250 very high doesnt this kill Apps you need like Phone or something?

Well it seems it's working well atm, but would it be possible to know what it is doing ?
Like what means the value i put in, is it automatically killing tasks when it's going under 50mb or is it killing some periodically ect...
Because I saw somewhere that android was optimised to work without task killer ect...
Thx in adv

zyryck said:
Well it seems it's working well atm, but would it be possible to know what it is doing ?
Like what means the value i put in, is it automatically killing tasks when it's going under 50mb or is it killing some periodically ect...
Because I saw somewhere that android was optimised to work without task killer ect...
Thx in adv
Click to expand...
Click to collapse
Android kill it when 20-40mb is left and with this Settings it kills when 150 is left^^

after hitting apply button it says failed
do i need an rooted phone to do this?

npk21 said:
after hitting apply button it says failed
do i need an rooted phone to do this?
Click to expand...
Click to collapse
Yes you need root

my phone is not rooting thru superuser method, i will wait for some months and wait for 1 click root

npk21 said:
my phone is not rooting thru superuser method, i will wait for some months and wait for 1 click root
Click to expand...
Click to collapse
It took me forever to get root, what finally worked was first doing shell root and then after that regular root, try it it'll work

Bialynia said:
It took me forever to get root, what finally worked was first doing shell root and then after that regular root, try it it'll work
Click to expand...
Click to collapse
........................
ok...i will try

Bialynia said:
It took me forever to get root, what finally worked was first doing shell root and then after that regular root, try it it'll work
Click to expand...
Click to collapse
...............................................
oh wow!!! it helped man....now i have an rooted 2.1 x10i.
Now what should be the first step after rooting the phone?

npk21 said:
...............................................
oh wow!!! it helped man....now i have an rooted 2.1 x10i.
Now what should be the first step after rooting the phone?
Click to expand...
Click to collapse
Install Titanium and get rid of crap you dont need like Japan Keyboard,Moxier and something like that. And Minfree+JIT would also be very good.

Wolfbreak said:
Install Titanium and get rid of crap you dont need like Japan Keyboard,Moxier and something like that. And Minfree+JIT would also be very good.
Click to expand...
Click to collapse
.............................................
well i wont mind having moxier and other crap on cell, but what is JIT , i have installed Minfree and used these settings
foreground app - 6
visible app- 8
secondary server- 16
hidden app- 150
content provider- 200
empty app- 250

npk21 said:
.............................................
well i wont mind having moxier and other crap on cell, but what is JIT , i have installed Minfree and used these settings
foreground app - 6
visible app- 8
secondary server- 16
hidden app- 150
content provider- 200
empty app- 250
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=829660 This is JIT it helped to get my Quadrant score from 500 to 760 but you need Shell Root to Install JIT and when JIT is done you need to root normal again.

Wolfbreak said:
http://forum.xda-developers.com/showthread.php?t=829660 This is JIT it helped to get my Quadrant score from 500 to 760 but you need Shell Root to Install JIT and when JIT is done you need to root normal again.
Click to expand...
Click to collapse
.........................................
i guess i have done shell root..i mean
when i installed superuser.exe first i did shell root and then i did normal root, so do i need to do that process again for JIT ?

npk21 said:
.........................................
i guess i have done shell root..i mean
when i installed superuser.exe first i did shell root and then i did normal root, so do i need to do that process again for JIT ?
Click to expand...
Click to collapse
Shell Root is only there until you Reboot so you need to do Shell Root then install JIT and when its rebootet you can do normal Root.

[Q] Setting liveoc values on boot.

Hi i was wondering if what is the proper way to use an init.d file. I want to set my liveoc value to 105 on boot using an init.d file. I edited the line below in an init.d file using a file manager with root rights.
echo 105 > /sys/class/misc/liveoc/oc_value
but somehow it does not work. do i need special permissions for this??

There's an app called "Script Manager" that lets you create scripts and have them executed at boot
Greetz

frutelaken said:
There's an app called "Script Manager" that lets you create scripts and have them executed at boot
Greetz
Click to expand...
Click to collapse
yupp its great!! i'm using it in the mean time. but i really want to know the proper way to go about using init.d files. if someone could help that would be greatly appreciated!!

Hey guys, So how I would use script manager? I want to the same of running the script at boot so liveoc starts at reboot! Thanks!
Sent from my Google Nexus S using Tapatalk

frutelaken said:
There's an app called "Script Manager" that lets you create scripts and have them executed at boot
Greetz
Click to expand...
Click to collapse
yes its great try it "Script Manager" hope you like it sory for my bad eng

idelgado782 said:
Hey guys, So how I would use script manager? I want to the same of running the script at boot so liveoc starts at reboot! Thanks!
Sent from my Google Nexus S using Tapatalk
Click to expand...
Click to collapse
I just learned all this.. so here's my take.
You simply put your script to the /init.d subfolder in /system/etc
There's one more essential step, you'll see all the scripts named with "01, 02" etc. I named mine as "58liveoc" as another post in Dec section recommended. Keeps it out of the way of system scripts and tweak scripts for kernel.
make sure you have " #!/system/bin/sh" at the top and have voltages and Max frequently set before echo for live_oc
see live oc thread for some demo scripts, backup your device!!!!
---------- Post added at 02:43 PM ---------- Previous post was at 02:36 PM ----------
Almost forgot match permissions of file to that of existing ones... should be rwxr-x--- also change owner to 0 root and group 2000 shell.... did it all using root explorer

ecksion said:
I just learned all this.. so here's my take.
You simply put your script to the /init.d subfolder in /system/etc
There's one more essential step, you'll see all the scripts named with "01, 02" etc. I named mine as "58liveoc" as another post in Dec section recommended. Keeps it out of the way of system scripts and tweak scripts for kernel.
make sure you have " #!/system/bin/sh" at the top and have voltages and Max frequently set before echo for live_oc
see live oc thread for some demo scripts, backup your device!!!!
---------- Post added at 02:43 PM ---------- Previous post was at 02:36 PM ----------
Almost forgot match permissions of file to that of existing ones... should be rwxr-x--- also change owner to 0 root and group 2000 shell.... did it all using root explorer
Click to expand...
Click to collapse
oh wow!! hmmm ok i'll give it a shot. thanks for the help. cheers.
edit: i tried what you told me and did it exactly but its still not setting my live oc on boot. is there something else i am missing??

tinselttown said:
oh wow!! hmmm ok i'll give it a shot. thanks for the help. cheers.
edit: i tried what you told me and did it exactly but its still not setting my live oc on boot. is there something else i am missing??
Click to expand...
Click to collapse
OK.. Im sure we can figure it out here
So step 1 you're using a kernel that supports live oc
Step 2 script has been copied from SD to init.d and then permissions and group set(not sure if those stick when copy/pasting)
Step three I guess is renaming it
And step 4 is the script itself...
Are you using one of the preset scripts?
If not.. what values? Voltage/Max/min/oc/gov's
When I screwed mine up my phone would crash left and right
..
Hmm... oh make sure "run on boot" is unchecked in SM for said script... reboot and CPU frequency. Should all be set as desired....
Lemme know? I'm not an expert but if you've got the time Im happy to help

does anyone know if you need round numbers for this to work?
or will something like 113 be such an odd multiplier that it breaks

xtracrispy said:
does anyone know if you need round numbers for this to work?
or will something like 113 be such an odd multiplier that it breaks
Click to expand...
Click to collapse
I think its best to use multiples of 5. That being said I think its capped at 125. Also it requires higher voltages the higher you set it. If you want a 200 MHz bus you can use trinity kernel its compiled at 200 and keeps lowest possible voltages while giving overclock aswell

wait hang on...
I always thought it was a double pumped bus, so 100 base close = 200 bus, the trinity kernel's not actually 2x faster bus than anything else, is it?

xtracrispy said:
does anyone know if you need round numbers for this to work?
or will something like 113 be such an odd multiplier that it breaks
Click to expand...
Click to collapse
yupp it works for odd numbers but like ecksion said its better to use multiples of 5.

ecksion said:
OK.. Im sure we can figure it out here
So step 1 you're using a kernel that supports live oc
Step 2 script has been copied from SD to init.d and then permissions and group set(not sure if those stick when copy/pasting)
Step three I guess is renaming it
And step 4 is the script itself...
Are you using one of the preset scripts?
If not.. what values? Voltage/Max/min/oc/gov's
When I screwed mine up my phone would crash left and right
..
Hmm... oh make sure "run on boot" is unchecked in SM for said script... reboot and CPU frequency. Should all be set as desired....
Lemme know? I'm not an expert but if you've got the time Im happy to help
Click to expand...
Click to collapse
ok i have done step 1-3 correctly. about the script i am using the one that is written for my phone, i just changed the liveoc value. is it a must to include all the steps?? can i just set the oc values and not set the stuff i don't want to change?? because currently i have only that line included in the script. i also have a test script inside init.d which does not execute as well which makes me believe that the scripts in init.d aren't being run on boot.

[Q] LG Optimus T P509 (Tmo)

Hello All,
I have looked on every forum I can think of for the past two days and can not find an answer to my problem anywhere... so if i am double posting i am very sry please point me in the right direction...
I successfully rooted my gf's optimus t yesterday using Z4root (extremely easy!!) My problem occurs when i try to flash the recovery thunderg.... I have tried many many times using a Terminal Emulator from the market and then (after much headache) I taught myself how to use adb shell. With both applications and after all my attempts I get the error message: cannot create /system/bin/flash_image: read-only file system. I have followed all the steps as carefully as I can from: All In One Recovery from Android Forums.
Here is the code I followed:
$ su
# mount -o remount,rw -t yaffs2 (your device /system path) /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# flash_image recovery /sdcard/(your device recovery.img name)
# sync
I get the error after I enter: # cat /sdcard/flash_image > /system/bin/flash_image
Any help would be much appreciated thanks!
HTC Sensation 4G
Cyanogenmod 7.0 beta
Overclocked

Why not just use ROM Manager to flash recovery?
&10chars

I have used ROM Manager in the past to flash but I thought I remembered reading somewhere that the LG p509 was having issues with clockworkmod??
btw thanks for the quick reply!

I've used rom manager twice to flash recovery for optimus t ...never any problems...
Sent from my LG-P509 using xda premium

Excalibur6677 said:
I have used ROM Manager in the past to flash but I thought I remembered reading somewhere that the LG p509 was having issues with clockworkmod??
btw thanks for the quick reply!
Click to expand...
Click to collapse
Only if you flash wrong device.
&10chars

Excalibur6677 said:
I get the error after I enter: # cat /sdcard/flash_image > /system/bin/flash_image
Click to expand...
Click to collapse
rom manager can randomly cause problems, so id stick with this first.
what is the error that you get? check the following:
is the file "flash_image" located in the root of your sdcard? and make sure that the name of the file is "flash_image." if that is not the name of the file, replace "flash_image" in the command with whatever the file name is

You're receiving that error because you didn't copy flash_image to your sdcard.
Download it here

I went ahead and used Rom Manager (figured what the hell) and it worked great! Thanks to everyone for your help!
Now that I have flashed Mik's CM7 I tried flashing francos 19.4 kernel to overclock. Everytime I would set the over clock over 748 the phone would freeze, a white screen would appear, and the phone would reboot.... any suggestions??

Excalibur6677 said:
I went ahead and used Rom Manager (figured what the hell) and it worked great! Thanks to everyone for your help!
Now that I have flashed Mik's CM7 I tried flashing francos 19.4 kernel to overclock. Everytime I would set the over clock over 748 the phone would freeze, a white screen would appear, and the phone would reboot.... any suggestions??
Click to expand...
Click to collapse
That's classic kernel panic. Lower your overclock and try again. Keep lowering until it's stable.

That what I read but I was hoping there was another option... I was looking forward to pushing this little beast a little haha

Go to 729,710...729 is recommended but some users claim to get as high as 806, I've never used higher that 787, what your experiencing is called a KP (kernel panic)...try changing your governor around than OC at higher than 710 and see what your phone is doing...or try to start over from scratch...wipe it all than reflash rom than OC....just a heads up I run 480/729-767 on interactivex (governor) and noop for I/O scheduler..follow my configuration and see what it does for you
Sent from my LG-P500 using xda premium

Excalibur6677 said:
That what I read but I was hoping there was another option... I was looking forward to pushing this little beast a little haha
Click to expand...
Click to collapse
It's luck of the draw. Some can do 768 or better while others struggle at 729.
For example, mine is stable at 748 but panics at 768.
Trust me, your phone is a whole lot better now than when you bought it

Oh no question about it!! Its running sooo much smoother. The Optimus is actually my gf's phone. I put CM7 on it because I running it on my HTC Sensation and its awesome!

You can only push this device so far before you fry it, settle for adequate performance and stellar battery life....I'm not even sure why there's an option for us to OC past 787, our phones don't have a snapdragon processor....some roms can handle OC at higher voltages and some can't, most I got out of cm7 is 787 but its not stable enough for me
Sent from my LG-P500 using xda premium

Thanks man Ill take your word for it! Any other suggestions/concerns with the phone?? I just flashed the rom yesterday so i dont know what to expect (as far as bugs and such) are there any nightlies yet?

Well if you have a computer, learn how to code source and you can cook roms for everyone else to enjoy....there is alot more to android development other than the basics...ie...root than custom recovery and custom roms....speaking of kernel panics, I just had one at 748 on popdogs oxygen port, cm7 I can easily run 767...btw are you using no frills or setcpu
Sent from my LG-P500 using xda premium

Jrhodes85 said:
You can only push this device so far before you fry it, settle for adequate performance and stellar battery life....I'm not even sure why there's an option for us to OC past 787, our phones don't have a snapdragon processor....some roms can handle OC at higher voltages and some can't, most I got out of cm7 is 787 but its not stable enough for me
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Actually, CPU's rarely fail due to OC'ing. Instability forces you to lower the clock. The phone's metal casing and battery acts as a heatsink.
Batteries on the other hand are extremely susceptible to damage due to excessive heat. This is what you need to watch.

Is the stuff hard to learn? I'm not bad with a computer but to be honest it took me like two hrs to figure out how to adb shell haha... i believe im using setcpu with the interactiveX governor but i dont have the phone right in front of me so im not sure..

Excalibur6677 said:
Is the stuff hard to learn? I'm not bad with a computer but to be honest it took me like two hrs to figure out how to adb shell haha... i believe im using setcpu with the interactiveX governor but i dont have the phone right in front of me so im not sure..
Click to expand...
Click to collapse
Read the sticky in the Dev section. Links to all the tutorials are there. Read them and see if it's beyond your skill set.

Didnt know that either thanks! Ill definitely keep that in mind for my Sensation shes tends to get a little warm. I have it OC at 1.56 which isnt that high but it still gets warm.

[Q] How to make a flashable rom from romdump

how to make a flashable rom/firmware from the images from romdump.
need it for my rk3188 tablet.
thanks

th3f33 said:
how to make a flashable rom/firmware from the images from romdump.
need it for my rk3188 tablet.
thanks
Click to expand...
Click to collapse
Depends
Whats The Main Device
Screen DPI
Kernel
Droid Version

Pranto Roy said:
Depends
Whats The Main Device
Screen DPI
Kernel
Droid Version
Click to expand...
Click to collapse
Device is:
Skyworth skypad x7010 , rk3188 quad, 2gb ram, 8gb storage
DPI - 160
Kernel - i dont know, still using the stock...
running on jellybean 4.1.1

th3f33 said:
Device is:
Skyworth skypad x7010 , rk3188 quad, 2gb ram, 8gb storage
DPI - 160
Kernel - i dont know, still using the stock...
running on jellybean 4.1.1
Click to expand...
Click to collapse
Is It The main device's or your's??

Pranto Roy said:
Is It The main device's or your's??
Click to expand...
Click to collapse
its mine,
i have stock images from rom dump
but it is soft bricked as of now.. due to some build.prop errors or maybe when i set the cpu minimum frequency state...
.

th3f33 said:
its mine,
i have stock images from rom dump
but it is soft bricked as of now.. due to some build.prop errors or maybe when i set the cpu minimum frequency state...
.
Click to expand...
Click to collapse
If Both Build.prop 's are of same droid version replace it with your phone's
cpu won't Matter

thanks for the replys
Pranto Roy said:
If Both Build.prop 's are of same droid version replace it with your phone's
cpu won't Matter
Click to expand...
Click to collapse
yeah i would really like to do that, to keep my save files in some rpgs i played, but i had this problem where i cant access the tablet thru adb, although i am rooted, usb debugging is on, and have installed the right / working/ correct adb drivers for my device although i was supposed to be able to do it before, i dunno what had happened to it,
maybe it happened somewhere during my initial setup of factory restore - root - clear bloat apps - clear cache - factory restore,
but i can access the tablet with adb when it is turned off, but even though i can access it with adb, cant seem to push any file anywhere, and cant use SU command, it just goes blank, and adb root / adb remount not working too, adb root says cannot run in production build and remount is not having permission.
i also checked the default.prop and it says
ro.secure=1
ro.debuggable= 1
when i check the adb devices when the tablet is off, it says
name - device
no access to recovery mode anymore, can only access the device in off state and flash state, (rkbatchtool flash state - green)
whenever i try to push the recovery button (Power + Volume Up, used to be working before i flashed the incorrect recovery) it ends up in the flash mode.
when the device is turned on and stuck in grey screen after logo, it can be detected in the windows as android adb interface but adb devices doesnt detect the tablet, even after i restart the adb thru adb kill-server adb start-srver

th3f33 said:
yeah i would really like to do that, to keep my save files in some rpgs i played, but i had this problem where i cant access the tablet thru adb, although i am rooted, usb debugging is on, and have installed the right / working/ correct adb drivers for my device although i was supposed to be able to do it before, i dunno what had happened to it,
maybe it happened somewhere during my initial setup of factory restore - root - clear bloat apps - clear cache - factory restore,
but i can access the tablet with adb when it is turned off, but even though i can access it with adb, cant seem to push any file anywhere, and cant use SU command, it just goes blank, and adb root / adb remount not working too, adb root says cannot run in production build and remount is not having permission.
i also checked the default.prop and it says
ro.secure=1
ro.debuggable= 1
when i check the adb devices when the tablet is off, it says
name - device
no access to recovery mode anymore, can only access the device in off state and flash state, (rkbatchtool flash state - green)
whenever i try to push the recovery button (Power + Volume Up, used to be working before i flashed the incorrect recovery) it ends up in the flash mode.
when the device is turned on and stuck in grey screen after logo, it can be detected in the windows as android adb interface but adb devices doesnt detect the tablet, even after i restart the adb thru adb kill-server adb start-srver
Click to expand...
Click to collapse
Complex Problems
Don't Think Can Be Solved At Home
Contact Customers Care

RE:
well i dont think i can do that because
skyworth is a chinese company, and they dont have a good support for the tablets they've released, i cant understand chinese/cantonese/mandarin too
in our local provider, i also have used the most of my warranty,
rooting/flashing the tablet voids the warranty
even though i had sucessfully made them replace my first tablet due to soft-bricking it, all i did is made the tablet bootable only to flashmode, and they didn't even understand/tracked what i had done, all they did was mark the device as faulty mobo then replaced it with a new one,
so right now i am asking for the online community in some help on how to restore it,
oh btw i have the stock romdump images of it. during the state where it is 100% working.

Pranto Roy said:
Complex Problems
Don't Think Can Be Solved At Home
Contact Customers Care
Click to expand...
Click to collapse
can you instruct me on how to make an update.zip that will replace the build.prop with my default build.prop from what ive learned, it is possible to make one right?

th3f33 said:
can you instruct me on how to make an update.zip that will replace the build.prop with my default build.prop from what ive learned, it is possible to make one right?
Click to expand...
Click to collapse
Possible But Can't Say If It Will Work.
Upload Your Build.prop
I'll Be Quite Late Though

Pranto Roy said:
Possible But Can't Say If It Will Work.
Upload Your Build.prop
I'll Be Quite Late Though
Click to expand...
Click to collapse
here it is.. oh i forgot to rename it to build.prop, it is a backup made weeks ago..
'well i've tried adding an update.zip and I dont think i can use it anyways, i think i need to find a way to flash the romdumps that i have.'

th3f33 said:
here it is.. oh i forgot to rename it to build.prop, it is a backup made weeks ago..
'well i've tried adding an update.zip and I dont think i can use it anyways, i think i need to find a way to flash the romdumps that i have.'
Click to expand...
Click to collapse
Allow Me 24 Hours
As Its Mid-Night In My Country I'll Do It Tomorrow

Pranto Roy said:
Allow Me 24 Hours
As Its Mid-Night In My Country I'll Do It Tomorrow
Click to expand...
Click to collapse
ok its already 2:51 am here, cant sleep without my tab running
still reading a lots of forum topics related to my problem...

RE:
I got my access back to the device thru adb
what i did was added the dev id of my device in the adb_usb.ini
now i can push files back to it
now i need to it to the working state

Verizon Root Guide (Knox still good)

I take no credit other than compiling info and making a guide. All credit goes to http://forum.xda-developers.com/member.php?u=4911585 (br3w3r, Chainfire and Princecomsy)
http://forum.xda-developers.com/att-...-root-t3410403
Also credits to Mastajeff for originally making the guide for T-Mobile.
First off download these files: http://d-h.st/PK3q
Extract them to whatever folder you want, there will be 5 files in there.
Folder named: "su" contains the SuperSU and thing needed to root the phone
ADB Setup EXE called: "adb-setup-1.4.3.exe" Needed to install ADB and the Drivers
Special patched Odin that skips the SHA 225 called: Odin PrinceComsy.exe (Mainly for AT&T)
.ini file named: "Odin3.ini"
Last, file, named: "Samsung_G935x_QC_Rooted_BOOT.TAR", this is the engBoot for the phone.
NOTE: Some users have experienced endless boot loop; this seems to be caused by using a package disabler that disabled certain services.
If you used one and end up getting an endless boot loop try wiping the cache and factory reset the phone.
I suggest you backup your phone before doing this, just in case something happens.
Install ADB by running adb-setup-1.4.3.exe
Make sure to put your phone into downloading mode (Power off--- Hold Down arrow + Home + Power button)
Open up Odin and click AP and mount Samsung_G935x_QC_Rooted_BOOT.TAR
Once restarted put the phone into USB debugging mode (Need Developer options for this)
To get developer mode, go to "About" then tap "build number" about 6 or 7 times
Go back to settings and you should now see developer options, turn on USB debugging
Now back on your PC, Move the folder named "su" into your ADB folder (Default Path: C:\adb)
Run CMD by either Win + R and typing cmd or from the control panel.
Once CMD is open type this
Code:
cd C:\adb\su
or whatever your path to your "su" folder.
After that type root.bat
Wait for the CMD to finish and then your phone should restart
Once your phone has finally restarted you will notice that SuperSU was installed and root should be working, download root checker to find out for yourself.
If your CMD just says starting Daemon and doesn't proceed any further than that, then you forgot to make sure USB debugging was turned on.
If everything went well you will see the CMD was able to push SuperSU.
You can now install Xposed via Flashfire. Unfortunately, TWRP does not work on this method, so, DO NOT TRY, there is a chance that you can Brick your phone from doing that.
NOTE: DO NOT UPDATE THE SU BINARY!
Fix for wifi bug on restart: http://forum.xda-developers.com/tmo...ticky-root-t3327399/post67592828#post67592828
Thanks 2swizzle for mentioning this.
If you want to fix the lag/slowness download any CPU or Kernel Editor or changer.
This one works fine: https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en
To fix the lag
Open up the APP
Go into the CPU settings
Set CPU Governor to ondemand
Apply on boot
Thanks to orgulloso4202 I have found a way to fix the battery drain and help with Youtube and the CPU.
L Speed seems work fine and my battery no longer drains when using the recommended Profile.

Interesting. First Sammy I've seen that Knox is intact but Samsung Pay won't work.

Have been searching a bit after rooting mine, don't suppose anyone has word on how to or if you can install TWRP or Xposed?

AlphaD1 said:
Have been searching a bit after rooting mine, don't suppose anyone has word on how to or if you can install TWRP or Xposed?
Click to expand...
Click to collapse
Got Xposed with flashfire but sadly it left me in a boot loop on the verizon logo, think I need to start over.

If we can get the bootloader unlocked it will be fun times indeed!
Going to try this soon.
Don't care if my phone blows up, it's the 4th here in the U-S-A!
Besides my trusty Nexus 6 and even Note 5 are ready for duty!
Xposed would be nice, I do miss those features.
Layer support even just to change up the statusbar.
Themes have done a nice job to blackout the device.
Root, center clock and some battery icon customizations and I'm all set for sure.
Perhaps the horrid standby time will be fixed.
Because as of late this phone has lead to high frustration to the point where I want to see how good it skips across the lake! But when I think of how much I paid for it, well I keep it in my pocket!

TWRP doesnt work, but you can install Xposed from flashfire.

Argyrus said:
TWRP doesnt work, but you can install Xposed from flashfire.
Click to expand...
Click to collapse
So with Xposed working, that means battery saving apps like Greenify and Amplify work now for our devices?

GigaSPX said:
So with Xposed working, that means battery saving apps like Greenify and Amplify work now for our devices?
Click to expand...
Click to collapse
Not 100% sure.
I haven't really installed it on my phone. I only know Xposed work due to the countless others that tried it; however, I don't see why those should not work.

Xposed is working fine and you guys need to install a kennel app and change the engboot settings to ondemand, that's why it lags and slow

2swizzle said:
Xposed is working fine and you guys need to install a kennel app and change the engboot settings to ondemand, that's why it lags and slow
Click to expand...
Click to collapse
Root gives performance issues??

GigaSPX said:
Root gives performance issues??
Click to expand...
Click to collapse
Negative. The eng kernel has shown some lag and performance slowdowns for some people but can be remedied by changing the governor.
Sent from my SM-G935V using Tapatalk

MisterSprinkles said:
Negative. The eng kernel has shown some lag and performance slowdowns for some people but can be remedied by changing the governor.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Which governer do you recommend we use for optimal performance?

zachchen1996 said:
Which governer do you recommend we use for optimal performance?
Click to expand...
Click to collapse
Would seem the consensus is on-demand.
Sent from my SM-G935V using Tapatalk

Am I missing the download files for Verizon or are they not posted here

Can anyone report that they are suffering overheating issues after rooting even after a FDR? Thanks!

shawnten said:
Am I missing the download files for Verizon or are they not posted here
Click to expand...
Click to collapse
They are posted here: http://forum.xda-developers.com/tmobile-s7-edge/how-to/how-to-root-s7-edge-t3410470
I guess maybe I should make a thread here with all the download links and some other links that fix things.

Thread updated!
Added links and more stuff.

farfromovin said:
Interesting. First Sammy I've seen that Knox is intact but Samsung Pay won't work.
Click to expand...
Click to collapse
If you try opening the app you will get a message saying: "Access denied. Unauthorized modifications have been made to your device."
I am guessing that the app has some other type of security that checks if phone has been modded.

Anyone tried to unroot? Does Samsung Pay work if you revert NB to stock?
Sent from my SM-T320 using Tapatalk

How do we install xposed with flashfire?