yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] meetkalamar:
Thanks for everything decatf! You are awesome! Unfortunately with my financial situation I can't have you a beer nor a coffee, but I am thankful all the ROMs and experiences you've been promoting! My custom rom/rooting adventures started with this tab back to 2012 and as the following years I got surprised with your ROMs. You keeped my p4 update for so long, even when I stopped using it... Now my wife's phone is dead and she's been using the Tab your nougat rom (pretty faster than this Oreo one) as we can't afford a new phone for now. Again, thank you!
[Galaxy Tab 10.1 Android Development] PolesApart:
Sorry for the off topic, but I'd like to port your kernel to the Motorola Atrix. Maybe try to get some rom running but I'd do it for fun, if I manage to get some free time, so no expectations . Running Linux would be enough. Any tips are appreciated. I think that making the panel and a usb keyboard working would be enough for start. I know little about Android bootloader on the device and Tegra 2 in particular, but I'm experienced in kernel programming. Thanks!
[Galaxy Tab 10.1 Android Development] decatf:
There is barebones Tegra 2 support in the mainline kernel. This kernel is basically the mainline kernel + peripheral drivers. In truth it's actually the android common kernel but with respect to device porting the android kernel stuff has no relevance here. That is because those android patches are for higher layer things related to Android userspace.

First thing and most important thing. Does your device have a serial debug connection (UART)? You need it to read kernel logs.

If it does not then you might be able to do it the harder way which is what I did for this device. I used the android ram_console (last_kmsg) which dumps the kernel log to RAM.

The process is:

Port ram_console to mainline and make sure it writes to the same memory address as your stock kernel.

This part is device specific so you must implement it for the Atrix so that the log is written to the same memory address that recovery will read it from.

Install the bare kernel and boot the device then wait for a few seconds. I counted to about ~10 seconds on the Galaxy Tab 10.1.

Mind you, there is no display or anything at all because nothing is ported. We only want to let kernel log be written to ram console.

Reboot (using power+volume) into recovery and read the log from /proc/last_kmsg.

It's a bit tedious but once the kernel boots far enough to initialize USB and mount the partitions then you don't need this process anymore because you can connect to ADB. I spent the better part of last summer doing this. If you want to proceed with this method I can help you get started on it.

You must have one or the other of these working. Otherwise you can't get kernel log. You'll not be able to port without the kernel log for debugging.

Once you've got kernel logs then the main tasks are as follows. These are device specific so you must do this for your device. You can't copy pasta it from another one but you can and should reference other tegra devices that run on mainline.

- Port all of the stuff from arch/arm/mach-tegra/board*.c to device tree.

- Port peripheral drivers (batter, charger, display, touch, sound, etc)

Luckily for us Tegra 2 owners a couple of key components like power and regulators are the same and have mainline drivers already. So once you've got the bare platform booting then the rest of the work is a matter of which peripheral driver you want to get working.

Edit: I never touched the bootloader since it is locked on this device anyways. We can boot custom kernels on the Galaxy Tab 10.1 but the bootloader has always been stock.
[Galaxy Tab 10.1 Android Development] PolesApart:
Sweet! I'll see if I find the time to spare and I'll cry for help if I get stuck :) Thanks!
[Galaxy Tab 10.1 Android Development] astepkin:
Hi decatf! Could you please update the root software download link? Thanks!

UPD: Will this work? https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Galaxy Tab 10.1 Android Development] astepkin:
Thanks!

For any bigsys edition my tab goes to sleep of death. The sleep of death happens when the device is booted and left untended for more that several minutes. I can't do anything until the battery is discharged. I am not sure that log file you require can give the answer. I could upload a backup to you if you wish.

Latest non-bigsys firmware works good.

What else can be done? Thanks!
[Galaxy Tab 10.1 Android Development] Sparubens:
So, is the 7.1 ROM smoother then this 8.1?
[Galaxy Tab 10.1 Android Development] Vybze:
Any way to get stick mount or any otg mounting app to work with this rom?
[Galaxy Tab 10.1 Android Development] Oliwa KausA:
Will there be Pie for the tablet? Yes, no, maybe
[Galaxy Tab 10.1 Android Development] mistersixt:
No : https://xdaforums.com/showpost.php?p=77299942&postcount=185

Kind regards, mistersixt.
[Galaxy Tab 10.1 Android Development] bobo187:
rom install failure

noob

SGH-T859

followed instructions. installed twrp bigsys, wiped cache and system. reboot --install aosp-8.1-p4wifi-2081011.zip. get error

E1001: failed to update system image. updater process ended with ERROR: 7.

Do i need to install new kernel first or is it compiled in the rom, if so, where can i get it.

edit: once i got this error:

failed to mount /dev/bloch/mmcblk0p4 at /system: device or resource busy

updater process ended with error: 7

i think i forgot to wipe on this one.

can you help? thx

---------- Post added at 04:59 PM ---------- Previous post was at 04:53 PM ----------

noob

SGH-T859

followed instructions. installed twrp bigsys, cleared cache and system. reboot --install aosp-8.1-p4wifi-2081011.zip. get error

E1001: failed to update system image. updater process ended with ERROR: 7.

Do i need to install new kernel first or is it compiled in the rom, if so, where can i get it.

edit: once i got this error:

failed to mount /dev/bloch/mmcblk0p4 at /system: device or resource busy

updater process ended with error: 7

i think i forgot to wipe on this one.

can you help? thx
[Galaxy Tab 10.1 Android Development] Clamor:
host1x syncpt stuck

[MENTION=4404851]decatf[/MENTION], Hello! How you managed to fix host1x syncpt stuck? I'm Tegra 3 developer and have same issue on ported 3.4 kernel on N or higher :(
[Galaxy Tab 10.1 Android Development] decatf:
Try to assert the reset control for gr3d and gr2d during probe. Here's what it looks like on this kernel but keep in mind it's kernel 4.4 and this reset mechanism doesn't exist in the downstream kernel 3.1 or 3.4.

https://github.com/Decatf/linux/blo...taging/tegra/video/host/gr3d/gr3d.c#L220-L232

I think the equivalent in the downstream kernel is tegra_periph_reset_assert. Here it is for the dc controller in the downstream kernel. Maybe apply a similar operation to gr3d and gr2d.

https://github.com/pershoot/android...-10.1/drivers/video/tegra/dc/dc.c#L2665-L2671
[Galaxy Tab 10.1 Android Development] MaximalRoot:
so I also had this type of problem was using aosp-7.1-p4wifi-20180427 and twrp311-20180416-BIGSYS and P7500-open_gapps-arm-7.1-pico-20170416 , these I installed, I also used aosp-8.1-p4wifi-20181011

anyway yesterday I was listening to some music with my android tab with that 7.1 above on my tab with my Blu tooth headphones, had the tablet in sleep mode, where you press the power button once, and it turn itself off, would not start up again without plugging it the usb power cord, once I connected it to the pc, I was able to get it going again, I don't think I had this problem when I was using either aosp-7.1-p4wifi-20171005 or aosp 6.0 versions with twrp311-20171009-p4wifi version, anyway I going to have to downgrade the version because of the hard powering off that is happening, since I need my tablet stable, I want to use 8.1 but can't if its going to cause that type of problem where only plugging in it to charge the battery will allow it to turn on again, I think this is what the Sleep of death problem is either from BIGSYS version or a bug in the newer versions of aosp. if its fixed in a newer release version, well I keep checking to see if this problem ever gets fixed, since I can live without the flashing feature of the camera, but I can't or will not use an unstable upgrade, I do want to use the newer versions but if it causes the sleep mode of the tablet to hard power off to the point where it will not start up without having to plug it into the charger then that's not good, I and have to downgrade it to an stable version because of that. I don't no if this problem would also be in android 9.0 pie if its related to the boot loader BIGSYS versions or the aosp versions themselves. if these tablets ever get an stable android 9.0 or not.
[Galaxy Tab 10.1 Android Development] henry136:
I have clean flash new firmware:

aosp-8.1-p4wifi-20181011.zip + Open GApps (pico)

everything running good. (included google play)
[Galaxy Tab 10.1 Android Development] maximal2019user:
maybe its the optional install root part, after installing 20181011 and gapps (pico) I was installing also supersu on older 2017 builds and Magisk-v17.2 or v17.1 on this 2018 build I think, maybe is the not restarting after sleep mode or sleep of death problem with its batteries etc.. having to replug it into the usb port on my computer to start my p4wifi device. I noticed on the 1st page , their is nothing about install either supersu or magisk with this version, maybe that's the problem I was having since I think I had done so, my question to henry136 is it stable and do you also have the same model device as me? I maybe made the mistake of thinking I needed to install the root optional zip file before, maybe that the cause of the problem, where the device when in sleep mode would seem like it shuts down, and will not start up again without pluging it into the usb port, when it showed the battery charging mode then and only then would my device bootup again running the aosp-8.1-p4wifi-20181011.zip build with GApps (pico) and the Magisk .zip could that of been the hardware problem that was causing it when in sleep mode not to turn on again with this build? that's my main question if its related to using any rooting software with this build, again on my 2017 aosp 7.1 I have been using supersu and also not twrp311-20180416-BIGSYS with the aosp 7.1 I have been using the one that's labeled twrp 3.0.0-0 p4wifi. zip file instead, that's the only difference between whats been stable for me and what's not stable, I am guessing the death of device in sleep mode is related to having the root zip file installed, maybe my mistake if that's what causes that big problem with the hardware, I try it without the root zip and see if that fixes the problem, since I would like to install use 8.1 if its just the root install zip causesing the sleep mode to power off and not power on this device again, if not using it fixes that problem, that would make me happy in any case to know if that's the cause of my device problem.

p.s. I was also clean flash new firmware with this software, I forgot to tell you that, again I think the sleep of death or sleep mode device problem is related to using optional root file listed in my post above. not installing it on an clean formatted device from twrp bigsys , I reformatted all partitions before installing 8.1 and I am now not installing any root zip file not going to use supersu or Magisk , just install 20181011 and open_gapps-arm-8.1-pico-20181222 , I have notice before that some of the open gapps pico builds can causes crashing problems, I hope that the downloaded newest version doesn't have that problem, since some of them crashed and other gapps work, I guessing its because this device is old etc..
[Galaxy Tab 10.1 Android Development] hybiepoo:
I'm having the same issue where the tablet won't wake up after it sleeps. Have to hold the power button until it reboots. I'm not at home to run logcat against it yet, but I will do that later.
[Galaxy Tab 10.1 Android Development] C0rn3j:
Fresh ROM flash + magisk flash and logcat is already being spammed to high hell. Didn't try launching the app yet even. Is this an issue on your side or on Magisk's side?

https://haste.rys.pw/raw/ogiwaqewip

^ via 'adb logcat'
[Galaxy Tab 10.1 Android Development] decatf:
https://github.com/topjohnwu/Magisk/issues/921
[Galaxy Tab 10.1 Android Development] C0rn3j:
Oh, thanks, so a Magisk issue.

I've reflashed without Magisk for now (don't really need root) and tried installing f-droid and some random game I could find there called TowerJumper, but it just launches into a black screen.

01-08 20:51:00.380 2006 2026 I godot : ERROR: set_custom_uniform: Index p_idx out of size (version->custom_uniform_locations.size()).

01-08 20:51:00.380 2006 2026 I godot : At: ./drivers/gles2/shader_gles2.h:323

01-08 20:51:00.381 2006 2026 I godot : ERROR: set_custom_uniform: Index p_idx out of size (version->custom_uniform_locations.size()).

01-08 20:51:00.381 2006 2026 I godot : At: ./drivers/gles2/shader_gles2.h:323

01-08 20:51:00.381 2006 2026 I godot : ERROR: set_custom_uniform: Index p_idx out of size (version->custom_uniform_locations.size()).

01-08 20:51:00.381 2006 2026 I godot : At: ./drivers/gles2/shader_gles2.h:323

01-08 20:51:01.363 2006 2026 I godot : ERROR: mesh_add_surface: Condition ' surface->vertex_id == 0 ' is true.

01-08 20:51:01.363 2006 2026 I godot : At: drivers/gles2/rasterizer_gles2.cpp:2036

01-08 20:51:02.161 344 396 D MPLSensor: cb_onMotion:2

Am not sure if this is a Godot issue, issue of the game or some issue with the tablet HW/SW since it's shader errors.
[Galaxy Tab 10.1 Android Development] decatf:
The GPU drivers are closed source. There's nothing that can be done on this side.
[Galaxy Tab 10.1 Android Development] C0rn3j:
Hm, looks like this tablet uses Tegra 2 SoC, and it looks there indeed is a 2D/3D MIT-licensed driver, did you try it or similar efforts?

https://github.com/grate-driver/
[Galaxy Tab 10.1 Android Development] decatf:
Barebones 2D X11 acceleration. No 3D acceleration. Not meant for Android.
[Galaxy Tab 10.1 Android Development] C0rn3j:
The dev blamed the kernel and closed the issue.
[Galaxy Tab 10.1 Android Development] MysticJ:
TWRP-BigSys

Hi,

I am about to upgrade my 10.1 (GT-P7501, Wifi+G3, P7501XXLP1, Kernel 3.1.10+) from Nougat(7.1.2) to Oreo.

While I have now spent an hour searching and downloading all files I fail to find a link to TWRP BIGSSYS and the PIT-File for Odin to repartition the device.

(Or do I misunderstand some step?)

Thanks for your advise

M.

Update: blind me. Didn't realize the file in the same folder as the ROM as the download opened in the same window...
[Galaxy Tab 10.1 Android Development] mistersixt:
Hi decatf,

any chance to get a new 8.1 version including the Feb 2019 security updates? And maybe Bromite 72.X, too? That would be great!

Kind regards, mistersixt.
[Galaxy Tab 10.1 Android Development] decatf:
I bricked my device some time ago. The previous time my device died, someone donated one to me. This time I've paid for (a damaged) one myself off Ebay. Hopefully the motherboard is still good on it. We'll see when it arrives!
[Galaxy Tab 10.1 Android Development] SeeDoubleYous:
Thanks decatf for the great work on all these ROMs for our tablet over the years.

I have now decided to go to a newer tab, but the old P7501 is still working. If you are interested in it, I would donate it to you. :)
[Galaxy Tab 10.1 Android Development] decatf:
Thanks but no need to. I've gotten a working one again.
[Galaxy Tab 10.1 Android Development] akira86:
Hello,

I tried to install android 8.1 without error but system never starts after the reboot (stuck on white android logo). To be sure, I tried the previous release but with the same result.

I give a change on android 7.1 because present is the download page and this worked and started correclty.

So, I checked that the system partition has the 1Go size but don't know if I miss an important step to have the 8.1 version working.

Have you any advice ?
[Galaxy Tab 10.1 Android Development] juangutierrez29:
Can somebody tell me how to get root with android 8?
[Galaxy Tab 10.1 Android Development] mistersixt:
Flash Magisk in TWRP, and install the Magisk app afterwards ... I would say :) .

Kind regards, mistersixt.
[Galaxy Tab 10.1 Android Development] kro362:
Setcpu

After installing magisk manager I tried to install setcpu but it did not work, any solution? Thank you
[Galaxy Tab 10.1 Android Development] Ryan681:
Any news for an update ?
[Galaxy Tab 10.1 Android Development] ithink314:
Kernel Adiutor

Kernel Adiutor, from f-droid.
[Galaxy Tab 10.1 Android Development] mistersixt:
...yup, also waiting for a new 8.1 update including latest security patches, detcat, any chance to bring up a new build please?

Kind regards, mistersixt.
[Galaxy Tab 10.1 Android Development] perrin21:
Is this still being developed? There doesnt seem to be any updates since 2018. When is the next due?

---------- Post added at 12:53 PM ---------- Previous post was at 12:08 PM ----------

Mine didn't work either, i used a different app 3C CPU manager instead. Not sure what settings are optimal though yet
[Galaxy Tab 10.1 Android Development] OgJeeves:
p4vzw

Hello all,

First, thank you Decatf and all of the other devs out there for all the work that you have done. I have learned a lot about what it takes to create ROMs for these older devices. Thank you for all that you do!

I have a GT 10.1 and wanted to breath new life into it, as it currently sits at stock ICS 4.0.4. I'm hoping there is a way to make this update compatible with my device.

If you are willing to modify the ROM for the device, or provide guidance on how to modify it myself, I would be eternally grateful! I do not need cellular service to work.

Thanks again!
[Galaxy Tab 10.1 Android Development] thekaki:
We n8000 users

Hoping to see one for n8000 coz we are normally left behind
[Galaxy Tab 10.1 Android Development] daneal2u:
Just took the tab out of the dust and charged it overnight. It doesn't power on, no matter I boot normally or onto recovery mode. Need help cuz I need to sale it out.
[Galaxy Tab 10.1 Android Development] bierma32:
Only chance , open the Tab, unplug the Battery and hold Power button for 20 sec. Connect the battery and hope its boot up. Make sure that your battery is charged .
[Galaxy Tab 10.1 Android Development] daneal2u:
does this rom have any issue of offline charging?
[Galaxy Tab 10.1 Android Development] hellfreezover:
Hi,

Trying to see if this works on my old P4WIFI...

Successfully installed TWRP 3.11, Wiped system , Rebooted to TWRP

Installed Rom and Pico GAPPS.

After ~25 min it is still stuck on android animation...

I assume this is not the expected outcome...

Should I clean data?

Should I install Rom boot, and only then install GAPPS?

Should I clean everything?

Appreciate any help on this :)

I had Nougat AOSP based rom before, on my TAB
[Galaxy Tab 10.1 Android Development] bierma32:
Clean data, system , cache dalvik and art

Install ROM and gapps at the same time, than reboot,

Wpie cache and dalvik
[Galaxy Tab 10.1 Android Development] hellfreezover:
Yes, I figured I need to do this...

Note that Google play services is not working, you have to install the version from apkmirror to fix it..
[Galaxy Tab 10.1 Android Development] MaximalRoot:
just got a new device that can run android 9 but with a few bugs so far.

my devices this one model and an Samsung galaxy tab A SM-T580 device

https://www.sammobile.com/samsung/gt-p7510/firmware/GT-P7510/XAB/ this device if anyone ever needs to restore Samsung stock rom android 4.0.4 on it with odin.

https://xdaforums.com/galaxy-tab-a/development

anyway today I reported the two bugs to that other forum since testing out two different android 9 roms, which the headphones both blutooth and plugin would not playback voices in google play books, it tested them fine, but when I went to play aloud if failed to run it on an eBook.

anyway if this one ever gets android 9 rom I hope this old device doesn't have the same problems my new one had with android 9, since I tried it and google text to speech with play books read aloud was not working under it, and of course on the SM-T580 the camera app crashing when going to front view on some custom rom's and panoramic view was not working so I did that thing with Odin software and restore the stock rom from sam mobiles website, which above is the link for this old device, I also went back to stock rom under it since the camera still works better on this device with android 4.0.4 since too much of the camera was broken after a few versions on this device, on android 4.4.4 it was working correctly and ever since newer custom roms where released it was broken afterwords I think that maybe android 5 it camera working maybe not really sure of the camera history when it worked on this device and when the custom roms started breaking the camera drivers around what year and what custom firmware's anyway.

I think and then when android 6 custom roms came out it broke the camera app but anyway I just got tired on using half broken roms and went back to the stock rom on this device for now.

anyway it would be cool if this device would get android 9 since they have built in smart brightness adjustment power management system type feature, and night mode too on android 9, like a bluelight effect for nighttime reading etc.. which google play books also has built into it still.

liquid_remix-10.0.10-20190716-OFFICIAL-gtaxlwifi

lineage-16.0-20190811-UNOFFICIAL-gtaxlwifi

open_gapps-arm64-9.0-stock-20190815

Magisk-v19.3

these above roms is where I had the camera app and google play books read aloud problems since the google text to speech seems to work but not in the app on the new device, which of course works with Samsung stock rom 8.1.0 but not android 9 on the same device yet. anyway I am new to using 64bit versions of android on this device that may be the problem but I am not sure, since I just tried these custom roms on my new device yesterday and found two problems right away with it , so I went back to its stock firmware for now.

below is what I tried on my new device before going back to android 8.1.0 Samsung stock rom for SM T580. from the sam mobile website.

""https://www.sammobile.com/samsung/galaxy-tab-a/firmware/SM-T580/XAR/download/T580UEU4CSC1/269289/"" Url for new device not for this one device that I also own still.
[Galaxy Tab 10.1 Android Development] Brianm94:
Great ROM

My device is working great with Android 8.1 especially after installing Android Go Enabler and Universal GMS Doze through Magisk. The device is way more responsive then before. The only drawback of installing Android Go Enabler is that you can no longer use split screen. But considering the spec of this device, you shouldnt use split screen it even if u can.

The built-in launcher is still kinda laggy especially swiping into apps drawer. Highly suggest to use a third-party launcher. I'm using Nova launcher, the "circle" app open animation makes the homescreen feels way snappier.

My only problem is audioand visual getting out of sync when watching youtube videos using the youtube app white using built-in speakers or headphone jack (BT is fine though). After rebooting the device, the adio visual sync is good for awhile until it starts building up again. It really bothers me that I'll have to watch youtube with a browser. Please!! If anyone knows how to fix this.

Besides, there's a few seconds delay when trying to open the recent apps screen. Grid Recents helps slightly, but the lagis still obvious. I'm guessing it was because of the thumbnail screenshot. Wish there's a way for it to show only the app icon like android 2.3, im sure it will make it way snappier.

Besides, the design of the recent screen seems like it's from an older Android version and not native to Oreo.

There's some lag during screen rotation as well, but since I'm not spinning my device all day round, it doesnt bother me too much.

Anyway, big thanks to [MENTION=4404851]decatf[/MENTION] for giving support to our tabs after all these years.

Typed and sent from GT P7500 Android 8.1.0