Heya - Introductions

Hi all,
I've been a long time viewer and user of the info here in XDA, I think I was probably even a member here in the past. It's been a few years since I last rooted a phone, so seems this is where I need to be.
I've gone down this path as for the last few months, I have been putting up with the frustration of my new work phone (a Galazy A11). The only good thing about the A11 is its battery life, it is terribly underpowered and due to this I can't get it to stay connected to Android Auto & it doesn't support Paywave. So I decided that my 4 year old U11 with the latest Android was going to be more useful. So I have once again started down the journey of rooting and updating a phone - only to find 2 of the things I can't get to work are Google Pay & Wireless Android Auto (go figure!!!) - although wired Android Auto connects & stays connected which is a big improvement.
But anyway, I'm sure my adventure into getting into a deep and meaningful relationship with the hidden parts of my phone are just starting once more!

Lollylegs59 said:
Hi all,
I've been a long time viewer and user of the info here in XDA, I think I was probably even a member here in the past. It's been a few years since I last rooted a phone, so seems this is where I need to be.
I've gone down this path as for the last few months, I have been putting up with the frustration of my new work phone (a Galazy A11). The only good thing about the A11 is its battery life, it is terribly underpowered and due to this I can't get it to stay connected to Android Auto & it doesn't support Paywave. So I decided that my 4 year old U11 with the latest Android was going to be more useful. So I have once again started down the journey of rooting and updating a phone - only to find 2 of the things I can't get to work are Google Pay & Wireless Android Auto (go figure!!!) - although wired Android Auto connects & stays connected which is a big improvement.
But anyway, I'm sure my adventure into getting into a deep and meaningful relationship with the hidden parts of my phone are just starting once more!
Click to expand...
Click to collapse
Well now welcome to XDA! Officially.
And enjoy your stay

Related

[Q] Main GalaxyS bugs or bad features.

Hi! I hope to write in the right area, but if not I ask someone to move my post in the right one.
Now I have a HTC Diamond device, but I've to change it for a GalaxyS or an iPhone4.
I would like to buy a GalaxyS device, but I read many posts about bugs, lags, gps problems, so I wonder if it is a great choice this GalaxyS.
I like android and all the development opportunities around it (thanks to XDA), but it seems to be not so stable yet...
I flashed many ROMS on my Diamond in the past, so it's not a problem to do the same for my GalaxyS, but problems are fixed? The GPS works fine? Maybe not...
Maybe with Froyo 2.2?
iPhone4 is not so open as an Android device, but it's a very stable device!
What do you think about?
coming from a winmo background you're gonna love the galaxy s! its miles ahead in terms of refinements, polish and brilliant integration. The GPS problems are nothing so critical...its more of a sw fix im guessing. I live in India, and i have ZERO problems on my GPS....i feel the bug is something country/carrier specific.
there are many things to love and obsess with the galaxy s....go get yourself one, you sure wont regret it
While I'd love to echo what dreamtheater39 has said, I can't. It's a brilliant phone, but after having mine for just under a month, it's starting to lag like crazy, and in the last two days I've had a ton of dropped calls and the phone has switched itself off/crashed three times in the last few hours resulting in data loss because the power button doesn't respond (forcing me to hard-reset the phone).
All I can say is that, if you do get one, have an open mind. And make sure you don't get locked into a lengthy contract in case things do go awry.
same here GPS working great since day 1
http://forum.xda-developers.com/showthread.php?t=775450
Maybe I got a lemon
Maybe I got a lemon but I can not stand the i9000. I have 4 bugs that drive me crazy.
1. Market Place hangs at starting download. I have to do a factory reset to download an update an app.
2. GPS just stops working or it puts you on a different street when you are using navigation. The worst part is then it has to recalculate the directions twice, once for the wrong location and then again for the correct location, which is a real pain in the pocketbook when you are rooming.
3. Receives invalided cert from a hotspot connects the 1st time then never again. So I cannot use my hotspot at work, my old iphone connects no problem.
4. Does not always switch between wifi and mobile network. Have to go to airplane mode and back to get 3G network. (I tried changing the wifi sleep settings)
Mmmm...so maybe it's a good device, but I understand that who had an iPhone before it seems to be a step backward...is it?

[Q] Will GPS ever be "truly" fixed

Since some think that the GPS hardware (that can't be fixed by software settings) in the Captivate is crap, do you think that Samsung should use hardware from a different GPS provider in their next version of the phone? Does Broadcom have any GPS hardware in other phones that work well? Other than buying a Garmin phone, are there any other phones out there that use "true" GPS, as in one that you would find in a "real" handheld GPS device? I see/hear a lot of people returning their phones strictly because of the GPS not working well.
I'm just wondering if there will ever be a GPS fix for my Captivate, if the hardware is at fault. If it is a poor GPS chip in the phone, there's not much we can do about it, unless the GPS manufacturer updates their driver and they produce some type of software fix.
I updated my Captivate with the OTA update that claims to "fix" GPS performance. It has improved from never getting a fix to providing one relatively quickly. However it loses the fix moving, it loses the fix for NO REASON when stationary (sitting on a surface with a clear view of the sky), goes nearly a minute without updating at times and isn't accurate. People that are using it and saying it works great have never used a real GPS before. The Captivate is useful for location based services at best and hopefully with more improvements navigation.
I compared it side by side with a 9 year old Garmin eTrex and the ancient eTrex blew the Samsung out of the water. Initial fix on the Samsung was faster (thanks to AGPS) but while the Garmin hovered between 6-8ft CEP and the Galaxy S was about 32ft CEP. This makes the Garmin about 30x more accurate in my book.
This was both outside and INSIDE in my home. To the naysayers that say GPS shouldn't be working indoors please take a walk. It depends on the construction of your home. The fact that a 9 year old GPS receiver that was never known for its sensitivity beats the pants off off the Galaxy S really speaks to how much of a terrible joke the phone's GPS is.
If I could I would return the phone. This OTA update was AT&T and Samsung's fix for the GPS and I believe they're going to say it's "done". Because they'll claim to have fixed it already I hold out no hope that this issue will be further addressed and am upset I have the phone. GPS is a basic feature for such a well-spec'ed phone - we shouldn't be thankful when features work - we should demand that they do.
I'd say probably that's all Samsung can do for its crapy implementation of BroadCOM 4751 chip. The GPS chip may be the latest and greatest (newer than the one used in iPhone4, BCM4750) but we are the beta testers for BroadCom/Samsung as the chip is very new (released in April 2010) and never field tested in any devices.
I have no doubt that we will see great GPS performance from this chip later on from other phones or GPS devices. Just not from any of the current Samsung Galaxy S phones. There is only so much they can do to compensate in software for the bad hardware implementation. Ultimately they have to change the board design and/or chip designs to address the real issue. I just can't see Samsung willing to recall millions of existing SGS phones back and replace the motherboard on each one of them.
The update was certainly discouraging. The phone really has no ability to track you correctly on GPS when moving and it loses its lock frequently. Wasn't there a leaked vibrant rom that fixes the tracking part of GPS? Having something like that come to the Captivate is really the only hope we have left at this point.
I'm not a GPS expert, but since basically every phone that comes out these days has a working GPS, I really can't understand how Samsung managed to screw this up. I'm sure that GPS is quite complicated, but aren't the methods and alrogithms for calculating position from the data pretty well established at this point? I don't know why its this difficult for them to get this right. They souldn't have to reinvent the wheel with this; just implement an existing algorith. I wish I knew what is so challenging for them, it seems way to easy for this much time to go by without addressing this properly.
This needs to go in Q&A or General.
TheSopranos16 said:
They souldn't have to reinvent the wheel with this; just implement an existing algorith.
Click to expand...
Click to collapse
It is not the algorithm, it is the chip. For what ever reason, Samsung decided to use the latest and greatest, but untested, GPS chip that was officially anounced only the spring of 2010. Basically, we are beta testers for BroadCom for its BCM4751 version 1.0 sillicon. Of course, adding a slighly bigger or better GPS atenna inside the phone probably will help too but Samsung has to cut corners somewhere (they always do)
I'm also disappointed with the GPS in this phone. I have a standalone Garmin that I bought this summer, but its nice to know that I can use the phone if I don't have my Garmin with me...but I can't rely on this thing.
I had the Nexus One before this and its GPS was great. I used it on a 300+ mile trip between St. Louis and Chicago and it never lost its fix.
I like the Captivate better for its screen, true multitouch and better graphics processor (although I don't really notice a difference there).
I like the Nexus One better for more ROMs (Cyanogen), stock Android, WORKING GPS, first for updates.
IF (and that's a big IF), they can get GPS to be reliable while driving, then I will prefer this phone.
It is very frustrating. I purchased 2 Captivates, one for my wife and one for myself. Both phones are factory still. The wifes gps works excellently, fix within 5 seconds (indoors too).....whereas my gps couldn't find me if I was the only crumb on the plate.
I returned the first phone. The second phone handed to me worked just as my wifes did. Excellent gps fixes. This phone unfortunately had the turn off problem. If the phone was in my pocket for any period off time it would turn off.
I returned this one for a third phone. The third phone stays on but still has the gps problem.
Is it the device, the hardware or the software, you be the judge!
Sent from my SAMSUNG-SGH-I897 using XDA App
drez22 said:
It is very frustrating. I purchased 2 Captivates, one for my wife and one for myself. Both phones are factory still. The wifes gps works excellently, fix within 5 seconds (indoors too).....whereas my gps couldn't find me if I was the only crumb on the plate.
I returned the first phone. The second phone handed to me worked just as my wifes did. Excellent gps fixes. This phone unfortunately had the turn off problem. If the phone was in my pocket for any period off time it would turn off.
I returned this one for a third phone. The third phone stays on but still has the gps problem.
Is it the device, the hardware or the software, you be the judge!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Its still hard to say. Signs are starting to point towards hardware, but it could also just be poor drivers, which will eventually get fixed hopefully.
I've said this in another post.. but these phones are being produced on an assembly line - errors get made - the phones are all using the same hardware.
this is my #5 captivate - the last 2 phones were battery issues, but att replaced the entire phone.. I tested gps before I left the store with the new phone -
everyone needs to understand that there will ALWAYS be problems - It's technology. If your GPS didn't work within the first 29 days, take it back!
There is a reason Samsung is creating a "fix" for the GPS - they aren't RECALLING the phone because of a hardware problem. I will eat my words if the phone gets recalled because of a bad "GPS chip." But for now, if you are within 30 days and you aren't happy, please go return it, test the new phone in the store before you leave!
There is still SOME home for this chipset. Nokia is developing a device with the same chipset. I made a thread in i9000 - Android Development forum with the linux driver source code written by Nokia. We'll have to see. If Nokia releases a device with this chip and the GPS works, we know it's Samsung's fault.
Has anyone ever tried to get a comment from Broadcom about the GPS issues? Since its their chip and there are over a million Galaxy S phones out there, I would think it would be appropriate for them to weigh in on this...
born_fisherman said:
I've said this in another post.. but these phones are being produced on an assembly line - errors get made - the phones are all using the same hardware.
this is my #5 captivate - the last 2 phones were battery issues, but att replaced the entire phone.. I tested gps before I left the store with the new phone -
everyone needs to understand that there will ALWAYS be problems - It's technology. If your GPS didn't work within the first 29 days, take it back!
There is a reason Samsung is creating a "fix" for the GPS - they aren't RECALLING the phone because of a hardware problem. I will eat my words if the phone gets recalled because of a bad "GPS chip." But for now, if you are within 30 days and you aren't happy, please go return it, test the new phone in the store before you leave!
Click to expand...
Click to collapse
You have to realize that the percentage of the bad SGS with GPS issues are too high to be caused by any reasonable manufacturaing defects.
You can't test GPS properly in a store without going through a driving test. Period. The problem with the GPS is not about whether or not you get a lock, it is whether or not the phone can keep an accurate lock on you while driving. Unfortunately, most ppl didn't realize this at all.
Samsung will not recall the phone even if it turns of the GPS chip or motherboard is the problem. It is not some kind of safety issue.
TheSopranos16 said:
Has anyone ever tried to get a comment from Broadcom about the GPS issues? Since its their chip and there are over a million Galaxy S phones out there, I would think it would be appropriate for them to weigh in on this...
Click to expand...
Click to collapse
Broadcom made some small fixes in the driver. That's why with JH7, you can see your phone can lock on to more than 8 satellites now. Old drivers will only allow max lock of 8 satellites and minimal SNR value of 20. New driver allow lock on to more than 8 satellites and minimal SNR value of 10 or so. But unfortunately, it didn't improve moving accuracy.
So when you go to the AT&T store take the phone outside and the phone you are going to walk away with doesn't see any satellites, you should just take it and run?
I'm saying this with experience. I've had 2 phones that didn't pickup any satellites even after waiting 5 minutes.
My current phone immediately saw satellites and got a lock within 45 seconds.
Regardless if you are moving or not, the phone should be able to see satellites - I understand the problem is when you are mobile and keeping the lock, this is not my argument.
my argument is that people are still complaining that they can't get a lock even after the OTA update - Test your phone before taking it home. That's all. Not a big deal if you ask me! If your new LCD TV with HD tuner isn't picking up HD channels, you would bring it back right??
My gps was pretty terrible until I flashed Cognition the first version. Now my gps works amazingly and never has the blue circle of ambiguity. Very happy with the gps performance now. So much that I haven't flashed the cognition that is updated with JH7. Worried it could brea kit haha. might as well try though.
Yeah, the new one (Cognition v2.1) with OTA JH7 in it is pretty bad based on my reading. JH7 is an old firmware. Original Cognition has some files from T-Mo Vibrant JI2 firmware which is newer than JH7.
Our only hope is that the final version of Froyo has some improvement baked into.

[Q] Evervolv Jelly Bean - 3G connection unavail and sim self locking

Hi guys,
First of all, a great (really great !) thanks to all and everyone involved with the JellyBean evervol rom, it work very very well on my dear old N1...
Well, it works very well but not quite flawlessly for me, and since I have not been able to find complaint about this on the dedicated topic in the android dev section, I post my questions here :
Since about one week ago, I remarked that my phone seems often unable to use the 3G connection : I mean I have full scale network with 3G label in the notification bar, but the logo stays grey (not turning blue) and all data request meet a deadend (chrome, news, gmail, ...) while, if I turn wifi on, it works great ...
And since 2 days ago, I started to have another trouble : my sim card just keep locking itself without (apparent) reason, I have to enter the pin code nearly every 5mn ...
No idea of what may be causing that ...
OK, I think I will in some times fall in love with the Nexus 4, but my N1 still working great with this superb Rom, I would like to wait a little (for instance, the time for Google to announce a 32 Go version of their baby ...)
So many thanks to anyone who can help me puting some additional life into this dear N1 ...
For info, I'm running the 3.1.0p1 version of the rom with a 32.50.00.32U_5.12.00.08 radio and I'm running on the Free Mobile network in France ...
I don't know what additional information I could provide to help, or any diagnostic I can run ?
Thank you in advance for your help ...

Bluetooth is driving me nuts! Need help please.....

Hello everyone,
I'm having major issues with my Nexus 6 over the past 3 weeks or so.
I've had this phone for almost 2 full years now and love it, however, over the past 3 weeks the bluetooth function keeps turning off when I reboot my phone every night.
It NEVER did this in the past 2 years. Only the last 3 weeks. It seems to be some sort of battery saving feature, I would presume.
What drives me nuts, is I always like to have my bluetooth on, since I get in my truck and it auto connects to my GMC IntelliLink (which is also a problem).
So does anyone know why, all of a sudden, after reboot, bluetooth defaults to off and I have to manually turn it on every time? My Nexus 6 has been flawless up until now.
I've looked everywhere for an "auto start" option for bluetooth, but cannot find one. I have ZERO idea how this happened all of a sudden. I've been running the same ROM since last February with no problems (ROM screenshot attached).
As for my bluetooth truck problem, that started today. All of a sudden "phone audio" will not let me select the box, only "Media Audio" and "Contact Sharing" boxes are selected. Thus my Pandora plays over bluetooth, but my phone calls will not.
Also my Bose Quiet Comfort headphones used to connect perfectly with my Nexus 6, now I'm at work and I notice if I turn the headphones off, then come back and turn on, it'll say "connected to Nexus 6", but the sound is playing through the phone instead of the headphones, even though the bluetooth connection has been established.
Again, this is only over the last few weeks.
Any help would be greatly appreciated.
I'm willing to update to a new ROM or do a wipe, I just tend to live by the motto "if it ain't broke, don't fix it"........ except now it is broke and I want to fix it.
Thank you-
Paste a logcat here. A dev could take a look and help you out.
or
Backup your stuff and do a clean install of a new pure nexus or whatever rom, if it's still present after that, maybe it's just your battery starts to dying after 2 years.
Edit: I'm using crdroid as daily driver and have no bt issues
So glad you posted this, I'm having the same issue! After either a restart or just a period of time my Bluetooth turns to disabled. It is especially frustrating as I have it connected to my watch, which allows me to unlock with smart unlock. When the Bluetooth is disabled, I have to punch my pin in.
I am on stock 7.1.1, February update. I am rooted and flashed the Echo Permissions Fix. I was going to flash stock again this morning, but decided to check here first for a solution. I am just happy to know that it's not just me.
That being said, like @MVLJR, I recently flashed PureNexus ROM and that for me is when this began. I flashed back to stock via flashall, but it has not stopped the problem. Could it be a PureNexus thing?
As we have PureNexus somewhat in common, I am doing some searching on that page. I had previously posted there about it, but I don't think I ever got a response. Someone mentions it on Page 3417, I'll keep reading to see if I find a solution.
My post, by the way, is on page 3420.
I had a problem like this on Pure Nexus and flashed back to stock (N6F26R) to see if the problem goes away...
Previously on stock (release before N6F26R) and never had an issue. I use Bluetooth with a watch, fitness band and sometimes my Wife's Ford...
Sent from my Nexus 6 using Tapatalk
@muiriddin, did the problem go away for you? Because I flashed back to stock and the problem persists.
@MVLJR, I suspect that the problem is Android Wear 2.0 on our phones. Do you have a smart watch?
Edit: On the PureNexus forum, people without Android Wear are also experiencing it. So back to the drawing board. I still do not think it is your ROM.
Reading this thread reminded me of something I dealt with a while back, I don't know if this will do it for all of you, but I figured I'd post this. I screenshotted a reddit thread that fixed the problem for me. I can't remember if what I experienced was the same as all of you, and I am not having the problem now. But I hope this helps. Please see the attached screenshot.
I don't have an android watch, but I do have a fitbit and don't have any problems with it.
A little update, I cleared my Bluetooth cache and changed the name of my device, which seems to have helped.
My Bose headphones now autoconnect like before.
However, my Bluetooth still shuts off after reboot. My GMC Intellilink still won't let me select "Phone Audio" either.
I think I'm going to flash a new ROM this week, which sucks because I've grown attached to the Pure Nexus ROM.
Can someone show me how to post a logcat?
Thanks
This (and similar) bluetooth issues have been reported on the nougat product pages. It's not unique to PureNexus or the Nexus 6.
Reports are that 7.1.2 (beta) fixes the issue on devices that have access to it. Hopefully a fix comes down the pipe for the Nexus 6 as well, as I have some of the same issues.
Similar posts can be found on the nexus6 and googlepixel subreddit pages.
My question is, what prompted this?
I've had the same ROM for a year, no OTA updates. Had to be an app update, correct?
No other way to explain how it worked for a year, now problems all over the place
You've been using the same ROM, but updating the version of the ROM, correct?
And the ROM updates are based on updates made to Android by Google.
So if a bug makes it into Nougat, it will (generally) make it into the modified ROM as well.
Incorrect, I've been on the same version of Pure Nexus since last February, screen shot in original post
I take it the fix I posted didn't help? I was really hopeful that it was the same issue and that would fix it up.
I haven't tried it yet, at work right now, I'll give it a shot later.
I'll update my findings.
Thanks
Will keep my fingers crossed. One thing to note, when doing that fix, it *will* wipe your bluetooth auto-pair devices. So don't fret if nothing automatically connects afterwards. You have to repair everything.
It is not a new problem, there are many threads in the Q&A forum if you search. Here is one:
https://forum.xda-developers.com/nexus-6/help/bluetooth-off-reason-pattern-t3435436
(there are more links and suggested workarounds in that thread from me)
That said, installing the AW 2.0 DP 4 totally solved my BT disconnects from my Huawei watch and LG stereo headset.
The changelog on the latest Huawei AW 1.5 mentions BT issues, but I have not tried it.
AW 2.0 official is supposed to start rolling out OTA tomorrow, so we shall see. (finners crossed tite )
I'm on Jan 21 PN 7.1.1, latest AW app. I have no suggestions of those having issues with no Android Wear, but there are threads here with suggested workarounds that solved this for many of us before, you might want to check them.
@Morpherios and @MVLJR
I don't know if it's of any note, but one of the actions I attempted in trying to fix mine was to reset all network settings via the "More" option in Wireless & Networks settings (I backed up wifi settings in advance). That's essentially a nuking of all network settings, including wifi, cell, and bluetooth. It did not resolve my issue.
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening. How the software on the watch (as opposed to the AW app on the phone) would be causing bluetooth to crash, I'm not sure. But it's not outside the realm of possibility.
larrysteeze said:
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening.
Click to expand...
Click to collapse
My words were / are different than that:
AW 2.0 DP 4 totally solved my BT disconnects
That means they do NOT happen any more, since Dec 11, 2016 when I installed AW OS 2.0 DP4 was released and I installed it on my watch. Not. One. Disconnect. None. Nada. Zero. Zip. Zilch. Nein.. :victory:
BT devices communicate both directions. The watch CAN control the phone, and was turning off BT. It was obvious when it happened, when my headphones prompt "Out of Range, trying to connect" (I came to hate hate that voice prompt )
I would immediately open the AW app on the phone at disconnect and was prompted to turn on BT because it was off.
@Pkt_Lnt I completely agree that it BT communication is two-way...I stated that it's not outside the realm of possibility because there are a number of factors that could do it, including the phone receiving a message it simply doesn't know what to do with and causing a fault. This could explain my bluetooth share crash messages that I received on occasion.
It's encouraging to know that it's fixed with AW 2.0 for you. I hope it carries through to me when I get the update. If the OTA doesn't drop tomorrow, I may have to flash the DP as well.

AA Shutting down after screen unlock

Hi all guys, I've been missing a long time from here, so please be care enough to forgive me if I posted the thread in the wrong place.
I'm currently using Android Auto and enjoying very much the amazing work made from Gabriele (AAAD, of which I payed the PRO version in order to help the developer's job).
I'm running AA version 6.3.611314 (downgraded from 6.4, because otherwise AAAD didn't work, since AA 6.4.... doesnt' let you show the apps installed apart from the official ones); Ford Focus Active with Sync 3 updated to 3.4 version, a Galaxy Note 20 Ultra5G (European) with Android 11.
Everything works fine, even AAAD installed programs.
The only problem is that every time I unlock the phone it disconnects from AA and then it starts again from the beginning. I opened the DEv Options in the phone settings and chose as standard setting for the usb - File transfer / Android Auto.
My question is: Why this disconnections happen and HOW can I fix it? I currently drive with the phone unlocked and, useless to say, it doesn't charge as much as it would if the screen had been off. I alredy tried with other cables, even with a Sam S9+ original one.
Thanks in advantage, any help is appreciated.
Same here, S10+ latest official, AA 6.4.611714-release, Ford Sync 3.x .
Doing so for about a week (or some more). At phone unlock, AA is crashing to Sync interface, and phone is asking for permissions in order to start Android Auto again (need to press Allow, otherwise AA will not start!)
Thx!
Same here , s10
It'd be nice to know whether the problem starts from the phone version , the AA version or from the car itself.
gidannifico said:
It'd be nice to know whether the problem starts from the phone version , the AA version or from the car itself.
Click to expand...
Click to collapse
I can confirm that the issue is related to the last Sammy update , I have downgraded to may update , now aa works perfect
Guys, Google just updated the discussion thread three days ago:
Thanks for all the reports. We informed the Samsung team and they have applied a fix on an upcoming upgrade as part of the regular July maintenance release to resolve this issue. Please keep checking for system updates on the device.
Click to expand...
Click to collapse

Categories

Resources