Related
I lost my Eris, the battery is dead.
Question, what can someone get off of the phone? I deactivated it and had it put on the "Lost/Stolen" list. My concern is someone can get a lot of personal info.
Any advice/help would be appreciated.
Thanks
Nailzaz said:
I lost my Eris, the battery is dead.
Question, what can someone get off of the phone? I deactivated it and had it put on the "Lost/Stolen" list. My concern is someone can get a lot of personal info.
Any advice/help would be appreciated.
Thanks
Click to expand...
Click to collapse
First, you should've already changed your passwords on all of your email accounts, especially Google (used to sync. info/data/contacts/emails, etc. between the server & your ex-Eris) .... Facebook, Twitter, Skype/Voice, et. al.
Second, you did not install any phone tracking or recovery/security apps on the Eris like Wheres My Droid, which would allow you to ring & find it via GPS, etc. so whatever was stored on it (photos, sensitive emails/text or mms msgs. and even web search history could be easily read & extracted off the phone, once it's powered on (regardless of whether the battery is dead or not - a generic mini-usb charger/cable or inexpensive replacement will easily bring it back to life again). So the question that you need to think & answer for yourself is: do I and should I tell & alert someone, anyone or nearly everyone that I "communicate" with about the lost Eris & possible breach of info and security, and to be cautious about data mining and misuse/abuse, etc.
Third, was it lost in a public place, misplaced or dropped while getting in/out of a car/bus/taxi/train or possibily intentionally taken - might want to file a police report (if PD would take one) just for the records & future proof (identity theft ??)
While this lost/stolen phone will not be activated on VZW (at least not so easy) - it could still be ebay as parts or spares or be on craigslist (ever wonder about some of phones seen at the flea market ....) - so you will need to be on your guard for a while as the data might still be vunerable to exposure and misuse down the road.
Hard lessons learned here, consider & do install an app to track/recover one's smartphone as it's becoming our mobile wallet with access to mobile banking info and even one's Starbuckscard account - easily swiped for getting that latte around the corner .... (no, I will did not d/l or install that latest apps)
Thank you and yes, very hard lessons learned.
I will always password protect my next phone and have tracking software installed.
I will take your advice and change all of my passwords.
Wow, pictures of my kids, everything... very sensitive information all out there.
Did you happen to have sense on it with a hub account? I believe that is supposed to be able to locate your phone as well if I'm not mistaken.
Sent from my ADR6300 using XDA App
hi, i bought my sgs2 a couple of weeks ago, and well at first i thought it was due to some bad data/energy configurations but i don't seem to find a way out of it, first of all my battery lasts 10 hours when i don't use it, maybe 5 when i use it (use the internet, make phone calls, text, chat, play some games and not much), second of all, my phone signal/reception to make phone calls or 3g just works for moments, i have tried several working sims but none seem to work so its definitely some antenna or phone issue, plus it gets hot for no reason, and when i play 3d games the screen gets really really hot, so hot that it burns, i already tried changin roms, kernells, configurations and everything, im really dissapointed with my phone, and i havent seen much people with these issues (besides the battery one) so i think my phone its factory damaged, what do you think? whats your recommendation? please help me, i really don't like to waste money and there goes $800
PLEASE PLEASE HELP ME!!!
Others reported battery performance similar to yours. It may have something to do with your cell signal. The SGS2 doesn't like certain carriers or particularly weak signals. That could be the cause of your 2/3G issues and your battery drain. If you post where you are and what carrier you're using maybe others can tell you their experiences.
Yeah sure, i live in El Salvador, my carrier is tigo, i bought my phone unlocked, maybe someone else has had similar issues related to 2/3g signal.
Try one of the stock(!) 2.3.4 based FWs, XXKG2 or XXKG3.
If things don't get better it might indeed be a HW fault, talk to the shop who sold it about it for replacement/fixage under warranty in that case.
HellcatDroid said:
... talk to the shop who sold it about it for replacement/fixage under warranty in that case.
Click to expand...
Click to collapse
Yes, OP - just make sure you reset the phone with "the jig" if you suspect the shop will be checking how many roms you flashed violating warranties.
and how do i do this, reset the phone with the jig? please instruct me
you can buy the jig from online sources. all you have to do is plug it in while its off
Am I the only person that's noticed the cover up (or at best complete overlooking) of the 920 MANY issues?
Let me say, I own(d) a 920 and I loved it so much I looked past all its flaws, and I dealt with a lot. Previous owner factory reset it right in front of me and we know what that means. I spent the next 12 ****ing hours unbricking the thing just so I could use it! Now, after owning the 920 a freakin week, it stops reading my SIM card suddenly so now I'm back with android.
I just notice that no tech site has EVER run any articles about the litany of major issues with this phone. Hell even in the forums nobody seems to have put it together! Am I the only one who sees it??
Bricking on factory reset
Battery life issues
Black screen on calls
Hardware buttons randomly not working, requires soft reset
Phone suddenly stops reading SIM cards
I'm sure I'm missing some but those are the one I dealt with. Am I alone?
Sent from my HTC6435LVW using xda app-developers app
I've been using the 920 for 2.5 months now and I have none of your issues. I had the restart bug but it got fixed with portico update. also there is some dust under the FFC but i don't care because it is not on the lense and it don't use it anyway.
i know about black screen and factory reset bug but i read for the 1st time that there should be major problems with the SIM card or the hardware buttons.
NSAgent said:
Am I the only person that's noticed the cover up (or at best complete overlooking) of the 920 MANY issues?
Let me say, I own(d) a 920 and I loved it so much I looked past all its flaws, and I dealt with a lot. Previous owner factory reset it right in front of me and we know what that means. I spent the next 12 ****ing hours unbricking the thing just so I could use it! Now, after owning the 920 a freakin week, it stops reading my SIM card suddenly so now I'm back with android.
I just notice that no tech site has EVER run any articles about the litany of major issues with this phone. Hell even in the forums nobody seems to have put it together! Am I the only one who sees it??
Bricking on factory reset
Battery life issues
Black screen on calls
Hardware buttons randomly not working, requires soft reset
Phone suddenly stops reading SIM cards
I'm sure I'm missing some but those are the one I dealt with. Am I alone?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Previous owner. Maybe that is your problem.
Son Loves it!!
Heelfan71 said:
Previous owner. Maybe that is your problem.
Click to expand...
Click to collapse
My son has had the 920 since it came out...Other than *****ing about the lack of the most popular apps (instagram, temple run, Jetpack Joyride...etc) the phone has been nothing but flawless. He will never give it up because he is an xbox junkie lol
i've had it for almost 2 months now..
only issue i've had is the crashing (normally every couple of days), since updating seems ok so far...I've flashed a few 'roms' to it, EE branded and normal
I thought the screen going blank in calls was supposed to happen? Like to save power? last couple of phones i've had turn the screen off when you put it to your head?
I'll be honest, i'm a little disapointed in windows phone 8, after coming from 7 with no crashes for a year (apart from once when i started messing with the registry) I found windows phone 8 quite shocking, coming from android/windows mobile i'd say its not to bad, but in someways it seems a downgrade. But so far no crashes with the latest update, and i'm hoping it stays that way, but honestly, I have a feeling your issues are isolated.
Also had the chance to use the new nexus 4 the other day, if theres a cover up going on, i'd say its those who say android is smooth and responsive....
I've been using my 920 for a month and haven't encountered any of your problems. The only thing I don't like about my 920 is that there is no app so far to automatically switch phone profile according to time and location.
I'm shocked 2 of you have had no problems. Search Google for any of the problems I listed and you'll find loads of people with the same issues.
Id get another one but I can't afford to keep buying phones when one ****s up. And yea the screens supposed to go black when you put it to your head but it was going black and staying like that so I could end calls, use the num pad, use speaker phone, or any of that. I found a work around but the proximity sensor is supposed to work
Sent from my HTC6435LVW using xda app-developers app
NSAgent said:
I'm shocked 2 of you have had no problems. Search Google for any of the problems I listed and you'll find loads of people with the same issues.
Id get another one but I can't afford to keep buying phones when one ****s up. And yea the screens supposed to go black when you put it to your head but it was going black and staying like that so I could end calls, use the num pad, use speaker phone, or any of that. I found a work around but the proximity sensor is supposed to work
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Search google for ANY electronic device followed by the keyword 'issue / problem' and you are sure to get pages of results. People that don't have problems (most people) typically don't post about it while people with issues regularly post because they want the issue resolved. This gives an artificial bias to the negative and only reinforces the already tainted view of people in a mindset that something is rubbish.
voluptuary said:
Search google for ANY electronic device followed by the keyword 'issue / problem' and you are sure to get pages of results. People that don't have problems (most people) typically don't post about it while people with issues regularly post because they want the issue resolved. This gives an artificial bias to the negative and only reinforces the already tainted view of people in a mindset that something is rubbish.
Click to expand...
Click to collapse
I agree, since the last update I haven't had very many problems at all. And since I haven't been having issues I haven't been coming to the forums as much. I just come in every once in a while now to see if there's anything new. I'm not constantly hounding for an answer to my problems on a daily basis since I don't have problems. It's my guess that other people who have perfectly working phones would have like minds as me... or just not visit the forums at all.
No bricking during factory reset (had to do it once and I'm not going to do it again just to prove a point).
Battery life is awesome.
Hardware buttons are working fine.
Blank screen during calls isn't an issue for me since the proximity sensor works almost all the time, I think.... at least, it hasn't been a big enough concern for me that I actually notice it.... guess I should keep track of it.
Sent from my Windows 8 device using Board Express Pro
Pre-portico
No stability issues, but craptastic daylight camera and bluetooth connectivity issues
Portico:
Unstable. Reboots at least twice a day.
Good daylight camera
Good bluetooth connectivity.
Think people have to make a choice about the portico.
unstable and functional or stable and unfunctional.
Lemark said:
I've been using my 920 for a month and haven't encountered any of your problems. The only thing I don't like about my 920 is that there is no app so far to automatically switch phone profile according to time and location.
Click to expand...
Click to collapse
This is also the main thing I'm missing, coming from Nokia N8 the situations was really a great app...
I think Nokia lumia phones in general have a lot of issues, as does Windows Phone. It's just there are so few users even if there was a problem, it would seem isolated. Microsoft's share in the smartphone market didn't even budge at all in 2012. WP users are not power users so they just run back to the store to get an exchange. Even the lumia 920 forum at wpcentral.com is slow as molasses. 90% of the posts are very shallow anyway. Most don't even know what screen size their phone is or what processor its running. the camera is just AMAZING and the phone is PERFECT, over and over again. Of course, this forum isn't any better. The only difference being the plethora of unlock threads, because xda is international.
Your description of WP users is fairly accurate & the market segment MS is going after. The enthusiast market is small & even on Android accounts for a very small % of sales. The easiest way to solve an issue is by exchanging the phone, if you have that option available to you. A lot of issues people are having are either caused by defective hardware or a bad flash IMO, which is an issue on any of the platforms.
Do people not expect bugs and hiccups at launch for these kinds of devices?
It happens. And it's not as bad as you perceive; it's not a conspiracy.
AW: The great Lumia 920 conspiracy.......
If ms allows developers create store accounts for free I bet there would be more apps on store.,.
I get what you guys are saying, but phone busting issues like that black screen on calls and bricking on hard resets shouldn't be common enough to have a thread full of people experiencing them.
If anyone knows of any way to get the phone to read SIM cards again, I'd like your help. I still miss using my lumia 920 :'(
Sent from my HTC6435LVW using xda app-developers app
I have experianced just about every issue in this thread. I have users of the 920 I support for other stuff and I see how they basically ignore them as they did on their Blackberry or iPhone. I had the brick issue... news flash as I posted in another thread, it is not bricked!!! use the Nokia Care Suite, gets you going no problem. During my day I may deal with just about every phone they see at an AT&T store (Tmobile, Sprint,or Verizon for that matter)... they all have issues. Have you ever seen an iPhone user change their password on their laptop and not update the iPhone? Lets say you need to get to something before updating that password, like they changed the server setting trying to update it... go ahead try it. Drop calls, Steve Jobs had to properly instruct dumb iPhone users how to hold an iPhone. Andriod, perfect????? WTF are serious?? And becuase of that piece of software, it does not matter what hardware you are talking about.
My phone is limited compared to Andriod, I can agree with that.... but I can do more with fewer Apps and I like that. The 920 has had some hiccups along the way, but the hardware I have right now is as solid as any other phone out there, actually physically a tougher phone then any other top tier phone.
awagner said:
they all have issues.
Click to expand...
Click to collapse
This is exactly what I was trying to get at. These sorts of issues and threads are everywhere for many high profile smartphone launches, especially lately with this insane obsession with HW spec wars.
I've seen much worse, many times, you will not buy a high end smartphone at launch these days without having some sort of worry that there will be a game-breaking bug or defect.
WP 8 for 3 months:
NO ISSUES
POWER USER (i had portico when the first roms were available on navi)
my question is, are all these faulty devices on ATT or another crap american service , cause i think this may be your problem, ive had to work on vodaphone orange tmobile and ee 920's and 820's and i can say with pride that the only issue people have is the lack of popular apps., there is no conspiracy. why the eff are you people needing to hard reset anyway wtf are you doing to your phones?
I have to admit I've been having freezing issues regularly, often when it's just sat on my desk or in my pocket, and almost every night while on USB charge. I've also noticed on the odd occasion a reboot, but only because of my SIM being PIN locked.
Mine was a German Vodafone one, which I flashed on day 1 to the CV_GB ROM, then again to CV_GB Portico ROM. Maybe I'll try a different one, as I've heard the EE one has fewer issues.
So,
Putting my infinite wisdom to use, I've established anecdotal evidence (oxymoron? I tease....) that says something is pooping on my MicroSD cards...and that something is....wait for it, wait for it....Custom ROMs (dun, dun, dunnnnnnn). Ehr Mah Guards!!!
I ran the stock ICS ROM for many, many months without issue, and my SD Card was a champ the whole time (excluding one time I plugged it into my Wintel Box, windows thought it was damaged and decided to move a few files around, leaving me a few hundred presents, in the form of LOST.DIR checkdisk files). However, once the Jellies Beans Leakz came out, it was quickly the consensus that it had become, literally overnight, the Bee's Knees. I hopped on mah 'pooter right 'way, and downloaded that sweet sweet ROM dew. Minutes later, and it was like Mardis Gras...if ya know what I mean. He he.
Fast furward about a month, and my Good Old Champ starting to fail on me. "SD Damaged. Yada yada yada...format me." So I did. I figured it was a one off thing kinda thing, ya know? So I continued on my happy way to flashing heaven...combining endlessly different mods, themes, etc. Since charging has always been slower on AOSP ROMs, I jus' charged me batterease in my external travel charger (which can charge a battery from zero to hero in 30 minutes flat), and when mah juices got down to critical levels, I just plopped may battery out, without shutting down or anything, and popped a new one back in! Ah...the marvels of modern devices, right? I figured I could shut this baby down a hundred different ways, and as along as I wasn't flashing something, I'd be fine!
WRONG!!! A week later, I was minding my own business, watching a Keira Knightley Flix, and I forgot to charge or change me battery. The thing crapped on me, and when i booted back up, KABLAM! YOUR SD CARD IS CORRUPTED!!! FORMAT ME NOWWWWWWW.
Oops! I went back to ICS, had a merry time for some months, and not furgetting about mah SD issue, I bought a new card. A stand up card, from a stand up kinda guy, I think his name was Mamason, and the SD card was made by Sand Tisk.
But im a regular kinda guy. So i spent a buttload of cheddar on it, thinking i suffered a fool for buyin' he cheap stuff before. Well no more! No more o' DAT cheap stuff for me Meow. You coodint pay me to use the cheap, regular, barnyard animal quality micros anymore!
So there I was, happy as a kitty with a catnip lollipop, on mah Galaxy Note, new Sandy Micros and e'rything, enjoyin me stocks. I enjoyed it for a few more months, unhindered....then I got fancy...I needed a fix. Bad.
So I decided to go checking out some new flashables, in the Developmental sections at the local ExDeeAysss. I got ter flashing...enjoyed meself quite a bit, dare I say--for about two weeks; before I got thàt DEEaarrrnnnn "SD damaged!" Message again. Yowserrs! Not again!
I formatted once more, switched to a different Bean ROM, and flashed away! Guess what? A month later: "SD Damaged!”
Emooooooo Raaaagggeeeee! Kaaaaammmaaayyyyyyuuuuuuhhhhh!
I went back to ICS, flashed and flashed some stuff there, and voila!!!! No issues!
Now, I cant tie this to random reboots, to Google's extremely vulgar and disappointing lack of knowledge when it comes to modern file systems, for supporting only FAT32, to code in the AOSP, or to a bug somewhere.....but what i can say, is that abusing my phone in AoSP almost immediately gets you a donkey punch to the Note face, leaving your SD Card's brain concussed, and your memory corrupted, with a complete loss of data. Which is really bad, if you plan on using your NANDROIDs on your external storage to recover from in case something bad happens.
I can also say that this doesn't seem to happen on the stock ROMs, or at least it doesn't happen nearly as often on Samsung ROMs. As someone who uses flash memory on an industrial scale for his side jobs and projects, and abuses it elsewhere, this isn't typical. ID really like to know if anyone else has any experience or knowledge to share here, which might just turn this from anecdotal evidence, to something a tad bit more concrete.
Anyone else care to share/chip in?
Sent from my SGH-I717 using XDA Premium HD app
1) Interesting post. You might have a future in writting.
2) Huh?
3) Kinda long winded. Couldn't read it all.
4) Huh???
I'm not going to dis-agree with your analogies regarding the SD card, and it's possibly being damaged by particular roms/builds.
I too, have suffered 2 SD card failures since running custom builds, and in particular, the JB builds.
I've not yet isolated the cause of course, but it seems that some pieces of code are likely messing up the file structure when the card is being written.
However, it is also quite possible, that the rom itself is not the issue, As many applications have the same ability in messing up the card, and it's read/write access.
We may never know what the cause is, unless folks are willing to disect the build down to the base level, an eliminate each and every application that runs to the external SD.
No doubt a long and painful activity.
Also, I've not had any more issues..(4 months) using (cough...not sandisk) other cards, and at least class 8 or higher.
I'm also running an AOSP/JB build. (thank you Flappjaxxx)....
So I really can't say what may cause the issue, but I know it certainly exists, as I can confirm your findings as well.
Perhaps a skilled Dev. or another person, much more skilled than myself will crack the mystery one day. But for now, I suggest a good quality card, in a class 8-10, and if the card gives you trouble, then try another brand.
I know these cards are mass produced, and vary greatly in quality. Good luck in your quest Sir.....g
gregsarg said:
I'm not going to dis-agree with your analogies regarding the SD card, and it's possibly being damaged by particular roms/builds.
I too, have suffered 2 SD card failures since running custom builds, and in particular, the JB builds.
I've not yet isolated the cause of course, but it seems that some pieces of code are likely messing up the file structure when the card is being written.
However, it is also quite possible, that the rom itself is not the issue, As many applications have the same ability in messing up the card, and it's read/write access.
We may never know what the cause is, unless folks are willing to disect the build down to the base level, an eliminate each and every application that runs to the external SD.
No doubt a long and painful activity.
Also, I've not had any more issues..(4 months) using (cough...not sandisk) other cards, and at least class 8 or higher.
I'm also running an AOSP/JB build. (thank you Flappjaxxx)....
So I really can't say what may cause the issue, but I know it certainly exists, as I can confirm your findings as well.
Perhaps a skilled Dev. or another person, much more skilled than myself will crack the mystery one day. But for now, I suggest a good quality card, in a class 8-10, and if the card gives you trouble, then try another brand.
I know these cards are mass produced, and vary greatly in quality. Good luck in your quest Sir.....g
Click to expand...
Click to collapse
Yes! Exactly my thinking...I can't realistically even make a guesstimate at this point. Is it tied to reboots during disk access? A certain program I'm using? Themes? Etc.
But I can say that it happens exponentially more often with my AOSP runs. Absence of evidence isn't evidence of absence. So I say "it happens more often" to be conservative--it hasn't happened to me on a stock ROM, and I don't remember it even happening on a stock-based ROM. But that doesn't mean it doesn't happen, amirite? Maybe it's the infinitely configurable nature and availability of AOSP customizations, mixed with my infinitely-satisfied-for-just-a-day-or-two behaviors, that's causing this-- primarily due to my tinkering.
Donald Rumsfeld had it right...the things we know we know, the things we know we don't know, the things we don't know we don't know....jeeze.
And equally, the versatility, and the sheer force of diversity, will probably ensure we never nail something down.
Sent from my Transformer using XDA Premium HD app
My guess would be the lack of a certain piece of code. Something that protects, or at least improves and stabilizes the write process.
Since we are dealing with the AOSP buids here, we lack the code added by carriers prior to device shipment, and certainly the testing of those builds.
AOSP is simply raw android, and ported to our devices by a number of means. One can only surmise, that a potential flaw may exist in the transfer proccess. (Maybe)
We may never know the cause, but it certainly is worth looking into further, given the costs associated with SD cards in general, and the amount of important data that they can store.
I know it's painful, to rely on a simple card that stores photos of families etc....Being lost and impossible to recover.
We have become dependent on our devices for support. And when a failure occurs, I suggest a backup plan, by leaving nothing on a simple card, we are not willing to be without.
Backups, and storage to other areas is really quite mandatory.....g
I fried one of mine recently by using Dark Side Super Wipe. Nobody believed me lol.
But I'm good with just the internal memory.
Sent from my SAMSUNG-SGH-I717 using xda premium
charlieb620 said:
I fried one of mine recently by using Dark Side Super Wipe. Nobody believed me lol.
But I'm good with just the internal memory.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
As mentioned above.....what we know, we dont know.....LOL
It is "WITHOUT QUESTION"...possible for a script to reach the SD card, and kill it.
Not that it's a common occurence, but without a doubt it can happen.
I wish my skill set regarding the file structure of android was a bit better, so I could look deeper into these issues.
But my old brain gets too hurting over this stuff...LOL.....g
gregsarg said:
My guess would be the lack of a certain piece of code. Something that protects, or at least improves and stabilizes the write process.
Since we are dealing with the AOSP buids here, we lack the code added by carriers prior to device shipment, and certainly the testing of those builds.
AOSP is simply raw android, and ported to our devices by a number of means. One can only surmise, that a potential flaw may exist in the transfer proccess. (Maybe)
We may never know the cause, but it certainly is worth looking into further, given the costs associated with SD cards in general, and the amount of important data that they can store.
I know it's painful, to rely on a simple card that stores photos of families etc....Being lost and impossible to recover.
We have become dependent on our devices for support. And when a failure occurs, I suggest a backup plan, by leaving nothing on a simple card, we are not willing to be without.
Backups, and storage to other areas is really quite mandatory.....g
Click to expand...
Click to collapse
Titanium Media Sync would be a worthy solution, were it able to write over Samba. I could just mirror everything over to my NAS. For now, drop box will have to do. With a paltry 6Mbps up, it could take days to reach the initial parity.
Sent from my SGH-I717 using XDA Premium HD app
Jamesyboy said:
Titanium Media Sync would be a worthy solution, were it able to write over Samba. I could just mirror everything over to my NAS. For now, drop box will have to do. With a paltry 6Mbps up, it could take days to reach the initial parity.
Sent from my SGH-I717 using XDA Premium HD app
Click to expand...
Click to collapse
Days indeed ....
I suggest a good book while the upload occurs ..LOL ...g
I'm not sure if this is even allowed here but, I can't use the phone for phone calls AND 1 other "over the air service" such as GPS or WIFI hotspot or even wifi - if I do the calls get broken up with the poor audio routing of the blue tooth adapter--it's almost like the phone doesn't have enough resources to run cell phone call AND GPS or cell phone call AND blue tooth music or cell phone call AND wifi/hotspot service....any eon one service used at one time works flawlessly but with a cell phone you want to use ALL the wireless services at once and have them work.
AND, the phone shuts itself off when it's in my pocket and charge to 95-100%?? I miss phone calls from work all the time, I am constantly checking the phone to make sure it is still turn on. What a pain the behind.
I call Google - so sorry it's Huawei's problem, I call Huawei - so sorry its Googles problem. In the meantime I bought this phone from google and it worked well for 1.5(purchased 06-16-2016) years (besides the shutdown issue) then poof gone - it is now a piece of crap - 3 months outside of the one year warranty and I need a new phone!
So, my question to these two companies ( and I know they have lurkers in these forums all the time - that's why I am posting this here after speaking with BOTH of them) is: How in all honesty can you expect me and every single person I talk to about this to ever purchase another phone from either one of you?
Because I do talk, to everyone who will listen, about this; I see a LOT of people everyday, different jobs sites all over eastern Ontario. I tell them that as a technician for the past 30 years and knowing how technology works and also knowing that BOTH of these companies are probably to blame each in their own way and that NEITHER of these companies are thinking about their customers on this issue and only about their own bottom line I couldn't possibly recommend either one of them for anything.
Without exception these people I meet ask me which brand they think I SHOULD buy. I tell them this: "If you want a phone that just works and you aren't a customizer get an iPhone. If you are a customizer get a Razer Phone, an LG if you want cheap or a Samsung, Samsung being my preferred choice - but whatever you do, DO NOT buy a google phone or any phone made by Huawei because BOTH of these companies have proven to not be trust worthy, over this debacle, to their customers and if this is the case now then why would you think any future incidents of this nature would be any different?
Good bye to Google and Huawei, hello to Samsung again.
Thanks for letting me rant/rage here.
I have to say, I'm also disappointed on my nexus 6p. One day it just went nuts, shutdown itself and then bam! bootloop occurred and from that day on I can't install roms including stock, yes including stock, without applying a 4-core mod (forces my device to use only 4-cores to work and boot). Some say it's a hardware failure or something, idk. And even before that i have been having issues with my battery, i only get 4h sot average. I cant believe i spent so much for this crap. Dont get me wrong though, i love this camera very much and the stock google experience (and custom roms) but everything else is sh*t. So yeah, +1 for this "dissatisfaction"
aserate said:
I have to say, I'm also disappointed on my nexus 6p. One day it just went nuts, shutdown itself and then bam! bootloop occurred and from that day on I can't install roms including stock, yes including stock, without applying a 4-core mod (forces my device to use only 4-cores to work and boot). Some say it's a hardware failure or something, idk. And even before that i have been having issues with my battery, i only get 4h sot average. I cant believe i spent so much for this crap. Dont get me wrong though, i love this camera very much and the stock google experience (and custom roms) but everything else is sh*t. So yeah, +1 for this "dissatisfaction"
Click to expand...
Click to collapse
Well I have no idea what carrier you use but if I was you I'd "accidentally drop" or "lose" my phone and file an insurance claim- I know Verizon told me if I end up breaking or losing my 6p they would either give me a Pixel 2 or 2XL so maybe that's something to look into?
Sent from my Nexus 6P using XDA Labs
Personal experience is the complete opposite. Phone was nearly 2 years old (1 year warranty in the UK) and started shutting down. Online chat with Google and confirmed I had done the basic fault fixes like factory reset and they immediately send out a refurb to replace it.
They had no legal requirement to do so but also did this for a lot of people who bought their phone through the play store. Its more complex if it was bought through a carrier as the warranty / contract is then with the carrier or Huawei and those experiences appear to be less straight forward.
Everyone has different experiences, I wouldn't touch Samsung with a barge pole due to personal problems I had with them and the number of faults our organisation has with their phones. Had an LG phone that had the reboot issue and they wouldn't do anything as it was outside of the 12 month warranty.
Warranties have an end date that you sign up to, they may give a goodwill gesture outside of this, or you can fight them to say the fault was inherent.
What have you done to diagnose the issue on your phone?
It could be as simple as the battery needs replacing. It can have all sorts of symptoms including shutting down or failing services when there is high demand and a power spike which the dying battery can't provide. Have you run something like Accubattery to check the battery state?
400ixl said:
Personal experience is the complete opposite. Phone was nearly 2 years old (1 year warranty in the UK) and started shutting down. Online chat with Google and confirmed I had done the basic fault fixes like factory reset and they immediately send out a refurb to replace it.
They had no legal requirement to do so but also did this for a lot of people who bought their phone through the play store. Its more complex if it was bought through a carrier as the warranty / contract is then with the carrier or Huawei and those experiences appear to be less straight forward.
Everyone has different experiences, I wouldn't touch Samsung with a barge pole due to personal problems I had with them and the number of faults our organisation has with their phones. Had an LG phone that had the reboot issue and they wouldn't do anything as it was outside of the 12 month warranty.
Warranties have an end date that you sign up to, they may give a goodwill gesture outside of this, or you can fight them to say the fault was inherent.
What have you done to diagnose the issue on your phone?
It could be as simple as the battery needs replacing. It can have all sorts of symptoms including shutting down or failing services when there is high demand and a power spike which the dying battery can't provide. Have you run something like Accubattery to check the battery state?
Click to expand...
Click to collapse
I'm in the UK. I bought mine from Playstore but the warranty card states the handset had a 2 year warranty?
I agree with you on LG though. I bought two LG G4's. One had the well documented bootloop within warranty and they repaired it. The second started to bootloop two weeks out of warranty...LG didn't want to know.
Sent from my Nexus 6P using Tapatalk
Had the same issue. The phone was practically useless for calls due to its secondary mic issue. The battery aged really well for me, though
When I contacted Google - they were pretty responsive. I really appreciate Google for this. After a year they had no obligation to even entertain me. But that's about it - they gave me standard replies like factory reset - to which I laughed. Rooting and disabling the secondary mic would have probably solved the issue but then the payment options would'nt have worked for me. Google had acknowledged the mic and the battery issue in North America but here in India they went the factory reset route. I shared the bug id as well. Nothing helped. They asked me to visit the Huawei service center. They changed mic - issue still persisted - asked me to contact Google.
I eventually got myself a Samsung N8. Had been with Google for 3 generations. The Pixel 2 XL couldn't convince me this time. Customer lost.