[Q] Audio issues since upgrade - HTC One SV

Hello all,
Ever since updating to the leaked release of JB for the One SV (with the, at the time, newer sense) I have had in-call audio issues. This was a known issue at the time, and I flashed back to an older release (the default, factory one).
But since I have upgraded to ViperSV 1.1.0, the issue is back. I've seen people talking about different kernels and such, but I have no idea how to do so. I have re-flashed the boot.img contained in the ViperSV 1.1 ZIP file, but this has not resolved the issue.
Any ideas how I can get my in-call audio back?
(I am using the non-lte european HTC One SV)
Thanks in advance!
- Kyentei

Need to update your firmware in respect to your current available android OS.
Sent from my C525c using Tapatalk

Related

[Q] Darkforest Stuck At Beats Logo?

Hi
I've just tried to do a install of the Darkforest custom rom - version 6.1.0.
Im running Hboot 1.27.1111 and am S-OFF I'm using the clockworkmod recovery
I've installed the update.zip via clockworkmod and the rom seems to have installed okay - i've done the superwipe etc too - but now when i turn the phone on it starts to load upto the beats logo and then doesn't get past that point?
Anyone have any answers for me please?
The only answer I've got is: I have tried flashing it last week, had the same problem, couldn't solve it and used another ROM.
Every ROM works fine on my device, but Darkforest didn't.
install 4ext recovery and try to flash it again.see if it works
best wishes
Guys, please read maybe the last 4-6 pages on the thread. Known issue and I've only had a sensation for 4 days now (and 2 of them don't count because I've been at work or out) meaning I haven't had a chance to debug it yet. Latest stable version is 6.6.0
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
I actually have similar problems
Hello. Actually, I'm having very similar problems as you. In my case, after trying all combinations of custom ROMs (dark forest included) firmwares, etc, I'd found that I'm unable to boot ANY sense-based rom, even though they all successfully install without any issues. I then attempted to install aosp and aokp based roms and to my surprise, it worked flawlessly! I know for a fact it's not a software or installation issue because I repeated each attempt on my sister's Sensation 4g and it had zero problems my particular phone experienced. As of right now, I'm totally stumped as to why this is happening, but I guess I'm lucky that I could still function running Touchcream 2.1 or CM9. Please try more combinations of roms and fw to see if you're having similar problems. If you do, then there's a possibility that we're having hardware issues.
roccatkone said:
The only answer I've got is: I have tried flashing it last week, had the same problem, couldn't solve it and used another ROM.
Every ROM works fine on my device, but Darkforest didn't.
Click to expand...
Click to collapse
Hi thanks for the reply - I'm in the same boat too I've just installed the viperS ROM and worked fine first time so must be something up as Jonny has nicely pointed out - i'll stick to this ROM untill i see an update from Jonny on his thread.
Many thanks

Roms that work with T-Mobile htc one s

I started this to see if anyone can list a few ROMs that work with T-Mobiles htc one s. Please help by listing the ROM you are on and by saying if the ROM has any issues; such as WiFi not working for example.
Sent from my HTC One S using xda app-developers app
I'll be first
Cm10 nightly- works excellent but it takes WiFi about 5 mins to kick in after I toggle it. If any one knows how to fix it please reply to this post
Sent from my HTC One S using xda app-developers app
I've been using $droyd$'s AOKP 4.2.2 ROM and the only issue is that as of right now, you can't record in 1080p. Other than that, its very smooth and fast.
Also if you were unaware before, wifi-calling doesn't work on any jelly bean rom.
Good luck!
Sent from my HTC One S using xda premium
tjsinghlion said:
I started this to see if anyone can list a few ROMs that work with T-Mobiles htc one s. Please help by listing the ROM you are on and by saying if the ROM has any issues; such as WiFi not working for example.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
WIFI issues are a nuance of this phone and the tmobile seems to be the most affected - it's different for each access point, user, phone, rom and firmware. In short you'll have to try it.
My tmobile worked with wifi on CM10 and CM10.1, it would not work with Viper until I downgraded my hboot (partial s-off enables some firmware write access) and flashed my wifi firmware. It get's interesting - I then put the old firmware back and the wifi still worked!!
Did you see the S-OFF thread? This will enable you to flash the radio firmware which will solve any problems.
Remember your WIFI channels - different countries use different range of channels and some access points 'helpfull' set the channel automaticlly. I have many devices that cannot cope with channel12.
Not trying to be a buzz kill here, but what's the purpose of this thread? I mean the Dev section is right over there, and the first page is flowing with fully working or close to fully working new ROMS.
Just saying.
I see what your saying. But honestly when you go through the a certain ROMs thread, they never say how WiFi doesn't work on T-Mobile phones. Or any of the problems Tmobiles users face.And who wants to go through a thread having to look for that one specific detail about a ROM whether or not to see if WiFi works. Also when looking through these ROM threads you find people that just like to say thank you (which there is nothing wrong with) that fill up the pages, making it harder to know if everything in that ROM is really going to work on your tmobile HTC one s, because people do search through comments to see what the users say. Therefore I made this thread for all T-Mobile users who want to post and say whether their ROM they are using works perfectly or if they are experiencing problems. And who wants to go through the process of flashing a new ROM without even knowing whether something like WiFi works. So yeah that's why i made this thread
Sent from my HTC One S using xda app-developers app
I get that, ROM posts can be a little all over the place sometimes. I didn't understand at first; I'm one of the few T-Mo users with pretty much no problems. It also doesn't help that the ROM database that some guy did in the Dev section hasn't been updated for some time.
Thankyou
skyline93r34 said:
I've been using $droyd$'s AOKP 4.2.2 ROM and the only issue is that as of right now, you can't record in 1080p. Other than that, its very smooth and fast.
Also if you were unaware before, wifi-calling doesn't work on any jelly bean rom.
Good luck!
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Ok thank you. Now i think im going to go Flash that rom. And also did you do anything specific to get your wifi working. and what Hboot are you on
If you are S-ON and have high HBOOT and want a Sense-based ROM with working WiFi, you were looking at TrickDroid 7 (TMOUS based), Unknown Retribution, and I think one more (Energy Blue, IIRC) that were based on recent updates. Since they were all based on the TMOUS ROM, everything should work without doing anything super special, including WiFi-calling. Virtuous Ville+ also had working WiFi, but no WiFi-calling. Recent CM 10.1 nightlies are working really well. At least, those are the ROMs I've used.
ardax said:
If you are S-ON and have high HBOOT and want a Sense-based ROM with working WiFi, you were looking at TrickDroid 7 (TMOUS based), Unknown Retribution, and I think one more (Energy Blue, IIRC) that were based on recent updates. Since they were all based on the TMOUS ROM, everything should work without doing anything super special, including WiFi-calling. Virtuous Ville+ also had working WiFi, but no WiFi-calling. Recent CM 10.1 nightlies are working really well. At least, those are the ROMs I've used.
Click to expand...
Click to collapse
Wait are you saying that Recent cm10.1 nightlies have wifi working on our device. and by wifi working i mean it automatically turns on, and not just hangs and turns on later .
I haven't had any WiFi hangs.
I just started using Liquid Smooth. Pretty nice IMO. The only issues I've notcied were a bluetooth hang that fixed after a reboot, and Voice search keeps crashing.
ardax said:
I haven't had any WiFi hangs.
Click to expand...
Click to collapse
so let me ask you a question. What radio are you on. And also what HBOOT version are you running
tjsinghlion said:
so let me ask you a question. What radio are you on. And also what HBOOT version are you running
Click to expand...
Click to collapse
Right now I'm on Viper 2.1.0 with the full firmware from the 3.16 WWE OTA -- I only made that jump because S-OFF makes it easy to switch without having to downgrade HBOOT. So HBOOT is 2.15 and Radio is 1.11.50.05.28. But I've just started using that and can't give you much in the way of impressions on WiFi stability yet. Just flashed it last night and didn't have any WiFi problems downloading my apps last night or weather checks this morning.
Before that I was using a recent CM 10.1 nightly on the TMOUS 2.35.531.10 firmware. So HBOOT 1.14 and 1.11t. I ran that firmware combination from shortly after its release until flashing Viper. ROMs in use were either CM 10.1 nightlies or Unknown Retribution (TMOUS 2.35 based).
ardax said:
Right now I'm on Viper 2.1.0 with the full firmware from the 3.16 WWE OTA -- I only made that jump because S-OFF makes it easy to switch without having to downgrade HBOOT. So HBOOT is 2.15 and Radio is 1.11.50.05.28. But I've just started using that and can't give you much in the way of impressions on WiFi stability yet. Just flashed it last night and didn't have any WiFi problems downloading my apps last night or weather checks this morning.
Before that I was using a recent CM 10.1 nightly on the TMOUS 2.35.531.10 firmware. So HBOOT 1.14 and 1.11t. I ran that firmware combination from shortly after its release until flashing Viper. ROMs in use were either CM 10.1 nightlies or Unknown Retribution (TMOUS 2.35 based).
Click to expand...
Click to collapse
noob question- What do you mean by TMOUS 2.35 based. And how does that affect the cm10.1 nightly
I mean ROMs that were built using T-Mobile US's 2.35 ROM as a base. Other Sense-based ROMs, like Viper, start with different ROMs as a base. The different Sense bases are part of the reason people run into WiFi problems when using ROMs originally created for other regions.
CM 10.1 has an entirely different heritage so it has its own ways of dealing with those issues.
tjsinghlion said:
Ok thank you. Now i think im going to go Flash that rom. And also did you do anything specific to get your wifi working. and what Hboot are you on
Click to expand...
Click to collapse
I'm on hboot 1.09 and the wi-fi worked right from the start.
p.s. sorry for the slow reply
Gotta Tell you the Viper 2.1.0 rocks...its fast awesome battery life and its got working wifi...not wifi calling but just wifi in general...it honestly is the best sense ROM...I have tried CM 10, Virtuous Ville+, P.A.C Man and even the ICS ROMs and I gotta say the Venom team makes an awesome product...:laugh:
"[rom][S4][15FEB]Updated_4.2.2_AOKP-Working-video" seems to work great with TMOUS hboot 1.14, added the new camera (in the post) with photosphere, The only little bug I found is the bluetooth doesn't list station info on my car stereo. I saw a tearing fix using bubba kernel, but I'm just living with it for now. Everything else seems to work great!
I just flashed the LiquidSmooth JB ROM from Droyd and this thing is amazing.. Coming from a rooted Stock Sense there really is no comparison, I might give Viper a try but this is clearly gonna be my daily driver

Data disconnecting only on Sense Roms

So I decided to flash cm Rom to see if my data would stop disconnecting. And it worked. Had data without any problems.
But when I went back sense data started to disconnect again.
Any opinions?
Sent from my HTC One S using Tapatalk 2
No-one ?
Sent from my HTC One S using Tapatalk 2
First thing that comes to mind that it might be a radio issue. CM for example uses 1.08t version of the radio as stock JB (and Sense roms based on that) use a newer version (mine seems to be 1.11). Kernel is also a possible troublemaker in these kind problems. Could you give some more details? Which roms you're trying?
Sent from my One S. Please hit thanks if I helped.

Manual Fix for Known 4.2.2 Audio Crackle?

Hi all,
I have been updating my wife's Infuse with the unofficial CM10.1 build by Scott. When I first installed my wife's 7/14 build (CM10.1, JB 4.2.2) we have NOT experienced any audio crackling. Several nights ago, my wife encountered the crackling noise in videos she's taken using her camera.
I know the issue has been fixed in 4.3, but since this is the first 4.3, I am not very sure that my wife will be able to deal with a few instabilities here and there (which has been the approach I've been following for my wife's installations; waiting a month or so for each version until it stabilizes a bit).
My question is: Is there a manual way of fixing the audio crackling issue (change a setting, edit a config file, flash a ZIP, etc.) that I can perform in the 07/14 build? Or is it a code change and I'm SOL?
Thanks in advance!
dashrendar said:
Hi all,
I have been updating my wife's Infuse with the unofficial CM10.1 build by Scott. When I first installed my wife's 7/14 build (CM10.1, JB 4.2.2) we have NOT experienced any audio crackling. Several nights ago, my wife encountered the crackling noise in videos she's taken using her camera.
I know the issue has been fixed in 4.3, but since this is the first 4.3, I am not very sure that my wife will be able to deal with a few instabilities here and there (which has been the approach I've been following for my wife's installations; waiting a month or so for each version until it stabilizes a bit).
My question is: Is there a manual way of fixing the audio crackling issue (change a setting, edit a config file, flash a ZIP, etc.) that I can perform in the 07/14 build? Or is it a code change and I'm SOL?
Thanks in advance!
Click to expand...
Click to collapse
The problem is caused by viper audio. You'd need the app removed and the lib file...it would have to be built without it included ahead of time.. If you have to stay on 4.2.2 downgrade to the first version without viper. If you don't care then just update to 4.3
Sent from my SGH-I997 using xda premium
FauxAffliction said:
The problem is caused by viper audio. You'd need the app removed and the lib file...it would have to be built without it included ahead of time.. If you have to stay on 4.2.2 downgrade to the first version without viper. If you don't care then just update to 4.3
Click to expand...
Click to collapse
When you say it would have to be built without it ahead of time do you mean this isnt a modifcation that can be made once the rom is installed?
I would like to use Unofficial CM10.1 - 4.2.2 - 7/14/13 version of this rom http://forum.xda-developers.com/showthread.php?t=1776129 and not have choppy audio.
I cant upgrade to Unofficial CM10.2 - 4.3 - 8/5/13 because -
Cannot send or receive MMS because of crashing mms aplication
Front facing camera images with high ambient light crashes the camera (crashes or freezes whichever app your using)
Cannot use Titanium Backup to "modify" system applications (a bug in Titanium that only happens on Android 4.3)
Thanks for your help
braschlosan said:
When you say it would have to be built without it ahead of time do you mean this isnt a modifcation that can be made once the rom is installed?
I would like to use Unofficial CM10.1 - 4.2.2 - 7/14/13 version of this rom http://forum.xda-developers.com/showthread.php?t=1776129 and not have choppy audio.
I cant upgrade to Unofficial CM10.2 - 4.3 - 8/5/13 because -
Cannot send or receive MMS because of crashing mms aplication
Front facing camera images with high ambient light crashes the camera (crashes or freezes whichever app your using)
Cannot use Titanium Backup to "modify" system applications (a bug in Titanium that only happens on Android 4.3)
Thanks for your help
Click to expand...
Click to collapse
No, it unfortunately isn't something you can modify on your own. As far as the MMS crashing problem I saw a commit earlier by slimroms that fixes that so Scott will probably add it in by the next build. The other problems will also be fixed in time, 4.3 hasn't been out long...just give it time
Sent from my SGH-I997 using xda premium
Is it possible for someone to create a zip containing the audio crackle fix that can be flashed via CWM? Or is that out of the question?
If someone can pinpoint the library that needs to be updated and with what version (i.e. grabbing a version from a later build), I can look into how to create a flash-able zip to fix the issue. I would appreciate it even more if someone else did it.

[Q] Beanstalk OTA Update

I have been a user of Cyanogenmod on my Verizon Galaxy S3 for a while now. I'm what most would call a newbie as far as android tech flash custom rom stuff. But I can get around...
My question is I just flashed Beanstalk and everything seems good so far. Loveing 4.4 (why I switched from Cyanogenmod) I get an OTA notification about a new version of Beanstalk but the numbers don't seem to be NEWER.
Current Beanstalk: 4.4.215-20140117-d2vzw
Update Version: 4.3.1009-20131016-d2vzw
Doesn't make sense to me, is there something wrong with the OTA app, or are they falling back to a previous version for some reason...anyone with info or help. Thanks!
I noticed the same thing. I believe the OTA updater may be broken or not updated. You have the latest build.
I get the same thing here
Been getting this since installing beanstalk that included the beanstalk OTA app....love the idea of it but it looks like the OTA app is broken or beanstalk is reporting itself as the wrong version.
I am running the most current 4.4.285 i believe but yet i get update notifications that new versions are available.
The "new" versions message i get is:
2 updates available for download
Beanstalk-4.3.1015-20131227-d2att.zip
Beanstalk-4.3.1009-20131015-d2att.zip
anyone figure this out as i am getting these older versions but not an actual new versions (and newer did exist while getting this message)?
When I was using beanstalk it was the same issue it would warn me of a lower version update. I don't know why it seems like to do that but just ignore it
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
ShapesBlue said:
When I was using beanstalk it was the same issue it would warn me of a lower version update. I don't know why it seems like to do that but just ignore it
Click to expand...
Click to collapse
Me too. The only AOSP ROM I've ever used that actually had a working OTA updater was C-ROM.

Categories

Resources