Related
Someone enlighten me on why official reviews of this phone do not include a GPS test. Knowing how all variants of the Galaxy S failed miserably on the GPS, would it not make sense to put peoples minds at ease with a simple mention of GPS? Why official reviewers never mention GPS is kind of strange and especially with this particular branded phone ;(.
OmniNut said:
Someone enlighten me on why official reviews of this phone do not include a GPS test. Knowing how all variants of the Galaxy S failed miserably on the GPS, would it not make sense to put peoples minds at ease with a simple mention of GPS? Why official reviewers never mention GPS is kind of strange and especially with this particular branded phone ;(.
Click to expand...
Click to collapse
i'm sure i read on a few of those that gps is quick and accurate. What official tests do you need? didn't all the mobilers show you the performance of their units?
Also do we need another thread for this?
ph00ny said:
i'm sure i read on a few of those that gps is quick and accurate. What official tests do you need? didn't all the mobilers show you the performance of their units?
Also do we need another thread for this?
Click to expand...
Click to collapse
An official review would be from someone like Engadget or Cnet or Android Central. Official reviewers are more meticulous with everything. I just don't understand why they wouldn't do it lol. There's no rational reason not to quickly mention that either "gps is very accurate" and vice versa =/. Strange.
OmniNut said:
An official review would be from someone like Engadget or Cnet or Android Central. Official reviewers are more meticulous with everything. I just don't understand why they wouldn't do it lol. There's no rational reason not to quickly mention that either "gps is very accurate" and vice versa =/. Strange.
Click to expand...
Click to collapse
engadget is meticulous with their reviews? lol you're kidding right?
you should probably catch up on mobiler's reviews which had gps tracking with diagrams drawn. If that's not enough for you then what is
Engadget goes straight to the main points that matter and give an educated opinion, which is what I look for. It's blog short, meaning very little fluff. If I want to read an exhaustive and robotic detail of every feature, with very little I would call "impressions" because really, almost every phone is good to them, I read a GSMArena review. If I want a poorly translated and very dry review that is so long but says so little, I read a mobile-review.com review. If I want to get my tabloid kicks and whoever is paying them to defecate on some brand or write vilifying troll reviews, I'll go Gizmodo. If I want blind fanboy lust reviews with tons of smooching, I read Androidcentral and Phandroid reviews.
Here's a respectable enough looking and sounding review, saying thte GPS locked in under 5 seconds and the compass seems better than most.
http://www.techradar.com/reviews/phones/mobile-phones/samsung-galaxy-s2-930907/review?artc_pg=11
I have found Anandtech have the most thorough reviews...
silverwolf0 said:
Here's a respectable enough looking and sounding review, saying thte GPS locked in under 5 seconds and the compass seems better than most.
http://www.techradar.com/reviews/phones/mobile-phones/samsung-galaxy-s2-930907/review?artc_pg=11
Click to expand...
Click to collapse
Frome same article:
"Another point we were happy with – the compass on the Samsung Galaxy S2 was more accurate than anything we've seen recently on smartphones, and actually pointed in the right direction most of the time."
This is indeed good news... ^^
GPS Test on engadget:
http://www.engadget.com/2011/04/29/samsung-galaxy-s-ii-gps-it-works-it-really-works-video/
Wis12 said:
http://www.engadget.com/2011/04/29/samsung-galaxy-s-ii-gps-it-works-it-really-works-video/
Click to expand...
Click to collapse
Just saw that as well ...
So in one instance at one location the phone's GPS locks quickly, but they don't say how quickly, if the lock was hot or cold or even how accurate it was. Also, why they turned off wireless network positioning is beyond me. If it works, it should only help, not hinder, the lock. If it doesn't, well, they should have said so. (Disabling A-GPS altogether would make sense if you only wanted to test the chip + antenna setup instead of the whole stack, but they didn't do that.)
I'm assuming there's labs where GPS signals can be simulated and conditions completely controlled. That's really the only way you can meaningfully test GPS functionality for a single device. To expect even a professional publication to run such a lab is unrealistic but they could certainly pay to have a few devices tested.
Aside from that there's the far easier way of comparison. Take a top of the line (civilian) GPS as a reference, 10+ phones including some with known good and known bad GPS, including non-Android ones and run a few tests in different locations.
But no, none of the above. I'm so fed up with people who conclude something works great just because it doesn't fall flat on it's face ... Instead, another video that takes ages to make, ages to watch and is absolutely devoid of any meaningful content. Bloody worthless ...
Yep, pretty hopeless video at Engadget. A quick lock with no real indication of accuracy, and no information about how well it maintains a lock. Face palm.
Jeez!
Nothing is good enough for you guys.. go buy the device and do the test yourself.
There are alot of posts about GPS and it simply works as it should!
techradar.com/reviews/phones/mobile-phones/samsung-galaxy-s2-930907/review?artc_pg=11
"the Galaxy S2 managed to lock our GPS in less than five seconds, and we were away in no time at all."
lugi93 said:
Nothing is good enough for you guys.. go buy the device and do the test yourself.
Click to expand...
Click to collapse
That simply isn't practical. Even if I wanted to pay for the SGS2 itself out of pocket just to review it, I still wouldn't have enough phones and/or stand-alone GPS units for a meaningfull comparison. Never mind the equipment needed for the audio, screen and camera quality measurements. A little more technical knowledge would surely be beneficial as well.
But the fact that this is impractical if not impossible for a private layperson to do is the very reason that tech publications exist in the first place! If all I wanted were an (more or less) uneducated impression or opinion I could just order the thing off Amazon and return it after a few day, if I don't like it.
This problem is not specific to mobile phones, of course, but it's especially bad there since a lot of non-overlapping knowledge would be required to do a proper review - basically you'd have to review each device
as a mobile phone (calling & SMS/texts only)
as a portable music player
as a compact camera
as a personal / in-car navigation device
as an e-book reader
as a mobile web-browsing device
as a gaming handheld
as an external storage device / thumb drive
... ... ...
Now, some of those features can be evaluated "at a glance" but a lot simply cannot.
And no, I'm not being perfectionist right now - if I were, I'd be insisting on multiple review copies from different batches ...
lugi93 said:
There are alot of posts about GPS and it simply works as it should!
Click to expand...
Click to collapse
Not quite. There are a lot of posts about the GPS, yes. But it seems to me that they are by people who don't have much experience with GPS, on mobile phones or otherwise. How could they know if it works as it should if they've nothing to compare it to?
In my very limited personal experience the LG P500 for example is so much better than the SGS1, NS and - by the looks of it the SGS2 as well - that it isn't even funny.
Wis12 said:
GPS Test on engadget:
http://www.engadget.com/2011/04/29/samsung-galaxy-s-ii-gps-it-works-it-really-works-video/
Click to expand...
Click to collapse
That must have killed them to say something positive that wasn't iPhone related!...
My contribution to testing the GPS functions, hopefully useful to people (particularly prospective buyers). If you have comments please post them there at the blog, rather than here.
http://www.youtube.com/watch?v=2VuptfBPIEI&feature=player_embedded
It is a general failing of many reviews that they do not compare but just give an overall impression .
But that is the same across a broad range from inkjets to GPS with all in-between .
Not that i am complain about my SGS2 GPS far from it i have no complaints it works as i want it to .
A minority view possible but 14 million users did not complain about SGS1 GPS some did but not 14 million of them .
jje
This is a new concept to me. There are no PCs that "just don't like Windows". With the same hardware, a PC will run the same software at the same speed with the same stability. All SGS II i777's have the same hardware, don't they?
There are of course variations in the quality (=bin) of some components, but that just sets voltage boundaries for a given clockspeed (or in extreme cases, makes a phone defective), but this shouldn't affect how a ROM runs.
What am I missing?
Why do some problems persist on what seems to be a clean install on some phones, and don't manifest on others? Do some ROMs run better because of different recoveries? What's left after a full wipe?
Obviously, installed apps and settings will make a phone perform differently, but that aside, shouldn't all SGS II run the same?
Eckyx said:
This is a new concept to me. There are no PCs that "just don't like Windows". With the same hardware, a PC will run the same software at the same speed with the same stability. All SGS II i777's have the same hardware, don't they?
There are of course variations in the quality (=bin) of some components, but that just sets voltage boundaries for a given clockspeed (or in extreme cases, makes a phone defective), but this shouldn't affect how a ROM runs.
What am I missing?
Why do some problems persist on what seems to be a clean install on some phones, and don't manifest on others? Do some ROMs run better because of different recoveries? What's left after a full wipe?
Obviously, installed apps and settings will make a phone perform differently, but that aside, shouldn't all SGS II run the same?
Click to expand...
Click to collapse
Simple answer is no not all devices are made the same. You see this with mass produced hardware. As for your PC ref. My brother and I have the same laptop while mine loves my set up, my brother has nothing but problems with it on his system. It comes alot down to personal set up and device. This has always been the case with mobile devices and custom roms. Stock roms are set to run on all devices the same. This is not so with custom roms.
Eckyx said:
This is a new concept to me. There are no PCs that "just don't like Windows". With the same hardware, a PC will run the same software at the same speed with the same stability. All SGS II i777's have the same hardware, don't they?
There are of course variations in the quality (=bin) of some components, but that just sets voltage boundaries for a given clockspeed (or in extreme cases, makes a phone defective), but this shouldn't affect how a ROM runs.
What am I missing?
Why do some problems persist on what seems to be a clean install on some phones, and don't manifest on others? Do some ROMs run better because of different recoveries? What's left after a full wipe?
Obviously, installed apps and settings will make a phone perform differently, but that aside, shouldn't all SGS II run the same?
Click to expand...
Click to collapse
Zel pretty neatly answered this, but I will also add that modern consumer electronics interact with the immediate environment far more than our pcs do. Light sensors, 3g radios, barometers, etc. are far less deterministic than our classic closed-loop pcs. Part of this perception of flux is based on this real flux, for example one of the core features people will discuss is call/modem quality, but driver tweaking vs. actual signal strength is a pretty fuzzy battle for anyone but an electrical/firmware engineer. And just like in the pc world, when you're talking under volting and over clocking your mileage will vary.
If you are methodical and read all the materials, your phone will operate tip top. It seems to me a lot (not all) of the variances often do boil down to the users configuration.
Sent from my iPad using Forum Runner
I have fixed a lot of computers and have been flashing custom roms for a year and ill tell you, in my personal opinion, problems are 90% user error. If people would all install properly and wipe everything completely and follow everything they're told to do and read all possible material on what they're flashing they can, a huge portion of the problems would dissapear. But is that gonna happen? I hope so
Heck I make mistakes too. None of us are immune to screwing up right? Good luck all, happy flashing.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Eckyx said:
Obviously, installed apps and settings will make a phone perform differently, but that aside, shouldn't all SGS II run the same?
Click to expand...
Click to collapse
Yes, they should and they do, absolutely with every ROM, stock or custom.
If they're purely, properly installed, they're all the same.
By "purely", I meant completely, virgin-like ROM without any add-on.
If you choose to install somethings else, to customize your needs or set it up the way you want, then it's a whole different ball game.
zelendel said:
Simple answer is no not all devices are made the same. You see this with mass produced hardware. As for your PC ref. My brother and I have the same laptop while mine loves my set up, my brother has nothing but problems with it on his system. It comes alot down to personal set up and device. This has always been the case with mobile devices and custom roms. Stock roms are set to run on all devices the same. This is not so with custom roms.
Click to expand...
Click to collapse
Just to chime in on the Windows thing - we buy a standard build HP computer at work for all developers. But if you put the same Windows disk in two of them and boot and install accepting all the defaults, there will always be slight variations in the way it configures itself between the two. It's probably the hardware detection that does it, but I swear you could get two of the same build lot and you'd STILL get something that didn't set up the same way. Sunspots? Power surge during the process? I dunno, but it does vary
You cant change the disk. Your network adapter has a MAC adress on it... windows will know something has changed. motherboard also has one.
A PC component are not the same at all.
You can buy a good I7 2600k or a bad I7 2600k. There are revisions of the very same model of CPU, memory, everything and its really hard to make 1 equal another.
Another thing is that one smartphone is a lot more delicate piece of hardware and the most important, has limited power to it components.
That makes harder to change anything on it. A small change could lead you to a failure.
just blame it on the ghosts in the machine and be done with it
votinh said:
Yes, they should and they do, absolutely with every ROM, stock or custom.
If they're purely, properly installed, they're all the same.
By "purely", I meant completely, virgin-like ROM without any add-on.
If you choose to install somethings else, to customize your needs or set it up the way you want, then it's a whole different ball game.
Click to expand...
Click to collapse
This is not the case. I have tested with two different EVO 4Gs and two different SGS IIs - of the same hardware revision, even.
I performed the same steps to root and ROM both of the sets of phones, and put the same ROM on them. There were no other apps installed, nor themes/addons. I then used each as my phone for a week, making sure that I installed identical apps and even synced app data.
Both performed differently. My i777 is the faster of the two, but my EVO 4G was the slower and more bug-prone.
Yes, this is anecdotal evidence, but I at least am convinced. Take it as you will.
Also the phones are made with lower quality checks than desktop. ie I can oc my sgs 1 up to 1.6GHz but uv of -25, the phone well restart. But other people can't go more than 1.2 and cab apply a uv of -150 on the same step.
This is a fact. Think if every phone it's done with high quality checks the price of the device will raise pretty high.
Once of the frustrating things is that the people responding on the forums, (ROM devs and regular users) often try to have it both ways.
If you're experiencing something they aren't, it's obviously your fault because it doesn't happen on their one phone so it can't possibly be anything but your own fault. Go wipe 50 times and do other things that will take 3+ hours each time and don't come back until you do.
Oh... you've done all that already and still having the issue? Oh well, all phones are different... tough luck, bro. I'm not going to spend any time on anything my one phone doesn't do.
(Never mind that a dozen other people have reported the exact same issue, and another several dozen are experiencing it but are too scared to post about it because they see how everyone else is being flamed, castrated or even banned for daring to suggest a bug.)
One way or another, it seems a convenient way to blow off users having legit issues.
While I suppose there might be slight deviations in components once in a blue moon, I think the "all phones are different" excuse is more often than not used as a way to easily dismiss people and issues without helping. It's been repeated over and over for so long now, the majority take it as "fact" without really putting much thought into how it could possibly be as widespread and dramatic as they're pretending it is.
I don't buy it.
Even just with modems... everyone's like, "Oh well all phones are different... some modems work better on some phones, or in different areas". What kind of BS is that? How on earth could any phone manufacturer then create a mass-market phone that worked across the country without hacking? I'm sorry, but you can't chastise and criticize the manufacturers for not producing the universal "uber-phone" that works great anywhere while at the same time admitting that "all phones are different" and therefore require hacking for your specific flavor or region. It's hypocritical.
I think it's very, very rare that actual hardware differences between the exact same model phone account for issues people experience, and is more often than not either user or dev (as much as they try to paint themselves as infallible gods) error that they don't want to bother with. "All phones are different" = "F-off, I don't want to deal with this"
sremick said:
Once of the frustrating things is that the people responding on the forums, (ROM devs and regular users) often try to have it both ways.
If you're experiencing something they aren't, it's obviously your fault because it doesn't happen on their one phone so it can't possibly be anything but your own fault. Go wipe 50 times and do other things that will take 3+ hours each time and don't come back until you do.
Oh... you've done all that already and still having the issue? Oh well, all phones are different... tough luck, bro. I'm not going to spend any time on anything my one phone doesn't do.
(Never mind that a dozen other people have reported the exact same issue, and another several dozen are experiencing it but are too scared to post about it because they see how everyone else is being flamed, castrated or even banned for daring to suggest a bug.)
One way or another, it seems a convenient way to blow off users having legit issues.
While I suppose there might be slight deviations in components once in a blue moon, I think the "all phones are different" excuse is more often than not used as a way to easily dismiss people and issues without helping. It's been repeated over and over for so long now, the majority take it as "fact" without really putting much thought into how it could possibly be as widespread and dramatic as they're pretending it is.
I don't buy it.
Even just with modems... everyone's like, "Oh well all phones are different... some modems work better on some phones, or in different areas". What kind of BS is that? How on earth could any phone manufacturer then create a mass-market phone that worked across the country without hacking? I'm sorry, but you can't chastise and criticize the manufacturers for not producing the universal "uber-phone" that works great anywhere while at the same time admitting that "all phones are different" and therefore require hacking for your specific flavor or region. It's hypocritical.
I think it's very, very rare that actual hardware differences between the exact same model phone account for issues people experience, and is more often than not either user or dev (as much as they try to paint themselves as infallible gods) error that they don't want to bother with. "All phones are different" = "F-off, I don't want to deal with this"
Click to expand...
Click to collapse
Great so what you're saying is everyone that says this (especially devs) are a bunch of dicks. Nice.
Sent from my SGH-I777 using Tapatalk 2
Nick281051 said:
Great so what you're saying is everyone that says this (especially devs) are a bunch of dicks. Nice.
Click to expand...
Click to collapse
That's actually not what I said at all, but I know it's a lot easier to summarize my post into one sentence that makes me look like an ass, than actually look at the points that I made.
sremick said:
That's actually not what I said at all, but I know it's a lot easier to summarize my post into one sentence that makes me look like an ass, than actually look at the points that I made.
Click to expand...
Click to collapse
I read the whole thing and that's exactly what it says.
Sent from my SGH-I777 using Tapatalk 2
Nick281051 said:
I read the whole thing and that's exactly what it says.
Click to expand...
Click to collapse
Nope. But let me simplify it for you:
1) There can't be the level of hardware variation that people claim. It's not seen in other electronics, and it's not been seen before the recent generation of smartphones. The assumption of its existence is a recent phenomenon however if it were real we'd see it everywhere, on other electronics other than phones.
2) If it were to really exist, people would lose the ability to legitimately blame the phone manufacturers for 90% of what they currently give them crap about, especially in regards to making a quality stock ROM. What are they expected to do, create thousands of variations of stock ROMs, one for ever county in the USA to compensate for this accepted "all phones are different" theology?
3) Due to it being repeated over and over and simply assumed to be true without any actual evidence to the fact, it's become a convenient way to dismiss user issues... even in the face of mounting evidence to the contrary on a specific issue. This unfortunate trend causes lots of friction between users and devs. Even if it were true, it's now become an over-used dismissal without allowing for the chance that the user might be right.
People can't have it both ways, but right now there's a lot of hypocrisy. If it's true, there's been no evidence actually shown... just anecdotal experiences that could be chalked up to any number of other things. And whether it's true or its not, either way a massive amount of thinking and behavior would then have to then change... but right now, people behave like it's true and not true at the same time, which is nonsensical and frustrating.
The simple answer is, there is no answer. Its the nature of the process.
I've had one click roms fail the 1st attempt only to succeed the 2nd without even closing the Odin just reconnect the phone.
Either you accept that and have fun with it. Or stick to stock and move on.
Sent from my SGH-I777 using xda premium
sremick said:
Nope. But let me simplify it for you:
1) There can't be the level of hardware variation that people claim. It's not seen in other electronics, and it's not been seen before the recent generation of smartphones. The assumption of its existence is a recent phenomenon however if it were real we'd see it everywhere, on other electronics other than phones.
2) If it were to really exist, people would lose the ability to legitimately blame the phone manufacturers for 90% of what they currently give them crap about, especially in regards to making a quality stock ROM. What are they expected to do, create thousands of variations of stock ROMs, one for ever county in the USA to compensate for this accepted "all phones are different" theology?
3) Due to it being repeated over and over and simply assumed to be true without any actual evidence to the fact, it's become a convenient way to dismiss user issues... even in the face of mounting evidence to the contrary on a specific issue. This unfortunate trend causes lots of friction between users and devs. Even if it were true, it's now become an over-used dismissal without allowing for the chance that the user might be right.
People can't have it both ways, but right now there's a lot of hypocrisy. If it's true, there's been no evidence actually shown... just anecdotal experiences that could be chalked up to any number of other things. And whether it's true or its not, either way a massive amount of thinking and behavior would then have to then change... but right now, people behave like it's true and not true at the same time, which is nonsensical and frustrating.
Click to expand...
Click to collapse
No you're actually wrong because sometimes things CAN go wrong with flashing stuff. And modems in fact do work better in some places than others even though they try to make them universal it is very difficult to do that. Also, if a dev doesn't see a problem, how is he supposed to fix it? Riddle me that one. Also, restoring should take at most an hour with something like titanium backup. So 3+ hours is bull.
Sent from my SGH-I777 using Tapatalk 2
Nick281051 said:
if a dev doesn't see a problem, how is he supposed to fix it?
Click to expand...
Click to collapse
He can start by not flaming the several people experiencing it (which scares away others also experiencing it, self-validating him and making him think the problem is less-common than it really is)
There's a difference between a problem being simply difficult for a dev to pin down and solve, and just attacking any user who dares bring up an issue that the dev himself isn't experiencing. Therein lies the hypocrisy, though: if "all phones are different", then a dev has to accept that a problem a user is experiencing might not be the result of stupidity on the user's part, and might actually be something in the ROM that simply didn't surface on the dev's phone, but is still something that needs to be addressed at the ROM level.
I totally accept that an issue the dev can't reproduce on his own phone is harder to resolve. But there are several devs who even make ROMs for phones they don't own anymore, and still manage to work with users to resolve issues. App devs do the same thing to resolve incompatibility bugs/issues with specific phone models the app dev don't own.
Also, restoring should take at most an hour with something like titanium backup. So 3+ hours is bull.
Click to expand...
Click to collapse
Not quite. Just the backup alone takes 45+ mins on my phone. The restore is the same amount, so you've got 1.5 hours right there without taking into account everything else that TB doesn't handle that needs to be reconfigured by hand, or the actual flashing, and tracking down other surprises. And because I apparently am one of the few people who care about their data, I also back up my internal SD... just in-case something goes wrong. I know the wipe shouldn't touch it... but "**** happens" and if something goes wrong during a flash and I didn't have a backup, it'd be my own fault and I'd be subsequently flamed for that. So I play it safe.
Once again, a case of users for whom its quick trying to tell everyone else they're full of BS. I accept that for some users, whether it's the # of apps, amount of data, or whatever, it goes fast for them. Lucky them. Why can't they accept the fact that it's not "10 mins" for everyone like they spread around and flame others for suggesting otherwise?
Ok Here is the thing. I have personally been flashing and making custom roms for phones as far back as the Motorola razor v3. I have multiple phone running the exact same firmware, set up the exact same way and the have run totally differently. If all phone were made equal then there would be no returns due to issues the phone had as they would have all run the same and acted the same as the units that the OEM quality control tested. Lets take the Black Jack 2 as an example. The BJII was a WM phone that would self corrupt the system/media folder. This prevented any ringtones from working and the OS had to be reflashed. All this running on Stock firmware. This didnt happen to all of them, but became a well known glitch to anyone that did cell phone troubleshooting and repair. Did you ever stop to think why OEM and carriers dont use the roms from places like XDA? This is because things here are always under development. There will always be bugs. In the end the developers are making things for their phones and are nice enough to share it for others to use. Some do keep making roms for phones they dont have as this is overly not hard to do. They do this just to be nice. Except for the hardware drivers most of the under lying OS is all the same.
If a dev cant reproduce it then there is no way for them to fix it with the way people tend to report bugs. (The wrong way without the proper info)
Now lets jump to the present. I have 4 phones sitting on my desk. 2 are the HTC Inspire and 2 are the Samsung Captivate. Both running the exact same rom and apps, but guess what. They run very differently. On 1 Inspire and 1 captivate, I can OC to almost double, while the other 2 cant handle more then 1.2 over clock.
One of them also doesnt like the AOSP based software while the others are fine.
As for your backing up and restoring. It can take a long time if you have a TON of apps. Flashing custom roms are not for everyone. If you dont have the time or the want to learn something then you are doing it for the wrong reasons.
sremick said:
He can start by not flaming the several people experiencing it (which scares away others also experiencing it, self-validating him and making him think the problem is less-common than it really is)
There's a difference between a problem being simply difficult for a dev to pin down and solve, and just attacking any user who dares bring up an issue that the dev himself isn't experiencing. Therein lies the hypocrisy, though: if "all phones are different", then a dev has to accept that a problem a user is experiencing might not be the result of stupidity on the user's part, and might actually be something in the ROM that simply didn't surface on the dev's phone, but is still something that needs to be addressed at the ROM level.
I totally accept that an issue the dev can't reproduce on his own phone is harder to resolve. But there are several devs who even make ROMs for phones they don't own anymore, and still manage to work with users to resolve issues. App devs do the same thing to resolve incompatibility bugs/issues with specific phone models the app dev don't own.
Not quite. Just the backup alone takes 45+ mins on my phone. The restore is the same amount, so you've got 1.5 hours right there without taking into account everything else that TB doesn't handle that needs to be reconfigured by hand, or the actual flashing, and tracking down other surprises. And because I apparently am one of the few people who care about their data, I also back up my internal SD... just in-case something goes wrong. I know the wipe shouldn't touch it... but "**** happens" and if something goes wrong during a flash and I didn't have a backup, it'd be my own fault and I'd be subsequently flamed for that. So I play it safe.
Once again, a case of users for whom its quick trying to tell everyone else they're full of BS. I accept that for some users, whether it's the # of apps, amount of data, or whatever, it goes fast for them. Lucky them. Why can't they accept the fact that it's not "10 mins" for everyone like they spread around and flame others for suggesting otherwise?
Click to expand...
Click to collapse
I agree with your point about the dev/user relationship. It can get pretty hostile sometimes which is completely unnecessary. Recently, I've been trying to emphasize the respect rule, regardless of who you are. Patience and cooperation can go a long way. And as zelendel said, sometimes people do report stuff the wrong way, but there's no need to be rude about it. Again, patience goes a long way.
Back to the main thing though, I'm not entirely sure how 2 fresh-out-of-the-box phones would work with the same settings and ROMs, but as others said, environmental and external factors can stress the phone and stuff just goes wrong. My phone, for example, would not operate the same as a fresh-out-of-the-box SGS2, even if you put the exact same stuff on it. Stuff just starts freaking out, and I'm pretty sure my phone is having hardware issues :[
i wanna buy a phone and i searched for it a lot because my sony z3+ was really bad and made me sad a lot.....plz tell me about this phone.battery and heat and android os(is that really pure android?how is the interface?)and screen and etc .because i had a brain tumor i can not work with screens that hurt my eyes.does this phone hurt eys?ty all
Don't buy this phone
A total waste of 240$ !!!
No support from UMIDIGI to serious software bugs
I've not noticed any "serious software bugs". What do you mean?
hotphil said:
I've not noticed any "serious software bugs". What do you mean?
Click to expand...
Click to collapse
Look at this. The moderator has deleted several posts from me. Also I've been banned three times, just to complain about the problems found in the ROM and the bad treatment received by the company.
Never more Mediatek and above all never more UMIDIGI.
Sorry, but not knowing how to use a product is different from the product being bad.
I was going to answer you, but ... I'll just ignore you.
Not worth it.
That's fine. But in that thread all you've posted is that there's "problems" with battery, camera and Bluetooth. You've posted no details. Kinda makes it hard for them to help you. And, as an aside, there's not many other people reporting the same issues. That's a very long way from being "bugs" that affect all units/users.
Interesting, a whole thread full of users who do not know how to use their mobile and can not distinguish a bug from its clumsiness.
Luckily we have experts like you who know how to light our way.
Thank you for your valuable help.
I have an umi z and i definitiefly say "dont buy any umi phone !!!"
It's true ,my battery gets swollen after 3 month of normal using and you have no chance to get a simple answer to your mails to the support team.
On a umidigi forum a "developer " just talking bull**** to us customer.
hotphil said:
That's fine. But in that thread all you've posted is that there's "problems" with battery, camera and Bluetooth. You've posted no details. Kinda makes it hard for them to help you. And, as an aside, there's not many other people reporting the same issues. That's a very long way from being "bugs" that affect all units/users.
Click to expand...
Click to collapse
I really love the fan boys who use the phone no more than to browse facebook and make calls. We posted the issues they are the ones who did not ask for details. Al they do is saying "oh, we dont have that problem on our testing devices". learn to read more or come earlier to read the deleted posts and maybe you find more about how useless umidigi is.
Just saying that if the vast majority of users aren't having those issues then you've been unlucky or there's something else wrong.
hotphil said:
Just saying that if the vast majority of users aren't having those issues then you've been unlucky or there's something else wrong.
Click to expand...
Click to collapse
The vast majority does not know what a damn 4k is altough the processor supports. The vast majority does not now what Volte is and does not needs it because they dont know what it does. The vast majority does not use bluetooth as a principle. The vast majority has the phone to say it is deca core without knowing what that really is
Hey folks,
I have noticed that in my poco if you hover you finger too close to your screen(note that i haven't touched the screen) it will capture it as touch. This becomes annoying when you are typing or playing games. I have asked for replacement but the technical guy who came for visit is not ready to accept this issue. And I am blocked now with this faulty poco.
This is because of the extra sensitive touch i guess(like glove mode in iPhone), I have changed the pointer speed, reset the phone but nothing works. This should be resolved by calibration but don't know how.
Please let me know if anyone else is facing this issue or has the solution for same.
Thanks
sachin_2552 said:
Hey folks,
I have noticed that in my poco if you hover you finger too close to your screen(note that i haven't touched the screen) it will capture it as touch. This becomes annoying when you are typing or playing games. I have asked for replacement but the technical guy who came for visit is not ready to accept this issue. And I am blocked now with this faulty poco.
This is because of the extra sensitive touch i guess(like glove mode in iPhone), I have changed the pointer speed, reset the phone but nothing works. This should be resolved by calibration but don't know how.
Please let me know if anyone else is facing this issue or has the solution for same.
Thanks
Click to expand...
Click to collapse
I have been writing about this issue since day 1, I somehow got the phone replaced. I showed them the PUBG game issue but they didn't help me, in the end I had to show them that ghost touch issue (which was a software bug and since the device was just launched very few people knew that it's actually a software glitch) so I forced them to take back the device.
I wasted hours on phone to emulate all the problems so that I could get it returned, this is a ****ty device and the company need to be sued for selling faulty products.
Is it something you might be able to get used to? Honestly, I've found this a problem on ALL touch-screen smartphones since forever lol.
Maybe it can be fixed in software in a custom kernel soon. If it bothers me that much when I get my device, I might look into it - it seems the kind of thing that could differ between devices and production runs, so the factory is forced to make a "best average guess" for all devices.
But it could also be a factory calibration thing, which has device-specific values in proprietary files or firmware....
shailendra1993 said:
I wasted hours on phone to emulate all the problems so that I could get it returned, this is a ****ty device and the company need to be sued for selling faulty products.
Click to expand...
Click to collapse
Because the touch is "too-sensitive", a purely subjective thing, you think the device is faulty and they should be sued?
So dramatic. Are you new to this place called reality or something?
It's a $500 flagship device, if you came into this expecting 100% premium quality then you're a fool.
CosmicDan said:
Is it something you might be able to get used to? Honestly, I've found this a problem on ALL touch-screen smartphones since forever lol.
Maybe it can be fixed in software in a custom kernel soon. If it bothers me that much when I get my device, I might look into it - it seems the kind of thing that could differ between devices and production runs, so the factory is forced to make a "best average guess" for all devices.
But it could also be a factory calibration thing, which has device-specific values in proprietary files or firmware....
Because the touch is "too-sensitive", a purely subjective thing, you think the device is faulty and they should be sued?
So dramatic. Are you new to this place called reality or something?
It's a $500 flagship device, if you came into this expecting 100% premium quality then you're a fool.
Click to expand...
Click to collapse
Ever heard about Honor 8 Pro? It was launched last year and was called the flagship killer, the issue is not present in there, why?
Ever Heard of any MiA1 or MiA2 device having this problem?
Do you have the device?
If not then try it out, it's not something you can live with.
What do you think I am asking for? I just want Xiaomi to admit that there is an issue and work on it and nothing else.
Not happening on my unit. Any specific steps to reproduce it?
shailendra1993 said:
What do you think I am asking for? I just want Xiaomi to admit that there is an issue and work on it and nothing else.
Click to expand...
Click to collapse
So go harass the Manager on Twitter, what can we do about it? Complaining about the device once is fair enough to raise awareness, but every thread I see seems like you are on a mission to destroy this community.
I don't see the relevance of comparing it to other devices. May as well say "Ferrari can make cars that fast, why can't my Prius?"
shailendra1993 said:
Ever heard about Honor 8 Pro? It was launched last year and was called the flagship killer, the issue is not present in there, why?
Ever Heard of any MiA1 or MiA2 device having this problem?
Do you have the device?
If not then try it out, it's not something you can live with.
What do you think I am asking for? I just want Xiaomi to admit that there is an issue and work on it and nothing else.
Click to expand...
Click to collapse
you should be known to the fact that many of xiaomi devices comes with bugs at first. Xiaomi fixes almost all bugs after some updates. Most of the current bug's fixes (audio, notification, battery percentage, ok google) are coming soon on next OTA. Some of them, they're investing. from my POV, Xiaomi is doing great with Poco's software side. Jai Mani himself taking care of these
you complain about camera?
- use gcam
you complain about miui?
- wait for AOSP Roms
you complain about the phone?
- get a refund
But don't just flood everywhere. Grab more cash. Get a Oneplus 6. Be happy with it. Have a nice day
CosmicDan said:
So go harass the Manager on Twitter, what can we do about it? Complaining about the device once is fair enough to raise awareness, but every thread I see seems like you are on a mission to destroy this community.
I don't see the relevance of comparing it to other devices. May as well say "Ferrari can make cars that fast, why can't my Prius?"
Click to expand...
Click to collapse
Please tell me why the issue exists on phones like Redmi Note 4, redmi Note 5, Redmi Note 5 Pro and now Poco but the problem is not there on MiA1, MiA2, etc. You will say that the software is different that's right, but can't the issue be of hardware kind because if they used the same displays why not the same touch hardware? and why the problem is still not solved in the Redmi Note devices?
I tweeted them all and there are some bug reports, Xiaomi did not reply to anything.
shailendra1993 said:
Please tell me why the issue exists on phones like Redmi Note 4, redmi Note 5, Redmi Note 5 Pro and now Poco but the problem is not there on MiA1, MiA2, etc. You will say that the software is different that's right, but can't the issue be of hardware kind because if they used the same displays why not the same touch hardware? and why the problem is still not solved in the Redmi Note devices?
I tweeted them all and there are some bug reports, Xiaomi did not reply to anything.
Click to expand...
Click to collapse
isnt redmi the low ends of xiaomi ? not surprised if they used lower grade Digitizer , if you are taking about mi series or mi mix ,then something is wrong
shailendra1993 said:
Please tell me why the issue exists on phones like Redmi Note 4, redmi Note 5, Redmi Note 5 Pro and now Poco but the problem is not there on MiA1, MiA2, etc. You will say that the software is different that's right, but can't the issue be of hardware kind because if they used the same displays why not the same touch hardware? and why the problem is still not solved in the Redmi Note devices?
I tweeted them all and there are some bug reports, Xiaomi did not reply to anything.
Click to expand...
Click to collapse
The issue does NOT exist on the Redmi Note 4, my Note 4 is perfectly fine.
The reason why devices are not updated by Xiaomi is because this is an OEM issue, OEM's will charge money to Xiaomi for fixes, and Redmi is budget crap line which Xiaomi don't want to go bankrupt over. You do know the Xiaomi fame of them having extremely small profit margins, right? If you want to have a 100% perfect digitizer on launch, go and pay twice as much for a device with identical specs.
This is a brand new device from a brand new department. We are the early adopters. Even the Google Pixel devices had major bugs when they first came out. Go get a refund if you're unhappy. And if you can't, then learn the lesson to not be an early adopter for a brand new product line.
The gain on the digitizer is too high (or the threshold is too low), it's a SOFTWARE issue. Simple as that. I don't have the device yet so I can't tell if it's in the kernel driver or the firmware, but it's 100% a software issue because literally all mobile phone digitizers are calibrated in software for the past decade. Anybody who knows anything about Linux/kernel development knows this stuff.
Enough with your non-constructive ramblings, it's not beneficial to the conversation at all. Stop being obnoxious and passive-aggressive with your patronizing questions.
---------- Post added at 13:19 ---------- Previous post was at 13:08 ----------
Back on topic,
@OP, I wonder what digitizer hardware you have. Is there a service menu we know about yet? According to the kernel source and config there may be two possible digitizer panels for the Poco (just like how they often have two or three different LCD suppliers for one device).
If I notice an imperfect touch on my device when it arrives, I'm going to dig into the kernel source to see if I can find something - but if people have two different digitizer panels then that will complicate things.
Another thought:
Do you have a tempered glass protector? If not, try it. It could reduce the sensitivity. It may even be *intentional* to allow that.
CosmicDan said:
The issue does NOT exist on the Redmi Note 4, my Note 4 is perfectly fine.
The reason why devices are not updated by Xiaomi is because this is an OEM issue, OEM's will charge money to Xiaomi for fixes, and Redmi is budget crap line which Xiaomi don't want to go bankrupt over. You do know the Xiaomi fame of them having extremely small profit margins, right? If you want to have a 100% perfect digitizer on launch, go and pay twice as much for a device with identical specs.
Do you have a tempered glass protector? If not, try it. It could reduce the sensitivity. It may even be *intentional* to allow that.
Click to expand...
Click to collapse
If you are saying it's a software bug, then I can believe it, I just want someone experienced to tell me if it's a s/w issue or h/w issue, the problem is getting rid of the phone is not easy, no one is buying this, Flipkart is making the issue more complex, the replacement itself took me 2 hours to explain the guy about the problems and I am not sure they will provide the return.
Also, Pixel had the issue fixed as soon as the issue was discovered and other OEM's had to fix the issue too, Google didn't charge money for that, the multitouch issue was fixed in May patch, why do you think it still exists in MIUI?
Zenfone Max Pro M1 is a ****ty device I agree but the device has the same spec as Redmi Note 5 Pro but costs a lot less and they have already fixed the issue, it's also a crappy budget phones and you know what? Zenfone is the worst company and well known for not fixing bugs, but they still did!
Talking about the go buy other crappy phones for more: Nokia 7 Plus and Honor Play are still a better deal only HPlay has a bad camera but Honor has a better support than atleast Xiaomi, their performance is not like Poco but atleast there is no lag, no framedrop, no structural issues, no touch issue or anything. I would be glad to switch only if I get my money, if not atleast someone from Xiaomi guarantee me that they issue will be fixed soon.
I see that you don't have the device till now, I will wait till you get the device and test it. Here is the bug report, see if you can reproduce it once you get your hands on it:
http://en.miui.com/forum.php?mod=viewthread&tid=3746297&page=2#pid30155106
----------------------------
Call me idiot or anything you want, I have kept the replacement that I got all packed up and didn't open the package, because I am trying to sell the package in case Flipkart refuses refund. I have to use an old Lenovo Vibe K4 Note instead.
----------------------------
Wait for an update: I have very few days left to return the device, since Xiaomi is not telling if the bug will be fixed or not one can not say anything about it. Except for the 10 bug fix update MIUI9 is not going to get another update and all the bugs will be tested and fixed once MIUI10 is launched whose launch date is December 2018.
This is not my story, an admin said that all development work on MIUI9 (all versions) has been stopped.
People who installed MIUI10 on their Poco are not telling if the problem is fixed in the beta ROM but Redmi Note 5 Pro users are saying that the bug is still not fixed.
CosmicDan said:
The issue does NOT exist on the Redmi Note 4, my Note 4 is perfectly fine.
The gain on the digitizer is too high (or the threshold is too low), it's a SOFTWARE issue. Simple as that. I don't have the device yet so I can't tell if it's in the kernel driver or the firmware, but it's 100% a software issue because literally all mobile phone digitizers are calibrated in software for the past decade. Anybody who knows anything about Linux/kernel development knows this stuff.
Click to expand...
Click to collapse
i. Many people don't seem to have this problem and the reviewers didn't report the problem with the Armoured edition, why? they have the same setup (hardware and software) right? And if the review units do have this problem then how come reviewers didn't say anything?
ii. Let's say they by mistake left a bug, that clearly means no testing was done with this device, they just launched it without checking anything. But what can you expect from a Chinese phone, right? So, why call it a flagship killer killer and why so much hype?
This is a real issue and needs to be fixed and Xiaomi should atleast show some respect by telling this to the customers and you are defending them for no reason. You have enough technical knowledge, do you really think we should have an inaccurate and slow input device just for the sake of a faster processor? because that's most stupid statement of all time. Input device should be as accurate and fast as the processor for full usage. It's like having a 1Gbit internet but a computer that can process only few MB per sec, the throughput will be a lot less and waste of money.
Hello.
Will this problem be fixed? Is it a software or hardware problem?
I will have to sell this phone if it does not fix it.
Thanks.
update:
Please, likes and leave comments there:
en.miui. com / forum.php?mod=viewthread&tid=3746297&page=3
We need to be noticed.
Video demonstration of the problem (playlist. 2 video):
youtube.com / watch?v=C6s2ZqwpkPY&list=PLFpEm6ANmniMdy13bBct5L-OxJrR3RLiY
shailendra1993 said:
*snip*
Click to expand...
Click to collapse
I answered your questions, I gave my opinion and shared the facts that I know, and you just ignored them and repeated yourself.
Please just stop spamming and hijacking threads with drama. You keep saying the same things over and over and it's just exhausting; nobody wants to read it anymore.
---------- Post added at 17:44 ---------- Previous post was at 17:20 ----------
@ Everyone with the issue,
Try the Magisk module mentioned in this thread (and read more about it there). It might solve it, might do nothing, might cause bootloop... good luck!
CosmicDan said:
I answered your questions, I gave my opinion and shared the facts that I know, and you just ignored them and repeated yourself.
Please just stop spamming and hijacking threads with drama. You keep saying the same things over and over and it's just exhausting; nobody wants to read it anymore.
Click to expand...
Click to collapse
Do you have the phone?
shailendra1993 said:
Do you have the phone?
Click to expand...
Click to collapse
Irrelevant to the point I was making.
I told you to stay on topic and get over it. Posts reported for off-topic / spam / harassment, and congratulations for being the first person in my 9 years here to make it onto my Ignore List.
Enough of the back-and-forth here thanks guys... Keep things civil or move along.
There were something like that in a device called infinix zero 2. and it needed a screen protector to solve the issue.
shailendra1993 said:
Please tell me why the issue exists on phones like Redmi Note 4, redmi Note 5, Redmi Note 5 Pro and now Poco but the problem is not there on MiA1, MiA2, etc. You will say that the software is different that's right, but can't the issue be of hardware kind because if they used the same displays why not the same touch hardware? and why the problem is still not solved in the Redmi Note devices?
I tweeted them all and there are some bug reports, Xiaomi did not reply to anything.
Click to expand...
Click to collapse
I believe you're not a retard who keeps trying to get a slice of cheese on a electrified metal plate and keeps getting electricuted but still persist on taking the cheese from it. If you keep having issues with Xiaomi devices then why stay with the brand. Move on and look for other brands instead of staying and keeps whinning.
Jaistah said:
I believe you're not a retard who keeps trying to get a slice of cheese on a electrified metal plate and keeps getting electricuted but still persist on taking the cheese from it. If you keep having issues with Xiaomi devices then why stay with the brand. Move on and look for other brands instead of staying and keeps whinning.
Click to expand...
Click to collapse
Eh, just ignore it. I did try and report him but that was silly because I'm the one who look like a jerk in this thread haha but it's unfair to expect moderators to dig into the issue of him spamming across the 5+ threads.
So just ignore, and let's try and stay on topic. He will ignore everything you say an just keep repeating the lies of it being a defect on other devices as his main argument.
- Does call recording work out of the box? (ACR for example)
- Can you take a picture of Excel running, and Waze running? I would like to see how it looks like with curved corners. Maybe a second smartphone picture would be better? I don't know.
- Do you experience this "touch issue" that many complain about?
Thank you for answering. I know it's a lot to ask for.
Ps.: I placed my order, but have not paid yet. I know I could buy a OnePlus, but my friend had a dead touchscreen issue there as well, and heck, all models were notorious for their issues. The battery is also too tiny on that phone. There is the Pixel 3XL, which will cost like 1000EUR or something. So yea. Would like to stick to Poco F1.
h8Aramex said:
- Does call recording work out of the box? (ACR for example)
- Can you take a picture of Excel running, and Waze running? I would like to see how it looks like with curved corners. Maybe a second smartphone picture would be better? I don't know.
- Do you experience this "touch issue" that many complain about?
Thank you for answering. I know it's a lot to ask for.
Ps.: I placed my order, but have not paid yet. I know I could buy a OnePlus, but my friend had a dead touchscreen issue there as well, and heck, all models were notorious for their issues. The battery is also too tiny on that phone. There is the Pixel 3XL, which will cost like 1000EUR or something. So yea. Would like to stick to Poco F1.
Click to expand...
Click to collapse
Call recording is built into the phone app.
I have not experienced the touch issues, some users have