yashsingh1/xdaforums huggingface dataset:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Floehelis:
I've also noticed the flicker starts happening when bringing the brightness slider down to below 20%. I don't know if it's the A7 alone or if other phones also have this, at around 20% brightness the screen switches to a limited color range profile. Could it be this is causing a problem? But that said the flicker still happens when on full-range colours as well. In any case, when I first installed the rom in early december this issue wasn't there, it started happening around after the early january updates.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Androbots:
Sounds really like a hardware problem cuz what you are describing is something I've had even on stock and Samsung Service Center suggested me to get my device's screen replaced for $150 which I obviously didn't xD
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] greenberet33:
Not sure how to start with this. Could you point me out to something?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Androbots:
GitHub - LineageOS/android_device_samsung_a7xelte

Contribute to LineageOS/android_device_samsung_a7xelte development by creating an account on GitHub.

github.com

GitHub - LineageOS/android_device_samsung_a5xelte

Contribute to LineageOS/android_device_samsung_a5xelte development by creating an account on GitHub.

github.com
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Floehelis:
I reverted back to stock. The problem is still there. So, that essentially rules Lineage out of the question. But the problem is only there for very low brightness, and when trying to bring the phone out of sleep. While the phone is on and the brightness is sufficient, everything is working fine, both in Lineage, and Samsung's default OS.

But, since this is a circumstantial glitch, I'd like to believe it's a software error and not hardware. And it looks like the issue isn't the ROM itself since it persists on a clean samsung OS install.

I'm fairly new to this so I'll look around for what other data still persists. Maybe that'll provide some answers. Eventually.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Er@g0n:
I can flash LineageOS 17.1 for my phone variant A7108 exynos?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Asutosh01:
Can you please make the screen turn off instantly whenever power button is pressed. Because a lot of Galaxy A7 2016 including mine comes with faulty amoled displays which flickers at low brightness. In this is version when the power button is pressed the screen gradually lowers its brightness before going in to sleep mode and the screen flickers for 2-3 seconds. When power button is pressed again to wake up the phone it flickers again sometimes wakes up after 4-5 attempts. Please make this is to wake up and sleep the phone whenever power button is pressed instantly without gradually lowering or increasing brightness

SOLVED: Screen flickering at low brightness - samsung galaxy a5 2016

The LCD screen flex cable is worn out and not well connected with the motherboard. This may cause by overheating, moisture or dropping damage. - samsung galaxy a5 2016

www.ifixit.com
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Asutosh01:
Turn off transition animation scale window animation scale and duration scale . Then use pwm app. Thank me later
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Asutosh01:
Use pwm app
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] impasta:
Hello. I'm curious about 2 things.

Will there be a LineageOS 18.* build for this device?

Has someone experienced random system crashes specially when the GPS is used (e.g. LiveDisplay is set to Automatic and location is on; Google tries to access your GPS even if location is off)?

I can provide a stack trace and a symbolized stack trace if that will help the developers.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Androbots:
Yep. We have already made a lot of progress over the months and things are pretty stable now. We plan on releasing after we level out some more inconsistencies. Here are some screenshots though to keep you chugging along :D

About GPS, I am blind without a logcat. Googling how to get a logcat should help you get one from your device.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] wektorizm7:
Hi, first of all thank you for your super work but after throwing the rom I can no longer call anyone, IMEI problem I guess what can I do?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Ariskwn:
Hi, kudos to the Dev for the ROM. Working nice and smooth. Anyhow does anyone having issues with formatting the SD card as internal storage? In my case, it failed during formatting (stuck at 40 percent and then it force close), is it a bug on this release? Thanks
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] retiredtab:
@Androbots and @impasta

Was the above ever solved? We are running into the exact same error messages when gnss crashes on the exynos5433 platforum (Samsung Tab S2 and Galaxy Note 4). We get the same marshal_agps_ril_request_setid and AGnssRil::requestSetId and AGnssRilCallback::requestSetIdCb.

Both exynos7580 and exynos5433 use the same BCM4752 gps chipset.

We have tried lots of things to fix it over the last week and now trying to switch manifest.xml from gnss passthrough to hwbinder. I cannot recreate the gnss crash at all and it seems random when it crashes so I have to wait for my testers to report it, but usually it crashes with 24 hours.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] retiredtab:
Just to update. Switching to hwbinder let's my 3 testers have > 100+ hours uptime now. Details at

https://github.com/universal5433/android_device_samsung_gts2-common/pull/4

It may help you guys out?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mihancad:
hello @Androbots

my brother

Will there be a LineageOS 18.1 build for this device?

You can give a date?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mihancad:
HI @Androbots

Considering the release of the unofficial version 18.1 for A3 and A5 phones, when is version A7 going to be made?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Androbots:
I guess I'll do it too then, lol. No update on the OFFICIAL submission yet.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mihancad:
Thank you, my brother, I look forward to it
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Saeeda72016_a7108:
Lineageos 17.1 don't work on a7108

Bootloader is succeful but install page after 30 min trying this error :

E:Failed to bind mount / mnt / staging / emulated / media / 0 to /storage / emulated : No such file or directory

E: Emoleted failed No Bind mount / mnt /storage /emolated/ media / 0 on / storage / emulated / media / 0 on / storage / emulated : No such file or directory
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] retiredtab:
I created the 18.1 trees for S2 Tab wifi devices and included that gnss hwbinder patch and so far the people who were getting < 24 daily crashes with 17.1 running gnss passthrough have not experienced it anymore. The longest uptime was 27 days before @lpedia rebooted the S2 running 18.1 on purpose to load the latest rom with the Oct 1 security patches.

I find some people don't care, don't bother and/or don't know how to report things. If your device crashed, there's likely tombstone data as I discussed at

https://xdaforums.com/t/troubleshoo...rs-running-any-version-of-android-10.4308203/

If you are using 18.1 and getting random crashes everyday, check your tombstone as I show above.

If you are building 18.1 on your own computer, then you just need to change line 73 to hwbinder because it's still set to passthrough in the current code.

https://github.com/LineageOS/android_device_samsung_a7xelte/blob/lineage-18.1/manifest.xml#L73

If you are not building 18.1, then the above thread also points to how you can manually change manifest.xml. However, this may or may not work as we found out through trial and error. If it doesn't work, then you will have to get a developer to compile this.

Anyway, let me know how it goes and which route you chose to proceed with.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] impasta:
Got this. This is the first time I learned about tombstone files; so these backtraces are actually saved.

I build it on my computer since neither the official nor the unofficial build includes the fastcharge "hidl" and that I need some changes that limits the current to 1.2A on non-fastcharge and automatically stops charging when the battery temperature exceeds 43C.

Anyways, I tried the easy way of just changing the manifest.xml on the device itself but just boot loops. It turns out that I also need to build android.hardware.gnss@1.0-service.

I just rebuilt it yesterday and the phone is still up. 23 hours and counting...
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] retiredtab:
I think the OS saves up to 50 tombstones before it recycles the filenames and starts at 00 again. So if you have a lot of tombstone files with 18.1, it's easy to look through them all using something like

adb root
adb shell
cd data/tombstones
head -n 20 tomb* | more

The above is consistent with what we discovered. It works on some, but not others for whatever reason.

I didn't check the .mk file to see if that line of code was in there or not, but I did document that both -impl and -service are required in my github pull request.

Only 77 hours more to get to 100 hours. Please report back if the gnss hwbinder patch makes it to 100 hours or not.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] impasta:
Well, it seem that it worked. 272 hours and counting and I did not have that gps crash ever again, screenshot attached (IMEI redacted). Also, GPS still works as intended.

Thank you for the suggestion.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] retiredtab:
272+ hours uptime probably means it's fixed!

Thanks for posting your original logcat so I could find it via search. Too many people report problems but without logcats making it difficult to coordinate efforts to fix them.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I am happy to merge a fix To official if you upload the change to Gerrit.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] impasta:
Hello,

Sorry for the delay in responding and also, Happy New Year!

On the flip side, within the last 2 months, I did not have another crash because of GPS (I did have other crashes but it's mostly openGL errors bringing SurfaceFlinger down and the newer sdfat crashing the kernel). Thanks again @retiredtab .

This is quite a trivial change (i.e. just inserting 3 lines). Though, the problem I have here is that the change targets the "manifest.xml" file which is available in the specific device tree for a7xelte. I was kind of expecting a single file in "universal7580-common"

Should I still proceed on this?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Yes, it would need a change for each device. Just focus on the a7 (so you need one patch for common and one for a7), I will do the rest.

I've not had any reports of sdfat crashes on 17.1. on 18.1 I fixed the bug (missing patch) quite a while ago.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] impasta:
... So that's why it crashes. The fix is at https://github.com/LineageOS/androi...mmit/c972033d326606a0ee3c909b37d8e11c76e35bb0

Thanks,
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] retiredtab:
@impasta and @danwood76 , you can look at this for a detailed explanation on why the change is required. Too often, I find commits that make changes with no explanation as to why we are changing from passthrough to hwbinder (as an example).

https://github.com/retiredtab/andro...mmit/1bbb341259f6aee071d88e4abdce42190fd620a7
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Personally I think you're commit is way too verbose (patch is one line, commit message is hundreds). You should be able to summarise it in one line. But then I am a programmer 😂

Unfortunately Stricted has reminded me that binder gnss caused issues with encryption on our devices before. I need to do some testing before this could be merged.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] retiredtab:
Because 5 of us spent nearly a month troubleshooting an issue that was ignored for nearly a year, I thought the verbosity was necessary so that others could benefit. For example, impasta's error messages were identical to ours so documenting that certainly helped.

And I'm not. What's obvious to you is not to me. What's a simple change and the motivation behind that change is not obvious to me.

All I will say is that we see and understand things from different points of view.

What type of encryption could be affected by gnss code?

Anyway, I'm interested in your findings even though I don't have this device because I'm interested in learning how you solve problems.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I have done a bit of digging this morning and the libgps we use on the 7580 devices creates a few files on the data partition before the decryption occurs. In this state it is a tmpfs but it needs to be unmounted so the real data partition can be loaded.

These files are not cleaned up correctly when the hidl service is shut down so cryptfs cannot unmount the volume which hangs boot.

This seems to fix it on our devices:

https://review.lineageos.org/c/LineageOS/android_device_samsung_universal7580-common/+/321187

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] retiredtab:
That's the exact type of extra information that I would like to see in commits so it helps others who are looking for solutions in the gerrit database. In addition, it's good to see that's documented in the code so future people know why gnss is stopped and restarted.

Thank you for the explanation. I appreciate learning from you.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Joanga:
Hi guys,

Can you tell me if this ROM works for my Samsung Galaxy A7(2016) SM-A7100 with Snapdragon?

This mobile phone is from Hong Kong

I don't know if my phone is A7xelte or other, I don't know where I can see that.

Thank you very much.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] monsiu:
a7 2016 goes by the codename a7xelte

there are different versions of the phone but i do not think it matters coz its all part of the a7 2016 family hence its still a7xelte

even on the official lineage page it shows all models as being under a7xelte :) give the rom a try....

look for the lineage 18.1(by dannywood) for a stable android 11 experience!

there is also a group working on lineage 19! How cool is that!

you can move there too and contribute....and build an aweome android 12 experience
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sdeev99:
У кого-нибудь есть последняя версия Does anyone have the latest version
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Joanga:
Thank you very much for your reply.

I will look at lineage 18.1(by dannywood) and install it on my phone and see how it works.

Thanks my friend
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Umair2984:
Where is the download link?? Please provide link to download this rom!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] musstt:
A7 2015 içinde lineage OS 17.1 istiyoruz
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Bunny Munnu:
Rom missing in the link. if anyone have a backup of it, please upload anywhere and share the link. It is for Galaxy A7 2016
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ARaW10:
Hi,

I am not promoter but you has to using this

LineageOS Downloads

download.lineageos.org

I know you using version 2016 and not 2017 but I have try it and it works properly!

And if you want the Gapps you must using ARM, ANDROID 11.0, nano for great

Its simple

tips: You can expand your storage using sdcard so you have more space (more hot for your phone if you playing game)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] desaturated:
So you manage to install 2017 ROM into 2016 device?

are you sure it;s okay?
[OnePlus 8 Pro Questions & Answers] 123Opie:
My phone has a slight issue where on low volumes the earpiece speaker is clearly louder than the bottom one which isn't the case for my "old" 7 pro, and my overall audio level is lower. Have any of you guys had any issue with this? Please let me know otherwise I will probably return it and buy a new one because the speakers are a big deal for me. I also have the screen problem which isn't helping.
[OnePlus 8 Pro Questions & Answers] 123Opie:
fixed

just downloaded a vpn and set my location to finland for the new software version and its fixed... My screen tint is a little better but not 100%, especially by the punch hole where i have a clear horizontal line.
[Touch Diamond, MDA Compact IV General] gigi06:
Hello,

sorry for my english, I'am french.

My problem : It's impossible to synchro ma headset BT or rather it is recognised and no run.

my Diamond is a SFR Pack.

I am the only one to have this problem

Gigi06

en Fr : j'ai une Samsung wep200 comme oreillette Bt avec mon Diamond. Quand je fais la synchro avec le Diamond, ça fonctionne, elle est reconnue mais je n'arrive pas à la faire fonctionner ! Elle ne réagit pas malgré qu'elle clignote toujours (sous tension).

Si vous avez une idée !! je suis preneur ?
[Realme 5 Pro Themes, Apps, and Mods] sansgood:
Hello, I'm Sansgood and I'd like to share with you a little project I've been working in.

Knowing how under saturated are the colors in our device's screen, I was searching for some option

to improve their vibrancy. In my opinion, screen is the only weak point of this device.

So, I found a nice project which I forked and improved as much as I could: [url]https://github.com/zacharee/Sa2ration[/URL]

My improvements are:

- Restablisment of saturation values on startup.

- Improved fonts and styles more according to material design.

- Going back to default values.

- Initial root check to ensure app can be used.

- Support for upcoming Android releases (as core behaviour code will be deprecated soon...)

This app needs a rooted device. I am not responsible for any damage accurred to your device during rooting or using the app.

Download:

[url]https://sourceforge.net/projects/sa2ration/files/[/URL]

Fork source code:

[url]https://github.com/sansgood/Sa2ration[/URL]

Please keep in mind this is my first share in this community. I have few experience developing and I would like some share and constructive criticism.
[Realme 5 Pro Themes, Apps, and Mods] sansgood:
Attached screenshots
[Realme 5 Pro Themes, Apps, and Mods] gl33ch3r:
will it work on realme ui rooted?
[Realme 5 Pro Themes, Apps, and Mods] sansgood:
Almost certainly yes.
[Realme 5 Pro Themes, Apps, and Mods] savrin:
is the app needs to always run in the background? or i can just kill it?
[Realme 5 Pro Themes, Apps, and Mods] sansgood:
You can kill it if you wish. It does nothing in the background.
[Realme 5 Pro Themes, Apps, and Mods] sean222:
Thank you! This works on my Pixel 5 :)
[Realme 5 Pro Themes, Apps, and Mods] GRAM333:
the standard apk works on my mi max 2 but this one not...says cant run app whe i try and open it..?????
[Realme 5 Pro Themes, Apps, and Mods] Vladtdr3:
Wow . After spending the whole day flashing magisk modules and configuring then via terminal and not working. I found this amazing app. That is in the store and is easy and works so good! Congrats man
[Realme 5 Pro Themes, Apps, and Mods] PhanesEos:
good apps, and can add rgb adjust? or some tools?
[Huawei P9 Lite Questions & Answers] l00ping:
hello, I wanted to pass my P9 in double sim but I had to crash somewhere ...

the Rom works perfectly but I can no longer do an update or factory reset. I no longer have access to recovery stock / twrp

I have access to the bootloader (unlocked) and the eRecovery.

I tried an update with dload. the P9 restarts and hangs on "your device is booting now".

update with erecovery: software install failed. incompatibility with current version.

the phone has been like this for 4 years and I no longer remember the manipulations made.

I managed to have access to the twrp recovery, I wanted to make a wipe but I have the error message "can't mount data" I specify that EXT2 to EXT4 does not work either ...

In summary:

Start: vns L31 C109B160 go to vns L31 C432B160... ****!! :rolleyes:

Arrival: about the phone:

HI6250 vns C432B160

EMUI 4.1.2

android 6.0

version info:

manufacture information: VENUS_L_31_VB ...recovery?

AP VERSION: VNS-C900B160_SYSTEM :eek:

screenshot about the phone

[IMG="about the phone"]https://zupimages.net/up/20/17/2gvq.png[/IMG]

screenshot version info

[IMG="version info"]https://zupimages.net/up/20/17/wvgh.png[/IMG]

Is there a way to go back to a basic version?

Thank you in advance for your help
[Huawei P9 Lite Questions & Answers] Dadditz:
Hello,

if i understood well you switched from a branded (orange C109)

to the european unbranded (C432) firmware.

You said it works perfectly, that's a good scenario, i think you could

upgrade to android 7, just try to use firmware finder app like

[MENTION=4512283]xykarelxy[/MENTION] have done with his device. (see here and/or ask him for details)

You should point to VNS-L31C432B370 FULLOTA-MF-PV,

the only difference is in device version, his is L21, yours is L31...

In order to go back to basic (C109 cust), i think it's possible,

but you'll need to find out the correct oeminfo file (L31C109oeminfo.zip file)

and the VNS-L31C109B160 firmware.

But, if you succeed, you will face the same problems to upgrade to android 7.

Happy flash dude... :)
[Huawei P9 Lite Questions & Answers] l00ping:
Hello,

yes I was in C109 (orange)

I successfully reinstalled TWRP recovery.

I see for the future and I keep you informed.

thanks for your help

Hello, thank you very much !! I was successful. The phone runs with the latest firmware... but without bluetooth and without the possibility to make updates. Which is curious
[Galaxy Tab 4 Q&A, Help & Troubleshooting] delj:
Question for those who have been testing ROMs on Matisse (Galaxy Tab 4 10.1" SM-T530). Which ROM is currently most stable for a daily driver?

a) lineage-16.0-20200415-UNOFFICIAL-matissewifi.zip from matteo026

b) lineage-17.1-20200419-UNOFFICIAL-matissewifi-Unsweetened-XDA-BUILD.zip from DJABHipHop

c) lineage_matissewifi-ota-eng.android.zip <-- What exactly is this one? It was in the same directory with other ROMs from DJABHipHop

d) some other ROM

I'm mainly looking for stability (as in, doesn't crash too much) and security (patches for known major vulnerabilities)

Thanks all

j
[Galaxy Tab 4 Q&A, Help & Troubleshooting] d_tshudy:
I also have a SM-T530NU. I've run the Lineage 16 and 17 ROMs. Unfortunately you're going to have to temper your expectations. This is an old tablet. I'm amazed that Android 10 runs on it at all. You're not going to find both stability and recent vulnerability updates. If you want stability, use the old stock ROM. If you want new, the Lineage 17 ROM runs but crashes/reboots far too frequently to use daily.

Try them. Flashing this thing is straightforward.
[Samsung Galaxy Note 10+ Themes, Apps, and Mods] elevation_ph:
Please i looking for alternative Game Launcher for Note 10+ N975F some with more graphic options. anyone know any? Thank´s