Well, i have a Moto G5 Plus with AOSP Extended Rom (Now), and i have experinced soft reboot some times in my pocket and others when i use my phone (Specially in facebook Apps), i think the problem maybe was for the rom (Resurrection Remix) so i decided to change, so i flash Validus, Aosp Extended and Stock, but in all Roms i Have these soft reboots, i unistall unused apps, do a factory reset, clean flash, reinstall apps and nothing someone who has the same issue? any fix?
*Another thing/issue haptic feedback some times work and some times dont (fingerprint sensor, virtual buttons, keyboard)
*Im on Aosp Extended Rom
*Xposed Systemless
*Magisk
*Stock Kernel(AOSP Ext Rom)
Add Some Logs(last softreboot 19:47 to 19:52) hope will be usefull
Related
I'm sorry to sound noobish, but every time I flash a ROM on my Nexus 4 (mako) that isn't a Cyanogenmod build (10.2-20130904-NIGHTLY-mako) , my home softkey becomes completely useless and the AOSP or AOKP keyboard constantly crashes. I was told this is a known bug in certain source codes as far as the keyboard is concerned in 4.2.2 builds, but I'm still mystified by the home button issue and as to why I other people can be using the same ROMs that I can't without a problem. Is there a certain version of GAPPS that I can flash to avoid this problem, or is there a known fix? I always wipe data and cache when flashing, so I'm pretty sure this isn't a user error, other than which version of GAPPS I'm flashing (gapps-jb-20130813-signed.zip).
trevorftard said:
I'm sorry to sound noobish, but every time I flash a ROM on my Nexus 4 (mako) that isn't a Cyanogenmod build (10.2-20130904-NIGHTLY-mako) , my home softkey becomes completely useless and the AOSP or AOKP keyboard constantly crashes. I was told this is a known bug in certain source codes as far as the keyboard is concerned in 4.2.2 builds, but I'm still mystified by the home button issue and as to why I other people can be using the same ROMs that I can't without a problem. Is there a certain version of GAPPS that I can flash to avoid this problem, or is there a known fix? I always wipe data and cache when flashing, so I'm pretty sure this isn't a user error, other than which version of GAPPS I'm flashing (gapps-jb-20130813-signed.zip).
Click to expand...
Click to collapse
The known issue you are talking about is the JSS deadlocks? if yes, then it is not the problem with you.. for you it force closes the keyboard.. are you following the procedure of installing rom properly? are you doing dirty flash (flash without wiping data)? you can find out if gapps is responsible by booting into a freshly installed rom without installing gapps and see if the problem persists..
You should also format the /system partition when you flash a new rom.
For some roms the Home button stop working for me and to fix it I had to install gapps, but most CM based roms I use don't have that issue.
As for keyboard, I always delete the default keyboard from the rom and use Google Keyboard.
Andre_Vitto said:
The known issue you are talking about is the JSS deadlocks? if yes, then it is not the problem with you.. for you it force closes the keyboard.. are you following the procedure of installing rom properly? are you doing dirty flash (flash without wiping data)? you can find out if gapps is responsible by booting into a freshly installed rom without installing gapps and see if the problem persists..
Click to expand...
Click to collapse
Please explain what JSS deadlocks are. I don't dirty flash. I always wipe data. As for the keyboard and home buttons not functioning properly,I have this problem with XenonHD, PACman ROM, AOKP and CM variants.
trevorftard said:
Please explain what JSS deadlocks are. I don't dirty flash. I always wipe data. As for the keyboard and home buttons not functioning properly,I have this problem with XenonHD, PACman ROM, AOKP and CM variants.
Click to expand...
Click to collapse
No your problem is not the jss deadlocks.. it happens when you type very fast or something.. it phone vibrates for like 5-10 sec and then restarts. I dont think its your problem. Sorry mate I have no idea why you are having the keyboard and homescreen issue even when you are are doing a factory reset every time you flash.. and why its not happening with CM 10.2..
Andre_Vitto said:
No your problem is not the jss deadlocks.. it happens when you type very fast or something.. it phone vibrates for like 5-10 sec and then restarts. I dont think its your problem. Sorry mate I have no idea why you are having the keyboard and homescreen issue even when you are are doing a factory reset every time you flash.. and why its not happening with CM 10.2..
Click to expand...
Click to collapse
Well, that's unfortunate. I've found that the RevoltHD ROM doesn't have problems, but that's because it's got integrated GAPPS.
Been having the same issue with my Nexus 4, after installing GAPPS the keyboard crashes and the home button stops responding. Did anyone figured it out by any chance? Thanks.
I still don't know what caused it, but I figured out that more recent nightly versions of those ROMs don't have that problem. I'm using AOKP currently and that used to be a problem ROM.
Take off vibration and sound and all the bells and whistles and your keyboard should be fine if the issue isn't Rom specific. Also, it could be kernel related.....try boosting touch input if nothing else
Sent by flying midget
I get the same problem, I factory reset each time I switch ROMs. I was trying with Vanir a couple of days ago and couldn't get the home button to work, tried OmniROM and it worked perfectly, went back to Paranoid it worked perfectly again, went back to Vanir and it didn't work. Was odd.
Hello Everyone,
Nexus 4
Paranoid Android 4.2Beta1
Franco Kernel
I just upgraded to PA 4.2Beta1 from PA 4.1.......
after installing the rom.....when i use my browser or messenger where we require keyboard....the Keyboard doesnt pop up....whats up with this....and also the back button of my navigation bar doesnt work.......this even happened with carbon rom a few days back...when i was experimenting with it.....but then i restored to PA4.1 due to the above given problems....plz offer a solution to this...
The same problem
keyboards not working
please help me my keyboards are not working . i have installed an custom rom.
I'm on Exodus ROM, 1707 build.
Lightning SBTC kernel.
Pico CyanogenMod gapps.
My issue is that apps download normally but some (most of them) take way too longer than normal to install.
I tried Installing apps from apks and the same issue arises.
I reflashed the to, went back to kk and upgraded. Then flashed this ROM again. But no luck
Also After flashing CMOS 12 apps, I had 2 theme store. I had to remove one (the one without cyanogen logo).
But the issue is that after I apply a theme, the messenger, whatsapp and some other apps' fonts reset to default after sometime.
Please help to solve these issues!
About your issue of slow install, that has been quite the normal case with Lollipop in general, if you feel that apps are being installed at a slower rate then try some other ROM if same continues with other ROM then you'd have found that it's not the ROM's fault else its got something to do with the ROM, post a query to the OP of that ROM's thread.
There maybe some conflict in the theme manager due to you flashing COS12 apps. I'd recommend that you flash the ROM again and see if this issue persists without you flashing COS12 apps.
d3athwarrior said:
About your issue of slow install, that has been quite the normal case with Lollipop in general, if you feel that apps are being installed at a slower rate then try some other ROM if same continues with other ROM then you'd have found that it's not the ROM's fault else its got something to do with the ROM, post a query to the OP of that ROM's thread.
There maybe some conflict in the theme manager due to you flashing COS12 apps. I'd recommend that you flash the ROM again and see if this issue persists without you flashing COS12 apps.
Click to expand...
Click to collapse
Happens for almost all ROMS
My boss rooted his LG G2-D02 and installing CM 12.1 in the process. Now, after knowing that CM 13 was already released, he downloaded a copy of it and immediately flashed it onto his phone. He got a problem with Gapps and DL-ed a problematic version which caused the notification,"Unfortunately, Setup Wizard has stopped" to pop up repeatedly. We had tried following a few advices from this website but to no avail.
1.) We already tried using Force Stop and Disable under Apps->(Show system apps)->Setup Wizard (CM). I had also tried giving it app permissions, but all app permissions were already available.
2.) The only option is to flash CM 12.1 back again but it can't be done. My boss set the default recovery app to Cyanogenmod's own recovery program, which had limited functions, so I can't
also use TWRP ATM.
3.) My boss also tried something on ADB but to no avail
4.) Factory reset didn't also solve the problems.
I'm almost running out of solutions... Perhaps, I can use a helping hand from brighter minds in this community.
TIA
I'm using cloudyg2 v3.3 because cm13 has got a lot of bug for example
-I can't proceeded to music
-systtem has stopped once a hour
-I can't close touching vibration
I can't remember now but cm13 has got really much bug (yeah my english is very bad,I know this)
Now system is stable and battery is very very good but still İ can't scretch to music
So hey.
I'm facing a really weird issue with my phone. I currently use DU and it works perfectly, however whenever I install 'Ubermallow' or 'Omni ROM' or 'chroma' or even PN for that matter they all initially work perfectly. I go ahead and install AK and xposed it's all still fine, then I randomly restart my device. It starts bootlooping. So I think maybe it's substratum going haywire I remove the overlay, and it's still looping. I end up rm-rF'ing the vendor partition and reflash that to no avail. Now I'm thinking AK kernel is messing up, but it works fine on DU. Xposed could also be it but again I've used it for so long on DU and before that on PA. So if anyone has any advice or anything drop a comment. Thank you
Well typically if you get a bootloop, something isn't playing nice with the system[obviously].
In your case: I'm using Pure Nexus + Kylo Kernel + Substratum and no random reboots / bootlooping on a controlled reboot.
Suggestions:
AK Kernel - Make a profile and then back it up, make sure it is working - no screen glitches or ui crashes, and reboot. Bad kernel settings [undervolting, etc] can cause bootlooping. Once you verified there you can boot, move onto your theme.
Regarding substratum - I would go into the vendor folder, delete the entire overlay folder, reboot, then apply your theme - making sure the themes are compatible. If you experiecing per-app issues, go back and then individually disable its over. Once it is set, backup your theme and reboot. If you experience bootlooping here then you've narrowed it down to the theme. You can delete the overlay folder from TWRP.
As always, install the ROM via clean flash for the best results.
Device Lenovo k6 power k33a42 running stock 7.0 last stock build.
Issue
Device would work fine as long as I am on lockscreen, I can put password type every thing, but the moment I enter the correct password and start using it, it would freeze on the homescreen, I would lock and unlock again by typing the password, only to get frozen screen. so power off and reboot, I can type in password again and get to homescreen, this time I could use the device without freezing,
3rd time, it freeze in between.
lock, unlock, reboot, seems to make it work again.
factory reset many times. no effect.
flashed custom ROM LOS 15.1 and LOS 14.1, got process system stopped error on LOS 15.1 and on 14.1 have to log.
Used no mods, no files apart from ROM and opengapps
Clean flash, No external sd card.
My first few suspect,
1. LCD display loose connection that causes the device to sometimes works flawlessly and sometimes make it impossible, opened back panel, did some not so useful checkup, closed again. useless don't try.
2. Messed up OTA updates, flashing stock S223 update, will report if this solved.
3. Overheat, most unlikely,
and the culprit
Lenovo, spoiled Moto as well.
If anyone has any info that they can share, please feel free to comment..
Update
After flashing
Lenovo_K33a42_S223_Q00440_20170610 via QFIL (removed all the data, including the internal sd card)
All The problem seems to be gone, touch is responsive, no freezing or overheating anymore, even the MIC issue was resolved which was present before on this particular unit. noticed unstable and low sim signal sometimes.
I think it's best for anyone who is coming from Stock ROM to flash the Stock ROM via QFIL to avoid such issues first.
Got OTA update K33_S223_170610_ROW_TO_K33_S229_170908_ROW of 76mb
after update again got another one, system looks to be working fine. touch was responsive as well.
K33_S229_170908_ROW_TO_K33_S231_17114_ROW
79MB
after flashing this I could notice touch lags, this is without installing any other 3rd party apps and no files whatsover apart from the ones lenovo pushed through the device.