yashsingh1/xdaforums huggingface dataset:
[HTC One S] $droyd$:
This question is every where...are you on tmo?
[HTC One S] boc11:
i have bug when take pictures in total darkness with flash On. The phone cant focus and freezes for about 5-8 seconds to take picture. Is it only my phone or from the rom?
[HTC One S] eckbauer:
Works fine for me just tried.I had to get in a cupboard for you mate.

Who uses a camera in total darkness anyway?
[HTC One S] AlphaDog_NL:
I have the same thing when the flash is needed for a proper picture
[HTC One S] eckbauer:
Ok i took one with flash and one without in total darkness.
[HTC One S] tnpapadakos:
just compiled 6/11 unofficial and it wouldn't boot:(
[HTC One S] $droyd$:
It won't boot because its likley running 3.4 kernel...do this....

In your directory go to

Kernel/htc/msm8960

Open the make file does it say in the top few lines somewhere sneaky weasel or sabertooth squirl...

Sounds stupid but just check and tell me what it says...
[HTC One S] tnpapadakos:
It says Sabertoothed squirrel

I hate crapple
[HTC One S] $droyd$:
Yup that's the 3.4 kernel..
[HTC One S] Darknites:
Ya I just had to change over to 10.1_3.0 branch to get things working again on baked.
[HTC One S] el_smurfo:
Ugh... that RUU is closing in on me from all sides ;)
[HTC One S] Darknites:
Yep lol.
[HTC One S] Dave77459:
Yet another painful chapter in the CM saga for the HOS. Happily, the latest nightly works really well for me, so there is no pressure to upgrade hboot and endure doing the RUU just to remove tearing that I don't experience.
[HTC One S] $droyd$:
Hahahahahah yeah its inevitable ...

---------- Post added at 09:10 PM ---------- Previous post was at 09:07 PM ----------

It's more than just removing tear... Don't worry tho it can still be built with out the 3.4 kernel... If someone wants to do it... Just takes more than repo sync and build
[HTC One S] el_smurfo:
I would say the same but:

Have tried 3.4 and it's noticeably better.

Can't even run Play Music on current nightlies without it closing.
[HTC One S] Michael1101:
Yeah I agree. It's really good, especially the beta 2. However the battery life is not really good. But I'm fully confident that this will be solved. :)

Edit: sorry smurfo, don't want to annoy you ;)
[HTC One S] carlos_abril_94:
And there is an anoying delay when waking the device.

Enviado desde mi One S usando Tapatalk 2
[HTC One S] $droyd$:
As of the last build there was... May be fixed..
[HTC One S] UnderZone7:
Hey hopefully you guys can help me out. I have a Rogers (Canada) HOS. I want to try the 3.4 Kernel but it won't boot. 1.13 and s-on I always flash kernels through fastboot. Do I have to S-off to use the 3.4 ?
[HTC One S] dyndragon:
Sorry, I missed it. Which RUU are you talking about that fixes tearing?
[HTC One S] eckbauer:
There's a thread for that.

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

---------- Post added at 02:31 PM ---------- Previous post was at 02:30 PM ----------

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

Just read the thread to get up to speed.
[HTC One S] Darknites:
No need for S-Off just an RUU thats at least 2.31 or higher to run it.
[HTC One S] wwelles:
What on earth happened to the battery life in the most recent builds. Any comments on what the most stable build is atm?
[HTC One S] Tendency88:
Wondering exactly the same thing, flashed from CM10.0 which had quite bad battery life on its own. But the most recent builds are by far worse. Is it the kernel causing this?
[HTC One S] carlos_abril_94:
I use the one from 12th May and lastest twisted kernel, great battery life.
[HTC One S] Tendency88:
On average use; some texting, some browsing, some music, and some simple game it doesn't even last 8 hours for me, before I have to charge it that is. My stand-by time is not even 12 hours, I'm charging nearly twice a day which is a pain in the ass haha.

You say great battery life, by what usage? And any idea on the stand-by time?
[HTC One S] maluus:
What is the latest kernel version available to use with CM 10.1?
[HTC One S] CarstenDutch:
Nightly 3.0.80 or Nightly 3.4 Beta
[HTC One S] tnpapadakos:
i found the 5/23 version and the 6/1 version to be really good all around
[HTC One S] maluus:
I m using nightly 3/12 and it is 3.0.68. so newer unofficial nightlies using 3.4 kernel? if not can you provide me a location where I can find that 3.4 beta kernel. thank you.
[HTC One S] $droyd$:
The kernel alone won't do you any good you'll need to go to the thread and flash the ROM and kernel...
[HTC One S] CarstenDutch:
There is a separate beta thread in developers section about Beta cm 10.1 with kernel 3.4, for some it's trouble to flash.

Don't know if the source is changed that they now are forced to build on the new 3.4 kernel. Can't tell you anything about that really,
[HTC One S] XXMrHyde:
Yes 3.4 kernel sources are merged into the CM sources, the 3.0 kernel source is still available, but its (to) much work to revert the device and vendor trees to work with the 3.0 kernel, (I guess that's the reason for some problems with newest unofficial builds using the 3.0 kernel).

Gesendet von meinem Nexus 4 mit Tapatalk 2
[HTC One S] Dave77459:
The 3.4 kernel thread does not want to discuss installation issues, it seems ("let's keep this pure so that the dozens of bootloops posts are obvious"), so I am asking here. I have an early hboot and have never had to fastboot the kernal like later hboots have. If I get 3.4 installed, am I forever stuck using fastboot to upgrade to the latest nightly?

I suppose I will come off as negative, but it seems really early to force a change to a kernel when so many people are reporting serious bugs and installation issues. I'm not a kernel wonk, just a user who enjoys the benefits of 10.1 work to date, and sees the other thread as portraying a step backward. Going from stable to unstable... why?
[HTC One S] ernestnwanu:
You'll probably need to run a RUU to get 3.4 kernel working. If you're S-OFF, you won't lose it. To answer your last question, isn't that what development is about? These are nightlies after all. It's quite the drastic change, but definitely necessary. It will only reach stable status after having being tested by a lot of devices and being worked on thanks to feedback from us.
[HTC One S] $droyd$:
Its not that I don't want to discuss the booting issues.. Its the fact that it has already been established yet everyone is trying to fight it ... You need the latest htc firmware to boot the 3.4 kernel .. Period..so it was discussed til a solution was found... Sorry if its not the solution you all where looking for but it is inevitable... Either you upgrade your firmware or you stay back...as far as the last of your question would you have rather I didn't break the ice with 4.2.2 ... Everything has to start somewhere otherwise we would still be on gingerbread... Someone has to break the ice... Do you remember the begining of 4.2.2 it was a little bumpy but is now the version of choice ..No one is forcing you to upgrade and run anything you don't want to run.. I for one will leave up all my links to the ROMs with the old kernel for those that want them but all further builds from me will be with the 3.4 kernel if I can help it. It is the future of our device...I hope you don't take any of that the wrong way I wasn't trying to be an a¢¢ ™
[HTC One S] el_smurfo:
Hopefully the firmware will get extracted from the ruu for folks like me and djsubtronic who get errors when running ruu. I'm now stuck with hboot 2.15 and still can't boot 3.4 due to ruu error. I know I can try super cid, but even the ruu is a dangerous requirement to run a ROM imo and super cid is not useful to most while causing problems for many.
[HTC One S] $droyd$:
Running an ruu is the easiest thing in android... Plug in your phone and double click the exe.. If you got an error you ran the wrong one... I told you in pm run one that coincides with your current hboot then accept the ota... You should find the correct ruu an re run it...
[HTC One S] el_smurfo:
Well, that's the thing with xda...everyone's an expert. In the 3.4 thread, one of the commentors said "why not just run the JB RUU?" which made sense to me. Unfortunately, RUUs seem to be very tempermental things, and mine managed to write the hboot to 2.15 before dumping out with an image error 158 which is very poorly documented. I tried to run it again with the same results, so now I can't run an RUU that coincides with my current hboot, because that one doesn't work for me and you can't downgrade hboot, so I'm mostly stuck until I have time to try some other stuff like flashing stock recovery, SuperCID and even flashing a Sense ROM which are all recommendations I've gotten.

So, no, flashing an RUU isn't easy at all. I'm an electronics hardware engineer with 20 years of experience designing ARM processor circuit boards which run Linux OS and it took me half the morning to get it to run at all, having to find an old XP computer because it wouldn't even run on my 64 bit Win7 box...dumped out at first click. After 4 hours, 2 of which were searches to gather the correct information, my phone is now way more hobbled than it was yesterday and I still can't run the latest CM kernel and I'm far from alone.
[HTC One S] topnomi:
Are you s-off?

if not, i would highly recommend it. The process went very easily. My phone isn't even a tmobile phone(cincinnati bell), i'm set to super-CID, and it took the RUU no problem.

another thing, USB 3.0 ports don't work properly in fastboot. just fyi.
[HTC One S] $droyd$:
OK well I want to help you.. Send me a pm with your gtalk ...I'm at work now but may be able too help...
[HTC One S] el_smurfo:
I have resisted SOFF as I have resisted running RUU because they don't add any value to me (until now). I will probably try that this weekend.

I am using a 2 year old i5 laptop with USB 2.0 ports and had to dig out my older Toshiba with XP to even get the RUU to run at all.

Thanks for the advice.
[HTC One S] intervigil:
FYI: Yes, 3.4 kernel sources and accompany device tree changes are now checked into the main CM repositories. The various issues (720p/1080p camcorder, battery drain, firmware/hboot) are the reason official CM nightly builds haven't started back up. There are no more legal issues preventing nightly builds now, as libDxOAF.so is gone.

For those installing various 3.4 kernel based builds, it's highly recommended you take the JB OTA. It may be better to direct discussion concerning installing JB via OTA or RUU to a different (maybe installing JB-specific) thread.

The reason JB OTA/RUU is recommended is because there are some changes that require either newer hboot, tz, rpm, sbl, or some combination of the above, it's just I'm not quite sure which ones/which combination are required. This is because the kernel expects that some CP15 register addresses are now different, and I have no explanation why. The relevant CodeAurora patches also shed no light on this matter. For what it's worth, 3.xx firmware seems to be required for evita as well, but strangely not fireball or jewel (maybe?).
[HTC One S] $droyd$:
Thank you for that...
[HTC One S] mo976:
back in march I did try the trick droid and viper sense JB ROMs perhaps something in the included firmware files as mentioned above is what allows my configuration of hboot 1.06 to work with the 3.4 kernel as they are based on 3.1x ruu's
[HTC One S] esbenm:
Sorry if this is too Q&A but:

When you guys talk about the 3.4 kernel (possibly) requiring the JB OTA - are you talking about the JB OTA from back in december 2012?

Or the update that came in May which, as far as I remember, includes a new radio?
[HTC One S] $droyd$:
The newest update is the one I'm talking about....
[HTC One S] Dave77459:
Seems like back in the day, unstable builds were labelled Experimental so that people with working versions wouldn't be lulled into thinking they were daily drivers. When a plurality of people reported continued success, then early-but-not-heroic adopters would jump in. It feels like this switch to 3.4 went from a stable nightly to reports of dysfunctional and possibly non-functional phones. It is self-labeled beta, after all.

I understand what you are saying, and don't mean to be an a¢¢ ™ myself. Thanks for all you do, and for your patience.

One thing that is so strange is that my wife has an HOS that she bought a month after me. Hers is stock. It is also running Android 4.0.4 and a 3.0.8 kernel. I don't think it has ever gotten a major OTA update from TMOUS, just a security patch. This excitement for 3.4 came from nowhere for me. AFAIK, 3.4 is a rogue thing completely foreign to HOS, not the way forward... a way sideways, perhaps? It doesn't seem driven by HTC if you look at her phone.

I see post 2 in the 3.4 Beta 2 thread finally includes a description of how to proceed forward. I am off tomorrow, so perhaps tonight I will give it a go. If it fails, my son recently upgraded phones so I have his old one to use if it goes badly. On the plus side, I'll maybe see why this is a step forward.

Time to be heroic, I guess.
[HTC One S] RockR172:
Just a heads up regarding the 3.4 kernel development being sideways:

No its not sideways, it is a forward progress.. the official HTC JellyBean uses 3.4 kernel.

The reason we have it slightly unstable is because it uses pure CodeAurora source with required parts n pieces of the Stock HTC 3.4 kernel source.. that way we get a less HTC bloated kernel and more pure Qualcomm based kernel... Also, can be easily up streamed to the latest revisions of the 3.4 kernel.. :)
[HTC One S] :
That's the one from Dezember. Or did I miss something?
[HTC One S] LIONS1:
Hey everybody for the several issues with the new 3.4 kernel that's what you should do to enjoy it :

http://xdaforums.com/showthread.php?p=42540922
[HTC One S] el_smurfo:
If this works, it's exactly what I've been hoping for. Did you try it yourself first?
[HTC One S] LIONS1:
Yes bro my phone had bootloops before this I couldn't try the new kernel & this way you won't get RUU stupid errors hope all of you manage to try the new kernel cuz it's really amazing :thumbup:
[HTC One S] $droyd$:
Can you make this into a thread that I can link ... Provided it works you saved me a lot of work..
[HTC One S] LIONS1:
I'll make a thread for that :thumbup:
[HTC One S] $droyd$:
Pm me the life k when your up.. Thanks
[HTC One S] Alie360:
Worked like a charm for me!
[HTC One S] LIONS1:
My own thread is up please feedback there if it's working for you guys

http://xdaforums.com/showthread.php?p=42540922
[HTC One S] bunga bunga matze:
Thx sir, but to late for me!

I installed ruu like oldschool (full ICS ruu.exe, than JB OTA)....

Just relock bootloader and installed it (without stock recovery), than OTA latest ruu.

Settings: s-on HB 1.13 -> 1.14 -> OTA 2.15

I can suggest this to all on JBrom and HBOOT/ firmware from ICS, since I am on newest ruu, I cant determine tearing!

The work paid off....

Ciao 3.0.xx Kernel and hello 3.4 Kernel....:D
[HTC One S] djsubtronic:
Experimental build - 3.4 kernel with hacks/workarounds for screen tearing, screen on delay, and battery life.

http://www.mediafire.com/download/t7owp669zzhljh5/cm-10.1-20130614-EXPERIMENTAL-ville.zip

Important - for anyone who has not used a 3.4 kernel ROM before, you might experience bootloops or the phone might not boot at all. Please refer to this thread for details: http://xdaforums.com/showthread.php?t=2322755
[HTC One S] yooouuri:
But with the 3.4 kernel there was no screen tearing?
[HTC One S] djsubtronic:
There was a tiny amount.
[HTC One S] mo976:
Does this include the updated camera commits and can it be flashed over beta 2?
[HTC One S] djsubtronic:
Yes and yes. I've flashed it over 3.0 kernel CM builds without a problem as well. But of course bear in mind it's experimental due to the workarounds I made, so always make a backup.
[HTC One S] blackhartct:
gonna test it out. I havn't used a cm10.1 rom in a while.
[HTC One S] adamfirari:
dirty flashed over 3.08 and first impression is good for me :) and camera works .(it didn't work for me with beta 2 kernel)
[HTC One S] el_smurfo:
You should probably link to the firmware update thread with each post. Some here haven't been following the saga in the other thread.
[HTC One S] ponchofiesta:
Can not say if any of these points are fixed but camera is working now. Didn't test 720p video.
[HTC One S] mo976:
720p doesn't work but 1080p and 480sd do as well as picture during video. Also the camera no longer "freezes" the screen with the last picture taken till you take another one.
[HTC One S] cdrom1028:
Holy cow, the train is back on track! @ djsubtronic .. How close is this to the Daily builds? Great work! :)
[HTC One S] Michael1101:
1080p video really works for you? For me it isn't. Picture during video is only possible with 480sd for me.
[HTC One S] mo976:
Must have been a fluke from the fresh reboot now it crashes oh well :(
[HTC One S] el_smurfo:
Are you still having signal stability issues? I notice mine bouncing from 3g to H a lot more since the firmware flash and wonder if we don't need the build prop changes listed in Tecardo's radio flasher thread?

ro.ril.hsdpa.category=28

ro.ril.hsupa.category=7

ro.ril.fast.dormancy.rule=2

ro.ril.radio.svn=5
[HTC One S] djsubtronic:
Yes but that's nothing to do with the ROM. My phone simply can't stick to any 3G/H signal at all. I did countless factory resets, RUUs back to Sense, it happens regardless of baseband, HBOOT, kernel, or ROM version. Leading me to believe it's either a SIM/service issue or a physical hardware fault - either/both of which happened to coincide scarily with my JB OTA update.

I need to get that resolved before I can do anything meaningful with those variables lol.
[HTC One S] el_smurfo:
Network issues at the same time as major ROM updates have happened several times to me, but TMO service is not very good here in the US. I'd wait it out for a few days (or take a weekend trip to the next town over!).
[HTC One S] Fruktsallad:
djsubtronic - thanks for you build, I'm downloading it as we speak. Mediafire is painfully slow, though so it will take me about an hour to get it. Does anyone know why people aren't using Mega (mega.co.nz) instead? So much faster and easier imho...
[HTC One S] el_smurfo:
mega is likely blocked by most corporate firewalls due to the copyright infringement history...i know it is on mine, while mediafire still is not.
[HTC One S] Michael1101:
Thanks for the build bro! I got two bugs. The first one is a strange one. Most of the time when I'm listening music with my headset only one ear piece is working (no, my ear piece is not broken, it is working with my computer and with other roms). When I'm rebooting it is working for a song or so and than again not.

The second one is probably not a bug but a feature :) When I lock my phone it wakes up when I press the home button. In settings the "unlock with homebutton" is not activated, it is greyed...
[HTC One S] Fruktsallad:
Oh... I was just about reboot into TWRP to backup/install, but that home button wake would be a deal breaker for me. Anyone else getting it?
[HTC One S] el_smurfo:
Argh...I have the ear piece thing too. I thought it was my cheap monoprice headphones! It's on today's $droyd$ build, so it must be a CM problem right now.

Mine doesn't wake with home though...I have all the wake options disabled.
[HTC One S] thiasB:
Noticed this too while playing songs via Google Play Music. The left channel was dead. Ingress sound and notifications were to hear on both speakers. Phone was connected to my car audio system with bluetooth.
[HTC One S] strker45:
Power amp works fine for music
[HTC One S] itsmikeramsay:
That's really weird you guys are having this media scan issues.... I can see my pics in gallery and play my music from Apollo with no issues...
[HTC One S] el_smurfo:
Mine was fine most of the day, then I noticed my custom Gmail ringtone wasn't working which led me to find all media on the sdcard was missing (though I can still view them all via a file explorer)
[HTC One S] itsmikeramsay:
Oh ok gotcha....that sucks it's happening, but I'd imagine it being fixed soon.
[HTC One S] LikeaG2root:
+1

Sent from my HTC One S using Xparent SkyBlue Tapatalk 2
[HTC One S] eckbauer:
What i did was:

1.Move all my my Media and pictures to my PC of my SD card

2.Then copied it back to SD card with an App call Airdroid.Do not use your USB cable and Mass Storage to copy it back,it wont work.It will take some time over wifi.

This worked for me Music and Picture show up now.:)
[HTC One S] djsubtronic:
The only work around which worked for me is to cut all your pics/music off the SD card, onto your PC. Then, go to Manage Apps - All - Media, and clear data. Reboot your phone. Then mount USB and copy back some of your media. Do it one folder or chunk at a time. After each chunk, unmount USB and let the media scanner run. Check your gallery. Your folder should appear. Lather, rinse, and repeat until all your media is back on the SD card. Reboot.
[HTC One S] el_smurfo:
That's weird, because I rarely use my USB to transfer files, and certainly haven't since installing CM10...All the files were already there when I installed the ROM. I ran a forced media scan and tried to snip some bits of logcat that seem relevant to me...the words "workaround" and error popped out, but I don't know enough to judge

I/ActivityManager( 561): Start proc com.addz.mediascanner for activity com.addz.mediascanner/.ScanActivity1: pid=12651 uid=10088 gids={1028}

I/dalvikvm(12651): Turning on JNI app bug workarounds for target SDK version 4...

W/NetworkManagementSocketTagger( 561): setKernelCountSet(10088, 1) failed with errno -13

E/Trace (12651): error opening trace file: No such file or directory (2)

W/ActivityManager( 561): Permission denied: checkComponentPermission() owningUid=10014

W/BroadcastQueue( 561): Permission Denial: broadcasting Intent { act=android.intent.action.MEDIA_MOUNTED dat=file:///storage/sdcard0 flg=0x10 } from com.addz.mediascanner (pid=12651, uid=10088) is not exported from uid 10014 due to receiver com.android.providers.downloads/com.android.providers.downloads.DownloadReceiver

I/ActivityManager( 561): Start proc android.process.media for broadcast com.android.providers.media/.MediaScannerReceiver: pid=12668 uid=10014 gids={1015, 1023, 1024, 1028, 2001, 3003, 3007}

E/Trace (12668): error opening trace file: No such file or directory (2)

W/MediaScanner(12668): Error opening directory '/storage/sdcard0/.android_secure/', skipping: Permission denied.
[HTC One S] OSCARIBANYEZ:
I stopped having problems when uninstalling applications you test purchase ... and you can play photo
[HTC One S] eckbauer:
I don't know enough to judge also,maybe one of the Devs can make more out of it.But i am happy my work around worked for me.
[HTC One S] itsmikeramsay:
Could very well be permissions are being denied to the SD Card. Looks like that's what I'm reading here lol. Might be the reason applications won't see it, but its weird file managers can though. So the SD Card is present, but may not be mounting so media apps can read it's data...

But for others like me it works, and some are using alternative apps which work....seems more so on the /system/app or something along those lines....Just thinking out loud lol
[HTC One S] el_smurfo:
It does seem like something along those lines but permissions for sdcard can't be set by the user. The line about .android_secure plus the comment from OSCARIBANYEZ about uninstalling applications you "test purchase" has me wondering if this isn't somehow indirectly related to the problems with paid apps on JellyBean in general. Maybe the media scanner gives up after being denied permission to .android_secure for some folks?
[HTC One S] djsubtronic:
This could be. But that doesn't explain the media scanner running for 36 minutes straight, building a database of about 11 MB, then closing. And nothing showing up in the gallery/music.

It's a mystery.
[HTC One S] el_smurfo:
Simply moving my notifications to /system/media/audio/notifications without changing the permissions of the individual files had them available on a reboot, so this issue appears to be totally localized to files on the sdcard.

There's so much storage wasted on /data, I wonder if folks could just put their music or photos somewhere there for now and have it work?