yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] wrongway213:
OmniROM has not rolled out official Lollipop nightlies yet, but these builds are coming from the official maintainer for OmniROM for the Nexus 6. Omni is a huge ROM and serves many devices - obviously one person is not handing thirty+ (guess) threads and developing it all alone for all devices. However, Omni is a collaborative effort, so to say jakew02 is developing it on his own would be inaccurate - however, he is, for all intents and purposes, the developer, especially in this thread.. Anyway, a maintainer build = an unofficial build that was built by the official maintainer. So this is as "official" as an unofficial build gets, for lack of better words.
[Nexus 6  Original Android Development] Nickchapstick:
i know what omni rom is. i just didnt know what a maintainer was and i appreciate you clearing that up.
[Nexus 6  Original Android Development] gamewarden234:
Ha. That was a very eloquent simple explanation of this scenario.
[Nexus 6  Original Android Development] psychomaniac189:
Which gaps should I use? The one dude retired
[Nexus 6  Original Android Development] Megaflop666:
Slim gapps works
[Nexus 6  Original Android Development] Gandalf:
OP updated w/ build dated 03-26 as well as a link to dhacker29's gapps
[Nexus 6  Original Android Development] mkcbbusiness:
Hi jake, I was wondering if there are any tasks that I can help with that will make putting out this rom easier? I'm not a developer but I have some Linux skills.
[Nexus 6  Original Android Development] Bingoig11:
Download in progress.

Hopefully sounds issues will be resolved :D
[Nexus 6  Original Android Development] Gandalf:
What did you have in mind?

I haven't received any calls so I haven't tested incoming call audio but outgoing works fine.
[Nexus 6  Original Android Development] Bingoig11:
I thought about mic/speaker issues I had.

And I can confirm that after dirty flash it is resolved :)

Great job!
[Nexus 6  Original Android Development] Gandalf:
Quoted those in the wrong order. "What did you have in mind" was directed to you
[Nexus 6  Original Android Development] gparmar76:
I'm assuming your talking about Banks Gapps...he's still making them...its on the Euroskank site that Rastapop is on...just google Banks Gapps and you'll see it in the search results.
[Nexus 6  Original Android Development] wrongway213:
He's talking about TKruzze, he retired from making PA gapps.
[Nexus 6  Original Android Development] mkcbbusiness:
I guess I was looking for something simple someone learning could easily figure out how to do that might save you some time. If your making modifications to the code.
[Nexus 6  Original Android Development] gparmar76:
Oh, didn't realize he left PA...I still think Banks Gapps are the best..small package with only the necessities.
[Nexus 6  Original Android Development] Gandalf:
purely personal preference, however for the time-being I have linked to dhacker's cm-gapps. They are comparable to Tkruzze's modular package, which is the bare necessities, and then a small amount of other commonly used Google apps.

I have also added a link in the OP to banks gapps. This package would be comparable to the "micro" or "pico" package from Tkruzze (not exactly sure just how slim the banks one is as I have not used it lately).
[Nexus 6  Original Android Development] wrongway213:
Banks is just Play Store, Google app and Facelock
[Nexus 6  Original Android Development] eng.stk:
Works good, audio is fine on GSM network.

I just noticed interfacr separator is empty, can you add some simple cobtrils like quick oull from right, center clock and battery percentage text?

Thanks mate
[Nexus 6  Original Android Development] Gandalf:
Fully aware of this. It was added recently but nothing is ready for that section yet ;)

Outstanding. My replacement device is now falling apart (the back plate is coming off, like it wasn't glued down properly or something). I swear, I have the worst luck with phones.
[Nexus 6  Original Android Development] Bingoig11:
Had a bad experience with my N5...After 7 days, I broke the screen. When I bought the N6 I bought a cover and screen protection on day 1 :D Guess what? It never has fallen apart... :D
[Nexus 6  Original Android Development] Gandalf:
going to be implementing a replacement for mpdecision soon :good: it is being ported to the 3.10 kernel currently.

Also, is anyone experiencing APN issues (resetting, causing service/signal drops)?

Also, I will be implementing power profiles and some other kernel tweaks in the coming days
[Nexus 6  Original Android Development] Bingoig11:
Experienced some APN issues (signal drops, H instead of 4G) but I thought it was because I recently flashed my radio with 95R. I flashed it because with the stock one and this latest build I experienced a lot of signal drops and was most of the time it was in H instead of 4G. With 95R it's better but not as good as older builds you published.
[Nexus 6  Original Android Development] Gandalf:
ok needed to know it wasn't just me. I'll get it fixed. Working on the kernel stuff now

I WOULD LIKE SOME TESTERS FOR THE NEW CPUFREQ/CPUQUIET STUFF I'VE BEEN WORKING ON. EVERYTHING SEEMS TO BE WORKING FINE FOR ME, BUT I WOULD LIKE SOME ADDITIONAL TESTING

The following commits are included in this TEST build:

android_device_moto_shamu

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

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

android_kernel_moto_shamu

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

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

cpuquiet is a replacement for mpdecision. I brought this over with much help from [MENTION=4683552]maxwen[/MENTION], thanks! :highfive:

As you can see:

mpdecision is disabled in the ramdisk now with 13170 and is replaced with cpuquiet.

The ramdisk will no longer force interactive cpu governor on boot anymore.

I currently have the default cpu governor set to ondemand but may end up changing this to ?interactive?

Basically what's happening is:

The cores are now unified, all cores will maintain the same governor

All 4 cores are not kept on at all times anymore, and will fire up when needed

This should increase battery life, since we DON'T have all 4 cores on all the time, as well as increase performance.

You MUST perform a FULL WIPE:

This includes wiping:

System

Data

Cache

Dalvik

DO NOT CHANGE ANY KERNEL SETTINGS WHATSOEVER

Enable CPU Info Overlays in Settings > Developer Options.

This will allow you to watch the cores and see what governor is applied to them, as well as their individual frequencies

Give it a good rigorous stress test:

Flick through long menus

Play hardware-intensive games

Whatever you want to give it a good run

GIVE ME FEEDBACK!!!!!

https://www.androidfilehost.com/?fid=95916177934552496

I highly recommend installing supersu for this as well

KEEP IN MIND that omni does not have f2fs support merged in by default, so you must have your partitions formatted as ext4. I may or may not consider adding f2fs support in the next few days depending on popular demand.

THIS BUILD HAS FULL f2fs SUPPORT
[Nexus 6  Original Android Development] warfenix:
Been playing around with new build. It seems to stutter and open menus a bit slow. Played a few games. It would freeze and then reboot. Same thing while browsing the play store it would freeze and then reboot.
[Nexus 6  Original Android Development] Gandalf:
OK, I'm going to revert one commit I believe is the cause of that and throw another one up for you guys after classes today. Try going to Performance and setting the governor to interactive and tick set on boot then reboot
[Nexus 6  Original Android Development] vergilbt:
Sorry, the same for me... reboots spontaneous and all was laggy...

But the former version was ?... Pls go ahead on this way
[Nexus 6  Original Android Development] manup456:
[MENTION=3878813]jakew02[/MENTION]

Is the 4/8 build the one with the fixed commits?
[Nexus 6  Original Android Development] Gandalf:
try this one https://www.androidfilehost.com/?fid=95916177934553490 [MENTION=1407738]manup456[/MENTION]
[Nexus 6  Original Android Development] manup456:
Downloading now thanks for the update. ?
[Nexus 6  Original Android Development] manup456:
[MENTION=3878813]jakew02[/MENTION]

Question the interface option is blank in settings is that because it's coming soon or did I just have a bad flash?
[Nexus 6  Original Android Development] Gandalf:
coming soon ;)

I'm idling at 0.24%/hr with the cpuquiet changes :good:
[Nexus 6  Original Android Development] Bingoig11:
Can I dirty flash the 0410 version over my 0326? Or should I full wipe as you requested for the test build you published earlier?
[Nexus 6  Original Android Development] Gandalf:
You can try to dirty flash but if you start having problems just do a clean one.
[Nexus 6  Original Android Development] omvir:
Jake, I pulled the boot.img from this ROM and flashed it over an unofficial CM 12.1 ROM, and it just bootloops. Would you have any idea why this might be?
[Nexus 6  Original Android Development] wrongway213:
Based on all custom kernels other than Hydra (our only hybrid built for CM and AOSP) not booting with Temasek's unofficial CM 12.1 initial release, I am assuming missing CAF commits from CM 12.1 would be the cause. See my post here and the preceding several pages of discussion for more information as to why this is my educated guess. http://xdaforums.com/showpost.php?p=60014627&postcount=1966 Hope this helps
[Nexus 6  Original Android Development] Gandalf:
Not surprising. CM does not have the device tree commits for cpuquiet. You're on your own with this one since this is the omni thread :highfive:

Actually there is no CAF merged by CM onto their kernel nor in the Omni kernel. Its most likely because I made changes to the ramdisk for cpuquiet which other Roms don't have (like CM).

It is a pretty awful idea to rip a boot.img from one ROM and try to use it with another ROM though
[Nexus 6  Original Android Development] Bingoig11:
Dirty flashed 0410 release on top of 0326 seems to be running smooth and fast :)

Great job as usual :D
[Nexus 6  Original Android Development] resynx:
Flashed this ROM tonight and it's running quick! Just wanted to say thank you for this :)
[Nexus 6  Original Android Development] Bingoig11:
Just a question that may be related to dirty flash. When in charge I noticed the device is much hotter than usual. Anyone else noticed that?
[Nexus 6  Original Android Development] Gandalf:
The device is supposed to be a little hotter while charging, that happens with every device. I haven't noticed this personally but I just plugged in at 30% and will monitor the temperature.

We are not going to support kexec in the kernel after a decision was made by the core developers, a decision i fully support.

We will maintain the kcal from savoca however, since most users need to calibrate their displays, we just will not incorporate any type of app interface to control it, that will be on the users to handle, but the kernel will support it.

20150423

default governor switched to ondemand

updates to KCAL from [MENTION=4316709]savoca[/MENTION]

kexec-hardboot MULTIROM support is REMOVED

AOSP Browser history page added back

expanding volume panel

https://www.androidfilehost.com/?fid=96042739161892555
[Nexus 6  Original Android Development] resynx:
Thanks for the update! :D
[Nexus 6  Original Android Development] Lancez:
Is there a change log and feature list? first time user. TIA
[Nexus 6  Original Android Development] Gandalf:
You can look at the Merged section of Gerrit but until nightlies start I will give a general changelog of noticeable changes with each build

During my testing with cpuquiet, I average ~ 0.2%/hr overnight and a little higher during the day, but that is expected.
[Nexus 6  Original Android Development] HaRdC0r3:
And just for clarification this has your enhanced kernel or should I flash the last boot image?
[Nexus 6  Original Android Development] warfenix:
I tried flashing this. Complete wipe. Fresh install but it just hangs at omni bootscreen? Anyone else. Good DL to md5 match.
[Nexus 6  Original Android Development] Bingoig11:
Dirty flash on 0410, everything's fine, smooth and fast :)
[Nexus 6  Original Android Development] omvir:
I'm having trouble deciding between omni, CM, or waiting for PA

??
[Nexus 6  Original Android Development] Gandalf:
Layers support is now being actively worked on. No promises as to whether it will be merged, but it is being worked on.

It seems to take significantly longer than other device to boot up, but it will boot. If it appears to be stuck in a boot loop (more than 5-7 minutes at the OmniROM boot animation) then I'll need you to get me logs.

No, this has the kernel that is at https://github.com/omnirom/android_kernel_moto_shamu/commits/android-5.1

I discontinued my "enhanced kernel" because it was ultimately completely and utterly pointless and becoming a waste of time. Everything that was in mine was elsewhere, so I am just keeping the aosp source up to date with the latest 3.10.x Linux kernel for others to reference/clone/fork

Which is the "stock" kernel from the AOSP source as well as several things:

CPUQuiet: core and scaling management - * this replaces mpdecision

KCAL display calibration from [MENTION=4316709]savoca[/MENTION]

futex security patch

ondemand is the default governor

It only takes 5 minutes to make a backup and flash something, nothing is holding you back from trying all of the ROMs you are interested in :good:
[Nexus 6  Original Android Development] omvir:
Hahaha, you're right. I'll do that soon! I'm really interested in the CPUquiet.
[Nexus 6  Original Android Development] Gandalf:
That's exactly what it is. We're not supporting f2fs in the kernel. As maxwen said: "it's about as useless as a pink elephant".

I would guess that you can probably just flash a custom kernel with f2fs support but I can't rightfully say it will work alright due to cpuquiet stuff in the device.

You can certainly try it, worse case is that you'll just remain in a bootloop. (this is why f2fs support on devices that don't NEED it, or ship with it, is pretty pointless.
[Nexus 6  Original Android Development] Gandalf:
There's a lot of information regarding f2fs and Nexus 6 around here, just search for it. The "speed" differences in using f2fs over ext4 are minimal at best and in reality are probably not even noticeable. I never noticed a difference so I don't use it.
[Nexus 6  Original Android Development] HaRdC0r3:
does the kernel force encryption?
[Nexus 6  Original Android Development] warfenix:
Sorry to keep bugging. I did a Google search but couldn't find the right answer. The calendar app keeps asking for me to sign in. Is there a fix for that?
[Nexus 6  Original Android Development] Gandalf:
AOSP Calendar, or Google Calendar?

That's a Gapps issue, not a ROM issue.
[Nexus 6  Original Android Development] warfenix:
Aosp
[Nexus 6  Original Android Development] vergilbt:
Why did you remove kexec support?
[Nexus 6  Original Android Development] wrongway213:
It's in the post you quoted.. the decision was made by Omni's core developer's, OP did not choose to remove kexec support himself, he just supports the decision Omni made as a whole.
[Nexus 6  Original Android Development] vergilbt:
THX, didnt read all...My fault
[Nexus 6  Original Android Development] Shawn5162:
I heard this ROM had DSP manager in it...Could someone upload the .apk of it

Thanks
[Nexus 6  Original Android Development] warfenix:
xdaforums.com/google-nexus-5/themes-apps/mod-cm-dspmanager-universal-zip-t2939933 google works wonders lol
[Nexus 6  Original Android Development] Bingoig11:
Experienced some soft reboots using latest release. As I didn't performed clean install for a while, I performed a fresh clean install (format everything, system, data etc.)

Experienced 1 soft reboot then.

Will try to generate logs but as it seems to be random, it will be quite difficult.

Jake, do you need specific logs or a logcat is OK?
[Nexus 6  Original Android Development] Gandalf:
Try changing your governor to interactive and see if that helps.

Also, check the link in my signature, that will describe the different types of logs, how to get them, and when they are most appropriate.

Random reboots would best be checked with a last_kmsg
[Nexus 6  Original Android Development] Bingoig11:
Changed governor ans will monitor.

Had a look, no last_kmsg available so I'll check if reboots happen again

Great howto by the way ;)

Edit: reboot happened, no last_kmsg available

Edit2: governor setting doesn't stick after reboot even with Apply on startup checked, back to on demand.

Edit3: back to 0410 release, more stable.
[Nexus 6  Original Android Development] Gandalf:
here is a test that reverts back to using interactive as the default governor, but still uses cpuquiet. I just tested it out and did a few intensive tasks and it was fine, let me know:

https://www.androidfilehost.com/?fid=23991606952592878

new build in OP 20150504
[Nexus 6  Original Android Development] resynx:
Oh cool, battery percent :D Thanks for the update.
[Nexus 6  Original Android Development] Gandalf:
I love the horizontal battery icon :highfive:
[Nexus 6  Original Android Development] resynx:
I'm only using the percentage myself :D
[Nexus 6  Original Android Development] ilpolpi65:
20150504

No boot with multirom [emoji17]
[Nexus 6  Original Android Development] tomzefi:
Have you looked at the size of the file? I am certain its an update. I tried flashing it alone and realized the size. 34 mb
[Nexus 6  Original Android Development] resynx:
AFH reported the wrong size. It's the normal 340mb.
[Nexus 6  Original Android Development] tomzefi:
Oh I kept getting google screen boot loop

---------- Post added at 12:01 PM ---------- Previous post was at 12:00 PM ----------

Does the ROM have rro support?
[Nexus 6  Original Android Development] manup456:
[MENTION=3878813]Gandalf[/MENTION] the white great ROM very stable and smooth. ?
[Nexus 6  Original Android Development] Gandalf:
As stated in the OP, right next to the download link that was clearly not read, AFH reported the incorrect file size. Just download it and you will see that you are actually downloading a 340 MB file, not 39.4.

No, as stated before, MultiROM was removed.

Failed to boot? Probably due to f2fs. Don't use f2fs

RRO - no. Entropy is working on a theming system that will allow the use of CM Themes as well. Still in planning/theory phase, don't expect it in the immediate future

More info can be found here: http://xdaforums.com/omni/development/planning-theme-t3096423

Every one of these questions has been answered in the thread, please search and read the OP before asking common questions
[Nexus 6  Original Android Development] ilpolpi65:
Sorry I didn't see....thanks for the explanation
[Nexus 6  Original Android Development] Gandalf:
Now, that's not saying you can't find a custom kernel that has multirom support, flash it, and use that. I just won't be able to debug any issues that you may encounter
[Nexus 6  Original Android Development] tomzefi:
:thumbup:
[Nexus 6  Original Android Development] manup456:
[MENTION=3878813]Gandalf[/MENTION] Question why are these maintainer builds and not officials. I have been on the latest version for a few days and everything is super solid.
[Nexus 6  Original Android Development] wrongway213:
Gandalf is the official Omni maintainer for Shamu, but until Omni rollout for nightlies starts for all devices, maintainers who have their builds for their respective devices ready to go are free to build and upload as Gandalf has for users to use. Check Omni Wiki if you want more information on devices/maintainers and such.
[Nexus 6  Original Android Development] jonzey231:
Any idea if multiwindow is going to be implemented? It was always one of my favorite features of Omni.
[Nexus 6  Original Android Development] micmars:
Check post 71...
[Nexus 6  Original Android Development] jonzey231:
Thanks man, I appreciate that.
[Nexus 6  Original Android Development] manup456:
[MENTION=3878813]Gandalf[/MENTION]

Not sure if anyone has mentioned or provided a logcat for this but aosp keyboard swipe force closes keyboard every time. Here is a logcat and I shortened it but believe the issue can be seen.

Link: http://pastebin.com/wGPD2ZWt
[Nexus 6  Original Android Development] Gandalf:
thanks, I'll take a look

I'm not seeing this . AOSP keyboard is working fine for me. I believe Gapps packages flash Swype libraries, so possibly your Gapps package conflicted. I used Banks minimal with no issues.
[Nexus 6  Original Android Development] Bingoig11:
Just tried to install 0504 release and had a Google logo loop.

As TWRP is not up to date, going to try again after updating TWRP.

Update: After updating TWRP to the latest version, still got the problem. Performed several tests to know if the ROM is the issue and it is.

Tried: Latest ROM + Latest Banks gapps (dynamic): Google Loop

Latest ROM + older Banks gapps package (04-21): Google Loop

0423 ROM + latest Banks: OK

Is there any debug I can perform to find the root cause as the issue is occuring on the Google boot logo so during a very early stage in the boot process?
[Nexus 6  Original Android Development] warfenix:
Well first make sure md5 match. I had this problem before my issue was that I was using f2fs. If you formatted any of your data/cache/system to f2fs. U need to format it back to ext4.

Also make sure you back up and whatever as it erases the internal card i believe.
[Nexus 6  Original Android Development] Gandalf:
Sounds like you are formatted to f2fs
[Nexus 6  Original Android Development] Zedonite:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,context=u:object_r:firmware_file:s0,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/mdm1m9kefs3 /fsg ext4 ro,context=u:object_r:fsg_file:s0,nosuid,nodev,relatime 0 0
/dev/block/dm-0 /data ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered 0 0

Had the same problem with hanging Google logo. MD5 matched. Booted after flashing boot.img from previous build.
[Nexus 6  Original Android Development] manup456:
Yeah if you flash the latest version on a fresh wipe it will bootloop. I had issues clean flashing, but ended up getting it just not sure what I did. I believe I flashed the previous version and then dirty flashed the latest.
[Nexus 6  Original Android Development] Gandalf:
Ok,. I just downloaded and flashed CLEAN from the OP and I can confirm this..

Not entirely sure what is going on, but I'm certain a bad upload to AFH is to blame, as I am running the same build that I uploaded (Although, mine didn't go through servers) I'll rebuild right now.
[Nexus 6  Original Android Development] Bingoig11:
Using Omni since the very beginning on N6 and never formatted any partition with f2fs.

Update: Just checked partitions types while running the 0423 version dirty flashed on top of the latest that was bootlooping, all ext4.

Going to check the hash
[Nexus 6  Original Android Development] manup456:
He is already aware that it is and issue and building a new one out.
[Nexus 6  Original Android Development] Gandalf:
I started the build before I left for work, it will be posted when I get home around midnight EST.
[Nexus 6  Original Android Development] manup456:
[MENTION=3878813]Gandalf[/MENTION]

I know you had work but is it uploaded. I appreciate your work and not rushing just want to fresh flash this.
[Nexus 6  Original Android Development] Gandalf:
Yea I need to look at something that may have caused it, that's why I didn't post anything. I'll check another build after work tonight, its the kernel since the no boot is a kernel panic

It's not the kernel, confirmed when I rolled back all changes made and used the kernel stock from AOSP source. I am testing the vendor now, but I believe that there was a commit or merge made elsewhere that is causing this that is not specifically a shamu issue.