yashsingh1/xdaforums huggingface dataset:
[Mi 3 General] The Dork Knight Rises:
Well, good luck, share details of what changes you made from cm12 once you confirm reboots don't happen.

And I sometimes didn't get SystemUI even after waiting for ~10 minutes...Could you tell exactly which parameters you changed in build.prop to prevent boot delay, in case I decide to try CM12 again?

And BTW, I set persist aries power mode to high and disabled MPDecision, now all my cores function, but as they're still getting locked at lower frequency when under stress, benchmark scores haven't improved.

Question is, would keeping aries power mode high and MPDecision off, will I get more battery drain (as more cores function)? Or is it OK if I keep it like that?
[Mi 3 General] SkipperRyujin:
Well, i also studying it by google in my free time ( usually when i got insomnia :D )

Well, i change the calib directory and vendor directory (like my old post) . The newest bulid.prop also including limitting the sensor read which i also ever try it (found it in hammerhead forum). Also disabling nfc. But in latest cm12 build, in the logcat reader, the sensor is all error (forget to take the screenshot). It actually not prevent the boot delay, just somehow faster boot ( it still has "boot blink" and usually after 3 blink it booted to lockscreen)

As long as procs running normally and not much lag, it always better to let the procs to sleep. Waking more core also absolutely increase the battery usage according to frequency. In cancro the high powermode is still in interactive governor
[Mi 3 General] Riichard63:
Sometime it's better to sleep :p I hate insomnia!

It depends, for the Mi3 it's interactive, for Mi4 it's performance, I don't know why Xiaomi made that difference.

When you're talking about changing power mode, it's on editing build.prop line, or and other file?
[Mi 3 General] The Dork Knight Rises:
Ah, insomnia. I've gotten used to sleeping at 3am these nights...

Wait, so changing persist.aries.power_mode only changes the CPU governor? I could have done that without having to edit build.prop and rebooting...
[Mi 3 General] SkipperRyujin:
Mi4 and mi3 basically sets at interactive, then on mi4 if you change to high, it will set governor to performance( just read the changepowermode under mi4, high)

Actually you can change it using any cpu-tweak-editor app,

Ofcourse not. It changing the parameter to which is included in changepowermode depending on which powermode is used, basically it just like the init.d support, it running on boot so we dont need extra resource for that. Ofcourse you can change or edit the parameter using app
[Mi 3 General] feed3:
Just some tips.

To change the cpu governor effectively, you need to change it in ramdisk and few files in /system/etc/.

For those cpu frequencies thingy, that is mpdecision in action. You need to disable it entirely if you want to totally take control of the cpu speed (remove mpdecision related lines in ramdisk and the bin file) but i dont recommend it. Also, thermal config is in effect to the max cpu speed.

Mpdecision in /system/bin/ and thermal config you need to look at /system/etc/ folder.

Another file you need to look at for governor, cpu frequency and active cores is init.qcom.post_boot.sh in /system/etc/ as well if I'm not mistaken.

Thermal config and init.qcom, you can refer to hammerhead files.

Last time, when i ported Ivan's aosp kernel to PA, modifying these two files, it will allow better hotplugging by mpdecision (core 0 active, all other cores offline in low load and other cores kicking in when in higher load.

Cheers..

Good luck to all mi3w users. :thumbup:
[Mi 3 General] The Dork Knight Rises:
Yeah, that's what I was saying. I have an app (Device Control) which has a Tasker function which I have set up to set CPU governor to powersave on screen off and ondemand (which, I believe is like a less aggressive version of interactive) on sceen on.

So what you're saying is, since aries.power_mode and changepowermode.sh together work to set CPU parameters at boot ONLY, they were made useless by my Tasker profiles? LOL :silly:
[Mi 3 General] SkipperRyujin:
Yeah, thats all i do :D

I also read in hammerhead forum since there is a stable lollipop already. Just still confusing about set domain and owner....

And do you know why there is some missing/invalid address at build prop? Like the calib address to /data but no such file exist, also for vendor directory?

---------- Post added at 02:23 PM ---------- Previous post was at 02:20 PM ----------

Yeah, thats true :D

Sorry for doublepost. I didnt see ur post when writing :D
[Mi 3 General] Riichard63:
Hum okay, with what you said I'm sure that I can't change anything to correct this CPU frequency and governor problem... Just have to wait for a new Ivan's release or the stable CM developped in ther thread...

I don't know anything about ramdisk, I just took informations and for me it seems impossible, and I prefer never touching this kind of file...

Edit : Anyway thanks for these precious informations =)
[Mi 3 General] Mr Rainman:
Seems cyanogenmod isn't going to happen for now, the thread was closed on op's request
[Mi 3 General] chankalson:
it's not closed, it's been moved to the original android development section :)
[Mi 3 General] Mr Rainman:
Well... and here I am, sitting, already having restored to AOSP 4.4.4...
[Mi 3 General] chankalson:
maybe it's a good thing, wait till it becomes more stable :D
[Mi 3 General] Mr Rainman:
From my point of view, probably yes but testers are always needed :D
[Mi 3 General] The Dork Knight Rises:
Aye, I'm thinking of dual booting it...
[Mi 3 General] srvoleti:
Any reboots so far sir? If no reboots, would like to test the ROM again. Please share the changes.
[Mi 3 General] Mr Rainman:
While the idea it's great, if my memory isn't fooling me, AOSP 4.4.4 doesn't support dual boot and there is no way I'm switching to MIUI if I have a working bug-free pure android experience
[Mi 3 General] The Dork Knight Rises:
No, I'm thinking of dual booting Ivan 5.0 and cm12...

From the tester point of view. Ivan 5.0 is very usable, except the random reboot issue, while CM12 as of now, has lots of features, but is pretty much unusable on daily basis.

Edit: This is assuming Ivan 5.0 supports dual booting, which it reportedly does with CWM r11.
[Mi 3 General] i snort flour:
Reboots are very few almost none I know of only 1 way to make mine reboot on 29 v1 and that's when I set it into deep sleep mode then tap on the screen a bunch then hold down on the screen for 10 seconds then more random taps and click the power button right away if I hit the power button right away it freezes and reboots cause it can't access the 17117 setpowermode command which causes a panic and a reboot. If I give it 15 to 30 seconds before I hit the power button it don't freeze, it don't panic and reboot and the screen pops up just fine so just give your device 15 seconds before you wake it if it was just in your pocket

Sent from my Xiaomi MI 3W

---------- Post added at 11:24 AM ---------- Previous post was at 11:18 AM ----------

BTW I use cm12 29 v1 as a daily driver and have no issues with it I don't use Bluetooth I don't use camera ever and I don't need an otg beings PlayStation remote play currently doesn't work with lollipop if I every need any of them features I just restore back to pa 4.4.4 which takes 5 minutes

Sent from my Xiaomi MI 3W
[Mi 3 General] s4tch:
probably that won't work. aosp/cm roms seem to work only on the system1 partition. i've already tried to install an early build of ivan's 4.4 rom on sys2, but all i got was a bootloop. anyway, good luck with that.
[Mi 3 General] Armin_van_buuren:
Currently I have the CM12 in the system 2 and system 1 and for a while I managed to hold off the bug mm-qcamera-daemon.

I've had it for about 3 hours and a reboot is back out on the graph.
[Mi 3 General] Riichard63:
That's weird, because on my Mi4 with the r11 CWM I have MIUI 6 on system 1 and AOSP lollipop from Ivan on system 2 and everything works like a charm (except rom bugs of course, and not efficient wipe with this version of CWM).
[Mi 3 General] s4tch:
^that's possible. i have a mi3, and i never managed to get any non-miui system working on sys2 with r7 than r8 cwm. i'll make an other try with the newer recovery.
[Mi 3 General] SkipperRyujin:
Well, its 16 hours up and no random reboot at all, but the battery is drain more if compared to latest edit, but not a big deal. All that i do is just disable some suspend parameter in cpu0, the rest is the same as i edited before. See the attachment

Edit: it is 20 hours up now :D
[Mi 3 General] srvoleti:
Thank you sir, I will try right now!
[Mi 3 General] deepesh.tickoo:
What are the changes from scratch?

Like if I just installed Ivan's AOSP and want to apply your mod and edits for 'no random reboots', what should I do all-in-all ?

I'll try it over a clean install myself and report. And if successful, ill try to make a flashable zip for easy installation.
[Mi 3 General] The Dork Knight Rises:
Off topic, but Redmi 1S sources are out guys! Happy New Year, those who own one!

https://github.com/MiCode/H1S_kernel/
[Mi 3 General] gau20:
Hello

Can anyone write down all the steps to avoid random reboots..?

its confusing so many posts.
[Mi 3 General] SkipperRyujin:
I reupload again the file that i change, it is build.prop (located in /system, permission rw-r--r--, owner root, group root), changepowermode.sh (located in /system/bin, permission rwxr-xr-x, owner root, group shell), init.qcom.post_boot.sh (located in /system/etc, permission rw-r--r--, owner root, group root) and calib.cfg (located in /system/etc, permission rw-r--r--, owner root, group root). All that need todo is backup your original file and copy those files to proper address, erase the txt extension, set permission and owner, and reboot. Or you can read the whole thing that i change, studying it (maybe we will get better result) and change your own parameter using my parameter as reference :D

Edit 1: Also dont change the launcher. My phone just reboot right after i using other launcher :'(

Edit 2: the build.prop didnt contain activating the navbar, so if you use it, edit the build.prop manually to add the navbar before rebooting. My capacitive button working almost fine so I didnt use the navbar :D . Thanks [MENTION=5782089]The Dork Knight Rises[/MENTION] for pointing it.
[Mi 3 General] lovleshgarg:
Yes, I can confirm that no reboots now..

A little more battery drain than usual is expected as the phone is not going into Complete deep sleep, cpu0 is running all the time as we have disabled it to go to sleep mode. But all other cores would be sleeping so it still should be better than using wakelock app.

I remember similar kind of configuration was there for Nexus 4 when it was launched. In that case, only 1 core was going into deep sleep and others were running. This had caused an increase in battery drain during standby. Then developers added setting for enabling other cores which improved deep sleep.

We have done it in other way for Mi3 but still it is definitely better than what we had earlier. Thanks!!
[Mi 3 General] SkipperRyujin:
Yeah, the cpu0 only enter the "idle" state, not "suspend" while the other still can enter "suspend" mode. Maybe if the kernel release it will improve the deepsleep method for mi3
[Mi 3 General] The Dork Knight Rises:
Whoa, haven't you enabled navbar and disabled capacitive keys yet? It helps for the wake up when locked bug.

I replaced your files and was left with no way of navigating. A build.prop edit worked, as always. You should add a small note to your previous post to enable capkeys before replacing, some ppl might not be able to reenable navbar so easily and be stuck.

Anyway, so you made changes so that cpu0 never enters suspend mode right? Question is, how would changing launchers affect that? (Btw, do you use Launcher3 or GNL?)

Or do you think it was just a normal random reboot (not deep sleep issue)? Because i don't see how launcher would affect cpu...
[Mi 3 General] SkipperRyujin:
Wew, i think i already post screenshot that show i didnt disable my capacitive button :D

Sry, my bad :'( .

Yeah its true, the build.prop didnt activate the navigation bar since i didnt use it

About the launcher, i still investigating it. It not only a reboot ( the cause is other, again) but also suddenly no touch response so i need to reboot it by long press power button. I uninstalling it, back to launcher3 and everything working fine again. No reboot at pocket, normal capacitive button, good battery live, and now i found my lost plantronics voyager edge :D

A wonderful day in the last day of 2014 :D

Edit: I using zero launcher when the phone suddenly reboot, and I forgot to take the logcat :'(

Edit2: I'm just curious about libsuspend that gets error when changing state and in cm12 build the OP disabling it all (at first build), and the phone didnt get a random reboot although the phone didnt enter deepsleep. Then I remembered that idle and suspend is a different parameter so I change that, one by one, and tested it whole day ( actually 3 day :D )
[Mi 3 General] The Dork Knight Rises:
Request:

Can someone provide me with the Calculator apk from CM12? It has more functions, and doesnt crash like the Play Store beta.

EDIT: Still seem to be getting reboots. Will try a dirty reflash.
[Mi 3 General] cosmicsatish:
My performance rating decreased after replacing the files previously i used to get somewhere in 44-45 range.. Now i am getting in 34-35 range.. :what:
[Mi 3 General] Armin_van_buuren:
I've already come to the conclusion that to use this rom and not be suffering if you restart or reset is used SuperUI or Wake lock and wait for Xiaomi he pleases to release the kernel code.

I do not want plus Xiaomi nor given .....
[Mi 3 General] Riichard63:
Try to install the app called cool tool and set as bar cpu frequency, and CPU load (activate the option to separate each core). Launch an other antutu and you may see why performances decreased.
[Mi 3 General] The Dork Knight Rises:
You used to get 44-45k on a Mi3w on Ivan's 5.0? I never got more than 38k...

BTW, the reboot situation is pretty weird for me. I use the method by [MENTION=5072699]i snort flour[/MENTION] (I think it was him), where you put your phone to sleep, cover the top part (sensors) then randomly tap the screen about 20-30 times, press capkeys, then uncovering sensors, instantly press power button. Got reboots about 7-8 times, but not this time. Now I'm in system2, about 18 mins up, with around nine min deep sleep....no reboot yet...

EDIT: REBOOT!
[Mi 3 General] kancrutt:
anyone knows how to disable percentage battery indicator?
[Mi 3 General] The Dork Knight Rises:
Agreed. While I share the attitude that we shouldn't lie around waiting, I am hoping Xiaomi releases the sources ASAP, that should solve most of our problems...

They released for the Redmi 1S today, so they're probably gonna keep their word about releasing Mi3/4 sources in Q1.:fingers-crossed:
[Mi 3 General] SkipperRyujin:
Well, in my phone it didnt reboot again, checked it by reboot logger. But if you try the method to make the phone reboot, it may so, bcoz the touch trouble like i mentioned before. But in past 2 day, the only reboot that happen in my device only when i install zero launcher. And until now, it didnt reboot again until the phone run out of power.

You can also change all suspend and idle mode of cpu0 to 0 (like the one in cm12) to prevent cpu entering full deepsleep mode
[Mi 3 General] The Dork Knight Rises:
Off topic, but happy new year to all of you! Have a great year!

(And hopefully Mi3 sources will be out this year... though i wish we all stay like this, solving bugs together! :highfive:)
[Mi 3 General] vasishath:
Same 2 u bro.. And happy new year to everybody here.. :) :)
[Mi 3 General] The Dork Knight Rises:
I may try that.

I did get two random reboots without method (in pocket, with touch screen towards my body, so probably by touch errors), but usually i get around 2-3 hours of deep sleep before that, so i think I'll actually keep it like this, and see if it reboots even once overnight. If it does I'll know that my phone reboots even without touch errors, so I'll try setting suspend and idle mode to 0.
[Mi 3 General] Tomi_Ohl:
Thanks, I've successfully followed your instructions, now my phone goes to deep sleep and doesn't reboot :good:

But I have one question: that calib.cfg file should be in system/etc. You recommend us to backup files, however there wasn't such file, so I've just added it. Is it okay like that, or did I miss something?

Edit: Happy New Year to everyone who have entered new year (it's 8:54PM in my country)
[Mi 3 General] i snort flour:
Yeah you still get random deep sleep reboots for me every 3 to 5 hours but it virtually eliminated deep sleep crash reboots (which is what I call it when causing it to manually random reboot at will) so there is definitely something there worth looking into but my theory is a failure so far. I'm waiting for my lawyer to call me back as I just got done going to court this morning once I get a call from him I'll test a couple more things to see if I can't come up with merging the non rebooting system 1 and the non crashing rebooting on system 2

Sent from my Xiaomi MI3W
[Mi 3 General] vasishath:
Hey.. we probably forgot that Ivan is going to release an update this year.. ( as he said previously ).. probably that will fix the bugs.. for the time being :)
[Mi 3 General] i snort flour:
The only thing is Ivan's roms are barebone and suck dingleberries. it's hard to have bugs when your rom contains nothing more than just enough to make the os run; plus cm cancro team has solved random reboot problems without having kernel source code. This is like building a luxury car out of junk yard parts compared to a guy who built a car in a factory with no luxuries and the luxury car isn't broke down on the side of the road like the non luxury car currently is
[Mi 3 General] colocynth:
Hey, I snort flour bro, thank you for your contribution to the ROM first. I love to read your posts as they are very useful for me to understand the development of this ROM.

But, do you mind add some commas to your sentences? It's time consuming to read paragraphs without commas. I have given up some of your long posts. I think I have missed your important msg.

Would you mind?
[Mi 3 General] i snort flour:
I'm probably not the right person to be listening to. I try to help where I can but others have far more knowledge than I. I'm just a bored felon that lost his job and can't do drugs anymore.
[Mi 3 General] colocynth:
u have been very helpful. Thx for that [emoji106]
[Mi 3 General] deepesh.tickoo:
Hahahahaha!! That mafe me laugh! ???

BTW back on topic please! [emoji14]
[Mi 3 General] i snort flour:
Your welcome. Sometimes you just need to think outside the box and try things that seem crazy. Just look at things from a logical perspective. Sometimes the outcomes will truly surprise you. Usually they will not work out, but it'll start you down the right path through process of elimination. This will also build your knowledge and spark curiosity. Keep at it
[Mi 3 General] srvoleti:
Please keep on posting your findings lol!
[Mi 3 General] The Dork Knight Rises:
Lol. But I'm still not switching to CancroCM till they fix the boot delay and battery drain. This Ivan's is stabler for me.

But there's one thing i disagree with. You say CancroCM has 'solved' random reboot problem. But the thing is, i honestly think they're using a workaround too... That's the reason the Miscellaneous battery drain exists, because somehow, the CPU is being kept awake when it shouldn't be awake.
[Mi 3 General] i snort flour:
Battery drain was taken care of on last alpha build beta builds took care of 3 other bugs but I'm sticking with last alpha build for certain reasons mainly app lag and boot time my current bout time is about 3 to 4 minutes
[Mi 3 General] i snort flour:
They aren't using a workaround because the work around prevented it going into deep sleep and miscellaneous bug has been gone for some time you need to clean install including factory reset. The mm-qcamera-daemon does exist however but has an easy solution and only needs to be done whenever you perform a full charge and disconnect charger. It happens every time the battery stats are reset is what I figured out. Maybe they will write a script to permanently take care of this with this knowledge. Here is a picture to prove there is no wake lock work around being used and a previous pic of misc not present.

Sent from my MI 3W
[Mi 3 General] SkipperRyujin:
yes its not exist there. i only copying from MIUI since the line in build.prop accesing it but it doesnt exist before.

Sorry for late reply coz i'm out of town since 1st january :D. And now i got different error with the EGL and adrenoEGL :'(
[Mi 3 General] The Dork Knight Rises:
No, I'm not taking about a WakeLock workaround, m talking about the workaround [MENTION=4276944]SkipperRyujin[/MENTION] shared, keeping one core from going idle. Because that doesn't seem to count as a wake lock, but still drains battery (but not while using, only had 6% overnight). Because i still have misc drain. But no mm-qcamera-daemon though.

I'm using DEODEXED build of beta. Which btw, boots in two minutes, but has some lag.
[Mi 3 General] i snort flour:
I'm not the sharpest tool in the shed but if 1 of the 4 cores wasn't going into idle state and staying active it would be running at the lowest frequency which is 300mhz and would not register as deep sleep in cpu spy. However it would be registering at 300mhz. BTW keeping 1 core from going idle is the exact definition of wake lock. All in all its called cpu spy not core spy, your cpu has 4 cores rated at a total processing speed of 2.3ghz which is a rounded up number from 2265mhz. I know each core is its own cpu but to explain how they tie into the system bus and ram operation would take multiple pages to thoroughly explain properly

Sent from my MI 3W
[Mi 3 General] The Dork Knight Rises:
While, it struck me weird too, that's exactly what you do by editing the init.qcom.post_boot.sh, prevent cpu0 from going idle, and it still shows up as deep sleep (and reboots too)
[Mi 3 General] srvoleti:
While editing the init.qcom.post_boot.sh to prevent cpu0 from going idle, do you have random reboots?
[Mi 3 General] The Dork Knight Rises:
Alas, yes, but only if I use the Method. (Covering sensor and randomly tapping screen multiple times, etc etc)

There doesn't seem to be any permanent way to stop reboots except wakelocks...

UPDATE: After editing init.qcomm.post_boot.sh to prevent idle and suspend states for cpu0 last night, I found a 27% Miscellaneous battery drain this morning...on Ivan's ROM!! This is pretty damning evidence, CancroCM probably use the same method...
[Mi 3 General] ashish289:
From Ivan's sina weibo

Originally planned to engage in machine years ago, the situation got even worse a little lollipop stable version meters 3W / 4W meter, do not know Shashi Hou can get.*Somewhat serious problem, no idea.*Reckon ago is impossible to get a first look stood there thinking.

weibo.cn/1697247850/BEDyQ2MYJ
[Mi 3 General] Armin_van_buuren:
I think it will take long time to see a version of Ivan .... if you see it.
[Mi 3 General] colocynth:
My translation:

originally planned to release a stable lollopop version for 3w, 4w before new year (Chinese new year, I think. To be start on Feb 19). Face big problems. Can't find any hints to solve them. Not likely to find out before new year. Leave it aside until got some clues
[Mi 3 General] Archmag3:
This basically translate to : "let xiaomi release the kernel sources, only after that I will release stable lollipop."