yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
You can use today's/yesterday's build with May ASB patches included.

Use latest Gapps by Deltadroid.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] jokapo:
on slimroms i only see the 6.0.1.build.2.1.

do you have a link for me on the gapps that you mean? i only found the opengaps.org... Its been a while for me that have done some flashing :o . So i choose the arm android 6.0 stock ... Is this the correct 1?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
http://andi34.github.io
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] daitalos:
great news for this old device

the device gets life again ... Lol
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Long Island NOOBIE:
P5113

Official SLIM-6 Alpha-0.9 functioning very nicely on my P5113. Thank you for keeping our aging tablets up to par with the latest and greatest rom firmware!
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Oldnobby:
Hi [MENTION=5153662]Android-Andi[/MENTION]

Were can I see the changes or what you add to this ROM if you don't mind me asking? I can't find the on first page? Thank you
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
[MENTION=7404588]Oldnobby[/MENTION] nothing on top of SlimRoms source. Device and kernel source also pushed to official slim source. Check gerrit or slimroms.org

~ All my work, news etc. on http://andi34.github.io ~
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Oldnobby:
Excellent, thank you for the reply much appreciated [MENTION=5153662]Android-Andi[/MENTION] :)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] captainnemo:
I love this ROM. It works smooth on an old device. Is there any way to increase the max volume though for the speakers? I'm trying to use the old tablet as a media player and while the sound is Ok if I'm close to it, walking away or having something else making noise makes it hard to hear. I tried editing the file in /system/etc/sound based on other info I could find about increasing the max, but that didn't seem to work (I edited the "10" file as I have a 10" tablet, so maybe that is the issue?).

Thanks

Brian
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] C03LH00:
hey guys, i have a P5100 and i flash this ROM, but when reboot say "unfortunately setup wizard has stopped" and no disappear this message, i install the gapps nano.

Sorry for my English
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] slayer101234:
open gapps will not work on slim roms use delta gapps or slim gapps
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] stevejohnson42:
? OpenGapps is one of the Gapp projects Andi lists on his page for the ROMS

I used Open Gapps Mini arm when I installed SlimRom on my tab; p3110
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] C03LH00:
hey again, sorry but i try to search for de slim gapss or delta gapps and don't find once that work, someone can give me works? sorry for my english :(
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] :
I have installed opengapps and can confirm that it works. https://slimroms.org/#/support/faq

Gesendet von meinem MotoG3 mit Tapatalk
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] slayer101234:
i clean flashed open gapps 2-3 time on slim lp while ago and everything was giving fc. on slim 6 i have tried delta gapps with google search and google keyboard addon works fine no fc and i have not tried open gapps on slim 6.

---------- Post added at 06:45 PM ---------- Previous post was at 06:43 PM ----------

here is the link for delta base 6.0.1 gapps https://www.androidfilehost.com/?fid=24591000424951861
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] :
Then your statement was not on topic and therefore wrong. We're talking about slim6 here..

Gesendet von meinem MotoG3 mit Tapatalk
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] C03LH00:
with me don't works. I have the rom manager to flash this rom on my P5100 and when the tab start give me messanges the stoped various services and the wizard setup message don't disappear.

and i F**k this because a delete the backup inconsistent :eek::eek:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] slayer101234:
did you clean flashed and what recovery did you used
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] hollandais:
Here are the links from Andi's page:

https://andi34.github.io/gapps.html

Envoyé de mon Galaxy Tab 2 en utilisant Tapatalk
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] C03LH00:
thank you slayer101234, i will try this and give you the feedback
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] smart-t78:
don't make a reboot between rom and gapps flashing.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] daitalos:
Deltadroid

https://www.androidfilehost.com/?fid=24591000424951861
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
Some older recoveries causes such issues too.

Make sure using latest common espresso twrp

~ All my work, news etc. on http://andi34.github.io ~
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] jokapo:
and then go to slimrom and select the slimkat?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
Or Slim6, lol.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] jokapo:
yeah sorry forgot to scroll still having a jetlag LOL

uhmmm wait if i click on slim 6 i go to https://slimroms.org/#/device/espressowifi this is the rom and not the gapps right

---------- Post added at 05:46 PM ---------- Previous post was at 05:41 PM ----------

ok now im confused. i downloaded the slim 6 rom but not sure which gapps to download when on http://andi34.github.io/gapps.html
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
https://androidfilehost.com/?w=files&flid=75111&sort_by=date&sort_dir=DESC

+

https://www.androidfilehost.com/?fid=817550096634796664
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Apikills:
So glad with latest security update. You're the best Andi!

Slim6 still rocks :)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] nofearek9:
from all the roms i;ve tested this is the best/fastest rom for samsung tab 2
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tobi24:
When I type "adb devices", the output is "List of devices attached: c16075f1532d06f

unauthorized

". USB debugging is enabled of course, tried MTP and PTP USB-mode and dozens of things I found in other forums, like kill-server, start-server, disable and enable developer-options again, but nothing worked. Usually a confirmation-popup should appear on the tablet, where you have to allow connecting to the PC. But it never shows up...

I have the Samsung USB-drivers installed, the tablet shows up in Windows Explorer without any problems. I came from Samsung's Stock Android 4.4, made backups from app-settings with the app "Helium", but with Slim6 the connection in Helium doesn't work anymore. The app always tells me that I would be in MTP-mode and that I "eventually have to switch to PTP-mode", but that's wrong, PTP already is selected.

That's why I wanted to restore my app-settings backups from Helium (.ab files) with "adb restore", but this doesn't work because the device is "unouthorized".

Would copying "adbkey.pub" be the solution? Where exactly do I find this file? I don't know what you mean with "from recovery". Couldn't find this file using the internal file-manager of Slim6 and also didn't find it using Windows Explorer.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] LRob:
Hi, in latest build i am facing a fast drain battery. Anyone have the same issue ?

Enviado do meu P028 através do Tapatalk
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
~/.android/adbkey.pub on Linux

If I remember right to /data/misc/adb/adb_keys/
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tobi24:
On Windows 7 I have this file in the folder C:\Users\Username\.android, but creating the folders "misc/adb/adb_keys" in the data-folder of the GalaxyTab 2 (they didn't exist) and copying adbkey.pub there made no difference, I still see the "unauthorized" response when I try to use ADB. Anything else I could try?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
In TWRP mount system and pull system/build.prop

persist.sys.usb.config=mtp,adb
ro.adb.secure=0
ro.secure=0
ro.debuggable=1

After changing it push it back and make sure it has proper file perms.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tobi24:
Sorry I never did something else in TWRP than flashing complete ROMs, so I'm not quite sure what to do. If I boot into TWRP there is a "Mount" button, and I could also select "System" there. But the only thing I can do there is clicking on "Select Storage", then select "Internal Storage" - and that's it / nothing changes, nothing more I can do.

The only thing I could do is extracting the complete ROM "Slim_espressowifi-6.0.1-20180520-2306.zip" on Windows, adding those 4 code-lines in the end of build.prop, save the file and re-pack the whole ROM with WinRar, then flash the whole ROM again? Is this what you mean perhaps? But I don't see what file permission I would have to set in this case...

PS: I'm also facing the problem that the Gallery crashes, as soon as I select an image or folder, like it was described here: https://xdaforums.com/showpost.php?p=73575555&postcount=628

This is my 1st installation of Slim6, a clean install with everything wiped / data formated, I just copied some old JPG-photos back to the tablet later on.

As solution it was written: you need to clear Data AND Cache for:

1. Gallery

2. Media Storage

3. Media Container Service

> reboot

I did it for 1 and 2, but there is no "Media Container Service" on my tablet. There also is no other file that does not belong to there in the image-folder.

In the end it was written that the .nomedia files that are created in some folders would cause this issue. Do I have to do anything with those files? Delete them? (but in this case these folders would be indexed by the gallery?)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
Extract the build.prop from attached zip.

Mount system in TWRP, after that:

adb root
adb remount
adb push /path/to/build-prop/build.prop /system/
adb shell chmod 644 /system/build.prop
adb reboot

Need to charge on of my tab2 and test if i am having problems.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tobi24:
After mounting system, I entered the 1st ADB-command in the command prompt of Windows 7, error-message is: "adb: unable to connect for root: no devices/emulators found"

So I tried the only button I found (and also used in the past) with "ADB" in TWRP, which is "ADB Sideload" in the "Advanced" menu. This way at least the ADB-connection works (device is found), but probably is in a wrong "mode" (sideload)? Error-message now is slightly different: "adb: unable to connect for root: closed"

PS: I never rooted this tablet. Would the "ADB root" command do so? Or do I have to root the device in another way? In this case I think I would give up the whole ADB-usage and don't restore my app-settings (completed leves of games should be recorded there, as well as account-details of some apps) from my backup. I also don't know if rooting maybe would cause problems with copyrighted e-books I borrow from a digital library? Maybe fixing the gallery chrash will be easier...
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
I've no issues on my own TWRP 3.2.0-0 for espresso-common on espresso3g, running Xubuntu 16.04 LTS on my PC.

andi@xeon:~/chromium/src$ adb devices
List of devices attached
c1607a408af047f	recovery

andi@xeon:~/chromium/src$ adb root
adbd is already running as root
andi@xeon:~/chromium/src$ adb remount
remount succeeded
andi@xeon:~/chromium/src$ adb devices
List of devices attached
c1607a408af047f	recovery

andi@xeon:~/chromium/src$

TWRP has root, without you wouldn't be able to do anything with it.

TWRP is a own tiny OS, while your ROM is a different OS ;)

Sideload is only for "adb sideload", for normal adb access you only need to be connected while TWRP is running.

ADB vs adb ? Wrong driver installed?

Get adb running, you can check via "adb devices" if it works or not... that's nothing i can do for you.

Once you get it working you can follow my instructions.

In TWRP make sure in Mount menu "mount system partition read-only" is NOT checked.

Maybe try in mount menu to disable and reenable MTP to get your adb issue solved.

Maybe delete all device drivers (e.g. use USBDeview https://www.nirsoft.net/utils/usb_devices_view.html ) and install the universal adb driver ( https://adb.clockworkmod.com/ )
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ze7zez:
I had a similar problem that only occurred in some ROMs.

In my case, it helped to remove the entry in the windows registry.

[HKEY_CURRENT_USER\Environment]
"ANDROID_SDK_HOME"="C:\Android"

You can read more in my thread and in the links in it.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tobi24:
DISABLING (and not re-enabling) MTP in mount-menu worked!

In TWRP now I also get:

List of devices attached

c16075f1532d06f recovery

before with MTP enabled, I only got the adb-connection in sideload-mode, but nowhere else in TWRP.

Your 5 commands of post #794 worked, the build.prop from you is transferred.

But having the ROM booted, there still are PTP- / adb-problems:

Even though PTP is selected

[IMG="PTP USB-mode"]https://i.imgur.com/isPLYaU.png[/IMG]

The backup-app "Helium" still says I would be in MTP-mode

[IMG="Helium"]https://i.imgur.com/FnLwAr3.png[/IMG]

It worked with Samsung's stock ROM just the day before, but does not Work in Slim6.

Also adb still doesn't work as it should. I have 2 versions:

- One is "Minimal ADB", this is its output:

adb devices
List of devices attached
adb server version (31) doesn't match this client (39); killing...
could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon

- the other one is from ClockworkMod's "Universal Adb Driver", here the output is:

adb devices
List of devices attached
c16075f1532d06f offline
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
Choose MTP instead PTP
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tobi24:
Thanks for this suggestion, but I don't have an "ANDROID_SDK_HOME" entry in "Environment". Also didn't find anything like this, searching the whole registry.

---------- Post added at 16:51 ---------- Previous post was at 16:44 ----------

The result is the same, same messages in "Helium" and exactly the same output with both adb-versions.

Maybe in the file build.prop your code

persist.sys.usb.config=mtp,adb

needs to be changed into

persist.sys.usb.config=ptp,adb

because DISABLING MTP also worked in TWRP?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
I'll play around next week with it. There's something wrong Google side for adb authentication on 6.0 on user builds.

For security reasons I am not compiling as userdebug anymore, this would allow "adb root" which breaks some apps.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
Well, you could try

C:\Users\\.android and delete both adbkey and adbkey.pub , see if the authentication dialogue pops up now.

(You can move the files instead deleting too, maybe safer solution)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tobi24:
Ok thanks a lot for everything! If there is no fix, I could also live without ADB I guess, but maybe it's more important for others...

After deleting those files, the output from ClockworkMod's "Universal Adb Driver" stays the same. The output from "Minimal ADB" now is "c16075f1532d06f unauthorized" again, still no authentication dialogue pops up. By the way: Those 2 files are created every time I run "Minimal ADB" , but not if I run adb from ClockworkMod's "Universal Adb Driver" folder.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
Ok, hope I found the issue for no authentication dialogue. Next build has the change included, will be up later or tomorrow.

Let me know if adb works for you on that.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ze7zez:
If the only reason for using adb is to restore the application, why do not you use the simplest method?

1. Install build 20171020 (adb works)

2. Restoration of the application

3. Wipe Dalvik Cache and Cache

4. Upgrade to build 20180520
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
No need. Can't test atm but quite sure the new build fixes it.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] LRob:
Returned to previous version of slim build 20180414, because drain battery issue, this version don't have this problem. [MENTION=5153662]Android-Andi[/MENTION] I suggest you take a look a this.

Enviado do meu Redmi Note 4 através do Tapatalk
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
Can you flash https://xdaforums.com/showpost.php?p=76505059&postcount=188 and see if the drain appears? In that case it's the lmk update causing the issue.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
New builds are up.

Edit:

Quick tested, now there's the request window asking "Allow USB Debugging?" [emoji3]

June ASB applied too.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ze7zez:
Just enough

C:\adb>adb devices
List of devices attached

and nothing more.

But when debugging mode is enabled, adb works. :D
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
Only works on latest build, else you'll have to pull the boot.img and modify the default.prop in ramdisk.

( https://github.com/SlimRomsSecurity/android_build/commit/df25170a3912897a005dad756a11c2ab026609de )

First you need to enable developer options, check USB debugging.

Now switch to MTP (the connection menu in notification bar)

Running "adb devices" on your PC now should open the request dialogue on your tablet.

Works fine here on clean flash.

edit: [MENTION=5159681]tobi24[/MENTION]

andi@xeon:~/android2/buildbot$ adb devices
List of devices attached
c1607b71de1b89f	unauthorized

andi@xeon:~/android2/buildbot$ adb devices
List of devices attached
c1607b71de1b89f	device
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tobi24:
Excellent! :) I can confirm it, now the request-window appears as soon as you plug in the USB-cable (having USB-debugging enabled of course), also the backup-app "Helium" now works with this ROM and also both adb-versions I have ("Minimal ADB" and the one from "Universal Adb Driver") now work!

But I still have the problem that the gallery crashes, as soon as I select an image or folder. I again cleared data and cache of Gallery and Media Storage, then rebooted, but still it crashes. Also wiped cache and dalvik in TWRP before flashing the new ROM and new GAPPS.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
[MENTION=5159681]tobi24[/MENTION] Gallery works fine here. No crash watching my screenshots, so I've transferred some other pictures from PC and also no crash (p3110).

Does 3rd party gallery work? (E.g. Simple Gallery)

Doesn't look like a general problem, but you can attach a logcat if you like.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ze7zez:
If this happens to you on a pure Slim, then there is a high probability that on some partition the file name is corrupted (or has a special character) that the media server can not handle.

Is it the same without an SD memory card?

Sometimes execution in TWRP helps:

Advanced -> Fix Contexts

If these tips do not help, then I suggest that you backup everything and before installing ROM.zip will do wipe all partitions including Internal Storage.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tobi24:
I don't have an SD card inserted anymore, just used it for flashing SLIM6. This tablet still was on Samsung's original stock ROM a few days ago, but I wiped all partitions (Dalvik / ART Cache, System, Cache, Data, Internal Storage) in "Advanced Wipe" and also used "Format Data" in TWRP before installing SLIM6.

I tried "Fix Contexts" in TWRP now, didn't help. I'll try another gallery next and/or provide a logcat, after searching how this has to be done. I did it just once, years ago and can't remember it ;)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
Reboot.

Connected via adb.

Start "adb shell logcat > logcat.txt"

Reproduce the Gallery FC.

Abort/stop the logcat creation by pressing Ctrl+C.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tobi24:
Here's the logcat, done exactly as described:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
06-11 13:33:43.611 1644 1709 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'int android.graphics.Bitmap.getWidth()' on a null object reference

Trying to fix it on next build for you. There's a nullpointer, hope https://github.com/SlimRomsSecurity...mmit/05c5e21b816d239ce974076e4496415e219e729f fixes it
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ze7zez:
In my logcat with P3110 there is no com.google.android.finsky, and there is a lot of this in your logcat.

Is logcat from fresh Slim ROM, or after installing gapps and / or anything other than ROM.zip? :confused:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tobi24:
A few days ago I installed Slim_espressowifi-6.0.1-20180520-2306.zip, a completely fresh installation with everything wiped as written in post https://xdaforums.com/showpost.php?p=76781816&postcount=814

Now I'm on the latest Slim_espressowifi-6.0.1-20180610-2114.zip from yesterday, this time I only wiped cache and dalvik, because it's just a minor update, no completely new ROM as before. I copied 8 photos in 3 sub-folders of "Pictures", but double checked all file- and folder-names, all just regular a-z characters and numbers. I also copied lots of eBooks onto the tablet, but also tried excluding this folder from Gallery-index by copying the .nomedia file from another folder into the eBook-folder today. There also are a few apps installed already now:

- FX File Explorer

- Brave Browser

- Adobe Acrobat Reader

- Aldiko Book Reader

- Onleihe (for renting eBooks from a library)

- Kindle

- GMX Mail

- Shazam

- Monument Valley

- OpenSudoku

And I activated the "Privacy Guard Manager" in the developer settings and changed some auto-start permissions of apps that I don't want to be started when booting (but only custom apps, no system apps). I used the latest PICO version of Open GApps.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
[MENTION=5159681]tobi24[/MENTION] new build up for espressowifi, let me know if the Gallery FC is fixed.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tobi24:
[MENTION=5153662]Android-Andi[/MENTION] THAT'S IT, the default-Gallery doesn't FC anymore! Thanks for your great work and fast fixes, you really know what you're doing :good:

But I have to admit that even though the Gallery now works, I tried "Simple Gallery" now, because in the default Gallery there's pretty much nothing you can do after selecting a photo or an album. I thought you could move photos from one album to another at least, like it was the case with Samsung's default Gallery. This is a function my mother needs (actually all this is for her) when importing photos from a digital camera, then select and move imported photos to an album named by the excursion or holiday. She always did it within the Gallery and I didn't want her to be exposed to a file-manager, where she accidentally could do something wrong. So I will show her how to use Simple Gallery, this one has all she needs. I'm sorry that I made you spend time for searching the bug in the default Gallery and now I'm using another one, but I had no chance to see that the default one doesn't have those basic-functions.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
Np, it's a bug and should be fixed even if I couldn't reproduce it. Good to hear it works now, might make other people happy :)

Enjoy the ROM!