Google Finally Acknowledges Volume Bug issue and has a fix in place for release according to this........
http://www.bbc.co.uk/news/technology-15870020
oka1 said:
Google Finally Acknowledges Volume Bug issue and has a fix in place for release according to this........
http://www.bbc.co.uk/news/technology-15870020
Click to expand...
Click to collapse
isnt that the same news as yesterday?
oka1 said:
Google Finally Acknowledges Volume Bug issue and has a fix in place for release according to this........
http://www.bbc.co.uk/news/technology-15870020
Click to expand...
Click to collapse
Google has acknowledged this quite a while ago. BBC is just catching up.
let's just hope samsung, under the pressure of google actually has a fix.
remember their supposed "fix" for the Galaxy S's GPS issues? yeah right
until this major flaw gets a 100% fix, not forking out my cash
terencec said:
let's just hope samsung, under the pressure of google actually has a fix.
remember their supposed "fix" for the Galaxy S's GPS issues? yeah right
until this major flaw gets a 100% fix, not forking out my cash
Click to expand...
Click to collapse
Same here. Needs fixed.
Sent from my HTC Desire using XDA App
kristovaher said:
Google has acknowledged this quite a while ago. BBC is just catching up.
Click to expand...
Click to collapse
not only are the BBC late, but they're also incorrect. Well done BBC
BBC is WOLS...
Related
Currently, Ventriloid and Mangler are non functional for the Android JB firmware. Although the Ventriloid dev has posted a temp fix in the app description, it crashes alot and will not serve much use for me. Is it possible for someone to post a fixed app or a way to access vent on JB?
Store link:
https://play.google.com/store/apps/details?id=com.jtxdriggers.android.ventriloid&hl=en
Temporary fix link:
https://code.google.com/p/ventriloid/downloads/list
Buuump. I totally need this, and many do aswell.
Metal Slug said:
Buuump. I totally need this, and many do aswell.
Click to expand...
Click to collapse
Ventriloid dev here. What issues are you having with the test version on the site? I just finished up my semester at school and will hopefully have an official release out by January, but I need some help testing.
Ventrilo for JB not working?
jtxdriggers said:
Ventriloid dev here. What issues are you having with the test version on the site? I just finished up my semester at school and will hopefully have an official release out by January, but I need some help testing.
Click to expand...
Click to collapse
Just wanted to jump in and mention that I am having issues too. Samsung SII, cm10. When I start ventriloid is initially says connecting, but then very often goes back to mobile's home screen. It then leaves a notification bar entry saying that it is connected. When you click on that, it does its two vibrates and goes off entirely. Sometimes I can get it going again, but is very fiddly. Dont know if this helps. Hope so.
London Lad
LondonLad said:
Just wanted to jump in and mention that I am having issues too. Samsung SII, cm10. When I start ventriloid is initially says connecting, but then very often goes back to mobile's home screen. It then leaves a notification bar entry saying that it is connected. When you click on that, it does its two vibrates and goes off entirely. Sometimes I can get it going again, but is very fiddly. Dont know if this helps. Hope so.
London Lad
Click to expand...
Click to collapse
Hey LondonLad, thanks for the report.
Are you using the Play Store version of the app or the Alpha on my Google Code?
jtxdriggers said:
Hey LondonLad, thanks for the report.
Are you using the Play Store version of the app or the Alpha on my Google Code?
Click to expand...
Click to collapse
Playstore version.
LondonLad said:
Playstore version.
Click to expand...
Click to collapse
Go try out the Alpha at ventriloid.googlecode.com in the downloads section and let me know how it works for you. I apologize for any lack of features in that version but it's a huge work in progress.
jtxdriggers said:
Go try out the Alpha at ventriloid.googlecode.com in the downloads section and let me know how it works for you. I apologize for any lack of features in that version but it's a huge work in progress.
Click to expand...
Click to collapse
Have downloaded and it seems to work well. (Did loose the Ventriloid icon though!) One comment: One must tick the box Enable Global Push to Talk in order to see key. That is fine, but it does cover up part of you keyboard if you, for example, need to type in a password for a channel. Not a problem, but thought I would at least mention it.).:good:
LondonLad said:
Have downloaded and it seems to work well. (Did loose the Ventriloid icon though!) One comment: One must tick the box Enable Global Push to Talk in order to see key. That is fine, but it does cover up part of you keyboard if you, for example, need to type in a password for a channel. Not a problem, but thought I would at least mention it.).:good:
Click to expand...
Click to collapse
I'm glad it's working for you I'm working on a complete UI overhaul and that global push to talk was more or less a proof of concept for being able to talk outside of the app. Android has limitations for hardware key interception that won't allow push to talk while the app is in the background, so hopefully people will enjoy this new button. It will eventually be a bar with other options that can be hidden. Thanks so much for testing, I'm glad the ICS/JB fix is working.
jtxdriggers said:
I'm glad it's working for you I'm working on a complete UI overhaul and that global push to talk was more or less a proof of concept for being able to talk outside of the app. Android has limitations for hardware key interception that won't allow push to talk while the app is in the background, so hopefully people will enjoy this new button. It will eventually be a bar with other options that can be hidden. Thanks so much for testing, I'm glad the ICS/JB fix is working.
Click to expand...
Click to collapse
Thank you for your work on this. It is helping a lot of people! (I will make a donation shortly.)
LondonLad said:
Thank you for your work on this. It is helping a lot of people! (I will make a donation shortly.)
Click to expand...
Click to collapse
I greatly appreciate it I need to get a Bluetooth headset for testing, but Christmas and next semester's tuition has completely drained me haha. Let me know if you have any other issues or feature requests!
I heard the gs3 had a bug when lightflow was enabled that it was also causing talkback to answer "FOLDER OPEN!!!!" and then "FOLDER CLOSED!!!".
This is extremely annoying but I love lightflow to much to uninstall it. Is anyone else having this problem and is there a solution? I read this was an ics bug but I never had any problem with my nexus.
I seemed to run into lightflow and talkback not being able to be on at the same time...even though talkback is off. It says it needs to disable airview for lightflow to work. No go for me. Deleted it.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
There is a new version of Lightflow out now...how does it work with the Note 2?
erick161 said:
I seemed to run into lightflow and talkback not being able to be on at the same time...even though talkback is off. It says it needs to disable airview for lightflow to work. No go for me. Deleted it.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
You'll find details about the issue here as after 6 months of trying different avenues, it seems Samsung may be listening. I got in touch with a few developers who also face the same issue and we all posted to the samsung developers forums. See here: http://developer.samsung.com/forum/...=GeneralB&messageId=204387&messageNumber=2156
As for airview you can just switch it back on after switching on accessibility. It's just another Samsung bug in this area.
Bug still here with last rom DMB6.
As much as good
send from my Lumia 1280 in Vietnam
takun92 said:
As much as good
send from my Lumia 1280 in Vietnam
Click to expand...
Click to collapse
Samsung have got a fix for this they have reported about a week ago. This from their site:
"The development team figured out the cause of the issue and corrected the cause.
They are planning to reflect it in the next version.
Regards,
Samsung Developers"
andrewpmoore said:
Samsung have got a fix for this they have reported about a week ago. This from their site:
"The development team figured out the cause of the issue and corrected the cause.
They are planning to reflect it in the next version.
Regards,
Samsung Developers"
Click to expand...
Click to collapse
Thats great news!
I explain the problem to the lady, and she said she will contact google to have it resolve fingers cross.
now im on the phone with google hehe, pushing the limit for a fix.
Lol. Oh yeah, she'll have Google get right on that.
Vandam500 said:
Lol. Oh yeah, she'll have Google get right on that.
Click to expand...
Click to collapse
i highly doubt
I tried Kodi 17 beta 4 and 5 on my S10.5 and each time it would start I got audio pops...like a headset getting plugged in. I would also get them when moving around various menus or playing a video.
I just was wondering if anyone else has installed it and had the same problem or not???
Might be I need to flash the MM update again...
Yeah, it`s normal with the beta, it happens to my T800 and another S1 owner has mentioned it as well.
John.
Tinderbox (UK) said:
Yeah, it`s normal with the beta, it happens to my T800 and another S1 owner has mentioned it as well.
John.
Click to expand...
Click to collapse
Sure hope they get it fixed in the final release..it's so annoying I can't stand using Krypton and reverted to Jarvis.
Glad to know I'm not alone....If I could figure out how to report it as a bug I would...
You should report the fault on the app download page on Google Play as if you were posing a review as you are a Beta Tester.
John.
flhthemi said:
Sure hope they get it fixed in the final release..it's so annoying I can't stand using Krypton and reverted to Jarvis.
Glad to know I'm not alone....If I could figure out how to report it as a bug I would...
Click to expand...
Click to collapse
Tinderbox (UK) said:
You should report the fault on the app download page on Google Play as if you were posing a review as you are a Beta Tester.
John.
Click to expand...
Click to collapse
I tried that when I first noticed it...no reaction there at all.
The answer
Well, well ,well....Today I installed beta 6 to see if they fixed the ugly audio pops I was hearing. They didn't, because it's NOT a bug, it's intentional! There is a setting to turn it OFF. Using the stupid estuary default skin go to
1 Settings
2 System Settings
3 Audio
4 Turn off "Send Low Volume Noise"
It's "supposed" to be an inaudible sound to keep some AVRs powered on. Maybe they need to try something else!
Marked as fixed.
The development team has fixed the issue that you have reported and it will be available in a future build.
Click to expand...
Click to collapse
No don't laugh but Google have marked the Pixel 6 as fixed in the next up date even though they've not released it thus won't know for sure everyone is happy
Google Issue Tracker
issuetracker.google.com
Just hoping the camera freezing issue is fixed soon!
Texan1 said:
Just hoping the camera freezing issue is fixed soon!
Click to expand...
Click to collapse
According to them it is even though its not been released for people to test, this will be the last Google device I buy
Texan1 said:
Just hoping the camera freezing issue is fixed soon!
Click to expand...
Click to collapse
I sure hope so! It's so annoying!!!!!