12 replies to this topic

[skylos]

First of all thx a lot for all the hard work! I do appreciate it.

Unfortunately the new release doesn't work at all for me. the SIM unlock screen pops up for a few seconds an then the boot screen reappears an stays while logcat shows lots of this:

I/ServiceManager(  814): Waiting for service media.audio_flinger...
I/ServiceManager(  825): Waiting for service media.audio_policy...
I/ServiceManager(  814): Waiting for service media.audio_flinger...
I/ServiceManager(  825): Waiting for service media.audio_policy...
I/ServiceManager(  814): Waiting for service media.audio_flinger...
I/ServiceManager(  825): Waiting for service media.audio_policy...
I/ServiceManager(  814): Waiting for service media.audio_flinger...
I/ServiceManager(  825): Waiting for service media.audio_policy...
W/AudioSystem(  814): AudioFlinger not published, waiting...

Any ideas?

BTW it would be nice to know, wht the .2-rease was supposed to fix.

Best regards
Kai

[ciwrl]

"CyanogenMod 7.1.0.2 is available for SEMC 2011 devices Fixes RIL and button lights."

[sulkie]

 skylos, on 25 October 2011 - 02:43 PM, said:

First of all thx a lot for all the hard work! I do appreciate it.

Unfortunately the new release doesn't work at all for me. the SIM unlock screen pops up for a few seconds an then the boot screen reappears an stays while logcat shows lots of this:

I/ServiceManager(  814): Waiting for service media.audio_flinger...
I/ServiceManager(  825): Waiting for service media.audio_policy...
I/ServiceManager(  814): Waiting for service media.audio_flinger...
I/ServiceManager(  825): Waiting for service media.audio_policy...
I/ServiceManager(  814): Waiting for service media.audio_flinger...
I/ServiceManager(  825): Waiting for service media.audio_policy...
I/ServiceManager(  814): Waiting for service media.audio_flinger...
I/ServiceManager(  825): Waiting for service media.audio_policy...
W/AudioSystem(  814): AudioFlinger not published, waiting...

Any ideas?

BTW it would be nice to know, wht the .2-rease was supposed to fix.

Best regards
Kai

I'm just guessing, but it could be a mistake of theirs to even put this ROM in Mini Pro section. Because if this build is the same that the developers are posting on xda forums ( http://forum.xda-dev...d.php?t=1226715 ) then it requires SEMC 4.0.2.A.0.42 rom which is released for all devices except for Mini Pro. It will be officially released in november by Sony, then you will need to flash that rom and then the new CM.
Here's a project page if you want a detailed look at the changelog, http://code.google.com/p/freexperia/. Again assuming that 7.1.0.2 and FXP043 are the same builds.

Edited by sulkie, 25 October 2011 - 03:23 PM.

[skylos]

That would explain, why it crashes when it tries to turn on the mobile reception. And as far as I could see it didn't even fix the button lights. I must say, the Mini Pro port is not yet quiet where the HTC Tattoo port was, when it was released.

[sulkie]

 skylos, on 25 October 2011 - 03:53 PM, said:

That would explain, why it crashes when it tries to turn on the mobile reception. And as far as I could see it didn't even fix the button lights. I must say, the Mini Pro port is not yet quiet where the HTC Tattoo port was, when it was released.

If you are refering to lights under soft keys, that can be fixed easily.
If however you are refering to hardware keys then the "easiest" solution is to use scriptmanager to turn them on and off manually. Not that bad since you can place widget buttons on homescreen.
I can give you details if interested.

Edited by sulkie, 25 October 2011 - 04:25 PM.

[motokoza]

Can you post details about it here please?

Edited by motokoza, 25 October 2011 - 04:58 PM.

[sulkie]

For lights under soft keys:
You have to edit "/system/etc/hw_config.sh".
Replace these lines:
echo 8000 > $dev/button-backlight-rgb1/max_current
echo 8000 > $dev/button-backlight-rgb2/max_current
With this one:
echo 2000 > $dev/button-backlight/max_current

Or this one if you dont want the light
echo 1 > $dev/button-backlight/max_current

Make sure it's to the space and letter exact.

I have a thread on XDA with those files already modified, so you would have to only replace it with any kind of file manager with root capability. http://forum.xda-dev...d.php?t=1300982

For hardware keys:
Detailed instructions here:
http://forum.xda-dev...00&postcount=14

Edited by sulkie, 25 October 2011 - 05:23 PM.

[motokoza]

Thx for that!

[Husain Zaidi]

Thanks a million for letting know man, would have updated otherwise :/

[sulkie]

Hey guys, 7.1.0.2. / FXP043 appears to be working. No issues reported so far. Check here for details http://forum.cyanoge...e-issue-so-far/

[royr719]

Hi. I just rooted my Xperia mini pro using the zergRush exploit with doesn't need to unlock the bootloader.
My question is: Should I still unlocked the bootloader in order to install CyanogenMod 7? Thanks.

[sulkie]

 royr719, on 30 October 2011 - 10:04 PM, said:

Hi. I just rooted my Xperia mini pro using the zergRush exploit with doesn't need to unlock the bootloader.
My question is: Should I still unlocked the bootloader in order to install CyanogenMod 7? Thanks.

You have only rooted your installed ROM but for installing any other ROMs which were not signed by SonyEricsson bootloader must be unlocked.

[royr719]

 sulkie, on 31 October 2011 - 09:17 AM, said:

You have only rooted your installed ROM but for installing any other ROMs which were not signed by SonyEricsson bootloader must be unlocked.

I see! Thanks a lot sulkie .