LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.
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.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for LineageOS 16.0 builds for OnePlus 3/3T. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed 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
Tips:
You need at least OxygenOS 9.0.2 firmware, otherwise you'll get error 7 when installing the zip. Latest firmware is recommended.
Installation:
First time flashing LineageOS 16.0 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Official TWRP 3.3 or higher is highly recommended: https://twrp.me/oneplus/oneplusthree.html)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
......
Download:
Official: https://download.lineageos.org/oneplus3
Last unofficial: https://androidfilehost.com/?fid=1395089523397903569
XDA:DevDB Information
LineageOS, ROM for the OnePlus 3
Contributors
dianlujitao
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Version Information
Status: Beta
Created 2018-11-13
Last Updated 2019-08-12
Reserved
Changelog:
2018.11.13:
Initial release
2018.11.17:
Sync latest source
Fixed directly reboot to recovery when attempting to enter power on password when secure boot enabled
Downgraded kernel to LA.UM.7.5.r1-02500-8x96.0 due to CAF stability regression, but there's still a race condition which could cause random kernel panic, especially when attempting to wake up the device, I'm still debugging on this.
Improved GPS performance
Minor bug fixes
2018.11.29:
Sync latest source
Kernel baseline updated to LA.UM.7.6.r1-03600-89xx.0
Thanks to a clue provided by @markakash , the "random kernel panic on wake up" issue seems to be fixed now. The ROM is probably stable enough for daily use, so I call it "beta" instead of "alpha" now. Please report if you still have the issue.
Minor bug fixes
2018.12.02:
Sync latest source
IMS experiments, VoLTE is confirmed working, VoWiFi is untested
Battery life optimization
Fix fingerprint sensor not respond on first boot and after user switched
Minor bug fixes
2018.12.05:
Sync latest source
SELinux enforcing for now, let me know if there're any regressions
Minor bug fixes
2018.12.15:
Sync latest source
Fix some suspend issue
Kernel baseline updated to LA.UM.7.5.r1-03700-8x96.0
Minor bug fixes
2018.12.22:
Sync latest source
Slider key fix by @nvertigo67
App launch boost & touch boost, hope it helps reduce lagging
2018.12.30:
Sync latest source
Kernel baseline updated to LA.UM.7.5.r1-04000-8x96.0
WiFi display support
Bug fixes & improvements
2019.1.1:
Sync latest source
Various bugs in the last build have been addressed
Working unofficial SU addon: https://androidfilehost.com/?fid=11410963190603887268
Happy New Year & Enjoy!
2019.1.12:
Sync latest source
Add support for always-on-display
Minor bug fixes
2019.1.24:
Sync latest source
Fix touchscreen when gesture disabled
Fix whatsapp and CamScanner camera issue? Not sure, need feedback
Minor bug fixes
2019.2.10:
Sync latest source
Update kernel to LA.UM.7.5.r1-04100-8x96.0
Livedisplay & touchscreen gestures internal API migration
Allow disabling new USB gadgets when the device is locked
Minor bug fixes
2019.3.1:
Sync latest source
Fix weird color after boot? Need your confirmation
Performance optimizations
New offmode charging animation
Minor bug fixes
Note that some features/bugfixes will NOT be included in the upcoming official builds, be aware before switching from unofficial to official.
Future:
https://download.lineageos.org/oneplus3/changes/
Your opinion on migrating to official Pie firmware
dianlujitao said:
As you're aware, OnePlus started Pie closed beta days ago, and there're already leaked builds. I made a new Lineage build with blobs from one OOS9.0 leak, installed and updated firmware. On first boot after fw update, when boot animation was done, unexpectedly, I didn't see my launcher desktop as usual, but an "Decryption unsuccessful" warning telling me that my data was corrupted. Undoubtedly, after rebooting to TWRP it failed to mount /data thus I lost everything on my internal storage.
After several experiments I finally figured out the cause:
If your data is encrypted and bootloader is unlocked, after upgrading to Pie modem firmware, there's 100% chance of your data to become corrupted, and probably no way to restore them. The cause is on firmware side, probably something wrong with key migration, so there's no way for 3rd party developers to fix it. Note that which ROM was in use pre-upgrade doesn't matter at all, i.e., if bootloader was unlocked and you were upgrading from OOS 5.0.8(enforce encryption by default) to OOS 9.0, you'll lose all personal data after reboot from recovery installation. Interestingly, everything works as expected if bootloader was locked.
I couldn't comprehend why do they apply diverse low-level strategies to locked and unlocked bootloader. Arguably this is a bug and should be fixed when they started rolling OTA updates to the public, but it's also possible that this is by design and aims to restrict "unsafe" operations. Regardless, always be careful and backup your data before upgrading firmware in the near future.
Click to expand...
Click to collapse
Unfortunately they still didn't fix the issue in the OxygenOS 9.0 Community Beta released hours ago, in contract their PR claimed "SW team is aware of this issue" during the early closed beta stage. Given the fact the issue persists in both public H2OS and OOS build, I highly doubt if they're actively working on fixing the issue or they'd even gaf. Ofc it's still possible but very unlikely for them to fix it in future builds.
Now I'd like to know your opinion on migrating to Pie firmware. Device owners with encrypted data and unlocked bootloader MUST either backup data or relock bootloader before installing new firmware, others are not affected. Please vote.
Nice
Is it possible to update with a wipe system only ?
good
whats the difference in this build and does this uses 4.4 kernel ?
Playa82 said:
Finally
Is it possible to update with a wipe system only ?
Click to expand...
Click to collapse
Why this question is asked each time ?
You have TWRP right ? So backup your current install, flash without wiping, if it goes wrong, you know you have to clean flash, simple.
Plus, from the O.P of this thread:
O.P said:
Installation:
First time flashing LineageOS 16.0 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Latest official TWRP is highly recommended: https://twrp.me/oneplus/oneplusthree.html)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
Reboot
Click to expand...
Click to collapse
lol, right when I clean flashed 15.1 and reinstalled everything from too many dirty flashes
karkiankit said:
does this uses 4.4 kernel ?
Click to expand...
Click to collapse
Why don't you check yourself? OP clearly states which kernel is in use:
https://github.com/dianlujitao/android_kernel_oneplus_msm8996/blob/lineage-16.0/Makefile#L1-L3
Nice!.. op3 community love u
Thank you
Weeew the legend is back. Awesome job
hi guys, what about these builds https://nyyu.tk/builds i also get ota update nightly
ele95 said:
hi guys, what about these builds https://nyyu.tk/builds i also get ota update nightly
Click to expand...
Click to collapse
Tried 9/11/18 build from jenkins. It wouldn't boot. You are welcome to try his latest one though and check if it boots.
Screenshots pls... Anyone??
Encryption still not working
Reboots to recovery right after "enter PIN" shows up
Racc145 said:
Encryption still not working
Reboots to recovery right after "enter PIN" shows up
Click to expand...
Click to collapse
IIRC, we need OnePlus sources from Android Pie for encryption to work correctly.
pjgowtham said:
Tried 9/11/18 build from jenkins. It wouldn't boot. You are welcome to try his latest one though and check if it boots.
Click to expand...
Click to collapse
dirty flash works and bootup fine for me but there is no sim signal so i revert to old one
Racc145 said:
Encryption still not working
Reboots to recovery right after "enter PIN" shows up
Click to expand...
Click to collapse
The same happened to me also. I'm encrypted on f2fs coming from OOS with a clean install.
@dianlujitao could you please add in the OP that it needs to be installed on an unencrypted phone - assuming that the reboot to recovery is caused by booting on an encrypted device.
Sent from my OnePlus3T using XDA Labs
Sometimes when I try to unlock using the fingerprint reader the screen stays black, while the buttons light up. The phone freezes and I need to reboot it. Someone else experienced the same issue?
Racc145 said:
Encryption still not working
Reboots to recovery right after "enter PIN" shows up
Click to expand...
Click to collapse
you knew that going in this, so why write and be supprised?
Related
[DEVELOPMENT] - CM12.1 - Android 5.1 - FreeXperia Project
CyanogenMod is a free, community built distribution of Android 5.1 which greatly extends the capabilities of your phone.
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.
*/
XDA:DevDB Information
[DEVELOPMENT] - CM12.1 - Android 5.1 - FreeXperia Project, ROM for the Sony Xperia Z3 Compact
Contributors
jerpelea
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2014-12-02
Last Updated 2015-04-13
HOWTO
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
ENJOY AN UNOFFICIAL CM RELEASE BROUGHT TO YOU BY FreeXperia Team
PLEASE DONT MIRROR OUR ROMS
Homepage
www.freexperiaproject.net
thanks to all who made this possible supporting us
contributing with code, donations or even trusting us
thanks to SONY that made all this possible !
the build should be here soon: http://fxpblog.co/cyanogenmod/cyanogenmod-12/
we have enabled daily builds
if your device is not yet in the list will appear soon (1 day,1 week, 1 month) no ETA please
but you have to remember that is an early alpha build
Thread closed until there is a build available
Thread cleaned
@jerpelea, please PM a mod or report this post to get the thread re-opened immediately.
Now that the daily builds are continued, have you or any other dev worked on CM12 for our device?
I am currently able to compile, but there seems to be a couple of issues that users are reporting,
Problems with com.qualcomm.location.apk
Updater script errors in recognizing proper device
System bootloops after 'starting apps'
Code:
E/installd( 269): DexInv: --- END '/system/priv-app/com.qualcomm.location/com.qualcomm.location.apk' --- status=0x0100, process failed
D/AndroidRuntime( 4634): Shutting down VM
E/AndroidRuntime( 4634): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
It might be that I am not importing all the necessary repositories or the wrong ones (in my local manifests),
I would be grateful if device specific repos can be mentioned in the OP or second post
Thank you
Merry Christmas!
Can't wait for my Z3C build to be available.
AlexBurnout77 said:
Can't wait for my Z3C build to be available.
Click to expand...
Click to collapse
On that topic -- why has this been re-opened if there are still no builds?
@jerpelea can we get at least a vague explanation of what's halting the builds from being made/uploaded?
Exactly. If they wanted to give us a full working built they can. I dont understand why theyre dragging thier boots, unless they want to release lollipop stock first.
someone755 said:
On that topic -- why has this been re-opened if there are still no builds?
@jerpelea can we get at least a vague explanation of what's halting the builds from being made/uploaded?
Click to expand...
Click to collapse
g0ldenchild562 said:
Exactly. If they wanted to give us a full working built they can. I dont understand why theyre dragging thier boots, unless they want to release lollipop stock first.
Click to expand...
Click to collapse
The builds weren't being uploaded because the build server was down for a couple of weeks. Now that it's back up things should be getting back to normal.
They can't give us a full working build because the builds aren't fully working. Even with Sony sources and binaries the modem still isn't working, CM12 isn't fairing much better.
Gairtial said:
The builds weren't being uploaded because the build server was down for a couple of weeks. Now that it's back up things should be getting back to normal.
They can't give us a full working build because the builds aren't fully working. Even with Sony sources and binaries the modem still isn't working, CM12 isn't fairing much better.
Click to expand...
Click to collapse
Well then the thread sbouldnt have been reopened. If theres nk available builds yet...
Yeah I'm not sure why they reopened it when they're not doing CM12 builds.
Did anyone flashed first release? What's working and not working.
Using the build from the 28th
Confirmed not working & issues:
*cell service
*camera
*Brightness slider is finicky
*device gets VERY hot
*massive battery drain
Things that work on this CM rom but not the latest AOSP build:
*NFC
*sd Card Support
*USB mounting to a PC
* Location
Notes:
This installs the stock CM recovery so make sure to get rom and gapps installed via TWRP the first go.
I had to edit the updater-script to flash. Removed the first line of device checks as it saw mine as a aries and would not flash
PS, for the love of all things holy, please setup a mirror. The current provider is just shy of torture.
finally we get one build,will flash.wait for my report
edit:lol,saw it,plan is over
edit2:still flashed it,it seems we have baseband at least(not display unknown),on its first boot,i noticed it's searching signal,then disappeared,checked baseband not unknown,tried to search for carrier but it never ends.
did a logcat,before logcat I turned on airplane mode,after its beginning i disabled airplane mode,tried to search for operator,then turned it to lte mode then tried to search again.
https://www.dropbox.com/s/nfexgudos3bni87/1.txt?dl=0
I don't understand why two built on 28 december ? One 280Mo and an other 285Mo .
http://uploaded.net/f/4bbo69
You can see to the bottom one this page .
Thanks i'm very happy to see CM12 on this device
mick711 said:
I don't understand why two built on 28 december ? One 280Mo and an other 285Mo .
http://uploaded.net/f/4bbo69
You can see to the bottom one this page .
Thanks i'm very happy to see CM12 on this device
Click to expand...
Click to collapse
the other one is for z3.I think I didn't see more builds..
Just tried the latest renamed nightly for (z3c instead of aries)-
FXP-cm-12-20141228-UNOFFICIAL-z3c.zip
The WIFI radio seems to work - but the LTE and voice radio connects
right at boot and then disconnects and goes away.
On shutdown/restart the same thing happens - LTE/Voice connects at first
and then it goes away.
I saw funky radio issues when testing the pure AOSP aries builds-
so it may not be just the CM12 ROMS.
I also had to edit the z3c zip file to allow the aries product name
so I could install it from doomlord's stock CWM kernel recovery image-
but that was minor compared to the radio issues.
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.
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.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for official LineageOS 14.1 builds for OnePlus 3/3T. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed 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
Known bugs:
Front camera is buggy, due to the buggy camera HAL Fixed by OnePlus
Installation:
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (See #2 for details)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package, install the SU addon package(https://download.lineageos.org/extras, choose arm64)
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
......
Download:
https://download.lineageos.org/oneplus3
XDA:DevDB Information
LineageOS, ROM for the OnePlus 3
Contributors
dianlujitao, Grarak
Source Code: https://github.com/lineageos
ROM OS Version: 7.x Nougat
Version Information
Status: Nightly
Created 2016-11-09
Last Updated 2017-03-27
Release note:
New builds (after 2017/1/15) uses F2FS backported from 4.10 kernel, you may meet compatibility problems such as deadlocks, if you do, flash TWRP provided in OP and choose "Wipe -> Format Data" to format(not just wipe) your /data partition, this will clean the entire /data partition, including the emulated sdcard, so don't forget to backup your data before. After that, your data partition will be formatted into ext4, if you want to keep using f2fs, just convert fs type normally in TWRP.
[*]For oneplus3, my unofficial TWRP is recommended, as it's what I use. For 3T, TWRP 3.0.4 is recommended.
As of 2017/6/17, official TWRP for OnePlus 3(https://dl.twrp.me/oneplus3/) is updated with latest LineageOS kernel and OxygenOS decryption stuff, it builds against Omni 7.1.2 and supports both op3&3t, now it's the recommended recovery.
20170120 build includes sdcardfs, security fixes and camera fixes&improvements, touch to focus is fixed as well, if it's still not working, clean Snap's data. BTW N kernel source is released now, I'll take days to bring up, don't ask for ETA.
Regarding installation, we recommend that users wipe when switching to LineageOS, and reinstall their gapps. However, we recognize that this can be time consuming, so we are offering an EXPERIMENTAL (read as, if it fails, you’ll have to wipe anyways) solution. Visit http://lineageos.org/Update-and-Build-Prep/for more details
Started from lineage-14.1-20170207-nightly-oneplus3-signed.zip, we provide unified builds for both 3&3T, and you need to install certain firmware to pass the TrustZone assertion. Currently they're the OxygenOS Open Beta 19/11 ones. As oneplus won't update them every time new OTAs are rolling out, firmware from other versions might also pass the assertion.
FAQs:
My status bar quick pulldown and notification slider are broken, why?
See https://github.com/opengapps/opengapps/wiki/Notes-for-CMSetupWizard
Why the builds are unified?
Tell me the difference between OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883 and OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8, why not?
{
"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"
}
Latest Firmware files for oneplus3/oneplus3t -5.7.2017-
Make a nandroid backup before you proceed
Flash the following files using the latest official twrp to avoid any recovery related issues.
Make sure to do a clean flash if your rom requires an updated firmware.
Don't ever flash an oneplus3 firmware on oneplus3t or an oneplus3t firmware on oneplus3.
Oneplus3
Instructions only for oneplus3!
1-clean flash is recommended.
2-Falsh OnePlus3_OpenBeta19-FIRMWARE+MODEM-flashable.zip.
3-Flash the latest laos nightly.
4-optional: gapps arm64 7.1 and -su-addon arm64, this enables inbuild laos root.
5-Wipe Dalvik/cache and reboot.
Oneplus3t
Instructions only for oneplus3t!
1-clean flash is recommended.
2-Flash OnePlus3T_Beta10-(4-7-17)-FIRMWARE-flashable.zip.
3-Flash the latest laos nightly
4-optional: gapps arm64 7.1 and -su-addon arm64, this enables inbuild laos root.
5-Wipe Dalvik/cache and reboot.
For people who rather use the oxygenos camera:
Get OnePlusCameraV8-siankatabg.apk and OnePlusGallery-V8-siankatabg.apk
If you have problems after flashing any custom kernels please provide a log in the thread where you got the kernel from and not here!
Credits:
@nvertigo67 @djsubterrain @Eliminater @kamilmirza op3t firmware
@jamal2367 op3 firmware
@siankatabg oos camera/gallery port
Maybe let a CM member start the official thread?
@dianlujitao : Thanks for maintaining this.
Currently call audio is broken by sound trigger commit.
Even when that revert, noise cancellation not working / echo happens while in calls.
please fix this only issue.
RohanAJoshi said:
@dianlujitao : Thanks for maintaining this.
Currently call audio is broken by sound trigger commit.
Even when that revert, noise cancellation not working / echo happens while in calls.
please fix this only issue.
Click to expand...
Click to collapse
Steve is investigating on that
dianlujitao said:
Steve is investigating on that
Click to expand...
Click to collapse
That's great, waiting for noise cancellation fix.
I have a custom TWRP from the OOS 3.5.5 (OnePlus thread),
twrp-3.0.2-22-oneplus3.img
I think only that is working correctly with CM 14.1 Official ROM ?
osr.arora said:
I have a custom TWRP from the OOS 3.5.5 (OnePlus thread),
twrp-3.0.2-22-oneplus3.img
I think only that is working correctly with CM 14.1 Official ROM ?
Click to expand...
Click to collapse
Yes, 3.0.2.19 & 3.0.2.22 should work with every rom.
So use always this twrp versions to get sure.
dianlujitao said:
Steve is investigating on that
Click to expand...
Click to collapse
Finally someone official is here
Thank you very much!!!
Can you just tell me,
Is that included baseband/firmware inside the rom, 3.5.5 or 3.2.7 or mixed or sth else?
Thanks
Cheers
Is possible flash 14.1nightly on experimental? I have from 2 weeks
alteus83 said:
Is possible flash 14.1nightly on experimental? I have from 2 weeks
Click to expand...
Click to collapse
It is possible, but you can get some unexpected bugs...
Better to do a clean start, with full wipe.
And dirty flash upcoming nightlys.
Cheers
When i plug my Phone into the charger or my pc the charging icon wont show up (lighting bolt in the battery)
After install i tried a cache/dalvik clear, did not help
The Phone is connected to the computer, it says charging..
https://postimg.org/image/xj8af43tf/
yooouuri said:
When i plug my Phone into the charger or my pc the charging icon wont show up (lighting bolt in the battery)
After install i tried a cache/dalvik clear, did not help
The Phone is connected to the computer, it says charging..
https://postimg.org/image/xj8af43tf/
Click to expand...
Click to collapse
known issue with cm14.1
yooouuri said:
When i plug my Phone into the charger or my pc the charging icon wont show up (lighting bolt in the battery)
After install i tried a cache/dalvik clear, did not help
The Phone is connected to the computer, it says charging..
https://postimg.org/image/xj8af43tf/
Click to expand...
Click to collapse
This is known... There are some problems with battery icon and battery stats too...
@dianlujitao
OP need to add that bugs into to the bug list:
1. Echo (loudspeaker) noise calcellation
2. Battery stats reset + charging text + charging icon
3. GPS problems especially while driving. (you get a perfect gps fix but if you move fast "drive" you get wrong coordinates)
4. All bugs related to legacy HAL1
5. Srgb colors not working
Cheers
Ramalama said:
This is known... There are some problems with battery icon and battery stats too...
OP need to add that bugs into to the bug list:
1. Echo (loudspeaker) noise calcellation
2. Battery stats reset + charging text + charging icon
3. GPS problems especially while driving. (you get a perfect gps fix but if you move fast "drive" you get wrong coordinates)
4. All bugs related to legacy HAL1
Cheers
Click to expand...
Click to collapse
Agree! :good:
Ramalama said:
This is known... There are some problems with battery icon and battery stats too...
@dianlujitao
OP need to add that bugs into to the bug list:
1. Echo (loudspeaker) noise calcellation
2. Battery stats reset + charging text + charging icon
3. GPS problems especially while driving. (you get a perfect gps fix but if you move fast "drive" you get wrong coordinates)
4. All bugs related to legacy HAL1
Cheers
Click to expand...
Click to collapse
You guys may need to wait because cm14.1 is still highly experimental
So its waiting for OP to release some of their HAL?
Ramalama said:
This is known... There are some problems with battery icon and battery stats too...
@dianlujitao
OP need to add that bugs into to the bug list:
1. Echo (loudspeaker) noise calcellation
2. Battery stats reset + charging text + charging icon
3. GPS problems especially while driving. (you get a perfect gps fix but if you move fast "drive" you get wrong coordinates)
4. All bugs related to legacy HAL1
Cheers
Click to expand...
Click to collapse
Add on
5. In call volume slider not working in speaker or headset mode.
dianlujitao said:
You guys may need to wait because cm14.1 is still highly experimental
Click to expand...
Click to collapse
You have right, but that's the actual bug list that users know what's not working atm
I don't think that next few builds will not be highly experimental
yooouuri said:
So its waiting for OP to release some of their HAL?
Click to expand...
Click to collapse
Yes, till they release nougat.
mgear356 said:
Add on
5. In call volume slider not working in speaker or headset mode.
Click to expand...
Click to collapse
I know, but this bug is only since yesterday, there is a commit that broke it... I think it will be fixed on next 1-2 builds...
Cheers
I would appreciate if op could add link to supported twrp in the first post.. It would be really helpful..
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.*/
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
All of the LineageOS source code is available on their github.
What's NOT working
Camera
Hotspot
Installation instructions
Boot to recovery mode, use TWRP 3.0.2 only as TWRP 3.0.0 reportedly has issues with flashing it.
Do a factory reset.
Flash ROM, then flash GApps, and then flash the addons if any.
Reboot. First boot will take time.
Downloads
ROM - AndroidfileHost
Source
Device Tree
Kernel Source
Credits
@Olivier @AdrianDC
@Agent_fabulous @STRYDER~007
@AdrianDC and all others who worked in development for Sony devices.
XDA:DevDB Information
LineageOS 15.1, ROM for the Sony Xperia L
Contributors
corphish
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Version Information
Status: Alpha
Created 2018-02-19
Last Updated 2018-06-10
F.A.Q
Q. Why pre-alpha and all?
The reason why this build is pre-alpha, and in other words, simply unusable, is because deep sleep doesn't work, that means the phone cannot be kept idle (it can be if connected to power source). This is a big issue as it renders other (basic) functionalities useless. I wanted to fix this and then release, but have been out of luck. So I decided to release this anyway, just to let people know that work is being done on getting Lineage 15.x work on Xperia L. Even if this fails big time and the project needs to be abandoned, well atleast the people would get to use whatever worked. Ofcourse I am not giving up yet, unless I really really get frustrated. As of this build, flash it if interested, see how oreo looks like, and then flash back the old rom.
Q. What GApps to flash?
I did not use GApps during my testing, but if you want to use, use opengapps (8.0 ARM). Recommended - pico or micro packages. You do need to modify the installer scripts inside opengapps zip, otherwise installation would fail due to version mismatch.
Changelog
20180610 (Alpha 2)
- Fixed mobile data.
- Fixed issue which caused downloads to fail.
- Updated lineage sources.
20180224 (Alpha 1)
- Fixed deep sleep.
- Fixed proximity sensor.
- Updated lineage sources.
20180219 (Pre-alpha)
- Initial release.
Wow,I was excited,until the moment when my phone turned off and on,every 2 minutes,data transmission not working,I count on amendments in future updates.
Thanks dev.
#Taoshan4ever.
thank you bro. been waiting for this for a long time, many cheers to you
Deep sleep issue was present in every LOS 15 rom, especially lenovo roms, Can it be fixed by replacing libsuspend.so from nougat rom, what's actually the issue
kish11 said:
Deep sleep issue was present in every LOS 15 rom, especially lenovo roms, Can it be fixed by replacing libsuspend.so from nougat rom, what's actually the issue
Click to expand...
Click to collapse
In oreo, earlysuspend got removed from libsuspend, and our kernel uses used earlysuspend. So during initial boot (that is our kernel using earlysuspend, and no earlysuspend in libsuspend), device won't comeback on after I turn off the display, even if it was connected to power source.
An abandoned patch does exist though, which brings back earlysuspend support back to libsuspend. With that patch applied, device did comeback on after display was turned off, and it would function normally as long as power supply was connected to it (just like how it does now), deep sleep still did not work then.
Since the patch was abandoned, and depending on it would not be appropriate, I decided to bring autosleep in kernel, which I eventually did, deep sleep still doesn't work
Great!
Thanks for your hard working and not giving up :good:
It's worth testing, at least we can see how it looks like
wow this is a good news, but i think with more 800MB ram taoshan should use android go
Thank you for your hard works:angel: Corphish :angel:
Hope the bug dies soon :laugh:
Alpha 1
New build is up.
Changelog
Fixed deep sleep.
Fixed proximity sensor, now all the sensors should be working as usual.
Updated lineage-15.1 sources - Switched from staging/lineage-15.1 branch to lineage-15.1 branch. Some immediate changes you will notice are the new icons and the addition of Lineage setup wizard.
Now that this has graduated from pre-alpha, and the device can stay awake in idle, this makes the alpha build way more usable than the pre-alpha build. If you end up using this, and face bugs that are not mentioned in the "not working" list, please let me know by posting about it in this thread. Logs would be welcome, but a proper way of reproducing it would be good too.
P.S - Firefox still doesn't work ¯\_(ツ)_/¯
Links updated in OP.
1. device not booting properly using restart in power options, doesn't respond to any action until battery removed
2 flashlight not working, and the flashlight toggle interrupts the music playback.
3 downloads fail using jelly browser
and, cheers for your hard work @corphish, Thank you
kish11 said:
1. device not booting properly using restart in power options, doesn't respond to any action until battery removed
2 flashlight not working, and the flashlight toggle interrupts the music playback.
3 downloads fail using jelly browser
and, cheers for your hard work @corphish, Thank you
Click to expand...
Click to collapse
1. It works fine here, does take a bit of time though. :/
2. Because camera does not work. It will work when camera is fixed.
3. That is because, vold assigns our internal storage name as "7384-14B3" (atleast it looks like that in mine), so storage location for internal storage is "/storage/7384-14B3". Turns out that DownloadManager cannot handle storage locations with such name . Will try to workaround it in the next build.
Now that's awesome and quick. Great work @corpish
I have tried it. It's amazing and fast
But there are some problems
1. Phone restarts when phone get stuck, or when starting camera
2. Music playback stopped when flash light turned on
3. Downloading get unsuccessful in the stock browser
I think other users have already mentioned some of the following problems.( I think the real problem is with the download manager )
4. And there was no gapps for Oreo 8.1.
So I installed a unofficial gapps which was created for 8.1 and the setup keeps closing
I have only noticed these problems yet.
But it's a amazing ROM.
Thanks Corphish
Nikhil kuttu said:
I have tried it. It's amazing and fast
But there are some problems
1. Phone restarts when phone get stuck, or when starting camera
2. Music playback stopped when flash light turned on
3. Downloading get unsuccessful in the stock browser
I think other users have already mentioned some of the following problems.
4. And there was no gapps for Oreo 8.1.
So I installed a unofficial gapps which was created for 8.1 and the setup keeps closing
I have only noticed these problems yet.
But it's a amazing ROM.
Thanks Corphish
Click to expand...
Click to collapse
I have the same problems
Split screen is not working.it says not supported in any app even sys app.
And casting is not working as well.just after connecting it closes and search for device again
These are not a major problems
But the camera and flash are little impotent
Nikhil kuttu said:
Split screen is not working.it says not supported in any app even sys app.
And casting is not working as well.just after connecting it closes and search for device again
These are not a major problems
But the camera and flash are little impotent
Click to expand...
Click to collapse
If camera and flash are important then,
Flash Back !
I wont change my OS just to get camera and flash
Working again.
Even while it's in alpha stage I really like this Rom:laugh:
The app's stay in the same position even after long time
And now I'm using mostly Google go edition app's to keep the device fast as possible
{
"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 is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Code:
* [B][U]Your warranty is now void.[/U][/B]
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)Q: Whenever I try flashing any lineage-16.0 build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Oreo-based rom within a version of TWRP older than 3.2. Simply flash the linked below version 3.2 or higher, reboot back into recovery, and flash the rom zip again.
Q: I am seeing Error 7 when trying to flash a GApps package.
A: This is due to the system partition being too small to fit both the rom and the GApps package. You need to re-partition it with a tool such as the one created by Clamor (linked below). You will only need to do this once.
Q: When will any of the variants receive official builds from LineageOS?
A: Not before all the issues listed under "Bugs" below are fixed.
Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.
Q: What will some of the differences be between unofficial and official builds?
A: The following technical changes will take effect:
- Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
- Phone status > LineageOS updates will be activated, allowing for the OTA downloading of official builds.
- The official builds will be digitally signed by Lineage to prove that they do not contain malicious source code and are able to pass the Play Store's SafetyNet check.
Note: Each official build will be cooked and released by LineageOS on their schedule and only if no major unexpected bug is introduced into the source code. The developers will announce if and when their source code will be submitted to Lineage for official support and when we can expect to see the first official builds.
Q: How often will new builds be released?
A: About once a week for both deb and flo, as soon as possible after each new Android security patch level is merged, and of course whenever a new feature is added or a bug is fixed.
[REPARTITION] Nexus 7 (2013) Repartition [FLO/DEB] [16GB/32GB] [UA TWRP]
ROMs
pitrus-
- LTE: deb
- Wi-Fi: flo
LineageOS Extras
- addonsu-16.0-arm-signed.zip
- addonsu-remove-16.0-arm-signed.zip
Magisk
Open GApps
How to flash LineageOS and Open GApps1. Move any files you want to keep to your computer or flash drive via a USB OTG cable – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Boot into Recovery Mode (Hold volume up and Power button until you see TWRP's splash screen),
4. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
5. Swipe to Wipe at Bottom of Screen,
6. Back to Main start screen,
7. Wipe > Format Data,
8. Type 'Yes' and press blue checkmark at the bottom-right corner,
9. Go Back to Main Start Screen,
10. Move your LineageOS Rom and GApps Package to the internal storage,
11. Install > select a zip file to flash (optionally, Add More Zips > select another zip file to flash),
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
- Encryption does not work at all. Upon encrypting your tablet, you will be unable to reboot into System. This is a bug in all AOSP-based custom Pie roms for deb and flo.
- You tell us!
Changelog
All major features and bug fixes are discussed in detail by the developers in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- Every open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for deb and flo.
Sources
- deb device tree
- flo device tree
- kernel
- blobs
XDA:DevDB Information
LineageOS 16.0, ROM for the Nexus 7 (2013)
Contributors
ripee, followmsi, pitrus-, flex1911, Clamor
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: System partition large enough to accommodate the rom and GApps.
Version Information
Status: Stable
Current Stable Version: 9
Stable Release Date: 2019-08-11
Created 2019-02-22
Last Updated 2019-11-10
Reserved
Reserved
Awesome! Keep up the great work and thank you for keeping this devices development alive
JT1510365 said:
Awesome! Keep up the great work and thank you for keeping this devices development alive
Click to expand...
Click to collapse
All credit to followmsi and flex1911
oh yeah maga
make android great again
Is this the same ROM you can find in followmsi androidfilehost directory?
https://androidfilehost.com/?w=files&flid=289297
Yesterday I try the Ressurection Remix 7.0
Everything works fine.
But in Kodi i cannot use the h264 hardware decoder.
Have this Rom the same issue?
DaCl88 said:
Is this the same ROM you can find in followmsi androidfilehost directory?
https://androidfilehost.com/?w=files&flid=289297
Yesterday I try the Ressurection Remix 7.0
Everything works fine.
But in Kodi i cannot use the h264 hardware decoder.
Have this Rom the same issue?
Click to expand...
Click to collapse
Since the sources I linked are followmsi's, yes this is the same rom, but built more recently to take advantage of the lineage commits added since followmsi's last build. Because of this, it will have the same h.264 bug in Kodi.
Rom is working very well but I cannot flash Gapps. I chosen Pico 9.0 arm. Which one should I use ? Thank you !
gaja22 said:
Rom is working very well but I cannot flash Gapps. I chosen Pico 9.0 arm. Which one should I use ? Thank you !
Click to expand...
Click to collapse
Did you re-partition the memory, as described in the FAQ's in the OP?
ripee said:
All credit to followmsi and flex1911
Click to expand...
Click to collapse
Of course
To a person who has installed this ROM, I have one question. If the orientation is locked to Landscape, when you turn on the screen, does the screen start from landscape mode, or does it start from portrait mode and quickly rotates to landscape mode?
It does not happen on the official LOS 14.1, but it did happen with unofficial LOS 15.1. This rotation is problematic, because it often causes a significant delay when I turn on the screen, depending on the app I had been using.
Thx!
Will test this ROM!
yourrealking said:
To a person who has installed this ROM, I have one question. If the orientation is locked to Landscape, when you turn on the screen, does the screen start from landscape mode, or does it start from portrait mode and quickly rotates to landscape mode?
It does not happen on the official LOS 14.1, but it did happen with unofficial LOS 15.1. This rotation is problematic, because it often causes a significant delay when I turn on the screen, depending on the app I had been using.
Click to expand...
Click to collapse
Hello, my lock screen will be temporarily displayed in portrait then rotates to landscape.
Quick question. A full data wipe? As in a full data partition wipe including rom backups, pictures, videos, personal files? Cant say I have ever hear of a rom requesting this and I have been flashing roms for a decade. Perhaps I am missing something. Is this only the first time I flash and then a dirty flash for daily builds?
hlxanthus said:
Quick question. A full data wipe? As in a full data partition wipe including rom backups, pictures, videos, personal files? Cant say I have ever hear of a rom requesting this and I have been flashing roms for a decade. Perhaps I am missing something. Is this only the first time I flash and then a dirty flash for daily builds?
Click to expand...
Click to collapse
A full data wipe cleans the data partition on which user apps and system settings reside. Your personal files are on the internal storage partition, which does NOT get wiped by TWRP when factory wiping.
Yes, clean flash prior to the first flash, then dirty flash subsequent builds.
ripee said:
A full data wipe cleans the data partition on which user apps and system settings reside. Your personal files are on the internal storage partition, which does NOT get wiped by TWRP when factory wiping.
Yes, clean flash prior to the first flash, then dirty flash subsequent builds.
Click to expand...
Click to collapse
Read the OP's instructions again. It clearly says to wipe data and internal storage.
Hi and thanks for (the) pie. It works great for the main user but i have a strange problem with a secondary (or guest) user:
Whenever i switch to the secondary user the navigation bar (three buttons) disappears. The bar is not just hidden but seems to be really gone/killed. When switching back to the main user the bar is still missing and i need to restart to get it back. Any ideas?
The pie ROM works great on my Nexus. Thank you so much. It's amazing. I hope you plan to add the security patches every month. Thx.
hlxanthus said:
Read the OP's instructions again. It clearly says to wipe data and internal storage.
Click to expand...
Click to collapse
Yes, I have read the OP. Wiping both data and internal storage is for the sake of less experienced users who should be starting fresh no matter what rom they're coming from. As you have more experience, please use your judgment to wipe whatever you know needs to be wiped.
{
"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:
* 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.
*
*/
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of Android 12 (S), 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.
Bugs
What's working:
Boot
Audio Playback
Video Playback
Camera/Camcorder
DT2W
FM Radio
Hardware Encryption
RIL (LTE/CALL/SMS)
WiFi
Hotspot
Bluetooth
GNSS GPS
NFC (Tested on single sim E8 with PN547 chip, Please let me know if it's working on yours)
USB (ADB, MTP) If MTP not working on Windows, Uninstall HTC drivers.
Sensors
Touch
What's not working:
SELinux is permissive
You tell me.
Installation instructions
Download the zip(s).
Install MY TWRP
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash ROM.
Optional: Install the Google Apps addon package.
Supported models:
Single SIM : htc_mecwhl,htc_mectl,htc_mecul,htc_mecul_emea
Dual SIM : htc_mecdug,htc_mecdugl,htc_mecdwg,htc_mecdwgl
Downloads
Recovery : Unofficial E8 TWRP (Support decryption)
Gapps : MindTheGApps ARM 12.1
Rom :
Single SIM Variants
Dual SIM Variants
Sources
Device Trees
Kernel Trees
Vendor Trees
Donate
DONATE To Me
Big Thanks
LineageOS Team.
@ RavnPW for his contribution on E8 sources, especially vendor blobs and kernel change.
All M8/MSM8974 contributors.
Changelogs
2022/08/26
Fixed boot process delay issues.
2022/08/08
Updated with August security patches.
Upstream updates and fixes.
2022/07/14
Enable Wi-Fi Display.
Kernel updates to reduce boot time a little bit.
Updated DRM clearkey plugin to 1.3.
Fixed NFC options.
2022/07/13
Updated to Android 12.1.0_r11 with July security patches.
Upstream updates and fixes.
Fixed pn544 NFC firmware loading problems.
2022/06/14
Updated to Android 12.1.0_r7 with June security patches.
Upstream updates and fixes.
2022/05/15 - REUPLOADED
Updated to Android 12.1.0_r5 with May security patches.
Upstream updates and fixes.
2022/05/05 - Dual SIM
Fixed SIM card detection and telephony issues.
2022/04/08
Updated to Android 12.1.0_r4 with April security patches.
Updated stock app icons.
Upstream updates and fixes.
2022/03/21
Updated to Android 12L with March security patches.
Updated to LineageOS 19.1.
Upstream updates and fixes.
Clean flash recommended.
2022/02/17
Updated to Android 12.0.0_r29 with February security patches.
Upstream updates and fixes.
Bring back FMRadio
Fixed Touchscreen gestures and DT2W.
Bring back legacy RIL support.
2022/01/18
Initial release of LineageOS 19.0 for E8/E8D.
Screenshots
Thaks for your work. My smart is htc e8 dual, and i installed dual variant, but firmware dosnt recognize sim card, dont metter in which slot i installing sim card. Certainly phone doesn't have mobile network. Please fix it
tarkzim said:
Code:
* 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.
*
*/
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of Android 12 (S), 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.
Bugs
What's working:
Boot
Audio Playback
Video Playback
Camera/Camcorder
FM Radio
Hardware Encryption
RIL (LTE/CALL/SMS)
WiFi
Hotspot
Bluetooth
GNSS GPS
NFC (Tested on single sim E8 with PN547 chip, Please let me know if it's working on yours)
USB (ADB, MTP) If MTP not working on Windows, Uninstall HTC drivers.
Sensors
Touch
What's not working:
DT2W
FM Radio
SELinux is permissive
You tell me.
Installation instructions
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash ROM.
Optional: Install the Google Apps addon package.
Supported models:
Single SIM : htc_mecwhl,htc_mectl,htc_mecul,htc_mecul_emea
Dual SIM : htc_mecdug,htc_mecdugl,htc_mecdwg,htc_mecdwgl
Downloads
Recovery : Unofficial E8 TWRP (Support decryption)
Gapps : BiTGApps ARM 12.0
Rom :
Single SIM Variants
Dual SIM Variants
Sources
Device Trees
Kernel Trees
Vendor Trees
Donate
DONATE To Me
Big Thanks
LineageOS Team.
@ RavnPW for his contribution on E8 sources, especially vendor blobs and kernel change.
All M8/MSM8974 contributors.
I don't have this device, just build it with my latest changes for E8 users
Click to expand...
Click to collapse
It remains at HTC logo after I install the rom, wipe cache/dalvik and reboot system. I installed previous versions easily. What can be the problem?
alikarimi3 said:
It remains at HTC logo after I install the rom, wipe cache/dalvik and reboot system. I installed previous versions easily. What can be the problem?
Click to expand...
Click to collapse
You have to wait a bit longer, it might take a few minutes to boot up.
alximiktik said:
Thaks for your work. My smart is htc e8 dual, and i installed dual variant, but firmware dosnt recognize sim card, dont metter in which slot i installing sim card. Certainly phone doesn't have mobile network. Please fix it
Click to expand...
Click to collapse
I need more info, is baseband version display correctly under settings > about phone > android version?
Also can you give me logs by running following commands:
adb shell
logcat -b radio > /sdcard/radio.txt
Click to expand...
Click to collapse
tarkzim said:
You have to wait a bit longer, it might take a few minutes to boot up.
Click to expand...
Click to collapse
tarkzim said:
You have to wait a bit longer, it might take a few minutes to boot up.
Click to expand...
Click to collapse
I waited about 30 minutes. It remains at primary HTC logo not even reach lineageos logo. I have attached the picture.
It works good enough, Thanks for keeping device alive,
Lags, Reboots sometimes,
Sometimes freezes at HTC screen, reboots, lags on boot screen,
Freezes on official TWRP slash screen, installed new unofficial version, works but is slow
Sometimes works normal
Also Can't find advance reboot option,
[email protected] said:
It works good enough, Thanks for keeping device alive,
Lags, Reboots sometimes,
Sometimes freezes at HTC screen, reboots, lags on boot screen,
Freezes on official TWRP slash screen, installed new unofficial version, works but is slow
Sometimes works normal
Also Can't find advance reboot option,
Click to expand...
Click to collapse
Hello, since this device is old and only have 1.5GB of RAM, the performances wouldn't be that good for sure.
And yes, you have to use latest TWRP to prevent freezing after installing A12 ROM.
LOS still WIP, so some features are not yet added.
alikarimi3 said:
It remains at HTC logo after I install the rom, wipe cache/dalvik and reboot system. I installed previous versions easily. What can be the problem?
Click to expand...
Click to collapse
mine was also stucked, just try to press power button, dont know why but it works, also pluging the charger unfrezzes devices,
Magisk 24 works
zygisk works
LsPosed works
finally tried BitGApps not working - constant reboot, After factory reset it seems to be working
i hope we get stable release soon,
Thanks again
tarkzim said:
Code:
* 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.
*
*/
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of Android 12 (S), 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.
Bugs
What's working:
Boot
Audio Playback
Video Playback
Camera/Camcorder
FM Radio
Hardware Encryption
RIL (LTE/CALL/SMS)
WiFi
Hotspot
Bluetooth
GNSS GPS
NFC (Tested on single sim E8 with PN547 chip, Please let me know if it's working on yours)
USB (ADB, MTP) If MTP not working on Windows, Uninstall HTC drivers.
Sensors
Touch
What's not working:
DT2W
FM Radio
SELinux is permissive
You tell me.
Installation instructions
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash ROM.
Optional: Install the Google Apps addon package.
Supported models:
Single SIM : htc_mecwhl,htc_mectl,htc_mecul,htc_mecul_emea
Dual SIM : htc_mecdug,htc_mecdugl,htc_mecdwg,htc_mecdwgl
Downloads
Recovery : Unofficial E8 TWRP (Support decryption)
Gapps : BiTGApps ARM 12.0
Rom :
Single SIM Variants
Dual SIM Variants
Sources
Device Trees
Kernel Trees
Vendor Trees
Donate
DONATE To Me
Big Thanks
LineageOS Team.
@ RavnPW for his contribution on E8 sources, especially vendor blobs and kernel change.
All M8/MSM8974 contributors.
I don't have this device, just build it with my latest changes for E8 users
Click to expand...
Click to collapse
sim cards not recognized on my dual sim device also stuck at htc logo issues. I have uploaded radio.txt and baseband version files. Here is radio.txt link: https://drive.google.com/file/d/1OV7L6dtsJsS3tcBltlWFcBc7mk4dCGno/view?usp=sharing
can you fix it?
New build released
Updated to Android 12.0.0_r29 with February security patches.
Upstream updates and fixes.
Bring back FMRadio
Fixed Touchscreen gestures and DT2W.
Bring back legacy RIL support.
tarkzim said:
New build released
Updated to Android 12.0.0_r29 with February security patches.
Upstream updates and fixes.
Bring back FMRadio
Fixed Touchscreen gestures and DT2W.
Bring back legacy RIL support.
Click to expand...
Click to collapse
sim cards not recognized in this build too.
tarkzim said:
New build released
Updated to Android 12.0.0_r29 with February security patches.
Upstream updates and fixes.
Bring back FMRadio
Fixed Touchscreen gestures and DT2W.
Bring back legacy RIL support.
Click to expand...
Click to collapse
Thanks again, its way smoother now,
But whenever I toggle flashlight from quick setting, phone soft reboots
Hi
While restoring backup, phone got stuck on twrp splash screen,
Phone dont have rom, (it got stuck between the process of restore)
I Tried multiple TWRP (official and unofficial) , all get stuck at TWRP splash screen, cant go in TWRP,
is there any solution ?
is there another way of installing rom?
[email protected] said:
Hi
While restoring backup, phone got stuck on twrp splash screen,
Phone dont have rom, (it got stuck between the process of restore)
I Tried multiple TWRP (official and unofficial) , all get stuck at TWRP splash screen, cant go in TWRP,
is there any solution ?
is there another way of installing rom?
Click to expand...
Click to collapse
Make sure you are using TWRP 3.6.0, older version doesn't support Android 12 storage formats.
tarkzim said:
Make sure you are using TWRP 3.6.0, older version doesn't support Android 12 storage formats.
Click to expand...
Click to collapse
Ya it was stuck, it's known issue with Android 12, luckily I had magick installed had to flash patched boot again
Then some how manage to run TWRP ,
Then was unable to restore any backup ( invalid partition and all error 225)
Then had to format data in ext2 then ext4 partition to install Android 11
Was rebooting randomly and used to go to bootloop after some time of use
Then tried to install sense based rom, failed, after multiple formats and file system repairs I got to installed sense based rom and phone was working just ok.. took long time ,
Then again installed Android 11
Everything is fine till now, but I'm really not sure when will
I will try again install android 12 some time later if phone don't bootloop now
fthjkmkffgd said:
sim cards not recognized on my dual sim device also stuck at htc logo issues. I have uploaded radio.txt and baseband version files. Here is radio.txt link: https://drive.google.com/file/d/1OV7L6dtsJsS3tcBltlWFcBc7mk4dCGno/view?usp=sharing
can you fix it?
Click to expand...
Click to collapse
Tarkzim, are my feedbacks good for you and are you working on them? I can provide you any information about my device to have a fully working rom