Related
Well, i took the plunge today, and went out and got one sim free. I had concerns that the gps would be a bit naff, and that there may be screen defects, or sluggishness and all the other commonly complained about things on here. However, in reality, non of these things were evident. It just goes to show that sometimes you can read too much and put yourself off buying a device on these fora. Which I nearly did. So, i'm really pleased with mine, screen is just great, gps is very good, not noticed a great deal of lag, just little hiccups here or there maybe, but that's it. Certainly nothing more than i got from my iphone 4 when it's ram was a bit pushed. So, if you think you might be put off, don't be, it's just great
+1 i have the same experience with my VZW GN. A hickup here and there, the AMOLED screen has the linen appearance with whites on low brightness, but overall I'm happy with it.
My colleague's did burn through a lot of battery this morning, but I just unlocked and rooted it for him so we will see if this was something he installed.
+1 excellent device
Sent from my Galaxy Nexus using xda premium
I disagree with the OP.
My Nexus while at first seemed great actually has a few issues that are making me second guess my decision to return my Razr.
1. When switching from Wifi to 3g/4g my data stops working. I have to switch to airplane mode then back to restore it.
2. The speaker phone is aweful. While in the car its completley useless. I spend half of my conversation repeating myself becuase the other person can't hear me. I did a comparison with my wife Incredible and it was night and day.
3. When typing on the keyboard I notice that they keys being registered are not the keys I am pressing. Not all the time but on average its worse than the razr. The upside of this is that the autocorrection of ICS fixes the mistakes so its a wash in the end but still annoying.
4. MTP file transfer fail often when transfering files. I ended up using a wifi ftp server to get my titanium backup files.
5. Audio breaks up when trying to stream over bluetooth. Worked flawlessly on my Razr.
The last two are not so much bugs as design limitations.
6. No SD slot...I mean really... why can't nexus phones have sd cards.
7. No voice search button with the rest of the "buttons"
This is kinda what i meant, these problems seem to be device specific. Generally, they are ok, but as was the case with the sgs2, the early batches seemed dubious and the software was full of bugs. If you are lucky tho, (as the majority will be). All will be fine.
Forgot about the bluetooth audio streaming issues. Updated my post with that as well.
So far I've had no problems with Bluetooth audio either. Although I have not tested it extensively. Only tried it out to check it.
trevoryour said:
Forgot about the bluetooth audio streaming issues. Updated my post with that as well.
Click to expand...
Click to collapse
Ooooh Please can you elaborate on this. BT/A2DP Streaming is essential for me.
Seems like ICS gets faster as you use it more. Also, most apps are not totally designed for ICS; Yet.
I would say I am more likely to share a bad experience post on the internet than a good one. I am sure there are a lot of people who are happy with their device that just don't feel the need to say so online.
I agree with the OP. You should always give something a go and if it don't work out there is usually a warranty.
Sent from my Galaxy Nexus using XDA App
I agree with the OP, most of my fears about the phone have not come to life. No problems with the signal, although if there is a fix, I hope that it will help when I am at work. zero ****ing bars..why is every place I work at built like a bomb shelter with no signals coming thru???
i have faith someone will make a bigger battery for this thing...
cenwesi said:
Ooooh Please can you elaborate on this. BT/A2DP Streaming is essential for me.
Click to expand...
Click to collapse
I tried streaming spotify over the bluetooth audio link in my Ford Sync and the audio stream kept breaking up as if the phone was really far away or something. I had seen this before with my Incredible when it first came out but a reboot usually fixed it. I rebooted the nexus and the problem remained.
I also agree with OP, this phone has been perfect before. I was espeically surprised with the GPS lock i was getting. with my Charge i had to go outside and stand still for like 30 seconds to a minute to get it to lock on, the Nexus locked on almost instantly sitting in my chair inside my house...
Clearly all of these issues are luck of the draw. My phone has had no such issues. I suppose some phones having these issues and others not might indicate lesser build quality, but even iPhones have hit and miss problems like this.
Sent from my Galaxy Nexus using XDA App
Hi everyone. I, as many others, have been having an issue with my microphone cutting out during a phone call. I have a roooted Verizon Galaxy Nexus running the 4.0.4 leak, but it appears that for everyone who is having this issue it doesn't matter which ROM you're running or even if you're rooted or not.
[EDIT]: It per one of the posters below, this is not so much a "microphone" issue as it is an "outbound audio" issue. Unfortunately I can't edit the subject name to refer to this, but for me personally when I've been doing google searches on this issue the first word that came to mind anyway was the word "microphone" or "mic" anyway.[/EDIT]
People have been trying different things like flashing different radios, muting and unmuting, turning off voice privacy, etc., but it seems that nothing helps. Not even several hardware replacements or sim card replacements.
However, I did notice a pattern from different forums, etc. It seems that some people either have the problem all the time, or not at all, and it seems that some people reported that traveling to different metro regions affected whether or not they had the issue.
So I was curious to see if the pattern has to do with geographical location as an issue with Verizon's network, vs. hardware/software issues.
This poll has 50 possible answers, 1 for each state. Please answer this poll ONLY if you ARE experiencing this issue, and please only vote for your state if you live in the state's capital. For example, I live in the Denver metro area, so I would vote for Colorado. However, if I lived in Fort Collins or Grand Junction, I would NOT vote at all.
If you have traveled and visited another state's capital and have had this issue there, you can go ahead and vote for it as well.
It will be interesting to see if we have a lot of hits in certain major metro areas and none in others.
[EDIT2] Also, if you don't have the problem at all, go ahead and post a comment with your location. In fact, it would be interesting to see if people don't have the problem but others in the same city do. [/EDIT2]
Thanks!
I thought I had this issue just turns out my pinkie was covering the microphone its king of poor positioning watch, the way u hold the phone after changing the way I hold it no one complains they can't hear me
Sent from my Galaxy Nexus using XDA
TLDR: I kept having people telling me that I sounded like a robot.
Sent from my Galaxy Nexus using XDA
I had this problem on back to back to back phone calls this morning. Horrible.
Sent from my Galaxy Nexus using Tapatalk
My wife and I are both having the issue in Richmond, VA but I could only vote once for myself. She has reverted to an old droid x as she cant rely on the phone anymore.
Might be a little late, but maybe we should collect ZIP codes instead? Then we could use this tool: http://batchgeo.com/
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA
I voted. I'm in South Carolina. I'm pretty sure it's NOT a regional problem though.
twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
If holding the phone different worked for you, then you don't have the issue this is referring to. This issue can happen with a wired headset, Bluetooth headset, on speaker phone, which none of these would be affected by how you are holding the phone considering you aren't using the mic on the phone. The people on the other end hear a series of clicking sounds, then no audio.
twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I realize you're trying to help, but you really don't understand the issue. The OP really didn't describe it properly, as it's not a "microphone" problem, but rather an "outbound audio" problem. I use mine at work as a speakerphone with it sitting on my desk, and I lose outbound audio all the time. Others have the problem with a bluetooth headset. I don't doubt that there are some people who have had an issue with covering the microphone hole, but that is not what this thread is about. This is an ongoing issue that people have been troubleshooting for months, and Verizon/Samsung is supposedly working on a software fix to resolve it (I'm not holding my breath).
I had the same problem on my 2 rogers GNs(GSM version)
after I upgrade my baseband to i9250xxkk6, the problem gone
I like the OP enthusiasm, but I don't think you will be able to glean any info on location. Owners are too spread out. Maybe in a few months.
I'm in Raleigh, NC.
I got my phone on release day and noticed this problem a few days later. I've since replaced the phone, then the SIM card (a theory that it was SIM-card related was floated over at AF).
After changing the SIM card the problem seemed to go away for a couple of weeks, but it came back with a vengeance.
I hate the idea of getting a "refurb" from Verizon (I put refurb in quotes because, based on the FIVE refurb'ed Incredibles I had, I'm pretty sure they don't do anything except replace the glass if it's scratched), but I guess a functional refurb would be better than an aggravating semi-functional new phone.
twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Click to expand...
Click to collapse
I can't help but be reminded of Steve Jobs.... "You're holding it wrong!"
I'm glad your phone is working properly but, as others have noted, this is most definitely not the problem we're talking about.
gabe23 said:
I realize you're trying to help, but you really don't understand the issue. The OP really didn't describe it properly, as it's not a "microphone" problem, but rather an "outbound audio" problem. I use mine at work as a speakerphone with it sitting on my desk, and I lose outbound audio all the time. Others have the problem with a bluetooth headset. I don't doubt that there are some people who have had an issue with covering the microphone hole, but that is not what this thread is about. This is an ongoing issue that people have been troubleshooting for months, and Verizon/Samsung is supposedly working on a software fix to resolve it (I'm not holding my breath).
Click to expand...
Click to collapse
Thanks for clarifying, I edited my original post, unfortunately I can't edit the subject name, but you're right, it's outbound audio and not mic. Thanks again!
adrynalyne said:
I like the OP enthusiasm, but I don't think you will be able to glean any info on location. Owners are too spread out. Maybe in a few months.
Click to expand...
Click to collapse
You're right, I was caught up in it at the moment and thought it would just be interesting to see how the issue maps out, but this little poll in no way is a troubleshooting tool, more of a type of infographic maybe?
The only fix is going to be a software update from el goog. can't wait for it!!!
I just got off the phone with Tech Support about this.
The Level 2 agent found an internal support document about the problem and read me what it said for the fix.... It says that the upcoming software release is going to cover this. It goes on to say that the tentative (dammit) release date for the software release is late March.
I don't want to trade in the new phone that I've babied since day 1 for a refurb of unknown quality if a fix is coming within the next couple of weeks.
If they don't release the update soon (which wouldn't surprise me at all), I'll probably just flash a new ROM & radio.
Flashing a new rom/radio does not help. I'm running nothing stock (leaked radios, CM9 Kang Nightly, Franco Nightly) and I still have this issue.
Good to know I'm not alone, Minnesota is currently winning! :-\ :-(
AnotherHiggins said:
I just got off the phone with Tech Support about this.
The Level 2 agent found an internal support document about the problem and read me what it said for the fix.... It says that the upcoming software release is going to cover this. It goes on to say that the tentative (dammit) release date for the software release is late March.
I don't want to trade in the new phone that I've babied since day 1 for a refurb of unknown quality if a fix is coming within the next couple of weeks.
If they don't release the update soon (which wouldn't surprise me at all), I'll probably just flash a new ROM & radio.
Click to expand...
Click to collapse
I was told the same thing by VZW support, but mid-march... which is NOW! I'm really getting sick of this. Ready for the fix and some info.
I have the same problem on the GSM version. Also Raleigh, NC.
It's a bit weird that all the decent ROMs are still on LJC, even after a few weeks with LK8 on the scene... Is there some valid reason for this, or is it simply because the GN2 development section is underwhelming compared to the GS3/etc?
Wifi issues, and until recently the inability to go back to older firmware mostly.
Interesting, I haven't seen any WiFi issues. Samsung devices always have crap radios, and LK8 seems on-par with the other releases.
Jellybomb, H20 and MIUI are great Roms and that's why they're on LK8. Hehe
Sent from my SPH-L900 using xda app-developers app
It happens in certain scenarios and im speaking from experience. I was unable to connect to a completely open network.
The GS2 had crappy radios, I would not say that about the Note 2.
Deuces.
JellyBomb is great in function, but on every device I've ever used it on, the theming causes problems. Fonts covered, hidden, etc due to the blue. Guess I'll try it again.
Itchiee said:
It happens in certain scenarios and im speaking from experience. I was unable to connect to a completely open network.
The GS2 had crappy radios, I would not say that about the Note 2.
Deuces.
Click to expand...
Click to collapse
This. And also simply because the devs don't want to work with a leak. Who would? Also I prefer few roms with less bugs than a variety with problems.
Sent from my SPH-L900 using xda premium
ScrapMaker said:
It's a bit weird that all the decent ROMs are still on LJC, even after a few weeks with LK8 on the scene... Is there some valid reason for this, or is it simply because the GN2 development section is underwhelming compared to the GS3/etc?
Click to expand...
Click to collapse
LJC works with fewer issues more often for more people than lk8. Many devs stick to it because of all the bugs that stem from lk8.
Sent from my SPH-L900 using Tapatalk HD
I know a lot of devs only upgrade to official releases and newer doesn't always equal better as well
-TeaM VeNuM Like A Boss
-Galaxy Note II Edition
Itchiee said:
It happens in certain scenarios and im speaking from experience. I was unable to connect to a completely open network.
The GS2 had crappy radios, I would not say that about the Note 2.
Deuces.
Click to expand...
Click to collapse
Compared to my HTC Evo series (any of them,) I'd say it's pretty obvious all the radios are quite inferior. That's good information that this firmware might contribute to that though. Thanks!
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
The Chameleon bug played a big role I think in people avoiding upgrading to LK8. While it didn't seem to cause any real damage, it was annoying as hell not only for the user experiencing it, but also the devs and other members having to see issues and questions related to it constantly. The bug has been squished, but I think the fear still lingers lol
thunderwagn said:
The Chameleon bug played a big role I think in people avoiding upgrading to LK8. While it didn't seem to cause any real damage, it was annoying as hell not only for the user experiencing it, but also the devs and other members having to see issues and questions related to it constantly. The bug has been squished, but I think the fear still lingers lol
Click to expand...
Click to collapse
I was one of the early catchers of that bug, and was vocal about getting some dev involvement. At the time it was a permanent error, and a pain in the a$$, I had the choice of LJC with HFA/chameleon FC errors (permanent, no matter how it was wiped back to stock), or no wifi.
Thanks to Garwynn, EvilKoncepts, a pal that did testing for them (can't remember his name), there is now a verified fix for it. (Has to do with LK8 changing carrier partition).
So right, most devs don't want to mess with leaks for official releases.
I won't touch it, at least not for now. LK8 has some nice little features, but I'll hold out for a bit, hope a (better? official?) version gets posted by Sammy for SxTp to bring us.
personally i havent seen any "bugs" in lk8. i've never had wifi problems and most everyone who has ran ProjectROM hasnt either. if you build off a stable base the only real bugs are usually caused by bad flashes, restoring backups and other misc crap. i'm not saying there arent bugs in roms because someone always forgets something but it's usually user induced not matter how much you dont want to admit it.
t3project said:
... the only real bugs are usually caused by bad flashes, restoring backups and other misc crap. i'm not saying there arent bugs in roms because someone always forgets something but it's usually user induced not matter how much you dont want to admit it.
Click to expand...
Click to collapse
normally, I might agree with you, having seen most issues caused by user negligence/ignorance. and fixed by proper procedure being used to reapply a ROM/Odin a stock. but in my (and several others) case, this was on Stock rooted, with the SxTp Stock leak applied. Wifi died for no reason after aprox 24 hrs use. No amount of wiping/resetting to fact-default would fix it.
But going back to LJC did, while bringing other (well documented) problems with it.
t3project said:
personally i havent seen any "bugs" in lk8. i've never had wifi problems and most everyone who has ran ProjectROM hasnt either. if you build off a stable base the only real bugs are usually caused by bad flashes, restoring backups and other misc crap. i'm not saying there arent bugs in roms because someone always forgets something but it's usually user induced not matter how much you dont want to admit it.
Click to expand...
Click to collapse
The only real bug I've found in lk8 is the wifi issue, it seems to not like certain wifi frequencies or channels, as it will connect to some routers but won't connect to others. Could possibly be an issue with the wifi supp or wifi conf files. The other big issue is the carrier partition upgrade in lk8 causing issues when going back to ljc
I like to break stuff!
I try any and every new firmware update with the HOPES AND PRAYERS that Samsung will fix their effin' horrible Bluetooth stack... worst of any device I've ever used. CM10 fixes it, but right now that's not a viable option, especially since I like having the SPen...
I hate that when I have my headphones plugged in, sounds still blurt out the speaker... wtf?
When I'm in the car with the headphone jack connected to my aux port, and the BT set to hands-free to my OnStar, I have to yank the audio cable out while driving just to answer. Pretty stupid. HTC, Palm, Motorola, etc all have this figured out, but not Samsung. All their Android smartphones do this.
ScrapMaker said:
I try any and every new firmware update with the HOPES AND PRAYERS that Samsung will fix their effin' horrible Bluetooth stack... worst of any device I've ever used. CM10 fixes it, but right now that's not a viable option, especially since I like having the SPen...
I hate that when I have my headphones plugged in, sounds still blurt out the speaker... wtf?
When I'm in the car with the headphone jack connected to my aux port, and the BT set to hands-free to my OnStar, I have to yank the audio cable out while driving just to answer. Pretty stupid. HTC, Palm, Motorola, etc all have this figured out, but not Samsung. All their Android smartphones do this.
Click to expand...
Click to collapse
I don't have any issues with BT or audio over the 3.5mm jack. Although I don't have BT in my car I use a headset while I'm working and will have headphones on in the other ear and it switches back and forth just fine
I like to break stuff!
I've never once had that work properly with the stock firmware, or even custom ROMs, (aside from AOSP.) If I have BT attached to hands-free only device, and playing music over 3.5mm connection, it will continue to play over the 3.5mm despite having the BT attached. Maybe something changed in LK8 that I didn't pay attention to. This holds true for the S3, S2, and GN2 that I'm aware of.
ScrapMaker said:
I've never once had that work properly with the stock firmware, or even custom ROMs, (aside from AOSP.) If I have BT attached to hands-free only device, and playing music over 3.5mm connection, it will continue to play over the 3.5mm despite having the BT attached. Maybe something changed in LK8 that I didn't pay attention to. This holds true for the S3, S2, and GN2 that I'm aware of.
Click to expand...
Click to collapse
I'm using ljc. Was stock but I've been building my own rom off of the stock OTA and haven't even messed with anything BT or audio out related and have no issues. Maybe it has something to do with your BT device itself, perhaps it and the phone aren't communicating properly after its been idle for a while. I had an old Motorola BT headset that would go idle/sleep and never wake up unless I pressed a button on it so I'd have to answer the call with the phone then press the button on the headset to switch over
I like to break stuff!
Now that the phone has been out for about half a year (1 month in the US), have any annoying/troubling issues been found?
For example, I was told by a manager at AT&T that some people who have the HTC One are complaining that the phone literally gets too hot to hold after "extended" video recording. They've only seen it with a few phones (owned by their salespeople), but it's been reported...
I've read both great and horrible reviews about the camera on the OGP, and I'm wondering if maybe LG is sourcing components from various vendors [something akin to TV manufacturers using display panels made by various manufacturers in models with the identical model number (AKA "the panel lottery")]. If that's correct, then maybe you get a good one and maybe you don't...but that's what I'm trying to find out.
I've read a few reviews/postings that some people had issues with battery life which turned out to be bad batteries. Anyone have that?
So, with that said, is there anything that seems to be out of sorts with the OGP?
The only issue I can find is the Wifi is junk.
raduque said:
The only issue I can find is the Wifi is junk.
Click to expand...
Click to collapse
Care to elaborate? I've not noticed any issues with mine.
It connects fine to both my routers, but will not sustain a stable data stream. It also seems far slower than it should be. Speedtest.net app runs about 2-3Mbps.
Sometimes, the test won't even complete, the Wifi will disconnect and reconnect.
It transfers fine for about 5 seconds or so. I just tried watching a free video on Google Play, and every 5 seconds the stream stalled. Web pages take forever to load, and forget about downloading a big app.
I guess I'll have to call AT&T, or visit a store. I paid full retail for this thing.
Edit: My routers are both a little bit older, a Belkin F5D7230-4 WirelessG and a Netgear WGR614V9, but I've never had this type of issue with any other device.
Edit2: I rebooted everything in sight, including (but not limited to) my routers, my cable modem, my switches, my WHS and the OG Pro. Seems to be more stable now, but still a little slow, around 2Mbps downstream.
There's only two issues with the thing, it's too good, and it's only on AT&T.
Seriously, there are a few niggling things.
1. The QSlide bar takes up too much space in the notification shade. Luckily, once you root, there's a fix around here somewhere for it.
2. The side buttons are very VERY shallow, to the point where even if you put on a SKIN the buttons are hard to feel and even get to. Still figuring out what to do about that one.
3. Not enough accessories. This is a very real consequence of it only being available on AT&T here, it's just not going to be as popular with the accessory makers as the Galaxy S4 and HTC One, which are pretty much available on every carrier.
raduque said:
It connects fine to both my routers, but will not sustain a stable data stream. It also seems far slower than it should be. Speedtest.net app runs about 2-3Mbps.
Sometimes, the test won't even complete, the Wifi will disconnect and reconnect.
It transfers fine for about 5 seconds or so. I just tried watching a free video on Google Play, and every 5 seconds the stream stalled. Web pages take forever to load, and forget about downloading a big app.
I guess I'll have to call AT&T, or visit a store. I paid full retail for this thing.
Edit: My routers are both a little bit older, a Belkin F5D7230-4 WirelessG and a Netgear WGR614V9, but I've never had this type of issue with any other device.
Edit2: I rebooted everything in sight, including (but not limited to) my routers, my cable modem, my switches, my WHS and the OG Pro. Seems to be more stable now, but still a little slow, around 2Mbps downstream.
Click to expand...
Click to collapse
my WiFi works great and I get a good range. I would look into getting a new router,I had this issue last year with all my Samsung phones once I got a we router things worked out great, Remember tech has a short life span you have to upgrade at times to keep everything on par.
Sent from my LG-E980 using xda premium
the frevia
nthknd said:
my WiFi works great and I get a good range. I would look into getting a new router,I had this issue last year with all my Samsung phones once I got a we router things worked out great, Remember tech has a short life span you have to upgrade at times to keep everything on par.
Sent from my LG-E980 using xda premium
Click to expand...
Click to collapse
Sound seems low on mine, even at full volume.
Shadowjack1965 said:
Sound seems low on mine, even at full volume.
Click to expand...
Click to collapse
It blasts my ears off with headphones, but I can easily crank my head unit to max and it's not anywhere near as loud of my NoteII was. I should be able to compensate by adjusting my gains, though.
Clipped voice commands in navigation
I read in another thread that at least 2 users were having issues with the voice commands during navigation. Their issue is that when the OGP speaks a navigation command, the audio stops in mid sentence. The last few words (or parts of the words) are clipped off. Example: instead of "turn left in 4 miles", they are getting, "turn left in 4 m", or instead of "proceed through the roundabout", they get "proceed through the roun".
Is anyone else having this issue? I'd be curious also if your phone is not having the issue.
My email client crashes every time I try to open an email. Used to work. Tried clearing data still crashes. Only problem so far.
Sent from my LG-E980 using Tapatalk 2
raduque said:
It blasts my ears off with headphones, but I can easily crank my head unit to max and it's not anywhere near as loud of my NoteII was. I should be able to compensate by adjusting my gains, though.
Click to expand...
Click to collapse
Wonder if it's just my particular unit somehow. Now I'll have to research adjustments that could make a difference.
Thanks.
Shadowjack1965 said:
Wonder if it's just my particular unit somehow. Now I'll have to research adjustments that could make a difference.
Thanks.
Click to expand...
Click to collapse
It could also be your headphones. I'm using a pair of Samsung OEM S3/NoteII headphones (all the controls work correctly).
When I mentioned adjustments, I meant to the amps in my truck, where 90% of my listening takes place.
I posted above about some users getting clipped voice instructions with navigation. I have not tried that yet but i found another voice issue. I don't know if it is due to an app or the phone. Using an NFC app (NFC Task Launcher), i have it set to read the time aloud when i tap an NFC tag to set my alarm. When it reads the time, it clips off the minutes and only reads the hours. For example, if i set the time for 11:30, all it says is "eleven", and cuts off the "thirty". Anyone else having voice issues?
Only actual issue I have is with the search feature in the contacts. When typing a name, it seems to reset or clear out the search field when you type more than 3 characters.
Anyone else seeing this?
Other than that, I love this phone. (I don't consider the slow progress on unlocking the bootloader to be an issue. The DEVs will crack this thing shortly. (They do have lives.)
Sent from my LG-E980 using xda premium
This phone is so far so good. The only thing I find uncomfortable is that when you exit your favorites tab from your phone app either by back or home button, and then when you hit phone again, it always brings you to the dial tab. It's kinda annoying since I never had that happen to me before on other phones.
Hey
So I'm pretty confident this is going to be my next phone most of the reviews have been favourable and Googles support in terms of updates ect is a big deciding factor.
Just wondering what this community's thoughts are in terms of community dev for the Pixel? I understand is very early days so far so please dont jump on me. I'm just curios if we are expecting this phone to have similar support here like the Nexus devices did? I'm a flash-a-holic however when I got my Note4 here in the UK, somehow I got the C (Exynos) variant where else almost every other Note4 I've seen here in the UK has been F (SD805) so I've missed out on a lot of Non-Samsung rom's for the last couple of years, before that I was spoiled for choice with my S3, and I'd very much like to get back to flashing several times a week playing around seeing what I like and what I don't like.
Anyway again, I know it's early days and it's hard to predict the future but some opinions are best guesses would be really helpful to make my decision and hopefully get what I want from my device this time....
Happy Pixeling
The phone is buggy as hell - Bluetooth is buggy, Do not disturb mode is buggy, Project FI / cellular connection is buggy, sometimes Google Services just straight up crashes.
To be honest I prefer the less buggy experience with Samsung phones. This frequency of updates Google likes to advertise, it's a blessing and a curse, and for all the bad reasons - they need to update frequently to fix bugs, but with each new update, they seem to introduce new bugs.
I haven't had any issues with my Pixel XL? Maybe because I haven't upgraded to 7.1.1?
Samsung phones are slow and sluggish as all getout IMO.
I have no bugs, great battery life, and the phone flies. Best out of the box experience I ever had. With that being said, I to, hope development picks up. Think with the dual partitions, and phones lack of availability is part of culprit. Once those two things straighten out, well this is a nexus except for the name
No bugs to report here. Everything has been flawless so far.
Development WILL pick up. The Nexus 5X sold at half the price of this phone and it still took a few months for development of truly custom ROMs and kernels to get into high gear.
I have been loving the phone. I got mine at launch and have had very little issues. Everything is fast and stable.
nabbed said:
The phone is buggy as hell - Bluetooth is buggy, Do not disturb mode is buggy, Project FI / cellular connection is buggy, sometimes Google Services just straight up crashes.
To be honest I prefer the less buggy experience with Samsung phones. This frequency of updates Google likes to advertise, it's a blessing and a curse, and for all the bad reasons - they need to update frequently to fix bugs, but with each new update, they seem to introduce new bugs.
Click to expand...
Click to collapse
I've had zero issues with mine on 7.1 or 7.1.1, have you tried a reset? I know 5 other people with the Pixel and they all love it and have had no problems.
nabbed said:
The phone is buggy as hell - Bluetooth is buggy, Do not disturb mode is buggy, Project FI / cellular connection is buggy, sometimes Google Services just straight up crashes.
To be honest I prefer the less buggy experience with Samsung phones. This frequency of updates Google likes to advertise, it's a blessing and a curse, and for all the bad reasons - they need to update frequently to fix bugs, but with each new update, they seem to introduce new bugs.
Click to expand...
Click to collapse
Sounds like you have a lemon. Had a black 32gb and upgraded to a silver 128gb because I had run out of space. Both had no issues. I'm actually amazed at the speed and smoothness of the overall user experience.
I had an LG V20 right before I traded in the 32 for the 128. It was very underwhelming. Although I appreciate the larger screen real estate, it's quality just wasn't on par with the Pixels. Colour uniformity issues and general graininess. Also found 2 dead pixels. As well, LG's skin over nougat felt very dated. The hardware, while impressive and very well put together, was very clunky. The Pixels hardware takes a backseat to the fantastic software.
Sent from my Pixel XL using Tapatalk
I am sorry to hear you are having so many problems. I have 128GB XL from the google store and do not have the problems you are having. I know that does not help you, just thought I would mention it.
nabbed said:
The phone is buggy as hell - Bluetooth is buggy, Do not disturb mode is buggy, Project FI / cellular connection is buggy, sometimes Google Services just straight up crashes.
To be honest I prefer the less buggy experience with Samsung phones. This frequency of updates Google likes to advertise, it's a blessing and a curse, and for all the bad reasons - they need to update frequently to fix bugs, but with each new update, they seem to introduce new bugs.
Click to expand...
Click to collapse
No bugs at all. Dunno what phones hes using
I haven't seen any bugs either, dnd works flawless, haven't had any issue with Bluetooth, nothing has force closed at all. I do notice my Nexus 6 had a tad bit better service at my house (~3-5dBm). But the funny thing is that my n6 always had higher cell standby use on my battery.
To make it short.
no bugs, great battery ( much better as my Angler ).
Great Device
Love this device. Just got it Tuesday. No bugs that I've seen yet. Went right to 7.1.1 after unboxing so I can't speak to 7.1. I've used bluetooth for car audio, a speaker in my apt, connection to my huawei watch, and wireless headphones for running and have yet to experience an issue with that. No problems on T-Mobile here in LA either. Dont' use DND so can't speak to that. But overall very happy with my purchase!
airmaxx23 said:
I've had zero issues with mine on 7.1 or 7.1.1, have you tried a reset? I know 5 other people with the Pixel and they all love it and have had no problems.
Click to expand...
Click to collapse
Well, you see, if you don't use features then there will be no problems with them.
Bluetooth - many people have reported that the phone would automatically connect to a bt car kit but it would be in the state of "Connected (no phone)." When you manually reconnect from the bt Settings menu it would work just fine. That's a bug. It may have something to do with a particular car kit, but I tried 3 - Motorola Roadster 2, Jabra Freeway, and a Jarbra Talk bt headset. All 3 started acting up this way after 7.1.1 update.
Do not disturb mode turn itself on occasionally during the day, even though it's set to turn on only at night hours. Someone has suggested that this particular bug had to do with an Android Wear smartwatch being connected, as this doesn't happen when the watch is disconnected. I wish they would fix that.
Project FI just straight up disconnects sometimes for no reason even though I have 3 partners in town US Cell, Sprint and T-Mob. So this bug is probably due to switching to a different carrier, even though US Cell has -60-80 dB signal strength everywhere, and in principle, the phone should stay connected to it all of the time.
And when I try to fix Bluetooth issues and play in the settings menu, Google Play Services sometimes just crashes. It's probably related to the bt bug.
None of these are major issues, but they are annoying, especially bt because I use it all of the time.
nabbed said:
Well, you see, if you don't use features then there will be no problems with them.
Bluetooth - many people reported that the phone will automatically connect to a bt car kit but it would be in the state of "Connected (no phone)." When manually reconnect from the bt Settings menu it would work just fine. That's a bug. It may have something to do with a particular car kit, but I tried 3 - Motorola Roadster 2, Jabra Freeway, and a Jarbra Talk bt headset. All 3 started acting up this way after 7.1.1 update.
Do not disturb mode turn itself on occasionally during the day, even though it's set to turn only at night hours. Someone has suggested that this particular bug has to do with an Android Wear smartwatch being connected, as this doesn't happen when the watch is disconnected. I wish they would fix that.
Project FI just straight up disconnects sometimes for no reason even though I have 3 partners in town US Cell, Sprint and T-Mob. So this bug is probably due to switching to a different carrier even though US Cell has -60-80 dB signal strength everywhere, and in principle, the phone should stay connected to it all of the time.
And when I try to fix Bluetooth issues and play in the settings menu, Google Play Services sometimes just crashes. It's probably related to the bt bug.
None of these are major issues, but they are annoying, especially bt because I use it all of the time.
Click to expand...
Click to collapse
I'm not seeing any of these issues. I use Bluetooth all day and my Moto 360 lives on my wrist. My T-Mobile signal in Boston is way better than it was with my 6p. I have never had dnd turn on by itself and I've had the phone since launch.
toknitup420 said:
I'm not seeing any of these issues. I use Bluetooth all day and my Moto 360 lives on my wrist. My T-Mobile signal in Boston is way better than it was with my 6p. I have never had dnd turn on by itself and I've had the phone since launch.
Click to expand...
Click to collapse
That's why they are bugs and not design decisions. They show up for some people but not others. Maybe it's a combination of apps or a combination of settings that are different between our phones. But all of these people who reported them, they aren't imagining these things. Please at least acknowledge that.
nabbed said:
Well, you see, if you don't use features then there will be no problems with them.
1. Bluetooth - many people have reported that the phone would automatically connect to a bt car kit but it would be in the state of "Connected (no phone)." When you manually reconnect from the bt Settings menu it would work just fine. That's a bug. It may have something to do with a particular car kit, but I tried 3 - Motorola Roadster 2, Jabra Freeway, and a Jarbra Talk bt headset. All 3 started acting up this way after 7.1.1 update.
2. Do not disturb mode turn itself on occasionally during the day, even though it's set to turn on only at night hours. Someone has suggested that this particular bug had to do with an Android Wear smartwatch being connected, as this doesn't happen when the watch is disconnected. I wish they would fix that.
3. Project FI just straight up disconnects sometimes for no reason even though I have 3 partners in town US Cell, Sprint and T-Mob. So this bug is probably due to switching to a different carrier, even though US Cell has -60-80 dB signal strength everywhere, and in principle, the phone should stay connected to it all of the time.
4. And when I try to fix Bluetooth issues and play in the settings menu, Google Play Services sometimes just crashes. It's probably related to the bt bug.
None of these are major issues, but they are annoying, especially bt because I use it all of the time.
Click to expand...
Click to collapse
1. Never had any B/T issues.
2. I have had that issue but it turned out to be the phone turning on in my pocket. Other things would turn on too like Flashlight and hot spot. My phone digitizer is just too sensitive. I can almost wave my hand over it to make selections. I also have a Huawei watch and dont feel this has any impact at all. I did chang to the Microsoft lock screen to minimize this (and its nicer than stock and works with fingerprints). But I dont consider my revision of your issue a bug. More like something is just too sensitive on my phone. Which you could turn down the sensitivity.
3. Dont know anything about that.
4. Yes, I can confirm I was doing something with connectivity in the Settings menu and it crashed. This happened on all versions since release. I dont quite recall what I was doing. But yes, I confirm this bug as well.
Well I'm glad I read this thread.
The "Do Not Disturb" bug has been bugging the heck out of me.
Never bothered to check if it was happening to anyone else.
"Someone has suggested that this particular bug had to do with an Android Wear smartwatch being connected"
No Andoid Wear here.
And I always disable the screen wake motion/tap features to prevent my phone screen from turning on when in my pocket. I hate it when that happens and then you notice flashlight through your pocket or pull your phone out and all sorts of freaking apps have opened up and are pissed.
Otherwise, other than lack of development and the huge chins on this phone and the sucky speaker it's been the best phone I've ever had.
Dirty Unicorns is prepping to drop their first XL ROM so my development issues will be resolved with that and the eventual release of Xposed for Nougat.
I seem to have kinda fixed the bt bug by doing something interwebs suggested, Reset Network Settings. I can now work the Jabra headset and will have to try and test the bt car kit tomorrow. But boy, is it simply buggy just trying to troubleshoot this thing! Multiple times after the reset, the bt headset would connect to the phone and be in the normal state "Connected" but would have the "phone audio" feature disabled in a radio button inside the bt device settings. And tapping on the radio button to enable it would do nothing! That was new, never seen that before.
Then I would click the bt on/off switch from the notification pulldown menu, until the thing got stuck in the on position. After a reboot, bt was actually off. I enabled it and finally bt was working.
I got sick of troubleshooting and testing it, so that's where I stopped.
---------- Post added at 06:55 PM ---------- Previous post was at 06:51 PM ----------
CZ Eddie said:
Otherwise, other than lack of development and the huge chins on this phone and the sucky speaker it's been the best phone I've ever had.
Click to expand...
Click to collapse
You should have seen Note 7. It was unlike any new phone before. I've had like 15 flagships on their release, and Note 7 was super special.
RIP!
nabbed said:
You should have seen Note 7. It was unlike any new phone before. I've had like 15 flagships on their release, and Note 7 was super special.
RIP!
Click to expand...
Click to collapse
Fugg Samsung and their lack of developer support and locked bootloaders.
I had every Samsung Superphone since the Galaxy Skyrocket and will never buy another one.
I do support Samsung otherwise though.
They employ thousands of people here in Austin, TX and are sinking Billions of dollars into the local economy. :good: