Hi ,
I've just moved from cm7 to MIUI
Everything seems to be ok , apart from the fact the whole phone freezes for 2-5 seconds often. During this time the display doesn't change anything on the screen and the hardware buttons do not work.
So for example, if your moving left/right between the home screens - when the freeze happens it will show half of one home screen and half of the other.
It doesn't matter what your doing - there is no pattern to it. Its so annoying.
I've looked in the main thread for MIUI but found anything. Any ideas?
1) are you using latest build?
2) did you wipe cache AND data AND dalvik?
3) if nothing of above helps, then try to change vsel and/or default cpu clock
... I'm using MIUI for a while and I don't experience that problems
thanks for reply:
1) I think so - 1.12.16
2) Yep , wiped factory and cache x2 just to make sure.
3) this could be what Im after.
I've installed Milestone2 Toolbox and the overclock tool is showing
Clock 1 - 300 Vsel 17
Clock 2 - 600 Vsel 32
Clock 3 - 900 Vsel 44
Clock 4 - 1200 Vsel 60
I've tried flashing the Stock cpu/vsel values zip on the first page on the main thread: ( [ROM] [12/18] MIUI 1.12.16 GB 2.3.7 + ICS Multilanguage for Milestone 2!)
It seems that it hasnt worked - but I will try again.
NOTE - My MS2 has not rebooted itself like a lot of people who are having problems.
I tried again flashing the stock values zip from Clockwork - it looked like it worked.
Going into milestone2 toolbox however the values listed above are correct.
As such , I've changed the values manually using the milestone2 toolbox to endless cm7 values as specfied on page 35 of the main thread:
http://forum.xda-developers.com/showthread.php?t=1258073&page=35
After a few mins of use - it hasn't frozen yet.
Will give it a few hours and see how it behaves.
just to let you all know the changes above seemed to have worked
DoPa6 v1 build 3 is the Marshmallow ROM for Sero 7 Pro owners worldwide.
This build, based on AOSP 6.0.1 r43, focuses on features that must be built in and can't be added on such as selective overclocking and multiple formatting options for your SDcards.
For those who want to customize the ROM's look and feel, Xposed and Gravity Box come pre-installed to provide all the tweaks you want - and none of the ones you don't.
DoPa6 also offers a companion build of TWRP v3.0.2 (DoPa6 v2). Based on Marshmallow code, this new version offers an updated look and feel plus a few Sero 7-specific tweaks.
Installation
backup your data so you can easily return to your current ROM
- initial installation: wipe your '/data' partition (a "Factory reset" in TWRP will work)
- upgrade from previous DoPa6: no need to wipe or format anything
install sero7pro-aosp601-dopa6-v1-bld3.zip
install your choice of Gapps packages
(optional)install the Nexus 7 spoof
reboot
Note: after using this ROM, TWRP 2.8.7 will report that it can't mount '/thirdparty'. This is to be expected since that partition is now used for swap space. You can safely ignore this warning. (TWRP 3.0.2 does not have this problem.)
Important: please do not report any bugs you encounter the first time you boot-up after installation. Instead, please reboot then see if the problem persists. If so, let me know so I can (try to) fix it.
Downgrade
If you decide to return to a previous version of a DoPa ROM (i.e. Kitkat or Lollipop) after using DoPa6, you must reformat the '/thirdparty' partition as ext4. This will restore compatibility with the older version - without it, previous versions won't boot. You can do so directly using TWRP 3.0.2 or by installing sero7pro-format-thirdparty.zip (links below).
Notes
Memory Features - users can enable/disable key memory features to suit their needs. Open Settings->Performance->Configure RAM options and change these items as appropriate:
Dynamic fsync - cache writes to flash memory until the screen goes off [excessive memory use]
Kernel same-page merge - scan for and merge blocks of kernel memory that have the same content [overhead]
Disk-based swap file - use the '/thirdparty' partition to add 256mb of virtual memory [possible i/o contention]
Low-ram mode - employ the memory-saving tactics normally used on a device with only 512mb of memory [reduced graphics capabilities]
Low-ram graphics - reenables accelerated drawing that low-ram mode disables [significant increase in RAM usage]
Note: all of the system properties used by previous versions to set these features are now obsolete and have been removed from 'build.prop'; do not restore them.
ADB Over WiFi - to access ADB with having to install any drivers, open Settings->Performance and check "Enable ADB access via WiFi". At a command prompt/terminal, run "adb connect <your.tablet's.ip.address>". You should now be able to run any adb command. Note that this setting is not saved: ADB Over WiFi will be disabled when you reboot.
External Storage - this ROM now supports two types of external storage:
portable - your sdcard is used for storing non-secure data (music, photos, etc.). It remains compatible with any device that supports the filesystem you've chosen.
adoptable - the sdcard becomes your "internal sdcard": besides storing app data and media, you can also move entire apps to the card. Because the card is encrypted, it is incompatible with any other device.
The first time you insert a card, there is an option in the Notifications pull-down to set up the card. Alternately, you can open Settings->Storage and USB, select the card, then tap the menu button for setup options. If you choose Format as internal, the card will be formatted F2FS and encrypted; you'll then be given the opportunity to move your data to it. Choosing the Format option displays a screen that lets you choose the filesystem to be used (fat32, exfat, ntfs, f2fs, or ext4). Be aware that both options repartition the card and destroy all existing data on it.
Multi-Window - To enable it, open Settings->Developer Options, then scroll down to the "Drawing" section. Multi-window mode is the last item in that category.
Known Bugs
Encryption - attempts to encrypt the '/data' partition will fail but no data is lost because the process never really gets started; the problem appears to lie in the kernel and may take a while to resolve
Large SDcards - Class 10 32gb and 64gb sdcards may not be recognized or may be reported to be corrupt; this issue was also reported for Lollipop
Bluetooth - Bluetooth Low Energy profiles are not supported
Downloads
sero7pro-aosp601-dopa6-v1-bld3.zip - the ROM
sero7pro-gapps-dopa6-v1-bld3.zip - a "nano" Gapps package compatible with this build
sero7pro-nexus7spoof-dopa6-v1-bld3.zip - have the ROM report that this is a Nexus7 - only for use with DoPa6 v1 bld 2
sero7pro-twrp302-dopa6-v2.zip - a customized version of TWRP Recovery v3.0.2
sero7pro-format-thirdparty.zip - use this if you plan to downgrade from DoPa6 to a previous version (no longer needed if using TWRP 3.0.2)
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
Changelog
v0 bld 8
* new: easy access to ADB over WiFi
* new: user control over key memory features such as swapping
* changed: restored ArchiDroid build optimizations used in DoPa5
* changed: reverted to original kernel due to Bluetooth and WiFi Display issues
v0 bld 7
* new: upgraded kernel to use networking code from Linux 3.4
v0 bld 6
* new: converted the unused '/thirdparty' partition into a dedicated 256mb swap partition
* new: Xposed and Gravity Box are now pre-installed
* enhanced: choose any filesystem when reformatting an SDcard from "adoptable" to "portable" storage
* bugfix: the flashlight/torch quick-settings tile would only work once per session
v0 bld 5
* new: format an external SDcard using any of the 5 supported filesystems from within the Settings app
* bugfix: screen rotation failed to work if the tablet wasn't charging
v0 bld 4
* new: extended SDcard/USB storage support to include ntfs, ext4, and f2fs
v0 bld 3
* bugfix: a regression prevented using an SDcard as "adoptable" storage
* bugfix: an empty MTP device appeared on a PC even when the tablet was set to "charge-only"
v0 bld 2
* new: all Bluetooth features work except BT-Low Energy
v0 bld 1
* new: major updates to the kernel to support mount namespaces - external storage now works
v0 bld 0
* initial release: most hardware features work except external storage and Bluetooth
That was fast.
Sent from my K013 using Tapatalk
I'm seeing s'mores in my future... or maybe fluffernutter? Thanks for the continued work!
Wow! That WAS fast! ?
Sent from my Nexus 7 using XDA Free mobile app
Superb! Keep up the excellent work!
Nice. I am behind on stuff due to being sick the past few weeks so I'll install this build and see what I notice within the next day or two. I do wonder perhaps since the Nexus 7 (Grouper) has semi official MM that stuff like Bluetooth, DRM, etc can be fixed from that source?
AngryManMLS said:
perhaps since the Nexus 7 (Grouper) has semi official MM that stuff like Bluetooth, DRM, etc can be fixed from that source?
Click to expand...
Click to collapse
Not necessarily. We're working from the same source code but in most cases the hardware is different. For BT, the hardware is the same (BCM4330) but the firmware is different. I tried using the N7's firmware and that eliminated the crashes - but it wouldn't connect to anything, so that wasn't much help. As to DRM, I haven't read of any problems but that could just mean that no one has tried. At some point I'll try swapping in some of their proprietary files (as I've done in the past) and see if that fixes anything.
Speaking of fixes... I made some massive changes to the kernel and now have external storage working (this took at least 60 hours to achieve). Once I have exFat support in place, I'll release an update.
dolorespark said:
Not necessarily. We're working from the same source code but in most cases the hardware is different. For BT, the hardware is the same (BCM4330) but the firmware is different. I tried using the N7's firmware and that eliminated the crashes - but it wouldn't connect to anything, so that wasn't much help.
Click to expand...
Click to collapse
I'll get some logs once the next version is out and see maybe if those error messages when connecting BT devices might help out.
amazing
Thank You DoloresPark!
it runs amazing for the first release. I flashed the new twrp, gapps, and the ROM from my USB memory stick without any issues. No problems downloading, uploading, notifications, it's great.
see my photos here:
http://sero7forum.com/sero-7-root-h...ro-aosp-6-0-0-dopa6-v0/msg8392/?topicseen#new
I can't get the update to flash. I get to the lockscreen, swipe to open, and all I can get is a black screen and the error message " unfortunately setup wizard has stopped". I've reflashed a couple times.
Ok. I got it flash. It took 17 min. to boot up. I could of fried an egg on the back of my tablet. But it's fine now! :laugh: runs great.
Thanks! Looks great!
So, do we know if xposed and gravity box works on this build yet?
Edit: Never mind. I don't suppose there will be a Gravity Box for Marshmallow for a while.
Sent from my Nexus 7 using XDA Free mobile app
v0 build2 released
Now that everything works (sorta), DoPa6 - Marshmallow for the Sero 7 Pro - has entered its beta-testing phase. It would be really helpful if you could try it out and tell me what glitches you encounter.
For example, I know that Launcher FCs when you rotate the tablet, and that the "Memory" figures displayed in the Settings app are all wrong, but what else? Does the thing spontaneously reboot? Is WiFi unreliable? Do apps lag? Et cetera, et cetera...
Truth is, I spend so much time screwing with the thing that I don't get to use it as much as you do. If it doesn't generate an error message in a logcat, I might never know something's wrong.
Auto-rotate issue
dolorespark - Thanks for the great rom. I'm really impressed with what this older hardware can do.
The only issue I'm seeing right now is that my auto-rotate only works occasionally. I originally noticed this problem with build 1 and I'm using build 2 and the problem is still there. If I switch from portrait to landscape the display will not turn. If I turn off the tablet while it's in portrait and power it back on in landscape it will display in landscape. When I originally noticed this I thought that the sensor might have stopped working but I used a hardware info app and I can see the changes as I rotate the tablet. I don't know if any logs would help with this but I'm willing to try if you need them.
Hi,
Over the week-end I had a brief try with your marshmallow ROM, it apparently installed OK, and appeared to be running fine once it settled down after a couple of
reboots.
There was an oddball thing happened though which may not be relative to your build (could be other causes) ... Marshmallow took a dislike to my 64GB SD card I got a
message saying the card had not been prepared, and did I want to do this ? (or words to that effect), I OK'd the preparation and it did it's stuff, next I had a
pop-up saying the card couldn't mount as it was corrupted (it had been OK when running in lollipop). At first it appeared as if the card was a write off, but I eventually got it
restored after running Chkdsk /R on the windows PC, strange thing is now it wont mount in the Sero 7, but mounts OK in 2 separate allwinner tablets we have in family,
2 separate identical SD cards do mount no problems in the Sero 7. (now back on Lollipop).
I think you said initially that there was problems with storage, could my issue be down to that ?.
I liked what I saw of marshmallow (great on this older hardware), but admit I didn't spend much more time on assessment of it, I was diverted into recovering the SD
card, and as I've said restored my Lollipop backup. ... J.
yanu said:
The only issue I'm seeing right now is that my auto-rotate only works occasionally. [...] I thought that the sensor might have stopped working but I used a hardware info app and I can see the changes as I rotate the tablet.
Click to expand...
Click to collapse
Everyone with a Nexus 7 has been reporting this problem. I've only seen it once when I killed the Launcher while in Settings->Apps but I haven't been able to reproduce it. As mentioned in the OP, I get FC's in Launcher when I rotate. However, I've found an odd "cure"...
I wanted to see if the FC problem was specific to Launcher3 or more generic, so I installed Apex. After switching to it, I was able to rotate without problem, so I went back to stock and discovered that the problem had disappeared. Even after I uninstalled Apex and cleared Launcher3's data so I was back to the default home screen, I didn't get any FCs
jachol said:
There was an oddball thing happened though which may not be relative to your build (could be other causes) ... Marshmallow took a dislike to my 64GB SD card
Click to expand...
Click to collapse
I don't think this is new. Several people mentioned intermittent problems with 64GB sdcards on Lollipop (Samsung in particular, IIRC). This is one thing I can't test because I don't have (or need) anything bigger than 16GB. Sorry...
dolorespark said:
Everyone with a Nexus 7 has been reporting this problem. I've only seen it once when I killed the Launcher while in Settings->Apps but I haven't been able to reproduce it. As mentioned in the OP, I get FC's in Launcher when I rotate. However, I've found an odd "cure"...
I wanted to see if the FC problem was specific to Launcher3 or more generic, so I installed Apex. After switching to it, I was able to rotate without problem, so I went back to stock and discovered that the problem had disappeared. Even after I uninstalled Apex and cleared Launcher3's data so I was back to the default home screen, I didn't get any FCs
Click to expand...
Click to collapse
I loaded Apex and auto-rotate still doesn't work. I installed 'Rotation Control' which allows me to easily rotate the display so I can live with it for now. I haven't seen any FC's in the Launcher or anything else at this point.
dolorespark said:
E
I don't think this is new. Several people mentioned intermittent problems with 64GB sdcards on Lollipop (Samsung in particular, IIRC). This is one thing I can't test because I don't have (or need) anything bigger than 16GB. Sorry...
Click to expand...
Click to collapse
Thanks ,,, no problem point taken, and thinking back I agree. SD card soon fills up when you store video files as I do that's the main reason for the 64GB card.
I'm more curious re. why this card will no longer mount in the Sero 7 when identical cards do, ideas anyone ?. ... J.
dolorespark said:
External Storage - this ROM now supports two types of external storage:
* conventional - your sdcard is used for storing data - currently only Fat32 and exFat are supported
* adoptable - the sdcard becomes an extension of internal storage and can store apps and data. The first time you insert a card, there is an option in the Notifications pull-down to set this up. Alternately, you can open Settings->Storage and USB, select the card, then tap the menu button for setup options. Note that the card gets formatted and encrypted, and can't be used with any other device until reformatted.
Click to expand...
Click to collapse
I never got the prompt nor do I have the setup option for the adoptable, all that is in the menu/settings is Eject and Format, am I missing something?
Garrett
After having a great deal of stress regarding the notification issues, I have come up with a solution.
Please note:
1. I have no idea why my solution works on only this one version of the firmware, but I can only reproduce it on build number NXT-AL10C00B129SP02 (The second-to-newest Chinese firmware). I cannot reproduce the solution on other versions and have not yet gotten notifications working on them, so please make sure you have the same version of everything as I do to make it go smoothly. I have only tried and failed on the latest Chinese and the latest international firmware, so perhaps an older version of that will have good results.
2. I can't guarantee this will work for everyone. Everyone has a different combination of software and settings, etc. What works for me very well may not work for you, and vice versa.
That being said, here is what I did, and how you can test and make sure it's working right for you.
Step One: Set up the OS.
Get NXT-AL10C00B129SP02 (available from the development section of this forum). You can unpack it and flash it with flashboot. The unpacking tool is as follows:
http://fs1.d-h.st/download/00173/wwfQ/HuaweiUpdateExtractor_0.9.9.3.zip
This tutorial won't cover flashboot usage. Please figure it out with google and feel free to ask if you need additional help.
You will then need to get TWRP installed. Please refer to root thread.
Getting into TWRP, please first format your /data partition, then flash the following in order. (maybe different versions will work, but these are what I used, and they worked for me, so maybe better safe than sorry.)
---
decrypt boot B129SP02.zip (can be found in this forum)
BETA-SuperSU-v2.66-2016013015024.zip
open_gapps-arm64-6.0-micro-20160108.zip
---
Then, clear cache and dalvik cache, boot the device up, and set it up.
Get into developer options and turn on ADB debugging. We will use adb to check that everything is working properly. Also, configure an email account with gmail. We'll use gmail to test as well.
Step Two: Doze Settings
Download and install Doze Settings Editor, available from the following:
http://forum.xda-developers.com/android/apps-games/root-doze-settings-editor-android-t3235130
Open SuperSU, then open Doze Settings Editor. SuperSU will ask for root permission, please grant it.
Go into Doze Setting Editor. To keep it easier, go to preferences and change display from milliseconds to seconds.
Set the following, from the top down.
30, 0, 0, 20.0, 0, 0, 12, 12, 2.0, 60, 600, 2.0, 3600, 300, 60, 20
(Easier way to do this is to load tuhinxp04's profile and just change idle timeout and max idle timeout to 60 sec and 600 sec respectively)
Step Three: Test
Now, we will test! Make sure you have adb on your computer, plug your phone into your computer, and run the following commands:
adb shell
dumpsys battery unplug
(turn off the screen of your phone)
dumpsys deviceidle step
(repeat this command until the state is IDLE.)
Now, check the status with this command:
dumpsys deviceidle
Things to look at from the output of this command are:
mState
mNextAlarmTime
Basically, mNextAlarmTime will count down to zero. When it reaches zero, mState will go from IDLE to IDLE_PENDING (and that's when you'll get your notifications). The settings we put in Doze Settings Editor make it so that the countdown starts at one minute, then increases twofold each time until it hits ten minutes. So the longest you'll wait to receive an email notification would be 9 min, 59 seconds.
If everything went well, the device will go from IDLE to IDLE_PENDING after the countdown. Send a test email and watch it arrive.
That's it! If this works, you'll get your notifications. You can adjust the numbers in Doze Settings Editor to match your personal preference.
Now here's the odd thing. With the latest Chinese firmware and international firmware, it does not go into IDLE_PENDING after the countdown. Instead, the countdown goes from +1sec to 0sec to -1sec and counts up, when debugging with ADB. I have no idea how to fix this, but if anyone with other firmware wants to try this solution and see what happens, hopefully we can fix notifications for all software versions. For now I'll stick with NXT-AL10C00B129SP02
UPDATE: I have somehow gotten AL10C00B129SP02 to behave the same as the newer version. I will look further into this as best I can and figure this out. So please hang on a little longer
Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!
Vikram1988 said:
Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!
Click to expand...
Click to collapse
I tried this on my L29 running B162. It seems to have made no difference at all. Notifications are still significantly delayed, especially for email.
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
Vikram1988 said:
Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!
Click to expand...
Click to collapse
I think this is a Huawei EMUI thing. If you look back at older phones on older versions of Android (P8, Mate 7, etc) they all had this issue (and still do). People try to blame doze, but this issue existed long before Marshmallow was around.
I have the European L29 model and I see this issue. Don't let anyone try to tell you that model doesn't suffer from it. It's real.
Guys check my post on 100% working solution for Notifications http://forum.xda-developers.com/mat...ues-huawei-t3345380/post66044102#post66044102
Tested on latest xiaomi.eu rom
BEFORE STARTING ALWAYS REMEMBER TO BACK UP THE FILES YOU ARE ABOUT TO EDIT
I AM NOT RESPONSIBLE FOR ANYTHING BAD THAT HAPPENS OKAY
I WISH THIS WERE POSSIBLE ON NON ROOTED PHONES BECAUSE I UNDERSTAND THE PAIN OF HAVING BAD MULTI TASKING
NOW LETS GO
1. Make sure phone is BL unlocked and Rooted
2. Flash latest Xiaomi.eu rom and make sure you have root (via superSU or whatever root app of your choice)
3. Install FX file explorer and FX root add on
4. Go to system/etc and find a file named mcd_default.conf
5. edit the file and delete the lines that are shown here highlighted
open image
6. Save file
7. Enable developer options
8. Find memory optimization and set to HIGH and Reboot
9. Wait for phone to boot back up
10. Go to Developer options in settings and Disable MIUI optimizations and Reboot
11. Install kernel audiotor and go to low memory killer option and select very light and enable "apply on boot"
12. Reboot
13. Go to fx file explorer and go to system/build.prop and edit the file - find the line persist.sys.whetstone.level=2 and change it to persist.sys.whetstone.level=0 and save file and reboot
14. Test it out yourself
EXPLANATION
Basically the lines that are deleted in the mcd_defaullt.conf makes sure that ALMOST ALL APPS are killed whenever you launch a system app like PHONE, MESSAGING, GALLERY. In AOSP roms this is not the behaviour, instead AOSP picks the least used app or the earliest app used to be killed when LMK (Low memory killer) values are reached. Deleting the lines brings back this AOSP behaviour. Benefit of MIUI is you can LOCK APPS IN MEMORY using the task manager/recent and now MIUI will kill the earliest used app in the recents/task manager that are NOT locked.
EXPLANATION NUMBER 2 REGARDING CHANGING LMK BEHAVIOUR USING KERNEL AUDITOR
The stock LMK values are not set by xiaomi or MIUI, instead it is automatically generated by ANY AOSP rom because it uses a ratio system. If the ram is big (like ours 3gb) than the ratio values will be higher. MIUI or Xiaomi should have fixed this but they didnt. SO PLEASE CHANGE THE LMK VALUES IN KERNEL AUDIOTOR
EXPLANATION NUMBER 3 REGARDING WHETSTONE
Don't uninstall or freeze this app. IT DOES NOT HELP OR AFFECT MULTITASKING AT ALL. DELETING IT WILL DISABLE MEMORY OPTIMIZATIONS
REMINDER
MIUI is a very RAM hungry OS so please dont expect a lot of free ram but unused ram is wasted ram anyway
Ok, first of all i just want to thx for this guide... but... it's not working.
Redmi Note 4 with MIUI EU 8.1.3.0 Stable.
I tested it for about 1day and here are my feedback:
- Phone hangs and become unresponsive quickly. I kill all apps, but still lags. If i restart the phone, then is ok for a while...but after i open again some apps, games, will die in huge lagging.
- Camera lags, google play lags, facebook lags.
- Fingerprint unlock have 1-2 sec onds delay. Never ever have this problem again.
- Battery is the same, no improvements here.
I finished after one day, restoring my backup.
I done all the steps, exactly in your way and your order. My feeling is that memory are not fully released, even if i kill all the apps.
I will test next every part in this guide, independently, to se how is doing...
x3m.zone said:
Ok, first of all i just want to thx for this guide... but... it's not working.
Redmi Note 4 with MIUI EU 8.1.3.0 Stable.
I tested it for about 1day and here are my feedback:
- Phone hangs and become unresponsive quickly. I kill all apps, but still lags. If i restart the phone, then is ok for a while...but after i open again some apps, games, will die in huge lagging.
- Camera lags, google play lags, facebook lags.
- Fingerprint unlock have 1-2 sec onds delay. Never ever have this problem again.
- Battery is the same, no improvements here.
I finished after one day, restoring my backup.
I done all the steps, exactly in your way and your order. My feeling is that memory are not fully released, even if i kill all the apps.
I will test next every part in this guide, independently, to se how is doing...
Click to expand...
Click to collapse
u have to use the latest xiaomi.eu rom
the stable 8.1.3.0 has a bug where the dev still classified the rom as having 2gb of ram only (we have 3gb variant as well) (i read this somewhere i forgot where) and the latest china dev xiaomi.eu rom has this bug fixed for our device. Try this tweak with memory optimization on LOW but remember use the LATEST xiaomi.eu rom. Phone is working wonderful on my device
also try freezing battery saver via Link2SD. This is the only other thing I have changed on my device
x3m.zone said:
Ok, first of all i just want to thx for this guide... but... it's not working.
Redmi Note 4 with MIUI EU 8.1.3.0 Stable.
I tested it for about 1day and here are my feedback:
- Phone hangs and become unresponsive quickly. I kill all apps, but still lags. If i restart the phone, then is ok for a while...but after i open again some apps, games, will die in huge lagging.
- Camera lags, google play lags, facebook lags.
- Fingerprint unlock have 1-2 sec onds delay. Never ever have this problem again.
- Battery is the same, no improvements here.
I finished after one day, restoring my backup.
I done all the steps, exactly in your way and your order. My feeling is that memory are not fully released, even if i kill all the apps.
I will test next every part in this guide, independently, to se how is doing...
Click to expand...
Click to collapse
also thanks for feedback which is very important in testing tweaks
asusm930 said:
u have to use the latest xiaomi.eu rom
the stable 8.1.3.0 has a bug where the dev still classified the rom as having 2gb of ram only (we have 3gb variant as well) (i read this somewhere i forgot where) and the latest china dev xiaomi.eu rom has this bug fixed for our device. Try this tweak with memory optimization on LOW but remember use the LATEST xiaomi.eu rom. Phone is working wonderful on my device
also try freezing battery saver via Link2SD. This is the only other thing I have changed on my device
Click to expand...
Click to collapse
I use EU Stable 8.1.3.0 ROM for about a week and never had problems or any bugs. None!
I will try this again on EU Dev 6.12.15 today to see how is doing...
x3m.zone said:
I use EU Stable 8.1.3.0 ROM for about a week and never had problems or any bugs. None!
I will try this again on EU Dev 6.12.15 today to see how is doing...
Click to expand...
Click to collapse
I just tried this just now on a clean flash of latest EU ROM
1. memory optimization on LOW
2. Use link2sd to freeze battery optimizer app
3. Delete this line from mcd_default.conf in system/etc directory https://drive.google.com/file/d/0B_Q4QjvbODxoS2RnRmRWTDk3TE0/view?usp=drivesdk
4. Set LMK Low Memory Killer value to medium on Kernel Auidotor
And thats it with the same result as my previous tweaks. I think this will resolve the lag that you are facing
Ignore my previous steps on this thread and follow these new ones. Good luck