yashsingh1/xdaforums huggingface dataset:
[HTC One S] el_smurfo:
It is wiped. There are scripts in system/addon.d that back up an files and libraries needed. You can add to these scripts to backup other files yourself. I recently added Google Plus and all related libraries to the script, as G+ needs to be system app on rooted phones for location (i.e. latitude) to work right.

---------- Post added at 09:25 AM ---------- Previous post was at 09:24 AM ----------

I only have slight heating in low signal areas and no reboots. What is your batt temp when it's getting hot?
[HTC One S] ponchofiesta:
It is. And I have to flash gapps every time.

Short example: flash a sense ROM and flash a CM ROM. If it wouldn't be wiped, you would have some sense apps in /system.
[HTC One S] yz250il:
Can anyone confirm a 1 sec to 2 sec lag when turning the screen (not unlocking the device)?
[HTC One S] machoman1337:
It's been around since the original move to the 3.4 kernel.
[HTC One S] yz250il:
I thought so my last CM10.1 nightly was 3/12/13 I guess I'll go back then.
[HTC One S] ernestnwanu:
The latest nightly relies fully on the hboot radio. All good here
[HTC One S] Lone Shepherd:
Is there a primer on what S-ON / S-OFF means (theory/practice) as well as all the SuperCID talk and what not? I am a bit lost as to the ramifications of these things.

Also, recent builds for me have had very flaky network connections (would often cut out for extended periods). I flashed 7/15 and have no network connectivity at all (wifi or cell). As I am S-ON, do I need to flash something else separately via fastboot? If so, how do I know when this is needed and when it is not?
[HTC One S] machoman1337:
S-ON -> You need to fastboot flash the boot.img.

If you already know about the boot.img, I have no idea what the problem could be.

S-Off stands for "security off" and basically allows certain rooting-related procedures to be permanent. I highly recommend going S-Off as it saves a few steps every time you want to flash an update. It's very easy and totally worth it. As for SuperCID, that is just part of the procedure for going S-Off. We already have quite a few posts in this thread about problems related to people forgetting to do something while S-On, whereas if they had been S-Off they wouldn't have had to worry.
[HTC One S] kalapyu:
Hey,

On 0715.

Wifi can be turned on using the switch but it does not find any network! Am i the only one? (Did a cache and davlick swipe after install)

Thanks

K

PS: SMS is working fine this tome :)
[HTC One S] Twist79:
21.05.2013 is the last build with the old Kernel and without all the bugs...after a complete wipe I can confirm this now...

I can recommend bubba Vn6 Kernel with this build...everything works and the battery last very long...
[HTC One S] mo976:
The only way to get it to default to the firmware radio is by doing the system wipe prior to flashing the ROM otherwise as you pointed out certain things are saved when it "wipes" the system.
[HTC One S] horno46:
Yes, I had to do a factory reset before installing ROM do get it to use boot loader radio.
[HTC One S] PeQuEsan:
So backup script saves installed cm radio, along with gapps and other things? I'll take a look... Good point.

BTW, I've got same mobile data drops as with temporary radio. No one said the opposite, but I had the hope... :(

Desde el móvil, con Tapatalk...
[HTC One S] el_smurfo:
No, backup script does not save CM radio...it used to be bundled with each ROM and now (as of 7/15) is not (file is 20MB smaller). That's why you needed to flash each time (or make a backup script yourself). Running the 7/15 and all is well...using my firmware radio partition of 1.13 and fast.dormancy=2 and no drops for me, just like before.

---------- Post added at 01:59 PM ---------- Previous post was at 01:57 PM ----------

Radio was never "saved"...it was written with the ROM each time. 7/15 now uses firmware radio version, no wipe required.
[HTC One S] PeQuEsan:
But you said you had some drops... Less after new build.prop edits and 1.13 radio, but you still had them

..

I'm on 1.15 radio, and similar build.prop edits... :(

Desde el móvil, con Tapatalk...
[HTC One S] el_smurfo:
From the Man himself

---------- Post added at 02:01 PM ---------- Previous post was at 02:00 PM ----------

I've probably had 3 in a week's time where before I was having 3 an hour. I had at least this much trouble with Sense ROMS, but they don't have the handy blue signal icon to tell you it's happening.
[HTC One S] yz250il:
Thanks, I'll give bubba Vn6 a shot.
[HTC One S] evil89:
Excuse me, maybe I'm asking a dumb question. How is the unbundled radio going to influence the installation or the upgrade of the nightly?

I mean, before I used to

1) copy the rom in the sd root

2) wipe cache and dalvik

3) flash the rom

4) reboot to bootloader and flash the boot.img with fastboot

There is now a new command I should enter with fastboot? And regarding what file?
[HTC One S] el_smurfo:
Nope...that's it...it will use the radio shown in the fastboot screen. BTW, try FlashImage GUI if you want to free yourself of fastboot (apps section).
[HTC One S] eypostel:
Baseband not working anymore - help desired

Hi together,

I had some stability (sudden reboots with reboot loop) issues with the latest nightlies so I updated to 20130714. With this version, WiFi did not work anymore. I tried a lot of things to get it working again, also deleting the modem* files in /system/etc/firmware.

Now the whole connectivity part is not working any more (WiFi and phone module) and the version info of baseband is "unknown".

I then tried to go back to an older version which is known working on my phone, but baseband still is not working. I also tried going back to CM 10.0, but it did not boot properly (stuck in boot logo). This is probably due to HBOOT 2.15 which is too new for CM 10.0?

Do you have any idea what I can do to bring my phone back to a working state?

I would either be happy with CM 10.0 (so any hints regarding a proper HBOOT would be welcome) or a working CM 10.1.

Thank you very much!

Best regards,

Marc
[HTC One S] el_smurfo:
Fastboot flash boot.img
[HTC One S] eypostel:
Thanks, but I'm doing this already always with the proper version after flashing an image.

But anyway, it says Kernel 3.4.49 in the system info, while I thought that the newer nightlies should be back to 3.4.10?

Can there something go wrong when flashing boot.img although fastboot says everything went fine?

I also tried wiping the system partition before flashing a new ROM.
[HTC One S] el_smurfo:
Something definitely wrong. Wrong kernel explains it all. Try flash image gui...different method of flashing boot.img from android, in case your driver is corrupted.

http://xdaforums.com/showthread.php?t=1954121
[HTC One S] $droyd$:
Yup new kernel is 3.4.10.... Did you remember to pull the kernel from the zip before you fast booted.. You probably flashed an old kernel hanging out in your drive.. If fast boot said its good and your phone booted then you flashed one....
[HTC One S] kalapyu:
Hi all,

I screwed something. Pretty much the same issue as Marc and I need some clarification...

Got a HTC one S rooted, with SOFF in HBOOT 2.15

Installed the latest 20130715 CM version and experienced reboots (ending in bootloop) + wifi issues (could turned wifi ON but the device could not find any network).

I figured out (reading all the posts here) it was a kernel issue.

So i downloaded the bubba_kernel-11Jul.zip here http://www.androidfilehost.com/?fid=23043426517778617

Extracted the boot.img file in the sdk\platform-tools folder.

Launched fastboot and fired "flash boot boot.img" command

It sent and flashed properly: I now read 3.4.49.Bubba-g342a046 in the "about phone" screen

BUT i cannot access any wireless network and cannot turn wifi ON.

I am sure i did something wrong... Could you please help and advise?

Thanks !!
[HTC One S] NQNH:
did you tried a clean install?

wipe everything (system, data, caches) 2-3x times and then flash the rom zip, no need for flash boot.img if you are s-off. then flash gapps, clea cache again and boot.

if you experienced any issue, first try a clean install
[HTC One S] kalapyu:
thanks for your answer.

But which kernel should i install??

3.4.49 here http://www.androidfilehost.com/?fid=23043426517778617

or Vn6 here http://www.androidfilehost.com/?fid=22979706399756504

Did i flash properly?
[HTC One S] ponchofiesta:
The mythos to have everything wiped multiple times is somewhat funny :D

This is not like playing jenga. If you wipe, it is wiped!
[HTC One S] djsubtronic:
I have said the same numerous times, but like religion and astrology, some things will always remain.
[HTC One S] NQNH:
^^ so wipe everything once! sry for letting you make more work as usefull

---------- Post added at 12:37 PM ---------- Previous post was at 12:36 PM ----------

try the stock kernel first.. the kernel which comes with the cm 10.1 zip and see if wifi works.
[HTC One S] kalapyu:
lol :)

I did ONE and ONLY one swipe (system, data and cache) and reinstalled CM and Gapps.

-> I can access 3G :)

-> I can turn wifi ON and I see some networks but the desappear after a few secs. Weird.

Still not clear on kernel. Now it says 3.4.10.

Should I keep this one? Try another one? Where is the one from the CM 10.1 zip?? in the cm-101-20130715-NIGHTLY.zip folder??
[HTC One S] NQNH:
The 3.4.10 is the cm10.1 one.
[HTC One S] kalapyu:
perfect then :)

So when i install a CM nightly, it updates automatically the kernel?
[HTC One S] NQNH:
it automatically installs the kernel which is integrated in the nightly, so yes ;)
[HTC One S] machoman1337:
Intervigilium's just added Widevine libs for S4-based HTC devices. I looked it up and it's some kind of DRM for web streaming. I wonder what's the impact?
[HTC One S] superbalza:
I was with 0602 nightly and started to have 2g-3g issues (when switching from 2g to 3g and viceversa, the connection drops and doesn't wake up). I tried to downgrade to 0521, but the issues remained.

I went on MIUI (no connection problems), then back on CM, 0523... the connection problem was there waiting for me :D

now: do you thing that doing a fresh install from 0523 to 07something (with new kernel etc) maybe will solve the problem? or if I have the connection issue, I will have it until some fix will be found?

I'm just asking before jumping the river...
[HTC One S] :
Got one of my crashes while playing Ingress, pulled my logcat this time around. It shows a few hundred of these:

D/QMI_FW ( 555): QCCI: QMI_CCI_RX: cntl_flag - 04, txn_id - 0000, msg_id - 0026, msg_len - 0045
D/QMI_FW ( 555): QCCI: reader_thread: Received 56 bytes from 240
D/QMI_FW ( 555): QCCI: QMI_CCI_RX: cntl_flag - 04, txn_id - 0000, msg_id - 0026, msg_len - 0031
D/QMI_FW ( 555): QCCI: reader_thread: Received 603 bytes from 240
D/QMI_FW ( 555): QCCI: QMI_CCI_RX: cntl_flag - 04, txn_id - 0000, msg_id - 0025, msg_len - 0254
D/QMI_FW ( 555): QCCI: reader_thread: Received 86 bytes from 240
D/QMI_FW ( 555): QCCI: QMI_CCI_RX: cntl_flag - 04, txn_id - 0000, msg_id - 0026, msg_len - 004f
D/QMI_FW ( 555): QCCI: reader_thread: Received 83 bytes from 240

Followed by a few hundred of these:

W/AudioTrack( 8116): obtainBuffer timed out (is the CPU pegged?) 0x604cb098 name=0x16user=00001000, server=00000000
W/AudioTrack( 8116): obtainBuffer timed out (is the CPU pegged?) 0x604c7648 name=0x6user=00001000, server=00000000
W/AudioTrack( 8116): obtainBuffer timed out (is the CPU pegged?) 0x5e08c948 name=0x7user=00001000, server=00000000
W/AudioTrack( 240): obtainBuffer timed out (is the CPU pegged?) 0x40023020 name=0x1user=0000160c, server=00000000
W/AudioTrack( 8116): obtainBuffer timed out (is the CPU pegged?) 0x61872c88 name=0xauser=00001000, server=00000000

with a few of these in here and there:

W/be ( 8116): playNextClip interrupted
W/be ( 8116): com.nianticproject.ingress.common.c.bo: acquireSoundPlayer too many sound players.
W/be ( 8116):	at com.nianticproject.ingress.a.a.a(SourceFile:69)
W/be ( 8116):	at com.nianticproject.ingress.common.c.be.j(SourceFile:619)
W/be ( 8116):	at com.nianticproject.ingress.common.c.be.i(SourceFile:596)
W/be ( 8116):	at com.nianticproject.ingress.common.c.be.h(SourceFile:546)
W/be ( 8116):	at com.nianticproject.ingress.common.c.be.a(SourceFile:196)
W/be ( 8116):	at com.nianticproject.ingress.common.c.ac.a(SourceFile:191)
W/be ( 8116):	at com.nianticproject.ingress.common.c.ac.b(SourceFile:325)
W/be ( 8116):	at com.nianticproject.ingress.common.c.q.b(SourceFile:22)
W/be ( 8116):	at com.nianticproject.ingress.common.c.ac.b(SourceFile:42)
W/be ( 8116):	at com.nianticproject.ingress.common.c.ae.a(SourceFile:273)
W/be ( 8116):	at com.nianticproject.ingress.common.f.c.call(SourceFile:299)
W/be ( 8116):	at java.util.concurrent.FutureTask.run(FutureTask.java:234)
W/be ( 8116):	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)
W/be ( 8116):	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573)
W/be ( 8116):	at java.lang.Thread.run(Thread.java:856)

I've got the full logcat kicking around if needed.
[HTC One S] machoman1337:
I'm guessing the crash happened as you were getting a GPS lock?
[HTC One S] :
Surprisingly, no. I'm indoors atm, so the GPS is turned off, and it's gets my location (successfully) via WiFi data. The lock-up happens after the game is left sitting open for a while.
[HTC One S] |RaVeR|:
Hello,

I was just looking around on the Jira bugtracker and I can't seem to find the one issue everyone on 3.4 seems to be having: the "resume delay".

Can anyone point me in the right direction?

Thanks
[HTC One S] machoman1337:
Ah yes, I think it's not actually the GPS, but rather the mode where you can turn the phone and the map rather than the marker turns at the same time (not sure how to describe it... compass mode?).
[HTC One S] :
Either or, it looks like an audio system is causing the lock-up. In that particular scenario, the phone just locked up for a while. I hit the home button, waited about 1-2 minutes, and she returned from Ingress to the home screen just fine.

A little while after that, it locked up and soft-rebooted anyway. Included in the logcat for that soft-reboot are 100+ of these:

D/AudioHardwareALSA( 3608): qcom.audio.init is set to
D/AudioHardwareALSA( 3608): Sleeping for 50 ms
[HTC One S] Lone Shepherd:
I did flash the boot.img when I got home, and that resolved the "no connectivity" issue, although I still drop connection a lot. I guess there's no way to know whether flashing boot.img is needed or not, other than keeping a close eye on the changelog?

Thanks for the info on S-OFF, I will see about getting that; it does sound like it makes things easier.
[HTC One S] el_smurfo:
I have heard a lot of people having problems with lockups and crashes while playing Ingress...Perhaps our phone just doesn't have enough RAM?
[HTC One S] :
I don't know if I'd say that... the game runs butter smooth all the time when it runs, along with the rest of the phone at that point. It's only when I trigger it, by say, leaving the device sitting there with Ingress on and screen-lock on. Or, re-open the back-grounded app after a bit of system instability.

It's great in CM10.0/sense, our RAM should be okay.
[HTC One S] machoman1337:
It was perfectly fine on my LG Optimus 2X with its paltry 512 MB of RAM.
[HTC One S] Lone Shepherd:
With the recent builds (starting 6-27) Angry Birds Space locks up on me all the time -- it will freeze for many, many seconds and then I will get the "app is not responding" message, if I say 'wait' the app is working again, but after that point the freezes become very numerous.

This was not a problem on earlier builds, so something is definitely screwy. Am considering going back to an old build from March until these issues (screen turn-on delay, data connectivity issues, in-game freezes, etc.) get resolved.
[HTC One S] superbalza:
I was with 0602 nightly and started to have 2g-3g issues (when switching from 2g to 3g and viceversa, the connection drops and doesn't wake up). I tried to downgrade to 0521, but the issues remained.

I went on MIUI (no connection problems), then back on CM, 0523... the connection problem was there waiting for me :D

now: do you thing that doing a fresh install from 0523 to 07something (with new kernel etc) maybe will solve the problem? or if I have the connection issue, I will have it until some fix will be found?

I'm just asking before jumping the river...

Inviato dal mio One S
[HTC One S] machoman1337:
I can't find the original CM10.0 (4.1) thread, so can anyone quickly clarify if the data drop issue existed on CM10.0 stable? Thanks.
[HTC One S] :
I recently tried it... I had drops, but in those days it was commonly needed (for me, anyhow) to try different radio zips to get a solid network connection. I'm on Telus, in Canada, and I have yet to see a data drop on CM10.1 with the bundled radio.
[HTC One S] intervigil:
Would appreciate a full logcat. The first snippet is normal, those are messages from the QMI libs. (used by GPS, radio, etc for IPC with the modem) The second one points to an issue with the media framework, specifically with the audio player. Does ingress do much with audio playback? (I never had an invite/don't play)
[HTC One S] :
Logcats sent in PM.

It has in-game background music, as well as specific audio effects when doing things in game, hacking portals, smashing portals, etc.

It never happens right away when opening the app, though, it's after the app has been running for some time, or has been backgrounded.

---------- Post added at 11:44 AM ---------- Previous post was at 11:42 AM ----------

If you'd like to try to reproduce the crash, I've got some spare invites, I can send one your way.
[HTC One S] djsubtronic:
I installed ingress today and played for a couple of minutes then minimised it. Opened it again a few times over the next few hours and each time played with it for a couple of minutes. I have experienced no crashes.
[HTC One S] maluus:
I want to share my experience about dreaded 3g data drop problem. I used 26/06 and 27/06 without problem. I also used 11/07 without problem. But both 14/07 and 15/07 have data drop problems. All of them with the same 1.15 europe radio firmware. I m back to 11/07 nightly. The ones I said without problem, are used for days (at least 3 days) in the same places where there are some low signal areas that I know. but the ones with which I had problems used for just one day and problem showed up already.
[HTC One S] :
Odd. Perhaps it's a combination of Ingress with some other system setting/application I have going, or it's that magical elf that varies our phones in unexplained ways.

I have seen the crash in other applications, all of which seem CPU/GPU intensive. I believe the two main one's for me are Ingress, and The Room. I also play Super Stickman Golf 2 (quite a bit lighter on graphics), and have never seen the crash in that one.

For reference, running TWRP 2.5.0.0, HBOOT 2.15, 20130715 nightly.
[HTC One S] PeQuEsan:
I've also never had problems with wifi and any cm10.1, but 14/7 has some random problems connecting to my usual wifi (home and work). You can fix it disabling / enabling...

Just my 2 cents... About data drops, more or less same problems with 14/7 and 5/7...

Remember that in 14/7 rom started to use radio partition...

Desde el móvil, con Tapatalk...
[HTC One S] eypostel:
You were right, after flushing boot.img from the correct ZIP file once again (20130706 nightly) everything works fine and Kernel and baseband version are consistent again.

Maybe I was too tired when trying to fix things late night... Maybe it's also not a good idea to use Android SDK and ROM files directly from a NAS share instead of copying files to a local drive.

Next time having trouble I'll also give Flash Image GUI a try...

One final question in case the reset/instability issues occur again: Is it possible with HBOOT 2.15 to go back to CM 10.0 again, or do I have to downgrade HBOOT? If yes, which version do you guys recommend?

Thank you very much for your help - glad that the phone isn't bricked :)
[HTC One S] djsubtronic:
I'm on HBOOT 2.15, TWRP 2.5.0.0, and 20130714. Can you describe the scenario that causes "The Room" to crash and I'll give that a try too.
[HTC One S] :
It's about the same for me with each game. Fire up, leave for a bit. It does seem random at times, for sure (it's most noticeable in Ingress because it takes up so much of my day lol), but sometimes I'll come back and she's completely unresponsive.

One thing you may like to try, set it for screen awake while charging in Dev Options, leave ingress open for a while (GPS on or off should be irrelevant, but leaving it on will boil your phone. I'll recommend leaving GPS off, wifi on) while you do other things. Pop back in once in a while, see if you notice lag/stuttering/complete freezing.

If you encounter any lag, but no crashes, try minimizing, letting the phone sleep a while, come back in and fire up Ingress. It's generally post-lag where the minimize crash will happen.
[HTC One S] dyndragon:
It did. I originally did some reporting of it when it was only CM10.0.
[HTC One S] djsubtronic:
Dunno if it was long enough but I let the app open on the map screen for about 45 mins with the screen awake aand experienced no lag.
[HTC One S] kalapyu:
I am on CM 20130715 (SOFF, HBOOT 2.15, kernel 3.4.10 that came with CM).

I could not turn mobile network or wifi on.

You recommended to perform a system, data and cache wipe + fresh install (CM + Gapps).

I did this and now have mobile network back :)

I can also turn wifi ON but the device does not find any network which is weird (i have tons of wifi networks arround me and can access them with my laptop and nexus 10)

Wifi is turned on but the network list is empty. Even when I hit "search" in the wifi 3 dots menu, nothing happens...

Help :/

and thanks in advance!

K
[HTC One S] NQNH:
just a guess.. but try to flash the boot.img which is inside the cm.zip via fastboot and boot again. just a try
[HTC One S] kalapyu:
thanks. Just did that and still the same issue.

The device "sees" one network (instead of 11 available arround me) and this network goes and comes back randomly and i can't access it :(
[HTC One S] Babaki:
ingress always crashes for me too
[HTC One S] djsubtronic:
Just played The Room for about ten minutes without crashes...
[HTC One S] Rugged96:
all this talk about wifi/data issues has me concerned. is there any reason i should update from the Jun 27 nightly? Has there been any other substantial changes?

I still have random data issues but that's it and it's a minor headache to me personally...
[HTC One S] NQNH:
you can see the changes here

http://changelog.bbqdroid.org/#/ville/next

and if you look a few pages back there is possible fix for the data issue.. fast dormancy = 2 etc.
[HTC One S] :
Your HOS is magic!! I'm really not sure at this point, tbh. It must be something specific some of us are doing, possibly something minor in settings.

Do you have a specific way you can reproduce this? I'm not the only one getting crashes, but I don't know why some of us will crash and some don't.
[HTC One S] MrThreeChains:
No single crash or reboot for me since 3 days plus WiFi works very well. Hope the new nightly comes out today because it got some s4 changes
[HTC One S] djsubtronic:
Although unlikely, I also wonder if there is some difference between the 20130714 and 20130715 nightlies since you said you're on 15, and I'm on 14.
[HTC One S] :
If I get some time today, I'll download the latest 20130714, run it with default CM options (without customizing the living daylights out of it) and see if my crashing continues . Generally I dump Trebuchet for Nova, along with a plethora of other customizations. I'll let ya know how it goes.
[HTC One S] djsubtronic:
I do the same (with Apex though). I delete a bunch of APKs before even flashing, and replaced the default Roboto font. But otherwise I haven't customised much else, the developer options and performance options are pretty much on default (except I have started to keep the CPU governor on performance mode now).
[HTC One S] Babaki:
start the game, play for a minute and then exit. after like an hour, my phone is completely frozen and i cant even power it on. also, the graphics are choppy and flashy the whole time.