that's why you don't trust an 'update' to a rom posted by some random user. the last actual update to this rom is november 7, posted by @@ki. any other roms posted aren't his work, and may (and obviously, in this case, does) cause massive issues. the obvious answer here is to not just install any rom you see just because the poster says it's updated.
VOLTE is still broken, but the developer told me he will soon update total RIL, which will fix VOLTE, so just hang on.
Else everything is rock solid and stable, absolutely no issues. I've heard it gives somewhat 5hrs of screen on time. Go for it if you have no issues with VOLTE, else try the new Oreo flavours, they're excellent too!
I installed the rom. Performance is very good, the clock processor to arrive up until 1,4GHz and GPU 450MHz. For play is great, the battery is ok (aceitable by performance that offer).
The single bug that i encountered was in the restart. The smartphone have a delay in start neeeding that i press the power botton by someone seconds.
lineageos logo in constant loop afer 20190119 ROM flash
Phone: Motorola Moto G4 Play (XT1607)
Did TWRP Factory reset, wiped data, system manually
installed lineage-16.0-20190116-UNOFFICIAL-harpia
When rebooting, got stuck at LineageOS logo, never fully got 3 circles.
---------- Post added at 04:21 PM ---------- Previous post was at 04:15 PM ----------
phone lineage-16.0-20190116-UNOFFICIAL-harpia
TWRP Factory reset, data and system manually wiped
Installed lineage-16.0-20180820-UNOFFICIAL-harpia.zip
Kept getting Pixel Setup Keeps Stopping, went to set QUICKSTEP as defualt HOME APP, but everytime I hit HOME ICON (Circle at bottom of screen) it would popup "Pixel Setup Keeps Stopping"
Installed Nova Launcher, but could not set as DEFAULT HOME APP.
Went to APP INFO and FORCED STOPPED, but restarted itself
Kept getting this :
[241/1007] including external/sony/boringssl-compat/Android.mk ...
build/make/core/base_rules.mk:260: error: external/sony/boringssl-compat: MODULE.TARGET.SHARED_LIBRARIES.libboringssl-compat already defined by device/motorola/msm8916-common/libshims.
22:00:56 ckati failed with: exit status 1
However in trying to troubleshoot, the good news is looks like development work is still going forward with this Rom as last updates to the Git Repo were 27th Feb.
Kept getting this :
[241/1007] including external/sony/boringssl-compat/Android.mk ...
build/make/core/base_rules.mk:260: error: external/sony/boringssl-compat: MODULE.TARGET.SHARED_LIBRARIES.libboringssl-compat already defined by device/motorola/msm8916-common/libshims.
22:00:56 ckati failed with: exit status 1
However in trying to troubleshoot, the good news is looks like development work is still going forward with this Rom as last updates to the Git Repo were 27th Feb.
Hmm... Oops lol. I kept updating los_harpia blindly as I'm focusing on SomeFeaK OS and COSP, I just wanted everyone else to keep it going if they wanted to. I forgot to get rid of that line in the manifest, it's now in the common repo of the device-tree. You should now be able to build it, I have just updated los_harpia.
Oh, and, BTW, there could be an issue with SELinux. Before doing a production/release build, try doing an eng build, then, fix all the denials and make a PR in Harpia-development (or contact me to add you to the org., I'll talk to the rest of members, don't think that'll be a problem though), anyways, if you want to get it working without much hassle, feel free to uncomment the line regarding permissive SELinux in BoardConfigCommon.mk (msm8916-common), it looks like this:
As always, please keep in mind that setting SELinux to permissive is a really huge security hole and you shouldn't be doing this, unless it's meant to "just get it working ASAP".
That said, I hope you get to build it at some point, and it's nice to know someone else is interested in the development for this device as well. Feel free to PM me if you get stuck or want to talk about nyancat memes.
Here's a little off-topic:
The only reason as I don't keep maintaining some ROMs, including LineageOS, CarbonROM, etc. is that I'm unable to keep track of the sources as I don't seem to have an easy way to just "fetch and build" in small parts, also, having to switch servers over and over wasn't helping. This whole thing "works" just because of some friends who are kind enough to give me a hand and provide me their servers for free. Hopefully, I'll get to be able to borrow one of theirs soon, I'll keep you up to date if I come back to the daily/weekly builds basis.
Ah, and no @hp420, you don't need to trust me. But I think you should, that's why I attach full build logs, MD5 and SHA256 hashes of the files, the maintainer's authorship string and more. But hey, you don't know that, because you're into a world where you're being scammed (yet I don't ask anyone for money, so... What kind of scam are we talking about?), all that, as I said, happens in t.me/somefeak. That said, please stop with these toxic comments, I'm not into that and I'm not willing to reply to any other of your posts if you keep showing that behavior, just because you don't know where those builds are coming from, doesn't mean that others are in the same position.
Hmm... Oops lol. I kept updating los_harpia blindly as I'm focusing on SomeFeaK OS and COSP, I just wanted everyone else to keep it going if they wanted to. I forgot to get rid of that line in the manifest, it's now in the common repo of the device-tree. You should now be able to build it, I have just updated los_harpia.
Oh, and, BTW, there could be an issue with SELinux. Before doing a production/release build, try doing an eng build, then, fix all the denials and make a PR in Harpia-development (or contact me to add you to the org., I'll talk to the rest of members, don't think that'll be a problem though), anyways, if you want to get it working without much hassle, feel free to uncomment the line regarding permissive SELinux in BoardConfigCommon.mk (msm8916-common), it looks like this:
As always, please keep in mind that setting SELinux to permissive is a really huge security hole and you shouldn't be doing this, unless it's meant to "just get it working ASAP".
That said, I hope you get to build it at some point, and it's nice to know someone else is interested in the development for this device as well. Feel free to PM me if you get stuck or want to talk about nyancat memes.
Here's a little off-topic:
The only reason as I don't keep maintaining some ROMs, including LineageOS, CarbonROM, etc. is that I'm unable to keep track of the sources as I don't seem to have an easy way to just "fetch and build" in small parts, also, having to switch servers over and over wasn't helping. This whole thing "works" just because of some friends who are kind enough to give me a hand and provide me their servers for free. Hopefully, I'll get to be able to borrow one of theirs soon, I'll keep you up to date if I come back to the daily/weekly builds basis.
Ah, and no @hp420, you don't need to trust me. But I think you should, that's why I attach full build logs, MD5 and SHA256 hashes of the files, the maintainer's authorship string and more. But hey, you don't know that, because you're into a world where you're being scammed (yet I don't ask anyone for money, so... What kind of scam are we talking about?), all that, as I said, happens in t.me/somefeak. That said, please stop with these toxic comments, I'm not into that and I'm not willing to reply to any other of your posts if you keep showing that behavior, just because you don't know where those builds are coming from, doesn't mean that others are in the same position.
Oh after the headache I had over the last two days with build errors I decided to find a rom on here that was already built would keep my Harpia going as long as possible and maybe get back to this in the future.
This isn't something i'm entirely familiar with and given the fact that the big lineage build tree swap just happened I might wait to see if any of the other devs have anything new posted over the next month or two on the off chance someone gets it going. I have limited time due to my health to spend tinkering on stuff like this so for the moment the ResurrectionRemix v6.2.1 [Harpia] [8.1.0_r52] seems the easiest option until that pesky Volte issue is resolved perhaps.
On a side note ... oooh whats SomeFeaK OS and COSP?? Will they work on Harpia??? Sounds interesting!
Oh after the headache I had over the last two days with build errors I decided to find a rom on here that was already built would keep my Harpia going as long as possible and maybe get back to this in the future.
This isn't something i'm entirely familiar with and given the fact that the big lineage build tree swap just happened I might wait to see if any of the other devs have anything new posted over the next month or two on the off chance someone gets it going. I have limited time due to my health to spend tinkering on stuff like this so for the moment the ResurrectionRemix v6.2.1 [Harpia] [8.1.0_r52] seems the easiest option until that pesky Volte issue is resolved perhaps.
On a side note ... oooh whats SomeFeaK OS and COSP?? Will they work on Harpia??? Sounds interesting!
Oh, well, I'm glad you found something for your harpia. And yes, COSP is already working here (although the latest versions aren't booting due to SELinux issues I gotta solve at some point lol), here you go: https://forum.xda-developers.com/g4-play/development/rom-cosp-t3897762 and SomeFeaK OS is still a WIP but it's working just fine, it's a LineageOS fork. The source is here: https://github.com/SomeFeaKOS, feel free to take a look and have fun!
Oh, well, I'm glad you found something for your harpia. And yes, COSP is already working here (although the latest versions aren't booting due to SELinux issues I gotta solve at some point lol), here you go: https://forum.xda-developers.com/g4-play/development/rom-cosp-t3897762 and SomeFeaK OS is still a WIP but it's working just fine, it's a LineageOS fork. The source is here: https://github.com/SomeFeaKOS, feel free to take a look and have fun!
Yeah I just saw them in the forum list! Lol i dont know how i missed the COSP post.
At this point im thinking of having a look and seeing what a few of them are like. COSP's concept sounds interesting indeed. Anything to take some power and privacy back from Google!
Oh, well, I'm glad you found something for your harpia. And yes, COSP is already working here (although the latest versions aren't booting due to SELinux issues I gotta solve at some point lol), here you go: https://forum.xda-developers.com/g4-play/development/rom-cosp-t3897762 and SomeFeaK OS is still a WIP but it's working just fine, it's a LineageOS fork. The source is here: https://github.com/SomeFeaKOS, feel free to take a look and have fun!
Just installed lineage-16.0-20181230-UNOFFICIAL-harpia from 14.1 Lineage, Used TWRP to wipe cache, delvik, data and internal Storage. I kept EXT SD card untouched.
My phone is REBOOTING every time the phone either times out (screen saver) or I press the SLEEP button. Annoying. Any suggestions? Don't want to reload all my apps because of this problem. If no quick fix, I will revert to 14.1 Nougat 7.1.2
Some more info. Loaded gapps_arm_cancro_9.0_pie.zip after loading 16.0.zip (since I read this ROM uses ARM) Every time I try to log into Wi-Fi, it "Fails to Save Network" and "Fails to Connect to Network".
I have Developer mode enabled.
=== WORK AROUND ===
It seems a cold restart fixes it (properly power it off and power it up). It seems the problem will present on first setup and boot.
=== DESCRIPTION ===
Same problem, any screen off event (phone answering, timeout or screen lock button) will trigger an automatic restart.
lineage-16.0-20190116-UNOFFICIAL-harpia.zip with open_gapps-arm-9.0-mini-20190323.zip
It happens either with or without an Screen Lock (None, Swipe, Pattern)
Device: XT1601/tefmx (Movistar Mexico)
On restart no settings changes will be saved.
Formatting SD Card as Internal Storage rekindles reboot bug
lineage-16.0-20190116-UNOFFICIAL-harpia.zip with open_gapps-arm-9.0-mini-20190323.zip
Device: XT1601/tefmx (Movistar Mexico)
Formatting the sdcard as internal storage makes the reboot bug on screen lock begin again. Dalvik and cache wipe didn't work.
I did a factory reset and did the cold boot and fixed the reboot bug. Then proceeded to reformat the sd card as internal storage and moved the data to the card and the bug reappeared. Then the bug won't disappear even with a cold boot.
Tried to format it back to portable sd card, and a second factory reset and surprisingly the sd card appeared as internal storage. I formatted it back to portable and once again to internal storage and the bug wouldn't disappear.
I formatted it back to portable once again and did a cold boot, the bug disappeared.
There's a requirement for sdcard as internal storage?
Here's adb logcat on screen lock button press.
HTML:
04-10 23:57:48.876 1531 1531 W Looper : Slow dispatch took 133ms main h=com.android.server.job.JobSchedulerService$JobHandler c=null m=4
04-10 23:57:48.908 337 7153 D audio_hw_primary: start_input_stream: exit
04-10 23:57:48.931 4872 4891 I MicroDetectionWorker: onReady
04-10 23:57:48.931 4872 4896 W SpeechLevelGenerator: Really low audio levels detected. The audio input may have issues.
04-10 23:57:50.703 337 529 D audio_hw_primary: out_standby: enter: stream (0xb34d5680) usecase(0: deep-buffer-playback)
04-10 23:57:50.973 337 529 D audio_hw_primary: disable_audio_route: reset and update mixer path: deep-buffer-playback
04-10 23:57:50.977 337 529 D hardware_info: hw_info_append_hw_type : device_name = speaker
04-10 23:57:50.977 337 529 D audio_hw_primary: disable_snd_device: snd_device(2: speaker)
04-10 23:57:51.048 1531 1629 D WindowManager: powerPress: eventTime=460978 interactive=true count=1 beganFromNonInteractive=false mShortPressOnPowerBehavior=1
04-10 23:57:51.048 1531 1629 I PowerManagerService: Going to sleep due to power button (uid 1000)...
04-10 23:57:51.050 1531 1556 I DreamManagerService: Entering dreamland.
04-10 23:57:51.052 1531 1556 I PowerManagerService: Dozing...
04-10 23:57:51.052 1531 1531 W UsageStatsService: Event reported without a package name
04-10 23:57:51.085 1531 1552 I DreamController: Starting dream: name=ComponentInfo{com.android.systemui/com.android.systemui.doze.DozeService}, isTest=false, canDoze=true, userId=0
04-10 23:57:51.099 1691 1691 V StatusBar: mStatusBarWindow: com.android.systemui.statusbar.phone.StatusBarWindowView{19925ff V.ED..... ........ 0,0-720,54} canPanelBeCollapsed(): false
04-10 23:57:51.109 1691 1691 I vol.Events: writeEvent dismiss_dialog volume_controller
04-10 23:57:51.124 1531 1552 D AutofillManagerService: Close system dialogs
04-10 23:57:51.133 362 362 W AudioFlinger: createTrack_l(): mismatch between requested flags (00000004) and output flags (00000002)
04-10 23:57:51.142 1691 1821 W AudioTrack: AUDIO_OUTPUT_FLAG_FAST denied by server; frameCount 0 -> 9989
04-10 23:57:51.166 337 2992 D audio_hw_primary: start_output_stream: enter: stream(0xb34d5680)usecase(0: deep-buffer-playback) devices(0x2)
04-10 23:57:51.167 337 2992 D audio_hw_primary: select_devices: out_snd_device(2: speaker) in_snd_device(0: )
04-10 23:57:51.167 337 2992 I msm8916_platform: platform_check_and_set_codec_backend_cfg: Usecase bitwidth 16, samplerate 48000, backend_idx 0
04-10 23:57:51.167 337 2992 I msm8916_platform: platform_check_codec_backend_cfg Codec selected backend: 0 current bit width: 16 and sample rate: 48000
04-10 23:57:51.167 337 2992 D msm8916_platform: platform_check_codec_backend_cfg: resetting sample_rate back to default, backend_idx: 0
04-10 23:57:51.167 337 2992 I msm8916_platform: platform_check_codec_backend_cfg Codec selected backend: 0 updated bit width: 16 and sample rate: 48000
04-10 23:57:51.167 337 2992 D hardware_info: hw_info_append_hw_type : device_name = speaker
04-10 23:57:51.167 337 2992 D audio_hw_primary: enable_snd_device: snd_device(2: speaker)
04-10 23:57:51.167 337 2992 D audio_route: Apply path: speaker
04-10 23:57:51.179 337 2992 W audio_hw_utils: audio_extn_utils_update_stream_app_type_cfg: App type could not be selected. Falling back to default
04-10 23:57:51.179 337 2992 I audio_hw_primary: select_devices Selected apptype: 69936
04-10 23:57:51.179 337 2992 I audio_hw_utils: audio_extn_utils_send_app_type_cfg app_type 69936, acdb_dev_id 15, sample_rate 48000
04-10 23:57:51.179 337 2992 D ACDB-LOADER: ACDB -> send_audio_cal, acdb_id = 15, path = 0
04-10 23:57:51.179 337 2992 D ACDB-LOADER: ACDB -> send_asm_topology
04-10 23:57:51.179 337 2992 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TOPOLOGY_ID
04-10 23:57:51.179 337 2992 D ACDB-LOADER: ACDB -> send_adm_topology
04-10 23:57:51.179 337 2992 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TOPOLOGY_ID
04-10 23:57:51.179 337 2992 D ACDB-LOADER: ACDB -> send_audtable
04-10 23:57:51.179 337 2992 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE_SIZE
04-10 23:57:51.179 337 2992 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE
04-10 23:57:51.180 337 2992 D ACDB-LOADER: ACDB -> AUDIO_SET_AUDPROC_CAL
04-10 23:57:51.180 337 2992 D ACDB-LOADER: ACDB -> send_audvoltable
04-10 23:57:51.180 337 2992 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_STEP_TABLE
04-10 23:57:51.180 337 2992 D ACDB-LOADER: ACDB -> AUDIO_SET_AUDPROC_VOL_CAL
04-10 23:57:51.180 337 2992 D ACDB-LOADER: ACDB -> send_afe_cal
04-10 23:57:51.180 337 2992 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AFE_COMMON_TABLE
04-10 23:57:51.180 337 2992 D : Failed to fetch the lookup information of the device 0000000F
04-10 23:57:51.180 337 2992 D ACDB-LOADER: ACDB -> AUDIO_SET_AFE_CAL
04-10 23:57:51.180 337 2992 D ACDB-LOADER: ACDB -> send_hw_delay : acdb_id = 15 path = 0
04-10 23:57:51.180 337 2992 D ACDB-LOADER: ACDB -> ACDB_AVSYNC_INFO: ACDB_CMD_GET_DEVICE_PROPERTY
04-10 23:57:51.180 337 2992 W audio_hw_utils: audio_extn_utils_send_audio_calibration: No audio calibration for usecase type = 0
04-10 23:57:51.180 337 2992 D audio_hw_primary: enable_audio_route: apply mixer and update path: deep-buffer-playback
04-10 23:57:51.180 337 2992 D audio_route: Apply path: deep-buffer-playback
04-10 23:57:51.182 337 2992 D audio_hw_primary: select_devices: done
04-10 23:57:51.185 1531 1556 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
04-10 23:57:51.192 1531 1556 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8916.so from current namespace instead of sphal namespace.
04-10 23:57:51.198 337 2992 D msm8916_platform: platform_set_channel_map mixer_ctl_name:Playback Channel Map0
04-10 23:57:51.198 337 2992 D msm8916_platform: platform_set_channel_map: set mapping(1 2 0 0 0 0 0 0) for channel:2
04-10 23:57:51.202 1531 1556 W Adreno-EGL: <qeglDrvAPI_eglQueryContext:4368>: EGL_BAD_ATTRIBUTE
04-10 23:57:51.205 1691 1691 I vol.Events: writeEvent dismiss_dialog volume_controller
04-10 23:57:51.217 258 258 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8916.so from current namespace instead of sphal namespace.
04-10 23:57:51.219 258 258 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8916.so from current namespace instead of sphal namespace.
04-10 23:57:51.237 337 2992 D audio_hw_primary: start_output_stream: exit
04-10 23:57:51.248 1531 1556 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8916.so from current namespace instead of sphal namespace.
04-10 23:57:51.356 1531 1556 E Sensors : als setDelay
04-10 23:57:51.359 1531 1556 E Sensors : als poll interval: 200
04-10 23:57:51.774 1531 1556 I DisplayPowerController: Blocking screen off
04-10 23:57:51.775 1531 1556 I DisplayPowerController: Unblocked screen off after 1 ms
04-10 23:57:51.819 1531 1556 E Sensors : AccSensor::setEnable handle:1 enable:0
04-10 23:57:51.819 1531 1556 E Sensors : AccSensor::setEnable handle:1 oldStatus=1 newStatus=0
04-10 23:57:51.820 1531 1556 E Sensors : AccSensor::setEnable finished!!!
04-10 23:57:51.827 1531 1556 E libEGL : call to OpenGL ES API with no current context (logged once per thread)
04-10 23:57:51.832 1531 1556 E LightsService: Light requested not available on this device. 2
04-10 23:57:51.833 258 258 D SurfaceFlinger: Set power mode=0, type=0 flinger=0xb01b6000
04-10 23:57:51.833 1531 1554 I DisplayManagerService: Display device changed state: "Built-in Screen", OFF
04-10 23:57:51.835 258 258 D qdhwcomposer: hwc_setPowerMode: Setting mode 0 on display: 0
04-10 23:57:51.866 1531 1591 W LocalDisplayAdapter: Unable to find color mode 0, ignoring request.
04-10 23:57:51.877 1531 1629 I InputReader: Reconfiguring input devices. changes=0x00000004
04-10 23:57:51.912 1531 1546 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
04-10 23:57:51.913 1531 1546 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
04-10 23:57:51.947 4872 4891 I MicroDetector: Keeping mic open: false
04-10 23:57:51.947 4872 4901 I DeviceStateChecker: DeviceStateChecker cancelled
04-10 23:57:51.948 4872 4900 I AudioController: internalShutdown
04-10 23:57:51.949 4872 4905 I MicroRecognitionRunner: Stopping hotword detection.
04-10 23:57:51.960 337 664 D audio_hw_primary: in_standby: enter: stream (0xb34af2a0) usecase(16: audio-record)
04-10 23:57:52.001 337 664 D audio_hw_primary: disable_audio_route: reset and update mixer path: audio-record
04-10 23:57:52.007 337 664 D hardware_info: hw_info_append_hw_type : device_name = voice-rec-mic
04-10 23:57:52.007 337 664 D audio_hw_primary: disable_snd_device: snd_device(81: voice-rec-mic)
04-10 23:57:52.008 1531 1546 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
04-10 23:57:52.020 337 337 D audio_hw_primary: in_set_parameters: enter: kvpairs=routing=0
04-10 23:57:52.028 337 664 D audio_hw_primary: adev_close_input_stream: enter:stream_handle(0xb34af2a0)
04-10 23:57:52.028 337 664 D audio_hw_primary: in_standby: enter: stream (0xb34af2a0) usecase(16: audio-record)
04-10 23:57:52.033 4872 4900 I MicrophoneInputStream: mic_close SR : 16000 CC : 16 SO : 1999
04-10 23:57:52.034 4872 4900 E AudioSource: Stop listening is called on already closed AudioSource
04-10 23:57:52.035 4872 4896 I MicroRecognitionRunner: Detection finished
04-10 23:57:52.063 4872 6286 I PBSessionCacheImpl: Deleted sessionId[1046341737720] from persistence.
04-10 23:57:52.074 1691 1691 D StatusBar: disable<e i a s b h r c s > disable2<q i n >
04-10 23:57:52.103 1531 1546 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
I'm very interested in lineageos 16 for this device. I installed 14.1 on the device of my girlfriend and a friend of mine. In the long term i want to let them use Android 9. do you guys plan to officially support lineagos 16 on this device?
Maybe I'll buy a used harpia to support the development and report errors etc.
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), 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.
Instructions :
Download the latest build and gapps
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
Builds :
Expect builds to be published per-post.
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks @Luk1337 for this thread template.
XDA:DevDB Information LineagOS 16.0 for Moto G4 Play, ROM for the Moto G4 Play
Replaced the whole way in that we handle denials for vendor modules, both private and public allow rules have been put together to make them easier to maintain.
Removed obsolete and unnecessary flags.
Brought back old kernel page shrink API as it wasn't compatible with our version of kgsl (causing GPU lags and crashes during first boot).
Fixed PowerHAL SELinux denials which caused zygote to crash whenever you plugged an USB cable (not seen by users, happened during test builds).
Reverted all patches related to power saving as they didn't play well with this device.
Added and fixed FM Radio support.
Ported some configs and properties from cedric.
General performance improvements (thread selection for dexpreopt).
Decrease GPS logging.
Enable smart battery (experimental).
Use lzma to build recovery imge.
Disable vulkan.
Setup zram during init: use lz4 algorithm, decrease disk size to 256 MB instead of 512 MB, use 4 compression threads.
General performance improvements for text fields and window renders.
Increased media volume and voice call steps to 60 and 7, respectively.
Fixed HALs issues with FM Radio.
Disabled OEM unlock toggle.
Shorten shutdown time.
Enable sustained performance mode.
Increase media and voice call volume steps to 60 and 7 respectively.
Compiled SnapDragon Camera.
Improve performance and stability on: EXT4, sdcardfs, timing, networking: tcp/diag, encryption, scheduling, ALSA, ksm, generic atomic reads for arm.
Pass new clocks for both CPU and GPU: 1.36 GHz and 465 MHz, respectively.
Fixed kernel issues.
Improved display default colour set (KCAL).
Improved responsiveness.
Force enter deep sleep.
Fixed CPU hotplugging.
Fixed input lag.
Fixed several UI crashes.
Fixed UI overlay errors.
Fixed all kernel bugs related to sdcardfs permissions (causing random kernel panics/reboots).
Release notes: Rolled back to Pixys common tree, please test. You should be able to flash this build on top of the previously working one without any issues.
