1779 replies to this topic

[cVariable]

patruns, on 25 November 2011 - 10:18 PM, said:

This may be of some interest: http://androidos.in/...ned-bootloader/

You really should do your research.
Some dumbass is trolling XDA-devs and all the idiots there are falling for it and celebrating it like the second coming.
He compiled a tool for kexec ... that means absolutely nothing for actually getting kexec to work! Yeah, it's helpful and will ultimately be necessary to hack it but it proves absolutely nothing.
And the one post from a dev who looked through the source code and found indications that the kexec exploit is actually locked in the bootloader ... well, he conveniently gets ignored by all the dumbasses.

Edited by cVariable, 27 November 2011 - 08:58 AM.

[cVariable]

bobstro, on 22 November 2011 - 03:28 PM, said:

Isn't this the same issue as with the Motorola Droid 2 phone? While it's disappointing, there's an active Cyanogenmod port for that device. They're just stuck with kernels released by Motorola. I enjoyed having Cyanogen running on both my Droid 2 and Nook Color. Unfortunately, battery life was an issue on the phone, so I've moved back to stock firmware for that device.

The bigger issue might be that there are two flavors of Nook vying for support. While I hope B&N free the device, given how much effort they've gone to locking up the hardware (based on recent tear down reports), I'm dubious.

NO kernerls = NO ICS.
And without ICS ... you really just have a slightly more expensive Nook Color. What's the point for devs?

[patruns]

cVariable, on 27 November 2011 - 08:59 AM, said:

NO kernerls = NO ICS.
And without ICS ... you really just have a slightly more expensive Nook Color. What's the point for devs?

The Nook Color needs a new kernel as well. That is well known but no one has taken up the task and the main devs are busy with other projects.

I get that you do not believe that this will ever be resolved. I choose to believe that it will. No need to slap down every single post someone puts up about ICS.

[bobstro]

Is it a known fact that ICS requires a new kernel? On the Motorola Droid 2, CM runs Gingerbread on top of a Froyo kernel. Unless there are specific compiled-in drivers that are required, I would think a similar approach could be taken as a last resort.

My kernel experience is primarily based on Linux, but in most cases, running a kernel that's a dot-rev or several behind is no big deal. And though the kernel is signed and must match, can't separately-compiled drivers still be loaded in?

I know the lock down is a problem, but I am wondering if it's truly a roadblock to at least getting ICS running on the NC.

[cVariable]

bobstro, on 27 November 2011 - 08:01 PM, said:

Is it a known fact that ICS requires a new kernel? On the Motorola Droid 2, CM runs Gingerbread on top of a Froyo kernel. Unless there are specific compiled-in drivers that are required, I would think a similar approach could be taken as a last resort.

My kernel experience is primarily based on Linux, but in most cases, running a kernel that's a dot-rev or several behind is no big deal. And though the kernel is signed and must match, can't separately-compiled drivers still be loaded in?

I know the lock down is a problem, but I am wondering if it's truly a roadblock to at least getting ICS running on the NC.

Yes. If you look through xda-dev it is 100% confirmed, since ICS and Honeycomb require a newer API. they just won't boot with an old kernel.
The NC is NOT locked down, ie it will surely get ICS/CM9 at some point.

The NT has a locked bootloader, preventing the loading of custom kernels - no new kernel for ICS/HoneyComb => NO CM9/CM8.

=> if you want to use your ebook reader as a tablet, you are better off getting the NC or the Kindle Fire.

[bobstro]

After posting above, I did find a reference that indicated a newer kernel version is, in fact, required for ICS. I understood that it was related to requirements for hardware acceleration. Having a Nook Tablet that runs slower than the Color wouldn't make a whole lot of sense, so the "run on old kernel" approach probably won't work.

That said, is B&N likely to release an ICS-based firmware update for the Tablet? If so, there's hope. Just not immediately.

I really only care because I'm debating whether to buy my wife a Tablet or Color. I'd like to put ICS on it, but having root is probably sufficient.

[SeaFractor]

Did some experimenting.   When editing the Build.prop and changing to 161 instead of 160, the market still works great (movies and music too)!

Primarily I'd changed back to 161 as the Nook for Android app has overlapping magazines (one icon over the other, so impossible to select other issues) at 160.    161 allows the Nook for Android app to work correctly.

I'd reported that to the BN Nook development team, but their interest in supporting 160 was low.

If the market stays fixed for the long haul at 161, I suggest that the nightly builds have 161 restored as the default.

Bill

[inportb]

SeaFractor, on 29 November 2011 - 07:39 PM, said:

If the market stays fixed for the long haul at 161, I suggest that the nightly builds have 161 restored as the default.

It doesn't...

[hobbeshill]

the market may still come up as the new version but many apps won't show if they don't support 161. many of my regular phone apps didn't show until I switched the nook to 160.

[patruns]

It's not that they don't support 161, it is the market restricting access. Most will run just fine at 161.

[Cousin Goose]

r00tUSR, on 25 November 2011 - 01:34 PM, said:

Thank you for this post!!

the 253m update fixed all of my problems with the nook color, mainly screen of death and a strange problem where I couldn't connect to my school wifi that used PEAP and MSCHAPV2 for authentication. I hope we get ICS for the nook but, if not at least what I have is fully-functional.

Same here. So far no problems at all.

Much appreciated.

[bobstro]

This seems significant: https://plus.google....sts/9xBnN7tQJ2n

Short-term, disappointing (at least for those compulsively doing nightly flashes) but long term, surely it's a good thing?

[patruns]

Since there is nothing more I really want out of CM7 I don't find this very distressing. I'll just stay with nightly 201 until a solid build of CM9 is available.  

[bobstro]

I agree. Even with nightly 253, I think the only issue I was having was the airplane indicator. Wifi was a tad flaky. I've rolled back to n218 for now, though I think n231 was pretty solid. I realized my son's NC has been on n19x for some time and he hasn't had a complaint in (literally) months. I may give Magnetron1's n253m a shot. Otherwise, I think the Cyanogenmod team has left us in pretty good shape with 7.1.

I'm not entirely clear, but reading the announcement, it sounds like there will be a 7.2 stable. I would think that would incorporate everything up through the unreleased 254. Does that sound about right?

And seriously, there's more productive stuff I should be doing than just futzing with flashing an new ROM every day!

[aegrotatio]

I've been using the CM 7.2-RC0 KANG and had to do some sqlite3 hacking to turn off the airplane indicator after my WiFi completely stopped working.

I have an older 7.0 Nook Color and it gets occasional use and is left on the kitchen counter for weeks and the battery never dies.  The 7.1 and 7.2-RC0 die overnight in spite of all my hacks and tweaks to it, and I've tried all of them.  I'm going to revert my other Nook Colors to 7.0 until CM9 comes out.

[patruns]

cVariable, on 29 November 2011 - 02:35 AM, said:

Yes. If you look through xda-dev it is 100% confirmed, since ICS and Honeycomb require a newer API. they just won't boot with an old kernel.
The NC is NOT locked down, ie it will surely get ICS/CM9 at some point.

The NT has a locked bootloader, preventing the loading of custom kernels - no new kernel for ICS/HoneyComb => NO CM9/CM8.

=> if you want to use your ebook reader as a tablet, you are better off getting the NC or the Kindle Fire.

http://forum.xda-dev...d.php?t=1446987

[Pandemic]

Hey all,

Nightly builds are running again for other devices.  When can we expect to see something for the NC again?  Looks like the push for 7.2 is on.

[jicama]

Pandemic, on 12 February 2012 - 07:15 PM, said:

Nightly builds are running again for other devices.  When can we expect to see something for the NC again?  Looks like the push for 7.2 is on.

There are unofficial 7.2-RC0 KANG builds available for the NC over at XDA:

http://forum.xda-dev...d.php?t=1344873

[Kroric]

Anyone had an issue with the newest version of nightly freezing and locking up? I thought it might just be the memory filling up and causing the issue. Maybe a simple fix. But I just wanted to check here first. Any details would be appreciated. Thanks!

[Spyd'R]

It happenned to me too with the 6/3 nightly. I actually just downloaded the premium rom manager and imstalled it thatbway and it worked fine. Not much of a difference from the last build tho.