Hi there.
I have an issue with auto-rotation and wifi.
I'm running an Asus tf 101, currently running CM. Technical details at the end of the post.
My issue is that autorotate is no longer working on CM, which led me to try upgrading to the latest CM, but when I tried a clean install (wiped cache, wiped data, wiped davlik) neither the autorotate nor the wifi worked.
Restoring my previous backup worked, and I returned to the situation which had wifi working, but no autorotate.
My poor searching skills found issues with the latest ROMs and autorotate, but I couldn't find any mention of autorotate which failed.
I suspect that with my messing about with ROMs & Kernels I might have messed things up, potentially corrupting the Kernel that I've been using.
[UPDATE] to eliminate sensor failure I installed a sensor app which indicates that the tf101 is successfully getting the orientation information.
[Q] Where is the best place to go to learn how Kernels & ROMs interact that I might learn how to fix whatever my mistake was?
[Q] Has anyone else encountered this? Does it sound like something fixable?
If I am in the wrong place, I would love a nudge in the direction of the appropriate forum.
Thank you.
Details:
Android Version: 4/1/2
Kernel version 2/6/39/4-kat-gae9f1bb
[email protected] #56
Sun Nov 11 19:08:06 CET 2012
CyanogenMod Version
10-201222-Nightly-tf101
I can sort you out with a build date and number as well if it would be useful.
It's pretty hard to troubleshoot. I had the same problem so I moved away from CM10 and went with Team EOS' 4.2.1 (see my sig).
But from what I could gather through months of playing around, this sort of stuff happens when you upgrade from another version and "something goes wrong". It doesn't mean that your new updated rom won't work, but you may get unexpected results. How did you do your rom install process, and from which rom/version?
You could install a logcat or manually tail -f the log files then trigger the autorotate with an app, then see what happens in the logs then report back. Otherwise all I can suggest is to get your post count to 10 and post in that rom's thread to get further help.
Lethe6 said:
It's pretty hard to troubleshoot. I had the same problem so I moved away from CM10 and went with Team EOS' 4.2.1 (see my sig).
But from what I could gather through months of playing around, this sort of stuff happens when you upgrade from another version and "something goes wrong". It doesn't mean that your new updated rom won't work, but you may get unexpected results. How did you do your rom install process, and from which rom/version?
Click to expand...
Click to collapse
Was the problem fixed when you went to Team EOS?
I have been messing with the ROM, and at one point while downgrading to 9.1 the screen was stuck on the loading image for more than two hours, so I turned off and restored from backup, that might well have done something.
I'll look around for a logcat to install....
Thank you very much.
You can also try this:
- Turn off the device completely
- adb logcat (see this for more details)
- Boot the device
You'll get all the logs printed in adb so you can check for errors. Yes the problem was solved with Team EOS' rom. I get perfect wifi signal and auto-rotate works nicely, my only "problem" is that if it goes to sleep it doesn't detect the dock SD card until I reboot, but I can live with that!
Edit: Dock SD card issue fixed with Preview B128.
In the end I also moved to Team EOS, there are a few little quirks, but nothing I can't live without at this stage. Also my video playback has become significanly better.
Thank you for your help!
maybe software auto rotation can fix your problem
search on playstore....
gutlak...
Related
Hi! I realise this if my first post I'd like to tread lightly; but I'm about 4 days into solving my issues and I just want to finish it...
I've had my Nexus i9020a (bought from Koodo) since ~May 2012. I upgraded to ICS sometime in the summer and sometime in the last few weeks it has started rebooting. I hadn't been installing new apps, etc. I'm not sure what the cause is. I 'Factory Reset' today in an attempt to resolve the issue, thinking it may be a program gone AWOL; but it has rebooted a few times since. I *just* looked through rebooting FAQ on this site and have edited the first few features listed there. I'm not sure if it has worked yet, but I'll get back to you on that. For the record, the only programs I have installed now are Swiftkey 3, Handcent and Beats (DDR simulator, updated in November).
In the meantime, before I found the solutions here, I decided to take another shot at unlocking the bootloader and try installing... probably CyanogenMod.
Specs: Windows 7 64 bit with Nexus S I9020a (Koodo) running 4.0.4 (4.1.1/2 OTA haven't come through, despite dozens of attempts at clearing the GSF cache, etc)
So I've been using the Nexus S: Full Update Guide found at:
hxxp://wiki.cyanogenmod.org/wiki/Nexus_S:_Full_Update_Guide
(It won't let me post the link)
I've followed the guide for installing the Android SDK, gone to CMD and typed 'adb devices' and had it show up. Theoretically, the SDK should be running fine.
Next, I turned on the USB debug mode. Then I booted up the bootloader, plugged the NS into the PC... and despite not having issue when the it's turned on (driver installed properly) windows says drivers have not been found for the device. Thus, when I type fastboot devices, it comes up with nothing.
I've been, and will continue perusing forums for this, but so far I haven't seen anyone with this specific problem.
Edit: I have also gone to the directory with fastboot/adb and used cmd to reboot into the bootloader, only to have windows 'ding ding ding' an unrecognised device.
2nd Edit.
I've gotten a stage further! I'll keep the thread open because I may come across something and it's nice to write my issues down. Seems my head can wrap around the problem a bit better. Anyway, I installed PDAnet and BAM, it works. Onto getting CWM installed! Thanks for the, uh, help!
3rd Edit.
CyanogenMod 10.0 stable is booting for the first time!! It's taking a while... but I appear to be on the home stretch! Also, my phone didn't reboot for a few hours before I installed CM. So if I don't end up somehow bricking it... and I mean, this first boot is taking a heck of a long time... The animation sets me at least a bit at ease... maybe 4.0.4 will work out...
Edit 4
I forgot to clear the app and cache data before flashing the ROM to the phone and thus the issue... after a VERY tension filled moment of pulling the battery during first boot... I rebooted, cleared said data and reflashed the ROM. After a boot, I realised I forgot the GAPPS zip and fixed that. Now I'm running CM10 Stable!! I'm stoked that after months of putting it off cuz last time I did it I didn't get anywhere after many days, but now it's done!! Thanks again for such an awesome site!
Thanks for sharing your experience instead of just saying "Mods please delete this i solved my own problem" :good:
Hello,
I've been reading this forum for quite some years and using some of the tutorials and ROMs from here but never actually posted anything and now that I have a few questions about on of the ROMs I'm using now I'm not quite sure where to post it since as a newly registered member I can't post anything in the correct ROM Thread [ http://forum.xda-developers.com/showthread.php?t=2467013 ], so please be patient with me.
I thought it would make more sense to post my actually questions than trying to reach those 10 posts to be able to post it directly there.
So now to my questions:
I have a HTC Desire S (obviously) and had for about 1 1/2 years now an old CoreDroid Version from here (can't remember which one) which I was quite happy with till it started to crash more and more often, battery kept draining and then there came a point a few weeks ago where it would just randomly go out and wouldn't restart till you charged it again.
That got me so annoyed I thought I either buy a new HTC Desire 310 soon or give another ROM a try, so I chose the cm-11-20140324-UNOFFICIAL-saga.zip from the first page and installed it after remembering how to do so.
Then the Gapps and started configuring it.
So far so good, ROM looks good, stable, battery is working much longer now, so thanks a lot.
But I had and still have some issues.
Whatsapp wouldn't instal, so through the search function I would a way around it (in the end downloading it from whatsapp directly and installing it through the .apk worked) and got that sorted.
The next thing is still a worry to me, I used to sync my contacts from my outlook through android-sync [ http://www.android-sync.com/ ] which I bought after non of the other syncing methods worked to my satisfaction. Everything worked fine with the old ROM (after I set it up) but with the new ROM the program on my computer can't find the mobile phone anymore, I tried to reinstall the ADB drivers, but it didn't work (I sent the error log from the program to the developer a few days ago but still haven't heard back), so maybe someone around here knows a way around it?
Last night I experienced another issue, the clock works fine and after I installed the ROM I set up a few different alarm clocks and they worked. But yesterday I wanted to change the alarms and now every time I try to access the alarm clock the clock app stops working "Clock stopped working" and it closes.
I can delete the alarms and set up a new one, but only the time, then it saves and when I try to change the days or the sound same error appears. I searched the forum and internet for a bit and found ideas like deleting the clock data and cache, rebooting the device, but none worked.
And last but not least it seems I can't find the right settings for it but every time I swype or type on the keyboard it vibrates. I turned off all the other noises that the phone made while typing but this one I can't find. I would like my phone to be silent and don't vibrate when I type. Where can I find the settings for it?
If anybody could help me with this I would appreciate it a lot.
Kind Regards
Marvin
For vibrating on keyboard press setting are at SETTINGS/Presonal/Languager and Input/Keyboard settings (for me it's ASOP keyboard settings).
Did you do dirty flash or clean one? Clean ROM flash is recommended.
Other problems I got with previous devil-kin CM11.Couldn't get usb mass storage and adb working.Now I keep Flinny CM11 build and it works.I didn't try devil-kin last build.
Maybe you can try install Flinny alpha 5 CM11 and try if that work.
SKENER said:
For vibrating on keyboard press setting are at SETTINGS/Presonal/Languager and Input/Keyboard settings (for me it's ASOP keyboard settings).
Did you do dirty flash or clean one? Clean ROM flash is recommended.
Other problems I got with previous devil-kin CM11.Couldn't get usb mass storage and adb working.Now I keep Flinny CM11 build and it works.I didn't try devil-kin last build.
Maybe you can try install Flinny alpha 5 CM11 and try if that work.
Click to expand...
Click to collapse
I installed Flinny alpha 5 CM11 now and tried it out. I had a few crashes with the devil-kin version too and bought a new battery, so hard to tell what solved what, but so far so good.
But for the syncing problem, now I have an even worse error:
ht*p :// i.gyazo.com/798a67697deb9f91904e7cac9b62bf76.png
with the devil-kin version it still found something and just had problems with the adb drivers, now there seems to be something else going on.
m4rvin88 said:
Hello,
That got me so annoyed I thought I either buy a new HTC Desire 310 soon or give another ROM a try, so I chose the cm-11-20140324-UNOFFICIAL-saga.zip from the first page and installed it after remembering how to do so.
Then the Gapps and started configuring it.
So far so good, ROM looks good, stable, battery is working much longer now, so thanks a lot.
But I had and still have some issues.
Whatsapp wouldn't instal, so through the search function I would a way around it (in the end downloading it from whatsapp directly and installing it through the .apk worked) and got that sorted.
Click to expand...
Click to collapse
Regarding that issue I also got problems with many other apps i.e. Redphone, Textsecure, Chiffry and so on there always comes the message that these apps are incompatible to my device - strange I also use cm11_saga_flinny_alpha5 Kernel 4.4.2.
These messages of incompatibility are generated by Google play store, when comparing AndroidManifest.XML permissions and requirements with the phone...
Further more Issues at Finny/Devilkin CM11.0
Hello guys,
I am also new at this Forum although using it "passiv" since years. Now I flashed the CM 11.0 from Devilkin and ones from Flinny.
- Unofficial CM10.2 / CM11.0 build for Saga / Desire S
All works (both ROMs) great up to the wired headphone Controles.
I think this might be the right thread to Post that until I reached the Number of Posts to put the in the right developerthread. Hope anyone can help.
The exactly problem:
I use orginal HTC-Headset with three controller Buttoms. The headphone itself is working though I can hear music and sound but the Controls and the Mic are not working. I tried to register an input with the jayzheadphone app but it shows no input. Headphone and controls worked fine with stock ROM.
Thank you for help.
@Terodax
Sorry but I cant't evaluate your issue cause of the missing HTC-Headset, but I got some other weird thing with the "mute" button on calling someboy it fails in doing it .-/
So I worked around the little problem in "holding" the call -> that works and it's like muting
htc wihc room to use
Hello
I bought this item.
http://www.ebay.com/itm/121361166744...84.m1423.l2649
Wich rom to android 4 or last?
How can I install those rom?
I need to using zip flashable file on recovery mod or addoin way?
will I need to flash the modem (phone) after?
has the recovery a nandroid backup option? I wanna backup the current rom like it is.
which is the best recovery for that item?
Thanks
---------- Post added at 10:45 PM ---------- Previous post was at 10:44 PM ----------
Hello
I need to use whatsapp and facebook mensseger on it.
thanks
Q&A for [ROM] Official Cyanogenmod 11 4.4.4 for the Moto G 4G (Peregrine)
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Notification light not working with cyanogenmod
Hi,
I'm using cyanogenmod (m6 and afterwards the current daily builds) on my moto g and for quite some time I have the problem that my notification light is not working. I tried out installing the motorola led activator widget, but this doesn't help. Even when trying out an LED tester app nothing happens. The LED is not broken though as it lights up when trying to boot my moto g on low battery. Do you have any ideas how to solve this?
Thank you in advance!
Link down
Seems the latest build link is down
not I download the latest build. fallen servers
Does the ROM still have the low ram bug ?
Problem audio speakers CM11 / Stock ROM
How about, first of all, I'm new here and do not speak English, so I excuse my writing.
I have a problem with my Moto G LTE (XT1040) with Stock ROM 4.4.4 KK Brazil, although I am from LatinAmerica.
Well, I have not much to this terminal, but a few days ago I had some problems with the rom Stock, restarting not it caught more, so I decided to flash the latest rom Cyanogenmod (specifically 20,141,012) due to some stability issues decided you go back to the Stock, having the same error when freezing some applications Motorola as usual to, so back to CM and switch to the "20141016" to the few hours I started to fail the camera, remained frozen when taking a photo . After that, it went back to flashing CM rom and had the same errors, updating the "20141018" was the same, but a new bug, and could not hear the music or videos without headphones was added, calls were heard if it was not for speaker, so I decided to go back to the Stock, but apparently the problem was continuing, feel that the speakers are damaged, but the alarms or notification sounds if they worked properly. Now try wipes Cache / Dalvik from CWM but only achieved a temporary solution, put a good song and all, but to change it or put it back the audio is going.
Help me, do not know what else to do, I guess that having unlocked the bootloader and lost my warranty
Thanks in advance if this post is incorrect or I violate any rule, excuse me, I'll delete.
I'm also trying to get GPS to work on my Moto G LTE in cm11:
Based on what I read here, I reflashed stock, and tried it out, had no problems at all. Then restored the cm11 nandroid I had made, and it couldn't see any satellites still. Will restoring the nandroid backup also restore the not-working-gps then? What is being saved by unlocking the gps? Will I have different results from backing up everything with titanium backup, then going back to stock, using gps, reinstalling cm, and restoring the backed up apps? It's much more of a pain to do it that way, but if it works, I'll find the time...
This is a canadian xt1040, btw, in case it makes a difference.
UPDATE: I went ahead and reinstalled stock, played with gps for a while, and it worked without any trouble, then reinstalled CM11 (oct 21 nightly this time) restored my backed up apps with titanium backup (not any system apps). Unfortunately, still no gps at all. It never sees a single satellite. Is there anything else to try?
Hello,
First of all, thank you and all people to contributing and helping developing CM for this device!
I only have one question about GPS bug :
You indicate that it's necessary to have a GPS lock in the stock ROM first to enable GPS in CM.
Does a fix for this bug is intended/possible or the only one solution is to reinstall the stock rom, enable GPS and install CM?
Thanks in advance.
Audio solved
It updated my previous query, I could solve the problem of audio speaker, I began to disassemble the phone and as imagined, I found steel wool at the entrance and were making contact, so the cell believed to have headphones all the time .
Enable GPS in Moto G Nightly
This is in response to jac0708 in the thread this thread who asked:
Mind expanding on these two? What is the low ram bug? And how do you get a lock from stock for the gps fix?
Sorry for noobishness
Click to expand...
Click to collapse
The answer I found for the GPS not working was that when I installed CM11 within hours after taking delivery of my Moto G, the GPS would not get a fix. The solution is explained here by colinw:
Posted 11 October 2014 - 10:42 PM
Okay I just fixed my problem following some other post for a Moto phone.
1) Made a (nandroid) backup using clockwordmod of my current setup (cyanogen 11)
2) Restored old backup of a stock rom (I restored back to the one that came with my phone)
3) Then I had to USE the GPS - hadn't done that yet. Also made sure it was set to Device Only mode in settings->location because someone somewhere suggested it.
4) Restored to cyanogen rom.
5) Working!!
Click to expand...
Click to collapse
Just wanted to add that it doesn't always work. I tried at least three times, restoring stock, using gps, and then restoring my backup before I had gps working in CM. But it does work now! Be patient, and maybe just leave the phone with the stock, sitting on maps for a while. Perhaps I rushed it before?
Q&A for [ROM] [COMMUNITY] ANDROID 5.1.1 OCTOS *Obake*
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] [COMMUNITY] ANDROID 5.1.1 OCTOS *Obake*. 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!
Can I install it without bootloader unlock?
Summersett said:
My bootloader unlocked Maxx is on 4.4 (19.5.3.obake-maxx_verizon.Verizon.en.US). Since my bootloader is unlocked, do I really have anything to fear when flashing ROMs or am I pretty much guaranteed to be able to always have WP off and root? I'd like to give this one a shot but don't want to cross any bridges I may not be able to come back across if need be.
Click to expand...
Click to collapse
My bootloader is locked, I'm on 4.4.4 with root, but I don't now how I can unlock my moto, I must to have TWRP? How can I install this recovery? Help me please, I want lollipop, and verizon is so slow.
This isn't the place to ask that, and right now you are stuck on stock. Please dig around the forums and do some research before spamming threads where content does not belong.
No GPS
Flashed this ROM on my Droid MAXX and love it. Everything seems to work except I cannot get any GPS lock on any application I tried. Downloaded GPS toolbox and reset and downloaded aGPS data but no change. Anyone have this problem? From what I've searched on forums it seems to be a somewhat common issue in Lollipop. FYI I also flashed a different 5.1.1 ROM and it had the same problem.
jwieler88 said:
Flashed this ROM on my Droid MAXX and love it. Everything seems to work except I cannot get any GPS lock on any application I tried. Downloaded GPS toolbox and reset and downloaded aGPS data but no change. Anyone have this problem? From what I've searched on forums it seems to be a somewhat common issue in Lollipop. FYI I also flashed a different 5.1.1 ROM and it had the same problem.
Click to expand...
Click to collapse
I haven't had this issue and have reflashed this ROM a few times. Tbh I have never even heard of that as an issue (though it's not like I researched Lollipop problems since I wasn't having any).
I used TWRP 2.8.4.0, factory reset, flashed the ROM, and then flashed these GApps. Idk if that makes a difference. Give it a shot if nothing else is working for you? Good luck.
Dang... That is exactly how I did it. I used that same exact gapps file and also am on TWRP 2.8.4.0. Seems like none else is reporting this problem on our phones. Maybe the radio got screwed up? Just thinking out loud here
Installed OctOS on two separate MAXXes. My gfs seems stable. Mines been touchy though-
A) Like someone else mentioned, using the flashlight for an extended period often ends up in the phone doing a hard reboot. Haven't tested this with her phone but she hasn't reported anything to me either.
B) WiFi has been unstable. Initially it was fine, but every now and then it starts refusing to connect to any network. It doesn't kick back any error. It will say connecting, etc, then at some point fail and go back to just noting it's a saved connection. Have to go through some combination of forgetting the connection, wiping cache/Darvin, think I even tried running fix permissions. Eventually it will work normally again, but not for long before having the same issue. There haven't been any wifi issues with the other phone. The first time this ever occurred was right after using it as a hotspot, but its happened more often without any hotspot usage than with it.
C) Did great at first, but without installing very many apps, it feels like it's gotten slightly sluggish and is often low on memory, and is burning through the battery much quicker. Used the be able to clear 24 hours before needing to charge, now I'm lucky to get 16. I haven't had the chance to see if this is also an issue on the other phone or not.
GPS works nicely for me with this rom. My phone got a fix in seconds with 16 satellites.
Question: which is the best way to theme this (or others, for that matter) rom? Download CM12 themes from mayket?
jwieler88 said:
Flashed this ROM on my Droid MAXX and love it. Everything seems to work except I cannot get any GPS lock on any application I tried. Downloaded GPS toolbox and reset and downloaded aGPS data but no change. Anyone have this problem? From what I've searched on forums it seems to be a somewhat common issue in Lollipop. FYI I also flashed a different 5.1.1 ROM and it had the same problem.
Click to expand...
Click to collapse
Did you ever get GPS back? Some say going back to stock, getting a lock, and then go back to the custom rom works. There is also a link in the exodus thread about doing two fastboot commands, which worked for me for a bit, bit now I'm back on stock with no GPS at all. Curious if you got yours working.
Hello and thank you for viewing my thread!
To start, my device is the OnePlus One, and i am running the latest Release of CyanogenMod 13 with the Latest Lightning Kernel for it's kexec/hardboot patch
I have tried multiple times, installing the multirom files, as well as flashing a factory image and flashing from a fresh install. Nothing seems to work.
The exact problem would be, even after performing the inject boot sector action, multiboot or the boot menu fails to appear.
I have no idea how to view kernel logs or anything of the sort. However i will gladly provide any logs or files if needed! Ill just have to figure them out is all.
Any help is greatly appreciated. Thank you in advance!
Edit:
1. I think i have the kernel ruled out as the problem as i have already tried a modified stock kernel, as well as bouffla's kernel.
2. The rom also doesnt seem to be the problem as i have tried both COS 12.1 and CM 13
3. The recovery seems to be ruled out as well. I rolled back to a previous version of TWRP and still have the same issue, no multiboot menu after proper installation.
4. This is really confusing. I even tried using the files built into the multirom manager application and that fails as well.
P.S. (on a semi-unrelated note)
I currently have a strong feeling it is a very low level issue (at least for my experience) due to the fact that kali nethunter is also failing to install and causing my device to brick every time i attempt an install.