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.
It 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.
{
"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:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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.
*
*/
This thread is for Official LineageOS 14.1 builds for k3gxx (SM-G900H). The following will not be supported here:
Custom kernels
Mods
Xposed
Magisk
I don't support Xposed/Magisk and any logcat which includes a Xposed/Magisk module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Install the Google Apps addon package (Optional)
Reboot
k3gxx Downloads
Google Apps:
http://opengapps.org/
Want Root access? Flash this!
LineageOS SU Addon
Flahed the SU Addon and now you want to remove it? Flash this!
LineageOS su addon Remover
07/09/2017
*Initial Release
*Reproducing videos with the camer app does not work. You must reproduce them from the gallery!
*Sharing videos on apps like WhatsApp or Snapchat does not work (this bug affects all the exynos5 family)
*You tell me!
Other issues?
Before posting in this thread, make sure of a few things:
You used the search function of the forums.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread.
Logs! You can use this: https://play.google.com/store/apps/d....tortel.syslog
@UpInTheAir for his kernel magic and misc fixes
@crpalmer (for picassowifi device and kernel gits)
@eousphoros (for his work on klimtwifi)
@nvertigo67 (for his work on chagallwifi)
@Nexorrr (for his work on chagalllte)
Exynos5420 Dev Team (@deadman96385 @thompatry @ZakooZ @Orion116 @mosimchah
@joshndroid @Andmoreagain @thermskin, @javelinanddart, @tincho5588)
Exynos5422 Dev Team (somadsul, hunnymadaan, griffin98)
Source Code:
Kernel
https://github.com/lineageos/android_kernel_samsung_k3gxx/tree/cm-14.1
Device Tree
https://github.com/lineageos/android_device_samsung_k3gxx/tree/cm-14.1
XDA:DevDB Information
[7.1.x|SM-G900H| Official LineageOS 14.1 (k3gxx), ROM for the Samsung Galaxy S5
Contributors
tincho5588
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: MM Bootloader
Based On: LineageOS
Version Information
Status: Stable
Created 2017-09-08
Last Updated 2017-09-08
Reserved
Want Root access??
Just flash with TWRP the LineageOS SU Addon zip file found on the download section... Flash it after you have flashed Google Apps!!!
Then enable the developer options menu with this guide:
To enable Developer Options, open the Settings screen, scroll down to the bottom, and tap About phone or About tablet.
Scroll down to the bottom of the About screen and find the Build number.
Tap the Build number field seven times to enable Developer Options. Tap a few times and you’ll see a toast notification with a countdown that reads “You are now X steps way from being a developer.”
When you’re done, you’ll see the message “You are now a developer!”. Congratulations. Don’t let this newfound power go to your head.
Tap the Back button and you’ll see the Developer options menu just above the “About Phone” section in Settings. This menu is now enabled on your device—you won’t have to repeat this process again unless you perform a factory reset.
Now go into the developers options menu and find the option to enable root access!!
Flashed the SU Addon and now you want to remove it from your phone??
Just download the LineageOS SU Addon remover and flash it with TWRP...
OTAs aren't working!! How do I fix this?!
Chillax... You need to update your TWRP recovery for the OTAs to work...
Please go to the TWRP k3gxx Page with this link and download the last version (twrp-3.1.1-1)
Reserved
Information about the kernel and its features will be added here soon...
Great effort man
Thanks mate
Thanks for your work. The bedt rom ever!!! But, I cant download big apps such as pes 2017. It download required files first then stucks at "downloading". What is the problem? Rom related or not? I have enough storage :/
You are the best.. :good::good:
Thank you for your effort and making our device alive again.. :victory:
Great work and congrats on official! I can finally unify my devices.
Except...
This is now the 4th rom that has a problem with sim cards. Is this a know thing? Are there any workarounds?
I will be more than happy to pass any logcat or debug file along (link to logger in post #1 not working). But I find it really interesting that with the latest batch of N roms for the G900h, they all have the same sim card issue.
And please do not tell me to try and insert the sim card WHILE the device is on.
---------- Post added at 08:29 PM ---------- Previous post was at 08:07 PM ----------
Info I can give right off the bat:
Device is G900h (k3gxx)
SIM Card is for Mobile Telephone Networks (MTN) South Africa (655-10)
Previous ROM: RR N 5.8.4-20170815
Advanced wipe: System, data, cache, dalvik
Flashed ROM found on official LoS site
Flashed GApps 7.1 arm nano
Wiped dalvik
Reboot
Device during setup does not detect presence of SIM card.
Additional steps after completing setup:
Powered off device
Removed SIM card
Booted device without SIM card in
Powered off device
Replaced SIM card and booted
SIM card still not detected
From setting, Network settings reset. No effect.
Logcat for network:
Code:
09-08 22:15:12.770 4026 4026 E ConnectivityService: Error in networkAttributes - ignoring attempt to define type 23
09-08 22:15:14.321 4026 4026 W LocationProviderProxy-network: Odd, no component found for service com.android.location.service.v3.NetworkLocationProvider
09-08 22:15:19.643 4026 4061 W LocationProviderProxy-network: Odd, no component found for service com.android.location.service.v3.NetworkLocationProvider
09-08 22:15:35.610 4789 5265 E ctxmgr : [BaseServerTask]Failed network request due to no network connectivity:
09-08 22:15:35.613 4789 5265 E ctxmgr : [SyncServerInterestRecordsOperation]Failed WriteInterestRecord: network status=1
09-08 22:16:16.239 5481 5481 I Finsky : [1] com.google.android.finsky.verifier.impl.VerifyInstalledPackagesReceiver.a(31): Skipping verification because network inactive
09-08 22:17:46.087 4789 5871 E ctxmgr : [BaseServerTask]Failed network request due to no network connectivity:
09-08 22:17:46.094 4789 5871 E ctxmgr : [SyncServerInterestRecordsOperation]Failed WriteInterestRecord: network status=1
SIM card still not detected.
---------- Post added at 08:36 PM ---------- Previous post was at 08:29 PM ----------
Additional issue detected:
Usually I skip the Google Assistant initial setup during device first boot just to get through it.
Device does not hear "Okay Google" keyword as well as being able to use voice search (from hotword or pressing the mic button).
Tested mic on sound recorder, low volume but audible. Tested with Video Camera, low volume but audible.
ka13b said:
Great work and congrats on official! I can finally unify my devices.
Except...
This is now the 4th rom that has a problem with sim cards. Is this a know thing? Are there any workarounds?
I will be more than happy to pass any logcat or debug file along (link to logger in post #1 not working). But I find it really interesting that with the latest batch of N roms for the G900h, they all have the same sim card issue.
And please do not tell me to try and insert the sim card WHILE the device is on.
---------- Post added at 08:29 PM ---------- Previous post was at 08:07 PM ----------
Info I can give right off the bat:
Device is G900h (k3gxx)
SIM Card is for Mobile Telephone Networks (MTN) South Africa (655-10)
Previous ROM: RR N 5.8.4-20170815
Advanced wipe: System, data, cache, dalvik
Flashed ROM found on official LoS site
Flashed GApps 7.1 arm nano
Wiped dalvik
Reboot
Device during setup does not detect presence of SIM card.
Additional steps after completing setup:
Powered off device
Removed SIM card
Booted device without SIM card in
Powered off device
Replaced SIM card and booted
SIM card still not detected
From setting, Network settings reset. No effect.
Logcat for network:
Code:
09-08 22:15:12.770 4026 4026 E ConnectivityService: Error in networkAttributes - ignoring attempt to define type 23
09-08 22:15:14.321 4026 4026 W LocationProviderProxy-network: Odd, no component found for service com.android.location.service.v3.NetworkLocationProvider
09-08 22:15:19.643 4026 4061 W LocationProviderProxy-network: Odd, no component found for service com.android.location.service.v3.NetworkLocationProvider
09-08 22:15:35.610 4789 5265 E ctxmgr : [BaseServerTask]Failed network request due to no network connectivity:
09-08 22:15:35.613 4789 5265 E ctxmgr : [SyncServerInterestRecordsOperation]Failed WriteInterestRecord: network status=1
09-08 22:16:16.239 5481 5481 I Finsky : [1] com.google.android.finsky.verifier.impl.VerifyInstalledPackagesReceiver.a(31): Skipping verification because network inactive
09-08 22:17:46.087 4789 5871 E ctxmgr : [BaseServerTask]Failed network request due to no network connectivity:
09-08 22:17:46.094 4789 5871 E ctxmgr : [SyncServerInterestRecordsOperation]Failed WriteInterestRecord: network status=1
SIM card still not detected.
---------- Post added at 08:36 PM ---------- Previous post was at 08:29 PM ----------
Additional issue detected:
Usually I skip the Google Assistant initial setup during device first boot just to get through it.
Device does not hear "Okay Google" keyword as well as being able to use voice search (from hotword or pressing the mic button).
Tested mic on sound recorder, low volume but audible. Tested with Video Camera, low volume but audible.
Click to expand...
Click to collapse
full logcat please... that small chunk contains nothing relevant...
anyway, RIL works fine for everybody else... are you sure your EFS partition is OK? if it is broken, rip...
tincho5588 said:
full logcat please... that small chunk contains nothing relevant...
anyway, RIL works fine for everybody else... are you sure your EFS partition is OK? if it is broken, rip...
Click to expand...
Click to collapse
I will provide a full logcat within the next few hours (I gotta get some sleep)
Previous ROM worked fine, so I'm not sure if my EFS partition is at play here.
I have noted that I have seen a few people using other ROMs (not with this ROM [yet?]) say after flashing that have no signal/no SIM card detected. It may be an isolated instance or it could be something in a shared library (though I may be wrong).
tincho5588 said:
full logcat please... that small chunk contains nothing relevant...
anyway, RIL works fine for everybody else... are you sure your EFS partition is OK? if it is broken, rip...
Click to expand...
Click to collapse
See attached logs.
ka13b said:
I will provide a full logcat within the next few hours (I gotta get some sleep)
Previous ROM worked fine, so I'm not sure if my EFS partition is at play here.
I have noted that I have seen a few people using other ROMs (not with this ROM [yet?]) say after flashing that have no signal/no SIM card detected. It may be an isolated instance or it could be something in a shared library (though I may be wrong).
Click to expand...
Click to collapse
Just flashed the official build to test it out... I really didn't have time to test it before, but I correctly assumed everything works cause it is built with the same trees as the unofficial builds...
The RIL works fine on my device... so you have a problem in your phone mate...
tincho5588 said:
Just flashed the official build to test it out... I really didn't have time to test it before, but I correctly assumed everything works cause it is built with the same trees as the unofficial builds...
The RIL works fine on my device... so you have a problem in your phone mate...
Click to expand...
Click to collapse
Anything you can see from the logs provided in post #10?
ka13b said:
Anything you can see from the logs provided in post #10?
Click to expand...
Click to collapse
No, I need a full log... if you can get the logs with syslog it is better... so I get to see the modem log and the kmesg...
The issue will most likely pop up in the modem log...
tincho5588 said:
No, I need a full log... if you can get the logs with syslog it is better... so I get to see the modem log and the kmesg...
The issue will most likely pop up in the modem log...
Click to expand...
Click to collapse
That was taken using Syslog. All logs zipped up neatly. At any rate, I'll run it again and upload i shortly.
[If I am doing something wrong, my apologies, new field for me (bug logging that is)]
tincho5588 said:
No, I need a full log... if you can get the logs with syslog it is better... so I get to see the modem log and the kmesg...
The issue will most likely pop up in the modem log...
Click to expand...
Click to collapse
Attached, please find Modem, kmsg and a zip of all the additional logs generated by Syslog.
If you need something else, just give a shout (I'll get this process right one say )
ka13b said:
Attached, please find Modem, kmsg and a zip of all the additional logs generated by Syslog.
If you need something else, just give a shout (I'll get this process right one say )
Click to expand...
Click to collapse
will check it out when I get back home... heading to college right now! got a math exam... wish me luck :laugh:
tincho5588 said:
will check it out when I get back home... heading to college right now! got a math exam... wish me luck :laugh:
Click to expand...
Click to collapse
GL HF :good::good:
ka13b said:
Attached, please find Modem, kmsg and a zip of all the additional logs generated by Syslog.
If you need something else, just give a shout (I'll get this process right one say )
Click to expand...
Click to collapse
Are you sure you cleaned flashed the ROM, no backups restored from TWRP, and the most important of all, no mods? your log is weird, you have selinux denials... but I wrote rules for those files, so something weird is going on here...
I want to fix voip calls for a3xelte (a3 2016) exynos 7580 on LOS 14.1! Any idea how to fix the problem? There is no output from earpiece or speaker. @tincho5588
xEmre66 said:
I want to fix voip calls for a3xelte (a3 2016) exynos 7580 on LOS 14.1! Any idea how to fix the problem? There is no output from earpiece or speaker. @tincho5588
Click to expand...
Click to collapse
Send me a link to your trees on a private message and i will check it out!
Related
{
"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"
}
CyanogenMod 13 for the Samsung Galaxy Tab 4 7.0 LTEBy Hennymcc and CTXz
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
CyanogenMod 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). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Before you start
This ROM is only for the T235 and T235Y
Code:
*
* Your warranty will be voided !
*
* 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.
*
Special Thanks
@hennymcc For his huge effort and contributions on Exynos 3470 related devices
@tyktak For the testing
And of course the entire CyanogenMod team!
What is Fixed
Incoming Calls
Red flashy frames
Lock Screen
CM setup Wizard
Google Setup Wizard
RIL (SIM Detection)
Youtube
Videos
Wifi
What is not working
Auto Rotate stops working after some time
Unswitchable preffered networks (Stuck on 3g but actually LTE)
SElinux
Instructions
How to install CM 13
If you don't have TWRP yet, get it from here : TWRP 3.0.0 for Samsung Galaxy Tab 4 7.0 LTE
Download the ROM and the Gapps that are located below on to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home
WARNING : The next three steps WILL delete all your your data but not your internal storage
Select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home
Select install and locate the ROM zip
After you selected the ROM select add more zips and select your Gapps zip
Finally swipe to install
When all of this is done, reboot into system, wait, and enjoy CyanogenMod 13 on your Galaxy Tab 4 7.0 LTE
How to ROOT
In CM 13, enable the developer options
Select Root access
Select Apps Only (Or Apps and ADB if you use ADB)
Done
Downloads
Lastest recommended CyanogenMod release for the Galaxy Tab 4 7.0 LTE T235 : ROM
All my releases can be found here : Android File Host
Gapps : Open Gapps
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Requests for other devices
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Change Log
Code:
2016/3/19
- Fixed incoming calls
- Synced to newest CM sources
2016/3/13
- Synced to newest CM sources
2016/3/13
- Fixed RIL (SIM detection)
- Updated to Lollipop Kernel
2016/3/10
- Fix Crash on CM and Google setup Wizzard
2016/2/28
- Switch from -eng to -userdebug
- Fixed Wifi
- Fixed CM Wizzard crash
- Fixed Lockscreen (Crash after entering sleep)
- Fixed Youtube Videos Crashing
- Fixed Videos freezing device
- Removed Flashy frames (By switching from -eng to -userdebug)
2016/2/27 - CM released
Screen Shots
XDA:DevDB Information
CyanogenMod 13 For Samsung Galaxy Tab 4 7.0 LTE, ROM for the Samsung Galaxy Tab 4
Contributors
CTXz, hennymcc
Source Code: https://github.com/cm-3470
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Beta
Created 2016-02-27
Last Updated 2016-03-19
Reserved
Q&A
Q: Will this work on T2XX
A: This build is ONLY for the LTE variant of the 4 inch tab. I have not tried if this rom works on the T235Y (should probably work though). However the LTE version has an Exynos 3470 where else the Wifi version has a Marvell chip (I have some bad experience with that chip *cough* attempt to get CM working on it *cough*). PLEASE DO NOT TRY TO FLASH THIS ON ANY OTHER DEVICE THAN THE T235 OR T235Y.
Q: What about the T230!!!
A: As mentioned in my TWRP thread. Sub77 will send me a T230, and I can give it a shot again to build at least CM11 on it.
Q: How long till <insert issue here> gets fixed
A: ETA's (Short for Estimated Time of Arrival) aren't tolerated that well on XDA. Please remember that this is only a hobby!
Reserved
Looking forward to run this on my SM-T235. Only if it isn't Monday tomorrow, i would test run this ROM.
New build released, links have been updated!
Code:
2016/2/28
- Switch from -eng to -userdebug
- Fixed Wifi
- Fixed CM Wizzard crash
- Fixed Lockscreen (Crash after entering sleep)
- Fixed Youtube Videos Crashing
- Fixed Videos freezing device
- Removed Flashy frames (By switching from -eng to -userdebug)
If RIL isn't working yet, i assume one won't be able to make call. Correct?
Gandicela said:
If RIL isn't working yet, i assume one won't be able to make call. Correct?
Click to expand...
Click to collapse
Not via phone, however you can call via wifi (skype etc)
I have been looking forward to this ROM for a while and I really appreciate your effort in this. Thank you very much!
Flashed it and deleted the setupwizard.apk as suggested but the CM setup wizard still crashes after pressing skip on "SIM card missing" tab. Any suggestions how to bypass this?
Any possibility for kernel with overclocking CPU and GPU functions for our tab?
Raido182 said:
I have been looking forward to this ROM for a while and I really appreciate your effort in this. Thank you very much!
Flashed it and deleted the setupwizard.apk as suggested but the CM setup wizard still crashes after pressing skip on "SIM card missing" tab. Any suggestions how to bypass this?
Any possibility for kernel with overclocking CPU and GPU functions for our tab?
Click to expand...
Click to collapse
Hey, i'll fix that issue in my next build, however I need to get my PC running again before I can start anything new
CTXz said:
Hey, i'll fix that issue in my next build, however I need to get my PC running again before I can start anything new
Click to expand...
Click to collapse
I'm patiently waiting, Mate. Quality work takes time. Thanks hugely for supporting our device.
So excited!
I have 2 SM-T230's for my boys, If you need someone to test something please let me know. (I am hoping that this will have the Marshmallow feature to use the SDcard as internal memory)
Thanks Andi
therealbroxy said:
I have 2 SM-T230's for my boys, If you need someone to test something please let me know. (I am hoping that this will have the Marshmallow feature to use the SDcard as internal memory)
Thanks Andi
Click to expand...
Click to collapse
Sorry mate, this thread is t235 only
CTXz said:
Sorry mate, this thread is t235 only
Click to expand...
Click to collapse
I know but...... you mentioned someone was sending you a 230, you might have time in the future, this might be the closest I get to seeing 6 on my Tab 7, A slim chance is still a chance! so I am still excited
I'm looking for someone to test my new build, my tester seems to be away at the moment, PM me if you're willing to test
CTXz said:
I'm looking for someone to test my new build, my tester seems to be away at the moment, PM me if you're willing to test
Click to expand...
Click to collapse
Is it for the 20160308 degaslte build? I've downloaded it and i try to find time to test tonight. Or is it another built?
Gandicela said:
Is it for the 20160308 degaslte build? I've downloaded it and i try to find time to test tonight. Or is it another built?
Click to expand...
Click to collapse
Hey, thanks but my tester returned, I'll update the OP
CTXz said:
Hey, thanks but my tester returned, I'll update the OP
Click to expand...
Click to collapse
No problem
I've dirty flashed the actual build over last lp build by hennymmc. Generally the last build works well but ril doesn't work with boh7 baseband. The camera preview hang up after taking a photo. If you take a new picture, the photo shows in gallery but the preview doesn't work.
New build released, links have been updated
Code:
2016/3/10
- Fix Crash on CM and Google setup Wizzard
CTXz said:
New build released, links have been updated
Code:
2016/3/10
- Fix Crash on CM and Google setup Wizzard
Click to expand...
Click to collapse
@CTXz
Thanks very much indeed for this ROM. It's running good, however i just want to point out 2 really minor things (aside from the RIL stuff).
1. Sensitive notification drawer, as from my hlte CM12.1, "Contents hidden" for any apps in the notification drawer
2. Quick unlock option inside Lockscreen menu
{
"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"
}
OmniROM
Android 8.0
Sony Xperia z3 (all variant)
What is Omnirom?
A Android custom rom announced at the BABBQ (Big Android BBQ) in late 2013 by @XpLoDWilD, @Chainfire, @Dees_Troy & Team.
"The goal of Omni is to experiment with Android development because we enjoy it. Omni isn’t better, just different. "
For more information go to omnirom's website
Code:
#include <disclamer.h>
/*
* Your warranty is now void.
*
* 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.
* If you dont like this rom, Stay away from this thread!
*/
TWRP with hardware decryption support can be found here
Usefull Links
You want to contribute to Omni? CLICK ME
You want to see the github? CLICK ME
Omni Wiki LOOK HERE
Contributors CLICK HERE
Who can use it
It is only for Z3 (single or dual) and UNLOCKED UPGRADED BOOTLOADERS
How to install
%= Only needed at first flash
% Update ROM to .291 with emma (or Flashtools)
% When install is done go into fastboot mode (plug usb + vol down key = blue led)
% Flash TWRP / If you already are in .291 and have a working TWRP (modded rom/kernel/adv kernel) you can use the flashable zips below instead.
Shutdown the device
Unplug the usb cable
Maintain volume down & power until you see twrp splash screen
% Wipe system, cache and data (factory-reset)
Install rom zip (+
% gapps if you need it, any size is ok
%Install root from @phhusson )
Reboot
Rolling back to stock
Flash stock rom with emma or flashtool
If you flash with flashtool remember to check wipe apps_log and userdata partitions to get a clean install
Stock compatible TWRP
Sources
Manifest file.
Everything else is omnirom.
Contribute gerrit.
This rom is not pure OmniRom, but close to, for convenience purpose. Roms are build from this script and can contain some lightweight modifications (like mkshrc, or TWRP app disabling, @nailyk certificate authority included, etc...) but will never have heavy changes like replacing an app by another, etc...
Downloads:
Latest release
2018-01-01:
md5: d6b1929cb7ce4f6c8fbc06d1487cd881
download mirrorWhat's new:
Switch to OmniRom 8.1
Full treble device
Clean camera code
Reworked devices trees
Add APTX support
GPS fixes
Click to expand...
Click to collapse
Release Timeline
2017-12-10:
md5:
downloadWhat's new:
Do not forget this update require a full wipe!
2017-11-03:
md5:
download
2017-11-01:
md5:
downloadWhat's new:
Code:
Restore double tap to wake from 26502 & 26504
Attempt to fix wifi acess point with 26524
Enable Messaging app (26526) & FM app (26527)
2017-10-29new:
md5: 70bf59e28cef54046e7eb4822a95c906
downloadWhat's new:
^z^z^z
Let's start again
XDA:DevDB Information
omnirom-oreo-z3, ROM for the Sony Xperia Z3
Contributors
nailyk, Dobsgw
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Based On: OmniRom
Version Information
Status: Beta
Created 2017-10-29
Last Updated 2018-01-01
Known issues:
- Video recording broken
- 120fps / 4k recording
- Wifi access point on 5GHz until country is set
- Off mode charging while connected to computer
- Quick charge
- Dual sim swap problem. After a change all the slot1 is lost!
- 4G connection issue until connected to a WIFI network.
- Audio problems. Depending on actual test could be:
1. No audio while ok siri is enabled,
2. Echo while on speaker mode.
- Wifi drop while ipv6 is set with router advertisements
How to post
Reports without logs or step to reproduce are useless (read contribute).
You are welcome to post your review: what is working, not working, etc... Check into know issues before.
You are welcome to report any typo, error, etc...
Try to keep thread clean as a dev reference. Thanks in advance.
How to report problems
To report problem, please provide logs.
It is always better to include reference to the Installed version. This guide is really detailed and explained everything about bug reports.
If you have any doubts, take the most logs. There is never enough logs
How to get logs
If your device is not booting at all, we need information about how you flash and all the handling you do, the display status, light status, and if available a dump of /proc/last_kmesg*
If you have a non working peripheral (non-working radio/wifi/etc...) please provide a full logcat and full dmesg, example:
Code:
adb reboot
adb wait-for-device
adb shell dmesg > dmesg.log
adb logcat -d > logcat.log
If you have a non working app please provide a partial logcat:
Code:
adb reboot
adb wait-for-device
adb logcat -c
<launch your app>
adb logcat -d > logcat.log
On this rom, there is a script who detect device at install time and provide the right functions for single or dual sim. If you have modem problems (like data not working or no signal) please also provide the /tmp/recovery.log.:
If you have ADB access to your device in twrp just use
Code:
adb pull /tmp/recovery.log .
after flashing omnirom.
If you do not have ADB access use the 'copy to SD' button in the advanced tab, then transfer it the way you like.
then upload your files to a service like pastebin.com / paste.omnirom.org
How to contribute
Code is like hieroglyphs for me:
No worries you can contribute anyway! Install the rom, do tests, read failure logs, look at internet for potential fix/similar users experience, is the biggest part of debugging. Then collect all of this and write your results here.
Code is like hieroglyphs for me and logs are worst:
No problem, collects logs the right way if you can, explain how you encounter the problem: detailed step to reproduce could be enough: explain exactly how you encounter the error/problem, it should produce each time someone repeat your steps. Then we will be able to fix it.
bar
Excited for the fresh start on Oreo
Thanks for supporting Leo!
Taste, thanks for you hard work ?
And now delete text and save it? Thats right?
Problem with error7 on d6603 (leo)
Sent from my Xperia Z3 using XDA-Developers Legacy app
santeria27 said:
And now delete text and save it? Thats right?
Problem with error7 on d6603 (leo)
Sent from my Xperia Z3 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Sent from my Xperia Z3 using XDA-Developers Legacy app
Hello guys,
As mentioned error 7 for 6603, but can be fixed via provided workaround for now☺
My sim card was not detected at all. System was asking for sim card insertion. ? (I wiped everything before installation, flashed zip and gapps nano, tried also the same with sideload)
I had to directly switch back, because I need working phone today. But I will try to provide logs as soon as possible.
Thank you a lot!
santeria27 said:
View attachment 4317281
Sent from my Xperia Z3 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Sent from my Xperia Z3 using XDA-Developers Legacy app
Hi, I'm still failing
i got error 7, i made changes to script file, zipped the entire folder again. now the twrp says the zip file is corrupt. what am i missing.
Gixchi said:
i got error 7, i made changes to script file, zipped the entire folder again. now the twrp says the zip file is corrupt. what am i missing.
Click to expand...
Click to collapse
Check the basic structure of your zip, if it corresponds to the original one. If this is not the problem zip it with other tool...
am gonna upload a fixed zip.
@nailyk will you update the rom to fix the BT and Hotspot soon?
And thanks for this great rom
release 3
That's a failing launch
So new zip with already removed assert, and some fix for single sim who do not have data. Please wipe /system before flashing.
Looks like another expected issue pop out: BT is broken. We are currently working on it. (bt was working 2 days ago )
Sorry for the mess
Looks very good. Even with October security patch level.
I know it may be a little early, but can you say anything about battery life (especially standby) compared to 7.1.2 or stock?
nailyk said:
That's a failing launch
So new zip with already removed assert, and some fix for single sim who do not have data. Please wipe /system before flashing.
Looks like another expected issue pop out: BT is broken. We are currently working on it. (bt was working 2 days ago )
Sorry for the mess
Click to expand...
Click to collapse
I excited to install it but i think to wait stable release to be good for daily use
Br4no said:
Check the basic structure of your zip, if it corresponds to the original one. If this is not the problem zip it with other tool...
Click to expand...
Click to collapse
thanks it helped. zip structure was not right
Ok lets start again.
New zip uploaded, we will base the work on this one.
Sorry again. Wont post zip at 4AM anymore!
{
"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:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1.0 (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. You can also view the Changelog for a full list of changes & features.
What's working :
Boots
Wifi
Bluetooth
Camera and Camcorder(video recorder)
Video Playback
Audio ( Recording and Playback )
Sensors
GPS
VoLTE
What's not working :
Usb tethering function does not work.A Third party app such as pdanet might be a solutiıon.
Flashing and updating
LineageOS clean install :
- Mandatory to flash 64bit recovery
- (Optional) Wipe the data & cache & system(Backup to make sure not to loose data)
- Flash the LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
LineageOS update / upgrade :
- Mandatory to flash 64bit recovery
- (Information) Don't wipe anything unless you want to
- Nothing to wipe when switching
- (FUTURE RELEASES) Might need clean, informations will be updated
- Flash the latest LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes
- (Optional) Every additional zip you want to flash
- Reboot
For root access :
- (Information) Read the Root section of the Q&A thread
Downloads Links
LineageOS 15.x arm64(Unlocked Bootloader) :
Development : https://www.androidfilehost.com/?w=files&flid=236385
Google Applications (optional) :
MindTheGapps : Link (Use packages for ARM64, Android 8.1)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Recovery Mandatory to flash for 64bits ROM :
Download TWRP 3.2.1-0 : https://www.androidfilehost.com/?w=files&flid=236353
About the builds
Device tree : https://github.com/Sohamlad7/android_device_motorola_cedric/commits/lineage-15.1-64
Kernel sources : https://github.com/Sohamlad7/android_kernel_motorola_msm8937/commits/lineage-15.1-64
Vendor blobs : https://github.com/Sohamlad7/android_vendor_motorola_cedric/commits/lineage-15.1-64
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /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
Bug report should be done in following format provided in code below
Code:
What is your
LineageOS version:
LineageOS Download url:
Gapps version:
Did you
wipe:
restored 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:
Q&A - FAQ
LineageOS 15.1 arm64 Cedric Regular Questions and Answers : Q&A Thread
Credits :
- The LineageOS Team
- Thanks to ROM that have been built on Legacy Server and also thanks to all the legacyserver member friends
- Special Thanks to @wzedlare and @vache without them it wouldn't have been possible for us to get Nougat and Oreo
- Thanks to @jobinrjohnson for helping and for contributing
- Thanks to dattebayorob and Renee.Souza for testing rom
- Let me know if i missed anyone
XDA:DevDB Information
LineageOS 15.1, ROM for the Moto G5
Contributors
CodeZero, vache
ROM OS Version: 8.x Oreo
Based On: AOSP
Version Information
Status: Stable
Created 2017-12-20
Last Updated 2018-05-24
Changelog
15/04/2018
April security patches
build using sdclang
added some qcom HALs
addressed some denials
Updated to KPTI patched time blobs
Used O-MR1 based display and media blobs
Used O-MR1 based GPS blobs
Kernel source is upstreamed to linux stable release 3.18.105
13/02/2018
February security patches
SELinux Enforced
Added TextClassifier Selection models
Imported oss sensors HALs
Kernel source is reworked from cm-14.1 kernel source
Kernel source is upstreamed to linux stable release 3.18.94
20/12/2017 - Initial Release
Note :-
We can now run 64bits ROM on our phone.
But actually we have to run app_process (system server) as 32bits, mainly cause of sensors non working actually with a 64bits system server.
More to come next, vendor tree is still missing many 64bits blobs, and some of our proprietary services still run in 32bits mode too.
As we have found out , Flashing stock whilst having anything 64bit even the recovery for some reason the efs (IMEI) gets wiped .
I do not recommend you revert to stock on any 64bit rom.
Current local manifest of the ROM build
Code:
<!-- https://github.com/Sohamlad7/android_development_manifest/blob/local_manifests/lineage-cedric-15.1-64.xml -->
Thank you very much that good job, it works in XT1676 ?
alejandrorobles12 said:
Thank you very much that good job, it works in XT1676 ?
Click to expand...
Click to collapse
yes it'll work
Testing
Testing the ROM, how I hide the navbar in this rom? Cant hide in SystemUI
Do you connect to the network?
Data work?
dattebayorob said:
Testing the ROM, how I hide the navbar in this rom? Cant hide in SystemUI
Click to expand...
Click to collapse
Currently you wont be able to hide those in settings because lineage os haven't merged those patches yet. So you have to edit the build prop and add this line
Code:
qemu.hw.mainkeys = 1
if you doesn't have root you can do this by
1 - reboot to TWRP
2 - mount system
3 - goto terminal and run this command
Code:
echo 'qemu.hw.mainkeys = 1' >> /system/build.prop
jobinrjohnson said:
Currently you wont be able to hide those in settings because lineage os haven't merged those patches yet. So you have to edit the build prop and add this line
Code:
qemu.hw.mainkeys = 1
if you doesn't have root you can do this by
1 - reboot to TWRP
2 - mount system
3 - goto local terminal and run this command
Code:
echo 'qemu.hw.mainkeys = 1' >> /system/build.prop
Click to expand...
Click to collapse
Ok thanks.
It seems to work really well on XT1675 2 GB 16 storage.
Everything working so far for me. I'm with magisk and root is working too.
Edit: Actually, Camera is with some bugs, like dark image and not working on whatsapp.
Edit2: Nevermind, camera works fine on Open Camera
Enable camera2 api
Can someone check whether enabling camera2 api works since this is needed to use the Google Camera ports with hdr+. Adding persist.camera.HAL3.enabled=1 to build.prop makes all camera apps stop working for me!
---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------
masterdex said:
Ok thanks.
It seems to work really well on XT1675 2 GB 16 storage.
Click to expand...
Click to collapse
Can you check whether the in-call audio quality problem has been solved?
soumitro316 said:
Can someone check whether enabling camera2 api works since this is needed to use the Google Camera ports with hdr+. Adding persist.camera.HAL3.enabled=1 to build.prop makes all camera apps stop working for me!
---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------
Can you check whether the in-call audio quality problem has been solved?
Click to expand...
Click to collapse
Not completely, I already noticed with AospExtended that the noise is attenuated but it is still present, however you can hear it quite well. If I have to give a better judgment on Aospextended. For the camera I use the pro version of Footej Camera and here it works really well while the standard one after 3 shots becomes dark.
soumitro316 said:
Can someone check whether enabling camera2 api works since this is needed to use the Google Camera ports with hdr+. Adding persist.camera.HAL3.enabled=1 to build.prop makes all camera apps stop working for me!
Click to expand...
Click to collapse
Currently we are using a camera wrapper in order to make the camera work. The wrapper doesn't support hal3 so enabling it in build.prop will screw your camera.
If you don't know what a wrapper is
The wrapper is the facade. Sometimes you may have a class which would suit a specific interface, but you can't change the code for it to make it conform to that interface. You can create a wrapper for that class which implements the interface, but which directs most of the calls to the wrapped object.
-- Stackoverflow
If you really want to use hal3 you need to
delete /system/lib/he/camera.msm8937.so
rename camera.vendor.msm8937.so to camera.msm8937.so
then enable hal3 in build prop
Reboot
But it will bring back our one photo bug on Oreo
jobinrjohnson said:
Currently we are using a camera wrapper in order to make the camera work. The wrapper doesn't support hal3 so enabling it in build.prop will screw your camera.
If you don't know what a wrapper is
The wrapper is the facade. Sometimes you may have a class which would suit a specific interface, but you can't change the code for it to make it conform to that interface. You can create a wrapper for that class which implements the interface, but which directs most of the calls to the wrapped object.
-- Stackoverflow
If you really want to use hal3 you need to
delete /system/lib/he/camera.msm8937.so
rename camera.vendor.msm8937.so to camera.msm8937.so
then enable hal3 in build prop
Reboot
But it will bring back our one photo bug on Oreo
Click to expand...
Click to collapse
Okay makes sense. Thank you for the detailed response!
*A fairly minor problem I've had is that the flashlight won't activate using the button in the QuickSettings. The button doesn't seem to respond in any way to being tapped. Is this broken for anyone else?
(*Edit: Having re-installed this ROM today the problem has gone, not sure what caused it.)
Also, wondering if anyone has managed to get Google Camera with HDR+ working in this ROM? I've currently got it working fairly reliably in LOS15 using the port that someone posted for the G5 back in November, but this didn't work for me when I tried it in this ROM yesterday. I've moved back to LOS15 for now, but it seems that there are a couple of extra steps to getting HAL3 enabled in this ROM beyond just the build.prop edit that I wasn't aware of yesterday so I'm just interested to know if anyone has had any success with this?
RaddingtonBear said:
A fairly minor problem I've had is that the flashlight won't activate using the button in the QuickSettings. The button doesn't seem to respond in any way to being tapped. Is this broken for anyone else?
Also, wondering if anyone has managed to get Google Camera with HDR+ working in this ROM? I've currently got it working fairly reliably in LOS15 using the port that someone posted for the G5 back in November, but this didn't work for me when I tried it in this ROM yesterday. I've moved back to LOS15 for now, but it seems that there are a couple of extra steps to getting HAL3 enabled in this ROM beyond just the build.prop edit that I wasn't aware of yesterday so I'm just interested to know if anyone has had any success with this?
Click to expand...
Click to collapse
I changed the lib, added the hal3 to build prop and downloaded that hdr+ port (https://androidfilehost.com/?fid=817906626617934890) and worked fine. But as said previously, the bug of one shot only is present.
Edit: Actually, doesn't seem to be making any difference with hdr+ on or off on this app. And the bug of one shot only you can work around by opening the photo that you took and coming back to the camera.
Edit2: The app has a lot of options to work with that can make the hdr+ work just fine, I just haven't found them yet, if I do I'll let you know.
Edit3: Got it working with the following config edited only:
Edit4: I took 2 photos just to see how it was (I don't think I need to say which one has the hdr+ enabled):
DavidKirsch said:
I changed the lib, added the hal3 to build prop and downloaded that hdr+ port (https://androidfilehost.com/?fid=817906626617934890) and worked fine. But as said previously, the bug of one shot only is present.
Edit: Actually, doesn't seem to be making any difference with hdr+ on or off on this app. And the bug of one shot only you can work around by opening the photo that you took and coming back to the camera.
Edit2: The app has a lot of options to work with that can make the hdr+ work just fine, I just haven't found them yet, if I do I'll let you know.
Edit3: Got it working with the following config edited only:
Click to expand...
Click to collapse
Thanks for the info, I appreciate you taking the time to post this! Very glad to hear that it's working
Ow, I wished the USB tethering bug could be fixed with a 64-bit build! Nevertheless, this is a great achievement, congratulations and thank you!
Shooting Star Max said:
Ow, I wished the USB tethering bug could be fixed with a 64-bit build! Nevertheless, this is a great achievement, congratulations and thank you!
Click to expand...
Click to collapse
Soham said maybe a third party app could fix usb tethering, you should try.
Fedray said:
Soham said maybe a third party app could fix usb tethering, you should try.
Click to expand...
Click to collapse
The mentioned app is a paid one, and the ideal thing would be fixing the actual Android function. Still, I can survive without USB tethering, as I have been doing since I installed LOS 14.1
{
"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"
}
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
Click to expand...
Click to collapse
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]
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
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
Reserved
First reply on first Q ROM for Galaxy J5.
This is a great ROM, it's really stable and I recommend it!
Woooowww!!!
I waited for it so long
I'm so much happy that we have such talented and hard worker devs
Thanks dear @Zakaryan2004
Congratulations to you, jenslody & everyone who worked to achieve this .
A best wishes for Android 10 journey. Thanks to everyone who involved to achieve Android 10 for j5 . j5 is still alive.
Fantastic :good:
I download and test.
You are the best
thank you so much
Nice, will test this in my phone in next days.
Edit: Trying j5lte ROM beta 2020-01-22, in SM-J500M. Some issues:
At fresh install in second config screen (connect to wi-fi or mobile data) can't connect to wireless if ssid is hidden (SSID Broadcast disabled in router/A.P.), after enable SSID Broadcast in access point the phone connects fine.
Even after successful connect, if SSID Broadcast is disabled in access point phone goes to "Out of Range" and WiFi is disconnected.
Bluetooth can't transfer/share files from my PC to phone (or inverse). In PC only shows like an Audio Device, not "other devices" and can't send files to phone.
Selecting a file from file explorer in phone, and tap Share button have none option in menu, neither Bluetooth.
Same as Luis Garrido, in my phone the carrier config is detected automatic but can't navigate or reach internet only with mobile data.
Again Thank you for this marvelous ROM.
I am testing this Rom and everything perfect, thanks for not letting this device die.
About the errors, so far the aforementioned data and mobile data do not work on my SM-J500M (Yes, I have already configured the APNs)
Thank all the people who worked on this and forgive my bad English. haha
Lokotito said:
Nice, will test this in my phone in next days.
Edit: Trying j5lte ROM beta 2020-01-22, in SM-J500M. Some issues:
At fresh install in second config screen (connect to wi-fi or mobile data) can't connect to wireless if ssid is hidden (SSID Broadcast disabled in router/A.P.), after enable SSID Broadcast in access point the phone connects fine.
Even after successful connect, if SSID Broadcast is disabled in access point phone goes to "Out of Range" and WiFi is disconnected.
Bluetooth can't transfer/share files from my PC to phone (or inverse). In PC only shows like an Audio Device, not "other devices" and can't send files to phone.
Selecting a file from file explorer in phone, and tap Share button have none option in menu, neither Bluetooth.
Same as Luis Garrido, in my phone the carrier config is detected automatic but can't navigate or reach internet only with mobile data.
Again Thank you for this marvelous ROM.
Click to expand...
Click to collapse
Much love you guys for testing.plz provide logcat.zip
That will be more helpfull with your words
(So upset bc of exam time and i wanna completely stable rom and can't try this rom right now
Btw provide some screen shot of this rom:good:
Luis Garrido said:
I am testing this Rom and everything perfect, thanks for not letting this device die.
About the errors, so far the aforementioned data and mobile data do not work on my SM-J500M (Yes, I have already configured the APNs)
Thank all the people who worked on this and forgive my bad English. haha
Click to expand...
Click to collapse
Lokotito said:
Nice, will test this in my phone in next days.
Edit: Trying j5lte ROM beta 2020-01-22, in SM-J500M. Some issues:
At fresh install in second config screen (connect to wi-fi or mobile data) can't connect to wireless if ssid is hidden (SSID Broadcast disabled in router/A.P.), after enable SSID Broadcast in access point the phone connects fine.
Even after successful connect, if SSID Broadcast is disabled in access point phone goes to "Out of Range" and WiFi is disconnected.
Bluetooth can't transfer/share files from my PC to phone (or inverse). In PC only shows like an Audio Device, not "other devices" and can't send files to phone.
Selecting a file from file explorer in phone, and tap Share button have none option in menu, neither Bluetooth.
Same as Luis Garrido, in my phone the carrier config is detected automatic but can't navigate or reach internet only with mobile data.
Again Thank you for this marvelous ROM.
Click to expand...
Click to collapse
No such outcome for me.
Wifi --> ok
Bluetooth authorized file transfer --> ok
on lineage-17.1-20200121-UNOFFICIAL-j5nlte
Marshmallow firmware required??
I flashed Lineage 16 and didn't had the stock backup also my PC is dead
Sent from my Xperia 1 using XDA Labs
BladeRunnerA2C said:
Marshmallow firmware required??
I flashed Lineage 16 and didn't had the stock backup also my PC is dead
Click to expand...
Click to collapse
Yep you should have been updated your phone to marshmallows stock before all
If you flashed lineage os 16 before and it booted you can flash this too!
Btw use correct twrp(mentioned at op)
Lokotito said:
Nice, will test this in my phone in next days.
Edit: Trying j5lte ROM beta 2020-01-22, in SM-J500M. Some issues:
At fresh install in second config screen (connect to wi-fi or mobile data) can't connect to wireless if ssid is hidden (SSID Broadcast disabled in router/A.P.), after enable SSID Broadcast in access point the phone connects fine.
Even after successful connect, if SSID Broadcast is disabled in access point phone goes to "Out of Range" and WiFi is disconnected.
Bluetooth can't transfer/share files from my PC to phone (or inverse). In PC only shows like an Audio Device, not "other devices" and can't send files to phone.
Selecting a file from file explorer in phone, and tap Share button have none option in menu, neither Bluetooth.
Same as Luis Garrido, in my phone the carrier config is detected automatic but can't navigate or reach internet only with mobile data.
Again Thank you for this marvelous ROM.
Click to expand...
Click to collapse
to connect hidden ssid , when you enter ssid name and pasword, scroll down and go advance option and there is option hidden network where select yes option then save. then you hidden wifi will connect
BladeRunnerA2C said:
Marshmallow firmware required??
I flashed Lineage 16 and didn't had the stock backup also my PC is dead
Click to expand...
Click to collapse
If you are on >=Oreo you are on mm fw
Thanks @Zakaryan2004 for posting this ROM , I flashed this ROM on my J500F , it works fine ,
I need your help . how to fix the brightness issue .?please tell me it in detail . other than the brightness issue ,the ROM is great for my device .
Zakaryan2004 said:
If you are on >=Oreo you are on mm fw
Click to expand...
Click to collapse
Thanks for the reply,,
Sorry for that noob question, I'm new to Samsung
Sent from my Xperia 1 using XDA Labs
---------- Post added at 10:35 AM ---------- Previous post was at 10:28 AM ----------
amirizad_7436 said:
Yep you should have been updated your phone to marshmallows stock before all
If you flashed lineage os 16 before and it booted you can flash this too!
Btw use correct twrp(mentioned at op)
Click to expand...
Click to collapse
Before I flashed LOS16 I was on official Marshmallow so as OP said it's suitable and I'm using the latest official TWRP available for J5
Sent from my Xperia 1 using XDA Labs
Stephinsiby1234 said:
Thanks @Zakaryan2004 for posting this ROM , I flashed this ROM on my J500F , it works fine ,
I need your help . how to fix the brightness issue .?please tell me it in detail . other than the brightness issue ,the ROM is great for my device .
Click to expand...
Click to collapse
You can't fix it, it's a known bug. Read the OP
After flashing this rom n gapps, i cant install telegram, google,chrome .Any fix arround?
fahisham72 said:
After flashing this rom n gapps, i cant install telegram, google,chrome .Any fix arround?
Click to expand...
Click to collapse
Download the apk file and install it.
{
"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"
}
This is discoveryOS (diOS)
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.
*/
About this project: discoveryOS (or in short: diOS)
I was not satisfied with any external car navigation system I can get because either they are ultra slow, outdated, having bad user experience, missing speed cam support or simply taking ages to get a gps lock within my car.
So the main approach here is not having the best ROM for all users but for those having the same need then I have. Usually these both should not conflict so if I fix an issue for my needs it might fix yours as well. But my focus is navigation, nothing (much) else.
Examples: if Camera has issues I might not solve it, if calling has issues I might not solve it, etc.
Features of discoveryOS
fully based on /e/ OS for a full google-free experience
F-Droid (OpenSource Apps as an alternative to Google Play) including extra repos
debloated everything not needed for diOS (for details check this list)
Integrated MagicEarth Navigation
Integrated Automate App
Integrated Aurora Store
Speaker output optimized for speech (i.e. increasing loudness as much as possible)
my builds come with full OTA update support (from v2.0 on)
(... you know that thing which informs you that a new update is there and where you just click to download + install)
Roadmap
Implementing Kiosk Mode for navigation only (might be provided as a separate build)
links: <--- abandoned by using the app "Automate" instead
the one I will go for (tested fine already): https://www.sdgsystems.com/post/pro...droid-devices-with-a-device-owner-application
older approaches:
Implementing Kiosk Mode in Android - Part 1
Part 2 Part 3 Part 4 Part 1: No Android Changes Required Note: Looking for Kiosk mode in Android Lollipop 5.0 or later? Skip to part 3. What is “Kiosk Mode” and why would you want to use it? Kiosk Mode basically allows a single Android application to have full control of the system. The user is...
www.sdgsystems.com
Implementing Kiosk Mode in Android - Part 3: Android Lollipop (and Marshmallow)
Part 1 Part 2 Part 4 Part 3: Android Lollipop (and Marshmallow) Android 5.0 (Lollipop) and 6.0 (Marshmallow) now have an official Kiosk Mode that anybody can use, but they don’t call it Kiosk Mode. They call it “screen pinning” or “task locking”. This article will provide information on how to...
www.sdgsystems.com
Implementing Kiosk Mode in Android - Part 4: A Better Provisioning Method for DPC / Device Owner
Part 1 Part 2 Part 3 In part 3 of our series on kiosk mode, we provided source code for our Set Device Owner app. This app allows you to provision Android Lollipop and Marshmallow devices using the “device bump” method, which configures device owner apps or device policy controllers (DPC) such...
www.sdgsystems.com
Integrate my created Automate flow to simulate a KIOSK mode (i.e. start navigation on boot and keep it on top always)
Requirements
Your device need to be unlocked (seriously?!)
Latest TWRP/SHRP build is highly recommended, e.g. mine: see my recovery post
Do a full Nandroid backup before doing anything else!
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
Installation
Backup
When you flash diOS the first time:
Wipe: System and do a factory reset !
A LOT of bad stuff can happen otherwise
Flash the ROM
Optional (if you want root): Flash Magisk
Flash OpenGapps ????? STOOOOOOOOP NO No no! you don't want that on a google-free phone! diOS contains everything you need to live without Google!
Boot (be patient on first boot!!! SIM detection might take a minute after the FIRST boot after clean flash as well)
Open Maps (MagicEarth) and click the download button to get your country/region maps
Open Automate to import the kioskmode flow
Open F-Droid -> Settings -> Repositories and choose those you want to enable (most of them are described here) & swipe down to update the repo list.
Open Aurora -> choose Anonymous as long as you don't want to have paid apps working
Enjoy
Known issues
no OMS support! OMS is a hack DEEP in the android sources and all these are outdated now. if you need that use jedl's build
build is ENG , i.e. "adb root" will work and no auth required for ADB
bluetooth is working but using the blobs by jedld's build until I find the time fixing the android sources (unfortunately the repo of jedld does not contain the full history so I have to compare manually...). Until then I keep it like that.
not charging on USB connection (normal power supply works fine) - still investigating. Seems to be an issue with my kernel.
This ROM is just coming with BASIC stuff so several apps you might want to see in a regular Android ROM are simply not there.
Examples (excerpt only!):
- no Camera app
- no Browser app
- no Gallery app
- no Email app
- no Calendar app
- no <fill-in-whatever-you-are-missing>
the complete list can be found here always
If you find a bug not listed, follow the instructions here and provide me with the logs: FAQ #1
Download
Get the builds from my leech server
discovery OS: https://leech.binbash.rocks:8008/discoveryos/nougat/gtexslte/
Note:
Builds are updated when I decide to do so. There is no build cycle.
Changelogs
search results from this thread: click
Credits
LineageOS
jedld, really! thanks dude, not just for giving a starting point but also for providing your sources.
... if I forgot to mention YOU, tell me
Sources
It took me a while (2 or 3 weeks iirc) to clean up all the sources from jedld in order to be able to update and keep in sync with LOS itself.. All these can be found here:
github org
build manifest
XDA:DevDB Information
discoveryOS, ROM for the Samsung Galaxy Tab A series
Contributors
steadfasterX, jedld (without his work I would never had bought that tab! he made all the main parts until 2018!)
Source Code: https://github.com/smt285
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: /e/ OS
Version Information
Status: Beta
Beta Release Date: 2020-11-19
Created 2020-04-03
Last Updated 2020-11-20
everything around my recovery images
RECOVERY images
Download (shrp + twrp)
TWRP: here
SHRP (recommended): here
I provide 3 formats:
IMG (twrp only)
TAR (shrp & twrp)
ZIP (shrp only)
When to use the IMG (twrp only)?
If you flashed a custom recovery already
if you like to flash by download mode with heimdall
When to use the TAR (shrp & twrp)?
If you never flashed a custom recovery before you have to use this one
if you like to flash by download mode with ODIN or JOdin
When to use the ZIP (shrp only)?
If you want to switch from TWRP
if you want to upgrade from one SHRP version to another
if you flashed the TAR of SHRP in download mode by ODIN or JOdin you HAVE to flash this ZIP in SHRP once
How to flash the IMG?
boot to your custom recovery
push the IMG to your device (e.g. by adb)
select flash
ensure you select "IMG" (when in TWRP. when in SHRP that is not needed)
select the IMG file
choose "Recovery" as the "Target Partition" and flash
Reboot to Recovery to complete the setup.
How to flash the TAR?
boot to download mode
start ODIN/JOdin
put the TAR into the AP/PDA slot
ensure the "Auto Reboot" is NOT ticked/checked
flash
turn the device off (HOME+PWR+VOLDOWN) and directly switch just the VOLDOWN button to VOLUP when it wakes up and hold all 3 buttons until you see the recovery loading
How to flash the ZIP?
boot to your custom recovery
push the ZIP to your device (e.g. by adb) (or start and use adb sideload and you are done)
select flash
select the ZIP & Flash
Reboot to Recovery to complete the setup
Reserved
New build arrived
Changelog
Release date: 2020-04-03
Download: see OP
initial build:
I had a REALLY hard time to actually make LOS 14.1 boot with cleaned sources.. thought the ramp-up will take a week at most .. but that was way off..
jedld had done several patches within AOSP and I had to find out which are required where etc. the main reason why my build were not booting at all (which is f**** hard to debug without and log and/or adb ) was that one.
But I needed to clean the sources as several parts of these were incredible outdated and so needs to be udpated.
I had spent several more days to cleaning up even more stuff and finally uploaded a test build.
feel free to join but read the KNOWN ISSUES topic carefully before.
It is still in a very early state and I have tested pretty much nothing else then boot, apps, bluetooth, WiFi
Kernel:
switching to EUR kernel
implemented kernel build within LOS build!
added own TWRP defconfig
moving kernel modules like WiFi to /system
.... and more (see "Detailed changes")
LOS:
added alle needed TWRP configs
moving kernel modules like WiFi to /system
sepolicy updates for rild
.... and more (see "Detailed changes")
Detailed changes:
LOS: this build VS. last build (by jedld, yea 19 pages ... was a long time )
Device tree: github
Kernel: github
.-
For those interested I will also provide SHRP (skyhawk recovery) after some testing and fine tuning ...
Sent from my OnePlus 6T using XDA Labs
Testing and report
Thank You for this Great JOB
---------- Post added at 07:32 PM ---------- Previous post was at 07:10 PM ----------
steadfasterX said:
For those interested I will also provide SHRP (skyhawk recovery) after some testing and fine tuning ...
Sent from my OnePlus 6T using XDA Labs
Click to expand...
Click to collapse
Migration from Lineage Jed for LOS 7.1.2
Recovery 3.3.1.1 Ok
installation Ok
Magisk Ok
Google Apps Ok
Fist Boot Ok
Wifi and sensors Ok
OpenCamera working Perfectly
ROM stable Ok no errors in all files i recomend this release for all users Galaxy Tab T285
Great Job Great ROM.
Hacker.
May I know how do I flash your TWRP build? I am using Odin and I am supposed to flash .tar.md5 file right? Yours is in disc img file and when I try to extract / mount it shows "corrupted file".
nicktsh said:
May I know how do I flash your TWRP build? I am using Odin and I am supposed to flash .tar.md5 file right? Yours is in disc img file and when I try to extract / mount it shows "corrupted file".
Click to expand...
Click to collapse
Ah yea I haven't uploaded the ODIN file yet. Thanks for reminding. You can either wait for that or flash any of the other available TWRP versions for the smt285 which have a ODIN package. Once you have TWRP you can simply flash my img from within TWRP to update .
Sent from my OnePlus 6T using XDA Labs
Great piece of work, very much needed. Thanks Bro.
I wished if volte would have worked, is there any chance!
---------- Post added at 07:24 AM ---------- Previous post was at 06:33 AM ----------
Getting CTSProfile false in Magisk 20.4, any fix ?
रRudra said:
Great piece of work, very much needed. Thanks Bro.
I wished if volte would have worked, is there any chance!
---------- Post added at 07:24 AM ---------- Previous post was at 06:33 AM ----------
Getting CTSProfile false in Magisk 20.4, any fix ?
Click to expand...
Click to collapse
VoLTE is always a pita. So no.
Will check cts profile, should be fixable ..
Sent from my OnePlus 6T using XDA Labs
steadfasterX said:
VoLTE is always a pita. So no.
Will check cts profile, should be fixable ..
Click to expand...
Click to collapse
ctsprofile issue solved, I can share the solution if u need! Thanks
रRudra said:
ctsprofile issue solved, I can share the solution if u need! Thanks
Click to expand...
Click to collapse
Fingerprint .. I just need to add it but if you can share the exact one from stock it saves 2min for me
EDIT: nvm got it.
Sent from my OnePlus 6T using XDA Labs
I recently flash the rom, mobile data to long to open. Thank for this, still finding bugs
Having trouble flashing a custom recovery. Odin doesn't seem to like me. Could anyone help me out?
Installed - works fine but found one annoying bug - lockscreen is not rotating at all - it's only vertical and not want to rotate to horizontal when I rotate device.
how to install this ?
im having error on flashing it through twrp 3.1.1.1 it states error 7
jayrakiztah said:
im having error on flashing it through twrp 3.1.1.1 it states error 7
Click to expand...
Click to collapse
use the latest TWRP linked in the OP.
steadfasterX said:
use the latest TWRP linked in the OP.
Click to expand...
Click to collapse
twrp 3.1.1.1? it is already installed
jayrakiztah said:
twrp 3.1.1.1? it is already installed
Click to expand...
Click to collapse
nope. 3.3.1.1 is the latest and it is linked in the OP
.-
steadfasterX said:
nope. 3.3.1.1 is the latest and it is linked in the OP
.-
Click to expand...
Click to collapse
i flashed your sharp recvoery and it still got an error 7