Related
Whats the best way to report bugs/suggestions with CM6 RC1 to cyanogen and his team?
For example...
In spare parts, there is an option to make the font size of the system smaller but when I select it and leave the menu. It reverts back to normal.
Another one being, in the customizable section of his settings where you can change the color of notification bars etc.... the color orange is not an option on his color wheel. I had to go find the HTML code for orange to input it myself.
I know these aren't major bugs but it would be nice to see a fix in future RC's
cyanogen said:
CyanogenMod is a free, community built distribution of Android 2.2 (Froyo) which greatly extends the capabilities of your phone.
This version is a release candidate, but you will find it stable for everyday use.
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, I will laugh at you.
*/
This is an AOSP-based build with extra contributions from many people which you can use without any type of Google applications. I found a link from some other project that can be used to restore the Google parts, which can be found below or elsewhere in the thread. I've still included the various hardware-specific code, which seems to be slowly being open-sourced anyway.
Visit the CHANGELOG for a full list of changes and features!
All source code is available at the CyanogenMod Github! If you'd like to to contribute to CyanogenMod, checkout our Gerrit instance.
INSTRUCTIONS:
- First time flashing CM 6 to your G2 (or coming from another ROM)?
1. Unlock/root your device and install Clockwork Recovery via ROM Manager
2. Do a Nandroid backup!
3. WIPE
4. Install the ROM
5. Optionally install the Google Addon
- Upgrading from earlier CM6?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
HOW TO REPORT BUGS OR PROBLEMS?
- Was it a hard reboot? Get me the file "/proc/last_kmsg".
- Was it a soft reboot or a "boot loop"? Run "adb logcat" and get me the full output.
- Pastebin links preferred
- Please use the issue tracker whenever possible!
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Known Issues:
* QuickKeys have not been implemented yet
* Bluetooth Voice Dialer will crash
* WiFi calling stutters a bit
The preferred method of installation is via ROM Manager, or you can head over to the CM Forums for manual downloads.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
Click to expand...
Click to collapse
Everything you need to know about how to report bugs is in the op above.
Sent from my T-Mobile G2 using XDA App
Sent from my T-Mobile G2 using XDA App
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
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.
*/
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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What are UNOFFICIAL builds? A version of CyanogenMod not compiled by CyanogenMod's build servers and may contain code not yet committed to the repository. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Downloads
ROM:http://d-h.st/myfiles?fld_id=28773#files (just look for the one with the newest date on it
Gapps:http://forum.xda-developers.com/showthread.php?t=2012857
use what ever gapps you want but i personally use these ones since its just the basic stuff and its art compatible
Installation
- First time flashing CM11 to your Galaxy S (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM7/CM9?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM10/10.1?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
You will finally see a "set_metadata_recursive" status 7 error. That is normal.
Reboot back into recovery (the reboot is required)
Install the ROM again from internal sdcard using ClockworkMod Recovery
Optionally restore /data from Nandroid Backup (the update will wipe your /data)
Optionally install the Google Addon
- Upgrading from CM10.2?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from another build of CM11?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Warning: You may get set_metadata_recursive related-errors during install if you're using a custom kernel without SELinux support. In that case, revert to the stock kernel before continuing or follow the instruction for upgrading from CM10.1.
Note: The partition layout of CM11 is the same as CM10.2.
Known Issues
Please do not report bugs if it is already listen in the list of known issues
No access to TV-Out menu
Layout issues in lockscreen
Menu soft-buttons appearing where they shouldn't
Some CyanogenMod features a missing - please do not file bug reports for those.
Privacy guard icon not disappearing when exited app
Broken layout of quick message popup (SMS)
Cannot set value via custom brightness "Edit" menu
If back button is pressed during incoming call, you can't answer the call.
FC when changing image sharpness
Pressing "menu" unlocks swipe lockscreen
Browser: FC in incognito mode and Advanced -> Website settings)
Quick Access Ribbon gone when switching from Quick Settings
2G/3G toggle does not work
Cannot flash CM10.2 from recovery (workaround: restore a 10.2 backup or flash a 10.2 kernel before flashing)
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
Code:
What is your--
Phone model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
ART Runtime:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
FAQ
Why is there no transparent status bar/lockscreen widget/"OK Google"?
Those features have been disabled by Google for low RAM device in order to save RAM. You can try enabling it by removing "ro.config.low_ram=true" from /system/build.prop, however, it is not an officially supported setup.
Is there a changelog for gapps?
I did not create the packages and do not know. (Please don't annoy the original developer of the packages by asking him either.)
Does this ROM support FM radio?
I've checked and the new FM API in CM is not really compatible with our device without heavy modification. Applications using the new API expect to be able to read the FM input as it if were another stream, but FM on our device only does pass-through from FM receiver to speaker/headset, which causes certain functionalities to not work such as volume control. Maybe one can modify the audio routing table in the kernel to have it behave like the API expected, but I'm not really interested in investing time to do that.
TL;DR: No built-in FM radio except if someone else does it and submits a patch.
the above gapps are what i personally use you can use what ever ones you would like though
Thanks to
pawtip
CM team
FaultException
Kasper_h
anyone else who i forgot pm me and il add you
Is the problem with the phone speaker solved? On receiving calls, speaker didn't work..
is it fixed??
n205des said:
Is the problem with the phone speaker solved? On receiving calls, speaker didn't work..
is it fixed??
Click to expand...
Click to collapse
Deleted
Could you expain what you did to create this ROM? Did you do straight what was said in the Cyanogenmod building instructions for captivatemtd?
ankamar92 said:
Could you expain what you did to create this ROM? Did you do straight what was said in the Cyanogenmod building instructions for captivatemtd?
Click to expand...
Click to collapse
Basicly
New build soon with some kernel modifications to make it even smoother
All the post is C&P from Pawitp i9000 post lol (except links and credits)
But, whatever, I'll download the rom right now, and will try it later..
BTW, gapps links doesn't work.
And..
cannondaleV2000 said:
Deleted
Click to expand...
Click to collapse
What do you mean with "DELETED"? Fixed?
Thanks for your work ^^
When i installed this, all i got was the little cyanogen robot with the rotating arrow, that lasted for about an hour until i got frustrated with it and just went back to my old rom, any ideas on why this is happening?
Boots fine for me. Did you dirty flash or flash anything else with it?
And yeah it is a c&p from pawtip because it is completely stock cm for now at least
Sent from my SGH-I897 using xda app-developers app
Link gapp error ,file not found
cannondaleV2000 said:
Boots fine for me. Did you dirty flash or flash anything else with it?
And yeah it is a c&p from pawtip because it is completely stock cm for now at least
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Ok, ok, but that not answer my question, the problem with the speaker on receiving call, is fixed?
You answered that to another user --> "Deleted", Deleted == Fixed?
Thanks.
should be. i have not run into the isue so far been running since lastnight.
new build up. syncd with cm sources and tweeked kernel to give more usable available ram
cannondaleV2000 said:
new build up. syncd with cm sources and tweeked kernel to give more usable available ram
Click to expand...
Click to collapse
I think the link you posted, isn't for public, when entering, I can't see anything, only you can see the files on the folder.
OK will fix
Sent from my SGH-I897 using xda app-developers app
Sorry guys I just realized I uploaded the wrong file. Il fix it tomorrow and post a new link
ManaSV93 said:
I think the link you posted, isn't for public, when entering, I can't see anything, only you can see the files on the folder.
Click to expand...
Click to collapse
He linked the myfile link in d-h its goes to my own uploaded file when I logged on in dev- host
Make direct link bro
mohammad.afaneh said:
He linked the myfile link in d-h its goes to my own uploaded file when I logged on in dev- host
Make direct link bro
Click to expand...
Click to collapse
Yep noticed that will fix after school. Because I also uploaded the wrong file top
Downloaded first version, and, have to say that the performance is awesome.
Ram: constant 170 mb free, using BBM, and listening some music.
Web Browser performance was better on CM 10.1
And, with all the KK builds I have tried on the cappy, Every time I turn ON the phone, When OS is completely loaded, I get a message, of invalid IMEI, and that, I can have some problems..
How can I solve this? If I go back to stock rom, and then to CM 10.1, I don't have any problem with this, but when I update to CM 11, I have this error, and don't know wich errors can this give me on future.
Any screenshot ?
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.4 (Kit Kat), 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.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions:
First time flashing CyanogenMod 11.0 your device, or coming from another ROM?
Download the zip(s).
Optional: adb backup
Perform a NANDroid backup of your current ROM.
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Issues?
Report them on github:
https://github.com/M1cha/android_device_xiaomi_aries/issues
What's important: if you use xposed - pls disable it and try it again because it can cause problems in some cases.
Also the issue must contain important information like your phone model(mi2(s)(c)), and the exact build version of the ROM.
Download Links:
CyanogenMod:
Nightly:
Download: http://download.cyanogenmod.org/?device=aries
Google Apps addon:
Use 4.4 gapps:
Download: http://wiki.cyanogenmod.org/w/Google_Apps
Sourcecode:
ROM: https://github.com/CyanogenMod
Devicetree: https://github.com/CyanogenMod/android_device_xiaomi_aries
Kernel: https://github.com/CyanogenMod/android_kernel_xiaomi_aries
GENERAL COMMENT AND REQUEST:
We ask all the regular contributors here to please answer the "xxx is broken" or "yyy force closes" statements without an attached logcat with something like "LOGCAT or it didn't happen"
Feel free to be creative but DO NOT respond with wipe cache/clear data or any other attempted solution before the reporting user has taken the trouble to actually try to help solve the problem (e.g. by attaching a logcat, detailed steps to reproduce etc.).
We need to force more discipline in how issues are reported which will help us all find and squash bugs that may exist.
Just clearing data etc. may in fact cause us to never find the bug that caused the issue and just makes for lazy users.
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
CyanogenMod 11.0 Nightlies, ROM for the Xiaomi Mi 2
Contributors
m11kkaa
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Created 2014-09-15
Last Updated 2014-09-15
Troubleshooting/ FAQs
I am reading FAQs, am I ok?
You're the best , but I'm not sure how you'll fell after you've read these things...
How can I enable Developer/ Performances Settings?
Go to Settings>Info>Click several times on build
How can I enable 4 way reboot (Recovery, System, soft, Bootloader) ?
Enable developer options, then go to Settings>Developer and enable Advanced Reboot
Why there's no HDR on camera?
Cyanogenmod does not provide closed source software, like drivers for HDR, you need to install Miui camera, or another camera from playstore
Why is there no Play Store or <insert gapp here>?
Since there are 2 system partitions they're small, and kk needs about 800mb to have a rom + gapps. There are 2 things u can do: First: install this gapps package this. Second way: use the repartition script of XiaomiTool to extend them.
Why is performances profile resetted every boot?
You need to enable Settings>performances>CPU>Set on boot
Why the phone doesn't fly if I enable airplane mode?
It's a WIP (work in progress) feature, now it works only if you throw it at 11,2 km/s² toward the space. It looks like there's no fix for this (yet).*
How can I enable adb root?
Go to Settings>Developer>Root access> Apps and Adb
How can I hide apps from trebuchet (launcher)?
Click Menu>Protected Apps> Set a "password"> Hide them
How can I charge my phone?
It looks like the xiaomi charger isn't enough powerful to charge the phone with cm. Here's your fix: buy a small nuclear reactor (you can find a cheap one on amazon or ebay I think), place the phone between the uranium fuel rods, power the reactor on and let the phone charging for about an half hour. It will be charged and it won't discharge again anymore.*
(I'm running art, it's very good and i feel better running it) This app FC... What can i do?
Switch to dalvik
Today I updated the phone and it's in a bootloop now...
Nice to get know you're enjoying art, switch back to dalvik flashing this
Bugs
http://wiki.cyanogenmod.org/w/Known_Issues_page_for_aries
[DEV] How to build
http://wiki.cyanogenmod.org/w/Build_for_aries
Two Releases: Nightlies and Stable/Monthly
Nightlies and Monthlies are very different. YOU CAN NOT UPDATE FROM A NIGHTLY TO A MONTHLY WITHOUT A WIPE /DATA. Why? Simple, M releases uses a different branch and it's much older than the previous Nightly avaible, so this may cause bootloops.
So you can update from a Monthly to newer Nightly, but you cannot update from a Nightly to a Monthly. If you choose unstable branch (aka Nightlies) you shouldn't update via ota to Stable branch (aka Monthly), you need to wipe /data.
Other Info
http://wiki.cyanogenmod.org/w/Aries_Info
I'll be building Slim (and maybe Omni) for this soon, so I was wondering which vendor repo do you use?
Great I use themuppets https://github.com/TheMuppets/proprietary_vendor_xiaomi
Sorry for the possible spam, I just wanted to ask will this be now ''official'' thread for CM11 instead of the one on xiaomi.eu?
SkaldfraNorden said:
Sorry for the possible spam, I just wanted to ask will this be now ''official'' thread for CM11 instead of the one on xiaomi.eu?
Click to expand...
Click to collapse
yes
Hi, a question about TDB: I (stupidly) formatted /sdcard before flashing CM11 (to get rid of MIUI folders), and I lost write permission. To fix that, I enabled TDB and installed MIUI on system2 and booted. However, I will never boot into MIUI again, I'm only interested in CM. Is leaving TDB enabled affects performance in any way? And is there a different way to restore permissions other than flashing MIUI?
isaacbh said:
Hi, a question about TDB: I (stupidly) formatted /sdcard before flashing CM11 (to get rid of MIUI folders), and I lost write permission. To fix that, I enabled TDB and installed MIUI on system2 and booted. However, I will never boot into MIUI again, I'm only interested in CM. Is leaving TDB enabled affects performance in any way? And is there a different way to restore permissions other than flashing MIUI?
Click to expand...
Click to collapse
Sdcard format is not working well on cwm cuz of tdb. U have to flash a fastboot package and or flash a stock miui with miflash.
Tdb doesn't affect performances at all.
Tdb doesn't mess with sdcard at all so it probably is a cwm bug.
Good to see we're moving to XDA!
m11kkaa said:
Tdb doesn't mess with sdcard at all so it probably is a cwm bug.
Click to expand...
Click to collapse
Another scenario in which this bug showed for me was this. Maybe this is useful to track the issue.
I installed CWM 6.0.5.0, and then WIUI (4.7.18) based on KK.
After formatting the sdcard from within WIUI, even without rebooting, at that point the internal sdcard couldn't be written any longer from within WIUI.
I'm using this ROM and i'm really impressed.
One thing though is that my battery is going down much faster than on miui.
Any tips?
Check if you have wakelocks and freeze with greenify
does anyone have problem with Gapps on CM11-M10 like me? Gapps force-close all the time although I had try to reflash the rom 2 times!
you either have to flash a very small gapps package or resize your system partition(s)
thienquang07 said:
does anyone have problem with Gapps on CM11-M10 like me? Gapps force-close all the time although I had try to reflash the rom 2 times!
Click to expand...
Click to collapse
Read FAQs
Great ROM!
So far everything has been running smooth. Performance is great, feels much speedier than Mokee OS. Battery seems to be going down a bit faster, but I've been setting everything up so that probably explains the battery drain.
Something that really annoys me though, is that music playback stutters whenever you touch something. Opening the app drawer, any app, upvoting a post on Reddit Sync, ... Everything makes the music stutter for a split second.
Mavamaarten said:
Great ROM!
So far everything has been running smooth. Performance is great, feels much speedier than Mokee OS. Battery seems to be going down a bit faster, but I've been setting everything up so that probably explains the battery drain.
Something that really annoys me though, is that music playback stutters whenever you touch something. Opening the app drawer, any app, upvoting a post on Reddit Sync, ... Everything makes the music stutter for a split second.
Click to expand...
Click to collapse
Disable "sound on touch"
linuxxxx said:
Disable "sound on touch"
Click to expand...
Click to collapse
Oh god. I'm glad the fix is that simple. Thanks a bunch, I really didn't think of that.
I even disabled the "Okay Google" hotword because according to some googling the issue was connected to that.
Video camera records video maximum 10 minutes. Could it be changed to unlimited?
And also sound quality is very poor in recorded videos. I looked through spectrums and it appears that they are cut above 8000Hz. Seems like on some stage signal is being sampled with 16000 Hz sample rate and, judging by some bubbling and other artefacts, it is made without prior antialiasing filtering. Output format acc 48000 Hz.
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
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.
This thread is for Official LineageOS 14.1 builds for chagallwifi (SM-T800) The following will not be supported here:
Custom kernels
Mods
Xposed
I 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
Have not attempted a clean flash
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Install the Google Apps addon package (Optional)
Reboot
Make sure you have the Marshmallow bootloader. Guide is in the comments below.
There will be a new build every week, every Monday.
The builds will no longer be personally tested by me before being uploaded (but everything will probably be fine)
Change logs will no longer be posted within every new build, but instead when the changes are uploaded to GitHub. I will try though to post changes for major bugs or fixes as they are released.
Some builds might feature only minor changes, ie. only updating the LineageOS source
Chagallwifi Download
Google Apps:
Beans GAPPS 7.1.2
Kernel
https://github.com/LineageOS/android_kernel_samsung_exynos5420
Device Tree
https://github.com/LineageOS/android_device_samsung_chagallwifi
Aytex, who made all of the banners on this post.
@Barracuda77777 (For helping along the way)
@UpInTheAir for his kernel magic and misc fixes
@crpalmer (for picassowifi device and kernel gits - the base @Barracuda77777 and @nvertigo67 started of from)
@eousphoros (for his device git)
@nvertigo67 (for his work on chagallwifi)
@Nexorrr (for his work on chagalllte)
Fingerprint is disabled
Other issues?
Before posting in this thread, make sure of a few things:
You used the search function of the forums.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread.
Logs! You can use this: https://play.google.com/store/apps/details?id=com.tortel.syslog
For OTA updates to flash correctly:
Update your TWRP to 3.1.0-1 (USE THE 2017-05-04 BUILD OR LATER. DO NOT USE A BUILD FROM BEFORE THIS DATE)
You can get Official TWRP 3.1.0-1 for chagallwifi from this link!
TWRP for CHAGALLWIFI
This updated TWRP recovery image contains a fix that will allow it to flash OTA updates properly!
How to update to Marshmallow bootloader (required for 20170324 and later builds)
Updating the bootloader is very quick and doesn't wipe data or repartition the device.
If the last Samsung ROM you had was 6.0.1 Touchwiz, you already have Marshmallow bootloader and don't need to follow these steps. (If you were on MM, and it still won't boot, follow the steps below)
1. Download the bootloader-only Odin package: T800XXU1CPK2.tar.md5
This has the latest Marshmallow bootloader (December 2016)
https://www.androidfilehost.com/?fid=457095661767146298
2. Download Odin 3.11
You can skip this if you already have a working Odin
https://www.androidfilehost.com/?fid=673368273298937183
3. Shutdown your tablet and start it up by holding Power+Home+Volume Down to enter Download Mode. Volume Down is the one right next to the power button. Really shut it down and use this key combination, if you use Advanced Restart, or go into download mode via TWRP the bootloader won't change.
4. Make sure the screen of your tablet has a green android symbol with a "Downloading..." text
5. Open Odin3_v3.11.1.exe and follow the instructions in this image:
If anything is missing, you WON'T flash bootloader successfully.
6. Click Start. Your tablet will automatically reboot back into your ROM.
7. To verify you have the new bootloader, you can run in terminal emulator "getprop ro.bootloader". It should say T800XXU1CPK2.
Thanks @ZakooZ for the post!
Deathly Adiutor App
Deathly Adiutor is an open-source, modified version of Kernel Adiutor made specifically for Exynos 5420 devices.
Features
Power Saving:
S-Pen Power Saving - Same as in Touchwiz, disables S-Pen detection if it's inserted in the slot
S-Pen Input Booster - Instantly increase CPU frequency when the S-Pen touches the screen
Touchscreen Input Booster - Instantly increase CPU frequency when you touch the screen
Touchkey Input Booster - Instantly increase CPU frequency when you touch the capacitive buttons
Touchscreen Glove Mode (Not all screens support this)
CPU Control:
CPU Settings reworked - Deathly adiutor back-end was cleaned up to work specifically with our CPU
CPU Thermal - Control all thermal throttling points for the CPU (make your device run colder... or even hotter)
GPU Control:
GPU Time in States - Same as CPU Time in States (Times in each frequency)
GPU Frequency Control (not yet supported on Nougat)
GPU Voltage Control (not yet supported on Nougat)
GPU Governor Control (not yet supported on Nougat)
Battery control:
Full power statistics - See current and maximum charging currents and current source of power
Unstable power source detection - Lowers current until the power source is stable
Customize charger current limits - Make your device charge faster (safe, if the charger can not supply enough current, the board will dynamically decrease the current)
Screen-On current limiter - Limit charging if screen is on (to avoid overheating)
Speakers:
Privacy mode - Disable main speaker if headphones are plugged in
Earpiece volume
Left/Right speaker volume
Speaker equalizer
Headphones:
Left/Right channel volume
Mono output mode
Headphone equalizer
App Themes:
Light theme - White and Red
Dark theme - Grey and Red
Credits
This post was written by @ZakooZ
This app is brought you by the exynos5420 developer team: @deadman96385 @thompatry @ZakooZ @Orion116 @mosimchah @joshndroid @Andmoreagain @thermskin, @javelinanddart, @tincho5588, @ShevT @DarkExistence
Translators:
@ShevT - Russian
The following people deserve distinction for their major contribution:
@tincho5588, responsible for 80%+ of the code for the new features
@deadman96385, the main maintainer of the Deathly kernel and most of the remaining code
Downloads
The app can be found in the Play Store:
Free version (with ads): https://play.google.com/store/apps/details?id=com.exynos5420.deathlyadiutor.ads
Donator version (no ads): https://play.google.com/store/apps/details?id=com.exynos5420.deathlyadiutor.adfree
Helping the developers
You may have noticed there's 2 versions of this app, one ad-free for donators and one with ads.
You can help us by clicking ads you're interested in for the free version, or purchasing the donator version!
We will use the money generated by this app as common money for the developers of the team. It will be used to pay for our web-hosting (we own a gerrit server and a domain name, exynos5420.com). It will also be used to buy a new device if one of ours breaks.
Translating the App
You can also help us by translating the app to your language:
1. You can start by looking at the full english language file: Link
2. Then compare it to your unfinished language file. You can find it here, under values-xx/strings.xml, xx being your language abbreviation.
3. You can then fill-in the missing strings in your language file. Here's an example of what a proper update looks like.
4. Then you can submit your translation by using our gerrit. If you don't know how to use gerrit, just PM the translation to your favorite developer and he'll get it merged!
Thx for your work
Looking forward to testing it out
Thank you very much for your work!
It doesn't works for me, I only see boot animation and it doesn't start even after 20 minutes. I tried Paulicat version and works fine. Whi? I did a clean flash.
Same for me. Bootllop after flashing ROM and latest Gapps (nano).
Yeah, bootlooping.
BananaPrime said:
Yeah, bootlooping.
Click to expand...
Click to collapse
I installed with a full wipe (including internal sdcard), using latest pico gapps.
No issues...
I also recently updated my bootloader to Mashmallow, but I doubt that's what makes mine bootup while some bootloop.
Bootlooping? How far does it boot ?
Please be 100% certain that you wiped dalvik, system, data and cache in twrp and try flashing without gapps. Did you change anything such as flash custom kernels etc?
Could one of you take a logcat during boot for me please. It has to be user error seeing as mine is working fine, and others are working fine. The number of downloads - complaints shows that.
Just plug your tablet into you PC while it's booting (make sure you have adb installed)
Then , once you start to see the screentype adb logcat into your terminal (./adb logcat if windows or Linux)
Thanks
Just upgrade from @Paulicat's Jan 17th build to this Jan 25th build; just flashed lineage, open gapps nano and SuperSU (in that order, in one go) and rebooted.
Looks like the video problems of the previous release are not present here; I can now play YouTube Videos at high res and use the HW codecs of MX Player without stuttering; previously I had to drop from 1080p to 720p or use the MX+ codecs to make it play smooth.
The WebView component apparently still have problems; using for instance FlipBoard to read articles causes a crash/weird screen flickering from time to time, associated with a crash. The log reports a WebView crash (there's first a "OpenGLRenderer: GL error: Out of memory!" followed by a google-breakpad dump of "WebView:55.0.2883.105" "A arm 04 armv7l samsung/lineage_chagallwifi/chagallwifi:7.1.1/NMF26V/e609fadfba:userdebug/test-keys" "webview" "OpenGL ES 3.0|ARM|Mali-T628" and a long hex dump.
Finally, GPS does not work out of the box; the gpsd still misses a few libraries. I've copied them from elsewhere (RR, if I recall correctly) and have placed libsec-ril.so and libxml.so in /system/lib -- and then GPS works instantly (as far as I can tell it may lock on faster than on the previous build).
I guess the WebView has to be fixed upstream, but maybe the missing gps related libraries could be included in the next build?
Thanks for your great work!
- Per.
pnomandk said:
Just upgrade from @Paulicat's Jan 17th build to this Jan 25th build; just flashed lineage, open gapps nano and SuperSU (in that order, in one go) and rebooted.
Looks like the video problems of the previous release are not present here; I can now play YouTube Videos at high res and use the HW codecs of MX Player without stuttering; previously I had to drop from 1080p to 720p or use the MX+ codecs to make it play smooth.
The WebView component apparently still have problems; using for instance FlipBoard to read articles causes a crash/weird screen flickering from time to time, associated with a crash. The log reports a WebView crash (there's first a "OpenGLRenderer: GL error: Out of memory!" followed by a google-breakpad dump of "WebView:55.0.2883.105" "A arm 04 armv7l samsung/lineage_chagallwifi/chagallwifi:7.1.1/NMF26V/e609fadfba:userdebug/test-keys" "webview" "OpenGL ES 3.0|ARM|Mali-T628" and a long hex dump.
Finally, GPS does not work out of the box; the gpsd still misses a few libraries. I've copied them from elsewhere (RR, if I recall correctly) and have placed libsec-ril.so and libxml.so in /system/lib -- and then GPS works instantly (as far as I can tell it may lock on faster than on the previous build).
I guess the WebView has to be fixed upstream, but maybe the missing gps related libraries could be included in the next build?
Thanks for your great work!
- Per.
Click to expand...
Click to collapse
Glad most things is working for you!
Yep, this build has a more updated device tree then what Paulicat had so there are a few fixes!
GPSD is being investigated by @deadman96385 and should be an easy enough implementation
Thats the first time I have heard about the webview implementation, would you mind sending a full log? Thanks for letting us know!
DarkExistence said:
Glad everything is working for you!
Click to expand...
Click to collapse
So far, it's better -- also appears more "smooth" and fluid in use, I think
GPSD is being investigated by @deadman96385 and should be an easy enough implementation
Click to expand...
Click to collapse
Yep, possibly just a few missing libraries or a different linking method, or something. Good you're working with @deadman96385 on this also; he already responded to this in the other thread when I debugged and reported it related to the previous build.
Wiped all for 3 times, it doesn't boot.
Eboshi Moriyama said:
Wiped all for 3 times, it doesn't boot.
Click to expand...
Click to collapse
I have a f2fs data partition. Perhaps that ist the reason for the bootloop?! (i have the bootloop too)
Clean flash - boot OK - flashed pico OK - flashed superSU OK - boot OK
No prob at all :good:
kaodd said:
Clean flash - boot OK - flashed pico OK - flashed superSU OK - boot OK
No prob at all :good:
Click to expand...
Click to collapse
tried again with clean ish flash - bootloop
tried dirty over RR 7 - boot ok - total frozen :laugh:
start with 3-fingers in recovery, u know what i mean
starting again lineageOS Darky-Edition
nice boot animation, kinda posh will try xposed too
My T800 is currently happily running the now out of date [AOSP 7.0][T700/T705/T800/T805] by @Schischu so I'm looking to upgrade. Here are apps I'd like to know work before I give this ROM a try. If anyone can tell me if they work or not I'd appreciate it. If any of them are considered mods I apologize in advance as I've read the OP mods policy. In any case I'd never ask for their support or inclusion in the ROM as that's my responsibility.
Here's my list:
Viper4Android
Substratum
LastPass (some other 7.1.1 ROMs have issues with this app)
Netflix
Plex
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
LineageOS is a free, community built, aftermarket firmware distribution of Android 12L (Sv2), 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 Githup repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended LineageOS recovery in the official installation instructions link below.
You can use TWRP for installation, however it is no longer officially supported since we do not have full control of its update cycle and potential issues.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
Installation Instructions:
Backup your data and see the next post below
Recommended TWRP Image:
twrp-3.7.0_9-0-kuntao.img
ROM Download Links:
Google Drive | SourceForge
Recommended Google Apps Package:
NikGapps-core-12.1
NikGapps-SetupWizard
NikGapps-AndroidAuto
Or
MindTheGapps-12.1 (Google Drive mirror)
Root Access:
Magisk v25.2 (more stable experience)
Magisk v26.1 (more updated build)
Recommended Useful Add-on:
p2oggle-1.2
Source Code:
https://github.com/LineageOS
ROM Firmware Required:
Any version of stock 6.0. Recommended P2a42_S251_171107_ROW
Acknowledgements:
Thanks to @mikeioannina for his hard work regarding kuntao and to all other Lineage OS developers
Special thanks to @Astridxx for the device tree sources and for helping me out and to @en666 for early testing the initial build
Important Notes:
As you can see from my profile, I'm not an experienced developer. I've made some builds as a considerable amount of users showed interest in having their devices updated with latest LineageOS code. Therefore, my main objective here is to bring the latest Android security patches to kuntao making monthly builds.
To be clear, I'm more in a situation of "user became builder" than of "ROM developer". Please, understand this.
Long live to our beloved kuntao!
XDAevDB Information
[ROM][12.1][UNOFFICIAL] LineageOS 19.1 for Lenovo P2
Contributors
@Astridxx ,@XiaoAk ,@Sohit5s, @mikeioannina
ROM OS Version: 12.x
ROM Kernel: Linux 3.18.x
Based On: LineageOS
Version Information
Status: Stable
Created 2023-02-22
Last Updated 2023-06-11
Installation Instructions
Remember, making a backup of your data before proceeding is recommended
If you are coming from Stock ROM, please refer first to the instructions below:
Install LineageOS on kuntao
If you are coming from astridxx previous build (aka lineage-19.1-20220822-UNOFFICIAL-kuntao) or my initial build (aka lineage-19.1-20230222-UNOFFICIAL-kuntao) or any version of LOS18.1 or below, you must perform a clean flash. Clean flash instructions:
0- Make a backup (optional, but recommended)
1- Reboot to recovery
2- Format data (will delete all your data!)
3- Reboot to recovery again
4- Wipe > Advanced Wipe:
- Dalvik
- System
- Vendor
- Data
- Cache
- Internal Storage (optional, but recommended)
5- Flash ROM ZIP, Gapps, Gapps add-ons, Magisk add-on, etc
6- Reboot to system
7- Wait until it boots for the first time (may take some minutes)
Update Instructions
NOTE: Dirty flash from any of the aforementioned builds is not supported, device trees were changed. You have been warned!
For updating from one of my builds to another (aka dirty flashing), please do the following:
1- Download ROM ZIP and copy it to the phone
2- Reboot to recovery
3- Flash ROM ZIP
4- Clean cache
5- Reboot to system
Known Issues- Storage encryption is partially broken (if your /data partition is unencrypted, trying to encrypt it using ROM menu will result in a dead OS; if already encrypted, storage encryption may or may not work. IFAIK, it's a kernel side issue)
- Device may not go to deep sleep
- Storage forceencrypt flag is disabled (to encrypt /data partition follow the instructions below)
- TWRP backups are broken (read notes below)
- You tell
Google Play Store Update Bug
If Google Play Store app keeps failing to find updates for apps with message "Something went wrong. Try again.", just clear its data and then it should work again
SafetyNet Check Fails
If your device is rooted, please, follow the instructions contained here
Magisk is Gone After First Boot
Please, just reflash Magisk again (i.e. Reboot to recovery > Flash ZIP > Reboot back to system)
How to encrypt data partition
0- Backup your files (this process will erase everything)
1- Boot to TWRP recovery
1.1- Wipe > Format data > Reboot to system
2- Settings menu > Security > Encryption & credentials > Encrypt phone
3- Reboot to system again
Error restoring TWRP system backups
It looks like TWRP backups are broken for now, so please, if this is a must have for you, you can try to install OrangeFox recovey and follow these instructions (thanks @Zdeslav for that)
ROM Change logs
Code:
02/22/2023
- Initial release
02/27/2023
- Sync latest LOS sources
- Device Tree change: Use old A12L dt instead of los
- Add Lenovo Parts menu (fp gestures, USB fast charge, in-call audio gain, screen kcal)
- Updates phone vibration strength
- Add fix to device deep sleep issue
- Many more changes
03/29/2023
- Fetch latest Device Tree sources
-- vendorsetup.sh: Add Trebuchet patch
-- AOSP WFD doesn't support protected Wi-Fi Display buffers
-- Overlays:
--- Enable voWIFI support
--- Disable IMS features for Turkiye networks
-- Don't warn user about FC in Vanced microG
-- DT rootdir:
--- Add cpuset for the camera daemon
--- Remove permission restrictions to the socket file
--- Restore iio sensor device6 on boot
-- Bump graphene camera version to 60
-- Don't force enable ims features
-- sepolicy: Address sensor hal denials
- Update LOS components
-- Manifest: Sync x86_64 webview prebuilts again
-- Update zlib source
- Sync latest LOS source
- Merge March security patch
04/09/2023
- Fetch latest Device Tree sources
-- Add navbar enable/disable support
-- fs: Revert sdfat update for OTG
-- block: Add zen io scheduler
-- dts: Decrease BCL low battery threshold to 5%
-- DeskClock:
--- Wallpaper based text coloring for digital
--- Adapt digital clocks to S style
--- Remove night mode
-- Trebuchet:
--- Kill haptics in recents
--- Make overview scrim transparent again
-- Nfc: Fix Mifare Classic reading
- Update LOS components:
-- lineage: Track the FMRadio App and dependencies
- Sync latest LOS source
04/19/2023
- Fetch latest Device Tree sources:
-- sepolicy: Silence tracingproxy_service neverallow denial
-- sepolicy: Allow system_app to access storaged via IPC
- Sync latest LOS source
- Merge April security patch
05/09/2023
- Fetch latest Device Tree sources:
-- Bump graphene camera version to 62
-- devicesettings: Protect broadcast to fingerprint gestures
-- rootdir: Remove permission restrictions to the socket file
- Sync latest LOS source
- Merge May security patch
06/11/2023
- Fetch latest Device Tree sources:
-- parts: Update few parts icon
-- vendorsetup.sh: Use depth=1
-- Remove pixel_2016_exclusive
-- Bump graphene camera version to 63
- Sync latest LOS sources:
-- Additional zstd cmdline tools
-- zstd compression support for rsync
-- 2023-06 ASB patching: packages/apps/Traceur
- Merge June security patch
ROM Screenshots
Attached below. Others are available here.
February 27th 2023 Release
Changelog:
- Sync latest LOS sources
- Device Tree change: Use old A12L dt instead of los
- Add Lenovo Parts menu (fp gestures, USB fast charge, in-call audio gain, screen kcal)
- Updates phone vibration strength
- Add fix to device deep sleep issue
- Many more changes
Download URLs: GDrive | SF
Dirty flash still not supported (tree changed), please make a clean flash
Thank you so much for keepng Lineage alive, its very much appreciated.
@leo_97 thank you for this new build! Installed it straight away and now the phone is running since then and also, I've flashed with battery at 67% and atm, after a quite hard usage to test out the new features, I'm on 13%. Basically, so far so good!
p2a42, twrp 3.7, rooted, unencrypted
Thank you @leo_97 !
I was frustrated that Lineageos 18.1 was no longer maintained when I saw this update!
It's amazing
To all users and developers who tested and created this ROM, is it time to switch on this version ?
Or is it better to wait ?
For example, automatic update is possible after install ?
bidulez said:
automatic update is possible after install ?
Click to expand...
Click to collapse
No
bidulez said:
Thank you @leo_97 !
I was frustrated that Lineageos 18.1 was no longer maintained when I saw this update!
It's amazing
To all users and developers who tested and created this ROM, is it time to switch on this version ?
Or is it better to wait ?
For example, automatic update is possible after install ?
Click to expand...
Click to collapse
You are welcome
If it's time to switch, I believe it's a matter of personal decision. Maybe you could wait the next build and then decide...
If with "automatic updates" you mean OTA updates, then the answer (as already pointed out by @utwer ) is no. But once the trees are stable enough, I hope every user will be able to just update to the newer versions flashing ROM ZIP through TWRP (just like it's done on LOS18.1)
BTW, IDK if you already saw it, but we are maintaining a monthly build of LOS18.1 which you can download from here. The source tree used there is far more tested (as it's older) than this one. Anyway, except by the encryption thing, you shouldn't have any problems using this LOS19.1 ROM as our amazing developers made an excellent job here.
Reg, Ive installed it and I may say it is quite good. Not tried to root it yet. Dont have direct problems with ROM and functionality, for me everything works. Camera, Location, GSM, Data, WiFi. With developer options I've turned off Animation scale on three options to OFF, and is good. Stable reliable.
MindTheGapps-12.1 works every app from Google, Phone, Contact, Gmail, maps...etc...
What I need root mostly is for Call recording (Skvalex) and Viper4Android.
Some words about twrp-3.7.0_9-0-kuntao.img,
With this I have only problems, so far I lost a few backups and I need to install it all over again a few times allready. Disappointed very. I can't rally on this when I make a nandroid ba.ckups.
Also lost backups for LOS18.1 and I am been very pis....ed off. Error 255 on System recovery, other Data, Boot, EFS, Vendor, etc.. recovery is good.
So I've installed OrageFox for Kuntao. Tried several backups to restore already and I may say I am very satisfied. Puh
What is on my mind, when I installed a Magisk 25.2, no matter of LOS 18.1 or 19.1 with very few modules, after 7-8 reboots I've got boot loops which is beyond repairable.. Try to remove modules in TWRP in file manager, uninstall whole magisk, no way, but what it is seems that DATA got corrupted some how, everytime.
There were also installed TWRP mentioned above.
Now I am with OrangeFox and I will try tomorrow to Root it and see is there any connection between Magisk and recovery software (OrangeFox or TWRP).
Reg
Tried quickly this ROM yesterday. In general all working, but didn't test much.
Few feedbacks:
-Scaler for brightness level is weird, very different from the original Lenovo roms. Anyway, not really important, but something that I noticed.
-Missing haptic feedback when using the fingerprint reader as a gesture button. Again, not critical, but I am really accustomed to it and thus I noticed immediately.
-Missing haptic feedback intensity regulation, or could not find it. It's there for general call/notification vibration, but if I remember correctly lineage could also change haptic.
Impressed that you could integrate also some lenovo features, even if of course not all of them
If you want me to test something more specific, please let me know. Ah, my model is the 4 GB/ 64 GB combination.
Cheers!
leo_97 said:
You are welcome
If it's time to switch, I believe it's a matter of personal decision. Maybe you could wait the next build and then decide...
If with "automatic updates" you mean OTA updates, then the answer (as already pointed out by @utwer ) is no. But once the trees are stable enough, I hope every user will be able to just update to the newer versions flashing ROM ZIP through TWRP (just like it's done on LOS18.1)
BTW, IDK if you already saw it, but we are maintaining a monthly build of LOS18.1 which you can download from here. The source tree used there is far more tested (as it's older) than this one. Anyway, except by the encryption thing, you shouldn't have any problems using this LOS19.1 ROM as our amazing developers made an excellent job here.
Click to expand...
Click to collapse
So for 18.1 we can just flash the newer versions via TWRP and do not have to reinstall the entire ROM?
Zdeslav said:
Reg, Ive installed it and I may say it is quite good. Not tried to root it yet. Dont have direct problems with ROM and functionality, for me everything works. Camera, Location, GSM, Data, WiFi. With developer options I've turned off Animation scale on three options to OFF, and is good. Stable reliable.
MindTheGapps-12.1 works every app from Google, Phone, Contact, Gmail, maps...etc...
What I need root mostly is for Call recording (Skvalex) and Viper4Android.
Some words about twrp-3.7.0_9-0-kuntao.img,
With this I have only problems, so far I lost a few backups and I need to install it all over again a few times allready. Disappointed very. I can't rally on this when I make a nandroid ba.ckups.
Also lost backups for LOS18.1 and I am been very pis....ed off. Error 255 on System recovery, other Data, Boot, EFS, Vendor, etc.. recovery is good.
So I've installed OrageFox for Kuntao. Tried several backups to restore already and I may say I am very satisfied. Puh
What is on my mind, when I installed a Magisk 25.2, no matter of LOS 18.1 or 19.1 with very few modules, after 7-8 reboots I've got boot loops which is beyond repairable.. Try to remove modules in TWRP in file manager, uninstall whole magisk, no way, but what it is seems that DATA got corrupted some how, everytime.
There were also installed TWRP mentioned above.
Now I am with OrangeFox and I will try tomorrow to Root it and see is there any connection between Magisk and recovery software (OrangeFox or TWRP).
Reg
Click to expand...
Click to collapse
So,
Resolved issue of bootloops:
after you install SU like Magisk, and wan to freeze apps by Titanium Backup or Neo-Backup, Apps which causes bootloops are ROM's Phone and Massages (In my case, for 16.1, 18.1, 19.1), I freeze Audio.apk who need to be shutdown for Viper4Android app who takes audio management and freezing is OK.
But Phone and Massages which are frozen cause bootloops, so you need to return from freeze state somehow in TWRP or OrangeFox with file management or revert backup. Revert backup is easier .
Camera; found issue when suddenly is out of work and cannot be connected to app. Also have problems with video cast Skype, Viber, Whatsapp, Telegram video is frozen. Hardly switch in Camera app from Camera mode to Video mode and vice-versa.
Clock & Info; missing dock icons and info, can't "capture" moment for reason when they disappear but after a while all is returned again.
P2oggle, left switch button work okey in form of 0.4 version.
Reg,
thanks on the development for this 19.1 ROM.
Zdeslav said:
Camera; found issue when suddenly is out of work and cannot be connected to app. Also have problems with video cast Skype, Viber, Whatsapp, Telegram video is frozen. Hardly switch in Camera app from Camera mode to Video mode and vice-versa.
Clock & Info; missing dock icons and info, can't "capture" moment for reason when they disappear but after a while all is returned again.
P2oggle, left switch button work okey in form of 0.4 version.
Reg,
thanks on the development for this 19.1 ROM.
Click to expand...
Click to collapse
Hello,
I've been using this ROM as my daily driver and couldn't confirm this camera bug, could you please give a few extra details? I tested on Telegram app. Which version are you using? The Play Store's one or the one from Telegram's official website? Did you give the app "While using app" permission or "Ask every time" permission for camera? Are you sure the QS Tile "Camera access" is activated (available) when the mentioned bug occurs?
Regarding the Clock widget, yes, there's a small glitch and I'm not sure on how to fix it, if it doesn't load at all, a system reboot should fix it.
P2oggle v1.2 is 100% working as far as I can tell, so you guys can try it too if you want.
MKbis said:
-Scaler for brightness level is weird, very different from the original Lenovo roms. Anyway, not really important, but something that I noticed.
-Missing haptic feedback when using the fingerprint reader as a gesture button. Again, not critical, but I am really accustomed to it and thus I noticed immediately.
-Missing haptic feedback intensity regulation, or could not find it. It's there for general call/notification vibration, but if I remember correctly lineage could also change haptic.
Click to expand...
Click to collapse
I'm not sure if it's possible to "fix" the brightness slider.
If with "haptic feedback" you mean the phone vibration, you can just adjust it to your liking in Settings > Lenovo parts > Vibration strength, it should affect fp reader too, dunno if it affects call vibration but IFAIK it should.
Regards
Leo_97
I've been using this ROM as my daily driver and couldn't confirm this camera bug, could you please give a few extra details? I tested on Telegram app. Which version are you using? The Play Store's one or the one from Telegram's official website? Did you give the app "While using app" permission or "Ask every time" permission for camera? Are you sure the QS Tile "Camera access" is activated (available) when the mentioned bug occurs?
Click to expand...
Click to collapse
Yes on latest Telegram app from web site, tried with Google Meet, Whatsapp, Viber.., always breaking connection with API/drivers. Yes I gave all permissions to Camera. If I am not giving permissions for camera, I have always noticed to confirm what I am giving, so I am excluded from this solution. And clean storage and cashe from app regular but not prevail.
But, in a while after installed a new ROM without giving SU/Root I noticed this behavior, right after I wrote earlier post up. My bad .
Choppy startup of camera, can't easily transfer from video 2 camera and vice-versa, so I tell to my self to test intensively.
Regarding the Clock widget, yes, there's a small glitch and I'm not sure on how to fix it, if it doesn't load at all, a system reboot should fix it.
Click to expand...
Click to collapse
Yes after a while it is returned back without reboot. weird.
P2oggle v1.2 is 100% working as far as I can tell, so you guys can try it too if you want.
Click to expand...
Click to collapse
Didn't know about P2oggle v1.2 app, thx
March 29th 2023 Release
Changelog:
- Fetch latest Device Tree sources
- Update LOS components webview & zlib
- Sync latest LOS source
- Merge March security patch
- Many more changes
Full change log available on the bottom of this post
Download URLs: GDrive | SF
Note: Please, before flashing, carefully read the instructions from the 3rd post above to avoid breaking your system.
Enjoy!
Big Thank you for this release. Will try it. - test
Great job, dude.
Previous versions had some buggy charging driver that left a wakelock running after each charging, and u had to restart phone each time or leave it to slowly drain battery by not going to sleep.
Somehow this problems seems to be gone in your build and that is awesome.
I've been using the build for about 2 weeks now and so far everything seems to be working fine.
April 09th 2023 Release
Change log:
- Fetch latest Device Tree sources (lots of changes)
- Update LOS components:
-- lineage: Track the FMRadio App and dependencies
- Sync latest LOS source
- Many more changes
Full change log available on the bottom of this post
Download URLs: GDrive | SF
Note: Dirty flash is unsupported for this build, please make a clean flash
Enjoy!