yashsingh1/xdaforums huggingface dataset:
[HTC One S] asdfasdfvful:
Radio is still 1.11.50.05.28, just like in the about phone
[HTC One S] khan.orak:
Just wondering, does this build of CM 10.1 have the masterkey exploit fix? What about stock and other ROMs?
[HTC One S] NQNH:
Afaik it has
[HTC One S] mo976:
Yes the more recent (past few weeks) builds have both patches. Unless they are recent CM based ROM's like PAC or PA probably not.
[HTC One S] Xdpker06:
Okay, maybe I'm just dumb, but I can't for the life of me figure out how to change the camera's standard resolution of 2448 x 3264 to HTC's more widescreen resolution of 1840 x 3264.
[HTC One S] bunga bunga matze:
.....:eek:
[HTC One S] Xdpker06:
I'm sorry, I meant the camera resolution, when I take pictures.
[HTC One S] Stainless7221:
I think he means the camera resolution..

In the standard camera app, i can't find it either at the moment.
[HTC One S] bunga bunga matze:
Oops, my fault...

It seems, that if you choose 8M than you get the resolution you want (see picture below)
[HTC One S] Xdpker06:
That looks like the sense camera isn't it? Im on CM 10
[HTC One S] NQNH:
as far as i know its not possible with the current aosp camera, in shooting mode, its fullscreen/widescreen, but it will be saved at 4:3 ratio.

on sense its cutted into 16:9, which you see on the different resolution.

if i remember correctly the new camera (focal) on cm 10.2 will support saving pix in widescreen.

really looking forward to get the first 4.3 nightlies :o
[HTC One S] striped121:
Focal works fine with 4.2

https://docs.google.com/file/d/0B8wUrrr9CQIpVkhHbXVqZ29tZ0U/preview?pli=1
[HTC One S] wwelles:
Thanks, installed 20130803 yesterday. Only problem I see is the lock screen delay. No freeze/reboots yet like I had previously.
[HTC One S] ponchofiesta:
On my last test it didn't. Some functions were disabled and it crashed several times when tring to use some features.
[HTC One S] striped121:
its all fine from what I can see but maybe its just me I ent that photo savvy :cyclops: 16.9 only seems available in 2mp mode though.
[HTC One S] Dave77459:
From your original post,

"how to change the camera's standard resolution of 2448 x 3264 to HTC's more widescreen resolution of 1840 x 3264"

What you are really asking is for a "less tall" resolution than a wider resolution. You can see that the wideness doesn't change, but the height does. All widescreen does is crop your photo for you. It discards image data from the top and bottom, making you think it is widescreen. This is the same thing that happens for square photos.

The discussions I saw way back when is that since widescreen is phony, you can always create a widescreen image (or square) in an image editor. Thus, why spend time creating something fake like a "widescreen" mode? That was the thinking at least when I last saw the issue emerge.

I use the Snap camera, and its editor allows you to fix the width:height ratio to 1:1 (square) or 16:9 (widescreen) when cropping. I'd be surprised if other in-camera touch up tools don't let you do this.

---------- Post added at 03:23 PM ---------- Previous post was at 03:15 PM ----------

I ended up doing a factory reset, and ultimately, wiping /system as well. Now it is rock solid again, under all signal strengths (although I am using Tasker to set to 2G at home).

In build.prop, ro.ril.fast.dormancy.rule=1

In local.prop, ro.ril.fast.dormancy.rule=2

I never set fast dormancy in build.prop after reinstalling 10.1, and likewise I didn't change or delete local.prop. Which setting takes precedence? I will assume local.prop, but is that right?
[HTC One S] el_smurfo:
Build prop takes precedence. The ro is read only.
[HTC One S] Krayvon:
q

what the hell is going on with Google Chrome? Everytime you scroll it refreshes the page it's doing it on this phone is doing it on my tablet and my Nexus
[HTC One S] Michael1101:
I also got this for a while. But only on one or two specific pages.
[HTC One S] surrealjam:
Yeah, I don't believe this is at all ROM-related as I have had this same issue on Viper S 2.2.0.
[HTC One S] mortek:
Hey all,

I just flashed the latest nightly on my HOS after having it stuck on boot loop while stock and unrooted.

Apart from the lockscreen lag bug, which is a pain, the ROM's performance is extremely low. Everything is lagging so much that it is unusable.

Is there something that I am missing? Is someone else having the same issue?

Edit:

I tried wiping the cache in TWRP and rebooting but it is now stuck in bootloop again!
[HTC One S] Kalashnikitty:
No, my performance is great except the little unlock delay (its not a pain).

Wipe again, flash the rom and flash the boot.img via fastboot if youre not s-off
[HTC One S] mortek:
Thanks for your reply.

Wiped, flashed ROM, wiped cache, flashed boot.img via fastboot, it rebooted 10 times before managing to get past the CM logo and once it finally booted the performance seems to be as laggy as before.

Do you think It could get better after a second boot?
[HTC One S] el_smurfo:
Can you take a look in settings/phone and make sure your kernel version matches the date of the ROM version?
[HTC One S] mortek:
The kernel is "3.4.11-g1c9ce1e build03@cyanogenmod #1 Sun Aug 4 13:21:06 PDT 2013" and the ROM's date is "Sun Aug 4 13:07:30 PDT 2013"
[HTC One S] ncosgray:
The screen-on delay would not bother me as much if the plug/unplug behavior had not changed recently. Before a couple builds ago, plugging in or unplugging from a power source would not cause the phone screen to turn on. Now, it does, and coupled with the screen-on lag, it is driving me a little bit crazy. I unplug the phone and hit the power button right away to start using it, but meanwhile it has already started turning on the screen (which takes 2-3 sec). The result is that the screen comes on and then turns off again immediately. I'm gradually learning not to hit that power button, but annoying nonetheless.

Does anyone know if there's setting or build.prop edit that controls whether the screen is activated on plug/unplug events? I always preferred that behavior anyway.
[HTC One S] djsubtronic:
+1
[HTC One S] Stainless7221:
I am also still wondering that the screen-on bug is such a huge deal to fix.

I am still on a kernel 4.0.8 rom, because i use my phone as watch and the delay drives me nuts ^^
[HTC One S] el_smurfo:
All we have to go on the matter was what Intervigil stated:

He also doesn't have any data disconnect issues and I guess spends more time on the One which has GE released code, so those two problems might be around for a long time.
[HTC One S] machoman1337:
He's currently occupied with the Samsung S4 now :/ I won't complain, just that we really have to be patient for the time being.
[HTC One S] el_smurfo:
Check his post history to see the dramarama on the i9500 thread. You'd think we were a vacation if you didn't assume he tried to stay away from the xda nuthouse entirely for his own sanity.
[HTC One S] KShatzkes:
I was wondering when was the data connection issues first observed? I've only encountered the problem in CM10.1, and don't remember having the problem in CM10. Is this correct? Or was there a CM10.1 version that didn't have any data connectivity issues?
[HTC One S] el_smurfo:
Seems to be tied to the 3.4 kernel. Older builds don't have the issue
[HTC One S] KShatzkes:
I don't believe that is completely true. I am running the 20130604 CM10.1 (mainly because I don't want to have to upgrade my kernel to 3.4) and was having lots of data connection issues.

Basically, whenever I would lose my data connection, unless I toggled Airplane Mode or rebooted the phone, the data connection would not reconnect. Granted, up until 10 minutes ago I was using a very old radio (TMUS 0.16), so that may have been the issue. I just upgraded to the EU 1.15 radio, and haven't seen any data drops or problems reconnecting yet, so maybe the problem is fixed. FIngers crossed!

Also, was wondering what the last build of CM10.1 with the 3.0 kernel is. Is it the 20130604 nightly, or a later one?
[HTC One S] el_smurfo:
Old man memory tells me it's 5/21, bit I don't care, so check for yourself
[HTC One S] Krayvon:
!

need some guidance, for some reason, on the latest nighly, i am only getting Edge. i have toggled 2g/3g numerous times, wiped, cleaned, reinstalled, and still getting E only.

any idea what could be causing this and/or how to solve it and get my 3g back.

i have tested my sim on my nexus 4 and it works just fine and i get 3g on it. so i'm assuming its the phone/rom/radio?

thanks.
[HTC One S] el_smurfo:
Haven't seen that one, but adding the following to build.prop helps me

http://xdaforums.com/showthread.php?p=43950040
[HTC One S] Krayvon:
k now its getting weird, i even flashed a sense rom and i'm still getting E only.. what is going on?? :(
[HTC One S] $droyd$:
Lol its the htc conspiracy ..
[HTC One S] Krayvon:
!

this is what i get for wanting to give it away instead of selling it. i should have dumped it on CL last week for 200 bucks... sigh.

Droyd, you're the brain in Ville Land, got any idea what is wrong with it? i can't even boot up nightlies anymroe, i think its the phone itself and not so much software :/
[HTC One S] xkonni:
flash boot and if coming from sense/cm9 wipe data. (of course you can backup/restore user-installed (as in no system-apps) app-data with titanium/whatever)
[HTC One S] Phantom Pt. II:
Yeah that's what I did. Maybe I'll try it some other day later again. :)
[HTC One S] GerBBAR14_c:
It took 2 minutes once, 20 minutes the other time. Don't be too fast.
[HTC One S] alphar:
10 hours isn't bad battery life considering it lasts most of your day.
[HTC One S] eminembdg:
Seriously. That's bad? Lol. That's good for me. Aweso actually. I'm a heavy user with lots of screen on time
[HTC One S] Navik57:
Because I can't seem to find it anywhere... can anyone point me to Superwipe for the Ville?

Also, anyone have any idea why the startup animation fails to repeat Part1? From what I can tell, everything is correct in the Desc file, and it seems to go to all white as soon as it is done going through the part 1 files.

Other than that, just getting started with CM10, looking forward to messing around with it =-)
[HTC One S] el_smurfo:
Any word on when HOS might hit the official nightly list?

https://plus.google.com/117962666888533781522/posts/3gjXR6AoSa2
[HTC One S] Navik57:
Make sure the charger or USB isn't plugged in. Don't know if that's what it was, but I seemed to be stuck at that point too, then I unplugged and rebooted. (this is after waiting 10 mins, twice).
[HTC One S] Bxrxyxaxn:
How do we get flash working on the browser?
[HTC One S] el_smurfo:
Flash is no longer being supported for new products. If it was included with your device, you can update it, but not install it.
[HTC One S] Bxrxyxaxn:
I read there was a work around for flash player just forgot where i read it.
[HTC One S] itsmikeramsay:
Flash Player anyone? You'll need this....(hope it still works)!: MoDaCo Flash Installer
[HTC One S] el_smurfo:
Gotta love Paul O'Brian. Seems to be working, though it turns out I already had install_flash_player.apk backed up on my phone...I think for sideloading on the wife's Kindle Fire...
[HTC One S] mikereidis:
Thanks !

RADIO_IRIS_TRANSPORT is built as a module in every kernel I've looked at. And I don't see the ko file in system/lib/modules.

Perhaps there is some reason it needs to be a module ?
[HTC One S] c_brown93:
Google Nav crashes still for me.
[HTC One S] GerBBAR14_c:
Some battery stats. Auto brightness.
[HTC One S] OccupyDemonoid:
My battery life seems a lot better now. This is with about two hours of straight Google Play Music streaming off of HSPA+. The screen was also on full brightness. I used Google Navigation for a bit today and couldn't get it to crash. It ran smooth and fast. :)

If you cannot see the attached thumbnail, after 7hours and 21 or so minutes on battery, I have 71% battery left. :)
[HTC One S] mrcrassic:
The battery life on this ROM is stellar and significantly better than the last build. For what it's worth, it's a daily driver for me. Thanks for such a great release!!!

discharged for 20 hours, battery life at 29%, about 1.3% drain per hour. Awesome! (I would get about 8 hours of battery life under similar conditions with the last build.)
[HTC One S] klutch:
ok guys i seen the problem with the gallery that some of us wont show the pics later 2day i was browsing the phone and i when to my gallery and it happen the same thing i only saw one pic that it was todays picture the only one i got shocked why all my pictures was gone so what i did was i opend ROOT EXPLORED when to /mnt/sdcard/DCIM/.thumbnails once i have there there is a file the only file with the star (i cant remember now since i deleted it) but i deleted that then i went to the gallery and saw all the pictures everything came back again who ever has this problem give it a shot let me know if it worked :D

it should be like this with no file on it since i deleted it
[HTC One S] BL4zD:
the battery life is phenomenal
[HTC One S] resetrobot:
I decided to move to a sense 5 ROM a couple of weeks ago and now I'm stuck on it. I can't flash any CM 10.1 ROMS at ALL :(

I feel ya...I gave up on trying to solve my issue.
[HTC One S] Krayvon:
!

on'ce you go sense you never go back?
[HTC One S] resetrobot:
I believe that is exactly what happened haha! But I am really bummed out because I love CM. I tried everything to go back and no dice. Stupid POS...I mean HOS bleh
[HTC One S] $droyd$:
You guys are having trouble flashing cm ROMs? What's the issue?
[HTC One S] djsubtronic:
I definitely did experience dropouts before the transition to 3.4, when changing bands.
[HTC One S] usaff22:
An RUU would be your best bet. (Keeping S-OFF ofc) Then flash nightlies again, and 1.15 AOSP radio for good measure.
[HTC One S] fzurita:
Try this:

http://technology-headlines.com/2010/09/17/4636-android-secret-codes/

It's the *#*#4636#*#* code you put in the dialer.

It allows you to change the band type in your radio, maybe somehow it get reset to 2G only. I believe anything you change in the radio would transfer to other ROMs as well.
[HTC One S] djsubtronic:
They definitely don't transfer to other ROMs, on CM they don't even survive a reboot.

It sounds suspiciously like the loss of 3G issue that a lot of people including myself faced when upgrading to the JB firmware while being S-OFF, 3G would only stay for a few seconds if at all. The only solution was to get the motherboard replaced by HTC.
[HTC One S] bunga bunga matze:
Any error message?

If all sucks, I would try to flash the latest ruu first... :rolleyes:
[HTC One S] el_smurfo:
Yeah...If he really went back to Sense a few weeks ago, probably missed out on the firmware update requirement and is failing the hboot test in recovery flashing.
[HTC One S] bunga bunga matze:
exactly....;)
[HTC One S] vonski:
Screen rotation does not work for me in last nightly. Anyone else with same problem?
[HTC One S] resetrobot:
No error message just bootloop. I'm on hboot 2.15 - baseband 1.13 - 3.4.10 bulletproof kernel - S-OFF - Super CID...I've searched and searched and flashed everything. Nothing worked. RUU seems to be my only option.
[HTC One S] maluus:
Personally I closely watch nightlies and try nearly everyone. I use europe 1.15 radio and never had data drop issue with 3.4.49 kernel. but in every nightly since the kenel reverted back to 3.4.10 and later 3.4.11 having data drop issues and find myself with 27/06 nightly with 3.4.49 kernel.
[HTC One S] machoman1337:
Currently on the Bell 1.09ts radio. Going stateside this weekend and getting a TMo sim - should I flash the TMo 1.13 radio? Or is the EU 1.15 better (seen some North Americans using it)?
[HTC One S] el_smurfo:
I've tried them all and only see very slight variations. I'd just stick with what you have...not sure if the temporary radio installer still works (Sense version, not CM), but that might be an option if you get here and find signal problems. You'll have much more of a problem from the crappy T-Mobile network in the first place, unless in a major population center.
[HTC One S] machoman1337:
Going to Boston, specifically the harvard/mit area in Cambridge.

On the topic of CM10.1, does anyone think it might be a good idea to revert back to a 3.0 kernel for official nightlies if the screen-on time can't be solved? Performance on that kernel was pretty decent, and other than the data drops, everything worked fine even GPS.
[HTC One S] Krayvon:
!

thats what i'm thinking too. downloading the latest ruu. for tmobile us, i'm assuming its the jb 45.us. 3.14.531.11?

i dont care about reunlocking or anything, i just want to get my 3g back as edge is extremely annoying
[HTC One S] Krayvon:
i just dont get it. just ran RUU latest and its completely return to stock. the bastard is still 2g fml
[HTC One S] usaff22:
In that case, it's HTC for you. They'll probably give you a new board.
[HTC One S] Frostbeule2k:
Hey guys,

I´ve one question; which of all the CM versions, nightlys, stables and snapshots are the best rom for the daily usage. So I mean in which rom does all functions will work and I´ve a good battery lifetime?

I´ve followed the thread for some days and see with each nighly some other user will report back that something is not going.

I will a good rom for my one s without the bloody sense ui. The problem which I have with BB9 or HBB is the darkness, I don´t want it soooo dark...
[HTC One S] Darknites:
You can use themes to change that lol.
[HTC One S] Stainless7221:
I flashed the ROM 2 days ago and my phone gets very hot when I am only browsing the web..
[HTC One S] machoman1337:
What is your CPU governor? It might be stuck on highest.
[HTC One S] bunga bunga matze:
Hallo Landsmann...:D

07/30 seems very good, all functions are working and the battery life is ok!

If you want much better battery life, choose one of the last with 3.0.x Kernel....

For roms with 3.4 kernel, you need HBOOT 2.15 (you get it by flashing the latest ruu)
[HTC One S] greatpratty:
I am having the exact same issue. I was running cm10.1 and having some data issues that I attributed to the known data issues. I decided to return to sense and ran the ruu. After running the RUU I no longer have 3g. I have tried everything but at this point it looks like the only option is to send back to HTC for repair.
[HTC One S] Trekvogel:
Well, as CM site states:

Stable is exactly that. Intended for everyday use with everything working. Just not the latest features.

Snapshots are less stable but offer newer software and more features. They may or may not work for you in everyday use.

Nightlies are the latest builds. Every nightly some issues get fixed but it may also introduce new issues. They can be stable but there's no guarantee things will work as intended. Basically, they're test builds.

I'm running one of the latest nightlies without any issues. Maybe I'm lucky, maybe it works for most. No one can tell for sure.
[HTC One S] Stainless7221:
I changed it from interactive to ondemand, its still getting very hot. Battery life is also poor, Lost 40% in 1h46m around half of that in use, only browsing xda and the web.
[HTC One S] el_smurfo:
Try Better Battery Stats to see if you have any rogue app wakelocks? Also, are you using stock browser or another?
[HTC One S] crakarjax:
Stuck at CM logo

I just moonshine'd my HOS, now have hboot 2.15.4444 with S-Off and the latest nightly (8-04) gets stuck at the spinning CM logo. I have tried wiping and factory reset a copious amount of times to no avail. Is this a common issue and if so, any workaround? The pre-3.4 builds seem to work fine.
[HTC One S] el_smurfo:
Did you do a full RUU or firmware update to get hboot 2.15? If not, there may be some firmware dependencies you are missing...Try fastboot flashing the boot.img and clearing cache in fastboot as well...just for fun.
[HTC One S] Kalashnikitty:
Have you tried to fastboot flash the boot.img (just for testing)

Edit: pröööp to late
[HTC One S] crakarjax:
I did do an RUU update to get to hboot 2.15 prior to moonshine, but the provided RUU gave me 2.15.0000 whereas moonshine put an (apparently) modified 2.15.4444 on there. I have tried fastboot flashing the boot.img manually as well -- is there a way to verify that the flash actually succeeded? It does have the symptoms of an incorrect kernel.
[HTC One S] el_smurfo:
I only know how to check the kernel version from a booted ROM. Can you put a Sense ROM on and have it boot? There was one other person who could only run Sense ROMs on here a bit ago...I wonder if the moonshine SOFF is wacky? Would you be willing to RUU again and leave SON just to try and boot the ROM (it's not really all that bad)?
[HTC One S] crakarjax:
I currently have a CM10 nightly from march (3.0 kernel) installed and booted. The kernel active now matches the build date of the ROM and I did not manually flash the boot.img, so I am assuming that the boot.img was automatically flashed when I installed the ROM. I must conclude that the 3.4 kernel probably was flashing correctly.

Edit: what's a popular 3.4 sense rom that I can use to test?
[HTC One S] el_smurfo:
I think only CM based ROMs use 3.4 kernel from code aurora. Sense are generally stuck back at 3.0ish...
[HTC One S] Stainless7221:
Im using chrome, i will try battery stats later on
[HTC One S] el_smurfo:
I think Chrome does use the GPU more than the stock browser. Have you turned on anything fancy in the chrome flags? Maybe uninstall and reinstall Chrome to see if it gets less hot.
[HTC One S] machoman1337:
Chrome is a terrible browser on Android, even on my Nexus 4. I love the desktop version, but the mobile version is just a disaster - huge system hog, bad performance, etc. The stock CM browser is much better, and if you like syncing bookmarks and passwords with Chrome desktop then you can do that on the stock browser.

Even if Chrome isn't the root cause of your problem, I would still suggest using just about any other browser to avoid other problems!
[HTC One S] Stainless7221:
This can't be only chromes fault, i was on a kernel 3.0 rom recently and had over 2 days battery life, also with mainly just surfing with chrome or currents etc. Even when i don't touch the phone at night, i loose 1% per hour now! When i browse the web it gets incredibly hot and the battery is just melting away. I tried the new kernel a few weeks ago and it was the same problem and i had to switch back. But i like the rom! My tumblr app is finally working and its sooo smooth!
[HTC One S] asdfasdfvful:
With the newer Nightlies, the phone's screen turns on when plugged in. Is there any way to keep it off?
[HTC One S] Tendency88:
Ah good to see that AMD (Android Device Manager) just went live, at least a few hours ago in my country. (Netherlands)

It works great on my device running stock Android, but on my HTC One S with CM10.0 it's not finding any devices. Anyone else having issues with AMD running a custom ROM?
[HTC One S] crakarjax:
I flashed the latest Illusion 3.4 based rom and it worked! Wondering if it was just CM the whole time...
[HTC One S] mo976:
In developer options
[HTC One S] asdfasdfvful:
Um... Sorry but I don't see it. Is it in launch tools?
[HTC One S] el_smurfo:
I think he's talking about a different setting. The annoying screen when charging one is hard coded for some reason.

http://review.cyanogenmod.org/#/c/45579/
[HTC One S] resetrobot:
Yeah I'm the guy stuck on Sense ROMS. I used the facepalm method to get s-off and super cid.
[HTC One S] Krayvon:
!

pm me, i think i got a solution
[HTC One S] crakarjax:
Was your issue the same as mine? (Stuck at boot screen). If so, I'm curious whether the same ROM that worked on mine would work on yours -- the latest Illusion rom.
[HTC One S] mrpalin:
I've been using CM10.0.0 because I can't stand the horrible battery life with CM 10.1. When Codename Lungo was still using the 3.0.80 Kernel, it had some stellar battery life, and the only issue was facebook would FC when scrolling around (I think it was the 7/15 one). I ended up coming back to CM 10.0.0 until I find a ROM that will be satisfactory for Daily use. Even with CM 10.0.0 I'm often down to <15% with my phone unplugged from 7:00AM to 10:00PM with fairly average use. It really depends on the day and the apps I use. I find it drains quite quickly when using chrome.