The sound issue seems to be user based and is not a ubiquitous device issue.
The latest version is fine. The dev is adding audio specific fixes for the next build which should drop fairly soon.
[ROM][A520F/DS] LineageOS 14.1 Alpha
- Thread starter RaymanFX
- Start date
The sound issue seems to be user based and is not a ubiquitous device issue.
The latest version is fine. The dev is adding audio specific fixes for the next build which should drop fairly soon.
Hi there. I have a little bit of problem here, when I flashed this rom my phone don't see any sim card. Even on stock, just checked right now. What should I do? Any way to fix it?
Check your IMEI. If it isn't there, even on stock, then your EFS partition has been wiped. If you have a backup of it, restore. Otherwise, enjoy your mini-tablet. There is no way to recover your EFS. sorry.
Sent from my athene using XDA Labs
No, if your EFS partition was genuinely deleted, there is no getting it back. If modem.bin were corrupted, the device may not turn on right, and WIFI would be completely broken. Please correct me if I'm wrong; i got this from the OP of a rom thread (I can't remember which). If you have any evidence disproving this, please PM me or post here, as I could be wrong.
Sent from my athene using XDA Labs
D
Deleted member 6304402
Guest
How do I prevent accidentally deleting my EFS partition? Or do I need to do some really weird **** in order to delete it?
Can't flash the newer releases cause of wrong bootloader
Hey everyone,
I'm new at this but i've tried to flash lineage OS on my Samsung Galaxy A5 2017 (SM-A520F). I already got lineage OS installed on my Phone. But that's the first build that was released. It is this one: 2017/08/11 - https://www.androidfilehost.com/?fid=817550096634791977. But there are couple of problems with this build that are fixed in future build. But i can't flash the other build's cause my bootloader ( At least I think is) Can anyone help me with this problem? I've tried flashing a different firmware on it. From this post: https://xdaforums.com/samsung-a-series-2017/how-to/official-nougat-release-download-guide-t3654413 . But it keeps giving me errors in Odin. Sometimes it's stuck at SetupConnection. Sometimes it fails at boot.img, param.bin etc. Please can someone help me. I'd like to flash the newest version of lineage OS
. Thanks in advance!
Hey everyone,
I'm new at this but i've tried to flash lineage OS on my Samsung Galaxy A5 2017 (SM-A520F). I already got lineage OS installed on my Phone. But that's the first build that was released. It is this one: 2017/08/11 - https://www.androidfilehost.com/?fid=817550096634791977. But there are couple of problems with this build that are fixed in future build. But i can't flash the other build's cause my bootloader ( At least I think is) Can anyone help me with this problem? I've tried flashing a different firmware on it. From this post: https://xdaforums.com/samsung-a-series-2017/how-to/official-nougat-release-download-guide-t3654413 . But it keeps giving me errors in Odin. Sometimes it's stuck at SetupConnection. Sometimes it fails at boot.img, param.bin etc. Please can someone help me. I'd like to flash the newest version of lineage OS
. Thanks in advance!
Supposedly both odin packages and twrp can randomly delete it, so be careful.
Someone else's IMEI won't work at all, as it has a relationship to the S/N...
Sent from my athene using XDA Labs
Strikes me as a mystery as to why people don't backup before trying stuff.
Mental.
Please, it is the third time I ask and I really did not find any guide that I fully understood, could someone give me a brief tutorial, guide, link to how can I flash a functional twrp and after that Lineage OS? Sorry for the insistency, buddies, but I really need. I'm new to Samsung devices, I only know how to do things with pure android like firnwares and os, Samsung is very different for me
First follow this tutorial
https://xdaforums.com/samsung-a-series-2017/how-to/samsung-sm-a520f-2017-kernel-source-t3557622
And then copy the ROM to the microsd card and download the ARM_64/ANDROID 7.1 Pico variant gapps from this web:
http://opengapps.org
And then copy it too to the microsd card. Then make a factory reset and manually format /data un the Format menu of TWRP
Next, flash the ROM, wipe Dalvik-Cache, flash the gapps, wipe Dalvik-Cache and if u want to root, first reboot the phone, wait until it starts, and then flash superSU zip.
And restart. DO NOT stop the process. Maybe the phone will last 5 minutes booting, just wait.
If u don't understand it, maybe you shouldn't be here installing a custom ROM.
But if you really want to, just tell me where do you have problems and i'll help
Last edited:
Thanks, thanks haha I'm kind of experienced with flashing, had already all the roms for the moto g 2014. But this Samsung thing isn't very "user friendly" lol
Anyway, I was having problems with that same guide, but thanks, I'll give it another tries later with more time ^^
Thanks again, buddy
Have tried this?:
https://www.techjuice.pk/how-to-root-samsung-galaxy-a5-2017/amp/
I think they explain it very well
Thanks, I'll take a look on that one too ^^
Here's a new build with the screen-off audio fixed and dt2w (double tap to wake): https://www.androidfilehost.com/?fid=890129502657581837.
DT2W is a really neat feature, which is possible by leveraging the Samsung AOD kernel code: https://github.com/raymanfx/android...mmit/acc44c75f95e3f4d8243e4017cf0ccb6e445652b.
It does not keep the device awake or drain too much power, but uses a low power mode in the touchscreen controller.
DT2W is a really neat feature, which is possible by leveraging the Samsung AOD kernel code: https://github.com/raymanfx/android...mmit/acc44c75f95e3f4d8243e4017cf0ccb6e445652b.
It does not keep the device awake or drain too much power, but uses a low power mode in the touchscreen controller.
OMG! Whoop! Been waiting for this for a while. Audio has been coming out of the only the loud speaker when I make phone calls (most of the time) and the Bluetooth audio has never worked with my car, but other than that, I've loved using this ROM. Thanks so much for the ROM RaymanFx!
Installing now!
---------- Post added at 01:17 AM ---------- Previous post was at 12:35 AM ----------
Whoop! The audio works (haven't tested Bluetooth yet).
Installing now!
---------- Post added at 01:17 AM ---------- Previous post was at 12:35 AM ----------
Whoop! The audio works (haven't tested Bluetooth yet).
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
86
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), 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.
Bugs/Issues :
GPS takes ~30secs to lockTorch cannot be activated from quick settingsExternal SDCard not showing up in gallery, etcFingerprintLTE is spotty - only 2G/3G seem to be stableScreen recording is broken (csc errors)- Camera saves picture in wrong orientation (workaround: lower quality to 11,9MP 16:9 in camera settings)
- ...more?
Instructions :
- Download the latest build and gapps
- Reboot to recovery
- Flash the latest build and gapps
- Reboot
- Builds : See below
- Root addon : https://download.lineageos.org/extras
- Google Apps : http://opengapps.org/
- 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 /proc/last_kmsg. (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
Code:What is your-- LineageOS version: LineageOS Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Are you using-- a task killer: a non-stock kernel: other modifications: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
### RELEASES ###
2017/08/11 - https://www.androidfilehost.com/?fid=817550096634791977
2017/08/14 - https://www.androidfilehost.com/?fid=745425885120755593
2017/08/22 - https://www.androidfilehost.com/?fid=961840155545590372
2018/01/03 - https://www.androidfilehost.com/?fid=673791459329070889
2018/01/03 - https://www.androidfilehost.com/?fid=746010030569953982
The releases are based on Samsung Nougat kernel sources. If you are facing issues regarding the radio stack, you need to flash official N to get the new baseband. The M baseband might work, but it unsupported!
XDA:DevDB Information
LineageOS, ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
RaymanFX
Source Code: https://github.com/raymanfx/android_kernel_samsung_a5y17lte
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2017-08-11
Last Updated 2018-02-1525
... I still don't care?
It hasn't been enabled here yet, and there are more important things I need to focus on.
If you want VoLTE/VoWiFi, you'll have to do it yourself, review.lineageos.org is open for your contributions.
For those who are feeling adventurous, here's a first build of Lineage 15.1 (Oreo 8.1):
https://www.androidfilehost.com/?w=files&flid=251962.
DO NOT USE OPENGAPPS, but instead use the Gapps that are inside that folder.
Bluetooth is broken, NFC might require a restart to work - other than that it's okay-ish for a first preview build.
If you want to support me and/or the project, I'm looking for a used Galaxy S8 to buy from donations, so, you know what to do if you want to help that cause22Today might be the day you have waited for!
https://www.androidfilehost.com/?fid=746010030569953982
This is the first build with open source (reversed) RIL I hacked and fixed today finally.
Lots of effort went into this one, I hate playing the cat and mouse game, especially in the radio subsystem, which is the one I'm the least familiar with.
Enjoy and report back please. Cycling between 2G, 3G, 4G should also work fine now.20I guess I can give you some info about the progress on 15.1.
Firstly read this post. What has happened since then?
Well, a few things. Now I'm going on holiday so I am releasing all this. This is where we at now:
It is still 95% work by raymanfx although I am releasing it. I maybe added some additional stuff to his work.
* Bluetooth is now working -> RaymanFX was working on this and in the end he was finally able to fix it. edit: Well at least it turns on on boot now.
* Always On Display -> Google added support for this on AOSP Oreo and I was able to enable it on lineage. Try it guys. Hopefully it works as intended and doesn't drain the battery too much.
* A7 and A5 unification attempt -> Well firstly I need to say thanks to Skorupsi for testing out my stuff. I experimentally added A7 support. I own an A7 and I can verify that it boots and it appears to be working fine. But maybe some calibration stuff - screen, camera, battery is still set to A5. So it's still experimental and I don't guarantee anything. Flashing this is your responsibility. This only applies to A7 users, if you own an A5 you can ignore this statement. It is exactly the same as it was before for A5.
* Fixed screen off while in calls. Yeah you probably saw this in 14.1 as well.
* Perhaps I messed up media codecs. I see 1080p youtube videos somehow lagging.
* Is NFC working? edit: I see some crashes in the logcat - probably not.
* Upstream updates from lineage
* You should use N bootloader and modem for your device
Lastly thanks to xda moderators for acting. Yeah developers have their jobs/schools/families and can't focus on this all the time. Please don't get rude. No ETA/volte.
Have fun
https://www.androidfilehost.com/?fid=5862345805528044189
