[ROM][11.0][UNOFFICIAL][cancro] LineageOS 18.1 [STABLE]

[ROM][11.0][UNOFFICIAL][cancro] LineageOS 18.1 [STABLE] - Mi 3 Android Development

{
"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 11 (R), 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
Bluetooth
Camera / Camcorder
RIL (CALL/DATA/SMS)
FM Radio
GPS
Hardware Encryption
IR Blaster (Mi 4)
WiFi
WiFi Hotspot
USB (ADB/MTP/PTP)
Audio Playback
Video Playback
Sensors
Touch
LED
NFC (Mi 3)
SELinux is Enforcing
What's not working:
You tell me.
Installation instructions
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe system / data / cache partitions
Flash ROM.
Optional: Install the Google Apps addon package.
Optional: Install Magisk for Root.
Supported models:
cancro (Mi3 / Mi4)
Downloads
Recovery : Official TWRP
Gapps : MindTheGapps Arm 11.0
Firmware : Download
Rom :
DOWNLOAD
Sources
Device/Kernel/Vendor Tree: Sources
Donate
DONATE To Me
Big Thanks
LineageOS Team.
xiaoMi-classic-dev team
Contributors
tarkzim
Source Code: https://github.com/LineageOS

Changelogs
2021/10/07
Updated to Android 11.0.0_r46 with October security patches.
Upstream updates and fixes.
2021/09/14
Fixed warning messages on boot of previous build.
2021/09/13
Updated to Android 11.0.0_r43 with September security patches.
Upstream updates and fixes.
2021/08/08
Updated to Android 11.0.0_r40 with August security patches.
Upstream updates and fixes.
Fixed WiFi hotspot with password connection issues.
2021/07/13
Updated to Android 11.0.0_r39 with July security patches.
Upstream updates and fixes.
2021/06/15
Updated to Android 11.0.0_r38 with June security patches.
Upstream updates and fixes.
2021/05/08
Updated to Android 11.0.0_r37 with May security patches.
Upstream updates and fixes.
Fixed sensors related SELinux policies, it should be working for all users.
Fixed offline charging and bring back MIUI charging animations.
2021/04/24
Fixed more app crashing issues.
Fixed CPU information bugs on 3rd-party apps.
Built-in terminal is buggy for some device, try other terminal apps on Play Store like "ConnectBot".
2021/04/21
Fixed Hardware Encryption.
Updated build fingerprint to match latest MIUI Global Stable.
2021/04/16
Bring back missing button brightness settings.
Resolved some SELinux denials that causing some bootloop issues.
Fixed AudioFX and audio effects related issues.
2021/04/15
Fixed crash/boot issues of previous build.
First boot after clean flash might be stuck, simply reboot manually will solve it.
Disable DT2W feature, which preventing screen from going sleep while calling or locked.
2021/04/14
SELinux is now enforcing.
Please let me know if something is broken after this build, like IR on Mi 4 since i can't test it on Mi 3.
Uprev Health HAL to 2.1.
2021/04/11
Updated to Android 11.0.0_r34 with April security patches.
Upstream updates and fixes.
2021/03/07
Updated to Android 11.0.0_r32 with March security patches.
Upstream updates and fixes.
Minor updates.
2021/02/10
Fixed boot issues on Mi 4.
Fixed IR Blaster on Mi 4.
2021/02/09
Updated to Android 11.0.0_r29 with February security patches.
Upstream updates and fixes.
Minor updates.
2021/01/13
Updated to Android 11.0.0_r27 with January security patches.
Updated to LineageOS 18.1.
Upstream updates and fixes.
LineageOS features updates.
Bring back Snap camera.
Fixed lockscreen settings.
Minor updates.
2020/11/19
Added DT2W.
(Built-in settings not working, DT2W enabled by default, use 3rd-party kernel manager to manage it)
2020/11/16
Initial release of LineageOS 18 for Mi3/Mi4.

Screenshots
Screenshots

Thanks! @tarkzim Bro!
Sent from my Redmi K30 Pro using Tapatalk

This is unbelievable, this device gets A11 all the way up from A4. This is history. Thanks @tarkzim bro. There are some devices you want to keep because, it has a long list of memories with it. I'm going to flash it.
I also request you to consider a double tap to wake and a reboot/recovery/power Quick tile for this device as power button is near eol. The earlier los17.1 dev did integrate these features , unfortunately his device got Bricked.

tarkzim said:
Screenshots
Click to expand...
Click to collapse
You can upload a backup file.

From this ROM. Booted fine

new build released
Added DT2W.
(Built-in settings not working, DT2W enabled by default, use 3rd-party kernel manager to manage it)

tarkzim said:
Added DT2W.
(Built-in settings not working, DT2W enabled by default, use 3rd-party kernel manager to manage it)
Click to expand...
Click to collapse
Can you please share kernel so that I can flash it. Kindly consider a power quick tile.

adityadeva said:
Can you please share kernel so that I can flash it. Kindly consider a power quick tile.
Click to expand...
Click to collapse
LOS team are working on advanced reboot menu, let's wait for them.
and please download the latest rom zip to make sure everything is fine.

tarkzim said:
LOS team are working on advanced reboot menu, let's wait for them.
and please download the latest rom zip to make sure everything is fine.
Click to expand...
Click to collapse
Thanks for that very essential advanced reboot hope. Meanwhile, I checked CTS profile. I don't know if there's a fix for that, but if there's one then NFC of this device coupled with Google pay in India will have a contactless, payment system in India.

Even this menu from the accessibility like icon near the navigation button in paranoid android in my poco f1 is a nice feature to save hardware buttons. I don't know the name thought.

adityadeva said:
Thanks for that very essential advanced reboot hope. Meanwhile, I checked CTS profile. I don't know if there's a fix for that, but if there's one then NFC of this device coupled with Google pay in India will have a contactless, payment system in India.
Click to expand...
Click to collapse
Install Magisk and enable Magisk Hide, Install "MagiskHide Props Config" module then reboot.
You can bypass the safetynet now.

Those hardware buttons (home, back, menu) lights are not on.

tarkzim said:
bypass the safetynet now.
Click to expand...
Click to collapse
Installed the much awaited Dt2w version and working fine. Dirty flashing resulted in rebooting back to recovery. I had to wipe both system and data to get the rom running. System partition was formatted to f2fs and is running fine.
With the mentioned changes, safety net has passed, but I didn't want to root the device in first instance. Hope that with advanced reboot on cards and safetynet and other issues sorted out in future builds, rooting could be avoided.
starfall88 said:
Those hardware buttons (home, back, menu) lights are not on.
Click to expand...
Click to collapse
Never knew that there was back light for these buttons
---------- Post added at 07:45 PM ---------- Previous post was at 07:44 PM ----------
tarkzim said:
bypass the safetynet now.
Click to expand...
Click to collapse
Installed the much awaited Dt2w version and working fine. Dirty flashing resulted in rebooting back to recovery. I had to wipe both system and data to get the rom running. System partition was formatted to f2fs and is running fine.
With the mentioned changes, safety net has passed, but I didn't want to root the device in first instance. Hope that with advanced reboot on cards and safetynet and other issues sorted out in future builds, rooting could be avoided.
starfall88 said:
Those hardware buttons (home, back, menu) lights are not on.
Click to expand...
Click to collapse
Never knew that there was back light for these buttons

How to install TWRP recovery?
I have a recently bought Xiaomi Mi 3W at home with stock everything. No modification was done after buying. How can I install a custom recovery (like TWRP) on it? From where should I start the process?
Can anyone please help?
It says,
Android version: 6.0.1 MMB29M
Android security patch level: 2017-06-01
MIUI version: MIUI 9 Global 8.3.1 | Beta
Kernel version: 3.4.0-gf4b741d-00690-gc8911e2

-You need adb and fastboot (installed correctly on your PC. Like minimal adb and fastboot app)
-You need turn on Developer options on your phone. And also turn on USB debugging on.
-ok. Then you need a DOS-box (command prompt) on your pc, in adb and fastboot folder
-then type on DOS-box "adb devices" if pc see your phone, then you will see a new message on your phone. Accept it.
-then type "adb reboot bootloader" and your phone will rebooting to fastboot mode
-then type "fastboot devices" if your pc see correctly your phone, you will see your phone in DOS-box. for example:
"fastboot devices 65eft4e2"
-the type "fastboot reboot" and your phone will reboot to normal mode
This is first lession. If you made this steps, write, and I will give you next steps.
Sent from my Redmi K20 Pro using Tapatalk

Battery backup at 4% - latest (dt2w) build. The battery is the original 6 years old one though. Taking a screenshot is cumbersome for me, I'm too much used to 3 finger swipe. Perhaps this build is intended for gaining a official status so don't know whether 3 finger swipe gesture will be incorporated by @tarkzim bro.

Can't boot on Xiaomi Mi 4W (cancro)
It shows boot animation then goes straight to TWRP on my Mi 4W. I have done the installation steps properly (wiped system, data, cache).
This also happened when I installed Android 10 last time. But I fixed it somehow I don't remember. Please reply if you have the same issue and know how to deal with it.

SimonVN said:
I have done the installation steps properly (wiped system, data, cache).
Click to expand...
Click to collapse
I faced the issue till I wiped data. Since you've done that, only thing left is "format data" which will ask for a Yes confirmation and your internal storage will be wiped out. You might need to flash the room from a external USB flash drive. So before that option check out whether your USB port is detecting the flash drive in recovery.
@tarkzim - I observed that once my ? battery had drained out fully and the phone got switched off all by itself, I put the phone on charging. There was no charging animation. It was stuck on mi logo, but it charged to 98%. By this time the phone was quite hot. Even after plugging it out, it continued to be stuck in mi logo. I had to hard press the (almost defective power button) for quite some time to get it booted. It's working fine now.

Related

[Q&A] [ROM][N7-2012][5.1 r3][LMY47I] Chroma – 04/05/2015 | Layers

Q&A for [ROM][N7-2012][5.1 r3][LMY47I] Chroma – 04/05/2015 | Layers
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][N7-2012][5.1 r3][LMY47I] Chroma – 04/05/2015 | Layers. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Chroma Nexus 7 3g tilapia can't install
Hey, I can't post anywhere else because of post count but I hope zephiK sees it here. The last zip for Nexus 7 3G of Chroma is not possible to install because it has the grouper binaries. Please could you update it to be able to install it?
(The exact error that console gives upon install is: Error executing updater binary in zip chroma_tilapia-ota-2015-04-05.zip. This package is for device: grouper; this device is tilapia)
(no, i have not downloaded the wrong zip, just in case.)
EDIT: I've seen the one maintaining Nexus 7 2012 builds is @sykopompos . Maybe no one has reported it yet. The builds you are building for tilapia don't work because recovery thinks they're for grouper. Could you update fix this error? I can't even install it...
zephiK said:
{
"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"
}
Chroma is a lightweight AOSP ROM focused on battery, performance and stability.
The philosophy of Chroma is to stay relatively close to Google's stock Lollipop with the additions of essential features that should have been included with stock Lollipop.
Features:
Layers Support
Status Bar Customization:
Battery Style (Icon Portrait/Landscape, Circle, Text, Hide) and Battery Percentage
Clock & Date (Show/Hide, Color, Alignment, AM/PM, Show/Hide Date, Date Style, Date Format)
Brightness Control (long press status bar to change brightness)
Double-tap status bar to turn device screen off
Quick pull-down on left/right side to pull down tiles
Long press tiles actions
Pressing on clock or date on status bar opens up Clock, Calendar
Show/hide notification count on status bar
Tile customizations (LTE, Screenshot, Sync, etc tiles)
Enlarge 1st row, show 4 tiles per row, show/hide brightness slider
Heads up notifications
Network traffic indicator
Navigation bar customization
Rearrange navigation bar to your likings
Navigation bar height (48/44/40/36/32/28/24/20/0dp)
Navigation button tint
Show/hide arrow keys while typing
Kill app back button
Navigation ring customizations
Clear all recents button (enable/disable) and location (top left, top right, top center, bottom left, bottom right, bottom center)
Clear all task (dismiss all task or ignore the foreground task)
Lock screen customization
Power menu customization (power off, reboot, screenshot, airplane mode)
Advanced Reboot (reboot/soft reboot/recovery/bootloader)
Volume rocker customization:
Wake device with volume keys when screen off
Long press volume up/down keys to skip track when screen off
Volume key adjustment sound (enable/disable)
Other:
A large number of optimizations and memory leak fixes
Ambient display controls
Animated expandable volume panel
Long press recents to swap back to previous app
AOSP Gallery2 with material design
Prevent accidental wake (proximity sensor before waking screen)
... and more (see changelog)
Special thanks to:
Donators: See Settings > Chroma > About Chroma in the ROM
Note: There are some users who've donated as a guest and doesn't have a username. I'd include you but not sure if you wanted me to put your name or not so let me know.
franciscofranco for the kernel
sykopompos for bringing it to non-Nexus 6 devices
vomer for the Chroma logo
boysetsfire for the wallpapers and boot animation
BitSyko team, SimpleAOSP, CyanogenMod
Instructions
Pre-requisites: unlocked bootloader | latest TWRP grouper (Nexus 7 2012 WiFi) recovery | latest TWRP tilapia (Nexus 7 2012 3G) recovery
1. Download ROM, Gapps, SuperSU and put it on the phone's internal storage.
2. Boot into TWRP recovery.
3. Coming from a different ROM? Perform a factory reset using TWRP. If you're upgrading from Chroma ROM, proceed to dirty flash (nandroid backup before flashing is a good idea)
4. Clean Installation: Flash ROM, Kernel (Optional), GApps, SuperSU
....Dirty Flash: Flash ROM, Kernel (Optional)
5. Reboot and enjoy.
Enjoy what I do? Want to show your appreciation? You can donate HERE.
Changelog: HERE
Download:
Grouper (2012 WiFi): Chroma 2015-04-05 | GApps | SuperSU
Tilapia (2012 3G): Chroma 2015-04-05
It should be noted that the zips posted are blind test builds, @sykopompos currently maintains it for N7 2012.
Do a nandroid before flashing.
Chroma does not use/support F2FS
You must flash SuperSU otherwise you will not have root access.
Want to be notified when a new update comes out? Subscribe to Chroma on Pushbullet and you’ll receive a push notification when a update is out.
To Moderators: Off-topic is allowed in this thread, please do not delete or modify posts unless user(s) are starting to become uncivil with one another.
XDA:DevDB Information
Chroma, ROM for the Nexus 7
Contributors
zephiK
ROM OS Version: 5.1.x Lollipop
Version Information
Status: Stable
Created 2015-04-06
Last Updated 2015-04-06
Click to expand...
Click to collapse

GPS not present
GPS Status app says "GPS not present on this device".
As reported by other user, Google Maps does not show location either.

A million thank you's to everyone who has worked so hard on this! I'm only a few hours in but I am really enjoying it, when I thought, "welp might as well try a couple more lollipop roms before going back to jellybean" I didn't expect this! In fact it kept me up all night (in a good way). Camera is working great with CameraMX but still having GPS issues, even after doing the selinux permissive via terminal: "su", then "setenforce 0." I mostly use this for games and browsing at home, so neither of these are a deal breaker, but after reading through the ROM thread I figured I should try
I know grouper is a small user base, but it's so nice to have your lollipop and eat it too. Much appreciation!
Now GPS works, not sure what changed, I just ran the same "setenforce 0" from a root terminal and it popped right up.

F2FS Support???
I know the OP states that the rom doesn't support F2FS but some people are apparently using it with f2fs by flashing a f2fs capable kernel. if this is true:
1. Which kernel is built into the ROM
2. What format will the ROM use upon installion? ext4 or just leaves the partition as it is (I already have f2fs which is why I'm asking)
3. Can I use the latest M-Kernel on this if it doesn't already have this kernel
Thank you in advance

wax911 said:
I know the OP states that the rom doesn't support F2FS but some people are apparently using it with f2fs by flashing a f2fs capable kernel. if this is true:
1. Which kernel is built into the ROM
2. What format will the ROM use upon installion? ext4 or just leaves the partition as it is (I already have f2fs which is why I'm asking)
3. Can I use the latest M-Kernel on this if it doesn't already have this kernel
Thank you in advance
Click to expand...
Click to collapse
1. I believe it is still the stock kernel for this device. The person working on this device hasn't been able to integrate Franco with it yet.
2. System *MUST* be ext4. I tried to format cache to f2fs but the kernel just reformatted it back to ext4.
3. You'll have to read the parent thread, but I believe the person doing the N7 development said that was possible using the "anykernel" framework, or pretty much make sure you don't replace the ramdisk or boot.img shipped with the ROM. But again, read through the parent thread for definitive answers.

Thanks dude, exactly the answer I was looking for!

Does anyone having success booting another kernel than franco r82? i dont want to use franco kernel but anything else turns my n7 in a bootloop state , im running the lastest 22/4 built, f2fs cache only

Juste Dan said:
Does anyone having success booting another kernel than franco r82? i dont want to use franco kernel but anything else turns my n7 in a bootloop state , im running the lastest 22/4 built, f2fs cache only
Click to expand...
Click to collapse
I'm using Franco, but I know some people have had success with Bricked in the parent thread. It is definitely a picky rom in terms that the kernel can't replace the boot.img or ramdisk, what kernel are you trying to use, and are you sure this isn't the case?

I had bricked on 5.1 and it felt as fast as my 2013 version, now it feels more like 5.0.2, i think i will simply roll back to 5.1 :good:

Location services are not working for me. No blue dot in google maps, pressing the current location button just prompts allowing gps access over and over.

Set up wizard has stopped
I factory reset with the latest TWRP, installed 4/22/15 Grouper ROM, installed Banks dynamic gapps 5-3-15 beta2, and installed SuperSU v2.46. After boot, I receive several error messages Unfortunately, Set up wizard has stopped. The only thing I can do is press OK. Then there is a black screen with the time and battery indicator on top and the navigation keys on the bottom. Thinking it was a gapps issue, I tried flashing the gapps again but it's still the same.
What should I try next?
Thank you!

Hi, the ROM is really soft , but i have one problem, i lock the screen and the tablet off alone, i run miui rigth now, i have the same problem with cm12, i install full clean ( NRT - stock) and nothing.. Help please ???

Stuck at Testing Connection
If I install Gapps, it gets stuck verifying internet connection. If I flash the rom first, it will boot fine, but no apps. Which Gapps version will help me?

setup
When I flash this it installs and boots to the setup but won't go any further. It keeps saying something like setup has unexpectedly closed, I have tried to install several times but it won't go past that point. What am I doing wrong.

The rom works great except when I change the DPI, I get stuck in a boot loop. I'd really love to be able to use this rom and change the dpi.

I encrypted my phone to test it out. I've decided I don't need it and want to undo it. A google search shows that doing a factory reset should undo this, but with this ROM that doesn't seem to be the case. Anyone know how I might un-encrypt the drive?

Hi, first to all sorry for my english.
I have a question, I revived my N7 2012 and work very fast and have a great performance with this rom. Before I was using the official rom. I flash the rom and gaps, but I still have the google kernel. How I can change that? I follow this post, I need download another kernel? how will be the correct order to flash again? Checking the filse system is ext4, is better use f2fs.
Thanks in advance.
Regards.

Flashing it right now, right here ^_^
---------- Post added at 05:58 PM ---------- Previous post was at 05:43 PM ----------
GtrCraft said:
I was a little bored so I made this: url](Chroma for Tilapia)[/B]
I cannot test it so pls someone tell me if it works
Click to expand...
Click to collapse
Nope...
still says: This package is for device: grouper; this device is tilapia
*sad*

Hi,
I installed the this ROM but it seems to be stuck in a bootloop on first startup.
Any help?

[VK810] [altev] [CM13] Invisiblek's Unofficial - Update from Invisiblek post #28

Update from Invisiblek post #28
This thread is only for until/if @invisiblek opens his own thread. If he does, I'll link to his thread and close this one, or transfer the OP to him if he wants.
or How I Learned to Stop Worrying and Love my Tablet Again.
{
"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"
}
Dr. Strangelove or: How I Learned to Stop Worrying and Love the Bomb (1964)
Thanks to:
@invisiblek for building and permission to link to his CM13 builds folder, and all his work to get this to the point it is right now, including getting Mobile Data to work
@Hnk1 for making me aware that the builds had started
Don't expect support from anyone in this thread. Help might come but it's likely that if you're experiencing a problem that @invisiblek is already aware of it, or it's a CyanogenMod issue that all ROMs will have. In the meantime, please feel free to communicate with other CM13 for VK810 users here to confirm/deny the existence of any issues you might have, or discuss any workarounds when possible.
Please mention what build date of CM13 you're on when you're discussing issues.
Installation Notes:
It's smooth as butter.
Flashing this definitely doesn't work with a newer bootloader. I recommend flashing this from TWRP v2.8.7.0 after a fresh flash of the 11A KDZ and downgrading the bootloader in order to install the initial Loki'd version of TWRP v2.7.0.1 and then upgrading to 2.8.7.0, or if necessary, first the 22B TOT and then the 11A KDZ after. All necessary instructions are in my [VK810.4G] [altev] most reliable way to root and install a custom recovery thread. I actually manually downgraded the aboot (bootloader) even though I was on 11A and my instructions at that link specify that downgrading the bootloader further wasn't necessary, so I haven't tested straight from 11A's bootloader.
When I had tried @invisiblek's TWRP v3.0 July 19, 2016 build for the VK810 (the current build that's available), it accessed internal storage just fine - my MicroSD card is formatted ExFAT so that might be the trouble - I haven't tested USB OTG on this build, nor backing up or restoring. This build of TWRP flashed the ROM okay, and looked like it flashed OpenGApps Pico okay, but no matter how many times I tried or even trying to flash OpenGApps Nano, when the ROM was booted the Play Store still wasn't there. Reverted to a known good version of 2.8.7.0, wiped all and fresh flashed ROM and OpenGApps Pico and all's good so far.
I use Slim Zero GApps for Marshmallow (6.x) with this, available at [GAPPS][6.0/5.1/5.0][arm/arm64] Official Slim GApps. @invisiblek uses Open GApps (Pico Package). This tablet uses an ARM processor and CM13 is Android 6.0x.
OTA's work and point to @invisiblek 's newer builds when they're available. If you take OTAs and you had system Xposed installed, you'll have to flash Xposed again.
[*]Root can be enabled without SuperSU by first enabling the "Developer options' in Settings. Do so by going to Settings / About tablet / scroll down and touch "Build number" about 10 times in a row, then you can see "Developer options" in the main Settings menu immediately before the About menu. At the bottom of the first screen of the "Developer options", under "Root access", enable either "Apps only" or "Apps and ADB", for most users' purpose. I believe "Android debugging" (two options down further from the "Root access" in "Developer options") was already enabled.
System Xposed build 86 (sdk23) for Arm processor, and Greenify including the latter's Xposed module appears to work okay. Trying G3TweaksBox (made for stock but might still provide some functionality under CyanogenMod) rotation tweaks doesn't appear to help the rotation issue I'm having. G3TweaksBox's Sound options like "Link Ringtone and Notifications volume", "Force media volume control" and "Auto expand volume panel" all appear to work. Other modules I've tested: Amplify, Battery Home Icon (% text at least for 100% is offset), DirectAPKInstall Module doesn't work (I think it didn't work on stock on this device, it works fine on my VS985 G3), Flat Style Bar Indicators, Marshmallow SD fix, Play Store Changelog, installed but haven't tested YouTube AdAway and YouTube Background Playback. I had attempted Systemless Xposed and it wouldn't flash from TWRP, but it's supposed to specifically require SuperSU v2.76, so I didn't necessarily expect it to work with CM's built-in root. Haven't tried SuperSU yet, but if you do, disable CM's built-in root first.
Do not ask about when anything will be fixed, nor requests for features/new builds etc, or when CM14 (Nougat) or CM26 (Zagnut) will be released.
What's broke (at least on cm-13.0-20160716-UNOFFICIAL-vk810.zip):
Camera
Brightness adjustment (I recommend Lux Auto Brightness or Lux lite by Vito Cassisi and it can be chosen to integrate with CF.Lumen by @Chainfire)
Occasional black screen when you try to wake up the tablet. It's necessary to hold the power button in for 10 seconds or so to force turn it on, then either continue to hold the power button or let go and press again to turn boot the tablet back up. @invisiblek hasn't had this issue on his own VK810 in a while so I need to provide some further testing and reporting once I experience the issue again. I haven't yet tried the GApps that @invisiblek uses just to rule that out although I doubt if that'll make a difference.
Rotation might not work - I haven't tested on the fully "stock" ROM and have a bunch of apps/tweaks installed now so will have to double-check on a fresh flash later. The best app workaround I've found is Rotation Control. This enables you to manually control rotation via icons in the pull down notifications. There's other apps to do the same thing but one of the other highly rated ones didn't work for Reverse Portrait, and the other one didn't have Reverse Portrait at all. At this time I have no idea if the tweaks I made in G3TweaksBox might've improved the "Rotation Control" app's behavior, or if any other settings I have going on might've one of the other apps I tested.
Downloads: [*]http://www.invisiblek.org/roms/cm-13.0/vk810/

Screenshots:
Keep in mind these screenshots are after my tweak apps:
Using Style part of Dark F Material theme:

My process of elimination steps trying to diagnose why I always get 1) sudden black screen and also 2) sudden soft reboots (starts immediately with CM boot animation) and 3) UI restarts.
8/2/2016 morning: wiped Cache, Dalvik/ART and Data flashed the 8/1 build and OpenGApps Pico 8/1 or 8/2 from TWRP v3.0 M5 July 19 build, then booted the ROM and noticed GApps hadn't installed even though it looked like it went through the motions. Repeated attempts to flash GApps both Pico and Bank from TWRP v3.0 had same results. Flashed TWRP v2.8.7.0 by Brian someone and flashed GApps and they installed fine.
Set my Google account up, changed a bunch of settings and I think I enabled CM's root, installed some stuff, was satisfied and then by mid-afternoon I opened my case and found it had black screened.
8/2/2016 evening: Put his TWRP v3.0 July 19 build back on, wiped Cache, Dalvik/ART and Data, flashed the 8/1 build (but not OpenGApps), then wiped internal storage, turned the tablet off, ejected my MicroSD card which is formatted ExFAT, and booted the ROM. I turned WiFi and Mobile Data off but otherwise didn't touch it at all.
8/3/2016 late morning, tablet still hasn't had issue so I put it in Airplane Mode, one of the things I almost have it set to when I'm not using Mobile Data.
8/4/2016 late morning, still no trouble. Connected to unsecured work WiFi, downloaded latest OpenGApps pico and latest stable SuperSU.zip v2.76. Rebooted to TWRP v3.0 M5, flashed SuperSU.zip and the log looked perfect but apparently the ROM won't boot. This TWRP 3.0 M5 build won't read my USB-OTG or a 16 GB FAT32 MicroSD card I put in. Using USB, the PC does access internal storage through MTP in TWRP v3.0 M5, so putting a copy of CM13 on internal storage to flash. Dirty flashed CM13 8/01 build and it's booting okay.
Enabled Developer options and CM's built in root for Apps only. Tomorrow I'll install @Chainfire 's FlashFire and try to use it to flash OpenGApps since when I used TWRP v3.0 M5 to flash OpenGApps, once booted to Android GApps weren't there and I'm trying to avoid going back to TWRP v2.8.7.0 for now.
[*]8/4/2016 mid-afternoon. Interesting but not conclusive observation. My last action late this morning was to enable CM's built in root for Apps only, and just now (four hours later?) I opened my case and found the tablet was having the black screen issue (requiring a power button long press to force off and turn back on). I just re-disabled CM's built-in root, I'm rebooting the tablet again after having changed that setting, and we'll see if it black screens again anytime by tomorrow. If not, I may enable root again and see if it black screen relatively quickly.

One more.

Updated OP with accurate information about @invisiblek 's latest build of TWRP v3.0 for the VK810 as of July 19th, 2016. Summary: seems to work, just possibly not with ExFAT for my MicroSD card, or not with a 128 GB card.
Edited update: This build of TWRP flashed the ROM okay, and looked like it flashed OpenGApps Pico okay, but no matter how many times I tried or even trying to flash OpenGApps Nano, when the ROM was booted the Play Store still wasn't there. Reverted to a known good version of 2.8.7.0, wiped all and fresh flashed ROM and OpenGApps Pico and all's good so far.
Ugh...still got a black screen. I'll try without installing any apps or having or root enabled.

Delete.

I am gonna try this weeked. Any idea which build is the most stable?
Sent from my unknown using XDA-Developers mobile app

lhrt said:
I am gonna try this weeked. Any idea which build is the most stable?
Click to expand...
Click to collapse
I think all the most recent builds are the same - he hasn't made any new commits to GitHub at least not as of yesterday. He tried getting the camera working, but it still doesn't for me, it FCs.
That said, be very careful and slow in setting it up and installing. I don't know why I always have trouble with CM builds on this tablet (sudden black screen requiring a long power button press to force off and back on, sometimes just suddenly it soft reboots - starts immediately with the CM boot logo, not a full reboot). I used the latest build and OpenGApps this time, I had a reasonably full gambit of my apps installed and set up, CM's built-in root enabled in Developer options, but I didn't have Xposed installed this last time and it still went black screen later yesterday.
So I went into full-process-of-elimination mode. I had all the files I needed on internal storage, but also on the MicroSD card, I installed his TWRP v3.0 M5 for the VK810, wiped all again including internal storage this time, and only flashed the ROM. Then I shut down the tablet from TWRP's reboot menu, ejected my MicroSD card which is formatted ExFAT and his TWRP doesn't like anyway, although it's always worked fine itself in both CM and in the stock ROM, and I've left it like that since last evening and it hasn't black screened.
Next I'll probably flash OpenGApps and then leave it sit for a day to see if it does anything. Oh yeah, when i tried flashing OpenGApps from his TWRP I don't think it worked right so I might have to either downgrade to someone else's TWRP v2.8.7.0 or try FlashFire to flash GApps.
I'll continue like this in patient stages so that I can notice when it starts black screening again. I haven't touched any settings in Android yet, not even enabled the built in root. I might flash SuperSU from TWRP instead this time though, once I get around to it.
Good luck! Let us know how it works for you!

Updated the third post with my process of elimination steps and progress. http://forum.xda-developers.com/showpost.php?p=67819877&postcount=3

Interesting but not conclusive observation - I'll add to the third post. My last action late this morning was to enable CM's built in root for Apps only, and just now (four hours later?) I opened my case and found the tablet was having the black screen issue (requiring a power button long press to force off and turn back on). I just re-disabled CM's built-in root, I'm rebooting the tablet again after having changed that setting, and we'll see if it black screens again anytime by tomorrow. If not, I may enable root again and see if it black screen relatively quickly.

So the CM (CyanogenMod) 13 is the same as Android 6.0 Marshmallow?
EDIT:
I just flashed the CM13 Unofficial zip for VK810 in TWRP v2.8.7.0 and my tablet is now stuck in bootloop. It shows the Android for a minute then goes to blank screen.
---------- Post added at 10:09 PM ---------- Previous post was at 09:54 PM ----------
roirraW "edor" ehT said:
Updated OP with accurate information about @invisiblek 's latest build of TWRP v3.0 for the VK810 as of July 19th, 2016. Summary: seems to work, just possibly not with ExFAT for my MicroSD card, or not with a 128 GB card.
Edited update: This build of TWRP flashed the ROM okay, and looked like it flashed OpenGApps Pico okay, but no matter how many times I tried or even trying to flash OpenGApps Nano, when the ROM was booted the Play Store still wasn't there. Reverted to a known good version of 2.8.7.0, wiped all and fresh flashed ROM and OpenGApps Pico and all's good so far.
Ugh...still got a black screen. I'll try without installing any apps or having or root enabled.
Click to expand...
Click to collapse
I got a black screen after I flashed this http://www.invisiblek.org/roms/cm-13.0/vk810/. Is there another solution for this?

kawhayang said:
So the CM (CyanogenMod) 13 is the same as Android 6.0 Marshmallow?
EDIT:
I just flashed the CM13 Unofficial zip for VK810 in TWRP v2.8.7.0 and my tablet is now stuck in bootloop. It shows the Android for a minute then goes to blank screen.
---------- Post added at 10:09 PM ---------- Previous post was at 09:54 PM ----------
I got a black screen after I flashed this http://www.invisiblek.org/roms/cm-13.0/vk810/. Is there another solution for this?
Click to expand...
Click to collapse
Yep.
Doubtfull, another user reported the same problem (in a different thread, unfortunately). You had wiped Cache, Dalvik/ART and Data, right?

roirraW "edor" ehT said:
Yep.
Doubtfull, another user reported the same problem (in a different thread, unfortunately). You had wiped Cache, Dalvik/ART and Data, right?
Click to expand...
Click to collapse
Whenever I wipe the data/cache from TWRP, it wipes the OS because it says afterwards there is no OS installed.
If I follow these instructions, do they also take me to Android 6.0 Marshmallow? http://forum.xda-developers.com/lg...t-install-t3283027/post64577888#post64577888

kawhayang said:
Whenever I wipe the data/cache from TWRP, it wipes the OS because it says afterwards there is no OS installed.
Click to expand...
Click to collapse
I don't know what's going wrong for you. Wiping Cache, Dalvik/ART and Data never wipes the OS on any device for me. You have to wipe those things before booting a new ROM, especially when going from stock LG ROMs to CyanogenMod/non-stock ROMs, or the ROM won't boot or work right.
If I follow these instructions, do they also take me to Android 6.0 Marshmallow? http://forum.xda-developers.com/lg...t-install-t3283027/post64577888#post64577888
Click to expand...
Click to collapse
No. This is the only Android 6.0 I've noticed for the VK810. My thread you referenced deals with stock LG ROMs, and there is no stock Marshmallow for the VK810, only Lollipop 5.0.2 which runs laggy, and is why I'm running 24A KitKat instead.

[/QUOTE] No. This is the only Android 6.0 I've noticed for the VK810. My thread you referenced deals with stock LG ROMs, and there is no stock Marshmallow for the VK810, only Lollipop 5.0.2 which runs laggy, and is why I'm running 24A KitKat instead.[/QUOTE]
This goes to show how different devices act differently. My tab was real laggy on kitkat, but on lollipop it's been pretty smooth. I'm counting on you for some marshmallow action! lol

ryanallaire said:
This goes to show how different devices act differently. My tab was real laggy on kitkat, but on lollipop it's been pretty smooth. I'm counting on you for some marshmallow action! lol
Click to expand...
Click to collapse
Absolutely! (different people's devices acting different with the same model). Of course, I've hardly been using my tablet at all and only have a couple dozen maximum apps installed, and I have severely debloated the stock stuff. Who knows. Make sure and gives thanks to @invisiblek, he's the one developing CM13 for the VK810 - I just created the thread. Since it's not mine is why I created it in the General section and since it's just a pretty much an announcement thread.

roirraW "edor" ehT said:
I don't know what's going wrong for you. Wiping Cache, Dalvik/ART and Data never wipes the OS on any device for me. You have to wipe those things before booting a new ROM, especially when going from stock LG ROMs to CyanogenMod/non-stock ROMs, or the ROM won't boot or work right.
No. This is the only Android 6.0 I've noticed for the VK810. My thread you referenced deals with stock LG ROMs, and there is no stock Marshmallow for the VK810, only Lollipop 5.0.2 which runs laggy, and is why I'm running 24A KitKat instead.
Click to expand...
Click to collapse
I wiped the Cache, Dalvik, and Data and flashed the CM13 Unofficial ROM. It takes me all the way to Starting Preparation/Optimization Completed and reboots and gives me a dark screen and doesn't get past the blue android and gets stuck in boot loop. I am thinking of just upgrading to Lollipop. http://forum.xda-developers.com/lg...10-4g-official-lollipop-5-0-2-35a08-t3113607

kawhayang said:
I wiped the Cache, Dalvik, and Data and flashed the CM13 Unofficial ROM. It takes me all the way to Starting Preparation/Optimization Completed and reboots and gives me a dark screen and doesn't get past the blue android and gets stuck in boot loop. I am thinking of just upgrading to Lollipop.
Click to expand...
Click to collapse
One or two other users had problems with the latest builds too. I had problems with builds from a couple of weeks back, as you can read in this thread, but not that problem. That's part of the trouble with CM, it takes a long time (and effort of the person doing the compiler, or others who submit commits to the device-specific source code) to iron out bugs. People have other troubles with CM13 on the LG G3, too.
I liked stock debloated Lollipop but it would just get so slow for me eventually - I used it for a year or so. I hope it works better for you.

roirraW "edor" ehT said:
One or two other users had problems with the latest builds too. I had problems with builds from a couple of weeks back, as you can read in this thread, but not that problem. That's part of the trouble with CM, it takes a long time (and effort of the person doing the compiler, or others who submit commits to the device-specific source code) to iron out bugs. People have other troubles with CM13 on the LG G3, too.
I liked stock debloated Lollipop but it would just get so slow for me eventually - I used it for a year or so. I hope it works better for you.
Click to expand...
Click to collapse
Is there any other way to get past this when flashing CM13? Sorry, I probably asked this before but I really want to be able to use this on my (VK810) device.

kawhayang said:
Is there any other way to get past this when flashing CM13? Sorry, I probably asked this before but I really want to be able to use this on my (VK810) device.
Click to expand...
Click to collapse
I've told you everything I know about it. I wish it worked better too, but I'm not in control of it, @invisiblek is most likely busy with lots of other things. The only other solution is for you to learn how to compile, debug and fix source code. I've never done any of those things.

[ROM][UNOFFICIAL] LineageOS 13.0 for Alcatel ONETOUCH IDOL 3 4.7

Status:
It still needs some polishing and cleaning up, and there are unresolved issues but nothing serious (check below). Based on user reports this is pretty usable. Battery and performance are both at least as good as stock, with the added benefit of having doze support, being less bloated, coming rooted etc.
Credits:
This wouldn't be possible without DeckerSU's post with an official MM rom. I've used his file to extract the binary stuff.
I've also cloned his device tree to build TWRP on omnirom since I was having a hard time building it on CM.
I started by cloning pivoq's device tree for CM12.1. So credit goes out to him too.
Those are just the things I've used directly but looking at other people's code also helped a ton to figure things out. So I guess credits goes also to the whole community/ecosystem.
Known Issues:
Smart lock isn't preserving settings across reboots. (If anyone is willing to test this and contact me, it can probably be fixed easily)
The bundled camera app (Snap) works well. Stock camera app works well as well (doesn't come with the ROM, maybe I'll provide a zip in the future). But some cam apps have issues.
Not Working / Enabled / Unknown:
Flip cover.
Drm?
Fastdormancy?
No NFC icon on statusbar. ** Won't fix ** - AOSP or CyanogenMod do not have such an icon. Some vendors add it. As such I don't think ROM should come with it by default. Either there's an exposed module for it that people can install, or a flashable zip can be made to add it. I think that's the better route rather than have the ROM come with it.
CNE - ** Won't fix ** - Disabled by choice. It's an anti-feature in my opinion.
Notes:
Doze: Officially doze requires a special motion sensor that our device does not have. Motion will not keep the device from dozing, or awake it. Also, doze by default takes a long time to kick in (about ~1h), and I would advise people to tweak those timings to their usage patterns with Doze Settings Editor (http://forum.xda-developers.com/android/apps-games/root-doze-settings-editor-android-t3235130), or some other app like Greenify / Nap time. Lastly doze is supposed to work with GCM, which isn't available on the ROM by default unless you install google apps or an adequate substitute.
XPosed: works with v87+.
SELinux: I've seen a lot of people setting selinux to permissive, often because of some xposed module. SELinux is an integral part of android's security. Things are already pretty bad with it, disabling it isn't recommended. While there will still be many security bugs, often selinux limits their scope or makes it so that multiple bugs will be required for successful explotation. No xposed module is worth that.
Download:
LineageOS 09/04/2017:
https://www.androidfilehost.com/?fid=745425885120723074
TWRP 3.1.0:
https://www.androidfilehost.com/?fid=817550096634753196
- The recovery has support for encryption and adopted storage (including mixed mode).
ROM Changelog:
** 09/04/2017 **
Code:
- April security patch level
- Kernel sync to 1.2.7-rb1.41
** 25/03/2017 **
Code:
- March security patch level
**13/03/2017**
Code:
- Move on to LineageOS
- Fix wifi tethering
- Fix OpenGapps issues
- February 01 security patch level
- Sync kernel to LA.BR.1.2.7_rb1.40
** 16/12/2016 **
Code:
- December 01 security patch level
** 09/12/2016 **
Code:
- Updated kernel for CVE-2016-5195 (November 06 security patch level now).
- Added ZEN IO Scheduler
- Tweaked cpu governor, 200Mhz+ clock (from 533).
- Added zram.
** 25/11/2016 **
Code:
- Fixed SIM regression for dual sim variants.
- Added F2FS support for data and cache (Beware recovery linked above wasn't updated)
- Tweaked minimum brightness setting
- Added 533Mhz as lowest frequency for cpu (from 800Mhz).
- Removed wifi dual band (device doesn't support 5Ghz).
- Compatible with microG/UnifiedNLP:
Permission for signature spoofing (don't give this to apps unless you know what you're doing).
Added location overlays for UnifiedNlp.
** 23/11/2016 **
Code:
- Fixed reported regressions. Unsure about the SIM one,hopefully it's fixed too.
** 21/11/2016 **
Code:
- Fixed modem battery drain
- Fixed FM radio (new app)
- Fixed camera (new app, Snap). As far as i've noticed everything's working under this app.
- Enabled Doze.
- Fixed operator name showing as numerical ID.
- Changed LTE label to 4G.
- November 5 security patch level.
** 09/11/2016 **
Code:
- Fixed wrong power accounting for bluetooth
- Updated wlan firmware blob
** 08/11/2016 **
Code:
- Fixed leds regression
- Fixed location battery drain
- FM radio kind of working:
(to hear sound you need to turn bluetooth on, you can turn it off again afterwards)
- Front camera isn't dark anymore but still crashes with HDR. Cam still has issues but is usable.
- Post processing daemon isn't crashing anymore, which was leading to some hiccups.
- Advanced reboot should be working for everyone now
- IRQ Balancing
- Added cne/dpm vendor libs. Haven't tested further so CNE might be working.
- Minor tweaks/fixes, some selinux stuff.
** 30/10/2016 **
Code:
- Correct variant should now be detected and multisim set up accordingly.
- Built without microG patch (which was incompatible with google apps)
** 27/10/2016 **
Code:
- Fixed camera. Had made a mistake while building previous rom.
(This is not a fix for the front camera darkness issue.)
Recovery Changelog:
**14/03/2017**
Code:
- Update to twrp 3.1.0
**21/01/2017**
Code:
- Update to twrp 3.0.3, fixes .img flashing.
- Removed superfluous mouse pointer.
- Updated kernel with current f2fs support.
Code:
I'm currently creating my first github account etc. As I find the time to clean up the commit history and set things up properly I'll update the post with links to the device tree and kernel sources.
I've decided to post now, perhaps prematurely, because I'm very limited on time I can spend on this (can't afford it). I'm also unsure if there's even many people interested. So the best way forward if there's interest is either other people joining in and carrying this further, or supporting development with some donations.
Donations:
So far got 9 donations.
$50 < Total donations < $100.
Thanks to anyone who's donated and has shown appreciation!.

reserved.

Cool nice to see devrlopment to the 4.7 idol, I'm still waiting for the official marshmallow update (europeu representativas on Twitter and Facebook keep saying its coming) but if that takes too long I might get to use this rom

wow, i never thought that we will ever get cm13! thank you for your hard work! please, don't give up!

Rom is Very good.

downloading it now, i'll have time to flash the rom tonight
does xposed work?
basic functions like phone, sms, 2g, wifi work without any problem?
what about battery?

jani0417 said:
downloading it now, i'll have time to flash the rom tonight
does xposed work?
basic functions like phone, sms, 2g, wifi work without any problem?
what about battery?
Click to expand...
Click to collapse
I noticed I made a mistake on this build and as such the camera is broken. I'm gonna make a new build in a couple hours.
Never tried xposed.
Basic functions are all working for me. At least for the 6039Y I think it should work but we'll find out if people leave feedback. My guess is that it's probably working, with the exception of maybe dual sim variants.
Wifi should be working. Qualcomm CNE isn't, and I'm unsure if I even want it as a feature, need to research on it.
I haven't thought of a way to measure battery performance but I'm using it on my phone daily. If it's worse than it should be it's not by a very large margin. I also haven't run any kind of benchmark. (Too early for that in my opinion).

Thx,
for your work on CM13 for 4,7" Variant. If you upload new build with fixed camera i will test it on my europe 6039Y and leave feedback here.
Have a nice day

alecbl said:
I noticed I made a mistake on this build and as such the camera is broken. I'm gonna make a new build in a couple hours.
Click to expand...
Click to collapse
thank you, i'll check it tonight before flashing. i'd do it now but i'm waiting for important calls
Basic functions are all working for me. At least for the 6039Y
Click to expand...
Click to collapse
perfect i also have an 6039Y (2AALWE7)
Wifi should be working. Qualcomm CNE isn't, and I'm unsure if I even want it as a feature, need to research on it.
Click to expand...
Click to collapse
as for me, i hate it.
i'm using profiles to make sure that when my wifi is on, data is off and vice versa. earlier i had surprising phone bills because of this feature :silly:
I haven't thought of a way to measure battery performance but I'm using it on my phone daily
Click to expand...
Click to collapse
perfect :good:
and again: THANK YOU :good:

Updated original post. Cam should be working now.

Thank you very much! I really liked the hardware, but missing the MM update. But CM13 is even better:good::good:

First time I got into a bootloot updating from CM12.1, had to change data and cache filesystem back to ext4, don't forget.
Gonna test it now, hopefully you can merge the latests @Unjustified Dev commits when he makes them public aswell

Phantom410 said:
First time I got into a bootloot updating from CM12.1, had to change data and cache filesystem back to ext4, don't forget.
Gonna test it now, hopefully you can merge the latests @Unjustified Dev commits when he makes them public aswell
Click to expand...
Click to collapse
Yes, I haven't enabled f2fs support yet. I intend to do it at some point. Pivoq had a kernel source tree in which he updated f2fs, supporting xattr etc. I haven't figured out where did he import those changes from yet. I wanted to do the same, but didn't want to import from him because that's not being kept in sync with upstream.
What commits are you talking about?

Xposed work perfectly.

Nice,
i have installed at this time incl. xposed , but without gapps. After first setup all OK. In the next days i test with all my apps and give you feedback. I`m hopefully. :good:

This is the greatest thing to ever happen to my Idol.
Thank you so much. Root and Xposed work fine. Latest version of Busybox installed fine.
Flashed Gapps Pico successfully.
Seems to be really smooth but time will tell. Themes work perfectly.
Using the advanced reboot menu to try and reboot into recovery doesn't work. Granted i'm not using the recovery linked in the original post. I'm using the recovery made by DeckerSU.
What recovery is linked in your post? Is it Cyanogenmod recovery or TWRP and if so, what version?
EDIT: Not even "Adb reboot recovery" will get the device to boot into recovery anymore. Hmm...

Wow, just wow. You did more in one day, than some of the "DEV's" here for their entire time good job man.

Sparkey159 said:
This is the greatest thing to ever happen to my Idol.
Thank you so much. Root and Xposed work fine. Latest version of Busybox installed fine.
Flashed Gapps Pico successfully.
Seems to be really smooth but time will tell. Themes work perfectly.
Using the advanced reboot menu to try and reboot into recovery doesn't work. Granted i'm not using the recovery linked in the original post. I'm using the recovery made by DeckerSU.
What recovery is linked in your post? Is it Cyanogenmod recovery or TWRP and if so, what version?
EDIT: Not even "Adb reboot recovery" will get the device to boot into recovery anymore. Hmm...
Click to expand...
Click to collapse
I have a very good idea of why that's happening. Did you happen to change your bootloader at any point? Alcatel's kernel source has a non standard way of handling reboot, what's more, it's not exactly the same in their lollipop vs marshmallow sources.
The recovery in the post is twrp 3.0.2 with support for encryption and adopted storage. It's using the same kernel, so if you flash that recovery what I expect will happen is that you wont be able to reboot into bootloader or reboot into recovery from the recovery either. The decision of where to reboot into is done by the bootloader and precedes the kernel, just so you know. Changing the recovery can't fix that. Of course you can always do so using power+volume keys, until I fix it.

alecbl said:
I have a very good idea of why that's happening. Did you happen to change your bootloader at any point? Alcatel's kernel source has a non standard way of handling reboot, what's more, it's not exactly the same in their lollipop vs marshmallow sources.
The recovery in the post is twrp 3.0.2 with support for encryption and adopted storage. It's using the same kernel, so if you flash that recovery what I expect will happen is that you wont be able to reboot into bootloader or reboot into recovery from the recovery either. The decision of where to reboot into is done by the bootloader and precedes the kernel, just so you know. Changing the recovery can't fix that. Of course you can always do so using power+volume keys, until I fix it.
Click to expand...
Click to collapse
I don't think I've changed the bootloader since I got the device. I don't have access to fastboot commands. My idol was a O2 branded one that I brought quite recently. I haven't been able to use Petrov.0's method of restoring the fastboot commands either. I don't really mind losing the ability to reboot into recovery from the system since its worth it for Android Marshmallow.
Thanks, I'll be using your recovery from now on too since its more updated. :good:

Flashed, tested
-unlocked 6039Y 2AALWE7
-tap to wake/sleep works
-sms, phone, wifi works
-gapps works
-front camera in photo mode really dark, in video mode is okay
-tried Google Camera from play store, it crashes everytime, when switching from video to photo mode
-so far I love this rom

UNOFFICIAL LineageOS 17.1 "SeLinux enforce mode" (Samsung Galaxy S6 - SM-G920F)

UNOFFICIAL LineageOS 17.1 "SeLinux enforce mode" (Samsung Galaxy S6 - SM-G920F)
Note:================
Tested ==> Samsung S6 (SM-G920F)(Zerofltexx)
========================
LineageOS is an operating system for smartphones, tablet computers, and set-top boxes, based on Android with mostly free and open-source software
All the source code for LineageOS is available in the LineageOS Github Repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
I've built this operating system with select userdebug .
It's unnoficial LineageOS17.1 for Galaxy S6 (ZEROFLTEXX)(SM-G920F).
I strongly recommend to perform a backup of your current rom before installation.
Tested ==> Samsung S6 (SM-G920F)(Zerofltexx)
SeLinux run in enforce mode,
also you can opt to have SeLinux run in permissive mode.
Installation process from stock rom
01. Boot into the download mode.
02. flash TWRP with Odin (comes in AP). The hooks at Auto Reboot and F. Reset Time out.
03. disconnect USB cable after flash, battery out and in again.
04. boot into recovery -> Allow Modifications
05. Advanced Wipe: Dalvik/ART Cache, System, Data, Internal Storage, Cache (lasts a while)
06. install -> select lineage image, then add more zips and gapps, then flash
07. patching system image unconditionally runs through with progress bar
08. Open Gapps are flashed, progress bar runs through
09. when done, tap reboot system, Swipe to install TWRP app (or not, if you don't need it)
10th reboot
11. Lot 17.1 boots. (quite a while ^^)
12. type through the facility
13. ready
Download:
==> tajaribsoft-en.blogspot.com/2020/09/unofficial-lineageos-171-samsung-galaxy.html
Because i'm new , i can't create link

Hi gapps included in ur ROM?
And can I install other boot.img files? I have tried that.
I know it won't work but a question..
Still will download and test..
---------- Post added at 07:25 AM ---------- Previous post was at 06:32 AM ----------
Almost everything works except Volume control while calling the same problem on 17.1 ROMs but everything else works fine I can just adjust volume from my file I'll just patch it with profile text lol thanks.. Very nice work ??????☎?

Yup this is my other account here.
and only on my laptop..
But i managed to get my favourite Kernel to be installed thanks to this beautiful work and kernel i installed is enforced and my ( favourite Kernel )
is pemissive so it depends on kernel and i don`t give a f... nice work man.. Thanks..
I can`t say thank you enough because i have tried other roms to get my thing install`d lol THANK YOU..

Are there any issues with audio on incoming or outgoing calls? Did you manage to get both the front and back cameras working? Most other custom roms have a combination of issues there.
EDIT: I just noticed Johannes did mention a call volume issue

add support 925f zeltexx pls

AnErare said:
Are there any issues with audio on incoming or outgoing calls? Did you manage to get both the front and back cameras working? Most other custom roms have a combination of issues there.
EDIT: I just noticed Johannes did mention a call volume issue
Click to expand...
Click to collapse
It has that same sound software problem.
But I think everything else is working. I try to restore boot from my previous backup it works but (sim not showing).
I try to restore other backup stuff but, of course did not working.
But it amazing i can use other kernel just by restoring from backup
They might be better ways to use other Rom's kernel.
I will use it like that soon without any possibility to have Sim card
I like my kernel lol..
This phone ( I ) use is near death so let end it Battery life with that Kernel I use... Lol
I'll test permissive only file download soon and try to restore boot from backup. And see
Or I should try to install Boot.img from the zip
Edit: It didn't work but first with enforcing SE always boot up no matter what i restore from my backup boot/cache/data/efs. I didn't test other rom enough yet.
And I will test more soon for fun..
Btw.. I got 3 mods installed on my backup so I'm gonna have to test new install's from all rom's and re-test from all over.. Or from start lol..
I want to know you guy's have any mods to make system faster or battery-friendly mods
I have added some text to build.prop and installed 3 mods I think. Maybe not all installs patches:
First for Fullscreen Gesture (Q) from Magisk modules.
Because my ROM is old and I removed some system apps.
And then I install kernel mod from this site. Lol (kTweak) it can be seen from Magisk
And 1 patch from here XDA post few days ago
And my build.prop tweak it looks funny:
ro.min_pointer_dur=0
ro.max_pointer_dur=40
wifi.supplicant_scan_interval=9000000000
windowsmgr.min_events_per_sec=0
windowsmgr.max_events_per_sec=60
debug.sf.nobootanimation=1
logcat.live=disable
ro.media.enc.jpeg.quality=100
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.mot.eri.losalert.delay.delay=1000000000
ro.kernel.checkjni=0
ro.kernel.android.checkjni=0
persist.android.strictmode=0
ro.config.nocheckin=1
That it if I didn't forget something
And make Settings less cpu hog or how to say make it CPU friendly lol .
1 more thing I have edited Sound mixer from System files
You can search it on my comments on my other account Johannes Davidsen
On Enezusun's 17.1 Lineage Os Multitarget rom
I couldn't post attachment's so I have to copied text
That all.
Here, there are 3 sections i think : https://forum.xda-developers.com/showpost.php?p=83187603&postcount=310

This ROM has still the sound volume issues, but camera is working here, right?
This one https://github.com/enesuzun2002/lineageos-ota/releases (28. Feb build) has working call volume and also working cameras, right?
The 13. April build of it has sound issues again and fast battery drain?
It's hard to keep track of what's working in each ROM build and what's not.

About Enes ROM
0x0rbit said:
This ROM has still the sound volume issues, but camera is working here, right?
This one https://github.com/enesuzun2002/lineageos-ota/releases (28. Feb build) has working call volume and also working cameras, right?
The 13. April build of it has sound issues again and fast battery drain?
It's hard to keep track of what's working in each ROM build and what's not.
Click to expand...
Click to collapse
Why don`t you test them by yourself sometimes same device have different problem with same rom and it is very confusing..
For me all of them have working camera and all of them have, calling sound software problem that i just fix by editing sound file..
Have a nice day..
And yes cam is working on this new august build,
same on sound problem too
---------- Post added at 08:13 AM ---------- Previous post was at 08:02 AM ----------
AnErare said:
Are there any issues with audio on incoming or outgoing calls? Did you manage to get both the front and back cameras working? Most other custom roms have a combination of issues there.
EDIT: I just noticed Johannes did mention a call volume issue
Click to expand...
Click to collapse
For me cam is working, only problem i so is the same software problem when trying to lowèr volume on calling or say on earpiece i`ll just replace sound file with the file i already have edited but it is very low.
You can test it i have commented on Enesuzun`s rom i think it started on page: 31 or 32 there are 3 comment sections i use for text
Here: https://forum.xda-developers.com/ga...ageos-17-1-t4053959/post83187603#post83187603

good

Nice work. Thanks for that selinux enforcing rom. Unfortuately I cannot enable encryption. After set in security settings the boot in a bootloop.

schlombie said:
Nice work. Thanks for that selinux enforcing rom. Unfortuately I cannot enable encryption. After set in security settings the boot in a bootloop.
Click to expand...
Click to collapse
I have exactly the same problem. And are there any other things to do to make the device even more secure? Some Modules ?

bemek01 said:
I have exactly the same problem. And are there any other things to do to make the device even more secure? Some Modules ?
Click to expand...
Click to collapse
My dirty trick to enable encryption was, I installed e rom for the device. Enabled encryption without a pin direct after the installation.
Than I installed the 17.1rom without format data. Only wipe system, data and the caches. The rom boot up allready encrypted.
I only set a pin and thats it.

hello or a little problem with the download link, just don't have the link, can you try s create a link on mega or google drive ???
to another thing i wanted to say, i am surprised that you are creating a rom for android 10 with the SElinux Enforcing, i wanted it a lot to increase the security, but the problem of this that lead to lose some battery, however i am interested to try this rom on my samsung galaxy s6 SM-920F i just have to understand where the link lol.
in my opinion, however, thanks to the rom with the SElinux Enforcing maybe this rom could become official if you want, and put on the lineage os website, but honestly I don't know how it works, this is just my opinion
I wanted to say another thing, that second it was better to do lineage os 16.1 because it is much more stable for this device, in fact existing official resurrection remix with android 9 that I use that not a bug, or tried official evolution x with android 10 but the problem of the wi fi that turns off and that you can disable it on the lock screen, and this and these 2 are a big problem, and that problem also exists in the lineage os 17.1 of another creator, everything to see if in the future when there will be lineage os 18.1 for this device with android 11 maybe the wi fi and lock screen security will work prevent you from turning off the wi fi from the lock screen
i am using google translator, hope the translation is right

schlombie said:
Than I installed the 17.1rom without format data. Only wipe system, data and the caches.
Click to expand...
Click to collapse
A wipe basically formats a partition, so what exactly do you mean, that you wiped the encryption too?
I'm sure this ROM doesn't support whatever encryption /e/ may support that you're suggesting.
But maybe I've got this all wrong

schlombie said:
My dirty trick to enable encryption was, I installed e rom for the device. Enabled encryption without a pin direct after the installation.
Than I installed the 17.1rom without format data. Only wipe system, data and the caches. The rom boot up allready encrypted.
I only set a pin and thats it.
Click to expand...
Click to collapse
Thanks. It works for me.
I have one problem with this rom. Bluetooth headphones don't work. I can connect to the phone but the conection is unstable and stop working. it something like: connected, not connected , connected, not connected each 10 seconds or so.
Sorry for my English thanks a lot for your attention.

gerardomare said:
Thanks. It works for me.
I have one problem with this rom. Bluetooth headphones don't work. I can connect to the phone but the conection is unstable and stop working. it something like: connected, not connected , connected, not connected each 10 seconds or so.
Sorry for my English thanks a lot for your attention.
Click to expand...
Click to collapse
Someone please can explain to me step by step how do this trick for enable encryption ?
I've tried 6 times and nothing works maybe I'm misleading something.

Hi, i just wanted to ask how you compiled lineageos for the s6. I tried to compile los 17.1 with the files provided by enesuzun and have massive problems with lunch detecting the files. Many are missing and even if i collect all it just acts weird. Since enes provided many working images these file should work to compile, don't they? Do you know any good tutorial? Most of them are only either for official builds or completely new unsupported devices.
Thank you in advance.
Chasbrot

What gapps? opengapps is provided for 10.0 only...
I have LOS 16.0 from enes but wanted to give it a try.
After wiping (system, cache, data) and installing this rom with opengapps 10.0 and magisk zips,
the reboot stucked in boot loop.

szazs89 said:
What gapps? opengapps is provided for 10.0 only...
I have LOS 16.0 from enes but wanted to give it a try.
After wiping (system, cache, data) and installing this rom with opengapps 10.0 and magisk zips,
the reboot stucked in boot loop.
Click to expand...
Click to collapse
For LOS 16, which is Android 9, you have to use the OpenGApps for Version 9. You can download them at the OpenGApps Project Homepage.
Try one step at a time when flashing or try the newest version from enes.

Chasbrot said:
For LOS 16, which is Android 9, you have to use the OpenGApps for Version 9. You can download them at the OpenGApps Project Homepage.
Try one step at a time when flashing or try the newest version from enes.
Click to expand...
Click to collapse
Oh, I mean: what gapps does this ROM (17.1) need? (with opengapps 10.0 I got into bootloop)

[ROM][R][OFFICIAL] LineageOS 18.1 for Xiaomi Mi 8 Lite [platina]

Reserved

Glad to welcome you devs

Hey @SebaUbuntu,
First of all, thank you for your efforts
I've a few things I'm stuck at, you or someone else hopefully can help me with.
I flashed it with a data partition, encrypted from Android 9. As expected, it refused to boot and going back to the recovery my data partition was garbled.
Formatting it let me boot fine. I then was surprised, to see the storage as encrypted again in settings.
Trying a reboot to recovery I can't manage to get in. All Recoveries I tried, are stuck on the splash screen.
I tried the Pitchblack, OrangeFox, TWRP and SkyHawk recoveries, but it's the same with all of them.
Is there a working recovery that is able to decrypt the data?
Additionally, I setup a lockscreen Pin, but never got asked if I wanted a secure boot. So I'm unable to use a custom pin for the encryption key, which makes it somehow pointless to encrypt in the first place.
How can I solve that?
I want to use the phone without GApps. Instead I plan on using MicroG, which needs signature spoofing.
My old way using Riru Core, Riru EdXposed and the XposedModule FakeGapps to enable signature spoofing doesn't work anymore sadly.
Would it be possible to add a signature spoofing patch to your builds?
TL;DR:
- Is there a Recovery, able to decrypt the data partition encrypted from your rom?
- I can't set my lockscreen pin for a 'secure start', is that a bug or desired behaviour? (And if so, why? )
- Could you enable signature spoofing in your builds please?
Regards,
L

@9Lukas5 Have you tried https://files.sebaubuntu.me/Recovery/LineageOS-Recovery/platina/ ?
I had similar issue with my Mi8 dipper when I upgraded from official Lineage 16 to 17. Twrp wouldn't decript, it turned out the /data mounting dev path was different and twrp couldn't find it. I lived with it for a while until twrp got an update. During that time, I had to use sideload to update Lineage OS.

@haoquan thanks for this tip, I'll save this definitely for the next attempt
I've restore my LOS16 setup for now to have a working phone, as my Setup relies on working Signature Spoofing + MicroG^^.
If someone knows a solution for the Signature Spoofing and custom encryption pin, I'd be pleased to try another upgrade.
In the mean time I'll try to compile an updated LOS16 build using the device parts of this rom (hopefully this will work, otherwise I'll have to find Pie compatible device parts first )
L

Thx sir, for u working.

9Lukas5 said:
Hey @SebaUbuntu,
First of all, thank you for your efforts
I've a few things I'm stuck at, you or someone else hopefully can help me with.
I flashed it with a data partition, encrypted from Android 9. As expected, it refused to boot and going back to the recovery my data partition was garbled.
Formatting it let me boot fine. I then was surprised, to see the storage as encrypted again in settings.
Trying a reboot to recovery I can't manage to get in. All Recoveries I tried, are stuck on the splash screen.
I tried the Pitchblack, OrangeFox, TWRP and SkyHawk recoveries, but it's the same with all of them.
Is there a working recovery that is able to decrypt the data?
Additionally, I setup a lockscreen Pin, but never got asked if I wanted a secure boot. So I'm unable to use a custom pin for the encryption key, which makes it somehow pointless to encrypt in the first place.
How can I solve that?
I want to use the phone without GApps. Instead I plan on using MicroG, which needs signature spoofing.
My old way using Riru Core, Riru EdXposed and the XposedModule FakeGapps to enable signature spoofing doesn't work anymore sadly.
Would it be possible to add a signature spoofing patch to your builds?
TL;DR:
- Is there a Recovery, able to decrypt the data partition encrypted from your rom?
- I can't set my lockscreen pin for a 'secure start', is that a bug or desired behaviour? (And if so, why? )
- Could you enable signature spoofing in your builds please?
Regards,
L
Click to expand...
Click to collapse
- This ROM uses FBE, Secure Boot is a FDE thing, the ROM will now "encrypts" always
- See 1
- No, I want to be compliant with LineageOS, I won't add anything additional to what it provides

SebaUbuntu said:
- This ROM uses FBE, Secure Boot is a FDE thing, the ROM will now "encrypts" always
- See 1
- No, I want to be compliant with LineageOS, I won't add anything additional to what it provides
Click to expand...
Click to collapse
Ok, so if I get this right, this is no bug that Android doesn't offer me a secure start anymore setting a lockscreen pin?
Maybe a bit offtopic, but if the storage can be decrypted by a default password that's not changeable, how is the data security provided?
Edit: Google FBE <-> FDE quickly.
So this means, a "secure start" is always provided automatically, if I set some sort of lockscreen security and the personal files will be accessible only after first unlock after a reboot?
Can you confirm if the recovery from your domain @haoquan linked above will work with the LOS18.1 encrypted data?
Regards,
L

9Lukas5 said:
Can you confirm if the recovery from your domain @haoquan linked above will work with the LOS18.1 encrypted data?
Click to expand...
Click to collapse
fyi, LineageOS Recovery doesn't support data decryption

SebaUbuntu said:
fyi, LineageOS Recovery doesn't support data decryption
Click to expand...
Click to collapse
Yeah discovered this by now^^
That means there's no way of making a nandroid backup before altering around with updates, etc right now :/
But huge thanks for bringing up this rom. Thanks to your work and fully linking the device repo's, I were able to make a private build including the MicroG patch which is mandatory for me. So I finally switched from Pie, which was a rather old build by now.
What I found/would give as feedback so far:
- Video recording doesn't work (gives a green imaged video).
Tried with the built in camera and OpenCamera, both are the same.
L

I have stuck to Havoc 3.9 for past few months. Tried the latest Colt OS but on my Mi 8 lite at least it led to very erratic responses on fingerprint sensor, so I switched back to Havoc. Anyone actually used Lineage 18.1 on theirs and offer any feedback please?
Pros/cons vs Havoc pls

Thanks for this room, I see that the effort has been very gratifying.
I have a problem in the use of the camera, it does not allow recording the images
or videos to the internal or external memory, thanks if you can verify and correct this big problem I would be very grateful.

TheDon13 said:
I have stuck to Havoc 3.9 for past few months. Tried the latest Colt OS but on my Mi 8 lite at least it led to very erratic responses on fingerprint sensor, so I switched back to Havoc. Anyone actually used Lineage 18.1 on theirs and offer any feedback please?
Pros/cons vs Havoc pls
Click to expand...
Click to collapse
I'm using it since ~a week. It's fully stable for me so far
Basically everything except video recording works for me.
Android 10 roms had all the same bug blocking me from switching, that I couldn't playback my music sadly (aac, mpeg4-audio container), that's working fine here.
So I can't give you much of a comparison review, other than that
lewismsc said:
Thanks for this room, I see that the effort has been very gratifying.
I have a problem in the use of the camera, it does not allow recording the images
or videos to the internal or external memory, thanks if you can verify and correct this big problem I would be very grateful.
Click to expand...
Click to collapse
What camera do you use? I'm using OpenCamera, set to use Camera2API and take pictures. Just video recording takes a green image all the way through
L

9Lukas5 said:
I'm using it since ~a week. It's fully stable for me so far
Basically everything except video recording works for me.
Android 10 roms had all the same bug blocking me from switching, that I couldn't playback my music sadly (aac, mpeg4-audio container), that's working fine here.
So I can't give you much of a comparison review, other than that
What camera do you use? I'm using OpenCamera, set to use Camera2API and take pictures. Just video recording takes a green image all the way through
L
Click to expand...
Click to collapse
Good afternoon, flash the rom I use the camera that comes with the same rom and install several additional ones and there is no way I can save the photos and videos that I make with this or another camera. I like the rom, but if I can't use the camera, I fail

9Lukas5 said:
I'm using it since ~a week. It's fully stable for me so far
Basically everything except video recording works for me.
Android 10 roms had all the same bug blocking me from switching, that I couldn't playback my music sadly (aac, mpeg4-audio container), that's working fine here.
So I can't give you much of a comparison review, other than that
What camera do you use? I'm using OpenCamera, set to use Camera2API and take pictures. Just video recording takes a green image all the way through
L
Click to expand...
Click to collapse
I used this rom and it seems better than the original rom, it is quite stable, but for me it is essential to use the camera for both photos and videos and voice recording

@lewismsc Do you know which firmware you're on?
I'm using the V10.3.2.0.PDTMIXM right now.
@SebaUbuntu could a too old / too new firmware cause these different experiences and is there a recommend firmware version for your rom?
L

9Lukas5 said:
@lewismsc Do you know which firmware you're on?
I'm using the V10.3.2.0.PDTMIXM right now.
@SebaUbuntu could a too old / too new firmware cause these different experiences and is there a recommend firmware version for your rom?
L
Click to expand...
Click to collapse
It is recommended to use V12.0.3.0.QDTMIXM

Hi all, thanks for all the advice on what is still a very good phone. I have managed to change the firmware to V12.0.3.0.QDTMIXM MIUI via Mi Flash tool, but when I try to send TWRP recovery (tried several) in fastboot, it says its sent the recovery, but there is no root and fastboot does not go back into main TWRP screen. Never had an issue using firmware 10..3.2. I was using Havoc 3.9 custom rom for a good few months. Also tried Orange Fox & PitchBlack with same result.
Keen to try this lineage 18.1 rom, but I'm stuck.
Grateful for any advice please, as MIUI 12 has its limitations. Can't even get Whatsapp notifications at top of screen!
Thanks

After a good few hours over past few days of frustration, I realised I simply need to press Volume Up on phone when entering fastboot reboot command after successfully flashing TWRP recovery (3.3.1 I tried) ...at long last I can restore my backup from 14 Jan of Havoc 3.12 rom !

Database Users

welcome