Related
Hi XDA,
I'm currently running latest Flinny CM10 test build (125), and an issue I've had for a while is that even when the phone is locked, but screen is on, I can pull down the notification bar and do actions. Is this normal? Is there a setting somewhere that needs to be switched off? I am using Apex launcher.
Cheers.
As far as I know this is a standard behavior since android 4.0 (ICS). There is no settings to disable it.
Someone correct me if I’m wrong
EDIT: If you have enabled screen security (pattern, PIN, password) you should not be able to pull down the notification bar. You should be able to pull it down only with slide lock.
I enabled a simple gesture unlock and yes now I can't pull down the notification bar.
It still seems strange that this is normal behaviour.
Thanks heaps!
yup... That's normal...
I also face some issue which is the ROM could not connect to external gps device... I think that's issue exist in CM10 since have same issue with galaxy smtd...
Yeah I don't have working orientation, light or gyro sensors still. It seems like some people have this problem and others don't depending on hardware revision.
Sorry for writing sth different here but i didnt want to create a new topic, so...
I had this andromadus version on my DZ but i didnt find any pre installed camera app, anyone else who had this or do i have to reload the rom (maybe sth went wrong during downloading)
Sent from my GT-N8010
Vauvenal7 said:
Sorry for writing sth different here but i didnt want to create a new topic, so...
I had this andromadus version on my DZ but i didnt find any pre installed camera app, anyone else who had this or do i have to reload the rom (maybe sth went wrong during downloading)
Sent from my GT-N8010
Click to expand...
Click to collapse
Just wondering... Do u install gapps? If not, you should do that when u install it for the first time (after you install the rom).
Vauvenal7 said:
Sorry for writing sth different here but i didnt want to create a new topic, so...
I had this andromadus version on my DZ but i didnt find any pre installed camera app, anyone else who had this or do i have to reload the rom (maybe sth went wrong during downloading)
Sent from my GT-N8010
Click to expand...
Click to collapse
As with every CM build after 4.1.11.1 on the G1, ALWAYS FLASH GAPPS AFTER FLASHING THE ROM.
cm made a 4.2 donut where the base was flashed first still, so starting with eclair gapps where flashed after
Sent from my HTC Vision using xda premium
blackknightavalon said:
As with every CM build after 4.1.11.1 on the G1, ALWAYS FLASH GAPPS AFTER FLASHING THE ROM.
Click to expand...
Click to collapse
I did, yet ther was no camera app pre installed
Even the icon on the unlock streen existed, but when i unlocked it with the cam symbol nothing happened, it just went back to the lockscreen
I had mimicry before and therefore i got used to flash gapps, so did i with this jb rom too
Sent from my GT-N8010
I love this ROM, everything I generally use on a regular basis works fine. My only real problem is this ROM is a serious power drain, within an hour of being unplugged in the morning I have already lost 10% of the battery, by mid afternoon I am forced to plug the phone back in, this is something of an issue as I work at hospitals and plugging appliances into the mains is a violation of health and safety regulations, but I need my phone so I do what ya gotta do. Is there any way to reduce the drain from this ROM as I am fairly sure it is not any applications I have installed causing it, as none are running in the background when I check running apps.
plug it in to a computer with a logcat running, see what is going on that way. or if you aren't able to sit in front of a computer for a while watchdog is a nice app for this (keep in mind it should be for testing basis and be removed later as it to will always be running in the background)
Sent from my HTC Vision using xda premium
evernote makes phone slow
I am using this rom (build 124) and I have and after restoring all my apps it became really slow. After some try/error I found that uninstalling some apps solved the problem. After that I started installing my apps again one by one and I found installing evernote make the phone near unusable.
Anybody is experiencing this? it also happen if I install "camera 360".
I am running build 127 of this ROM which definitely seems faster than build 126 which was the first one I tried and seems to be quick enough to actually use it most of the time.
When things do go slow it seems to be when switching to a new app and seems more likely to happen is the new or old app is big.
Regarding more apps slowing things down I wonder if it is actually more widgets and background services. If this is, as I suspect, do to with how many apps can be cached in RAM for fast switching then the more apps have something running in the background, for example to sync with a cloud service or to keep a widget updated, the less RAM there will be for the apps you are trying to use and there will therefore be a greater chance the app you are trying to start has to be started from scratch.
These threads really need to stop, Flinny's test build is just that A TEST BUILD problems/issues are expected.
I think it's normal...anyway it don't obstruct me
tarroyo said:
These threads really need to stop, Flinny's test build is just that A TEST BUILD problems/issues are expected.
Click to expand...
Click to collapse
In my case I am certainly NOT contributing in order to criticise. Of course I know a test build may have issues but, like many others I suspect, I am happy to try the latest thing. When things don't work quite right it is worth discussing it. If we can understand what is happening we can help each other mitigate the issue and maybe even have something useful to feed back to developers.
I was running build 127 and things had become very slow. I have now updated to build 128 and the phone is fast again. At this stage I am not sure if this has anything to do with the new build or whether it is down to apps. I have all 45 apps installed but for many of those that sync to cloud services I have not yet got round to setting up the username/password for that to happen so this may be limiting the amount of background activity to a level where it doesn't get in the way. I'll try setting some of them up and see what happens.
Is there any good data on which of the major ROMs are most trouble free?
I am a pretty simple guy. All I really want is to be able to use my phone as a hotspot, take pictures without the camera app crashing and easy access to turn the torch on and off. Seems like a lot of the reviews spend a lot of time focusing on how many colors you can change and relatively little on the actually reliability of the ROM. This sort of leaves us asking eachother and it seems like everyone and their brother has an opinion on how stable any given ROM is and all swear by different ones.
At any rate, this just leaves me wondering if there is actually any good reviews or sources that summarize what the weeknesses of each ROM are. I know it is a tricky thing to ask, because they are always changing with each nightly build, but I have been pulling my hair out for the last couple years trying to find a properly stable ROM for my T999.
They cant really review stability and functionality on some roms, such as CM for example. Its going to be different for every model device, and even between 2 identical model devices you will still find one has issues while another does not. Thats why they usually stick to reviewing features and options. But also, what works best will vary from person to person even more so than from one device to the next. As is stated in all the "what's the best rom" threads, only you can determine what suits your needs best.
But for what its worth, imo, if its stability you're after, stick to whatever the manufacturer included on any given device.
DocHoliday77 said:
They cant really review stability and functionality on some roms, such as CM for example. Its going to be different for every model device, and even between 2 identical model devices you will still find one has issues while another does not. Thats why they usually stick to reviewing features and options. But also, what works best will vary from person to person even more so than from one device to the next. As is stated in all the "what's the best rom" threads, only you can determine what suits your needs best.
But for what its worth, imo, if its stability you're after, stick to whatever the manufacturer included on any given device.
Click to expand...
Click to collapse
I would stick with the stock rom, but I just really don't like it. I have also gotten very used to using a more stock version of Android and don't want to have to adjust back to using the stock rom, even if there are ways to get tethering to work.
aviphysics said:
I would stick with the stock rom, but I just really don't like it. I have also gotten very used to using a more stock version of Android and don't want to have to adjust back to using the stock rom, even if there are ways to get tethering to work.
Click to expand...
Click to collapse
What don't you like about the stock ROM? You say you want simple and don't care about changing anything, but you're not happy with stock either. What do you really want? lol. Also note, than any other ROM is not going to have the Samsung camera app, they are all going to be a lot more basic camera's, no wifi calling if you use that t-mo feature.
Torch on and off can be accessed with a shortcut on stock ROM, any third party app that lets you add a widget, or if you install xposed framework, you can add torch to the volume up button, so you can turn the torch on without even waking the phone. I'm with Doc, I'm a Touchwiz kind of guy too. I don't get the hate for it.
I just don't like some of the extra junk Samsung adds on. I like a more stripped down vanilla Android. I originally switched yo get rid of sVoice in particular and just got used to it. Not needing extra apps for WiFi tethering is a nice bonus.
At any rate. Just totally wiped the phone back to stock with Odin and installed the latest AOKP. No problems yet.
You can strip the Samsung apps out, and there is mods to enable native tethering.. But aosp or the kind is a nice option as well, just depends on what you want and need
aviphysics said:
I just don't like some of the extra junk Samsung adds on. I like a more stripped down vanilla Android. I originally switched yo get rid of sVoice in particular and just got used to it. Not needing extra apps for WiFi tethering is a nice bonus.
At any rate. Just totally wiped the phone back to stock with Odin and installed the latest AOKP. No problems yet.
Click to expand...
Click to collapse
Thinly veiled best ROM thread. SlimKat with Banks' minimal gapps.
I don't use my S3 anymore, but I have that ROM on it and my other two devices. It is filed under d2lte on their site, it's a unified build.
If you have kernel problems, use ktoonsez'. That one was always really solid.
Aerowinder said:
Thinly veiled best ROM thread.
Click to expand...
Click to collapse
LOL. Totally not meant to be a best ROM thread. Just wanted to know if anyone was tracking reliability or issues common to the different ROMs in a way that was easy to sift through and not totally anecdotal.
SlimKat with Banks' minimal gapps.
I don't use my S3 anymore, but I have that ROM on it and my other two devices. It is filed under d2lte on their site, it's a unified build.
If you have kernel problems, use ktoonsez'. That one was always really solid.
Click to expand...
Click to collapse
I never figured out what was causing problems with my last ROM. TBH, I don't even recall what the kernel and ROM combination was. It was just something some random XDA forum member suggested. The biggest issue is that every time I opened the camera app, went away from it and came back, it would crash. Also happened when switching between camera and video. Sometimes it would require a system reset to get the camera back. I think it was something to do with the app itself, cause other apps that took pictures never had any problems. Super annoying. There were some other issues to. I stuck it out for a long time because the app fixed a BT audio issue I was having and I was too lazy to do more searching or reflashing my phone from scratch.
Right now I am just trying to make my phone last until the Sony Z3 launches. I am pretty sure that will be my next phone. Hopefully it won't cost a crazy amount to import it if t-mobile doesn't get it right away.
aviphysics said:
LOL. Totally not meant to be a best ROM thread. Just wanted to know if anyone was tracking reliability or issues common to the different ROMs in a way that was easy to sift through and not totally anecdotal.
I never figured out what was causing problems with my last ROM. TBH, I don't even recall what the kernel and ROM combination was. It was just something some random XDA forum member suggested. The biggest issue is that every time I opened the camera app, went away from it and came back, it would crash. Also happened when switching between camera and video. Sometimes it would require a system reset to get the camera back. I think it was something to do with the app itself, cause other apps that took pictures never had any problems. Super annoying. There were some other issues to. I stuck it out for a long time because the app fixed a BT audio issue I was having and I was too lazy to do more searching or reflashing my phone from scratch.
Right now I am just trying to make my phone last until the Sony Z3 launches. I am pretty sure that will be my next phone. Hopefully it won't cost a crazy amount to import it if t-mobile doesn't get it right away.
Click to expand...
Click to collapse
AOSP camera was always crap in general but especially so on the S3.
You can get an updated on in the play store now, so you can freeze the AOSP one.
Aerowinder said:
AOSP camera was always crap in general but especially so on the S3.
You can get an updated on in the play store now, so you can freeze the AOSP one.
Click to expand...
Click to collapse
The camera in the latest AOKP was working fine, but I downloaded the Google Camera app just to check it out. Works fine taking normal pictures, but the blur mode causes it to crash when you try to take a picture and the panorama/photosphere modes won't take pictures. I found some other people with identical problems, but didn't see a clear solution.
aviphysics said:
The camera in the latest AOKP was working fine, but I downloaded the Google Camera app just to check it out. Works fine taking normal pictures, but the blur mode causes it to crash when you try to take a picture and the panorama/photosphere modes won't take pictures. I found some other people with identical problems, but didn't see a clear solution.
Click to expand...
Click to collapse
It was originally for the Nexus 5, then they put it on the play store for everyone. Clearly issues with non Google devices.
I'd suggest a third party camera app, like Camera ZOOM or something.
All credit to this ROM goes to rogersb11. The only thing I did was change the install script so that it works on the d2tmo. With that said, this is an unofficial ROM and is not supported in any way by the original developer. That means don't go bugging rogersb11 with any questions about this. It is unsupported. It is only here so us d2tmo users can enjoy his kick ass ROM until and if there is an official port.
I will help in any way that I can, this is what I am using for my daily driver right now and I love it.
The camera does not work. I don't use my camera much, so I am fine with that for now. If you need a working camera, then this is not the ROM you want on your phone.
A few notes before install.
Thanks to rogersb11 for the Cyanide ROM, TheGeekyNimrod for the d2att port, without which I could not have done this, and leonid002, because without his assistance, I would not have even known how to do this to begin with.
First let's discuss the bugs:
The AOSP Keyboard will continuously crash on you from the first boot. Make sure you have a Google keyboard APK at the ready. This ROM comes with ES File Explorer, thanks to rogersb11, who put the ROM together in the first place, so you should have no problem installing any APKs you need to install, even before replacing the keyboard.
Install Google keyboard, then disable your AOSP keyboard. One this is done your keyboard will work just fine.
The phone will self report as the i747, that is where this ROM came from. As soon as I find what I need to change to fix that, I will update.
I believe the camera bug is still here, havent tested it yet, so just download Nexus camera from the Play store.
Other than that, works great so far.
Anyway, now it is time for the... Wait for it...
DISCLAIMER:
Despite the quality of this ROM, it is an ALPHA build.
Neither I, or any developer is responsible if you brick your device in any way, you're neighbor steals it, your nephew flushes it down the toilet, or you somehow travel back in time to an alternate 2012 where the world comes to an end in December, resulting in your phone being destroyed. Any damage to your device is YOUR RESPONSIBILITY.
You should be able to use any current Lollipop gapps with this ROM.
INSTRUCTIONS:
Download ROM below
Install a recovery if you don't have one (I use TWRP Multiboot, found in this same forum)
Factory reset (wipe Dalvik, cache, you know the drill)
Install the ROM (link below)
Install Gapps
Reboot into Cyanide
Install Google keyboard (or maybe your favorite alternative, SwiftKey works, not sure about anything else yet)
Disable AOSP Keyboard
Enjoy.
CYANIDE ROM DOWNLOAD:
1-02-2014 https://www.androidfilehost.com/?fid=95864024717074572
12-28-2014 https://www.androidfilehost.com/?fid=95864024717073794
XDA:DevDB Information
Cyanide-L Alpha d2tmo, ROM for the T-Mobile Samsung Galaxy S III
Contributors
reeferbob, leonid002, TheGeekyNimrod,
rogersb11,
Source Code: https://www.androidfilehost.com/?fid=95864024717073794
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Testing
Created 2015-01-02
Last Updated 2015-01-02
One thing I like about this ROM over CM12 is that the option to adjust your DPI is baked right in. Another is the darker theme, and the fact that you can wake with the Home button once again.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Thanks for taking the time to port this I will check it out in the morning
Sent from my d2lte using XDA Free mobile app
Thanks OP
Downloading now
?
This thread is now opened and continue.
Edfunkycold
Have a great day!
Here's something for the webOS people: Download the app Swipe Home Button from the Play Store, and configure it so that swipe up brings up recents, and swiping far up brings up the app drawer. Do this and swap the Menu and Back buttons, and it feels that much closer to a Pre, albeit without a keyboard, and on much better hardware. I still wish I knew of a way to modify the recents so we could implement webOS 2.x like card stacks in some form. I will be trying to learn how I might be able to do that in my free time though, that was always my goal since I got an Android phone, was to try and make the UI as intuitive as webOS was. Lollipop delivered with that in a big way, but I guess I'm a little OCD and am nitpicking the small details at this point. I'm not sure how much of it is lollipop, and how much of it is from the Cyanide coder's skills, but it's snappy as hell, and definitely made huge steps towards what I wanted to see Android become.
Now just to get rid of Google's intrusiveness (because let's be honest, you lose much of the functionality of Android if you don't install the gapps) and still keep the functionality of fundamentals like the app store, Maybe a third party solution, kind of like Preware, would be the way to go about this? That still leaves the issue of fragmentation with different apps being in different app stores, however. Either way, this is the best Android has gotten for me, and I can only hope it gets even better, who knows, maybe somewhere along the way I will learn a thing or two and be able to help get there.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
reeferbob said:
Here's something for the webOS people: Download the app Swipe Home Button from the Play Store, and configure it so that swipe up brings up recents, and swiping far up brings up the app drawer. Do this and swap the Menu and Back buttons, and it feels that much closer to a Pre, albeit without a keyboard, and on much better hardware. I still wish I knew of a way to modify the recents so we could implement webOS 2.x like card stacks in some form. I will be trying to learn how I might be able to do that in my free time though, that was always my goal since I got an Android phone, was to try and make the UI as intuitive as webOS was. Lollipop delivered with that in a big way, but I guess I'm a little OCD and am nitpicking the small details at this point. I'm not sure how much of it is lollipop, and how much of it is from the Cyanide coder's skills, but it's snappy as hell, and definitely made huge steps towards what I wanted to see Android become.
Now just to get rid of Google's intrusiveness (because let's be honest, you lose much of the functionality of Android if you don't install the gapps) and still keep the functionality of fundamentals like the app store, Maybe a third party solution, kind of like Preware, would be the way to go about this? That still leaves the issue of fragmentation with different apps being in different app stores, however. Either way, this is the best Android has gotten for me, and I can only hope it gets even better, who knows, maybe somewhere along the way I will learn a thing or two and be able to help get there.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
another rom to play with thank man
In the future, I do plan to start officially building this for d2tmo. Just got a few things to get straightened out before I do. I have the device trees and everything, just gotta tie up some other ends before I dive into supporting two devices.
That said though, I will need testers as I don't own this particular device, and maybe someone to help d2tmo users trouble shoot problems that crop up specifically for their device.
Sent from my SAMSUNG-SGH-I747
Masterloki666 said:
Thanks for taking the time to port this I will check it out in the morning
Sent from my d2lte using XDA Free mobile app
Click to expand...
Click to collapse
So I've been running this all day and coming from latest nightly build this isn't bad at all still has some work to be done but its loli-goodness on our ol s3 that being said I did have a few hangs when listening to Pandora when trying to turn on screen an switch songs was at work an unable to see what exactly happened anyone else ? BTW thanks again
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
The only things I've noticed so far are as follows:
Firefox makes Metro PCS think I'm tethering for some reason, except for, ironically, when I have request desktop site checked. Opera works great though. Not to mention, if you make sure to go into the settings and put Opera on Phone mode, the look and feel of it just kind of flows with Lollipop's multitasking cards, just horizontally scrolling and vertically closing.
I heavily dislike Chrome, so I don't use it, and couldn't tell you if it works or not, because I haven't installed it.
The stock browser kind of hung on me one time, but I haven't been able to make it happen again.
The phone shuts off without warning, it seems as soon as the battery goes down to 14%
As far as Pandora, I really haven't installed it, because I have Rhapsody. I may give it a shot and see what happens.
The Firefox issue probably has something to do with the lollipop user agent, as I know that this is how Metro blocks tethering. Still weird that it works fine with the other browsers though. Anyway, due to issues beyond my control, I probably won't be online for about two weeks after today, all my bills came up due at once so my phone bill will have to wait until next payday. The extra days off work the week of Christmas really put a strain on my finances. Sure I'll probably hit a hotspot from time to time, but my phone is my main internet connection at home. Hell, it's faster than cable internet or even any DSL connection I've ever had, so why spend the extra money? I'm really surprised how well MetroPCS works in Denver, even without an LTE phone. The HSPA+ is plenty fast. Before the T-Mobile deal, I had a Metro CDMA phone, in Texas, and it was atrocious.
But yeah, I have WiFi at work so I can keep checking in from time to time when I'm out on a smoke break, plus, I'm definitely keeping an eye out for new developments.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
I just got the new build installed, the dark color scheme is awesome. I just left in the check in the installer script for the d2att this time, and added one for d2tmo, maybe it will help anybody who may be testing across multiple devices.
In this one I've noticed the AOSP keyboard is working fine so far.
I will upload it as soon as I get the chance.
If you dirty flash over the previous build, make sure when you install the new build to reinstall the gapps. After its finished wipe the cache and dalvik, otherwise Google Play services will just keep crashing.
After reinstalling gapps, wiping the dalvik and cache, I got one Google play services error, but it hasn't seemed to affect anything.
Everything about this is the same as the build from rogersb11, I just edited the install script so that it installs on d2tmo as well. Just like the earlier build, it will be unsupported. There are bugs, and on an early build, that is to be expected. But so far, I've definitely seen an improvement.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Installed and running pretty smooth. The previous build would randomly advance my clock by 5 hours and would show all incoming calls as from "private". The new build however does none of those things.
So far on the new build, music has crashed once but relaunching it fixed that. I was not sure what nexus camera to get, not to mention their permissions were a bit crazy so I went with Open Camera and it works fine.
Thanks for taking the time to make and port this. The t999 is starting to fall to the way side and I cannot afford a new device so being able to run 5.0 is a blessing.
Working perfectly Thanks to all the devs over at d2att right How come no devs have d2tmo?? Smh.
No SIM
Hey did a clean install and the rom is telling me I have no sim inserted? Anyone else running in to this issue or have a quick fix? I tried editing APN's but it wouldnt save???
Try installing the older build first, and then install gapps, let it run it's first boot, and let everything set up. Then reboot into recovery, and install the later build, reinstall gapps, and wipe cache and Dalvik. Then boot again as normal.
This has resolved a couple of issues for me, although I haven't gotten the insert SIM message with either of these builds. Can't thoroughly test anything until the end of next week though, my phone service is cut off until I can pay my bill on the 15th, and my WiFi reception where I'm at is spotty at best (on all my devices).
Also, I am on MetroPCS, not T-Mobile, I'm just using the T999 on their network.. Which I guess is also the T-Mobile network. Not sure if there are any major differences or not.
The only issue I've had was with su, and after installing SuperSU, a couple reboots, the last one was after changing my DPI to 240, I was able to gain root access.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
jonesin said:
Hey did a clean install and the rom is telling me I have no sim inserted? Anyone else running in to this issue or have a quick fix? I tried editing APN's but it wouldnt save???
Click to expand...
Click to collapse
You may need to update your modem. I don't know about the T-Mobile modems and their availability, but for most using d2att in any LP rom, this has solved that issue.
Sent from my SAMSUNG-SGH-I747
I just installed it on my t999l. Will report back how it runs. Thanks for the ROM.
jonesin said:
Hey did a clean install and the rom is telling me I have no sim inserted? Anyone else running in to this issue or have a quick fix? I tried editing APN's but it wouldnt save???
Click to expand...
Click to collapse
I just installed the newer version, and I have the same problem. My device is t999l. Did you manage to fix the problem?
goldentequila said:
I just installed the newer version, and I have the same problem. My device is t999l. Did you manage to fix the problem?
Click to expand...
Click to collapse
Yes I was able to resolve this by updating to the latest baseband/radio. Resolved the problem immediately, I used the latest one available dated march of 2014. Hope this helps.
jonesin said:
Yes I was able to resolve this by updating to the latest baseband/radio. Resolved the problem immediately, I used the latest one available dated march of 2014. Hope this helps.
Click to expand...
Click to collapse
Thank you. I'll try that.
---------- Post added at 04:31 AM ---------- Previous post was at 04:29 AM ----------
goldentequila said:
Thank you. I'll try that.
Click to expand...
Click to collapse
OK. I encountered one major issue that was a bit scary. Everything was working fine at the first boot (except for the sim card). But, I turned off my phone. I then powered it back on, but it wouldn't boot into Android. It would just get stuck at the initial boot screen and go black. I was able to fix this by removing the battery and restarting it. If anyone experiences this issue, try that.
I tried turning off my phone to boot into recovery, and the same problem happened. I'm going to reinstall the ROM and see if the problem goes away.
When the problem first started I was running CyanogenMod 11 nightly. It ran sporadically and I replaced the battery, which fixed all of the problems I was experiencing except for the camera crash. I tried out SlimRom and then back to CM but it doesn't seem to work on any ROMs. I also tried disabling the built in camera and using the Google camera, and vice versa.
There are two error it gives:
Camera Error!
Cannot connect to camera.
And:
Unfortunately, camera has stopped.
I assume that the first error is given by the application and the second error is given by android itself.
The really weird thing, is that the CamScanner app can access my camera fine without crashing.
I have just been dealing with the issue, because I have tried everything I can think of to fix it. But I would like to use my camera as I am sure anyone could understand.
If anyone could brainstorm up any ideas as to why its crashing, feel free to share.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
After updating Cyanogenmod to the latest nightly, the problem persists.
For anyone who has the same problem, I did deep digging on the web and found some flashable zips marketing themselves as camera fixes, but all of then failed.
I did however come up with a work around that I am perfectly comfortable with keeping permanently. I installed the ex-cyanogenmod camera -- Focal.
Focal is on the Google play store and hasn't crashed for me once yet. Why get rid of something that ain't broke, Cyanogenmod?
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
dluds10 said:
For anyone who has the same problem, I did deep digging on the web and found some flashable zips marketing themselves as camera fixes, but all of then failed.
I did however come up with a work around that I am perfectly comfortable with keeping permanently. I installed the ex-cyanogenmod camera -- Focal.
Focal is on the Google play store and hasn't crashed for me once yet. Why get rid of something that ain't broke, Cyanogenmod?
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
i think the slimROM thread has a camera-fix-.zip on it , or did. but i see you fixed the issue.:good:
"all i can really do , is stay out of my own way and let the will of heaven be done"
I found at least 4 different ones for the Galaxy S3 but all of them failed. I'll have look into the SlimRom one though because I don't think that was one of the ones I tried.
I recently updated to the latest bootloader and 5.1.1 Touchwiz. I'm having a rough time without xposed and am considering changing to AOSP and scrapping Touchwiz so I can get my Xposed customizations back.
For anyone who has made this move, is there anything significant you lose by scrapping Touchwiz or any reason I should continue waiting?
UPSGuy said:
I recently updated to the latest bootloader and 5.1.1 Touchwiz. I'm having a rough time without xposed and am considering changing to AOSP and scrapping Touchwiz so I can get my Xposed customizations back.
For anyone who has made this move, is there anything significant you lose by scrapping Touchwiz or any reason I should continue waiting?
Click to expand...
Click to collapse
No fingerprint scanner, S-Pen features, basically all Galaxy line features lost and that's about it. I've had annoying times where SMS/MMS wouldn't go through and I had to keep doing stuff to make it go back. So if you like a Note 4 for its gimmicky features, I wouldn't go to AOSP. It doesn't hurt to try for a day though.
Sent from my SM-N910P using Tapatalk
XAlexander_AlexanderX said:
No fingerprint scanner, S-Pen features, basically all Galaxy line features lost and that's about it. I've had annoying times where SMS/MMS wouldn't go through and I had to keep doing stuff to make it go back. So if you like a Note 4 for its gimmicky features, I wouldn't go to AOSP. It doesn't hurt to try for a day though.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I took your suggestion and tried AOSP via CM12. I like the changes in the overall UI since the last time I ran CM on a previous device, but I would miss the fingerprint scanner for the screen lock. The google camera that came when I flashed the Gapps (tk_gapps-stock-5.1.1-20150816b-signed.zip) doesn't play nicely with CM12. "Could not connect to camera" and several seconds for the app to open when it does decide to open, and then if you decide to take a second photo it's crash city. I guess I'll go back to touchwiz, but I'm really gonna miss my xposed
UPSGuy said:
I took your suggestion and tried AOSP via CM12. I like the changes in the overall UI since the last time I ran CM on a previous device, but I would miss the fingerprint scanner for the screen lock. The google camera that came when I flashed the Gapps (tk_gapps-stock-5.1.1-20150816b-signed.zip) doesn't play nicely with CM12. "Could not connect to camera" and several seconds for the app to open when it does decide to open, and then if you decide to take a second photo it's crash city. I guess I'll go back to touchwiz, but I'm really gonna miss my xposed
Click to expand...
Click to collapse
People have fixed the problem with the camera by uninstalling the google camera and install it via Google Play Store. Android 6/Marshmallow is supposed to have native fingerprint support.
Sent from my SM-N910P using Tapatalk
Cool, also everytime any app attempted to access GPS the app would crash, the UI would crash and only the wallpaper was visible. Buttons went unresponsive and required a reboot. This happened with Maps and with the chrome browser when it tried to access GPS.
Back to touchwiz we go...