Database Info

[ROM][14-02-13][Flinny] Andromadus - AOSP4.2.2[9]

Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.

Reserved

Build 5 was pretty stable, interested to see what has changed.
Tapatalked from Desire S running Andromadus

Build 5 was first build i used of AOSP 4.2 and it was fantatic experience, i never expected 4.2 to work so flawlessly on desire s so fast after release. And to be honest i did not see many bugs.
So i flashed build 6 and i was not disapointed, as you said you will release only stable and advanced releases and it was the point with 4.2 build6.
It would be nice to see official changelog, but i have noticed some nice little resize job done and few small glitches fixed.
I just found one thing i dont know how to fix. On android keyboard swype Lithuanian dictionary doesnt work. It is not in official list until i refresh it and then it pops up and i install it ( it worked well with build 5) and with build 6 it just doesnt work, and when i return to dictionary list there is no Lithuanian dictionary again .

Sensors are not working properly. When i make a call, screen turns off even when i don't block the sensors and it stays that way till the time call is going
Sorry man posted it in wrong thread. Its for andromadus cm 10.1 but do look into the matter as its really is irritating
Sent from my Desire S using Tapatalk 2

Thanks for the info..

Why there is no Google Now on lock screen? Only unlock option...
I have latest gapps, updated Google Search etc.

Taranis said:
Why there is no Google Now on lock screen? Only unlock option...
I have latest gapps, updated Google Search etc.
Click to expand...
Click to collapse
That's just the way it is for 4.2, Google made it that way.

I thought I saw videos on YT with Google option on 4.2...

Taranis said:
I thought I saw videos on YT with Google option on 4.2...
Click to expand...
Click to collapse
Yeah, that is for devices with On Screen buttons (Galaxy Nexus or Nexus 4/7/10). For those, the buttons are replaced with a dotted circle on the lockscreen, swiping up from which opens Google Now. Since AOSP doesn't officially support any device without hardware buttons, Google probably thought that it would be best to remove the option from the lockscreen, since swiping from the buttons opens that anyways

Trouble with bluetooth
Hi,
Thanks for your work on this rom!
I would like to report an issue with the Bluetooth functionality in this (and earlier) versions of this rom. In my circumstance it doesn't produce an error of crash.
For example. My phone is connected with a handsfree carkit (parrot) and when entering the car it recognizes the phone, asks for pin code and 'gets connected'. The problem is that the phone is not visible (as usual) on the handsfree device and the overall functionality does not work.
If I can be of any assistance in this I'll gladly be of help.
Thanks for your work!

Well Google switched the bluetooth plugin in 4.2 from bluez to bluedroid. It has been causing issues across devices, even Nexus 7 has issues. As Flinny said we can't do much unless someone upstream fixes it.
Read more here...
http://forum.xda-developers.com/showthread.php?p=35093862
Tapatalked from Desire S running Andromadus

Anyone know why the sound disappear?. notifications, alarms, ringtones, ect.

Thanks for the enlightenment!
suku_patel_22 said:
Well Google switched the bluetooth plugin in 4.2 from bluez to bluedroid. It has been causing issues across devices, even Nexus 7 has issues. As Flinny said we can't do much unless someone upstream fixes it.
Read more here...
http://forum.xda-developers.com/showthread.php?p=35093862
Tapatalked from Desire S running Andromadus
Click to expand...
Click to collapse

Flinny, almost everything works great.
Issues I found (AOSP build 6):
- laggy Camera animations (not very important, maybe it cannot be better),
- high Android OS battery usage (battery really lasts less),
- dictionaries other than English doesn't work with swype keyboard feature,
- some people wrote about bluetooth audio issues.
ROM is very smooth, hope it will be smooth in next builds. Great work!

Taranis said:
Flinny, almost everything works great.
Issues I found (AOSP build 6):
- laggy Camera animations (not very important, maybe it cannot be better),
- high Android OS battery usage (battery really lasts less),
- dictionaries other than English doesn't work with swype keyboard feature,
- some people wrote about bluetooth audio issues.
ROM is very smooth, hope it will be smooth in next builds. Great work!
Click to expand...
Click to collapse
camera animations do lag sometimes and some pictures you take tend to not show up in gallery after you have taken them.
As for battery all i can say is :highfive: battery is almost same in all 4.0/4.1/ 4.2 roms AND it is not at all bad here. I managed to get from full charge(100%) to 81% in 30 hours. I doubt many roms can do something like this in low-med usage.
Other then that this rom is my personal favorite until someone release 4.2 rom with better theme or perfomance.
The only thing i lack in here is conservative cpu governor and maybe little undervoltage.

Taranis said:
Flinny, almost everything works great.
Issues I found (AOSP build 6):
- laggy Camera animations (not very important, maybe it cannot be better),
- high Android OS battery usage (battery really lasts less),
Click to expand...
Click to collapse
+1
Who can tell me how can I put GPS shortcut on quick setting ??I have everything I need except GPS shortcut...

Anyone else have an issue where Calendar just wont sync at all to any Google account? I don't have the options to sync calendars under any of the google accounts I've set up on the device. Tried reflashing, clearing app data etc.
Apart from that, great rom. Super nice battery life.

noponies said:
Anyone else have an issue where Calendar just wont sync at all to any Google account? I don't have the options to sync calendars under any of the google accounts I've set up on the device. Tried reflashing, clearing app data etc.
Apart from that, great rom. Super nice battery life.
Click to expand...
Click to collapse
Clean or dirty install?
By dirty install remove Google accound(s) and then add your accound(s) again.
Worked for me!

For JB4.2 based roms (CM10.1 and AOSP4.2)
if you use a BT headset and are having problems with the mic give this a try.
download the following file.
http://andromadus.flinny.org/libbt-vendor.zip
extract it
Push it to your phone with adb - from the command line
adb remount
adb push libbt-vendor.so /system/vendor/lib
adb reboot
try it now.
Give it a try again and tell me if it all works... If all goes to plan new builds soon
Nick.

Who is using ART instead of Dalvik VM?

Hey Folks,
I just switched from Dalvik VM to ART in my phones developer Options to test how Performance and Battery life will work out.
Anyone else up for the ART Train? You just Need to enter Developer Options and then select ART instead of Dalvik as Runtime.
It then will recompile all your apps (after a restart) using ART, which will Need some time as everything gets newly compiled and will take up slightly more space. The benefit should be a massive improvement in execution time and battery Performance due to running apps as native code.
Maybe someone else can give additional Feedback.
*EDIT*
WhatsApp is not working currently using ART!

Apps load instantaneously which shaves even more time off an already speedy OS. Some root apps like Titanium Backup however are force closing after the switch. I have sent a few crash reports and hot the dev is able to respond quickly because I want to keep using ART.

Hopefully all major apps will work with ART soon, it will be a major boost. I will definitely check it out, but won't really keep using it until everything I need works flawlessly.

Apps open extremely fast, but I've noticed a few minor GUI glitches. Runtime performance seems to be the same for most apps.
Edit: Noooo! Wordament closes at the splash screen =[
Sent from my Nexus 5

I've started using it too, my only complaint at the moment is that it breaks whatsapp
Sent from my Nexus 5 using Tapatalk

My only issue is now lack of TiBackup :crying:

It would be good if we could get a list of apps that are confirmed working and not working.
We know whatsapp and titanium backup are having issues. What apps are working? facebook? I assume all google apps work fine?

WhatsApp isn't launching with ART. So no ART for me atm

Had to revert to dalvik; art is great but it breaks too many things right now.
WhatsApp couldn't be installed again once back in "dalvik mode", plau store gave me an error 24. Here's how to fix it: http://forum.xda-developers.com/showthread.php?t=2027663
P. S. If anyone still on art, can you try what I linked above and let us know if it works?

ART felt much faster for me but Quadrant and Whatsapp wouldn't work, wasnt bothered about Quadrant but ive paid for Whatsapp for 5 years, i want to use it

So far, everything I've run on ART works great with the exception of some Square Enix titles. Chaos Rings 2 seems to be ok though

running ART. the only thing ive had force close are some random camera apps which are broken in 4.4 anyway

I will switch to ART as soon as WhatsApp is compatible with it.

RagePX said:
Hey Folks,
I just switched from Dalvik VM to ART in my phones developer Options to test how Performance and Battery life will work out.
Anyone else up for the ART Train? You just Need to enter Developer Options and then select ART instead of Dalvik as Runtime.
It then will recompile all your apps (after a restart) using ART, which will Need some time as everything gets newly compiled and will take up slightly more space. The benefit should be a massive improvement in execution time and battery Performance due to running apps as native code.
Maybe someone else can give additional Feedback.
*EDIT*
WhatsApp is not working currently using ART!
Click to expand...
Click to collapse
Switched over to ART this morning and the only issue I have is that titanium fc's - It feels quite snappy though :good:
EDIT: Ooooops - sorry guys - just saw that this is a nexus5 thread - anyho - ART stil feels good here on s2 - I wonder if we could have a 'general' thread for ART discussion.

Aerys said:
I will switch to ART as soon as WhatsApp is compatible with it.
Click to expand...
Click to collapse
ART compatible WhatsApp. You might have to uninstall the one you're running now or it might just install on top of the old one. https://db.tt/3PJcAv5E
Do not update in the market, it reverts to a non compatible one!

Switched to ART yesterday. Must admit I know little about it. All of my apps seem to function with it so far. I did notice a speed enhancement right away. Going to stick with it until it gives me grief.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Swapped to art a few days ago. No problems, a few apps actually seemed to hickup a little bit on launch. But no major issues. No noticeable speed improvements as far as I can tell.
Sent from my Nexus 5 using xda app-developers app

Guys - I just created a new thread for all android devices running 4.4 and for all users to discuss experiences of running ART. Theres a couple of useful links in there also. Hope you don't mind me posting in your thread and hope you may drop by, I think this is potentially a big Android discussion and hope you may find this useful. There is a link to the thread in my signature

[deleted]

Art, it's smoother and faster in every possible ways.
Sent from my Nexus 5 using xda app-developers app

LiquidSmooth is > Cyanogen

Thought I might just let everyone know.

DJRepresent said:
Thought I might just let everyone know.
Click to expand...
Click to collapse
why thank you....alot of work went into it...making sure code was done properly as well as building with gcc 4.8 for rom and sabermod 4.8 for kernel really finely tunes and optimizes the rom just perfectly

Now that it's out into the open!! The best ROM used since forever. Get 16k+ scores on antutu and whatnot. Very stable and have had no raging temperature sores. Definitely the best ROM out there. Period.
Credit goes to R3V3NT3CH for all his hard work and time spent on the development of what might be just one of the best phones with a physical keyboard till date..

You all are awesome.... Glad I can develop for you guys....more goodies to come soon...been spending the last week on prior device I developed for as I promised that community some updates and stuff...
Sent from my L1QU1D R3L4Y using xda-developers app

REV3NT3CH said:
You all are awesome.... Glad I can develop for you guys....more goodies to come soon...been spending the last week on prior device I developed for as I promised that community some updates and stuff...
Sent from my L1QU1D R3L4Y using xda-developers app
Click to expand...
Click to collapse
There actually are a few glitches that I'm noticing, now that I've had time to play with the phone. Is there a way to disable certain services / features to get the phone to run a little better? What I'm looking for is something very bare-bones; I don't need any bells or whistles. For example, I've disabled all the animations that I could, but are there any other tips to make the phone a little more responsive?
Another problem is that the phone doesn't want to update to a newer LS, it says "Invalid ROM (liquidd2lte) & device (apexqtmo) combo!"
Any ideas?

DJRepresent said:
There actually are a few glitches that I'm noticing, now that I've had time to play with the phone. Is there a way to disable certain services / features to get the phone to run a little better? What I'm looking for is something very bare-bones; I don't need any bells or whistles. For example, I've disabled all the animations that I could, but are there any other tips to make the phone a little more responsive?
Another problem is that the phone doesn't want to update to a newer LS, it says "Invalid ROM (liquidd2lte) & device (apexqtmo) combo!"
Any ideas?
Click to expand...
Click to collapse
the reason it wont update through settings is because although the relay is a d2 variant phone it is not unified for any of the d2 variant updates....hence why for now its unnoficial and not unified or seperately branched on liquids end for updates.....as for wanting something very bare liquid is not meant for this as it has a huge multitude of customizations....try using slimkat and flash my kernel over it and im sure youll find what you are looking for

LiquidSmooth
Hello and thx for the nice ROM, only KITKAT makes my phone useable.
Unfortunately i have some issues.
1. No deep sleep after charging, i have to reboot to resolve that.
(performance menue changes: cpu limit to 1458 on boot)
2. Email only imap and no way for option dont delete from server?
How i change to some kind with no delete from server or better which app work?
(k9 app don't have this option, gmx app have this option but activate the option do exactly nothing,
the mails are still deleted).
3. Gallary don't show photos that took with app Ucam, same if photos send by bluetooth.
I have to reboot to see the photos from the last session (media scanner only scan at boot).
4. TrackID with optical issue, i report a video if nessesary and i inform me about HowTo take a on screen video.
5. No undervolt possible, the performance menue told me my device doesn't support undervolting. Checked that behavior with some tuning tools, same issue. All tweaking tools tells me Kernel doesen't support undervolting so i deinstalled the tools without changes. No worries, i have some uv experience with xperia pro
I installed your new kernel yesterday (B14CK1RD v. 1.1) and repplaced the original one from LiquidSmooth but unfortunately the issues are the same.
Only 1. and 3. are realy important for me.
and again, thx for the nice LiquidSmooth
Marcus

[ROM][OVATION][EMMC][UNOFFICIAL] Liquidsmooth KitKat v3.2

ROM:
http://www.mediafire.com/download/wkzcatpp7az4r5f/LS-KK-v3.2-2014-10-17-ovation.zip
MD5:
http://www.mediafire.com/download/piwirf8ee421dqv/LS-KK-v3.2-2014-10-17-ovation.zip.md5sum
A shoutout and thanks goes out to Rhyang for his help with the Slimkat rom, (to which this is somewhat similar).
Compiled with Sabermod toolchains. 4.8 for the rom and 4.7.4 for the kernel.
O3 optimized.
I made an attempt to fix 'OK Google'. Dunno if it's working or not (haven't tested). If it's still broken then it will be in the board files and will be a bear to try and find....
Dunno, it seems to work fairly well (ALMOST as good as Cyanogenmod 10.1 ) I kinda like it in a way (except it's KitKat).
I'll try and upload some source later. My internet connection has been giving me problems lately (took four hours or so to upload this). Even with source this is somewhat difficult to compile anyways (I fought with it some).
Cheers!

Great. I'll download now and try it out today :good::good:

Oh man I love LiquidSmooth! I am using it on my phone and have never looked back.
I guess I will have to give this a try. Thanks a lot for this. Is it also running on your yellow kernel or something different?

Which Gapps file is used with the rom please?

Yes it's using the same kernel as Slimkat except that /sound and /drivers/mfd folders have been swapped out with their CM11 kernel counterparts.
If you go into settings and 'about tablet', you will find download links to two types of gapps, full and minimal.

Things are running well. OK Google doors not appear to work too well

Jon Lee said:
Yes it's using the same kernel as Slimkat except that /sound and /drivers/mfd folders have been swapped out with their CM11 kernel counterparts.
If you go into settings and 'about tablet', you will find download links to two types of gapps, full and minimal.
Click to expand...
Click to collapse
Hey Jon, thanks for yet another new rom. :good: Looking pretty cool so far but as already mentioned, "Ok Google" is not working properly. I swapped out your yellow kernel with the stock CM11 kernel and Google Now is working as it should.
Since I lack the capability to compile a kernel, I simply replaced the yellow kernel boot image and the entire modules folder in /system/lib with the CM11 boot image and modules folder. I hated to lose the yellow kernel as I feel that it has better performance than stock CM11 but I love using OK Google. Btw, I did the same with your Slim rom with similar positive results.
Also, I see in the build prop that the density is set to 320DPI instead of the standard 240. I happen to prefer 320 but I would think that the masses might want the standard density and would be wondering why their desktop looks so big.
Anyway, thanks again for your contributions. It's appreciated.
Mike T

Ooh, nice!

Wow, is this fast!
So many ROMs, so little time.
I've been using CM 11 nightlies for a couple months now and didn't have many complaints. The usual CM 11 screen flicker problem when charging, some screen black outs (and crashes) on a certain screen in one of my aviation apps. That was about it. CM 11 was fairly fast and incrementally getting better all the time.
CM 11 doesn't have zRAM built in (yet), so I got a lot of app restarts when switching between my high memory aviation moving maps and other apps. But we're trying an experimental zRAM build that's helping with the HD+'s limited RAM.
But then I got a wild hair and decided to look around in the HD forum to see if perhaps Jon had an OC kernel for CM 11. Then I found his build of Liquidsmooth for the HD+. I didn't want to spend a half day wiping and installing a completely different ROM. But I'm glad I did. Wow.
I don't know if it's the overclocking or the other tweaks or all the above, but my AnTuTu score jumped from 17300 to 19100! Thanks, Jon!
(Hotplug governor seems to work best for me in both LS and CM 11. Too early to tell, but battery life doesn't seem any worse in LS.)
I assume that LS does not force the CPU to 100% when running AnTuTu, as CM 11 does. So the 19100 is probably a realistic reflection of performance.
(I haven't experimented with the I/O scheduler yet. I left it set at fiops for now. (Supposedly best for flash memory. Heretofore I've always used Deadline.) I lowered the SD cache to 512, which I found worked best in CM 11. (Using SD Booster to make that change.) FWIW, I enabled the GPU Acceleration and Super Tweaks in LS. )
[FWIW, the word "compiler" is misspelled (twice) in the "Just in Time Complier [sic]" setting.]
I'm happy to report that the screen flickering/crashes are gone when on that special page in my aviation moving map that always flickered - and sometimes crashed - in CM 11. (Requiring that I disabled HW overlays in Developer Options in CM11.) And since I set the "Low Memory Killer" to "Light" in LS, it doesn't kill my apps as aggressively as CM 11 did. (Not apples and oranges, because I was running ART in CM 11, whereas LS implies you shouldn't even try ART.) LS should be even better with zRAM. (And the boot animation is better than the frowning, scary CM alien face. )
(Speaking of zRAM, I noticed that someone in the Slimkat forum is running zRAM on Slimkat. I read here that Slim and LS are kinda the same. Is there a way to turn zRAM on it LS?)
I'd be curious to know what the major differences are between LiquidSmooth and Slimkat. Since Jon says LS is "similar" to Slimkat, why does LS exist?
Not much I could find on the web about it. I looked at the Slim home page. It's main advantage seems to be fancy interface stuff. (Although LS has PIE too.) Kinda like a toned down version of PAC? But the LS home page is silent about what makes it better/different.
Like I need to spend another half day wiping and flashing can customizing another ROM. (Titanium Backup is supposed to save data/settings. If it does, it doesn't seem to work for me. I have to reset the Settings on my apps when I restore from Titanium.)
---------- Post added at 10:34 AM ---------- Previous post was at 10:21 AM ----------
Every trying for that last bit of performance, some questions:
Q: On zip align apps on boot. Should I expect a toast or a notification if an app needed to be zip aligned?
Q: In CM 11, there's a Developer's Option to kill an app with a long press of the Back button. (Seems to be different from swiping "closed" in Recents, in that it completely shuts down the app.) Is there a similar trick in LS?
Q: I updated the host file for disable ads. I got a message that it worked, 0/4. Zero out of Four? That doesn't sound right. Is it?
Q: In CM's Launcher settings, you can disable transitions, stop scrolling wallpaper, etc. But I can't find a way to disable transitions - especially in the App drawer - in LS. (I see ways to change the transitions, but none of the options have "None.") Where are they or what's the trick to kill them?
Q: Last, and this is more of a Slimkat design element, but shouldn't there be a "Close All" button in the Slim Recent panel?

PMikeP said:
Q: Last, and this is more of a Slimkat design element, but shouldn't there be a "Close All" button in the Slim Recent panel?
Click to expand...
Click to collapse
For a while SlimROMs said they wouldn't support this, but now you can close all apps in the recents panel with a two-finger pinch. I think they might even have a youtube video of this ...
I like Slim because it's minimalist -- no bloated theme engine and its associated bugs. That said, their drivers tend to be a little more out of date than CM. The framework source is also slightly different. This makes sharing code between the two a PIA sometimes. I have no familiarity with LS, so I'm not sure how applicable these comments are to it.
Looks like you've been busy Jon

rhyang said:
For a while SlimROMs said they wouldn't support this, but now you can close all apps in the recents panel with a two-finger pinch. I think they might even have a youtube video of this ...
Click to expand...
Click to collapse
Thanks. I found the pinch gesture serendipitously while trying to swipe away a running app in Recents. Still, it's problematic trying to get it to 'close all' all the time. I went back to stock Recents for now. (Favorites implementation in LS Recents might be nice, as they've implemented in Slim, but I haven't figured out how to invoke it in LS if it's there.)

Here's the device and vendor source as promised:
http://www.mediafire.com/download/z3llb4mauxo8m16/liquidsmooth.tar.gz
Let me know if you need help or any other source to build.
I kept this one very much "original"/plain, meaning I didn't add the zram script (or anything else extra).
To add zram to it, just extract the attached 60ZRM script to /system/etc/init.d
(make sure it is executable & root:shell owned), and reboot.
I believe as far as 'ok google' is concerned, the next step would be to compile with the normal vanilla Cyanogenmod defconfig (sorry, but I refuse to install Gapps just to test). Microphone works, mixer values are the same, so... There's a reason I disabled some of that IPv6 stuff...
Behind the scenes I've been (rather unsuccessfully) attempting a port of ION CMA Heap.
http://pastebin.com/J1Ptxz3W
(Which is why I shared the first build without adding any extras, because I knew I was going to break it immediately following).
BTW, I'm still very new at compiling android and it will take me some time to become better acquainted with the build process.

A hack to fix auditd error "protocol not supported"
Jon Lee said:
To add zram to it, just extract the attached 60ZRM script to /system/etc/init.d (make sure it is executable & root:shell owned), and reboot.
Click to expand...
Click to collapse
Thanks again Jon! The Permissions for your script file were correct from the start. I don't know how to make sure it was root:shell owned, but it worked nevertheless.
Now, a hack to stop auditd errors:
After I got my apps reinstalled and set late last night, I decided to run catlog, just to see what I could see.
LiquidSmooth is definitely quieter than CM 11. (In the sense of less processes starting and stopping.) To be fair, not quite apples to apples because I'm back to running Dalvik on LS and was running ART on CM 11. (ART comes alive frequently to trim memory.)
But there was one process in LS, that I didn't notice in CM 11, auditd, that just kept starting and stopping with an Error, "Protocol not supported."
Despite that fact that auditd is constantly trying to run, it doesn't stop one of the CPU cores from shutting down (with Hotplug governor), nor does it prevent the CPU from dropping to its lowest freq. So, in practice, it doesn't seem to be a problem. Still, it can't be good to have this one thread constantly starting and stopping and it bugged me.
Now, maybe I caused the problem, because I typically uninstall a lot of Google junk and I disable a lot of Google services in the junk I can't remove. (Boy, Google just keeps pinging and pinging you!) And I hadn't run catlog with a virgin build of LS to see if the auditd Error was there at first.
Having said that, I did find a few other people on Google asking about the same auditd Error. (Apparently, auditd is a process from Sun.)
On the assumption you all get the same Error too, the best way to stop this would be to find out why it's trying to start. And to stop it. (Duh.) But that's WAY beyond me. So instead, I simply renamed the auditd file in /system/bin (it's a binary) to auditd.old.
I cringe when I think about it, but it worked anyway. (Worked in the sense that I don't get the auditd Error anymore.)
(As I write this, I wonder if the "d" at the end of audit is Unix convention to signal a daemon? If so, the I suppose there's probably a start up folder or file somewhere in Linux that's trying to start it? Or do daemons start themselves?)

When streaming video on any room using yellow kernel I get occasional freezes that require powering off my nook

Can I use Yellow Kernel in CM 11?
webdroidmt said:
I swapped out your yellow kernel with the stock CM11 kernel and Google Now is working as it should.
Since I lack the capability to compile a kernel, I simply replaced the yellow kernel boot image and the entire modules folder in /system/lib with the CM11 boot image and modules folder.
Click to expand...
Click to collapse
Clever! So, then, can I do this in reverse and swap Jon' s OC kernel into a CM 11 build?

PMikeP said:
Clever! So, then, can I do this in reverse and swap Jon' s OC kernel into a CM 11 build?
Click to expand...
Click to collapse
Never tried but in theory, it should work. Best way to find out is to make a nandroid and try it.
Mike T

webdroidmt said:
Never tried but in theory, it should work. Best way to find out is to make a nandroid and try it.
Click to expand...
Click to collapse
I tried it. Unfortunately on first boot, after immediately getting the CM set up screen, I got the message "Unfortunately, the process com.android.phone has stopped." (It didn't even go thru the process of updating apps like it normally does after a clean wipe, so something seems wrong. I re-did a second Factory Resent and /system wipe. Still no joy.)
So let's make sure I'm doing what you did. I downloaded the latest CM Nightly zip. I have Jon's LS zip. I opened both archives in 7zip.
I took Jon's boot.img from the LS zip and copied over (and replaced) CM's boot.img. I did the same with the modules folder in /system/lib. Then I closed up 7zip and tried installing the new hybrid CM 11 zip file.
But, since you said that you found that "Ok Google" didn't work for you on LS with Jon's kernel, it occurs to me that maybe you made these changes in a running install? That is, I would first install a "stock" CM 11 Nightly and then, after it's running, go in and change boot.img and modules? (I think changing the boot img in the partition would be a challenge for me.)

PMikeP said:
I tried it. Unfortunately on first boot, after immediately getting the CM set up screen, I got the message "Unfortunately, the process com.android.phone has stopped." (It didn't even go thru the process of updating apps like it normally does after a clean wipe, so something seems wrong. I re-did a Factory Resent and /system wipe. Still no joy.)
So let's make sure I'm doing what you did. I downloaded the latest CM Nightly zip. I have Jon's LS zip. I opened both archives in 7zip.
I took Jon's boot.img from the LS zip and copied over (and replaced) CM's boot.img. I did the same with the modules folder in /system/lib. Then I closed up 7zip and tried installing the new hybrid CM 11 zip file.
But, since you said that you found that "Ok Google" didn't work for you on LS with Jon's kernel, it occurs to me that maybe you made these changes in a running install? That is, I would first install a "stock" CM 11 Nightly and then, after it's running, go in and change boot.img and modules? (I think changing the boot img in the partition would be a challenge for me.)
Click to expand...
Click to collapse
You did it right. I did a total clean install of the Liquid rom with the newly "implanted" CM11 kernel. I wouldn't mess around with the partitions, dangerous territory. :laugh:
There's possibly some "hook" that Yellow is looking for that is not contained in CM11.
After reading your post, I just decided to see if it would work in reverse. I also got the same process phone has stopped error. With the ease of making nandroid backups, stuff like this is always worth a try when it's something you want or need. I'm thrilled that it works the other way, as I do use "Ok Google" a lot on all my devices and this Liquid rom runs nicely on the Nook.
In addition, with the introduction of Lollipop, Google has revamped GN and it's even better to use than before.
Mike T

webdroidmt said:
You did it right. . . .
After reading your post, I just decided to see if it would work in reverse. I also got the same process phone has stopped error.
Click to expand...
Click to collapse
Good to know I'm not alone then. Oh well, it was a promising experiment.
(Last night I tried experimenting (hacking) to get zRAM to point to a swap file on /cache. Not really a LS thing, but I might write about it later.)

I tried installing this today and it ran really nice and smoothly, but it doesnt seem to have the full HD+ screen resolution. Seemed more like 720p than 1080, large fonts and icons, just a lower resolution. Am I missing a setting or is it not working at full resolution?

Installed CM11 - everything else seems to work great, Chrome crashes immediately?

So, I'm obviously not remotely an expert when it comes to Android mods, but I'm finally fed up with being stuck on Android 4.1 - since it doesn't appear we'll ever get any upgraded qwerty phones ever again, I figured I'd try diy'ing it.
I have successfully flashed TWRP, rooted the phone, and installed what I believe(?) to have been the most recent version of CM11 (I figured it'd be cleanest to keep the phone closer to what it was designed for - I've seen tons of apps require 4.4 at minimum, not too many that require 5+): cm-11-20150626-SNAPSHOT-XNG3CAO1L8-moto_msm8960_jbbl.zip. Was the most recent version I could find, anyway?
I booted it up and for the most part, everything seemed to be working. Everything except Chrome, which crashes reliably and immediately. I tried clearing all the caches (the app's cache + data, and the phone's, from recovery), uninstalling and reinstalling Chrome, I tried the beta version (crashes), I tried a fork, Brave (crashes). Other browsers are working fine, but I like Chrome.
One weird thing I did notice: I was thinking it might be a gapps issue, but weirdly, the Play store, gmail, maps, everything else just installed and seem to work out of the box before I did anything with gapps? I did also try flashing the most recent base 4.4.4 gapps zip from what I could tell (gapps-444-base-20170209-1-signed.zip), but I'm not sure how to tell if it actually did anything? It said it flashed successfully, but (other than having to wait for all my apps to recalculate because I cleared all the caches), nothing noticeably seemed to change on the front-end as a result, and yes, Chrome still crashes. Should I be using a different gapps install than that for the Photon Q? Or anything else I should check/try? Thanks!

Yay! Answered my own question, with sufficient digging!
Answer seems to be basically: the newest version of Chrome (v55) exposed some sort of weird incompatibility with CM, so the easy fix is just not to use it, at least for now. I sideloaded Chrome v54, and it stopped crashing, yay! Source: https://forum.xda-developers.com/showpost.php?p=70762641&postcount=198

Just FYI, the latest version available for this device is CM13.
They are working on Lineage.
Edit - seems you found the CM13 thread already

Yep - I'm glad to see people other than (and smarter than) myself recognize the Photon Q's unique place as being the final and, sadly, best qwerty slider available for our use, and that it therefore needs to be actively maintained even if Motorola won't... I just figured it'd be better to use an OS closer to the one the device was intended to be used with. Once I'm done testing CM11 out on my old half-working phone (re-purposed to a test phone) and push it to my new fully-functional one, I will probably at some point upgrade that first phone to the latest to try it out (probably once a Lineage build comes out, so I can be on a build that's actively being maintained). For right now, though, I figured I'd stick with CM11. Any case, looks like CM13 exposed the same Chrome issue, anyway.