No keyboard back-light or camera, cyanogenmod - Droid 2 General

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

Related

Camera failed to initialize

I can't use my back camera.. im not reaaly sure what happened. Before i was trying to get um frontcam and updating homebase rom after upgrade to 3.4 with 5.3a.. its gave me black lag screen and force close and it says camera failed to initialize after few try.. I did cam restore, full wipe, flashed stock rom it doesn't help.. I hope someone know what did I do wrong.. the front cam works ok.. its been a week I hope someone can help me fix this.. I can give donation for anyone fix this
Sent from my MB860 using Tapatalk
Sent from my MB860
Double posting certainly isn't going to help. To me it sounds like a hardware failure.
I have the same problem as you if solve the problem or have any information I'll be gratefull if you share it with me. Thanks
@ the home screen. Hit the Menu button, go to Settings>Applications?Manage Applications... Select all and find "camera" Open it an hit the "Clear Data" button. If it does not resolve, try also clearing data in Gallery as well. IF that doesn't work, could be a hardware issue. Hope this helps!
No luck until now but im quite sure its not a hardware problem. Is there any way to test camera hardware failure?
Sent from my MB860 using Tapatalk
Are you on a stock ROM? The reason I am asking is I have had a similar issue, but mine stemmed from me taking a swim with my phone. After I took 7 days to dry it out etc.. the phone powered up with no problem. The only problems I was having was with both cameras.. I was recieving the FC's and/ro Initialization errors...
At the time I was stock... I flashed the Pudding SBF 4.5.91 via RSDLite and my back camera started working with no FC. I do however have what I feel i is a hardware problem with my Front camera, as when I select it I just get a black screen,lock up, then FC on Camera. I will also get the Initialization errors. The only way to get any camera to work again is to go into the stock camera app and clear data. Then I can open any camera app back up again using the rear camera.
Have you tried different camera apps? Such as MIUI Camera, LG Camera, or Camera360 to see if you get the same message?
Im on hombase... I tried all camera apparently but none of them works. My frontcam works just fine... I wonder how to reinstall the camera firmware or update it.. I guess this problem occurred since I mod the ymfrontcam...
Sent from my MB860 using Tapatalk
Maybe you f'ed up pds partition, it contains camera calibration data and other stuff. But you would be seeing other issues as well if you did.
I had the same issue, I went into titanium backup and wiped data for the camera app
Sent from my CM860

Auto-rotate not working

Hi, today suddenly my phone didn't rotate the screen anymore when I rotated the phone to landscape. I had auto-rotate on. This problem had stayed for a while now and I have already rebooted my phone as well as turned off and on auto-rotate. I know the accelerometer is working because I used apps that use the accelerometer, so my guess is it's done software bug. I think it had happened before to me but briefly and it somehow got fixed. I'm wondering if this has happened to someone else and how you fixed it. Thanks!
Sent from my Nexus 4 using xda app-developers app
If u were referring to it auto rotating in the home screen, the stock launcher doesn't not do it
No not the home screen, any screen (browser, Facebook, mail, etc..)
Sent from my Nexus 4 using xda app-developers app
Try an app called ultimate rotate to force rotation in apps as a test
Sent from my Nexus 4 using xda premium
settings accessibility auto rotate
molesarecoming said:
settings accessibility auto rotate
Click to expand...
Click to collapse
Way to read the OP.
This just happened to me....I have auto-rotate checked in accessability and display...any help would be appreciated.
Happening to me now as well. Not sure whats causing it :-/
Auto Rotate
It is happening to me as well.
I don't know if it pertains to you or no as mine is rooted and it does only on AOKP Rom.
For now what I had is to install Screen Orientation app. It lets you toggle Forced Portrait / Forced Landscape mode from notification bar.
And i have checked auto rotation enable in settings.
Open Instagram, it forces portrait..
help
This is happening to me right now but much worse, I've toggled, rebooted, wiped, reflashed, flashed old backups, different kernels, different roms I was originally running AOKP with faux kernel and my auto-rotate had been working fine then I downloaded temple run and I couldn't tilt from side to side, I would re-calibrate but every sensor app I download says that my; Accelerometer, compass, light sensor, proximity sensor, temp, gyroscope, gravity sensor, linear acceleration, and rotation vector sensor don't even exist, the apps say there not there. I have no idea what more to do to reset them or fix them, they were all working fine before and then they just stopped.
Any ideas or information would be appreciated, the last thing I'm going to try is a full Odin flash back to stock everything (if that is even available yet for the nexus 4)
tech.central said:
This is happening to me right now but much worse, I've toggled, rebooted, wiped, reflashed, flashed old backups, different kernels, different roms I was originally running AOKP with faux kernel and my auto-rotate had been working fine then I downloaded temple run and I couldn't tilt from side to side, I would re-calibrate but every sensor app I download says that my; Accelerometer, compass, light sensor, proximity sensor, temp, gyroscope, gravity sensor, linear acceleration, and rotation vector sensor don't even exist, the apps say there not there. I have no idea what more to do to reset them or fix them, they were all working fine before and then they just stopped.
Any ideas or information would be appreciated, the last thing I'm going to try is a full Odin flash back to stock everything (if that is even available yet for the nexus 4)
Click to expand...
Click to collapse
i read something about losing sensors by using the 4.2.2 radio With a 4.2.1 Rom. anyways it's a documented issue. try going through the 4.2.2 threads. i believe that's where i saw it mentioned.
EDIT: here it is!
http://forum.xda-developers.com/showpost.php?p=37977813&postcount=3
searching the thread:
http://forum.xda-developers.com/search.php?searchid=146897726
smacking it worked
read on another forum that "a decently hard smack" would correct it.
they were right, Its working again.
solved mine
in my case, it was an app called gravity screen. uninstalled it, reboot phone, and the auto rotate is enabled now

[Q] Switching to front facing camera produces error. 'Camera not connected'.

Helllllo everyone!
So I apologize for being one of those people who just come here to ask questions. Unfortunately life doesn't have room for me spending time playing with my Android devices anymore, so having it 'work' is more important to me.
I am on 4.3, ParanoidAndroid 3.96. I am not on the latest because it took some time to have the app TouchControl work (with my Franco kernel), and Secure Settings etc. that I chose to just stick with it because it worked really well for me.
The problem!
I recently noticed that if I tried to switch to the front facing camera, it'd hang. After that, I would not be able to use my torch/led, and going into the camera would tell me that "The camera is not connected" or something like that. I could only fix this by clearing all the data on my Gallery, and shutting down, and then turning on again. Reboot would not work.
If I did that, I could go into my camera and use the rear camera fine. Take pictures, record video, etc. Torch works as normal. It's just that once I attempt to go into the front camera, this problem happens.
It's weird because I didn't flash anything or change any settings when this happened. I DID install https://play.google.com/store/apps/details?id=eu.mrogalski.saidit which wouldn't let me record a video while being used, but I since disabled/uninstalled it which solved that problem.
I have done a lot of googling on this problem, and noticed that I am not the only one who has this problem. For some people it seems like their phone is new, and some it just happens out of nowhere. For that reason I suspect it might be a hardware problem that can occur randomly, but it's weird that after triggering the problem, that my torch won't work anymore as well. Unless the torch is somehow tied to the camera/flash, and by triggering the problem when I try to access the front camera, it isn't able to 'call' the camera/flash anymore as a result?
I bought my Nexus 4 from Google in May 2013, so I believe I still have until May 2014 to RMA it, correct? Would I get another Nexus 4 at this point, or maybe I'd get a Nexus 5 instead?
Thanks in advance for any insight into my problem!
I know you would like to keep the rom you are on but to be on that rom you must have a custom recovery installed. So if I was you I would back you're rom up then flash something different to see if its hardware related or not . If so then return the phone.
Sent from my Nexus 4 using XDA Premium 4 mobile app
bladebuddy said:
I know you would like to keep the rom you are on but to be on that rom you must have a custom recovery installed. So if I was you I would back you're rom up then flash something different to see if its hardware related or not . If so then return the phone.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply.
I tried installing the latest PA rom, but came up with an error. I had the rom I was on originally still, so I tried wiping and flashing it again. Finished flashing, went and opened the camera and it still happened. Looks like it's a hardware problem then!
I guess I'll go look up a guide to flashing back to stock now.

[Q] Navigation buttons not working after 4.4.3 update

Has anyone faced similar issue? Here's bit of background. I was using Liquidsmooth custom ROM with navigation bar disabled and pie controls enabled for navigation. I used to to enable pie control to swipe from bottom border.
So, the day I got system update available notification (for 4.4.3), my pie control stopped working from bottom border. Just a coincidence I think. It was still working from other trigger positions though. I also had this incredible urge to see new update of Kitkat. So, I just got Google factory image of 4.4.3 & flashed it. Everything done, I got to home screen only to find out my navigation buttons are not working. That area is completely dead. Those buttons will randomly start working for some time. Only for a minute or so.
So I went back to the latest version of Liquid Smooth ROM. Pie control from bottom border & navigation bar is not working. Tried going back to stock 4.4.2 & take a 4.4.3 OTA. Still no go.
And to me, it seems a software issue since navigation buttons work in landscape mode. And the area where navigation buttons are in portrait mode also works fine for everything else. So, it's not as of that part of touch screen is dead.
So, to cut long story short, please help me out here guys!!! :crying::crying::crying:
Regards,
Mrugesh.
Did you find a solution to this? I know of a Nexus that also started having this problem and no clue how to fix.
Sent from my SM-T320 using Tapatalk
No clue dude... No resolution... I'm just using my Nexus with pie controls whichever way I can.... Thank God it's a Nexus. Else I'd have been screwed by now buddy.... But surprising to see no resolutions from XDA.
Sent from my Nexus 4 using XDA Free mobile app
Spoke to google support and they told me to return it for another device.
Sent from my SM-T320 using Tapatalk

[DISCUSSION] Problems & Bugs on stock CM11S

I created this thread in order to share the problems which I am facing on my 1+1. Hope can get resolved by CM soon... As well as others can discuss about the problem and solution (if available) that we are facing. State method if others can try reporduce the problem to confirm will the problem affect all other 1+1 device, if have screenshot the better.
Firstly, please state:
ROM version (Root Y/N, Other than CM11s don't discuss here, Nightly, Color OS etc.):
ROM mod (State which app will affect system files, from your opinion):
Custom kernel (Y/N, If yes please state kernel you've used):
Model & storage (CN/INT ver, 16/64G):
Recovery (Apparently has nothing to do with ROM I think, just state better)
Problem/bugs:
Okay, start with me...
ROM version: CM11s Rooted, XNPH25R - latest at the moment
ROM mod: AdAway, BusyBox 1.22.1, Xposed Framework 2.6
Custom kernel: NO
Model & storage: CN ver 16G
Recovery: PhilZ Touch 6.49
Problem/bugs:
USB OTG will be not functional when plug in while the screen is OFF, if screen is ON then no such problem, even if you insert USB OTG while screen off and reinsert back after waking the phone, the USB OTG still not working (suspect deep sleep cut off USB OTG power) - Temporary solution: Reboot the phone
MX Player crashes more often while playing with H/W decoder, however S/W decoder works flawlessly. Format Played - 480p FLV.S/W uses more battery consumption so I don't like it, I confirm the same type of video played on other phone doesn't have such MX Player FC problem (If it crashes too many times it will stop working at some point, you can't even play MP4 files with H/W decoder and or stock Gallery app - Temporary solution: Reboot the phone
GPS sometimes takes forever to lock - Temporary solution: Reboot the phone
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
As you can see all these problems can be fixed by rebooting the phone, so I guess it's ROM related problem.
ROM version: CM11s running XNPH25R
ROM mod: None, running stock and unrooted for now
Custom kernel: NO
Model & storage: 64gb sandstone black
Recovery: None
Problem/bugs:
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
Same issue with torch. I ended up disabling torch and music gestures.
Haven't had any other issues per se, but my battery hasn't been nearly as impressive as others have stated. I am going to continue monitoring it and will report back once I have solid information on battery usage.
I have the yellow hue at the bottem 25% of screen but its faint and not too noticeable. I am hoping its just temporary.
oneplusonepwns said:
ROM version: CM11s running XNPH25R
ROM mod: None, running stock and unrooted for now
Custom kernel: NO
Model & storage: 64gb sandstone black
Recovery: None
Problem/bugs:
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
Same issue with torch. I ended up disabling torch and music gestures.
Haven't had any other issues per se, but my battery hasn't been nearly as impressive as others have stated. I am going to continue monitoring it and will report back once I have solid information on battery usage.
I have the yellow hue at the bottem 25% of screen but its faint and not too noticeable. I am hoping its just temporary.
Click to expand...
Click to collapse
At battery stats see any other apps are draining your battery. In my case, sometimes Android OS/System, Google Play Service and Media Server are keeping awake draining the battery while screen is off, in that case, enable privacy guard deny them from keeping awake, or reboot your phone.
ROM version: CM11s running XNPH25R
ROM mod: Rooted with xposed framework, AdAway.
Custom kernel: Franco Kernel
Model & storage: 64gb sandstone black
Recovery: Stock
Firstly: I always like to disable the backlight illumination of the hardware buttons. This works perfect but it doesn't stick. After reboot, its back to lit up.
Secondly: Notification sounds can't be set on per app basis. For eg, Hangouts has its own notification tones and I like gmail and other email app to have different notification tone from the system wide one, however it doesn't happen. All apps use the system wide notification tone regardless of what I set separately on them. I guess this has something to do with the theme engine coz I chose tones from it.
Thirdly: when rotation is locked, camera interface doesn't rotate. I thought camera interface is meant to auto rotate regardless of the "rotate setting on or off"
Sent from my One using Tapatalk
ROM version: CM11s XNPH25R rooted
ROM mod: Why mess with a good thing?
Custom kernel: N
Model & storage: INT 64G
Recovery: PhilZ CWM
Lock screen delay doesn't work on built-in custom lock screen. Works fine otherwise.
ROM version: CM11S XNPH25R, not rooted
ROM mod: None
Custom kernel: N
Model & storage: INT 64G
Recovery: Stock
[ ] 2 Google Play Services force closes while setting up phone
[ ] Ringtone and default notification sound were reset to default once randomly
[ ] Double-tap to wake setting becomes checked again randomly after turning it off, but the feature is not re-enabled
[ ] Google Now keeps showing "Good morning / evening! Here are your current cards" and "Google Now is always working for you" cards even after swiping them away many times
[ ] In-call speaker volume is too low, MUCH lower than volume for everything else
[ ] Some ringtones and notification sounds are duplicated with different names
[ ] The screen seems to miss touches occasionally
[ ] "Ok Google" and Google voice searches only work if I speak VERY loudly
[ ] The phone occasionally sticks in landscape orientation and I have to shake it to get it to rotate back to portrait
[ ] Scrolling is not as smooth as my stock Nexus 5 (more dropped frames) in not all, but some apps. This could just be poor optimization, but I'm calling it a bug because really this phone should always perform better than a Nexus 5 because it has an 801 and 3GB of RAM.
Is there anyone who types fast on the OnePlus One?
Do you find it that it misses some keys sometimes and generally makes it hell to type on...
Does this have anything to do with it's multi touch issues?
Sent from my One using Tapatalk
ROM version: Stock CM11S XNPH25R, rooted
ROM mod: Busybox,Xposed
Custom kernel: No
Model & storage: CH 64G
Recovery: Philz
Problem:
Screen not wake when press power button,navigation light is on, but screen not wake. my solution for now is need to force restart.
Sent from my One using XDA Premium 4 mobile app
SleemLDJ said:
Is there anyone who types fast on the OnePlus One?
Do you find it that it misses some keys sometimes and generally makes it hell to type on...
Click to expand...
Click to collapse
Yes, I believe I have experienced this and quite often too.
Apart from the missed keystrokes, my phone reboots randomly every 30 mins or so. I haven't gotten around to root causing it.. Maybe due to ART (?)
ROM version: Stock CM11S XNPH25R, rooted
ROM mod: None
Custom kernel: No
Model & storage: INT 64G
Recovery: Stock
I have also issues with the touchscreen; some parts of the screen doesn't react on touch or swipe...For example when I touch the letter 'b' on the standard keyboard, its always the letter before or behind. In landscape modus it works well. Also games like candy crush and 2048 where you have to swipe alot on the screen and difficult to; sometimes it doesn't react on parts of the screen or it does something else ( to the right instead going down,...)
I 'm waiting since Friday for an answer...because I'm afraid its hardware failure
https://www.youtube.com/watch?v=SSmpYQYofOc
Sent from my LG-V500 using XDA Free mobile app
Maybe I'm just lucky I haven't come across any problems yet.
CM Version 11.0-XNPH25R
Completely Stock.
magnum73 said:
I have also issues with the touchscreen; some parts of the screen doesn't react on touch or swipe...For example when I touch the letter 'b' on the standard keyboard, its always the letter before or behind. In landscape modus it works well. Also games like candy crush and 2048 where you have to swipe alot on the screen and difficult to; sometimes it doesn't react on parts of the screen or it does something else ( to the right instead going down,...)
I 'm waiting since Friday for an answer...because I'm afraid its hardware failure
https://www.youtube.com/watch?v=SSmpYQYofOc
Sent from my LG-V500 using XDA Free mobile app
Click to expand...
Click to collapse
Oh god that looks terrible.
i haven't seen this mentioned yet, but sometimes when i open the Google keyboard in landscape mode, it will only show 1 line of keys. i fix it by force stopping the keyboard
Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app
cas8180 said:
Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
You are most likely missing a couple lib files, like hotword detection for Google now..
Sent from my Nexus S using XDA Premium 4 mobile app
Setting.Out said:
You are most likely missing a couple lib files, like hotword detection for Google now..
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
One of the moderators on the OP forums replied to my comment about the hotword detection and stated it is a known bug with CM and has been addressed and will be resolved in the next OTA.
cas8180 said:
Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
The speakerphone problem has been addressed in one of the recent nightlies. Call volume is good now. It is scheduled for the upcoming ota.
M9 just came out. Only in a matter of time we get the ota for the next update
jarjar124 said:
M9 just came out. Only in a matter of time we get the ota for the next update
Click to expand...
Click to collapse
Where are you guys seeing these updates. I went to cm's website but didn't see our device on there. Also tried googling it and didn't see it. Maybe I am just blind.
Edit:
Just found it nevermind...
Sent from my One using XDA Free mobile app
cas8180 said:
Where are you guys seeing these updates. I went to cm's website but didn't see our device on there. Also tried googling it and didn't see it. Maybe I am just blind.
Edit:
Just found it nevermind...
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Where
Sent from my One using XDA Free mobile app

Categories

Resources