yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10e Questions & Answers] TheVergs:
Last week my Galaxy s10e were exposed to salt water, right after it I did all the procedures recommended, and the phone was working fine, only problem was the camera that wasn't working. I went to a technical support store and they opened and washed the internal parts of the phone with

ethyl alcohol, then tested the camera and it didint work. After that, they factory reset and still nothing. At last, they replaced with new cameras, and after testing, still nothing! I was told that the problem is in the motherboard, and something about the sensors malfunctioning, and the app crashes because it's an defensive action to prevent overheating (since camera uses a lot of ram).

When I open any Camera app, it says "Warning: camera error". When I try to turn the flaslight on, it says the light is being used by another app. Altough, when I opened Instagram, the selfie camera automatically opens (before and after going to support), working fine! if I invert camera it crashes the app altough. I guess that the standard "Camera" app aways opens the rear camera at start, and because of that, I only see a black screen when trying to use the app.

I would like to know if somebody knows what could I do, maybe some system option that turns off the sensors that are disabling my camera, or to let me use only the front camera without crashing apps! I'm considering custom ROMs too, but not sure if could help me with anything.
[Samsung Galaxy S10e Questions & Answers] blackhawk:
Welcome to XDA🤗

The battery needed to be disconnected immediately.

First off RO water should have used followed by anhydrous isopropyl alcohol. Salt is readily soluble in water not as much so in ethanol.

All effected ribbon cable pulled and their connections soak in RO water and every part that the salt water touched.

Any electronic component exposed to salt water is likely toast. Salt water is insidious. If even a slight trace of it or the corrosion it caused remains the effected part will eventually fail especially switches and micro connector contacts. The mobo has conformal coating most likely which will protect it somewhat.

However all the microconnectors are at risk.

If only the cam module was exposed, replace it.

If the whole inside got it... it's likely already dead.

It's only chance is to completely purge the salt before it causes corrosion to form. Energized circuits, even just having the battery connected greatly accelerate the corrosion process... think minutes not days.

Salt water is the kiss of death to electronics...
[Samsung Galaxy S10e Questions & Answers] TheVergs:
Ohh I see, thanks for explaining! :(
[Samsung Galaxy S10e Questions & Answers] blackhawk:
You're welcome. Sorry, it's not a pretty picture.

It may last a while but don't throw too much money at it. If the mobo or display fail, time to punch out.

Even with "waterproof" phones do not submerge them especially in salt water. You need a diving enclosure for that. For limited protection on boats etc use a zip lock plastic bag... they float and it gets splashed or takes a plunge it should be ok.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] climber1872000:
Hi all,

I am currently using Shamanix_WM6_Ultimate_v2_FINAL with radio rom version 1.5407.00 and I am looking for a better radio. The data speed (even over 3G) is not that great and the reception at my house is literally 1 bar. I was wondering if anyone out there that lives in the Atlanta, GA area is using a different radio rom version that gets better results than mine. I'm on the AT&T network.

Thanks in advance!
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] nbkcu33:
I also live outside Atlanta and I find the closer I get to home the more often my calls drop. I am running the same radio version and I too would like to know if there is a better radio version for the Atlanta area. I am on AT&T as well.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Prerna:
You guys should try several Radio and see which one proves to be the most compatible with your operator there in Atlanta.

Remember, flashing the radio stack will not cause a hard reset. So it does not hurt trying.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] zachoo:
I visit the Atlanta area regularly and have exceptionally good speed and battery life with 1.54.30.10
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] leoingle:
i have been running into the same problems here in Houston since the Hurricance Ike and running the same version ya'll are. I am about to try 1.56.70.11. I will post my results later.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] climber1872000:
Thanks Zachoo! This radio rom is perfect!! I have been flashing radio stack after radio stack to try and find the best reception and battery life. I get much better reception, data transfers are quicker, and my battery life has increased by almost 30 percent!

:D
[Xiaomi Mi 11] alcahayag:
Hello. I am using MI 11 5G, it's a new phone. Just got over the weekend. We installed the WORK PROFILE for our company then everything was working fine not until when I tried to attach a file on Gmail app, the file explorer wont open. I already turned off the optimization and it showed the file explorer but won't attach the files. I went back to my personal profile, and the file explorer wont open when the optimization is off. When I turned it back on, the same thing happens on the work profile. It won't allow me to select files but on personal profile, everything is working fine.

My OS is: miui 12.5.1 Global. Thank you.

Video links:

Cannot upload:

Personal Profile says: Work Profile is Paused even if it is on:
[Samsung Galaxy Note 10+ Questions & Answers] Johneaguilar71:
Hello everyone! I am new to the family here, been reading allot of forums from many differerent places and it seems you guys really know what you are talking about, I hope... lol. I have a Samsung Note 10 Plus that is origianally a world phone so I assume it was completely unlocked. its obviouse I should of never been fooling around with the device on the devolopers side but I have now rooted my phone successfuly, but I cant make out going calls on it with any carrier, Can anyone please help me? I think I might of messed up The IMEI some how:
[Redmi Note 10 Pro] Hasan Shad:
I brought RN10P recently. I'm using USB DAC on my PC. I plug the USB DAC with an adapter on my mobile, but it is not working. If RN10P support a USB-c audio dongle, then I will buy a new USB-c audio dongle. Does it support a USB-c dongle?
[Redmi Note 10 Pro] iRet:
I've tried to use usb-c to 3.5mm mini jack from mi 11 lite.

Sadly, it didn't work for me either.
[Redmi Note 10 Pro] Hasan Shad:
then is very sad😌
[Redmi Note 10 Pro] harri2cool:
I tried the original HTC U11 USB C noise-canceling earphones on the RMN10PRO with Pixel Experience ROM. Doesn't work, although the phone recognises some audio thing is attached to it. No sound is output.
[Redmi Note 10 Pro] lovegambler:
Been using OnePlus Bullets Type-C for months, work like charm. If earphones work dongle should too 🤔
[Android Auto General] 1qazwsx4:
Hi guys, like many here I'm using aawireless and it works great (excluding problems caused by Google) however - I use poweramp exclusively for my music but the app keep randomly disappearing from android auto? Anyone else having this issue or other official AA apps disappearing without reason?
[Nexus 9 Android Development] linckandrea:
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

Important:

Official build are now available

What's working :

Boots

Wifi

Audio ( Record and Playback )

What's partially working:

Bluetooth

Video Playback

Camera

Camcorder

Flash

GPS

Nfc

What's not working :

SELinux enforcing

HWcomposer is buggy(rendering is made by gpu in order to avoid artifacts)

Instructions :

Download the latest build and gapps

Reboot to recovery

Do all wipes

Flash the latest build and gapps

Downloads :

Latest Build : LineageOS-16

Reporting Bugs

DO NOT Report bugs if you're running a custom kernel or you installed Xposed

Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)

If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)

If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log

Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

Sources

linckandrea - Repositories

Andrea Pucci. linckandrea has 46 repositories available. Follow their code on GitHub.

github.com

Credits :

LineageOS Team

if you want to offer me a coffee or anything else check this
[Nexus 9 Android Development] linckandrea:
reserved
[Nexus 9 Android Development] SirRGB:
nice, i never thought we would get another android pie attempt, Ill try soon
[Nexus 9 Android Development] SirRGB:
I just installed it and it works fine, but pls add sources. I already found them, but you should add them in your post.

and ofc thanks for all the effort you made @linckandrea
[Nexus 9 Android Development] SirRGB:
I am the first person to soft brick my N9 ig. To be fair, I installed Magisk, dirty flashed, ran undecrypted, everything not ideal circumstances, but here are ramoops as it now only boots to recovery saying "RescueParty".
[Nexus 9 Android Development] SirRGB:
cant share logs due to size limitations in xda, pastebin and hastebin. If you have a telegram acc it would make things easier.
[Nexus 9 Android Development] retiredtab:
Thanks for releasing 16.0. While I did have a bootable 16.0 back in March 2021, I couldn't fix the hwcomposer problems.

With your 16.0 build, Clash Royale completely froze and locked up after 15 minutes (roughly 5 games, each is 3 minutes long). adb logcat shows running low on memory? I can play same game on 15.1 with no problems.
[Nexus 9 Android Development] retiredtab:
After getting the logcat, I tried to start Clash Royale again, but the entire device locked up again and I get the same System UI isn't responding that I reported earlier.

5585 06-23 18:42:44.198 264 355 E ActivityManager: ANR in com.android.systemui
5586 06-23 18:42:44.198 264 355 E ActivityManager: PID: 661
5587 06-23 18:42:44.198 264 355 E ActivityManager: Reason: Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 1. Wait queue head age: 6085.9ms.)
5588 06-23 18:42:44.198 264 355 E ActivityManager: Load: 4.6 / 2.01 / 1.62
5589 06-23 18:42:44.198 264 355 E ActivityManager: CPU usage from 0ms to 22509ms later (2021-06-23 18:42:21.538 to 2021-06-23 18:42:44.047):
[Nexus 9 Android Development] retiredtab:
Here's the output of top from adb shell. BTW, there's no rush to look at this. I know you are still fine tuning your changes locally and on github. Thanks.

Tasks: 198 total, 1 running, 197 sleeping, 0 stopped, 0 zombie
Mem: 1879792k total, 1306832k used, 572960k free, 816k buffers
Swap: 786428k total, 158840k used, 627588k free, 553684k cached
[Nexus 9 Android Development] linckandrea:
source link added(i missed when created the thread but they were already present(with git history) on my github account)

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

due to broken hwc display composition is made by only the gpu

(this means that every heavily gpu apps will perform bad as the gpu does all the work)
[Nexus 9 Android Development] Isuress:
Would you say that @linckandrea 's v16 release is more up-to-date than your v15.1 release?

Obviously v16 > v15.1 but I wonder if the functionality is the same?

Having used both releases, would you say this one is more stable than your own?

Your last update for v15.1 was as of June 13, 2021.

Does this v16 update include both the security updates AND the hardware fixes in yours?

Such as improving the GPU rendering, etc?

I would assume that because it's v16, it would include all previous fixes from v15.1? Am I wrong in thinking this?

Or is the hardware decoding of video or say, YouTube; still an issue?

Also related/unrelated to these ROMs, have either of you (or other users reading) had the issues with the NEXUS9 related to crashing prior to installing any ROM; and then having those issues be resolved with the installation of this or any other ROMs? I'd like to know if this is a hardware-based or software-based issue.

If my NEXUS9 is still going to crash, I don't think it's worth my time installing any ROMs, etc.
[Nexus 9 Android Development] SirRGB:
Will there be any more development of Android 9? I am asking because your repos werent updated since June 24th and I dont know of anyone else, that is working on it...
[Nexus 9 Android Development] linckandrea:
i'm actually using a custom build of los15.1 of my nexus 9,

the hwcomposer bug is due by outdated display blobs(there's no tegra k1 device that has an oem pie build(this means that this issues will never be resolved))

so it is worth fixing the remain bugs when the performance will sucks no matter what?

probably not

and yes even on los17.1/18.1 display blobs would be the same
[Nexus 9 Android Development] SirRGB:
I currently run los16 just to try it and it runs quite nicely (only minor bugs e.g. livedisplay broken like A8, permissive selinux, ?fullscreen issue?). Ig dirty flashing was the reason it didnt work properly back then... Just wanted to note: a lot of people are using your build, so thanks for all your work.

LineageOS Statistics

stats.lineageos.org
[Nexus 9 Android Development] morse_c0de:
When i power off, the device is in some sort of sleep not true power off. I power off and there was 50% battery and when i switch it on weeks later battery is depleted. I noticed this with another rom i installed before. Any way around this ? To get a true power off. Apart from this, the rom works great.
[Nexus 9 Android Development] SirRGB:
I made an enforcing build a few months ago, but now I cant get Lineage 16.0 to build... Can someone look into it?

hastebin

I use your dt, kt and vt
[Nexus 9 Android Development] retiredtab:
I'm not an expert in compiler flags, but if I'm understanding this correctly ...

In file included from external/tinycompress/compress.c:57:
In file included from bionic/libc/include/fcntl.h:95:
bionic/libc/include/bits/fortify/fcntl.h:63:26: error: use of undeclared identifier 'O_TMPFILE'
__clang_error_if(__open_modes_useful(flags), "'open' " __open_too_few_args_error) {

it's complaining that 'O_TMPFILE' is not declared. You can bypass this by removing line 7 at

https://github.com/LineageOS/android_external_tinycompress/blob/lineage-16.0/Android.bp#L7

The "-Werror" according to

https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html

"Make all warnings into errors."

So by removing that flag, it should compile now.
[Nexus 9 Android Development] SirRGB:
Hm, I understand, but sadly it didnt work. In the end I nuked all flags and removed the out folder, but nothing changed...
[Nexus 9 Android Development] retiredtab:
Try renaming the external/tinycompress/Android.bp file to Android.bp.old as a test. That won't build that library at all then. You may also have to grep through the device/htc/flounder directory for instances of libtinycompress and comment it out.

I haven't tried to build 15.1 yet so I don't know if I will be affected by this or it's just in the 16.0 tree or it's specific to your build environment.
[Nexus 9 Android Development] linckandrea:
You used the wrong kernel branch... Pick lineageos-16...
[Nexus 9 Android Development] SirRGB:
Thanks, that worked, just needed to comment one thing I dont remember anymore. Booted up fine.
[Nexus 9 Android Development] pavuol:
One question - Wavelet App (supports Android v.9 and up) - will it run with this ROM on this device?

[I tried with Samsung S5 and Line 18 and had no luck - as I described in its thread #885 ]
[Nexus 9 Android Development] rfresh:
will there be android 10 or 11 on this device?
[Nexus 9 Android Development] GROOVYJOSHCLARK:
depends, you planning to build it? we dont ask for ETAs EVER, but you are more than free to build it yourself. I might as well for my flounder but IDK if I will have time
[Nexus 9 Android Development] retiredtab:
Curiously, stats LineageOS shows one 17.1 device at

https://stats.lineageos.org/model/flounder

I'm building monthly 15.1. I think SirRGB has done some recent 16.0 roms at

https://sourceforge.net/projects/sirrgb-roms/files/Flounder/Lineage_OS/

based on linckandrea's repos. razorloves is maintaining monthly 14.1 builds. DivestOS also has some 15.1 flounder roms as well.

So I'm not sure who is doing 17.1. I tried building 17.1 a while back in 2021, but got stuck on the boot animation screen with hwcomposer errors if I recall correctly. I tried a few things, but couldn't find a way around the problem and haven't revisited since.
[Nexus 9 Android Development] SirRGB:
Some shield tablet related repos (branch: lineage os 17.1) have been updated this year and some stuff is on their gerrit, so there is some hope of getting Q running on Tegra K1, but I havent seen any 17.1 on their stats website...

It seems that one person (webgeek1234) makes all these commits.
[Nexus 9 Android Development] RisingNoob:
Is this ROM improved? Wondering if Bluetooth is now working and video playback.
[Nexus 9 Android Development] gwallace:
Hi all

I recently got my hands on an old Nexus 9 WiFi, is it this the best custom rom? or is it best to stick to stock or older versions od Lineage? I see this one has some issues so maybe sticking with older versions is better, I just want it to run a little bit smooth for browsing and media consumption, no games

Thanks!
[Nexus 9 Android Development] Colin_Elips:
Hello! I use this Rom and am satisfied. So far, I haven't noticed any major problems. There are some bugs in the interface, but it's tolerable. I have an LTE version of this tablet.
[Nexus 9 Android Development] BaLazS28235:
anybodey no why i am getting always the same error message : symlink: some symlinks failed ? PLS Help
[Nexus 9 Android Development] SirRGB:
One Lineage 18.1 build popped up for the shieldtablet (1st link), so I assume it is also possible to build it for flounder. I assume the build booted as well, maybe a little borked since only 6 people seem to run it (see stats, 2nd link). The Tegra K1 might not be at the end...

Odd Solutions Downloads

updater.oddsolutions.us

https://stats.lineageos.org/model/shieldtablet
[Nexus 9 Android Development] SirRGB:
It happened.

18.1 seems to boot, 10 active installs on the shieldtablet.

https://stats.lineageos.org/model/shieldtablet
[Nexus 9 Android Development] jib@rmi.ge:
Official build link in the first post leads to victara.

Do you mean it will also work with flounder?
[Nexus 9 Android Development] lemon567:
I would like to know that as well is there someone who knows if the linked builds work on the old N9?
[Nexus 9 Android Development] SirRGB:
Yea, boots and works mostly
[Nexus 9 Android Development] lemon567:
Could you give some sort of overview what's working and what's patially/not working?
[Nexus 9 Android Development] SirRGB:
Well everything seems to be working, even on my enforcing build (even though I was too inexperienced to address denials back then).

The main issue is speed, which could decrease over time...
[Nexus 9 Android Development] lemon567:
Could you share some insights on how to install the victara build? Using adb sideload in twrp gives an updater error that the device is flounder not victara
[Nexus 9 Android Development] SirRGB:
wdym? victara?
[Nexus 9 Android Development] lemon567:
yes I'm referring to the official builds that are linked in the OP since the link to victara builds for lineageos 18.1

myself and jib@rmi.ge have asked if these builds work on N9 while you responded "Yea, boots and works mostly"

Or is the link in the OP deprecated?
[Nexus 9 Android Development] SirRGB:
victara is another device, so you cant install that one on the Nexus 9 (flounder)

I think the victara lineage thread was used as template and it got published without removing all the references to the moto x
[Nexus 9 Android Development] lemon567:
So basically there are no official builds for the N9 except for the build in Google drive from the OP
[Nexus 9 Android Development] SirRGB:
No official builds anymore, no buts

Last official version was 14.1
[Nexus 9 Android Development] lemon567:
so it's just the unofficial lineageos 16 build from the drive link that is available then

thanks for clarifying things
[Nexus 9 Android Development] SirRGB:
Obv there are older versions available, but none of them seems to be updated anymore

I will try xenon tmrw with the Nov patch, but still the patches missed in 2021 June make it irresponsible to set a higher security patch level in the settings, so it will just show the old one...
[Nexus 9 Android Development] 5dPZ:
Flashed lineage-16.0-20210622-UNOFFICIAL-flounder.zip

From developer options, I turned off all the animations and selected "no background processes"

Half of the time the rom is fairly responsive, but the other half, there is significant lag - I guess this is due to aged hardware, not the ROM?

It would be great to share any tricks to reduce the lag and slowness for this tablet, thanks.
[Nexus 9 Android Development] NaCN368:
Can i use the vulkan api with this rom? i want play sky which need vulkan 1.0.3
[Nexus 9 Android Development] dargonswim:
Hi, I managed to boot lineage 17.1 on Mipad 1 (Tegra K1) thanks, among others, to linckandrea's commits. Right now the error is that it reboots after two minutes.

I need to fix sepolicy denials for now.
[Nexus 9 Android Development] SirRGB:
The nvidia shield tablet with the k1 runs A10 as well with random reboots and A11 just doesnt boot and since the most skilled lineage devs (nolen, web,...) tried and failed I dont see any hope for newer versions tbh...
[Nexus 9 Android Development] dargonswim:
mipad always reboots every 2 minutes
[Nexus 9 Android Development] heyChristo:
Is this worthy upgrading to from 15.1?
[Nexus 9 Android Development] dargonswim:
Hi, we have fixed random reboots on mipad - lineage 17.1 and we are booted lineage 18.1, so it is possible for this tablet.
[Nexus 9 Android Development] SirRGB:
off watchdog · 380583067/android_kernel_xiaomi_mocha@5a34979

restart 2 minutes after booting is over

github.com

Not sure if anyone is willing to invest the time to get this booting, but we do have this config enabled in our kernel...