Related
Okay, so here's the deal:
- I've done some thread surfing.
- Read some tutorials.
- Compiled a list of my ideas, thoughts, comments, etc.
- Finally; have common knowledge of some "lingo."
Now, having stated all that; I'm trying to figure out HOW TO CREATE the "userinit.sh" file and insert it into my SD card. I'm trying to do this based on what I've been discussing in my previous thread regarding Compcache w/ back_swap vs. Linux-swap comparisons.
The issue here being; I flash new ROM builds often, whether it's HERO or Cyanogen, Enomther, etc. I'm always doing a WIPE, because I don't mind. I have MyBackupPro...it's never an issue to restore my applications in APK form using that method. Otherwise, sure if I am completely satisfied with the way a particular ROM is operating on either my MyTouch or G1, then I'll even Nandroid it, then back it up to my PC.
Keeping all that in mind, does anyone suggest SwitchROM? I hear that is a pretty convenient thing to have when you're like me...frequently flashing a new build or ROM port. Typically, I only WIPE when necessary, so it's not always every time. I'm just looking for a way to save time between switches and create that file to be able to ALWAYS set my Compcache and Linux-swap or if I wanted to enable back_swapping, etc.
I could really use a little bit of help in this department, I would greatly appreciate it. Despite this being a lengthy read, it's not too complicated if you know what to look for in this!
THANKS GUYS.
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.
I have a relatively new Aria that I have been considering rooting. Several reasons.
1. Not impressed with the onboard memory and would like to delete bloatware such as Peep, AT&T Maps/Navigator/Hot Spots, Footprints, Friend Stream, IM, Latitude, and a few others. A few of those apps keep showing up in my ATK list, so I'd like to just get rid of them, as I have no intent to use them...why let them wreck my RAM?
2. Speed. I've read enough forum posts to believe that my device will run selected apps faster. Make it so.
3. Use MicroSD card for apps. Hate to be limited to the internal capacity. I expect to partition the new SD card, 1GB dedicated to apps. New card likely to be 8GB.
Here are the questions...
1. I'll be getting a new SD card before the rooting begins. How important is the whole Class 2/4/6 thing. Is Class 4 good enough?
2. If I simply swap out the SD card with a new one before the root, what would I lose besides the photos, movies, music that I have manually transferred to the existing SD card?
3. How do I go about backing up the phone for restoration if the rooting thing doesn't work out?
4. What apps/functionality will I find in the phone after the rooting?
5. Is there a list of apps/files that should not be deleted after the rooting?
6. What is all this "flasing ROM" talk about? How do I chose what I should be flashing? What are the differences and does my device model matter in this decision?
I saw your post in the android forums also and will try to help you out. I can't help you much with your questions about just rooting it, as I switched to a CM6 ROM right after I rooted mine. I am also new the the Aria/hacking world and have only had my Aria for 4-5 days. With that said, I'll help with what I can. If anyone sees my n00b mistakes, please correct me.
1. For an Aria a class 4 MicroSD will be plenty. From what I've read, the classes only relate to write speed and not read speed. Class 4 writes at 4MB/s Class 6 at 6MB/s. I believe this means you would just have to wait a little longer for the files to write to the card. Also, read speed is always faster than write speed. I've also read that the speed rating is not universal. Some companies list their Class rating as their read speed instead of write speed. I've read that Kingston is one of the ones that actually list it as write speed. With this knowledge, I decided to buy a 8gb class 4 MicroSD from Kingston.
2. Before you root, I would format the new MicroSD card and move everything from the old one onto the new one.
I'm getting tired... it's nearly 2am and I can't answer your last questions without researching into all of it. I'll quickly type up what I can answer though.
3. When I rooted my phone, I was walked through using the Ubuntu LiveCD in the IRC. I think I made a backup using Clockwork Recovery, but I'm not totally sure if this program comes on the phone or if I put it there. I've read about unrooting some phone, but know little about it. I do suggest using the Ubuntu LiveCD method for rooting though. It definitely was simple. I also suggest going into the IRC if you are unsure of anything in the rooting process. They are really helpful there even though they don't have to be. Here's a link to the Ubuntu LiveCD root method. http://forum.xda-developers.com/showthread.php?t=741824
4. Like I said, I switched to the CM6 ROM right after rooting so I am not familiar with a stock Aria that's just been rooted. I am pretty sure that it doesn't install any apps and just gives you superuser access to modify the programming.
5. Don't uninstall anything that you aren't sure of unless you make a nandroid backup in Clockwork first. I don't believe it's that simple to just go in there and delete important files anyway. I know that on CM6 I had to access the adb to delete some things. I won't get further into that.
6. A ROM is sorta an emulator. Think how people play Nintendo games on their computers. The ROM emulates a Nintendo system on your computer, so a ROM for your phone emulates another operating system on your phone. (in this case Android 2.2 would being emulated on your phone) You don't have to install a new ROM after you root your phone. You can if you want, but you don't have to. As far as what version to install... I do not know the exact differences in each ROM. I am running CM6 Liberty A012 and don't have problems with it. The different builds of CM6 just fix bugs, I believe. I don't think they are 'theme specific', for lack of a better term, meaning that one isn't better than the other for gps use or whatever. Finally, as long as you have an HTC Aria, your device will work for any mod listed in this Aria forum.
Hopefully I didn't confuse you more and hopefully I didn't give the vets of this forum more work to fix my mistakes. I also hope that what I wrote is at least a little better than letting it go unanswered, as I assume you are as impatient for information as I am.
Anthony1s, your post is spot on except for a bit of confusion on what the term "ROM" really means. You basically have the idea right except that it really has nothing to do with emulation. You aren't emulating an operating system on your phone; you are running it natively!
The "ROM" (in terms of how it applies to an Android phone) is basically the main operating system and a collection of apps necessary for the phone to function. When you "flash" a ROM, you are replacing what is currently on the phone with a new version of the operating system. That's all you really need to know as far as Android ROMs are concerned.
For the Aria, there aren't a ton of options yet on which ROM to use. The Liberated ROMs by attn1 are created by taking the default ROM that comes with the phone and making minor adjustments -- namely, deleting a few built-in apps that most people don't want and removing boot up sounds. If you use this ROM, your phone will appear to function virtually unchanged from the way it comes out of the box. Everything will look the same, it will still have Sense UI on Android 2.1 (Eclair), etc. If the only thing you want is to remove some of the "bloatware" apps, I suggest using one of the Liberated ROMs instead of trying to delete the apps manually. It's a lot simpler this way.
There's also the CM6 Froyo ROM. You can read the thread on it to see all the differences, but it uses Android 2.2 (Froyo) with the default Android UI (not Sense UI). Also, if you install this, you have to do a complete reset on the phone to clear all settings/etc., which is not necessary with Liberated. The CM6 ROM is still in an early development stage which means there are probably some bugs that you will encounter although it may not be anything too significant, whereas the Liberated ROM seems to have almost everything working correctly. The main advantage of this build is the fact that it uses Froyo which has some speed improvements for apps among other new features.
Hopefully that answers all your questions.
Thanks Drumist. I got a question that I've had on my mind for two days. I've read that the Nexus One gets more MFLOPS because froyo 2.2 uses a JIT compiler. Does the CM6 ROM use a JIT compiler or is that something we have to wait for in the official release? I don't mean to hijack, but your knowledge reminded me of my question.
Yes, the CM6 ROM has the JIT compiler. It's one of the reasons the benchmarks for the Aria on CM6 are almost double that of the stock rom. You can actually turn it off as well if you hit Menu > Cyanogen Mod Settings > Performance Settings.
Is it possible? Can it be done without having to learn how to install and use ADB? And is it true that it lengthens battery life for the nook??? Thanks in advance!
les02jen17 said:
Is it possible? Can it be done without having to learn how to install and use ADB? And is it true that it lengthens battery life for the nook??? Thanks in advance!
Click to expand...
Click to collapse
Uninstall with titanium telephony.apk and phone.apk, in that order. You will get FC and just reboot then and you will be okay. Does it save battery life? That is up to speculation and probably not. Root explored can be used also to do it. Just delete these two files.
Airplane Mode WiFi Tool - https://market.android.com/details?id=net.geekherd.airplanemode&feature=search_result
life64x said:
Uninstall with titanium telephony.apk and phone.apk, in that order. You will get FC and just reboot then and you will be okay. Does it save battery life? That is up to speculation and probably not. Root explored can be used also to do it. Just delete these two files.
Click to expand...
Click to collapse
This is the correct answer.
I can't believe no one is being the voice of reason here.
Don't bother! It doesn't do anything for you.
http://forum.xda-developers.com/showthread.php?t=899861&highlight=phone.apk
It makes no difference, placebo at most.
photoassign said:
This is the correct answer.
Click to expand...
Click to collapse
Many times in life there is more than one correct answer. This is one of those times. Please keep that in mind the next time you choose to provide input.
it does not do anything but to free up some internal memory and give you more to run other apps..removing non needed crap that runs does do something....Drm apk..cmstats...setup...and many more items that are loaded that are not needed gives a healthy dose of memory back and general CPU efficiency
Jiggity Janx said:
Many times in life there is more than one correct answer. This is one of those times. Please keep that in mind the next time you choose to provide input.
Click to expand...
Click to collapse
The correct answer for one person may not be correct for another...you were rather harsh on him...let me get this straight...I gotta turn on airplane mode every time I start my nook and turn it off versus just turning it on and playing with it? Does not seem very practical now....imh..but then I dont disagree with the idea...I mean why load a program when you don't really need it?
life64x said:
The correct answer for one person may not be correct for another...you were rather harsh on him...let me get this straight...I gotta turn on airplane mode every time I start my nook and turn it off versus just turning it on and playing with it? Does not seem very practical now....imh..but then I dont disagree with the idea...I mean why load a program when you don't really need it?
Click to expand...
Click to collapse
The app I posted it is something that can be turned on once and will set airplane mode for cell while allowing wifi and bluetooth to function as normal however you want them set, even on a reboot.
It has been proven that many times removing cell (or other main) features can affect the ability to use other applications. My solution was clean, simple, and would affect nothing negatively. BTW, I was using it to avoid the wifi dropping issues that some have seen periodically since CM was first put on the NC. So in my case, it has been providing more than one useful capability.
I feel that people should open up their mind and follow up on other ideas before narrowing their and others minds to only one solution....
photoassign said:
This is the correct answer.
Click to expand...
Click to collapse
The correct answer would be to learn ADB, install the drives and do it manually.
life64x said:
it does not do anything but to free up some internal memory and give you more to run other apps..removing non needed crap that runs does do something....Drm apk..cmstats...setup...and many more items that are loaded that are not needed gives a healthy dose of memory back and general CPU efficiency
Click to expand...
Click to collapse
I'd just like to ask folks not to remove CMStats. Its obviously your prerogative but it helps CM developers track usage. This isn't just for bragging rights. These numbers help us in talks with OEMs to quantify the importance of things like open bootloaders and such. We are starting to see OEMs cooperate with CM and I think tracking usage has helped.
CMStats is not invasive and doesn't hog memory or CPU cycles. It is open source so you can feel free to verify my claims.
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.