yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sickopsycho:
I have had 0 issues and have been running this rom for the last couple months- done dirty flashes every time and updated as soon as new builds were out. For whatever reason I'm having trouble getting the latest builds to work. It *might* be a kernel issue- but the kernel I'm trying to run seems to work on others phones... anyway with the 12/13 build I got a bootloop, flashed back to nandroid (previous build). Downloaded the 12/15 with the mini-modular gapps- flashed that and it booted. switched to art and seemed ok. flashed the linaro grande askp kernel and when it booted it loaded my lockscreen underneath where the window said it was still optimising my apps. it was stuck- wouldnt go past 120/151 apps and couldnt unlock the screen or anything. battery pull, booted to lockscreen. set the phone down for 5 seconds and it rebooted itself and bootlooped. I had switched back to dalvik prior to flashing, wiped system, cache/dalvik- I even checked file integrity (which i rarely do- shame on me). Anyone on this kernel got any advice on what I might have done wrong? doesnt *seem* to be a rom issue- the rom *seemed* to load fine with current config. I'm about to flash back now without the kernel and see how it goes...
[Samsung Galaxy Nexus] metalspring:
do not use the linaro grande version, use the regular grande version

The linaro one was made with linaro 4.8 toolchain which does not work well for kernels (he did it as a test to see if anything had been fixed with linaro on it)

The regular ones are made with the linaro 4.7 toolchain which works just fine

Btw, [MENTION=3390093]MWisBest[/MENTION] what do you use to build the kernel in your rom anyway? I always use linaro 4.7 or sabermod 4.8 for arm-eabi
[Samsung Galaxy Nexus] MWisBest:
It's just building with the AOSP stock 4.7 toolchain for now. Don't see a reason to use anything else at this point, without adding more things in like overclocking and the fine-tuning-tweaks that other kernels have I don't see a reason to use it. I'm not going kernel-wise for speed, I'm going for stability at this point. Once the other bells-and-whistles are in place, then there will be more of a reason to try and squeeze every last drop out of the kernel.

EDIT: Also, all these "grande" things are making me think of Starbucks, haha. Didn't place it until now.

(For those unfamiliar with Starbucks, you order the drink size in mostly foreign language, one of them being "grande.")
[Samsung Galaxy Nexus] taz1458:
I'm glad I'm not the only one that was thinking that. Any luck with the handcent issue?
[Samsung Galaxy Nexus] Sheetzie03:
Apologies for the OT, but I have a question for you. Can you tell me why you like handcent so much?

Thanks

?Turnt Up-KK Metal with THE best Audio Improvement Patch out there↔@Misledz Xlouder?
[Samsung Galaxy Nexus] taz1458:
Just like all the customization and the fact I can change my ring tone. I can put the espn ring tones for espn, the penguins goal horn for Pens texts, etc. I'm using gosms for now. Just about the same.
[Samsung Galaxy Nexus] MBQ_:
Killin' it bro.

Good work. :)
[Samsung Galaxy Nexus] db306:
Silly question but any idea how to disable Whisper Push?
[Samsung Galaxy Nexus] MWisBest:
I haven't had any luck with it yet, no. I don't mean to be a burden but could you throw up another logcat but this time with the 2013/12/15 build? It might help a bit.
[Samsung Galaxy Nexus] taz1458:
I will later tonight
[Samsung Galaxy Nexus] db306:
MW is it possible to just delete Whisper push. I originally activated it and now all my texts go to people showing a different # etc and they have no idea who I am lol
[Samsung Galaxy Nexus] avtomat:
I deleted app data from whisperpush and messaging appears to be working as normal.
[Samsung Galaxy Nexus] botnryan:
I'm not real impressed with batt life so far, but its not worse than any others I've had. But besides that, this ROM with mpokang superram kernal is the fastest, smoothest and most bug free 4.4 ROM I've tried so far. Excellent.
[Samsung Galaxy Nexus] vitokes:
Hey mwisbest is it possible to use your fast charge mod with another ROM? I gave my girl my nexus and I missed being able to use fast charge and mass storage at the same time.
[Samsung Galaxy Nexus] MBQ_:
Give it a few days, everything will get better.

Play around with governors and stuff until you find what works for you. Definitely a trial and error thing my friend. :)
[Samsung Galaxy Nexus] MWisBest:
Well if it's fast and smooth, it should save some time and in that sense increase battery life! :P

This is a kernel change, not a ROM change, and I don't know if it'd work with another device's kernel/hardware. SCH-I535... is that a Galaxy S3 or so? I'll check that when I get home tonight. I could check if the patches apply to the kernel OK and you could ask some existing kernel devs for the device to give it a shot. I think the change effects some USB hardware that's sort of an industry-standard for this sort of application (application meaning like, usage for hardware like a smartphone), so the chances are good, especially since I at least know that's a Samsung device, lol. The reason I'd prefer an existing kernel developer for that device decide whether or not to include it is because they'll know the device better than I do and I'm not comfortable developing for a device I don't have myself, I'd hate for YOUR phone to fry because I couldn't test and double-check that there were no problems with it myself.

This. Every device is different. The way I like to look at it, is that microchips are like snowflakes. They're not going to all look (and in this case, behave) the same way, the goal of the software developer is to get something that targets the average device (full of different microchips, not just a single thing). Since the average user of an electronic device won't have a clue as to how to adjust those things, the developer is forced to lock all those things in so a person who runs their CPU at the lowest frequency 24/7 doesnt complain they have bad performance, etc. That's where we come in at XDA, and give users the ability to adjust all these things, so they can tune things to their device or own personal preferences.

Quick development update... I'm doing some work to fix every last bit of code I can that the compiler complains about with some of the optimizations it would make. Some things that couldn't be optimized before included stuff like surfaceflinger, which could certainly be nice if it was faster.

Sent this on my phone, ignore any typos >.
[Samsung Galaxy Nexus] botnryan:
I didn't mean my comment to come across as complaining lol! This things my new daily driver! Its amazing. Honestly battery life is an issue that can't be solved with these silly devices without a huge humpback battery pack the size of a rumble pack for old game boys.
[Samsung Galaxy Nexus] taz1458:
Your wish is my command:

http://pastebin.com/SjyVspvm
[Samsung Galaxy Nexus] vitokes:
You're amazing! At least my curiosity was pleased. Not a total hurry though at all. Not even a big priority cause I know you have the nexus going and this community really needs it. So don't sweat it! Thanks for the info though.

---------- Post added at 04:57 AM ---------- Previous post was at 04:50 AM ----------

Who's wish is this? Lol :what:
[Samsung Galaxy Nexus] taz1458:
Mw's. My logcat from handcent fc'ing.
[Samsung Galaxy Nexus] MBQ_:
2743 and 2751

Looks like it was trying to grab a function or a piece of code in that file but failed to, so it couldn't open.

Could be wrong though
[Samsung Galaxy Nexus] taz1458:
Idk if it is or not. I'm not leaving to find out either. Lol. I'll work with gosms for now. No biggie, just wanted to help you out a bit.
[Samsung Galaxy Nexus] swarlesbarkely:
Am I the only one who feels like cm is kinda betraying the development community?
[Samsung Galaxy Nexus] Rushead:
Just another example of the ultimate human condition: greed. More and more are individuals being taken advantage of by the mass. Empathy seems to not apply in the face of business. "Good" business practices maximize profits for shareholders regardless of detrimental effects. This just contributes to the dehumanizing of society. Individuals feel less morally beholden to one another as a result.

Hopefully we can maintain our humanity in light of such and remember that as humans we have a moral obligation to one another. The corporations will persist, but let not them define us. Thanks to the xda for an awesome community of humans. (Sorry for the rant / ot)

Sent from a flashead cracker.
[Samsung Galaxy Nexus] MWisBest:
No worries, it could simply turn out to be an issue with the last batch of builds. [MENTION=4244313]MBQ_[/MENTION] was correct in saying that a lib Handcent was using was referencing something that didn't exist, but that thing that didn't exist is something I remember experimenting with when I was attempting to use AOSP's "master" branch of ART as it required me to add it to get the build to work (libunwind was what it was). Either I need to include libunwind, or maybe some remnant of it was left in these last couple of builds and that caused the issue. So when the next build comes out, if it still has issues, I'll try adding libunwind back again to see if that resolves it.

Don't get me wrong here, I'm not saying CM is totally wrong for what they're doing. Look at MIUI, stealing CM's code and then passing it off as their own to start a million dollar business. If that happened to my project I would certainly feel that I should do the same thing as a way of sticking it to MIUI, but in the process I wouldn't turn my back and go against many of my project's contributor's wishes. In a way, they're somewhat doing what MIUI did, and hopefully they can realize that. There's still a way for them to dig out of this little hole they might end up in, I do have faith that they'll figure things out and do this the right way. One thing in particular they could maybe do is keep some of those things that violated CTS but that users enjoyed, but disable those things just in builds done for an official distribution sort of thing. This idea of contributors unknowingly signing away the rights to their contributions is something that should be looked at more closely, I understand the need to do this for a business model and that it's common in the business world for that dual-license sort of thing, but rather than have full rights to do whatever with the code being given to CM there should be a separate actual license. One thing I've seen that I found interesting is a dual GPL/MIT license where things are licensed under GPL, but then after X amount of days it is considered licensed as under the less-restrictive MIT license to allow somebody to pick up the project under a less-restrictive license in case the project dies out. Obviously that specifically is not the right license for CM, but it shows there are other ways to protect contributor's rights but still allow for a business model of some sort. Or at the very least just make it more transparent with the contributors as to what CM can and will do with their stuff.

Don't turn your back on CM or anything just yet, at the present time I don't think there's anything big to be worrying about.

Also, I'm going to make a little "CMApps" package in the near future, where I'll stick things like CMAccount and other apps that are kind of developed "in-house" by CM to allow users the choice of whether or not they are comfortable using them. I know some people are already annoyed with a few of the things CM has added, such as that WhisperPush thing, so although it'll add yet another thing to download it'll give you guys some more freedom and choice in the matter of these things.
[Samsung Galaxy Nexus] taz1458:
No worries mw. I'm not worried about it. Also, just an idea, there are some roms as you are flashing there are options to select different things. Always thought that was pretty cool. Maybe down the road with your gApps you could try that. I have no idea how much work would be in it however.
[Samsung Galaxy Nexus] Sheetzie03:
What in the world are you talking about❓?

?Turnt Up-KK Metal with THE best Audio Improvement Patch out there↔@Misledz Xlouder?
[Samsung Galaxy Nexus] taz1458:
Read the link on the last page about cyanogen mod
[Samsung Galaxy Nexus] Rushead:
Sent from a flashead cracker.
[Samsung Galaxy Nexus] Rushead:
Anyone try the latest Philz?

http://d-h.st/users/philz_touch/?fld_id=16692#files

Supposedly kk friendly. Haven't had the chance to try it yet...

Sent from a flashead cracker.
[Samsung Galaxy Nexus] huizingajm:
Wi-Fi

So I have two issues and both deal with Wi-Fi. The first is when I leave the range of a wireless network and then go back to same network my phone will not reconnect to the network unless I turn off Wi-Fi and then turn it back on. Second issue is randomly I can start downloads from Google Play or from Chrome and the Wi-Fi will just drop and then have to wait for it to start back up.

Using Mini Modular PAGapps, Mpokang v10
[Samsung Galaxy Nexus] taz1458:
Mine does the exact same thing. I'm also running the same setup. I've just kind of dealt with it.
[Samsung Galaxy Nexus] Sheetzie03:
There is a WiFi fix in metalsprings thread, check it out. If its the same issue, it fixes it

?Turnt Up-KK Metal with THE best Audio Improvement Patch out there↔@Misledz Xlouder?
[Samsung Galaxy Nexus] taz1458:
In the cmetal thread? I couldn't find one.....

EDIT: http://xdaforums.com/showthread.php?p=48471109
[Samsung Galaxy Nexus] MWisBest:
Well, the only thing I've noticed is that when I check my phone after it's been sitting for a while and probably in Deep Sleep, it takes a minute or so for the WiFi connection to stabilize. I'll try and take a closer look at what could be going on with WiFi, I might be able to update the kernel's bcmdhd drivers which should improve things.

I'll have a look at that, thank you.
[Samsung Galaxy Nexus] huizingajm:
I don't have Low Signal. My signal is almost always max. I will look at it though.

I will try and verify about the deep sleep. It does happen during the day but there are periods of time during the day I do not use my phone. I do recall that a couple times it has been when I first woke up.
[Samsung Galaxy Nexus] Rushead:
The only issue I've found is that I can't "back" out of dialer.

No wifi problems. Just now left & came back home. Reconnected no problems.

Sent from a flashead cracker.
[Samsung Galaxy Nexus] itzweber:
So, I also posted this in another thread, but what I thought was one of the coolest features of KitKat (Supported Nexus devices only, apparently..) was the new Google Dialer app with local business search. This article from Android Police has one of the first working ones I've seen, and it is working from the limited testing I've done on this ROM. Just tested the recovery flashable zip linked in the article.

I think the only other issue I've had so far is that AppOps no longer works, but apparently that can be fixed with an Xposed module. Thanks for all the effort MW!
[Samsung Galaxy Nexus] invisibastard:
I've been on the 12/15 version without a single problem. I've been running Tiny kernel with Nephalim's settings and the thing is running like a champ. I might be crazy (actually, I probably am) but I always wipe system when I flash a new ROM. A leftover habit from my Nexus S days. Would that make any difference in me not having problems? Or is it kernel related? Just thinking out loud.

Off topic, I read this article and it reminded me of the CM discussion in here lately:

http://prog21.dadgum.com/97.html

Thanks for all the work and a great rom MWisBest. You have a great future ahead of you.
[Samsung Galaxy Nexus] metalspring:
That probably wont help here lol

That was to fix not having the toro device repo set up properly for omni rom, cm already has it fixed

(toro needs a slightly different wifi driver than the other variants and I forgot to add that part into the toro repo for omni rom)
[Samsung Galaxy Nexus] taz1458:
Actually, I just got home and it's the first time I can remember this connecting back to wifi in a long time. Although, since about yesterday morning this thing is getting laggy. Might try to re-flash the super ram kernel. Also, if I get a phone call, it seems like it takes forever for the screen to come on.
[Samsung Galaxy Nexus] hotrodwinston:
+1
[Samsung Galaxy Nexus] MWisBest:
I might be uploading a new build soon, but it'll just be in a post in this topic and not put in the main topic. I'm trying some new experimental changes, so for those brave enough to give it a shot (it's "make sure you have every single thing on your device backed up and a copy of it on your computer" serious), you can try it. Should be within the next 12 hours, I don't think this build I'm about to flash right now is going to boot at all honestly but if it does then it'll be in the next couple of hours.
[Samsung Galaxy Nexus] MWisBest:
cm-11-20131219-FML-toro-DEBUGTEST.zip (192.47 MB)

Not putting this in the XDA Download section here as it lists everything in plain view, if Dev-Host is giving you problems let me know and I'll put this up on another mirror.

I'm not going to list off what I changed in an attempt to avoid any sort of placebo/nocebo effect, just let me know if it seems faster or slower or a bug was fixed or a new one was created etc. Give it some time to stabilize, it's always a tad laggy after an initial flash. Get me some logcats if anything goes wrong if you can!

A system wipe is absolutely required when testing this or going back to a different build after testing this. A data wipe shouldn't be necessary if you're coming from a semi-recent FML build.
[Samsung Galaxy Nexus] grandzu:
Be sure you deleted the default lock screen clock and replaced it with the cLock widget
[Samsung Galaxy Nexus] David 617:
Clean flashed latest build. I also flashed Ampeferic's Grande kernel. I got one freeze-up so far on dalvik. Attached dmesg below. For some reason I could not pull the last_kmesg, I tried repeatedly but it seems to not exist...

Other than that, it seems to be a tad snappier (although that can just be b/c it is a clean OS). No other bugs to report. I haven't switched to ART yet, but I will post back once I do.

Thank you for all your hard work. I posted a link to this thread in Vanir's to let those devs know of your work. They seem to be having the linaro+art issues which you solved.

Edit: running on ART now. Definitely feels smoother. So far no crashes.

Edit #2: found a rather large bug. YouTube doesn't work. It seems as if the videos are loading based on the bar the bottom, but the play button will not work. The screen flickers for a moment, but returns to the pause state. I will attach a logcat as soon as I am at my laptop.
[Samsung Galaxy Nexus] MWisBest:
Yeah I can confirm the YouTube thing and I'm pretty certain where the issue was introduced, if my theory is correct not only will YouTube videos be broken but all videos using the AVC video codec (h.264) will be broken as well.

EDIT: By the way, as to what was changed with this build from previous builds:

- Enabled Link-Time-Optimization.

- Attempted to fix as many aliasing violations as possible to allow for further optimization of code. (This is most likely where the YouTube breakage came from, as there were some things I wasn't completely sure of)

--- The only places where there are still aliasing violations are in openssh (external/openssh) and voip (frameworks/opt/net/voip). That's quite the change from having them in a good dozen or so other things. One of the places that had a really bad and hard to fix aliasing violation was in surfaceflinger, so I figured out a way around it. I definitely think that's making a difference.

Or... the YouTube problem may have come from what this fixed, as I didn't have this yet in that build I threw up last night: https://github.com/MWisBest/android_frameworks_av/commit/dbb2bb90acd47a53d84809b1aa150bac6093f752
[Samsung Galaxy Nexus] metalspring:
No worries, its not anything you did lol

Its a cm mistake :p

You probably didnt get this commit added in before you did your build-

http://review.cyanogenmod.org/#/c/56013/
[Samsung Galaxy Nexus] David 617:
I tested MXplayer and stock player and both were able to play videos recorded with my phone.

Thank you both for all the work you put in to keep Toro alive.

#ToroForever ;)
[Samsung Galaxy Nexus] heXacode:
That was it. I had no idea those 2 weren't related.
[Samsung Galaxy Nexus] MWisBest:
I'll get a new build up after school today, should be 5 to 6 hours from now and it'll have LTO enabled and that YouTube bug fixed (speaking of that bug, have a look at the comment I posted here... http://review.cyanogenmod.org/#/c/56013/ (you should be able to tell which is mine >.<)). After that build, I plan on experimenting with different ROM bases to possibly use instead of CM. That YouTube bug was kind of the last straw for me with CM. I don't know if I'd use OmniROM as a base, I don't want to step on metalspring's toes since he's already doing a great job with OmniMetal, but I don't know what that really leaves either. I think I'll just do a build for other ROM bases, see which I like best feature-wise, and ask you guys your thoughts on it. If everything checks out with it, I'll add in all the FML optimizing stuff to it.
[Samsung Galaxy Nexus] metalspring:
Vanir is good, plus they already have all the fixes needed for linaro/sabermod 4.8 (actually I think they use codefirex's 4.8 toolchains, which also have lots of optimization like linaro and sabermod) except for the ART issue lol

Or there's carbon rom as well, or you could give codefirex a go

Or, if you feel adventurous, there is always aospa (this might be tougher since they use their own proprietary repos see here)

or you can always build omni rom as well, afterall only 2 people I know of are making builds for the gnex, playfulgod and myself
[Samsung Galaxy Nexus] t1.8matt:
If you could somehow build some 4.4 Carbon that would be amazing. That's the one thing I miss since switching to 4.4 is all of Carbons features. But I don't know if it would be possible if their code isn't available yet.
[Samsung Galaxy Nexus] David 617:
I second vanir. Their 4.3 ROM was the fastest ROM for toro. They do some crazy optimizations to Android and to the compilers. You would be a valuable asset to their team as they move forward with 4.4
[Samsung Galaxy Nexus] MWisBest:
I'm gonna try Paranoid Android first. I synced up their code last night. I did get an idea though to not have to worry about downloading all of a ROM's code, since the majority of things are just straight from AOSP I can just copy my AOSP directory to a new folder and then change where repo gets the manifests for that directory, and then I'll only have to sync whatever changes the ROM introduces (which won't be nearly as much as all of AOSP's code).

As for basing off of a ROM that's already got a lot of the Linaro fixes, I almost think it'd be easier to not do that, otherwise I'd have to sort out what changes I need to grab that I've already made since Linaro is actually behind on lots of things. I don't think they fixed any new aliasing violations that popped up in KitKat, and they aren't even able to compile with C++11 enabled.
[Samsung Galaxy Nexus] afguy0127:
Well whatever you do, I'm on board. Have loved this ROM so far. Though I do have to say I'm excited about you trying Paranoid. I came from that ROM before this and I loved the feature set.
[Samsung Galaxy Nexus] Sheetzie03:
Very anxious to get a build running that doesn't have the YouTube issues

?Turnt Up-KK Metal with THE best Audio Improvement Patch out there↔@Misledz Xlouder?
[Samsung Galaxy Nexus] Dahsar:
Is anyone else having thumbnail issues with certain apps like pulse or even gallery
[Samsung Galaxy Nexus] MWisBest:
https://github.com/CyanogenMod/android_frameworks_av/commit/a0e62824ae1516bab95e945c6ac664e53dee36d0

Imagine that, 3 hours after I had posted that comment on the review, he goes into the git repo and reverts his crap. ^.^
[Samsung Galaxy Nexus] taz1458:
Hey mw, has anyone else had issues with the 12/13(whichever was previous to the one you put out a day or two ago) whenever a call is coming in? It takes forever for the screen to light up when a call is coming.