yashsingh1/xdaforums huggingface dataset:
[HTC One S] el_smurfo:
You probably need to remove the google dialer and reflash. Delete the backup script from /system/addon.d
[HTC One S] Yellowpor:
OK, i will try it :)

---------- Post added 12th March 2014 at 12:25 AM ---------- Previous post was 11th March 2014 at 11:29 PM ----------

I fixed my problem by

1. reinstall the original Stock

2. updated the Recovery to 6.19

3. complete flash

Thanks for your help
[HTC One S] hrkh83:
guys!

Which build is less buggy?! I want to install it for a friend and he does not live near me! So it really need to be robust!
[HTC One S] nicknc:
I back up and restore the data partition. It works well the majority of the time. The Google Play autoreinstall has never worked for me, not sure why, but I gave up on it months ago.

---------- Post added at 09:27 AM ---------- Previous post was at 09:13 AM ----------

This is something that was mentioned in the two kernel threads. Undervolting *should* work on "nominal" Kraits, but does not appear to always be the case.

I undervolt and do get occasional reboots, but these area almost always when running GPS, charging with usb fast charge on, screen on full-bright, 4G connection and streaming via bluetooth. When that scenario is in place and I enable/disable either GPS or bluetooth, it will infrequently cause a reboot.

My krait is "fast", so I should be able to undervolt reliably, however it appears heavy power use toggling will cause reboots for me.
[HTC One S] The Setlaz:
Thanks for the clarification. :good:

Do we know if CM kernel does undervolting or not ?

By the way, even at 594MHz min frequency, I had feeze... See my previous post with the logcat. :crying:
[HTC One S] el_smurfo:
CM kernel should not over clock or under volt...stability is the goal

BTW, wiped data and restored with Helium and I think I'm back. I can't imagine doing that every flash, and I agree Google backup doesn't work very well at all.
[HTC One S] bobjbain:
I bit the bullet and paid for Titanium Backup, it was cheap then but it's made flashing ROMs easy.
[HTC One S] m1schi:
So what ROM version and kernel is everybody on? I'm still on 20140214 and the newest Bubba kernel, but can't say I'm happy with the stability right now.
[HTC One S] bobjbain:
I'm on the latest nightly, previously was on the 5th nightly. For what I use the phone for I have had no stability issues.

Saying that when I have flashed Bubba or IceCode kernels I have had problems, SOD and reboots, so I tend to stick with the stock kernel.
[HTC One S] el_smurfo:
Voice+

FYI, since I didn't really get any responses to my previous post, I'll note that even on a totally clean CM11 flash of the latest nightly, Voice+ is still broken and I don't see anything pending that might fix it...

If anyone cares, I flashed it all with the latest official TWRP2.7. Works great and no longer has a length restriction on Nandroid filenames.
[HTC One S] nicknc:
Might just be you and I and the guy in fayettenam that use V+ here.
[HTC One S] el_smurfo:
Yeah...I resisted for a long time as Koush stuff is always very fragile, but once Hangouts got SMS integration, it was too useful. I should know better...BTW, Helium worked, but was a bug laden crash-a-thon to get things restored, so the streak continues.
[HTC One S] nicknc:
Just do the data backup and advanced restore in TWRP. Much easier and works almost every time.
[HTC One S] el_smurfo:
I'll try it next time...but the only reason I was wiping was that mysterious "system data" section of 1.2GB...if TWRP restored the whole data partition, then I might have been back to square one.
[HTC One S] bobjbain:
Have you tried Folder Size Chart, lets you drill into the directories to see what's in there.

Although it might not be the best as it's currently showing my /data as 0 bytes :confused:
[HTC One S] nicknc:
Sounds like root is not enabled, maybe.
[HTC One S] bobjbain:
Yeah ignore me, it doesn't ask for root permissions so I guess it's half lame then.

If you can adb (or use a terminal emulator on your device) then you can go to /data and issue 'du -s * | sort -n' and that'll give you the size of each folder with the largest one last, cd into system and 'du -s * | sort -n' again, cd into the biggest folder etc. etc. Bit manual but then at least you get a good idea of what is taking up all the space.
[HTC One S] nicknc:
It's a good suggestion though.
[HTC One S] el_smurfo:
Yeah, but "system data" did not seem to be a visible folder. Disk Usage app has root permissions and couldn't resolve what was on that space. I am slightly suspicious that a backup I made while running CW recovery was taking up the space, as this is a similar symptom for backups on the SD card, but it was probably time after all these months to start fresh. Got rid of some of my other funny problems with Device Administers and Lockscreen widgets, so it was worth the hour or so.
[HTC One S] nicknc:
...and did you go ahead and s-off while you were at it and join the big boys and girls? ;)
[HTC One S] el_smurfo:
Tried before and failed. See nothing that trying again would bring to my life other than the freedom to choose one of many different kernels I wouldn't use in the first place.
[HTC One S] Brushstroke:
I'm on the latest nightly with IceCode kernel. I know someone else said they have problems with IceCode and Bubba, but they've both been quite stable for me. I prefer IceCode though.

Never bothered to use Voice+. Is it worth it? :p

Sent from my HTC One S
[HTC One S] el_smurfo:
It's nice to have your hangouts and GV SMS in the name app (I don't have an SMS plan), but it's not worth it if it's going to randomly die with no fix in sight...I know, I know...nightlies...no expectation of functionality, but it seems they are leaving valuable information on the table by not having a bug report system...even just a star ranking of problems. On G+, Koush said he was running a few week old nightly build, so he didn't even know it was broken.
[HTC One S] intervigil:
We broke Voice+ during the qcril merge. It will be fixed, Arcee or Cyanogen will typically get it.
[HTC One S] nicknc:
Thanks for the info.
[HTC One S] 808phone:
I am having major problems with network data at least since M4. Also appears in the nightlies after M4 (of course).

Network data alternates continuously between 3g, 4g, H and H+ and none. Cannot do any network data operations because of this. Google play says RETRY and Chrome says offline most of the time. Every now and then it connects but only for a little while.

Nightly march 4th, 2014 did not have this problem. So the problem occurred after that.
[HTC One S] epsiblivion:
I'm currently running M3 snapshot. is M4 stable to use? do I need to wipe or flash over is ok?
[HTC One S] maluus:
Since last few nightlies (Not sure since when exactly) I've lost wifi auto connection. Wifi works, finds the network but it doesn't automatically connects as it was before. I have to manually connect and enter the pass everytime. I have a tasker profile to enable and connect to the home wifi whenever I arrive home but I've lost this ability.
[HTC One S] nicknc:
Could be Hawaii suffers from the same fast dormancy issues experienced in other select markets. Search this thread for the build.prop edits that resolve the issue you are mentioning.

Add them, then reboot and you problem should be fixed.

---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------

Do a clean install- best place to start for that issue.
[HTC One S] mikronac.ns:
20140313 bootloops for me, you shouldn't flash it...
[HTC One S] 808phone:
Thank you. Will try it.
[HTC One S] maluus:
For me it stuck at cm logo instead off looping. Back to 12/03.

Enviado desde mi One S mediante Tapatalk
[HTC One S] Brushstroke:
Same here, with both stock kernel and IceCode.

Sent from my Nexus 7
[HTC One S] Dverez:
Same here...
[HTC One S] teamet:
And here. Min also says relocked in fastboot.

12/3 instead..
[HTC One S] el_smurfo:
WTF? Relocked?
[HTC One S] Brushstroke:
That can't be related to this ROM. You must have done something else to get it like that.
[HTC One S] teamet:
Ok, well.. I relocked when downgrading my hboot but i definitly unlocked it again. I have been upgrading using OTA since mid-february so I haven't been using fastboot at all so it could have happened at any other time.. There have been several kernel upgrades since february and they are working fine, so something must have triggered the relock after my last kernel upgrade!
[HTC One S] maddehaan:
20140313 bootflop

Same here. I installed it this morning.

Situation:

Came from 2040312

tried a dalvik wipe

tried a cache wipe.

Now back to 20140312
[HTC One S] nespresso33:
14/3 boot fine
[HTC One S] Brushstroke:
Same here. I did notice that it automatically disabled ART and switched back to Dalvik. No big deal, just switched back.
[HTC One S] intervigil:
Voice+ was fixed last night.
[HTC One S] zodac01:
Hi, I'm having trouble connecting to my phone using Eclipse (for Android debugging). I've moved from CM 10.2 to the latest nightly, and all of a sudden Eclipse just doesn't recognise my phone. I can mount the sd card just fine, but that's it.

Is this a common issue (and is there a fix), or is this just something I may have messed up on my end?
[HTC One S] el_smurfo:
Are you running the latest sdk and drivers? Try putting phone in mtp mode...that worked for me.
[HTC One S] zodac01:
That did the trick. Thanks. :)
[HTC One S] syrelyre:
Latest nightlies (14 and 15) the process: com.Android.phone stops working, anyone know what could be wrong?
[HTC One S] noomarsil:
Did you flash Google Dialer from Nexus 5? They changed something in one of March Nightlies and now this Dialer doesn't work at all. Actually Im on older Nightly and everything works fine.
[HTC One S] syrelyre:
I tried clean-flashing 14 and 15 with GApps, both Stock and Full Modular from http://xdaforums.com/showthread.php?t=2397942

EDIT: and i did not flash the nexus dialer, i simply flashed the new rom and the new GApps, really annoying bug. I also tried formatting the /system partition, but unfortunately to no effect
[HTC One S] slainbybeats:
Running 14/03 together with icecode kernel. Working very well!

Gesendet von meinem One S mit Tapatalk
[HTC One S] Brushstroke:
03/16 is working very well. A big changelog with some under the hood stuff, and there looks to be a change to the GPS/location tile in the notification menu and a new icon for CM File Manager.
[HTC One S] The Setlaz:
The lockscreen rotation is not really working properly:

1. when wake-up in portrait and rotate to landscape display, the lockscreen gets messed with the cLock applet. The lock-screen ends up plain in the middle instead of having the cLock on the left hand side and the screen-lock function (slide, pattern, pin...) on the right hand side

2. when wake-up in landscape and rotate to portrait, the lockscreen is off-centered on the right side
[HTC One S] Brushstroke:
Lockscreen rotation? Wtf you talking about? I've never been able to rotate the lockscreen in CM11.

Sent from my HTC One S
[HTC One S] The Setlaz:
:eek: do you have "Auto-rotate screen" enabled in Accessibility ?

CM11 lockscreen does rotate... and it's been 2 months I'm complaining about some random freeze-on-rotate and posted several logcat about it.

Don't tell me I'm the only one who has a lockscreen that rotate ?!? (and crash...)
[HTC One S] el_smurfo:
I think I'm not the first to tell you you're the only one. Even if the option was available, I can't imagine why you'd want a rotating lockscreen. Maybe some app did it to you, like one messed with my widget capability requiring a clean flash to fix.

Btw, 3/16 has WiFi up/down arrows...more than reason enough to flash for me
[HTC One S] The Setlaz:
I've been told I was the only one to have freeze-on-rotate on the lockscreen, I can't remember anyone telling me the lockscreen is just not supposed to rotate :eek: :eek:

Could you confirm that ?

By the way, in CM10.1.3 that I was using previously, the lockscreen did rotate as well as the homescreen, so for me it was completely normal.

I can do another clean-install... and maybe format the sdcard just to be sure... (I already performed a few clean-install on CM11 and I always end-up with a lockscreen that rotates)
[HTC One S] Brushstroke:
Yeah, I have it enabled in Accessibility. My lockscreen doesn't rotate. I don't think it's supposed to and the homescreen doesn't rotate either. It only rotates in apps for me.
[HTC One S] The Setlaz:
Well homescreen does not rotate with Google Launcher or Trebuchet. But even when I select one of these launcher, my lockscreen still rotates. (my 3rd launcher which is the one I use is Apex Launcher)
[HTC One S] Brushstroke:
Yeah bro, I don't think it's supposed to do that...
[HTC One S] el_smurfo:
I just checked. I have rotation enabled in accessibility and no lockscreen rotation. I once use a lockscreen modifier app while running g CM10 and the setting carried clear into CM11, greying out my lockscreen widget setting. Only backing up apps/data, formatting system and data and clean flashing got this cleared. Just out of curiosity, do you have any weird files in /system/addon.d that might be saving this weird state?
[HTC One S] The Setlaz:
Mhm no. I can't remember installing apps to mess with lockscreen, and I was happily using Trebuchet on CM10.1.3 with home-screen rotation.

I just checked the /system/addon.d directory as you mentioned, everything seems normal.

EDIT: clean install after Wipe Data / Factory reset with 16/03 nightly: lockscreen still rotates...

EDIT2: new clean install after Wipe Data / Factory reset and NEW Google and CM credentials (created new accounts): lockscreen does not rotate anymore !!

PS: maybe that will also allow me to install Bubba Kernel now ?! I never managed to get it working, it always bootlooped on splash screen with a strange kernel-panic...
[HTC One S] bobjbain:
There was lockscreen rotation in CM10.2 but it has never been in CM11.

Do you restore apps from your Google account, maybe it's bringing something down when you signed in after a clean install??
[HTC One S] The Setlaz:
Well I do remember having this up/down arrows a few months back, didn't really noticed they disappeared but good to have them back !

Same here ! Camera produces f/c

Yes I was always restoring apps from my Google account, so that must be something like this...

2 other questions (seems I'm not entirely done with rotation issue :crying: ):

1. ON 16/03 ONLY: when going into sleep from an app' in landscape mode, at wake-up still, holding the phone in landscape mode, the lockscreen is messed up. (exactly as I described previously except now lockscreen does not rotate anymore ! but on 11/03 for example, I have no problem)

2. when using Apex Launcher and homescreen rotation, the freeze occurs at the lockscreen to homescreen transition (after unlocking) while when I had the lockscreen that rotated, it occured right at wake-up. Anyone using Apex Launcher (or any homescreen-rotation capable launcher) and experiencing this problem ? (on any nightly)
[HTC One S] bobjbain:
I have pin protection on my lockscreen and the 16/03 nightly does make my screen a bit funny at times. If I switch off and then back on again the lock screen is generally OK.

See attachment for scrambled lock screen.

I run Nova launcher and just tried unlocking when in landscape mode and NOVA rotated fine.
[HTC One S] The Setlaz:
Because when holding the phone in landscape mode, it just makes sense to me to have the lockscreen rotated. (for PIN / pattern unlock or even to read your notification without unlocking the phone). That's the last big thing I miss from 4.2.2 / 4.3: basic lockscreen + homescreen (bugfree :laugh: ) rotation by default. Let's hope CM is working on that :good:

Yep ! That's exactly it for the lockscreen! And indeed, a sleep and wake-up fixes it. So for PIN / Pattern unlock, that makes things a bit funky !

Well the thing about the freeze is that it can be pretty random. :crying: I disabled Apex auto-rotate and went back on 11/03 nightly, so no problem anymore, but still I'd like my homescreen to rotate.
[HTC One S] mineIsAlreadyTaken:
anyone else having issues with CyanDelta? For quite some time now the recovery script isn't processed (it just boots into TWRP) and I have to flash manually from there ..
[HTC One S] Brushstroke:
Yeah, it was doing that to me for awhile, then I switched to the new TWRP 2.7. It works flawlessly.
[HTC One S] mineIsAlreadyTaken:
I asked after I installed TWRP 2.7 and it didn't help (: anyway, the cause was "flash additional zip after ROM" .. I had three of these, all were valid files inside the Cyandelta directory. After clearing and re-adding them in the settings it works again (I didn't touch the actual files) ..

=sent from my OneS=
[HTC One S] provaleriy:
I'm on 16 Mar build. I have an lockscreen rotating issue.

How to reproduce the issue:

1. Start any app supporting landscape orientation.

2. Rotate phone to landscape.

3. Turn off screen.

4. Turn on.
[HTC One S] Albino_Mexican:
Screen of my lock screen issue when unlocking after locking in landscape.
[HTC One S] The Setlaz:
Yup, you're not alone ! Let's wait for a fix.
[HTC One S] cyxareg:
Will it be ok if i update my 03/01 nightly to 03/17?i stopped update it from 03/03 with android.phone issue, is it fixed or some ways to solve it? Thanks :o
[HTC One S] syrelyre:
Still present in 14 and 15, haven't tried 17
[HTC One S] Brushstroke:
For all you photographers out there, there's a camera FC bug on the latest nightly 03/18. Otherwise seems fine.
[HTC One S] el_smurfo:
I'd urge you all to consider Snap Camera. It's only $2, is based on the AOSP camera but has far more features, is faster and the developer is quite responsive on xda. He actually is the one who originally got the camera working on the HOS way back in CM9 or 10. You can use the trial version which is 100% functional when you put your phone in airplane mode...the hold for burst was the thing I missed most about the Sense camera and Snap has it.
[HTC One S] Brushstroke:
You are awesome. This is a great app.
[HTC One S] el_smurfo:
Not me...lots of folks bought it to "donate" to [MENTION=917443]dzo[/MENTION] when he got our camera running.

On another note...has anyone found and tested a compiled version of the CM dialer with google places API? It's been sitting in review for months, but I know others have compiled it, possibly into other ROMs and it's working well.
[HTC One S] Rapier:
I think Beanstalk, Slim and Twisted have it. Carbon should have it also. And you might want to check Thyrus's KK dialer (search for it on XDA), I am using it but it has several variants, see which works best for you

Sent from nowhere over the air...
[HTC One S] dhigby:
Hey, I have been running the M4 snapshot with no problems until I noticed today the camera crashes any time I try to record video.

Ditto for my wife who is running the same release.

Any fix for this?
[HTC One S] Brushstroke:
There have been a lot of camera problems with CM11. Seems like every other nightly, it breaks entirely or some feature of it does. Like el_smurfo mentioned earlier, you should look into Snap Camera HDR from the Play Store. It's a great replacement for the stock camera app.
[HTC One S] nicknc:
Sweet. Still going good here with no reboots or bootloops on 2.16.

Thanks for pushing forward.

---------- Post added at 11:36 PM ---------- Previous post was at 11:33 PM ----------

Strange, it's quoting the wrong post. Sorry elsmurfo. This XDA app has been acting goofy, meant to reply to op.
[HTC One S] el_smurfo:
This crap app has been doing that to me for weeks. Have to click 5 times to get the right post.
[HTC One S] nicknc:
I blame CM Inc. :p
[HTC One S] el_smurfo:
I guess both had their last stable release about the same time, so maybe. :what:
[HTC One S] RockR172:
[MENTION=4157305]Darknites[/MENTION] [MENTION=3921603]phoenixita[/MENTION] and anyone else building 4.4..

if you want to make your ROM flashable with TWRP, use THIS commit.

And add this line

SKIP_SET_METADATA := true

in device/htc/s4-common/BoardConfigCommon.mk
[HTC One S] :
Jeez :-| op is my friend :P he told me himself -.-' I think that's not stalking
[HTC One S] horno46:
I'm having trouble adding extra home screens. Can only get the swipe left for Google Now. I saw a YouTube vid that said to drag and drop icons/widgets of the edge of the screen to add home screens but it doesn't work.
[HTC One S] Rapier:
You should drag the icon over the right screen edge till it'll switch to all screen view, then drop it onto a new screen. Alternatively, you can long press on any empty space on screen, select widgets and do the same

Sent from nowhere over the air...
[HTC One S] _kevn_:
You have to make sure there is at least one thing (icon, widget) on the first home screen. When a home screen has nothing on it, it disappears.

I am using invisiwidget, https://play.google.com/store/apps/details?id=com.LOGMD.blankwidget , to have empty home screens

I hope that helps!
[HTC One S] horno46:
Yep tried that, doesn't switch to all screen view and icon rebounds on to home screen.

I notice gesture typing is borked as well.
[HTC One S] RockR172:
Added new build for 2.15 in first post..

As usual, 2.16 will come soon.. :)
[HTC One S] Michael1101:
Wiped again my gapps, but no problem. Finally we got our quick toggles back :) Thank you!!

in my opinion nightlys could start.

One more thing, maybe somebody can help. In cm10.2 times I installed manually the n5 clock. Now after every update my clock fc and I have to manually push the clock in app folder and restart again. I also tried to delete before installing update, but clock don't come with rom. Any chance this won't happen anymore?
[HTC One S] usaff22:
Any changelogs?

I'm a real stock-Google-Edition sort of person, so unless some things have been fixed, I probably won't upgrade lol

Too many features just alters the UX :p

Thanks for your work though :)
[HTC One S] RockR172:
Me too lol.. i prefer stock..

But there have been some changes to the device and kernel tree..

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

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

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

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

There might be more, but you get an idea.. ;)

Oh, and its synced to the new AOSP branch 4.4_r1.2, i.e, KRT16S over the previous KRT16M..

EDIT: Added 2.16 build in 2nd post.. :)
[HTC One S] Rapier:
Network event notification works? I mean if someone tested it... In Beanstalk it doesnt, and I find it very useful

Sent from nowhere over the air...
[HTC One S] usaff22:
Then I guess I'll have to back up SystemUI and Settings apps...

When a new version is released only then is CM as close to AOSP as possible lol
[HTC One S] Phantom Pt. II:
Silliest thing. It's not camera but the XDA app that randomly disappears sometimes after dalvik/cache wipe and reboot.

Thanks for the update. Good to have the swipe to quick settings back.
[HTC One S] RockR172:
Wouldn't recommend that..

Changes are not just in SystemUI or Settings app.. They go deep in the framework..
[HTC One S] Michael1101:
Haha, I thought it's just me. The xda app disappearing thing really puzzles me... :silly: (as a side note: I always wonder why the community with the best android developers of the world got such a bad gingerbread or froyo style app....)
[HTC One S] melo563:
That's why I use tapatalk it is free now and way better and is up to date with less issues.
[HTC One S] el_smurfo:
I think stock is fixed as of today's nightly according to other phone users.

---------- Post added at 09:24 AM ---------- Previous post was at 09:23 AM ----------

Thanks...I use Thyrus KK UI only theme already, so I'll try the dialer (though it's probably themed black which I don't like).

EDIT, here's the link

http://xdaforums.com/showthread.php?t=2526844

Looks like he's just theming the google dialer which crashed a lot for me when used with CM a while ago. I'll hold out for the CM dialer...looks like it's close to being approved.
[HTC One S] Rapier:
No, no, check last pages...he just post there a link with a dialer made specifically for CM11 latest builds (from 17th of March if I recall correctly). Check that one

Edit: Here's the link to that post

http://xdaforums.com/showthread.php?p=51151045

Sent from nowhere over the air...