yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] kldoc:
r26 indeed broke the build, working on fixing boot ( adreno blobs issue ), no ETA as of now because the lack of sources from flo (hurry up Google !).

Sorry for the inconvenience.
[Nexus 4 Original Android Development] kldoc:
Hello folks !

I was able to fix boot on r26, it was a problem with new drm blobs missing.

Enjoy :)

omni-6.0-20151113-mako-HOMEMADE.zip

Have fun with OmniROM !
[Nexus 4 Original Android Development] kldoc:
I'm having issues with phone calls, unsure if it needs a factory reset or not ...
[Nexus 4 Original Android Development] kldoc:
Ok I removed that last build, I'm having huge troubles with sound in phone call, it's not stable at the moment, even after a factory reset.
[Nexus 4 Original Android Development] I.P:
Hi,

with the 20153110 build my battery life is terrible:

[IMG="bat"]https://lh3.googleusercontent.com/XKQ4S9LBvLuM8fd94AXaXPpz9j49xCORLHJbgqpck9FynOxMklcVEnlQR9T2SRWF5K-8gLqjrGP0MiRpcZ6hkyKzMOICZQXJDGfdCe3v3eQFhAnFjstofEow98FGrrEflLAR8lPMQOwsuAyIf23eGXIz8ShJTPovN4ojV0FQ7bsE2RfRA_z6TPIaWmgRrFKbPxaT9_W-7RCLKKKHyi3--VPvPugj-fy8AYPR18Yjp6ze7KzV3N5exdmMIVSqQ1USVQQBiP9oSun-EHrEqJaPS7Z5aMNP7PSx5a6Ip7wfW7xdwEQHC9Bgujl7lrrL3qMXUDBLtxesEf-t6dxaovO5jaWYmOKKzsgOPRmqMS46wOSDDxTzsHv3KfIfGXq-PA_Vz1AFIpus5eiEODdmbjbCV3aJdUojN2DHyvX0i4rDxcI5E02wr0pakn7Peo5xGYguhNciF8FuJcbLovskayPxHcBG46BdTmuhRaWXjZ1Z3kBDsn4ZDtIhrZT09s_yDlJBbD1YlzQgcDfIZOF2gXHU4GkVpcd7_J2iMKPxaldRy60=w616-h1024-no[/IMG]

The phone was sitting on my desk most of the time, no data, some wifi (less than 15 mins). With 5.1 I was able to use the phone until midnight without recharhing...
[Nexus 4 Original Android Development] mandgeo:
What are you talking about? All the OmniRom release are from november and you are complaining about an october release.
[Nexus 4 Original Android Development] I.P:
Obviously I misquoted the release date ! I meant the latest one from 20151109...
[Nexus 4 Original Android Development] mandgeo:
Did you used the flashlight? That was the only time i've experienced higher battery drain than usual.
[Nexus 4 Original Android Development] TheeWolf:
Probably a wakelock due to some app... use Better Battery stats (I just hope it works on Marshmallow already).
[Nexus 4 Original Android Development] kldoc:
Confirmed, QuickSettings tile for NFC is fixed and working properly, enjoy :)
[Nexus 4 Original Android Development] fishears:
I was just about to post confirmation. Nice job. I promise to use it always ;)
[Nexus 4 Original Android Development] redj12:
Hi guys. I installed the ROM few days ago and I don't know how to disable the quick acess to the camera. When I am locking the phone with power button it turn ON the camera. How can I disable it please ?

Thanks
[Nexus 4 Original Android Development] fishears:
it's in Settings>Display "Press power button twice for camera"
[Nexus 4 Original Android Development] redj12:
Thank you.

Do you have some issue with your power button ? I can only lock my phone but can't longpress. So when I have to rebot, i must use some thirdappps.

There is some place where we suggest things to Omni developpers ? I would like to see the Flash tile and the Sync one in quick settings.
[Nexus 4 Original Android Development] kldoc:
I don't have that issue with the power button.

Flash tile ? You mean the flashlight ? That one i have it, working as intended ?

A sync tile ? I don't think that's possible neither needed, you've got the option to auto sync data in the account settings, and you can't disable sync anyway, you can limit network usage to cut all background activities, such as sync, but it's a network thing, not a sync thing.

If you want to report issues or make suggestions:

http://jira.omnirom.org/
[Nexus 4 Original Android Development] mrk2815:
nightly 7/8 is crashing once it boots up. its giving me errors blue share has crashed and gives me ok and cancel. no matter how many times I have tried to get around this its just crashing. I have reverted back to 7/7 nightly ttill this matter has been resolved.
[Nexus 4 Original Android Development] saenanme:
Working fine for me

Regards,
[Nexus 4 Original Android Development] fishears:
Bluetooth Share is constantly crashing for me with this build. I just updated from 20160704 this morning.
[Nexus 4 Original Android Development] mrk2815:
will have to wait to see with 7/9 nightly if this has been resolved on my nexus 4 . its strange that blue tooth share crash happening to some and not to others.
[Nexus 4 Original Android Development] Fif_:
This is not limited to the Nexus 4, all the Nexus devices I have show the same problem with 20160708.
[Nexus 4 Original Android Development] kldoc:
Sorry, I was out of reach for work reasons, and couldn't post about the bluetooth issue, latest security update broke bluetooth, team is working on a solution, sorry for the inconvenience.
[Nexus 4 Original Android Development] mrk2815:
7/9 nightly has resolved the blue tooth share issue. its not crashing and has now been fixed . thanks for a prompt fix for the matter.
[Nexus 4 Original Android Development] Pac-Man:
Does anyone know how to uninstall some system apps like Chromium? I can't with SD Maid :(

EDIT:

Wop, I just saw that no su binary is installed... What? :(
[Nexus 4 Original Android Development] mrk2815:
just a question for the Omni community. I have been reading up on the new ssecurity measures in place for android nugget. I was wondering how the custom roms like Omni rom will address this for android nugget. will it be easy or hard to build android AOSp roms for older devices based off of Android Nugget. I am just curious on the matter.
[Nexus 4 Original Android Development] Pac-Man:
For now we can only speculate that someone finds the way to hack the boot and allow custom roms until new phones with N come...

I'm sure that ,if N4 gets N, we don't have this problem since our phone didn't come with N by default.
[Nexus 4 Original Android Development] mrk2815:
I just took a look at the cm blogs there will be support for cm 14 for the nexus devices in the list of supported devices, it was nexus 7 2013, flo, nexus 4, nexus 5, nexus 5x, nexus 6 and 6p. So I am wondering if there is cm 14 support officially for nexus 4 will there be Omni rom support for nexus 4 for android n as well . just wondering.
[Nexus 4 Original Android Development] xWolf13:
Source? Just checked the blogs and there isn't anything that informs us that the Nexus 4 will receive CM14.
[Nexus 4 Original Android Development] mrk2815:
http://techxat.com/android-devices-getting-cm14-nougat-rom-big-list/
[Nexus 4 Original Android Development] fishears:
Looks like click-bait to me.
[Nexus 4 Original Android Development] xWolf13:
You said CyanogenMod Blog. Not some other source no one else has heard of. Clickbait link + False information.
[Nexus 4 Original Android Development] kldoc:
No one can actually answer about Nougat support on Nexus 4 before sources are actually released.

There will most likely be a few issues that will need work, blobs will be tough to obtain, because no device that uses the same SOC than ours will officially get supported. End of life for Flo, Hammerhead, we might be able to get changes on the kernel side, but not updated blobs to go along.

In other words, this is going to be a long fight if kernel changes are many.

I will of course keep you informed on progress once sources will be released, but that isn't going to happen before October/November, still some time to go :p

For that purpose, i'll actually fork sources on my own github when the time comes.
[Nexus 4 Original Android Development] mandgeo:
Question. Is there any way to keep both wifi and cellular connection active? I want to access LAN over wifi and the internet over cellular network.

I've just bought a ZSUN device. This piece of technology makes a wireless network that shares the content of a MicroSD. The problem is that I've bought this device to expand the storage in my car (and that requires wifi) and I'm using Waze for navigation (and that requires cellular network).
[Nexus 4 Original Android Development] kldoc:
You actually need to test this, i don't think it's possible, but I might be wrong.
[Nexus 4 Original Android Development] mandgeo:
I've tested it and it doesn't work. That's why I've asked.

I thought someone could have some tips for me.
[Nexus 4 Original Android Development] kldoc:
Only way I can think of, would be to set a hotspot from your phone, this way you share your internet connection from the cell network to the wifi network.

This way, both networks will be enabled
[Nexus 4 Original Android Development] mandgeo:
Doesn't work. Hotspot disables wifi and wifi disables hotspot.

I've never thought that the problems about using this device will come from android...
[Nexus 4 Original Android Development] redj12:
Hi guys. I face woth some syncing issue. I enable/disable it via quick settings tile but even if it's enabled, it won't sync ! Calendar that i use with DAVdroid app, mails with K-mail, none of them are synced. I have to go in the settings and click on "Sync Now". Do you have the same issue ?
[Nexus 4 Original Android Development] kldoc:
That sounds like permission issues, but it's specific to those apps, those apps have support for Android 6 ?
[Nexus 4 Original Android Development] glz:
Hi,

Is it possible to disable camera quick launch with double click on "power button" when screen is locked ?

I've removed to icon from the bottom right corner... But I can not remove the quick launch by double click.

Regards
[Nexus 4 Original Android Development] schiznik:
Yes, it's in Settings under Display
[Nexus 4 Original Android Development] mrk2815:
how long till android 7.0 officially rolls to AOSp. it was just official today august 22,2016 for nexus current devices.
[Nexus 4 Original Android Development] kldoc:
Ask Google ? We don't have more information than you do on that matter :( My guess is sources will be released along with new Nexus devices, but i could be wrong.

And given the massive changes in the frameworks, don't expect in on Nexus 4 anytime soon.

I'll give you my todo list on that matter so you can understand the process that i'll have to go through to make it happen.

1 - AOSP sync and merge with OmniROM ( this can take up to 1 month)

2 - make it build against Nexus 4/Mako kernel and device tree, solve dependencies issues, etc ...

3 - fix boot

4 - get drivers working

For step 2, 3 and 4, since i'm alone on Nexus 4 withing OmniROM, i'll have to dig around in the community to see any progress and find ideas to get the code working on OmniROM.

Any help very welcome on all this :D
[Nexus 4 Original Android Development] glz:
Hi,

Thanks a lot, I did not have a look in "display settings" for a shortcut !
[Nexus 4 Original Android Development] kldoc:
Hi folks, Android 7 ( Nougat )sources dropped, in consequence, and due to the lack of free space on my side (mostly due to that), I'm going to switch to AOSP sources to begin the work on Nexus 4, I don't have enough space to keep both, if the needs come to update Omni 6, I'll eventually resync, but initial work on 7 requires me to sync sources and see how "bad" things are for mako.
[Nexus 4 Original Android Development] mrk2815:
strange that we have android 7 but no new devices to complement android 7.
[Nexus 4 Original Android Development] kldoc:
Everybody wonder the same, no one has an answer, wait and see i guess ^^'
[Nexus 4 Original Android Development] schiznik:
I've started to notice an odd issue with my n4 over the last couple of days, it seems like the very right hand edge of the screen doesn't respond to input anymore - eg I can't use a 'p' or delete in portrait, whilst in landscape I can't expand the volume slider unless I flip it around to be on the opposite edge of the screen.

I've seen this before when I botched a screen replacement on a htc wildfire years ago -fixed by fitting the digitiser properly. My n4 hasn't been dropped & there's no damage externally so I doubt a cables loose inside etc...

Is there *any* chance this could be a software issue? Or has old age struck finally? :(
[Nexus 4 Original Android Development] kldoc:
Well, digitizer has always been a weak spot on Nexus 4, working fine here ...
[Nexus 4 Original Android Development] kldoc:
Just to give you some informations on what's going on, Omni is slowly moving to Android 7, build system isn't ready yet, my own build env is ready for Android 7, but there are a few things to be solved before a build can actually be started. I don't have the knowledge to work on the build system itself, and kernel building isn't ready yet, which we need to build Nexus 4 kernel against Android 7.

Device tree won't need much changes, neither kernel, i expect the same issues than hammerhead on cam and gps. But it's not looking too bad.

Will keep you informed on evolution, and will post a build here as soon as i get it to boot. Please be patient, only a few days have passed, and we're hard at work trying to do device bringup :)
[Nexus 4 Original Android Development] schiznik:
Well, judging by the screenshot attached, looks as though my digitiser has gone bad...

Decisions decisions... Repair or upgrade?.....
[Nexus 4 Original Android Development] kldoc:
If you can find a cheap screen assembly on ebay or anywhere else, Nexus 4 is worth the fix imho, but it's also time for an upgrade :p

Waiting for new Nexus myself to change :)
[Nexus 4 Original Android Development] mrk2815:
hello just saw on XDA-developer that there is a working build of unofficial aosp for nexus 4 for nnugget. i was just wondering how the progress is going for the omni rom build . patiently waiting to do omni as i want to support the omni community community.
[Nexus 4 Original Android Development] kldoc:
I'm nearing a build completion, but couldn't finish because of work, some selinux commits that blocked me and didn't find the time to add those ...
[Nexus 4 Original Android Development] mrk2815:
ok, will patiently wait to test your builds. i just tried the unofficial aosp build. tehr are force close issues with set up wizard and permissions issues with google play services. so i think for a first build its an okay build but could be better. so i will be holding out to test your builds. i know that you guys put out great awsome stable builds .so for the time being i have gone back to omni 6.0.1 til l i see an build from you. bbacktbuilds.
[Nexus 4 Original Android Development] kldoc:
Thank you for your trust, hope we won't disappoint;)

Truth is you flashed google play a bit early I think, not sure how far the teams building those actually are.

Omni is working on syncing trees, merging, and fixing the build system, a few major things behave completely differently than before, it seems the remote behavior in manifest handling has changed a lot, and we're trying to figure it out and adapt Omni's repos to it.

I didn't really look forward an instant boot on the ROM myself, important is the workflow is established so we can actually work on the ROM itself without everything breaking every 2 days because of a repo/revision change ;)

I had some warning from the compiler regarding the gps, not sure how much is broken in there, won't be that easy to solve, it's depending on a library that Google put as deprecated in Lollipop, and that was later shipped with Flo.

I will later explain the details on mako's build so more advanced users/devs reading this thread can actually work themselve around this :)
[Nexus 4 Original Android Development] mrk2815:
i will wait to find out the details on gps. Will that eventually get resolved or no hope for gps working. just wondering could we see a build in a few weeks or will it take longer then that. no rush and no ETA on the matter .wondering.
[Nexus 4 Original Android Development] mrk2815:
hello heres a gps working patch on git hub. take a look and if it would help you out.

https://gist.github.com/ganadist/75307f7d05defaa7d519ae87b148202a

---------- Post added at 09:50 PM ---------- Previous post was at 09:48 PM ----------

hello that link that i gave you for git hub for the gps patch which is working for gps for the unofficial aosp android 7 nexus 4 rom. i ma hoping it helps you out. i am not a coder but a tester. .

https://gist.github.com/ganadist/75307f7d05defaa7d519ae87b148202a
[Nexus 4 Original Android Development] kldoc:
It all depends on how much free time I have from my work, then how much free time I get with my family, incapable to answer that as of now.
[Nexus 4 Original Android Development] gbetous:
I just repaired mine yesterday ! I bought the complete screen + digitizer around $25. It took me about half an hour to change the screen. I have a perfect digitizer now (I had 2 arrays where there was strictly no detection).

My advice : repair it ! Once you realize that this is finally quite simple, you will look differently the zillion Nexus 4 with screen issues to be sold around $20-30 ;)
[Nexus 4 Original Android Development] kldoc:
Only thing that bothers me is we don't have the origin of that code, any code that fix things properly is welcome though :)

But I need to do some research to understand where that code comes from, in order to give proper credits to the original author.
[Nexus 4 Original Android Development] gbetous:
Hi !

I'm back on trying to generate my own build :)

I'm now trying to generate a user build, with my own keys. I posted here, but with no answers so far :(

http://xdaforums.com/omni/help/build-sign-user-build-t3449564

If I follow Google recommendations, I must perform a "make dist", which fails.

Can you point me a resource where this is documented ? Or explain me what is the process to generate the nightlies for example ?

Thanks !
[Nexus 4 Original Android Development] kldoc:
You actually need a user-debug build due to the way Omni did the build system.

. build/envsetup.sh

lunch (aosp for now)

make

This for Android 7

For android 6,

. build/envsetup.sh

brunch mako
[Nexus 4 Original Android Development] kldoc:
Here are my personal repos for Android 7, spent 1 hour on those today, mostly merging commits from the AOSP unofficial build that was made, still have a few stuff to fix, but closing in :)

Device tree

Kernel tree

I need to add the kernel build stuff, got somehow scrapped, but lacking the time to re-add tonight ...

All the hard work is mostly from [MENTION=4217103]zaclimon[/MENTION] a great thank to him for sharing his work with the community ! :D

Unofficial AOSP for Nexus 4
[Nexus 4 Original Android Development] gbetous:
Do you mean that nightlies build are userdebug builds ?
[Nexus 4 Original Android Development] kldoc:
Yes they are, only difference is usb debug option activated iirc.

On that matter, signing with your own keys doesn't make much sense for your own builds if you don't share those. This is mostly useful if you want to make sure a signed build won't be altered system wise, rendering support close to impossible.
[Nexus 4 Original Android Development] gbetous:
My issue is to have "Google Play Games" working : it refuses to run on a userdebug build, or on a user build signed with dev keys.
[Nexus 4 Original Android Development] kldoc:
It's working perfectly on nightlies, hard to answer right away what it could be. You're synced with Omni repos ?
[Nexus 4 Original Android Development] mrk2815:
kldoc, thanksfor you dedication to making 7 work for us. i did se the unofficial aosp 7 post today. it looks tlike he's also closing on a stable build in a few days. he has build version 2 of the aosp 7 build and he said that he should have build 3 out in a few days. i will flash on to my nexus 4 . i have two nexus 4 devices here. so i will flash his and then when you have yours done i will flash for helping with both builds.

---------- Post added at 01:58 PM ---------- Previous post was at 01:55 PM ----------

one more thing , with 7. builds will we have to wipe everytime and update or will there be an over the air update mechanism in ther for android 7 as far as updating your builds and testing them when they are available. well.
[Nexus 4 Original Android Development] kldoc:
I won't publish a build until everything is working, mostly to avoid giving again and again the same answers about why this or this is broken. I don't yet have a build, lacking time this week to get one, but I contacted zaclimon, and follow his work to merge his changes with Omni's device tree and kernel tree. The trees will still remain on the AOSP base it was before, just merging in the needed commits.

Main issue is Nexus 4 was built with GCC, and Android 7 moved to clang (actually, some devices already switched to cland on android 6), and it was a known fact that CLANG was breaking sensors on Nexus 4. That's one of the major stuff that remains to solve.

This is why i made my github public, so people wishing to build could actually follow and try on their own, without having people flashing this kind of unstable build without knowing what they're doing or the consequences. ;)
[Nexus 4 Original Android Development] avinashjirapure:
[MENTION=2604804]kldoc[/MENTION]

Thanks buddy for supporting our beloved Nexus 4 ?

Just to update, [MENTION=4217103]zaclimon[/MENTION] have managed to solve sensor issue...

http://xdaforums.com/showthread.php?p=68430719
[Nexus 4 Original Android Development] kldoc:
I read the thread, but nothing published on his github yet, I will have a build by this week end I think, only thing that worries me is i won't have the time to test it :( Might have to publish a test build without being able to test it, and I hate this :(

Things are looking good for Nexus 4, but I think that's my last AOSP port on it to be released in the main supported devices, device is getting too old, will buy one of the new Nexus this year, and I will switch to it for Omni's maintainance (if needed).
[Nexus 4 Original Android Development] kldoc:
A great thank you to [MENTION=4217103]zaclimon[/MENTION] (really can't thank you enough for the work you did here and your kindness answering as much and as fast as you could !) for all his work on Mako, all the pieces are now here to do Omni 7 bringup for Mako.

I won't have the time to merge everything and launch a build before this week end, but i do have the needed commits to make it happen :)

Stay tuned !
[Nexus 4 Original Android Development] zaclimon:
Don't forget that you need to allow execmod on SELinux policies as well as allowing text relocations or otherwise you won't be able to save pictures. Here's the 2 commits that I used for this:

https://github.com/xyyx/android_bionic/commit/038fd2b4b1ad9f43d684f57e5cfe3fba233aa566

https://review.cyanogenmod.org/#/c/158716/

I might redo the patch about bionic since we might not want every device to build libc_pthread on GCC.
[Nexus 4 Original Android Development] mrk2815:
so kldoc, what gaps will we need to flash with your build. I just want to be prepared when you post your build this weekend for testing. also will the set up screen work as well since the set up screen is not working on the unofficial aosp build .
[Nexus 4 Original Android Development] kldoc:
Right now, i have no idea if it will even boot ^^ Omni's team is still working on merging stuff and fixing stuff, don't expect to be able to use this at all, if it boots, if everything works, it will be a proof of concept. But give it at least a month or 2 before having usable builds.
[Nexus 4 Original Android Development] kldoc:
Indeed, bionic patch needs to be device wise, at least for ROMs that have multiple devices, if you know how to do this, then hats down sir :D
[Nexus 4 Original Android Development] zaclimon:
The question remains because we don't know yet the impact of this yet, would it be better to restrict it to device's board or the device itself needs to have a flag? (For example something like BOARD_SENSORS_NO_CLANG)
[Nexus 4 Original Android Development] kldoc:
We won't be able to answer that one without heavy testing, not sure what is feasible for the clang parameter, and requirements will differs from ROM to ROM.