Hi, I know this problem has been asked many times on this forum but I haven't found a solution yet. I'm from Spain and I have this phone and well, I have the double typing letter issue and I don't know how to fix it, I recently have read that the last patch fixes that, is it true?
The link:
http://forum.xda-developers.com/p8lite/general/official-upgrade-ale-l21c432b200-t3358773
I don't know if it works or not but I want to know if there's a solution for the double letter problem, it's very annoying.
Greetings.
PS: I think I have the B180 version.
http://forum.xda-developers.com/p8lite/general/double-tap-problem-keyboards-firmware-t3343287
Yup, the B190 fixes the problem and so should B200.
As for the Android 6.0 - it is not yet fixed.
Well my version is the B181 and I dont have any OTA updates... Im single sim, what can I do? Apparently, there is no latest versions for my phone, is it?
khrystoff said:
Hi, I know this problem has been asked many times on this forum but I haven't found a solution yet. I'm from Spain and I have this phone and well, I have the double typing letter issue and I don't know how to fix it, I recently have read that the last patch fixes that, is it true?
The link:
http://forum.xda-developers.com/p8lite/general/official-upgrade-ale-l21c432b200-t3358773
I don't know if it works or not but I want to know if there's a solution for the double letter problem, it's very annoying.
Greetings.
PS: I think I have the B180 version.
Click to expand...
Click to collapse
I am using BB Priv keyboard and no problem at all.
Rexton270 said:
I am using BB Priv keyboard and no problem at all.
Click to expand...
Click to collapse
What firmware are you using and which P8 Lite model do you have? Maybe you already have the firmware which is NOT affected.
wolfensg said:
What firmware are you using and which P8 Lite model do you have? Maybe you already have the firmware which is NOT affected.
Click to expand...
Click to collapse
Running official MM 6.0 , and have ALE-L21 model (single SIM).
Sent from my ALE-L21 using XDA-Developers mobile app
---------- Post added at 10:51 AM ---------- Previous post was at 10:49 AM ----------
Rexton270 said:
Running official MM 6.0 , and have ALE-L21 model (single SIM).
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
C432B551 is the firmware version
Sent from my ALE-L21 using XDA-Developers mobile app
It looks like BlackBerry keyboard fixes the problem!
I've just installed it and it works beautifully!
I'm running B311 (6.0), and the problem is present with other keyboards, like Swift-Key.
Is it true? Is this problem solved?
Sent from my hi6210sft using Tapatalk
---------- Post added at 09:01 PM ---------- Previous post was at 08:21 PM ----------
I can not believe thah huawei hasn't solved this problem yet..
@huaweil21
This is resolved in firmware B190 and B200.
It is not fixed in Android 6.0 base B5XX versions (at the moment, I hope the fix will be a matter of time).
However single-sim variant seems to be fixed in B551 version (see post from @Rexton270 )
@empy16
Installing BlackBerry keyboard is not a fix - more like a workaround but for me it did not work.
@Rexton270
That's kind of strange... it is NOT fixed in dual-sim base B550. So - if this is working in B551 (which AFAIK was released only few days later than B550) it means that the fix is more or less ready... but they did not include this in B550.... and thus the owners of dual-sim variant need to wait... (yeah... I know... I could revert to single-sim firmware and so... but I actively use two SIM's at once Thanks for the info about the single-sim B551 variant!
I have B551 and it has the same problem
I can't believe they haven't fixed that already. Such a big omission for huawei..
wolfensg said:
@huaweil21
@empy16
Installing BlackBerry keyboard is not a fix - more like a workaround but for me it did not work.
Click to expand...
Click to collapse
Well, changing the whole bloody firmware is not what you call a quick-fix either, is it?
I, myself, tried craploads of solutions to this problem an the BB keyboard seems to be the best one.
You either install the old firmware or you use the BlackBerry Keyboard.
Sorry it didn't work for you, but it looks like it works for a couple of people. Worth mentioning as a probable fix.
The keyboard itself is good as well, has multiple combo language support and doesn't take a lot of space on the screen...
empy16 said:
Well, changing the whole bloody firmware is not what you call a quick-fix either, is it?
I, myself, tried craploads of solutions to this problem an the BB keyboard seems to be the best one.
You either install the old firmware or you use the BlackBerry Keyboard.
Sorry it didn't work for you, but it looks like it works for a couple of people. Worth mentioning as a probable fix.
The keyboard itself is good as well, has multiple combo language support and doesn't take a lot of space on the screen...
Click to expand...
Click to collapse
I did not say it is a quick-fix* to change the whole firmware but yes - it is a "bloody firmware issue"
Fortunately this has been fixed now for both LP based (B190 and up) and MM based (B560 and up) firmwares.
Enjoy the BlackBerry keyboard but keep in mind that not everyone would like to change the keyboard "just because some bug occurs less often". In my case however the BlackBerry keyboard was not an acceptable solution (and honestly - did not work as a workaround either).
*) Oh come on mate! We're on EMUI - you didn't expect a quick-fix for EMUI based phone right? Cheer-up!
Hello, i use google keyboard and i have double letter problem, but when i set a lower vibration in keyboard settings the double letter problem has gone.
wolfensg said:
I did not say it is a quick-fix* to change the whole firmware but yes - it is a "bloody firmware issue"
Fortunately this has been fixed now for both LP based (B190 and up) and MM based (B560 and up) firmwares.
Enjoy the BlackBerry keyboard but keep in mind that not everyone would like to change the keyboard "just because some bug occurs less often". In my case however the BlackBerry keyboard was not an acceptable solution (and honestly - did not work as a workaround either).
*) Oh come on mate! We're on EMUI - you didn't expect a quick-fix for EMUI based phone right? Cheer-up!
Click to expand...
Click to collapse
Yeah, I guess you're right.
Also, BlackBerry keyboard stopped working for some reason. I think I changed a setting or something...
Either way, on to the B560 then!
Related
http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDMzMTU=
Beta1?? Again??
Sent from my IDEOS X5
demolition23 said:
Beta1?? Again??
Sent from my IDEOS X5
Click to expand...
Click to collapse
fixed (?) beta 1
Downloading
darkweather said:
fixed (?) beta 1
Click to expand...
Click to collapse
They said that the new beta would be available this week,i think that this one will be very close to the final!!!!!
No changelog or anything, but now there is only 1 step in the update
I have installed. No large changes. Why for other versions U8800 be immediately final version ROM? Why not for first model x5? Where is the problem???!!! If Huawei developers take be CM7 or Oxygen ROM and a little fine-tuned, so have per hour ready official firmware. I do not it.
If someone needs a mirror, i've upload it into rapidshare:
https://rapidshare.com/files/297936...01_Beta1.0__Overseas_Normal__Gingerbread_.zip
zemaniel said:
I have installed. No large changes. Why for other versions U8800 be immediately final version ROM? Why not for first model x5? Where is the problem???!!! If Huawei developers take be CM7 or Oxygen ROM and a little fine-tuned, so have per hour ready official firmware. I do not it.
Click to expand...
Click to collapse
please tell us the differences between this one and previous one.
No differences found for now... simply one step instead of 2...
nrdl said:
No differences found for now... simply one step instead of 2...
Click to expand...
Click to collapse
what about volume key wake up function?
Different file size - beta1 345.951kB, beta1 second 345.956kB Still not function haptic feedback, freeze touch screen when mobo player end play file - i lock-unlock screen, then again work. Yet no problem with detection SD card, work properly (tested 3 hours,reboot, power off, remove battery, still OK) Still verry sensitive touch display. That's all for now
P.S. My IMEI is still zero... :-( But all radio OK, GSM,WiFi,BT....
Volume up wake up does not work for me.
no differance at all, but one thing is working.... external card issue, now there is no cd drive option.... working fine...... but still the main problem is there.... MY IMEI=0
IS THERE NOT A SINGLE GOOD HEARTED PERSON WHO CAN HELP THOSE WHO HAVE UNINTENTIONALLY LOST THEIR IMEI... i request developers to help us as there is still a large number of people who own a legal x5 u8800, so the imei problem should not be an issue for them..... PLEASE HELP AND SAVE OUR PRECIOUS MONEY
chochweet said:
no differance at all, but one thing is working.... external card issue, now there is no cd drive option.... working fine...... but still the main problem is there.... MY IMEI=0
IS THERE NOT A SINGLE GOOD HEARTED PERSON WHO CAN HELP THOSE WHO HAVE UNINTENTIONALLY LOST THEIR IMEI... i request developers to help us as there is still a large number of people who own a legal x5 u8800, so the imei problem should not be an issue for them..... PLEASE HELP AND SAVE OUR PRECIOUS MONEY
Click to expand...
Click to collapse
There is no way other than changing complete mother board. I tried everything possible before i get mother board replaced under warranty. Better u go to authorised service provider.....
any way to upgrade directly from beta 1 to this version?
This may work?
android.modaco.com/topic/337340-update-zte-imei-flash-tool-for-imei-all-0-machine
But I do not to try...
---------- Post added at 09:18 PM ---------- Previous post was at 09:13 PM ----------
Power off phone. Insert SD card with dload\update.app Boot vol+/vol-/connect usb cable (do not press power buton) He begin flash ROM. This is my way.
Imei = 0
still have sd card insues
Your IMEI turned into 0 by updating to this beta 2?
yes, besides that, i dont notice any change
Just finished flashing, phone rebooted 4 or 5 times before I saw the lovely green android... Checked IMEI ok, wi-fi working, sd-card working, haptic feedback working on soft-keys and all keyboards except swype (could be some settings...) More testing tomorrow
Hi
Here are some version of latest SGP511 Nordic Combined firmware.
Nandroid backup are highly recommended.
Stock ftf install via flashtool:
https://mega.co.nz/#!kcxxjaLA!itErjRi2fYPPswal-c7XasF_lAvPKyY4GwEzY3xgHZ0
http://www.mediafire.com/download/x....A.0.314_Customized_NCB_(Nordic_Combined).ftf
Prerooted version flash via custom recovery. This install also SuperSu and DualRecovery:
https://mega.co.nz/#!hdZV1CBY!MJIOjMoN8uSposyaV6FyQOWeuNvQ2tSsHjw4F0rBakY
http://www.mediafire.com/view/bosul56grj4dbt8
Deodex patch flash via custom recovery and wipe dalvik cache:
https://mega.co.nz/#!JYxzFD4T!mBzCWiF9fHOFQYQ-9fuoiq2DMxYxVk9LYJkXKQymQEo
http://www.mediafire.com/view/6ty4vyx43aybovx
Credits: @Androxyde, @Chainfire, @Nut, @LaguCool , @zxz0O0 and @RyokoN
Thanks, I managed to update my SGP511 with this image using Flashtool (without wiping data, all setting were kept).
Rooting with Easyroot V11 took two tries, but works fine. Also reinstalled dual recovery again without problems.
MrMagic said:
Thanks, I managed to update my SGP511 with this image using Flashtool (without wiping data, all setting were kept).
Rooting with Easyroot V11 took two tries, but works fine. Also reinstalled dual recovery again without problems.
Click to expand...
Click to collapse
Thanks your feedback. You are right. No need to wipe anything.
kulvertti said:
Thanks your feedback. You are right. No need to wipe anything.
Click to expand...
Click to collapse
Ohh awesome to know
Had enough of waiting on my Swedish model that I just needed to update it
Just updated my tablet, and feels good to finaly be able to use a stylus on it. It's not perfect but alot better then before then i had to push really hard to get any sort of response with a stylus. The small issues i have using stylus now could be due to the stylus, i many times leaning it a bit to left or right and it dont always do as i wanted, but could be that im using a thinner stylus then i used to have so not enough of it are in contact with the tablet.
Aotw said:
Just updated my tablet, and feels good to finaly be able to use a stylus on it. It's not perfect but alot better then before then i had to push really hard to get any sort of response with a stylus. The small issues i have using stylus now could be due to the stylus, i many times leaning it a bit to left or right and it dont always do as i wanted, but could be that im using a thinner stylus then i used to have so not enough of it are in contact with the tablet.
Click to expand...
Click to collapse
Thanks for your feedback. I agree you that this ain't the most stylus friendly device but with right stylus still usable.
kulvertti said:
Thanks for your feedback. I agree you that this ain't the most stylus friendly device but with right stylus still usable.
Click to expand...
Click to collapse
After this update it works almost as is thould for me, but as i mentiond in my previous post i could be due to the thinner top of the stylus and how i hold it. Will try use some others to check.
wrong?
sryyy
flashed my 512 with flashtool, no problems. Thanks!
Edit: rooted with easy root v12.
Seemed like easyroot kind of hung after it said 'cleaning up' but a quick download of terminal emulator showed I could su/root no problem. (I think)
ChodTheWacko said:
flashed my 512 with flashtool, no problems. Thanks!
Edit: rooted with easy root v12.
Seemed like easyroot kind of hung after it said 'cleaning up' but a quick download of terminal emulator showed I could su/root no problem. (I think)
Click to expand...
Click to collapse
Just run it again and you be fine.
Can someone please mirror this file somewhere different from mega? The Italian gov blocked it and I'm unable to access it (nor I can change my DNS because of my ISP restrictions)
this firmware works great with my z2.
Thank you so much. this firmware works great with my z2.
Wifi speed now changes from 70 MBps to 125 MBps.
Only onthing is need to re-install some apps like Viber, Swype ...
GabMus said:
Can someone please mirror this file somewhere different from mega? The Italian gov blocked it and I'm unable to access it (nor I can change my DNS because of my ISP restrictions)
Click to expand...
Click to collapse
I make mirror for you. Uploading now and should be ready about hour and half.
Here are mirrors for you:
https://www.mediafire.com/?x4c5o2d099d1604
https://dl.dropboxusercontent.com/u/25635282/SGP511_17.1.2.A.0.314_Customized%20NCB%20(Nordic%20Combined).ftf
https://drive.google.com/file/d/0B4xHeTeWdVxGUmE2SGxKMmV4bVE/edit?usp=sharing
hungnm02 said:
Thank you so much. this firmware works great with my z2.
Wifi speed now changes from 70 MBps to 125 MBps.
Only onthing is need to re-install some apps like Viber, Swype ...
Click to expand...
Click to collapse
Thank you for feedback.
Thank you kindly
GabMus said:
Thank you kindly
Click to expand...
Click to collapse
You are welcome.
Hey Guys,
Did you see any improvement in touch bug with this version?
I'm on 17.1.1.A.0.402 and SGP511, I've some problem with scroll specially when the feature "double tap to wake up" is enabled.
Cheers,
chentz78 said:
Hey Guys,
Did you see any improvement in touch bug with this version?
I'm on 17.1.1.A.0.402 and SGP511, I've some problem with scroll specially when the feature "double tap to wake up" is enabled.
Cheers,
Click to expand...
Click to collapse
Hi bro
I haven't noticed any touch bug with this device and firmware. Even stylus is usable. Try it and report back.
kulvertti said:
Hi bro
I haven't noticed any touch bug with this device and firmware. Even stylus is usable. Try it and report back.
Click to expand...
Click to collapse
Hi,
I upgraded my SGP-511 yesterday with this version and the touch sensibility is really better.
Just a comment about the problem. I was looking for some fix for that problem when I found that with CM 11 the tablet doesn't have this kind of problem. In my case I didn't install the CM to keep the warranty.
chentz78 said:
Hi,
I upgraded my SGP-511 yesterday with this version and the touch sensibility is really better.
Just a comment about the problem. I was looking for some fix for that problem when I found that with CM 11 the tablet doesn't have this kind of problem. In my case I didn't install the CM to keep the warranty.
Click to expand...
Click to collapse
Hi mate. Thanks for you feedback.
Dear XDA-Community,
I have a really strange problem with my ZUK Z1 touchscreen, but only with ROMs with a build date after the 22th of Dezember 2016.
First I thought it's because I didn't wipe my phone fully before flashing the ROMs, but yesterday I tried it after wiping my phone completely.
But didn't work neither.
So after flashing the ROM and rebooting my phone, I "couldn't" control my phone, but then I realized that the touch reply was just in the "wrong place" like I touched in bottom and the output was in the middle of the screen.
I didn't have this problem before, and i researched all over the internet, if it's problem with the ROM but it doesn't seem so. Like I'm the only one with such an issue.
I hope anyone could help me.
Best regards
johannestheg
johannestheg said:
Dear XDA-Community,
I have a really strange problem with my ZUK Z1 touchscreen, but only with ROMs with a build date after the 22th of Dezember 2016.
First I thought it's because I didn't wipe my phone fully before flashing the ROMs, but yesterday I tried it after wiping my phone completely.
But didn't work neither.
So after flashing the ROM and rebooting my phone, I "couldn't" control my phone, but then I realized that the touch reply was just in the "wrong place" like I touched in bottom and the output was in the middle of the screen.
I didn't have this problem before, and i researched all over the internet, if it's problem with the ROM but it doesn't seem so. Like I'm the only one with such an issue.
I hope anyone could help me.
Best regards
johannestheg
Click to expand...
Click to collapse
It was the same for me. Becomes more and more and finally also in twrp the digitizer wasn't working anymore. I don't had a wrong calibration.
strongst said:
It was the same for me. Becomes more and more and finally also in twrp the digitizer wasn't working anymore. I don't had a wrong calibration.
Click to expand...
Click to collapse
Could you fix it? Or did you buy a new phone?
And if you fixed it, how did you do so?
best regards
johannestheg said:
Could you fix it? Or did you buy a new phone?
And if you fixed it, how did you do so?
best regards
Click to expand...
Click to collapse
I sent it back for warranty.
strongst said:
I sent it back for warranty.
Click to expand...
Click to collapse
Damn. Shouldn't have bought it on such a unserious site^^
If someone has a solution, pls tell me
How I said, it's working perfectly on CM 14.1, so it seems like a software problem
johannestheg said:
Damn. Shouldn't have bought it on such a unserious site^^
If someone has a solution, pls tell me
How I said, it's working perfectly on CM 14.1, so it seems like a software problem
Click to expand...
Click to collapse
Few users reported touch issue solved after flashing Radi active kernel in N. Did u try latest NuceaRom or Mokee?
Narasimha12 said:
Few users reported touch issue solved after flashing Radi active kernel in N. Did u try latest NuceaRom or Mokee?
Click to expand...
Click to collapse
No I didn't, but I'll give it a try, thank you mate
But I wonder if the problem is solved then completely, or only if you have installed NucleaRom/Mokee
johannestheg said:
No I didn't, but I'll give it a try, thank you mate
But I wonder if the problem is solved then completely, or only if you have installed NucleaRom/Mokee
Click to expand...
Click to collapse
My understanding is that, something messed in upstream lineage OS, which effected couple of updates of NucleaRom and initial testing builds of Mokee. With the help of Radioactive kernel developers, thankfully Mokee managed to debug it.
Does screen issue happens in lower version of Android too? Like MM & L? if so I'm not sure this is going to help.
Narasimha12 said:
My understanding is that, something messed in upstream lineage OS, which effected couple of updates of NucleaRom and initial testing builds of Mokee. With the help of Radioactive kernel developers, thankfully Mokee managed to debug it.
Does screen issue happens in lower version of Android too? Like MM & L? if so I'm not sure this is going to help.
Click to expand...
Click to collapse
No didn't ever have this problem before, so thanks for the good news, I'll update after testing
So I tried it with the Tesla Rom and it worked fine
Thanks for the help
johannestheg said:
So I tried it with the Tesla Rom and it worked fine
Thanks for the help
Click to expand...
Click to collapse
Bingo
Sent from my Zuk Z1 using XDA Labs
Same problem with my Zuk Z1.
Today I flashed de unofficial LineageOS and the touchscreen don't work.
I flashed again the old ROM (October CM) and the touchscreen worked again.
I tried later with full wipe... Same problem.
From: Me
Via: Huawei Mate 9 (MHA-L09) - Tapatalk
To:
sethnet said:
Same problem with my Zuk Z1.
Today I flashed de unofficial LineageOS and the touchscreen don't work.
I flashed again the old ROM (October CM) and the touchscreen worked again.
I tried later with full wipe... Same problem.
From: Me
Via: Huawei Mate 9 (MHA-L09) - Tapatalk
To:
Click to expand...
Click to collapse
Latest lineage OS doesn't have this problem. If you are still getting the touch screen issues, try NucleaRom
Sent from my Zuk Z1 using XDA Labs
Hi
I downloaded the b225 firmware 3-4 days ago and since then the battery from its over 5 hours average SOT has lost +20% of its power...
Has anyone else faced a similar issue after updating??!!
The old issues for me still not resolved :
Google now does not get activated by voice command
Whatsapp/telegram/etc social apps dont download latest messages unless the apps are open and running in background
Oh well....
I'm not facing the battery issue.
But the WhatsApp messages' auto receive failure persists.
Better battery life...
Sal_Al said:
Hi
Has anyone else faced a similar issue after updating??!!
The old issues for me still not resolved :
Google now does not get activated by voice command
Whatsapp/telegram/etc social apps dont download latest messages unless the apps are open and running in background
Oh well....
Click to expand...
Click to collapse
I upgraded from B213 to B225 and I've actually seen slight improvement in battery life overall. FYI, I use Brevent.
As for notification issues.. still there... no change since I bought the phone in December last year.
Interesting answers...
Thanks.
Will keep on monitoring battery...
Have you installed google framework to use push.
Test with the app PNF push.
My device: Mate 9 supersu b156 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
audioralf said:
Have you installed google framework to use push.
Test with the app PNF push.
My device: Mate 9 supersu b156 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
Click to expand...
Click to collapse
Thanks. Tried but not working.
You are try to factory reset after update ota?
newyesor said:
You are try to factory reset after update ota?
Click to expand...
Click to collapse
Nope. Didnt try. Have lots of files to backup.
rbt001 said:
I upgraded from B213 to B225 and I've actually seen slight improvement in battery life overall. FYI, I use Brevent.
As for notification issues.. still there... no change since I bought the phone in December last year.
Click to expand...
Click to collapse
Today finally back to the old levels of battery life...
can i use latest chinese firmware in us version of the mate 9 - B567 ?
Manan79 said:
can i use latest chinese firmware in us version of the mate 9 - B567 ?
Click to expand...
Click to collapse
Yes. But you have to do rebranding.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
5[Strogino] said:
Yes. But you have to do rebranding.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Click to expand...
Click to collapse
Thanks, any advantage of rebranding US version to china version ? more upto date firmare, any other ?
Manan79 said:
Thanks, any advantage of rebranding US version to china version ? more upto date firmare, any other ?
Click to expand...
Click to collapse
Yes, Chinese version is updated frequently.
Additionally, it has call recording out-of-box and option to hide navigation keys
But there are some disadvantages too, like some specific problems with Google apps. I can't say that it is big problem, but in some cases it can broke your common way of using phone (navigation, Google assistant...). Yeah, it can be fixed, but you have to do something instead of gaining same in world roms.
There are also some bloatware with Chinese symbols which you have to disable or uninstall.
And Chinese version has tough algorithm to unload apps from memory, so user will get some problems with notifications. There is workaround to lock apps in memory. But it is another fix that you have to do manually in Chinese roms.
Anyway, you can try rebrand to Chinese rom, use it a few time, then back to US version or stay.
Sal_Al said:
Today finally back to the old levels of battery life...
Click to expand...
Click to collapse
I am facing a similar issue, what did you do to correct this?
Wipe cache partition or factory reset?
update to B231 and it will be back to 24+ hrs of battery
#redmi3s #ViperOS
guys, please help! I decided to try Viper OS, the Rom runs great, but whenever I want to use the GPS for Navigation my phone reboots! I tried with Google Maps and Waze. I was with RR_final before that and also experienced random reboots, even when I am in a call the phone would just restart, so I decided to try ViperOS, but still have these issues. For now the phone only reboots when I use the GPS.
What can I do to solve the problem?
P.s I have not flashed Firmware recently because there was a discussion if we need to update Firmware and several guys stated that updating Firmware can ruin the phone.
Thanks
Anyone?
Try another rom. See if the issue persists. Also give gps fix by difr a try. You can find it in the ROMs thread.
I tried many custom roms,almost all of them have random reboot issues,and even miui.It will stuck a while and reboot,but sometimes even forever until you manual reboot,I don't know is sources or soc issues
Developer. said:
I tried many custom roms,almost all of them have random reboot issues,and even miui.It will stuck a while and reboot,but sometimes even forever until you manual reboot,I don't know is sources or soc issues
Click to expand...
Click to collapse
Try underclocking the cpu. It's a hardware issue.
william.johhn7! said:
Try underclocking the cpu. It's a hardware issue.
Click to expand...
Click to collapse
That means it can't be fixed?
Developer. said:
That means it can't be fixed?
Click to expand...
Click to collapse
Well I faced this random reboot issues in marshmallow ROMs (MIUI as well as custom). But now I don't. Someone else mentioned they had such an issue and told me it was a hardware problem.
william.johhn7! said:
Well I faced this random reboot issues in marshmallow ROMs (MIUI as well as custom). But now I don't. Someone else mentioned they had such an issue and told me it was a hardware problem.
Click to expand...
Click to collapse
Ok,nougat rom also have this issue
I`ll try Arvansoft MIUI. Have not tried it
I've been having this problem as well for the past couple months.
Was thinking of reinstalling MIUI just to make sure the firmware is installing properly.
Its battery draining I used it for weeks and replaced it by aosp v5 (8.0) it's best ROM I think its better than rr
I managed to rid myself of this problem. First, I installed the latest MIUI (global beta) by the official method. Then I installed the latest CarbonROM. Reboots are gone.
Hey there man
I'm facing the same problem as you are, in my case it restart completely randomly. It's a common bug when it comes to custom roms. I searched for an answer on what or wheter there's even a solution.
What I'm trying right now is this:
You need to download SELinuxModeChanger, (I just read out there the safest way to do it is via F-Droid, so get the app from their own client app, should be okay, the XDA thread is this one https://forum.xda-developers.com/showthread.php?t=2524485).
You're going to need as well the lastest SU binary and that's all pretty much.
Now, open the app and obv give it root permissions, then change the SELinuxMode from permissive to enforcing. I don't really much know, but so far it works for me, I'll keep an eye on your thread and tell you if this actually fixed my phone, but you've waited enough I guess so you might want to give it a try.
Maybe (if it's a Hardware problem, which I'm not sure at all) you might have overclocked a lil bit too much, try to underclock it.
Search, you find plenty of solutions out there, on of them might be the one! (but keep an eye on what you should and shoudn't do, and search on different forums for the same method so you figure out how safe it is and exactly how to do it)
Hope it helps, at least I've tried. If it doesn't, well, we'll both still having random reboots hahaha
Edit: it didn't but now it reboots less often I guess.
Exactly
Developer. said:
I tried many custom roms,almost all of them have random reboot issues,and even miui.It will stuck a while and reboot,but sometimes even forever until you manual reboot,I don't know is sources or soc issues
Click to expand...
Click to collapse
Thats exactly what i have faced.Sometimes it goes on days with out any problem. Sometimes it restarts 3 times in a day.
While looking in logs(logs from Android studio monitor , while phone restarted suddenly) the peculiar one i saw is FPC_TAC log . Is it related to fingerprint or what?After that it restarts.
phalsgun said:
Thats exactly what i have faced.Sometimes it goes on days with out any problem. Sometimes it restarts 3 times in a day.
While looking in logs(logs from Android studio monitor , while phone restarted suddenly) the peculiar one i saw is FPC_TAC log . Is it related to fingerprint or what?After that it restarts.
Click to expand...
Click to collapse
FPC_TAC log usually appeared if you touched the fingerprint
Developer. said:
FPC_TAC log usually appeared if you touched the fingerprint
Click to expand...
Click to collapse
But not at error level right?
ofmoll said:
Hey there man
I'm facing the same problem as you are, in my case it restart completely randomly. It's a common bug when it comes to custom roms. I searched for an answer on what or wheter there's even a solution.
What I'm trying right now is this:
You need to download SELinuxModeChanger, (I just read out there the safest way to do it is via F-Droid, so get the app from their own client app, should be okay, the XDA thread is this one https://forum.xda-developers.com/showthread.php?t=2524485).
You're going to need as well the lastest SU binary and that's all pretty much.
Now, open the app and obv give it root permissions, then change the SELinuxMode from permissive to enforcing. I don't really much know, but so far it works for me, I'll keep an eye on your thread and tell you if this actually fixed my phone, but you've waited enough I guess so you might want to give it a try.
Maybe (if it's a Hardware problem, which I'm not sure at all) you might have overclocked a lil bit too much, try to underclock it.
Search, you find plenty of solutions out there, on of them might be the one! (but keep an eye on what you should and shoudn't do, and search on different forums for the same method so you figure out how safe it is and exactly how to do it)
Hope it helps, at least I've tried. If it doesn't, well, we'll both still having random reboots hahaha
Edit: it didn't but now it reboots less often I guess.
Click to expand...
Click to collapse
Well,thst's not really helped,it seems a hardware problem
---------- Post added at 20:09 ---------- Previous post was at 19:56 ----------
phalsgun said:
But not at error level right?
Click to expand...
Click to collapse
No,see the logcat,every touchs have many error logs
Developer. said:
Well,thst's not really helped,it seems a hardware problem
---------- Post added at 20:09 ---------- Previous post was at 19:56 ----------
No,see the logcat,every touchs have many error logs
Click to expand...
Click to collapse
Or maybe the reboots are because of bad memory blocks in the rom.
---------- Post added at 07:38 PM ---------- Previous post was at 07:36 PM ----------
I am maintaining atleast 10 gb free now and faced no reboots in a week.Before when my rom was full it used to restart too frequently.
Anyone can confirm this suspicion of mine?
phalsgun said:
Or maybe the reboots are because of bad memory blocks in the rom.
---------- Post added at 07:38 PM ---------- Previous post was at 07:36 PM ----------
I am maintaining atleast 10 gb free now and faced no reboots in a week.Before when my rom was full it used to restart too frequently.
Anyone can confirm this suspicion of mine?
Click to expand...
Click to collapse
No,it's not a full space problem,and some rom I used a month or a week or just few days and faced random reboots,