Hey guys! For the first time I am having a device Nexus and I am very happy. But I would like to test new ROMs customized. in my devices previous (non-Nexus) whenever opted for any ROM AOSP or CM based, the camera had lower quality compared to the stock, because the manufacturers not release their drivers owners for parallel development. Thus, always have CM drivers generic in the camera and other parts of the device.
I wonde then, if we Nexus happens otherwise. Google provides these codes for developers? I will lose quality in photographs case use another ROM AOSP based?
Grateful for the replies!
There isn't a custom ROM that will degrade your photo quality on the 6p.
Sent from my Nexus 6P using XDA-Developers mobile app
Indeed: https://developers.google.com/android/nexus/drivers
Additionally, the blobs/drivers can be easily extracted from a rooted device/the factory images. So all in all, no, you do not have to worry about any issues with the camera or any other hardware with custom ROMs (aside from Bluetooth with CM based ROMs).
Related
Hey guys,
I`am thinking of ordering a Oppo Find 5 32GB, i have a Nexus 4 atm and i`am looking for something new.
Is it a definate upgrade? The specs on paper seem great but how does the phone do in real life.
Would appreciate some user feedback
Same here. I am thinking of doing the same. I am particularly hoping for a stable PA/CM10.1 ROM soon, and more kernel development if possible.
gee2012 said:
Hey guys,
I`am thinking of ordering a Oppo Find 5 32GB, i have a Nexus 4 atm and i`am looking for something new.
Is it a definate upgrade? The specs on paper seem great but how does the phone do in real life.
Would appreciate some user feedback
Click to expand...
Click to collapse
it's not a goodupgrade..
same CPU, RAM, GPU, same problems with: OTG, no microSD expansion, no removable battery
you get a better/larger display, slightly better(in specs) or worse(in terms of software capabilities so far) camera....
and worse battery life / smoothless/performance in ROMs.....and more expensive
no matter how good the CM10.1 port for the find 5 is, nexus 4 ports will be snappier as they have the backing of google
If ports are based on aosp how can they be snappier .....only a bit of kernel tweaks and some camera enhancements will make this phone awesome
Sent from my Find 5 using Tapatalk 2
munchy_cool said:
If ports are based on aosp how can they be snappier .....only a bit of kernel tweaks and some camera enhancements will make this phone awesome
Sent from my Find 5 using Tapatalk 2
Click to expand...
Click to collapse
i'm talking specifically about the device/kernel tree....
for nexus 4, it comes from google (who has access to all the proprietary documents, binaries)
for oppo find 5, it comes from people like XpLoDWilD, Entropy512, ... . They may have to interpret that info based on how the Oppo Stock Rom works, previous experience, hacks needed to make stuff work...
this portion will contain bugs / inefficiencies in the codebase
and when you move from different android versions, the proprietary binaries differ and may not be compatible. For Nexus devices, google gives you those updated binaries... for other devices (like Oppo), you may have to beg Oppo to get the latest binaries, steal it from a similar device that has the update, or hack your way (which creates inefficiencies / bugs)
see: https://developers.google.com/android/nexus/drivers
this is why you have: stable cm10.1 ports on some devices, but still buggy/slow compared to the nexus line
paperWastage said:
i'm talking specifically about the device/kernel tree....
for nexus 4, it comes from google (who has access to all the proprietary documents, binaries)
for oppo find 5, it comes from people like XpLoDWilD, Entropy512, ... . They may have to interpret that info based on how the Oppo Stock Rom works, previous experience, hacks needed to make stuff work...
this portion will contain bugs / inefficiencies in the codebase
and when you move from different android versions, the proprietary binaries differ and may not be compatible. For Nexus devices, google gives you those updated binaries... for other devices (like Oppo), you may have to beg Oppo to get the latest binaries, steal it from a similar device that has the update, or hack your way (which creates inefficiencies / bugs)
see: https://developers.google.com/android/nexus/drivers
this is why you have: stable cm10.1 ports on some devices, but still buggy/slow compared to the nexus line
Click to expand...
Click to collapse
I agree with you but that's the case with all non-Google devices.
if you want latest android version you gotta stick with Google devices.
munchy_cool said:
I agree with you but that's the case with all non-Google devices.
if you want latest android version you gotta stick with Google devices.
Click to expand...
Click to collapse
i'm talking about the device tree on the current android version.... device tree port by CM developers vs device tree from google
since hardware is mostly the same from nexus 4, but you're moving software-wise from a "optimized" port (with device tree from google) to a Cm10.1 port (with device tree that is still buggy and not optimized by google)..
don't see the reason to switch from nexus 4.
Find 5: aosp -> cm10.1 + device tree from CM developers = ROM
Nexus 4: aosp -> cm10.1 + google's device tree = better ROM
replace cm10.1 with anything else (AOKP, PAC, PA)...
paperWastage said:
i'm talking about the device tree on the current android version.... device tree port by CM developers vs device tree from google
since hardware is mostly the same from nexus 4, but you're moving software-wise from a "optimized" port (with device tree from google) to a Cm10.1 port (with device tree that is still buggy and not optimized by google)..
don't see the reason to switch from nexus 4.
Find 5: aosp -> cm10.1 + device tree from CM developers = ROM
Nexus 4: aosp -> cm10.1 + google's device tree = better ROM
Click to expand...
Click to collapse
the reason to switch from n4 would be better & bigger screen, but in that case I would recommend the DNA
I'm making the switch. Mainly for the screen and I didn't feel like paying $650 for the dev HTC One. It'll be interesting to see how Oppo's firmware is as well.
I switched from a Nexus 4 that I've had since November. I was just getting tired of the device and was looking for something with a slightly larger/higher resolution display, but I wasn't looking for a full on phablet (Note II). I have been incredibly satisfied with the unit's build quality and am only slightly thrown off by it's less than stellar stock rom. No worries though, as PA has been rock solid for me. :good::good: Two thumbs up on making the switch!
I'm also thinking of making the switch and also coming from a nexus 4. What I want to see get more development though is on the android ROMs as there are none. On the original android development I do see cm 10.1,pa,ect.. Which is pretty much the stuff I'm running on the nexus 4 already. I wanna see oppo find 5 u.i based roms.if I'm gonna make the switch and use the same base ROMs as the nexus 4 I might as well stick with the nexus 4 instead.
marcviado said:
I'm also thinking of making the switch and also coming from a nexus 4. What I want to see get more development though is on the android ROMs as there are none. On the original android development I do see cm 10.1,pa,ect.. Which is pretty much the stuff I'm running on the nexus 4 already. I wanna see oppo find 5 u.i based roms.if I'm gonna make the switch and use the same base ROMs as the nexus 4 I might as well stick with the nexus 4 instead.
Click to expand...
Click to collapse
I think it is pretty unlikely that you'll see a lot of custom ROM's for Find 5, considering much lower number of users compared to other phones.
I think i`am gonna stick with the N4 for now and mainly for its optimized firmware. The firmware of the Oppo is clearly not as good (or finished) as the N4`s. Pitty, would have liked to try it out. Aah well, maybe at a later point or its successor. Thanks for the reply`s guys :good:
marcviado said:
I'm also thinking of making the switch and also coming from a nexus 4. What I want to see get more development though is on the android ROMs as there are none. On the original android development I do see cm 10.1,pa,ect.. Which is pretty much the stuff I'm running on the nexus 4 already. I wanna see oppo find 5 u.i based roms.if I'm gonna make the switch and use the same base ROMs as the nexus 4 I might as well stick with the nexus 4 instead.
Click to expand...
Click to collapse
MIUI is the closest "alternative" to Find 5's stock UI rom... find one (probably won't be on XDA) that works on a phone you would want, then buy that phone
next alternative would be the iPhone
N4 owner as well. While I have a hard time putting down my Find 5, if I'm to be totally honest, the N4 is hard to beat. Mostly software I guess, its hard to find a flaw. The Find 5 is still being optimized and tweaked on a regular basis... which is great but not needed in the Nexus. Still though, the Find 5 is one nice device with a lot of potential!
sent from my <Nexus 7>
I have ordered a nexus 4 and will most likely root and rom it when I get it.
I have noticed on my two old phones (current g2x and an optimus t) that I installed roms on, specifically cyanogenmod, it always made the camera quality worse.
Does installing any of the custom roms on these phones make the camera worse, the same, or better?
no, installing any of the custom roms does not make the camera worse or better. However, u can use third party apps to improve the picture quality.
skarookidoo said:
I have ordered a nexus 4 and will most likely root and rom it when I get it.
I have noticed on my two old phones (current g2x and an optimus t) that I installed roms on, specifically cyanogenmod, it always made the camera quality worse.
Does installing any of the custom roms on these phones make the camera worse, the same, or better?
Click to expand...
Click to collapse
No, Installing a custom ROM won't improve or make your camera worse.
How ever if you use a beta version of any third party camera app, it may not be able to take full usage of your camera, its just that stock camera app is usually optimized for your phone.
No, it won't. The reason why it makes those phones take worse pictures is because the manufacturer has their own closed source libraries for processing images and autofocus, so custom ROMs are forced to use the (usually worse) AOSP camera libraries. The Nexus 4 is based off of AOSP, so stock already has the AOSP camera libraries.
I compared shots taken with the stock LG camera vs the stock jelly bean camera, and the results are dramatic. The LG camera wins hands down, so I'm just curious if AOSP roms would work with the LG camera.
Also, are we going to see custom kernels for this device?
Don't worry, you'll still be able to use your camera. However the stock LG camera app will probably be replaced with focal or something similar.
Geekybiker said:
Don't worry, you'll still be able to use your camera. However the stock LG camera app will probably be replaced with focal or something similar.
Click to expand...
Click to collapse
What he's asking is if we can still use lgs camera app... Because I agree aosp sucks...
Of the stock camera isn't reliant on the framework then yes.. Otherwise no
Sent from my LG-D801 using Tapatalk 2
whittikins said:
I compared shots taken with the stock LG camera vs the stock jelly bean camera, and the results are dramatic. The LG camera wins hands down, so I'm just curious if AOSP roms would work with the LG camera.
Also, are we going to see custom kernels for this device?
Click to expand...
Click to collapse
I doubt we will see a camera with all the options of the LG G2 stock app, but there will be options. Focal is one. Generally manufacturers apps don't make it into AOSP or CM roms, I think because they require other framework or files that aren't included in in the custom roms.
Look at the size of a CM rom, and then at an original rom, and you'll probably see a difference of 500MB+ (i.e. lots of proprietary files not there in AOSP or CM)
As for Kernels, I would think there will be some on the way. There are already a couple, so I'm sure more work will be done to increase the offering.
chronicfathead said:
I doubt we will see a camera with all the options of the LG G2 stock app, but there will be options. Focal is one. Generally manufacturers apps don't make it into AOSP or CM roms, I think because they require other framework or files that aren't included in in the custom roms.
Look at the size of a CM rom, and then at an original rom, and you'll probably see a difference of 500MB+ (i.e. lots of proprietary files not there in AOSP or CM)
As for Kernels, I would think there will be some on the way. There are already a couple, so I'm sure more work will be done to increase the offering.
Click to expand...
Click to collapse
That makes sense, but it kind of sucks to lose the improvements that LG made. The options are one thing, but the difference in image quality is huge comparing it to AOSP camera .
Don't give up your hopes too soon, as you may already know there's alot of third party camera ported to work with all device including those that uses AOSP roms in Android Apps section.. And they usually comes with their proprietary libs/so to make their functions work..
Although none of them are 100% perfect as they're not intended to be used on other device in the first place, LG cam should work better on LG devices.. Time will tell..
costum kernel will be available soon after the devs gets their hands dirty on the SD800 SoC..
i'm interested about porting the moto x always listening feature to the G2, as the latter has the chip to do so..
I'd like to ask what would be the state of each of the next features on SGS5 (any of its models) when moving to an AOSP based rom (like CM, Omni, PA, ...) :
1. MHL/HDMI
2. Screen recording.
3. Calls recording
4. hovering with the fingers.
5. touching with gloves
6. sensors
7. IR
8. Any TW app (camera, keyboard, etc...)
By state, I mean, how well would it function, if at all.
Also, I'd like to ask (as I don't really own the device) : what would you miss the most in case you moved from stock-Samsung rom to AOSP-based rom?
Any feature I didn't mention ?
AndroidDeveloperLB said:
I'd like to ask what would be the state of each of the next features on SGS5 (any of its models) when moving to an AOSP based rom (like CM, Omni, PA, ...) :
1. MHL/HDMI
2. Screen recording.
3. Calls recording
4. hovering with the fingers.
5. touching with gloves
6. sensors
7. IR
8. Any TW app (camera, keyboard, etc...)
By state, I mean, how well would it function, if at all.
Also, I'd like to ask (as I don't really own the device) : what would you miss the most in case you moved from stock-Samsung rom to AOSP-based rom?
Any feature I didn't mention ?
Click to expand...
Click to collapse
Sadly, most of these functions have not been carried over to AOSP based roms. Most of these functions seem to arrive on Cyanogenmod first.
I do know that Cyanogenmod is currently supporting IR but it is not complete enough to run 100% daily driver. They're having GPU video/image rendering issues in some apps, camera isn't properly configured. It's all stuff being worked on but I am sure all of these functions are on Cyanogenmod's to-do to support all of the hardware features of most devices.
Glove sensitivity functions perfectly in cyanogenmod, most sensors work perfectly as well. The eye-tracking features are likely not ever going to be a part of AOSP roms. Hopefully Hover gets picked up by more manufactures and becomes a part of AOSP and the SDK for apps, it has great possibilities for better intuitive interfaces.
stevey500 said:
Sadly, most of these functions have not been carried over to AOSP based roms. Most of these functions seem to arrive on Cyanogenmod first.
I do know that Cyanogenmod is currently supporting IR but it is not complete enough to run 100% daily driver. They're having GPU video/image rendering issues in some apps, camera isn't properly configured. It's all stuff being worked on but I am sure all of these functions are on Cyanogenmod's to-do to support all of the hardware features of most devices.
Glove sensitivity functions perfectly in cyanogenmod, most sensors work perfectly as well. The eye-tracking features are likely not ever going to be a part of AOSP roms. Hopefully Hover gets picked up by more manufactures and becomes a part of AOSP and the SDK for apps, it has great possibilities for better intuitive interfaces.
Click to expand...
Click to collapse
I see. Not even screen recording?
Is this the situation with all of the variants of the device?
I wonder how well other devices (even of other manufacturers) are supported by CM (and other AOSP based roms).
I assume Nexus is one of the best ones that they support.
AndroidDeveloperLB said:
I see. Not even screen recording?
Is this the situation with all of the variants of the device?
I wonder how well other devices (even of other manufacturers) are supported by CM (and other AOSP based roms).
I assume Nexus is one of the best ones that they support.
Click to expand...
Click to collapse
Screen recording is in the works on Cyanogenmod and in the process of being built for compatibility on all devices. It's a lot of work to build software in compatibility will all hardware. Nexus devices to get the extra bit of love because those devices are arms wide open to the developer community. Samsung, LG, and HTC are getting hit hard by locked bootloaders on the two giant carriers verizon and AT&T... if those bootloaders were not locked, I am sure that the flagship devices from those companies would be getting a LOT more developer support, especially from Cyanogenmod team.
Such as, the Galaxy S3 (and a moment for the S4) were the last devices that were getting insta-written AOSP code and compatibility support for AOSP based roms while the majority of them were bootloader unlocked/unlockable. The Galaxy S5 is being developed for, just a bit slowly, sadly. AT&T and Verizon models are totally bootloader locked with no current workaround.
The nexus devices may seem to be better supported by the developers but the Nexus devices aren't as complex and have a more basic hardware layout lacking alot of the extras and premium features of the samsung, htc, and LG family- those devices require more attention.
stevey500 said:
Screen recording is in the works on Cyanogenmod and in the process of being built for compatibility on all devices. It's a lot of work to build software in compatibility will all hardware. Nexus devices to get the extra bit of love because those devices are arms wide open to the developer community. Samsung, LG, and HTC are getting hit hard by locked bootloaders on the two giant carriers verizon and AT&T... if those bootloaders were not locked, I am sure that the flagship devices from those companies would be getting a LOT more developer support, especially from Cyanogenmod team.
Such as, the Galaxy S3 (and a moment for the S4) were the last devices that were getting insta-written AOSP code and compatibility support for AOSP based roms while the majority of them were bootloader unlocked/unlockable. The Galaxy S5 is being developed for, just a bit slowly, sadly. AT&T and Verizon models are totally bootloader locked with no current workaround.
The nexus devices may seem to be better supported by the developers but the Nexus devices aren't as complex and have a more basic hardware layout lacking alot of the extras and premium features of the samsung, htc, and LG family- those devices require more attention.
Click to expand...
Click to collapse
I see. So it takes a lot of work.
Say, you mentioned the SGS3. I have this device. Do you think it will ever support screen recording on CM ? Currently it's very very slow. I've tried the special customized rom that's based on Note 2, and this feature worked fine there. I've left this rom because of some reasons I don't remember about (maybe stability).
All those features are available in samsung based custom roms. Why does it have to be AOSP based?
Sent from my SM-G900F using Tapatalk
Pardon me if it's a noob question
Just wanted to know that whether camera capabilities like the potrait mode and other tweaks will be affected when running a custom rom?
If so, what differences could one expect?
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
Not completely sure. But from what I understand so far. If it is a stock based, custom ROM, then stock camera app is there to function same as always.
But for non stock ROMs (Lineage, Resurrection Remix, AOSP), it seems camera functionally will be significantly reduced (OnePlus aren't delivering camera blobs by the sounds of things). And because of that, not sure what community is able to do in that regard