Related
Any devs planning on porting this to the N9? Since Jolla is based of Meego (I Think?).
l.Urker said:
Any devs planning on porting this to the N9? Since Jolla is based of Meego (I Think?).
Click to expand...
Click to collapse
They said that the N9 can be flash on sailfish but there will be no support provide by Jolla.
Plus, you can find some video with the N950 running sailfish. As the N950 have the same hardware as the N9 so it is compatible.
Please do. I heart my n9 so much...
Sent from my Nexus 7 using xda app-developers app
There'll eventually be a community port of Sailfish*, don't expect it to be very reliable/slick though, there'll be some things that never work properly.
This has all been explained time & time again, I'm not going into the back story as-to-why all this is true, the information is out there.
*not Jolla's flavour, just the stock version of Sailfish, which means it'll be quite bare-bones compared Jolla's Sailfish (initially anyway).
oh thanks for all the replies. my N9 is just collecting dust right now. whats the difference between jolla sailfish and normal one?
Swyped from my M9704
l.Urker said:
oh thanks for all the replies. my N9 is just collecting dust right now. whats the difference between jolla sailfish and normal one?
Swyped from my M9704
Click to expand...
Click to collapse
Jolla is the name of the company..
Sailfish is the name of the operating system
Do we have any news on this?
Still now, don't seen any port from Jolla..
even SDK is out..
But I really like to see Jolla port to N9.. :good:
any news about this?
and anyone has stock sailfish on n9?
Chyea!
Sent from my VZW Galaxy Note II, hyper powered via MeanBean - ICE 1.0
- Hyperion 6,200MAh Extended Battery
- Modded Otterbox to fit battery
- An S-Pen (deal with it)
Just to clarify things.
There is this company called Jolla. They make this operating system called SailfishOS which in fact is Mer.
So what is Mer? Mer is an operating system without hardware layer and UX. This means it's useless because it won't run on any hardware. You need the hardware layer which means drivers und you probably need the UX which means the GUI. This 3 parts together give you an operating system that you can use on your hardware. An example of this is SailfishOS.
If you take Mer and add the Hardware layer for the Jolla device and then the Sailfish Silica UI you get SailfishOS. The only other iteration of SailfishOS which exists is the one with the hardware layer for the Nokia N950. This will never be released as an official or supported Version.
So for all you guys waiting for a port of SailfishOS for device xyz. This won't happen. There is only one thing that could possible become reality and that's a leaked, unsupported beta image of SailfishOS for the Nokia N950/N9. Maybe this image will be the same which we saw in early demos of SailfishOS.
So the rule is as follows:
Even if you get all the linux drivers (not Android) for Mer so that you could possibly run Mer on your device you still need the UX. Jolla won't give you their Sailfish UI. You could use the Nemo mobile UI that is similar to it but the Sailfish UI will only be available on official Jolla devices.
But let's dream a little bit. If you really get Linux drivers for your device xyz and the Jolla device is out there and it has nearly the same hardware as your device it could be possible that you take all the packages that contain the Sailfish Silica UI and install them on your own device with Mer and your own hardware layer. This is possible in theory. In reality I don't think we will see a usable port that can be your daily driver.
An exchange which should help folks understand why there's no images*: http://pastie.org/private/lgldc4h3dikjkqc9nxecaq
They've said once they have one or more devices shipping, they'll probably start to open Sailfish much more, but not a minute before, for several reasons.
But that doesn't mean they'll also start to support images for 3rd-party devices, they'll probably never do that to the degree Canonical does, see the above.
*original source for that pastie
http://forums.whirlpool.net.au/forum-replies.cfm?t=1941044&p=48#r950
Jolla will be ported to N9. It won't hava all the functions, that on the Jolla device (for ex. no Voice control...anyway who needs it?), but it will be officially released around september/october 2013. So be patient
Giorgio84 said:
Jolla will be ported to N9. It won't hava all the functions, that on the Jolla device (for ex. no Voice control...anyway who needs it?), but it will be officially released around september/october 2013. So be patient
Click to expand...
Click to collapse
For real? or just your wish?
Is there an ETA?
Is there an ETA on when someone could make some early progress on this project? I'm worried that people are losing so much interest that a preview version of Sailfish running on the N9 might be a great idea to get people wanting more of the Meego successor.
That way, people would be falling in love with Sailfish and since it would have a significant spec-bump over the N9, people would be willing to buy it for the screen/display improvement, the "other half," and the great UI.
Giorgio84 said:
Jolla will be ported to N9. It won't hava all the functions, that on the Jolla device (for ex. no Voice control...anyway who needs it?), but it will be officially released around september/october 2013. So be patient
Click to expand...
Click to collapse
Do you have any source for this info? Because there is no official announcement that hit my attention.
hacker00740 said:
Is there an ETA on when someone could make some early progress on this project?
Click to expand...
Click to collapse
As always "when it's done". Please stop asking for ports. Just wait until Jolla came out with there first device. I'm sure there will be ports and adaptions all over the place once the Software gets in the hands of the right guys. And this community or t.m.o is prbably the first place to know it. But asking for it every second won't let that happen earlier.
Hello friends ..
No new news??
SDK when the operating system was released.
Test video of the operating system on it is N9. Why not port the operating system to handset N9 its wonderful ...
Please help developers...
maxomid said:
Hello friends ..
No new news??
SDK when the operating system was released.
Test video of the operating system on it is N9. Why not port the operating system to handset N9 its wonderful ...
Please help developers...
Click to expand...
Click to collapse
The SDK didn't include the full version of the Sailfish OS. It only contains a basic emulator for apps. So until Jolla releases a phone with Sailfish, it is impossible to port
Sent from my GT-N7100 using xda app-developers app
tbo-art said:
The SDK didn't include the full version of the Sailfish OS. It only contains a basic emulator for apps. So until Jolla releases a phone with Sailfish, it is impossible to port
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the answer
Will be released in full when it is SDk?
Why developers do not work on this phone Nitdroid ROM Port ... Time to full Android experience on these phones ...
http://forum.xda-developers.com/showthread.php?t=2342102
Hi, i want to share this post from a Jolla engineer giving tips to start porting Sailfish:
I'm pretty sure I phrased it a bit different So, both the N900 and N9 have the problem of having binary blobs, which Jolla is not allowed to distribute, and almost certainly never will be. The N9 additionally has the problem of having an older kernel than the N900 -- old enough that it's starting to cause problems. That's the reason why I probably mentioned N900.
As for Nemo and N9, Nemo is a community followup project of MeeGo, and as such inherited basic N9 hardware adaptation, and the right to redistribute those binary blobs. So, if you as user take a Nemo image and put Jolla stuff in there it works -- but we as Jolla can't do that.
Another problem is that the old N9 adaptation is based on X11, while we are using Wayland. We do have a proof of concept Wayland stack up on N9 (available through Nemo as well), but it has its fair shair of problems.
That we're using Wayland makes your suggestion of porting Sailfish libraries to Harmattan hard as well: Harmattan is an X11 stack (same in the different direction: you can't use a Harmattan binary on Sailfish. If you have the source porting is trivial -- unless it's using meegotouch. But if you only have a binary it won't run. In theory something hacking with xwayland might be possible, but that's pretty crazy, and a sailfish port/rewrite would almost certainly be the better option)
So, it should be pretty clear by now that we will not do N9 images. What needs to happen for community to be able to do the port? Easy: Get involved in Nemo. I mentioned that several times, though so far nobody showed interest.
It's mainly 3 areas that need work:
- finish port to the 3.5 kernel we started. The required tasks are in Nemos Bugzilla
- start fixing bugs in the Wayland proof-of-concept for N9
- reverse engineer hardware components where no driver exists, and do drivers (like GPS)
So, it's a hard task, but not impossible. The Nemo community and Jolla provided a very good starting point with Nemo, now it's up to community members to step up, and continue.
SOURCE: TMO
Can someone give me a tl;dr technical reason that Gonk doesn't work on every phone that runs Android? Isn't it using the Android foundation? I'm sad that my Droid 1 isn't on the compatibility list .
I am a coder, but not a kernel/system developer... so that should should tell you how 'technical' to make your answer.
Well,
First, Gonk it's modified by Mozilla Developer, and Mozillians (Contributors), if it works in any X devices it doesn't means that your devices runs it without any issue. It's the same thing with the Ports of FirefoxOS to other devices, for example, i made the Port for the S3 i9300, it doesn't means that the S3 AT&T, Verizon or other devices with similar hardware can runs my build, are different targets.
If you have something in you device, you need Port it from sources (scratch), good luck man.
lol wut?
Allow me to rephrase: Linux already boots on every Android device because Android uses Linux. Since "Gonk consists of a Linux kernel and userspace hardware abstraction layer (HAL)" (Wikipedia article on Firefox OS, Section: Gonk (gah hate this site, can't post links)), why doesn't every Android phone boot Gonk also? Can't we use Android's Linux/HAL as is? What is there to port? Do you mean compile? Is the only reason I can't have Firefox OS on my Droid 1 simply because nobody has compiled it? I understand compiling can be a freaking pain in itself, but it's not the same as porting.
Sorry if this seems nubby.
I've done some easy searching and found what might be the actual cause of the Xperia Z3 not being announced as getting Android N with other devices from the Sony line.
Even though we have Android 7.0 previews available and it works fine with a few software bugs that need to be ironed out, the Xperia Z3 will not be getting official Android N.
And heres why:
The problem lies in Google and their Android N requirements.
You might be asking, what do you mean by requirements the device ran the previews just fine!?
Well, Google has introduced new encryption methods in Android N which have certain hardware requirements.
The Snapdragon 800/801 don't have support for some of these newer encryption methods.
Another question you might be asking is, well we don't need these encryption methods, but Google says otherwise.
Their policy is that their encryption methods must be fully running by the time the device setup is done.
So the actual reason for the Z3 not getting Android N is both technical and legal.
In the end, its actually not Sony's fault, Sony is just following the rules which Google put.
Although I don't see any problems for Qualcomm releasing the drivers needed for further development.
We will probably see unofficial Android N on our devices, but at the moment it seems like a far stretch due to Qualcomm not wanting to release drivers.
Sources:
Android Authority
It's exactly full-disk encryption and GG haves Compatibility Definition Document (CDD) for all devices need to run Android N. So easily, Snap 800/801 have feature full-disk encryption, but with this, they do pass Compatibility Test Suite (CTS) but don't meet the CDD because read/write speed. Snap 805 is newer and have module for this feature, so can make it faster.
But, if Sony open our kernel, Snap public your driver, custom rook does not need full-disk encryption at all.
That's all I found about this.
This is just one of many reasons why we can't get N. Opengl 3.1 or Vulkan is also required for certification which only SD 805 and later have. Basically all devices older than SD 805 are sol for future updates. Now Sony could release stockbased build in a zip format through dev program without gapps which wouldn't cause issues with Google
Lets try and keep it in one thread
http://forum.xda-developers.com/z3/general/xperia-z3-wont-android-n-t3446158
Thread closed.
Google has made it mandatory for devices launched with Android Oreo to have Linux Kernel 4.4 and Project Treble but
Older Android devices released prior to Android O but that will be upgraded to Android O can continue to use their original base kernel version if desired.
Click to expand...
Click to collapse
From AOSP/Google (I can't yet put links to source as I don't have 10 posts yet)
Which includes our OnePlus 3T. As OnePlus has already said Android Oreo will be the last major update for our device (officially) we might not get Project Treble (like Nexus 5X and 6P) and Linux kernel 4.4 (a major update from our current 3.18) making it very difficult for the developer community to port future updates as Android P and above might only have Treble base unlike Android Oreo.:crying:
That would be a another bummer after there limited support announcement for 3t. For know I keep my fingers crossed for a better message on this front.
Still if images are released for AOSP you still will get development for our phone though. ?
Goku80 said:
Still if images are released for AOSP you still will get development for our phone though. ?
Click to expand...
Click to collapse
Exactly. Honestly I don't see why Project Treble matters to the average ROM user. I just want my phone to work and perform well and have a decent battery life. Besides that I don't really care. Currently I have a Nexus 6 and just replaced the battery in it but I'm perusing the forums for various devices (this was one of them) that I may be interested in. I want to see how the development community is for each one before I decide. Reason I may be considering this over the OP5 is I have heard bad things about the screen and jelly scrolling.
rjmxtech said:
Honestly I don't see why Project Treble matters to the average ROM user.
Click to expand...
Click to collapse
You don't see why?
Let me help you out:
Ars Technica said:
Custom ROMs shouldn't need to be painstakingly hand-crafted for individual devices anymore—a single build should cover multiple Treble devices from multiple manufacturers. Imagine the next time a major new version of Android is released. On Day One of the AOSP code drop, a single build (or a small handful of builds) could cover every Treble device with an unlocked bootloader, with a "download Android 9.0 here" link on XDA or some other technical website.
Click to expand...
Click to collapse
UltimateGoblin said:
You don't see why?
Let me help you out:
Click to expand...
Click to collapse
I totally agree this !
UltimateGoblin said:
You don't see why?
Let me help you out:
Click to expand...
Click to collapse
Exactly! Development and porting of Custom ROMs will become easier than ever before and porting of future versions of Android will also become way lot easier (if possible at all as future versions of Android might become completely dependent on Project Treble unlike Android Oreo which is compatible with both)! And porting Project Treble is very very difficult if not impossible (unless you are the Silicon Manufacturer) !
So lets together spread the information about the importance of Project Treble and pressure OnePlus to provide Project Treble with #WeWantTreble
We shall Never Settle!
#WeWantTreble
Sent from my ONEPLUS A3003 using XDA Labs
Lets spam Carl Pei twitter with questions regarding this..
(Well not really spam, that would be rude, more like a lot of people asking him same question in shorts period of time)
I could be wrong but I think Treble integration is likely more on the SoC vendor than it is the OEM making the device. While they work hand-in-hand, I kind of doubt QCOM is going to make a Treble-compatible BSP for the 821 at this point.
Lyokacanthrope said:
I could be wrong but I think Treble integration is likely more on the SoC vendor than it is the OEM making the device. While they work hand-in-hand, I kind of doubt QCOM is going to make a Treble-compatible BSP for the 821 at this point.
Click to expand...
Click to collapse
i have red somewhere that pixel devices support treble. Same Soc, should have supported. idk.
From my experience as a Junior Android developer and reading the papers about the project treble, i could say that if there is a little group op3t developers who want this, this can be possible.
UltimateGoblin said:
You don't see why?
Let me help you out:
Click to expand...
Click to collapse
Interesting. But I assume there would still be issues even if they tried to make a universal solution.
Lyokacanthrope said:
I could be wrong but I think Treble integration is likely more on the SoC vendor than it is the OEM making the device. While they work hand-in-hand, I kind of doubt QCOM is going to make a Treble-compatible BSP for the 821 at this point.
Click to expand...
Click to collapse
Treble is mostly dependent on the SoC vendor as Project Treble is all about a vendor implementation with a vendor interface layer connecting it to the Android OS Framework unlike before when (parts of) Android OS Framework had to be compiled along with the vendor implementation as there was no interface layer in between them.
But Google Pixel which is also on the Qualcomm Snapdragon 821 as the OnePlus 3T has Project Treble but I also doubt how did they manage to get the silicon specific code required for implementing Project Treble during Developer Previews as generally the source code of Developers Previews is available only to Google and Qualcomm generally doesn't share the uncompiled silicon specific code even with OEMs (I might be wrong and Qualcomm and Google might be having partnership).
As there is already Project Treble for Qualcomm Snapdragon 821 (Google Pixel) I think it might be upto OnePlus to choose if it wants to implement it.:fingers-crossed:
DelicatePanda said:
Treble is mostly dependent on the SoC vendor as Project Treble is all about a vendor implementation with a vendor interface layer connecting it to the Android OS Framework unlike before when (parts of) Android OS Framework had to be compiled along with the vendor implementation as there was no interface layer in between them.
But Google Pixel which is also on the Qualcomm Snapdragon 821 as the OnePlus 3T has Project Treble but I also doubt how did they manage to get the silicon specific code required for implementing Project Treble during Developer Previews as generally the source code of Developers Previews is available only to Google and Qualcomm generally doesn't share the uncompiled silicon specific code even with OEMs (I might be wrong and Qualcomm and Google might be having partnership).
As there is already Project Treble for Qualcomm Snapdragon 821 (Google Pixel) I think it might be upto OnePlus to choose if it wants to implement it.:fingers-crossed:
Click to expand...
Click to collapse
Friggin' derp. How did I forget about the Pixel?
That being said, we'd still need to see how its implemented on the Pixel...As far as I know Treble also relies in a specific type of device partitioning which may be problematic for existing device adaptations. The Pixel phones already used the /vendor partition how it's supposed to be used so adapting Treble is almost a non-issue. I don't think our phone uses the same partition layout.
As of open beta 16 Oxygen OS we didn't get the new v4.4 kernel and also project Treble:crying:
DelicatePanda said:
As of open beta 16 Oxygen OS we didn't get the new v4.4 kernel and also project Treble:crying:
Click to expand...
Click to collapse
That sucks .. even for OnePlus 5?
why the heck Carl is not replying officially on it, anywhere???
To all those who want to know more about Project Treble please use this thread to discuss about it.
What is Project Treble?
Ans. Treble is the most significant low-level change to the Android platform to date. To simplify heavily, it separates the vendor implementation from the Android framework in an effort to avoid lengthy waits for updates. . Let’s break things down a bit more:
The full update process to bring a new Android version to devices is a long and complex topic.
The “vendor” usually refers to silicon-manufacturers such as Qualcomm, but can also refer to the maker of any other proprietary hardware found in a device. The “device maker” or “OEM” usually needs to wait for the vendor to update their code so the proprietary hardware works with the Android OS framework in a newer version of Android.
However, what is happening with Project Treble is that Google is requiring that any vendor-specific code be separated from the Android OS framework and instead live in its own vendor implementation. Usually this means that there is now a separate /vendor partition on Treble-enabled smartphones that contains a bunch of HALs (Hardware Abstraction Layers).
Furthermore, vendors must implement code that lets the Android OS framework communicate with HALs in a standardized way. This is done via HIDL (HAL Interface Definition Language). With this in place, an OEM can work on an Android update without having to wait on vendors to update their HALs. Theoretically, this should speed up the entire Android update process as vendors can update their code at any time through the Play Store.
For indepth information check out this pagehttps://www.androidauthority.com/project-treble-818225/
Devices with Treble support:
- Essential PH-1
- Google Pixel
- Google Pixel XL
- HTC U11 Plus
- Huawei Honor 8 Pro
- Huawei Mate 9
- Huawei Mate 10 Pro
- Sony Xperia XZ1
- Sony Xperia XZ1 Compact
- Asus Zenfone 4 (ZE554KL)
- Honor V10
- Huawei P10/ P10 Plus
Devices which will ship with Android 8.0 Oreo will be Treble compatible by default.
Older devices will become treble compatible if the OEM creates a vendor partition via OTA update, like the Honor 8 Pro.
Custom Roms:
As of now @phhusson is working hard to make his AOSP rom boot as a fully functional rom on all the Treble supported devices, go check out the rom thread here https://forum.xda-developers.com/pr...evelopment/experimental-phh-treble-t3709659"]
Check Treble Compability
Open a terminal app on your device and simply type the following command:
getprop ro.treble.enabled
Click to expand...
Click to collapse
If it returns a boolean value true, your device supports Treble and if false it doesn’t.
[NOTE: New devices with Treble support are launching so its not possible for me to update the supported device list, so they'll not make their name on my list, but you can surely ask about your device on the discussion thread]
My understanding of Treble is, from the *big picture* anyway, that the responsibility for hardware access shifts from Google to the individual device mfgs.
The hope for us is that new versions of Android can be distributed much more rapidly, because testing of new hardware (or changes to existing hdw) won't have to wait for the new OS to be done, and that the interface to the hdw will be separate from the OS.
Another hope would be that a devices 'life span' would increase? (or at least stay current longer).
AsItLies said:
My understanding of Treble is, from the *big picture* anyway, that the responsibility for hardware access shifts from Google to the individual device mfgs.
The hope for us is that new versions of Android can be distributed much more rapidly, because testing of new hardware (or changes to existing hdw) won't have to wait for the new OS to be done, and that the interface to the hdw will be separate from the OS.
Another hope would be that a devices 'life span' would increase? (or at least stay current longer).
Click to expand...
Click to collapse
Treble means separating the vendor source from the software source, the treble devices will have a separate vendor partition, in which the vendor source will be. Now the manufacturers will only require to make the Software bug free so that the user dosent face any problems in day to day usage. From @phhussons AOSP treble rom we can get a clear picture that by separating the vendor source, the Treble based AOSP roms will run on any Treble compatible device regardless of the SOC/hardware configuration.
venom928 said:
Treble means separating the vendor source from the software source, the treble devices will have a separate vendor partition, in which the vendor source will be. <snip>
Click to expand...
Click to collapse
Ah yes that makes sense, it's not only the hardware source (vendor specific), it's also the vendors software (their mods and bloatware) that will be in the separate partition.
It really does sound as though this should speed up the time it takes for users to get updates of all kinds. It also seems pretty certain, non-Treble enabled devices will fall by the wayside. Doesn't seem there's any way around that?
AsItLies said:
Ah yes that makes sense, it's not only the hardware source (vendor specific), it's also the vendors software (their mods and bloatware) that will be in the separate partition.
It really does sound as though this should speed up the time it takes for users to get updates of all kinds. It also seems pretty certain, non-Treble enabled devices will fall by the wayside. Doesn't seem there's any way around that?
Click to expand...
Click to collapse
For non-treble devices the only way is that the OEMs must release an OTA update which will create a separate Vendor partition, but OEMs won't do(except some recent flagships) that bcz they want sales of newer devices with Treble support. As far as time is concerned, suppose it takes 2-3months for an OEM to build a fully bug free update, but it will require 3-4weeks for the OEM to build that same update
venom928 said:
For non-treble devices the only way is that the OEMs must release an OTA update which will create a separate Vendor partition
Click to expand...
Click to collapse
Yes, it seems the consensus is that mfg's won't risk bricking the phones by doing that kind of an OTA update? We'll see fairly soon what they'll do with the older devices.
It's good that google is calling the shots with this and is insisting new Oreo devices have it. It's bad though that devices just a few months old that cost mucho bucks may go without it.
AsItLies said:
Yes, it seems the consensus is that mfg's won't risk bricking the phones by doing that kind of an OTA update? We'll see fairly soon what they'll do with the older devices.
It's good that google is calling the shots with this and is insisting new Oreo devices have it. It's bad though that devices just a few months old that cost mucho bucks may go without it.
Click to expand...
Click to collapse
The honor 8 pro got Treble via OTA because it was one of the best selling device, but some OEMs will prefer not to do that so that customers will shift to newer devices. Like OnePlus could have easily added Treble to atleast 5/5T but they thought of not doing it, just depends upon the OEM
venom928 said:
The honor 8 pro got Treble via OTA because it was one of the best selling device
Click to expand...
Click to collapse
Wow, I did not know that, thanks. I better read more of the Treble threads to keep up to date
AsItLies said:
Wow, I did not know that, thanks. I better read more of the Treble threads to keep up to date
Click to expand...
Click to collapse
yep surely
Mate 9 as well
AsItLies said:
Wow, I did not know that, thanks. I better read more of the Treble threads to keep up to date
Click to expand...
Click to collapse
Mate 9 got treble as well with the Oreo update, major repartitioning as well.
revjamescarver said:
Mate 9 got treble as well with the Oreo update, major repartitioning as well.
Click to expand...
Click to collapse
Mate 9 is in the list bro, check OP
revjamescarver said:
Mate 9 got treble as well with the Oreo update, major repartitioning as well.
Click to expand...
Click to collapse
Thanks Neighbor. Huawei is rapidly moving to the top of my list of phone mfg to buy. It doesn't look like the kirin processors have much los support, but with treble... well, it seems previous prerequisites are being turned upside down.
For sure, when one evaluates (buying) a phone, many factors are relevant. But for most (if not all) of us, how long the phone will stay up to date is probably at the top of that list.
Hope the other mfg's follow Huawei's lead here, else we'll have a lot of recently mfg phones with outdated sftwr soon.
AsItLies said:
Thanks Neighbor. Huawei is rapidly moving to the top of my list of phone mfg to buy. It doesn't look like the kirin processors have much los support, but with treble... well, it seems previous prerequisites are being turned upside down.
For sure, when one evaluates (buying) a phone, many factors are relevant. But for most (if not all) of us, how long the phone will stay up to date is probably at the top of that list.
Hope the other mfg's follow Huawei's lead here, else we'll have a lot of recently mfg phones with outdated sftwr soon.
Click to expand...
Click to collapse
Huawei is the 3rd most fastest growing OEM after Apple and Samsung. What stops me from buying a Honor Device is the Kirin SOC and apps like Google Camera port dosent work on the devices except devices with Snapdragon SOC, so will wait for a device with the specs like the Mi A1 and a 18:9 display
venom928 said:
Huawei is the 3rd most fastest growing OEM after Apple and Samsung. What stops me from buying a Honor Device is the Kirin SOC and apps like Google Camera port dosent work on the devices except devices with Snapdragon SOC, so will wait for a device with the specs like the Mi A1 and a 18:9 display
Click to expand...
Click to collapse
Very good point. So even with Treble, which SOC (the phone has) will still be relevant in some respects. I have a G6 and think a wide angle lens is da bomb, but could easily do without all the glass 'bling'.
Kirin SoC
venom928 said:
Huawei is the 3rd most fastest growing OEM after Apple and Samsung. What stops me from buying a Honor Device is the Kirin SOC and apps like Google Camera port dosent work on the devices except devices with Snapdragon SOC, so will wait for a device with the specs like the Mi A1 and a 18:9 display
Click to expand...
Click to collapse
Nothing at all wrong with the Kirin SoC, performance is on par with the Qualcomm SoC, only real downfall is that Huawei doesn't sell the Kirin to other oems, otherwise it would be more widespread. The Kirin 970 with its built in NPU and and gigabit LTE modem is going to give the Qualcomm 835/845 a run for their money. Of course the port of the new Google camera app is not going to give you more than the basic functionality as it was written specifically for Google pixel devices (it doesn't give you all the features on older Google or snapdragon devices either), I installed the port on my mate 9 and it was acceptable for basic camera functions but no matter what you do you're never going to get a port of something written for another device to have the same features or performance as the stock app written for your device.
revjamescarver said:
Nothing at all wrong with the Kirin SoC, performance is on par with the Qualcomm SoC, only real downfall is that Huawei doesn't sell the Kirin to other oems, otherwise it would be more widespread. The Kirin 970 with its built in NPU and and gigabit LTE modem is going to give the Qualcomm 835/845 a run for their money. Of course the port of the new Google camera app is not going to give you more than the basic functionality as it was written specifically for Google pixel devices (it doesn't give you all the features on older Google or snapdragon devices either), I installed the port on my mate 9 and it was acceptable for basic camera functions but no matter what you do you're never going to get a port of something written for another device to have the same features or performance as the stock app written for your device.
Click to expand...
Click to collapse
I agree that the Kirin Processors are good, and the reason is Kirin is Huawei's home made processor so the pairing between Hardware and Software is perfectly optimisez for better performance and as far as Better Processing is concerned, after Apple Qualcomm holds the 2nd position no doubt, yeah in near future Kirin might surpass Qualcomm interms of performance no idea.
As far as the ported app is concerned I prefer stock android/custom roms over stock roms(MIUI/EMUI) and if someone ports the stock huawei camera for Los/RR running on Huawei devices itself, I'll surely go with a Kirin device but right now thats not available so after installing a custom rom I'll prefer Google camera app, if not the ported one, I'll go with the one available in Apkmirror, though this is my own preference as I'm addicted to using stock android and google apps suite, lets see how much development the Honor 7X gets, if it gets Treble support via OTA I'll go with it else the Mi A1 as of now is my 1st choice
I'm wondering, and the answer may be 'We don't know yet', but...
Many of us have used custom ROM's to avoid using an OEM's UI, bloatware, etc. Because Treble enabled phones will have a 'Vendor' partition (which will include these UI's etc), will that then mean the mfg's specific stuff can't really be (completely) removed the way an after market ROM does?
Of course, there's always ways of disabling mfg stuff, but Roms like Los just do it all in one fell swoop (much easier).
Do we know at this point how this will work with Treble?
Cheers and Happy New Year
AsItLies said:
I'm wondering, and the answer may be 'We don't know yet', but...
Many of us have used custom ROM's to avoid using an OEM's UI, bloatware, etc. Because Treble enabled phones will have a 'Vendor' partition (which will include these UI's etc), will that then mean the mfg's specific stuff can't really be (completely) removed the way an after market ROM does?
Of course, there's always ways of disabling mfg stuff, but Roms like Los just do it all in one fell swoop (much easier).
Do we know at this point how this will work with Treble?
Cheers and Happy New Year
Click to expand...
Click to collapse
The SOC source code will reside in the vendor partition, for example The Pixel XL has SD835 so the source code of the SOC will be there in itz Vendor partition. So if you are using a Treble enabled device such as the Huawei Mate 9 which has its own custom UI, if u flash a custom rom on it, the stock OS will get completely removed and the run ROM will run on it.
The Mgf's UI is a part of the system nd not of the vendor partition.
I am planning to buy Honor 7x, I found a thread on 7X forum which has Mount points and partition layout details for 7x. In the details, i can see below line, does this mean that phone supports Treble once updated to Oreo?
lrwxrwxrwx 1 root root 21 Dec 24 10:46 vendor -> /dev/block/mmcblk0p47
Orignal thread link
https://forum.xda-developers.com/honor-7x/development/mount-partition-layout-profile-xml-t3727990
Thanks:good: in advance!!
indigo110 said:
I am planning to buy Honor 7x, I found a thread on 7X forum which has Mount points and partition layout details for 7x. In the details, i can see below line, does this mean that phone supports Treble once updated to Oreo?
lrwxrwxrwx 1 root root 21 Dec 24 10:46 vendor -> /dev/block/mmcblk0p47
Orignal thread link
https://forum.xda-developers.com/honor-7x/development/mount-partition-layout-profile-xml-t3727990
Thanks:good: in advance!!
Click to expand...
Click to collapse
It is evident from past experiences that the Honor 7X might get Treble via OTA update as the case was with Honor 8 Pro. The Honor 7X's source code got released a few weeks ago and I got some info that the Open Kirin team will also support the 7X so I guess the Open Kirin team will also release a Treble supported rom