[KMA KERNEL][CM-11.0 | .283 blobs][SM 4.9 | Graphite][22-10]

[macia10]

Hi,
Where can I find 91mpdecision file?

 

[deepongi]

Hi,
Where can I find 91mpdecision file?

https://www.dropbox.com/s/ho6z0uf8fx24qrj/91mpdecision

 

[Tobbyax]

Here, with today build, Spotify FC immediatly on launch. Am I the only one?
Reverted to the previous build (by Infected), and Spotify works fine.

 

[thomas1991_12]

Here, with today build, Spotify FC immediatly on launch. Am I the only one?
Reverted to the previous build (by Infected), and Spotify works fine.

What does the log say?

 

[rlees85]

Last build wouldn't boot for me. Stuck on Cyanogenmod logo (screen brightness still bright - it didn't get to the bit where it goes to auto and dims a bit). Unfortunately, too soon in the boot process for a logcat.

I am assuming it is because I had ART enabled before trying to flash. So this latest build may not be ART friendly Please don't take this post as a bug report, just a warning to others!

The build before - the one infected posted - does boot interestingly...

EDIT:

Also something about MP-DECISION on Infected's build, it looks like it attempts to start the MPDECISION daemon (in logcat) but fails due to "pm_qos file missing". This occurs weather the INIT.D script is present or NOT.

I managed to get the init.d script working by adding a sleep 60 statement to make it wait 60 seconds after bootup before trying to run mpdecision. It then works, and the pm_qos error is not present in logcat.

What I am saying is, I think mpdecision could work "out the box" without any init.d scripts on infected's build if it just tries to start it a few seconds later...

To clarify:
infected build + no init.d: logcat reports mp-decision tries to start but fails due to pm_qos file missing.
infected build + init.d: same again
infected build + my custom init.d instead of the provided one: mp-decision appears to attempt to start twice in the boot process. first early in the boot process but fails due to pm_qos and was not initiated by init.d. But when my script tries to start it after a 60 second wait it starts successfully.

EDIT again:

99mpdecision

#!/system/bin/sh
# Start the mp-decision daemon if it is not already running...
# 

log -p i -t mpdecision "Waiting boot to complete... (60 seconds)"
sleep 60 > /dev/null


ps mpdecision | grep mpdecision > /dev/null
if [ $? -eq 0 ]; then
  log -p i -t mpdecision "Process is already running!"
else
  log -p i -t mpdecision "Process is not running, starting..."
  su -c "/system/bin/mpdecision" &
fi

 

[Tobbyax]

What does the log say?

Here is the logcat.
I don’t know if it’s possible/useful to grab the app crash log.

 

[thomas1991_12]

Here is the logcat.
I don’t know if it’s possible/useful to grab the app crash log.

Is this a fresh install? If not try that, else provide dmesg/kmsg logs.

 

[Tobbyax]

Is this a fresh install? If not try that, else provide dmesg/kmsg logs.

If you mean having wiped everything: no it’s not. I can try a clean install, but it takes time since I have to backup everything. But I’ll try, since nobody else seems to encounter this issue…

 

[thomas1991_12]

New build and redid first post.

 

[kaotomut]

New build and redid first post.

Your rom is really interesting. I have never flashed CM Rom on my my Xperia Z before though. Would you mind update your first page about step to step to get fully completely installation includes some screenshots?
Thanks

Sent from my C6603 using Tapatalk

 

[thomas1991_12]

Your rom is really interesting. I have never flashed CM Rom on my my Xperia Z before though. Would you mind update your first page about step to step to get fully completely installation includes some screenshots?
Thanks

Sent from my C6603 using Tapatalk

I suggest you follow this wiki: http://wiki.cyanogenmod.org/w/Install_CM_for_yuga

 

[Tobbyax]

Is this a fresh install? If not try that, else provide dmesg/kmsg logs.

With your today release, fresh install:

• impossible to make a call (5 bars goes to empty triangle, message callFailed_outOfService “Out of service area”), receiving calls work fine
• spotify still FC

Please find dmesg and logcat.
Thanks in advance!

 

[Deleted member 3358925]

With your today release, fresh install:

• impossible to make a call (5 bars goes to empty triangle, message callFailed_outOfService “Out of service area”), receiving calls work fine
• spotify still FC

Please find dmesg and logcat.
Thanks in advance!

I can confirm the "impossible to make a call". I had the same problem with the build before this one.
Flashed back the official CM11 nightly cause I needed to call someone, which worked again, so it doesn't seem to be something in the CM code-base.

 

[SuperHanss]

With your today release, fresh install:

• impossible to make a call (5 bars goes to empty triangle, message callFailed_outOfService “Out of service area”), receiving calls work fine
• spotify still FC

Please find dmesg and logcat.
Thanks in advance!

@thomas1991_12

This commit fixes outgoing calls: https://github.com/AOSPA-legacy/android_device_sony_qcom-common/commit/fc7f9ea343e9a909e4f467fb82e9b2ab9a51074a

 

[thomas1991_12]

Thans for the headsup. Here is a fixed build:
https://docs.google.com/file/d/0B7XCSgymRoP0V1Y1cE8yNTNuN1E/edit?usp=docslist_api

Sent from my C6603 using xda app-developers app

 

[hrulik]

Thans for the headsup. Here is a fixed build:
https://docs.google.com/file/d/0B7XCSgymRoP0V1Y1cE8yNTNuN1E/edit?usp=docslist_api

Sent from my C6603 using xda app-developers app

cant download, "You need permission" message

 

[junixquiaoit]

How to install guys?

 

[buche23]

How to install guys?

Wait for the latest build (the one two posts up that is currently not accessible as otherwise you won't be able to make calls.

Follow this, as suggested by Thomas.

http://wiki.cyanogenmod.org/w/Install_CM_for_yuga

 

[thomas1991_12]

This build should be fine:
https://drive.google.com/file/d/0B7XCSgymRoP0R0F1RkFKSElrcWs/edit?usp=sharing

 

[Tobbyax]

This build should be fine:
https://drive.google.com/file/d/0B7XCSgymRoP0R0F1RkFKSElrcWs/edit?usp=sharing

I confirm this release solved the call issue.
But I still have Spotify FC. I’ve made new logs if needed.

If someone wants to help me [dis]confirm the Spotify issue, it’s very simple: no need of an account or anything. Just download and install the Spotify app, and try to launch it, it may crash immediately. Thanks in advance for any help about that!