Related
I have been reading this forum for some weeks now and wanted to thank you all for the great info here. I got my first Android phone (Vibrant) a few weeks ago.
I found out about rooting just yesterday. Since I really don't want to spend a lot of time troubleshooting the phone, I had a few questions to figure out whether I should root or not:
Will rooting my phone be overall worth it? Will I have to troubleshoot it a lot as a result? It works well now.
How will the updates work in the future? For example, I won't have to worry about Android 2.2 because it will be included in Cyanogen? Will my phone notify me when it's time to update?
This one is important: are there any instructions that tell me how to backup my current phone so that I can restore it to the original condition in case something happens?
Is Cyanogen accepted to be the best for rooting?
Will all my applications become uninstalled? Will anything else change besides my access level? I read some conflicting into on this.
Can you think of any disadvantages to rooting (other than possible voiding of warranty if you can't hide it)?
Do you guys have a list in this forum as to which applications are bloatware and should be removed (and are safe to remove)? I don't know anything about Android, so I have no idea
And finally, is there a thread/list where all the most important/useful applications that should be installed after rooting are listed? I know titanium backup is one. I couldn't understand what BusyBox does. So a list with explanations would be great.
I haven't liked the battery life of this phone and I am hoping that after removing all the bloatware from it that issue might be fixed as well. My phone starts with 160M+ memory. Even though I keep killing open applications, the performance keeps dropping over time until I can't get more memory beyond ~90M. This is when I have to shut down the phone and turn back on. Other than tethering, my main reason for rooting is 1.performance gain and 2.battery life extension.
Thanks for all the help. A lot of talented people on this forum.
There is no reason to not root this phone in my opinion. You can unroot it. You will get OTA updates using the stock ROM. Many of the recommended apps, guides, useful information is in the sticky at the top. Please read that, then ask any more detailed question you may have.
edit: when you root, there will be NO change to your apps/contacts/settings/etc.... you will reboot and be like "well, am I rooted?"... look for the superuser app in your app drawer, there? Good, you were successful.
Ok, you got an excellent thread there that pretty much answered all my questions! I will root my phone and get back here if I have any more questions, with a cleaned up list. Thanks.
will applying the RyanZA fix stop the OTA update?
A lot of people have this misconception that rooting means modifying their phone. Rooting by itself is not really modifying anything on your phone, all it does is give you super user privileges.
Think of your Mac or Windows PC, you have administrative accounts and you have user accounts. Admins can do anything, user accounts are typically limited.
When you have root access to your phone, you are the admin. You can access features that default account can't.
With that said, once you do have su you step into a whole new world with many different paths. You can can simply stay rooted and use apps that required root access and leave it at that.
Or you can dive into custom ROMs. This is where you step off the manufacturers intended path and follow community developed versions of the operating system.
Alternatively, in between those two extremes above you can do many things in between. You can stay with stock rom but have custom (modules or programs) APKs, or other modifications that change or expand on stock ROM.
Always keep in mind that once you choose to root, what happens to your device is your responsibility. Once again, your responsibility. If you are not willing to accept that, then stay non-rooted/stock and responsibility will be on Samsung to add/remove features, provide updates, fix bugs, etc.
Ok, so a few questions:
I bought Autostart and hid the system apps. Now what? I don't know what to disable from this list. There are applications, but they are listed under several categories. For example, "Application Removed." I have no idea what that category is for. Should I just worry about "After Startup"? Please elaborate.
You don't recommend AppKiller. Won't all those open applications just drain the battery? For example, if I have TeleNav open, how can I close it after I am done using it without AKiller?
There is an entire thread of various people posting various things, but I still would like to see just ONE combined list of all the "safe" bloatware to remove and "risky" ones. That thread did not help me at all since various people are reporting various things.
You recommend Root Explorer, which is kind of expensive. Is there any reason why I can't use the uninstall function of Titanium Backup? Is it any less thorough?
Where is the restart function?
How can I disable those annoying power down and power up sounds of the phone? Can this be done without lowering system volume?
Thanks!
Awesome, Glad to hear your root went well.
1. I bought Autostart and hid the system apps. Now what? I don't know what to disable from this list. There are applications, but they are listed under several categories. For example, "Application Removed." I have no idea what that category is for. Should I just worry about "After Startup"? Please elaborate.
I remove almost all non-system apps unless it is logical wht said app would need to function, aka, text received you would not want to block messanger/handcent..... if there is something you are questioning, just let me know.
2. You don't recommend AppKiller. Won't all those open applications just drain the battery? For example, if I have TeleNav open, how can I close it after I am done using it without AKiller?
Now that you have root, remove all of the bloatware and it will not be an issue. These run in the background and very likely are not using ANY of your resources.
3. There is an entire thread of various people posting various things, but I still would like to see just ONE combined list of all the "safe" bloatware to remove and "risky" ones. That thread did not help me at all since various people are reporting various things.
I used that thread because a lot of people posted the apps they removed. Almost all of them can be removed, if there is one you are questioning, let me know.
4. You recommend Root Explorer, which is kind of expensive. Is there any reason why I can't use the uninstall function of Titanium Backup? Is it any less thorough?
I mentioned in the sticky that I do not use TB. I know it allows you to remove apps, but Root Explorer does this and a lot more. For example..... #6
5. Where is the restart function?
Not sure I know what you mean? if you want a reboot option you can get Quick Boot from the market.
6. How can I disable those annoying power down and power up sounds of the phone? Can this be done without lowering system volume?
In the sticky I show where the files are located. With Root Explorer you can navigate to them and delete the files.
I agree with a lot on this thread. A master Guide for rooting/unrooting and usage should be made. The FAQ currently stickied is informative for the most part but it focuses on far too many things to be able to go into enough detail on each. Personally I would like a "All things root" guide or something sticked which is comprehensive and focuses JUST on that, with the most common root usage apps and things posted (including safe disabling or removal of bloat, backing up, flashing roms, etc.) so that people who have NO idea whatsoever and it is their first phone or something can just read that and feel at home. I may start working on one if no one else does it, we'll see.
}{Alienz}{ said:
so that people who have NO idea whatsoever and it is their first phone or something can just read that and feel at home.
Click to expand...
Click to collapse
I'd say that if someone has no idea what they are doing, the last thing they should be attempting is flashing firmware on their phone.
The layer of obscurity and technical difficulty associated with rooting/modding is of benefit in terms of preventing people from doing things they should not be doing without sufficient knowledge base.
There is plenty of info here and online in general to start someone off if they are interested in learning about this in general.
IMHO, creating a trail of bread crumbs for someone who doesn't know what they are doing is more likely to hurt them or community in general rather than help them.
In my experience rooting your could be fun and a nightmare, if not done properly and, you have of time on you're you could become a rom switching addict cyanogen is currently available for the vibrant you can still root, but you will be on stock vibrant rom.till samsung release the source code so no froyo.and the rumor is that they won't release the source code.
Sent from my Nexus One using XDA App
s15274n said:
Awesome, Glad to hear your root went well.
1. I bought Autostart and hid the system apps. Now what? I don't know what to disable from this list. There are applications, but they are listed under several categories. For example, "Application Removed." I have no idea what that category is for. Should I just worry about "After Startup"? Please elaborate.
I remove almost all non-system apps unless it is logical wht said app would need to function, aka, text received you would not want to block messanger/handcent..... if there is something you are questioning, just let me know.
2. You don't recommend AppKiller. Won't all those open applications just drain the battery? For example, if I have TeleNav open, how can I close it after I am done using it without AKiller?
Now that you have root, remove all of the bloatware and it will not be an issue. These run in the background and very likely are not using ANY of your resources.
3. There is an entire thread of various people posting various things, but I still would like to see just ONE combined list of all the "safe" bloatware to remove and "risky" ones. That thread did not help me at all since various people are reporting various things.
I used that thread because a lot of people posted the apps they removed. Almost all of them can be removed, if there is one you are questioning, let me know.
4. You recommend Root Explorer, which is kind of expensive. Is there any reason why I can't use the uninstall function of Titanium Backup? Is it any less thorough?
I mentioned in the sticky that I do not use TB. I know it allows you to remove apps, but Root Explorer does this and a lot more. For example..... #6
5. Where is the restart function?
Not sure I know what you mean? if you want a reboot option you can get Quick Boot from the market.
6. How can I disable those annoying power down and power up sounds of the phone? Can this be done without lowering system volume?
In the sticky I show where the files are located. With Root Explorer you can navigate to them and delete the files.
Click to expand...
Click to collapse
1. What I don't understand is that the category says "New Outgoing Call" and GVoice beneath it. So I should NOT disable it, right? Because it has nothing to do with startup? But if so, then almost every other category has nothing to do with startup either. It is only the first listing that says "After Startup" and it misses A LOT of applications that do start up, like TeleNav. I don't even see TeleNav anywhere in that list. Same is true for "Email," Gallery," "Voice Dialer," and a bunch of other apps that I don't want to start on startup. I don't see any way of killing these other than by ATKiller. Am I missing something here?
2. See the problem is this: right now I have Telenav and I use it sometimes. However, I don't want it to run just whenever. So if I don't want to uninstall it, isn't my only solution ATKiller? There are other programs like this. And I can't disable them from the Autostart menu either since they're not there (Filtered out System files).
3. That site does not list what each of the bloatware does. For example, I am not sure I want to remove Account and Sync because I might need it for my bills. Same thing with "MyFiles." I don't even know what "vvm" is.
4. I am not able to tether the phone. I already tried Barnacle and it said "Running..." after I disabled supplicant, used channel 6, and disable ad-hoc. Then I tried this: http://forum.xda-developers.com/showthread.php?t=739147&highlight=tether, but I am still not able to connect. My laptop detects the phone as "computer-to-computer network," but when I click connect, it keeps trying to connect and then doesn't. I am not sure where to go from here.
Thanks.
One more thing I still don't know: how are the updates going to work from now on? Whenever an Android update comes out, like 2.1update or Froyo, do I have to come here and do everything manually? Or is there a way from within the phone to find out with one click? I am assuming whatever update is available for the phone will also be available for custom download (otherwise I could unroot, update, reroot?).
Thanks.
By the way, I also agree about a complete guide. It's not that it will enable the clueless to mess up their phone, but rather the opposite - it will allow the clueless to become cluefull. Such a guide would be very helpful. Meanwhile I am having to jump from thread to thread and then to Google trying to find out about this or that. That's not to say that the guide available isn't very helpful already.
I've already contacted a few people about starting said guide. I have not got much feedback from people willing to help....
^ you've asked a lot man... I can try and answer some, but you need to keep doing some reading. I feel like I've offered up a lot as is.
Just b/c you have root, does not mean you will not receive the OTA updates. If Froyo is released, you can update from the phone, you will lose root though. Most of us, will wait for the developers to have a stock froyo + root that we can flash.
why use telenav? I am not familiar.. just curious why not use google nav?
autostarts, just b/c you have it set to not start an app on boot, does not mean when you click the icon to open it will cause an issue. Really not that big of a deal. If you notice an issue, just set the app back to enabled.
Do not use a task killer.
The thread I linked has plenty of information for what you can remove from the phone, with instructions.... same for the barnacle tether app. If you want, download Wireless Tether, google it... the source code is on google.
http://code.google.com/p/android-wifi-tether/downloads/list
androidaddict23 said:
In my experience rooting your could be fun and a nightmare, if not done properly and, you have of time on you're you could become a rom switching addict cyanogen is currently available for the vibrant you can still root, but you will be on stock vibrant rom.till samsung release the source code so no froyo.and the rumor is that they won't release the source code.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Cyanogen is not yet available for the Vibrant. It will soon.
Froyo-cooked ROMS are already out for the Vibrant (alas with some bugs) so I don't think there's a reason to think Cyanogen won't be on Froyo.
Also: Never having done a root/rom flash does not make someone stupid or signify they should never try it. It just means they should READ some documentation and be technically up to the challenge before they do. I don't think having a clear guide on most of the process will hurt anyone who is coming into this but doesn't yet know all the details and steps of what to do.
Excelsius said:
Ok, you got an excellent thread there that pretty much answered all my questions! I will root my phone and get back here if I have any more questions, with a cleaned up list. Thanks.
Click to expand...
Click to collapse
glad the root went well for you. I am wanting to root my phone too, but not sure which root method is easiest and best.
Which root method did you use?
I had a mytouch rooted before the Vibrant, but they are way different and I dont want to screw up
s15274n said:
I've already contacted a few people about starting said guide. I have not got much feedback from people willing to help....
^ you've asked a lot man... I can try and answer some, but you need to keep doing some reading. I feel like I've offered up a lot as is.
Just b/c you have root, does not mean you will not receive the OTA updates. If Froyo is released, you can update from the phone, you will lose root though. Most of us, will wait for the developers to have a stock froyo + root that we can flash.
why use telenav? I am not familiar.. just curious why not use google nav?
autostarts, just b/c you have it set to not start an app on boot, does not mean when you click the icon to open it will cause an issue. Really not that big of a deal. If you notice an issue, just set the app back to enabled.
Do not use a task killer.
The thread I linked has plenty of information for what you can remove from the phone, with instructions.... same for the barnacle tether app. If you want, download Wireless Tether, google it... the source code is on google.
http://code.google.com/p/android-wifi-tether/downloads/list
Click to expand...
Click to collapse
I appreciate all your answers. I don't mean to say that anyone else can't answer as well. I am still unclear on several things I asked and would appreciate if someone could chime in, at least about the exact procedures for using autostart and the reasoning behind not using the task killer. I am new to Android, but I am pretty good at computers, including building them. So when I am learning about doing this or that, I would like to know about the reasoning behind that. I am sure that all of the questions I ask here I can find out on my own, but I was hoping that I could utilize the purpose of the forum and learn something from the veterans rather than reinventing the wheel myself.
I am using Telenav because I have a one month free trial. I discovered Google Nav just yesterday. I just want to compare them myself, even though it is unlikely I will pay $10/month in either case. But remember that Telenav is just one of the applications causing issues.
Thanks for all the answers. Please don't feel pressured to answer all the things I might ask. If I don't get enough answers, I'll just do a quick thread search and if that's not fruitful, I'll create a specific thread for autostart usage.
androidaddict23 said:
till samsung release the source code so no froyo.and the rumor is that they won't release the source code.
Click to expand...
Click to collapse
Isn't this illegal? I thought the whole point of Android was opensource and under the GPL License, they are required to post the full source code, right? Or I could just be way off base here.
kboater said:
glad the root went well for you. I am wanting to root my phone too, but not sure which root method is easiest and best.
Which root method did you use?
I had a mytouch rooted before the Vibrant, but they are way different and I dont want to screw up
Click to expand...
Click to collapse
I used the first procedure recommended in the sticky: http://forum.xda-developers.com/showpost.php?p=7150299&postcount=1
I am not sure why it said that you have to restart several times. Here are some clarifications on the steps there that I think were not too clear:
1. When you connect your device, you need to pull down the message area, click on the USB, and only then you will see the option to MOUNT your phone. I had to experiment to figure this out.
2. The guide doesn't say, but if your USB debugging mode is on, I would disable it, just to be safe: Settings (this is that leftmost button on your phone when you're at your desktop)-->Applications-->Development-->USB debugging (uncheck). This might be unnecessary, but I did it just to be safe.
3. When you are copying the Update.zip file into your phone, make sure you check the size of the folder. It must be your internal storage - it will be 12GB+ and will have your system files. If you have trouble identifying this, simply remove your SD card!
4. When you are restarting the phone, make sure you press the volume button in the MIDDLE so that it is entirely pressed (up and down). While holding it, press and hold the power. Do not let go of the volume button until your enter the recovery menu.
Anyway, that's what I did and rooted from the first time without any issues.
t0phux said:
Isn't this illegal? I thought the whole point of Android was opensource and under the GPL License, they are required to post the full source code, right? Or I could just be way off base here.
Click to expand...
Click to collapse
It could be that Samsung has modified the code for their own phones making the code their property, while the "regular" 2.2 (unmodified) would be available to everyone. I could be wrong, but I think this how it would work.
Excelsius said:
I used the first procedure recommended in the sticky: http://forum.xda-developers.com/showpost.php?p=7150299&postcount=1
I am not sure why it said that you have to restart several times. Here are some clarifications on the steps there that I think were not too clear:
1. When you connect your device, you need to pull down the message area, click on the USB, and only then you will see the option to MOUNT your phone. I had to experiment to figure this out.
2. The guide doesn't say, but if your USB debugging mode is on, I would disable it, just to be safe: Settings (this is that leftmost button on your phone when you're at your desktop)-->Applications-->Development-->USB debugging (uncheck). This might be unnecessary, but I did it just to be safe.
3. When you are copying the Update.zip file into your phone, make sure you check the size of the folder. It must be your internal storage - it will be 12GB+ and will have your system files. If you have trouble identifying this, simply remove your SD card!
4. When you are restarting the phone, make sure you press the volume button in the MIDDLE so that it is entirely pressed (up and down). While holding it, press and hold the power. Do not let go of the volume button until your enter the recovery menu.
Anyway, that's what I did and rooted from the first time without any issues.
Click to expand...
Click to collapse
thanks
10 char
Hi, thank you very much bestialbud , for your contribution now enjoy factory firmware and all functions work perfectly in A7. and also I have the Market.
thanks for the positive confirmation.
i'll try and throw out some more stuff for you the a7 users this weekend to accompany the gapps fix; some build prop improvements to get you access to more apps.
i'll try and throw out some more stuff for the rom chefs to kick up the activity in rom and mod development for the a7; map out all the files, permissions and uid/gid's, and then MAYBE if i have the time this weekend go experimental and package the factory rom into what i consider a normal update zip; zipped up rom instead of a system image w/ a script that sets all the roms permissions, symbolic links and busybox install. once its in a more manageable format like that you'll get more would be chef's and themer's contributing.
been thinkin' about it all week, i just don't have a tablet of my own (i'm the misses android fixit tech), so my works restricted to weekend mornings.
would be great, that within your improvements we have an ad-hoc connection to work properly.
the market does not have all the permissions, but wiht the permissions you indicate the fix the problem.
I'm anxious to see your improvements. Thanks again.
i'm sorry my english.
genialor; yeah, i never had any success w the adhoc wifi fixes myself. adhoc limitations are pretty common for mobile devices, not just android. i actually picked up a dsl connection due to this limitation, quite reluctantly i might add.
there is some 25 other similar tegra tablets. a portable solution could still present itself. i wouldnt count on any manufacturer adding adhoc connectity if they didnt provide it in the initial release.
i can say the usual passion finger, or release keys added to the stock one didnt make any difference. but im only using skyfire for an app name to search.
if folks could list other apps they dont see, it may help to make some gradual steps.
otherwise as far as savey folks looking at direct manipulation; the fingerprint that the market app reads after being copied from build prop is stored in /data/data/com.android.vending along w the characteristics your device supports. im a compare the tabs to my phone for fun to see if i can manipulate the data, because fingerprint replacement, w this gapps package in the rom isnt working. if that works, i can post instructions for the savvy, and MAYBE dig up some way to creatively automate adding those details.
Sent from my X10a using Tapatalk
Thanks buddy install UPDATE04-16 market + google apps and it works perfectly.
Bestialbud excellent job. Full Market yes, yes, yes ...
What is the latest market app, on Dexter mod I am running 2.3.6..
if folks could list other apps they dont see, it may help to make some gradual steps.
Click to expand...
Click to collapse
Hey, Tested your update and it seems to work fine except for some game apps. These aren't crucial but may indicate some permission issues: "crazy snowboards" seems to have a orientation problem.( only work in portrait mode.) "mau mau"intermittent FC.
*** note these apps worked in Dexter's latest mode ***
Otherwise Good Job!!
I find the installation notes for gapps mod in original thread extremely confusing.
I just installed official firmware (BTW the installation notes on official site were crystal clear). What should I do now?
A video of the entire process would be great.
P.S: NP, I just did not understand that to navigate between recovery menu items I must use "back" button.
Looks like gapps works now
sorry, i didnt provide step by step details for recovery use. i wont update that information either, as recovery is likely to change soon w lightly different instructions..
Sent from my X10i using Tapatalk
Some market applications can't see sdcard...
Looks like it is mounted as /storage/sdcard-disk0 while these apps expect it to be at /sdcard. Also /sdcard is mounted somewhere on internal memory, same place as /storage actually . Is there any way to change it?
Some market applications can't see sdcard...
Looks like it is mounted as /storage/sdcard-disk0 while these apps expect it to be at /sdcard. Also /sdcard is mounted somewhere on internal memory, same place as /storage actually . Is there any way to change it?
Ummm, there's so much information on this...please do a search in these threads on SD card and you will understand why no one wants to answer that question............
okantomi said:
Some market applications can't see sdcard...
Ummm, there's so much information on this...please do a search in these threads on SD card and you will understand why no one wants to answer that question............
Click to expand...
Click to collapse
I did search and could not find any comprehensible information.
I didn't say it would be comprehensible.
The external sd card is mounted as /storage/sdcard-disk0. The A7 can read from it but not write apps to it, or at least the market doesn't and I don't think you can run apps from it, just install from it. There is an internal sd card 4GB total, but with 1+GB available for apps, and we can also add our own sd card (up to 32GB) stuffed with our music, videos, jpgs, documents, etc....that way we can access them through gallery and media players, etc, without having to download a bunch of junk onto our internal memory.
1GB is a huge amount of internal space for the kind of apps that I suspect most of us are using. Sorry if I'm not clear, but in truth this topic has been done to death.
Maybe our intrepid developers can find a way to rewrite the way this thing works now that they have the kernel source but maybe not.
there are ways and roms that may change the sdcard mount location. the apps may com thru the google market, but their ability to run is another function of the rom.
this is only a google apps addon.
you'll have to wait a lil bit longer til you see a rom from me. i'm interested in recovery and themeing for this device right now..
Sent from my X10i using Tapatalk
muxecoid said:
Some market applications can't see sdcard...
Looks like it is mounted as /storage/sdcard-disk0 while these apps expect it to be at /sdcard. Also /sdcard is mounted somewhere on internal memory, same place as /storage actually . Is there any way to change it?
Click to expand...
Click to collapse
This is an on going problem with the sd card and the way its mounted by elocity's implementation of Android 2.2. To male a long story short, Elocity's android version is 2.2 compatible not a true implementation of Android 2.2. As far as I know no one has been able to work around this problem. Dexter tried starting with mod 1.3 but people started having problems with sd and usb detection. I'm waiting for Stream Tv to finally decide to fix this problem.
rphilippe777 said:
This is an on going problem with the sd card and the way its mounted by elocity's implementation of Android 2.2. To male a long story short, Elocity's android version is 2.2 compatible not a true implementation of Android 2.2. As far as I know no one has been able to work around this problem. Dexter tried starting with mod 1.3 but people started having problems with sd and usb detection. I'm waiting for Stream Tv to finally decide to fix this problem.
Click to expand...
Click to collapse
Drugs are bad mm'kay
Why on earth do people feel the need to disseminate misinformation on here on such a regular basis.
Go back and re-read Dexter's posts on the subject. There is a reason, a real reason, not made up like "its not true android 2.2". This is not a phone, it has larger internal storage and thus relies less on the external media. To have it the way you people want it (like a monstrous phone) the external storage would end up being the default, making it difficult to use the internal storage, and also REQUIRING that you have a decent size microSD just to make the tablet usable.
BTW, I am still laughing that I am apparently using an Android knock off lolololol
netstat_EVO said:
Drugs are bad mm'kay
Why on earth do people feel the need to disseminate misinformation on here on such a regular basis.
Go back and re-read Dexter's posts on the subject. There is a reason, a real reason, not made up like "its not true android 2.2".
This is not a phone, it has larger internal storage and thus relies less on the external media. To have it the way you people want it (like a monstrous phone) the external storage would end up being the default, making it difficult to use the internal storage, and also REQUIRING that you have a decent size microSD just to make the tablet usable.
Click to expand...
Click to collapse
BTW, I am still laughing that I am apparently using an Android knock off lolololol
Click to expand...
Click to collapse
I don't understand your response. I read Dexter's post on the subject. You need to re-read it. OS's in general have standards. If I run a windows, linux or mac system to name a few, you expect your hardware and software to run a certain way. For example, when you to read, write or print a file, any software you run for that OS should allow you to this on any computer that you run that particular OS on the same way. This isn't rocket science for a typical consumer. If you want to prove to me that I don't know what I'm talking about or worse yet that I
"disseminate misinformation on here on such a regular basis
Click to expand...
Click to collapse
. , please show specifically where what I said concerning Android 2.2 is wrong other then that you may have read dexter's post.
This is not a phone, it has larger internal storage and thus relies less on the external media. To have it the way you people want it (like a monstrous phone) the external storage would end up being the default, making it difficult to use the internal storage, and also REQUIRING that you have a decent size microSD just to make the tablet usable.
Click to expand...
Click to collapse
. That's irrelevant. The standard is not about what you want but the way it was decided that the OS should work plus I believe this is or will be addressed in Android 3.0. This constitutes and opinion rather than a fact. I didn't spend $299 on your opinion which BTW I don't agree with.
I understand XDA is developers site and you guys are use to thinking outside the box, which is fine by me, but we aren't all here for the same reasons and when I purchase something and it says I'm getting a certain thing, as a consumer, I expect the minimum of what if I'm purchasing. The box days "Android 2.2" not "Android 2.2 compatible" or "Android 2.2 features" or "Android 2.2 clone."
The question is:
- What is "Android 2.2"
- How does this relate to software and hardware issues with the A7?
- Is there a work around?
- Is there a firmware update?
and If your replying to a post, do can you contribute anything helpeful because telling me to search all of Dexter's post because you think you say a post concerning this already without reference that to that post is a waste of everyone time.
rphilippe777 said:
I don't understand your response. I read Dexter's post on the subject. You need to re-read it. OS's in general have standards. If I run a windows, linux or mac system to name a few, you expect your hardware and software to run a certain way. For example, when you to read, write or print a file, any software you run for that OS should allow you to this on any computer that you run that particular OS on the same way. This isn't rocket science for a typical consumer. If you want to prove to me that I don't know what I'm talking about or worse yet that I . , please show specifically where what I said concerning Android 2.2 is wrong other then that you may have read dexter's post. . That's irrelevant. The standard is not about what you want but the way it was decided that the OS should work plus I believe this is or will be addressed in Android 3.0. This constitutes and opinion rather than a fact. I didn't spend $299 on your opinion which BTW I don't agree with.
I understand XDA is developers site and you guys are use to thinking outside the box, which is fine by me, but we aren't all here for the same reasons and when I purchase something and it says I'm getting a certain thing, as a consumer, I expect the minimum of what if I'm purchasing. The box days "Android 2.2" not "Android 2.2 compatible" or "Android 2.2 features" or "Android 2.2 clone."
The question is:
- What is "Android 2.2"
- How does this relate to software and hardware issues with the A7?
- Is there a work around?
- Is there a firmware update?
and If your replying to a post, do can you contribute anything helpeful because telling me to search all of Dexter's post because you think you say a post concerning this already without reference that to that post is a waste of everyone time.
Click to expand...
Click to collapse
----------------------------------------------
Dexter_nlb said:
this is all a misunderstanding of how tablets are supposed to work, and caused by the fact that android 2.2 is made for a phone with external memory cards, and less to nothing of internal memory.
the current installation where apps are "moved" to internal storage is actually how vendors are trying to implement 2 types of storage.
comparing this to a mobile with just sdcard, and android 2.2 only supporting one storage type, the preferred storage becomes the "internal" and sdcard handling as you notice is now pointing to a location with the internal storage location.
the mountpoint at the internal storage location is planned based on the fact that users coming from an android based mobile knows alot about where to find data, which is in the storage location, so its put as mount at the storage so its easy to access, and not actually any bug at all.
so until better handling is presented (hopefully 3.0) people will continue to think that the handling is wrong or something is not wright here, but it is correct.
your internal storage of "just" 1.5GB is the preferred location, as tablets are not meant to have sdcards as preferred storage, if you chose not to put a sdcard into the tablet. so the choice was easy, use internal storage for android so ppl didnt need to buy additional cards.
but the lack of storage internally is a vendor decision, not a bug or not "the android way" a problem in any way..
imagine, those users without any sdcard, being unable to use the feature of android to a storage, and needed to use data storage for all files, that would look strange, if you didnt have the option available..
it could have been planned differently but vendors (all of the tegra2 vendors) has chosen this path, which could have been done differently but its all relate to apps and how they expect your device to work..
a long explanation, but remember 2.2 is not made for tablets, it made for small devices with external memory cards, which is long overdue and is followed up with the new android 3.0 which hopefully solves your problem.
conclusion,
Nvidia could have chosen a different way of using android, but they're still rather new to the platform and their design is not without problems yet (honeycomb will show that too), so if they used real planning and organized memory and sdcard handling like 2.2 was made for, you would have no problems at all. Remember Nvidia designed it this way, and they are the reason you have problems..Lack of knowledge of design and functionality, like BMW trying to make graphics card for a pc, coming from designing cars, their work would not be in a class like nvidia graphics, but probably ok..but far from good..
Click to expand...
Click to collapse
There was no button to make the important text blink and slap you in the face at the same time, so I hope bold and red will suffice.
Don't get pissy with me because you are putting out misinformation and got called on it. There are people who come on here to learn and someone might have actually believed your BS about "Android 2.2 compatible" or "Android 2.2 features" or "Android 2.2 clone."
I have contributed. You on the other hand have not. Spreading crap like this is merely tantamount to telling people the sky is purple.
Edit: by the way, the "on a regular basis" part was not directed at you or any other individual person. I was pointing out how often this happens, not keeping score of who has done it the most.
Another Edit: Of course it will be addressed in Android 3.0 ... 3.0 IS FOR TABLETS!
Yet Another Edit: No, you are right, you didn't spend $299 on my opinion. You spent $299 on a bottom of the line Android 2.2 tablet hoping for the best, just like the rest of us... And since you seem so hung up on what the box said, did your box say "Powered by Android 2.2" or did it say "Powered by some guy named Rob's opinion"? I am willing to bet it said the first. However if you decide that you are willing to pay for my "opinion", there happens to be a donate button right under my name on the left. Thanks for playing.
so, yeah. mount locations a rom issue.
'piss' somewhere else?
Sent from my X10i using Tapatalk
Okay--this might be a stupid question, but am I supposed to install this and Dexter's mod over the firmware?
If so, should I do them in a particular order?
Thanks for all that you guys do!
What you guys did, after you tear down the box and turn on your acer a500 for the first time, excluding language and timezone selection?
Check for update manually
root it
ibila said:
Check for update manually
Click to expand...
Click to collapse
What's the easiest way to do this?
ken_sadgit said:
root it
Click to expand...
Click to collapse
I don't know what is it, or how they do it, but first I wanna know why they do it. All I heard is root! root! root!
get to know it
Do not root update install 3rd party apps until you know honeycomb and android
Of course root is obviously needed it also puts system files in your hands to mess up.
Please be careful and read all the forums and threads here
Thanks for hearing my 2 cents
If you dont know why you most likely do not need to do so yet
There are a great bunch of people here .take your time and do not jumpinto to deep
If you're not going to root, obviously the first thing is to set your tablet up with your Google account (either an existing GMail account or a new one.) Then set up any other email accounts, and install any apps you know you want that aren't on the tablet already (Kindle/Nook, games, utilities, TweetDeck, Pandora, MoboPlayer, etc.)
Find yourself a good File Manager; Android doesn't come by default with a program to let you view the files on your tablet :| I personally use ES File Explorer, but HD File Manager is also pretty good and was designed for Honeycomb/tablet size displays.
As Erica said above, don't even consider rooting until you've worked with Android a bit. If you don't need the tools root provides, you're better off not doing it.
Rooting your tablet (or other Android device) installs a "SuperUser" application which can allow other apps to act as the owner of the operating system (for Windows user, Administrator level privileges rather than User). In most cases, the method of getting root involves using a device- or Android-version-specific exploit/security hole.
With Root/SU, you can:
Run root-only apps like Titanium Backup, SetCPU (profiles only currently)
Remove and/or replace apps and other files not normally in the "user" space (CAUTION: Acer's update process expects damned near all of the pre-installed apps to still be there, so ALWAYS back up the original files!)
Once the hard-working and never-appreciated-enough Devs figure out a way around the bootloader (or Acer unlocks it), you can replace the kernel files, overclock, replace the entire ROM with a custom one
Some caveats:
Rooting will almost certainly void your warranty (if discovered should you have to return it for warranty service) and if you do it wrong, you can brick your device (i.e. you now have a flat black brick, not a functional device)
Some apps will not work on devices that are rooted (and/or have the SuperUser app present). Currently this includes at a minimum Google Movies and Blockbuster.
DON'T waste you time trying to update. It's been pulled until release fo HC 3.1.
DO enjoy the unit!
DO download apps and play.
Root at your own risk, but HC 3.1 is around the corner and you will have a dificult time getting it if you don't know what your not a techie.
Lastly, put it in Airplane mode before sleep mode to save battery. If you are turning it off, no dif.
Get Astro file mgr - free
Get Weatherbug for HC - free
Get Pandora - free
Load a micro mem card with all you music and videos, and enjoy one of the best devices in production.
If you have a memory card reader, blow you Ipad friends minds by asking them to borrow the memory card in their digital camera, plug it into the USB and swipe through their pictures. They don't have an app for that.
I have had my A500 since last week. I have basically just been trying out apps and browsing Forums to get more info. In the end the forum here seems to be most active and contains the most interesting information.
Also try to google for list with "Optimized for Honeycomb". This will make you fiind the apps that are optimized for the Tablet.
I did not root my device as I dont have any need for it (yet), but I am certainly waiting for 3.1. The current version of honeycomb is a bit unstable.
For the rest just enjoy the tablet
Smile, you just bought a great tablet
So what are you guys saying is that I should not update my build version, and wait for the 3.1 update
Of course first have to buy a screen protector before remove the plastic cover. Apply the screen protector before it get dusted. Then only turn on the device, sign in your Google account and connect internet and do setting. Then go update the firmware.
Sent from my A500 using XDA Premium App
So what are you guys saying is that I should not update my build version, and wait for the 3.1 update
Click to expand...
Click to collapse
Correct, unless you know what you are doing.
Hi, a new guy here!
I recently became a happy owner of 32Gb wi-fi only N7. I’m familiar with software dev (windows developer for 20 years with some work on unix) and customization/modding/flashing process (mostly for satellite receivers). However this is my first tablet and my first Android device so I could use some help
I successfully unlocked, rooted and installed custom recovery on my N7. I would like to get to a bare bones state of the N7 and then slowly add new features/programs to it when it becomes necessary for me. So I would like to remove all non essential parts that were preinstalled on my N7.
I was under impression that I could uninstall programs using N7 UI after device gets rooted. However it seems that for majority of the apps I still only have an option to disable.
I shelled into N7 and looked around. It seems that all (majority?) of the apps are in /system/apps folder. Can I simply remove the apps and their files from that folder? Does this folder only contain user apps or does it also have system apps that are essential for N7 to function? Is there a chance to brick it by removing something (everything?) from that folder?
I searched on a forum for a list of apps that are safe to remove. I thought it would exist since it seems to be something many of us would be interested in doing. I didn’t find the list. If there is such a thing and someone could direct me there, it would be great!
Given that I can remove apps by deleting them from that folder safely, I still have a question what each app does and how important it is. Is safe to assume that any app that has a wheel with a drive belt on it as an icon in apps screen on N7 is system app and has to stay?
I have two keyboard app installed – one is Android keyboard and one is ASUS keyboard. Judging by the name 2 of these are essential since Android is the OS and ASUS is the manufacturer. But do I really need two of them?
If there is a resource/thread that discussed something similar, please let know. I look forward to learn from anyone on this forum!
_Diver said:
Hi, a new guy here!
I recently became a happy owner of 32Gb wi-fi only N7. I’m familiar with software dev (windows developer for 20 years with some work on unix) and customization/modding/flashing process (mostly for satellite receivers). However this is my first tablet and my first Android device so I could use some help
I successfully unlocked, rooted and installed custom recovery on my N7. I would like to get to a bare bones state of the N7 and then slowly add new features/programs to it when it becomes necessary for me. So I would like to remove all non essential parts that were preinstalled on my N7.
I was under impression that I could uninstall programs using N7 UI after device gets rooted. However it seems that for majority of the apps I still only have an option to disable.
I shelled into N7 and looked around. It seems that all (majority?) of the apps are in /system/apps folder. Can I simply remove the apps and their files from that folder? Does this folder only contain user apps or does it also have system apps that are essential for N7 to function? Is there a chance to brick it by removing something (everything?) from that folder?
I searched on a forum for a list of apps that are safe to remove. I thought it would exist since it seems to be something many of us would be interested in doing. I didn’t find the list. If there is such a thing and someone could direct me there, it would be great!
Given that I can remove apps by deleting them from that folder safely, I still have a question what each app does and how important it is. Is safe to assume that any app that has a wheel with a drive belt on it as an icon in apps screen on N7 is system app and has to stay?
I have two keyboard app installed – one is Android keyboard and one is ASUS keyboard. Judging by the name 2 of these are essential since Android is the OS and ASUS is the manufacturer. But do I really need two of them?
If there is a resource/thread that discussed something similar, please let know. I look forward to learn from anyone on this forum!
Click to expand...
Click to collapse
I don't have the energy right now to address every app one at a time, but I'll nudge you in the right direction. That should help you start tinkering.
The Nexus 7 is very popular in this community because it's intentionally more open, and less bloated, than much of the competition.
That being said, sure there are apps you could uninstall if you decide to. Some of the custom ROM's will have probably already have done this for you, but may create little unexpected quirks here and there.
The first thing you'll want to do is backing everything up thoroughly. I would use Titanium Pro (you'll see it referred to as Tibu a lot), to backup all apps and settings. Then I would use the Google Nexus 7 toolkit (found in the forums here) to do a backup, as well as make a nandroid backup.
Ok, so you're ready to tinker. Well, if you bought Titanium Pro from the app store, you've already got all you really need. First, use titanium to freeze an app you don't feel you need, and don't think is required. Re-boot, go about your daily routine, and see if all is ok. Continue on in this manner. Once you've frozen everything you're interested in, and made sure all is well, you can probably go ahead and uninstall them through Tibu. Freezing them should generally make them not start up anyways, so unless the tiny amount of space they take up is a concern, that's really all you generally need to do *.
* Ok, sometimes you have to fully uninstall things you don't want, but this should get you plenty to tinker with for now.
bladebarrier,
Thanks for your response. I understand the approach you suggested – disabling apps one at a time and then when they all disabled and device is working to my liking for a while I could uninstall them.
However, I’m somewhat frustrated with a sheer number of apps that I have out of the box and I can’t find a good description of what they do. For example:
Mobile Network Configuration
Google Partner Setup
Google Services Framework
Searching online doesn’t yield definitive answers if it’s something I need or will N7 work without them. I have google play store and google play services installed – does store app require services? Reading a bit about it doesn’t make it seem so, but I’m not 100% sure. So I was wondering if there is a list of apps that are required for N7 well being and that cannot be removed no matter what.
For example, Black Viper has an excellent example of what I’m looking for but for windows nt services: (can't post a link)
This page explain what each service is, what it does and if it’s safe to disable it depending on configuration you’re seeking – minimal set, typical, out of box of experimental. I would love to find something like that for N7 system apps
I installed CWM recovery when I rooted and as far as I can understand I does NAND backups. I plan on moving the backup file from the device to my desktop and keeping it there for safety reason.
The Tibu process that you described, as far as I understand (and I might be wrong here) is basically equivalent of disabling the apps using native N7 setting app, rebooting, using it for a while and then removing .apk and .odex (or simply app_name.*) files from system/apps folder. Tibu just makes it easier. Did I get that right?
And it’s still removing one app/widget at the time. I’d like to clean it out completely first and start from that point. So Tibu will probably not help me there. So my main Q is still out there – can I brick it by removing everything from system/app? Are there only user apps there or essential system apps as well? With CWM back up file on hand will I be able to recover if my experiment goes bad?
> * Ok, sometimes you have to fully uninstall things you don't want, but this should get you plenty to tinker with for now.
One of the reasons I want to have them removed is to clean up the list of apps I have on N7. Right now I have 5 pages of apps and I have little idea what they do and if I need them – I had Korean keyboard installed for example.
As I mentioned I’m a newb in this area, so maybe my approach is a bit dumb, so please be patient with me
_Diver said:
bladebarrier,
Thanks for your response. I understand the approach you suggested – disabling apps one at a time and then when they all disabled and device is working to my liking for a while I could uninstall them.
However, I’m somewhat frustrated with a sheer number of apps that I have out of the box and I can’t find a good description of what they do. For example:
Mobile Network Configuration
Google Partner Setup
Google Services Framework
Searching online doesn’t yield definitive answers if it’s something I need or will N7 work without them. I have google play store and google play services installed – does store app require services? Reading a bit about it doesn’t make it seem so, but I’m not 100% sure. So I was wondering if there is a list of apps that are required for N7 well being and that cannot be removed no matter what.
For example, Black Viper has an excellent example of what I’m looking for but for windows nt services: (can't post a link)
This page explain what each service is, what it does and if it’s safe to disable it depending on configuration you’re seeking – minimal set, typical, out of box of experimental. I would love to find something like that for N7 system apps
I installed CWM recovery when I rooted and as far as I can understand I does NAND backups. I plan on moving the backup file from the device to my desktop and keeping it there for safety reason.
The Tibu process that you described, as far as I understand (and I might be wrong here) is basically equivalent of disabling the apps using native N7 setting app, rebooting, using it for a while and then removing .apk and .odex (or simply app_name.*) files from system/apps folder. Tibu just makes it easier. Did I get that right?
And it’s still removing one app/widget at the time. I’d like to clean it out completely first and start from that point. So Tibu will probably not help me there. So my main Q is still out there – can I brick it by removing everything from system/app? Are there only user apps there or essential system apps as well? With CWM back up file on hand will I be able to recover if my experiment goes bad?
> * Ok, sometimes you have to fully uninstall things you don't want, but this should get you plenty to tinker with for now.
One of the reasons I want to have them removed is to clean up the list of apps I have on N7. Right now I have 5 pages of apps and I have little idea what they do and if I need them – I had Korean keyboard installed for example.
As I mentioned I’m a newb in this area, so maybe my approach is a bit dumb, so please be patient with me
Click to expand...
Click to collapse
Removing Google framework services is a big no-no. To be honest, the easiest way to accomplish what you want is installing a custom ROM like CyanogenMod, especially since you've done all the prep work for such a thing.
Once you install any official CM build it is as close to app-less as you can get on a modular OS like this.
littleemp said:
Removing Google framework services is a big no-no. To be honest, the easiest way to accomplish what you want is installing a custom ROM like CyanogenMod, especially since you've done all the prep work for such a thing.
Once you install any official CM build it is as close to app-less as you can get on a modular OS like this.
Click to expand...
Click to collapse
that's what i suspected! i thought that google framework would be something essential, but there is not much easily available information there to arrive at that conclusion
since i'm new to this, i thought i should stay away from any rom flashing until i get a bit more familiar with a device, terminology and stuff like that. i'm looking at the "[ROM] CyanogenMod 10.1 [OFFICIAL]" thread and i'm not sure about half of the terms - GAPPS, PSA, Nightlies i do know what ROM is, I do know what kernel is, virtual machine, etc. But it's applied to the platform that I have little experience with, so it makes me a little bit uneasy
_Diver said:
bladebarrier,
Thanks for your response. I understand the approach you suggested – disabling apps one at a time and then when they all disabled and device is working to my liking for a while I could uninstall them.
However, I’m somewhat frustrated with a sheer number of apps that I have out of the box and I can’t find a good description of what they do. For example:
Mobile Network Configuration
Google Partner Setup
Google Services Framework
Searching online doesn’t yield definitive answers if it’s something I need or will N7 work without them. I have google play store and google play services installed – does store app require services? Reading a bit about it doesn’t make it seem so, but I’m not 100% sure. So I was wondering if there is a list of apps that are required for N7 well being and that cannot be removed no matter what.
For example, Black Viper has an excellent example of what I’m looking for but for windows nt services: (can't post a link)
This page explain what each service is, what it does and if it’s safe to disable it depending on configuration you’re seeking – minimal set, typical, out of box of experimental. I would love to find something like that for N7 system apps
I installed CWM recovery when I rooted and as far as I can understand I does NAND backups. I plan on moving the backup file from the device to my desktop and keeping it there for safety reason.
The Tibu process that you described, as far as I understand (and I might be wrong here) is basically equivalent of disabling the apps using native N7 setting app, rebooting, using it for a while and then removing .apk and .odex (or simply app_name.*) files from system/apps folder. Tibu just makes it easier. Did I get that right?
And it’s still removing one app/widget at the time. I’d like to clean it out completely first and start from that point. So Tibu will probably not help me there. So my main Q is still out there – can I brick it by removing everything from system/app? Are there only user apps there or essential system apps as well? With CWM back up file on hand will I be able to recover if my experiment goes bad?
> * Ok, sometimes you have to fully uninstall things you don't want, but this should get you plenty to tinker with for now.
One of the reasons I want to have them removed is to clean up the list of apps I have on N7. Right now I have 5 pages of apps and I have little idea what they do and if I need them – I had Korean keyboard installed for example.
As I mentioned I’m a newb in this area, so maybe my approach is a bit dumb, so please be patient with me
Click to expand...
Click to collapse
Tibu requires root access, in order to perform what we're discussing. I'm relatively new to JB, but I can't imagine any stock settings replicating its capabilities.
As far as a whole bunch of apps being in your list, that's sort of the way Android works. Think of it like "superfetch", or whatever that term was in Windows Vista. Basically, two things happen when you boot. Android looks at a list of apps that are designed to start on boot, and also apps that it expects you may want to run in the future. Both of these are designed to make the device run smoother overall, and it will kill apps if extra ram is required and they are not in use. Certain Android apps require themselves to run at all times. Some of these are apps like Tasker (if you're using tasker profiles), some of these are system apps that make the device function, some of these are apps that maintain widgets or background monitoring (weather apps, gmail, calendar).
Now, there are two ways to go about sorting what is bloat, and what is there because Android decided to load it. You can install an app called Autostarts, that will give an insight into apps that start up when certain criteria are met. You can also use it to stop those apps from queuing up at those trigger points. This is another root required app, and while I purchased it long ago, may have a free version as well. It's time consuming to use, and not perfect, which is why Tibu is better for flat out locking down unwanted apps.
Back to my initial thoughts though, you will see apps in your system list that you haven't touched since boot, because Android tries to anticipate your needs. People used to use "task killers" to close the apps, and came to realize that unless one is causing a real problem, it's just going to go back into the cached app list again anyways, thus reducing battery life when it has to load it over and over again. "Task killer" is a dirty word around XDA, unless you're using it to close an app that doesn't just go into the background like a good little app should.
Basically, you're going to start playing whack-a-mole if you want your list to remain as small as possible, at all times, and yet still actually use the device for anything interesting. You can reduce it, via various methods, and if this were a device from say "insert-name" brand, and was loaded with bloat apps, by all means you should clean those out. However, I think you'll find that while google does install things that aren't needed, or even used by everyone, it's mostly not a big issue.
Check out Better Battery Stats, in the XDA forums. It's an app that shows a pretty good picture of what is actually going on when you're not looking, and can provide data on how to improve your performance. It's probably a better way to start delving into what processes are actually being used, and which ones are just basically harmless. You'll also learn a good bit about how Android works from the Dev's explanations of many of the processes.
---------- Post added at 08:36 PM ---------- Previous post was at 08:32 PM ----------
_Diver said:
that's what i suspected! i thought that google framework would be something essential, but there is not much easily available information there to arrive at that conclusion
since i'm new to this, i thought i should stay away from any rom flashing until i get a bit more familiar with a device, terminology and stuff like that. i'm looking at the "[ROM] CyanogenMod 10.1 [OFFICIAL]" thread and i'm not sure about half of the terms - GAPPS, PSA, Nightlies i do know what ROM is, I do know what kernel is, virtual machine, etc. But it's applied to the platform that I have little experience with, so it makes me a little bit uneasy
Click to expand...
Click to collapse
Make sure whichever ROM you use, if you decide to, supports your HSPA+ model. There is a separate development section in the Nexus 7 forums, for those of us that have the HSPA+ version. We are the minority, as the Nexus 7 was initially released as a wifi only tablet.
bladebarrier said:
Tibu requires root access, in order to perform what we're discussing. I'm relatively new to JB, but I can't imagine any stock settings replicating its capabilities.
Click to expand...
Click to collapse
i do have SU privileges, so what i was talking about was disabling an app thru N7 setting screen and then when i deem the app ok to remove, going to adb shell and removing the actual file.
i just did this:
mount -o remount rw /system
rm iWnnIME_Kbd_White.apk
rm iWnnIME.apk
and it removed the japanese keyboard. however when i go back to app screen under settings, i still see it but now it has a grey icon with a SD symbols in the corner. so it appears it recognizes that the app is gone, but it's still referenced in the list. i pushed the files back using NRT and it all back to the way it was. so looks like my idea of cleaning the list by removing the apk might not fly.
and now I wonder how Tibu uninstalls the apps.
bladebarrier said:
People used to use "task killers" to close the apps, and came to realize that unless one is causing a real problem, it's just going to go back into the cached app list again anyways, thus reducing battery life when it has to load it over and over again.
Click to expand...
Click to collapse
I understand the notion of apps being in the cache and being removed when more RAM is needed, however the purist in me just doesn't want the junk apps to be there in first place However there is a lot of validity to these of your words:
bladebarrier said:
Basically, you're going to start playing whack-a-mole if you want your list to remain as small as possible, at all times, and yet still actually use the device for anything interesting.
Click to expand...
Click to collapse
My wife got Kindle Fire HD recently and she's been using it happily. While I was thinking why would anyone want a closed up system (well, more closed up system then Nexus), she's been using it and I've been frustrated with my N7 so i might just let it go and enjoy the japanese and korean keyboards anyway
bladebarrier said:
Make sure whichever ROM you use, if you decide to, supports your HSPA+ model.
Click to expand...
Click to collapse
i'm wifi only
ngshniq every
i think i found what i was after: http wiki.cyanogenmod.org/wiki/barebones (url modified since i still can't post urls). this wiki page has the list of app with a short description and if it's safe to remove. it also has additional information that explains why i still saw the reference to the app in the list when apk file was deleted:
looks like i need to pay attention to 2 additional files:
/data/system/packages.xml
/data/system/packages.list
i bet I would find a reference to the apps in these and i would need to remove it in order to have the app disappear from the app list. i'll play around a bit more and report back
One thing, could you explain your reasoning behind wanting to delete everything but the essentials? Do you have a particular goal in mind or is it because of your windows background? Because if so, you should know that android operates very differently when compared to windows, and such, the requirements to keep your device working in tip top shape vary greatly.
In my opinion, with your current limited knowledge of each process/app inner workings, what you're trying to do surefire way to break something beyond repair and needing to use a factory image to get back to zero. A custom ROM will be much safer and yield the exact same results that you're looking for. (Eventually, once you understand what each thing does, then this manual approach could satisfy your needs)
Note: GApps are the basic Google apps to flash on top of the barebones system. Gmail, Play store, and the framework.
Nightlies are experimental builds compiled nightly by a bot with the latest CyanogenMod code available.
Sent from my Nexus 7 using Tapatalk HD
My goal was to simplify my approach to N7 by removing anything that I don’t need now and slowly adding all necessary components as I get familiar with it. But it seems at this point that this approach is a bit more complicated as thought it would be.
So I think I would leave it alone for now and revisit this later
_Diver said:
My goal was to simplify my approach to N7 by removing anything that I don’t need now and slowly adding all necessary components as I get familiar with it. But it seems at this point that this approach is a bit more complicated as thought it would be.
So I think I would leave it alone for now and revisit this later
Click to expand...
Click to collapse
From what you've done manually, you're clearly far ahead of a new user when it comes to understanding linux/unix.
If you want to lock down parts of what google implements, purely to keep it minimalistic, I would agree with the above poster. Go for one of the popular ROM options that are available, like CM, and work your way backwards. The Nexus 7 only has as much bloat as you allow it to have via the settings. This is another reason why Better Battery Stats is an excellent way to make sure your device isn't draining battery, yet isn't locked down. The other day I noticed an app that kept fetching my position, even though the case was closed (magnetic sleep mode). It turned out I forgot to disable the tracking in google maps (why it was defaulted to ON, I have no idea). BBS showed me what was running during the sleep phase, and I fixed it when I woke up the next morning after wondering why my battery dropped.
The Kindle Fire is a great option, because it doesn't require any of this fussing about. My woman loves hers. LOVES IT. Personally, I like to tinker a bit, and I'm too invested in Android apps to not have access to the play store. The Nexus 7, is for people like what you find here. We like to tinker, and make everything custom. At the same time, you could spend all day trying to figure out why EntriesRefresh_wakelock is your highest partial wakelock count, at 60seconds per 7 hours, or you can find that you just went 7 hours and only used 6% of the battery, even though you've been connected to wifi, texting, emailing, and checking the weather and news, the whole time. Not bad, honestly.
The biggest investment you can do for your Nexus, is probably getting a case that magnetically puts it to rest when you close it. After that, learn about the settings that drain battery in the background. Then, get Tasker and play around that (it's like programming, without the need to learn the code). After that, go to a custom ROM, or dig out Tibu, and basically start customizing which apps you will use. If that doesn't pass the time long enough, you can literally make your own ROM and put together exactly what you want. Whether the performance will be that much better or not, and whether you'll spend most of your day trying to look for coding errors, is up to you. I don't have the patience to code, but you're a coder, so what is broccoli to me, may be bacon to you.
I got a Like New NST, reset it, unregistered it, and rooted it. I haven't replaced the kernel yet. But I have noticed that (even before I rooted it) the battery consumption is unacceptable. I've seen some old threads about this (for example https://forum.xda-developers.com/showthread.php?t=1475070) , and some suggested removing some APKs like Phone.apk and TelephonyProvider.apk, while others suggested removing or disabling some B&N-related APKs.
The thing is that some other threads seem to imply these solutions are bogus and that they don't really help. There is a lot of conflicting information spread around on this topic.
Does anybody know if there is a solution to this issue? I'm really loving the NST, it's an amazing reader in all ways except for this glaring issue.
Thanks!
Winston S. said:
I got a Like New NST, reset it, unregistered it, and rooted it. I haven't replaced the kernel yet. But I have noticed that (even before I rooted it) the battery consumption is unacceptable. I've seen some old threads about this (for example https://forum.xda-developers.com/showthread.php?t=1475070) , and some suggested removing some APKs like Phone.apk and TelephonyProvider.apk, while others suggested removing or disabling some B&N-related APKs.
The thing is that some other threads seem to imply these solutions are bogus and that they don't really help. There is a lot of conflicting information spread around on this topic.
Does anybody know if there is a solution to this issue? I'm really loving the NST, it's an amazing reader in all ways except for this glaring issue.
Thanks!
Click to expand...
Click to collapse
I sympathize and don't want to add to the conflicting information. Read what I wrote here: https://forum.xda-developers.com/showpost.php?p=78287581&postcount=2 under "Decrapify system/app". I can tell you definitively that Phone.apk has little or nothing to do with your battery drain. I did a major study on that issue a long time ago: https://forum.xda-developers.com/nook-touch/general/battery-usage-phone-apk-t3341370
nmyshkin said:
I sympathize and don't want to add to the conflicting information. Read what I wrote here: https://forum.xda-developers.com/showpost.php?p=78287581&postcount=2 under "Decrapify system/app". I can tell you definitively that Phone.apk has little or nothing to do with your battery drain. I did a major study on that issue a long time ago: https://forum.xda-developers.com/nook-touch/general/battery-usage-phone-apk-t3341370
Click to expand...
Click to collapse
Thank you for all your work, you are very methodic and logical, and I appreciate your generosity sharing all your knowledge about the NST (I have been reading up on different things here before I decided to buy one.) :good:
So, to condense all this, it looks as if neither deleting Phone.apk nor disabling B&N apps helps with battery consumption. Also, am I correct in concluding that having an unregistered Nook (or a Nook which is offline, even if registered) will invariably result in poor battery life? That's quite unfortunate, as I was planning to use my NST as a fully offline device.
Winston S. said:
So, to condense all this, it looks as if neither deleting Phone.apk nor disabling B&N apps helps with battery consumption. Also, am I correct in concluding that having an unregistered Nook (or a Nook which is offline, even if registered) will invariably result in poor battery life? That's quite unfortunate, as I was planning to use my NST as a fully offline device.
Click to expand...
Click to collapse
Almost, but fortunately not quite right. Although B&N did some questionable stuff when they cobbled together the NST/G system, I don't think they expected the devices to spend a lot of time online. If the system detects that there is no WiFi, it just slaps a post-it on its internal "refrigerator" to remind it to try a check-in later. All of that happens pretty quickly and in the grand scheme of things Android where stuff is not always killed outright even when you've finished with it, it's not a Big Deal.
So register and forget. It's the easiest path to device stability and the intended power consumption pattern.
nmyshkin said:
Almost, but fortunately not quite right. Although B&N did some questionable stuff when they cobbled together the NST/G system, I don't think they expected the devices to spend a lot of time online. If the system detects that there is no WiFi, it just slaps a post-it on its internal "refrigerator" to remind it to try a check-in later. All of that happens pretty quickly and in the grand scheme of things Android where stuff is not always killed outright even when you've finished with it, it's not a Big Deal.
So register and forget. It's the easiest path to device stability and the intended power consumption pattern.
Click to expand...
Click to collapse
Thank you again, I suppose if that's the case then I will register my NST. A couple questions: So if I register the device and never again connect to Wireless that "refrigerator post-it" won't expire?
And, most importantly, if I register with B&N will they push the 1.2.2 update on my device, or can I prevent that without any ill effect? I'd really like to stick to 1.2.1.
EDIT: I read your previous OP about the 1.2.2 OTA update, and your link for how to block it here: https://forum.xda-developers.com/showpost.php?p=34433959&postcount=3
Renate NST also suggested deleting /system/app/DeviceManager.apk, but I don't know if this would be problematic with the B&N registration issue I'm trying to fix to begin with.
Is there a preferred way to do this and still keep the device registered and battery life unscathed?
I appreciate your help!
Winston S. said:
Thank you again, I suppose if that's the case then I will register my NST. A couple questions: So if I register the device and never again connect to Wireless that "refrigerator post-it" won't expire?
And, most importantly, if I register with B&N will they push the 1.2.2 update on my device, or can I prevent that without any ill effect? I'd really like to stick to 1.2.1.
EDIT: I read your previous OP about the 1.2.2 OTA update, and your link for how to block it here: https://forum.xda-developers.com/showpost.php?p=34433959&postcount=3
Renate NST also suggested deleting /system/app/DeviceManager.apk, but I don't know if this would be problematic with the B&N registration issue I'm trying to fix to begin with.
Is there a preferred way to do this and still keep the device registered and battery life unscathed?
I appreciate your help!
Click to expand...
Click to collapse
I think since you are just starting out working with the device and don't have work to lose by updating and re-rooting, registering and then updating (you can do it manually by downloading the file yourself) is your best bet. The device keeps a "last date contacted" and "next date to try contact" in settings.db. If there is no WiFi, it will just keep changing the dates. That's all.
OTOH, if you do not update but NEVER connect to WiFi, there will probably be no issue. The method to block updates "works", as I found, but it did not prevent the occasional reboot when I was connected to WiFi, so I finally just threw in the towel and updated my devices, starting over from scratch. I'm happy with the many changes I've made since, so it worked out for me. Not sure why you want to stay with 1.2.1. It is virtually identical to 1.2.2 and I don't believe there is anything on-site here that worked with 1.2.1 which doesn't also work with 1.2.2. All B&N did was patch contacts with their servers for TLS 1.2 compliance.
Deleting/disabling DeviceManager will give your NST Alzheimers as far as your registration is concerned and it will just begin wondering why it can't remember who it is and how/when to phone home--wherever that is. One of the problems with disabling B&N apps is that there are also jar files which don't get disabled and the system still tries to fool with those. You can delete/disable those as well but the more you niggle at the system architecture the more unstable the device becomes and the more things fail to work properly (like the Reader and Library).
Like I said before, it's better AND easier to just treat the device the way it was designed as far as updating or registering. You don't have to use a credit card, you don't even have to use a real e-mail address, I suppose. Then when all that is out of the way you can just install your own launcher and set the "n" button to Home. Voila! You'll never see or hear from the B&N stuff again and your battery will last a good long time.
nmyshkin said:
I think since you are just starting out working with the device and don't have work to lose by updating and re-rooting, registering and then updating (you can do it manually by downloading the file yourself) is your best bet. The device keeps a "last date contacted" and "next date to try contact" in settings.db. If there is no WiFi, it will just keep changing the dates. That's all.
OTOH, if you do not update but NEVER connect to WiFi, there will probably be no issue. The method to block updates "works", as I found, but it did not prevent the occasional reboot when I was connected to WiFi, so I finally just threw in the towel and updated my devices, starting over from scratch. I'm happy with the many changes I've made since, so it worked out for me. Not sure why you want to stay with 1.2.1. It is virtually identical to 1.2.2 and I don't believe there is anything on-site here that worked with 1.2.1 which doesn't also work with 1.2.2. All B&N did was patch contacts with their servers for TLS 1.2 compliance.
Deleting/disabling DeviceManager will give your NST Alzheimers as far as your registration is concerned and it will just begin wondering why it can't remember who it is and how/when to phone home--wherever that is. One of the problems with disabling B&N apps is that there are also jar files which don't get disabled and the system still tries to fool with those. You can delete/disable those as well but the more you niggle at the system architecture the more unstable the device becomes and the more things fail to work properly (like the Reader and Library).
Like I said before, it's better AND easier to just treat the device the way it was designed as far as updating or registering. You don't have to use a credit card, you don't even have to use a real e-mail address, I suppose. Then when all that is out of the way you can just install your own launcher and set the "n" button to Home. Voila! You'll never see or hear from the B&N stuff again and your battery will last a good long time.
Click to expand...
Click to collapse
The main reason I want to avoid 1.2.2 is because I tend to value stability overall, and since most of the stuff here was created by the era of 1.2.1 or before, I am leery of doing something that will make things less compatible. Plus I am distrustful of B&N changes on a device this old. I also thought I had read you explaining some changes that needed to be done after a 1.2.2 update to make something work (NM, maybe? I forget.)
So my question was more along the lines of whether, when I register the device, it will be flagged immediately for update and cause some trouble if I don't, or even if the update will be downloaded in the background without me being able to do anything about it. I suppose I could always patch the sqlite file to disable OTA updates and then register. That would be the safest way to go. And you need to use ADB for this to work, right? There is no way to edit the file onboard the NST itself?
I can't wait for the battery consumption to be normal, because I am really enjoying my NST with its great ergonomy and the ability to install different readers. Mine is going to be a dedicated offline ebook reader, but a great one. And much of the reason it is so amazing is thanks to folks like you and Renate who have contributed so much. :good:
Winston S. said:
The main reason I want to avoid 1.2.2 is because I tend to value stability overall, and since most of the stuff here was created by the era of 1.2.1 or before, I am leery of doing something that will make things less compatible. Plus I am distrustful of B&N changes on a device this old. I also thought I had read you explaining some changes that needed to be done after a 1.2.2 update to make something work (NM, maybe? I forget.)
So my question was more along the lines of whether, when I register the device, it will be flagged immediately for update and cause some trouble if I don't, or even if the update will be downloaded in the background without me being able to do anything about it. I suppose I could always patch the sqlite file to disable OTA updates and then register. That would be the safest way to go. And you need to use ADB for this to work, right? There is no way to edit the file onboard the NST itself?
Click to expand...
Click to collapse
There's really no reason to be concerned about the 1.2.2 update. It's all fine. B&N would not go to the trouble on an old device like this only to somehow wreck it. It's just a TLS security update and involves connection to their servers. Since you do not intend to use the device online, the only minor issue (resigning Opera Mobile browser-- which I've already provided elsewhere) is moot for you.
As for changing the OTA flag, you can do it via ADB if you install sqlite3. This is probably best since moving settings.db back onto the device after editing can be tricky. But you could eliminate the entire tango by just updating to 1.2.2 and going on with your life
nmyshkin said:
There's really no reason to be concerned about the 1.2.2 update. It's all fine. B&N would not go to the trouble on an old device like this only to somehow wreck it. It's just a TLS security update and involves connection to their servers. Since you do not intend to use the device online, the only minor issue (resigning Opera Mobile browser-- which I've already provided elsewhere) is moot for you.
As for changing the OTA flag, you can do it via ADB if you install sqlite3. This is probably best since moving settings.db back onto the device after editing can be tricky. But you could eliminate the entire tango by just updating to 1.2.2 and going on with your life
Click to expand...
Click to collapse
Thank you for clarifying that, I think I have had an overdose of information from reading too many threads in a short span of time and somehow I got the idea NookManager had some sort of issue after the 1.2.2 update that required some tinkering. The fact that the update is limited to the TLS update means it doesn't affect me, so things would be OK. On the other hand, not installing the update also seems like wouldn't be an issue and I really wanted to get ADB going anyway to install things wirelessly, so the most logical path seems to go through the minimal effort required to change that setting anyway. It turns out I already have sqlite3 installed (I am running an Ubuntu system,) so even more reason to do this!
I'll be reading up on the way to get ADB working.
BTW, I know you have proposed probably changing NookManager to address different issues you have encountered. Let me know if I can be of any help. I have no experience building Android components and limited experience compiling, but I would be happy to learn a new skill.
Thanks! :good:
@nmyshkin I easily managed to change the OTA setting through USB ADB. (I'm keeping track of all this process so when I have everything set up I will create a thread for posterity to help anyone else with the same questions.)
Now, the problem I wasn't anticipating is that I didn't foresee the battery problems, so I used that procedure to avoid the Register prompt on startup (Bypass OOBE procedure.) But of course now I don't know how to register the Nook. Do I need to reset to Factory using NookManager, root, disable OTA, and then register? It would be nice if there is a way to avoid this?
EDIT: Searching through another thread I saw your suggestions (almost 3 years old) to use the DeviceRegistrator, so after creating a B&N account I did and it said that the registration was successful, but in Settings the Account is showing up as unavailable, so I restarted the NST, and still I am getting Account Unavailable under Settings. Does the Device Registrator not work anymore? Or have B&N stop registering NST devices?
So I checked by logging into the B&N account and as expected there are no NSTs linked to my account. The DeviceRegistrator app has a few options (Register Device, Authenticate Device, Register User, and Authenticate User.) I didn't touch the User options so I guess that is to create a new account. I just used the "Register Device" option. Do I need to Authenticate Device too, or is this just not working anymore?
I read somewhere that there is also another app called OOBE Reg or something like that that basically runs the default registration procedure, but I haven't found that app in my NST.
I actually went down a similar rabbit hole myself at one point when I was investigating selective disabling of B&N apps, etc. Yes, you need to authenticate. That may or may not have the desired effect. Right now DeviceRegistrator is your only option. It may or may not be possible to authenticate a rooted device by this method.
Having said that, maybe it's time to take a step back and ask yourself whether all this angst is worth the end result when the path of least resistance will yield an equally functional result. The answer to that depends, in part, on how much other stuff you have already done. But before you do more things don't forget that the basic device needs to be in optimum working condition (like not eating battery) first.
nmyshkin said:
I actually went down a similar rabbit hole myself at one point when I was investigating selective disabling of B&N apps, etc. Yes, you need to authenticate. That may or may not have the desired effect. Right now DeviceRegistrator is your only option. It may or may not be possible to authenticate a rooted device by this method.
Having said that, maybe it's time to take a step back and ask yourself whether all this angst is worth the end result when the path of least resistance will yield an equally functional result. The answer to that depends, in part, on how much other stuff you have already done. But before you do more things don't forget that the basic device needs to be in optimum working condition (like not eating battery) first.
Click to expand...
Click to collapse
I will Authenticate using DeviceRegistrator and see if it works. The Catch 22 is that if I revert to Factory and then register the device I might have a problem with the 1.2.2 update I want to avoid (but yes, I realize at this point my aversion to 1.2.2 is basically irrational.) So I will try this approach first and report back. I will double check to see if the Nook Device shows up in my B&N account too, and I'll report again.
I agree 100% about putting the device in a sound baseline state before installing a lot into it. I'm documenting all that I do, and when I reach that state I'll create a thread about it. Hopefully it can be of use to someone down the road, because I do see new NST units being bought still every week in eBay.
I was relieved that ADB over USB was already enabled by installing NookManager and that I only needed to create a couple of files in my Ubuntu machine for it to work.
Winston S. said:
I was relieved that ADB over USB was already enabled by installing NookManager and that I only needed to create a couple of files in my Ubuntu machine for it to work.
Click to expand...
Click to collapse
That's actually news to me. I had thought the flag for WiFi ADB was set. I've never tried USB.
nmyshkin said:
That's actually news to me. I had thought the flag for WiFi ADB was set. I've never tried USB.
Click to expand...
Click to collapse
Yes, apparently ADB Konnect is set up so that if you start ADB Wireless it sets the flag, and then unsets it. I just tried ADB through Wireless and it also works.
To update on the DeviceRegistrator, I tried to Authenticate the Device and it didn't work (I got a banner saying that the operation is no longer supported.) So it looks like I will need to restore to Factory, register, and then root (which defeats the purpose of disabling OTA updates, as I can't do that until I root.)
@nmyshkin, is resetting the Nook to factory by using "Erase & Deregister Device" option in the stock Nook Settings the same as resetting to factory.zip from NookManager or holding the two Page Back hardware buttons on startup?
I reset mine using the "Erase & Deregister Device" menu option, and then registered and rooted it again, but still I am having problems with CoolReader (I am using the cr3_0_49_13.apk posted in the relevant thread.) Basically, there are no options to set the refresh interval where they should be, and the Options interface is black. Somebody mentioned this as well but they fixed it by restoring to factory, so I'm wondering what the deal is. Is this the only version of CoolReader people use with the NST?
Winston S. said:
@nmyshkin, is resetting the Nook to factory by using "Erase & Deregister Device" option in the stock Nook Settings the same as resetting to factory.zip from NookManager or holding the two Page Back hardware buttons on startup?
I reset mine using the "Erase & Deregister Device" menu option, and then registered and rooted it again, but still I am having problems with CoolReader (I am using the cr3_0_49_13.apk posted in the relevant thread.) Basically, there are no options to set the refresh interval where they should be, and the Options interface is black. Somebody mentioned this as well but they fixed it by restoring to factory, so I'm wondering what the deal is. Is this the only version of CoolReader people use with the NST?
Click to expand...
Click to collapse
No, erase and deregister does just that. It removes your account info and settings. The factory reset is an actual reimaging of the device from the protected onboard image. This can be done with the two button technique, NookManager or eight failed boot attempts.
I'm afraid I can't help much with CoolReader. I once had a version installed but found it had way too many settings for me. I ended up using only the screensaver/book cover option but that was pretty silly and I eventually got rid of and wrote my own app for that.
I located the version for the other fellow, but that's the extent of my knowledge. I'll try it in a bit and see what you're talking about.
nmyshkin said:
No, erase and deregister does just that. It removes your account info and settings. The factory reset is an actual reimaging of the device from the protected onboard image. This can be done with the two button technique, NookManager or eight failed boot attempts.
I'm afraid I can't help much with CoolReader. I once had a version installed but found it had way too many settings for me. I ended up using only the screensaver/book cover option but that was pretty silly and I eventually got rid of and wrote my own app for that.
I located the version for the other fellow, but that's the extent of my knowledge. I'll try it in a bit and see what you're talking about.
Click to expand...
Click to collapse
Please, don't waste any time with CoolReader. As usual, you saved the day. I'll reimage the device using the correct procedure, as I mistakenly believed this is what the Erase and Deregister option did. I think this will take care of the CoolReader weirdness, and if not I have found that NoRefresh works remarkably well with it anyway. Thank you!
Winston S. said:
Please, don't waste any time with CoolReader. As usual, you saved the day. I'll reimage the device using the correct procedure, as I mistakenly believed this is what the Erase and Deregister option did. I think this will take care of the CoolReader weirdness, and if not I have found that NoRefresh works remarkably well with it anyway. Thank you!
Click to expand...
Click to collapse
Mmm.....I see nothing in that version of CoolReader thats looks anything like it was adapted for the NST. I got that version from a e-book blog post link so shame on me for passing along bogus stuff. It's definitely NOT the version I once had installed (whatever that was...). The current market version is incompatible and the "new" CoolReader GL installs but does not run. I took a look at the CR home at SourceForge and there are many versions available there but it would be trial-and-error with them--and maybe there is no magic bullet. If you search for "CoolReader" on the forum you will find a variety of references. In some lists of "working" apps there are version numbers. Tracking down one of those might be a start.
nmyshkin said:
Mmm.....I see nothing in that version of CoolReader thats looks anything like it was adapted for the NST. I got that version from a e-book blog post link so shame on me for passing along bogus stuff. It's definitely NOT the version I once had installed (whatever that was...). The current market version is incompatible and the "new" CoolReader GL installs but does not run. I took a look at the CR home at SourceForge and there are many versions available there but it would be trial-and-error with them--and maybe there is no magic bullet. If you search for "CoolReader" on the forum you will find a variety of references. In some lists of "working" apps there are version numbers. Tracking down one of those might be a start.
Click to expand...
Click to collapse
Thank you for looking at this. I am a little confused, because you helped @ALinkToTao who was having problems with it, and he seems to imply that the version linked here which you referred him to ended up working for him..
So I'm just going to write that off to him being confused about the version he ended up installing. I will see if I find something that works, thanks again.
Winston S. said:
Thank you for looking at this. I am a little confused, because you helped @ALinkToTao who was having problems with it, and he seems to imply that the version linked here which you referred him to ended up working for him..
So I'm just going to write that off to him being confused about the version he ended up installing. I will see if I find something that works, thanks again.
Click to expand...
Click to collapse
Yeah, so I need to redeem myself there. In my lame defense, I was just going with what was posted here: https://blog.the-ebook-reader.com/2...artial-refresh-and-page-button-support-video/
Clearly that is bogus. So I checked out @wozhere's listed working version, or something close.
I think the place to start is with the 3.1.2 series from the SourceForge home of CoolReader. The attached version looks a lot more like what I remember and has screen refresh options (only visible as settings while viewing a book).
There were many more options on the version I once had, so this one is a starting point only.