22 replies to this topic

[hecatae]

LG have just released the Optimus L7, running ICS, sadly they want £300 for it, and seeing as it's the same cpu as the G300, seems a waste of money.

But, would anyone like to try and help me port the rom to the g300?

got a system dump here: http://www.handy-faq...a_euroopen.html

we can probably borrow the libs for ics anyway

[omegamoon]

I'm interested But in order to do so we need an ICS kernel. I tried flasing the L7 image, but that doesn't work. I got the original G300 kernel config and I will now try to build my own ICS kernel. Lets see if that works out

[tilal6991]

Ooooooo. Welll that'll certainly help with CM9....

Can't wait to get my hands on this phone now...

[Frankish]

I'm happy to test anything but otherwise I'm pretty much useless.

[tilal6991]

Just use the system from the LG and the boot image of the GB Huawei. That should atleast get you to logcat stages. From there working backwards should get a working build.

[Frankish]

Are you sure on the price too? Seems extortionate at 3x the price of the G300!

Love that massive dialer screen though!

Edited by Frankish, 11 May 2012 - 10:12 AM.

[omegamoon]

I'll reflash to see if I can get hold of the logging to see why it is bootlooping

[Frankish]

Is there any chance of us using the libs for cm9 at all or would we still need kernel source from Huawei?

[tilal6991]

We could use all the libs from the LG. The kernel source would help but initially it wouldn't make a difference.

[Frankish]

Sounds good where do we start then ha ha.

Was going to install the LG System to grab some logcats but my pc reboots every time i think something is dying somewhere and i've got to be at work soon. Hopefully by tonight there will be some progress

Edited by Frankish, 11 May 2012 - 11:18 AM.

[hecatae]

Frankish, on 11 May 2012 - 10:11 AM, said:

Are you sure on the price too? Seems extortionate at 3x the price of the G300!

Love that massive dialer screen though!

seen it for £299 payg or £249 sim free, let me see if i can find something else

[omegamoon]

I'm unable to get logcat logging so far... it's constantly rebooting into CWM, and running "adb logcat > logcat.txt" doesn't work when CWM is booted.

What I did so far:

• Copied the original G300 kernel modules back in.
  
• Stripped the LG system image considerably. unpacked it's about 420Mb in size, which could well be too large. The original Huawei system image is about 268Mb. Current size is about 270Mb

I would welcome any ideas on how to debug the bootloop

Edited by omegamoon, 11 May 2012 - 02:11 PM.

[tilal6991]

No!! Please don't tell me they went and put the kernel as 2GVMSPLIT.

Could you get me the config inside /proc/config.gz?

[omegamoon]

tilal6991, on 11 May 2012 - 02:22 PM, said:

No!! Please don't tell me they went and put the kernel as 2GVMSPLIT.

Could you get me the config inside /proc/config.gz?

Sure, it can be found here

[tilal6991]

Right. Then I have a feeling that it's the LG which is compiled 2GVMSPLIT. So it's unlikely it'll run on the G300 without the kernel source.

[hecatae]

tilal6991, on 11 May 2012 - 02:44 PM, said:

Right. Then I have a feeling that it's the LG which is compiled 2GVMSPLIT. So it's unlikely it'll run on the G300 without the kernel source.

it's got a 128mb vmheap

[omegamoon]

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'lge/u0_open_eu/u0:4.0.3/IML74K/lgp700-V10a.20120417.233414:user/release-keys'
pid: 786, tid: 786  >>> zygote <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadd00d
 r0 00000000  r1 00000000  r2 400e723c  r3 00000000
 r4 deadd00d  r5 40ab0f58  r6 00006e10  r7 0001c548
 r8 00000000  r9 be90e410  10 00000000  fp 40aabfbc
 ip 40aac098  sp be90e160  lr 40a4c493  pc 40a4c492  cpsr 60000030
 d0  74726f6261204d56  d1  72616a2e6b6f6f68
 d2  6d65747379732f3a  d3  6f77656d6172662f
 d4  69767265732f6b72  d5  3a72616a2e736563
 d6  2f6d65747379732f  d7  726f77656d617266
 d8  0000000000000000  d9  0000000000000000
 d10 0000000000000000  d11 0000000000000000
 d12 0000000000000000  d13 0000000000000000
 d14 0000000000000000  d15 0000000000000000
 d16 6a2d65726f632f6b  d17 72616a2e74696e75
 d18 6d65747379732f3a  d19 6f77656d6172662f
 d20 69766e63712f6b72  d21 72616a2e736d6574
 d22 6d65747379732f3a  d23 6f77656d6172662f
 d24 0000000000000000  d25 0000000000000000
 d26 0000000000000000  d27 0000000000000000
 d28 0000000000000000  d29 0000000000000000
 d30 0000000000000000  d31 0000000000000000
 scr 00000010

		 #00  pc 00051492  /system/lib/libdvm.so (dvmAbort)
		 #01  pc 00075ece  /system/lib/libdvm.so (_Z15dvmClassStartupv)
		 #02  pc 0005314e  /system/lib/libdvm.so (_Z10dvmStartupiPKPKcbP7_JNIEnv)
		 #03  pc 00054a5e  /system/lib/libdvm.so (JNI_CreateJavaVM)
		 #04  pc 00046ba2  /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime7startVmEPP7_JavaVMPP7_JNIEnv)
		 #05  pc 00046f5e  /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime5startEPKcS2_)
		 #06  pc 00008f0a  /system/bin/app_process
		 #07  pc 00016778  /system/lib/libc.so (__libc_init)

 

[Frankish]

Has this hit a brick wall then?

[FrankieADZ]

Frankish, on 11 May 2012 - 11:16 PM, said:

Has this hit a brick wall then?

looks like it could until Huawei release the surce kernal...going by what Til said

[tilal6991]

The dalvik machine is crashing which makes it likely that either the kernel or something deep in Android is not working.