yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] kldoc:
No it's not implemented.

From the look of it, it's a flashable zip, did you try to flash it to see if it worked ? OmniROM is based on AOSP, so if the code for this patch was made to work with AOSP, no reason it doesn't work as is.

I'm not asking you to buy anything, but usually, when softkeys are not working, it often means digitizer is dead, which can easily be replaced, around 50$ on ebay for a screen assembly, and I think it's worth it on a device such as Nexus 4. Just saying ;)
[Nexus 4 Original Android Development] I.P:
Speaking of implementing things, my question from last week was buried by the advent of the nightlies but is there something planned regarding EAP SIM ?

Thanks !
[Nexus 4 Original Android Development] kldoc:
Actually, there doesn't seem to be any AOSP ROM wich support EAP-SIM/aka, that's all I can say, I don't think it's a priority for devs right now, focus will be made on missing features before implementing anything new. Then, it needs developers that can test it, for my part, I can't test it since I don't have any network that uses it.
[Nexus 4 Original Android Development] I.P:
Well never mind, I lived without it until now anyway.

Thanks.
[Nexus 4 Original Android Development] dayr:
Wow. I am quite surprised about this room. I was on another room (5.0) waiting for Omnirom, and my battery used to last around 10 hours. More than 24 with you :D And I just love the "omni-feeling" :P

Happy to be back!

Thank you for the work!
[Nexus 4 Original Android Development] glz:
Hi,

First of all: thank you for the fantastic job ! This is running very well.

But I have one little problem: I only have "H" speed and not "H+" like before with version 4.

I've done a full wipe and clean install, I've upgraded radio to the latest version.

I've also try flushing APN and recreate it.

I'm using Sosh on Orange network in France.

Any similar problem ?
[Nexus 4 Original Android Development] kldoc:
Thanks for your feedback, glad you enjoy OmniROM.

I don't remember seing H+ on Nexus 4 actually, being AOSP, CyanogenMod or OmniROM. Then I'm not in France (although I'm french), I'll do some research about this matter.
[Nexus 4 Original Android Development] kldoc:
Welcome back :) And glad you like OmniROM :)
[Nexus 4 Original Android Development] I.P:
For the record I found this patch for Android 2.3, it's supposed to implement EAP SIM:

https://code.google.com/p/seek-for-android/wiki/EapSimAka

I guess many things have changed since it was released though... As it looks like there are many French people on this thread I guess you know why it would be useful to have this feature ;)
[Nexus 4 Original Android Development] glz:
I'm sure with omnirom 4, I've alreay seen, every day, H+

Thanks for working on this.
[Nexus 4 Original Android Development] kldoc:
I know, 1 year ago, I did go back to France for a month, and yes, EAP-SIM is really useful for free-wifi, and i was forced to manually log in to get in. I really don't have much time to look into it right now, but i'll give it a look when I've got time, admitting i can get it to build, I'll need people willing to test since I can't.
[Nexus 4 Original Android Development] I.P:
Well, ask for it on any French Android related forum and you'll get more testers than you've ever had for any other feature ;)
[Nexus 4 Original Android Development] kldoc:
After a small search on Google, this seems to be a lollipop thing. I can't tell you if there are any plan to add an option to customize this or not, one is surely free to work on it and submit it to Gerrit ;)
[Nexus 4 Original Android Development] kldoc:
The "free time" factor is really playing against me here, I've got to move next month, and I really don't have much time remaining to start anything and actually finish it, neither do I know if I can actually do it. Things will calm down around September, but until then, most urgent is keeping Nexus 4 builds fully functional and answer issues as they arise, that's my primary focus until I can actually have time to "play" with sources and try out things ;)
[Nexus 4 Original Android Development] glz:
I did not really get it.

Is it only cosmetic problem ? Like Omnirom 5.1.1 did not have a "H+" display.

Or a real networking problem ? Like the phone running 5.1.1 can not work on "H+".

Of course, I don't really mind for cosmetic... :D
[Nexus 4 Original Android Development] I.P:
Don't worry, I know what it is to have lots of cool stuff I'd like to code and 1/10th of the time I would need to do it...
[Nexus 4 Original Android Development] kldoc:
It's purely cosmetic :)
[Nexus 4 Original Android Development] greg17477:
Yes, as I remember correctly there is no more H+ icon on android L. Never saw it on stock L.
[Nexus 4 Original Android Development] glz:
I was not sure I understood corectly ! It is clear now.

So there is no problem. :D

---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------

Ok, I did not know that.

Thanks for the information.
[Nexus 4 Original Android Development] TheeWolf:
Anyone using ambient display managed to get the screen to wake up just after getting the notification? I set the fade in and fade out values to 200msec (thought maybe it has something to do with it) but that didn't help.
[Nexus 4 Original Android Development] greg17477:
Yes, it's working out of the box for me. I did a full wipe before flashing.
[Nexus 4 Original Android Development] TheeWolf:
It's working for me too, but it takes about 2-3 seconds before the screen wakes up. For you the screen wakes up immediately? Again, just to be clear, I mean after getting a notification and not when you take it out of your pocket.
[Nexus 4 Original Android Development] greg17477:
I understand now. I will have to check how it works here. The 2-3 seconds delay could be intentional. Might ask this in the omni g+ community.

Edit:

Ok, just tested. Sending a pushbullet notification from a desktop to the N4. I hear the notification sound and the display wakes up approx. half a second later.

I am on franco kernel btw.
[Nexus 4 Original Android Development] Stevica Smederevac:
This is how it works,there is always the delay.
[Nexus 4 Original Android Development] TheeWolf:
That's how Google intended it to work?
[Nexus 4 Original Android Development] Stevica Smederevac:
I guess so. Tried many roms and there were always a delay .
[Nexus 4 Original Android Development] j2002:
I'm subscribing to the thread. I was anxious waiting for this version.
[Nexus 4 Original Android Development] usenexus4:
WLAN standby

I am back on omnirom.

The problem with the reboot seems to be solved.

I have a new problem: android seems to deactivate WiFi in standby.

I also had this problem with the stock rom. In the WiFi options I selected the option to keep it connected during standby.
[Nexus 4 Original Android Development] kldoc:
Glad you don't have random reboots anymore. Wifi issues ? Do you encounter the same issue on other wifi networks than your home network ? I know that Lollipop will actually not re-connect to your network if the connectivity isn't good. Thing is this connectivity is checked through Google's dns servers, and I'm in China where Google is completely blocked, I can't really test this since the vpn I use will actually try to keep the connection alive. Wish I could help here, but I really can't.
[Nexus 4 Original Android Development] usenexus4:
I am at the moment testing it with an other Hotspot.

Meanwhile I found this in the router log:

This comes from the fritz!box (a popular german router)

Translation:

A Huawei P6 which is also connected has no disconnects.

The connectivity is perfect I am just a few meters away from the router.
[Nexus 4 Original Android Development] kldoc:
I know a few commits to better handle Wifi in Europe are waiting, with nightlies server broken (out of space), it will take a few days to get those in a build.

European Wifi differs in that you have more channels to connect to (goes beyond 11), and it's a possibility that your phone and/or router doesn't really like the channel it connects to. In the meantime, in the wifi advanced options, there is no standby options, it says keep alive while sleeping(always, only when plugged or never). Wifi has two options, 2.5 ghz or 5ghz, default is automatic, can always try setting it on 2.5ghz manually.

Your p6 is on lollipop ?
[Nexus 4 Original Android Development] usenexus4:
No the P6 is on KK :)

I had channel 1 and changed it to 7 but the problem remains. The other network I tested (hotsport from another mobile phone) seems to be stable (no disconnects).
[Nexus 4 Original Android Development] kldoc:
It indeed seems to be a frequency problem (according to the bug report i read on Google's forum concerning lollipop), set it to 2.4 ghz instead of automatic, should solve your problem. It can happen that some devices have troubles with a router, aside from finding the good settings, there's not much you can do. Let's hope the commits to support regional wifi will help.
[Nexus 4 Original Android Development] usenexus4:
Done.

Lets see if it helps.
[Nexus 4 Original Android Development] usenexus4:
It does not help :(
[Nexus 4 Original Android Development] kldoc:
Well, nightlies restarted, you can try flashing latest build, and see if the wifi commits help. Again, you saw the thread for yourself, not many bug reports actually, difficult to know if it's an isolated case with a particular router, since it does the same on stock Lollipop, and you told me another hotspot wouldn't do that. If those commits don't work, means you've got to tweak your router, I can't help you more than that.
[Nexus 4 Original Android Development] usenexus4:
Must the nightlies flashed manually or will they be available on OTA?
[Nexus 4 Original Android Development] kldoc:
OTA is working now
[Nexus 4 Original Android Development] usenexus4:
Not for me :) it says that I am having the newest version.
[Nexus 4 Original Android Development] I.P:
YMMV but I had to update manually when OTA was made available again and only then did it start to detect new releases.
[Nexus 4 Original Android Development] Romman0:
I got notifications of the last 2 updates. Just ran it and it worked fine for the 7/8 nightly.
[Nexus 4 Original Android Development] kldoc:
Last 3 updates, also no issue for me :)

On a sidenote, I've bought a clone of cardboard, not too bad on Nexus 4, resolution is a bit low, but still usable/watchable :)
[Nexus 4 Original Android Development] demhareesan:
Can't install Google Play Games

Hi,

Tried installing google play games from the store, it gives a 505 error message. Then I downloaded the apk and tried to install it using ADB, it gave the following error message.

[INSTALL_FAILED_NO_MATCHING_ABIS]

Also I have installed other apps like google drive. G+ etc. they gave no errors. Anyone else having this problem?
[Nexus 4 Original Android Development] kldoc:
Which gapps are you using ?
[Nexus 4 Original Android Development] Romman0:
I had an issue with Google play games also, running PA gapps from Apr from here http://xdaforums.com/android/software/reborn-gapps-5-t3074660

There are some newer gapps here http://xdaforums.com/android/software/tk-gapps-t3116347

I got the 505 error from play store, all other apps installed fine. So I googled the apk and downloaded version 3.1.11 from here http://www4.zippyshare.com/v/Kmua9nVi/file.html

Installed fine and even updated through play store later on. Was able to play coc and bb again.

GL.
[Nexus 4 Original Android Development] demhareesan:
I'm using the gapps provided in the first post.

installing the apk from the provided link worked. Thanks
[Nexus 4 Original Android Development] I.P:
Glad to be able to set omniswitch as default app switcher again !
[Nexus 4 Original Android Development] :
ota update is not working for me with latest builds
[Nexus 4 Original Android Development] kldoc:
Yes it's broken at the moment due to download server change, sorry for the inconvenience, might take a few days to fix.
[Nexus 4 Original Android Development] eliav12:
Why I can't update the new version (I downloaded the file from the web and I tried to update from my recovery but I got error) do you know what to do?
[Nexus 4 Original Android Development] tedr108:
Two things:

1) Verify the md5 check sum on the downloaded ROM file

2) Give us the error message you receive while flashing
[Nexus 4 Original Android Development] usenexus4:
I am using 5.1.1-20150630-mako-NIGHTLY

Do I have to do a factory reset after an update to the newest nightly?
[Nexus 4 Original Android Development] tedr108:
No, I never do and never have any problems. I just flash the ROM, flash SuperSU (for root) ... and reboot the system. I still flash SuperSU along with the ROM (out of habit), but not sure that is necessary.

With some ROMs, it is necessary (even on a simple update) to clear cache and Dalvik, but with Omni that is covered.
[Nexus 4 Original Android Development] TheeWolf:
[MENTION=2604804]kldoc[/MENTION]

My phone restarted on itself twice today, once during a call and once for no reason. Of course those are not the first two times this is happening.

If I use an app for taking logcats (I think I used one called catLog) after the restart, will it still provide the important information that you need to figure out the problem?
[Nexus 4 Original Android Development] kldoc:
After a restart, no, only way would be to get last kernel message:

/proc/last_kmsg

But it's probably due to some app/widget you are using, not having those reboots here. Lots of apps are still not fully compatible with Lollipop.

Hardware issue can also explain this.

Force close are easy to log, because they'll add an entry into logcat, but logat gets erased after a reboot, so only kernel message can provide some infos about what triggered kernel panic.

If you manage to get a usable log of the reboot, feel free to submit, I'll try to investigate it as soon as I can.

I'll be unavailable for the next 3 weeks (changing city, and it'll be a few days before I can get a new Internet access).

Generally speaking, Random reboots are really hard to debug, when it's not happening to all devices, it's near impossible, almost always tied to either hardware issues or 3rd party software. 3 years old device, mainboard is aging, and it will eventually fail at one point or another.

Regarding Lollipop, there is nothing that can be really done driver side, since those are coming from Google, and OmniROM is built against AOSP. Real challenge on Nexus 4 will be Android M, admitting Google doesn't officially support it. If other users encounters the same random reboots, try to submit a usable log, so we can identify the source of the random reboot.
[Nexus 4 Original Android Development] TheeWolf:
I'll try to get that last kernel message.

By the way, I don't have any widgets so that's not that, maybe an app. Would be pretty problematic finding out which one though.

Also, I'm using the stock kernel, so no custom kernel causing this.
[Nexus 4 Original Android Development] kldoc:
Problem is there, since I can't reproduce it :( Most likely app related
[Nexus 4 Original Android Development] :
i also have a reboot issue with build from 24th. as soon as i touch a telephone number in contacts and want to dial phone immediately reboots and shows omni logo.

if i use the dialer and insert the numbers then its working.

i have configured sip account. maybe contacts does not provide the "ask which account u want to dial from".

24th and no custom kernel

br

edit: happens only when "ask first" (which account to use, mobile or internet) is activated and the bug is a real deal breaker ;) at least for me...
[Nexus 4 Original Android Development] kldoc:
What SIP app are you using ? I use CSipSimple and didn't have any issue related, then Contacts apps doesn't communicate with it, at least never tried.

Is it Contacts from the ROM itself or from gapps package ? Then again, I need logs to debug.
[Nexus 4 Original Android Development] kldoc:
Ok, i saw that options for SIP calling from Contacts apps, and had the same issue. Investigating.

I managed to get a logcat of it, transmitted the issue to core team.

You only had that issue starting with 24th nightly right ?

Found a bug report in Google's issue tracker:

https://code.google.com/p/android/issues/detail?id=161272

Which is exactly what's happening now, I'll let you know if any solution can be found.
[Nexus 4 Original Android Development] :
thanks for reproducing.

i dont know if it started from 24th or before.

did use an older build before.

have no gapps installed so using build-in contacts app.

br
[Nexus 4 Original Android Development] kldoc:
Thing is I actually also need SIP, but I didn't know there was already a native client. What you could try is use another app to do this in the meanwhile, I use CSIPSimple, not the best app ever, but I actually do phone calls with it.
[Nexus 4 Original Android Development] Romman0:
Just a heads up, Manually updated to 8/1/15, ota working again (was on 7/18). Not sure if it was dumb luck and they got the server fixed or if it was the rom.
[Nexus 4 Original Android Development] kldoc:
From what I understood, you actually need to be on the first previous build for OTA to work, or else it'll fail.
[Nexus 4 Original Android Development] TheeWolf:
[MENTION=2604804]kldoc[/MENTION] Can someone take a look at this:

http://jira.omnirom.org/browse/OMNI-1242

It makes a lot of sense in my opinion.
[Nexus 4 Original Android Development] Romman0:
Is there a difference between the ota or clicking update in the about phone. I used update to skip versions back in early July.
[Nexus 4 Original Android Development] kldoc:
OTA is actually triggered by using the update button.
[Nexus 4 Original Android Development] kldoc:
It does make a lot of sense, but it's actually not device specific, it's a ROM wise feature request, and we're summer time, lots of devs aren't active at the moment, and I myself don't have the time to start a work on it before September. Backport of features will eventually happen, but those need time, that's all I can say about it. But if you have the required knowledge to help on backporting that feature, you're more than welcome :)

I'll add that Android M is just around the corner, but the difficulties all ROM encountered in Android 5 won't likely be repeated on Android M. Android 5 was a major rewrite of some core parts of the framework, while Android M is a polished version, means, if everything goes well, work on it should go a lot faster.

Then, not knowing what will happen with Nexus 4 and Android M, I can't tell for now how long it'll take to have a working version. I know that all attempts that were done to try to port Android M on Nexus 4 failed, and until sources are released, there's not much that can be done about it. I'll be there, and give it as much time as I can to have a functional release of OmniROM, just remember i do that on my free time ;)
[Nexus 4 Original Android Development] TheeWolf:
I don't have the necessary knowledge, not yet :)

I thought that maybe the devs forgot about it or thought that there is no reason to implement it, so I wanted to know what you think about it.

Also, remember I told you about reboots that are happening on my device? I got that kmsg for you.

Can you check it and see why those reboots are occurring?
[Nexus 4 Original Android Development] kldoc:
I've read it, but there's nothing inside about a kernel panic. Only way to track your bug is to launch a logcat from your computer (better use linux for that), and wait that it reboots, that's the only way to get the infos we need to identify the source of the problem. That's how I tracked the SIP error, plugged the phone, launched logcat, launch SIP call, and get the logcat from the crash.

I think you were using SIM side pin code right ? Remove it and set it phone wise, that's the only difference I see for the random reboots you're having. If you can't do that, and can't log the reboot, there's not much I can do, sorry.
[Nexus 4 Original Android Development] TheeWolf:
I'm not sure what a SIM side pin code is, so I'm probably not using it.

I'll get you that logcat.
[Nexus 4 Original Android Development] kldoc:
Maybe I'm mistaken on the user, my bad, but basically, you can set a code when you unlock your phone on the SIM card itself, instead of the phone.

I'm sorry the logcat is tough to obtain, random reboots are truly hard to predict and trigger, and logging those is hard too.

But once the error triggering this is logged, it'll be easier (i hope) to identify what's making your phone reboot randomly.

I barely have 10 days ahead of me to work on this, and it won't be full 10 days, I'm moving to another city, and not sure when i'll recover a full internet access with everything settle down, might be rather fast, but I expect a week without anything but my Nexus 4 to get Internet.
[Nexus 4 Original Android Development] usenexus4:
I am using a nightly from the 25.07.2015. If I open the system updates, no new versions are shown. Is there any way to make updates automatic or do I have to use twrp for omnirom updates?
[Nexus 4 Original Android Development] TheeWolf:
One of the new nightlies that came out this month fixed the system updates problem - it now has a new UI and will automatically notify you of new updates. Install the latest nightly manually and you'll have the system updates working again.
[Nexus 4 Original Android Development] kldoc:
Small patch suggested by core team, https://gerrit.omnirom.org/#/c/14368/, to be included in next nightly.
[Nexus 4 Original Android Development] Strikkt:
I am not sure if this is ROM-related, but my app drawer icon somehow changed and I have no clue how to get it back to normal. Anyone else experience this?

Edit: nevermind, I'm stupid. Forgot to disable an xposed module...
[Nexus 4 Original Android Development] TheeWolf:
Can you explain to us mortals, what this commit is? :)
[Nexus 4 Original Android Development] kldoc:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3636

To make it simple, it's an exploit patch, that avoid someone from taking over your device ;)
[Nexus 4 Original Android Development] TheeWolf:
Thanks :)

I also wanted to ask, are the stagefright vulnerabilities fixed or is there a fix planned?
[Nexus 4 Original Android Development] Nurfed:
Zimperium tool says we are not vulnerable.
[Nexus 4 Original Android Development] usenexus4:
I have the problem that my interlocutor can here him self when I am using csipsimple.

This seems to be a known problem for nexus 4 and lolipopp:

There is already a fix:

https://code.google.com/p/csipsimple/issues/detail?id=2838#makechanges

could this be implemented in OmniRom?
[Nexus 4 Original Android Development] kldoc:
Going to test it myself, since I do need SIP, i'm in China, and I call my family in France using SIP, if it indeed works, will submit a patch, can't tell you exactly when though, i'm on the edge of moving to another city (next week), and won't have much free time this month. In the meantime, the workaround is simple, modify a plain text file that you can access with root access.
[Nexus 4 Original Android Development] usenexus4:
I changed the file but my interlocutor still hears himself talking.

My file looks like this:

http://pastebin.com/PAY9m280

edit:

https://code.google.com/p/android/issues/detail?id=62218

i am using omnirom 5.1.1-20150811-mako-NIGHTLY

Not fixed for me...
[Nexus 4 Original Android Development] :
sip calling trough contacts still reboots the phone.

swyping still fc android keyboard. could it be disabled by default?

or aosp lib used?
[Nexus 4 Original Android Development] TheeWolf:
As for swyping, just download Google Keyboard, it's a lot better anyway.
[Nexus 4 Original Android Development] usenexus4:
Looks that the nexus 4 has severe SIP problems.
[Nexus 4 Original Android Development] kldoc:
In the comments :

pre_processing {

voice_communication {

aec {}

ns {}

}

}

At the very end of that file.

I did the modification myself, and sounds seems a lot better on both side.