I have turned on all permissions in Uber from Setttings, but when I request an Uber car I get an error message saying that the request can't be completed.
I'm using Model Number LON-A00, Build Number LON-AL00C00B167
Does anyone know a fix?
That's because Uber is a joke, probably not phone related.
I'm going through my own bit of Uber hell after they locked my account for no reason whatsoever.
Related
Hello peeps, I posted this in another thread but thought it prudent to create a new thread as well.
I am using an unlocked Hero on the Three Network in the UK, I bought it last month just before they announced that they were releasing the phone with spotify.
Anyway I was able to install the skype client this morning, which, as it was on my old 3 phone, worked perfectly with using any of my minutes.
The issue I know have is that it does not put the phone back to sleep, even after I removed the installation and power cycled my phone... it is awake 100% of the time even after skype has been removed and my power usage has suffered as a result.
I used taskiller to check but skype is not running and I can seem to work out what is running permanently. Any help or ideas (I'm pretty nooby when it comes to this though) would be appreciated.
Cheers,
John.
No such problem here. Just to confirm. Indeed this matter could have been raised in existing thread. Not to worry.
Where can you get the 3 skype client for Hero from? I am currently using the modified iskoot and didn't realise you could get the official 3 skype client now?
cambria83 said:
Where can you get the 3 skype client for Hero from? I am currently using the modified iskoot and didn't realise you could get the official 3 skype client now?
Click to expand...
Click to collapse
It's now available on android market, under skype 3 beta I believe. Or you can go to the three website, go to the skype area, select your phone and enter your number and they will send a text message with the address to download from.
Lucan, you're right, after a couple of resets and reinstalls it seems to be ok now...very weird indeed.
I've noticed when dialling a skype contact it actually believes I am dialing someone else and it comes up with another name in the dialled number lists.
Also not getting any contact details when someone dials in from skype, just details as 'skype contact'. I think i can live with this though...
PLease delete this thread if you think it is necessary,
cheers,
John
actually, scratch my last comments, it does seem to be chewing power when logged into skype...very frustrating!
pkspidermonkey,
Compared to iskoot I and several other have been using in the absense of Skype on 3, it is not too bad. I am sure there will be several releases before final.
So bought a Nexus 4. And I am so upset with one major issue with this phone: it's inability to properly record calling card numbers. I dial internationally a lot, and my phone company provided me with an access number. So all my outbound calls look something like this: 1 800 xxx xxxx , 011 xx xxx xxx xxxxx #
Now, if I dial ten different numbers (already stored in my contacts), the call log or history shows only the access number (the 1 800 number) ten times!!! I have tried this on a Samsung Galaxy S3, on a Samsung Galaxy Blaze, and they all have this problem. I also have an HTC One S, and some old HTC MyTouch and they DO NOT have this problem! An older LG Optimus T HAS this issue. What the heck?!?!
I have tried multiple dialers, and none can handle this properly. I have researched forums as much as I could, and it seems that this is a somewhat common issue with Google Voice calls... I have reached to Google and this is what they said:
"I understand you are having an issue using a calling card for international calls and not having them present in your call log. As of right now there is no current workaround for that and I apologize for the inconvenience. We frequently share customer feedback with our development team and will be sure to pass along your input."
and when I asked if this will ever be fixed:
"It is a known issue and there a solution to the problem is currently being worked on. Unfortunately I do not know when a solution will be available so I can't advise you whether it would be a good idea to return the device or not. If I can assist you further please let me know. Once again sorry for the inconvenience."
I fail to understand how this MAJOR FLAW can exist in the phone that promises to put "the world’s information at my fingertips", and yet, it cannot perform something as basic as remembering the very international calls it made...
Is there something I can do? Install? Am I stuck with HTC? Should I thus take a leap of faith and keep the Nexus 4 hoping for a fix to this problem?
My friend just retired and moved to Costa Rica. We tried Movistar prepaid and could not get his n4 to recognize the Sim. Does anyone have experience using the N4 with a Costa Rican sim? If so which carrier? Was I missing something? If there is somewhere I should have looked before posting please let me know. Its important I find an answer for him as he is legally blind and has little expertise in this area. Also if it matters, he needs to stay on 4.3 stock, rooted because of his difficulties seeing the updated dialer and call log. Thanks!
It depends on what you mean by "recognize the sim" do you mean the phone will not accept the sim or once the sim is inserted , data doesn't work. It could be something simple like APN settings or something else so could you please specify you're problem.
Also android runs voice navigation throughout its operating system which should help you're friend significantly. Dialer can also be changed by apk to provide a better experience for partially sighted users.
Phone : Nexus 4 /Rom : cataclysm / Kernel : Stock.
bladebuddy said:
It depends on what you mean by "recognize the sim" do you mean the phone will not accept the sim or once the sim is inserted , data doesn't work. It could be something simple like APN settings or something else so could you please specify you're problem.
Also android runs voice navigation throughout its operating system which should help you're friend significantly. Dialer can also be changed by apk to provide a better experience for partially sighted users.
Phone : Nexus 4 /Rom : cataclysm / Kernel : Stock.
Click to expand...
Click to collapse
Thanks for your response to my post! After inserting the sim and rebooting, the Movistar manager and I attempted to add a new APN, After inputting the correct information and selecting save, it would not connect and would respond with a No valid SIM warning. It would never retain the apn settings.
He has learned the layout and position of 4.3 and loves the voice commands, assistive technology, and google now, it has been a struggle getting him a setup he can use and I may someday post a thread concerning that process.
edit: the APN steetings that automatically loaded also did not work
Bump because my friend could really use my help!
Hey guys, this is actually a post regarding my mom's LG G2 we just got for her. We switched from Sprint and got this in the mail. I was excited to handle a new device as usual and was surprised to learn that it already had the Kitkat update. I soon discovered that outbound Wifi-Calling calls would not work at all, however SMS send/receive as well as receiving calls over Wifi worked just fine. There are no error messages associated with the Wifi calling, it will say connecting when dialing a call and then say call ended after about one second. I did some digging around and learned that T-mobile has not actually released 4.4.2 for the LG G2 so I assume that this may be related to the issue, considering the Wifi calling framework is something they add over Android. I assume that the phone my mom received has some sort of test build on it or something? Maybe you guys can help me out with it. T Mobile support were friendly but basically useless in getting this problem resolved, and said that the outbound calls is a known issue for this phone. I suspect that may be BS but maybe not.
Here's some info about the phone under software information:
4.4.2
baseband: M8974A-AAAANAZM-1.0.190034
kernel 3.4
Build JDQ39B
Software version: D80110g
Does any of this look familiar? Is this some sort of testing build? I may just try and send the phone back and get one with a more stable 4.3 if possible.
Thanks for any help or information you can provide.
That's 4.2.2 not 4.4.2
All the build numbers you posted except the 4.4.2 refer to 4.2.2
Looks like the latest version (7.0.140755802) has a bug whereas GSM feature code's do not work. Whenever any are used one is greeted with the error "Call settings error Network or SIM card error". This also happens if you go to phone>settings>Additional Settings or Call Forwarding. This did not happen with the previous version of the Google Phone Dialer (7.0.139927323). I've transferred the SIM to a Nexus 6P with the old version and everything works fine. Also a Nexus 5 and 4 with older dialers all works fine. It's only on the 5X which has the new version (installed today). Unfortunately it doesn't look like one can roll back to the older version. My carrier is Cricket Wireless, but since everything is fine on the other phones I don't think it has anything to do with the SIM card. I can make phone calls fine, it's just any GSM codes and attempts thru settings to change things like Caller ID reporting, Forwarding, etc.
Update: I went ahead and updated my 6P to the latest version of the dialer and didn't receive the error. Seems to be unique to the 5X. Since the final release of 7.1 is supposed to be out next week, I'll do a complete wipe and reload of the 5X at that time and see if the issue persists.
I could be wrong, but I believe your dialer app version is specific to the carrier, I am on Project Fi and have a totally different build version of yours 4.2.136732862, sounds like your problem is with the carrier...
mcerk02 said:
I could be wrong, but I believe your dialer app version is specific to the carrier, I am on Project Fi and have a totally different build version of yours 4.2.136732862, sounds like your problem is with the carrier...
Click to expand...
Click to collapse
I don't think so. I now have the same version of the dialer on both my 6P and 5X. 6P is able to do the codes and access the settings I mentioned fine, the 5X still throws the error. I'm able to make calls, receive send data on the 5X, just can't access some settings. I'm going to hang tight till the final release of 7.1 which is due to hit next week and see if the problem resolves. I'll also make sure that I flash the image fresh at that point.