Related
I've had nothing but bad experiences with every HTC phone i've ever had. From the Touch Pro, to the TP2, to the incredible.
I sent my old INC in and got a new one because it would boot loop for no apparant reason, the only thing i could think of is the 2150maH battery but tried with the stock battery and same thing.
So the first replacement phone i never received because somehow fedex got the shipping address fine, except the wrong city and zip code and they said verizon would have to call and have it changed, which they did, but it never got delivered and returned to sender. so they sent me a 2nd replacement. I got that one. Activated it yesterday morning, and not 4 hours into it, its boot looping again. I've had to factory reset 3 times and activate it twice (not counting the initial activation)
ugh
User error? Ive had all 3, the dinc is the best overall. did you root it and install custom roms?
Refurb?
Was the replacement (or original) DInc refurbished? I've heard nothing good about refurbs.
Are you using an SD card from another device in the DInc? An old SD card?
Is the SD card full or nearly so?
Rooting w/ UnrEVOked?
The 2 DInc's in our family have none of the issues you listed, we have one each of the AMOLED and SLCD. Both have been extensively modified - ROMs, kernels, PRL's, etc etc. Both run the 2150 battery from VZW. Is your 2150 from elsewhere?
Subjective Opinion:
FWIW, the DX is severely limited in what can be modified since it's not fully rooted. Compared to the DInc, essentially all you can really do on the DX is theme variants of the stock ROM. Then there is the small, and seemingly dis-interested group of devs. There just aren't as many devs because there is so little you can actually truly develop for the device.
IDK anything about the Samsung, but a quick look @ the Fascinate forum here on XDA..... the number of ROMs or mods isn't anywhere near what there are for the DInc.
To be fair, the DInc community has the benefit of time and has a strong bench of interested developers, but browsing the Fascinate forum doesn't look so interesting as the DInc forum.
So, it really depends on what you want to do w/ your device - if you want to be able to modify it six ways from Sunday, it's the DInc, no question.
DX, not so much.
Fascinate - meh.
that's my $0.02
I had both the TP1 & TP2, used mightymike (from ppcgeeks) roms on both of them and the phones were amazing. The Inc is the best phone I have ever owned. I too am going to have to go with user error.
Are you stock or rooted? If you are rooted what have you installed? What kernel are you using? What type of screen is the refurb?
If you don't care to try and fix it, and you must have a different phone now, I would go with the Samsung. The DX is horrible, screen looks like crap, not fully rooted, etc... The Samsung is a bit better, but I don't think it is anywhere near as good as the Inc.
Verizon has a batch of crap Incs that they got back in as warranty phones and instead of actually fixing the problem (bootloop) they factory reset the damn things and set them back out broken. Its just a big cycle, it took me 3 Incs in a week to get one that actually worked. They offered the X and honestly I probably would've taken that over the Fascinate, neither phone has the developer support that the Inc has, and at least the X will be supported by the manufacture.
Wait a couple weeks and get the Thunderbolt. Just don't mess up your phone again and you won't have to bug Verizon for a replacement.
Agreed
I am on DINC 3 myself. The 'bad batch' would be the first batch of DINC's as they shipped with a faulty hardware radio. They would struggle so hard to get a signal, that the phone would superheat, and bootloop. That happened to my DINC 1.
DINC 2 shipped to me with an already blown speaker (I guess running 30 seconds of electronic diagnostics before shipping out a returned phone, doesn't test for that).
I have had DINC 3 since August, and while I think I may have a small power issue, it is fine.
I would not get the X. My wife has the Droid 2 and I just can't stand MotoBlur. Combine that with the relative difficulty of getting a custom ROM on the 2/X (you have to use a few market solutions to force one on), and you may as well pass on Motorola products.
I'll just tell you that I've had nothing but problems with my Droid 1 and 2. I went through 7 (I lost count) before they sent me the Droid 2. I had two replacements for the Droid 2 before they sent me the Incredible. My 3rd incredible is on the way tomorrow. In general I've had terrible luck with refurbs. The quality control is non existent. But if I had to give you advise on the X over the Samsung I would go with Samsung. Knowing how many problems I've had with Motorola phones I'd hesitate to ever own one again.
I got a refurb in November. AMOLED and works perfectly. My fault I needed to get it replaced, too.
Jes7er said:
I got a refurb in November. AMOLED and works perfectly. My fault I needed to get it replaced, too.
Click to expand...
Click to collapse
I hope I have your luck then. I don't care about the whole AMOLED vs LED deal. I just want a freakin phone that works correctly.
At first the fascinate was an okay phone and slow on developement and me being use to my d1 development amount got frustrated by the lack of it. Now however, I have to say with froyo being here and other ROMs at around 80% done with more on their way I'm beginning to love this phone like I should have in the first place. You honestly can't beat the internals on this phone right now with anything on the market and I highly recommended it over the DX due to the locked bootloader (and let's not even get into the screen/camera differences)
As always remember that any kind of post on here (including mine) is subject to bias and you should really just get the one that suits your needs best if you really want to even leave the dinc. Just my 2cents.
Sent from my SCH-I500 using XDA App
if you constantly like to flash things, i would not recommend either, but just stick with the incredible and wait for something else.
I would wait as well. I've not had a lot of confidence in moto phones since my pos Moto Q (which I stall have and works if anyone wants to buy that junk lol). I've also seen the fascinate from a coworker, and while the screen looks nice, the rest doesn't seem to impress me.
Get yourself a free flip, cancel the data plan and wait a month or 3, take the money you saved from no data plan and get some newer nicer phone than all the rest of us on aa 1 year contract. Or get another Dinc, find someone on CL or something that wants to trade you for a samsung and a couple of bucks and swap or something.
A buddy of mine hates his Droid x. Don't know anything about the others
Sent from my ADR6300 using XDA App
Don't get either.
X sucks
Fascinate sucks and buggy and not well supported. Get the thunderbolt or wait for the LG or MOTO dual core phones. There might even be a dInc 2 coming soon.
trillonometry said:
User error? Ive had all 3, the dinc is the best overall. did you root it and install custom roms?
Click to expand...
Click to collapse
The first one I did, but it happened while stock as well as rooted, with any kernel/rom combination i tried.
the refurb i got was jewed out of the box. I highly doubt its user error as I didnt even do anything outside of activate it and add my google account before it started
smtom said:
Was the replacement (or original) DInc refurbished? I've heard nothing good about refurbs.
Are you using an SD card from another device in the DInc? An old SD card?
Is the SD card full or nearly so?
Click to expand...
Click to collapse
Yes, it was a refurb. thats all they will give me.
I've tried a number of SD's and even bought a brand new one. no change
g00s3y said:
I had both the TP1 & TP2, used mightymike (from ppcgeeks) roms on both of them and the phones were amazing. The Inc is the best phone I have ever owned. I too am going to have to go with user error.
Are you stock or rooted? If you are rooted what have you installed? What kernel are you using? What type of screen is the refurb?
If you don't care to try and fix it, and you must have a different phone now, I would go with the Samsung. The DX is horrible, screen looks like crap, not fully rooted, etc... The Samsung is a bit better, but I don't think it is anywhere near as good as the Inc.
Click to expand...
Click to collapse
See above, but there is absolutely zero way this is a user error and so many people are having problems. there is literally a 20 page topic on the VZW forums of people having this issue who are on their 7th and 8th dINCs
jdmba said:
I am on DINC 3 myself. The 'bad batch' would be the first batch of DINC's as they shipped with a faulty hardware radio. They would struggle so hard to get a signal, that the phone would superheat, and bootloop. That happened to my DINC 1.
DINC 2 shipped to me with an already blown speaker (I guess running 30 seconds of electronic diagnostics before shipping out a returned phone, doesn't test for that).
I have had DINC 3 since August, and while I think I may have a small power issue, it is fine.
I would not get the X. My wife has the Droid 2 and I just can't stand MotoBlur. Combine that with the relative difficulty of getting a custom ROM on the 2/X (you have to use a few market solutions to force one on), and you may as well pass on Motorola products.
Click to expand...
Click to collapse
Yea mine was pre-ordered so it would definitely have been from the first batch
bomber889 said:
if you constantly like to flash things, i would not recommend either, but just stick with the incredible and wait for something else.
Click to expand...
Click to collapse
this phone is literally unusable. hopefully number 3 (4 actually, though i never received 2 to know if it would work) will be better.
xmilkmanx said:
The first one I did, but it happened while stock as well as rooted, with any kernel/rom combination i tried.
the refurb i got was jewed out of the box. I highly doubt its user error as I didnt even do anything outside of activate it and add my google account before it started
Yes, it was a refurb. thats all they will give me.
I've tried a number of SD's and even bought a brand new one. no change
See above, but there is absolutely zero way this is a user error and so many people are having problems. there is literally a 20 page topic on the VZW forums of people having this issue who are on their 7th and 8th dINCs
Yea mine was pre-ordered so it would definitely have been from the first batch
this phone is literally unusable. hopefully number 3 (4 actually, though i never received 2 to know if it would work) will be better.
Click to expand...
Click to collapse
Good luck man, I know how your feeling.
the refurb i got was jewed out of the box.
Wtf does that mean?
hexon said:
I'll just tell you that I've had nothing but problems with my Droid 1 and 2. I went through 7 (I lost count) before they sent me the Droid 2. I had two replacements for the Droid 2 before they sent me the Incredible. My 3rd incredible is on the way tomorrow. In general I've had terrible luck with refurbs. The quality control is non existent. But if I had to give you advise on the X over the Samsung I would go with Samsung. Knowing how many problems I've had with Motorola phones I'd hesitate to ever own one again.
Click to expand...
Click to collapse
Hmmm what's the common denominator here? 12 phones total over 3 models?
midnight assassin said:
the refurb i got was jewed out of the box.
Should watch what you say a little closer. No offense, I'm not anyone's dad, but that's crossing the line.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I'll try to keep it short, but;
I bought a Google edition Pixel XL from swappa because I saw a really good deal on it and couldn't pass it up. Though even though it's a google bought phone (I checked the IMEI and unlocked the bootloader with no problems, so it basically has to be), I'm on the Verizon build of NDE63X instead of NDE63V, which is the "regular" build. I'm not sure if this could pose any problems in the future, but I thought I'd try to get on the regular build in case.
I tried sideloading the normal OTA image, but it denied by saying it was out of date as compared the build I'm on now? It was downloaded straight from the Google developers page, so that doesn't seem to make sense to me. Eventually I toyed around and ended up flashing the phone with the google edition of the OTA, and everything seemed to be in order. All of this was a pretty long and painstaking process because I've known barely anything about the intricacies of Android before like 2 days ago and have just been learning it all from scratch. However, when I finally was in the V build over the X build, I saw my phone had an update; I went ahead and installed it just thinking that it was standard and maybe the OTA I flashed in was lacking the November security patch or something. When this update went through, it put me back on the X build. Needless to say I was a little frustrated, I kinda felt like I just wasted a royally large amount of time.
So I guess that leaves the question of; why/how exactly did this happen? Is it an issue?
My bootloader is unlocked now after that whole fiasco; should I relock it? Is it any kind of significant security issue? I've heard that relocking the bootloader can brick the phone entirely, and lord knows I don't want that.
If I keep the bootloader unlocked, what exactly can I do with it? I know it allows to install custom kernals/roms, but I'm not exactly sure what that's like or what it's exactly capable of. I know, this is a very general question that I could google. But I'd also just like to hear people's inputs about it.
Will my phone get regular updates with the bootloader unlocked, or would it unable/cause some kind of error?
Thanks in advance for any replies! Like I said, I'm still really new to this whole thing, so if you could kind of explain answers and/or instructions in kind of a black-and-white way that would help me a lot. All of this is kind of intimidating, but it's also been a lot of fun, I like learning about it all.
@cam30era
This is what I did, I actually had it on the V build, for all of about 20 minutes. Then it pushed an update through and the update changed it back to the X. I'm not sure if I screwed something up along the way or exactly how it happened, but it seemed like a kind of unique thing.
Actually, if you'd like to downgrade, make sure your bootloader is unlocked. Flash the boot image from the factory image zip. After that you can sideload the V ota.
Sent from my Pixel XL
So what exactly is your problem with the build that you have other than being the "Verizon" version? The phone isn't going to function any different and there are probably little to no differences in the software other than a letter on the build number.
Sent from my Pixel XL
Odds are that the radio is the only difference. There were different radios for the Nexus 6 between VZW and GSM, but the firmware was basically identical there too. I really don't get why everyone is hell-bent on the VZW firmware being different or no good with the Pixel but they weren't with past devices.
Sent from my Pixel XL
That would only affect models sourced from Verizon...
Sent from my Pixel XL
imnuts said:
Odds are that the radio is the only difference. There were different radios for the Nexus 6 between VZW and GSM, but the firmware was basically identical there too. I really don't get why everyone is hell-bent on the VZW firmware being different or no good with the Pixel but they weren't with past devices.
Sent from my Pixel XL
Click to expand...
Click to collapse
Agreed. AS long as you keep your bootloader unlocked you can flash what you want. If you see something amiss flash another version.
Flashing the verizon firmware on a Non verizon phone should be fine. @imnuts said, same questions and answers with the Nexus 6. I flashed all sorts of builds just to see how they would perform... IN the end there were all the same.
For those who received their XLs in February after the delay (who ordered in November/December), have you been experiencing issues? I had trouble activating the phone and ever since, my cellular connection has been spotty. Even when it says its connected, texts and calls sometimes fail to go through or drop. Despite the reviews, I have experienced some lag and freezes. And my battery life definitely does not last a day (I have to charge it twice a day for moderate to light use with 2 hours screen on time). I wonder if this is common with the new batch of XLs that were shipped out or if, I hope, I just received a faulty device.
Try flashing the new Feb factory image, it will wipe all data and be a complete factory reset. Try that it will most likely fix any issue or issues.
I'm completely stock (locked and unrooted) and have done a couple factory resets. I'm on the latest build. Would it still help? If so, how do I do it?
RLPSZ said:
I'm completely stock (locked and unrooted) and have done a couple factory resets. I'm on the latest build. Would it still help? If so, how do I do it?
Click to expand...
Click to collapse
Go to the link below and follow googles instructions. Pick the feb image that is in the Marlin section and listed for Verizon and most others, unless your on rogers which the other is supposed to be for rogers which is in Canada.
https://developers.google.com/android/images?hl=en
Is you're phone from vzw or directly from Google.
RLPSZ said:
I'm completely stock (locked and unrooted) and have done a couple factory resets. I'm on the latest build. Would it still help? If so, how do I do it?
Click to expand...
Click to collapse
Oh sorry about that I looked past the part where you listed your stock and locked. Since your all factory I would call verizon and let them troubleshoot it, or if you bought through the google play store contact google cs about it, because you cant flash factory images with a locked bootloader.
Thanks for the replies! I bought it directly through Verizon and they will be sending out a replacement (in a couple weeks tho :/). I'm just wondering if anyone else with a February-delivered XL has been dealing with these issues.
RLPSZ said:
Thanks for the replies! I bought it directly through Verizon and they will be sending out a replacement (in a couple weeks tho :/). I'm just wondering if anyone else with a February-delivered XL has been dealing with these issues.
Click to expand...
Click to collapse
No problem here. Got mine last week.
Picked up mine from a corporate Verizon store a week ago and my cell connection is garbage. No service 30% of the time for no reason. Not to mention, the wifi calling keeps disabling itself. I going to try a factory wipe and reflash a Google image to see if that helps.
mycomputerisjunk said:
Picked up mine from a corporate Verizon store a week ago and my cell connection is garbage. No service 30% of the time for no reason. Not to mention, the wifi calling keeps disabling itself. I going to try a factory wipe and reflash a Google image to see if that helps.
Click to expand...
Click to collapse
Are you running a custom rom or stock ? Honestly I get better signal and performance running the rom Pure Nexus and the Elemental x kernel. If your on stock I would recommend giving Pure Nexus a try and Elemental x also.
I got my pixel xl at the beginning of feb, thru verizon, so far no problems. The pixel xl definitely doesnt get the same reception as my g3 did/does. All i can say is thank god im not having any issues with wifi calling, cuz i now get zero bars at my home. Purenexus is pretty nice, but i saw no gain in reception using it but ymmv. The only other thing is with substratum on PN, regardless which theme i choose they all set the color of links in irc for android to the same color as the background.
Sent from my VK810 4G using Tapatalk
RLPSZ said:
Thanks for the replies! I bought it directly through Verizon and they will be sending out a replacement (in a couple weeks tho :/). I'm just wondering if anyone else with a February-delivered XL has been dealing with these issues.
Click to expand...
Click to collapse
couple of weeks? how come I'm getting a replacement tomorrow and I talked to them sunday Feb 19.
alobear said:
couple of weeks? how come I'm getting a replacement tomorrow and I talked to them sunday Feb 19.
Click to expand...
Click to collapse
That's what they had told me. Though I did notice that they shipped it yesterday!
RLPSZ said:
That's what they had told me. Though I did notice that they shipped it yesterday!
Click to expand...
Click to collapse
Guess what? Verizon shipped a regular Pixel instead of an XL! Verizon has been messing up and misleading at every freaking point. This is unacceptable on so many levels. And they charged me for it!
And they no doubt will make it right. Ffs anybody or company if you prefer, can make mistakes, nobodies perfect. But, because verizon is everyones favorite whipping boy any and all oopses are just dogpiled onto. Give just a tiny bit of room for human error, believe me, they undoubtedly will do something else before long to incur everyones anger.
Sent from my VK810 4G using Tapatalk
wyrdtrtle said:
And they no doubt will make it right. Ffs anybody or company if you prefer, can make mistakes, nobodies perfect. But, because verizon is everyones favorite whipping boy any and all oopses are just dogpiled onto. Give just a tiny bit of room for human error, believe me, they undoubtedly will do something else before long to incur everyones anger.
Sent from my VK810 4G using Tapatalk
Click to expand...
Click to collapse
Of course, I understand this is a mistake and human error is normal. But, it can be frustrating for someone after ordering a phone, it taking two months to be delivered with constantly being told different dates and information each time they contact Verizon, being promised a fee being waived by one rep but then being told otherwise by another, and then again being promised it but it not being applied after multiple calls. Then, the same thing occurs with a Daydream View. Then, when the phone finally arrives, it has cellular and battery issues. Then, when a replacement phone is promised, it turns out the be the wrong one. And this is just a summary. I had to speak with Verizon multiple times for different things and the customer service to address these issues was not so great.
To update on this situation, they now tell me I need to wait for this phone to arrive and activate it, in order to return it for a refund and receive the correct replacement without charge. So I still have to wait another couple weeks to enjoy a usable Pixel XL :/
I feel your pain, ordered mine dec 15th, i also kept getting diff shipping dates, was literally on the phone cancelling my order when the shipped e-mail arrived. I didnt have a clue about the vr headset until fedex dropped it off on monday cuz i had not returned their call that previous fri.
I can understand your frustration, and tbh, had forgotten the litany of mishaps you had already gone thru, i just see and read so many gripe fests against them, and most of them are from people that are mad about the locked bootloader and they then blame them for world climate change, dropping birthrates, famine, pestilence and hillary losing. Allbeit, that last one i for one would praise them for, if it were their doing.
Anyhoo, dealing with most any corporation can and often is a PITA, but ill say this, after six years, verizon has not once failed to make it right by me. The wait has rarely been very long, but it has happened.
Hope they fix it for you sooner rather then later.
Sent from my VK810 4G using Tapatalk
I got a QB and a VS Pixel XL in February. No problems at all. I live in a rural area and both my wife and I had Samsung GS4 phones before these. I actually get a little better reception I believe.
The only problem I've run into is Trusted Voice doing its auto-disable thing, but I applied the workaround and haven't had any problems since.
My battery life is really good. I play Pokemon Go with my kids and use my phone as a hot-spot, and I can still get through a full day. Though, if I'm around a charger when the phone hits 50% I just charge it anyway.
JU57US said:
I got a QB and a VS Pixel XL in February. No problems at all. I live in a rural area and both my wife and I had Samsung GS4 phones before these. I actually get a little better reception I believe.
The only problem I've run into is Trusted Voice doing its auto-disable thing, but I applied the workaround and haven't had any problems since.
My battery life is really good. I play Pokemon Go with my kids and use my phone as a hot-spot, and I can still get through a full day. Though, if I'm around a charger when the phone hits 50% I just charge it anyway.
Click to expand...
Click to collapse
That's good to hear! It means I just received a faulty device and the replacement should work fine. I was worried that the new batch may have all come out like this since perhaps Google rushed their production by reducing time for quality checks or something like that.
I still haven't received a replacement :/ Verizon keeps sending a regular Pixel by accident.
Anyways, from the many conversations I've had with them, they eventually admitted that the February XL's have had multiple reports of issues with activation, like mine did.
Did anyone else have activation and cellular issues? If so, how are your phones doing now?
So, my Google Edition Pixel XL arrives tomorrow, and I've been digging around in preparation (I've previously owned the OG Droid and Galaxy Nexus, so consider myself marginally competent as a consumer of non-OEM firmware). Anyway, I'm super intrigued by the firmware slots I've heard mentioned, but was hoping for some clarification on how they work.
-Do they run from the same Data partition, so you can run one Kernal/ROM one day, and the other on another day, back and forth, forever...
-Or are they more like a nandroid backup?
Thanks for helping me understand this new feature,
Christian
Same data.
So remember what they were built for. They were built to run the same OS and provide seamless updates. They were not built for dual boot.
You can do a little trickery. Like same Rom with one rooted and one not pretty easily. Beyond that it is very tricky, there are a couple of folks here that seem to habe a handle on it.
Hopefully they will be along shortly.
The slots on the Pixel XL seem to trip up a lot of people who try to install TWRP, a custom Rom or root the phone. The really frustrating thing is that I did my research too and came across completely contradictory information regarding how they relate to custom flashing and should be handled. Even worse, the custom flashing guide on XDA for this phone is terrible. If you read through all the pages at various points it tells you to do something different than at the beginning of the thread and it doesn't deal with the dual slots at all. Google also seems to keep breaking root on the Pixel XL where SU programmers have to come up with updates and new flashing procedures to keep root working. The Pixel XL is the only phone I have ever owned that I am afraid to flash on, but if you are braver than me then I certainly wish you luck.
What's up guys.
I'm facing occasional lags on my Pixel. Every now and then the launcher and UI overall become unresponsive. It happens with the stock rom and LineageOS. I think it could be caused by an app or something but I haven't had any luck finding the culprit.
I tried disabling Digital Wellbeing, and even though it seems to work at first the lag comes back time after.
How are your Pixels standing up? Do you have any lag on yours?
I have a Verizon Pixel XL with the bootloader unlocked, do you think unlocking the bootloader may cause this issue?
Hope to heard from you, my experienced comrades.
I suppose a fresh flash is needed. However, as you said you are on LOS, so you have already done a fresh installation. In that case I am not sure. Maybe something hardware breaking as the device is old or something? I certainly wish not.
ithehappy said:
I suppose a fresh flash is needed. However, as you said you are on LOS, so you have already done a fresh installation. In that case I am not sure. Maybe something hardware breaking as the device is old or something? I certainly wish not.
Click to expand...
Click to collapse
Hmm, this is my 2nd Pixel. I recently purchased 2 for some friends, I also had a 32gb version before, all of them have the same issue. I just happen to think is caused by Android P.
liriolebron said:
Hmm, this is my 2nd Pixel. I recently purchased 2 for some friends, I also had a 32gb version before, all of them have the same issue. I just happen to think is caused by Android P.
Click to expand...
Click to collapse
I happen to have a stuck-for-few-seconds problem way back when the phone was new, on Nougat. It drove me crazy. Sold the first pixel for that reason alone and moved to the dark side. But then when I came back to another Marlin after couple of months I found that the problem was gone! Sometimes this type of problem happens on some specific Pixel devices I suppose, its not reported as it happens to a very few Pixels I guess! Either wait for an upcoming update to see whether it fixes stuffs, or maybe move to some other device. But I feel you, I remember quite well how that problem made me go total bonkers, probably you will find my threads on it as well. Good luck.