Just got an old Nook Simple Touch. Market not working. What can I do with it besides?

Just got an old Nook Simple Touch. Market not working. What can I do with it besides? - Nook Touch General

Ok, so I got an old Nook Simple Touch. In part because they can be had for such a cheap price on eBay these days and in part because they're among the few eInk based devices that run on Android and can actually be unlocked and more done with them than the manufacturers intended (I've used an old Kindle and man I hate how locked down and generally useless they are.) Actually, I was hoping I could do some neat stuff like setup daydream with weather info and a clock and all on it while the screen was "off" but I guess I forgot that this is a relatively new thing and it looks like it's based on a really really old Android version? Either way, I'm so used to CyanogenMod and its relatively near to AOSP nature that this thing is feeling horribly limiting and unpleasant to use for me.
Anyway, I've been searching around for various guides and such. I've found tools for rooting and putting the Google Market (yeesh, I forgot they used to call it "Market" ages ago.) It seems I needed to update the system to 1.1 for this (I had bootloops until I did, so clearly you have to have the right system version.) It seems there is a newer version or two beyond this though, but I didn't see root tools (I'm still hoping I can do more with this that might require root access to actually do.) Should I be updating beyond that? Namely, are there tools to actually root and all if I do?
Also, in the meantime, I'm running into troubles with the plain and simple fact that neither Google Market nor Amazon's app store installed by these tools work which may not be fixable. The thread on here says to add an account through Youtube first, then go to gmail and manually refresh over and over until it eventually crashes. After probably 15 minutes of this my hands were too tired to continue though. I just don't think it's supposed to take 15 minutes though. When I start the market it doesn't crash like that guide mentions either. Is there any other way to fix this? Is there any point? Obviously the market app is quite old, so perhaps it's simply never going to work? Is there some alternative way to find stuff that actually works on the NST? I thought to do F-Droid, but even it requires a newer SDK version apparently (I'm getting kind of curious what version of Android its base corresponds to. Does it predate 2.2? If so I may be in trouble since I don't think any of the stuff I was hoping I could put on there will go lower than 2.2.)
For this matter, is there a better way I can do stuff like loading apps? I was hoping to at least have a file manager to be able to use do stuff, but they didn't include one. I'll probably have to track down an apk. For now I'm having to actually use the network adb (I installed the version of the tools that was supposed to do adb over USB, but it doesn't even show up as an adb device at all for me to even so much as install a driver, so I guess it's not doing adb over USB as it should. The network method seems to work, though I'm not a big fan of leaving it wide open like that on principle really, yet remembering to manually change it on and off is a pain too.)
I realize this is a really old device and probably it is very limited what I can really do with it, but I was hoping I could at least squeeze a bit of use out of it. In particular, I'm going to need a much better reading app even if I use it for its intended purpose only. When I looked it up I had thought it was a close enough to stock Android that I'd be able to load up most apps I guess and I didn't think it would be so hard to even get anything on it.

Whew!
OK, let's start with basics. You didn't say how you rooted it but if you're working from 1.1 you probably are not getting the best out of the device. 1.21 is the final stock version. If you can get your NST back to stock, I would recommend doing so. Considering what you seem to have done already probably the easiest way to go is to use the NookManager route. Go here. Follow the instructions. There is info there for adding a Gapps package after rooting. But first get yourself back to 1.21 stock. Once that's done you can either use the Search Market tool from the Gapps package, or find apps on your computer and have them show up on the NST via the PlayStore, or side-load apps from the SD card or via ADB (default on that is WiFi with NookManager--you can install the ADB Konnect app and it works fine). There are plenty of alternate readers that run on the NST. I happen to like the stock reader very much, but to each his/her own.
When all that's done, everything depends on what your expectations are and what you want from your NST. There are a variety of kernals out there as well as USB host/audio mods. Although the Android system is old and the display limits what you can do, there are many apps that run well on the device and I personally get a lot of use out of mine, even more now that I have audio. Check out what I've done (second post) and look at what others have done (in the same thread).
There's a lot of good info in this forum on modifications, apps that run well (and don't) and many tips and tricks.

I think I have most of what I need with that actually, yes. I didn't realize from the guides I initially found that you could root or install third party components with a > 1.1 system version. With that stuff I do have a semi-working Google Market now and can actually install a lot more stuff than I thought. I see also my favorite reader app not only works, but apparently knows I'm running it on a device with an eInk screen and defaults to having eInk adaptations turned on.
Is there any way it can do anything like what I had sort of envisioned before btw? Eg on the screen "off" mode have some sort of thing that shows weather or news or something that updates every so often? (Nevermind the clock thing, that's probably a bad idea. I was just wondering about dedicating it to being sort of something like a clock with it plugged in all the time. Now I think maybe I can stop using my tablet for reading and use this instead.)

Nazo said:
Is there any way it can do anything like what I had sort of envisioned before btw? Eg on the screen "off" mode have some sort of thing that shows weather or news or something that updates every so often? (Nevermind the clock thing, that's probably a bad idea. I was just wondering about dedicating it to being sort of something like a clock with it plugged in all the time. Now I think maybe I can stop using my tablet for reading and use this instead.)
Click to expand...
Click to collapse
Sounds like you are having CM lockscreen widget withdrawal
Actually that seems like a job for Tasker. But it would be potentially messy. You'd need to:
1. Clear image in custom screensaver folder
2. Turn on wi-fi
3. Open weather/whatever app to update info
4. Take screenshot and save to custom screensaver folder
5. Close app
6. Turn off wi-fi
At that point when the Nook goes to sleep the info will be displayed on the lock screen. The question is whether Tasker can wake up the Nook and repeat this at desired intervals when you're not using it.
Also, have a look here for something along the same lines. Maybe you'll get an idea.

Ironically on my phone and tablet I keep it really simple. It's just that the eInk screen of the Nook can essentially be "always on" so to speak without draining the battery like mad (since it would only actually need to wake up every half hour or so for a frequent update schedule.)
But, all that said, it just doesn't sound like this is really worth all the effort. I guess I'm actually more used to newer versions of Android mostly rather than CyanogenMod specifically as they just have more power in what these things can do. With the Nook -- even unlocked and opened up -- it really sounds like the amount of time and effort required to even remotely approach such a thing is orders of magnitude higher. Well, that's fine. I had initially thought that I might maybe just use it as some sort of really neat "smart clock" type thing (at $35-ish on eBay you won't find many clocks that could come close to doing what an Android device could theoretically do) but in the end I don't think this is really all that realistic and definitely not worth the effort. On the other hand, now that I'm able to get more stuff actually running on it and open up its capabilities more I'm thinking I could maybe use this thing for something more akin to its original intended purpose: reading. From time to time I want my tablet to be able to do a bit more and I think this can do pretty well everything I care about beyond the basic reading stuff, so maybe I can stop carrying my tablet around all the time. (And for stuff like music I have a dedicated multimedia phone courtesy of eBay that's much better off really.)

Related

[Q] Syncing apps to multiple devices

I just bought a Xoom tablet and so far love it. I also own an Inspire 4G which is rooted and has many apps installed. I noticed soon after first sync that the apps from my phone are now on my tablet. I assume they are they apps listed in the Market which is ok except that it seems that they are "small screen" versions if there is such a thing. Is there a way to block or stop syncing to certain devices while allowing others? Am I clear whith this question? Do large format apps exist? Will the market auto download the correct version of the app depending on the device?
Just started to get up to speed with Android on my inspire, now comes another learning curve!!!!
Thanks in advance.

For most apps, there is only one version which the author can update to include our tablet (16:10) format. It's not that "small" versions are being downloaded, it's just that the version doesn't yet take full advantage of the extra screen size on our tablets. It's worth searching though, because some apps may have a larger (or tablet-specific) version abailable. Or, you may find another developer has a similar app optimized for the tablet. But, for the most part, the apps come in one flavor and as the author has time (or need), they can/will update the app for Honeycomb support.
Hope this helps to answer at least part of your question...not sure about stopping the process once it has started. I know that the first time you setup your account on some android devices, they will start downloading any apps you have in your library. My Xoom didn't though... Probably because I canceled the initial setup purposely then did it manually later. Doing it manually will bypass the app download as I recall.

As always... Great support on this community driven site!!! Thanks.
I suppose I will next look to perhaps rooting, although, as yet I see little need. Haven't noticed the bloatware that so burdened my Inspire4G.

I think there is also a "compatibility" setting on the Xoom that you can uncheck...in Applications??? that will allow the apps to show full screen, though they may be jaggy. Search for it...it might work for some of your "Must Have" apps=win!
Also, the market should show you a tablet specific selection of apps.
Good luck.

[Q] Going after minimalistic set of programms/feature on N7

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

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.

Cobwebs growing on Windows phone 8 blogs and forums

At least with windows 7.x you could switch ROMs and side load useful apps, with this safeboot thing and Microsoft's lame attitude to give us more of the features and apps that we want it's no wonder why Windows Phone 8 fourms and blogs are so boring. Way to go Microsoft.

Agreed. I used to come here every day but, now it's once a week (kind of how it was on PPCgeeks.com). No roms, No interop unlocks, no unlocks period.
If you want more discussion about WP8, I suggest going to WPcentral.com...It's pretty active over there...
I really wish a hack of some type would hit, this is getting old. I just want my custom colors back (like I have with WP7).... Advanced Config I miss you !!!

Nobody has been able to find an exploit yet , but I don't really mind lack of activity in forms though as long as cobwebs don't settle upon the entire ecosystem itself we'll be fine

DavidinCT said:
Agreed. I used to come here every day but, now it's once a week (kind of how it was on PPCgeeks.com). No roms, No interop unlocks, no unlocks period.
If you want more discussion about WP8, I suggest going to WPcentral.com...It's pretty active over there...
I really wish a hack of some type would hit, this is getting old. I just want my custom colors back (like I have with WP7).... Advanced Config I miss you !!!
Click to expand...
Click to collapse
Yea I agree that WP Central has lost more action going on but it's all the same stuff; I mean how many reviews of itsdagram, Facebook, Angry Birds and Skype can one handle before they get bored.
I always use to wonder why XDA turned into Android forum almost over night; now I know why its thanks to Microsoft. I feel sorry for Nokia though they took a big risk and now MS is being stubborn.

sinister1 said:
Yea I agree that WP Central has lost more action going on but it's all the same stuff; I mean how many reviews of itsdagram, Facebook, Angry Birds and Skype can one handle before they get bored.
I always use to wonder why XDA turned into Android forum almost over night; now I know why its thanks to Microsoft. I feel sorry for Nokia though they took a big risk and now MS is being stubborn.
Click to expand...
Click to collapse
Agreed, it's the same *****ing over there sometimes. Don't get me wrong, it's a good site if you want new and useful Windows Phone news. This site used to be a WM haven, just like PPCgeeks was. As that is all there was at the time, we had WM and BB...they were all mainly used by business people or hackers like ourselves.
WP7.x was pretty hackable after a while (with custom roms for most phones and interop unlock for about 90% of the models) so it was pretty active but, now with everyone moving to WP8 (ex WP7 users and converts) and No hacks yet, it's slowed down to almost nothing.
Android is mostly hackable and most phones have or NEED a custom rom, so this became a haven for Android users. And for now, as long as they are not going in this area and trolling, there is no issue with it or at least, I don't have an issue with it.
I do think it's a matter of time, they will find a exploit in WP8. I know why MS locked it down, once WP7 was hacked, it opened the doors for the pirates and some people took advantage if it. Sure there was some cool underground apps but, it just opened the system for the pirates. They wanted to lock down WP8 to make the higher end DEVs come and create the apps and games people want, to grow the system.
Nokia was paid pretty well to make a change to WP and over all they are doing very well with it...and their market is growing.
I'm stil deciding if I am going to pick up the Lumia 928 or stick with my HTC 8X(full price, Not giving up my unlimited data)....Hmmmmm... I just wish I could use Advanced Config to get my custom tile colors back

^stick with 8x at least till Nokia world sometime in September because surprises are on its way

Personally I like the very secure nature of my windows phone, I have rimmed more than my share of devices over the years, so its kind of refreshing to k ow this nuts hard to crack. Nokia did take a big risk but I think its been good for both companies. Nokia has done well with exclusive apps in a starved market and there devices are aimed well at a growing group of android overloaded users. With apps like tumble, netflix, Hulu and others coming over the devices are getting more main stream support and with time that will pay good dividends too. All in all I have found little reason to "root" this device other than for the hell of it. They come pretty lean on apps out of box. The biggest thing people seem to be trying to do is get tethering to work without paying out to a carrier for it. Personally if that's basically the reason your wanting to rom so bad, go back to android its far easier get going. I ramble now though, to sum up phone runs great unrommed, clean eco system and very secure setup makes for an all around pleasant device. I think special rimming is more or less unneeded for these devices. Been running unrommed windows mobile 7 and 8 now for about two years collectively. Have android tablets all rommed and a s3 rommed as a backup device.
Sent from my RM-878_nam_usa_100 using XDA Windows Phone 7 App

Meh... I considered WP7 without hacks to be nigh-unusable, even though I stuck with a stock ROM. No way to have apps open files automatically, for example (but I could manually add the registry entries, and could write apps that knew how to handle them). No way to access the filesystem (but I could sideload Kindle ebooks using homebrew file managers). No way back up app data or messages (except with homebrew). Minimal control of theming (as a class, this was one of the biggest homebrew categories). No real control over multitasking (I like that the default behavior is so conserving of battery life, but sometimes I don't *want* Puzzle Quest 2 or Fruit Ninja to have to go through its entire launch process just because I switched tasks or let the phone sleep for a bit!). Severe limit on sideloaded apps (I have over 30 of them, counting small utilities that that I developed, and not counting outdated versions, redundent apps, or anything else I removed). No listener sockets (though this didn't require a very fancy hack). No C++ code reuse (same as the server sockets). No way to tell how much space each app was using (but there's a homebrew for that).
WP8 fixes many of the worst problems. We can now register filetype handlers (though Kindle still doesn't register .MOBI or .PRC, so no more sideloading my ebooks for now...), use native code (with restrictions, but it's better than the default on WP7), and theme our phones (well, a litttttle bit more than before; still not enough). They added some much-requested features (SMS backup, variable text size, ability to control the browser app bar at least a bit, WiFi on while sleeping, Skype integration) and of course the change in OS brought many other improvements (multi-core, removable SD cards, higher resolutions, etc.). However, it still has some big problems of its own. True multitasking is still very limited. Data backup is still iffy. Still no filesystem access (or ability to do anything outside an app sandbox except the official Settings tools). Still very limited sideloading.
I promise you, though, people are working on it. I'm one of them, and several of the other names you know from WP7 hacking are as well.

People like GoodDayToDie & netham45 make the windows forums so much fun to follow

nikufellow said:
^stick with 8x at least till Nokia world sometime in September because surprises are on its way
Click to expand...
Click to collapse
Yea but, I am on Verizon....After a release of a model it will take 6 months for Verizon to get a phone that is almost outdated on release.
The 8X is so limited on space that it's driving me nuts, If I find app or game I want to try, I have to uninstall a Paid app to install it. It's getting too old. 8X on format is 11.5gb and the Lumia 928 is 23.5gb, a little over double the space might be worth it, depending on what I can get it for, of course.

The blogs are dead because places like XDA that centralize around modding your phone to improve performance isn't necessary when WP8 software already performs flawlessly. Go to blogs like WPCentral and the Windows Phone community is alive and well swapping out our black Lumia shells for yellow and talking about games and apps. Pretty much doing what we should be doing on a phone, not repairing phones that came broken.

Flawlessly? Ahahahahaha
Still no app data backup machanism.
Still no custom themes.
Still no way to sideload XAP files (unless they are "company apps") without a PC.
Still no filesystem access.
Still no way to control the permissions an app has (what if I want to use the app, but don't want to give it access to my camera?)
Still no way remove "Settings" apps.
Still no way to do true multitasking (not the restricted and often crippled things that the official APIs call multitasking).
Still no way to overwrite file associations (you can choose them when opening a file that multiple apps claim to support, but that's it).
Still no way to change the default browser or email client or dialer.
Still no way to install apps to the SD card.
Still have only limited access to Bluetooth.
Still no way to browse, much less edit, the registry.
Still no way to sideload large numbers of (non-"company") apps.
...
Seriously, go look at the list of things that are possible with WP7 homebrew (never mind WinMo or Android or iOS), and then see how many of them are possible with WP8 right now. It's a joke. MS added some (much needed) features, but also took away some things that I think are vitally important, and took away our ability to re-create them for the new OS... unless and until we break it as we have broken OSes in the past.
You imply that WP8 didn't come "broken" and therefore doesn't need modding? Bull.

I've been wanting to root/unlock my Lumia for one purpose only, sideloading my own developed apps. It's gruesome to try an app in the emulator all the time, but in a month that will be fixed with an AppHub account. And after that my real purpose for rooting/unlocking is gone.
Always fun to see what's possible on the unlocked device though, code-wise.
Sent from my Lumia 920 using Board Express

GoodDayToDie said:
Flawlessly? Ahahahahaha
Still no app data backup machanism.
Still no custom themes.
Still no way to sideload XAP files (unless they are "company apps") without a PC.
Still no filesystem access.
Still no way to control the permissions an app has (what if I want to use the app, but don't want to give it access to my camera?)
Still no way remove "Settings" apps.
Still no way to do true multitasking (not the restricted and often crippled things that the official APIs call multitasking).
Still no way to overwrite file associations (you can choose them when opening a file that multiple apps claim to support, but that's it).
Still no way to change the default browser or email client or dialer.
Still no way to install apps to the SD card.
Still have only limited access to Bluetooth.
Still no way to browse, much less edit, the registry.
Still no way to sideload large numbers of (non-"company") apps.
...
Seriously, go look at the list of things that are possible with WP7 homebrew (never mind WinMo or Android or iOS), and then see how many of them are possible with WP8 right now. It's a joke. MS added some (much needed) features, but also took away some things that I think are vitally important, and took away our ability to re-create them for the new OS... unless and until we break it as we have broken OSes in the past.
You imply that WP8 didn't come "broken" and therefore doesn't need modding? Bull.
Click to expand...
Click to collapse
If there is one thing I do not understand about the new SDK APIs, is why on earth an app can not register itself to open file formats reserved by the system. IMO thats the most retarded idea ever implemented in the history of computing. And to make the retarded thing completely retarded, they made it so most common files are handled by system apps, so you can not override the file association.
I am really wondering what is microsoft going to do about these things. If they really want a marketplace full of games, facebook, youtube and instagram apps, then they should stick to their current plan. WP will never get useful in a broad sense.
I hope the update this fall brings new stuff, otherwise the platform will die soon.

GoodDayToDie said:
Flawlessly? ... You imply that WP8 didn't come "broken" and therefore doesn't need modding? Bull.
Click to expand...
Click to collapse
Although I don't agree with much of his bill-of-particulars, I have to agree with GDTD's sentiment.
Probably, modders need to correct deficiencies. I'm down with MS or anybody else who steps up. I'm in no hurry to crack my OS open right now, though.
I am especially offended at Microsoft's pitiful PDF reader attempt. And some of the apps in the store make me squint. I want to see the author "Google" emblazoned on my YouTube app, not a third party dev. I sure hope MS is putting these apps under a microscope.

The joy of homebrew (and of a developer forum, like this one) is, even if your goals are different from mine, it's possible for you to make your own changes to the device. It's yours; you control it. That's what security *means*, or at least what it's supposed to mean: you (the owner) are in control of what happens.
Ever since the iPhone, though, the trend has been twoards more and more lockdown, taking control away from the device owner and branding this as "security". I don't like it, so I aim to break it. Ideally, we break it in ways that only work with a local attack; I don't want somebody else able to control my device (that really would be the opposite of security)... but I do want to control it myself!

Part of the problem is that there have been no updates in recent months. Portico came out, Nokia dropped some new firmwares last month. But largely, nothing has changed in WP8 since launch. Personally, I find that boring. Maybe I should have an Android phone on the side to keep me entertained with updates, but I find Windows Phone much more usable day-to-day.
It has been more than 6 months since the WP8 launch, and GDR1 didn't really add much. Microsoft should have planned to have GDR2 out by now, even if it meant postponing some features for GDR3. I think most of us would rather have small quarterly updates to WP8, rather than a massive upgrade once a year. It's starting to feel like WP7 and the Mango anticipation all over again, now that it sounds like WP8.1 might be delayed into 2014. Hopefully they come through with their vaporware enthusiast program to keep our attention in the meantime.

I agree with the OP. Cobwebs on this side of the section totally. A thread in a week may be? But there is something I often read on many forums. People who are happy (I know it's a very wide term) with their devices, I.e don't run into problems with their devices, see no need to lurk around. So actually, it is a good sign. It shows how well-thought after a WP device is.
And GoodDayToDie, even though I agree with everything u've noted down, I don't quite believe WP needs all of that.
Still no app data backup machanism. - Umm...Data Sense?
Still no custom themes. - Fair Enough, but again, WP IS NOT meant to be themed to the T
Still no way to sideload XAP files (unless they are "company apps") without a PC. - I believe this is for security reasons.
Still no filesystem access. - Why do you even want that when the system is running flawless, (yes the same word u scorned at.)
Still no way to control the permissions an app has (what if I want to use the app, but don't want to give it access to my camera?) - LOL! You gotta be kidding me right?
Android has the worst permission management I have ever seen in my adult life. Android gives wayyyyyyyyyyyyyy more information out than any OS out there.
Still no way remove "Settings" apps. Umm..u sure u want that?
Still no way to do true multitasking (not the restricted and often crippled things that the official APIs call multitasking). Multi-tasking is really good with WP8.
Still no way to overwrite file associations (you can choose them when opening a file that multiple apps claim to support, but that's it). - Fair enough, but not a deal breaker either.
Still no way to change the default browser or email client or dialer. - I believe you are again entering the territory of themeing, already replied above. Every OS comes with it's own email client. I don't see the point here.
Still no way to install apps to the SD card. - Fair enough. By far the best point in your list.
Still have only limited access to Bluetooth. - In what way?
Still no way to browse, much less edit, the registry. - Again, WHY? WHy mend it when it's not broken.
Still no way to sideload large numbers of (non-"company") apps - U can download the app(paid or otherwise) from the App store on your computer, put it on the SD card and say install from the Store App on the phone. Simple?

DataSense has nothing even remotely to do with backing up (and restoring) app data; where'd you get that idea? Vital feature that homebrew eventually made avaialble in WP7 but is missing in WP8.
"IS NOT meant" nothing! Somewhere under all that sandboxing and locked-down UI is a general-purpose OS running on top of highly capable hardware. It's "meant" to be whatever the owner fo the device *wants* it to be, including (in the case of many, many people if the popularity of WP7 homebrew apps is any sign) theming. Stop being an apologist for Microsoft; it's one thing to say "extensive theming wasn't implemented because other features were higher priority" but when you start trying to tell me that I'm not supposed to theme it, you seriously need to put down the Kool-Ade. Besides, the very claim is ludicrous to the point of disingenious; have you *seen* the WP8 ads? They all stress the customizability of the Start screen. To the point of suggesting you can "meet" a person simply through how they have their phone set up... those ads freaking scream "customize me!" Then you discover there's only a handful of pre-set colors, two background styles, and the ability to mess with the tiles; nothing else.
No, it is quite absolutely *not* for "security" reasons. Security means the owner of the device controlling the device's behavior. If somebody else (like, for example, the manufacturer of the device) is controlling its behavior, that is not security; it's lockdown. The sideloading restriction can only be called security if it's not your device but actually belongs to Microsft. Screw that. Besides, that argument makes no sense anyhow; if I can pay my $99 and sideload with a PC, why can't I sideload without one (or without paying)? The marketplace has DRM to mitigate piracy and that's a darn weak excuse to cripple a device anyhow.
When I can load my Puzzle Quest 2 savegames and other game progress and high scores, copy my PGP keychain, sideload my Kindle ebooks into the Kindle app (yes, this is possible on WP7), extract or replace the built-in audio files, and delete the junk which accumulates in the OS and uses up storage space (without hard resetting the device), then I will stop considering the level of filesystem access a problem. Until then, "running flawless" is quite worthy of scorn indeed.
Wow, I seriously question your reading comprehension. I never mentioned Android in this point, or anywhere else (except to point out that it has a lot of homebrew). But, for your information, the default permissions / capabilities handling in Android is just as broken as in WP8. The difference is that with Android, it is possible (CyanogenMOD did this, for example) to install apps without actually granting them all the permissions they ask for. On WP7, this wasn't properly possible yet, but I was working on a system to do it that hooked the app install process and allowed people to uncheck app capabilities they didn't want to permit.
Um yes, I'd like to remove the non-functioning Samsung apps (until they are fixed) that are taking up space on my phone's storage and making the Settings list longer. I can always re-install them if needed. Every other carrier or OEM app is removable; why should these get special treatment just because they have a field in their app manifest that says "install me in the Settings hub"?
Multitasking - true multitasking, where multiple apps can run at once - is nigh-nonexistent on WP8. Aside from things like audio background agents and once-every-30-minutes-you-get-a-few-seconds-of-CPU-time scheduled tasks, there basically isn't any multitasking (of third-party apps) at all. Fast app switching is *not* multitasking; every app aside from the main one is suspended, unable to do amything until brought into the foreground.
Changing file associations obviusly isn't a deal-breaker, or I wouldn't be using the phone... but definitely a problem. Windows has offered the ability to control file associations since at least Win95, and I think it was possible in 3.1 as well...
Changing the default browser and email client and calendar and dialer aren't "theming" by any conventional definition, but the point made above about theming stands anyhow: it's a matter of personalization. It can also be a matter of functionality (for example, the built-in email client can't handle S/MIME encrypted email at all and has no PGP integration). Or a matter of usability (I use folders a lot; it's a pain needing to expand a menu to get to them)! Or something else... the important point is that it should be possible. Every OS comes with an email client, but every OS except iOS (and WP) allows you to change the default email client, too. This isn't even hard to implement (the relevant registry keys were present on WP7, at least; carrying over the API to control them wouldn't have been hard at all); it's once again a case of Microsoft intentionally restricting what you can do with your phone. If I wanted a mobile OS designed by a control freak, I'd buy an iPhone...
Nothing more really needs to be said here, except that with filesystem access (create a symlink or junction in the apps folder, for example) this would be possible...
Many BT profiles, such as HID devices (for mice and keyboards), are missing from WP8. So far as I know, apps can't use the Headset profile either; the pseudo-turn-by-turn navigation on WP7 would give its instructions via the car's BT if possible, but Nokia/Here Drive must use the phone's speakerphone speaker instead.
When I can change default browser and text editor, create my own themes, enable features that a ROM shipped disabled (have you seen the thread by the guy who can't get visual voicemail?), sideload high-privilege apps (without paying for the privilege), and remove root certificates of CAs that I don't trust (in WP7, these were stored in the registry), then I will stop considering the level of registry access to be a problem.
If they're from the store, they aren't really sideloaded, just downloaded on a different machine. I'm talking homebrew, stuff that the isn't yet, or never will be, or *can't* be (because it breaks some policy of Microsoft's, or requires high privileges to work) put in the store. Besides, many of the most popular WP8 models don't have an SD card slot at all.

GoodDayToDie said:
Flawlessly? Ahahahahaha
Still no app data backup machanism.
Still no custom themes.
Still no way to sideload XAP files (unless they are "company apps") without a PC.
Still no filesystem access.
Still no way to control the permissions an app has (what if I want to use the app, but don't want to give it access to my camera?)
Still no way remove "Settings" apps.
Still no way to do true multitasking (not the restricted and often crippled things that the official APIs call multitasking).
Still no way to overwrite file associations (you can choose them when opening a file that multiple apps claim to support, but that's it).
Still no way to change the default browser or email client or dialer.
Still no way to install apps to the SD card.
Still have only limited access to Bluetooth.
Still no way to browse, much less edit, the registry.
Still no way to sideload large numbers of (non-"company") apps.
...
Seriously, go look at the list of things that are possible with WP7 homebrew (never mind WinMo or Android or iOS), and then see how many of them are possible with WP8 right now. It's a joke. MS added some (much needed) features, but also took away some things that I think are vitally important, and took away our ability to re-create them for the new OS... unless and until we break it as we have broken OSes in the past.
You imply that WP8 didn't come "broken" and therefore doesn't need modding? Bull.
Click to expand...
Click to collapse
The only thing I can agree with you on is the file system, bluetooth, and not being able to override the default apps associations (seriously, the default apps is the most retarded idea ever).

Can Glowlight 3 ROM be modified to work on original NST?

I've been thinking about how all these new apps are out now that would work great on my old NST if only it ran a more recent version of Android. I saw on the old l337 thread that the NST is confirmed to be able to run more adavanced versions, but that we'd have to pull the files from a phone or other, much more powerful device, rendering the resulting ROM pretty much unusable.
Until, that is, the Nook Glowlight Plus and 3 came along. The NG+ and NG3 run Android 4.4.2. 4.4 Android could mean being able to run apps like Overdrive and Libby, without workarounds. And that would be pretty sweet.
Now these are two different devices. I'm having a hard time finding data on the difference between the guts beyond the fact that the newer models have a higher DPI screen. I'd guess they have similar amount of processing speed to preserve battery life, though maybe more RAM.
I did a little googling, and I found this CM11 Mod but it looks like it it fizzled out after getting pretty close.
Do we think this can be done?

Was wondering about this the other day. There are an awful lot of NSTs floating around ebay for US$15 now. It would be fun to be able to breathe a little life into them, if only to use them for displays of calendars, to-do lists, or anything else you can do with more modern android apps

jptiger said:
There are an awful lot of NSTs floating around ebay for US$15 now.
Click to expand...
Click to collapse
The NST, NSTG and the first Glowlight used TI OMAP3621 processors.
The Glow2, 3, 4 use Freescale (now NXP) iMX6SL processors.
That's quite a difference.
I don't think that anything would be compatible.

jptiger said:
Was wondering about this the other day. There are an awful lot of NSTs floating around ebay for US$15 now. It would be fun to be able to breathe a little life into them, if only to use them for displays of calendars, to-do lists, or anything else you can do with more modern android apps
Click to expand...
Click to collapse
Oh, I'm going to promise not to look at ebay!!! Three devices are enough, even at that price. But it's very tempting. Too bad the NSTGs are rare as hens teeth and always high priced. Then there is a screen artifact issue. The one I finally got has three, but it's not too bad, I guess.
Other than watching movies or live TV (both of which, admittedly, are actually possible with the NST if you can stand it), it seems to me these devices are still wonderfully versatile. With a minimal installation of GApps you can have all the calendar displays you want, to-do-lists, etc. For some of these applications, there are still apps that work fine. For other uses (you dream it up) it's amazing what can be done with Tasker to create an app that looks like "the real thing". And while the learning curve for Tasker is a little steep, baby steps and lots of online help and examples are available.
The one clear drawback is almost anything that requires a login. The fact that Overdrive has not yet been hacked to address this issue is probably due to a lack of interest from a person with the proper expertise (not me). But really, selecting a library book on Opera Mobile from your local library? I'd sooner slit my wrists. Books can still be downloaded to a PC and then transferred to the NST via Adobe's software (or you can get around the whole DRM issue if you wish). And, you can get mobi format books from most libraries now and they will still magically appear in your Kindle app
That said, having flashed a Nook Tablet with CM 11 (KitKat), I can attest that there are still issues with that less-old Android version. For example, you can't view XDA properly in any browser. You have to go back to an earlier skin which has tiny print and is most annoying. In fact you can't get to some sites at all with any browser. And the OS returns SSL errors for some operations with other apps. So KitKat is no panacea. Even so, I like my Nook Tablet running CM 11. It's an 8 GB version and so has limited RAM and storage. Therefore I have scaled down my usual apps to some essentials and things it is really good at. In fact, it has fewer apps on it than my NST!
Every one of those NSTs on ebay is a treasure. But I'm not going to look!!!!

Renate NST said:
I don't think that anything would be compatible.
Click to expand...
Click to collapse
I meant as fas as kernel, various hardware libraries.

nmyshkin said:
Other than watching movies or live TV (both of which, admittedly, are actually possible with the NST if you can stand it), it seems to me these devices are still wonderfully versatile. With a minimal installation of GApps you can have all the calendar displays you want, to-do-lists, etc. For some of these applications, there are still apps that work fine. For other uses (you dream it up) it's amazing what can be done with Tasker to create an app that looks like "the real thing". And while the learning curve for Tasker is a little steep, baby steps and lots of online help and examples are available.
The one clear drawback is almost anything that requires a login. The fact that Overdrive has not yet been hacked to address this issue is probably due to a lack of interest from a person with the proper expertise (not me).
Click to expand...
Click to collapse
Thanks for the thorough response! I didn't realize you could do so much! I was envisioning having three mounted on walls in various places in my apartment, one with an interactive Google calendar, one with my to-do list from Any.do, and one with a local transit app that shows if there are delays on specific trains etc. (though I guess that one might wait until we're all using public transit again...) I've never used Tasker before, do you have any suggestions of resources or guides on getting it to replicate any functionality like this on an NST?
nmyshkin said:
Every one of those NSTs on ebay is a treasure. But I'm not going to look!!!!
Click to expand...
Click to collapse
Good luck! Save your money and vicariously help me do stuff with them?

jptiger said:
Thanks for the thorough response! I didn't realize you could do so much! I was envisioning having three mounted on walls in various places in my apartment, one with an interactive Google calendar, one with my to-do list from Any.do, and one with a local transit app that shows if there are delays on specific trains etc. (though I guess that one might wait until we're all using public transit again...) I've never used Tasker before, do you have any suggestions of resources or guides on getting it to replicate any functionality like this on an NST?
Click to expand...
Click to collapse
There is only one version of Tasker that will run on the NST/G (check your PM). It is designed to run in the background and execute tasks from shortcuts on the home screen or automatically start a series of tasks based on some trigger (time of day, opening a specific app, connection to WiFi, etc.). I originally used it to automatically start WiFi for apps that needed it. This is definitely a "baby step" idea. I don't use Tasker as a background service any longer. There is a companion app called AppFactory which takes your Tasker routines and converts them into stand-alone apps that anyone can run (with the caveat that either GApps must be installed or else two small Maps library files would need to be copied onto the device--actually this is a dependency for Tasker itself also). You can see many examples of "apps" I have created in this fashion in the last section of this forum. You design your own GUI to fit the NST/G screen. Tasks can vary from a simple activity call to website data scraping and massaging (definitely advanced) and more.
AppFactory will not run on the NST/G. It requires Android 2.2. I have a KitKat device which will run both the ancient version of Tasker and also AppFactory, so after I finish designing and testing the routines on the NST I move all the files over to the KitKat device and compile with AppFactory. The resulting app can be installed on the NST and behaves just like any other app (and does not require the presence of Tasker to run).
A lot of patience is required to get things right, especially if you want a full-screen GUI since Tasker seems to hate screen edges and when you edit a screen containing a near-full-screen image it tends to resize it a little smaller, throwing off other elements. Fixing this requires hand-editing the coordinates in the xml files which describe the scene elements. Also, because the file structure on the NST is not the same as on a KitKat device, references to images have to be edited by hand before (or after) moving files to the second device to compile. For example, "/media/" might need to be changed to "/storage/external_SD/Pictures/" or similar. Also, the touch screen on the NST is not always as responsive as we might like.
Finally, there is one one last fly in the ointment, so to speak. Tasker will not install on FW 1.2.2 for some reason unless it is resigned. When it is resigned, it ceases to interact properly with plugin apps (things like RotationLocker, or Minimalistic Text, as examples). The compiled apps will work properly, but testing on the NST is problematic if you are referencing plugins. On FW 1.2.1 everything works properly. Since I have three devices (gulp) I kept one on FW 1.2.1 to help me with this issue.
There is a Tasker Wiki with many examples, but just Googling will yield all kinds of things. There is a guy (Hollywood Frodo) who created all kinds of videos from the basic to the exotic and I found some of those very helpful. Finally, there is a Tasker Google group where--to judge by my personal experience--no question is too stupid!

My rooted unregistered Nook Simple Touch chews battery like crazy

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.

Database Users

welcome