Hey
I got my x829 a week ago and was super excited for this awesome value phone...But from the very start it randomly rebooted with the stock EUI 5.8.016s (been told its US version)
I was very sad since Geekbuying offers no support, now i tried my luck with the "Small EUI 7.1" Custom rom as i hoped this would resolve my issue, to my disappointment it has not, and it still randomly restarts out of nowhere when just laying idle on the table.
Does anyone have a clue what could be the cause and how to fix it?
As mentioned it been there from the very first time i booted the phone, i havnt even at any point inserted a Sim card or SD card as its pretty much useless like it is now.
It gets luke warm to the touch but nothing major that i would think would cause this, also i installed Deadtrigger and played for 30 minutes with no issues...Seems only to reboot when in idle and locked.
Hope you guys have some ideas because right now i have a 200 dollar brick...
I now did a completely clean flash of Resurection Remix rom and the issue is still there, sometimes just turns off and you have to hold in power button for 10 seconds for it to boot up again, other times it simply reboots.
Once its boots and i use the phone it works just fine, i have yet to see it randomly reboot/power off when im playing a game or actively using it, but as soon as it sits idle it goes wrong.
Im thinking it might be doze mode related but not quite sure.
Noone else experiencing these issues?
Im slowly going insane, yesterday the phone trolled me and decided work fine for 8 hours straight (even laying idle on the table), only to start randomly rebooting again.....i used it for quite some time yesterday confirmed that it works perfectly fine under heavy loads.
But every time i stop using it, put it on a desk or in my pocket so that it goes into idle and the screen powers off, then after 2-10min it begins to reboot for no apparent reason.
Im out of idea's i tried some diffrent power profiles in the RR rom, it works fine under heavy load with no power connected so the battery should work perfect i have no clue what could be the issue....
If anyone have any ideas i would welcome them....
Can't you email the guys from Geekbuying and tell them about this problem that you're having? Seems like some serious issue that you're facing over there. Try to contact them and tell them what is wrong. In the beginning they will ask you to install a stock ROM.
I've had a similar problem with my phone, simply the fingerprint was not working upon receipt and my wife didn't know how to flash the ROM, so she had to wait for me to arrive home in order to check if the phone was working properly. After some email exchange, the guys from honorbuy.com were suggesting Stock ROM, buy I was lucky enough that the fp started to work after this. I am not sure that they would respect their 14-day return if I came home after more than 20 days from purchase.
At least you can try to contact them. It can be a motherboard issue but who knows...
Set your minimum Cpu frequency to a relative high value.
Do you have to unlock the phone by tipping the PIN of your SIM card after the random reboots? If so it could be a problem related to your SIM...
Normally if you inserts the SIM card while a Android device is powered on and running, the phone is going to reboot and you have to tipe the PIN. I know about many phones that are having problems with specific SIM cards. And our Le Max 2 is one of those. The most reported issues are totally killed cards for example. But random reboots are also a common problem. I don't want to go more into details, cause it's a stand alone story.
So you can check if the device will perform normal and without rebooting by using it without a inserted SIM card.
If you're not facing any problems then you can simply try another SIM ...
Here in Germany are hundreds of people who are getting frustrated because of this kind of problem. Older cards getting killed by newer phones (especially when the phone is a so called China phone). For example combination of xiaomi mi 5/5s and T-Mobile Germany seems to be a problem.
Indeed sim cards can reboot phones, if we're you I'd install another Rom , with full data wipe (very important). Remove sin card in the night and check if phone is ok in the morning, use 3c toolbox app to check error logs (root required)
Like unrafa said, remove Sim card over night and let the app do it's job.
I'm also using 3c toolbox for many years now. It's the best all in one app when it comes to failure and issue tracking!
?
Hey thanks for all the replies
I have never had a sim card inserted, i tried to put one in yesterday to see if it might solve the issue, but it didnt.
I booted into TWRP and waited for the screen to time out so it went into idle, there it behaves just fine when the screen is turned off, but i think TWRP doesnt force a "idle" state because i noticed the battery went from 80-5% with the screen off in about 9 hours.
I did think about the CPU freq myself but im thinking its about the minimum voltage maybe, setting the freq higher i cant see should fix anything, speaking from my experience with undervolting/overclocking computers im guessing the current minimum cpu freq isnt stable at the voltage its getting.
However i have never done any undervolting/overclocking on phones, how do i go about doing it in an easy way?
I will try install 3c toolbox and see if i get any useful info, should come pretty fast as it most of the time happens within 2-5 minutes of the phone being idle.
It is a known bug with the x829 variant aka the canceled US variant. I have experienced it with my prototype x829 since I got it for doing beta testing for LeEco. It happens less often on MIUI and AOSP/lineage based roms. X829 will never be officially launched all of its inventory was dumped on to Indian and Chinese sites.
deadman96385 said:
It is a known bug with the x829 variant aka the canceled US variant. I have experienced it with my prototype x829 since I got it for doing beta testing for LeEco. It happens less often on MIUI and AOSP/lineage based roms. X829 will never be officially launched all of its inventory was dumped on to Indian and Chinese sites.
Click to expand...
Click to collapse
that makes sense.. unfortunately I never knew this.. otherwise I wouldn't have ordered a x829.. my device is still on the way.. I'll sell or return it if I notice any of these issues..
deadman96385 said:
It is a known bug with the x829 variant aka the canceled US variant. I have experienced it with my prototype x829 since I got it for doing beta testing for LeEco. It happens less often on MIUI and AOSP/lineage based roms. X829 will never be officially launched all of its inventory was dumped on to Indian and Chinese sites.
Click to expand...
Click to collapse
Can you disclose any official document regarding this? My X829 is arriving tomorrow, I hope I'll be lucky not to have this problem, but if it happens I'd want a solid ground for refund claim.
Thanks!
appsmarsterx said:
that makes sense..
Click to expand...
Click to collapse
Actually, it doesn't. From a hardware perspective, the X829 firmware pulled from one of those beta devices works fine on the other model name variants. I've run it for a while on my X820, and never experienced a random reboot.
It's also not beyond the realm of possibility that LeEco took a lead off base and had a metric ton of cnc'd aluminum shells and packaging made, printed with the X829 name and US applicable FCC information, and later scrapped the idea in favor of a new, US only model. And, rather than recycle the finished parts for the value of the base metal, slapped them together with possibly sub-par internals (i.e. finished circuit boards which proved during QC to not be 100% reliable) and dumped the result at very low prices into the Chinese re-seller market, where they happily flashed them with the older, leaked X829 firmware to make them attractive to frugal US buyers. Come to your own conclusions, but consider the lower price tag of the models sold as X829's, which are not supported by LeEco USA, and ask yourself how this model came to be.
Does anyone have any definitive knowledge of specific hardware differences between these models, or is it still in the realm of assumption and "urban legend"?
Well i sure hope thats not true, i installed 3C now and turned on the event monitoring, waiting for it to reboot again.
Speaking og this topic, check this screenshot, i found it bit weird my phone score that much lower than a real x820.
My device identifies as x820 on the left because og the RR rom.
https://imghost.io/image/aSDUO
Im guessing this big a difference isnt because of a poorly optimized rom.
My x829 that I got from Banggood on Monday hasn't rebooted on me once, the fp sensor works fine, and I've had no negative issues with it at all actually.
I'm just super confused about whether it's flashable or not, and what ROMs have a functioning camera!
Kodes said:
My x829 that I got from Banggood on Monday hasn't rebooted on me once, the fp sensor works fine, and I've had no negative issues with it at all actually.
I'm just super confused about whether it's flashable or not, and what ROMs have a functioning camera!
Click to expand...
Click to collapse
I also ordered mine from Banggood too. it's still on its way .. hoping everyone would be fine too..
Kodes said:
My x829 that I got from Banggood on Monday hasn't rebooted on me once, the fp sensor works fine, and I've had no negative issues with it at all actually.
I'm just super confused about whether it's flashable or not, and what ROMs have a functioning camera!
Click to expand...
Click to collapse
Resurrection remix rom works perfectly fine except my little problem, but i had that with stock rom aswell.
Small update, after installing 3C and turning on the recording it has not rebooted, i wonder if the recording prevents it from 100% idle state thus solving the problem.
If anything its a good temporary solution and i guess proves its not hardware related :/
This is the longest its gone without reboot in idle (about 13 hours and counting), i will shut it down and insert a simcard + turn on recording and see what happens now.
Khorngor said:
Small update, after installing 3C and turning on the recording it has not rebooted, i wonder if the recording prevents it from 100% idle state thus solving the problem.
If anything its a good temporary solution and i guess proves its not hardware related :/
Click to expand...
Click to collapse
Maybe, maybe not. Sounds like it could be a power management issue, which may well be hardware related. With the logger running, it may never try to go into deep sleep.
The performance numbers are pretty poor as well. I'd give a clean install of AOKP MM a shot and see what you get with that ROM. My X820 scores well above the recorded Antutu score for X820 with that one installed.
RandyT2 said:
Maybe, maybe not. Sounds like it could be a power management issue, which may well be hardware related. With the logger running, it may never try to go into deep sleep.
The performance numbers are pretty poor as well. I'd give a clean install of AOKP MM a shot and see what you get with that ROM. My X820 scores well above the recorded Antutu score for X820 with that one installed.
Click to expand...
Click to collapse
You refering to the brand new AOKP Rom posted 2-3 days ago or you thinking about another one? please link the one you have in mind and i will give it a try.
Ye my scores a total **** compared to the "normal" version, not sure whats going on, inb4 china spoofed fake chip...
Related
Hello.
I have questions for current users of P9000. I do not have this phone. I can buy new P9000 for 180 USD. What you think? It is good idea? Chinese phones are always good "on paper" but always have bugged stock roms. We have any stable rom for P9000 for daily use without pain in ass? If you had to choose, would you buy it a second time?
Please help me decide.
Regards
I bought it but I am not hapy with it.
Camera from the biginning was not well, and now stopped at all by itself. I did not drop or do something just in one day it stopped to launch.
Edge of display came of from the body. Battery drain is good if you don't use 3G.
If you want good phone search among Xiaomi , Meizu or ZTE.
For me "ZTE nubia z11 Mini" is good.
Definitely not. Gps, fast charge and camera are not good enough. Android pay does not work..buy one plus 3
Its is a good phone , interesting phone, but google pay not working, when it is working its is a great phone....
Enviado do meu SHIELD Tablet K1 através de Tapatalk
I think its all about expectations. For me after rooting and flashing Eragon ROM I am happy with what I paid for. Don't expect Samsung/Apple standards for its camera its really bad compared to those. I dont use google/android pay so that doesn't bug me.
For that price I don't think you can get anything better.
I'm not sure what Google pay is but there is no problem buying apps with the phone.
GPS is not perfect but usable, same with the camera.
Battery time is very good at least for me. Twice I have left the phone fully charge at 10 pm and att 5 am I have 100% & 99%. This is with wifi and sync on. When I hade 99% there was a Titanium Backup of all user apps 200+ in the middle of the night.
Fast charge I don't know anything about, I charge the phone during night so that would not be an issue.
I have Eragon ROM on the phone.
The physical device itself is pretty solid but the stock software, as of present, is similar to that of an early beta build.
I'd advise you don't take the leap as I believe Elephone shouldn't be encouraged for releasing an incomplete phone.
I would not buy again. External SD doesn't work at all. Had to factory reset after update to get fingerprints back. Spontaneous reboots & alarms unreliable since last OTA update. I'd spend more money and get OnePlus 3 or used OnePlus 2.
Sent from my P9000 using Tapatalk
meganox said:
I would not buy again. External SD doesn't work at all. Had to factory reset after update to get fingerprints back. Spontaneous reboots & alarms unreliable since last OTA update. I'd spend more money and get OnePlus 3 or used OnePlus 2.
Sent from my P9000 using Tapatalk
Click to expand...
Click to collapse
External SD works just fine. Fingerprints dissapearing after an update of software is a known issue but a very minor inconvenience - all you have to do is add them back again. Which software version are you currently on?
20160810
I knew about the fingerprint issue but misread something from the release notes that caused me to think it had been fixed. It's not that they go missing, it's that they remain used but unrecoverable, so I went for a few weeks with only one fingerprint. No biggie.
My SD Card has never, ever worked. It's as though it's not even there. SIM works fine in that slot though.
In general I find the phone is not quite stable enough that I would recommend it to anyone else to buy, but it's not quite unstable enough that I sent it back, although I might have done if I'd had a decent spare.
Sent from my P9000 using Tapatalk
On paper it sounds good but too many bugs for me to use as a my daily driver so sent back to Amazon. GPS not great, fingerprint unlock not reliable. Unable to send or receive text without rebooting occasionally which was the biggie for me.
You get what you pay for, all phones have problems at one time or another no phone is perfect, GPS after lock works fine, finger print a bit slow but never had a problem as such, Camera isn't the problem it's the software use a different app and it's not that bad and I still have an Xperia Z1 so i can compare, Android Pay i live in the UK all bank card are contactless why fiddle about with a phone when it easier to just pull out your bank card the number of time i've stood behind some one trying to pay for something with their IPhone is mind numbing, you can make calls you can send texts you can receive calls and texts, if you have a higher budget then try something else if not this phone is as good or as bad as any.
carlx said:
You get what you pay for, all phones have problems at one time or another no phone is perfect, GPS after lock works fine, finger print a bit slow but never had a problem as such, Camera isn't the problem it's the software use a different app and it's not that bad and I still have an Xperia Z1 so i can compare, Android Pay i live in the UK all bank card are contactless why fiddle about with a phone when it easier to just pull out your bank card the number of time i've stood behind some one trying to pay for something with their IPhone is mind numbing, you can make calls you can send texts you can receive calls and texts, if you have a higher budget then try something else if not this phone is as good or as bad as any.
Click to expand...
Click to collapse
I suspected exactly that, Carl.
I am considering this phone, too. Most of my friends have Apple and Samsung high ends (that what's absolutely dominates the market here in Singapore), some of them are already on the 3. device while I still have my 2 yo crappy beaten-up Zenfone 5 ... it's as well not without flaws but surprisingly solid. I'm 100% off the high end stuff. The time we payed high end money and really got something feelably and visably better is long over. Yep, more money buys me better, but now it's not always, and not 3 - 4 times better.
I'm currently waiting for my 6P rma to arrive, for battery shutdown issues, and a very small lift in the screen near Power/Volume buttons.
Since T-Mobile is going to start sending out an ota that will prevent Note 7s from charging, it got part of my mind wondering, are all the devices that are having battery shutdown/bootlooping problems (afaik, 6P, 5x, and some Pixels) using flash memory supplied by Samsung? How does a provider like T-Mobile target only Note 7s and not other phones that have Samsung parts? Is it purely based off of imei #s?
sgvjon said:
I'm currently waiting for my 6P rma to arrive, for battery shutdown issues, and a very small lift in the screen near Power/Volume buttons.
Since T-Mobile is going to start sending out an ota that will prevent Note 7s from charging, it got part of my mind wondering, are all the devices that are having battery shutdown/bootlooping problems (afaik, 6P, 5x, and some Pixels) using flash memory supplied by Samsung? How does a provider like T-Mobile target only Note 7s and not other phones that have Samsung parts? Is it purely based off of imei #s?
Click to expand...
Click to collapse
The battery shut down is an issue with nougat, put your tinfoil hat away
Lawlrus said:
The battery shut down is an issue with nougat, put your tinfoil hat away
Click to expand...
Click to collapse
I've actually had the battery shutdown before Nougat. So there goes your theory. I will say that with Nougat, the problem definitely got worse and more frequent.
sgvjon said:
I've actually had the battery shutdown before Nougat. So there goes your theory. I will say that with Nougat, the problem definitely got worse and more frequent.
Click to expand...
Click to collapse
If you've been having the issue before 7.0 launched, then what does the devices flash memory matter ?
Lawlrus said:
If you've been having the issue before 7.0 launched, then what does the devices flash memory matter ?
Click to expand...
Click to collapse
Just looking for any other commonalities among all affected devices (other than software). Afaik, the devices with these problems are 6Ps, 5x, and i guess now Pixels as well, from reading the reddit sub there. And i was mainly curious as to how a provider would target a certain phone model, by just using imei's or what.
sgvjon said:
Just looking for any other commonalities among all affected devices (other than software). Afaik, the devices with these problems are 6Ps, 5x, and i guess now Pixels as well, from reading the reddit sub there. And i was mainly curious as to how a provider would target a certain phone model, by just using imei's or what.
Click to expand...
Click to collapse
Apparently the G5 has the issue as well.
Yeah, more than likely by targeting the iemi. I guess I read your op as you thinking them shutting done the note 7 possibly being a reason as to why this was happening. If that's the case then you having the issue before 7.0 totally debunks that.
I read huawei made a statement that the issue is software based. But I dunno, if that's the case, I have no idea why they would have offered you an RMA.
I've never had it happen to me, then again I don't think I've ever let this device get below 45% before I ran into a wall outlet, or a car
Lawlrus said:
Apparently the G5 has the issue as well.
Yeah, more than likely by targeting the iemi. I guess I read your op as you thinking them shutting done the note 7 possibly being a reason as to why this was happening. If that's the case then you having the issue before 7.0 totally debunks that.
I read huawei made a statement that the issue is software based. But I dunno, if that's the case, I have no idea why they would have offered you an RMA.
I've never had it happen to me, then again I don't think I've ever let this device get below 45% before I ran into a wall outlet, or a car
Click to expand...
Click to collapse
Haha no problem. Oh i didn't know it was happening with the g5. Yes, mines been happening since summer but infrequently. After Nougat, it's been happening more often. My rma was through Google not Huawei. I think in my case, it was because i had a veryyyyy small lift beginning to appear on edge of screen near the power/volume buttons, and i bought from the play store.
Well i wish it to never happen to your phone. Yeah i don't know who to believe, if it's software or hardware.
sgvjon said:
I'm currently waiting for my 6P rma to arrive, for battery shutdown issues, and a very small lift in the screen near Power/Volume buttons.
Since T-Mobile is going to start sending out an ota that will prevent Note 7s from charging, it got part of my mind wondering, are all the devices that are having battery shutdown/bootlooping problems (afaik, 6P, 5x, and some Pixels) using flash memory supplied by Samsung? How does a provider like T-Mobile target only Note 7s and not other phones that have Samsung parts? Is it purely based off of imei #s?
Click to expand...
Click to collapse
Well the update that is pushed out is a Samsung update(impossible to install on a Nexus), not a Nexus 6p update, so there is zero chance these could be related. I have two 6ps and no issues so far, knock on wood, one has Samsung storage and the other is Toshiba.
@Lawlrus hey buddy!
sorry somewhat off-topic, since you said that the random reboot is a Nougat issue, i thought maybe you'll know something about home button bugs i am having on Nougat based custom Roms.
it always happens randomly, or especially after i apply a theme with substratum (rom i use have full oms support) theme apply correctly, but the home button stops responding like when i tap it to return home it just wont do.
and it works again either after a couple of hours, or when i reboot the phone it works again normally. (and the bug will return if i uninstall theme and install another theme.) is this issue related to substratum you think ?
Lawlrus said:
The battery shut down is an issue with nougat, put your tinfoil hat away
Click to expand...
Click to collapse
I had it on Marshmallow so it can't be a Nougat problem. The fact Google are RMAing them outside warranty also shows its not something they can fix with software.
leondestiny said:
@Lawlrus hey buddy!
sorry somewhat off-topic, since you said that the random reboot is a Nougat issue, i thought maybe you'll know something about home button bugs i am having on Nougat based custom Roms.
it always happens randomly, or especially after i apply a theme with substratum (rom i use have full oms support) theme apply correctly, but the home button stops responding like when i tap it to return home it just wont do.
and it works again either after a couple of hours, or when i reboot the phone it works again normally. (and the bug will return if i uninstall theme and install another theme.) is this issue related to substratum you think ?
Click to expand...
Click to collapse
I've noticed that as of late, and I don't understand what the issue is honestly. Normally after it happens, if I pull up recents and close all the windows, it works again
I'll have to start to take notice if its every ROM I'm on or if its isolated.
But yeah, its most certainly an issue with applying layers, as it just recently started happening and is the only time it happens. I do know that the substratum guys are making a ton of changes it seems as of late with the templates that themes are using, so its very possible that the next or a future sub update will fox the issues.
Lawlrus said:
I've noticed that as of late, and I don't understand what the issue is honestly. Normally after it happens, if I pull up recents and close all the windows, it works again
I'll have to start to take notice if its every ROM I'm on or if its isolated.
But yeah, its most certainly an issue with applying layers, as it just recently started happening and is the only time it happens. I do know that the substratum guys are making a ton of changes it seems as of late with the templates that themes are using, so its very possible that the next or a future sub update will fox the issues.
Click to expand...
Click to collapse
awesome, i will try the recents trick.
thanks , i am glad i am not the only one with this issue !
I'm about to RMA my 6P again because it started happening over the Christmas weekend. I won't if the Lemon Law would apply at this point, but then again, they aren't repairing it, they are just sending me a different phone to replace this one.
Hello everyone, I just got this tablet today and I'm having an issue with it. I was trying to play a music game and I noticed that when I touched both extremes of the screen the multitouch would release my fingers for some reason. I've recorded a video of it using a multitouch application just to make sure I wasn't going crazy, here it is:
Link to the Youtube video
Do you think it's defective? If anyone has this M5 10 tablet could you test it for me and see if you also have the same multitouch issue? Since I just got it today, should I return it? Or is it something that can be fixed?
Thank you.
Received mine today from Boulanger in France, i used the same software as you to test it. Everything is working fine, even with 3 or 4 fingers, using the same kind of routine you used. So i suppose that your tablet is faulty. Sorry mate.
RubyRP62 said:
Received mine today from Boulanger in France, i used the same software as you to test it. Everything is working fine, even with 3 or 4 fingers, using the same kind of routine you used. So i suppose that your tablet is faulty. Sorry mate.
Click to expand...
Click to collapse
This stuff happens Thanks for testing it out! This one is going back
I have the same problem bro! You can find my post here: https://forum.xda-developers.com/showthread.php?t=3777471
I have already open a ticket on the support
Sent from my [device_name] using XDA-Developers Legacy app
I have the same issues als well. You can see it very well with the App "Multi touch test" from Spencer Studios.
Has someone more info on this issue as the tablet is useless for me with those touch problems and I will send it back if there is no fix available in the near future.
andrgin said:
I have the same issues als well. You can see it very well with the App "Multi touch test" from Spencer Studios.
Has someone more info on this issue as the tablet is useless for me with those touch problems and I will send it back if there is no fix available in the near future.
Click to expand...
Click to collapse
Hi Andrgin, which is your problem? In my case I have the problem only if I touch the screen with two fingers. In this case seems that the tablet, after 2 sec, can't recognize anymore the touch. I'm waiting the response of the support for the ticket that I opened, hopping that they can tell me that is only a software problem and not an hardware issue, let's see...Anyway I have your idea too, I bought this tablet to play music game and is really useless with this problem.
When I touch the screen with 2 fingers at the same time and do not move them for about 1 second the tablets looses the touch of both fingers. It does not happen if I dont put both fingers down at the same time (more than about 500ms), move the fingers around while they touch the screen. Also it does not happen with 3 or more fingers.
To me it seems like the system treats the as a gesture.
I made a video about it:
youtu.be/PXXakOw_1Hk
I also thinks that the system treats this as some kind of a weird gesture. I don't think it is related to the hardware. I'll ask the Huawei support soonish because it really is annoying with cytus 2 for example or even pdfs when you want to pan soon and have 2 fingers on it and then your touch input gets removed.
This is with the 10 pro
Could it be, I hope that you are right but is really strange that only some devices have this problem, if it is a software problem, all the devices with this software need to have the issue.
I think all have this problem. So far everybody that said he does not have this bug had tested it the wrong way. You have to place both fingers at the same time and do not move them. If you move them while touching the screen it still works.
And no I dont think it is hardware related.
I also experienced this (talked about it in another thread), but it must be more complicated than that.
It's not something that systematically happens whenever i put two fingers down a the same time. It works just fine most of the time, but occasionally notes will drop, always in the same spots, in the same songs. "Pointer location" shows the touch is still being registered, if that's anything to be trusted.
I'll take the occasion to ask again since there seem to be other people who play music games in this thread: beside the touchscreen issues, has anyone noticed a slight delay on the audio feedback? I'm talking about a 100-150 ms delay from the moment i touch the screen to the moment the corresponding sound effect plays. The touch itself is registered correctly, but the audio lags behind for some reason.
Either way, i sent back the 10.8", gonna have the 8.4" here by tomorrow i hope, will update on how this one behaves.
It does not matter where you place your fingers only that it happens at the same time (less than about 500ms) and you dont move them for about 1 second.
About audio I dont know. Most time I had sound off.
It may be a general Android Oreo bug, although the article speaks about Android 8.1, not 8.0:
https://www.xda-developers.com/android-8-1-oreo-multi-touch-bug-fixed-june-update/
Maybe Huawei used parts of Android 8.1 for the M5.
A fix from Google is planned for the June security update.
Just tested the 8.4", after installing the new update. Interestingly enough, it didn't seem to drop any inputs.
The sound delay, however, is exactly the same, and it baffles me no one else seems to notice it.
On top of that, i think i got a defective unit, as the charging speed starts off at 3300-3400 mAh, then drops to 500-600, never to rise again. So much for quickcharge.
Battery also seems to run considerably hotter for no apparent reason: 37 degrees Celsius while charging at that pitiful speed, no other apps running.
For reference, the 10.8" never exceeded 32 degrees, and that's while charging at max speed, with apps running at the same time.
Overall, this tablet has been nothing but a huge disappointment, i'll just refund it and wait for something else to come out at this point.
Edit: it charges normally when the screen is turned off. When the screen is on, the charger seems to provide enough current to offset whatever i'm consuming, plus those 500-600 extra mAh, so no matter what i'm doing that speed doesn't change. The 10.8" was charging normally, full speed minus whatever power i was drawing, so i'm still pretty sure something's not right.
@chris_g I really hope it could be the problem but wait two more months it's really frustrating! For now I haven't received yet one answer from the support...
Not really good news from Italian support, them tell me that no reports was received about our problem, so them suggested me to try to reset the device to the default to see if is a software problem. Did you guys found something else? I'm really thinking to request the replace of the device.
Just to be sure, could someone give me the mail of the international/English support? I want to try to write a mail also to them.
Cheers
I got the M5 Pro from amazon.it and the warranty check showed that I get warranty in most European countries. I opened a ticked with the Austrian support providing all the info they needed. They said they dont know of the problem so far and will forward it. This was over 1 week ago and I did not receive any response yet.
Replacing the tablet will not solve anything because every M5 (at least the 10" versions) have this bug.
And no it is not an Oreo bug because my Mate 10 (also EMUI 8.0) works fine. I guess it is some code Huawei added to support the pen.
Firmware Finder already shows a EMUI 8.1, but it is not approved for installation yet. I guess we will get Oreo 8.1 in a few weeks/months and this bug will hopefully be fixed in the new version.
andrgin said:
Firmware Finder already shows a EMUI 8.1, but it is not approved for installation yet. I guess we will get Oreo 8.1 in a few weeks/months and this bug will hopefully be fixed in the new version.
Click to expand...
Click to collapse
Don't be so optimistic on that one, as Google themselves introduced an all new multi-touch bug in the 8.1 base. Thus one bug will maybe just be replaced by another one, as Google already stated that they'll have the bug fixed in the June update soonest. Let's hope Huawei uses the patched June base to upgrade our tablet to 8.1.
Sent from my HTC U11 using XDA Labs
Huawei already ships Android 8.1 with the P20 so I guess we are getting the same code. I never heard about multi touch problems there so I guess Huawei has already replaced that faulty Google code. With all the people complaining about late Android updates for existing devices, but there is a reason most vendors wait until they release a new Android version for the masses. Google phones are simply beta test devices.
I have the 8.4" wifi model. It suffers the multi-touch problem but not the sound delay problem. I tried the drum pad app, sounds play instantly as soon as I touch them.
I have a bunch of log-cats, but I'm not exactly sure what they mean.
I'm flashed the Chinese dev rom (marshmallow) and run the calibration. The messages I see: https://pastebin.com/i1ZiMQ15
And from when I had AOSPEx 8.1, running logcat during attempts to add a fingerprint: https://pastebin.com/VunWrFhA
I downloaded the source I could find for this phone and ran a file scan from inside notepad ++ to try and find the references to these log entries. Unfortunately they seem to be something automatically generated higher up in the code due to class inheritance/object delegation. I'm not very good at following that sort of thing. I decompiled the QFPservice apk and found code making references to a bunch of the status and enroll results, but again, at this point they're just integers, as I have no idea where the entity defining them is located within source, and Google's source documentation didn't really help.
Does anyone think this is a hardware failure? I just want to know before I go through the trouble of getting the parts to attempt to replace the sensor, and the more definitive an answer I can get the better.
Thank you for any assistance.
Just reflash a ROM, EUI from start and Just try to update the firmware -> https://androidfilehost.com/?fid=818070582850487752
And make a test again on EUI rom.
Is there a guide on the specifics of this? I may just be paranoid as I type this, but I just have a message on TWRP saying "Phone will reboot in 5 seconds" after "Firmware updated". The console on my PC shows only 48% on the sideload though....
Edit: I forced a reboot since things seemed done. No adverse results, but the FP scanner still doesn't work.
Edit2: Tap for photo .... "works", but its random. I suspect the sensor is if not entirely dead, entirely faulty. I bought an FP sensor anyhow, so I guess it's kind of moot to waste time on this now.
I don't believe that you can fix the dead fingerprint sensor with a firmware upgrade. Mine works for only one day when I bought the Le Max2 X820 and then it was death. 100 % shure that this is a hardware issue and can't be fixed without change the fingerprint sensor.
Beackman said:
Just reflash a ROM, EUI from start and Just try to update the firmware -> https://androidfilehost.com/?fid=818070582850487752
And make a test again on EUI rom.
Click to expand...
Click to collapse
shredman said:
I don't believe that you can fix the dead fingerprint sensor with a firmware upgrade. Mine works for only one day when I bought the Le Max2 X820 and then it was death. 100 % shure that this is a hardware issue and can't be fixed without change the fingerprint sensor.
Click to expand...
Click to collapse
It may be coincidental, but I'm virtually certain this was due to a hardware problem I directly caused. It was working quite well, and then I used a qi-receiver tag that I had just ordered from China (one of no particular quality to recommend it) and the sensor failed immediately thereafter. So, in my particular case I think I did it to myself.
In my isolated result however, I am forced to concur. A full restoration from Qualcomm's QFIL flash failed to restore function to the sensor, and at best it shows phantom presses, though these seem to have ceased entirely in favour of total death. I've had the sensor "die" on some ROMs before, but I'm pretty convinced at this point, having loaded every offering I could find, that I have killed it in the purest sense.
However, I was just wondering if anyone knew what those reported values actually meant in the logcats? I guess it's moot now, as I've ordered a new FP scanner from Aliexpress, but we'll see. My hope is that switching out the hardware goes smoothly, particularly considering there only seem to be QFIL available for X820, not for the X829.
TheLastCanadian said:
It may be coincidental, but I'm virtually certain this was due to a hardware problem I directly caused. It was working quite well, and then I used a qi-receiver tag that I had just ordered from China (one of no particular quality to recommend it) and the sensor failed immediately thereafter. So, in my particular case I think I did it to myself.
In my isolated result however, I am forced to concur. A full restoration from Qualcomm's QFIL flash failed to restore function to the sensor, and at best it shows phantom presses, though these seem to have ceased entirely in favour of total death. I've had the sensor "die" on some ROMs before, but I'm pretty convinced at this point, having loaded every offering I could find, that I have killed it in the purest sense.
However, I was just wondering if anyone knew what those reported values actually meant in the logcats? I guess it's moot now, as I've ordered a new FP scanner from Aliexpress, but we'll see. My hope is that switching out the hardware goes smoothly, particularly considering there only seem to be QFIL available for X820, not for the X829.
Click to expand...
Click to collapse
Now you have ordered a new FP sensor, i thinck is better wait and install the new one, before install update the firmware with the file i have posted and replace the FP sensor.
The errors on log maybe is a fault on try to initiate the FP sensor.
Please delete this thread and please ban me and people who are calling me a troll, this is for you, (check the date):
https://forum.xda-developers.com/showpost.php?p=77495198&postcount=17
Hi there, there might be some issues with Pocophone in general and your device in particular but all this hate is absolutely uncalled for. If you are not happy with it - return it or sell it. It is just a $300 phone, what did you expect?
Neznam123 said:
Hi there, there might be some issues with Pocophone in general and your device in particular but all this hate is absolutely uncalled for. If you are not happy with it - return it or sell it. It is just a $300 phone, what did you expect?
Click to expand...
Click to collapse
This device is made for gaming, but you can't play games and when you complain against it, "it's just a $300 phone, what do you expect?" dude, why it has a SD845 if touch issue is a norm? why didn't they put SD430 in it? a lot of people have this issue.
As the last user replies, there's no reason to hate it for being a little worse than 500$ devices. For the money you're spending its definitely the best device you could buy right now.
1. Sound issues - Software fix will work.
2. DRM issues - Another software fix.
3. Multi touch issue - Check the thread someone posted a solution, though most of us never faced it.
4. Lag/Frame drop issues - Never faced in the games I've played but 845 is more than capable of not having frame drops, so its just software optimization again.
5. Battery and Heating - I never saw 50 C on my poco and my other devices remain there even after moderate use so its better. (Ambient temperature is high in my area) and the battery lasts forever. My standby usage on 4g mobile data was 0.3% yesterday (3.5 hr in 1% drop) and SOT is consistently using just 10-15% per hour which roughly translates to 7-8 hour of SOT and at least 6 hours for a heavy user, tell me one 845 device capable of this?
And Jai Mani from poco does see our tweets and repiles too, they're working on DRM fix currently, notifications on notch area are also being looked into and they resolved the bootloader unlock issue so fast, I'm hoping they'll fix the other minor things too.
narora9999 said:
As the last user replies, there's no reason to hate it for being a little worse than 500$ devices. For the money you're spending its definitely the best device you could buy right now.
1. Sound issues - Software fix will work.
2. DRM issues - Another software fix.'
...
Click to expand...
Click to collapse
I don't know what world you live in, but for solving DRM issues, OTA won't work in this one
Multitouch issue is a major issue and the device is useless unless this issue is solved. A lot of users are facing this issue and I am not alone apart from PUBG keyboard is very slow and lags, touch has a delay, inaccuracy in selecting texts. With these kinds of problem SD845 is useless because input devices are limiting the hardware capability.
If you have ever taken Computer Science 101, a input device should be as responsive and accurate as possible else using a fast processor on a slow input device is as stupid as it gets.
regarding the reply, I have made multiple queries on the forum and filed 2 bug reports, and even quoted few admins and mods, they aren't even replying.
And if they still think that it's normal then they should take this device and refund me my money, which they are not doing. I had to convince them for about the issue for at least 2 hours and best they did was replacing the device but I don't want this **** and will never buy phones from Xiaomi ever again unless the devices are thoroughly tested and bugs are fixed.
shailendra1993 said:
I don't know what world you live in, but for solving DRM issues, OTA won't work in this one
Multitouch issue is a major issue and the device is useless unless this issue is solved. A lot of users are facing this issue and I am not alone apart from PUBG keyboard is very slow and lags, touch has a delay, inaccuracy in selecting texts. With these kinds of problem SD845 is useless because input devices are limiting the hardware capability.
If you have ever taken Computer Science 101, a input device should be as responsive and accurate as possible else using a fast processor on a slow input device is as stupid as it gets.
regarding the reply, I have made multiple queries on the forum and filed 2 bug reports, and even quoted few admins and mods, they aren't even replying.
And if they still think that it's normal then they should take this device and refund me my money, which they are not doing. I had to convince them for about the issue for at least 2 hours and best they did was replacing the device but I don't want this **** and will never buy phones from Xiaomi ever again unless the devices are thoroughly tested and bugs are fixed.
Click to expand...
Click to collapse
Please verify your information about DRM, oneplus 5 and 5T had the same issue of netflix hd and they resolved it via update(Yeah the update had to be done at service center only). I've taken every computer science involved in engineering (a CS engineer myself) and I understand your concern but somebody did post a fix for that. I've faced the touch issue in my other phone while charging which was due to a buggy kernel so its definitely debatable that it could be a software issue.
I had a speaker distortion issue, my replacement was arranged instantly over phone (Flipkart).
source: https://www.xda-developers.com/oneplus-5t-netflix-amazon-prime-video-hd/
1. Sound issues - We will solve it soon
I've no idea what's that. Can you explain?
2. DRM issues - Just don't watch netflix or prime in HD because we have loads of money to have HD plan but can't watch it.
The phone doesn't support V1 out of the box, most of the Xiaomi phones doesn't support. Heck even the One Plus 5/5t also doesn't support. You get what you pay. To make it clear, I don't believe it can be fixed by a software since it requires secured machine to update the phone which only OEM's use. Only way Xiaomi can fix it by asking customers to visit Service center and updating the V1 from their machine. Otherwise, just forget about it.
3. Multi touch issue - what do you expect from a $300 phone?
No such issues here.
4. Lag/Frame drop issues - What do you expect from a budget phone
No frame drops, lag issues. Source? I play PUBG 4-5hrs per day and never faced that issue. PS: It's not a budget phone.
5. Battery and Heating - Every phone has it, what is the problem?
So what if the phone gets heated, it'll heat when you do intensive tasks, I guess you've never used a flagship phone in your life? All top high end CPU's like SD835/845 etc generate heat. Xiaomi did great job in keeping it cool, my phone never crossed 50+ during games.
May be you should stick to Samsung J7 phones. That's what you're meant to use.
Use what you like and stop cribbing about it. You don't like Poco F1, use iPhone X or any other high end Android phone. You pay $300 and you want a phone to behave like $1000? No phone is perfect including the iPhone X/Samsung Note 9.
I've been using Poco F1 from last 1 week and so far I'm in love with this phone.
Wow... so much hate, and most of us had no issues with phone what so ever. What gives you the right to be hater and try to generalize some problems that 95% people never experience?
shailendra1993 said:
Is poco F1 nothing but a brick?
It has top specs like SD845 and UFS 2.1 and all but we have a few issue and what other people are suggesting?
1. Sound issues - We will solve it soon
2. DRM issues - Just don't watch netflix or prime in HD because we have loads of money to have HD plan but can't watch it.
3. Multi touch issue - what do you expect from a $300 phone?
4. Lag/Frame drop issues - What do you expect from a budget phone
5. Battery and Heating - Every phone has it, what is the problem?
etc
Tell me, did we just buy this phone for the sake of having a SD845 and liquid cooling system and not use it properly?
Is this device only capable of calculating 2+2 and no heavy work?
This device's name should be named Poco Compromise 1 instead...
BELIEVE ME I HAVE USED A LOT OF XIAOMI PHONES, I KNOW HOW THEY WORK:
I have used Redmi 2/Prime,3S/Prime,Note 3/4/5, Mi4i - Do you know Mi4i? This **** was launched as a Flagship in India but they ****ed us up.During the first month, they provided support although few people won't call it a support because for the heating issue they released a fix, that arsehead Barra called it their pathbreaking thermal config, when the developers looked at the config they found out that those idiots permanently turned off 2 cores of the SD615. Later when the hype died, they slept as they do everytime and after just 1 year the SOT of that phone dropped to 1 hour even when the device was used minimally. Because of their pathbreaking config, SD615 earned a bad name for being a non-battery friendly processor, although Moto G Turbo had the same processor and was one of the best device during that time.
I URGE YOU ALL (THOSE WHO HAVE TOUCH ISSUES) TO COMPLAIN WHEREVER YOU CAN SO THAT XIAOMI WILL AT LAST EITHER FIX THIS ISSUE OR TELL US IF IT IS A HARDWARE ISSUE BEFORE IT'S TOO LATE AND THE HYPE DIES. JUST WRITE IT ANYWHERE YOU WANT, AFTER A MONTH OR WHENEVER POCO ANNOUNCES A NEW DEVICE ALL THE HYPE WILL SUDDENLY DIE AND NO ONE WILL CARE ABOUT THE ISSUES, SO DO SOMETHING WHILE THE TIME IS RIGHT!!!!
Click to expand...
Click to collapse
Dude. Just come on already. You keep making it sound worse each time you post the same thing.
Sound issue : A software bug nothing new. It'll get fixed if not improved in the later updates
DRM - Frankly if you had "loads" of money, then why didn't you put your trust in samsung or Apple. Leave Xiaomi to budgeteers.
Multi touch - Every one knows they made the biggest compromise in the display/touch panel. But most touch issues are due to gestures. Can be optimised.
Lag/Frame drops - unless you are playing emulator games from PS2, this is impossible. I play PUBG for 2-3 hrs every day.
Battery/heating - When you turn the best feature of a device into its worst, then it makes people think you ahve some kinda agenda here. Avg SOT is 9 hrs and max temp during intense gaming 40+ which comes down in 2 secs.
Only capable of 2+2, really? I had a legitimate argument going on with touch/display compromises but now.
I ordered mine earlier today. God help me lol
narora9999 said:
Please verify your information about DRM, oneplus 5 and 5T had the same issue of netflix hd and they resolved it via update(Yeah the update had to be done at service center only). I've taken every computer science involved in engineering (a CS engineer myself) and I understand your concern but somebody did post a fix for that. I've faced the touch issue in my other phone while charging which was due to a buggy kernel so its definitely debatable that it could be a software issue.
I had a speaker distortion issue, my replacement was arranged instantly over phone (Flipkart).
source: https://www.xda-developers.com/oneplus-5t-netflix-amazon-prime-video-hd/
Click to expand...
Click to collapse
The only phone I have ever heard that the DRM was changed is OP5 others had to stick with whatever version they got. Apart from that the certificate change requires physical connection with an authenticated computer i.e. the company's computer that means about 7-10 days for those who live outside cities like Mumbai and Delhi and since very few (or none of) Xiaomi phones in India has L1 Widevine support all the legal hassles and paperwork will be so tedious that they will either charge you for that or won't do it.
Multitouch issue is different from what you are referring, check the following bug report and video:
Bug report:http://en.miui.com/forum.php?mod=viewthread&tid=3746297
Video:https://www.youtube.com/watch?v=e5K2N6McC_s
P.S. I also have a CS degree and multiple certifications on Programming and Ethical Hacking from Lynda,Pluralsight,Udemy,etc.
Daruwalla said:
1. Sound issues - We will solve it soon
I've no idea what's that. Can you explain?...
Click to expand...
Click to collapse
Dude, I am not saying those things, that is actually what people are replying when someone says that they are having a problem with the phone
BELIEVE ME I HAVE USED A LOT OF XIAOMI PHONES, I KNOW HOW THEY WORK: So assuming you knew they treat you the wrong way all the time, why spend money on them again, and DRM issue for Xiaomi is well known, if you are familiar with their phones, why would you be shocked to know it now?
Maybe you are just angry!! Channelize it on the Xiaomi and Flipkart social feeds and your problem has higher chance of being solved.
Seems like OP got a bad unit.Sound issue and multitouch issue will be fixed in next update.Except Widevine L1 support, all thing said by you is wrong. No issue here, bought in first sale.
watsinaname said:
BELIEVE ME I HAVE USED A LOT OF XIAOMI PHONES, I KNOW HOW THEY WORK: So assuming you knew they treat you the wrong way all the time, why spend money on them again, and DRM issue for Xiaomi is well known, if you are familiar with their phones, why would you be shocked to know it now?
Maybe you are just angry!! Channelize it on the Xiaomi and Flipkart social feeds and your problem has higher chance of being solved.
Click to expand...
Click to collapse
I have posted it there and even a bug report please see before posting. The problem is I am getting no reply and Flipkart is delaying the return request.
shailendra1993 said:
The only phone I have ever heard that the DRM was changed is OP5 others had to stick with whatever version they got. Apart from that the certificate change requires physical connection with an authenticated computer i.e. the company's computer that means about 7-10 days for those who live outside cities like Mumbai and Delhi and since very few (or none of) Xiaomi phones in India has L1 Widevine support all the legal hassles and paperwork will be so tedious that they will either charge you for that or won't do it.
Multitouch issue is different from what you are referring, check the following bug report and video:
Bug report:http://en.miui.com/forum.php?mod=viewthread&tid=3746297
Video:https://www.youtube.com/watch?v=e5K2N6McC_s
P.S. I also have a CS degree and multiple certifications on Programming and Ethical Hacking from Lynda,Pluralsight,Udemy,etc.
Click to expand...
Click to collapse
Yea I only said its possible and as no Mi devices supported it, even some huawei and zte didn't support it but only poco f1 model is being bashed for it because you all try to find cons in a product that offers at least more than its cost.
Multitouch is due to gestures implementation and it is a software issue. Sound is always fixable even if they don't(root and fix yourself). You may have gotten a bad unit but we didn't face any issues that are worth so much hate.
Thread closed at OP request