Related
Here is a thread that will be all about speculation..
I saw the honeycomb and it was smoking!!! What are the chances that the guys here will get it on the nook? And if yes, how it will run? Given that it only have a 800Mhz processor (1Ghz overclocked).
Looking forward for any opinions
I hope so, but that's a good bit away. Honeycomb uses on screen buttons, so our hardware button deficiencies would go away, if it were possible.
IIRC, Honey requires a 1Ghz processor. If we can get the overclocked kernels working with the five 9's of accuracy, then its possible. I really would like for there to be a way to strip out the nooks reader and shop apps for B&N so that I can keep the books and magazines that I've purchased. Thats pretty much a prerequisite for me.
10equals2 said:
IIRC, Honey requires a 1Ghz processor. If we can get the overclocked kernels working with the five 9's of accuracy, then its possible. I really would like for there to be a way to strip out the nooks reader and shop apps for B&N so that I can keep the books and magazines that I've purchased. Thats pretty much a prerequisite for me.
Click to expand...
Click to collapse
There are no mandatory hardware requirements for honeycomb, but it will certainly run a lot smoother at 1ghz+
Sent from my Nooted friend...
paleh0rse said:
There are no mandatory hardware requirements for honeycomb, but it will certainly run a lot smoother at 1ghz+
Sent from my Nooted friend...
Click to expand...
Click to collapse
That's true and the more and more limitations are taken away as launch approaches..
I have no doubt it will run well, but also wonder if anyone will create a Nook version..
spikey911 said:
That's true and the more and more limitations are taken away as launch approaches..
I have no doubt it will run well, but also wonder if anyone will create a Nook version..
Click to expand...
Click to collapse
why not......
elcape said:
why not......
Click to expand...
Click to collapse
Well, this is just my opinion of course...
It will still be some time before we even see a 2.3
3.0 will not be out for a while and by the time that happens newer, faster, better, tablets will hit the market and catch everyone eye..
People may flock towards the newer tablets and leave the older ones behind..
I don't want to say it will never happen, but it is possible we won't see a 3.0 if the developers flock to newer tabs..
One thing is for sure, you will not see an official version from B&N.. I have my doubts there will even be an official 2.2 from them.
Is it bringing something amazing to the table? Haven't even bothered looking at honey just because the GUI stuff everyone likes looks ugly as hell.
Nook color was my first android device so I prefer the simple notification bar at the bottom, as well as using a taskmanager to kill/switch apps.
sent from a Nook Color using xda-app
spikey911 said:
Well, this is just my opinion of course...
It will still be some time before we even see a 2.3
3.0 will not be out for a while and by the time that happens newer, faster, better, tablets will hit the market and catch everyone eye..
People may flock towards the newer tablets and leave the older ones behind..
I don't want to say it will never happen, but it is possible we won't see a 3.0 if the developers flock to newer tabs..
One thing is for sure, you will not see an official version from B&N.. I have my doubts there will even be an official 2.2 from them.
Click to expand...
Click to collapse
I hope you realize that the fine folks at Cyanogen are already working on a NC version of CyanogenMOD version 7 -- which is a Gingerbread (2.3) rom. Some of their best devs are on it, and they've even gotten it to boot already!
So, don't be surprised when you see 2.3 sooner, rather than later...
Sent from my Nooted friend.
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.
Came across a funny older article on a fruit based website about the nook color when it first came out. After reading it i couldnt help but chuckle.
This was the best part of it,
But unlike forthcoming Android tablets like the Samsung Galaxy Tab, this device is going to be locked down and will only be able to run a limited number of B&N-approved apps such as Pandora and Lonely Planet.
Click to expand...
Click to collapse
lol
Its a good read for a laugh.
I know that my nook color countinues to amaze me with more and more functionality everyday.
Its amazing what xda devs can accomplish. Take something and make it do something it was never meant to do and do it better than its competition.
That article is an unfortunate example of what a lot of tech journalists are doing these days. Hastily research a new product, then clip together a bunch of other coverage and bang out an article. By demonstrating his technical incompetence, sure he's got egg on his face now after the fact, however he also represents a large (the majority) percentage of B&N's customer base. The average purchaser would says "rooting what now?".
Amazingly, the NC has proven wildly popular and B&N's top selling item EVER, so obviously even with the limitations the author describes it's trouncing the competition. For those of use who know about ADB and scripts/img files, hey it's even better. Bought one for myself, then for my Dad (50's, tech savvy still). I rooted it, installed xeam and some apps then wrapped it back up and bang, best Christmas present ever!)
I've had a book 3g and then the NC which i rooted. Bottom line it rocks!!!!
Sent from my NOOTED NC using XDA App
I cannot wait for a fully functional froyo rom for the internal memory that will make this a true tablet
Sent from my DROIDX using Tapatalk
sp1kez said:
I cannot wait for a fully functional froyo rom for the internal memory that will make this a true tablet
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Forgot Froyo. Gingerbread CM7. It's going to be B-E-A-UTIFUL
nicbennett said:
Forgot Froyo. Gingerbread CM7. It's going to be B-E-A-UTIFUL
Click to expand...
Click to collapse
Name 5 things that Gingerbread does better than Froyo....
Anywho, I too look forward to a tablet-friendly custom ROM.. I still really like the status bar on the bottom of the screen, but the stupid B&N shortcut thing gets on my nerves when I'm typing.
khaytsus said:
Name 5 things that Gingerbread does better than Froyo....
Anywho, I too look forward to a tablet-friendly custom ROM.. I still really like the status bar on the bottom of the screen, but the stupid B&N shortcut thing gets on my nerves when I'm typing.
Click to expand...
Click to collapse
You mean aside from the better Dalvik VM, better battery management, improved UI, improved hardware capabilities (improved camera handling, gyroscope, NFC), improved game API, improved audio API, new media (audio/video) support, and a new linux base kernel? I guess if you don't count those, you still have the new/updated core libraries, updated bluetooth stack, improved text selection, built-in VOIP, and of course, the better keyboard...
Seriously, i mean, really seriously, why would ANYONE have anything against getting the NEWEST OS? All our efforts should be on gingerbread, since it offers the most compared to Froyo. Its not like moving to GB has any shortcomings, so why NOT want it?
I just got my nook color last night - I've found BBuy that had it in stock about 50 miles and drove there - sure enough about 20 were on the shelve - forgot to mention I traveled actually from one state to another (about 50 miles) to get it right of the shelve ... so anyhow, I am happy with "locked" nook color has to offer - I am even more thrilled about rooting it soon and unlocking the full potential. NC here I come
Yeah, a lot of the reviews bemoaned its alleged "doesn't know what it is" status. I've rooted mine, OC'd it, isntalled dozens of apps and games. Yet I still use it primarily to read novels, and do some light web browsing. And for that, it's dead perfect.
In other words, even an unrooted NC is an outstanding gizmo. I mean that screen is just to die for.
I definitely love my Nook. People are always surprised when I tell them it was only $250. Froyo on teh emmc via dd ftw! It's much better than the stock OS.
rjsmith2007 said:
I definitely love my Nook. People are always surprised when I tell them it was only $250. Froyo on teh emmc via dd ftw! It's much better than the stock OS.
Click to expand...
Click to collapse
IN regards to emmc Froyo - what about the lag? I guess it may just be my SD card, but every Froyo build i have tried, has been painfully laggy - not slow, but things like gmail can take 1-2 minutes to actually show the mail. The app drawer animations are also oddly slow. Does emmc really make Froyo more usable for you?
Divine_Madcat said:
IN regards to emmc Froyo - what about the lag? I guess it may just be my SD card, but every Froyo build i have tried, has been painfully laggy - not slow, but things like gmail can take 1-2 minutes to actually show the mail. The app drawer animations are also oddly slow. Does emmc really make Froyo more usable for you?
Click to expand...
Click to collapse
Oh GOD yes. There is no lag on eMMC. Typing this comment to you on my Froyo'd NC right now
Divine_Madcat said:
You mean aside from the better Dalvik VM, better battery management, improved UI, improved hardware capabilities (improved camera handling, gyroscope, NFC), improved game API, improved audio API, new media (audio/video) support, and a new linux base kernel? I guess if you don't count those, you still have the new/updated core libraries, updated bluetooth stack, improved text selection, built-in VOIP, and of course, the better keyboard...
Seriously, i mean, really seriously, why would ANYONE have anything against getting the NEWEST OS? All our efforts should be on gingerbread, since it offers the most compared to Froyo. Its not like moving to GB has any shortcomings, so why NOT want it?
Click to expand...
Click to collapse
No, I agree that Gingerbread has small incremental improvements, but nothing that'd cause me to say screw Froyo, wait for Gingerbread. Especially if Gingerbread on the NC is well off.
khaytsus said:
No, I agree that Gingerbread has small incremental improvements, but nothing that'd cause me to say screw Froyo, wait for Gingerbread. Especially if Gingerbread on the NC is well off.
Click to expand...
Click to collapse
I guess what i am thinking - given that Gingerbread is already being worked on, and our Froyo build doesn't actually work that well, why not just move ALL the resources out there to GB, and the most recent right away. Why go incrementally?
Divine_Madcat said:
I guess what i am thinking - given that Gingerbread is already being worked on, and our Froyo build doesn't actually work that well, why not just move ALL the resources out there to GB, and the most recent right away. Why go incrementally?
Click to expand...
Click to collapse
I'd agree with that.. If the effort is the same for both, go with Gingerbread. However so far we have Nookie Froyo which is "mostly" there and I haven't heard of Gingerbread on the NC at all.
Just to add how amazing this gadget is I'm typing this comment using SlideIT and it has taken mea fraction of what it used to.
Sent from my rooted Nook Color
khaytsus said:
I'd agree with that.. If the effort is the same for both, go with Gingerbread. However so far we have Nookie Froyo which is "mostly" there and I haven't heard of Gingerbread on the NC at all.
Click to expand...
Click to collapse
WEll, there is a gingerbread branch that is being worked on here: https://github.com/fat-tire/android_device_bn_encore
And there is plenty of talk that CM7 is on its way (though, i admit that i still fall into the see it to believe it camp). http://forum.cyanogenmod.com/topic/11127-nook-color/page__st__40
But regardless, the froyo build really isn't that usable - its laggy, market is like sludge, etc. I really think that the devs working on it, should take the froyo lessons, and focus totally on GB. Let froyo be the sandbox for others to learn on, and let GB be the first real OS upgrade for the NC.
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
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).