Related
PLEASE NOTE THE FOLLOWING:
This is BETA code. Some things do not work and you should assume there will be BUGS. I am not responsible if you brick your phone with this or any other firmware. You are your own warranty once you start loading firmware. Please do NOT post about anything that's in the "broken" list; I will ignore you if you do.
If it's not listed as working or broken below then that particular feature has likely not been tested at all.
Kernel: Mine, built from Motorola's released source. Includes Smartassv2 governor and ext2, ext3 and ext4 filesystems plus MSS clamping support.
Codebase and credits: Originally sync'd from Isaac's work, heavily modified at this point. Isaac deserves the credit for getting the base code to boot and getting me interested in hacking on it.
What's working
Pretty much everything, except what's listed below.
What's known BROKEN:
Hdmi non-functional
The is an interrupt storm if you enable both Wifi and Bluetooth at the same time. Don't.
Front camera does not mirror snapshots or video, but does on preview.
Occasional force-closes when switching cameras front-to-back.
What's Intermittent: Nothing.
Included Apps:
Essentially nothing. Load GAPPS for Google apps (yes, you want them) by flashing these AFTER you flash the ROM:
http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip - Base Google Apps
http://goo-inside.me/gapps/gapps-gb-20110828-newtalk-signed.zip - Google Talk (if you want it)
NOTE: You cannot provision on the CM7 ROM (the "Activate" apk, if you grab it from the Triumph, will not work - it appears to run, but does not function.) You must be provisioned using the stock ROM before you load this code. I am attempting to fix that, but am not confident it can be fixed as it appears to want things in the framework that I have no way to discover or duplicate.
To install:
1. MAKE A NANDROID BACKUP! I cannot emphasize this enough - and make sure you keep that backup somewhere SAFE. Most notably there is no way to activate the phone on CM7 at this time, and there may never be. If you need to change your phone number or similar you need to swap back to stock firmware. If you lose the ability to do that you will be pissed. Consider yourself warned.
2. Place the file in the below post on your SD card in the root.
3. Boot to clockwork by turning your phone off and then hold BOTH volume buttons while pressing POWER. Release power when the phone vibrates and continue to hold both volume rockers until Clockwork comes up.
4. Important: Clear the cache and data ("factory reset") If you fail to do this CM7 will blow up on boot unless you are coming from previous RECENT build. You've been warned! If you're coming from an OLD build (or stock) format /system as well.
5. Select the ZIP file from the SD card (about halfway down on the top screen of Clockwork to get to that menu, then the first entry and point at it.)
6. Commit the update.
7. If you formatted /system (and if you're coming from STOCK) flash GAPPS (below; the first is the standard GAPPS apps, the second is Google Talk) using the same procedure in #5 and #6.
On first boot it will take about 2 minutes before it comes up; if you have lots of apps it may take longer. Provided you see the little CM7 guy with the rotating arrow, it's working - be patient.
Current code download link(s)
11/19 - vB.08 http://www.mediafire.com/?bhmitbx7weqf8g2 - Wifi Tethering / FINAL
11/06 - vB.07 http://www.mediafire.com/?eqdfo7ktmtuq281 - Haptic soft keys / light sensor
10/30 - vB.06 http://www.mediafire.com/?qj28ip6o09j1ai6 - Screenshot / restore GB Launcher
10/29 - vB.05 http://www.mediafire.com/?rjf20vb74oc0irb - Cleanup release; see below
10/26: http://www.mediafire.com/download.php?wwj1l5lzjb4glfy - Wifi/PRL/Prox Sensor
10/22: http://www.mediafire.com/download.php?nssofns6sljfj33 - CIFS/Prox Sensor/USB Tether
10/16: http://www.mediafire.com/?jg5matblx1d7bq2 - First BETA
10/12: http://www.mediafire.com/download.php?wtwvx80ccsz8vfi - Last ALPHA build
Note: Loading this version requires a Clockwork that understands ext4. The following version is recommended: http://www.mediafire.com/download.php?acpcd9xtlpzqge1
Expected to be fixed in the NEXT build -
Work continues on the list in the first post along with tracking bugs that have been posted to GitHub.
Change Log (tracking as of 9/5), reverse chronological order:
11/19:
Wifi tethering is now built into the code (from Isaac's work); untested other than the fact that it does come up and is believed working. No other changes. FINAL RELEASE.
11/06:
Haptic feedback on soft keyboard now works and is treated as any other "virtual key" off the screen. Kernel modified to multiply light sensor readings by 30; this "sorta" aligns them with actual lux values (not really, but I don't have a light box that can get me a closer integration formula) and makes possible the CM7 options for "jump" settings, hysteresis and such to work as designed. No other material changes against b.06.
10/30:
Screenshot from power menu fixed and Gingerbread default launcher restored.
10/29:
Cleanup release. 2.3.7 codebase merge with CM7 upstream completed. "99memory" file added - see the notes below for how to tune this if you want to. Significant change to power management was made in the kernel; if you have Wifi turned off the phone will enter deep sleep, but if it's loaded then the sleep state is held at one level higher to prevent Wifi lockups. Note that data, when active, is a major power pig, even if nothing appears to be using it. It looks like Sprint has some "keep alive" processing going on either at the network level or in the actual CDMA driver code (which we don't have) that plays hell with power consumption. In short, with a data connection up I can't get materially under 30ma when idle and it's either the carrier or the CDMA radio code doing it - either way, I have no way to change it as there's no source to the chipset code available. Juice Defender, assuming Wifi is off, does a amazingly excellent job in conjunction with this release in shutting down the data connection and "waking it" once every 15 minutes or so to check for new notifications. It makes a huge difference in power burn with the phone in your pocket. You decide if its worth losing "instant" data notifies. I noted the same battery behavior on stock (Froyo) when I first got this phone, so my best guess is that this is in the radio firmware itself. Last alpha release pulled.
10/26:
Wifi wakelock problem is fixed. PRL now comes out of the radio and proximity sensor has more changes made. Note that the prox sensor may "flash" if you put the phone to your head before the call connects (before the "vibrate" after you dial); it should stop as soon as the phone goes into the "active" state.
10/22:
CIFS support via kernel loadable (.ko); NOT loaded by default as its very large. You can enable this in the startup scripts if you want it. USB tethering fixed. Proximity sensor "blinking" fixed. Various other minor changes as well.
10/16:
Data drop detection/correct code added. Front camera options that were unsupported in the hardware (and which could cause lockups) removed. Memory management changes made to improve performance. Soft keypad now PWM controlled (change levels under the CM7 options if you don't like my defaults) and other cleanup. Note: This release was early as there's a problem with some of the dependencies in the GIT servers, and as such I could not do a clean "verify builds from zero" run. Note that front camera mirror mode is enabled for preview but is NOT on snapshots and taken videos; this is being investigated as the mirroring should be on but doesn't work when the actual picture is taken.
10/12:
GAPPS removed from base build, front camera fixes complete, rear camera will now video record in HD. Tunneling support now internal to the kernel (no longer requires a loadable) for VPN users. Previous versions REMOVED.
10/2:
Partial front camera support is now available. The camera functions properly in video calling software such as Skype. Note that the "hacked" Froyo-capable Skype does not work properly; the one in the market, however, does. Other video calling applications may work but have not been tested. The Camera application itself will display the preview on the front camera but it is flipped 180 degrees (top to bottom), attempting to switch to video mode force-closes and a snapshot attempt hangs. Don't do that, basically. These are on the list to be fixed but progress is slow due to the very hacksterish way I had to implement the camera (no thanks to Motorola on that with no source access.) Kernel has the smartassv2 governor available for those who wish it and the build tree was synced up from CM7 to incorporate their fixes and updates.
9/25
Bluetooth tethering and MSS clamping implemented. Bluetooth tether is native; the MSS clamping, if recognized by other tethering applications (e.g. wireless tether) will also function to get rid of the need to set the client's MTU.
9/21
GPS now functional
9/10 morning:
Compass/geomagnetic sensors now working properly
Lights code now honors CM7's customization screens
9/5 morning build:
Market problems with apps not showing up repaired.
To file a BUG report
Use the Bugtracker Git at https://github.com/ikarosdev/CM7_Triumph_bug_tracker/issues?sort=created&direction=desc&state=open
Filing a new bug will require that you set up a login ID on Github if you don't have one. Please note that bugs reported in this thread (as opposed to discussion, which is always welcome) may or may not be noticed and tracked; if you care about whatever you're reporting, please use the GITHub system. Bugs filed on Github must include steps to re-create the problem if you're able to do so and if you can obtain one, a logcat or other trace is very helpful. You can also look at the above link to see what issues are open (please do not duplicate already-reported bugs, although if you have comments on them adding them is fine) as well as what has bene closed which may be of interest if you're looking for what is likely to show up in the next code turn.
Notes
Do NOT tamper with the following lines in build.prop:
ro.telephony.ril_nid=97
ro.telephony.ril_prl=1115
ro.telephony.ril_class=Triumph
ro.ril.def.preferred.network=4
ro.telephony.default_network=4
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
If you do there is a high probability that the radio will break. In particular the ril_class is required to deal with the oddities in the Qualcomm radio code. If you are running a different PRL you can change the prl line but it should remain present.
If you are updating from previous releases and have problems format the /system partition before you load the update. You should not need to format the data partition ("factory reset") and reload your applications, but no promises can be made at this point in development.
Custom backlight options (Settings->Cyanogen Mod->Display->Automatic Backlight) are available; you can change the behavior of the LCD backlight, including thresholds and illumination settings, the number of steps, whether averaging is used, whether hysteresis is operational and whether the button backlight is on or off as desired. Please note that unlike many devices the sensor value returned to the code is not in "lux"; it is a raw value and tops out in full sunlight somewhere under 100, with "0" being a fairly dim (but not dark) room. The default table I have loaded has the button backlight OFF for very dim ambient conditions (I like to use the phone as an alarm clock and want the buttons off at night), ON for low-but-present ambient conditions, and then OFF again (power saving) for ambient light high enough that the backlight has no real purpose. You may change this to suit yourself and your desires; some people will want the buttons on for zero-ambient conditions.
Note: As of 9/24 this load is using the "ext4" filesystem. Alternative kernels must support both that filesystem and the options CONFIG_NETFILTER_XT_TARGET_TCPMSS and CONFIG_IP_NF_MANGLE. If they do not MSS clamping will not function. If ext4 is not supported the kernel will not boot.
3g/1x data lock
If you are in a place that often switches down to 1xRTT for data due to questionable signal levels it is possible to lock the RIL to 3g mode. Note that doing so means you either get 3g speed or nothing. You need to access the "Phone Info" menu to do this using either AnyCut (from the market) or from the "Battery Monitor" Widget (go to "Tests" in the selected screen from there.) Note, however, that doing so (1) will not survive a reboot and (2) disables SMS/MMS and inbound phone calls during the time it is active. SMS/MMS will come through if you make a phone call but the EVDO-only mode for data blocks something in the radio that is required to receive and send SMS messages and the notifications of an inbound call. Since this "mode change" is actually a request to the radio ROM (which we do not have source for) this probably can't be worked around. However, I am looking into what this mode select does in the hope of being able to detect the 1x switch (which I can easily do with the existing RIL support code) and temporarily force a 3g switchback - which may or may not be highly-disruptive to data transport (if it is it's not worth doing at all, but if not...)
Note: There is an apparent memory leak in the base CM7 code somewhere. This is the cause of sensor slowdown (e.g. rotation is not immediately recognized) as the system becomes memory-constrained and ultimately will fault and reboot. I do not have isolation of this problem as of yet and have no reasonable expectation on when or if I may; for the time being I recommend a reboot on a daily basis to avoid the worst of these effects. The impact becomes particularly-severe if you use things like CoPilot that require large working sets of RAM. My instrumentation leads me to believe the problem is not in the kernel nor in the user application side of the system, but rather is in the base CM7 load. Investigation continues.
A note on overclocked kernels:
I will not be supporting these in my builds. They work, and some people want them. Isaac has built one that can (theoretically) go to 1.9Ghz.
Here's the issue in a nutshell: It's pretty easy to exceed thermal limits in a CPU doing this, and if you do, the best thing that happens is that the device becomes unstable and reboots. The worst thing that can happen is that the internal junctions in the CPU can be damaged or even destroyed. This damage is not always immediately apparent and can in fact be cumulative.
I understand some people want to overclock, but nobody really knows where "the wall" in this regard, and if you find it you're going to be very unhappy. As such if you want to have fun of this sort you'll need to load your own overclocked kernel over what I build. I respect those who are willing to take the risk but I just don't see the potential reward as being worthwhile and I don't want to be the guy that hands you a build that smokes the CPU in your phone.
Sweet man, keep up the good work! CM7 is gonna be great on the triumph.
Market fix in the latest build - please update.
Just flashed the updated ROM and so far so good. As long as the calls come through then I can wait for a full port. Thanks for your hard work =)
And on a side note, it seems like I'm getting better reception after I flashed this. (-85dBm vs ~ -95dBm to -105dBm)
The two big problems are the GPS and MMS. The MMS is a matter of hacking and time (Virgin's MMS is... odd...), the GPS is pissing me off. Again a lack of documentation strikes; it appears there's a versioning problem with the RPC stuff and the chipset and driver in question do not expose the NMEA port (which sucks.)
Awesome work!
Here is a random question. Does that lock/unlock flickering issue go away with this? What about the sometimes unresponsive back capacitive key?
Sent from my MOTWX435KT using XDA App
The auto-brightness code was completely re-implemented (by me); it's DIFFERENT in its behavior, but I like how it behaves.
I haven't had a back key problem with either this rom or the original....
HDMI bug report
I'm just trying to help out. HDMI out does not seem to be working just wanted to report this minor bug. Overall I'm loving this rom. Great job.
Great work Genesis!
Sent from my NookColor using xda premium
Anyone experiencing issues with data?
Seems like my data is intermittent and goes in and out randomly. I still see the 3G icon (and the signal status) but it goes white (no Google services) and I have no data access.
Yeah I've been losing data. Easiest fix is to turn on airplane mode on the off. Should come back on.
I've also noticed that email 2.3 keeps force closing. Got around this buy restoring email 2.2 with titanium backup.
stock video player bug
When playing videos with the stock video player the video comes out slightly glitchy. The same thing happens with YouTube videos.
I have not noticed the problem when watching flash videos or using arc media video player (have not had a chance to test others)
Love the ability to use the different themes with theme Chooser.
Agai appreciate all the hard work. Can't wait for a custom kernel
my review
ok i would like to start this off by saying that i love you for all the work you have done, you and Isaac. this is not asking you to fix anything this is just my first impressions after using this rom for two days.
*market: i believe this was already addressed in the original post of this rom. i updated market to the newest version and ever sense it has been force closing at random times. it still works to download things and browse but it will randomly force close.
*battery life has greatly decreased since i flashed cm7. even with juice defender pro it was still a much shorter life span.
*screen auto brightness: this has already been addressed i know but i am trying to do a very in depth review. it takes a while after i turn the screen on for it to brighten up enough to be clearly visible. another thing i just recently noticed was that while i was in a call and holding the phone up to my ear, the screen would repeatedly turn on and off. i believe this may have been the way i was holding the phone but it happened more than once so this is why i thought to address it.
*head set volume dropping issue. i have addressed this in a previous thread as a fix. i was hoping this would be fixed in cm7 but it must be a deep hardware issue. what happens is, when you are listening to music through the headset port and a text comes in, the phone will ring and then the music will come back on but at a significantly lower volume. the only way i have found to bring the volume back up is to make a call and then play your music again.
*music and calling: i have noticed that if you answer a call and have music playing, when you hang up the music will stay paused. i dont know if this can be fixed but i thought i would just throw it out there.
*wifi will work untill the screen goes off. the phone will not rewake and you will have to do a batt pull.
*swype fails hard. with froyo swype worked just fine but now it has very bad lag and doesnt even register when im swyiping sometimes. this is not that big of an issue because i use swype as personal preference.
*wifi wireless teather for root users. this works now! only with google web pages -_-
*mms: wont work at all. just a heads up though you can go to message settings and switch it to split messages so you can send longer messages.
as of now this is all i have but i will update this if i come up with more. as i said before i am not trying to nag you at all i just want to get my views out there and hopefully help with feature development of cm7 for the triumph.
keep up the great work guys! i cant thank you enough.
1. Market - if you loaded over the first load, you need to format /system before you do that. You've got pieces of old things laying around.
2. Battery - it's wrong (charge state) until you fully cycle it. I'm getting battery life roughly equal to the stock load (and I am off-charge a LOT)
3. Auto-brightness - This will be adjustable in the next load - the issue is that the phone turns in with the screen in the "dimmed" state and there's a smoothing period before it reacts. You can set that with the next load to make it behave however you'd like (defaults are close to, but not identical to, how it behaves now.)
4. Headset. I think this is a hardware problem.
5. Music and calling: This is a common issue with Android; when the output and input sources get reassigned the current stream is interrupted. Same thing happens if you're on speakers and plug in a headset. I doubt it's fixable (I know why it happens, but preventing the switching task from throwing the exception upstream could have extremely bad results - I'll look at it at a later date, but this is common to a LOT of Android devices.)
6. Wifi is a documented issue.
7. Swype works fine. Download the CURRENT beta. If you're using a hacked version, all bets are off. I use Swype exclusively for my keyboard on this ROM. Ditto if you're trying to sideload it from somewhere (e.g. restore from Titanium) - don't do that.
8. MMS: Documented as broken.
The thread over on Androidforums is more current than the one here, but I will endeavor to at least mirror MAJOR updates here.
richiehd said:
Here is a random question. Does that lock/unlock flickering issue go away with this? What about the sometimes unresponsive back capacitive key?
Sent from my MOTWX435KT using XDA App
Click to expand...
Click to collapse
Yes, that was something I found with CM7. The screen flickering issue is not present. YMMV.
platypuss94 said:
* another thing i just recently noticed was that while i was in a call and holding the phone up to my ear, the screen would repeatedly turn on and off. i believe this may have been the way i was holding the phone but it happened more than once so this is why i thought to address it.
Click to expand...
Click to collapse
on this note i will say it is in fact how you hold the phone. it happens to me all the time on my stock triumph. no big deal and nothing to worry about. but thank you for saying something about it none the less.
Hi there fellow robot lovers (or killers as it may be) !
Before we start, both identical phones (public mobile zte n762), both rooted, both booting normallish, meaning they get to keyguard screen, apps are starting, messages coming in, etc. Only one is activated, which would be the one with the broken screen, which boots fine, the touch membrane works, it's just the screen only displays pure white light, from total dark to overbright (meaning brighter than full brightness)
What I want from this one is an up to date backup that I might flash on the other one when its softish brick status is resolved.
Then, I can think of hacking the hardware itself, as in changing screen.
Goal for this one is to get a full backup so I can then mess around with it. Or if someone knows that the screen is not dead, since it does light up, I'm all ears on way to play with it. After a backup.
For the little history : I dropped my activated phone while trying to figure out the problem with the other one, to my great dismay and no immediate hilarity I had been running it for more than 4 months with a nasty crack on the screen, and it seems the dropping from a foot high the other night was the shock that sent it over the top.
Now it seems this can also be caused by software glitches ? aka White Screen Of Death
Now, the soft brick phone, which I got for nothing before it was thrown to the garbage (supposedly defective, it was just very barebones, and missing its sdcard)
Now, why do I say very softly bricked ? Well, it works, fully boots, and I sometimes manage to get a glimpse of the running OS "behind" the boot anim when I let if fully boot.
It's running a varianf of the Warp Cream sandwich rom for the n762, called Ice Cream Sandwich 420
It's like the boot anim is looping as an overlay over the running OS. Even managed to get Text+ in the foreground yesterday and chat with a buddy for a while.
Now, why didn't I just wipe it and reinstall ? For one, I thought [ I had no copy of the rom, just a cwm recovery backup once it started acting up.
Mostly, because the challenge in getting it (both phones if it so happens the screen on the other one can be brought back to normal operation) back to glorified PDA status without wiping it, as that's a bit like the good ole, reinstall DOS/Windows/etc. tech support level 1 answer, isn't it ?
So what options exist for soft brick to resume normal activities without wiping the whole thing ?
What could lead to the custom boot anim playing as an overlay to the OS ?
All ears and eyes on your suggestions, shouldn't be that hard for someone who knows, as I have read quite a bit of information that doesn't agree with each other...
anything in italic is edit(s)
After installing Lollipop, everything became unbearably slow. I've tried flashing multiple ROMs, both Lollipop and Kitkat, but everything remains so slow: the actual boot-up process and the ROM itself. Does anybody have any ideas about what can be done about this? In fastboot I see hammerhead D820(H) 32GB; HW version rev_11; Bootloader version HHZ12d, Baseband M8974A-2.0.50.2.22. Lock state is unlocked. Any suggestions will be highly appreciated!
Wipe cache and see if that helps and disable Chrome's integration into the app switcher. Also get rid of Facebook and FB Messenger.
Sent from my Nexus 5 using XDA Free mobile app
Instead of Lollypop try some LSD
Thanks. But it is that slow even before any of these apps are loaded (e.g. after I do a factory reset and flash a new rom). Is it possible that Lollipop did sthg to the hardware? If so, how could I find out? Just to give you an idea about how slow exactly it is: when I am typing 5 letters at normal speed, it takes until the fifth letter before the first letter actually displays on the screen. I should also note that when the screen goes off, I can no longer get it on again without a reboot...
I'm still trying to figure out what this might be. I first thought my problems were similar to those that others have described, but I now think they be different. Here are some of the issues I'm encountering:
when I boot up the phone (whether in kitkat or lollipop), the initial android (animation sequence is already incredibly slow
there are all sorts of strange things happening with my screen. When it goes to sleep in Android, I can not wake it up anymore. When it goes to sleep in recovery, and I push the power button, the screen goes (again after some time) from pitch dark to a slightly 'lit' dark, but it never displays anything, and I have to reboot again to get the info on the screen. Also, the screen is even slow in twrp - when I swipe to do a factory reset, for instance, there is also a noticeable lag.
I have tried with various ROMs (both stock and not); with ART and Dalvik, etc. but none of these changes seem to affect the slow screen issues
Does anybody have any ideas about what the problem might be? I should also add that we had the screen replaced a few months ago - could that have something to do with it?
sdspieg said:
I'm still trying to figure out what this might be. I first thought my problems were similar to those that others have described, but I now think they be different. Here are some of the issues I'm encountering:
when I boot up the phone (whether in kitkat or lollipop), the initial android (animation sequence is already incredibly slow
there are all sorts of strange things happening with my screen. When it goes to sleep in Android, I can not wake it up anymore. When it goes to sleep in recovery, and I push the power button, the screen goes (again after some time) from pitch dark to a slightly 'lit' dark, but it never displays anything, and I have to reboot again to get the info on the screen. Also, the screen is even slow in twrp - when I swipe to do a factory reset, for instance, there is also a noticeable lag.
I have tried with various ROMs (both stock and not); with ART and Dalvik, etc. but none of these changes seem to affect the slow screen issues
Does anybody have any ideas about what the problem might be? I should also add that we had the screen replaced a few months ago - could that have something to do with it?
Click to expand...
Click to collapse
Probably the replacement screen has been reconnected poorly. There's nothing you can do on software side, for me, it's more like a hardware problem.
I'm having this problem with my NEW mi note 10 phone.
I notice it when first when I'm typing on my keyboard as usual speed.
It kept doing this phantom swipe across two finger taps.
I posted some videos to illustrate my problem.
Is it a software or hardware problem? (This problem is intermittent as well so it's really hard to pinpoint it)
ttps://drive.google.com/file/d/1-QMHaYYpsEizVRpPHqPvzx-E2hUMa0ur/view?usp=sharing(Using keyboard)
ttps://drive.google.com/file/d/1-6M1e33Qxz8HXckkcLb3sWVTXG6fPHzv/view?usp=sharing (Using touchscreen tester, you can clearly see the phantom swipe across the two taps)
Anyone else having this problem except for me?
When this problem comes, I can't even properly play a game.
reformat factory reset - fail
reinstall latest miui global 11.1. 2 - fail
optimise animation all off - fail
gboard - fail
xiaomi keyboard - fail
SwiftKey - fail
turn off Miui optimization - fail
restart phone - fail
clear ram, clear cache, clear recent, speed boast - fail
CPU slowing down due to background processes?
Touch digitalizer got problem? (I tried shaking it gently, poking it but it does not affect anything at all)
As I said, this problem is intermittent. There are times when I can use it without any problems at all.
It's really weird.
It can be totally fine one moment and then it acts up again.
There's another thread about this. Most of us face this issue on all variants of the phone (Pro/Lite). This started with April or May update where Mi added a edge sensitivity control setting.
What happens here is that touch sensitivity suddenly reduces and it will be hard to do anything that involves rapid touch such as typing.
Lock and unlocking the screen or restarting the phone will fix this temporarily. There's no permanent solution.
Also when this issue occurs again, go to the settings and turn on Game Turbo for an app such as WhatsApp, without and then try typing on WhatsApp, you will see that the issue is gone.
We all are waiting for Mi to fix this. But I would advice to return the phone if it's under warranty though this is a software issue
Android 10
Release date: Sunday, Aug 9th, 2020
Build Version: QKQ1.191002.002.V11.0.9.0.QDLMIXM
Kernel Version: 3.18.124-perf-gceec2f0
Bootloader Version: MSM8953_DAISY2.0_20200805174034
Baseband Version: 953_GEN_PACK-1.202044.1.240106.1,953_GEN_PACK-1.202044.1.240106.1
Android Security Patch Version: 1 July 2020
Please report bugs via Xiaomi's Feedback app.
How to Generate Bug Reports
Bugs:
1- [email protected] fps Video Recorder doesnt work on OmniVision OV12A10 Back Camera sensor. (Tap here for more info)
2- We still cant turn off Settings app suggestions.
3- Direct share feature doesnt work. It gives an error:
"Direct share is not available"
4- Multiple users experiencing installation problems. Source-1 Source-2
5- Sim card menu is still not adapted to the dark mode, it persists to be white while global theme is dark. Source 1 - Source 2 (Same as v11.0.5)
6- Splitscreen feature doesnt let us to fit video.
7- Ram management is still bad. When i switch to YouTube app from Firefox (with 1 page) LMK kills Firefox app from memory. It even restarts second Firefox page when i trying to select image file via default file manager.
8- I am experiencing a lot of glitches (most likely screen tearing) while scrolling with Firefox.
9- Some app services stucks on Restart state.
- diaglogger
- com.qualcomm.qti.workloadclassifier
- Simcontacts
- CallEnhancement
- com.qualcomm.atfwd
Reboot fixes all. Maybe these apps causes sluggishness. Maybe these apps Xiaomi's little secret. We dont know yet.
10- Still requires daily reboot to maintain its performance. If we dont device becomes sluggish.
Missing features:
N/A
Enhancements:
1- Fourth Stable Android 10 release.
2- It comes with July 2020 Android Security patch.
Battery Life:
N/A
Notes:
- This is the fourth stable Android 10 update for Xiaomi Mi A2 Lite.
- There was June 2020 Security patch in the third stable Android 10 update.
- Arrived 47 days later after v11.0.7
- It weights 180 MB for OTA.
- Xiaomi didnt updated the modem and gpu drivers(gpu driver is same -OpenGL ES 3.2 [email protected] ([email protected], Ieeb4a86f7b, 1573670678) (Date:11/13/19)- since first build) in this build so dont expect something new.
3DMark Test Results: (v2.0.4661)
Slingshot Extreme OpenGL ES 3.1 - Overall score 463
Slingshot Extreme Vulkan - Overall score 515
It will be beneficial to restart your phone after the first installation.
Older builds:
1 - Android 10 v11.0.4
2- Android 10 v11.0.5
3- Android 10 v11.0.7
I will constantly update this thread.
First of all, I changed my logic in which I do this updates. Last month I had my one and only random system reboot so I tried to give it a little thought on how I should update this system, and so far I had no problem with it: You see, Android 10 had quite a lot of bad, unresolved updates, especially for those who manage to have a "successful" day one update (this translates to those who didn't have a bricked device) so now, when an update comes, it just tried to patch the old broken version, with mixed results, and not completely over write it. Remember back in A9 age? When you'd miss an montly update, the next month your update size would be >1gb? That means the 2 version old android version wouldn't be compatible with the new build so it did a complete rewrite of the partition? This never happened on A10 since launch, so here's what I did, after that system crash I downloaded the 10.0.7 and flashed it twice (by rewriting twice it means this, flash, reboot, boot into system, shut down, recovery, flash again, reboot, boot into system) through recovery, thus rewriting both A and B partitions with a known "good" (it still has bugs, but it doesn't carry the day 1 or day 2 major bugs) firmware flash. Now the same happened with the new update the 11.0.9, copied to SD, flashed through recovery and here is my review.
The bug in which the 5G icon in the wi-fi menu wouldn't hold if connected to the network and turned into a 4G wi-fi network still stands. This is only a visual bug, since the 5G network is doing just fine.
Tested the camera extensively and now it has a more aggressive focus and it's sharp again, image size is now large, like before, quality is improved in daylight, but the low light still could use some improvement.
The "useless" cards in Settings menu are still there (I personally only have the Customize your pixel one).
There is now a smoother feedback in the haptic feedback, so sometimes it seems like it's not working, but it's me not feeling it.
The 4G speeds still seem to be low, but again, like I said last time it could be a problem from my network provider, so I can't be 100% sure.
The internal storage speeds seem more and more slow on the other hand, I can't get transfers over 30mb/s on the internal storage, weird, because on .7 I could go over 100mb/s without a problem.
The RAM management is weird, after flashing the phone "my way", I can open ALL of the phone's apps and they'd stay up and running in the RAM until the phone starts going so sluggish that's almost a burden to use. It doesn't selectively remove apps from ram until closed from the recent menu. It isn't a problem for 5-10 apps open at once, but it starts getting weird after 30-40. Also the background apps are killed after a specific time, not by RAM usage which is counter intuitive... damn.
The MTP - SD card is still faulty. Refuses to display contents of large folders unless plugged out and plugged back in again. At least it's not crashing transfers right now.
The Media scanner is still faulty, after copying data to SD card they won't display in the specific apps (Google Photos, Google Music) but if manually searched (for example in my case Hiby Music) they're there and they can be used. Only reboot fixes this problem.
Direct Share is still not working.
This is all I had to say about the new .9 update, the rest of the more extensive things I covered can be found in the 11.0.7 thread, and it wasn't productive to write them here again, since the experience didn't change.
Battery seems a little worse than 11.0.7 but that was just the first day of testing, so it's irrelevant for most real world situations.
Other than the new method of installing and the few problems that seems odd to me, I can't report anything else after 1 day of usage. It's more usable, but it still have it's quirks... at least they didn't break anything else this time.
Yup.. Day two ram managent is getting as you described.. Still the device seems working better..
Update: generally better but still ram gets full after a couple of days. Still needs to reboot to fix the issue and clean the memory.
I think it's unbelievable that 4gb of ram are not enough to run this system.. There must be some bad development.
Not seeing "Some app services stucks on Restart state".
I can confirm you that the app you have mentioned in 9 are causing the device to slow because if you restart the app and then force stop them via hibernator Pro your phone who don't feel slow until they start again
I'm still having memory issues on my 4GB RAM model. Chrome tabs usually reload when switching back from another app even if I only have 1 tab open. The Google feed on the left of the main screen also reloads constantly. Those things didn't happen on android 9, I was able to seemingly switch between apps.
ema93a said:
I'm still having memory issues on my 4GB RAM model. Chrome tabs usually reload when switching back from another app even if I only have 1 tab open. The Google feed on the left of the main screen also reloads constantly. Those things didn't happen on android 9, I was able to seemingly switch between apps.
Click to expand...
Click to collapse
Same. I cant even download Call Of Duty: Mobile if i wont stay on Google Play Store app. Play Store downloads it %99 and if i switch to another app LMK kills the download process and then i am switching back to Play Store app it starts downloading from %0.
perfect_ said:
Same. I cant even download Call Of Duty: Mobile if i wont stay on Google Play Store app. Play Store downloads it %99 and if i switch to another app LMK kills the download process and then i am switching back to Play Store app it starts downloading from %0.
Click to expand...
Click to collapse
Lspeed fixes it
I had issues when multitasking Youtube and Opera/Chrome. It lagged until starting to freeze the browser, requiring me to press home and go back to browser. In some ocasions, the device restarted, maybe when ram got full or somehow corrupted.
After months in this situation, I gave up the once beloved Android One for the MIUI port HybridOS. After flashing this rom my device is completely different, more responsive, much less laggy, battery charges much more faster, and drains a lot less. The difference is like water turned into wine. Not to mention better camera quality (much better!), and the ability to record internal audio from everything (thanks to MIUI). I'm happy with my device again.
Sir waiting for 11.0.10.0 review
dplc81 said:
I had issues when multitasking Youtube and Opera/Chrome. It lagged until starting to freeze the browser, requiring me to press home and go back to browser. In some ocasions, the device restarted, maybe when ram got full or somehow corrupted.
After months in this situation, I gave up the once beloved Android One for the MIUI port HybridOS. After flashing this rom my device is completely different, more responsive, much less laggy, battery charges much more faster, and drains a lot less. The difference is like water turned into wine. Not to mention better camera quality (much better!), and the ability to record internal audio from everything (thanks to MIUI). I'm happy with my device again.
Click to expand...
Click to collapse
Hi
Are you still on that version ?
How has it been I'm tempted as my phone's so slow now I'm still on stock.
Do the banking apps work ok as that's my main worry for changing as I need them.
Do you have a link for your version I can't seem to find it.
Thanks
steve.loveday said:
Hi
Are you still on that version ?
How has it been I'm tempted as my phone's so slow now I'm still on stock.
Do the banking apps work ok as that's my main worry for changing as I need them.
Do you have a link for your version I can't seem to find it.
Thanks
Click to expand...
Click to collapse
Hi, I felt my device was slowly becoming unstable, and some bugs from the original MIUI device began to bother me a little, e.g. "Do Not Disturb" mode don't block message sounds from favorite contacts, I wanted only call sounds, as in Android One. My wife still uses the Hybrid OS (same phone as ours) and she likes it a lot because of the camera quality and the cool interface. Banking apps work fine in HybridOS.
I decided to downgrade my A2 Lite to the original Oreo Android One (8.1), and I think battery lasts more then Hybrid OS, and the phone is even more smoother and stable. Some tradeoffs are the (very bad) camera, no dark theme, no radio, and some other minor features, but the phone is almost like when I bought it back in 2018. Now I remember how great this phone was/is.
If you really wish, I can try to upload the Hybrid OS somewhere.