Database Develop

No service, independent of ROM

Hello people,
while trying out some Eclair(-/Hero) ROMs today, i suddenly had problems testing since, whatever eclair ROM i flashed, it just wouldn't boot. logcat gave me errors about "ConnectionService" not being able to start.... so i checked whether my nandroid backup of CM 4.2.10.1 would do the trick, however, i had no signal there as well! whenever i tried to enter settings->Wireless->Mobile i got a settings FC! any ideas?

You answered your own problem
Look @ the SPL in your sig it says "Hard SPL"
EClair roms need Haykuro
You sealed your won fate.

so not even flashing the new spl and radio will solve his problem?

melterx12 said:
so not even flashing the new spl and radio will solve his problem?
Click to expand...
Click to collapse
It could also be a hardware problem with the phone's antenna being damaged or broken.
@OP try another rom like enom/dwang/wesgarner those are 1.6 roms so try then report back
Notice:They dont need the ADP image to be installed, just wipe and install the rom.

Well Ace42, it wasn't the SPL ( i flashed haykuro yesterday, just forgot to update sig ) it somehow works now, but i've got problems getting back to CM now. here's the logcat:
Code:
[...]default android stuff[...]
I//system/xbin/busybox( 48): cp: cannot stat '/data/dalvik-cache/*': No such file or directory
I//system/xbin/busybox( 48): +++ Apps-to-SD successfully enabled
I/logwrapper( 48): /system/xbin/busybox terminated by exit(0)
I/DEBUG ( 128): debuggerd: Dec 17 2009 21:34:52
E/flash_image( 134): error opening /data/recovery.img: No such file or directory
I/vold ( 127): Android Volume Daemon version 2.0
I/vold ( 127): New MMC card 'NCard' (serial 614381121) added @ /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:b368
I/vold ( 127): Disk (blkdev 179:0), 15659008 secs (7646 MB) 3 partitions
I/vold ( 127): New blkdev 179.0 on media NCard, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:b368, Dpp 3
I/vold ( 127): Partition (blkdev 179:1), 14763672 secs (7208 MB) type 0xb
I/vold ( 127): New blkdev 179.1 on media NCard, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:b368, Dpp 2
I/vold ( 127): Partition (blkdev 179:2), 610470 secs (298 MB) type 0x83
I/vold ( 127): New blkdev 179.2 on media NCard, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:b368, Dpp 1
I/vold ( 127): Partition (blkdev 179:3), 273105 secs (133 MB) type 0x82
I/vold ( 127): New blkdev 179.3 on media NCard, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:b368, Dpp 0
I/vold ( 127): Evaluating dev '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:b368/block/mmcblk0' for mountable filesystems for '/sdcard'
I/vold ( 127): Aborting start of /sdcard (bootstrap = 1)
I/vold ( 127): Volmgr not ready to handle device
D/vold ( 127): Bootstrapping complete
so far i've tried:
wipe ext
wipe data
reflash HTC recovery & then CM
flash different rom, then HTC recovery & then CM
still won't boot any ideas?

try to format your sd card and partition it again

[Q] I need some help with this logcat, if some more experianced devs can take a look

I am working on something, been playing in the Kernel+initramfs corner all day.
Finally got the tab to boot, even if it doesnt draw a UI, its past the Bootlooping.
Problem is, I just dont understand what some of this stuff means, i am pretty green on the kernel level, and porting.
So, can yall pitch in, help me figure out what this stuff means. I would appreciate.
Jim
to much text to paste, so i will zip it an attach the file instead.

Whatever happened to this problem?

blacklevel said:
Whatever happened to this problem?
Click to expand...
Click to collapse
I had rebuilt the kernel and ramdisk, didnt want to bring that thread back to life.
regarding this LC, i see at least in my inexperience, the obvious Dbus issue, possible cache issue with the init, i have a theory that at a minimum fixing the sdcard mount issue might fix the cache issue, the dbus, well i am about to yank all references out of the init in hopes it fixes that issue as I think the source rom i am porting not having a dbus and my putting one in as the init was looking for one, may be the problem.
And in theory, the app and framework problems might be solved whgen the caching issue is fixed?
Am i on the right path?

You definitely need dbus running.
On my GSM tab with technomancers latest CM7 the first few lines in the logcat look like this:
Code:
--------- beginning of /dev/log/main
I/DEBUG ( 82): debuggerd: Aug 7 2011 19:55:51
--------- beginning of /dev/log/system
I/Vold ( 80): Vold 2.1 (the revenge) firing up
I/cm ( 106): Welcome to Android 2.3.5 / CyanogenMod-7-2011-08-07-Beta-GalaxyTab-KANG
I/cm ( 108): _
I/cm ( 110): __ __ _ ___ _ _ __ ___ __ _ _ _ _ __ __))
I/cm ( 111): ((_ \(/'((_( ((\( ((_)((_( (('((\( ((`1( ((_)((_(
I/cm ( 112): )) _))
I/cm ( 113):
D/Vold ( 80): Volume emmc state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 80): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 80): Volume emmc state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 80): Volume emmc state changing 2 (Pending) -> 1 (Idle-Unmounted)
D/Vold ( 80): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 80): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
I/Netd ( 81): Netd 1.0 starting
D/Vold ( 80): USB connected
D/Vold ( 80): Share method ums now available
D/Vold ( 80): USB connected
I/logwrapper( 75): /system/xbin/busybox terminated by exit(0)
Yes, there are no references to dbus. But it is still running:
Code:
~# ps w
(...)
87 root 1272 S /system/bin/dbus-daemon --system --nofork
(...)
These are the corresponding lines the logcat you provided here:
Code:
--------- beginning of /dev/log/main
I/DEBUG ( 81): debuggerd: Aug 7 2011 19:55:51
I/cm ( 104): Welcome to Android 2.3.5 / CyanogenMod-7-2011-08-07-Beta-GalaxyTab-KANG
I/cm ( 106): _
W/libdbus ( 85): Failed to start message bus: Failed to open "/etc/dbus.conf": Permission denied
I/cm ( 108): __ __ _ ___ _ _ __ ___ __ _ _ _ _ __ __))
I/cm ( 110): ((_ \(/'((_( ((\( ((_)((_( (('((\( ((`1( ((_)((_(
I/cm ( 112): )) _))
I/cm ( 114):
I//system/xbin/busybox( 75): sysctl: /etc/sysctl.conf: No such file or directory
--------- beginning of /dev/log/system
I/Vold ( 79): Vold 2.1 (the revenge) firing up
E/Vold ( 79): Error reading configuration (No such file or directory)... continuing anyways
D/Vold ( 79): USB connected
D/Vold ( 79): Share method ums now available
I/Netd ( 80): Netd 1.0 starting
I/logwrapper( 75): /system/xbin/busybox terminated by exit(0)
You can see that both, dbus and vold are borked. Also /etc/sysctl.conf is not accessible. Maybe these problems are all for the same reason.
Can you check if /etc exists at all? It should be a symbolic link to /system/etc. Perhaps it is just that this link is not created. Perhaps the permissions of the /system/etc directory are wrong.
How is the initramfs configured?

I needed to update this thread.
Got past dbus, cache and /etc/sysctl.conf issue.
System booted to animated skating droid, and the 2 large issues currently are an EGL Bad Display, and Zygote. otherwise logcat looks ok so far.
I had to modify the init from the Sprint kernel i had originally released for the 2 Gingerbread roms for the tab, I removed all references to the GSM cache and partitions setup.
Right now, EGL and Zygote are my focus. I dont understand where the problem, is am basically running a sprint kernel 2.3.4 from source, so same video drivers.
I am so new to some of this more technical stuff, I have learned so much in past few days, but, i tool along as best I can

Great, you made some progress. How does the logcat currently look like?

ICS problem

hi,
I'm trying to make an ICS rom for the Sensation XL, but run into a problem with the internal storage.
This is the log from the boot:
Code:
D/VoldCmdListener( 1507): volume mount_encrypted /mnt/sdcard {} off
I/Vold ( 1507): /dev/block/vold/16777215:255 being considered for volume sdcard
D/Vold ( 1507): Volume sdcard state changing 1 (Idle-Unmounted) -> 3 (Checking)
E/Vold ( 1507): Failed to open loopdevice (No such file or directory)
E/Vold ( 1507): /dev/block/vold/16777215:255 may be encrypted, but could not be mounted as such
D/Vold ( 1507): Volume sdcard state changing 3 (Checking) -> 1 (Idle-Unmounted)
I think /dev/block/vold/16777215:255 is wrong... should be /dev/block/vold/179:33 ... but I have no idea where to change that in the rom.
Perhaps someone had a problem like this already...

Try to follow the path on your device, and see what you can find. Most info is available on your device.
Use root explorer to find what you need.
Send from my BinDroid Sensation XL with Tapatalk

U using Dsixda's kitchen?
What's your edify file for the runnymede say?

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.