About CyanogenMod
CyanogenMod is a free, community built, aftermarket firmware distribution of Android which is designed to increase security, performance, reliability and customization over stock Android.
About nightly builds
Nightly builds are automatically compiled builds of the latest CyanogenMod source from github. These builds are not officially supported. If you find bugs or issues please discuss here. Do not submit bug reports for nightly builds on the CyanogenMod issue tracker.
How to install
Preparation
Ensure you have a working copy of ADB for your PC. A simple search should find versions for all major operating systems.
If you are running "stock" (ColorOS), the first thing you will need is a recovery. There are many recoveries available. The most popular ones are CWM and TWRP. Please consult other threads to find and install a suitable recovery.
Once you have a suitable recovery, download from download.cyanogenmod.org to your PC.
If you wish to have Google applications available such as the Play Store, download a current copy of gapps. CM recommended gapps are shown at wiki.cyanogenmod.org.
Reboot your phone into recovery.
Installation
If you wish to save any of your current data, back it up. Details vary by recovery. The app "Titanium Backup" is also popular to backup and restore your installed apps.
Wipe your internal data. Again, details vary by recovery. The option is usually called "wipe data / factory reset" or something similar. This is absolutely critical and required if you are coming from a stock ROM or a different third party ROM. Note! If you are coming from a previous nightly build of CM11, you can often get away with keeping your data. But if you encounter any issues, please wipe data and retry.
Find an option in your recovery that looks like "Install from sideload" or Install from ADB" and select it. On your PC, run "adb sideload cm-11-yyyymmdd-NIGHTLY-find7.zip". ADB should show a progress indicator. When the file has completed uploading, it should install. Repeat with your gapps package if desired.
Reboot your phone. The first boot after install can take a few minutes (usually no more than 5 minutes) so be patient.
Enjoy!
tdm
Systems Engineer
Cyanogen, Inc.
Known Issues
* Find7s: Screen may not wake when phone is hot.
This is apparently an interaction between the thermal throttling code and the video/gpu driver. It has been reproduced and we are working on a fix.
* Find7s: Notification light sometimes misbehaves.
We are working on a fix.
* Find7a: Battery sometimes drains too quickly.
This issue is under investigation. We do not have a repro or a fix at this point.
* Find7a: Mic doesn't work while on speakerphone.
This issue is under investigation. We do not have a repro or a fix at this point.
@tdm,
thanks for this, could you please let me know what the bugs for this are?
About time we hade a thread for CM in here!
Thanx and good work @tdm.
Would like to know what Recovery we must use. CWM or can we also use TWRP? What GAPPS - BANKS or PA GAPPS. Also when u use the package with google camera it breaks the camera functionality!
Answered my own question:
TWRP and CWM both work good.
Use PA GAPPS with NO! Google Camera
Cm works pretty well for me. When the Android OS is not draining my battery I can easily hold it out for over 24h, hope it gets fixed soon.
Is there something I can do to help in helping fixing this problem?
Besides I've had it a few times now that when I unlock my screen that my flashlight turns on, very weird, but only had it since today/latest nightly.
Willthor said:
I've had it a few times now that when I unlock my screen that my flashlight turns on, very weird, but only had it since today/latest nightly.
Click to expand...
Click to collapse
That has happened to me many times. The screen gestures are very sensitive. This is a firmware/hardware issue. I believe we plan to use the proximity sensor to mitigate the issue, not sure if that has been committed already or not.
Will CM include this following?
*50 MP Camera Snapper like on ColorOS
*Breathing Notifications (not Blinking Notifications like implemented now on CM).
Also there is a problem when you charge via VOOC Rapid Charger when the device is turned off, the output process on the screen will be an endless loop of Oppo logo->then Charging Indicator->Oppo Logo-> Charging Indicator again and just repeatedly same process.
hulicow said:
Will CM include this following?
*50 MP Camera Snapper like on ColorOS
*Breathing Notifications (not Blinking Notifications like implemented now on CM).
Also there is a problem when you charge via VOOC Rapid Charger when the device is turned off, the output process on the screen will be an endless loop of Oppo logo->then Charging Indicator->Oppo Logo-> Charging Indicator again and just repeatedly same process.
Click to expand...
Click to collapse
I believe Oppo is reserving 50mp for their own ROM.
Don't know about breathing notifications.
I'll try to look into off mode charging.
I'm on 07/15 nightly and the only bug I have is mic on speaker calls.
This is my daily driver now.
Anyone knows of a camera app that can take slow shutter photos like on colorOS camera?(about the only feature I miss from colorOS)
I don't need the 50mp camera thing. But proper hdr and more reliable auto focus would be nice. Up get a lot of out of focus pics on CM compared to ColorOS.
And a fix for the busted HLS streaming in kitKat would be sweet.
One more thing...a solid newb proof fix for the stupid partition layout would be awesome.
Finally...Auto brightness is borked. It's an issue on every ROM I've tried. Really frustrating.
Sent from my X9006 using XDA Premium 4 mobile app
tdm said:
Known Issues
* Find7s: Screen may not wake when phone is hot.
This is apparently an interaction between the thermal throttling code and the video/gpu driver. It has been reproduced and we are working on a fix.
* Find7s: Notification light sometimes misbehaves.
We are working on a fix.
* Find7a: Battery sometimes drains too quickly.
This issue is under investigation. We do not have a repro or a fix at this point.
* Find7a: Mic doesn't work while on speakerphone.
This issue is under investigation. We do not have a repro or a fix at this point.
Click to expand...
Click to collapse
Is the battery draining issue still there?
Juiceboy125 said:
Is the battery draining issue still there?
Click to expand...
Click to collapse
No battery drain for me at least.
But I can't seem to take a proper panorama photo, not even with OnePlus camera.
Other than those few annoying bugs it's the smoothest experience I 've ever had.
gamotom said:
No battery drain for me at least.
But I can't seem to take a proper panorama photo, not even with OnePlus camera.
Other than those few annoying bugs it's the smoothest experience I 've ever had.
Click to expand...
Click to collapse
Well, that's good to hear. I've had this rom for awhile and I just wanted to make sure. But, if you mind me asking, how much screen time do you usually get? I get about 5 and a half average.
Juiceboy125 said:
Well, that's good to hear. I've had this rom for awhile and I just wanted to make sure. But, if you mind me asking, how much screen time do you usually get? I get about 5 and a half average.
Click to expand...
Click to collapse
I get about 1,5 days of use with 4 and a half SOT. But keep in mind that I like my display bright so I've tweaked up autobrightness values.
Has anyone here experienced screen going unresponsive after a bit of browsing on chrome. No issues using Mozilla Firefox though!
Re battery drain: the battery drain happens in standby. Then the battery looses ~1.5-2% per hour, meaning almost 15-20% overnight. It should be only a few instead.
To investigate this, can you guys with no battery drain let us know which modem/firmware you guys are using?
Thanks!
Using the last few nightlies, I've noticed that the gestures no longer work with the screen off. Specifically, double tap to wake and drawing a circle to start the camera.
Not sure if it's something I did on my end or a more common issue
nihir said:
Using the last few nightlies, I've noticed that the gestures no longer work with the screen off. Specifically, double tap to wake and drawing a circle to start the camera.
Not sure if it's something I did on my end or a more common issue
Click to expand...
Click to collapse
double tap 2 wake works with flashing last 3 nightlys!
silasje1 said:
double tap 2 wake works with flashing last 3 nightlys!
Click to expand...
Click to collapse
Hmm. Must be something I've done. Thanks!
Related
Thread Closed !!
New Google's Android 4.2.1 Features
-> Photo Sphere
-> Gesture Typing
-> Multi-User Support (Tablets Only)
-> Miracast Wireless Display Support
-> Daydream
-> Notification Power Controls
-> Google Now Improvements
For More Information on Which of the above features available in CyanogenMod, Come to My New Thread T989 Official CM10.1 4.2.1 Discussion (Coming Soon)
Enjoy !!! :good:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
theandroidrooter88 said:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
Click to expand...
Click to collapse
This is why i started this Thread, So we can discuss Bugs in the latest versions. :highfive:
I heard AOKP JB is stll having SODs and RRs. Do u find anything like these?
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
First we have to fix our flashing methods and recoveries used. I for one haven't experienced one single RR or SoD since I started flashing official nightlies. People are probably causing these issues themselves to begin with. Expecting a fix for an issue that has no identifiable cause.. I wonder if any other phones outside the t989 forums are experiencing RR and SoDs with Jelly Bean..
Sent from my SAMSUNG-SGH-T989 using xda premium
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
garth719 said:
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
Click to expand...
Click to collapse
Great to hear that your running latest 10-Oct Nightly. A Simple advice to you & all other users, is to restore app without data if your are using any backup tools such as TitaniumBackup etc., Restore Apps with data cause Problems.
srikanth.t989 said:
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
Click to expand...
Click to collapse
Sorry, I don't mean to crap on the thread but unless you can confidently say that SODs and RRs have been fixed (changelogs, yourself writing the code, etc.), going by your own experience shouldn't be the end-all-be-all to say whether something is fixed or not. Just like with call echo, some devices are worse than others.
I see that supposedly the issue with audio and docking has been addressed. However, the docking option is still grayed out for me when docked. Just looking for audio pass-through while docked...
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
eight_heads said:
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
Click to expand...
Click to collapse
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
I'm on recent CM10 Oct10 nightly and the BLN lights stay on, even with the Oct 7 nightly.
Update: fixed my own problems. This post helped: go to menu - systems - advanced settings - sensor and uncheck and check enable keys notifications and then send yourself a text or email. It actually should work out the box mine always has. Make sure you have notifications checked off in the apps like sms and gmail.
Also check display - notification light to make sure it enabled and you can add the apps you want to have the light enabled to work
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
garth719 said:
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
EDIT:
Just ran the music player for 45min on a run. no skips, nothing.. ran a 90 mb mp3 file too which usually gives my ipod trouble.. good sign
Click to expand...
Click to collapse
So is that how we're saying we don't get random reboots anymore? We just call them something else??
algorhythm said:
So is that how we're saying we don't get random reboots anymore? We just call them something else??
Click to expand...
Click to collapse
well there was a difference in this reboot because my phone didnt actually fully shut off. the "cyanogenmod" boot animation came up and the phone was ready to go in about 20 seconds. there was no usual vibration indicating that the phone has shut off and no "samsung" boot image as a regular reboot would do. call it what you will
Quote:
[email protected]: on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
Try updating it on the market
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Laazyboy said:
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Run only One ROM. Do a clean reflash. We are not experiencing any SODs or RRs. Use only one ROM because Flashing different ROMs one after the Other will Make your device weak. The data left by the AOKP causes some errors to CM10. Thats why i said that don't restore the apps with data.
Happy New Year everyone!
I'm a complete noob to root/flashing my samsung captivate glide so please forgive me if these questions seems stupid. I searched on google and in this forum but can't seem to find answers.
I just recently rooted + flash to CM10.1 (android 4.2.1 beta) on my phone and I have been playing around with the software for the past 2 days. I'm pretty happy with it so far; patiently waiting for some fixes like Bluetooth and keyboard back light (like everyone else). I would also like to take this opportunity to say thanks to everyone involved in these kinds of projects. You guys fill the need left in the gap between the manufacturers and the service providers that decide that our phones are obsolete and shouldn't get updates even if the phone can actually benefit from said update.
Today I just tried something: I pushed the power button and on the screen there was a menu to reboot or shutdown: I selected reboot, and then had other choices on screen, and I selected "download" thinking it would go into update mode?... so the device rebooted into download mode and I see the green android logo with the words "Downloading..." in white and "Do not turn off target!!" in green. It's been like that for 30 minutes now and I was just wondering if it truly is downloading something and/or if I can just pull the battery out right now to turn the phone back on normally. If it really is downloading, I find it funny that it's taking so long since I have a 20 MB connection speed...
The reason I went into download mode is because I saw the options inside android 4.2.1 to update CM10.1 automatically (I chose "nightlies" and "check twice a day"...) and I have yet to see any updates being done. Will there be a pop-up of some kind if there are any nightlies available for download? Will I have to go into download mode to apply the updates? Do they auto-download when the phone is on and they update at next reboot? Please explain the update process...
Also. I don't know if this is a problem or not, but I noticed in JB that my battery seems to drain faster than with GB installed... nothing drastic, but noticeable. For example, if I turn everything off except cell antenna overnight, 10 hours later I have 10% less battery. It used to be around 5% less battery. Can anyone confirm that JB uses more battery than other android versions?
Thanks for taking the time to answer all my questions, I appreciate it and hopefully it will answer other noob questions in the future.
Download mode is used for downloading an operating system via Odin and USB connection. Rather curious how you would not have used that to get to where you are now, unless you obtained your phone with a CWM recovery already on it?
As for battery life, in my time lurking here, I haven't seen many posts about it, but can weigh in with my thoughts. I noticed a significant power drain when I had enabled Google Now. Once I had turned it off, my battery life improved drastically. Still does seem to drain a bit more than stock, but I suspect that is due to optimizations that need to happen for our devices and/or bugs in cm10 itself, as I have seen some things suggesting issues with the screen auto brightness in someone's ROM notes...
Hope this helps and welcome to the world of Android modding!
Artemis-kun said:
Download mode is used for downloading an operating system via Odin and USB connection. Rather curious how you would not have used that to get to where you are now, unless you obtained your phone with a CWM recovery already on it?
As for battery life, in my time lurking here, I haven't seen many posts about it, but can weigh in with my thoughts. I noticed a significant power drain when I had enabled Google Now. Once I had turned it off, my battery life improved drastically. Still does seem to drain a bit more than stock, but I suspect that is due to optimizations that need to happen for our devices and/or bugs in cm10 itself, as I have seen some things suggesting issues with the screen auto brightness in someone's ROM notes...
Hope this helps and welcome to the world of Android modding!
Click to expand...
Click to collapse
Thanks for your quick reply,
Yes I used the Download mode with odin to root my device, but I wasn't sure why it was written "Downloading...." like it was actually downloading something (like a CM10.1 update or something). Anyway, thanks for confirming that this is the same download mode as for odin.
Do you know how the CM10.1 updates work? will it post a message on the phone when an update is available?
I am already using auto-brightness so that's not the issue and all other antennas are off, except for cellphone antenna to receive calls.
anyway, it's not a big problem for now, there are still tweaks and updates to come so we will see how battery use develops in the coming weeks/months.
Thanks for your answers.
bombermanCC said:
Thanks for your quick reply,
Yes I used the Download mode with odin to root my device, but I wasn't sure why it was written "Downloading...." like it was actually downloading something (like a CM10.1 update or something). Anyway, thanks for confirming that this is the same download mode as for odin.
Do you know how the CM10.1 updates work? will it post a message on the phone when an update is available?
I am already using auto-brightness so that's not the issue and all other antennas are off, except for cellphone antenna to receive calls.
anyway, it's not a big problem for now, there are still tweaks and updates to come so we will see how battery use develops in the coming weeks/months.
Thanks for your answers.
Click to expand...
Click to collapse
Purely guessing, but seeing as how the OTA updates work from carriers, you get notified in the notification bar and downloads the ROM while the phone is still up and running, I would assume CM would work the same way. But, I don't think it's actually enabled as of yet, since the ROM is still in development. Feel free to anyone to correct me on this, but I feel I am more or less correct on this.
bombermanCC said:
Today I just tried something: I pushed the power button and on the screen there was a menu to reboot or shutdown: I selected reboot, and then had other choices on screen, and I selected "download" thinking it would go into update mode?... so the device rebooted into download mode and I see the green android logo with the words "Downloading..." in white and "Do not turn off target!!" in green. It's been like that for 30 minutes now and I was just wondering if it truly is downloading something and/or if I can just pull the battery out right now to turn the phone back on normally. If it really is downloading, I find it funny that it's taking so long since I have a 20 MB connection speed...
Click to expand...
Click to collapse
It's waiting for Odin to connect to it via USB. Just hold the power button until it shuts off.
The reason I went into download mode is because I saw the options inside android 4.2.1 to update CM10.1 automatically (I chose "nightlies" and "check twice a day"...) and I have yet to see any updates being done. Will there be a pop-up of some kind if there are any nightlies available for download? Will I have to go into download mode to apply the updates? Do they auto-download when the phone is on and they update at next reboot? Please explain the update process...
Click to expand...
Click to collapse
That only works for official CM releases. You'll have to check the thread periodically and manually update by downloading the zip and flashing it with CWM.
Also. I don't know if this is a problem or not, but I noticed in JB that my battery seems to drain faster than with GB installed... nothing drastic, but noticeable. For example, if I turn everything off except cell antenna overnight, 10 hours later I have 10% less battery. It used to be around 5% less battery. Can anyone confirm that JB uses more battery than other android versions?
Click to expand...
Click to collapse
JB battery has been better for me than the official ICS was. There's so many variables there though, you're probably doing something different or have some app installed that you didn't before.
BACKUP YOUR EFS THROUGH FREEGEE AND/OR TWRP
{
"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"
}
This is a preview of CM-12.0 built entirely from CM sources. There are few modifications (listed below in features).
Features
- Settings->About Phone->CyanogenMod updates uses wfhome.net servers (my builds)
Latest Build
I have started Nightly's
Downloads
Latest Builds
http://goo.gl/kQP3f8 - Private Hosting (no ads, no waiting, enjoy)
Old Builds
http://goo.gl/Sz2K7a - Android File Host
Google Apps
http://forum.xda-developers.com/android/software/gapps-google-apps-flashable-package-t2930266
TWRP - 2.8.3.0
http://teamw.in/project/twrp2/155
Known Issues
- "No SIM Card" message on lock screen (CM12 issue)
- Built in Messenger App doesn't work right (CM12 issue)
- Nothing else that I have noticed
All changes can be viewed on the CyanogenMod gerrit.
Thanks to all who have developed CyanogenMod and the device and kernel trees for the Optimus G.
I'm using a modified version of @JulianXhokaxhiu CyanogenModOTA tools on my web server.
https://github.com/julianxhokaxhiu/CyanogenModOTA
Source
http://github.com/CyanogenMod
http://github.com/rjwil1086
The E970 and LS970 are slightly different, have you used the LS970 sources to build? The LS970 has minor differences in the camera as well as it being CDMA and not requiring a SIM card. Are these taken into affect? I am going to test because this is actually based on US hardware so I am hoping for most things to work that do not because other builds are based from international versions.
dopy25 said:
The E970 and LS970 are slightly different, have you used the LS970 sources to build? The LS970 has minor differences in the camera as well as it being CDMA and not requiring a SIM card. Are these taken into affect? I am going to test because this is actually based on US hardware so I am hoping for most things to work that do not because other builds are based from international versions.
Click to expand...
Click to collapse
I did use the LS970 sources. I have AT&T and Sprint phones (just not an LS970) so I am aware of the network differences. I am also aware of the 13MP camera the LS970 has. This is built entirely with CM sources (I'm using a fork of http://github.com/TheMuppets for vendor blobs; I added some gps blobs to get gps working). The device tree for these two phones share a lot of stuff as they are broken into 3 repositories (gproj-common, ls970-common, and ls970). The e970 also uses gproj-common and ls970-common which are about 95% of the device tree code for both phones. There is already a CM-12.0 branch on github for the ls970 so I'm assuming it was updated just like the e970. Just need someone with hardware to check it out.
rjwil1086 said:
I did use the LS970 sources. I have AT&T and Sprint phones (just not an LS970) so I am aware of the network differences. I am also aware of the 13MP camera the LS970 has. This is built entirely with CM sources (I'm using a fork of http://github.com/TheMuppets for vendor blobs; I added some gps blobs to get gps working). The device tree for these two phones share a lot of stuff as they are broken into 3 repositories (gproj-common, ls970-common, and ls970). The e970 also uses gproj-common and ls970-common which are about 95% of the device tree code for both phones. There is already a CM-12.0 branch on github for the ls970 so I'm assuming it was updated just like the e970. Just need someone with hardware to check it out.
Click to expand...
Click to collapse
Great! Sounds like you know what you are doing. I am downloading it right now and am at 20%. I will flash when done and absolutely report back.
EDIT FOR FINDINGS
@rjwil1086 GREAT JOB! The ROM is working great on my device (LS970) so I will send some feedback
PROS
1) Everything seems to work for the most part except items listed under CONS.
2) Calls and data are working from flashing, no extra steps needed to achieve calls or data. 4G coverage included.
3) Superuser is integrated (THANK YOU)
4) Camera works superb, even quality is amazing. (see cons)
5) Voicemail by long pressing one works and on other CM12 does not.
6) You can turn on "flash" while video recording so you have overhead light. Maybe I've missed that in every other ROM but that's great! (Does not cause phone to power down, see #6 cons)
CONS
1) Messaging app does not send a text from within the built in app (Quick reply works fine) I think this is CM issue and not device because it is in all CM based roms currently.
2) Swipe texting does not work with built in keyboard.
3) No SIM card appears in notification bar on lock screen (once again in other CM12 ROMS).
4) Data usage is not tracked at all, it says no apps used data right after I used the browser and the Play Store to download something.
5) NEW FINDINGS:: Phone calls will not end, pressing the end icon only makes the end option go away but the phone call is still in progress. I tried using a bluetooth headset and only the device. My work around is to enable Airplane Mode then disable it, that shuts the phone call off.
6) using flash in any camera app causes device to power off, overhead light during video recording is fine though.
7) Volume control on screen lock is not possible. You must unlock the screen to alter the volume (notable in music playing)
8) Very important!! While making a call, the phone immediately disconnects. When I call back, the other caller is still connected so it goes to voicemail. I have to ask them to ignore the first call so I can make it again. This happens every time and is very difficult to manage since I have to enable airplane mode to end the call.
On another note, I am using the Multiboot method and have this installed as primary, I haven't tested any secondary ROMs but I do not expect them to boot and that is due to a specific patch being required for the kernel that is not compatible with gproj. Also, it will not install as secondary, it fails upon flashing. The only thing I noticed is that it takes awhile longer at the boot screen to get past it than other roms. No issues though since it works to my expectations.
I will continue to use this to see if anything else comes up, but over all this is awesome. I look forward to CM fixing things upstream. Please keep those builds coming, they work.
Looks good. Once those CM bugs get worked out, this ROM will be fantastic! Thank you for this ROM! Willing to test any new updates. Seems like dopy did a pretty solid review so far.
This ROM running Android Lollipop 5.0?
RegKilla said:
This ROM running Android Lollipop 5.0?
Click to expand...
Click to collapse
Yes, CM12 is 5.0 (in this case 5.0.1)
EDIT: @rjwil1086 ...
GREAT JOB ON THAT UPDATE. I'm not sure if it was you that fixed it or CM fixes, but some of the previous issues are gone. Now this is extremely stable. I definitely recommend it to anyone with an LS970.
Fixed issues: (calls are main thing fixed)
1) Calls end perfectly fine
2) Phone no longer shuts off at flash of the camera.
3) no issues with music. (I didn't mention it before but when I would try to play music from any app, it would say it was playing but the song would not progress and there was no sound. I also attributed it to my bluetooth headset, but now the issue is gone)
4) Adaptive brightness and notification bar brightness adjustment has always worked with this ROM. (basically all aspects of brightness work)
still existing issues
1) Volume control on inactive lock screen. (still have to turn on screen)
2) Data usage still not tracked by settings/data usage.
3) messaging app will not show active send, pressable icon (cannot send text from within the app but quick reply still works) (I'm certain CM issue)
4) Swipe texting with built in keyboard (most likely CM issue)
5) Not really an issue but lock screen still says "No SIM card" (CM issue?)
Great update, more than half of the major issues have been fixed, now it seems like mostly CM issues , and not even major problems.
dopy25 said:
Yes, CM12 is 5.0 (in this case 5.0.1)
EDIT: @rjwil1086 ...
GREAT JOB ON THAT UPDATE. I'm not sure if it was you that fixed it or CM fixes, but some of the previous issues are gone. Now this is extremely stable. I definitely recommend it to anyone with an LS970.
Fixed issues: (calls are main thing fixed)
1) Calls end perfectly fine
2) Phone no longer shuts off at flash of the camera.
3) no issues with music. (I didn't mention it before but when I would try to play music from any app, it would say it was playing but the song would not progress and there was no sound. I also attributed it to my bluetooth headset, but now the issue is gone)
4) Adaptive brightness and notification bar brightness adjustment has always worked with this ROM. (basically all aspects of brightness work)
still existing issues
1) Volume control on inactive lock screen. (still have to turn on screen)
2) Data usage still not tracked by settings/data usage.
3) messaging app will not show active send, pressable icon (cannot send text from within the app but quick reply still works) (I'm certain CM issue)
4) Swipe texting with built in keyboard (most likely CM issue)
5) Not really an issue but lock screen still says "No SIM card" (CM issue?)
Great update, more than half of the major issues have been fixed, no it seems like mostly CM issues , and not even major problems.
Click to expand...
Click to collapse
Yup all those were fixed by CM developers. I saw several CDMA fixes in the ril code. I'm sure there were more elsewhere in the code. Swipe on the keyboard is disabled in CM because it doesn't work on any of my devices.
rjwil1086 said:
Yup all those were fixed by CM developers. I saw several CDMA fixes in the ril code. I'm sure there were more elsewhere in the code. Swipe on the keyboard is disabled in CM because it doesn't work on any of my devices.
Click to expand...
Click to collapse
So the 12/20/14 build fixes those bugs?
Downloading now. Thank you for this again! Breathes some life into this old phone lol.
Edit; I would just like to add; you sir, have made me love cyanogenmod once again.
I use to use CM 10.2 all the time, but honestly, when the official CM11 came out with LS970 sources, it always felt, not laggy, but not responsive. As in just sluggish. Gee Roms always ran fast on my optimus, but always over heated easily too.
I absolutely love this ROM. It is extremely fast and uses LS970 sources. I can finally leave stock confidently. Is there anyway I can repay you? I am on mobile, so I can't see much, but do you have a donation link? I'd pay to keep this going.
Fantastic job. It works great!
Never had this much responsiveness on a LS970 cm ROM before.
Edit 2: Does anyone know how to disable mobile data? I like to turn it off so it doesn't suck battery in low service areas. Thanks again.
Whiplashh said:
Edit; I would just like to add; you sir, have made me love cyanogenmod once again.
I use to use CM 10.2 all the time, but honestly, when the official CM11 came out with LS970 sources, it always felt, not laggy, but not responsive. As in just sluggish. Gee Roms always ran fast on my optimus, but always over heated easily too.
I absolutely love this ROM. It is extremely fast and uses LS970 sources. I can finally leave stock confidently. Is there anyway I can repay you? I am on mobile, so I can't see much, but do you have a donation link? I'd pay to keep this going.
Fantastic job. It works great!
Never had this much responsiveness on a LS970 cm ROM before.
Edit 2: Does anyone know how to disable mobile data? I like to turn it off so it doesn't suck battery in low service areas. Thanks again.
Click to expand...
Click to collapse
I agree, it is definitely snappier than any ROM I've ever used on this phone.
As far as data, I don't know. I tried a few widgets and shortcuts to no avail. I'm sure it's a matter of time before it's enabled in settings from CM.
I did have some partial success with quick shortcut maker. Run a search for "data" and try to use the shortcut to data roaming under "phone." What it did was say settings has force closed, but it shut off my mobile data. It caught me off guard but a reboot turned it back on.
On the plus side, battery life is pretty wicked already.
dopy25 said:
I agree, it is definitely snappier than any ROM I've ever used on this phone.
As far as data, I don't know. I tried a few widgets and shortcuts to no avail. I'm sure it's a matter of time before it's enabled in settings from CM.
I did have some partial success with quick shortcut maker. Run a search for "data" and try to use the shortcut to data roaming under "phone." What it did was say settings has force closed, but it shut off my mobile data. It caught me off guard but a reboot turned it back on.
On the plus side, battery life is pretty wicked already.
Click to expand...
Click to collapse
Even with data on the battery is good? That's awesome!
Just a heads up, the build does still have some phone issues. Can't call on first try and hangup without hitting airplane mode. Calls coming in work perfectly, but out can be a hassle.
Whiplashh said:
Even with data on the battery is good? That's awesome!
Just a heads up, the build does still have some phone issues. Can't call on first try and hangup without hitting airplane mode. Calls coming in work perfectly, but out can be a hassle.
Click to expand...
Click to collapse
From what I've noticed, it is absolutely great on battery. I'll post some screen shots. I was in and out of 3/4G. Downloaded a few files, probably 500mb worth. Played tapped out, which is a freaking battery hog. And still lasted a whole day. I did just notice that the total hours don't seem to be tracked, that's odd.
On the phone thing, I am so sorry you're still having that issue, it is gone for me. Are you sure you're on the 12/20 build? Maybe we did something different.
I flashed the 12/18 and GApps since I tried it first (then restored the backup of it because I had since flashed another ROM and neither would work as secondary on my multi boot setup) then I flashed the 12/20 build to update (dirty flash over 12/18) cleared cache's twice because I like to. And it seemed to work. That's a real bummer that it doesn't work for you. Incoming or outgoing work fine for me, for now anyway.
screen shots I'll have to post later, I always have issues doing that on my phone
dopy25 said:
From what I've noticed, it is absolutely great on battery. I'll post some screen shots. I was in and out of 3/4G. Downloaded a few files, probably 500mb worth. Played tapped out, which is a freaking battery hog. And still lasted a whole day. I did just notice that the total hours don't seem to be tracked, that's odd.
On the phone thing, I am so sorry you're still having that issue, it is gone for me. Are you sure you're on the 12/20 build? Maybe we did something different.
I flashed the 12/18 and GApps since I tried it first (then restored the backup of it because I had since flashed another ROM and neither would work as secondary on my multi boot setup) then I flashed the 12/20 build to update (dirty flash over 12/18) cleared cache's twice because I like to. And it seemed to work. That's a real bummer that it doesn't work for you. Incoming or outgoing work fine for me, for now anyway.
screen shots I'll have to post later, I always have issues doing that on my phone
Click to expand...
Click to collapse
I clean flashed the 12/20 build. Wiped everything twice because thats how I do. Had to go back to stock so I could make calls and organize a friends bday party. Hopefully this flash will be better.
Whiplashh said:
I clean flashed the 12/20 build. Wiped everything twice because thats how I do. Had to go back to stock so I could make calls and organize a friends bday party. Hopefully this flash will be better.
Click to expand...
Click to collapse
The weird thing is, it's happening intermittently for me as well. But it seems more like making calls from the first call screen. Selecting recents seems to not do it. Also seems like it happens more when LTE is on. I haven't tried switching to 3G only but it dedi definitely didn't do it when I only have 3G.
dopy25 said:
The weird thing is, it's happening intermittently for me as well. But it seems more like making calls from the first call screen. Selecting recents seems to not do it. Also seems like it happens more when LTE is on. I haven't tried switching to 3G only but it dedi definitely didn't do it when I only have 3G.
Click to expand...
Click to collapse
It just happens all the time. I'm using CWM recovery so I don't know if that effects it. Hopefully it will work out soon. That and the messaging bug. Loving the ROM so far. Once those 3 things are fixed, this phone won't see stock again lol.
(Data toggle, messaging send which IS a cm thing, and the phone issue).
Whiplashh said:
It just happens all the time. I'm using CWM recovery so I don't know if that effects it. Hopefully it will work out soon. That and the messaging bug. Loving the ROM so far. Once those 3 things are fixed, this phone won't see stock again lol.
(Data toggle, messaging send which IS a cm thing, and the phone issue).
Click to expand...
Click to collapse
I can only assume that recovery shouldn't be an issue as long as it's semi up to date. But some people are having sensor issues on all other builds and it very well could be related, I don't know enough on the subject. I will keep up on this because this ROM really is slick. I use textra for messaging but I really like the built in messenger. Google messenger is almost identical but has MMS issues. Nothing on textra, it works perfectly. So I'm still using this daily. I'm sure data toggle will go in soon. I see an APN update in the change log so I'm sure it's coming soon. I'll keep you updated.
dopy25 said:
I can only assume that recovery shouldn't be an issue as long as it's semi up to date. But some people are having sensor issues on all other builds and it very well could be related, I don't know enough on the subject. I will keep up on this because this ROM really is slick. I use textra for messaging but I really like the built in messenger. Google messenger is almost identical but has MMS issues. Nothing on textra, it works perfectly. So I'm still using this daily. I'm sure data toggle will go in soon. I see an APN update in the change log so I'm sure it's coming soon. I'll keep you updated.
Click to expand...
Click to collapse
Thank you!
Whiplashh said:
Thank you!
Click to expand...
Click to collapse
Give today's build a shot. I just made about 10 phone calls to various numbers from various locations within the dialer and all connected the first time, and disconnected fine.
There is still no data toggle, but data is now being tracked (or at least showing that it was previously tracked) I also do not see any apn settings but that might not have been an update for our device that I saw.
Messaging still does not send from within the app but quick reply is fine (I use Textra SMS and everything works in it)
If there's anything else you want me to check just say the word. I wonder if it's a cache issue with the dialer or something causing the phone to misbehave, but it seems to be working fine now.
dopy25 said:
Give today's build a shot. I just made about 10 phone calls to various numbers from various locations within the dialer and all connected the first time, and disconnected fine.
There is still no data toggle, but data is now being tracked (or at least showing that it was previously tracked) I also do not see any apn settings but that might not have been an update for our device that I saw.
Messaging still does not send from within the app but quick reply is fine (I use Textra SMS and everything works in it)
If there's anything else you want me to check just say the word. I wonder if it's a cache issue with the dialer or something causing the phone to misbehave, but it seems to be working fine now.
Click to expand...
Click to collapse
That's one down. Like I said, I love this ROM. The camera is AMAZING. I'll test it and see what happens.
Hi all
I have been using this phone for a month, and I have experienced a lot of different small issues, I hope someone may have solution to them.
Phone:
Mi A2 Lite, rooted (Magisk) Android one pie, January update. Has a screen protector.
Apps:
Here are some apps that I think may cause the issue that I mention below, these apps are Nova and datally. Really can't think of a third one, I don't use any cleaning app or battery performance app.
Issue:
1. Typing experience is horrible. Using stock google input, the keyboard is not very sensitive and accurate. The letter just can't be recognized even though I am sure I have pressed the key and pressed the right key. So my typing is really slow, the key doesn't display immediately (it does seem to have a delay), and for some reason I always type wrong and missing some letters, so gotta use backspace a lot.
2. It always wakes up randomly in my pocket, so I may take the phone out with torch on and airplane mode on without my awareness.
3. When I am on a call, I can accidentally press some random on screen keys.
4. The background apps AWALYS get killed, even though I have turned the battery optimization off globally, and the individual apps that I never want to be killed.
5. Messaging service apps have huge delay when delivering the notification. It may only show when I open the app. Used PNF app but couldn't fix the problem.
Does anyone have the same issue and know the fix?
I hope it is only the software problem (Pie system) and maybe I can fix it by flashing a better rom, but I don't seem to find a stable official custom ROM for Mi A2 Lite (even lineage OS is unofficial)
Many thanks
luckyvictor said:
Hi all
I have been using this phone for a month, and I have experienced a lot of different small issues, I hope someone may have solution to them.
Phone:
Mi A2 Lite, rooted (Magisk) Android one pie, January update. Has a screen protector.
Apps:
Here are some apps that I think may cause the issue that I mention below, these apps are Nova and datally. Really can't think of a third one, I don't use any cleaning app or battery performance app.
Issue:
1. Typing experience is horrible. Using stock google input, the keyboard is not very sensitive and accurate. The letter just can't be recognized even though I am sure I have pressed the key and pressed the right key. So my typing is really slow, the key doesn't display immediately (it does seem to have a delay), and for some reason I always type wrong and missing some letters, so gotta use backspace a lot.
2. It always wakes up randomly in my pocket, so I may take the phone out with torch on and airplane mode on without my awareness.
3. When I am on a call, I can accidentally press some random on screen keys.
4. The background apps AWALYS get killed, even though I have turned the battery optimization off globally, and the individual apps that I never want to be killed.
5. Messaging service apps have huge delay when delivering the notification. It may only show when I open the app. Used PNF app but couldn't fix the problem.
Does anyone have the same issue and know the fix?
I hope it is only the software problem (Pie system) and maybe I can fix it by flashing a better rom, but I don't seem to find a stable official custom ROM for Mi A2 Lite (even lineage OS is unofficial)
Many thanks
Click to expand...
Click to collapse
Try to update I never had any of those issues
I have also these problems. I have February update.
madmanwild said:
I have also these problems. I have February update.
Click to expand...
Click to collapse
Do you have all these problems? or just one or two? After seeing my configuration/apps that I installed, do you think is it app related or system related?
rob420p said:
Try to update I never had any of those issues
Click to expand...
Click to collapse
not even one of these? Your background app never get killed?
Are you using Stock Android One? did you root your phone?
luckyvictor said:
Do you have all these problems? or just one or two? After seeing my configuration/apps that I installed, do you think is it app related or system related?
Click to expand...
Click to collapse
all these problems without wakes up in pocket. killing the background application is the biggest problem for me (I use a lot of smart home app- eWelink,Room Heat,Magic Home) and it's horrible. ewelink starts 5sec after kill, Room Heat - frequent crash like a white screen...
the next problem is huge delay when delivering the notification....
I am on Stock Android One-February update,I'm allowed only cam2api...
madmanwild said:
all these problems without wakes up in pocket. killing the background application is the biggest problem for me (I use a lot of smart home app- eWelink,Room Heat,Magic Home) and it's horrible. ewelink starts 5sec after kill, Room Heat - frequent crash like a white screen...
the next problem is huge delay when delivering the notification....
I am on Stock Android One-February update,I'm allowed only cam2api...
Click to expand...
Click to collapse
You have battery optimization off? any battery improvement app? I think all these is because the 'intelligence' in Android is playing up, it doesn't understand exactly how we use the app. However, even have it turned off, the problem exists....
luckyvictor said:
not even one of these? Your background app never get killed?
Are you using Stock Android One? did you root your phone?
Click to expand...
Click to collapse
I am on stock but I do have root.havent done much modification yet waiting for twrp
rob420p said:
I am on stock but I do have root.havent done much modification yet waiting for twrp
Click to expand...
Click to collapse
Don't understand why there is such different, did you have battery optimisation off and all time since the first day you use the device?
luckyvictor said:
Don't understand why there is such different, did you have battery optimisation off and all time since the first day you use the device?
Click to expand...
Click to collapse
Honestly I don't think so I really haven't messed with the battery besides putting a %
luckyvictor said:
You have battery optimization off? any battery improvement app? I think all these is because the 'intelligence' in Android is playing up, it doesn't understand exactly how we use the app. However, even have it turned off, the problem exists....
Click to expand...
Click to collapse
Yes, all off - battery adaptation and manually set no optimization on my app...
Dt2w works fine for the first few minutes after locking phone but after that, it requires 7-8 taps to wake up. Anyone else experiencing this? Im using xiaomi.eu 12.5 stable.
ApexPrime said:
Dt2w works fine for the first few minutes after locking phone but after that, it requires 7-8 taps to wake up. Anyone else experiencing this? Im using xiaomi.eu 12.5 stable.
Click to expand...
Click to collapse
I'm on the weekly and I also have this issue. Not 7-8, but I have to tap twice. Like 2 taps then 2 taps again. Happens sometimes.
all good on ArrowOS, DT2W and sleep working great... i know it's possibly not what ur looking for... but it's a seriously good rom.
ApexPrime said:
Dt2w works fine for the first few minutes after locking phone but after that, it requires 7-8 taps to wake up. Anyone else experiencing this? Im using xiaomi.eu 12.5 stable.
Click to expand...
Click to collapse
Yes, this happens also for me
I'd assume this would also be an issue on the Global rom?
If so, we can bring it to Poco's attention via Poco community forum.
Otherwise, we'd have to bring it to Xiaomi's attention on the Mi community forum.
I noticed this too but for me it’s the very slight movement between taps where it presumes a gesture is upcoming. It also seems a little worse with a slippery tempered glass protector.
If I make a conscious effort not to move position between taps it works for me every time. Maybe they can adjust swipe detection sensitivity?
festor said:
I noticed this too but for me it’s the very slight movement between taps where it presumes a gesture is upcoming. It also seems a little worse with a slippery tempered glass protector.
If I make a conscious effort not to move position between taps it works for me every time. Maybe they can adjust swipe detection sensitivity?
Click to expand...
Click to collapse
this any good? or there's others if you search playstore....
this one maybe
(as a possible temporary solution, i mean)
EDIT: sorry, i read ur post as a touch sensitivity issue. have re-read, don't think those apps are of much use
Interestingly, don't have problems with double tap to wake, it works always, only with tapping for always on display to quick check time or notifications. Works 1 in 10 times. It's funny, tap, nothing, double tap ok.
Morak75 said:
I'm on the weekly and I also have this issue. Not 7-8, but I have to tap twice. Like 2 taps then 2 taps again. Happens sometimes.
Click to expand...
Click to collapse
same issue
Same issue, probably the biggest annoyance for me since I'm almost unable to use 10 second AOD tapping to conserve standby power.
Any power management active?... destroyer of worlds.
Try clearing system cache, and a hard reboot.
Try altering AOD settings or clearing apk data.
Maybe a firmware glitch... they happen.
blackhawk said:
Any power management active?... destroyer of worlds.
Try clearing system cache, and a hard reboot.
Try altering AOD settings or clearing apk data.
Maybe a firmware glitch... they happen.
Click to expand...
Click to collapse
Already done this to fix my drain problem one day one of receiving the device.
I know Android is just like any other OS installed on a computer sometimes needs clearing of cache, a shutdown of the OS or a manual reboot.
In fact I've done it many times just to make sure MIUI is not glitching on me.
Nemix77 said:
Already done this to fix my drain problem one day one of receiving the device.
I know Android is just like any other OS installed on a computer sometimes needs clearing of cache, a shutdown of the OS or a manual reboot.
In fact I've done it many times just to make sure MIUI is not glitching on me.
Click to expand...
Click to collapse
You be amazed how many have no clue or just don't think using of it.
It may be a settings glitch or again some sort of power management running amuck in the background. Play with it...
I posted the issue on Mi Community and Poco Community forum.
Not many people seem to use the double tab to wake feature with AOD set to 10 seconds.
I tried searching on Xiaomi and Poco both forums with keyword double tap and not a single thread for the Poco F3/Redmi K40.
festor said:
I noticed this too but for me it’s the very slight movement between taps where it presumes a gesture is upcoming. It also seems a little worse with a slippery tempered glass protector.
If I make a conscious effort not to move position between taps it works for me every time. Maybe they can adjust swipe detection sensitivity?
Click to expand...
Click to collapse
I think youre right bro. If i time my taps perfectly and dont move position between taps, it works most of the time. Same goes for the AOD. Single tap works but it takes almost 2 seconds for the AOD to pop up which is pretty slow imo.
I think figured it out, 3 fast taps without moving my finger always works with AOD now.
Whatever, I'll just leave the posts on the Mi and Poco forum...hopefully they can replicate the issue and improve single/double/triple tap detection with future updates.
Nemix77 said:
I think figured it out, 3 fast taps without moving my finger always works with AOD now.
Whatever, I'll just leave the posts on the Mi and Poco forum...hopefully they can replicate the issue and improve single/double/triple tap detection with future updates.
Click to expand...
Click to collapse
Bro did you try single tapping and waiting for ~2 seconds?
Everything magically works now, after I let the battery deplete to 0% (MIUI auto shutdown) for a second time and then charge to 100% (for initial battery calibration).
Of course I won't be letting the battery deplete past 20% anymore after this, and I'll only be charging up to 90% when I have the phone rooted.
I'm pretty sure there some other minor issues with MIUI I haven't encountered yet, but for now it's pretty enjoyable to use.
Nemix77 said:
Everything magically works now, after I let the battery deplete to 0% (MIUI auto shutdown) for a second time and then charge to 100% (for initial battery calibration).
Of course I won't be letting the battery deplete past 20% anymore after this, and I'll only be charging up to 90% when I have the phone rooted.
I'm pretty sure there some other minor issues with MIUI I haven't encountered yet, but for now it's pretty enjoyable to use.
Click to expand...
Click to collapse
One question, double tap to wake drains battery on Amoled screens? read somewhere that it was a function for LCD displays
colosocool said:
One question, double tap to wake drains battery on Amoled screens? read somewhere that it was a function for LCD displays
Click to expand...
Click to collapse
Might depend on the device. Doesn't use much at all on my Samsung Note 10+.
With AOD touch to view active and phone/text running I use less than .5% @HR.
Never tried deactivating Double Tap on though... it's too useful.
More than likely it's not the culprit. Cloud apps and trashware like WhatsApp, FB, Google system apks are prime suspects.
Easy enough to test...