yashsingh1/xdaforums huggingface dataset:
[HTC One S] Ollaz:
Unfortunately the thread I need gives me a 404 error.

Still looking for a way how to update from 2.15 to 2.16 as flashing the rom doesn't help - script checks for hboot and it refuses to install.

/edit: nevermind, this helped me: http://xdaforums.com/htc-one-s/general/guide-how-to-install-hboot-2-16-time-t2898605

Finally everything works as it should.
[HTC One S] kudykam:
Hi,

still have problem with camera. Sometimes it works sometime it doesnt run (device cannot be connected). Any idea how to solve it?

Phone restart usually help...
[HTC One S] overgonas:
Try to dirty flash the rom over, for me it solve a problem.
[HTC One S] Rapier:
On what nightly you're on? There was a commit for camera included in latest nightly (27.07) that could solve the problem. If you're on an older nightly you could still have the problem
[HTC One S] overgonas:
Amazing battery life compare to Liberty sense 6. My M9 has 2 hours less on screen wtf... :(
[HTC One S] qd42:
It seems camera really was fixed in 27.07 nightly, but I still have system crashes because of compass which I desribed in this post.

upd: false allert, camera error still there.
[HTC One S] FCKöln:
Since a few weeks there is a patch set available for the gyrometer. For testing i have compiled this into the frosted kernel and it seems to fix the reboots with Photo Sphere and Panorama in Google Camera. :laugh:
[HTC One S] qd42:
How can I install this patch?
[HTC One S] Rapier:
You can't. It has to be used when the kernel is compiled, at build time. Only way for a user to have it, is if someone provides a kernel with the patch included
[HTC One S] qd42:
Well, then I hope It will be included into the build one day.
[HTC One S] Rapier:
Change was submitted by [MENTION=5795145]javelinanddart[/MENTION] to CM and it was reviewed. They might merge it soon so it'll be included in CM12.1
[HTC One S] javelinanddart:
They haven't done too much about it yet....

However I posted a comment that users are reporting it's fixing gyro related reboots and I talked to [MENTION=1815755]intervigil[/MENTION] about it
[HTC One S] F-L-Y-E-R:
New build

#Added 29/07

#Tested

P.S. Camera doesn't work :confused:
[HTC One S] realTobbse:
Build 7/29

Got the same Build running and in my case camera works fine. I got the original version for Hboot 2.15 (S-on).
[HTC One S] F-L-Y-E-R:
Hmm, strange. Are you using the stock one? I tried to clean data on both stock and google camera apps but when I tried them they did not work.

Just opened camera app from the lock screen and it's actually working :confused:
[HTC One S] Hauk92:
CM 12.1 with gyrofix

I have build CM 12.1 for hboot 2.16 with the above mentioned gyroscope related commit.

Download:

Android File Host

BasketBuild

Camera including photosphere works for me, but panorama seems to be broken.

With this and the last two builds from F-L-Y-E-R I can force a reboot in Cadence Running Tracker and I can crash Titans of Space.

So all in all not much seems to be fixed, but I noticed no regressions.
[HTC One S] ianjane:
with 29/07 build (2.16 hboot), I also got the camera issue (failed with message prompting unable to connect to camera).

But now camera seems working after a soft rebooting. :confused:
[HTC One S] qd42:
This sound like this fix doesn't change anything because now I can do the same things without it. I mean sometimes I can use photosphere and panorama in camera, observe panoramas in Google Maps and use Compass app and system will keep working. But at other times all this action can crash the system.

This Compass app is absolutely not essential everyday app for me, but I like to use it as indicator of gyrometer stability. On this CM12.1 I can't run and close it more than 3-5 times in a row, on 3-5 exit from this app system crash for sure will happen. On CM11 a can run and close it more than 10 times in a row and system will not crash.
[HTC One S] FCKöln:
Here are some results of my further testing. Without this patch my device reboots in about 95% when starting Panorama or Photo Sphere. Even in that situations where i was able to start Photo Sphere i was not able to save the result because every time i have done taking all the photos with Photo Sphere the Gyrometer was reinitialized and it rebooted again. With this patch i did not have a single reboot with Google Camera.

Even with this patch there are still issues present. In about 50% when starting Photo Sphere or Panorama, the Gyrometeris is acting crazy, it looks like if i am flipping/turning the phone around very fast. It seems that initializing the Gyrometer was not done correctly in this case. I have to switch between Camera and Photo Sphere one or two times to get it working.

Another issue is that the Gyrometer is not that precise and the Photo Sphere picture starts moving to one side even if i am holding still the phone but that issue was even present without this patch. Might be faulty hardware...

I also tried the compass app with the patch and it initializes fine but when closing the app the phone reboots in about 50% of the tests with about 500 lines of this message in last_kmsg within 7 seconds

ewtzmu2daemon_ioctl: EWDAE_IOCTL_GET_AKM_READY,akm_ready= 0x0

btw i am using EuphoriaOS with Frosted Kernel
[HTC One S] F-L-Y-E-R:
Just built a new nightly and again the camera doesn't work 'can't connect to the camera', someone has same problem? Maybe something is wrong with my hardware :confused:
[HTC One S] overgonas:
I'm just installed latest official cm and had to reboot couple of times to get camera working.
[HTC One S] F-L-Y-E-R:
New build

#Added 07/08

#Tested

P.S. Camera seems to work fine. From what I understand there was an update to Google Camera that made some changes which messed something up, so just uninstall the app and install it from the Play store again.
[HTC One S] qd42:
Why it's so many troubles with CM 12.1 for this phone? I'm using unofficial build on older HTC Desire S and it works a lot better in terms of stability and it doesn't have any problems with camera.
[HTC One S] F-L-Y-E-R:
I think there was some changes made either to CM/AOSP source or Google Camera app that messed something up. I actually uninstalled the Google Camera and reinstalled it again, everything seems to be ok with the latest build.
[HTC One S] qd42:
And what about gyrometer?

UPD: I'm just tested it by myself and gyrometer problem is still intact. I make clean install of the rom and get phone reboot on first start of compass app.
[HTC One S] Pori12:
Guys, please how to remove "Google quick search box" from the top of my homescreen? Thx!
[HTC One S] Gudio142:
Hey, I had a problem with data connection so I checked APN settings and everything looks well comparing to settings given on Orange PL website. I noticed that data started working when I switched IP protocol to v6. Why? I can't send MMS now.
[HTC One S] qd42:
Delete Google app or use alternative launcher, e.g. Apex.
[HTC One S] Pori12:
Thenks! So, amazing idea to eternally stick a piece of s . . t to the main screen. Congratulations CM!
[HTC One S] Rapier:
Same does Google with GEL so that's not their ideea
[HTC One S] SirBeherit:
But what when stock camera app doesn't work and others application (Snapchat, Messager etc.)?
[HTC One S] kdd998:
Don't know if anyone is still having GPS/gyroscope/compass problems but I switched back to CM 12.1 (2015-08-06 nightly) on HBOOT 2.15 with radio 1.20 and I didn't have a single reboot. Before, when using Ingress and Google Maps I could have a reboot at least 2 times a day. I saw the related commits to our kernel and it might have done the trick.

Yesterday I tried hard to have a reboot by multi-tasking with GPS intensive apps without success.

On another matter while changing the battery I cut wires somewhere and I lost the capacitive buttons. I can't see how it would be related.

Anyone still having reboots on a recent official nightly?
[HTC One S] EssCee:
Is anybody having 'Setup Wizard stopped' issues?

Updating to cm-12.1-20150810-NIGHTLY-ville.

I've tried with both gapps-5.1-2015-07-03-13-41.zip and gapps-5.1-arm-2015-07-17-13-29.zip, with Dalvik and Cache wipes after.

No joy.

Cheers,

Stuart
[HTC One S] qd42:
I'm still have reboots on exit from compass app :(

Can you check it on your device? Install this app and try to open end close it 3-5 times in a row. Crash should occur on exit from the app.

---------- Post added at 10:45 PM ---------- Previous post was at 10:41 PM ----------

I never had issue like this. Are you doing factory reset before flashing ROM?
[HTC One S] EssCee:
Hi qd42,

... have to admit, I've been wiping Cache, Dalvik, Data (and System, altho I am aware that it's not needed). I thought doing these removed the need for factory reset?

Cheers,

Stuart
[HTC One S] qd42:
Yeah, this actions actually the same as factory reset. Well, I don't know then. I'm personally using this Minimal Edition of gapps, maybe you should try too.

Wipe everything again, install cm image, than gapps and don't forget flash boot.img via fastboot.
[HTC One S] kdd998:
I guess I was very lucky those past days, with this app, on first usage: a reboot [emoji22]
[HTC One S] qd42:
Yeah, this app is perfect stress test for this firmware :D On CM 11 I can open and close it an infinite number of times.

Thanks for your shot on this anyway, now I'm at least know that I'm not lonely with this problem. Hope developers will solve it one day.
[HTC One S] F-L-Y-E-R:
We always hope for someone to fix these issues but the main problem is - 4 years old One S that no one really takes serious anymore because there is no point to do so.

If issues like that really bothers you, there's only one way out - get a new phone which is still supported by OEM and don't make the same mistake by choosing 2nd tier device like One S because OEMs only take care of main phones.
[HTC One S] EssCee:
Flashing boot.img is only needed if the phone is s-on, am I correct?
[HTC One S] pauldey:
Yes, you're right
[HTC One S] qd42:
I know that this model is old. But I think since CyanogenMod team claim that they support it officially, they should take care of it more seriously and make releases without major issues like this gyrometer one.

Or they should just discontinue it as official version, because otherwise it just ruins CyanogenMod brand.
[HTC One S] FCKöln:
Unfortunately these low level issues are hard to track but i agree with you. If it's officially supported then there should be someone who can take care of bugs like these.

However, there has been some progress because, as i have posted before, the patch that javelinanddart provided fixes the google camera reboot with Photo Sphere for me. The compass app still reboots the phone when closing it but i was able to workaround this by setting "akm_ready=1" (ignoring akm_get_akmd_ready()) when EWDAE_IOCTL_GET_AKM_READY is called. We most likely need a similar workaround here like the NACK workaround by javelinanddart. There is definitely something wrong on the communication part with this gyro device...

For me, the only things left is the gyro initialization (need to start Photo Sphere 2 or 3 times to get it working) and the camera bug, where camera can not be connected (or flashlight can not be turned off) but this one happens to me only on the first boot after flashing the device. After a reboot i don't see this issue anymore and i am able connect the camera and start/stop flash light.
[HTC One S] EssCee:
Have now tried with that version of GApps - same result 'Setup Wizard has stopped'.

My phone is S-OFF and unlocked

My procedure is:

- Backup current configuration.

- Wipe Data, Dalvik and Cache.

- Install new ROM.

- Install GApps.

- Wipe Dalvik and Cache.

- Reboot into system.

The boot happens normally, the apps install and I am presented with the SIM card PIN entry screen. Entry happens without issue, and the phone connects.

At this point the setup wizard error occurs

Do I need to boot to system between installing the ROM and GApps? Or wipe Dalvik and Cache between the installations?

Cheers,

Stuart
[HTC One S] qd42:
Did you tried to boot system without installing gapps? Does this error occurs in this case?
[HTC One S] EssCee:
I tried it and it works.

Procedure now is:

- Backup current configuration.

- Wipe Data, Dalvik and Cache.

- Install new ROM.

- Boot to system - complete setup wizard - no connection to internet configured.

- Reboot to recovery.

- Install GApps.

- Wipe Dalvik and Cache.

- Reboot into system.

:good:
[HTC One S] F-L-Y-E-R:
New build

#Added 14/08

#Tested
[HTC One S] qd42:
Compass problem still there.
[HTC One S] F-L-Y-E-R:
Thanks, but there is no need to mention it everytime. If you check http://www.cmxlog.com/12.1/ville/ you will see that there were no changes regarding this issue so it's obvious that it will not disappear by itself.
[HTC One S] imilne:
I've just upgraded from CM11 and I've noticed that apps moved to the "sdcard" don't remember their privacy guard settings. Has it always been this way with CM12.1 or is it just pot luck with the nightly I'm on (7th August just now).
[HTC One S] Rapier:
You should've made a clean flash

Sent from nowhere over the air...
[HTC One S] imilne:
It was a clean flash. A completely fresh start.
[HTC One S] frantisek.nesveda:
I'm using the latest build now, I've made a clean install, and sometimes I still get the "Can't connect to camera" error. Usually it goes away after a reboot. It's not only Google Camera that has the problem, other camera apps don't work as well, so I suppose it's a problem with the CM source. I can't find anything useful in the logs, though.
[HTC One S] F-L-Y-E-R:
New build

#Added 22/08

#Tested
[HTC One S] ChristianFS1:
aren't we supposed to flash the boot.img before flashing roms and so on?

and is it really strictly necessary to upgrade recovery if it's relatively recent? add to that we're flashing boot.img on top of it anyways.
[HTC One S] Rapier:
You need to flash boot.img ONLY if you're S-On...if S-Off you don't need to. Flashing it before or after the ROM zip in recovery doesn't matter. In recovery, the boot partition is not flashed (cause you're S-On) so what matters is to HAVE a boot when booting the ROM. You don't need to upgrade recovery if you're using some of the latest versions though, "relatively recent" is...relative. Theoretically any TWRP after 2.8.1.0 will work but it's better to have the latest (2.8.7.0). And flashing boot.img is not done "on top" of it, boot.img has nothing to do with the recovery
[HTC One S] mkoev:
If he comes from an Xperia phone that explains all of it. I had an Xperia Sola and there boot and recovery partition was the same thing.
[HTC One S] ChristianFS1:
I've got access to several Sony Ericsson phones, and yep, you're absolutely correct. i was getting error messages on an ST15i, it told me that "encryption was unsuccessful". afterwards i tried flashing a newer iteration, following the correct procedure and all, and now i'm getting infinite bootloops. i made sure that i did everything correctly, so i'm pretty clueless as to what happened and how to fix it, besides restoring it to stock if that's even possible. and that's why i was asking that question, since i can't really afford to lose my main phone.

so, i'm supposed to do the following in order:

flash a recovery first via adb.

flash boot.img via adb

do all the obligatory stuff like wiping and so on.

flash rom and gapps in recovery (twrp)

reboot and pray for it to work.

please correct me if i'm wrong, before i do something stupid/irreversible. :)
[HTC One S] mkoev:
You need to flash the boot.img file after you flash the rom and gapps, not before. That goes only for S-on. If you are S-off you don't have to flash boot.img at all.
[HTC One S] dim.on:
I've written a small patch for the gyro-sensor.; try it if you have problems with it.

http://pastebin.com/HBTfjXSQ
[HTC One S] qd42:
How to use it?
[HTC One S] Rapier:
You can flash boot.img whenever you want, before or after ROM flash but AFTER you wipe...wiping cache/dalvik doesn't matter but wiping /system will also wipe boot. So a correct order would be:

either:

flash a recovery first via adb.

do all the obligatory stuff like wiping and so on.

flash rom and gapps in recovery (twrp)

flash boot.img via adb

reboot and pray for it to work.

or:

flash a recovery first via adb.

do all the obligatory stuff like wiping and so on.

flash boot.img via adb

flash rom and gapps in recovery (twrp)

reboot and pray for it to work.
[HTC One S] dim.on:
This is a kernel patch for the gyroscope driver.

It fixes reboots which appear when apps access sensors.

You have to downlaod the kernel sources for ville, apply the patch, build the new kernel and flash it on your phone.
[HTC One S] Vap0rX:
Which kernel is recommended? I tried Frosted Brick Edition kernel, but as soon as I increase Headphone Amp, I am having trouble with mic.
[HTC One S] Darknites:
Wiping system does nothing to boot.img more so with S-on, I'm shocked you even said that.

The best way is flash recovery then boot.img then factory wipe in twrp (not the bootloader) then flash rom and reboot.

---------- Post added at 10:03 AM ---------- Previous post was at 09:57 AM ----------

There is a file you can edit to boost volume, if you search for volume fix or volume boost in the Candy thread you find out what file.
[HTC One S] Rapier:
Right...I'm used too much to be S-Off and even before, when I was S-On, I could flash boot.img, radios and so on straight from recovery. I never had to flash the kernel in fastboot. But the flash sequence is right in both cases.
[HTC One S] pavel.bosco:
I'm now on build of 2 June.

could someone please recommend most recent fast and stable version for HBOOT 2.16, w/o major bugs?

my version is almost good, but it seems laggy, especially then I turn display on, and start any app like gmail or chrome - it take 3-4 seconds for them to pop-up

and also after reboot it always optimizes apps, which takes 2-3 minutes and some battery..

I noticed that current version not correctly handles compass, which might be critical as I use navigator kind of app in car. Are there any more recent than 2 Jun and stable versions exists?
[HTC One S] GrayFox814:
Didn't work :-/

Maybe I should try flashing a radio? I have no idea which one though.
[HTC One S] F-L-Y-E-R:
1.35a should be fine
[HTC One S] F-L-Y-E-R:
[MENTION=5795145]javelinanddart[/MENTION] [MENTION=5917915]Ivan16198[/MENTION] have you both flashed this ROM on top of CM11 without wiping?
[HTC One S] Ivan16198:
No, full wipe (except the internal storage).
[HTC One S] corbeau56:
Same problem for me. Google play services crashes during search for updates after first connection to WiFi. No possibility to skip that step, so I can't continue.
[HTC One S] F-L-Y-E-R:
@corbeau56 @Ivan16198 If both of you are on hboot 2.15 you flashed 11/21? Try flashing 11/20 as it was build from clean. If you have twrp recovery just swipe 'factory reset' it'll not wipe you internal memory don't worry.
[HTC One S] Rapier:
Which versions have you tried ? I started with first LP build after that I've flashed them dirty. Maybe the later builds have issues if flashed with full wipe, don't know. Anyone who has those issues tried to clean flash the first build? And also please state your hboot cause this could also be a difference and TWRP version you used for flashing
[HTC One S] Ivan16198:
I tried 11/20 and now all works perfectly. I will try to update to 11/21 to see what happens.

UPDATE: Updated to 11/21, random crashes and issues again. I noticed apps like Google Camera were hidden.
[HTC One S] javelinanddart:
Wiped all but Internal Storage and USB OTG

I only tried 21/11
[HTC One S] letsurock:
Is camera working with the latest build?
[HTC One S] and.u:
Nope?
[HTC One S] bidiro:
Any updates on Android 5.0(lollipop) for HTC One S (Ville C2) ?

Any updates on Android 5.0(lollipop) for HTC One S (Ville C2) ?:confused:

Please Send me link of latest and stable ROM.

Waiting for Android 5.0

:cyclops:
[HTC One S] st4y.g0ld:
I read somewhere it's only cm10.2 for c2..
[HTC One S] Loreane Van Daal:
You should check http://xdaforums.com/htc-one-s/c2-development. But don't expect much.
[HTC One S] Rafek Rafat:
small problem

i face a strange problem with CM in general ,,, i have to change the kernal to can use the Rom without restart OS is there any kernal for CM12 to test the Rom ???
[HTC One S] Rapier:
Not at the moment. Only available kernel is the one that comes with the ROM

Sent from nowhere over the air...
[HTC One S] javelinanddart:
Working on it.... :)
[HTC One S] drkxyz:
YES!! Just recompiled from source and camera works ... Thanks to all!
[HTC One S] Rapier:
You've built it based on latest source and camera works now in CM12? That's great news. Hope they'll fix the hotspot too, I think that was the last remaining thing to fix. And add the CM customization options ofc

Edit: you might upload it somewhere for others to play with it if you don't mind

Sent from nowhere over the air...
[HTC One S] YoMarK:
Could you share your build? Do not have a build environment myself right now.

Tnx in advance.
[HTC One S] qd42:
It seems all 5.0 and 5.1 based ROMs have problems with camera and compass, so it will be hard to find really recent one. Maximus HD probably one of the best options for hboot 2.16, it fast and stable but based on quite outdated Android 4.4.2 and it also has HTC Sense.
[HTC One S] sorewinner:
Can anyone explain the reboots that seem to occur when available RAM gets very low? Would a different kernel fix this?
[HTC One S] kdd998:
Did you see the recent changes in Gerrit?

Those ones: ewtzmu2 topic on Gerrit for android_kernel_htc_msm8960

It seems that Ethan (and Matt) have been working on the gyro problems. Let's wait for the next nightly build and test this. Big thanks to them anyway :good::good::good::highfive:
[HTC One S] qd42:
Sounds like amazing news :fingers-crossed:
[HTC One S] wachutunai:
WiFi to Data switch

Hi guys,

Has anybody experienced problems with mobile data not connecting when moving away from a WiFi hotspot. I've observed that after several hours connected to a WiFi router, when leaving my place for example, the phone is not able to establish a data connection. I'm using radio version 1.15.50.05.29_10.30.50.08L in case someone has experienced similar issues.

Cheers!
[HTC One S] qd42:
Well, I'm tested this build from 26.08.2015 but gyro problem doesn't seems solved for me. Phone still reboots on exit from Compass app like before.
[HTC One S] FCKöln:
I didn't test the compass app, only Google Camera and it is much better now. With the previous patches i had to switch a couple of times between Photo Sphere and Panorama until the gyroscope initialized correctly. This issue is gone now. Great work!
[HTC One S] kdd998:
I'd say this is better. I used the compass app and it still often reboots while exiting, but not always. For Google Camera, no reboot while using panoramas.

But with Maps or Ingress not one reboot yet, but it doesn't say much: I often saw no reboots during almost one week.

I'm going to keep using the nightlies during a few days to see...
[HTC One S] fradav:
I tried your patch on latest CM HEAD, but be aware that the name of

EWTZMU2_ReadSensorData

and

EWTZMU2_ReadSensorDataFIFO

functions has changed since they added proper I2C lock wrapping around them (hence the

_Locked

name). If I understand correctly your patch, you count 10 times before actually sending

EW_DEVICE_POWERED_OFF

?

Nevertheless, compass app still crashes on exit with this.

Regards
[HTC One S] dim.on:
Please post the contents of /proc/last_kmsg after the reboot happened.