yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] pinoz:
Xposed framework for GT-P7500

Is there anyone who got to install Xposed framework on the GT P7500 with this rom? I tried the v89 and the v88.2 with the Xposed Installer app, but both drive the tablet into bootloops.

I'm not an expert in those kind of things and any advise or guidance would be greatly appreciated.
[Galaxy Tab 10.1 Android Development] ndoki:
Help me

Flashe the rom but I have problems with the gapp tells me that I have a problem with the binary

installed gmail and Google services from aptide but do not allow to enter the google account
[Galaxy Tab 10.1 Android Development] benjdgroup:
Wifi connected but show not connection.

Hi everyone,

thanks for the instruction!

I had go through the process and get successfully update. The only issue i am facing is wifi not working. Its got connected

but show no network access. Please advise what should i do now.

Thanks !
[Galaxy Tab 10.1 Android Development] Duvel999:
Flash again

This is how I did it

Great fast Rom.

I updated from Lollipop.

Made a Titanium backup.

Followed post 1-3.

(Don't wipe internal storage.)

Installed Pico gapps & superuser.

Give it some time to Boot > 5 minutes

Enabled Unknown sources and Usb debugging.

Installed Titanium backup from Playstore, restored my apps.

Give each app their right / all permissions in Settings > Apps.

Everything works.
[Galaxy Tab 10.1 Android Development] Oliwa KausA:
Will there be an Android 9 "Pie" ersion?

My tablet is the most stable on 7.12!
[Galaxy Tab 10.1 Android Development] jrobbom5:
Help!

EDIT: Fixed. Turned out I had no idea what I was doing! :)
[Galaxy Tab 10.1 Android Development] zerong:
Hello,

I have galaxy tab GT 7510 wifi. Audio is desynchronised with video ! i reboot then all seem ok but after a moment audio is desynchronised again ! what's the trouble ?

Thanks
[Galaxy Tab 10.1 Android Development] ps.m:
Compiling from source

Hello Decatf,

thanks keeping this device alive.

I have an P7500 and installed all versions you provided up to Oreo. On Oreo I have the same problem as described in https://xdaforums.com/showpost.php?p=77541851&postcount=192

Marshmallow was the last version that handled battery status correctly. It was mentioned more times but none of the versions fixed it.

I decided to compile the sources myself and try to find the cause and later update the sources with current security patches. I have some experience with Linux (kernel and apps), maybe it it enough for this...

I have started with git://github.com/Decatf/manifest.git -b aosp-7.1.2. Moved local_manifest.xml to local_manifests.

Changes I did:

- allowed openjdk (the build environment is on Ubuntu 16.04.5 LTS), using openjdk-8

- kernel compiler set to AOSP default 4.9

- added back name="platform/hardware/google/apf" since it is used (was disabled in manifest.xml)

- added back copying Makefile in name="platform_build"

- disabled device/samsung/p5 - non-existent

- renamed arm-tcg to tcg-arm

- running source build/envsetup.sh; lunch p4-userdebug; make otapackage

The result is somewhat bigger then your last version (probably due to changes up to 7.1.2_r36).

Made a clean install through twrp. After boot it hangs in showing the boot logo (android)

Any idea what could be wrong?

Thanks
[Galaxy Tab 10.1 Android Development] decatf:
Can you elaborate on which battery status issue are you talking about?

To debug the boot process. Enable USB debugging and look at logcat / dmesg.
[Galaxy Tab 10.1 Android Development] ps.m:
Battery status incorrect

All cases were tested after clean install.

Case 1:

Let's assume, that the battery becomes low < 15%. I begin to charge (with original adapter or others that support speed charging). It shows charging and does not change the battery status,remains at the same %. If I reboot with connected charger, it switches to 100%. If I reboot without charger, it powers off due to low battery at boot.

Case 2:

Battery is low, tablet powers off. I connect charger and after some time it shows (if power button touched) that the battery is full (or partly charged). If I disconnect the charger and boot the tablet, it stops starting due to low battery.

Case 3:

Battery is charged >50%. Attaching the charger it is charged to 100%. I disconnect the charger and use the tablet. Within 10-20 minutes the battery status does not change / does not drop significantly but the tablet is powered off due to low battery.

Under other circumstances the battery can last for 2-3 days (if I do not use wifi/gps intensively). With enabled gps (using 2 apps that make use of it - Boating HD and LD-Log that takes waypoints each 3 minutes) it can be used 1 day long, so I can assume that the battery itself is not so bad.

---------- Post added at 02:19 PM ---------- Previous post was at 02:01 PM ----------

Hi Decatf,

it seems that the "uploaded" version from github was never tested by you (same applies to 6.0.1, tried that first, but much of the sources show to your home repository instead of the github one and if I replace those with github versions - or original AOSP versions, it fails too many times).

Is it (the 7.1.2_r36 version) a work in progress trying to update it to newest AOSP sources (you updated it ti 7.1.2_r36 about 2 months ago)?

Would you be so kind to update it to a version that worked for you (or provide another set of *.xml files that worked or tell me which version I should check out)?

Could you tell me what is different in my build environment from yours? I would start with a known good version...

Thanks
[Galaxy Tab 10.1 Android Development] decatf:
That's quite detailed. I haven't had those issues myself. And I honestly haven't seen those cases mentioned before. Maybe I've forgotten. Or maybe others have not described it as well as you have.

I compile the user builds for release. Not userdebug. That is probably why your build is bigger. You want userdebug for debugging anyways.

The _rXX branches of AOSP are just the monthly security patches. Nothing significant size or feature wise changes between those.

I push the branches to github. My home respositories are exactly the same as what is on github. But yeah, I don't compile from those manifests. The manifest I use are the same but with the repositories pointing to home instead of github.

There should be no difference but I haven't compiled android 7.1.2 for the 3.1.10 (downstream) kernel in a long time. Nor anything older than that. I've been using 7.1.2 and kernel 4.4 which requires a few modifications here and there. I suppose some of the 7.1.2 repositories might have gone out of sync with the branches for downstream kernel.

The 6.0 ROM was a bit of a forgotten step child. Here's the last manifest I used for android 6.0.

https://pastebin.com/13dhD9J4

https://pastebin.com/T2QJ2peH

It's best if you get the logcat and dmesg. That should tell us exactly why it isn't booting.
[Galaxy Tab 10.1 Android Development] denso_89:
why 720p playback from the hard is laggy
[Galaxy Tab 10.1 Android Development] Warzzy:
I can't download any app from Google Play( stay at the download pending).

Back button and home button aren't working for me. In addition,

I can't reach my files and folders using computer connection.

Clock was stopped.

Are they common bugs? How can I fix these bugs if they aren't common?
[Galaxy Tab 10.1 Android Development] bierma32:
[MENTION=5711912]Warzzy[/MENTION]

I See you solved your issue with the /0 Folder?

Have you make a clean install ?

Which gapps Version you are installed ?

Please active the Developer Options for MTP File transfer Protocol under USB Connections if connect your Tab to PC
[Galaxy Tab 10.1 Android Development] Warzzy:
Yes I solved the problem. I flashed the twrp few times and then I reached to folders and other things. And... Neew problems have occurred ?

Gapps ver 7.1.1

I will check the developer option.

Do its buttons work as correctly for your tab? .

Thank you again.
[Galaxy Tab 10.1 Android Development] bierma32:
[MENTION=5711912]Warzzy[/MENTION]

Have you make a clean install ?

Yes, the ROM works perfectly for me.

Also Button works, but I know other User poster the same issue with it.

Why you are not install the Open Gapps 7.1.2 ?
[Galaxy Tab 10.1 Android Development] Warzzy:
[MENTION=5390857]bierma32[/MENTION]

What is the meaning of clean install? I wiped dalvik cache, cache and system before the installation.

I did not notice this differences between gapps 7.1.1 and 7.1.2
[Galaxy Tab 10.1 Android Development] bierma32:
What about Data ? You wiped also ?

I don't know why [MENTION=4404851]decatf[/MENTION] post 2 Versions.

for Android 7.1 - 7.1.1

- P7500-open_gapps-arm-7.1-pico-20170119.zip

for Android 7.1.2

- P7500-open_gapps-arm-7.1-pico-20170416.zip
[Galaxy Tab 10.1 Android Development] Warzzy:
[MENTION=5390857]bierma32[/MENTION]

Installation:

Backup all data

Install TWRP 3.0

Wipe cache, dalvik cache, system, data

Install the ROM

Optional steps:

- Install gapps pico

- Install phh Superuser

Boot the ROM

Enable on screen keyboard by toggling "Show input method"

I just followed these steps which [MENTION=4404851]decatf[/MENTION] 's pointed out. Now I'm re-flashed StockROM for the clean install.

There're 3 different Roms which updated in 3 different times at the topic. Which is the ROM that you use? and your Tab model (p4, wifi, etc)?
[Galaxy Tab 10.1 Android Development] bierma32:
[MENTION=5711912]Warzzy[/MENTION]

Ive got the latest WiFi Version.

For a clean install you wipe / format system ,data , cache and Dalvik. I wipe also data media, but I use an OTG USB for install the ROM..

All other steps you are posted OK.

Important is that you flash ROM and opengapps at one time, than reboot.
[Galaxy Tab 10.1 Android Development] Warzzy:
[MENTION=5390857]bierma32[/MENTION]

I' ve p-7500 model (p4). It may have a problem.

I'll try the last time. Thank you for helping. :)
[Galaxy Tab 10.1 Android Development] ps.m:
Well, that is what I meant, you used your local repository that I can't access, see the first paste.

---------- Post added at 01:06 PM ---------- Previous post was at 01:02 PM ----------

I couldn't catch the early part of dmesg it seems, no idea how to do it.

Uploaded to ftp://83.65.242.238/p4/
[Galaxy Tab 10.1 Android Development] decatf:
I have now compiled and tested on device the following branches of https://github.com/decatf/manifest

aosp-6.0

aosp-7.1

All repositories were fetched entirely from online sources.
[Galaxy Tab 10.1 Android Development] ps.m:
wondering why it works for you and not for me ;-(

I checked out your current aosp-6.0 manifest.xml and local_manifest.xml and checked out a completely clean repo with them. At least the following patch

ftp://83.65.242.238/p4/decatf-mm.patch

(missing journal in some structure) is needed

with 7.1 you really meant 7.1.2 ?

7.1.2 has more build problems, I have to check, if it lies in the java version I used (since openjdk is not really supported on Ubuntu I am using a "zulu" Debian build from https://www.azul.com/downloads/zulu/#Linux)
[Galaxy Tab 10.1 Android Development] ps.m:
finally it built (6.0_r59, target=p4-userdebug) after tweaking the build environment (it wrongly uses the host toolchain - probably the assembler - and fails on libart.so with wrong/unknown relocations). It can be booted up. Wifi does not work, it sees the SSIDs, but after saving the password it does not connect. Any ideas?

Should we continue this on the appropiate 6.0.1 thread and keep only the 7.1 related issues here?
[Galaxy Tab 10.1 Android Development] decatf:
Yeah, I meant 7.1.2.

The distro matters for compiling Android. Google doesn't really keep the build system distro agnostic. The recommended one for android 6 was Ubuntu 14.04. I just stuck with Ubuntu 14.04 or 16.04 to compile ROMs. In my repos there aren't any patches for distro specific compile issues.

The ROM itself usually runs fine once it does compile though. I'm pretty sure I've used different jdk versions at some point too.

Post logs for the wifi issue. Continue in this thread. They are all pretty much inactive anyways.
[Galaxy Tab 10.1 Android Development] ps.m:
Logs after boot when wifi was disabled, trying to enable it, it does not really enable anything (does not find any SSID)

ftp://83.65.242.238/p4/wifi.log

Logs after boot when wifi was enabled, it sees all SSIDs, but it does not connect (password was saved before)

ftp://83.65.242.238/p4/wifi-reboot.log
[Galaxy Tab 10.1 Android Development] decatf:
Some thing to do with access point configuration maybe?

The wifi related parts don't require any patches other than loading the kernel module. So I don't see why it would stop working now if it was working in the last released ROM.

11-03 20:58:57.751 844 844 I wpa_supplicant: wlan0: CTRL-EVENT-CONNECTED - Connection to 54:a0:50:d8:41:4c completed [id=0 id_str=]
11-03 20:58:57.756 844 844 W wpa_supplicant: wlan0: WPA: Failed to configure IGTK to the driver
11-03 20:58:57.756 844 844 I wpa_supplicant: wlan0: RSN: Failed to configure IGTK
11-03 20:58:57.761 844 844 I wpa_supplicant: wlan0: CTRL-EVENT-DISCONNECTED bssid=54:a0:50:d8:41:4c reason=1 locally_generated=1
[Galaxy Tab 10.1 Android Development] ps.m:
wondering why it fails loading a driver (not named, so I do not know if the wifi module is meant), see the first log file.

I will revert to an Ubuntu 14..x to build your version ...
[Galaxy Tab 10.1 Android Development] ps.m:
clean Ubuntu server 14.04 LTS install

update it to latest state of this LTS (14.04.5)

install needed packages as needed for an Android build environment

install zulu7.24.0.1-jdk7.0.191-linux_amd64.deb package

checked out your manifests for 6.0.1_r59

applied:

ftp://83.65.242.238/p4/decatf-mm.patch (journal missing from structure)

ftp://83.65.242.238/p4/decatf-mm-openjdk.patch (makes it possible to use the zulu openjdk version)

compiled, it boots and wifi works now, thanks.

So the result is, that the newer build environment fails, it seems that the host toolchain is too often used even if it should not be: I found one location in libart (wrong assembler), but there are probably more that influence the build...

Have you ever tried to replace the stuff from "prebuilts"?

Are you intending to update this one (6.0.1) to _r81 and latest ASB security patches?

Which environment do you use for the 7.1.2 build (Ubuntu version + java)?

Are you intending to update it to latest ASB security patches?

Even if 8.x is tempting I need to know what the battery problem is in 7.1.2 first before going with that update...
[Galaxy Tab 10.1 Android Development] ps.m:
not quite, wifi is unstable, it can be disabled, after that sometimes it needs to be rebooted to reenable it
[Galaxy Tab 10.1 Android Development] decatf:
I've used other cross compilers for the kernel. And I've used the oracle jdk from the ubuntu repos. Never used different prebuilts for anything else.

No.

Ubuntu has openjdk. I don't know why you needed that external jdk package. I compile 7.1.2 on Ubuntu 16.04.

r@r:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.4 LTS
Release:	16.04
Codename:	xenial

$ apt show openjdk-8-jdk
Package: openjdk-8-jdk
Version: 8u181-b13-1ubuntu0.16.04.1
Priority: optional
Section: java
Source: openjdk-8
Origin: Ubuntu
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: OpenJDK Team <openjdk@lists.launchpad.net>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 540 kB
Provides: java-compiler, java-sdk, java2-sdk, java5-sdk, java6-sdk, java7-sdk, java8-sdk
Depends: openjdk-8-jre (= 8u181-b13-1ubuntu0.16.04.1), openjdk-8-jdk-headless (= 8u181-b13-1ubuntu0.16.04.1), libc6 (>= 2.2.5)
Recommends: libxt-dev
Suggests: openjdk-8-demo, openjdk-8-source, visualvm
Homepage: http://openjdk.java.net/
Supported: 5y
Download-Size: 450 kB
APT-Sources: http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
Description: OpenJDK Development Kit (JDK)
OpenJDK is a development environment for building applications,
applets, and components using the Java programming language.
.
The packages are built using the IcedTea build support and patches
from the IcedTea project.

N: There are 2 additional records. Please use the '-a' switch to see them.

$ sudo update-alternatives --config java
[sudo] password for r:
There are 2 choices for the alternative java (providing /usr/bin/java).

Selection Path Priority Status
------------------------------------------------------------
0 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081 auto mode
* 1 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081 manual mode
2 /usr/lib/jvm/java-8-oracle/jre/bin/java 1081 manual mode

Press <enter> to keep the current choice[*], or type selection number: ^C

Wifi is known to have such problems on this devices. Sleep of death and the wifi chip not initializing.

Try compiling the kernel with gcc 4.6. This device was originally built on much older compilers. GCC 4.6 is the oldest one still provided by the AOSP sources. I have used that as a fallback.

https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/
[Galaxy Tab 10.1 Android Development] ps.m:
I use the external jdk on Ubuntu 14.x to compile 6.0.1

Thanks for the hints
[Galaxy Tab 10.1 Android Development] Casper Young:
I may be off your subject a bit here, but just to say, I've never had any kind of a problem with the wifi on my device. I did replace the battery that wasn't holding a charge anymore. The Rom of this discussion easily flashed in. However, I do have one question about how my device went from a 32Gb memory down to 28Gb. Anyone got an idea where 4Gb dissappeared to?
[Galaxy Tab 10.1 Android Development] ps.m:
compiling 7.1.2

I have used your recent 7.1.2 manifest files on Ubuntu 16.04 using openjdk-8-jdk, replaced the kernel compiler with arm-eabi-4.8 and enabled the use of openjdk.

On first boot process system stopped. I choose wait, allowed fingerprint for adb debugging. The logcat is in ftp://83.65.242.238/p4/712.zip

Do you see anything unusual in the logs (I do not have yet eyes to recognize what is unusual)?

There are some services though that could be disabled like fingerprint, or disable anything phone related until a sim card is inserted...
[Galaxy Tab 10.1 Android Development] ps.m:
It seems that at least media.codec has problems. Any ideas?

The security patch is of 2017-08 in your build, but 7.1.2_r36 has 2017-10. Have you forgotten to update to patch string or was your version based on an earlier release?
[Galaxy Tab 10.1 Android Development] decatf:
I can't tell about the system process tbh. The unused services should be harmless.

The mediacodec problems are related to some kind of heap corruption. Something is strange about malloc implementation since android 7 that can cause those crashes on this device. I don't know why it's happening nor how to debug it. If media files still play which they should then whatever because there isn't anything to do about it anyways.

This ROM uses dlmalloc which is the previous malloc implementation. The standard one for android 7 is jemalloc which causes a ton of similar crashes all over the place. The best I can tell is that memory allocations mysteriously disappear from under our feet. That leads to segmentation faults.

The last release was built on r28. I never uploaded an r36 of this ROM. See the android 8 thread for an r36 build which is based on a different kernel.
[Galaxy Tab 10.1 Android Development] ps.m:
well, your manifest files for 7.1.2 use r36, not r28, so I should rather downgrade your manifest.xml to r28 and start from there?
[Galaxy Tab 10.1 Android Development] decatf:
No. Just use the r36 manifest.

I've used the ROM compiled from the aosp-7.1.2 manifest. I haven't had any problems with it. Could you upload your builds some where?
[Galaxy Tab 10.1 Android Development] ps.m:
ftp://83.65.242.238/p4/aosp*

the 6.0 build is 6.0.1_r81, updated to the 2018 september security patch level (but is useless, for ex. it reboots sporadically if connected through usb). Used with superuser/no gapps. Removed some apps.

the 7.1 build is 7.1.2, applied all updates that were missing from r28 up to r36, security state is now the "official" from r36. Used with magisk/no gapps/some apps from fdroid and microg.org (fakestore). Removed some apps (QuickSearchBar/OpenWnn), used launcher2. kernel compiled with 4.6

On first boot process system stops, later on it did not happen anymore...
[Galaxy Tab 10.1 Android Development] decatf:
Don't install superuser or any root. The userdebug builds include root by default.

With your 7.1.2 ROM here's what I've tested:

- Wiped everything

- Install the ROM (nothing else)

- Boot to launcher

- Connect to wifi

- Watch a Youtube video in the browser app

On my device it wouldn't boot to the launcher with your 6.0 ROM. Your 6.0 ROM appears to be compiled against r81. If you want to compile against r81 then you must create an r81 branch of all of the repos in local_manifest.xml. That means for each repo:

- Checkout android-6.0.1_r81 from aosp

- Apply all of the patches from my repos on top of r81

Don't merge r81 into my branches. Nor can you only change manifest.xml from r59 to r81. The branches (rXX) can't be mixed. Use the same branch for everything.

r59 is nexus 7 branch (MOB30X). That is the one I was tracking.. The aosp branches are meant for specific devices. See here:

https://source.android.com/setup/start/build-numbers#source-code-tags-and-builds
[Galaxy Tab 10.1 Android Development] ps.m:
I have uploaded a new 7.1.2 one that includes all security updates up to september 2018 (userdebug).

Did you have the "Process system isn't responding" with my build on first boot?

If not, for completeness I am booting without a sim card in 7500, could this be the cause for the failure on first boot?

Wifi has problems with WPA2-PSK, if the password is exactly 8 characters long. On the same AP, other SSID, 9 character password there is no problem. On another AP, other SSID, same password, the problem is present. I recall seeing some change in your sources in wifi code saying that it is not finished/has to be reworked... Any ideas?
[Galaxy Tab 10.1 Android Development] decatf:
I emulated simple NEON load stores in kernel. ART is using some vector registers to optimize some things. It didn't take much since the kernel task struct already stores the full 32 vfp registers even when built for a vfpv3-D16 processor so that was convenient. It's not been published on any release since I ended up reverting those optimizations instead.

I thought you had to deal with the exception then return execution to the next instruction. I hadn't thought about loading some more helper code this way. How do we determine where to jump to? And what about returning to the actual next instruction? If I understand right the process might be something like. Instr trap > branch to helper lib > emulate neon data operation > return to next instruction?

There is also a matter of conforming to the hardware floating point representation. Whatever NEON emulation library is used must be compatible with hardware float representation.
[Galaxy Tab 10.1 Android Development] jacky03:
Is this kernel supported bootanimation? I saw your aosp 5.1/6.0 all didn't supportrd bootanimation.

The "ANDROID"is:o:angel:
[Galaxy Tab 10.1 Android Development] bri972:
except a few bug i like your rom keep on doing what you do on it seem better than marsmallow