Database Users

No keyboard back-light or camera, cyanogenmod

On the last two latest version of it, my keyboard backlight doesn't turn on, and my camera says 'can't connect to camera everytime i go into it.
any ideas on how to solve this ?

What version are you on exactly?
Sent from my DROID 2 ICS using xda premium

on my phone it says 2.3.7 ,
I used rom manager to do this

The cm7 on rom manager hasn't been updated in a long time and is probably broken.
Sent from my EncounterICS droid 2

oh yea but I forgot to mention that I downloaded the 12/19 version of it and installed it through rom manager but the problems were the same.

Are you wiping data/cache/dalvik before and after you flash?
Sent from my EncounterICS droid 2

I've noticed this for quite some time, backlight doesn't work on keyboard unless you close the phone, cover the light sensor with your hand and slide it open. I'm using 12/17 nightly. Also i noticed a combination of locking the phone and unlocking, sliding the keyboard open, works.

What are you guys flashing from? I went back to cm7 today and everything was working fine. Including the keyboard lights.
Sent from my EncounterICS droid 2

not sure the exact positions but you have to edit the auto back light setting from 0 to 255 in a couple of positions

That's only if they are using MIUI.
Sent from my EncounterICS droid 2

[Q] Camera Problem

Guys,
i had earlier flashed cm 7.2 to my defy plus with the battery fix and the camera fix....everything was working fine
However, a few days back, i got it back to the stock 2.3.6 via custom recovery....everything works normally, however, the camera is not working
It starts up and shows a blank screen with all the options....as if the camera were on, and someone had switched off just the lens....
When i click, the picture is taken and i can see the image, however, i cannot see the viewfinder view.....
Please help me....cheers

rohan2jos said:
Guys,
i had earlier flashed cm 7.2 to my defy plus with the battery fix and the camera fix....everything was working fine
However, a few days back, i got it back to the stock 2.3.6 via custom recovery....everything works normally, however, the camera is not working
It starts up and shows a blank screen with all the options....as if the camera were on, and someone had switched off just the lens....
When i click, the picture is taken and i can see the image, however, i cannot see the viewfinder view.....
Please help me....cheers
Click to expand...
Click to collapse
Which phone MB526 or MB525??
If it is MB525 then which color lens (Green or Red)?
However, in both the cases you may search the thread from which you have downloaded the ROM; that thread may have Camera fix for your phone.

rohan2jos said:
Guys,
i had earlier flashed cm 7.2 to my defy plus with the battery fix and the camera fix....everything was working fine
However, a few days back, i got it back to the stock 2.3.6 via custom recovery....everything works normally, however, the camera is not working
It starts up and shows a blank screen with all the options....as if the camera were on, and someone had switched off just the lens....
When i click, the picture is taken and i can see the image, however, i cannot see the viewfinder view.....
Please help me....cheers
Click to expand...
Click to collapse
Maybe, it helps.
Go to settings > apps > manage apps > all > camera > erase data

rohan2jos said:
Guys,
i had earlier flashed cm 7.2 to my defy plus with the battery fix and the camera fix....everything was working fine
However, a few days back, i got it back to the stock 2.3.6 via custom recovery....everything works normally, however, the camera is not working
It starts up and shows a blank screen with all the options....as if the camera were on, and someone had switched off just the lens....
When i click, the picture is taken and i can see the image, however, i cannot see the viewfinder view.....
Please help me....cheers
Click to expand...
Click to collapse
Happened to me few days back on CM7.2... turned out the culprit was "live logcat"...
[check: http://forum.xda-developers.com/archive/index.php/t-1146496.html]
Not sure if what you are facing is the same thing...

Phone Process closing immediately after opening on ShenduOS

Hey guys, I recently installed [7.18.13][4.1.2][v1.0] ShenDu OS,
and everything works fine aside from getting the message "video recording failed" on snapchat.
But the real issue that I care about is the phone process immediately closes after launching.
So I can't or even receive a call at the moment. Anyone else having this problem?
I've reinstalled a couple of times now. I really like the look of this rom, and
it runs smoothly. It's just, you know, I'd like to call people sometimes.
Thanks

That's a bug with ShenduOS rom port.
I know that ROM is amazing but 2 others have also reported phone fc
It might be because the kernel is missing a few files in the ramdisk since i remember coderzs saying that the .61 cannot be used with cyanogenmod .
Sent from my myTouch 4G using xda app-developers app

Skype & Kitkat issue

Everything was perfect when i was on Android 4.3, any skype calls working, video/audio doesn't matter.
But when i updated my wife's phone to kitkat, some skype calls making phone reboot(black screen, then its loading as usual).
It happens not always. And i have noticed that it crashes only while talking to people who have Windows XP installed(with latest version of skype, checked & updated myself).
When she talks to anyone on 7&8 Windows - everything is perfect.
I have tried all custom roms, original, rooted\not rooted, anything.
I gonna write this issue to Skype too.
Skype support asked that Skype not supporting KitKat yet.
Btw it only happens on Nexus 4, when i'm on my phone (XT910) on KitKat, it works and not hangs.

In my case occurs the same...I believe is maybe kit Kat by itself and usually happens when I leave a call in the background while I use another application. Unfortunately I haven't found any solution for that.

i have noticed that it crashes only while talking to people who have Windows XP installed(with latest version of skype, checked & updated myself).
Click to expand...
Click to collapse
Not really. The problem is a bit more serious: all ROMs (stock and custom) based on 4.3 or 4.4 are affected by this overly annoying camera bug. I obviously hope you're not, but if you end up as unlucky as I did, your camera and LED flash will soon become totally unusable (on all applications), fixable only by reverting to 4.2 or updating to L (I did and it's totally worth it)
Good luck :good:

Also another issue with Skype and N4 is that whrn listening to music and an image is being sent / received in the Skype chat window, fetching that image from the gallery/disk causes the audio system to crash. It's really annoying. Probably it's the same issue as the well-known audio stutters on changing connectivity and high cpu load.

Im using the Verizon G2 and running 4.4 2...xdabebb rom..i use skype a lot for business calls and havent come across this issue at all. On unrooted stock as well as custom. Ive also faced no issues on an S4 i9500...so it might not really be a kit kat issue but a nexus 4 specific...or an aosp based rom specific issue
Sent from my VS980 4G using Tapatalk

I have another kind of issue with my xiaomi Mi2 with MIUI Rom on kitkat 4.4.4. I have systematically a black screen when the communication is established on Skype also using test sound server. The sound is working but I can't do nothing with the phone until the end of communication decided by my correspondant.. Very annoying . I have post the question to Skype 5 days ago but no answer. Skype was working properly on my phone on miuiv5 android 4.1.2
Envoyé depuis mon Mi2 kitkat 4.4.4 Miui6

I'm having the exact same problem ... I was talking on Skype video call and the phone screen went black and I couldn't hear the other party.. I don't if they were able to hear me or not. I had to hold the power button and reboot my phone manually. I don't know what the problem is but its very annoying and it happened three times in a row. I have used multiple ROMs and it was happening on all of them and they were all 4.4.4. I don't flash kernels, I just use the kernels that come with ROM because they have obviously been tested and have been found compatible with the rom. So I know its not because of kernels. Currently I'm on Slimkat latest weekly and was thinking about going back to stock but someone said its also happening on stock ROM. I'm going to try CM11 and see if it happens there as well. Will report back soon. Hopefully it's just a 4.4.4 issue and not a phone issue.
Sent from my Nexus 4 using XDA Free mobile app

[Q] CyanogenMod + Android Wear

Hi,
I have a samsung galaxy express i8730 with cyanogenmod 11 (4.4.4).
Does cyanogenmod work with android wear?
Sebastiaan

sebastiaann said:
Hi,
I have a samsung galaxy express i8730 with cyanogenmod 11 (4.4.4).
Does cyanogenmod work with android wear?
Sebastiaan
Click to expand...
Click to collapse
So far i know it works
Sent from my LG-D855 using XDA Free mobile app

I have an S4, and I haven't gotten mine to work on CM 11. I mean it does, but not very well. Gonna switch to a TW rom tonight.

S4 running CM11 and no issues with my LG g watch. Everything comes through with no disconnects.
Sent from my GT-I9505 using XDA Free mobile app

sebastiaann said:
Hi,
I have a samsung galaxy express i8730 with cyanogenmod 11 (4.4.4).
Does cyanogenmod work with android wear?
Sebastiaan
Click to expand...
Click to collapse
I'm using CM 11 (4.4.4) on a S4 with Android Wear. No issues that I can see so far.

On Nexus 5, anything other than stock doesn't work well. Watch disconnects too often to be usable (bluetooth stack is dodgy on aosp or CM).
The fix is to flash Elemental kernel. Problem solved. This kernel is available for both aosp and CM.
Even in stock rom, if you flash another kernel, like franco kernel, the watch becomes unusable.
Again, the fix is to flash Elemental, with gives you the added bonus of enabling screen calibration for nice poping colors.
It took me time to discover all this. And frustration.

lost network connection
Hello I installed cm 10.2 through flash recovery. Onti my galaxy ace 2GT I8160 was gingerbread 2.3.6
Now its team conja jls361 if ive looked in the rite plce i still have iemi number and can recieve messages
But when i try and send or call it say no network ive been on to 3 my provider and they say its the phone
Please could you help with thi ive read it happens alot with this release of cm.. Would installing cm 11 sort it out im a newbie to being root ive already soft bricked it once so can see it being a bumpy ride so all the help i can get the better thank you
Also I looked at the build list and the radio and boitloader are unknown the biitloader has been like that when i got the phine that's bootloader not biitloader or bout loader dam key pad lol
My kernal is a i8160xxlk8 or it was I dunno if it still is

Connecting, running sync loop
Latoc said:
On Nexus 5, anything other than stock doesn't work well. Watch disconnects too often to be usable (bluetooth stack is dodgy on aosp or CM).
The fix is to flash Elemental kernel. Problem solved. This kernel is available for both aosp and CM.
Even in stock rom, if you flash another kernel, like franco kernel, the watch becomes unusable.
Again, the fix is to flash Elemental, with gives you the added bonus of enabling screen calibration for nice poping colors.
It took me time to discover all this. And frustration.
Click to expand...
Click to collapse
Any ideas for running CM on the galaxy s3? Android wear will not switch to connected, shows, "connecting, running sync loop". Most functions work OK but the watch is dying terribly quick. I know the moto 360 battery is supposed to be iffy, but I should get more than 4-5 hours....

Garrett 77 said:
Any ideas for running CM on the galaxy s3? Android wear will not switch to connected, shows, "connecting, running sync loop". Most functions work OK but the watch is dying terribly quick. I know the moto 360 battery is supposed to be iffy, but I should get more than 4-5 hours....
Click to expand...
Click to collapse
I don't know about s3, but you should try a few kernels and see what works...

FIXED
Latoc said:
I don't know about s3, but you should try a few kernels and see what works...
Click to expand...
Click to collapse
Well,
I tried a different kernel and still same issue. I flashed a TouchWiz based rom and it WORKED. Shows "connected". Battery life on moto 360 also vastly improved. Went from dead at 3:30 PM to 45% at same time!

I'm on DarkCM(11) for the xperia z1 and can't get it to work either.
Tested on my brothers stock xperia and that worked just fine. Il try downgrading to stock as well. :'(
If anyone gets CM on the z1 running with android wear please let me know.

I have a Oneplus One CM 11S works great on my old Gear Live and my new Sony Smartwatch 3
I read that MOTO 360 has (had) issues ?? Maybe the watch not the phones OS

Hi. My first post here and very New to all this. I have Samsung S4 with cm11 just got an Samsung galaxy gear2 neo and now i have to figure out how to get it to work with cm11 ? Can some body help

TechieInAK said:
I'm using CM 11 (4.4.4) on a S4 with Android Wear. No issues that I can see so far.
Click to expand...
Click to collapse
Sorry for bringing up an old post. I wanted to check in on your Android Wear connection to CM ROMs. I have a Sprint S4 (jfltespr) running CM12. I will be getting a LG G Watch R in a few days but someone else on our ROM thread was having issues with his Moto 360 and the CM12 ROM. Have you experienced any issues not connection or remaining in a sync loop?
Has anyone else experienced Android Wear issues with CM 11 or CM 12 on S4 phones? Particularly jfltespr?

Cant speak for the S4 but my LG G3 has had nothing but issues with my G Watch R since I flashed CM12. I reverted back to CM11 (recent build) and its working great, never disconnects. With CM12 it would disconnect at least 10-20 times a day its unusable.

I just installed the Google Play Edition Lollipop on my GS4 and it paired perfectly with my ASUS ZenWatch. Lollipop AOSP is AMAZING and i am so stoked it works so great!

Garrett 77 said:
Any ideas for running CM on the galaxy s3? Android wear will not switch to connected, shows, "connecting, running sync loop". Most functions work OK but the watch is dying terribly quick. I know the moto 360 battery is supposed to be iffy, but I should get more than 4-5 hours....
Click to expand...
Click to collapse
"Connecting, running sync loop" is just a different message for the same thing - it is activated on some ROMs(?) apparently when you have Developer mode enabled. But it works the same, and this message in itself doesn't indicate there should be any battery drain.
Of course something in the ROM might be causing this problem - a logcat from the watch would help in that case, but my guess is you just need to let everything install, settle down and then reboot both devices, and the drain will be gone...

My Zenwatch works perfectly with my Oneplus One running the latest CM11S. Having bluetooth on all the time does drain a bit more battery, but that's it.

I am having an issue with google wear (zenwatch) completing some tasks:
It fails to launch a phone call from google wear (my watch simply says "try again using your phone")
It fails to launch google play for music (it gives the same error as above)
Setting reminders using google keep (same error)
Text messages sent from android wear are NOT working.
Starting navigation on my watch using voice commands works.
Other basic apps appear to be working as well.
So far I've only noticed the above listed (maybe a few others) google apps and dialer that fail to launch when initiated from the watch, I have tried another dialer to see if that was the issue.
Anyone have any suggestions or insight on what I might be able to do in order to get google wear working 100% with this ROM?
Any help is greatly appreciated.

Mine works well
I have OnePlus One with CM11 and everything works quite well so far with my G Watch R