yashsingh1/xdaforums huggingface dataset:
[HTC One S] Brushstroke:
Hah, "dipping into the 60s." Try dipping into the single digits with more snow to come. It's 8 here in Arkansas and only going to get colder as the night goes on. :p
[HTC One S] blinksilver:
Gyro stuff got merged as well as a couple ville specific RIL updates, the next nightly should be one to watch out for!
[HTC One S] |RaVeR|:
Quick question: couple of nightlies ago, Launcher3 got swapped for Trebuchet.

I had set my screen to contain 6 rows and 4 columns of icons in Launcher3.

When Trebuchet returned to cm, I had 4-5 rows on my desktop again (the default), leaving a lot of whitespace.

I can't seem to find where to change this. Has anyone else changed the icon density?
[HTC One S] mikronac.ns:
So, Gyro caused reboots while Ingressing or what?

---------- Post added at 12:20 PM ---------- Previous post was at 12:17 PM ----------

It iis under 0.5 sec as on stock rom...
[HTC One S] kavafree:
The RIL update is the fix for the "error while searching for networks" bug.
[HTC One S] eabinsan:
Yes. In general it was causing reboots when using it while multitasking. First we thought it was GPS, because most GPS apps use the gyro as well.
[HTC One S] mikronac.ns:
I love you, oh yes :D
[HTC One S] el_smurfo:
Trebuchet has very few customizations. I would highly recommend Apex or Nova launchers, or even the GEL which gets you Now integration. Trebuchet couldn't get added to my delete script fast enough.
[HTC One S] antaine:
I flashed the 31/01 nightly onto one my friend's One S but I seams that the front camera doesn't work, any idea ?

Envoyé de mon One S en utilisant Tapatalk
[HTC One S] el_smurfo:
BTW, if you're still looking at the "signal bouncing" bug, I grabbed a log just now walking from my car to work. I only captured the errors, because you can't post huge logs here, but there is definitely something weird about the RILJ exceptions.

There are groups of these:

02-06 08:01:20.207 E/PHONE (1465): [ServiceState] setState deprecated use setVoiceRegState()

02-06 08:02:09.580 E/RILJ (1465): Exception processing unsol response: 5757Exception:java.lang.RuntimeException: Unrecognized unsol response: 5757

02-06 08:02:09.580 E/RILJ (1465): Exception processing unsol response: 5757Exception:java.lang.RuntimeException: Unrecognized unsol response: 5757

Often followed by large sections of these:

02-06 08:02:09.600 E/Dcc (1465): onDataStateChanged: no associated DC yet, ignore

02-06 08:02:09.600 E/Dcc (1465): onDataStateChanged: no associated DC yet, ignore

02-06 08:02:09.600 E/Dcc (1465): onDataStateChanged: no associated DC yet, ignore

02-06 08:02:09.600 E/Dcc (1465): onDataStateChanged: no associated DC yet, ignore

02-06 08:02:09.600 E/Dcc (1465): onDataStateChanged: no associated DC yet, ignore

02-06 08:02:09.600 E/Dcc (1465): onDataStateChanged: no associated DC yet, ignore

And at least one of these:

02-06 08:06:25.352 E/DCT (1465): CMD_SET_ENABLE_FAIL_FAST_MOBILE_DATA: sEnableFailFastRefCounter:-1 < 0
[HTC One S] Brushstroke:
You might try upgrading to the 02/05 nightly. It looks like the camera problems were fixed.
[HTC One S] nicknc:
I get 10 mbps - 17mbps. Without the build.prop values of hsdpa/hsupa set at 28/7, I will get 3-4 mbps.

On wifi, I get the same speeds my other wifi devices get.

---------- Post added at 01:07 PM ---------- Previous post was at 12:49 PM ----------

Might shed some light:

Droid DNA, CM11-- http://xdaforums.com/showthread.php?t=2558758&page=46

They claim the signal hopping is actually fast dormancy working
[HTC One S] el_smurfo:
2/6 nightly

Spontaneous reboot just sitting on home screen.

---------- Post added at 10:23 AM ---------- Previous post was at 10:17 AM ----------

Read a few pages and didn't get that. One guy was trying to tweak with some IPv6 settings, and strangely, my APN was the IPv6 one, though switching it didn't stop the "RILJ" errors...I'll see how well the network works at noon.
[HTC One S] eabinsan:
So the device is not crashing anymore in the car dock, but there is no sound either. Not a big problem for me, because it connects to the bluetooth audio after that anyway. Do you have a suggestion for other settings I could test? Or can I change the setting in android somewhere?
[HTC One S] nicknc:
It was one of the posts on the first page that comes up that made that claim.

I didn't read past the first page, though, so didn't see it went in a different direction.

---------- Post added at 02:18 PM ---------- Previous post was at 02:17 PM ----------

Your tether working now?
[HTC One S] Brushstroke:
Yup! :)
[HTC One S] intervigil:
May still be missing a use case. Got a logcat again?
[HTC One S] antaine:
He did upgraded to the 05/02 and then 06/02 but no luck, still doesn't work ...

Envoyé de mon One S en utilisant Tapatalk
[HTC One S] eabinsan:
Hm, I think it tries to route sound to a non-existent usb audio device

D/alsa_ucm( 255): snd_use_case_set(): uc_mgr 0xb89ab810 identifier _disdev value Speaker
D/alsa_ucm( 255): disdev: device Speaker not enabled, no need to disable
D/alsa_ucm( 255): snd_use_case_set(): uc_mgr 0xb89ab810 identifier _enadev value USB PROXY Rx
D/ALSADevice( 255): switchDevice: mCurTxUCMDevivce None mCurRxDevDevice USB PROXY Rx
D/ALSADevice( 255): route: devices 0x800 in mode 0
D/ALSADevice( 255): No valid input device: 0
D/alsa_ucm( 255): snd_use_case_set(): uc_mgr 0xb89ab810 identifier _enadev value USB PROXY Rx
D/ALSADevice( 255): switchDevice: mCurTxUCMDevivce None mCurRxDevDevice USB PROXY Rx
D/alsa_ucm( 255): snd_use_case_set(): uc_mgr 0xb89ab810 identifier _verb value HiFi
D/alsa_ucm( 255): Set mixer controls for USB PROXY Rx enable 1
D/alsa_ucm( 255): acdb_id 45 cap 1 enable 1
D/alsa_ucm( 255): Set mixer controls for HiFiUSB PROXY Rx enable 1
D/alsa_ucm( 255): Setting mixer control: AFE_PCM_RX Audio Mixer MultiMedia1, value: 1
D/ALSADevice( 255): close: handle 0xb89cf918 h 0x0
D/ALSADevice( 255): open: handle 0xb89cf918, format 0x2
D/ALSADevice( 255): Device value returned is hw:0,0
D/ALSADevice( 255): handle->format: 0x2
D/ALSADevice( 255): setHardwareParams: reqBuffSize 2048 channels 2 sampleRate 48000
D/ALSADevice( 255): setHardwareParams: buffer_size 16384, period_size 2048, period_cnt 8
D/AudioUsbALSA( 255): Creating USB Playback Thread
D/AudioUsbALSA( 255): PlaybackThreadEntry
D/AudioUsbALSA( 255): getCap for Playback:
E/AudioUsbALSA( 255): ERROR: failed to open config file /proc/asound/card1/stream0 error: 2
E/AudioUsbALSA( 255): ERROR: Could not get playback capabilities from usb device
E/AudioStreamOutALSA( 255): pcm_write returned error -5, trying to recover
D/ALSADevice( 255): close: handle 0xb89cf918 h 0x0
D/ALSADevice( 255): open: handle 0xb89cf918, format 0x2
D/ALSADevice( 255): Device value returned is hw:0,0
D/ALSADevice( 255): handle->format: 0x2
D/ALSADevice( 255): setHardwareParams: reqBuffSize 2048 channels 2 sampleRate 48000
D/ALSADevice( 255): setHardwareParams: buffer_size 16384, period_size 2048, period_cnt 8
[HTC One S] Aeonxul:
Well for me i think it is near 1 sec! Also in comparison to my previous nightly 02/02 if i m not mistaken, the delay is more definitely.

PS> still suffering from pm latency in viber when my device screen is off.
[HTC One S] mikronac.ns:
I will try to find out what increased delay and why we have music stuggling when unlocking Phone...
[HTC One S] el_smurfo:
I think the answer was posted a page or so back. Kondik broke something (that bootloop build from last week), patched it, but the patch added 350ms delay. Promised to fix soon in the commit notes. I think the music glitch crept in with the last performance governor changes.
[HTC One S] mikronac.ns:
Ok, I know for that. But we have music stuggling when unlocking phone or when it rings while it Is in sleep mode. I think that I know what causing that, i "just" need to figure out how to fix it. Just to get back my fujitsu from service, i have burned motherboard and HDD... :'(
[HTC One S] blinksilver:
Would you be willing to explain what the issue really is? Like why does it take so long to wake up, kondik's recent change aside, the wake time before then were bearable, but far from ideal. I'm not asking anyone to work on it further, or anything of the sorta, I'm just wondering what the deal is.
[HTC One S] AKToronto:
Hard to see that being an issue. I thought the recent kernel commits were to ondemand gov and the cm kernel defaults to interactive anyway doesn't it? I may be wrong
[HTC One S] intervigil:
There may be something else missing for USB audio in the kernel.
[HTC One S] mikronac.ns:
https://github.com/CyanogenMod/andr...h/arm/mach-msm/htc/ville/display/mipi_ville.c

I think If I remove lines 330 and 331, sound problem will dissapear but we will get backlight problem again... I will see what I can do...
[HTC One S] eabinsan:
Maybe. But the dock is connected to the cigarette plug, so there is no usb audio device connected :)
[HTC One S] mikronac.ns:
Started compiling kernel to see if I fixed music stuggling when unlocking phone... Compiling on Intel(R) Celeron(R) CPU G1610 @ 2.60GHz... :crying:

I found what caused problem... I will upload Bubba kernel tommorow to test it... :)

I dont have PC at home for few days more, just on work... And I am going home now :P
[HTC One S] darius359:
I'm unable to send MMS. I tried changing my APN but it seems to be stuck on the MetroPCS LTE settings. Is there a way to set it to the T-Mobile option?

11-20140202 Nightly
[HTC One S] sirio87s:
how i can 'activate' the photosphere mode on cyano 11??
[HTC One S] el_smurfo:
By installing a google camera that supports it. You can find them on xda by googling photosphere camera.
[HTC One S] nicknc:
First, update your nightly.

Second, what do you mean it's "stuck"? The little radio button to switch between APNs must be precisely touched or it opens the APN settings. Is that the issue you are encountering?
[HTC One S] sirio87s:
i've found an apk that work on sense roms, but not on cyano11! :eek:
[HTC One S] Brushstroke:
What APK is this?
[HTC One S] nicknc:
What in the world...
[HTC One S] el_smurfo:
ugh...you probably found one of those sense camera enhancements. probably should take your talk of non-cm apps elsewhere.
[HTC One S] djsubtronic:
I'm getting sick of how CM keeps closing services, even those with forced notification icons to keep them in memory, even when there's over 250 MB of free RAM. Why in Gods name does it keeping doing this?

I never thought this day would come but I'm actually considering going back to Sense because coupled with signal hopping issues, screen lag getting worse instead of better, this is getting ridiculous.

Sorry for the rant and no disrespect to devs.. :(
[HTC One S] el_smurfo:
Huh...I almost always have 350MB or more free RAM. I wonder if your problem isn't with CM, but with KitKat itself and the fact that you are running a lot of large memory resident apps.

Have you messed with the background process limit or Done Keep Activities in Dev Settings? Have you carried over some MinFree Manager settings that are too low? Are you using Greenify, because it was doing exactly what you are complaining about to me...even on stuff I didn't Greenify?
[HTC One S] djsubtronic:
Literally did a clean install 2 days ago. Got rid of every unnecessary app I could think of. It starts off with around 350 MB free upon boot, but browse a few web pages and listen to some music, send some messages on Whatsapp, you're down to 250 MB.

The point remains though, why kill a 10 MB background service when there's still 250 MB left?
[HTC One S] nicknc:
Whatsapp can be a memory hog. Have had a lot of issues with it
[HTC One S] el_smurfo:
I almost mentioned that. Seems like anytime someone is having performance or memory issues, WhatsApp is installed. Was one of the last apps to work with ART too. Those crazy kids and their newfangled messaging apps...
[HTC One S] mikronac.ns:
Newest official bubba doesnt have sound stuggling when unlocking phone :D
[HTC One S] nicknc:
Don't tell [MENTION=2101224]el_smurfo[/MENTION].
[HTC One S] el_smurfo:
Another black screen. Gmail led still blinking, so assume just backlight off. Started happening right around when in call backlight bug was patched too.
[HTC One S] nicknc:
Hmm. I haven't had any black screens in awhile. Running the "IceCold" kernel for awhile to test it out, so that could be contributing to the stability.
[HTC One S] justaway2:
When did you first start noticing it? I've had it happen once on the Feb 2 build.
[HTC One S] Rapier:
I tried to search for those settings and I found that they not even fit for our device.

Based on the hardware, our device is capable of 42.2 Mbps download speed and 5.76 Mbps upload. That means hsupa category should be 6 and hsdpa category should be 20

I really don't see any point in setting them to higher values since they won't do anything

Sent from nowhere over the air...
[HTC One S] mikronac.ns:
I anyone want to compile kernel to see will this solve music glitches, because I dont have PC to do this...

In function

void mipi_dsi_clk_enable(void)

{

u32 pll_ctrl = MIPI_INP(MIPI_DSI_BASE + 0x0200);

if (mipi_dsi_clk_on) {

pr_info("%s: mipi_dsi_clks already ON\n", __func__);

return;

}

MIPI_OUTP(MIPI_DSI_BASE + 0x0200, pll_ctrl | 0x01);

mb();

hr_msleep(100); /*ADD DELAY BETWEEN 100 AND 125ms*/

if (clk_set_rate(dsi_byte_div_clk, 1) < 0)/* divided by 1 */

pr_err("%s: clk_set_rate failed\n",__func__);

mipi_dsi_pclk_ctrl(&dsi_pclk, 1);

mipi_dsi_clk_ctrl(&dsicore_clk, 1);

clk_enable(dsi_byte_div_clk);

clk_enable(dsi_esc_clk);

mipi_dsi_clk_on = 1;

}

Sould be added delay to wait for mipi bus because it is A little bit lazzy so we must wait for it to avoid glitches... Delay must be below calling mb(); function...

path of file is:

drivers/video/msm/msm_dss_io_89x0.c

Also you sould try adding delay into same function but In another file on same path but file is msm_dss_io_8960.

Or, look into code somewhere else if you think that is 100-150ms big delay....

Please, someone try this, it is saturday morning, i Will have access to pc In monday morning....

Maybe [MENTION=1815755]intervigil[/MENTION] can take a look on this...
[HTC One S] blinksilver:
Finally, someone making sense again.
[HTC One S] horno46:
My backups keep failing with the TWRP in the OP, at the split tarring stage. I can't get the official CM recovery to work either. :(
[HTC One S] Microphone:
Use the TWRP app to do backups

Gesendet von meinem HTC One S mit Tapatalk
[HTC One S] djsubtronic:
Regardless, it's an app used by millions, none of whom seem to have an issue. So why does it have to be us? You can't blame a single app for services being killed when there's so much free RAM available. It just doesn't make sense. The memory handling needs to be looked at and tweaked IMHO. I'd do it myself if I knew the first thing about how.
[HTC One S] mikronac.ns:
Selecting power button for shutter button will crash camera app...
[HTC One S] Michael1101:
Had the same problem. Only thing helped was full wipe of system and SD card. I did a recovery in cwm (from op) and restored it after wipe. Then I installed twrp again and it worked... No idea what went wrong with my filesystem
[HTC One S] nicknc:
They've been making sense for awhile.

This is the cm thread though. ;)

28/7 doesn't hurt either way.
[HTC One S] el_smurfo:
Does anyone have a stock backup. I always used 24 and 6 because I thought it was stock
[HTC One S] darius359:
You're completely correct about precisely touching the APN options. I thought that was the reason I was having issues sending MMS messages. Perhaps I should have elaborated. Messaging crashed whenever I try to send an MMS. Updated the APN and the ROM to the most recent nightly. MMS works.

Is there a way to take screenshots on CM11?
[HTC One S] Albino_Mexican:
24 & 6 is stock for my carrier.
[HTC One S] Rapier:
HSDPA category 20 and 24 both indicate 42.2 Mbps speed. Don't know the difference between them tho
[HTC One S] Albino_Mexican:
20 is MIMO 2x2 while 24 is Dual Cell...whatever that means. :confused:

---------- Post added at 01:12 PM ---------- Previous post was at 12:52 PM ----------

I know this is OT but fast dormancy settings have been discussed here before. I know that ro.ril.fast.dormancy.rule=1 means enable and 0 is disable. What does setting it to 2 mean?

I have disabled fast dormancy and my battery life is much improved strictly from a user experience perspective. Reason I did so is because my carrier's (Fido) network does not support fast dormancy. Strange that they have it enabled in the stock ROM but I suspect it may be because it's a technology they might implement in the future so it makes sense to enable it from factory so they don't have to update everyone's phone at a later date. That being said, HTC must implement some code that masks the 3g/H+ switching and makes the phone consistently display 4g. Having disabled fast dormancy, my phone doesn't switch nearly as often and I suspect the switching with fast dormancy enabled or disabled is normal depending on the volume of data being transmitted/received. The only question is if your carrier's network has implemented fast dormancy on their network. My point is, I don't think the frequent switching on CM is a bug but merely the radio behaving as it should; it's just visible to us. Also, just because the stock ROM from your carrier has fast dormancy enabled, doesn't mean their network actually supports it.

Anyway, thanks for listening to my rambling.
[HTC One S] Rapier:
Take a look here and here
[HTC One S] el_smurfo:
What do you guys think of this post?

https://plus.google.com/106417415856537095600/posts/LrmL5mtzTeN
[HTC One S] blinksilver:
I'll give anything posted on the internet a try, especially if its from a stranger I don't know! ...i'll report, tell you guys if my phone exploded or not
[HTC One S] nicknc:
Thanks for the insight, it really helps.

What I wonder at this point is why having FD set to 1 or 2 causes the perpetual data drops for some TMOUS users on this phone, but not others. 2 is the stock setting for CM on pyramid and glacier, and they don't have issues.
[HTC One S] Rapier:
For me it doesn't work at all. Replacing the file switches automatically on Dalvik. Set it back to ART, rebooted and it's back on Dalvik...something is wrong at least for me. It was working for you and have you checked in Dev Options that the runtime is set to ART with this version?
[HTC One S] Albino_Mexican:
Has TMOUS implemented FD on their network? Do the data drops cease with FD set to 0?

Perhaps we should carry on here: http://xdaforums.com/showthread.php?t=1710275
[HTC One S] blinksilver:
nah, it won't take for me either. I wonder if its because he didn't include a libart-compiler.so
[HTC One S] nicknc:
1. They report partial implementation in some markets

2. Yes
[HTC One S] mdanish4:
Hi

Hi all, I am totally new here i need some help. I am on hboot 2.15 and every time i try to install the latest cwm or twrp recoveries it wont boot in the recovery. and every time i am trying to install cm11 it gives me error. i tried everything that i could. Can anyone here tell me what do i need to do?
[HTC One S] ATSPerson:
Use one of the recoveries linked to in the OP
[HTC One S] elias.acab:
Anyone have the solution to the snapchat front camera issue? its bugging me a little bit...

Thanks
[HTC One S] Brushstroke:
Pretty quiet in here. How is 02/08 running for everyone? Seems fine here.
[HTC One S] The Setlaz:
Today has been terrible with the black-screen on wake-up bug for me... (I'm on 05/02 nightly)

As sais el_smurfo, the notification LED keeps blinking, but it's not a simple backlight issue. The screen is completely irresponsive.

Phone being on-charge or not doesn't matter. It just occurs randomly.

Will test today's nightly, but I think I'll fallback on January nightly soon and wait until the bug gets fixed.
[HTC One S] darius359:
On 2/07 and it's running pretty great. It fixed a previous issue with mms crashing the messaging app. Apollo had crashed a few times until I cleared all data and restarted. Everything else is running smoothly.

The only way I can take screenshots is via the apm. Is there a way to remap one of the nav buttons to do this?
[HTC One S] horno46:
I'm stuck on 29/01, with no working recovery and reluctant to wipe SD card etc to get it working again.
[HTC One S] mdanish4:
??

Ok so i installed the recovery and then i installed the cm nightly for hboot 2.15. but after the htv logo my system reboots.. why is that?
[HTC One S] deniz2694:
are you S-Off or S-On ?
[HTC One S] adamfirari:
do you know which is the latest nightly without this bug?
[HTC One S] mdanish4:
i dont know that. like i said on my previous post i m new with htc's.. well i tried to do "fastboot flash boot boot.img" but still nothing.

Edit: Ohh yeah i am s-on
[HTC One S] The Setlaz:
Well, it seems my "Golden" nightly is 19/01 (sitll have it on my SD card 'just in case').

After that, there was some backlight fix and wake-up delay, screen-rotate freeze, and now black-screen on wake-up.
[HTC One S] nicknc:
1. Stop sexting

2. Problem solved.

You're welcome. :)

---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------

No blank screens for days and days here on latest nightly with IceCode kernel. No issues really at all.
[HTC One S] Brushstroke:
How's the battery life on IceCold?
[HTC One S] el_smurfo:
Hold down vol and power. Just verified it works
[HTC One S] nicknc:
Very weird and variable. Evens out to a little better than stock.

Lose about 1-2% per hour in sleep, and 3-5% each time the screen is on about five minutes or more.
[HTC One S] blinksilver:
Bunch of ril related cleanup came down the pipe for 2/11. Nothing specific to the vile, but you who knows it might help those having connection problems. Just a heads up...

Edit: this was my 300th post, only took 6-7 years... took me almost as long go open an account!
[HTC One S] The Setlaz:
10/02 running, still the same bugs for me: black screen on wake-up and Pattern unlock weird black-screen sliding... (but the latter seems only to affect me...)

About the black-screen on wake-up bug, I just noticed if you press the power button multiple times to wake-up/sleep, my screen eventually got back alive !
[HTC One S] nicknc:
Still have FD data drops here, but signal toggling is very reduced.

No other problems noticed, still running IceCode without issue
[HTC One S] djsubtronic:
I take it the screen lag and music hitch still exists on wake on the latest nightly?
[HTC One S] darius359:
Are you on T-Mobile? Check this out:

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

I was also having FD drops on ALL ROMs until I added a line to my build prop.
[HTC One S] nicknc:
Thanks for the link. I do apply that FD edit along with a few others between flashes.

Simply changing fd to 0 wasn't enough for my area, unfortunately. I also have to change another ril parameter. If you're curious, both I and [MENTION=2101224]el_smurfo[/MENTION] have posted several lines that appear to resolve FD drops, boost speeds for a select few markets, and help with battery drain, in this thread a couple of times.

I haven't seen that power drop parameter though-- I'll have to look at that a little.

Either way, I was merely reporting that the ril changes in the latest nightly don't appear to fix the native FD issues (for those that experience them), but do appear to clean up some of the residual 3g/h/h+ indication toggling. Doesn't eliminate it completely, but it no longer does it when I am stationary.

Thanks again!
[HTC One S] epsiblivion:
so there is a new snapshot up. how far back is it in terms of nightlies? should I try that instead of 2/10? I'm on 2/3 build
[HTC One S] el_smurfo:
Looks like it was built latest, so it should be the very latest. You should be able to click on the 2/10 and the M3 in cmupdater and see the changelogs...
[HTC One S] deniz2694:
I have a huge bug,

I flashed the nighly from 07/02 and it was all fine for 2 days but today my phone won't connect to network and won't detect sim card (no asking for pin at boot) . I reflashed rom,kernel, radio 10 times but it still doesn't come back, what should i do because now i can't receive or make calls or send SMS ...
[HTC One S] el_smurfo:
Perhaps try calling your provider? You could try a full wipe and install, but if it was running fine for 2 days, it seems unlikely to be the phone?