Hi!
Just wanted to know if someone has started, or is thinking about starting, a Github account for Huawei U8800 (non-pro).
It looks like U8800Pro is starting to get somewhere: https://github.com/U8800Pro
So, if someone wants to do this then they can. And if they do want to do it, make sure you include trees for different android versions that are available. And no, there is no need to include trees that are not fully functional and will not be updated anymore.
Thanks. :good:
OK. I have taken up this task myself. Our github is here: http://github.com/U8800
Please give me suggestions as to which repositories should be added. I will start forking repositories from CyanogenMod.
For anyone that doesn't know why I want this done then it is only to make things much easier. It will be easier to download the whole source code for our phone from one github account. This will also give people a chance of downloading source code for what ever android they want and then build it.
Who ever wants to help me with this in any way then please let me know.
hey guys im the new guy here and wanted to know if you can give me a complete list what i need to make a sailfish rom.
and a question cant we use cyanogenmod 11 instead aof 10.1.3??
T-uzun said:
hey guys im the new guy here and wanted to know if you can give me a complete list what i need to make a sailfish rom.
and a question cant we use cyanogenmod 11 instead aof 10.1.3??
Click to expand...
Click to collapse
Well that's how the Nexus 5 was ported, but you'll need to modify the kernel a bit, I think, you'll also need the actual Sailfish ROM, here are the repo's for the Nexus 5, have a look at the kernel files, compare it to the standard CM11 kernel, and play close attention to the Kickstarter file (there is a link for the generic sailfish image in the kickstarter file), that will show what and where all the stuff is collected together, you then use the kickstarter file to make a sailfish image for your phone.
Have a look at the mer project wiki page, that will tell you some more about how to make an image.
nexus4 xiaomi mi2
thanks for your help
i realize that it is much harder to port sailfish than something more common
the nexus 4 port shoud be more easier to port, to xiaomi mi2 right?
you'll still have to modify some stuff to get it working, but in theory it could be easier.
T-uzun said:
thanks for your help
i realize that it is much harder to port sailfish than something more common
the nexus 4 port shoud be more easier to port, to xiaomi mi2 right?
Click to expand...
Click to collapse
if you can be patient the jolla team will release hadk soon. This means hardare adaption development kit. After this it will be much easier to port
sailfish os on other devices.
Sorry if there is a more appropriate thread but if anyone is still interested:
https://twitter.com/Nokius/status/679796509278355456
https://twitter.com/Nokius/status/679573564845101056
Not sure how far he is into the port though.
As the title suggests... i have looked all over the web for a device tree to be able to compile android with but all i have found is a basic dev tree for building twrp...
could someone please point me in the right direction or even advise me on how i would compile android from source for the sm-t230/t230nu
thanks in advance...
I've also been looking into this. I want rid of TW in the worst way.
Inside 4ndroid said:
As the title suggests... i have looked all over the web for a device tree to be able to compile android with but all i have found is a basic dev tree for building twrp...
could someone please point me in the right direction or even advise me on how i would compile android from source for the sm-t230/t230nu
thanks in advance...
Click to expand...
Click to collapse
We don't have a complete dev-tree yet. Samsung dosen't really want to release a lot of source code and so, there are lots of missing parts like driver sources and incomplete kernel sources etc. We also don't have a proper cousin device yet so it is very hard to build a tree for us.
Hi!
I'm new in this of the porting.
I have read mozilla's documentation for porting and I don't understand how proceed with the guide.
I have a Motorola XT915 and I would like to have firefox os on it.
I only find that the Xt915 has lock bootloader and I don't fine CyanogenMod or AOKP repositories for this phone, therefor, I don't know where to find the configuration tree files. But I don't have problem to build it.
I don't know where to find info to build the configuration file and xml and where to put it after.
if you give me a hand with this I would be grateful.
Xt915 razr d1?
Qwerpic said:
Hi!
I'm new in this of the porting.
I have read mozilla's documentation for porting and I don't understand how proceed with the guide.
I have a Motorola XT915 and I would like to have firefox os on it.
I only find that the Xt915 has lock bootloader and I don't fine CyanogenMod or AOKP repositories for this phone, therefor, I don't know where to find the configuration tree files. But I don't have problem to build it.
I don't know where to find info to build the configuration file and xml and where to put it after.
if you give me a hand with this I would be grateful.
Click to expand...
Click to collapse
You might have gone through already, if not, it will be useful for you
developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Installing_on_a_mobile_device
I could see few links which directly talks about porting firefox os to XT915, may be, if you can describe what you have done and in what step you failed to proceed, it will easy for the people to guide you.
Hey folks,
I know most people have already given up on this phone because it didn't sell well and doesn't have much support. But like the rest of us still browsing this forum, I still have my M9 and still believe it can be improved. I am currently working on a project to build a clean AOSP rom (without any kinky modifications, just a nice stock rom built directly from the AOSP sources.)
I've never undergone such a project, and I've been reading a lot about the steps necessary to realize this goal. I've been following Sony's excellent AOSP building guide so far. I have the android sources downloaded, all I'm missing are the proprietary files (from the device itself, most likely) and the ability to set up the proper device trees/manifests. I was planning to use the Cyanogenmod device tree because a lot of work has gone into it and, given that my M9 is currently running one of the CM13 nightlies, is pretty stable and works with new device firmwares. I know there is already a guide on the Cyanogenmod wiki for building CM for the M9, but I am not building CM at all, I want to build a 100% stock AOSP rom.
Can anybody help me proceed from here? I've downloaded the https://github.com/CyanogenMod/android_device_htc_hima-common tree and put it into device/htc/himaul but I'm not sure where to go from here. The extract-files.sh script does not work (because there is no CM helper script). Does anyone have any experience with this sort of thing?
Thank you very much in advance. I hope this will help everyone as I know many people have been looking for a non-CM AOSP rom for this phone (some do not agree with CM design philosophies). I definitely plan to share this rom and write a guide to help other projects when this is figured out.
I look forward to hearing back,
vivremetrique
Hi, I have no idea on doing roms, but you could help be your tester ...
whatever you need, talk me
---------- Post added at 10:22 PM ---------- Previous post was at 10:19 PM ----------
It would be good to make a ROM Nougat if possible
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Frug01 said:
[/COLOR]It would be good to make a ROM Nougat if possible
Click to expand...
Click to collapse
Yes, the sources I will be building from will be Nougat sources (7.1 experimental sources). Thank you for offering to test once this is done.
throcker said:
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Click to expand...
Click to collapse
I mean the operating system will be 100% AOSP, but obviously since this is not a Nexus/Pixel device the device tree will not be included in AOSP... The device tree/proprietary files have nothing to do with the actual user experience, they are simply needed for support of the hardware/stock kernel if desired/camera or wireless firmware. I don't see the sense is rewriting these from scratch given the time and effort already put into them by CM devs/those in the Cyanogenmod threads in this forum.
It would be great if some of you could help gather helpers for this project. It seems that properly setting up the device and getting ready to build the rom are all that is missing, so I'm hoping this goes relatively quickly.
So I believe I've made some progress. I downloaded the htc vendor files, the htc msm8994 kernel files, the hima-common tree, and the himaul tree. There is still something missing, because running the "lunch" command warns that it cannot locate the config makefile.
I found references to cm in cm.mk in device/htc/himaul/cm.mk but I don't know what to replace them with and I don't want to download the whole CM source tree as well.
Can anyone shed some light on this issue?
I can't help you, but that is a very good idea! Hope you can solve this issue.
Nice project, I would love to see AOSP Nougat on our M9! I'm not a dev who could help you with the building process, but maybe the dev of the CM14 port for M8 could give you an advice. Good luck!
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Any telegram group of One M9???
Enviado desde mi HTC_M9u mediante Tapatalk
Adromir said:
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Click to expand...
Click to collapse
That effort would.not be wasted. Once the solution to the camera problem is solved, it's solved for all versions, not just Marshmallow. We can reuse the kernel source and firmware blobs in N. I reckon that we don't have a rom because nobody is working on it.
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Adromir said:
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Click to expand...
Click to collapse
Because there is almost zero demand for one. People in the CM13 thread are actively discouraged from even mentioning CM14. How can we develop the ROM if we don't have anybody working on it?
Given CM's automated device tree preparation system, I doubt it would take more than a simple source tree update to Nougat to start compiling a 7.x ROM (whether it works perfectly or not, it would be a start).
Well then I would say, a way to start might be to try compile a booting cm 14 for the m9. Last time I looked there has been at least a device tree prepared for cm 14. I guess that would be the easiest way to test, if you might be succesfull with it
Any news @vivremetrique ? Or did you drop the project?
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Trainwr3ck said:
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Click to expand...
Click to collapse
If it is the same Problem I had with a CM13 based rom, then the build.prop is missing some Values to detect network. I took them from a working one and put them in the BoardConfig by hand
can't help, but my hopes are so high for this one!