yashsingh1/xdaforums huggingface dataset:
[HTC One S] qazsxdcfv:
Wow , so im not alone :D

Yeah i get that problem too (1-5) post before me ..

And also i've checked that Google Now and Playstore has the best Wakelocker , i mean this 2 apps seems "wakes" my device a lot :confused:

And sometimes my phone goes insane ,

It gonna be very hot / hot if goes to standby mode or idle :eek:
[HTC One S] The Setlaz:
Hi,

I'm facing an issue with the 2 latest nightly (20130124 and 20130125) that I didn't have on 20130119 : I use the "3x3 schema" lockscreen and on these 2 latest nightly builds, rotating the screen on lock-screen would cause a freeze. (and requires holding power-button for 10s in order to reboot ... that's the only escape)

Also, there is still something that seems to go wrong at unlock phase with schema: sometimes (randomly), it takes about 1-2s to exit something (black screen sliding) after unlocking.

Am I the only one facing these 2 issues with 'schema' screenlock ??

I reverted to 20130119 because of the rotate-freeze.

By the way, I noticed cLock had been updated now the lock-screen wirdget takes into account user's preferences. :)

According to cmxlog, stuff from Trebuchet was pushed in to the git rep', but haven't seen it in the Settings yet.
[HTC One S] Dragn4rce:
I added the tweak into the build.prop and no change. In fact now I can't connect to T-Mobile's internet at all now.

Is there any other AOSP ROM you guys suggest? :/

I'm S-Off and everything.

Sent from my Ñ£×Ú$ 5
[HTC One S] Brushstroke:
Are you using the correct APN? I'm on T-Mobile US and my mobile data connection is fine.
[HTC One S] Dragn4rce:
I switched it to Pv3 last night I believe.

Sent from my Ñ£×Ú$ 5
[HTC One S] Brushstroke:
Pv3...? What?
[HTC One S] el_smurfo:
Should be one of the bottom 3.
[HTC One S] nicknc:
Mine likes to default to metropcs between occasional flashes.

Fast.T-Mobile has been very problematic for me. Ironically, epc is now a lot faster.

---------- Post added at 08:42 PM ---------- Previous post was at 08:40 PM ----------

Dude, something else is going on then. Post the settings you added to build.prop if you could.

You saw that fast dormancy was already in there, right? Just had to change that one to 0.
[HTC One S] el_smurfo:
I try each, but seem to end up on epc. The network must be deciding for us
[HTC One S] nicknc:
Or ipv6 which wastes thirty minutes of my time when I try to tether before i realize it, lol.
[HTC One S] Dragn4rce:
This is what I did.

EDIT: Have internet connection now. still has issues tho. It's still everywhere and disconnect when switching between H+ and H.

Sent from my Ñ£×Ú$ 5
[HTC One S] nicknc:
Try setting fast dormancy to 2 and ro.ril.radio.svn to 5. For some folks, that's the preferred settings for TMOUS. For me, it still causes occasional data drops,but nowhere near what I get with fast dormancy set to 1.

Also, delete the "skipradiooff" parameter altogether.

You rebooted after the edit, right?

Also, what radio are you on?
[HTC One S] Dragn4rce:
Did it. And yes I did reboot.

Radio 0.16.3.0.45.0815

Sent from my Ñ£×Ú$ 5
[HTC One S] nicknc:
Settings-->about phone-->baseband version

Just provide the first three digits, ie 1.13, 1.20, etc.
[HTC One S] Dragn4rce:
0.16.315.etc

Sent from my Ñ£×Ú$ 5
[HTC One S] nicknc:
Can you post a screenshot of that? Never heard of that radio. You are talking about a one s, right? I see your signature says nexus 5...
[HTC One S] Dragn4rce:
I'm using both phones lol.

Sent from my Ñ£×Ú$ 5
[HTC One S] Brushstroke:
You're on T-Mobile US (I think you mentioned T-Mobile earlier), right? Because if I'm correct, the radio you currently have on your One S is an EU radio rather than a US radio. That might explain the weak signal given your location.
[HTC One S] Dragn4rce:
Yup T-Mobile US. what radio file should I use then? I'm in Cali located in Anaheim in the Disneyland Resort Area. Got EXCELLENT reception with the Nexus 5.

Sent from my Ñ£×Ú$ 5
[HTC One S] Brushstroke:
Ah okay, makes sense now. Give me a little more info about your device. What hboot is it? Is it the version that has the T-Mobile branding on it?

EDIT: Also, forgot to ask: is the phone S-ON or S-OFF?
[HTC One S] Dragn4rce:
International Version(Bought it from ebay, Hboot 2.15, S-OFF

Sent from my Ñ£×Ú$ 5
[HTC One S] Brushstroke:
I see. I have bad news. You might be out of luck as far as signal quality if you're in the US using the international version of the One S, I'm afraid. T-Mobile US uses a frequency band called AWS. It uses a combination of two bands, the 1700MHz band for uploading and the 2100MHz band for downloading, to provide access to their HSPA+ network. If you don't have one of those bands, you're going to be limited to 3G in the US on T-Mobile no matter what you do. The international version of the One S doesn't have the 1700MHz band needed for T-Mobile's network in the US.
[HTC One S] Dragn4rce:
The device will be on at&t(although not sure for how long.) and the phone originally came from solavei which is a US Carrier. So I dunno if that's changes anything. I do get H, H+, and 3G. So if there are any radio files you recommend for this device. How could I give you the model number (ex Gnex Toro+, Toro, etc)

Sent from my Ñ£×Ú$ 5
[HTC One S] Brushstroke:
You should be good using it on AT&T's network, at least according to this frequency list.
[HTC One S] Dragn4rce:
Any radio files you recommend then? Since it's using a EU Radio file apparently.

Sent from my Ñ£×Ú$ 5
[HTC One S] Brushstroke:
I'd keep the radio its on and bring it over to AT&T's network when you can. The radio isn't the problem, it's the lack of frequency band support on T-Mobile's network for that variant of the One S.
[HTC One S] Dragn4rce:
But I do get H+,H, and 3G tho. It's just everywhere however and constantly switching. Is the T-Mobile version 4G LTE capable? Or are all One S models 4G capable only(which is HSPA+). Which is why I ask which would be better and more stable and what you would recommend.

Sent from my Ñ£×Ú$ 5
[HTC One S] Brushstroke:
Nope, none of the One S variants have LTE, only HSPA+. It probably says you're getting H+ and is bouncing around a lot between 3G, H and H+ but I really suspect that's a fault of the device's incompatibility with T-Mobile's network. The hardware just isn't there. If it had the capability to work with the frequencies they use, you would see it switching consistently from 3G to H+ (and not see H at all) specifically when you're doing things that use data.
[HTC One S] Dragn4rce:
Could I at least try a radio file anyways that you would? Cuz the I found a thread with that has em and links are dead. I just wanna try it anyways and see what happens. The only good news is after making the suggested changes to the build.prop that Nicknc suggested I don't lose internet connection anymore.

Sent from my Ñ£×Ú$ 5
[HTC One S] Brushstroke:
You could try it, but I doubt it would do you any good. If I recall correctly, CM 10.2 and CM 11 use the radio listed in the hboot, and the flashable radios do not change the one listed in the hboot.

If you want to try it, you could try using the TMOUS 1.13 radio. It's what is installed by default when the T-Mobile stock One S ROM gets the OTA to Jelly Bean. The exact number is: 1.13.50.05.31_10.30.50.08L
[HTC One S] Dragn4rce:
Where can I find it? The radio thread here has dead links.

Sent from my Ñ£×Ú$ 5
[HTC One S] ChessSpider:
oh guys.. Im from Europe, and I only S-OFF'ed and went off the stock ROM about 2 months ago. i have radio 1.15. Never received a 1.16 OTA (nor a 1.20 btw) from HTC. I never manually up/downgraded my radio.

It doesn't seem as if 1.16 is a European radio?
[HTC One S] Brushstroke:
Besides that thread, I don't know where you would find it anymore. You could run an RUU to get it since your phone is S-OFF but I dunno, seems a bit overkill because you'd have to flash CM11 again.
[HTC One S] Dragn4rce:
Found this.

Sent from my Ñ£×Ú$ 5
[HTC One S] Brushstroke:
It's worth a shot. There's also a 1.20 radio I've seen mentioned that people have had success with.
[HTC One S] Dragn4rce:
Do you know where I can find that?

Edit: found it

Sent from my Ñ£×Ú$ 5
[HTC One S] Brushstroke:
Here you go.
[HTC One S] Dragn4rce:
That works well. It seems to switch to H+ when I need it lol. Not even kidding.

So the only issue now is WiFi.... >.> which cannot be fixed till later if I'm correct.

Sent from my Ñ£×Ú$ 5
[HTC One S] Brushstroke:
Huh, strange. Maybe I'll flash 1.20 for the hell of it and see what happens lol. I'm doing fine on 1.13 but whatever.
[HTC One S] Dragn4rce:
Don't fix what isn't broken... ?

When will we know WiFi had been fixed?

Sent from my Ñ£×Ú$ 5
[HTC One S] Brushstroke:
Hah, true.

I wasn't aware WiFi was broken. Works fine here...
[HTC One S] Dragn4rce:
Wth? I'm using the official build 1/24 and I can't connect to any WiFi.

What are you using?

EDIT: OH SH*T 1.12 FIXED IT! F*CK YA!

Sent from my Ñ£×Ú$ 5
[HTC One S] Brushstroke:
Official build 01/25. T-Mobile branded HTC One S, S-OFF, HBoot 2.15.

EDIT: Which radio? 1.12? Where did you find that? Or did you mean 1.15?
[HTC One S] The Setlaz:
Aren't you facing any of the issues I have on 24-25/01 ?

http://xdaforums.com/showpost.php?p=49763378&postcount=2477
[HTC One S] AndroidInsanity:
Can someone tell me which recovery to use to install the Hboot 216 version. I tried the crossed out CWM recovery in the downloads post but it never boots into recovery. I also tried using TWRP found in Maximus ROM firmware update. But it shows my device as if nothing is on it at all.

Or fails to flash.

If someone could tell me a link to a recovery that works?
[HTC One S] F-L-Y-E-R:
Hm... So maybe you downloaded the 2.15 version? Because recovery from 'maximus hd' worked and still working fine for me.
[HTC One S] nicknc:
Why haven't you tried the TWRP listed in this thread?
[HTC One S] AndroidInsanity:
I just have done still no luck :/

---------- Post added at 01:45 PM ---------- Previous post was at 01:45 PM ----------

Nope 100% downloaded 2.16 version. Thanks anyway

I found the issue. I am on 2.15 Hboot, it must of changed it to 2.15 from 2.16 when I did a RUU. Sorry
[HTC One S] Brushstroke:
I just tried using the 3x3 pattern lockscreen and it worked fine for me. I also wasn't aware that lockscreen rotation (or homescreen rotation, for that matter) had been introduced yet. I've only been able to use screen rotation in apps so far.
[HTC One S] The Setlaz:
Well, home-screen doesn't rotate with Launcher3 or default launcher, only the lock-screen does.
[HTC One S] intervigil:
Looks like the issue may be with the audio HAL. I'm guessing there are no routes for the audio output, so the HAL locks up trying to play the sound. What does logcat tell you about the route it's trying to use?

I'm pretty sure we don't have the correct audio routes for car docks and the like, mostly because I've never been able to test them. (I wasn't even aware there was some kind of car dock for the One S)
[HTC One S] eabinsan:
You are definitely onto something. Not sure how to check the audio routes though. Logcat repeats the following until it dies around 60k lines later:

I will gladly assist you in testing the dock - seems nobody else is using it, because its 40 € :)

I/ActivityManager( 659): Process com.andrew.apollo (pid 6201) has died.
D/ALSADevice( 255): close: handle 0xb86330a8 h 0x0
E/alsa_pcm( 255): pcm_close invalid pcm handle:0xb5d65164
D/ALSADevice( 255): close: handle 0xb86330a8 h 0x0
D/ALSADevice( 255): open: handle 0xb86330a8, format 0x2
D/ALSADevice( 255): Device value returned is hw:0,0
E/alsa_pcm( 255): cannot open device '/dev/snd/pcmC0D0p', errno 22
E/ALSADevice( 255): open: Failed to initialize ALSA device 'hw:0,0'
E/alsa_pcm( 255): cannot prepare channel: errno =-9
E/AudioStreamOutALSA( 255): pcm_write returned error -9, trying to recover
E/alsa_pcm( 255): pcm_close invalid pcm handle:0xb5d65164
D/ALSADevice( 255): close: handle 0xb86330a8 h 0x0
D/ALSADevice( 255): open: handle 0xb86330a8, format 0x2
D/ALSADevice( 255): Device value returned is hw:0,0
E/alsa_pcm( 255): cannot open device '/dev/snd/pcmC0D0p', errno 22
E/ALSADevice( 255): open: Failed to initialize ALSA device 'hw:0,0'
E/alsa_pcm( 255): cannot prepare channel: errno =-9
E/AudioStreamOutALSA( 255): pcm_write returned error -9, trying to recover
E/alsa_pcm( 255): pcm_close invalid pcm handle:0xb5d65164
D/ALSADevice( 255): close: handle 0xb86330a8 h 0x0
D/ALSADevice( 255): open: handle 0xb86330a8, format 0x2
D/ALSADevice( 255): Device value returned is hw:0,0
E/alsa_pcm( 255): cannot open device '/dev/snd/pcmC0D0p', errno 22
E/ALSADevice( 255): open: Failed to initialize ALSA device 'hw:0,0'
E/alsa_pcm( 255): cannot prepare channel: errno =-9
E/AudioStreamOutALSA( 255): pcm_write returned error -9, trying to recover
E/alsa_pcm( 255): pcm_close invalid pcm handle:0xb5d65164
D/ALSADevice( 255): close: handle 0xb86330a8 h 0x0
D/ALSADevice( 255): open: handle 0xb86330a8, format 0x2
D/ALSADevice( 255): Device value returned is hw:0,0
E/alsa_pcm( 255): cannot open device '/dev/snd/pcmC0D0p', errno 22
E/ALSADevice( 255): open: Failed to initialize ALSA device 'hw:0,0'
E/alsa_pcm( 255): cannot prepare channel: errno =-9
E/AudioStreamOutALSA( 255): pcm_write returned error -9, trying to recover
E/alsa_pcm( 255): pcm_close invalid pcm handle:0xb5d65164
D/ALSADevice( 255): close: handle 0xb86330a8 h 0x0
D/ALSADevice( 255): open: handle 0xb86330a8, format 0x2
D/ALSADevice( 255): Device value returned is hw:0,0
[HTC One S] nojoboy:
ART 1-25

ART runtime not working on 1-25
[HTC One S] Brushstroke:
Works fine for me. What happened when you tried to enable it?
[HTC One S] nojoboy:
It just turns off like its going to switch to ART but when its starting back up it just turns on like normal (the android is upgrading process doesn't run) and when I check it, it's still on Dalvik. Tried multiple times but does the same thing.
[HTC One S] Brushstroke:
Strange. Is this on a clean flash of 01/25 or did you do an update from a previous build?
[HTC One S] nespresso33:
Disable Xposed framework
[HTC One S] nojoboy:
I updated from 01/23 where it was working... I have since switched back to 01/23 and it is working again.
[HTC One S] intervigil:
The actual routes it's attempting to use should show up with an alsa_ucm tag. Since you are plugging in a USB dock, you can't use adb over USB, so use ADB over WiFi to get the log. Run adb logcat alsa_ucm:* *:S then connect the dock.
[HTC One S] leosparta:
Viber stops working when answering a call :P

it's really annoying that every time when i get a call on viber it stops working

is there any solution please !?
[HTC One S] eabinsan:
Thanks, it show only the following lines between plugging in and rebooting:

D/alsa_ucm( 255): snd_use_case_set(): uc_mgr 0xb8f83188 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 0xb8f83188 identifier _enadev value USB PROXY Rx
E/alsa_ucm( 255): No valid device USB PROXY Rx found
[HTC One S] Insecret:
You can try this it is walkman app with latest libs of alsa, maybe it will fix your issue. Don't forget to make a nand.
[HTC One S] mikronac.ns:
I have GPS related reboots while play Ingress... :/
[HTC One S] provaleriy:
And I have 3G related reboots...
[HTC One S] Insecret:
Use OnDemand governor
[HTC One S] icest0rm:
hi, does this rom still have many bugs?
[HTC One S] nicknc:
Only the ones listed in the last ten pages or so.

:)
[HTC One S] icest0rm:
so still not for production use
[HTC One S] el_smurfo:
It's fine for daily use.
[HTC One S] Sebba513:
My brother has this rom on his phone, he was running 2014-04-01 build, but Maps didn't work for him so I told him to update to latest nightly, which was 2014-25-01. Now his WiFi doesn't work. He cleared the cache, dalvik cache, but WiFi still doesn't work. Is there any way to fix this without clearing data? it's not S-Off so i guess the new kernel didn't install.. He's hboot 2.15
[HTC One S] Insecret:
WIPE everything, then fastboot flash boot boot.img after that chose the apropiate zip in recovery to install it. No issues are officially for dirty installs
[HTC One S] Sebba513:
Is there any other way? He's not techie enough to do that by himself, and I won't see him for like another 2 weeks. He's on a Mac too, so that could be difficult as well.
[HTC One S] ApneaB:
He can try flashing boot.img using flash image GUI, that worked fine for me when I was still s-on.
[HTC One S] striped121:
Download bubba kernel and flash as you did the ROM in recovery
[HTC One S] intervigil:
Yup, USB PROXY Rx appears to be missing... I'll look at it.
[HTC One S] eabinsan:
Thanks! Does that mean that audio will be routed through USB in that case? Because I don't think that my cigarette plug does audio :eek:
[HTC One S] el_smurfo:
He is S-ON. As stated previously, download Flash Image GUI from the Apps forum (or buy in Play Store to support great app). Use it to flash the boot.img which you are not flashing properly now.
[HTC One S] gajodafeira:
That's not the place but... I have S-ON too, it has to be off? I install any release with twrp recovery and sometimes i get status 7, and with the roms that install fine, it wont boot..
[HTC One S] Sebba513:
Will bubba kernel flash in recovery still work even though it's s-on? I thought you needed a computer for that.

Also, has anyone tried using flash image GUI while s-on? I'd rather know for sure instead of jeopardizing losing his phone for 2 weeks..
[HTC One S] ApneaB:
Yes, me and many others, as stated above.........
[HTC One S] The Setlaz:
No, if S-ON, you just have to manually flash the boot.img (for those who are S-OFF, it is done automatically)

If you have boot or wifi issue, that would most likely fix it.
[HTC One S] thiasB:
Me too :( Also tried Bubba with no improvements. this and the permanent 3G,H, H+ switching are the only annoying bugs left. And for those who don't see the GPS related reboots, this issue IS real. try switching an app which uses GPS from backe to foreground multiple times and you'll have a reboot for sure. The number of switches to force the reboot is random.

On the other hand I love the speed of the device esp. when considering that it was released about two years ago. Its worth to maintain it for another two years ;)
[HTC One S] gajodafeira:
So, I flash the ROM and I have to flash a boot after? In my other devices that never hapened..
[HTC One S] el_smurfo:
Welcome to HTC's half-a$$ unlock. If you have a booting system, I always flash the boot.img first using FlashImage GUI, then reboot and install the ROM in recovery.
[HTC One S] gajodafeira:
I have a samsung tab and a Nexus 4 and it's not like that... So, from the beginning. I flash the ROM and the Gapps, now what?
[HTC One S] el_smurfo:
As has been stated many times, including the OP, you will need to flash the boot.img. If you are in recovery, you can mount your SD, extract the boot.img from the ROM.zip, then reboot to the bootloader/fastboot and flash it will this command from your PC. It is documented well throughout these forums.

fastboot flash boot boot.img
[HTC One S] The Setlaz:
1. Boot in Bootloader, flash the boot.img. ( http://xdaforums.com/showthread.php?t=1752270 )

2. Reboot in recovery

2.0 Wipe Cache / Wipe Dalvik

2.1 Flash the ROM

2.2 Flash GApps

3. Reboot and enjoy CM11
[HTC One S] epsiblivion:
running 1/26 official nightly on 2.15 hboot, cwm 6.0.4.6 touch. only issue seems to be wakelag so far. I thought that was solved months ago (it is solved in 2.16 build). very odd
[HTC One S] el_smurfo:
Yeah...they were tinkering with the phone screen blackout issue. Solved that, but the next days they tweaked a few more things and now the wake lag is back. Seems worse than before to me because you used to be able to swipe the screen unlocked before the panel even came on, but now it doesn't seem to work like that for me.
[HTC One S] epsiblivion:
hmm a shame. I can't wait for all the new phones to come out already so I can pick an upgrade. going by last year, s5 and m8 should be out by mid april.
[HTC One S] nespresso33:
Big changelog incoming for next nightly.

Happy to see that work for our phone, I remember with CM10.2, my One S was so unstable, not smooth, I wanted to buy a new phone, CM team made me save money.
[HTC One S] Brushstroke:
You mean 01/28, right?
[HTC One S] nespresso33:
Yes, I like to see the work done by the team http://www.cmxlog.com/11/ville/
[HTC One S] Navik57:
Any way you can send me the firmware.zip file you used? We'll see if that works. If not, I'll try turning s-on.
[HTC One S] icest0rm:
well, if push notification are not working after a while, wi-fi not always working, how can we say is fine for daily use? :confused:
[HTC One S] ATSPerson:
Been running CM11 for well over a month. Yes there are a few little niggles but perfectly usable as a daily driver.

If you want perfection. Keep looking. (and good luck, it'll be a long search)
[HTC One S] icest0rm:
well, I don't want perfect...actually I'm using MIUI which is very nice but has some bugs and since HTC One S is not an officially supported device but the rom is ported, there is no possibility to get those bugs fixed.

I'm searching for a new ROM to switch, I'm looking forward to CM11, SlimKat and others, trying to focus on which would be the cons of every ROM.

In my opinion push notifications not working after a while are not a little bug, am I wrong? can you live with this?

OTA also would be a nice plus seeing all these nightly builds with extreme development
[HTC One S] ATSPerson:
Personally the push notification bug you describe bug doesn't affect me, but if it did it wouldn't be the end if the world, I could easily live with it. WiFi is a little flaky, (but perfectly usable, I don't use mobile data at all) but that's the same for all CM based ROMs.

I can honestly say weighing up all pros and cons for me CM11 is the best ROM I've had on this phone in the two years I've had it. 4.4/CM11 has given our abandoned handset a new lease of life.
[HTC One S] nicknc:
Hey man, this really doesn't belong in this thread. If you don't mind, either take it to the firmware threads or start a new one. Just post a link here pointing to where you went and we will follow you there.

---------- Post added at 06:28 AM ---------- Previous post was at 06:25 AM ----------

Be best to just read through the last week or so of posts and decide for yourself.

:)
[HTC One S] ThomasHunter:
So I saw some people talking about wakelag some pages ago.

I'm on 1/18, and since a few days my device has a no-sleep policy. :(

The drain isn't huge, but more than I'd like. Also, when I go to Partial Wakelocks in BBS, it only counts seconds of wakelocks while it's been awake for five hours now. So the Kernel Wakelocks add up in percentages, but the Partial do not. That's been an issue for several weeks now, for me. Any ideas?

Of course, if anyone could give a tip to stop the device from being awake, you'll have my greatest thanks.
[HTC One S] nicknc:
This persists after a reboot, right? You running art or dalvik?
[HTC One S] Insecret:
Better without bubba, stock kernel is more stabile
[HTC One S] ThomasHunter:
It does persist, yes. I'm running old trusty Dalvik, haven't even tried ART yet. It does seem to vary; sometimes it's 50-50 awake-asleep, but multiple charges have been 100% awake.

I also had 3G on for the whole charge one time, and at a given point it was at 12%/hour discharge. So yeah, it can be a problem.
[HTC One S] striped121:
Is live wallpapers working for everyone? Just force closes for me?
[HTC One S] ThomasHunter:
It does work for me. Used Phase Beam and now the Grass wallpaper (I know, I know. I like that it changes according to the time of day).

Worked on snapshot build and my current, 18/1.
[HTC One S] RockR172:
I don't get this.

WHY are people upgrading their HBOOT when there are ROMs available for both 2.15 & 2.16 versions?

2.15 will get official nightlies, 2.16 won't.. I do builds for 2.16 for people who are already on that hboot and don't want to downgrade, yet use CM..