yashsingh1/xdaforums huggingface dataset:
[Touch Viva, MDA Basic ROM Development] VICEREY:
por fin Rom Opal en Español

Buenos dias

desde esta diureccion pude conseguir el rom en español, la he probado por dos dias y ha funcionado bien, he utlizado el Hard-SPL que aparece aqui en xda-developers

saludos

http://www.megaupload.com/es/?d=6U1OY11B
[Touch Viva, MDA Basic ROM Development] A.J:
yes just came in lol

http://xdaforums.com/showthread.php?t=481895
[Touch Viva, MDA Basic ROM Development] julio829:
Buenisimo brother

Vale tio que me has sacado de un gran Lio con esta rom en SPA muchas gracias saludos.
[Touch Viva, MDA Basic ROM Development] EL_CARTERO_D97:
Al finnn

Lo esperado esperado , grax hermano por sacar esta ROMS saludos
[Touch Viva, MDA Basic ROM Development] d_olalla:
Buenas!!

Podriais decir que version de Rom es??

saludos
[Touch Viva, MDA Basic ROM Development] bcnboy:
pudes subir esta link otravez esta desactivado.

bcnboy
[Android TV General] dqtingler:
i have an old android tv (safaricom big box the first one) and i was wondering if there is anything i can do to make it work.
[Android TV General] Sabaab2:
were you able to upgrade?
[Honor View 10 Questions & Answers] PowerHero:
hi all!

this device became old and already goy it's last update emui 10 in 2019 .but readinf in some websites like huaweicentral that it will get emui 12 update as other old devices such huawei mate 10 pro and p 20 pro.first i thought it's just a rumour butt since the mate 10 pro got the emui 12 update recently, i hope that honor v10 also will be updaed since it has the same processor and launch year as mate 10 pro.

wondering if someone got the update or any official information if it will be updated.
[Honor View 10 Questions & Answers] redsnc:
any news?
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
I'm NOT a gapps user so I will NOT be participating in this thread. I'm not supporting or answering any gapps project questions.

This thread is for users who want/need to run gapps with 19.1 on msm8916 tablet devices like SM-T35x, SM-T550, SM-T560NU and SM-P550.

I opened this thread as a courtesy for users who want/need gapps.

At last count there were 5 gapps projects and they are in various states of "working" wrt to 19.1. It's your responsibility to put in some hours of research to find out what gapps works for you.

All I can say is that some testers report that NikGapps 12.1L arm64 core (May 1, 2022) work. Despite the arm64 name, that version WILL work on msm8916. Your mileage may vary.

https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-SL/01-May-2022/
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
Reserved #2
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
Reserved #3
[Samsung Galaxy Tab A series Questions & Answers] doctorsk:
I installed retiredtab's Lineage 19.1 on my P550. I then tried to install various GApps to see which was best (doing a clean install of lineage and then the Gapps files each time). Here's what I found:

1. Could not find any OpenGapps 12.1 to run on ARM

2. FlameGapps did not install (error: must be ARM64).

3. MindTheGapps works but seemed to really slow the P550.

4. NikGapps ARM64 Core works okay. I tried the other larger NikGapps (Basic, Omni, Stock & Full) while they installed okay the functions did not seem to be present. For example the Lineage Calendar did not get replaced by the Google calendar, Chrome did not replace Browser, etc. Perhaps they are ARM64 versions that do not run on ARM devices.

5. BiTGApps-arm-12.1.0-v1.4_signed.zip was the best I found. The first time I loaded it, the Google Play Store always showed 'Paused' but I reinstalled it (wipe everything, format, then load Lineage and BitGApps zip files together) and everything worked fine. Quite happy with the this setup !!
[Samsung Galaxy Tab A series Questions & Answers] t_sg7:
What happens if you dont install gapps?
[Samsung Galaxy Tab A series Questions & Answers] SuaveCanadian:
Then you won't have access to the Google apps and services.

Some things you can access with other apps (like checking your Gmail in another client).
[Samsung Galaxy Tab A series Questions & Answers] SuaveCanadian:
It has been some time since anyone has posted here, but I just installed this ROM yesterday and wanted to share my experience.

Based on doctorsk's recommendation, I used BiTGApps Core (current version is v2.3) which I installed at the same time as the ROM and it worked nicely. I found the initial Google account setup felt very laggy and the device took some time to respond at each step. But once it was all done and rebooted the tablet all was good.

I also found out that BiTGApps has addons which allows you to flash common Google apps (Gmail, Maps, Gboard, etc) along with the GApps package to pre-install these and have them overwrite the Lineage default apps. I flashed a handful of these add-on apps which also work well.
[Samsung Galaxy Tab A series Questions & Answers] koylum:
hello masters. I have an SM-P550 tablet. android 5.0.2 version. I can't install any new applications, it says it's not supported. I installed twrp and tablet reverse touch worked. I had to downgrade again to the old version. I installed lineage-19.1-20230413-UNOFFICIAL-gt510wifi.zip and the reverse touch continued. Please help me which programs should I install? respects.
[Samsung Galaxy Tab A series Questions & Answers] koylum:
Hello . I am installing twrp on my sm-p550 tablet, touch reverse works. Left works when clicking right, right works when clicking left. what should I do. Help please.
[Samsung Galaxy Tab A series Questions & Answers] koylum:
help please
[Samsung Galaxy Tab A series Questions & Answers] koylum:
Hello master. I have an sm-p550 tablet, I am installing twrp and the touch screen works in reverse. I tried a few twrp ones, same thing. Which one is compatible or how can I solve it, please help.
[Samsung Galaxy Tab A series Questions & Answers] TheIrmoGuy:
I can't see the image you posted but hope I am answering your question. I recently installed lineage 21 on my Pixel 3 and a few of the apps gave the message "App not installed as app isn't compatible with your phone." My solution was to sideload it from my computer.

You probably already have Developer mode turned on and USB debugging enabled. If not, re-enable them.

Download the apk to your computer.

From a terminal (I'm using Linux Bash but PowerShell or Command should work) run the following

adb install --bypass-low-target-sdk-block YourAppName.apk

Hope that helps.
[Samsung Galaxy Tab A series Questions & Answers] koylum:
Hello . I installed ALPHA LineageOS 19.1 [SM-P550] 12 November 2023 for [UNOFFICIAL][ROM]Galaxy Tab A on sm-p550 tablet, I installed a few gapps, it installs without any problems, but the tablet shuts down at startup and does not turn on, can you please help.
[Samsung Galaxy Tab A series Questions & Answers] doctorsk:
Can't comment on that version of Lineage, but I installed retiredtab's Lineage 20.0 20240410 and BiTGApps Core 13.0 v3.3 (see #7 SuaveCanadian above) last week on my P550. It worked first time and works well.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen:
Thanks for making this! So far I haven't found any other issues than the ones you have listed. Stability so far is pretty solid too. Had no idea a12 had a taskbar until today, I quite like it.

One thing, the twrp you have listed does not seem to work by default, as the install script thinks its a different device. I stuck with using nubianprince's build and it worked fine. If people do the research they're supposed to though they can probably noodle around that 😆.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I like the taskbar, but disabling it is a FAQ in many 19.1 threads.

Oops, that's a cut and paste error. I put the T357 TWRP in T350 thread and vice versa. Thanks I have fixed that now. That's what I get for announcing 7 (yes, seven) 19.1 roms in a 24 hour span.

Yes, my FAQ now correctly points to @nubianprince's TWRP build. I've been using that one as well. It works so I haven't bothered to make an updated version. It's the same build that I recommended in my 18.1 FAQ as well.

Thanks for catching my cut and paste TWRP error and glad you find the 19.1 build working well so far.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen:
Holy crap! 7?!

You have been very busy.

Also I don't know if this was you or if this was the lineage team, but thank you to whoever made the lowest android setting brightness actually be 1 on the soc lcd block instead of 5.

(I swear there is a name for when a device is mounted like that but I can't remember, eg /sys/devices/soc.0/1a00000.qcom,mdss_mdp/qcom,mdss_fb_primary.132/leds/lcd-backlight/brightness is the hardware brightness value I think)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] John007778:
Just saw it, will flash and will reply with an update later
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] John007778:
There are definitely bugs but the name says it but it booted
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] uOySsElNu:
Why is the file size displayed as 558.8MB on the download page, but only 533MB when it is actually downloaded? Is this normal?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen:
Yes it is. Source forge is funky. I am not sure if they somehow calculate the file size differently, or store it different. I think androidfilehost.com does this too. If you want to check it, click the (i) on the right side of the file on source forge to get some checksums.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Do "man ls" and you know why.

gt58wifi:/sdcard $ ls -alh lineage-19.1-20220809-UNOFFICIAL-gt58wifi.zip
-rw-rw---- 1 root everybody 533M 2022-08-09 18:00 lineage-19.1-20220809-UNOFFICIAL-gt58wifi.zip
gt58wifi:/sdcard $ ls -al lineage-19.1-20220809-UNOFFICIAL-gt58wifi.zip
-rw-rw---- 1 root everybody 558839729 2022-08-09 18:00 lineage-19.1-20220809-UNOFFICIAL-gt58wifi.zip
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
The above is the correct answer. Each time I upload a file, I check the sha1sum on my local drive to make sure it matches with the uploaded sha1sum. While sha1sum takes longer than md5, it's more "tamper" resistant.

The build process also includes a sha256sum file, but based on other rom download stats, very few people download that sha256sum file to check the integrity of the download. And yes, doing a sha256sum takes longest of the three.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Wikdclown:
To anyone wondering how this performs compared to the 18 build, it runs just as good. So dont let the alpha scare you off. I have been using for 3 days now and haven't encountered any issues.

Thank you for your continued work on these ROMS.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] John007778:
tried turning it on today and it's bootlooping, will try to send the log
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] davepot04:
my tab boot looped when i was using ur other custom lineage 18.1 rom, and when i tried to re-flash using this new rom it is still boot looping, what do you think the problem is??
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] zpunout:
Tested dirty flash update from your last LineageOS 18.1 build to your 19.1 build on a T355Y device.

Confirmed working.

F-Droid will lose privileged extension and Aurora services will be gone though, but I easily re-installed via adb root.

Root manager (Lygisk) is also lost but is easily re-installable via TWRP 3.5.2_9-0 recovery. Now confirmed working with Lygisk version 25.1

In Aurora Store, I reviewed the blacklist because upgrading to Android 12 has a few extra bits and pieces which are sometimes "updatable" via Google Play Store but I didn't want to be interfered with during automatic app updates.

Nova launcher required permission confirmation again for notification badges and my custom keyboards needed permissions again too, so maybe other apps with permission requests might need to be granted again.

Thanks for supporting this device. I don't really use it for much other than as an occasional ebook reader, but it is fun to show friends that it is running Android 11 (now 12) when they see it on the coffee table and that old devices can have an extended life.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] psuryatej:
Hi @retiredtab

First of all, thanks for all your help and hardwork in keeping Galaxy Tab A devices alive.

I am trying to build your sources to start development for my SM-P555 device and following the instructions detailed in your https://github.com/retiredtab/LineageOS-build-manifests/blob/main/191-build-instructions.txt

While executing https://github.com/retiredtab/LineageOS-build-manifests/blob/main/191-build-instructions.txt#L43, I am hitting this prompt and seeking your advice on what needs to be done.

View attachment 5705753

Many thanks!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Please start a new thread called "How to build 19.1 for SM-P555" in the Q&A subforum.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-19.1-20220911-UNOFFICIAL-gt58wifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

19.1 has been my daily driver since March 2022.

Sept 11, 2022 release notes

1. Sept 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-09

2. Switched to different timekeep repo that works with Android 12 and up.

3. Whatever LineageOS changed since Aug 5 patches. About 9,500 files had to be recompiled.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] OliverLew:
Just here to say thank you, @retiredtab. Installed it and it's working quite well.

Only issue found so far is failing to split windows under portrait mode, but that's hardly useful since this device is too slow to do that much multitasking.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-19.1-20221006-UNOFFICIAL-gt58wifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

19.1 has been my daily driver since March 2022.

Oct 6, 2022 release notes

1. Oct 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-10

2. Whatever LineageOS changed since Sept 5 patches. About 7,200 files had to be recompiled.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] kyle2570:
Very smooth, faster than 17.1.

Flashed rom then mindtheapos, cleared cach, did not delete or format. Apps and layout almost the same as before.

Life for T350 is extended for few more years.

Thanks !
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] zpunout:
Been testing GPS. I've noticed it worked for awhile then functionality breaks. I got it working again after a reboot once, but now that doesn't seem to get it working anymore. I'll try to get a logcat hopefully tonight and upload it here in case it is helpful to anyone.

The device is a T-355Y
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
My T357W has 209 hours uptime and my T350 has 188 hours uptime. Both work with GPStest and show correct time/date/location. It takes a while to get the fix, but it does work.

In order to get best gps fix, go near window or outside.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] zpunout:
On average, GPS fix takes about 30 seconds to a minute when it does work. The tablet has been used in the car the past week. This afternoon, GPS fix worked again in about 30 seconds after the tablet sitting idle for 8 hours, but in the morning it couldn't get a fix for the entire one hour journey. I'll try to replicate the issue while collecting a logcat at home tonight and see if there is anything interesting to look at. It might be an issue unique to the T355Y.

[edit: Ok, seems gps gets problems after I attempt to pair the Bluetooth to the car sound system (which I'm not having success neither, but that's a separate topic). To get this logcat, I brought the tab back inside the house after the problem obtaining a fix outside in the car for several minutes, started logcat then toggled location off then back on. I searched for "gps" and found

10-24 19:01:28.005 407 407 E LocSvc_eng: loc_eng_agps_init: log_eng state error: agps instance already initialized.

Worth noting, is that about 1 minute after this logcat, the gps got a fix again despite the tab being indoors while connected to the PC.

Is there anything else I could run a search on in the logcat? ]
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I can bluetooth pair both my T350 and T357 and have gps running at the same time with no problems.

As for the error messages, I would search (case insensitive) for gnss, dlopen, fatal signal. It's not uncommon for me to look through 1000s', sometimes 10,000s of logcat messages to find a relevant clue. In addition, sometimes an "error" message doesn't mean it's really an error. I've been reading logcats for over 2 years now and examined 100,000s lines and it's still a mystery to me.

Once I find an interesting message, I find that web searches are generally useless as most are geared towards Windows, then linux distros and rarely Android.

Tip. If you adb logcat to a file, use an editor that can read/decode the messages with a color code so that error messages are in red to make it easier to spot.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] zpunout:
Thanks for the tips on what to look for in the logcats. It'll probably be a couple of weeks before I get some time for those logcats though.

I'm not too worried about the Bluetooth issue because the car radio causes the same problem with some other devices.

Meanwhile, I noticed that if I keep the tablet switched on when not in use, the gps function seems to be reliable when I need it, as opposed to switching the tablet on then starting a navigation app such as Waze soon afterwards.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] yxo 6o6uka:
Can someone share a SM-T350 *PIT* file or a pointer to? TIA
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Are you asking for this partition?

--- Entry #29 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: MSM8974.pit
FOTA Filename:

or a listing of the partitions via

$ heimdall print-pit

# or

$ heimdall download-pit
Action: download-pit
Arguments: --output <filename> [--verbose] [--no-reboot] [--stdout-errors]
[--usb-log-level <none/error/warning/debug>]
Description: Downloads the connected device's PIT file to the specified
output file.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] yxo 6o6uka:
Appreciate the quick reply!

I'm looking for a valid PIT file to wipe the flash and repartition w/Odin.

The tab is acting up badly after years of experiments. I made a PIT on the device with a DD command in terminal, attached. But getting "Re-partitioning failed" in odin, so doubt that PIT. If you could post a valid PIT file or perhaps confirm the attached is correct, would be great. Thx!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
This is what I have from heimdall download-pit on linux. I don't run Windows. My pit is 8K filesize.

$ sha1sum 350-pit.bin
53d29b666a282d1fcb8d61041f9de863694ddc8d 350.pit
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] yxo 6o6uka:
This gets me closer to resuscitating the device, thanks again!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-19.1-20221111-UNOFFICIAL-gt58wifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

Nov 11, 2022 release notes

1. Nov 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-11

2. Whatever LineageOS changed since Oct 5 patches. About 5,400 files had to be recompiled.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-19.1-20221209-UNOFFICIAL-gt58wifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

19.1 has been my daily driver since March 2022.

Dec 9, 2022 release notes

1. Dec 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-12

2. Whatever LineageOS changed since Nov 5 patches. About 4,700 files had to be recompiled.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] tikanorcun:
Hey @retiredtab, Thanks for all your hard work. I have a problem with lineageos recovery. When I click "reboot system now" it doesn't reboot to system, always boots into the recovery. Is there anything you might think a cause about what happens to that issue? Thanks your for your concern and contributions.

Edit: I also have tried to power off and power on but still goes to recovery mode.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I provided recovery.img as a courtesy for those who wanted to flash some gapps projects in case TWRP didn't work. I personally use TWRP and I suggest you do the same as per FAQ 5.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] tikanorcun:
Thanks for your reply! I have read the post. However I have two problems. First one is my usb port is broken so I am not able to flash twrp recovery img via download mode. The second one is linked to that issue: due to broken usb port I had to find a flashable recovery zip file. Tried to find a way how to create a flashable zip file, tried several solutions but none of them helped ( btw im not a developer : ) ). The only way may be lead to solution to get fixed the port but the tablet is old, so it doesn't make sense to me to pay and make it fixed.

Thank you for your concern, again. It was a such delicate act.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lividhen:
I think the twrp app can flash recovery while the system is live if you have root access.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
New build called lineage-19.1-20230107-UNOFFICIAL-gt58wifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

19.1 has been my daily driver since March 2022.

Jan 7, 2023 release notes

1. Jan 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-01

2. Whatever LineageOS changed since Dec 5 patches. About 4,400 files had to be recompiled.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Techguy777:
Which mindthegapps? I just flashed latest 12.1 and it doesn't show anything. If you could help me out I would appreciate it.