yashsingh1/xdaforums huggingface dataset:
[HTC One S] el_smurfo:
Not familiar with KSM and purging of assets....quick explanation?

Lag is not really an issue when you realize the touchscreen is up before the AMOLED. Just swipe to unlock where you think the ring should be.
[HTC One S] nicknc:
settings-->performance-->memory management

Reboot after disabling, of course.

---------- Post added at 10:59 PM ---------- Previous post was at 10:58 PM ----------

Also, try setting governor to interactive, and i/o to noop while you're at it. Those are the other two changes I made. I doubt they make a difference, but it's worth trying.
[HTC One S] el_smurfo:
10 bootloops later and I'm back. I already use Interactive, so I can pretty definitively say this is a problem only Ethan can fix. Affects Evita too, so it will get fixed eventually.
[HTC One S] nicknc:
Lol. Well, it was worth a shot. You're on 10/02, right? No reason it should suddenly work for me. Has to be something I changed.
[HTC One S] el_smurfo:
10/2. Seems to be luck of the draw. So you can select "reboot" from the power menu and it comes right back up?
[HTC One S] nicknc:
Yep, every time so far. Maybe things will be different today ;)
[HTC One S] nicknc:
Got mild bootloops today. Quickly resolved by trying to go into recovery. It didn't make it into recovery, but booted fine after that.
[HTC One S] bluebenno:
Yes, Ejecting and re-inserting the SIM cleared the fault.
[HTC One S] jmginer:
cm-10.2-20131002-NIGHTLY-ville

Error on FN Button settings.
[HTC One S] el_smurfo:
Fixed today
[HTC One S] bunga bunga matze:
Same here....

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

The fixe seems to be for camera related stuff....:rolleyes:

But the crash happens if you choose button in settings..
[HTC One S] djsubtronic:
What are FN buttons?
[HTC One S] el_smurfo:
If you enter the buttons settings menu, settings crashes. This appears to fix that (I know it says camera button, but that is just the button setting that is probably crashing the whole menu)

https://github.com/CyanogenMod/andr...mmit/c4c2a027455fb81ac9049f4b3e980533087c7cb3
[HTC One S] nicknc:
Adding OTG support, but still nothing I can see for the bootloops, unless it's ION related...
[HTC One S] bunga bunga matze:
Can anybody explain me what "OTG" is/does...:rolleyes:
[HTC One S] crnkoj:
On the go. Its basically usb host support.
[HTC One S] justaway2:
What is this "ION" thing I keep seeing in the changelog? I'm guessing it's not the Sony Xperia Ion.
[HTC One S] el_smurfo:
It's some sort of asynchronous networking thing. You'll generally see Koush making commits, as he has been tinkering a lot with streaming stuff like Chromecast support.

https://github.com/koush/ion
[HTC One S] nicknc:
For those who want to know more:

ION

USB OTG

ION is probably more heavily used for now due to the inherent capabilities it brings to Android.

OTG is one of those technologies like Near-Field Communications (NFC) or Mobile High-Definition Link (MHL) that probably the majority of folks don't currently use. That's not to say they're not really neat and incredibly useful-- just that knowledge of them has not saturated the smartphone market.

The only every-day use I could think of for OTG now is connecting an external hard drive or using a usb mouse or keyboard, but both of these uses are already more widely served by mounting your phone to a computer and bluetooth, respectively.
[HTC One S] el_smurfo:
If you check the latest Ville commits, they line up with Koush's ION github, which is not the same as the ION memory manager.

https://github.com/koush/ion

OTG is useful for getting stuff on/off a phone without a computer, as you can use a cable and mount an external flash drive.
[HTC One S] jrior001:
Bingo...or emailing that important file off a thumb drive while playing golf instead of working:)
[HTC One S] nicknc:
:)

I figured you would jump in.

You're right-- I didn't check the commits themselves-- too many IONs in android. I assumed it was the same ION, and didn't realize there was a third out there beyond the memory manager and Nvidia's platform.

And you're right OTG is useful, but I have yet to see anyone in real life use it or express a desire to use it. On here, sure, but not in the smartphone world as a whole. That's not to say it won't take off soon (we have bluetooth stereo headphones and wifi tethering now-- both unreliable, dubiously useful and niche technologies when they were introduced), but for the time being, it would be nice to see major bugs worked out before hammering in new technologies. Particularly when those new technologies could bring additional issues (ie the introduction of the ION memory manager killing camera access on a number of devices).
[HTC One S] jamus28:
The older play services does stop the bootloops on nightlies 9/19 and older, but it was likely auto-upgrading you without you realizing it. If I left my phone on 3g for too long or rebooted, the newer services would be installed (without ever clicking the prompt) and I would bootloop when using maps. I never experienced a crash as long as the upgrade notification was in my tray.

Your solution is a lot better though. I had tried disabling individual services before, but didn't try "locate service". I've disabled those 4 and have not had a bootloop in 2.5 days of extensive maps use. Running 9/19 build (kernel 3.4.60, no reboot bootloops either) Thanks!
[HTC One S] wwelles:
Could be related to play services. Come to think of it, I usually have app updates when I get back in after a crash and boot loop. Anyone else have the same?
[HTC One S] nicknc:
That's fairly normal-- on all my android phones I frequently have updates after a reboot. It's because Google Play polls for app updates on boot.

---------- Post added at 10:38 PM ---------- Previous post was at 10:23 PM ----------

IF you know how to access the flash drive, and IF you have an OTG cable and IF you have a flash drive that is formatted correctly (assuming your phone can handle ntfs or fat-ex). I don't think it's beyond that pale to suggest that most of your general folks out there don't currently use OTG.

But I'll leave it alone-- I was making a point that was getting lost-- that not knowing what ION or OTG are is very understandable. ION (whether it is memory allocation or Koush's tech) is an underlying technology that most folks will experience as a "neat feature" that enables other "neat features" to work better. OTG is a (as yet) niche technology that while pretty cool, is not something encountered by the majority of folks out there.

Bear in mind that 28% of android users still blissfully use 2.3 and think that "jelly bean" is made by Jelly Belly in California. OTG, MHL, ION, and even A2DP are way off their radar.
[HTC One S] waqypaqy:
Phone's decided to stay stuck on a bootloop for about an hour now. Any way to get out of it?

I was on nightly 1st October

I've tried the following:

Wiping cache and dalvik and then rebooting

Installing the latest nightly and then rebooting

Installing an older nightly from the end of September

Flashing boot.img from the .zip via fastboot

Any ideas guys? :( :( :(
[HTC One S] el_smurfo:
Hold power for 20 seconds, then power back up. Lather, rinse, repeat as necessary
[HTC One S] jamus28:
You have no problem getting to recovery, so flash a nightly before the problems started (before 9/20). Also sounds like your S-on, so Flash the boot.img in fastboot first, then go straight to recovery and flash the rom. Make sure you wipe everything before installing.
[HTC One S] xparagonx:
just a heads up i had an interesting problem that i think was caused by the bootloops... last night while i was sleeping the phone started bootlooping until the battery died on nightly 10/1. i wasn't even using it! once i charged it up and finally got android going i decided to flash 9/17 since i didn't have huge problems on that one. i went into twrp, hit backup and it failed multiple times. i've never had any problems with twrp whatsoever, so i flashed earlier versions of twrp and still backups failed. i took a look at all my recovery logs and notice that the failures came after trying to backup the folder data/system/dropbox. this is where all the app and kernel crash logs are stored in android. so i opened my file explorer, navigated to that folder and sure enough everytime i opened that folder it would get stuck loading the files and the whole system root partition became unreadable. dirty flashing another nightly and wiping caches did not fix this so i had to full wipe in order to get it working again. now that folder is accessible and backups work like normal.

sorry for the novel. just wanted to warn anyone if they have similar problems.
[HTC One S] waqypaqy:
I'm on S-Off already but I tried the fastboot flash just be to sure. Will try an even early nightly and see how it goes.

Thanks :)
[HTC One S] bunga bunga matze:
Good news everyone, 2013-10-04 is out, booting fine after flashing and the crash on Button settings seems fixed...:D

Its realy smooth and fast, and I dont find any wake up delay (or its realy realy short)...:good:
[HTC One S] el_smurfo:
Mine booted on first try too. I did make sure to fully power down first though...

Edit: have manually rebooted twice without issues, so I'm pretty happy
[HTC One S] crnkoj:
Gps/maps reboot present?
[HTC One S] Phuturist:
Had no issues with the 20131002 but 20131004 resulted in bootloops again (S-ON and flashed the kernel with Flash Image GUI). The trick selecting recovery in the bootloader also didnt work. Keeps rebooting on app optimization. Been in bootloops for about 10 minutes now ... :rolleyes:

[edit] another time rebooting to bootloader and selecting recovery did the trick
[HTC One S] Dave77459:
Rebooting from recovery initially gave me bootloops with 1004, but powering down and booting went smoothly and she is running great now. :)
[HTC One S] horno46:
Booted first time no power down needed. S off used the open recovery script to install.

Seems to run faster than before too.
[HTC One S] Brushstroke:
Flashed 10/04 nightly, and it's running beautifully. No issues to report here other than a weird data drop issue. The data would drop out intermittently even though the icon would show 3G or H+ speeds. Changed the APN from T-Mobile to T-Mobile LTE and it has stopped. Screen wake lag is gone too!

EDIT: Perhaps I spoke too soon. I just tried to use Google Maps and it crashed and caused a bootloop. Other than this glaring error, it's working fine!
[HTC One S] el_smurfo:
Hmmn...never heard of that APN...how do we enter it?
[HTC One S] :
Same here. Lockscreen delay is as good as gone with the Oct 4 nightly, and I haven't had any data drops so far. Yay!
[HTC One S] :
If there were an option to disable 'vibrate on touch' just on the lockscreen, now, I'd be entirely happy :) The vibration on pattern unlock drives me mad, but I don't want to turn vibration off completely via settings>sound.
[HTC One S] Brushstroke:
It was available by default for me.
[HTC One S] justaway2:
Flashed 10/04 and no boot loop :)
[HTC One S] nicknc:
I had mentioned trying this workaround earlier in the thread-- you can switch APN's by going to settings --> mobile data --> mobile networks --> access point names (I believe that is the path).

T-Mobile (epc.tmobile.com), T-Mobile LTE (fast.tmobile.com) and T-Mobile IPv6 are all provided by default when a T-Mobile SIM is inserted. This is one of the major "selling" points of CM-- one of the largest APN lists.

It is a placebo for the data drop issue, and doesn't have a long-term effect on data drops in my experience on this phone. Switching from epc.tmobile.com to fast.tmobile.com can cause DNS queries to speed up in some markets, giving the perception of faster internet.

---------- Post added at 09:33 PM ---------- Previous post was at 09:28 PM ----------

T-Mobile APN switch to LTE improved the data drop condition for me, but they still persist on T-Mobile LTE. I posted the fix I found that absolutely works a few pages back in this thread. Do a thread search for "build.prop" and add the missing lines to your build.prop using ES File Explorer or another similar root explorer. Make sure to set fast dormancy to "0" or "2". CM is missing this required information, and that seems to make the phone act up in some T-Mobile markets by dropping the data. It's five lines of code that you put in (initially, I posted only four, but found a fifth one that references ro.ril.radio.svn=19, as I still got around 1 drop a day without it), so make sure you add all five lines.

You'll probably notice the data drop occurs more frequently in areas with good 4G coverage, and typically when transitioning from one tower to another. The other time it occurs a lot is immediately after waking your phone-- it will work for about a minute, then drop, exactly as you described.

The only aggravation is having to add those lines after each update, so you may want to paste them into a text file on your SD card for easy copy/paste later on into your build.prop.
[HTC One S] el_smurfo:
Maybe it only appears is areas with LTE...I don't have that APN but might try to add.

Edit... OK, weird...did a "reset to default" and now its there. I had added a test APN forever ago and I guess that kept it from updating. That's the one small problem with dirty flashing CM ROMS for a year and a half without a wipe...every once in a while, some weirdness carries over ;)
[HTC One S] nicknc:
I got a bootloop after powering down and then turning it back on.
[HTC One S] Dam4rusxp:
I can confirm that!
[HTC One S] nicknc:
Got a ton of problems with 10/04.

Freezes, random reboots (without maps usage), bootloops, and lockups.

On 10/05 now. Still with bootloops.
[HTC One S] el_smurfo:
Yeah... I'd say is time to go way back to RC until the Oppo release.
[HTC One S] nicknc:
I wasn't around for that-- was it stable at all? I had bootloops on CM10.1.3 for crying out loud...
[HTC One S] el_smurfo:
Just frustrated....CM was a savior for every phone I've owned, but hasn't been feature complete on this device as long as I've owned it, and now they are busy with more monetizing bloat and supporting goofy devices none of us will ever buy.
[HTC One S] nicknc:
You mean they are imitating Google? :)

Back on CM10.1. Aggravating to have to reinstall everything, but no boot loops. :)
[HTC One S] Dam4rusxp:
Did a clean install of 4/10 and it seems to be pretty stable now. Charged over night without reboot. Let's see what the day brings...
[HTC One S] bunga bunga matze:
Therefore, I am considering to get me a Nexus 5, despite the fact that my One S still be good....:rolleyes:
[HTC One S] tnpapadakos:
hi y'all, i'm still on 6/10/2013 and have no issues

I always used to flash the latest greatest, but when the kernel changed, I resisted and stayed put

i am glad i did

I do miss flashing the latest though, lol
[HTC One S] phoenixita:
i could build a one with 3.4.60 kernel wich means no bootloops but a little lock delay!
[HTC One S] tnpapadakos:
great, thanks! it would be nice to flash something again, and not have to go through all the other steps of "upgrading" my hboot, etc
[HTC One S] phoenixita:
you should be on 2.15 hboot for runnig 3.4 based roms or not? Correct me if i'm wrong! cause the build it's based on 3.4.60.
[HTC One S] tnpapadakos:
if so, i will stay put
[HTC One S] voidzero:
Ho hum.

I have TWRP 2.5.0.0 and I have been running CM 10.1 for a pretty long time with no issues.

Now I want to update my phone to 10.2, just like I did with my Galaxy S2 a while ago. On the Galaxy it was very simple - wipe the phone, install cm and gapps, reboot, done.

With my One S, moving from CM10.1 to CM10.2 was just as easy... I thought. So, I followed the same procedure, installed cm-10.2-20131005-NIGHTLY-ville.zip and guess what? It's not working. Just getting a reboot loop.

Browsing through the shipload of instructions doesn't make it easier. I don't want to do all the flash, ruu, flash again, S-off, etc. I just want CM10.2 but it's not so simple.

I guess I'm just sharing a bit of my sadness with you guys. I can't help but wonder: Why oh why does the installation for CM10.2 have to be so hard with the HTC One S? :eek:

For now I'm restoring my 10.1 TWRP backup. Too bad..

---------- Post added at 02:16 PM ---------- Previous post was at 02:05 PM ----------

Answer: because I'm not reading properly. All I had to do was `fastboot flash boot boot.img` and it seems that we have CM10.2 without any of the S-off stuff. We'll see how far it goes now that CM 10.2 did boot... :cowboy:
[HTC One S] bunga bunga matze:
Hey dude, you have to upgrade your HBoot up to 2.15. (2.16 caused major problems, so stay away from that)!

Otherwise it will not work

- Just relock your bootloader

- install the latest ruu.exe

- unlock bootloader

- flash recovery

- unless s-off flash boot.img via fastboot

- than boot in recovery and flash a cm-10.2 based rom....

The whole procedure tooks me 40min
[HTC One S] machoman1337:
No data drop issues? Those were the only problems I experienced with the older 3.0 kernel. Everything else was perfect. Sure, 3.4 gives more userland RAM, but it's not like 3.0 was suffering from less RAM.

Would be very grateful if someone could make a 3.0 build incorporating the data drop fix :)
[HTC One S] tnpapadakos:
i do have the data drop fix from time to time...if i knew what the fix was, i would add it to the 6/10 rom
[HTC One S] nicknc:
---------- Post added at 01:17 PM ---------- Previous post was at 01:16 PM ----------

[/COLOR]

Fix for the data drop: Add the following lines to your build.prop. If you have any of the lines pre-existing in your build.prop, then either delete them and replace with the following, or adjust them to reflect the proper value.

ro.ril.hsdpa.category = 24

ro.ril.hsupa.category = 6

ro.ril.hsxpa = 4

ro.ril.fast.dormancy.rule = 0

ro.ril.radio.svn=19

Reboot, and that data drop is

gone

.

What it does:

HSDPA/HSUPA/HSXPA settings increase your 3.5G speeds to the max supported by your phone. This is not to say you will get 24mbps down, but the stock values appear to limit network speed for some folks in some markets.

Fast dormancy is a battery saving technology. The stock setting for CM (for some reason) on this phone is "1", which apparently is incompatible with T-Mobile's network

in some, but not all markets

. I checked the other phones (HTC glacier and HTC pyramid) that run CM10.2 in my house, and both of them are set to a stock value of "2". Why it is set by default to "1" on the Ville CM10.2 is a mystery to me. You can change this to "2", but you may still experience a

very

small number of data drops (1/day or less). Changing it to 0 decreased my battery life by about 1%/hour, but completely eradicated data drops. I haven't had any in over a week, except for one day where I updated CM10.2 and forgot to edit the build.prop-- I had a data drop every 10 minutes or so until I remembered I hadn't edited the build.prop.

The last setting (SVN) is necessary, but I have no clue what it does. A lot of folks on AT&T networks refer to it, but none spell out what its function is. I can tell you that with the above edits (and fast dormancy set to 2), I had about 1-2 data drops per day without this setting. Adding it almost completely eliminated the data drops until I changed fast dormancy to 0. If you need it, add it. If you don't, don't feel compelled. It

is

used on both pyramid and glacier CM10.2 build.props that I mentioned before.

So, this value may be necessary for you, or it may not

.

Either way, with the above lines, I have had no data drops for many days now. If I remove those five lines, and set fast dormancy to "1", then my 3.5G speeds drop, and I almost immediately start getting data drops. I can confirm this on both 10.1 and 10.2.

So there you go. The full fix, compiled, so hopefully folks don't have to go and piece together my two previous posts giving the information.
[HTC One S] tnpapadakos:
OK the ro.ril.radio.svn=19 must be it, cause I never saw 19 before...trying it now...thanks!!:)

I hate crapple
[HTC One S] nicknc:
It's referenced in the Ville forums somewhere, and when I saw it on my wife and daughter's phones, I figured it would be worth a shot. Sure enough, it did the trick.

I wish I could figure out what it actually did. Or better yet, what the fix is to get TMobile to hurry up and add 3G/4G to the 2G towers on my commute. 2G speeds are so damn low on T-Mobile, I've gotten to where I'll just disable it altogether sometimes. Everything times out on T-Mobile 2G. Everything.
[HTC One S] machoman1337:
Are you sure that is identical to the proper fix intervigil posted back in mid August? His fix was something related to HTCQualcommRIL. I'm not even a US resident so fast dormancy fixes that work on T-Mobile may not apply to me.
[HTC One S] nicknc:
Found it here: http://xdaforums.com/showpost.php?p=45839084&postcount=908

Forum search is apparently down at the moment, and I couldn't find a Google search to intervigil's fix that you referenced, so I can't comment there.

Do you have a link to the thread you're referring to? I'd be curious to see what he has done.

And yes, the above settings seem to produce great results on TMobile-US, no clue if that's reciprocated elsewhere. You could always take a look inside the zip for a working ROM (CM9 or something) and see what is working there. Did you try the build.prop edit? What carrier are you on?

Also, fast dormancy did not fix it 100% for me-- I also had to make the svn parameter change. No clue why fast dormancy=0 would make such a difference, but not resolve completely.
[HTC One S] xparagonx:
http://xdaforums.com/showthread.php?p=44770903

Intervigils fix is there. Links to both fixes for cm 10.1 and 10.2 but I think it's only for 3.4 kernel.
[HTC One S] nicknc:
Thanks for the link. Interesting logic in the patch there, but I can tell you the data drops are still very much there in 10.2. Haven't tried 10.1 without the build.prop edit yet.

What behavior are you experiencing when your data drops? Mine is usually a stall of data, followed by a quick switching between H to 3G to E to H, and then a complete drop (but no drop of signal). It takes about a minute for it to go down and come back up. Other folks have reported similar behavior. Maybe Ethan's fix is for a different issue.
[HTC One S] crnkoj:
hey guys, for oall those who get this endless boot with endless boot animation, coudl oyu please connect the phone while its in endless boot and do adb logcat and report back if the following line is present and/or dominating:

D/AudioHardwareALSA(11092): qcom.audio.init is set to

if so, please do adb shell than, navigate as su to /data/system and than remove packages.xml there, than write reboot, and see if it boots

thanks

adb shell
su
cd /data/system
rm -rf packages.xml
reboot
[HTC One S] Dave77459:
I wanted to post an experience I had this weekend and this morning. I was at my brother-in-law's house, and hooked to his wifi. Well, my android tablet connected immediately with the proper password. My HOS would sign in and immediately disconnect. I've had this frustrating problem many times in the past: failure to connect/authenticate/work.

I downloaded the app Wifi Analyzer, because I wanted to see if it was in the problem channel. This thread suggested that 6 was fine, and that was what the router was using. Inside Wifi Analyzer, I clicked to connect. It said it needed some companion app (Wifi Connection?) because something was missing, and I OK'd the installation. Shazaam! Immediate connection, and it connected immediately afterwards as well.

At home, my wifi was never faster or stronger.

I mentioned before that here at the office I could connect but that almost always I would get a reported 1mbps speed. Today, I am getting 56mbps.

I am struck that Wifi Analyzer said something was missing (sure wish I'd taken a screen shot!) and now my wifi is so strong and sure. Not sure what Wifi Connection did, but it seems like magick. :good:

Edit:

As it happened, it was working so well that I kicked off Titanium Backup with the sync to dropbox. Of course, it dropped down to 1Mbps again. I wonder if Dropbox is a culprit? :(