yashsingh1/xdaforums huggingface dataset:
[HTC One S] kuroyume_cl:
I have S-Off, so as far as i know i don't need to flash the kernel separately
[HTC One S] :
Oh. Sorry, my bad. I always forget about s-off.
[HTC One S] xparagonx:
I'm having trouble dirty flashing older nightlies. It was never a problem before but now when i try i get a message that says something like "unfortunately process.android.Phone has stopped working." That message pops up so much that i can't do anything except restore a backup.
[HTC One S] maluus:
From the battery life perspective 10/29 looks promising. Had bootloops and settings app crashed after I change the theme of the keyboard app. I ll report my other findings.
[HTC One S] nicknc:
Looks like the folks over on MagioROM (Sense 5) have been getting reboots and bootloops as well. Unless I'm missing something, I'd say "the plot thickens"....

That's obviously different base and kernel than what we have here.
[HTC One S] mikronac.ns:
no problems with 30/10... it is awesome... no bootloops and gps problems... 70% battery left, 90 mins display on...
[HTC One S] yooouuri:
Huh, is there a 30/10 available?

http://10.2.cmxlog.com/?device=ville
[HTC One S] nicknc:
Yeah, clearly it's the CM without bootloops and amazing battery life that we've been waiting for. I heard 32/10 is even better performance.

Good luck finding it, lol.
[HTC One S] mikronac.ns:
Second 10/29 :)
[HTC One S] yooouuri:
So [MENTION=4612496]mikronac.ns[/MENTION] and [MENTION=2207213]nicknc[/MENTION] confirm the last nightly is very good? Can somebody else confirm it?
[HTC One S] nicknc:
No, I was being facetious...

I'll give it a whirl, though, as one of the guys that has always had tons of bootloops with CM10.2.
[HTC One S] Albino_Mexican:
The 2nd 10/29 has been troublesome for me. Took several reboots to get it going after install. Reboots in general are hit or miss. Sometimes completely freezes while loading the lock screen after booting up. Same results whether dirty flash or clean.

Edit: Boot/freezing problems resolved by flashing boot.img in fastboot. Strange that I would have to do that though as my phone is s-off.
[HTC One S] djsubtronic:
Deciding to give the 2nd 29th Oct a go. No bootloops around flashing, no crashes in the first 30 minutes. No crash when running maps and multitasking (even after re-enabling all Google Play services). Screen on delay is virtually instant. So far so good. Will report back after a while on longer term usage.
[HTC One S] mikronac.ns:
It is awesome... Clean flash...
[HTC One S] djsubtronic:
Just noticed Viper4Android doesn't work on 29/10... can someone confirm?
[HTC One S] nicknc:
No bootloops so far, and I have tried, including rebooting with power plugged in, rebooting rapidly in succession, etc.

The phone does either turn off or completely hang at random intervals-- requiring holding the power button to get it to shutdown. Random shutdowns are honestly worse than bootloops, so my 2 cents is to avoid this nightly.

This is after a 100% complete wipe and full flash.

I tried the latest Bubba kernel, and this DID cause bootloops.

------------------

Scratch that-- no sooner did I post this, but now it's bootlooping.
[HTC One S] Navik57:
On 10/29 - 2. No bootloops so far, but had it crash within a few minutes of flashing. =-/

EDIT: Constantly locking up or restarting. Completely unusable for me. Going to try to reflash boot.img (I am s-off), and if that doesn't work, going to revert back to an early August build. If i can get into recovery without a bootloop. =-/

Update 2: For some reason, recovery cannot see boot.img to flash it... I re-flashed the rom, wiped cache, etc... now it is going to the optimizing apps, and taking about 1 minute an app. After it has done a few, it restarts itself... I'm not liking this...
[HTC One S] mikronac.ns:
I was just disabled animations and rebooted phone. I got bootloop. Wipe cache and dalvik and power off it. Booted just fine. Then I rebooted it 5 times and there wasnt any bootloop...
[HTC One S] nicknc:
I got this too. Only resolution was to do a full restore from an earlier backup (10/01 in my case)
[HTC One S] el_smurfo:
huh...i get two android.process.gapps FC at first boot, then it runs fine. are you running a theme or something? maybe some sort of contacts integration that's now broken?
[HTC One S] nicknc:
I was thinking it was more of a radio problem, as I also had no signal. It was caused by attempting to clean install 10/29 v.2 and then restoring data from a 10/01 full backup I had. No custom themes or anything out of the ordinary. It was constant, and certainly did not resolve after rebooting. I tried flashing gapps again and wiping caches. Neither helped at all.

The 10/01 data restored fine into both PA and Beanstalk earlier today (at least as far as the FC went-- I had other problems of course), so I don't know what to make of it.

I'll try and update the 10/01 rom to 10/29 v.1 later this evening to see if it happens again.
[HTC One S] el_smurfo:
I get that no radio sometimes... A reboot or two fixes
[HTC One S] dave il barbaro:
I'm on 26/10 nightly, so far so good... No bootloops and no reboot, only the data connection switches between 3g/H/H+ every minute

Sent with HTC ONE S
[HTC One S] el_smurfo:
Try adding this to build prop and rebooting (fast dormancy is already there to edit)

ro.ril.hsdpa.category = 24

ro.ril.hsupa.category = 6

ro.ril.hsxpa = 4

ro.ril.radio.svn=19

ro.ril.fast.dormancy.rule = 0 (or 2)
[HTC One S] nicknc:
Thanks for jumping on that. I still get data jumps, fyi-- no data drops though.
[HTC One S] The Setlaz:
Hey,

I'm running CM10.1.3 and I'm facing GPS issue after a little while. (can work for hours or just few minutes... it seems pretty random !)

Any apps using GPS (I have 3 different) hung and the phone almost freezes and eventually causes the phone to reboot with bootloop.

To stop the bootloop, I just need to go to Bootloader and Reboot from Bootloader, and it boots normally as if nothing happened...

If I start the GPS app again, it will work for a few minutes, and hung again and bootloop all over again...

Anyone faced/heard this problem before ?

Thanks !
[HTC One S] djsubtronic:
Been using 29th Oct 2 since yesterday, and so far so good. I can vouch the battery life is as good, if not better, than the 9th Sept nightly which was already awesome.

I've only noticed one glitch, sometimes upon reboot the baseband will be unknown. Another reboot usually fixes it but it happens quite a bit.
[HTC One S] nicknc:
Lol! We've been dealing with this for nearly two months now. It's something in the 3.4 kernel, or in CM or both that's causing this in CM10.2 (a lot) and CM10.1 (some)

Read back in the thread some. There may be a solution that mitigates the bootloops some for you.

Multitasking with GPS use and/or manual reboots seem to be triggers, particularly when a USB cable is hooked up to the phone.
[HTC One S] The Setlaz:
Hey,

Alright ! I noticed there was a few messages regarding GPS issues in CM10.2 but not really in CM10.1.

Anyway, for what it's worth, I only have the issue when driving with USB cable hooked-up and screen-on.

I'm using ViewRanger app for hiking with GPS enable to record the hiking trail, it's usually for about 4-5 hours (mostly screen-off but I turn it on a few time during the hike and multi-task) and never ran into this issue.

So there's something indeed with either USB cable or screen-on or both or whatever !

Anyway, thanks for the piece of info !!
[HTC One S] KShatzkes:
]I've almost had it with this CM10.1-10.2 on this phone. It just does not work well. I might as well have a ****ty phone.

Is it possible to go back to 10.0 easily? Or do I have to go through some sort of method to downgrade the kernel back to 3.0?
[HTC One S] machoman1337:
Just back up your data and clean-install a ROM of your choice. No need to "downgrade the kernel".
[HTC One S] KShatzkes:
That's what I figured. Just wanted to make sure I didn't brick my phone. Thanks!
[HTC One S] nicknc:
It certainly sounds like you're checking all the boxes for bootloop trouble, lol. You may want to consider just going ahead and doing a full wipe and moving up to CM10.2.

My phone is one of the ones that has been heavily affected by bootloops in CM10.2. However, with the 1st 10/29 build installed with the latest bubba kernel, I have had no bootloops, and just one random shutdown, despite rebooting with usb plugged in, GPS usage while multitasking, and doing numerous manual reboots.

If you do decide to move up, I'd heavily recommend doing a backup of your data partition, doing a full wipe with reinstall, and then restoring your data. This seems to have worked well for me.

---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------

I had a lot of issues with trying to restore data backed up under 10.2 into 10.1.3 when I similarly was fed up with 10.2. I could never get 10.1.3 to work without constant freezes, data drops, FC's, and TONS of bootloops after restoring. I reckon there was some stupid 10.2 setting being imported somewhere that caused problems on 10.1.

Just be aware-- you may have a similar experience trying to import 10.1.3 data into 10.0. Maybe not. Just make sure you do a full backup so at least you can go back until you figure out a better way to downgrade.
[HTC One S] machoman1337:
When I downgraded from 10.2 to 10.1 on my N4, I only backed up and restored apps, not system settings. That gave me no problems. Restoring settings between different releases of Android tends to cause problems.
[HTC One S] djsubtronic:
The recent builds don't seem to let the LED torch stay on when the screen goes off. Used to be fine in older builds, the LED would stay on until turned off regardless of screen. Is there some new setting somewhere that will let me use the flashlight while the screen is off?
[HTC One S] wwelles:
I found exactly the same issue
[HTC One S] nicknc:
How did you pull that off? Titanium? I've always just restored data partition, and it's worked (until now, lol)
[HTC One S] djsubtronic:
I found that TeslaLED app from Play Store seems to work when the screen goes off. Guess that's a workaround for now.
[HTC One S] machoman1337:
Yeah, I use Titanium. Paid for the Pro version so I can restore all apps in one move instead of clicking "ok" for each individual app (huge annoyance with the free version).
[HTC One S] nicknc:
Okay, I've gone 24 hours now on the 1st 10/29 with bubba's kernel. I had one shutdown last night, but that's been it. No bootloops

at all

, despite:

Rebooting multiple times (even in quick sequence)

Rebooting with usb plugged in

Multi-tasking with GPS running in the background

Clearing dalvik/cache

This is a first for me. I did a clean install and imported data from a 10/01 backup I had. Perhaps bootloops only happen on even-numbered days, but for my phone (which rivals el_smurfo's for bootloop city), this has been terrific.

For what it's worth, I have usb debugging disabled, cpu set to interactive, and no overclock/undervolts. As mentioned before, I did get a lot of issues with the 2nd 10/29 nightly, especially once I flashed bubba kernel.

Any feedback from any other bootloop-prone folks regarding 10/29 1st version?
[HTC One S] el_smurfo:
I haven't had any bootloops with the second 10/29. Probably rebooted a half dozen times. Every other reboot has unknown radio though, which is nearly as annoying.

Having fun with all the kit kat apps (got them on android police and phandroid). For once, a recent cm addition is paying off as voice plus actually integrates with the new hangouts SMS function.
[HTC One S] Humanio:
Glad to hear it. 10/28 was a huge disaster for me. Freezes, random shutdowns, random bootloops, data randomly disabled. No idea why. Hoping the 10/31 Nightly is a bit more solid before decided to go back to Viper until hopefully a KitKat Rom is in the wild.
[HTC One S] Darknites:
Ya that was pretty much the reason I got pro too.
[HTC One S] nickmv:
You didn't have any issues installing?

I'm on CM 10.2 10/11 nightly, and managed to get the combo of Google Services, Search, and Experience Launcher installed.

However all attempts to get Clock, Maps, Street View, and any other of the remaining apps has completely failed. I open the apk's from Root Explorer, and it brings up the installer screen, but I can't ever click the Install button. Only the cancel button is clickable. Someone recommended uninstalling all updates (ie. clearing data from the app mgmt screen), but this makes no difference.

Anyone else getting this issue?
[HTC One S] el_smurfo:
I got all to attempt to install using root explorer but the keyboard and clock failed due to matching signatures Maps and street view did work though.
[HTC One S] crnkoj:
I'm confused, why not simply install maps and keyboard from market? I'm running my own compiled cm builds and all of those things work. I've been using a version from the sources from the 8th Oct, and I never had a reboot while using maps navigation. I've upgraded to a new build made from yesterday's sources today and it still works without reboots. I didn't even wipe data today as I upgraded.
[HTC One S] nickmv:
Haha, so you're gonna get a kick out of this. I tried this morning and it works fine. I'm pretty sure the problem was none other than my THUMB. It was like 4am and I couldn't sleep, so I was laying in bed trying to install some of those apps, and I bet each time I tried to press Install, I pressed with a part of my thumb that wasn't registering. But when pressing Cancel, I was using the other side of my thumb.

Damn fingers!
[HTC One S] el_smurfo:
We are talking about apps pulled from the Kit Kat factory images. All are newer versions than those in AOSP or on the market right now. Some, like Hangouts have nice new features like SMS integration.

---------- Post added at 09:10 AM ---------- Previous post was at 09:08 AM ----------

For me, it's usually the base of my thumb hitting the bottom right of the screen when reaching across to the other side. Odd, but this phone is just a little too small for my hand...that N5 will fit just right once back in stock and my wallet is not empty.

I did get the keyboard to install this morning with a little finessing, but with the Holo Glass theme, the keys are a really ugly blue color, so either I'm ditching the theme or sticking with the AOSP keyboard.
[HTC One S] asdfasdfvful:
Off topic and not exactly related, but I'm wondering if anyone has unlocked their sim card when on this rom. Both my phone company and other stores have given me the same unlock code bit it didn't work, so I'm trying to figure out what's wrong

Sent from my One S
[HTC One S] el_smurfo:
Ugh... was afraid this would happen...

http://www.cyanogenmod.org/blog/cyanogenmod-10-2-m1-release
[HTC One S] nickmv:
Am I missing something? Says nothing about whether or not Ville will be supported (which it likely will, considering it's less than 1.5 yrs old).
[HTC One S] bunga bunga matze:
Dont flash the version from 2013-10-31, it has only 1.40kb!:rolleyes:
[HTC One S] Darknites:
Just try it on a Sense rom, might have better luck.
[HTC One S] b_ignatov:
I see that there is a stable release 10.1.3 in cynogenmon.com.Can someone tell me something about it??Any bugs or big battery drain??I'm looking for stable version.....no matter wich version of android is.
[HTC One S] thiasB:
Its 173MB. try downloading it... ;)
[HTC One S] horno46:
Strange I am running 31/10, and the download size was 172mb!
[HTC One S] :
What about it?
[HTC One S] The Setlaz:
I've been running it since RC1 (updated to RC2 and stable), aside from the GPS that reboot when USB cable is puggled, haven't had any issue at all with it ! (no freeze / reboot / shutdown / bootloop...) I'm really happy with it !

I just updated to ParanoidAndroid 3.99RC2 yesterday, but too many bugs for me.

Reverting back to CM10.1.3 today.
[HTC One S] b_ignatov:
Thank you for your quick report.
[HTC One S] machoman1337:
Well, the builds for the ville aren't exactly stable, yet they're being declared as such (automated code freeze), which will mislead a lot of people.
[HTC One S] horno46:
Looks like those a CM agree, no M1 build for ville!
[HTC One S] bunga bunga matze:
Luckily I have ordered the Nexus 5 on the first of november, I'm tired off the unstable one S-Firmware and the bad radios...:rolleyes:

Hope Nexus has better firmware....
[HTC One S] machoman1337:
Nexus is pretty much guaranteed to have the least problems with AOSP roms.
[HTC One S] ThomasHunter:
Yeah, it's a shame that the ville can't seem to get stable, I wonder if it will ever have another snapshot-release.

Personally, for now I'm satisfied with the nightlies, I hope they'll continue for another year or so and that we can enjoy a near-stable KitKat!

I pledged to carry on with this phone for two years, I think I'll buy a Nexus as well after that. Else maybe a Motorola with their firmware, I really like their subtle additions to the stock experience from lately.
[HTC One S] nicknc:
Yes, and it is also guaranteed to have problems, just like all the other Nexus phones. Flip through their threads sometime-- whether it is N4, Galaxy Nexus, Nexus One, whatever. Tons of issues AOSP, CM or whatever.

---------- Post added at 06:38 AM ---------- Previous post was at 06:36 AM ----------

CM 10.1.3 is okay, but battery isn't the best. There is no kernel I could find that can be used on it (bubba's just causes eternal booting). Big lock screen delays. Some bootloops (although rare). Performance seems to be a little worse than CM10.2 (something I also noticed on the HTC Pyramid).

It's okay, but far from perfect.
[HTC One S] Darknites:
For lock screen delay on 10.1 you could give my kernel a try that I posted in the bb thread.
[HTC One S] |RaVeR|:
I'm itching to get the N5, but my One S is now only (yesterday, to be exact) 12 months old. I'd like to try to get at least a little bit more out of it. Especially since it's always had a screen protector and a silicone jacket applied to it. It really looks brand new.

If the problems keep up, I'd like to remind everyone how good life was with cm10.0! Worst case, we could always downgrade to that.

As stated before, we might have lost a DMCA'd binary since then, but who cares? It worked and it could do everything cm10.2 can. Except making you furious when it gets a bootlooping episode that you didn't notice for half an hour and that absolutely ate your battery at the worst time possible and left you with a corrupted /data partition, meaning you have to revert to a backup you took weeks ago :)

Does everybody agree that the only -REAL- problem with cm10.2 on ville is the spontaneous rebooting and the fact that these reboots cause loops?

If I take a step back, I must admit this is not such a bad ROM at all. It simply has a kernel bug that's massively annoying and that, proportionally to its annoyingness, does not get enough attention from developers.

I've looked into the code myself, but I just don't have the time to learn all there is to learn just to fix one bug.

I wonder if it would be possible to draw more attention to it?

Surely I'm not the only one who would prefer to pay money to see this fixed instead of having to buy a new phone?

Maybe If a couple of people chipped in, we could jointly offer some sort of reward to the person that submits the patch that (demonstrably) fixes this?
[HTC One S] pyrocide:
RUU my device,

Moonshined on .17 F/W

Advance wiped the entire device

Flashed TWRP 2.6.3

Installed 10/3.

Results: Bootloops and random reboots. Cant even get past the first CM setup screen.

Too much work to get bootloops and reboots consistently on what is almost like a brand new device. Moved to beanstalk and not a single problem so far. I loved CM on my SG2 and Pre 10.2 on my Ville. Cant justify supporting the CM dev team for this device any longer until it gets fixed.
[HTC One S] Darknites:
Odd that BS works fine yet CM don't. It don't make much sense since they using the same device trees and I wouldn't of thought CM rom would be this bad.
[HTC One S] pyrocide:
That exactly what I thought. Beanstalk being CM based i was just giving it a go to see if its all CM based ROMs or just CM.

All I know is that I have a working phone again.
[HTC One S] intervigil:
FWIW: I've known about the reboot thing and been looking at it since around April of this year. If it was that easy to fix I would have fixed it already. As it currently stands, my suspicion is something in the firmware is causing strange stuff to happen with the CPU up/down code.
[HTC One S] mo976:
Supposedly 4.4 solves many of the qcom bugs errr "features" but who knows what that means for phones like ours...
[HTC One S] machoman1337:
https://github.com/CyanogenMod/andr...mmit/f8fed45b504cb8c716c8684a1018217e7ac74e9d

Looks like someone's fixed the problem of one of the cores going offline after a spontaneous reboot?
[HTC One S] el_smurfo:
Yeah... I think Ethan has been rummaging around in CAF for the last week, trying to fix the reboot/bootloop issue.
[HTC One S] |RaVeR|:
Great! If the phone only rebooted occasionally, that would be a thousand times better than bootlooping!

Intervigil, I'm sorry if my previous post offended you. I did not mean to imply this bug would be easy to fix.

Since it is also a problem with cpu1 that causes the loop, does that mean the first reboot as well as the loop are caused by one and the same problem? The bug does seem to occur most often when multitasking (like reading your e-mail while navigation is running in the background, or taking a phone call while navigating)

---------- Post added at 04:24 PM ---------- Previous post was at 04:07 PM ----------

I just installed 11/04 and tried to trigger the reboot (and loop) by opening a couple of cpu-hungry apps simultaneously and then switching between them. The phone rebooted within 30 seconds, and rebooted into a frozen desktop. Don't get your hopes up ;)
[HTC One S] el_smurfo:
I think he's already mentioned the GPS issue is I2C related, while the bootlooping issue is likely a result of the second core not coming online. Running 11/4 without issues, but don't have patience to try to force a bootloop right now, so can't tell you if it's fixed or just careful power down after flashing.
[HTC One S] Humanio:
I too can verify that Beanstalk for whatever reason fixed any issues I had while just on CM alone. No bootloops, multitasking is fine, chrome doesnt cause lock ups, gps, etc..

Its a bit late since I managed to snag a Nexus 5 set to arrive this week, but since I'm handing this down to my sister I wanted to make sure she had a stable phone running AOSP.
[HTC One S] wwelles:
I get the impression everyone else bought a nexus 5 as well?
[HTC One S] thiasB:
How comes that cm-10.1.3-ville with its 3.4.11 kernel along with the 08/12 gapps is superstable? I did a clean install from scratch yesterday and tried hard to trigger reboots by playing Ingress, using Google Maps Navigation and switching between these apps. Normally I would have seen about 5 reboots in this time but I never had any issues with the new installation and will stick with it as long as cm10.2 does not reach the same stability.

Is the 3.4.XX kernel really responsible for the issues in cm10.2?

EDIT: had one spontaneous reboot now while having the Ingress app open. It then bootlooped. Nonetheless it seem to occur less often than under cm10.2 nighlies.
[HTC One S] bobjbain:
I didn't use to suffer bootloops with CM10.2 but I thought I'd Beanstalk a try, and within days I had spontaneous reboots and bootloops.

Then my WiFi started refusing to connect to anything and I couldn't reboot the phone without going through the pain of bootlooping. So I reverted back to CM10.2 and I haven't had any spontaneous reboots since.

Also, with BeanStalk, playing Candy Crush ate my battery like nothing and the phone would get really, really hot....

CM10.2, on my phone, seems to be really stable for some reason. I am on the 30th Oct nightly ATM
[HTC One S] :
The latest 10.2 nightlies are running the 3.4.11 kernel, too. There has been a revert a couple of weeks ago.