yashsingh1/xdaforums huggingface dataset:
[Lenovo Vibe K5 Plus ROMs, Kernels, Recoveries, & O] hsj51:
Twrp version shouldn't cause an issue.

Report to dev with proper logs to get it fixed.
[Lenovo Vibe K5 Plus ROMs, Kernels, Recoveries, & O] raynofff:
3.3.1 on pie builds, im now on aex 6.6, with pbh kernel its much better
[Lenovo Vibe K5 Plus ROMs, Kernels, Recoveries, & O] hsj51:
Pbh kernel works on pie roms??

Can you link it.
[Lenovo Vibe K5 Plus ROMs, Kernels, Recoveries, & O] Fax Max:
Pbh on pie?
[Lenovo Vibe K5 Plus ROMs, Kernels, Recoveries, & O] augugusto:
I been told this isn't maintained anymore. Is that true? How stable is it? How reliable are the alarms? (I'm asking this in the viper post because it is unclear to me)
[Lenovo Vibe K5 Plus ROMs, Kernels, Recoveries, & O] Betrayal92:
I think not... Search for telegram group, there are several Pie ROM. DOT os 3.1 works really good, AEX 6.7 is on the oficial page
[Lenovo Vibe K5 Plus ROMs, Kernels, Recoveries, & O] mmohamed2:
Hi,

i'm having a problem with the voice, when i call someone, it's very low, i barely hear the voice, how can i fix that?

thanks
[General Topics] ccpraveen:
Is it possible by some tweaks/settings to make the coreplayer 1.24 to stream only the audio? Heck, I see there are lots of good music on Youtube, and many a time I dont want to watch the video, burning up the bandwidth and battery, leading to slow speeds/buffering/reduced battery life.

So is there a way to turn off the video streaming (not just turning off the screen), and thereby save bandwidth and listen to the wonderful audio streams alone?

Thanks

Steve
[General Topics] Rudegar:
i doubt it stream mean a stream of data providing the reciver with data bits of the time

it's one stream
[Nokia 8.1 Questions & Answers] Saswata Chakraborty:
So, I bought this device yesterday. Updated the device to the latest security patch. Everything is up and running smooth. However, there is an issue on Google Play Store. When I go to Play store settings, I can't find Play store certification info. I know it is supposed to be at the bottom. But, on my Play store, it's just missing. There is nothing below play store version info (see screenshot). I have already cleared play store data and cache, disabled and enabled play store. Nothing works. Still can't see play store certification info. However, I did a safetynet test and it is passed. Play store is up to date. Can find Netflix. Everything is fine. It's just that, the certification info is completely missing on my play store.
[Nokia 8.1 Questions & Answers] singhnsk:
Same verison of PS here and I can see certified text there. I haven't updated to the June patch yet and I can't say if it makes any difference. Even if it does, I don't think it's anything concerning [emoji28]

Sent from my Nokia 8.1
[Nokia 8.1 Questions & Answers] Saswata Chakraborty:
I agree. I don't have any issue. I can see all my purchased apps. However, I had pre registered a few games like COD Mobile etc and now they are not showing as registered. Just a bit curious, what might be the issue.
[Xiaomi Redmi Note 7 Questions & Answers] mCdroid09:
Is there a splash logo of Redmi note 7 pro violet for our note 7 lavander? Please could someone port it :laugh:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Awesomeslayerg:
Oo our first custom rom!! Thanks alot!! Cant wair to try it soon
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Important Note: The Night Mode setting in Developer Options is set to "Always off" by default. Don't change it! When I set it to "Automatic (based on time of day)", the screen went black and I couldn't recover without a factory reset. (I'm assuming that this was a bug in SystemUI.apk.)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] NightHawkUndead:
Thanks for the effort and time you've put into this.

Unfortunately I can't get it to work. I will wait for detailed full instructions. I just keep getting Odin fails.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Well, I just verified the MD5s and they match. However, to be a little more squared away, I replaced the original .tar file that I uploaded with a .tar.md5 (a.k.a. "tarball) which has the MD5 footer that Odin can use to verify the file integrity. I've also compressed the contents with LZ4, which cut the size down by a third.

Installing the new tarball with Odin3 v3.13.3 on my tablet went smoothly, so I hope this works for you.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] NightHawkUndead:
Finally got it to work. Had to flash back to stock. Wipe. Then immediately reboot bootloader again and flash Rom.

How do I go about rooting now?

Edit: nevermind, got it rooted. Everything is working fine now!

Sent you a donation for your work. ? ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] garyemiller:
I have a new SM-T510 on T510XXU1ASEF

I flashed this ROM with Oding3 3.13.3. Then it rebooted. The Nexus logo goes by, I am asked to confirm the ROM is non-standard by pressing the "power" button. Then I get the TWRP splash screen, and it hangs.

Tried to flash 3 times, same result.

Is there something to going back to stock, wiping, bootloader, flash again? Or is that just doing things until it works?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
It's important that you wipe the data partition before TWRP boots, since it currently hangs when it encounters an encrypted file system. (Yes, this really shouldn't happen, but I haven't found a fix for that TWRP bug yet.)

Did you select "Wipe data/factory reset" in the stock OEM recovery immediately before you flashed this custom ROM?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] garyemiller:
"Did you select "Wipe data/factory reset" in the stock OEM recovery immediately before you flashed this custom ROM? "

Yes.

I got it to work. reinstalled stock rom (link above). Booted it stock. Enabled Developer Mode, Enabled USB debugging. confirmed OEM still unlocked. Boot to recovery, wipe, boot to bootloader. Flash this ROM with Odin3. reboot. All is well.

So now I guess I gotta do the Device ID dance. Install Magisk Manager, patch the boot.img from your tar file, then use TWRP to install the magisk_patched.img as boot.

Along the way I also wasted a lot of time trying to flash with heimdall 1.4.2. But that was very flakey. Odin3 just worked.

---------- Post added at 08:46 PM ---------- Previous post was at 08:23 PM ----------

I guess I should mention my biggest issue was unlocking the bootloader. Not like before.

Power off. Hold Vol UP and Vol Down. Plug in USB. Long press Vol UP to unlock.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
If you install Magisk, you might not have to do the device certification dance. It tries to fake out Play Protect.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] garyemiller:
The device certification was painless. I've doe that before on other devices.

Rooting with Magisk was also painless:

Grab boot.img from your tarball.

adb push boot.img /storeage/emulated/0/Download

patch using Magisk Manager

adb pull /storage/emulated/0/Download/magisk_patched.img .

heimdall flash --BOOT magisk_patched.img

I can't get SafetyNet to pass, even with Magisk SafetyPatch module. But not a big deal to me.

Is there a way to turn off the google page on the launcher?

Thanks for the nice ROM! So much better than stock.

I'm still looking for a good ad blocker for Pie. Up tile now I have used a Raspberry Pi as a dnsmasq server for ad blocking.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
If you open up the Android One Launcher settings, there's a "Display Google app" option that you can disable.

Yeah, I've tried the usual tricks like spoofing the fingerprint, but that didn't work either. This kind of hard Play Protect device rejection seems to happen for me whenever the vendor partition is using release keys and the system partition is using test keys.

I haven't found an XDA thread yet that really provided deep insight into the algorithm that Google uses for Play Protect and SafetyNet. And given the proprietary nature of what it's doing, we may never get it. I think our best long-term solution is to get LineageOS 16 builds that pass CTS testing, but we may have to scrounge for 64-bit drivers.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] garyemiller:
I just went with Nova Launcher. It has been good to me.

I can wait for Lineage to catch up. I'm happy to be rid of bloatware. And with root I can block ads and my firewall works.

Thanks for the ROM! I'm happy!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Just restore the original param image. (But seriously, why would you? The stock boot splash is ugly! :))
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] d4dave:
Just ordered my T510, can't wait to try this out when it arrives:)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
The 3G/128G config was selling for just $250 USD through Costco until a few days ago. That's a pretty insane value....as long as you aren't stuck with Samsung's One UI, that is. ;)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DarthGW:
will there be a new release coming?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yes, I'm trying to build an unofficial LineageOS 16.0 release, but am struggling with some build issues. The primary goal is to deal with the Play Protect device certification (but I definitely won't pass SafetyNet). Eventually, I'll also get to fixing MTP.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] macapa1994:
wow dude, thanks a lot for you work
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] andreasoz:
Is it possible to install this on the 510 with Product code	NEE

PDA	T510XXU1ASF2

CSC	T510OXM1ASF3

It's the stock may Nordic firmware
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] MossyTC:
I guess you didn't wipe data/factory reset in stock recovery.

There is a link to stock firmwares in the OP. Extract the files from the firmware download, flash the BL_..., AP_..., and CSC... files in Odin (at the same time). You will then need to boot into the system (skip Google log in) to turn on USB debugging before continuing with the steps in the OP.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Alternatively, you just can download the latest TWRP (v3.3.1-5) and install it with Odin. The new version doesn't hang on the splash screen when it hits an encrypted data partition. From there you can do a factory wipe and reboot to system.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] joseduardo199201:
I have a SM-T510 on T510XXS2ASH4 and i can't install the rom. I tried to downgrade to T510XXU1ASEF with ODIN but i have "fail" any ideas to fix this?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
My last build of TWRP (v3.3.1-5) also included a .zip for install from TWRP.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] davekaz:
I installed it thru twrp. Perfect:svetius:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
I finally got the stock ROM re-installed and turned on USB debugging. Made sure bootloader was still unlocked, wiped with factory reset, but neither the Nexus stock nor the LOS would flash. Error says "only original firmware can be flashed".
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Just so you know, I've got a new build of Nexus Stock based on the latest LineageOS 16.0 and the OEM September 2019 update (T510XXU2ASI4) and with the latest TWRP (v3.3.1-5) and OpenGApps (20191017). However, I can't get Odin to flash the damn thing. All seems to proceed normally with it writing each image, but at the end I get a "Complete(Write) operation failed." I've tried different cables, different computers, upgraded my drivers, checked the images with e2fsck...but nothing seems to work.

<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1303)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 2199 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> param.bin
<ID:0/005> product.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> vbmeta.img
<ID:0/005> vendor.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

At this point, I've killed about 6 hours screwing around with Odin, so this release will need to wait until next weekend.

What do you think about just blowing off Odin tarballs and releasing these builds as OTA updates (.zip files) that can be installed from TWRP?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] :
This will be better to share them as twrp zip file
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] PopCaps1996:
What do you think about just blowing off Odin tarballs and releasing these builds as OTA updates (.zip files) that can be installed from TWRP?........

this would be great because them twrp zip doesnt require pc! also i really love this rom! just wish there was an option for status bar to add date format to clock
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] davekaz:
Yes
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
I can get TWRP to install, but it won't boot to system once I do. And I can't install either the Nexus or LOS md5s from Odiin. So it seems a zip install for TWRP is my only option.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Qrion:
SM-T515 stuck on TWRP splash screen

Hi newbie here. i tried to root my SM-T515 without doing much research and ended up with bootloop. The device in now stuck on TWRP logo and i am unable to shutdown or boot to recovery or download mode.

1. Enabled USB debugging and OEM unlock

2. Booted to Download mode and removed OEM lock by long pressing vol up.

3. Rebooted to bootloader and rooted using Odin3_v3.13.1 and twrp-3.3.1-1-gta3xlwifi.tar

4. Odin root PASS

But after reboot the device it stuck on TWRP splash screen. Have i bricked the tablet or is there any hope of recovery?

Thank you for any help you can offer.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] fredrik0612:
Hi I'm coming from the initial release. How do I update? Do I need to do a factory reset on twrp? Thanks!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] MossyTC:
Use Odin to flash the latest tar.md5 file. It will enter TWRP after the flash, no need to do a factory reset, just reboot to system.

Some users have reported getting stuck on the boot animation after a dirty flash, I don't know if that still happens with the latest version. If it does the solution is to boot into recovery and flash Multi-disabler.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
After all the mistake I've made trying to get this installed, including having to wait all day for the battery to drain to recover from what I feared was a total brick, I figured to wait a few days before making another attempt. But my curiosity got the best of me and I decided to make one more attempt. It seems I was able to learn from all of my previous mistakes, and this time everything went like clockwork. Up and running with latest LOS version and everything looks great so far. I think the biggest difference was that I started from the AS14 stock version and not what was on the tablet when I bought it.:good::o
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] milsabords:
So far I have not succeeded unlocking the boot loader.

Dumb question %-( : instructions say to press Volume Up AND Volume Down. There is only ONE Vomume button wth three positions, Idle, Up and Down. How can I mash Up and Down at the same time ?

Should I do it power-on or power-off, with or without USB cable connected to my PC ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] MossyTC:
There are no dumb questions! Only dumb people asking dumb ... wait that doesn't sound right ...

Anyway - the Up and Down parts of the volume button can be pressed at the same time. You can see this if you first press the Up part, and while keeping the Up part pressed you can then also press the Down part.

Do this while the device is off, USB cable not connected, then connect the USB cable.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] milsabords:
Thanks, it did not work, tablet in power off state would not get alive pressing either Vol keys..

Shoud I mash the power button while pressing the Volume Up, then the Volume Down buttons ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] MossyTC:
It should work with only the Volume and Volume down buttons held down when the USB cable is connected from the computer.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] milsabords:
Did not work.

On the powered offed screen while connected to the PC I see a 100% level in the middle and yellow triangle with an USB picture at the bottom.

Pressing either Vol key does nothing.

In an earlier post you advised not to connect ???

Note: I have a 2016 Tab A, running RR Pie. Never had this kind of problem with it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Check the Status Bar settings in the new build based on LineageOS 16.0. It has options for Clock Position, Show Seconds, and AM/PM style.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Could you please take this side discussion to one of the bootloader unlocking threads? The trouble you're experiencing is not specific to this custom ROM.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] kieffey:
Need help problems with internal storage

having an issue and was wondering if anyone could help me. I flashed the ASI4 September update. Then flashed the Nexus rom and flashed magisk with twrp but I cant download modules and infact I cant do anything with the internal store. Cant make files at all. But I can download from play store. This is the sm-t510.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
If you open the file manager, do all of the folders on the sdcard look wierd? It sounds like you neglected the wipe/factory reset prior to flashing the Nexus ROM. This will result in the data partition remaining encrypted and unusable in Nexus. There is supposed to be a way to solve the problem but I think the easiest solution is to reflash AS14 and start over.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] kieffey:
Ok thank you, I'll do that when I get home from work. That does sound like it will fix it. And yeah there was a bunch of goofy files I deleted prior to the nexus flash

---------- Post added at 09:05 PM ---------- Previous post was at 08:49 PM ----------

Other question. Does it matter for the CSC part cause there's the home csc as well
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
I always use the CSC. You never use both, just one or the other. The HOME one is supposed to save some of your data, but if you did a factory reset, it is all gone anyway.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] kieffey:
Thanks for that. And your help worked. Shes running great now thanks a bunch
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] davekaz:
Anyone have a problem connecting to PC.? My PC doesn't see it anymore
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yeah, that's the MTP bug. Enabling USB Debugging should work around the issue until I can figure out a better fix.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] davekaz:
It's always been on.. thanks for replying so quickly
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Which version are you running? The original few releases had no MTP support whatsoever, but a kernel fix re-enabled it in the 20190906 build. This last build tried to forego maintaining two kernels (one that works with OEM ROMs and another that works with AOSP-based custom ROMs) by using a change in the init .rc file to support FunctionFS. Unfortunately, that only works if ADB is around to initialize FunctionFS first.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] davekaz:
The latest
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Well, MTP has been working for me on the latest release as long as USB Debugging is enabled in Developer Options. You might check to see that ADB is really working. Could be the service needs to be started on the PC, but I don't think that's the case.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] davekaz:
I'll check it tonight but if it doesn't pop up on computer I doubt adb devices will work thanks for all you help.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] HisokaRyodan:
Hey guys, turns out I accidentally flashed the BTU-T515XXU2ASI5-20191001131757 version with Odin and altho I can install twrp and root via Magisk, I can't install the rom without getting an error. I assume its due to the firmware version. Is there a way to revert back to the older version used with this rom? Or will I just have to wait until the rom gets updated to support the 10.01 version of the firmware? Thank you for all the hard work!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] kieffey:
I've been using it for over a week now and it runs great. No problems with magisk either
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] itsjch:
I know this might be a big ask but could you de-bloat the rom so much that you only start with google play and settings?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Sorry, but no. I've published a LineageOS 16.0 build if you want to start from bare bones and you can always remove apps you don't want in TWRP. This one's called Nexus Stock because it includes the Stock variant of OpenGApps.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ChangeToTower:
..any chance for a version of LOS for the 515 in the future?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Actually, I've been meaning to serve notice that I'm officially dropping support for the SM-T515, as I don't have the hardware available for testing. I'll continue to build TWRP releases with the custom kernel, but some developers who can actually test their builds will have to take over responsibility for building custom ROMs.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] StarGeneral:
Can i dirty flash the LOS-based build over the previous non-LOS ROM? Or do i have to wipe the device? Thank you in advance :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] d4dave:
I did this yesterday on my T510 and had no issues. YMMV but if take a full backup first then give it a go.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
A new build has just been posted:

Change Log:

20191109:

USB Debugging is enabled by default (MTP workaround)

SurfaceFlinger optimization to improve scrolling performance

Updated to latest OpenGApps (20191109)

Now building TWRP update (.zip file)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] GalaxyNexus1st:
Thank you !!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] StarGeneral:
Thank you very much for your work. I can confirm that dirty-flashing over non-LOS based ROM works indeed.

I have a question: Is it correct that the tablet says "20191017-110649" under Settings -> About Phone -> Build number? I would have expected sth. like 20191109 there? Or where can i check the version of the ROM currently installed?

Thank you in advance.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Well, that's the LineageOS 16.0 GSI build date. Currently, I'm not changing the build timestamp for simple tweaks to the build.prop because it's not been rebuilt. I'll have to consider what would be most appropriate.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] StarGeneral:
Thank you for your fast response. It would be really cool if there would be a menue giving information about which version of your ROM is currently installed.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] leonkernan:
Just updated with the zip file and Chrome certainly feels like it's scrolling a bit better. Hopefully it's not just in my head since I read that changelog.