yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] taz1458:
Follow his steps on the last page. It got the messaging and hangouts app working for me. Handcent just doesn't work. Also, is it not possible to change fonts in 4.4?
[Samsung Galaxy Nexus] NuclearBier:
Could you please provide a link to the 12/5 nightly.

Thanks for the help.
[Samsung Galaxy Nexus] taz1458:
Follow these steps first:

EDIT: Try to go to the dev host or xda link, at the top you should be able to go to all of his uploads.
[Samsung Galaxy Nexus] telktrot:
Handcent is fully updated on mine and keeps fc'ing for be as well.

Using hangouts for now.

Also, is there no advanced power menu to reboot to recovery? Am I just missing it?

Thanks!
[Samsung Galaxy Nexus] NuclearBier:
I can't restore any of my current TiBus because they are from 4.3 and from a totally different rom. In my OP i mentioned that this was my first 4.4 ROM install so I have no 4.4 backups to restore. I will try and find the 12/5 nightly.

Thanks again
[Samsung Galaxy Nexus] taz1458:
Go to about phone, click on build number about 7 times, it'll unlock developer options, it's like the 3rd option down.

Missed that, sorry about that. Here's a link with all builds.

http://xdaforums.com/devdb/project/?id=1098#downloads
[Samsung Galaxy Nexus] kb8no:
Ummmm... From what he says, this was caused by unexpected new gapps. He now reccomends "modular mini" gapps which I presume does not break MMS. So I'd say do nandroid for good practice, then dirty flash same ROM after Dalvik and cache wipe. Then flash the good gapps and boot.

Edit. So now I read all the rest of the flurry of posts I hope this doesn't sound stupid.
[Samsung Galaxy Nexus] metalspring:
[MENTION=3390093]MWisBest[/MENTION] have you ever checked out IAmTheOneTheyCallNeo's github? He also has tons of things for linaro and 4.8

https://github.com/IAmTheOneTheyCallNeo

It would be awesome if the 2 of you worked together and made it even easier for devs to use full linaro optimizations (he even has a script to automatically add tons of cherry picks to get linaro working for cm-11)
[Samsung Galaxy Nexus] David 617:
Thank you for all your hard work. This is the smoothest and fastest my phone has ever been.
[Samsung Galaxy Nexus] MWisBest:
New build up, should fix some of the issues with the 2013/12/13 build such as SMS/MMS.
[Samsung Galaxy Nexus] modernbummer:
I like that one.
[Samsung Galaxy Nexus] MWisBest:
I really appreciate all the support, and I think that pretty much settles it as to my decision: merge it is!

I don't quite know what things would be easy to do for this, I'm thinking some things might require a complete rewrite of code, while others might just merge in without any changes. My plan is to not use ROMControl from AOKP, and instead stick everything in the Settings app neatly and organized like CM is doing.

One thing that might be helpful is knowing what your favorite features are from AOKP so I can maybe prioritize what to do first as this certainly won't be an all-at-once thing. :good:
[Samsung Galaxy Nexus] swarlesbarkely:
I like trebuchet for the launcher because the aokp one is boring and I prefer ROM control over pretty much any cm setting personally.
[Samsung Galaxy Nexus] Rushead:
I've grown accustomed to, nay reliant on dpi adjustment. 280 - 300 is just about right for me. 320 just seems ungawdly.

Sent from a frequent flasher.
[Samsung Galaxy Nexus] MWisBest:
I planned on keeping Trebuchet.

As for the ROMControl thing, I'm not saying I won't be implementing the features included in ROMControl, I'm saying I won't stick all of the options in that app or something similar. Instead I'll integrate it into the Settings like it's a real part of the ROM and not some afterthought separate app, if you get what I'm saying.
[Samsung Galaxy Nexus] swarlesbarkely:
Yeah that makes sense. Looks more professional that way. I'm just saying I like what ROM control does. I could care less how it's implemented
[Samsung Galaxy Nexus] modernbummer:
I'd rather this have the look and feel of CM with some AOKP features added. It doesn't need to go overboard with the features like PAC or Carbon. I think this could be a good niche ROM for people who love CM, but wish it had just a bit more, if you know what I mean.
[Samsung Galaxy Nexus] swarlesbarkely:
Exactly!
[Samsung Galaxy Nexus] MWisBest:
That's generally the direction I was thinking of taking, I'm glad to hear that I'm not the only one who feels this way. Really with all the stuff AOKP has I myself got overwhelmed just looking at the settings. I started my custom ROM stuff with CyanogenMod, and then AOKP came along and I liked it but I missed the rock-solid feel of CyanogenMod and could never really decide between the two.

One thing I don't plan on adding unless there's really a lot of interest in it is the "battery bar", the (by default) blue line that would be at the top of your screen stretching across based on how much battery was remaining. As soon as I saw this, my FIRST thought was: "omg burn-in alert!" If anybody does want it, I might consider adding it with a warning when you enable it (I just thought of this as I was typing, haha.)

Yeah I've really got a lot of ideas piled up to sort through here, I think I'm going to take the weekend to think about it as it looks like I'll be busy with work this weekend so I won't have much time to do any coding. I plan on maybe tossing up an updated CM-10.2 build on the weekend and then after that start on the merging stuff.

Ideas popping into my head now... maybe use the regular Nexus-style boot animation... get some sleep for tomorr- make that today... cut down on translations to decrease ROM size a bit, will provide what I'd think the essentials are (English US and UK, Spanish, French, German?) and then add any others people might request, considering the fact that I'm currently only making this for a phone for a USA carrier... add a dark theme (not enabled by default, I don't want to force look changes like that on people) and make sure that it makes as much use of true black as it can to save battery by not having to power the screen so much... SLEEP... :good:
[Samsung Galaxy Nexus] bluerez79:
Love the idea of a dark theme. What about the feature of sliding you finger across the status bar to adjust brightness? I've always thought that feature was useful. Rest up .
[Samsung Galaxy Nexus] swarlesbarkely:
Can I request swiping between qs and notifications?
[Samsung Galaxy Nexus] MWisBest:
Settings --> Interface --> Status bar --> Brightness control

I didn't think it was in CM anymore either at first, it certainly seems to have buried itself in there well.

The bottom bar of the notification/QS thing allows you to do this, if you kinda get what I'm saying. If not there might be a video I can find with it to show you.
[Samsung Galaxy Nexus] swarlesbarkely:
Ahh never noticed that. Thank you!

Also I hate the nexus boot animation because I associate it with the ROM I just tried to flash not booting properly. Just my two bits haha
[Samsung Galaxy Nexus] MWisBest:
I'll think about it... maybe I'll provide a couple extra flashable zips containing the AOKP and CM boot animations but default to the Nexus one, is that an OK compromise? :)

I think I might get some time soon to throw up an updated CM-10.2 build, and then while I'm at work I'm going to let some stuff run in order to begin the merging things. I think I'm going to create a separate git branch for CM/KP so that in the mean time while I work out the kinks with that I can still easily provide updated regular CM builds.
[Samsung Galaxy Nexus] MWisBest:
New build for today is up! Check the changelog and flash away. :highfive:
[Samsung Galaxy Nexus] swarlesbarkely:
Getting really bad lag with ondemandplus. Any chance this is from the kernel change? I came from golden
[Samsung Galaxy Nexus] MWisBest:
That's something I've been putting off fixing since day 1 actually, it isn't related to anything new... you know how devs are...... laaaazzzyyyy!!! It's why I set interactive as the default governor until I sorted this out. It's actually something I was looking at potentially fixing before I started CMKP stuff.
[Samsung Galaxy Nexus] swarlesbarkely:
I thought I remembered something about that but I wasn't sure. Thanks!
[Samsung Galaxy Nexus] MWisBest:
Today looks like it'll be busy for me, not sure how much I'll be able to get done on the ROM. Yesterday I slept 16 hours and woke up still tired... haven't been feeling very good lately either so I'm probably going to see if I can get into the clinic soon to see what's up. :(
[Samsung Galaxy Nexus] David 617:
Thanks! New build runs perfect.
[Samsung Galaxy Nexus] 99problemz:
Much respect for sharing your views and listening to what we have to say.. I normally don't post just flash.. I just wanted to comment on your post and commend you on a ROM well done. Hats off to you sir.
[Samsung Galaxy Nexus] David 617:
I noticed on 4.4 that DNS-setting apps do not work.

Does anybody know how to set the DNS permanently in android 4.4? I like to use fools DNS as an adblocker.

Thank you
[Samsung Galaxy Nexus] MWisBest:
I had a look at his stuff. To be honest, I'm not exactly thrilled with it. Instead of fixing aliasing violations, he disables strict aliasing (in some cases, even unnecessarily) just to get the code to compile, but that takes away from some of the things the compiler can do to optimize the code. While there are some aliasing violations that are difficult to fix, there are plenty that can be fixed. However, when I was first starting out with all this Linaro stuff long ago, I wasn't much different. The more I worked with it the more I learned, and I think he'll improve like I did. It seems to me that our forks generally overlap anyway.

I'm not particularly interested in providing a script to allow a "one-click to cherry-pick" sort of thing to let people use my work, for a few reasons:

- Cherry-picks can become outdated and start having conflicts. I can't spend time making sure this stuff doesn't start conflicting.

- Right on my GitHub is a fork of CM's manifest too, with all the changes I've made right there. I'm almost certain they can go into an already-existing CyanogenMod repo clone, and run "repo init -u git://github.com/MWisBest/android_manifest.git -b cm-11.0" and all my changes would come right in without having to redownload every single thing. I know at the very least I was able to do this when going from the cm-10.2 branch to the cm-11.0 branch. This could be their one-click thing, but avoids the problems mentioned above with cherry-picks.

- Providing a script to do everything for somebody just isn't fair with all the work I had to put into this. I want people to learn something from this stuff, not just have somebody hold their hands for them. If people are willing to learn new things, I'm willing to help them, but I'm not willing to do something for people who don't want to learn anything. I don't think that's the right attitude to have, and if that was my attitude FML wouldn't be here in the first place.

As an example of learning, something cool that I figured out recently was this: https://github.com/MWisBest/android_frameworks_base/commit/d64a187045c5d01d0fba823e229b718ebdb058bc

It allows me to work around strict aliasing violations without having to exclude every single file in a directory. I haven't seen anything like this yet, and I'll gradually begin rolling out this change to any place I've had to disable strict aliasing. It's easier to at least start with this instead of sitting there trying to fix the strict aliasing violation, as I'm still not all that great with that, and from what I understand, not all of them are really fixable either. Had I not taken the time to learn, I wouldn't have brought something new to the table like this. That's why I'd like people to learn about what they're doing and get a deeper understanding of it!
[Samsung Galaxy Nexus] MWisBest:
Have you used any other 4.4 ROM or a build of FML before the 2013/12/13 one, and if so, do they have the same problem? I just want to make sure this wasn't something I introduced with the recent changes to FML, as it does have a chance to introduce random things like this.
[Samsung Galaxy Nexus] metalspring:
I see your point, I know I just had to add a bunch of fno-strict-aliasing to get omni rom to get anywhere with -O3

even after cherry-picking all the strict aliasing commits... apparently omni uses twrp recovery source and no one has any commits I could find to fix strict aliasing on it

Same thing for OpenWnn and PinyinIME

And had to add fno-strict-aliasing to external_chromium because it kept erroring out on net/base/host_resolver.cc for some odd reason (even with the strict aliasing commits)

At any rate its just a test build anyway to see how tough it would be to get all the commits needed to build lol

The one big thing I like about neo's commits though is- https://github.com/IAmTheOneTheyCal...mmit/2c1e134c8a97cbc02adf7888327a7a276a7c4846

It makes it very easy to switch toolchain versions for both arm-eabi and arm-androideabi and use different versions for each one
[Samsung Galaxy Nexus] MWisBest:
I did see that, definitely not a bad idea. I think the reason for the difference in aliasing violations is that he has "-Wstrict-aliasing=3" set in the compiler flags rather than the "-Wstrict-aliasing=2" that I and Linaro use. 3 might not be a bad idea though, GCC documentation says it is more accurate, having very few false positives and very few false negatives, just that the main downside of 3 is that it's slower. I'll definitely be doing some testing with it. :good:
[Samsung Galaxy Nexus] darklordofthesith:
Quick question. Tried flashing this rom and it did not take. Am I supposed to have the newest bootloader on my gnex to get this to work?
[Samsung Galaxy Nexus] kb8no:
Shiny has a nice OP with latest bootloader, radios, and CWM recovery. Its probably the recovery though.

http://rootzwiki.com/index.php?/topic/36706-[ROM][AOSP](12/11/13)-Shiny-ROM:-OTA-Like,-Stock-Android-[4.4.2]-[KOT49H]
[Samsung Galaxy Nexus] David 617:
Yes. It is not an issue with your ROM.

I have experience with these kind of things, was just hoping someone knew where to set it in the file system.
[Samsung Galaxy Nexus] xFaultx:
I gotta say, your ROM totally revitalized my phone. My gnexus was dying and crashing all the time. Thanks for this great rom!
[Samsung Galaxy Nexus] ricola1989:
Tried flashing 1213 build. Got stuck on boot and bootloops galore. Tried every combo of clean/dirty flash, multiple kernels and gapps packages. Got nothing. Kinda weary of flashing the latest build just cus if anything goes wrong I'm not aroundn WiFi to recover anything..

Any advice guys?
[Samsung Galaxy Nexus] agreenbhm:
I just successfully flashed 1215 after several failed attempts. I was previously using a PA Gapps Full package from November, but downloaded the latest PA Stock and Full packages. I got lots of FCs with Stock, a couple with Full, and finally had success with Mini. I suggest reverting to your backup, reboot into Android (I got a hung boot after flashing before rebooting after a restore), boot into recovery, wipe cache, dalvik and system, then install the latest build plus the Modular Mini PA Gapps.

---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------

MW, the latest 1215 build shows build date of 1213 in status. Is that normal?
[Samsung Galaxy Nexus] cujo6801:
Flashed 12/15

W/no problems

Used rommanager

W/latest cwm

All at once In order

Nexus super wipe

ROM 12/15

Pa mini gapps 12/15

Mpo SR 4.4

Rebooted..

Profit..

sent from the DOG pound
[Samsung Galaxy Nexus] ricola1989:
Finally got the latest build to boot, I'm kinda scared to flash a custom kernel though. Wish me luck :s
[Samsung Galaxy Nexus] t1.8matt:
No probems here on latest build. ASKP Grande works fine, this thing is flying. No problems with SMS either, used mini modular gapps.
[Samsung Galaxy Nexus] agreenbhm:
No reason to be scared. Take a backup and restore it if anything goes wrong.
[Samsung Galaxy Nexus] skylordusa1:
Thanks for the quick SMS fix MW. I loaded the latest FML 12/15 build with the latest full PA gapps and SMS is working great along with everything else. I haven't noticed any issues yet. ROM is running very smooth. Thanks again for all your hard work.
[Samsung Galaxy Nexus] MWisBest:
Yeah the build date thing doesn't change with incremental builds, I haven't added in the fix to stop that from happening yet, totally spaced it. Thanks for the reminder.

I'm glad the new build is running speedy for everybody, that week worth of work definitely paid off! I appreciate the support you guys have shown for me and the ROM, especially with the struggles I've had with it recently.

Some brighter news is that I was recently accepted to the college I want to start out at. My plan is to start out at a tech school to save a bunch of money, and then transfer to a 4 year school. The tech school has an "IT Software Developer" program so I should be able to get a computer programming job somewhere with that Associate's Degree while I finish up at a 4 year school getting a Bachelor's Degree. :victory:
[Samsung Galaxy Nexus] agreenbhm:
Congrats MW! Seeing as you're already doing some advanced development work, you'll likely feel the same way about your CompSci program as I do about my InfoSec program: stupid-easy because of all the previous experience. Best of luck!
[Samsung Galaxy Nexus] MWisBest:
Yeah that's how I felt with computer science class in high school, they had Computer Science 1, 2, and 3, all year-long (both semester) classes, and the teacher for 2 and 3 recognized that and gave me some leeway to go beyond the curriculum so I got something out of the class. I was able to take 1 as a freshman because in middle school I was in Advanced Math, which was equivalent to the required Algebra 1 course for it. I think I always got at least 98% or so on the finals, the last one I got 100% on, and after Computer Science 3 we got the option to take the AP Computer Science exam, I ended up getting a 5 of 5 on it, the first person from my school to get even above a 2! I think my passion for it and my teacher's flexibility has contributed greatly to my success. I am definitely in his debt. Good luck to you too. :)
[Samsung Galaxy Nexus] agreenbhm:
Thanks man. As a former CS major myself, I'll say this: the fact that you know what a makefile is, can compile something using GCC (and switch between compilers to stomp out bugs), and can fix bugs period, means you have several boring semesters ahead of you :laugh: At least you'll get to solidify your understanding of OOP and data structures, and depending on the language taught for the program, perhaps pick up a new language along the way. I'm working full time and going to school online/at night for InfoSec, so really no CS there except for basic cryptography and an Intro to C++ course (hahaha, brought me back to when I learned BASIC at age 10...). I do appreciate my CS background, though, b/c while I'm not doing dev work on a daily basis, I can read through code and get the gist of it, build the occasional application for work and/or fun, and write a mean script to automate the **** out of repetitive tasks at work. Most recent accomplishment: writing a script to chain-load 19 .exe and .msi installers together (silently) so I don't need to manually deploy our big-bad LOB application (w/ local SQL backend) ever again. What a PITA that was!
[Samsung Galaxy Nexus] ricola1989:
For those of you using ASKP kernel: linaro, or base Grande?
[Samsung Galaxy Nexus] hotrodwinston:
Just some ideas on the kernel side of things - maybe include some more frequencies? I like to set my min a little lower to save battery. Also could you take a look at the modified governors and schedulers used in Franco kernel? They were tested and tuned across a lot of testers gnex's and have been really smooth but he is all but mothballing gnex development. The reason I ask is your kernel so far has been so good I extracted the boot img and have been using it in other roms - and just feel it can go from being a awesome 4.4 kernel to THE awesome 4.4 kernel.
[Samsung Galaxy Nexus] taz1458:
Flashed the new one. 0 issues other then handcent closing.
[Samsung Galaxy Nexus] heXacode:
On build 12/15 using ASKP Grande and mini pa gapps.

No issues here except I tried ART for a second time. First time was on different ROM almost a month ago and it seemed like it lagged more than dalvik. Went back to dalvik for awhile. Now on this build. I switched to ART to see if maybe it would be an improvement or not. It seem to have even more lag than the last time. It would take anywhere from 8 seconds to 15 seconds to open an app. Switched back to dalvik and its a lot better.

Not a deal breaker at all since its fairly new and needs more improvement.

Secondly, I havent explored this ROM a whole lot but I did notice for Lockscreen settings when enabling alarm, weather, and calendar nothing showed up on the lockscreen. I don't know if anyone has mentioned it or not. No big deal though.

Everything else is running great for the time being.
[Samsung Galaxy Nexus] MWisBest:
That's definitely in the works, I just don't want to introduce a bunch of changes at the same time to everything, as that makes it nearly impossible to figure out what I've changed that caused everything to screw up.

Well as for ART, it is a little sluggish at first but after a good 15 minutes followed by a reboot it seems to stabilize out for me.

Not sure about the whole Lockscreen thing, will have a look at it.
[Samsung Galaxy Nexus] metalspring:
[MENTION=3390093]MWisBest[/MENTION] why not just switch to a different kernel? It makes it easier than adding all those features yourself

I know of 2 that should be easy to switch out for the cm kernel- ASKP (all it requires is just using the milestone branch and changing the default defconfig in tuna's boardconfig to askpkk_tuna_defconfig)

and tiny kernel, which would need similar changes but with one more change to ramdisk (check his kernel script)

Also askp kernel is already set up to work just fine with linaro
[Samsung Galaxy Nexus] t1.8matt:
Does anyone know what would cause you from being able to use ART? I tried switching over and it stayed on Dalvik. Does xposed framework have an effect on it?
[Samsung Galaxy Nexus] metalspring:
yes, xposed does not work with ART, so it automatically switches you back to dalvik
[Samsung Galaxy Nexus] t1.8matt:
Thanks, I don't think ART is worth me losing xposed. Oh well, hopefully it's something that can be fixed in the future whether from the app side or rom side.
[Samsung Galaxy Nexus] MWisBest:
I had used another kernel previously, but ended up with a bunch of freezing that required at least 1 battery pull a day for users to fix. CM's kernel managed to not have this problem for some reason, so I've just stuck with it. I'll be pulling in things gradually, I just prefer the ability to screen everything again.

XPosed isn't compatible with ART, but I didn't think XPosed would have the ability to just completely break ART like that...
[Samsung Galaxy Nexus] HTCF4N:
Dude.. [MENTION=3390093]MWisBest[/MENTION], I just want to say that you are a genius! You are gifted! Keep learning and keep your head up, bro! :)
[Samsung Galaxy Nexus] hotrodwinston:
It's actually a script that is part of xposed to prevent bootloops - if it didn't switch back to dalvik it would never boot.
[Samsung Galaxy Nexus] botnryan:
I just flashed thia and damn! I'm very impressed. Very fast and smooth. Does anyone have any custom kernal suggestions? I usually go with mpokangs superram kernal, does it work well with this ROM?
[Samsung Galaxy Nexus] cujo6801:
That's the one I use...

Works great...

sent from the DOG pound