yashsingh1/xdaforums huggingface dataset:
[HTC One S] crakarjax:
One thing I noticed about the Illusion ROM is excellent battery life... I think I was at 86% at the end of the day yesterday.
[HTC One S] usaff22:
Is that with the 3.4 kernel?
[HTC One S] Stainless7221:
I flashed my backup of 2013-06-10 Unofficial with kernel 3.0 -> best battery life

Battery life with the newest nightly was horrible Oô
[HTC One S] asdfasdfvful:
Illusion with 3.4 kernel has the same battery life as the newer cyanogenmod. It might be the 3.0.8 kernel
[HTC One S] apg5031:
Can you please share the link for me to download the file...
[HTC One S] Stainless7221:
http://www.thenow1.com/ones/cm-10.1-20130610-UNOFFICIAL-ville.zip
[HTC One S] don.peugot:
Are you sure about that? Source?

I myself am getting a significantly better battery life on Illusion than on CM10.1. On Cm I regularly lost more than 5% per hour without using it. Illusion has a great battery life in comparison to that, although I prefer CM from the functionality point of view.
[HTC One S] crakarjax:
Yes, Illusion has kernel 3.4.10-ge1dcd3f dated July 15th. I can't compare to the newer CM10.1 builds since they won't boot for me, but it's much better than the 3.0 kernel CM10.1 builds.
[HTC One S] asdfasdfvful:
Well, for me, both illusion 2.1 and cm with the new kernel were perfectly fine. I am always connected to wi-fi and it still lasts me through a day. Illusion was actually perfect for me since it had everything I needed and nothing more; the only issue was the halo f/c

Edit: maybe it is just my phone, but I lose about 2% on cm without using it
[HTC One S] :
This question might have been asked a million times before, but still: Say I had a phone running CM 10.0, and I'd like to update it to a 10.1 nightly. Would I have to flash the 10.1-gapps package, too, or would all Google apps get updated just like that by flashing a 4.2.2 rom?
[HTC One S] el_smurfo:
I'd flash it. There are often other things in the packages not available in the store
[HTC One S] asdfasdfvful:
I suggest you flash the gapps for 10.1. It takes a few seconds

Edit: sorry, didn't see the previous post from my phone
[HTC One S] :
So, basically overwriting the old Gapps won't cause any issues? Ah, then again, why am I even asking this? I'm probably gonna end up wiping all data before upgrading anyway.
[HTC One S] djsubtronic:
You don't have to wipe data. Just wipe system, flash the ROM (and kernel via fastboot if not S-OFF), then flash the 4.2.2 GApps.
[HTC One S] asdfasdfvful:
Overwriting hasn't caused issues for me. And additionally, even if I don't wipe data, I have to reflash gapps anyways cause it disappears.
[HTC One S] |RaVeR|:
Intervigil, by placing printk's in the kernel code between these routines, I tracked down the 'code pause' in the the wakeup routine. Unfortunately, although it is occurring while waking up the display, this is quite normal since the display wakeup takes so much time and msleeps() a lot.

The delay is always on one of these msleeps. Which makes sense, since while msleeping in one routing the kernel will start to handle other things.

Therefore, I'm doubtful this is even display-related at all.

Actually at this point I'm speculating the problem lies with I2C, as both the light sensor and the touch panel are using it and are both being waked while coming out of sleep. VERY often, the light sensor waking up is the very first thing that happens after the delay.

As I'm a complete noob when it comes to android (development), I welcome any pointers you might be able to give to help track this bug down!
[HTC One S] el_smurfo:
I think a lot of folks suspected it wasnt really related to the panel since most audio stalls out when waking also.
[HTC One S] asdfasdfvful:
Just wondering, with the 0802 build, I can turn the phone on with a simple press of the power button, not a hold. Is that normal?
[HTC One S] madstitz:
Did anyone here get full disk encryption to work on CM10.1?

Mine just shows the "encryption-android" screen but doesn't start encrypting, at least not for the following two hours :P.

I can even leave the app and reboot without any change or harm.
[HTC One S] yooouuri:
Offtopic:

Does somebody have the best ROM (nightly) with the 3.0 kernel. (because i love CM but hate the lockscreen delay and connection issue)
[HTC One S] NQNH:
.... One page back dude....
[HTC One S] yooouuri:
I tried the nightly, but got still the connection issue..

Radio: 1.08ts.50.02.16_10.08e.50.04L

Should i upgrade my radio to 1.15?

Can i install the radio from here: http://xdaforums.com/showthread.php?t=2255906&highlight=radio

I am S-ON!

EDIT:

Installed the 1.15 radio, hopefully the issue is gone
[HTC One S] Stainless7221:
look a few pages back, i posted a link there, battery life is excellent. 2013-06-10 i think
[HTC One S] machoman1337:
Both 3.0 and 3.4 AOSP builds have the data drop issue.
[HTC One S] asdfasdfvful:
Is there any particularly good cm nightly that is more stable than others? Sorry, I'm about 10 days behind now and feel I should update
[HTC One S] xparagonx:
I think it depends on the phone and other unknown factors. Some have data drops on 3.4 kernel (including me) while others do not. I know some users reported data problems with 3.0 kernel but I never experienced any of them. I even use an older cm 10.1 build with 3.0x kernel now after upgrading firmware and it still performs well without dropping data.
[HTC One S] yooouuri:
When i used 3.0 kernel back in the days never had problems with data issue. And now after 10 hours. No drop.. (Flashed tot 1.15 radio)
[HTC One S] machoman1337:
Yeah it's quite weird. In my experience, 3.0 builds (last used 5/23) gave me more frequent data drops than any 3.4 build I tried. With 3.0 it was almost daily for me (and occurring multiple times a day), whereas with 3.4 it can go several days, maybe even a week, without dropping.

I'm in Boston now on TMo and will report back on my experience there later (what I described was on Telus Canada).
[HTC One S] Babaki:
between connection drops, new kernels, 10.2 and bricked phones...etc. i feel like i have no idea what's going on anymore.
[HTC One S] :
Same here. I've gone back to Stock...
[HTC One S] el_smurfo:
Yeah, I've never been so tempted. I'm afraid our maintainers may have bitten off more they can chew with so many devices to support and so much code in flux. I'm hanging on with the 7/30 build, hoping each morning the thing won't be a brick, but it seems most of the problems may be 10.2 related, with a few random failures on 10.1 just to make things confusing.
[HTC One S] |RaVeR|:
Yeah me too. That's why I started looking at the code to try to figure out the delay lock. It just bugs me so enormously I'd almost RUU the phone.

Haven't given up yet....

I've heard there are very few people who have had a brick after 3.4, but do you actually think it's possible for a phone that's been running 3.4 for weeks to suddenly brick out of nowhere?

Just asking, honestly, I'm probably not tracking this forum as much as you do.
[HTC One S] sGollSv:
Download the experimantal Mr 2 ...
[HTC One S] fzurita:
I was running CM10.1 with the 3.4 kernel for weeks before mine bricked all of the sudden.
[HTC One S] nethavoc:
I did have some issues with 10.1 back in July with the kernel change but now running August nightly with no issue except for WiFi not staying on.
[HTC One S] shakurass:
I have been having this issue for a very long time with many different ROMs (CM10, CM10.1, TrickDroid 9, Viper 1.2.1) and no one seems to know what's causing it. Going to work (802.1x EAP) the WiFi works every time however when I walk home (WPA/WPA2 PSK) my phone will not connect until I turn WiFi off then on again. The only time I didn't need to do this is when I first bought the phone but even going back to stock Bell RUU didn't seem to fix the issue.
[HTC One S] kalapyu:
Funny. Was about to ask the same question. I gave my one s to my wife but she is annoyed by the data con issue. I would like to switch her to the most stable version with regards to data and random reboot. Would you guys know which is the best?

Thanks

K
[HTC One S] ponchofiesta:
I have the same problem but only with Cyanogenmod. Stock based ROMs did work for me.

But I use a workaround. I installed Llama. It brings location based profiles and I configured it to enable WiFi in some locations (home, work) and disable WiFi everywhere else. So when I come home WiFi is enabled automatically and works without problems.
[HTC One S] aegentirony:
Im afraid im also going back to stock...Yesterday out of the blue i thought it was going to brick...Constant reboots and the i got into bootloader and tryed to boot to recovery and it wouldnt..Just boot looped. Then all of the sudden it rebooted again into the rom! im now going to run the latest Ruu...and stick with stock i cant afford to lose my only phone :highfive:
[HTC One S] el_smurfo:
I wish RUU worked for me. Might just flash McKinney's stock-ish ROM and hope for the best if to many more brick without doing anything
[HTC One S] aegentirony:
Why wont Ruu work for you ?
[HTC One S] el_smurfo:
IDK, just errors out every time, no matter what computer . The firmware update process is the only reason I can run 3.4 kernels.
[HTC One S] jcbwng:
I used the stable CM10 for a long time, but are finding the newest Miui V5 better.

I need my phone to be a rock steady daily driver and MIUI v5 is not letting me down (as ALL other custom One S ROMs do).

The OTAs are even working delivering updates every saturday.

MOD EDIT: Link Removed - Be mindful for which versions you're posting s3<->s4
[HTC One S] asdfasdfvful:
The most stable one I've seen with android 4.2.2 is pac. It also comes packed with features. Only issue is that it's battery life is not the greatest (for me at least)
[HTC One S] Stainless7221:
I am using TrickDroid since today, till now everything is ok. Sense 5 ist pretty neat. Its not as smooth as kernel 3.4 and not as buggy as 3.0, i will see about the battery life in the next days :)
[HTC One S] carlos_abril_94:
I've tried miui, sense 4 and 5, cm10, cm10.1 with various 3.0 kernels and cm10.1 3.4, and the most satisfying experience with this phone for me comes with a nightly from May (the 11th, but that doesnt really matter) with the latest twisted kernel. Its stable, no bugs, fast and smooth. I recomend trying this kernel if you don't stand 3.4 bugs.

Enviado desde mi One S usando Tapatalk 4
[HTC One S] djsubtronic:
I've been on 25/07 since it came out and had only a couple of data drops, zero random reboots, and no funny stuff at all.
[HTC One S] DeerSteak:
I found that with mine if I put it in fastboot before launching the RUU, it'll go through, but if I just run it, it never wants to update. Errors out. Have you tried starting in fastboot and then trying again?
[HTC One S] el_smurfo:
Yup. That's how I did it. sounds like a lot of folks are on the hunt for the brick problem, so I'll hold out for a bit
[HTC One S] NQNH:
Official 10.2 nightlys are building right now! The first cm10.2 nightlys are already in get.cm (for other devices)

http://jenkins.cyanogenmod.com/job/android/?
[HTC One S] usaff22:
Same happens to me occasionally. Not to mention I partially corrupted my phone the other day by doing a factory reset in bootloader by accident. With all these reported bricks I might return to stable Sense 5.
[HTC One S] bunga bunga matze:
Yes Sir, nice to read....:D
[HTC One S] Kevin336:
Is it building for the ville or do you mean the other devices??

Gesendet von meinem One S mit Tapatalk 2
[HTC One S] ernestnwanu:
Seems like Ville gets skipped?
[HTC One S] yooouuri:
All the ville stuff on github got a 10.2 branche, so likely to me i think we get CM10.2
[HTC One S] RockR172:
HTC MSM8960 Family is currently under testing since the brick bug is not fully fixed..

Once that's fixed, nightlies will be started as soon as possible.
[HTC One S] yooouuri:
First DCMA takedown, now the bricks..

Will it ever stop :crying:
[HTC One S] djsubtronic:
Nope.
[HTC One S] evil89:
I'm back to stock for the next future.. Hoping in HTC or in getting a Nexus 4..

I'm very sad. This is the only phone that gave me problems..
[HTC One S] asdfasdfvful:
I know this has been asked before but I don't think there was an answer. If we are on an aosp rom and it is fine for a few days, is it possible that it will randomly reboot in the future?
[HTC One S] yooouuri:
After a few days, no random reboots had. I was using navigation app and playing music trough Google Play Music, and my phone just randomly rebooted...
[HTC One S] djsubtronic:
Isn't that a possibility with any OS on any machine?
[HTC One S] asdfasdfvful:
I can understand that. But I mean to the point where it cannot be fixed with a restart. I'm still s-on so if I can't fix things by restoring a backup I'll be a bit worried

---------- Post added at 10:51 AM ---------- Previous post was at 10:51 AM ----------

Sorry. Maybe I wasn't clear. I'm not talking about a simple one time reboot. I'm asking if it is possible to go into a constant boot loop of some sort
[HTC One S] yooouuri:
Had once the phone constant was boot looping, had to clear cache and dalvik. Then the phone worked again!
[HTC One S] djsubtronic:
Well like I said last night, I been on the 25th July nightly and didn't have a single reboot. Although ironically, I had one this morning, my first one. It was one of those random reboots which caused a bootloop at the lock screen, but all I had to do was hold the power button and it booted up normally. This is the only random reboot I know of that CM10.1 is suffering, but as I said, I had my first one today since the 25th...which is like 3 weeks ago. And I use my phone heavily. These reboots, as far as I know, don't cause bricks or unrecoverable bootloops either.
[HTC One S] asdfasdfvful:
Okay... Well I guess everything is still fine then
[HTC One S] crakarjax:
I see now what all the fuss is about wrt the data dropping. The illusion ROM didn't have that problem for me, with the 3,4 kernel fwiw.
[HTC One S] kalapyu:
I am still experiencing data dropping and this is very anoying.

I have been away for a few days but i understand that :

- 10.2 could potentially never come out due to a technical/legal issue

- the latest 10.1 nightlies could end up in a briked phone

- the other 10.1 nightlies are unstable (data drops and reboots)

--> I am wondering wether i should go back to CM10.1 Experimental Snapshot or even CM10 wich as far as i remember, was very stable...
[HTC One S] ernestnwanu:
Seems like some interesting kernel stuff has been added, FITRIM disabled as well. Official 10.2 incoming? http://changelog.bbqdroid.org/#/ville/next
[HTC One S] el_smurfo:
None of those things are true.
[HTC One S] kalapyu:
I am happy to be wrong then :) but I am still experiencing data drops (this is true ;) )

I will wait for 10.2 then!

THANKS!!!!!

K
[HTC One S] djsubtronic:
No need to wait.

http://xdaforums.com/showthread.php?t=2407127

Running like a charm.
[HTC One S] el_smurfo:
The only thing you did identify correctly was the data issue, but the rest of you're statements were old or backwards
[HTC One S] :
That made me wonder if the developer team has any plans of releasing a new m-snapshot any time soon; respectively, what issues there are waiting to be sorted out before this is going to happen?
[HTC One S] el_smurfo:
It's my understanding that 10.1.3 is in the works. I imagine it is 10.1 with a lot of the fun new features in nightlies such as focal and voice+.
[HTC One S] crakarjax:
Errrrmmm...

"""

Bugs:

Lockscreen Delay

Random Data Drops

Some other minor issues

"""
[HTC One S] el_smurfo:
That's the charm we all know and love for the last couple months ;)
[HTC One S] nethavoc:
10.2 is running pretty damn nice for me. Very smooth damn nice battery use. Fantastic work.
[HTC One S] asdfasdfvful:
Just wondering, what are the big differences/added features? And by what you mentioned, is the battery life better?
[HTC One S] nethavoc:
Yes my battery life is better and I have no lag between any screens. I am also just using built in launcher. Very smooth.
[HTC One S] asdfasdfvful:
Might i ask what your %/hr was with 10.1 and then 10.2?

Sent from my One S
[HTC One S] dredmentia:
Mass chaos after installing CM 10.1 Nightly

Hi guys, I have been using the HTC One S since the week it came out, w/ Tmobile here in the states. First thing I did was root it, ran a few different roms, and stuck with CM since around December of 2012. Had been running CM fine for months, but noticed on this thread that the newer nightlies required the firmware update. So I RUUed to the latest Tmobile update, then re rooted, and installed CM 10.1 nightly, August 13 build. This is where the trouble started. Since I connected to wifi first, I thought everything was fine. It installed perfectly, was very responsive, no boot loops, much better battery life, all my apps updated properly. Then the next day I left to go to work, and I saw that my phone was on Edge network. I thought it was just a fluke or the area I was in, so I rebooted the phone. Still Edge network, with it sometimes switching into HSPA. I did what a few people suggested and played around with the mobile data settings in the settings, switched Airplane mode on/off, still stuck on Edge, or worse, no data in some areas. Phone calls and text still come in fine, but the data is either EXTREMELY slow (12 hours to download a 150 mb file) , or would just cut out for no reason. So I thought, no big deal, ill just wipe and reinstall the CM build that was working fine for me. Now even with that build, I can't get onto my 4g network, or anything above this super slow data that connects/disconnects randomly. I wiped again and even went back to the cm 10.0 STABLE rom, same problem. So it appears installing this nightly has caused some major chaos on my phone. Has anyone else experienced this problem, I know people are having problems specifically with the recent nightlies, but what I'm asking is, are they having those SAME problems when they revert back to the rom they were using before, which was working just fine before I put this nightly on.

I guess right now my options are to revert back to stock again. The only problem though is that, I updated to the latest Tmobile firmware, which was released on June 24th. I had trouble going backwards with another HTC phone for a friend (HTC Rezound for Verizon), so I don't even know if its possible to run that RUU again. I will try and let everyone know my results. But if that doesn't work, does anyone have any advice for me on how to get my phone back to stock settings, so I can my high speed data back? Besides that I have to say that this rom worked perfectly, and the battery life was much better with the 3.4.0 kernell. But what good is a mobile phone if I can only use it on wifi...
[HTC One S] el_smurfo:
Wow... Wall of text. I think if you search around, you'll find that "stuck on 2g" issues after ruu require HTC repair service. Try sense ROM and if issues persist, you'll need a repair.
[HTC One S] dredmentia:
Just letting everyone know I was able to go back to Stock thank god. I don't get a 4g signal in my house, I only use wifi , but when I go to work tommorow, I will let everyone know if running the latest RUU helped restored my 4g service.
[HTC One S] dredmentia:
I understand that, I was just bringing up the point that I didn't have this issue until I installed the CM 10.1 Aug 13 Nightly. When I put my post on here , I try to put in as many details as I can, so people don't have to ask if I tried this, or if I tried that, or when did this start happening, or when did that start happening. Regardless if I don't have 4G service tommorow, ill be bringing it to the T Mobile store. I already returned to stock and locked the bootloader, and I was never s-off, so there shouldn't be any issues.
[HTC One S] yooouuri:
There is a patch for the data drop issue!!

http://review.cyanogenmod.org/#/c/48342/
[HTC One S] dredmentia:
Is this specific for the HTC One S or CM 10.1 in general
[HTC One S] yooouuri:
For CM10.1 and CM10.2
[HTC One S] :
But for "HTCQualcommRIL". Seems to be for HTC phones.

And it's by Intervigil...
[HTC One S] $droyd$:
Its a ROM patch not a device patch.. It'll work for any device that uses htcqualcom
[HTC One S] nethavoc:
Well I am not a heavy user but I do a lot with phone. With 10.1 being on from 6 am I would be at 10% by 10 pm. 10.2 I had it on from 6 am and at 10 pm with same uses I was at 35 % 20 + is good for me.
[HTC One S] Tendency88:
Is it just me or has this thread become slightly irrelevant ever since CM10.2 started building for HTC One S and it got it's own thread: http://xdaforums.com/showthread.php?p=44707718
[HTC One S] Kalashnikitty:
You know the difference between official and unofficial?
[HTC One S] Tendency88:
Oh shoot, my bad! Didn't read well enough I guess, apologies.

But since HTC One S has been added to the official CM10.2 nightly build process, will there be a CM10.2 official thread as well anytime soon?

https://github.com/CyanogenMod/hudson/pull/118
[HTC One S] Kalashnikitty:
I'll rename this thread!
[HTC One S] alexeius:
Hi there. I was using cm10.1 some time ago, but then i flashed cm10 (412). It was smoother and worked better. But who wins now? 10 or 10.1?
[HTC One S] el_smurfo:
10.2
[HTC One S] alexeius:
Ok, I'll try 10.2. There was some firmware updates for 3.4 kernel, i must install them?
[HTC One S] Michael1101:
Haha. Was about saying the same. You was faster :)
[HTC One S] yuan_1202:
Is it just me or the autofocus doesn't work. i find it fail to focus on anything close up, i.e. macro focus.

i tried to scan some 2d code and the app just cannot recognise anything and the image looks very blur.
[HTC One S] el_smurfo:
Back up, let it focus, then move slowly back.
[HTC One S] yuan_1202:
u kidding me right?
[HTC One S] asdfasdfvful:
When you are too close, it won't focus well so backing up to the point where it focuses and slowly inching closer can actually help some times

Sent from my One S
[HTC One S] yuan_1202:
it appears anything less than about 40cm away from the lense cannot focus properly.

this "problem" is not present in the sense based roms.
[HTC One S] el_smurfo:
Yeah, well that's the trade off you get for not having to use Sense
[HTC One S] yuan_1202:
yeah i know.
[HTC One S] |RaVeR|:
just a small rip-rep on this:

I've been looking at this for most of today and haven't really made much progress. I'm quite frustrated now but nevertheless, I'll note here what little I've found so far:

If you turn off the gyro and the light sensor (which is also the proximity sensor), the wake delay time is almost halved (I got it sub-second)

I've been doing this by simply commenting out the platform_register() routines for those devices. Phone works great, only the sensors don't work of course.

I'm not sure whether or not this confirms my theory that something related to I2C is at fault.

Unfortunately, the delay time could also just be lower because there is less work to be done when the device wakes up.

Still, I can't shake the feeling I need to keep looking at I2C-connected devices.

The problem I'm facing is: how do you fix something when you don't know how it works and don't have a working example to compare?

The kernel code is just way too complicated for a relative n00b like me to fully understand, let alone _FIX_!

I'd like to RUU my device now so that I can witness the original HTC code in action and compare it with how CM behaves, but I don't have the time for that today (in fact, I'll probably not have time again this week). Also, last I checked, an RUU doesn't work on my phone.

Does anyone know if it would be possible to run CM with a stock HTC kernel? That would be awesome for comparing performance.

PS. Intervigil, if you're reading this, I'd really welcome any insights you might have on this
[HTC One S] slar:
You should take a look at a 3.0 based kernel. Those versions didn't have any delay
[HTC One S] mikronac.ns:
10.2 nightlies starting tonight...

What about bricks which experienced some people when flashing 10.2? Is it fixed?
[HTC One S] highKo:
should be fixed, the trim function is disabled now. it was probably the reason for the bricks