Hello
I recently flashed the BETA 2 build of CM12.1, and used the sensor fix for it to boot. Everything works fine.
But when I flashed Xposed Framework it resulted in many crashes, Settings crashes when trying to see all apps. Email and Trebuchet crashes too when booting.
Is there any solution to get everything to work? I really love CM12.1 and hate the stock LP firmware. (flashed CM12.1 on top of the latest kitkat firmware)
* Sorry for my poor english
Related
Hey...
Just got a new OnePlus One from the box.
i got him with cm 11s 4.4.4 .
Everything worked just fine...
After updating to CM 12S or CM12.1 or OxygenOS 1.0
The screen doesn't go off during calls..
It really annoying and i wonder how to fix that.
Update :
Tried to flash old modem like the 44S and still doesn't work.. what should i do?
I'm running nighly CM 12.1
You need to flash a Lollipop modem, not KitKat. Have you tried that?
i have been installed 5.0.2 modem...
doesnt work... if i install 5.1.1 proximity work , but gyroscope doesn't work...
update , after installing all types of modems.
44S
and Oxygen OS 1.0 modem
and 5.0.2 CM12S
And 5.1.1
Still nothing...
I found one file on XDA that "fix" the problem and indeed it has fixed it but
after installing that the gyroscope and rotation on phone stopped working...
In the same boat, I'm in stock CM12 5.0.2 and both proximity sensor and gyroscope are not working. Any help ?
hi..
i hav this problem with my tab 2 p3100..and its bit annoying me for som time nw.
i was using the cyanogenMod (CM 12.1) by @Android-Andi ..the earlest build..bt due to some soft reboot problm i changed to official cyanogenmom 11 nighties. and its respective gapps..
aftr some days its started showing "unfortunately process.com.google.process.gapps has stopped" message continuously..it was annoying ..it also shows fc messages of most of the apps installed including trebuchet app.
so i thought its a rom issue or gapps issue..so chaged by rom to stable official jellybean cyanogenmod and its gapps..but agn i encounter similr annoying problem of "unfortunately process.com.google.process.gapps has stopped" message and other apps
atlast i chage bac to Android-Andi's cyanogenMod (CM 12.1) and lollipop Base Gapps package for 5.1.1 by Deltadroid..
bt i am stll having same problem..first i thought its a sofware problm ..nw am confused whtr its a hardware problm..
please help me
I had some of this trouble once, It was fixed by installing stock rom for a few days then returning to CM11, it seems something wrong with our eMMC, may be disabling on the kernel trim caused it, on stock trim is working, Anyway on returning to CM11 it's much slower than it used to be before, So I am now with Next Rom from ketut.kumajaya, A good smooth stock based rom and could be the smoothest among stock based roms.
Hassan 4 said:
I had some of this trouble once, It was fixed by installing stock rom for a few days then returning to CM11, it seems something wrong with our eMMC, may be disabling on the kernel trim caused it, on stock trim is working, Anyway on returning to CM11 it's much slower than it used to be before, So I am now with Next Rom from ketut.kumajaya, A good smooth stock based rom and could be the smoothest among stock based roms.
Click to expand...
Click to collapse
thnks for the replay..nw am on stock rom..working fine
pauldominik said:
thnks for the replay..nw am on stock rom..working fine
Click to expand...
Click to collapse
Urw, If it doesn't get fixed for CM11, you may try Next rom, It's a non-laggy stock rom even in games it's as cm11.
Hassan 4 said:
Urw, If it doesn't get fixed for CM11, you may try Next rom, It's a non-laggy stock rom even in games it's as cm11.
Click to expand...
Click to collapse
ok...i wll try..bt crrnly i am running it on slimkat..and its wrks ok..so wll keep it runnig fr som days..
It will come back again after a few days. I haven't discovered any permanent fixes but resetting app preferences in app settings helps. If even Settings is also FCing then go to recovery do backup and restore. You don't need to have old backups, you can backup the broken ROM itself and restore it. That way you can restart and not face Settings FC. Then you can reset preferences and the problem will go away for sometime.
Issue might be lollipop or the recent stock gapps post-PA Gapps era. Stock gapps get very close to occupying system partition during installation itself. Try having a smaller Gapps and download any google app you require from playstore
Hi there members of xda
A few months ago i updated to marshmallow on my moto g3 , and the experience was awful, not to mention the touch screen issues. I successfully downgraded to lollipop by skipping gpt.bin and bootloader.img, and i used lollipop for a while then got bored of it, so i tried to install cm13 official. When i did that , my phone gets google play store and google play services FC's on cm13. I have set google play services all permissions .. I have tried a wide variety of gapp packages and they all have the same problem. Google play store instantly crashes when i tap it, if that helps atall.
For now, i reflashed marshmallow stock. Should i be flashing cm13 from stock mm , or stock lp.. becuase i havent tried flashing using stock mm , becuase i didnt think it would make a difference as i always wipe the system partition before flashing cm anyway. :/
Many thanks,
therealduff1
therealduff1 said:
Hi there members of xda
A few months ago i updated to marshmallow on my moto g3 , and the experience was awful, not to mention the touch screen issues. I successfully downgraded to lollipop by skipping gpt.bin and bootloader.img, and i used lollipop for a while then got bored of it, so i tried to install cm13 official. When i did that , my phone gets google play store and google play services FC's on cm13. I have set google play services all permissions .. I have tried a wide variety of gapp packages and they all have the same problem. Google play store instantly crashes when i tap it, if that helps atall.
For now, i reflashed marshmallow stock. Should i be flashing cm13 from stock mm , or stock lp.. becuase i havent tried flashing using stock mm , becuase i didnt think it would make a difference as i always wipe the system partition before flashing cm anyway. :/
Many thanks,
therealduff1
Click to expand...
Click to collapse
Which gapps did you use? If you are having issues on cm try CrDroid or BrokenOS (go to their G+ community)
Btw, on the cm thread Alberto posted a fix for the touchscreen issues.
Henriquefeira said:
Which gapps did you use? If you are having issues on cm try CrDroid or BrokenOS (go to their G+ community)
Btw, on the cm thread Alberto posted a fix for the touchscreen issues.
Click to expand...
Click to collapse
I installed an old build of cm in the end and then updated to new version via ota. thanks anyway !
Cyanogenmod 14.1 Nightly official went out for OPO,i found some several bugs for my phone:
-AudioFX Scroll Problems(when you swipe left or right ,it's choppy
-when you swipe down the status bar,and enable Bluetooth,and disable,then enable button gets grey,so you can't turn it on or off again,there you have to go to settings for doing it
Device: OnePlus One
Cyanogenmod Version:cm 14.1-20161119-NIGHTLY-bacon
Sorry guys for my crap english,i speak German
Krypno said:
Cyanogenmod 14.1 Nightly official went out for OPO,i found some several bugs for my phone:
-AudioFX Scroll Problems(when you swipe left or right ,it's choppy
-when you swipe down the status bar,and enable Bluetooth,and disable,then enable button gets grey,so you can't turn it on or off again,there you have to go to settings for doing it
Device: OnePlus One
Cyanogenmod Version:cm 14.1-20161119-NIGHTLY-bacon
Sorry guys for my crap english,i speak German
Click to expand...
Click to collapse
There's a lot more bugs than that but nightlies have just started so in time they'll be fixed.
The Bluetooth bug I've confirmed it but if you select it one more time, after its grayed out it works and you can disable.
Audio FX is choppy but luckily EQ settings are set just once. I didn't notice initially when I used it cause I was driving (I know it's not safe).
System Profiles don't work. CM Bug Report FC on boot and when you install apps.
Slow charging (affects some devices).
Circle battery in status bar doesn't work.
Volume keys control media volume doesn't work... etc
Just be patient these bugs will be ironed out
Renosh said:
There's a lot more bugs than that but nightlies have just started so in time they'll be fixed.
The Bluetooth bug I've confirmed it but if you select it one more time, after its grayed out it works and you can disable.
Audio FX is choppy but luckily EQ settings are set just once. I didn't notice initially when I used it cause I was driving (I know it's not safe).
System Profiles don't work. CM Bug Report FC on boot and when you install apps.
Slow charging (affects some devices).
Circle battery in status bar doesn't work.
Volume keys control media volume doesn't work... etc
Just be patient these bugs will be ironed out
Click to expand...
Click to collapse
oh wow thanks but the bluetooth bug is really annoying for me,but i am patient:]
OPO UPDATER issue with all OFICIAL CM14. 1.
Hi guys,
Freshly coming COS 13 today. I installed oficial TWRP 3.0.2.0 then CLEAN flashed the first CM14. 1 nightly and then 7.1 Gapps.
All happened correctly, l also noticed the bugs already mentioned. Ok... Not bad beginning this cm14.1 after 4 nightlies....
almost....
THE OTA UPDATER DOES NOT FIND ANY NEW UPDATE (when there are 3 till the 2016.11.19 version).
So l download and dirty flash them manually...
Just if l have to do that every 3 days.... ?
I also just flashed unofficial TWRP 3.0.3.2 Tugapower.img, but no change.
DOES SOMEBODY WOULD HAVE AN IDEA WHY THIS TROUBLE? IS IT A PROBLEM OF THE ROM? I doubt about it cause l saw only one similar case on inet today (no answer) and nothing in here.
I did updating tests on Marshmallow Resurrection remix 5.7.4 and official CM13 nightlies and l have no problem....
.Only with OFFICIAL CM14. 1 NIGHTLIES
Thanks.
d#
catleya60 said:
Hi guys,
Freshly coming COS 13 today. I installed oficial TWRP 3.0.2.0 then CLEAN flashed the first CM14. 1 nightly and then 7.1 Gapps.
All happened correctly, l also noticed the bugs already mentioned. Ok... Not bad beginning this cm14.1 after 4 nightlies....
almost....
THE OTA UPDATER DOES NOT FIND ANY NEW UPDATE (when there are 3 till the 2016.11.19 version).
So l download and dirty flash them manually...
Just if l have to do that every 3 days....
I also just flashed unofficial TWRP 3.0.3.2 Tugapower.img, but no change.
DOES SOMEBODY WOULD HAVE AN IDEA WHY THIS TROUBLE? IS IT A PROBLEM OF THE ROM? I doubt about it cause l saw only one similar case on inet today (no answer) and nothing in here.
I did updating tests on Marshmallow Resurrection remix 5.7.4 and official CM13 nightlies and l have no problem....
.Only with OFFICIAL CM14. 1 NIGHTLIES
Thanks.
Click to expand...
Click to collapse
maybe disable auto cyanogenmod recovery download?
So I had installed the latest lineageOS version ( 17.1, android 10, osprey moto g3) from the official website and flashed it correctly, but after some time, I noticed that the torch icon was greyed out in the status bar and any camera app won't work.
The app showed- "Camera stopped working"
Cleared cache, app info, rebooted the phone but nothing seemed to work.
I thought that flashing the ROM again would fix it, I redownloaded the latest lineageOS version, new GApps, and flashed it in the correct way( first wipe then flash), but the issue came back after a few reboots.
So I rebooted again and it got fixed, but I think the issue might spring back.
Is there any fix for this?
atharvvvg said:
So I had installed the latest lineageOS version ( 17.1, android 10, osprey moto g3) from the official website and flashed it correctly, but after some time, I noticed that the torch icon was greyed out in the status bar and any camera app won't work.
The app showed- "Camera stopped working"
Cleared cache, app info, rebooted the phone but nothing seemed to work.
I thought that flashing the ROM again would fix it, I redownloaded the latest lineageOS version, new GApps, and flashed it in the correct way( first wipe then flash), but the issue came back after a few reboots.
So I rebooted again and it got fixed, but I think the issue might spring back.
Is there any fix for this?
Click to expand...
Click to collapse
Hello members,
Last week i'v also installed the latest lineageOS version ( 17.1, android 10) Gapps nano, on my Samsung A3 2017. With the TWRP tool., Nice ROM!
Unfortionally with the same issue as above, Samsung and other camera app's very often not working, need to reboot to fix that.
The flashlight does not work either then, and much more irritating BlueTooth not working anymore, my A3 always had perfect connection with my Parrot carkit CK3100.
I'v found in several forum some workarounds for this but these do not solve the issues long enough.
But the issues are also found in older releases from LineageOS.
Will there be a update for these mentioned 3 issues?
If not, i need to install another ROM which is not based on LineageOS.
The Cam and BT must work without any problems.
Thank you very much.
Frank.