yashsingh1/xdaforums huggingface dataset:
[HTC One S] kurtfimmers:
Camera

Just Downloaded the latest MIUI rom, AOSP based, cause they don't speak of camera issues. Looks like it is indeed AOSP based and they have the sense camera working?

How s that possible?
[HTC One S] fipsib:
Your definitely asking in the wrong thread, how shall we know what they did? ;)

& the other question is, do they not have any camera problems or do they just not talk about it? ;) are you sure they are using the sense camera? Did you flash the room already& tried it ? Let us know!
[HTC One S] kurtfimmers:
Indeed I downloaded the last version, and flashed it. It is definitely AOSP based and has the sense camera. I tried it, took 10 pics and created different videos, closed and reopened the app and never crashed, all video's were ok...

And I'm NOT ASKING in the wrong tread 'cause I DON'T WANT A MIUI ROM! I'm a huge fan of CM ROMS but need camera (photo and video) working perfect (needed for work) before I can use it as a Daily driver...

Was just curious how they do it but am not a devolper nor a programmer...
[HTC One S] everywell:
/* OT

The miui based on AOSP is based on CM9 so it has the same problems that has the CM9 with the camera.

The miui based on Sense has the camera 100% working because it is the Sense one.

There are 2 different threads where you can find the two differents roms.

OT */

If you have something more to ask let's do it in the right thread.
[HTC One S] fipsib:
hm after my latest researches I also suspect opening/using the gallery application to introduce a wakelock, so better reboot after using it!

or deactivate it & install e.g. Quipick (not sure yet if it works/not introduces a wakelock)

//xkonni postet a Hotfix for the in-call echo

//updated the OP
[HTC One S] djsubtronic:
What's the status of the headphone issue?

I came up with a hack which fixes it for the most part, and while it's not an ideal solution, I think it's better than using a widget.
[HTC One S] fipsib:
what does your hack do, how does it work? (or: what's working & what is not?)

why do you think it's not an ideal solution?

//updated Q&A/FAQ section
[HTC One S] djsubtronic:
Basically in the WiredAccessoryObserver it looks for a specific headphone state which is triggered when it's plugged in, using a public variable.

This is what happens when the headphones are plugged in:

V/WiredAccessoryObserver( 430): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=130, DEVPATH=/devices/virtual
/switch/h2w, SEQNUM=3317, ACTION=change, SWITCH_NAME=Headset}
E/WiredAccessoryObserver( 430): unsetting h2w flag
V/WiredAccessoryObserver( 430): newState = 0, headsetState = 0,mHeadsetState = 0

And plugged out

V/WiredAccessoryObserver( 430): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=0, DEVPATH=/devices/virtual/s
witch/h2w, SEQNUM=3318, ACTION=change, SWITCH_NAME=Headset}
E/WiredAccessoryObserver( 430): unsetting h2w flag
V/WiredAccessoryObserver( 430): newState = 0, headsetState = 0,mHeadsetState = 0

If you notice when plugged in the SWITCH_STATE is 130, but the newState and headsetState remains zero and it says 'unsetting h2w flag', so no change happens. I added an if condition on the UEVENT method so that if the switch state is 130 to set my custom public variable to 1. Then on the final update method it checks if that variable has been set to 1 and forces the newState and headsetState to 1 instead of 0.

It's quite a crude hack hence why not ideal, cuz it's probably not a complete solution. From what I've seen it causes errors when the mic is used - eg calls won't work, and Google Now doesn't work either etc.
[HTC One S] fipsib:
thanks for your work! But as making calls is like the most important thing on a phone it's not that ideal! :)

talked to xkonni & he told me that they fixed it, so in the next build its working!

// & it's alive! http://ville.giev.de/?p=436

//updated the OP
[HTC One S] mustang00066:
New build is running smooth. Notifications no longer blur and music plays through headphones without widget. It doesnt show headphone icon when plugged in like i seem to remember it doing. Also, phone call doesnt come through headphones and person on other end doesnt hear anything when theyre plugged in either.

Not a 100 percent clean install as i just flashed it over the last build.
[HTC One S] djsubtronic:
Calls work fine with headphones for me on today's build.
[HTC One S] No_Fear:
Great work. Themes are working too.
[HTC One S] fipsib:
did you use the widget before? could it be that its still on? because that sounds very much like the problems I had when I did not tun off the widget before answering/making a call

for me it's working brilliant over here, plugging in/out headphones works like a charme, no matter if during a call or while listening to music (safe headset volume feature also works!)
[HTC One S] LikeaG2root:
Downloaded latest 29 version and have no camera app. Is that correct?

Sent from my HTC One S using Xparent SkyBlue Tapatalk 2
[HTC One S] klutch:
nice work on the headset only couple of things still failing on me some of the widgets i put on stayz but when u reboot they disappeared and battery same again everytime i trype something on it it sukz in 5% of the battery keepz draining again but other then that good job guys @ least i can wait lol
[HTC One S] fipsib:
did you try the steps in the OP? because now i get brilliant battery life,...
[HTC One S] Marcel_87:
Stuck in Bootscreen

Im not sure if I made a mistake... Im stuck on the bootscreen (froze)

Installed just like adviced in the OP. I´ll give it another shot and hope it works as other users posted the the new version (20120729) seems to be working fine.
[HTC One S] LikeaG2root:
Camera??? Full wiped, flashed latest ROM and jb gapps...no camera app.

Anyone respond please?

Sent from my HTC One S using Xparent SkyBlue Tapatalk 2
[HTC One S] djsubtronic:
Did you flash the kernel through fastboot?
[HTC One S] fipsib:
did you flash the boot.img in fastbood?

Please read the Q&A part in the OP!

download ICS camera like mentioned in the OP (theres also a link)

& better deactivate gallery as opening it also introduces a wakelock according to my researches. therefore install e.g quickpic
[HTC One S] klutch:
yes i did even a full wipe makes we wonder wat i am doing wrong then since u have good battery life :confused:
[HTC One S] Marcel_87:
Yes,

First I wiped factory, then installed ROM + JB GAPPS and then I flashed Kernel through fastboot. I use a script to fastboot the kernel. Worked for all other roms I have tried! Tried it 3x now without any result... :(

Do I do something wrong?! Im pretty sure I did everything as posted here http://xdaforums.com/showthread.php?t=1799139

Flashed using TWRP

===================================================================================

...:::EDIT:::...

I will try again using the --> boot-20120729-eng.img <-- you can dl at http://ville.giev.de/?p=436#comment-330 ... Also in other ROMs they have first of all flashed the boot.img then wiped data factory and then installed the rom... Maybe this will work out for me. Or will this not work with cm10...?! Is the order important anyway?! Thanks for your help in advance!! :)
[HTC One S] LikeaG2root:
First of all I am no noob. There is no camera app when I did fresh install. So I did try camera ICS and camera fx and both will not work.

Next I installed cm10 version 28 from other thread and it has camera. Then flashed xkonni's 29 version over top and camera app shows but does not open along with other camera apps.

Latest 29 version is missing camera function is all I can figure.

Sent from my HTC One S using Xparent SkyBlue Tapatalk 2
[HTC One S] fipsib:
hm thats strange, did you calibrate the battery (correctly)?

if it still doesnt work, in my signature you can find a tutorial to do it without any script (its very easy!)

order should not matter (i normally flash it before flashing the ROM, but never had problems flashing the Rom first)
[HTC One S] Marcel_87:
It worked... :) Thats the good news... But unfortunately, I have no camera app..?!?!!?
[HTC One S] LikeaG2root:
Latest version works awesome and so smooth but its not useable without a camera app:(

Sent from my HTC One S using Xparent SkyBlue Tapatalk 2
[HTC One S] jellydroid13:
Zaxondis already got it booted:confused:
[HTC One S] zaxondis:
I certainly did, but he makes a good point: Seems like you have to wait much longer than usual for it to boot, even if it looks frozen on the boot screen or like it's looping. Sounds like 10 minutes is the sweet spot.

With cache wiping, I only waited about 5 before I got impatient so maybe it works.

Either way, the devs are making tremendous progress.
[HTC One S] Bohemus:
+1, was really amazed by the quality of these first early versions. They run incredibly fast, and only a matter of time until the important things are working. On another note, will there continue to be development on CM9 towards an official for the ville or will it essentially be scrapped for developement on CM10? Seems to me jb is so similar to ics that it makes sense to focus all efforts on jb. the CM9 on ville was so close to "official" level anyway imho.
[HTC One S] djsubtronic:
This is true. Cyanogen has stated that CM9 development will likely stop as soon as the RC is reached, with all focus shifting to CM10.
[HTC One S] fipsib:
let me correct you, they will stop developing whenever a stable stable CM9 will be available:
[HTC One S] Bohemus:
Yes I read this as well, except that looking also on G+ at any of the multitude of CM posts regarding specific devices it would appear they have already begun work on CM10 considering there are already releases for some devices. Looks like they are working on both concurrently.
[HTC One S] mindsclosure:
xkonni said on his CM9 thread that he was mostly busy with JB right now. I guess they want to release a JB rom, with the fundamentals and stable enough, then release a stable official CM9, and finally work 100% on JB.
[HTC One S] klutch:
well i wipe everything on this working fine then again i know there work to do but the signal is doing alot of H to 3G and the signal bar not colored blue dont know why tho other then that the booting scared me i thought my fone frooze but it was loading tho lol ill play with this n see wassup with other stuff but Xkonni & intervigill good work keep it up

Edit 1:damn is it me or that booting takes for ever lol?

Edit 2:stared to download some apps this wat came up (Couldnt downloaded due to an error.(error retrieving information from server. [RPC:AEC:0])

Edit 3:if not mistaking when i click to make a call freezes wont let me dial and same thing going towards settings
[HTC One S] simnik123:
Try to Clear the cache and reboot. That Worked when the fail was on ICS
[HTC One S] Lodberg:
Is there anything a semi-noob with lots of brainpower can do to help you devs?
[HTC One S] fipsib:
I'm not a dev but I think everything we "normal" android rooters & flashers can do is not bothering the devs with unnecessary questions (this is why I opened this thread, so that we can help us by our self hopefully ;))

if you want to go deeper (this is what I will do once my exams are done in about a month) you can read, read & read & then try helping to fix things but that's a long way to go (at least for me)
[HTC One S] BiteBlaze:
If you want to get into developing, I made a thread on Compiling Jellybean for the HTC One S, and you can read about general development in the Chef Central: Android section
[HTC One S] klutch:
i did that twice and still the same and it was last nite i tried it still giving me that
[HTC One S] UserDemos:
New ROM posted for today 7/19. Anyone flash it yet to determine how it works? I'm interested in jumping ship to CM10, but won't until the phone calling capabilities are working first.
[HTC One S] Bohemus:
Just flashed it, boot time is significantly improved. See some more CM items have been merged, other than that not much different from the previous experimental release. Wasn't able to test to see if incoming calls worked, no one called while I was testing. At least not that I was aware of :)
[HTC One S] BiteBlaze:
Incoming and outgoing calls work! Its a miracle!
[HTC One S] fipsib:
I added a list to the OP with working things, if I missed something please tell me & I will add it :)

same goes for things which should be stressed that they are not working yet!

thanks for your help!
[HTC One S] nicxus:
This is my working list not sure how reliable is it.

I know this is all experimental but WOW great work to those that contributed. :highfive:

Working:

Sending/Receiving a mms works

GPS seems to lock/work so far

Receiving phone calls work so far, not sure how reliable it is

Not working:

Plugging in headphones doesn't not work

Screenshots:

On the third image signal drops completely and once in awhile.
[HTC One S] OriginalAuratic:
new build with wifi working is up
[HTC One S] phoenixita:
One build each day D: i think we'll get CM10 with almost all the HW working in a week :D
[HTC One S] fipsib:
I did not call you a noob, did I? ;)

if you had posted this in your last post I wouldn't have directed you to the OP :)

I assumed camera to be working (didnt try it until now) but on this build i'm also getting the "cant connect to the camera" message again, will talk to the devs about this! thanks for pointing out!

//edit: intervigil forgot a little change, so it should be working in the next release again!
[HTC One S] klutch:
i flashed the boot.img and this is wat it came up i am wondering why its saying fail @ the end

C:\Program Files\Android\android-sdk\platform-tools>fastboot flash boot.img C:\U

sers\KLUTCH\Desktop\boot-cm10-20120729-eng.img

sending 'boot.img' (5304 KB)...

OKAY [ 0.961s]

writing 'boot.img'...

(bootloader) signature checking...

FAILED (remote: signature verify fail)

finished. total time: 1.383s
[HTC One S] fipsib:
//edit:

its your fault,..

command is:

fastboot flash boot boot.img

& not:

fastboot flash boot.img boot.img
[HTC One S] Marcel_87:
same

Same here... Maybe there should´nt be a cameraapp because of the wakelock...(?!) But its not said to be like that anywhere :(
[HTC One S] LikeaG2root:
Thank you. I was just letting you know I am not new to this so that you didn't think I was crazy,lol.

Sent from my HTC One S using Xparent SkyBlue Tapatalk 2
[HTC One S] klutch:
hold on i try with the one Rom.zip from the and it worked but the solo boot.img that i downloaded from there didnt work
[HTC One S] xkonni:
fastboot flash boot /path/to/boot.img
[HTC One S] klin1344:
I think the problem is because you typed the command incorrectly.

It should be "fastboot flash boot boot.img"
[HTC One S] fipsib:
read the 1st post on this page ;)

sorry if my first answer sounded rude or so! peace ! ;) :D:angel:
[HTC One S] klutch:
i alwayz type it right and it go good but this one didnt and i did it with the ROM.zip and correctly when trough
[HTC One S] DigitalMonk:
I'm getting the call echo again on the 7/29 build. Person I called said it seemed less echo but definitely enough to be noticed. I can confirm notifications are no longer blurred and headset jack appears to work correctly.

Any chance of a hotfix for the echo problem? I'd love to stay on this build because of the other fixes but call echo is too bad.

Update: The 7/25 echo hotfix appears to fix the echo problem.

Sent from my HTC One S
[HTC One S] qwerty warrior:
thank you for telling us about the echo issue

i guess i will wait for a hot fix
[HTC One S] fipsib:
I also called a buddy to see if it works with the headphones & so, I also asked him if he can hear any echo but he denied,...

but glad to hear that the 7/25 Hotfix worked for you!

as I said, I couldnt reproduce the echo, perhaps it was a onetime thing for him (could also be caused by the carrier or so) & if not he wrote that the 7/25 Hotfix worked. so there you go

//edit: I checked both files in the Hotfix & the Rom & compared them & they're the exact same files so I dont know what went wrong for you, DigitalMonk!

so maybe it was caused by one of you two speakingpartners having bad receiption which was better after flashing the hotfix because you/your friend moved to somewhere with a better signal,.. dont know but thats the only explanation I have atm
[HTC One S] unk2009:
Hey guys, looking to give ROM a shot, where can I find the dl link ? Thanks
[HTC One S] frdd:
Link is in the middle of the first post, doesn't seem to carry over when quoting it though, some kind of quote in a quote in a quote situation:) Anyways download from http://ville.giev.de
[HTC One S] Brandonrz:
WHAT

THE CAMERA IS NOW BROKEN!! WTF!! :mad:
[HTC One S] mustang00066:
Did a clean install and had that thing where the SD card isn't accessible and had to erase everything... so an absolutely clean wipe.

Headphone doesn't work for me on calls. Same headphones work on my wife's mytouch 4g slide just fine. Not sure what that's all about.
[HTC One S] Lodberg:
cool down :). I'm sure the devs are aware of the camera status.

Outbreaks like yours doesn't do any good!
[HTC One S] Brandonrz:
K, just makes me mad
[HTC One S] fipsib:
thanks your words, mine wouldnt have been that nice.

// new build is up:
[HTC One S] phoenixita:
i'd like to test this rom but i'm scared about the "media process unstable"what does it means? :)
[HTC One S] djsubtronic:
Means that it doesn't properly scan the media on SD card. So your gallery/music player apps may be empty or incomplete. To be honest this is the only thing stopping me from upgrading. I even tried putting a .nomedia file in every single non-media folder on the sd card but still had no luck getting the media to appear. Hell, I also tried using the ICS MediaProvider.apk to see if that would work correctly, but got the same result.
[HTC One S] fipsib:
djsubtronic told you everything, but to be stressed: this doesnt erase the stuff on your sdcard, the content just doesnt show up (nevertheless you should always have a backup of you data somewhere when flashing)

putting a .nomedia file should stop the content from appearing, so this would have been the total opposite of what you wanted to achieve as far as I know.
[HTC One S] xkonni:
but he wants the mediascanner to ignore certain folders, which do not contain any media.

i suppose there are certain media files that crash the mediascanner, but i dont know which ones.

we have added some more libs that may help with it though.
[HTC One S] eckbauer:
Media process

All my media files show up, no problems eg Music Pics and my Document PDF files that are saved on my SD card.:fingers-crossed:
[HTC One S] djsubtronic:
No, I put a .nomedia file in all folders that I didn't want scanned. Interestingly enough, before I did that, my DCIM/camera folder didn't show up in the gallery at all, but afterwards, it showed up with 91 pictures instead of the 900+ that are actually there. On my CM10 build my music library stops building after 5000 songs, instead of around 5300, and in xkonni's build the music doesn't appear at all. I'm really baffled as to why it happens, and especially why it behaves differently on different builds. I don't even think the problem is with the scanner service since the ICS apk didn't help.

---------- Post added at 01:09 PM ---------- Previous post was at 01:08 PM ----------

How much media do you have on your sdcard? In terms of size and number of pics, number of songs, etc?
[HTC One S] xkonni:
We don't have that much space unfortunately. And with roms, backups and so on i just have a small part of my music on the phone:

localhost music # find | grep -c mp3
766
localhost music # du -hs .
4.1G	.

And not that many pictures either:

localhost ~ # find DCIM media Pictures| grep -ic -e jpg -e png
282

but i never had issues with disappearing ringtones or similar.
[HTC One S] djsubtronic:
I'm wondering if it is to do with pure volume...

find | grep -c m4a
5239
du -hs
6.9G

find DCIM Pictures | grep -ic -e jpg -e png
find DCIM Pictures | grep -ic -e jpg -e png
1329

...but still confusing as to why the result is not consistent between attempts/ROMs.

I noticed the new media scanner seems to scan in chunks of 500 files at at time, wonder if it's something to do with that?
[HTC One S] eckbauer:
Music 1.30GB Pictures 50MB

PS Just rebooted to see if it scanned the sd card and just the pdf file (document) were not picked up. Music ok.:(
[HTC One S] Chrisch-RT:
Hi,

is the "SIM Network Login" bug fixed?

Regards

Chris
[HTC One S] alchemyst:
Is the quality of pictures taken with the ROM better than the CM9 port?
[HTC One S] nicxus:
Build: CM10 20120729

The headphones issue seems to work when you plug it in, but let's say you restart your phone, while the headphones are plugged-in. The phone won't notice there are headphones plugged-in, and will play what ever sound out of the speaker phone first. Until you unplug replug it so it detects it again.

Aside from that the progress is damn awesome. :cool:
[HTC One S] adnana1024:
Is this stable enough to be used as a daily driver?
[HTC One S] fipsib:
No not yet

I dont think so as it's the same camera/code (but I didnt compare them as I never use the phonecamera)

its stable, so no force closes, reboots or so but take a look at the list of bugs & decide if they are the dealbreaker for you!

(also have a look at the Q&A/FAQ section in the OP!)
[HTC One S] el_smurfo:
I used it for a week with minimal problems. Had to go back to stock because I needed the camera for the weekend. If you don't use the camera much, are in a good signal area and can possibly charge the phone for a bit mid day, I would go for it.

---------- Post added at 09:43 AM ---------- Previous post was at 09:42 AM ----------

I did notice that the photos I took were not nearly as good as the sense camera and also seemed to be much smaller file sizes. Can't check settings now, but maybe someone can confirm the CM10 camera defaults to hi res 8MP photos?

---------- Post added at 09:46 AM ---------- Previous post was at 09:43 AM ----------

Now I remember why most of the original CM team left XDA. If the camera is broken, just restore a nandroid of a ROM that worked well for you and monitor the progress here until a more stable version is out.
[HTC One S] fipsib:
I can only say it again, updating to the latest radio, fixing permissions and clearing caches, turning off Google Now & location History, deactivating the standart gallery & recalibrating the battery fixed the battery issues for me,.. (I still think that deactivating Google now was one of the most important reasons for this) I had like 5 hours maximum until the battery went dead, atm it's running for 21hrs with a Screen-on time of 3h 8minutes & with HSDPA enabled,.. which is (in my case) way better than stock :)

so perhaps these steps (or one of the others I posted in the OP) might help you also, just try it! :)
[HTC One S] el_smurfo:
Did all that...I was the one asking about how to disable Now in the first place. The fact is, my office is in a low signal area and my phone stayed hot and my battery drained before my eyes. New radio seems to be helping a lot with stock Sense though and Now seems to be working on other phones running CM10 without this issue, so I'll hang out and wait until more investigations are done.
[HTC One S] Rodsky11:
My phone was burning up on the weekend as a result of the camera wakelock of death. However, I think the dev is right when he said the gallery may be causing the problem as well. I have taken care not to open the gallery today and so far the battery performance has been normal - 5 hours deep and only 20% down rather than 5 hours deep and phone dead! ;)
[HTC One S] el_smurfo:
I used quickpic as suggested. No gallery, no camera. I even returned to stock because I needed to use the nice Sense camera for the weekend.

Why should a "wakelock" cause such high heat when normal operation in a high signal area didn't? I would think it would act just like an idle phone with screen on?
[HTC One S] nickmv:
Edit: nevmind.
[HTC One S] ronnyhawks:
download link has NOT worked for 2 days now. not on 0729 build or 0730 build. op please use new download site that actually works, or someone please post a link/mirror? otherwise this is just a thread for old builds since new builds that are posted as "working" dont even have a working link to download. PLEASE FIX