[ROM][4.4.4][Version 1]Android-L Themed Omega ROM (Screenshots updated)

xdema

Senior Member
Jul 5, 2014
100
52
0
I think bluetooth did work on earlier Omnis, do not know when it quit. As I said, on previous betas and also on beta9, I can toggle bluetooth, pair with the headset, but not receive or do calls from it.

Might check for differences, but why would CM's be any different? Never know. First betas lacked GPS and adding (really restoring) a few files fixed that (one of the reasons remove the format system from the updater-script!).
on omega 7 i'm quite sure it was ok to transfer file, not sure for a2dp
 
  • Like
Reactions: xu3sno and rharshit

Dovidhalevi

Senior Member
Jun 26, 2012
2,729
1,171
0
Sorry for my bad english. I do not understand.
I use super_trim.zip. I do not add anything to the system partition.
At first I did not encounter such problems. After using beta 9 a few days and the problem starting happen.
I still have the icon, still have plenty space on system. The quick update gesture( right/down from bar), however, is no longer working.
 

rharshit

Senior Member
Jul 17, 2012
700
1,113
0
Mumbai
Sorry for my bad english. I do not understand.
I use super_trim.zip. I do not add anything to the system partition.
At first I did not encounter such problems. After using beta 9 a few days and the problem starting happen.
Just see if you have enough space in /system partition. Se if its in Megabytes and not Kilobytes
I still have the icon, still have plenty space on system. The quick update gesture( right/down from bar), however, is no longer working.
That works for me, though. Did you enable it from settings?
Or wait, are you telling about swipe in notification bar?
 

Dovidhalevi

Senior Member
Jun 26, 2012
2,729
1,171
0
L-flavored apps working just fine on this ROM:

Play and Play Services. Had problems with side-loaded Play from the thread, but the versions auto-updated by Google are working without a hitch.

Calendar. Remove older version first, whether from the ROM or from Play, then side-load version from the thread. New material interface, event view. Other views accessible from the upper-right menu and elsewhere. Caveat: Much larger than previous versions--must install as user app on our device.

Messenger. No new functionality, but with material UI. Hint: Make it the default message handler. LIke this one? The mms from the ROM can be removed. Hangouts2 is another alternative, of course.

GMail5. Official (but leaked) apk installs normally (user App) and runs out of the box. Will handle non-gmail accounts as well. Material interface. Version on thread from preview image was laggy. This one is fine. I have been happily using K-9 for a couple of years, but may go over the gmail5 since it can handle all my accounts, nicer interface.

What won't work: Keyboard, Camera -- depend on prebuilt armv7 libs--old news. Dialer and contacts -- depend on newer API.
Boo-hiss: Microsoft has a lovely lockscreen and OneNote app, but these come with prebuilt armv7 libs.
 
  • Like
Reactions: rharshit and xu3sno

Dovidhalevi

Senior Member
Jun 26, 2012
2,729
1,171
0
Maps 9 apk is around. It includes a armv7 lib. So the illusion that it is "compatible with device" can be laid to rest. I have not been able to use any version after 6!
 

xdema

Senior Member
Jul 5, 2014
100
52
0
Google maps, whether armv6 or armv7, always lagged in p500. So either way it wasn't usable.

P.S the screenshot is from an armv7 device
in the past versions of maps there was a problem with the hw renderings settings, if it was enabled there was flicker in maps render (settings-performance menu-hardware renderings settings- disable hw render for maps).
the last that i've used was maps v. 7.7.0 (september)
are you talking about that?
 
  • Like
Reactions: xu3sno

Dovidhalevi

Senior Member
Jun 26, 2012
2,729
1,171
0
in the past versions of maps there was a problem with the hw renderings settings, if it was enabled there was flicker in maps render (settings-performance menu-hardware renderings settings- disable hw render for maps).
the last that i've used was maps v. 7.7.0 (september)
are you talking about that?
This might be worth a try! (Where do I find this app checklist for this ROM. Performance settings has stuff like CPU speed, governers, memory, dalvik setttings for fine-tuning.)

The app would eventually force a reboot, however.
 
Last edited:

rharshit

Senior Member
Jul 17, 2012
700
1,113
0
Mumbai
This might be worth a try! (Where do I find this app checklist for this ROM. Performance settings has stuff like CPU speed, governers, memory, dalvik setttings for fine-tuning.)

The app would eventually force a reboot, however.
Tap on build no 7 timed. Then go back to settings main activity. And there it is with development settings
 

Dovidhalevi

Senior Member
Jun 26, 2012
2,729
1,171
0
I too didn't get anything for he acc.
Googled about it?
On CM, there is a small system app HwaSettings.apk. It is run from the settings, a line entry in one of the places mentioned (have not run CM in ages so do not remember). The app from a CM ROM is inconsistent with our ROM.

Our settings say "force hw acceleration." I would assume its status as false would have no effect on apps not requesting hw acceleration and true would make ALL apps use it. Does Maps want it?
 

ibub

Senior Member
Oct 22, 2012
1,730
1,522
0
Louisville,Ky
I too didn't get anything for he acc.
Googled about it?
HWA.apk is available on XDA. Maps is a long story, but I'll try to make it brief. The original problem with maps was not a flicker, but the inability to render labels of street names, etc, which looked like pieces of white tape on the screen. The cause I found was this commit to hephappy's cm-9:
https://github.com/GenetICS/frameworks_base/commit/7bd1c41e4fc842623e3d9096040b0ea1a34dd3ce
This continued through cm-10.2 at androidarmv6, not included in cm-11.
But Google "fixed" it, sort of. After call for 32bit format failed, maps would call for 16bit to display. Hence flicker, and lag. But that was a cm problem, and should not be present here.

Sent from my LG-P509 using Tapatalk 2
 

xdema

Senior Member
Jul 5, 2014
100
52
0
On CM, there is a small system app HwaSettings.apk. It is run from the settings, a line entry in one of the places mentioned (have not run CM in ages so do not remember). The app from a CM ROM is inconsistent with our ROM.

Our settings say "force hw acceleration." I would assume its status as false would have no effect on apps not requesting hw acceleration and true would make ALL apps use it. Does Maps want it?
yes, the sys app is that, and came from CM, sorry.
edit
tested on os2sd, the v7.7.0
it's ok if i leave hw acc in hwa settings, else the map become black.
if i enable "force rendering gpu" or enable "disable overlay hw" in dev options then there are flickering/glitch in maps
i test it tomorrow on omni
 
Last edited:
  • Like
Reactions: rharshit