yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] kldoc:
You should check on Omnirom's dev irc channel, can't really help you on that particular error on One plus one, each device is very different ...
[Nexus 4 Original Android Development] black.ic3:
Already fixed :) But i am 90% sure this wont compile succefull, and if compiled, 99% wont boot.

So many errors and my stupid fixes...
[Nexus 4 Original Android Development] eagleeyetom:
Out of pure curiosity. What is the fix for this?
[Nexus 4 Original Android Development] black.ic3:
Sounds stupid, but i saw on chinese forum advice to use newer android_frameworks_native

Used android_frameworks_native from cm12.1 branch, added some files that caused errors from the original omni 5.1 branch

Builded, but it stucks on OnePlus logo and reboots

I dont know what causes this, mixing of this things, or anything else.

Maybe it's because there are no proprietaries for 5.1 on OPO yet
[Nexus 4 Original Android Development] kldoc:
Try not to use too many commits from CyanogenMOD if you're going to build OmniROM, they have a lot of code that isn't 100% compatible with AOSP, and that might indeed lead to some breakage either when building, either some force close. Cherry pick wisely :p
[Nexus 4 Original Android Development] kldoc:
Hello, I could use your help on testing some online streaming services, such as Hulu/Netflix/whatever, Google didn't publish 5.1 for Nexus 4 yet, and I live in China, with no possibilities of taking a tryout account on those. I know for sure that Google play movie is broken at the moment because of that (temporary until those blobs), but I don't know which other services are working or not.

If you encounter issues with those services, just mention the name of the service with a logcat attached to it.

I'll do my best to fix those ASAP.
[Nexus 4 Original Android Development] magnet1215:
Looking forward to official nightly Omnirom of Mako.:good::good::good:
[Nexus 4 Original Android Development] kldoc:
Not too much longer to wait, it will happen eventually, things are still getting polished, and on Nexus 4 side, I'm still waiting for Google to release those 5.1 blobs ...
[Nexus 4 Original Android Development] kldoc:
New build, 22/03/2015, OmniGears battery light customization, wake up keys, Ambiant display, etc ... Things are slowly getting together ;)
[Nexus 4 Original Android Development] ibanez89:
Tx for your work
[Nexus 4 Original Android Development] morganmf:
Hi kldoc, I have managed to setup compile environment and it did build without errors but after flashing it wont boot at all, it just stops on google splash screen.

I synced repo with 5.0.2 branch, done breakfast and then brunch. It was building fine with 4.4.4 so I have no idea what is wrong. Your help would be apreciated.
[Nexus 4 Original Android Development] sparksco:
Sounds like your missing proprietary blobs. I don't think it's default in omni. It's required to make a functioning ROM.
[Nexus 4 Original Android Development] kldoc:
You indeed need to get 5.0.2 blobs. Thing is the current build is actually 5.1, and we're not working on 5.0.x anymore. But Google didn't publish mako's binaries yet. You can use CM's binaries repo to get 5.0.2 blobs, Omnirom's binaries repo wasn't updated and probably won't be, issues with the lack of correct blobs is mainly drm issues, google video, netflix, hulu.

It's not really an issue until nightlies, Omnirom's features are slowly being ported to Lollipop, don't ask for ETA, we're nearing, but not here just yet ;) And I am myself working on porting some of those features, but I do this on my free time, along work and family life, i still try to keep you updated with at least a build per week, except when there are no significant changes on Nexus 4. I think that's all for now, if you got any Nexus 4 related questions, feel free to ask, for other devices, please ask in their respective threads, I myself only own Nexus 4 and really can't answer for any other device.

Have fun with OmniROM ;)
[Nexus 4 Original Android Development] morganmf:
You mean binaries in vendor folder? Downloaded from google site, unpacked and copied to omni folder.. Same as I done with KK, obviously I downloaded Nexus 4 binaries for Android 5.0.1 (LRX22C).. What java version is meant to be used?
[Nexus 4 Original Android Development] kldoc:
You need Java 7 openjdk, did you update your bootloader/radio ? If you did all that, I'll need a logcat to tell you more, but that's surprising, many devs were able to build and flash without issues. How large is your final zip, it should be around 209mb (that's what my latest build wheighs). First Boot can take a real long time too, give it at least up to 5 to 10 minutes.

Almost forgot, did you update TWRP, this can also be an issue if your recovery is outdated.
[Nexus 4 Original Android Development] morganmf:
Yep, everything is up to date, got java 7. My build is indid ~209MB, it shows omnirom bootsplash so fingers crossed.....it boots :D
[Nexus 4 Original Android Development] ubston:
My phone is showing an update available today. And the d/l page is showing that the update is for 6.0. The update on my phone doesn't show a changelog, so I'm not certain if this will automatically update me to 6.0. So I'm going to avoid it. I keep reading that the battery stinks with nexus 4/6.0.
[Nexus 4 Original Android Development] OniNoSeishin:
I see that update too now. I'll give it a shot but if battery really sucks as you say, It may be time to let go my nexus 4. It's been a long ride :p
[Nexus 4 Original Android Development] ubston:
Personally, I've only used 6.0 (and 6.1) ROMs for a few moments while testing them. But I've read a lot of comments about different ROMs for mako, and bad battery seems to be a common complaint.

Yeah, mako is old. But mine's still going strong. I get great battery life with the January omnirom build and with no gapps.
[Nexus 4 Original Android Development] bart.found:
Battery is actually a lot better in Marshmallow than in Lollipop! That's a fact.. probably due to the doze feature
[Nexus 4 Original Android Development] s_k_u_ll:
Hi all!!

One question, is there anyone using this rom? Can you confirm if pocket mode is working?

Thank you!
[Nexus 4 Original Android Development] kldoc:
Some features in my build are not yet merged, you'll need to cherry pick ;)

And gratz :)
[Nexus 4 Original Android Development] morganmf:
So it boots but it ain't stable, neither have any of the customisation options.
[Nexus 4 Original Android Development] kldoc:
Can you be more precise when you say it's not stable ? I don't encounter any issue ? And this is my daily driver. If you have force close, please join a logcat. Did you wipe data before flashing ?

Customization options: battery lights in sound and notifications. Ambiant display in display. I'll make a more up to date build around thursday.
[Nexus 4 Original Android Development] gravufo:
I tried flashing it today, just the ROM zip, dirty upgrade from 5.0.1 homemade build and everything GApps related was force closing.

I supposed I should try again but flashing GApps as well...Thing is, PA Gapps don't exist anymore and I don't know where to get a good version for 5.1!

Went back to my backup for now. Thanks for the build though :)
[Nexus 4 Original Android Development] kldoc:
Team seems to say those are working, I'm still on the removed PA gapps.

http://fitsnugly.euroskank.com/?rom=banks&device=gapps
[Nexus 4 Original Android Development] criminalzen:
builds

I just finished a 5.1 build with 3-15-15 banks gapps and all is (and has been the past few days) fine...
[Nexus 4 Original Android Development] kldoc:
Thanks for your feedback, glad to see everything is fine :)
[Nexus 4 Original Android Development] magnet1215:
I can't replace launcher by Google now launcher with default.. The button of launcher default resetting is grey.
[Nexus 4 Original Android Development] kldoc:
I see in your nicknane that you are located in Shanghai. Google Now is not available in China. You need to trick the gps and the playstore into thinking you are in a supported location to enable Google Now launcher. I am in China myself, that's how i do to force enable Google Now.

If you need help regarding this, just tell me, i can't provide any link (market unlocker), but i can guide you through the procedure if you need.
[Nexus 4 Original Android Development] Jokerli:
I think it's not the problem. Gel only works, if you flash it with gapps package. If you install from play store, you can't change the default launcher, even in germany. But with Nova Launcher, it works.
[Nexus 4 Original Android Development] TheeWolf:
A question, why is this considered unofficial?
[Nexus 4 Original Android Development] Jokerli:
Because, there are no official dailys yet... Some parts are missing and the blobs are from the 5.0 version
[Nexus 4 Original Android Development] kldoc:
Also true, but it should work with bank gapps, although I honestly didn't test that case.
[Nexus 4 Original Android Development] kldoc:
Because nightlies haven't started yet, nightlies being considered as beta version, this is actually alpha version.

Then, still waiting for Google to release 5.1 for mako, kernel and binaries weren't released yet. I don't want to tagg this thread official until everything is supported, and I'll only do so after core team decide to switch to official release for Nexus devices.
[Nexus 4 Original Android Development] kldoc:
Ok, updated the build (27/03/2015), not that many changes, also changed gapps to Bank's gapps, I'm actually on PA 5.1 beta2 gapps, I didn't test those Bank's gapps yet, but they are reported perfectly working.

Enjoy :)
[Nexus 4 Original Android Development] magnet1215:
Thanks you for your reply.

I am living in Europe now. I said in last post mean replacing launcher3 with Google Now launcher , not to activate Google Now.
[Nexus 4 Original Android Development] kldoc:
For this you need to flash Gapps. Bank's gapps should work fine, if they don't on the launcher, there are flashable zip that can be used to install the launcher. Google for it :)
[Nexus 4 Original Android Development] Jokerli:
Bank's gapps doesn't help... The Google Launcher is not included and if you install it from the play store, it can't be started... You need a gapps package with Launcher included, like tbo gapps package
[Nexus 4 Original Android Development] sparksco:
I have the same problem on hammerhead (nexus 5). Many Google apps like Google launcher, inbox and drive won't work. Google launcher just won't work but the other two force close.
[Nexus 4 Original Android Development] kldoc:
Nexus 5 running OmniROM ? If yes, you should talk to its maintainer. I wasn't able to reproduce those force close on OmniROM Nexus 4.

Nexus 6 update got pushed to AOSP, will post a new build with latest AOSP changes tomorrow if everything works well. I'm not inluding too many cherry pick, for stabilty reasons. The actual only cherry pick on current build is battery light support.

Kernel tree is still on 5.0.2, since Google didn't push anything related for 5.1 on Nexus 4. It shouldn't change much anyway.

Don't worry if I don't upload a new build on a daily basis, most devs are still focused on device bringup, therefore changes and enhancements are slowly getting done. We don't say it enough, if you encounter issues, please, provide a logcat with eventually a screenshot, the later not being fully needed in most cases.

Toward Gapps, 5.1 is still very recent. I'm certain a viable package for everyone to use will eventually be done. For now, Bank's gapps is the proposed solution. For the google now launcher, I'll try to find a proper link with a proper package to flash, not sure if such thing already exist on Xda or not.

Have fun with OmniROM :)
[Nexus 4 Original Android Development] sparksco:
It's only running on my nexus 5 since I tested it last and compiled from source. I'm actually on a different ROM now because the bugs didn't seem to be addressed for weeks on end. I may try again sometime, but like I said it didn't really seem worth it to use it as a daily ROM at the time. I may talk to the maintainer although I'm sure they are aware of the issues.
[Nexus 4 Original Android Development] kldoc:
Thing is your feedback is not relevant at all with this thread ? You said it yourself, older build, and lots have been done since then, both on ROM stability and Gapps and on AOSP side (already fifth version on AOSP). I don't know if Nexus 5 has a pre-nightly thread for OmniROM or not, but I really can not handle the support on that device simply because I don't own it. You can check who is its maintainer for Lollipop on this page:

http://docs.omnirom.org/Lollipop_Device_Status
[Nexus 4 Original Android Development] sparksco:
Thing is I never asked for support ?

I simply mentioned that I had the same issue with Google Now Launcher as others here do as well, and my comment was not even directed towards you. I also mentioned a few other problems just to see if others were experiencing it, then you came in and started trying to direct me on what to do.

Anyways, I won't bother your thread anymore, as it seems that's what your implying.
[Nexus 4 Original Android Development] kldoc:
As OP, it's part of the job when you post a ROM to try to answer your users questions, and since I'm Nexus 4 maintainer for OmniROM, it does seem a bit odd to see people coming from another device asking about its behaviour, then I'm new as a device maintainer, and slowly learning to handle issues and communication (nobody's perfect). I also had this issue with Google Now launcher, that I got fixed with a flashable zip that I found on Google, but the link didn't seem coming from a proper enough source to include on that thread. And I lacked the time to find another one. I'm sorry if my answer was a bit rough, I do have to keep this thread on topic to grab feedback, and solve issues as they come, but be certain I didn't mean no offense.

Gapps is truly an issue for a lot of ROM at the moment, and I don't have yet a definitive answer on this matter as devs keep talking about it even or IRC.
[Nexus 4 Original Android Development] herna:
Okay, I was reading this thread these last two days, and was waiting the [MENTION=2394329]sparksco[/MENTION] PM, but since he did not do is time to me reply you both.

[MENTION=2604804]kldoc[/MENTION] You need to controle yourself a little more. Maybe your native language is not English so you have some problems when you wanna say something to the users, or maybe you need to relax a little more, is not bad another guy to ask you if you have some errors. Also this time he is a Recognized Developer, it does not mean he is better than anyone, but if he got the title it means he has enough knowledge and he knows what and why he is asking.

[MENTION=2394329]sparksco[/MENTION] I am the Nexus 5 mantainer, and yes I have Google Now Launcher working with my device. I use my own gapps that I edited just for getting Now Launcher to works since I really use a lot the "Ok Google" command and the Cards. Also all the Google apps I have installed here works perfectly, including Inbox which I use over Gmail and Drive too, I tested the last one right now.

Here you have a link with the album showing the apps I mentioned before working correctly: Screenshots!

PD: [MENTION=2394329]sparksco[/MENTION] if you want my gapps I will have no problem to share you, just send me a PM.

PD2: Let be more friendly and share a good ambient here in the forum, and also let try to make OmniRom better helping new users to this ROM(yes, even if it was asked before) and always with the spirit of guys which wanna help other users to enjoy.
[Nexus 4 Original Android Development] kldoc:
Hello, new update :)

- 5.1.0_r3 (LMY47G) version bump

- various improvements / enhancements

- 1 cherry pick: Omnirom's gerrit

Some of you might experience troubles with that commit, I included it in this build mostly to get feedback. I have been running with it for a week or so, and didn't experience any issue, that's why I'm including it.

Expected result is a faster boot time after flashing update :)

Enjoy OmniROM :)
[Nexus 4 Original Android Development] sparksco:
PM sent
[Nexus 4 Original Android Development] morganmf:
Sorry for delay. After flashing fresh, no gapps, no su, just rom, it keeps unlocking, waking up, and the worse, because I am using PIN with my simcard, it keeps poping up with pin code request randomly, which means it can request pin 10 times during 10 minutes. This for me is unstable. Am I clear enough? Stable for you doesn't mean stable for everyone else.

Anyway yesterday I synced repo and make new build of it, shall try it today and see how it goes.
[Nexus 4 Original Android Development] kldoc:
I didn't have those issues on pin code because I use the security code built-in Android, not the SIM code itself, unfortunately, i can't reproduce it because I'm in China, and the SIM card menu is in chinese, I just can't read it.

I'll transmit this to main team, and ask them to test this, but I'll definitely need a full logcat to be able to investigate.

Edit: One question, were you running another ROM before or were you on stock ? Issue "might be" a false contact in the sim tray, that could explain this behavior. What you could try, is fully removing the sim, then reinsert it. I'll keep investigating about this, clearly not normal. Don't forget to reboot your phone after reinserting the SIM (might sound obvious for a lot of people, but I myself tend to forget about that ^^').
[Nexus 4 Original Android Development] morganmf:
Do you at least try to understand what I wrote?? I mentioned that I flashed rom only! No gapps neither su. Only rom. Done it on purpose so I could exclude potential problems from those two. On daily basis I am using omni 4.4.4 with KK gapps and SuperSU from chainfire. When I try my LP builds I make complete format so I flash only rom on clean phone. Also I don't keep any contacts on my sim card as I am using Google for contacts.
[Nexus 4 Original Android Development] kldoc:
Indeed, sorry, I actually read too fast.

I already reported the problem you are having to main team, but it might take me 1 day or 2 for me to obtain feedback, due to different timezone (+12 hours with USA).

I already asked them to test with a pin code on SIM card, since it's where your problem lies.

If you can provide a logcat when this happen, it would really be helpful, and sorry to insist about that, I actually want to know if it's device related issue or ROM related issue, and we can't find out easily without a logcat.

In the meantime, pin code on SIM card will protect your phone line, but not your phone itself, if security is an issue for you, you might want to also setup a code on phone side, since simply removing the sim card would then allow anyone to unlock your phone and access your data.

Also let me know if removing/reinserting SIM card fix that issue, it can happen that sometimes, sim moves slightly in the tray, that could trigger the pin code to be asked again.

Another thing that I read on Google's forum, if protocol changes (2g=>3g), it can also trigger this issue, try to setup a fixed carrier instead of automatic in network operator settings, and see if that works, I actually have issues on that side, modem that really often check for network. This will need updated binaries from Google to fix, we're stuck on 5.0.1 at the moment. And setting up a fixed carrier can be a workaround until it gets fixed for good.
[Nexus 4 Original Android Development] morganmf:
Ok, thanks. Sim code is to protect my simcard obviously. I will flash today's build later on, maybe even today. I am bit busy at the moment. Anyway, once flashed i will try to reproduce error and get the logs.
[Nexus 4 Original Android Development] kldoc:
You're very welcome. I edited my precedent message with a possible workaround, let me know if that helps. I've seen bug reports from users on Google's forum reporting the same kind of issue, and setting up a fixed carrier actually helps with disconnections.
[Nexus 4 Original Android Development] radekula:
Hi.

I'm not sure but it looks like there may be a problem with radio binaries. I was on 5.0.x for a longer while and I didn't have any problems, on 5.1 (27.03 and earlier) I did have one random restart per day. I'm still waiting if on 29.03 this will be repeated.

I did not write last_kmsg but from what I remember there was something like that in log:

Boot info:
Last boot reason: wakelock

and wakelock was something like that: qcom_rx_wakelock (I will try to catch whole log next time).

Maybe this is also a reason for morganmf problems?
[Nexus 4 Original Android Development] kldoc:
Thing is radio binaries themselves are not part of the ROM, you've got to flash them manually. And the other problem is OmniROM is now 5.1 while binaries modem and bootloader are all 5.0.1. Most of those issues should be solved when Google finally release those. Until then it will be difficult to do anything on that side, mostly because any attempt to fix these would be wasted once Google release updates. I will report those to main team, but they can't really do much at the moment :(
[Nexus 4 Original Android Development] radekula:
Don't worry - it's not a bug report :) I'm waiting for new binaries too before posting anything about 5.1. My intention was to indicate that errors with sim card doesn't have to be related directly to ROM.
[Nexus 4 Original Android Development] kldoc:
I'm not having those reboots, I actually had 1 sleep of death, but I do have problems with the radio, keeps looking for network, I guess that's what's causing those issues when you set a SIM pin code, connection to the network means pin code asks. *Sigh* Come on Google, it's about time now ... We had no 5.0.2, we're in April. we need 5.1 ...
[Nexus 4 Original Android Development] ebsbow:
Also have 3x soft reboot at random(..) and no SIM notice one time. Had to pull it out and in again.

But so far the rom(2903) seems to run fine.
[Nexus 4 Original Android Development] kldoc:
Thanks for your feedback.

Seems to be common issues on Lollipop on Mako, it might explain the HUGE delay from Google ... We should have 5.1 this month though, at least that's what I read.
[Nexus 4 Original Android Development] magnet1215:
Battery drains too fast
[Nexus 4 Original Android Development] kldoc:
Hello folks !

New build, 4/4/2015, DeskClock updated, beside that, not many changes.

Still no updates from Google, don't expect a different behavior on the ROM before we get updated kernel/binaries.

I'm aware of the modem issues, but those will have to wait 5.1 from Google or whatever next release it will be (5.1.1 has been spotted).

Not directly related to OmniROM, Google Play movie is now working without issue with latest updare ( I first thought it was a blob/DRM issue, it appears it's not).

[MENTION=2394329]sparksco[/MENTION] Tried to apply the modifications to switch to a user build, didn't work, will try to find out why, but I didn't have the time this week to do so.
[Nexus 4 Original Android Development] kldoc:
Thanks to [MENTION=5977233]Cem0[/MENTION] I'm currently testing this commit

https://github.com/ProjectDISCO/and...mmit/f9d53c992aba482ee0fe016927e7766412fbc886

I'll make an updated build during the week end to publish here as a cherry pick for you to test it out.

This is supposed to help with your battery drain issue.
[Nexus 4 Original Android Development] sparksco:
It looks like that hides some battery usage on the summary... How exactly does this fix battery drain? Can you explain exactly how the code is extending battery life? If your solely basing your battery life off of the usage summary, instead of how many hours your battery is actually lasting then your fooling yourself [emoji38]

Interestingly enough I never had this "miscellaneous" battery drain showing before. Must be device specific.
[Nexus 4 Original Android Development] sparksco:
Odd, works fine for me .. Did you dirty flash keeping USB debugging on the whole time? You should realize that just by having USB debugging on all the time will cause more battery drain (and logging). At least with user builds USB debugging is off by default.