Check this out:
http://www.siriusxm.com/android/indexd.html
It's about time. Been waiting for some word from them about an app.
Data connection doesn't seem to work with the app on latest Cyan.
Getting this error:
Code:
E/sirius ( 4136): ChunkSelector:setChannelId: Unknown format
E/sirius ( 4136): java.io.IOException: Unknown format
E/sirius ( 4136): at java.util.zip.GZIPInputStream.<init>(GZIPInputStream.java:85)
E/sirius ( 4136): at java.util.zip.GZIPInputStream.<init>(GZIPInputStream.java:66)
E/sirius ( 4136): at com.sirius.service.k.e(k.java)
E/sirius ( 4136): at com.sirius.service.SiriusPlayerService.startPlayback(SiriusPlayerService.java)
E/sirius ( 4136): at com.sirius.service.bb.run(bb.java)
E/sirius ( 4136): at java.util.Timer$TimerImpl.run(Timer.java:290)
E/SiriusPlayerService( 4136): SiriusPlayerService : startPlayback -> Exception in _chunkSelector.reset() or _chunkQueue.reset()
E/SiriusPlayerService( 4136): com.sirius.service.e: java.io.IOException: Unknown format
E/SiriusPlayerService( 4136): at com.sirius.service.k.e(k.java)
E/SiriusPlayerService( 4136): at com.sirius.service.SiriusPlayerService.startPlayback(SiriusPlayerService.java)
E/SiriusPlayerService( 4136): at com.sirius.service.bb.run(bb.java)
E/SiriusPlayerService( 4136): at java.util.Timer$TimerImpl.run(Timer.java:290)
E/SiriusPlayerService( 4136): Caused by: java.io.IOException: Unknown format
E/SiriusPlayerService( 4136): at java.util.zip.GZIPInputStream.<init>(GZIPInputStream.java:85)
E/SiriusPlayerService( 4136): at java.util.zip.GZIPInputStream.<init>(GZIPInputStream.java:66)
E/SiriusPlayerService( 4136): ... 4 more
However it will play over wi-fi...
does anyone understand this? lol im trying to fix bluetooth on senselx rom..
D/MCPMonitorService( 272): starting daemon!
D/MCPMonitorService( 272): state of daemon after start: running started: true
D/skia ( 272): purging 167K from font cache [18 entries]
D/dalvikvm( 272): GC freed 17074 objects / 878752 bytes in 270ms
D/JBtlBmg ( 272): destroy: Entered
D/ ( 272): NativeJBtlBmg_Destroy: Entered
D/ ( 272): NativeJBtlBmg_Destroy: Calling BTL_BMG_Destroy
D/ ( 272): NativeJBtlBmg_Destroy: BTL_BMG_Destroy returned 1
D/ ( 272): NativeJBtlBmg_Destroy:Exiting Successfully
D/JBtlBmg ( 272): After NativeJBtlBmg_Destroy, status=FAILED
D/JBtlBmg ( 272): destroy: Exiting
D/JBtlBmg ( 272): create: Entered
D/JBtlBmg ( 272): Calling NativeJBtlBmg_Create
D/ ( 272): NativeJBtlBmg_Create: Entered
D/ ( 272): NativeJBtlBmg_Create: Calling BTL_BMG_Remote_Create
D/ ( 272): NativeJBtlBmg_Create: BTL_BMG_Remote_Create returned 0, context: 1
D/ ( 272): NativeJBtlBmg_Create: Calling BTL_BMG_SetEventForwardingMode
D/ ( 272): NativeJBtlBmg_Create: BTL_BMG_SetEventForwardingMode returned 0
D/JBtlProfileContext( 272): setValue: setValue called, value:1
D/ ( 272): NativeJBtlBmg_Create:Exiting Successfully
D/JBtlBmg ( 272): After NativeJBtlBmg_Create, status=SUCCESS, Context = 1
D/JBtlBmg ( 272): create: Exiting
D/JBtlCommon( 272): radioOn: Entered
D/JBtlCommonNative( 272): NativeJBtlCommon_RadioOn: Calling BTL_RadioOn
D/JBtlCommonNative( 272): NativeJBtlCommon_RadioOn: BTL_RadioOn Returned 2
D/JBtlCommon( 272): radioOn: After NativeJBtlCommon_RadioOn, status=PENDING
D/BluetoothService( 272): Bluetooth state 10 -> 11
D/BluetoothService( 272): Sending ACTION_STATE_CHANGED intent, new mBluetoothState = 11
D/BluetoothAvrcpService( 272): Received intent with action: android.bluetooth.adapter.action.STATE_CHANGED
D/BluetoothPbapService( 272): Received intent with action: android.bluetooth.adapter.action.STATE_CHANGED
D/BluetoothA2dpService( 272): Received intent with action: android.bluetooth.adapter.action.STATE_CHANGED
D/JBtlCommonNative( 272): signal_BTL_EVENT_HCI_INIT_ERROR: status = 0
D/JBtlCommon( 272): In hciInitError
D/BluetoothService( 272): Callback - hciInitError, status = SUCCESS
D/JBtlCommonNative( 272): After the call to HCI Init Error
V/BluetoothEventRedirector( 4859): Received android.bluetooth.adapter.action.STATE_CHANGED
D/BT HS/HF( 436): gsmAsuToSignal=28
D/dalvikvm( 436): GC freed 1729 objects / 82656 bytes in 128ms
D/JBtlCommonNative( 272): signal_BTL_EVENT_HCI_INIT_ERROR: status = 0
D/JBtlCommon( 272): In hciInitError
D/BluetoothService( 272): Callback - hciInitError, status = SUCCESS
D/JBtlCommonNative( 272): After the call to HCI Init Error
D/BT HS/HF( 436): gsmAsuToSignal=27
D/BT HS/HF( 436): gsmAsuToSignal=28
D/dalvikvm( 440): GC freed 219 objects / 7576 bytes in 127ms
D/BT HS/HF( 436): gsmAsuToSignal=29
E/BluetoothService( 272): got timeout (or bad status) switching bluetooth state! indicating non-responsiveness to MCPMonitor
D/MCPMonitorService( 272): indicateNotResponding: refcount: 1
D/MCPMonitorService( 272): will stop deamon and reset refcount
D/MCPMonitorService( 272): stopping daemon. force: true
D/MCPMonitorService( 272): calling all onStop callbacks
D/BluetoothService( 272): onDeamonStop: forceStop: true
D/BluetoothService( 272): onDeamonStop: forceStop - simulating radio off
D/BluetoothService( 272): Callback - radioOffComplete, status = SUCCESS
D/MCPMonitorService( 272): state of daemon after stop: stopped stopped: true
D/MCPMonitorService( 272): shuting down chip...
D/BluetoothService( 272): Bluetooth state 11 -> 10
D/BluetoothService( 272): Sending ACTION_STATE_CHANGED intent, new mBluetoothState = 10
D/BluetoothAvrcpService( 272): Received intent with action: android.bluetooth.adapter.action.STATE_CHANGED
D/BluetoothPbapService( 272): Received intent with action: android.bluetooth.adapter.action.STATE_CHANGED
D/BluetoothA2dpService( 272): Received intent with action: android.bluetooth.adapter.action.STATE_CHANGED
V/BluetoothEventRedirector( 4859): Received android.bluetooth.adapter.action.STATE_CHANGED
D/BT HS/HF( 436): gsmAsuToSignal=30
D/BT HS/HF( 436): gsmAsuToSignal=29
D/dalvikvm( 433): GC freed 69 objects / 3152 bytes in 102ms
D/skia ( 779): purging 93K from font cache [12 entries]
D/dalvikvm( 779): GC freed 2455 objects / 120680 bytes in 151ms
The GPS is not starting up, tried everything. Flashing new GPS configuration, Cleaning GPS data with angry GPS, Booting, reebooting.
i9000 running CM7 7.1.0 Stable
It started after following this Post
http://forum.xda-developers.com/showthread.php?t=1182735
-GPS Antenna is on
-The gps notification used to blink while trying to fix a position, now it doesn't even show up.
Please Help
Part of a alogcat file where the same error keeps repeating itself while the antenna is on.
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
Can anyone give me a hint please?
biomanuel666 said:
The GPS is not starting up, tried everything. Flashing new GPS configuration, Cleaning GPS data with angry GPS, Booting, reebooting.
i9000 running CM7 7.1.0 Stable
It started after following this Post
http://forum.xda-developers.com/showthread.php?t=1182735
-GPS Antenna is on
-The gps notification used to blink while trying to fix a position, now it doesn't even show up.
Please Help
Part of a alogcat file where the same error keeps repeating itself while the antenna is on.
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
Click to expand...
Click to collapse
Please help me out with this!
GPS no longer working
You have a GT-I9000, yet you have sought the answer to your problem on a Vibrant thread. Did you, by any chance, install CM7 for the Vibrant onto your GT-I9000, find a problem with the GPS, and look for the answer within the Vibrant thread?
If you could supply a little more background information, then this would be helpful.
hi guys pls anyone can help me about my problem which i update my phone to ics and the Bluetooth doesn't working
and i dont have recovery or root cuz my phone locked and S-ON
and i cant downgrade to GB
pls help
thank u .
if your phone have s-off you can install ruu for your country with gb.
Just find your CID and go to android development section for gb ruu
stona175 said:
if your phone have s-off you can install ruu for your country with gb.
Just find your CID and go to android development section for gb ruu
Click to expand...
Click to collapse
iam sorry my freind for my misatke it's not S-OFF it's S-ON and locked
:crying:
white_knight1 said:
iam sorry my freind for my misatke it's not S-OFF it's S-ON and locked
:crying:
Click to expand...
Click to collapse
Have you done a hard reset? Coz frankly you are the first i know of with such issue.....
chaki- said:
Have you done a hard reset? Coz frankly you are the first i know of with such issue.....
Click to expand...
Click to collapse
yes i made a factory rest and everything erased and the same problem still
Its wird problem but if you still want back to GB go to my tutorial or in android developmend section. There is oryginal threat about s- off and backing to GB.
Link on sygnature.
Sent from my HTC One V using xda premium
white_knight1 said:
yes i made a factory rest and everything erased and the same problem still
Click to expand...
Click to collapse
Have you tried with different BT devices? I mean phones, PC's etc ?
chaki- said:
Have you tried with different BT devices? I mean phones, PC's etc ?
Click to expand...
Click to collapse
yes my friend i tried the problem is that the Bluetooth not working well coz when i want to send anything stock in the middle of sending and then i when i want to try again nothing happens
white_knight1 said:
yes my friend i tried the problem is that the Bluetooth not working well coz when i want to send anything stock in the middle of sending and then i when i want to try again nothing happens
Click to expand...
Click to collapse
Sometimes makes that trouble. After the XE updates to ICS almost everyone had those problem with wi-fi and bluetooth. I guess something went wrong with the update. If you don't care about the warranty you can root and install another rom. But if the problem is still there you can't repair it under warranty. So my advise is you go to the service and let it checked out. Just to be sure coz not everything is software related.
And if everythings fine listen to stona175 and check out how to perform root and etc.
Good luck man
I would try to revert to stock GB rom and see whether BT is working on it. If so, try a fresh update to ICS and recheck BT.
If reverting back to stock GB does not do the job, I would return the phone on warranty and request a replacement.
Coz if it is a hardware issue (I hope it isn't) then you have no other choice. Sometimes dropping your phone can damage the BT antenna (it happened to my girlfriend's DHD).
In other words, do not void your warranty before you make sure your issue is not hardware related.
Good luck
i have the exact same problem
im quite sure it was working in gb, i updated to ics and now it wont turn on atall, the logcat reads
/BTE-MAIN( 4969): **** Starting BtSnoop ****
E/BTL_CFG ( 4969): WARNING : [service.brcm.bt.TRC_BTSNOOP] property_get failed (0)
I/BTE-MAIN( 4969): Build time: Mar 23 2012 14:08:01
I/BTE-MAIN( 4969): get specific BD address...
I/BTE-MAIN( 4969): Got BD address 18:87:96:ce:00:cf
I/BTE-MAIN( 4969): from /sys/module/htc_bdaddress/parameters/bdaddress
I/BTL_CFG ( 4969): SetProperties: save default BDA: 188796ce00cf
I/BTL_CFG ( 4969): btl_cfg_get_bdaddr: BDA=188796ce00cf
E/BTL_CFG ( 4969): WARNING : [service.brcm.bt.patchfile] property_get failed (0)
I/BTL_CFG ( 4969): btl_cfg_get_3way_conf_support: service.brcm.bt.3way_support=true
E/BTL_CFG ( 4969): WARNING : [service.brcm.bt.bt_wake_polar] property_get failed (0)
I/BTL_CFG ( 4969): btl_cfg_get_lpm_params: service.brcm.bt.bt_wake_polar=0
E/BTL_CFG ( 4969): WARNING : [service.brcm.bt.host_wake_polar] property_get failed (0)
I/BTL_CFG ( 4969): btl_cfg_get_lpm_params: service.brcm.bt.host_wake_polar=0
I/BTL_CFG ( 4969): btl_cfg_get_pcm_i2c_params: service.brcm.bt.sco_i2s=false
I/BTL_CFG ( 4969): btl_cfg_get_ag_hsp_only: service.brcm.bt.ag_hsp_only=false
E/BTL_CFG ( 4969): WARNING : [service.brcm.bt.pcm_clk] property_get failed (0)
E/BTL_CFG ( 4969): WARNING : [service.brcm.bt.pcm_sync] property_get failed (0)
E/BTL_CFG ( 4969): WARNING : [service.brcm.bt.pcm_ms_role] property_get failed (0)
E/BTL_CFG ( 4969): WARNING : [service.brcm.bt.pcm_lsb_first] property_get failed (0)
E/BTL_CFG ( 4969): WARNING : [service.brcm.bt.pcm_fill_bits] property_get failed (0)
E/BTL_CFG ( 4969): WARNING : [service.brcm.bt.pcm_fill_method] property_get failed (0)
E/BTL_CFG ( 4969): WARNING : [service.brcm.bt.pcm_fill_num] property_get failed (0)
E/BTL_CFG ( 4969): WARNING : [service.brcm.bt.pcm_right_jstfy] property_get failed (0)
I/BTL_CFG ( 4969): btl_cfg_get_contacts_db: service.brcm.bt.contacts_db=/data/data/com.android.providers.contacts/databases/
I/bluedroid( 4136): BTLD start retry count 17/20
W/ ( 4969): btm_dev_timeout( timeout_reason: x1 )::devcb.state: 0
I/bluedroid( 4136): dtun_property_is_active : service.brcm.bt.srv_active=0
I/bluedroid( 4136): BTLD start retry count 18/20
I/bluedroid( 4136): dtun_property_is_active : service.brcm.bt.srv_active=0
I/bluedroid( 4136): BTLD start retry count 19/20
E/bluedroid( 4136): btld start timed out
I/bluedroid( 4136): PROFILE:bt_enable: Turnaround time: 9.517273 seconds
E/BluetoothEventLoop.cpp( 4136): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
this isnt all of it but maybe give soebody an idea as to whats going on??
any help would greatly be appreciated
thanks
Trying to compile a rootbox vanilla build for qinara (4.2.2 / host:s2)
When I logcat e (error), I get this...
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\John>cd android/sdk/platform-tools
C:\Users\John\Android\sdk\platform-tools>adb logcat d
- waiting for device -
^C
C:\Users\John\Android\sdk\platform-tools>adb logcat e
- waiting for device -
^C
C:\Users\John\Android\sdk\platform-tools>adb logcat e
- waiting for device -
--------- beginning of /dev/log/main
I/init.qcom.modem_links.sh( 157): modem_fw.mdt: No such file or directory
I/init.qcom.modem_links.sh( 157): /system/etc/init.qcom.modem_links.sh[83]: bre
ak: can't break
I/init.qcom.modem_links.sh( 157): /system/etc/init.qcom.modem_links.sh[170]: br
eak: can't break
D/ ( 261): MOTO_PUPD: mot_boot_mode
D/ ( 261): MOTO_PUPD: mot_boot_mode : normal
E/mm-camera( 259):
E/mm-camera( 259): Camera Daemon starting
D/QSEECOMD: ( 263): qseecom listener services process entry PPID = 1
D/QSEECOMD: ( 263): Parent qseecom daemon process terminated!!
D/QSEECOMD: ( 289): qseecom listener service threads starting!!!
D/QSEECOMD: ( 289): Total listener services to start = 2
D/QSEECOMD: ( 289): Init dlopen(libdrmfs.so, RTLD_NOW) succeeds
D/QSEECOMD: ( 289): Init::Init dlsym(g_FSHandle fs_start) succeeds
D/QSEECOMAPI: ( 289): QSEECom_register_listener 10 sb_length = 0x5000
D/DrmLibFs( 289): registering fs service to QSEECom is done!
D/DrmLibFs( 289): begin to create a thread!
D/DrmLibFs( 289): Creating a pthread in fs_start is done! return 0
D/QSEECOMD: ( 289): Init fs_start ret = 0
D/QSEECOMD: ( 289): file system services: Started
D/DrmLibFs( 289): Dispatch starts!
D/DrmLibFs( 289): before calling ioctl to read the next cmd
D/QDUMPD ( 286): Start polling.
D/BHD ( 285): Battery Health Daemon start!
I/ATVC ( 283): atvc_pal_production_part: start
I/ATVC ( 283): dbval_production_part: determined production part
I/ATVC ( 283): atvc_pal_init_factory_state: start
I/ATVC ( 283): atvc_pal_init_factory_state: determined out of factory state
I/ATVC ( 283): atval_pal_read_datablock: enter
I/ATVC ( 283): atval_pal_read_datablock: getting size of datablock
D/QDUMPD ( 286): dump polling (/dev/ramdump_smem)
D/QDUMPD ( 286): dump polling (/dev/coredump_riva)
D/QDUMPD ( 286): dump polling (/dev/ramdump_modem_sw)
I/DEBUG ( 273): debuggerd: Apr 21 2013 00:38:24
D/QDUMPD ( 286): dump polling (/dev/ramdump_riva)
D/QDUMPD ( 286): dump polling (/dev/ramdump_modem_fw)
I/installd( 279): installd firing up
D/QDUMPD ( 286): dump polling (/dev/coredump_modem)
I/graphicsd( 287): graphicsd - version: 1.0
I/graphicsd( 287): graphicsd - watching [/sys/class/kgsl/kgsl-3d0/snapshot/time
stamp][fd: 3]
D/BHD ( 285): EEPROM - Battery ID = 898bc7a41c0050b7
I/ATVC ( 283): atval_pal_read_datablock: exit
I/ATVC ( 283): atval_enforce_android_policy: validation failed. all disable
d.
I/ATVC ( 283): read handset resource access flags:
I/ATVC ( 283): 0x00000000
I/ATVC ( 283): atval_setup_properties: valid datablock - setting flags
D/BHD ( 285): NVM Read - Opened NVM file /pds/batt_health/batt-898bc7a41c00
50b7_0
E/mm-camera( 259): GETTING MCTL INFO
I/ATVC ( 283): atval_enforce_android_policy: finalize the properties
I/DMM ( 346): DMM available. movable_start_bytes at
--------- beginning of /dev/log/system
I/Vold ( 266): Vold 2.1 (the revenge) firing up
V/XTWiFi ( 354): [MessageQ] creating server socket
I/location-mq( 335): [XTWiFi-MessageQ] creating server socket
V/XTWiFi ( 354): [MessageQ] binding server socket to name [/data/misc/location
/mq/location-mq-s]
I/location-mq( 335): [XTWiFi-MessageQ] binding server socket to name [/data/mis
c/location/mq/location-mq-s]
D/Vold ( 266): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media
)
D/Vold ( 266): Volume usbdisk_1.1.1 state changing -1 (Initializing) -> 0 (N
o-Media)
D/Vold ( 266): Volume usbdisk_1.0 state changing -1 (Initializing) -> 0 (No-
Media)
D/Vold ( 266): Volume usbdisk_1.1 state changing -1 (Initializing) -> 0 (No-
Media)
D/Vold ( 266): Volume usbdisk_1.2 state changing -1 (Initializing) -> 0 (No-
Media)
D/Vold ( 266): Volume usbdisk_1.3 state changing -1 (Initializing) -> 0 (No-
Media)
D/Vold ( 266): Volume usbdisk_1.4 state changing -1 (Initializing) -> 0 (No-
Media)
D/Vold ( 266): Volume usbdisk_1.5 state changing -1 (Initializing) -> 0 (No-
Media)
D/Vold ( 266): Volume usbdisk_1.6 state changing -1 (Initializing) -> 0 (No-
Media)
D/Vold ( 266): Volume usbdisk_1.7 state changing -1 (Initializing) -> 0 (No-
Media)
I/cm ( 367): ____ _ _ ____ _ _ ____ ____ ____ _ _ _ _ ____ ___
I/Netd ( 272): Netd 1.0 starting
W/InterfaceController( 272): Warning (Cannot load library: load_library(linker.
cpp:771): library "/system/lib/libnetcmdiface.so" not found) while opening the n
et interface command library
I/rmt_storage( 338): Target is APQ8064: 1074105669
D/BHD ( 285): NVM Read - Read header, version = 1, file write count = 190,
time = Sun Apr 21 03:18:08 2013
D/BHD ( 285): NVM Read - Opened NVM file /pds/batt_health/batt-898bc7a41c00
50b7_1
D/BHD ( 285): NVM Read - Read header, version = 1, file write count = 189,
time = Sat Apr 20 06:34:09 2013
D/BHD ( 285): NVM Load - Found newest file, index to use = 0
D/BHD ( 285): State - EEPROM id = 898bc7a41c0050b7; capacity = 1750
D/BHD ( 285): State - BMS real fcc batt temp = 282, real fcc = 1700
D/BHD ( 285): State - BMS SOC = 100%, OCV = 3682000, rbatt = 241
D/BHD ( 285): State - BMS charge inc = 66, charge cycles = 121
D/BHD ( 285): State - is factory mode = 0
D/BHD ( 285): State - is charging = 0
D/BHD ( 285): State - aged capacity % = 98
D/BHD ( 285): State - aged capacity calculated @ Fri Apr 5 00:04:14 2013
D/BHD ( 285): State - Begin charge % = 0, cc = 972508, ocv = 4011000
D/BHD ( 285): State - End charge % = 100, cc = -468380, ocv = 4011000
I/cm ( 369): | \_/ |__| |\ | | | | __ |___ |\ | |\/| | | | \
D/BHD ( 285): Created socket 7 for uevents
D/PPDaemon( 334): isHDMIPrimary: HDMI is not primary display
D/PPDaemon( 334): CABL version 1.0.20120512
E/ThermalDaemon( 284): Thermal daemon started
D/QC-time-services( 339): Daemon:genoff_pre_init::Base = 0
D/QC-time-services( 339): Daemon:ats_rtc_init: Time read from RTC -- year = 113
, month = 3,day = 3
D/Vold ( 266): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 266): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 97
, PARTN 1
E/QC-time-services( 339): Daemon:genoff_boot_tod_init: Unable to set TOD at boo
t up
E/QC-time-services( 339): Daemon: Unable to set TOD at boot up
D/QC-time-services( 339): Daemon:genoff_modem_qmi_init: Initiallizing QMI
I/cm ( 385): Welcome to Android 4.2.2 / CyanogenMod-
I/Atfwd_Daemon( 333): ATFWD --> QMI Port : rmnet1
I/start ( 400): A wise man never plays leapfrog with a unicorn
W/libc ( 336): WARNING: generic atexit() called from legacy shared library
I/Sensors ( 376): sns_init_la.c(292):initializing sns_memmgr_init
I/Sensors ( 376): sns_init_la.c(303):Waiting for sns_memmgr_init...
I/Sensors ( 376): sns_init_la.c(307):Done waiting for sns_memmgr_init
I/Sensors ( 376): sns_init_la.c(292):initializing sns_debug_test_init1
I/Sensors ( 376): sns_init_la.c(303):Waiting for sns_debug_test_init1...
I/Sensors ( 376): sns_init_la.c(307):Done waiting for sns_debug_test_init1
I/Sensors ( 376): sns_init_la.c(292):initializing sns_pwr_init
I/sensorsqcomwrapper.sh( 374): Use option "-d" to run as background process.
I/sensorsqcomwrapper.sh( 374): Running in foreground...
I/run-parts( 342): sysctl: /etc/sysctl.conf: No such file or directory
I/SurfaceFlinger( 275): SurfaceFlinger is starting
I/SurfaceFlinger( 275): SurfaceFlinger's main thread ready to run. Initializing
graphics H/W...
I/Sensors ( 376): sns_init_la.c(303):Waiting for sns_pwr_init...
I/Sensors ( 376): sns_init_la.c(307):Done waiting for sns_pwr_init
I/Sensors ( 376): sns_init_la.c(292):initializing sns_em_init
I/Sensors ( 376): sns_init_la.c(303):Waiting for sns_em_init...
D/libEGL ( 275): loaded /system/lib/egl/libEGL_adreno200.so
I/Sensors ( 376): sns_init_la.c(307):Done waiting for sns_em_init
I/Sensors ( 376): sns_init_la.c(292):initializing sns_smr_init
I/Sensors ( 376): sns_init_la.c(303):Waiting for sns_smr_init...
W/Sensors ( 376): sns_smr_la.c(415):smr_la: smr_apps_la_thread_main is starting
, fd=15, sns_smr.en_rx_msg_ptr=400c87e8
I/Sensors ( 376): sns_init_la.c(307):Done waiting for sns_smr_init
I/Sensors ( 376): sns_init_la.c(292):initializing sns_reg_init
I/Sensors ( 376): sns_init_la.c(303):Waiting for sns_reg_init...
D/BHD ( 285): Got a battery uevent,log details
D/BHD ( 285): Battery start charging @ 88%!
D/libEGL ( 275): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 275): loaded /system/lib/egl/libGLESv2_adreno200.so
I/Sensors ( 376): sns_init_la.c(307):Done waiting for sns_reg_init
I/Sensors ( 376): sns_init_la.c(292):initializing sns_sam_init
I/Sensors ( 376): sns_init_la.c(303):Waiting for sns_sam_init...
I/Adreno200-EGL( 275): <eglInitialize:269>: EGL 1.4 QUALCOMM build: Nondetermin
istic AU_full_mako_PARTNER-ANDROID/JB-MR1-DEV_CL2946718_release_AU (CL2946718)
I/Adreno200-EGL( 275): Build Date: 11/04/12 Sun
I/Adreno200-EGL( 275): Local Branch:
I/Adreno200-EGL( 275): Remote Branch: m/partner-android/jb-mr1-dev
I/Adreno200-EGL( 275): Local Patches: NONE
I/Adreno200-EGL( 275): Reconstruct Branch: NOTHING
I/gralloc ( 275): using (fd=21)
I/gralloc ( 275): id = msmfb42_90701
I/gralloc ( 275): xres = 720 px
I/gralloc ( 275): yres = 1280 px
I/gralloc ( 275): xres_virtual = 720 px
I/gralloc ( 275): yres_virtual = 3840 px
I/gralloc ( 275): bpp = 32
I/gralloc ( 275): r = 24:8
I/gralloc ( 275): g = 16:8
I/gralloc ( 275): b = 8:8
I/gralloc ( 275): width = 56 mm (326.571442 dpi)
I/gralloc ( 275): height = 99 mm (328.404053 dpi)
I/gralloc ( 275): refresh rate = 60.00 Hz
D/CALCFPS ( 275): DEBUG_CALC_FPS: 0
D/CALCFPS ( 275): period: 10
D/CALCFPS ( 275): ignorethresh_us: 500000
D/CALCFPS ( 275): DEBUG_CALC_FPS: 0
D/CALCFPS ( 275): period: 10
D/CALCFPS ( 275): ignorethresh_us: 500000
D/overlay ( 275): initoverlay:: opening the device:: /dev/graphics/fb0
D/overlay ( 275): initoverlay:: opening the device:: /dev/graphics/fb1
D/overlay ( 275): ndx=6 num=5 z_order=-1
D/AndroidRuntime( 276):
D/AndroidRuntime( 276): >>>>>> AndroidRuntime START com.android.internal.os.Zyg
oteInit <<<<<<
D/AndroidRuntime( 276): CheckJNI is OFF
D/overlay ( 275): initoverlay:: opening the device:: /dev/graphics/fb2
I/mediaserver( 278): ServiceManager: 0x414a7ed8
I/AudioFlinger( 278): Using default 3000 mSec as standby time.
I/CameraService( 278): CameraService started (pid=278)
^C
C:\Users\John\Android\sdk\platform-tools>adb logcat e
--------- beginning of /dev/log/system
I/Vold ( 266): Vold 2.1 (the revenge) firing up
D/Vold ( 266): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media
)
D/Vold ( 266): Volume usbdisk_1.1.1 state changing -1 (Initializing) -> 0 (N
o-Media)
D/Vold ( 266): Volume usbdisk_1.0 state changing -1 (Initializing) -> 0 (No-
Media)
D/Vold ( 266): Volume usbdisk_1.1 state changing -1 (Initializing) -> 0 (No-
Media)
D/Vold ( 266): Volume usbdisk_1.2 state changing -1 (Initializing) -> 0 (No-
Media)
D/Vold ( 266): Volume usbdisk_1.3 state changing -1 (Initializing) -> 0 (No-
Media)
D/Vold ( 266): Volume usbdisk_1.4 state changing -1 (Initializing) -> 0 (No-
Media)
D/Vold ( 266): Volume usbdisk_1.5 state changing -1 (Initializing) -> 0 (No-
Media)
D/Vold ( 266): Volume usbdisk_1.6 state changing -1 (Initializing) -> 0 (No-
Media)
D/Vold ( 266): Volume usbdisk_1.7 state changing -1 (Initializing) -> 0 (No-
Media)
D/Vold ( 266): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 266): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 97
, PARTN 1
Can anyone help me?
Really, no one?
Sent from my MB886 using xda app-developers app
Codex01 said:
Really, no one?
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Some people (like me) don't even know what to do with that so just be patient friend.
Sent from my MB886 using xda app-developers app
worlddominatiin said:
Some people (like me) don't even know what to do with that so just be patient friend.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I pretty much know whats going on, I may have the wrong lib_runtime and android policy, also may be a faulty kernel. From the log you can tell it finalises boot, it has all the scripts but there are a few errors, that I know cant be errors.
system/lib/libnetcmdiface.so - look like that lib isn't there
camera drivers might be wrong - use the CM10.1 drivers
and looks like some of the /etc scripts aren't working properly and some .conf files aren't present.
I'd have to flash the rom and have a physical copy to mess with to tell you more.
skeevydude said:
system/lib/libnetcmdiface.so - look like that lib isn't there
camera drivers might be wrong - use the CM10.1 drivers
and looks like some of the /etc scripts aren't working properly and some .conf files aren't present.
I'd have to flash the rom and have a physical copy to mess with to tell you more.
Click to expand...
Click to collapse
I will upload this on the new site asap.
Any word on ur progress my friend?
Sent from my MB886 using xda premium
sickkside13 said:
Any word on ur progress my friend?
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
@sickkside13, @skeevydude and I are working on this port, hes helping me alot. He says (I deleted the email, so don't quote me.) that we will have a build from source probably by tomorrow or the day after.
Nice
Sent from my MB886 using xda premium
I still gotta tweak our device\vendor repo (if its anything like PA, which it seems to be, should only be a few lines). Hard part will be making a vendor/rootbox repo for us -- just gonna base it on a Nexus and start playing the follow the makefile game . Due to the way our CM10.1 repo is set up -- our only custom repos are for kernel, device, and device vendor -- the very minimal necessary -- roms like this & PACMAN shouldn't be that hard to make for us from source. Atrix HD and GSM Razr HD anyways...don't know much about CDMA roms.
Depending on time, I should have the necessary changes and additions done today. I gotta go with the bossman on a bid and to pick up some materials today --- not sure how long that'll take. Gotta go 20 miles one way from town for the bid, 40 miles the other way for materials (60 miles from the bid).
Waiting for this, looks good
Sent from my MB886 using xda app-developers app
Just finished everything and starting the first compile. Been going for 10 minutes now. Hopefully it'll finish. :fingers-crossed:
If it goes well, sources should be on github this evening and my tweaked vendor and device repo should just work with the PacMan sources. PacMan should just need some qinara vendor/pacman config and make files. Root and Pac both use a modified PA style build system, I've done a bit of PA in the past so, and luckily, doing these tweaks\making the necessary vendor make files is nothing new to me.
Plan is to do Unofficial Atrix HD RootBox. If this works, then I'll do the same for Razr HD. Once all that's done I'll move on to PacMan.
I'm also going to add, before all you guys start giving me the same BS you've been giving Codex, that all I'm doing is taking the razr-qcom dev team repos and making them compatible with other projects. All the actual development will either be via the dev team's CM10.1 kernel or whatever project's dev team. That's not saying that I won't add in any fixes or whatever myself, just that most of what I'm doing is combining other peoples hard work for our benefit.
//20 minutes compiling and goind strong
skeevydude said:
Plan is to do Unofficial Atrix HD RootBox. If this works, then I'll do the same for Razr HD. Once all that's done I'll move on to PacMan.
Click to expand...
Click to collapse
Thanks for the Razr HD love!
Didn't compile, had some errors with tcpdump, removing it and trying again.
Sources available on git-hub
Code:
repo init -u [url]https://github.com/skeevy420/platform_manifest.git[/url] -b razrqcom-rootbox
repo sync
. build_rootbox.sh qinara [B][COLOR="Blue"]X[/COLOR][/B] clean
[B][COLOR="Blue"]X[/COLOR][/B] is the number of threads to use, use either number of cores or number of cores +1 -- whichever you find works best.
//Why all of a sudden does XDA decide to email me when I post a code box in my own post? You'd think I'd be aware of that one
Once you get a build I'd be more than happy to beta, PM me if you need anything. I was a beta tester for eight months for two devs on the Galaxy Player 5.0 so I have a lot of experience...
Sent from my MB886 using xda app-developers app
EcHoFiiVe said:
Once you get a build I'd be more than happy to beta, PM me if you need anything. I was a beta tester for eight months for two devs on the Galaxy Player 5.0 so I have a lot of experience...
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Let ya know when I know
Was having some defconfig issues with the kernel. Resolved them and starting over. It was crappin out around 35 minutes, so once 10:00 central hits I'll be farther along in the process anyways
Day one fun
skeevydude said:
Let ya know when I know
Was having some defconfig issues with the kernel. Resolved them and starting over. It was crappin out around 35 minutes, so once 10:00 central hits I'll be farther along in the process anyways
Day one fun
Click to expand...
Click to collapse
How long do you think it'll take to build? Four, seven hours?
Sent from my MB886 using xda app-developers app
EcHoFiiVe said:
How long do you think it'll take to build? Four, seven hours?
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
From start to finish? Defy CM10.1 takes an hour an a half, so this should be between an hour an a half to two hours...providing it finishes.
i have a nexus 4 and i just flashed rootbox its kinda buggy but there is another build. Il try it out in a bit
Sent from my MB886 using xda premium
sickkside13 said:
i have a nexus 4 and i just flashed rootbox its kinda buggy but there is another build. Il try it out in a bit
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
Even if it is buggy I'd at least like to get it set up and compiling so that when its not buggy all the leg work is already done.