Thread copy pasterino here from Q&A....
PETITION https://www.change.org/p/zte-camera-api2-support-for-axon-7
We want ZTE to add Camera Api2 support for Axon 7
why do we want it? it is easy to add! and axon 7 supports it, But is not enabled by ZTE yet.
"Camera API 2.0 is New API which allowing you much better camera control by camera apps and also increase the performance of camera.
Camera API 2.0 is fast enough to take advantage of the full resolution of the sensor at 30 fps-burst mode. This means HDR or other such computational photography should be much "cheaper" to do on Android devices. The new API also allows for much more fine-grained control of the sensor, lens and flash per individual frame".
- Poll added
also, dac support for any audio app can be worked so that DAC is always on, but can be turned off/on function. "qualcomm/akm switch" for battery saving.
Please request also Treble support for Oreo release
Gachmuret said:
Please request also Treble support for Oreo release
Click to expand...
Click to collapse
Yes, will do.
is there a petition page, or shuld we just like your post?
vishnoo said:
is there a petition page, or shuld we just like your post?
Click to expand...
Click to collapse
My bad ,sorry here you go https://www.change.org/p/zte-camera-api2-support-for-axon-7
Link added to the post now. Thanks!
Signed.
This is what I wrote when I singed it.
Hope they read it.
" This is the correct way to implement camera features, ZTE should not use their proprietary closed source way and leave us out of all the mods we could use, like the enhanced Google Camera with HDR+ support, and all the camera apps that rely on Api2 for Manual Exposure time and ISO adjustments.
Please listen to us and make the camera Api2 guys, we'll make sure to advertise it as a good deed in all the developer community and this will uplift your sales, the Axon 7 is a great phone, if you provide support for it as well you could score a winner and make your Axon line as known as the Galaxy line one day. "
Pruikki said:
My bad ,sorry here you go https://www.change.org/p/zte-camera-api2-support-for-axon-7
Link added to the post now. Thanks!
Click to expand...
Click to collapse
why not add for treble support they are giving us Oreo but excluding treble seems like a bad move to have.
so also start or add petition for adding support for project treble on our Axon7:fingers-crossed:
not sure if you guys are aware but there has been progress and success by LOS devs on other devices that shipped with legacy cameras.
they build an oss camera hal with full level support (camera api 2) with the help of IDA. and there will be more devices using the same approach.
I'm not gone name the devs who did it because I want to prevent that random users spam them with begs for help/support to port.
they are already limited in their free time as it is.
just saying it is possible with the proper knowledge even if the OEM doesn't provide any sources.
celoxocis said:
they build an oss camera hal with full level support (camera api 2) with the help of IDA. and there will be more devices using the same approach.
I'm not gone name the devs who did it because I want to prevent that random users spam them with begs for help/support to port.
they are already limited in their free time as it is.
just saying it is possible with the proper knowledge even if the OEM doesn't provide any sources.
Click to expand...
Click to collapse
Is this something that the you/Mike could implement on the Axon 7? Are the codes semi/partially transferable?
kg3 said:
Is this something that the you/Mike could implement on the Axon 7? Are the codes semi/partially transferable?
Click to expand...
Click to collapse
no nothing is actually. every device is different.
and the dev would also require to have the device.
As said in other thread, No api2 in Oreo, but thats 50/50 now (petiton had effect perhaps)
-No treble, new axon hero phone will be soon announced, not this year but early next year like Q1 (if things go accordingly/as planned) (no worry,current owners,wont feel jealous)
Api 2 enabled on next device 100%
, i think
Pruikki said:
As said in other thread, No api2 in Oreo, but thats 50/50 now (petiton had effect perhaps)
-No treble, new axon hero phone will be soon announced, not this year but early next year like Q1 (if things go accordingly/as planned) (no worry,current owners,wont feel jealous)
Api 2 enabled on next device 100%
, i think
Click to expand...
Click to collapse
but he just said it is non transferable lol
celoxocis said:
no nothing is actually. every device is different.
and the dev would also require to have the device.
Click to expand...
Click to collapse
If the Axon 7 XDA community raise funds to buy Mike a Axon 7, will he consider trying to get API2 working on the Axon 7? Does he have the time to work on the device?
What does Mike think the chances are of getting API2 working, without having looked into the sources/device etc? High level of course.
kg3 said:
If the Axon 7 XDA community raise funds to buy Mike a Axon 7, will he consider trying to get API2 working on the Axon 7? Does he have the time to work on the device?
What does Mike think the chances are of getting API2 working, without having looked into the sources/device etc? High level of course.
Click to expand...
Click to collapse
I don't think he would consider maintaining/working on an additional device.
as he is already maintaining a bunch of other device's and has limited free time. as he is also one of the head dev's of los, he works on los code besides devices.
you could however try and ask Vitaliy who figured out how to IDA port the camera legacy to camera full.
Can you PM me Vitaliy details?
I'm putting my trust on this thread, please make it happen!
Hello.
We have reached more than our goal of 100 people on the petition now, And that is good.
232 signatures, To show for that there is large interest in this feature.
The Petition will be kept open, Because it is very active.
Now we need Change.Org to forward the message and ZTE Germany to take a look as well.
Things are going well.
But i can not guarantee that Api2 will be fully enabled in future updates in Oreo, But is looking promising
hope this gets to the ZTE CEO
kg3 said:
Can you PM me Vitaliy details?
Click to expand...
Click to collapse
going to quote you here as i'm not sure if you receive notifications on pm's. I sent you two pm's today. I've talked to highwaystar today and he is interested. after you read them. I suggest to start a discussion in the axon7 community on my proposal.
Related
I wonder if anyone here is delved deep enough into the inner workings of the camera system. Would it be possible, for example, to control the exposure settings independently for each lens?
That way, we could do *real* HDR shots that would blow the socks off the iPhone HDR stuff.
Of course, it wouldn't work for anything too close because of the distortion, but anything further away should work great.
Thoughts?
Would be a good idea!
Sent from my Dual Core HTC 3vo 3D
Agreed, HDR on my phone has been my dream for a while now. I plan on taking some skilled photos in 3d, and this would be awesome
Sent from my Evo 3D
Speed Shooting
Would It Also Be Possible To Use Both Cameras For Speed Shooting?
Like Where One Would Take The Picture Then The Other Would Take It Again.
That Would Be Awesome.
This should be in q&a.....and I only say that because I opened this thread, not noticing the ?, thinking it was a working modification to the cameras. Might want to pm a mod and have it moved.
hockeyfamily737 said:
This should be in q&a.....and I only say that because I opened this thread, not noticing the ?, thinking it was a working modification to the cameras. Might want to pm a mod and have it moved.
Click to expand...
Click to collapse
I think this is in the correct area. Yes, it is a question. But it is a question geared towards a topic that will in all likelihood take some heavy development.
The ideas for HDR and speed shots (halving the time between pictures) are great and definitely something I would use if/when they can be implemented.
spartan15A said:
Would It Also Be Possible To Use Both Cameras For Speed Shooting?
Like Where One Would Take The Picture Then The Other Would Take It Again.
That Would Be Awesome.
Click to expand...
Click to collapse
If your memory card could handle it I'm sure it's possible. You would probably need access to the kernel source to do much of anything with it though.
Imagine a camera app where each core gets a camera hdw to read and process.
Imagine a camera app where we know what each core is doing !
@ OP - wrong section. You developed?
@ Spartan15A - check the market "fast burst camera", is frakking awesome...
BANG! from my shooter...
The Android Camera API only allows you to specify one Camera at a time so you'll need to overcome that obstacle first. Mostly you are limited to what the Android Camera API makes available to you. In some cases you can include additional non-standard properties that the vendor's implementation checks for. Another possibility is that HTC will release a library to make more of the Camera features available.
joe85 said:
The Android Camera API only allows you to specify one Camera at a time so you'll need to overcome that obstacle first. Mostly you are limited to what the Android Camera API makes available to you. In some cases you can include additional non-standard properties that the vendor's implementation checks for. Another possibility is that HTC will release a library to make more of the Camera features available.
Click to expand...
Click to collapse
I wonder if the cameras are even accessible independently at all, or if it just defaults to one of the two.
Have you guys seen the Sony Panorama camera app? Is that using both cameras?
ioos said:
Have you guys seen the Sony Panorama camera app? Is that using both cameras?
Click to expand...
Click to collapse
Cool app - but I don't think it uses the second camera.
<stupid
delete
gthing said:
I wonder if the cameras are even accessible independently at all, or if it just defaults to one of the two.
Click to expand...
Click to collapse
http://developer.android.com/reference/android/hardware/Camera.html#open(int)
Try that method out and see.
creator2456 said:
I think this is in the correct area. Yes, it is a question.
Click to expand...
Click to collapse
Why is this so hard for people to understand. You yourself just said its a question...so therefore it should be in q&a. Development is for developing...Not Asking Questions. To the op, nice idea.
Sent from my PG86100
I wish when in 2D mode the camera towards the middle was used. I always have a finger over the outside camera.
But yeah, HTC could really let us do some cool stuff with both cameras in 2D mode.
Moved to proper forum.
Not sure why this was moved, as it is clearly a development question (is it possible to access the hardware cameras independently - and if so, how?) but whatever...
Here's another application that we could use the two cameras for:
http://gizmodo.com/5822623/two-lenses-will-fix-compact-cameras-depth-of-field-proposes-samsung
Would probably need to go through the actual patent doc to figure out exactly what the method is...
Has anyone been able to port Google's HDR+ algorithm on other phones, i.e. the G5?
In the end it's only a software processing and on my wife's Nexus 5X it works damn good, mostly putting my G5 to shame...
Did anyone successfully reverse-engineered it to port it on more camera hardwares??
Thanks.
This is the closest you will get
http://chromloop.com/
Unfortunately the zero shutter lag requires Android 7.1 and HDR+ is also disabled
lolmensch said:
This is the closest you will get
http://chromloop.com/
Unfortunately the zero shutter lag requires Android 7.1 and HDR+ is also disabled
Click to expand...
Click to collapse
Thank you for the tip.
Is there a particular reason why HDR+ shouldn't be working for other cameras too? Isn't it just a software algorithm based on taking multiple pictures in rapid succession?
Gatz said:
Thank you for the tip.
Is there a particular reason why HDR+ shouldn't be working for other cameras too? Isn't it just a software algorithm based on taking multiple pictures in rapid succession?
Click to expand...
Click to collapse
np mate.
it is actually rather complicated. you should probably be able to do hdr on our phones by idk maybe change build prop or similiar stuff. maybe even some libs are needed. it seems though that the 5x and 6p hdr+ isnt the real deal.
if you are more interested: https://www.reddit.com/r/nexus5x/comments/57ukba/psa_google_camera_42_mod_on_5x6p_literary_bring/
tl;dr:
even hw accelerated hdr+ should work on our phones but we are missing people wanting/being able to port it I'd say (as well as 7.1.1 for all features)
lolmensch said:
np mate.
it is actually rather complicated. you should probably be able to do hdr on our phones by idk maybe change build prop or similiar stuff. maybe even some libs are needed. it seems though that the 5x and 6p hdr+ isnt the real deal.
if you are more interested: https://www.reddit.com/r/nexus5x/comments/57ukba/psa_google_camera_42_mod_on_5x6p_literary_bring/
tl;dr:
even hw accelerated hdr+ should work on our phones but we are missing people wanting/being able to port it I'd say (as well as 7.1.1 for all features)
Click to expand...
Click to collapse
Interesting one. In fact I tried this Camera NX both on my G5 and on the Nexus 5X of my wife and already uninstalled in both...
On the G5 it does absolutely nothing.
On the 5X it is supposed to use HDR+ with ZSL, but actually doesn't. The photos come out much worse than with the stock camera. I don't understand why people claim it works...
I wish someone could make the Pixel's HDR+ work on the Snapdragon 820 and make it available for all smartphones using that chipset, which are quite many and nice ones.
The current HDR mode on the G5 is good for an alternative
lywyn said:
The current HDR mode on the G5 is good for an alternative
Click to expand...
Click to collapse
It's crap, if you're not directly in perfectly lit room or area you'll get lag while it takes the three shots
girn26 said:
It's crap, if you're not directly in perfectly lit room or area you'll get lag while it takes the three shots
Click to expand...
Click to collapse
... and everything blurry.
This camera may even be very good hardware, but the software makes it unusable in most situations where everything isn't very still. A bit disappointing.
Hi all -- A few weeks ago, I bought a Moto Z to play with Daydream, and one of the first things I noticed was that Google's HDR+ feature that I had used for so long on my Nexus 6 was not available. It didn't even occur to me that this feature was proprietary to Nexus devices, so I got to work right away trying to unlock access to HDR+ on my Moto Z as I firmly believe that HDR+ is still the gold standard in computational image blending for Android devices.
It turns out that tricking non-Nexus devices into using HDR+ is not that hard. I grabbed a copy of Camera NX from chromloop.com, decompiled using apktool, and tweaked the smali code in the DeviceHelper file to ensure that the function isNexus6P() always returns a value of true, regardless of device (the corresponding line can be edited to read "const v0, 1"). I'll post a modified APK from my development machine in just a moment...
elosito said:
Hi all -- A few weeks ago, I bought a Moto Z to play with Daydream, and one of the first things I noticed was that Google's HDR+ feature that I had used for so long on my Nexus 6 was not available. It didn't even occur to me that this feature was proprietary to Nexus devices, so I got to work right away trying to unlock access to HDR+ on my Moto Z as I firmly believe that HDR+ is still the gold standard in computational image blending for Android devices.
It turns out that tricking non-Nexus devices into using HDR+ is not that hard. I grabbed a copy of Camera NX from chromloop.com, decompiled using apktool, and tweaked the smali code in the DeviceHelper file to ensure that the function isNexus6P() always returns a value of true, regardless of device (the corresponding line can be edited to read "const v0, 1"). I'll post a modified APK from my development machine in just a moment...
Click to expand...
Click to collapse
This sounds great. Would be very appreciative if you posted it.
elosito said:
Hi all -- A few weeks ago, I bought a Moto Z to play with Daydream, and one of the first things I noticed was that Google's HDR+ feature that I had used for so long on my Nexus 6 was not available. It didn't even occur to me that this feature was proprietary to Nexus devices, so I got to work right away trying to unlock access to HDR+ on my Moto Z as I firmly believe that HDR+ is still the gold standard in computational image blending for Android devices.
It turns out that tricking non-Nexus devices into using HDR+ is not that hard. I grabbed a copy of Camera NX from chromloop.com, decompiled using apktool, and tweaked the smali code in the DeviceHelper file to ensure that the function isNexus6P() always returns a value of true, regardless of device (the corresponding line can be edited to read "const v0, 1"). I'll post a modified APK from my development machine in just a moment...
Click to expand...
Click to collapse
sounds great. wait for your good news
elosito said:
Hi all -- A few weeks ago, I bought a Moto Z to play with Daydream, and one of the first things I noticed was that Google's HDR+ feature that I had used for so long on my Nexus 6 was not available. It didn't even occur to me that this feature was proprietary to Nexus devices, so I got to work right away trying to unlock access to HDR+ on my Moto Z as I firmly believe that HDR+ is still the gold standard in computational image blending for Android devices.
It turns out that tricking non-Nexus devices into using HDR+ is not that hard. I grabbed a copy of Camera NX from chromloop.com, decompiled using apktool, and tweaked the smali code in the DeviceHelper file to ensure that the function isNexus6P() always returns a value of true, regardless of device (the corresponding line can be edited to read "const v0, 1"). I'll post a modified APK from my development machine in just a moment...
Click to expand...
Click to collapse
Please post!! Much appreciated
Apologies for the delay -- I'm working up to my total of 10 posts so that I can share the file with you all. Give me just a few minutes (and forgive this short post that is helping me reach 10!)...
---------- Post added at 09:20 AM ---------- Previous post was at 08:57 AM ----------
Okay, just worked myself up past ten posts so that I can share a link with you all: http://www.mediafire.com/file/l8num4lyw05vybt/Camera4-hdrplus.apk
I hope that this works as well for enabling HDR+ on the G5 as it does on my Moto Z! Please let me know how it goes when you try it.
I had install the apps and it had HDR+ option in it
but once I take the photo with HDR+ auto or HDR+ on , the photo come out like it blur and just 1.XX MB
and if i take the photo with HDR+ Off , the photo will just back to normal
elosito said:
Apologies for the delay -- I'm working up to my total of 10 posts so that I can share the file with you all. Give me just a few minutes (and forgive this short post that is helping me reach 10!)...
---------- Post added at 09:20 AM ---------- Previous post was at 08:57 AM ----------
Okay, just worked myself up past ten posts so that I can share a link with you all: http://www.mediafire.com/file/l8num4lyw05vybt/Camera4-hdrplus.apk
I hope that this works as well for enabling HDR+ on the G5 as it does on my Moto Z! Please let me know how it goes when you try it.
Click to expand...
Click to collapse
This is what I got all on default settings (HDR + with highest res)
Seems low res and blurry. Thanks for attempting this! Hope you get it
girn26 said:
This is what I got all on default settings (HDR + with highest res)
Seems low res and blurry. Thanks for attempting this! Hope you get it
Click to expand...
Click to collapse
Thanks so much for sharing the sample images -- bummer that this doesn't seem to be working yet on your device. Just to confirm, are you indeed using a G5? I didn't see any device specs in the photo metadata. I would also be curious to hear what OS version you're running on your device. HDR+ support seems to be based upon how complete a device's access to the camera2 API is, and it is clear that completeness of support for this API varies considerably across devices and OS versions. Guess I just got lucky that my Moto Z with 7.0 supports all of the needed API calls! Maybe there is still hope for modifying a different version of the camera app to support the G5.
elosito said:
Thanks so much for sharing the sample images -- bummer that this doesn't seem to be working yet on your device. Just to confirm, are you indeed using a G5? I didn't see any device specs in the photo metadata. I would also be curious to hear what OS version you're running on your device. HDR+ support seems to be based upon how complete a device's access to the camera2 API is, and it is clear that completeness of support for this API varies considerably across devices and OS versions. Guess I just got lucky that my Moto Z with 7.0 supports all of the needed API calls! Maybe there is still hope for modifying a different version of the camera app to support the G5.
Click to expand...
Click to collapse
I have the same results. H830 T-Mobile G5 on 7.0.
elosito said:
Thanks so much for sharing the sample images -- bummer that this doesn't seem to be working yet on your device. Just to confirm, are you indeed using a G5? I didn't see any device specs in the photo metadata. I would also be curious to hear what OS version you're running on your device. HDR+ support seems to be based upon how complete a device's access to the camera2 API is, and it is clear that completeness of support for this API varies considerably across devices and OS versions. Guess I just got lucky that my Moto Z with 7.0 supports all of the needed API calls! Maybe there is still hope for modifying a different version of the camera app to support the G5.
Click to expand...
Click to collapse
Hey bud, I'm in on H831 on 7.0. Hopefully you can work some magic and get it working. Best of luck !
H850 with 7.0 stock rooted same results. It is odd as it is basically the same hardware besides the imaging sensor. I have the impression that it refocuses after the first picture for HDR leaving it blurry after stitching together
Huh. I tried it out on the V20 and same blurry result. The 6p uses an IMX377 while the Pixel uses an IMX 378. The G5 uses an IMX234 and the V20 uses an IMX298. I wonder if the sensors in use have anything to do with it, too?
I'm really interested in getting this phone, I have skipped the Note 8 until I see what this phone brings, and from what I saw at the presentation I looks like an AWESOME phone, but when I look at past Huawei flagships (mate 9, P9, etc) almost non-existing major updates, custom roms support and mods I start thinking if paying a premium price for a phone like this its really worth for a person like me who likes to play around with rooting, modding and installing custom roms in my devices or should I play safe and get a Samsung or Pixel device.
No. Do not buy Huawei if modding is important.
Non existent with previous mate 9 and barely with mate 8.
Across the board, it's not getting easier
intruda119 said:
No. Do not buy Huawei if modding is important.
Non existent with previous mate 9 and barely with mate 8.
Across the board, it's not getting easier
Click to expand...
Click to collapse
I appreciate your answer, there are great devices but not for us.
yael20 said:
I'm really interested in getting this phone, I have skipped the Note 8 until I see what this phone brings, and from what I saw at the presentation I looks like an AWESOME phone, but when I look at past Huawei flagships (mate 9, P9, etc) almost non-existing major updates, custom roms support and mods I start thinking if paying a premium price for a phone like this its really worth for a person like me who likes to play around with rooting, modding and installing custom roms in my devices or should I play safe and get a Samsung or Pixel device.
Click to expand...
Click to collapse
To be honest you are better off not getting any flagship if you like modding. The pixel is a pain to dev for to the point that many devs are not getting the new pixel or even supporting it. Samsung well we all know that dev support for that is a joke.
zelendel said:
To be honest you are better off not getting any flagship if you like modding. The pixel is a pain to dev for to the point that many devs are not getting the new pixel or even supporting it. Samsung well we all know that dev support for that is a joke.
Click to expand...
Click to collapse
Thanks for your answer, so that being the case, which phone(s) would you recommend me?
yael20 said:
Thanks for your answer, so that being the case, which phone(s) would you recommend me?
Click to expand...
Click to collapse
If modding is your thing then I would look at something like one plus. Things to avoid are devices with dual partition setup. The pixel showed how much devs dont want to deal with that.
Things to look out for are things like kernel source being up to date which I hate to say knocks 90% of the China based OEM out of it. Maybe the Euro version of samsung devices might be OK but even they get little to no real devs support. I would look around the site. See what devices have real support. No I am not talking about tons of los based roms. That is not development. I mean real development with system mods and hardware tweaks.
zelendel said:
If modding is your thing then I would look at something like one plus.
Click to expand...
Click to collapse
Unfortunately OnePlus sucks at many things that are important for many of us so I guess we don't have a choice.
zadox said:
Unfortunately OnePlus sucks at many things that are important for many of us so I guess we don't have a choice.
Click to expand...
Click to collapse
Things like what? The one bonus is that with one plus it can be fixed for the most part as to where even the kernel code on huawei devices is useless.
zelendel said:
Things like what? The one bonus is that with one plus it can be fixed for the most part as to where even the kernel code on huawei devices is useless.
Click to expand...
Click to collapse
Can we start with the MicroSD ?
zadox said:
Can we start with the MicroSD ?
Click to expand...
Click to collapse
This I agree with but many of the OEM are opting out of sdcards ever since google removed all the code fore native sdcard support from android years ago. But to be hones 64gb is more then enough for a mobile device. Mix that with some common sense (backing up stuff. No I dont mean cloud backup lol)
zadox said:
Unfortunately OnePlus sucks at many things that are important for many of us so I guess we don't have a choice.
Click to expand...
Click to collapse
I think the one plus is a good device with great specs, but I don't like it's design... May be due it's Iphoneish look lol
zelendel said:
To be honest you are better off not getting any flagship if you like modding. The pixel is a pain to dev for to the point that many devs are not getting the new pixel or even supporting it. Samsung well we all know that dev support for that is a joke.
Click to expand...
Click to collapse
Why not? You can get systemless root (Exynos) or TWRP installed classic root (Snapdragon) for Note8.
Sure Knox and/or SafetyNet gets tripped, but that's the price to pay for rooting.
But you can root current flagship phones and there's plenty of modding community for Note8.
vasra said:
Why not? You can get systemless root (Exynos) or TWRP installed classic root (Snapdragon) for Note8.
Sure Knox and/or SafetyNet gets tripped, but that's the price to pay for rooting.
But you can root current flagship phones and there's plenty of modding community for Note8.
Click to expand...
Click to collapse
Samsung based roms are not development. Samsung devices have sucked for development for years. This is why main stream developers don't get that device.
Ok, thanks for the info. I haven't followed the scene. Just installed a good LO fork on my Note3 and it is working wonders (sans NFC and GPS/camera performance is generic).
zelendel said:
To be honest you are better off not getting any flagship if you like modding. The pixel is a pain to dev for to the point that many devs are not getting the new pixel or even supporting it. Samsung well we all know that dev support for that is a joke.
Click to expand...
Click to collapse
That being said , what are 3 phones that you can say "this is a good phone, and I can do all lot of things with it("? is the nexus 6p one of them? thanks for your help.
yael20 said:
That being said , what are 3 phones that you can say "this is a good phone, and I can do all lot of things with it("? is the nexus 6p one of them? thanks for your help.
Click to expand...
Click to collapse
Yes. The 6p (minus the battery issues) is good for rom development. It will get support from 3rd parties for at least another 2 years.
I would say the one plus 3 or 3t
The nexus 6p
Any one of the Sony devices as they have a good development setup.
yael20 said:
I'm really interested in getting this phone, I have skipped the Note 8 until I see what this phone brings, and from what I saw at the presentation I looks like an AWESOME phone, but when I look at past Huawei flagships (mate 9, P9, etc) almost non-existing major updates, custom roms support and mods I start thinking if paying a premium price for a phone like this its really worth for a person like me who likes to play around with rooting, modding and installing custom roms in my devices or should I play safe and get a Samsung or Pixel device.
Click to expand...
Click to collapse
@auras76 (confirmed via private message that he will be supporting Mate 10 and continue his awesome rom that he has for Mate 9 ->[ROM] RomAur-v2.2-[16/10]-[UB][7.0_Fw.b197]-FAST-STABLE :good:
yael20 said:
I think the one plus is a good device with great specs, but I don't like it's design... May be due it's Iphoneish look lol
Click to expand...
Click to collapse
Problem with OP (I switched from OP5 to IP7+ just recently because I kept hearing rumors that OP5T/OP6 might come out and I was afraid the value might drop to a point where re-sale value is no longer profitable..IP7+ is awesome in many ways, but my initial goal was getting LG V30 but now it seems Mate 10 is much wiser choice because of its awesome screen to body ratio + 16:9 aspect ratio which currently IMO is way better than 18:9/18:9.5 considering full app support, including youtube and so on) is that it does not have its own identity - its basically an iphone clone design wise and with it you look like a wannabe iphone user . Its awesome in performance but that identity thing sucks + they recent actions where they discontinue a model even before 6 month span is just plain ridiculous (OP3 to OP3T and then OP3T to OP5 all done within 1 year)..
zelendel said:
Yes. The 6p (minus the battery issues) is good for rom development. It will get support from 3rd parties for at least another 2 years.
I would say the one plus 3 or 3t
The nexus 6p
Any one of the Sony devices as they have a good development setup.
Click to expand...
Click to collapse
Sony is bad in development because their stupid DRM system.
El Solido said:
Sony is bad in development because their stupid DRM system.
Click to expand...
Click to collapse
Tell that to the fact that they offer how to build aosp for their devices, have worked with developers on it as well as pretty much made the theme engine that susbstratum works off of.
Will there be loses. Sure but that is the difference between aosp and using code made for the device. You don't always get all the features of the device with aosp. But that is not the point of using aosp. It's to learn.
zelendel said:
Tell that to the fact that they offer how to build aosp for their devices, have worked with developers on it as well as pretty much made the theme engine that susbstratum works off of.
Will there be loses. Sure but that is the difference between aosp and using code made for the device. You don't always get all the features of the device with aosp. But that is not the point of using aosp. It's to learn.
Click to expand...
Click to collapse
Yes, but with sony aosp you get 13% quality of camera comparing it to stock, so they are stupid.
So, according to these:
https://www.xda-developers.com/project-treble-android-o-exist-flagship/
https://www.xda-developers.com/stock-android-oreo-huawei-mate-9-project-treble/
any existing device can get project Treble support.
It doesn't have to ship with Oreo.
(although all devices that do ship with it will have to support Treble as a requirement)
Google's own Pixel and Pixel XL, as well as Huawei's Mate 9 were definitely not shipped with Oreo on board, but were made Treble compatible, which is great news.
Could we show ZTE this somehow and hopefully get them to add project Treble support?
This can help all of us tremendously (the devs mainly and us as users) and offload ZTE a lot of time with updates because they can be way faster with Treble, hopefully on any new Axon they release, not just on the Axon 7.
What are your thougts on this?
it would be a good thing, as it would extend the phone's life, but im not too positive that zte is going to implement it, sadly. but there still is a chance for that. as we know, axon M uses basically the same hardware, and if axon m is going to support the feature maybe the axon 7 will have it too. you never know with zte, as they do some things surprisingly well, while they do other things lame. time will tell.
hope it too that ZTE will join Treble soon
gogo ZTE!
regards ice
I believe there's someone from ZTE on XDA, maybe he would ask?
reas0n said:
I believe there's someone from ZTE on XDA, maybe he would ask?
Click to expand...
Click to collapse
Good Idea, gonna try to find him and tag him.
Hey @Sunn76 you may be interested in this mate!
hope it helps!
The good news is that Google got Qualcom to support Treble on their Snapdraggon 821 so they could update their Pixel. That takes care of the largest stumbling block. The bad news is that ZTE will likely need support from some other their other part suppliers and unlike Google, ZTE doesn't have the muscle to strong-arm them
Bump. Let's make this happen ZTE!
Doubt it will happen. Be lucky to get a stable O ROM at all IMO. The next Axon is where ZTE will put development effort.
I'd certainly be happy if they did do an O ROM supporting it though......
nfsmw_gr said:
Hey @Sunn76 you may be interested in this mate!
hope it helps!
Click to expand...
Click to collapse
Still reading in the background[emoji5]
And yes I will pass it on
Gesendet von meinem ZTE A2017U mit Tapatalk
@Sunn76 thanks! We really appreciate you passing on the message that the community would like support for project treble (and API2 ).
Thanks.
Sunn76 said:
Still reading in the background[emoji5]
And yes I will pass it on
Gesendet von meinem ZTE A2017U mit Tapatalk
Click to expand...
Click to collapse
Great, thanks man
Api2 for camera is important as well, If I'm not mistaken there is a thread for that already posted!
I want this phone to support everything too. It's a great phone. Camera 2 api and treble would bring ZTE to legendary status in my eyes.
However I am a realist too and I understand where money is to made and I can tell you now there's nothing at all in it for ZTE to give us anything extraordinary at all.
At the end of the day I paid half the money for a phone that I believe to be in some ways better than flagship models costing twice the amount and I realise that so my feet are firmly on the ground.
Be realistic with your expectations and don't be disappointed. There aren't any other phones as good as this when it comes to pure bang for buck and things like treble and camera 2 api also aren't enabled on phones far more expensive than ours.
RobboW said:
Doubt it will happen. Be lucky to get a stable O ROM at all IMO.
Click to expand...
Click to collapse
I'm curious what makes you doubt a stable O ROM will be available for the Axon. It's got a what I assumes is a stable LineageOS 14.1 at the moment.
They've recently come down a bit in price and I was thinking of picking one up to replace a Nexus 6P which suffered from the random reboot problem (using modified kernel, only little cores to get it stable).
I won't buy any phone unless I know it has decent custom ROM support.
What ZTE does with this phone will define how well the next phone sells. ZTE isn't mainstream enough to sell phones just out of carrier partnerships and advertisements. Word of mouth is a huge factor and if people aren't satisfied, they will not recommend the phone.
Another factor are Android news websites who will give free advertisements when axon 7 gets oreo and/or treble by reporting on it.
Gryphticon said:
What ZTE does with this phone will define how well the next phone sells. ZTE isn't mainstream enough to sell phones just out of carrier partnerships and advertisements. Wired of mouth parts a huge factor and if people aren't satisfied, they will not recommend the phone.
Another factor are Android news websites who will give free advertisements when axon 7 gets oreo and/or treble by reporting on it.
Click to expand...
Click to collapse
I agree.
I'm personally pretty satisfied, and I'd definitely buy a new Axon if it's build similarly to the Axon 7 and the price is right.
Zte has the capability to go big I think if they keep their head straight and not compromise on features or sell their devices as expensive as Samsung does for example.
So I'm confused about treble. So from what I'm reading, it will allow Android to be broken down in parts and integrated into separate roms? So for instance, with our phone, it will allow things like stock axon 7 audio to work with our roms? If not can I got a short understanding of what it involves?
pinkywinky said:
So I'm confused about treble. So from what I'm reading, it will allow Android to be broken down in parts and integrated into separate roms? So for instance, with our phone, it will allow things like stock axon 7 audio to work with our roms? If not can I got a short understanding of what it involves?
Click to expand...
Click to collapse
More or less it means what you said.
The drivers will be independently updated from the core system if I'm not mistaken and this will make updating and porting so much easier.
According to Udev the Axon 7 will not be getting Treble because it does not have a vendor partition
bkores said:
According to Udev the Axon 7 will not be getting Treble because it does not have a vendor partition
Click to expand...
Click to collapse
I don't think that means it can't get a vendor partition because it doesn't have one right now.
We've seen device repartitioning since the early Galaxy S i9000 days.
Nothing is impossible in my books unless proven.
Does this mean development may be much better, despite it being a Kirin based SoC? I would imagine so.
Ascertion said:
Does this mean development may be much better, despite it being a Kirin based SoC? I would imagine so.
Click to expand...
Click to collapse
No. That chip is still a nightmare to work with. Most developers have given up on honor. Only a few remain that are holding out hope.
The main issue is that qualcomm has spent decades working with 3rd party developers. Providing documentation, class and all kinds of tools to help them. Other chip makers are not willing to put that much money into it really.
zelendel said:
No. That chip is still a nightmare to work with. Most developers have given up on honor. Only a few remain that are holding out hope.
The main issue is that qualcomm has spent decades working with 3rd party developers. Providing documentation, class and all kinds of tools to help them. Other chip makers are not willing to put that much money into it really.
Click to expand...
Click to collapse
Welp, so much for Honor's XDA partnership. Guess I'll stick with Qualcomm in the future.
Thanks for the informative reply!
Ascertion said:
Does this mean development may be much better, despite it being a Kirin based SoC? I would imagine so.
Click to expand...
Click to collapse
Yes, honor V10 (like honor 9, mate 10, mate 10 pro, P10) are allready booting allmost fully fonctionnal AOSP treble rom, take a look on treble section in xda.
ayziaa said:
Yes, honor V10 (like honor 9, mate 10, mate 10 pro, P10) are allready booting allmost fully fonctionnal AOSP treble rom, take a look on treble section in xda.
Click to expand...
Click to collapse
To be honest, they have only gotten as far as devs have before when getting aosp to boot on a device that doesnt have it. Treble support has not been as important as it was lead to seem.
Treble has allow to boot one Rom on several devices using different soc. Plus it can use stock kernel so only system partition is flashed. It's as close as a revolution can happen in the Rom development world. Did you check the treble forum?
ayziaa said:
Treble has allow to boot one Rom on several devices using different soc. Plus it can use stock kernel so only system partition is flashed. It's as close as a revolution can happen in the Rom development world. Did you check the treble forum?
Click to expand...
Click to collapse
Oh I am well aware of what is going on over there. Now let me let you in on something. A stock based kernel would always boot on many devices. The thing is that most of the stuff doesnt work without changes. Which is still the case. If it is such a revolution then why are there not soo many developers involved?
We will just have to wait to see. Just how important it turns out to be. I like many dont think it will do a whole lot of anything really. As the updates are still pushed by the OEM anyway and you lose all the features from the OEM on AOSP. So almost no point to it really. It wont make updates any faster or for a longer time frame. IT will be like Net neutrality. Not a whole lot will change.