Related
I recently updated to CM 12.1 from CM 12. I had a lock screen PIN setup earlier.
Now there is no option to change it under Settings->Security!!
I have attached the screenshots of Security options available for me in Settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Click to expand...
Click to collapse
"LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (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. You will need to provide your own Google Applications package (gapps). 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 (without device tree/kernel/vendor repos). And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit."
LineageOS 16.0 for Samsung Galaxy C5
SM-C5000
Android 9.0 OREO
64-bit(better for 4Gb RAM, than 32-bit stock)
What's working:
Display
Touchscreen and multitouch
RIL (Calls, SMS, USSD, Mobile data, LTE, dualsim)
NFC
Wi-Fi
Bluetooth
Fingerprint sensor
Camera (photo,video,flshlight)
Audio
Sensors
RGB LED, button backlight
Screen auto brightness
GPS
SD-card (and adopted storage)
F2FS, SDcardFS, exFAT file systems
Data encryption
SELinux
What's NOT working (Know issues):
AOD unstable
...
Installation:
Install only over C5000ZHU1BRA1 stock ROM
Unlock (https://forum.xda-developers.com/android/help/samsung-sm-c5000-t3407143)
Install a compatible Recovery (TWRP > 3.2 https://vasy.ru/TWRP/c5lte/)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps (ARM64 - 9.0) addon http://opengapps.org/
Reboot
Video Installation Manual by O S M A NC.
Download
Donate
Source code:
ROM: https://github.com/LineageOS
Device tree: https://github.com/vm03/android_device_samsung_c5lte
Kernel: https://github.com/vm03/android_kernel_samsung_c5lte
Vendor: https://github.com/vm03/proprietary_vendor_samsung_c5lte
Credits:
LineageOS Team & Contributors
XDA:DevDB Information
ROM][UNOFFICIAL][PIE] LineageOS 16.0 for Samsung Galaxy C5, ROM for the Android General
Contributors
vm03
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Beta
Created 2019-06-01
Last Updated 2019-06-01
Changelog20191016:
- SELinux Enforcing
- fixed power profiles
- fixed button backlight
- NFC fixes
- mainstream LineageOS updates
20191009:
- mainstream LineageOS updates
20190711:
- Fix USB and WiFi tethering
- mainstream LineageOS updates
20190531:
- First public release
Possibly update from 15.1 without wipe:
1. install LineageOS 16.0
2. install gapps 9.0
3. reboot
Can you tell me about nokia x2 ara?
I have been using it for 1 week.You did a really great job.Samsung can't even make such rom on this phone .This rom has good battery life.Even the performance is very fine but it needs optimization(Maybe problem in power profiles).I'm using l speed and I'm using its CPU optimization,it gives better performance and less warming.
I found some bugs.
Sometimes Phone LED light and key lights don't work.
Hotspot doesn't work (phone restarts whenever someone connects).
Can't read contacts on SIM CARD.
If you fix these bugs it would be a perfect rom for this device.
Can u make one for c5010 also
thnx great rom
I got caught in a bootloop, did I miss anything?
Edit: The GAPPS that I was flashing weren't the right ones and were causing the bootloops, the roms is perfectly fine.
Cant set to up dude. Setup wizard is stopped again and again when i flash rom and flash gapps.
Verusrex said:
Cant set to up dude. Setup wizard is stopped again and again when i flash rom and flash gapps.
Click to expand...
Click to collapse
Watch video for how to install it.
https://youtu.be/XjsYV79zzJU
Thank you for creating a ROm with such great performance and battery life! HOWEVER, there is one critical bug that I have been encountering consistently, no matter how many times I wipe and clean install following the instructions exactly (I have the correct bootloader and gapps versions).
>>>What happens:
Sometimes, when I try to turn on the screen after it has timed out (using the home or power button), the lockscreen would rapidly blink between screen on and screen off, causing a "lockscreen loop" that prevents me from unlocking the phone. This would repeat infinitely, and the only thing I can do to get out of it is hold the power button and hit power off or restart if I time it correctly between the blinking. Once the phone restarts, it would usually go back to normal, but once in a while, the phone would reboot back into the exact same "lockscreen loop". When this happens, this loop NEVER stops, no matter how many times I reboot, so I am eventually forced to wipe/factory reset and reinstall the ROM again from scratch.
>>>How frequently/when does it happen:
This happens after every clean install within 2 to 72 hours (I've done 5 clean installs now), but happens randomly with no apparent trigger. After a reboot, sometimes it would go back to normal, but eventually, it will happen again and cause the death loop I described above. It has happened even after a fresh install with no 3rd party apps/gapps/magisk installed, and has never occured with your other Lineage OS 15.1 ROM.
>>>A secondary problem:
If the phone is able to recover from the initial "lockscreen loop" after a reboot, the LED light for charging and notifications would stop working completely (same issue described by dragon170 above). Although, this issue is not important since the phone will stop booting into the OS soon after.
I would love to continue using this ROM as my daily driver if there's anyway to resolve this issue. Any advice would be greatly appreciated!
chasemedown said:
Thank you for creating a ROm with such great performance and battery life! HOWEVER, there is one critical bug that I have been encountering consistently, no matter how many times I wipe and clean install following the instructions exactly (I have the correct bootloader and gapps versions).
>>>What happens:
Sometimes, when I try to turn on the screen after it has timed out (using the home or power button), the lockscreen would rapidly blink between screen on and screen off, causing a "lockscreen loop" that prevents me from unlocking the phone. This would repeat infinitely, and the only thing I can do to get out of it is hold the power button and hit power off or restart if I time it correctly between the blinking. Once the phone restarts, it would usually go back to normal, but once in a while, the phone would reboot back into the exact same "lockscreen loop". When this happens, this loop NEVER stops, no matter how many times I reboot, so I am eventually forced to wipe/factory reset and reinstall the ROM again from scratch.
>>>How frequently/when does it happen:
This happens after every clean install within 2 to 72 hours (I've done 5 clean installs now), but happens randomly with no apparent trigger. After a reboot, sometimes it would go back to normal, but eventually, it will happen again and cause the death loop I described above. It has happened even after a fresh install with no 3rd party apps/gapps/magisk installed, and has never occured with your other Lineage OS 15.1 ROM.
>>>A secondary problem:
If the phone is able to recover from the initial "lockscreen loop" after a reboot, the LED light for charging and notifications would stop working completely (same issue described by dragon170 above). Although, this issue is not important since the phone will stop booting into the OS soon after.
I would love to continue using this ROM as my daily driver if there's anyway to resolve this issue. Any advice would be greatly appreciated!
Click to expand...
Click to collapse
for lockscreen loop preblem you can delet locksettings.db from twrp and will boot to system i had the problem before directory : data/system/locksettings.db
delete this file this way worked for me
don't forget to mount system
but you will need to resetting lock pattern
ammar mk said:
for lockscreen loop preblem you can delet locksettings.db from twrp and will boot to system i had the problem before directory : data/system/locksettings.db
delete this file this way worked for me
don't forget to mount system
but you will need to resetting lock pattern
Click to expand...
Click to collapse
Thank you very much!!! I just deleted locksettings.db and restarted; so far so good. Fingers crossed this resolves the issue permanently.
UPDATE: Deleting locksettings.db alone did not resolve the issue. HOWEVER, it lead me to figuring out the cause was a fingerprint scanner issue. I deleted data/system/user/0/settings_fingerprint.xml and stopped using the fingerprint scanner; everything is fine now!
chasemedown said:
Thank you very much!!! I just deleted locksettings.db and restarted; so far so good. Fingers crossed this resolves the issue permanently.
Click to expand...
Click to collapse
you welcome bro
Well i like the rom. I have a humble request to developers and team of the rom can you please add a additional lte band to it.. i need lte bnd 5 to be working on it. Thank you
chasemedown said:
Thank you for creating a ROm with such great performance and battery life! HOWEVER, there is one critical bug that I have been encountering consistently, no matter how many times I wipe and clean install following the instructions exactly (I have the correct bootloader and gapps versions).
>>>What happens:
Sometimes, when I try to turn on the screen after it has timed out (using the home or power button), the lockscreen would rapidly blink between screen on and screen off, causing a "lockscreen loop" that prevents me from unlocking the phone. This would repeat infinitely, and the only thing I can do to get out of it is hold the power button and hit power off or restart if I time it correctly between the blinking. Once the phone restarts, it would usually go back to normal, but once in a while, the phone would reboot back into the exact same "lockscreen loop". When this happens, this loop NEVER stops, no matter how many times I reboot, so I am eventually forced to wipe/factory reset and reinstall the ROM again from scratch.
>>>How frequently/when does it happen:
This happens after every clean install within 2 to 72 hours (I've done 5 clean installs now), but happens randomly with no apparent trigger. After a reboot, sometimes it would go back to normal, but eventually, it will happen again and cause the death loop I described above. It has happened even after a fresh install with no 3rd party apps/gapps/magisk installed, and has never occured with your other Lineage OS 15.1 ROM.
>>>A secondary problem:
If the phone is able to recover from the initial "lockscreen loop" after a reboot, the LED light for charging and notifications would stop working completely (same issue described by dragon170 above). Although, this issue is not important since the phone will stop booting into the OS soon after.
I would love to continue using this ROM as my daily driver if there's anyway to resolve this issue. Any advice would be greatly appreciated!
Click to expand...
Click to collapse
Try to disable AOD.
vm03 said:
Changelog
20190531:
- First public release
Possibly update from 15.1 without wipe:
1. install LineageOS 16.0
2. install gapps 9.0
3. reboot
Click to expand...
Click to collapse
Will a new update come for lineageos updates and bugs?
wifi dose not work again
ammar mk said:
for lockscreen loop preblem you can delet locksettings.db from twrp and will boot to system i had the problem before directory : data/system/locksettings.db
delete this file this way worked for me
don't forget to mount system
but you will need to resetting lock pattern
Click to expand...
Click to collapse
Same issue on my Galaxy Note 3.
I was able to get rid of the loop after deleting locksetting.db
Thank you sir!
S.
20190711:
- Fix USB and WiFi tethering
- mainstream LineageOS updates
thinhx2 said:
Can you tell me about nokia x2 ara?
Click to expand...
Click to collapse
msm8610 very-very old for current android world....
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Prerequisites
1. Unlocked bootloader.
Bugs
1. No tested yet, be the tester and,
2. If you have found a bug, please consider posting it to my GitHub Issues.
Instructions
1. Go to the fastboot mode.
2. Download the recovery.img and transfer it to the adb folder.
3. Open the cmd/terminal and change directory into the adb folder.
4. Now confirm/check that device is connected by typing:-
Code:
fastboot devices
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
Code:
fastboot flash recovery twrp-name.img
BooM ! TWRP flashed successfully.
6. Now unplug your device and then hold power button untill the phone turned off,after that press power button while holding vol down(-) button simultaneously and you will boot into TWRP recovery mode.
Enjoy !
Downloads
Test Build : https://androidfilehost.com/?fid=6006931924117887773
Official TWRP Website : Not submitted yet
Version Information
ROM OS Version: 9.0 Pie
Source Code: Device Tree
Based On: TWRP
Credits
Omni Team for minimal TWRP source
@chankruze (myself) for device tree and compilation.
SUPPORT
Official Telegram Group
Official Telegram Channel
Works very well. Just flashed the latest update with it. Thank you very much
Works real good so far.backed up,restored,formatted flash.everything I've tried so far works.was having trouble with forced encryption on stock rom but finally got past it.thanks for ur time to make this for community.
1. BlissOS latest GSI with device PIN selected during setup:
Data partition shows as 0mb in TWRP and asks for password to decrypt. Can't decrypt it with selected phone PIN.
Removing PIN from phone did not help either (still asked for password)
2. phh-AOSP 9v114 with device PIN and secure start-up selected during setup:
Data partition asks for pattern(?) to unlock in TWRP, even though pattern was not set.
Also the header at the top changes/flashes colors when on pattern screen.
3. Factory reset and setup with PIN but with secure start-up disabled:
This time it doesn't ask for pattern but password again. And can't decrypt with PIN.
4 .Factory reset again and setup without any kind of pin/pattern/password.
TWRP still asks for password to decrypt data.
5. Factory reset and setup pattern
TWRP asks for password
6. Repeat steps but this time with stock ROM from Umidigi. Same problems.
Code:
E:Decrypt took too long, killing process
Failed to decrypt data.
Unable to decrypt with default password. You may need to perform a Format Data
Unable to mount storage
Unable to mount /data/media/TWRP/.twrps
marcukial said:
was having trouble with forced encryption on stock rom but finally got past it
Click to expand...
Click to collapse
Why not share your solution?
@shookica
https://forum.xda-developers.com/showpost.php?p=79740894&postcount=263
marcukial said:
@shookica
https://forum.xda-developers.com/showpost.php?p=79740894&postcount=263
Click to expand...
Click to collapse
So you just flashed Magisk over stock ROM if I understand correctly from that post?
You say you flashed disable dm-verity but after that you restored from a full backup. That means the disable dm-verity package was removed anyway.
I tried flashing Magisk as well and even disabling persist force encrypt in Magisk app but that didn't solve my issue.
In any case I would like to be able to backup my data partition without flashing magisk and disable dm verity forceencrypt, simply by entering the password I set in Android.
That is how it is supposed to work anyway from my understanding.
shookica said:
So you just flashed Magisk over stock ROM if I understand correctly from that post?
You say you flashed disable dm-verity but after that you restored from a full backup. That means the disable dm-verity package was removed anyway.
I tried flashing Magisk as well and even disabling persist force encrypt in Magisk app but that didn't solve my issue.
In any case I would like to be able to backup my data partition without flashing magisk and disable dm verity forceencrypt, simply by entering the password I set in Android.
That is how it is supposed to work anyway from my understanding.
Click to expand...
Click to collapse
Yes.lol...i know that's what's so crazy.i gave up trying when I flashed the backup and just flashed magisk maybe something got left behind that didn't get wiped I don't know.i was shocked when I checked in settings/security and phone not encrypted. Rebooted to recovery and no password prompt all storage visible.
Code:
*** Disclamer
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
[B][U][SIZE="5"]Introduction[/SIZE][/U][/B]
[QUOTE]
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (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. 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.
LIneageOS 14.1 has now been ported from source and is available for the Brown 1. This ROM is not recommended to be used as a daily driver because of its issues. As usual do not hesitate to let us know of any issues regarding this ROM.
[/QUOTE]
[B][U][SIZE="5"]Installation instructions[/SIZE][/U][/B]
[QUOTE]
-- 1. Unlock the bootloader of your device on PC through ADB. Do a research about it on Google.
• Before proceeding, please make sure that you have already installed MediaTek USB Drivers on your PC, otherwise it will not work!
• Plug your Brown 1 to your PC
• Go to a folder, and right click to reveal the “Open Command Window Here” option by holding the “Shift” button and by clicking the right button of your mouse simultaneously.
• Type this line “adb reboot bootloader”
• Once your Brown 1 is in its bootloader, type this another line “fastboot oem unlock”
• Now, once it’s unlocked, It will erase everything stored in your phone’s Internal Storage. Please do a backup of your files first to avoid losing your files.
• Congrats, Bootloader is now unlocked!
2. After unlocking the bootloader, flash TWRP via PC.
• Before proceeding, please make sure that you have already downloaded all the files in your SD Card, otherwise, your Brown 1 will encounter a bootloop.
• Install MediaTek USB Drivers and “15 Second ADB Installer” from XDA.
• After installing. Download the PitchBlack Recovery File.
• Now, go to the folder where the pitchblack recovery is downloaded, and right click to reveal the “Open Command Window Here” option by holding the “Shift” button and by clicking the right button of your mouse simultaneously.
• Type this line “adb reboot bootloader”
• Your Brown 1 should boot now into its bootloader, now, type this line “fastboot flash recovery PBRP-2.9.0-20190119-V4701_I01-UNOFFICIAL.img”
• After that, type this line “fastboot boot PBRP-2.9.0-20190119-V4701_I01-UNOFFICIAL.img”
• Your Brown 1 should boot automatically to PitchBlack Recovery.
• Done!
3. Decrypt your phone.
• If you’re now on Pitch Black Recovery, ignore the “Enter your encryption password” dialogue, and then flash “Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip” from your SD Card to decrypt your Brown 1.
• After that, reboot your phone to recovery mode again, and then perform a factory reset.
• Done!
4. (OPTIONAL) Firmware Backup
• Click the “Backup” Button
• Swipe to perform the action
• Done! You can use this backup file when you encountered a bootloop, or something like that.
5. Flash Lineage OS 14.1
• Root first, Flash "Magisk (v18.0).zip" on PitchBlack Recovery
• After that, Click the “Wipe” button
• Perform a clean wipe by clicking the “Advanced” button and ticking system, data, dalvik and cache. Do not wipe your SD Card or your Internal Storage.
• Locate where the Custom ROM is stored and look for this file “lineage-14.1-20190525-UNOFFICIAL-V4701_I01.zip"
• And then, Flash it.
• After flashing it, flash Google Apps by looking for “open_gapps-arm64-7.1-mini-20190119.zip”
•After flashing Google Apps, flash Magisk again to obtain root access, look for "Magisk (v18.0).zip"
• After flashing all those files, reboot your system and enjoy!
• Congratulations! You have now flashed Lineage OS 14.1 on your Brown 1! Please take note that first boot will take 5 to 10 minutes, so please be patient.
[/QUOTE]
[B][U][SIZE="5"]Changelog[/SIZE][/U][/B]
[QUOTE]
[CODE]
Current changelog: -- v1.0 (20190525)
[note] -- • First Initial Release
• March 2019 Security Patch from Sources
• Based from Nokia 3
What's working?
-- - Connectivity
• Wi-Fi
• Bluetooth
• Hotspot
• RIL
• SIM Cards
• LTE Connectivity
- Miscellaneous
• Audio
• Flashlight
• Some Sensors
• Offline Charging (No Glitches)
- Recording
• Screen Recorder (Both in-built and app built)
• Audio Recorder
• Screen Capture
- Others
• Almost Everything Works
Click to expand...
Click to collapse
What are the bugs?
-- - Minor
• Camera - There's issues you might face when recording in video mode; The Camera app force closes once the mode's been changed to video mode
• Music App - The Application force closes everytime you open it. There will be a patch soon.
• FM Radio - The Application force closes everytime you open it.
• MTP Host - The Application force closes.
• CM Audio Service - The Application force closes.
- Major
• Android Application Installation - You won't be able to finish the installation of an application from Google Play Store or Android Package Installer if an error pops-up. The solution to install an application is to reboot the device everytime you encounter an error. There's no fix for this bug this time.
• Fingerprint Sensor - The fingerprint sensor of your phone won't be able to detect your fingerprint even when you point it to the sensor. There will be a patch soon.
Click to expand...
Click to collapse
Download
-- Lineage OS 14.1 for brown 1 (V4701_I01)
https://www.mediafire.com/file/jt2jf5sqc4xcg8q/lineage-14.1-20190525-UNOFFICIAL-V4701_I01.zip/
Click to expand...
Click to collapse
Credits
Code:
* • Lineage OS Team – For the continuation of the CyanogenMod Project; for developing this AOSP based ROM
* • Optimitist ROM Portings (My Team) – For distributing the ROM that I ported
* • Brahm Daniel Verano (me) – For making this possible to Brown 1 and MediaTek MT6735 devices
XDA:DevDB Information
Lineage OS 14.1 for brown 1, ROM for all devices (see above for details)
Contributors
LiaFourté, Team Xenomorph
ROM OS Version: 7.1.x Nougat
ROM Kernel: Linux 3.18.x
ROM Firmware Required: Stock Firmware
Based On: Lineage OS
Version Information
Status: Alpha
Current Stable Version: v1.5 FINAL (20190905)
Stable Release Date: 2019-09-05
Current Beta Version: v1.1 (20190725)
Beta Release Date: 2019-07-25
Created 2019-06-09
Last Updated 2020-08-13
[ROM][UNOFFICIAL][9.0] LineageOS 16.0 for Galaxy J4+ & J6+ [j4primelte & j6primelte]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (oreo), 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.
What's working :
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
GPS
NFC
Fingerprint on J6+
Sim slots
Flashlight
Mobicore keystore
Known issues:
VoLTE
Selinux is permissive
Instructions :
If you're on oreo, flash OneUI latest.
Download the latest build.
Reboot to recovery
Flash the latest build.
Optional: Flash GApps for Google Services and Magisk for root.
Reboot
Downloads :
All updates will be here.
Sources :
Device Tree
Vendor Blobs
Kernel Source
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0] LineageOS 16.0 for Galaxy J4+/J6+ [j4primelte & j6primelte], ROM for the Samsung Galaxy J4+
Contributors
ataberkozen
Source Code: https://github.com/lineageos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Pie, OneUI
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2020-01-29
Current Beta Version: 1.0
Beta Release Date: 2019-06-26
Created 2019-06-25
Last Updated 2020-01-29
Changelogs :
Stable version 1 - 29/01/2020 :
Now we are building vendor too. Goodbye OneUI vendor.
Happy news to J6+ users: my builds are now supporting j6primelte.
NFC is fixed on NFC variants.
Keystore is now fixed and got rid of aosp's software implementation. You don't need any hacks or tricks to make it work on GSIs.
SIM count detection added, single sim users won't have annoying second sim.
Previous build had dead flashlight sometimes. Fixed.
Removed Samsung's bloatwares.
RIL working delay after boot fixed.
And so much more that I did in past couple of months that I don't remember.
Public Beta 4 - 18/08/2019 :
MTP totally fixed.
Added FM Radio.
NFC should work now on FN users (Current device I have isn't NFC variant. I am not sure).
Public Beta 3 - 27/06/2019 :
Added USB and Bluetooth tethering.
Public Beta 2 - 26/06/2019 :
Lockscreen password fixed.
Audio on camcorder(video recording) fixed.
Autobrightness fixed.
Hotspot fixed.
MTP fixed.
Second SIM Slot fixed.
Public Beta 1 - 25/06/2019 :
First release.
Thanks to abhishek987 for thread template.
Screenshots on attachment.
Note(s) :
Send me logs if you've find any bug.
Reserved for just-in-case.
Please give me credits while building roms and sharing with my sources.
By hitting thanks button and following me on GitHub you can make me happy. Have fun!
Wow just wanna say thanks for this. But based on this sentence by you: "If you're on oreo, flash OneUI latest."
Does it mean that we need to upgrade it to Samsung Android Pie first?
Andhika24kd said:
Wow just wanna say thanks for this. But based on this sentence by you: "If you're on oreo, flash OneUI latest."
Does it mean that we need to upgrade it to Samsung Android Pie first?
Click to expand...
Click to collapse
Yes.
New update released. Enjoy.
ataberkozen said:
New update released. Enjoy.
Click to expand...
Click to collapse
hi ataberkozen.i must say thank you for this rom.i flash it today and is boot and all work. i have few questions if i may. in your device tree is write that architeture is armv7-a-neon,but when i compile rom then is warning about a53 is armv8-a-neon(not error just warning).,thats ok,i add line for armv8-a-neon and now is ok. then no vendorsetup.sh in device tree.dont be mad is just observation from my side.btw thank you very much for device tree,vendor tree and kernel for this device.:good: btw for people who want flash this device do as: Must be on pie;when flash twrp go to format data,write yes,go to advance wipe and wipe dalvik,cache,system,data;then Flash RMM Bypass and forceencrypt disabler and then flash rom and magisk.reboot.as i hate gapps i dont flash it.once again thanks on rom and other stuff and your hard work.
rudi021 said:
hi ataberkozen.i must say thank you for this rom.i flash it today and is boot and all work. i have few questions if i may. in your device tree is write that architeture is armv7-a-neon,but when i compile rom then is warning about a53 is armv8-a-neon(not error just warning).,thats ok,i add line for armv8-a-neon and now is ok. then no vendorsetup.sh in device tree.dont be mad is just observation from my side.btw thank you very much for device tree,vendor tree and kernel for this device.:good: btw for people who want flash this device do as: Must be on pie;when flash twrp go to format data,write yes,go to advance wipe and wipe dalvik,cache,system,data;then Flash RMM Bypass and forceencrypt disabler and then flash rom and magisk.reboot.as i hate gapps i dont flash it.once again thanks on rom and other stuff and your hard work.
Click to expand...
Click to collapse
Are you also building a ROM?
Geckyn said:
Are you also building a ROM?
Click to expand...
Click to collapse
yes.i build roms.i build also few gsi for j4+ just for test.but mostly for mtk devices.is my first samsung device.is my hobby. i have 55 years.
ataberkozen said:
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (oreo), 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.
What's working :
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
GPS
Known issues:
VoLTE
Selinux is permissive
Instructions :
If you're on oreo, flash OneUI latest.
Flash RMM Bypass and forceencrypt disabler from TWRP thread.
Download the latest build and GApps
Reboot to recovery
Flash the latest build and GApps
Optional: Flash magisk for root.
Reboot
Downloads :
All updates will be here.
Sources :
Device Tree
Vendor Blobs
Kernel Source
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0] LineageOS 16.0 for Galaxy J4+ [j4primelte], ROM for the Samsung Galaxy J4+
Contributors
ataberkozen
Source Code: https://github.com/lineageos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Pie, OneUI
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2019-06-26
Created 2019-06-26
Last Updated 2019-06-25
Click to expand...
Click to collapse
I tried to flash this on my SM-J415GN . It says on TWRP. "Size of image is larger than target device." How do i fix this? Thank you.
edit. I'm just dumb so uh nvm this. Lol
Necrosis Virus said:
I tried to flash this on my SM-J415GN . It says on TWRP. "Size of image is larger than target device." How do i fix this? Thank you.
edit. I'm just dumb so uh nvm this. Lol
Click to expand...
Click to collapse
Some notes and bugs encountered by me on J415F:
1) No face unlock option even after flashing GApps. Workaround: use other screen lock method
2) SIM 2 will be named as 'CARD 2' instead of its real name on many occasions. Workaround: Change your SIM 2 name manually from Settings -> Network & internet -> SIM Cards -> SIM slot 2. This may happen because your SIM carrier is unrecognized by Android
3) Samsung Pay and Samsung Max are there. Workaround: Remove the APKs manually using File Manager that supports root feature. They are located inside ./odm/app
4) If Android cant 'sign in to network' on SIM 1. It will display an error referring to SIM 2's name. It will also use mobile data from SIM 2 instead (pic 1, pic 2). No workaround
5) Bluelight filter not working (won't change settings). Workaround: Use 3rd party app to filter it (such as CF.Lumen)
6) Saved screenshot shows a blank preview image (on notification list). No workaround
7) Removing system apps cause bootloop. Workaround: Just disable it or use ADB to uninstall it instead (current user only)
8) MTP/PTP still not working, will show an error when copying files. Workaround: Use 3rd party file sharing apps like ShareIt or AirMore
9) Download manager is buggy, taking long time or failed to download something (for example Magisk module), or download file with strange name (instead of its real name on Jelly browser). Workaround: Restart the device at least once or use other browser like Chrome or Firefox (Lite)
10) 'Files' app shows an error when renaming file (but it actually works). No workaround
11) Bluetooth keeps stoping when accessed/enabled by apps (example: Google Play Games). No workaround?
12) When setting navigation bar to compact mode (or other mode), the 'change rotation' button (if you don't use auto rotate) will appear behind/on top of/in the middle of other navigation buttons. Workaround: Use the default one or use 'Gesture' navigation bar instead. This may happen if you change your screen 'Display size' (aka DPI) from Settings -> Display
13) Changing navigation bar to lefty/righty may cause the navigation bar to disappear. Workaround: Reboot the device at least once or use the same workaround as above
14) Changing home screen wallpaper will also change lock screen wallpaper and using custom image as wallpaper will cause the default 'Wallpaper' app to crash. Workaround: Use other app to change wallpaper (such as Google Wallpaper app)
15) Lock screen message does not appear, although emergency message/info works fine. Workaround: Change it and save it again (for the second time), if the problem stays reboot the device at least once
16) Keyboard will not appear on some conditions (like when writing app review on Play Store) and cause heavy lag or screen blinking. Workaround: Press home button and kill the 'hanging' app. Install alternative keyboard (such as G-Board or Simple Keyboard)
17) Changing accent color (from Settings -> Display -> Style) will not change 'Trebuchet' launcher accent color. Workaround: Change it to other color and save it again. If the problem persist force stop the launcher or reboot the device
18) 'Trebuchet' launcher is using light theme even after I change the system style color to Dark/AMOLED. Workaround: Change your wallpaper to a darker one
19) Notifications are still on white color even after I change the system style color to Dark/AMOLED. Workaround: Use 3rd party theming app (such as Substratum) or Xposed module or whatever
20) Signal bar is empty on both SIMs but mobile data, SMS, and phone work fine. No workaround?
21) Some apps notifications (like Messaging app) will be delayed or not showing up at all if 'Do no disturb' mode is activated. Workaround: Check it manually, of course
22) Minor UI bugs here and there that doesn't affect anything (maybe also DPI related issue) (pic 1, pic 2, pic 3). No workaround?
Some of this may be features/limitations of AOSP and LineageOS, not actually bugs. Tested on beta 3 release, will always update this post once I found new bugs. Thanks for the ROM by the way. Cheers
Andhika24kd said:
1) No face unlock option even after flashing GApps. Workaround: use other screen lock method
2) SIM 2 will be named as 'CARD 2' instead of its real name on many occasions. Workaround: Change your SIM 2 name manually from Settings -> Network & internet -> SIM Cards -> SIM slot 2. This may happen because your SIM carrier is unrecognized by Android
3) Samsung Pay and Samsung Max are there. Workaround: Remove the APKs manually using File Manager that supports root feature. They are located inside ./odm/app
4) If Android cant 'sign in to network' on SIM 1. It will display an error referring to SIM 2's name. It will also use mobile data from SIM 2 instead (pic 1, pic 2). No workaround
5) Bluelight filter not working (won't change settings). Workaround: Use 3rd party app to filter it (such as CF.Lumen)
6) Saved screenshot shows a blank preview image (on notification list). No workaround
7) Removing system apps cause bootloop. Workaround: Just disable it or use ADB to uninstall it instead (current user only)
8) MTP/PTP still not working, will show an error when copying files. Workaround: Use 3rd party file sharing apps like ShareIt or AirMore
9) Download manager is buggy, taking long time or failed to download something (for example Magisk module), or download file with strange name (instead of its real name on Jelly browser). Workaround: Restart the device at least once or use other browser like Chrome or Firefox (Lite)
10) 'Files' app shows an error when renaming file (but it actually works). No workaround
11) Bluetooth keeps stoping when accessed/enabled by apps (example: Google Play Games). No workaround?
12) When setting navigation bar to compact mode (or other mode), the 'change rotation' button (if you don't use auto rotate) will appear behind/on top of/in the middle of other navigation buttons. Workaround: Use the default one or use 'Gesture' navigation bar instead. This may happen if you change your screen 'Display size' (aka DPI) from Settings -> Display
13) Changing navigation bar to lefty/righty may cause the navigation bar to disappear. Workaround: Reboot the device at least once or use the same workaround as above
14) Changing home screen wallpaper will also change lock screen wallpaper and using custom image as wallpaper will cause the default 'Wallpaper' app to crash. Workaround: Use other app to change wallpaper (such as Google Wallpaper app)
15) Lock screen message does not appear, although emergency message/info works fine. Workaround: Change it and save it again (for the second time), if the problem stays reboot the device at least once
16) Keyboard will not appear on some conditions (like when writing app review on Play Store) and cause heavy lag or screen blinking. Workaround: Press home button and kill the 'hanging' app. Install alternative keyboard (such as G-Board or Simple Keyboard)
17) Changing accent color (from Settings -> Display -> Style) will not change 'Trebuchet' launcher accent color. Workaround: Change it to other color and save it again. If the problem persist force stop the launcher or reboot the device
18) 'Trebuchet' launcher is using light theme even after I change the system style color to Dark/AMOLED. Workaround: Change your wallpaper to a darker one
19) Notifications are still on white color even after I change the system style color to Dark/AMOLED. Workaround: Use 3rd party theming app (such as Substratum) or Xposed module or whatever
20) Signal bar is empty on both SIMs but mobile data, SMS, and phone work fine. No workaround?
21) Some apps notifications (like Messaging app) will be delayed or not showing up at all if 'Do no disturb' mode is activated. Workaround: Check it manually, of course
22) Minor UI bugs here and there that doesn't affect anything (maybe also DPI related issue) (pic 1, pic 2, pic 3). No workaround?
Some of this may be features/limitations of AOSP and LineageOS, not actually bugs. Tested on beta 3 release, will always update this post once I found new bugs. Thanks for the ROM by the way. Cheers
Click to expand...
Click to collapse
1-) OpenGApps telegram group aware of this problem, wait for them.
2-) Prepaid doesn't show for me too, but others shows.
3-) I'll disable it later.
4-) Send logs from telegram.
5-) I forgot to add lineage livedisplay while creating tree. I'll add next update.
6-) SkiaGL problematic on sd425, 425 phones are using opengl. I had to choose between fixing lags and other ui problems or working screenshot. I choose first one.
7-) You said yourself, removing system apps causes bootloop.
I'll fix it later.
9-) IDK is it problem or not but i am pretty sure isn't bcz of me.
10-) Same 9.
11-) I didn't faced problem while sending mp3, but if u you can send logs i'll check.
12-) Not my problem.
13-) Not bcz of me.
14-) I didn't faced but it's app bug really not my problem.
15-) Not my problem 2.
16-) You said yourself install gboard.
17-) Accent colors is overlay based. Bug isn't from my side.
1 App feature missing or buggy. Idk java I cannot fix.
19-) It's not problem by me, even official devices same.
20-) I am aware of this problem. I need to find a way to change it to rssi.
21-) Isn't this point of DND ? I am busy don't send me any notifications ?
22-) Set ro.lcd.density to 280 with build.prop editor and report back.
Sorry I'm quiet busy nowadays (and I'm sure you are). I will upload the log (you mean logcat, right?) when I have time. Yeah, some of these bugs are actually features on AOSP/LineageOS, I'm just informing other users in case it's their first time switching from Samsung ROM to LineageOS or AOSP based ROM.
11) I didn't use the Bluetooth directly, Google Play Games used it to find a match with nearby player on the game "Bowmasters", will send logcat later.
16) Installing Gboard doesn't help, I already tried that 3-4 days ago.
19) Yes, I'm just informing the others in case they never tried LineageOS/AOSP before. However some unofficial LineageOS have that. Of course I'm not asking you to make/merge it, I don't care about themes.
22) Setting it to 280 doesn't help so far, but I think I need more time to see if it works or not.
Andhika24kd said:
8) MTP/PTP still not working, will show an error when copying files. Workaround: Use 3rd party file sharing apps like ShareIt or AirMore
Click to expand...
Click to collapse
This is a real show-stopper.
@ataberkozen :
When you hopefully fix this soon, will I be able to simply flash your new ROM version on top of the current one, or will I have to clean flash the phone first ?
breversa said:
This is a real show-stopper.
@ataberkozen :
When you hopefully fix this soon, will I be able to simply flash your new ROM version on top of the current one, or will I have to clean flash the phone first ?
Click to expand...
Click to collapse
I fixed it yesterday, a new update expected today. Yes you can flash dirty.
Awesome work, @ataberkozen ! I can't wait !
---------- Post added at 13:20 ---------- Previous post was at 12:37 ----------
ataberkozen said:
I fixed it yesterday, a new update expected today. Yes you can flash dirty.
Click to expand...
Click to collapse
Now that's weird… I installed lineage-16.0-20190627-UNOFFICIAL-j4primelte while waiting for your new build, but MTP works without problem… I'm confused ! ^^
However, I can't connect to any hidden wifi. Seems to be an Android 9 issue though, as I encountered the same issue earlier today with another Android 9 ROM*: https://forum.xda-developers.com/showpost.php?p=79888858&postcount=10
breversa said:
Awesome work, @ataberkozen ! I can't wait !
---------- Post added at 13:20 ---------- Previous post was at 12:37 ----------
Now that's weird… I installed lineage-16.0-20190627-UNOFFICIAL-j4primelte while waiting for your new build, but MTP works without problem… I'm confused ! ^^
However, I can't connect to any hidden wifi. Seems to be an Android 9 issue though, as I encountered the same issue earlier today with another Android 9 ROM*: https://forum.xda-developers.com/showpost.php?p=79888858&postcount=10
Click to expand...
Click to collapse
MTP fails while copying from phone to pc.