yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] halomademeapc:
I'm also not an expert, but considering that CM encourages people to build and distribute the ROM, which includes the apps, it would make sense that distributing parts of the ROM is perfectly acceptable. I'll host them on my SkyDrive as well, along with some other CM apps I have a hard time living without (namely Torch, Calculator, and cLock)

Edit: http://sdrv.ms/18Npe8I apks are in the Xoom folder. Just push to your device and install like a normal user app.
[Xoom Android Development] menissalt:
Are you able to access the Treb. settings? I haven't figured out a way how yet.

::EDIT::

NVM, I'm just tired and stupid right now.
[Xoom Android Development] halomademeapc:
To work around it, you can use apex launcher or any app with the option to launch an activity then expand trebuchet and pick settings.
[Xoom Android Development] rajones19:
To me, the biggest downfall to Trebuchet is the inability to back up your settings and homescreen layouts. If that's changed, somebody PLEASE straighten me out.
[Xoom Android Development] notbrodie:
just back up trebuchet's data with titanium or any other backup utility
[Xoom Android Development] pots22:
4.3 Everest

Hello [MENTION=2383306]dreamcwli[/MENTION]

In Taipei, I hope not like in Hong Kong: big invasion of Hornet.
[Xoom Android Development] audioblivious:
Is there any news on a stingray flavor of 4.3
[Xoom Android Development] Winesnob:
Doesn't appear to be much happening on any variant at this point. I'm back to 4.2.2 as there may be no future Xoom development given the age of the hardware and the GPU issues at present.
[Xoom Android Development] stylez:
Not sure it's a GPU issue if it's the same graphic issue as seen on many divices it seems like kernel build mis match issue, since no 4.3 kernel available for XOOM.
[Xoom Android Development] shpitz461:
Just patience... BRD is on it, and it's not a top priority at the moment, he's onto many other things, so just be patient.

Either he's working on it, or he just received my tablet and ran away... LMAO
[Xoom Android Development] halomademeapc:
Any way to enable the charging light on this?
[Xoom Android Development] bigrushdog:
Yes! Yes! I was getting bored of my HTC One and hustled to get a free Xoom! Lol.

Tonight I'll see what the options are for repartitioning. At some point a decision must be made. Do we try it and risk brick or do we step into the unknown and maybe enjoy a 1GB /system partition. Only one of two outcomes....
[Xoom Android Development] shpitz461:
Would this be of any help?

http://xdaforums.com/showthread.php?t=1203128

And here posts #5-6
[Xoom Android Development] bigrushdog:
I agree. I'm running [MENTION=2383306]dreamcwli[/MENTION] 's build on the xoom [MENTION=583152]shpitz461[/MENTION] sent me. 100% for sure it's the kernel. Also keep in mind, the newest blobs we have are from 4.1.2. Those are ancient.

I did some messing around last night and I think I have a roadmap for repartitioning. I'll lay these steps out just for folks to reflect on. Also, if anybody has any intelligent input it would be most appreciated.

We are going to do a NAND dump onto a USB drive over OTG. The usb drive must be formatted as NTFS or EXT4 due to the NAND size of just over 32GB. Only with a full NAND dump can we utilize tools such as parted to analyse the image and get partition offsets.

To execute the NAND dump, we do the following in a root shell.

dd if=/dev/block/mmcblk0 of=/mnt/usb/otg/path/to/drive

Notice: the "of - output file" path is made up because i don't know it. The process will take probably a couple hours.

From there, we take the NAND image and run it through "parted" or a similar drive image analysis tool to get the offsets for mmcblk0p8, mmcblk0p9, and mmcblk0p10 (/system, /cache, and /userdata, respectively)

Since we wish to resize the /system partition, we will also have to resize /cache and /userdata accordingly. The good news is they are all ext4 and physically next to each other! We don't have to touch any of the emmc partitions like radio and bootloader.

Once we get this far, I'll post up my next thoughts. I'll try this tomorrow, but if anybody gets motivated and want's to dump a NAND, let me know. I'll get you a way to deliver the NAND image to me.
[Xoom Android Development] realjumy:
32GB???? Wow!!! I will look for an USB stick with that size and then I will try to do it for you.
[Xoom Android Development] halomademeapc:
I think a portable hard drive would handle that job well. I can probably try it in the next few days.
[Xoom Android Development] realjumy:
Yes, I was considering that, but right now all my USB HDs are full...
[Xoom Android Development] shpitz461:
I think the image would compress pretty good since most of the 32GB space is supposed to be empty.
[Xoom Android Development] taninos:
[MENTION=470268]bigrushdog[/MENTION] Dear friend, I need your help to solve a personal problem. I'm allergic to the UV of backlight screens, so I need to control the color temperature of any device screen to avoid damaging my eyes. Hence, I would like to ask you if we can control or adjust the color temperature and gamma effect through this rom or EOS 4 rom settings.

Many thanks in advance.

Best.
[Xoom Android Development] Zn7mkUKzN1r8aCIV:
looking for 4.3 compatible RIL(s)

Sorry to interrupt, I am from Atrix 4G and working on 4.3, but hit roadblock on RIL

it seems that CM4.3 phone ril has changed a lot and Atrix's libmot_ril.so is no longer compatible

Do you guys by any chance have source/binary for 4.3 RILs for Moto Tegra2 and care to share?

Thx. in advance
[Xoom Android Development] Cameron581:
We don't use rils since we a a tablet... I could be wrong
[Xoom Android Development] pkelly517:
Well, there is that whole Stingray gotta connect to VZW 3G/4G thing.
[Xoom Android Development] bigrushdog:
Something I forgot to mention. We can use any rom, any version, that has USB otg working to make the image dump. Since the partition information stays the same.... Heck. I've been slacking guys... I'm dumping this bad boy tonight! I just got mad lol!
[Xoom Android Development] bigrushdog:
This ROM is not my project and, Regrettably, the eos project is no longer supported.

We got about 20 steps to go before we even get to the subject of radios. I can tell you cdma is a total nightmare on 4.3. But no, nobody has source for any proprietary radio libs. I'd start by decoding and hacking up proprietary radio apks though.
[Xoom Android Development] bigrushdog:
Ok guys. I got my ntfs USB drive with plenty of storage and I loaded some Eos :D since it is easier to work with. But I discovered ntfs mount is borked on it. Crappy eos devs :P. So... What are you guys using to mount ntfs?
[Xoom Android Development] realjumy:
I think that I found a HD that I can use for doing this. If everything is working fine, I can format it into EXT4. But first, I need to finish formatting my computer and then check if I can temporally copy all the data from that HD. I will let you know...
[Xoom Android Development] notbrodie:
does it have to be ntfs? why not ext4?

Sent from my Nexus 4
[Xoom Android Development] bigrushdog:
It can be any fs xoom can mount and must be able to hold large files. I'm doing my work from 4.2.2. So I'll write a simple script to do all the work. I'll post a flash zip to install script. Then when the first person is up and running, they can just run "dumper" in a terminal. I think there's a root app for mounting file systems. I'll look.
[Xoom Android Development] chykal:
Try USB mass storage watcher.
[Xoom Android Development] alex_72gr:
CM10.1 can mount NTFS without any external program
[Xoom Android Development] bigrushdog:
Ok. Between the two I'll get something going. I'm telling you guys, this one is a science project!
[Xoom Android Development] shpitz461:
haha, going back to school baby!

We're crossing our fingers,,,
[Xoom Android Development] realjumy:
OK, I finally have a HD that I can use for this. I have an Everest Xoom. Tomorrow I will follow the steps that you posted and then I will send you a link...
[Xoom Android Development] realjumy:
OK guys, let's do it!
[Xoom Android Development] notbrodie:
will this 4.3 mod require all users to dump to USB otg? or will you eventually be able to script it?

Sent from my Nexus 4
[Xoom Android Development] drewski_1:
I could be wrong, but it sounds like the dump is for forensic purposes.

Repartitioning will probably be needed which I don't think is dependent on everyone doing a system dump.

My take. I'll let the experts give the real skinny.
[Xoom Android Development] realjumy:
Bad luck guys. In the 1st trial, the tablet freezed after ~1hour dumping... I will try again. Lets hope I will have no further problems...
[Xoom Android Development] realjumy:
[MENTION=470268]bigrushdog[/MENTION], I can't try it now because my Xoom is dumping right now but, do you think that we can use

./adb pull /dev/block/mmcblk0 ./

to avoid the need of a big USB drive?
[Xoom Android Development] realjumy:
Done! [MENTION=470268]bigrushdog[/MENTION], send me a PM.
[Xoom Android Development] hawkstorm:
[MENTION=470268]bigrushdog[/MENTION], [MENTION=2383306]dreamcwli[/MENTION]

Hey guys, I'm willing to help with development for MZ601 (everest) if you need to test builds etc. Just PM me if you need me to test anything.
[Xoom Android Development] bigrushdog:
I was in a deep sleep and my wife woke me over some bs. I check my notifications and I see some win! Ok. Gimme a few to wake up. In the meantime, Google for "disk image partition analysis". We need a full knowledge dump of all the partitions on that image. Linux tools are free. Windows tools, not so sure. Post up what you find. And CONGRATULATIONS! we're now in uncharted waters!
[Xoom Android Development] bigrushdog:
Also, we need a "cat /proc/partitions" posted up for wingray and everest. Remember, I'm working on a stingray. So we need to see if all the devices have the same partitions.
[Xoom Android Development] EKershner:
For Wingray:

root@wingray:/ # cat /proc/partitions

cat /proc/partitions

major minor #blocks name

7 0 12506 loop0

7 1 5229 loop1

7 2 4190 loop2

7 3 23940 loop3

7 4 18743 loop4

7 5 2111 loop5

7 6 2111 loop6

7 7 2111 loop7

253 0 73236 zram0

253 1 98304 zram1

179 0 32422912 mmcblk0

179 1 32418816 mmcblk0p1

179 8 31162368 mmcblk1

179 9 3072 mmcblk1p1

179 10 2048 mmcblk1p2

179 11 2048 mmcblk1p3

179 12 4096 mmcblk1p4

179 13 2048 mmcblk1p5

179 14 12288 mmcblk1p6

179 15 8192 mmcblk1p7

259 0 262144 mmcblk1p8

259 1 173056 mmcblk1p9

259 2 30663168 mmcblk1p10

254 0 12505 dm-0

254 1 5229 dm-1

254 2 4189 dm-2

254 3 23940 dm-3

254 4 18742 dm-4

254 5 2110 dm-5

254 6 2110 dm-6

254 7 2110 dm-7

root@wingray:/ #
[Xoom Android Development] ro.chi:
For Everest:

u0_a34@android:/ $ su

root@android:/ # cat /proc/partitions

major minor #blocks name

253 0 71492 zram0

179 0 30702592 mmcblk0

179 1 30698496 mmcblk0p1

179 16 31162368 mmcblk1

179 17 3072 mmcblk1p1

179 18 2048 mmcblk1p2

179 19 2048 mmcblk1p3

179 20 4096 mmcblk1p4

179 21 2048 mmcblk1p5

179 22 12288 mmcblk1p6

179 23 8192 mmcblk1p7

179 24 262144 mmcblk1p8

179 25 173056 mmcblk1p9

179 26 30663168 mmcblk1p10

179 48 1024 mmcblk1boot1

179 32 1024 mmcblk1boot0

root@android:/ #
[Xoom Android Development] shpitz461:
Can you post the partition listing for Stingray? I'm curious how it compares to the other two posted above :)
[Xoom Android Development] AlEsC:
I do not have the exact same result on my Wingray MZ604 :

major minor #blocks name

7 0 26019 loop0

7 2 11466 loop2

179 0 31260672 mmcblk0

179 1 3072 mmcblk0p1

179 2 2048 mmcblk0p2

179 3 2048 mmcblk0p3

179 4 4096 mmcblk0p4

179 5 2048 mmcblk0p5

179 6 12288 mmcblk0p6

179 7 8192 mmcblk0p7

259 0 262144 mmcblk0p8

259 1 173056 mmcblk0p9

259 2 30761472 mmcblk0p10

254 0 26019 dm-0

254 2 11466 dm-2
[Xoom Android Development] EKershner:
I am using a different kernel that enables zram (compressed swap space). Also, a sdcard was installed and mounted when the command was executed. This might account for some of the difference.

Thanks
[Xoom Android Development] bigrushdog:
Can you remove the micro SD and run it again. We gotta be real sure on this one.
[Xoom Android Development] EKershner:
Sure.

Here is the output with sdcard removed and zram disabled. I rebooted after making the changes to make sure things were refreshed. BTW, sdcard dismounting is not working in the 4.3 test build. ;)

If you would like me to rerun after a clean install, let me know.

root@wingray:/ # cat /proc/partitions

cat /proc/partitions

major minor #blocks name

7 0 12506 loop0

7 1 2111 loop1

7 2 4190 loop2

7 3 2111 loop3

7 4 23940 loop4

7 5 18743 loop5

7 6 5229 loop6

7 7 2111 loop7

253 0 98304 zram0

253 1 98304 zram1

179 0 31162368 mmcblk0

179 1 3072 mmcblk0p1

179 2 2048 mmcblk0p2

179 3 2048 mmcblk0p3

179 4 4096 mmcblk0p4

179 5 2048 mmcblk0p5

179 6 12288 mmcblk0p6

179 7 8192 mmcblk0p7

259 0 262144 mmcblk0p8

259 1 173056 mmcblk0p9

259 2 30663168 mmcblk0p10

254 0 12505 dm-0

254 1 2110 dm-1

254 2 4189 dm-2

254 3 2110 dm-3

254 4 23940 dm-4

254 5 18742 dm-5

254 6 5229 dm-6

254 7 2110 dm-7

root@wingray:/ #

Thanks.
[Xoom Android Development] realjumy:
No problem. I hardly use Windows :P

---------- Post added at 06:39 AM ---------- Previous post was at 06:21 AM ----------

Everest, UK model, freshly flashed:

major minor #blocks name

179 0 31166976 mmcblk0

179 1 31162880 mmcblk0p1

179 8 31162368 mmcblk1

179 9 3072 mmcblk1p1

179 10 2048 mmcblk1p2

179 11 2048 mmcblk1p3

179 12 4096 mmcblk1p4

179 13 2048 mmcblk1p5

179 14 12288 mmcblk1p6

179 15 8192 mmcblk1p7

259 0 262144 mmcblk1p8

259 1 173056 mmcblk1p9

259 2 30663168 mmcblk1p10

---------- Post added at 07:07 AM ---------- Previous post was at 06:39 AM ----------

I think that there is a lot of useful info here: http://xdaforums.com/showthread.php?t=1959445

---------- Post added at 08:39 AM ---------- Previous post was at 07:07 AM ----------

ls -al /dev/block/platform/sdhci-tegra.3/by-name

lrwxrwxrwx root root 2013-10-29 06:17 boot -> /dev/block/mmcblk1p7

lrwxrwxrwx root root 2013-10-29 06:17 cache -> /dev/block/mmcblk1p9

lrwxrwxrwx root root 2013-10-29 06:17 ebb -> /dev/block/mmcblk1p1

lrwxrwxrwx root root 2013-10-29 06:17 kpanic -> /dev/block/mmcblk1p5

lrwxrwxrwx root root 2013-10-29 06:17 logo -> /dev/block/mmcblk1p4

lrwxrwxrwx root root 2013-10-29 06:17 misc -> /dev/block/mmcblk1p3

lrwxrwxrwx root root 2013-10-29 06:17 pdsb -> /dev/block/mmcblk1p2

lrwxrwxrwx root root 2013-10-29 06:17 recovery -> /dev/block/mmcblk1p6

lrwxrwxrwx root root 2013-10-29 06:17 system -> /dev/block/mmcblk1p8

lrwxrwxrwx root root 2013-10-29 06:17 userdata -> /dev/block/mmcblk1p10
[Xoom Android Development] Yuccaman:
Most of this is so far over my head I can't see it, but here's a UK Wingray output from EOS 3 155.

au0_a32@android:/ $ cat /proc/partitions

major minor #blocks name

7 0 9387 loop0

7 1 26019 loop1

7 2 12506 loop2

7 3 14585 loop3

7 4 16664 loop4

7 5 12506 loop5

7 6 2111 loop6

7 7 54086 loop7

253 0 131072 zram0

179 0 15558144 mmcblk0

179 1 15554048 mmcblk0p1

179 16 31260672 mmcblk1

179 17 3072 mmcblk1p1

179 18 2048 mmcblk1p2

179 19 2048 mmcblk1p3

179 20 4096 mmcblk1p4

179 21 2048 mmcblk1p5

179 22 12288 mmcblk1p6

179 23 8192 mmcblk1p7

179 24 262144 mmcblk1p8

179 25 173056 mmcblk1p9

179 26 30761472 mmcblk1p10

179 48 2048 mmcblk1boot1

179 32 2048 mmcblk1boot0

254 0 9387 dm-0

254 1 26019 dm-1

254 3 14584 dm-3

254 4 16663 dm-4

254 6 2110 dm-6

254 7 54085 dm-7

7 8 30177 loop8

254 8 30177 dm-8

7 9 17703 loop9

254 9 17703 dm-9

7 10 8348 loop10

254 10 8347 dm-10

7 11 48888 loop11

254 11 48888 dm-11

7 12 82184 loop12

254 12 82183 dm-12

7 13 55125 loop13

254 13 55125 dm-13

7 14 34335 loop14

254 14 34335 dm-14

7 15 2111 loop15

254 2 12505 dm-2

254 15 2110 dm-15

254 5 12505 dm-5

7 16 46809 loop16

254 16 46809 dm-16

7 18 2111 loop18

254 18 2110 dm-18

u0_a32@android:/ $
[Xoom Android Development] pots22:
4.3 Everest

Hard Job

Exciting for an Everest 4.3 experimental :p
[Xoom Android Development] realjumy:
I can only see that with the SD in the Xoom... Maybe we are looking in the wrong place...

In addition, I have no luck with my dump, maybe it's corrupted... Damn!

---------- Post added at 12:24 PM ---------- Previous post was at 11:54 AM ----------

OK, 7 hours of researching is enough for me... More tomorrow... [MENTION=470268]bigrushdog[/MENTION] maybe this will be useful for you: http://www.imajeenyus.com/computer/20130301_android_tablet/android/index.html

I think that maybe we can't go further because of the Cyanogenmod rom. I will try to restore a system image, root it and then use it to work. I will try to use ADB instead of a HD in order to avoid the use of Cyano.

If you figure up how to see the offsets or to manage the dump image, let me know and I will help with the Everest version.
[Xoom Android Development] bigrushdog:
It looks like you are executing parted on Android. I'm sorry I should have been more clear. You want to execute parted on your linux box and analyze the image dump. If you still have issues I'll give you ssh on my server and you can scp it.
[Xoom Android Development] realjumy:
Don't worry. I tried both Linux and Android. No results:

Error: /home/jumy/Desktop/TMP/mmcblk0: unrecognised disk label
[Xoom Android Development] bigrushdog:
Ok no worries. I'll give you a ssh account today so we can try scp. I'll PM you info later today when I get up. Very nice work sir.
[Xoom Android Development] realjumy:
Anyway, I will try later to do another dump... Maybe I have a corrupted one...
[Xoom Android Development] realjumy:
2nd attempt:

./adb pull /dev/block/mmcblk0 /home/dump

Seems to be slightly faster than the other command.

EDIT: After thinking about it, I believe that what I will obtain with this command will be not useful... I should be using dd instead...

EDIT2: The complete process should finish in 3 hours. After the 1st hour I decided that that method should not work, so I'm trying with another method that bypass the step of the HD plugged to the Xoom... If it work, I will let you know. At the moment seems to work :)
[Xoom Android Development] realjumy:
BINGO!!!!

Using EOS4 V170.

Partition Start End Size in sectors
>P MS Data 47104 51199 4096
P MS Data 61440 65535 4096
P MS Data 122880 647159 524280
P MS Data 647168 993279 346112
P MS Data 993280 62319583 61326304

[MENTION=470268]bigrushdog[/MENTION], I hope that this will be useful :)

---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------

Aaaaand more info here:

Error: The backup GPT table is corrupt, but the primary appears OK, so that will be used.
OK/Cancel? ok
Model: (file)
Disk /home/jumy/Downloads/Android/adt-bundle-linux-x86_64-20130917/sdk/platform-tools/mmcblk0.raw: 31.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 24.1MB 26.2MB 2097kB ext2
2 31.5MB 33.6MB 2097kB ext2
3 62.9MB 331MB 268MB ext4
4 331MB 509MB 177MB ext4
5 509MB 31.9GB 31.4GB ext4

(parted)

---------- Post added at 09:39 PM ---------- Previous post was at 09:35 PM ----------

And here you go, we are in sales!!! :P

Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged

****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************
Disk mmcblk0.raw: 62324737 sectors, 29.7 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): A2D1248F-4AD6-524E-8792-E3AA13175D0F
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 62324703
Partitions will be aligned on 2048-sector boundaries
Total free space is 119782 sectors (58.5 MiB)

Number Start (sector) End (sector) Size Code Name
1 47104 51199 2.0 MiB 0700
2 61440 65535 2.0 MiB 0700
3 122880 647159 256.0 MiB 0700
4 647168 993279 169.0 MiB 0700
5 993280 62319583 29.2 GiB 0700

---------- Post added at 09:46 PM ---------- Previous post was at 09:39 PM ----------

This looks great. brd, I'm going to send you and PM to see if we can compare the results.
[Xoom Android Development] bigrushdog:
[MENTION=697814]realjumy[/MENTION] I got your email and I'm dumping stingray now. MUCH more elegant than the slop I was posting lol. Very nice find sir.

http://www.df.lth.se/~jokke/androidfilerecovery/

If anybody wants to participate that's where the juice is. Next, we can start work on a repartition script and cross our fingers.
[Xoom Android Development] bigrushdog:
Ok guys, while i got this dump going, I wanted to post some thoughts on the next move. Basically, I'm thinking let's resize the system partition to 1GB. This is inline with new devices and gives us plenty of room for the foreseeable future. So, what do we do?

Let's look at the partition table.

START END SIZE

3 122880 647159 256.0 MiB 0700

4 647168 993279 169.0 MiB 0700

5 993280 62319583 29.2 GiB 0700

"3" is the system partiton, "4" is the cache partition, and "5" is the userdata partition. So basically, we need some calculations. If system goes from 256 to 1024, that means the space has to be pulled from 4 and 5. So in other words, the start offset for system should stay the same, but all the other offsets will be shifted accordingly.

I'll do some googling and see if there's a "easy offset calculator" somewhere. Once we have that info, we can produce a recovery script to do all the work for us.

When my stingray dump is done, i'll compare against the info already posted by [MENTION=697814]realjumy[/MENTION]. We need to ensure the start offset for system is the same for all devices. If not, we'll need more dumps. But that is easy now with the WIN [MENTION=697814]realjumy[/MENTION] found.
[Xoom Android Development] realjumy:
Check in the Samsung threads, there is a lot of useful info there, as many of these handsets have the same problem than Xoom.
[Xoom Android Development] ggrammer:
couldn't we just take the difference of the end offset and the start then calculate? so the system partition is 256 MB so we subtract the start from the end then add that number to the end offset 3 times giving us 1024MB offset. Here is what I calculated. Now I increased the cache from 169 to 256 in these calculations

3 122880 - 2219996

4 2219997 - 2744276

5 2744277 - 62319583

please let me know if I am wrong.

Sorry forgot to account for the extra 1 and being divisable by 16. new offsets

3 122880 - 2219999

4 2220000 - 2744287

5 2744288 - 62319583

---------- Post added at 12:51 AM ---------- Previous post was at 12:11 AM ----------

or if you wanted to keep cache the same

3 122880 - 2219999

4 2220000 - 2566111

5 2566112 - 62319583
[Xoom Android Development] realjumy:
I will write what I'm finding about the offset calculation:

http://xdaforums.com/showthread.php?t=1959691

http://aarondiep.blogspot.co.uk/2011/11/resize-partition-on-android.html

http://www.modaco.com/topic/357459-acer-gallant-duo-root-hacking-tools/page-5
[Xoom Android Development] jasonbtx:
Hell Yeah!! Get Gang!!
[Xoom Android Development] RedWingsFanEd:
Do you think Kit Kat will be easier?

http://androidcommunity.com/android-4-4-tipped-to-address-low-end-phones-wearables-and-tvs-20131031/
[Xoom Android Development] realjumy:
Maybe. But changing the size of the partitions will make it even easier.
[Xoom Android Development] realjumy:
By the way, in less than 24 hours KitKat will be released...
[Xoom Android Development] notbrodie:
more like: in less than 2 hours :smiley
[Xoom Android Development] realjumy:
Yes, indeed: http://www.android.com/versions/kit-kat-4-4/

Now let's see how to manage the repartioning, and let's see if Xoom KitKat is possible :)
[Xoom Android Development] notbrodie:
that would be amazing. I thought I'd read that support for non-neon devices had been dropped from Android. our was that only cm?

Sent from my Nexus 4