yashsingh1/xdaforums huggingface dataset:
[HTC One S] kavafree:
When I enter Network Operators it starts searching and fails after 40 seconds. Then I can select search networks, which starts a new search (which also fails) or choose automatically which brings up a toast that says registered on network.

I've compared my APN with a friend who has the same carrier and they are a match.

In About phone/Status I can't find anything special, but the IMEI seems to be correct.
[HTC One S] bobjbain:
[MENTION=5350204]ThomasHunter[/MENTION] (the new TapaTalk won't let me quote your post) from what I remember about CM naming conventions the M2 is just a snapshot at a certain point in time, sort of random but not, the nightless after an M2 are generally just as stable, if not more so, that the M2 release....

General question now. Is it just me the compass is broken for or is it for everyone or is there a setting I am missing?
[HTC One S] el_smurfo:
Happens to me sometimes. I just use GPS toolbox to calibrate it, then it works again. Someone said you don't even need the app, just rotate the phone several times on each of the 3 axes to self calibrate.

FYI, 1/17 build is up. Has some new light dialer theming, some settings shuffling and a few new lockscreen options. Running well for me.
[HTC One S] nespresso33:
Flash latest nightly only if you want an unusable phone, I warn you :)

So many changes in the changelog.
[HTC One S] el_smurfo:
Huh? Been running for half an hour or so with no issues.
[HTC One S] nespresso33:
Maybe because I updated with Cyandelta.
[HTC One S] el_smurfo:
Seems likely. During the day, I always download the full file on my PC from the CM download site, since I have terrible EDGE service at work.
[HTC One S] nespresso33:
I flashed the full zip, and I get again an unusable phone.

I don't want to do a full wipe now.

Let's see tomorrow if it affects others people too.
[HTC One S] el_smurfo:
weird. did you update the kernel properly? now on version 3.4.76

EDIT. Take that back. Took off charger and have had two reboots in 5 minutes. Guess it's a pass on this one guys.
[HTC One S] aasterix:
I can confirm that.

Kernel 3.4.76

Im s-off and the flash went flawlessly and no problems using the phone now.
[HTC One S] el_smurfo:
Reverted to 1/15...suspect "input boost" commits are causing reboots yet again.
[HTC One S] Brushstroke:
I updated with CyanDelta and my phone works fine? When was the last time you updated before tonight?
[HTC One S] bilal_liberty:
i flashed the latest nightly, so far seems stable.
[HTC One S] Brushstroke:
What are these input boost commits?
[HTC One S] Brooklyn8807:
Running drkxyz 0117-hboot 2.16 build and its running smooth. Love me some stable CM. :)
[HTC One S] el_smurfo:
From my recollection, input boost was causing our previous reboot issues. There were commits to revert this fix and implement in a different manner in this last nightly. I had at least 5 reboots, most while screen off, before flashing 1/15 back.
[HTC One S] Brushstroke:
Hm, weird. I haven't experienced any reboots at all since I updated at about 6 PM (it's a little after 9 PM here now) and I updated in the same way nespresso33 did. Streamed some music from Google Play in the car on my way home, sent a few texts while in the store, a brief call, and now I'm tethering. No problems.
[HTC One S] nicknc:
No reboots here. Using cyandelta and bubba.
[HTC One S] el_smurfo:
You guys are making me want to try again...for no reason at all!!!
[HTC One S] Brushstroke:
You should! I'm not using Bubba, just the stock kernel. But seriously, just flash 01/13 cleanly (this just happens to be the last clean flash I did) and then do an update with CyanDelta and do delta updates every day or every other day. You can't go wrong I think. I've been updating through CyanDelta for a couple weeks to a month, then I do a clean flash of the latest nightly, rinse and repeat.
[HTC One S] nicknc:
Don't rule out a bad flash. Although I've only had it installed for four hours or so.
[HTC One S] el_smurfo:
Did that and stable for an hour. I'll let it ride overnight and see if it reboots.
[HTC One S] adobrakic:
Just a heads up, latest update causes constant reboots for me. I hadn't had reboots in a while. I downgraded back to the Jan. 15th nightly, iirc, and the reboots have stopped.
[HTC One S] mikronac.ns:
Dialer photo is awful in newest build. Someone put black background and cover half of dialer photo... :@
[HTC One S] |RaVeR|:
My phone rebooted twice within minutes of installing the 20140117 nightly. went back to 0115

Reboots occur maybe once or twice a week for me usually, so it COULD be a coincidence, but that would be unlikely. Is is working for everybody else?
[HTC One S] ThomasHunter:
Quoting for me is tapping a post and then pressing the "message" icon. But their shuffling up the layout every update isn't a good thing.

Anyway, on topic! Yeah, I'm a bit familiar with that, though I thought people said it consisted of some older, "more proven", commits.

So the newest nightlies (couple days old, I see the opinion on the very newest varies) are quite stable? :)
[HTC One S] bobjbain:
Nah, when I was trying to quote your post it kept chucking up "invalid thread id" or something like that

For me they are very stable, saying that I installed the 17th ROM yesterday and started getting random reboots all over the shop. So I just re-flashed an older ROM!

Ah I see the random reboots is a common theme on the 17th ROM, commentators curse strikes again...
[HTC One S] mikronac.ns:
May anyone tell me how autmatic brightness works on other CM phones? Is it there problem like we have on ville? Do any other msm8960 phone have this problem? I am trying to find out what causing problem...
[HTC One S] maluus:
Unstable here too. 2-3 reboots out of nowhere and then again when I woke up found the phone rebooted again waiting for pin. Had to go back to 15/01.

Enviado desde mi One S mediante Tapatalk
[HTC One S] Merche300:
I'm using the kernel for two days no reboot

Enviado desde mi One S mediante Tapatalk
[HTC One S] striped121:
17th has been stable for me since yesterday using bubba. No reboots
[HTC One S] el_smurfo:
It's the CM kernel that's unstable. Comments about bubba really should stay in the bubba thread.
[HTC One S] Merche300:
Sorry my kernel is Bubba

Enviado desde mi One S mediante Tapatalk
[HTC One S] Brushstroke:
I take back what I said about the 01/17 build being stable. It's not. Reboots everywhere.
[HTC One S] maluus:
Anyone tried todays? I mean 18/01. Any improvement?
[HTC One S] el_smurfo:
Yeah...tried 1/15 kernel and still reboots. Back to 1/15 ROM

Looks like pages of kernel commits in 1/18. Should be a fun ride for the first brave one to try that.
[HTC One S] Aktivehate:
The 20140118 build has an massive changelog with kernel improvements, so maybe the reboots are gone now. Maybe the input boost was an early commit for this.
[HTC One S] nespresso33:
Where is your massive changelog ?

I see only that for the kernel in 1/18 http://review.cyanogenmod.org/#/c/57741/
[HTC One S] Aktivehate:
It was in the changelog for the msm8960, and that's are soc. The commit you posted is also made under the msm8960 kernel, only ville specific.
[HTC One S] el_smurfo:
Click on the 1/18 nightly in the cmupdater for the full change log from the build bot
[HTC One S] maluus:
well 18/01 seems to be stable for now.
[HTC One S] Michael1101:
Also for me.
[HTC One S] blinksilver:
Has anyone on 1/18 noticed the end result of this commit? I went through the diff loosely and on the surface it just looks like some code clean up/reorganizing. At best it might improve the screen delay a bit.
[HTC One S] mikronac.ns:
It is always better when you using switch/case statements instead of bunch of if/else/elsif conditions... It is faster a little bit...
[HTC One S] ChessSpider:
Well, a good compiler should optimize it to the same opcode AFAIK. But it s neater. Still can't find the more elaborate changelogs btw. I am using http://www.cmxlog.com/11/ville/
[HTC One S] justaway2:
You'll see it in the built-in CM updater.
[HTC One S] adobrakic:
An update to this issue, I upgraded to today's nightly (1/18), and I've yet to experience any reboots after 2 hours.
[HTC One S] el_smurfo:
Seems maybe the 17th nightly built between commits. 18th ok for me for the last hour.
[HTC One S] jnne2012:
Running 18th about 4 hours without problems. Dirty flash over 15th so i think its ok.

Lähetetty minun One S laitteesta Tapatalkilla
[HTC One S] leald:
Has anyone addressed the snapchat front facing camera issue yet? I have asked before and haven't really gotten a response. And haven't seen anyone else talking about it. Thanks.
[HTC One S] el_smurfo:
What's snapchat?
[HTC One S] kavafree:
An app for sending pictures and videos to your friends (which get deleted after given seconds). I got the same problem, and I've seen a lot of other people having the same problem. Works in stock camera, but not in Snapchat.
[HTC One S] el_smurfo:
So, dickpics? Does any other pic sharing app do this, because hangouts and others I use seem fine.
[HTC One S] Brushstroke:
Pretty much.

Also, there's a slight delay when turning on the lockscreen on the latest nightly. Have you noticed? It's not a big deal but still…
[HTC One S] el_smurfo:
Agreed...delay is worse.
[HTC One S] blinksilver:
I would go as far as to say, it can be once again categorized as a "bug".

I feel like this is going to end up like wifi, its buggy, but we've all agree to just deal with it.
[HTC One S] redspeed:
Ok to flash over latest 2.16 release?
[HTC One S] drkxyz:
I've been running it since Friday with no problems yet, also not a single reboot. I guess I was lucky when syncing the

CM sources since the official 0117 nightly seems to have some problems
[HTC One S] Brushstroke:
01/18 (official 2.15 version) nightly running very smooth. No reboots since last night and I think my battery life has gotten better too.
[HTC One S] nojoboy:
ART runtime.

I strongly recommend everyone try out the ART runtime (located in developer options) it greatly improved my battery life as well as improved multitasking performance along with smoother and faster transitions. The graphics performance is also better. When I switched back to Dalvik to see the difference it felt laggy and slow in comparison.
[HTC One S] Rapier:
I couldn't find any difference in using ART. And some use Xposed framework which is incompatible with ART

Sent from nowhere over the air...
[HTC One S] Brushstroke:
So ART is actually working and functional now?
[HTC One S] elias.acab:
Last time I switched to Art, most app on my phone would crash, including the playstore. Does it actually work now? and did you have to flash different gapps?

Thanks
[HTC One S] ATSPerson:
I'm running 19/1 nightly, but I've noticed recently WiFi is flakier than ever.

Just me?
[HTC One S] jnne2012:
Im using 19/1 and wifi is ok for me. I updated from 18th build with cyandelta. Everything working fine.

Lähetetty minun One S laitteesta Tapatalkilla
[HTC One S] mikronac.ns:
Hm, I just flashed newest build and I dont have lockscreen delay and neither delay without lockscreen. Image is showed very quickly...

If you want I will compile latest kernel source with reverted commit which Ethan included and you can test it to see difference...
[HTC One S] el_smurfo:
Not for me...the delay was never that big of a deal, because you could unlock the phone before the screen came up. I don't use any lockscreen widgets, so don't even look at the phone when unlocking.
[HTC One S] Michael1101:
today I started backup via twrp since about two weeks. It gave me an error: tarring split files. It worked without problems before and I didn't change my setup, except always updating newest nightlys. I googled but didn't find a solution.
[HTC One S] nespresso33:
You have to rename the backup name. Because the name by default is too long, I don't know why.
[HTC One S] el_smurfo:
I just hit the date tab and it names the file with the date alone but that doesn't sound like his problem...Maybe a full sd card?
[HTC One S] Michael1101:
I renamed the file. If I won't rename it, it gives me an error right at the beginning. The splitting error occurres after a while.
[HTC One S] nespresso33:
Is there enough space ? Try do disable compression if enabled.
[HTC One S] Michael1101:
Compressions is disabled. And I got around 5gb free space.
[HTC One S] nespresso33:
Do you have this app https://play.google.com/store/apps/details?id=com.gogii.textplusgold&hl=fr ?
[HTC One S] Merche300:
ART works with rom Day 13 -1 -2014, hboot 2.16?

Enviado desde mi One S mediante Tapatalk
[HTC One S] Darknites:
Lame wasn't like that for 1.15.
[HTC One S] nicknc:
Nope, no evidence, but 2.15 with CM10.2 is bootlooping all over the place for me the past few days. Random reboots are back in a bad way. I figure best to jump on up now, and if it stays bad on CM11, this way I can go ahead on to Sense.

---------- Post added at 07:33 PM ---------- Previous post was at 07:32 PM ----------

It doesn't happen to most folks. I guess I'm one of the lucky few. Hooray.
[HTC One S] nicknc:
Okay, so for the sake of other folks that might deal with this...

Went for the bootloader unlock again, it worked this time (still shows tampered though).

Now, TWRP is prompting me for a password (which I never set, of course). I reflashed TWRP, and it's still prompting for a password. I can bypass the password check, but can't get access to any partitions.

Any suggestions?
[HTC One S] don.peugot:
Oh dear. I was there. Took me two days to figure it out...

So. Basically the new partition system on HBoot 2.16 screws up your twrp. It puts some kind of encryption on the filesystem, or at least that's how twrp sees the new partition system. That's also why a lot of people (including me) only got 48 MB of storage after updating to HBoot 2.16.

I solved these issues by going back to HBoot 2.15. For that, you'd need to run an RUU. Since I'm no expert in all these things and I'm just telling you what happened to me, you should gather some information before flashing, because according to my last information downgrading your HBoot is RISKY. Also, I think if you're s-off you can just flash another HBoot. But again, better get some other opinions on this one, also I don't know if just flashing the HBoot solves the issue since I did the RUU thing.

It took me some time though. Had to run it multiple times and also my phone seems to run less stable after the whole adventure, but this might be a wrong impression. Sorry that you have to make the same experience as I did...

Gesendet von meinem One S mit Tapatalk
[HTC One S] el_smurfo:
Can you try fastbooting philz or cwr?
[HTC One S] nicknc:
Thanks for weighing in-- yeah I got that 48mb partition too. Well, I reflashed the firmware (which fortunately left my bootloader unlocked this time). Then I reflashed TWRP 2.6.1.0 (provided with the firmware package on the maximus site).

This repartitioned my device, and I'm able to see the full 12GB again.

So, I had to close the command prompt so that I could adb sideload CM11 back on. For some reason, it wouldn't find the device, despite killing and restarting adb.

Sideload supposedly worked, but didn't install anything, and the sideload.zip file disappeared. I may try with a different recovery.
[HTC One S] topnomi:
I think it's encrypted due to the unlock process. Try wiping your partitions, pushing the rom via adb push, and flash the rom.

adb shell
mkdir /sdcard/@ROMS
exit
adb push ROMLOCATION /sdcard/@ROMS
adb push GAPPLOCATION /sdcard/@ROMS

I think i remember doing this with my wife's one s. I tried using the 2.16 hboot when i tried Maximus HD.

It's funny, she hates Sense, but her phone keeps random rebooting/bootlooping with most anything cm based. It ran perfect, with no issues whatsoever on Maximus, but she hated a few things about sense and told me to switch it back. I've had better luck with bootloops on beanstalk 4.3.1, but she's having other issues with that.

I'm hoping CM11 on 2.16 will clear up these reboot/bootloops issues. :fingers-crossed:
[HTC One S] nicknc:
Which philz should I use?

---------- Post added at 09:23 PM ---------- Previous post was at 09:21 PM ----------

I'll give it a shot, but after sideloading, I can't even get adb to recognize the device (error:device not found)
[HTC One S] el_smurfo:
There's a thread in development, but not sure how stable it is. Was just a thought
[HTC One S] topnomi:
I had that issue. let it sit for a few minutes. i freaked out at first when it wouldn't connect. i found some new drivers, and was downloading them when all the sudden it started working.

you can type "adb devices" to see if any devices are connected. Just keep pinging that command every minute or so. (or every few seconds:silly:)
[HTC One S] AKToronto:
As an fyi, what this usually means when the password thing comes up without your prompt is that somehow the data partition has become corrupted. A format is needed.
[HTC One S] nicknc:
Thanks for the extra ideas. I went and flashed TWRP 2.6.3.0 through fastboot and got 48mb storage (was trying to see if that would help with the adb issue, and didn't see your suggestion yet). Flashed TWRP 2.6.1.0 back on there, and it rebooted into CM with 12GB showing.

I let it mount the SD-card in Windows and then copied gapps and bubba kernel back on. The file structure was rendering horribly in windows, so I'm not sure if it took. Either way, I'm going to try to flash those on and wipe/reflash CM to see where I'm at.

---------- Post added at 09:41 PM ---------- Previous post was at 09:39 PM ----------

That's a good point, and I tried formatting data several times. After about 4 or 5 tries, it quit prompting for password, but started with the "48 mb" crap. Hopefully this little adventure helps the next guy out.

CM11 is booting for now, but TWRP's adb sideload still seems to be taking an eternity to link up.
[HTC One S] aegentirony:
Can't you just mount SD from recovery? Then copy files like normal?
[HTC One S] clubkevin11:
I actually had this as well, except that the RUU didn't manage to run all the way but just enough to put my hboot back at 1.06. After this I flashed the update (2.15), flashed the stock recovery, cleared storage and factory reset it, then flashed TWRP, then I was able to mount/see my 12 GB on my SD card. I then proceeded to sideload CM 10.1.3 (I had previously deleted the system) and got my phone booting. Now I'm on this ROM and its running great despite some bugs.

I don't know about you guys, but I also wasn't able to mount my SD (soft-brick) so this was the only thing that worked. I hope i can save some of you a couple of days lol.
[HTC One S] AKToronto:
With the new firmware, the data partition and sdcard are formatted differently in EXT4 (as one partition). This has benefits and drawbacks. One drawback is you cant mount the sd card in recovery, as its not FAT32 and wont be recognized by windows... The benefit is that you can divide space between apps and sd card as you see fit, so you can load a lot more apps onto your phone, if you dont mind that taking away some space for videos, music, etc.

---------- Post added at 10:46 PM ---------- Previous post was at 10:44 PM ----------

LOL, yes hopefully it does. It also goes to show that you need to follow the instructions very carefully in order to do the firmware upgrade, and read a few of the posts in maximus, in order to avoid these issues, and use the right recovery with the new firmware.
[HTC One S] nicknc:
Alright, so all seems to be working now. I just have to go back through (again) and install Trebuchet, etc.

So for those folks with similar issues to mine (48mb data partition, no sideload, locked bootloader after hboot upgrade, etc.)-- here's what I did to resolve:

1) Unlock bootloader with HTC Dev site

2) Flash firmware again through fastboot

3) Flash the TWRP given with the MaximusHD hboot installer zip through fastboot

4) Go into TWRP and make sure your data/internal sdcard partition is set to 12000mb

5) If you get prompted for a password to get into TWRP -or- you see anything less than 12GB for data, go back and do 2 and 3 again

6) adb sideload cm11, gapps, and kernel cleaner/bubba zip - keep in mind it may take a few minutes for the PC to recognize adb devices

7) It's basically normal install stuff from there

I'm getting a lot of exchange and email f/c's after restoring my data partition, but it tapered off before, so I'll see if it does the same now.

It's nice to be able to warm reboot without bootloops, btw. :)

Thanks to those who jumped in to help.
[HTC One S] Brushstroke:
Okay, I've been reading through this thread and I'm noticing some similarities with this and Maximus. Similar problems. I just want some clarification.

- I am on HBoot 2.15

- My phone is S-OFF with Moonshine.

- I'm currently running CM 10.1.3

- My recovery version is 2.6.3. It's the one from the TWRP website, not the modified one from Maximus.

Can I flash the version of this ROM that works with 2.15 like I normally do without flashing the boot.img?

Thanks.
[HTC One S] nicknc:
Yes, but a lot of standard settings will be missing due to the beta status. Just know what you're getting into-- this is NOT a daily driver (and that is reflected in the first post). You'll likely want to grab the trebuchet.apk from your CM10.1.3 zip at a minimum.

I've also found I have to recreate my exchange accounts.
[HTC One S] dcacklam:
I've noticed that the Settings app seems to be 'vanilla', without any of CM's customizations or even some standard Google tweaks... No cLock lockscreen, lockscreen customization (change 'circle' actions or add/remove widgets), hard button remap, or APN editing, for instance....
[HTC One S] nicknc:
What's funny is that those settings will import in if you import your data through twrp. Also, try DashClock, same thing as cLock, but more extensions.

My custom key mappings are working great.

Just got my first random reboot, though. And can't get my exchange contacts to sync. Exchange settings are flaky too.
[HTC One S] Michael1101:
I also read this. No I don't have it. Maybe another app I installed lately. I have to try :( anyone got the Jenkins link of the newest cwm? (even I don't like it, I feel naked without a backup)

Edit: nevermind got the link
[HTC One S] JgCurry:
01/19 Akku is ok

Gesendet von meinem One S mit Tapatalk
[HTC One S] Navik57:
Just brainstorming on this issue with not being able to connect to different networks... could the CID have anything to do with it? I currently have super-cid.

For those that are able to search other networks, do you also have Super-CID? (11111111). For those that are not able to scan the networks, same thing?
[HTC One S] kavafree:
I have Super-CID and can not search for networks.
[HTC One S] el_smurfo:
Maybe your network needs the correct cid?
[HTC One S] kavafree:
Just reverted to the old CID. Still doesn't work.
[HTC One S] Flashalot:
Have you flashed any new radios or flashed the leaked firmware

If you have flashed the leaked firmware then change your radio the radio in the at firmware is best on sense Roms
[HTC One S] kavafree:
List of my modifications:

- I've run RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4

- S-OFF / SuperCID

- International firmware in this thread.

- Modded HBOOT 2.15.0000 to remove the dev warning

- Changed the HTC boot animation.

- TWRP 2.6.3.0a (unofficial)

- cm-11-20140119-NIGHTLY-ville.zip

- Now back at HTC__H10 CID.

Anyway, doesn't cm override your radio if you do not flash anything after installing it?
[HTC One S] mik11279:
I have exactly the same problem! but it seems as there is no easy fix for this!
[HTC One S] ChessSpider:
My phone is stock with the exception of CM11 on 2.15 with S-OFF. Radio is still 1.15, never SuperCID or w/e.. Experiencing same problem @ Tele2 network (Roaming to T-Mobile) in Holland. Note, I had to do these fixes from [MENTION=2207213]nicknc[/MENTION] to get a reliable connection.