yashsingh1/xdaforums huggingface dataset:
[HTC One S] mikereidis:
The crash is in the V4L FM driver I think. Same happens on my ATT OneX when I rename /system/lib/modules/radio-iris-transport.ko .

I hope xkonni can enable radio-iris-transport as a module for the kernel build.

Alternatively, try a kernel that supports the driver. The "Fusion Ultimate v1.0" kernel by klin1344 may include the driver: http://xdaforums.com/showthread.php?t=1837630

His CM9 kernel seems to; I can't tell with the CM10 kernel. (boot.img)

Hopefully this will at least result in RSSI readings, RDS, etc.

The next hurdle may be audio. I believe xkonni said on the CM9 thread that most FM functionality was removed from the audio libraries when trying to fix audio.

I had the same issue on CM10 for my ATT OneXL (same SOC). I tried to enable FM audio via ALSA, replicating the differences on a stock like ROM. I had no success, I think because audio transfer is digital, and some setup is needed for this.
[HTC One S] Dave77459:
I tried again, and yes, from deep sleep.

Sent from my HTC One S

CM-10. 1-20130709-NIGHTLY-Ville
[HTC One S] el_smurfo:
I always find this hilarious. It's a "nightly snapshot" that they deemed "stable". IMO, I'd call our build stable for my personal use...

FYI, finally had a dropout after two days of use with 1.13 radio and build.prop mods. It was a bit inconvenient as having some family issues, but since I'm using the phone so much, I just toggled airplane and was OK again.
[HTC One S] djsubtronic:
I think toggling data is a little safer, because sometimes I find turning on airplane mode renders the phone into a state where you can't come out of airplane mode without a reboot.
[HTC One S] el_smurfo:
Toggling data doesn't work for me and airplane mode never requires a reboot... Darn these phones are weird.
[HTC One S] b_ignatov:
Hello everyone.

I had my holiday for couple weeks and miss the threat too much.I see that in the last couple comments is talking about stable version....is it true??
[HTC One S] NQNH:
as far as i know the 10.1.1 stable is only for the devices which already got the 10.1.0 stable.. it will be like a fix.

but this doesnt affect us because we dont have an official stable version yet ...
[HTC One S] b_ignatov:
Thank you for your quick reply
[HTC One S] djsubtronic:
Wow, on the latest nightly I just scored 12,027 points in AnTuTu on interactive governor with MP4 music playing in the background. So I tried again on performance mode without any background music and got this rather pleasant score.
[HTC One S] yuan_1202:
The same as stock 4.1.1 sense 4+.
[HTC One S] RiffyDivine:
What settings did use?
[HTC One S] el_smurfo:
I have a /data/local.prop file with:

ro.ril.hsdpa.category=24

ro.ril.hsupa.category=6

ro.ril.hsxpa=4

ro.ril.fast.dormancy.rule=2

ro.ril.radio.svn=19

ro.ril.disable.power.collapse=1

I also changed the fast dormancy to 2 in build.prop as local.prop apparently doesn't modify read only parameters.

I have had one or two drops in 2 days... The rest recovered automatically.
[HTC One S] wwelles:
This resolved my issues with maps.
[HTC One S] djsubtronic:
What's the difference between fast dormancy 1 and 2?
[HTC One S] wwelles:
I've had this enabled for awhile on 2013-06-28, works fine although same 2 second delay as with power button.

---------- Post added at 10:35 AM ---------- Previous post was at 10:32 AM ----------

Are the wake delay and random reboots addressed in versions after 2013-06-28? What's changed since then?
[HTC One S] el_smurfo:
Only thing I know is that stock TMOUS supposedly uses 2. YMMV
[HTC One S] NQNH:
wake delay still exist.

one change is that you can disable widget pages on the lockscreen.

if you want to the changes google for "bbq changelog cm ville" or take a look here

http://changelog.bbqdroid.org/#/ville/next
[HTC One S] mo976:
I'm in Israel on Orange and I have had better signal consistency and no drops using fast dormancy on 2 then on 1. As you said YMMV. Its obviously carrier dependant so I would say people should try both and see what works for them.
[HTC One S] djsubtronic:
Today's nightly seems to boot up and load up homescreens/widgets much quicker. :confused:

Edit: oh nevermind. The phone was generally running much faster and smoother and I realised it was on performance governor. I wonder if keeping it on performance actually has an impact on battery life? Since it will be idle most of the time, and when the screen is off it will go into deep sleep mode regardless won't it? So really, by keeping it on performance mode, shouldn't you technically get a smoother experience with a negligible hit on battery... maybe even an improvement since I'm sure the governor polling and ramping the CPU loads/speeds is a choe in itself...?
[HTC One S] aegentirony:
i have changed fast dormancy to 0 ... With great results as well...No loss of signal now for three days :highfive:
[HTC One S] PeQuEsan:
About fast dormancy, if your operator doesn't support it then yes, it's good idea to disable it.

El_smurfo, I'd say all that ril settings are ro, so they should be in build.prop, shouldn't they?

Desde el móvil, con Tapatalk...

---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------

We didn't find an answer to that question in Tecardo's flashable radios thread.

Do you mean that today's nightly has changed default governor to performance, or did you switched to it prior to upgrade?

Desde el móvil, con Tapatalk...
[HTC One S] antaine:
Which nightly got the best battery life for now ?

Envoyé depuis mon One S en utilisant Tapatalk 4 Beta
[HTC One S] Ponchoman:
I can't activate wifi or hotspot in the two latest nightlies. What could that be?

Went back to the 07/04 nightly and it works.

Radio is 1.15, Kernel 3.4.49
[HTC One S] el_smurfo:
When this happens to me, a recovery cache clear fixes it
[HTC One S] djsubtronic:
I switched it earlier when I ran Antutu and must have forgotten to switch it back. I'm gonna keep it on performance for a few days and see how the battery life is.
[HTC One S] Ponchoman:
Thanks for the answer, but did not work.
[HTC One S] el_smurfo:
Um...I just noticed that you said you had kernel 3.4.49? AFAIK, the kernel was reverted to 3.4.10 some days ago. This must mean you are not properly flashing the boot.img along with your ROM?
[HTC One S] bunga bunga matze:
You haven't flashed boot.img via fastboot, right!?
[HTC One S] Ponchoman:
Thank you, that was the problem! Now it's working
[HTC One S] aegentirony:
i was having an issue last night where tethering worked good until i used an app....then data would not transfer....Any ideas???
[HTC One S] nickmv:
What radio do you have?

And what do you mean "it doesn't activate." You need to clarify a bit.

1. Is the checkbox greyed out?

2. If not, is it just not doing anything when you check it?

3. OR, is it checking, but you're unable to go anywhere?

Reason I'm asking is that only the 1.06 radio works for tethering with the screen off. It's possible you're trying it that way?
[HTC One S] ahoslc:
Would you guys consider this stable? My customer want's a CM 10.1 Rom and trying to figure out what one is most stable since I don't own the HTC One S.
[HTC One S] mo976:
It's decently stable but it has issues with data connection, wake up lag and battery life if you don't mind supporting it with ROM updates over the next few months as fixes and kernel improvements are merged then go for it.
[HTC One S] el_smurfo:
I'd say that it depends on why the customer wants CM10.1. If it's for the newest features such as Privacy Guard and the Google Voice/SMS integration, they will have to sacrifice a bit in the battery department. Everyone seems quite obsessed with the wake up lag, but it really doesn't bother me much once I got used to it.

The one disadvantage you will find is that you will probably have to do any updates personally. The latest CM10.1 requires hboot 2.15, so you will either need to SOFF or flash the boot.img separately with each ROM update.

If they don't want the latest and greatest, I think the 5/21 unofficial nightly was highly regarded as stable and good battery life, but without the smoothness you get with the latest kernel (including 100MB less free RAM and some screen tearing).
[HTC One S] YoMarK:
Not trying to be an ass, but is does not have data connection issues for me. I think it has something to do with radio/firmware/baseband in combination with specific providers. I have T mobile in the Netherlands, using radio 1.11. I'm s-on. No data issues at all....
[HTC One S] el_smurfo:
Yup...as usual with this phone, seems super sensitive and YMMV. Some folks had maps issues, some not. Some had radio issues, some not. I'm an HTC fanboy, but will probably switch to moto next phone after the drop in support (just on principle, not that it matters much to us right now)
[HTC One S] mo976:
I wasn't specifically referring to issues I have, my data is fine. But a quick read will show that plenty of users do have various problems. As el_smurfo said some people have issues that others don't.
[HTC One S] oliveko:
Can't find the local.prop file, where do i find it?
[HTC One S] el_smurfo:
Just make it. Still not 100% sure its supported, so if you don't flash much just edit build.prop
[HTC One S] oliveko:
Oki thanx for the answer!!
[HTC One S] Rugged96:
if you are S-Off do you still need to flash the boot img seperately?
[HTC One S] khan.orak:
No
[HTC One S] aegentirony:
Everyone should be soff at this point because of the hboot and just the general ease of flashing...all we have now is cm and the others who build for us ...this phone like a lot of great HTC phones is no longer supported
[HTC One S] el_smurfo:
meh. flash image gui is fine for me right now. flashing the firmware.zip to get to the 3.4 kernel was stressful enough.
[HTC One S] bunga bunga matze:
Hm, for me its not a big deal to flash rom in recovery and boot.img by fastboot.exe......

And I cant discem the big benefits from s-off...::rolleyes:
[HTC One S] cdrom1028:
HA, I like to flash when I'm leaving work before the commute and the long delay in traffic with no computer around. Also its just nice to not have to deal with the extra step. Besides S-Off takes like 10 min to do. So why not just make life easier. IMHO ... cheers :cool:
[HTC One S] Rugged96:
for me i felt despite the extra steps it was worth it to get super ciid and s-off just to get my HBOOT to 2.15 from 2.08 so I could flash these newer ROMs
[HTC One S] annndrewww:
I've been thinking of diving in to get S-Off this weekend. Last week I went through the headache of updating the firmware so I could hop back on the Nightlies Train. Where should I start?
[HTC One S] cdrom1028:
I had great success with Facepalm S-OFF, just read the instructions and it works great.
[HTC One S] tungers:
For this interested in best battery life with these nightlies, my best experience so far has been with the 7/11 nightly (don't forget to flash boot.img so the kernel is reverted to 3.4.1). I'm getting about 1-2% drain/hr with normal use. Besides lag in wake lock, everything else seems pretty stable.

Also, for those interested in using the new google voice sms integration with these new nightlies follow these instructions:

http://www.androidpolice.com/2013/0...-now-be-sent-through-the-stock-messaging-app/

Works like a charm for me. Just use root explorer to put the apk in the system/app directory and change the app permissions. Really happy I don't have to use the google voice app anymore!
[HTC One S] Hai96:
I didnt follow the last 4 days this thread, so my question: is the lockscreen lag fixed?
[HTC One S] djsubtronic:
You don't have to follow 4 days worth of the thread but at the very least read the last damn post!
[HTC One S] kalapyu:
Hi everyone,

My SOFF HTC One S is running 7/11.

Everything worked fine (besides the lockscreen lag ;) until I installed this afternoon the latest Google Play Music update (v5.0.1053J.731804)

After each song, the phone reboots (and keep rebooting) until I wipe cache & dalvik...

So after the wipe, the phone boots properly, I can launch the music app, play one song and then it goes to bootloop again until a new wipe.

Do you experience this too?

Thanks!!

Kala

Edit : does this with any song
[HTC One S] djsubtronic:
When it crashes and reboots, does it keep booting up to the lockscreen then rebooting again?
[HTC One S] kalapyu:
Yes. This is exactly what happens.

It boots until the SIM PIN CODE screen and reboots.

BTW, the rebooting is very slooooooooow (the spinning CM logo is lagging)
[HTC One S] djsubtronic:
I have had this happen a few times, but not from Play Music. It happened a few times when I opened up Google Maps and the phone crashed into a bootloop. But even cache/dalvik wipe didn't fix it for me. I had to wipe system and reflash the ROM and GApps.

I wonder if these are similar situations...
[HTC One S] kalapyu:
I can try this... So I go to Recovery, wipe Cache/dalvik and system, thn install the latest ROM and GApps from recovery?
[HTC One S] djsubtronic:
Basically, that is what I did. But I don't know what was causing Maps to crash, as a couple of days later they released the new Maps version which no longer crashes.
[HTC One S] kalapyu:
I will give it a try this weekend (or sooner if this behavior upsets me enough ;) )

Thanks for your answer!

Cheers

K
[HTC One S] :
I get crashes like this quite frequently, for me it's mostly caused by Ingress.
[HTC One S] :
No. Maybe you should come back in 4 weeks or 4 months.
[HTC One S] wwelles:
I find that after a crash that causes a reboot, you need to reboot properly or else the system is slow.
[HTC One S] machoman1337:
I can confirm this. It seems like a reboot caused by a kernel panic also results in the CPU being stuck at minimum frequency or something.

Anyway, intervigil's github shows that the only device-specific upcoming changes are related to MHL. No word yet on the lockscreen lag.
[HTC One S] mannequin:
regarding the data issue: i noticed that none of the build.prop really help in my case. no matter if they present or not, the signal never manages to reconnect (just displays the grey bars) after coming out of no signal zone (for example subway). it works perfectly coming out of deep sleep, etc but once you're in no signal zone, that's it, airplane mode is the only solution.
[HTC One S] kurtfimmers:
Same to me here. Tried all different combinations of build.prop changes and radio. Some are better than other but problem stays when switching from 2g to 3g or conning from zone without signal.
[HTC One S] Microphone:
For me, when I switch from 3G to 2G via Tasker, it helped to toggle the data connection off and on again.

Perherps it helps you guys. Great work from the devs anyway :thumbup:
[HTC One S] kalapyu:
Hey again

Installed 0712.

Big issue with sms : get a red triangle (error 1) for every SMS sent (they are actually sent but i get the red warning triangle for all of them and the app keeps displaying "sending...")

Went back to 0709 and works fine. Is there an issue with this build?!?

Btw, did what i was told to avoid reboot loops (wipe system + fresh install) and it worked (so far)

Thanks!

K
[HTC One S] el_smurfo:
Koush has been adding a lot of behind the scenes for his "babel" Google Voice / SMS integration and encryption stuff. Probably broke something temporarily.
[HTC One S] yooouuri:
There are some new commits about the kernel for our device!
[HTC One S] el_smurfo:
Just some SE Linux stuff, but im not smart enough to know how this benefits us

http://selinuxproject.org/page/Main_Page
[HTC One S] maluus:
doesn't seem related to the problems at hand.
[HTC One S] yooouuri:
Haha (sarcasm..)
[HTC One S] MrThreeChains:
Very satisfied with 2013-07-13 so far :good::good:

Way better battery life than with Sense 5
[HTC One S] PeQuEsan:
After using wifi hotspot last night, I left the phone charging and didn't switch off wifi hotspot. This morning I've found it boot lopping (going till sim unlock code)... I've had to do a manual reboot to stop it. Later I'll attach last_kmsg of last spontaneous reboot. There's a "reboot reason unknown" and a code that some dev may understand...

[ 7.300473] set_restart_reason: set restart reason = 776655aa

[ 7.305783] set_restart_msg: set restart msg = `Unknown'

Desde el móvil, con Tapatalk...
[HTC One S] Rugged96:
I had an unusual event yesterday....right at the exact moment i needed my phone to coordinate a link up at the airport it shut down and rebooted to the HTC screen where it got stuck.

I rebooted several times but nothing happened and then I decided to boot into recovery and wipe davlik/cache. Before I wiped though I discovered the ROM had been erased. I did a dirty flash of the ROM and GAPPS and things were fine but the whole timing was the issue.

has anyone ever had this happen before?

I'm still running CM 0627.

maybe it's time i update?
[HTC One S] frdd:
Seems CM-bundled firmware is out again in 20130713, back to using the firmware partitions on the phone.

https://github.com/CyanogenMod/andr...mmit/15f903aa65d69e48e3167302be729d1dde2e5a44
[HTC One S] el_smurfo:
Ugh.... Another push to SOFF. Wish he didn't do that...

Edit...guess I have 1.13 from the firmware update, so I'm not too upset...still loses a lot of flexibility though.
[HTC One S] phin586:
Lots of random reboots and a very hot phone. I am not S-OFF as I do not have a windows pc to get back to the default ruu. I did flash boot.img with fastboot. I wiped fastboot cache. Anyone have any suggestions?
[HTC One S] Michael1101:
Ok this means that the cm10 radio installer won't work anymore, right? And we need to flash radios light in sense based roms and the radio won't change if we flash new nighlties? To flash a new radio do we now need the radio installer from tecardo and select sense instead of cm? Will it work that way?
[HTC One S] el_smurfo:
Only if SOFF. Hboot 2.15 wont let you flash radio
[HTC One S] Michael1101:
Yes. I'm s-off. Thanks!
[HTC One S] horno46:
I think that it us still a temporary radio installer CM or Sense. That's what it said when I just ran it.

Edit

I think you need to download specific Sense installer from the thread. The one designed for HBoot below 1.13
[HTC One S] Michael1101:
Is this an effort to fix the disconnections when switching from 2g to 3g? I'm wondering if this will work.
[HTC One S] PeQuEsan:
That radio partitions usage change will be included in 14/7 nightly, NOT 13/7...

BTW, could it have some positive effect in data drops? Hopping is free, we say here in Spain.

Desde el móvil, con Tapatalk...
[HTC One S] XXMrHyde:
The Temporary-Radio-Installer is still working,

but I`ll add an option to delete the radio files at /sytem/...,

to be able to use the "HBoot" radio without installing the rom again.
[HTC One S] PeQuEsan:
I see 14/7 nightly still includes modem* files inside /system/etc/firmware... Now I don't know if I'm using temporary files or radio partitions... :eek

Can I just delete modem* files inside that path to fall back to radio partitions? Last time I tested rom wouldn't boot...

Desde el móvil, con Tapatalk...
[HTC One S] yuan_1202:
Sorry. Does it mean i have to get s off to use nightly now?
[HTC One S] mo976:
If we use the sense installer V6 will that work as well?
[HTC One S] XXMrHyde:
Yes, I done the same a few minutes ago, I deleted all files with modem in the filename, but i guess you only have to delete the "additional" files,

(all others will be "recovered" again after a reboot), but I can`t find them, because there are many similar called files).

After a reboot the radio changed to the "HBoot" one.

Yes, the Sense Installer will work as expected, too

Edit:

I guess the modem files inside the official zip will be removed in one of the next builds.

(I don`t be sure, but I guess with build 14/7 the radio files inside the zip are still used)
[HTC One S] ernestnwanu:
Which ones are the "additional" ones?
[HTC One S] XXMrHyde:
the ones without a number in the filename
[HTC One S] ernestnwanu:
So 3 files in total? (The ones that end with .mdt)
[HTC One S] XXMrHyde:
No, take a look in the temp installer zip, to get the right file names, I guess you have to delete about 30 files

Gesendet von meinem Nexus 4 mit Tapatalk 2
[HTC One S] ernestnwanu:
So all those in temp installer can be deleted from system/etc/firmware. (All that begin with "modem)
[HTC One S] XXMrHyde:
Yes, all files included in the temp installer zip have to be deleted at /system/etc/firmware

Gesendet von meinem Nexus 4 mit Tapatalk 2

Edit:

next time i have to take a look, before posting "without numbers", ;)
[HTC One S] ernestnwanu:
Hmm I took those out but they all returned after a reboot..
[HTC One S] el_smurfo:
My bootloader has radio 1.13, but 7/14 still boots with 1.11, so still using radio bundled with ROM.
[HTC One S] XXMrHyde:
Take a look at Baseband Version, it should changed to the HBoot radio

Gesendet von meinem Nexus 4 mit Tapatalk 2
[HTC One S] maluus:
I wonder something: I m s-off and I flash 1.15 europe through temporary-radio-installer (CM mode) after every nightly I flashed. Are these flashed over radio partitions when I m s-off or still in system files? I mean after radio firmware removed from nightlies, will my radio be 1.15 anymore (since last time I again flashed 1.15) or is there a different radio firmware which will become active unless I reflash 1.15 after flash CM nightly? in this case is there a positive difference if I don't flash 1.15 and let it use other (if there is of course) radio?
[HTC One S] PeQuEsan:
Ok. I've erased all (28) modem*.* files inside /system/etc/firmware (with Aroma file manager, also you could use TWRP file manager) and after a reboot, all 28 files are back on /system/etc/firmware, but also some other modem_f1*.* and modem_f2*.* files... ANYWAY, ROM has fallen back to my hardware radio partitions, so I'm on EU 1.15. Good.

CM Radio Installer always writes to /system/etc/firmware, regardless you are s-off or not.

bye!
[HTC One S] intervigil:
Please stop using the radio installer that's floating around. It will no longer work. The relevant radio files in /system/etc/firmware are symlinked from /firmware_radio (the radio partition) (and will be re-symlinked) on boot now.

Also front facing camera facial detection will no longer cause a crash.
[HTC One S] NQNH:
I tried to delete the files too, but after the reboot they aren't back. and I have no baseband, neither the cm one nor the bootloader one..

had to restore the modem files from the cm.zip.
[HTC One S] |RaVeR|:
Intervigil, are you aware of the option in the radio installer to install for Sense? As mentioned a few posts ago, that might still work.

Or am I wrong?
[HTC One S] PeQuEsan:
Sense Radio Installer (v6) is still working as it should. What intervigilium, says is that modem*.* files inside CM are now symbolic links to radio partition.
[HTC One S] horno46:
Flashed 14/7, baseband is still 1.11 but bootloader says 1.15?
[HTC One S] djsubtronic:
+1 same here.
[HTC One S] PeQuEsan:
Read above please... firmware files are still bundled. You must delete them to fall back to radio partition. At least that's what I did with nightly 14/7 also.
[HTC One S] horno46:
So its a bit of a halfway house at the moment?
[HTC One S] PeQuEsan:
That's what I understand, but intervigilium could confirm... He has prepared it so CM10.1 uses radio partition (mounting it and symlinking at boot time from /system/etc/firmware), but old CM radio files are still there...

EDIT: This entry in intervigilium github seems that deletes radio files:

"PROPRIETARY_VENDOR_HTC 2013-07-13 08:24:30

s4-common: remove modem and q6 firmware"

So may be I was wrong.
[HTC One S] Stainless7221:
Is it work in progress to leave the files out by default? Or is it gonna stay like this ?
[HTC One S] highKo:
i dont have this version difference.

but i always wipe system + cache, so it isnt that "dirty"
[HTC One S] phin586:
Finally S-OFF'd my phone.. Did a fresh install and I am still getting overheating and random reboots... Anything I could provide that could help you guys out?
[HTC One S] ponchofiesta:
AFAIK system and cache is wiped automatically when flashing CM. So it makes no difference.
[HTC One S] djsubtronic:
System isn't fully wiped, otherwise you'd have to reflash GApps every time.