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 ?
Related
Hey guys,
So I'm sure a few of you must be aware of the fact that Rovo89 has released an alpha version of Xposed for android 5.0 and up,
which is available here
I wanted to ask if anyone has tried to install Xposed on their 1033's successfully, because I want to avoid screwing up my phone again.
So please comment on whether you have got it working, along with the recovery and android version you were on.
Thanks
I did.. it's being a night mare.. apk is not getting installed and the framework zip was flased for nothing.. now I am kinda screwed, phone is totally slow and strge says it's gone/// I am trying to see if there are any other better options to work this out.. otherwise I have to flash sourav firmware
Yes i did..and its working fine for me..i m using xt1033 running on android 5.0.2 srock with philz recovery install...its working fine in lots of xt1033 with various roms..here is a thread for working module if u want
http://forum.xda-developers.com/showthread.php?t=3032004
Alright, I've done it and it works perfectly
you should flash ROm, then wipe cache and dalvik. it works fine.
Can anyone provide me exactly which version of Xposed Framework needs to be installed for Moto G XT1033 running on stock rooted 5.0.2? Link would be appreciable as the one I downloaded isnt working.
error running modules
this is all very confusing for me...
i've tried following every step carefully... it installs fine but none of the modules are working for me...
can anyone pls tell me what version do i need for XT1033 running CM 12.1 (android 5.1.1)
thnx
Hi
I have an issue with an XT1032 running 5.0.2. I flashed Xposed with TWRP and it went fine. But, the phone shows a low space warning and the apk does not install. Tried to remove almost everything (3 GB now free) and still the warning.
Does anybody faced this already? Is there a way to make it work?
Thanks
Hi , i've updated my Oneplus one to official Cm12s.
My screen wont wake up when call comes , i have to double tap / press power buttom in order to see call screen.
Its happening specially when sensor is coverd or phone is in my pocket.
I've tried many diffrent solutions like flashing old 11s modem , new alpha lollipop modem , cm12s proximity fix zip , cm12s extras zip but nothing works !
So i attempted to create this thread , please help if you know how to solve it !
Thanks
Try flashing the latest Lollipop modem:
http://boeffla.df-kunde.de/bacon/modems/Full-YNG1TAS0YL-modem-flashable.zip
Transmitted via Bacon
I am having an issue with my proximity sensor not working at all. The phone goes blank during a phone call and I cannot wake it up until after the call is over.
I am using an unofficial nightly build for CM11 from a few days ago. This was a recent downgrade from the recently released official CM12.1 nightly because I was not pleased with it's stability.
I used an app to see the sensor values and the light sensor works while the proximity reports nothing. Which modem should I try to flash for CM11 to try to get my sensor back?
I read the proximity sensor and the light sensor are the same hardware unit. Is this true? Or is there a chance I have to warranty my phone?
IAmTheRobin said:
I am having an issue with my proximity sensor not working at all. The phone goes blank during a phone call and I cannot wake it up until after the call is over.
I am using an unofficial nightly build for CM11 from a few days ago. This was a recent downgrade from the recently released official CM12.1 nightly because I was not pleased with it's stability.
I used an app to see the sensor values and the light sensor works while the proximity reports nothing. Which modem should I try to flash for CM11 to try to get my sensor back?
I read the proximity sensor and the light sensor are the same hardware unit. Is this true? Or is there a chance I have to warranty my phone?
Click to expand...
Click to collapse
You need to flash a KitKat modem, this is the latest:
http://boeffla.df-kunde.de/bacon/modems/Full-XNPH05Q-modem-flashable.zip
Transmitted via Bacon
Fixed! Thanks.
IAmTheRobin said:
Fixed! Thanks.
Click to expand...
Click to collapse
No worries.
Transmitted via Bacon
Help
Is it possible to flash the modem with cm (stock) recovery? My device is not rooted (bootloader locked).
I'm on cyanogen os 12. (ota update).
.::[email protected]::. said:
Is it possible to flash the modem with cm (stock) recovery? My device is not rooted (bootloader locked).
I'm on cyanogen os 12. (ota update).
Click to expand...
Click to collapse
No, you need a custom recovery. Just unlock your bootloader, simple. It really should be unlocked anyway, you'll be screwed if you get into trouble and need to flash the stock images, because it's at that time that the unlock command won't work, and then you can say bye bye to your phone.
Transmitted via Bacon
Not fixed !
Isuue remain same
Sent from my A0001 using XDA Free mobile app
Proximity sensor not working
I'm on COS12 and my proximity sensor isn't working as well.
Tried reflashing the rom (not clean install but just reflash), and wiping cache and dalvik, but no luck
Also tried the oxygen modem, it gave me no result either...
What should i do now
timmaaa said:
Try flashing the latest Lollipop modem:
http://boeffla.df-kunde.de/bacon/modems/Full-YNG1TAS0YL-modem-flashable.zip
Transmitted via Bacon
Click to expand...
Click to collapse
I downloaded the sensor app and it did show that the proximity sensor was not working.
1) Flashed full CM modem, proximity fixed, no text/notifications on wifi. I know because I sent text with a different phone through WIFI, nothing popped up. I turned off WIFI and I get the texts.
2) Flashed 12.1 CM, same behaviors as above.
3) Flashed back to Team Nocturnal's 5.1.1 build, still same result.
4) I flash CM11 05Q modem, I get notifications/text on WIFI, but the other end is I get the proximity sensor issue; phone doesn't turn off while on a call and it activates the screen.
Still no solution or fix. Just FYI I am an at&t customer on the west coast.
I've some issue related to yours with proximity, but before trying to flash with new firmware - want to ask some people who know more about this than me.
My proximity sensor works good, screen disables during calls, enables while I've put my phone away an ear, BUT it stops working in random situations. I'm using an option to prevent phone unlock with proximity sensor, but phones somehow wakes up in my pocket. After restart all backs to normal. So I think it's not HW related issue as proximity sensor works. Do you think that changing firmware might help?
I'm on latest COS12.1S ROM (updated to second OTA). On COS12S all works good with disabled ambient display option, with enabled same issue. On COS12.1S tried to disable ambient display but no success.
I want to ask if there is any problem (flicker screen, red notification on booting up...) when I install CM11 from stock 5.0.2 on Falcon Moto G XT1032? (follow this official guide on CyanogenMod: http://wiki.cyanogenmod.org/w/Install_CM_for_falcon)
Thank you.
I've done this recently and the only issue I've noticed is the screen flickering problem. The solution is to simply press the power button to lock the screen then unlock it and it should be fixed. You only have to do this once but if you reboot your phone you will have to lock/unlock again on first boot.
Thank you for your answer. Just to be sure, did you follow CM guide? Is there anything important which I should be careful about? (I did the same thing with several phones but still noob)
I just booted into custom recovery (I use Philz) and wiped the different partitions along with /cache and /dalvik. You can follow the guide and use the push method or you can use sideload which I did.
I did that and now i have problems with the mac address (i was using 5.1.1) my shows me a different mac and i don't know how fix it, but if i back to LP the problem is solved.
It's a bootloader issue for sure and general happen because you're bootloader is updated to Lolipop 5.0.2 and now you install kitkat as cm 11 over Lolipop.
In simple words your bootloader is new while the software is old
screen flickering issue can be resolved by downgrade bootloader but "BE EXTREMELY CAUTIOUS" failed to upgrade bootloader make your device permanently dead and downgrading is not recommended....
I will recommend try cm12.1 it's rock solid stable as cm11
I finished installed CM 11, firstly the prob is screen flickering. Then after installing all my apps, the android.com.systemui was crashed over and over and cannot use anymore. I reflashed CM and gapps and reinstalled apps but it happened again. Finally, I had to returned to Lollipop.
Anyway, thank you all for your help
Same thing happened to me unfortunately but I've found this one here and it is working beautifully. Try it and see if it works for you without the constant systemui errors.
Thank you. At the moment i am quite happy with GPE version. It seems that this version GPE 5.1.1 is better than Moto stock one.
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
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 !