Hi guys...
Regretfully I am close to giving up with the HD2 music player. Beaten! Long delays, failure to find any of my mp3s even after retagging... the list of bugs and annoyances is nearly endless, such promise in a phone, such incompetence in the software testing. My last effort was a rushed and irritated email to HTC. Pointless I know but its all I've got, I am now forced to use.... WMP
HD2 Music Player Issues.
I am sure you are sick of these but you are gonna have to read another, please route these to some dev or something, I have already wasted too many hours with this dreadfully realised piece of music software.
I am baffled by HTC. The music player on the HD2 is simply not tested sufficiently. I work in testing so perhaps I am slightly more critical but the list of issues is staggering.
HTC are seriously shooting themselves in the foot, and when I am (frequently) am asked whether I recommend the phone I have to say no, because of the MUSIC PLAYER.
1. Firstly I reported the most incredible 'Genre & brackets bug' on the HTC forums last year and received NO response from HTC. A quick recap, if an mp3 ID3 tag has a ( or a ) in the genre field the music updater stalls FOREVER, yes regardless of tag format etc, its just coded badly. plain and simple, it has 'coded in china and tested in india' written all over it! The updating icon continues forever using up your battery and not updating the rest of the disk. My question to the technical team here is, well why not just skip the file you cant read after some specific timeout, that is 2 extra lines of code and an hugely (but not satisfactory) better user experience.
2. If you have a largish (more than 20) items in a playlist there is a considerable and extremely irritating delay EVERYTIME you go to the now playing screen. Why. Why. Why, who tested this app, who signed it off, how in the hell is it acceptable to have to wait 30seconds to open the music app if you have 400 songs in a playlist, answer dont use large playlists, ok but that leads onto the NEXT huge flaw..
3. When you return to a list (any list), you are always back at the start.. so you just clicked on ZZ Top and you then think oh actually I want to listen to Willie nelson, you are right back at A in the artist list, and it then takes 15 seconds of scrolling to get back to W, why is there no ABCDEG.. index like EVERY OTHER MP3 player.
If it were not for the other dreadful bugs one would have to conclude HTC intentionally crippled this device, what other explanation could there be? Were HTC paid off by Apple?
4. Here is a new one for me, just today I added 500 new Mp3s, to my 16gb memory card, now totaling 1300. Opening the music player sent the CPU to 95% (all manilla) for the best part of 15mins during which time nothing really could be used on the device. When it finally dropped a bit I went in to music player, there are ZERO artists, ZERO albums, ZERO genres but almost all the tracks listed in 'All Songs'. I then allowed the animation to continue for 30 more mins with no change, nothing added. By the way I have rewritten all the id3 tags to various different formats with no affect. I have a feeling that it is stalling on the 1st mp3, what is it stalling on I do not know, is there a log file with errors in it? Can't find one. Again terrible coding, using too much processor, not handling errors, falling over if the format is not exactly as expected. Bad all round.
This is completely unacceptable for a $500 phone.
Just spend a day with and IPod/IPhone and a HD2, that's all your technical team need to do to see what sort of job they have done.
There are loads more but I cannot be bothered now.
It seems HTC have responded to one bug that luckily did not affect me (the stuttering), please can you forward this to the most senior person you know, it really is a joke and whoever does your software testing needs a long vacation and you need to stop outsourcing.
Disgruntled user.
Tom Deloford
Click to expand...
Click to collapse
I'm sure this has been discussed before, but I couldn't figure out the right search terms to find it, so I'm posting a new thread.
No doubt many (if not all) of us have noticed that the audio subsytem is (conceptually) not multi-task -- i.e. it seems only able to play one sound channel at a time. There's no multichannel mixing. So, when listening to music, watching a video, etc., and an email, message, etc. come in, or anything else that triggers a sound notification, the media audio mutes while the notification plays, then the media audio unmutes.
This is highly annoying, and frankly very amateurish of Google. It's not like the functionality in question here is difficult and/or complex, and there's plenty of public domain code to make it work. Just laziness it seems to me.
Anyway, anybody know of a mod/fix, or that this will be fixed in Froyo? It's really bugging me.
I'm on the Syndicate ROM. Could be the ROM, but I seem to remember this problem when I was running stock too.
dwallersv said:
I'm sure this has been discussed before, but I couldn't figure out the right search terms to find it, so I'm posting a new thread.
No doubt many (if not all) of us have noticed that the audio subsytem is (conceptually) not multi-task -- i.e. it seems only able to play one sound channel at a time. There's no multichannel mixing. So, when listening to music, watching a video, etc., and an email, message, etc. come in, or anything else that triggers a sound notification, the media audio mutes while the notification plays, then the media audio unmutes.
This is highly annoying, and frankly very amateurish of Google. It's not like the functionality in question here is difficult and/or complex, and there's plenty of public domain code to make it work. Just laziness it seems to me.
Anyway, anybody know of a mod/fix, or that this will be fixed in Froyo? It's really bugging me.
I'm on the Syndicate ROM. Could be the ROM, but I seem to remember this problem when I was running stock too.
Click to expand...
Click to collapse
This may be a Honeycomb 3.0 (after Gingerbread 2.3) feature because I could see tablets needing to play more than one sound source at a time. And while we may eventually get a Gingerbread port. I doubt we will see Honeycomb.
Hi,
MIUI Rom has always been a great ROM for many Android Devices, I was so excited about installing it into my GSII, but after a while I discovered that the ROM is loaded with many bugs that nobody cares to FIX! I posed This thread In the Official forum of MIUI but what I got is more replies of Bug Reports from other Users, So I decided to post it here maybe someone will care and help develop the theme better, The last version I used was 1.11.11 Three months Old by now, But I checked the changelog of every singl weekly release and it's always the same routine Mi-one Only, Status bar Bug... bla bla bla.
Here is the Complete Bugs List (Report any bug that isn't in this list):
1. Call Recording doesn't work!, when you set the setting to auto-record then return after the call to the recording list, all files are muted! No sound are in the files, useless files
2. [Headphones Only] Volume buttons get the sound to its highest level ( Which is lower than stock Rom and many custom ROMs ) after 4 clicks ( about 25% of the bar ) after that clicking volume up just fills the volume bar without actual sound volume increase in your ears !
3. Battery Drains
4. Feedback widget, Updater app, Themes app ( Including 99% of themes in it ) Contain Chinese phrases which I can't understand
5. No Service Issue ( Connection to cellular carrier disconnects and you need to restart the phone to get signal bars and receive calls/sms ) ( TERRIBLE BUG )
6. Camera takes photos sooooooooooo slowly
7. Notifications Bar doesn't show labels under icons ( Quick shortcuts, small version )
8. Arabic isn't Officially implemented, using patches found On XDA-Developers forums can only add read/write support but it's limited and doesn't include Carrier USSD codes ( Like *150# and various Carrier USSD codes ), Please implement system-wide Arabic support
9. In Call Log when you hold on unsaved # it shows you ( View Contact ) !!! it should show ( Add contact ) Directly
10. Messaging app doesn't support sending Blank SMS which is required by some carriers to subscribe to several services ( So Important please support this )
11. Music app gets 1 album art from the internet and pastes it to 90% of songs instead of finding the appropriate album art for each song and save it like lyrics feature
12. Also in Music app it's so hard to jump to a specific time of the song, The time bar and the equalizer are so stick, you need to separate them by moving the time bar to the bottom.
13. Attach the Stock Android Source Theme with the themes app for the people who don't like themeing.
14. WI-FI specific-network proxy work only with the stock browser, it doesn't support using 3rd party browsers like Firefox, nor using Market/Maps/Downloads or any app thar requires internet connection, you need to make Wi-FI networks that work only via a proxy to work system-wide.
15. Microfone Bug Reported and confirmed by Some users Here
16. Sound Via USB/HDMI Bug ( Car Dock ) also reported here
17. Sometimes when headphones are disconnected when Clicking Volume Up the Popping Volume is Labeled "Bluetooth Headset" While there is no BT headphones connected nor BT is even activated!
Please spread the word and help improve this great ROM.
Thanks
The title says it all what do you prefer?Viber?or Skype?
For me I prefer Viber Because it automatically add people as long as you have them in contacts, it doesn't require a password to login also you can close it and it opens automatically when you receive a message or a call so it doesnt drain battery.
Whatsapp
Non
skype =)
ofc skype
Viber for me
Viber. Better Android integration and the UI looks cleaner
This is the first time i heard about app Viber.it seems be very good(102 000 download),i'm trying it soon
Viber
Viber
Hi,
This is a member of the Viber R&D Team!
We are delighted to see this discussion about our app, and we are here to provide you with direct help
If anyone has any questions/suggestions for Viber, please feel free to let us know, and we will address them shortly.
Thanks,
Viber Team
Viber Team said:
Hi,
This is a member of the Viber R&D Team!
We are delighted to see this discussion about our app, and we are here to provide you with direct help
If anyone has any questions/suggestions for Viber, please feel free to let us know, and we will address them shortly.
Thanks,
Viber Team
Click to expand...
Click to collapse
Hi
Can you tell me what is the average usage of date when I make a call? Thanks
Viber needs seriously to make it compatible with ICS, today has issues with sgs2 and seems that the viber team is totally ignoring them. Take a look how Fring works, the quality of voice is better in Viber, but Fring is an example of a good development.
I prefer Viber but because all friends use Skype on Phone and PC, I use Skype.
@ulrih78 -
Viber uses approximately 0.25MB per minute of call.
@citytrader -
Is your ICS a Custom ROM on your Galaxy S2? (In other words, CM9?)
Viber Team said:
@ulrih78 -
Viber uses approximately 0.25MB per minute of call.
@citytrader -
Is your ICS a Custom ROM on your Galaxy S2? (In other words, CM9?)
Click to expand...
Click to collapse
Is Neat Rom ICS, check in this forum because is the one that has less issues and is pure stock!
For the other side, the mic in viber is so slow, compare your mic with Tango and you will see a big difference, I have to talk to the mic attached at my mouth!
citytrader said:
Is Neat Rom ICS, check in this forum because is the one that has less issues and is pure stock!
For the other side, the mic in viber is so slow, compare your mic with Tango and you will see a big difference, I have to talk to the mic attached at my mouth!
Click to expand...
Click to collapse
Please note that Viber does not fully support custom ICS ROMs (as smooth as they may run on your device), and that could be the source of the problem. Note that many ROMs alter the microphone settings within the devices' API, and this collides with Viber's attempts to utilize it. It sounds like this is the case here as well.
This issue was discussed, and a user-solution was proposed, in this thread here on XDA: http://forum.xda-developers.com/showthread.php?p=25865775#post25865775
But we should emphasize that this is a user solution, not an official solution by Viber.
Take an example of Neat Rom
Viber Team said:
Please note that Viber does not fully support custom ICS ROMs (as smooth as they may run on your device), and that could be the source of the problem. Note that many ROMs alter the microphone settings within the devices' API, and this collides with Viber's attempts to utilize it. It sounds like this is the case here as well.
This issue was discussed, and a user-solution was proposed, in this thread here on XDA: http://forum.xda-developers.com/showthread.php?p=25865775#post25865775
But we should emphasize that this is a user solution, not an official solution by Viber.
Click to expand...
Click to collapse
Hello, sorry for not agree with you, you blame the ROM because Viber has a bad development, Neat Rom is pure Samsung Stock Rom, Fring, Whatsapp, Tango, Skype all works fine and has the mic excellent, I could even talk with my mic far from my mouth with Tango for example.
Your software is buggy even does not start fine when I restart the phone, so take an example of Neat Rom that works without issues and take their developer as an example how his support is free, fast, excellent and how he hear it's users, so maybe you can give him a job to help you to become Viber a better program.
Here is the link of the ROM:
http://forum.xda-developers.com/showthread.php?t=1569686
citytrader said:
Hello, sorry for not agree with you, you blame the ROM because Viber has a bad development, Neat Rom is pure Samsung Stock Rom, Fring, Whatsapp, Tango, Skype all works fine and has the mic excellent, I could even talk with my mic far from my mouth with Tango for example.
Your software is buggy even does not start fine when I restart the phone, so take an example of Neat Rom that works without issues and take their developer as an example how his support is free, fast, excellent and how he hear it's users, so maybe you can give him a job to help you to become Viber a better program.
Here is the link of the ROM:
http://forum.xda-developers.com/showthread.php?t=1569686
Click to expand...
Click to collapse
Hi again,
This isn't a development issue - it's not that we lack the technological knowledge to solve this problem. We just can't afford to attend to each and every Custom ROM in the world and adapt Viber to it, even if other applications do. Because the next day, a new developer would release a new version of their ROM, and then another version, and then another ROM, and it goes on and on.
We don't have the resources nor the time to deal with all these Custom ROMs at this stage, and it is certainly not our responsibility if ROM developers create ROMs that alter the API and access to the microphone by changing the Model Number, for example (a common issue that repeated itself in all of the CM9 ROMs).
We apologize that you feel that our support here on XDA is bad. We feel the contrary - we make sure that each and every user gets a full answer from us, and we take into consideration users' requests and bug reports.
Having said that, I will make sure this report is passed on to our development team, and we will see what we can do (in the future) about it. Thanks again for your time!
Viber Team said:
Hi again,
This isn't a development issue - it's not that we lack the technological knowledge to solve this problem. We just can't afford to attend to each and every Custom ROM in the world and adapt Viber to it, even if other applications do. Because the next day, a new developer would release a new version of their ROM, and then another version, and then another ROM, and it goes on and on.
We don't have the resources nor the time to deal with all these Custom ROMs at this stage, and it is certainly not our responsibility if ROM developers create ROMs that alter the API and access to the microphone by changing the Model Number, for example (a common issue that repeated itself in all of the CM9 ROMs).
We apologize that you feel that our support here on XDA is bad. We feel the contrary - we make sure that each and every user gets a full answer from us, and we take into consideration users' requests and bug reports.
Having said that, I will make sure this report is passed on to our development team, and we will see what we can do (in the future) about it. Thanks again for your time!
Click to expand...
Click to collapse
Thanks for your answer, Neat Rom is a stock rom, so if it works with it, it will work with any stock, for the other side, the mic problem is even with IOS, not so bad than android, but I have to talk with the mic near my mouth, this does not happens with facetime for example.
The list of bugs with stock rom are:
- Mic so low
- Viber does not autostart fine when I restart the phone, I have to click Viber once to let it run in
background to receive call
- When there is a missing call and this appears in notification area, when I click this notification, viber opens showing nothing, I have to open viber and click recents to clear the missing call notification
With this 3 bugs resolved, you program will be great and again, take a look to Neat Rom, is the Rom with less issues I have tested and I have no relationship with the developer, I'm only a happy user!
Best regards!
@citytrader -
Neat is naturally not a 100% Stock ROM. Otherwise there wouldn't be a developer working on it, having to fix it (just like you said above), and doing it all on XDA.
It might be very close to Stock, but not 100% Stock.
About the bugs you mentioned - they are known to us and we are continuously working to fix them (there is a new, big version coming up soon, so stay tuned for updates!). Meanwhile, I invite you to use this direct link and report these issues to our support teams along with the technical details. This will help us speed up the fixing of these issues: http://bit.ly/ukGVJ0
And as a general note - it is important to explain that, as a company that's developing a service that more than 70 millions people around the world use, we have many projects running parallel, and sometimes we cannot immediately devote all of our resources and manpower to a specific bugs. Of course, we log them and they are on our list, but things cannot happen as fast as they do when it comes to fixing a ROM
So, we kindly ask your patience, and we can guarantee you that our development teams are working around the clock to improve Viber with every new version that's released
Hey,
I didnt know where i should Post my Bug Report so if its the wrong section dont hold back to tell me.
I'm currently using my Galaxy S2 for daily use and after flashing some Kitkat Roms Omni is in my opinion the most stable rom and with Nova + ART a damn fast Rom, so thank you very much for supporting my Device.
I dont know whats happening the last weeks but it all began with an Opendelta Issue, i wiped all Data / Factory Reset via TWRP and flashed the Rom completely new and OpenDelta still didnt work, it just said every day its all up2date. Now after a couple of days it is working again, dont know if it was a Server Issue or something else - at the official Omni Page no one post News so i have always to guess whats happening
Currently i found 2 Bugs, if you want to call someone you open up the Dialer and then the Button for the Numbers but after clicking it, theres nothing(Screenshot is attached). You have to go back and try it again then the Numbers are there. The second Problem is that there is no Zoom in the AOSP Camera App if you record a Video. My currently workaround is the Google Camera App, there all is working fine. Also there are some Issues with Apollo , freezing , doesnt update the Song DB etc. , dont know why its so popular - its horrible. Replaced it also with a 3rd party App - Omich/Rocket Player.
The last Problem is that not everywhere in the Settings the correct language is used, if you need some translation help im sure many users would like to help(including me) but that is in my opinion nothing critical .
...and sorry if my Text was hard to read, its not my native language but im working on it :silly:
Regards
Per the FAQ, this is not the place to put bug reports.
However, I9100 hasn't been maintained in a long time, so filing a bug report will be a waste of time. Support for this device is currently going to be dropped with Android 5.0, and if it receives 4.4 bugfixes, that'll have to come from a new maintainer as none of the former maintainers have time/motivation for the Exynos 4210 devices these days.
Some of the issues you describe with Apollo aren't Apollo issues, but the result of a very deep-down core bug that has a side effect of screwing up storage access. This bug has been known for nearly a year (there's a big thread disucssing it somewhere around here...) and still no one has found a fix for the root cause. In fact, it's one of the #1 reasons the device is getting dropped for L. (It will absolutely not receive nightlies unless someone finds and corrects the root cause.)
Hey,
Thank you for your response. :good:
I reported the Bug on jira and there is a workaround for the Dialer Bug: Setting The Animator Scale higher than 0.
The Drivers are the problem right?
pfxandroid said:
Hey,
Thank you for your response. :good:
I reported the Bug on jira and there is a workaround for the Dialer Bug: Setting The Animator Scale higher than 0.
The Drivers are the problem right?
Click to expand...
Click to collapse
Well, there are three things you listed:
1) Dialer stuff - probably some sort of odd HDPI issue and/or graphics subsystem stuff. The Exynos4 graphics subsystem is why many developers don't want to ever touch the platform again.
2) Zoom in video - What resolution was Google Camera? Zoom has NEVER been available for 1080p resolutions on the Exynos 4210 family, not even stock firmware will zoom in 1080p
3) The storage issues are a symptom of a deep-down kernel bug that no one has found the root cause of. This is the #1 reason the device is getting dropped for 5.0 - there is no chance even if a new maintainer steps up that nightlies will resume until someone tracks down the root cause of this one. http://forum.xda-developers.com/showthread.php?t=2612329 has more discussion (warning: It's long...)