Related
HTC has released a new ROM for Orange customers.
It can be found on the HTC website.
good find, now if only htc would be so kind as to give a changelog
Could anybody who has downloaded this tell us what the major differences are please. Don't want to be bothered to download it if it tries to fix a problem i haven't got - if it aint broke etc.
peterc10 said:
Could anybody who has downloaded this tell us what the major differences are please. Don't want to be bothered to download it if it tries to fix a problem i haven't got - if it aint broke etc.
Click to expand...
Click to collapse
Same here, I want to know what changes it will make, No point doing all that hard work for a minor bug that I don't have.
Thanks.
peterc10 said:
Could anybody who has downloaded this tell us what the major differences are please. Don't want to be bothered to download it if it tries to fix a problem i haven't got - if it aint broke etc.
Click to expand...
Click to collapse
Same here, I want to know what changes it will make, No point doing all that hard work for a minor bug that I don't have.
Thanks.
Well I've downloaded and installed the update - I'm one of those "strange" fellows who assumes that an update should just be applied as it will "update" things.
What have I found:
No real differences to anything at all. I did have a bug whereby the browser would start turning itself off randomly (both WiFi and 3G and with 1 or more tabs open & many different sites so no idea what caused it - happened both straight after a reboot and also when been left on for a few days) This no longer seems to be happening.
My main bugbear with it now is that I've found that I can't see all the programs that I used to have on the Store. I can see Twidroid free but not Twidroid Pro (which seeing as I've paid for it I'd rather like to download again!) I also can't see Space Physics - again I can see the lite version but I've paid for the full game and that's not showing anywhere.
I can see other programs that I've previously purchased & able to download (CoPilot, Retro Defence) but it's irritating in the least to not get the full versions of other programs I've paid for already.
m_memmory said:
Well I've downloaded and installed the update - I'm one of those "strange" fellows who assumes that an update should just be applied as it will "update" things.
What have I found:
No real differences to anything at all. I did have a bug whereby the browser would start turning itself off randomly (both WiFi and 3G and with 1 or more tabs open & many different sites so no idea what caused it - happened both straight after a reboot and also when been left on for a few days) This no longer seems to be happening.
My main bugbear with it now is that I've found that I can't see all the programs that I used to have on the Store. I can see Twidroid free but not Twidroid Pro (which seeing as I've paid for it I'd rather like to download again!) I also can't see Space Physics - again I can see the lite version but I've paid for the full game and that's not showing anywhere.
I can see other programs that I've previously purchased & able to download (CoPilot, Retro Defence) but it's irritating in the least to not get the full versions of other programs I've paid for already.
Click to expand...
Click to collapse
I wouldn't worry about that. It sometimes happens when a carrier releases an update. They need to 'validate' it with the big G before it gets access to protected/paid apps...
m_memmory said:
Well I've downloaded and installed the update - I'm one of those "strange" fellows who assumes that an update should just be applied as it will "update" things.
What have I found:
No real differences to anything at all. I did have a bug whereby the browser would start turning itself off randomly (both WiFi and 3G and with 1 or more tabs open & many different sites so no idea what caused it - happened both straight after a reboot and also when been left on for a few days) This no longer seems to be happening.
My main bugbear with it now is that I've found that I can't see all the programs that I used to have on the Store. I can see Twidroid free but not Twidroid Pro (which seeing as I've paid for it I'd rather like to download again!) I also can't see Space Physics - again I can see the lite version but I've paid for the full game and that's not showing anywhere.
I can see other programs that I've previously purchased & able to download (CoPilot, Retro Defence) but it's irritating in the least to not get the full versions of other programs I've paid for already.
Click to expand...
Click to collapse
Thanks for the reply, frankly I haven't come across the bug on my browser, which goes to say, I won't need this update.
Shahin
I have just installed this and there are no real differences except they have added a 4x4 (i.e. the whole screen) People widget, and increased the size of the thumbnails on the People widget.
Tristan
Applied this update. Readme did not work. Now my headphone connection autosense is fsuked. HTC still haven't confirmed the changelog.
Hi,
I am new here and I am Hichjacking this thread, as my problem is in regards to the ROM Update on Orange.
As someone posted in this thread earlier, I do have the same issue that some of my paid apps are no longer available for me. ie Silent time, my backup pro.
I was able to get my MyBackup Pro online, however Silent time pro is not available. Is this also probably because its not approved for the new ROM update yet, although its not nearly 2 weeks old.
I can live without the other ones, but I loved Silent time Pro.
Can anyone help me and shed some light?
Markus
HI all, this past weekend Kies popped up with a notification that there was a firmware upgrade for my Galaxy S. I immediately downloaded and installed it, I guess a newbie mistake. When completed I found that all my apps vanished and my settings went back to out of the box state. Though annoying I spent much of Saturday morning trying to get my phone back to where I had it before the update. The issue now though is that when I log into the market I find I am unable to download certain apps, I get to the install button on the phone then I get an error message "file not found". This is troublesome as there are a few apps that I had before the upgrade that I can no longer install, including paid apps, (examples Pandora, Pure Calendar) nor am I able to install certain new apps. I read that the market will no longer display protected content after this upgrade. I spoke to Samsung who told me to take the phone back to the Bell store. Bell told me to call Samsung as it is a firmware issue
Has anyone else experienced this, and does anyone know of a solution to the problem.
Thank you
tori60 said:
HI all, this past weekend Kies popped up with a notification that there was a firmware upgrade for my Galaxy S. I immediately downloaded and installed it, I guess a newbie mistake. When completed I found that all my apps vanished and my settings went back to out of the box state. Though annoying I spent much of Saturday morning trying to get my phone back to where I had it before the update. The issue now though is that when I log into the market I find I am unable to download certain apps, I get to the install button on the phone then I get an error message "file not found". This is troublesome as there are a few apps that I had before the upgrade that I can no longer install, including paid apps, (examples Pandora, Pure Calendar) nor am I able to install certain new apps. I read that the market will no longer display protected content after this upgrade. I spoke to Samsung who told me to take the phone back to the Bell store. Bell told me to call Samsung as it is a firmware issue
Has anyone else experienced this, and does anyone know of a solution to the problem.
Thank you
Click to expand...
Click to collapse
Some people suffered market problems after upgrading to the UK-released JM1 last week. Apparently Samsung has to notify Google that they released an official update, so that Google allows access to paid and copy protected apps for that firmware. It took a couple of days for everyone to see everything over here. Maybe you just have to wait a bit (?)
Same happened here in Australia.. It was fixed the next day. I called Samsung to complain about it (when it was still happening) and was told that there was nothing they could do (which seemed like rubbish to me)..
If you are updating to a unsupported (beta) fw, make sure you install a rom or replace your build.prop file with a supported fw file.
Hi my phone is a month old now, everything is stock..no mods so far..I am having multiple problems with my phone.
- I cannot download anything from Market..it starts download and then 'download unsuccessful'
- FM radio never worked for me, not even after manually tuning it.
- I am not able to use wifi..it just says 'obtaining address...'
I did a factory reset yesterday and after that I was able to download 2~3 apps from Market..but today I am facing the same issue again.
Please help me guys..
Thanks guys for the help, it turns out that the issue was exactly what you said, but maybe more to the point, my own impatience.
Thanks again
sturmeh said:
If you are updating to a unsupported (beta) fw, make sure you install a rom or replace your build.prop file with a supported fw file.
Click to expand...
Click to collapse
I am on the Captivate running the beta I897UCJH2 firmware. I have market issue with some apps (e.g., Asphalt 5 HD, Fandango, and G4Tv) not showing up. I tried your method of copying over the build.prop file from the official I897UCJF6 firmware release. Even rebooted after doing that. The missing apps never showed up, so I reverted back to the JH2 build.prop file. Any other suggestions to fix my issue?
P.S. - Spoke too soon. This does work. Someone suggested clearing Market cache, followed by reboot, and then installing and reinstalling a couple of apps. And that did the trick.
from what i can gather it seems to be related to a location issue, as in certain apps will not show up for some countries and other apps will, etc.
so if you load firmwares from different geographic location the market is filtering what it allows/not allows bassed on the rom firmware location.
it'll be great if we can remove that filter and have it show everything online.
the work around that i do is find and download the apps via browser, instead of market
also avoid the barcode scanner downloads, which just launches the market app
AllGamer said:
from what i can gather it seems to be related to a location issue, as in certain apps will not show up for some countries and other apps will, etc.
so if you load firmwares from different geographic location the market is filtering what it allows/not allows bassed on the rom firmware location.
it'll be great if we can remove that filter and have it show everything online.
the work around that i do is find and download the apps via browser, instead of market
also avoid the barcode scanner downloads, which just launches the market app
Click to expand...
Click to collapse
Are you saying there a site where I can get the all the apks for these missing apps downloaded by bypassing the market? I have never run across it so far. Every one of the solutions so far has the phone launching the market app at some point, which fails, as the apps are not listed or downloadable there. The apps I am talking about are all free and should be legally able to be sideloaded, but how?
Hi,
Anybody seen any actual implementations of a more secure permissions model for Android? That is, patched and compiled a kernel, used it in a custom ROM or anything like that?
A little background information:
The very first time, I tried to install an app from the Market, I was stunned to find the lack of options, in regard to which permissions I wanted to grant a certain app, when installed. It is all or nothing - "That can't be true?!", I said to myself, so I went looking for a way to control, which permissions were granted to an app, only to find out, that it's simply not possible (yes, I know you can hack the .apk, but that's besides the point here, and not very user friendly).
The solution (to be?):
While searching the net on this issue, I came across a paper written by a couple of Software Engineers, which seems quite interesting, and just about the perfect solution for my problem. However, I can't find any actual implementations on this - whether the authors didn't make any, or just didn't release it, I cannot say.
The paper I'm referring to, can be found here:
http://recluze.files.wordpress.com/2007/06/and-usage-nauman10.pdf
And another paper here:
http://www.list.gmu.edu/zhang/pub/asiaccs10-apex.pdf
After reading the papers, I went "OMG, that's freaking awesome! Where can I get that?" - So does anyone know something about this? Anything? Work-in-progress perhaps?
I'm very attracted to Android, being the number one open source mobile operating system, but the lack of security features is holding me back somewhat.
There's already posted an issue about this on Google Code - I urge everyone to go and put up a vote for this issue (login, and scroll to the bottom), in order to put some focus on it.
http://code.google.com/p/android/issues/detail?id=6266
In the meantime - anybody know of any patches?
Best regards,
Michael
I have read that it's possible to use google books on the NST (or NTG) but i can't find it in the market place. and every time i try and side load the apk i get INSTALL_FAILED_OLDER_SDK. I downloaded google play books 2.3.5 apk which is supposably built for 2.1. I thought the NST/NTG was on 2.1 (or is it 2.2?) so im curious why this doesn't work... anyone care to comment?
If i just have the wrong version please let me know the correct version to use.
You can try apktool-ing the apk and see what version it specs in AndroidManifest.xml.
You could modify the version and see if it crashes.
We're running Eclair, 2.1, API level 7 on the Nook Touch.
Any luck OP?
EDIT:
Tried this one: http://www.iapktop.com/google-play-books-2-4-3.html since it said compatible with 2.1, but I had no luck.
Then I tried this one: http://www.iapktop.com/google-books-1-4-5.html and it looks to be working! I saw my library in the window and I have it downloading one of my books now for reading to test.
EDIT2: AAaaaaand... works. Perfectly I might add. The only thing that doesn't work is the side buttons don't switch pages. I think because they are bound to PAGE_NEXT or something. Changing them to Right and Left arrow should do it.
EDIT3: Yep. A quick change to the keylayout lets me page with the right hand buttons. It does break the ability to page in the stock reading app though with those buttons. For now I'm leaving it with paging in Google books with right side buttons and paging in Nook with left side buttons. I'll probably go all in later.
What I did was edit /system/usr/keylayout/TWL4030_Keypad.kl and switch RIGHT_NEXTPAGE to DPAD_RIGHT and then switched RIGHT_PREVPAGE to DPAD_LEFT.
Hopefully that makes sense. If not I can probably make it easier for you by pulling the file itself, but I figure I'd try to "teach a man to fish."
Dynamic button remapping; getting rid of page-turn animation
(Interested lurker speaking. I don't have a NST, but a rooted Sony PRS-T1, which is similar, but running Android 2.2. Please take what I say with a grain of salt.)
The latest version of Google Play Books that does not require 3D hardware (for its carousel view and its page-turn animation) and that is available for older Android versions appears to be version 1.5.4.
I'm using that version on the PRS-T1, but was annoyed by its flickering slide animation when turning pages. If you're comfortable with the Android SDK and apktool, here's a hack I did to remove that animation:
mobileread.com/forums/showthread.php?t=187741
The problem of different Left/Right key bindings for different apps plagues the PRS-T1 as well. This led me to look for a solution to remap these buttons dynamically, depending on which app was currently running in the foreground. Here's my hack for the PRS-T1, which a semi-experienced developer could port over to the NST. I'd be happy to accept patches.
mobileread.com/forums/showthread.php?t=187054
github.com/altruizine/pgdn
(Sorry for not posting direct links – I'm not allowed to post links yet.)
altruizine said:
(Interested lurker speaking. I don't have a NST, but a rooted Sony PRS-T1, which is similar, but running Android 2.2. Please take what I say with a grain of salt.)
The latest version of Google Play Books that does not require 3D hardware (for its carousel view and it page-turn animation) and that it available for older Android versions appears to be version 1.5.4.
I'm using that version on the PRS-T1, but was annoyed by its flickering slide animation when turning pages. If you're comfortable with the Android SDK and apktool, here's a hack I did to remove that animation:
mobileread.com/forums/showthread.php?t=187741
The problem of different Left/Right key bindings for different apps plagues the PRS-T1 as well. This led me to look for a solution to remap these buttons dynamically, depending on which app was currently running in the foreground. Here's my hack for the PRS-T1, which a semi-experienced developer could port over to the NST. I'd be happy to accept patches.
mobileread.com/forums/showthread.php?t=187054
github.com/altruizine/pgdn
(Sorry for not posting direct links – I'm not allowed to post links yet.)
Click to expand...
Click to collapse
That's awesome! I only just got this device last night so haven't got too far into hacking it, but I have plenty of other Android experience. I'll see if I can replicate.
Sent from my HTC One S using xda premium
So close!
ViViDboarder said:
Then I tried this one: .iapktop.com/google-books-1-4-5 and it looks to be working! I saw my library in the window and I have it downloading one of my books now for reading to test.
EDIT2: AAaaaaand... works. Perfectly I might add. The only thing that doesn't work is the side buttons don't switch pages. I think because they are bound to PAGE_NEXT or something. Changing them to Right and Left arrow should do it.
Click to expand...
Click to collapse
Thank you so much for posting this!
I installed the1-4-5 apk without incident and all my books synced beautifully, including where I left off in them. I was pretty sure I was home free at this point but I've found that the actual content of the books never loads. I get the spinning loading icon off into infinity.
This is the way for all my books. Looks for all the world like it should work fine but just never loads the actual content.
I've tried a system reboot, scanning around between pages, fussing with text size/line spacing and same outcome.
I tried the 2-4-3 apk and got a parsing error when i tried to open the package.
This is so close I can taste it. Any ideas anyone?
Thank you
Update:
I found that if I toggled on "Original pages" in the book options the content would load. After I did that once I could switch back to "flowing text" and adjust as needed.
Update 2:
I still intermittently have issues with book content loading. Probably once per day the loading icon displays indefinitely. The flowing text/original pages workaround I listed before was likely a flook, I haven't been able to find a way to reliably get around this problem. It's terribly annoying.
Update 3:
I tried using the refresh option on the library view prior to loading my book this time and it popped up immediately afterward. I'll continue to experiment with this to see if it works consistently.
Update 4:
That's unreliable as well. There doesn't seem to be any good way to prompt my book to actually load the content of the book. Super annoying.
Version 1.0.16
jorgenric said:
Thank you so much for posting this!
I installed the1-4-5 apk without incident and all my books synced beautifully, including where I left off in them. I was pretty sure I was home free at this point but I've found that the actual content of the books never loads. I get the spinning loading icon off into infinity.
This is the way for all my books. Looks for all the world like it should work fine but just never loads the actual content.
I've tried a system reboot, scanning around between pages, fussing with text size/line spacing and same outcome.
I tried the 2-4-3 apk and got a parsing error when i tried to open the package.
This is so close I can taste it. Any ideas anyone?
Thank you
Update:
I found that if I toggled on "Original pages" in the book options the content would load. After I did that once I could switch back to "flowing text" and adjust as needed.
Update 2:
I still intermittently have issues with book content loading. Probably once per day the loading icon displays indefinitely. The flowing text/original pages workaround I listed before was likely a flook, I haven't been able to find a way to reliably get around this problem. It's terribly annoying.
Update 3:
I tried using the refresh option on the library view prior to loading my book this time and it popped up immediately afterward. I'll continue to experiment with this to see if it works consistently.
Update 4:
That's unreliable as well. There doesn't seem to be any good way to prompt my book to actually load the content of the book. Super annoying.
Click to expand...
Click to collapse
Here is an older version that I found somewhere on the web. It is version 1.0.16...I installed it and it seems to work excellently so far. The bug where version 1.5.4 often never loads the book doesn't seem to be present. :cyclops:
finitary said:
Here is an older version that I found somewhere on the web. It is version 1.0.16...I installed it and it seems to work excellently so far. The bug where version 1.5.4 often never loads the book doesn't seem to be present. :cyclops:
Click to expand...
Click to collapse
I may have to give this a shot. I am frequently annoyed with this bug. Thankfully the books I'm reading actually fit perfectly on the screen when viewing the scanned versions.
Just wanted to bump and see if you're still getting good results with that version of Google Books. I haven't switched yet (started reading something on Kindle) but I'm about to start a new book on Google Play.
Seems to work!
finitary said:
Here is an older version that I found somewhere on the web. It is version 1.0.16...I installed it and it seems to work excellently so far. The bug where version 1.5.4 often never loads the book doesn't seem to be present. :cyclops:
Click to expand...
Click to collapse
I just loaded up the 1.0.16 version and the book loaded right up where as 10 minutes ago it stubbornly refused. I'm not going to get my hopes up yet but I'll try and remember to give an update after some more use. Thanks for the post!
goodereader.com has version 1.5.2 for download. Worth a try.
Success!
jorgenric said:
I just loaded up the 1.0.16 version and the book loaded right up where as 10 minutes ago it stubbornly refused. I'm not going to get my hopes up yet but I'll try and remember to give an update after some more use. Thanks for the post!
Click to expand...
Click to collapse
Seems to be working consistently with this version of reader.
jorgenric said:
Seems to be working consistently with this version of reader.
Click to expand...
Click to collapse
Awesome! Thanks for the update.
Finally got around to rooting my Nook Touch, as I wanted to utilize the syncing feature of Google Play Books. They now let you upload your own epub files to your library, and I have been reading mainly on my phone or Nexus 7 as a result.
Unfortunately it looks like the 1.0.16 version does not support user uploaded books. All of my purchased books appear, but none of the many I uploaded. 1.5.2 and 1.5.4 both have the book not loading issue.
Anyone have any thoughts or other versions to try? Would love to get this working.
urinsane said:
Finally got around to rooting my Nook Touch, as I wanted to utilize the syncing feature of Google Play Books. They now let you upload your own epub files to your library, and I have been reading mainly on my phone or Nexus 7 as a result.
Unfortunately it looks like the 1.0.16 version does not support user uploaded books. All of my purchased books appear, but none of the many I uploaded. 1.5.2 and 1.5.4 both have the book not loading issue.
Anyone have any thoughts or other versions to try? Would love to get this working.
Click to expand...
Click to collapse
I'm in the same boat. I can see my uploaded library in play but it's not loading the book. I think it has loaded the book but it's not ending the load part of the function. Just guessing.
Hope we can get this worked out.. This would help me tremendously being able to read on the N2T and sync across my computer and Nexus.
*update For some strange reason this started working for about a minute. Book I'm reading synced right to the exact page. Exited and went back in to see if it would still work and it went back to the looping circle page. It's so close I can taste it.
*update Managed to get 1.5.2 working but only in offline mode only. I've noticed the more pages the book has the slower it is to load, but it's loading none the less 9/10 times. Progress, so it is possible to get this working.
ForSquirel said:
I'm in the same boat. I can see my uploaded library in play but it's not loading the book. I think it has loaded the book but it's not ending the load part of the function. Just guessing.
Hope we can get this worked out.. This would help me tremendously being able to read on the N2T and sync across my computer and Nexus.
*update For some strange reason this started working for about a minute. Book I'm reading synced right to the exact page. Exited and went back in to see if it would still work and it went back to the looping circle page. It's so close I can taste it.
*update Managed to get 1.5.2 working but only in offline mode only. I've noticed the more pages the book has the slower it is to load, but it's loading none the less 9/10 times. Progress, so it is possible to get this working.
Click to expand...
Click to collapse
I'm not really sure what version I am using now but it loaded once on my NST. However, the next time I tried loading a book it took forever to load (and I eventually closed the app). It might have to do with memory... Who knows... The funny thing is that once it has loaded the book it works like a charm. Really fast (I would say as fast as the native app). The only thing that don't work are the hardware buttons but it was quite expectable.
enekomh said:
I'm not really sure what version I am using now but it loaded once on my NST. However, the next time I tried loading a book it took forever to load (and I eventually closed the app). It might have to do with memory... Who knows... The funny thing is that once it has loaded the book it works like a charm. Really fast (I would say as fast as the native app). The only thing that don't work are the hardware buttons but it was quite expectable.
Click to expand...
Click to collapse
Any updates? Looks promising....
Here's a link to an old version that worked for me (I later uninstalled it,finding better sources for books).
nmyshkin said:
Here's a link to an old version that worked for me (I later uninstalled it,finding better sources for books).
Click to expand...
Click to collapse
Sorry meant the 1.5.2 or up version. I have uploaded books on Google Play that I hope to read.
I'm also searching for this solution. I have tried the older versions, but there doesn't seem to be a solution. Best I've got is installing an old Google Drive apk, and downloading from there. Box also works, but it's Drive for me.
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.