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...
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.
I still face touch issue after latest update.Which rom and kernel will help me to solve this problem
me too bro, its gone real bad now, due to ghost touches the entire experience is so sluggish, even my dad's redmi 4 has better touch than my poco
nISTHUR said:
me too bro, its gone real bad now, due to ghost touches the entire experience is so sluggish, even my dad's redmi 4 has better touch than my poco
Click to expand...
Click to collapse
I am pretty much sure it is a hardware problem.Are you considering replacing it?
I've already got screen replaced once as my replacement period according to Xiaomi viz. 3mths was over so i doubt there is any solution
use Pixel experience rom...i switched to pixel rom after 10.3.4.0
try malakas display oc kernel...
I don't think you can fix it. it's a hardware issue.
I could tell you my version of the digitiser which is the one without problems but ever since i updated to 10.3.4 Xiaomi removed that Info from tapping 5 times on the kennel info and then lcm info.
Luckily i got the new panel without touch issues.
I'll try and find another way to check my digitiser model again but if my memory doesn't deceive me i think the tiamat is the one that has problems.
Edit: mine is ebbg digitiser not tiamat. Maybe you can improve with a different kennel.
AliNT77 said:
try malakas display oc kernel...
Click to expand...
Click to collapse
Display OC is for display and not for touchscreen. It increases the refresh rate of the Display and it has nothing to do with touch responsiveness.
thunderc8 said:
I don't think you can fix it. it's a hardware issue.
I could tell you my version of the digitiser which is the one without problems but ever since i updated to 10.3.4 Xiaomi removed that Info from tapping 5 times on the kennel info and then lcm info.
Luckily i got the new panel without touch issues.
I'll try and find another way to check my digitiser model again but if my memory doesn't deceive me i think the tiamat is the one that has problems.
Edit: mine is ebbg digitiser not tiamat. Maybe you can improve with a different kennel.
Click to expand...
Click to collapse
how did you checked the digitiser info?
After disable pocket/bag mode in settings, no more touch issues in my pocophone. I use miui.eu beta + franco kernel
Try the last beta version
Dynamo2020 said:
I still face touch issue after latest update.Which rom and kernel will help me to solve this problem
Click to expand...
Click to collapse
.
.
Could someone please explain these touch issues to me?
Describe them so I can also look for them as mine is still under replacement period.
Thanks
Xebeck said:
.
.
Could someone please explain these touch issues to me?
Describe them so I can also look for them as mine is still under replacement period.
Thanks
Click to expand...
Click to collapse
In my case 2 days ago I was in a concert and I wanted to take some shoots. Opened the camera app, and touch was not responding at all.
I turn off the screen, then on, randomly started to press any place of the screen until I was able to get away from the app. (I restarted the phone few times and same thing happen)
Hi guys!
I have this Redmi Note 4 with broken screen, so I decided to buy a replecement screen/touch to fix it.
The new touch works fine, but the double tap to wake only works on TWRP: It doesn't work anymore on ROMs (I've tried official and unofficial LineageOS 16). This feature worked with the old broken screen on both ROMs.
I also changed ROM and wiped everything, but it still doesn't work.
Is there anything related to new screen?
Thanks in advance for the help!
I got the same experience with my Redmi Note 4 with a replaced screen from a few weeks back.
Kelvino9 said:
I got the same experience with my Redmi Note 4 with a replaced screen from a few weeks back.
Click to expand...
Click to collapse
Is your working only on twrp?
huh ?
is it working now