Question... does anyone else use Google Listen on this phone? I just got a new one with 2.2 pre-installed and I am wondering if Google Listen is buggy with 2.2 or if it is buggy with the EVO in general before and after 2.2. Listen works perfectly on my Samsung Moment (under 1.6 and 2.1) and the bugs I am experiencing on the EVO are starting to make me hate it. I have also had problems adding items to my calendar and with my Gmail data staying in sync. All these things worked perfect on the Moment, so I am not sure if these are 2.2 bugs or EVO bugs caused by HTC Sense (which I hate in comparison to vanilla android). Seriously, I am about to the point of returning this phone or selling it and going back to the Moment, which worked perfect aside from the data radio lockups that would happen every few days or less.
Any feedback would be greatly appreciated before I make a rash decision that I will later regret.
Question about
Help before I throw mine out a window!
top answers
community pick
Listen is quite buggy. It is VERY beta. I stayed on 1.1.2 because comments in the Marketplace said 1.1.3 was worse in some cases. You probably had 1.1.1 or 1.1.2 on the Moment and got the newer one when you upgraded.
I use it daily and it works well enough, but you have to be willing to endure some BS.
- Sometimes it only partially downloads a podcast before giving up for no apparent reason.
I then need to jump through menu-hoops to get it to delete the corrupt file and try again.
- Sometimes it will hang refreshing the list.
- Sometimes the playback will grind to a halt mid-podcast and only emit blips of sound, necessitating a force-close and reload. It does remember where it stopped though.
- Scrubbing is hit and miss.
- I wish you could turn off landscape mode.
- The whole "My Listen Items" vs. "My Subscriptions" subsection delineation is a bit confusing. I can never remember what functions are where and never understood the point in the separation.
This is on a 2.2 N1, BTW.
I use it daily and it works well enough, but you have to be willing to endure some BS.
- Sometimes it only partially downloads a podcast before giving up for no apparent reason.
I then need to jump through menu-hoops to get it to delete the corrupt file and try again.
- Sometimes it will hang refreshing the list.
- Sometimes the playback will grind to a halt mid-podcast and only emit blips of sound, necessitating a force-close and reload. It does remember where it stopped though.
- Scrubbing is hit and miss.
- I wish you could turn off landscape mode.
- The whole "My Listen Items" vs. "My Subscriptions" subsection delineation is a bit confusing. I can never remember what functions are where and never understood the point in the separation.
This is on a 2.2 N1, BTW.
mark as good answer
2 people like this answer
Clicking the mark as good answer button helps us highlight the best answers.
I know 2.2 caused more than a few audio problems on a lot of phones. They did something like drop support for some legacy codecs which screwed up some audio programs. I don't know if google listen is one of those since I don't use it.
mark as good answer
0 people like this answer
Issue here: code.google.com/p/android/issues/detail?id=9308
Explanation here: www.androidcentral.com/fix-coming-froyo-audio-issu...
Correction to the above the article comments: "Because Pandora and all other app developers assumed the codec would be continued to be supported. This is an acceptable assumption as it is SUPPOSED to be. Yes, Froyo was supposed to support this, it was NOT phased out as Jerry reported.
It's not like it isn't being decoded at all. It's being decoded improperly.
There's many other reasons wrong with this too, like:
A. They need to support the most used formats, not the ones they like most. Should they kill off MP3 too? That would be stupid.
B. Google obviously sides with app developers, that's why they fixed this bug and acknowledged it as such, instead of dismissing it as intentional.
C. You can't expect app developers to re-encode their entire thousand+ GB music library because Google can't maintain a good AAC+ decoder.
D. The codec isn't even legacy to begin with!"
Possible fix here: forum.xda-developers.com/showthread.php?t=737111
Another Possible fix from the first link: "Addendum/correction to my earlier post #37:
After losing battery on my N1 and restarting, I lost the setting, and audio quality improvements with it to boot.
To make the change permanent, the setting should be changed in /system/build.prop
Because of issues with the mount mode for the volume in which /system resides, it's not easy to make the change to build.prop.
Ultimately, I found the easiest way to do it was to download and install "Root Explorer", open, navigate to the /system folder, press the button to remount the volume in read/write mode, then open build.prop up for editing, and make the change there, all on the device itself. No USB connection required."
It looks like you have to root or wait it out.
Explanation here: www.androidcentral.com/fix-coming-froyo-audio-issu...
Correction to the above the article comments: "Because Pandora and all other app developers assumed the codec would be continued to be supported. This is an acceptable assumption as it is SUPPOSED to be. Yes, Froyo was supposed to support this, it was NOT phased out as Jerry reported.
It's not like it isn't being decoded at all. It's being decoded improperly.
There's many other reasons wrong with this too, like:
A. They need to support the most used formats, not the ones they like most. Should they kill off MP3 too? That would be stupid.
B. Google obviously sides with app developers, that's why they fixed this bug and acknowledged it as such, instead of dismissing it as intentional.
C. You can't expect app developers to re-encode their entire thousand+ GB music library because Google can't maintain a good AAC+ decoder.
D. The codec isn't even legacy to begin with!"
Possible fix here: forum.xda-developers.com/showthread.php?t=737111
Another Possible fix from the first link: "Addendum/correction to my earlier post #37:
After losing battery on my N1 and restarting, I lost the setting, and audio quality improvements with it to boot.
To make the change permanent, the setting should be changed in /system/build.prop
Because of issues with the mount mode for the volume in which /system resides, it's not easy to make the change to build.prop.
Ultimately, I found the easiest way to do it was to download and install "Root Explorer", open, navigate to the /system folder, press the button to remount the volume in read/write mode, then open build.prop up for editing, and make the change there, all on the device itself. No USB connection required."
It looks like you have to root or wait it out.
mark as good answer
0 people like this answer
this won't be very helpful but i'm not having any issues with Listen at all.
I use it almost everyday.
the only audio app i have had a problem with is .Podkast. sometimes it doesn't remove the notification icon after playback is through. I have to reboot to get rid of it.
I use it almost everyday.
the only audio app i have had a problem with is .Podkast. sometimes it doesn't remove the notification icon after playback is through. I have to reboot to get rid of it.
mark as good answer
0 people like this answer
I have an EVO 4G with 2.2 and I just recently downloaded Google Listen. It seems to play fine for me, but I am annoyed that I can't fast forward or select a point to start playing from without the podcast restarting all together. But I went on the Google Listen discussion page and it seems that it is having this problem with a lot of phone. Bottom line is that Google Listen is on of what google calls a lab program and I imagine it will have a lot of kinks to work out in the process. I will try using it more this week and report back.
mark as good answer
0 people like this answer
Google Listen is very buggy, I have always used dog catcher instead, never had an issue
mark as good answer
0 people like this answer
follow this question
share:
Related questions
7 users following this question:
This question has been viewed 94 times.
Last activity .
Tips for giving the best answers
Sometimes it's just little details that separates a great and not so great answer! Here are a few simple tips to keep in mind:
- 1
- Be complete and thorough. Don't skimp on the details!
- 2
- Try not to answer with a question. Because that's not really an answer, right?
- 3
- A little research goes a long way. Back up your claims and assumptions!
- 4
- Try to be patient, tech questions can be complicated.
- 5
- You are awesome for both reading this and answering questions.