Related
NEW THREAD HERE
http://forum.xda-developers.com/showthread.php?t=765822
THIS IS NOW AVAILABLE IN EXT2, EXT3, AND EXT4 VARIATES(DOES NOT REQUIRE CUSTOM KERNEL!)
IF YOU ARE USING JH2/JH3 FIRMWARE, READ THIS POST, IT IS VERY VERY VERY IMPORTANT:
http://forum.xda-developers.com/showpost.php?p=7650658&postcount=312
The reason this step is important is that the JH2 firmware is a test build, and as a test build it has GPS logging enabled... this uses an absolutely ludicrous amount of storage space- and the real kicker? It uses the space OUTSIDE of this fix, meaning your phone will encounter low space warnings very quickly if not instantly upon applying the fix!
THIS NOTE IS FOR EVERYONE. THESE FIXES WORK BETTER FROM A FRESH FLASH. THEY *CAN* WORK WITHOUT A CLEAN FLASH BUT REALIZE THAT YOU ARE POTENTIALLY PUTTING YOUR DATA AT RISK!
What this does (Shamelessly stolen from RyanAZ's OP)
Creates a VIRTUAL EXT2 filesystem inside the stock RFS filesystem on the internal SD card, with a 4KB block size. This means that this lag fix creates a buffer between the real filesystem and the android system. This buffer should reduce the amount of disk I/O required for all operations by utilizing EXT2 buffering, as well as not writing file access times to disk, etc.
PROS
Doesn't rely on external SD
Easy to do
Reverse-able
Real, noticeable performance increases outside of Quadrant (Seriously don't pay attention to Quadrant, but if that's what you care about this will make your pants tighter)
CONS
Uses EXT2 file system which is non-journaled and CAN become corrupted, frequent backups are strongly recommended! (2.2 Implements error checking every 30 mounts)
It's also up for debate as to whether this adds extra strain on your internal memory.
1.0 SECTION WILL FOLLOW 2.0 STUFF
AS WITH ANY FIX: READ THE INFO, KNOW WHAT YOU'RE DOING, AND UNDERSTAND POTENTIAL CONSEQUENCES!
LINKS TO GET THE GOODS BELOW!!
The RyanZA version that does EXT2 is Available at the thread linked below
http://forum.xda-developers.com/showthread.php?t=751864
RyanZA has put out an APK version of the fix for people less comfortable doing the update.zip or batch file methods! (This is the V1 lagfix, so for people having issues with the newer fixes this one might work for you!)
TEMPORARILY DOWN UNTIL VERSION 2.3
http://forum.xda-developers.com/showthread.php?t=760571
There is also an update.zip version that does EXT2, EXT3 (1500 Quadrant), or EXT4 (1800 quadrant) versions thanks to Tayutama! I've tested this to work on JH2, and JM5 firmwares! There is also a special version for Captivate JH2 (It also works for JH3) that fixes the GPS Log issues so no need to edit the XML's yourself!
http://forum.xda-developers.com/showpost.php?p=7632258&postcount=208
praveer01 threw up a handy writeup for those of you running Unbuntu or any other Linux system:
http://forum.xda-developers.com/showpost.php?p=7671640&postcount=583
READ THE INSTRUCTIONS AND REMEMBER THIS IS *VERY* BETA, NEITHER RYANZA OR MYSELF WILL TAKE RESPONSIBILITY FOR MELTING YOUR DEVICES OR KILLING YOUR DOG IF THIS FAILS. That said, this thread has been very good about helping people who borked their Captivates with 1.0
Here's the reasons you'd want to do this:
Benefits over version 1
1.7GB of application data available, with no data loss. (Up from < 1GB)
e2fsck of the EXT2 partition on each boot. (To scan and fix corruption!)
Correct busybox version included! YES! (Because no one can get it right =P)
/app directory included in the fix for faster application installs.
Mounts instead of symlinks for extra performance as OS does less work (about 100 or so more quadrant).
2.3 Changelog
/dbdata has been removed. This fixes maps issues.
/app-private is now a symlink to /app/app-private. This fixes paid apps issues.
2.2 Changelog
/app-private is included
A second EXT2 partition is created in fast /dbdata storage. /dbdata/databases are moved inside here for increased speed in applications that use it. (System apps mostly, I think)
Proper parameters for e2fsck.
0% space reserved in the EXT2.
EXT2 partition reduced from 1.7GB to 1.5GB to allow more space for captivate users.
Running from a stock install of JH2 I'm currently getting 2300 quadrant scores with ALL AT&T BLOATWARE AND TW ENABLED!
IF YOU'RE NEW TO THIS KIND OF THING, OR ARE WORRIED ABOUT POSSIBLY HAVING TO REFLASH YOUR PHONE, YOU PROBABLY SHOULD WAIT A LITTLE WHILE FOR MORE PEOPLE TO TEST THIS!
___________________________________________________________________________
Found this over in the i9000 forums and tested it myself- I'm getting 2100+ quadrants scores with the stock Captivate kernel and it doesn't hang up on the I/O portion like all the other fixes... in addition you don't require an SDcard for this to work.
Original thread:
http://forum.xda-developers.com/showthread.php?t=748596
One of the folks over there created a one-click lagfixer and it DOES work for the Captivate:
http://forum.xda-developers.com/showthread.php?t=749495
FOR PEOPLE WHO DONT WANT TO READ THE ORIGINAL THREAD
This fix creates a 1GB file formatted in EXT2 and moves all of your apps, data, dbdata into it which DRASTICALLY improves I/O performance. One advisory SHUT YOUR PHONE DOWN PROPERLY, this means no yanking the battery out. Due to it being EXT2, non graceful shutdowns CAN cause corruption.
Edit: No wake up lag either- not sure if that's due to using a non-modded kernel or because the ext2 file is located on the internal memory.
Edit 2: Make *SURE* before attempting this that you have Busybox 1.17.1 or the boot animation script calls won't work!
Link to Busybox 1.17.1
http://forum.xda-developers.com/showpost.php?p=7574130&postcount=229
DO NOT UPGRADE BUSYBOX TO 1.18! 1.18 REMOVES MAKEFS WHICH IS NECESSARY FOR THIS PROCESS
Edit 3: I haven't used the stock Captivate ROM for a while, but this feels quite fast- Also worth noting that this SHOULD work with any ROM- including i9000, I might test that later but I'm enjoying having functioning haptic feedback. 2200 Quadrant with Shootme and market running! Since seeing is believing I've thrown in a screen cap.
Confirmed working with JM5 ROM
IF YOU USE A MAC OR JUST CAN'T GET ADB TO WORK THIS FIX CAN BE PERFORMED WITHOUT A PC- SEE THE POST BELOW:
http://forum.xda-developers.com/showpost.php?p=7583565&postcount=116
Ha! it worked thanks dude you should rename this thread with brackets. " [Fix][Lag] Alternative by {author name} - alpha " .. so it can gain more attention. Just we need two more fixes GPS and my attenna issues then i'm good with my captivate.
[edit]omg my phone is flying see this is how my phone should have been out the box it flies!
rebooting from this now. I should not that I had to run the shell script manually because it kept not prompting me for SU...? No biggy though.
Will test, can't post screen from work though.
Edit: running quadrant....
Edit: ... *thud* 1961, 2237 ( FB, gmail, etc were running & syncing in background last time!)
mykenyc said:
Ha! it worked thanks dude you should rename this thread with brackets. " [Fix][Lag] Alternative by {author name} - alpha " .. so it can gain more attention. Just we need two more fixes GPS and my attenna issues then i'm good with my captivate.
[edit]omg my phone is flying see this is how my phone should have been out the box it flies!
Click to expand...
Click to collapse
Title change done!
Glad this is working for you guys, I've tried every fix so far and this one is MILES ahead of the others in terms of real world improvement (At least for me).
Zilch25 said:
Title change done!
Glad this is working for you guys, I've tried every fix so far and this one is MILES ahead of the others in terms of real world improvement (At least for me).
Click to expand...
Click to collapse
I agree! waking up this morning in fear of being fired from my job, this made my day a little lol.
Besides downloading the .zip file, do i need anything else?
Also, i am assuming we install this by booting into recovery mode?
Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
LockeCPM4 said:
Besides downloading the .zip file, do i need anything else?
Also, i am assuming we install this by booting into recovery mode?
Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Nope just run lagfixme.bat this in the zip file, run and leave your phone screen on so you can see the root request permission.
LockeCPM4 said:
Besides downloading the .zip file, do i need anything else?
Also, i am assuming we install this by booting into recovery mode?
Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Nope, you don't need anything else. Also nope, no recovery mode shenanigans, just unzip the file, turn on debugging mode on your phone, plug her in, and run the batch file!
Also you MUST undo any prior lag fix
Sent from my SAMSUNG-SGH-I897 using XDA App
again, those high quadrant scores mean nothing unless you get no lag in real world testing. Such tests can be done in the following apps: Dolphin HD browser, facebook, twitter, touchdown, k-9 email
All common applications that have serious lag on the SGS. Assuming that this method does fix I/O problems (Especially the I/O quadrant tests), there should be no lag in those apps. Anyone try?
I noticed this in the original thread:
EDIT3 09 aug 0033HKT:
it's not for the benchmark only, instead, it has very good effects on ur phone's io
Click to expand...
Click to collapse
Sounds good, I'll give it a try
andy2na said:
again, those high quadrant scores mean nothing unless you get no lag in the following apps: Dolphin HD browser, facebook, twitter, touchdown, k-9 email
All common applications that have serious lag on the SGS. Assuming that this method does fix I/O problems (Especially the I/O quadrant tests), there should be no lag in those apps. Anyone try?
Click to expand...
Click to collapse
I know you have your reservations about these fixes, and you've been very vocal about your opinions on the matter. I happen to agree with you on most points, but as someone who has tried all of these, I can tell you this doesn't feel like the placebo effect. I'll install DolphinHD and toy with it, but everything I've messed with so far seems much snappier. Feel free to try it yourself, it literally takes less than 5 minutes to install, and is completely reverse able.
Edit: So far with dolphin HD things feel snappy, the only exception is pages absolutely laden with flash lite ads... but that's not really an I/O issue, if you've got any particular web site recommendations I'd be glad to check them out and let you know my mileage
So far so good, I recently erased my phone (130mb lag fix not big enough). And this is working wonderfully so far, dolphon browser HD(my favorite browser) works very fast. So far so good, I'll report back when I've tried it for the whole day.
Zilch25 said:
I know you have your reservations about these fixes, and you've been very vocal about your opinions on the matter. I happen to agree with you on most points, but as someone who has tried all of these, I can tell you this doesn't feel like the placebo effect. I'll install DolphinHD and toy with it, but everything I've messed with so far seems much snappier. Feel free to try it yourself, it literally takes less than 5 minutes to install, and is completely reverse able.
Edit: So far with dolphin HD things feel snappy, the only exception is pages absolutely laden with flash lite ads... but that's not really an I/O issue, if you've got any particular web site recommendations I'd be glad to check them out and let you know my mileage
Click to expand...
Click to collapse
Thanks! I'll give it a try as I don't like being tied down to 130mb for application storage using the NAND fix.
Basic usage should be snappy:
- opening\closing\switching tabs
- scrolling with the volume buttons
- pinch zooming
- loading multiple pages
On stock, and even mimocan's fix, it would lag horrible to the point of unusability.
The only way to make it run smoothly and quickly was to move all your /data/ to the /dbdata/ on the NAND (but limited to 130mb of app space)
I guess my install question wasnt answered. You said run the .BAT file, do i run it on my pc? And what software on the pc side must i have installed?
Thanks for helping a noob!
Sent from my SAMSUNG-SGH-I897 using XDA App
Zilch25 said:
I know you have your reservations about these fixes, and you've been very vocal about your opinions on the matter. I happen to agree with you on most points, but as someone who has tried all of these, I can tell you this doesn't feel like the placebo effect. I'll install DolphinHD and toy with it, but everything I've messed with so far seems much snappier. Feel free to try it yourself, it literally takes less than 5 minutes to install, and is completely reverse able.
Edit: So far with dolphin HD things feel snappy, the only exception is pages absolutely laden with flash lite ads... but that's not really an I/O issue, if you've got any particular web site recommendations I'd be glad to check them out and let you know my mileage
Click to expand...
Click to collapse
Tested:
Gmail, FB (official), GVoice, messaging, TWC, stock browser, andoku (yeah, I can SEE it faster. and thats a simple app!)
LockeCPM4 said:
I guess my install question wasnt answered. You said run the .BAT file, do i run it on my pc? And what software on the pc side must i have installed?
Thanks for helping a noob!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Plug it into your pc making sure the USB debugging is on. Download the zip file, extract all of it. Run the Lagfixme.bat and make sure you leave the phone screen on (tap it if low time out) to accept the super user permission request. After that it will finish on it's own. Just reboot the phone by shutting it down. The zip file contains all the necessary files.
Edit: and make sure your phone is rooted / has the drivers installed!
LockeCPM4 said:
I guess my install question wasnt answered. You said run the .BAT file, do i run it on my pc? And what software on the pc side must i have installed?
Thanks for helping a noob!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The zip file actually contains a copy of the adb as needed, so other than the drivers to be able to connect via USB Debugging, nada.
All I can say is wow. Definitely not placebo. Certain apps used to take forever to initialize (i.e. Facebook, Market). They now start up almost instantly.
I have not tried any of the other "fixes" because to me they break more than they fix. I don't want to use my external SD in a way that makes it non-swappable and I don't want to be restricted to 130mb for apps. This fix is the best so far. I'm guessing it may not be necessary once we have Froyo (double the RAM) but it does the trick for now.
Seemingly didn't work for me, my Quadrant scores are still sitting at 948. I'm on the stock ROM, and undid the previous speed fix I had.
LockeCPM4 said:
I guess my install question wasnt answered. You said run the .BAT file, do i run it on my pc? And what software on the pc side must i have installed?
Thanks for helping a noob!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It was answered:
You need root
Download zip file- unzip it.
Put phone into debug mode and plug in USB
run the included .bat file from the zip file and it will do the rest for you.
It has it's own adb.exe but you might need to install the SDK if you haven't already. That's it though.
Hey all i created this thread for ADVANCED users (and some newbies lol) so that i can better help users tweak and improve performance on their eris. My inbox was getting crazy so i thought this would be better i will still take pm questions but it would be better if we can all learn here. This isn't really a place to report bugs as it would be better to contact your respective developer or post in that developers thread. I will try my very best to get the best performance out of your eris and hopefully we will have some fun along the way. So hopefully this can help take some of the load off of the developers threads and reduce noob-age.
I ONLY ASK THAT IF USERS WANT TO TWEAK I STRONGLY RECOMMEND THAT YOU EITHER..........
1) PURCHASE ROOT EXPLORER FROM THE MARKET OR THE FREE ESTRONGS FILE EXPLORER APP FROM THE MARKET WHICH ALSO ALLOWS ROOT ACCESS AS WELL.... BUT I THINK ROOT EXPLORER IS BETTER IMHO.
2) HAVE ADB SET UP FOR YOURSELVES AT HOME OR KNOWLEDGEABLE OF ADB. I WILL NOT HELP YOU SET UP ADB OR THE SDK
ALSO I RECOMEND PURCHING THE FULL VERSION OF TITANIUM BACKUP AS IT IS AN INVALUABLE TOOL FOR ROOTED USERS AND MAKES BACKING UP AND TWEAKING MUCH EASIER FOR NEWBIES PLUS IT HAS SOME REALLY AWSOME FEATURES
so hopefully this will give us fun things to do in between releases from our devs. And always remember to donate to these awesome awesome eris devs for their hard work and commitment to us.
i want to keep an open discussion thread, nothing is off the table.
kernels
kitchens
cooking
roms
tweaks
hacks
apps
fixes
workarounds
you name it lets talk
lets figure it out together while learning along the way
Things are always changing so if you see any errors or things that need to be updated please let me know and i will be more than happy to get the correct information posted.
Moving apks and deleting dulicates...make your system efficient
YOU need either rootexplorer OR be ADB inclined to do the following....
i was thinking while doing some root exploring of ways to make this rom more solid and here are a few tips i thought everyone could use.
IF YOU DONT HAVE DUPLICATES DONT KILL YOURSELF SEARCHING JUST CONSIDER YOURSELF LUCKY. AND YOU DONT NEED THIS POST
FIRST
when i flash a Rom i always do my set up. here is an overview of what i do when i flash........
-i flash the Rom
-then i login to google as normal so i can receive Titanium Backup (TB) and Root Explorer (RE) from the market updates
if someone could be kind enough to give us a sample command to use terminal to install apps from the sd would be a great shortcut for us
-move those two apps from data/app to system/app
-then i do a full wipe (huh a full wipe you say....system files are never wiped....they can only be flashed over, so TB and RE will still be there)
-clean nand (so if you get crazy and screw up you can easily start over)
-Rom surgery
-Restore
-login to google last and sync
-batt tweaks and extras
this process IMHO makes your rom way more efficient than flashing, login and syncing.
OK
first thing i do when i flash a rom is to remove junk
i navigate with either explorer to system/app folder
then i remove all the useless apps i dont use, need or want
AND/OR remove the "ONE USE" apps (like setupwizard.apk only need it once or none at all if your a pro )
this reduces the ROMs footprint making it smaller
the smaller the Rom the better the faster
here are some things i like to rip out of system/app folder....
ADWLauncher.apk (make sure you have another launcher first i use lanucher pro)
Mail.apk (i use gmail)
Twitter.apk (i currently dont tweet)
ProTips.apk
HtcCalibrate.apk (after i calibrate of course)
Launcher2.apk(why have a bunch of other launchers you dont use hogging memory get rid of them)
MagicSmokeWallpapers.apk (this dont work for me but other do)
Carhomegoogle.apk ONLY
etc. there are others you can remove as well depending on you
and we will experiment to find more......
NEXT
i like to move IMPORTANT apks or apps from the data/app folder to the system/app folder epically if your Rom dev has not updated the gapps lately or you cant get access to the latest gapps.zip.
if you do not then you will end up with a lot of duplicate apps installed in your system when ever you receive a gapps update and that wastes memory and will cause memory issues in the future and it screws with autokiller
i like to move my favorite launcher (launcher pro paid) to the same place where launchers go, in the system/app folder (why have your launcher where regular apps go and get killed by autokiller) i think this is better for the system and doesn't hog your app data space plus it adds stability to your launcher.
here are some things i like to move into system/app.....
i like move into system/app are
launchers (stabilze launcher)
keyboards (should speed up keyboard strokes)
root tools and IMPORTANT apps (R.E. T.B.)
security apps (never deleted or wiped in case of theft, hoping thief is not nerdy)
any of the latest gapps update
and some others
this way if any issue occurs wipe and restore is easy as pie
IMPORTANT: APPS IN THE SYSTEM FOLDERS DO NOT GET WIPED OR DELETED DURING A FACTORY DATA WIPE OR DALVIK WIPE.....THEY CAN ONLY BE FLASHED OVER BY A ROM(OVERWRITTEN)
APPS IN THE DATA FOLDERS WILL GET DELETED DURING A FACTORY WIPE......BUT NOT DALVIK
i know we are ALL have at least one pair of identical (double apks in the system)
-but the identical apks have different names
-on is in data/app the other is in system/app
if you have updated ANY google app then chances are that you may have some double apps on your system wasting. when we update these google apks 'think' the rom comes with the apk already and is stored in the protected system/app folder WHILE the actual update is stored in the data/app folder (or where regular apps go) under a different name
EXAMPLE
google maps
-MAPS.apk ........is stored system/app
-com.google.android.app.map-1.apk........is stored in the data/app (this is the latest update of google maps and should replace the older MAPS.apk in system/app)
-these are the SAME APKs
hmmm so think gmaps is 5-6 megs in size and you have 2 of them so thats like 10-12 megs in your system, get rid of the old one.
there are two thing you can do here with two different benefits
-you can either remove the copy from either the data OR system folders depending on what you prefer.
if you remove the old app from system/app that means easier updates with now file moving BUT less app storage
OR move from data/app to system/app which means less FCs, more other app memory, and dealing with future updates and moving each app.
i like to move the new apks to the system/app where they belong
unstable Launcher PRO
my launcher was very unstable for a while wasn't a big deal for me
soo i decided to move my launcher to the system/app folder like all the other launchers....
I think the instability of that launcher was because of AUTOKILLER thinking this is just a regular app in data/app which it was at the moment. i may be wrong but autokiller doesnt kill system apps. so i move my launcher there and guess what now my launcher is much better and faster and stable beacuse you now have lots more memory.
SPEED TIP: in spare parts speed up your transition and animation windows to FAST
MOVING APPS ADVANCED SHORTCUT
i finally figure out a great short cut for moving apps
-first rename and put your favorite file manager (ROOT EXPLO) onto the sd.
to be even faster rename and put your launcher and TB on there too.
-after flashing a rom bypass the setup (touch the android screen) to home screen.
-open terminal
-type
SU
cd sdcard
busybox install yourapp.apk /data/app
-now you have the file explorer ready to go
instead of trying to restore wipe restore.
and hopefully you know what to do next.
so to summarize...
-get rid of junk you dont use and free up that memory
-move apps to the proper locations in system/app AND/OR data/app
-make sure you dont have multiple google apps using different names
"MAPS.apk" and "com.google.android.app.map-1.apk" IS THE SAME APP IN DIFFERENT LOCATIONS. remove the old and put the new in system/app
make sure your main launcher is in system app so it doesn't keep getting killed by auto killer settings and reloading
Replace THESE apps = with THESE apps
system/app = data/app
Gmail.apk = com.google.android.apps.gm-1.apk
ChrometoPhone.apk = com.google.android.apps.chrometophone-1.apk
Maps.apk = com.google.android.apps.maps-1.apk
CarHomeGoogle.apk = com.google.android.carhome-1.apk
GoogleSearch.apk = com.google.android.googlequicksearchbox-1.apk
Googles.apk = com.google.android.appsunveil-1.apk
SuperUser.apk = com.noshufou.android.su-1.apk
AutoKiller = com.rs.autokiller-2.apk
TitaniumBackup = com.keramidas.TitaniumBackup-2.apk
Twittter = (forget)
Voice= com.google.android.apps.gv-1.apk i think
YouTube=
delete OLD in system/app = move NEW from data/app to system/app
YES i did all those with success more memory and speed and a massive increase in overall Rom stability
there may be more
BUT ALL THESE HAVE DUPLICATE APPS USING DIFFERENT NAMES stored in data/app and/or system/app WHEN the latest update should be system/app IMHO to prevent AUTOKILLER from always killing i believe autokiller will try to kill data apps first before system apps.
i still have my auto killer set at optimum and things work even better now
and i gained 25mb of system memory no more Force closes
Batt tweak custom set up process (a 1-2 day process to complete)
How to increase battery life
first off battery life depends on many factors.....
where you live, work, and the daily place you travel to.
im one of the lucky ones who has a cell tower down the street from me here in S. FL.
WARNING: IF you multitask alllllll day on your phone then this is not for you.This is more beneficial when your phone is at rest or in an idle state or screen off state.
Others may not be so lucky and may live in a bad signal area....which causes your phone to constantly search and listen for signals.
Also battery life could depend on the widgets you use or apps that you have active.
Example: Beautiful Widgets beautiful home is a constantly running app that also
-on occasion activates the GPS to acquire location
-on occasion downloads update weather data
Example: Facebook Widget
-by default update statuses every 15 minutes, so every 15 minutes its downloading data
so i usually adjust these settings to my personal liking
Now for the battery calibration process and how it works
Decad3nce port of Colins_ph batt tweak allows us to use some setcpu profiles without setcpu.
Setcpu and its widgets were resource monsters crippling our system and drain battery life as well. kiss setcpu goodbye we wont be needing it anymore.
the batt tweak calibration process takes some patience as the entire process could take 1-3 days to complete depending. Also i highly recommend using the latest CFS kernel by Conap as it provides extra battery savings
we will be running colins batt tweak during the calibration process so that both calibrate together, which makes a lot of sense as opposed to doning them separately.
here is the process and DS's custom settings for batt tweak 1 (the first release)
please remember to prepare yourself not to interrupt the process. the draining process may die while you are at work or during an emergency. so be prepared to have little use of your phone.
-flash latest CFS kernel found here
-flash batt tweak attached at the bottom of this post until its updated and fixed....more info in thread here
-turn off phone and let charge for a few hours or more to ensure that it is full
-when ready boot into recovery mode and wipe the batt stats and power off
-unplug phone and power on (charging cable not needed) you may experience weird battery levels or fast draining (this is normal)
-immediately open TERMINAL and activate colins_ batt tweak
with command batt-cfg and go to option 3 and input these settings........
I think this works much better
this schedueler keeps the cpu much lower
here if anyone want to try it out
underclock
ondemand
anticipatory
19200
710400
19200
710400
19200
710400 (ONLY IF YOU KNOW YOU CAN 768000)
90
15
15
15
- close terminal and operate phone normally if you want...i highly suggest leaving it alone as much as possible until it drains completely dead.
-use a cpu monitoring app just to make sure the cpu is idle i have seen mine dip down 80mhz if not then you need to kill active open apps
-let phone naturally drain completely until its dead (could take a full day or two mine was 48hrs with some usage)
-when dead make sure by pressing power rapidly a few times
-while off let phone recharge for as long as possible maybe four hours or more the mor the better
-when ready unplug phone and turn on
-when powered on reactivate batt tweak using terminal batt-cfg, then option 9 to save and your done (once setup all you need is option 9 to save and reactivate)
-wtf DS my phone is on but reads less than 100% battery. this is normal replug while on and let charge to full
- when full the process is now complete and you can use phone as normal
REMEMBER THAT SOME ROMS DO NOT ACTIVATE THE TWEAK AND YOU WILL NEED TO DO SO UNTIL YOUR DEV AS ADD THE SCRIPT TO ACTIVATE ON A REBOOT. SO UNTIL THEN OPTION 9 IN BATT TWEAK WILL DO THIS
use an app like system panel or seepu to look at cpu speeds make sure the cpu isnt running at 100%.
try to close apps if you see this but a reboot usually fixes this.
these settings allow for the cpu to use lower clock speeds when idle. much lower than the stock 245000 settings yes were going to the minimum 19200 with little to no side effects or slow downs, but the benefits are more when in a idle state. But it WILL drain at about same rate when your using it heavily.
make sure the tweak is running by either opening terminal and enter pidof batt.sh you should see the processing id number if its running.
OR for a full read out of stats do batt-diag
and observe the time in state read out at the bottom. if you see values next to the 19200 clock speeds........SUCCESS!
PS if you screen on time is 3 hours and your phone is dead, DONT BLAME THE BATT TWEAK....BLAME YOURSELF !
ENJOY
alright now lets get some real stuff in here....lol
jdog94 said:
alright now lets get some real stuff in here....lol
Click to expand...
Click to collapse
just trying to a make a nice neat place to put all my post on past tweaks for users and to do some advanced stuff in the future stay tuned
DS36 said:
just trying to a make a nice neat place to put all my post on past tweaks for users and to do some advanced stuff in the future stay tuned
Click to expand...
Click to collapse
good, i need this!
Great idea"!"!!
HAI! Hau do i route mai fone? I wantz haxorz warez an wireles heatherin fo free intanetz!
So seriously, is this a fan-club for DS? I'm totally in if it is.
sticktodrum said:
HAI! Hau do i route mai fone? I wantz haxorz warez an wireles heatherin fo free intanetz!
So seriously, is this a fan-club for DS? I'm totally in if it is.
Click to expand...
Click to collapse
LMAO can you please please be my threads personal comedian
Keep this thread development related or Ill move it to General, Is this a support thread or something? Something about tweaks?
Its all about me
Captainkrtek said:
Keep this thread development related or Ill move it to General, Is this a support thread or something? Something about tweaks?
Click to expand...
Click to collapse
this is a thread to help old and new users tweak and mod their phones and other advanced stuff
trying to put all the knowledgeable stuff in to one easy thread and it will be dev related
im just started this thread im not done i have lots to do here
my in box is getting a little crazy
this should benefit all and provides basic dev techniques and instruction
this is the beginning stages
plus should reduce the number of faqs for everyone
less fights
less arguments
and less captainrtek (but thats not a bad thing)
DS36 said:
this is a thread to help old and new users tweak and mod their phones and other advanced stuff
trying to put all the knowledgeable stuff in to one easy thread and it will be dev related
im just started this thread im not done i have lots to do here
my in box is getting a little crazy
this should benefit all and provides basic dev techniques and instruction
this is the beginning stages
plus should reduce the number of faqs for everyone
less fights
less arguments
and less captainrtek (but thats not a bad thing)
Click to expand...
Click to collapse
Haha gotcha, and thanks
Thanks in advance, DS.
roirraW "edor" ehT said:
Thanks in advance, DS.
Click to expand...
Click to collapse
Looking forward to working together with everyone learning along the way.
Will be post new batt tweak setting in the morn keep an eye out
Do not up date to the latest version of batt tweak it doesn't work.
Sent from my FroyoEris using XDA App
Brilliant.
sticktodrum said:
HAI! Hau do i route mai fone? I wantz haxorz warez an wireles heatherin fo free intanetz!
So seriously, is this a fan-club for DS? I'm totally in if it is.
Click to expand...
Click to collapse
Lol I haz cheez burger
Sent from my FroyoEris using XDA App
rick311 said:
good, i need this!
Click to expand...
Click to collapse
hey man are you ready
im going to post in the third POST what i have written down so far
but its NOT complete yet....so take a gander
DS36 said:
hey man are you ready
im going to post in the third POST what i have written down so far
but its NOT complete yet....so take a gander
Click to expand...
Click to collapse
ok, i did all the setting tweaks that you recommend. do i have to input them every time i reboot? i dont see a setting that restores my previous settings.
Hey DS,
Great idea to help newbs like me! So after reading your first two posts I looked where my apps are, and every one of them seems to be in system/app... I checked in data/ and can't see anything in there (unless it's sdcard/data, in which case I have folders for Beautiful Widgets and Titanium). I'm using the EStrongs FE, although I don't think that would make a difference. Also, couldn't find any of the duplicate apps you were talking about either (I only have com.google.android.apps.maps.apk, for example). I'm on xtrROM 4.6 and used Titanium Backup to restore my apps.
I've rooted my phones but haven't rooted my NST yet.
I'm interested in doing it mainly to get access to Dropbox and one of the Dropbox apps that let's you get feeds put onto your NST daily (I want to get my local paper there--which is available). I already have the paper portion working locally.
I have a few concerns:
1. What's the absolute latest/best way to root the NST? I'm on 1.1.
2. Will rooting suddenly drive my battery life down while the NST is sitting idle? I can go a week without touching it. I don't want to have to charge it every time I touch it.
3. Are the latest approaches problematic? I'm seeing threads about people having some pretty serious issues. Should I just wait at this point assuming there's serious thought to a near-bulletproof approach right around the corner?
All roots are pretty stable, there have been some methods that have had issues. TouchNooter for example had a major issue just yesterday because of a space in an Apps name. But it's been resolved and is stable.
Battery Life won't be affected so much depending on your wifi settings, if you keep wifi off you won't notice the difference between root and non-root. If you keep your wifi on though you may find yourself needing to recharge more often if you have your nook doing data updates too often.
Each version has it's advantages and disadvantages:
MinimalNooter - If you're willing to use CWM Minimal Nooter is available and is easily one of the most customizable of all the Nooters with different packages ranging from the most basic of roots "Minimal" to a full root package with Gapps XorZone's Mods etc.
Advantages
Clear Instructions, lots of information, can be a little confusing/overwhelming.
More Customizable with multiple packages
Lowest chance of FS corruption due to CWM use
No One Day Market Wait
No extra Apps to fix Market Search
Disadvantages
More steps to get to root through using CWM (Not just pop it in wait and done)
TouchNooter - TouchNooter was the original Nooter for Nook Simple Touch using the original Methods used on it's sibling the Nook Color. It installs a few mods and the basics to make it as customizable as a person needs you can drop apps in or remove them without having any real technical know how.
Advantages
Customizable with most extra apps in /data/app
Lower chance of FS corruption due to new TouchNooter methods
No extra Apps to fix Market Search
Clear Instructions that go step by step through each requirement
Disadvantages
One Day Wait to get Market Working
I would use TorimuNooter, because theCPU underclocking saves the most battery power.
I'd be very curious to know why Gabrial originally included TorimuNooter but then edited his post to remove mention of it.
[NST]MinimalTouch 1.1beta5 (+Index to manual rooting)
http://forum.xda-developers.com/showthread.php?t=1346748
My favorite so far, easy install as long as you can follow directions.
Market works immediately, lightweight - only includes apps necessary for functionality and has had no problems since installing a few weeks ago.
Still waiting for XorZones NST launcher for my nook to be complete
Agrajag27 said:
I'd be very curious to know why Gabrial originally included TorimuNooter but then edited his post to remove mention of it.
Click to expand...
Click to collapse
After the update to 0.5 in which TorimuNooter is no longer really a derivative of TouchNooter, not even bothering to change bootloader images or disk names or a number of other things unique to TouchNooter, I feel that it no longer deserves to be recognized as it's own "Nooter"
GabrialDestruir said:
After the update to 0.5 in which TorimuNooter is no longer really a derivative of TouchNooter, not even bothering to change bootloader images or disk names or a number of other things unique to TouchNooter, I feel that it no longer deserves to be recognized as it's own "Nooter"
Click to expand...
Click to collapse
He's gonna freak about that...
*hides*
So do I take it that the "simple" act of rooting will drive my battery life down, possibly significantly?
Agrajag27 said:
So do I take it that the "simple" act of rooting will drive my battery life down, possibly significantly?
Click to expand...
Click to collapse
No.
Rooting just makes you gain root access, so you can modify your device.
It wont eat any battery just for rooting, but depends on what you do with your device, it will consume more or less battery.
On idle, except if some app is preventing your device to go to sleep, it should be the same.
If you read a lot of pdfs, play games, use web browsers, etc, the cpu will stay much more time active and there will be many more screen refreshes than when reading books.
Your battery will last less when doing more intensive tasks, the same when reading books, and the same when idle.
Just dont bloat it with trilions of apps you wont use, keep it minimal as more apps running, normally means more problems with battery.
If you wanted to lessen the cpu states, you could try SetCpu or follow this manual tuto http://forum.xda-developers.com/showpost.php?p=20069231&postcount=4 (I preffer this type of tricks, instead of installing extra apps).
Don't forget to never leave the wifi on for long periods of time, as it dosn't let the device go to sleep.
Agrajag27 said:
So do I take it that the "simple" act of rooting will drive my battery life down, possibly significantly?
Click to expand...
Click to collapse
No.
If you have too many applications running the background such as email and twitter and weather updates and etc. Your battery life will be significantly less than if you have just email running. Your battery life is directly affected by what you put on your device and by which settings you use.
My nook is rooted and without underclocking my battery life hasn't changed that much, if I leave wifi off I can go weeks before I ever need to recharge, if I leave Wifi on I can go maybe a few days to a week. Which isn't abnormal or extreme battery difference from root to non-rooted.
It's very much like your android phone, when you rooted it the battery life didn't actually change, if you install new roms, or different kernels you risk a difference between non-root and root. However the only real difference between root and non root on this device is your ability to install apps on the device and do things that require root such as directly modify the filesystem, or use root ADB.
If you don't overload your device with bloat and lots of apps that want to run in the background you won't notice a difference. If you decide to bloat your device up with a bunch of excess apps that like to stick around in the background you risk the chance your battery life will suffer.
Googie2149 said:
He's gonna freak about that...
*hides*
Click to expand...
Click to collapse
I'm a dev, I don't care if he freaks, it's my honest opinion. To me there's a fine line between derivatives and non derivatives, if he can't even bother to change the things that mark the image he used as TouchNooter than to me that is theft and nothing else, regardless of the changes or additions he makes to it.
I had read elsewhere that an app or two that got installed as a by-product of the rooting process was taking up CPU that wasn't there prior.
That was the concern. For me I'd think about adding passive e-mail support, another keyboard, possibly another reading app and would be likely to read more PDF's though now it appears I can get my newspaper (which is the primary goal) in epub format daily.
On WiFi, I haven't touched the default other than setting up access and it's been a good three weeks since I last charged and just re-charged it at 10%. I guess I could do better than that turning that off.
GabrialDestruir said:
I'm a dev, I don't care if he freaks, it's my honest opinion. To me there's a fine line between derivatives and non derivatives, if he can't even bother to change the things that mark the image he used as TouchNooter than to me that is theft and nothing else, regardless of the changes or additions he makes to it.
Click to expand...
Click to collapse
I understand that entirely, but Torimu will still be upset about it. He is kind of going around advertising his as the best nooter, and having it "insulted" (in his mind) will probably set him off. You know what, I should probably just leave this whole thing alone... :/
Agrajag27 said:
I had read elsewhere that an app or two that got installed as a by-product of the rooting process was taking up CPU that wasn't there prior.
That was the concern. For me I'd think about adding passive e-mail support, another keyboard, possibly another reading app and would be likely to read more PDF's though now it appears I can get my newspaper (which is the primary goal) in epub format daily.
On WiFi, I haven't touched the default other than setting up access and it's been a good three weeks since I last charged and just re-charged it at 10%. I guess I could do better than that turning that off.
Click to expand...
Click to collapse
Gapps does get added in with some other apps to make it more usable. Gmail runs in the background but with the right settings it isn't an issue. The launcher I believe could also run in the background with some settings (I believe there's an option in ADW so it doesn't close completely) but I pretty much find battery life between root and non root is pretty much negligible.
I forgot about the disk names...
But I will change that. I'm just trying to improve upon others work.
Thanks for your opinion Gabreil......
I'll try to stop advertising.
Torimu.Joji said:
I forgot about the disk names...
But I will change that. I'm just trying to improve upon others work.
Thanks for your opinion Gabreil......
I'll try to stop advertising.
Click to expand...
Click to collapse
It's more than just disk names there were other changes I made, big changes that would be rather noticeable if you bothered to test your work. Like for example the start up image which was left completely unchanged in both your most recent updates.
@Gabrial and the other nooters
While you're on the subject of images I just want to take the opportunity to emphasize the importance of you guys keeping your images within the size of the original NST boot partition.
Reason is, as said before, people regularly do the mistake of writing your image directly to the NST instead of writing it to the SD card.
Just this week I've had four cases where people have written "garbage" data outside the boundaries of the boot partition, and as you (should) know, the next one is the tiny /rom partition with the really important stuff.
Thank you
-Roger
ros87 said:
@Gabrial and the other nooters
While you're on the subject of images I just want to take the opportunity to emphasize the importance of you guys keeping your images within the size of the original NST boot partition.
Reason is, as said before, people regularly do the mistake of writing your image directly to the NST instead of writing it to the SD card.
Just this week I've had four cases where people have written "garbage" data outside the boundaries of the boot partition, and as you (should) know, the next one is the tiny /rom partition with the really important stuff.
Thank you
-Roger
Click to expand...
Click to collapse
I often keep this in mind. It's even addressed as one of my "Before you Begin" pieces. The problem is there's only so much you can do before it just falls to the user to pay attention and not screw up their device. When "You must have an external microSDCard reader or this will not work. Do NOT use the Nook Simple Touch." is apart of the "Before you Begin" and a user ignores that, then it's unfortunately their fault if or when they screw up their device by not following directions.
I've always limited my images to 128 because it's big enough for people to add what they want or to expand Nooter as needed. I'll actually be switching over to the CWM method which would be safer but you're stuck with the same issues with CWM that you will see with using TouchNooter's current image based method and that is people not following instructions and screwing up their devices.
While limiting images and such to 70MB (I think that's right) would be ideal the issue is the majority of that space is already filled, meaning you're very much limiting what you can do with an "automatic" method.
Mind you I've heard of methods like noogie which is the exact size if I remember for the boot partition completely destroy a device because someone wasn't following the proper directions. So the issue isn't the size of the image but how the user uses them.
GabrialDestruir said:
Mind you I've heard of methods like noogie which is the exact size if I remember for the boot partition completely destroy a device because someone wasn't following the proper directions. So the issue isn't the size of the image but how the user uses them.
Click to expand...
Click to collapse
True, but my experience is, and I get around three to four cases every week, is that they write it to the root device which means that 76MB (or 155648 sectors to be exact) is ok.
Beyond that you go into the next partition and the data there is only a couple of hundred kilobytes.
So you see, just 300KB beyond the size of /boot is enough to completely brick a NST forever :/
Yes, there's a backup zip in p3 (factory) but it's usually fragmented and I have only once succeeded in recovering it..
Let me end with a 2012 version of a famous (mis)quote:
"155648 sectors ought to be enough for anybody"
-Roger
ros87 said:
Let me end with a 2012 version of a famous (mis)quote:
"155648 sectors ought to be enough for anybody"
-Roger
Click to expand...
Click to collapse
I wish that were true, lol, but considering how much information we want to put on the device it's hard. Perhaps if CWM could grab zip files off of the internal media storage you could toss CWM on 155648 sectors then keep all update zips, etc on the internal storage partition
So i just squires an NST and already have a Fire and Sensation for most of my needs, i really only want to use this as a reader, but the restrictions blow. i really only care about fixing this partition silliness. Which is the best way for just getting that space available.
For the sake of completeness (most of you will have noticed this app already): For a change, Samsung have done a fantastic job and released a great app called "Game Tuner". It's simple to use, doesn't even need root, and renders all of the stuff I wrote below obsolete!
What it does is, it renders each game at an individual screen resolution, frame rate, and texture quality (texture quality only working for me since MM upgrade).
All you have to do is install Game Tuner from Google Play (above link), start it, follow the instructions to install GameMode through Galaxy Apps, and you're good to go. Create a custom profile, set default values (e.g. 75% resolution=1080p), activate the profile. Set different resolutions for other games. And if you want to control apps other than games, tap top left menu, and chose "Apps".
I've done the same benchmarks as with the method below, and the results were exactly the same, so it's really working, but without messing up the UI or impairing system apps like the camera.
Hey folks,
I've decided to put together a little wrap-up of the stuff I found regarding the sometimes rather poor 3D performance of the Note 4. This is only for experienced users who are familiar with things as rooting, backups, adb, in general: unbricking their phone if bad things happen. As usual, I don't take any responsibilty if you brick your phone or destroy it in any other way. Just make sure to activate USB debugging, and if anything goes wrong, either follow this guide, or simply reflash your ROM.
Just make sure you make a Nandroid or at least Titanium backup before you try this. Better safe than sorry...
It comes as no surprise that running a cpu at almost 3GHz takes its toll. Demanding games such as Real Racing 3 or XCOM:EW, or emulators such as PPSSPP cause the cpu to heat up rapidly, until it reaches ~80°C, before it gets mercilessly downclocked to cool down. At this point, you start noticing more or less pronounced performance drops. There isn't really much you can do, except using a custom kernel to downclock cpu & gpu, before your phone does.
But apart from that, there is another, even greater performance hog, which is also one of the main reasons for the overheating issue: the QHD resolution of our Note 4's screen. We're talking about a 3.69 megapixel resolution, that's almost twice as much as Full HD (2.07 MP), and exactly four times as much as HD (0.92 MP). Gorgeous and brilliant, beautiful to look at during everyday use, but pushing the Adreno gpu to its limits when it comes to gaming.
So, an ingenious guy called NOMone has created a nifty little tool called "NOMone Resolution Changer", already some time ago. It's available for free at Google Play. It's been widely discussed here on xda and on other forums, but I want to share my experience specifically on the Note 4.
Btw, it seems he only posted here two times, so he's most likely not active anymore, but you should head over and thank him anyway.
Now, if you're thinking "no way, why should I deliberately sacrifice my QHD resolution?", read on nonetheless. Because this tool is extremely easy to use, and if you only switch the resolution before playing a game, and revert afterwards (it's only one click), you won't have to sacrifice any visual quality. The settings stick after a reboot, so make sure to really restore defaults if you want to go back to QHD.
The trick is to use the appropriate resolution and dpi values, so your screen doesn't get mixed up.
The results are impressive, sometimes even staggering. Has anyone ever wondered why PPSSPP doesn't perform better on a Note 4 than it does on a Note 2? Here's the reason. PPSSPP gains so much performance , it's almost unbelievable.
I've also done some benchmark runs to measure the improvements (yeah, I know, benchmarks are bad, but still :angel: ). The improvement is clearly visible and, even more important, reproducable:
GFXBench GL Benchmark 3.1 (Manhattan):
1. 1440p: 449,4 frames, 7.2 fps
2. 1080p: 800,6 frames, 13 fps (+78%)
3. 720p: 1621 frames, 26 fps (+261%)
4. 480p: 2728 frames, 44 fps (+507%)
This is plain awesome. The Note 4 is listed even lower, with 434 frames, in the device list, while the 1080p Galaxy S5 reaches 775 frames.
AnTuTu (gpu score only):
1. 1440p: 16210
2. 1080p: 21253 (+31%)
3. 720p: 22524 (+40%)
4. 480p: 22523 (+40%)
Obviously, by comparing scores 3 and 4, the Note 4 hits the fps limit at HD resolution, so there's no more room for improvement in AnTuTu.
Seascape Benchmark (detail setting: Very High):
1440p: 26.9 fps
1080p: 46.6 fps (+73%)
720p: 53.4 fps (+99%, sometimes hits the frame limit of 59.0 fps)
480p: 59.0 fps (+119%, hits the frame limit constantly).
This is a beautiful OpenGL ES 2.0 test, so no cpu scores interfering with the result. Again the fps limit prevents a higher score, but nonetheless, this is pretty amazing.
Other benefits: if you're using a custom kernel, you can run gpu-intensive games at lower cpu speeds to keep the cpu temperature in check. In my case, XCOM:EW runs smoothly @ 30% (!!) cpu speed. This way, the cpu doesn't heat up to more than 60°C, which means it doesn't get downclocked while playing. If you like, you can also automate the process of setting the cpu speed with the aptly named app "Automate" . Which is fantastic, btw.
Now what about visual quality?
Seriously: it's hard to tell the difference. If you look very closely, you can see the display isn't as sharp in FHD as in QHD. But if you look that closely, you're in constant danger of triggering some random app with the tip of your nose. At normal viewing distance, especially while gaming, it's impossible to tell the difference.
So, are there any drawbacks?
Yes, there are: the UI gets messed up a bit (e.g. bigger status bar, some Samsung apps don't fit on screen anymore), and NOMone Resolution Changer doesn't seem to work with CM12.1. Well, at least for me, and other users reported so as well. I tested it some time ago, while I was on CM12.1, and even thought it was a fake app, which it isn't! Seems that the resolution is somehow hard coded into CM12, and you can only switch dpi. There's probably nothing you can do when you're running CM, except try your luck.
But if you are running a Touchwiz ROM, stock or custom, it should work as intended (Emotion Revolution ROM r10.1 in my case). And you can simply ignore the UI issues, as long as you only switch the resolution for gaming. It's not a real issue then, because the status bar is hidden anyway while the game is running.
If you want to keep your device running at FullHD permanently, it's a bit more complicated: first, you'll need Xposed, so you can use the App Settings module to set Android System and SystemUI to 480 dpi. This'll fix the UI (Not needed. Just reboot)
Some apps like phone, contacts, S-Note scale down to the lower dpi setting, whereas Samsung keyboard and the camera won't (camera works, see post #10 below).
So you'll have to install another keyboard like SwiftKey (if you don't have it already), find a working camera app (3rd party or hacked Note 4 camera), and clear your Google Play data (at least I had to, it wouldn't install any apps after the changes), and you're good to go. There might also be other issues I'm not aware of yet. But apart from the ones I described, everything's working fine so far.
Have fun!
you don't need root to change the dpi and the resolution.
enable usb debugging and adb the following:
adb shell wm density 480
adb shell wm size 1080x1920
adb reboot
if you want to revert back:
adb shell wm size reset
adb shell wm density reset
adb reboot
the changes persist after reboot.
I am using it like that for some time. Everything is much faster. Even the browsing..
the only 2 bugs I noticed is the Samsung keyboard (i switched to swiftkey) and the action memo (c'mon Samsung devs, code properly..)
mitko76 said:
you don't need root to change the dpi and the resolution.
enable usb debugging and adb the following:
adb shell wm density 480
adb shell wm size 1080x1920
adb reboot
if you want to revert back:
adb shell wm size reset
adb shell wm density reset
adb reboot
the changes persist after reboot.
I am using it like that for some time. Everything is much faster. Even the browsing..
the only 2 bugs I noticed is the Samsung keyboard (i switched to swiftkey) and the action memo (c'mon Samsung devs, code properly..)
Click to expand...
Click to collapse
You're right, you don't necessarily need this tool. All it does is simplify the process. And you should really be able to use adb commands to fix your phone when you mess it up. But NOMone's tool comes in very handy when you're away from your pc and need to switch resolutions quickly. In my case, it's when I want to use the camera: the UI is messed up at 1080p and I haven't found a way to fix it yet, except switch back to QHD. Or the other way round: if you want to play a demanding game on the train at lower resolution, but go back to QHD again.
I'm using 1080p resolution permanently now, because I get a smoother UI, a cooler phone, better battery life, and much better performance. I hope they don't give us 5" UHD screens next...
Could you please explain what is wrong with the camera on 1080p 480dpi? I am using these settings and have 0 problems with the camera. Just curious.. If possible please attach a screen shot. Cheers
The UI is messed. I can't see most of the buttons, and can't take a photo, see attached screenshot.
Xelasarg said:
The UI is messed. I can't see most of the buttons, and can't take a photo, see attached screenshot.
Click to expand...
Click to collapse
Using my method and my values, it is absolutely fine for me. Do you restart after changing the resolution and the dpi?
I am on UK BTU 5.1.1
mitko76 said:
Using my method and my values, it is absolutely fine for me. Do you restart after changing the resolution and the dpi?
I am on UK BTU 5.1.1
Click to expand...
Click to collapse
I even wiped /cache and /dalvik. Strange. My device is a Snapdragon N910F. Is yours an Exynos N910C perhaps? If not, would you mind sending me your camera apk for testing?
Thanks!
Xelasarg said:
I even wiped /cache and /dalvik. Strange. My device is a Snapdragon N910F. Is yours an Exynos N910C perhaps? If not, would you mind sending me your camera apk for testing?
Thanks!
Click to expand...
Click to collapse
very strange indeed. My device is n910f as well. Not rooted and fully stock. I used the Debloater app to disable all unused apps (works via adb) and the method descried in my other post to change the resolution and dpi. The camera is working absolutely fine i.e. no visual changes or glitches. As I am not rooted I am not sure if I can give you the camera apk. It is basically the same apk as in the stock 5.1.1 BTU rom. Try my method on the stock rom with my values and I am sure it will work.
Cool
mitko76 said:
very strange indeed. My device is n910f as well. Not rooted and fully stock. I used the Debloater app to disable all unused apps (works via adb) and the method descried in my other post to change the resolution and dpi. The camera is working absolutely fine i.e. no visual changes or glitches. As I am not rooted I am not sure if I can give you the camera apk. It is basically the same apk as in the stock 5.1.1 BTU rom. Try my method on the stock rom with my values and I am sure it will work.
Click to expand...
Click to collapse
Well, I went ahead and downloaded _alexndr's COI3 stock debloated rom base (Deodexed), extracted SamsungCamera3.apk, replaced the one in my /system/app dir, set permissions, rebooted, and everything's working fine now. :good:
No idea what the Emotroid guys did to the camera app.
I've attached the apk to this post in case anyone else is having this issue.
Man, I've been playing XCOM:EW at 720p, and my phone didn't get warmer than 59°C, even after 2+ hours. And the performance boost is just so incredible... Turns out I don't even mind the 720p resolution in 3D games, it didn't bother me at all.
Just a warning:
I just managed to render my phone useless with this. After changing resolution and DPI, the phone did a soft reboot (as it should), startet booting, then, after the initialisation of systemUI reboots. Has been Bootlooping the past hour. ADB doesn't work, as reboot it's unauthorised and boot loop doesn't allow for any authorisation. Tried resetting via build.prop and userinit.sh. Even Direct Script Injection into init.rc didn't work.
Cache wipe -> no chance
System wipe and reflash -> Nope
In the End i ended up factory resetting and reflashing complete rom. This did work. Not to rant or anything, just a little story for those that are not capable to troubleshoot problems: This might screw your Installation!
domsch1988 said:
Just a warning:
I just managed to render my phone useless with this. After changing resolution and DPI, the phone did a soft reboot (as it should), startet booting, then, after the initialisation of systemUI reboots. Has been Bootlooping the past hour. ADB doesn't work, as reboot it's unauthorised and boot loop doesn't allow for any authorisation. Tried resetting via build.prop and userinit.sh. Even Direct Script Injection into init.rc didn't work.
Cache wipe -> no chance
System wipe and reflash -> Nope
In the End i ended up factory resetting and reflashing complete rom. This did work. Not to rant or anything, just a little story for those that are not capable to troubleshoot problems: This might screw your Installation!
Click to expand...
Click to collapse
Hence the warning at the beginning of the thread.
But seriously: which method did you use? The NOMone app or the adb commands? Because only the adb command needs a reboot to take effect, NOMone does not reboot: it changes the resolution on the fly, then waits 10 seconds for confirmation and switches back to default resolution otherwise.
It's impossible to tell what went wrong in your case, might have been anything from a bad adb command to a malfunction of the app or your rom. I guess if you enter bad values, both methods might break your SystemUI. I managed to do so by using Automate to activate the shell commands on app launch (no bootloop, though, only permanent FC of SystemUI), but I was able to fix it with adb easily.
It's a shame it didn't work for you, most people who are using this method are very happy with it.
THANKS !
dooes this improve battery as well /
gonna try this
Boody hegan said:
THANKS !
dooes this improve battery as well
Click to expand...
Click to collapse
Yes, it does, at least a bit. The screen does still burn a lot of juice because it's so big and bright, but the cpu stays much cooler. Less heat=less power consumption.
Thanks alot , i'm on simplrom v5c and googy max kernel v2
can this still work ..
Xelasarg said:
Hence the warning at the beginning of the thread.
But seriously: which method did you use? The NOMone app or the adb commands? Because only the adb command needs a reboot to take effect, NOMone does not reboot: it changes the resolution on the fly, then waits 10 seconds for confirmation and switches back to default resolution otherwise.
It's impossible to tell what went wrong in your case, might have been anything from a bad adb command to a malfunction of the app or your rom. I guess if you enter bad values, both methods might break your SystemUI. I managed to do so by using Automate to activate the shell commands on app launch (no bootloop, though, only permanent FC of SystemUI), but I was able to fix it with adb easily.
It's a shame it didn't work for you, most people who are using this method are very happy with it.
Click to expand...
Click to collapse
It was completely my fault. I knew what i was getting into, so no problem. It's just that, the "mistakes" i did could easily be done by accident by some less experienced users.
First off, i'm on CM12. NOMones Sollution doesn't seem to work there. CM does a "Hot Reboot" to reload the system UI. No matter what you set in NOMones app, the resolution doesn't change. DPI does though. This seems to be a CM related issue. Maybe they hardcode the resolution at build time...
After that i tried another app, which had the Orientation labeled backwards. So it set 1920x1080 landscape instead of portrait. After that the Phone Bootlooped the System UI. It would always boot up to the PIN Enter Screen and then reboot.
As said, no big Problem. I knew what to do and was able to bring my phone back to working state. Just make sure that you are 100% sure about the numbers you put into such apps and keep in mind that even with such "small" changes you should always have a up to date Backup of everything.
Boody hegan said:
Thanks alot , i'm on simplrom v5c and googy max kernel v2
can this still work ..
Click to expand...
Click to collapse
It should, unless SimplROM is CM12-based. NOMone Resolution Changer, as well as similar apps and the adb method, aren't limited to specific devices. In theory, they may all work on all Android phones. You'll have to try it out yourself, just make a backup before you do so!
domsch1988 said:
It was completely my fault. I knew what i was getting into, so no problem. It's just that, the "mistakes" i did could easily be done by accident by some less experienced users.
First off, i'm on CM12. NOMones Sollution doesn't seem to work there. CM does a "Hot Reboot" to reload the system UI. No matter what you set in NOMones app, the resolution doesn't change. DPI does though. This seems to be a CM related issue. Maybe they hardcode the resolution at build time...
After that i tried another app, which had the Orientation labeled backwards. So it set 1920x1080 landscape instead of portrait. After that the Phone Bootlooped the System UI. It would always boot up to the PIN Enter Screen and then reboot.
As said, no big Problem. I knew what to do and was able to bring my phone back to working state. Just make sure that you are 100% sure about the numbers you put into such apps and keep in mind that even with such "small" changes you should always have a up to date Backup of everything.
Click to expand...
Click to collapse
Right, thanks for clarification. I don't remember the hot reboot in CM12, but I know the resolution switch didn't work when I tried it on my Note 2 some time ago. Funny that for once Touchwiz is more customizable than CM.
If you're still interested, but hate the Samsung colour scheme (like me), you can try out Emotion Revolution ROM r10.1. It's based on the latest COI3 TW firmware, but they themed the notifcation/status bar and toggles to somewhat more like stock Android, see attached screenshot. Looks pretty sleek, performance is easily on par with CM12, and the Emotion kernel has tons of great tweaking options. Or you can go for their Port Note 5 r2.1 ROM, also based on COI3, which should offer full Theme Store support. That's the one I'll flash next. :good:
Xelasarg said:
Right, thanks for clarification. I don't remember the hot reboot in CM12, but I know the resolution switch didn't work when I tried it on my Note 2 some time ago. Funny that for once Touchwiz is more customizable than CM.
If you're still interested, but hate the Samsung colour scheme (like me), you can try out Emotion Revolution ROM r10.1. It's based on the latest COI3 TW firmware, but they themed the notifcation/status bar and toggles to somewhat more like stock Android, see attached screenshot. Looks pretty sleek, performance is easily on par with CM12, and the Emotion kernel has tons of great tweaking options. Or you can go for their Port Note 5 r2.1 ROM, also based on COI3, which should offer full Theme Store support. That's the one I'll flash next. :good:
Click to expand...
Click to collapse
Nah, TW is no option... I choose CM because of the straight forward no bllsht Apps approach. Plus Nightly builds via OTA... In no possible way am i going back to TW
AnTuTu Benchmark @ 1080p, performance governor, stock cpu frequency (2.65 GHz): :highfive:
(OK, cpu was also very cool when benchmark started, 28°C).
So the dev section here has been active recently with some high quality work, and I am looking to add to the fun
**SEE POST 2 FOR CHANGE LOG**
***VERY IMPORTANT IF YOU ARE GOING TO USE THIS MOD, you need to navigate to the /system/etc folder on your device, and rename the file "init.lge.zramswap.sh" to "init.lge.zramswap.sh.bak" so it does not run at boot.
This is a step by step instruction on how to replace the /system/etc/init.qcom.post_boot.sh file for the LG V10. Be it known, however, that this instruction (and file) can be used with any device running the Snapdragon 808 SoC combo.
What does this do?
Simple. It turns your device into an even more efficient powerhouse. Here are is a list of everything done:
-Interactive Governor tuning for performance and better battery life, a quick description of what I did...
-low load, quick response, low frequency
-high load, quick response, higher frequency
-modified input boost settings for Interactive
-Adjusted GPU target load values
-Switched IO scheduler to noop, and tuned accordingly
-Adjusted minfree values (RAM management, it is a little more multi-tasking friendly)
-Adjusted VM parameters - swappiness, dirty ratios, cache pressure, centisec values, etc (again to complement multi-tasking... your data will hang out a little bit more before being written to disk, but house cleaning won't happen all at once, so there is still good performance and your system won't bog down while it is flushing the toilet)
-DISABLED zRAM!!! - I have no idea why a device with 4 GB of RAM has zRAM enabled. This is purely a waste of CPU cycles and other system resources. You want physical memory, not compressed memory.
-Changed congestion algorithm to cubic (better network performance... assuming the network bandwidth is already there
-Cleaned up the shell file and fixed some errors.
-More to come!
How to do this, we'll just get right to it.
Download this app https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Download this file https://drive.google.com/open?id=0BzM9W6qUvx-gcm1SVDhsTDVWZ3M
And while you are here, check this out, decide which one you want.
http://forum.xda-developers.com/showpost.php?p=66792862&postcount=109
Very important you put the file on the root of your INTERNAL SDCARD!!!
Do not forget to do this.
After you do that, open terminal emulator, and type the following commands in the order they are presented (I would highly recommend just copying them from this post and switching back and forth between your browser and the terminal app):
Code:
su
Code:
cd /
Code:
mount -o remount,rw /system
Code:
cd /system/etc
Code:
rm init.qcom.post_boot.sh
Code:
cd /sdcard
Code:
mv init.qcom.post_boot.sh /system/etc
Code:
chmod 0644 /system/etc/init.qcom.post_boot.sh
Double check the file has been replaced with a file explorer of some sort, double check permissions, then reboot. Good to go.
Some of this stuff explained http://forum.xda-developers.com/tmo...nux-virtual-machine-explained-part-1-t3386956
CHANGE LOG***
May 1, 2017
-Pretty major overhaul of the file. I've done some stuff on the Axon 7 that has been pretty effective. Rolling those changes out to other devices. https://drive.google.com/open?id=0BzM9W6qUvx-gcm1SVDhsTDVWZ3M
May 31, 2016
-Replaced corrupted files. Good to go now!
Dangerously version (fixed) https://drive.google.com/open?id=0BzM9W6qUvx-gVHBGWEp3QkpURVE md5sum: a632c866e22114c0e18fa335f005293e
May 25, 2016
Quite a bit of changes here...
-VM completely readjusted. vfs_cache_pressure set back to default 100 to fairly reclaim memory pages that have been allocated to block specific data about file location, etc.. there are tons of write ups on this stuff if you guys want to investigate more into what this setting does, how it works. It's basically a fairness multiplier centered around a value 100. + or - that value increases or decreases the probability that the kernel will reclaim those certain memory pages relative to swap.
-Swappiness reduced drastically... from 80 to 40 (default is 60 depending on which kernel you are running)
-dirty ratio and dirty background ratios reduced drastically to avoid massive amounts of data being flushed and causing system hangups when that ceiling is hit. (lol this happened to me... system ran out of mem... *shrugs* I go hard bros)
-Increased the probably of the system to reclaim memory pages, and made a pretty big adjustment to writeback_centisecs and expire_centisecs
-Changed functional aspects of the interactive governor again - it is perfect. Nominal user experience. Same with touch input_boost. This system definitely has a sweet spot, and I'm pretty sure we've found it now.
-Decided to ditch the laptop mode idea and not mess with the RAM console outputs, the functional loss wasn't returning enough reward. So, here we are.
-Adjusted minfree once more, to
-It is important to note that the system will, admittedly, not multitask quite as aggressively. I had to do this, however, for myself mostly. As I was achieving OOM conditions and hitting the high ceilings set in other parameters like dirty_ratio and when it hits that wall, man it hits hard. Complete lock up for a good 40 seconds while everything is getting dumped from memory. I need a phone with more RAM lol. Didn't think that would ever happen on my mobile set up with 4 GB of it but here we are. I suppose I could re-enable zRAM for myself? But that would hardly help as compression ratios aren't going to yield me an extra gigabyte. Ok now I'm rambling. DOWNLOAD THE FILE!
Very interesting, I'll be trying this in the next hour or so! Thanks for posting.
Edit: Made changes as per the instructions and rebooted successfully. No issues so far, we'll see! Thanks again.
Nice...
Desde V10 (LG-H901)
For all variants? Is it compatible with H961N LP?
Looks promising and wanted to try.
How do I know it worked? I followed the steps
Sent from my LG-H901 using XDA-Developers mobile app
roosxter said:
How do I know it worked? I followed the steps
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
After every line he explains what it does, you would recognize the changes through your usage or maybe non-usage (as far as battery life and RAM management goes)
When I try to move the file it's giving me this error. I have BusyBox and pretty sure it's on read/write access. What am I doing wrong -_-
1|[email protected]:/ # mv init.qcom.post_boot.sh /system/etc
mv: init.qcom.post_boot.sh: remove: Read-only file system
1|[email protected]:/ #
iamtheon said:
When I try to move the file it's giving me this error. I have BusyBox and pretty sure it's on read/write access. What am I doing wrong -_-
1|[email protected]:/ # mv init.qcom.post_boot.sh /system/etc
mv: init.qcom.post_boot.sh: remove: Read-only file system
1|[email protected]:/ #
Click to expand...
Click to collapse
i got problem with the !!!!!!cd /sdcard , writing
i tried cd /storage/emulated/0
and worked for me
11868 said:
i got problem with the !!!!!!cd /sdcard , writing
i tried cd /storage/emulated/0
and worked for me
Click to expand...
Click to collapse
I tried that, but doesn't hurt trying again.
Edit: It worked. I did the same thing lol oh well thanks @11868
Can this be done with the root explorer instead of terminal emulator?
So this can be used on the G4? And does this overwrite settings within the kernel? If I push this file and I don't like the results can I flash a kernel to get rid of the changes?
iamtheon said:
When I try to move the file it's giving me this error. I have BusyBox and pretty sure it's on read/write access. What am I doing wrong -_-
1|[email protected]:/ # mv init.qcom.post_boot.sh /system/etc
mv: init.qcom.post_boot.sh: remove: Read-only file system
1|[email protected]:/ #
Click to expand...
Click to collapse
Your system wasn't mounted as rw when you executed the command
agrenwa said:
Can this be done with the root explorer instead of terminal emulator?
Click to expand...
Click to collapse
It can, yes, I just prefer the old school way. You can manually drop the file in the /etc folder after deleting the previous one. Just need to make sure the permissions are set appropriately.
klbjr said:
So this can be used on the G4? And does this overwrite settings within the kernel? If I push this file and I don't like the results can I flash a kernel to get rid of the changes?
Click to expand...
Click to collapse
Yes, this can be used on the G4 and any other device using the Snapdragon 808. Overwrite settings within the kernel? No, I wouldn't say that. sysfs is more of a userspace / virtual file system that allows you to interact with the hardware... but the parameters we are working with here are completely writable, not permanent, and more important, will reapply AFTER boot. So, no, flashing a kernel will not revert the changes. If you want to go back, you'll need the original file to replace mine with.
Hope this answers your questions.
Since the file is hosted on Dropbox, anyone who has a dropbox account please choose the login option, and transfer the file to your dropbox before downloading it from your own storage to avoid OP's dropbox being blocked for too many downloads in a row.
Good Job OP, nice to see Junior Members doing something great in the dev section
So I did it last night, and so far battery life seems to be much worse than before when nothing has changed but these tweaks. Any idea why? Battery stats is the same for me as usual with the exception of Android System being at 6% and Android OS at 6% use each.
So far so good, not sure what battery usage will be like. I had terrible lag in a game called Underworld Empire and that has disappeared! How badly was the kernel/system coded before?!
Question , how come your file is smaller than the original? Was there a lot of excess code that was useless?
Sent from my debloated rooted LG V10 using Tapatalk
rirozizo said:
Since the file is hosted on Dropbox, anyone who has a dropbox account please choose the login option, and transfer the file to your dropbox before downloading it from your own storage to avoid OP's dropbox being blocked for too many downloads in a row.
Good Job OP, nice to see Junior Members doing something great in the dev section
Click to expand...
Click to collapse
I'll try to upload the file elsewhere, didn't consider that. However, it is a very small file and dropbox might not notice/care. Good observation.
danstheman7 said:
So I did it last night, and so far battery life seems to be much worse than before when nothing has changed but these tweaks. Any idea why? Battery stats is the same for me as usual with the exception of Android System being at 6% and Android OS at 6% use each.
Click to expand...
Click to collapse
Coincidence maybe? Keep monitoring, report back.
Also, bear in mind: rebooting your system causes a little more activity within the OS the first day or so (particularly google services) and it does have an effect on battery drain.
amoot329 said:
So far so good, not sure what battery usage will be like. I had terrible lag in a game called Underworld Empire and that has disappeared! How badly was the kernel/system coded before?!
Question , how come your file is smaller than the original? Was there a lot of excess code that was useless?
Sent from my debloated rooted LG V10 using Tapatalk
Click to expand...
Click to collapse
Yes, it is smaller because I removed everything that was not relevant to the msm8992 SoC. Qualcomm uses common files for just about everything and anything they can - saves them time, hassle and consolidates work somewhat.
Most of the content removed from the stock file is for other platforms not relevant for us.
warBeard_actual said:
I'll try to upload the file elsewhere, didn't consider that. However, it is a very small file and dropbox might not notice/care. Good observation.
Click to expand...
Click to collapse
I recommend Google Drive or Box
@warBeard_actual
Great job buddy on this.... @freeza mad af!
To everyone else I've been using this for a while and am happy to report my buddy warBeard_actual has been killing it!
bencze, proof or it didn't happen