Hi, I'm really sorry if this is considered cross posting, but I'm starting to get desperate here and really need help. I'm on a deadline and running out of time, I need to figure this out somehow and have been bashing away for almost 24 hours now.
My question is in this thread - and is the last post.
I am actively online and working on this. I'm starting to consider just reverting to stock from the recovery partition and then building everything from scratch, but if I can avoid that time vampire I would like to. Does anyone know what's going on, have some ideas, or anything?
Next step, I'm going to try the 1Gb 5Gb repartition that Dean originally developed. Though with my Nook broken already and my inability to restore it to a working state despite having a ton of perfectly fine Nan backups, I have doubts as to whether anything will change there.
I'll monitor both threads. Thanks in advance for any guidance/help.
Edit: Still plugging away, last steps mentioned above didn't work. Next steps: I'm reading Leaping Lar's partition fix thread and getting some ideas. am going to try:
Flash Partition > Boot to CWR
Format > Flash to CWR
Flash Dizzy Den's signed 4.1 zip > Boot to CWR
Flash my Registered Nan backup of Stock 4.1. > Boot to MMC, get a look around
I think I already did this, but left out the last step. Might work as it should restore my registration data instead of starting me from an unregistered account. If it seems worth trying at that stage, I will then flash my registered Nan of 1.4.2 and get a look at that.
Speculation: I just realized, I've been trying to restore a backup of a rooted 1.4.2 over an unregistered 1.4.1 - which is what I keep getting reverted to. I don't know if that matters, but my hope is if I flash my registered backup over what I'm reverted to, then build up to registered 1.4.2, that will help things... We'll see.
Failing all of this, I will try Leapin' Lar's partition repair.
I have finished reading the Partition thread I linked to above (where my original post is) and found that one other person reported my issue, almost to the T. His/Her user name is Blondie. Blondie seems to have quit without a fix, or if ever got a fix it was never posted. It was quite some time ago, but if any of those who helped him/her can remember if there was a fix would you let me know what it was?
Screw the original nook firmware. Go install CM7 Mirage ROM.
Rooting a stock nook is pointless. CM7 is better, faster, more efficient than stock and it comes rooted by default.
Now that your serial number is probably gone or corrupted in the /rom partition, you most likely cannot register your nook with the B&N servers, and that is probably why you can't install apps.
If you need a complete partition table wipe, follow this guide. http://forum.xda-developers.com/showthread.php?t=1759558
Next time you decide to mess around, be sure you backup your ROM and factory partition before doing anything.
sagirfahmid3 said:
Screw the original nook firmware. Go install CM7 Mirage ROM.
Rooting a stock nook is pointless. CM7 is better, faster, more efficient than stock and it comes rooted by default.
Now that your serial number is probably gone or corrupted in the /rom partition, you most likely cannot register your nook with the B&N servers, and that is probably why you can't install apps.
If you need a complete partition table wipe, follow this guide. http://forum.xda-developers.com/showthread.php?t=1759558
Next time you decide to mess around, be sure you backup your ROM and factory partition before doing anything.
Click to expand...
Click to collapse
I do have backups of everything. As I said above, they aren't wholly functional.
I never said I was completely unable to install apps, or that I couldn't register with B&N. I can register fine, and in some scenarios I can indeed download my apps just fine, just not if I try and restore a MN Nan backup. That is not because of a missing SN but because of a registration issue that can be caused by the MN process - otherwise I would not be able to download them at all in any scenario.
Also, if you know the MN process you know my factory partition is intact. Perhaps the partitioning messed with it a little, I'm not sure - but nowhere did I say I have yet tried to reset to stock from the factory partition, so we have no real way of knowing yet.
I understand that my OP is starting to get tl;dr because I don't want to double-post, but actually reading what has been done so far and reading the post at the original thread I linked to might be more useful in trying to give people advice. A little less snark would be useful too, I am not a n00b at this by a long shot and talking down to people tends to get hackles up instead of being productive - especially when you clearly haven't read their thread - as an example, if you had read it, you would have seen I already know about Leapin' Lar's partition fix and it's one of the next things I plan to try..
On the other hand, I may take your suggestion about installing CM7 Mirage. Honestly, I had my reasons for not doing that in the past, but those reasons are largely moot today. I will get a look at the thread. Thank you for the suggestion.
You're right, I apologize for not reading thoroughly. I had a derp moment.
No worries Sagirfahmid, I owe you an apology too. I'm sorry to have jumped on you, I am a little bit... stressed, and tired. Not that it's any great excuse. I need to take my own advice about talking to people. Sorry.
And fwiw, I believe you are right and the original partition did mess with the factory partitions, I've just been avoiding facing it. I really ought to get off the fence and run the repair and then follow Dean's guide to using fdisk on the emmc, but I'm getting OCD about trying every other thing first - even down to considering a flat reset to factory and rebuild from scratch. Stupid, I know.
Thing is, there is at least one other person out there who had this exact problem, and it didn't sound like her issue ended up being a corrupt partition as the partition repair didn't help her. Unless it was too corrupted. I know there were a lot of people running the same system as me, and it was very stable. Someone besides me and one other person has to know what this is and how to deal with it. That's what I'm hoping anyway. LOL
And seriously, thank you again for the reminder that there are other options out there that might better suit me now. The more I read the more I think if I can just reset the darned thing to a fully working state, I may well just do an SD CM10... or should I just stick with Mirage? Is there an advantage to Mirage over 10.2?
Yes definitely. It's faster--that's the most obvious advantage. (I disabled all the fancy animations and removed a lot of useless system apps like the phone, contacts, calendar, camera, and GPS app via adb).
Also, CM7 Mirage has USB host mode, so if you get a male microUSB to female standard USB port, it is very possible to use a keyboard or mouse, or a flashdrive or harddrive (if you get a powered hub). AFAIK, the max current it can supply without a powered hub is 100mA (enough for a flashdrive or keyboard/mouse that isn't too fancy--skip the ones with LEDs; each LED uses around 15mA).
Oh yeah, CM10 runs in phone UI (there's an extra bar on top taking up space).
In CM7, there's only 1 bar, so you have a bigger area on the screen. Of course, there is a patch to get CM10 into tablet mode, but I don't like all the hassle.
On CM7, you can overclock the CPU to 1.2GHz, but on CM10, it's limited to 1.1GHz AFAIK.
=====================================================
Right now, I'm hoping to get Debian ARM natively installed on the Nook Color. I've been making progress thanks to the devs and users here. Android is still required, but it will be on top (instead of the other way around, which is Android on top and Debian chrooted). SInce they'll be using the same kernel, I think I can get Debian to use the Nook Color's USB port to connect devices like printers or scanners (that would be so awesome...).
If you're interested in running full blown Debian on the NC, and assuming that you are able to fix yours, you can check out this thread: http://forum.xda-developers.com/showthread.php?t=2422518
Solved
Sorry for the double post. Need to separate this from the wall o text above. Problem is solved and since I never did find a spelled out definite answer while I was reading the last 2 days, I want to post it here where someone who might be looking in the future might easily find it.
To reiterate the problem concisely for those who don't have time for the diatribe above:
My device is a Green dot Nook Color:
* Running a stable Manual Nooter 5.08.20 over a Stock B&N 1.4.2 ROM, and using > This < method to block OTA Updates - basically use a SQLite Editor for Andriod to modify the fota mode in the nook's registry.
I recently started getting the Low Memory message asking me to please archive some of my apps to SD. Am about to go on a long trip abroad and I not only needed what apps I had but also need a couple more. Solution: Repartition the Data and Media partitions.
Full backups: have a whole slew of backed up NC B&N Update zips, Flashable updates created by several awesome people here, and step-by step Nan Backups of every single time I have re-rooted my device after a B&N Update - signed and registered stock configs, roots and final images, and finally a whole store of dated backups of my Tibu backups off of my SD card.
So, I repartition following steps exactly.
* At first reboot, CWR freezes on load. This makes me thing something went horribly wrong.
* Reboot again, everything seems to Format fine, reboot into Nook
* Unlike most people, my nook has reverted to an unregistered stock 1.4.1, no root.
* Flash my latest Nan-backup of my rooted NC, doesn't take properly and B&N is a mess because (duh) I didn't register it before flashing - But I shouldn't have needed to because all of those settings were in my Nan Backup. Okayyyy... weird.
* Flash back to a Registered stock NC nan backup of 1.4.2 since that was the last version I used. I was able to DL books and read them, and could DL apps - but my apps couldn't install at all and there were a couple of new B&N Apps that were stuck in a DL/Install loop too. Hm.
* Flash an earlier root Nan over that. Now my Nook can't download anything, I get an error message that it cannot execute. Lovely.
* Bash around in this fashion trying to make it work, occasionally trying different partition schemes in the process, while reading every thread I can find on the subject of what issues I'm having.
I begin to suspect that my partitions might be all messed up, especially considering the original freeze from CWR, but have no real way to check that and don't want to give up, so I post in the instruction thread and later here to see if anyone has any guidance or knows what this is.
A whole slew of people have endorsed this method and had no problems.
A few people had some problems, but only one user has reported exactly my problem off of the exact build I was running, no less. (1st link is that user's first post and 2nd is the page where her posts begin). However, that thread ended with no real answer - or so I thought.
At once point before the issue ended with no further response from the poster with the issues, Leapinlar (who had been assisting her, or at least trying to) tells her that if his Partition Repair didn't solve anything, then it likely wasn't the problem. If she cannot get her B&N Apps to DL & Install, then it's most likely the version of the B&N Stock that she is on and she needs to flash to the most recent - he even points her to a signed CWR Flashable one that he created for 1.4.3. She argues that can't be the issue - and I get that, because the apps installed and worked before in 1.4.1 right? So why all of a not now simply because she's back on 1.4.1 again?
I don't know why B&N would have made it so that you can't install any older apps on your device even though they installed on older ROM versions, forcing people to move up to 1.4.3, but it appears to me that this is exactly the case and Leapinlar is once again correct.
Took me a long time to internalize that and have it click. After running his Partition Repair with the same results as her, I left it on a registered 1.4.1 Stock, put the NC down and stepped away for a while to do other things. when I came back I was fixated on what Leapinlar said about flashing to a newer version of B&N Stock. So I did. And when that didn't really fix it I flashed up to the next ans last version, 1.4.3.
Hallelujah, problem solved!
For my own apps to download, I had to wait for a couple of new ones sent to Nooks from B&N for version 1.4.3 to download and install - and they were not able to do that on earlier versions. I propose that their inability to install was what was blocking my other apps. but it could be that the others were also made version specific once B&N stopped making NCs in favor of HD's and the Tablet, and released the final update.
Regardless, that is the final answer. If you are on MN and repartition, and then find when you boot you are taken to unregistered stock, and upon registering you can access your books but your apps will not install after downloading and you have a couple of new ones that seem stuck at dlownload and install, all you need to do is Update your NC to the final release, 1.4.3, and the re-root. I think you will need to re-root from scratch, unless maybe your last root backup was from 1.4.3 - which mine was not.
Next dilemma: Stick with root or start running a CM ROM from SD...
I'm a cheapskate, that's the truth. I am a geek, I want to do **** with my devices and I don't care if I end up bricking them so long as there are ways to recover. I also care about my privacy. I don't stick with the stock firmware because:
1. B&N wants you to REGISTER with your CREDIT CARD to be able to actually USE the Nook Color. Why the hell?
2. B&N possibly has BACK DOORS to your Nook Color. They might DRM lock apps or something. They can obviously force updates onto their users unless they root. They might also decide it's time to brick your tablet if they wanted, so you would go buy another one (yes, this is more of a conspiracy theory, but hey, if they can force updates, they surely can also do this).
3. B&N's custom Android is crippled unless you root. You can't use the 5GBs of space. Why the hell not?
etc etc...there are more reasons I don't stick with any stock firmware, be it for a tablet or phone.
(I use Debian on my computer most of the time now because Windows is a piece of crap. You can't do whatever you want on it, except game. Did I mention the useless startup services and apps you need, especially antivirus, for Windows to function without worries of getting a keylogger or some nasty virus? Valve has made Steam for Linux very usable, and I rarely use Windows for gaming now. Linux is tons faster, and I can do almost anything on it).
Have you ever used a T-Mobile smartphone? the apps that come installed are numerous! It makes me want to puke every time I use a stock Android phone from a phone company. I like and want my devices to only contain the apps I want. That means NO BACKDOORS, NO FISHY BACKGROUND PROCESSES, NO **** APPS, NO RESTRICTIONS.
======================================================
Backup the documents and whatever you have on your B&N firmware. Install CM7.2 Mirage onto INTERNAL SD card.
Stop being a wuss :silly: and start enjoying a better Android experience.
sagirfahmid3 said:
I'm a cheapskate, that's the truth. I am a geek, I want to do **** with my devices and I don't care if I end up bricking them so long as there are ways to recover. I also care about my privacy. I don't stick with the stock firmware because....
Click to expand...
Click to collapse
I completely understand! I have many of the same concerns and make workarounds and otherwise try to frustrate the usual 'Big Brother' tactic that are becoming so prevalent. I don't think you've gone into the realm of conspiracy theory at all, what you're talking about is a long term goal I think. Think of the marketing and capital profit possibilities of that kind of control over a still largely unregulated market - 'largely unregulated' because the technologies and the possibilities they allow are evolving so quickly.
I also am a 'computer geek', prefer control of my own devices and am very strict about personal security. So then why does B&N have my personal data? Largely because they had it far earlier than there was ever a blip on the tech radar of 'e-readers'. I'm also incredibly bookish and there haven't been a whole lot of B&N in my region, but I prefer their company as a book retailer, so I was a member that had begun ordering from them online as soon as they had a website to order from. So, it wasn't a huge loss for me to keep the stock and use it as intended. here are some things about this that do grate with me, yes, but they wouldn't have lost my data history anyway, so wth, I might as well get a really elegant e-reader interface from a company I mostly like and support. This is definitely not a situation that applies for everyone, I know.
I use windows on a secondary boot partition and funnily enough, largely for gaming. I also use it on a work laptop because I have to. I run Suse most of the time, myself.
As far as DRM, it' something we need to fight in the courts and through making our own backups for experimentation, and that's all I can really say.
When I bought my NC over two years ago, tablets were still pretty uncommon and e-ink readers all the rage. I splurged on this even though I was still using a flip phone because I felt it would serve multi needs well:
a) The need for an e-reader (I travel at least 1ce a year and I read a lot while traveling. Books are HEAVY! and I'm getting oilder...)
b) The desire for an e-reader that could read color and comics - so I could DL comics and fan creations and manga as well as books on the same device - and one that isn't an Apple (I dislike Apple as much as I dislike MS).
c) The desire to have a good interface in a size that is more readable than most phones on the market, to surf the web on or read the above during my long commutes.
d) The desire to have all of the above in one item that would also not tie me to a single seller - in other words I also wanted to run the Kindle App and Google books.
At the time, Kindle Fire had not been released and the next best machine (actually, tied as of the time I bought this nook) was an iPad. Other tablets out there were more expensive and glitchy and without that quality - some didn't even expect to ever update their android ROM. There was nothing on the market close to the NC in that price range - and I knew I could root it or otherwise replace the original ROM if I didn't like it, to do what I wanted, and essentially never brick it!
I chose MN over CM or Nightlies because I didn't have to mess with the factory partition at all or ever worry about replacing it, and it let me use my nook directly from system in a two-sided boot that had a tablet on one end and a Nook on the other. Very neat. I got the 3 yr warranty when I bought it because at that time they stated that you could return the NC within that time for a lower price on the next new thing. I plan to use that, so I wanted the original factory partition intact.
There are only two things today that would keep me from running a CM install or SD right now. The most important of those two is Battery Life.
The trip I'm about to go on is to India from the east coast of the US. We'll be gone about a month and my NC/Rooted or flashed tablet will be my ONLY mobile device. I need something stable, and that if I am not already familiar with it will be fairly intuitive, and most important - Good Battery Life. As far as I know, the CM ROMs for NC are energy hogs - is that still the case? We will have a lot of devices to try and keep charged, one plug adapter, and the NC will have a central role in our keeping in touch with family and friends. We we go for a day without a charge but with about 8 hours of use including wifi time on a MN root, I know I will still have enough charge the next day till we get to the next location where we can try and charge everything.
My other concern is more about running apps and what apps will work with the setup I'm planning - which I already know would work on my NC had I not hit the "Low Memory" wall and started all of this.
I am still interested in running CM, can you point me to info on these? For the second, I need to link to Canon Image Gateway wirelessly and also a Bloggie. I love that CM7 can run a USB interface! That's a huge advantage that I could use!
Even if I don't use it for this trip, I may change it when I get back to a CM7 sd boot to play with till I'm used to it. Also, I am rooting a NC for a Niece before I leave, and I think I'm going to change tactics and put CM on it instead.
As to smartphones... LOL. I still have a pay-as-you-go flip phone, wanna talk about being cheap and having security paranoia? XD Seriously, I spend a lot on my computers - which I prefer to build - and spent a lot on my tablet back when I bought it and when I replace it will consider carefully and spend on that again. =) Smartphones? I will get one eventually, it's a matter of time, but I'm holding out as long as I can. LOL
...I need something stable, and that if I am not already familiar with it will be fairly intuitive, and most important - Good Battery Life. As far as I know, the CM ROMs for NC are energy hogs - is that still the case?
Click to expand...
Click to collapse
Nah, CM ROMs have great battery life these days. I get 10 hours on my Nook Tablet (CM10, 4700mAH battery AFAIK); 8 hours on my Nook Color (CM7, 4000mAH battery. Obviously, it's going to have a slightly lower battery life). Also, keep in mind the li-ion battery is almost a year older than the Nook Tablet, so it has a decreased charge capacity. Li-ion's have a lifespan of 3 to 5 years--after than, you're gonna get crappy runtime on battery. Good news is li-ions are very recycle-able and non-toxic. I think most major electronics stores accept li-ions for free.
The only issue with stability is that, if you have wi-fi set to "always on" in CM7, sometimes you'll get a SOD (screen of death) after an extended period of sleep. Basically, your screen will fail to turn on--you must force power off and restart the NC. The guaranteed workaround is to set the wi-fi setting to "only when screen is on." You can safely overclock your CPU to 1GHz (+200MHz past stock 800MHz) guaranteed, and 1.2GHz almost guaranteed (I have mine at 1.2GHz, no freezes or crashes at all, and I run Debian chrooted in it currently, which takes a lot of power).
My other concern is more about running apps and what apps will work with the setup I'm planning - which I already know would work on my NC had I not hit the "Low Memory" wall and started all of this.
Click to expand...
Click to collapse
All CM builds can transfer apps' storage location to the external microSD if you wish. I have all my games and non-essential apps on my 32GB class 10 microSD, both on my NC and NT. Again, don't forget, the CM7 build for NC has USB host mode (so if you were really crazy, you could possibly plug in a 3TB+ mechanical harddrive, with a powered hub of course). Don't forget, the Nook Color also has bluetooth (which isn't there on B&N software). I have successfully transferred files between my netbook and my NC via bluetooth (but you have to be within 1 to 2 feet distance lol, unless you tear apart the NC and mod an antenna or something). You can also use an external bluetooth GPS receiver and bluetooth headset. Go look on the NC accessories thread if interested.
Even if I don't use it for this trip, I may change it when I get back to a CM7 sd boot to play with till I'm used to it. Also, I am rooting a NC for a Niece before I leave, and I think I'm going to change tactics and put CM on it instead.
Click to expand...
Click to collapse
Good idea. Install CM7 on your niece's NC (INTERNALLY :silly: ) and see how you like it. I guarantee you'll like it, and so will she. Since you messed with the partitions, I would suggest you visit the CM7.2 Mirage thread and post if the changes in partition sizes should make any problems with flashing.
Thank you for all this great info! I had read about the SOD issue, but I usually keep my wifi off when not using it, so I'm not too worried about that - it helps battery life some too. Interesting, I hadn't realized lion batts had that limited a lifespan. I haven't noticed a whole lot of change in my own NC's life, but to be honest I haven't looked either. I should.
Regardless, great to know CM is better at battery life.
sagirfahmid3 said:
I have all my games and non-essential apps on my 32GB class 10 microSD, both on my NC and NT.
Click to expand...
Click to collapse
Actually, that brings up the issue of class 2 vs class 10 cards and stability. There are a few threads that have benchmarked SD cards for running CM ROMS and have found the best and most stable - especially for large cards - is a 16 Gb Cl2 SanDisk... it looked by recent discussions that this is still the case, have you noticed this at all? My card is also Cl10, and as of now I think I would want to run CM off of an SD, at least until I'm used to it.
Turns out I didn't mess with my partitions after all. Gotta love computer systems! LOL Turns out the issue was version of stock I was running, and only that. I re-registered, updated to 4.3 stock and all is fine. You would think I would learn one day to read, step away and consider, instead of banging my head against a wall repeatedly. I should have figured it out much sooner, Leapinlar basically spelled it out for the other member who had this problem. And it completely explains the issues I had too. I may end up messing with them correctly again though.
I did not know the NC ended up having a blue tooth after all! I remember the speculation but the teardowns had only begun then and I never followed up on them. Now that IS interesting!
My Niece's on the other hand does have a corrupted partition, but from something she did to it. I think I will flash CM to the emmc, nice idea!
Related
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.
Background:
The devs have had some major breakthroughs in getting Android ported over to our HD2s lately. Just a bit ago, they finally got Bluetooth working and I decided it was time to give it a shot. I was pleasantly surprised at the stability of the version I ran and have actually been using it as my primary ROM for five days as of this writing.
My biggest problem was in wading through the myriad of techno-speak and complaints piled on top of vague references to a non-existent thread over on the Leo forums. However, once I got things figured out, I was good to go and haven't looked back!
Please see post 2 for some tips and tricks and "Don't do's" that I learned along the way.
You absolutely MUST HAVE data access to install Android. If you have WiFi, that might work, but if you may be able to talk a friend with a data account to lend you their SIM card for a few minutes
For the curious, I did initially install Android on my 16gb C2 microSD card that came with the phone. See post 2 for why I am no longer doing so
Read "Steps" for the fast and easy version, "Details" if you're a bit nervous or want to see how neurotic I can be with explanations.
And so, without further ado, here is the simple method for locating, download, installing and running Android on your HD2!
Steps:
I recommend finding a nice, stable ROM and flashing it fresh after a Task29 before moving forward. Be sure to hard reset (or use Clear Memory under Settings) and then soft reset your phone to ensure the ROM is stabilized.
If you are using a stock radio you may have issues, the radio I am using is: 2.10.50.26.
Once your phone is up and running, go to Settings Tab->Sound & Display: Single Volume On (100%), Pocket Mode On, then click Backlight: Ensure "Automatically adjust backlight" is NOT checked, adjust your screen brightness to optimal levels, then un-check the other four boxes.
Exit Settings and make a call using the Speaker Phone, then turn the Speaker Volume to 100%.
Visit GameSquare by clicking this link and scroll to the bottom of that page, look for the "Download" link at the bottom. Save the file (currently it is named "HD2Froyo_V2.1.7z") to your computer.
At this point, it would be a brilliant idea to backup the contents of your microSD card and reformat it.
Once your microSD card is ready, place the file you downloaded from GameSquare on the root of the card ("root" means don't put it in any folders you might have on the card) and extract the contents.
If you removed the card to reformat or unzip the file, put it back in the phone. It is a good idea to go ahead and soft reset the phone at this point, just in case some of the hardware has developed some issues while you were working.
Open File Explorer and navigate to Storage Card->Android, then click on CLRCAD.exe (it won't respond, but then it's not supposed to, click it anyway), then click haret.exe. Always run CLRCAD.exe before haret.exe to ensure you can actually hear phone calls
You phone should now show the HTC Penguin and a ton of text. The phone may hang a few times, but it's fine, just let it run.
Once Android has booted, follow the customization prompts. It may seem to take forever to boot, but let it go.
Once Android has completely booted and you can see the Home Screen, wait for the icon on the top left (sd card scan) to disappear and then soft reset and reboot Android. If you have run Android or used Google Backup in the past, wait for the sync icon to disappear before soft resetting the phone.
You should now be able to fully load Android and make calls, texts, data connections etc. Enjoy!
Details:
Myself, I chose to ignore the google location, facebook - twitter - youtube logins and weather; this is because I never intend to actually use the Windows Mobile ROM anyway
You may or may not have luck with a different radio, but I know people running stock are complaining and looking for replacements. I will not explain where to find or how to flash radios in this thread, use the search button above to find one that will.
My screen brightness is set to 50%, which is optimal for me. Un-checking the boxes will prevent your phone from darkening the screen while Android is running!
This seemed to help when I had issues with a very quiet speaker and ringtones running Android.
I will not link directly to the build because (1) it's not my site or work and (2) there are important messages on that page that DarkStone1337 wanted everyone to read. For your edification, the original thread: [BUILD] [18.08.2010] [darkstone HD2Froyo V2.1] [kernel: darkstone 2.6.32.9 #36]
I haven't used a stock ROM in forever, but all of the customs I have run had a "Format SD Card" app in the Start->Tools folder. If you use your PC to format it, be sure to use Fat with a 32 cluster (or allocation) size. Formatting your card will help to eliminate issues that some have been having (I had the same issues and reformatted later). I found that formatting the card via Windows allows for a less-buggy system.
This will create a new directory named Android and a small text file. You can read the "readme.txt" file if you want, but don't move anything around. Unlike the original builds, HaRET is located in the Android folder and should stay there.
If I get a call, text or email on my phone before I get Android booted, I go ahead and soft-reset again. It may be a pain in the butt, but it helps to narrow down any issues you might have to just the Android build.
Android may reboot your phone before you see any prompts, and if so just go back and run CLRCAD.exe and then haret.exe as before.
If you have any issues, reformat the card and start over. Here is where you need that initial data (internet) access. Android does not require you to always have internet, but if you reset or re-install it, you will always need it at this point.
You can turn off the phone by holding the "End Call" button (that's the red one ) and choosing "Power Off" from the popup menu.
Of course, you don't have to enjoy Android, that's just a suggestion
This tutorial is subject to updates and bug fixes in the future, but no promises
Be sure to read Post 2 for lessons I learned along the way!
Tips and Tricks
Format and Content of this post may change, depending on how I feel and what I learn along the way (respectively).
SD Card Care:
I would recommend you to always reformat your microSD card before installing or re-installing Android on it. This is the same as doing a Task 29 on your phone before installing a new ROM.
I don't know much about Android, but I've been using Linux on my personal computers at home for over 10 years. Android seems to continually read and write data to the SD card while the system is running. If it is in "write" mode and you change something on the card or reset the phone, it can damage your SD card. So far, I have managed to get through this by reformatting my card, but you can easily wipe the card by removing the battery or hitting the reset button instead of using "Power Off" via the Android menu.
Never attach your phone to the PC and activate "Turn on USB storage". When I say, "Never", I really mean, "If you ever, ever do this, your children will despise you." Writing to the card while Android is in "write" mode will cause data that is being written by Android to be misplaced and this is a very bad thing.
Do not use the "transfer to sd card" option that some of the apps may offer. For the same reason as the last tip, it will really screw your card up.
Android was not meant to run on external card like your microSD card. Some geniuses here on xda have managed to trick it into doing so, but it will never be safe. Some day the devs may actually manage to hack into the phone's NAND memory and then we can have real Android ROMs running without an SD card, but until then we have to use this system. You do risk ruining your card, but I feel that it is worth the risk
Stability:
Just after running HaRET, hit the back arrow key. This will cause your buttons to light up momentarily. I'm not sure exactly why, but this seems to help the battery drain issue a lot.
The current crop of Froyo (Android 2.2) builds all seem to cause issues with our phone's hardware. Specifically, the screen is often unresponsive, sometimes never waking up after being turned off and necessitating a hard reset or battery pull.
Bluetooth works, but you may have to cycle the service by hitting "Bluetooth" in a call twice, once to turn it off and then again to turn it back on. I have had to do this several times, particularly after a hard reset.
I find that a task killer is particularly helpful. I found a free one called "Advanced Task Killer Free" in the market and it works just fine for my needs. When I need to turn off the screen, I run the killer and wait a few seconds before hitting the End Call button. Using this method, I have reduced the non-responsive screen issues somewhat.
Another trick I have learned is to turn off the lock screen. Even the simple slider seemed to cause issues, so I found "No Lock", a free app in the market that, when activated, will turn off the lock screen. If you keep your phone in your pocket (bad idea, you're gonna scratch or break it!), this is not a solution you will be able to tolerate after a few butt-dials.
Some people over on the Leo forums report that turning off the Live Wallpaper helped with the non-responsive screen issues. I haven't really tried this because I really, really like the wallpaper interaction. Of course, since my issues haven't totally gone away, I gave that a shot, but it didn't seem to help.
I switched ROMs, trying to find a WinMo ROM that was lighter but still up-to-date and every call I made with the phone thereafter caused the "robot voice" (some call it the "android voice"). I am now flashing a new ROM that I found on the T-Mobile USA HTC HD2 ROM Development forum that said "Android" in the title. The chef claims it is "Android Safe" and so I've flashed it, but left the Android installation alone. The "robot voice" is definitely gone, so that's awesome. Not sure what else may have improved, but at least I can make phone calls
I've noticed a trend over on the Leo forums to shy away from "Best WinMo ROM for Hosting Android". Not sure why this is, but I will carry that trend on until I am better informed. That being said, I have flashed three different ROMs to my phone and only one has actually produced a stabilizing effect on my Android. You can find it in the T-Mobile USD HTC HD2 ROM Development forum, just search for "Android"
Apps:
Having trouble getting your apps to install? Try going into Settings - SD Card and "Unmount" your card and then try the install again. This worked for me when installing Angry Birds and Pocket Legends (two very awesome games).
"No Lock": This app disables the default sliding-lock screen. I had some issues early on with the screen locking up as I tried to turn it on. This has helped tremendously.
"Advanced Task Killer": Although cnet says this is rarely needed, they are not running Android from the SD card as we are You will need some sort of task killer because your phone can't handle the RAM drain every day activity brings.
"SlideIT Keyboard": Replacement for Swype. I've used Swype for so long that I consider this app a poor replacement, though you might disagree. It's better than nothing!
More to come!
Snarksneeze said:
Coming Soon!
This is just a placeholder while I get the real deal written. Please be patient, I have a 2yo to care for and my keyboard time is hard to justify these days.
Click to expand...
Click to collapse
Snarksneeze said:
Reserved.
Will put some lessons I learned in here later.
Click to expand...
Click to collapse
This just raises the question of why didn't you just wait until you had the tutorial written before creating this thread?
Paten said:
This just raises the question of why didn't you just wait until you had the tutorial written before creating this thread?
Click to expand...
Click to collapse
Sorry, I accidentally submitted my first post instead of previewing it. Had to work fast before I looked like a complete idiot. Guess I wasn't fast enough, eh?
Thank you for this post, Ive been wanting to do this for a while but the other threads were very confusing to me...
sound dll of 2.13.xxx.xx problem
hi i have the tmous rom 2.13.xxx.xx when i run android i have the robotic voice, i understand that the sound dll is different than the 2.10.xxx.xx and this is the couse.
is there any solution??
Did you ever try android on a stock rom? will any of these android set ups work in stock tmous rom?
אםזגםנש said:
hi i have the tmous rom 2.13.xxx.xx when i run android i have the robotic voice, i understand that the sound dll is different than the 2.10.xxx.xx and this is the couse.
is there any solution??
Click to expand...
Click to collapse
I actually had a custom ROM installed on my HD2 that caused the "robot voice". This ROM: {ROM}13Sep Omega WM6.5.x24634 Base3.04 manila2018#XT+Dinik+GTX+MaxSense+Black#Android is the only one I've been able to get a decent run of Android on.
We really, really need more than one option when it comes to ROMs that give Android good support, so if anyone else knows of one, this is a good thread to link it to.
szfjcr said:
Did you ever try android on a stock rom? will any of these android set ups work in stock tmous rom?
Click to expand...
Click to collapse
I tried two different stocks: The one my phone came with way back in June and the new one at tmobile.com/wm_update. I was able to make calls, but the other person couldn't hear me.
I would recommend the ROM I linked to in the post just before this one; it's working great for me so far!
gonna try it thanks
for some reason i cant get it to reboot into android, it keeps going back to the stock windows rom, anyone know how to solve this? thanks in advance
dementievafan said:
for some reason i cant get it to reboot into android, it keeps going back to the stock windows rom, anyone know how to solve this? thanks in advance
Click to expand...
Click to collapse
You might want to check this out: http://forum.xda-developers.com/showthread.php?t=723200
hmm so that is the only way to do it currently? what is the logic behind not being able to put android directly on the phone's memory?
thanks again
I'm one of the lucky ones!
So far at least... I have been running Darkstone Froyo/Sense for approximately six hours with zero issues beyond it taking a bit to get used to Android again, which is not a complaint at all.
As I stated, I used Darkstone Froyo with Sense, latest release.
2.11 Radio
I did not have to revert my rom because I was able to use HSPL3 Successfully.
I have read several threads/posts but this was the most helpful, although I could not have completed this task without some other [TUT] threads.
Side note: I stated I have not had any issues, I wanted to mention that I had read some posts stating the 2.11 Radio had caused heat issues. With heavy downloading of apps, chatting, texting, and browsing constantly for the last six hours (as I was a passenger on a long drive right after I completed the install) I never noticed the phone getting hot, and I made a point to watch for this.
Again, thank you.
dementievafan said:
hmm so that is the only way to do it currently? what is the logic behind not being able to put android directly on the phone's memory?
thanks again
Click to expand...
Click to collapse
Apologies to everyone for not responding to this thread while on vacation in Arkansas.
In order to install Android on the HD2 as a regular ROM we would need access to the NAND processor, which we do not have at this time. We may never be able to get Android to flash that way. In the meantime, we can run it via Linux by using HaRET (Hardware Reverse-Engineering Tool). As far as I can tell, this is the API version of Froyo, the one that can be run via an emulator and downloaded from Google. So it's not really the phone version of Android, but from a user's standpoint, there is no difference.
electshrimp said:
So far at least... I have been running Darkstone Froyo/Sense for approximately six hours with zero issues beyond it taking a bit to get used to Android again, which is not a complaint at all.
As I stated, I used Darkstone Froyo with Sense, latest release.
2.11 Radio
I did not have to revert my rom because I was able to use HSPL3 Successfully.
I have read several threads/posts but this was the most helpful, although I could not have completed this task without some other [TUT] threads.
Side note: I stated I have not had any issues, I wanted to mention that I had read some posts stating the 2.11 Radio had caused heat issues. With heavy downloading of apps, chatting, texting, and browsing constantly for the last six hours (as I was a passenger on a long drive right after I completed the install) I never noticed the phone getting hot, and I made a point to watch for this.
Again, thank you.
Click to expand...
Click to collapse
Thanks for your feedback
You mentioned that you could not have completed the install without other tutorials. Would you mind linking to them or telling me what I am missing?
To write this, I reformatted my SD card and installed a fresh ROM, then detailed each step I made along the way. I have looked back but can't see anything that I might have missed.
I see that you are running Froyo Sense. I linked to the regular Froyo, since it was the version that ran without any issues for me. Would this TUT be better if I were to link to the other builds as well?
Thanks for this [TUT]! I have this installed with Omega v13 and Radio 2.12.50.02_02. Works beautifully.
I also added Dual Boot option with Jmz Android Dual-Boot.cab as suggested by you in an earlier post. Very sweet.
wackywalt said:
Thanks for this [TUT]! I have this installed with Omega v13 and Radio 2.12.50.02_02. Works beautifully.
I also added Dual Boot option with Jmz Android Dual-Boot.cab as suggested by you in an earlier post. Very sweet.
Click to expand...
Click to collapse
Glad things worked out for you!
Keep us informed of any issues, tips or tricks you stumble upon as you enjoy your new Android
i have a few questions
im new to HD2, i want to run android on tmous unlocked hd2, i have stock rom no hspl, my spl version is 2.10.8 or something like that ... so how can i do it. Help appriciated
rukhi said:
i have a few questions
im new to HD2, i want to run android on tmous unlocked hd2, i have stock rom no hspl, my spl version is 2.10.8 or something like that ... so how can i do it. Help appriciated
Click to expand...
Click to collapse
Stock simply doesn't work for Android. You can boot up, but can't make calls or hear external sound.
In order to get Android running, you will have to (1)Flash HSPL and (2)Flash an Android-friendly ROM.
I am far from being an expert on Android or Windows Mobile, so there may be something that I don't know about. If you are dead set on keeping stock, you might contact one of the Android-friendly chefs and ask them what changes they made to their versions.
Don't forget: Flashing your T-Mobile HD2 is dangerous. Never flash a ROM unless you found it here: T-Mobile USA HD2 ROM Development.
The original (Leo) HD2 is incompatible with the T-Mobile version and it is easy to get confused. Some websites aren't even bothering to mention the incompatibility and lot of folks are bricking their phones as a result.
Should I back up what I feel to be a problematic installation and copy it to another (higher-quality) SD card, or just start with a clean slate?
Here's the situation: Up until about 2 weeks ago, my installations of CM7 nightlies (using vergreen's SD installer) were working relatively well, albeit with the occasional crash and PBD. But recently, I've been having issues that just don't go away. I average maybe a day and half of battery life under what I feel to be light-to-moderate use, I get kernel panics (sometimes when my NC is just sitting there doing nothing), every third reboot or startup the CM7 logo animation just cycles, and when it does boot up it's a coin toss as to whether it'll run smoothly or I get a ton of FCs of downloaded apps and/or Framework.
As you can guess, this is getting frustrating and serves to make my friends with iPads be all smug about how stable their devices are. On the one hand, yes, I'm using nightlies and those come with a large risk of instability. But on the other hand, I had been using said nightlies for a while with few problems. Plus, I've heard of the issues people have with lower-quality SD cards, and a lot of those issues match what I'm getting with my current build. I've already gone ahead and bought one of the recommended Sandisk cards, which is currently sitting idle. In the meantime, I haven't made a lot of tweaks to either my CM7 installation or my apps, and very few of them have any data that I feel is even worthy of a backup. However, if a clean install could affect, say, any future devices being able to connect to my Google account, then I would be a lot queasier about just blowing everything away and starting again on a new card.
So, what's the opinion of the group? Either way, the install will be going on the new card, I'm just trying to figure out if it's worth it to keep things the way they are.
I would start from scratch. Things always work better that way.
Actually, I would also recommend you run cm7 from the EMMC. I was never satisfied with cm7 on an sdcard. Runs smoother, and less headaches/issues with sdcard management - transferring files, updating nightlies etc.
If you like the stock software, look into the dual-boot option ...
jasoraso said:
I would start from scratch. Things always work better that way.
Click to expand...
Click to collapse
That's what I've been leaning towards (if that wasn't obvious in the post), but I'm just seeing how others feel. Thanks.
Actually, I would also recommend you run cm7 from the EMMC. I was never satisfied with cm7 on an sdcard. Runs smoother, and less headaches/issues with sdcard management - transferring files, updating nightlies etc.
If you like the stock software, look into the dual-boot option ...
Click to expand...
Click to collapse
I do use the CM7 boot menu, but I've chosen SD because (a) I can use more space with a bigger SD card, and (b) I like having an immediate "out" if something goes pear-shaped. If my SD card stops working, at least with stock I can still get on the internet and read e-books.
I have owned several tablets, Augen ZT180, NC, GTAB etc.
Currently we have 2 NC in the house, one my wife has and uses 50% stock and the other 50% she boots off an SD card( shes not ready to commit)
the other is my son, his is a very happy 100% CM7
however, we just bought one for my mom (80+), mostly as an ereader, BUT with the ability to read emails and watch video of the boy and see pix.
Since it was a group by the rest of the family is not quite ready to let mom loose with Android, so its still stock 100%
However that being said there are somethings that I have been asked to do, to help prep it for Xmas that I dont have a clue on, and Im on a limited TIME budget.
I would love to install a file manager, for ease of navigation, no matter what I grab it either wont install or wont 'execute' (cant find it even though it says its installed).
Then of course there is the issue of installing ANYTHING else.
I LOVE XDA and have learned a GREAT deal here, so Im sure all my questions are SOMEWHERE but my searches havent found what I need. I guess most folks, boot from a card or go all in. Truth is with her arthritis my mom couldnt hold a card.
I REALLY like the NC, and think its a great device, if I "root" the NC will it boot as android or will it just be a 'rooted NC'? If I do have a rooted NC, what are the advantages?
I know most of you guys are busy writing new FW to make these tablets as awesome as they can be (and hats off), but if anyone can point me in the right direction I would be very greatful.
Thanks
J
The nook boots android whether you root it or not. Rooting just gives access to more of the features (a key one being market). I would probably set it to boot from the card and then load the apps and features you want her to use to the homescreen and maybe use parental controls to block the market, settings and anything else that she might get confused by.
You might consider MiUi from an SD card. It is a simple interface, reasonably large icons and runs well if you use a class 2 or 4 Sandisk card. It is an iPad-like interface, i.e. it doesn't use an app drawer. Everything is on the home screen(s).
New NC w/1.3 did BN stock update to 1.41, confirmed all working. Then I applied the manual nooter 5-12-20 using CWM sd with no errors or issues in installing/rooting/booting. A couple issues/observations after successful booting.
Posting here as new user hoping other new users in same boat without enough time on forum to be allowed to post to the dev thread (I've read every page of the thread and every post since 5-12-20 was released mult times so can say these questions/observations are either not observed or observed and not definitively answered that I could find).
A couple observations and questions:
1. At least 2 other posts noting issues with WiFi.....mid-usage wifi just drops goes dead and I have to manually connect - only started after applying 5-12-20 - is there a fix or something more I can contribute testing?
2. Damned market. Seen many posts relating to market - some claimed to "fix" by re-rooting after going back to stock (doesn't make sense since I observed no errors in the process). My market launched, then updated fine. I, however like others saw many common apps simply not there like Google's own Voice app, facebook app, etc. Maybe someone can tell me, should my rooted nook color NEVER even see those 2 apps in the market? If it should, something went wrong. **Yes, I went back to page 1 of that thread and applied the "market visibility fix" which really needs to be updated to say you MUST uninstall the market "update" to roll it back to the original rooted market then apply the steps - then yes, it worked in the sense that all apps EXCEPT for some pretty BIG ones like facebook, google voice, etc are listed. This one is the primary reason I'm rooting and I've read a LOT of different "fixes" of changing DPI, fingerprint, build.props, etc. yet in any of the original root instructions seen an indication that this is a STANDARD action every rooter needs to take. Why do some need this "workaround" of hacking dpi and props and some don't? Is it simply that those that don't are not using these very common apps like facebook? Someone could make my day by helping out with this as I really hate doing things half-assed and having something half-working.
3. Power consumption seems a bit higher than pre-MN-root which leads me to next question - the MN rooting process installs "google latitude", "navigation", and what appears to be phone processes. Without a gps or location services I can't seem to get these nav type apps to work (hang at aquiring location), is there a reason they are installed and is there a way to make them work? Can any of the phone/dialer type daemons be removed could any of them be increasing power consumption? Again, I'm game for testing if a dev can shed some light.
4. Basic question but one I saw people had app "updating" issues with but no clear answer as to best practices. If an app is available in both BN store and android market, are there pros/cons to installing one vs other? Netflix good example installed via BN store yet market says update when BN store does not.
5. Dual-booting - seen different threads but they are dated to older firmware and with the awesome job GMPOWER did putting together 5-12-20 MN, would love to help him or the devs test and put together a step by step rolling his 5-12-20 MN and current 1.41 in with whatever the best practices are for setting up a dual boot with CM7, etc.
Again, you guys rock and I love the NC, any help on these would be greatly appreciated!
I'm new here too,but I might have a simple solution to question #1.If you're "dropping WiFi" at home,check the channel your router is using and see if a neighbor (or two or three)are also using that channel."Sniffer" programs are around that will give you the info.Try to set yours up on a "clear" channel.Worked for me when the neighborhood "filled up" with routers all set to channel 6.Went to ch.3 and problem solved.
Good luck.
Thanks but as I stated only after the manual nooter is the wifi dropping - no need to get out wireshark when 4 other wifi devices including a non-rooted nook in the same room without dropping but thanks for the suggestion!
BTW, I should ask are you rooted and which version, etc?
WyldWolf said:
[...] 1. At least 2 other posts noting issues with WiFi.....mid-usage wifi just drops goes dead and I have to manually connect - only started after applying 5-12-20 - is there a fix or something more I can contribute testing?
Click to expand...
Click to collapse
I did not experience this issue. In fact, on B&N 1.4.1, my wifi was more dependable than on CyanogenMod. I suspect a lot of has to do with specifics on your wifi setup, including router make, security used and so forth. You could try tweaking parameters to see if it helps. Was it dropping as much before you ran MN? I wouldn't expect what was done with MN to make a difference. Are you using Dalingrin's kernel or anything similar?
2. Damned market. Seen many posts relating to market - some claimed to "fix" by re-rooting after going back to stock (doesn't make sense since I observed no errors in the process). My market launched, then updated fine.
Click to expand...
Click to collapse
Hmm. I never got around to trying Google Voice, and have no use for Facebook, so can't say for sure those were there. I've since nuked 1.4.1, so can't test now either. I can say that I had well over 100 apps that I commonly use on CM loaded, and didn't find any that I weren't visible in Market without any tweaks. It did take a long time for Market to update, but after that, it worked smoothly. You might try accessing the Market via the web interface and see if those apps will install from there. I did that a few times. Maybe that trips something?
3. Power consumption seems a bit higher than pre-MN-root which leads me to next question - the MN rooting process installs "google latitude", "navigation", and what appears to be phone processes. Without a gps or location services I can't seem to get these nav type apps to work (hang at aquiring location), is there a reason they are installed and is there a way to make them work? Can any of the phone/dialer type daemons be removed could any of them be increasing power consumption? Again, I'm game for testing if a dev can shed some light.
Click to expand...
Click to collapse
My power consumption was initially very good, but after a week or so, I started seeing the battery drain go to 3-5% per hour. Unfortunately, 1.4.1 hobbled a lot of troubleshooting tools, so I wasn't able to nail down the culprit. This is what ultimately drove me to abandon 1.4.1 for CM again.
I did try renaming phone.apk and others that have been recommended, but my NC seemed to get very unstable thereafter. Lots of spontaneous reboots and the like. I put them back and really didn't see a big difference one way or the other that I can attribute to these. From everything I've read, they're not likely to cause noticeable drain, but some other standard functions depend on them.
4. Basic question but one I saw people had app "updating" issues with but no clear answer as to best practices. If an app is available in both BN store and android market, are there pros/cons to installing one vs other? Netflix good example installed via BN store yet market says update when BN store does not.
Click to expand...
Click to collapse
Cost is probably the main factor. Netflix from B&N supposedly supports HD while the Market version does not. On a 7 inch screen, I couldn't care less. Netflix off of the Market looks pretty good, so I'm happy.
5. Dual-booting - seen different threads but they are dated to older firmware and with the awesome job GMPOWER did putting together 5-12-20 MN, would love to help him or the devs test and put together a step by step rolling his 5-12-20 MN and current 1.41 in with whatever the best practices are for setting up a dual boot with CM7, etc.
Click to expand...
Click to collapse
What you do to stock is pretty much independent of dual-booting.
Bobstro,
Thanks so much for the input! As for the wifi, it does seem very specific to after I ran the MN on 1.41, in fact it never once dropped and I went back to stock 1.41 for the last day and haven't seen it drop again (my wife's is stock 1.41 and doesn't drop either when my MN does so unless it's a hardware issue I'm guessing it's something in the MN process, driver, etc.)
One weird thing I did have happen and searching found a couple references but nothing definitive was using CWM 3.2.0.1 flashing the 1.3 stock after formatting system, data, cache multiple times was my touchscreen did not work. I even re-downloaded the 1.3 from xda must have flashed 6 times never worked. Then downloaded a 1.41 posted on one of the recovery xda threads and lo and behold my touchscreen worked. Also, unlike the 1.3-1.41 upgrade, when I flashed right to 1.41 a couple things came up that didn't after upgrading mine and my wife's to 1.41, namely netflix right on the home screen touch to install, and the nook friends app right on the home screen.
Have you come across anything that would indicate why my touchscreen went dead no matter how many times I rebuild the CWM card, formatted the nook partitions correctly and flashed without error? It really made me worry I had a bad unit but like I said worked out of box, worked after 1.41 upgrade, worked after latest MN, only once I returned to 1.3 stock did it die until flashing 1.41 directly.
Interesting about the market, I did have thousands of apps just not some of the most common big ones and I did try through browser it told me facebook was incompatible with my device which led me to all the "hack the dpi, props file, etc." threads I just didn't want to be part of a minority for for some unknown reason had to hack workarounds if 99% of folks running the MN could simply install facebook and google voice from market without workarounds.
Thanks again!
Edit: on the dual boot I thought there was a way to install CWM or something to internal to allow dual internal booting from stock (nootered) and CM7 - I'll keep looking.
WyldWolf said:
Thanks so much for the input!
Click to expand...
Click to collapse
I'm happy to help where I can. The smart folks here on XDA have helped me tremendously, so I trying to pay it forward as best I can!
[...] One weird thing I did have happen and searching found a couple references but nothing definitive was using CWM 3.2.0.1 flashing the 1.3 stock after formatting system, data, cache multiple times was my touchscreen did not work. I even re-downloaded the 1.3 from xda must have flashed 6 times never worked. Then downloaded a 1.41 posted on one of the recovery xda threads and lo and behold my touchscreen worked.
Click to expand...
Click to collapse
EDIT: Sorry about that strange post. I wanted to point you to the thread about the hardware having changed with more recent NC versions. 1.4.1 includes the newer drivers. Depending on where you get your older versions from, they may or may not work.
Well that 'kinda" makes me feel better that I at least don't have bad hardware, had I known the 1.3 that's posted was "different" then the 1.3 that came on my newer unit apparently must have had the newer screen drivers I would have backed it up - surprised someone hasn't posted it. I mean, mine came with 1.3 installed and the screen worked so it must have had the newer driver until I wiped it, right?
Also, do you have the links you referred to for the screen issues thread?
Thanks again!
The ongoing discussion I referred to is here. On page 2 or so, I've got a link the the original post.
HimWill said:
I'm new here too,but I might have a simple solution to question #1.If you're "dropping WiFi" at home,check the channel your router is using and see if a neighbor (or two or three)are also using that channel."Sniffer" programs are around that will give you the info.Try to set yours up on a "clear" channel.Worked for me when the neighborhood "filled up" with routers all set to channel 6.Went to ch.3 and problem solved.
Good luck.
Click to expand...
Click to collapse
Do look at WiFi, Once I Locked it on channel 1 it is rock solid reliable.
Bobstro,
I'm guessing your battery life must be a typo, at 10% an hour discharge would be 10 hours of runtime - they advertise 8. 3-5% sounds awfully low. Mine out of box is at about 10% an hour with wifi on and screen at 30% with constant online web browsing, maybe an app or two install, launching in and out of system apps, etc. - constant "activity" on my part not just flipping book pages or watching a video, etc.....I hope my unit is on par with others.
I also noted that my wife's refurb bought about thanksgiving that does not have the "new" screen hardware mine does actually looks side by side more blue/white with mine slightly yellower tinge which annoys me a bit. I know from years of jailbreaking and swapping iphones that there was definitely a difference in screen colors as they went from the 3g to the first 3gs I had, same thing blueish/whiter to a more yellow tinge - I can't win! LOL
Ah, sorry for the ambiguity. That was 3-5% while idle with screen off, which is far worse than normal. I expect to see 4-6% drop while idle with screen off overnight, max.
While in use, consumption is roughly 10% per hour, and mostly due to screen, which I usually run at 25%.