yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] armido:
Linux kernels

My understanding of linux is mediocre at best. Linux is backward compatible with older hardware because the kernel includes older drivers. Linux kernels are regularly updated to include new drivers for new hardware - provided the manufacturers make the driver code available to the open source community. Failing that, the Linux community of developers engineer drivers that while often imperfect, work well enough. The problem with the Nvidia folks who manufactured the Tegra2 is they have been hostile to the open source community. According to this: http://www.slashgear.com/meego-tegra-2-drivers-could-end-android-monopoly-on-nvidia-soc-27167704/ , drivers were released by Nvidia back in 2011. Were they or were they not? I'm not a kernel guru & get sweatty palms just trying to compile a custom kernel. The question I have is, if the drivers for the Tegra2 are available, can they be compiled into a custom kernel? Have they already been compiled into one of the kernels distributed by the well known Linux packagers such as Ubuntu, Fedora or Debian? Linux distributions for the armhf architecture can be installed using Linux Deploy from Google Play. Granted, there is no kernel included, but Fedora for example offers installs with and without kernels for some platforms. Once installed on an android tablet in a chroot environment, would it be possible to compile a custom kernel drawing drivers in from the android side?

Finally, why can't we create a boot image using a modified grub boot manager and replace android altogether with Linux? I believe Linux developers are already adapting Linux programs for use with touch screens. Witness the computers being sold now with touch screens.
[Xoom Android Development] Asphyx:
The problem is threefold...

1 - There are no sources (from Moto anyway) that are compatible with the newer android flavors.

2 - The Hardware itself is missing key innovations that newer hardware (Chipset) has that is almost impossible to duplicate via software alone.

3 - Android is not written in a way that is STANDARDIZED as far as Kernel Access is concerned when going from one version of Android to the other. The assumption is that the Manufacturer will change the Kernel to fit the Android version they will put on their device as opposed to Android source being written to support every Kernel that might exist. So instead of the Operating system being written for the Kernel as it is under most OS environments, it is the reverse the Kernel in most cases is written to fit the Operating system.

Which is why once your unit stops getting OFFICIAL updates your more or less locked into whatever the last version of Android they released was and can maybe squeeze a few more minor updates out if the Kernel will support those Minor Updates.

Kit Kat maybe different as it seemed to be a goal of this version supporting more older devices.

I guess we will find out soon enough.
[Xoom Android Development] armido:
Nothing ventured, nothing gained...

You didn't address my suggestion, if possible, to abandon android for Linux. The text below was taken from the Fedora website https://fedoraproject.org/wiki/Architectures/Fedora_ARM_Kernels . It concerns android devices with Tegra2 chips and discusses both the kernel and boot process. Isn't there anything there that suggests with some tinkering everything might be adapted to work on our Xooms? The repartitioning to accommodate a larger kernel has already be accomplished. I'll apologize in advance if some believe the idea is foolish, but we Aquarians are dreamers.

Installing the Fedora ARM Kernel

Both of the boards selected for testing use the U-Boot bootloader, so support was added to the grubby package to automate the creation of appropriate U-Boot images for the kernel being installed. Automatic boot of the installed kernel is accomplished through configuring the U-Boot autoboot script to use those U-Boot image files.

Issues

U-Boot does not support a "boot menu", like lilo or grub

U-Boot partitions are vfat, which means no hard links

U-Boot does not support symlinks

Assumptions

U-Boot will use an autoboot script (boot.scr uEnv.txt)

The kernel will boot using an initrd

The U-Boot partition (vfat) will be mounted on /boot/uboot

the default boot images will use standard named files (i.e. uImage, uInitrd)

Approach

To automate the kernel installation for U-Boot, the grubby package was modified as follows:

require uboot-tools

add sections to handle U-Boot images in both update and remove

run mkimage in the RPM posttrans script if U-Boot is configured

copy the new images to uImage and uInitrd (making it the default)

remove the corresponding version of U-Boot images when a kernel is removed

Multiple kernel version images may be installed, and kernel versions may be switched by simply copying the desired image versions to uImage and uInitrd and rebooting. The only negative is some wasted space in the U-Boot partition, since two copies of the default kernel and initrd are stored.

No U-Boot specific changes were made to the kernel package, so it can be installed elsewhere without using the modified grubby, although in that case the U-Boot files would not be automatically updated.

A simple text file was added that keeps a log of the installed kernel versions (assuming they were installed via yum or rpm). When a new kernel is installed its version is appended to the list. When a kernel is removed its version entry is removed from the list. The last entry in the list is always assumed to be the default. If the default kernel is removed, the "new default" version of the U-Boot image files (the new "last" version in the list) are copied to uImage and uInitrd.
[Xoom Android Development] LOGMD:
Use other sources besides android for tegra stuff

[MENTION=4674742]armido[/MENTION] [MENTION=744716]Asphyx[/MENTION]

but here's an idea, the nvidia Tegra official project i have not read enough into it but maybe we could create a driver based on the Nvidia tegra source?

open source driver for tegra devices i know its probably for a full distro of linux but ports have been made before ;)

and as much as we could port linux we could portlinux drivers to android with some work!? especially if they are based on tegra or arm architecture. there was some work going into the ubuntu project too
[Xoom Android Development] jwbtx:
+1

I know i won't part with my Xoom until its dead or I am .
[Xoom Android Development] logitechor:
I still use the Xoom daily. I do have 4.3 on repartitioned Xoom. It works fine. If it is the last update that can be successfully made count me as very happy. All the developers have made the Xoom a better tablet the Motorola.
[Xoom Android Development] Alxoom33:
After updating to Big Part and losing root on 4.3 I went back to the EOS 4 203 build. I'm happy to wait for 4.4 KitKat on my Xoom!
[Xoom Android Development] Asphyx:
Yes But then your just running Linux which is fine if you want Linux but does nothing for KitKat.

I use my Tab like just a big version of my phone and truth is I would (myself) rather stick with the EOS I have than move to linux merely because it is easier to make drivers for it.

What I would hope for is that Moto releases a new Tablet that has KitKat so we could take the source from that and tweak it to work with the older Tegra2 we have...

But I have faith that we will see a KitKat working for Xoom..Beyond that maybe not...

BTW Kit Kat dropped into AOSP so lets keep our fingers crossed.
[Xoom Android Development] Alxoom33:
4.4.1 source was released, yesterday, I believe.
[Xoom Android Development] mmfxda:
Revert Partitions.

I have flashed Bigpart, repartitioned and installed MyWingray 4.3 Successfully. However I am noticing major lag and was wondering if going to stock is even possible at this point. Do I need to revert the partitions in order to downgrade the OS?

If so, how?
[Xoom Android Development] shpitz461:
good question, but try to O/C the tablet and see if it helps. Also, try Nova (or any other) launcher, it's not lagging too bad for me...
[Xoom Android Development] notbrodie:
download trickster mod app from. play store. set cpu governor to ondemand, set io scheduler to noop/row (if present), and set readahead to 512/2048.

see if that doesn't make a difference

Sent from my Nexus 5
[Xoom Android Development] Domunus:
Also don't enable Z RAM, that caused terrible lag with Bigpart for me.
[Xoom Android Development] flar2:
Hey guys, anyone have a link for the bigpart kernel patch?

I was looking through the thread and found this, but not sure if it is final or not

http://xdaforums.com/showpost.php?p=47421260&postcount=120

Nevermind: found it

https://github.com/codefireXperiment/kernel_moto_wingray
[Xoom Android Development] matt4321:
Here is the patch on it's own if people want it in the efi.c file

http://fs1.androidfilesharing.com/71665c4a68bb4100
[Xoom Android Development] audioblivious:
Does the cm 10.1 partition work for this or do I have to do the instructions if so how do I do it with cwm I don't use trwp
[Xoom Android Development] sepia66:
I am using CM10.1 and it works flawlessly. It is imperative to flash Matt's BigPart boot image each time you update the CM10.1 ROM. Otherwise it will not boot. Happened to me just yesterday.
[Xoom Android Development] realjumy:
That's is because CM don't includes BP. If they decide to change to BP or release both versions (regular and BP) you don't need to flash the BP boot image.
[Xoom Android Development] hawkstorm:
The elemental-X kernel has been updated to support the BP mod in beta. Thanks to [MENTION=4684315]flar2[/MENTION]!
[Xoom Android Development] audioblivious:
So I can just flash this 4.3 right over cm 10.1?
[Xoom Android Development] sepia66:
If you re-partitioned you need to flash the 4.3, then the 4.3 BigPart boot image and then the GAPPS.
[Xoom Android Development] pots22:
Flash different ROM in BIGPART

I make the repartition guide from the first page here and flash EOS 4 umts Everest + EOS 4 bigpart + Gapp

Reboot and work perfect with Systeme size 1007 Mo.

After that i reboot in the recovery make only Wipe (Swipe to factory reset) + Advanced wipe all except sdcard.

flash wingray 4.3 + 4.3 bigpart reboot and the partition stay the same 1007 Mo

And finaly i reboot on recovery, juste wipe all, flash CM 10.1 from 09/12/2013 + CM 10.1 bigpart + Gapp EOS

reboot and work like a charm with the same bigpart system file.

So for me when you make this after you just flash the rom you like but all the time with the specific bigpart boot img.
[Xoom Android Development] audioblivious:
Ok from ur guide it uses trwp I use cwm can you make a guide using it also I use stingray version
[Xoom Android Development] drewski_1:
There is no BigPart CWM so you have to use the modified Big Part TWRP if you want to do this mod
[Xoom Android Development] audioblivious:
Ok so to have 4.3 on my xoom I have to do this big part partition
[Xoom Android Development] drewski_1:
no. Dream's 4.3 ROM works on the regular partition size, but there is only a Wingray version.
[Xoom Android Development] matt4321:
You can flash 4.3 from Dreamwclis thread, but would be small system partition
[Xoom Android Development] audioblivious:
Is there a stingray version of it last I heard only wingray is there a link that's why I'm here there's a stingray version
[Xoom Android Development] matt4321:
No, there isn't a stingray version
[Xoom Android Development] audioblivious:
Ok just here has a stingray version then
[Xoom Android Development] flar2:
You can still flash whatever ROM you want after the bigpart mod.

You just need to use a kernel with the appropriate patch (some are listed in OP)
[Xoom Android Development] audioblivious:
Just want a stingray version of 4.3 for xoom
[Xoom Android Development] drewski_1:
sit back, relax, and wait with the rest of us :D
[Xoom Android Development] KwestJones:
I tried the cm10.1 wingray big part on my stingray. No bueno as I didn't get any data. I unzipped it did a folder diff with the eos4 big part and the only significant change seemed to be the boot.IMG. it would have been too easy to just switch them out I suppose. It failed when i tried to flash it. Is there a way we can get a stingray cm10.1 big part zip?

Or....am I missing something? I wouldn't doubt it.
[Xoom Android Development] shpitz461:
Think about what you just said... you flash wingray and expect data?

There are drivers needed for the radios, which wingray doesn't have.
[Xoom Android Development] matt4321:
Did you flash a wingray or stingray system? Flash a stingray system if you flashed wingray.

Flash stingray CM10.1 then the wingray CM10.1 bigpart kernel
[Xoom Android Development] KwestJones:
Maybe I wasn't clear enough. It was a stingray ROM but the BigPart zip CM10.1 is for wingray hence my request for a BigPart CM10.1 zip for stingray.

---------- Post added at 09:26 PM ---------- Previous post was at 09:22 PM ----------

I flashed a stingray CM10.1 rom on a stingray system however due to the BigPart file system I have to do the BigPart zip which was made for wingray.
[Xoom Android Development] SgtTeabag:
And it works on my stingray!
[Xoom Android Development] Asphyx:
Yes it would seemingly work...BUT do you have 3G or LTE Data?

I bet you don't! LOL
[Xoom Android Development] ndt192:
how to restore the stock partitions?

I succeded in big repartition, but now I would like to return to the stock so as to use the baked ROM with its own kernel :( I flashed the R.A.H TWRP kernel (the common one, flashed by using bigpart one) and now my stingray just displays "TWRP" while loading to recovery. Could you show me how to restore to stock partitions? tks in advance
[Xoom Android Development] SgtTeabag:
Baked runs on big part too ya know? ;)
[Xoom Android Development] pots22:
TWRP

For me, to retrieved the stock partition i flash with Fastboot the stock ROM, after that i flash TWRP 2.6.3 with Fastboot but surprise TWRP don't open, stay on the logo TWRP

Finaly i find on my PC an old version of TWRP https://www.dropbox.com/s/kqmawi257iny2f5/recovery.img

Flash this version with Fastboot and working like a charm.

After i put The RAH 2.6.3 on the SDcard, restart in the recovery with my old version flash the new one and all ok.
[Xoom Android Development] ndt192:
this is what I'm seeking for :) tks bro :)
[Xoom Android Development] SgtTeabag:
Actually I get 3g LOL ;)

Actually I apologize I don't think I do now can't test till later
[Xoom Android Development] Chadwick108:
Running EOS nightly 199

Working Great!! was unable to install the latest nightly from EOS after doing the BigPart upgrade I currently running Nightly 199 with no issues!

thanks so much!!:good:
[Xoom Android Development] Asphyx:
Yes I am not sure that the CM Bigpart Boot.img has a Stingray Kernel in it. Perhaps it does.

In any case you might see a 3G Icon but not actually get any data over it.

If you don't perhaps a PM to the creator of the CM BigPart file can cook one up for Stingray as well.

It would seem that one of the big hurdles BRD was having was with the Radios in Stingray. The kernal code we have for them might just be completely incompatible with 4.3 and above which is why we hasn't been able to get them going. (Just Guessing BRD would be the best source for info on that).
[Xoom Android Development] Geeba:
I'm kinda confused.... Is Xoom development dead? I can remember reading that newer code won't work on it because of the Tegra limitations? I regularly check the forums to see if there is any movement, but it seems very quiet lately...

The big part stuff sound really promising especially as flare has modded his kernel to match... But is anyone actually working on a ROM?

I'm running EOS 203 with ElimentalX kernel... Really very good... What would I gain with big part? Is this just the neccasary foundation for newer ROM`s?

Wish I could help with a 4.4 port... :(
[Xoom Android Development] matt4321:
I had a tester who tested in the Q&A section who said it worked on everest, see here: http://xdaforums.com/showpost.php?p=47729626&postcount=5

also on the CM repos wingray, stingray and everest had the same kernel. so I thought it would work.

People need to make sure they flash either CM Stingray/Everest zip (system) first then the CM BigPart Wingray kernel to see if it works.

Also be sure, do various tests/reboots
[Xoom Android Development] Asphyx:
Perhaps it does...I have stayed away from doing the entire BigPart procedure myself until I know there is a 4.3 or 4.4 reason for doing it.

If not then I already have 4.2 with EOS so no reason to do it.

I can see Everest and Stingray using the same Kernel it does seem logical.

Guess we will find out when he can test it further.

Would be nice to know I could switch to CM and BigPart if I wanted to though I have no problem with the current ROm other than it being on so long the normal cruddup of the filesystem is slowing it down...

Time for a Factory Reset for me but I was waiting to see if anything developed on the Kit Kat front first.

And no Geeba, I wouldn't say it is dead...Just a lot harder to do these days than it was in the days before 4.2 came out.

It's the Holidays...People have Midterms and things to get ready for....Just be patient because if Kit Kat is possible on Xoom we will see it...If not it was a great run!
[Xoom Android Development] notbrodie:
is anyone else having problems flashing roms from within TWRP bigpart? i was unable to flash eos 203 until i copied the file to internal memory. when i tried to flash from sdcard, it just failed upon attempt
[Xoom Android Development] Adler12:
BigPart Xoom MZ601 Everest

Hi,

Today I was flashing the BigPart.

By the Instruction evrything was successful including Part 8.

Then Part 9

Go into install.

= OK

Recovery should show your microsd storage by default. If not, using the navigation panel, navigate to root then go into "sdcard".

= OK

Flash your rom, BigPart boot image package, and any other resources as you normally would.

= OK

Her I Flash first the Eos 4 BigPart Everest Boot Image, then EOS v170.

Then reboot into System.......nothing! It stop on the Motorola Splash-Screen. What do I wrong?

I need help.
[Xoom Android Development] grussinko:
Flash EOS rom first, then boot image second and it should work.
[Xoom Android Development] Adler12:
You are the Best......(-:

It works. Wow, my best Part is back on Life.

Do you now a good 4.3/4.4 ROM vor th MZ601?
[Xoom Android Development] notbrodie:
only 4.3 is dreamcwli's aosp build, and there is no 4.4... yet.

Sent from my Nexus 5
[Xoom Android Development] js345:
Once finished the repartioning, can I restore a nandroid made when i had the old partition ?

What i'd like to do is repartitioning and then restoring all my apps and data simply changing the regular EOS for the big part EOS. In this case what will be the easiest way to restore my xoom exactly the way it was, but with big part so i can test the new omni 4.4 and go back to 170 EOS Everest if I need the 3G working?

What would be the easiest way to achieve that?

I don't have the full titanium backup, and restore every app one by one is a pain in the ass.
[Xoom Android Development] matt4321:
Kernel and recovery can't be restored, this will screw things up. Your best way is to restore system and data, then flash the compatible eos kernel from the OP, then make a backup of all that, then you'll be able to restore that without issue when needed
[Xoom Android Development] shpitz461:
I suggest you try Ease Backup, I'm using the free version and it works very well, i always had issues with titanium.
[Xoom Android Development] makakalo:
There's just one command you need to know to backup and restore your app data:

adb backup -all

There are other variations of this command (Google it), but it works with or without root.

Sent from my XT1053
[Xoom Android Development] js345:
Thank you all for the help. I think i'll go matt4321's way since i'm not confortable with adb commands yet.
[Xoom Android Development] bigkris74:
I have a Hong Kong Everest model.

Haven't read the whole thread, is there a step-by-step of what you need from me?

Currently running an EOS 3 ROM.

Cheers.
[Xoom Android Development] logitechor:
Thank you for big Partition. I am now running a smooth version on a android 4.4.2.
[Xoom Android Development] RoryPG:
Thank you!

Thank you for this repartioning guide and all your work. You have paved the way to KitKat. I am now running Schischu's Omni 4.4.2 on my Xoom and it is running without issue, is snappy, Art works well, it over clocks, and "Okay, Google..." works. Perfect. Xoom is back!!!!

Only one odd thing happened to me when following this guide: I got stuck at the Motorola boot screen when I loaded Schischu's ROM, your Wingray EOS 4 boot image and gapps, in that order. I fixed this by changing the order: boot image, ROM, gapps. Not sure why this worked. I then loaded the SuperSU via recovery , not Play Store, to restore root.

Thank you to all of the developers!!!!!
[Xoom Android Development] dkahs23:
When using the Omni ROM you don't need the Wingray EOS 4 boot image. The order should be after partitioning omni ROM, gapps, then reboot the system and set up then reboot to the recovery and flash super su. This is how I did it and everything is working great. I used ttb to restore my apps. Then updated my apps so they would work with KK. So far Excellent.
[Xoom Android Development] dccrens:
WoW! That is great. :) Just wish we could do this for Stingray. :(
[Xoom Android Development] audioblivious:
Seems no one wants to touch stingray for some reason :'(
[Xoom Android Development] matt4321:
It's because RIL is a pain in the arse
[Xoom Android Development] jasonbtx:
Can I flash BigPart rom via fastboot?

Like the question states I have converted file system over to BigPart. But external sd card cannot be accessed. Tried two different cards. Cards can be read on pc as well as on GS3 and on xoom before i flashed TWRP. Tried multiple formats. Any help would be appreciated.
[Xoom Android Development] notbrodie:
Just copy files to internal data. once it boots, sdcard works fine

Sent from my Xoom Wifi
[Xoom Android Development] jasonbtx:
Wont boot cause I cant load the rom cause its on my sdcard that cant be read.
[Xoom Android Development] drewski_1:
How do you have the ROM on the SD Card?

Or do you mean flagging it in TWRP? I have no issues accessing SD card in TWRP
[Xoom Android Development] jasonbtx:
The external sd card. Cant be mounted in twrp. Could this be because its a stingray?
[Xoom Android Development] notbrodie:
adb sideload path/to/rom.zip

Sent from my Nexus 5
[Xoom Android Development] SgtTeabag:
Mounted and installed great on my stingray!
[Xoom Android Development] dkahs23:
Sorry wrong thread.
[Xoom Android Development] chykal:
A Big Thank You!

I just followed the instructions here and in the OmniROM thread and right now both CPU cores are pegged at 1700 MHz while the system is downloading and installing my apps from the play store. This is awesome. I came from CM10.1 for stingray and was happy with that but this with OmniROM is a huge upgrade. I do not have a data plan so I only use WiFi anyway.

Thank you very much for all the work that goes went into developing this mod.
[Xoom Android Development] parkentosh:
Finally got around to trying this mod. Installation is pretty easy and now my system is 1GB. Thank You! This mod with the new omniROM have given my Xoom a second life (or a third or fourth :) )
[Xoom Android Development] aR_ChRiS:
Just wanna ask again whether TWRP is a must or how to make a compatible CWM recovery?
[Xoom Android Development] jasonbtx:
Does TWRP support OTG?
[Xoom Android Development] notbrodie:
bigpart TWRP is required

have you tried it?

on a side note: why do you need otg inside TWRP?

Sent from my Nexus 5