GPS issue - Liquid S100 General

I found my gps isn't working at all.
What happened?
Once a day I found my phone out of battery and I wasn't able to turn it on again. I performed a guarantee motherboard replacement. So I was very happy with my renewed 2.1 liquid.
In a month after the new brilliant 2.2 froyo leak was published and I reflashed my phone. Than a few days later I found my phone unable to find any sattelites at all, so I decided that it was a leaked 2.2 fault and didn't disturb myself and community about it. Now we have official 2.2 released on which I reflashed my phone too, but this unfortunately didn't solve the problem.
I tried adb logcat *:W and the output looks like this:
Code:
W/libloc ( 123): loc_inform_gps_status, status: GPS_STATUS_ENGINE_ON
W/libloc ( 123): Fix session state: RPC_LOC_FIX_SESSION_STATE_END
W/libloc ( 123): Fix session state: RPC_LOC_FIX_SESSION_STATE_BEGIN
W/libloc ( 123): loc_inform_gps_status, status: GPS_STATUS_SESSION_BEGIN
W/libloc ( 123): Fix session state: RPC_LOC_FIX_SESSION_STATE_END
W/libloc ( 123): Fix session state: RPC_LOC_FIX_SESSION_STATE_BEGIN
W/libloc ( 123): loc_inform_gps_status, status: GPS_STATUS_SESSION_BEGIN
E/Tethering( 123): active iface (usb0) reported as added, ignoring
W/libloc ( 123): Fix session state: RPC_LOC_FIX_SESSION_STATE_END
W/libloc ( 123): Fix session state: RPC_LOC_FIX_SESSION_STATE_BEGIN
W/libloc ( 123): loc_inform_gps_status, status: GPS_STATUS_SESSION_BEGIN
W/libloc ( 123): Fix session state: RPC_LOC_FIX_SESSION_STATE_END
W/libloc ( 123): Fix session state: RPC_LOC_FIX_SESSION_STATE_BEGIN
W/libloc ( 123): loc_inform_gps_status, status: GPS_STATUS_SESSION_BEGIN
W/libloc ( 123): Fix session state: RPC_LOC_FIX_SESSION_STATE_END
W/libloc ( 123): loc_inform_gps_status, status: GPS_STATUS_SESSION_END
W/libloc ( 123): Engine state: RPC_LOC_ENGINE_STATE_OFF
W/libloc ( 123): loc_inform_gps_status, status: GPS_STATUS_ENGINE_OFF
W/libloc ( 123): Fix session state: RPC_LOC_FIX_SESSION_STATE_BEGIN
W/libloc ( 123): loc_inform_gps_status, status: GPS_STATUS_SESSION_BEGIN
W/libloc ( 123): Engine state: RPC_LOC_ENGINE_STATE_ON
W/libloc ( 123): loc_inform_gps_status, status: GPS_STATUS_ENGINE_ON
and so on: session start, session end, session start, session end... Also, on boot there are another interesting messages:
Code:
E/acer_AgpsSetting( 120): Acer A-GPS Settings Interface init! Curren version(201)
W/GpsLocationProvider( 120): Doesn't have stored SUPL host and port, using PROPERTIES_FILE settings!
E/GpsLocationProvider( 120): GPS_CERT file exists: false
E/GpsLocationProvider( 120): Failed to default A-GPS settings!
E/GpsLocationProvider( 120): unable to parse SUPL_PORT:
I decided that it was complete 2.2 fault and went back to official stock 2.1 eclair but got abosolutely the same logcat output and no sattelites found.
I can't believe this is a hw problem again I am very dissapointed about it because the service quality in Russia is awful (45 days of waiting for my beauty in september).
I not sure very well but I think (don't remember because of what, actually) it WAS OK before 2.2 flashing. But I can't say it absolutely definite.
Any help would be appreciate, lost any hope

additional info:
i've set debug level in gps.conf to 5 (verbose) and got this output:
Code:
D/libloc ( 123): Event RPC_LOC_EVENT_PARSED_POSITION_REPORT (client 0)
D/libloc ( 123): Session status: RPC_LOC_SESS_STATUS_IN_PROGESS Valid mask: 0xF1E9
D/libloc ( 123): Latitude: 54.7367835 (intermediate)
D/libloc ( 123): Longitude: 55.9604287
D/libloc ( 123): Accuracy: 1772.0000000
V/libloc ( 123): loc_eng_report_position: ignore position report when session status = 1
D/libloc ( 123):
D/libloc ( 123): Event RPC_LOC_EVENT_SATELLITE_REPORT (client 0)
D/libloc ( 123): sv count: 0
D/libloc ( 123):
D/libloc ( 123): Event RPC_LOC_EVENT_PARSED_POSITION_REPORT (client 0)
D/libloc ( 123): Session status: RPC_LOC_SESS_STATUS_IN_PROGESS Valid mask: 0xF1E9
D/libloc ( 123): Latitude: 54.7367835 (intermediate)
D/libloc ( 123): Longitude: 55.9604287
D/libloc ( 123): Accuracy: 1789.0000000
V/libloc ( 123): loc_eng_report_position: ignore position report when session status = 1
D/libloc ( 123):
D/libloc ( 123): Event RPC_LOC_EVENT_SATELLITE_REPORT (client 0)
D/libloc ( 123): sv count: 0
and so on. Latitude and longitude remains absolutely the same, but Accuracy always changing (grows a little bit).
Is there any ideas? I got maximum from the logs, hope someone give me advice... Is there any chance to "wipe gps data" or something?

still requesting any help..

Hi
Have you found any solution to your problem? I have the same issue (see www .htcforums.com/desire-hd/7699-gps-interruption-problem.html). I am using Android 2.2 on HTC Desire HD.
Thanks in advance.

Related

Porting AOSP*1.6

Hi,
I don't know if it's the right section but..
I'm trying to port AOSP 1.6 on Galaxy. After a few mod on init.rc, the system boot and work. Now, i want to have phone, and perhaps other things working on.
To make phone working, i tried to use the same libsec-ril.so from 1.5, but i got :
I/RILJ ( 2548): Couldn't find 'rild' socket; retrying after timeout
I/RIL ( 8488): Opening tty device /dev/ttyS0
I/RILJ ( 2548): Couldn't find 'rild' socket; retrying after timeout
I/RILJ ( 2548): Couldn't find 'rild' socket; retrying after timeout
I/RILJ ( 2548): Couldn't find 'rild' socket; retrying after timeout
I/RILJ ( 2548): Couldn't find 'rild' socket; retrying after timeout
I/RILJ ( 2548): Couldn't find 'rild' socket; retrying after timeout
I/RILJ ( 2548): Couldn't find 'rild' socket; retrying after timeout
E/RILJ ( 2548): Couldn't find 'rild' socket after 8 times, continuing to retry silently
E/RIL ( 8488): Failed to start RX reader thread
E/RILC ( 8488): RIL_register: RIL_RadioFunctions * null or invalid version (expected 2)
Click to expand...
Click to collapse
i also try with libreference-ril :
E/RILJ ( 2548): Hit EOS reading message length
I/RILJ ( 2548): Disconnected from 'rild' socket
I/RIL ( 8330): Opening tty device /dev/ttyS0
D/RILC ( 8330): startMultiClientSocket() START
D/RILC ( 8330): startMultiClientSocket() fd=8 END
I/RILJ ( 2548): Connected to 'rild' socket
D/RILC ( 8330): removeWatch: fd=11
I/RILC ( 8330): libril: new connection=12
D/RILC ( 8330): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED {RADIO_UNAVAILABLE}
D/RILC ( 8330): sendResponseRaw(): fd=12, header=201326592
D/RILC ( 8330): sendResponseRaw(): fd=12, dataSize=12
I/RILC ( 8330): RIL Daemon version: android reference-ril 1.0
D/RILJ ( 2548): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED RADIO_UNAVAILABLE
D/RILC ( 8330): processTimeouts: fd=-1
Click to expand...
Click to collapse
Anyone know what happens ? I don"t know if it the right way, or if i simply run into a wall...

Ok I really need help with this....

So my market keeps dying. Simply what it does is when I go to downloads, it dies and goes back to main page. Sometimes I can get to an app to update it, but never click the ok button on the popup to confirm the update. It simply closes, and goes back to market home. This only happens on 2.1 ROMs. Never on a 1.6.
I hate tried EVERYTHING. I have no market update to uninstall. I've deleted marketupdater.apk. I've signed into Google talk manually. I've cleared market cache. Disabled compatability mode. Disable compcache. I've done EVERYTHING you can THINK of. I've Googled it for days and days. I don't think anyone else is having this problem.
Below is a logcat of when it dies. Seems like the quoted text before it might be important?
Edit: Seems if I do the search for the application it updates as normal. My only problem is with Market Downloads when updating (marketupdater.apk is still there for reference)! Sync issues?
android.providers.downloads.DownloadProvider is in dying process android.process.media
Click to expand...
Click to collapse
Code:
E/vending ( 5589): com.android.vending.cache.CacheManagerImpl.readFromDisk(): Reading cach
e file: GIR_6976532497457602818_0_0
E/vending ( 5589): java.io.EOFException
E/vending ( 5589): at java.io.DataInputStream.readShort(DataInputStream.java:375)
E/vending ( 5589): at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.ja
va:2402)
E/vending ( 5589): at java.io.ObjectInputStream.<init>(ObjectInputStream.java:445)
E/vending ( 5589): at com.android.vending.cache.CacheManagerImpl.readFromDisk(CacheMa
nagerImpl.java:308)
E/vending ( 5589): at com.android.vending.cache.CacheManagerImpl.get(CacheManagerImpl
.java:129)
E/vending ( 5589): at com.android.vending.api.RequestDispatcher.populateFromCache(Req
uestDispatcher.java:433)
E/vending ( 5589): at com.android.vending.api.RequestDispatcher.performRequestsFromCa
che(RequestDispatcher.java:138)
E/vending ( 5589): at com.android.vending.api.RequestManager.doRequestsFromCache(Requ
estManager.java:167)
E/vending ( 5589): at com.android.vending.api.RequestManager.doRequests(RequestManage
r.java:222)
E/vending ( 5589): at com.android.vending.AssetItemAdapter$ImagesRequest.doRequest(As
setItemAdapter.java:809)
E/vending ( 5589): at com.android.vending.AsynchRequestRunner$1.runRequestRetryingFai
lure(AsynchRequestRunner.java:57)
E/vending ( 5589): at com.android.vending.AsynchRequestRunner$1.run(AsynchRequestRunn
er.java:50)
E/vending ( 5589): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExe
cutor.java:1068)
E/vending ( 5589): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolEx
ecutor.java:561)
E/vending ( 5589): at java.lang.Thread.run(Thread.java:1096)
E/vending ( 5589): at com.android.vending.AsynchRequestRunner$VendingThreadFactory$Ve
ndingFactoryThread.run(AsynchRequestRunner.java:114)
D/dalvikvm( 5661): GC freed 2752 objects / 176128 bytes in 108ms
I/DumpStateReceiver( 154): Added state dump to 1 crashes
I/ActivityManager( 154): Process android.process.media (pid 5661) has died.
I/ActivityManager( 154): Killing app com.android.vending (pid 5589) because provider com.
android.providers.downloads.DownloadProvider is in dying process android.process.media
I/Process ( 154): Sending signal. PID: 5589 SIG: 9
I/ActivityManager( 154): Low Memory: No more background processes.
I/WindowManager( 154): WIN DEATH: Window{44115a00 com.android.vending/com.android.vending
.MyDownloadsActivity paused=false}
I/ActivityManager( 154): Process com.android.vending (pid 5589) has died.
I/WindowManager( 154): WIN DEATH: Window{44173d10 com.android.vending/com.android.vending
.AssetBrowserActivity paused=false}
I/ActivityManager( 154): Start proc com.android.vending for activity com.android.vending/
.AssetBrowserActivity: pid=5675 uid=10007 gids={3003}
I/ActivityManager( 154): Low Memory: No more background processes.
I/UsageStats( 154): Unexpected resume of com.android.vending while already resumed in com
.android.vending
I/ActivityThread( 5675): Publishing provider com.android.vending.SuggestionsProvider: com.
android.vending.SuggestionsProvider
D/dalvikvm( 5675): GC freed 2777 objects / 188480 bytes in 96ms
I/vending ( 5675): com.android.vending.api.RadioHttpClient$1.handleMessage(): Handle DATA_
STATE_CHANGED event: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspe
cified), extra: (none), roaming: false, failover: false, isAvailable: true
D/dalvikvm( 154): GC freed 13136 objects / 780520 bytes in 322ms
mine is a lil weird on the download tab also....if i hit download n leave it there itll restart the market....
if i hit downloads...and then click on one of the updateable apps real quick i can go back to the download tab with out a problem....a lil annoying sumtimes....but its really not that big of an issue for me
im having the exact same problem. it loads the downloads section then resets to market main. it does it a few times before i actually get to use it to update my apps.
Sorry, my computer died on me so I can't respond as often. No one has found a fix for this or any idea why this is happening?

I keep getting stuck here...

- waiting for device -
--------- beginning of /dev/log/main
E/logwrapper( 62): executing /system/xbin/run
rectory
I/logwrapper( 61): /system/xbin/run-parts ter
I/DEBUG ( 66): debuggerd: Jul 31 2010 00:18
D/AKMD ( 73): akmd 1.6.6 START
D/AKMD ( 73): library version: 1.2.1.1129
thats it it has happened on so many roms its annoying any clue?

Spontaneus data corruption?

I had to shut down my phone when getting on the plane last night and when I tried to boot it up it doesn't go any further than the kernel splash screen. Can't access recovery, download mode is working though. ADB is working after I fkasg Devil Kernel so I can access shell and logcat no problems.
The phone was running SlimBean with Semaphore previously but Semaphore did not provide me with ADB-access during kernel splash.
This is what comes out in logcat during boot:
Code:
--------- beginning of /dev/log/main
I/DEBUG ( 186): debuggerd: Jul 19 2012 13:10:13
--------- beginning of /dev/log/system
I/Vold ( 182): Vold 2.1 (the revenge) firing up
D/Vold ( 182): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 182): Volume emmc state changing -1 (Initializing) -> 0 (No-Media)
I/Netd ( 185): Netd 1.0 starting
D/Vold ( 182): Volume emmc state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 182): Volume emmc state changing 2 (Pending) -> 1 (Idle-Unmounted)
D/Vold ( 182): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 182): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
I/SurfaceFlinger( 187): SurfaceFlinger is starting
I/SurfaceFlinger( 187): use dithering
I/SurfaceFlinger( 187): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
E/FramebufferNativeWindow( 187): couldn't open framebuffer HAL (Not a typewriter)
E/FramebufferNativeWindow( 187): couldn't open gralloc HAL (Not a typewriter)
E/SurfaceFlinger( 187): Display subsystem failed to initialize. check logs. exiting...
I/Netd ( 240): Netd 1.0 starting
I/SurfaceFlinger( 241): SurfaceFlinger is starting
I/SurfaceFlinger( 241): use dithering
D/AndroidRuntime( 242):
D/AndroidRuntime( 242): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 242): CheckJNI is OFF
I/SurfaceFlinger( 241): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
E/FramebufferNativeWindow( 241): couldn't open framebuffer HAL (Not a typewriter)
E/FramebufferNativeWindow( 241): couldn't open gralloc HAL (Not a typewriter)
E/SurfaceFlinger( 241): Display subsystem failed to initialize. check logs. exiting...
It just loops on the SurfaceFlinger errors indef.
Any way of fixing this easily without having to wipe the internal sdcard partition? Got some pictures on there which I unfortunately have not synced to my backup yet :\
http://forum.xda-developers.com/showthread.php?t=1841250 and the 30s power button trick helped to get in to Recovery again but still the same boot error when booting.
Now at least I can try nowipe-reflashing slim from zip

(HELP) RootBox Rom Build

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.

Categories

Resources