yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] AAccount:
So the xda app messed up my post big time. What I wanted to say was that by using a non selinux kernel, setting the selinux build.prop flag and changing the install script it boots? Yesterday I tried doing the build.prop edit on my cm11 rom and it didn't boot. Very interesting suggestion about the kernel though.

--------------------------------------------Added-----------------------------------------------------------------------

I tried the 3 things you did on my cm11 rom from yesterday:

-Add the ro.boot.selinux=disabled prop (maybe we should try ro.build.selinux=0 as well!)

-I removed all the SELinux patches from the kernel (so essentially go back to the 4.2 kernel). This kernel boot fine on 4.3

-Manually swap the set_metadata lines in the updater script by set_perm lines from a 4.3 script (I compared the two and besides the change from set_prop to set_metadata, the permissions set are the same).

and I can't get past the "samsung galaxy tab 10.1" screen. Note I did these things after the rom was compiled since build.prop can be edited from the update zip and I just flashed an older A1 kernel with no selinux.
[Galaxy Tab 10.1 Android Development] AAccount:
Finally downloaded the omnirom source. A possible cause of this is becasue omni rom has no ICS_AUDIO_BLOB flag in its source at all. You'll probably need to take a working android 4.3 source, do a "grep ICS_AUDIO_BLOB -r ." on the source and find every place in the working source this flag is defined and then transfer it over to omni rom. Yes it sounds like a pain in the butt.
[Galaxy Tab 10.1 Android Development] kasper_h:
Maybe it is easier to swap all OMNI project that contain ICS_AUDIO_BLOB in CM for the CM-code :)

With regard to the kernel, you can't flash a 4.2 kernel on 4.4, as there are ramdisk changes causing it to not boot. I can send you a kernel that will boot on 4.4 that you could try to flash on top of CM11....

I will try a kernel on CM11 and then compare the ramdisk to OMNI to see if that gives a hint why it won't boot...
[Galaxy Tab 10.1 Android Development] AAccount:
What are those ramdisk changes? That would probably help for the rom not booting.
[Galaxy Tab 10.1 Android Development] DemonGloom:
Anyone succeeded with TWRP? I've built latest version from twrp27 branch, but it cannot see any mount points.
[Galaxy Tab 10.1 Android Development] kasper_h:
For me, the recovery image would be the large to fit on recovery partition if I build twrp 2.7 branch...

Did you create the correct fstab for twrp? Has other requirements than the ROM.

Verstuurd van mijn Nexus 5
[Galaxy Tab 10.1 Android Development] DemonGloom:
I've taken fstab from cm-10.1 branch of our device tree.

BTW, in order to fit twrp in 5mb partition you need to:

1) Compile kernel without BT,wifi,ppp,nfs,cifs,gamepads and modules support

2) Convert png's from skin to jpeg's at 50% quality

3) Strip all libraries at recovery/root/sbin before packing cpio.

_______________

Oooops, my mistake. I've taken fstab from p4-common tree and not p5 :(
[Galaxy Tab 10.1 Android Development] Demonic240:
Would this help in allowing you to resize the allocated recovery partition so you can have a larger than 5 MB recovery?

http://xdaforums.com/showthread.php?t=717874
[Galaxy Tab 10.1 Android Development] DemonGloom:
No, that method just tricks kernel about sizes.

TWRP works now. If you point me to correct p4/p4wifi device and kernel trees, I'll build it for your tablets.

*UPDATE*

Latest TWRP cannot install cm11. It says: "error executing updater binary in zip". So we need to build latest CWM and fit it in 5MB.
[Galaxy Tab 10.1 Android Development] martin26765:
did you try using cwm 6.0.3.6 from pershoot?

keep it up guys, good work!:good:
[Galaxy Tab 10.1 Android Development] kasper_h:
CWM can be reduced enough by reducing kernel size & making stich.png black. But for me that didn't show flashing. On sgs, I actually use later twrp successfully, so I think that twrp may be better at the moment.
[Galaxy Tab 10.1 Android Development] DemonGloom:
I have Galaxy Tab 8.9, it's allmost identical, but we have 6.0.2.7 as latest CWM.

I've tried to build CWM from cm-11.0 branch, but it does not boot at all. It is under 5MB, so there is no problem in size. TWRP works with the same kernel.
[Galaxy Tab 10.1 Android Development] DefQoN_BE:
Nope,

http://droidbasement.com/db-blog/?p=3158
[Galaxy Tab 10.1 Android Development] DemonGloom:
Galaxy Tab 8.9, not 10.1. It is P7300/P7310, not P75xx. Board names p5/p5wifi.
[Galaxy Tab 10.1 Android Development] DefQoN_BE:
Oh... I missunderstood you, i didn't say anything then, my bad
[Galaxy Tab 10.1 Android Development] kasper_h:
Same here....won't work.
[Galaxy Tab 10.1 Android Development] scaryshark:
This might be a bit of a long shot but there is a new firmware for the P7500 (3G) model on Sammobile. Perhaps the recovery partition is larger on this one because it's newer?

Also, looks like the dev's over on the Xoom forums have the sam problem but it looks like they have fixed the problem:

http://xdaforums.com/showpost.php?p=47359571&postcount=68

Check out the rest of the thread for more info.

Also, IIRC AAcount, did you not have a mod on your kernel quite a while ago that re-allocated some "empty" space somewhere but had to go back because of some issues. Is that helpful here?
[Galaxy Tab 10.1 Android Development] raystriker:
I don't think so. An update for another region really doesn't count. Nevertheless we can still try .Btw, good work devs. Keep it going
[Galaxy Tab 10.1 Android Development] kasper_h:
Recovery is no longer the problem. Audio is: ICS audio blobs don't work at all and HC blobs are doing a bad job (stuttering). With no comparable devices running KitKat we also can't look at how others solved similar problems. Feels like a dead end for the time being...

Verstuurd van mijn Nexus 5
[Galaxy Tab 10.1 Android Development] kuntau:
I could live without sound on my tab.. any chance for alpha release? Thanks for you hard work :good:
[Galaxy Tab 10.1 Android Development] AnakTeKa:
It can't even past boot animation, I guess
[Galaxy Tab 10.1 Android Development] kuntau:
If you read previous reply kasper manage to reach homescreen.. so there is some hope in that :good::highfive:
[Galaxy Tab 10.1 Android Development] AAccount:
Here's how kasper_h and I managed to do it. Get a comfy chair because this is going to be a long read. First off, you need to download pershoot's latest device, and vendor tress. There will be 3 of them since there's a p4wifi and p4-common. Once you're done that you need to look through the commit log for all 3 of those and look for one commit that mentions adding in kernel 3.1 changes. Look at the commit just under that one and click on "browse code" for the commit under it to get a copy of the 3 folders at a previous point in time. That's your ticket to audio sorta working. Oh yeah, make sure you're on OMNIRom because cyanogenmod's surfaceflinger isn't working right. It never has for me and OMNIRom is made by former cyanogenmod members whose core philosophy is more in line with the custom rom spirit.

Now look at your p4-common tree. You'll need to copy in the libaudio folder from the honeycomb one and remove the audio folder. This provides half open source drivers for the audio. Then, going back to the commit look at how pershoot edited p4-common.mk to remove the lines for audio.primary.p3 and audio_policy.p3. Add them back in. Also, add back in the lines that pershoot removed mentioning libaudio and liba2dp. You'll want to add those back in as well. Last step: you'll need to edit board config common and remove the -DICS_AUDIO_BLOB line. It's no longer needed with this half open half closed source driver.

Next you'll need to look into the device p4wifi folder. The only thing that needs to edited here is the setup-makefiles.sh Undo the commit lines that removed PRODUCT_COPY_FILES:\\ ...libaudio.so and libaudiopolicy.so.

And lastly, the p4wifi vendor folder. For this folder I took a rather dirty approach and put in the old honeycomb parts as well as kept in the new ics parts that don't conflict. Also for this folder, there is no clear commit that shows the changes from the 2.6 kernel to the 3.1 kernel. You'll have to make an approximate guess on this one. The p4wifi-vendor-blobs.mk has to be changed so that libaudio and libaudiopolicy and liba2dp are put back. In addition, the new files lib/hw/tegra**.so files need to be removed. I copied in all the etc/audio/Tx* Rx* files. That folder is a dirty copy since there are some files in there from the ics blobs that aren't effected. Lastly, don't forget to copy in those 3 files: libaudio, libaudiopolicy and liba2dp back in and remove the new ones /lib/hw/audio**tegra.so

A few more things before you're ready. Get a copy of nova launcher and use root on your phone to extract it. You'll need to adb install it since launcher3 doesn't work. Oh, and to make wifi work, look at this S3 I9300 commit paying special attention to the init.rc file. Make the same changes to wpa_supplicant and p2p_supplicant or you will have no wifi.

Be warned, getting it to boot is the easier part. Fixing the sound, random reboot, gps, camera are the hard parts and is impossible for me. The instructions I just wrote out may sound somewhat trivial but they're actually the result of 2 weeks worth of hard trial and error involving almost all error.

Have fun with that :cyclops:
[Galaxy Tab 10.1 Android Development] mrvtec69:
heres a new commit got PRE kitkat audio blobs, maybe it can help

https://gerrit.omnirom.org/#/c/2463/
[Galaxy Tab 10.1 Android Development] kasper_h:
I already tried that one as well...
[Galaxy Tab 10.1 Android Development] tonyp:
If you want to make the compiled ROM compatible to older recoveries you can do so by picking this:

http://review.cyanogenmod.org/#/c/53559/

Then add USE_SET_METADATA := false into your BoardConfig.
[Galaxy Tab 10.1 Android Development] AAccount:
Thanks for the pointer. Actually, since kasper_h and I disable selinux, kasper_h discovered you can manually hand swap all the metadata lines for set_perm from an android 4.3 rom and that's what we've been doing so far. Have you made progress on your android 4.4 rom? Do you get random reboots to or is your gps or camera working?

On another note, I tried flashing omni4.4 on my i9300 and it has the same flac stuttering problem so it turns out I did get audio working 100% on the p4wifi. The flac stuttering is an android problem.
[Galaxy Tab 10.1 Android Development] tonyp:
Yes, by using the flag I posted above you won't have to replace the lines manually anymore :)

I didn't yet spent much time into the 4.4 bringup, the one CM11 ROM I compiled didn't make it to the bootanimation (someone else who made it fully boot before experienced the same problem, so something changed in the sources, possibly egl related).

For the camera you'll probably need quite some hacks in frameworks/av - this has already been a pita for my 4.3 ROM.

Damn this Tegra2 ...
[Galaxy Tab 10.1 Android Development] AAccount:
Never mind, it was only a temporary fix. Later on I couldn't open any email app soon followed by chrome not being able to open. I'm back on CM10.2: 4.3.1.

Would this change help? I'm currently building omni rom because the surfaceflinger of cm11 would never work for me. I checked my cm10.2 sources and it is there.
[Galaxy Tab 10.1 Android Development] kasper_h:
Great report. The apps you mention all depend on webview. CM merged some improvements for that last week. Also, some patches for frameworks_native are under review for older devices. So I decided to try cm building this weekend.

Verstuurd van mijn GT-I9000
[Galaxy Tab 10.1 Android Development] Demonic240:
Just watching this thread makes me all giddy inside. Keep up the good work gents :)
[Galaxy Tab 10.1 Android Development] sarge.bastards:
Yes, I really hope this work out! Keep up the good work :)
[Galaxy Tab 10.1 Android Development] John Kester:
Hi Kasper, how did the build go last weekend? Any good news yet?

Thanks for all your effort.

Cheers.
[Galaxy Tab 10.1 Android Development] kasper_h:
It is getting better, last build was stable. Only big problem left was Wi-Fi, but got some hints from aaccount for that one, so the struggle continues. Besides WiFi, there will probably more issues, but at least it is now compiling and booting without issues.

Verstuurd van mijn Nexus 5
[Galaxy Tab 10.1 Android Development] drashran:
Thanks a lot for trying to port 4.4 to our tab, Please keep us posted about the latest development in 4.4
[Galaxy Tab 10.1 Android Development] rtoussaint:
let me know if you need a 'proefkonijn' :D

(guinea pig)
[Galaxy Tab 10.1 Android Development] BeeGee_Tokyo:
Hello Kasper,

Can you share with me your current device and vendor trees? Maybe I can help as well a little bit.
[Galaxy Tab 10.1 Android Development] kasper_h:
https://github.com/InfamousAOKP/android_device_samsung_p4-common

https://github.com/InfamousAOKP/android_device_samsung_p4wifi

https://github.com/InfamousAOKP/android_vendor_samsung_p4wifi

This is for building OMNI.

Launcher3 doesn't work in omni, so I replaced it with CM one.

Other than that, it just compiles & boot straight away

Sound works good (with HC partly open-source blobs)

Wifi works fine

Everything video related (Camera, Movies) does not work

Frequent soft reboots.

CM compiles fine as well, but won't boot (screen goes blank after kernel splash, haven't been able to get any image - I once had a CM bootanimation when replacing all surfaceflinger files from OMNI -> CM).
[Galaxy Tab 10.1 Android Development] DefQoN_BE:
Could you make it a flashable zip so we can contribute to your ROM?
[Galaxy Tab 10.1 Android Development] pershoot:
hi all.

keep the galaxy tab 10.1 t2 dream alive:)

-pershoot
[Galaxy Tab 10.1 Android Development] kasper_h:
I don't know whether the t2 is the best follow-up, but let's not get into that discussion :p

I have discussed with AAccount a lot in the past weeks to see whether we could solve the issues. It seems the problem won't be solvable :( We tried so many different angles. But it never resulted in a functional 4.4 build. CM won't boot due to surfaceflinger issues. Omni boots, but is unstable (many soft reboots) and video&camera won't work.

Unless someone else comes along with a brilliant idea, I am staying behind on JB4.3.
[Galaxy Tab 10.1 Android Development] SystemDoctor:
Well that's bad news for the ones who want the KitKat experience. I hope someone has a solution to this.
[Galaxy Tab 10.1 Android Development] kasper_h:
I will keep on trying every now-and-then. But I have already spent a huge amount of time on it without any success, so I don't want people to keep their hopes high ;)
[Galaxy Tab 10.1 Android Development] AnakTeKa:
Have you try to contract pershoot?
[Galaxy Tab 10.1 Android Development] BeeGee_Tokyo:
You used branch "infamous-kk" I guess?

I build the omni ROM for Galaxy S3 with success after I changed the vendor blobs. First I was trying to go with the 4.3 blobs, but it didn't work well. I will give the 7500 tab a try this weekend. Thanks for the links to the repositories you used.

One more question, which recovery did you use? On the S3 I could get the ROM flashed only with the real latest TWRP recovery. Any advice is appreciated.

And another one: which kernel did you use?
[Galaxy Tab 10.1 Android Development] kasper_h:
Yes, infamous-kk branch

I used an old TWRP recovery. An updated one is always 5+MB and will therefore not fit on our tiny recovery partition. I enabled the SKIP_SET_METADATA flag to make sure the updater-script is compatible with our old recovery.

I use my JB4.2 kernel.

I am actually doing one last try with some of the things reverted: omni has started adding ICS_AUDIO_BLOB flags, so maybe our ICS audio blobs work and we don't have to go back to the HC ones.
[Galaxy Tab 10.1 Android Development] nokia-xxx:
CM11 nightlies are officially since dec7... Hopefully that is helpfull for this "project".

It would be great to have Kitkat on ourdevices!

Thanks for all your effort.....
[Galaxy Tab 10.1 Android Development] kasper_h:
Does not make a difference, the problem is device-specific. Google decided to stop supporting tegra2 after JB4.2. So that we can run JB4.3 is already a step further than expected. But KK is just a leap to far.
[Galaxy Tab 10.1 Android Development] Backe888:
So you say we wont see 4.4 on the P7500/P7510?
[Galaxy Tab 10.1 Android Development] DefQoN_BE:
He didn't say we'll never see android 4.4 on our tabs, he said that we shouldn't keep our hopes too high..
[Galaxy Tab 10.1 Android Development] AAccount:
I figured I try this again and I think I've got something for the soft reboot. It's not a perfect solution but at the cost of a split second flicker where a soft reboot would be I think it's acceptable. Check out surfaceflinger.cpp and add these ifndefs where I have:

#ifndef BOARD_EGL_NEEDS_LEGACY_FB
if (useReadPixels)
{
sp<GraphicBuffer> buf = static_cast<GraphicBuffer*>(buffer);
void* vaddr;
if (buf->lock(GRALLOC_USAGE_SW_WRITE_OFTEN, &vaddr) == NO_ERROR) {
getRenderEngine().readPixels(0, 0, buffer->stride, reqHeight, (uint32_t *)vaddr);
buf->unlock();
}
}
#endif

As you may know, I figured out from the logcat that a graphics buffer lock is the cause of this but couldn't figure out where it's called from so I tried to kill the function all together which backfired. Now, I think I may have found it. As you can see, if the graphics buffer lock isn't successful it isn't unlocked which means you have a permalock. I'm guessing this is bad and the cause of the backfire. Now I'm getting straight to the source and killing any "funny business".

virtual bool handler() {
Mutex::Autolock _l(flinger->mStateLock);
sp<const DisplayDevice> hw(flinger->getDisplayDevice(display));
#ifndef BOARD_EGL_NEEDS_LEGACY_FB
bool useReadPixels = this->useReadPixels && !flinger->mGpuToCpuSupported;
result = flinger->captureScreenImplLocked(hw,
producer, reqWidth, reqHeight, minLayerZ, maxLayerZ,
useReadPixels);
#endif
static_cast<GraphicProducerWrapper*>(producer->asBinder().get())->exit(result);
return true;
}

I needed this one to compile cm10.2. It dropped out of the omni code at some point in the last few weeks I wasn't playing with it.

So in summary here's what's working on my omni 4.4.1 tablet:

-wifi

-bluetooth

-youtube standard def (Tried card games ftw episodes. They're hilarious.)

-sound

-not randomly rebooting

-usb host keyboard and mouse

-usb tethering of wifi (needed to get internet on my pentium 4)

-gps (seems to have fixed itself)

Not working

-camera

-youtube hidef (tried big buck bunny)

PLEASE DON'T EXPECT A ROM ANY TIME SOON THOUGH. Personally, I hate broken expectations so I'm trying to prevent it because that feeling of not getting something you're really expecting sucks.
[Galaxy Tab 10.1 Android Development] nort1973:
:) This is great news. For me the camera and also gps are no needs working on my tablet (It's always the same with the fu.... g proprietary drivers of the manufacturers :mad: ).

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy Tab 10.1 Android Development] Ackoman:
Likewise - I can totally live without camera and gps, and even HD youtube. If you need someone to try out what you've achieved so far, then I'd be happy to help out :)
[Galaxy Tab 10.1 Android Development] Benzoman:
As always willing to test and report issues using my 7510 that is just sitting idle.
[Galaxy Tab 10.1 Android Development] info.brandenburg:
Congratulations!

It would be really nice to see 4.4 on our tablets.

Camera and GPS are nice, but they are not necessary on a tablet.

Thank you for all the work up to this point.
[Galaxy Tab 10.1 Android Development] TheOrangeRemix:
Even if HD YouTube isn't working on the Tab with this ROM so far, I wonder if you can still get HD YouTube via Chromecast?
[Galaxy Tab 10.1 Android Development] AAccount:
GPS fixed itself. I got the galaxy s3 exfat kernel modules to compile. Kasper_h got zram in the performance control. Also flac stuttering is no longer a problem. Screenshots are disabled because of a 4.3 bug but that means the 2 bar ui is lag free.
[Galaxy Tab 10.1 Android Development] jaibar:
If this is far enough to produce a test build, I'm willing to flash it :)
[Galaxy Tab 10.1 Android Development] AAccount:
I don't like handing out "secret" test builds for selected individuals only. The reason for this has to do with my personality. I don't like begging my way into things (whether that be a group of friends, getting reference letters etc...). I have seen some xda threads where developers hand out special betas to a few select individuals and occasionally it would be for modifications I use. While I'd like the newest modification/version for psychological satisfaction, it somewhat irritated me that I had to be "special" "selected" to test it.

It's only been since Monday night that I got the random reboot fixed so I'd like to work on it a bit more before making any moves. Actually, kasper_h and I are hard at work tinkering and since we both compile our own builds, it makes testing and fixing easy. We can look through the sources and point out fixes to each other.

Time will tell how good KitKat is on this tablet.

Oh and while I'm on it, it's rather off topic, but I HATE the whole reference letter thing. It's an exercise in who can kiss up to someone else best. Those g** d**n f***** reference letters!!!! What I wouldn't do to have Yu-Gi-Oh mind crush capabilities on someone who tells me: "Oh, you want to apply for _____, you need ____ references to go with that application".
[Galaxy Tab 10.1 Android Development] Sik-1:
Even with your test builds , I'm wondering how does it feel, lol very exciting indeed
[Galaxy Tab 10.1 Android Development] kasper_h:
I totally agree with AAccount in this one. It is still getting better every day and the list of unsolvable bugs gets smaller. It will be released IF and WHEN it is a ready :) This may also depend on the availability of features from Omni ROM upstream: also from that side it is not a full-features ROM yet.

Anyway, since the solutions of early this week, I finally am running 4.4 as a daily ROM. Even for me, it was too unstable as a daily driver until then :) It runs very smooth, but still has some glitches.

And for people that are very curious, the device trees, vendor tree & frameworks/native tree that I used to compile yesterdays build are updated on github. I am also testing some additional features, that can be found in my frameworks/base-1, packages/apps/OmniGears & Settings-1, and PerformanceControl projects on github. So for those able to build -> you can make it yourself and maybe even contribute to the effort!
[Galaxy Tab 10.1 Android Development] jaibar:
oh, I wasn't thinking about secret under the table build- looks like there are enough crack flashers willing to test an early pre-alpha build, not minding that lots of stuff not fully functional yet. I don't mind if it helps debugging, producing some logcats.

But, waiting patiently is just as fine, I'm very grateful that you guys are working on this old tegra device and keeping it alive. Many thanks!
[Galaxy Tab 10.1 Android Development] jolobe:
+1! !:good:
[Galaxy Tab 10.1 Android Development] Nash123:
Great news :)
[Galaxy Tab 10.1 Android Development] AAccount:
One thing I discussed with kasper_h is that we're not going to support the 3G version. Specifically I mean we won't be trying to get the ril to work. Both of us have wifi only tablets. Since android 4.3-->4.4 is a big change, we have seen there are no guarantees (except bluetooth) that anything that worked in 4.3 will work in 4.4.

For me at least, I simply don't have the skills to look at a logcat and fix the problem in a few attempts. It took several grep commands, careful reading, and a lot of trial and error to find the random reboot fix. Because of this, it's probably not possible and certainly not practical for me to look at the ril. Even if I could just solder in the modem, I only have 1 sim card that's my only telephone line so I wouldn't take it offline to experiment anyways.

If the p7500 is just your secondary tablet with no active data plan you could just go for the wifi rom at some point. My p7510 is my only tablet so that's why I'm working on it.