yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Note 20 Ultra Themes, Apps, and Mod] davidstjohn1:
I loaded this on my Note 20 ultra and the image quality is bad right now. Very blurry and fuzzy. I tried every option and it's the same. I'm sure it will be worked on.
[Samsung Galaxy Note 20 Ultra Themes, Apps, and Mod] Poliarinis_eziukas:
Gcam without selfie camera... why bother ... :D
[Samsung Galaxy Note 20 Ultra Themes, Apps, and Mod] VioNeo:
I'm in
[Samsung Galaxy Note 20 Ultra Themes, Apps, and Mod] JohnJoseph34:
any updates?
[Samsung Galaxy Note 20 Ultra Themes, Apps, and Mod] ca12bon:
As an FYI, there was a GCAM that worked very well with the Snapdragon N20U. I've since sold my note but I'm sure it won't be difficult to find
[LG V30 Questions & Answers] stifbaker7:
hello so i got a refurbished us998 on android 7.1 i couldnt get it to update vie ota so i flashed oreo firmware with lgup after that i unlocked bootloader and installed twrp all good but after that i wanted to update to pie so i can install android 10 custom roms i flashed the pie kdz and i got stuck at lg logo couldn't boot then i tried with flashable zip same i tried flashing back 7.1 then to pie that didnt work then i flashed all the oreo zip from build 820e to 820h as mentioned in a thread and then pie

that didnt work as well so i tried to flash lineage os 16 or and other pie roms same thing they all dont boot up and got stuck on logo so is there any other ways to try that would be appreciated
[LG V30 Questions & Answers] ChazzMatt:
In the US998 Pie KDZ thread, there's several methods to get to Pie. Look at post #2 and post #6. It sounds like you tried some of those, but read again carefully. Method #4 in post #6 seems to work for almost everyone.

You can't flash LOS-16 immediately after failing to update to Pie. Enough Pie infected the partitions that it will not work. So, if you want LOS-16 you have to flash back to Oreo first. LOS-16 needs Oreo blobs (drivers).
[LG V30 Questions & Answers] stifbaker7:
thanks i will try method 4 but i already flashed back to oreo and los 16 still cant boot and when i boot back to twrp i find it that nth is installed and everything is wiped out 0mb its like not detecting internal storage or smth maybe partition issue like u said

edit: so i tried method 4 and it worked thanks a lot hopefully i can install adnroid 10 custom roms now
[Huawei Mate 10  Questions & Answers] :
Hello, I come to ask you for help, my problem is the following.

Some time ago I bought a second-hand mate 10 pro and unfortunately they blocked it, so I took it to change the IMEI reported since the one that sold me did not give me a solution, so they downgraded with android 8.0 and when entering The system model came out as an unknown model, so since that day I tried to update at least to android 9.0 but I could not find a firmware that works, yesterday was where I found an android 9.0 firmware from my operator that I had before my cell phone before the Blocked, which is the next name that Huawei Mate 10 Pro had, of course the BLA-L09C 9.0.0.159 (C25E5R1P11T8) Firmware 9.0.0 r3 EMUI9.0.0 05014YPA

(I can't put the link, I'm already new to the forum)

and it worked correctly for me, because that moment I decided to hardreset the device to make it a clean installation, then I was surprised, until the initial emui configuration appeared and from that menu it does not pass and returns to the starting point in a loop (I accept everything but at the end it returns to the beginning to select the language), could you give me help to solve it.

THANK YOU VERY MUCH IN ADVANCE.
[Samsung Galaxy Note 20 Ultra Questions & Answers] rsacipher:
My note 20 Ultra on T-Mobile seems to have intermittent data speeds and or unstable connections regardless whether or not it's on WiFi (6) Verizon Fios 1GB or 5G.

If I'm on WiFi I would need to turn it off and back on to get respectable speeds, on 5G I'm getting slower speeds than my Note 10 with 4G.

Is anyone else having this issue?
[Samsung Galaxy Note 20 Ultra Questions & Answers] JCordero31:
get it replace
[Samsung Galaxy Note 20 Ultra Questions & Answers] S188:
Same issue here on Wifi unfortunately :\
[Samsung Galaxy Note 20 Ultra Questions & Answers] marctronixx:
no such issues on ultra 20 5G 512 unlocked on tmo in LA.

agree, get it replaced. obviously thats not how the phone should work.
[Samsung Galaxy Note 20 Ultra Questions & Answers] ggrant3876:
Just curious, did you set the phone up from scratch or did you restore a backup from another phone? If you restored data from another phone I'd do a FDR before exchanging the phone.
[Samsung Galaxy Note 20 Ultra Questions & Answers] blackhawk:
Try a network reset, then clear system cache on the boot menu.

Ask carrier for a reset on their side.

Clear sim toolkit data, double check configuration

if no joy replace sim card.
[Samsung Galaxy Note 20 Ultra Questions & Answers] rsacipher:
I set it up from scratch.
[Samsung Galaxy Note 20 Ultra Questions & Answers] rsacipher:
I'll give this a try.
[Samsung Galaxy Note 20 Ultra Questions & Answers] blackhawk:
More than likely a settings, software or firmware issue rather than hardwire.

It possible the base load got corrupted; if so a hard reset would not fix it.

It's irritating to send one back only to have the same issue crop up on the replacement and find out it's a settings issue that is easy to correct.

Been there, done that.

Samsung tech support is just about useless, but do document the problem with them.

Keep looking and send it back for factory service as the last option.

Samsung Experience centers can possibly find it or reflash it. They have diagnostic tools. They may do good... good luck.

Make sure the issue isn't the case... just saying.
[Samsung Galaxy Note 20 Ultra Questions & Answers] Compusmurf:
I had issues where my unlocked would "unregister" itself with TMobile forcing me to reboot. I chatted with their online folks and they suggested I replace my "over 7 yr old sim".

knock on wood, after that the issue went away.

My wifi has been totally solid. I pay for a 500/500 plan with Frontier and I get 512/509 consistently on wifi. Little slower than wired but that's to be expected.
[Samsung Galaxy Note 20 Ultra Questions & Answers] blackhawk:
You should handle a sim like a stick of ram.

Few people handle them properly and this can cause a lot of avoidable trouble.

ESD easily can damage them.

>If you can see, feel or hear a static charge it's already enough to cause damage. ESD input protection is limited at best.

>Do not touch contacts.

>Do earth ground yourself before handling; a wrist strap and earth grounded ESD mat are best but simple touching an earth ground after sitting down can work.

>Best to do with humidity above 50%.

Almost all sim card failure are the direct result of ESD damage... it can take years to manifest itself.

Damage can be accumulative or the result of one exposure. Failure afterwhich is completely unpredictable.

Learn to it yourself if you want it done right...
[Samsung Galaxy Note 20 Ultra Questions & Answers] Compusmurf:
AFAIK, I've never touched the contacts. Just moved from phone to phone over the years. Never replaced it the whole time.

I didn't have any spares either.

Guy at local store took one look and said it was well past it's date and just swapped it out for me no charge.

As far as humidity. HA. I live in Florida. Between heat, mosquitos and sand, humidity is one of those things we have an over abundance of. :)

Guy at store suggested replacing every 3 years or so. Said it's why they "force a sim" in the package with every new phone they ship. (I always just tossed them) Going forward, maybe I'll just change it out the next time. (I know I can do it online, just never bothered)
[Samsung Galaxy Note 20 Ultra Questions & Answers] blackhawk:
That's old. No clue if they upgrade protocols, code but it would seem likely.

At 90% humidity a static charge doesn't last long and is harder to form in the first place. At 10% it's everywhere.

Nothing worse than the AT&T guy walking across carpet in leather shoes before they handle a sim card in the nice dry air conditioner store.

In 10 years I only ever saw one person at a phone store do it the correct way... no joke.
[Samsung Galaxy Note 20 Ultra Questions & Answers] Compusmurf:
Last time I was in an area with 10% humidity, people were shooting at me. ;)
[Samsung Galaxy Note 20 Ultra Questions & Answers] blackhawk:
I've handled a lot of ram sticks and sim cards... never had one fail. Those sim and ram modules are 100% when they are shipped... what's that tell you?

A little care saves a lot of needless trouble shooting.
[Samsung Galaxy Note 20 Ultra Questions & Answers] CyberWolf575:
I have spoken to the T-Mobile reps, and it looks like it's a known issue with the S20 Ultra 5G models, and looks like it's been passed on to the Note 20 5G models. It has specifically to do with the 5G models. The non 5G models work just fine. They said they are in contact with Samsung to get it fixed, but it's not something that you will see fixed just by replacing the phone. I am on my #3 Note 20 Ultra, and still same issue with T-Mobile. I was on Verizon 2 weeks ago ( I literally just switched to T-Mobile), and when I had Verzion, I had 0 issues.
[Samsung Galaxy Note 20 Ultra Questions & Answers] rsacipher:
I turned off 5G and am getting much faster data speeds over LTE and the connection seems more reliable.

I'm not a fan of having to reinstall everything with a replacement and hopefully they have a software update that fixes it.
[Samsung Galaxy Note 20 Ultra Questions & Answers] fabienpascal:
I have exactly the same issue. Everything is up to date and I have two massive Asus Rapture AX-11000 routers in mesh wired to a 2 Gbps fiber connection. And I am in Singapore, we have 5G.

Unfortunately my speed test ranges from great speed to miserable speeds:

[IMG="SpeedTests"]https://i.ibb.co/8YvMtK5/speeds.jpg[/IMG]
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
NOTE: There is no S-pen support. If you need S-pen, DO NOT USE THIS ROM.

I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.

Try this build at your own risk. It's likely to have bugs and is EXPERIMENTAL as it is a work in progress. It boots and seems to work fine on my SM-P550, but I have only tested it for 24 hours. Problems will likley surface later?

I'm posting the rom to get more testers and help fixing the bugs.

BACKUP YOUR FILES and have a copy of your working image BEFORE trying my build.

What works.

1. bluetooth

2. wifi

3. brightness

4. external audio

5. GPS

6. audio through headphone jack

7. camera

8. touchscreen X-axis works properly

9. Google play store - use pico apps

10. Flip flap smart cover

Note: first initial boot takes a bit longer, roughly 36 right to left circle animations or 1 minute 40 seconds without gapps. After that, it boots quicker.

Known problems.

1. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.

2. Home screen text may look fuzzy.

Text on home screen looks funny/fuzzy. This only seems to affect the home screen and nowhere else. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.

Problem is with stock trebuchet launcher and/or its fonts. I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future lineageos update could resolve the problem?

3. Lineageos FM Radio app does not work.

FM Radio also requires the tablet to have the LTE chipset which the S550 lacks.

Thanks/Credits

Thanks to @virsys for the SM-T550 build. The T550 is essentially the same as the P550, but without the S-pen support. I used his github repos at

https://github.com/VirsysElectron

The T550 code at https://github.com/Galaxy-MSM8916 compiles without errors, but crashes at the boot logo.

Virsys repos no longer work for 16.0 as of Oct 2020. I switched to https://github.com/aala27. @aala27 was nice enough to share his work so my build is based on his 17.1 with some minor changes.

Thanks to @nubianprince and @lividhen99 for ideas and suggestions on fixing the incorrect lcd density issue.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
TODO

1. Clean up the roomservice.xml so it's easier to read. Done

2. Try lineageos recovery image to see if X-axis is mapped correctly.

3. Fix huge screen problem at bootup.

4. Documentation for myself to help with possible future 17.1 and 18.0 builds. Done.

5. Look at possibility of making a P550 specific TWRP. Tried, too hard to do atm.

6. Look at possibility of adding S-pen support IF there is existing repo and working code. Tried. Too hard to do.

7. The proper code name of the P550 is gt5note10wifi. I may change around the directory names and repos to reflect that. Done.

8. Fork or mirror virsys repos in case they are deleted. Done.

9. Build userdebug release instead of eng release. Eng only used for testing. Done

10. Look at ifdef code to see if one rom image can work for both P550 and T550. I now keep P550 and T550 on separate hard drives.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Dec 14, 2021 release notes

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

2. Whatever LiineageOS changed since last November release (about 4,400 files had to be recompiled).

Nov 8, 2021 release notes

1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318647

2. Whatever LiineageOS changed since last October release (about 5,100 files had to be recompiled).

Oct 10, 2021 release notes

1. Oct 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317410

2. Whatever LiineageOS changed since last Sept release (about 4,200 files had to be recompiled).

Sept 17, 2021 release notes

1. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/316083

2. Whatever LiineageOS changed since last August release (about 49,500 files had to be recompiled).

Aug 7, 2021 release notes

1. August 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/314572

2. Whatever LiineageOS changed since last July release (about 5000 files had to be recompiled).

July 12, 2021 release notes

1. July 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/313448

2. Whatever LiineageOS changed since last June release (about 4500 files had to be recompiled).

June 15, 2021 release notes

1. June 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/312240

2. Whatever LiineageOS changed since last May release.

May 9, 2021 release notes

1. May 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309564

2. Whatever LiineageOS changed since last April release.

April 11, 2021 release notes

1. April 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307454

2. Whatever LiineageOS changed since last March release. Nearly 59,000 out of the 70,000 files had to be recompiled due to the last set of changes.

March 7, 2021 release notes

1. Mar 5 security patches.

2. Whatever LiineageOS changed since last February release.

3. audio over bluetooth fixed. I had to use the audio.hardware@5.0 hal.

Feb 15, 2021 release notes

1. Feb 5 security patches

2. Whatever LiineageOS changed since last January release.

Jan 14, 2021 release

- Jan 5 security patches

- based code on aala27 repos since virsys 17.1 repo never worked for me

- initial BETA 17.1 release, 16.0 doesn't boot properly anymore

Sept 23 release

- Sept 5 security patches

- added onscreen navigation buttons

Sept 10 beta release

- initial 16.0 release for testing and help fixing bugs

- CPU and GPU overclocked to 1.6Ghz and 650 respectively

- based on virsys SM-T550 github repos

- fixed X-axis inverted for P550

- incoporates Aug 5, 2020 security update. Sept 5 patches wasn't available when I built the rom.

- Sept 10 beta release will be removed once I get all the bugs fixed
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] MrRoy3:
Thanks OP, works great so far, gave a new life to my device
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] damismtz:
installed via adb or by odin?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Severongas:
OMG Thanks a lot for this OP. I do use S-Pen however my device reboots randomly and frequently while on stock rom rendering it almost unusable, I am more than willing to sacrifice the pen in favor of stability. I will test it out and provide any feedback or address bugs if any.

Once again thanks for this, P550 seemed like a forgotten device. :):)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
If your tablet operated perfectly when it was brand new with no random reboots on stock rom, it could be your battery is dying if you used it heavily for almost 4 to 5 years?

When the battery degrades, it can't provide enough "juice" or amps when needed for heavy CPU tasks and this could cause it to randomly reboot. Alternatively, sometimes cleaning and reseating the battery connector might help as well?

See

https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+A+9.7++Battery+Replacement/88890
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Severongas:
That's the thing, other than it being 3-4 years old now it was mainly used by my son to browse YouTube, not even playing. So it's use was very low.

Recalling, I did had it running on 6.0.1 stock, then updated to Fenix Rom and some time later upgraded to 7.1.1 stock using Odin, that is when this started happening.

Update on your modded Rom, it has been running flawlessly since yesterday, only issue was when after flashing GApps Pixel Launcher crashed 5-10 secs after opening app drawer, however this was later fixed after updating to latest version of all apps.

Not a single random reboot and I can finally start using it once again! Thanks a lot for your work on this.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
If youtube is the primary use, check out youtube vanced (no ads) and microg.

With the combo above, you do NOT need to install gapps of any kind. That way, your tablet will use less memory and less software.

https://vanced.app/

https://microg.org/

For pixel launcher, you can find it at fdroid.org instead of play store.

https://f-droid.org/en/packages/amirz.rootless.nexuslauncher/

The above is how I have one tablet setup. It works fine for me, but I can't guarantee that it will meet your requirements.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Sept 23 build up. See post #4 for changes.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] CW_texashack:
Having an issue flashing

i left it running for an hour and a half after flash and it keep just sitting on the boot animation. Restarted and same outcome. I tried flashing both ways, however i can't get it to boot for some reason. I did wipe data before i flashed, could that be the issue?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
If you are using twrp to flash, I suggest wipe, advanced wipe, check dalvik/art cache, data, internal storage, cache and system. Then install rom zip (both work on my P550 tablet). After install rom zip, then use twrp to wipe, format data.

If using lineageos recovery, click factory reset, choose wipe data/factory reset, then wipe cache, then wipe system. Do each wipe twice. Then adb sideload the rom.

PS. I'm using my P550 to view your message with the latest Sept 23 rom so I know it boots on mine. I test all my roms that I upload to make sure it boots on my tablet and for the functionality that I put in post #1. I never shared untested roms.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] CW_texashack:
Thank you, I'll try this out.

I wasn't trying to say it was your fault or anything, I'm 99.9% sure it's my fault. I just thought maybe you had an idea what may be causing it to stick for me. It's obvious it's working fine as there's plenty other replies saying it works as well.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] aala27:
Hey [MENTION=8726605]retiredtab[/MENTION],

I was working on getting RR rom on this tab and managed to get the S-Pen to work in portrait mode a few months ago (In landscape mode, I believe the axes are swapped and inverted which I have not been able to fix). I have just uploaded the kernel source that I was using to get this to work, which might be of interest to you.

https://github.com/aala27/samsung_P550_Kernel.git

I have used the following defconfig files in BoardConfig.mk:

TARGET_KERNEL_VARIANT_CONFIG := p550_defconfig
TARGET_KERNEL_CONFIG := common_defconfig
TARGET_KERNEL_SELINUX_CONFIG := selinux_p550_defconfig
TARGET_KERNEL_SELINUX_LOG_CONFIG := selinux_log_defconfig

Hope this helps.

Also note I am working on getting RR 8 (Android 10) on this tab. Managed to get it to boot but I am unable to get the audio to work from the loudspeakers
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
[MENTION=7071452]aala27[/MENTION], thanks for your post and sharing your code. Can you post your RR s-pen rom somewhere so I can download it and test it with the s-pen. I never used it on this tablet and want to see how it works.

I will download your code and have a look. Where do you get the s-pen code?

I tried compiling virsys Android 10 code, but I get stuck at a bootloop. I have been trying for weeks to figure out the problem, but no success so far. I know he has a working build dated June 2020, but his github repo only goes to March 2020 so it might not be updated with all the necesssary fixes?

If you want help fixing the audio on your 10 build, can you upload the rom so I can look at logcats?

Thanks.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
[MENTION=7071452]aala27[/MENTION], I was able to build your kernel and get the same results as you. S-pen works in portrait mode, but not in landscape.

Do you know which procedure or module draws the s-pen pointer?

Using adb shell and

getevent -l | grep event3,

I can see the coordinates being reported by the s-pen. They all look correct to me. The top left hand corner is 0,0 and the bottom right hand corner is 768, 1024. So top left hand corner is always 0,0 in portrait and landscape. Bottom right is always 768, 1024 in portrait and landscape.

gt510wifi:/ $ getevent -lp /dev/input/event3
add device 1: /dev/input/event3
name: "sec_e-pen"
events:
KEY (0001): KEY_BACK KEY_UNKNOWN 00fe BTN_DIGI*
BTN_TOOL_RUBBER BTN_TOUCH BTN_STYLUS KEY_ALS_TOGGLE
ABS (0003): ABS_X : value 1871, min 0, max 14745, fuzz 4, flat 0, resolution 0
ABS_Y : value 13381, min 0, max 19660, fuzz 4, flat 0, resolution 0
ABS_PRESSURE : value 0, min 0, max 2047, fuzz 0, flat 0, resolution 0
ABS_DISTANCE : value 6, min 0, max 1024, fuzz 0, flat 0, resolution 0
SW (0005): 0013*
input props:
<none>[/SIZE]

P550 screen resolution is 1024 / 768 = 1.333 aspect ratio. 19660/14745 = 1.333. So "sec_e-pen" has correct resolution.

PS. The git file you uploaded had link which caused the compiler to stop. You had

dt-bindings -> /home/ali/rr9/kernel/samsung/msm8916/include/dt-bindings

Luckily, it was an easy fix for me to recode the link.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] aala27:
This was done a while ago, however, I do recall finding out that the S-Pen uses wacom drivers. The driver is found in /drivers/input/touchscreen/wacom.

I have uploaded the RR Pie rom at the link below:

https://drive.google.com/file/d/1zQuvVOr_8eq0Q3vU-UagURcU-8t6sBUO/view?usp=sharing

I'll upload the RR 10 rom soon.

Thanks for the error. I have now corrected that.