[UNOFFICIAL][BETA][Q][ROM]LineageOS 17.1 Beta for Galaxy J5 [J500H/FN/F/G/M/Y/8]

Search This thread

qscesza

Member
Oct 19, 2018
14
1
Hi...
Thanks for developing this ROM.. I installed this ROM for J500H ... almost everything works fine ... except:

-If WiFi name is hidden, it can not be connected to it (even by marking the hidden option in advance option)

- Sometimes it does not recognize the second SIM card after restarting ... If Restarting for the second time! , solves the problem.

- The option (setting>apps>change storage) does not exist and has been removed ... Why?
 

.apoorv.

Member
Sep 12, 2020
22
3
J500F(j5lte), latest TWRP, low volume

Thank you for the ROM, I've had a terrible time trying to flash others for some reason (screen artifacts and some other problems), and this worked perfectly with the addition of allowing me to use an SD card as internal storage (couldn't with stock).

I've noticed the device's max volume is lower than the stock (android 6), it seems that videos/music sound much more quiet even when the multimedia volume bar is at full, is it a bug, or is it a just a matter of a simple fix?

Model: J500F (j5lte)
Recovery: TWRP 3.4.0
open GApps: Mini or Micro (one of them wasn't able to install because of size).
ROM version: lineage-17.1-20200826-NIGHTLY-j5lte
Are you able to use mobile data though? I just can't get it to work on my J500F.

Update: Don't bother. I got it to work. Check my post on the previous page if you want to know how.
 
Last edited:

zeusalmighty717

New member
Jan 25, 2021
1
0
I can't connect to the device using usb. Is this a known issue?
I can connect to adb using wireless debugging. In usb Preferences - everything is disabled and no data transfer is selected. I cant change usb options.
 

Shadow__dgrt

Member
Jul 17, 2020
12
1
Even i am having the same issue, when i install some basic apps like whatsapp and insta it works fine for initial 2-3 days then starts to hang. Even i didnt flash the recovery.img and booloader.img provided in downloads. @Zakaryan2004 pls do help me i am in need and need phone to be properly functional. I was thinking reason for more ram consumption is cause its android 10 but it turned out same in stock rom also and as a matter of fact this is the only functional rom for this device, i really thank u for that @Zakaryan2004 . If flashing of recovery and bootloader is a must pls do let me know. Again a load thanks to u
I got this issue solved by using magisk edexposed and greenify. now its highly smooth, thanks for this rom again
 

hjsuffolk18

New member
Jan 3, 2021
2
1
I have just compiled a new version of this rom thanks to the sources being available. The only difference is the boot animation (Custom Samsung Boot Animation in place of default one) and the default wallpaper. Other than that it is stock lineage, and I have made provision to provide updates over the air. Would anyone be willing to test this by any chance?

Note: this is for the J5NLTE Varient Only.

 
  • Like
Reactions: jjustinerovicc

.apoorv.

Member
Sep 12, 2020
22
3
Hello guys can anyone guide me after i installed this rom , how can i root this rom

1. Extract 'boot.img" from the .zip file of this ROM.
2. Download and install (preferably the latest version of) Magisk Manager from "magiskmanager.com".
3. Once you're done installing it, open the app. You'll see two options(first- 'Magisk', second- 'Manager') . Tap 'install' in front of the first option.
4. Now you'll see a menu. Tap on "Select and patch a file", and then tap on "Let's Go".
5. Look for the boot.img file that you extracted before, and select it. Magisk Manager will patch it and save it to a location.
6. Boot into TWRP recovery, and tap "install". Tap on "install image" at the bottom. Now look for the file that Magisk Manager patched and saved, and select it.
7. Swipe to flash. When it's done, wipe cache and dalvik cache and reboot into system.


That's it!

This is how I did it on my J500F.
 

.apoorv.

Member
Sep 12, 2020
22
3
Is it possible to pass the SafetyNet check on this ROM (after rooting with Magisk)? If yes, please assist me in doing so. Thanks in advance.
 

r0mushii

Senior Member
Is it possible to pass the SafetyNet check on this ROM (after rooting with Magisk)? If yes, please assist me in doing so. Thanks in advance.
use magiskhide props config from the magisk repo(its in the app under modules) to pass cts tests. see the module's readme on how to use it
if both basicintegrity and cts failed, check if magiskhide is enabled in settings and check safetynet again. if it still fails, make sure youre not using any hacks that tampers directly with the framework/system(i.e. xposed)
 

.apoorv.

Member
Sep 12, 2020
22
3
use magiskhide props config from the magisk repo(its in the app under modules) to pass cts tests. see the module's readme on how to use it
if both basicintegrity and cts failed, check if magiskhide is enabled in settings and check safetynet again. if it still fails, make sure youre not using any hacks that tampers directly with the framework/system(i.e. xposed)
Okay. Thanks a lot! I'll try this.

Update: This worked perfectly. All I had to do was change the device fingerprint to Samsung J5 (2015). Thank you very much!
 
Last edited:

.apoorv.

Member
Sep 12, 2020
22
3
I'd like to report a bug. The system audio player does not display the played audio correctly. Apps that use their own audio player (such as spotify) work fine but apps that rely on the system player such as some audio editing apps (such as this one- https://play.google.com/store/apps/details?id=com.appzcloud.audioeditor)
suffer from this bug.

Audio plays correctly but the playback indicator just keeps repeating itself between 00:00 and 00:01. This also occurs in the audio editing app I mentioned above, hence making it impossible to correctly edit it.

Is someone aware of this, and is there a workaround, or can another audio player be flashed to replace the built in audio player?

Update: This also happens while playing videos in the built-in gallery app, but even the video doesn't play correctly. It gets stuck after 1-2 seconds, and then just the audio keeps playing. Also, the playback indicator is just fine in the notifications area.

I'm on a J500F


Conclusion: This is a source code bug as mentioned previously on this thread. Probably no fix.
 
Last edited:
  • Like
Reactions: Shiningb

Jeremito1

Member
Apr 9, 2020
19
3
Venezuela
I have just compiled a new version of this rom thanks to the sources being available. The only difference is the boot animation (Custom Samsung Boot Animation in place of default one) and the default wallpaper. Other than that it is stock lineage, and I have made provision to provide updates over the air. Would anyone be willing to test this by any chance?

Note: this is for the J5NLTE Varient Only.

You can also make one for the j5lteCan you make one for the j5lte too? pls
 

Shadow__dgrt

Member
Jul 17, 2020
12
1
hey i have already used this rom for more than 8 months now and am really pleased with it. Just faced a bug recently that device is unable to recognise 5ghz wifi can someone suggest any fix pls
 

Shadow__dgrt

Member
Jul 17, 2020
12
1
For some reason, Mobile Data only works sometimes on my J500F (j5lte). Most of the time, when I turn data on, it just displays a little cross beside the signal bar, just like when it is off. I have not found any specific pattern of when it works and when it doesn't. For reference, I am using an Airtel (India) SIM card and calling and messaging works perfectly fine. The ROM is solid except for this one thing. Please help me fix it.

Alright! I fixed it. Here's what I did.
1. Clean wiped everything including modem (except SD card).
2. Flashed Stock ROM (Marshmallow)
3. Checked if SIM worked. It did. Noted APN settings.
4. Flashed recovery to TWRP.
5. Clean wiped, just the 5 options from the top.
6. Flashed this ROM.
7. Flashed GApps (Pico) without booting first.
8. Booted the phone.
9. Phone couldn't connect to mobile network during initial setup. So, skipped that part.
10. Created new APN with the noted settings, and activated it.
11. Mobile Data worked!

Now you might think that all that I did was change the APN settings. However, I had tried setting the APN multiple times when I had flashed this ROM before. Unfortunately, it didn't work. It does now. So, yeah.

I guess some ROM must have messed up my modem (?)

Thanks by the way, this ROM is awesome.

hey even i am facing the same problem, ya its true that some rom has messed with my modem files also but when i flash the stock rom even still am unable to connect to internet,
could i be provided with modem tar file pls so that i can reset it completely
 
Apr 27, 2019
6
2
I have just compiled a new version of this rom thanks to the sources being available. The only difference is the boot animation (Custom Samsung Boot Animation in place of default one) and the default wallpaper. Other than that it is stock lineage, and I have made provision to provide updates over the air. Would anyone be willing to test this by any chance?

Note: this is for the J5NLTE Varient Only.

Could someone please make this rom compatible for J500F because I use it as my personal phone?
Or someone tells me how to do it
Thank you!
 

.apoorv.

Member
Sep 12, 2020
22
3
hey even i am facing the same problem, ya its true that some rom has messed with my modem files also but when i flash the stock rom even still am unable to connect to internet,
could i be provided with modem tar file pls so that i can reset it completely
PLEASE NOTE: I am not a professional/developer. In fact I am new to XDA. I just came here to get an upgrade for my phone, and I was not disappointed :) .Therefore, all I state is based solely on my personal experience.


So, before doing what I stated in my post, I tried to flash just the "modem.bin" file from my stock J500F ROM using Odin. Unfortunately, it did not fix the problem.

By the way, do you have the stock ROM (the original Samsung Touchwiz ROM) for your phone? If yes, you can extract the files you need(including modem.bin) from the stock ROM using 7zip.

Also, be aware that for some reason, you won't be able to flash the modem file using the latest version of Odin. I had to use Odin 3.07 to flash mine and could not flash it using Odin 3.14.1.
Further, I can give the files to you but please make sure your phone is the same model as mine(J500F) before flashing. If not, you will have to find the stock firmware for your model and extract modem from that. However, as I said, flashing just the modem did not work for me (it might just work for you though :) ).
If you want me to share the files nonetheless, would you like me to e-mail the files to you? Send me a message about it.

Also, if this doesn't work, do what I did. Wipe Dalvik/ART Cache, Data, Internal Storage, Cache, System from recovery, also wipe the modem. Now flash the Stock ROM. Check if Mobile Data works and please note your APN settings if it works. Now, if it works, flash Lineage OS again, and enter your APN settings.

By the way, are you saying that for you, Mobile Data doesn't work EVEN ON THE STOCK ROM?
 

.apoorv.

Member
Sep 12, 2020
22
3
I'd like to report a bug. The system audio player does not display the played audio correctly. Apps that use their own audio player (such as spotify) work fine but apps that rely on the system player such as some audio editing apps (such as this one- https://play.google.com/store/apps/details?id=com.appzcloud.audioeditor)
suffer from this bug.

Audio plays correctly but the playback indicator just keeps repeating itself between 00:00 and 00:01. This also occurs in the audio editing app I mentioned above, hence making it impossible to correctly edit it.

Is someone aware of this, and is there a workaround, or can another audio player be flashed to replace the built in audio player?

Update: This also happens while playing videos in the built-in gallery app, but even the video doesn't play correctly. It gets stuck after 1-2 seconds, and then just the audio keeps playing. Also, the playback indicator is just fine in the notifications area.

I'm on a J500F
It appears that this problem is specific to my device. Does anyone else experience this bug?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 44
    2okPze5.png


    LineageOS 17.1 is a free, community built, aftermarket firmware distribution of Android 10.0, 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.

    Code:
    ** Disclaimer
    I am not responsible if flashing this ROM bricks your
       phone or causes thermonuclear war  and ends the
        world as we know it. You have been warned.

    ROM Information

    • ROM Target Device: Samsung Galaxy J5 SM-J5008 | SM-J500H | SM-J500F/G/M/Y | SM-J500FN
    • ROM Status: Beta
    • ROM OS: LineageOS 17.1

    What works
    * RIL (in-call audio, messaging, data)
    * Bluetooth
    * WiFi
    * Audio (music, etc)
    * Camera (including video recording)
    * Flash
    * Sensors
    * GPS
    * Brightness controls
    * NFC
    * Bluetooth audio

    What doesn't work
    * Bluetooth audio(an easy workaround can be found below) Fixed
    * KeyDisabler (read below) Removed
    * VoLTE, this will never work on AOSP as it's not easy to implement Samsung's proprietary implementation.

    Workarounds:
    * Bluetooth Audio
    To fix BT Audio on a Bluetooth headset, first connect to the device and after connecting press the gear icon near it. You should see a screen with 3 toggles(Phone calls, Media audio, Contact sharing), untoggle Phone calls and Contact sharing, leaving only Media audio on. After this you should be able to listen to media with bt headphones.


    Play Store not showing some apps
    You can avoid this bug by adding ro.opengles.version=196608 to your build.prop and rebooting. Make sure to clean Play Store app data.


    KeyDisabler
    The Navigation bar toggle in Settings>System>Buttons will cause touch screen not work after a reboot until the screen is timed out. This means that after rebooting your device you should let the screen turn off itself and then turn it off again to be able to unlock it.
    Device Names


    Verify your device codename before downloading any firmwares or recovery images!
    Code:
    [B]SM-J500F/G/M/Y[/B] - [COLOR="DarkSlateBlue"][B]j5lte[/B][/COLOR]
    [B]SM-J5008[/B] - [COLOR="DarkSlateBlue"][B]j5ltechn[/B][/COLOR]
    [B]SM-J500FN[/B] - [COLOR="DarkSlateBlue"][B]j5nlte[/B][/COLOR]
    [B]SM-J500H[/B] - [COLOR="DarkSlateBlue"][B]j53gxx[/B][/COLOR]


    Downloads
    ROM Download: here
    OpenGApps Download: here


    Installation
    Install the latest version(R10.1 or later) of OrangeFox(recommended, download here) or TWRP 3.3.1 or later
    Make a full backup (just in case something goes wrong)
    Make a full wipe(System, Data, Cache)
    * If you are already running LineageOS 16.0(by Galaxy-MSM8916) you can make a dirty flash(flash the build and the Android 10 GApps) but a wipe is recommended
    Download the latest build and transfer it to your phone
    Flash the zip
    If you are installing GApps do it before booting to the ROM. Make sure to flash the correct architecture and version(arm 10.0)
    And finally boot, the first boot can take several minutes as it optimizes all the apps

    There are still quite a few features that are not yet completed for LineageOS 17.1, these are not bugs, this is a beta release.
    You should provide logs when reporting any hardware-related issue.

    How to provide logcats

    Under Windows:


    Code:
    [B]* Install samsung device drivers and then
     the adb utils from here:[/B]
    
    [url]https://forum.xda-developers.com/showthread.php?t=2588979[/url]
    
    [b]* Then enable developer mode, connect your phone to usb,
     and from [B]cmd[/B] paste this command:[/b]
    
    [I]adb logcat > %userprofile%/Desktop/logcat.txt[/I]
    
    [b]then try to reproduce the bug.[/b]
    
    [b]* The logcat file will be on your desktop.[/b]



    Under Linux:


    Code:
    [b]* Install the adb utils from your distribution's
     package manager and execute the command:[/b]
    
    [I]adb logcat > ~/logcat.txt[/I]
    
    [b]then try to reproduce the bug.[/b]
    
    [b]* The logcat file will be on your home directory.[/b]

    * Submit the logcat here on the forums, or on the Telegram group.

    * If you cant connect the device through adb on windows because the drivers, connect the device over wifi, enable adb over network in developer options, and type:

    Code:
    adb connect [ip address here]

    And then the adb logcat command for windows.

    Also do not under any circumstances post bug reports if you are using substratum themes or unsupported Magisk modules or you have performed any system modifications.


    Credits
    I would like to everyone who has helped me throughout the whole process of making Q for J5, included but not limited to those people:

    jenslody for doing the Q bringup, making it boot, fixing most of the bugs, and for everything else he has done to the development!
    Galaxy-MSM8916 team for our base trees.
    SebaUbuntu for finally fixing NFC on j5nlte and for every other fix he has provided!
    Soft-Bullet for suggesting Camera fix.
    All of the testers who have willingly tested the builds.
    And to everyone else who has done even the slightest for the project.

    Source code
    Kernel source code: https://github.com/Galaxy-MSM8916/android_kernel_samsung_msm8916
    ROM Source code: https://github.com/LineageOS
    Device trees: https://github.com/Galaxy-MSM8916/android_device_samsung_msm8916-common

    XDA:DevDB Information
    LineageOS 17.1 Beta for Galaxy J5(2015), ROM for the Samsung Galaxy J5

    Contributors
    Zakaryan2004
    ROM OS Version: Android 10
    ROM Kernel: Linux 3.10.x
    ROM Firmware Required: >= Marshmallow 6.0

    Version Information
    Status: Beta

    Created 2020-01-22
    Last Updated 2020-01-22
    11
    A new update for LineageOS 17.1 for Galaxy J5 is now available!

    After a long break on the updates, Galaxy-MSM8916 is back up again, with 17.1 builds rolling, thanks to everyone for our hard work and spent time.

    Changelog:
    June security patch, with latest LineageOS changes (cool ones!)
    Fixed Bluetooth Audio
    OpenGLES(e.g. Play Store app compatibility check) and other build prop issues have been properly fixed instead of hardcoding.
    Thermal HAL should now work properly
    Snap should be included instead of Camera2.
    Wallpaper flicker issue when transitioning from Doze to Lock screen should be fixed.
    MIDI should now work
    Touch HAL and KeyDisabler have been removed, as those are too buggy and cause other bugs, even when the feature isn't being used.
    Cleanups in device trees, maybe some performance improvements.
    Much more I don't remember.

    Expect to see more updates coming, as the massive bringups and preparations are finished on Galaxy-MSM8916, and everything is now ready.
    Download links are updated on the OP.
    LineageOS 17.1 Go builds will come a bit later.
    If there is anything broken in this build, feel free to report!
    7
    A new LineageOS 17.1 build for Galaxy J5 has been released.

    Changelog:
    Latest LineageOS source
    Fixed OpenGLES value (Play Store issues)
    - If you still don't have some apps on the Play Store, clear Play Store's data.

    If you have found any bugs, don't forget to report them here!
    7
    New LineageOS 17.1 update for Galaxy J5 (2015) is out!

    Changelog:
    - Merged new LineageOS changes (expect new features and bug fixes)
    - Fixed Miracast
    - Fixed 2nd SIM In-call Audio
    - NFC and DRM issues have been thoroughly fixed! (Thanks to SebaUbuntu for this amazing contribution)
    - Rounded corner animation has been disabled(less lag on gestures)
    - KeyDisabler has been added, meaning you can now see Navigation bar toggle in Settings>System>Buttons (beware, known bugs)
    - Button backlight options have been removed from Settings>System>Buttons
    - OpenGLES version flag has temporarily been hardcoded (Play Store will work properly now, clear Play Store data if it doesn't)

    Known bugs:
    - The Navigation bar toggle will cause touch screen not work after a reboot until the screen is timed out. This means that after rebooting your device you should let the screen turn off itself and then turn it off again to be able to unlock it.

    As always, download from the links in OP.