Android 3.0 Honeycomb Preview Image v04 - 2/7/2011

Search This thread

arrjaytea

Senior Member
Dec 7, 2010
242
47
lastminutedisco.net
Running from internal.

Btw, just had my first random reboot now. Dang.. this HC has so many problems. I think the Froyo is quicker and smoother that this HC. Wish there's no wifi issue with Froyo.

Well... I mean... Wasn't it pretty clear that there were going to be problems from the outset?

I've only been running the flashable version for a day or so, but I'm generally well pleased. It has its issues, but most of the applications I run on a daily basis seem to be working great. No random reboots yet, but hell, I get those with my phone to this day, but they've never really become an issue.

All in all, for a preview build, this is solid. Excited to see how it progresses.
 
D

diversificationied

Guest
Just wanted to bump this:

Xoom was released with development code. As soon as they AOSP 3.0, the Xoom will be getting an immediate update to AOSP code, and it will be 3.0.1



How do you know this?

I'm not saying it's not true; I just want to read more on this, preferably straight from the horse's mouth.

http://blogs.adobe.com/flashplayer/2011/03/update-on-flash-player-10-2-for-mobile-devices.html

he March 18th beta release of Flash Player 10.2 in conjunction with Google’s first system update to Android 3.0 (version 3.0.1) currently underway for the MOTOROLA XOOM™ will deliver the first phase of our work together.
 
D

diversificationied

Guest
Techincally it could be today. I'm guessing it'll happen next week.

As far as I can remember they all had a X.X.1 update. Droid, N1, NS, were all updated immediately after release which coincided with their release dates. In this case Moto convinced them to let em ship with early code (huge risk).
 
Last edited:

ADude

Senior Member
Mar 5, 2011
528
59
How do you differentiate what the speeds are in his files?
f08c443ed730b147e57ac224fdd521eb update-HC-dalingrin-OC-emmc-022511.zip
25ba50b8865315b44fc8b98d382b5447 update-HC-dalingrin-OC-sd-022511.zip

The one I ended up using lets me go to 1.1.

I have not used any of this on a Nook, but from what I have read:

You need to buy an App called SetCPU to set the speed and voltage, and you would be advised to read threads here about that before doing anything, as this is probably the one thing that can fry your Nook.

Overclocking is based on the idea that slow chips and fast chips are the same design, faster ones are simply wafers that came out better (oversimplification).
Sometimes, chip makers will have too many of the fast ones sitting in the warehouse (because they are priced higher), so they label them with the slower speed in order to sell them.

You can't tell in advance what is in your device, hence the need to try faster speeds gradually and incrementally.

All this is the theory, there may be variations for the particular CPU used by B&N.
 

msherwood

Senior Member
Apr 6, 2009
57
3
Salt Lake City, UT
the gingerbread source was released at least a week or two before 2.3.1 came out
I don't think the x.x.1 update really has anything to do with the release to aosp

Yeah, but the Gingerbread code was ready for release (unlike, you know, Honeycomb). Maybe this 3.0.1 update will bring Honeycomb up to snuff and solve some of the problems it had at launch. Google doesn't want to release crappy code into the wild, and although I'm pretty impatient I'm with them on this one. I'm just really hoping that 3.0.1 is the magic number. If this doesn't solve some of the early bugs, they might even make another update before AOSP release.
 

jaysckap

Senior Member
Sep 21, 2010
980
133
No frying here ive been running mine for a month oc' ed to 1.1 ghz and it runs great no overheating. Just smooth
I have not used any of this on a Nook, but from what I have read:

You need to buy an App called SetCPU to set the speed and voltage, and you would be advised to read threads here about that before doing anything, as this is probably the one thing that can fry your Nook.

Overclocking is based on the idea that slow chips and fast chips are the same design, faster ones are simply wafers that came out better (oversimplification).
Sometimes, chip makers will have too many of the fast ones sitting in the warehouse (because they are priced higher), so they label them with the slower speed in order to sell them.

You can't tell in advance what is in your device, hence the need to try faster speeds gradually and incrementally.

All this is the theory, there may be variations for the particular CPU used by B&N.



HTC Incredible OMFGB 2.3.2
 

hanbalfrek

Member
Dec 8, 2007
26
0
Image file size?

Hi all,

I have a question I'm hoping you can help me with.

I've burned the 4 gb image of HC and it works great!


However, I only have a 6gb card, and want to get my other 2 GB's back.

How can I make this into a 6gb image?

Or is there another way to get my extra space on a separate partition?

Thanks!
 

ghodzilla5150

Senior Member
Jul 6, 2010
406
39
San Bernardino, CA
I got it on my NC running deeper-blue's HC V4 and it still is not working. In my application it says I have Adobe V10.2 but Youtube and CNN still do not work. I installed Adobe 10.2 thru Astro file manager after I changed the Surprise_Flash from a .zip to a .apk. It installed correctly but it does not work. Wonder what went wrong. I downloaded it from MyDroidWorld.com from my Nook Color's stock browser. It downloaded to sdcard\download
 

luigi90210

Senior Member
Jul 29, 2010
518
91
I got it on my NC running deeper-blue's HC V4 and it still is not working. In my application it says I have Adobe V10.2 but Youtube and CNN still do not work. I installed Adobe 10.2 thru Astro file manager after I changed the Surprise_Flash from a .zip to a .apk. It installed correctly but it does not work. Wonder what went wrong. I downloaded it from MyDroidWorld.com from my Nook Color's stock browser. It downloaded to sdcard\download

i think it might be because we are on an older sdk port

EDIT

i was wondering if we are going to be updated to the final sdk over this one
usually i would say "wait for aosp" but see as aosp might not be released for quite sometime i think it would be better if we were running the latest SDK(from what i read on the nexus forums apps like google body work on the final sdk but it doesnt work on the preview
 
Last edited:

trilogy069

Senior Member
Dec 11, 2008
93
0
i think it might be because we are on an older sdk port

EDIT

i was wondering if we are going to be updated to the final sdk over this one
usually i would say "wait for aosp" but see as aosp might not be released for quite sometime i think it would be better if we were running the latest SDK(from what i read on the nexus forums apps like google body work on the final sdk but it doesnt work on the preview

I could not agree more. While we wait for AOSp, it would be nice to have a build with he final SDK while we wait. Any other thoughts on that? What would be a reason why that would not be done?
 

joe91584

Member
Jan 19, 2011
38
2
Delanco
Thank you all for the wonderful work on this rom.

Tomorrow I am going to be buying 2 more nooks for a friend and a family member. I just cant wait to see what updates we have next like bluetooth on CM7 and smooth video playback on 2.2.1 or even that not so good flash.

But no matter how many down sides and up sides HC has at this time, it;s my daily driver.

Thank you all for the hard work and keep up the great job.
 

fzr-r4

Senior Member
Sep 7, 2010
434
75
Berkeley
I could not agree more. While we wait for AOSp, it would be nice to have a build with he final SDK while we wait. Any other thoughts on that? What would be a reason why that would not be done?

deeper-blue put a lot of time in to this build. I think it's understandable that it's hard to gear up to do it again for the final sdk when aosp is lurking somewhere around the corner, and we all know how eager we'll be for an aosp build.
 

thezero4

Member
Dec 4, 2007
46
2
I know I'm looking forward to a google to remade aosp build. Honeycomb is already so nice, can't wait till I can run tablet apis on it. Especially the gmail, calendar and music app that are on the xoom.

Sent from my SPH-D700 using XDA App
 

Top Liked Posts

  • There are no posts matching your filters.
  • 284
    First of all I have to thank the CM people, especially mbm, nemith, fattire and cvpcs for their work on gingerbread which helped me a lot in understanding where to look and what to patch.

    The whole thing is based on the honeycomb preview emulator images, some of the B&N modules+driver, pieces from the upcoming CM7 and manual patching ARM assembler in libraries, writing ugly scripts to hack around various issues, a lot of time and many brain cells.


    Use this on your own risk. I'm not responsible for any damages. This is not meant as a primetime ready rom. This is a preview after all.


    The unzipped image is around 3.5gb and fits on 4GB SD cards.

    MD5 (nookhoney04.img.zip) = 27396e63396a59a25f5d6fdbe0341276
    http://www.rbrune.de/nookhoney04.img.zip.torrent
    http://www.rbrune.de/nookhoney04.img.zip



    Changelog

    v04 - 02/07/2011
    • increased touchscreen sensitivity and made touchscreen more usable close to the borders (kernel change)
    • fixed heap size issue to get much more programs running (e.g. nook app, kindle app, etc.)


    v03 - 02/05/2011
    • fixed screen turning animations and previews in taskswitcher
    • sd card access and secure storage support
    • turned off the debug screen flashes and vibrator
    • added display timings
    • sd card image now usable on 4gb cards
    • changed to a self compiled kernel to make these things work
    • reduced compressed image size


    v02 - 02/02/2011
    • sound support
    • patched in some graphics improvements. Can play non-hd videos from m.youtube.com
    • sdcard storage


    v01 - 02/01/2011
    • initial release


    Status

    What works:
    • Graphics acceleration
    • Accelerometer
    • Wireless!
    • Touchscreen
    • Buttons
    • Sleep/Wakeup
    • Sound

    Known issues:
    • The accelerometer behaves funky. Will try to fix this.
    • The Gallery app crashes when opening an image. Not my fault, it's broken in the emulator from google too.

    Doesn't work:
    • DSP e.g. no hardware video decoding (and will possibly never work before the AOSP release)


    FAQ

    Q: Why?
    A: I thought it would be fun. It was and still is. And now developers have an actual device to test their apps on instead of relying on the slow emulator.

    Q: How?
    A: I'm planning to write a blog post. Mostly learning how Android works, debugging, patching, reusing binaries from different sources, finding easy ways to reach a goal, try and error, a lot of brain power.

    Q: During boot I get stuck at the Android screen with the blinking cursor.
    A: It seems to be a timing issue with mounting the partitions. Sometimes rebooting helps to get it booting. If not a different SD card might to the trick.

    Q: Why is there no Market app installed?
    A: There's no legal way to distribute the google apps with a ROM.

    Q: Angry Birds, Nook reader, Kindle app?
    A: Yes.

    Q: I want to port Honeycomb to device xyz... send me the instructions how to do that now!
    A: I like the 'I' in that sentence - but there are no instructions, no source, no nothing. Learn and read about Android, Android porting, making custom roms, embedded systems, ARM assembly, driver programming, programming in general, the Linux Kernel and much more - and when you're comfortable and have experience with all of that come back and do your port.

    Q: Can you port Honeycomb to device xyz?
    A: I don't have xyz. And even if device xyz would magically appear at my front door doesn't necessarily mean I'll have the time and motivation to port anything to it.

    Q: I want to use a different kernel what changes did you make in the kernel?
    A: https://github.com/rbrune/nook_kernel

    Q: Where can I donate?
    A: I don't want any money. If you want to put your money to good use donate to a humanitarian organization and/or the EFF.

    --
    Rafael Brune
    12
    A Children's Book

    So Many Zeroes!

    Blue had his V2, all shiny and GNU, and wanted to send it, but stopped to review.
    "What would this ware weigh, if zipped up today? Should it not be much larger than the SDK?"
    And yet it was bigger (nearly one-half a gigger!), but Blue still released it with vim and with vigor.
    "A drive is a drive, at any old size! But a drive is alive when its zero'ed to thrive!"
    So Blue packered his tracks with a /dev/zero-whacker. And then that blue cracker, he launched his bittracker...
    And he ripped, and he zipped (but he didn't encrypt), until it was scripted, and that's when he shipped it!
    It was plain to see-- that his brand-new V3-- was shiny and tiny and better. Whoopie!
    In fact the whole thing was down to 180. A number of megs that was far, far less weighty.
    And now when the Rommers all rom their romses, and now when the Singers all sing their songses,
    their image of Blue will be bigger and taller,
    and installers they image will be *many* megs smaller.
    9
    There are a LOT of devices in CM7's stable. In order for them to launch even an RC, each has to be working or near-working, which takes a lot of effort.

    Also, from what I understand, Gingerbread has a few critical bugs that the CM team is attempting to fix before committing to a formal release. It's a choice not to put it out now, not a lack of skill or talent.

    That's right. There could have been a release in early Jan but while the demo video would have been neato, the build itself would have been WAY too early. And then it would have been a month of "IS IT READY? IS IT READY NOW? Why isn't there sound? Where's the accelerometer? Why is the keyboard so screwy?" etc etc.

    CM has a rule not to release until it's 100% hardware compliant-- that's how CM got a reputation for being so great. That said, the nook CM team has been working with blue in the last few days, so what you're seeing in his release today has several parts from cm7 in it (as he noted in the original post). CM7 also does have sound working, ext4 support, and other hardware and build-process fixes that were impossible to migrate in blue's timeframe (or did not apply w/o the source). Those will be in cm7 (it's two bugs away from full hardware support), and when the source is released for honeycomb, I've no doubt the work will be leveraged into that quickly. Which is good because as you can see, HC and NC fit together very well.

    In other words, this has been time well spent, and you're seeing some of the fruits of that project today.
    8
    Looks like you're gonna make the front page of engadget and the other sites again ;)

    Heres a Mirror to v04:
    http://android.stolenrobot.com/NookColor/Honeycomb/nookhoney04.img.zip

    Here are some basic instructions on how to flash it:

    Windows Instructions
    Download Win32DiskImager.exe
    Download the file in the first post and extract the img from the zip
    Run Win32DiskImager and make sure you pick the drive letter corresponding to your MicroSD card
    Click the Folder icon and locate the img file you extracted earlier
    Click on Write and then wait...

    Once its done remove the SD card from your computer
    Power off your nook color and insert the MicroSD you just prepared
    Power On your Nook Color and wait for it to load

    Welcome to Honeycomb!
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone