yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] raptir:
It's all listed right there in the PA GApps thread. The basic theme is that if an app in CM has a google equivalent (launcher, MMS, etc...) it replaces it with the Google version. They also have modular versions that allow you to decide what apps get replaced and what don't. Interestingly the calendar application is always replaced if you choose a package that includes it. I imagine there must be some conflict when having both the Calendar and Google Calendar apps installed.
[Nexus 5 Original Android Development] doctor_droid:
Just did a clean install of cm and i found it's uc'ed by default to 1948mhz.... Feature ??
[Nexus 5 Original Android Development] ssauger:
I think its thermal throttling. look some time later when you doesn't used your phone.
[Nexus 5 Original Android Development] magnamentis:
niet :)

sorry, albeit i do not like to contradict more experienced users i'm as sure as one can be that

this is not the case. i've never set anything on boot and always have the 2265MHz as max.

always ready to stand corrected but that would take many users seconding that UC :)
[Nexus 5 Original Android Development] doctor_droid:
May be i should retry another clean install..... Thanks mate...:)
[Nexus 5 Original Android Development] sjknight413:
It's always been 1948mhz Max for me too
[Nexus 5 Original Android Development] californicated:
Max clock is fine on my phone.
[Nexus 5 Original Android Development] magnamentis:
the question was !

the question was if it is a feature and indirectly if the rom (kernel) is underclocked by default.

my answer was that it is neither a feature nor is it underclocked by CM by default.

everything else like: who sees what which which measurement tool ( different monitors show different values ) has neither been

the question nor part of the answer. there are enough post on xda which state that there are kernel tweaking apps and

monitors of various kinds and that they measure differently and often show false results, which again is not what i

say it is, just that it happens quite often, i come across such posts like ( my app ( i.e. trickster mod) shows that and that value

albeit it's know as being false ( not real time at least ) etc. ect.
[Nexus 5 Original Android Development] sjknight413:
What are you on about?

My Max frequency on cm's stock kernel is 1948mhz. End of. I'm not reading it incorrectly, it's not being reported incorrectly, that's just what it is.

So sick of people on these forums who think they know it all and who think spouting a load of gibberish is going to prove someone wrong.
[Nexus 5 Original Android Development] doctor_droid:
[MENTION=5372360]magnamentis[/MENTION] - i used the inbuilt processor setting ... So i guess it can't be wrong .. I just reflashed stock...i did a clean install again and it was still at 1948... (A bit laggy on 1948mhz lol)
[Nexus 5 Original Android Development] thederekjay:
I guess you're the exception to the rule.. The facts are the facts. The code doesn't lie. So IMHO you're the only one "spouting a load of gibberish trying to prove someone wrong". Either way..

scaling_max_freq == 2265600
[Nexus 5 Original Android Development] wintrxtrem:
When the ROM is initially flashed the processor has usually been working hard for a while. Since it's been heating up it is automatically underclocked/thermally throttled to a lower clock until it cools back down, at which point max clock frequency is set back up to 2,265mhz
[Nexus 5 Original Android Development] gotzaDroid:
I mean no offense by this, but if you're worried about max CPU speed, why don't you try a new kernel or a kernel mod app like trickster mod.
[Nexus 5 Original Android Development] Sultanxda:
The default thermal thresholds in CyanogenMod are fairly strict: https://github.com/CyanogenMod/andr...b/cm-11.0/thermal-engine-hammerhead.conf#L135

From what I can tell, these are the current settings:

Threshold 1: CPU max-frequency is lowered to 1958MHz when the temperature reaches 40°C. At 38.5°C your CPU's max-frequency is returned to what is was before it was throttled (kernel default: 2265MHz).

Threshold 2: CPU max-frequency is lowered to 1574MHz when the temperature reaches 42°C. At 40.5°C your CPU's max-frequency is returned to 1958MHz.

Threshold 3: CPU max-frequency is lowered to 1190MHz when the temperature reaches 44°C. At 42.5°C your CPU's max-frequency is returned to 1574MHz.

You can try flashing the zip at the bottom of this post with more-relaxed thermal thresholds. I wouldn't recommend them for daily use; they are only to show that thermald is what's lowering your CPU's max frequency so quickly. Your CPU's max-frequency should stay at 2265MHz much more often with these thresholds. The modified thresholds are as follows:

Threshold 1: CPU max-frequency is lowered to 1958MHz when the temperature reaches 64°C. At 62.5°C your CPU's max-frequency is returned to what is was before it was throttled (kernel default: 2265MHz).

Threshold 2: CPU max-frequency is lowered to 1574MHz when the temperature reaches 69°C. At 66°C your CPU's max-frequency is returned to 1958MHz.

Threshold 3: CPU max-frequency is lowered to 1190MHz when the temperature reaches 74°C. At 70°C your CPU's max-frequency is returned to 1574MHz.

If you guys are going to whine and argue with each other then at the very least use ROM and/or kernel source code to back up your arguments...
[Nexus 5 Original Android Development] gpvecchi:
Very interesting! But thermal throttle isn't kernel related? Disabling it with Trickster will just let the shutdown temp, right?
[Nexus 5 Original Android Development] wp7chris:
What if you don't want google+ and google drive.... F that bloatware and wakelocks
[Nexus 5 Original Android Development] Sultanxda:
In official CM11, thermal throttling is controlled by a binary in the ROM: /system/bin/thermal-engine-hh

This binary parses a config file in the ROM to retrieve the thermal thresholds. The binary interfaces with thermal drivers in the kernel.

It looks like there is some emergency thermal-throttling code in the kernel: https://github.com/CyanogenMod/andr.../cm-11.0/arch/arm/boot/dts/msm8974.dtsi#L2137

But that's at 110°C :eek: The SoC might be hardcoded to reset at a certain temperature, but if it doesn't and you disable all forms of active thermal control then the kernel won't shut down the device when it reaches critical temps: https://github.com/CyanogenMod/andr.../cm-11.0/drivers/thermal/msm8974-tsens.c#L562

tsens_tz_notify always returns 1, so orderly_poweroff is never called: https://github.com/CyanogenMod/andr...b/cm-11.0/drivers/thermal/thermal_sys.c#L1469

https://github.com/CyanogenMod/andr...b/cm-11.0/drivers/thermal/thermal_sys.c#L1497

In other words, when the device reaches critical temps the thermal drivers in the kernel do nothing and instead defer to the thermal daemon (thermal-engine-hh) to make a decision, so disabling thermal control probably isn't a good idea :p You could just make the thresholds much more relaxed instead.
[Nexus 5 Original Android Development] thloe:
why no cm-2014-07-30 nightly for hammerhead? :(
[Nexus 5 Original Android Development] om22:
Nightlies failed for all devices beside of 5.
[Nexus 5 Original Android Development] californicated:
Will there be any further building attempts today?
[Nexus 5 Original Android Development] om22:
Usually not. Tomorrow is the next try.
[Nexus 5 Original Android Development] gee one:
The CM build server has been failing occasionally in the last few months, but home builds seem to be fine... do you know what the difference is? I know they have a more elaborate build system, but what specifically breaks?

OK, Jenkins is pretty cool, but I don't know what this error is...

make: *** [/opt/jenkins/android/workspace/android/cm-11.0/out/host/linux-x86/obj/EXECUTABLES/aapt_intermediates/aapt] Error 1
[Nexus 5 Original Android Development] om22:
Strange. Are you sure that your home build is from the same branch like the nightlies? Usually own build should also fail. Or maybe it's been already fixed in the last hours.
[Nexus 5 Original Android Development] gee one:
I am on the cm-11.0 branch and I build at 12:01 CDT. I run a make clobber before I build, but, I think, this would only increase the chances my homebuild would break.

I do add a few sounds and server CA certs to my build, but that shouldn't make it more break resistant.
[Nexus 5 Original Android Development] kellybrf:
I can't use superuser anymore. Flashed 7/28 the other day on a clean install (new phone even) and it worked as I initially set up a few apps. Now that I've gone back to set up more I can't choose "accept" when the dialogue pops up. It doesn't matter which of the 3 options I choose, tapping accept does nothing, not even the button press glow. Deny works fine. Apps that had already been granted root are working as expected, and when I open them the XXX has been privileges dialogue appears. Any thoughts?
[Nexus 5 Original Android Development] Tylog:
Flash SuperSu with recovery

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] thionylx:
I totally agree. For quite a while now I've just been restoring the few Google apps I actually use via Titanium Backup and I skip both of those as I do not use them.
[Nexus 5 Original Android Development] Doopliss:
The button is disabled because you have another app that is drawing over the superuser prompt.

See the comments here.
[Nexus 5 Original Android Development] kellybrf:
thanks, it turned out to be lux like that indicated
[Nexus 5 Original Android Development] blyndfyre:
Last full charge was 1 day 9 hours. Used quick toggle to turn off wifi about 1 hour after phone was unplugged from charger. Battery reports that wifi has been running for 1 day 9 hours. Is this possibly a bug?
[Nexus 5 Original Android Development] Digidice:
Hi

Just got my N5 and are going to install the CM 11 that i already running on an another device.

Is the M8 good to start out with for the N5 ?
[Nexus 5 Original Android Development] sjknight413:
I'd go with the latest nightlies.

There's been a whole host of reported problems with M8 but the nightlies, at least for me, have been extremely stable as of late.

Oh! just some advice as you're new to the nexus 5 like I was a few weeks ago, watch what kernels you flash if you decide to try any, the majority won't work on cm unless they are stated as being 'CAF' kernels.
[Nexus 5 Original Android Development] AA1973:
Check WiFi > Advanced Settings if "scanning always available" is ticked. Uncheck it.

Not a bug, it's a "feature" since 4.3
[Nexus 5 Original Android Development] bettypayne:
systemui battery drain

facing this again.. on 27/07 nightly... anyone else?
[Nexus 5 Original Android Development] draztikrhymez:
Had a few freeze and reboots today. Was at work so I don't remember exactly what I was doing. Do remember one time opening my case that has the open wake feature and the screen lit up but no picture. Then it rebooted.
[Nexus 5 Original Android Development] AndroidBR:
Today I've inserted a T-Mobile prepaid SIM card and I noticed that my quick settings panel and settings menu weren't behaving properly. The actual quick settings menu that allows you to choose LTE and so forth, wouldn't reflect my selection of "values" for the quick settings toggle (4G, 3G, 3G+2G, 2G). That menu for the toggle button simply disappeared from the CM settings menu when I selected 4G. Now, if I toggle 3G or 2G only in quick settings or under mobile network settings, the CM menu for the quick settings shows up again. What gives?
[Nexus 5 Original Android Development] Traged:
use intelli3g for this, automatic switchinch between sites. needs xposed framework and dont work with ART,dalvik only.
[Nexus 5 Original Android Development] gpvecchi:
Thanks! But I think that 110° shutdown works, as I get a reboot with Antutu and throttling off...
[Nexus 5 Original Android Development] Sultanxda:
If your phone actually got to 110°C then it would probably be permanently damaged (if the SoC doesn't die then at the very least you might end up with dead pixels). The SoC isn't designed to handle 110°C... Temperatures of 80°C and lower are usually considered safe; anything above that is putting your device at risk of being damaged.

Disabling thermal protection just for a number from a benchmark isn't worth damaging your device...
[Nexus 5 Original Android Development] McCol1:
Haven't rooted my phone for a while but about to do so today.

Just one quick question - Is USB Audio supported at the moment on this build? I've tried the search and the last few posts from June suggest some problems. Want to use the N5 with Fiio E18 and Spotify.
[Nexus 5 Original Android Development] thloe:
hi guys newbie-question: how does proximity-wake up work?
[Nexus 5 Original Android Development] djsubtronic:
He probably meant 110 F .. which is around 43 C.
[Nexus 5 Original Android Development] Bluewall:
Isn't 90°C the max for this SoC ?
[Nexus 5 Original Android Development] blyndfyre:
I didn't notice this feature was implemented. Thanks for taking the time to enlighten me.
[Nexus 5 Original Android Development] topgeardave:
According to qcom thermal throttling should hit hard at 88 degrees
[Nexus 5 Original Android Development] Oscarandco:
Hello, sorry to land in your conversation, but I'm new to CM and I just flash the nightly from 07/31/2014 and I would like to know if we can display notifications on the lockscreen. Thank's
[Nexus 5 Original Android Development] Bluewall:
Close enough :D

---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------

That's a really good question. I've seen the option but I have no idea how this even works and what's the actual purpose of it.
[Nexus 5 Original Android Development] gorgo80:
Just a question. Does anyone have problem to get lte working?
[Nexus 5 Original Android Development] Bluewall:
Well, not natively, but I'm sure you'll find plenty of apps that does this.
[Nexus 5 Original Android Development] wipian:
As hard as a time travelling DeLorean?

(Apologies for the off topic, I couldn't resist)
[Nexus 5 Original Android Development] Ntmcn:
here is a noob question, otg is working in this rom? how i enable it?
[Nexus 5 Original Android Development] Oscarandco:
Ok I found one on the Playstore: Notify me. I try this.. Thank's:good:
[Nexus 5 Original Android Development] zazza8:
When you try to turn on the display it uses proximity sensor (the same which turns the screen off when your on a call) to check if there is something at close range in front of the device, if there is the display won't turn on, if not then it will. It should prevent the display from turning on when the device is in your pocket or facing down on a table and the power button gets somehow pressed accidentally.

It worked on 20140727 and 20140729 but it caused the proximity sensor to be on all the time. That problem is fixed on 20140731 but now it doesn't seem work at all because the sensor gets turned off too early for our device.
[Nexus 5 Original Android Development] Mr.World.Wide:
hi

i have a problem in this rom

this rom is very good and fast

but in skype , smile icon is very very small

Is there a way to solve this???

[IMG="my skype problem"]http://files.cinemacenter.ir/images/8a9rtnijbvrnw8h9ngd.png[/IMG]
[Nexus 5 Original Android Development] gotzaDroid:
I noticed that on the 7/31 nightly, my phone seemed to hang on H+ longer than usual. The phone will connect to LTE, but not in places like it did before. Mind you though, that I work overnights and flashed the latest nightly at 5am and only messed with it for 2 hours before I just woke up a bit ago. I'm currently on WiFi.
[Nexus 5 Original Android Development] RootTheMachine:
I may be experiencing this as well. Just updated from 7/10 to 7/31 and the phone connects to H+ or struggles to connect to LTE to seemingly no avail.
[Nexus 5 Original Android Development] reinert012:
7-25 nightly has ROCK solid for me. Been using it as a daily driver even traveling across states for business with zero issues. Battery is totes cray cray :)
[Nexus 5 Original Android Development] Sultanxda:
Took another look at the kernel and found this: https://github.com/CyanogenMod/andr...m8974-hammerhead/msm8974-hammerhead.dtsi#L140

So I guess the limit is at 90°C. CM cherry-picked a bunch of commits from CAF and this was one of them: https://github.com/CyanogenMod/andr...mmit/b3bbab7831a04590f5dc0b702f781641ee5e2b5b

I saw 110°C and got confused :p There's a bunch of thermal parameters scattered everywhere in arch/arm/boot/dts and I'm still not quite used to it (I've mostly played with MSM8660 kernels so far; I've only been playing with MSM8974 code for a couple weeks). But I can't find where the thermal drivers shut down the device at critical temps since orderly_poweroff is never used :confused:

[MENTION=4909585]gpvecchi[/MENTION] said he got a reboot with thermal control off, so maybe something else caused his device to reboot since the thermal drivers are designed to shut off the device at critical temps instead of rebooting it. If anyone here is familiar with the thermal drivers and what happens at critical temps when the thermal daemon is disabled then it would be awesome if you could shed some light on this.
[Nexus 5 Original Android Development] Gips3yD4ng3r:
I just saw this today, will it work with this CM11 ROM

Sent from Nexus 5
[Nexus 5 Original Android Development] jrny99:
i'll purchase it and let you know k . . .
[Nexus 5 Original Android Development] Gips3yD4ng3r:
Awesome, yea let me know cause if it works i jumping on that real quick

Sent from Nexus 5
[Nexus 5 Original Android Development] Wh1t3Rose:
Just bought it myself. Looks great. I havent noticed any issues. I'm on the 28th nightly. Just make sure you are on a recent nightly. It does matter. And be sure to read the description. :)

Side note: I got to leave the first review for the theme :D
[Nexus 5 Original Android Development] Gips3yD4ng3r:
Make sure to read the description in the app?

Sent from Nexus 5
[Nexus 5 Original Android Development] Wh1t3Rose:
Description for the app in the play store :)
[Nexus 5 Original Android Development] vtec_:
Yup it will work. Just be careful doing a lot of multi tasking as the phone is prone to lock up while playing USB audio.
[Nexus 5 Original Android Development] dannyella:
Massive battery drain since proximity wake was added. I'm struggling to get 4hrs SOT.:(
[Nexus 5 Original Android Development] c_86:
Jesh. Only 4hours of on screen time. Oh no. I barely get 2.5.
[Nexus 5 Original Android Development] zormoff116:
Guys do not know why, when any operation with root explore there is an error worth last night? Does anyone have this problem and how to fix it
[Nexus 5 Original Android Development] Gips3yD4ng3r:
Ok i will and will the 7/31 nightly work fine i know you have the 7/28 nightly

Sent from Nexus 5
[Nexus 5 Original Android Development] reinert012:
You can then that feature off
[Nexus 5 Original Android Development] Wh1t3Rose:
It should [emoji106]
[Nexus 5 Original Android Development] gorgo80:
To bad LTE is not working so good
[Nexus 5 Original Android Development] Gips3yD4ng3r:
Nice ill check it out and ill let you know

Sent from Nexus 5
[Nexus 5 Original Android Development] Gips3yD4ng3r:
Since its a nightly build can you just dirty flash the updated nightly with out wiping the phone clean

Sent from Nexus 5
[Nexus 5 Original Android Development] Mr.World.Wide:
Is there anyone who can help me?????????
[Nexus 5 Original Android Development] sylar945:
How can I change the lockscreen wallpaper?
[Nexus 5 Original Android Development] baggord:
Settings>themes>lockscreen wallpapers
[Nexus 5 Original Android Development] alexiuss:
Cyanogen touch Recovery is coming, bye bye CWM...

CyanogenMod@Nexus5
[Nexus 5 Original Android Development] swat4samp:
Source?
[Nexus 5 Original Android Development] kornklown69:
yes!
[Nexus 5 Original Android Development] alexiuss:
http://review.cyanogenmod.org/#/c/63676/

CyanogenMod@Nexus5
[Nexus 5 Original Android Development] swat4samp:
Wow, my Nexus 5 is ready :D
[Nexus 5 Original Android Development] gotzaDroid:
I hate to ask as I might sound dumb, but will CM'S recovery be full featured like CWM touch? At least is that the consensus? I'd hate to upgrade to CM'S recovery and only be able to flash CM stuff and not custom kernels and what not.
[Nexus 5 Original Android Development] Smallsmx3:
I'm sure CM recovery is based off of CWM
[Nexus 5 Original Android Development] maidenboston:
hope they add multi file flash in the recovery
[Nexus 5 Original Android Development] i.adrian:
I'm using the 1.08. nightly but I cannot install any theme. I've tried a bunch of them but they all failed. Anyone have this issue?
[Nexus 5 Original Android Development] Elluel:
If applicable: http://xdaforums.com/showpost.php?p=54143201&postcount=2221
[Nexus 5 Original Android Development] Smedo:
Last few nightlies I have an issue with the menu (auto hide) button in the navigation bar. It keeps active even when there is no menu option. Even in home screen (Google now) it keeps active. When enforcing the auto hide version again of the menu button in the navigation bar, it's good for a while and then it comes back and stays active again...am I the only one having this?
[Nexus 5 Original Android Development] Doopliss:
If other roms don't have the same problem then you should probably submit a bug report. I think the devs who read this thread mainly work on kernel stuff so you're unlikely to get help here.

Instructions are on the wiki. Bugs aren't generally accepted from nightlies so you need to be on the latest 'M' build.
[Nexus 5 Original Android Development] gotzaDroid:
You're not alone. Selecting always hide seems to be the only way to fix it for me.
[Nexus 5 Original Android Development] Darkside14:
For me the same, but i've choose to always show them
[Nexus 5 Original Android Development] kornklown69:
looks like tomorrow implements cm recovery update!
[Nexus 5 Original Android Development] hanschke:
we will see if it is better as other :rolleyes:
[Nexus 5 Original Android Development] sjknight413:
So it isn't in the latest nightly then? Commits point to it being there
[Nexus 5 Original Android Development] magnamentis:
which of the commits in the changelog points to that ?

[IMG="02.08.2014 Changelog"]http://xdaforums.com/attachment.php?attachmentid=2880793&stc=1&d=1406990170[/IMG]

http://www.cmxlog.com/11/hammerhead/
[Nexus 5 Original Android Development] sjknight413:
Yes,

' sr: Touch UI (android_bootable_recovery-cm) '

http://review.cyanogenmod.org/#/c/63676/

Why screenshot the commits I have clearly seen when I said 'commits point to it being there'?
[Nexus 5 Original Android Development] gotzaDroid:
It's out, anyone try the new recovery yet? I don't want to waste time updating if it's crap.
[Nexus 5 Original Android Development] gee one:
For the home audience, I think you need to set RECOVERY_VARIANT=cm to build the cm recovery.... building as we speak...
[Nexus 5 Original Android Development] gee one:
I built it for the mako- I haven't tested it too thoroughly, but I don't see a backup/restore menu- just wipe and flash. Cache will wipe without a confirmation dialog, but user media and factory data reset will ask for confirmation before wiping.

There is no advanced menu to reboot to bootloader or reboot recovery.
[Nexus 5 Original Android Development] Spinergy02:
Could someone please explain why we even need a cm recovery when we already have two that are already working just fine?
[Nexus 5 Original Android Development] kornklown69:
The question is why not... its a development phone lol
[Nexus 5 Original Android Development] topgeardave:
Just for lolz
[Nexus 5 Original Android Development] Bluewall:
Oddly accurate.
[Nexus 5 Original Android Development] sjknight413:
So it definitely isn't worth switching from TWRP then i guess? haha
[Nexus 5 Original Android Development] gee one:
Yeah, I would hang on to what you have now. Maybe they add more features soon...
[Nexus 5 Original Android Development] gorgo80:
I think I will stay with cwm ?
[Nexus 5 Original Android Development] dEris:
TWRP > CWM

-------------------------------------------------------------------------

[ DEVICE : N5 ] [ ROM : CrDROID ] [ KERNEL : BIGBUM ]