Hey,
my proximity sensor is not working after:
-backing up my phone with twrp
-installing another rom
-restoring the backup with twrp
Now the proximity sensor is not working anymore. It's annoying, because my phone turns of while calling.
What can I do to fix this?
I downloaded an app to check the sensor values and it always showed "0" for the proximity sensor. I have no idea how to fix this. I rebooted my phone, installed the backup again, ...
Nothing helped
same problem happened with me today...
i also need solution..
devs plz help..
It's your modern causing the problem most likely. What ROM were you on? What ROM did you change to? What ROM did you go back to?
Transmitted via Bacon
hi,
i ve the same problem! Help......
1º i was the ROM euphoria CM12!
2º i make the restore of stock rom 44s oneplus
3º the proximity sensor dont work!!!!
hi,
Did you solved the problem? how?
thks.
c00l3rf4rm3r said:
Hey,
my proximity sensor is not working after:
-backing up my phone with twrp
-installing another rom
-restoring the backup with twrp
Now the proximity sensor is not working anymore. It's annoying, because my phone turns of while calling.
What can I do to fix this?
I downloaded an app to check the sensor values and it always showed "0" for the proximity sensor. I have no idea how to fix this. I rebooted my phone, installed the backup again, ...
Nothing helped
Click to expand...
Click to collapse
jeronimo.ribeiro.pedome said:
hi,
i ve the same problem! Help......
1º i was the ROM euphoria CM12!
2º i make the restore of stock rom 44s oneplus
3º the proximity sensor dont work!!!!
Click to expand...
Click to collapse
Go to the modem thread by @zephiK in the General Section and flash the 44S radio.
Transmitted via Bacon
Newer lollipop ROM are advising you to flash the new alpha modem. If you ever flashed cm12 official alpha, the new modem has been flashed to make proximity sensor on new cm12 code.
It'll break proximity sensor on older cm11s code. Answer is flash older modem like timmaaa said and problem fixed.
Sent From Lollipopified Bacon Goodness!
timmaaa said:
Go to the modem thread by @zephiK in the General Section and flash the 44S radio.
Transmitted via Bacon
Click to expand...
Click to collapse
Solved !! Thanks
YES!!
Rohitgomes said:
Solved !! Thanks
Click to expand...
Click to collapse
Dude! Thanks so much! I spent the whole day trying to find at least what had broken the proximity sensor and now it's fixed!!!!!
ek69 said:
Newer lollipop ROM are advising you to flash the new alpha modem. If you ever flashed cm12 official alpha, the new modem has been flashed to make proximity sensor on new cm12 code.
It'll break proximity sensor on older cm11s code. Answer is flash older modem like timmaaa said and problem fixed.
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
It's working again in my case!!! Thanks a lot :laugh:
timmaaa said:
Go to the modem thread by @zephiK in the General Section and flash the 44S radio.
Transmitted via Bacon
Click to expand...
Click to collapse
Didn't work for me.
1)Backup cm11s
2)Full wipe
3)Flashed from 11S to cm12 nightly
4)Flashed the 44S radio
inf:
opo 64Gb ver.
TWRP 2.8.5.1
b0r0d1nsky said:
Didn't work for me.
1)Backup cm11s
2)Full wipe
3)Flashed from 11S to cm12 nightly
4)Flashed the 44S radio
inf:
opo 64Gb ver.
TWRP 2.8.5.1
Click to expand...
Click to collapse
That's because if you're on a Lollipop ROM you need to flash a Lollipop modem.
http://boeffla.df-kunde.de/bacon/modems
Transmitted via Bacon
timmaaa said:
That's because if you're on a Lollipop ROM you need to flash a Lollipop modem.
Transmitted via Bacon
Click to expand...
Click to collapse
I tried all modem at page you gave me - same problem.
I solved problem by flashing old cm12 nightly (cm-12-20150106-NIGHTLY-bacon) - it works, but if i'll try update it - it will cause problem again
P.S. I extracted NON-HLOS.bin (it's modem file, right?) from this old nightly , i flashed last cm12 nightly and after that i flashed extracted modem via fastboot - it didn't help me
b0r0d1nsky said:
I tried all modem at page you gave me - same problem.
I solved problem by flashing old cm12 nightly (cm-12-20150106-NIGHTLY-bacon) - it works, but if i'll try update it - it will cause problem again
P.S. I extracted NON-HLOS.bin (it's modem file, right?) from this old nightly , i flashed last cm12 nightly and after that i flashed extracted modem via fastboot - it didn't help me
Click to expand...
Click to collapse
Why try all of them? Most of those modems are KitKat modems. Are you on the right firmware? And yes, NON-HLOS.bin is the modem, but it's only part of what's required. The Lollipop modems from Boeffla and the Lollipop firmware should fix your problem.
Transmitted via Bacon
timmaaa said:
Why try all of them? Most of those modems are KitKat modems. Are you on the right firmware? And yes, NON-HLOS.bin is the modem, but it's only part of what's required. The Lollipop modems from Boeffla and the Lollipop firmware should fix your problem.
Transmitted via Bacon
Click to expand...
Click to collapse
I tried all modems because the lolipop modems didnt work for me! I started from the new one in the list and finished with the oldest
As i said only cm-12-20150106-NIGHTLY-bacon work now, but if you'll turn on "adaptive backlight" - it will crash like other roms. It works because "adaptive backlight" is disabled by default.
Is it possible to edit cm12 nightly zip file to disable adaptive backlight (maybe some kind of config file) and flash after that?
b0r0d1nsky said:
I tried all modems because the lolipop modems didnt work for me! I started from the new one in the list and finished with the oldest
As i said only cm-12-20150106-NIGHTLY-bacon work now, but if you'll turn on "adaptive backlight" - it will crash like other roms. It works because "adaptive backlight" is disabled by default.
Is it possible to edit cm12 nightly zip file to disable adaptive backlight (maybe some kind of config file) and flash after that?
Click to expand...
Click to collapse
b0r0d1nsky said:
I tried all modems because the lolipop modems didnt work for me! I started from the new one in the list and finished with the oldest
As i said only cm-12-20150106-NIGHTLY-bacon work now, but if you'll turn on "adaptive backlight" - it will crash like other roms. It works because "adaptive backlight" is disabled by default.
Is it possible to edit cm12 nightly zip file to disable adaptive backlight (maybe some kind of config file) and flash after that?
Click to expand...
Click to collapse
There's no point in flashing the KitKat modems, they'll only cause the problem, not fix it. If the Lollipop modems didn't work for you, you're doing something wrong. Like maybe you're on the wrong firmware, you never answered my question asking which firmware you're on.
And no, you can't just edit the zip to remove the adaptive backlight feature, you'd need to fork the CM12 repo and remove that commit, and then build the ROM from source.
Transmitted via Bacon
timmaaa said:
ou never answered my question asking which firmware you're on.
Click to expand...
Click to collapse
i am on CM12 nightly (cm-12-20150106-NIGHTLY-bacon) now and i wanted to install the last nightly.
I found the solution - my friend with same OPOphone will disable "adaptive backlight" and he'll made TWRP backup, i'll flash it today.
thank you very much for help. :good:
UPD. Forgot to say - modem isn't the main reason, the adaptive backlite and my proximity sensor - are the problem... maybe sensor is broken
b0r0d1nsky said:
i am on CM12 nightly (cm-12-20150106-NIGHTLY-bacon) now and i wanted to install the last nightly.
I found the solution - my friend with same OPOphone will disable "adaptive backlight" and he'll made TWRP backup, i'll flash it today.
thank you very much for help. :good:
UPD. Forgot to say - modem isn't the main reason, the adaptive backlite and my proximity sensor - are the problem... maybe sensor is broken
Click to expand...
Click to collapse
The modem is the problem, the proximity sensor is governed by the modem. The way the proximity sensor is handled changed when they released Lollipop. Adaptive backlight has absolutely nothing to do with it, you're mistaking a symptom of the problem for the cause. Of course adaptive backlight is going to cause problems, it relies on your proximity sensor, which in turn relies on the modem. The cause of the problem is the modem, without doubt. Hundreds of people have had the exact same problem.
Transmitted via Bacon
timmaaa said:
Hundreds of people have had the exact same problem.
Transmitted via Bacon
Click to expand...
Click to collapse
but all that people solved this problem by flashing lollipop modem... why it doesn't helped me?
ok, lets start again
1) I had cm 11S
2) installed TWRP
3) flashed cm12 nightly from official site
4) i tried to flash other lollipop roms from xda
5) after all faults i returned to cm 11S
6) I posted my problem here
7) now I am on cm-12-20150106-NIGHTLY-bacon - it works... but if i'll go to settings -> screen and will enable the adaptive backlight - it will cause same problem!
b0r0d1nsky said:
but all that people solved this problem by flashing lollipop modem... why it doesn't helped me?
ok, lets start again
1) I had cm 11S
2) installed TWRP
3) flashed cm12 nightly from official site
4) i tried to flash other lollipop roms from xda
5) after all faults i returned to cm 11S
6) I posted my problem here
7) now I am on cm-12-20150106-NIGHTLY-bacon - it works... but if i'll go to settings -> screen and will enable the adaptive backlight - it will cause same problem!
Click to expand...
Click to collapse
That isn't what you said in your initial post. This is what you said:
Didn't work for me.
1)Backup cm11s
2)Full wipe
3)Flashed from 11S to cm12 nightly
4)Flashed the 44S radio
inf:
opo 64Gb ver.
TWRP 2.8.5.1
Click to expand...
Click to collapse
In your first you went from CM11S to CM12 nightly and flashed an incompatible modem. Now you're telling me you went from CM11S to CM12 nightly to other ROMs and back to CM11S. Completely different scenarios. So which is it? It turns out you haven't been very accurate or specific with your information. I'm still waiting for you to answer my question about which firmware you're on (this is the third time I'm asking). If you can't even provide accurate and specific information about what you've done, then you can't expect anyone to be able to help you effectively.
So maybe it's better to ask this way; exactly which ROM do you want to be on? You tell me that and I'll give you links to the correct firmware and modem(s).
Transmitted via Bacon
Related
Q&A for [ROM][5.0]+[4.4.4][Official][Nighties]VanirAOSP Lollipop Alpha 3
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.0]+[4.4.4][Official][Nighties]VanirAOSP Lollipop Alpha 3. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
help
I dont have root. To take this one i have to?
Sorry, have been busy lately.
As of today, you will have two options:
You can use the version vanir_bacon_5.0.0.120214.zip that will have working root buildin but a permissive SELinux (and therefore there is some risk of something invading your system) or you can use the version vanir_bacon_5.0.0.120214.enforced.zip and install SuperSU afterwards...
I am totally stock ROM and recovery.
Can I just download Vanir Rom and Gapps to phone and then:
1: wolume+ and powerbotton
2: wipe data
3: install Vanir zip
4: install Gapps zip
Finished......
Or I am totally on the wrong way ?
Printet on OnePlus One
ZoNe_dk said:
I am totally stock ROM and recovery.
Can I just download Vanir Rom and Gapps to phone and then:
1: wolume+ and powerbotton
2: wipe data
3: install Vanir zip
4: install Gapps zip
Finished......
Or I am totally on the wrong way ?
Printet on OnePlus One
Click to expand...
Click to collapse
you need to install custom recovery first
http://forum.xda-developers.com/showthread.php?t=2788632
There is no face unlock feature in smart lock menu. Someone told me to flash a different version of gapps to fix it. Can I dirty flash a different version or should I do it after wiping data?
Thanks.
Sent from my A0001 using XDA Free mobile app
agentinani047 said:
There is no face unlock feature in smart lock menu. Someone told me to flash a different version of gapps to fix it. Can I dirty flash a different version or should I do it after wiping data?
Thanks.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
You can try without wiping data: just wipe system, dalvik and cache partitions, flash your ROM, flash gapps, reboot.
for everyone who wants to change the settings for the notification bar weather: just add a "cLock" widget and set everything up there. :good:
i'm on vanir 5.0.2 (problem with xpose mod)
I just wanted to know why xpose module is not working on this rom.
whenever i run xpose mod it says ur version of android is not suported.
wat to do??
deb1806 said:
I just wanted to know why xpose module is not working on this rom.
whenever i run xpose mod it says ur version of android is not suported.
wat to do??
Click to expand...
Click to collapse
Xposed does not work with ART. You'll have to go back to a 4.4.4 ROM, where dalvik cache is enabled.
cam30era said:
Xposed does not work with ART. You'll have to go back to a 4.4.4 ROM, where dalvik cache is enabled.
Click to expand...
Click to collapse
sorry for being a noob.. i jst forgot dat 5.o is ART .
any alternative of xpose for 5.0
deb1806 said:
sorry for being a noob.. i jst forgot dat 5.o is ART .
any alternative of xpose for 5.0
Click to expand...
Click to collapse
No need to apologize. Everyone was a noob once. I think you'll have to wait until the developer updates xposed to work with ART. I can't imagine it'll be long. If you search XDA you might even find a thread.
You can get the buildprop editor from the play store too. I use 401 dpi
so I had this rom and worked perfectly and almost without bugs (version 122914) and now in the last version the wifi is working very badly and does not connect correctly, gives authentication error. Anyone knows how to fix it? thanks in advance
joseka22 said:
so I had this rom and worked perfectly and almost without bugs (version 122914) and now in the last version the wifi is working very badly and does not connect correctly, gives authentication error. Anyone knows how to fix it? thanks in advance
Click to expand...
Click to collapse
Upon further research, it is confirmed that Vanir ROM does NOT include any modem files. Sorry for the previous misinformation.
I just flashed it and got caught in a bootloop I turned it off but it finally booted because (and I dont know the reasoning behind how it works, I just know it worked) I booted into fastboot and then reboot it that way and it works.
EDIT: It only works when you have a usb plugged and when you unplug it it reboots.
Will flashing a new kernel like AK fix this problem?
elpiggo said:
I just flashed it and got caught in a bootloop I turned it off but it finally booted because (and I dont know the reasoning behind how it works, I just know it worked) I booted into fastboot and then reboot it that way and it works.
EDIT: It only works when you have a usb plugged and when you unplug it it reboots.
Will flashing a new kernel like AK fix this problem?
Click to expand...
Click to collapse
That's an odd problem... Did you clean flash?
rudi_j7 said:
That's an odd problem... Did you clean flash?
Click to expand...
Click to collapse
Yeah I came from stock and wiped everything. The Rom would only run if usb debugging was enabled and when I tried to reboot into recovery, it wouldnt let me unless i selected recovery from the power menu, then waited until the twrp logo showed up, then unplugged it. Otherwise it would just reboot into the rom
Latest vanir has a kernel that needs latest firmware to work.
Our Exodus has a kernel that works with normal firmware so you might want to use this.
And you should maybe stay away from CM's new firmware as we got informed that at least find7 seems to hardbrick with the newest firmware and find7 is very close to bacon...
Martin_Ro said:
Latest vanir has a kernel that needs latest firmware to work.
Our Exodus has a kernel that works with normal firmware so you might want to use this.
And you should maybe stay away from CM's new firmware as we got informed that at least find7 seems to hardbrick with the newest firmware and find7 is very close to bacon...
Click to expand...
Click to collapse
I have insalled 13.01 nightly CM12 and I don't have any problems. No bootlops, no brick. Not tried today nightly yet.
i tried to update my opo 64gb from 33r to 38r by ota when it asks me to
but when it reboots in recovery(twrp in my case, i'm rooted and i have twrp recovery nothing else, neither xposed or things like that) it gives me error about updater binary if i'm not wrong
then i reboot to system and obviously it remain 33r
how can i solve this problem?
i read of people that get the same error and cant even flash other zips...
Updating your recovery to the latest TWRP (2.8.1.0) should solve your problem.
It's a known issue.
What's the exact error you get please?
Transmitted via Bacon
babbo96 said:
i tried to update my opo 64gb from 33r to 38r by ota when it asks me to
but when it reboots in recovery(twrp in my case, i'm rooted and i have twrp recovery nothing else, neither xposed or things like that) it gives me error about updater binary if i'm not wrong
then i reboot to system and obviously it remain 33r
how can i solve this problem?
i read of people that get the same error and cant even flash other zips...
Click to expand...
Click to collapse
if your rooted why are messing around with an ota anyways. Download one of Calkulins completely stock zips and your done
timmaaa said:
What's the exact error you get please?
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah we need the exact error to see what's going on. Other than that, ota zip flashing with twrp will work but u might have to manually select the zip...
Download the ota zip yourself into your phone is available in a thread here somewhere search for it, reboot into recovery, select "install zip", browse to the correct ota zip, swipe to flash, clear dalvik then clear cache.
//edit
Just saw you're on 33r. Download ota zip for 38r and 44s. Make sure you flash them in the correct order don't mix them up!
Sent From Bacon
solved flashing via fastboot factory images with bacon root toolkit(i'm lazy :silly of 33r to see if it would update it and it did
i flashed 38r ota and 44s one as well
anyway i'm considering flashing cm11 stable builds...is there the option for slowmotion and othe things like gesture on off screen?
babbo96 said:
solved flashing via fastboot factory images with bacon root toolkit(i'm lazy :silly of 33r to see if it would update it and it did
i flashed 38r ota and 44s one as well
anyway i'm considering flashing cm11 stable builds...is there the option for slowmotion and othe things like gesture on off screen?
Click to expand...
Click to collapse
CM11 doesn't come with the CameraNext camera so you need to install the apk manually, but once you do that you will have full functionality. It has all gestures.
A word of advice: don't be lazy, stay away from toolkits. Firstly, they're unreliable and I've seen them cause many issues for people. Secondly, the experience you gain from using fastboot and adb manually is priceless.
Transmitted via Bacon
I think cm11s 44s is ahead of cm snapshots in terms if fixes and stuff so I would stick with that then go to a custom kernel for further updates past 44s kernel
And I totally agree with timmaaa I learned about flashing etc on this phone from his threads and posts lol trust me a one click app won't help when things hit the fan... But do as you want, I wanted to learn the proper way
Sent From Bacon
ek69 said:
I think cm11s 44s is ahead of cm snapshots in terms if fixes and stuff so I would stick with that then go to a custom kernel for further updates past 44s kernel
And I totally agree with timmaaa I learned about flashing etc on this phone from his threads and posts lol trust me a one click app won't help when things hit the fan... But do as you want, I wanted to learn the proper way
Sent From Bacon
Click to expand...
Click to collapse
i know how to use fastboot(i'm not a genius but i know how to use it basically)
the fact is that i didnt know how to flash factory images so i used it. and i also learned how to do it couse i read the log of toolkit...
FASTBOOT FLASH (modem/system/recovery/logo/etc...) modem/system/recovery/logo/etc.img
timmaaa said:
CM11 doesn't come with the CameraNext camera so you need to install the apk manually, but once you do that you will have full functionality. It has all gestures.
A word of advice: don't be lazy, stay away from toolkits. Firstly, they're unreliable and I've seen them cause many issues for people. Secondly, the experience you gain from using fastboot and adb manually is priceless.
Transmitted via Bacon
Click to expand...
Click to collapse
so gesture of music(2 fingers to play/pause, right/left arrow to change song), circle for camera and doubletap2wake are present also in cm11 non-S stable?
are they better then cm11s in terms of stability and smoothness?
could you also suggest me a good kernel?
babbo96 said:
so gesture of music(2 fingers to play/pause, right/left arrow to change song), circle for camera and doubletap2wake are present also in cm11 non-S stable?
are they better then cm11s in terms of stability and smoothness?
could you also suggest me a good kernel?
Click to expand...
Click to collapse
Yes, all of the gestures are present. It's essentially the exact same ROM but without the fancy lockscreen and camera. The main difference being that it receives merged fixes and commits sooner than CM11S. The best kernel? Stock.
Transmitted via Bacon
Hi Friends
The power button on my device does not unlock my phone (it is working well otherwise) also If I try to unlock using double tap to wake up, it does not happen. Here is what I did before this problem started:
I had stock CM11s (bootloader unlocked + rooted+TWRP), I backed up the ROM using TWRP. Then, I wanted to try out a few ROMs and hence I flashed MIUI Patchrom, then after using it for a few hours I flashed ColorOS by relic242, I used it for a day and then I flashed LiquidSmooth Lollipop current build. Then in the end I restored my CM11s using the TWRP restore. My oneplus logo is now red, please help me undo this. Also, I am having the unlocking problem which I described above + the oneplus logo at boot of my device is now red in color. please help.
Update: If I turn "prevent accidental wake up" off, the power button and double tap works, but if I turn it on these doesn't. Still buggy ! During calls the screen is always off, seems like there is a problem with the proximity sensor, which was not there earlier. Maybe after flashing any of those ROMs?
Thanks !
You're gonna need to flash the fastboot images to go back to being fully stock, go to my guide thread and look at section 8 for instructions.
Transmitted via Bacon
timmaaa said:
You're gonna need to flash the fastboot images to go back to being fully stock, go to my guide thread and look at section 8 for instructions.
Transmitted via Bacon
Click to expand...
Click to collapse
Can I flash the modem only ?
xyz_1232005 said:
Can I flash the modem only ?
Click to expand...
Click to collapse
when he clearly declares "fully stock" then you will need to flash ALL images ...
or what do you mean when he sais fully stock?
xyz_1232005 said:
Can I flash the modem only ?
Click to expand...
Click to collapse
No. What on earth.would flashing the modem accomplish anyway? It wouldn't accomplish anything, it's entirely unrelated to your problem. You need a clean slate, flash the fastboot images.
Transmitted via Bacon
timmaaa said:
No. What on earth.would flashing the modem accomplish anyway? It wouldn't accomplish anything, it's entirely unrelated to your problem. You need a clean slate, flash the fastboot images.
Transmitted via Bacon
Click to expand...
Click to collapse
It's not neccesary true. On CM11 we need cm11 compatible modem, on cm12 - cm12 compatible modem. Wrong modem causes problem with screen off/on, he can try to flash compatible modem only and see if it helps
Flashing Modem Works !
I flashed the CM11s Modem and it worked ! Thanks guys !
Flashing the modem worked for me also! I was facing the exact same problem due to trying new CM 12 nightlies.
I've done some searching around, and can't really find anyone else that is having quite the same problem as me. So, I'm running CM12 Nightlies on my One. After I upgraded from stock, everything worked flawlessly. But now, whenever I try to update it to a new nightly, it gets stuck in a bootloop. The only way I've found to get it to update without the bootloop is to wipe the whole system. Which is getting a little annoying having to reinstall my apps and stuff every day. I've found a few work arounds, like making a backup through TWRP, updating, then restoring just the data of the backup. But I'd like to be able to just update it without having to go through all that trouble. I don't know if I'm the only one having this specific issue, or if it's a CM12 issue. Any help would be great.
Have you tried using CyanDelta?
https://play.google.com/store/apps/details?id=com.cyandelta
Transmitted via Bacon
Its also possible there are firmware differences. I have read about some new firmware pushes in the nighties. I am currently on Bliss and we have to flash updated files to keep up with the cm commits. It could be that because your dirty flashing its causing an issue. Perhaps do a backup of data, install latest. And restore data is your best bet.
Sent from my A0001 using Tapatalk
timmaaa said:
Have you tried using CyanDelta?
Transmitted via Bacon
Click to expand...
Click to collapse
Tried that earlier today, didn't help anything.
gmac1990 said:
Its also possible there are firmware differences. I have read about some new firmware pushes in the nighties. I am currently on Bliss and we have to flash updated files to keep up with the cm commits. It could be that because your dirty flashing its causing an issue. Perhaps do a backup of data, install latest. And restore data is your best bet.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yeah, I think that might be my best bet. I guess it's better than nothing, haha. Thanks for you answers guys.
It probably is due to not having updated firmware. Which nightly? Wipe everything and flash the most recent nightly or go to blisspop thread and find the updated firmware zip it's around 30mb and flash that. It should fix your boot loop issues
Sent From Lollipopified Bacon Goodness!
The firmware can be found here:
http://www.vanir-exodus.net/exodus/bacon/
Transmitted via Bacon
Thanks for the help guys. That most likely would have been the issue. But, alas, I ended up soft bricking (still not sure how), and now I'm back to stock. I'll probably stick here until a more stable Lollipop ROM is out.
Skizwack said:
Thanks for the help guys. That most likely would have been the issue. But, alas, I ended up soft bricking (still not sure how), and now I'm back to stock. I'll probably stick here until a more stable Lollipop ROM is out.
Click to expand...
Click to collapse
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon
timmaaa said:
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon
Click to expand...
Click to collapse
I suppose that may have been my problem all along. The main problems I was having were just little bugs (system UI very rarely crashing, and a couple other minor annoyances), but I guess those could have been caused by having the wrong firmware. Maybe I'll give it another go soon. Now that I'm all settled in to CM11S, haha. Thanks again!
Has anyone else had any issues with the automated download and install feature in the CM12 settings? Mine will download the night lies and even automatically boot into TWRP but it doesn't flash?
timmaaa said:
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon
Click to expand...
Click to collapse
So, I'm still having this issue. I flashed the new firmware yesterday, and I went back and installed CM12 (the 1-28-15 nightly). Just now I tried updating it to the 1-29-15 nightly with CyanDelta, and it's doing the exact same thing again. Any other suggestions? Did I flash the firmware in the wrong order?
Skizwack said:
So, I'm still having this issue. I flashed the new firmware yesterday, and I went back and installed CM12 (the 1-28-15 nightly). Just now I tried updating it to the 1-29-15 nightly with CyanDelta, and it's doing the exact same thing again. Any other suggestions? Did I flash the firmware in the wrong order?
Click to expand...
Click to collapse
which recovery and version are you using?
playya said:
which recovery and version are you using?
Click to expand...
Click to collapse
TWRP 2.8.4.1
Skizwack said:
TWRP 2.8.4.1
Click to expand...
Click to collapse
What's the name of the firmware file you flashed?
Transmitted via Bacon
timmaaa said:
What's the name of the firmware file you flashed?
Transmitted via Bacon
Click to expand...
Click to collapse
bacon_firmware_update_2015_01_16.zip, from that link you gave me before.
Skizwack said:
I've done some searching around, and can't really find anyone else that is having quite the same problem as me. So, I'm running CM12 Nightlies on my One. After I upgraded from stock, everything worked flawlessly. But now, whenever I try to update it to a new nightly, it gets stuck in a bootloop. The only way I've found to get it to update without the bootloop is to wipe the whole system. Which is getting a little annoying having to reinstall my apps and stuff every day. I've found a few work arounds, like making a backup through TWRP, updating, then restoring just the data of the backup. But I'd like to be able to just update it without having to go through all that trouble. I don't know if I'm the only one having this specific issue, or if it's a CM12 issue. Any help would be great.
Click to expand...
Click to collapse
have tried different version TWRP?
Skizwack said:
bacon_firmware_update_2015_01_16.zip, from that link you gave me before.
Click to expand...
Click to collapse
What about when you download the whole ROM zip from the CM site?
geowolf1000 said:
have tried different version TWRP?
Click to expand...
Click to collapse
The version he's on is fine.
timmaaa said:
What about when you download the whole ROM zip from the CM site?
Click to expand...
Click to collapse
I think I tried that before. Even if I downloaded that and flashed it from recovery (without wiping anything first), it would do the same thing.
I know it's best to not dirty flash, but my main reason I want to figure this out is because I use Google Music All Access. And every time I wipe my system I have to re-download all my music.
Skizwack said:
I think I tried that before. Even if I downloaded that and flashed it from recovery (without wiping anything first), it would do the same thing.
I know it's best to not dirty flash, but my main reason I want to figure this out is because I use Google Music All Access. And every time I wipe my system I have to re-download all my music.
Click to expand...
Click to collapse
Dirty flashing should be fine if you're just updating the same ROM. Do you check the md5 when you download the file? They might be getting corrupt during the download.
timmaaa said:
Dirty flashing should be fine if you're just updating the same ROM. Do you check the md5 when you download the file? They might be getting corrupt during the download.
Click to expand...
Click to collapse
If I remember right, I do. I'm on the latest version now though, so I can't really test it. When a new one comes out tomorrow I'll give it a go and see what happens.
No matter what cm 12.1/5.1 roms I flashed, the gyroscope sensor isn't working. If I flashed back to cm 12.0 roms or lower, it works again. What could be the issue?
sseng587 said:
No matter what cm 12.1/5.1 roms I flashed, the gyroscope sensor isn't working. If I flashed back to cm 12.0 roms or lower, it works again. What could be the issue?
Click to expand...
Click to collapse
Revert to some other cm12.1 build nightly instead or flash latest nightly build
May be it's a problem associated with that build
I tried other 12.1 rom, same results. Cm 12.0 is fine though.
Fixed. I fastboot flashed the firmware partition.
take the files out the firmware.zip
and use the steps (8. How To Flash The Cyanogen OS Fastboot Images) from this link
edit: I found the steps! http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the files you extracted from the firmware zip
I have this issue too ... Brand new OnePlus One, put TWRP on it, flashed the latest CyanogenMod 12.1 nightly. Looks like rotation is not working and when I look at apps that show pitch and roll values they are seemingly not getting output from the sensors.
I see that you fixed yours ... But what is this problem from? Did the 12.1 ROM come bundled with bad firmware or something?
When I flash a ROM, maybe I'm ignorant, but I presume that the right and proper firmware and radios are bundled in.
Any advise OP?
Cheers!
cg6ry79m
[email protected] said:
I have this issue too ... Brand new OnePlus One, put TWRP on it, flashed the latest CyanogenMod 12.1 nightly. Looks like rotation is not working and when I look at apps that show pitch and roll values they are seemingly not getting output from the sensors.
I see that you fixed yours ... But what is this problem from? Did the 12.1 ROM come bundled with bad firmware or something?
When I flash a ROM, maybe I'm ignorant, but I presume that the right and proper firmware and radios are bundled in.
Any advise OP?
Cheers!
cg6ry79m
Click to expand...
Click to collapse
Depends on the ROM you flashed. I usually flash the firmware separately and never had issues.
https://www.androidfilehost.com/?fid=23991606952604019
Flash this for CM12.1
Flashed that firmware ROM ... Seemed to go in just fine ... But no joy. Still no rotation/gyro function. Any ideas? Sure would like to fix that.
cg6ry79m
[email protected] said:
Flashed that firmware ROM ... Seemed to go in just fine ... But no joy. Still no rotation/gyro function. Any ideas? Sure would like to fix that.
cg6ry79m
Click to expand...
Click to collapse
Same problem here, I think the problem is located in the firmware. So it is something that CM will have to modify. Because the latest firmware (like the one in the zip) is also included in the latest nightly builds.
If rotation is something you need badly you can try the following 2 options:
- use an app to do the rotation like: playstore:rotation manager
- flash the stock CM11 and the accompaning firmware back, reflash the firmware in attachement and then reflash the CM12.1 nightly. (untested)
[email protected] said:
Flashed that firmware ROM ... Seemed to go in just fine ... But no joy. Still no rotation/gyro function. Any ideas? Sure would like to fix that.
cg6ry79m
Click to expand...
Click to collapse
Little update ... Rotation seemed to work for a minute but has since stopped. Frustrating.
Same issue here, all sensors are shown to be off by Sensor Kinetics from Play Store.
Flashing everything from the factory restore image via fastboot did not help...
I have been troubleshooting the issue of rotation/orientation sensors seemingly not working. What I have found on my new OnePlus One, running the latest CyanogenMod 12.1 nightly builds is this:
Once I root the device using SuperSu I cannot regain use of the sensors/auto-rotate. I use the app named Phone Tester and after the phone is rooted the comps/orientation sensors show no output.
If I unroot the phone and reboot several times, the orientation subsystem functionality returns.
No matter what firmware/Cyanogen ROM combination I use the result is the same.
I wonder if anyone else can confirm that their screen rotation ceases to function when the phone is rooted.
Cg6ry79m
davebugyi said:
Depends on the ROM you flashed. I usually flash the firmware separately and never had issues.
https://www.androidfilehost.com/?fid=23991606952604019
Flash this for CM12.1
Click to expand...
Click to collapse
Nooby question ... Doesn't the Cyanogen Nightly that I flash contain the device's firmware also? So if I flash the firmware file above separately, will it not be replaced by the next nightly that I flash? Should I tell TWRP to flash both items every time?
Before, I flashed that firmware that is mentioned above. ... But I feel like maybe it was superseded when I flashed a nightly.
Educate me.
cg6ry79m
[email protected] said:
Nooby question ... Doesn't the Cyanogen Nightly that I flash contain the device's firmware also? So if I flash the firmware file above separately, will it not be replaced by the next nightly that I flash? Should I tell TWRP to flash both items every time?
Before, I flashed that firmware that is mentioned above. ... But I feel like maybe it was superseded when I flashed a nightly.
Educate me.
cg6ry79m
Click to expand...
Click to collapse
Yes, the nightly contains and will overwrite your firmware. When going from CM to a different ROM, you don't have to flash the firmware again. As long as the android version is the same ofcourse.
Abiut your problem, do you use Superuser or SuperSU? Make sure you flash the latest SuperSU zip. More people had problems with the built in one from TWRP
Sent from my A0001 using XDA Free mobile app
cantthinkofagoodname said:
Yes, the nightly contains and will overwrite your firmware. When going from CM to a different ROM, you don't have to flash the firmware again. As long as the android version is the same ofcourse.
Abiut your problem, do you use Superuser or SuperSU? Make sure you flash the latest SuperSU zip. More people had problems with the built in one from TWRP
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah I had used the latest SuperSU. The problem persists even when I don't use SuperSU though. I feel like it is some sort of race condition as processes kick off during boot or something.
I wish I wasn't relying on voodoo to get the accelerometer/auto-rotate to work.
cg6ry79m
sseng587 said:
Fixed. I fastboot flashed the firmware partition.
take the files out the firmware.zip
and use the steps (8. How To Flash The Cyanogen OS Fastboot Images) from this link
edit: I found the steps! http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the files you extracted from the firmware zip
Click to expand...
Click to collapse
Yes! Thank you this worked. Was getting really annoyed by this issue, thought I was gonna be stuck on 5.02 forever. Tried flashing different nightlies, different modems...
Flashed everything from the 20150505 Firmware, the first 8 steps in the guide quoted above. For some reason flashing each file manually works as opposed to flashing the zip with all of them- odd, but hey whatever works...
Great thanks that worked!!
Sent from my A0001 using Tapatalk
I wanted to close out this issue as I believe it has been resolved. This problem was also a case of TWRP not correctly flashing the firmware. I "downgraded" from the X.X.0.7 TWRP to that X.X.0.6 version that others have posted links to in other threads. Frankly the GUI on this version is better.
So I downgraded TWRP, reflashed the 9 July Cyanogen nightly build. Accelerometer, compass, and proximity sensor working fine. Survived reboots. Survived new nightly.
Thanks to you folks who posted the issue about TWRP not flashing firmware correctly.
cg6ry79m
sseng587 said:
Fixed. I fastboot flashed the firmware partition.
take the files out the firmware.zip
and use the steps (8. How To Flash The Cyanogen OS Fastboot Images) from this link
edit: I found the steps! http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the files you extracted from the firmware zip
Click to expand...
Click to collapse
i have issue with gyroscope like this video:
https://www.youtube.com/watch?v=cXsB2LG1ftM
Thanks for this method but not working for me!
could you give me more detail working firmware
i try 8 step in fastboot mode with 20150515 and 20150518 firmware but the issue still here!
Which version of twrp do you use? And did you flash the latest su?
Sent from my A0001 using Tapatalk
davebugyi said:
Depends on the ROM you flashed. I usually flash the firmware separately and never had issues.
https://www.androidfilehost.com/?fid=23991606952604019
Flash this for CM12.1
Click to expand...
Click to collapse
sseng587 said:
Fixed. I fastboot flashed the firmware partition.
take the files out the firmware.zip
and use the steps (8. How To Flash The Cyanogen OS Fastboot Images) from this link
edit: I found the steps! http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the files you extracted from the firmware zip
Click to expand...
Click to collapse
Thaks guys it worked for me
Cheers!