20 Jan Gr6 (V20o): MoDaCo Custom ROM for the LG Optimus 2X with Online Kitchen (stock+vanilla)

[Guest Flix123]

Went from BB 622 Fr19 to BB 0725 and your new Gr5 with stock kernel (no MCK).

- No issues whatsoever, have to see how long battery lasts yet. With my personal tweaks (too many to count), Fr19 lasts ~3 days on one charge. I've even gone 4 days with data/WiFi/BT disabled. Will report back.

- I'm not seeing any of the issues mentioned here.

- I replaced all of the vanilla Google apps in the ROM with my own 2.3.7_r1 build.

- Camera works fine, even zoom while recording FullHD video.

If anyone's interested, I patched Camera.apk again with the following changes:

- 1080p video (h.264): 24 -> 30 FPS

- 1080p audio bitrate (AAC): 64 kbps -> 128 kbps

- 1080p super fine bitrate: 9528 kbps -> 19056 kbps (even @ 25Mbps was smooth, but no visible quality bonus)

- 1080p fine bitrate: 7038 kbps -> 9528 kbps

- 1080p normal bitrate: 5130 kbps (no change)

- 720p video (h.264): 30 FSP (no change)

- 720p audio bitrate (AAC): 64 kbps -> 128 kbps

- 720P super fine bitrate: 4096 kbps -> 8192 kbps

- 720P fine bitrate: 3072 kbps -> 4096 kbps

- 720P normal bitrate: 2048 kbps (no change)

- Quicktime 3GPP container (*.3gp) changed to ISO MP4 (*.mp4) for all video files

Other resolutions are left on original settings, those seem appropriate. Above numbers were chosen based on visual feedback testing and best perceived quality of the recordings. The lowest (NORMAL) settings is left the same (for people with small SD's, etc), while every next step basically doubles the bitrate. Much better scale/range than stock LG presets. If you have tips for other values, let me know.

Audio bitrate boost has a very noticeable impact on audio quality.

Switch from proprietary crap 3GP to standard ISO MP4 is purely a matter of my preference - no quality/size advantage.

APK is not signed with Paul's platform keys, obviously, so it first needs to be uninstalled, then pushed in. To keep LG Home / Launcher app. menu icon position and "system" status, replace the APK using ADB in recovery mode, then boot.

All of the Camera mods are tested and working perfectly. I modded the previous versions of LG Camera a week after I purchased the phone, so it has about 7 months of testing.

Camera.apk [1.5M]: http://oron.com/jne75xl4evwa

Cheers! Great ROM.

PS: As a senior enterprise UNIX specialist I can tell you that going to all this trouble just for EXT4 is arguable, at best. EXT2/3 has the same real-world performance on this HW (or better, in most cases) and is much easier on the block wear of the FLASH memory. Without special settings and tuning for MTD, EXT4 is doing more harm than good. Just a friendly advice.

Wow, great! Could you disable the sound when capturing video, too?

[Guest SuperSkill]

Went from BB 622 Fr19 to BB 0725 and your new Gr5 with stock kernel (no MCK).

- No issues whatsoever, have to see how long battery lasts yet. With my personal tweaks (too many to count), Fr19 lasts ~3 days on one charge. I've even gone 4 days with data/WiFi/BT disabled. Will report back.

- I'm not seeing any of the issues mentioned here.

- I replaced all of the vanilla Google apps in the ROM with my own 2.3.7_r1 build.

- Camera works fine, even zoom while recording FullHD video.

If anyone's interested, I patched Camera.apk again with the following changes:

- 1080p video (h.264): 24 -> 30 FPS

- 1080p audio bitrate (AAC): 64 kbps -> 128 kbps

- 1080p super fine bitrate: 9528 kbps -> 19056 kbps (even @ 25Mbps was smooth, but no visible quality bonus)

- 1080p fine bitrate: 7038 kbps -> 9528 kbps

- 1080p normal bitrate: 5130 kbps (no change)

- 720p video (h.264): 30 FSP (no change)

- 720p audio bitrate (AAC): 64 kbps -> 128 kbps

- 720P super fine bitrate: 4096 kbps -> 8192 kbps

- 720P fine bitrate: 3072 kbps -> 4096 kbps

- 720P normal bitrate: 2048 kbps (no change)

- Quicktime 3GPP container (*.3gp) changed to ISO MP4 (*.mp4) for all video files

Other resolutions are left on original settings, those seem appropriate. Above numbers were chosen based on visual feedback testing and best perceived quality of the recordings. The lowest (NORMAL) settings is left the same (for people with small SD's, etc), while every next step basically doubles the bitrate. Much better scale/range than stock LG presets. If you have tips for other values, let me know.

Audio bitrate boost has a very noticeable impact on audio quality.

Switch from proprietary crap 3GP to standard ISO MP4 is purely a matter of my preference - no quality/size advantage.

APK is not signed with Paul's platform keys, obviously, so it first needs to be uninstalled, then pushed in. To keep LG Home / Launcher app. menu icon position and "system" status, replace the APK using ADB in recovery mode, then boot.

All of the Camera mods are tested and working perfectly. I modded the previous versions of LG Camera a week after I purchased the phone, so it has about 7 months of testing.

Camera.apk [1.5M]: http://oron.com/jne75xl4evwa

Cheers! Great ROM.

PS: As a senior enterprise UNIX specialist I can tell you that going to all this trouble just for EXT4 is arguable, at best. EXT2/3 has the same real-world performance on this HW (or better, in most cases) and is much easier on the block wear of the FLASH memory. Without special settings and tuning for MTD, EXT4 is doing more harm than good. Just a friendly advice.

Hi :rolleyes:

This seems like a real goodie. Is it usable on both Fr19, Gr4 and Gr5?

Other Roms? It would probable be apreciated if you could upload(and leave a link) your own tweaked rom making all of able to test it.

Don`t be afraid to ask for donations, all of us who uses custom software/roms for our phones should donate to all of you that`s able to make our phones better than de manufacturers.

Thanks in advance.

SuperSkill B)

[Guest orlroc]

Maniacdave could u make a zip to flash with the 2.3.7 apps for us????

Thx a lot

orlroc

Edited November 23, 2011 by orlroc

[Guest caffeine666]

Went from BB 622 Fr19 to BB 0725 and your new Gr5 with stock kernel (no MCK).

- No issues whatsoever, have to see how long battery lasts yet. With my personal tweaks (too many to count), Fr19 lasts ~3 days on one charge. I've even gone 4 days with data/WiFi/BT disabled. Will report back.

- I'm not seeing any of the issues mentioned here.

- I replaced all of the vanilla Google apps in the ROM with my own 2.3.7_r1 build.

- Camera works fine, even zoom while recording FullHD video.

If anyone's interested, I patched Camera.apk again with the following changes:

- 1080p video (h.264): 24 -> 30 FPS

- 1080p audio bitrate (AAC): 64 kbps -> 128 kbps

- 1080p super fine bitrate: 9528 kbps -> 19056 kbps (even @ 25Mbps was smooth, but no visible quality bonus)

- 1080p fine bitrate: 7038 kbps -> 9528 kbps

- 1080p normal bitrate: 5130 kbps (no change)

- 720p video (h.264): 30 FSP (no change)

- 720p audio bitrate (AAC): 64 kbps -> 128 kbps

- 720P super fine bitrate: 4096 kbps -> 8192 kbps

- 720P fine bitrate: 3072 kbps -> 4096 kbps

- 720P normal bitrate: 2048 kbps (no change)

- Quicktime 3GPP container (*.3gp) changed to ISO MP4 (*.mp4) for all video files

Other resolutions are left on original settings, those seem appropriate. Above numbers were chosen based on visual feedback testing and best perceived quality of the recordings. The lowest (NORMAL) settings is left the same (for people with small SD's, etc), while every next step basically doubles the bitrate. Much better scale/range than stock LG presets. If you have tips for other values, let me know.

Audio bitrate boost has a very noticeable impact on audio quality.

Switch from proprietary crap 3GP to standard ISO MP4 is purely a matter of my preference - no quality/size advantage.

APK is not signed with Paul's platform keys, obviously, so it first needs to be uninstalled, then pushed in. To keep LG Home / Launcher app. menu icon position and "system" status, replace the APK using ADB in recovery mode, then boot.

All of the Camera mods are tested and working perfectly. I modded the previous versions of LG Camera a week after I purchased the phone, so it has about 7 months of testing.

Camera.apk [1.5M]: http://oron.com/jne75xl4evwa

Cheers! Great ROM.

PS: As a senior enterprise UNIX specialist I can tell you that going to all this trouble just for EXT4 is arguable, at best. EXT2/3 has the same real-world performance on this HW (or better, in most cases) and is much easier on the block wear of the FLASH memory. Without special settings and tuning for MTD, EXT4 is doing more harm than good. Just a friendly advice.

just a pair of question :P can you patch also pics compression, making them bigger but better?

can you make a more "equilibrated" version?

something like

SF 17mbps

F 13mbps

N 10 mbps

for example i find 19mbps and 9mbps a too wide rage, huge and good quality, and smaller but also a lot worse detail....

i suggest (made this suggest also to developer of first camera patch on xda) making 3 different patches

19-15-10 (full HQ for huge sdcards 32/64) 720p (11-9-7) (obviously if 11 has a better quality on 9, if not it can be the same as the middle 720p profile)

16-13-8 hq for big (16/32) sdcards (9 - 6 - 4)

14 -10 -5 for small sdcards (<8/16) (9 - 4 - 2)

i think i would use the middle one, for example ;)

also cause, usually, if a video doesn't need top quality, and having a good file size, usually i prefer to record in 720p ;)

this assuming that patching files, for you that already know how to do it, takes few minutes... if it takes so long, no problems ;)

just suggesting, cause i really respect you ;) don't know why so many cooks, and not a so important patch before yours ;)

[Guest RedeemerSK]

If you have a working ADB and e.g. CWM recovery, it's super-easy.

1) Power off, PowerOn button + VolDown button until recovery appears

2) Choose "mounts" in the top-level menu

3) Choose "mount /system"

4) Connect phone via USB to your PC and issue this ADB command:

adb push C:\path\to\my\Camera.apk /system/app/

5) Choose "umount /system"

6) Choose "reboot"

I do it this way.

1. Copy apk to the phone via MSC (phone as mass storage device)
2. adb remount
3. adb shell
4. cp /sdcard/PATH_TO_YOUR_FILE /system/app

Feel free to switch 1) for adb push

[Guest sangriaman]

I did it using root explorer. Deleted camera.apk in system. Pasted the new camera.apk. And rebooted.

[Guest Involver]

First of all, thanks Paul and everybody involved in Modaco developpement !

I recently installed a cooked Gr5 version but as far as I am, i noticed 2 "bugs" or strange behaviour ... :

- home button doesn't do anything except "vibrating". I tried what Paul suggested a few post ago, but it didn't solve anything (I didn't cooked with LG Launcher, only stock one, and I'm using LauncherPro)

- Camera shows pictures, but doesn't save them ... The button doesn't do anything :(

Any help would be appreciated, even if it's just a "wait for Gr6" :)

Thanks.

Martin.

Hi Martin,

I had the exact same issue and you reaaly should try running the setup wizard completely. I did a full wipe then reboot and start the wizard,complete the wizard and the buttons started working again..

Good luck!

[Guest maniacdave]

Wow, great! Could you disable the sound when capturing video, too?

Photo mode shutter sound can be disabled via settings menu. Video start/stop doesn't have any sound...

Plenty of stuff can also be changed in /data/data/com.android.camera/shared_prefs/arc_camera_prefs.xml -- without APK patching.

[Guest HAL_9000]

What about GPS? Does it work properly on Gr5?

[Guest Ximo F. Verde]

Photo mode shutter sound can be disabled via settings menu. Video start/stop doesn't have any sound...

Plenty of stuff can also be changed in /data/data/com.android.camera/shared_prefs/arc_camera_prefs.xml -- without APK patching.

Tried the mod, installation via root explorer went fine, but unfortunately i get lots of dropped frames @ 1080p, video is not fluid at all. Any suggestions?

Thanx

[Guest okdac]

Dave speaking...

So far, no problem with gps on Gr5. but maybe it depends on kernel and radio...

I'm using r26, ext3 ril 725 and everything is fine.

Okdac

What about GPS? Does it work properly on Gr5?

[Guest HAL_9000]

Dave speaking...

Thanks Dave. This mission is too important for me to allow you to jeopardize it. :D

So than I will upgrade on Gr5 Vanilla.B)

[Guest maniacdave]

Tried the mod, installation via root explorer went fine, but unfortunately i get lots of dropped frames @ 1080p, video is not fluid at all. Any suggestions?

Thanx

Just try a different kernel, nothing else could screw the performance so badly. Mine is just as smooth and stable as Fr19.

I found a first problem myself. Charged the phone before going to bed. Played some mp3's while in bed, then stand-by. In the morning, battery was at 77%.

Not a good performance. Lost 20% just overnight doing nothing, suspended.

I pick it up and go to work. Here, I touch it and it's completely overheating! Battery says 70%. I attach ADB to check which process is causing the gratuitous heavy CPU load. Before "top" finishes, the phone self-reboots (via com.lge.poweroff)! Battery now says 20%.

Something screws the ROM badly - system parts are all stock LG. I'm gonna have to watch it now and analyze what's going on next time it starts heating up.

Battery reporting is waaay off too, basically useless for estimating remaining charge.

I don't like this. Another half-assed release. WTF, LG?!

[Guest Tsaglis]

Just try a different kernel, nothing else could screw the performance so badly. Mine is just as smooth and stable as Fr19.

I found a first problem myself. Charged the phone before going to bed. Played some mp3's while in bed, then stand-by. In the morning, battery was at 77%.

Not a good performance. Lost 20% just overnight doing nothing, suspended.

I pick it up and go to work. Here, I touch it and it's completely overheating! Battery says 70%. I attach ADB to check which process is causing the gratuitous heavy CPU load. Before "top" finishes, the phone self-reboots (via com.lge.poweroff)! Battery now says 20%.

Something screws the ROM badly - system parts are all stock LG. I'm gonna have to watch it now and analyze what's going on next time it starts heating up.

Battery reporting is waaay off too, basically useless for estimating remaining charge.

I don't like this. Another half-assed release. WTF, LG?!

I had exactly the same issues. It was with completely stock (only rooted) 2.3.4, with GR5 + Stock kernel and only once with GR5+r26 (this one after charging).

BB and Ril the ones with V20L.

See my post here

Edited November 24, 2011 by Tsaglis

[Guest maniacdave]

I had exactly the same issues. It was with completely stock (only rooted) 2.3.4, with GR5 + Stock kernel and only once with GR5+r26 (this one after charging).

BB and Ril the ones with V20L.

See my post here

It happened again, just now. Take it to call, it's hot, battery 55%, so I attach ADB to see what's going on and 5 secs later, I see com.lge.poweroff starting and phone shuts down.

After restart, battery down to 1%.

The reboot is definitely triggered by me attaching the USB cable and/or opening ADB session -- both times it was happily running mad hot, with enough battery remaining, but as soon as I plug it in, it shuts down. I repeat - it's a controlled shutdown, app-initiated. In fact, it's a Java app that's doing it. Seems like an intentional logic. I don't believe it's overheat protection, because the phone was warm for a long time and shut down only after (and as soon as) I attached ADB.

What's weird is that there are no CPU-runaway processes at the time. The only is "system_server" at around 20% CPU. That's not much. It looks to me like something related to Tegra chips. Last time the biggest CPU eater at the time of shutdown was "nvrm_daemon". Either way, CPU usage was negligible, so the source of drainage and heat dissipation must be something else.

There's not much we can do about this. It's a problem in the platform libs and binaries. Especially the proprietary nVidia stuff. Next time I'll concentrate on logcat. I feel like I'll have many opportunities to debug this in the 5 sec window.

FUUUUUUUUUUUUUUUU!!!!!!!!

Edited November 24, 2011 by maniacdave

[Guest Diskbox]

maniacdave, have you got a file/copy of the changes you used to get FR19 up to 3 days? If so I've be very interested in a copy as I'm often away for long periods and need a phone to last as long as possible.

(I tend to flip/flop between longest lasting 2x rom and bleeding edge when I'm at home)

Diskbox

Went from BB 622 Fr19 to BB 0725 and your new Gr5 with stock kernel (no MCK).

- No issues whatsoever, have to see how long battery lasts yet. With my personal tweaks (too many to count), Fr19 lasts ~3 days on one charge. I've even gone 4 days with data/WiFi/BT disabled. Will report back.

- I'm not seeing any of the issues mentioned here.

- I replaced all of the vanilla Google apps in the ROM with my own 2.3.7_r1 build.

- Camera works fine, even zoom while recording FullHD video.

If anyone's interested, I patched Camera.apk again with the following changes:

- 1080p video (h.264): 24 -> 30 FPS

- 1080p audio bitrate (AAC): 64 kbps -> 128 kbps

- 1080p super fine bitrate: 9528 kbps -> 19056 kbps (even @ 25Mbps was smooth, but no visible quality bonus)

- 1080p fine bitrate: 7038 kbps -> 9528 kbps

- 1080p normal bitrate: 5130 kbps (no change)

- 720p video (h.264): 30 FSP (no change)

- 720p audio bitrate (AAC): 64 kbps -> 128 kbps

- 720P super fine bitrate: 4096 kbps -> 8192 kbps

- 720P fine bitrate: 3072 kbps -> 4096 kbps

- 720P normal bitrate: 2048 kbps (no change)

- Quicktime 3GPP container (*.3gp) changed to ISO MP4 (*.mp4) for all video files

Other resolutions are left on original settings, those seem appropriate. Above numbers were chosen based on visual feedback testing and best perceived quality of the recordings. The lowest (NORMAL) settings is left the same (for people with small SD's, etc), while every next step basically doubles the bitrate. Much better scale/range than stock LG presets. If you have tips for other values, let me know.

Audio bitrate boost has a very noticeable impact on audio quality.

Switch from proprietary crap 3GP to standard ISO MP4 is purely a matter of my preference - no quality/size advantage.

APK is not signed with Paul's platform keys, obviously, so it first needs to be uninstalled, then pushed in. To keep LG Home / Launcher app. menu icon position and "system" status, replace the APK using ADB in recovery mode, then boot.

All of the Camera mods are tested and working perfectly. I modded the previous versions of LG Camera a week after I purchased the phone, so it has about 7 months of testing.

Camera.apk [1.5M]: http://oron.com/jne75xl4evwa

Cheers! Great ROM.

PS: As a senior enterprise UNIX specialist I can tell you that going to all this trouble just for EXT4 is arguable, at best. EXT2/3 has the same real-world performance on this HW (or better, in most cases) and is much easier on the block wear of the FLASH memory. Without special settings and tuning for MTD, EXT4 is doing more harm than good. Just a friendly advice.

[Guest Mr.HTML]

After installing this i am not able to do a factory reset nor from the OS or the Recovery Menu.

I'm getting an Cannot mount /data! error in Recevery

How to solve this?

[Guest maniacdave]

First off: Was charging whole night. Data completely off since the last heatup/reboot yesterday. 2G network mode only. No heat up or reboots since then. Yesterday I had data ON and 3G. Heating & associated battery issues could be caused by the radio. Too soon to say.

Battery is OK, actually very good, but probably because of another issue that appeared today instead: since sometime in the morning until about noon, the phone lost network connection. I found out an hour ago. Dark gray sig. mon. with little red "X". As if you disable GSM. I tried Airplane ON/OFF, but phone still not getting reception. Had to force switch from GSM to WCDMA to re-connect and then switch back. Now I have normal, full reception again.

But for a couple of hours, the phone was offline without any warning. Had to force GSM connect/disconnect to get it back. Now, two hours later (4hrs after charging, ~2-3 of which w/o GSM) there's still 99% of battery left. If that's accurate, then we could get good running times when the issues are resolved.

Both issues seem to be pointing to the radio. Could be one issue, really.

[Guest c.joenie]

I updated to GR5(and updated radio to recommended radio) (from FR19 again :)) and it seems that Dungeon Defenders is not running that well on this rom...

[Guest maniacdave]

Thanks Dave. This mission is too important for me to allow you to jeopardize it. :D

So than I will upgrade on Gr5 Vanilla.B)

Open the pod bay door, HAL!!

[Guest Tsaglis]

First off: Was charging whole night. Data completely off since the last heatup/reboot yesterday. 2G network mode only. No heat up or reboots since then. Yesterday I had data ON and 3G. Heating & associated battery issues could be caused by the radio. Too soon to say.

Battery is OK, actually very good, but probably because of another issue that appeared today instead: since sometime in the morning until about noon, the phone lost network connection. I found out an hour ago. Dark gray sig. mon. with little red "X". As if you disable GSM. I tried Airplane ON/OFF, but phone still not getting reception. Had to force switch from GSM to WCDMA to re-connect and then switch back. Now I have normal, full reception again.

But for a couple of hours, the phone was offline without any warning. Had to force GSM connect/disconnect to get it back. Now, two hours later (4hrs after charging, ~2-3 of which w/o GSM) there's still 99% of battery left. If that's accurate, then we could get good running times when the issues are resolved.

Both issues seem to be pointing to the radio. Could be one issue, really.

I have everything on, data, GPS, WiFi, BT except 3G. I also bought a new battery (genuine ~9Euros from S.Korea) and with its first charge with minimal use, only as ~15 min of calls, 3-4 sms and ~20 min browsing, it lasted 50H until it went to 10%, when I plug it again. It had at least other 6-7 hours left according to battery monitor predictions. Not bad. If the battery becomes better after 2-3 cycles then it will be perfect!

The whole time with out any problems whatsoever.

Edited November 25, 2011 by Tsaglis

[Guest maniacdave]

I have everything on, data, GPS, WiFi, BT except 3G. I also bought a new battery (genuine ~9Euros from S.Korea) and with its first charge with minimal use, only as ~15 min of calls, 3-4 sms and ~20 min browsing, it lasted 50H until it went to 10%, when I plug it again. It had at least other 6-7 hours left according to battery monitor predictions. Not bad. If the battery becomes better after 2-3 cycles then it will be perfect!

The whole time with out any problems whatsoever.

That's bogus, man. Just active data (actual transfers) will kill your battery in 24h. If you also had WiFi, BT, GPS and made several calls, then you're either mystifying or had it plugged in a USB frequently or it was asleep the whole time. :) Having these "ON" doesn't mean they're active, you know -- if you had the phone in sleep mode for the duration of 50h and just called 3 times, then what you say is quite expected, because those chips weren't actually fully powered. I mean come on, just browsing the web with Flash and lots of images via 3G will drain your whole battery in well under 6 hours. With the phone LCD ON to make actual use of WiFi + BT + GSM and data, you're looking at couple of hours battery life. Not 50. Seriously.

This release is definitely very buggy, many people sharing the same issues or subsets of issues. It's probably not a MCR issue, rather crap in the original LG SW. Strange is that different groups of people share different bugs, not everybody reports everything. It could be network and HW-revision dependent. I'm gonna try the stock LG ROM just to eliminate possible MCR influence, but I doubt it will help.

I went almost a day after installing this ROM without any issues. Then bam! Two deal-breakers in 16 hours. The phone was hotter while asleep than with any intensive computation I had running ever. Full charge gone in 2 hours. That never happened with 2.2 ROMs.

[Guest Tsaglis]

That's bogus, man. Just active data (actual transfers) will kill your battery in 24h. If you also had WiFi, BT, GPS and made several calls, then you're either mystifying or had it plugged in a USB frequently or it was asleep the whole time. :) Having these "ON" doesn't mean they're active, you know -- if you had the phone in sleep mode for the duration of 50h and just called 3 times, then what you say is quite expected, because those chips weren't actually fully powered. I mean come on, just browsing the web with Flash and lots of images via 3G will drain your whole battery in well under 6 hours. With the phone LCD ON to make actual use of WiFi + BT + GSM and data, you're looking at couple of hours battery life. Not 50. Seriously.

This release is definitely very buggy, many people sharing the same issues or subsets of issues. It's probably not a MCR issue, rather crap in the original LG SW. Strange is that different groups of people share different bugs, not everybody reports everything. It could be network and HW-revision dependent. I'm gonna try the stock LG ROM just to eliminate possible MCR influence, but I doubt it will help.

I went almost a day after installing this ROM without any issues. Then bam! Two deal-breakers in 16 hours. The phone was hotter while asleep than with any intensive computation I had running ever. Full charge gone in 2 hours. That never happened with 2.2 ROMs.

When I say all are on, I don't mean active, I mean the switches were on. Most of the time the device was sleeping (And I was working or also sleeping!)

I wanted to point out that by switching something on or off, when you don't actualy use it. (ie the GPS), it does not consume any power.

I had the same problem with stock rom+kernel. So probably it is a LG to blame.

An other issue is memory leak, after several hours, my device becomes laggy. The memory, after killing all aps with a task manager, remains ~100MB free. After a restart it is significantly higher.

So I do a restart every second day the latest. (I have a lot of crap running and several widgets in my screens)

[Guest IzzyStradlin]

Hi guys! Have you tried other kernels with GR5, like Neoblaze or HP? If so, what is the most recommended? Thanks!

[Guest stegg]

hi, I'm using GR5 core+stock, all's OK except I don't like the LG lockscreen. so I searched and tried to set in build.prop

user.feature.lock_andy=false

user.feature.lock_sui=true

but it's not working, the LG lockscreen is still there... anyone can confirm? any other way?

Edited November 27, 2011 by stegg