Related
Issue: \data partititon become corrupt for no obvious reason.
Manifests itself through: Freezes followed eventually by (endless) reboots
When: Randomly when you install new apps (may be every day as it can happen only every other week/month), or setting up apps (like Twitter, mail, etc)
Temporary solution: Re-flash Samsung FW but lose ALL YOUR DATA. Attention: CWM restore will not fix the problem!
---- Here goes a link to the fabulous mskip's tutorial, you will find here everything you need to get it back up temporarily
I experienced this in 401, 402, 403 and 404, some were expecting better data integrity in 404... I confirm this is not the case
I would not go as far as saying that this is 100% the reason, but it looks like the NAND quality is craaaaaap! There is no external SD card, Android should be able to do a perfect job now at handling info and preserving quality of data.
I will contact Samsung and ask for a refund (if at all possible)... Disgusting thing to put such a piece of s''t on the market without proper testing and call it "flagship/pure Google experience". This is not an isolated issue, it happens to at least half of the people around and the others may have not seen it yet (it all depends on how often you manipulate data on the phone)...
Any advice, I am inetersted, have tried pretty much everything so far and did not solve the problem...
DO YOU HAVE THE SAME ISSUE? Let your voice heard...
DO YOU HAVE THE SAME ISSUE?
Click to expand...
Click to collapse
No. Could it be possible you're overreacting?
David Horn said:
No. Could it be possible you're overreacting?
Click to expand...
Click to collapse
Agree as well ..seems more like rubbish
Sent from my Galaxy Nexus using xda premium
David Horn said:
No. Could it be possible you're overreacting?
Click to expand...
Click to collapse
Thanks David, you're of great help :/
Overreacting? Glad you had a better sample, I bet you would "overreact" as well if you spent 500£ on a piece of junk losing all you data on a daily basis.
But hey, this is not happening to you, right ?
Community means lots of people, some are here to help, others just looking for a social life while trolling on this forum.
Sorry mate, I am trying to get through to the first category...
Umm, sounds like you need a replacement phone.
Deep breath....deep breath.
KWKSLVR said:
Umm, sounds like you need a replacement phone.
Deep breath....deep breath.
Click to expand...
Click to collapse
Right While i'm catching my breath, found another thread pointing to the same issue IMHO (didn't not see it initially):
http://forum.xda-developers.com/showthread.php?t=1490815
Attempting to contact Samsung already...
vulpy said:
Thanks David, you're of great help :/
Overreacting? Glad you had a better sample, I bet you would "overreact" as well if you spent 500£ on a piece of junk losing all you data on a daily basis.
But hey, this is not happening to you, right ?
Community means lots of people, some are here to help, others just looking for a social life while trolling on this forum.
Sorry mate, I am trying to get through to the first category...
Click to expand...
Click to collapse
Your first post came across as a hysterical rant - this is the first I've heard of the problem so it's not affecting many phones, and ultimately Samsung are going to have the occasional dodgy NAND chip. Sounds like you got one.
If you'd had several phones and they'd all exhibited this problem you'd be right to be peeved, but it simply sounds like you've been unlucky and are pissed off about it. Have you even discussed it with Samsung's tech support or taken it back to the shop you bought it from?
And accusing an XDA recognised developer of trolling is not a great start to your time here.
I've not heard of other people having this problem with the Gnex? Who are these other people having this same problem? Maybe speak with them and see if a replacement phone might solve the problem. I really hope you can get this fixed and not give up on such a great platform.
Sent from my Galaxy Nexus using Tapatalk
vulpy said:
This is not an isolated issue, it happens to at least half of the people around and the others may have not seen it yet (it all depends on how often you manipulate data on the phone)...
Click to expand...
Click to collapse
The burden of evidence is on you bro. That is a pretty bold claim.
David Horn said:
...And accusing an XDA recognized developer of trolling is not a great start to your time here.
Click to expand...
Click to collapse
Respect for your dev background (haven't used any of your ROMs yet), in all fairness I'm far less impressed with your communication skills... I must agree though, my message may have come across as too abrupt and you're right again, I am going to sort it out with Samsung...
Did not mean to get people horrified, rather to blow the whistle on a worrying and annoying bug and smth people may consider if they come across or consider a purchase.
For having worked in the mobile comm semiconductors space for years, I know just what sets apart a serious company from a me-too profile. Surprised to see Samsung having this king of issues. Normally they are ironed out easily though SW regression tests and HW stress processes (at least at serious OEMs).
I will let one of the moderators judge if my crime is so serious, your ego will survive, I'm sure I will come back when/if issue solved (or in good progress).
yeah, mine is fine. If it was a widespread problem I would back your corner, but I seems rather isolated. Rather then cause mass hysteria I would say you need to return your handset
Sent from my Galaxy Nexus using XDA
This happened to mine. But only once.
Quite frustrating, as my phone is my alarm clock and it was bootlooping when I needed to go to sleep!
However, a reflash of the 4.0.2 stock images sorted it out, and no problems since. I'm pretty sure I caused it by pulling out the battery at some sensitive point in a reboot or something.
If this happens to you frequently, then you need to exchange your phone.
Also, I think this could be a pretty good resource as opposed to a rant if you put your mind to it. I'm not a developer, but I'm also not a total n00b, and it took me a little while to figure out how to fix the problem, when I had it. I'm sure there are people out there who would appreciate a guide.
In this thread, op is going through that time of the month, when was his own modification back fires in his face, his explosive emotions reek havoc on an online forum.
If you want to see a device with bad nand memory, see the HTC Desire S forum .
Also the reboots and freezes I used to experience on my device were application related. Device hasn't frozen, nor rebooted in about *looks at up time* .. 27 days .
adrynalyne said:
The burden of evidence is on you bro. That is a pretty bold claim.
Click to expand...
Click to collapse
... I was actually referring to a poll in another thread (link in this thread) concluding that half of the people who answered have experienced freezes and reboots... it may be biased somewhat by the fact that people who experienced the issue are more likely to vote than those who didn't... maybe an overstatement from me.
Get the odd reboot (Chrome seems to provoke, strangely) but zero data corruption in 3+ months of heavy use. (4.0.3 AOKP)
Sorry, no endemic fault that I can see here (from reading these forums) and if I were you I'd be looking for a warranty replacement. Refund will depend on your location and supplier and duration of ownership.
Daern
Sent from my Galaxy Nexus using Tapatalk
First I heard about this too. I've flashed tons of roms and mods and constantly installing uninstalling apps.
The GNex has been anything but non-stable. I think I've had to pull the battery once or twice since ownership. Never heard anyone complain about randomly losing all their data... especially not daily. Perhaps on a bad flash in CWM.
Maybe you should look into a super wipe that completely erases everything, deletes the partition tables and recreates everything from scratch. Maybe it'll help but it honestly sounds defective.
Sent from my Galaxy Nexus using xda premium
Thanks Player911... Interesting idea, was thinking as well to do a total wipe and sort of a sector-by-sector reformat, but could not find a way of doing it. Is there any tool that would allow me to do it? Maybe this will isolate bad sectors...
Will check shortly with Samsung folks, thanks mate! (what slows me down is the fact that I'm currently travelling to the US and the guarantee is only European and it's Sunday= hotline is closed in Europe).
daern said:
Get the odd reboot (Chrome seems to provoke, strangely) but zero data corruption in 3+ months of heavy use. (4.0.3 AOKP)
Sorry, no endemic fault that I can see here (from reading these forums) and if I were you I'd be looking for a warranty replacement. Refund will depend on your location and supplier and duration of ownership.
Daern
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Uhh, I don't believe my reboots are due to this. Just saying. That whole thread does not point to your theory as the issue. I'm gonna go ahead and call this myth busted and suggest you go get a replacement because this is just another extremist "my phone is busted but I refuse to get a new one" thread.
Sent from my Galaxy Nexus using xda premium
You've been Samsunged
Sent from my Galaxy Nexus using xda premium
Hi all,
I got my One X a few weeks ago, very soon after launch (O2). Initially I was very happy with my purchase but now I'm left extremely frustrated with this handset and regretting buying it - screen flicker, dropped calls, lots of little bugs, and now... The camera won't work!
I've been using it quite a bit since I bought it, but yesterday I was using it (no settings changed) and each time I took a picture there was either corruption in the image or a blank image with an exclamation mark icon instead of the picture. This now seems to happen almost every time I try to take a shot - I've done the following in an attempt to rectify:
1. Reboot handset
2. Ensured no other apps are running prior to using camera
3. Reset camera settings to default
4. Ensured phone was fully charged
5. Ensured I have enough free storage space (~22GB free)
I'm not going to perform a factory reset because I'm not convinced it's going to help anything AND I shouldn't really have to do that! I haven't got time to completely reconfigure my phone.
Still, I'm unable to take a photo and this is *really* annoying me! A premium handset with issues all over the place... Unacceptable!
Now I'm left thinking I'm going to go back to O2 and demand replacement with a SGS3, because by the looks of things HTC haven't actually fixed most of the bugs we're all experiencing.
Such a shame - had so much potential and a genuinely amazing device to pick up and use in many ways, but it's quite frankly not fit for purpose if I can't make reliable calls, take pictures or use the screen without serious flickering.
Has anyone else experienced these camera issues I described above?
Apologies for the tl;dr, just a very frustrated HOX owner.
So because you got a faulty phone all the others out there are not fit for purpose?
OK got ya that seems fair
There's something wrong with your particular phone, just get it replaced. The vast majority of people have no flaws whatsoever.
Lol... They won't offer a refund until you do a factory reset. I guarantee a factory reset will fix the problem. Stop having a cry are you 12 or something.
Sent from my HTC One X using Tapatalk 2
nikorette said:
Lol... They won't offer a refund until you do a factory reset. I guarantee a factory reset will fix the problem. Stop having a cry are you 12 or something.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Oh the irony of a childish response like that. That's how keyboard warriors really show their age.
For the record no, I'm significantly older and understandably annoyed by the poor quality of a ~£500 handset that I worked hard to pay for.
And as for the vast majority of people having no flaws - really?! I don't believe that for a second - by the looks of most of the boards a high proportion of HOX handsets have issues.
So yeah, I'm quite understandably frustrated - didn't realise how defensive this forum is lol
adamsharif said:
And as for the vast majority of people having no flaws - really?! I don't believe that for a second - by the looks of most of the boards a high proportion of HOX handsets have issues.
Click to expand...
Click to collapse
Yes really. It'd be incredibly foolish to assume that XDA users are representative of the majority of phone users and even more foolish to assume that people who have flawless phones will be just as vociferous as those with flawed phones.
So yeah, I'm quite understandably frustrated - didn't realise how defensive this forum is lol
Click to expand...
Click to collapse
Why don't you try and reflash your phone with a RUU or return it for replacement?
Well that's what I've done - just booked it in with O2 so will see what happens.
Still interested to know whether anyone has had this camera issue though?
adamsharif said:
Oh the irony of a childish response like that. That's how keyboard warriors really show their age.
For the record no, I'm significantly older and understandably annoyed by the poor quality of a ~£500 handset that I worked hard to pay for.
And as for the vast majority of people having no flaws - really?! I don't believe that for a second - by the looks of most of the boards a high proportion of HOX handsets have issues.
So yeah, I'm quite understandably frustrated - didn't realise how defensive this forum is lol
Click to expand...
Click to collapse
No just no. A high proportion of XDA USERS' HOX's have problems. Maybe because most have noticed a problem and have done a google search to find xda as one of the first links. They sign up and vote/make a topic about their problem, now to you and the rest of us it looks like most of the handsets are suffering from some sort of problem.
Most take this on board without looking at the big picture, those normal run of the mill users that don't have any use for xda, don't post about problems because they don't have any.
Stop being so closed minded xda is not the be all and end all of android. There are users out there that have never herd of xda or even ics.
It's pointless complaining here with such an aggressive attitude just do the factory reset and be done with it atleast if you do it now you'll be able to backup your apps via abd/fastboot.
IMHO your just childish, you need to suck it up and stop being such a girl.
Sent from my HTC One X using Tapatalk 2
nikorette said:
No just no. A high proportion of XDA USERS' HOX's have problems. Maybe because most have noticed a problem and have done a google search to find xda as one of the first links. They sign up and vote/make a topic about their problem, now to you and the rest of us it looks like most of the handsets are suffering from some sort of problem.
Most take this on board without looking at the big picture, those normal run of the mill users that don't have any use for xda, don't post about problems because they don't have any.
Stop being so closed minded xda is not the be all and end all of android. There are users out there that have never herd of xda or even ics.
It's pointless complaining here with such an aggressive attitude just do the factory reset and be done with it atleast if you do it now you'll be able to backup your apps via abd/fastboot.
IMHO your just childish, you need to suck it up and stop being such a girl.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Right, so how about the fact that I've actually read a variety of other forums including some of the operators' own too? You have ASSUMED that I have only looked at XDA.
Aggressive?! Childish?! I think you're reading into things too much here... What part of "man pays relatively large sum for device and is disappointed by its many flaws" do you not get?
Anyway, this is boring me; I guess I'll never know if anyone else actually has the same camera issues...
Lol you still don't get it. Some people just do not know about forums. Unless you get a number from HTC that states how many returns per device made. Nobody, not you or me will know. Not reading anything other than what's on my screen. I'm defensive, by logic you're aggressive.
I guess you won't. Everyone else just ran a factory reset instead of crying about it.
Anyway like most of the threads on here its no longer about the op's post and more about the ego of the people posting. I'll admit I am at fault sorry if I derailed your thread..
Sent from my HTC One X using Tapatalk 2
Did u updated to 1.28? In 1.26 some pics cannot be processed,this has been solved completely in .1.28
Sent from my HTC One X using XDA
Adamsharif;
You do seem to have a phone that, under UK law does not appear to be fit for the purpose for which it is intended, regardless of the warranty obligations of HTC.
In reality, you should back everything up and factory reset the phone, if only to rule out any problems which could be solved, by doing this. If then, the phone does not work, you are well within your rights to demand a refund or a replacement.
If you're not willing to do a simple reset to fix potential issue, HTC and the users here are definitely not going to be willing to help you out. We can't reset the phone for you, but you still want to fix it by using and looking at the phone until it behaves itself.
adamsharif said:
Right, so how about the fact that I've actually read a variety of other forums including some of the operators' own too? You have ASSUMED that I have only looked at XDA.
Aggressive?! Childish?! I think you're reading into things too much here... What part of "man pays relatively large sum for device and is disappointed by its many flaws" do you not get?
Anyway, this is boring me; I guess I'll never know if anyone else actually has the same camera issues...
Click to expand...
Click to collapse
Here you go, proof that the majority of XDA members have no issues whatsoever with their device.
http://forum.xda-developers.com/showthread.php?t=1585082
Of course, people with no problems don't post much on forums, so the actual, real-world results of such a poll would be MUCH more one-sided.
As for your camera problem, many people have suggested fixes; Factory Reset, re-flashing RUU and, if all else fails, return the device and get a refund/replacement.
People seem to think their £500 device is going to be perfect. Don't get me wrong, It SHOULD be perfect, but no device is ever going to be. The HTC One X issues are also relatively minor compared to some devices that came before it.
kannanX10 said:
Did u updated to 1.28? In 1.26 some pics cannot be processed,this has been solved completely in .1.28
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Exactly. There's an old thread about this issue. Fixed with 1.28
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Ok, I guess I shouldn't have been so stubborn - currently backing up the device and will do a factory reset.
The backlight issue, however, is the one I'm returning for - the thing I find strange about both that and the camera issue is that they suddenly appear which really makes me feel that there are hardware issues in the first batch.
Lesson learned - don't buy a handset as soon as it comes out!
Personally I feel that mobile manufacturers need to undertake better testing and not rush their products to market - if you look at many of the recent handsets from Apple, Samsung, HTC there have been a lot of silly issues which have damaged reputations.
If I can have a HOX with working camera, backlight and calling it will be the perfect device!
You don't want to change your phone and yet you can't live with the problems. What do you want? Just ranting? Got it.
Sent from my HTC One X using XDA
ALL THE CORRUPTION ISSUES EXCEPT FLICKER are solved by firmware 1.29
My new hox was updated to 1.29 two days after I bought it, I never encountered the said issues, also flicker is related to overheat on 1.29 the phone temperature is a lot better
you regret buying the most praised and critically acclaimed android phone lol
I think we're being a little harsh on adamsharif, I love my HOX but its not without it's flaws and some of the 1.26 bugs were just messy...the phone shouldn't have been released with this firmware...it was rushed but I can understand why with the SG3 looming!
Unfortunately the average user turns to a forum when he / she has issues, the average user doesn't sign up to XDA to just say how happy they are, some do, just not your average joe, so it all looks like doom & gloom!
£500 is a lot of money, should we have to factory reset it after a few days / weeks? Should we not expect a near perfect product considering the money spent....I don't know....android isnt a perfect OS so I think the arsehole answer is get an iPhone!? I think in 3 months time we'll all be happier and mostly problem free!
Sent from my HTC One X using XDA
Guys please stop the pointless comments.
Back on topic. I suggest you try a third party camera app from market and see if that works. If it works, i too believe that hard reset will solve the problem. Also, don't underestimate hard reset. It usually solves most unknown issues
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Go to the above mentioned link to see the entire discussion.
Right now, nobody 'official' is talking either way.
In fact the freezing isn't even being addressed by Google/ASUS in their 'update'.
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
I get this issue when playing a game or typing.
pheonix991 said:
I get this issue when playing a game or typing.
Click to expand...
Click to collapse
IXChicharitoXI said:
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Muikkuman said:
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
danvee said:
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Click to expand...
Click to collapse
Jaxione said:
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Click to expand...
Click to collapse
Well, I can give you some insight on this issue. I am working on this issue for some time and I am doing some research and tweaks with my device. I have enabled "show touches when registered" in developers option. I have always had this feature on since day one.
My device came without any problems apart from one non functional top speaker which is still not working till now. I even opened my nexus to see what could be the problem but I couldnot really find anything in the hardware.
However, when I upgraded my Nexus to the new version JSS15Q from JSS15J manually (I forced it, it didnot come on my device when I did) , I started to have little touch issues which I didnot have before. I only had one faulty speakers with no other issues and after the update I started to notice these little issues. In the beginning, however I was also facing jumpy touches (suddenly two words being typed or key stuck in one place or :silly: a word next to the word i am trying to type is typed instead ) issues which automatically were gone, not sure due to restarting it or the device settled itself or maybe me getting used to typing that way.
Now I am having issues of stuck keys.The key or game is stuck if my device is registering a touch although it shouldnot
.
I am planning to do a hard reset and clear wipes and cache and see what happens. If the problem persists, I will simply go back to Jss15j again.
This tells me that the issue for my device is simply SOFTWARE and not in the hardware. However, regarding some other issues like waking up device in its case automatically by light/magnetic sensors works sometimes and sometimes it doesnot especially after few minutes in sleep or if there is no opened app when the screen got into sleep. Yet, it will always turn on if it is connected to the charger. So there could be some earthing issues with the device too which could be taken care of by kernels. Or it maybe could be due to my case simply.
This concludes for me as simply softwares issues that are brought with 4.3 JB which I guess would be hopefully solved soon.
I am planning to visit Asus for fixing my speakers and I will try to see if they give me some heads up about jumpy touches and auto wake up issues.
Good thought, but current information is that 15Q contained a firmware update to the digitizer (or the likes), so reflashing 15J wouldn't change that. Apparently device firmware can only flash up.
Google /ASUS would need to package another update to do that. I'm sure they will if that's determined to be the problem.
Probably Google is loosing out on us. We have so many issues to be addressed. This Nexus seems to be a hurried productoin. I mean, like 2 - wait, 3 - Nexuses in one year....... man that's pretty obvious that Google is competing stupidly
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
That's odd indeed. I rarely type on my Nexus 7, but I do have this issue on 4.3 with my Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
player911 said:
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
Click to expand...
Click to collapse
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
OJ in Compton said:
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
Click to expand...
Click to collapse
They would have to have some sort of programming to determine what to do. Not saying there are 2 different firmwares or devices. But it is a huge issue for me.
I think it is probably the same on all devices but some just don't type enough or use it enough for it to become a problem. Maybe they don't know?
My touchscreen was a bit wonky before the new update, not saying it was perfect, but very manageable. Now its missing inputs, random ghost touches, stuck touches, etc.
I haven't seen any proof that there is a N7 running on 15Q with no touchscreen issues.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Touchscreen freezing totally is a new symptom of 15Q on mine.
Froze solid just using Tapatalk.
The power switch would activate the shutdown menu, but I couldn't select any option via screen. Volume control didn't do it either.
Had to hold power for 20 sec to shut it down.
Rebooted and all is well.
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
danvee said:
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
Click to expand...
Click to collapse
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
I've had this problem too... Since I switched to PAC ROM and added the faux kernel it hasn't happened
Sent from my Nexus 7 using xda app-developers app
sfhub said:
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Love to, and thanks for the hard work.
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices .... don't want to give them any.....
They've got us caught here: they're not doing anything effective, and we'd be penalized for using self-help.
I really hope that it solves at least the touch issues.
danvee said:
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices
Click to expand...
Click to collapse
I seriously doubt unlocking the bootloader will void the warranty
they actually can't legally just say you unlocked it therefore your warranty is void. They have to show how your unlocking caused the warranty issue you are complaining about. Look up Magnuson–Moss Warranty Act. It originally came about to protect car owners from dealerships voiding their warranty for using after-market wipers, oil filters, etc. Yes, they can void your warranty, but they'd have to show that the oil filter caused your window to not open. There needs to be cause and effect.
nobody has ever posted they were refused warranty because they unlocked the bootloader
since google hasn't been signing their factory images, you actually need to be unlocked even to flash those
Anyway, it is up to you. You need to do what is right for yourself. I got tired of waiting for Google so took things into my own hands.
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
danvee said:
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
Click to expand...
Click to collapse
First off, I don't think they are trying to find fault with it to start, but if they did, yes, you could make the argument that the ease and availability of factory images made available publically was one of the reasons you bought this tablet over others and the fact that they require an unlocked bootloader, would make that standard procedure, so how could they possibly say that unlocking the bootloader is an automatic warranty void.
More importantly, simply ask them to show how unlocking the bootloader caused the damage/issue in question. They cannot, unless you really did do something that broke it as a direct result of something you put on the tablet after you unlocked it, but I think in that case, you would probably accept blame.
Hi I own a LG G2 and planning to upgrade. So I am researching into worthy upgrades and their common issues faced by people regularly.
So please mention the common and uncommon issues you faced while using this device or heard about.
Any other suggestions regarding my upgrade is also welcome.
Thanks
in_core said:
Hi I own a LG G2 and planning to upgrade. So I am researching into worthy upgrades and their common issues faced by people regularly.
So please mention the common and uncommon issues you faced while using this device or heard about.
Any other suggestions regarding my upgrade is also welcome.
Thanks
Click to expand...
Click to collapse
Common issue:
People that don't know what they're doing and are to lazy to read up messing up and soft bricking their devices.
Not so common issues but has been reported:
Lettering falling out on the back of the device
Camera showing some purple tint in low light
SIM cards not being picked up / read. Possibly not making proper contact
Some reports of camera lenses cracking
Have seen some people say that they have some dropped calls and/or SMSs not sending
Any other issues might possibly have been discussed in the Build Quality Concerns thread, might want to drop there and have a look at it.
BerndM14 said:
Common issue:
People that don't know what they're doing and are to lazy to read up messing up and soft bricking their devices.
Not so common issues but has been reported:
Lettering falling out on the back of the device
Camera showing some purple tint in low light
SIM cards not being picked up / read. Possibly not making proper contact
Some reports of camera lenses cracking
Have seen some people say that they have some dropped calls and/or SMSs not sending
Any other issues might possibly have been discussed in the Build Quality Concerns thread, might want to drop there and have a look at it.
Click to expand...
Click to collapse
Pink Tint again? Like the M7? Oh Boy :/
Why can't giant manufacturers like HTC and Sony get things perfect even for once :/
in_core said:
Pink Tint again? Like the M7? Oh Boy :/
Why can't giant manufacturers like HTC and Sony get things perfect even for once :/
Click to expand...
Click to collapse
Yeah like the M7 though I haven't seen a lot of reports of it and I haven't noticed a problem like that on my device either.
And yes, it would be nice to have things perfect if you take into consideration the price we pay for these devices. :good:
BerndM14 said:
Yeah like the M7 though I haven't seen a lot of reports of it and I haven't noticed a problem like that on my device either.
And yes, it would be nice to have things perfect if you take into consideration the price we pay for these devices. :good:
Click to expand...
Click to collapse
Exactly. Just about 10 months back I bought this G2 wi the same price the HTC One M8 is offered now in my country and after 7-8 months of usage suddenly i get this weird touch sensor issue and then after weeks it come to a point i cant even operate the phone properly and end up spending around $130 to change the whole display for it.
Thats the main reason I am changin this phone to get something which is reliable for a long period. Orelse i really loved my G2 and intended to keep it for atleast a Whole year more.
one common problem is the camera lens... even if you keep the phone in a case all the time, u are likely to get scratches on the lens, causing blur/soft pictures. but fret not! turns out its just some coating on it and can easily be removed with car polish or toothpaste.
I have read several threads and reviews on several different sites concerning the G4, and my head is spinning. I am currently on a g3, and looking to do an upgrade through best buy to re up my contract to avoid the unlimited data price increase. My choices are between an s6 variant and the G4. That's all background...so here we go...
I have read about touchscreen issues here on XDA. On other sites I have read about some sort of hardware issues with G4's mAde before September, but also saying that those are now resolved. Are these the same issue? Are these issues resolved? If it is not, how bad is this touch screen issue? I see lots of positive reviews, but then On a few trusted sites like XDA I see what looks like horror stories, but some of these stories are in posts that weeks and months old, so I am having trouble getting the picture of the current state of affairs. I also see something about a eifi issue too.
Camera. I read it is the best camera out there on some sites, but others saying that the phone takes a few seconds from "click to pic" so that you miss the shot you want. That is the issue I have on the g3, and don't want to repeat it. Can anyone share their experiences please?
Is there anything I am missing here?
Thanks in advance to all responders.
Sent from my VS985 4G using Tapatalk
wekurtz74 said:
I have read several threads and reviews on several different sites concerning the G4, and my head is spinning. I am currently on a g3, and looking to do an upgrade through best buy to re up my contract to avoid the unlimited data price increase. My choices are between an s6 variant and the G4. That's all background...so here we go...
I have read about touchscreen issues here on XDA. On other sites I have read about some sort of hardware issues with G4's mAde before September, but also saying that those are now resolved. Are these the same issue? Are these issues resolved? If it is not, how bad is this touch screen issue? I see lots of positive reviews, but then On a few trusted sites like XDA I see what looks like horror stories, but some of these stories are in posts that weeks and months old, so I am having trouble getting the picture of the current state of affairs. I also see something about a eifi issue too.
Camera. I read it is the best camera out there on some sites, but others saying that the phone takes a few seconds from "click to pic" so that you miss the shot you want. That is the issue I have on the g3, and don't want to repeat it. Can anyone share their experiences please?
Is there anything I am missing here?
Thanks in advance to all responders.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
I recently updated to software version 12A and have unfortunately been one of the users affected by the wifi issue. I don't receive any notifications while connected to wifi, but do when I turn wifi off and run off of 4G LTE. Annoying having to turn off wifi to get notifications from Gmail or Hangouts and then have to remember to re-enable it before streaming videos/music or downloading files. Apparently several users on this forum have discovered that the wifi notifications problem is related to IPv6 and that by disabling it (rooted device) or using a VPN (forces device to use IPv4) will fix that issue, I haven't tried this myself yet.
After updating when using wifi I have also experienced noticeable lag on Google or browsing the web using Chrome. It's not too bad but it just doesn't feel as snappy as it did before the upgrade. I haven't had any issues with the touchscreen on my G4 so far. It would appear that Verizon has since pulled that particular update as it was causing so many problems. Hopefully Android 6.0 Marshmallow fixes these problems, but so far there isn't a time-frame for when it is expected to be released.
In regards to the camera, it is nice to have the ability to adjust most of the controls manually. (although the f-stop appears to be fixed to 1.8) I have noticed it can sometimes take a second or two to take photos, but most of the time once it has focus in automatic mode it's pretty responsive. The G4 also has the ability to shoot RAW photos if you're into that kind of thing and prefer to edit the photos later and pull out more data from shadows/highlights.
Tek-Image said:
Apparently several users on this forum have discovered that the wifi notifications problem is related to IPv6 and that by disabling it (rooted device) or using a VPN (forces device to use IPv4) will fix that issue, I haven't tried this myself yet.
After updating when using wifi I have also experienced noticeable lag on Google or browsing the web using Chrome. It's not too bad but it just doesn't feel as snappy as it did before the upgrade. I haven't had any issues with the touchscreen on my G4 so far. It would appear that Verizon has since pulled that particular update as it was causing so many problems. Hopefully Android 6.0 Marshmallow fixes these problems, but so far there isn't a time-frame for when it is expected to be released.
In regards to the camera, it is nice to have the ability to adjust most of the controls manually. (although the f-stop appears to be fixed to 1.8) I have noticed it can sometimes take a second or two to take photos, but most of the time once it has focus in automatic mode it's pretty responsive. The G4 also has the ability to shoot RAW photos if you're into that kind of thing and prefer to edit the photos later and pull out more data from shadows/highlights.
Click to expand...
Click to collapse
Thank you for your help. I am a former HTC thunderbolt owner, so I am very warry about these things. I am sure the notifications issue will be solved with a update like the thunder bolt similar issue was.
If I may ask you, how long have you owned this? I am trying to get a sense of when it was made as I am concerned about this vague harware issue I read about in some places.
I am not sure I want to root this phone as I wish to use stuff like android pay now, and I have given up xposed due to severe battery drain on my g3 tied to it.
With respect to the camera, I have noticed that I take far fewer pictures on my g3 vs what I did on my samsung s3. I attribute this to the difficulty of talking the picture due to the delay.
This is more difficult decision than I wanted! Anyone else have any thoughts on these issues?
Sent from my GT-N5110 using Tapatalk
wekurtz74 said:
If I may ask you, how long have you owned this? I am trying to get a sense of when it was made as I am concerned about this vague harware issue I read about in some places.
Click to expand...
Click to collapse
It was purchased at the end of July so I've had it for about three months now.
I'm ready to throw mine out the window. The keyboard lag is horrendous on my phone. I can't type more than 4 words without have a missed key. I do love the phone other than that issue.
Mine died last week. This android system battery drain is murdering my battery. I've had it with this phone
Sent from my VS986 using Tapatalk
Maduro78 said:
Mine died last week. This android system battery drain is murdering my battery. I've had it with this phone
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
That's why I switched to the 6P