Related
5000 of the attendees of the BUILD conference were given Sammy Tablets with Windows 8. This is most likely the only public source of the ARM version of Win 8. Please upload what you can, within legal limits...
That Samsung Tablet wasn't ARM-based I think.
Nope it is not arm
I would love an arm dump to get it on touhpad via making install.wim...
slimshady322 said:
That Samsung Tablet wasn't ARM-based I think.
Click to expand...
Click to collapse
It was nVidia based. I'll post the article link in a sec.
Core i5, that was told at conference.
No its not
Its an intel i5 no arm on the Samsung model
daweiteh said:
It was nVidia based. I'll post the article link in a sec.
Click to expand...
Click to collapse
Nvidia Tegra 2 and above are ARMv7+ Chips. All Nvidia does it put their name on it. But those are ARMv7 chips. This goes for all the current and future mobile devices. If they are using i5 Intel with the builtin Intel GPU then that's a different story and it's not Nvidia. It's Intel. As far as I know Nvidia's mobile devices are going to be entirely ARM based.
As a matter of fact even Intel uses ARM to a lesser degree with memory managment chips for example. Everyone uses ARM to be specific. There isn't really a chip manufacturer out there that does not deal with ARM Holdings in some form. I'm very interested in putting Windows 8 on ARM so I'm following these threads closely myself. I have yet to see the ARM build and being a dev for MS myself, I have been testing Windows 8, but when I have conference calls with Microsoft and I ask for ARM support, they are telling me the setup is not done yet most likely and the support just isn't ready for developers yet. Stay tuned for sure. It should be a higher build number than 8200 I think.
Sent from Atrix4G Mobile
RedLineJoes said:
Nvidia Tegra 2 and above are ARMv7+ Chips. All Nvidia does it put their name on it. But those are ARMv7 chips. This goes for all the current and future mobile devices. If they are using i5 Intel with the builtin Intel GPU then that's a different story and it's not Nvidia. It's Intel. As far as I know Nvidia's mobile devices are going to be entirely ARM based.
As a matter of fact even Intel uses ARM to a lesser degree with memory managment chips for example. Everyone uses ARM to be specific. There isn't really a chip manufacturer out there that does not deal with ARM Holdings in some form. I'm very interested in putting Windows 8 on ARM so I'm following these threads closely myself. I have yet to see the ARM build and being a dev for MS myself, I have been testing Windows 8, but when I have conference calls with Microsoft and I ask for ARM support, they are telling me the setup is not done yet most likely and the support just isn't ready for developers yet. Stay tuned for sure. It should be a higher build number than 8200 I think.
Sent from Atrix4G Mobile
Click to expand...
Click to collapse
Nvidia makes the tegra line of arm socs as well as chipsets for x86 and gpus for pcs. lets try not to get their products confused. Nvidia does a lot more than just "put their name on it" They tape out the chip and add their gpu to it. It's a custom implementation of an arm chip based loosely around the "standard" that arm creates. The series 7 slate that was passed out at build is the same series 7 that is going on sale later this month with an i5 in it, it also uses intel graphics. It's x86 aka not arm. Because there is no standard off the shelf arm system I highly doubt they will release any sort of preview arm build. Most likely it will take many many system dumps and a lot of work to get arm windows 8 working fully on devices that did not ship with it.
---------- Post added at 01:10 PM ---------- Previous post was at 12:54 PM ----------
Remember Texas Instruments and Qualcomm are also throwing their hats into the windows 8 ARM(s) race. Don't count them out. Likely each device will have a version of windows compiled specifically for it ala windows mobile. I just don't see any real way around that. Unless they give the different arm chips special drivers and build them all in - but that would make for less efficiency and a waste of storage and more complexity considering that no one is going to be putting a windows 8 dvd into their tablet to install the arm version ever ever ever. I'm thinking this will all be precompiled specifically for each device and it will likely lack certain features like device manager and complicated driver handling controls. This is going to be a pain in the ass.
It is not confusing because I was only speaking on Nvidia ARM SoCs, not anything else they do. Ye have little faith if you think Microsoft can't bring a mutli kernalized version of Windows 8 to market for all the different platforms similar to what Linux/Android already does.
The big buzz about Windows 8 when we first started talking about it with Microsoft was "kernalized versions with ARM support". That's right from the horses mouth. I sure hope they deliver on that more than anything else. And seeing as how I help make the OS what it is, i'll be testing the functionality eventually. Due to NDA you aren't allowed to say much about it though until these types of releases become available to the general public and developers. Then we can discuss what works and what doesn't with the people who plan to actually use it and make applications for it.
Sent from Atrix4G Mobile
I just heard that Vulkan API is coming to mobile and it is supporting PowerVR chips like the one we have on the phone.
(PowerVR G6430). Some people say on the ZENTALK forum that that's why it takes so much freaking time for Asus to implement Marshmallow as they are busy incorporating the API on the phone.
If this is true just image the gigantic boost it will give to our phones! (just watch on Youtube or search on Google for more information about Vulkan API)
If Vulkan API is implemented at our phone it would be fantastic. Hope Asus will work on the API and make the best for our phone, let's see in a couple of months of so
Too good to be true man, too good to be true.
hi, I'm very interested in everything about vulkan since i could see some videos about it. But my knowledge about api, android and rom's is not that good, so i would thank you if i could get some answers.
1 - Is this implementation of API a work for ASUS or Intel?
2 - Since i saw that PowerVR Rogue has now SDK(i dont know what it is) for Vulkan, Is ANYONE able to make a custom rom that could use Vulkan?
3 - I've heard that Android N will have native support for Vulkan. Does it mean that if i download a custom rom, like a cyanogenmod, for Android N to my Zenfone 2 i will have the benefits of using Vulkan?
4 - Does anyone know if that Galasy S7 that had 135k+ on antutu was using Vulkan? Because my Zenfone 2 is a great phone and only scores 65k, it's scary to thing that a S7 should have more than the double of hardware capacity that my Zenfone has. I thing that should be because of vulkan, but i need to hear it from someone who knows what's talking.
I hope to get answers for this questions. Thank you all.
SSJMatt said:
)Some people say on the ZENTALK forum that that's why it takes so much freaking time for Asus to implement Marshmallow as they are busy incorporating the API on the phone.
Click to expand...
Click to collapse
Sorry, that's not how ASUS usually manages fixes and updates. That would take time and money and we've already spent our money so they have nothing to gain, therefore nothing will happen. Only future customers are a priority for ASUS.
A happy ASUS customer is one with low expectations.
Well, at least It'd give Asus a good excuse for being so late...
Vulkan is something that would need to be implemented at the OS level on Android (mainly the kernel, no idea what other bits Google is including in the rest of the OS). And support for each hardware would need to be provided by the OEM or manufacturers. It MAY be possible for a custom ROM to implement Vulkan support in some fashion in a current version of Android (harder and more "impossible" things have been accomplished) but it's not likely due to too many technical challenges. Besides, it wouldn't happen until after Android N is released and the AOSP code is posted. Only then would someone attempt to backport Vulkan.
I'm not 100% sure, but I do believe that Vulkan support will be a requirement by Google for devices to run Android N. So if Asus does plan on upgrading the phones then they will need to include a kernel for the hardware that supports Vulkan and those drivers would come from Intel. So the chance of the Zenfone supporting Vulkan is 100%, provided Asus upgrades it to N.
SSJMatt said:
I just heard that Vulkan API is coming to mobile and it is supporting PowerVR chips like the one we have on the phone.
(PowerVR G6430). Some people say on the ZENTALK forum that that's why it takes so much freaking time for Asus to implement Marshmallow as they are busy incorporating the API on the phone.
If this is true just image the gigantic boost it will give to our phones! (just watch on Youtube or search on Google for more information about Vulkan API)
Click to expand...
Click to collapse
So is the VULCAN API present in the M update?
Is Vulkan something like the Mantle for Desktops?
EDIT:
Vulkan Drivers for Nexus Player
Google’s Android Image
As part of the Android N Developer Preview 2 release, Google released an Android N image for the Nexus Player that includes Vulkan drivers. You can find out more about the Android N Developer Preview here and can download the image here. As this image is officially supported by Google, we recommend using it for Vulkan Android development.
Click to expand...
Click to collapse
https://community.imgtec.com/developers/powervr/vulkan/
There is two possibilities:
1- Vulkan added in Android N's mainline code, and CM14 (maybe) will do this too.
2- Vulkan driver will be only in manufacters Android N's source. In this case, will be needed to be backported.
In both possibilites, isnt impossible to do it, even without Asus help. But would be awesome if some official MM give it to us (not in the first version, obviously).
Its GPU manufacturer job to implement vulkan, they provide the drivers to OEM manufacturer implement it on their otas. Nvidia already did that on latest MM update to shield TV and shield tablet.
Download links here: http://llabtoofer.com/2016/10/09/pixel-and-pixel-xl-system-image/
Any dev willing to port Google Pixel android ROM to Nexus 6?
konradit said:
Download links here: http://llabtoofer.com/2016/10/09/pixel-and-pixel-xl-system-image/
Any dev willing to port Google Pixel android ROM to Nexus 6?
Click to expand...
Click to collapse
Already tried to dump APKs, almost everything is for arm64, i think ports will not be such a thing. The included launcher and wallpaper picker are 32bit tho, but are the same as those leaked before, with a different signature tho
Unfortunate if true. I was curious what might be ported to the N6.
Someone can Im sure, and hopefully integrate Google assistant into our roms, that's the only thing I want, pixel launcher is already on my phone
Does anybody have an extractable system image, where I can pull alarms, ringtones, notifications and the SystemUI and Framework? I wouldn't mind getting ahold of that new battery icon.
I was able to unrar the images posted via that link and was able to simply ext4fuse mount them. No need to run through sim2img it appears. The media ringtones and notifications appear to be the same files that were released back in August.
file *.img
system.img: Linux rev 1.0 ext4 filesystem data, UUID=bbcb9ad2-245d-035f-a549-7d500312efe1 (extents) (large files)
system_other.img: Linux rev 1.0 ext4 filesystem data, UUID=da594c53-9beb-f85c-85c5-cedf76546f7a, volume name "system" (extents) (large files)
@Yasharkhan: I don't think Google Assistant will ever appear on the Nexus 6, for a very simple reason: the 32/64-bit divide. The Pixel/Pixel XL devices run a 64-bit Snapdragon 821 while the Snapdragon 805 in the Nexus 6 is only a 32-bit processor. 64-bit processors can run 32-bit apps, as evident by the Pixel launcher being a 32-bit app in a 64-bit system, but 32-bit processors cannot run 64-bit apps. If Google makes the Google Assistant a 64-bit app and does not create a 32-bit version, even if we could install it on the Nexus 6 it won't run. Since the Assistant is not an open source app, no one would be able to build a 32-bit version that would run on the Nexus 6.
I'd like to be wrong on this one, but the Assistant is an exclusive that only the 5X and 6P are going to get, if Google decides to provide it.
absolutely correct!
Strephon Alkhalikoi said:
@Yasharkhan: I don't think Google Assistant will ever appear on the Nexus 6, for a very simple reason: the 32/64-bit divide. The Pixel/Pixel XL devices run a 64-bit Snapdragon 821 while the Snapdragon 805 in the Nexus 6 is only a 32-bit processor. 64-bit processors can run 32-bit apps, as evident by the Pixel launcher being a 32-bit app in a 64-bit system, but 32-bit processors cannot run 64-bit apps. If Google makes the Google Assistant a 64-bit app and does not create a 32-bit version, even if we could install it on the Nexus 6 it won't run. Since the Assistant is not an open source app, no one would be able to build a 32-bit version that would run on the Nexus 6.
I'd like to be wrong on this one, but the Assistant is an exclusive that only the 5X and 6P are going to get, if Google decides to provide it.
Click to expand...
Click to collapse
Interestingly, however, we can already install Allo, which has the Assistant. I don't think I would put it past Google to offer a 32 bit option since the code base for it is already there. 64 bit devices may see it before the N6 simply because someone will port it over to other 64 bit devices from the Pixel. But otherwise, I think Google is going to to play the long game here (maintaining official Pixel exclusivity for a while) and eventually release it for any device that can support API level 24 (?) If memory serves, Now On Tap had this kind of exclusivity when it first appeared with the 6P and 5X
With the Nexus 6 being Google's last 32-bit device, and with the Pixel line being 64-bit only, chances of the N6 getting the Assistant are between slim and none. Allo is not a terribly good example. While it does have an assistant, the assistant supposedly only works in Allo. A big stumbling block in porting the Assistant from Allo would be Google's penchant for encrypting their code.
I would like to be wrong. I'd like to think we'll get the Assistant. However, I don't see it happening.
Is the new launcher a newer version than what has leaked? if so, can it be pulled out, and posted as an APK?
Strephon Alkhalikoi said:
With the Nexus 6 being Google's last 32-bit device, and with the Pixel line being 64-bit only, chances of the N6 getting the Assistant are between slim and none. Allo is not a terribly good example. While it does have an assistant, the assistant supposedly only works in Allo. A big stumbling block in porting the Assistant from Allo would be Google's penchant for encrypting their code.
I would like to be wrong. I'd like to think we'll get the Assistant. However, I don't see it happening.
Click to expand...
Click to collapse
I don't mean that we will see a "port" to 32 bit devices. I mean we may see official Google support sometime in the 7.x lifetime. As long as the N6 receives official 7.1 and up (which according to what I read today, the N6 may not. 7.1 will only go to devices that can support Daydream... and unless there is indeed official support for Vulcan (different argument entirely...and I don't mean developer support like Qualcomm has insinuated will be possible)), the N6 may not see 7.1 onwards.
I guess I need to upgrade to a 6p, to take advantage of a lot of the future apps.
We won't see official support, as it's not in Google's best interests to support a device that is two years old with a feature that is an exclusive on the Pixel/Pixel XL. The 32/64-bit divide is a convenient excuse to not provide the Assistant. Same goes for Vulkan.
We won't be seeing Android 7.1 anytime soon, if ever. Google has apparently not released any code related to 7.1.
Strephon Alkhalikoi said:
We won't see official support, as it's not in Google's best interests to support a device that is two years old with a feature that is an exclusive on the Pixel/Pixel XL. The 32/64-bit divide is a convenient excuse to not provide the Assistant. Same goes for Vulkan.
We won't be seeing Android 7.1 anytime soon, if ever. Google has apparently not released any code related to 7.1.
Click to expand...
Click to collapse
That's more or less what I've been saying.
cameraddict said:
That's more or less what I've been saying.
Click to expand...
Click to collapse
No. What you said is that Google may provide official support to the N6 at some point. I said they won't provide any such support, and provided reasons as to why. How you could draw a conclusion that I said essentially the same thing as you is unknown.
Strephon Alkhalikoi said:
No. What you said is that Google may provide official support to the N6 at some point. I said they won't provide any such support, and provided reasons as to why. How you could draw a conclusion that I said essentially the same thing as you is unknown.
Click to expand...
Click to collapse
Here is my last comment. Please reread it:
I don't mean that we will see a "port" to 32 bit devices. I mean we may see official Google support sometime in the 7.x lifetime. As long as the N6 receives official 7.1 and up (which according to what I read today, the N6 may not. 7.1 will only go to devices that can support Daydream... and unless there is indeed official support for Vulcan (different argument entirely...and I don't mean developer support like Qualcomm has insinuated will be possible)), the N6 may not see 7.1 onwards.
Click to expand...
Click to collapse
I've added some highlighting for context. I'm not trying to argue with you. But, this clearly shows that I also doubt that we will see official support... So yes, within context, basically the same thing.
Cheers
Regarding Google assistant for our nexus 6.
Found this mod in Nexus 6P forum and was able to implement it in my Nexus 6 successfully.
http://forum.xda-developers.com/nexus-6p/development/mod-google-assistant-stock-nbd90x-t3477868
Did not require flashing/porting anything at all. Must be on any stock or stock based Nougat ROM (I use latest Nutty Nexus by RachetPanda)
Warning : Experiment at your own risk. Editing build.prop may cause your device to not function properly.
My exact steps-
1. Make sure you have Google App (6.5.35.21 or newer)
2. Add ro.opa.eligible_device=true to the end of your build.prop
3. Edit build.prop and change ro.product.model=Nexus 6 to ro.product.model=Pixel
4. Clear Google App data and remove your Google account.
5. Reboot.
6. After reboot add your google account and activate Now on Tap. This will walk you through setting up Google Assistant
Bugs : Encountered none so far.
Well, contrary to what we have been saying, Google just officially said that the N6 will indeed get 7.1
And near the end is this line:
"...in early December, we’ll roll out updates to the full lineup of supported devices — Nexus 6, 5X, 6P, 9, Player, Pixel C, and supported Android One devices..."
Can someone port the copperhead os to moto g4 plus.. which is the most secure android ever used by google itself... in their pixel series of phones.. :highfive:
stkpxl said:
As much as I would love to see it ported, the G4 doesn't support it. These are the types of phones that are supported currently: Devices directly supported by the Android Open Source Project are candidates, meaning the Nexus and Pixel lines. Only devices with a 64-bit CPU architecture, full verified boot and LPDDR4 memory with TRR will be considered. Devices also need guaranteed security updates from the hardware vendor for device-specific components like firmware.
Pretty sure that leaves us out.
Click to expand...
Click to collapse
on their website they mentioned as.. it's an open source project. it should have been developed for 32 bit.. bcoz more than 90℅ devices are 32bit based system... but why they are not developing for other Android.. even though other android phones are the majority..
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???