yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Original Android Development] Destroyedbeauty:
Hm, I will continue looking after the best governor / IO combo for the msm_mpdecision hotplug driver regarding battery life..

EDIT: Found it! I can recommend everyone to try out Intelliactive and SIO combo! Amazing battery life and smooth as butter!
[Xperia Z1 Original Android Development] omegahanggara:
Running v17 for 2 days, and I can confirm that ondemand governor is the most stable than the others. I get heavy lag on intellidemand and intelliactive, especially when using camera which is intolerable for me.
[Xperia Z1 Original Android Development] Destroyedbeauty:
I am running Intelliactive / SIO combo right now and I got no lags at all. My GPU is also underclocked a little - no lag at all.
[Xperia Z1 Original Android Development] omegahanggara:
Weird. Is your governor tweaked?
[Xperia Z1 Original Android Development] Destroyedbeauty:
Nope, I am using the stock presets for the Intelliactive governor that's bundled with Doomkernel v17. I was on tweaked Ondemand / Deadline combo before that on the custom msm_mpdecision hotplug driver and got some pretty nasty battery juice drain, and now when I changed to Intelliactive / SIO - my phone is acting like a dog in a leash. No weird battery drain, no lag, no stuttering and no performance issues. Smooth as butter and rapidly fast.

Maybe my usage patterns is best responded & executed by using an Interactive based governor and a more simple IO Scheduler (=like the SIO I/O scheduler..), or it's just my luck. Who knows..

Have you renamed the mpdecision binary in /system/bin to mpdecision_bck?
[Xperia Z1 Original Android Development] omegahanggara:
Yes, I have renamed that. I'll try your settings and see if I there's any different. I'll post here again after 12 hours. Thanks anyway.
[Xperia Z1 Original Android Development] lbaquerizo:
How is it that I have to rename mpdecision.bck or mpdecision_bck and what about permissions?

From my Z1 UB

RomAur v 7.1

DooMkernel v 17

XZDualRecovery 2.7.123
[Xperia Z1 Original Android Development] Destroyedbeauty:
I followed the official guide by show-p1984 in his Bricked kernel for Nexus 5 / Hammerhead and saw that the kernel installer renamed the mpdecision to mpdecision_bck and I did guess that it was the correct way to rename it..

Permissions should be like this (as they was before you renamed the binary file); rwxr-xr-x / 0755!

EDIT: [MENTION=2784807]DooMLoRD[/MENTION] Any chance that you'll add the multicore & hotplug aware PegasusQ & Hotplug CPU governors in v18?

I saw that someone did mention a few pages back in this thread that those two CPU governors can take over the hotplug policy completly if there is no hotplugging driver enabled, and this would be awesome to try out ourself.. Right? :)
[Xperia Z1 Original Android Development] omegahanggara:
Just rename it, don't change the permission. If it's changed, fix the permission to 0755. So just in case you need to back to v16 and you want to use mpdecision, it should be working.
[Xperia Z1 Original Android Development] lbaquerizo:
How do I fix the permission

From my Z1 UB

RomAur v 7.1

DooMkernel v 17

XZDualRecovery 2.7.123
[Xperia Z1 Original Android Development] omegahanggara:
From terminal emulator

su
mount -o remount,rw /system
chmod 0755 /system/bin/mpdecision
mount -o remount,ro /system
[Xperia Z1 Original Android Development] lbaquerizo:
I have tried but no luck terminal says that the file doesn't exist. Thanks anyway gonna stay like this until I can figure it out

From my Z1 UB

RomAur v 7.1

DooMkernel v 17

XZDualRecovery 2.7.123
[Xperia Z1 Original Android Development] omegahanggara:
How if

ls /system/bin | grep mpdecision
[Xperia Z1 Original Android Development] lbaquerizo:
Finally I got it looking it up on the net

So now that I have everything what is the best configuration for battery and smoothness and for performance

From my Z1 UB

RomAur v 7.1

DooMkernel v 17

XZDualRecovery 2.7.123
[Xperia Z1 Original Android Development] omegahanggara:
Best of luck! For hints:

linux permission calculator

You're welcome ;)
[Xperia Z1 Original Android Development] lbaquerizo:
No need for terminal, Su commands are not my favorite

From my Z1 UB

RomAur v 7.1

DooMkernel v 17

XZDualRecovery 2.7.123

---------- Post added at 03:50 PM ---------- Previous post was at 03:47 PM ----------

Found this article from 2001

http://www.elated.com/articles/understanding-permissions/

Understanding Permissions

From my Z1 UB

RomAur v 7.1

DooMkernel v 17

XZDualRecovery 2.7.123
[Xperia Z1 Original Android Development] togcbu:
64gb sd card issues

is the problem i have no with the 64GB sd card related to this kernel? the previous versions didn't give me any problem. can't delete files, can't format the card.
[Xperia Z1 Original Android Development] lbaquerizo:
Buddy you posted the same on RomAur thread. Blaming the ROM now is the kernel. Try to format it in your PC and problem solved. It never crossed your mind that you might have a bugged SD card

From my Z1 UB

RomAur v 7.1

DooMkernel v 17

XZDualRecovery 2.7.123
[Xperia Z1 Original Android Development] Ashray_Vk:
Back to v16, my cpu frequency used to get stuck at highest frequency :/

Tried many governors too
[Xperia Z1 Original Android Development] Destroyedbeauty:
Sure that you doesn't have both Qualcomm MP-Decision and showp msm_mpdecision enabled at the same time?
[Xperia Z1 Original Android Development] Ashray_Vk:
Followed the instructions including the one where you have to rename the mpdecision file, still, sometimes, it gets stuck at a high frequency.
[Xperia Z1 Original Android Development] Destroyedbeauty:
Which governor and IO combo are you at?
[Xperia Z1 Original Android Development] Ashray_Vk:
Tried default ones, tried with ondemand too.

Sent from The Sony Beast powered by DoomKernel
[Xperia Z1 Original Android Development] Destroyedbeauty:
Maybe the CPU Boost drivers that is misbehaving / causing conflicts..
[Xperia Z1 Original Android Development] Ashray_Vk:
Have you switched it off? The boost control in the mpdecision control?

Sent from The Sony Beast powered by DoomKernel
[Xperia Z1 Original Android Development] pranii23:
Happened with me - 64gb MicroSD

The same thing happened with me while i was using 64GB Sandisk Class 10.

I formatted it to exFat and been using it in Cyanogen mod. After few days of usage it became a readonly disk and it was the end of the card.

We can never format it or add/remove data from the card.

http://www.phonearena.com/news/SanDisk-says-it-produced-some-bad-32GB-and-64GB-microSD-cards_id40986
[Xperia Z1 Original Android Development] Destroyedbeauty:
No, the CPU Boost driver I am speaking about is not a part of the msm_mpdecision driver..

Pm me!
[Xperia Z1 Original Android Development] pemell:
[MENTION=2784807]DooMLoRD[/MENTION]

I have some spamming in my logcat:

- Couldn't load memtrack module

and

- QCOM PowerHal Failed to acquire lock (happens every time I touch the screen). Answering myself here: The powerhal message is normal. My kernel does the touch boost completely internal, the powerhal just complains that it cannot initiate the touch boost with the qcom mpdecision disabled.

Why is that? Thanks
[Xperia Z1 Original Android Development] pemell:
Okay [MENTION=2784807]DooMLoRD[/MENTION]

Made some more testing with the msm_mpdecision.

The huge issue causing lags is because only one core will be online. The other cores won't get hotplugged, not for me at least. I guess this is what causing other users to report lags too.
[Xperia Z1 Original Android Development] Destroyedbeauty:
Strange, I have not got any single lag on my Z1 with the msm_mpdecision driver. Everythink is slinky, smooth and rapidly flying on my device, and that is even with underclocking down to 1728 Mhz on CPU side..
[Xperia Z1 Original Android Development] pemell:
use system monitor and see if core 1-3 goes online please.

also I guess you made sure to rename the default mpdecision so that the custom one actually gets used?
[Xperia Z1 Original Android Development] hlavicka82:
I also noticed that with msm_mpdecision the cores 1-3 do not get plugged no matter what I did. I also tried to lower the thresholds but it did not help. Maybe the msm_mpdecision has trouble to read the run queue thresholds of the cpus?
[Xperia Z1 Original Android Development] Destroyedbeauty:
Yes, I did rename the default mpdecision binary to mpdecision_bck and rebooted my phone, beside some minor additional CPU based tweaks / modifications..
[Xperia Z1 Original Android Development] pemell:
lol you didn't answer if core 1-3 goes online. But above you there's one more user confirming this.
[Xperia Z1 Original Android Development] Destroyedbeauty:
Sorry and lol on yourself..

I was going to check if it was the same for me regarding core 1-3 and I can verify it - only core0 is active and is hell a lot of time at highest frequency (in my case - 1728 Mhz)..

This explains why my battery life went from good to awful with screen off..
[Xperia Z1 Original Android Development] pemell:
So this is now confirmed. It must be regarded as a critical issue and I've contacted doomlord about it.

Thing is that if you don't touch the default mpdecision (don't rename it) the custom one will kick in at some point.

If you want to disable it at boot you need to use the init script posted earlier in this thread.
[Xperia Z1 Original Android Development] TheKnux:
I popped in my T-Mobile SIM and everything works fine. Doesn't that mean it's unlocked?
[Xperia Z1 Original Android Development] gregbradley:
no, sim unlock and bootloader unlock are different things

Please do what I said above
[Xperia Z1 Original Android Development] gregbradley:
ok, so that shows that it is not unlocked yet but you are allowed to do it.

Make a backup of your TA and then goto here to unlock.

Please ensure you read the everything including the warnings
[Xperia Z1 Original Android Development] TheKnux:
I already read about it and understand it, but in your opinion, what are the benefits of unlocking other than flashing different kernels?
[Xperia Z1 Original Android Development] gregbradley:
that's it, but with custom kernels you can do so much....

If you need to know more then please ask in the guides.

EDIT, you may also want to remove that picture now, as you are sharing your IMEI number with the world
[Xperia Z1 Original Android Development] gregbradley:
you may need to know that root comes before boot.

you can root your phone following any of the several guides in the general section

Unlocking the bootloader and installing custom kernels is something else
[Xperia Z1 Original Android Development] YamazakiRobert:
question

its not possible to change the ta mount point to ta.img on the partition start script like the mods for data2sd?

or change the ta mount point to us restore the ta on other partition of the phone (like the fota kernel, or create a extra partition on extsd...)
[Xperia Z1 Original Android Development] mirhl:
already tried
[Xperia Z1 Original Android Development] Jacob_Bentzen:
Why is it saying this??

OKAY [ 14.907s]

writing 'boot'...

FAILED (remote: Command not allowed)

finished. total time: 14.910s

---------- Post added at 10:57 PM ---------- Previous post was at 10:57 PM ----------

Why is it saying this?? :(

OKAY [ 14.907s]

writing 'boot'...

FAILED (remote: Command not allowed)

finished. total time: 14.910s
[Xperia Z1 Original Android Development] gregbradley:
Have you unlocked your bootloader?
[Xperia Z1 Original Android Development] Jacob_Bentzen:
No I didn't because then it would break my camera. (Working again)
[Xperia Z1 Original Android Development] gregbradley:
I wish I had a picture with three...
[Xperia Z1 Original Android Development] TeamR:
Got one ! :p

**********************************

What about the double tap feature you're talking about on this previous post ??
[Xperia Z1 Original Android Development] jos_031:
Please remove the picture. you are not supposed to share imei number
[Xperia Z1 Original Android Development] gregbradley:
He is perfectly entitled to share it if he wants, its his number. Its just not advisable.
[Xperia Z1 Original Android Development] jos_031:
imagine some terrorist cloned his imei number and used the phone... just saying ... i know it is not a rule... but it is better to think it as a rule than advising ..
[Xperia Z1 Original Android Development] DooMLoRD:
ITS FIXED! FINALLY!

Xperia Z1 bootloader-camera bug is now fixed on the 4.3 update!

finally can resume my custom kernel work!

new kernel will be released when sources are available :)

regards,

DooMLoRD
[Xperia Z1 Original Android Development] DeanBoro:
really?
[Xperia Z1 Original Android Development] Destroyedbeauty:
True!

For those that doesn't know how to disable the msm_mpdecision driver - put those lines in a empty, UNIX-code supported file and save it inside the init.d folder with 0777 permissions and leave it as it is, until [MENTION=2784807]DooMLoRD[/MENTION] fixes this critical issue..;

(# Disabling of showp1984 open source msm_mpdecision replacement module..)

echo 0 > /sys/kernel/msm_mpdecision/conf/boost_enabled

echo 0 > /sys/kernel/msm_mpdecision/conf/enabled

echo 0 > /sys/kernel/msm_mpdecision/conf/scroff_single_core

EDIT: Use Root browser or any root enabled file browser with capability to create empty files!
[Xperia Z1 Original Android Development] pemell:
It's funny how you can be disillusioned. For a while I thought the device was running smooth and fast on the custom mp decision (even made a post about it some page ago). But I knew something was not all right with it.

Same with you I guess? :)

I haven't used System Monitor very much in the past (I love the floating window) but it's very informative. Now I'm playing around with governors to see how the cpu behaves in my apps.
[Xperia Z1 Original Android Development] DooMLoRD:
well if u dont disable the stock mpdecision binary there will be lots of conflicts... i have disable the stock mpdecision in kernel source (it never get compiled) but the accompanying mpdecision binary is still there and causes a lot of issues..
[Xperia Z1 Original Android Development] Destroyedbeauty:
Haha, I thought everything was working because I did check the CPU Spy app a lot and everything looked fine there. Then I installed the CPU-Z app and was horrified with the core misbehaving.. O.o

Well, now back on default QC MP-Decision with my favourite Intelliactive / SIO combo and everything is rock solid with proper core managment. And that battery leeching 1190 Mhz touch boost thing on top of that.. ;)
[Xperia Z1 Original Android Development] pemell:
Doesn't matter. Even if you disable the stock mpdecision binary, the hotplugging in msm_mpdecision don't work. This making the device run on one core only.

What is not very clear is that you have to disable msm_mpdecision to make it run on the stock mpdecision.

You should really just remove the msm_mpdecision.
[Xperia Z1 Original Android Development] John.D..:
So you can use ****** mpdecision or not?)
[Xperia Z1 Original Android Development] pemell:
yes, you can use the msm_mpdecision, but your device will run on one core only (thus hurt the user experience alot). try it yourself and see. I'm trying to explain this to DooMLoRD but I don't know if he gets me.

1. There seem to be some kind of idea that disabling the stock qcom mpdecision fixes it. It doesn't. The msm_mpdecision will still make your device run on one core only.

2. If you don't disable msm_mpdecision at boot it will kick in at some point and cause the hotplugging (one-core) issue.
[Xperia Z1 Original Android Development] DooMLoRD:
the custom msm_mpdecision will kick in as intended but it prefers keeping other cores down..

you can check the kernel logs

adb shell "su -c cat /proc/kmsg | grep MPDEC"

BTW... this custom msm_mpdecision driver was in testing phase for this kernel v17... future releases will NOT have this driver...
[Xperia Z1 Original Android Development] John.D..:
Hmm, that's just like I intellidemand Governor and all cores are working when the screen is on but untouched runs on a single core 300 MHz, and in the process all the work, in turn ... only effect of any, effect on the battery and bad performance below stock kernel: (BUT nexus 5 also works ....
[Xperia Z1 Original Android Development] pemell:
It don't keep the cores down, it disables them and they won't be used at all.

Anyway, don't give up ;)

prbassplayer has an interesting post for you here:

http://xdaforums.com/showpost.php?p=52597028&postcount=244
[Xperia Z1 Original Android Development] DooMLoRD:
again you should read my posts properly...

1) if u execute those commands u will see MPDEC in action (bringing up and then sleeping the cores)

2) i could remove anything i want using the ramdisk/kernel but this driver in kernel was ment ONLY for test purposes... i dont want uses with broken stock mpdecision binary...
[Xperia Z1 Original Android Development] pemell:
You don't think I did?

Use msm_mpdecision for a while then:

adb shell "su -c cat /sys/kernel/msm_mpdecision/stats/times_cpus_hotplugged"

and you really don't need to do that. just monitor the cpu's in some app like system monitor and you'll see that core 1-3 stays inactive no matter what you do with you device.
[Xperia Z1 Original Android Development] Destroyedbeauty:
Intelliplug next, Doom? :angel:
[Xperia Z1 Original Android Development] DooMLoRD:
Get me good sources of prima/pronto which will work on stock kernel sources (not CM/AOSP) and you will have intelliplug :)
[Xperia Z1 Original Android Development] Destroyedbeauty:
Perhaps Faux got anything regarding this that can help you - well, his sources / work are on Nexus 5 but both the Z1 and N5 uses the same chipset as far as I know and maybe something can be ported / converted? *hmm*
[Xperia Z1 Original Android Development] lbaquerizo:
I went back to v16 but can't seem to get all the cores up and running just one core WTF. Since v 17 is all messed up

From my Z1 UB

RomAur v 7.1

DooMkernel v 17

XZDualRecovery 2.7.123
[Xperia Z1 Original Android Development] DooMLoRD:
Hey I did some more testing and your hypothesis seems to be correct... Cores 1-3 are not waking up... No wonder the battery life was awesome ;)

Might be some issue somewhere in driver...

Recommend everyone to shift to v16 for better performance!

Reenable the mpdecision binary

Rename it back to mpdecision in /system/bin/

And incase you screwed up the permissions then it should have the following permissions

chmod 755 /system/bin/mpdecision

I will post a rollback package tonight or better release a v18 without this custom mpdecision
[Xperia Z1 Original Android Development] smartyyadav:
after using this kernel i flashed stock kernel and then my mobile began to restart again and again. So i flashed .534 and i got warnig "ignored simlock.ta" and after that my phone is not recognizing any sim and not receiving signals.

is this problem due to simlock.ta file?

how fix this issue pls help me
[Xperia Z1 Original Android Development] DooMLoRD:
Isn't .534 a very old firmware?

Please DO NOT DOWNGRADE FIRMWAREs... I remember on the Xperia Arc people permanently damaged their battery fuel gauge by flashing old firmwares!

Try flashing any latest Kitkat firmware
[Xperia Z1 Original Android Development] pemell:
[MENTION=2784807]DooMLoRD[/MENTION] I'm trying to change /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq to 2419200 by script but the value won't change. Is there some file somewhere protecting this value?
[Xperia Z1 Original Android Development] smartyyadav:
ok but pls tell did i locked my phone to any carrier? and why is it not recieving any signal?

pls help me
[Xperia Z1 Original Android Development] lbaquerizo:
Flash any KitKat Ftf via flashtools

From my Z1 UB

RomAur v 7.1

DooMkernel v 17

XZDualRecovery 2.7.123
[Xperia Z1 Original Android Development] DooMLoRD:
Will your baseband is screwed... Hopefully flashing any latest Kitkat firmware should do it
[Xperia Z1 Original Android Development] smartyyadav:
ok will try to flash kitkat firmware and tell you soon

thanx alot both of you
[Xperia Z1 Original Android Development] DooMLoRD:
DooMKernel v18 released!

changelog

reverted and removed custom MP-Decision

re-enabled Stock Qualcomm MSM MP-Decision driver

added stock mpdecision binary to recovery package (this will get flashed while flashing kernel, should fix any issues which were there while testing v17 kernel)

download links at first post!

Please do consider donating if you like my work!

please keep the advanced stock kernel recovery package on sdcard to avoid bootloops!

please keep sending in your feedback it helps me improve my kernel! constructive feedback is ALWAYS welcome!

regards,

DooMLoRD
[Xperia Z1 Original Android Development] pranii23:
v16->v18 ?

So do ppl using v16 need to update to this kernel ?

Optimisations?
[Xperia Z1 Original Android Development] DooMLoRD:
yup all users v16 & v17 SHOULD update to v18!!

v18 is compiled using GCC 4.9.1 Linaro toolchain optimized for Cortex-A15...
[Xperia Z1 Original Android Development] lbaquerizo:
If I turn on mpdecision with FauxClock al my cores are offline. If I turned off all of them are back is this normal? (^o^) , sorry for the question.

From my Z1 UB

RomAur v 7.1

DooMkernel v 18
[Xperia Z1 Original Android Development] omegahanggara:
Yes
[Xperia Z1 Original Android Development] Ame123:
Can anybody help me on how to get back to stock kernel??
[Xperia Z1 Original Android Development] DooMLoRD:
Flash only kernel.sin using FlashTool

Btw why going back to stock kernel? Any issues you facing?
[Xperia Z1 Original Android Development] Ame123:
Yeah i m kind of new to this yesterday only unlocked my bootloader for flashing your kernel but i dont know what setting should i use. Phones getting warm. It will be good even if you provide me some good setting for overall good battery temp and normal performance
[Xperia Z1 Original Android Development] Klaus N.:
[MENTION=2784807]DooMLoRD[/MENTION]

v.18 works fine, no issues so far. Thanks for another good job!

Just one question: Will v.18 also work with .761 fw? Nevermind, I'll try it with RomAur v.8.0 after work...
[Xperia Z1 Original Android Development] omegahanggara:
Wipe cache and dalvik cache. Boot up the phone, use default kernel setting, wait at least 12 hours so your phone can adapting with new kernel. Once it stable (No warm issue), reboot, and try to tweak kernel setting.
[Xperia Z1 Original Android Development] Ame123:
Hmmm i didnt wipe but now i have changed the settings somewhat. I am using intelliactive and some intellithermal setting its quite good now veryy happy thanks to doomlord
[Xperia Z1 Original Android Development] lbaquerizo:
Finally got kernel up and running the way I like it. Had to upgrade the Rom but it was worth it. Now everything is silky smooth. DOOMLORD you're a genius + RomAur is a beautiful combo [emoji2]

From my Z1

RomAur v 8 UB

DooMkernel v 18
[Xperia Z1 Original Android Development] avs333:
Yup. Has anyone tried to contact sony for that matter? What do they mean by opensource without posting one of the key drivers...

I'd write to them anyway (never mind modversions as a last resort), but they don't respond to my mails anymore after a row on z1c hootbooting with no carrier (hey DooMLoRD, does it work okay on z2 now you have it?).

[MENTION=4598683]Destroyedbeauty[/MENTION], doubt that n5 sources would be more helpful than those non-stock ones we already have for z1.
[Xperia Z1 Original Android Development] Destroyedbeauty:
How-to contact them? What is their email to their Android dedicated / cellphone / tablet section of the company?
[Xperia Z1 Original Android Development] avs333:
developer.world@sonymobile.com. And there are some other options at http://developer.sonymobile.com/about/how-do-i-get-in-contact (e.g. forum, but it's rather user-oriented than technical).
[Xperia Z1 Original Android Development] Destroyedbeauty:
Thanks! Will send them an email asap and see what they can do..
[Xperia Z1 Original Android Development] dbolivar:
What about the sources in sonyxperiadev's GitHub and CodeAurora? Are they only meant for CM/AOSP?

https://github.com/sonyxperiadev/prima

https://www.codeaurora.org/cgit/external/wlan/prima/