Jump to content


Photo

Blade 3 Development

- - - - -

  • Please log in to reply
85 replies to this topic

#81
KonstaT

KonstaT

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,598 posts
  • Gender:Male
  • Location:Finland
  • Devices:Moto G, ZTE Open C
  • Twitter:@konstatuomio
You revert either (or both) of the changes that added it. But like said, it doesn't prevent your device from booting even if you had it. At worst, it only causes spam in your logcat.
 
If you still have the same error, you haven't updated framemeworks/native properly. Previous error was caused by what I already linked and nothing else. FYI if you're using framemeworks/native from legaCyMod with the latest changes, you also need to have this patch in your build or add "ARCH_ARM_HAVE_TLS_REGISTER := true" to your BoardConfig.mk.

  • 1

#82
robt77

robt77

    Diehard

  • Members
  • PipPipPipPip
  • 343 posts
  • Gender:Male
  • Location:Salford
  • Devices:ZTE Blade III
I seemed to manage to apply the FM patches successfully and build PAC-man4.22, the FM App is there but it just force closes.  Below is the logcat from when I tried to turn on the FM App
 
D/FMService( 5592): ACTION_HEADSET_PLUG Intent received
D/FMService( 5592): mReceiver: ACTION_HEADSET_PLUG
D/FMService( 5592): ==> intent: Intent { act=android.intent.action.HEADSET_PLUG flg=0x40000010 (has extras) }
D/FMService( 5592):     state: 0
D/FMService( 5592):     name: No Device
D/FMService( 5592): audioManager.setFmRadioOn = false 
D/FMService( 5592): In stopFM
I/HeadsetService(  804): Headset=false; Bluetooth=false
D/FMService( 5592): FMRadio: sending the intent
I/HeadsetService(  804): Selected configuration: speaker
D/FMService( 5592): audioManager.setFmRadioOn false done 
V/AudioService(  469): FM Intent received
D/FMService( 5592): in stop
D/AudioPolicyManager7627a( 4511): turning off Fm device in Mode 3
W/AudioPolicyManager7627a( 4511): setDeviceConnectionState() device not connected: 80000
D/FMRadio ( 5592): mServiceCallbacks.onDisabled :
D/FMRadio ( 5592): Debug:Stopped Recording
V/WiredAccessoryManager(  469): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=1, DEVPATH=/devices/virtual/switch/h2w, SEQNUM=1577, ACTION=change, SWITCH_NAME=Headset}
V/WiredAccessoryManager(  469): newName=Headset newState=1 headsetState=1 prev headsetState=0
V/WiredAccessoryManager(  469): device Headset connected
W/AudioPolicyManagerBase( 4511): checkOutputsForDevice() could not open output for device 4
W/AudioPolicyManagerBase( 4511): checkOutputsForDevice() could not open output for device 4
D/FMService( 5592): ACTION_HEADSET_PLUG Intent received
D/FMService( 5592): mReceiver: ACTION_HEADSET_PLUG
D/FMService( 5592): ==> intent: Intent { act=android.intent.action.HEADSET_PLUG flg=0x40000010 (has extras) }
D/FMService( 5592):     state: 1
D/FMService( 5592):     name: Headset
I/HeadsetService(  804): Headset=true; Bluetooth=false
I/HeadsetService(  804): Selected configuration: headset
D/FMService( 5592): fmOn: RadioBand   :4
D/FMService( 5592): fmOn: Emphasis    :1
D/FMService( 5592): fmOn: ChSpacing   :1
D/FMService( 5592): fmOn: RdsStd      :1
D/FMService( 5592): fmOn: LowerLimit  :87500
D/FMService( 5592): fmOn: UpperLimit  :108000
V/FMRadio ( 5592): enable: CURRENT-STATE : FMOff ---> NEW-STATE : FMRxStarting
D/FmTransceiver( 5592): Fail to Open -1
E/FMRadio ( 5592): enable: Error while turning FM On
E/FMRadio ( 5592): enable: CURRENT-STATE : FMRxStarting ---> NEW-STATE : FMOff
E/fmradio ( 5592): id(8000029) value: 1
E/fmradio ( 5592): setControl native returned with err -1
D/FMService( 5592): Error in toggling analog/digital path true
D/FMService( 5592): mReceiver.enable done, Status :false
D/FMService( 5592): in stop
 
Bit late now and will have a proper google research tomorrow but can anyone tell what I did wrong?

  • 0

#83
KonstaT

KonstaT

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,598 posts
  • Gender:Male
  • Location:Finland
  • Devices:Moto G, ZTE Open C
  • Twitter:@konstatuomio

 

I seemed to manage to apply the FM patches successfully and build PAC-man4.22, the FM App is there but it just force closes.  Below is the logcat from when I tried to turn on the FM App

What system/core are you using? Do you have this (patch)?


  • 2

#84
robt77

robt77

    Diehard

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

What system/core are you using? Do you have this (patch)?

 

I was using PAC's system core & not using the patch, have just amended manifest to use legacymod  system core instead, hopefully that should work. thanks for your help as always.

 

Worked like a charm  :D


Edited by robt77, 29 October 2013 - 11:25 PM.

  • 0

#85
robt77

robt77

    Diehard

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

Hi, sorry to bump an old thread, been trying to build pac-man 4.4 and have been getting the following error make: *** [/home/rob/android/pacman4.4/out/target/product/atlas40/obj/SHARED_LIBRARIES/audio.primary.msm7x27a_intermediates/AudioHardware.o] Error 1

the full gog can be found here   http://pastebin.com/wXzGQK4d   Have repo synced and made clobber, am using the relevant LM replacements for frameworks/av & native the qcom display&media legacy, system/core etc but keep running into this issue.  Can anyone shed light as to what I am doing wrong? thanks

  • 0

#86
KonstaT

KonstaT

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,598 posts
  • Gender:Male
  • Location:Finland
  • Devices:Moto G, ZTE Open C
  • Twitter:@konstatuomio

This or add 'COMMON_GLOBAL_CFLAGS += -DQCOM_DIRECTTRACK' to your BoardConfig.mk.


  • 2




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users