Jump to content

Well check this out developers


Recommended Posts

Guest hecatae
Posted

yes Chingizzka.

here's hoping it's the same screen tech, camera tech, sensor tech, etc etc.

do you know what the internal model number is?

e400 is e0

I'm hoping this is the e1

sratch that:

1. Android buid
- Download original android source code ( Jelly Bean 4.1 ) from http://source.android.com
- Unzip opensource packages of E435F(Optimus L3II)_Android_JB_E435f10a_BR.zip into downloaded android source directory
- And, merge the source into the android source code(Jelly Bean)
- Run following scripts to build android
a) source build/envsetup.sh
B) choosecombo
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain)
into the android folder
( add prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin to PATH )
- After build, you can find output at out/target/product/generic

2. Kernel Build
- Unzip using following command at the android folder
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain)
into the android folder.
- cd kernel
- export ARCH=arm
- export TARGET_PRODUCT=vee3ds_open_br
- export CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
- make vee3ds-rev_11_defconfig
- make zImage

3. After Build, You Can find the build image at arch/arm/boot[/code]

melfas touchscreen yes

bmm050 sensor tick

hi351 camera yes

radio tavarua yes

ebi2 yes

FB_MSM_EBI2_TOVIS_QVGA lcd panel yes

looks compatible, and it's a 3.4.0 kernel

can someone grab the rom

Posted (edited)

downloaded the rom, extracted .kdz to .dz but unable to open .dz with dzdecrypt :( says "invalid markers in main header"

Edited by andwie
Guest Chingizzka
Posted

I hope you guys can port this) You guys fixed our blurred screen problem)

Guest hecatae
Posted

downloaded the rom, extracted .kdz to .dz but unable to open .dz with dzdecrypt :( says "invalid markers in main header"

I hope you guys can port this) You guys fixed our blurred screen problem)

port, cant we just use the kernel source for cm10?

Guest Chingizzka
Posted

port, cant we just use the kernel source for cm10?

ehm... :P. Well a stable rom on JB >-<

  • 2 weeks later...
Guest hecatae
Posted

anyone seen a L3 II yet?

scratch that, new source available

Guest nikufellow
Posted

So how's the porting going. Doesn't l3 2 have a mrdiatek chipset could that be a problem?

Guest hecatae
Posted

So how's the porting going. Doesn't l3 2 have a mrdiatek chipset could that be a problem?

L3 II has a msm7225a qualcomm chipset overclovked to 1000mhz

Guest SaDneSS
Posted (edited)

L3 II has a msm7225a qualcomm chipset overclovked to 1000mhz

it's cool))so,what about porting?)

Edited by SaDneSS
Guest nikufellow
Posted

I know roms can be ported from other devices but does the same hold for kernels if so what would it take to recompile l3 ii kernel to boot in ours I mean what changes? Or is it enough to back port bits to existing cm9 kernel?

Guest hecatae
Posted

I know roms can be ported from other devices but does the same hold for kernels if so what would it take to recompile l3 ii kernel to boot in ours I mean what changes? Or is it enough to back port bits to existing cm9 kernel?

from what I have seen, the 3.4 kernel should work on our e400, all bits present and correct, just got to build from scratch and test repeatedly

Guest Ygreck
Posted

okay, if i understand you right... and the e430 is exactly like the e400 (only if we take a look to the kernel), did we really need to compile it as a port for the e400 or can we take the kernel set in e430 firmware and put it stupidly to our device?

Guest ajeeshvijayan
Posted

i wish cyanogen team to port/compile kernel from e430 and include on e400 in next nightly.. just hoping ..can we contact them and notice them about this possibility?

Guest ajeeshvijayan
Posted

e430 have ips display, 512mb ram... will that be a problem?

Guest Ygreck
Posted

@hecatae is in the e430 firmware a FM-Radio?

can we take this?

Guest hecatae
Posted

@hecatae is in the e430 firmware a FM-Radio?

can we take this?

see this, same components in e430 and e400:

melfas touchscreen yes

bmm050 sensor tick

hi351 camera yes

radio tavarua yes

ebi2 yes

FB_MSM_EBI2_TOVIS_QVGA lcd panel yes

which is why I asked someone to pull the kdz apart earlier

  • 3 weeks later...
Guest nikufellow
Posted (edited)

Sorry for unnecessary posts - opera problem

Edited by nikufellow

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.