Related
I have so far only deleted Rosie.apk and all of the HTC widgets.
I do not like the AOSP look of say... DarchDroid, I like the HTC touches here and there, but without Sense UI.
I'm getting Force Closes now. I can't find the apk associated with the FC'es.
HTC Widget Download Manager (process com.htc.RosieUtility)
poor_red_neck said:
process com.htc.RosieUtility
Click to expand...
Click to collapse
im not sure, but didnt you just answer your own question? im probably wrong, but i think thats it. use root explorer and go on a deleting spree...
I wish it were that easy! lol
I searched all the directories for that file (com.htc.rosieutility) and its nowhere to be found.
I actually searched for *rosie* and all it came up with was:
/sdcard/rosie_scroll
/sdcard/download/Rosie_Icons.zip
Jesus ive searched the phone high and low. I am so ****ing lost. I dont know wtf is going on here.
was your search global? it seems you only searched your sd card...
why not just leave rosie and use helix? seems to me itd be the most stable.
The rom without rosie is very stable.. The only issue you will have is when you boot up, youll have 1 force close. After that the only time it comes up is if you are downloading something from the market. Which it doesnt even always come up.
For the most part the force close doesnt even mean much. I just got used to it being there. I never cared to look into it. But i will now.
Edit: also comes up when uninstalling something. but i dont do that much
Have you tried deleting
HtcAddProgramWidget.apk
hey fyi ic3 is completely aosp, and has fixed the utility issue. check his thread out, ppl seem satisfied.
Im pretty sure i figured it out
delete these
HtcAddProgramWidget.apk <-- If you havent already
com.android.launcher2.apk <-- I think this is what did it
I read the ice rom thread and all he did was use an older version of Launcher, so I just deleted it and rebooted without getting a force close (first time its worked)
I think that did it!
Sweet!
Yeah, I was getting the one FC at boot, and sometimes in the market, but I was also getting it while in the browser, sometimes in People, other times just at random.
I am using Helix.
So far so good.
Thank you!!!
mountaindont said:
hey fyi ic3 is completely aosp, and has fixed the utility issue. check his thread out, ppl seem satisfied.
Click to expand...
Click to collapse
I tried ic3....
I'm just not a fan of completely AOSP. I like the touch of HTC apps here and there.
I'm slowly getting FreshToast exactly how I want it.
Its super fast, and getting more and more stable even with JIT.
The only other thing I'm trying to narrow down is this memory leak type issue.
Sometimes with NO active running services or apps, the available RAM will drop as low as 55MB, then withing a few minutes I'll check it and it'll go back up to 70-80MB. Doesn't seem to affect performance too much, and I'm COMPLETELY taking a stab in the dark here but maybe has something to do with JIT?
I dunno. I'm going to try and disable JIT and see if the available RAM stays in the 60-70 range.
I just removed the HTC Mms.apk with the AOSP Mms.apk to try and cut back on keyboard lag.
I tried going with the AOSP/standard keyboard... I think ive just been typing on the HTC_IME keyboard for way too long that my muscle memory has been trained to it. I keep screwing up with the vanialla keyboard. Also the spell correct doesn't seem to work as well as it does the HTC keyboard. I have no vibration or sound, as well as no key preview to try and cut back on lag.
It seems that the actual spell correction is what is lagging the keyboard down so bad. If I turn off all spell correct/auto complete it seems to be much snappier.
poor_red_neck said:
I tried ic3....
I'm just not a fan of completely AOSP. I like the touch of HTC apps here and there.
I'm slowly getting FreshToast exactly how I want it.
Its super fast, and getting more and more stable even with JIT.
The only other thing I'm trying to narrow down is this memory leak type issue.
Sometimes with NO active running services or apps, the available RAM will drop as low as 55MB, then withing a few minutes I'll check it and it'll go back up to 70-80MB. Doesn't seem to affect performance too much, and I'm COMPLETELY taking a stab in the dark here but maybe has something to do with JIT?
I dunno. I'm going to try and disable JIT and see if the available RAM stays in the 60-70 range.
I just removed the HTC Mms.apk with the AOSP Mms.apk to try and cut back on keyboard lag.
I tried going with the AOSP/standard keyboard... I think ive just been typing on the HTC_IME keyboard for way too long that my muscle memory has been trained to it. I keep screwing up with the vanialla keyboard. Also the spell correct doesn't seem to work as well as it does the HTC keyboard. I have no vibration or sound, as well as no key preview to try and cut back on lag.
It seems that the actual spell correction is what is lagging the keyboard down so bad. If I turn off all spell correct/auto complete it seems to be much snappier.
Click to expand...
Click to collapse
it sounds like compcache is working
So is the memory increase a result of compcache compressing the data to the ramz swap space? Or the opposite? Ive been reading on google code about compcache and of course, I cant wrap my redneck head around it.
I seem to def. like this better than autokiller. ROMs with autokiller seem to kill active running apps too much, especially with the browser if there were a few flash ads on the site. It would just randomly close.
The only thing I'm doing now is going through the com.htc.resources.apk and changing the green to blue. I'm hoping its easy enough of just editing the pngs to blue. Im sure though, somewhere Im going to have to edit some xml files somewhere that have a color hex associated with it. Im just not a fan of green, and am getting sick of it hah. I like blue
is there any way you can compile a signed update that i can flash, that is exactly what you have, Fresh Toast 1.1 with no Sense and JIT enabled..?
I'd be more than happy to, if I knew how to!
I assume it would just be an update script, but i've never done that before.
poor_red_neck said:
I'd be more than happy to, if I knew how to!
I assume it would just be an update script, but i've never done that before.
Click to expand...
Click to collapse
Just make a nandroid of your rom.. Dont include the ext partition. And maybe delete some personal stuff. lol
You could make a nandroid.. Then boot up again, delete all personal stuff and sign out of everything. Make another nandroid (the one you can send to people). And then flash back to your nandroid of all your personal stuff back on it.
I think it would be easier to just make a tutorial as I didn't really do anything that hard. Just removed some files here, replaced some there, and re-configure some stuff.
As a matter of fact it may be easier to just zip a bunch of files, and make a batch file to do it, as pretty much everything was done through ADB.
I don't like the idea of nandroid, wouldn't want to accidents include some paid app, or risk personal data getting in there.
Actually I'm going to read up on making update zips. Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Hey all. I'm considering this phone as my first Android purchase because it's on a really good plan where I live. I've heard multiple, semi-contradictory reports of lag problems with this handset due to the TouchWiz 3.0 interface.
Quick questions:
How bad is it?
Does the fabled Launcherpro UI replacement app fix the lag?
Oh, and if it's not too much to ask, one further query:
Is there a way to backup pre-installed apps?
The telco I want to get this phone with has pre-installed a bunch of stuff that might be useful in tracking my usage etc. In the event of rooting and ROMing this thing, I may want to keep those apps and re-install them after flashing the ROM.
Thanks in advance
im in the same position as you.
the mention of slight lag keeps cropping up. This worries me. I will be coming from a HTC Desire. I am wanting speed improvements, not slow downs.
Can anyone advise?
Also - in preperation for my new galaxy, I installed Launcher Pro on my Desire to see what it is like. It is ok. A bit laggy tho (more so than stock). Then I tried the ADW Launcher (which doesnt get talked about as much coz presumebly it isnt as good). I found it very smooth and just as smooth as stock Sense. Therefore.. maybe you guys should be trying ADW launcher instead
I've used both launcherpro and touchwiz and the only time I've seen any lag with either was when the phone ran out of RAM(or below 60mb).
lagging might be solved by installing custom rom
I don't have the phone, though i've been following Paul (Modaco)
forum/twitter, he also had lag issued until he installed custom ROM
and did some changes in it.
You can review his work in his forum
forum.xda-developers.com/newreply.php?do=postreply&t=715038
good luck.
Toss3 said:
I've used both launcherpro and touchwiz and the only time I've seen any lag with either was when the phone ran out of RAM(or below 60mb).
Click to expand...
Click to collapse
See, this is exactly what I mean by contradictory. It must be that some of them have it and some don't. WTF?
c_on said:
I don't have the phone, though i've been following Paul (Modaco)
forum/twitter, he also had lag issued until he installed custom ROM
and did some changes in it.
You can review his work in his forum
forum.xda-developers.com/newreply.php?do=postreply&t=715038
good luck.
Click to expand...
Click to collapse
That's good, but that doesn't really answer any of my questions all that much. Thanks anyway.
This phone is ultra fast, end of. it'll be even faster when it gets updated to access the full 512 megs of ram
compared to the nexus one i had for the past two weeks, the galaxy s has serious memory problems and is significantly slower than the nexus.
As described above, the device is lightning fast until the free memory drops below a certain point (60mb mentioned aboce seems to be about right).
At this point is becomes _very_ laggy, and the only way to get it back to normal is by killing tasks with a task killer app.
The way Android's memory model works, it should never be necessary to end applications manually. And with the nexus this was indeed never necessary.
On the samsung firmware however, garbage collection does not seem to work as it should. Maybe it expectes that there are 512mb RAM accessable (currently the galaxy's kernel only recognises 256). Or maybe it is something else. Anyway, something is currently broken. I'm on the JF3 firmware.
bookwormat said:
On the samsung firmware however, garbage collection does not seem to work as it should. Maybe it expectes that there are 512mb RAM accessable (currently the galaxy's kernel only recognises 256). Or maybe it is something else. Anyway, something is currently broken. I'm on the JF3 firmware.
Click to expand...
Click to collapse
I installed Spare Parts and set Activity/Process management to aggressive, and I've not seen any lag yet (Also JF3 firmware). While it's not an ideal solution, I feel it's better than running a task killer as it doesn't make my phone unstable just because I forgot to put something on the ignore list.
@mickeko thank you, I will try that.
Update: Setting Activity/Process management to aggressive in Spare parts doesn't help much. It is still very laggy.
I really wonder why mickeko does not have the problem - maybe I have a faulty device?
bookwormat said:
@mickeko thank you, I will try that.
Update: Setting Activity/Process management to aggressive in Spare parts doesn't help much. It is still very laggy.
I really wonder why mickeko does not have the problem - maybe I have a faulty device?
Click to expand...
Click to collapse
I had quite severe lag problems at first. I tried some task managers and they only caused more issues for me. Then I made a full factory reset, it's my first android phone so I wanted to get rid of any weird things I might have caused during my testing (I messed things up alot til I understood what it's about ). After factory reset, I installed spare parts, set to aggressive, and things work fine. I still have some lag, but it's way less than before.
I don't want to install inofficial firmwares quite yet, so I hope Samsung hurries up with the official update which seems to have resolved the lag entirely.
The lag is not being caused by lack of RAM (the device does see 512MB or RAM by the way, not only 256MB as reported above).
Currently the way the device is setup, it is writing all DATA files to the internal storage and not to the NAND as it should. For some unknown reason the internal storage has slow access times which is causing the lag.
There is a hack on Modaco's website that allows you to have the device write DATA onto the NAND and that fixes all the slow down issue however it has a limitation of max 130MB usable space on the NAND.
Samsung can fix this in a firmware upgrade by partitioning the space better.
clubtech said:
The lag is not being caused by lack of RAM (the device does see 512MB or RAM by the way, not only 256MB as reported above).
Currently the way the device is setup, it is writing all DATA files to the internal storage and not to the NAND as it should. For some unknown reason the internal storage has slow access times which is causing the lag.
There is a hack on Modaco's website that allows you to have the device write DATA onto the NAND and that fixes all the slow down issue however it has a limitation of max 130MB usable space on the NAND.
Samsung can fix this in a firmware upgrade by partitioning the space better.
Click to expand...
Click to collapse
I never had any issues with apps opening slowly before and after doing the hack I didn't notice a huge increase in speed(it's still noticeable though). Maybe some of the devices have worse access times or something as they seemed very high for such a high-end device?
You can watch my video of application starting speeds:
http://www.youtube.com/watch?v=rAE_zKAtMvg
its launcher pro, MinFreeMem on max preset, and apps data is moved to NAND memory.
Just check the speed
clubtech said:
The lag is not being caused by lack of RAM (the device does see 512MB or RAM by the way, not only 256MB as reported above).
Click to expand...
Click to collapse
I don't know much about the Android inner workings, but Android System Information states 326MB(?) RAM. Which implies that the OS sees less than 512MB RAM on my device.
mickeko said:
I don't know much about the Android inner workings, but Android System Information states 326MB(?) RAM. Which implies that the OS sees less than 512MB RAM on my device.
Click to expand...
Click to collapse
No. it means that the rest is not accessible to u and is reserved to the OS.
vitalij said:
You can watch my video of application starting speeds:
http://www.youtube.com/watch?v=rAE_zKAtMvg
its launcher pro, MinFreeMem on max preset, and apps data is moved to NAND memory.
Just check the speed
Click to expand...
Click to collapse
Speechless.
Yes its fast now, but that speed obtained is only the same speed you get with the desire without any hacks. This phone should be faster, and one shouldn't have to root and hack it to obtain a speed only comparable to a HTC desire . It's not fair coz I want this phone badly but this lag issue is really putting me.of
Sent from my HTC Desire using XDA App
But aren't there problems inherent with moving the apps data to NAND?
(I can't post the link because apparently the mods need to verify my account or something, but there's a thread in the dev forum titled "Fix for lag" that addresses this.)
Ah okay. Over at MoDaCo they're saying that it stuffs up when the NAND runs out of space (as the fix simply moves the folder for application settings to the NAND instead of the 'internal memory,' which is actually an SD card).
Javalu said:
Ah okay. Over at MoDaCo they're saying that it stuffs up when the NAND runs out of space (as the fix simply moves the folder for application settings to the NAND instead of the 'internal memory,' which is actually an SD card).
Click to expand...
Click to collapse
Yes there is one hidden thing here: If you have lots of heavy programs like some games, some navigation progs, google earth, you must keep those heavy programs in the old location. I did exactly this - moved to NAND everything except Google Earth, some Gameloft games and navigation. So now I have really fast phone, all my programs, and there is still plenty of space on NAND memory.
My biggest problem with G1 is not having enough ram. While checking what sits in my ram with MemoryUsage app I noticed virtual keyboard. Since I almost never used it, I killed it. This caused home to reload, but I believe that keyboard has not been loaded instantly.
But after some time, I could see it there again hogging my precious 9MB. Since my phone has usually only like 15MB ram free, this was quite annoying.
After doing some research and BACKUP, since I am rooted I decided to rename the application to see if it will work. The app in question is LatinIME.apk. I renamed it to LatinIME.apkBkp. While I have been there, I did the same thing with LatinImeTutorial.apk. Both files are located in /system/app.
You have to remount it writable first, search this forum for how to do it.
After renaming that file (and maybe killing the app, don't remember exactly) my phone tried to reload home. It failed to do so, force closed and then tried again, resulting in infinite loop.
I rebooted the phone and it worked well, starting normally. Now I have more ram and performance of my phone improved a bit. My free ram stays a bit higher and apps are not so often removed from it.
Overall I am happy about the result and I am looking for more unnecessary stuff to remove.
I am on CyanogenMod 4 btw., so there might be different keyboard apps on other roms.
I have not found anyone mentioning this here, only some tutorials how to change default keyboard, so hopefully someone will find this useful.
If you have any suggestion how to sqeeze even more ram from my G1, bring them on please. (I know of swap, compcache, 10mb hack and keeping low number of apps)
raqua said:
My biggest problem with G1 is not having enough ram. While checking what sits in my ram with MemoryUsage app I noticed virtual keyboard. Since I almost never used it, I killed it. This caused home to reload, but I believe that keyboard has not been loaded instantly.
But after some time, I could see it there again hogging my precious 9MB. Since my phone has usually only like 15MB ram free, this was quite annoying.
After doing some research and BACKUP, since I am rooted I decided to rename the application to see if it will work. The app in question is LatinIME.apk. I renamed it to LatinIME.apkBkp. While I have been there, I did the same thing with LatinImeTutorial.apk. Both files are located in /system/app.
You have to remount it writable first, search this forum for how to do it.
After renaming that file (and maybe killing the app, don't remember exactly) my phone tried to reload home. It failed to do so, force closed and then tried again, resulting in infinite loop.
I rebooted the phone and it worked well, starting normally. Now I have more ram and performance of my phone improved a bit. My free ram stays a bit higher and apps are not so often removed from it.
Overall I am happy about the result and I am looking for more unnecessary stuff to remove.
I am on CyanogenMod 4 btw., so there might be different keyboard apps on other roms.
I have not found anyone mentioning this here, only some tutorials how to change default keyboard, so hopefully someone will find this useful.
If you have any suggestion how to sqeeze even more ram from my G1, bring them on please. (I know of swap, compcache, 10mb hack and keeping low number of apps)
Click to expand...
Click to collapse
Unused RAM is wasted RAM. The system will kill applications when more memory is needed. Don't worry about it.
And time for you to upgrade to CM6, don't you think?
lbcoder said:
Unused RAM is wasted RAM. The system will kill applications when more memory is needed. Don't worry about it.
And time for you to upgrade to CM6, don't you think?
Click to expand...
Click to collapse
Idiocy runs rampant at Dream forums, huh? Blame the stupid Advanced Task killer dev for getting all these idiots believing killing apps actually serves a purpose...
Anyway, if the OP is concerned about memory usage and bloat, I very much doubt CM6 is a step in the right direction. Maybe the latest CM 5 is a better option.
lbcoder said:
Unused RAM is wasted RAM. The system will kill applications when more memory is needed. Don't worry about it.
And time for you to upgrade to CM6, don't you think?
Click to expand...
Click to collapse
Yep, I am very well aware how does it work, but killing the app and loading the other one uses CPU cycles and makes system slow. Especially if it happens all the time as it does on my phone. This is actually the biggest source of laggines imho.
Plus, I am pretty sure, that system apps are not unloaded (some of them at least) or they are unloaded as a last resort. Which was also the case here. I could see other apps being killed (which I did not wanted to be killed) while unused virtual keyboard was happily sitting there.
For the record, I do not use task killer of any sort, does not make significant difference for me and occupies more ram than it saves. So please save that 'idiot' for someone else.
I do not plan to switch to CM5 or CM6, because those need even more ram as CM4 does. Afaik, those roms use hw graphics support which prohibits 10mb hack. I definitely keep 10mb hack on my phone. Did a lot of good to it's speed.
Okay so what setup are you using?
I have tryed every which rom out there since i got into it and i usually only use my phone for browsing youtube music and normal phone stuff and am find these new firmwares to be getting sluggish. Basically i want a lightning quick basic build. I am interested in what exactly you are using.
elltg said:
Okay so what setup are you using?
I have tryed every which rom out there since i got into it and i usually only use my phone for browsing youtube music and normal phone stuff and am find these new firmwares to be getting sluggish. Basically i want a lightning quick basic build. I am interested in what exactly you are using.
Click to expand...
Click to collapse
I am using last version of CyanogenMod from 4 series. That is Android 1.6 based.
I have apps2sd, 10mb hack and compcache enabled. No swap. Was not working for me. I removed all the apps that stay in memory like all widgets etc. The only things that is running in my memory permanently are: SeePU (to monitor my phone), JuiceDefender (to save battery), Battery Left widget and Astrid.
I set my phone to keep Home app in memory all the time, removed all the unnecessary effects in Spare Parts and removed virtual keyboard.
With this setup, my phone performs quite ok. Not as snappy as I would want it to be, but acceptable.
Hope it helps.
I have been using Super-D 1.9.3 with 10mb hack. Removed VPN, VoiceDialer, GenieWidget and some other misc things. Latest ADW instead of Launcher.apk, MusicMod 1.5 instead of stock music, latest 1.6 Phone.apk from Wysie. I also themed my lockscreen and Powertop widget. I has been about 4 months since I flashed it and it hasn't slowed down much at all (and I rarely reboot it). Not a singel FC! Battery lasts me thru the day (I have facebook, twitter and Gmail updating themselves). All in all, its one of the best set-ups I've used. I strongly suggest trying out earlier Super-D roms if you're looking for reliable daily driver (anything before 1.11 should be quite good, 1.11 is when it all went downhill)
Good luck.
raqua said:
I am using last version of CyanogenMod from 4 series. That is Android 1.6 based.
I have apps2sd, 10mb hack and compcache enabled. No swap. Was not working for me. I removed all the apps that stay in memory like all widgets etc. The only things that is running in my memory permanently are: SeePU (to monitor my phone), JuiceDefender (to save battery), Battery Left widget and Astrid.
I set my phone to keep Home app in memory all the time, removed all the unnecessary effects in Spare Parts and removed virtual keyboard.
With this setup, my phone performs quite ok. Not as snappy as I would want it to be, but acceptable.
Hope it helps.
Click to expand...
Click to collapse
You have options.
-Remove apps2sd and use the mtd patch method. That way you cut out the slowest link on the phone: the memory card. With the MTD hack, you can get maybe 150 megs or more of internal space for apps on a donut rom.
-Use the latest version of setcpu since it doesn't stay in memory. You can try an overclock, it will help but shorten battery life some. Maybe 576 or 595 would be enough of an overclock to make it feel faster yet not drain battery like crazy.
-Keep CC on and lock home in memory
-remove the battery widget lol.
=Delete juicedefender and just use the power control widget.
-I usually remove apps that tend to launch on their own, such as the genie widget or the voice search, as well the the VK since I never use those. It's easy enough to write a script or remove them by hand from the terminal. for example, to remove the VK, open terminal and type
Code:
su
mount -o rw,remount /system
rm -f /system/app/LatinIME.apk
-reboot your phone often, and try clearing your cache using cachemate or similar
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.
This issue actually started before I updated to 4.4.4. I am currently on 5.02.
I have the WiFi version of the 2012 Nexus 7. I am running the stock Rom, and am rooted (using Wug).
I have several issues with this tablet, but by far the worst is it runs VERY slowly, sometimes taking 15-20 seconds or more to respond to my input.
I have tried doing a factory reset. The problem with that is that the tablet responded better for a day or so, but as soon as I set up my account it began downloading all my apps, making it impossible to determine whether one or more of them is responsible.
I have tried going into developer Options and checking the "Don't keep activities" option. That had no effect.
It's especially maddening when I'm trying to view web pages (using Chrome) and a page takes f o r e v e r to load. Then all those javascript ads that pop up just as the page finally loads (I tried deselecting that as well, but then I can't view slide shows, videos, and user comments on web sites).
It's also fun to click on a link, only to have the page jump right at that instant, resulting in the click hitting an unintended link!
At this point I am out of ideas, other than buying a different tablet, which I can't do right now due to financial reasons.
So my questions:
How do I troubleshoot the speed/lag issue?
How do I prevent my apps automatically installing themselves after a factory reset so I can install them one by one in an attempt to determine whether it's one or two apps causing this?
Is there a pop up blocker available for Chrome (or an alternate browser) to both block, or allow on a case by case basis those dang Javascript ads?
Thanks everyone.
Sent from my Nexus 7 using XDA Free mobile app
leebo said:
How do I troubleshoot the speed/lag issue?
How do I prevent my apps automatically installing themselves after a factory reset so I can install them one by one in an attempt to determine whether it's one or two apps causing this?
Is there a pop up blocker available for Chrome (or an alternate browser) to both block, or allow on a case by case basis those dang Javascript ads?
Click to expand...
Click to collapse
2 of these are easy, the other may take more work.
To prevent the apps from automatically reinstalling, open the play store as soon as the tablet boots up, go to my apps > installed, and click Stop. Then go to Settings in play store, and change auto-update apps option to "Do not update".
There's many adblockers out there, if you're rooted then you shouldn't have a problem installing them. I use AdAway and it works fine, Adblock plus is also popular. Just download the .apk for one you want to use and install it, run the app, then reboot, profit.
As for lag, though it's possible you have an app causing you some issues, this older device is also pretty well known for having a big problem with declining i/o performance over time, and this is more likely the culprit. But any apps that constantly run in the background can exaggerate this further, especially since we also only have 1GB of RAM on this device.
As you mentioned, a factory reset can sometimes help with degrading performance, but it will just degrade over time again through regular use (or as soon as a bunch of apps are immediately restored). This can sometimes be mitigated to a point by using fstrim, but this is not the final solution for everyone.
For me, converting to F2FS format helped with this a lot, it actually felt faster than when it was brand new initially. But it takes some extra work to make the conversion, especially the first time (you have to format your partitions, losing all data in the process, so EVERYTHING you want to keep has to first be backed up elsewhere then restored after conversion). You'll also need to install an F2FS compatible kernel or ROM. Do your research before jumping in if you go this route, and backup your data!
Thanks Prismatic.
I've seen a few posts from people complaining about the slowness of the OG Nexus. Since hardware like cpu's and Ram don't actually slow down (to my knowledge at least), I assume it's usually due to the larger size of newer apps? Like a Windows thing where a version seemingly becomes slower after several years because hardware requirements get more demanding?
But has Chrome for Android really gotten that much larger over these years to cause our little tablets to slow so much? I'm almost at the point where I use my phone (HTC One) more than my tablet for looking things up and browsing.
As far as changing file systems, I'll have to look into whether the community overwhelmingly agrees that the speed gain is worth such a drastic measure. Thanks for the input.
Sent from my Nexus 7 using XDA Free mobile app
Chrome has been a problem (along with Facebook) for my 2012 for a long time. When I did the 5.0.2 upgrade I did a factory reset afterwards about did not let it reinstall apps. I installed some fresh from the Play Store that were essential (none that run continuously) one by one. I replaced Chrome as the default with UC Browser which has Facebook Fast integrated (does FB notifications running in background) and all was like new. The only defect is that you don't have a "share to FB" in other apps. Haven't tried FB Messenger yet either. Beside the system/Google and cloud apps running in the background the major hits are Amazon Kindle and my password manager (50 and 35 MB). UCB (w/FF) are only 7.3 MB. Leaves about 500 free ram.
---------- Post added at 08:11 PM ---------- Previous post was at 08:01 PM ----------
BTW I only keep about a half dozen apps in "Recent Apps" and clear some out when it starts to lag a bit. The 2012 is not up to L's multitasking as L puts each tab or instance of an app there. Open a bunch of tabs in Chrome and you'll see what I mean.
I may try that myself. I already uninstalled FB (I've been suspecting it was a resource hog for a long time now).
I've been out of the loop for over a year though, what is "L"?
Sent from my HTC One using XDA Free mobile app
Let me guess: 16GB version? Those models used really crappy emmc that had a flash firmware bug where IO would get really slow once you hit 2-3 GB free space left on the device. If you're in that position, try freeing up space until you have 3-4GB free. It'll probably speed up again.
rtiangha said:
Let me guess: 16GB version? Those models used really crappy emmc that had a flash firmware bug where IO would get really slow once you hit 2-3 GB free space left on the device. If you're in that position, try freeing up space until you have 3-4GB free. It'll probably speed up again.
Click to expand...
Click to collapse
You are correct that I have the 16Gb version, but under storage it currently says, 8.5Gb free.
XDA Mobile App
Encrypted? If so, it wouldn't matter how much space you have free because as soon as the full-disk encryption operation completed, the internal map in the flash controller that keeps track of free blocks would think that there was no space left on the device (even though the OS and the file system would obviously report otherwise) and the only way to reset it once it gets to that point would be to reformat the file system (ex. Factory reset) which forces the flash controller to clear its internal map and start from scratch.
Either way, if your tablet is not encrypted and you're rooted, you could try to download the LagFix program from the Play Store and have it run fstrim, which would sync up the internal map of the flash controller with the current locations of free blocks of flash memory so the device doesn't keep slowing down trying to manually probe for free blocks every single damn time it needs to do a write operation. You may have to do it every once in a while as that internal map slowly fills up again though (the pro version lets you set a schedule). Theoretically, from Android 4.3 and onward, it's built into the OS and the the OS is supposed to be able to do it automatically based on certain conditions (ex. Idle for a certain amount of time, plugged in or 80%+ battery on a certain schedule), but I found that sometimes it needed to be done more often and it's always nice to be able to run the command manually if needed, although to be blunt, there's no reason why the end user should have to resort to this in the first place. That said, I don't know if LagFix will work on Lollipop (never tried; no longer have a rooted 16gb N7 due to a replacement logic board but a busted USB port so I can't unlock my bootloader to re-root the new board) and the program looks like it hasn't been updated since 2013. One way to find out, though and that'd be to try it.
Switching to F2FS as the file system rather than ext4 might help as well (I really wish I could re-root my device to try it for myself). The speed increases over other file systems when using it on flash memory come from letting the flash controller deal with the disk I/O rather than having the OS schedule things. When you look at the bug and what causes it, it could be the communication between the OS and the flash controller that's the culprit. So using a file system that cuts out the middle man and makes the controller deal with scheduling all the I/O might mitigate the problem (after all, the flash controller works fine when there's lots of free space, it's only when it fills up to less than 3gb of space that the flash controller's algorithm to sync what the file system advertises as free blocks with its own internal map starts to screw up).
I am not encrypted. I will try this LagFix app and report back, hopefully in next day or two. Do you recommend another factory reset first? Is been about three months.
XDA Mobile App
If you want, although I'd try LagFix first to see if that's all you need. If you do go through the wipe, run LagFix every so often to sync things up (assuming it works for you or on Lollipop in the first place).
OK, lagfix does NOT work on lollipop. It gives an error. When I can find the time maybe I'll try to convert to F2FS. Or else when I can find the money, try a new tablet.
Sent from a mobile device.
Question: When you wiped the device previously, how did you do it? If you're using TWRP and use the Advanced options under format to manually wipe /data and internal storage, it'll just use the rm command to delete the files which won't reset the controller's internal map. You need to use the factory wipe option, which will use the mkfs.ext4 commamnd to format the partition (which is what you want). If you've been doing it the wrong way, then that might explain why you're still getting the lag despite having a lot of space still free.
Also, the built-in trim functionality (supposedly) only triggers when the tablet is plugged in or at 70 or 80% battery *and* has been idle for 2-3 hours so if you use the tablet a lot or keep it powered off when not in use, there's a chance that the automated task won't run (and since LagFix doesn't work in Lollipop until the Dev updates it to be compatible, then there's currently no way to manually trigger it). So if you haven't already, try leaving it in powered on and plugged into the wall outlet overnight while you sleep and see if it's better in the morning. Might be worth a shot if all else fails.
Thanks. Yeah, I always leave it plugged in over night to make sure it's ready the next day.
I probably did do a factory wipe, but I'm not certain. Guess I'll try that again eventually.
XDA Mobile App
Cool. Well, if all else fails, there's one last trick to try, which is to zero fill all the empty spaces on the drive to tell the controller that the empty space is indeed empty when it hits the "start probing the file system for empty blocks to perform the write operation" part of its I/O algorithm. You can do that yourself on the command line by using dd to create a giant empty file until the drive is filled up, syncing the file buffers and then deleting the empty file, and then sync the file buffers one last time. There's also an app that can do it automatically, which is just a GUI that calls dd, rm, sync, rm and sync in the background. I forget the name, but it's in the store and I think it has "secure" as part of its name.
I had moderate success with that method as things would speed up again once done, but would slow up again over time as the drive was used. Formatting the partition is preferable because it saves on write operations and thus, wear and tear on the flash drive but the downside is that you lose all your data. And zero-fill was the preferred method outside of re-formatting the partition until someone figured out the fstrim trick. You might be able to run the fstrim command from the command line if you're rooted since LagFix doesn't work anymore on Lollipop, but I forgot what the command line arguments are. Google could probably help with that.
So still a few more things to try before giving up. But I wonder if F2FS would work better. Let us know if you ultimately go that route.
You can run the trim commands from terminal. But I found increasing the minimum clock helped.
Sent from my D6503 using XDA Free mobile app
leebo said:
This issue actually started before I updated to 4.4.4. I am currently on 5.02.
Click to expand...
Click to collapse
WOW same here, I updated from kitkat to 5.02 today and my god, this is TERRIBLE!!!
I keep rebooting in hope that SOMETHING will be better. I know this is an old tablet but I have a good mind to call Google tech support and complain about this abysmal ROM.
I did not do a wipe, just upgraded as you'd imagine that would be all one needs to do, it is a factory upgrade after all...
Some apps take forever to boot and then are inoperable because they can take a minute to respond to a touch (facebook seems the worst)
Others are very laggy but useable (like a cheap phone from 5 years ago).
I guess I have to try a factory reset/wipe.
So just to update: I have been wiping the cache partition about every five days. It lasts about two to three days. I plan on waiting until I have money to get a different tablet before getting a different ROM, or converting to the newer file system (though that will probably be some time from now). In its current condition I can't even give this thing away!
Sent from my Nexus 7 using Tapatalk
Same deal here. When new the Nexus 7 performs great. I have a 2012 8 gb version primarily for platform testing. The interface is so slow now I've given up and just use my phone. The keyboard takes forever to show up. When you first load an app it takes forever and switching between apps takes just as long. The last Nexus and Asus mobile device I will buy for a good while. At least I can still use it to test an app and know that the app will run on a crappy performing device.
Nexus 7 2012 (8gb)
Android 5.1.1
I've done factory resets and it doesn't really help, maybe for a few minutes and then back to the slow clunker. Even after the reset the keyboard is slow as snot to show up.
Just to update, I ended up using Wug's Nexus Root Toolkit to push 5.1 to my Nexus, then I did a factory reset. It had already downloaded 5.1 from Google, but I was desperate.
I had already given up and bought a Samsung Galaxy S 8.1 by then. It's now much faster. Because I bought the Samsung, I'm not using the Nexus very much, so I can't say for certain I cured it. It's worth a try however.
Signature edited to appease the OCD's
I would suggest installing Chroma 22/6/2015. It's very good since Android 5.1.1 fixes some memory leaks over 5.0.2 ^^ It runs perfectly P.S I wanted to sell or blow up my nexus with other roms so it's worth giving it a try ^^ I'd suggest wiping internal storage too after installation so you have a fresher feel ^^
Plz do it :3 You'll not regret it! The UI is pretty coolio too!