yashsingh1/xdaforums huggingface dataset:
[HTC One S] Michael1101:
Hm... No. Why not download 29/3 mount internal storage in recovery, copy from computer, flash rom, boot, switch to dalvik then flash newest nightly?
[HTC One S] el_smurfo:
I'm with the CM guys...ART is definitely not ready for primetime and is mostly a placebo. Switched back after the last problems and really don't notice any difference.
[HTC One S] Rapier:
You shouldn't even report an issue if you're on ART. It is not officially supported, you have even a warning from CM team when switching to it. It's experimental. And I used it for more than two months without noticing any difference

Sent from nowhere over the air..
[HTC One S] melo563:
I disagree with you on this also the only reason that I am on cm is actually for kit Kat I have always been a fan of sense and the apps can't wait to get the apps working. On a related note has anyone else noticed some stutter and lag on 3/30 update have had it here and there since I updated to it today.
[HTC One S] Brushstroke:
Well yeah I know, and I know the warning is there...I just wasn't sure why it was happening until I ruled out everything else it could be. I'm pretty convinced now that ART's benefits at this point are placebo anyway.
[HTC One S] el_smurfo:
Fyi, rumor says skip 4/1 nightly unless you want all your ringtones to be sheep noises.
[HTC One S] Brushstroke:
Wut. O.o

Hah, oh...April fools... :p
[HTC One S] el_smurfo:
Trying to play April Fools with the big boys, I guess. I don't know anyone that uses CM sounds anyways, so I probably wouldn't notice.
[HTC One S] melo563:
So does anyone else have a problem work camera not working still just photos video works but taking pictures is not possible
[HTC One S] 808phone:
Do you mean from the locked screen? Otherwise I believe it's working. I've been using camera+ since camera problems were mentioned.
[HTC One S] tjamzt:
I am currently running the February 12th nightly and it has been pretty stable for me with good battery life. Is there a newer, stable nightly that you guys would recommend updating to?
[HTC One S] Brushstroke:
Yeah, go to 04/01. It's very stable and you can enjoy having all your ringtones and notifications play sheep noises. Well, for today anyway... :p
[HTC One S] maluus:
is there a change lately? 01/04 and 02/04 both cause the phone and incallui fc's upon boot.
[HTC One S] Brushstroke:
Do you have ART enabled? If so, that's the reason for the phone and incallui FC's on boot. It happened to me too. I switched to Dalvik and it's very stable now on 04/02, same with 04/01.
[HTC One S] el_smurfo:
If there is a poll, I vote for restoring the old backlight power sequence. The screen on lag now is worse than it has ever been for this phone.
[HTC One S] maluus:
yes I have art enabled. I think I ll wait for them to be fixed somehow. Instead of switching to Dalvik. I m now used to it.

Same here. It is getting worse lately.

Enviado desde mi One S mediante Tapatalk
[HTC One S] mikronac.ns:
Not for me, it is very quick...
[HTC One S] Dverez:
Same here...the screen on lag is worse.
[HTC One S] paranoidpenguin:
Am I really the only one how has this mic problems with google?

Tried the fixes Darknites posted but didn't worked but as I said it must have something to do with cm, cause everything works fine on Viper.

I also compared the snd_soc_msm files of cm and viper, second has a lot more files than cm, also has some htc "specials" in it.

Tried to run it with the Viper snd_soc_msm but ended up with a bootloop.

Why am I the only one?
[HTC One S] maltumbo:
0403 doesnt boot for me

reflashed 0402 which booted fine yesterday. now unable to boot too.
[HTC One S] el_smurfo:
Google Now has always seemed to hear me too softly. Someone suggested it was actually using the top speaker as a mic, but talking into that didn't seem to help. I just yell and look like a moron when it still mis hears me, then I deactivate it again.

---------- Post added at 01:31 PM ---------- Previous post was at 01:30 PM ----------

If you use ART runtime, you may have a bad time on the last few nightlies. I use Dalvik and 4/3 is running fine for me.
[HTC One S] Sinistah_:
Coming from 4.2.2 how do I update to this? Thanks :)
[HTC One S] ectobk:
How i can switched to Dalvik and disabl ART because i have incallui FC's on boot
[HTC One S] Rapier:
You flashed without making a backup first? Bad choice. Now you'll remember for the future...

Flash an older nightly that has ART working over it, start ROM and switch to Dalvik. Then flash latest nightly again

Sent from nowhere over the air..
[HTC One S] ectobk:
thankx but how i can switch to Dalvik ? how i can found this
[HTC One S] Rapier:
OH. I thought you remember since ART is not default runtime. You have previously switch to it.

Go to Settings - Developer Settings and you have there an option called "runtime". Press on it and select Dalvik instead of ART. Phone wil ask for a confirmation then reboot itself.

NOTE: If Developer Settings are not displayed in Settings, you should go to About Phone and tap several times on the BUILD VERSION to have it shown up. A message saying "Now you're a developer" (even if you're not) will be shown briefly
[HTC One S] ectobk:
ah i tap several times on the BUILD VERSION big tanks :laugh:
[HTC One S] epsiblivion:
is the new logo in the nightly?
[HTC One S] el_smurfo:
I don't think so, and I'm worried it's only for Inc phones..."Cid is for the community" I use the N5 animation...
[HTC One S] epsiblivion:
push bootanimation.zip to /data/local/ right? I wonder if anyone has the boot.zip yet
[HTC One S] Navid-CR7:
guys please tell me which nightly is more stable and good for daily use?
[HTC One S] Dverez:
The latest.
[HTC One S] Navid-CR7:
no reboots? no lag?

can i use it for daily?
[HTC One S] Dverez:
No reboots, can use it daily, leave Dalvik default don`t use ART otherwise you`d get force close on apps.
[HTC One S] Navid-CR7:
buddy can you explain for me (( leave Dalvik default don`t use ART otherwise you`d get force close on apps ))?
[HTC One S] Dverez:
Dalvik and ART a bit technical if you don`t know that part just install the ROM and use it, you cannot get it wrong at all.

Dalvik and ART are uses different ways of executing apps (ART is still an ongoing project on Google`s side).

If you want to know more just Google it...
[HTC One S] Navid-CR7:
aha thanks. and i have to first install twrp 2.7.0.0 then install latest nightly and gapps i will have a stable rom without any bug and force close
[HTC One S] Dverez:
Yes, correct but use gapps from the first post of this topic. (I`m using twrp 2.7.0.0 too)
[HTC One S] b_ignatov:
What about the battery life on the latest nighly?Is it better than stock sense rom?And finally....can we hope that soon we'll have a stable release.I feel little stupid to change roms every day.I would like to get stuck with a stable one.....and no more changes at all.
[HTC One S] Rapier:
No one force you to flash every nightly. Flash one that you find stable for you, then wait till the stable release is out

Sent from nowhere over the air..
[HTC One S] b_ignatov:
I already stopped to do that.Now I'm waiting for really stable one , without major bugs and many complains from users.
[HTC One S] paranoidpenguin:
Glad to hear I am actually not the only one with this problem...

In my understanding there is a kind of miscommunication between the audio server and the google apps, am I right? Is there maybe a way to trigger the inquiry from google now to find out which mic it want to use?
[HTC One S] 1aladdin1:
ART causes force-close loops on 20140404-nightly

till today I used 20140303-nightly with ART runtime without problems.

Today I updated to 20140404-nightly and my device was stuck in a force-close-loop after boot :(

Had to go back to dalvik-runtime to overcome this situation.

Any similar experiences out there???

how to resolve force-close-loops after switching to ART: use adb shell and issue "setprop persist.sys.dalvik.vm.lib libdvm.so" and then adb reboot
[HTC One S] Brushstroke:
Yeah, this has already been discussed at length a couple pages back. CyanogenMod doesn't officially support ART and they give you a warning before enabling it...
[HTC One S] 1aladdin1:
I know that ART is experimental. But - as already stated - 20140303 was fine with art and now it crashes. So we have development in a wrong direction
[HTC One S] epsiblivion:
M5 snapshots rolling out! can't wait
[HTC One S] el_smurfo:
Pretty sure M builds are a step back from nightlies? Last one was certainly less stable IMO.
[HTC One S] nicknc:
Ask for a refund then.
[HTC One S] teamet:
We? :)

I was an ART'er back when it was possible .. now I do dalvik with an overclock to 1.7 ghz - pretty much same same. My biggest problem is not speed or stability (it is/was awesome on either runtime!), but the proximity sensor when making calls. The screen does not turn off or lock and I often press stuff accidently while performing calls. Quite annoying when flight mode gets activated during a call :)

Is it a general problem or is it just me who have missed a setting somewhere?
[HTC One S] nicknc:
Custom kernel?
[HTC One S] paranoidpenguin:
I checked the logcat using the mic in Google Now:

D/alsa_ucm( 260): snd_use_case_set(): uc_mgr 0xb7b91818 identifier _enamod value Capture Music
D/alsa_ucm( 260): Set mixer controls for Voice Recognition enable 1
D/alsa_ucm( 260): acdb_id 11 cap 2 enable 1
D/ACDB-LOADER( 260): ACDB -> send_audio_cal, acdb_id = 11, path = 1
D/ACDB-LOADER( 260): ACDB -> send_adm_topology
D/ACDB-LOADER( 260): ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TOPOLOGY_ID
D/ACDB-LOADER( 260): ACDB -> send_audtable
D/ACDB-LOADER( 260): ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE
D/ACDB-LOADER( 260): ACDB -> AUDIO_SET_AUDPROC_CAL
D/ACDB-LOADER( 260): ACDB -> send_audvoltable
D/ACDB-LOADER( 260): ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_VOLTBL_STEP_COPP
D/ACDB-LOADER( 260): ACDB -> AUDIO_SET_AUDPROC_VOL_CAL
D/ACDB-LOADER( 260): ACDB -> AUDIO_SET_AFE_CAL
D/alsa_ucm( 260): Setting mixer control: SLIM_0_TX Channels, value: One
D/alsa_ucm( 260): Setting mixer control: SLIM TX7 MUX, value: DEC4
D/alsa_ucm( 260): Setting mixer control: DEC4 MUX, value: ADC3
D/alsa_ucm( 260): Setting mixer control: DEC4 Volume, value: 70
D/alsa_ucm( 260): Setting mixer control: ADC3 Volume, value: 100
D/alsa_ucm( 260): Setting mixer control: MICBIAS3 CAPLESS Switch, value: 1
D/alsa_ucm( 260): Set mixer controls for Capture Music enable 1
D/alsa_ucm( 260): Setting mixer control: MultiMedia1 Mixer SLIM_0_TX, value: 1

And Shazam:

D/alsa_ucm( 260): snd_use_case_set(): uc_mgr 0xb7b91818 identifier _verb value HiFi Rec
D/alsa_ucm( 260): Set mixer controls for Line enable 1
D/alsa_ucm( 260): acdb_id 501 cap 2 enable 1
D/ACDB-LOADER( 260): ACDB -> send_audio_cal, acdb_id = 501, path = 1
D/ACDB-LOADER( 260): ACDB -> send_adm_topology
D/ACDB-LOADER( 260): ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TOPOLOGY_ID
D/ACDB-LOADER( 260): ACDB -> send_audtable
D/ACDB-LOADER( 260): ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE
D/ACDB-LOADER( 260): ACDB -> AUDIO_SET_AUDPROC_CAL
D/ACDB-LOADER( 260): ACDB -> send_audvoltable
D/ACDB-LOADER( 260): ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_VOLTBL_STEP_COPP
D/ACDB-LOADER( 260): ACDB -> AUDIO_SET_AUDPROC_VOL_CAL
D/ACDB-LOADER( 260): ACDB -> AUDIO_SET_AFE_CAL
D/alsa_ucm( 260): Setting mixer control: SLIM_0_TX Channels, value: One
D/alsa_ucm( 260): Setting mixer control: SLIM TX7 MUX, value: DEC6
D/alsa_ucm( 260): Setting mixer control: DEC6 MUX, value: ADC1
D/alsa_ucm( 260): Setting mixer control: DEC6 Volume, value: 76
D/alsa_ucm( 260): Setting mixer control: ADC1 Volume, value: 100
D/alsa_ucm( 260): Setting mixer control: MICBIAS1 CAPLESS Switch, value: 0
D/alsa_ucm( 260): Set mixer controls for HiFi Rec enable 1
D/alsa_ucm( 260): Setting mixer control: MultiMedia1 Mixer SLIM_0_TX, value: 1

Hopefully this are the relevant lines ...

As supposed they are using different mic settings, so can I just change the acdb_id and route Google Now to the right mic?
[HTC One S] teamet:
The problem is present both on stock cyaogen kernel and on custom. I use Icecode as of this week for OC.
[HTC One S] nicknc:
OK. I'd suggest a clean install at this point. No proximity sensor issues here, and I'm also using Icecode, but without oc
[HTC One S] maluus:
Same here. But I noticed that it doesn't happen everytime. I had to change the flight mode button location on quicksettings pane. But even then sometimes even opens the app drawer and apps run. As a summary the problem is present. It happens sometimes. Used stock, bubbas and icecode. Probably not kernel related.
[HTC One S] Darknites:
Flash this and try Google Now again.
[HTC One S] paranoidpenguin:
Didn't work. What did you changed?
[HTC One S] Darknites:
I tried to boosting DEC4 Volume that was set to 70 to 76.
[HTC One S] paranoidpenguin:
This I already tried few days ago, Even set it to 100, didn't change a thing.

Tried to copy paste the config for the line mic to voice recognition and push it with adb, but somehow after reboot the settings changed itself back to normal.

Could I not just use the DEC6 instead of the DEC4?
[HTC One S] loki6666:
Cm11 Mobile Network Dropped Multiple Times Per Day , Requires Pin

hello all,

I hope there is someone who can help me finding out what's going on with my phone. I did already a wipe on cache/dalvik and later on also a full wipe.

HBOOT 2.15

S-OFF

Radio 1.20...

LATEST ICECODE KERNEL

Nightly Builds

I cannot remember exactly, but since january updates, my mobile network is dropped every once in a while, several times during the day. I mean the network totally and requiring to enter the PIN code again. I first thought that it is my sim card, what is just thrown out. then, some days later I saw by accident, that my phone was silently rebooting - there was no "HTC" boot screen shown, but only the cyanogenmod boot screen (blue with moving circle). I am wondering and cannot exactly tell if it is always rebooting (silent) or dropping my network (sim).

I already saw similar problem of one user in cyanogenmod forum, but did not get any answer.

Does anybody think there is a solution for this, or is there maybe a hardware failure?

I attached a logcat file for better analysis. I was recorded while network was dropped.

View attachment logcat.zip

regards

nandor
[HTC One S] Darknites:
Got no idea how to do that.
[HTC One S] DoogleDood:
I'm getting some TERRIBLE battery life over here from the latest snapshot. I'm talking less than 8 hours from full charge, normal use...

Anyone having batter issues? The last couple versions have been like this.
[HTC One S] nicknc:
What does betterbatterystats say? Sounds like your phone isn't going to sleep.
[HTC One S] DoogleDood:
I don't have that app. It's 3 bucks? Is it really necessary?

What can I do to fix battery life?
[HTC One S] JgCurry:
That's my! Not good

Gesendet von meinem One S mit Tapatalk
[HTC One S] DoogleDood:
I'm getting even worse than that...
[HTC One S] JgCurry:
Oh man that's bad

Gesendet von meinem One S mit Tapatalk
[HTC One S] nicknc:
Well, you could try another app that let's you see your CPU states.

Can't do much to help you without more info other than recommending a clean install.

I get terrific battery life.
[HTC One S] el_smurfo:
There's a free xda version
[HTC One S] Aduck79:
Look here for the XDA-edition: http://xdaforums.com/showthread.php?t=1179809
[HTC One S] Brushstroke:
It's just terrible battery life on the latest snapshot, right? Because my battery life on the latest nightly is actually pretty good.
[HTC One S] ThomasHunter:
Well, my battery life is actually chronically terrible on every build.

When I have mobile data enabled, it uses 5-10% per hour without having the screen on, which I think is ridiculous because it causes me to almost never use data. On wifi, it's around 4-5% at the end of the day with about 1 hour of screen-on time, which I'm content with.

BBS indicates that Awake is around 40-50%, sometimes with RILJ and sometimes NlpCollector as the bad guys. I know what these are, but I figure that it should be possible to have Google Location enabled and have the battery last about 16-20 hours with just one hour of battery time.

Do you guys have any recommendations? Anything to have better battery life. If I'd get 150% on a Sense-based ROM, I'd do that, but I'm really specifically confused by how much my data drains because I've heard that almost anyone isn't affected by this.

As you can see in the screenshot above, this is what happens when the phone is idle and connected to 3G/H+ networks. :(
[HTC One S] Aduck79:
Have you tried Greenify (https://play.google.com/store/apps/details?id=com.oasisfeng.greenify)?
[HTC One S] ThomasHunter:
Yes, I have, and greenifying things like Facebook helps a bit, but I see data connectivity as a/the culprit here and I don't think I can greenify that, right?

And I've also tried JuiceDefender in the past, but I think only having 1 in 5/10 minutes of data is a big compromise, especially when having Hangouts conversation and the like.
[HTC One S] speedfreak007:
I have 3G/wifi always on and manage to get anywhere between 2 to 3 hours of screen on (2040 mah battery, icecode kernel). I still think this is way too low (compared to iphone users for example) as I can't manage to get through the day without constantly thinking about my battery. so anything to improve this is welcome.
[HTC One S] 808phone:
I have to use greenify along with task killers to get decent battery life. On a few tests I got 5 1/2 hours of screen time. I also set my auto brightness levels lower.

On my iPhone the main culprit is Facebook - kill that app and have reasonable brightness and the battery lasts a long time with location services, wifi etc... all on.

I have a larger battery in my One S so that helps a bit too.
[HTC One S] hillbicks:
Does anyone still experience random reboots? The phone is actually used by my girlfriend, which makes it really hard to get logfiles and she wasn't able to see a pattern that causes the reboots. Stock kernel, HBOOT 2.15 and S-OFF, not sure about the radio (btw. how the hell do I upgrade the radio, I couldn't find anything that seemed still relevant)

I wiped everything when I upgraded the phone from CM10 when it started to act up and only restored user apps via Titatnium, so I hope it's not one the apps that it's causing the problem here. Any suggestions are welcome.
[HTC One S] el_smurfo:
I have maybe one reboot every couple weeks. Are you using an M build or nightly, because M build quality seems spotty.
[HTC One S] hillbicks:
Nightly from a couple of days ago since I already read that the M builds were really not that reliable.
[HTC One S] el_smurfo:
lockscreen wallpaper

cool...though never seen such a long list of comments on a commit

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

but mostly I can't wait for this...sounds like it fixes a laundry list of every bug reported here

http://trickonlyz.blogspot.de/2014/04/android-443-kitkat-os-update-rolls-out.html
[HTC One S] ThomasHunter:
Wow, if it really fixes the wifi *and* the data dropping, that update would indeed be our saviour. Less wakes by power manager also sounds good.
[HTC One S] cyxareg:
sorry for silly questions,havn't been here for long time. is there still exist dialer problem for people who update from early march nightlies?tried 2 dialers from here 10-15 pages ago with no effect,back on 03\01 backup
[HTC One S] el_smurfo:
Not sure what your question is...dialer works fine for me in all builds. If you mean the Google dialer, it's never worked right and is no longer even offered in the PA gapps because of all the complaints. If you're trying to put a current CM dialer in an older nightly, that's also probably going be a bad time due to all the caller ID changes recently.

PSA, if you flash 4/10, don't use the custom lockscreen wallpaper. Took me 4 reboots to fight through the systemui FC and get it turned off...almost had to restore backup.
[HTC One S] cyxareg:
yeah, i meant google dialer with android.phone FC. so..what i should do to flash last nightly from 01\03 nightly with no android.phone fc?
[HTC One S] nespresso33:
Wait this commit http://review.cyanogenmod.org/#/c/62377/
[HTC One S] el_smurfo:
Don't bother with google dialer. CM dialer now supports reverse caller id using the same data sources which works close enough for me.

---------- Post added at 08:52 AM ---------- Previous post was at 08:51 AM ----------

Yeah...except it isn't "initial selection"...it happens constantly...I guess hold off until tomorrow's nightly if you're interested in this feature. Otherwise 4/10 seems fine.

Hopefully this will get you ARTers back up and running?

http://review.cyanogenmod.org/#/c/62128/
[HTC One S] nicknc:
Thanks for the BBS info.

Are you on a lower-HSDPA area? My phone will kick into E when I put it in my pocket or a drawer in a few places where the 4G signal isn't terribly strong. As you likely already know, toggling between E and H will drain the battery quickly.

Also, if you haven't done build.prop edit to disable fast dormancy, I'd recommend that as well. Otherwise, it's highly likely that you data connection is dropping constantly and cycling through E/3G/H over and over.

Lastly, it would be worth making a nandroid, do a complete wipe and run just a basic vanilla install with minimal configuration. Let it run a few hours and see if the battery drain continues. If it doesn't, then you're looking at an app or rogue setting problem. Make sure you're running a recent gapps version-- they don't always update through google play (GNow in particular)

I get random battery drains from time to time when dirty flashing, and doing a complete wipe seems to be the only fix. Also, consider switching to IceCode or Bubba if all else fails. I get fantastic standby battery life (2+ days) with the undervolt both provide.
[HTC One S] ThomasHunter:
That's a good idea, I'll try that when I have time. :) I've done a few clean flashes in my time on CM11, but I always let Titanium restore everything first thing, so it could indeed be some app.

It could be the fast switching between speeds, although I haven't noticed that on my display really. I'm also sometimes just on 2G/E because data drains that bad, and I believe that's better but still meh.

I'll definitely do the build.prop change, and switching kernels is indeed a last resort because I'm still S-ON (I know, I know ^^).
[HTC One S] tim_h:
Hi everybody,

yesterday I did a fresh install of the 0409 nightly. Everything works great, including WiFi - except for mobile data, which does not work at all. The APN settings are correct as far as I can see, but mobile data does not connect (no H/E/...) in status bar.

I am on stock CM Kernel. Baseband version is 1.15.50.05.29_10.30.50.08L.

Any advice? A smartphone without mobile data is not really so useful. ;)

EDIT: Ok, a reboot did not help, but completely shutting off the phone and restarting it did the trick. I will have to see how often this problem appears. If anybody has further advice, I would still very much appreciate it.

Cheers,

Tim
[HTC One S] epsiblivion:
it was a good 2 years, everyone. I am getting an HTC One m8 today on T-Mobile :D
[HTC One S] el_smurfo:
What plan are you on, how much is the plan and how much are you paying for the phone? I'm wobbling between the M8 and the Nexus5...HTC bugs me so much, but that phone is just so pretty.
[HTC One S] teamet:
looks a little like your APN isn't setup correctly.. could you perhaps confirm the settings?
[HTC One S] bilal_liberty:
good decision

happy flashing ur new toy :D
[HTC One S] epsiblivion:
I am on the simple family plan. 4 lines for $100 with unlimited voice, text, and 1gb 4g data (throttled after the cap). I am guessing it's gonna be full price $636 though my friend told me when he bought a Galaxy S4 last year and paid the full amount instead of monthly payments, they gave a $30 discount.
[HTC One S] tim_h:
I agree it looks like it, but I double-checked the settings. They are ok, and also they have been working just fine for hours before stopping to work without me having made any changes.
[HTC One S] el_smurfo:
Have you tried "reset to defaults" in the APN settings?
[HTC One S] anant210:
FYI, the latest nightly (11th) seems to work with ART... I was getting boot loops for almost all nightlies in the last two weeks