Database Users

1.5 -> 2.1 upgrade process?

I'm still running Fresh 1.1. I've been holding off on the upgrade to a 2.1 ROM since I use this phone daily for business, and CAN'T have a ROM that has things missing or broken, or that just has general annoyances that interfere with the usability of the phone. It looks like we finally have some 2.1 ROMs that really are "100%" (there were claims going back awhile ago, but they definitely were not "100%").
My question is: What is the exact upgrade process, and what is the impact of that process? There are tons of threads about these 2.1 ROMs, but none have detailed specific install steps and explain exactly what you're doing. The threads seem to be targeted towards those that have a "disposable" state of their phone, not those that need a consistent and reliable phone.
It seems to be consistent that these upgrades require a factory and dalvik cache wipe. What exactly does that do? I have ~20 apps installed from the market, and they're probably 50/50 paid and free. Will these disappear during the wipe/upgrade process? Will they auto-reinstall from the market? If not, what is the best way to back them up and restore them? What other data will I lose and need to restore after the wipe/upgrade? I'm ready to move to a 2.1 ROM, but can't risk losing data or spending a couple days rebuilding my phone back to a usable state.

cmccracken,
I have been running 2.1 based roms since the Eris leak and have been very satisfied and have come to the place that i am currently experiencing no problems, however, I would advise you to wait if you are using your phone for business because all current Sprint based 2.1 roms Damage, Flipz, Regaw, etc) have the potential to leave you with no audio (no audio in calls, rings, notifications). This is a random problem that is not affecting everyone but just know it could happen. Rethink this move until the devs here can fix the audio problem for sure.

Yowza, that's scary. It would be nice if ROM dev's would actually list known issues and remove bogus "100%" claims. Flakey audio on a phone for even a portion of users is NOT "100%" by any stretch of the imagination.
I'd still like to see an explanation of the upgrade process, and what the impact to apps and data is.

Well, for most people these roms are 100% (just not for a select few and no one knows why yet).
As for impact of data etc. If you upgrade to a 2.1 rom, you will loose everything. All apps will be deleted (although thy can be backed up with Titanium backup, an app on the Market)You can still use your paid apps. All themes will be deleted. All contacts will be deleted, though they will resync as long as you have them backed up through your Google acct. All saved texts and emails will be deleted. This will be a complete wipe and I would strongly advise you to try 2.1 if you were only using your phone for personal use, but business......

cmccracken said:
Yowza, that's scary. It would be nice if ROM dev's would actually list known issues and remove bogus "100%" claims. Flakey audio on a phone for even a portion of users is NOT "100%" by any stretch of the imagination.
I'd still like to see an explanation of the upgrade process, and what the impact to apps and data is.
Click to expand...
Click to collapse
hello,
when you change firmware versions (1.5 to 2.1) you will need to wipe data. basically start over. everything on the sd card will stay (pictures, music, anything you've downloaded) but all apps and app data will be gone. never fear, your market history will be there still and any paid apps you don't need to pay again. even your free ones should still be in your download history. then after a while your contacts will get pushed from gmail and pretty much all you will need to set up is individual app settings/ custom ringtones/ custom sense setups.
you get used to it after a few times
EDIT: but yes if you use your "phone" a lot for calling you may experience the no-audio (i haven't...yet) and sometimes your phone will ring and then freeze up you won't be able to answer the call. that's irritating

cmccracken said:
Yowza, that's scary. It would be nice if ROM dev's would actually list known issues and remove bogus "100%" claims. Flakey audio on a phone for even a portion of users is NOT "100%" by any stretch of the imagination.
I'd still like to see an explanation of the upgrade process, and what the impact to apps and data is.
Click to expand...
Click to collapse
first I use my phone to run 2 different businesses and have been running 2.1 since the first eris build with no problems. I would strongly suggest making the change as now we are building off of the actual sprint leaks everything works out of the box. and considering that from the way the 2.1 releases have been for the droid sprints "official" 2.1 will more than likely come in the form of an RUU anyways and you will lose everything. so why not make the switch now.
second yes there are some that have the sound problem but that seems to be the only issue if you use wither damage control or fresh 2.0d the new zen one still needs a fix for the market so that would not be the way for you to go if you dont want to fix it. also just so you know by your logic even the sprint 1.5 release could not be considered "100%" as even it had its bugs and there are people that have issues. you have to understand that we basically have computers in our pockets and with that comes some bugs. hell even the market leader in personal comp OS's (microsoft) just sometimes does not work right on some peoples comps. This is the reality that we live with in a world of tech. in the world of software NOTHING is EVER gaurented to work for 100% of the people 100% of the time. if you can find a company that pulls that off let me know so that I can buy stock. lol
as far as the upgrade process goes it is pretty much the same as when you flashed fresh 1.1 download the zip, put it on the root of your sd card, boot into recovery, choose the wipe option and then choose wipe data/factory rest and wipe dalvick cache, go to the option flash zip from sd, choose the proper file, flash, reboot, enter info, done.

1.5 doesn't work 100% either by our standards. Flipz 1.1 is a step in the right direction, but the underlying version of the OS is flawed.
2.1 makes the phone work better, period. Ive tried almost every ROM around for this thing, and I'd have to say the latest Flipz offerings are pretty spot on. I dont have anything not working at this point. Sure there are some minor annoyances, but nothing deal-breaking. Plus when you get used to the process, its easy to update to a new rom or figure it out and patch yourself if you DO find a problem.
Sure there are some having odd issues, but their numbers are low (or theyre not posting) and every problem ive been able to either
A)try wiping and reflashing more than once
B)go back to my old install via backup/recovery (nandroid...recovery image)
The benefits of 2.1 far outweigh the very minor bugs ive encountered . Just getting rid of the laggy moments sold me on the 2.1 v 1.5.
BTW When is a device ever at 100% working? Ive never seen it.

[Q] battery drain on unregistered nook simple touch

hi. I just found out that cellular radio is taking up most of my battery on the NST. its strange, considering the fact that nook does not have telephoning capabilities. I went a bit deeper and found out that a process named DemoModeService is present, as all as WaveFormDownloaderService and DeviceManagerService, all of which are bn services. I wonder if they have a role in battery drainage and if anything will happen if I stop them.

I would start with switching nook completely off and on again. Solved all my battery drain issues in the past.

cceerrtt said:
I would start with switching nook completely off and on again. Solved all my battery drain issues in the past.
Click to expand...
Click to collapse
Is yours unregistered as well?
Increased battery drain on unregistered devices is a known issue and most likely caused by B&N services that, in lack of a better description, "wont settle down" due to the device not being registered and logged on to B&N
Stopping those services might be worth a try, and I doubt doing so will cause any major problems.

I'm not sure what causes the battery drain, but i'm betting it has to do with the Google apps.
I rooted my nook with both the methods listed here and my battery life was awful.
I restored to stock manual rooted with out adding any Google apps just manually installed what i wanted and my battery life is awesome.
The other methods might be easier but they install way too much junk that causes battery life issue.

persichini said:
I'm not sure what causes the battery drain, but i'm betting it has to do with the Google apps.
I rooted my nook with both the methods listed here and my battery life was awful.
I restored to stock manual rooted with out adding any Google apps just manually installed what i wanted and my battery life is awesome.
The other methods might be easier but they install way too much junk that causes battery life issue.
Click to expand...
Click to collapse
You're off topic
This is a topic about increased battery drain on devices that are not registered with B&N. (i.o.w., the user skipped the registration process)

I don't think gapps have to do with anything. they do get automatically installed even when the device is registered and rooted they don't cause any major problems then. they do take up a lot of battery , but its not as much as unregistered and rooted NSTs. I am sure this has to do with those bn services.
I don't want to reroot it and go through all that nonsense again. just tell me if stopping those useless services would cause any problems, and if anyone has tried it. I am not too enterprising, and would be glad if some ambitious developer did it first.

ros87 said:
You're off topic
This is a topic about increased battery drain on devices that are not registered with B&N. (i.o.w., the user skipped the registration process)
Click to expand...
Click to collapse
by the way, thanks @ros87 for your help the other day. I reached the technical team and the only thing they'd say was to use their bloody chat room that's always offline in my time zone, or to call them on their international number. they are not very helpful. so, I just bypassed the registeration.

ros87 said:
You're off topic
This is a topic about increased battery drain on devices that are not registered with B&N. (i.o.w., the user skipped the registration process)
Click to expand...
Click to collapse
Actually, is there a way to find out which app drains CPU?
Same Q I asked already: how to convince ps to display cumulated CPU time

ros87 said:
Is yours unregistered as well?
Increased battery drain on unregistered devices is a known issue and most likely caused by B&N services that, in lack of a better description, "wont settle down" due to the device not being registered and logged on to B&N
Stopping those services might be worth a try, and I doubt doing so will cause any major problems.
Click to expand...
Click to collapse
How do you stop the B&N services?

I uninstall system apk
Phone.apk & TelephonyProvider.apk
and after that my nst works fine
look at http://forum.xda-developers.com/showthread.php?t=887957

Thanks for that latuk. I think I'm one step ahead of myself here. Presumably in order to do these things the NST needs to be rooted. I now need to investigate how to root the NST.

My wife and I have each got an NST Glow. I operated them both unregistered. We both experienced battery drain of about 6% overnight (10 hours) in screen saver mode. I was about to embark on the rooting/apk removal solution as discussed above.
Before I started that process I thought I might as well try registering one of the NSTG's as a test. The result was conclusive.
Again overnight in screen saver mode the unregistered NSTG experienced 6% battery drain, the registered NSTG experienced zero battery drain.
I can only conclude that B&N have got built in processes that use a great deal of battery power if the nook is unregistered.
So it appears to me that for simpletons like myself the easy answer is to register. They simply require your email address and name, no credit card details. So registering isn't so bad.

Unfortunately, the time has come where B&N have taken their e-store and their registration servers offline. Even if your device isn't rooted, rom'd or otherwise customised, it is now an absolute necessity to know how to bypass the registration screen, the Out Of Box Experience*.
1. Turn on your NOOK.
2. At the welcome screen hold down the button on the top right (page turn button) and at the same time slide your finger across the top of the screen from left to right.
3. You should now see a Factory link on the top left of the screen, press this link.
4. On the factory screen hold down the same button (top right) and at the same time tap the bottom right of the screen.
5. You should now see a Skip Oobe link on the bottom right, press this link.​
So it is still really a good idea to know how to work around the battery drain, as it is still an issue with this custom ROM I'm presently using, retired in 2015 [NST/NSTG][ROM] Tweaked Modded ROM Final
With Superuser installed, I used this ROM's Clean Master app to remove
com.adome.air.apk
com.benhirashima.nookcolorsettings.apk
com.android.email.apk
com.bndeviceregistrator.apk
com.bn.nook.affiledownloadservice.apk
com.bn.nook.cloud.service.apk
com.bn.nook.community.apk
com.bn.nook.shop.apk
Will report back if battery drain fixed.
This is the second time I tried to fix battery drain on a custom ROM, last time was using the 1337 ROM that came out in 2014. It was preloaded with too many utilities imho and I removed too many apks that I broke the dictionary app while fixing the battery drain.
*Uech! Out of Box. Experience. Remember when an experience was something worthwhile, like the first time you heard The Jimi Hendrix Experience or how much practice you've had in your profession.

Anne-d'Royd said:
Unfortunately, the time has come where B&N have taken their e-store and their registration servers offline. Even if your device isn't rooted, rom'd or otherwise customised, it is now an absolute necessity to know how to bypass the registration screen, the Out Of Box Experience*.
Click to expand...
Click to collapse
Maybe. If you update the firmware to 1.2.2 everything will work as before--assuming you have a US ROM. If not, you can change ROMs to a US version and then update the firmware. Either way, you don't need to skip oobe unless you want to for some reason.
I tried it recently on a second NST I got to experiment with. I thought I was doing really well, just keeping enough to allow the Reader/Library/Dictionary to function. Then I had occasion to look at a logcat to track down a problem. There was an endless string of system wails over this and that which could not be found or not be contacted. I could hardly find what I was actually looking for. In the end I decided it was better to update to 1.2.2, register, and just ignore the B&N stuff (except for the Reader/Library/Dictionary)--oh, all except for the NookCommunity app. That I did disable because it constantly nags you in the notification area.
OK, now having said that, I am still using my original NST which is running FW 1.2.1 (and is rooted and much modified). I've had no issues with it despite the dire warnings from B&N about June 29, although I did turn off the automatic update a few weeks before because attempts to update OTA were causing reboots.
But I've never bought any books from them, so I've not done anything that needs intentional connection to their servers since the change.

Hi, I live in the UK and I recently bought a Nook ST for cheap on eBay, planning to use it bypassing the registration. Little did I know about the battery drain and processes of the stock unregistered ROM. Mine runs under 1.2.1 I firmly believe UK version as I tried to reset and register but only got errors, forcing me to use the bypass sequence of buttons. Obviously I didn't even register any WiFi spot and the module is always off.
Based on your experiences, what is the best way and quickest to solve this battery drain? I'd use the Nook just as a e-reader, so I'm not interested about added functionality - if anything I'd like it as simple and little distracting as possible.
Is the US firmware a good fix for the problem? I wouldn't mind using stock US firmware as long as you confirm it still lets you register... Do you need root? Is there any particular procedure to switch to a different firmware? Is the ROM available on the internet?
If that doesn't even require rooting, I'd probably go for it... Otherwise what are the best things to do to fix the issue in a rooted UK device?

EmaTheMirror said:
Based on your experiences, what is the best way and quickest to solve this battery drain? I'd use the Nook just as a e-reader, so I'm not interested about added functionality - if anything I'd like it as simple and little distracting as possible.
Is the US firmware a good fix for the problem? I wouldn't mind using stock US firmware as long as you confirm it still lets you register... Do you need root? Is there any particular procedure to switch to a different firmware? Is the ROM available on the internet?
If that doesn't even require rooting, I'd probably go for it... Otherwise what are the best things to do to fix the issue in a rooted UK device?
Click to expand...
Click to collapse
You can reset the device to factory and then flash the US firmware. This will allow you to register and avoid the power drain issue which, to my knowledge, has never been fully resolved. Actually, you probably don't even need to reset the device, just flash the US firmware. That will put you at 1.2.1. (US firmware flash: https://sites.google.com/site/xcdguides/nook/nookregion)
As you may know, there is a new firmware, version 1.2.2 which incorporates updated TLS standards--but only for B&N transactions. However, even if you don't transact any business with B&N, a registered device will be constantly nagged until it is updated, and rooting will disable updating, but not the nagging. For that reason I recommend that after you flash the US firmware (but before rooting) you do the 1.2.2 update manually and get it over with. (update download and instructions: https://help.barnesandnoble.com/app...tware-updates-for-tls-1.2-compliance#ManualDL scroll waaaaay down.....)
If you want to root the device after updating, I recommend Nook Manager, but you need to make a minor change to the files on the SD card before you use it with 1.2.2. This is described here: https://forum.xda-developers.com/nook-touch/general/nst-nstg-fw-1-2-2-update-t3785566

Hi, thanks for the reply, I solved the solved the problem changing the firmware to US following this simple guide:
https://sites.google.com/site/xcdguides/nook/nookregion
Then updated to the latest firmware manually, which solves the connectivity issues among others, with these official instructions:
https://help.barnesandnoble.com/app...evice-software-updates-for-tls-1.2-compliance
Otherwise it wouldn't even connect. I didn't know at first and registered a new account via browser, signing in from nook later - then it connected just to register the device, don't ask me why - but it's always best to have the firmware up to date anyways.
The battery seems now fine, so far.
Just for the lulz, I tried to link a card to the shop but can only have US addresses for billing... Lol, eBook DRMs have always amazed me. Luckily, you can easily download Google Play purchases and sideload them (among others) via Calibre.
Thanks anyway, hopefully this post will be useful for future reference.

Tweak for N900 Stock Lollipop to fix memory leak and battery drain?

Hi guys,
I ordered a GNote 3 and I'm really excited. But I read a lot of stories about the lollipop really buggy, memory leak, and battery drain. But I don't see many comments about these in the ROM thread, and someone mentioned that they like Stock lollipop better than CM12. Does this mean stock lollipop for Exynos is working fine? I don't have the device yet, so I have no way to try out yet myself, but I plan to flash my desired ROM right away when I get the phone. It could be one of the TW lolliop ROMs or CM12.
Just a note that I would love to run lollipop, and not kitkat. So could you please advise around that? Are there tweak that people use to fix the issues?
Thanks!

Hello!
Right now I have over a month testing the stock LP ROM on an exinos device, it has been quite a good experience, the ROM is very responsive, and although it has a huge memory leak (I have found my device running on RAM as high as 85% with no running apps, just running the processes needed for the OS to run) nevertheless I can harddly notice any lag n the system, I use Clan Master to monitor RAM usage, when I find my device I use the clean now feature, and the RAM usage goes back to around 60-65%.
On the battery subject I run my Note 3 paired via bluetooth with a Gear S, and I am getting between 20 to 24 hrs. Of continuos use, so taking into account I am always running with bluetooth on, I think I am getting a pretty decent usage time, I would like to let you know that I mustly connect to the internet via WIFI, only use Celllular Data when driving or in places where there is no WIFI available.
After installing LP ROM I went straight to rooting my device and installing Titanium Backup in order to be able to debloat, I have managed to uninstall APK that I found useless for me, and got rid of them, also I use Greenify and I have greenifyed every app not essential, I also use Startup Manager ( Free) to get control over what apks startsup.
Finally, I use tasker to get control over how my device handles the changes between Cell Data and WIFI.
I hope you find this information useful, and please excuse my english!

Graphical corruption and random (frequent) app crashes?

Hi everyone,
So I have a really really strange issue with my phone lately and that is: I get a lot of graphical corruption and random app crashes (any app, including system apps like the Samsung or Google ones), I did in the past do some overclocking but that was way more than 6 months ago and this issue just popped up about 1 month ago and my battery life is now also really short and the phone can show 40% and shut down or show 20% and shut down and then when I plug it in I get the battery charger indicator with 50%+ battery left.
Now here's an even weirder thing: that is not specific to any ROM and happens on more than one, any TW 5.1.1 ROM I try and even on CM13.
I do use multi-boot but I did test the ROMs even without a multiboot environment and those things still happen.
So I was thinking that it might be that my battery is dead (although apps say it's healthy) as I've seen phones doing that when the battery is close to dead but since I can't really purchase a new battery in my country I would like to ask if someone has an opinion on this?
Could this be a hardware defect or something broken in my "hidden" Samsung-specific partitions or is it just the battery, has anyone else encountered this?
I really would like to know how big of a chance it is that my phone is somewhat of a brick before wasting a lot of money to buy a new battery from an other country.
As you can see most of the photos I took have either missing letters or strangely colored letters but that's because that's the graphical glitches I get most, the worse ones have big parts or even half of the screen totally black, UI elements extended awkwardly with gray outlines, strange colors on-screen and missing whole UI elements.
Sorry for the potato quality....took the photos with my Redmi Note 2 with CM12.1 instead of MIUI7 cause I am too sleepy to wait for it to reboot into the other ROM (and I think I wiped the whole cache+dalvik on my last CM update so the boot would take a long time since it would need to do the whole optimization for MIUI7 as well).
Also a photo of Settings crashing, all I did was just open it, saw the settings list and after a second crash.
NOTE: I am on a 100% clean install right now (wiped EVERYTHING including internal storage) and I barely even managed to get past the setup wizard since it kept crashing.
Thanks for any help/opinions/ideas.

No one knows anything?

How can I get it
Sent from my Q510s using XDA Free mobile app

New battery and did a full odin reflash (with SEA pit file), even updated to 6.0, bugs still here but way less frequent, crashes not here anymore after update to 6.0 but still here before even with a 5.1.1 reflash and clean install, seems like the phone is as good as gone, will try to send it to warranty to see what happens but don't expect much since "Knox Warranty Void=1".
Lesson learned: if such bugs start popping up for any of you guys even if the battery is not in a good state you'd end up better just buying a new phone since your note 4 is quite surely done and gone.

Removing the downloaded but not installed Nougat update

Hi, first post. I asked the question on another site some months back about deleting or stopping the install notification about the downloaded, although not installed Nougat update, no answers were forthcoming. My phone on 6.0.1 works great and I have no issues that warrant an upgrade. I have hardly any apps installed on it and really only use it for light internet, photos, the phone and GPS. I don’t really want to update it to Nougat due to some of the horror stories I have read. I am not (yet) very Android proficient.
Can I just leave the downloaded Nougat updated installed, but stop the daily notification to install it?
Or
Can I easily delete the downloaded but not installed Nougat update?
In this case I subscribe to the notion, if it isn’t broke don’t touch it. Maybe I am being too overly cautious.
Current details
Hardware: XT1642.
Version: 6.0.1
Build: MPJ24.139.23.4
Security Update: 1 May 2016
Any help steering me in the right direction is appreciated.
Cheers,

@CC2005
If you remove downloaded files, still it will not stop, then you will get notification for new update available and to download it.
Better if you update to latest version,
otherwise you need to restrict notification for moto updater app or data for it. (I don't remember correctly if those feature existed on MM, as the way it is present in N)

It looks as if I will have to just go ahead and install the OTA Nougat 7.0 update that has downloaded; as there doesn't seem to be a simple way of stopping the notification to install it. As mentioned, I didn't want to install Nougat as it works perfectly now on 6.01, maybe I am just worrying about nothing, obviously Nougat 7.0 doesn't stuff up all devices.
It is still in warranty so if an OTA update causes problems I may be able to return it?
Cheers

CC2005 said:
It looks as if I will have to just go ahead and install the OTA Nougat 7.0 update that has downloaded; as there doesn't seem to be a simple way of stopping the notification to install it. As mentioned, I didn't want to install Nougat as it works perfectly now on 6.01, maybe I am just worrying about nothing, obviously Nougat 7.0 doesn't stuff up all devices.
It is still in warranty so if an OTA update causes problems I may be able to return it?
Cheers
Click to expand...
Click to collapse
If there is any problems and if it's under warranty, you can surely take it to the service center.
As far as I know, if you get a replacement device, it will be updated to the latest version out of the box. So there is no way going back to MM.
If you still want to use MM, your only hope is custom ROMs.
You can't downgrade the official updates.
Nougat is not that bad. Most of us are waiting for Oreo and I am wondering how are you still on MM
Have a nice Day :good:

arunzone said:
If there is any problems and if it's under warranty, you can surely take it to the service center.
I am wondering how are you still on MM
:good:
Click to expand...
Click to collapse
I have disabled most of the Motorola notifications "Motorola Update Services", "Motorola Notification" and one or two others. This sometimes prevents the "Install System Update" notification as long as I do not power it off, I put it to sleep by putting if face down. Although most of the time I have to delay the install manually by rescheduling the install time-pressing later etc when the message pops up.
I am a light user, and can get up to 8 days (rarely) usage out of a single charge, I have disabled a lot of Google & other Apps that I don't want to use, and turned off many Google Play Services. Lots of photos, calls and WiFi use I get 2-3 days use, so I am trying to keep the current OS. Also the works reasonably well in very hot weather taking photos and using the GPS-off line maps, it does at times get hot and can suffer camera issues and more so, GPS stuttering and lag above 35C-40+C but shade it from the sun and minimise use and it will work ok.
Cheers & have a great day too.

Ok, I've been operating with Nougat 7.0 for two months now. There are pros and cons and some of the cons I will adapt to as they are only preferences, minor setting and appearance.
My main concerns about the OS update were battery life and heating. Normal use, the battery drains a little quicker without WIFI or Sim data on, not enough to cause concern. But with WIFI and or sim data on, it definitely uses more battery power than before, almost at an average of 10%-15% more-not a scientific analysis. I am not a big data users so again not big concern. Although when using data, downloading, surfing etc, the battery rate depletes at a much quicker rate than before, I would estimate 30%-40% faster. I also notice the battery depletes much quicker when using the camera and the associated heat when using the camera feels (going by sense not measuring it) somewhat higher. The camera and video mode are the one that bother me and I forgot to mention, using offline maps, gps enabled (no WIFI or Sim data activated) the battery use is again higher than before.
So, I would have been better off on MM, yes, but it is what it is and I can work around the battery issue when I know my usage of those features will be heavy. A cheap pocket portable USB charger may need to be purchased.
I haven’t done a factory reset and I have only cleared the cache via settings app. Maybe the next step before a portable pocket USB charger is purchased.
Cheers