[UPDATE-3][ROM][4.2] KitKat for Optimus One

rharshit · Nov 6, 2013

KitKat for Optimus One P500!
I am not kidding. KitKat is optimized for devices with 512mb of RAM.

But wait! This is not Android 4.4. This is Android 4.2.2 (CM10.1.5 with HALO))) ) with KitKat experience!
Almost like KitKat.

Features:

Android 4.4 KitKat experience
CM10.1.5 with HALO)))
KitKat Play Store
KitKat Play Services
KitKat Home (trimmed)
KitKat Google Now (trimmed)
etc, etc...

Whats Working:

Everything in CM10.1.5
HALO)))
Google apps
Everything else

Bugs:

WiFi Battery drain (kernel 3+ problem)
Google Now sometimes force closes on search
Google Now Voice Search gives FC (will be fixed soon )
PlatLogo gives a FC. Will be fixed in next update.
All ARMv7 features (Gesture typing in stock keyboard, Voice recognition, PhotoSphere, etc..

Screenhots:

Tips:

To enable Google now in home screen, go to home, settings and turn on Google Now
To get better UI and UX, change the density from 160 to 145.
To see Android version as 4.4 in About phone, change the Android version in build.prop to 4.4.
To get better Ui and UX with updated Android version, do both the steps.

*To get back original values, revert the changes.

Downloads:

Base ROM

Google Drive

Installation:

Download the Zip and place it in your SD card
Reboot into recovery
Wipe everything (Not necessary for CM10.1.5 or 10.1.6 but recommended)
Then flash the zip in your SD card
After it is completed, reboot it (First boot can take a bit of time, as long as 10 mins. So have patience)
Enjoy!

rharshit · Nov 6, 2013

Updates, Changelogs and Patches

Updates:
Don't need to flash the whole ROM again. Just flash the latest Update though recovery.

Update 1
Update 2
Update 3
(Some users have reported a bootloop after installing this update. Be sure to make a nandroid backup before installing this update.)
EDIT: Refer this.

Changelog:

Update 1
- Added gradient statusbar
- Added gradient Navigation Bar
- Partially ported KitKat Platform Logo
Update 2
- Fixed Platform Logo issue (Used to Force Close)
Update 3
- Added KitKat clock
- Changed some visuals
- Added many tweaks and scripts for smoother and lag-free experiance
- build.prop tweaks for performance and quality
  (NOTE: Density and android version will revert back to orignal.)

Coming up next:

~~KitKat gradient Statusbar~~(In Update 1)
Google Now fix
KitKat camera (trimmed)

Sent from a device running KitKat

carmeloseven · Nov 6, 2013

This phone still under developement

why not 10.1.6 of CM?

rharshit · Nov 6, 2013

carmeloseven said:
This phone still under developement why not 10.1.6 of CM?

CM 10.1.6 is already out. Check this.
But it doesn't have HALO))). So i chose CM10.1.5

itouchables · Nov 6, 2013

A working google now...soo downloading this

sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed

itouchables · Nov 7, 2013

itouchables said:
A working google now...soo downloading this

sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed

lags alot and google now doesn't really work........but thanks for trying man:good::good::good:

rharshit · Nov 7, 2013

itouchables said:
lags alot and google now doesn't really work........but thanks for trying man:good::good::good:

It lags in the start. But stable afterwards. And for Google now, what isnt working?

Dovidhalevi · Nov 7, 2013

rhar**** said:
It lags in the start. But stable afterwards. And for Google now, what isnt working?

Downloading this to see what you did! How do you intend to "fix" GoogleSearch?

I have Velvet installed on my cm-10.2 (user app). It would FC almost immediately using the libgoogle_recognizer_jni_1.so from the thread. This is closed-source armv7 stuff so sort of cuts us out.

EDITED POST: What I thought was happening was simply wrong: Not the 4.4 Velvet. With what I did have, the following still valid:

That armv7 precompiled close source stuff kills us (if Google is to support "older" devices, it needs to make armv6 precompiled jni's available or make it all open source so we can do them!). However, when I was experimenting with my current configuration, somehow, Google Search's speech input came up. "Initializing en-US." (I have that srec but NOT symlinked in), and then ... it took my voice and used it. Just once, but it did do it! Not an illusion. So maybe this can be fixed up.

EDIT: Conspicous by it absense is the "PrebuiltGMSCore." I did install that, user upgrade to my previous gmscore. Needed by Play and the thread claims that its "prebuilt" version is required by Google Now.

Kfire21 · Nov 8, 2013

Ext2 partition with cronmod causes boot loop, but nice integration of Google now

nvm. my partitions were messed up

Maurice5813 · Nov 8, 2013

Google Search FC Fix

Hey heres how to fix google search forces closes! Long press the home screen, select Settings. Select Voice. Select Language to change the default. Change to another language, I choose English – UK. Hit Home. Do a Google Search. Repeat the first three steps. Change back to English – US.

Enjoy

Dovidhalevi · Nov 8, 2013

arDroid.99 said:
Hey heres how to fix google search forces closes! Long press the home screen, select Settings. Select Voice. Select Language to change the default. Change to another language, I choose English – UK. Hit Home. Do a Google Search. Repeat the first three steps. Change back to English – US.

Enjoy

This has been bandied about on the thread, sometimes successful, sometimes not.

In our case, I doubt you will see any benefit. I tried it. First off, there is no offline recognition currently working on our device. No off-line options in settings (if one can get that far), no language kits, nothing.

At our stage, Google Search FC trying to initialize/access off-line voice recognition which is armv7 compiled. Bingo. Edit: The Rashed's old modded version apparently neutralized that call. Clicking mic would, of course, FC.

rharshit · Nov 8, 2013

Dovidhalevi said:
Downloading this to see what you did! How do you intend to "fix" GoogleSearch?

I have Velvet installed on my cm-10.2 (user app). It would FC almost immediately using the libgoogle_recognizer_jni_1.so from the thread. This is closed-source armv7 stuff so sort of cuts us out. However ... brainstorm: Extracted the jni from Rashed's Jan 7 GoogleNow.apk and lo and behold, it starts up, one can do searches, access cards, etc. I can get online voice recognition into it using the voice search assistant widget shortcut and I have that using overlays covering Google Search's mic icons (which are guaranteed FC). Not the most fluid but the thing works.

With the thread's JNI, launcher worked, Google Search FC in a loop. WIth Rashed's, launcher does not find Google Search (which really is the launcher--GoogleHome is a stub and maybe the wallpapers).
With the thread's JNI, I could get to settings->voice if I did it quick enough (before the FC). Offline options not shown. With Rashed's jni, setting->voice FC immediately.

The voice recognition did work for me a few times. I dont know how, but it did. Unfortunately, the FC.
Fortunately, I was able to get a screenshot before the FC popup.
See this

And this

Dovidhalevi said:
That armv7 precompiled close source stuff kills us (if Google is to support "older" devices, it needs to make armv6 precompiled jni's available or make it all open source so we can do them!). However, when I was experimenting with my current configuration, somehow, Google Search's speech input came up. "Initializing en-US." (I have that srec but NOT symlinked in), and then ... it took my voice and used it. Just once, but it did do it! Not an illusion. So maybe this can be fixed up.

This is the same reason why I think this can be fixed!

Helbelinc · Nov 8, 2013

Different thing: I installed it but can't get over the initial settings because the Android keyboard gets FC all the time. Just a corrupt download?

I tried to edit the rom via the Oone editor and install the keyboard i normally use as user app but that won'T help me get over the damn initial settings

Is there actually a way to set a different keyboard than the AOSP as default?

Edit: Found the solution 3 seconds after posting -.- I didn't have the German pack in the LatinME installed, but chosen in the initial settings. That made it crash.

However the question how to set an alternative keyboard as default still interests me, though it might be a little OT

rharshit · Nov 8, 2013

Helbelinc said:
Different thing: I installed it but can't get over the initial settings because the Android keyboard gets FC all the time. Just a corrupt download?

I tried to edit the rom via the Oone editor and install the keyboard i normally use as user app but that won'T help me get over the damn initial settings
Is there actually a way to set a different keyboard than the AOSP as default?

Edit: Found the solution 3 seconds after posting -.- I didn't have the German pack in the LatinME installed, but chosen in the initial settings. That made it crash.

However the question how to set an alternative keyboard as default still interests me, though it might be a little OT

If you want to set alternative keyboard as default, you first have to install it in phone memory and not SD card.
Then i guess, that's it. Now select the keyboard and enjoy!
tell me if it still doesnt work

Helbelinc · Nov 8, 2013

rhar**** said:
If you want to set alternative keyboard as default, you first have to install it in phone memory and not SD card.
Then i guess, that's it. Now select the keyboard and enjoy!
tell me if it still doesnt work

That's not what I meant

I meant rather somehting like replacing the stock keyboard with an alternative (MessagEase in my case), so that it basically 'identifies' this as stock keyboard.

rharshit · Nov 8, 2013

Helbelinc said:
That's not what I meant I meant rather somehting like replacing the stock keyboard with an alternative (MessagEase in my case), so that it basically 'identifies' this as stock keyboard.

Just place the apk in /system/app/ and change permission to rw-r--r--
Or simply install the app and make it a system app through apps like Link2SD or /system/app mover

rishabh22 · Nov 8, 2013

Helbelinc said:
That's not what I meant I meant rather somehting like replacing the stock keyboard with an alternative (MessagEase in my case), so that it basically 'identifies' this as stock keyboard.

If you want to install a good keyboard like swiftkey you'll also have to copy the library file from data/data/appfolder/lib into sytem/lib besides the apk

marcomarinho · Nov 8, 2013

rhar**** said:
Coming up next:

KitKat gradient Statusbar

Google Now fix

KitKat camera (trimmed)

Sent from a device running KitKat

Congratulations bro. I like your ROM :highfive: This looks promissing ...
By the way don't inclue the KitKat gradient Statusbar, I already put, it's looks good on launcher & lockscreen but in all others apps it's confused. Just my opinion. Congratulations :good:

Regards,
Marco Marinho

borchaniz · Nov 9, 2013

You're awesome rhar**** I'll try it in few minutes!

Sent from my LG-P500 using xda app-developers app

rharshit · Nov 9, 2013

_MarcoMarinho_ said:
Congratulations bro. I like your ROM :highfive: This looks promissing ...
By the way don't inclue the KitKat gradient Statusbar, I already put, it's looks good on launcher & lockscreen but in all others apps it's confused. Just my opinion. Congratulations :good:

Regards,
Marco Marinho

Umm.. i have already included the statusbar and the navigation bar gradient. And yes, its a bit messy in some of the apps. I guess because of the Holo light theme. what if i edit the Holo light background to make it black in the statusbar area?

[UPDATE-3][ROM][4.2] KitKat for Optimus One

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Guest

Senior Member

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Inactive Recognized Developer

Senior Member

Senior Member

Similar threads

Top Liked Posts