Ever since the Nexus 5 got Lollipop, there have been developers wanting to take advantage of the new camera API. This would greatly improve our already beastly camera.
https://github.com/PkmX/lcamera
I am wondering if we can get this to work on our devices. I tried installing the APK but the latest version says it's incompatible and the earlier versions crash.
DarkFlasher said:
Ever since the Nexus 5 got Lollipop, there have been developers wanting to take advantage of the new camera API. This would greatly improve our already beastly camera.
https://github.com/PkmX/lcamera
I am wondering if we can get this to work on our devices. I tried installing the APK but the latest version says it's incompatible and the earlier versions crash.
Click to expand...
Click to collapse
Same question here...
Have you tried editing the build prop to say the phone is a Nexus 5 or 6? Should work then.
DarkFlasher said:
Ever since the Nexus 5 got Lollipop, there have been developers wanting to take advantage of the new camera API. This would greatly improve our already beastly camera.
https://github.com/PkmX/lcamera
I am wondering if we can get this to work on our devices. I tried installing the APK but the latest version says it's incompatible and the earlier versions crash.
Click to expand...
Click to collapse
Are you even on Lollipop?
I've tried this on Lollipop CM12. It fails with "L Camera is not supported on your device" message. Checked the source code:
Code:
val capabilities = characteristics.get(REQUEST_AVAILABLE_CAPABILITIES)
val requiredCapabilities = List(
REQUEST_AVAILABLE_CAPABILITIES_MANUAL_SENSOR,
REQUEST_AVAILABLE_CAPABILITIES_MANUAL_POST_PROCESSING,
REQUEST_AVAILABLE_CAPABILITIES_RAW)
if (!(requiredCapabilities forall { capabilities contains _ })) {
toast("L Camera is not supported on your device")
finish()
return
}
which means that driver is not returning all the required capabilities, if returning any of them at all. So changing phone's name to nexus5 or nexus6 won't help, we need that camera driver fixed
NForce25 said:
I've tried this on Lollipop CM12. It fails with "L Camera is not supported on your device" message. Checked the source code:
Code:
val capabilities = characteristics.get(REQUEST_AVAILABLE_CAPABILITIES)
val requiredCapabilities = List(
REQUEST_AVAILABLE_CAPABILITIES_MANUAL_SENSOR,
REQUEST_AVAILABLE_CAPABILITIES_MANUAL_POST_PROCESSING,
REQUEST_AVAILABLE_CAPABILITIES_RAW)
if (!(requiredCapabilities forall { capabilities contains _ })) {
toast("L Camera is not supported on your device")
finish()
return
}
which means that driver is not returning all the required capabilities, if returning any of them at all. So changing phone's name to nexus5 or nexus6 won't help, we need that camera driver fixed
Click to expand...
Click to collapse
So it is more of a case of the camera drivers not supporting all of the new API stuff then? Hopefully it isn't to much of a job or we'll be waiting for the LG update.
Since we have good Lollipop ROM's popping out, I'd also like to get my hands on this.
In the meanwhile try Mi2RAW on google play...
kultus said:
In the meanwhile try Mi2RAW on google play...
Click to expand...
Click to collapse
It is not working with CM12 Unofficial. A least in my case.
kultus said:
In the meanwhile try Mi2RAW on google play...
Click to expand...
Click to collapse
But it doesn't support Lollipop's new camera API's. The whole point of LCamera is to use those new API's and let the user mess around with them. Sadly, it seems that many devices that have been updated to Lollipop, officially or through ports, don't have the new API's and are just using wrappers, meaning none of the new functions are there. Someone smarter than I am would have to look at the source code for our ports to see if any of them actually include support for the new stuff.
https://github.com/PkmX/lcamera/issues/3
https://github.com/PkmX/lcamera/issues/14
Thanks for info very said. And its ofcourse very unfortunate for android fragmentation again. I hate google if its truth, but have to wait for more investigation for LG phones. On the other side, It seems to be a nonsence, that lollipop wont have new camera API in system for some phones...we will see, its too soon.
Related
So, with the recent news of a port of Sailfish to the Nexus 4, I've been thinking. Does anyone know what it would take to port this OS? Does anyone here know the system well enough to be able to describe what it would entail to port this to another Nexus device, like the Nexus 5?
To clarify, I'm not asking anyone else to port the OS (though if someone would like to, that's fine), because I'm more than happy to do the work for it. I've just never actually ported anything like a completely new OS, so I don't know what it would involve and I'd like it if someone explained or even gave a rough outline of what would need to be done.
jabza said:
So, with the recent news of a port of Sailfish to the Nexus 4, I've been thinking. Does anyone know what it would take to port this OS? Does anyone here know the system well enough to be able to describe what it would entail to port this to another Nexus device, like the Nexus 5?
To clarify, I'm not asking anyone else to port the OS (though if someone would like to, that's fine), because I'm more than happy to do the work for it. I've just never actually ported anything like a completely new OS, so I don't know what it would involve and I'd like it if someone explained or even gave a rough outline of what would need to be done.
Click to expand...
Click to collapse
I tried to do that a few weeks back but didn't have time to hunt down all the problems I had.
Check out this blog:
http://martinbrook.blogspot.com/?m=1
There's a rough guide in one entry. Basically you need to build CM from source, apply libhybris patches and then set up Mer on top of it. When you get Mer running it should be easy to install Sailfish packages. Libhybris is a compatibility layer for Android drivers to work on normal linux. Good luck and let us know how it goes. I had troubles with building Mer image for my device. In the video you mentioned it looks like the whole patch+Mer+ sailfish packages is this second prepared zip he flashes.
Sent from my LG-P760 using Tapatalk
jabza said:
So, with the recent news of a port of Sailfish to the Nexus 4, I've been thinking. Does anyone know what it would take to port this OS? Does anyone here know the system well enough to be able to describe what it would entail to port this to another Nexus device, like the Nexus 5?
To clarify, I'm not asking anyone else to port the OS (though if someone would like to, that's fine), because I'm more than happy to do the work for it. I've just never actually ported anything like a completely new OS, so I don't know what it would involve and I'd like it if someone explained or even gave a rough outline of what would need to be done.
Click to expand...
Click to collapse
Hey man have you tried yet? My laptop is currently being serviced but upon its return I really want to try this.
aeppacher said:
Hey man have you tried yet? My laptop is currently being serviced but upon its return I really want to try this.
Click to expand...
Click to collapse
Not yet; I've been busy working with other things. Though it looks like we're in pretty good shape so far because the recent Ubuntu Touch builds have been getting doing some good work for Mer on the Nexus 5, so hopefully we can use that progress. I just haven't found the time to work on this yet, unfortunately.
jabza said:
Not yet; I've been busy working with other things. Though it looks like we're in pretty good shape so far because the recent Ubuntu Touch builds have been getting doing some good work for Mer on the Nexus 5, so hopefully we can use that progress. I just haven't found the time to work on this yet, unfortunately.
Click to expand...
Click to collapse
I think SF is a really promising OS more so than Firefox is, tizen, and I think more polished than Ubuntu phone. I can't wait to start developing for it so I really want to port it when I get my laptop back. Nice thing is if you use Qt you can basically just write one app that will natively run on Ubuntu and SailFish
aeppacher said:
I think SF is a really promising OS more so than Firefox is, tizen, and I think more polished than Ubuntu phone. I can't wait to start developing for it so I really want to port it when I get my laptop back. Nice thing is if you use Qt you can basically just write one app that will natively run on Ubuntu and SailFish
Click to expand...
Click to collapse
I agree completely. It's sad that it hasn't seen a bigger leap in development, but I hope that it'll pick up sooner rather than later. I was just reading earlier today about Qt, which is pretty nifty if you ask me. Hopefully I'll find some time this week to actually make progress on it.
jabza said:
I agree completely. It's sad that it hasn't seen a bigger leap in development, but I hope that it'll pick up sooner rather than later. I was just reading earlier today about Qt, which is pretty nifty if you ask me. Hopefully I'll find some time this week to actually make progress on it.
Click to expand...
Click to collapse
Well once I get my laptop back I will message you and maybe we can tag team it
Nice..get it work!
Lähetetty minun Nexus 4 laitteesta Tapatalkilla
Jolla is working hard on the android hardware adaptation libraries, here's official status about whats going on, its work in progres and might not be quite upto date.
https://wiki.merproject.org/wiki/Adaptations/libhybris
source: https://twitter.com/HarriHakulinen/status/433163017555959808
jabza said:
I agree completely. It's sad that it hasn't seen a bigger leap in development, but I hope that it'll pick up sooner rather than later. I was just reading earlier today about Qt, which is pretty nifty if you ask me. Hopefully I'll find some time this week to actually make progress on it.
Click to expand...
Click to collapse
Whippler said:
Jolla is working hard on the android hardware adaptation libraries, here's official status about whats going on, its work in progres and might not be quite upto date.
https://wiki.merproject.org/wiki/Adaptations/libhybris
source: https://twitter.com/HarriHakulinen/status/433163017555959808
Click to expand...
Click to collapse
I tweeted Jolla asking if there was now an arm image within the SDK instead of just a x86 one and they told me that there is so that will take care of one major issue.
Android One port
Hi there! I'm not sure if this is where I can ask but I will, just to make sure. Could it be possible for someone to please port Sailfish OS to the Android One devices? They share nearly identical hardware (only differences are in storage).
Here are the specs:
Processor: Mediatek MT6582M 1.3GHz Quad Core ARM Cortex-A7 CPU
GPU: Mali-400 MP2
RAM: 1GB
Camera: 5.0 MP Autofocus Back Camera with LED Flash; 2.0 MP Front Camera
Storage: 4/8 GB (varies; categorized into sprout4 and sprout8 devices, respectively)
MicroSD: 32 GB max caapacity
Sim: Dual Micro
Network: 3G HSPA+, 2G EDGE and GPRS; Wi-Fi
Bluetooth: 4.0 with LE support
Location sensor: GPS with A-GPS
FM Radio
Ports: MicroUSB 2.0, 3.5mm audio jack
Other sensors: Gyroscope, Accelerometer, Ambient Light Sensor
Battery: 1,780mAh Li-ion
Don't worry about the MediaTek processor hampering sources, check Google repos for code. Also sources are updated frequently.
I want to experience Sailfish on my phone and likely other fellow Android One users. Minimal modifications necessary for sprout8-specific patches.
sailfish os
hi i seen list of devices already ported using HADK some devices such as samsung they have some problem in application such as gps and fingerprint .... why these application doesnt work ?? is this problems based in sailfish error or this problems related to porters ? and hiw to fix this problems
sailfish os
hi i seen list of devices already ported using HADK some devices such as samsung they have some problem in application such as gps and fingerprint .... why these application doesnt work ?? is this problems based in sailfish error or this problems related to porters ? and hiw to fix this problems
As per the title, has development ceased on that style of multi-window? Is the 'Floating Window' similar? With the Nexus 6 rumored to have a 5.9" screen I was hoping that a custom ROM would have something similar to the LG G3 Dual Windows which is great.
parker09 said:
As per the title, has development ceased on that style of multi-window? Is the 'Floating Window' similar? With the Nexus 6 rumored to have a 5.9" screen I was hoping that a custom ROM would have something similar to the LG G3 Dual Windows which is great.
Click to expand...
Click to collapse
It's been on hold for quite some time. It was about 90% working, but had some final issues that needed work. After further review, xplodwild actually wants to completely rewrite the feature again after reading up on some interesting infrastructure in Android we didn't know about before. (I don't have the link on this machine).
At this point it might not get finalized until L - since L is going to change a LOT of different things.
Entropy512 said:
It's been on hold for quite some time. It was about 90% working, but had some final issues that needed work. After further review, xplodwild actually wants to completely rewrite the feature again after reading up on some interesting infrastructure in Android we didn't know about before. (I don't have the link on this machine).
At this point it might not get finalized until L - since L is going to change a LOT of different things.
Click to expand...
Click to collapse
Thanks for the fast response, glad it didn't get abandoned.
parker09 said:
Thanks for the fast response, glad it didn't get abandoned.
Click to expand...
Click to collapse
Yeah it's something I've wanted to finish up but didn't have time. The last issues with the patch proved significantly more difficult/time-consuming to solve than expected. Namely:
1) Layout in some apps is totally broken. G+ is the most obvious example of this. As a result we're probably going to have to implement a whitelist similar to Samsung's multiwindow. (Apps won't work unless whitelisted by the frameworks or the app declares itself as compatible in the manifest. We'll likely use the same manifest declarations Samsung does, e.g. assume any app compatible with Samsung's multiwindow should be compatible with ours.
2) Re-layout of apps after a rotation was really flaky. This is the #1 reason plodey wants to do a rewrite. He's been buried in a special project for a while, he was supposed to be wrapping up in September but that schedule seems to have slipped.
Hello guys
May i ask if OmniROM will ever make it to the Xperia Z2 (Sirius)?
Been missing it for ages now
Keep up the great work
mariotme said:
Hello guys
May i ask if OmniROM will ever make it to the Xperia Z2 (Sirius)?
Been missing it for ages now
Keep up the great work
Click to expand...
Click to collapse
I normally just report device requests, but since I've done a lot of the Sony bringups:
I wanted a Z2. I really, really wanted one.
However I don't buy greymarket imports, and Sony refused to sell the Z2 in North America until after the Z3 was launched. Even now, the purchasing link is nearly impossible to find (it is not listed for sale anywhere on sonymobile.com)
Z3 is a possibility if it goes on sale unlocked in North America in a timely fashion. (Which is unlikely...) Z2 is a possibility if some maintainer picks it up, of course, but considering the device's successor is out now, that's pretty unlikely.
Entropy512 said:
I normally just report device requests, but since I've done a lot of the Sony bringups:
I wanted a Z2. I really, really wanted one.
However I don't buy greymarket imports, and Sony refused to sell the Z2 in North America until after the Z3 was launched. Even now, the purchasing link is nearly impossible to find (it is not listed for sale anywhere on sonymobile.com)
Z3 is a possibility if it goes on sale unlocked in North America in a timely fashion. (Which is unlikely...) Z2 is a possibility if some maintainer picks it up, of course, but considering the device's successor is out now, that's pretty unlikely.
Click to expand...
Click to collapse
I totally understand Entropy512! Thanks for your input buddy. Appreciate all your efforts man. Keep it up :good:
Entropy512 said:
I wanted a Z2. I really, really wanted one.
Click to expand...
Click to collapse
Thanks for your answer, yes that's the best smartphone I've ever got! Why the hell do they think they don't need to sell their devices in america??
As I know you are a major developer of OmniRom, I really hope you will be able to get an Xperia Z4, and hopefully port the ROM on it..
Thanks for your work!:good:
May I Taste said:
Thanks for your answer, yes that's the best smartphone I've ever got! Why the hell do they think they don't need to sell their devices in america??
As I know you are a major developer of OmniRom, I really hope you will be able to get an Xperia Z4, and hopefully port the ROM on it..
Thanks for your work!:good:
Click to expand...
Click to collapse
I'll probably skip the Z4 thanks to Sony's crazy 6-month product cycle.
I have a Z3 but so far it's stock. This device is holding a record for the longest I've gone without root/unlocking the BL.
Sony did an awesome job with the stock firmware on the SIM-unlocked Z3.
Entropy512 said:
I'll probably skip the Z4 thanks to Sony's crazy 6-month product cycle.
I have a Z3 but so far it's stock. This device is holding a record for the longest I've gone without root/unlocking the BL.
Sony did an awesome job with the stock firmware on the SIM-unlocked Z3.
Click to expand...
Click to collapse
Thanks for your kind answer and I can understand you. It seems however that the Z4 will now last for one year as flagship. Anyway I'll make sure to stay tuned if by chance you work on OmniROM for it.
Have a wonderful year, you and your whole family!
There some unofficial builds for the Sony Sirius floating around...
http://infectedbuilds.net/downloads/sirius/omni_lp/
From my very brief play with it, there's no Cam or NFC but everything else seems pretty useable.
A number of Omni team members are working with the Sony AOSP guys. Short-term it means a lot of things are broken that aren't in CM since Sony AOSP is reworking a bunch of stuff onto a newer unified kernel that will support a large variety of devices. Long-term it'll allow us to support more Sony devices with less effort.
I think one of the guys working this has a sirius... I forget who.
I just synced all the Omnirom repos and compiled for the Z2. It works ok, just no Camera, recovery and there seems to be a bug around internal storage, as it thinks there is no space left.
I'd be interested in helping to fix these things, I'm pretty comfortable using git and gerrit and know some Java and C++ but I have no idea where to start.
Code:
adb logcat | grep camera
- waiting for device -
E/CameraService( 373): Could not load camera HAL module
W/ResourcesManager( 1057): Asset path '/system/framework/com.google.android.camera2.jar' does not exist or contains no resources.
I/CameraManagerGlobal( 1057): getCameraService: Reconnecting to camera service
E/CameraService( 373): getCameraVendorTagDescriptor: camera hardware module doesn't exist
W/CameraManagerGlobal( 1057): Failed to set up vendor tags: The camera device is removable and has been disconnected from the Android device, or the camera service has shut down the connection due to a higher-priority access request for the camera device.
So I'd guess I'd have to find out why the camera HAL module can't be loaded?
mikeysteele said:
I just synced all the Omnirom repos and compiled for the Z2. It works ok, just no Camera, recovery and there seems to be a bug around internal storage, as it thinks there is no space left.
I'd be interested in helping to fix these things, I'm pretty comfortable using git and gerrit and know some Java and C++ but I have no idea where to start.
Code:
adb logcat | grep camera
- waiting for device -
E/CameraService( 373): Could not load camera HAL module
W/ResourcesManager( 1057): Asset path '/system/framework/com.google.android.camera2.jar' does not exist or contains no resources.
I/CameraManagerGlobal( 1057): getCameraService: Reconnecting to camera service
E/CameraService( 373): getCameraVendorTagDescriptor: camera hardware module doesn't exist
W/CameraManagerGlobal( 1057): Failed to set up vendor tags: The camera device is removable and has been disconnected from the Android device, or the camera service has shut down the connection due to a higher-priority access request for the camera device.
So I'd guess I'd have to find out why the camera HAL module can't be loaded?
Click to expand...
Click to collapse
Camera is far away from being supported. The blobs are completely missing, because they simply won't work with our kernel.
There's work being done, however a lot of it has to be done by someone within Sony and that results in stuff having to go through a legal approval process.
In theory it might be possible with some work to get 5.0 camera blobs working with a lot of kernel hacking, but most people are focusing on a cleaner approach that will take longer and unfortunately has dependencies on Sony's lawyers.
Entropy512 said:
Camera is far away from being supported. The blobs are completely missing, because they simply won't work with our kernel.
There's work being done, however a lot of it has to be done by someone within Sony and that results in stuff having to go through a legal approval process.
In theory it might be possible with some work to get 5.0 camera blobs working with a lot of kernel hacking, but most people are focusing on a cleaner approach that will take longer and unfortunately has dependencies on Sony's lawyers.
Click to expand...
Click to collapse
Thanks for the update. I noticed there weren't any camera blobs in the source, so I assumed it wasn't as simple as just adding them in. I see on github the CM guys hacked their kernel to be able to use the old Jellybean camera blobs which looks painful. Hopefully Sony's lawyers aren't too obstructionist. Although to their credit the Sony stock rom isn't actually too bad. Nothing compared to Omni Rom though.
mikeysteele said:
Thanks for the update. I noticed there weren't any camera blobs in the source, so I assumed it wasn't as simple as just adding them in. I see on github the CM guys hacked their kernel to be able to use the old Jellybean camera blobs which looks painful. Hopefully Sony's lawyers aren't too obstructionist. Although to their credit the Sony stock rom isn't actually too bad. Nothing compared to Omni Rom though.
Click to expand...
Click to collapse
Yeah. They used a kernel backcompat hack, and are using old 4.3 rhine blobs because those are the last ones that were completely 100% DRM-free.
DRM issues have caused all sorts of problems with rhine/shinano cameras ever since 4.4 - Workarounds for many of these have been found, but not all. But the kernel backcompat hacks would still be needed (potentially multiple hacks for each device supported by the Sony AOSP kernel) and that gets nasty.
So the current plan is to have a unified set of sensor drivers in the kernel, with blobs provided as part of the Sony AOSP project. However I think this is going to be easier said than done - it's not just Sony lawyers, but Qualcomm lawyers. It really sucks that the entirety of Qualcomm's mm-camera subsystem is proprietary and there's no way for an opensource developer to write modules for it, which prevents any of the community side of the Sony AOSP project from working on some things. Otherwise it would probably be not too difficult to replace Sony's noise reduction algorithm (likely with a better one... Sony's NR algorithm got slammed for being too aggressive and killing sharpness over in a dpreview review... All that DRM protection for something some people actually prefer to have gone.)
Edit: And yes, Sony's stock firmwares are amazing. My Z3 holds the record for longest I've ever owned a device without even bothering to root it.
Another thing, my phone is the China Mobile version (L50t) and OmniRom runs perfectly on it, I just have to change the radio and wlan firmware. I can supply the required files and be a tester if you wanted to add official support for this varient.
So as some of you may or may not know tomorrow is Google I/O. And like last year Google will be announcing Android M. It will also most likely release an "M Preview" for the Nexus 6 and 9. Do you guys think it would be possible to port the M Preview from the Nexus 6 to OnePlus One. Also this thread is for everything related to Android M for the OnePlus One
Do you remember situation with Lollipop? I think it will be in the same way
It may be possible, though unlikely. It's just not really worth it. Too many bugs and instability. This time around I'll be looking forward to ports for the nexus 5. As I think it won't get Dev preview
Sent from my Nexus 5 using XDA Free mobile app
Android M Developer Preview will be available today for Nexus phones. How long until someone makes port to Bacon, or how long until we see first ROM:? :fingers-crossed:
/sub
---------- Post added at 03:35 PM ---------- Previous post was at 03:17 PM ----------
http://www.androidpolice.com/2015/0...ages-are-live-now-for-nexus-5-6-9-and-player/
Here they go!
Guess it would be pretty sweet to get a little blend of a ROM with the cherry pickins from the Android M preview.
I think we will get the android m port when Google releases the sources of it.
Liking the new Google photos app, seems pretty slick and great that they detached it from Google+. Seems like they've refined Lollipop a bit and added some decent features. I've seen theres an option for dark theme built in now, maybe not as big a deal to us as we have total theme/customisation control, but the Nexus 6 users are going to appreciate that with their amoled display. Interested to see the app permission/privacy thing in a bit more detail as well. They sorted the volume control (mostly) with an expandable panel although is silent mode still missing?
Android M comes with App Permissions which is slick! Doze mode sounds cool but it doesn't seem to work with Google Play Services
If anyone is interested, the new google camera, search app and play services from the M-preview are already available on apkmirror (haven't tried them, son don't shoot me if they don't work).
Is it me, or is M just a slight update to lollipop?.. Why M and not 5.2?.. Most of the "features" are apps, not the OS.. The OS only got a few changes and is still virtually Lollipop.. I'm happy for the update, but, I had higher hopes for a full "version" jump..
Sent from my A0001 using XDA Premium 4 mobile app
fmc000 said:
If anyone is interested, the new google camera, search app and play services from the M-preview are already available on apkmirror (haven't tried them, son don't shoot me if they don't work).
Click to expand...
Click to collapse
I've tried them - DO NOT INSTALL !
First, you have to manually uninstall existing apps (uninstall updates, disable the built-in apps, reboot device). This allows installation of the new packages.
Second, the device will NOT boot - the new GMS triggers a crash in ProcessManager which brings down the whole system - you will probably have to re-flash the entire shebang.
ddalex said:
I've tried them - DO NOT INSTALL !
First, you have to manually uninstall existing apps (uninstall updates, disable the built-in apps, reboot device). This allows installation of the new packages.
Second, the device will NOT boot - the new GMS triggers a crash in ProcessManager which brings down the whole system - you will probably have to re-flash the entire shebang.
Click to expand...
Click to collapse
Google app is working fine and Google Camera crashes on Panorama. that's all I've found atm.
So just GMS must be avoided. Also, for me apps installed just fine w/o uninstalling/rebooting
You guys should explain if these apks replace system apps or Google apps from play store
nezlobnyj said:
Google Camera crashes on Panorama.
Click to expand...
Click to collapse
That's expected as you need a system lib to use the feature and installing google camera as a user app does not provide that.
It is clearly not possible to port this over. Our device uses heavy caf optimizations in kernel and framework (includes CM and Oxygen). Simply using the frameworks and app core from m will always result in a not booting device. We will have to wait for the source to be published.
OldDroid said:
It is clearly not possible to port this over. Our device uses heavy caf optimizations in kernel and framework (includes CM and Oxygen). Simply using the frameworks and app core from m will always result in a not booting device. We will have to wait for the source to be published.
Click to expand...
Click to collapse
Never say it's not possible! With coding everything is possible.
raafaell said:
Never say it's not possible! With coding everything is possible.
Click to expand...
Click to collapse
it is NOT possible at all!
we need to wait for opensourced code from google to start working.
Calm down a bit my friends. The image had just been released, so it is a matter of time for it to be available for bacon. Be patient, the time will come and enjoy android 5.1.1 first.. Chill
Sent from my A0001 using XDA Free mobile app
i would like an android M version of Cyangonmod or maybe direct port of android M from google with a Cyangodemod recovery
Anybody know if camera2 api access to manual camera functions supported in MM, Nougat updates? Nice phone but no camera2 api support dealbreaker for me and my students. Cheers.
It seems there's no support
What the actual #[email protected]?! I wish I knew this before I bought it. To think that I went for 'an older phone but with a good camera' just to end up with worse camera controls than the cheapest 2013 Lumia...
It's ok man move into a new phone.
SujaySN46 said:
It's ok man move into a new phone.
Click to expand...
Click to collapse
The thing is it IS my new phone. The maximum I could afford. But hey, at least I bailed out from the two-year-abandonware Window Phone/Windows <whatever>.
By the way...
Q: Why can't I change shutter speed / ISO / focus? Where is RAW?
A: Only devices with Camera2 API support have access to these features. Unfortunately, there is nothing we can do about this, it is up to your device manufacturer to add support.
Click to expand...
Click to collapse
More details
http://www.riseupgames.com/proshot/camera2api
https://forum.xda-developers.com/moto-x-style/general/howto-enable-camera2-manual-camera-t3238748/