This was not written by me. It was written by Ayman al-Sanad, username UAE (I believe), who has been working for some time to create workable libraries for so Android devices can properly display Arabic. Oddly there was no thread posted here that I can find so I'm going to go ahead and post it, since I know this is a much-desired feature for many people and at least some people will find it over Google or the like.
As Google has yet to add native support for Right-To-Left languages like Arabic, Persian and Urdu (despite it being the top feature request) Ayman stepped in and created libraries for our usage.
The downloads page is available here: http://ardoid.com/?page_id=5. I'm assuming the libraries will work with any Froyo install. Put the library zip on your SD card, flash it. Reboot will take some time on a black screen.
Big thanks to Ayman for his great work. Evo libraries are also available on his page.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is the best news yet!!! i will try right now and report back
Works Perfect !!!!! i can't believe it's finally happening. thank you very much for posting
Dose this works with WebOS (Palm Pre) ?
amjz said:
Dose this works with WebOS (Palm Pre) ?
Click to expand...
Click to collapse
Really? Your in a forum for an ANDROID device, and if that wasn't enough of a hint, the OP says "ANDROID" in the first line.
works perfectly, Thanks for the heads up
Problem with ROM updates
The ZIP files on the ardoid.com site worked perfectly with my phone. This was when Verizon rolled out the Froyo update, and i was able to use the same ZIP files for both a stock ROM as well as a custom one.
But couple weeks ago, Verizon rolled out a minor update to Froyo (2.2.1 I think), and it was also picked up by some developers of custom ROMs. Once I applied any of these updates, I am unable to use the Arabic ZIP file anymore.
Here is what I usually do:
- Use the ROM Manager to download the new ROM.
- Reboot to recovery mode and apply the ROM (done automatically by the ROM Manager).
- Verify the ROM is working correctly.
- Download the Ariabic ZIP file from ardoid.con.
- Reboot to Custom Recovery, and manually apply the Arabic update.
- Reboot the phone one last time.
- The phone remains stuck in the HTC Incredible splash screen.
The only way out is to remove the battery, boot into recovery mode, and do a restore.
I tried this approach with the Virtuous ROM 3.1 and the CyanogenMod 6.1. In both cases, I was trying "froyo_incredible_libs_arabic_android_plus_signed.zip".
I also tried the following ZIP files, and they both failed (didn't expect them to work anyway):
- froyo_stock_generic_signed.zip
- froyo_cm_n1_6_1_1_stable_arabic_android_plus_signed.zip
The questions that I have are:
- Is there a dependency for the ZIP file on the actual system image? Does this mean that there has to be a new ZIP file for the 2.2.1 release?
- Is there another preferred way for applying the ZIP file? (I am using ClockworkMod Recover 2.5.0.5).
Quick update
I would like to add one little detail: using CyanogenMod 6.1, most apps have decent Arabic support by default (for example, tweetdeck or facebook). Unfortunately, the browser doesn't know how to join the Arabic letters correctly (doesn't matter if I am using the stock browser, or Dolphin).
I tried pushing the libwebcore.so and libskia.so files from the Desire HD ZIP from http://ardoid.com/?p=176
I copied the files to the SD card, then copied them over the original files using ADB. After the reboot, the phone got stuck in an endless loop, and here is what I saw repeated when doing "adb logcat":
W/dalvikvm( 1311): ERROR: Unable to find decl for native Landroid/webkit/BrowserFrame;.clearNativeCache ()V
E/JNIHelp ( 1311): RegisterNatives failed for 'android/webkit/BrowserFrame'
E/webcoreglue( 1311): WebFrame registration failed!
W/dalvikvm( 1311): JNI_OnLoad returned bad version (-1) in /system/lib/libwebcore.so 0x0
W/dalvikvm( 1311): Exception Ljava/lang/UnsatisfiedLinkError; thrown during Landroid/webkit/WebViewCore;.<clinit>
E/Zygote ( 1311): Error preloading android.webkit.WebViewCore.
E/Zygote ( 1311): java.lang.ExceptionInInitializerError
E/Zygote ( 1311): at java.lang.Class.classForName(Native Method)
E/Zygote ( 1311): at java.lang.Class.forName(Class.java:235)
E/Zygote ( 1311): at java.lang.Class.forName(Class.java:182)
E/Zygote ( 1311): at com.android.internal.os.ZygoteInit.preloadClasses(ZygoteInit.java:302)
E/Zygote ( 1311): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:589)
E/Zygote ( 1311): at dalvik.system.NativeStart.main(Native Method)
E/Zygote ( 1311): Caused by: java.lang.UnsatisfiedLinkError: Library webcore not found
E/Zygote ( 1311): at java.lang.Runtime.loadLibrary(Runtime.java:461)
E/Zygote ( 1311): at java.lang.System.loadLibrary(System.java:557)
E/Zygote ( 1311): at android.webkit.WebViewCore.<clinit>(WebViewCore.java:61)
E/Zygote ( 1311): ... 6 more
E/Zygote ( 1311): setreuid() failed. errno: 17
D/AndroidRuntime( 1311): Shutting down VM
W/dalvikvm( 1311): threadid=1: thread exiting with uncaught exception (group=0x4001d7f0)
D/skia ( 1311): purging 6K from font cache [1 entries]
I/ServiceManager( 105): service 'media.audio_flinger' died
I/ServiceManager( 105): service 'media.player' died
I/ServiceManager( 105): service 'media.camera' died
I/ServiceManager( 105): service 'media.audio_policy' died
I/ ( 1312): ServiceManager: 0xaec8
I think the root cause is "JNI_OnLoad returned bad version (-1) in /system/lib/libwebcore.so 0x0", but I am not sure what this means, or how to fix it.
Here is another update..
I tried to copy the libwebcore.so and libskia.so directly without the ZIP file. I basically extracted the two library files to a folder "Arabic/New" on my sdcard. The I did the following steps using ADB:
- remount the system mount as rw.
- copy the files from the SD to /system/lib
- change the permission to 644
- reboot
Here is the capture from my CMD console
===========================
C:\my_program_files\Android\android-sdk-windows\platform-tools>adb remount
remount succeeded
C:\my_program_files\Android\android-sdk-windows\platform-tools>adb shell
# su
su
# ls -l /system/lib/libwebcore.so
ls -l /system/lib/libwebcore.so
-rw-r--r-- 1 root root 4859848 Dec 22 19:08 /system/lib/libwebcore.so
# ls -l /system/lib/libskia.so
ls -l /system/lib/libskia.so
-rw-r--r-- 1 root root 1126112 Dec 22 19:08 /system/lib/libskia.so
# cp -f /sdcard/Arabic/New/libwebcore.so /system/lib
cp -f /sdcard/Arabic/New/libwebcore.so /system/lib
# cp -f /sdcard/Arabic/New/libskia.so /system/lib
cp -f /sdcard/Arabic/New/libskia.so /system/lib
# ls -l /system/lib/libwebcore.so
ls -l /system/lib/libwebcore.so
----rwxr-x 1 root root 5118240 Dec 22 19:11 /system/lib/libwebcore.so
# ls -l /system/lib/libskia.so
ls -l /system/lib/libskia.so
----rwxr-x 1 root root 1126552 Dec 22 19:11 /system/lib/libskia.so
# chmod 644 /system/lib/libwebcore.so
chmod 644 /system/lib/libwebcore.so
# chmod 644 /system/lib/libskia.so
chmod 644 /system/lib/libskia.so
# ls -l /system/lib/libwebcore.so
ls -l /system/lib/libwebcore.so
-rw-r--r-- 1 root root 5118240 Dec 22 19:11 /system/lib/libwebcore.so
# ls -l /system/lib/libskia.so
ls -l /system/lib/libskia.so
-rw-r--r-- 1 root root 1126552 Dec 22 19:11 /system/lib/libskia.so
# reboot
reboot
===========================
After the reboot, the phone gets stuck on the white screen
When I look at the log file via "adb logcat", I see it frozen at:
===========================
--------- beginning of /dev/log/main
I/cm ( 73): Welcome to Android 2.2.1 / CyanogenMod-6.1.0-Inc
I/cm ( 74): _
I/cm ( 75): __ __ _ ___ _ _ __ ___ __ _ _ _ _ __ __))
I/cm ( 76): ((_ \(/'((_( ((\( ((_)((_( (('((\( ((`1( ((_)((_(
I/cm ( 77): )) _))
I/cm ( 78):
I//system/xbin/run-parts( 68): modprobe: chdir(2.6.32.26-invisiblek-aosp): No such file or directory
I//system/xbin/run-parts( 68): run-parts: /system/etc/init.d/04modules exited with code 1
I/mountsd ( 93): Checking filesystems..
I//system/xbin/run-parts( 68): e2fsck 1.41.10 (10-Feb-2009)
I//system/xbin/run-parts( 68): e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p1
I//system/xbin/run-parts( 68): Filesystem mounted or opened exclusively by another program?
E/mountsd ( 99): Unable to repair filesystem, disabling apps2sd
I/logwrapper( 68): /system/xbin/run-parts terminated by exit(1)
I/DEBUG ( 108): debuggerd: Dec 12 2010 12:46:44
D/AK8973 ( 115): AK8973 daemon 1.3.3 Start
D/AK8973 ( 115): (Library version : 1.2.1.620)
--------- beginning of /dev/log/system
I/Vold ( 106): Vold 2.1 (the revenge) firing up
I/Netd ( 107): Netd 1.0 starting
D/Vold ( 106): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 106): Volume emmc state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 106): Volume emmc state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 106): Volume emmc state changing 2 (Pending) -> 1 (Idle-Unmounted)
D/Vold ( 106): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 106): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
===========================
In comparison, when the phone was booting before, here is what the log would look like:
===========================
--------- beginning of /dev/log/main
I/cm ( 73): Welcome to Android 2.2.1 / CyanogenMod-6.1.0-Inc
I/cm ( 74): _
I/cm ( 75): __ __ _ ___ _ _ __ ___ __ _ _ _ _ __ __))
I/cm ( 76): ((_ \(/'((_( ((\( ((_)((_( (('((\( ((`1( ((_)((_(
I/cm ( 77): )) _))
I/cm ( 78):
I//system/xbin/run-parts( 68): modprobe: chdir(2.6.32.26-invisiblek-aosp): No such file or directory
I//system/xbin/run-parts( 68): run-parts: /system/etc/init.d/04modules exited with code 1
I/mountsd ( 93): Checking filesystems..
I//system/xbin/run-parts( 68): e2fsck 1.41.10 (10-Feb-2009)
I//system/xbin/run-parts( 68): e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p1
I//system/xbin/run-parts( 68): Filesystem mounted or opened exclusively by another program?
E/mountsd ( 99): Unable to repair filesystem, disabling apps2sd
I/logwrapper( 68): /system/xbin/run-parts terminated by exit(1)
I/DEBUG ( 108): debuggerd: Dec 12 2010 12:46:44
D/AK8973 ( 115): AK8973 daemon 1.3.3 Start
D/AK8973 ( 115): (Library version : 1.2.1.620)
--------- beginning of /dev/log/system
I/Vold ( 106): Vold 2.1 (the revenge) firing up
I/Netd ( 107): Netd 1.0 starting
D/Vold ( 106): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 106): Volume emmc state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 106): Volume emmc state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 106): Volume emmc state changing 2 (Pending) -> 1 (Idle-Unmounted)
D/Vold ( 106): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 106): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
D/AndroidRuntime( 110):
D/AndroidRuntime( 110): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
I/AndroidRuntime( 110): Heap size: -Xmx32m
D/AndroidRuntime( 110): CheckJNI is OFF
D/dalvikvm( 110): creating instr width table
I/ ( 111): ServiceManager: 0xaec8
===========================
Are there any protection mechanisms that is preventing the phone from continuing the boot. If there is an issue with the library file, then I would expect a more specific error message when the library is loaded. However, it seems that the boot sequence is being aborted even before loading libwebcore.so or libskia.so
By the way, I have my phone rooted a long time ago. I think that was using the "unrevoked forever", and I have "SHIP S-OFF" on the main boot screen.
It finally worked!
I downloaded the ZIP file for the Cyanogn Nexus 6.1.1 from http://ardoid.com/?p=21 (I was starting from a CyanogenMod 6.1 for HTC Droid Incredible).
I repeated the same steps as before, but with the following exceptions:
- I copied the "libwebcore.so" file alone (didn't update the libskia.so).
- I rebooted the phone as usual rather than via ADB.
I am not sure which step made the difference, but at least my phone can boot, and most importantly, I can now see proper Arabic text in the browser. Other apps looks fine as well (tweetdeck, reader, etc.). I was even able to enter Arabic text using the browser (in Google search) and everything looked perfect.
I don't know what I might be missing by not updating ibskia.so, but things look really nice already.
Thanks Ayman for helping me out (via Twitter)!!!
Related
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
- 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?
As the title states, and the logcat. Seemed to have lost part of my recovery, yet my recovery still works, though Im thinking its not working correctly.
Still a Noob, yes Im going back to donut, little worried about this error, or is it just a fastboot a new recovery.img?
Code:
C:\android-sdk-windows\tools>adb logcat
I//system/xbin/busybox( 47): +++ "Pleased to meet you, we came to drop bombs o
n you!"
I//system/xbin/busybox( 47): +++ Welcome to Android 1.6 / Super D-blk 1.10.4
I//system/xbin/busybox( 47): +++ Starting Shadow's Renice
I//system/xbin/busybox( 47): --- Executing firstboot.sh
I//system/bin/sh( 50): rmmod: delete_module 'ramzswap' failed (errno 2)
I//system/xbin/busybox( 47): +++ Shadow Script: wait 140s for process to start
on first boot
I/logwrapper( 50): /system/bin/sh terminated by exit(0)
I//system/xbin/busybox( 47): --- Checking filesystems
I//system/xbin/busybox( 47): e2fsck 1.41.9 (22-Aug-2009)
I//system/xbin/busybox( 47): /dev/block/mmcblk0p2: recovering journal
I//system/xbin/busybox( 47): /dev/block/mmcblk0p2: clean, 41/249856 files, 504
52/499713 blocks
I//system/xbin/busybox( 47): cp: can't stat '/data/app-private/*': No such fil
e or directory
I//system/xbin/busybox( 47): cp: can't stat '/data/dalvik-cache/*': No such fi
le or directory
I//system/xbin/busybox( 47): +++ Apps-to-SD successfully enabled
I//system/xbin/busybox( 47): +++ Running Media to Data script
I//system/xbin/busybox( 47): mv: can't rename '/system/media': Read-only file
system
I//system/xbin/busybox( 47): link failed File exists
I//system/xbin/busybox( 47): *** media2data: ERROR2 making symlink to /data/me
dia
I//system/xbin/busybox( 47): *** media2data: pls report to dev
I//system/xbin/busybox( 47): mv: can't rename '/system/media-bck': No such fil
e or directory
I/vold ( 166): Android Volume Daemon version 2.0
I/DEBUG ( 167): debuggerd: Mar 3 2010 17:56:48
I/vold ( 166): New MMC card '00000' (serial 1892747644) added @ /devices/pla
tform/msm_sdcc.2/mmc_host/mmc1/mmc1:0001
I/vold ( 166): Disk (blkdev 179:0), 15949824 secs (7788 MB) 3 partitions
I/vold ( 166): New blkdev 179.0 on media 00000, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:0001, Dpp 3
I/vold ( 166): Partition (blkdev 179:1), 14761718 secs (7207 MB) type 0xc
I/vold ( 166): New blkdev 179.1 on media 00000, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:0001, Dpp 2
I/vold ( 166): Partition (blkdev 179:2), 1000000 secs (488 MB) type 0x83
I/vold ( 166): New blkdev 179.2 on media 00000, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:0001, Dpp 1
I/vold ( 166): Partition (blkdev 179:3), 188105 secs (91 MB) type 0x82
I/vold ( 166): New blkdev 179.3 on media 00000, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:0001, Dpp 0
I/vold ( 166): Evaluating dev '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mm
c1:0001/block/mmcblk0' for mountable filesystems for '/sdcard'
I/vold ( 166): Aborting start of /sdcard (bootstrap = 1)
I/vold ( 166): Volmgr not ready to handle device
D/vold ( 166): Bootstrapping complete
E/flash_image( 173): error opening /data/recovery.img: No such file or director
y
fastbooted new recovery img. Good to go.
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?
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