yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Tasssadar:
Shamu's kernel just straight up panics when CONFIG_CPU_FREQ_DEFAULT_GOV_INTERACTIVE is set. Something is wrong with it's initialization when it's default. They use performance as the default in AOSP, so nobody noticed, I guess. Don't really care enough to look for a proper fix.
[Nexus 6  Original Android Development] Gandalf:
I'm not entirely sure that's the issue, although its not out of the question. I've reverted those commits, and even gone as far as just using the stock kernel and vendor (and reverting the appropriate device tree commits) per AOSP and still wouldn't boot. I have an exam right now but I will look around more when I get home.
[Nexus 6  Original Android Development] nizammoidu:
I found what we missed , it was init :)

https://gerrit.omnirom.org/#/c/13726/
[Nexus 6  Original Android Development] Gandalf:
great find. it's been merged. i'll post an up-to-date build today.

op updated with build dated 0521
[Nexus 6  Original Android Development] manup456:
You do anything with the kernel on this release?
[Nexus 6  Original Android Development] Gandalf:
nothing besides rolling back to ondemand as default.

check gerrit for other changes
[Nexus 6  Original Android Development] omvir:
I got a random reboot on the latest build, all stock(also a clean flash). I've got logs:

https://www.dropbox.com/s/nyuc0jwjh71ez8t/console-ramoops?dl=0

https://www.dropbox.com/s/a452bopl6ypnr21/dmesg-ramoops-0?dl=0
[Nexus 6  Original Android Development] manup456:
I ask because I was getting weird reboots and figured it may be kernel related, so I flashed Elite kernel to see and they are no longer happening.

If you need I can flash back and pull a dmesg log for you when it happens.
[Nexus 6  Original Android Development] Gandalf:
manually change your governor to "interactive" for now. I'll fix it tomorrow if I have time.
[Nexus 6  Original Android Development] omvir:
Wait.. I think I remember changing it to interactive... Or not. Does the error point to the ondemand governor?
[Nexus 6  Original Android Development] Zedonite:
One random reboot with -interactive
[Nexus 6  Original Android Development] Gandalf:
I should have time after class to push another build. I'm going to need to take another look because there have not been many changes to the kernel, and none regarding cpuquiet or any of these related things, so why there are now issues, I do not know.
[Nexus 6  Original Android Development] nizammoidu:
just a dump question to those who are experiencing random reboot , do you have any bluetooth device connected ( I do have wear device ) ?
[Nexus 6  Original Android Development] Zedonite:
Yeah, using Wear. Sometimes random reboot, not much.
[Nexus 6  Original Android Development] Bingoig11:
Had random reboots without any BT or Wear or anything else. After reverting to 0410 build, no more reboots (had it with 0423 build also)
[Nexus 6  Original Android Development] Gandalf:
Fully aware of this and it will be fixed as soon as I have time. Cpuquiet is not playing nice anymore for some reason. I'm quiet tired of random things breaking when no changes have been made to the device.
[Nexus 6  Original Android Development] manup456:
Are you going to remove the link for the time being since the ROM is sending people into random reboots? I use a different kernel for now but people are going to continue to report the same issue until fixed.
[Nexus 6  Original Android Development] nizammoidu:
reverting cpu quiet https://github.com/omnirom/android_kernel_moto_shamu/commit/002cebe8ec0f77666e64b4591703a37f2c0cf8a6 didnt fix. reboot after 11h 13m :(
[Nexus 6  Original Android Development] Gandalf:
just reverting it will not fix the issue, nor is that the proper way to revert cpuquiet. cpuquiet is an mpdecision replacement, so you would have needed to re-enable mpdecision from the ramdisk as well.

again, i know about this and I'm going to fix it as soon as I have time

stock core management (mpdecision) http://xdaforums.com/devdb/project/dl/?id=12632
[Nexus 6  Original Android Development] Bingoig11:
Can't get Google Now launcher as my default launcher. Installed it and removed default behavior from the app settings in Launcher 3 but it comes back to Launcher 3 without asking which launcher I want to use.

Any idea?
[Nexus 6  Original Android Development] Gandalf:
I never use Google Now Launcher, so I haven't experienced this (Nova guy, myself) but I'll look after I get the new stuff merged, which I'm doing now.

update: I will be uploading a new build today. I just finished updating the vendor to LMY47Z.

The next build will have LYZ28E binaries

Update: I need a tester from Vzw or T-Mobile for VoLTE (isn't provisioned for ATT yet) using the build I just uploaded

Edit: New build uploaded with LMY47Z vendor + updated liblights for working battery and notification LED, and whatever else has been merged since the last build on 5/26
[Nexus 6  Original Android Development] Toneman07:
Sooooooooo this is what took you away from the tablet. Good to see you on another device I own haha if no one else gets to the volte testing will tomorrow for you < tmobile
[Nexus 6  Original Android Development] Blaiser47:
VoLTE in verizon works! I had to go into the special dialer setting and turn on the volte provision, which was sort of stuck (had to tap multiple times, toggle radio, etc, but eventually went on, and then option in cellular networks showed up. Turned that on an voila, it works!! Mind sharing the changes you made to get this going with [MENTION=2033478]Yank555[/MENTION] so he can get it going on slim?
[Nexus 6  Original Android Development] Gandalf:
If slim is AOSP based it should work as long as the vendor binaries and frameworks are there and deodexed. If its CAF based like CM then he'll need a specific change per CM's shamu tree.

You probably don't have to mash the toggle multiple times, but be patient and give it a few seconds. It has to read your Sim card to see if volte is provisioned
[Nexus 6  Original Android Development] Blaiser47:
Awesome thanks for the info!
[Nexus 6  Original Android Development] TonyStark R.I.P.:
Why is this version so old?

Where is Android M?
[Nexus 6  Original Android Development] Gandalf:
New build in OP with LYZ28E binaries, only at AFH mirror right now (having issues with XDA hosting...)

:crying:
[Nexus 6  Original Android Development] TonyStark R.I.P.:
Downloading now :good:
[Nexus 6  Original Android Development] noonecanhide:
Should i flash the corresponding modem before?
[Nexus 6  Original Android Development] Gandalf:
I am using the bootloader and radio from LYZ28E with no problems.

I'm running a build with tap to wake enabled but I want to see how it affects battery first before submitting it
[Nexus 6  Original Android Development] Bingoig11:
Downloaded and Installed latest update, working great so far!

Thanks for your great work!
[Nexus 6  Original Android Development] noonecanhide:
I had to switch back to the build from 20150526 after i lost data connection with the current build and LYZ28E. Telephony was fine, but i couldn't access the internet (network symbol had exclamation mark). i tried to fix that with the following things:

- reboot

- APN reset

- delete all APNs and entering a new one manually

- downgrade to LMY47D (i had this one before updating to LYZ28E)

- APN reset

After dirtyflashing to the 26/05 build and LMY47D everything was fine again. Mobile network was fine, my other phone was OK (multisim-card, same number, same provider). Provider is T-Mobile Germany.

I'll try again today evening when i am at home after courses, maybe i can get some proper logs then.
[Nexus 6  Original Android Development] manup456:
[MENTION=3878813]Gandalf[/MENTION] Everything working primo on my end great work.
[Nexus 6  Original Android Development] Gandalf:
did you flash the lmyz28e radio?
[Nexus 6  Original Android Development] resynx:
I am having the same problem. Flashed the 28e radio and still no data signal :(
[Nexus 6  Original Android Development] Gandalf:
ok then get me logs, i can't figure out anything just based on this, and I'm not even going to waste my time until you guys provide logs. everything is working fine for myself and most others, so it may very well be something on your end.

Seriously, STOP POSTING ABOUT PROBLEMS WITHOUT LOGS
[Nexus 6  Original Android Development] resynx:
Okay, I never grabbed a log for just not having a data signal before, usually I grab it when something crashes so it didn't come to my mind initially. I will get you log hold on..

Edit:

okay here you go [MENTION=3878813]Gandalf[/MENTION]

http://pastiebin.com/5571c5160d415
[Nexus 6  Original Android Development] Gandalf:
Thanks, I'm looking now.

For future reference this is a great app to use that will grab all logs you can imagine automatically and zip them up for you, then provides an option to upload and gives a link.

https://play.google.com/store/apps/details?id=com.tortel.syslog
[Nexus 6  Original Android Development] resynx:
Thanks for looking into it and the app recommendation, will download and look. Sounds like it's more functional than the catlog app I usually use. Let me know if you need another log, I've never grabbed a log for a data issue such as this so I hope that log was proper.
[Nexus 6  Original Android Development] DontPushButtons:
Catlog is good for viewing realtime logging, but syslog is what I go to to consolidate the logs into one place and output them.
[Nexus 6  Original Android Development] noonecanhide:
sorry, i wasn't able to catch logs while at courses, i had my laptop left at home. i just wanted you to know that maybe something odd is happening ;)

now i am at home, after flashing the 0604 build and the LYZ28E modem the data issue is back immediately. and the logs are attached ;)
[Nexus 6  Original Android Development] Gandalf:
[MENTION=2656295]Ngo93[/MENTION] [MENTION=1320503]noonecanhide[/MENTION]

what carrier? T-Mobile?

try the ipv6 APN, I remember having some problems with T-Mobile LTE (when I had T-Mobile) and using the ipv6 APN resolved it. It's not a device issue at that point, it's the APNs/Carrier (to my knowledge) although it seems that AT&T is not having any issues (from my own use or a fellow moderator), although I can't speak for any other carriers.
[Nexus 6  Original Android Development] noonecanhide:
t-mobile germany. they currently don't provide ipv6 to mobile clients, rollout should be autumn this year. I'm trying the 05/26 build with LYZ28E modem now, then i'll switch back to the current build with LYZ28E and ipv6 apn. reports coming soon ;)

edit:

20150526 with LMY47D and default apn settings: data access is fine.

20150526 with LYZ28E and default apn settings: data access is fine.

20150604 with LYZ28E and default apn settings: data access fails

20150604 with LYZ28E and ipv6 apn settings: data access fails

20150604 with LYZ28E and default apn settings and full wipe: data access fails
[Nexus 6  Original Android Development] resynx:
I am on T-Mobile also. IPv6 was still a no go. This is odd.. that only me and noonecanhide are experiencing this :/
[Nexus 6  Original Android Development] Gandalf:
well you're both on T-Mobile, so I'm going to assume only T-Mobile is affected. AT&T users are not having an issue.

I am building now with some stuff I missed from LYZ28E that will probably correct the problem, give me about 10 minutes to finish the build and upload
[Nexus 6  Original Android Development] resynx:
Hope it fixes! Really appreciate you looking into this Gandalf. Omni is the only ROM where I don't have a single problem.
[Nexus 6  Original Android Development] Gandalf:
im about 99% positive this will fix your issues: https://www.androidfilehost.com/?fid=23991606952614938
[Nexus 6  Original Android Development] resynx:
Dang, data is still dead on this build :( bummer.. Here are more logs though:
[Nexus 6  Original Android Development] Gandalf:
wow, i made a typo.

I'm rebuilding now. you can also test this yourself, by doing the following:

-Reboot to recovery
-mount /system
-adb push libcneapiclient.so /system/vendor/lib/
-reboot to system

I have temporarily attached the file to this post.
[Nexus 6  Original Android Development] resynx:
It worked!! I've got data back:victory::victory: and I'm on the M radio as of right now too, so 28E radio isn't required :D Thanks a bunch, will await your updated build and gonna do a clean flash :)
[Nexus 6  Original Android Development] noonecanhide:
Back on track, too. Had to replace the library with root explorer ? Thank you very much! Was the Oops from AOSP?
[Nexus 6  Original Android Development] Gandalf:
no, i just wasn't paying attention and copied the same file under the wrong file name.

new build here: https://www.androidfilehost.com/?fid=23991606952614985

and OP updated as well.

[MENTION=2656295]Ngo93[/MENTION] and [MENTION=1320503]noonecanhide[/MENTION] please do a clean flash and confirm that data is indeed working with the 0605 build before I merge anything

(so annoying that some carriers require extra crap)
[Nexus 6  Original Android Development] resynx:
Confirming data is working on clean flash :good:
[Nexus 6  Original Android Development] noonecanhide:
Data is fine on clean flash here. Thank you
[Nexus 6  Original Android Development] resynx:
6/5 has been performing excellent with zen kernel, smooth and good battery. Loving this combination :D
[Nexus 6  Original Android Development] Gandalf:
I am looking to add cpuquiet back, I have my last exam tomorrow at 5 so I'll have time after that.

CPU_QUIET for testing: https://www.androidfilehost.com/?fid=24052804347757483 in OP Downloads section as well.
[Nexus 6  Original Android Development] aalupatti:
Where can I find a detailed description of the omni ambient display?

Thanks

Ps : did not find a q&a thread
[Nexus 6  Original Android Development] Gandalf:
https://gerrit.omnirom.org/#/c/11928/

This applies to any ROM that uses Omni's implementation.

I haven't had time to make a q&a thread so questions are fine in here for now until one is created, just make sure a search is done before posting.
[Nexus 6  Original Android Development] aalupatti:
Thanks for the link. I have seen this before but was looking for some more information.
[Nexus 6  Original Android Development] Circaflex:
What other type of information are you seeking? Yanuar has added the different descriptions on the upper left hand corner of that link.
[Nexus 6  Original Android Development] aalupatti:
I Re read it and found the things I need to know. Mostly looking at a detail description of each setting.
[Nexus 6  Original Android Development] Gandalf:
Once nightlies begin, I will create a Q&A thread which will house all further questions not related to development. I will also get JIRA setup so bug reports should go there as well as a post here WITH LOGS
[Nexus 6  Original Android Development] sms2000:
Hi all

Can I install this ROM on Nexus 6 with official 5.1.1?

I read CM12.1 is having issues and may brick the phone. I know Omni is based on AOSP and I'm in doubt if the issue persists here too?

Thanks
[Nexus 6  Original Android Development] DontPushButtons:
I've run a few cm ROMs lately, haven't seen any reports of bricks on any of the threads. I think you'll be pretty safe with omni though, regardless.
[Nexus 6  Original Android Development] Megaflop666:
What issues? I run cm roms all the time on my 6 with no issues.
[Nexus 6  Original Android Development] mkcbbusiness:
Does this rom have theme manager?
[Nexus 6  Original Android Development] sms2000:
It's stated on the official CM12 site there is a real brick possibility when installing CM12 over stock 5.1.

http://wiki.cyanogenmod.org/w/Known_Issues_page_for_shamu
[Nexus 6  Original Android Development] resynx:
No, there is layers support though.
[Nexus 6  Original Android Development] Gandalf:
I don't think that was merged just yet. Just check gerrit to be sure.

Well, Omni does NOT have that problem , I assure you that. This was caused by CM choosing to include bootloader and modem images in their nighties. This then caused the bricks when people had the 5.0 kernel and 5.1 bootloader (or vice-versa, I don't remember nor care at this point) but Omni will never touch anything other than system and kernel.
[Nexus 6  Original Android Development] sms2000:
Oh, many thanks.

I'd never recommend to include low-level elements into recovery flashables with ROMs. Too dangerous.
[Nexus 6  Original Android Development] resynx:
Layers works for me right now though :D
[Nexus 6  Original Android Development] x111:
Is it possible to include an option to make navbar buttons in full black or even better fully transparent ?
[Nexus 6  Original Android Development] subterfugium:
I've been lurking on this forum for few months and first of all I'd like to thank you and whole omni team for great rom! Swtiched from CM to omni.

I have a question about syncing bootloader/radio files with current omnibuilds (in this thread or in nightlies).

Correct me if I'm wrong, but to get the communication stack working from top to botton you need compatible bootloader/modem blobs (in shamu, qcom images from google factory images page) <-> compatible vendor (qcom) RIL (shamu qcom blobs) <-> compatible common RIL and android (omni). Updating omnirom might have changes on android/common RIL side which might have compatible issues if using too old/incompatible interfaces?

I guess what I'm trying to ask is how do I find out which bootloader/radio combination I need to use with any of the builds delivered here or in nightlies so that bootloader/radio combination matches with blobs (you do update blobs right?) included in each omnirom build?

Sorry, if my question is not clear enough. If so, please don't hesitate to tell so and I'll try to explain more carefully :)
[Nexus 6  Original Android Development] Gandalf:
The best thing to do would be to flash updated bootloader and modem from the factory image that matches the build used in vendor at the time. I generally have it updated same or next day from when Google posts sources and binaries. Currently you should be using LYZ28E
[Nexus 6  Original Android Development] Gandalf:
And, NIGHTLIES!

http://dl.omnirom.org/shamu/

ALL Non-Development questions must be posted in the newly created Q&A section now. Any bugs must be reported to JIRA as well as a post here with LOGS LOGS LOGS
[Nexus 6  Original Android Development] :
Can't get it boot on official night. Already Tried 19th and 21st, both stay on omni logo forever. flashed back to 0506 homemade, all good now. Do I need clean flash?
[Nexus 6  Original Android Development] markusf21:
According to g+ you need to clean flash the first nightly or you'll get a bootloop. First boot took forever but running buttery smooth so far

Sent from my Nexus 6
[Nexus 6  Original Android Development] suzook:
ROM runs great, but unfortunately most of the ROMs out are basically the same right now. I think we all can agree we want theming, and ui options. Thanks for this, I'm sure once loli gets dissected, we will have many options.
[Nexus 6  Original Android Development] noonecanhide:
There are privacy settings per app, but at the moment they only give a FC. Hopefully, this will be merged soon, with omni kitkat everything is fine
[Nexus 6  Original Android Development] eighty1:
+1 Haven't tried this yet, but kinda how I'm feeling and agree.
[Nexus 6  Original Android Development] ##W4TCH0UT##:
Omni ROM's 13/12/14 build has been uploaded.

For more changes, head over to omni's merged status gerrit:https://gerrit.omnirom.org/#/q/status:merged

Now you should see some customizations. Enjoy the ROM!
[Nexus 6  Original Android Development] darkcroc:
Nice i always loved Omni for one super thing multiwindow i must have it back Thanks for the unofficial build look forward to your success with this Rom
[Nexus 6  Original Android Development] TwelfthMan:
Did the last build 12/13 break? I see its only like 190mb
[Nexus 6  Original Android Development] ##W4TCH0UT##:
No. That's the correct size.
[Nexus 6  Original Android Development] TwelfthMan:
Oh OK thank you
[Nexus 6  Original Android Development] noonecanhide:
The 12/13 release does not boot, stuck at bootloader (google logo). My date and time is wrong after every reboot (1970/01/01 01:00)
[Nexus 6  Original Android Development] enjoidotcom:
Same problem here. 12/11 flashed fine, but 12/13 gets stuck at Google logo. I also tried flashing 12/11 and dirty flashing 12/13 over it with no luck.
[Nexus 6  Original Android Development] noonecanhide:
Clean install (rom only without gapps) after full wipe does not boot, too. Md5 checksum is correct.
[Nexus 6  Original Android Development] gregg0829:
It did not boot for me as well.
[Nexus 6  Original Android Development] ##W4TCH0UT##:
Hmm...I guess it did not build correctly after all..Let me make another build..See if that works for you..
[Nexus 6  Original Android Development] ##W4TCH0UT##:
Omni ROM's 15/12/14 build has been uploaded.

Fixed the bootloop.

No major changes.

Enjoy the ROM!!! This time with even more customization options.
[Nexus 6  Original Android Development] ice0901:
Is multi window working on this ROM?
[Nexus 6  Original Android Development] stkman32:
Is the LED for notifications working on this ROM?
[Nexus 6  Original Android Development] The5Venomz:
Just got mine today, rooted and got a rom on it already, I'm going to flash this in the morning though. Can't wait!!
[Nexus 6  Original Android Development] noonecanhide:
Does anyone know why date & time are reset to 1970-01-01 every reboot? To reproduce enable flightmode and reboot
[Nexus 6  Original Android Development] ##W4TCH0UT##:
Well no. The omni team are working on that.

No.
[Nexus 6  Original Android Development] michmeister:
What the heck is flight mode?
[Nexus 6  Original Android Development] :
Thanks. Will give it a try.
[Nexus 6  Original Android Development] Gandalf:
Yea, that's dexopt. Further boot doesn't take nearly as long.

Do people want double tap to wake enabled or what?
[Nexus 6  Original Android Development] Bingoig11:
Flashed first nightly everything is running smooth and great!

Interested in double tap to wake yes :D
[Nexus 6  Original Android Development] Tibedabeeto:
Yes to dt2w
[Nexus 6  Original Android Development] subterfugium:
what's your recommendation how I should be able to track when these updates are done?

The latest Google binaries for international shamu are LMY47I, which I am running. Is this compatible with the latest blobs in shamu nightlies? I know big interface changes in modem or RIL at this point are very rare, but for example enabling VoLTE for international model might bring changes if not already did.

As a new user, I'm just trying to figure out how track and make sure the softwares I'm using are compatible... [emoji46]
[Nexus 6  Original Android Development] Gandalf:
You can check that here: https://github.com/omnirom/android_device_moto_shamu/blob/android-5.1/omni_shamu.mk#L45 as that will match the binaries used.
[Nexus 6  Original Android Development] manup456:
[MENTION=3878813]Gandalf[/MENTION] Did you know today's build is kicking out a .zip signature verification fail in twrp?
[Nexus 6  Original Android Development] guthrien:
Yes d2w. This ROM is incredibly smooth. I've had none of the weird issues I've gotten with EVERY not close to stock option. My phone likes it.
[Nexus 6  Original Android Development] Gandalf:
Have you updated to the latest TWRP?
[Nexus 6  Original Android Development] manup456:
Yeah I have the latest 2.8.6.0 and I'm coming from the 6/19 nightly. I have tried downloading through the update in settings, downloading from the site on my phone and downloading on my laptop and they all fail with that error.
[Nexus 6  Original Android Development] Gandalf:
Please attach recovery log from /tmp after failed flash
[Nexus 6  Original Android Development] manup456:
I just tried flashing again and it failed but can't seem to find that folder. I'll keep looking around should I connect to the computer or I should see it with root browser?