DeathArrow

Members
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

6 Neutral

About DeathArrow

  • Rank
    Newbie

Previous Fields

  • Your Current Device(s)
    LG E400
  1. Yes. Buy a new phone.
  2. I've built CM 10.1 and tried to boot it with this kernel but I haven't had any luck so far. Tried different command line parameters for kernel, rebuilding ramdisk, messing with the kernel but still can't boot. Probably the boards differ too much. I don't have jtag or UART board to see why it doesn't boot. He just merged e610 source provided by lg with p700 source also provided by lg. It's simple, really. At the time of the release of L3, the only difference between L5, L7 and L3 was that L5 and L7 had more ram and a bigger screen at a much higher price. To justify the price difference, L3 has to have an "old" Android version while L5 and L7 has to have a "newer" Android version. Now they release L3 II and the only difference with L3 is that L3 II has more ram. So to show potential buyers that L3 II is "better" and they have to upgrade, LG overclocked the kernel to 1000Mhz and release L3 II with Gingerbread.
  3. Different boards. You have to rewrite all LG junk in arch/arm/mach-msm/lge.
  4. Thanks for uploads. Just to let you update where we are .Generally speaking, I'm a busy man. I'm studying for Ph D, I'm doing things for money, got this as a side project since no one wants to do it.So bear with me, I'm sorry but I will develop this kernel/rom on a slow pace since I do not have much spare time. What I did: I've compiled CM 10.2 with the old kernel.I got kernel 3.4 to play from Code Aurora, got it in GIT, maybe I should upload. It's hard to port the kernel to our very device. It's even harder since L3 is now my only phone. I've missed calls trying to boot custom kernels.Anyway, since I don't have very much time, I will upload my modifications to a complete 10.2 os and I will upload the kernel I'm working on. Maybe some guys could help.LG code sucks, their proprietary hacks sucks big time!
  5. Alright, I'm quite inexperienced when it comes to porting Android, but I'm a programmer and I've already developed software under Linux, so I'm going to try and port kernel 3.0+ and CM 10.1 or JB 4.2 to our device. CM 10.1 is almost building, I have to iron out some errors but I think I'll get it to compile correctly in a few days. However we have no 3.0+ kernel. And JB with 2.6 kernel doesn't seem too attractive to me. I'm trying also to port a 3.0+ kernel to our device, and that is the most hard thing to do. You can't diff stock 2.6 kernel and patch against 3+ kernel because 3.0 and 2.6 kernels are quite different things. Heck, you can't even use the lge patches against a 2.6 kernel because LG made quite ugly source modifications and hacks after hacks. So my goals are: a.) build CM 10.1/JB against 2.6 kernel, to have something to test against b.) port some 3.0+ kernel to our device For a.) I think it's an easy job. For b.) it's quite hard. I have three ideas to follow: 1.) use kernel 3.0 from LG L5 / lge 610 2.) use kernel from CAF and add drivers and patches 3.) use regular android kernel 3.0+ from nexus devices and add drivers and patches I've tried 1.), but the boards are quite different, I was able to boot the kernel but got kernel panics. I've looked to the source and the code for lge 610 is quite different from the code for e400, board is different and lge modifications of source code sucks big time. If I am ever to decide to hire a former LG coder, I would not. They just fu...cked the kernel source lots of if defs and custom bulshiting with the android kernel 3.) is last idea I will try it if 2.) isn't suitable for some reasom 2.) is our best bet to have a modern, new kernel for our device and have JB 4.2 CM 10.1 shine. Code Aurora already has most of Qualcomm drivers in the source tree, I have just to add different drivers for some devices (lots of) not made by Qualcomm. So I'm trying to pursuit number 2.) I will probably set up a github for compiling CM 10.1, when I will build it successfully, mainly /device/lge/e400 and /vendor/lge/e400 and modified build scripts. However this will be only to build a test CM 10.1 to have something to test against. I will set up a github for kernel development, I will start from Code Aurora Forums 3.4 kernel. How you can help: I need/we need (if some other devs join in) more info about the hardware. I have lge400 service manual but not all devices are mentioned. I've already made a list but it's not complete. a.) you are not a developer: if you have stock image and you are rooted, type these in terminal: #dmesg > /mnt/sdcard/dmesg.txt put somewhere dmesg.txt and give the link in the thread if you are not rooted, install ADB, and type: adb shell dmesg > /mnt/sdcard/dmesg.txt exit adb pull /mnt/sdcard/dmesg.txt whatever directory Upload dmesg.txt to some filesharing and put the link in this thread. b.) if you are a developer, you can help by identify devices based on dmesg and logcat. If you are a developer and want to help, download 3.4 kernel from Code Aurora. Try to compile it and add drivers. I will set up github for kernel and CM 10.1.
  6. Set a static IP for that particular network. It should work.
  7. Maybe you need to set a static IP for the network you are trying to connect. Have you tried to connect in different locations/to different networks?
  8. You have a different display, that's why you are having problems. People with blurred screens have E400G, E400R, etc. not regular E400.
  9. Lol, it seems like the kernel it's 2.6 instead of 3.0. So CM team did a half assed job and instead of porting the kernel to E400, they just used stock kernel.
  10. Nice! Anybody did any benchmarks with kernel overclocked to 1000Mhz on stock firmware? Because on CM9 when I test with Antutu I get around 4800 without overclocking and 4100-4400 with overclocking and performance governor. Cpu test gets more points but GPU seems to get way less points in Antutu. In Nenamark2 and Basemark ES 2.0 I also get less fps. Probably a sync problem between CPU speed and RAM speed.
  11. Those roms are useless. Just stock rom with themes changed, launcher changed and some apps removed and other apps added. Those roms don't add new functionality and won't work better than any stock rom.

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.