Jump to content

CM9 for Lg Optimus L3 (E400)


Guest tony_secreto

Recommended Posts

Guest Manoel Conde

Package complete: /home/hecatae/cm9/out/target/product/e400/cm-9-20121118-UNOFFICIAL-e400.zip

0642f62343cc27999d3e1bde7aab7b3e cm-9-20121118-UNOFFICIAL-e400.zip

http://www.multiupload.nl/5FF2NTTQQ5

the camera guy is giving force closure

but otherwise it is a good rom

I was wondering how to fix up the unlock screen that is bigger?

I know that the file you have to modify is in the framework-res

but which file within it?

Link to comment
Share on other sites

Guest hecatae

What is the difference between this and the official rom?

all fixes up to 18th included

the camera guy is giving force closure

but otherwise it is a good rom

I was wondering how to fix up the unlock screen that is bigger?

I know that the file you have to modify is in the framework-res

but which file within it?

yeah some how i got broken camera, the unlock screen is down to e400.mk

$(call inherit-product, $(SRC_TARGET_DIR)/product/languages_full.mk)

# The gps config appropriate for this device
$(call inherit-product, device/common/gps/gps_us_supl.mk)

$(call inherit-product-if-exists, vendor/lge/e400/e400-vendor.mk)

DEVICE_PACKAGE_OVERLAYS += device/lge/e400/overlay

PRODUCT_TAGS += dalvik.gc.type-precise
PRODUCT_PROPERTY_OVERRIDES += \
dalvik.vm.heapstartsize=5m \
dalvik.vm.heapgrowthlimit=32m \
dalvik.vm.heapsize=76m

PRODUCT_AAPT_CONFIG := normal mdpi ldpi
PRODUCT_AAPT_PREF_CONFIG := ldpi

PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/init.e0.rc:root/init.e0.rc \
$(LOCAL_PATH)/ueventd.e0.rc:root/ueventd.e0.rc \
$(LOCAL_PATH)/init.e0.usb.rc:root/init.e0.usb.rc

PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/configs/7k_handset.kl:system/usr/keylayout/7k_handset.kl \
$(LOCAL_PATH)/configs/e0_keypad.kl:system/usr/keylayout/e0_keypad.kl \
$(LOCAL_PATH)/configs/touch_mcs8000.idc:system/usr/idc/touch_mcs8000.idc \
$(LOCAL_PATH)/configs/touch_mcs8000.kl:system/usr/keylayout/touch_mcs8000.idc \
$(LOCAL_PATH)/configs/vold.fstab:system/etc/vold.fstab \
$(LOCAL_PATH)/configs/AudioFilter.csv:system/etc/AudioFilter.csv


PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/configs/media_profiles.xml:system/etc/media_profiles.xml

$(call inherit-product, build/target/product/full.mk)

# Permission files
PRODUCT_COPY_FILES += \
frameworks/base/data/etc/handheld_core_hardware.xml:system/etc/permissions/handheld_core_hardware.xml \
frameworks/base/data/etc/android.hardware.camera.flash-autofocus.xml:system/etc/permissions/android.hardware.camera.flash-autofocus.xml \
frameworks/base/data/etc/android.hardware.camera.front.xml:system/etc/permissions/android.hardware.camera.front.xml \
frameworks/base/data/etc/android.hardware.telephony.gsm.xml:system/etc/permissions/android.hardware.telephony.gsm.xml \
frameworks/base/data/etc/android.hardware.location.gps.xml:system/etc/permissions/android.hardware.location.gps.xml \
frameworks/base/data/etc/android.hardware.wifi.xml:system/etc/permissions/android.hardware.wifi.xml \
frameworks/base/data/etc/android.hardware.sensor.proximity.xml:system/etc/permissions/android.hardware.sensor.proximity.xml \
frameworks/base/data/etc/android.hardware.sensor.light.xml:system/etc/permissions/android.hardware.sensor.light.xml \
frameworks/base/data/etc/android.hardware.sensor.gyroscope.xml:system/etc/permissions/android.hardware.sensor.gyroscope.xml \
frameworks/base/data/etc/android.hardware.sensor.compass.xml:system/etc/permissions/android.hardware.sensor.compass.xml \
frameworks/base/data/etc/android.software.sip.voip.xml:system/etc/permissions/android.software.sip.voip.xml \
frameworks/base/data/etc/android.hardware.touchscreen.multitouch.jazzhand.xml:system/etc/permissions/android.hardware.touchscreen.multitouch.jazzhand.xml

PRODUCT_PACKAGES += \
hwprops

# Wifi
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/configs/wpa_supplicant.conf:system/etc/wifi/wpa_supplicant.conf \
$(LOCAL_PATH)/prebuilt/wlan.ko:system/lib/modules/wlan.ko

# BT
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/prebuilt/init.qcom.bt.sh:system/etc/init.qcom.bt.sh

# HW HALS
PRODUCT_PACKAGES += \
libgenlock \
liboverlay \
gralloc.msm7x27a \
hwcomposer.msm7x27a \
copybit.msm7x27a \
camera.e400 \
gps.e400 \
audio.a2dp.default \
audio.primary.msm7x27a \
audio_policy.msm7x27a \
charger \
charger_res_images

# OMX
PRODUCT_PACKAGES += \
libstagefrighthw \
libmm-omxcore \
libOmxCore

PRODUCT_BUILD_PROP_OVERRIDES += BUILD_UTC_DATE=0
PRODUCT_NAME := full_e400
PRODUCT_DEVICE := e400
PRODUCT_MODEL := LG-E400
PRODUCT_MANUFACTURER := LGE[/code]

Link to comment
Share on other sites

Guest chelseartb

you are on the Stock T-Mobile UK rom?

UNITED KINGDOM

428 O2U/O2(UNITED KINGDOM)	V10C	LGE400	157.15 MiB		

429 ORU/ORANGE UK(UNITED KINGDOM)	V10D	LGE400	185.01 MiB		

430 O2U/O2(UNITED KINGDOM)	V10D	LGE400	157.14 MiB		

431 GBR/UNITED KINGDOM	V10E	LGE400	154.62 MiB		

432 GBR/UNITED KINGDOM	V10F	LGE400	154.61 MiB		

433 TMU/T-MOBILE(UNITED KINGDOM)	V10G	LGE400	158.56 MiB		

434 O2U/O2(UNITED KINGDOM)	V10G	LGE400	160.58 MiB		

435 ORU/ORANGE UK(UNITED KINGDOM)	V10G	LGE400	185 MiB		

436 GBR/UNITED KINGDOM	V10I	LGE400	160.32 MiB		

437 O2U/O2(UNITED KINGDOM)	V10I	LGE400	160.68 MiB		

438 GBR/UNITED KINGDOM	V10K	LGE400	160.39 MiB		

439 TMU/T-MOBILE(UNITED KINGDOM)	V10K	LGE400	161.21 MiB		

440 ORU/ORANGE UK(UNITED KINGDOM)	V10K	LGE400	184.82 MiB		

441 ORU/ORANGE UK(UNITED KINGDOM)	V10M	LGE400	184.88 MiB		

442 TMU/T-MOBILE(UNITED KINGDOM)	V10M	LGE400	160.84 MiB		

443 TMU/T-MOBILE(UNITED KINGDOM)	V10N	LGE400	160.18 MiB

list above is from the stock roms thread http://www.modaco.co...400-stock-roms/

I'm running 438 United Kingdom V10K, did you OTA (Over the air) update to V10N?

Yes i updated to V10N OTA, would that affect my cm9 in some way?

Link to comment
Share on other sites

Guest hecatae

Yes i updated to V10N OTA, would that affect my cm9 in some way?

Yes you have some how updated the baseband and made it incompatible with CM9, may be down to RIL (Radio Interface Layer), seems I have some testing to do.

Link to comment
Share on other sites

@hecatae i has got a question for you.

Why i need install drivers to use the USB? With gingerbread no, and my windows can´t install it

PD: Good luck with your work n_n

Link to comment
Share on other sites

Guest chelseartb

Yes you have some how updated the baseband and made it incompatible with CM9, may be down to RIL (Radio Interface Layer), seems I have some testing to do.

In the meantime, is there some way i could downgrade the baseband? For example reflashing V10K on KDZ for tmobile UK? I really enjoyed the ICS experience and would love to go back to tht again even though there are some small bugs.

Link to comment
Share on other sites

In the meantime, is there some way i could downgrade the baseband? For example reflashing V10K on KDZ for tmobile UK? I really enjoyed the ICS experience and would love to go back to tht again even though there are some small bugs.

First wipe on recovery mode, next flash with emergency mode without start CM9 n_n

Link to comment
Share on other sites

Guest chelseartb

First wipe on recovery mode, next flash with emergency mode without start CM9 n_n

im sorry wat do i do after i flash on emergency more? do i flash v10k and then root and rom manager and flash cm9?

Link to comment
Share on other sites

im sorry wat do i do after i flash on emergency more? do i flash v10k and then root and rom manager and flash cm9?

CM9 don´t flash, install of the recovery mode after makes de 2 WIPEs

Link to comment
Share on other sites

Guest chelseartb

CM9 don´t flash, install of the recovery mode after makes de 2 WIPEs

So i i root my current V10N

install ROM manager

transfer CM9 to my SD card

install via recovery menu

wipe all data and dalvik cache

wipe all data and dalvik cache again?

And this would downgrade my baseband version?

Link to comment
Share on other sites

So i i root my current V10N

install ROM manager

transfer CM9 to my SD card

install via recovery menu

wipe all data and dalvik cache

wipe all data and dalvik cache again?

And this would downgrade my baseband version?

No xD

When you put CM9 on the SD go to Recovery Mode

1- wipe data/factory reset

2-wipe cache partition

3-install zip from sd card

4-choose zip from sd card

5-And then select your CM9.zip

Y you finish this and can boot in CM9 reply me on this post n_n

Or you can ad me to Google Talk xDD

Link to comment
Share on other sites

Guest sparhawk76

I am trying to get this to work on my e400r, originally running firmware V11E. I have installed it but when it boots up it appears to have no access to the wireless networks. Also, when I look in the about phone it says the baseband version is unknown. I am guessing that my phone has too new a baseband for this build of CM, and that is why I am having problems.

Is there any known way to downgrade the baseband on e400 series phones?

Link to comment
Share on other sites

Guest jomkingal

So i i root my current V10N

install ROM manager

transfer CM9 to my SD card

install via recovery menu

wipe all data and dalvik cache

wipe all data and dalvik cache again?

And this would downgrade my baseband version?

YOu could downgrade your baseband version with kdz flasher. just find the stock rom with the version you want then flash it with kdz flasher. then root then install cm9. :)

Link to comment
Share on other sites

Guest chelseartb

YOu could downgrade your baseband version with kdz flasher. just find the stock rom with the version you want then flash it with kdz flasher. then root then install cm9. :)

I could try tht but i wud also like to say tht my contacts menu is unable to import any contacts or data from the sim card and it says the phone number is unknown in the settings menu.... this was all on the last cm9 nightly of october. I will be able to use kdz flasher in 2 weeks' time from now to see if i can downgrade the baseband.

Link to comment
Share on other sites

Guest chelseartb

I am trying to get this to work on my e400r, originally running firmware V11E. I have installed it but when it boots up it appears to have no access to the wireless networks. Also, when I look in the about phone it says the baseband version is unknown. I am guessing that my phone has too new a baseband for this build of CM, and that is why I am having problems.

Is there any known way to downgrade the baseband on e400 series phones?

What network are you on and what country?

Link to comment
Share on other sites

Guest jomkingal

I could try tht but i wud also like to say tht my contacts menu is unable to import any contacts or data from the sim card and it says the phone number is unknown in the settings menu.... this was all on the last cm9 nightly of october. I will be able to use kdz flasher in 2 weeks' time from now to see if i can downgrade the baseband.

i use google backup for contact backups. :3

Link to comment
Share on other sites

Guest hecatae

Overclocking for CM9/Miui rom is here:http://www.androidworld.it/forum/lg-optimus-l3-259/%5Bkernel%5Doverclocked-1ghz-newgovernor-miuiv4icsmixed-77817/

i tried it and battery on boot bug is fixed, plus 1ghz overclock :) read more there..

interesting attached config if anyone wants to see the difference

main changes:


CONFIG_MSM_CPU_FREQ_SET_MIN_MAX=y
CONFIG_MSM_CPU_FREQ_MAX=800000
CONFIG_MSM_CPU_FREQ_MIN=245000
CONFIG_CPU_FREQ_GOV_LAZY=y
CONFIG_CPU_FREQ_GOV_LIONHEART=y
CONFIG_CPU_FREQ_GOV_LAGFREE=y
CONFIG_CPU_FREQ_GOV_SCARY=y
# CONFIG_CPU_FREQ_GOV_BRAZILIANWAX is not set
CONFIG_CPU_FREQ_GOV_MINMAX=y
CONFIG_CPU_FREQ_GOV_INTERACTIVEX=y
CONFIG_CPU_FREQ_GOV_SAVAGEDZEN=y
# CONFIG_CPU_FREQ_GOV_SMOOTHASS is not set
CONFIG_CPU_FREQ_GOV_SMARTASS2=y
CONFIG_CPU_FREQ_MIN_TICKS=10
CONFIG_CPU_FREQ_SAMPLING_LATENCY_MULTIPLIER=1000[/code]

Link to comment
Share on other sites

Guest irberserk

Other governors are configured but i prefered not compile them and add only smartassv2.Maybe in the next release i will insert them.Main changes are in acpulock-7201.c

Edited by irberserk
Link to comment
Share on other sites

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.