It seems we can enable Camera2 API in our Z2_plus - Lenovo ZUK Z2 (Plus) Guides, News, & Discussion

The [email protected] replied me that we can enable HAL3 by "modify Qualcomm source code", but I don't know what means it is. Does any one know that?
Here's the original e-mail text:
You can get get Qualcomm source code in theory, but I’m not sure how it works.
Here the way to enable HAL3,
Modify following source code:
Hardware/qcom/camera/QCamera2/QCamera2Factory.cpp
QCamera2Factory:: QCamera2Factory()
Modify the HAL switcher logic as you want.

Send this to a dev , maybe we will get google camera to work
Wysłane z mojego Z2 Plus przy użyciu Tapatalka

great info! would love to have this working........

I hope somebody gets it working!

Ushiocc said:
The [email protected] replied me that we can enable HAL3 by "modify Qualcomm source code", but I don't know what means it is. Does any one know that?
Here's the original e-mail text:
You can get get Qualcomm source code in theory, but I’m not sure how it works.
Here the way to enable HAL3,
Modify following source code:
Hardware/qcom/camera/QCamera2/QCamera2Factory.cpp
QCamera2Factory:: QCamera2Factory()
Modify the HAL switcher logic as you want.
Click to expand...
Click to collapse
Maybe we have to do some modification here

From what I can gather, they're basically telling you to implement HAL3 features yourself... not very useful for developers, unless I'm really mistaken.

Ushiocc said:
The [email protected] replied me that we can enable HAL3 by "modify Qualcomm source code", but I don't know what means it is. Does any one know that?
Here's the original e-mail text:
You can get get Qualcomm source code in theory, but I’m not sure how it works.
Here the way to enable HAL3,
Modify following source code:
Hardware/qcom/camera/QCamera2/QCamera2Factory.cpp
QCamera2Factory:: QCamera2Factory()
Modify the HAL switcher logic as you want.
Click to expand...
Click to collapse
This info is most probably wrong i guess...
Devs @ zuk were working on camera api2 they had it done almost.....but the problem was it was highly unstable.....they also replied that it would take some more time to make it stable

Here you have some fresh news. Hope we will get it working.
HI:
*
Yes, we can switch to API2 by modifying some of codes, but here is the problem,
We can’t guarantee the stability of camera API2 right now.
We have implemented 30+ features on API1 to provide competitive camera experience,
and we can make sure that camera can perfectly run for hundreds of hours in stability test and pressure test.
But for Camera API2, the lunch time for ZUK Z2 is much earlier than Redmi note 4.
We tried to deploy API2 but failed since the platform baseline is not stabile enough to deliver to user,
It have many stability issues and even CTS issue.
*
We are trying to bring Camera API2 next, but the timetable is uncertain for now.
You can get get Qualcomm source code in theory, but I’m not sure how it works.
Wysłane z mojego Z2 Plus przy użyciu Tapatalka

Wooby said:
Here you have some fresh news. Hope we will get it working.
HI:
*
Yes, we can switch to API2 by modifying some of codes, but here is the problem,
We can’t guarantee the stability of camera API2 right now.
We have implemented 30+ features on API1 to provide competitive camera experience,
and we can make sure that camera can perfectly run for hundreds of hours in stability test and pressure test.
But for Camera API2, the lunch time for ZUK Z2 is much earlier than Redmi note 4.
We tried to deploy API2 but failed since the platform baseline is not stabile enough to deliver to user,
It have many stability issues and even CTS issue.
*
We are trying to bring Camera API2 next, but the timetable is uncertain for now.
You can get get Qualcomm source code in theory, but I’m not sure how it works.
Wysłane z mojego Z2 Plus przy użyciu Tapatalka
Click to expand...
Click to collapse
What do they mean by lunch time?
Like mid-time in phone's whole development time or did they simply misspell Launch?

wow! is happy to see you guys start doing mission impossible . is not easy but good to hear some news.

Guys, it would be very good. Let's keep up this post
Sent from my Z2 Plus using Tapatalk

have you guys signed the petition?

Alright, but one confusion friends... If it such a complex thing to do then how I used Google camera in Stock ROM of Z2 plus. I'm facing problem just after flashing custom ROM AEX 4.6.

Related

Multitasking - best case scenario

Hi guys I was so confused on choosing between G4 and S6 and actually I was about to pick G4 for it overall great performance. Then few people told me that custom roms can give me even 7-8 hours SOT on s6 and i trust them because I had completely debloated note 2 that could run 5-6h sot every day. Now I'm using Z3 which I love despite the terrible (in comparison to Samsung and LG) camera. I wanted to change but I'm looking for good performance in all sectors - battery, camera and multitasking.
Now here's the deal. If anyone can run similar multitasking situation like the one on the video (13 apps switching simultaneously on my Z3, could do more but it's not the thing, at least 10 is what I'm really looking for, if more is possible that would be great too! ) and could post a video + information of changes (rom, mod etc.), I would be so much grateful.
Don't ask why I want, don't tell me it's useless, in my opinion it's the best android feature that works excellent, as you see on Z3 makes opening all apps extremely smooth without need to reopen anything (even throughout the whole day).
PS. Actually just make this just like battery thread, showing how good it can multitask. I think it might help other people who hate this device for poor multitasking.
Wysłane z mojego D6603 przy użyciu Tapatalka
We all already know how it multitasks.
Sent from my SM-G925F
@Elisha
Yeah maybe, but I couldn't find any good custom rom multitasking performance on YouTube, only stock (which performs very bad). Luckily I found nice video.
This guy runs xtrestolite rom. I'm a heavy user so that's why it was so important to me. I thought of switching to nexus device, but I use camera from time to time as well.
Wysłane z mojego D6603 przy użyciu Tapatalka
I am using this on my s6 edge. And my best multitasking scenario was 16 app at the same time(3 games, browser, carbon for twitter, youtube, spotify, etc)
I think there is room for improvement for the s6. but if you want maximum multitasking. wait for the moto x style. according reviews it has an excellent camera and is the closest as it get to aosp.
Turn all of your apps into bubbles.
Jhayzt what do you want how do you turn the to bubbles please??
Jhayzt said:
Turn all of your apps into bubbles.
Click to expand...
Click to collapse
Only works for apps that can run in pop up view
Sent from my SM-N920C using Tapatalk
ChongoDroid said:
Only works for apps that can run in pop up view
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
But at least you're given an option to turn some apps into bubbles right?
I am running the arter97 note 5 custom rom version 4. With his kernal(same version). I'm on 5.1.1 base. Multitasking is the best I've seen on this device. I have approximately 10-12 apps open as we speak and am able to switch between them with no reopening of any kind. It is the "back to not3" rom in this forum. Best rom I've ever used on a smartphone and the best for multitasking I've used on the s6

[ROM] CyanogenMod 12.1 for Meizu MX4 (20151015 testing update)

UPDATE: 20151015 testing package is out! Check it out for details.
Hello, I've updated the CM12.1 testing package and translated the release notes at my blog. Also took the time to support Disqus for the English blog posts... the release can be found here.
Also that I will stop regularly updating the port at October 20th, having to allocate much of my time to academic work. Security updates and minor bugfixes (as in not requiring massive porting) will continue as usual, however. Feel free to make ssuggestions!
(Note: I don't know how to patchrom so I can't do the Flyme camera app porting, or anything but the easiest features requiring porting of closed-source components, sorry about that but I'm primarily a Web/Android developer and as such don't have much time to learn about smali and the likes.)
don't know what to say ,.. but thanks for you awesome work is it's source on github? maybe we find someone who can do this
Anyone have FC on Facebook app when it want to play a video? I haven't had this problem in previous versions of rom
Wysłane z mojego MX4 przy użyciu Tapatalka
Me too
Inviato dal mio MX4 utilizzando Tapatalk
---------- Post added at 10:06 PM ---------- Previous post was at 09:50 PM ----------
DeadAngel43 said:
Anyone have FC on Facebook app when it want to play a video? I haven't had this problem in previous versions of rom
Wysłane z mojego MX4 przy użyciu Tapatalka
Click to expand...
Click to collapse
Disable the autoplay of videos and the app works well!! Tested [emoji14]
Inviato dal mio MX4 utilizzando Tapatalk
issue
I have a weird issue : phone locks automatically when i make a call, the only vay to hang up is to turn off the phone !
La Blatte said:
I have a weird issue : phone locks automatically when i make a call, the only vay to hang up is to turn off the phone !
Click to expand...
Click to collapse
Distance sensor have some problems, you can set power to hang up.
来自我的 MX4 上的 Tapatalk
https://github.com/xen0n/android_device_meizu_arale/issues/7 Proximity sensor is fixed, the solution is beyond my wildest imagination... Having looked at pile after pile of smali code and kernel sources to no avail a simple echo gets it.
Next release scheduled in ~3 days, stay tuned.
Xenon, can you fix notificarion volume level? All notifications are too loud. I try to fix it by myself, but i didnt find config in /system/etc
Thanks xxxxen0n! i'm waiting for the next release (for proximity sensor fix) then i'm going to install this rom
finally an unlocked bootloader and CM12.1 for meizu mx4. i tought that wasn't possible, but here it is!
Thanks again for your work!
I've tried to edit manually ps_data... XD acces denied even with kali linux adb root and recovery wtf??!!! XDDDD
Sent from my MX4 using XDA Premium HD app
Working great for me, except mobile data. Battery life is awesome, smooth animations, all sensors are ok, only data connection and would be perfect. Thanks for this rom
I'm not sure is it concern to this ROM, but I have strange issue.
Paired Sony SmartBand Talk SWR30 with Meizu and battery of band drying within one day. When switch bluetooth on the phone off, then drying stops. Previously I have used the same band with Sony Xperia Z3 and battery lasts 4-5 days.
I can't imagine what wrong with Meizu and CM12. Factory reset of the band did not help. Bluetooth stack incompatibility? Wakelock detector shows big activity of com.android.bluetooth process.
artlov said:
I'm not sure is it concern to this ROM, but I have strange issue.
Paired Sony SmartBand Talk SWR30 with Meizu and battery of band drying within one day. When switch bluetooth on the phone off, then drying stops. Previously I have used the same band with Sony Xperia Z3 and battery lasts 4-5 days.
I can't imagine what wrong with Meizu and CM12. Factory reset of the band did not help. Bluetooth stack incompatibility? Wakelock detector shows big activity of com.android.bluetooth process.
Click to expand...
Click to collapse
I have the same device and test it on CM12.1 No problem! 5-10 percent by day in paired mode. Do you use aditional widgets for SWR30 like Clocki?
Do you use aditional widgets for SWR30 like Clocki?
Click to expand...
Click to collapse
No, currently only default settings - default digital clock (with date) and activity monitor are in the use.
After full reinstall yesterday and freezing Lifelog, today battery is much better - from 7am to the 5pm battery have 80% juice remaining, but it still worse that was with Z3.
Try to wipe dalvik/art cache via philz
Sent from my MX4 using XDA Premium HD app
Hey everybody watching this, fresh build is out for testing! Please see the announcement for details.
thanks you
@xxxenOn could wake the screen gestures, double tab and gesture upward and could import slow motion mode and manual camera?
Enviado desde mi MX4 mediante Tapatalk
works great, but notifications are still much too loud.
For camera you could try these ports
http://forum.xda-developers.com/galaxy-note-3/themes-apps/flyme-os-camera-ported-t3165380
http://forum.xda-developers.com/android/apps-games/port-meizu-mx5-apps-device-t3155760

AOSP Camera Bounty, Z3 and Z3 Compact

Hi XDA community,
I am currently running the latest AOSP on our phone, and it is very nice. The only part really missing now is the camera. I know anyone who is familiar with AOSP on our device will know the story.
What I am wondering now is if people would be interested in raising a bounty to get an implementation put together?
I for one would be happy to put up some cash if it meant that we got a fully functioning Android for another year. The hardware in the phone is plenty enough for everything I use it for.
Developers would any of you be interested in claiming a bounty by fixing up our camera drivers to work with the 3.10 AOSP kernel?
Flashable Zips of AOSP Nougat Z3c:https://www.androidfilehost.com/user/?w=settings-dev-files&flid=73595
Promised Donations:
@mcgi5sr2 $50
@smorgar $10
@istux $15
@okij $15
@Rumbi $10
 @danilobertelli $15
 @nailyk $20
 @Tilarou $20
 @Me Gusta $10
Total: $165
I will need to work out exactly what we are going to specify as a working camera. Please comment with thoughts.
requests so far:
No fish eye
picture and video recording
Auto Focus
This is a neat idea. But I don't even know if it's possible to achieve this.
Im in! 10$ from me!
---------- Post added at 08:38 AM ---------- Previous post was at 08:18 AM ----------
mcgi5sr2 said:
Hi XDA community,
I am currently running the latest AOSP on our phone, and it is very nice.
Click to expand...
Click to collapse
Is it stable enough to use as a daily driver? Other bugs/kinks than the broken camera? Im really tempted to test it but i cant download it through the mirror they use. Get some popup regarding adblock that i cant get rid of, even tho i use IE with no adblock at all...
Put me up for $15 :good:
I'll give my money ONLY IF the camera will be fisheye-bug free. (no flame please, this is just my offer)
I'm in with 15 $ too.
And I share the opinion of @istux that the camera should be fisheye-bug free.
@mcgi5sr2: Could you cross-post this in the Z3 forums too, since they are in the same situation and also might participate in the bounty? Cheers.
I would be in with 10 Bucks, too. Afaik the camera is already working with picture and video, only this fisheye bug makes it more or less useless. So with the fisheye bug fixed, everything should be fine?!
Rumbi said:
I would be in with 10 Bucks, too. Afaik the camera is already working with picture and video, only this fisheye bug makes it more or less useless. So with the fisheye bug fixed, everything should be fine?!
Click to expand...
Click to collapse
On the 1.3.3 kernel the cameras are split, and video isn't working. Work is still ongoing on it, but I'm hoping a financial incentive will help
I'm in with 15 $ too if all camera issues can be fixed.
danilobertelli said:
I'm in with 15 $ too if all camera issues can be fixed.
Click to expand...
Click to collapse
cool camera is improving a lot, next set of blobs should have it all sorted including auto focus. Would be cool if we could find a good dev and get him interested in sorting out the fish eye issue
Glad to see your thread as I wanna do the same.
Do you know a dev thread had been opened for this problem?
How do you plan to split the bounty between the devs who will fix the issue?
I buy my device for the camera. Without camera it is useless for me. Depending of the month on the claim I can be in between 20 and 50$.
The fisheye bug isn't there in the new camera. It's there only in the older blobs.
oSandmaNo said:
The fisheye bug isn't there in the new camera. It's there only in the older blobs.
Click to expand...
Click to collapse
I assume the same progress has been done for both Z3/C, right?
If so, what are the downsides of the new 7.1 builds?
doriandiaconu said:
I assume the same progress has been done for both Z3/C, right?
If so, what are the downsides of the new 7.1 builds?
Click to expand...
Click to collapse
I don't see anyone compiling 7.0/1 for z3/C except for Nailyk, but AFAIK he does cm14 and not AOSP. But whatever is fixed in z1 and z2 will work for z3 as well. As long as someone builds one for us
oSandmaNo said:
I don't see anyone compiling 7.0/1 for z3/C except for Nailyk, but AFAIK he does cm14 and not AOSP. But whatever is fixed in z1 and z2 will work for z3 as well. As long as someone builds one for us
Click to expand...
Click to collapse
They are not on xda but fxpblog roms should be up-to-date with sonyxperiadev work.
And you are right, I only build CyanogenMod.
If I get it right you said fisheye is not present anymore. Can you link me to the rom zip and sources as I can give a try please? Or maybe you are talking about incoming blobs?
nailyk said:
They are not on xda but fxpblog roms should be up-to-date with sonyxperiadev work.
And you are right, I only build CyanogenMod.
If I get it right you said fisheye is not present anymore. Can you link me to the rom zip and sources as I can give a try please? Or maybe you are talking about incoming blobs?
Click to expand...
Click to collapse
I'm not a developer but from what I've been reading (I'm a lurker ) for the past year is that the fish eye bug is introduced due to using the jellybean blobs from Z1 and then using a wrapper around it. The new camera does not use that, so there is no fish eye bug. Please correct me if I'm wrong, I haven't flashed any AOSP ROM on my device, but I read a lot. I've also seen the pictures taken by the z2 users and I can't see the fisheye in them. The incoming blobs should fix the focus problems, but the fish eye was never a problem ever since they got it working.
oSandmaNo said:
I'm not a developer but from what I've been reading (I'm a lurker ) for the past year is that the fish eye bug is introduced due to using the jellybean blobs from Z1 and then using a wrapper around it. The new camera does not use that, so there is no fish eye bug. Please correct me if I'm wrong, I haven't flashed any AOSP ROM on my device, but I read a lot. I've also seen the pictures taken by the z2 users and I can't see the fisheye in them. The incoming blobs should fix the focus problems, but the fish eye was never a problem ever since they got it working.
Click to expand...
Click to collapse
Sorry but the fisheye problem doesn't came from blobs only. We discuss a little about it here (and next posts). Our z3(c) had a wide angle camera in a small component. The only way to get this is with a specific lens on the imx220. (imx220c iirc). So honami blobs on z3 get the camera working (almost) perfectly except the proprietary implementation of sony lens correction is absent, that is why we have this fisheye bug. And afaik only z3(c) had this imx220 version.
So if new blobs doesn't provide this proprietary correction or release it still under drm protection, fisheyebug will still be present.
The fisheye is something that needs to be corrected with aftermarket picture processing. As of V5 blobs, the camera on shinano is working, but autofocus is not properly calibrated. That will be done in the future V6 blobs.
If someone wants a 7.1 Build for aries with a working (read non-crashing cam, but broken AutoFocus), I upload some of my Carbon Builds from time to time here:
https://dl.myself5.de/aries/CarbonROM/
Btw, the fix for the camera on 1.3.3 that made full pictures possible was done by @erikas, maybe you want to consider him in your bounty decision. Everything else will be done using vendor blobs or picture post processing.
Sent from my D6603 using Tapatalk
the new camera fix noises in night pictures ?
images night z1 and z2 is is incredibly good this can also work on z3 / C / tablet ? I know that has many problems focus and others but it's a big step to aosp in xperias
I would gladly put 20€ if the camera support the following:
Z3 dual (D6633/D6683), noise reduction, all feature of original sony camera app including video with audio and 4K (except proprietary function like Sony noise reduction and other DRM related fonctions).
tiliarou said:
I would gladly put 20€ if the camera support the following:
Z3 dual (D6633/D6683), noise reduction, all feature of original sony camera app including video with audio and 4K (except proprietary function like Sony noise reduction and other DRM related fonctions).
Click to expand...
Click to collapse
That is never gonna happen

New Xperia Project

Hey Folks,
I just ordered a XZ Premium yesterday, which will come till this Weekend. First Thing to do is updating and unlocking the Bootloader, before checking out how actual SONY Stock Firmware looks like nowadys (My last SONY was a Z3). After that comes the next important Step. Contributing to the XZ Premium Forums.
I'm not sure what will be better or makes more Sense. The Options are:
-A new AOSP based Project for Xperia Devices
-A new Stock ROM Project (Snappatch Xperia Stock Exclusive)
-A new Patch for a own AOSP based Project (Combing the first two Options somehow)
If You want to know what the Patch is, just check out My Signature where You will find the Link to My actual Thread. I'm just really happy to get a XZ Premium (Since i don't like the XZ2 and prefer the XZP Design over the XZ1 Design), and can't wait to work with it and share the Results with You! Let Me know what You think which is mostly needed or what would make the biggest difference (Upgrade) to Your Device...
BR
Miustone said:
Hey Folks,
I just ordered a XZ Premium yesterday, which will come till this Weekend. First Thing to do is updating and unlocking the Bootloader, before checking out how actual SONY Stock Firmware looks like nowadys (My last SONY was a Z3). After that comes the next important Step. Contributing to the XZ Premium Forums.
I'm not sure what will be better or makes more Sense. The Options are:
-A new AOSP based Project for Xperia Devices
-A new Stock ROM Project (Snappatch Xperia Stock Exclusive)
-A new Patch for a own AOSP based Project (Combing the first two Options somehow)
If You want to know what the Patch is, just check out My Signature where You will find the Link to My actual Thread. I'm just really happy to get a XZ Premium (Since i don't like the XZ2 and prefer the XZP Design over the XZ1 Design), and can't wait to work with it and share the Results with You! Let Me know what You think which is mostly needed or what would make the biggest difference (Upgrade) to Your Device...
BR
Click to expand...
Click to collapse
I gotta say im very happy to hear that!
well most of the community here just want google camera working properly without losing drm keys and to have a native 4k screen option or 1080p/120hz hdr and all that stuff
so as i understood unlocking bootloader loses drm keys so flashing aosp roms with google camera doesnt make the camera better due to loss of drm (as noise reduction is lost along with the drm)
if its just possible a way to keep drm while having aosp that way we would have a God level of a camera, coming with 4k/1080p-120hz options that would do it! this phone would be the best for long time
but i guess its impossible to combine those features together which hurts me a lot knowing what potential this device has but cannot be used to the fullest...
any way thank you for joining in i love how developers here are very helpful and doing a great job
so to show my love to them im willing to donate cash to whoever makes a rom with all these features up and running, and there are other people too who are willing to do the same
so good luck dev <3 much love
madshark2009 said:
I gotta say im very happy to hear that!
well most of the community here just want google camera working properly without losing drm keys and to have a native 4k screen option or 1080p/120hz hdr and all that stuff
so as i understood unlocking bootloader loses drm keys so flashing aosp roms with google camera doesnt make the camera better due to loss of drm (as noise reduction is lost along with the drm)
if its just possible a way to keep drm while having aosp that way we would have a God level of a camera, coming with 4k/1080p-120hz options that would do it! this phone would be the best for long time
but i guess its impossible to combine those features together which hurts me a lot knowing what potential this device has but cannot be used to the fullest...
any way thank you for joining in i love how developers here are very helpful and doing a great job
so to show my love to them im willing to donate cash to whoever makes a rom with all these features up and running, and there are other people too who are willing to do the same
so good luck dev <3 much love
Click to expand...
Click to collapse
Thanks for the nice and quick response! As a ex Xperia Usera am i aware of the benefits and cons of unlocking the Bootloader. I remeber well how the Camera stopped working on the Z1 after unlocking the Bootloader and the lack the of Camera2 API. And it looks like it isn't much better these Days.
A thing i really miss here is the choice to have a locked Bootloader with at least Root to save the DRMs and to be able to use modified Stock. With My Patch would this End in endless Options and Ways of Optimizing/Customizing the Firmware without loosing any Features. But this is something i don't count on anymore (Android is a Fort Knox since Marshmallow/Nougat)...
How does it actually looks like on AOSP? The Camera works and has legacy Camera2 API Support? Lost Features are the Super Slow Motion Recording and Noise Reduction? The added 120Hz Mode and 4K / HDR Features seem to be there...!?
Well, i'm still not sure what to do. I see a lack of Stock ROMs on the Xperia Forums (I worked on this last Night but was unable to extract the sin Files), but i see also how AOSP has enhanced on Xperia Devices. We don't have treble Support on the XZ Premium but the XZ1 is already able to use Unified AOSP Builds and almost everything is working well thanks to the great Devs and of course SONY. And i'm sure AOSP will ever be a important alternative to Stock (Smaller, faster, fresher)...
So which Way should i go? I'm planning for Years to create a AOSP based close to Google Firmware like OS, but Stock is just looking great too on Xperias. And the DRM Fix is allowing to use all the Features on Stock for now!?
Hmm... Sorry for the many Questions! :angel:
first welcome..great to see devs have an interest in this device. I'm sure you will love it. only thing i would wish for is to have google camera work on it. as for custom roms ,not well versed in that scene,, its my first ever android device to still getting to grips with it.
kibet85 said:
first welcome..great to see devs have an interest in this device. I'm sure you will love it. only thing i would wish for is to have google camera work on it. as for custom roms ,not well versed in that scene,, its my first ever android device to still getting to grips with it.
Click to expand...
Click to collapse
Thanks
Couldn't live without a unlocked Android anymore. Android User since around 8 Years here (Made some Holidays on iOS and Windows). And i'm glad to be back on Xperia. Hope You enjoy it as much as i do and will with the XZP But to understand that right, what's the actual Point with the Google Camera? I managed to gain some extra functionalities in the Past, but how does it actually looks like after installing the Stock Google Camera (Or even the Modded Ones)?
Is it full functional? Are the Pixel (2) Configs working? Differences between Stock and AOSP? Would love to take a look on the Camera Part overall. I want to shoot great Results with My new Baby so it's also important for Me...
Miustone said:
Thanks for the nice and quick response! As a ex Xperia Usera am i aware of the benefits and cons of unlocking the Bootloader. I remeber well how the Camera stopped working on the Z1 after unlocking the Bootloader and the lack the of Camera2 API. And it looks like it isn't much better these Days.
A thing i really miss here is the choice to have a locked Bootloader with at least Root to save the DRMs and to be able to use modified Stock. With My Patch would this End in endless Options and Ways of Optimizing/Customizing the Firmware without loosing any Features. But this is something i don't count on anymore (Android is a Fort Knox since Marshmallow/Nougat)...
How does it actually looks like on AOSP? The Camera works and has legacy Camera2 API Support? Lost Features are the Super Slow Motion Recording and Noise Reduction? The added 120Hz Mode and 4K / HDR Features seem to be there...!?
Well, i'm still not sure what to do. I see a lack of Stock ROMs on the Xperia Forums (I worked on this last Night but was unable to extract the sin Files), but i see also how AOSP has enhanced on Xperia Devices. We don't have treble Support on the XZ Premium but the XZ1 is already able to use Unified AOSP Builds and almost everything is working well thanks to the great Devs and of course SONY. And i'm sure AOSP will ever be a important alternative to Stock (Smaller, faster, fresher)...
So which Way should i go? I'm planning for Years to create a AOSP based close to Google Firmware like OS, but Stock is just looking great too on Xperias. And the DRM Fix is allowing to use all the Features on Stock for now!?
Hmm... Sorry for the many Questions! :angel:
Click to expand...
Click to collapse
thats the thing, what I understood is aosp doesnt have legace camera2 API support, no super slow mo, no noise reduction (as drm is lost).
as for screen options 4k HDR or 1080p 120hz seem to show in options but people and devs say its not actually working, as after they choose an option and restart they claim to nothing changing.
these are the main reasons why people here hesitate unlocking the bootloader, as there is no camera2 API support on aosp so you get google camera but lose noise reduction and so many other camera features.
and there is no additional features that aosp give, neither of 4k nor 120hz work, so there is really no point of unlocking, if any thing its not just useless but also worsens...
and while still having drm, google camera has no support for max resolution (only 8mp) and does not have HDR+ option
so here to sum up:
2 thing that will make this community love you so much
1) fully working google camera while still having drm (or drm patch for that matter if its impossible to backup drm)
2) screen options of [email protected] or [email protected]
if you can do that in aosp build thats the best
if you can do it in stock based build, also great
but as I saw your snappatch rom it looks very nice but yet again, unless it has those 2 things, unlocking bootloader and going through this much trouble is useless in my opinion
so good luck bro I really appreciate your collaboration
Miustone said:
Thanks
Couldn't live without a unlocked Android anymore. Android User since around 8 Years here (Made some Holidays on iOS and Windows). And i'm glad to be back on Xperia. Hope You enjoy it as much as i do and will with the XZP But to understand that right, what's the actual Point with the Google Camera? I managed to gain some extra functionalities in the Past, but how does it actually looks like after installing the Stock Google Camera (Or even the Modded Ones)?
Is it full functional? Are the Pixel (2) Configs working? Differences between Stock and AOSP? Would love to take a look on the Camera Part overall. I want to shoot great Results with My new Baby so it's also important for Me...
Click to expand...
Click to collapse
the thing about google camera is in the HDR+ algorithm. its an incredibly easy way to produce some stunning photos. for HDR+ to work,, it needs the full camera2api and support of RAW images. currently, Sony use some kind of legacy camera2api and doesn't support RAW, So most ports are limited to 8mp and HDR+ doesn't work.
madshark2009 said:
thats the thing, what I understood is aosp doesnt have legace camera2 API support, no super slow mo, no noise reduction (as drm is lost).
as for screen options 4k HDR or 1080p 120hz seem to show in options but people and devs say its not actually working, as after they choose an option and restart they claim to nothing changing.
these are the main reasons why people here hesitate unlocking the bootloader, as there is no camera2 API support on aosp so you get google camera but lose noise reduction and so many other camera features.
and there is no additional features that aosp give, neither of 4k nor 120hz work, so there is really no point of unlocking, if any thing its not just useless but also worsens...
and while still having drm, google camera has no support for max resolution (only 8mp) and does not have HDR+ option
so here to sum up:
2 thing that will make this community love you so much
1) fully working google camera while still having drm (or drm patch for that matter if its impossible to backup drm)
2) screen options of [email protected] or [email protected]
if you can do that in aosp build thats the best
if you can do it in stock based build, also great
but as I saw your snappatch rom it looks very nice but yet again, unless it has those 2 things, unlocking bootloader and going through this much trouble is useless in my opinion
so good luck bro I really appreciate your collaboration
Click to expand...
Click to collapse
kibet85 said:
the thing about google camera is in the HDR+ algorithm. its an incredibly easy way to produce some stunning photos. for HDR+ to work,, it needs the full camera2api and support of RAW images. currently, Sony use some kind of legacy camera2api and doesn't support RAW, So most ports are limited to 8mp and HDR+ doesn't work.
Click to expand...
Click to collapse
SONY really HAS to include Camera HAL3 in the Future... Looks like the XZ2 will have the same Issues, but i wonder how hard it can be to change the Software of the own produced Hardware!? The Xperia Cameras would be outstanding against Others running AOSP, but even with all the Developer Support are they missing this Important Point...
I really hope i can gain some nice Results on Stock, otherwise would i like to try out Porting the SONY Camera App(s) to AOSP (With working Noise Reduction) which would even without HAL3 Support end in better Results as without HAL3 on AOSP/Google Camera Apps. Could be something for Xperia Cross Device Development, but i don't know yet if this is even possible without Porting the half of the Xperia Stock Systems to AOSP...
Can't wait to get My Hands on the XZP... Checking the Shipping State all 10 Minutes
https://nolp.dhl.de/nextt-online-public/set_identcodes.do?lang=de&idc=JJD1405123613478
Bit worried about the coming Camera Quality but i'm looking forward to get the best out of our Devices! Treble would also be something nice to have... Has anyone checked the Partition Table of the XZ Premium to see if there is a chance for a Vendor Partition!?
I think if you create a stock based rom with ported xz2 features and native 4k, you are doing the best and it most be easier and more stable than a aosp.
Blackghosthm said:
I think if you create a stock based rom with ported xz2 features and native 4k, you are doing the best and it most be easier and more stable than a aosp.
Click to expand...
Click to collapse
Yeha, i was thinking about to deliver Stock again (Since SONY Stock is also really good except of the End of Support with Updates at any Point). But that means pretty Device Specific Work (Lot of Work). I could ease the Things on Stock up if i would deliver real Stock (Barely Debloated) flashable ZIPs for Xperia Devices besides doing the Snappatch for Xperia (Debloating, Adding, Root, Features, Google App Replacements, Mods and such).
I see there is also actually no alternative to this "Turbo ROM" i've taken a look on. And to be honestly, i don't see Me using this ROM. So a Stock Flashable with some Extra Features and deep going Optimizations from the Patch could be something great in My Eyes. I could also extend the Support with that up to other Xperia Devices like the XZ1 and XZ2 (If the need is there).
Let's see what i'm able to do after getting My new Baby. I'm full of Hopes that i rock this Device for all of us here :fingers-crossed:
madshark2009 said:
due to loss of drm (as noise reduction is lost
Click to expand...
Click to collapse
I used to run an old build of AOSP to test out the 120 hz feature (though it's bugged. Sony devs are aware of this and I filed an issue in their github). The noise reduction was albeit the same. AFAIK the pictures you take will just show a green picture if you don't have the drm keys (at least the fix). But the noise reduction is still quite the same. However, I did not test that completely, just from memory.
As for topic, I'd rather go stock. The google camera isn't really something I'm after, but that's just me. I'm slowly teaching myself how to port stuff from other phones, specifically the new XZ2. I'd rather have stock + your patch + xz2 goodies, maybe?
iArvee said:
I used to run an old build of AOSP to test out the 120 hz feature (though it's bugged. Sony devs are aware of this and I filed an issue in their github). The noise reduction was albeit the same. AFAIK the pictures you take will just show a green picture if you don't have the drm keys (at least the fix). But the noise reduction is still quite the same. However, I did not test that completely, just from memory.
As for topic, I'd rather go stock. The google camera isn't really something I'm after, but that's just me. I'm slowly teaching myself how to port stuff from other phones, specifically the new XZ2. I'd rather have stock + your patch + xz2 goodies, maybe?
Click to expand...
Click to collapse
Yah in stock based the fix works good
But in aosp that doesnt work
iArvee said:
I used to run an old build of AOSP to test out the 120 hz feature (though it's bugged. Sony devs are aware of this and I filed an issue in their github). The noise reduction was albeit the same. AFAIK the pictures you take will just show a green picture if you don't have the drm keys (at least the fix). But the noise reduction is still quite the same. However, I did not test that completely, just from memory.
As for topic, I'd rather go stock. The google camera isn't really something I'm after, but that's just me. I'm slowly teaching myself how to port stuff from other phones, specifically the new XZ2. I'd rather have stock + your patch + xz2 goodies, maybe?
Click to expand...
Click to collapse
Getting XZ2 Features on the XZ Premium sounds Good to Me. Smart would be to integrate the Ported Content into the Patch so People can add it or just keep it Original with a untouched Stock Firmware (System+Boot). But i wonder...
madshark2009 said:
Yah in stock based the fix works good
But in aosp that doesnt work
Click to expand...
Click to collapse
Does it mean that the Camera does not work without this DRM Fix (Which isn't TWRP flashable (Without a PC))?
And AOSP has a working Camera out of the Box but without Camera2 API and with Noisy Pictures!? Just want to make sure i got it right before flaming about the lack of a mobile DRM Fix (Which could be included in ROMs, or simple be a Flashable ZIP for on the go)
Something i don't want is the need for a PC after flashing anything. I test so often My changes with Clean Flashs over the Day that it would kill Me to use Windows with this DRM Fix over and over again >.<
When you wana fix drm keys on stock or stock based rom you need twrp+flashable kernel (you can find it in afs)+flashable magisk+drm fix flashable file thats all so quickly without pc.
Im do it all the time in all oreo firmware.
Blackghosthm said:
When you wana fix drm keys on stock or stock based rom you need twrp+flashable kernel (you can find it in afs)+flashable magisk+drm fix flashable file thats all so quickly without pc.
Im do it all the time in all oreo firmware.
Click to expand...
Click to collapse
So there no need for the XperiFix Tool all the Time? Can You give Me any Links to it? I don't see the need to include it into the ROMs itself, but i would really like to take a look on what it does (Especially since Magisk in involved somehow). Maybe is there a way to get the Noise Reduction on a AOSP Port of the SONY Camera App. Can't say anything about this yet...
Kernel link:https://androidfilehost.com/?fid=673791459329069491
Drm fix link:https://mega.nz/#!LRoFkSDA!bOsnRRE1gRpAZ0su-bZMfUjvMB7aRkLEc3V63bOuKnM
You dont need xperifix but if you flash stock rom with flashtool you need to flash twrp in fastboot and if you want twrp you can download it from here:https://dl.twrp.me/maple/twrp-3.2.1-0-maple.img.html
Blackghosthm said:
Kernel link:https://androidfilehost.com/?fid=673791459329069491
Drm fix link:https://mega.nz/#!LRoFkSDA!bOsnRRE1gRpAZ0su-bZMfUjvMB7aRkLEc3V63bOuKnM
You dont need xperifix but if you flash stock rom with flashtool you need to flash twrp in fastboot and if you want twrp you can download it from here:https://dl.twrp.me/maple/twrp-3.2.1-0-maple.img.html
Click to expand...
Click to collapse
Thanks for sharing this with Me! Since this includes a Kernel am i wondering what's changed on the boot.img to get the Fix working. And it's dated on 2017 and still working on newer Firmwares?
I just extracted the latest G8414 .145 Firmware. Would be cool if i could Patch the kernel for the fix so that we can run the latest Kernel with it...
Yes it works,this is canbe good.
Miustone said:
So there no need for the XperiFix Tool all the Time? Can You give Me any Links to it? I don't see the need to include it into the ROMs itself, but i would really like to take a look on what it does (Especially since Magisk in involved somehow). Maybe is there a way to get the Noise Reduction on a AOSP Port of the SONY Camera App. Can't say anything about this yet...
Click to expand...
Click to collapse
Yes and no. On an old version of the hack, you can just flash the drmfix. However, on the new xperifix software, it seems to also change a few file attributes. Not really sure about that though.
Androplus' kernel (kernel.andro.plus) is always updated to the latest version. You can flash that and do the old method of the drmfix (flashing) instead of the xperifix. I've tried that before but it seems to not work. I probably missed a step anyways.
iArvee said:
Yes and no. On an old version of the hack, you can just flash the drmfix. However, on the new xperifix software, it seems to also change a few file attributes. Not really sure about that though.
Androplus' kernel (kernel.andro.plus) is always updated to the latest version. You can flash that and do the old method of the drmfix (flashing) instead of the xperifix. I've tried that before but it seems to not work. I probably missed a step anyways.
Click to expand...
Click to collapse
Im tried androplus kernel and it doesn't fix drm keys.

Which Rom?

Just got a Mi 9T and trying to decide on which ROM to laod onto it? I have Pixel Experience+ on my Mi 8 Se which I like, after something similar.
I've noticed there's no official PE for this phone, likewise with LineageOS. Where these are "unofficial", what are the downsides to not having official support for a device? Are either likely to become official?
Evolution X 2.0 also looks quite interesting but I need to look into it a bit more.
So, what are others using? I'd like to get the near stock experience I got from PE+ along with the device being nice and snappy without hammering the battery more than it should.
BJozi said:
Just got a Mi 9T and trying to decide on which ROM to laod onto it? I have Pixel Experience+ on my Mi 8 Se which I like, after something similar.
I've noticed there's no official PE for this phone, likewise with LineageOS. Where these are "unofficial", what are the downsides to not having official support for a device? Are either likely to become official?
Evolution X 2.0 also looks quite interesting but I need to look into it a bit more.
So, what are others using? I'd like to get the near stock experience I got from PE+ along with the device being nice and snappy without hammering the battery more than it should.
Click to expand...
Click to collapse
Only downside is that if the person who make the port decide to stop doing it, move on to another device or if life become too busy.. the ROMs will not be updated, where Official ports you kind of have updates for sure.
Pupet_Master said:
Only downside is that if the person who make the port decide to stop doing it, move on to another device or if life become too busy.. the ROMs will not be updated, where Official ports you kind of have updates for sure.
Click to expand...
Click to collapse
For sure? Don't be so optimistic You apparently haven't seen much yet.
Wysłane z mojego Mi 9T przy użyciu Tapatalka
Antyhaker said:
For sure? Don't be so optimistic You apparently haven't seen much yet.
Wysłane z mojego Mi 9T przy użyciu Tapatalka
Click to expand...
Click to collapse
Dude i'm in XDA since 2014. The community always keep things alive. I'm not being optimistic.
Pupet_Master said:
Dude i'm in XDA since 2014. The community always keep things alive. I'm not being optimistic.
Click to expand...
Click to collapse
Apparently still too short Unofficial versions often have much better support.
Wysłane z mojego Mi 9T przy użyciu Tapatalka
Antyhaker said:
Apparently still too short Unofficial versions often have much better support.
Wysłane z mojego Mi 9T przy użyciu Tapatalka
Click to expand...
Click to collapse
They do, but he asked the downside
The only one i can think is that if who compile/maintain move on the ROM become "abandonware".
but i agree, unofficial is better.
Running official havocos 2.9 at the moment, seems pretty good

Categories

Resources