yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] kldoc:
I actually have this "miscellaneous" battery drain showing up.

I know it doesn't act as a battery life extender, but many users base their appreciation of their battery life using battery stats. "If" that code can actually reflect more accurately battery usage, why not, that's why I'm testing it and didn't publish a build with it just yet. I myself tend to to never look at battery stats, and observe its life by myself. But everyone's usage and habits are different ;) This is an unofficial build anyway, and it's likely such commit might simply get rejected. Doesn't hurt to test :)
[Nexus 4 Original Android Development] kldoc:
I once again wasn't clear enough when I said it failed, thing is i have USB debugging on all the time because I work on some code port from 4.4 to 5.x. But what I meant, is I was expecting (maybe wrongly ?), that the name of the build in the about screen would switch to user, even with usb debugging enabled, and it didn't so my assumption (again maybe wrong), was that modifying the script the same way than the commit you showed me wasn't enough.
[Nexus 4 Original Android Development] sparksco:
I see. Well maybe it's better to have both options. You could build userdebug for yourself since I doubt most people will need a debug build for everyday usage to run logcats. Also note that people will have to turn off USB debugging constantly after a clean flash to avoid logging draining their battery, where user builds they won't [emoji3]

And if they dirty flash a user build while USB debugging is enabled it won't turn it off automatically.
[Nexus 4 Original Android Development] kldoc:
Ok, new build (05/05/2015), switched to user build, less battery drain due to less log spam.

Enjoy :)

[MENTION=2394329]sparksco[/MENTION], thank you for pointing this out :)

I switched to Slim gapps, and so far, looks good, I am currently having fc with inbox, not really sure why. Will investigate ;)
[Nexus 4 Original Android Development] Jokerli:
It seems that severall google apps have problems with the latest version. google keep and the gmail app also terminates with fc.
[Nexus 4 Original Android Development] kldoc:
That's why I switched to Slimgapps, which solved the problem.
[Nexus 4 Original Android Development] Jokerli:
This doesn't solve the problem, only the symptoms. All apps, that flashed with the package work fine, but if you install a google app from the play store, like google fit for example, the app will fc. I switched back to the version 20150404 and all the problems are gone. So it must be an issue in the latest rom version. If you need a log, it will be possible i think...

for Information, i use the normal package version of the slim gapps beta
[Nexus 4 Original Android Development] maheshjagadeesan:
Inbox opens momentarily, but won't stay open. Strangely enough, it's able to post notifications for new emails!
[Nexus 4 Original Android Development] kldoc:
I've noticed the same thing, still trying to figure out what's wrong.

I'm using the full version of slim gapps package, but what you're describing seems more like an issue with something else, will investigate on all changes (not that many) between those builds.

EDIT: I've found out one change, when I switched the build, I actually tested those changes on a different source tree (for testing purpose), and I forgot (sorry about that) to update the blobs along an currently unmerged commit (will get merged with next update from Google), I've got to make a full build, and will test it out to find out if those issues get solved or not. Rest assured I'm doing my best to solve those, Nexus 4 is my only device and my daily driver, so is OmniROM. Although my free time is limited, I really try to fix those ASAP and release a better working build.
[Nexus 4 Original Android Development] Jokerli:
Don't worry. I know that this rom is still beta and you do a great job... If you need logs or other things which helps to solve issues, i'll try to provide the information
[Nexus 4 Original Android Development] kldoc:
Thanks, for now it's not really needed, I encountered the same issues over the week end, but I did put that on the old pa gapps, I was using, that's why I tried the full sim gapps package, so aside inbox force closing, i have no other issues. Your posts made me think it might be something else, so checking out, never do anything in a hurry, never ends well :p
[Nexus 4 Original Android Development] kldoc:
Ok, regarding Inbox, can't seem to be able to fix it. It keeps force closing for now.

I did the test after a wipe data, which makes me think there's a bug on the app itself.

I will check on other apps.
[Nexus 4 Original Android Development] Jokerli:
Inbox works on 20150404 with no issues...
[Nexus 4 Original Android Development] maheshjagadeesan:
Yes, I remember it working on the previous one (20150326) too. I have a feeling it might be some sort of incompatibility with Play Services, but that's just a guess. I did manage to get Authenticator working by choosing Setup from the menu instead of clicking on the Begin Setup button. Weird!
[Nexus 4 Original Android Development] kldoc:
Only difference with today's build is preodex optimization. Gonna post the build .
[Nexus 4 Original Android Development] kldoc:
8/4/15 test build

https://drive.google.com/file/d/0B7SdORCtpN8bU1JvbWZZTTVXWk0/view?usp=sharing

Honestly , if preodex is needed , just doesn't make sense :(

Nothing else has changed. Gonna try out with that 4/4 build, since i have that same issue with Inbox, but I doubt i will fix Inbox FC
[Nexus 4 Original Android Development] Jokerli:
I will test it as soon as possible and report my observations...
[Nexus 4 Original Android Development] sparksco:
I had the same issue on hammerhead with preodex and google apps... But only on omni, other ROM sources like pa works OK with odex. So this only seems to be a issue with OmniRom and odex.
[Nexus 4 Original Android Development] manpildo:
Hi all,

Once all the main bugs have been ironed out, are there any plans on adding a few more features? For example customizable navigation ring targets, customizable quick settings and double-tap status bar to sleep? I hope it's being considered, otherwise a very nice ROM.
[Nexus 4 Original Android Development] Jokerli:
Still no luck with google apps from play store with version 20150408... I attached log
[Nexus 4 Original Android Development] kldoc:
Thing is I actually removed dex preoptimization, I reanabled it and am making a clean build, will then test inbox, and other apps. I've switched to the normal slim gapps to be in the same scenario than you. Hopefully it will work, although it is really odd lack of dex optimization triggers a certificate problem. Be sure that I won't let you down, since I also need it to work :)

EDIT:This build with dex pre optimization gives the same results, problem seems to be in a remaining Google Service Framework from an older gapps package, I just did a wipe data, and trying to use Banks gapps to have a real clean install. I'm using 8/4/2015 build.

EDIT:It seems at least one of the gapps package actually messed up with the local storage, I can't install PA gapps as is, it detects older gapps, means a complete full wipe is needed, and I don't have the time to test it today unfortunately.
[Nexus 4 Original Android Development] kldoc:
I tested Banks gapps on a full clean install (including internal data wipe), Google inbox force close for the same reason.

E/AndroidRuntime(10793): java.lang.SecurityException: Signature check failed for com.google.android.apps.inbox

I've reported that to core team. But I expect other devices to have that issue in the coming days.
[Nexus 4 Original Android Development] sparksco:
[MENTION=2604804]kldoc[/MENTION] I know you want to blame google apps packages but I already explained it's a ROM issue with odex on Omni [emoji13]

I guess you don't believe me when I say on other Roms that are also odex with the same google packages it works fine.

You don't need to format your sdcard storage or anything crazy to make it work...
[Nexus 4 Original Android Development] XpLoDWilD:
Care to explain how Odexing changes packages signature? Pre-dexopt'ing a ROM only pre-optimizes the system APKs (ie. skip the "Optimizing app xxx of xxx" at first boot). After that step, your system is in the same state, pre-dexopt'd or not. This has nothing to do with packages having a wrong signature, especially since it would happen on ALL devices not just a specific device with a specific Gapps package. I've been using 5.0 PA Gapps for months without any trouble.

Last time I had a signature error was when I used Nexus 6 leaked Gapps (L Gmail, etc), which had a Google Test signature, instead of the regular Google release signature.
[Nexus 4 Original Android Development] sparksco:
I was using OmniRom for months living with these bugs because they weren't that big of a deal to me. Eventually I got sick of the bugs and trying to figure out why it behaves this way so I decided to switch ROM sources and guess what? Every other ROM source I've tried so far (which is two others) works fine with any gapps. Can I explain why? Nope. So who knows, maybe on this ROM your forced to use specific gapps packages, but on other Roms your not... And if your forced to format your sdcard that would seem pretty ridiculous.
[Nexus 4 Original Android Development] XpLoDWilD:
I haven't seen anyone having issues with any GApps running Omni, but we're not forcing any specific package or anything. Try a full reset (ie. return to stock) of your device, but I never had that issue on hammerhead at least (and it's the first time I hear about such issues).
[Nexus 4 Original Android Development] sparksco:
I only build odex (user builds), not userdebug. My own Roms compiled from source. I think you missed the point of that conversation that they are testing user builds here. I have tried everything. Maybe you haven't tried user build yet and that's why you don't have the issues.
[Nexus 4 Original Android Development] sparksco:
[MENTION=2162789]XpLoDWilD[/MENTION] I still have omni source. If you want I'll sync up later and pm you a build if you want to try it. Also you said you haven't see anyone with these issues on hammerhead but I don't see any hammerhead threads for omni lollipop android 5.0 or android 5.1...

I've seen these bugs in both omni 5.0 and 5.1 with various gapps packages.

Edit: THIS thread is still on omni 4.4 so it didn't seem appropriate to discuss unofficial builds of omni 5.0 or 5.1... Would you rather I post a test build there for users to try or test yourself?
[Nexus 4 Original Android Development] kldoc:
Ok, problem solved, user build actually doesn't work well with gapps at the moment, I'll try to see what I can do about it, but for now, have to do with user-debug build. Uploading it.

EDIT: Build 09/04/2015 is up, it comes mostly to fix Google apps force closure, dex optimization isn't back yet. If you are flashing coming from a previous build, please wipe dalvik cache/cache. If you encounter any issue related to gapps, please, attach a logcat.

Thank you
[Nexus 4 Original Android Development] Jokerli:
no issues found so far, all apps work as expected
[Nexus 4 Original Android Development] adamshumpisxxx:
I'm having an issue. At night, I put on a podcast VIA Podkicker to listen to while I fall asleep. Ever since I installed OmniROM the podcast will play for about 15 minutes and then stop. When I go to look at my phone to see what the issue is it's in the process of rebooting. The screen is asleep during this because I press play, tap the power button and lay the phone face down on the bed. This has never happened before with any other ROM I have used on this device. What could be causing this? Has anyone else experienced this? Does anyone know how to fix it? Thank you.

EDIT:

I have some additional information. Two things.

1) The time it takes for the phone to crash and reboot is more like 5 minutes and not 15 minutes.

2) When I use the "Fullscreen carmode" function of Podkicker to keep the screen awake the phone does not crash and reboot.

The conclusion I have come to is that the phone crashes when Podkicker is playing while the screen is asleep. I'm not sure if this happens with all media programs as I have not yet synced my music library to my phone yet. I will do so tomorrow and report back. I will also try another podcast app to see if that makes a difference.

EDIT2:

I can't seem to let this go. Haha. I have an innate ability to troubleshoot and when problems like this arise in my line of work I can't drop it until I have it beat. Anyways, I have some additional information that is pretty interesting. The issue persists when I try another podcast app (Podcast Addict). When I download the podcast and play it with Apollo the issue persists as well. Pandora DOES NOT have this issue as far as I can recreate. My inkling is that it has something to do with the size / length of the individual audio files being streamed / played locally. Tomorrow I will sync my music library to Apollo. If I am correct, Apollo will not cause a crash and reboot due to the smaller size / length of my MP3 music files. So far I have narrowed the issue down to the screen being asleep. I will let you know what I come up with tomorrow.
[Nexus 4 Original Android Development] kldoc:
Need a logcat, without a logcat, will be hard to debug anything.
[Nexus 4 Original Android Development] magnet1215:
Finally. Google released 5.1 for mako.
[Nexus 4 Original Android Development] dhanmohan:
yeah :D
[Nexus 4 Original Android Development] kldoc:
Uploading a new build with updated blobs, hopefully, i forgot nothing and it should work just fine. Google Play Movie seems to remain broken (at least through my VPN), trying to find a solution, let me know if it works for you ;)

Don't forget to update your radio( fastboot flash radio radio.img).

EDIT:Uploaded, this build being experimental, I'll put it on main thread when I'm certain it runs fine.

https://drive.google.com/file/d/0B7SdORCtpN8bOTR3dnNfb0FFNFU/view?usp=sharing
[Nexus 4 Original Android Development] server3249:
Where are the customization features.. this rom hardly has anything.
[Nexus 4 Original Android Development] Dark Emotion:
wow
[Nexus 4 Original Android Development] criminalzen:
heh ....
[Nexus 4 Original Android Development] sparksco:
The features they do have they can call theirs I suppose? I'm not entirely sure but I think they spend to much time trying to support old hardware/devices and it's become too difficult for them in the newer platforms of android like lollipop. Now we have all these things like selinux and other things we didn't have in jellybean that makes their lives more difficult.
[Nexus 4 Original Android Development] kldoc:
That's one of the reason it's still in alpha status and not int beta/nightly status.

If you want to help, you're more than welcome :)

OmniSwitch isn't fully implemented on softkeys devices (i.e: Nexus devices) because the navbar customization hasn't been ported yet.

Ambiant Display is there, Notification and Alarm sound linking is there (expanded volume panel coming soon), notification lights customization (coming soon).
[Nexus 4 Original Android Development] iamloco:
Got FC on Youtube Timely gmail inbox etc

will try later didn't had time to wipe and/or grab logcat
[Nexus 4 Original Android Development] kldoc:
That's odd, I'm running the same build (15/4/2015), youtube, inbox, google plus, absolutely no issue.
[Nexus 4 Original Android Development] iamloco:
Which gapps?

I did installed Slim_full_gapps.BETA.5.1.x.build.0.x-20150406

As I said I'll will wipe and also update gapps when I have time.

Maybe tomorrow
[Nexus 4 Original Android Development] kldoc:
I'm on a newer gapps Slim_mini_gapps.BETA.5.1.x.build.0.x-20150416.zip , i've just added a flashable google now launcher to get it.

Although you might want to wait a little, maybe wait 2 or 3 days, kernel tree and blobs weren't merged yet on OmniROM's github, that's also why i didn't put the build in the main thread. Even though it runs fine for me. might be wise to wait to flash a complete build. I'll post one as soon as merging is done.
[Nexus 4 Original Android Development] hashtask:
Daily driver

I installed the ROM in the first post, over the 4.4.4 Omnirom a few days back. It was a clean install with Banks Gapps and the 5.1 modem. There were FC issues with Deskclock and I was not able to set Google Now launcher (from Play store) as the default launcher. I disabled Deskclock and enabled it again to make it work. To get Google Now working, I uninstalled it and installed the apk.

After that, all Google apps work fine. No issues with audio and video so far. I'm on the latest update posted by kldoc a couple of days back.

Can't wait for the omni features to be added. :good:
[Nexus 4 Original Android Development] kldoc:
Thank you for your feedback. I hope being able to release a newer build during the week end.

Install is less straightforward for me since I'm in a non supported country for Goole now launcher, but latest build seems to work better than before, exit the wake up lagg (really got scared on that one) and didn't have any reboot nor SOD since then.

I can assure you that I'm doing whatever I can to make nightlies for Nexus 4 a reality, but I want it to be a clean build, without any major issue. All I can say, we're closing in, but not here just yet on OmniROM features, a little more patience ;) I love this device just as much as you all do, it's also my only device (feels like a repetition here), and I'm dedicated 100% to my phone being available and working all the time.
[Nexus 4 Original Android Development] hashtask:
Take your time :) I'm glad someone took up the maintainer role and brought it to this stage. Thanks for the hard work.
[Nexus 4 Original Android Development] kldoc:
Ok, new build (18/04/2015). Update to Android 5.1 r5, blobs updates, kernel still not updated, probably by tomorrow. Google Play movie DRM issue fixed.
[Nexus 4 Original Android Development] kldoc:
Hello folks, I'm not forgetting you, I didn't do any newer build because there's no need at the moment. There's nothing changed ROM side, kernel sources hasn't been updated yet on Omni's side, should be soon, but core team is quite busy at the moment.

Nightlies are closing in for Nexus devices. Latest build I uploaded seems stable enough for me, if you encounter issues, please report those along with a logcat since an issue can't be debugged without.

It'll probably be a week or two before I make another build, not enough changes (if any) to justify an update. And luckily, next build I upload will be one of the last before nightlies.

Have fun with OmniROM :)
[Nexus 4 Original Android Development] kldoc:
Hello, I know i said there wouldn't be any update, but Google decided otherwise:

https://drive.google.com/file/d/0B7SdORCtpN8bcHZudlY4OVNyZVk/view?usp=sharing

First build with 5.1.1, I'm running it, but way to early to tell if any issue.
[Nexus 4 Original Android Development] iamloco:
should it work with custom kernel like the Franco one?
[Nexus 4 Original Android Development] kldoc:
OmniROM is AOSP based, if Franco kernel work on AOSP, it should work too.
[Nexus 4 Original Android Development] gorilla p:
Planning on checking out Lollipop OmniROM once the 5.1.1 is confirmed clear of major bugs.

For those who have used a recent version, is it pretty Vanilla, or a bit more customized?

Sent from my Nexus 4
[Nexus 4 Original Android Development] :
it is pretty vanilla and ultra stable. hope omnirom will be one of the top roms again. it was maybe the most stable and for me the #1 best rom ever until lollipop.

hope omnirom will regain lost time in the next weeks and overhaul roms like cyanogenmod or ressurrection remix again.
[Nexus 4 Original Android Development] kldoc:
New build (02/05/2015): Volume panel expandable and Battery styles added.

Enjoy :)
[Nexus 4 Original Android Development] morganmf:
Are the omni tweaks not included yet?
[Nexus 4 Original Android Development] kldoc:
Volume panel expandable, link/unlink notification/ringtone, Battery light, Ambiant Display, Battery styles, custom keys, etc ... All those are Omni's tweaks.
[Nexus 4 Original Android Development] morganmf:
So where are they? I flashed your build and could not find any of it.
[Nexus 4 Original Android Development] gorilla p:
Are you referring to an omni-tweaks section in settings or something like that?
[Nexus 4 Original Android Development] morganmf:
Yep
[Nexus 4 Original Android Development] gorilla p:
Yeah, the they're not those kind of tweaks, and idk if Omni has that yet on lollipop. Development has been extremely slow on Omni, possibly due to the amount of supported devices, but the lack of features has kept a lot of people from using it.

Its not the Omni you remember from KitKat.

To be fair, it seems like lollipop development has been slow in general for all ROMs. I know when there are big updates like Jb>Kk>Lp, a lot of things need to be re-written and unfortunately they can't just add the same features.
[Nexus 4 Original Android Development] morganmf:
So as I thought. This is why I flashed back to KitKat. Stable and reliable.
[Nexus 4 Original Android Development] kldoc:
Organisation of those features is different than what it was on 4.4, mostly because Android has evolved a lot between 4.4 and 5.x.

At the moment, not many features are actually missing if you compare those 2 versions, custom notification lights (in rework, since the whole notification system has be reworked by Google and features from 4.4 just won't work as is), lockscreen widgets ( it will not come back, as OmniROM stays 100% compatible with AOSP), Custom tiles ( I think I've seen someone starting some work on it).

But rest of the features are here actually, including OmniSwitch, the file manager is also back. but we merged those features within existing categories to keep something logical as much as we could.

First step is/was to bring back those features from the dead, and they indeed really were dead, I can't think of a single feature that didn't ask even a small part of rewrite.

UI is set to evolve, it's of course subject to change in the future according to users feedback, will and feasibility :)

I agree, there are so many changes in Lollipop, it's really huge actually, and thing is there were also changes withing Lollipop, 5.0 till 5.1.1, and that probably didn't help speeding up dev.
[Nexus 4 Original Android Development] kldoc:
KitKat is of course a reasonable choice as a daily driver. But I tend to personally push Lollipop as it really is smoother and it's actually really stable now. I have a way better battery life on 5.1.1 than on 5.1.

Now everyone's usage is different, but I'm curious about which feature you are missing from Lollipop, I can try to give it a look and see what can be done.
[Nexus 4 Original Android Development] kldoc:
[MENTION=2785344]morganmf[/MENTION]

Performance settings is actually there just before about phone section in Settings app
[Nexus 4 Original Android Development] greg17477:
Hi,

is the omni clock already in?

cheers
[Nexus 4 Original Android Development] kldoc:
You've got DeskClock that has been modified. Can't tell for now if DashClock will come back or not.
[Nexus 4 Original Android Development] gorilla p:
I've been using it for a couple days and I like what has been done with it so far. The only issue that I have personally that is a deal breaker (and it may not be a big deal for some) is lack of Privacy Guard. App Ops is installed, and it is very limited. It doesn't allow access to any system apps.

I have seen Privacy Guard work well on AOSP and CM based ROMs and it is significantly better than the AppOps that's installed in Omni at the moment.
[Nexus 4 Original Android Development] kldoc:
I know there's plan for something similar, that's all I can tell about it.
[Nexus 4 Original Android Development] morganmf:
So I am missing led notification settings, navbar height and ability to edit the navbar buttons order. I never mentioned performance settings as they don't bother me. Also status bar clock adjustment, generally speaking navbar tweaks, statusbar tweaks. Are they included already and I am just blind?