[Okay... I'm posting this because or seems like there's a lot of chatter about this issue but for some reason it doesn't seen like a damned thing had been done about it, and that's not cool in my book. And yes, I'm cross-posting this between Android Development and Original Android Development, because it effects both groups.]
Okay... Having determined that this is something that I can't fix, I submit this logcat to the group:
http://pastebin.com/Av4P7H8Q
That is the result of me opening Hangouts and placing a VOIP call to a contract. The result is the ring-to call sound continues to play after the called party picks up, and they cannot hear any sound I make. Further, hanging up results (eventually) in Hangouts crashing (but the call not actually ending until then).
As you may (or may not know) using Hangouts VOIP calls is BORKED, and it has been for several days. This seems to affect all downstream CM12 ROMs, at least for the LG G3 D851.
Take a look at that logcat... It Is a MESS. Why are cameras being called ajillionty times for making a VOIP call? Why is there no path to the necessary VOIP_MIC component? When you realize that all 8000+ lines of this comprise *only a few seconds* just how...odd...things really are.
It is my understanding that this began after a pile of CM12 commits several days ago, but I'm not certain exactly when. I seem to remember someone is $droyd$'s Illusion ROM thread had the exact date(s).
Surely amongst all the developer brainpower we have amassed here we can figure this out...
So: any ideas?
Cm12 12/8 is when hangouts broke.
---------- Post added at 06:05 AM ---------- Previous post was at 06:04 AM ----------
Illusion vs 1.xx hangouts still work.
So anything built on 12/8 and after, or beginning on 12/9?
I believe it's 12/9 when it broke.. 12/8 still worked.. I should have been more clear.
I've created this post in the "dev only" forum. Please move any discussion on this subject to this thread:
http://forum.xda-developers.com/lg-g3/devs-only/hangouts-voip-calling-broken-figure-fix-t2978600
Related
Ok. Short story of what I want to do and why.
I am a developer and I feel that I don't contribute enough to this fantastic site and its users. After the recent unpleasantness I went away and thought about what it is that I could do to try and fix this. My idea is a site or section of the wiki built specifically to track bugs and issues in new roms (I was specifically thinking WMXL but there is no reason this can't be used for all of them).
I am currently working on my own XML based site with PHP5 driving and if people think it will be useful I'd write and host this service before I continued with my own site (hopefully before WMXL 0.30 is released).
I want to try and restrict the way people enter and search the information relating to problems with new roms and try to cut out the background noise. I was thinking about having fields such as ROM version (drop down list), radio version (text box), boot loader (drop down list), main program affected (text box), extent of interference (drop down list), description of problem (text area), how to reproduce error (mandatory text area!).
This will hopefully encourage more people to think about what might be causing the problem rather than just posting what they cant do and expecting someone else to work everything out. Forcing a description of how to recreate the problem will hopefully find most users not needing to post after they work it out, and if the recreation steps dont work then the post will be closed. Hopefully people will think enough that I will be able to moderate this forum (type thing) myself and maybe someone in another timezone (closer to the UK) can take care of it while im asleep.
No one can stop n00bs posting silly questions but hopefully we can reduce the amount this annoys everyone else.
Sorry it took so long to describe my idea.
Maz
UPDATE: STARTED!
I got started as soon as I'd got a couple of replies but I still need you all.
For the chef's and other brilliant people:
1. What info do you need with each ticket to try solve them?
2. Do you want to be the only one to close tickets? Or should the submitter be able to?
3. What info do you want to store for the roms to filter to the smallest pool of specific tickets?
For the users:
1. How do you want to be able to search this?
I DON'T ASK FOR DONATIONS! ALL I ASK IS THAT PEOPLE SEARCH BEFORE SUBMITTING!
---------------
http://maz.net.au/
Bugzilla? yes please
This is a very good idea. In fact, I think that we need too a place to store the temporary fixes generated after each ROM publishing. It will be a good place for this too.
Good Idea.
It Would Help A Lot, Sounds Like Finding Answers Would Be Easier And Should Cut Down On The Hostile Atmosphere.
Cheers
Yes, very good idea.
This become easyest forum for everyone.
If it would be of any use, i can host this on one of our UK servers so we get very good speeds? I know 'iammaz' has said he can host it but he is in Australia so for the UK guys it might be a tad slow.
If not then no worries, but just trying to do my bit!
jaso2005 said:
If it would be of any use, i can host this on one of our UK servers so we get very good speeds? I know 'iammaz' has said he can host it but he is in Australia so for the UK guys it might be a tad slow.
If not then no worries, but just trying to do my bit!
Click to expand...
Click to collapse
Cheers and I'm sure everyone appreciates the offer. My site is hosted in the US. At the moment this is being built as a module to my current CMS. Whether or not this adds too much overhead I won't know until I try. The problem will be if I use too much cpu time im sure it's against the ToS with my hosting company and they will shut me down.
I hope that I will have it built as a stand alone object by then and anyone else can take this and run this on php5 hosting or in fact I could run it as web services from my personal server at home.
Progress goes well. Just working on possible searching and indexing algorithms to make searching fast and useful.
Maz
-------------------
I can't believe I forget to type this.
http://maz.net.au/
Great idea
It's 2am. I'm piking for the night. I'm expecting a phone call at 7am tomorrow so will be back into it then for 5 or 6 hours. Hopefully will be almost done by the end of that.
I need to work out how you want to have logins work. I don't think i can make it authenticate against this forum (i havent tried integrating with vBulletin before). Do I allow open registration? do I try make it force you to register the same name but PM'ing the password to that username here? do i manually add people as they ask and restrict the group?
let me know in the next 6 hours or so.
Maz
----------------------
Badly styled CMS can be seen here. (new version looks so much better )
http://maz.net.au/
Open registration, but obviously grant privileges to those of us who classify as developers.
Olipro said:
Open registration, but obviously grant privileges to those of us who classify as developers.
Click to expand...
Click to collapse
And super-user privileges for the chef's for bug tickets that apply to their cooked roms.
Maz
----------------
hard at work again at http://maz.net.au/
So as the title states, I'm not only new to the forum, but to the whole world of stock/custom ROMs, and about 95% of the vernacular that appears in your typical conversations.
Before opening this thread, I did read a few others on the subject of Open Mobile users successfully using customized ROMs of other carriers, but with the loss of 3G and/or MMS. (By the way, the feature that shows similar threads under the title box- genius.) I, too, have fallen into that unfortunate category, but with a stock ROM belonging to Metro PCS. It was completely unintentional, the changeover.
After the first 10 minutes of freaking the out, I got my act together and found this forum, among others with not a single solution to my problem, or that of other users with a situation similar to mine.
I would simply like to know if anyone has been able to fix this problem.
As proof I've check other threads,
-This one is for an HTC Hero and in page 2, post #11, someone offers a possible solution, but the person referred to doesn't respond. And I can't really understand what it says.
-This one offers three posts of nothingness.
-This oneseems to have a user inventing a Battleship/Bingo hybrid with all them numbers and less-than-average use of periods.
I appreciate any help anyone offers. And if I posted this in the wrong section, feel free to move it as needed.
Again, thanks.
As a follow-up, today I realized that I could access the Play Store by using 3G only. I could also browse/download apps and use apps that require internet/data connections, such as Words with Friends and Draw Something.
Basically, all I lack now it internet access (I was able to download another browser even just to make sure it wasn't the original one that was FUBAR) and MMS capability (I can receive pictures, but not 100%; more like 90%).
Any thoughts or suggestions?
First of all I want to thank everybody whos making efforts so that our beloved Desire survive through out these years!!
I am a Desire owner for more than three years and I could say that I have tried nearly anything on my device.
Currently I am using this Rom with the exactly configuration written by the user.
As the user Tonyp has written in the post, that exact setup is working really good and without any major issues. I have only 3 spots that i would like to point out:
1st When I am call directly from the address book a contact that is stored without the national prefix (+30 Greece) the phone adds automatically the prefix +1 (maybe US I don't really know), so this make the call goes wrong.
2nd From Optimo Settings (included in the Rom) I don't have the choise to dissapear the battery icon and leavy only the numbers.
3rd As it already pointed out, in the Rosie Options, the right button choise for the shortcut isn't working if you select anything else bit the internet browser.
I would really like to hear your thoughts about the things that i've pointed out before, and again to thank everyone that is contributing to the development of our device!!
As an addition to the previous post I have found out that some appz that they use the google account to log in such as youtube and quicktime, they sign in feature doesn't work, although I have install the latest google play services and the syncing of the google account works fine.
Thanks in advance and please if some wants to copy my 2 posts to the development thread, be my guest!!!
[I originally posted this in the T-Mobile G3 Dev & Original Dev forums, but it was pointed out that those were not the appropriate forums for this thread. In an attempt to follow the rules (and hopefully spark some conversation about this issue) I'm posting this here, now. Please, read on...]
Okay... Having determined that this is something that I can't fix, I submit this logcat to the group:
http://pastebin.com/Av4P7H8Q
That is the result of me opening Hangouts and placing a VOIP call to a contract. The result is the ring-to call sound continues to play after the called party picks up, and they cannot hear any sound I make. Further, hanging up results (eventually) in Hangouts crashing (but the call not actually ending until then).
As you may (or may not know) using Hangouts VOIP calls is BORKED, and it has been for several days. This seems to affect all downstream CM12 ROMs, at least for the LG G3 D851.
Take a look at that logcat... It Is a MESS. Why are cameras being called ajillionty times for making a VOIP call? Why is there no path to the necessary VOIP_MIC component? When you realize that all 8000+ lines of this comprise *only a few seconds* just how...odd...things really are.
It is my understanding that this began on or around 12/8-9. The culprit would seem to be commits made to CM12.0 on 12/7, 8 or 9. I've gone over the commits that were merged during that timeframe and nothing stands or as obvious... Though there do appear to be a few that warrant further investigation. I'll try and a compile a list of commits that I think make good candidates for inspection.
Anyone have any other ideas, or places to start, maybe even areas/projects in CM12.0 that should be looked at more closely?
Has anyone tried a version of the app for a 5.0.1 device(N6) I know some of googles apps vary depending on your OS version (Google Now is different from 4.4 to 5.0) I'm not sure how to get it other than having a compatible device and copying the apk over to an G3.
It's not the apk causing the problem @candler33w I'm using illusion ROM vs 1.02 and hangouts works fine on that and that is android 5.01. but it doesn't work on his latest version of illusion (v2.xx). He says he switched his base and since it's been broken.
mic problem is apparently a build.prop property..
change "use.dedicated.device.for.voip=true" to false.
seen here: http://forum.xda-developers.com/lg-g3/help/fix-fix-voip-calling-lollipop-roms-t2980294 or here https://github.com/AndroidUser00110001/device_lge_d855/issues/7
edit, sorry FULL/ALL credit to @marcelol151 no need to mention my name.
I am finding that ads are stealing the focus from the textarea, like the one I am typing into now, so that every few seconds what I type goes into oblivion and I need to click back into the textarea.
Having said that, I've not noticed it on this one, so perhaps it is specific to one forum, or ads that are placed on that forum. The post this most recently happened on is:
https://forum.xda-developers.com/mate-30-pro/accessories/screen-protectors-t4013837#post81412545
It would be excellent if this behaviour could be prevented.
Google Chrome 79.0.3945.88 (Official Build) unknown (64-bit)