Develop Bugs

Quarx CM Nightly Releases - CM7 2012\05\06 & CM9 2012\05\09

With two different nightlies being released by Quarx at different times, I thought it would be a good idea to put both in one thread and keep the first post updated with the latest nightlies, install instructions, and links to gapps. All roms are on Quarx's server @ http://quarx2k.ru Use the builds for Kobe, Kobe is Bravo.
Rom Links
CM7 Nightlies Latest 2012\05\06
CM9 Nightlies Latest 2012\05\09
Gapps Links
Gapps GB 2011\02\28 - Download Here
Hacked Gapps GB 2012\04\04 - Download Here
Gapps ICS 2012\03\17 - Download Here
The only difference between GB Gapps and Hacked GB Gapps in the Hacked one comes with Marked updated to Play and it included Hacked Maps with International Navigation (not limited to the US).
Quarx CM7 Nightly - 2012\04\10
Bugs & Issues: Nothing major (I haven't seen any, but it is a nightly) Sometimes, the SDCard takes a while for the PC to recognize it (1-2 mins). Usually only happens 1 out of 10 times. Can't find the cause to replicate, but it happens sometimes.
Gapps - Use 2011\08\28 or my Hacked Gapps in Bravo Apps Forum. For instructions on how to get into recovery\rooting\2nd-init, please refer to one of the many tutorials in Bravo General.
Quarx CM7 Nightly Latest - 2012\05\06
BUGS
Haven't installed rom, only reporting the release.
CM7 Install Instructions
Reboot Into Recovery
Select Wipe Data\Factory Reset
Select Install Zip From SDCard
Locate and pick the CM7 Nightly
Flash Rom
Select Install Zip From SDCard
Locate and pick GB Gapps or Hacked Gapps
Flash GB or Hacked Gapps
Reboot, you're done
Quarx CM9 2012\04\17 (hwui and standard)
Bugs and Issues:
US ATT APN is not installed by default (Still not fixed, follow BravoMotorola's guide here.
USB Data Tethering Doesn't Work **Now Fixed
No Panorama Camera
Camcorder only records with 640x480
No screen off animation **Now Fixed
No Superuser on Multiboot **Now Fixed
Defy Parts doesn't list options **Now Fixed
sd-ext not detected (mmblk0p2)
cdrom not detected (mmblk1p17)
HWUI only--No flash videos.
Percentage Battery Icon can cause various glitches to occur with the status bar.
Quarx CM9 2012\05\06
BUGS
Bugs and Issues:
Flash doesn't work
Long Pressing Volume for Track Skip defaults to Music.apk unless unintalled.
Quarx CM9 2012\05\08
Haven't Installed Yet.......
Quarx CM9 2012\05\09
Haven't Installed Yet.......
CM9 Install Instructions
Reboot Into Recovery
Select Wipe Data\Factory Reset
Select Install Zip From SDCard
Locate and pick the CM9 Nightly
Flash Rom
Select Install Zip From SDCard
Locate and pick ICS Gapps
Flash ICS Gapps
Reboot, you're done
Many thanks to Quarx for all hard work he's done for us. Post any bugs or missing info and I'll update this post accordingly.

(Reserved)

So the camera and camcorder are both actually working?
Sent from my MB860 using XDA App

BravoMotorola said:
So the camera and camcorder are both actually working?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yes, but Camcorder only in 640x480. No other settings for resolution with stock camera app. No panorama either. I'm not sure if Defy has panorama yet.

check in
skeevy420 said:
Yes, but Camcorder only in 640x480. No other settings for resolution with stock camera app. No panorama either. I'm not sure if Defy has panorama yet.
Click to expand...
Click to collapse
check in....

amazing, thanks Quarx!
missing the framework crt off anim. but I can live

skeevy420 said:
Yes, but Camcorder only in 640x480. No other settings for resolution with stock camera app. No panorama either. I'm not sure if Defy has panorama yet.
Click to expand...
Click to collapse
Wow, that's honestly amazing. And do you see how many phones he has supported? How does he keep this all maintained? I just don't understand how it's even possible. Quarx does a wonderful job. I would have ditched the Bravo so long ago! LOL.

Yes, I agree completely. I'm just glad Motorola's lazy and made basicly the same device with different cameras and touch buttons (and a keyboard if you include the Milestone2).

New cm9 out. Will update main post when I install on phone and have access to my PC.

i will upload new build soon, because this build doesn't have root access.
HWA build has partial hwui

thanks
Quarx said:
i will upload new build soon, because this build doesn't have root access.
HWA build has partial hwui
Click to expand...
Click to collapse
thanks Quarx......

I've been using the Newest HWUI for about 30 minutes now. Almost everything listed has been fixed. Only bugs I've seen so far are that 2 partitions won't mount, sd-ext and cdrom; and youtube videos won't play. Other than that, I haven't seen any major issues. The ui likes to lag a bit, but I haven't even rebooted yet and rebooting fixed some of the hwui lag from yesterday's build.
Now that we have data tethering, I can finally move on to CM9 as a primary nand rom....Except for the 5 gigs of music I keep on sd-ext....looks like I get to format and partition my sdcard later.
I'm about to install the non hwui version and I'll post back on how it goes.
5MIN UPDATE
HWUI Started rebootlooping. All I did was take picture, shoot video, crashed panoroama, enabled data tethering, and watched(tried to) a video on youtube. My guess was it was panorama. If anyone else rebootloops, post what you think might have caused it. BTW rebootlooping is what I call when the phone works fine, reboots out of nowhere to bootanimation, works fine for a while and then back to bootanimation and repeat.
NON HWUI UPDATE
Youtube works. UI is smooth. Other bugs same. Great rom overall.

i try to download CM9-20120417-NIGHTLY-kobe(hwui).zip and CM9-20120417-NIGHTLY-kobe.zip, but where i open it. it's appears "unknown format or zip error"...
downloading with google chrome. previous versions fine...

NikolasV said:
i try to download CM9-20120417-NIGHTLY-kobe(hwui).zip and CM9-20120417-NIGHTLY-kobe.zip, but where i open it. it's appears "unknown format or zip error"...
downloading with google chrome. previous versions fine...
Click to expand...
Click to collapse
I'm not sure why they don't work for you. Both downloaded and installed fine for me.
Also, the nonhwui version has randomly rebooted twice on my in the past 12 hours (maybe more while I was sleeping, Its hard to check that). The only thing I was doing was using usb tethering at the time. It doesn't really surprise me since we just got usb tethering with CM9, prolly just some kinks that need worked out. Even with the random reboots its an awesome rom.
@Quarx, could you add the following line to /system/etc/apns-conf.xml. Its the US ATT APN.
<apn carrier="ATT" mcc="310" mnc="410" apn="wap.cingular" user="[email protected]" mmsc="http://mmsc.cingular.com" mmsproxy="wireless.cingular.com" mmsport="80" type="default,supl,mms" />

is anyone having trouble getting data connection? i had to manually input the ATT apn. and then when i switched on data, H logo came on. but i wasn't able to use the browser, go to the play store, etc..
suggestions? i'm on the 4/17 non-hwui build.

syllogyking said:
is anyone having trouble getting data connection? i had to manually input the ATT apn. and then when i switched on data, H logo came on. but i wasn't able to use the browser, go to the play store, etc..
suggestions? i'm on the 4/17 non-hwui build.
Click to expand...
Click to collapse
I haven't had any data problems, just to check I swithched to 3g and used data tethering to post this message from my pc. Also, it should be 3g above signal bars on CM9, not H like in CM7. Make sure you're not in 2g only mode, and if that doesn't work, try enabling National Data Roaming. I used to have to use National Data Roaming awhile back on 3g to work with CM7 (not anymore though).
Did you enter everything exactly? One wrong character will cause it to fail and not connect.
I really need to make a CM9 APN Patch. I just figured Quarx would have that fixed by now, so I haven't.
If you look a few posts up, you'll see the correct line that needs to be added to /system/etc/apns-conf.xml. You can manually add that line in preflash, or add it in afterwords and then use 0664 permissions (adb shell chmod 0644 /system/etc/apns-conf.xml) or just use root explorer and make its permissions look like everything else in that directory.
I'll attach the cm7 apns-conf.xml. It'll work with CM9. Remove the .txt, open a terminal in the directory with the xml, then just push to the phone with (adb push ./apns-conf.xml /system/etc/apns-conf.xml) then use (adb shell chmod 0644 /system/etc/apns-conf.xml). Parenthesis aren't needed, just using them to distinguish the commands from the text. Or use a root explorer. Just make sure you set the proper permissions or you may not boot.
I will add that data does seem a bit slower with CM9 than CM7 right now, but that could just be the time of day and a possible 3g load on my cell tower. And I haven't used 3gTurbocharger yet.
Does anybody else get random reboots out of nowhere when doing nothing what so ever? I get one every hour or two it seems. I still think its data tethering causing the reboots. I need to leave a terminal running adb logcat to catch what may be causing that. Other than the random reboots, I'm loving the new CM9 Build.

thanks, tried all of that. still same problem. when i try to access a webpage, usually if i don't have internet connection it will show that "browser can't connect to webpage", but instead i'm getting a blank screen with a line that says "access to the url is blocked". sigh i guess i'll just wait for the next build, hopefully flashing will fix it.

I am having issues with the status bar freezing up and the only way to fix it is to revolt. But overall it is a great Rom.
Sent from my Kindle Fire

syllogyking said:
thanks, tried all of that. still same problem. when i try to access a webpage, usually if i don't have internet connection it will show that "browser can't connect to webpage", but instead i'm getting a blank screen with a line that says "access to the url is blocked". sigh i guess i'll just wait for the next build, hopefully flashing will fix it.
Click to expand...
Click to collapse
Sounds like your behind a proxy or firewall. Have you installed any firewall or access control programs similar to Pdroid? Does the internet work on wifi? Other than that, have there been storms in you area lately? Have you been playing with build.prop?
About a month or so ago, I was having similar issuss, then I realized Droidwall installed itself (along with every app I ever installed) and Droidwall was blocking network access. Its possible the Gapps app sync at first boot installed something that's giving you problems.
Its kind of a guessing game now. The only network problem I have now, other than APN, is the random reboots that occur when using data tethering. You could try installing a different browser. I like Dolphin HD. I actually use Dolphin to test undervolting....just open a ton of loading tabs, it'll crash after 8-10 if you volted too low.
If an alternate web browser doesn't work, try the baseband switcher and use Argentina RT. Next try using wifi. If the internet doesn't work with wifi its probably bad settings\firewall program. After that, install CM7 or MIUI on multiboot and see if they have mobile data. If they don't, then your 3g tower may be down. BTW, I've only installed Mortplayer and Mortplayer Widget. I like to run as stock as possible when I'm bug testing.
I'm suggesting so much because I don't have much to go on other than its not the APN and you're using CM9 0417 non hwui.

feistygoat10 said:
I am having issues with the status bar freezing up and the only way to fix it is to revolt. But overall it is a great Rom.
Sent from my Kindle Fire
Click to expand...
Click to collapse
Revolt??? I'm assuming you mean reboot.
HWUI or not? If its hwui, then it doesn't surprise me. The status bar was my first FC on hwui, followed by Trebuchet. I haven't had the status bar freeze on the regular version.
Have you messed with the Notification Power Widget? I remember it had issues on CM7 at the end of February\beginning of March. Back then, the settings wouldn't stick and it would act wonky until a reboot. All system settings acted funny until reboot when that bug occurred.

Android Revolution HD 7.0.0.0 camera problem

Hi all,
Just installed Android Revolution HD version 7.0.0.0 and now the camera isn't working properly:
When the photo is taken, there is no "confirmation" with the small animation that shows the picture zooming out in the corner.
When you try to watch videos the phone reboots or / video does not appear in the camera folder list.
I tried installing the stock version again, but the camera problems are still there. Could this be because of an edited Camera.apk file? Could it be one of the tweaks in the installation screen? (writeback , etc) ? I also installed again without the tweaks but the problems are still there.
I now installed Android_Revolution_HD-One_X_7.1.0 and the camera seems to work better but when I have low battery neither the camera or the video work, the buttons are disabled and it takes no pictures. Is this a tweak or a bug?
Finally, I think that version 7.0.0.0 changed a setting that affects the whole phone and all other roms that I flash, since even the stock rom is affected now by this camera problem. I 'think' it might be the data_writeback tweak, but now I can't disable it?
Any help very appreciated.

htckt said:
Hi all,
Just installed Android Revolution HD version 7.0.0.0 and now the camera isn't working properly:
When the photo is taken, there is no "confirmation" with the small animation that shows the picture zooming out in the corner.
When you try to watch videos the phone reboots or / video does not appear in the camera folder list.
I tried installing the stock version again, but the camera problems are still there. Could this be because of an edited Camera.apk file? Could it be one of the tweaks in the installation screen? (writeback , etc) ? I also installed again without the tweaks but the problems are still there.
I now installed Android_Revolution_HD-One_X_7.1.0 and the camera seems to work better but when I have low battery neither the camera or the video work, the buttons are disabled and it takes no pictures. Is this a tweak or a bug?
Finally, I think that version 7.0.0.0 changed a setting that affects the whole phone and all other roms that I flash, since even the stock rom is affected now by this camera problem. I 'think' it might be the data_writeback tweak, but now I can't disable it?
Any help very appreciated.
Click to expand...
Click to collapse
All the issues you mentioned above seems to work perfectly for me. Did you do a full wipe when installing 7.0.0? Has is ever successfully worked on any other rom?

dr9722 said:
All the issues you mentioned above seems to work perfectly for me. Did you do a full wipe when installing 7.0.0? Has is ever successfully worked on any other rom?
Click to expand...
Click to collapse
All other versions of ARHD used to work normally, including the camera. Now watching videos freezes the phone or restarts.
I also installed Insert Coin yesterday in case it fixes the tweaks from ARHD but the camera is still not working properly.

Did u do full wipe?

I'm also experiencing this problem. What should I do?

shiningarmor Did u do full wipe?
I did a full wipe yes, before the installation. Not sure if I did one afterwards (when installing the stock rom or ARHD v 6.0.0.0). You think that would reset all the tweaks?
monchee said:
I'm also experiencing this problem. What should I do?
Click to expand...
Click to collapse
The only thing that fixed the camera file system (saving videos and viewing them and also the crashes) was installing Pro Capture or some other alternate camera app and saving the files with that one, afterwards the default camera started working properly as well.
BTW, I installed Insert Coin 7.0.0.0 and that fixed the camera as well, but try using Pro Capture free also and saving some picture with that one.

SOLVED:
This resets the camera app and all the file saving/video playback becomes normal.
If you had enabled the data_writeback tweak there are chances that the camera will stop saving pictures normally (At least the Data_writeback seems to be the most relevant tweak towards file handling).
In case your camera is stuffed up in ARHD 7.0.0.0, install Insert Coin 7.0.0.0, then do a ARHD Super Wipe and then install ARHD 7.0.0.0 again without any of the tweaks. Now you can also update to ARHD 7.1.0.0 with a working camera.

4.2 Camera and the DInc.

Has anyone been able to get the 4.2 camera on the Dinc? I've been trying to get it to work on mine but I have had no luck. If anyone has, would please show how you got it to work? thanks!

ck04 said:
Has anyone been able to get the 4.2 camera on the Dinc? I've been trying to get it to work on mine but I have had no luck. If anyone has, would please show how you got it to work? thanks!
Click to expand...
Click to collapse
When I saw this, I though, "Your'e crazy!" But I tried it anyway...yeah, I'm crazy too...Amazingly, it actually works!! It's pretty slow (and the camera preview goes wonky just like the stock JB camera app), and video recording is broken on this ROM currently (Pons CM10-Unofficial-11-01). But the 4.2 camera actually works.
I copied the files over manually and fixed permissions (I used X-plore, but Root Explorer or adb would work as well), that way I could back up all the files I was replacing in case things went ugly. I quickly found:
The Problem. There's not enough room on the system partition for this newer (bigger) camera app and for the extra libs it requires. SO it will fail if you just try to flash the .zip. The easiest way to get it to work is to use Titanium Backup to uninstall some stuff. First to go is Gallery (we're replacing that), then I uninstalled Email, Exchange Services, Setup Wizard, Google One Time Init, and Trebuchet (make sure you have another launcher installed before you remove Trebuchet). THen, it was just a matter of copying the new files into place, fixing their permissions, and rebooting. But if you clean up some space on /system, you should be able to install the .zip from recovery and be good to go.

musical_chairs said:
When I saw this, I though, "Your'e crazy!" But I tried it anyway...yeah, I'm crazy too...Amazingly, it actually works!! It's pretty slow (and the camera preview goes wonky just like the stock JB camera app), and video recording is broken on this ROM currently (Pons CM10-Unofficial-11-01). But the 4.2 camera actually works.
I copied the files over manually and fixed permissions (I used X-plore, but Root Explorer or adb would work as well), that way I could back up all the files I was replacing in case things went ugly. I quickly found:
The Problem. There's not enough room on the system partition for this newer (bigger) camera app and for the extra libs it requires. SO it will fail if you just try to flash the .zip. The easiest way to get it to work is to use Titanium Backup to uninstall some stuff. First to go is Gallery (we're replacing that), then I uninstalled Email, Exchange Services, Setup Wizard, Google One Time Init, and Trebuchet (make sure you have another launcher installed before you remove Trebuchet). THen, it was just a matter of copying the new files into place, fixing their permissions, and rebooting. But if you clean up some space on /system, you should be able to install the .zip from recovery and be good to go.
Click to expand...
Click to collapse
I did exactly what you put and it WORKED!!! you have no idea how excited I am thank you so very much!

Just by way of confirmation, it does work (and is easier) to install the 4.2 camera this way:
1. Install your favorite JB ROM and gapps; boot the phone.
2. Using Titanium, uninstall gallery, and a few other things as mentined in post #2.
3. Boot into recovery again and install the 4.2 camera zip. (the one that's patched to work on non-nexus devices, procured elsewhere)
4. Boot the phone again and enjoy the goodness!
If anybody figures out a way to get anything useful out of photosphere on this phone, let me know.

musical_chairs said:
Just by way of confirmation, it does work (and is easier) to install the 4.2 camera this way:
1. Install your favorite JB ROM and gapps; boot the phone.
2. Using Titanium, uninstall gallery, and a few other things as mentined in post #2.
3. Boot into recovery again and install the 4.2 camera zip. (the one that's patched to work on non-nexus devices, procured elsewhere)
4. Boot the phone again and enjoy the goodness!
If anybody figures out a way to get anything useful out of photosphere on this phone, let me know.
Click to expand...
Click to collapse
All good advice, and uninstalling unneeded system apps is prudent with JB Roms. But to short circuit all this - I simply use the Camera360 app, which I find to be much better than the native camera app.

CyanoLou said:
All good advice, and uninstalling unneeded system apps is prudent with JB Roms. But to short circuit all this - I simply use the Camera360 app, which I find to be much better than the native camera app.
Click to expand...
Click to collapse
Except this thread is about the 4.2 camera which has Photosphere it in, not the stock app itself.

Well photosphere seems to be pretty much a functional failure on the Dinc, but the new gallery app is pretty cool. It's fast (it took some time to 'settle in'), plus the photo editing features are pretty neat. I'm liking it!

do you have a link where the 4.2 camera zip is? I've been looking for days to find a way to get the camera working on this dinc running tinys cm10. if there is another thread with a detailed walkthrough or if you could maybe post one to help those like me looking for this camera fix it would be much appreciated. desperately need to get this monkey off my back so I can pass this phone on. thanks!
Sent from my XT875 using xda premium

homeskool said:
do you have a link where the 4.2 camera zip is? I've been looking for days to find a way to get the camera working on this dinc running tinys cm10. if there is another thread with a detailed walkthrough or if you could maybe post one to help those like me looking for this camera fix it would be much appreciated. desperately need to get this monkey off my back so I can pass this phone on. thanks!
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
The 4.2 camera being discussed in this thread had been ripped from the Nexus 4 and patched by Android Police (I believe) to work on other phones. I don't have the link handy, but I'm not sure it would do you any good anyway. What are you trying to fix? The camera (except for video recording) works on tiny's CM10, works better than the 4.2 camera actually because the camera preview goes nuts sometimes on the 4.2 camera, and tiny's CM10 uses the legacy (ICS) camera which does not have the preview issues. If you really want the 4.2 camera, an easier way to get it is to flash tiny's CM10.1, but like I said, this will have the preview issues. The only difference between the default CM10.1 camera and the patched 4.2 camera is Photosphere, which does not work on our phones anyway.
If you're looking for a camera 'fix' for CM10, the only thing that needs fixing is the camcorder, and for that you have two options:
1. Low-quality video recording with VideoCam Illusions, free on the Play Store
2. Use a Gingerbread (or older) ROM.

sorry for misunderstanding, I've been looking everywhere to figure out the issues I'm having with this dinc. I can't get the camera working or Netflix running tinys cm10. I don't think it's the Rom but I can't figure out where I've gone wrong. I've been lurking these forums for a while and have been able to troubleshoot the three other devices pretty good with the amazing info on here, but this one is getting the best of me at the moment. bought this dinc reconditioned, it was running 2.3.4 and I followed a tutorial to downgrade to 2.2 and root and get s-off with cwm. I upgraded to the latest cwm recovery and have flashed this rom 3 times trying to make sure it was clean. just keep getting a black screen when I try any camera app until it force closes. when I play a movie on Netflix everything works but the video is a black screen, even the sound plays. I realize this is in the wrong place but I can't post in dev yet, maybe I should start a new thread?
Sent from my ADR6300 using xda app-developers app

homeskool said:
sorry for misunderstanding, I've been looking everywhere to figure out the issues I'm having with this dinc. I can't get the camera working or Netflix running tinys cm10. I don't think it's the Rom but I can't figure out where I've gone wrong. I've been lurking these forums for a while and have been able to troubleshoot the three other devices pretty good with the amazing info on here, but this one is getting the best of me at the moment. bought this dinc reconditioned, it was running 2.3.4 and I followed a tutorial to downgrade to 2.2 and root and get s-off with cwm. I upgraded to the latest cwm recovery and have flashed this rom 3 times trying to make sure it was clean. just keep getting a black screen when I try any camera app until it force closes. when I play a movie on Netflix everything works but the video is a black screen, even the sound plays. I realize this is in the wrong place but I can't post in dev yet, maybe I should start a new thread?
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Netflix is broken on this device past gingerbread. I've yet to hear a single user report video on Netflix as working.
Do you remember having a working camera when you first started using it? It could be hardware failure for the camera. Also which gapps file did you flash? If you flashed the wrong one it could cause funkiness. If you didn't flash any, the camera should be working. I know that doesn't make sense but try to answer these questions as best as you can.

I followed the link to the gapps from tinys cm10 thread and downloaded jb 20121011 signed. I'll try without gapps tomorrow to see what that does. I hadn't begun to look into the Netflix issue yet so thank you for saving me the time on that. if that's not the right gapps then I'll try another, I appreciate the help, thank you. thanks for an awesome Rom btw, I have yet to find one this nice for any other device I'm using. Happy New year!
Sent from my ADR6300 using xda app-developers app

I'm going to start a new thread since I need help figuring this camera problem out and I've already derailed this thread enough. any mods feel free to delete my posts in here if you see fit. thanks!
Sent from my XT875 using xda premium

[Q] Can't connect to camera on AOSP Roms?

Hi, I can't seem to connect to my camera after flashing my ROM. I get "Camera Error: Can't connect to the camera". I'm using an N7105
I've tried:
1. CM10.1 and AOKP-JB-mr1-build6 roms. Restoring to the stock ROM made the camera work again, but flashing to the AOSP roms again after that breaks the camera.
2. Tried the NEAK kernel.
3. Tried removing the sdcard.
4. Tried fixing permissions in CWM.
I noticed that this seems to be an issue with AOSP Roms and S3s, but I can't seem to find a fix for the Note II. Is there one?
Thanks in advance!

Try some other kernel....
Sent from my GT-N7100 using xda premium

Any solution to this? I'm experiencing the same phenomenon, nothing seems to remedy it. Flashed different roms, kernels, etc.

Did u guys used touch focus or the camera app wont Just open? The aosp camera works fine but Whenever u use the touch focus while flash is set on : always on: then it will FC.. reboot and try again.. (my experience)
Cheers
Sent from my GT-N7100 using xda premium

Nah, for me it just won't open up at all, in any AOSP ROM i try. Full wipes of system, caches, etc. I don't know what else to try.
App starts, I see controls and black screen, then "Cannot connect to camera"

styx66 said:
Nah, for me it just won't open up at all, in any AOSP ROM i try. Full wipes of system, caches, etc. I don't know what else to try.
App starts, I see controls and black screen, then "Cannot connect to camera"
Click to expand...
Click to collapse
Exactly the same problem for me. Tried multiple camera apps all with the same effect.

Im aware that this is for the Galaxy S3 but looks like a similar problem and might be worth trying out.
http://forum.xda-developers.com/showthread.php?t=2113526
I will give it a go when I get a chance but busy at work today so may not happen any time soon.

I find this app https://play.google.com/store/apps/details?id=com.moblynx.camerajbplus
to be the best alternative.
Sent from my GT-N7100 using Tapatalk 2

Its not about the app. Its about the Camera. No app can connect to the camera because the firmware doesnt exist in the AOSP ROMs, only in the stock ROMs

I think I read that a recent CM nightly made some kind of stride forward in the camera dept. Haven't tested it, as am surprised to find myself happy with the stock ROM (albeit debloated).
from tapatalk (Galaxy Note 2)

Does it have to do with fixing permissions? I had this same error on my T-mobile Note 2 when I tried using an AOSP rom. I tried re-wiping, flashing etc to no avail. I was just getting ready to try an updated version to see if this fixed it.

harroguk said:
Its not about the app. Its about the Camera. No app can connect to the camera because the firmware doesnt exist in the AOSP ROMs, only in the stock ROMs
Click to expand...
Click to collapse
Ofcourse it does, prior to installing this app the default camera was working just fine with slimbean which is based off of AOSP. Ive only changed my default camera because of the extra options, otherwise default work. Get your facts straight. Also i can connect to the camera just fine using any application including social and media apps..

bushako said:
Ofcourse it does, prior to installing this app the default camera was working just fine with slimbean which is based off of AOSP.
Click to expand...
Click to collapse
Okay, so maybe it has been added to that ROM or maybe your camera has a different firmware to mine. For reference my camera firmwares are
REAR CAMERA:
Cam FW Ver: ZMGA01
Phone FW Ver: ZMGA01
FRONT CAMERA:
Cam and Phone FW Ver: S5K6A3

So after a couple of days of research I have managed to solve this problem.
Problem
When using a non-stock rom if you try to open ANY camera application that uses the rear camera you get the message "Can't Connect to camera" and the application force closes.​Solution
Flash back to a stock ROM where the camera works and root your device.
Dial *#34971539# in stock dialer.
Check your camera vendor using "Phone/CAM FW Ver Check". For me it was ZMGA01
Install Root Explorer from the Google Store
Use Root Explorer to navigate to /data/cfw/
Copy the SlimISP_xx.bin to your SDCARD where xx = the first two letters of your firmware. For me it was SlimISP_ZM.bin
Flash the ROM you wish to use. I installed CM10.1
Using Root Explorer place the SlimISP_xx.bin into /data/cfw/
Change the permissions on the file to 775 (rwxrwxr-x)
Change the owner to System
Change the group to Media
Launch your camera app of choice
Take photos.
I have submitted my camera firmware file to CM10.1 so hopefully if anyone else has this camera it should start working for you i you flash the latest nightly in a few days.
I would rate this as something that is easy to do yourself, the biggest problem I had was researching it.
Thanks,
Harroguk

harroguk said:
So after a couple of days of research I have managed to solve this problem.
Problem
When using a non-stock rom if you try to open ANY camera application that uses the rear camera you get the message "Can't Connect to camera" and the application force closes.​Solution
Flash back to a stock ROM where the camera works and root your device.
Dial *#34971539# in stock dialer.
Check your camera vendor using "Phone/CAM FW Ver Check". For me it was ZMGA01
Install Root Explorer from the Google Store
Use Root Explorer to navigate to /data/cfw/
Copy the SlimISP_xx.bin to your SDCARD where xx = the first two letters of your firmware. For me it was SlimISP_ZM.bin
Flash the ROM you wish to use. I installed CM10.1
Using Root Explorer place the SlimISP_xx.bin into /data/cfw/
Change the permissions on the file to 775 (rwxrwxr-x)
Change the owner to System
Change the group to Media
Launch your camera app of choice
Take photos.
I have submitted my camera firmware file to CM10.1 so hopefully if anyone else has this camera it should start working for you i you flash the latest nightly in a few days.
I would rate this as something that is easy to do yourself, the biggest problem I had was researching it.
Thanks,
Harroguk
Click to expand...
Click to collapse
Dude awsomeee thanks so much was searching for the solution for days ,,, thanks again a lot...

harroguk said:
So after a couple of days of research I have managed to solve this problem.
Problem
When using a non-stock rom if you try to open ANY camera application that uses the rear camera you get the message "Can't Connect to camera" and the application force closes.​Solution
Flash back to a stock ROM where the camera works and root your device.
Dial *#34971539# in stock dialer.
Check your camera vendor using "Phone/CAM FW Ver Check". For me it was ZMGA01
Install Root Explorer from the Google Store
Use Root Explorer to navigate to /data/cfw/
Copy the SlimISP_xx.bin to your SDCARD where xx = the first two letters of your firmware. For me it was SlimISP_ZM.bin
Flash the ROM you wish to use. I installed CM10.1
Using Root Explorer place the SlimISP_xx.bin into /data/cfw/
Change the permissions on the file to 775 (rwxrwxr-x)
Change the owner to System
Change the group to Media
Launch your camera app of choice
Take photos.
I have submitted my camera firmware file to CM10.1 so hopefully if anyone else has this camera it should start working for you i you flash the latest nightly in a few days.
I would rate this as something that is easy to do yourself, the biggest problem I had was researching it.
Thanks,
Harroguk
Click to expand...
Click to collapse
/data/cfw/ empty for me

I believe on some ROMs the camera firmware is kept somewhere else (Obviously) filename format should be the same though.
Posted from my phone. Please excuse my bad spelling.

harroguk said:
I believe on some ROMs the camera firmware is kept somewhere else (Obviously) filename format should be the same though.
Posted from my phone. Please excuse my bad spelling.
Click to expand...
Click to collapse
The mod is not anymore necessary, look a the cyanogen install package under /system/vendor/firmware
All the firmware have been submitted.. but I had the issue...
I fixed the whole thing using NEAK kernel.

FUSIONdev said:
The mod is not anymore necessary, look a the cyanogen install package under /system/vendor/firmware
All the firmware have been submitted.. but I had the issue...
I fixed the whole thing using NEAK kernel.
Click to expand...
Click to collapse
Hi,
i have changed rom to cyanogen 10.2 because my original rom not working camera (error connecting to camera). so i tried to reset to defaults with same result. I changed rom to cyanogen 10.2 (it was very good) and i have the same camera problem. I changed with another N7100 camera (in other phone it worked fine ) and it work for 1 day (in the other phone a put the "not working camera" and it worksssss) . So i think tnat is not a camera hardware problem. In cyanogen the dialer pressing test function doesn't work and in "/data/cfw" directory i have 8 files : SlimISP_BH, SlimSP_GD, SlimSP_GH, SlimSP_GK, SlimSP_ZD, SlimSP_ZH,SlimSP_ZK,SlimSP_ZM files. I have to had only one of this (i don't know my original firmware) or the cyanogen generic N7100 rom have all camera firmware to logically work with all N7100 firmware? I think that every specific firmware phone get automatically its file for the firmware they have. But i think that all firmware in the same direcotry can overload the rom information firmware too. I need to return to stock and check with original rom by dealer what firmware i have ? It was an original N7100 tim branded phone (samsung changed already 1 time camera in warrenty time but after 2 months the same error). I don't want to think its a logic board problem because or work or not work. I think its a "stupid" firmware problem.
Francesco

[Discussion]How to re-enable full Photochrom on INT.10.5.11/EU.10.5.10

As we all know by now, the new update(INT.10.5.11/EU.10.5.10) changed how the photochrom work
now, it's working with the main sensor, and act like a filter, it's working only outdoor, with a minor effect
The new photochrom is like 10% of what it used to be.
I'm trying to re-enable the full Photochrom experience
For now, I've had tried these three ways to re-enable it, and NONE of if work
I tried to replace the OnePlusCamera.apk to the older version, doesn't work
I tried to replace these following files from vendor to the older version
Code:
Code:
/vendor/lib/camera/*
/vendor/lib/hw/camera.qcom.so
/vendor/lib64/camera/*
/vendor/lib64/hw/camera.qcom.so
but still, doesn't work.
And I can also confirm, the "fake device model" method doesn't work either.
(for IN2020 Chinese model, it fake the device model to other region, so it won't block the photochrom filter, work at EU.10.5.9/INT.10.5.10 for IN2020)
I can't seems to figure out what is changed between this & last update, that changed the photochrom behavior
If anyone can get it woking again, please let me know
BTW, the whole privacy concern is just nonsense, IT CAN'T SEE THROUGH CLOUTHES
Otherwise, you'll be naked every time you see a security cam, coz those things got IR too
OnePlus shouldn't disable/crippled a camera sensor on our phone, just for their own PR
UPDATE
The latest workaround is to use the FactoryMode app to "Test" the camera
First method is to unlock the FactoryMode
Follow this thread: [GUIDE] Unlock Factory Mode *root*
Then you can launch the camera test/camera preview in FactoryMode
Another way is to directly launch the CameraManualTest with adb command/local shell
Code:
For shell(require root):
su
am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
For adb(require PC):
adb shell am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
For wireless adb(require wireless adb debugging to be enabled):
[URL="https://github.com/lllsondowlll/OP8_Camera/blob/master/README.md"]https://github.com/lllsondowlll/OP8_Camera/blob/master/README.md[/URL]
These are still just workaround with FactoryMode, hope to see the original build-in camera method soon

Hoping for good solution for this problem, as it was cool feature I didn't have time to play with. Wouldnt have upgraded if I knew beforehand that this was the case.

Not only did the camera app update from 4.0.267 to 4.0.279, but the com.oneplus.camera.pictureprocessing updated from 4.0.79 to 4.0.81. I backed up both of these apps before updating using Apk Generator (play.google[dot]com/store/apps/details?id=com.aksapps.apkgenerator) but I'm not rooted so I can't replace system apps. You can try it and let me know though. Be sure to backup your apps in case it doesn't work.
drive.google[dot]com/folderview?id=18D_XwiiTJxfuhaV3TqJ5N4cDyYg_2gkE
There's a couple other camera related stuff I backed up but it doesn't look like changes were made to those. Links are censored with [dot] to get around the 10 post restriction.

I'm still on 10.5.9 EU.
Let me know if you need anything from mine..
I'm not rooted as yet so it can't be pulled without root I can't help as yet.

GiveMeAnthony said:
Not only did the camera app update from 4.0.267 to 4.0.279, but the com.oneplus.camera.pictureprocessing updated from 4.0.79 to 4.0.81. I backed up both of these apps before updating using Apk Generator (play.google[dot]com/store/apps/details?id=com.aksapps.apkgenerator) but I'm not rooted so I can't replace system apps. You can try it and let me know though. Be sure to backup your apps in case it doesn't work.
drive.google[dot]com/folderview?id=18D_XwiiTJxfuhaV3TqJ5N4cDyYg_2gkE
There's a couple other camera related stuff I backed up but it doesn't look like changes were made to those. Links are censored with [dot] to get around the 10 post restriction.
Click to expand...
Click to collapse
Tried this method, didn't work either

GiveMeAnthony said:
Not only did the camera app update from 4.0.267 to 4.0.279, but the com.oneplus.camera.pictureprocessing updated from 4.0.79 to 4.0.81. I backed up both of these apps before updating using Apk Generator (play.google[dot]com/store/apps/details?id=com.aksapps.apkgenerator) but I'm not rooted so I can't replace system apps. You can try it and let me know though. Be sure to backup your apps in case it doesn't work.
drive.google[dot]com/folderview?id=18D_XwiiTJxfuhaV3TqJ5N4cDyYg_2gkE
There's a couple other camera related stuff I backed up but it doesn't look like changes were made to those. Links are censored with [dot] to get around the 10 post restriction.
Click to expand...
Click to collapse
Still, won't work
Why are they making this so hard to do?

I tried to replace anything seems remotely relate to camera in /vendor/lib and /vendor/lib64
nothing work, I think the change might not in /vendor?
By doing the file compare, i see these OnePlus service has been updated through this update, is it possible they restrict the camera with those service?
Code:
/system/priv-app/oneplus-framework-res
/system/priv-app/OPCoreService
I tried to replace them with older file, but system will be shutdown after boot
Anyone got any more ideas?

Cattell said:
I tried to replace anything seems remotely relate to camera in /vendor/lib and /vendor/lib64
nothing work, I think the change might not in /vendor?
By doing the file compare, i see these OnePlus service has been updated through this update, is it possible they restrict the camera with those service?
Code:
/system/priv-app/oneplus-framework-res
/system/priv-app/OPCoreService
I tried to replace them with older file, but system will be shutdown after boot
Anyone got any more ideas?
Click to expand...
Click to collapse
How about trying to connect only Photochrom camera with an test/debug app?

ster88 said:
How about trying to connect only Photochrom camera with an test/debug app?
Click to expand...
Click to collapse
You gave me an idea. Tested with factory mode and camera tab then forth camera preview. Interesting, can still see the preview with it seeing through thin plastics even indoors. So, whatever they did with this update can probably be circumvented, just not sure how hard it would be. If you want to check it out, enable factory mode app then go to camera tab and do forth camera preview. Included screenshots of where to go and it still working.

jeffsga88 said:
You gave me an idea. Tested with factory mode and camera tab then forth camera preview. Interesting, can still see the preview with it seeing through thin plastics even indoors. So, whatever they did with this update can probably be circumvented, just not sure how hard it would be. If you want to check it out, enable factory mode app then go to camera tab and do forth camera preview. Included screenshots of where to go and it still working.
Click to expand...
Click to collapse
Wow it worked
Oneplus 8 Pro IN2023 10.5.10IN11BA
https://drive.google.com/file/d/1D5YRdOBKInFYQ2ns9r-eoefprCiUASj7/view
https://drive.google.com/file/d/1D9v40zFyMbiKLPFPLw36XzNUHCpK7gwE/view
https://drive.google.com/file/d/1D4JEyb-kJTCfzxiN0lYPhvvDcr2zX8Qr/view
https://drive.google.com/file/d/1D1FDJIRc_CmmIfh5P8IU3afeVkQfbCVS/view
Edit :
If you go to camera test in factory mode app, then you can take a picture with photochrom mode.
https://drive.google.com/file/d/1DNLkrOU8w-LI8TH4oZ8h6xOkeCd_Md1Q/view?usp=sharing
https://drive.google.com/file/d/1DKUJj2Xy4bKrJSot7CHtP3UYpV4LqIMg/view?usp=sharing

ster88 said:
Wow it worked
Oneplus 8 Pro IN2023 10.5.10IN11BA
https://drive.google.com/file/d/1D5YRdOBKInFYQ2ns9r-eoefprCiUASj7/view
https://drive.google.com/file/d/1D9v40zFyMbiKLPFPLw36XzNUHCpK7gwE/view
https://drive.google.com/file/d/1D4JEyb-kJTCfzxiN0lYPhvvDcr2zX8Qr/view
https://drive.google.com/file/d/1D1FDJIRc_CmmIfh5P8IU3afeVkQfbCVS/view
Edit :
If you go to camera test in factory mode app, then you can take a picture with photochrom mode.
https://drive.google.com/file/d/1DNLkrOU8w-LI8TH4oZ8h6xOkeCd_Md1Q/view?usp=sharing
https://drive.google.com/file/d/1DKUJj2Xy4bKrJSot7CHtP3UYpV4LqIMg/view?usp=sharing
Click to expand...
Click to collapse
Nice find. I knew someone would take a better look at all the options in that menu. At least there is a way to still use the photochrome mode now.

how to open the factory mode plz i dial *#808# and nothing happens it just clears everything on my dialer how to open factory mode on in2020 plus i m using one plus dialer

babsvsphudi said:
how to open the factory mode plz i dial *#808# and nothing happens it just clears everything on my dialer how to open factory mode on in2020 plus i m using one plus dialer
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlock-factory-mode-root-t4118527

How to enable factory mode, *#808# doesn't work I am not rooted.

Good work guys
Considering how difficult they tried to make it, I believe the best long term solution would be to have a specific app used just for this feature (mimicking this factory mode)
Else they would mess it up with more updates

i just rolled back my software version, so i have the function again

I'm on 10.5.11. but factory mode camera did not pick x-ray vision as mentioned. I tried several remotes and stuff. Any reason for that?

snovharry said:
I'm on 10.5.11. but factory mode camera did not pick x-ray vision as mentioned. I tried several remotes and stuff. Any reason for that?
Click to expand...
Click to collapse
It's not x ray vision. It's an IR camera and can only see through very thin plastics without IR shielding. It works on Amazon remotes and Vizio remotes that I've tried.

I found a way to launch the color filter camera without being root and without using MMI dial codes to access factory mode.
It is a bit impractical right now because I couldn't make it work on a terminal emulator app yet, but it works through the adb shell just fine.
Just run this from the adb shell:
Code:
am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
It will launch the manual camera test from the FactoryMode app right away.
Press the bottom right icon to switch the camera until you get to the IR camera.
I'm running on the 10.5.10.IN11BA build.

Shure. Naming it "x-ray" is only a metaphor for the effect.