Related
http://www.change.org/petitions/nvidia-useful-driver-for-tegra-2-chipset#
just thought id share it in here guys. even if you dont think its relevant to you, since you dont flash roms (which is unlikely, because you would not be in xda..lol ), still sign it ! its important stuff, especially if we want a good ics rom.
cheers
xilw3r said:
http://www.change.org/petitions/nvidia-useful-driver-for-tegra-2-chipset#
just thought id share it in here guys. even if you dont think its relevant to you, since you dont flash roms (which is unlikely, because you would not be in xda..lol ), still sign it ! its important stuff, especially if we want a good ics rom.
cheers
Click to expand...
Click to collapse
Note from Nvidia about drivers
Hello Android Development Community
We appreciate all the interest and passion surrounding the NVIDIA Tegra Platform and we take our support for the development community seriously. NVIDIA has been working with Google and Motorola to provide the open source community with the required drivers and other binary code to build full Android OS images for the Tegra 2 powered "Motorola Xoom". We expect Google to make those components available as part of the Android Open Source Project soon.
In addition, NVIDIA is working on a full release of Ice Cream Sandwich (ICS) for our Tegra 2 Dual Core and Tegra 3 Quad Core reference devices to be made available early next year. This release package will comprise of binary code, drivers developed on our reference platforms and any patches necessary to ensure stability & performance with ICS. We hope the open source community can leverage this release for their work on all Tegra devices.
Andrew Edelsten
Source: http://forum.xda-developers.com/showthread.php?t=1309620
These petitions are of no use. The only option we have is to wait.
i know i know... online petitions dont accomplish anything.. but i guess im just a bit desperate.
ive seen that statement and what troubles me is that it mainly concerns xoom which is actually using a different kind of tegra2, ventenara or sth like that whereas 2x has harmony tegra 2, so if nvidia releases drivers for xoom, we wont have much use of them
Is there anyone planning on trying to hack Windows Phone 8 on to Windows Phone 7 handsets? I'd like to get WP8, but I also want to wait to see if there's a Surface Phone announced in the next six months, so I don't want to spend a ton of money on an off-contract Lumia 920 right now.
I'd check if the hardware is up to it ,ice the ram.
The reason they are not being updated I understand is due to the hardware restrictions. They must know a lot of owners are very fed up and would surely update if they could as its a PR disaster for them
Sent from the man in Your attic.....
howard bamber said:
I'd check if the hardware is up to it ,ice the ram.
The reason they are not being updated I understand is due to the hardware restrictions. They must know a lot of owners are very fed up and would surely update if they could as its a PR disaster for them
Sent from the man in Your attic.....
Click to expand...
Click to collapse
Well I'm suspecting it may be possible because the HTC HD2 can run Windows Phone 7. I think it may be a bit slow and whatever, but I'd bet it's possible.
revxx14 said:
Well I'm suspecting it may be possible because the HTC HD2 can run Windows Phone 7. I think it may be a bit slow and whatever, but I'd bet it's possible.
Click to expand...
Click to collapse
The HTC HD2 has exactlly the same chipset on board as the first wave of WP7 handsets used (Qualcomm Snapdragon S1 - QSD 8x50).
Contrary to this WP8 devices all feature at least Dual-Core Snapdragon S4 Chips, while the strongest WP7.5 devices have a Single Core Snapdragon S2 (MSM8255T). The RAM is actually a much smaller problem, given that entry level WP8 devices have 512 MB, same as most WP7 devices.
The hardware should be able to run WIndows 8 without much problems.
The big obstacle ahead is the lack of drivers. We need to create drivers for our chipsets and hack them into Windows Phone 8. We should be able to remove some features that require the dual core processors and other hardware aspects like NFC or secure bot.
But i don't think this will be necessary, as the 7.8 update will do pretty much that and we won't have to bother about it.
Idk about other OEMs, but Nokia is determined to bring as many WP8 features as possible. We probably won't get a file manager and real multitasking, but that is not a big issue.
The HTC 8s has single core and almost the same resolution as 2nd generation wp handsets
mcosmin222 said:
We should be able to remove some features that require the dual core processors
Click to expand...
Click to collapse
Ha-ha it's impossible without source code. Or you can easily do it using only assembler?
mcosmin222 said:
But i don't think this will be necessary, as the 7.8 update will do pretty much that and we won't have to bother about it.
Click to expand...
Click to collapse
WP7.8 is using wince kernel while wp8 is using NT. They have different API.
2Topicstarter : The answer is NO. WP7 was ported to HD2 and TG01 only because they have the same hardware (SoC and Radio). If you want to use WP8 - buy new phone. Same to android.
jrtorrents said:
The HTC 8s has single core and almost the same resolution as 2nd generation wp handsets
Click to expand...
Click to collapse
It has dual core.
---------- Post added at 07:37 PM ---------- Previous post was at 07:33 PM ----------
Useless guy said:
Ha-ha it's impossible without source code. Or you can easily do it using only assembler?
WP7.8 is using wince kernel while wp8 is using NT. They have different API.
2Topicstarter : The answer is NO. WP7 was ported to HD2 and TG01 only because they have the same hardware (SoC and Radio). If you want to use WP8 - buy new phone. Same to android.
Click to expand...
Click to collapse
Whats the catch with the kernel? I'm talking about the features in windows phone 8 that wp 7.8 will bring. The kernel really has nothing to do with those, if they really want to bring em. As i said, we wouldn't get real multitasking, NFC and Directx games(if nokia really wants it, directx can be fixed too).
mcosmin222 said:
It has dual core.
---------- Post added at 07:37 PM ---------- Previous post was at 07:33 PM ----------
Whats the catch with the kernel? I'm talking about the features in windows phone 8 that wp 7.8 will bring. The kernel really has nothing to do with those, if they really want to bring em. As i said, we wouldn't get real multitasking, NFC and Directx games(if nokia really wants it, directx can be fixed too).
Click to expand...
Click to collapse
Quoting:
The hardware should be able to run WIndows 8 without much problems.
The big obstacle ahead is the lack of drivers. We need to create drivers for our chipsets and hack them into Windows Phone 8. We should be able to remove some features that require the dual core processors and other hardware aspects like NFC or secure bot.
Click to expand...
Click to collapse
Maybe I'm drunk (cause I'm from Russia) and unable to read this.
You are drunk
About 7.8: I don't want a kernel change in 7.8 It won't happen. But we will get as many features of windows 8 as our hardware can handle.
Reverse engineering WP8 will do the same. The only advantage it might have over 7.8 is that we will run directx games. The huge disadvantage is that we need to get the source code, hack drivers for our hardware in it, disable the windows phone 8 specific stuff that our hardware does not support. I don't really see such huge benefit in doing it. We are better off waiting for 7.8 instead, which will bring pretty much the same (sans the directx games).
That's what i wanted to say. Sorry I didn't make it clear enough. My bad
That is never going to be possible!!
cant u see the size of the ROMS?
1GB- 1.31 GB
they will never get half the OS on our WP7 nands!
mcosmin222 : mate i meant by the size of the ROMs we download for flashing.
a lumia 800 rom around 320 MB and lumia 820 around 1.2 GB
so the matter of content maybe much larger while talking about porting..
surya467 said:
That is never going to be possible!!
cant u see the size of the ROMS?
1GB- 1.31 GB
they will never get half the OS on our WP7 nands!
lOL! XD
Click to expand...
Click to collapse
LOLWUT?
The current WP7.5 OS is about 2 GB size.
The smallest WP device is 4GB i think.
So you do the math.
And if you meant RAM, the OS uses around 130 mb.
mcosmin222 said:
You are drunk
About 7.8: I don't want a kernel change in 7.8 It won't happen. But we will get as many features of windows 8 as our hardware can handle.
Reverse engineering WP8 will do the same. The only advantage it might have over 7.8 is that we will run directx games. The huge disadvantage is that we need to get the source code, hack drivers for our hardware in it, disable the windows phone 8 specific stuff that our hardware does not support. I don't really see such huge benefit in doing it. We are better off waiting for 7.8 instead, which will bring pretty much the same (sans the directx games).
That's what i wanted to say. Sorry I didn't make it clear enough. My bad
Click to expand...
Click to collapse
Ok, I finally understood
Useless guy said:
Ha-ha it's impossible without source code. Or you can easily do it using only assembler?
WP7.8 is using wince kernel while wp8 is using NT. They have different API.
2Topicstarter : The answer is NO. WP7 was ported to HD2 and TG01 only because they have the same hardware (SoC and Radio). If you want to use WP8 - buy new phone. Same to android.
Click to expand...
Click to collapse
I have WP8 source code. The drivers are *.sys files. Porting could be possible.
sianto1997 said:
I have WP8 source code.
Click to expand...
Click to collapse
sianto1997 said:
The drivers are *.sys files. Porting could be possible.
Click to expand...
Click to collapse
D: D: D:
sianto1997 said:
I have WP8 source code. The drivers are *.sys files. Porting could be possible.
Click to expand...
Click to collapse
WHAT? how...tell meeeeeeeeeeeeeee
---------- Post added at 07:56 PM ---------- Previous post was at 07:54 PM ----------
surya467 said:
That is never going to be possible!!
cant u see the size of the ROMS?
1GB- 1.31 GB
they will never get half the OS on our WP7 nands!
mcosmin222 : mate i meant by the size of the ROMs we download for flashing.
a lumia 800 rom around 320 MB and lumia 820 around 1.2 GB
so the matter of content maybe much larger while talking about porting..
Click to expand...
Click to collapse
I don't think the size is going to be a problem.
If we can hack the entire system, we surely can use our magic to get around the size, if that is an issue.
mcosmin222 said:
WHAT? how...tell meeeeeeeeeeeeeee
Click to expand...
Click to collapse
Its the 9900 emulator build, which cant run on a phone, but still, you can get the idea!
sianto1997 said:
Its the 9900 emulator build, which cant run on a phone, but still, you can get the idea!
Click to expand...
Click to collapse
Hi Sianto 1977. Can you share source code download link?
The Tab Pro 10.1 has tons of development activity. Tab S 10.5 not so much (i.e., practically none as far as roms). Just private messaged the top Developers in the Tab Pro forum asking if their work there can be ported to the Tab S. Hardware other than the screen is very similar. Seems like it should be doable (although I'm not a developer and there may be complications of which I am unaware).
Anyway, flare fired, emergency beacon activated. Let's hope we can get some port love here and get a solid rom or two going.
** They may need some guinea pigs to test things out. But these are extremely experienced recognized Devs and you should take some comfort in that.
UPDATE: All development for the 10.1 is for the SM-T520 which is the Exynos 5 wifi model. Should be no issues there.
TAB PRO 10.1:
Chipset Exynos 5 Octa 5420
CPU Quad-core 1.9 GHz Cortex-A15 & quad-core 1.3 GHz Cortex-A7
GPU Mali-T628 MP6
TAB S 10.5:
Chipset Exynos 5 Octa 5420
CPU Quad-core 1.9 GHz Cortex-A15 & quad-core 1.3 GHz Cortex-A7
GPU Mali-T628 MP6
Identical.
UPDATE:
Good news folks! Our little project here has resulted in a working, smooth and pretty dammed fast rom for the 10.5 (US Version). It is still in Beta but based upon my experience, everything seems to be working.
Special appreciation to @Shaheer who came here from the 10.1 Pro Forums and without the benefit of his own device built a working rom for us. My thanks also go out to all the smart people who teamed with him to make it happen.
Go give it a flash. It only gets better from here
http://forum.xda-developers.com/galaxy-tab-s/development/sm-wip-rom-t2832360
** Update: Have just heard from @mrwookie6379 in the Tab Pro 10.1 forums. He has also expressed interest in developing for us. Cool.
There is a big difference between tab pro and tab s.
Maybe I'm wrong but the development is only on snapdragon version of the tab pro...
Orphee said:
There is a big difference between tab pro and tab s.
Maybe I'm wrong but the development is only on snapdragon version of the tab pro...
Click to expand...
Click to collapse
All development for the 10.1 is for the SM-T520 which is the Exynos 5 wifi model. Should be no issues there.
TAB PRO 10.1:
Chipset Exynos 5 Octa 5420
CPU Quad-core 1.9 GHz Cortex-A15 & quad-core 1.3 GHz Cortex-A7
GPU Mali-T628 MP6
TAB S 10.5:
Chipset Exynos 5 Octa 5420
CPU Quad-core 1.9 GHz Cortex-A15 & quad-core 1.3 GHz Cortex-A7
GPU Mali-T628 MP6
Identical.
** OP amended.
If any of these devs ported CyanogenMod or aosp, I would love to take a look at their device directory. I am getting closer with my port but running into a crash with surfaceflinger and the mali driver.
My wife would be happy if I got this working so I could stop obsessing.
eousphoros said:
If any of these devs ported CyanogenMod or aosp, I would love to take a look at their device directory. I am getting closer with my port but running into a crash with surfaceflinger and the mali driver.
My wife would be happy if I got this working so I could stop obsessing.
Click to expand...
Click to collapse
i have the 10.1 and have been considering the S and so looking around here to make my decision. i will say that the Exynos component is probably going to prevent us from every seeing CM11 becase they dont develeop for it. also there is very little dev for the 10.1 and what little there is sees very little updates and most roms seem to be abandoned.
none of the 10.1 to date have developed far enough to make me want to install them yet.
you can look here to see them and then check OP for last update and you will see what i mean
Ah the mondrianwifi, I took a look at that one initially but unfortunately it had enough subtle differences it wasn't much use.
Edit: So just did some digging, still can't find any ports of cyanogenmod to 10.1 (SM-T520). Ill spend a little bit more time digging but as far as I can tell the closest port has been the exynos 5410 samsung galaxy s4 which is what I forked my current port.
When I said there was no development on the Tab Pro, I meant the T520 of course, as the T525 is snapdragon...
It seems I was right, I didn't see any cm11 work for the T520.
Orphee said:
When I said there was no development on the Tab Pro, I meant the T520 of course, as the T525 is snapdragon...
It seems I was right, I didn't see any cm11 work for the T520.
Click to expand...
Click to collapse
By "development" are you referring only to CM? That's a pretty narrow definition of development. And of course no CM for Exynos but lots of TW based roms as you can see from the Tab Pro forum.
CM is awesome and clean and light and fast but you also give up the entire TW ecosystem including multiwindow which is a big price to pay for a little more speed.
Yes TW can go to the junk, CM is the best thing we could have on our tablets.
I consider TW based Rom more as tweaks / tuning than real development.
Orphee said:
Yes TW can go to the junk, CM is the best thing we could have on our tablets.
I consider TW based Rom more as tweaks / tuning than real development.
Click to expand...
Click to collapse
Well using that argument, CM is just tweaked Android.
Yes of course ...........
Well so far no responses to my private messages from the developers at Tab Pro forum. Next step will be to post in the actual threads and ask nicely for help. These guys probably get a million PMs so I'm not surprised not to hear a response.
mitchellvii said:
Well using that argument, CM is just tweaked Android.
Click to expand...
Click to collapse
And android is just tweaked linux. Though the difference in porting AOSP/CM to this device versus modifying the current rom is like the difference between building a model rocket from a kit and launching a shuttle into orbit.
Really anyone who knows how to extract/build a system.img can build a rom for this device in under an hour. Super simple. Though thats not what I am personally interested in accomplishing. There is way too much stuff in the samsung rom that triggers my paranoia, up to and including the clause in the license that says something along the lines of any data we collect can be used to evaluate your eligibilty for hiring at samsung.
I am getting AOSP/CM on here or this tablet is going up for sale. If anyone is interested in helping out I have a couple github repos up and making progress on a daily basis.
eousphoros said:
And android is just tweaked linux. Though the difference in porting AOSP/CM to this device versus modifying the current rom is like the difference between building a model rocket from a kit and launching a shuttle into orbit.
Really anyone who knows how to extract/build a system.img can build a rom for this device in under an hour. Super simple. Though thats not what I am personally interested in accomplishing. There is way too much stuff in the samsung rom that triggers my paranoia, up to and including the clause in the license that says something along the lines of any data we collect can be used to evaluate your eligibilty for hiring at samsung.
I am getting AOSP/CM on here or this tablet is going up for sale. If anyone is interested in helping out I have a couple github repos up and making progress on a daily basis.
Click to expand...
Click to collapse
Contact UpInTheAir. He knows a lot about this stuff.
eousphoros said:
And android is just tweaked linux. Though the difference in porting AOSP/CM to this device versus modifying the current rom is like the difference between building a model rocket from a kit and launching a shuttle into orbit.
Really anyone who knows how to extract/build a system.img can build a rom for this device in under an hour. Super simple. Though thats not what I am personally interested in accomplishing. There is way too much stuff in the samsung rom that triggers my paranoia, up to and including the clause in the license that says something along the lines of any data we collect can be used to evaluate your eligibilty for hiring at samsung.
I am getting AOSP/CM on here or this tablet is going up for sale. If anyone is interested in helping out I have a couple github repos up and making progress on a daily basis.
Click to expand...
Click to collapse
I know slim had been built for the 5410... maybe poking about their Gerrit may help?
Sent from my SM-T800 using XDA Premium 4 mobile app
Poser said:
I know slim had been built for the 5410... maybe poking about their Gerrit may help?
Sent from my SM-T800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately the 5410 doesn't use the mali gpu which is where I am currently getting a crash. I just imported a bunch of code from the arndale_octa (Raspberry pi like board that uses the 5420 SOC) and waiting for my build to finish.
eousphoros said:
Unfortunately the 5410 doesn't use the mali gpu which is where I am currently getting a crash. I just imported a bunch of code from the arndale_octa (Raspberry pi like board that uses the 5420 SOC) and waiting for my build to finish.
Click to expand...
Click to collapse
Power VR...totally forgot. Does anything other than 5420 and arndale use the T628?
You think the crash is at the 3D render...or the handoff back to the a15 display controller?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Poser said:
I know slim had been built for the 5410... maybe poking about their Gerrit may help?
Sent from my SM-T800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Poser said:
Power VR...totally forgot. Does anything other than 5420 and arndale use the T628?
You think the crash is at the 3D render...or the handoff back to the a15 display controller?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
5420, 5422, and the 5800 use the T628.
As for the crash it looks like its happening somewhere between hwcomposer, gralloc, libEGL, and libGLES_mali. I put that fork on pause while I try take a look at the arndale_octa mali code.
eousphoros said:
And android is just tweaked linux. Though the difference in porting AOSP/CM to this device versus modifying the current rom is like the difference between building a model rocket from a kit and launching a shuttle into orbit.
Really anyone who knows how to extract/build a system.img can build a rom for this device in under an hour. Super simple. Though thats not what I am personally interested in accomplishing. There is way too much stuff in the samsung rom that triggers my paranoia, up to and including the clause in the license that says something along the lines of any data we collect can be used to evaluate your eligibilty for hiring at samsung.
I am getting AOSP/CM on here or this tablet is going up for sale. If anyone is interested in helping out I have a couple github repos up and making progress on a daily basis.
Click to expand...
Click to collapse
Thank you, I taught it was useless to argue with mitchellvi but you explained it very well.
I couldn't do as good as you did.
Thank you a lot
Orphee said:
Thank you, I taught it was useless to argue with mitchellvi but you explained it very well.
I couldn't do as good as you did.
Thank you a lot
Click to expand...
Click to collapse
Lol, argue with me about what, that only CM development is real development? The entire Development section of any Samsung forum is dedicated to non-CM based roms and represents 95% of all development for that device - and simple they're not.
The purpose of this thread is to draw rom development to the Tab S 10.5. Denigrating TW developers and comparing their efforts to model rocketry doesn't help. As far as CM being the space shuttle, that ship is already built and on the pad, you're just looking for the launch codes.
So, Nexus 6 doesn't have Vulkan right? That's not fair by google because Adreno 420 is supposedly supported by Qualcomm on this.
It will. We are waiting on a driver from Qualcomm. They say on their website it is comming.
Maybe Android 7.1 will have it. Fingers crossed!
Lawstorant said:
So, Nexus 6 doesn't have Vulkan right? That's not fair by google because Adreno 420 is supposedly supported by Qualcomm on this.
Click to expand...
Click to collapse
The clarification is this; Vulkan is an API. That means APPLICATION PROGRAMMING INTERFACE. I.e., it defines the language used by APPLICATIONS to talk to the DRIVER.
Until there are actually APPLICATIONS that YOU require, that themselves *REQUIRE* Vulkan, then it doesn't matter if your driver implements that API.
Translation: Who cares? It won't do you any good. This is a long term far far off kind of preparing for the future API.
Yeah, I know all that. It's just that Vainglory is rushing with Vulkan support and Vulkan might prolong N6 gaming lifespan. I'm just interested if it would be at all possible to add Vulkan drivers even if Google refuses to do so.
Unless Qualcomm releases binaries for the N6, there will be no Vulkan. Dropping in binaries from a device with Vulkan won't help, at least from what little I've read on the topic.
That needs to be tried out. I flashed marshmallow graphics drivers intended for nexus on my Samsung tablet and zuk phone without problems.
Any update on vulkan?
santi1993 said:
Any update on vulkan?
Click to expand...
Click to collapse
The Nexus 6 will not get it due to the chip not supporting it. This info has been around for a while. Too be honest it really wont even be worth having for a few years yet.
zelendel said:
The Nexus 6 will not get it due to the chip not supporting it. This info has been around for a while. Too be honest it really wont even be worth having for a few years yet.
Click to expand...
Click to collapse
But they said they were going to support it? https://www.xda-developers.com/vulkan-api-means-more-control-but-not-outright-replacement-of-opengl/
Sorry if i'm being a little stupid here, but the nexus 6 has the 805 and the 805 is said to be supported since it has a 4xx GPU right?
What were you going to do if it was available? As stated above, Vulkan isn't really widely used yet so having it enabled wouldn't really make any difference.
clonetrooper67 said:
Sorry if i'm being a little stupid here, but the nexus 6 has the 805 and the 805 is said to be supported since it has a 4xx GPU right?
Click to expand...
Click to collapse
The Nexus 6 is capable of supporting Vulkan, but Qualcomm has to provide the APIs and apparently have no desire to do so.
Strephon Alkhalikoi said:
The Nexus 6 is capable of supporting Vulkan, but Qualcomm has to provide the APIs and apparently have no desire to do so.
Click to expand...
Click to collapse
Here is an article from a google engineer
https://www.androidheadlines.com/2016/07/google-engineer-says-no-vulkan-support-for-the-nexus-9.html
" Aside from the Nexus 9, the Nexus 6 is also left out of the list of supported devices."
What an engineer says is beside the point here. The fact of the matter is Qualcomm themselves noted the 805 as being compatible. Therefore it is up to Qualcomm to provide or not provide the support, NOT Google. Qualcomm chose not to, and I really don't have a problem with that. It's not a huge deal since there really isn't anything requiring Vulkan in the first place.
Strephon Alkhalikoi said:
What an engineer says is beside the point here. The fact of the matter is Qualcomm themselves noted the 805 as being compatible. Therefore it is up to Qualcomm to provide or not provide the support, NOT Google. Qualcomm chose not to, and I really don't have a problem with that. It's not a huge deal since there really isn't anything requiring Vulkan in the first place.
Click to expand...
Click to collapse
It's not just one side. It has to be both. Qualcomm could support it but Google decides not to. Or the reverse. Google has the final say
zelendel said:
It's not just one side. It has to be both.
Click to expand...
Click to collapse
Says who? If Qualcomm desired they could release Vulkan for the 805 and there isn't a thing Google could do about it. This is solely Qualcomm not wishing to provide further support for the 805, which is totally understandable given they have switched over to 64-bit processors. At the end of the day, all that really matters is the N6 isn't getting Vulkan, and by the time games become available which require Vulkan, the N6 will be sitting in some forgotten corner of a dresser drawer or storage box. Thus, who makes the decision isn't nearly as important as the decision itself.
So today Motorola India launched a new variant of X4 in India. Bumping the RAM from 3 & 4 GB to 6GB with same 64GB storage.
The main highlight is the phone comes with Oreo out of box and it supports Treble..
Now see what Motorola has to say about new X4 Variant -
There don't seem to be any other differences but the RAM amount, and the fact that the handset ships with Oreo by default. Motorola does say that there are a few interface tweaks pertinent to the fresh X4, but the other models will eventually get them, too. After that the key difference will be the extra 2GB of RAM.
So what is Motorola is talking here abt that the older models will eventually get it..? Is it the treble support.?
If they don't enable treble on the original moto x4, they will be loosing out on many potential customers who care about the latest updates and ROMs. I think that not enabling treble will be a huge mistake on Motorola's part. I'm also starting to get annoyed with the huge market catering to India...
Honestly, I think there's 0 chance it will happen, sorry.
Do you guys think its possible to flash the stock rom from a new moto x4 to an old one ? That could be a way to enable treble for the "old" devices
harry_martini said:
Do you guys think its possible to flash the stock rom from a new moto x4 to an old one ? That could be a way to enable treble for the "old" devices
Click to expand...
Click to collapse
I am curious to take a look at the firmware from this device. Does anyone have it?
No one should hold their breath for a "Treble Update" from Motorola... it may require repartitioning the device and doing that via OTA would be quite a challenge and be too risky for them.
That said, I would still like to see the vendor/HAL implementation, and especially check out partitioning. From an efficiency/cost standpoint it would be surprising to see any major differences in structure since that would require Motorola to have a dev team just for one new variant.
But even if the devices are identical that does not mean we could simply flash the Treble firmware. There would seem to be an intermediate step that would require partitioning. It may be beyond the scope of our existing tools. These may be changes that could only be made with Motorola proprietary software.
But an interesting development, nonetheless...
Just did a little reading, and it seems that the hardware IS different than the original X4...specifically the SoC which is SDM636 running custom Kyro architecture vs. our SDM630
mightysween said:
Just did a little reading, and it seems that the hardware IS different than the original X4...specifically the SoC which is SDM636 running custom Kyro architecture vs. our SDM630
Click to expand...
Click to collapse
where did u read that..?
The only difference is extra 2gb ram and Oreo out of box.
here is the product page, check for yourself..
https://www.flipkart.com/moto-x4-super-black-64-gb/p/itmez9u3cgg9zfy2?pid=MOBFF6GGPJYKGQCK&sattr=color&sattr=storage&sattr=ram&st=ram
Jithin91 said:
where did u read that..?
The only difference is extra 2gb ram and Oreo out of box.
here is the product page, check for yourself..
https://www.flipkart.com/moto-x4-su...CK&sattr=color&sattr=storage&sattr=ram&st=ram
Click to expand...
Click to collapse
Read it here on XDA
https://www.xda-developers.com/new-motorola-moto-x4-variant-india-february-1/
mightysween said:
Read it here on XDA
https://www.xda-developers.com/new-motorola-moto-x4-variant-india-february-1/
Click to expand...
Click to collapse
it was a rumour. x4 6gb version is still having sdm630.
kraatus90 said:
it was a rumour. x4 6gb version is still having sdm630.
Click to expand...
Click to collapse
Excellent... can't wait to see under the hood
I don't think so, but it IS possible.
When Oreo came out, it was important for Motorola to update their phones quickly to Oreo;
in order to look good compared to other brands.
Implementing Treble would take more time; but once implemented would make it easier for them to provide faster security updates in the future.
So it's a possibility that the next security update in january or february, may include Treble.
The moto X4 is due to receive Security updates until April 2019, so Treble might make sense to Motorola.
But there's definately no way to know for sure.
But isn't 6 GB just a variant of Moto x4, so probably it also doesn't have project treble enabled.
Jithin91 said:
So today Motorola India launched a new variant of X4 in India. Bumping the RAM from 3 & 4 GB to 6GB with same 64GB storage.
The main highlight is the phone comes with Oreo out of box and it supports Treble..
Now see what Motorola has to say about new X4 Variant -
There don't seem to be any other differences but the RAM amount, and the fact that the handset ships with Oreo by default. Motorola does say that there are a few interface tweaks pertinent to the fresh X4, but the other models will eventually get them, too. After that the key difference will be the extra 2GB of RAM.
So what is Motorola is talking here abt that the older models will eventually get it..? Is it the treble support.?
Click to expand...
Click to collapse
I am also sad seeing such slow development on X4 not much roms, not official or unofficial treble support!, still being Android one device is so sad and bad!
---------- Post added at 11:49 AM ---------- Previous post was at 11:43 AM ----------
mightysween said:
I am curious to take a look at the firmware from this device. Does anyone have it?
No one should hold their breath for a "Treble Update" from Motorola... it may require repartitioning the device and doing that via OTA would be quite a challenge and be too risky for them.
That said, I would still like to see the vendor/HAL implementation, and especially check out partitioning. From an efficiency/cost standpoint it would be surprising to see any major differences in structure since that would require Motorola to have a dev team just for one new variant.
But even if the devices are identical that does not mean we could simply flash the Treble firmware. There would seem to be an intermediate step that would require partitioning. It may be beyond the scope of our existing tools. These may be changes that could only be made with Motorola proprietary software.
But an interesting development, nonetheless...
Click to expand...
Click to collapse
I am very sad seeing such slow development on X4 not much roms, not official or unofficial treble support!, still being Android one device is so sad and bad!
The slow development is because of the A/B partition scheme, if you look other phones that uses the same partition system it'll be the same, it's Google "fault".
Last I checked, all devices running Oreo have to have Treble. That is why everyone was mad at HTC for shipping new phones with Nougat.It especially makes sense for the Android One variant because the have to get timely updates out, which they have. It would be off for the 6gb to have it and no others because Google requires every