Develop Bugs

[SOLVED] Recompile official kernel 2.6.29 - Sense 3D problem

Hello,
When I found out this morning that HTC has released their hero-2.6.29-5f74b252, I decided to go ahead and try to compile this without modifications. Just to make sure it works as the pre-compiled version before doing any modifications.
As I'm already running the official 2.1 (ChungHwa, same kernel as the source) I performed the following steps to try to replicate the official build:
Fetch kernel config from my device
Code:
adb pull /proc/config.gz config-htc-2.1.gz
Build zImage
Code:
export PATH=$PATH:<path/to/android/source>prebuilt/linux-x86/toolchain/arm-eabi-4.3.1/bin/
gunzip -c ../config-htc-2.1.gz > .config
make -j4 zImage ARCH=arm CROSS_COMPILE=arm-eabi-
After that I built a new wlan.ko and created a boot.img, followed by a signed update package and so on.
The kernel booted just fine and everything seemed to be working as it should. But sometimes when unlocking (lock screen) the phone and entering sense with the weather/clock widget (that shows a weather animation overlay in fullscreen) I get some bad looking gray-scale shapes flying over the screen. Also games like Labyrinth runs really slow after this problem occurs. Attaching screenshot of weather animation bug.
Has anyone else had similar experience with the released kernel source???
I've been running the official hero-2.6.29-5f74b252 kernel for quite some time now and never had any problems like this.
logcat (when unlocking)
Code:
I/HtcLockScreen( 90): touch ACTION_DOWN
D/skia ( 90): purging 191K from font cache [26 entries]
I/HtcLockScreen( 90): touch ACTION_UP
W/dalvikvm( 90): disableGcForExternalAlloc: true
D/HtcLockScreen( 90): unlock animationn done
I/HtcLockScreen( 90): Drag down to unlock screen
W/dalvikvm( 90): disableGcForExternalAlloc: false
I/HtcLockScreen( 90): HtcLockScreen:onPause
D/dalvikvm( 160): GC freed 9041 objects / 531616 bytes in 200ms
W/IndicatorRequest( 445): The running request PersonIndicatorRequest(112) is no longer valid... requeue it!
W/IndicatorRequest( 445): The running request PersonIndicatorRequest(112) is no longer valid... requeue it!
D/KeyguardViewMediator( 90): pokeWakelock(7000)
D/KeyguardViewMediator( 90): pokeWakelock(7000)
D/HtcLockScreen( 90): onScreenPause
D/KeyguardViewManager( 90): hide()
W/InputManagerService( 90): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy <at> 4494e8b0
D/dalvikvm( 1732): GC freed 1224 objects / 190144 bytes in 80ms
D/dalvikvm( 1732): GC freed 483 objects / 186216 bytes in 82ms
D/libEGL ( 1732): loaded /system/lib/egl/libGLES_qcom.so
[B]E/EGL.oem ( 1732): could not open hw3dc (Operation not permitted)
E/libEGL ( 1732): No EGLDisplay for hardware EGL!
E/copybit ( 1732): Error opening frame buffer errno=13 (Permission denied)
E/copybit ( 1732): Error opening frame buffer errno=13 (Permission denied)
E/copybit ( 1732): Error opening frame buffer errno=13 (Permission denied)[/B]
D/dalvikvm( 1533): GC freed 567 objects / 28344 bytes in 10 sec
dmesg (when unlocking)
Code:
<6>[ 4886.515686] request_suspend_state: wakeup (3->0) at 4883223881359 (2010-07-06 06:31:19.395568809 UTC)
<6>[ 4886.516357] [R] late_resume start
<6>[ 4886.517425] perflock_notifier_call: screen_on_policy_req 1,policy_min 480000
<6>[ 4886.517700] perflock_notifier_call: cpufreq recover policy 480000 528000
<6>[ 4886.538818] lightsensor_enable
<3>[ 4886.541076] lightsensor_enable: microp is suspended
<6>[ 4886.829010] msmfb: ready, waiting for full update
<6>[ 4886.829345] hero_ts_power:1
<6>[ 4886.836975] msmfb: pan_update in state(1)
<6>[ 4886.837005] msmfb: full update starting
<6>[ 4886.866638] msmfb: full update completed
<6>[ 4886.867065] msmfb: turning on panel
<7>[ 4886.907775] turn on backlight.
<6>[ 4887.109832] microp-i2c 0-0066: microp_i2c_auto_backlight_set_interrupt_mode: 1
<6>[ 4887.112579] [R] late_resume end
<7>[ 4887.613098] ALS value: 0x4, level: 2 #
<7>[ 4887.618255] ALS value: 0x4, level: 2 #
<6>[ 4887.649444] S1 <at> 2025, 2676
<6>[ 4887.925445] E1 <at> 2071, 5196
[B]<6>[ 4892.686065] hw3d_open: pid 1772 tid 1777 opening client node
<4>[ 4892.686340] hw3d_open: can't open hw3d while suspending
<6>[ 4892.697113] hw3d_open: pid 1772 tid 1777 opening client node
<4>[ 4892.697387] hw3d_open: can't open hw3d while suspending
<6>[ 4892.708160] hw3d_open: pid 1772 tid 1777 opening client node
<4>[ 4892.708435] hw3d_open: can't open hw3d while suspending
<6>[ 4892.719207] hw3d_open: pid 1772 tid 1777 opening client node
<4>[ 4892.719482] hw3d_open: can't open hw3d while suspending
<6>[ 4892.730255] hw3d_open: pid 1772 tid 1777 opening client node
<4>[ 4892.730560] hw3d_open: can't open hw3d while suspending
<6>[ 4892.741302] hw3d_open: pid 1772 tid 1777 opening client node
<4>[ 4892.741577] hw3d_open: can't open hw3d while suspending
<6>[ 4892.752532] hw3d_open: pid 1772 tid 1777 opening client node
<4>[ 4892.752807] hw3d_open: can't open hw3d while suspending
<6>[ 4892.763763] hw3d_open: pid 1772 tid 1777 opening client node
<4>[ 4892.764068] hw3d_open: can't open hw3d while suspending
<6>[ 4892.774871] hw3d_open: pid 1772 tid 1777 opening client node
<4>[ 4892.775146] hw3d_open: can't open hw3d while suspending
<6>[ 4892.785919] hw3d_open: pid 1772 tid 1777 opening client node
<4>[ 4892.786224] hw3d_open: can't open hw3d while suspending[/B]
<4>[ 4893.162109] select 1762 (ufou.android.su), adj 15, size 4030, to kill
<4>[ 4893.162384] send sigkill to 1762 (ufou.android.su), adj 15, size 4030
It seems as there is some kind of conflict with the power states, as if the kernel has not understood that the device is awake:
Code:
hw3d_open: can't open hw3d while suspending
arch / arm / mach-msm / hw3d.c
Code:
...
spin_lock_irqsave(&info->lock, flags);
if (info->suspending) {
pr_warning("%s: can't open hw3d while suspending\n", __func__);
ret = -EPERM;
spin_unlock_irqrestore(&info->lock, flags);
goto err;
}
...

Can you please share that .config? I need the one from an official 2.1 WWE based build, like the one you have. Thanks.

RaduG said:
Can you please share that .config? I need the one from an official 2.1 based build, like the one you have. Thanks.
Click to expand...
Click to collapse
Sure, attaching the config here

Thanks mate. I will compile now too and I'll let you know.

I bet its caused by the animated weather overlay from the clock widget, does it still happen if you remove the clock widget from your homescreen?

Yup, you're right it's caused by the animated weather overlay. It happens to be partly sunny here today, so some light clouds are supposed to fly over the screen after unlocking... and these are now the grayish boxes instead.
The problem on the attached picture will go away when removing the widget or just tapping the screen.
But there must be an underlaying problem with the new kernel (or my compilation at least) since the same problem also affects games that uses 3D, i.e. Labyrinth Lite for example.
The same "hw3d_open: can't open hw3d while suspending" can be seen when playing Labyrinth...

Just to add... after rebooting the problem does not usually show up immediately... meaning I will see the weather clouds etc (and games run smoothly). But after using the phone for a short while, i.e. unlocking a couple of times and perhaps opening a few 3D related apps the problem will appear. A reboot will again make it OK for a while and so on...

As I promised, I'm back with feedback.
I've done some kernel tweaks and enabled overclocking and it works properly. I get no 3D issues whatsoever. I need to optimize it because it is not working as I want it to(speed wise).

Thanks RaduG, I'm re-building again as well... and will double check that the code is clean first. Hope it solves my 3D issues as well...

Could it be, that if the Device is going into a "powersave" mode, some functions are going into standby and cannot come up, when the device is awaken?

Could be something like that...
I just finished another recompile after making sure the code from HTC was properly clean (ready to build), when running it it again looked perfectly OK for some time... but after starting and stopping i.e. Labyrinth (3D mode) and locking/unlocking a couple of times the problem came back :-(
I found a dmesg log indicating that the 3D "device" failed to suspend:
Code:
<6>[ 1272.269500] [R] suspend start
<6>[ 1272.275177] PM: Syncing filesystems ... done.
<4>[ 1272.281707] Freezing user space processes ... (elapsed 0.05 seconds) done.
<4>[ 1272.336822] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<3>[ 1272.362335] pm_op(): platform_pm_suspend+0x0/0x58 returns 1
[B]<3>[ 1272.363372] PM: Device msm_hw3d.0 failed to suspend: error 1[/B]
<3>[ 1272.363891] PM: Some devices failed to suspend

For me the following steps solved my problem...
I noticed that during compilation a few warnings was thrown related to the file "arch/arm/mach-msm/hw3d.c". When looking deeper into this it seems that the driver suspend function was wrong.
I therefore applied the following changes, and the problem has not re-occurred since then:
Code:
diff -crB hero-2.6.29-5f74b252/arch/arm/mach-msm/hw3d.c hero-2.6.29-5f74b252-pon/arch/arm/mach-msm/hw3d.c
*** hero-2.6.29-5f74b252/arch/arm/mach-msm/hw3d.c 2010-06-15 17:58:03.000000000 +0800
--- hero-2.6.29-5f74b252-pon/arch/arm/mach-msm/hw3d.c 2010-07-06 21:02:59.288988755 +0800
***************
*** 645,651 ****
}
#ifndef CONFIG_MSM_HW3D_EARLYSUSPEND_ENABLED
! static void hw3d_suspend(struct platform_device *pdev)
{
struct hw3d_info *info = platform_get_drvdata(pdev);
unsigned long flags;
--- 645,651 ----
}
#ifndef CONFIG_MSM_HW3D_EARLYSUSPEND_ENABLED
! static int hw3d_suspend(struct platform_device *pdev, pm_message_t state)
{
struct hw3d_info *info = platform_get_drvdata(pdev);
unsigned long flags;

your patch is very usaful!

I'm glad if you find it useful

So what did RaduG change?

Guys, you're really crazy, doing kernel hacking and stuff... and I'm loving it
I was wondering: if these are the official kernel sources, HTC should have used these sources for the official kernel. So, why doesn't this happen with the official kernel?

xdafalter said:
Guys, you're really crazy, doing kernel hacking and stuff... and I'm loving it
I was wondering: if these are the official kernel sources, HTC should have used these sources for the official kernel. So, why doesn't this happen with the official kernel?
Click to expand...
Click to collapse
Because they removed a few lines of codes to "fully" support all the hardware

I'm kinda wondering the same thing, it's hard to know if the source is really the exact one that HTC used for our device. But it could also be affected by i.e. which gcc version was used to compile it. I'm gonna compare the GCC version as soon as I bother to boot up the official kernel again. I'm currently using arm-eabi-4.3.1 (because it's the only one I happen to have installed) while I've seen that most people seem to use arm-eabi-4.4.0 by now.
Regardless of if another compiler would make it work I think I will stick to the patch, as this is the expected format of a suspend function for a platform driver of this kernel version
Code:
struct platform_driver {
int (*probe)(struct platform_device *);
int (*remove)(struct platform_device *);
void (*shutdown)(struct platform_device *);
[B]int (*suspend)(struct platform_device *, pm_message_t state);[/B]
int (*suspend_late)(struct platform_device *, pm_message_t state);
int (*resume_early)(struct platform_device *);
int (*resume)(struct platform_device *);
struct device_driver driver;
};
As you would see it's supposed to return an int (not void) as well as taking an additional parameter (pm_message_t).

Hi, All,
I have some problems while compiling the WIFI driver with this kernel.
it seems something changed we didn't know with the WIFI support? I use the same .config works great with the leak version of kernel source, but with this official one, it doesn't work.
if I check the wlan.ko module with insmod, it can be loaded.
and use lsmod, it's there but just not work.

witysimon said:
Hi, All,
I have some problems while compiling the WIFI driver with this kernel.
it seems something changed we didn't know with the WIFI support? I use the same .config works great with the leak version of kernel source, but with this official one, it doesn't work.
if I check the wlan.ko module with insmod, it can be loaded.
and use lsmod, it's there but just not work.
Click to expand...
Click to collapse
cant confirm that, wifi is working fine here, sure you rebuild your wlan.ko with the new kernel sources and not using the old one?

[Q] What is IQFD?

I don't know if this question belongs here but I figure a dev might know what this means. Sometimes my phone will become VERY sluggish and when I open the System Panel which is monitoring the phone in the background, it will show the CPU usage pegged at 98-100%... When I check what apps are consuming cpu with this same app, it shows a system service named IQFD as the culprit. I usually have to reboot my phone in other to clear everything up.
Anyone?

Try Advanced Task Killer next time you see that process running. Kill off apps one by one, hopefully if one of those kill the process - you'll be able to identify the offending app

Whatever it is, I doubt it will be stopped by a task killer, but I'm pretty sure it is related to this:
http://en.wikipedia.org/wiki/Quality_function_deployment
If your phone is rooted, you can try freezing the app using Titanium Backup. OSMonitor may work; I don't remember if root is needed for that app, but I don't think so. If it locks up your phone when you stop the app, just pull the battery and reboot. I am not sure if it is essential for the OS to function, but you can try.
Also, I'm pretty sure this should go in the Q&A section.

I've actually have had the same symptoms since flashing kings bfs kernel, I usually reboot to recovery them clear dalvik cache. It also takes an abnormal amount of time for the dalvik to wipe

Bump, this is getting annoying

I started seeing the same thing today - was running netarchy's 4.1.8 BFS for several days and it was great. Today the phone's almost unusable because iqfd is taking all the CPU, which also runs the battery down. I restored back to an earlier kernel (4.0.3 I think) and it's not doing it.
While it was looping, I tried a few things that needed root like Titanium Backup, and an "su" command in Terminal Emulator and they both failed with Permission Denied.
Very Disturbing.

I installed the latest Netarchy kernel yesterday (CFS, IIRC) and it was working great until tonight, when randomly I started having /system/bin/iqfd go to 100%. I noticed the following:
- It came back after reboots
- It seemed to stay gone after I killed it using OSMonitor until I shut off the display. Once I shut off the display, it would always come back.
- I was doing some development of an app when I first started noticing this. Eclipse started acting up when I told it to deploy... this could be unrelated, but just a note.
- I restored to the Stock Froyo kernel, and it seems to be fixed for the moment.

i get this too iw onder if this has anything to do with BFQ of BFS or HAVS. i only starrted getting this issue once these were introduced into the kernels. its really annoying though

It seems that IQFD is one of two CIQ daemons launched by init. I believe CIQ stands for Carrier IQ. This startup company is a provider of intelligence solutions to the wireless industry, using embedded diagnostic software, to give them a real-time picture of network activity. Carrier IQ's client list includes Sprint.

Here's some more information I've found on CIQ.
/system/bin/iqd is the CIQ backend daemon.
/system/bin/iqfd is the CIQ frontend daemon.
The two CIQ daemons are launched by /init.
Code:
# cat init.supersonic.rc
...
# CIQ backend daemon
service iqd /system/bin/iqd
user root
group root system
# CIQ frontend daemon
service iqfd /system/bin/iqfd
user root
group root system
...
I confirmed their parent process is /init and found that com.htc.android.iqagent is launched by zygoyte. com.htc.android.iqagent (possibly com.carrieriq.iqagent.service on other devices?) is the Android Client.
Code:
# ps
USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 348 256 c00cc66c 0000d2ac S /init
...
root 292 1 124020 29572 c00cc66c afd0dd44 S zygote
...
root 306 1 10468 1432 ffffffff afd0dd44 S /system/bin/iqd
root 307 1 4828 780 ffffffff afd0ea5c S /system/bin/iqfd
...
app_29 439 292 157168 22440 ffffffff afd0ebd8 S com.htc.android.iqagent
...
The CIQ backend daemon is an active server on the device running on port 2479.
Code:
# busybox netstat -lp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
...
tcp 0 0 0.0.0.0:2479 0.0.0.0:* LISTEN 306/iqd
...
Active UNIX domain sockets (only servers)
Proto RefCnt Flags Type State I-Node PID/Program name Path
...
unix 2 [ ACC ] STREAM LISTENING 7409 306/iqd /app-cache/iqserver
...
CIQ has some associated libraries, devices, parameters, and a profile. The profile contains a URL to the collector along with some other info probably used to identify the type of device and network.
Code:
# find / -name *iq*
...
/app-cache/iqserver
/data/data/com.htc.android.iqrd
/data/data/com.htc.android.iqagent
/sys/devices/virtual/misc/pmem_ciq
/sys/devices/virtual/misc/pmem_ciq1
/sys/devices/virtual/misc/pmem_ciq2
/sys/devices/virtual/misc/pmem_ciq3
...
/sys/class/misc/pmem_ciq
/sys/class/misc/pmem_ciq1
/sys/class/misc/pmem_ciq2
/sys/class/misc/pmem_ciq3
/sys/module/smd/parameters/ciq_info
/system/lib/libciq_client.so
/system/lib/libhtciqagent.so
/system/lib/libciq_htc.so
/system/etc/iqprofile.pro
...
/system/bin/iqd
/system/bin/iqfd
/dev/pmem_ciq3
/dev/pmem_ciq2
/dev/pmem_ciq1
/dev/pmem_ciq
The following CIQ log entries are extracted from multiple logs (not a single log) that I have seen in various forum postings. These could be application event failures. I don't see these on a healthy device.
Code:
...
D/CIQ ( 116): throwUI04 com.htc.bgp
D/CIQ ( 116): processName com.htc.bgp
D/CIQ ( 116): throwUI05 com.htc.RosieUtility
D/CIQ ( 116): processName
D/CIQ ( 112): throwUI05 com.htc.bg
D/CIQ ( 112): processName com.htc.bg
D/CIQ ( 66): throwUI04 com.newsrob
D/CIQ ( 66): processName com.newsrob
D/CIQ ( 66): throwUI03
D/CIQ ( 66): processName com.coremobility.app.vnotes
D/CIQ ( 3833): throwUI04 android.process.media
D/CIQ ( 3833): processName android.process.media
D/CIQ ( 3833): throwUI04 com.htc.android.iqagent
D/CIQ ( 3833): processName com.htc.android.iqagent
D/CIQ ( 3833): throwUI04 com.google.process.gapps
D/CIQ ( 3833): processName com.google.process.gapps
D/CIQ ( 3833): throwUI04 com.android.wallpaper
D/CIQ ( 3833): processName com.android.wallpaper
D/CIQ ( 3833): throwUI04 com.htc.android.htcime
D/CIQ ( 3833): processName com.htc.android.htcime
D/CIQ ( 3833): throwUI04 com.android.phone
D/CIQ ( 3833): processName com.android.phone
D/CIQ ( 3833): throwUI04 android.process.acore
D/CIQ ( 3833): processName android.process.acore
D/CIQ ( 3833): throwUI04 com.htc.launcher
D/CIQ ( 3833): processName com.htc.launcher
...
Maybe if the IQ Server (iqd) is not responding, then the IQ Client (iqfd) is constantly trying to reconnect. I found the following log snippet from other posts in the forums about similiar issues.
Code:
...
E/com_htc_android_iqagent_Controller( 129): backend daemon was not ready!
D/IQClient( 51): wait for backend daemon ready ...
D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
D/IQServer( 50): Reset the timeout to 3000(ms) for AlarmSet retry...
D/IQJavaJob( 50): JavaRequestAlarmSet: Java job client is not connected now!
D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
D/IQServer( 50): Reset the timeout to 3000(ms) for AlarmSet retry...
D/IQJavaJob( 50): JavaRequestAlarmSet: Java job client is not connected now!
D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
D/IQServer( 50): Reset the timeout to 3000(ms) for AlarmSet retry...
D/IQJavaJob( 50): JavaRequestAlarmSet: Java job client is not connected now!
D/IQServer( 50): JavaRequestAlarmSet is failed... Will not release wakelock[ciq-backend]!
D/IQServer( 50): Reset the timeout to 3000(ms) for AlarmSet retry...
...
That's all I have. Please provide any additional information you have.

Reporting in from unlocked land
Wanted to report I had this same issue this morning, iqfd @ 101.1% (!?!) over the previous 8 hours according to System Panel. But I'm running the stock froyo rom from Sprint.

jazmatician said:
Wanted to report I had this same issue this morning, iqfd @ 101.1% (!?!) over the previous 8 hours according to System Panel. But I'm running the stock froyo rom from Sprint.
Click to expand...
Click to collapse
Wait wait.
So Stock Froyo. As in No Root, No Custom Recovery, and no custom kernel?

a lot of good ifnormation. now we need to figure out a way to try to prevent it from hosing up the phone

Yes. This and "Suspend" drestroy my battery after a few days and requires a battery pull. Because simply resetting doesn't fix it.
...in 1943, I killed a drifter.

any update on this?

I don't know of this will help but it seems to have worked for me so far. It was running away on me as well and I couldn't find any solution on the forum. I cleared the cache and it hasn't done it in four days. It was going crazy at least once a day before that. Running netarchys latest.
Sent from my PC36100 using XDA App

jnewkirk10 said:
I don't know of this will help but it seems to have worked for me so far. It was running away on me as well and I couldn't find any solution on the forum. I cleared the cache and it hasn't done it in four days. It was going crazy at least once a day before that. Running netarchys latest.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
exactly which cache did u clear?

The only way I've been able to avoid this IQFD hang up has been with the 4.1.9.1 CFS build of netarchy's kernel. I'm not saying that it's a BFS issue, but it's just not present while running on this particular kernel. My girlfriend and I both have an evo, one with Fresh 3.2, one with Fresh 3.1.0.2, and both had the same problem.

I also have not had issues using CFS kernels and first noticed it had started happenign to me around the time i switched to the BFS kingxkernel. not sure if it is coincidence but so far have been ok with both kingx 8 and netarchy cfs version.

Having a hell of a time with this process just the last 24 hrs. This is ridiculous - the phone is unusable! Trying to flash a CFS kernel right now to see if that fixes it...

[Q] 4.0.3 AOSP build stuck at google logo. Kernel problem?

Hey guys,
i have a problem when building 4.0.3 from source. When i flash the fresh compiled
OTA package to my device, the device ends in a bootloop stuck at the google logo.
Logcat says:
Code:
I/SystemServer( 238): Power Manager
I/SystemServer( 238): Activity Manager
I/ActivityManager( 238): Memory class: 64
I/SurfaceFlinger( 251): SurfaceFlinger is starting
I/SurfaceFlinger( 251): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
E/IMGSRV ( 251): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086860 (Bad address).
E/IMGSRV ( 251): :0: OpenServices: PVRSRVBridgeCall failed.
E/IMGSRV ( 251): :0: PVRSRVConnect: Unable to open connection.
E/IMGSRV ( 251): :0: OpenPVRServices: Failed to open services connection
E/IMGSRV ( 251): :0: hal_init: Failed to open services (err=-14)
E/IMGSRV ( 251): :0: hal_open: Graphics HAL not initialized
E/FramebufferNativeWindow( 251): couldn't open framebuffer HAL (Not a typewriter)
E/IMGSRV ( 251): :0: hal_open: Graphics HAL not initialized
E/FramebufferNativeWindow( 251): couldn't open gralloc HAL (Not a typewriter)
E/SurfaceFlinger( 251): Display subsystem failed to initialize. check logs. exiting...
I/ServiceManager( 109): service 'sensorservice' died
I/ServiceManager( 109): service 'power' died
I/ServiceManager( 109): service 'entropy' died
D/AndroidRuntime( 259):
D/AndroidRuntime( 259): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 259): CheckJNI is OFF
I don't know whats going wrong. Can it be a kernel problem? I have tried different 4.0.3 kernels from the dev section, but the result is the same.
The device is a GSM device with PRIMEKK15 unlocked bootloader and I9250XXKK6 baseband.
After pulling the latest 4.0.3 sources with repo and setting up the proprietary files i'have compiled the system without errors:
Code:
~/android/4.0.3$ . build/envsetup.sh
~/android/4.0.3$ lunch full_maguro-userdebug
~/android/4.0.3$ make -j4 otapackage
I really don't understand what i am doing wrong ...
Thanks for any suggestions or answers.

Soft Bricked my Galaxy Nexus,HELP!!

I soft bricked my Galaxy Nexus .I formatted everything on that device, its completely empty(not purposely)(no android files in sd and no system files backup is not available too).Please can anyone help me to return my nexus to stock and BTW I also rooted my nexus before and tried to install a custom rom but it failed and thus later led to this situation.I am on mac please send advices which can be done on mac :roll eyes: .I want it fixed please please please help me!!

Custom Rom installation failed??
How are you flashing them?
Or getting any error?
Sent from my C6603 using xda app-developers app

Sorry, but wrong section mate! This is the correct section for ur device:
http://forum.xda-developers.com/forumdisplay.php?f=1431
I have asked the mods to move this post.
"To err is human, to forgive is divine"
Sent from my SGS II

Tritinum said:
I soft bricked my Galaxy Nexus .I formatted everything on that device, its completely empty(not purposely)(no android files in sd and no system files backup is not available too).Please can anyone help me to return my nexus to stock and BTW I also rooted my nexus before and tried to install a custom rom but it failed and thus later led to this situation.I am on mac please send advices which can be done on mac :roll eyes: .I want it fixed please please please help me!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1626895
follow this.

It looks like I sofbricked my gnex too. I restored my CM10.1 RC2 copy then dirty-flashed RC3, phone booted but then restarted immediately (it's been like that over and over again). I thought it could be dirty flash that caused this issue so I did full wipe and reflashed everything....As a result I didn't even go beyond the boot animation screen - bootloop and then restart! I restored my stock backup - the same. I wiped everything reflashed stock image using standrad fastboot procedure...IT didn't do the trick either. Still bootloop + reboot!
Perhaps I will try Odin and then Omap flash....but I start to think that it can be something related to CPU (overheat - I did couple of backup/restore/install processes in a row indeed. and last time I checked CPU temp was about 65-70 centigrades). I decided to turn it off and wait an hour or two.

forever_lol said:
It looks like I sofbricked my gnex too. I restored my CM10.1 RC2 copy then dirty-flashed RC3, phone booted but then restarted immediately (it's been like that over and over again). I thought it could be dirty flash that caused this issue so I did full wipe and reflashed everything....As a result I didn't even go beyond the boot animation screen - bootloop and then restart! I restored my stock backup - the same. I wiped everything reflashed stock image using standrad fastboot procedure...IT didn't do the trick either. Still bootloop + reboot!
Perhaps I will try Odin and then Omap flash....but I start to think that it can be something related to CPU (overheat - I did couple of backup/restore/install processes in a row indeed. and last time I checked CPU temp was about 65-70 centigrades). I decided to turn it off and wait an hour or two.
Click to expand...
Click to collapse
its almost like you totally missed the link i posted right above your post.
impressive.

Zepius said:
its almost like you totally missed the link i posted right above your post.
impressive.
Click to expand...
Click to collapse
You're kidding right? Did you even read what I posted? You clearly misunderstand what my issue is all about.
I know how to flash nexus in every possible way and I DID it several times today (even repartitioned). Phone boots in bootloader, recovery, download mode without any issues. Installation goes smooth and it's always successful. Problems begin when I try to restart the system. It just simply reboots after couple of seconds. I can hardly reach welcome screen. Forget about signing in. I am not a tech guy but It looks like it can be related to processor power circuit. Device reboots when cpu speeds up. I cannot even enable (usb-debugging) to get the logcat.
EDIT: OMAP flash didn't help either. I guess my adventure with gnex is over. It was imported via ebay so no warranty, I am not really willing to pay for motherboard replacement or stuff like that.

You could just have flashed a custom rom that has adbd enabled and get access to see logs at least from the android boot process.
Sent from my Nexus

It looks like a hardware defect anyway. I bought N4 today. I'll take a deeper look in gnex when I have more time.

bk201doesntexist said:
You could just have flashed a custom rom that has adbd enabled and get access to see logs at least from the android boot process.
Sent from my Nexus
Click to expand...
Click to collapse
I took your advice and pushed rasbean jelly via adb (recovery) and managed to get a logcat (I mean before it rebooted on bootanimantion screen
Code:
--------- beginning of /dev/log/main
I/installd( 132): installd firing up
E/IMGSRV ( 122): :0: SetupuKernel : EDM status value DevVAddr: 0x0F004000 pvLinAddrKM: 0xC89B1000
--------- beginning of /dev/log/system
I/Vold ( 121): Vold 2.1 (the revenge) firing up
E/Vold ( 121): Error reading configuration (No such file or directory)... continuing anyways
I/DEBUG ( 126): debuggerd: May 26 2013 17:30:01
I/Netd ( 125): Netd 1.0 starting
W/InterfaceController( 125): Warning (Cannot load library: load_library(linker.cpp:771): library "/system/lib/libnetcmdiface.so" not found) while opening the net interface command library
I/SurfaceFlinger( 128): SurfaceFlinger is starting
I/SurfaceFlinger( 128): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL ( 128): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/ ( 127): [CP BOOT] __boot_6260: START CP BOOT
D/libEGL ( 128): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 128): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
D/ ( 127): [CP BOOT] __boot_6260: CP POWER ON DONE
D/ ( 127): [CP BOOT] mipi_xmit_atat: SENT ATAT 0
I/mediaserver( 131): ServiceManager: 0x419e2e30
I/AudioFlinger( 131): Using default 3000 mSec as standby time.
I/CameraService( 131): CameraService started (pid=131)
D/ ( 127): [CP BOOT] mipi_xmit_atat: SENT ATAT 1
I/AudioPolicyManagerBase( 131): loadAudioPolicyConfig() loaded /system/etc/audio_policy.conf
I/ti_hwc ( 128): clone region is set to (0,0) to (720,1280)
I/ti_hwc ( 128): external display changed (state=0, mirror={disabled tform=0deg}, dock={disabled tform=0deg}, tv=0
I/ti_hwc ( 128): omap4_hwc_device_open(rgb_order=1 nv12_only=0)
I/SurfaceFlinger( 128): Using composer version 1.0
W/SurfaceFlinger( 128): getting VSYNC period from fb HAL: 16954612
W/SurfaceFlinger( 128): no suitable EGLConfig found, trying without EGL_FRAMEBUFFER_TARGET_ANDROID
I/AudioFlinger( 131): loadHwModule() Loaded primary audio interface from Tuna audio HW HAL (audio) handle 1
I/AudioFlinger( 131): HAL output buffer size 144 frames, normal mix buffer size 864 frames
I/SurfaceFlinger( 128): EGL informations:
I/SurfaceFlinger( 128): vendor : Android
I/SurfaceFlinger( 128): version : 1.4 Android META-EGL
I/SurfaceFlinger( 128): extensions: EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_fence_sync EGL_ANDROID_image_native_buffer
I/SurfaceFlinger( 128): Client API: OpenGL_ES
I/SurfaceFlinger( 128): EGLSurface: 8-8-8-8, config=0x2
I/SurfaceFlinger( 128): OpenGL ES informations:
I/SurfaceFlinger( 128): vendor : Imagination Technologies
I/SurfaceFlinger( 128): renderer : PowerVR SGX 540
I/SurfaceFlinger( 128): version : OpenGL ES-CM 1.1
I/SurfaceFlinger( 128): extensions: GL_EXT_debug_marker GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_matrix_get GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_point_sprite GL_OES_point_size_array GL_OES_matrix_palette GL_OES_draw_texture GL_OES_query_matrix GL_OES_texture_env_crossbar GL_OES_texture_mirrored_repeat GL_OES_texture_cube_map GL_OES_blend_subtract GL_OES_blend_func_separate GL_OES_blend_equation_separate GL_OES_stencil_wrap GL_OES_extended_matrix_palette GL_OES_framebuffer_object GL_OES_rgb8_rgba8 GL_OES_depth24 GL_OES_stencil8 GL_OES_compressed_ETC1_RGB8_texture GL_OES_mapbuffer GL_OES_EGL_image GL_OES_EGL_image_external GL_EXT_multi_draw_arrays GL_OES_required_internalformat GL_IMG_read_format GL_IMG_texture_compression_pvrtc GL_IMG_texture_format_BGRA8888 GL_EXT_texture_format_BGRA8888 GL_OES_egl_sync GL_IMG_vertex_array_object
I/SurfaceFlinger( 128): GL_MAX_TEXTURE_SIZE = 2048
I/SurfaceFlinger( 128): GL_MAX_VIEWPORT_DIMS = 2048 x 2048
I/AudioMixer( 131): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
E/MonoPipe( 131): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
D/SurfaceFlinger( 128): Screen acquired, type=0 flinger=0x4203c318
D/ ( 127): [CP BOOT] __boot_6260: XIMT PSI DONE
D/ ( 127): [CP BOOT] __boot_6260: XIMT EBL DONE
D/ ( 127): [CP BOOT] __boot_6260: SET EBL DONE
D/ ( 127): [CP BOOT] __boot_6260: REQSECSTART CMD DONE
D/AndroidRuntime( 129):
D/AndroidRuntime( 129): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 129): CheckJNI is OFF
D/MDnsDS ( 125): MDnsSdListener::Hander starting up
D/MDnsDS ( 125): MDnsSdListener starting to monitor
D/MDnsDS ( 125): Going to poll with pollCount 1
D/libEGL ( 293): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 293): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 293): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
D/dalvikvm( 129): Trying to load lib libjavacore.so 0x0
D/dalvikvm( 129): Added shared lib libjavacore.so 0x0
D/dalvikvm( 129): Trying to load lib libnativehelper.so 0x0
D/dalvikvm( 129): Added shared lib libnativehelper.so 0x0
W/dalvikvm( 129): Failed to mount /storage as MS_SLAVE: Invalid argument

Evervolv 3.2/CM10.1 (4.2.2) development thread -All welcome

{
"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 start of the Evervolv build for the PrimoU, it should give us all a good base to learn how to build from source and get more roms up and running for this device. The original device tree and msm7x30 come from @1ceb0x who I am extremely grateful for helping me understand the little I already do.
https://github.com/mcgi5sr2 contains all the sources I have so far.
Working:
boot to adb
Not Working:
Everything else
XDA:DevDB Information
EV3.2/CM10.1 restart, a ROM for the HTC One V
Contributors
mcgi5sr2, mcgi5sr2, MScorporation95
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.0.x
ROM Firmware Required: PrimoU
Based On: AOSP
Version Information
Status: Alpha
Current Stable Version: N/A
Created 2014-04-07
Last Updated 2014-04-17

Status:
20140407: Rom boots past HTC logo and adb is available, no bootanimation
Handy Terminal Commands:
#Make rom command can use mka instead in CM based roms, also creates log -j* indicates number of cores to use in building
make -j8 otapackage 2>&1 | tee filename.log
#Adds logcat pull request -thanks Lloir
add this to your init.primou.rc
service logcat /system/bin/logcat -f /data/data/logcat
class main
oneshot
reboot into recovery once you got "enough"
adb pull /data/data/logcat
and tada you have a logcat
#Pulls last kernel kmsg - reboot straight into recovery then pull -thanks Simon
adb pull /proc/last_kmsg kernel.txt
#Clears the heads for a new clean sync - helps fix repo sync issues
repo forall -vc "git reset --hard"

So building from source is fun and can take a lot of time. Ultimately it will benefit you and the community somehow.
http://forum.xda-developers.com/showthread.php?t=2060017
Is a good starting point.
http://wiki.cyanogenmod.org/w/Development
Also contains loads of info on how to get started on it all
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
and also how to port
http://elinux.org/Android_Build_System
How building works...
Also the Evervol git hub:
https://github.com/Evervolv/android
will show you the sources we are currently using, I have no qualms with anyone going freelance and splitting into their own sources or anything else they want to try. I can help with the compiling errors etc, where I can but not with anything after that as I am yet to get through all of that myself.
Anyway I am trying to build the JellyBean version which relates to EV3.2 or Android 4.2.2

Code:
I/DEBUG ( 7076): memory map around fault addr deadbaad:
I/DEBUG ( 7076): be9f8000-bea19000 [stack]
I/DEBUG ( 7076): (no map for address)
I/DEBUG ( 7076): ffff0000-ffff1000 [vectors]
I/Netd (24351): Netd 1.0 starting
W/InterfaceController(24351): Warning (Cannot load library: load_library(linker.cpp:747): library "/system/lib/libnetcmdiface.so" not found) while opening the net interface command library
D/MDnsDS (24351): MDnsSdListener::Hander starting up
D/MDnsDS (24351): MDnsSdListener starting to monitor
D/MDnsDS (24351): Going to poll with pollCount 1
I/SurfaceFlinger(24558): SurfaceFlinger is starting
I/SurfaceFlinger(24558): use dithering
I/SurfaceFlinger(24558): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL (24558): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL (24558): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL (24558): loaded /system/lib/egl/libGLESv2_adreno200.so
I/Adreno200-EGL(24558): <qeglDrvAPI_eglInitialize:294>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_JB.04.01.01.00.036_msm8960_JB_CL2644550_release_AU (CL2644550)
I/Adreno200-EGL(24558): Build Date: 07/31/12 Tue
I/Adreno200-EGL(24558): Local Branch:
I/Adreno200-EGL(24558): Remote Branch: quic/master
I/Adreno200-EGL(24558): Local Patches: NONE
I/Adreno200-EGL(24558): Reconstruct Branch: AU_LINUX_ANDROID_JB.04.01.01.00.036 + NOTHING
I/gralloc (24558): using (fd=20)
I/gralloc (24558): id = msmfb40_0
I/gralloc (24558): xres = 480 px
I/gralloc (24558): yres = 800 px
I/gralloc (24558): xres_virtual = 480 px
I/gralloc (24558): yres_virtual = 2400 px
I/gralloc (24558): bpp = 32
I/gralloc (24558): r = 0:8
I/gralloc (24558): g = 8:8
I/gralloc (24558): b = 16:8
I/gralloc (24558): width = 52 mm (234.461533 dpi)
I/gralloc (24558): height = 88 mm (230.909088 dpi)
I/gralloc (24558): refresh rate = 60.00 Hz
D/CALCFPS (24558): DEBUG_CALC_FPS: 0
D/CALCFPS (24558): period: 10
D/CALCFPS (24558): ignorethresh_us: 500000
D/CALCFPS (24558): DEBUG_CALC_FPS: 0
D/CALCFPS (24558): period: 10
D/CALCFPS (24558): ignorethresh_us: 500000
E/HAL (24558): load: module=/system/lib/hw/hwcomposer.msm7x30.so
E/HAL (24558): Cannot load library: soinfo_relocate(linker.cpp:989): cannot locate symbol "_ZN7overlay7Overlay12waitForVsyncENS_5utils5eDestE" referenced by "hwcomposer.msm7x30.so"...
E/SurfaceFlinger(24558): hwcomposer module not found
W/SurfaceFlinger(24558): getting VSYNC period from fb HAL: 16666666
W/Adreno200-EGL(24558): <qeglDrvAPI_eglChooseConfig:780>: EGL_BAD_ATTRIBUTE
W/SurfaceFlinger(24558): no suitable EGLConfig found, trying without EGL_FRAMEBUFFER_TARGET_ANDROID
W/SurfaceFlinger(24558): no suitable EGLConfig found, trying without EGL_RECORDABLE_ANDROID
E/Trace (24558): error opening trace file: No such file or directory (2)
Code:
D/AndroidRuntime(24561):
D/AndroidRuntime(24561): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime(24561): CheckJNI is OFF
D/dalvikvm(24561): Trying to load lib libjavacore.so 0x0
D/dalvikvm(24561): Added shared lib libjavacore.so 0x0
D/dalvikvm(24561): Trying to load lib libnativehelper.so 0x0
D/dalvikvm(24561): Added shared lib libnativehelper.so 0x0
E/dalvikvm(24561): ERROR: couldn't find native method
E/dalvikvm(24561): Requested: Landroid/net/wifi/WifiNative;.killSupplicant:(Z)Z
E/dalvikvm(24561): Candidate: Landroid/net/wifi/WifiNative;.killSupplicant:()Z
E/JNIHelp (24561): RegisterNatives failed for 'android/net/wifi/WifiNative', aborting
F/libc (24561): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 24561 (zygote)
I/DEBUG ( 7076): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Seems its a wifi issue holding us up right now
@Lloir fancy throwing any helpful hints.

What I am trying to do next...
##New Stuff to look into
Its a Framework reboot issue. You need to collect ADB logs from the boot up.
adb logcat -v threadtime > logcat.txt
adb shell cat /proc/kmsg > kernellogs.txt
.............
adb bugreport > bugreport.txt
................
Make sure you clear below things at the beginning
/data/anr/*
/data/tombstone/*
Pull the traces and tombstone files from the /data/anr and /data/tombstone
adb pull /data/anr/ .
adb pull /data/tombstone .
Note: You can save in any folder by logging it outside the adb shell prompt
Search for the time stamp where you encountered the Framework reboot.
Map it appropriately with the traces/tombstones to find the issue
Click to expand...
Click to collapse
Scratch the tombstone bit as we don't seem to have that on the phone :'(

Hah Good luck. I can help you if you need, but I don't think that we can do new 4.2 base for it

Minto107 said:
Hah Good luck. I can help you if you need, but I don't think that we can do new 4.2 base for it
Click to expand...
Click to collapse
Thanks Minto, but I'm not sure what you mean?

This phone is not supported like some years ago. There is no one who can help us
Wysłane z mojego HTC One V przy użyciu Tapatalka

Minto107 said:
This phone is not supported like some years ago. There is no one who can help us
Wysłane z mojego HTC One V przy użyciu Tapatalka
Click to expand...
Click to collapse
If there's no one who can help us, we'll stick together and make it work..
@mcgi5sr2 I'm almost ready just syncing repos...

This phone is a fail and it was a fail so what do you want from it? It was next bad HTC phone, now there are more bad than good ones. Sure we can try.
Wysłane z mojego HTC One V przy użyciu Tapatalka

Minto107 said:
This phone is a fail and it was a fail so what do you want from it? It was next bad HTC phone, now there are more bad than good ones. Sure we can try.
Wysłane z mojego HTC One V przy użyciu Tapatalka
Click to expand...
Click to collapse
did you suddenly completely lose confidence.
and poland has a cool national anthem.
@mcgi5sr2 What's in logcat ...?

It's caused that I was using One S and S3 last time
Wysłane z mojego HTC One V przy użyciu Tapatalka

MameTozhio said:
did you suddenly completely lose confidence.
and poland has a cool national anthem.
@mcgi5sr2 What's in logcat ...?
Click to expand...
Click to collapse
I don't get what national anthem have to losing confidence because of bad phones

Hi guys,
I'm too happy to see people actually alive on the forum to worry about phone. Agreed it is a difficult beast, but I figure if we cut our teeth here everything else is only going to be easier in future! Also I think that a lot of the lessons we learn on Evervolv will help CM10.1 and then CM11 builds as well. The more of us know something about the phone, how it works, what loving it needs the better.
Logcat:
logcat.txt - 646.91 KB
BugReport:
bugreport.txt - 614.13 KB
Traces:
traces.txt.bugreport - 1.15 KB
I'm still perusing to try and work out what the magic is, I am starting to think its a frameworks problem, but thats only from the similarity in issues with other people I've found on google.
 @MameTozhio thanks for sticking with us !
 @MScorporation95 will do eventually we will end up as genuine Devs!
 @Minto107 I agree with almost all you said, but I have the phone until at least September, want to learn to Dev some more, and also don't know what I would do with a top of the line super powered phone right now...

Anything new? I'm looking at logcat which you sent.
---------- Post added at 07:59 PM ---------- Previous post was at 07:55 PM ----------
First: There is a problem with Adreno drivers
Many libs are missing
This rly important lib is missing: libnetcmdiface.so ROM is calling it really often

Minto107 said:
Anything new? I'm looking at logcat which you sent.
---------- Post added at 07:59 PM ---------- Previous post was at 07:55 PM ----------
First: There is a problem with Adreno drivers
Many libs are missing
This rly important lib is missing: libnetcmdiface.so ROM is calling it really often
Click to expand...
Click to collapse
Not made any real progress on EV3.2 but have now got a CM10.1 built and squished the first booting issue today. Will post sources once I'm back on a good connection. I am genuinely hopeful that we may get a build up and running both for CM10.1 and EV as AOSP.
With all this learning then we can apply it to CM11!
Sorry to be taking so long, but I am travelling for courses all month.

why everlov, sphongle is based on everlov

Hi cyber,
I used evervolv for that exact reason so that I could learn how it was done, and what did what. Also evervolv is a good base for use as it has legacy depositories.
I am also working through CM10.1 right now as well, I have ADB up and running and am currently looking for a fix for this badger
W/InterfaceController( 9806): Warning (Cannot load library: load_library(linker.cpp:771): library "/system/lib/libnetcmdiface.so" not found) while opening the net interface command library
might be able to add it to packages in the device make, but need to do a bit more research first. OK seemed to do the trick including the package, next up seems to be an egl error:
I/Netd ( 4825): Netd 1.0 starting
D/MDnsDS ( 4825): MDnsSdListener::Hander starting up
D/MDnsDS ( 4825): MDnsSdListener starting to monitor
D/MDnsDS ( 4825): Going to poll with pollCount 1
I/SurfaceFlinger( 5033): SurfaceFlinger is starting
I/SurfaceFlinger( 5033): use dithering
I/SurfaceFlinger( 5033): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL ( 5033): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 5033): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 5033): loaded /system/lib/egl/libGLESv2_adreno200.so
I/Adreno200-EGL( 5033): <qeglDrvAPI_eglInitialize:294>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_JB.04.01.01.00.036_msm8960_JB_CL2644550_release_AU (CL2644550)
I/Adreno200-EGL( 5033): Build Date: 07/31/12 Tue
I/Adreno200-EGL( 5033): Local Branch:
I/Adreno200-EGL( 5033): Remote Branch: quic/master
I/Adreno200-EGL( 5033): Local Patches: NONE
I/Adreno200-EGL( 5033): Reconstruct Branch: AU_LINUX_ANDROID_JB.04.01.01.00.036 + NOTHING
F/libc ( 5033): Fatal signal 11 (SIGSEGV) at 0x00000001 (code=1), thread 5034 (SurfaceFlinger)
I/DEBUG ( 1513): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1513): Build fingerprint: 'htc_europe/htc_primou/primou:4.2.2/JDQ39/330937:user/user-debug'
I/DEBUG ( 1513): Revision: '2'
I/DEBUG ( 1513): pid: 5033, tid: 5034, name: SurfaceFlinger >>> /system/bin/surfaceflinger <<<

Cool Rom!

Any progress?
Waiting for CM10.1 eagerly!
:good::good::good: