Jump to content


Photo

Ported Rom Help Required re error AudioPolicyService not published, waiting...

- - - - -

  • Please log in to reply
10 replies to this topic

#1
robt77

robt77

    Diehard

  • Members
  • PipPipPipPip
  • 343 posts
  • Gender:Male
  • Location:Salford
  • Devices:ZTE Blade III
Hi,

If anyone with technical knowlege could help . I tried to port XMasterNinni's Rom [ROM][ICS] LEZO 4.0.4 using his porting tool.

It seemed to be successful and when I rebooted the phone it got to the boota animation screen abnd just hung. I took a logcat full message can be found here

http://pastebin.com/raw.php?i=4sEjQFsB

But the error was basically

/ServiceManager( 200): Waiting for service media.player...
W/AudioSystem( 200): AudioPolicyService not published, waiting...

I did some googling and it appears to be a problem with the audioflinger and I need to edit the frameworks/base/services/audioflinger/Android.mk

I found the file in the lib section of system but I have absolutely no idea how to edit the .so file type it is in. Would anyone be able to point me in the right direction in terms of editing it

  • 0

#2
Dazzozo

Dazzozo

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 3,304 posts
  • Gender:Male
  • Location:Shropshire, UK
  • Devices:Crescent, G300, Y300, Nexus 5
  • Twitter:@Dazzozo
You would probably be better off substituting in those libs from a CM9 Crescent build.

  • 0
Like my work? Give me rep!

Like my work a lot? Donate! Remember to leave your forum name if you want to be credited!

You're likely to get a quicker response from me on Twitter.

#3
robt77

robt77

    Diehard

  • Members
  • PipPipPipPip
  • 343 posts
  • Gender:Male
  • Location:Salford
  • Devices:ZTE Blade III

You would probably be better off substituting in those libs from a CM9 Crescent build.


Thanks I will give it a go

  • 0

#4
robt77

robt77

    Diehard

  • Members
  • PipPipPipPip
  • 343 posts
  • Gender:Male
  • Location:Salford
  • Devices:ZTE Blade III
Good news and bad news. Replacing the libs has enabled me to get the rom to boot thanks for the advice Dazzoz. bad news it is all in chinese :(

back to the drawing board

I lie stumbled across the english language some how wifi seems to work as does 3 g, only annoying thing it is not touch screen and has the annoying pointer thing instead.

Edited by robt77, 09 October 2012 - 11:51 PM.

  • 0

#5
Dazzozo

Dazzozo

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 3,304 posts
  • Gender:Male
  • Location:Shropshire, UK
  • Devices:Crescent, G300, Y300, Nexus 5
  • Twitter:@Dazzozo

I lie stumbled across the english language some how wifi seems to work as does 3 g, only annoying thing it is not touch screen and has the annoying pointer thing instead.


The touchscreen issue is due to there being no input device configuration, so it defaults to the cursor. https://github.com/D...ee/ics/prebuilt

You need the .idc files from there to be at /system/usr/idc/. They're both the same, and contain only 'touch.deviceType = touchScreen', but it's the file name that's important.

  • 0
Like my work? Give me rep!

Like my work a lot? Donate! Remember to leave your forum name if you want to be credited!

You're likely to get a quicker response from me on Twitter.

#6
robt77

robt77

    Diehard

  • Members
  • PipPipPipPip
  • 343 posts
  • Gender:Male
  • Location:Salford
  • Devices:ZTE Blade III

The touchscreen issue is due to there being no input device configuration, so it defaults to the cursor. https://github.com/D...ee/ics/prebuilt

You need the .idc files from there to be at /system/usr/idc/. They're both the same, and contain only 'touch.deviceType = touchScreen', but it's the file name that's important.


Will look at that tomorrow. appreciate all the help. First rom that I have ported that seems to have more things working than not :)

actually can't be bothered sleeping, there are to idc files there called qwerty.idc and qwerty2.idc opened them up in geddit and they both say

Emulator keyboard configuration file #2.
#

touch.deviceType = touchScreen
touch.orientationAware = 1

keyboard.layout = qwerty
keyboard.characterMap = qwerty2
keyboard.orientationAware = 1
keyboard.builtIn = 1

cursor.mode = navigation
cursor.orientationAware = 1

Edit 2 I have looked at your cm9 usr idc files and see there are the two files I mentioned and another 3 with the touch screen, I will see if i copy that it will work. Thanks again

Edited by robt77, 10 October 2012 - 12:19 AM.

  • 0

#7
robt77

robt77

    Diehard

  • Members
  • PipPipPipPip
  • 343 posts
  • Gender:Male
  • Location:Salford
  • Devices:ZTE Blade III
Thanks for your help Dazzozo, managed to successfully port that rom and all seems to be working :)

After that success I tried to port the jb paranoid android rom, The rom installed great but it is stuck on the boot animation screen according to the logcat the main error is

I/ServiceManager( 108): service 'media.audio_flinger' died
I/ServiceManager( 108): service 'media.player' died
I/ServiceManager( 108): service 'media.camera' died
I/ServiceManager( 108): service 'media.audio_policy' died

full logcat at http://pastebin.com/raw.php?i=2GqfPqip

I have done some searches on google but not come up with anything definitive. Can I be cheeky and ask your opinion on what is causing that error?

Thanks

Edited by robt77, 10 October 2012 - 10:51 PM.

  • 0

#8
Dazzozo

Dazzozo

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 3,304 posts
  • Gender:Male
  • Location:Shropshire, UK
  • Devices:Crescent, G300, Y300, Nexus 5
  • Twitter:@Dazzozo
libwebcore by the looks of it. Are you porting with the CM10 base?

  • 0
Like my work? Give me rep!

Like my work a lot? Donate! Remember to leave your forum name if you want to be credited!

You're likely to get a quicker response from me on Twitter.

#9
robt77

robt77

    Diehard

  • Members
  • PipPipPipPip
  • 343 posts
  • Gender:Male
  • Location:Salford
  • Devices:ZTE Blade III
Yes but I didn't use the porting tool. I unzipped your ROM and replaced the framework, app and media folders with those from the PA ROM.

Do you know of any guide or site that is noob friendly which can decipher log cats so I can learn myself?

Thanks for your help

Edited by robt77, 11 October 2012 - 05:56 PM.

  • 0

#10
Dazzozo

Dazzozo

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 3,304 posts
  • Gender:Male
  • Location:Shropshire, UK
  • Devices:Crescent, G300, Y300, Nexus 5
  • Twitter:@Dazzozo

Do you know of any guide or site that is noob friendly which can decipher log cats so I can learn myself?


There's literally nothing.

If Google returns nothing, you are on your own. None of this stuff is very well documented, and if you ask me that's the challenge and the beauty of it.

  • 0
Like my work? Give me rep!

Like my work a lot? Donate! Remember to leave your forum name if you want to be credited!

You're likely to get a quicker response from me on Twitter.

#11
robt77

robt77

    Diehard

  • Members
  • PipPipPipPip
  • 343 posts
  • Gender:Male
  • Location:Salford
  • Devices:ZTE Blade III

There's literally nothing.

If Google returns nothing, you are on your own. None of this stuff is very well documented, and if you ask me that's the challenge and the beauty of it.


No worries, I thought I maybe missing something obvious that is out there. Will crack on and do more research. This seems as if it can get quite addictive

  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users