So I've encountered this issue for a while but haven't asked about it. Has anyone figured why the Quick Controls (Settings>Labs>Quick Controls) don't work in Landscape mode? It works on newer phones that have official ICS builds, but not on CM9 or Slim ICS.
I don't have a Vibrant but I spent a while yesterday Google-ing the same exact issue on my Galaxy S II (AT&T) with AOKP.
After a few hours of playing with settings, ROMs, and kernels, I finally found the problem (on my phone at least, hopefully it may help with yours). On my phone, quick controls does NOT work in landscape when the phone is connected to a power source- but, as soon as you unplug it from its charger, quick controls works perfectly in landscape with no issues. I have no idea why this is or if it is a bug or it was designed to do this.
If you have been trying QC with the phone plugged in, unplug it and hopefully it'll work!
Good luck
James
Related
Not being able to post on the Development sections cramps on my style a bit, but I have a couple of questions:
* First of all, I am still on Oxygen, do you guys think there's any good reason to switch? I like Oxygen a lot and apart from a couple of issues (see below) I've been very happy with it... Will dzo ever show up again and merge the new drivers into his release?
* Have the camera and GPU driver from the official 2.3 been ported to any other ROM?
* I've been seeing a lot of ICS related ROMS in Development as of late, is there a fully functional ICS ROM yet? What's stopping us, since it seems almost every other device is making some progress with it (i.e: having hardware acceleration enabled, radios working, etc.)?
Problems with Oxygen:
* Light Sensor behaves strangely: for example, with auto brightness enabled, turning on or off the light in my room makes no change in screen brightness. If I put the device close or directly under a lightbulb it will only then begin to change. I can confirm this with some sensor testing apps. Is there any way to calibrate the light sensor?
* Microphone acts strange: I have never seen anyone report this, but when I connect headphones, then try to use for example voice dialing or voice commands it will not work (wait forever) or simply give an error. If I disconnect the headphones after I tried to use voice it will never work again unless I reboot. If I connect headphones, never use voice, and then disconnect them and use voice it will work as it should
* Signal Strength very irregular: I live in a area with difficult reception, but signal strength is insane, sometimes is goes from 0 to full bars like no big deal
* Camera's FPS very jumpy (new drivers will fix this?)
* No access to internal storage: I knew this going in, but still...
* Flash videos sometimes green and overlapping the screen. This happens with both the YouTube app and any video player that can play FLV. It only happens from time to time and I can't reproduce it.
I went straight from stock (TMN Portugal) to Oxygen, never messed around with any other ROM (I tried CM7 for half an hour or so) but these little things start to bother me, plus it breaks my heart to know that the camera and GPU could be much smoother just by using different drivers. It also scares me that Huawei disabled the standard method of installing Recovery and rooting, so I'd prefer not to upgrade to the official ROM right away. So, is it worth to change ROM at this point? Can you help me with any of my problems with Oxygen?
Hi!
I tryed "all" ROMs I found here in XDA, Oxygen for me is not enough, it just lacks of "options" I love the Cyanogen Settings, you can do a lot of customizations there. Im on custom ROMs for 5 months now, never had a problem with the phone itself. Strange rebooting, camera stopped working and drainage of the battery does NOT count in here. I would suggest you try CM for more than a half hour since - in my opinion - it is the best. I hate the original Froyo, because it lacks of customization. So MIUI is not an option for me, it is just to simple. I was thinking I know all about flashing, but yesterday I just bricked my u8800, simply because I did not notice the + on the end of the official 2.3 update and installed update for u8800+.
My suggestion is, to follow guides here on XDA (they are excellent) and try all the ROMs, and see which one suits you best.
I'm also very happy with Oxygen, I'm still on r1 and have no major issues at all, so thank you very much dzo!
But I hope for the future that dzo will continue to update this rom so we can get better drivers for camera and other small fixes. It looks like the official rom will never be an stable option for us...
Mach III
Because I can't post in the proper place, maybe the forum admin could transfer
this post to the proper place(development).
On version b-37(5/26) of the AKOP build for vision I have a couple of comments.
I have exercised this build for the last few days and it works very well, I only have found a couple of possible bugs.
The mic in the headset(earbuds) does not seem to work for phone calls. The little switch on the headset does seems to work and the playback works fine. The mic in the phone works fine if you unplug the headset. There might be another program switching the mic off, but I haven't found any. It is like the mic is in mute and the mute switch does nothing on the headset mic.
The WiFi is off when the phone boots up, This might be a feature rather than a bug. Unless there is a lot of complaints I don't think it needs to be changed. The Internet phone from T-mobile does not work(known).
Another problem and I don't know if it is a program problem of a version problem.
I have tried many web browsers and on some sites they are very slow for the page to loads(like a minute or so). It might have something to do with Flash,
although most sites are OK. You Tube does work OK. Another quirk is the sites will come on with low resolution and then it appears as though the site has finished loading and the font is fine. It appears as though some sort of page loading problem. This happens with all the browsers I have tried.
A couple of times I have had the font under the Icons scramble, if the page gets rewritten then the font is OK.
All in all this is a very good version with very few bugs, great job !!!
Clyde
New build is up. Some of your bugs should be fixed already (e.g. with microphone).
AKOP build 38
The mic problem is fixed in b38(thanks), only one other problem that is new
to b38 is that the Home key and the Search key on the bottom of the phone
no longer function.
I found that the included browser has problems when loading then freezing on a
white screen. Other browsers seem to work, so deleted same.
I might add that in b37 and b38 the track pad finally works like it is supposed to.
In earlier versions and 2.3.4 it never worked properly. Also, the lights on the
keyboard and the 4 buttons on the bottom of the phone now stay lighted and
don't go off and on. Thanks for the improvements.
Clyde
Hello,
I also use the ROM and find it great. But I have two problems with it.
I can't send MMS. I have delete and recreated the MMS-APN but without any change.
My second problem is the clock when I use the apex launcher. When the phone ist unused for a while the clock goes wrong. On the widgets it shows 10:20, on the screenlock it shows 9:45 an the realtime ist 11:34 or so.
I hope someone has an answer.
thx
Home Key fixed
Found the problem I was having with the Home key being non-functional.
Seems like 2 programs I found write data where it is not supposed to be,
they are Android Assistant and Super Task Killer. If you run either one of these
programs the home key becomes non-functional.
The standard included browser has a problem with most of the time not
starting and giving only a white screen. I have tried 6 other browsers and all
work fine. Deleted same.
This fixed the 2 major problems with Build 38. There is a minor problem with the
Sim Card recognition, gives a error message to restart which is in error. The
main screen comes up long before the initial boot process has finished. I think
init.d is running after the main screen comes up. Works fine if you just let it
complete its work.
Build 38 is very stable and has very few problems. Great work !!
Clyde
I'm not sure if it's the fact that Wifi Direct isn't working on latest PACMAN rom or the fact that just the wireless display function isn't working, but one of those two isn't working and it doesn't allow me to connect to my TV. I've tried a few ROMs each with their own problems like wifi not working blah blah blah.. but I don't want to use other ROMs, I'd like to stick to PACMAN if I can, just would like to know how to make it work!
Is it a kernel problem? I mean the functionality is there in PACMAN, but it says "To see devices, turn wireless display on" with no toggle at the top? :/
I would post in the thread but I can't yet, so hopefully someone can help me out... please.
I had the same issue with my Nexus 4. The problem I have is that the On/Off switch isn't shown in Tablet UI. I switched from tablet to either phablet/phone ui in hybrid properties and now it shows the on/off switch. Find them in your settings.
I don't know why it is not being shown in Tablet UI. Rotating the phone to landscape/portrait doesn't show the butten either. I guess it is left out in tablet mode because no tablets exist with the technology? Or is that a wrong guess? Maybe it's a bug that has yet to be fixed.
I have a Canadian Note 3 (SM-N900W8), it's KNOX 0x0 rooted and I have CM11 M12 installed. I have been using only the M builds since I got this phone, I didn't even set up Touchwiz when I got it, I rooted and installed Cyanogenmod out of the box.
Now, with the new CM12 builds coming out, what happened to CM11, are they going to fix the remaining issues? Or did they just bail on legacy KitKat users because I'm having TONS of problems and I don't want lollipop, it runs like absolute crap for the nightlies right now and CM11 M12 isn't much better. Bluetooth takes a couple of attempts to connect, when it does my phone runs super slow to the point it force restarts. For instance, if I'm driving around, listening to music on the car stereo, pull over some where, find a new album on Google Music, start playing that, it's all good, do this a few times, every time I use my phone it gets slower and slower until it force restarts and then bluetooth has trouble connecting again. I've tried this on a few other vehicles of different brands and aftermarket stereos and it's the same result.
Audio is all funky when bluetooth is on too, it sounds like robots for the system sounds and if bluetooth drops while it's connected the music starts playing from the phone and sounds all roboty. I always do clean flashes too and the latest Paranoid Android GAPPS every time I reflash, the ROM is fine out of the box, works flawless for the first few days but after awhile, it becomes so bad I have to backup, wipe, reflash, and start over for another few weeks.
Another issue is somewhere between M8 and M12 one of the builds corrupted my SD card, I tossed in a second new card, it was corrupted again, FutureShop won't give me another one and said my phone is breaking them so I'm SD-less right now.
There are also quite a few apps that force close, but always at random, it's never when doing the same thing over and over, for instance, I can be scrolling through G+ and it tells me settings has stopped working, wasn't even using settings, didn't even have it open, haven't clicked it since booting my phone, just randomly stops working for no reason, this also happens all the time with the Camera, it says it just stops working when I haven't even used it and then if I try to use it, it says the camera is disconnected and won't work until I reboot.
I turn my phone off every night while it's charging and turn it back on every morning so every morning it gets a fresh restart, and I have to restart my phone probably 5ish times a day, if I'm using bluetooth more then normal then there's quite a few more unintentional reboots in there as well.
The last issue, which is a known issue is NFC not working, is there a fix for this yet? I kinda miss this feature and with how flawed CM11 is getting I don't know where to turn since they always seemed to be the most stable out of everything I've tried.
Any before anyone says Temasek's CM builds, I tried it, the final for CM11, it was worse then M12, it's exactly the same as M12, but every issue happens more frequently. Also, the pull down menu (when pulling down from the top right to show toggles), the bottoms of the last row was cut off so it didn't look very appealing either, it also used WAY more battery life, I usually get a full day out of one charge, so around 18 to 20ish hours on one charge, with temaseks cm11 I had to charge my phone half way through the day, sometimes my phone would just die on me without me knowing, the battery usage was always Android System.
A new problem that just happened lastnight was Google Keyboard was deleted and only the voice search would work, but "voice search can't be reached" so I couldn't search for another keyboard app from the playstore. I also used the stock GAPPS so AOSP keyboard is replaced with Google Keyboard, I had to reflash again this morning because I couldn't figure out the keyboard thing, there wasn't even a keyboard under languages in settings so I had no options to pick which keyboard to use. When I reflashes this morning I used the Modular GAPPS to it keeps the AOSP Keyboard just in case this happens again but I'm getting really tired of only having a reliable phone for a few weeks.
So, are there any fixes for these issues?
Bluetooth taking multiple attempts to connect
Bluetooth forcing random reboots
Bluetooth making audio from device all funky and sounds like a robot
Corrupting SD cards
Random system apps stopping without me even using or opening them
Google Keyboard vanishing
Are there any stable ROMs I could try for the HLTE? Maybe one that has working NFC? I'm almost thinking of going back to stock *throws up in mouth* but I don't know what else to do with how many bugs there are and Lollipop is only getting worse with the issues.
I'm also trying to avoid Lollipop because everything is white, Note 3 is an AMOLED display, each pixel illuminates on it's own so white screens use WAY more battery life then black ones which was a feature of Temasek's CM11 that I liked, had the option in settings to make everything black like the good old days.
So guys? Really out on my luck here, not sure what the next step is, any fixes for these problems? Any other ROM's I could try? Would flashing a new recovery and reflashing CM11 M12 fix some of these issues? I'm using Xiaoli CWM v6.0.4.7(20140125). Would the fact that KNOX isn't tripped have something to do with this? I really don't understand why there aren't more posts for these issues which leads me to believe I'm one of the only ones experiencing them.
Any help or suggestions would be greatly appreciated
EDIT:
I forgot to mention that when recording audio or video, it's as if the mic gain is set on full so even the slightest sound is pure distortion, normal talking volume and it clips, I found an app that lets me choose between the mics and when I pic the external mic, it's all muffles as if something is covering it but my phone wasn't in a case while I was testing so I'm not sure what the deal is there but I can't record any decent audio with this and when I record in 4K using Cinema FV-5, all the videos turn out looking like Anaglyph 3D but all pink and green, it's really weird and I don't understand why, but 1080p at 60fps works fine.
I am on CM12 and luckily have had no issues at all. I came from KK 4.4.4 and still have the NB7 BL and modem. I tried one of the guys slim ROMs alpha builds but had issues (probably operator error) but I've tried Bluetooth, GPS, WiFi , LTE etc and everything is good. Not sure what to tell you. I do however always wipe internally and d/l all my apps again through WiFi. A bit cumbersome I know but it won't give me any residual data.
Sent from my SM-N900W8 using XDA Free mobile app
So i finally gave cm 12.1 a chance because it's been rolling for a while now... and i was actually pretty impressed. The one issue i couldn't deal with is the bluetooth audio playback in my car. Basically it was playing too fast, then pausing every 10-20 seconds and then continuing to play too fast again (also at a slightly higher pitch). I was able to temporarily fix the problem by turning bluetooth off and on but it came back. other than this i didn't see many issues and thought it was pretty good, but for no i'm going to go back to stock until this issue is fixed, i did find that it was already reported to the cyanogenmod team and they are already working on a fix so i'm waiting impatiently until it's fixed and i'll probably be moving from stock kitkat as my main rom to cm 12.1. How has everyone elses experience been with cm 12.1 nightlies so far?
What doesn't work. (if i missed something here post so i can update)
- saving 4k video (1080p works tho)
Battery life ?
- used to be terrible but it's almost as good as stock now but with better performance.
hey
i would like to use CM as i was doing that on my Moto G. the questions I have to users of the newest CM version:
- does quickcircle, google text-to-speech, intelligent screen (LG app) features work?
- what is the quality of videos and pictures taken by the phone running CM opposite to android v20i?
thank you.
Brtnsk said:
hey
i would like to use CM as i was doing that on my Moto G. the questions I have to users of the newest CM version:
- does quickcircle, google text-to-speech, intelligent screen (LG app) features work?
- what is the quality of videos and pictures taken by the phone running CM opposite to android v20i?
thank you.
Click to expand...
Click to collapse
1. Quickcircle won't work. To make it work again you have to install a special app. Google text-to-speech works ok for me (I haven't test it too much). LG features/apps won't work
2.For me the quality of pics and videos are the worst I have ever seen!!!! (Much better in the stock LG)
My experience with CM12.1 was average. I was waiting for something better. Camera is awful in the Custom roms. Battery life wasn't the best. In terms of performance the cm12.1 is better than the stock lg.
i've only been running cm 12.1 for a few days now so i don't have alot of substantive input, i did find a fix for the bad bluetooth car audio using a macro/tasker app but i think they have fixed it in the nightly released today, i'm downloading it now it says bluetooth stream parameters in the patch notes so i wont bother sharing my fix until i try this nightly to see if they already fixed it. i'll give a better review of whats working and the camera/video quality after i have a chance to play around with it more.
by the way anything running ART instead of DALVIK cache/runtime is going to perform better but it's at the price of xposed modules and such, i'm not expert on it but i know they switched to ART cache/runtime to be more competitive with the iphone. On Kitkat and lower an android device needs better hardware to output the same performance as an iphone with lesser hardware. ART should fix that problem. If you are curious google ART vs DALVIK
*edit* yeah bluetooth is fixed with the newest nightly update... atleast for my car which is a mazda 3. (yay)
Avrage camera and bugs like video not saving after recording is main culpit to not use CM 12.1. Otherwise it is good as clean android can be.
it's getting alot better every day now
netmaniack said:
Avrage camera and bugs like video not saving after recording is main culpit to not use CM 12.1. Otherwise it is good as clean android can be.
Click to expand...
Click to collapse
Videos do save. It is a issue with 4K video ONLY. Switch to 1080p video and videos save just fine.
c_brown93 said:
Videos do save. It is a issue with 4K video ONLY. Switch to 1080p video and videos save just fine.
Click to expand...
Click to collapse
I found that myselfe, tnx. But I believe that issue is fixed already. Maybe Im wrong, but I did see in changelog or other forum. Maybe someone can test it?
I switched to stock kitkat, I love CM, been running CM since it was 10.1, the problem is that it starts really really fast and after a while CM 12.1 becomes laggy it drives me crazy, other than that is the camera quality which doesn't bothers me as the performance issue,
I guess we'll need to wait for LG to release the G3 source file but who know's when that's gonna happend
good news the latest daily added some balancing between power and battery life. I went from losing a huge chunk of my battery during work when my phone is in my pocket to going 9.5 hours at work and coming home with 94% battery. (that is alot of standby but i use my phone at lunch and have bluetooth running for about 50 minutes of driving). Basically it got alot better, i'm not sure what they did but i did notice that there is a balanced setting in battery screen that i didn't notice before. Anyways I think those who were concerned about battery drain my have had their wishes answered over the last few nightlies.
netmaniack said:
I found that myselfe, tnx. But I believe that issue is fixed already. Maybe Im wrong, but I did see in changelog or other forum. Maybe someone can test it?
Click to expand...
Click to collapse
i still can't get 4k video to save but 1080p did.
Do knock on and knock code work?
Lucenzo7 said:
Do knock on and knock code work?
Click to expand...
Click to collapse
Knock on works but knock code doesn't, which is quite normal considered it's an LG feature.
Lucenzo7 said:
Do knock on and knock code work?
Click to expand...
Click to collapse
Partly working. You can turn screen on by clicking anywhere, and turn it off by knocking at notification bar.
Phone encryption not working?
I've just flashed the 20150603 CM12.1 and I cannot seem to get the phone encrypted. On the reboot to start the encryption, the phone gets stuck in the CM boot animation and the encryption process never starts. Any ideas or suggestions? Many thanks in advance.
I'm on 06/05 nigthly. When I plug the phone in my computer, it's not being recognized. If I change from MTP to PTP, then it works.
I've tried going to Device Manager, and could see that my phone is being recognized as a Nexus device. I tried installing latest drivers from Google's website, but I got a message saying that I'm already on the latest version. So that didn't do anything. I've tried uninstalling that "nexus" driver and rebooting my PC, but it somehow came back when I plugged my phone in. Trying to update gave me the same message.
If I run "adb devices", I can see that there's no devices (it's enabled in developer settings). If I enable ADB over WiFi and try to connect -- it works, and I can do whatever I want. But only over WiFi and not via USB.
Tried different cable and different port as well.