I'm on CyanogenMod 12.1 Nightly 2015.07.03 The auto rotate does not work what so ever. It worked in previous ROMs. I downloaded a app that calibrates the gyroscope and accelerometer, and it showed no values for x,y, and z. To make sure it wasn't the app I downloaded another. Same result.
Anyone else have this problem?
I want to downgrade to a previous nightly(but not too far back) but I don't want to go flash down the list until it works.
Is there a fix?
If you are on a CM 12.1 nightly and your auto rotate works, can you reply with build date.
Thanks.
I'm struggling with this problem still. I have talked about it in another thread. I have tried everything short of going to another ROM provider (like Oxygen). It looks like it is actually the accelerometer and compass that are not starting up correctly.
The good news is that the auto-rotate does come back but I have not found the magic sequence that consistently revives it.
Generally when I re-flash the 20150515 firmware then reboot a couple of times to comes back. But that is no guarantee.
It is driving me crazy. It should be an easy fix (but what do I know).
The fact that it is intermittent and that multiple reboots or fresh/repeated ROM/firmware re-flashes bring the accelerometer/auto-rotate/compass subsystem back to life tells me it is not a hardware issue.
I beseech someone to look at this and get a fix or a consistent work around.
cg6ry79m
---------- Post added at 01:56 AM ---------- Previous post was at 01:29 AM ----------
P.s. ... Right after I wrote the reply above, I rebooted for like the 10th time and viola, the accelerometer/auto-rotate function returned to normal. It rarely survives a reboot though. And since I'm a compulsive CyanogenMod nightly flasher, I'll have the same issue tomorrow I'm sure.
I had the same problem, reflashing firmware files one by one in fastboot fixed the gyroscope permanently for me.
Chronzy said:
I had the same problem, reflashing firmware files one by one in fastboot fixed the gyroscope permanently for me.
Click to expand...
Click to collapse
Can you detail the process you used to get the accelerometer functioning again?
Do you have to reflash the firmware files with every nightly update?
What file are you using to get the firmware from? Standard nightly or from COS12/Oxygen?
Note: Just got the nightly working by doing what Chronzy said. I reflashed the following files from the latest nightly.
sbl1.mbn
emmc_appsboot.mbn
rpm.mbn
tz.mbn
logo.bin
static_nvbk.bin
boot.img
sdi.mbn
Perhaps you can shed some light as to which files are the exact ones needed?
micemicerabies said:
Can you detail the process you used to get the accelerometer functioning again?
Do you have to reflash the firmware files with every nightly update?
What file are you using to get the firmware from? Standard nightly or from COS12/Oxygen?
Note: Just got the nightly working by doing what Chronzy said. I reflashed the following files from the latest nightly.
sbl1.mbn
emmc_appsboot.mbn
rpm.mbn
tz.mbn
logo.bin
static_nvbk.bin
boot.img
sdi.mbn
Perhaps you can shed some light as to which files are the exact ones needed?
Click to expand...
Click to collapse
Good sounds like you got it working. It worked for me on every rom after I flashed the 20150505 firmware. In case you run into the problem again, or for anyone else looking for the fix:
Fastboot commands, #8: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the first 8 commands listed; do not need system, boot, cache, or recovery. Those might wipe your phone. Not sure exactly which one does the trick out of the first 8.
20150505 firmware: https://www.androidfilehost.com/?fid=23991606952597817
Chronzy said:
I had the same problem, reflashing firmware files one by one in fastboot fixed the gyroscope permanently for me.
Click to expand...
Click to collapse
Chronzy said:
Good sounds like you got it working. It worked for me on every rom after I flashed the 20150505 firmware. In case you run into the problem again, or for anyone else looking for the fix:
Fastboot commands, #8: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the first 8 commands listed; do not need system, boot, cache, or recovery. Those might wipe your phone. Not sure exactly which one does the trick out of the first 8.
20150505 firmware: https://www.androidfilehost.com/?fid=23991606952597817
Click to expand...
Click to collapse
I DL'd a copy of the 20150505 just in case.
I tried flashing the firmware that came from CyanogenOS12 from Oneplus using the above method and have also had success.
What is the difference between their firmware and the cm-nightly firmware? It seems like using the stock firmware would offer more stability for the rom though I could be wrong.
Can this be marked as solved? or do we need to wait for the OP's success?
I'd be interested in knowing if you flash nightly builds and if this "fix" survived nightly build flashes. It all seems way to voodoo to me. I am surprised this is still an issue. Mine still fails randomly and a series of voodoo actions and reboots usually bring it back ... But no consistent sequence works for me.
Do the fixes noted above survive reboots for you folks?
[email protected] said:
I'd be interested in knowing if you flash nightly builds and if this "fix" survived nightly build flashes. It all seems way to voodoo to me. I am surprised this is still an issue. Mine still fails randomly and a series of voodoo actions and reboots usually bring it back ... But no consistent sequence works for me.
Do the fixes noted above survive reboots for you folks?
Click to expand...
Click to collapse
So far this has fixed the autorotate issue for me and does survive reboots.
I have flashed these files from OxygenOS, COS12 and the CM nightly with success.
On a strange note my NFC is acting up now. This could be due to me screwing around too much. Im going to clean flash everything and try again. I want to find the perfect mix to get everything working.
Finally! I only flashed latest bacon firmware and auto rotate is working after 4 months.
http://forum.xda-developers.com/one...oneplus-one-modem-collection-t2858734/page108
Related
I tried the CM updater, like I have been for the nightlies, except, now I'm stuck and a bootloop and I can't get into recovery. I go from the bootloader and select recovery and it takes me to the same screen that the updater does where it says:
Updating partition details....
Running boot script....
Finished running boot script.
Installing zip file '/sdcard/cmupdater/cm-10-20121110-NIGHTLY-evita.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
This is the screen I get every time I flash nightlies, then I reboot and my phone boots normally, but, now when I do this, it puts me in a bootloop (HTC screen comes up, goes dark, no Cyanogen screen, then reboots to the HTC screen and goes to a dark screen...you get the point)...any thoughts on what I need to do to get my phone to work again?
CM10 Nightlies 20121110
First of all I love CM but Ive been having an issue with it. Ok so I flash the rom everything goes fine as far as that goes but Im having call issue. I can hear the person Im calling but that person cannot hear me. When I put the caller on speaker I cant hear him and that person still cant hear me, then the phone freezes. Im no developer but i have flashed plenty of roms so Im literate to this stuff. Some help or tips would be great as I love CM10 and havent been able to use any CM10 based roms they all do the same. I have an At&t One X unlocked, rooted, unlocked bootloader 1.14...
Rising32 said:
First of all I love CM but Ive been having an issue with it. Ok so I flash the rom everything goes fine as far as that goes but Im having call issue. I can hear the person Im calling but that person cannot hear me. When I put the caller on speaker I cant hear him and that person still cant hear me, then the phone freezes. Im no developer but i have flashed plenty of roms so Im literate to this stuff. Some help or tips would be great as I love CM10 and havent been able to use any CM10 based roms they all do the same. I have an At&t One X unlocked, rooted, unlocked bootloader 1.14...
Click to expand...
Click to collapse
Try flashing the previous boot.img then install the latest nightly. I've seen a few people have problems and that normally fixes it.
If that doesn't fix, re download the latest nightly and flash it. Could be a bad dl
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
I had the same problem just like u. I flashed back to 1109.
Sent from my One X using xda app-developers app
So every time I get a newer version of CM10 do I need to flash the boot.IMG first then flash the ROM or is it OK just to flash the ROM with my existing boot.IMG? I mean does the boot.IMG change? I have been just flashing the zip file without the boot.IMG just keeping the original boot.IMG from one of last months update.
Sent from my One X using xda app-developers app
always flash boot.img with any new build, unless your using a custom kernel
cm10 call issue
Myrder said:
Try flashing the previous boot.img then install the latest nightly. I've seen a few people have problems and that normally fixes it.
If that doesn't fix, re download the latest nightly and flash it. Could be a bad dl
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
Click to expand...
Click to collapse
So ur saying flash the previous nightly's boot image??? Thanks if that's the case then I will try it and report back. I've tried several CM10 based Rome they all have the same issue... Is it just my phone??? Is it something in the CM code that needs to be fixed? I mean one Rom is one thing but every one Ive tried so far lol. That's what I get for loving asp lol.
---------- Post added at 02:49 AM ---------- Previous post was at 01:52 AM ----------
Myrder said:
Try flashing the previous boot.img then install the latest nightly. I've seen a few people have problems and that normally fixes it.
If that doesn't fix, re download the latest nightly and flash it. Could be a bad dl
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
Click to expand...
Click to collapse
Well I tried ur suggestion and nothing... re-downloaded the lates nighty and used previous boot image, nothing. Wiped cache and reflashed the rom and still nothing.
Hi all,
Did anyone able to use gps with custom rom ( I would say CM base). I research and try everything that's I could find here but not success.
Every time I do clean wipe everything including a internal storage. So that will nothing left behind.
I know that stock is work fine with gps. some said that install and replace stock but I have no idea that what file will left in our device when we delete all.
Always had the same problem when running Paranoid Android (not tried other ROMs). Had to return to stock, where GPS runs fine. Would also love to kknow how people have got it functioning.
I am trying too. I modified gps.conf files, tried some workarounds mentioned in cm11 thread like restoring GPS Status backup from stock with titanium so far with no success. Some people say that it works but it doesn't on mine whatever I do.
I run on CM and I don't have any problem. Everything works fine with gps and I didn't use any fix or something similar.
I'm on CM 11-20140627 and I have 1032 phone.
Interesting, why does it work on some while it doesn't on others? Maybe some variants are having problems...
I have xt1033 asia version.
spajdo said:
I run on CM and I don't have any problem. Everything works fine with gps and I didn't use any fix or something similar.
I'm on CM 11-20140627 and I have 1032 phone.
Click to expand...
Click to collapse
Which recovery did you use?
CWM
As I wonder is about library missing or some partition need from stock ?
I've also been using the micro gapps package, would this matter?
I had problems with Paranoid Android and GPS too... If anyone know something about that, please comment!
TMaxtor said:
I had problems with Paranoid Android and GPS too... If anyone know something about that, please comment!
Click to expand...
Click to collapse
Hey i found a solution, you have do this flash following in this order.
- flash stock 4.4.4 (depend on your current)
- flash cm
- flash gapp
I try this twice and work like a charm.
Sent from my Moto G using XDA Free mobile app
thestory101 said:
Hey i found a solution, you have do this flash following in this order.
- flash stock 4.4.4 (depend on your current)
- flash cm
- flash gapp
I try this twice and work like a charm.
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
I am having he same problem on XT1032 running Carbon ROM. GPS worked fine on stock, no signal with Carbon.
I found many answers saying to flash stock and then reflash custom ROM. I will try it, but I wonder, how does this help? Isn't the phone restoring the whole system? Do I have to keep the gps.conf from stock?
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Did you wipe anything, like Dalvik, Cache and Data, or you just flashed it over?
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Sorry people, I was so happy to have my phone back working, I forgot to write it back here.
Yes it worked indeed, all I did was flashing back the stock, going outside to have a gps lock with gmaps, then re-flashing back the Carbon. I also kept a copy of the gps.conf, but I never needed it, the GPS got a fix quickly. Working fine so far, it only takes some tens of seconds to fix, from time to time.
I can't remember if I also did all the wiping, I think I didn't, but I made so many trials in a couple days, I am not sure.
Thanks a lot guys!
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Yes, this worked for me too on PA.
I couldn't even see a single sat (it wasn't just a lock problem). No matter with gps patch, gpx fix app, or gps.conf I used.
What I did?: Back to stock, lock GPS, flash again the custom ROM (but don't wipe /system!).
Good luck on that guys, it should work for you too.
thestory101 said:
Hi all,
Did anyone able to use gps with custom rom ( I would say CM base). I research and try everything that's I could find here but not success.
Every time I do clean wipe everything including a internal storage. So that will nothing left behind.
I know that stock is work fine with gps. some said that install and replace stock but I have no idea that what file will left in our device when we delete all.
Click to expand...
Click to collapse
GPS works fine on this unofficial CM11 rom for me. Stable daily driver rom for me, YMMV.
General advice is to:
- make sure you get a GPS lock on stock rom first
- flash CM11 (or other custom rom)
There may not be a file left on the device. it may just be that stock contains the code to initialize the GPS functionality on the SoC or chipset firmware. Whatever, it works...
Hello All,
I've been getting random reboots on my phone and just went ahead to take the kmsg. I'm not really sure how to go from here so any help would be great. The Kmsg is attached (slightly lengthy). Thanks!
Yeah mine has exactly the same problem. I can tell you that another kernel doesn't work. I've tried both the AK and the franco kernel. None seem sto change anything.
Apart from that - sometimes my phone is unable to enable WiFi or mobile data after crashing, and it won't work until I reboot it again. Maybe I should try another radio - are there updated versions out there?
I'll keep you updated if anything happens. Until then - Who can help out?
Thanks for responding! I'm not sure if I should start flashing different modems but I'd like to wait until someone with more experience on this places some input. I don't know if this is a hardware issue or a software one.
Update: The modem/radio of the Oppo Find 7 possibly did the trick. Haven't had any reboots since a couple of hours.
Maybe it works for you.
http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734
Edit: The reboots are back - didn't fix
xbenbox your kmsg actually points to the modem... Try reflashing it using one from the following thread and see if you have any luck.
[REF] [RADIO] OnePlus One Modem Collection
What ROM are you using? Yeah it points to the modem but your phone is having a kernel panic.
Have you tried other ROMs? Have you verified that the modem is the correct MD5 Hash?
MasterMind33 said:
xbenbox your kmsg actually points to the modem... Try reflashing it using one from the following thread and see if you have any luck.
[REF] [RADIO] OnePlus One Modem Collection
Click to expand...
Click to collapse
zephiK said:
What ROM are you using? Yeah it points to the modem but your phone is having a kernel panic.
Have you tried other ROMs? Have you verified that the modem is the correct MD5 Hash?
Click to expand...
Click to collapse
Thanks for the help guys. I was going to flash the modems but wanted to make sure that it would be okay before I did so. To be honest I'm not sure if it's the correct md5 hash. This phone shipped to me with stock 33R and I ended up putting 25R on it. I didn't do any changes to the modem after that. I haven't tried other roms yet since I'm hoping to stay with cm. Also I thought that other roms tend to use the roms from cm as well.
I flashed the 33r modem and it still seems to be restarting every once in a while. The kmsg read exactly the same as the one I posted before. Any chance that it's not the modem?
xbenbox said:
I flashed the 33r modem and it still seems to be restarting every once in a while. The kmsg read exactly the same as the one I posted before. Any chance that it's not the modem?
Click to expand...
Click to collapse
I am having SAME situation. I have this phone for a week, and sod-s every day. Two days ago phone restarts and now in the loop of logo 1+. Same error, MODEM time out.
Tried ROMS: Mahdi ,CM11
Kernels: Franco r18, r19, stock from both..
Can not get out of the loop.. I have wiped all partitions, formated all of them, clean flash of ever rom... nothing.
And yes, tried all modems...
Updated to 33R with the same rebooting issues although the kmsg now reads differently. Dalvik and Cache were wiped as well and same issue still occurs.
Still need help - bumping with my newest kmsg.
I doubt anyone on XDA has the solution to this problem. I would suggest for all others to go to Jira Cyanogenmod under the issue labeled Bacon-213 for progress checks and uploading last_ksmgs. This may be a hardware issue as not a lot of people are reporting having this issue.
Hello,
I am facing a weird problem regarding the proximity sensor on all CM11 roms.
I was using lollipop roms for a long time now, and have been following latest builds, until I decided that I liked KitKat more. I already had a backup of temasek's last CM11 build, so I reverted to that one, after flasing the cm11 firmware. All was working perfect until I reverted a backup of my 5.1.1 rom, to try xposed. Again, before doing so, I flashed the latest cm12 firmware. After a couple of days experimenting with xposed, I eventually went back to my kitkat rom. After boot, I noticed that the proximity sensor wasn't working. I had already flashed the cm11 firmware before restoring, but I went and flashed it again. Problem was still there. I then tried cm11s 44s firmware, 05Q firmware and 05Q modem only. The proximity sensor problem was there in all cases. (Shows 0.0cm, like I always have my phone in my ear or pocket). I then tried flashing a complete cm11s rom (05Q) with no success.
This is not a hardware problem, as the sensor is working FINE on ALL lollipop roms. I used sensor box in all my tests. I even tried proximity fix from play store, but it did nothing. I also tried to install it as secondary on multirom, then flash the firmware, but again, no success.
I really really need some help on this one, I can't troubleshoot it on my own, I am out of ideas.
Thanks in advance.
(My device is OnePlus one - always using boeffla kernel on both lollipop and kitkat roms.)
EDIT: Solved. Look at my last post.
Flash again only modem but matching http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734 I had the same problem, flashing again modem solved this issue for me.
chazxt said:
Flash again only modem but matching http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734 I had the same problem, flashing again modem solved this issue for me.
Click to expand...
Click to collapse
Hello,
Which modem did you flash from that thread? I have only tried the 44s from there but it was a no go.
Thanks in advance.
XNPH44S for me it worked
Hello,
Finally found a fix for my problem.
It seems that I had to flash from fastboot the CM11 nightly modem from here: http://forum.xda-developers.com/showpost.php?p=57125376&postcount=389
The process doesn't wipe anything in case anyone is wondering, it just flashes the modem ( NON-HLOS.bin)
Hello friends,
I had so many problems in the last days. I flashed the first INU 5.1.1 version on my G920I, after a few problems flashing TWRP. Finally I got the phone working and no major problems until last days when battery started to malfunction. Anyway, after that I tried to flash the latest INU 5.1.1 versión (G925IDVU2COGA_G925IODD2COGA_G925IDVU2COGA_HOME.tar) but the phone couldt start the Odin process. Then I tried anothers roms but nothing (all of them 5.1.1) after that Iflashed the TWRP and made a stupid "factory wipe" and then my device was softbricked.
The phone was on boot loop.. Finally, I splitted COGA rom in parts (modem.bin, cache, etc) and flashed system separated from the rest ROM. This worked but the only file that wasn't possible to load was sboot.bin cm.bin. Anyway, after that I tried to reflash COGA in one part but nothing. Finally I used the COF room (INU 5.1.1 from sammobile) and it was flashed full with noproblems via Odin but now my device has the TOUCH SENSOR INVERSED. whe I type in the right the letters on the left side of the keyboard are presssed.
By now I don't know what to do. Except that Im triying to flash a moded stock rom to get things fixed . I hope anyone could helpme because Im very worried.
Reflash again with stock 5.1.1 ROM via odin. Do full reset after
---------- Post added at 11:04 PM ---------- Previous post was at 11:01 PM ----------
http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
I just could make it happen. Odin and device don't let me flash but now im flashing again COF8. After flashin at least forty times different roms, and splitted most of them. I hope this help.
I have read that there's an option to make a "NAND erase all" along with flashing a stock ROM, to make a clean install after a messed up like this. If anyone could corroborate that. I have read most of the comments saying thats its a murder for the device but also some another good references, about making it wipe al that garbage from stupids flashings like mine.
andifds said:
I just could make it happen. Odin and device don't let me flash but now im flashing again COF8. After flashin at least forty times different roms, and splitted most of them. I hope this help.
I have read that there's an option to make a "NAND erase all" along with flashing a stock ROM, to make a clean install after a messed up like this. If anyone could corroborate that. I have read most of the comments saying thats its a murder for the device but also some another good references, about making it wipe al that garbage from stupids flashings like mine.
Click to expand...
Click to collapse
You must have flashed the wrong firmware initially. Thus giving you this problem. To fix just go into your dialer and hit *#2663# then tap tsp fw update (general) . That'll fix it all for you. Next time be careful when flashing things, I suspect you flashed something meant for one of the edge devices.