yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] VertigoInc:
So I finally got around to rooting the galaxy 10.1 (GT-7500) tab.

Following the guide by Jiia.

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

(all went well)

Then I decided to flash this rom.

Upgraded to twrp2870-20150814-p4.zip supplied in this guide.

Downloaded and installed:

aosp-5.1.1-p4-20150814.zip

p75xx-gapps-L-7-17-15.zip

UPDATE-SuperSU-v2.46.zip

So far all well.

Tab rebooting and everything is smooth.

I register I need additional steps to get 3g to work, so I download:

CWM_I9103XXLQ3_Modem.zip

and

Voice_Call_Enable__AOKP__ICS_4.0.4_ROM_Build_1.zip

However, once installed the tab enters a bootloop.

After finishing a clean reinstall of

aosp-5.1.1-p4-20150814.zip

p75xx-gapps-L-7-17-15.zip

UPDATE-SuperSU-v2.46.zip

I try to install only the CWM_I9103XXLQ3_Modem.zip

With only that extra install the tab reboots just fine, but still no 3g.

(Will not detect sim)

I find a post by sherpya:

xdaforums.com/showpost.php?p=62368653&postcount=1572

After downlading the supplied p4-20150814-radiofix.zip 3g works.

So I'm pretty much up and running as far as I can see.

However, I do wonder if anyone can see what I did wrong, or if anyone also experienced the bootloop after installing the Voice_Call_Enable__AOKP__ICS_4.0.4_ROM_Build_1.zip

Or did I pick the wrong file, and should have used any of the other files?

(I don't have a dock, so I skipped the p75xx-ICS_AudioHAL-AOSP_5.1.0-20150311.zip)

Finally I have not enabled SELinux enforcing mode, as I'm not sure why I should yet.

I know it will harden the install, but as I probably will update or try a few more roms as time permits before settling on one, it probably isn't the end of the world to leave it out?

Thanks for the great work everyone, nice to find most of the info in one place ^^
[Galaxy Tab 10.1 Android Development] sherpya:
If you use Voice_Call_Enable__AOKP__ICS_4.0.4_ROM_Build_1.zip you'll sure screw the rom since it's for another rom, to enable voice calls you only need to flash the modem. Then you need my radiofix zip because latest rom does not have radio userland
[Galaxy Tab 10.1 Android Development] VertigoInc:
haha, I see it now x)

I was to tired to notice at 4 in the night.

Looking at the formatting in this original post I somehow thought I needed 2 files from that link.

(Modem file, and a Enable file)

when I looked at the install instructions

( http://xdaforums.com/showthread.php?t=1875024 )

I noticed links to samsung stock and CyanogenMod that I didn't need, and somehow read AOKP as AOSP...

x)

Ah well, mystery solved :)
[Galaxy Tab 10.1 Android Development] God_King_Nation:
Anyone have an idea of how to solve the problem at the top of this page? :confused:
[Galaxy Tab 10.1 Android Development] Kaherdin:
I have had issues before with Wi-Fi networks that my device wasn't able to connect or see. My issue then could often be resolved with Airplane mode on/off or a reboot.

There are certain Wi-Fi types that require certain radio protocols. You might just have one missing, and I'm sorry, I don't know how-to fix those types of issues.

I would flash any and all radio builds I could find

Skickat från min LG-D802 via Tapatalk
[Galaxy Tab 10.1 Android Development] God_King_Nation:
Alright, it works now, but I have no idea how.

I tried adding the network once more but now I went to advanced settings and I enabled, then disabled the proxy.

And that's it... somehow... but thanks for your help [MENTION=2304118]Kaherdin[/MENTION]
[Galaxy Tab 10.1 Android Development] cogitooo:
thanks for great rom.

I have 2 questions, sorry if asked before;

- Is keyboard dock still not working? I m using june build.

- How about usb otg is it working?

thanks again
[Galaxy Tab 10.1 Android Development] swannema:
A big thank you for this rom and thread with a lot of valuable informations. It works beautifully on my device. Took awhile to get the 3G going but with the radiofix file I got it running.
[Galaxy Tab 10.1 Android Development] sflesch:
Keyboard dock is not, however it sounds like someone got it working in an earlier (somewhat recent) thread.

I've noticed it's kind of quiet lately. Have people been giving up on this device?
[Galaxy Tab 10.1 Android Development] alburke47:
I'm still using it. Haven't had any issues, so I didn't feel the urge to post. I'm very happy to be still using a 3 year old tablet with lollipop on it. Thanks Dev!
[Galaxy Tab 10.1 Android Development] jaibar:
Same here. I guess no news is good news.
[Galaxy Tab 10.1 Android Development] yitzi:
I'm still using the rom it's great to have lollipop on this device thanks so much
[Galaxy Tab 10.1 Android Development] sherri:
Mine still has Kitkat, but it runs flawlessly!
[Galaxy Tab 10.1 Android Development] Raceit:
This ROM was the sole reason I bought a replacement digitizer and display since my screen was shattered. Looks great now, but does anybody else get an additional search bar when in portrait mode? The top one I can't get rid of - the bottom one is the one that is used when in landscape and is the actual widget.
[Galaxy Tab 10.1 Android Development] fz798:
Not sure about the extra search bar, but love that wallpaper. Can you post it?
[Galaxy Tab 10.1 Android Development] Raceit:
It's a 20MB file. Enjoy! :)

http://i.imgur.com/c5SGlUX.jpg
[Galaxy Tab 10.1 Android Development] L3R0N:
Seems like you're using Nova Launcher. The search bar at the top is the persistent search bar which you can disable in nova launcher settings. The second one below is a widget and can be removed by long pressing on it and dragging it to the x that should appear at the top of the screen. Awesome wallpaper tho:good:
[Galaxy Tab 10.1 Android Development] iambaba:
installed this rom but im having issues with 3G
[Galaxy Tab 10.1 Android Development] Just_Another_N00b:
Please read posts in this thread on this subject. You should be able to find the solution in the last 20-30 posts.
[Galaxy Tab 10.1 Android Development] nencho:
Hi, I have a problem with Skype, starting to dial on and off. Anyone know a solution,It is constantly being thrown?
[Galaxy Tab 10.1 Android Development] iambaba:
still havent seen the fix, the supposed file on page 123 is deleted
[Galaxy Tab 10.1 Android Development] nencho:
p75xx-ICS-AudioHAL-20150110.zip The file is removed, can someone post it new.
[Galaxy Tab 10.1 Android Development] spamam1:
Hello,

I don't have the Jan 10 version, but have the Apr 23 version;

both are 2015.

Not sure if this 'breaks' stuff that works in Jan 10 version, though;

and it's not listed in the OP.. but I'm pretty sure I downloaded

from this thread.

Anyway, have a look. Hope it helps.
[Galaxy Tab 10.1 Android Development] sflesch:
How are you making out on this? Any chance you can work this in [MENTION=4404851]decatf[/MENTION] ?
[Galaxy Tab 10.1 Android Development] nencho:
Thank you, thank you, thank you very much, directly saved my life :)

---------- Post added at 09:53 PM ---------- Previous post was at 09:53 PM ----------

Thank you, thank you, thank you very much, directly saved my life :)
[Galaxy Tab 10.1 Android Development] fz798:
+1 for eagerly awaiting any update on the keyboard dock, thanks much for all you do.
[Galaxy Tab 10.1 Android Development] FCKöln:
I guess decatf is busy otherwise he would have responded. You can try the keyboard stuff out on your own if you like. It's not that hard to setup. You only need to download the sec_keyboard from here,

copy it to /system/bin/ and start it with "/system/bin/sec_keyboard /dev/ttyS0 &" from an adb console. Instead of the console you can also use an app called "kernel adiutor" from the playstore. It has an init.d emulation. Additionally the keyboard layout file needs to be tweaked because not all keys are recognized.

In my tests so far it happened once that sec_keyboard was consuming 100% cpu time and i had to reboot the tab.
[Galaxy Tab 10.1 Android Development] FCKöln:
I was also trying to compile Euphoria OS for p4wifi just to test some recent Android build with minor modifications to see if there are any keyboard related changes. I can boot this build as secondary ROM and it has a lot of issues but the keyboard is working out of the box without any additional sec_keyboard binary. This is what i can tell so far...

(no idea why i had to split my message in two posts... seems like there is a limited message size!?)
[Galaxy Tab 10.1 Android Development] decatf:
I uploaded a new build with the October security updates.

Not much else changed

- A few kernel things

- Switched the compiler back to the stock Android GCC 4.8 because the Sabermod toolchain was causing some weird crash with Youtube.

I did not try to address the 3G issue in this build. I guess something broke in the last build when I used an older revision of the Omnirom telephony framework. Omnirom merged a different branch of the AOSP code into their repo so it not compatible with the most recent stock AOSP without following their merges in other repos resulting in a big mess.

I don't know what the deal is with the sec_keyboard binary. I have noticed it before but it was removed a long time ago so I figured it wasn't relevant anymore. That application seems to read from /dev/ttyS0 in an infinite loop so it could be why it uses up CPU and prevents the device from sleep.

[MENTION=2398752]FCKöln[/MENTION]: Which device (android_device_samsung_p4-common) and kernel repo did you use to build the ROM?
[Galaxy Tab 10.1 Android Development] rtiangha:
No more support for the p4tmo (missing baseband notwithstanding)? Is it possible to flash the p4 or p4wifi roms on this thing? I tried both after a clean wipe, but neither would boot past the Samsung logo. On the bright side, I can confirm that USB-OTG works great in the latest version of TWRP as I was able to backup/restore my Aug 14 p4tmo nandroid multiple times.
[Galaxy Tab 10.1 Android Development] mistersixt:
Thanks a lot decatf for still supporting our "old" device, I use still use it on a daily basis (like a lot of other people as far as one can read here @ XDA) and it is working mostly without any flaws! Please keep updating it from time to time ;) !

kind regards, mistersixt.

PS: I assume bringing Android-6 to our device won't happen, or what do you think?
[Galaxy Tab 10.1 Android Development] grej:
Release notes for 20151012 builds

[MENTION=4404851]decatf[/MENTION], Could You update changelog, there is no release notes for 20151012 builds.
[Galaxy Tab 10.1 Android Development] decatf:
I ran super low on disk space since pulling the Android 6.0 repos so I only did the two most used devices. I figured I would try to work something out for baseband thing first before properly doing all the ROMs for cellular tablets.

Don't expect anything.

Google made a lot of fundamental changes to the underlying parts of Android and they dropped support for the Nexus 7 2012. Why is the Nexus 7 2012 relevant to this device? Both devices are from the same generation and based on the same Nvidia Tegra Linux 3.1 kernel. As long as Google had been supporting the Nexus 7 2012 this device could benefit too. Now that they've ended support there is no guarantee that anything will remain compatible.

I've tried Android 6.0 on this device and it will not work. There are some weird problems which are beyond the scope of my knowledge. I won't comment much more on it since it would be pure guessing and I don't want people to read it and get wrong information based on that.

So right now I have nothing to go on and the outlook isn't good.

The changes can be seen on my github page. https://github.com/Decatf?tab=activity
[Galaxy Tab 10.1 Android Development] rtiangha:
That's too bad. In the meantime, is it just a matter of the wrong kernel preventing this thing from booting? Like, would it be possible to flash the p4 rom on this thing, and then the tmo kernel on top of that? Or is there more to it?

Also, I'm willing to set up a build environment on my own to play around with this, but the only rom I've ever compiled is CM for the Nexus 7 2012 (which is essentially download the source and compile with no modifications). I've never done anything custom, so to compile your tmo version, is it just a matter of downloading the latest 5.1 AOSP source and then overwriting the various files with versions from your github and then compiling normally, or is there more to it? It's a newb question, I know, but I figure once I figure out how to build proper working roms for this thing, then I can be of more assistance with things so I may as well start learning now.

Edit: Which 5.1 AOSP branch should I start off with? One of the Nexus 7 branches (r19 or r20) or does it really matter (if not, then r24)?
[Galaxy Tab 10.1 Android Development] Mjoelnir77:
Did anyone try already whether this still works with the current build to get 3g working?
[Galaxy Tab 10.1 Android Development] decatf:
Please test the 3G on this build.

aosp-5.1.1-p4-20151013.zip
[Galaxy Tab 10.1 Android Development] Kaherdin:
These discussions are a proof of the hypothesis that OEMs just don't WANT to make their devices to live longer than 12 months.

You, the people with the knowledge to develop, impress me greatly! Keep it up as long as you find it fun!

Peace

From my D802
[Galaxy Tab 10.1 Android Development] jaibar:
It is not really a proof, but it is probably common knowledge anyway.

I think the people here who maintain this ancient device are just a minority. Probably have newer tablet too, keeping this one alive maybe to let kids play, or just for fun?

Don't forget that lots of people actually want to replace their device with a shiny new one every once in a while.

In the past, when cellphones were ridiculously expensive, people stuck with them longer. When pieces started drifting down towards the 500$ mark, it seems that people feel better upgrading/changing more often. Cell providers encourage you to "upgrade" phone just to get hold of customers for longer periods.

It is a classic situation where the customers want to be fed, and the manufacturers are willing to oblige...
[Galaxy Tab 10.1 Android Development] donjuan10:
I've tried but 3G still doesn't work, simcard is not detected
[Galaxy Tab 10.1 Android Development] rtiangha:
I'm curious, when you go to Settings>About, does it say "unknown" under Baseband version? It does on mine, but it's a p4tmo.
[Galaxy Tab 10.1 Android Development] FCKöln:
I have used your kernel and device repositories from github to build "github.com/Euphoria-OS-Legacy"

<project name="Decatf/android_device_samsung_p4-common" path="device/samsung/p4-common" remote="github" revision="aosp-5.1.0" />
<project name="Decatf/android_device_samsung_p4wifi" path="device/samsung/p4wifi" remote="github" revision="cm-11.0" />
<project name="Decatf/android_kernel_samsung_p4" path="kernel/samsung/p4" remote="github" revision="aosp-lollipop-stable" />
<project name="Decatf/android_vendor_samsung_p4wifi" path="vendor/samsung/p4wifi" remote="github" revision="aosp-5.1" />

Some additional changes i had to do

change TARGET_CPU_VARIANT to tegra2 in p4-common/BoardConfigCommon.mk otherwise update-binary does not work
sepolicy adjustments in p4-common because of duplicates
bionic needs tegra2 addons in libc -> taken from decatf
delete libjni_latinimegoogle.so in/system/lib otherwise keyboard crashes over and over again (from /vendor/eos/prebuilt, because of NEON instructions)

I have not used any of the other projects you have branched and modified to make it p4 compatible (native, av, system, base, bionic ... and more?) because i wanted to start from scratch. I'm still in the process of learning and understanding the Android structure and projects and I didn't really understand what modifications were required in each of these projects to make p4 working. Any chance to give me a short summary? :)
[Galaxy Tab 10.1 Android Development] decatf:
The proprietary libraries for this device are from Android 4.0.4. Android has gone through several API changes since then. So most of the modifications are so that the Android API is compatible with the old libraries.

- bionic is Androids standard C library implementation. If the ROM boots then you probably have most or all of the necessary things for that.

- Most if not all of the modifications for graphics and video compatibility are in frameworks/native and frameworks/av

- There is nothing in frameworks/base that is absolutely necessary. That is the upper layer stuff like the UI, AppOps, and other bells and whistles.

- I have not made any keyboard specific changes in the frameworks.

What issues are remaining with your ROM?
[Galaxy Tab 10.1 Android Development] donjuan10:
Yap, same with me
[Galaxy Tab 10.1 Android Development] FCKöln:
Thanks for the explantation. I didn't test everything deeply to give an exact overview of what is not working but so far i can tell that

- Wifi works

- Bluetooth discovery works (didn't test connectivity, file transfers and so one)

- Audio doesn't work at all

- Lot of selinux issues. Causes apps like playstore to crash until i execute "su setenforce 0" from the command line

- Not sure if GPS is actually working. Google Maps finds my exact position but i am getting a lot of "[gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)" messages

- Google Maps crashes when switching from Maps to another app and switching back to Maps. Seems to be OpenGL related "NvRmChannelSubmit failed (err = 196623, SyncPointValue = 0)" and "java.lang.IllegalStateException: Unable to get uMVPMatrix handle on program 0"

- Camera app crashes immediately

- Video decoding/playback of a simple xvid avi seems to work. (Tested using archos video player)

- Internal memory/sdcard can not be mounted. Might be selinux related...
[Galaxy Tab 10.1 Android Development] Mjoelnir77:
this=using the radiofix zip

OK, upgraded now my girlfriends tab with a clean install coming from nameless (kitkat, build one year old). It does work, but the whole story was a bit cumbersome. I am now on the October build, but also with earlier builds i got some problems with aosp keyboard on all of them (did not show and hat entry "rebooting" in the apps list - no clue why). Anyway, i pushed Hackers keyboard to the tab and then manually entered an APN (list was empty) and then i had a working 3g connection again.

So far all looks stable (except the aosp keyboard, but i prefer a different one anyway), 3g is there and so all should be fine. Thanks a lot, decatf! And also thanks to all the others for the hints on how to get the stuff running.
[Galaxy Tab 10.1 Android Development] Raceit:
On 5.1 is there any way to swap the recent tasks and back soft buttons? I'm ruined by Samsung devices. Lol
[Galaxy Tab 10.1 Android Development] Lucas Kado:
You can try this Xposed module, probably GravityBox can also do the job...
[Galaxy Tab 10.1 Android Development] daneal2u:
[MENTION=4404851]decatf[/MENTION] android m is out for nexus 7 2012 . Now is there chance that we might get marshmallow?
[Galaxy Tab 10.1 Android Development] batusaibrito:
Hello, I just installed this ROM, and everysing went well, but there is one problem, when I get in some menu, for exemple "definitions" I can´t get back. I don´t have the back;home; menu control :(

I don´t have the status information bar, on top too :(

Can you please help me ?

Best regards
[Galaxy Tab 10.1 Android Development] decatf:
Don't forget to add the audio wrapper to your manifest. https://github.com/Decatf/android-audio-wrapper

It's probably better to build the kernel without SELinux and get everything working then resolve the SELinux problems.

The Google Maps problem happens on this ROM too. The only way it might be fixed is if it was due to some change in the code that we have. The best way to tell would be to determine when the problem started happening and test if a previous build has the same problem but I don't know when the problem started. It's possible it is due to some incompatibility in the proprietary binaries. In that case there is nothing that can be done to fix it.

No.

They came up with a way to get the NVidia binaries working but there is a more serious issue that is preventing M for this device. ART does not work. I cannot debug any further because I don't know enough about the Android Runtime. At the moment my efforts are no better than randomly poking around in the dark.

The worst case is if it is some problem specific to this device then there is no chance of a Marshmallow ROM from me. If there are some other devices that have this problem then maybe that will bring the attention of someone who might be able figure out what is going on. So far I have not seen any other device that has this issue. So at the moment it's looking like this is some weird device specific issue.
[Galaxy Tab 10.1 Android Development] Technical:
Sadly, but we need to face that the device went very far due to your (and others) efforts.

Maybe Omni team (or devs) could manage that.

Thanks for all your efforts :good:
[Galaxy Tab 10.1 Android Development] daneal2u:
thanks for replying

will u still keep providing us with lollipop updates?
[Galaxy Tab 10.1 Android Development] Raceit:
Awesome! That did the trick. For anyone else that wants to swap the Right and Recents soft buttons, I installed the Xposed framework from here followed by the apk.

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

Then installed the GravityBox.

http://repo.xposed.info/module/com.ceco.lollipop.gravitybox
[Galaxy Tab 10.1 Android Development] Mjoelnir77:
[MENTION=4404851]decatf[/MENTION]

Would it be possible to add support for com.google.android.webview in the ROM?
[Galaxy Tab 10.1 Android Development] FCKöln:
Disabling selinux at boot (androidboot.selinux=disabled enforcing=0 in kernel config) fixed both, the playstore crash and internal flash not being mounted. By adding the audio wrapper and REFBASE_JB_MR1_COMPAT_SYMBOLS to p4-common/BoardConfigCommon.mk audio started to work too :) GPS was fixed by adding a non-PIE executables related patch to bionic linker/linker.cpp (see commit d81b3b275dff99561cbe5905ca63a1c72fa54a17)

So, all in all there was not that much required to make it work. Of course, there is stuff like camera missing and probably some other issues too but it is not that bad :) Thanks a lot.
[Galaxy Tab 10.1 Android Development] Kaherdin:
Thank you for your dedication during these years with my first and only tab!

Impressive work. If this is the end up updates I wouldn't be too upset - you kept it going longer than the oem!

Best of luck with all your future endeavors!

From my D802
[Galaxy Tab 10.1 Android Development] dietoro:
I do NOT get wich version May I install on this:

GT-P7500 XXLQ8

Model N° GT-P7500

Android version 4.0.4

Baseband version P7500XXLQ8

Build n° IMM76D.XXLQ8

Which is the difference between p4Wifi , p4 and p4tmo ??
[Galaxy Tab 10.1 Android Development] Johnny camaro:
Download this app

https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo

And it wil show your device info:thumbup:
[Galaxy Tab 10.1 Android Development] LiverpoolFCfan:
p4 - GT-P7500 - is the original Samsung TAB that had both 3G and wi-fi connectivity

p4wifi - GT-P7510 - is the original Samsung TAB that had ONLY wi-fi connectivity

p4tmo - SGH-T859 - is a variant of the TAB that was released by T-Mobile in the USA

Your model - GT-P7500 is a p4 - so you would need the p4 set of files.

You will also need to read back over the last few pages of this thread to get information on some additional patches needed and instructions on how to re-enable 3G after flashing the ROM
[Galaxy Tab 10.1 Android Development] MatzingerHH:
Same here. :crying:

decatf, do you want a logfile from my device?

Regards