Database Users

Honeycomb?

http://android-developers.blogspot.com/2011/01/android-30-platform-preview-and-updated.html

v0kal said:
http://android-developers.blogspot.com/2011/01/android-30-platform-preview-and-updated.html
Click to expand...
Click to collapse
As of now this is all I would be interested in from 3.0 . Hope cyanogen can pull this into CM7
New types of connectivity: New APIs for Bluetooth A2DP and HSP let applications offer audio streaming and headset control. Support for Bluetooth insecure socket connection lets applications connect to simple devices that may not have a user interface.

Yep seems to be a preview SDK for 3.0 with a final SDK in coming weeks. Simply prep for Honeycomb tablets.

"A built-in GL renderer lets developers request hardware-acceleration of common 2D rendering operations in their apps, across the entire app or only in specific activities or views."
So it seems that 2.3 isn't hardware accelerated...now I want 3.0 on my desire . But here's another quote:
"Android 3.0 (Honeycomb) is a new version of the Android platform that is designed from the ground up for devices with larger screen sizes, particularly tablets."
So Honycomb isn't for phones? I really hope Google can clear things up a bit because I remember Andy rubben saying the Honycomb can adapt to phones & tablets.
Any thoughts or theories?

Weren't there enough thoughts and theories about it?

Jack_R1 said:
Weren't there enough thoughts and theories about it?
Click to expand...
Click to collapse
Yes there was a lot of theories, but now we have something official to discuss rather than hearsay. Anyway, don't discuss if you don't feel like it.

How about the 2.4? really don't know what Goolge is thinking about. Just want a stable version and improve it by other works. Not so much version and make people confuse. It seems that N1 may not flash it~~

mr.r9 said:
Yes there was a lot of theories, but now we have something official to discuss rather than hearsay. Anyway, don't discuss if you don't feel like it.
Click to expand...
Click to collapse
Looking at the new preview SDK, it only big screens by default. And reading through the platform highlights really only mentions tablets. However, a couple Android devs have already stated its for all platforms. Seems to me that they don't want to reveal that its for phones yet, so that they can advertise that it is made for tablets.
The main criticism the iPad got was being a giant iPhone. I think they want to avoid that by having people believe that it isn't the same Android that is on phones.
I guess when they release the full SDK we'll know for sure.

Interesting...the beat goes on!

Honeycomb is also for phones, but we all knew that right?
From the documentation:
Publishing your app for tablet-type devices only
Additionally, you should decide whether your application is for only tablet devices (specifically, xlarge devices) or for devices of all sizes that may run Android 3.0.
If your application is only for tablets (xlarge screens; not for mobile devices/phones), then you should include the <supports-screens> element in your manifest with all sizes except for xlarge declared false.
With this declaration, you indicate that your application does not support any screen size except extra large. External services such as Android Market may use this to filter your application from devices that do not have an extra large screen.
Otherwise, if you want your application to be available to both small devices (phones) and large devices (tablets), do not include the <supports-screens> element.
Click to expand...
Click to collapse
Well, all clear then! The future of Android looks neat!

Nice find
Sent from my Nexus One using XDA App

spamlucal said:
Honeycomb is also for phones, but we all knew that right?
From the documentation:
Well, all clear then! The future of Android looks neat!
Click to expand...
Click to collapse
Hmmmm...good find! Android is getting really interesting visually, which is IMO a milestone it needed to reach a while ago
Anyway, can't wait for an alpha sdk image on my phone to play with if that's possible currently

Forget Ginga and Honeycomb. Havent you all hear of whats ahead of honeycomb? Its called " Chicken Soup". Yup, ik... Weird name. But its only for dual core over 2ghz. So phones arent ready. Its suppose to be completely holographic 3d without glasses. Pretty neat. And requires horsepower of xbox 360 or more. Anything less and its a no go. Its suppose to be the next gen OS and quantum leap from even honeycomb. Remember the name "chicken soup". Its comming next year by christman. Cant wait!
Sent from my SPH-D700 using Tapatalk

SINNN said:
Forget Ginga and Honeycomb. Havent you all hear of whats ahead of honeycomb? Its called " Chicken Soup". Yup, ik... Weird name. But its only for dual core over 2ghz. So phones arent ready. Its suppose to be completely holographic 3d without glasses. Pretty neat. And requires horsepower of xbox 360 or more. Anything less and its a no go. Its suppose to be the next gen OS and quantum leap from even honeycomb. Remember the name "chicken soup". Its comming next year by christman. Cant wait!
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
This was a horrible and incredibly illogical troll/joke attempt

spamlucal said:
Honeycomb is also for phones, but we all knew that right?
From the documentation:
Well, all clear then! The future of Android looks neat!
Click to expand...
Click to collapse
It actually does not mean much.
Android application could always define different layouts for different resolutions, orientations, themes or screen sizes. So, it is just one additional form factor, one of many. And the way to say to the market which layouts are supported and which are not.
It also does not mean, that "honeycomb for phones" would be the same as honeycomb for tablets "just smaller".
They only said, that phone version will move in similar direction. Which can mean pretty much anything.
In fact I expect, that honeycomb for phones will be seriously different, since a lot of new honeycomb for tablets features on smaller screens do not make any sense.

My theory:
Honeycomb is currently, Tablets only.
We are going to see a division in Android for Phones and Android for Tablets.
Tablets will be at 3.0 starting off.
Phones are currently at 2.3, and will continue 2.4 being Gingerbread as well with updates that should have happened with 2.3. (Like 2.0 and 2.1 being Eclair)
Once phones have the ability to run such a resource hungry operating system(3.0) the Phone and Tablet versions of Android will merge into one.

Wisefire said:
My theory:
Honeycomb is currently, Tablets only.
We are going to see a division in Android for Phones and Android for Tablets.
Tablets will be at 3.0 starting off.
Phones are currently at 2.3, and will continue 2.4 being Gingerbread as well with updates that should have happened with 2.3. (Like 2.0 and 2.1 being Eclair)
Once phones have the ability to run such a resource hungry operating system(3.0) the Phone and Tablet versions of Android will merge into one.
Click to expand...
Click to collapse
But the hardware of the new tablets is the same Tegra 2 of the new phones, so I think the problem is the adaptability of the OS to smaller screens in a way it is usable for our fingers.
Anyone here used the leaked "honeycomb music player"? It has all the new characteristics we saw on the xoom tablet but worked very nice on my Nexus One with 2.2.1.
I think when honeycomb's source code come out we will get working builds.
Sent from my Nexus One using XDA App

I heard Ice cream is going to be only for refrigerators. You know cause of the thermostat API that very few phones support.

marlonbr said:
But the hardware of the new tablets is the same Tegra 2 of the new phones, so I think the problem is the adaptability of the OS to smaller screens in a way it is usable for our fingers.
Anyone here used the leaked "honeycomb music player"? It has all the new characteristics we saw on the xoom tablet but worked very nice on my Nexus One with 2.2.1.
I think when honeycomb's source code come out we will get working builds.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I believe you are absolutely right. I tried making an AVD for Honeycomb with the screen resolution of my Nexus One. The launcher force closed continuously but you could see that the standard pull down notification bar was there. So I take that to mean that Honeycomb is for all devices and just changes its layout based on screen size.

draugaz said:
It actually does not mean much.
Click to expand...
Click to collapse
A little bit of context: The text I copy-pasted is in a section called "Upgrade or Develop a New App for Tablets and Similar Devices"
In it, is says:
If you want to develop something truly for tablet-type devices running Android 3.0, then you need to use new APIs available in Android 3.0. This section introduces some of the new features that you should use.
The first thing to do when you create a project with the Android 3.0 preview is set the <uses-sdk> element to use "Honeycomb" for the android:minSdkVersion.
Click to expand...
Click to collapse
What does this mean? it means this app won't work on anything other lower than honeycomb. So, the "choose your screen size" text I pasted yesterday applies to honeycomb-only apps.
The documentation in the SDK is a nice read actually

Dexter (Possible kernel/driver source) A7

Was searching around about our elocity interesting how this offers a built in 3g or bluetooths and sim card option this product seems quite a bit like our elocity same components too.
Dexter and any other developer see what you kind find out about this, looks like different interface could be the break in the kernel we wanted.
pioneercomputers.com.au/products/configure.asp?c1=183&c2=185&id=3203
Drivers and more under support tab
Hope this is what we needed to really get this ball rolling on other O.S.

Anyone feel free to find out what you can about thisw site and the drivers listed and lets work on pulling what we need from it and establishing a center for all the drivers.

rombold said:
pioneercomputers.com.au/products/configure.asp?c1=183&c2=185&id=3203
Click to expand...
Click to collapse
Nice findings.. i tried search naz10 and epad n700, aigo N700 etc.. but no luck, but i guess you hit jackpot here
thanks..

ok, the site does not have any files for this tablet..

Dex I know it list everything for every product they have or so it would seem under driver tab. I wonder if we can email thier support and them compile the files or point them out for us.

Anyone have an in at Compal?
It would be awesome to get our hands on the boards they were making before they removed the GSM provisions.
As for that site, it just looks like a reseller to me.

codon.org.uk/~mjg59/android_tablets/
List android devices who are compliant with open kernel and access to them
Now there is alot I don't understand with these devices and how to build a rom, but with this from nvidea can't we use a existing kernel and patch into it.
NVIDIA Tegra 250 Developer Kit Hardware

rombold said:
Now there is alot I don't understand with these devices and how to build a rom, but with this from nvidea can't we use a existing kernel and patch into it.
NVIDIA Tegra 250 Developer Kit Hardware
Click to expand...
Click to collapse
but you understand your PC?
so if you board has a core2duo with 2GB memory, and you add a Geforce, and as modems are rare, you find a nice windows7 compatible modem card + a wifi from broadcom with integrated bluetooth.
Next guy does almost the same but he uses a different wifi and bluetooth card for his pc..
so we got 2 pc's equipped almost the same but with different wifi/bt and of course on chose panasonic touch display , where the other one got LG touchscreen which again uses different drivers.
its all about drivers, not just the chipset

I will continue the search for every driver for this device. If you could list any known manaufacters and the part they made. I will search for every driver I can, and will keep you up to date with my progress. Keep me informed on your break throughs with honeycomb or if there is something you need to find and I will help.

u-boot, drivers and kernel source
Does anyone have the nvidia Tegra 250 devkit? Supposedly they were going to include u-boot support and source. See tegradeveloper.nvidia.com/tegra/forum/uboot-tegra-250
Does the dev kit even have open source for drivers and kernel patches. Is full support for the tegra 250 already at kernel.org or is it missing some key features?
I've held up on ordering the dev kit since my experience with nvidia is that they tend to keep as much information private as possible even with an NDA in place.
I'd gladly help develop a completely open bootloader with u-boot, Linux kernel and distro for this device if hardware specifications are actually available. Google was talking about a possible tegra based device that surely would include open source, but I don't think that project ever made it to market.

2ShedsJackson said:
Does anyone have the nvidia Tegra 250 devkit? Supposedly they were going to include u-boot support and source. See tegradeveloper.nvidia.com/tegra/forum/uboot-tegra-250
Click to expand...
Click to collapse
you sign a NDA with Nvidia, so no chance of anyone releasing it to community. if they do if will be figured out, and a lawsuit coming their way..
so thats a no go.
Registered developers with Nvidia, know this, so they wouldn't dare risking a lawsuit..

So in their typical control freak fashion they don't want specs or source getting out into the open. Looks like I'll be skipping the A7 until it gets at least a touchscreen update.

2ShedsJackson said:
So in their typical control freak fashion they don't want specs or source getting out into the open. Looks like I'll be skipping the A7 until it gets at least a touchscreen update.
Click to expand...
Click to collapse
not entirely true, its only the parts you asked about..
kernel is GPL and parts of related drivers follows.. but bootloaders are a protected part, and some the vendor specific parts used to manage the chipset together with their nv drivers.. but thats how i read it..
more might be available, but i have not seen all of it.
toshiba + xoom is the only kernels with drivers i seen so far..

[Q] Honeycomb from Gen9 to Gen8 Port

Hey,
The Archos Gen9 Tablets (from 5" to 10") will be released in July with Honeycomb
The Devices proposed will have the same architecture as our Gen8 Tabs.
Now my question is:
Will we be able to port the Honeycomb Rom ( designed for Gen9 Archos ) to our Gen 8 ?
I would love my tab even more if Honeycomb be on it

They may have the same architecture like Gen8 (and like all other tablets) but not the same chipset and may need other drivers.
regarding the honeycomb source code rumors: http://android-developers.blogspot.com/2011/04/i-think-im-having-gene-amdahl-moment.html

@Lennb:
You really should learn to read the whole thing.
http://forum.archosfans.com/viewtopic.php?f=84&t=50692
Here and everywhere else is stated that archos will ANOUNCE the tablets in June and that they MIGHT BE available in september.

The archos gen9 tablets will have 1.6 GHz dual-core A9 processors
http://www.engadget.com/2011/03/20/sneak-peek-at-archos-gen-9-tablets-1-6-ghz-dual-core-a9-process/

If the gen9 tablets have an USB connected display as gen8 it should easy to port.

luisivan said:
If the gen9 tablets have an USB connected display as gen8 it should easy to port.
Click to expand...
Click to collapse
Hey luisivan,
These are great news
Do you still work on honeycomb?

Well wait a second....
Wouldn't it be possible to get Honeycomb to work on our Gen 8 tablets by way of decompiling the source code from Honeycomb 3.0 on the Xoom and adding the same exact drivers or tweaked drivers from our own 70/101 tablets that we have now? Someone could possibly take the build.prop and/or other needed parts from Honeycomb and somehow make it all work for us sooner so we don't have to wait for Google to release it?? Also, maybe even go as far as verifying that some/most of the code is correct by matching it up like a mirrored image to see what is and isn't supplied from the partial code that Asus released. Then copy the code Asus released and take the remaining supplied code from the Xoom and copy that as well to a custom Archos community-built Honeycomb firmware that we could use? After then someone could make an overclock to 1400-1550+ MHz or any speed that is stable for that matter?
But really, would something like this even be possible for us regardless if these new Archos Gen 9 tablets have the USB connected display or not?? And yes, I do agree that it would be easier with either a micro or full-size USB connected display. Am I thinking too big here people?

spicy_puerto_rican said:
Am I thinking too big here people?
Click to expand...
Click to collapse
A little bit, yes
Here is my opinion:
We have to spend money into Developement for Gen8, or nobody cares about our devices
i know, its hard to believe but it is so..
Yes, we've some good developers, but the best of them (sauron) isn't an android developer, he works as an linux developer (i know android is an distribution, but its not the same, exspecially in developement)
My Proposal:
Everybody spends 1-2 Dollars (accepted ca. 50-100 people would do this: 50 to 200 dollars) to the deceloper (team), that gets honeycomb on our gen8(i think best would be if they work with sauron and other urukdroid developers together, because of their archos knowledge)
With that we can ask here at xda in "normal" developement section for a developer (team) to do it
From my point of view that's the only way to get honeycomb on our devices
What do you guys think about this?
EDIT:I've seen the Xoom yesterday in town (lippstadt) at the t-mobile store, its freaking assome (i mean honeycomb)

Is be happy to contribute a couple of dollars!
Sent from my HTC Wildfire using XDA App

50-200 $ for a full project team? Are you kidding me?
While I'm working, I cost CHF 200 (~$225) per hour!
I know you mean it in good manner, but please stay realistic. this money will be just a donation, not a real support. you can buy them beer but you can't buy THEM.

chulri said:
50-200 $ for a full project team? Are you kidding me?
While I'm working, I cost CHF 200 (~$225) per hour!
I know you mean it in good manner, but please stay realistic. this money will be just a donation, not a real support. you can buy them beer but you can't buy THEM.
Click to expand...
Click to collapse
I know,i know oh chulri du verdienst viel^^
But if there's reward more developers think about this, i think
I've created this thread at "normal" Android Developement Section:
[Developers Wanted] -Honeycomb on Archos Gen8 (Reward in $)
Maybe this will help, we'll see

Lennb said:
I know,i know oh chulri du verdienst viel^^
Click to expand...
Click to collapse
No I don't earn but I cost that much, this is a big difference
Lennb said:
But if there's reward more developers think about this, i think
Click to expand...
Click to collapse
I love neverending optimists

chulri said:
No I don't earn but I cost that much, this is a big difference
Click to expand...
Click to collapse
Oh sorry i read it wrong
I love neverending optimists
Click to expand...
Click to collapse
Oh i toohehe^^

Great News!
I've found an Developer, who's interested in Developing for Archos Gen8
See here:
http://forum.xda-developers.com/showthread.php?p=13877108

Well I'd be very willing to work on porting Honeycomb to our Gen 8 devices even without donations or compensation but I'm completely clueless on knowing linux/android, programming, writing code, etcetera because I'm a total noob so I'm out unfortunately. I guess I need to hit the books... but by that time Honeycomb will probably already be ported and/or the full code released by Google too.

spicy_puerto_rican said:
Well I'd be very willing to work on porting Honeycomb to our Gen 8 devices even without donations or compensation but I'm completely clueless on knowing linux/android, programming, writing code, etcetera because I'm a total noob so I'm out unfortunately. I guess I need to hit the books... but by that time Honeycomb will probably already be ported and/or the full code released by Google too.
Click to expand...
Click to collapse
1:
No problem, you can help the Urukdroid Developement as little helper or tester
2:
Yes, but no one really know if and when they'll release the sc

Lennb said:
Yes, but no one really know if and when they'll release the sc
Click to expand...
Click to collapse
I know: For Honeycomb? Never!
But for it's successor: http://gizmodo.com/5800358/what-is-androids-ice-cream-sandwich

chulri said:
I know: For Honeycomb? Never!
But for it's successor: http://gizmodo.com/5800358/what-is-androids-ice-cream-sandwich
Click to expand...
Click to collapse
Yep, unfortunality
But can you understand the guide how to compile android drivers for our touchscreen?

don't even hope 3.0 on the gen9 in the first time
2.3 yes

cajl said:
don't even hope 3.0 on the gen9 in the first time
2.3 yes
Click to expand...
Click to collapse
Okey,okey
But anyone could tell what i found? Is it the solution for our problem about porting the touchscreens drivers?
Here the link once again:
http://lii-enac.fr/en/architecture/linux-input/multitouch-android-howto.html

cyanogenmod 7 FINAL BUILD gingerbread tegra harmony release

Wrong: CYANOGENMOD 7 RELEASED, HARMONY SUPPORT, DIDN'T NOTICE ANY POSTS REFERING TO IT
Right: CM7 was released, with Harmony support.
Wrong: SHAME THAT NVIDIA ARE NOT SUPPORTING DEVELOPMENT FOR HARMONY CHIP FROM 2.2 ONWARDS IF REPORTS ARE TRUE
Right: It's a shame that nVidia isn't supporting Harmony developers from 2.2 onwards, if reports are true.
Mod Edit: All caps is annoying. Please don't use it. Thanks.

Yes if you actually look at the other CM7 threads you will see that the Vega changes have been added to the official tree now.....
and how can you go and say that we have cm7 (2.3) and then complain about the lack of nvidia support beyond 2.2 in the same post, completely contradicts itself....

but doesnt the tegra 2 already power a bunch of honeycomb tablets already?

mintvilla said:
but doesnt the tegra 2 already power a bunch of honeycomb tablets already?
Click to expand...
Click to collapse
there are two types of tegra 2 boards, Harmony which the vega has supported to android 2.2 and Ventana which the xoom has, supported beyond 2.2

Useless posts removed, OP reformatted. All caps is just annoying.
Also, thank you Lennyuk for your expertise. I actually wasn't aware of the two Tegra 2 revisions. What are the differences between Harmony and Ventana?

willverduzco said:
Useless posts removed, OP reformatted. All caps is just annoying.
Also, thank you Lennyuk for your expertise. I actually wasn't aware of the two Tegra 2 revisions. What are the differences between Harmony and Ventana?
Click to expand...
Click to collapse
as far as I know there is not actually a great deal of differences between the two, I think the ventana board has an extra GPU slot, that might be it.

Lennyuk said:
as far as I know there is not actually a great deal of differences between the two, I think the ventana board has an extra GPU slot, that might be it.
Click to expand...
Click to collapse
Interesting. I wonder why that would be since these SOCs don't have modular components, with the GPU being directly integrated into the SOC itself... Weird.

UPDATE 12 APRIL 2011:
Sorry folks looks like I caused a bit of confusion. Since this is a developer forum my comments
were targeted at Tegra Honeycomb developers and for this we’d like to focus on Ventana. For shipping or production products, customers should contact the device makers directly for OS support plans. They are responsible for the OS shipping on their device.
In relation to our linux kernel git repository, NVIDIA will continue to provide full open-source support for all of our kernel components and will push more of that upstream over time.
Andrew Edelsten
Tegra Developer Relations
NVIDIA CorporationTop
Sent from my HTC Desire using XDA App

Interesting update something for developers to get teeth into sometime
Sent from my HTC Desire using XDA App

Mod Edit: All caps is annoying. Please don't use it. Thanks.[/QUOTE]
haha to right

UPDATE 13 APRIL 2011
A lot has been read into a very short post about a Tegra development kit. I'd like to clear up a few points.
First, nothing changes in what we’re delivering to the open source community or customers. NVIDIA will continue to post the Tegra kernel to kernel.org and publish our Android code to our public git servers. Additionally, we will continue to make our BSP (codecs, GPU driver etc) available to all our hardware partners. We will continue to do this and nothing about these processes has changed.
For our partners' Android devices, NVIDIA provides support until the hardware partner chooses to no longer support the device. So, for instance, NVIDIA will support the Xoom on all versions of Android Motorola requests until Motorola ceases to support the Xoom. The same goes for ViewSonic with the G-Tablet, Notion Ink with the Adam, Acer with the Iconia, LG with the Optimus 2X and so on.
In relation to my original reply, that was a response to a specific question about a Tegra 250 Development Kit. Given the confusion, we will work with owners of Tegra 250 Development Kits individually to determine their needs. The term "Harmony" is an internal codename for the Tegra 250 Development Kit. It is not a tablet reference design. Each shipping tablet is a custom design with varying hardware components and requires a custom OS image from the OEM who made the tablet.
Finally, while we cannot support or give out third party peripheral drivers or provide the Android 3.0 source before Google does, we do want to explore whether we can assist the open source ROM makers. We will be reaching out to them today.
*
Sent from my HTC Desire using XDA App

Caps from original nvidia forum post.
Stop being so anal anyway
Sent from my HTC Desire using XDA App

Can anyone translate this for me? Are we (Advent Vega users) getting the Tegra 2 update? And is this the one for Honeycomb?
From what I can tell, Yes. Or am I reading this wrong?

GaiusSensei said:
Can anyone translate this for me? Are we (Advent Vega users) getting the Tegra 2 update? And is this the one for Honeycomb?
From what I can tell, Yes. Or am I reading this wrong?
Click to expand...
Click to collapse
There is no "Tegra 2" Update
You are getting confused.
Basically when the Tegra2 boards were given to manufacturers they had one of two designs
Harmony which the vega has
or Ventana which newer tablets have
These are not set in stone, they were just designs that then get built to specific needs by each manufacturer.
Nvidia are not releasing their own stock images beyond android 2.2 for Harmony however they have made it very clear that it is down to each manufacturer to do this, Nvidia will support the manufacturers for as long as they want to continue service on each device.
Advent do not yet know if the manufacturer (Shuttle) will give us a HC rom, however at least 2 other clones of the Vega have confirmed it, so it looks promising.

Point of View is supposed to deliver us a fresh HC ROM, I would be really thankful!
All I need is a rom w/o cellphone stuff, just tablet things to work always with optimizations and no slow downs.. That's why I bought a tablet with tegra... but after news like this, customers like me get pretty sad and will regret buying another device from them. Gz;

[IDEA] Petition Xoom

Hello i want to talk about a (in my mind the last) Idea to getting more help for the Xoom Family from Moto / Google.
The Xoom Tablet is introduced January 5, 2011.
It was the first tablet to be sold with Android 3.0 aka Honeycomb.
Build up with 2 MP front-facing camera and a rear-facing 5 MP camera that records 720p video.
The Screen has a 1280×800 px widescreen, 10.1-inch display and 3D graphics acceleration.
Inside it runs a Nvidia Tegra 2 T20, 1 GHz dual-core processor combined with 1 GB DDR2 SDRAM and 32 GB Internal Memory and also could be upgraded with External SDHC microSD card slot.
At the Google I/O conference (June 27, 2012) it was announced that the Xoom would be one of the first devices to receive an upgrade to Android 4.1 aka Jelly Bean.
We have these great Product but for Developers we need so much more Informations:
If we followed the Post in the Developer Section we could readout Problem about the Size of the System Partition.
The short story is that Motorola only allocated 236MB to the system partition on the Xoom.
But with new Android Versions like Jelly Bean it fits around nearly 231MB.
Sad when you realize that there is a giant 32GB flash memory chip built in.
We could say hardware will work, but the system partition is just too small.
We should start Petition to get from Moto / Google more Informations and hopefully updated Bootloader with new Partition Layout but better would be NvFlash or ADB / Fastboot Command Support integrated.
NvFlash need the secure boot key so lets talk =)
########## Petition Text #######
To: Motorola / Google
----------------
Release the Secure Boot Key for Xoom Family Devices and bring up new Bootloader
We as consumers have loved the product that Motorola created, but feel that we should also have unlimited access to the devices we purchased.
Its great to bring up newest Android Version to Xoom but also updated Partition Layout please.
Not only does the SBK unlock huge potential for the Xoom, it also protects its users from possible bricked devices.
----------------
Sincerely,
[Your name]
Click to expand...
Click to collapse
Should we start it ???

Sounds like a good idea, but would Motorola take the risk? Since changing partition tables could screw over your tablet.

Motorola stopped updates on several other devices after they announced updates, why would they continue support for this one?
I really wish the OEMs would release their own non-carrier updates with the cavat that they will destroy all your data, and leave it up to the end user to decide if they are okay with that, instead of forcing us all into OTA releases and stopping update support.
[Motorola Atrix and Xoom owner]

I think if we could get enough activity about the Xoom they could bring up the needing points.
I actually also write to Motorola at Twitter:
@Motorola Motorola Xoom System Partition to small, please upgrade them to 1GB we have 32GB NAND inside! Update Bootloader for it please!
Click to expand...
Click to collapse
and also another point of special
@Motorola Bring Motorola Xoom telephony support. Hardware is okay only Modem and Libs doesn´t allow it. Support these great Product !!
Click to expand...
Click to collapse
Lets write to Motorola ... maybe we could win =)

In the GED Xoom don't Motorola only support hardware - Google to support software - so I half wonder if this will fall in deaf ears if directed at Moto

Lothaen said:
In the GED Xoom don't Motorola only support hardware - Google to support software - so I half wonder if this will fall in deaf ears if directed at Moto
Click to expand...
Click to collapse
Moto's ****ty partitioning is the reason we have this problem. I don't know which genius only set aside 236mb out of 32GB + an SD card slot but their lack of foresight is causing problems for devs.

063_XOBX said:
Moto's ****ty partitioning is the reason we have this problem. I don't know which genius only set aside 236mb out of 32GB + an SD card slot but their lack of foresight is causing problems for devs.
Click to expand...
Click to collapse
I think if we could flash Alternative Bootloader like U-Boot it would help too,but Motorola / Google should release Bootloader with Partition modification Support like other Companys does.
Partition layout at config file inside own Partition would be great or simply fastboot commands!
Hope more people would help these Command!
Sent from my GT-I9300 using xda app-developers app

Hello,
today i write to the Google Group who Jean-Baptiste Queru telling about the new Sources (4.2) and the Statement of Xoom doesn´t support any more.
-There is no support for 4.2 on Nexus S and Xoom. Those devices should
continue using 4.1.2.
Click to expand...
Click to collapse
I can't comment about the future of Nexus S and Xoom, sorry.
Click to expand...
Click to collapse
So i released answer about these Statement: Hope it would be agreed and is readable soon so maybe we got new Answer direct from Google!

xlanhackerx said:
Hello,
today i write to the Google Group who Jean-Baptiste Queru telling about the new Sources (4.2) and the Statement of Xoom doesn´t support any more.
So i released answer about these Statement: Hope it would be agreed and is readable soon so maybe we got new Answer direct from Google!
Click to expand...
Click to collapse
You won't.

063_XOBX said:
You won't.
Click to expand...
Click to collapse
Seems to be , the author doesnt publish my answer !
I receive only notification that the post would be readable and i become now access to the aosp group!
Sent from my GT-I9300 using xda app-developers app