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
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.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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, we will laugh at you, all, at the same time.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATIONS
We'll not support users and answer questions from users which:
- are running a custom kernel
- have flashed mods
- modified system files
- didn't follow our intructions word by word
- are unfriendly
Even if you tell us that your problem is not related to your custom kernel /mod / magic => WE DON'T CARE!
Your mod => your problem!
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/
Download
https://github.com/cyanogenmod/android_device_huawei_g620_a2
https://github.com/cyanogenmod/android_kernel_huawei_msm8226
change log
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't mean Out-of-Respect!!!
XDA:DevDB Information
OFFICIAL CM-12.1 SnapTo (G620-A2), ROM for all devices (see above for details)
Contributors
Lloir, Lloir, Thömy
ROM OS Version: 5.1.x Lollipop
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-08-30
Last Updated 2015-08-30
ChangeLog
31/8/15 (Next Nightly)
Add in missing CVE -- 2015-1534
Remove 1080p from video record (device doesn't support it)
Add in Selinux policies to stop log spam
Add in correct lunfile path to enable SDcard mounting
Fixed Loudspeaker (Let me know how this is)
------------------------------------------------------------------------------------
30/8/15
Add in all the latest CVE patches too many to list (approx 20)
Fix LED
Known Issues
Loudspeaker doesn't work in calls currently
LED pulse length and speed still isn't working. Also noticed loudspeaker in calls is still broken in 8/30 nightly build.
USHAM2 said:
LED pulse length and speed still isn't working. Also noticed loudspeaker in calls is still broken in 8/30 nightly build.
Click to expand...
Click to collapse
Umm you sure? It's working perfectly fine here.....
and I already said loudspeaker is broken
Yes.. If you set the pulse length to long or very long, the LED should fade in out vs. continuous flashing when you receive a new notification. I did a clean flash to 8/30 build.
USHAM2 said:
Yes.. If you set the pulse length to long or very long, the LED should fade in out vs. continuous flashing when you receive a new notification. I did a clean flash to 8/30 build.
Click to expand...
Click to collapse
I just set it manually to long sent my self a text and it's pulsing green correctly.....
Uploading a video to show you what I have, to see if it's the same....
or if you don't have flash http://youtu.be/QLDaW86rGa0
Hmm. I guess an easier way to describe it... When I change the pulse length to very short then to very long, the pulse length stays the same. There's no noticeable difference.
USHAM2 said:
Hmm. I guess an easier way to describe it... When I change the pulse length to very short then to very long, the pulse length stays the same. There's no noticeable difference.
Click to expand...
Click to collapse
AHH now that's worded better, ok. I'll check it out properly once everything else is sorted.
Good afternoon all!
This phone is currently on sale and I'm debating whether to get it or now. it's around $100 USD, so not terribly expensive.
Lloir, will you continue support for this device past CM12.1? If you do, I think I'll buy it as a back up phone...as if I didn't have enough haha.
After installing via the provided insrtructions I show only 4gb instead of the 8gb that i should have in total storage capacity. Anyone else getting this or know how to fix it?
Thanks
edxmon said:
Good afternoon all!
This phone is currently on sale and I'm debating whether to get it or now. it's around $100 USD, so not terribly expensive.
Lloir, will you continue support for this device past CM12.1? If you do, I think I'll buy it as a back up phone...as if I didn't have enough haha.
Click to expand...
Click to collapse
need help.
hello... i´m a beginer.... i have tried to install a twrp recovery on my huawei g620-a2 but cellphone can´t start.... when i press start button just apear recovery system.... i can acces the bootloader too selectin reboot to bootloader.
i have tried to wipe data/factory reset and install this rom through "apply update option" (i don´t have other option), it finish succefully but when i reboot system.... it doen´t start. HELP ME... What can i do??
i´m trying to use roms and recoverys downloaded from url that apears in one picture of my attachments.
no have The key by my bootloader, Speak Spanish :v
Hello, I have a problem when getting the code to unlock my bootloader says I should write well the model of my phone or imei, someone could send me a screenshot of how I should correctly write the form ???:crying:
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?
Code:
/* 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.
*/
What is AOSP?
AOSP (Android Open Source Project) is Android just as Google publishes, without any other modifications or additions. More or less AOSP is the Pixel devices stock ROM without gapps and proprietary additions. Check out the screenshots to know more!
What's working?
Boots
RIL (Calls, SMS)
Mobile data
Bluetooth
WiFi/hotspot
Media (audio/video)
Camera
Camcorder
GPS
Fingerprint
NFC
Sensors
etc.
Bugs?
BT CALLS/voWiFi/voLTE
How to install?
Wipe system, data, dalvik's cache and cache Do not wipe vendor
TWRP:Install > select Image > select if they ask "system" select System and then the AOSP_A40......Image > install
Ofox: Tap on the Image > As system image
Reboot recovery
Flash Gapps
reboot system
Enjoy the goodness of Android 11.
Downloads
ROM: AOSP_VANILLA_STOCK_A40_R [Systemimage only]
Screenshots
Attachment
Sources
https://github.com/aosp-mirror
NOTE: For reporting any bugs, describe the issue properly and make sure to accompany it with a logcat. Without a logcat, bugs cannot and will not be fixed.
Don't forget to hit the thanks button to show love and support my work.
XDAevDB Information
AOSP 11.0, ROM for the Samsung Galaxy A40
Contributors
Kevios12
Source Code: Kernel Tree
ROM OS Version: 11.0.0
ROM Kernel: Linux 4.x
ROM Firmware Required: OneUI 2.0 or ALT+F4
Based On: AOSP
Version Information
Status: Stable
Created 2021-04-30
Last Updated xxxx-xx-xx
(Based On: AOSP) Roms unfortunately do not have the option to make sim2 passive while sim1 is active (or vice versa). Is there a solution to this?
I have installed the ROM with TWRP and my phone is now bricked, I cannot even get into TWRP anymore. Any idea what I could do now?
- Install order was: Unlocked bootloader, used Odin to install TWRP, flashed Multidisabler, reboot, then followed the instructions here
- Black screen followed the "reboot" button in TWRP
- I can reboot the phone by pressing all three buttons but this will only give me the Samsung warning I have to confirm and then black screen again
- this phone uses Exynos CPUs
- OneUI 3.1 was installed before. Is that the issue? I read "Firmware required" as "Minimum Firmware required"...
Edit: I can NOT reboot the phone while a USB cable is plugged in.
Yes OneUI 2.0 is required. OneUI3 FW is GAY! And you can go instand to twrp by pressing power + vol - then if restart hold power+vol+ if samsung logo come, release powerbutton and wait. Have u the A40 for sure? the rom is testet and works, nobody has a brick or whatever. Flash This image as system_image only no wipe vendor or everything btw. look in other treads for my custom vendor it will works.
kevios12 said:
Yes OneUI 2.0 is required. OneUI3 FW is GAY!
Click to expand...
Click to collapse
So I managed to flash OneUI 2.0 and then repeated the whole process and now your ROM boots. I can't connect to WIFI though (yes I made sure I used the correct password). It just says "connecting failed". Also, when I call someone, there is no call window. Is this ROM compatible with FlameGApps?
Also, yes, definitely the A40.
only u can Try gapps idk if flame works. did u use WPA2/3? combinied
My router uses WPA2/3 combined and Android does not give me an option.
I was now able to connect to another Wifi and tried to update my apps. It tells me I had not enough space. But I have over 50 GB free.
Edit: So, the Wifi problem depends on encryption. WPA+WPA2 works, WPA2+WPA3 does not work. I think that is a bug.
Also, I cannot get Play Store to install anything. It always complains about not enough space despite me having no apps installed and lots of free space on both internal and external memory. Cleaning cache did not help. This happens with both NikGapps and FlameGApps. FlameGApps works way better though.
Also explaine better, it should work maybe bug of gapps
I tried the rom , but it’s stuck on the android logo , any help?
Have u installed vendor? ... the custom one
kevios12 said:
Also explaine better, it should work maybe bug of gapps
Click to expand...
Click to collapse
Possible, but I do not know. Might also be partitioning. I did nothing but flash ROM and flash Gapps, then boot and run through the Gapps initial setup tool that automatically started (connect wifi etc). Then I tried to install any app from the Play Store. It always says I need to free up space before I can install an app. But I have lots of space, tens of GB.
hmm thats weird
It is weird indeed... also, are there known issues with phone calls with a Bluetooth headset? I couldn't use mine today, even though it was properly connected.
kevios12 said:
Have u installed vendor? ... the custom one
Click to expand...
Click to collapse
I did
CozmoGM said:
I did
Click to expand...
Click to collapse
Nevermind , i think i did something wrong , but i reflashed the rom and everything and now it works.
Konzertheld said:
It is weird indeed... also, are there known issues with phone calls with a Bluetooth headset? I couldn't use mine today, even though it was properly connected.
Click to expand...
Click to collapse
known bug, like voLTE/voWIFI/BT CALLS BUG/EXYNOS WONT WORK
kevios12 said:
known bug
Click to expand...
Click to collapse
So... please put that in your description above instead of stating "bugs: none". Other ROMs named the bug with Bluetooth etc and yours didn't, so I assumed it was not relevant. I would not have downloaded it if I knew.
Konzertheld said:
So... please put that in your description above instead of stating "bugs: none". Other ROMs named the bug with Bluetooth etc and yours didn't, so I assumed it was not relevant. I would not have downloaded it if I knew.
Click to expand...
Click to collapse
Well the problem is when you are developer & tester at the same time, because nobody feels like doing it, or you really do everything alone ... mistakes can happen!
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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.
Whats works:
Booting
Audio
Graphics
RIL (calls, sms, mobile data)
Wi-Fi, Wi-Fi Direct
Bluetooth
GPS, GLONASS
FM Radio
Sensors
Camera
Face Unlock
Video recording
Screen cast
Offline charging
SELinux (enforcing)
SafetyNet (with hidden Magisk or without root)
Tell me, if something does not work.
FAQ
Q: Does this ROM supports double tap to wake? A: No. And will not in future.
Q: Cannot add widgets to home screen. Widgets is not supported? A: Widgets is not supported in builtin launcher. Download any third-party home app (like Nova Launcher) and enjoy!
Q: Why split screen mode is not available? How to enable? A: Due to Android Go limitations, all forms of multiwindowing is not available on this edition of Android.
Q: When my app "foo" asks permission to access to notifications or to run on top of other apps, I see "This feature is disabled"... A: This is limitations of Android Go to save memory.
Q: Cannot use my sdcard as primary storage! A: This feature is unstable and excluded from ROM.
Q: Flashed this ROM but phone don't booting! A1: Boot to recovery and wipe /data, then reboot. A2: If your /data is formatted to f2fs, format it to ext4 and boot your phone.
Q: What is "Gapps for Android Go"? A: This is Gapps set, extracted as-is from Nokia 1 Plus Android 11 Go firmware and packaged for Lenovo A6000. Nothing removed, just fixed some permissions and added Google Camera Go.
Installation
Flash latest recovery (if needed), based on TWRP >= 3.2
Reboot to recovery
Wipe /cache and /data. If your /data is formatted in f2fs, format it in ext4, otherwise OS will not boot.
Flash the rom
Flash Gapps (Gapps for Android Go or OpenGapps ARM/Android 11/pico or nano)
Flash Magisk (also if needed)
Reboot to ROM
Spoiler: Latest changes
Build 05.09:
August security patch level
ROM is signed with release-keys
Build variant now is user, not userdebug
Updates from Lineage OS team
Clipboard access notification
USB fast charging toggler
Some OEM Android Go tweaks (from Nokia, ZTE)
New default wallpaper
Stricten background limits: 2 apps for 1/8 and 4 for 2/16
Recents is limited to 4 apps
Reworked WiFi and Tethering configuration overlays
Added overlays for Gboard, MessagesGo
Disabled caching in Trebuchet (launcher is fast enough to allow us to save some amount of memory)
zRam switched to Zstandart compression algorithm
Implemented clean page protection to reduce lags under memory pressure
Disabled rounded corners in UI
SEPolicy fixes
Misc...
NOTE: Strongly not recommended "dirty" updating. If you want to do this anyway, flash migration script before flashing the ROM!
Migration script: https://drive.google.com/file/d/15hB63RkyRpCljho9jyFTHoYWvCl4cDWe/view?usp=drivesdk
Download ROM: https://drive.google.com/file/d/1vUHuS18vDowwCSIWl8Dl4xxRHR4EHir0/view?usp=drivesdk
Gapps: Gapps for Android Go(updated!) or OpenGapps (ARM, pico or nano)
Credits to:
twain55
Moto-M8916 guys
Teo Flo
dev_harsh1998
SkepticOne
Nitrogradient
IvanHephaestus
Our Telegram discussion group: Lenovo A6000/Plus Community Discussions
Contributors
acroreiser
dev_harsh1998
Source code
Device tree: https://github.com/acroreiser/android_device_lenovo_a6000
Kernel tree: https://github.com/acroreiser/android_kernel_lenovo_a6000
Vendor tree: https://github.com/acroreiser/android_vendor_lenovo_a6000
ROM OS Version: Android 11 Go
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Hex Firmware Patch, TWRP >= 3.2
Based On: LineageOS
Version Information
Status: Stable
Created 2021-05-12
Last Updated 2021-09-13
Finally android 11 for a6000 thank you
Wow, I thought the previous version (17.1) is the last one for this device.
I am really happy I was wrong!
Thank you so much for your work acroreiser and dev_harsh1998. Also thanks to everyone who is credited!
First of all thanks to all the Devs who have kept this device still alive by providing it with those up to date roms...
Well I am using this rom for last 3 days i must say its super smooth apps are opening blazing fast, all major functions are working properly and it can be used as a daily driver for sure...
Now I encounter one bug so far its in Camera Go app the thing is when i change the storage location to SD card and start video recording than it suddenly freezes after some seconds by saying "Something went wrong " than i need to restart the app for using it again, by the way when i change the storage location back to internal than video recording is working fine so its really not bothering me that much....
There is one more thing well its not a bug its just my observation with this rom that during charging its heat up more than expected even when its charging at 90% to 100% slot which i never experience with any other roms.
All in all still its worth a shot everything's working fine, thanks to the devs again...
[email protected] said:
First of all thanks to all the Devs who have kept this device still alive by providing it with those up to date roms...
Well I am using this rom for last 3 days i must say its super smooth apps are opening blazing fast, all major functions are working properly and it can be used as a daily driver for sure...
Now I encounter one bug so far its in Camera Go app the thing is when i change the storage location to SD card and start video recording than it suddenly freezes after some seconds by saying "Something went wrong " than i need to restart the app for using it again, by the way when i change the storage location back to internal than video recording is working fine so its really not bothering me that much....
There is one more thing well its not a bug its just my observation with this rom that during charging its heat up more than expected even when its charging at 90% to 100% slot which i never experience with any other roms.
All in all still its worth a shot everything's working fine, thanks to the devs again...
Click to expand...
Click to collapse
The problem is in the application itself. in the firmware the application is of the old version and there should be no problems with the video. But it is automatically updated to the latest version in the Playmarket and there is a problem. Remove the app update and it will work as expected.
Teo Flo said:
The problem is in the application itself. in the firmware the application is of the old version and there should be no problems with the video. But it is automatically updated to the latest version in the Playmarket and there is a problem. Remove the app update and it will work as expected.
Click to expand...
Click to collapse
Thanks for the info, I will try that for sure...
Hey devs,
Thanks for this brand new ROM! I use this phone as a daily driver and wanted your advice on this version or the 17.1 version. Which one is likely to be maintained in the future? I understand that 17.1 is stable but will it still get more updates or security patches or should I go ahead with this 18.1 version, please?
Thank you for your help and also for keeping this phone alive in 2021.
Cheers,
S
santoshwins said:
Which one is likely to be maintained in the future?
Click to expand...
Click to collapse
Currently Lineage OS 18.1 is maintained.
Both 17.1 and 18.1 is based on my Go device tree (forked from @dev_harsh1998 lineage-16.0 tree) but lineage-17.1 branch is not maintained since february 2021.
I don't know is @twain55 can maintain 17.1 builds for a long time (better ask him).
Lineage OS 18.1 is pretty stable for daily usage by user reports and my experience with a6010 (I don't have a6000 and primarily maintaining a6010 with merging stable changes to a6000 tree).
Can a dirty flash be done from 17.1 ?
Zack316 said:
Can a dirty flash be done from 17.1 ?
Click to expand...
Click to collapse
Of course no.
New build is up!
Changes:
June security patch level
Updates from Lineage OS team
Memory and performance optimizations for 1/8 devices
Forward-ported qcom memory optimizations (frameworks/base)
Updated Binder driver (kernel)
Implemented automatic background apps memory reclaim (kernel)
Restored Qualcomm VP8 and HEVC codecs
Updated Bluetooth HAL from Nokia 1.3
Updated some media blobs
Some kernel tweaks from other low ram devices (Redmi Go, Nokia 1.3)
Workaround for broken video recording in recent versions of Google Camera Go
Recent apps screen is limited to 5 apps to save memory
Killed multiuser support - Go devices should not have this. Also this feature is pointless in our ancient phones...
Download: https://drive.google.com/file/d/1IqRTbY9CYH9Je3bmqaavjQHnn-763bx5/view?usp=drivesdk
Wow, thank you so much for the android 11 version. It is minimalistic and smooth. Loved the rom. Also thank you devs for keeping this device alive.
Needs Undervolting.
Even the standby drain is around 600ma.
Also I've bought a new battery for this, even that cannot survive more than an hour of SOT.
Please optimised the kernel or just undervolt it a bit.
Also only one of the back speaker is working,
Hi , Dear
Thank you for your your creativity
For Lenovo A6000 1G Ram & 8Gb Rom
Which version is the best 17.1 or 18.1 ??
Can i flash Twrp 3.2 on kitkat or must to be on Lolipop ??
Cheers ^_^
so this rom i cannot use my sd card right? that's super bad for me!
-ARiCK- said:
so this rom i cannot use my sd card right? that's super bad for me!
Click to expand...
Click to collapse
There is no problem with the firmware for using the SD card
I keep getting the "This build is signed with public key" error notification every time at startup.
New build us up!
Quick changelog:
August security patch level
ROM is signed with release-keys
Build variant now is user, not userdebug
Updates from Lineage OS team
Clipboard access notification
USB fast charging toggler
Some OEM Android Go tweaks (from Nokia, ZTE)
New default wallpaper
Stricten background limits: 2 apps for 1/8 and 4 for 2/16
Recents is limited to 4 apps
Reworked WiFi and Tethering configuration overlays
Added overlays for Gboard, MessagesGo
Disabled caching in Trebuchet (launcher is fast enough to allow us to save some amount of memory)
zRam switched to Zstandart compression algorithm
Implemented clean page protection to reduce lags under memory pressure
Disabled rounded corners in UI
SEPolicy fixes
Misc...
Read notes in OP before installing!
Installed the latest build. Thank you. Great work . Everything is working very good. Battery life is extremely good. Got 7-8 hours full HD youtube playback on 4g. Go version is working very smoothly ( previously was using android 5.0 stock )
...
I also have another device 10or.E which has similar SoC SD430. Can you tell me step by step instructions. Kernel source is available. ( I read about building but did not clearly understand various terms like vendor etc... Tried to create initial .mk files for the board but errors at luch command itself )