Related
New here, dont think this has been brought up. Has anyone else had the problem where music played in android sounds like its been sped up? It has a high pitch and the song seems to be a couple seconds shorter than it should. Any ideas?
The same thing happens to me. Weither it is from my sd card or through pandora.
same thing here. it sounds like alvin and the chipmunks!
I'm not entirely sure but I think this is because of the same reason which makes the clock go faster than it should be.
This is because android is set to turbo mode, so that it runs faster and smoother for you guys, but i'm sure the devs will have something sorted out soon so that its at normal speed.
sorry if i'm wrong, but i think that's what the problem is
Raary101 said:
I'm not entirely sure but I think this is because of the same reason which makes the clock go faster than it should be.
This is because android is set to turbo mode, so that it runs faster and smoother for you guys, but i'm sure the devs will have something sorted out soon so that its at normal speed.
sorry if i'm wrong, but i think that's what the problem is
Click to expand...
Click to collapse
WHEN this is the problem than guys who have this should read the right posts. You have to try the different Zimages,or in best way the latest. There are no problems anymore with pichtin tracks or turbo mode.
no problems with dan's v1 2.2 froyo build with music. I've always started up android manually via explorer instead of using one of those dual-boot solutions... maybe that'll help you guys?
aussiebum said:
no problems with dan's v1 2.2 froyo build with music. I've always started up android manually via explorer instead of using one of those dual-boot solutions... maybe that'll help you guys?
Click to expand...
Click to collapse
Which ROM and Radio are you using?
I am running the newest version of wm6.5 and radio version 2.10.50.26. im just too nervous to brick my phone by putting a new rom on it, should that help?
This is related to the robot noise in calls issue.
It is fixed by using a tmous 2.10 base winmo rom.
Search could have told you this....
GavTheStoner said:
This is related to the robot noise in calls issue.
It is fixed by using a tmous 2.10 base winmo rom.
Search could have told you this....
Click to expand...
Click to collapse
I had this issue (Chipmunk-esque music playback and robo-voice). Flashing to my current rom fixed both problems.
My radio version is 2.10.50.26 on the stock tmo rom (2.13.531.1) and still get the sped up music and robot voice also running the latest zimage from cotulla.
same here, zimage seem not to solve the problem its also not the turbo mode cuz mi clock is working correct but the tracks still sound to fast. Would really like a fix flashed about 5 roms now but nothing seems to work.
I also appear to get this problem, could this be due to a change in hardware in recent models (i got a replacement HD2 in June).
dragonhuntur said:
My radio version is 2.10.50.26 on the stock tmo rom (2.13.531.1) and still get the sped up music and robot voice also running the latest zimage from cotulla.
Click to expand...
Click to collapse
same here. i just stopped listening to music while on android. the songs sound 10x better on winmo right now.
OK, an update seems i managed to fix it by flashing Dutty's latest test ROM
I am looking for a clean useable ROM.
I have tried a few now and cannot find one that works well enough to use day to day, the nearest i have had to a useable rom is mdeejay_froyo_HDv.3.4.1, however typing is useless and all over the place. I logged it but go no answer or fix suggested so I had to ditch it.
I have tried other roms who dont have problems with typing but they have all got there own issues, for instance, some dont pickup you sim contacts, some dont have internet configureable, some just are just too darn ugly to use.
dont suppose anyone can recommend anything for elegancia GTX wwe - 11/6/2010 - radio 2.10
I'm using hyperdroid without any problems. My requirements were a CM-based ROM, with a decent or good-looking theme and low lcd density (240 makes everything waaay too big imo), and hyperdroid has all this. Not too much bloatware either.
Sent from my HTC HD2 using XDA App
The closest I've come so far is HyperDroid 1.6. It's ALMOST there. Occasionally, it falls asleep and needs a power cycle (pop out the battery) to bring it back to life. It also seems to persistently have trouble working with my bluetooth radio in the car. Playing audio works great, but it simply hangs if I get an incoming call or attempt to make an outgoing call.
Bluetooth is also somewhat dodgy with WinMo 6.5 so it might not even be Android's fault. The hardware is really nice so I'm hoping things will get better in a future release.
I have tried these, I cannot get any internet, doesn't seem to autosetup.
Try FroyoStone Sense v3.1, it works really well. I use VBNROM (minimal) and Radio 2.15.50 and it works just like a native android phone. Great Battery life too. Oh and you have to enter APN stuff manually, just google it.
I'm having quite good luck with Bangsters 1.5
Had to switch to rmnet because ppp connections were bloody useless. still having some slight data reception issues, but even with that a MUCH better experience than with my old cliq.
I've been using FroyoStone v3.1 with great success for a little while now, easily my most favourite and most reliable build I've found to date. Everything works, apart from the camera flash delay but that's pretty much universal on most recent (non-evo based) builds.
I'm testing Froyo HD at the moment and really quite like it, only problems I seem to be having could well be my fault (Titanium Backup might have replaced a couple of critical HTC components by accident)
shubcraft 1.5 is about as stable and complete as you are going to get. theres another 2.2 stock cm6 floating around too. however you would have to do something i know you hate. SEARCHING
FroyoStone 3.1 worked much better than others and seemed to be almost perfect for over a week. However, despite DarkStone's claims, by the end of the second week the screen freezes gradually came back, rendering the phone barely usable when walking. The PPP started getting stuck on upload more and more, adding to the problems list.
I should admit there's still no build that has all the functionality working flawlessly, unless you're willing to sacrifice some features, like camera, flash, G-sensor, PPP, music player, etc...
DARKSTONE=perfection
Sent from HTC HD2 w/ Android
Mccm 2.5 SE . EVEEYTHING works and most important, it never freezes for me, data is stable like the hulk
Sent from my HTC HD2 using XDA App
cheers for all the advice everyone, managed to get FroyoStone Sense v3.1 working pretty well, still no camcorder though which is a shame.
Hello all,
I was hoping someone could point me in the right direction to a Gingerbread ROM with a working media start/stop/call end headphone button (I'm using the OEM headphones that came with the phone) and 911. Both of these issues are documented bugs.
I've tried CM 7 and a couple of MIUI ROMs and the non-functioning headphone is pretty much a deal breaker, as I use my Vibrant for podcasts more or less everyday; the fact that 911 doesn't work just seems dangerous.
I've scanned lots of posts for different ROMs and neither issue really seems to come up telling me one way or the other and I don't have a day to load every single available GB ROM and figure it out via trial and error. Search hasn't been particularly revealing either.
For now, it's back to Team Whiskey NextGen v2, but I've tasted Gingerbread and I like it.
Thanks for your time.
Sorry everyone, posted in the wrong sub-forum.
Well, according to similar threads, this looks like it's a problem with quite a few phones, yet no one has been able to give a solution
Basically, the problem is that when I stream audio over bluetooth to my VW 2011 Jetta SE's stereo, every 1 or 2 minutes, the audio stops playing for a second and then fades back in.
Things I've noticed:
I'm fairly certain that the audio actually stops playing for a second rather than the volume going down for a second because I decided to test it out with a metronome. I started the metronome in sync with the music, but after the short audio cut, it became slightly out of sync.
I first noticed the problem when I flashed a Froyo Sense rom way back when (forgot which rom), but it would only happen once within a few minutes of connecting my phone to bluetooth. It wouldn't appear again until the next time I would connect to my car's Bluetooth. Not a big deal
Then I flashed a Sense 3.0 ROM. This is when it started happening every 1-2 minutes. Every Gingerbread Sense ROM I've tried after that has had this problem.
I decided to flash MIUI to try it out, and I noticed that the problem had gone back to only just happening once within a few minutes of connecting to BT. So the problem was definitely not the switch to GB, but most likely Sense on GB.
My friend has the same phone as me and has the same problem in my car, but does not have this problem in his car, so this led me to believe that somehow the combination of my car's system plus Sense on GB is not mixing well.
Problem persists in Sense 3.5
I have yet to try CM7 yet to see if that also has the problem or not.
I will regularly bump this thread to make sure people see it so that SOMEONE can figure out a solution to this problem because it's DRIVING ME INSANE (well, you know, unless the mods are like "**** you stop bumping this ****")
bumpin' as promised.
and i'm bumpin' again
Have u tried switching radios? I a2dp stream to my after market indash DVD player and never gave any issues.
Running tdj dark side runny with .26 radio.
Although i remember when the phone first came out there were massive issues with bt connections to certain in dash stock decks, but believe it got resolved over time with ota updates
Sent from my HTC Glacier using Tapatalk
I have been keeping up to date with radios. I just flashed the latest radio and went back to the stock rooted GB sense ROM and BT seems to be working fine, but I don't know if that's just because it's the stock ROM. I'll try flashing Darkside Sense or Virtuous Affinity and see if the problem returns.
I have the same problem with my bluetooth every minute and half it cuts out then fades back in I drive a 2011 golf. I noticed in my moms 2011 acura rdx turbo it doesn't fade out period. I believe its just the volkswagen bluetooth setup
Sent from my HTC Glacier using XDA App
Welp. Tried Virtuous Affinity. BT Problem came back even on the latest radio. I just got a replacement phone because the vibrate on my phone stopped working for whatever reason. I'll flash it on that to see if it works.
Welp, flashed new phone with Darkside Sense. Same problem :/
Thanks for posting this. I have the same problem with my new Passat. I listen to audiobooks on my long commute and the problem is severely irritating in that context. The first 1-2 words are chopped out of the sentence every 30-60 seconds, because narrators pause their recording to edit or practice inflection or whatever. Result: having to guess what is going on in the story while restraining myself from punching the dash. I'm resorting to aux cable for now and will watch this thread to see if it's ever resolved.
I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. <--- Reported fixed with light patch v1.2 experimental
Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?
I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.
ThePublisher said:
I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.
Click to expand...
Click to collapse
Yeah you're prolly right. I'll excise the last part. I tried Bad Boyz. It's great but I can't do stock based. I've come to rely on all the tweaks in custom ROMs. I should have done more research prior to buying the phone. I need a tweaker's phone like the OnePlus 5. Thank you for your response.
I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. It solved mine and others too.
---------- Post added at 07:22 AM ---------- Previous post was at 07:17 AM ----------
Doc Ames said:
I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...
ArgonautPollux said:
I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.
Click to expand...
Click to collapse
Thank you. That's very helpful.
Laleka said:
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...
Click to expand...
Click to collapse
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.
Doc Ames said:
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.
Click to expand...
Click to collapse
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.
Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
That's a really good idea to use a Tasker task. I wonder if Bluetooth will ever be fixed though. Problem is that Bluetooth connectivity issues only happen with some car head units. It seems like devs aren't looking to fix Bluetooth on custom ROMs because they don't think there's an issue.
piet8stevens said:
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.
Click to expand...
Click to collapse
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.
Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.
Doc Ames said:
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.
Click to expand...
Click to collapse
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.
piet8stevens said:
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.
Click to expand...
Click to collapse
Audio streaming with AVRCP works fine. However the head unit (Kenwood KMM-BT515HD) shows a status of "Connected (no phone)" in Android Bluetooth settings. This means that I can't use my deck to make/answer calls or use voice commands. It works as expected on stock and on Pure Nexus. Others are having this issue too. I know a couple members had issues on Nissan decks and one that I know of had a BMW deck.
Does anyone get voice echo during voice calls on custom roms?
I'm looking to buy the Axon 7 soon, but the voice echo would be a dealbreaker if it exists.
( it's currently an issue with the custom roms I've tried on my Xperia XZ - if I call anyone they complain that they can hear an echo of their voice )
Waancho said:
Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.
Click to expand...
Click to collapse
You need to install Dolby digital
Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.
rafyvitto said:
Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.
Click to expand...
Click to collapse
Whatever the issue is it only causes connection problems (i.e. "Connected (no phone)" ) with some head units. I should try connecting to my roommate's Toyota. I bet it would connect as a phone just fine. There was an issue with BT in LOS that was causing AVRCP (remote control, song info) to not work with some head units. I'm guessing the devs couldn't solve the underlying issue because the fix was to roll back the AVRCP version. It seems there are still compatibility issues with Bluetooth in LOS and AOSP ROMs (save Pure Nexus).
If I could get BT to work fully with my car I would absolutely use RR as my daily driver. Unfortunately the phone is sitting in the box right now until I lose patience and sell the phone or the BT gets fixed. Sucks because I was totally thrilled with the phone after installing and setting up AOSPExtended. Then I got into my car and noticed the issue forcing me back to the dusty, but trusty OnePlus One.
supergear said:
You need to install Dolby digital
Click to expand...
Click to collapse
Hi there,
Thanks a lot for the info (new to me) - to verify:
Are you referring to
https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342
or is there another (preferable safe/easy to install) version one would need?
Thanks again!