yashsingh1/xdaforums huggingface dataset:
[HTC One S] aegentirony:
I've been googling lol and I've found a few new to me build prop mods ...I'll post them after some more testing but I believe I fixed the backlight issue
[HTC One S] horno46:
I've lost the three dot menu button in Chrome on the last couple of nightlies.
[HTC One S] Phuturist:
Is changing the radio through the temporary radio installer still usefull? I always have had better signal with the 1.15EU radio but I read somewhere that since some time updating the radio for CM doesnt do much as it uses the radio as seen in the bootloader. Can someone shed some light on this for me?
[HTC One S] usaff22:
Try unmapping whatever button press you have set to the menu key in Settings > Buttons
[HTC One S] Rapier:
Not it isn't. CM11 as well as all KitKat ROMs uses the one in bootloader
[HTC One S] horno46:
Nope still not there. I think the setting for force 3 dot overflow is now missing, either that or I can't remember where to find it.
[HTC One S] usaff22:
Seemed to be missing on the December 12 2.16 HBOOT build too.
[HTC One S] Spardantex:
In CyanomogenMod page, about Ville, there was a relase of 16/12/13.. Someone has try it?
[HTC One S] Phuturist:
Ok, thanx for the quick reply. Is it possible to change the radio in the bootloader?
[HTC One S] Rapier:
Of course. From the same thread in which is the temporary radio, you should flash V6 radio for Sense ROMs. That is writing the radio to bootloader.

Sent from nowhere over the air...
[HTC One S] Spardantex:
And...? xD
[HTC One S] qwerty warrior:
can some one help me out

the only good radio i have ever used was the first one that came with ICS (4.0)

everything after that had its own set of problems

(calling issues)

1.13 was really bad

1.15 has weird issues different than 1.13

ill try 1.20 and see how that goes

is there a download for the ICS radio (aosp) ?
[HTC One S] grorg:
What exactly are you interested in?

I think it just a minor update
[HTC One S] Yves88:
I came across this problem as well. While being only a minor issue, it did disturb the consistency of the button placement.

As ufass pointed out, the menu button overflow option is missing since a couple of updates, but I was able to fix it by removing the menu-function from

all

of my soft button keys (back, home and recent apps).
[HTC One S] Spardantex:
I wrote'' someone has tried it?''

you said'' yeah'' (meaning that you've tried it).

So, have you tried the latest version? There are changes?
[HTC One S] Yves88:
As far as I know there are no significant changes.

So like Grorg asked: are you looking for a particular change, because giving a detailed change report is besides being incredibly time comsuming also rather pointless since a new nightlys build is probably right around te corner changing things around again ever so slightly.

So why don't you just try it out yourself?
[HTC One S] Spardantex:
Becouse i'm on hboot 2.16... I doesn't say if is for 2.15 or 2.16
[HTC One S] Yves88:
In which case: why does it matter to you?

As far as we know the newest 2.16 release won't be the same as the 2.15 release of 12/16/13.

Why don't you downgrade to 2.15? The official CM11 release probably won't be released for 2.16, meaning you have to wait for the unofficial versions to be released and you can experience the newest CM11 goodness of the bat ;)
[HTC One S] Spardantex:
Wtf? Bro, I asked a simple question which was to end with a simple answer. Do not turn round to the question, we avoid unnecessary posts.
[HTC One S] Brushstroke:
Hey guys. I've been using CyanDelta for updates and I got a notice last night about a 12/18 nightly but I still don't see it on CM's website. Anyone else using CyanDelta get notified of this?
[HTC One S] el_smurfo:
I think get.cm is having issues. Jenkins made a 2/18, but it never appeared to download. Changelog was pretty minimal, so its no loss to stick with 2/16
[HTC One S] Yves88:
And to that simple question a simple answer was given, after which you asked a more extensive answer which neither Grorg nor a where able to give for the reasons I have given you.

But let me repeat the answer to your initial question and your first follow-up question:

You: Is there someone who has used the CM11 release of 12/16/13

The answer given: Yeah (fully answering your question)

To which you reply: And?

The answer given: What exactly are you interested in?

To which you reply: So, have you tried the latest version? There are changes?

To which I reply: As far as I know there are no significant changes. With the suggestion to try it out yourself, because why wouldn't you?

So every (simple) question asked was answered, no?
[HTC One S] justaway2:
http://changelog.bbqdroid.org/#/ville/next

Bookmark this page. Then you won't have to keep asking the same question every day.
[HTC One S] lejohn:
Should you downgrade from 2.16 to 2.15 and flash the recovery, keep in mind it needs to format your SD card. So back up before doing this.
[HTC One S] el_smurfo:
Second day in a row that CM download site doesn't update, so I guess it's OK to get right from Jenkins

http://jenkins.cyanogenmod.com/job/android/51836/

EDIT: [MENTION=3672968]kavafree[/MENTION] informed me that you can find all current downloads at

http://beta.download.cyanogenmod.org/builds/ville

I guess they made the switchover without telling anyone (including their cmupdater app that still lists 12/16 as the latest).

Thanks kavafree
[HTC One S] Brushstroke:
I see. I went ahead and installed 12/18 anyway. Seems to be no difference at all other than the audio stuttering problem when changing the volume has been fixed. I'm pretty amazed at how stable this is compared to the disaster that was 10.2.
[HTC One S] el_smurfo:
TBH, the bootloop fix was added to 10.2 also...just most of us here had moved on...BTW, second 12/18 hit Jenkins a bit ago...getting ready to try flashing with Flashify instead of FlashImageGUI for a change...
[HTC One S] qazsxdcfv:
Anyone cna redirect me the tuts how to downgrade the bootloader ? Or i just flash the hboot image on the device ? Thanks :D

Sent from my hTC One S powered Maximus HD by LlabTooFeR™
[HTC One S] F-L-Y-E-R:
Yes, how many people with knowledge we have there and only one could port cm for 2.16hboot, unfortunately he's not there anymore... So should I call him master of masters or just everybody else is to lazy or not bothered at all..?
[HTC One S] el_smurfo:
It's not a port...it's just one cherry pick commit. Anyone who could build the ROM could do it, but what is the incentive? If you're going to be on CM longterm, you're going to have to use the officially supported hboot, just like we all had to upgrade to 2.15 to run the 3.4 kernel in the first place. 2.16 was never even officially released, so you can't expect CM to support it.
[HTC One S] asdfasdfvful:
Does anyone have a bubba kernel for the 12/18 build? I'm s-on and I'm just wondering if it's available...I've looked at rmbq's site for making the img on PC and I'm sorry to say that I am no where near competent enough to do so myself...

---------- Post added at 04:50 PM ---------- Previous post was at 04:27 PM ----------

So from what I read, others have also gotten a "fail" when flashing with TWRP. And supposedly it is fixed if I wipe everything? Is it necessary to wipe USB-OTG? And as for sd card, is there a way for me to backup all of the app data that is left there?
[HTC One S] nicknc:
Well, this is what I did and it worked fine (backing up SD card, of course):

1) Undo SuperCID (if you did), changing it to TMOUS10

2) Lock bootloader

3) Run RUU, I used RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2

4) Verify S-Off is still there (it was for me)

5) Unlock bootloader using HTC Dev

6) Fastboot flash recovery (I used the latest TWRP)

7) Install CM11, gapps, etc. from there (note, I did get a encrypted SD-Card error prompting me for a password in TWRP-- simply wiping everything and rebooting to recovery fixed this just fine)

8) Install latest radio, 1.20

A number of threads, both here and Evita, warned against flashing a RUU on CID 11111111, which is what I had. It seems some folks change it back, some don't, but it wasn't worth the risk of a brick for me.

You'll note the RUU I used is NOT the latest available from TMobile/HTC, as I wasn't sure if it was S-Off capable, and again did not want to add extra steps or lose S-Off.

I didn't bother restoring the data partition or converting back to superCID, as I kept my S-Off, and didn't see any value to either.

A few folks seem to have lost 3G/4G after downgrading to 2.15, but who knows what process they used.

---------- Post added at 09:25 PM ---------- Previous post was at 08:43 PM ----------

I'm using bubba non-QV on 12/18 without issue.

Wiping USB-OTG will only wipe devices you currently have connected to your phone via USB-OTG.

Wiping all partitions will commonly fix the flash fail error on TWRP. Create a backup of your data partition and manually copy all the contents off of the sd-card (including the data partition backup) to a computer or other device. Outside of stuff stored in android.secure on my sdcard, restoring the two after the fact seems to restore app data just fine.

If you can't copy your sd-card contents via USB while in recovery due to 2.16 or whatever other reason, try the Airdroid app. It takes a little longer, but as long as your wifi doesn't kick off, it will allow you to transfer everything as well.
[HTC One S] machoman1337:
Tried installing TWRP 2.6.3.0 over 2.5.0.0 via Goo manager, TWICE (adb doesn't seem to see the phone on the laptop I'm using =.=)

Every time I try to reboot into recovery, it fails, and just boots back into CM10.2. I guess that's better than a bricked phone, but come on, I want TWRP to be accessible.

I'm going to try adb-ing off a different computer, but before I do that, does anyone know why Goo Manager f***ed up TWRP?
[HTC One S] Brushstroke:
Just put the phone in fastboot mode and flash the new recovery using the fastboot command?

fastboot flash recovery nameofrecovery.img

...

No need to use Goo Manager. :)
[HTC One S] machoman1337:
that's the problem, my laptop isn't recognizing the phone when I type "adb devices" so I couldn't use fastboot. I'm going to try reinstalling adb.
[HTC One S] justaway2:
Get the TWRP in the first post. The one on GooManager won't work with CM11.
[HTC One S] machoman1337:
Thanks, I'm going to reinstall adb and manually push that recovery.img
[HTC One S] gannicus84:
If you are using windows 8/8.1 and USB 3.0, you have to make this operation to use fastboot :

http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/
[HTC One S] Rapier:
I confirm it is working, but ONLY if you have an Intel USB eXtensible Host Controller. If you don't have it, will not work

Sent from nowhere over the air...
[HTC One S] bobjbain:
I'm guessing you're on websites 8.1 so reinstalling adb won't mage a hit of difference (it's a driver issue with 8.1)

When I needed to redo the whole lot I downloaded a Linux distribution and ran if from CD, installing adb and fastboot was a doddle (Google is your friend).

I would suggest this course if action. I used mint Linux BTW
[HTC One S] esbenm:
Did you install htc sync for the drivers plus enable debugging?
[HTC One S] qazsxdcfv:
wow thanks , i just tried to use my extracted 2.15 single file .. but it fails ( cant read any partition ) so i flashed back 2.16 :D thanks bro i gonna download that RUU , ( My stock ruu are gone )

On 2.16 if you want to transferring contents use Android File Transfer (mac) or native ( For windows ) and Linux user ( ADB is still Worked ) :D
[HTC One S] bobjbain:
For me (Windows 8.1) adb works. fastboot does not and (unless something changes in the foreseeable future) will not work with the HOS.

So I use Flash Image GUI (or Flashify) to flash boot and recovery images or, if I didn't have a working ROM, I would use a linux distro running off of a live CD.
[HTC One S] mineIsAlreadyTaken:
Anyone having issus with Waze? I'm running CM11 on my company Galaxy SIII Mini and that has no issues at all with Waze. See video below for the ONE S. I tried changing governors, kernel, etc. to no avail. Clean install of both ROM and Waze.

http://youtu.be/wx_8d4WPBUw
[HTC One S] wwelles:
In case it helps others:

- I was getting a fail with flashing with TWRP 2.5.0.0, updating to the one in the OP fixed the issue.

- I haven't noticed any boot loops like with CM10.2, but I haven't been using the phone much as I own a N5 now.
[HTC One S] knickerblogger:
I am going to stick with the CM11 nightly builds so far its the only ROM I can get working, my only qualm is with the epically pathetic battery life.
[HTC One S] horno46:
I'm getting epically brilliant battery life.
[HTC One S] Microphone:
Google Now issue

hi there,

is anyone else facing the problem, that Google Now only runs one time (if you use voice recognition and answering) after each reboot?

running the latest official nightly
[HTC One S] KJS021:
Can you tell us which nightly youre currently one, if you changed kernels and if you changed the governor?

I'm quite curious cause my phone lasts 15-20h which for me is quite normal with 2-3h screen on time.
[HTC One S] horno46:
I consider that to be epically brilliant for this phone on CM.

I did a night shift the other day, turned network off and just ran on WiFi, left work with 50% after 12.5hrs. About 2 hrs screen on time.
[HTC One S] nicknc:
I didn't notice the behavior you described, but I had abysmal performance on Waze navigation with a few builds back on 2.16. When I downgraded to 2.15 and did a complete reinstall from scratch, it worked of course.

It was pretty close to what you showed, though. The arrow in navigation wouldn't advance or move unless I panned the screen-- pretty frustrating. Audio worked though.

Try a complete kernel wipe script and slap bubba back on.
[HTC One S] el_smurfo:
I've been having a lot of luck revoking keep awake permissions using this app, a modified version of the old appopps

http://xdaforums.com/showthread.php?t=2573499
[HTC One S] mikronac.ns:
What Is with bug related to display backlight? Is there any movement?
[HTC One S] Rapier:
CM11 doesn't have Apps Permissions in settings?:confused: Why do you need the extra app for that?
[HTC One S] slainbybeats:
If I flash 12/18 build... Will i be able to do updates OTA again afterwards?

Gesendet von meinem One S mit Tapatalk
[HTC One S] maluus:
got another reboot today with 18/12 nightly during a phone call. proximity sensor was active even after screen blacked out for a reboot.
[HTC One S] el_smurfo:
CM privacy guard has seemed broken to me since CM11. This restores the AppOpps control that was removed in 4.4.2...its a better interface than privacy guard has as well.

---------- Post added at 12:55 PM ---------- Previous post was at 12:55 PM ----------

Yes... Assuming you mean cm ota updates...

---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------

If you mean in call proximity sensor, then no. If you mean something else, it may be a bug only you have
[HTC One S] mikronac.ns:
I tought on bug when unlocking phone And display backlight Is turned off...
[HTC One S] antaine:
Is anyone facing a bug with print settings, when I installed the HP plug in it worked right away with my Ofiicejet 8600 plus but then when I tried to print something from quick office, there was no printer detected. ... Same with the Google cloud print extracted from Nexus 5 (integrated in settings compared to the normal one from play store which is incompatible with Kitkat. I had to reinstall one (Google cloud print or HP plug in) to it to make it work.

Any idea ?

I'm using latest HBoot 2.16 build

Envoyé de mon One S en utilisant Tapatalk
[HTC One S] el_smurfo:
I don't have that...if it ever was a bug, it was so long ago, i don't remember it. Now the backlight in crappy CWR...that's a problem, but I just use the TWRP in the OP.
[HTC One S] Brushstroke:
Yeah, the cloud printing feature is really buggy. I have Google Cloud Print from the PA Gapps package installed and it works at first, printing to my HP printer attached to my Google account, but each time I try to print after that I get this message when trying to print anywhere (Chrome, Quickoffice, etc): "Unfortunately, Print Spooler has stopped."
[HTC One S] mikronac.ns:
I am sure that i am not the only one who have this issue... Display Is turned on but backlight Is turned off...
[HTC One S] Dverez:
I had that too but today I`ve installed the latest 18/12 one, so far that did not happen yet.
[HTC One S] ATSPerson:
Yes this happens to me, mostly when I'm using the phone app, but other times too, but I can't see any particular pattern to it. Definitely an issue along with the CWR backlight problem, but have tried TWRP (both the "official" and the one in the OP) repeatedly with this ROM without success. I'm currently on the latest nightly.

But really these issues are fairly trivial.

Loving this ROM.
[HTC One S] mikronac.ns:
Sometimes I trying to unlock phone/turn on backlight for 5-6 times...
[HTC One S] el_smurfo:
Do you use any special widgets or PIN/pattern unlock? I disable all lockscreen widgets, including camera and only have the AOSP clock and lock ring and can't recall this ever happening.
[HTC One S] mikronac.ns:
No, I have disabled lock screen. Display is turned ON but backlight is turned OFF. You can see this if you have phone in dark room...

And this bug is present from android 4.2.2... I asked $Droyd$ about it but he didnt know whats happaning...
[HTC One S] knickerblogger:
I have this issue as well.

---------- Post added at 12:14 AM ---------- Previous post was at 12:09 AM ----------

with data on?
[HTC One S] mikronac.ns:
OK guys, which settings you use in sensitivity? Very high, High, Medium, Low, Very Low? [MENTION=4697974]knickerblogger[/MENTION] [MENTION=2101224]el_smurfo[/MENTION] [MENTION=4850079]ATSPerson[/MENTION] [MENTION=4673703]Dverez[/MENTION]

I used Very High and often I have backlight turned off. Now I put it on low and tried to unlock phone about 50 times. Every time I have backlight turned ON. My phone was on charger when I tried this... May some one try this and report what is result?

I think that we have some race between light sensor and display so we dont have turned ON backlight every time... [MENTION=1815755]intervigil[/MENTION] [MENTION=2703964]h8rift[/MENTION]
[HTC One S] el_smurfo:
I have Very High plus adjust to sunrise/sunset and adjustment maxed out. I think nicknc or someone else was having the issue too and high sensitivity fixed it? You are probably right though...some race condition introduced when the screen off/on timing was tweaked to make it faster.
[HTC One S] mikronac.ns:
Hm, On very high I have this issue. On low i don't have it. Will report tommorow after more usage...
[HTC One S] ATSPerson:
I haven't touched any sensitivity setting so its on whatever CM presets it at. Will check out the behaviour when the phone is on charge.
[HTC One S] nicknc:
I got it too man. The backlight isn't off--- it just comes on extremely dim, rendering the phone unreadable in all but the dimmest light. Toggling the screen on and off a few times fixes it until the next screen off.

It's been brought up several times over the past few weeks for CM11, but not fixed.

Not a critical bug, but it can make hanging up after a call a frustrating experience.
[HTC One S] Rapier:
Maybe someone could do the test and confirm or not... The backlight issue is happening ONLY when phone is not charging. I've done only tests in the last hour in different light conditions and with that sensitivity on both "very low" and "very high" settings. I even did the test while in a call.

How I tested. Called the free customer relations number (from the carrier) and while in the call, I've covered repeatedly the proximity sensor with my hand. The backlight was not turning on ONLY when phone was not connected to USB. In all cases, light or dark environment, high or low sensitivity. During several calls I made mixed tests...plugged the USB, covered the sensor, then unplugged the USB and covered the sensor again. In all these tests, the backlight issue was not present even once while phone was connected to USB, but was appearing just after a couple of tries when it was not connected.

Dunno if somebody could take advantage of this to solve the issue but maybe it'll help
[HTC One S] nicknc:
I didn't fix it but [MENTION=2906247]aegentirony[/MENTION] said a few pages back that he did, citing a build.prop edit. Hopefully he'll jump back on.

Never noticed a correlation between plugged in or not, but I am set to "very high" with sunrise/sunset checked. I have all kinds of brightness issues, particularly with brightness either going to dark or max after ending a call.

Best solution in my book would be for CM to re-enable brightness adjustments via sliding on the notification bar. Faster and more responsive than auto in my experience.
[HTC One S] Rapier:
Plug in the phone, call a free toll number and test...I am almost sure your backlight will come on every time. Unplug it and the problem will occur in short time...regardless of your sensitivity settings

Also what you say about the sliding on notification has nothing to do with the issue. Practically you disable auto brightness, something you can do now as well but the problem will still occur. You'll just get another way to manual adjust the brightness but that will not solve the in-call backlight issue
[HTC One S] nicknc:
Yeah, I'll have to try that out. Will post back if it doesn't work.
[HTC One S] Brushstroke:
I've also noticed a backlight issue, but it only happens when I'm in a call. When I take the phone away from my ear, sometimes the backlight won't come on. I've noticed a pattern with it though. If I take the phone away from my ear relatively quickly, the backlight will come on, but if I move my hand very slowly away from my ear, it won't. Seems to be an issue with the proximity sensor.
[HTC One S] aegentirony:
I had a build prop edit that seems to help but did not fix it ...

ro.lcd_min_brightness=40

Again maybe placebo but i think it helps slow them down a bit. Line goes under LCD density

Edit had to make some calls and it seems it does relate almost to how fast or slow u pull the phone away..seems like the proximity sensor isn't told to come back on or gets stuck
[HTC One S] nicknc:
Just picked up my phone and noticed that exchange issues appear to have returned. My outlook.com email (which connects via exchange) mysteriously disappeared and the email app is prompting for setup. Also, my exchange contacts and calendar from the same account are suddenly not syncing. This is with 12/18. Account is still showing as setup under settings with a sync date of today.

FYI
[HTC One S] esbenm:
Just installed cm11 coming from cm 10.2 with its maybe GPS problems.

First time I ran maps with navigation I had a reboot.

Not looking good so far :(
[HTC One S] mikronac.ns:
It would be nice if Ethan know something about this problem and tell us if he can do anything about this... [MENTION=1815755]intervigil[/MENTION]
[HTC One S] aegentirony:
I posted logs with attention to intervigil don't blow the man up lol he will take a look at it I'm sure when he can
[HTC One S] Aussi:
Hi all

got a question. Do more ppl have the problem that the sound sometimes just dissapeares?

quite annoying cause than my alarm wont go off in the morning haha :D

or am I the only one ?
[HTC One S] guythnick:
I have experienced this... It has happened on the past several releases. Will remember to logcat next time it happens

I did notice that the alarm vibrated my watch via bluetooth, but didn't sound on phone. May be related to plugging/unplugging the headset but have to test.
[HTC One S] Aussi:
Aah Oke so I am not the only one. I thought maybe my hardware of the phone is getting faulty.....

hopefully in the future it will be fixed :D
[HTC One S] Phantom Pt. II:
That happens for me when I'm listening to music in my headphones and plug out the headphones while it's playing.

Sent from my One S