yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] Just_Another_N00b:
The latest 3.18 kernel you posted did NOT have the scrolling issue [i.e. works FINE] after dirty flashing the kernel only (and without wiping cache)... Attached are the 3.18 clk_summary and mode files anyhoo (even though not needed).

Mind you, restarting takes some time (because of ?)... And the Samsung 10.1 pre-boot logo shows some pixellation in short bursts. Also some black screen moments between pre-boot logo and "Android" text logo when doing full restart.

-- EDIT --

Kernel Adiutor works fine, currently running 1400MHz overclock. Deep Sleep no issue, so all in all this kernel does work!

-- EDIT --

Spoke too soon, got a spontaneous reboot when trying to switch on WiFi from default pulldown menu. Will pull a dmesg.log if it happens again...
[Galaxy Tab 10.1 Android Development] decatf:
Okay. 3.18 is only a midway for development. You don't need to do anything about those other issues on 3.18. I will post an updated TWRP Bigsys and 8.0 ROM with kernel 4.4.
[Galaxy Tab 10.1 Android Development] decatf:
I've updated the ROM and recovery to 20171109. Hopefully this works on all display panel types.
[Galaxy Tab 10.1 Android Development] Just_Another_N00b:
I will try it and report.
[Galaxy Tab 10.1 Android Development] tiberian41:
Update from twrp311-20171107-BIGSYS.zip to twrp311-20171109-BIGSYS.zip, and,

aosp-8.0-p4wifi-20171107.zip to aosp-8.0-p4wifi-20171109.zip,

appeared to go smoothly, :good:

---------- Post added at 11:34 PM ---------- Previous post was at 11:05 PM ----------

Edit: Tab no longer seems to power off from the power menu, it reboots instead.
[Galaxy Tab 10.1 Android Development] tiberian41:
Forgot the log file, have added it now.
[Galaxy Tab 10.1 Android Development] decatf:
Get the kernel log from the previous boot /proc/last_kmsg. The problem occurred during the previous boot not the current one.
[Galaxy Tab 10.1 Android Development] tiberian41:
Sorry mate, had to reboot/recreate the error as the last_kmsg file is blank/empty.
[Galaxy Tab 10.1 Android Development] tiberian41:
Sorry last_kmsg didn't upload.
[Galaxy Tab 10.1 Android Development] decatf:
Do you have the USB cable plugged in when powering off? If so that is a known issue. Unplug the cable and it should power off.
[Galaxy Tab 10.1 Android Development] tiberian41:
:o Thanks, I had forgotten about that. I've been used to leaving it plugged in and it powering off OK. :good:
[Galaxy Tab 10.1 Android Development] zubozrout:
Screen flickering (TWRP works just fine)

Hello,

I've got the 3G version of this tablet (GT-P7500) and am experiencing screen flickering and and later noise - soon after a static Samsung Galaxy Tab logo appears.

I am on the 20171109 version.

Since the device is unusable as is I can't even enable adb.

Is there anything I can do to?

I am attaching a dmesg log file from the recovery - but am not sure if that can help.

And since apparently I am not allowed to attach files nor link to external sources here is all I can do, so sorry for the difficulty:

url: paste [dot] ubuntu [dot] com [slash] 25974980
[Galaxy Tab 10.1 Android Development] decatf:
What is the display mode?

cat /sys/devices/tegradc.0/mode

The proper config should be:

pclk: 76000000
h_ref_to_sync: 0
v_ref_to_sync: 0
h_sync_width: 48
v_sync_width: 18
h_back_porch: 64
v_back_porch: 76
h_active: 1280
v_active: 800
h_front_porch: 16
v_front_porch: 6
stereo_mode: 0

What is the display clock?

mount -t debugfs none /sys/kernel/debug/
cat /sys/kernel/debug/clk/clk_summary

The disp1 clock should be 570000000.

pll_c 1 1 570000000 0 0
disp1 1 1 570000000 0 0

If both are correct then try toggling the display panel.

echo 0 > /sys/devices/virtual/mdnie/mdnie/lcd_power
echo 1 > /sys/devices/virtual/mdnie/mdnie/lcd_power
[Galaxy Tab 10.1 Android Development] zubozrout:
Hello,

thank you very much for the info. The /sys/devices/tegradc.0/mode is different:

pclk: 76005000
h_ref_to_sync: 0
v_ref_to_sync: 1
h_sync_width: 48
v_sync_width: 18
h_back_porch: 64
v_back_porch: 76
h_active: 1280
v_active: 800
h_front_porch: 16
v_front_porch: 6
stereo_mode: 0

As for this /sys/kernel/debug/clk/clk_summary the display clock is the same:

pll_c 0 0 570000000 0 0
disp1 0 0 570000000 0 0

And this does what is expected - that is turn the screen off and on again. I haven't seen any issue there:

echo 0 > /sys/devices/virtual/mdnie/mdnie/lcd_power
echo 1 > /sys/devices/virtual/mdnie/mdnie/lcd_power
[Galaxy Tab 10.1 Android Development] decatf:
The display is unusable in recovery too?
[Galaxy Tab 10.1 Android Development] zubozrout:
Oh, sorry if I made that impression. No at all, it works in the recovery just fine.
[Galaxy Tab 10.1 Android Development] decatf:
It is the exact same kernel code (but different build) for ROM and recovery. That means if recovery works then the ROM should too. Maybe I compiled the ROM kernel wrong or something.

I've compiled it again and uploaded the boot image. This boot image also allows adb to be enabled. Flash this image on to the boot partition.

To enable adb you need to push your adb key to the device while in recovery.

adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys

On Windows it might be in your user folder under the same .android directory.

xdaforums.com/devdb/project/dl/?id=27344
[Galaxy Tab 10.1 Android Development] zubozrout:
Wow, well, the latest kernel works and there is no more flickering. Interesting is that this file looks the same as yours (with the latest boot.img build): /sys/devices/tegradc.0/mode

I've tried flashing the AOSP image again and I can confirm it flickers but if I then flash the separate boot image you provided it becomes functional.

Therefore I am happy and thank you very much for your time and help :).
[Galaxy Tab 10.1 Android Development] decatf:
Build 20171117

- November security patches

- Linux 4.4.98

- kernel bug fixes
[Galaxy Tab 10.1 Android Development] dookie23:
I installed the 20171117 rom today. It's working very well. It seems to boot up a lot quicker and it also seems to be running smoother than Nougat. The only thing that I can't get to work is the Play Store. Is there a working version that I can install? Thanks.
[Galaxy Tab 10.1 Android Development] Oliwa KausA:
Which GAPPS version do I have to take? with camera, phone, gmail, maps, ...
[Galaxy Tab 10.1 Android Development] bonotheedge:
Tablet is not waking up

Anybody else experience the issue were the tablet not waking up after the screen is off for a while?
[Galaxy Tab 10.1 Android Development] decatf:
GApps pico

Try to get previous kernel log when this happens.
[Galaxy Tab 10.1 Android Development] dookie23:
I have tried open-gapps-arm-8.0-pico-20171117.zip but I am not able to login to the Play Store. I got stuck at the screen saying "Checking Info" or something like that.
[Galaxy Tab 10.1 Android Development] decatf:
Wait a bit. It takes some time for the GApps to be processed by the runtime compiler. It's not a smooth user experience but I don't think there's anything that can be done since this device cannot run as fast as modern hardware.
[Galaxy Tab 10.1 Android Development] Oliwa KausA:
Where is the camera app?

Where is the phone app?

---------- Post added at 06:32 PM ---------- Previous post was at 05:37 PM ----------

What about the 3G function? Is there still a special version? And how does the camera work?
[Galaxy Tab 10.1 Android Development] Amsrael:
Dude, read the first post
[Galaxy Tab 10.1 Android Development] Amsrael:
First of all i congratulate you [MENTION=4404851]decatf[/MENTION] for making a effort to develop this new version for our reliable old tab :) , i attach the last kernel log if its any help :D
[Galaxy Tab 10.1 Android Development] bonotheedge:
Here is the link for the previous kernel log . I have the issue that the tablet is not waking up after the screen is off for a while. I hope it helps.

https://drive.google.com/file/d/1F3Rruj-2Jc6PSTTJHddL4RL6JFSyQ0Ox/view?usp=drivesdk
[Galaxy Tab 10.1 Android Development] dookie23:
I left that running and came back after 4 hours. The tablet was still showing that screen. WiFi has been on the entire time. Attached a screenshot of what the screen looks like.
[Galaxy Tab 10.1 Android Development] decatf:
It shouldn't take that long. Maybe closer to 5-10 minutes or so. I experienced the same problem but it always makes it though once the dexopt process has done its thing. For now I can only suggest that you clear the dalvik/art cache and try again.
[Galaxy Tab 10.1 Android Development] ianlamb42:
Hang/freeze in TWRP 3.1.1-20171109-BigSys

My Tab 10.1 p4wifi was working fine with aosp-7.1-p4wifi-20171005, and using twrp2870-20150814-p4wifi, but when installing 8.0 here with twrp311-20171109-BIGSYS, I am having problems with twrp. Sometimes it freezes on the teamwin splash display, but usually it gets to the menus. However, if I don't keep clicking or swiping something faster than maybe once every half second to a second, twrp hangs, and I have to start over. This makes it really hard to carefully follow the instructions, of course. There's no device listed from adb devices when it's frozen. Previously adb was working OK with 7.1.2.

I once managed to get the aosp-8.0-p4wifi-20171109 installed, but it was also freezing after android boot, with a distorted background image displayed.

It's model GT-P7510-MA16ARB, if I'm reading the label correctly. It was not rooted, and did not have gapps installed with 7.1.2, and I wasn't intending to install them now, unless needed.

If there are any suggestions or additional info' I can provide, please let me know. I have a last_kmsg and adb bugreport output from 7.1.2 if anything in there would help. Thanks!
[Galaxy Tab 10.1 Android Development] Amsrael:
After test a few gapps versions, i found a possible solution

https://www.apkmirror.com/apk/googl...-940-175751883-android-apk-download/download/

This version of gservices works fine for me
[Galaxy Tab 10.1 Android Development] dookie23:
I finally got gapps to work. My mistake was that I rebooted the tablet after flashing the rom and then booted back to recovery to flash gapps.

I did notice one thing. I am not able to automatically apply my overclock settings during boot using Kernel Adiutor. The settings will succeed to apply manually after the tablet boots up but not automatically at start-up.
[Galaxy Tab 10.1 Android Development] decatf:
Does it happen frequently? The log shows that it suspends and there's nothing after that. It seems characteristic of that old sleep of death bug.

Are there any sort of system or kernel tweaks applied?

Do you have to the same problem with the non BigSys TWRP 3?
[Galaxy Tab 10.1 Android Development] ianlamb42:
I had some kind of problem, but don't remember exactly what. I tried twrp3000-20160207-p4wifi and twrp303-20170120-p4wifi some time ago, had problems, and went back to 287.

At this point, something went wrong when I tried to (speedily) go back to 287, and I don't get anything except the Samsung splash screen and a blank screen when trying to boot or start recovery. I can access it with heimdall in "Odin3 Download" mode, but am new to using heimdall, and haven't found the way to get a working recovery yet. It did seem to take a recovery.img expanded from twrp2870-20150814-p4wifi.zip, with:

heimdall flash --SOS recovery.img --no-reboot
...
Downloading device's PIT file...
PIT file download successful.

Uploading SOS
100%
SOS upload successful

Ending session...
Releasing device interface...

However, it only gives a blank screen when booting to recovery mode.

I probably need to re-format back to the previous, but don't know how yet. :o
[Galaxy Tab 10.1 Android Development] ianlamb42:
So with the expanded 287 recovery zip I also did

heimdall flash --HID hidden.img --no-reboot

which, with the ole power/volume button presses got it to boot into 287 recovery. From there installed the 7.1 OS, and wipe fixed/formatted the cache. A long reboot, turned on virtual keyboard, and things seem to be working OK again. Apparently it wasn't actually charging the battery all day while plugged into the usb though, so it got down to 14%. Phew. :D

Please let me know how I might help debug the 3.0 TWRP.
[Galaxy Tab 10.1 Android Development] mop09737:
New Oreo Rom

I've install this rom following the procedure in first post with no problem, also the chromium apk. So far it's slow but it is OK.

Thanks for everything :)
[Galaxy Tab 10.1 Android Development] HannibalLecter:
deleted. I thought this was for galaxy tab 8.9. [MENTION=4404851]decatf[/MENTION] can we get Oreo for p5 too?
[Galaxy Tab 10.1 Android Development] decatf:
If I remember right the old sleep of death issue was sporadic.

Is bluetooth or gps on? What about connecting to different wifi access points?

Something is different on your configuration which is triggering this bug...

Are able to get into adb shell before it freezes? Maybe if you can get something out of the 'top' command and see if there is some process using all the CPU.

It is possible to get the kernel log of TWRP 3 if you can't access adb from recovery itself. Install a working ROM with root. Then install TWRP 3 (via heimdall or odin). Boot into recovery and let it freeze. Then reboot to the ROM and grab the previous kernel log from /proc/last_kmsg.
[Galaxy Tab 10.1 Android Development] ianlamb42:
I will try TWRP 3 again in couple days, after Thanksgiving.

There is an odd occurrence rooting when flashing 7.1.2 again, with phh superuser.zip, without gapps, then installed phh superuser app from f-droid. Now, there is a notification for SuperSU Installer, to tap to install. Unfortunately, that gives "SuperSU's su binary is not present, this is a fatal error !" Using phh superuser app, and setting Superuser Access, for Apps and ADB, adb shell WILL allow su to root. Could the SuperSU installer message problem be from having the zip under /sdcard/Download instead of at the top?
[Galaxy Tab 10.1 Android Development] Oliwa KausA:
My system is not stable yet. Freeze more often! The boot process is very fast!
[Galaxy Tab 10.1 Android Development] decatf:
I don't know of any mechanism which works that way...
[Galaxy Tab 10.1 Android Development] mahowi:
How long should it take to install the ROM?

I have installed TWRP 3.1.1-20171109-BigSys and wiped system. When trying to install aosp-8.0-p4wif-20171117.zip it hangs at about 75%.

Output:

Installing zip file '/sdcard/aosp-8.0-p4wif-20171117.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
Warning: No file_contexts
Target: samsung/GT-P7510/GT-P7510: 4.0.4/IMM76D/UELPL:user/release-keys
Patching system image unconditionally...

Edit: Installation hangs now for more than 1,5 hours. Is there any log, where I can find the reason for hanging?

Edit2: Ok, now I have found /tmp/recovery.log:

I:operation_start: 'Flashing'
Installing zip file '/sdcard/aosp-8.0-p4wifi-20171117.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
selinux_android_file_context: Error getting file context handle (No such file or directory)
Warning: No file_contextsTarget: samsung/GT-P7510/GT-P7510:4.0.4/IMM76D/UELPL:user/release-keysTarget: samsung/GT-P7510/GT-P7510:4.0.4/IMM76D/UELPL:user/release-keys

Extracted file "/tmp/install/bin/backuptool.functions"
Extracted file "/tmp/install/bin/backuptool.sh"
Extracted 2 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
run_program: child exited with status 127
Patching system image unconditionally...

performing update
Patching system image unconditionally...blockimg version is 4
maximum stash entries 0
using existing stash /data/recovery/d25689ab0c7831ae4baddb7ee984bf0256a48ed0/
erasing 96479 blocks
writing 1024 blocks of new data
writing 1024 blocks of new data
[...]
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data

Shouldn't the system partition get mounted?

~ # mount
rootfs on / type rootfs (rw,seclabel,size=358236k,nr_inodes=89559)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
/dev/block/mmcblk0p10 on /extra type ext4 (ro,seclabel,relatime,data=ordered)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
none on /config type configfs (rw,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p8 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p8 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
[Galaxy Tab 10.1 Android Development] ianlamb42:
Attached are several last_kmsg files from after restarts with twrp 3 bigsys, and one from no bigsys. This time twrp 3 no bigsys, twrp311-20171009-p4wifi, seemed to work OK, except the OS never actually started (7.1.2).
[Galaxy Tab 10.1 Android Development] decatf:
It should not take long. It is much faster than my Nougat ROM. Try to get the kernel log from recovery.

No.

It is hanging a lot on the TRIM command in last_kmsg-nobigsys-171126. I enabled TRIM in TWRP 3 so that might explain the reports of freezing during install.

For the BigSys recovery it shows some sort of freeze ups in last_kmsg-171126-2 but the kernel messages are not very descriptive and kind of cryptic. The TRIM command is only used when installing a ROM so this is a different problem. The last_kmsg-171126-4 is from booting the aosp-8.0 ROM and it shows the display driver hanging. I had already fixed a bunch of issues causing that but evidently there's some devices which still have this problem. Recovery only uses basic framebuffer graphics so it is uncertain of these two are related.

Here's a build with some changes related to display and graphics. It's a few things that I can think of which might affect the display freeze.

twrp311-20171127-BIGSYS.zip
[Galaxy Tab 10.1 Android Development] ianlamb42:
This twrp 3 works better, at least it only froze for me once; however, the ROM is not working. After showing samsung splash screen for a while (10+ minutes?), it eventually goes back to twrp. Attached are a few more last_kmsgs files.
[Galaxy Tab 10.1 Android Development] decatf:
Here is the kernel for the ROM. Give them both a try.

p4wifi-aosp-8.0-kernel-20171127a.zip

p4wifi-aosp-8.0-kernel-20171127b.zip
[Galaxy Tab 10.1 Android Development] ianlamb42:
Reboot to recovery from twrp 3 bigsys is not working - just goes to blank screen, no response to adb devices

Noticed top of twrp 3 20171127 version still says 20171109 at top, fwiw.

Here is what I did, and got.

install aosp-8.0-p4wifi-20171117, kernel 20171127a, and phh superuser zips; reboot to system; blank screen

manually reboot recovery

adb pull last_kmsgs-171128-1

install aosp-8.0-p4wifi-20171117, kernel 20171127b, and phh superuser zips; reboot to system; blank screen

manually reboot recovery

adb pull last_kmsgs-171128-2

reboot to system; blank screen

manually reboot recovery

adb pull last_kmsgs-171128-3

twrp fell asleep or stopped responding to adb

manually reboot recovery

adb pull last_kmsgs-171128-4

There's a lot of "unable to open" "failed" and "denied" in the logs.
[Galaxy Tab 10.1 Android Development] decatf:
None of those captured the kernel from the ROM. That means it didn't boot or didn't get very far into the boot process.

It does show a lot of disk i/o timeouts in recovery. Have you been using other ROMs without any problems? Perhaps run an fsck on the storage.
[Galaxy Tab 10.1 Android Development] ianlamb42:
I'd been using your 7.1.2 ROM without any problems.

fsck looks OK?

~ # mount
rootfs on / type rootfs (rw,seclabel,size=358236k,nr_inodes=89559)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
/dev/block/mmcblk0p10 on /extra type ext4 (ro,seclabel,relatime,data=ordered)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
none on /config type configfs (rw,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p8 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p8 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 359.2M 20.0K 359.2M 0% /dev
tmpfs 359.2M 20.0K 359.2M 0% /tmp
/dev/block/mmcblk0p10
11.7M 5.5M 5.9M 48% /extra
/dev/block/mmcblk0p8 13.1G 2.3G 10.8G 18% /data
/dev/block/mmcblk0p8 13.1G 2.3G 10.8G 18% /sdcard
~ # umount /sdcard
~ # umount /data
~ # e2fsck -fv /dev/block/mmcblk0p8
e2fsck 1.42.9 (28-Dec-2013)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

3103 inodes used (0.35%, out of 884736)
1006 non-contiguous files (32.4%)
2 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 3035/29
697221 blocks used (19.73%, out of 3533436)
0 bad blocks
1 large file

2513 regular files
549 directories
0 character device files
0 block device files
1 fifo
0 links
31 symbolic links (29 fast symbolic links)
0 sockets
------------
3094 files
~ #
[Galaxy Tab 10.1 Android Development] ianlamb42:
FWIW, to return to aosp-7.1-p4wifi-20171005, I could not get it installed with twrp 3 (non bigsys) - it just stayed at the OS install step "forever." Twrp 2.8.7 worked fine. However, I still get the "superSU's su binary is not present, this is a fatal error !" from SuperSU installer, although su works OK, like in adb shell.
[Galaxy Tab 10.1 Android Development] jaibar:
Works like a charm! Many thanks, decatf ?
[Galaxy Tab 10.1 Android Development] tiberian41:
My setup was starting to glitch after I updated a couple of programs and I couldn't clear it so I did a clean install. Now Firefox sync won't work in spite of being set to auto sync. I may repit and go back to 7.1. Any ideas guys?

Under manage account, sync is enabled, but the options for what to sync are greyed out.

Edit. I've gone back to 7.1.2 for now. But will test 8.0 again very soon.
[Galaxy Tab 10.1 Android Development] Sparubens:
Also having the sleep of death on random moments. Clean flash, no apps installed or no settings/kernel settings changed
[Galaxy Tab 10.1 Android Development] Maximal2018:
Hi just wondering how the process going with this?? will it work stable in a few months, any new builds would be great, it seems twrp311-20171127-BIGSYS.zip is very unstable and locks up under my Samsung galaxy tab 10.1 wifi only, had to go back to twrp2870-20150814-p4wifi.zip version, also I was not able to boot either kernels on my device at all, I be stock on android 7.1 or older, sometimes I do need the flash on the device, and panorama effects sometimes, so I switch back to old versions sometimes just for that reason, sometimes I use the camera other times I prefer just to use it as an ebook reader at times.

anyway I be using Android 7.1.2 Nougat until this is stable and working, I understand the camera app may never run right with new builds, at least this can be updated, my insignia tablet10.1 is stuck with android 6.0.1, since insignia broke their update app, and will not even release an upgrade to android 7.1.2 which is cool that this tablet can be updated, I just wish I was able to upgrade my cheap Insignia tablet too :) thanks trying to keep this alive with android build updates.
[Galaxy Tab 10.1 Android Development] Oliwa KausA:
Oreo installed. Runs very unstable. I returned to 7.12. Let's wait and see what the future with 8.0 and 10.1 still has in mind ?!
[Galaxy Tab 10.1 Android Development] decatf:
I've posted an 8.1 ROM. Do a full wipe when coming from 8.0.

There are no changes with regards to the recovery/install issues.