yashsingh1/xdaforums huggingface dataset:
[HTC One S] machoman1337:
Better yet, would it be possible to integrate the data drop fix into an older 3.0-kernel build? Those never had GPS or lockscreen delay problems and were perfectly fine apart from the data drops. I know the 3.4 kernel frees up more memory for the user, but it's not like the 3.0 kernel was a slouch.
[HTC One S] el_smurfo:
3.0 kernel build will never be supported due to the focus DMCA issues. One of the main benefits of cm is running the latest Android, so its time to just cut off those older builds.
[HTC One S] abracadabra11:
Anyone else getting horrible battery life on 10.1.3 stable? Looks like 12 hours of standby is enough to drain the battery from full.
[HTC One S] mannequin:
el_smurfo,

so it still doesn't reboot for you no matter what (talking about latest builds)?
[HTC One S] el_smurfo:
If you read back, you'll see I've had periods of terrible boot loops in the last few builds, but usually after flashing or following a manual reboot. I dont use navigation, so don't really have many other common causes of spontaneous reboots.
[HTC One S] nicknc:
Chiming in here--

As long as I don't allow an automatic reboot after flashing a nightly,

I do not get bootloops

. Even after manual reboots. This is something I noticed a day or two ago, and have confirmed for the past three nightlies.

Also, Waze navigation works very well for me with no reboots at all. Maps DOES give me random reboots, but nowhere near the frequency described here.

I am S-Off, and always download the latest nightly through Cyandelta (which really is a pretty cool service)

Could either of you try my suggestion of forcing a power off after flashing before that first post-flash boot? I'd be interested to see if that resolves the reboot bootloops for you.

On a side note, it seems the data drops occur most frequently for me when switching from one T-Mobile tower to another (I drive the same route across three counties every day, and know exactly where tower handoffs occur). Also, they calm down significantly after rebooting my phone. Manually, of course. Without a bootloop :)
[HTC One S] el_smurfo:
It was the same for me, but after flashing 9/24, I fully powered down, then endured a series of a half dozen bootloops. Been fine since.
[HTC One S] Phuturist:
Second that. I'm also experiencing the gray Wi-Fi signal bars again which results in no internet until you flip airplane mode.

Should have stuck with the nightly of about a week ago, all was perfect then. To addicted to the nightlies though.
[HTC One S] jmginer:
What is the better 10.2 nightly?

Currently using this: cm-10.2-20130905-NIGHTLY-ville.zip

But some bug on GPS that cause phones restarts.

What you recommend to upgrade?

Thanks!
[HTC One S] Pickled Jesus:
I had horrible drain with all verisions for a long time (i thought my battery was bad), but it disappeared after i did a FULL wipe...(not just factory reset..). Try that.. Worked wonders for me.
[HTC One S] :
Hm. Something rather odd just happened: When I flashed the Sept 26 nightly, my phone started bootlooping right away. So far nothing new. As I then tried start recovery, however, TWRP wouldn't start properly (the TWRP logo screen showed for a couple of seconds, though) but instead the phone suddenly began booting normally and this time without any issues. Has this occurred to anybody else?
[HTC One S] el_smurfo:
On 9/24, after a few bootloops I booted into fastboot, selected recovery and got a reboot similar to yours.
[HTC One S] cannondale0815:
Having the same issue. PPTP VPN connections aren't working yet.
[HTC One S] Tendency88:
First of all nice name.. ;p Second, I'm still doubting whether I should flash to CM10.1.3 or not. It's not for my own phone, but if battery life is even worse than CM10.0 then it's a big no go. Will try your method with the wiping, anyone who can confirm this does solve battery drain issues?
[HTC One S] Brushstroke:
Honestly, I wouldn't bother. The battery life was unimpressive and the now infamous lockscreen delay is still present. Oddly enough, I seem to have a lot of success with this CM10.1 build. It doesn't have all of the new features that CM10.1.3 offers, but it's stable and everything works.
[HTC One S] jamus28:
So far no upgrade helps. Using Google play services 3.1.36 I posted a few pages back cures the GPS reboots completely.

I'm hoping to edit the apk version number this weekend so it won't harass me to upgrade. Then I'll be truly happy on this build. I'll upload it if it works.

I would use something between 9/3 and 9/19. I get the best battery I've ever had on this phone currently

Sent from my One S
[HTC One S] annndrewww:
I have had issues with CM 10 causing MMS picture messages to send images super-compressed to the point that they can barely be recognized by the receiver. Does anyone else have this issue and/or have a known fix for it?
[HTC One S] nicknc:
Data drops

I got a brief notification today to "sign in to T-Mobile" in my notification bar. I clicked it, and it launched a browser as if I were connected to a hotel wifi network. Of course, it didn't go anywhere other than google.com.

It's happened several times before following one of those brief data drops, and it's making me wonder if it's an access point issue.

I seem to get fewer data drops with the old epc.tmobile AP versus the fast.tmobile one. Is there a possibility that T-Mobile has changed their APN settings, or perhaps there is an APN authentication issue with CM10.2 (as it seems CM10.1 and CM10 are unaffected)?

Perhaps CM10.2 is flooding TMobile towers with multiple APN registration attempts, or is providing slightly incorrect information.

Is anyone on another provider experiencing these momentary data drops (meaning the H or E symbol drops off with full coverage, and takes about 10-30 seconds to come back up)?

Also, it happens much less frequently when I am streaming, and the data is fixed on-- again making me wonder if it is an authentication problem.
[HTC One S] el_smurfo:
Had half a dozen of those. I think there were some RIL changes a few days ago that eliminated some errors but caused this login message.
[HTC One S] jmginer:
Please, can you send me the link to download?

Thanks!!!
[HTC One S] abracadabra11:
I'll give it a shot

Thanks.
[HTC One S] el_smurfo:
FYI, dirty flashed 9/27 and it updated, optimized and booted without bootloops. Running fine now for a bit.
[HTC One S] cannondale0815:
I had a couple of boot loops again after dirty flashing 9/27 at the beginning of the app optimization process.
[HTC One S] Babaki:
yes this is one of my pet peeves with this rom. apparently its jelly bean "feature". this doesnt happen on sense roms though.
[HTC One S] crnkoj:
guys i got a question regarding the "new" 2.16 firmware and its setup of sdcard and data.

To my knowledge the fact that /data has practically all the space to be used by a user is quite standard in newer phones (i know the galaxy s4 has it like, as well as many other flagship phones nowadays, nexus 4 etc) as well as in AOSP based roms for other devices, which is actually better as it can use data for all the apps and it can use MTP for the data transfer to a pc, which makes it work faster and with more features as it can use ext4 and not the dated fat32 filesystem.

My question now, why not just migrate cm10.2 for ville to the use of ext4 for sdcard as well as use of mtp for connecting? This can be done even on the latest official 2.15 firmware, just by changing a few things in cms fstab and the support for ext4 sdcard (which is supported by cm since cm10.1 on several other devices). That way it could both support the old as well as the new partition layout. Hope im not overstepping any boundaries here.
[HTC One S] nespresso33:
I thinks stock kernel CM10 doesn't support MTP storage.
[HTC One S] nicknc:
I have bootloops after manual power off with 09/27. Also had the first boot not recognize any mobile networks and the APN list was blank.

A power off (which triggered the boot loops) and successful boot after that fixed the mobile data issue.

Immediately got a data stall then drop. Glad to see nothing has been fixed, lol.

Also getting complete lockups during the data drops. Sometimes I really wish this phone had an easily-removed battery...
[HTC One S] esbenm:
By dirty flashing do you mean just flashing the new zip in recovery,no wipes of any kind before or after?

Do all apps keep working?
[HTC One S] nicknc:
That's my experience.
[HTC One S] :
Layman's question: could this put an end to those bootloops?

---------- Post added at 01:07 PM ---------- Previous post was at 01:06 PM ----------

I've never really experienced any problems with apps after dirty flashing.
[HTC One S] mannequin:
well, only one way to test that ;)
[HTC One S] yzoni:
You forgot the camera zoom not working properly after taking a picture zoomed in.

Whatsapp sync works fine for me with the screen turned off. Baseband version 0.16.31501S.17_2_10.23.31501S.10L. And build of 15 august. I do know this issue from the stock rom.
[HTC One S] phoenixita:
I found a bug when you charge your phone the green led appears when you reach 90% and this should appear when you reach 100%...Correct me if i'm wrong! Not a BIG bug and the rom is perfectly usable without this fix :P
[HTC One S] thiasB:
No bug. It has always been this way.
[HTC One S] Phuturist:
I tested this and it works fine for me. You where the only one to report this and therefor I did not include it.

Perhaps the syncing issue is related to the baseband, I upgrade to radio 2.21 right around the time the problems started.
[HTC One S] eckbauer:
Thats not a bug its always been that way with CyanogenMod ROMS.:)

---------- Post added at 03:54 PM ---------- Previous post was at 03:47 PM ----------

Iam on Baseband version 0.16.31501S.17_2_10.23.31501S.10L and i have no sync problems.So it looks like a Radio problem for sum users.I hope iam wrong.:fingers-crossed:
[HTC One S] djsubtronic:
I have the same baseband but I still get this sync issue. It doesn't happen all the time though, only sometimes.
[HTC One S] eckbauer:
Then its safe to say its not the Radio.:D
[HTC One S] Bohemus:
I have the camera zoom issue as well.
[HTC One S] Phuturist:
Ok, I have added it to the previously posted list of reported bugs. :good:
[HTC One S] everywell:
+1
[HTC One S] blinksilver:
I'm not sure how this all played out, so I'm going to have to be sparse on the details, but a while back on ( what i believe was) the aospx ics rom for the desire hd ported over to the glacier, I noticed that the camera supported raw image output. Any way that can be turned on here (perhaps a build props edit)?
[HTC One S] Zaffobaffo:
gps

i think that video recorder is the priority but gps is also important i hope in a update
[HTC One S] DigitalMonk:
I was one of the people having the data drops when GPS was turned on and with the 8/15 build (I skipped the 8/11 build) I seem to be having far fewer issues with it. I think I've seen it drop once or twice in the almost week I've been running this build.
[HTC One S] kuroneko007:
GPS is working fine
[HTC One S] JmPTaz09:
Not here... everything is running really smooth, but navigation crashes for me... did a full wipe clean install, tried clearing map data, etc. ,but still wonky. Nothing else really broken that I can tell, haven't tries recording since I understand that's not fixed yet. Overall, running amazingly well for a beta!

Sent from my HTC One S
[HTC One S] Biohazard0289:
I was getting the GPS crash, I decided to tap OK instead of wait. Then it started running in the background, for whatever reason now if works great upon opening and closing.
[HTC One S] DigitalMonk:
To clarify, I don't experience the data drops near as frequently but I am having problems with Google Nav. Waze works fine, Co-Pilot works fine, geo-caching apps that access GPS work fine (CacheSense) but I get frequent FCs just with Google Nav. Already tried clearing data, uninstalling and reinstalling, etc.

Sent from my HTC One S
[HTC One S] JmPTaz09:
Same here. GPS works great, fast and accurate lock. It's just Google Navigation that crashes. It doesn't crash data, I don't lose data at all, it just crashes "maps", of which navigation is a part.

It will track me for a bit and then crash.

Sent from my HTC One S
[HTC One S] GerBBAR14_c:
BetterBatteryStats asks root permissions multiple times after unplugging. 3 times minum, usually even after 15 minutes when I wake the phone again.

Anyone else?
[HTC One S] baby281:
I have this same issue.
[HTC One S] :
Yeah, and the answer is: Nope.
[HTC One S] ncosgray:
How I get out of bootloops:

1. Power off

2. Boot to recovery

3. Wipe caches

4. Power off

5. Boot normally

Works every time. But it's still really annoying. :)

Anyone know if it's possible to dirty flash to an *older* CM nightly? I will give it a try myself later when I have time.
[HTC One S] mo976:
I found with the past few nightly builds if I don't wipe caches after flashing it boots up fine, otherwise I have to boot back into recovery wipe caches again and then it boots.
[HTC One S] nicknc:
I wipe caches with every update, and still have bootloops

--Update---

Reverted to 09/13 and then updated to 09/28. Wiped caches like always, did not have bootloop on initial boot (went straight to optimizing apps)

Testing for manual reboot bootloops now.

...maybe I'll eat some fruit loops while watching for these boot loops.

--Update 2 --

Yep, manually rebooting phone still produces bootloops (took me three reboots to reproduce, but it's there-- more intermittent than before, but there.)

Didn't even have time for fruit loops.
[HTC One S] driz:
so, im having a problem. Here is what i just did

1) Installed RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2

2) Moonshine S-off

3) SuperCID

4) Firmware update for AOSP 3.4 Kernels (http://xdaforums.com/showthread.php?t=2322755)

5) Installed latest TWRP

6) Flashed CM Nightly and Gapps

7) loaded fine, but said my sim wasn't there; reseated sim, no change

8) updated radio to latest 1.20.50.05.16_10.31.50.08 (http://xdaforums.com/showthread.php?t=2450807)

9) bootloop

10) re-ran firmware update (reduced radio to 1.13.50.05.31)

11) bootloop (cant even get into twrp now; tried reinstalling)

anyone have any thoughts?
[HTC One S] mannequin:
latest builds are complete mess, try something like 09/04 build.
[HTC One S] nicknc:
Can you get to fastboot okay?

If so two things to try:

Flash a different recovery

Flash a sense-based ROM and work from there to get back to the ROM you want (at least you will have a working phone)

Keep trying-- it will shake loose.
[HTC One S] mo976:
Because you obviously read my post before quoting it...
[HTC One S] MaximVT:
I'm using 9/13 experimental without bootloops and without unlock delay.
[HTC One S] djsubtronic:
Where is that?

Also, does anyone still have the 5th Sept nightly zip? Or a link for it?
[HTC One S] nicknc:
Yep, I did misread your post. Sorry about that.
[HTC One S] mo976:
NP cheers!
[HTC One S] zaak00:
Goo.im is your friend :)

http://goo.im/devs/cm/ville/nightly/cm-10.2-20130905-NIGHTLY-ville.zip

I've been running that build since it was released without a single reboot, crash or hang. And plan to stick with this until something significant is included in a newer build.
[HTC One S] djsubtronic:
Thanks. Yeah, I went back to 10th Sept thinking it was stable but yesterday I had a bootloop after opening Maps when I really needed it. After that the battery depleted all day at a ridiculous rate. The one I used before that was 5th, I guess that one's the sweet spot.
[HTC One S] djsubtronic:
FFS, even the 5th Sept nightly has crash/bootloop when trying to use navigation.

So what is the current guaranteed workaround for it? I know there's a few options but could someone please point me in the direction of the most effective one...?
[HTC One S] MaximVT:
Sorry, 09/03:

http://get.cm/?device=ville

cm-10.2-20130903-EXPERIMENTAL-ville-NODELAY.zip

http://get.cm/get/jenkins/40389/cm-10.2-20130903-EXPERIMENTAL-ville-NODELAY.zip
[HTC One S] driz:
i can get into fastboot and after slamming twrp back into it multiple times i can get recovery. sadly im still bootlooping on CM. I'm going to try your suggestion and flash a sense based rom. thanks for your help :)
[HTC One S] nicknc:
I'd almost recommend switching to cwm just to rule out some goofy twrp bug or residual setting causing you problems.

Did you try CM10 stable, by the way? It's a big step back, but 100% of the bugs should be out of it by now.

I was in a very similar boat, but eventually got everything working. Certainly was aggravating.
[HTC One S] nicknc:
Dude-- took me about 90 seconds on goo.im to drill this down:

http://goo.im/devs/cm/ville/nightly

---edit--

Never mind, you found it. I guess it took you less time than me! lol. :)
[HTC One S] djsubtronic:
Yeah, someone posted the link already. I didnt know goo.im hosted ROMs so I never thought to look there.
[HTC One S] nicknc:
Coming off of a CM10.1/10.2 unsupported phone for the past 18 months (HTC Sensation), goo.im and dev host have been some of my most frequently visited sites for kangs.

It's really nice to not have to rely on either for this phone, believe me...
[HTC One S] jamus28:
http://www.androidfilehost.com/?fid=22946563261203992

3.1.36

Youll have the notification asking you to upgrade, but I have not had a single bootloop with this running for the past 2 weeks. Sometimes the system will autoupgrade you on manual reboots, so just check the "google settings" version number if you have problems.
[HTC One S] djsubtronic:
I tried that one. The notifications were too annoying, and Hangouts failed to work (which I need to use) but most importantly, it didn't even fix the crashes.

I ended up retrying the disable service options with the latest Google Play Services, and I disabled almost everything that had the word Location or NLP in it. Tried to reproduce the crash which happened 100% of the time before disabling, and it seemed to work fine. The ones I disabled were:

LocateService

FusedLocationService

NlpLocationReceiverService

GoogleLocationService
[HTC One S] nicknc:
Alternatively, you could use Waze in the interim. Google Maps is supposedly merging with Waze (Google bought it out a few weeks ago), and it has very similar features. You lose the ability to quickly do a map search, but this can be easily accomplished by searching via a browser, then opening the address link with Waze instead of GMaps.

Workaround, not a fix, but that has worked better for me than gambling with GMaps.

I've had absolutely no reboots with Waze, and navigation locks the GPS better than GMaps from what I've seen.
[HTC One S] djsubtronic:
I have tried Waze before, and this is a completely personal opinion, but I just didn't like it. I don't use Maps all that often so it's not a big deal but I much prefer it to Waze when I do use it. Thanks though.
[HTC One S] driz:
I've rolled through 3 diff versions of twrp and the 03 version of cm. Ill give cm stable a shot and if that fails, im going to ruu the latest tmob and go from there...

thanks for all the help all, at this point im thinking my issue isn't related to CM so i'm going to stop posting the issues in here!
[HTC One S] nicknc:
Please don't. Outside of hardware failure on your phone, it's very possible that there is a minor hardware revision that affects some phones but not others. Keep us up to date on how you resolved it so the next person with the same issue can quickly work to resolution.

IIRC, it wasn't until CM9 caused non-booting issues on the MyTouch4g that folks realized the phone had two different screens from two different manufacturers. Of all things, that was what caused some folks to be 100% unable to boot CM until the proper driver was found for the misbehaving screen. The only way to tell was to compare two phones side by side (one screen is vastly superior in color depth), or run a dmesg and look at the vendor string.
[HTC One S] driz:
Will do; im digging through, but apparently in recovery mode i lack the logcat executable. I've now tried CWM and have the same issue with bootloops. I feel like it has something to do with the firmware, but without a logcat i cant say with any certainty.

Oddly enough sometimes I cant get into recovery either, i have to let it bootloop and hold vol down and get in after it fails the first time. I loaded the latest RUU and it booted into android, but when i slid the locker up it would hang at "setting up storage" until it bootlooped. This suggests to me that theres a problem with my storage.. I just have no clue where to start.

I've reverted to my HTC MyTouch 4g for now.
[HTC One S] nicknc:
Sorry to quote your original post, but just reviewing what you've done-- I can tell you I never updated my firmware using the thread above (instead I flashed the 3.14.531.11 RUU, which did it for me), got it from here:

I never updated the radio (I guess this came in via the RUU).

I installed the RUU, moonshined-off, super-CID, and then installed TWRP

2.5.0.0

. After that, it was simply flashing away like normal.

Could you try those steps, just to see if it works? Don't mess around with firmware or radios at this point. Just use that RUU, from that website, then do your moonshine s-off, supercid, and recovery install.

My phone was similarly goofed up (primarily from trying to facepalm s-off via the super one-click utility, which never really did it for me), and that's what fixed it. It actually got to the point where all I could hit was the bootloader-- not even recovery worked. Took me awhile to get the RUU to work too, but it did.

I honestly wonder if something has thrashed your partitioning.

--edit--

I see you did install what appears to be the same RUU. Either way, try the source above, just to rule out some stupid corruption that might have goofed you up.
[HTC One S] driz:
I just re-did the RUU and it will load android and then says something about preparing phone storage and bootloops
[HTC One S] nicknc:
Yeah, that's fine. Go forward with the Moonshine S-Off, etc. you shouldn't need to boot the stock image-- I'm saying to do it more just to reset your baseband, ril, firmware, etc. Just to reset back to zero.

Once you have s-off, supercid, and recovery, go into recovery and format everything (including SD-card). Align your partitions and then give it a go with CM10 or CM10.1 stable, or one of the sense-based ROMs.

You mentioned initially that you could boot CM and just got sim card errors, after which you installed radio and firmware. That tells me that it's more likely that you have a firmware or partition alignment issue. Your phone worked fine initially, right? Before you started anything? Solid-state storage is different than mechanical hard drives-- it doesn't usually allow a little bit of corruption to exist without symptoms-- it usually fails very quickly and emphatically. Nothing you did should have physically damaged your internal storage, and if the phone worked before, then it's highly likely that it was fine. There must have been a bad flash somewhere, and I'm betting it was that firmware update after the baseband update you did.

You are Hboot 2.15, right? I thought there was something in here about 2.16 causing massive storage issues with CM10.1 and 10.2.