[ICS] CyanogenMod 9 for the Ascend G300 [LINK UP]

[Guest tilal6991]

What???? Never even heard of that before.

What's the output of:

adb shell

ls /dev/log

ls /dev

please?

[Guest FlatPackPete]

root@android:/ # ls /dev/log

ls /dev/log

/dev/log: No such file or directory

1|root@android:/ # ls /dev

ls /dev

accel

adsp

akm8975_dev

alarm

android_adb

android_adb_enable

apr_apps_user

ashmem

binder

block

compass_aot

console

cpu_dma_latency

cpuctl

device-mapper

diag

full

fuse

genlock

graphics

hw_extern_sdcard

hw_extern_sdcardMounted

hw_led

i2c-0

i2c-1

i2c-debug-0

i2c-debug-1

input

key_test

keychord

kgsl-3d0

kmem

kmsg

light

mem

msm_aac

msm_amrnb

msm_amrnb_in

msm_amrwb

msm_camera

msm_evrc

msm_evrc_in

msm_fm

msm_mp3

msm_mvs

msm_pcm_ctl

msm_pcm_dec

msm_pcm_in

msm_pcm_out

msm_preproc_ctl

msm_qcelp

msm_qcelp_in

msm_snd

msm_voicememo

msm_wma

msm_wmapro

msmdma

mtd

network_latency

network_throughput

null

oncrpc

pmem

pmem_adsp

pmem_audio

ppp

proximity

ptmx

pts

random

rfkill

rmt_oeminfo

rmt_storage

rtc0

rtc1

share_mem

smd0

smd1

smd17

smd2

smd21

smd22

smd27

smd3

smd36

smd4

smd7

smd_pkt_loopback

smd_sns_dsps

smdcntl0

smdcntl1

smdcntl2

smdcntl3

smdcntl4

smdcntl5

smdcntl6

smdcntl7

smem_log

smem_sleep_log

snd

socket

tgt

tty

ttyGS0

ttyGS1

ttyHS0

uinput

urandom

zero

[Guest FlatPackPete]

First, sorry the massive post above, I thought the code tags would put it in a scrollable box.

The touchscreen was way off but I did the "ca t > /system/usr/idc/synaptics.idc"command on the previous page and that has fixed that.

I also tried the commands on "/dev/kgsl-3d0" but it's no good, you can't get past the lock screen, it just keeps coming up with "Unfortunately, Trebuchet has stopped" error when you drag the circle over the padlock

Edited June 5, 2012 by FlatPackPete

[Guest tilal6991]

http://goo.im/devs/tilal6991/boot.img New boot image to flash.

[Guest FlatPackPete]

sorry, no change and no logcat available

[Guest]

My first look at cm9 on g300 such a tease.

I put the boot.img in rom zip on sd card,even put apek launcher in for good measure,boots fine,can see lockscreen and option to choose launcher,both launchers dont respond,and as above,touchscreen is way off.

Could not wait,had to have a look.lol

Edited June 5, 2012 by Guest

[Guest Gary_J_Wright]

CWM'd the cm9 and could only fastboot the 'NEW' boot image seems the same as previous ,we get boot animation, then lock screen with cursor pointer that will unlock the screen for a few seconds (showing a camera icon and a unlocked padlock) then it relocks, only other thing that seems to work is the power button to turn on screen

[Guest tilal6991]

I'll put up a new fixed version soon. I'll get rid of HW accel but it'll allow the system to work.

[Guest Davidoff59]

NeoMJ, how far along were you? You mentioned touchscreen wasn't working but was there any force closures or did they not present themselves as touch wasn't being registered?

Would his image help Tilal or is it likely that his build will have the same issues?.

[Guest FlatPackPete]

Any idea what's going on with no logcat?

[Guest tilal6991]

The reason for the fcs is the ambitious way in which I tried to enable full hw acceleration on the first build. Its a simple fix. Getting rid if hw fixes fcs.

[Guest tilal6991]

Any idea what's going on with no logcat?

Huawei have been sneaky with the kernel. Any overactive change results in a cut off of logcat.

[Guest neoMJ]

NeoMJ, how far along were you? You mentioned touchscreen wasn't working but was there any force closures or did they not present themselves as touch wasn't being registered?

Would his image help Tilal or is it likely that his build will have the same issues?.

Unfortunately my build's Touchscreen does not work so I can't see if the Trebuchet launcher force closes... Can't pass throught the lock screen. I have created the synaptics.idc file but touch screen is still not working. (I even tried the boot.img of tilal6991 but it didn't work too).

My logcat is also not working. It says /dev/log/main does not exist.

[Guest tilal6991]

The line in BoardConfig about legacy touch screen fixes that.

[Guest neoMJ]

The line in BoardConfig about legacy touch screen fixes that.

Actually I have tried this but it did not work somehow.

BOARD_USE_LEGACY_TOUCHSCREEN := true

[Guest tilal6991]

Weird. That's the only thing I changed to do with touchscreen.

[Guest timfimjim]

I'd be happy to test a bit but never done any adb work before - anyone point me to a tutorial?

Thanks everyone for your work and testing so far!! :D

[Guest FlatPackPete]

I'd be happy to test a bit but never done any adb work before - anyone point me to a tutorial?

I'm sure there's one on here somewhere, but this one on XDA is pretty good

http://forum.xda-developers.com/showthread.php?t=1241935

[Guest tilal6991]

My last for today:

http://goo.im/devs/tilal6991/u8815/ROMs/CFX/update-cm-9-20120605-SNAPSHOT-u8815-ColdFusionX-tilal6991-signed.zip

It may be laggy but hopefully the launcher won't fc.

[Guest FlatPackPete]

Just a FIY I'm off for the night and I'm in work tomorrow so someone else will have to pick up the guinea pig duties until tomorrow evening :)

[Guest]

Was it this hard for the skate ? or do you think huawei have made a mess with this one ?

Edited June 5, 2012 by Guest

[Guest tilal6991]

With the skate all this I was able to do locally so, it took much less time. Since I actually don't have the device it seems tougher,

[Guest]

How you are doing this with no device is amazing.

Are you still hoping to get one then ?

Ok,lets get this flashed and see what happens.......

Rebooting.....

Not even booting :(

I can try some adb ? but you will have to help me with that,I am very noob with adb ;)

edit: adb cannot see my device now?

Oh well,you done good tilal,days work there.

Edited June 5, 2012 by Guest

[Guest Gary_J_Wright]

when its boot looping (stuck on logo) battery out hold down volume battery in and power on holding volume down still, wait about 10-15 seconds and plug in USB cable , then reflash CWM- you then can either use adb again and/or restore a backup

Edited June 5, 2012 by Gary_J_Wright

[Guest tilal6991]

Dd flash the previous boot.img. That should get you a working adb.