Is it possible to porting roms(who maded for for mtk and snapdragon devices)for x86 devices,or I have to build a new one?
Thanks
naberl said:
Is it possible to porting roms(who maded for for mtk and snapdragon devices)for x86 devices,or I have to build a new one?
Thanks
Click to expand...
Click to collapse
No because the kernel is completely different, you can only port rom from another x86 devices like Samsung Galaxy Tab 3
Thank you.Is there a guide you are suggesting for building rom for x86 based devices
Impossible.The hardware is different.
Related
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
lgstoian said:
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
Click to expand...
Click to collapse
What about use a base of stock roms and make the things work??? I know Cm its for armv, but all its adaptable,
Enviado desde mi XT890 usando Tapatalk 2
as for MIUI (there already is a MIUI port on the razr i, not complet I think, but it exist). MIUI is mostly a framework mod.. this is platerform independant AFAIK.
I don't think CM & Cie are so dependant of the SoC architecture. There's lot of différences between some ARM SoC .. maybe more than you can imagine. If CM can be adapt to so many device with so many ARM SoC witch a so différent, why not for a x86 Soc ?
I think you're a little bit pessimist here...
I didn't say it's impossible but it's more complex then a normal port for an ARM device. The issue is it requires more knowledge on the issue and will eat far more time. A CM port to x86 is a very unlikely goal for a single dev , and I'm saying this because a few months ago I discussed this issue with the people behind Android x86.
So a talented DEV will be able to achieve this but it will take time and a bigger struggle , that's why to start of developing for this device it would be more reasonable to look at Android code already ported to x86.
lgstoian said:
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
Click to expand...
Click to collapse
Sure there is some ARM dependent code in the repos but most of android doesn't really depend on the arch (like apps using the sdk dont need to be recompiled for working on the I, see play store apps). I have worked with o1 and android-x86 and there isn't really that much change from CM and android-x86, just some extra optimizations for x86 which can be added in later.
There are plenty of device on where even custom rom seems to be impossible. mostly because of a locked bootloader.
Look at the Motorola Defy. At the beginning, the development of a custom rom like CM was pretty impossible.... but they did it. They did it so far that the Defy became one of must used device with Cyanogenmod. And you now the most astonishing? It's thanks to only 2 devs.
I think bypassing a locked bootloader like the Moto one is far more tricky than adapting a CM ROM to a x86 SoC (while the device is natively unlocked).
AFAIK, android-x86 project is not so close to the Android we have on our phone.
When you develop a custom rom you can either take the AOSP source and try to put it on your phone : the tricky way. Mainly when you don't have access to the source of the drivers (ARM or x86 .. same fight)
Or you can take the official rom and mod it to reach the AOSP/CM/MUI/etc level. And I think on most device it's the way to go (unless the manufacturer release all the source code of the device.... something that never appends).
lgstoian said:
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
Click to expand...
Click to collapse
You really know what you are talking about? As others already mentioned above CM is in most a framework - porting android to x86 seems to be not such a big gap as motorola did it already and for sure you can run android on your pc - do you own an arm pc (in this case i think an rasperry pi...). The toolchain remains the same so why you make such a story out of it? Are you a razr i owner or do you just want to frighten all razr i devs and owners awaiting a CM port??
ARM architecture is different in some points but most of the work will do the compiler and to be honest i think there will be some more x86 phones in the future, intel never developed it for one or two phones....
So what is your intention with this topic??
kind regards.
lord0815 said:
So what is your intention with this topic??
Click to expand...
Click to collapse
That's what I'm wondering. Any dev that's taking on this task obviously knows it's going to take a bit of extra work. It would have been different had the OP offered some help and advice, but he just posted the obvious while making it seem like a bigger deal than it is (at least I'm guessing it's not as big a deal as he makes it seem, considering the other posts in this thread). Nothing but fear mongering and pessimism at this point. Sure, we will have to wait a bit for the devs to figure things out, but I know enough of them picked up this phone that something will eventually come. Plus, there seems to be a bit of dev interest in the Intel Yolo as well.
I don't know much about porting or developing and getting cm to run with all the necesary source and drivers is probably not easy but I do know that one of the basic options when running the build/make command for AOSP and CM is an x86 build for emulation. So basic x86 infrastructure exists does that ensure compatibility with this phone maybe not but it might help and certainly it would still require SOC and device optimization drivers but its probably the better place to start then tackling trying to port ARM based code and drivers.
However in the meantime my thinking is maybe a CM style rom could be achieved by first stripping down the rom making it "blurless" and then porting CM features especially since the latest Moto ROM's are comparatively closer to stock then sense or touchwiz. Of course I don't have the phone yet its in England waiting to be brought to me.
HI I am not an Expert at building rom. I Really love Resurrection Remix ROM as it got most costimizable feature and extreme good battery and i am sure you would love it aswell and i got this rom on my nexus 5 and galaxy s3 so, i tried to port this rom From Oneplus one as it has similar specs but it didn't work after lots of try i cant build it i want to build it from source but i dont have computer with high specs and ubuntu os .( Even if i did build it from a source i wont be able to solve bug so no point)
So could any one please build this ROM For our device please .
about this rom: http://www.resurrectionremix.com
Source: https://github.com/ResurrectionRemix/platform_manifest/blob/kitkat1/README.mkdn
:good:Thank you :good:
[email protected] said:
HI I am not an Expert at building rom. I Really love Resurrection Remix ROM as it got most costimizable feature and extreme good battery and i am sure you would love it aswell and i got this rom on my nexus 5 and galaxy s3 so, i tried to port this rom From Oneplus one as it has similar specs but it didn't work after lots of try i cant build it i want to build it from source but i dont have computer with high specs and ubuntu os .( Even if i did build it from a source i wont be able to solve bug so no point)
So could any one please build this ROM For our device please .
about this rom: http://www.resurrectionremix.com
Source: https://github.com/ResurrectionRemix/platform_manifest/blob/kitkat1/README.mkdn
:good:Thank you :good:
Click to expand...
Click to collapse
Yes, its realy good rom i use this rom on galaxy s3.
What specs need to build, I have ubuntu i can help.
you can build with any specs, all you need is a decent cpu and hdd (ssd not recomended)
Envious_Data said:
you can build with any specs, all you need is a decent cpu and hdd (ssd not recomended)
Click to expand...
Click to collapse
Why ssd isnt recommend for build roms?
I find:
Operating system – Tested on Ubuntu 12.04, 12.10 and 13.10 (64-bit)
Terminal
Decent hardware (minimum of at least a dual core CPU and 4 GB of RAM)
Optimally have an SSD (standard mechanical drives work as well but slow down the process drastically)
Must have required packages for building installed, I will list them further down
PRO>KOMP.< said:
I find:
Operating system – Tested on Ubuntu 12.04, 12.10 and 13.10 (64-bit)
Terminal
Decent hardware (minimum of at least a dual core CPU and 4 GB of RAM)
Optimally have an SSD (standard mechanical drives work as well but slow down the process drastically)
Must have required packages for building installed, I will list them further down
Click to expand...
Click to collapse
try using this guide
https://github.com/ResurrectionRemix/platform_manifest/blob/kitkat1/README.mkdn
Hi,
I just bought a new Galaxy Tab 4 10.1 tablet and the model number is SM-T533. From what I've seen, the only difference is that the processor is a 64-bit snapdragon 410, vs the 32-bit snapdragon 400 from the other models. Does anyone know if ROMs for T530NU are compatible?
Thanks in advance .
only difference is that the processor is a 64-bit snapdragon 410, vs the 32-bit snapdragon 400
Click to expand...
Click to collapse
Not only ! This is a main and key difference
repey6 said:
Not only ! This is a main and key difference
Click to expand...
Click to collapse
Yeah, I know. I'm just wondering if the T530 ROMs are compatible or even if they can be installed at all. Maybe I'll have to wait until devs compile a version for this processor.
There is no custom recovery as far as I know as there is no source code for kernel. No way to root either unless you are on very old firmware.
Im using Infocus M530 [MT6595] i saw lots of that for MT65xx but only few is worked on MT6595. There is no specific guides for MT6595 for development etc and Mtkdroid,SP flash tool both also not work on my device. Only found "How To Root".Please Respective MTK devs do anything for MT6595 also n help others..
Thank You !
Sorry for my RIP english.
Hello Sahil Sir,
Lenovo vibe x2 is based on same procesor mt6595 and they just rolled out Android L update for their device, is it possible to port that rom on infocus m530 its also shares the same specs.
if it is possible kindly guide me i'll be highly thankfull for ur support.
snandan.gupta said:
Hello Sahil Sir,
Lenovo vibe x2 is based on same procesor mt6595 and they just rolled out Android L update for their device, is it possible to port that rom on infocus m530 its also shares the same specs.
if it is possible kindly guide me i'll be highly thankfull for ur support.
Click to expand...
Click to collapse
Hi,
Lenovo Vibe X2 is having same specifications as you said. I think it is possible to port that rom in Infocus M530 but, before that I want to say that the lenovo X2's L update is having some serious bugs. Please check it. And one more thing, in order to port you need custom recovery. Did ported any custom recovery into your M530. If yes, please let me know. Because I tried lot times & failed to port CWM & as well as TWRP.
No update for our device yet?
No custom rom,No recovery..... Is infocus m530 support dead?
shra1 said:
No custom rom,No recovery..... Is infocus m530 support dead?
Click to expand...
Click to collapse
Nope. Since it is rooted you can directly write to the raw partitions for "flashing" a rom, thus no need for a recovery. But it is too dangerous. One tiny error would brick the device.
Jamesits said:
Nope. Since it is rooted you can directly write to the raw partitions for "flashing" a rom, thus no need for a recovery. But it is too dangerous. One tiny error would brick the device.
Click to expand...
Click to collapse
so better to buy a new phone than waiting for a os update...
I have a zopo zp999 (with a shattered screen so I'm back on ol' faithful - Galaxy Note 2 n7100)
The whole MT6595 I think suffered from being relatively closed source. Even though there was an ubuntu version of the mi3 I think and its source code released, other manufacturers didn't come to the party - like zopo.
Manufacturers are really their own worst enemy for slitting their own throats by being so restrictive with source.
It also might be partly associated with the MT6595 containing a PowerVR GPU.
Non-Mali (ARM) gpus tend to be more closed with their drivers too.
Whereas ARM have been releasing the drivers for their mali gpus for years now.
the MT6595 was the targeted at being a super-mid SoC. The top of its time. I think the last 32-bit CPU, and once the 64-bit MT697x cortex A57 & A53 based product well everyone lost interest really.
It's a good modem. They have a pretty good engineering mode - eg ability to choose LTE/HSPA frequencies.
beyond that... eh...
Since google released the source,did anyone try building aosp 7.0 yet?Even xperia m managed to boot it XD
Since we have snapdragon 410 and with our kernel,Im pretty sure its compatible,1gb ram does the job too.
MaRtYy01 said:
Since google released the source,did anyone try building aosp 7.0 yet?Even xperia m managed to boot it XD
Since we have snapdragon 410 and with our kernel,Im pretty sure its compatible,1gb ram does the job too.
Click to expand...
Click to collapse
Moreover, there is another device Wileyfox Swift with almost the same specs as our phone has (the only difference is that in Wileyfox users have 2 gb of RAM). Still, enthusiasts managed to compile almost fully working ROM on AOSP 7.0 for that device. I think, that what is needed for our device is kernel. Once we have a kernel that supports Android 7, I guess it'll be easy to port that ROM for our device. I wish I were a dev to do all of that by myself
georgearn said:
Moreover, there is another device Wileyfox Swift with almost the same specs as our phone has (the only difference is that in Wileyfox users have 2 gb of RAM). Still, enthusiasts managed to compile almost fully working ROM on AOSP 7.0 for that device. I think, that what is needed for our device is kernel. Once we have a kernel that supports Android 7, I guess it'll be easy to port that ROM for our device. I wish I were a dev to do all of that by myself
Click to expand...
Click to collapse
The dragonite kernel of har**** jain is android n ready which he included in his rom
Junaid Shafi said:
The dragonite kernel of har**** jain is android n ready which he included in his rom
Click to expand...
Click to collapse
That ROM is ARM64 and kernel is compiled accordingly for x64. And the AOSP 7.0 ROM for Wileyfox is ARM.
georgearn said:
That ROM is ARM64 and kernel is compiled accordingly for x64. And the AOSP 7.0 ROM for Wileyfox is ARM.
Click to expand...
Click to collapse
Maybe har**** has 32bit android n kernel contact him on telegram
Dev_harsh1998