1.1 is here! - Nook Color General

It looks like the 1.1.0 update is now available. Not sure what it includes yet.
h t t p ://w w w.barnesandnoble.com/u/nookcolor-support-software-update/379002520/?cds2Pid=35505
Thanks,
Matt

Now with froyo. I am probably not going to try out this update.

It looks like there is a lengthy discussion about this in the Developer section, you should probably check that out for more info.
Thanks,
Matt

Can I install ver. 1.1.0 after rooting or it's dangerous for Nook Color?

It indeed seems to break rooting.
However for me most important it has sorted out the Sound Issue once and for all. Now I can put it in and out of standby, and sound is always there after it wakes.
Also flickering has been addressed seemingly by upping the refresh rate.

It would be nice to see 1.1 version rooted soon ... I think blocking OTA updates is kind of an option no one wants - especially if there are bugs to address.
I have not rooted my nook col. as it is going to be a gift to my brother who does not care about tablet - but reading 100%... however, getting another one is very likely to be an option for my life which I will probably root... Now, if something comes our way like it did for HD2 where we can load SD Card based Android builds - it would be AWESOME

eenbox said:
Now, if something comes our way like it did for HD2 where we can load SD Card based Android builds - it would be AWESOME
Click to expand...
Click to collapse
Umm, unless I don't understand what you are asking for, we already have SD Card based Android builds that work just fine!
http://forum.xda-developers.com/showthread.php?t=883175
http://forum.xda-developers.com/showthread.php?t=922324

Damn. How do I block this update for good? It looks like it's an automatic thing.

A. Nonymous said:
Damn. How do I block this update for good? It looks like it's an automatic thing.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=930382
Try that, but nobody is 100% sure it'll actually not download and install the OTA.
Do delete the file in /media if it's already downloaded though.

Not real confident any of the re-editing approaches are going to actually prevent the update. If they do, great. Fortunately, it looks like a couple of developers are already working on methods of rooting 1.1. They seem mostly to be using CWM and update.zips though. Haven't heard anything from the Autonooter developer yet, but he may be working on solutions as well.

Related

[ROM] Final Froyo Release for Obsidian by CCRoms V2.02 Next Up Gingerbread

Welcome to the final release of Froyo, by the CCRoms team, which means you guessed it, we're switching gears to Gingerbread after this release. With this release we managed to get the Evo/Emerald going as intended(sorry for the wait.) The Galaxy S style pulldown power widget has been implemented in this release as well. Gem settings have been completely re-written as well, to provide a more intuitive and easier to understand interface for everyone, and of course bug fixes abound.
downloads available at: http://www.ccroms.net
Note:
Droid X users, at this point there is nothign more we can find to do to improve battery life. When/If the battery starts to drain fast, gets sluggish, or gets hot, reboot the phone this will put the race condition causing all of these problems back to sleep, unfortunately there is no way to put the process back to sleep once it wakes up and if you kill the process kernel panics and the phone reboots anyway.
sniffle said:
Welcome to the final release of Froyo, by the CCRoms team, which means you guessed it, we're switching gears to Gingerbread after this release. With this release we managed to get the Evo/Emerald going as intended(sorry for the wait.) The Galaxy S style pulldown power widget has been implemented in this release as well. Gem settings have been completely re-written as well, to provide a more intuitive and easier to understand interface for everyone, and of course bug fixes abound.
downloads available at: http://www.ccroms.net
Note:
Droid X users, at this point there is nothign more we can find to do to improve battery life. When/If the battery starts to drain fast, gets sluggish, or gets hot, reboot the phone this will put the race condition causing all of these problems back to sleep, unfortunately there is no way to put the process back to sleep once it wakes up and if you kill the process kernel panics and the phone reboots anyway.
Click to expand...
Click to collapse
How do you plan on bringing gingerbread to the droid x when we won't have the proper kernel to take advantage of it?
Are the "known issues" (GPS, camera/camcorder, etc.) fixed in this release?
avlfive said:
Are the "known issues" (GPS, camera/camcorder, etc.) fixed in this release?
Click to expand...
Click to collapse
No they are not. It shows all the known issues from the dl link posted above
bravo1234 said:
How do you plan on bringing gingerbread to the droid x when we won't have the proper kernel to take advantage of it?
Click to expand...
Click to collapse
for the record, a kernel is nothing more than a core piece of low-level software that executes other programs and provides access to the hardware. nothing says that when you upgrade an android version you MUST upgrade the kernel as well, if anything you just might need to modify how android interfaces with the hardware to match the old kernel interfaces.
joebob296 said:
No they are not. It shows all the known issues from the dl link posted above
Click to expand...
Click to collapse
Saw that, just didn't know if it hadn't been updated quite yet. Too bad. I'm still waiting on these to be fixed before I can jump back in. LOVED the ROM though.
avlfive said:
Saw that, just didn't know if it hadn't been updated quite yet. Too bad. I'm still waiting on these to be fixed before I can jump back in. LOVED the ROM though.
Click to expand...
Click to collapse
Those are all a must for me at least
Sent from my DROIDX using XDA App
I don't understand the gps issue or the camera issue. If there was fine GPS and a camera i would love the fact it is AOSP however not that i use them all that often but if i loaded it i would inevitably need one or both. and its still beta if you can't get a totally stable and working froyo rom how will you ever get the GB stable. Will the kexec(?) be used to use custom kernels to make the gps and camera work?
I just booted this up seemed ok other than the problems known but for some reason it wouldn't let me download anything from the market said I didn't have enough room.... Idk y that happened
Sent from my DROIDX using XDA App
Funnyface19 said:
I just booted this up seemed ok other than the problems known but for some reason it wouldn't let me download anything from the market said I didn't have enough room.... Idk y that happened
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
same here. it's been reported in other obsidian forums too. i was able to get around it by using an older version of market. i installed cm gapps instead of obsidian gapps. The cm gapps had a version of market from 2 month ago. everything worked fine. then i updated my market to 2.2.11 and the "There's not enough room..." error message was right back again.
other than that, i really love how clean and fast this rom is. thanks a ton cvpcs and best of luck with the cyanogenmod team.
any pics of the drop down toggles???
tttuning said:
any pics of the drop down toggles???
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=RbKJy6MPUz0
cvpcs said:
for the record, a kernel is nothing more than a core piece of low-level software that executes other programs and provides access to the hardware. nothing says that when you upgrade an android version you MUST upgrade the kernel as well, if anything you just might need to modify how android interfaces with the hardware to match the old kernel interfaces.
Click to expand...
Click to collapse
what...? What!? That is completely wrong... Nothing says you have to upgrade the kernel... unless Gingerbread uses modules not currently in the present kernel, which I can pretty much guarantee it will... Your statement could hold true for something such as minor update like 2.2 to 2.2.1 as we saw earlier, but would very like cause many things to not work come gingerbread. A good example is the previous hacked upgrades of 2.1 to 2.2 back before the proper kernels were released (specifically in memory of the HTC Incredible) sure, 2.2 could run without the proper kernel, of course your WiFi wouldn't work, GPS didn't work, if you tried to run the 720p camera it would crash, as well as several others that I cannot remember as of this moment. The kernel is not "just a low level piece of software" it is the backbone of your entire system, especially when it comes to the system talking with the hardware itself.
I think Taco that you should reread CVPS post. It stated this...
"nothing says that when you upgrade an android version you MUST upgrade the kernel as well"
Which is what you said was wrong, then said the same thing following it.
So how is the rom working for everyone? or it's pretty much dead..
ram130 said:
So how is the rom working for everyone? or it's pretty much dead..
Click to expand...
Click to collapse
I think it was pretty much dead on arrival when it said the camera & camcorder didn't work...that's kind of a mandatory feature of any smartphone.
If it's been fixed...then they're lame for not updating the page noting the bugs.
JagoX said:
I think it was pretty much dead on arrival when it said the camera & camcorder didn't work...that's kind of a mandatory feature of any smartphone.
If it's been fixed...then they're lame for not updating the page noting the bugs.
Click to expand...
Click to collapse
Well that sucks ..development on this phone is so slow..
The worst part is the x HAD so much potential, do to great things. I have watched this forum since the day the x launched and the sad thing is that the tbolt is only 6 days old right now and has a much larger devwlopment thread than the x has had at any point. Sad to say it but i think moto phones are done in the development community.
Sent from my ADR6400L using XDA App
ksizzle9 said:
The worst part is the x HAD so much potential, do to great things. I have watched this forum since the day the x launched and the sad thing is that the tbolt is only 6 days old right now and has a much larger devwlopment thread than the x has had at any point. Sad to say it but i think moto phones are done in the development community.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
The X development has all but ceased from what I can see. Such a bummer since I'm stuck with it for another year and a half. Hopefully we can see a few updates to some ROMs once gingerbread rolls around for the phone, but after that I don't see much reason for hope.
True...so what was the most annoying issue with this rom? Im thinking about flashing it. Im on 3.4.2 now.
Also you can sell your DX on swappa.com then pay the difference and get a htc.

With new update pending, what is best way to block OTA updates?

I've seen modifying build.prop, using sqllite, and changing the name of the otacerts file. Doesn't seem build.prop is valid here until someone gets a hold of one with the new update. But I don't want to lose my root. So, what's the consensus? (please vote in the poll)
Here are the 3 mentioned:
1. Rename OTA Certs
2. Use Sqllite
3. Edit Build Prop
The build.prop is sort of experimental but seems to be working so far from reports.
The consensus is definitely to read the other 1000 threads on the subject before starting yet another one.
Really? There are 1000 other threads that compare all 3 options?
All the ones I read are where someone brings up one thing and then a few other people chime in on a different one. I was trying to find out, in one place, what the most recommended one was.
It is my fault for not creating a poll at first.
It is your fault for being a jackass.
ADude said:
The consensus is definitely to read the other 1000 threads on the subject before starting yet another one.
Click to expand...
Click to collapse
I'd say he's read the 1000 threads, given the fact that he rattle off a list of suggested solutions from those threads.
FWIW, I too am interested in knowing if this issue has been settled. Just rooted my NC the other night, am really enjoying all teh apps I've downloaded and would be happy to block updates and wait for a rooted 2.2 update.
So if anyone knows the definitive answer ot the OP's question, please do let us know.
for what it's worth
doncaruana said:
I've seen modifying build.prop, using sqllite, and changing the name of the otacerts file. Doesn't seem build.prop is valid here until someone gets a hold of one with the new update. But I don't want to lose my root. So, what's the consensus?
Click to expand...
Click to collapse
Don,
I haven't read the reputed 1,000 other posts on this topic, so I don't know what consensus may have been reached there, but this is my take on it:
- otacerts renaming isn't going to be reliable
- the sqllite fix (modding the fota.mode item) is a permanent fix, which eliminates any possibility of OTA updates creating problems
- modding build.props may work, even if you don't have a master to reference from.
I.e., some reasonable higher settings for ro.build.version.incremental, ro.build.description, and ro.build.date MAY do the trick, even if they're not a clone from a legit updated version. I don't know (perhaps someone else does) if perhaps only one of those is really necessary, E.g., something like ro.build.description=2.1.0.428.int.enc.rrdp.s39975 may be enough to do the trick, since it holds the main versioning string (currently at 1.1.0.328).
So my recommendation if you want to be sure would be to do the sqllite fix.
- Mark
Flash CM7..... problem solved
I added links to the 3 methods I mentioned, for everyone's reference anyway. I did also read somewhere that someone said that installing CMR would stop OTA updates as well. But didn't see a lot of discussion about that.
xwint3rxmut3x said:
Flash CM7..... problem solved
Click to expand...
Click to collapse
I don't think CM7 is ready for prime time on the NC. Last I saw video driver and flash still had issues. I too would like to see a 2.2 stock update so it could be rooted. BTW I am running Nookie Froyo right now and it is pretty sweet.
I tried the CM7 Agnostic SDCard option and nightly build and, well... did I mention it isn't ready for prime time?
But I am one of those fringe lunatics that never says anything important, never gets noticed, and is instantly marginalized. I'll likely die an early death and no one will notice...
Sorry, to get back on topic, I don't think CM7 is ready yet for Nook Color.
Nothing to see here, move along.
migrax
Agree. CM7 is not quite up to where it needs to be as a daily driver.
build.prop flat out works... End of story.
Of course someone needs to get the build.prop from the new one when it's released, so if you're really scared about it, stay off wifi I suppose. But it usually takes a while before people start getting it.
khaytsus said:
build.prop flat out works... End of story.
Of course someone needs to get the build.prop from the new one when it's released, so if you're really scared about it, stay off wifi I suppose. But it usually takes a while before people start getting it.
Click to expand...
Click to collapse
The build prop only blocks one update. In order to block the Froyo update, you'd need the build prop for the Froyo update. That would only work until there is another update. Then you need the build prop from that update to block it. It becomes a vicious, never ending cycle. I may be incorrect in my understanding though.
I don't think anyone really knows at this point which is why there are "1000 threads" on the topic. We just all have to sit back, drink a beer or 7, and wait until the next update is being pushed out. I personally went with the SQlite edit in Root Explorer. Seemed like the easiest way to me.
Pre-dawn raid said:
I don't think anyone really knows at this point which is why there are "1000 threads" on the topic. We just all have to sit back, drink a beer or 7, and wait until the next update is being pushed out. I personally went with the SQlite edit in Root Explorer. Seemed like the easiest way to me.
Click to expand...
Click to collapse
That's what I'm going to try. I found the entry, but haven't changed it to "manual" from "auto" yet.
Update questions
I'm running Android 2.1 on my rooted Nook Color. What will happen if I don't block Barnes & Noble's upcoming update in April? Will my NC merely become unrooted and operate like a regular stock Nook Color? Is it possible that any damage will be done to the NC?
I'm actually curious to see exactly what an updated, unrooted NC will look like and how it will operate. I know that somebody eventually will come up with a way to root an Android 2.2 Nook.
My rooted 1.0.0 NC (Dec. ~8 autoroot) ignores the updates *DOING NOTHING AT ALL*. I can use the Market, download books from BN, etc.
Knock on wood!
cameraz said:
I'm running Android 2.1 on my rooted Nook Color. What will happen if I don't block Barnes & Noble's upcoming update in April? Will my NC merely become unrooted and operate like a regular stock Nook Color? Is it possible that any damage will be done to the NC?
I'm actually curious to see exactly what an updated, unrooted NC will look like and how it will operate. I know that somebody eventually will come up with a way to root an Android 2.2 Nook.
Click to expand...
Click to collapse
From what I've read on other Andriod devices, it relocks the device and you lose superuser. Still, I'm curious if all the apps I downloaded with root will work after the update. The device was a b-day gift for my sister and she really loves the e-reader aspect, hence why HC and nookie froyo haven't been slapped on there.
Well, if you run the stock launcher on a rooted Nook, you still see all the apps you have downloaded from Market in Extras. So I would assume that the 2.2 upgrade could preserve the apps you have on there. Though, I would always recommend doing a backup, getting updated, wait for whatever exploit is employed and re-enable your apps.
colorado_al said:
Agree. CM7 is not quite up to where it needs to be as a daily driver.
Click to expand...
Click to collapse
Don't tell that the to hundreds of CM7 users running this as a daily.
Honestly, the only functionality "hurting" right now is video performance, as caused by an audio wierdity. Past that, I can't think of alot of broken stuff CM7 needs fixed. Sleep battery performance can be improved i guess... as it is, i like CM7 ALOT more than Froyo (no more SOD!)
migrax said:
I don't think CM7 is ready for prime time on the NC. Last I saw video driver and flash still had issues. I too would like to see a 2.2 stock update so it could be rooted. BTW I am running Nookie Froyo right now and it is pretty sweet.
I tried the CM7 Agnostic SDCard option and nightly build and, well... did I mention it isn't ready for prime time?
But I am one of those fringe lunatics that never says anything important, never gets noticed, and is instantly marginalized. I'll likely die an early death and no one will notice...
Sorry, to get back on topic, I don't think CM7 is ready yet for Nook Color.
Nothing to see here, move along.
migrax
Click to expand...
Click to collapse
I'm with you. Tried the CM7 from SDCard yesterday. It was okay, but it didn't exactly rock my world. Waiting for all the bugs to get worked out. In the meantime, sticking with Nookie Froyo.
Divine_Madcat said:
Don't tell that the to hundreds of CM7 users running this as a daily.
Honestly, the only functionality "hurting" right now is video performance, as caused by an audio wierdity. Past that, I can't think of alot of broken stuff CM7 needs fixed. Sleep battery performance can be improved i guess... as it is, i like CM7 ALOT more than Froyo (no more SOD!)
Click to expand...
Click to collapse
I skipped over Nookie Froyo, but I used stock Root for awhile, and i've been on Cm7 for awhile and I love it. I agree video is not at 100% on cm7, but I really don't spend alot of time watching video on my nc at all. I downloaded the nook app from the market, and the tablet works great. The devs have done a great job, I have no issues using CM7 as my daily driver.
Gotta back you up madcat since we're the only pro CM7 users on this thread

NOOK Color’s update to Android OS 2.2/Froyo

B&N Update Next Week?
Just showing you the link:
http://androidos.in/2011/04/nook-co...-update-on-april-25-froyo-incoming-with-apps/
Doubt it. Would be all over the internet if it was (Engadget etc). Seems like a shady site.
I saw the same thread earlier today on the Barnes and Noble site.
I cannot post the link but title of the thread is "Monday it is"
http://bookclubs.barnesandnoble.com/t5/NOOKcolor-General-Discussion/Monday-it-is/td-p/970372
Look at post #6 in that thread. "Go to B&N if you need help with anything." Yeah right im going to make a trip to Barnes and Noble and tell a representative that i don't fully understand how to use the new update LOL.
I too heard the chatter, it might actually be monday. Let's hope they come out with a newer kernel. The one we have is kind of getting old.
I just hope the update contains something of use to the community that it doesn't already know -- like being able to use Bluetooth beyond a couple of feet.
Just as interesting as the date is the content. If you keep reading that thread, you get a link to another thread where they say a manager actually saw (and shared) the update: She shared what she saw....WOW. Flash, new PDF and lots of aps.
Monday will be interesting: if the updates actually comes, will it manage to get past the OTA blocking?
Just calm down and relax,if you're looking on the B&N Community board there's daily some folks that fool around those update.
Does anyone know if this update could maybe increase app compatibilty due to an official update to froyo such as Homerun battle when we get it rooted with android market and/or sideloading? Cause that would be the only reason I'd have for updating.
It will be interesting
Agree. It will be what it will be. But to be on the safe side, I've flashed back to stock 1.1.0 for a couple people at work who rooted. That should allow the OTA (whatever it will be) to install as BN designs.
And so it goes....
I really hope it's 2.2 and not 2.1 with an app store. I wonder if they're going to release a new kernel (and its source)? That would really help out the CM7 people...
I would think the likelihood of an update this week is very high. Remember they're taking on a major retail partner in Staples starting May 1st. If they have an update, they would want to make sure that it's finished before Staples start selling them, it'd make things a lot easier for their new partner.
buzz killington said:
Remember they're taking on a major retail partner in Staples starting May 1st.
Click to expand...
Click to collapse
Where did you hear/read this?
I think one of the most exciting features of the upcoming update will be an official froyo build that will have full aceess to all of the internal storage. That and an overclocked kernel plus being rooted will be pretty damn awesome in my opinion. I can't wait, time to backup my nook and revert to stock in preparation.
BN
Paul22000 said:
Where did you hear/read this?
Click to expand...
Click to collapse
Straight from a BN press release
http://www.barnesandnobleinc.com/pr...aples_announces_plans_to_sell_nook_color.html
Also the fiscal year for BN ends on 4/30. There may be things you want announced before year end or if it is bad news after year end. The NC product distribution strategy is beginning to resemble the Apple one. However, BN does not have its app developer support strategy in place.
Auto Update came through today (despite devicemanager editing and OTA certs renaming)
I was using my nook today, when all of a sudden a B&N permissions dialog screen popped up (specifically, it said something like "permissions error, rebooting". Then it rebooted into clockwork(???) which formated my data and cache partitions, pulled up a list of errors trying to change other things (possibly because I am rooted with an OC kernel?), and then rebooted.
Despite this, it managed to reboot into stock. I didn't get any further than the setup, before I decided to flash my nandroid backup. I'm actually kind of regretting that a bit now, since it would have been interesting to see what the new stock was like (presuming it worked correctly), but ultimately, I think it is probably best to wait for XDA to tell me what to do about updating or otherwise. In the meantime I'll be leaving my wifi off.
I've been debating upgrading to CM7, but the sleep / battery issue has prevented me. If this update really is froyo, and the devs here get it rooted nicely soon, I may not make that step at all, or at the least I may be able to wait much longer for the sleep issue to be fixed.
Also of interest is the fact that I had renamed the OTA certs and used sqlite editor to tweak the devicemanager.db file. I don't recall if I had spoofed the build.prop or not. But this seems to imply that we don't really have any reliable way of preventing OTA updates at this point, other than installing a completely new rom. That alone might be enough to warrant switching to CM7. I'm so confused!
I'll have to grab my NC and turn it off and take out the sd card.
I don't think I've turned it off for a couple of weeks...running CM7.
Nothing new showing up here yet:
http://www.barnesandnoble.com/u/nookcolor-support-software-update/379002520/?cds2Pid=35758
CM7 won't auto-update, will it? I was running stock 1.0 rooted (and now that I've flashed my nandroid backup, I am again, though I lost two weeks worth of tweaking).

Want to buy a NC but have a question

Sorry if this question is asked. I would like to buy a new NC and run Honeycomb. All NC can do that, right? I mean, it's not like iphone that only certain ios can be jailbroken/unlocked? Thank you!!
As far as I know, yes..
Worst case you can run Honeycomb from the SD card but, if I am not mistaken Clockwork recovery works at least up to 1.1 so it should be able to be installed onto the device as well.
Not 100% sure about 1.2 (that is out right? I quit looking for B&N updates a while back.. )
.... aaaand then I read this.. LOL
****IF YOU RECENTLY GOT A NEW NOOK COLOR OR A REPLACEMENT FROM B+N THEY HAVE CHANGED THE PARTITIONS AVAILABLE ON THE DEVICE AND DUE TO THAT NO CUSTOM ROMS CAN BE FLASHED WITH THE CURRENT RECOVERIES. IF YOU HAVE A BLUE STICKER ON THE BOX YOUR DEVICE IS AFFECTED. STICK TO STOCK/ROOTED STOCK FOR NOW. THE ISSUE IS BEING WORKED ON AND I WILL UPDATE ONCE YOU CAN FLASH AGAIN****
From this thread..
http://forum.xda-developers.com/showthread.php?t=1030227
So perhaps no on the install but, running from an SD card may still be possible..
Thank you!!
There are ways to repartition the storage to what it was before hand, but it's more difficult than the normal simple root, flash, etc. Look around for the threads.
that's what happened to me. returned my refurb NC and got a new one. never read the thread that was posted above. had spent 3 days trying to figure out how to fix it after I brutally screwed it up.
After you repartition it, however, works good as gravy!
andycai said:
Sorry if this question is asked. I would like to buy a new NC and run Honeycomb. All NC can do that, right? I mean, it's not like iphone that only certain ios can be jailbroken/unlocked? Thank you!!
Click to expand...
Click to collapse
Yeah right. You can do it right. Good luck for your new NC.

[Q] Why no Honeycomb OTA on this unit?

WiFi S7 with 2.2.2
Bought in July - works fine but I'd like Honeycomb. Apparently others have gotten it OTA already. I check for updates and get nada...
Why not this one?
What rom do you have installed?
noguru said:
WiFi S7 with 2.2.2
Bought in July - works fine but I'd like Honeycomb. Apparently others have gotten it OTA already. I check for updates and get nada...
Why not this one?
Click to expand...
Click to collapse
Yeah, mine is the same. Several other people noted the same thing, and curiously still it does not have the OTA even though the official one works just fine. Look in Settings, I suspect you have a 338.
Probably the best thing to do is go over to where DJ Steve is now and install his latest ROM.. I am soon, but right now there's some weird problem where the display blinks randomly so I'm waiting for that to get figured out.
Why go through the extra steps of a rom when you can just force the official one on your DS7. It's been posted. Pop this in your browser:
http://mobileupdate.dell.com/?version=GLUNB1A334430
dbpaddler said:
Why go through the extra steps of a rom when you can just force the official one on your DS7. It's been posted. Pop this in your browser:
http://mobileupdate.dell.com/?version=GLUNB1A334430
Click to expand...
Click to collapse
Because Steve's ROM is much better than Dell's, obviously.
Yeah, that's why his thread hasn't been touched since august 29th with zero updates since a bit before then. Once official HC hit everyone NV flashed back to stock and updated to official HC. But I'm sure you're right. A ported Xoom dump of 3.2 modified to work on the DS7 is going to be better than the official version made for it.
Sent from my SPH-D700
dbpaddler said:
Yeah, that's why his thread hasn't been touched since august 29th with zero updates since a bit before then. Once official HC hit everyone NV flashed back to stock and updated to official HC. But I'm sure you're right. A ported Xoom dump of 3.2 modified to work on the DS7 is going to be better than the official version made for it.
Click to expand...
Click to collapse
um.. Yeah. Look again, the mods here closed his thread because he couldn't provide the kernel source he's using. So he's on another forum now, with a large number of people using it. It's based on the official version, better setup, kernel, rooted, etc...
Use whatever you want.
Not that I mind standing corrected, but giving vague advice with no real direction doesn't really help the guy. You could at least point him in the right direction. Tell someone to just do "this" and assume he knows where to go or what to do doesn't really help.
There's a REASON that direct links arnt posted, since xda had issues previously with him and his source code, the right thing to do is not post direct links. (Though the sauce issue has resolved itself)
If you look at the other website they avoid linking back to xda.
Well I could care less about political crap on here and who has issues with what. If they want to flag my post, so be it. If the link is there, he can click on it.
Sent from my SPH-D700
I took the paddler's advice (and thanked).
Honeycomb works as advertised, though to tell the truth I haven't found a reason (yet) to prefer it over Froyo.
Just start roaming through the tablet oriented apps in the market. There are a few that make a difference. The one problem is if you already have vga res on your phone. The Dell just stretches it to a 7" screen, so you won't notice that much of a difference during normal use as you would if you had a 600p screen (like I have on my Evo View now, though it's only running GB).

Categories

Resources