Weirdest Camera Issue Ever - Verizon Samsung Galaxy S III

I have a Verizon S3 d2vzw with an unlocked bootloader runnign Oct M Android 6 custom ROM. When I use the back camera I takes pics just fine. When I use the front camera it takes pics just fine in low light i.e. when the light is to low to take a decent picture. When I move to a location where the light is good I get a force close. "Unfortunately Camera has stopped". The Camera is version 2.0.002 (7a32386e9-30) org.cyanogenmod.snap that comes with the ROM, but I tried it with Open Camera from the Play Store and I got the same issue. Has anyone ever heard of anything like this? Perhaps someone would be able to speculate...
Update
I now believe this is a CM-13 issue. I'm not certain if it applies to devices other than d2vzw, but all CM-13 based ROMs for d2vzw e.g. Oct-M and AICP, have this issue including CM-13 Nightlies. If you search "camera" in this thread you can read all about it: http://forum.xda-developers.com/gal...m-cyanogenmod-13-0-nightlies-verizon-t3269675 Also in the threads for Oct-M for d2vzw and AICP for d2vzw I've found the same issue being discussed. When I originally posted this I was using Oct-M and there was no talk about this issue in that thread and in all my noobiness I thought I was the only one in the world that had the problem. I didn't think of searching threads for all CM-13 based ROMs. In light of this discovery I'm questioning the usefulness of this thread.

bigbaluka said:
I have a Verizon S3 d2vzw with an unlocked bootloader runnign Oct M Android 6 custom ROM. When I use the back camera I takes pics just fine. When I use the front camera it takes pics just fine in low light i.e. when the light is to low to take a decent picture. When I move to a location where the light is good I get a force close. "Unfortunately Camera has stopped". The Camera is version 2.0.002 (7a32386e9-30) org.cyanogenmod.snap that comes with the ROM, but I tried it with Open Camera from the Play Store and I got the same issue. Has anyone ever heard of anything like this? Perhaps someone would be able to speculate...
Click to expand...
Click to collapse
Pretty unusual.
The phone is old and you're running old firmware. It's really hard to tell what the issue is. Could be a hardware or AOSP issue.
If you can take a logcat while the phone force closes and you can see how it fails. You can post that in the cm thread and see if you can get the developer to fix the problem. You can post it here and I'll tell you when it's failing.
Alternatively, you can attempt to boot up a stock based rom and see if that camera is still giving you problems.

Camera Firmware?
BadUsername said:
Pretty unusual.
The phone is old and you're running old firmware. It's really hard to tell what the issue is. Could be a hardware or AOSP issue.
If you can take a logcat while the phone force closes and you can see how it fails. You can post that in the cm thread and see if you can get the developer to fix the problem. You can post it here and I'll tell you when it's failing.
Alternatively, you can attempt to boot up a stock based rom and see if that camera is still giving you problems.
Click to expand...
Click to collapse
I was reading about camera issues and I read something about "camera firmware". I thought the phone's firmware included firmware for the whole phone. I guess that's why sometimes there's separate "modem firmware". I'll get a logcat done so someone with a clue can pehaps buy me a clue. I've been meaning to try Alliance ROM from beanstown to see if the problem persists with a stock based ROM. I was messing with it yesterday in a dark room and the front camera works fine 'til I turn on the light then I get a big fat FC as soon as i take a picture. No problems with back camera. I love my S3 and it's in very good shape, but I think it may be getting tired. I've been wanting a Nexus 6 or 6p for a while now. Those seem to be my only options since for now I'm stuck with Verizon. I think all bootloaders should have the option to be unlocked by the user. They could even put up a big scary warning, notifying us users of all the chaos that might ensue from recklessly unlocking our bootloaders. Here's one of the posts I found about camera firmware. http://forum.xda-developers.com/galaxy-s3/general/jb-4-1-2-camera-driver-t2006128
Thanks for your thoughts on all this wierdness.

bigbaluka said:
I was reading about camera issues and I read something about "camera firmware". I thought the phone's firmware included firmware for the whole phone. I guess that's why sometimes there's separate "modem firmware". I'll get a logcat done so someone with a clue can pehaps buy me a clue. I've been meaning to try Alliance ROM from beanstown to see if the problem persists with a stock based ROM. I was messing with it yesterday in a dark room and the front camera works fine 'til I turn on the light then I get a big fat FC as soon as i take a picture. No problems with back camera. I love my S3 and it's in very good shape, but I think it may be getting tired. I've been wanting a Nexus 6 or 6p for a while now. Those seem to be my only options since for now I'm stuck with Verizon. I think all bootloaders should have the option to be unlocked by the user. They could even put up a big scary warning, notifying us users of all the chaos that might ensue from recklessly unlocking our bootloaders. Here's one of the posts I found about camera firmware. http://forum.xda-developers.com/galaxy-s3/general/jb-4-1-2-camera-driver-t2006128
Thanks for your thoughts on all this wierdness.
Click to expand...
Click to collapse
Camera is usually always an issue in CM ROMs because the stock camera firmware is closed source so the devs can't use it, they have to piece the camera firmware together themselves. Some devices never get the camera straightened out in CM.
BadUsername said:
Pretty unusual.
The phone is old and you're running old firmware. It's really hard to tell what the issue is. Could be a hardware or AOSP issue.
If you can take a logcat while the phone force closes and you can see how it fails. You can post that in the cm thread and see if you can get the developer to fix the problem. You can post it here and I'll tell you when it's failing.
Alternatively, you can attempt to boot up a stock based rom and see if that camera is still giving you problems.
Click to expand...
Click to collapse
Ink'd from my KrAkEn'd S3

Droidriven said:
Camera is usually always an issue in CM ROMs because the stock camera firmware is closed source so the devs can't use it, they have to piece the camera firmware together themselves. Some devices never get the camera straightened out in CM.
Ink'd from my KrAkEn'd S3
Click to expand...
Click to collapse
Right, hence my suggestion to use a logcat since it's impossible to tell if it's aosp or hardware related. Camera usually still works on aosp, just not nearly as well.

Related

Jellybean (CM/AOKP/Virtuous) Maps/Photoshpere Bug (Report Here)

Hello,
I have the following problem:
I experience visual artifacts when using two-finger rotate in Google Maps, also Photoshpere is really acting up... the images flicker...
Not all devices have it, as a matter of fact there are few of them (reported). Let's try to collect as much data as we can in order to find the cause of this and maybe a fix. I'll start.
HTC One S
Color: Gradient Blue
HBOOT:1.14.0002
Radio:1.06es.50.02.31
Jun 11 2012, 14:36:28
It's recommended to attach a logcat with the problem.
The problem allways happen when try to rotate Gmaps with two fingers, and photoshpere gets crazy especially after taking 1st photo.
It seems like an accelerometer problem, but accelerometer utilities seems to report the sensors working fine, so maybe a GPU driver problem.
C'mon guys, let's get this fixed
For the flicker have you tried changing debug.composition.type=dyn to debug.composition.type=gpu? I also had the same issue with that camera but only tried it when it come out, have you tried other packs that have it?
Darknites said:
For the flicker have you tried changing debug.composition.type=dyn to debug.composition.type=gpu? I also had the same issue with that camera but only tried it when it come out, have you tried other packs that have it?
Click to expand...
Click to collapse
I've tried many packs... i will try those and report back. The thing that scares me is that this happens on Virtuous Rom also (which is almost stock build with HTC jb libs), and this may mean that i will never have fully working jb not either from HTC.
adi4motion said:
I've tried many packs... i will try those and report bach. The thing that scares me is that this happens on Virtuous Rom also (which is almost stock build with HTC jb libs), and this may mean that i will never have fully working jb not either from HTC.
Click to expand...
Click to collapse
What you get both issues on Virtuous? that can't be good.
Darknites said:
What you get both issues on Virtuous? that can't be good.
Click to expand...
Click to collapse
yes... that's also what i'm afraid of...
Keep in mind the camera is for 4.2, not 4.1, and I doubt we'd ever get stock camera on official Sense.
PcFish said:
Keep in mind the camera is for 4.2, not 4.1, and I doubt we'd ever get stock camera on official Sense.
Click to expand...
Click to collapse
ok, that's not a problem, i can live without photoshpere, but the fact is Google Maps also have this problem and I need GMaps...
I know that at least 3 others reported this problem (and i'm sure that are many others who didn't test for it) I wonder where are they now...
I started this thread hoping that if other users reported it, the devs would try to solve this, but i think i'll just have to wait for HTC to give us JB and see if i still have the problem (but I am really concerned that I might have it). What's wrong with this One series? so many bugs (and not minor): cases chipping, helicoptering bug, sound issues, performance issues (one x), this problem....
I reported in another thread that I have this problem and I do, when using photosphere, I've seen it, although if I keep my movements nice and slow and steady, it seems to hold together.
I haven't seen any problem in Google Maps though, what happens to you in there?
Cheers
wheeliemonster said:
I reported in another thread that I have this problem and I do, when using photosphere, I've seen it, although if I keep my movements nice and slow and steady, it seems to hold together.
I haven't seen any problem in Google Maps though, what happens to you in there?
Cheers
Click to expand...
Click to collapse
when i rotate the map with two fingers i get visual artifacts
I have the same problem on photospere, on maps I have no graphical problems, but the magnet sensor seams to change it's direction sometimes. Had this on CM10, and now on 4.1 Sense+.
Edit: I mean I have the orientation problem on photosphere. My screen does not flicker.
I have this same exact problem with an HTC One XL. I have not found a fix for it.
I've tried flashing every flavor of jellybean there is. It oddly seems to not happen if I use a sense version of jellybean. But I hate sense and want vanilla android.
AOKP, AOSP, modded, unmodded, doesn't matter. I get this annoying graphics glitch when I try to scroll around using maps or photosphere.
I hope it's not purely hardware related, and that there's an easy software fix for it.

Flickering screen

Hey guys so I've got a huge issue. I'm on now my 3rd SGSIII and I'm getting very annoyed. My screen goes nuts randomly. I think I've found a fix, but I'm not sure what's causing it, as most people don't show the symptoms. My screen starts flashing and flickering, whether it's the lockscreen, the homescreens, within an app or in the app menu it does the same thing. I haven't taken a video of it yet, but will if someone wants to see what's happening. I've had it happen only on JB, both roms and stock doesn't seem to matter. The 'fix' is the same one as AOSP rom users use, which is to disable hardware overlay, however I don't know why a non-AOSP rom would need to deal with this. The roms I've used are: Vengeance, CleanRom, Synergy and The Executioner. I've gotten so annoyed that I've gotten Verizon to allow me to switch to the DNA if I want. I've taken a few Logcat's, if someone who can decipher them more than I can to figure out what's actually wrong would be great! I've taken a bunch of logcats, but only have one posted to pastebin. It was taken whilst I was having the issues. Thanks for the help guys!
http://pastebin.com/2SZkQGZJ
LlirasChosen said:
Hey guys so I've got a huge issue. I'm on now my 3rd SGSIII and I'm getting very annoyed. My screen goes nuts randomly. I think I've found a fix, but I'm not sure what's causing it, as most people don't show the symptoms. My screen starts flashing and flickering, whether it's the lockscreen, the homescreens, within an app or in the app menu it does the same thing. I haven't taken a video of it yet, but will if someone wants to see what's happening. I've had it happen only on JB, both roms and stock doesn't seem to matter. The 'fix' is the same one as AOSP rom users use, which is to disable hardware overlay, however I don't know why a non-AOSP rom would need to deal with this. The roms I've used are: Vengeance, CleanRom, Synergy and The Executioner. I've gotten so annoyed that I've gotten Verizon to allow me to switch to the DNA if I want. I've taken a few Logcat's, if someone who can decipher them more than I can to figure out what's actually wrong would be great! I've taken a bunch of logcats, but only have one posted to pastebin. It was taken whilst I was having the issues. Thanks for the help guys!
http://pastebin.com/2SZkQGZJ
Click to expand...
Click to collapse
is the show screen updates or something similar on in developer settings?
dragon1357 said:
is the show screen updates or something similar on in developer settings?
Click to expand...
Click to collapse
Nope, I don't run that stuff because all of the rendering updates and stuff can get annoying to look at while working. I'm able to get the same issues on a fully stock rom, and a pure flashed rom, with a few programs installed. But the fact that the hardware render seems to be the issue to me is just very odd on a non-AOSP rom.
I have been having screen flickering issues ever since I flashed the latest AOKP build (AOSP) I originally thought that it was because of the kernal and the under voting that I applied but even with a different governor and normal volt settings the screen still flickeres. After some poking around I figured you that it is only happening while I am trying to type and by uninstalling the Swype beta keyboard the screen flicker had been reduced to almost nothing. I do not know why the keyboard would amplify the effect but if I use the system keyboard the flickering becomes almost non existent.
Also, the screen flickers anytime a pop up menu is on screen, such as in the tapatalk app, the menu that pops up to allow you to quote someone..
Sent from my SCH-I535 using Tapatalk 2
Had been having the same issue on Baked Bean 6, flashed BB7 last night and it seems the problem is gone. BB7 being 4.2.1 I'm guessing whether intentional or not somewhere along the process of updating the "bug" if it indeed was as it appeared was squashed.
I'd be curious to know what was causing this, if by chance you find a definitive answer please post it.
Thanks
Lk
I had a very similar issue for a while, i flashed LEAN KERNEL
Rebooted twice, and problem went away.
For an update, I flashed kt's latest kernal and the flashing has ceased.
Sent from my SCH-I535 using Tapatalk 2

[Q] Various potential hardware/sensor related issues

Hey guys,
I have a VZW HTC One M8 with the following version details:
Cyanogenmod 11-20141112-snapshot-m12-m8
Unlocked bootloader
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0222
OPENDSP-V26.2.2-00538-M8974.0106
OS-
eMMC-boot
This phone came to me with a clean Cyanogenmod install on it. I wiped it anyway to be sure. I have an S3 that I've been running CM11 on up until I got this phone so I'm no stranger to Cyanogenmod.
My issues appear to be randomly occurring and I cannot seem to pin down what is causing it or when it actually happens. Here are the various issues I'm seeing:
1. Screen fails to reorient when being turn - this happens system wide, even the home screen fails to reorient. Perhaps a problem reading the gyro sensor?
2. Lux values get stuck, usually at 45. Ambient light sensor?
3. Double tap to wake stops working - need to use the sleep/wake button to turn the screen on. Can still double tap the status bar to turn the screen off
4. Incorrect battery reporting - The battery appears to drain normally and at a consistent pace, however if the phone is shutoff or rebooted I will sometime see a huge drop when the phone boots back up.
I have a screenshot from the phone this afternoon but cannot post it (attachments fail to upload on this forum). I can probably PM it to you though.
I noticed if the phone gets to 5%, sometimes ~15% it will just turn off because the battery has actually died but the OS thinks differently.
The first 3 issues fix themselves after reboot.
Oh and I've noticed that the profiles feature doesn't work properly. If the ring mode is set to vibrate on the work profile, it will stay in vibrate even when it switches back to the default profile which is set to ring mode. The phone will not let me set custom notification sounds with Profiles enabled either. Example: Hangouts uses the notification sound as set by the default in Settings. I cannot change this. I can turn off Profiles and I can change the notification tone on Hangouts all day long.
Not quite sure what I should be looking at here so any guidance or suggestions would be much appreciated. Let me know if you need any more details.
You answered the question yourself in the second sentence of your post.
beaups said:
You answered the question yourself in the second sentence of your post.
Click to expand...
Click to collapse
beaups,
Was really hoping for a more descript answer. Can you please elaborate?
cstokes86 said:
beaups,
Was really hoping for a more descript answer. Can you please elaborate?
Click to expand...
Click to collapse
You are running cm. Probably known cm bugs or possibly you need different firmware. Either way, there's no such thing as a hardware problem until it exists on stock software.
beaups said:
You are running cm. Probably known cm bugs or possibly you need different firmware. Either way, there's no such thing as a hardware problem until it exists on stock software.
Click to expand...
Click to collapse
I forgot to mention in my original post:
I already searched around for the various issues I'm having but was not able to find any mentioning of them in any known issues lists. Was hoping to see if any devs on here had suggestions on things to try.
cstokes86 said:
I forgot to mention in my original post:
I already searched around for the various issues I'm having but was not able to find any mentioning of them in any known issues lists. Was hoping to see if any devs on here had suggestions on things to try.
Click to expand...
Click to collapse
Search better. This took me less than 5 minutes:
http://forum.xda-developers.com/showpost.php?p=56813202&postcount=3167
http://forum.xda-developers.com/showpost.php?p=56733227&postcount=3140
http://forum.xda-developers.com/showpost.php?p=56719654&postcount=3130
and many, many more all in that thread, which happens to be the CM thread for your phone.
Oh, and welcome to XDA
beaups said:
Search better. This took me less than 5 minutes:
http://forum.xda-developers.com/showpost.php?p=56813202&postcount=3167
http://forum.xda-developers.com/showpost.php?p=56733227&postcount=3140
http://forum.xda-developers.com/showpost.php?p=56719654&postcount=3130
and many, many more all in that thread, which happens to be the CM thread for your phone.
Oh, and welcome to XDA
Click to expand...
Click to collapse
Thanks for those links. I was looking in the official known problem lists for Cynogenmod for these issues to see if they actually confirmed anything. I will look at possibly installing a nightly and testing with that, but I'm a bit reluctant to go that route since this is my daily driver.
cstokes86 said:
Thanks for those links. I was looking in the official known problem lists for Cynogenmod for these issues to see if they actually confirmed anything. I will look at possibly installing a nightly and testing with that, but I'm a bit reluctant to go that route since this is my daily driver.
Click to expand...
Click to collapse
If you are looking for stability, flash a sense based ROM. Its just the way it is.
beaups said:
If you are looking for stability, flash a sense based ROM. Its just the way it is.
Click to expand...
Click to collapse
^ Can't disagree with that, but I loathe the bloatware and manufacturer UI and skins they put on their devices, not to mention the freedom and functionality I lose out on by going back to a more or less stock experience. If I want stock non-CM, I'll just flash 5.0 GPE and see how that goes, but I've already tested with that as well and missed the functionality that CM brings. :/
Win/Lose.
Do you think the firmware (not the ROM/OS) is highly out of date and should be updated by now?
cstokes86 said:
^ Can't disagree with that, but I loathe the bloatware and manufacturer UI and skins they put on their devices, not to mention the freedom and functionality I lose out on by going back to a more or less stock experience. If I want stock non-CM, I'll just flash 5.0 GPE and see how that goes, but I've already tested with that as well and missed the functionality that CM brings. :/
Win/Lose.
Do you think the firmware (not the ROM/OS) is highly out of date and should be updated by now?
Click to expand...
Click to collapse
Yes you should update that firmware. There's an emmc controller firmware update amongst other things included you should have. Have you tried gpe or stock with some of the xposed modules now available?

Lollipop, KK, Ics, JB, TW, AOSP, CM, Recommendations, & Opinions for a dying Device

Lollipop, KK, Ics, JB, TW, AOSP, CM, Recommendations, & Opinions for a dying Device
Well I haven't seen a general lollipop thread so I wanted to start one. The Pub seems like a nice place but since there's so much talk on there about everything in general, info could become hard to find. I do like the pub and read it every so often.
That said. I may or may not update the op with links posted. But most know where to find things if they look hard enough.
What I've found so far are AICP, Liquid, Mastamoon's CM, and a Slimpop build. I've tried AICP and Liquid. Thus far I've not been impressed with Lollipop, to each their own though. It looks okay, seems to run great, (I didn't do any benches, rather relying on the seat of the pants feel), I realize our device is getting at the age where not a lot of further development may happen. But it's still one of the few newer phones that you don't have to jump though hoops to install a rom.
What I'm asking if anything, is what have you tried, and why do you like or dislike it. Again, I know it's early especially for the d2vzw, but builds are out and are fairly stable, on AICP I never had a single reboot that I can recall. I'm going to try the latest Liquid tonight. I don't understand the new DD layers or whatever it is. I think it's a new way of theming possibly used by slim and maybe now liquid since I think they're using slim as a base now according to their thread in original development.
I'm backing up my favorite KK build now. Don't know if I want to try slim first or liquid. Both have builds dated 02-07 and 02-08 respectively.
If you dislike it I assume you're still running KK, or JB. In this case, I'd like to know if you're running a custom TW JB rom such as alliance or Moar or Wicked or anything else. And why. I am in an area where signal is ****. And although I'd imagine TW should get better signal, I'm not seeing a huge difference here. Maybe if I could get 3-5 DB/m better I'd stay on TW JB, but I'd have to make some measurments first. Signal on Lollipop seemed better but it can't be because I'd assume they're using the exact same RIL as on KK. Again, if I'm wrong on any of this please fill me in.
If there is another thread to follow that has already addressed all this let me know. I'm loving lollipop but can't find one namely AICP my current favorite that's releases regularly besides Masta and liquid, that have camera and video working if you have lollipop installed with these things working please share. I've tried freezing camera, then installing OPEN CAMERA, VIVAvideo, CM Camera FIX w/ the added apk for resetting the camera drive without a reboot to no avail. And I can't seem to make VIVA default to 640*480, maybe it does it on it's own but I've looked though all the settings I can find and can't seem to figure it out for the life of me. I've read damn near every thread and q&a thread to no avail.. I didn't read Masta's in it's entirety because it's so dang big. But I did browse the last ten-twenty pages or so. Once you stop keeping up for a few day's you're just lost... Which is what I wanted to make this thread to try to shed light on things without beating anyone up, and without downing any dev's they all make these things possible.
SO PLEASE if you don't mind let me know what rom has worked for you, with camera and video working and what you did to get it going.. WITHOUT STEPPING ON ANYONE"S TOES if at all possible. Thanks and have a great day/night/evening/morning.
Ain't getting a bite. Oh well. I saw a post about the slim ROM like a day later. Haven't ran it but that post has detailed data on what works and what doesn't in the op. I did try the newest liquid from 02-08 I think and it ran fine. I couldn't find how to change which settings though. A lot of features were there some weren't. Tried AICP same deal except I found the quick settings modifier in this one.
Both ran very well but I did use dkp's excellent kernel. Tierservative governor and clocked at 216-1728. Using his voltages.
I did try sending a text with liquid and I don't know if it went or not. I had read receipts checked but didn't get one. Someone else had this same issue in the liquid thread.
I'm back on KitKat but will n be testing new builds as I find them. Please give the developers some love and support or if you can donate. These guys work on this for fun and experience and some are in college. I've never known many wealthy college students. I was thrilled to have a case of naddy light or ughhhh beast ice.
griz.droidx said:
Ain't getting a bite. Oh well. I saw a post about the slim ROM like a day later. Haven't ran it but that post has detailed data on what works and what doesn't in the op. I did try the newest liquid from 02-08 I think and it ran fine. I couldn't find how to change which settings though. A lot of features were there some weren't. Tried AICP same deal except I found the quick settings modifier in this one.
Both ran very well but I did use dkp's excellent kernel. Tierservative governor and clocked at 216-1728. Using his voltages.
I did try sending a text with liquid and I don't know if it went or not. I had read receipts checked but didn't get one. Someone else had this same issue in the liquid thread.
I'm back on KitKat but will n be testing new builds as I find them. Please give the developers some love and support or if you can donate. These guys work on this for fun and experience and some are in college. I've never known many wealthy college students. I was thrilled to have a case of naddy light or ughhhh beast ice.
Click to expand...
Click to collapse
I ran LS and mastas LP roms and loved em both on my S3 (I still have it even though I upgraded) and while I was impressed with the rom itself in both cases the battery life for me at least was horrendous. I've since learned a lot about wake locks and having too many apps can be a bad thing. I'm running slimkat on the S3 currently but I think I might just try out another LP rom seeming how it's only a wifi device now
Sent from my Nexus 5
Thanks. I think my battery may just be getting old but I do have a few wake locks. If your using the s3 as WiFi device then use airplane mode to help battery. Turn it on then turn on WiFi. That should help your battery life a lot. At least on my dx2 it does.
Sent from my SCH-I535 using Tapatalk
This was supposed to be an edit sorry.
Thanks. I think my battery may just be getting old but I do have a few wake locks. If your using the s3 as WiFi device then use airplane mode to help battery. Turn it on then turn on WiFi. That should help your battery life a lot. At least on my dx2 it does.
Out of curiosity what did you upgrade to? I'd love a nexus six but I'm not sure they'll work with CDMA networks or a new moto. Since my old motos DX and x2 are bullet proof. Built like tanks. But I need to get something that'll let me scratch the flashing itch.
griz.droidx said:
This was supposed to be an edit sorry.
Thanks. I think my battery may just be getting old but I do have a few wake locks. If your using the s3 as WiFi device then use airplane mode to help battery. Turn it on then turn on WiFi. That should help your battery life a lot. At least on my dx2 it does.
Out of curiosity what did you upgrade to? I'd love a nexus six but I'm not sure they'll work with CDMA networks or a new moto. Since my old motos DX and x2 are bullet proof. Built like tanks. But I need to get something that'll let me scratch the flashing itch.
Click to expand...
Click to collapse
I upgraded to a Nexus 5, I'm on straight talk so I can get any phone i want. And yea I run the S3 with wifi and airplane mode on, I do the same with my tablet
Sent from my Nexus 5
---------- Post added at 04:40 PM ---------- Previous post was at 04:37 PM ----------
griz.droidx said:
This was supposed to be an edit sorry.
Thanks. I think my battery may just be getting old but I do have a few wake locks. If your using the s3 as WiFi device then use airplane mode to help battery. Turn it on then turn on WiFi. That should help your battery life a lot. At least on my dx2 it does.
Out of curiosity what did you upgrade to? I'd love a nexus six but I'm not sure they'll work with CDMA networks or a new moto. Since my old motos DX and x2 are bullet proof. Built like tanks. But I need to get something that'll let me scratch the flashing itch.
Click to expand...
Click to collapse
The nexus 6 will work with CDMA carriers, it's the first Nexus (other than the Galaxy nexus) to work with CDMA carriers
Sent from my Nexus 5
Dam I want my
I want my nexusss sixxx.
From the old dire straits mark knoplfer I want my mtveeee. When it was an actual music channel.
Showing my age again. Going to test some more and try to keep updating this thread but it's been hectic lately.
Sent from my SCH-I535 using Tapatalk
griz.droidx said:
Dam I want my
I want my nexusss sixxx.
From the old dire straits mark knoplfer I want my mtveeee. When it was an actual music channel.
Showing my age again. Going to test some more and try to keep updating this thread but it's been hectic lately.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Its a solid phone, the price really turned me away from it though
Sent from my Nexus 5
ShapesBlue said:
Its a solid phone, the price really turned me away from it though
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeah I really can't afford one, but unlocked devices from major carriers seem to be few and far between. I mean without jumping though every hurtle out there to try to root and rom and device is getting harder and harder these days..
On the lollipop note, I really want to run it and have received advice from various forums on how to get the camera and video to work using A better camera, which i haven't tried, to open camera which i did try, and vivavideo which i just couldn't get to work for me at all. I might try another tonight maybe liquid maybe CM, I'd try Slim which was once my absolute favorite, until I used nameless. It had the features I wanted with none of the bloat I didn't.
I've been trying every aicp that I can get my hands on but have yet to get the camera or video to function.. Of course lots of people are useing Mastamoons CM and he probably has the biggest following of all the rom's out there at the moment. Maybe I should give that a whirl just to see how things fare with using the camera and video. But I can't imagine that other dev's haven't picked up on his tips, tricks, and cherry picks to include in their own roms to make them work just as well, but then again, maybe they're going their own route.
My question to everyone is which rom are you running lollipop that is, that have both camera and video working... Any kind of camera and video. I'm not too worried about resolution at the moment as far as video is concerned as I understand it, VIVAvideo only works at 640-480, but I can't for the life of me find a setting in there to get it to work.
I've found an app on the app store called cm camera fix or similar that is supposed to get things going without a reboot using another apk called camera reboot or simlar, but didn't have much luck with either.. Again, this is using AICP which I love. If anyone can suggest a rom and I've read through all threads except for the massive mastamoon thread, please do so. and please share your experiences
your not so on the spot op
griz
People seem to forget our builds are still alpha builds. Its unfortunate, but the truth. Doesn't seem like we will get any unofficial love until the camera API problem is hacked & working. My favorite devs aren't building for our phone yet because of all the camera issues. Hopefully these issues will be resolved before I get my new phone. Looks like I'll be making the switch back to HTC
sjpritch25 said:
People seem to forget our builds are still alpha builds. Its unfortunate, but the truth. Doesn't seem like we will get any unofficial love until the camera API problem is hacked & working. My favorite devs aren't building for our phone yet because of all the camera issues. Hopefully these issues will be resolved before I get my new phone. Looks like I'll be making the switch back to HTC
Click to expand...
Click to collapse
Sadly there aren't many devs left for the VZW S3 either. A lot of them have moved on. Now that mine is only a wifi device I might just run a LP rom on it. It runs pretty well on my N5, I've yet to have a random reboot which is great
Sent from my Nexus 5
Thanks guys, yeah dev's are getting few and far between and many don't use the device and rely on users for feedback and logcat's and debugging information.
Here's something I posted in AICP and thought I'd post here as well.
Just an FYI. Using suggestions from here and other threads, I've been able to successfully take both photos and video. I used A better Camera as suggested by Pyrite123 so thanks for that suggestion. I first uninstalled the stock camera using ROM Toolbox, I'm sure Titanium would do the same or just removing the apk. Anyway, after doing this and installing A Better Camera (Which is quite nice I must say), and VivaVideo I was able to both take pics and record video. I do not care for VivaVideo, but ABC wouldn't take video... Been thinking about trying LG Camera, this used to work with all else failed back on the DX when dev's were trying to get the camera working on a particular build. LG Camera includes LG camcorder.
On another note, having used DKP, BMS, and KT kernels for sometime now I was afraid those may be inferfering with getting the camera working. Not the case. I've used DKP which should probably be updated to something newer since it's from around the middle of Jan. I like it because of the stock undervolting and many governor options. I usually underclock using the stock voltages to 216-280 and sometimes up to 1728 down to 1350 on the high end. depending on what I feel I need.
Another thing, I noticed my KitKat Rom wasn't locking GPS so I re-installed a stock based rom to get a lock as has been suggested a zillion times over a zillion builds and roms.. Getting a lock in Alliance Rom 23, then immediately installing AICP fixed gps locking.. I got 6 sats locked inside my home tonight with a metal roof, and a huge metal shed outside. I'm certain I could get 10 or more standing still outside.
Just wanted to update and say thanks to not only the AICP dev, but all dev's who are and have been working on lollipop for this device.
Shapesblue mentioned on his GN5, I too have never had a single reboot. Which is one reason I've been so hell been on getting the camera and video working somehow someway.. It may not be working correctly, but it's working.
Looking at masta's thread, it looks like his next build will have the camera fixed. I guess we will wait and see.
Thanks sjpritch25, I saw that. Something about PA having it working but not having anything in Gerrit or something and them possibly just including a third party camera.
My camera works most of the time. I'd say 80-95% of the time.. Yesterday I installed the latest AICP just because it was there, did the camera freeze, and Sometimes Open Camera and A Better Camera would work and sometimes not. usually using the Camera reset apk linked in the CM Camera Fix app in the Play store fixes it in a jiffy so that I can take photos again. I think I even used the front facing camera on one app, don't remember which one. And since another user suggested trying Camera Zoom FX I did that and it worked as well as the others.. All in all the pic's turned out fine with flash, and although one user mentioned that using flash screwed up their Torch Tile in Quick Settings, I experience no such issue.
I had a crazy issue where hangouts would crash and burn horribly upon launch. After installing the latest release, I didn't restore my version from TiBu instead installing it from the play store, and all was right again in the universe.. Again, I'm using the DKP kernel from 01-10 or so what seems like ages ago, but it works and as I've mentioned I like the stock voltages, governors and being able to underclock on the low end, and overclock on the highend if necessary.
Just wanted to report in.
Question, and I should read the BMS thread for this and the G+ community, but Ed has released a couple kernels and I think they're for lollipop, I can't confirm this because nothing in the name of the file says anything about it, but it does say 34, so perhaps KK uses the same version. I just checked and those kernels will probably work, looking in about phone in LP, I see that it's still a 3.4 kernel so I'd say, but I'm just guessing here, that the BMS kernels will work at least the ones release after the date he mentioned including CM12 stuff. Maybe they'll work with both KK and LP. And I'm almost 100% certain this is the case but YMMV. Don't come looking for me if it doesn't.. I'll try one whenever I decide to try another build. I'm itching to try Slim, always loved slim I have, And I reckon RRO Layers are supposed to work theoretically according to the OP. But even though I've read up on that next gen method of theming, I'm still in the dark and need to just dive in I suppose and get my feets wet. I know "feets"
I was on aicp, but flashed mastas build to test the camera. I wonder if PA had video working too? Open camera works great with the latest build. Still no video
I WANT YOUR VOTE!! Opinions Wanted! Not spam... LOL
No I'm not running for public office. I value everyones opinion so please if you have a few minutes read on.
sjpritch25 said:
I was on aicp, but flashed mastas build to test the camera. I wonder if PA had video working too? Open camera works great with the latest build. Still no video
Click to expand...
Click to collapse
Latest Build of what? PA?
As one might have noticed I've changed the thread title. I know a there are a ton of resources about how to do this or that, and listings on what's available for Big Red's S3. Which I will probably own for the forseeable future. I have been unemployed for over a year now, Have had prospects on a few good well paying jobs, but they didn't pan out (One Network Admin Position, I should have landed easily, but didn't have the pull of the board like the other person, but I digress)
The S3 thanks to the hard work of a lot of developers and the community has had a great and exciting life. Hopefully people will continue deving for it well into the future like the DX, or the S2 etc.
My S3 runs great on most any rom I install be it TW, AOSP based, JB, KK, and now pretty dang good one Lollipop. The only problem for me with lollipop is that the moga universal driver doesn't work with L-Pop. This has been noted in the thread, but I don't know if any more work will be done to fix it. So I'll probably go back to TW or KK or JB.
I went from AICP which I have to admit is progressing nicely with their L-pop build. But since the moga universal driver doesn't work I'm going to use something else. And I've got that itch to flash something new again. All the KK's I've ran have been pretty dang good, SlimKat, Carbon, Liquid, Omni, and others but I've always stuck with nameless for whatever reason. Well, one reason is the adjustable timeout to kill apps via back button. Kinda like MIUI used to have.
My question is, for those of you who've flashed a lot of toms and can remember the details because it's all about the details. is what rom did you like the best and why.
Also aside from the massive drawback of not being able to install AOSP roms, is there any benefit to being on the TW 4.4.2 or 4.4.4? I can't remember which one they releaased. Some of the TW roms, Alliance, Moar, and Wicked are great roms and have a nice selection of theme's available. They run pretty good and are running JB.
The JB/KK, mostly KK, roms I've ran run absolutely awesome, I'm currently working on eliminating the play services wakelock without loosing much or any functionality, some say you can use the privacy manager (a big plus for Slim, Nameless, and Other users) to block the app staying awake. I haven't tried to use DS battery saver, Greenify, or many of the other zillion "Install me and I'll magically double or triple battery life using a method called "Using the Force!" At least that's what most ammount to or killing off apps blah blah blah.
Some users I've noticed are Die-hard TW fans and some Die-hard AOSP fans. I strongly lean toward the latter. I like being able to theme my rom I sil love MrDSL's Mixer series and DustinB's Cobalt series. With the new Lpop Roms this isn't possible. I have used the theme manager with CM12 themes in lpop but they're all flat and I don't care for that I do like aesthetics, but to each their own. Maybe the new flat method of lpop makes for better battery life?? It certainly makes for a duller looking rom. I do like the all black ones with white text however. Even they get old compared to the themes for CM7-11.
And TW roms are almost, and I stress almost as themeable as the the older CM varients. So many combinations of this or that and the Ultimate Icon Them or UIT is pretty slick IMHO. The themes for Wicked are almost as Wicked as the ROM itself.
If you made it this far, or just skipped the middle, congradulations you win.... well an opportunity to help myself and others answer a timeless question... Not the chicken or the Egg question.. Not Are we Alone in the Universe, Not is there a God and is he a nice guy, But rather you can help myself and others by giving reasons as to why you prefer one rom over the rest.
Please be detailed or as detailed as possible. Most who are in these forums know the jargon or should, and if not it's past time to learn.
Oh I've posted extensively about the 03-15 ish to 03-25 ish AICP if anyone wants to hear how things are going with that rom. It has quite a lot of the old features many of us miss and now includes the option to adjust the delay in killing apps too a'la Nameless and MIUI (I know the older MIUI did this on my X, DX that is)
So go on kick off your shoes, put your feet up, and write a post about why your running what. I've asked this in the past but opinions change sometimes quicker than it took me to write this short story as one guy used to tell me. Oggie I think it was..
Before I run, I wanted to wish Mastamoon all the best in his future Nexus 6 endeavors. That's probably my favorite phone at the moment, since I used to want a note anyway. SO thanks Masta for all those builds, cherrypicks, news, and releases you whipped up for us over here in Big Red Country, (NO not China, but rather VZW China's more Capitalist today anyway), I've left Verizon for an MVNO called Selectel because of their 15 dollar a month plan using big red's towers, but they don't offer data roaming. Here it's either Big Red or a Regional Carrier (which is probably more expensive than Big Red).
To read my massive off topic thanks to mastamoon press teh magical button.
Since I got way off topic, Here is is: THANKS MASTAMOON for all the work you've done the past few years working for free or next to free I hope someone bought you a beer or beverage of your choice. I can't afford a KitKat right now.. ha ha bad joke.. But thanks man, THANK YOU and thanks again to everyone who's worked on building and maintaining ROMS for this aging device. I for one appreciate it to no end. I used to be a distro hopper, I still am (remember the Mitch Hedberg [RIP] Joke?), I'm still a distro hopper but using Android Distro's for my phones. One an aging DX2, A DX with a screwy, Screen, and my baby the S3. Thanks to the community too, because without their feedback, bugs and stuff may never get solved, and many people wouldn't get the help they need, and just give up with their phone soft-bricked.
So one more for the road Thanks to the Dev's, Thanks to the maintainers, and Thanks to the community. Many don't thank the community enough but I can remember back in my DX says which I was a bit younger but still eager to learn all I could about Android and Customizing the DX. Without the community, I wouldn't have had the guides that get stickied, I wouldn't have got out of my softbrick situatiiiions, my re-activation woes which by the way, with the help of RazorLoves, I was able to re-activate at home which I was told by Big Red that I needed to drive 45min to one hour away to activate because the only towers in my home location and surrounding area belonged to Appalachian Wireless, a more expensive than big red regional companuy, Razor gave me the codes to get into the stock dialer to program the phone. Just one example out of many where the community has been very vey helpful. Kinda like the Dev's are the Doctors in the operating room, the Anesthesiolgist and nurses are maintainers and builders, with the other nurses and guest docs being the community. Probably a terrible analogy. But really. thanks to everyone involved on there. Just wish they got thanked more often and users didn't haggle them about stuff like "when will this be fixed" or "how much longer on the new build" "Rom X dries my dishes while yours only washes and scrubs them", "Rom X is better then Yours" Crap like that gets on my nerves. I'm sure my massive posts and continuous thank yous get on some peoples last nerve, But I'm trying to work on the massive short story length postings. I could care less about what people think of the latter, because the least I can do is thank someone for their hard work.
Back to the rest of the story. Let me know and others for that matter, why you've settled on TW and if yor're on TW, which build and why. If you're on another custom AOSP rom, again, why? What makes it better than any others., and if you're on the new KK locked down one why unless it was an acccident. Because I've even considered takeing that route but I doubt it's that much better than TW4.3 plus there would be no way to go back to lollipop or KK built from CM or AOSP.
I already know most people will say try them out and see for yourself. That's just it. I've tried 95% of the TW stuff, and almost all of the aosp/cm based roms. From Slim which was my DD for a long long time. Slim and I had a serious relationship but we broke it off because after JB she quit doing a few things she used to be able to do very well and I needed them only for my own pleasure. I know not funny, but true.
Just looking for others opinions, whethers its about battery life, signal (I live in a rural area with little signal if any), performance, looks, stability (of the OS not apps), if the Camera/Camcorder works well, so on and so forth.
Thanks for reading something that contained little to no information Also, if you use Xposed, which modules do you use and why?
Thanks in advance, I'll be checking in every day or two until I get my new work schedule.
Your Friend and fellow S3 owner
Griz.
I was wondering what's good for roms anymore I haven't had ran custom since my og s3 since I had it was running ose rom doesn't seem like they are around anymore need to downgrade from nc1 to ml1 thanks
any lp roms yet if any are dd?
nikkifm said:
I was wondering what's good for roms anymore I haven't had ran custom since my og s3 since I had it was running ose rom doesn't seem like they are around anymore need to downgrade from nc1 to ml1 thanks
any lp roms yet if any are dd?
Click to expand...
Click to collapse
I've found a lot of LP roms on the S3 are battery hogs. I'm still running slimkat on my S3 which I only use for games and a mp3 player now
Sent from my N5
ShapesBlue said:
I've found a lot of LP roms on the S3 are battery hogs. I'm still running slimkat on my S3 which I only use for games and a mp3 player now
Sent from my N5
Click to expand...
Click to collapse
would you say slimkat dd? and does it need new ne1 baseband for it kinda wished my old rom dev was still around that I ran was getting day worth of charge on one battery
nikkifm said:
would you say slimkat dd? and does it need new ne1 baseband for it kinda wished my old rom dev was still around that I ran was getting day worth of charge on one battery
Click to expand...
Click to collapse
I'd definitely say slimkat is a dd. I did have to update to the NE1 modem
Sent from my N5

Can anyone share the latest OOS CAM apk?

I have custom ROM, and I'd like to use the latest OOS cam apk, but in apkmirror there is only ports from OP7/P which are always crashing when I opening them.
Where can I download it?
lyor said:
I have custom ROM, and I'd like to use the latest OOS cam apk, but in apkmirror there is only ports from OP7/P which are always crashing when I opening them.
Where can I download it?
Click to expand...
Click to collapse
Let me Google that for you... https://lmgtfy.com/?q=oneplus+6+oos+camera+for+custom+rom
Apparently it's somehow super hard for some people to do a quick Google Search... It's that easy.
Here's some links to some threads that might be helpful:
https://forum.xda-developers.com/oneplus-6/themes/magisk-oos-camera-3rd-party-roms-t3873821
https://forum.xda-developers.com/oneplus-6/themes/magisk-oneplus6-oos-camera-t3888204
If those ports don't work you might be out of luck, not every Custom ROM has support for the OOS Camera.
Not that it really matters, the OOS Camera sucks anyway. You'll be able to get way better results with a Google Camera port.
Also in many Custom ROM threads there have been reports of certain features of the OOS Camera to be not working, like Slow Motion and Portrait Mode.
So I wouldn't be expecting a fully working OOS Camera on a Custom ROM.
Mr.FREE_Bird said:
Let me Google that for you... https://lmgtfy.com/?q=oneplus+6+oos+camera+for+custom+rom
Apparently it's somehow super hard for some people to do a quick Google Search... It's that easy.
Here's some links to some threads that might be helpful:
https://forum.xda-developers.com/oneplus-6/themes/magisk-oos-camera-3rd-party-roms-t3873821
https://forum.xda-developers.com/oneplus-6/themes/magisk-oneplus6-oos-camera-t3888204
If those ports don't work you might be out of luck, not every Custom ROM has support for the OOS Camera.
Not that it really matters, the OOS Camera sucks anyway. You'll be able to get way better results with a Google Camera port.
Also in many Custom ROM threads there have been reports of certain features of the OOS Camera to be not working, like Slow Motion and Portrait Mode.
So I wouldn't be expecting a fully working OOS Camera on a Custom ROM.
Click to expand...
Click to collapse
Don't assume I didn't google that before if you don't even bother to ask
If you'd pay close attention, you would see that I even commented on the thread in your 3rd link, but it's a dead old port, and I'd like to use a newer one (like the one in OmniROM for example, which is somehow managed to do so) because all of the options that you gave are extremely old, and most (if not all) the issue you mentioned are already fixed in the newer versions which you didn't even bother to look into account.
And I don't know why do you think the OOS cam so bad, especially if you're recommending a buggy cam like GCAM, which is behaving like an early alfa stage and crashing randomly.
lyor said:
Don't assume I didn't google that before if you don't even bother to ask
If you'd pay close attention, you would see that I even commented on the thread in your 3rd link, but it's a dead old port, and I'd like to use a newer one (like the one in OmniROM for example, which is somehow managed to do so) because all of the options that you gave are extremely old, and most (if not all) the issue you mentioned are already fixed in the newer versions which you didn't even bother to look into account.
And I don't know why do you think the OOS cam so bad, especially if you're recommending a buggy cam like GCAM, which is behaving like an early alfa stage and crashing randomly.
Click to expand...
Click to collapse
Well if you did search well than you would've already known that there isn't any great working port available but the ones included with certain ROM's. Something I already knew but you just assumed I didn't, now you are doing the exact same thing you were pointing out to me. So the advise you gave me would be fitting for you too. "Don't assume I didn't knew that before if you don't even bother to ask".
And I'm not going to read through all those threads just to see if you have already commented in them, why would I?
Beside that, yes the OOS Camera absolutely sucks. The unreliable post processing kills all the details, which results in very ugly digital looking, sometimes oversharpenend or soft picture's. A small crop isn't even possible due to that.
The Nightscape mode sucks too, makes every picture look like an oil painting. And it's funny you call GCam buggy, shows you didn't do much research on it. Currently I'm using Miniflex which works just fine and at least makes it possible to take usable pictures. The older xtreme GCam mod works fine too.
Both capturing details and night shots with GCam is superior compared to the OOS Camera. The only two things that work better with the OOS Camera are taking videos and Slowmo's, for which it actually is pretty good. But I don't need those features, maybe you do.
Look, you started a thread with your question without providing any basic info like which ROM you are running etc. Getting a bit tired of seeing new threads requesting stuff with hardly providing any info that might be useful to know. I might have sounded very rude so sorry for that, maybe I should've took a 10sec count before I wrote my response.
Mr.FREE_Bird said:
Well if you did search well than you would've already known that there isn't any great working port available but the ones included with certain ROM's. Something I already knew but you just assumed I didn't, now you are doing the exact same thing you were pointing out to me. So the advise you gave me would be fitting for you too. "Don't assume I didn't knew that before if you don't even bother to ask".
And I'm not going to read through all those threads just to see if you have already commented in them, why would I?
Beside that, yes the OOS Camera absolutely sucks. The unreliable post processing kills all the details, which results in very ugly digital looking, sometimes oversharpenend or soft picture's. A small crop isn't even possible due to that.
The Nightscape mode sucks too, makes every picture look like an oil painting. And it's funny you call GCam buggy, shows you didn't do much research on it. Currently I'm using Miniflex which works just fine and at least makes it possible to take usable pictures. The older xtreme GCam mod works fine too.
Both capturing details and night shots with GCam is superior compared to the OOS Camera. The only two things that work better with the OOS Camera are taking videos and Slowmo's, for which it actually is pretty good. But I don't need those features, maybe you do.
Look, you started a thread with your question without providing any basic info like which ROM you are running etc. Getting a bit tired of seeing new threads requesting stuff with hardly providing any info that might be useful to know. I might have sounded very rude so sorry for that, maybe I should've took a 10sec count before I wrote my response.
Click to expand...
Click to collapse
Maybe I was running out of options, maybe it was just wishful thinking, but I thought at first that someone here knows something that I do not about it.
And regarding the OOS functionality, I don't know, but I was fully satisfied with anything I used from 3.8.72 and above.
lyor said:
Maybe I was running out of options, maybe it was just wishful thinking, but I thought at first that someone here knows something that I do not about it.
And regarding the OOS functionality, I don't know, but I was fully satisfied with anything I used from 3.8.72 and above.
Click to expand...
Click to collapse
Well since there are some ROM's which do provide a pretty well functional OOS Camera there should be a way. But the best you could do is probably to run a ROM that provides the OOS Camera by default...
Regarding to camera quality it's probably because I'm a photographer, I'm probably looking at pictures differently than you do.
Mr.FREE_Bird said:
Well since there are some ROM's which do provide a pretty well functional OOS Camera there should be a way. But the best you could do is probably to run a ROM that provides the OOS Camera by default...
Regarding to camera quality it's probably because I'm a photographer, I'm probably looking at pictures differently than you do.
Click to expand...
Click to collapse
I prefer to stay with the rom that I have right now (havoc).
It combines the best from all the worlds into it.
The downside of it, of course, the lack of OOS (imo).

Categories

Resources