yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] kldoc:
I prefer to tell you ahead, I'm still working on initial build, but I don't have the time to test it if it completes.

Don't hold your breath on Omni 7 for Nexus 4 just yet, i'm really lacking the time to do it as fast as other ROMS, and Omni itself is still on device bringup, trees are pretty much AOSP at the moment, and I simply can't manage to find enough time to fix, include commits and so on, then test my own builds (still have none at the moment).

Doing as fast as I can, but truly no ETA.

Little teaser :p:

OBJCOPY arch/arm/boot/zImage

Kernel: arch/arm/boot/zImage is ready

Spent the day facing issues while building, out of memory errors then out of space ^^'

Fixed those, but i'm lacking a few audio commits to finish this. I won't have the time to work on it tomorrow, but my github is up to date if you can't wait :p

Right now, unless you know what you're doing, building is rather complicated (omni building trees are slowly being integrated).

Then it's mostly AOSP for now, phase is device bringup more than anything, Nexus 4 fall in that category, but I'm really alone on this with Omni, and got too much work to give it more than a few hours a week.

I'm really sorry to delay things, but life is life, and really don't have more time than this on it.

The way I see things, since I need my phone 100% functional every day and don't have the time to manage backups, I won't be able to run my own builds before I get a new device, planning to buy either Sailfish or Marlin.

Most maintainers don't like blind building, and I'm not different.

But ... Admitting that when build will be ok, and admitting that no new commit could change anything, i might publish a non tested build, but that won't be before Omni finishes the initial work on the repos.

At the moment, we still haven't decided whether to start from scratch or merge.

You know as much as I do, asking for patience :)
[Nexus 4 Original Android Development] kldoc:
Omni 7, Mako 1, take 1

[100% 2468/2468] -e Package complete: /home/kldoc/android/omni_ext/out/target/product/mako/omni-7.0-20160906-mako-HOMEMADE.zip

I still have one patch to integrate, but it builds :D

Stay tuned ;)
[Nexus 4 Original Android Development] Thrikiller18:
I think we can expect same camera bug like zaclimon's builds right? Also thanks for supporting mako, it is nice to being able to use a newer android on a 4 years old device.
[Nexus 4 Original Android Development] kldoc:
I'm not sure yet, Omni 7 will soon switch again to snapdragon camera, then selinux config is not done at the moment, build is done, it should boot, won't be able to test that build before this weekend, still have a few things to integrate, I give it at least a good month before having a usable build. My builld is also selinux enabled, mostly to make sure it builds properly, but I won't publish an selinux enabled build before Omni 7 selinux is ready, so it might work better (remains to be seen).

Initial work is done, my build env is ready, and i can easily work on it now. Only lacking factor is time.

One thing though, since Mako's trees are now a real thing, I will have this device to work on when I get my new phone, means i will be able to work on it without risking a day without a phone, which i really can't afford anymore.

My wife also gave me an older android tablet, which will allow me to transfer some apps that i need without risking any loss.

So in the end, things are looking good for Mako on Omni 7.
[Nexus 4 Original Android Development] mrk2815:
cant wait till you of havea build up. also planning on buying either one of the newer devices as well.
[Nexus 4 Original Android Development] Mrkblo:
Regarding the latest nightly, can anyone confirm if Omni 6 Builds have the same camera problem as CM13? ("cannot connect to camera" some minutes after booting up).
[Nexus 4 Original Android Development] mrk2815:
just wondering with Omni 6.0.1 are there going to be security updates for September. I have not seen any for Omni . I was reading up on android central a few days ago that there will be the september security patch and it will be broken down into three levels. I was just wondering if the security patches for September have been sent to the AOSp branch.
[Nexus 4 Original Android Development] kldoc:
You're right, September wasn't actually merged yet, all devs are actively working on 7 bringup, and none had the time to do it ...
[Nexus 4 Original Android Development] mrk2815:
thanks kldoc, i will just wait to see what happens to android 7 for nexus 4.i still want to install omni rom on to the device. i have supported omni and continue to do so. even if i do get a new device i will still be flashing omni builds as i think its the cleanest aosp build with lots of neat features that enhance the AOSP experience.
[Nexus 4 Original Android Development] kldoc:
I'm taking late on Nexus 4 bringup on Omni, didn't have as much time as i wanted to work on it, then, repos are still not ready, given the tree is more or less what [MENTION=4217103]zaclimon[/MENTION] did, it should boot, i just didn't test it yet. But as is it's not usable.

Nexus 4 will eventually get (at least) an unofficial Omni 7 build, somewhere in the future, but I can't make any guarantee toward nightlies. Marshmallow was already at the limit of what Nexus 4 can handle, and meaning it can boot and run it doesn't mean it will be pleasant to use.

I got my old i9100g back, and it got fixed (hardware issue), I might work on it in a far future, as that was my first android phone.

It's mainly a secondary device to keep a working phone while I work on my main phone.

Work is eating a lot more of my free time than i first anticipated, and that's one of the reasons i'm late on Nexus 4.

Project isn't cancelled, just delayed until I can find the time (and the energy) to finalize the work on it.

I don't want to give any ETA because i'm unable to respect those at the moment.

https://github.com/ganadist/device_lge_occam/commit/09409abdcdbe737f07402ff4b77109e9682a2805

That's what's missing from my current work, couldn't find the time to redo that properly, then selinux is partly broken on Omni 7 at the moment, and repos handling itself is partly broken, folks are hard at work on it, but any change i would submit now wouldn't make much sense until everything is working properly on that side. I did prepare my own github for device tree and kernel, but I've got to wait for some commits in the core to be integrated to publish anything. That's where I am now.
[Nexus 4 Original Android Development] berturion:
random shutdown help needed to diagnose

Hello folks,

My phone runs Omin 6 since the beginning of the nightlies and I am very happy with it. Thanks [MENTION=2604804]kldoc[/MENTION].

Since 2 weeks though, my phone shutdown itself for no reason. Sometimes, I have to turn it on 5 to 15 times because it shutdowns just after the sim password screen. My phone is rooted, I use last system less beta supersu, TWRP 3.0.2, Xposed v86, pico OpenGapps 20160903.

So I thought it was related to some apps or my specific installation. To be sure, after backing up everything, I completely erase all with TWRP (cache, system, data, internal memory) and reinstalled Omnirom only. But I faced the same issue.

Now I know that it is not Omnirom's fault because, I face the same issue with last stable Slim6 rom. And it is even worse (shutdowns more often).

I ordered a new battery (I found that it can be the reason) but shipping is very long to Reunion Island so I wanted to know if someone can help me to diagnose precisely what happens.

I would like to know if I can grab logs of the phone and how. I installed alogcat root from F-Droid but I am not sure what to look for and if the logs of a shutdown are available on the next boot...

Can someone can guide me to identify the reason of the shutdowns ?
[Nexus 4 Original Android Development] kldoc:
I'm unfortunately having the same issue, last kmesg should give an answer, but didn't have the time yet to look into it.

Nightlies have been stopped by the way.
[Nexus 4 Original Android Development] schiznik:
Mines been doing that too. Ordered a new front panel, screen & digitiser. Hopefully that will fix it, if not then will be ordering a battery replacement next.
[Nexus 4 Original Android Development] mrk2815:
kldock, how are you doing. the aosp 7 rom is now complete . now we will just be patiently waiting for the Omni commits and for Omni 7 to test on the old nexus 4. which is in pretty good shape. have not had any hick ups what so ever. everything is working flawlessly on aosp 7 and just waiting to test Omni 7 on the nexus 4. I am also going to be buying the new google devices in a month or two.
[Nexus 4 Original Android Development] berturion:
Is the last nightly considered as the last stable omni 6 ?

---------- Post added at 08:39 PM ---------- Previous post was at 08:33 PM ----------

I replaced recently my panel+screen+digitizer because 30% bottom of my previous screen was dead, it didn't respond from touch. This random shutdowns problem came some months after. So I think the problem doesn't come from this. I really hope that replacing the battery will fix this issue. I will report back.

But, not knowing exactly where the problem comes from, maybe replacing the screen will fix your device. I hope so.
[Nexus 4 Original Android Development] kldoc:
Even though Omni is AOSP based, lots of our features needs backporting, and folks have been having issues with some basic repos, I'm waiting to have enough free time to push the last commits device wise before publishing any build. I'm also having a backup issue, I don't have enough free space to run a nand backup. I'm doing as fast as I can, but work is keeping me very busy with very little free time at the moment.

Here is an insight of what's happening, and why it takes time to actually go forward:

https://gerrit.omnirom.org/#/q/status:open++branch:android-7.0

All non device specific commits need to be cherry-picked.
[Nexus 4 Original Android Development] kldoc:
A very early build will be pusblished through the weekend, it's already built, but since I'm finally in vacations, I want to test it before publishing it, lots of stuff should be broken, i set selinux permissive because there's still a lot of work on that side. It won't be an usable build, more a proof of concept, and there won't be a newer build until merge process is done.
[Nexus 4 Original Android Development] kldoc:
I didn't forget you, just got really really busy with work, but here it is.

First (very early) build for Omni 7 on Nexus 4/Mako.

Camera is broken (some stuff to do there), but it boots, not sure how much is broken, then all my trees aren't up to date.

Here is the link for the build, selinux set permissive for now (will change when selinux work is done on Omni)

[URL='http://xdaforums.com/devdb/project/dl/?id=20713']omni-7.0-20161001-mako-HOMEMADE.zip[/URL]

This build comes with ZERO support, no bug reports will be accepted, I already know a lot is broken, as previously announced, this is only a proof of concept, I'll continue the work on Mako when Omni trees are ready to build, they are not at this time.

I share my work mostly to reassure you about Nexus 4 support on Omni, but it comes with no ETA and no guarantee whatsoever towards the future.

You are warned :p
[Nexus 4 Original Android Development] deshmukhrb2000:
:good::good::good:

All the best [MENTION=2604804]kldoc[/MENTION], hope you will not disappoint MAKO.

Keep it up
[Nexus 4 Original Android Development] kldoc:
I know I said no newer build, but I wanted to at least partly fix the camera, it's done, both AOSP and SnapDragon camera are working to take pictures, video recording isn't working yet (need to investigate), selinux is set permissive, I still have a lot of work on that side, and gerrit is broken at the moment (can't merge), so I can't really finish the work just yet.

Build seems to work properly, for those who know what they're doing, be my guest, and flash this build for debugging purpose.

I need detailed logcat with every bug submission, any bug report without a proper logcat will be ignored, i'm lacking the time to reproduce every issue to get those.

I'm not using it yet as a daily driver as I don't have a newer device yet.

Outside of camera video recording issue, i'm not yet aware of anything else broken, if you find errors, please let me know.

omni-7.0-20161003-mako-HOMEMADE.zip

It still is a very early build, but my trees are up to date this time, won't be able to publish anything any newer before Omni's gerrit is fixed (need for selinux commits before I go forward).
[Nexus 4 Original Android Development] kldoc:
Ok, being lucky here, gerrit just got fixed, lots of stuff being merged, updating my own env (a bit outdated), launching a build, and let's see how much got fixed/broken.
[Nexus 4 Original Android Development] kldoc:
Hello folks, updated version:

omni-7.0-20161004-mako-HOMEMADE.zip

Changes: Selinux enabled, latest changes from Omni.

Camera recording is still broken, but it should be the last remaining bug (still being investigated).

Enjoy :)
[Nexus 4 Original Android Development] kldoc:
Given that Omni 7 for Mako has become a reality, I end announcements and support about it here, and just created a new thread for it, Omni 6 has been shutdown in term of nightlies, and unless the need come for urgent patches, there won't be additional support for it.

Thank you for your understanding.

Kldoc
[Nexus 4 Original Android Development] mrk2815:
hello kldoc, how are you doing. where is the thread for omni 7. so i can grab the builds and test for you. i cant wait for omni 7 to be reality. reality.
[Nexus 4 Original Android Development] kldoc:
Have been really busy this fall. change of work and place again, for good this time around, but that has delayed my work on Nexus 4 a lot.

Here is the new thread :p

http://xdaforums.com/nexus-4/orig-development/rom-omni-7-t3473744

I'm planning to switch to it this week, I could care less about video recording, and since 720p is working on Google Camera, what delays me is the headache of backups ^^'

I still have battery leds to reenable that i did disable for the sake of the build, and notification lights are also back, will make an updated build tomorrow with those, but everything should work properly as far as I'm concerned.
[Nexus 4 Original Android Development] justmix4:
Hello kldoc. :)

I'm very happy with Omni6 last nightly, it's very stable and fast as Bolt.

I found Omni6 with November Security Update 6.0.1_r74 and decided to install it.

Everything is installed and work fine, but when I try to set Deity Theme (substratum legacy) and do reboot my N4 falls into bootloop. Strange that security patches affect the theme engine.

This is used kernel, Quanta v20 AOSP with September Security Updates

http://xdaforums.com/nexus-4/development/kernel-sabermod-franco-kernel-r211-t2858561

Is the cause may be Quanta Kernel with older ASB? Last August nightly works well with this kernel.

I wonder if I compile the kernel from sources with the latest ASB, Omni6 from November would work?

I have a nightly backup, but I want to try to solve this problem and maybe learn something.

Cheers, thanks for your work and a Happy Chinese New Year!
[Nexus 4 Original Android Development] kldoc:
Are you rooted ? Latest security update requires latest SuperSU, that's the only thing I can think of.

I didn't test the theme engine honestly, but as far as I can remember, Omni isn't compatible with themes ?
[Nexus 4 Original Android Development] justmix4:
Yes, I'm rooted by SuperSU 2.78. It's weird, because Deity and other themes on Omni nightly 30.08.2016 works without problems so Omni must be compatible with this theme.

I suspect that the fault of the kernel. In free time I try to compile the kernel with the latest ASB, maybe this will help.

WysÅ‚ane z Tapatalka
[Nexus 4 Original Android Development] parkourz:
well, nevermind... new Pokemon GO security sucks :(
[Nexus 4 Original Android Development] berturion:
Hello [MENTION=2604804]kldoc[/MENTION], did you find a fix for this or do you still have this issue ?

I replaced the battery twice with no effect on this... :(
[Nexus 4 Original Android Development] kldoc:
Unfortunately, I don't have an answer for this, device is old, might be an hardware issue. I'm not using my Nexus 4 anymore, I kinda stopped dev on Nexus 4, I am maintaining OnePlus 3 and 3t.
[Nexus 4 Original Android Development] berturion:
Ok. I understand. Thank you for your answer. I think I will give up on this random shutdown issue.
[Nexus 4 Original Android Development] justmix4:
I just wanted to say that I know the reason for bootloops with the latest release of OmniRom 6 named "SECURITY_RELEASE"

Substratum Legacy description from Play Store:

So if someone wants to use themes I suggest to use last nightly from August, everything will work and you can pass SafetyNet. :)
[Nexus 4 Original Android Development] berturion:
I finally bought a usb charge connector that could resolve this issue, I hope. I am waiting the delivery and will report back. As I live in reunion island, shipping from china takes 2 months. So the answer will take time...
[Nexus 4 Original Android Development] I.P:
Problem is I have no new app since 5.1, I only reinstalled them after a factory reset.

Anyway if I'm the only one with this problem it means it comes from my phone and not from Omnirom. I'll try to figure out what's happening.
[Nexus 4 Original Android Development] kldoc:
Nope, I didn't use the commits for it, as Nexus 4 doesn't support it.

I was finding the battery to actually behave better than on Lollipop ... I'm still runing 11/9 build, and it does behave really nicely.
[Nexus 4 Original Android Development] kldoc:
There are no new apps, things that changed are in the settings, and better battery stats won't give you much since cpufreq_stats doesn't exist in this kernel :p

I've seen a few attempts, but i'm waiting to see if someone ports a "good" implementation to actually have something usable.

Right now i'm working on r26 which has big problems with audio, hard to find solutions, as commits comes from msm_common or flo (most of them), and flo hasn't received r26 sources yet, which means i don't have a device tree/kernel tree to look at to find out what could work, only some generic commit from msm_common.
[Nexus 4 Original Android Development] kldoc:
I hope you are ok, this attack really shocked me, hope you, your friends and family are safe !
[Nexus 4 Original Android Development] I.P:
I'm far from Paris and I have no relatives there, anyway it was difficult to get to sleep last night, very shocking indeed.
[Nexus 4 Original Android Development] I.P:
Hi,

I've seen nothing weird regarding wakelocks, still battery life is awful... I keep on trying to understand what's happening.
[Nexus 4 Original Android Development] brandonabandon:
exactly why i compiled personally with justarchi opts, and uber toolchains. running non optimized builds, i suggest switch governor to powersave and install a battery saving app.
[Nexus 4 Original Android Development] kldoc:
Really odd, I'm actually have a lot better screen on time than before, and battery last longer. Till the point I actually don't cut wifi anymore.

I can't really work on it at the moment though. I'm having a hard time to fix r26, in call audio is broken, and sources are not yet available for msm kernel, flo and hammerhead. I'm trying to isolate what changes in r26 triggers that, but failing so far.
[Nexus 4 Original Android Development] kldoc:
Hi folks, I have good news, I managed to fix in-call audio on Omni 6 r26, since the ROM needs some testing, I publish that r26 build.

omni-6.0-20151115-mako-HOMEMADE.zip

I'm going to have more time to work on other issues, but I'm also going to need sources from flo and hammerhead to do so.

Dex2oat force no-swap is included, should allow a faster boot, and solve an issue with facebook app where the app constantly rebuilds at reboot.

Have fun with OmniROM !
[Nexus 4 Original Android Development] saenanme:
One issue: the stock browser fc when I try to download any file.

Any ideas of how to fix it?

Regards
[Nexus 4 Original Android Development] kldoc:
Yes, I checked in the app properties, it actually has storage permission disabled, since it doesn't have access for it, it force close.

Setting => apps => browser => permissions: just enable the switch :)
[Nexus 4 Original Android Development] saenanme:
Simple. It seems that we need to check deeply the android M changes.

Regards
[Nexus 4 Original Android Development] kldoc:
Indeed, I didn't have much time myself to play with it, spending more time to bring up and fix things than actually use it lol ^^

On that matter, forgot to mention, but I also updated adreno blobs to latest flo's.

Rom wise, a lot of things will eventually get fixed or modified, we're nearing nightlies on a few devices, including Nexus 4, but needs testing, and I really thank you all for your feedback that is quite helpful :)
[Nexus 4 Original Android Development] I.P:
As I couldn't find anything I gave a try to another kernel (hells core) and the result does not need any comment :

[IMG="pouet"]https://lh3.googleusercontent.com/fqlHD3AsjrITuNH3ur8vgbmlyi0KggsP0PugG4Py_XInHgxp72il5oOHGmfDpvpIoMktMVcpRbOcPli8fyAWV1CaopOzQTG8YdDWkKKUhgFnqEumgZGSL-JJisFVKWIpg5BD6BJrRXlHFEZZAU3zg5OUu4A5VIAgT845WR_5LVU35usugQcJzmKkZx-6gRu79RvckPNmX_-5uJ9U9ENzHby8xtDeiD4m2f0L64K4IIUfRT1tss7u9G9dAN-GIQP1CGh-uk7Qd1bEZf_ImjPylnE7Bb6-RJ9Vk-I-qz5a6MDvCSIdHpsimmldihN3Vxs5OHeZ74FZz95LfYBuFI6GXvpr2vFX4wGLGaMVJuSOf4Ma2bAZZpV2CUVbrJUqx1wTQCBByxzJylSv-pC4NplqIc_wYvIY96TSZmDAo2CF-teHKtqmo7yIRdDIKRH1M4tacpQma52m6_QyifyAJqMPJPZ8SOSQKqeLqWl5V1ATHqAKCEx2waiWqAlYTFjfBQNllVJZMuP85AOZPKZQW3uap14wq8cD3h4Wc6j9wI1RC8g=w616-h1024-no[/IMG]

Sorry I can't give you any more input to try to solve this problem but ask me if you need anything.
[Nexus 4 Original Android Development] kldoc:
Don't rely on battery stats, those are meaningless as is, what matters is real usage. Battery stats always needed time to build-up. Give it a few days, I actually can stand 1 day with my phone. If you wish to use another kernel, you are free to do so, but I actually can't work on battery stats right now, especially since this is an app/widget issue. Lots of apps aren't Android 6 ready.
[Nexus 4 Original Android Development] I.P:
Hi

I'm only using these screenshots as a way to give you an idea of the battery drain I had, not for serious debugging. Anyway before my phone's battery was depleting really fast, I had to charge it in the middle of the afternoon, and that was not a widget issue the battery was down for real.

Today it went until 11pm with this kernel, don't ask me how or why but the difference is noticeable.
[Nexus 4 Original Android Development] kldoc:
Here is my own battery stats, so you can see by yourself there's obviously a problem with your setup ... This is with the kernel inside latest Omni 6 build, I didn't change anything ...

[IMG="battery stats"]http://i.imgur.com/bQBjfRU.png[/IMG]
[Nexus 4 Original Android Development] I.P:
Indeed there must be something wrong, but I checked everything I could think of and it was a clean install with a factory reset.

I'll wait for the next build and see if something changes.
[Nexus 4 Original Android Development] kldoc:
You can try cleanmaster which is very efficient at detecting what apps run in background, and eventually block those you don't need permanently running.
[Nexus 4 Original Android Development] I.P:
I'll give it a try, thanks.
[Nexus 4 Original Android Development] kldoc:
New build, only one change, add dex2oat speed filter (speed up initial boot and attempt to fix facebook app cache regeneration at reboot).

I don't cherry pick commit from apps or frameworks, to ensure maximum stability, but a few nice things are coming, volume unlinking etc ...

omni-6.0-20151119-mako-HOMEMADE.zip
[Nexus 4 Original Android Development] TheeWolf:
Can you say if ambient display is in the build, and if not, when it will be? That's the most crucial thing for me.

Thanks!