yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] kldoc:
It's in the build :) But with the new doze mode introduced with Marshmallow, you won't get much actually, since only high priority notifications gets relayed when doze mode is active, and those must go through google cloud, so sms/text and phone calls.

My experience is it actually works rather well, but my usage is pretty different from all of you since Google is blocked here. I guess you'll need to test by yourself to see its behavior and see if it suits your needs. I really can't test that here ( Doze kill wifi when active, my vpn doesn't survive).

If you want to make a test, backup all your data, sms and call logs, make a twrp backup, flash the ROM and test, this way you can very easily go back to lollipop ;)
[Nexus 4 Original Android Development] PVL_93_RU:
Regarding the Ambient Display - I find it highly inreliable on N4 custom ROMs (or perhaps on Custom ROMs in general). My device may sit on the table perfectly flat without any movements or vibrations from outside, and the Ambient Display will trigger automatically on a complete random occasion, sometimes several times in a row

And I don't even know what happens when the device is in my pocket, probably activating even more often, wasting my battery constantly
[Nexus 4 Original Android Development] TheeWolf:
Thanks, actually I care way more about turning on my screen by swiping my hand over the proximity sensor, than getting notifications. What I should have asked is of this feature exists.
[Nexus 4 Original Android Development] kldoc:
I've got it enabled, but I don't have your random activation issue, I use it mostly to take a peek at what came up, and kill the notification if I don't want it. Have to admit I didn't touch anything either on its settings.
[Nexus 4 Original Android Development] kldoc:
You know Nexus 4 doesn't have the required hardware to make it work without draining battery ? It was introduced on Nexus 5 IIRC. Basically, how it works on Nexus 4 is avoid deep sleep to keep on proximity sensor. It will not be "that" a huge drain, but still.

Modified Ambiant display hasn't come back yet, I guess it won't be too long, didn't see any commit yet about it, UI is currently being backported, along with device bringup (r26 triggered some issues on a few devices). Things are now going rather well, I can't tell you much more, I'm myself quite busy with work and fix issues I encounter as much as I can as fast as I can. Found out about the speed filter on dex2oat today, and this issue with facebook was driving me nuts, that's why i published the build as soon as i got it tested :p

Device wise, Nexus 4 is more or less ready, didn't find any major blocking bug, waiting for kernel updates from Google to see if there's any fix needed. Thing is, and that might be an issue for a lot of you, and a requirement for me, you're not without knowing that OmniROM doesn't include root, and my builds are actually set with selinux permissive, but it won't be the case for nightlies. I'll keep on publishing my own builds until a proper solution is found toward that matter. I myself need root to fake my location to enable google now and google now on tap (even harder to do than it was on Lollipop).
[Nexus 4 Original Android Development] I.P:
Flashed it an hour ago with open gapps mini, so far so good.

Thanks for your work.
[Nexus 4 Original Android Development] PVL_93_RU:
Well, I have a very recent example - just yesterday I flashed this ROM, I didn't touch any settings other than the basic stuff like sounds and brightness and whatnot, and as I was updating apps via Play Store, I have witnessed how my Nexus woke up due to Ambient Display two times in a row displaying the same notification.

I haven't touched the device itself, it sat completely flat on the table, I didn't kick or shake the table itself, so I have no idea what trigger the device to turn the screen on, unless Ambient Display is supposed to automatically show me the latest notifications even without the reaction from the sensors of the device itself

Isn't the whole idea of this feature to only show you the notifications when you pick up your device or pull it out from a pocket?
[Nexus 4 Original Android Development] kldoc:
As far as I understand, no, it should light up if it's not in your pocket, and since the proximity sensor is currently not active (because needed hardware isn't there, therefore not supported, and software modification not backported yet), this actually is the normal behavior, if a notification pops up, it will triggers a black and white screen to let you quickly read what the notification is about, and let you take action towards it. Before ambiant display, you would'nt have anything displayed, just a sound, and the led that blinks, ambiant display here is to let you see the notification without draining too much battery by displaying a black and white screen.

I wished Nexus 4 had the hardware to support proximity sensor while deep sleeping ( Nexus 5, Moto x), but it doesn't, that's the reason why, out of the box, ambiant display's behavior isn't that useful on Nexus 4. As soon as someone backports it, i'll include it in my builds, but I don't have much time to do the backport myself (probably not much work involved, still requires time that I don't have right now)
[Nexus 4 Original Android Development] PVL_93_RU:
Oh? Well if it's supposed to trigger upon receiving every notification - I'm glad that I turned it off as soon as possible, the N4 battery life is already bad as is, no need to waste additional percent due to such a "Feature"
[Nexus 4 Original Android Development] kldoc:
Unfortunately, I can only agree ... But, with doze mode that got introduced in Marshmallow, you should receive a lot less notification while your phone is standing on a table unplugged, since only priority notifications can wake up the device.
[Nexus 4 Original Android Development] mandgeo:
Please investigate this bug...

Using Omni 19.11.2015 with Quanta V9 (for usb otg).

I'm in a call. I'm using the loudspeaker mode. I can hear the other person, but the other person can't understand me. The sound is scrambled. In the usual way, the sound is great.

Is it a rom or a kernel problem?

And another thing...

Sometimes camera app is starting when i push the wakeup button. I know that i saw in other roms double tap wakeup to start camera, but i didn't saw it in omni. And i do know that it could be a button problem, but that setting is somewhere...
[Nexus 4 Original Android Development] kldoc:
Without a logcat, i can't tell you much, I didn't try to make a phone call using speaker, but did some VOIP, no issue on my side.

You can't use a kernel that has been based on cyanogenmod, that's for sure. Did you download the CM based or the AOSP based ? Even then, I'll need a logcat to see what's going on there, I've got my idea why it would react like this, but I need logcat to verify.

Double tap require software modifications since Nexus 4 hardware doesn't support it, and OmniROM is very close to AOSP on that matter. Keeping the screen sensitive while sleeping will avoid deep sleep, I don't remember seeing that feature in OmniROM, and wouldn't recommend using it because of battery-life issue. Nexus 4 is aging ;) It's aging rather well, but it still is a 3 years old device, and features that came after that can be ported, but when hardware doesn't support it, it means more work for the SOC and the software to do the work that would normally be done by hardware, which needs more power, as simple as that.

On that matter, Nexus 4's hardware doesn't support any of the gesture, tap and so on technology to wake up the device, means any ROM that implements those actually keep the phone from going deep sleep.

I don't have that issue with my camera, then you're using a custom kernel, can be related. I don't really recommand using a custom kernel right now, only a few ROM did the move to Android 6 r26, and kernel from Google hasn't been updated yet, this certainly can bring issues, had to import a new drm blob to allow boot, and add a modified channel count for audio input in the framework to be able to use phone.
[Nexus 4 Original Android Development] mandgeo:
I'll try to send you a logcat in a private message. I don't know if it's ok to post it here.

In the first post, you are tellng that this rom is based on AOSP. That's what i've installed. An aosp compatible kernel. And it works like a charm in every way.

For the low mic volume in speaker mode... I've cleaned the microphone holes and now it's better. I would expected to be a little louder, but still it better than before. Questions... Mako has two microphones? One near the charging/data socket and another near the front camera? Both of them should be active when using speaker mode? Maybe, in my case, the upper mic is not working, or maybe the phone is not using it. In speakermode, the upper mic is used. In normal mode, the lower mode is used.

I'm not talking about touchscreen double tap. I'm talking about power button double tap. In Chroma, there is an option to enable/disable this feature. I was wondering if in Omni has this feature active by default or is the kernel who is doing this. Just found it in settings :D
[Nexus 4 Original Android Development] brandonabandon:
+kldoc i didnt want to quote yer last comment as it was rather long. im particularly interested in the last few sentences. anyway you can point the frameworks commit used to enable audio?
[Nexus 4 Original Android Development] kldoc:
Sure,

https://gerrit.omnirom.org/#/c/15700/

Channel count is initialized to zero by default, which was breaking audio input on a few devices. Nexus 4 should be initialized to 2.
[Nexus 4 Original Android Development] kldoc:
Didn't have time to analyse your logcat yet, the fact that there are two mics might need further modifications on how HAL is defined. I know that Google did some changes internally, but we don't have any sources yet.
[Nexus 4 Original Android Development] mandgeo:
Let me know if i got it right. You are telling me that both mics should be used when talking in speaker mode?

I'm asking because i have in mind to open my phone and if something is wrong with the top mic. Something other than dirt.
[Nexus 4 Original Android Development] kldoc:
I actually didn't have much time to study how mics are being used (crawling under work),

before doing so, I'd advise you to make a TWRP backup, wipe and try another ROM to see if the problem is there or not, this will eliminate (or not) the software issue.

Proceeding to "surgery" when you are not certain where the issue comes from doesn't seem a good idea to me ^^'

In the meantime, if someone else can give me similar feedback on this, would help, thanks :)
[Nexus 4 Original Android Development] kldoc:
[MENTION=4645037]mandgeo[/MENTION] If you find a ROM that is Android 6 r26 without that problem, thanks to give me the name, would be real useful to see how they fixed it admitting the problem is software, thank you.
[Nexus 4 Original Android Development] mandgeo:
I've tried resurrection re mix and xenon HD 5.1...both are using the upper mic and on one of them the volume was even worse.

On Chroma, is at the same level as on Omni and still using the upper mic.

I think it's normal for the speaker mode to use the upper mic. Using both could get to echo.

I think, in my case at least, that it's a hardware fault and I'm going to open the phone. It's not for the first time :D

It would be nice if someone could test and tell something about this issue.
[Nexus 4 Original Android Development] kldoc:
Thanks for this advanced testing, thing is I don't have much people to call actually ( a foreigner in China can't call much people :p ), that's why I'm looking for people to test this issue you're having.
[Nexus 4 Original Android Development] PVL_93_RU:
One thing that kinda irks me about this ROM is that the ripple effect when interacting with menu items seems bugged

It stays permanently on screen until you tap somewhere else. If needed I can provide a screenshot of how it looks
[Nexus 4 Original Android Development] kldoc:
I think I had that bug only once, at boot time, then I'm due for a new build, really didn't have time this week to make a new build, I hope being able to publish one by tomorrow.
[Nexus 4 Original Android Development] kldoc:
Hello, new build omni-6.0-20151128-mako-HOMEMADE.zip

Some bug fix regarding the cam, some deprecation removal, and this Fixes wifi auto-connect after sleep/reboot taken from Nvidia Shield as I was experimenting some issues with wifi.

Have fun with OmniROM !
[Nexus 4 Original Android Development] I.P:
Works like a charm here.
[Nexus 4 Original Android Development] kldoc:
Following CyanogenMod's github on latest changes for CM13, I cherry-picked latest commit, and are included in 11/28 build.

But one revert happened since them, CLANG usage was apparently breaking sensors, for that matter, I did a new build without CLANG usage. I highly recommand flashing that build over 11/28 build.

Wifi actually seems fixed ( I had a problen with the quicktile not activating wifi properly).

Here is the new build:

omni-6.0-20151129-mako-HOMEMADE.zip

Have fun with OmniROM
[Nexus 4 Original Android Development] I.P:
No issue so far, battery life is very good.
[Nexus 4 Original Android Development] kldoc:
Thanks for your feedback
[Nexus 4 Original Android Development] kldoc:
Hello folks,

there is a debate going on at the moment, and I need to know what you wish.

AOSP browser is EOL and has been abandonned by Google. Team is working on bringing prebuilt Chromium to OmniROM, and since the possibility to opt-out for it and keep AOSP browser is there, I wish to know what you'd like, keep AOSP browser, or have Chromium bundled with OmniROM as a replacement.

We're talking about a difference of size around 100MB more. I don't see myself deciding whether to include it or not without asking you all first, and will eventually run a poll when nightlies time comes. Regarding my experimental builds, I was thinking about bringing you a build with Chromium instead of AOSP browser for this week-end, but wish to ask you first if that's something you'd want. ROM size right now is around 230 MB, which would make it around 330 MB.

So, please, let me know what you wish :)
[Nexus 4 Original Android Development] I.P:
+100MB for a browser ? Man that's huge for a software many people won't use imho. I might be wrong but how many people despise google so much in your user base that they can't install the play store to download a browser ?

I think that downloading a browser from the play store will be OK for most people and for those who don't want to use gapps is it possible to develop some kind of F-droid downloader bundled with omnirom ? Once F-droid will be installed those people will be able to download any browser or other alternative appstore they like. This way you have nothing to develop/build/test except a very basic custom app.

Or else package a flashable chromium ZIP file and add a warning in OP that people who don't want to use the play store should download and flash chromium.
[Nexus 4 Original Android Development] kldoc:
I tend to agree with you, thing is AOSP browser is clearly outdated and abandoned, and there aren't many other alternatives on Opensource side.

That's why the topic has come to the table. I myself use Chrome or Dolphin. Since everybody downloading or building OmniROM for Nexus 4 is a user and/or developer, that's why I didn't take an arbitrary decision, OmniROM is opensource, and when some decisions can change a lot, and can be set differently device-wise, my reaction would be to involve everyone in the discussion to decide whether or not including such a large change :)

For that matter, I'll try to actually make 2 builds next week end, one with Chromium, and one with AOSP browser. The number of downloads will be a good indication of what people wish for ;)

I myself would tend for AOSP browser, mainly because I don't have the need for Chromium since I like Chrome's features (google sync), and then to avoid killing the system partition which is already rather small on Nexus 4.

But once again, this is not a decision I'll take alone, that's why I open the debate for Nexus 4 on experimental builds for Omni 6 here.

Never used f-droid before, and probably not going to, but you can suggest this in a feature request. I think it's not in the spirit of the ROM to offer any external bundle, there are official recommendations, but nothing in term of optional flashable zip (still open to debate :p ).
[Nexus 4 Original Android Development] saenanme:
Regarding the browser, usually I use AOSP browser on every android device I have, but if Google is going to deprecate it I prefer to install another one instead Chrome

I don't know if it is necessary that a browser be part of any android rom; but if it is not, I prefer a ROM without browser and I would install another one after flashing this rom.

BTW, I flashed the last version and it works without problems but I'm not a normal user because I use my N4 as secondary phone without data ...

Thanks for your work

Regards,
[Nexus 4 Original Android Development] I.P:
Well I don't use f-droid either it was just an idea to avoid 100mb of bloat in my system partition.

Anyway as long as the default browser is good enough to download an alternative appstore I think there is nothing broken and hence nothing to fix. If I wished I could even download f-droid/whatever with lynx over a RTC link so there is definitely no problem imho.
[Nexus 4 Original Android Development] schiznik:
I'd say leave both the aosp browser and chromium out. Anyone looking to use this is advanced enough to be able to get their preferred browser installed one way or another
[Nexus 4 Original Android Development] kldoc:
All your answers tend to go in the same way I was myself going, keep AOSP browser, I'll still provide a build with Chromium for the sake of it and for testing purpose, but I tend to agree with you :)
[Nexus 4 Original Android Development] mandgeo:
As far as I understand, chromium is the open source version of chrome. Open source meaning that it hasn't some proprietary codecs and stuff. At least that's the story on PC.

I don't see why to bundle chromium with a rom. The user has the choice to install chrome if he wishes.

The size is almost the same.

** l've asked someone to test the sound quality in speaker mode and he said it's allright. I've opened the phone to see if something is wrong with the upper mic, and there is no problem.

I think that my problem it's caused by the hardware.
[Nexus 4 Original Android Development] saenanme:
No idea that there was an open source version from Chrome. :good:

Off-topic:

I downladed the last version and there are two apk files.

Does anybody know if both files must be installed? :confused:

End off-topic

Thanks in advance

Regards
[Nexus 4 Original Android Development] kldoc:
If I'm correct, there should be a 64 bits apk and a 32 bits apk, we're 32 bits ;)
[Nexus 4 Original Android Development] kldoc:
You can follow this Chromium thing here:

https://gerrit.omnirom.org/#/c/15811/
[Nexus 4 Original Android Development] kldoc:
New build, most noticeable change is back of silent mode, some bugfix, you can follow changes on OmniROM's gerrit.

I didn't include Chromium yet.

omni-6.0-20151204-mako-HOMEMADE.zip
[Nexus 4 Original Android Development] gbetous:
First of all, thanks so much for asking :D

I guess that it really depend on what you want from OmniROM. And this choice is not a detail, it should/must/shall be directed by the philosophy of the ROM.

Want the best user experience out of the box ? Include Chrome

Want OmniROM as a base for anyone to build its own ROM ? Don't include it

Want to be Google oriented ? Include Chrome

Want to let user choice independant brower ? Don't include it

But here is my personnal answer to help on move forward : don't include it. You don't give GoogleApps ? Users can still download/install them quite easily ? So keep light ROM based on pure AOSP, keep default browser as long as it is included in AOSP, and prepare yourself to give a ROM to the community that don't even contains browser.

And also... thanks again for your great work ;)
[Nexus 4 Original Android Development] kldoc:
Thank you for your elaborated answer :)

Thing is you pointed all things that are currently being talked towards that possible change.

Some wants it, some don't. I kinda agree with keeping AOSP browser for now, less strain on system partition, and in the end, it's very easy to download a more up to date and complete browser.

I don't see myself taking decision without asking you folks first, because OmniROM is a community opensource ROM, so when a device question rise, its users should have the right to participate to what should be included or not.

I always was strict on AOSP compatibility because it's a ROM policy, OmniROM is AOSP based, and should stay 99% compatible. Since I took over Nexus 4 on OmniROM, things that have been added in device tree are either to enable new features in OmniROM, either bugfix, but there's nothing "hacky" either in device tree either in kernel tree.

That's why, for example, that OmniROM don't have the needed patch for OTG or LTE support, because those are not supported by any mean out of the box in AOSP for Nexus 4. LTE requires a modified radio that could introduce bugs, and OTG support doesn't work without a Y cable.

But because OmniROM is AOSP based, that means that most AOSP based kernel with those enhancements will work out of the box.

This (rather long, sorry for the novel :p) explanation, for all of you to understand my approach on maintaining Nexus 4 on OmniROM.

As long as there are ROM wise decision that have a switch device wise, I will ask you what you wish, since you're a user as well as I am, and no decision of this kind should be taken without a device's userbase opinion :)
[Nexus 4 Original Android Development] kldoc:
ROM is stable enough for me to remove experimental status, welcome to those who were waiting for this to try out Omni 6 on Nexus 4 :)
[Nexus 4 Original Android Development] saenanme:
For me too.

I'm using chromium in my shield tablet and I think that is a good alternative to ASOP browser.

I think that the size is not a problem if we can use Cyandelta to update the flashable omnirom file

Thanks for your work

Regards

Enviado desde mi A0001 mediante Tapatalk
[Nexus 4 Original Android Development] I.P:
Flashed last build this afternoon, everything works well. Thanks !
[Nexus 4 Original Android Development] kldoc:
Hello folks !

OmniROM has been synced to Android 6.0.1 r6, I already partially synced repos, I intend to make a test build tonight, but I'll wait until this week end to publish any build. This to allow me to do some testing on the ROM to make sure nothing is broken (last time in-call audio was broken). Those who are building by themselves "should" be good to go, but until I tested it myself, I can't guarantee any success there.

I didn't push blobs to OmniROM's github yet, there is no hurry on that yet, just know that you can't use CyanogenMOD's vendor tree as is on OmniROM, but you can take the newer blobs from there and put those in the right place in OmniROM.
[Nexus 4 Original Android Development] kldoc:
UPDATE on Omni 6.0.1 r6, I did an initial build, everything runs fine, but I need some more testing, will probably publish a build this week end :)
[Nexus 4 Original Android Development] kldoc:
Ok, quick update for those who are building by themselves. i just got blobs merged for Nexus 4 on Donkeycoyote, you now can use it to get the needed blobs to build Omni 6 on Nexus 4 :)
[Nexus 4 Original Android Development] kldoc:
Hello folks. as promised. new build:

omni-6.0.1-20151211-mako-HOMEMADE.zip

Android 6.0.1 update along with a few backported stuff and bugfix.

I'm probably going to make another build this week end to test system less root with selinux setenforce.

If that would succeed, all future builds would be selinux enforced.

Have fun with OmniROM :)
[Nexus 4 Original Android Development] TheeWolf:
Thank you! But, would it still be possible to root?
[Nexus 4 Original Android Development] I.P:
+1 for this question