Are the device trees the same between the 500 and the 510? If not, what might be the closest device to the gpe?
If so, does anybody have :
updater script for mount points, I've got em cat, but easier would be to have a template, same for the following two.
the BoardConfig.mk
the device_[codename].mk
And any other info that may be relevent.
All help is greatly appreciated. I'm trying for a Cyanogen mod from source for the 510. I know somebody else may, or may not be doing this per ifo in the rom threads and Iv'e heard, but am giving it a go myself.
Related
As I was trying to create a swap file on my Hero I noticed that both mkswap and swapon are missing. HTC might have removed them from the ROM.
So I was wondering. Is is possible to take these binaries out from a, let's say, Magic ROM and put them in Hero. In theory it should work because of the same architecture. So If anyone is willing to share these binaries, I would give it a try
Can you look inside your Heros and let me know if this is just on mine. (Of course you must root it, mine done without a problem).
Have fun with hero!!
Aren't swap apps always hacks? Thought you'd only get that in cooked ROM
Daisy xxx
Dayzee said:
Aren't swap apps always hacks? Thought you'd only get that in cooked ROM
Click to expand...
Click to collapse
Makes sense. However as android being linux, it could be done just by adding the binaries and the appropriate libs. In theory it should work. Someone should try it
I'm not so up-to-date, are there any cooked ROMs for Hero (I'd flash mine, but I would like to keep the senseUI)?
Nothing yet
ok...
I have decided to start editing the Htc Hero wiki page here on xda-devs, so I'd be grateful if anyone could help. For example: for cooked roms and stuff like that. I'm already adding rooting methods so other users don't need to search in the forum, just go to the wiki page. So if anyone is interested, please help me edit the wiki page. (Oh this was a little of-topic:S - I'll make new thread)
Peace!
This will give you swapon etc.:
http://www.modaco.com/index.php?showtopic=291345
I'll add it to an update.zip shortly.
P
What exactly does the hybrid method update.zip does? I have seen it does something with the boot partition... Just asking because I don't want to brick my hero.
If updates the boot.img one to one that lets you adb remount.
P
Hi all Desirian Guru,
I am not sure this is the right place to bring this stupid question, but if you, the operator, found it is wrong, please move to where it should be. I would like to create or develop, if I can, my own custom ROM for fun and share. Could anyone here kindly point me what steps I should take, what the prerequisites I should have.
Appreciate you guys so much if those tools are supported on my Ubuntu.
and on windows too!
Same sort of thread made before: http://forum.xda-developers.com/showthread.php?t=817699
Might help
Start here, if you are intending to build from the AOSP source:
http://source.android.com/porting/index.html
http://source.android.com/source/git-repo.html
Get the source code from here:
http://android.git.kernel.org/
There is an unofficial "vendor" from devoferreria for the htc bravo board here:
https://github.com/defer/android_device_htc_bravo
The cyanogenmod wiki has a load of excellent info on it, including compiling your kernel:
http://wiki.cyanogenmod.com/index.php?title=Building_Kernel_from_source
If you are looking to mod a SenseUI rom there are guides around here that explain how to change the framework. That is a different art ... use a wider forum search and you should find them.
TheGost1233, stOkes,
thanks for your advise.
You guys rock.
Greetings all,
I would like to know something that seems to be so simple it hasn't been documented here anywhere.
My question is: How do I build the source provided by Google for my Desire HD?
Yes, there are tutorials, don't point me to them. They either provide you with the AOKP way or the CM way.
I want to build my stuff from scratch.
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I know about the vendor files, these are created by a third party. How do I know what vendor files I need to create? How do I know how to name them?
Don't get me wrong, I've used C, C++ and C# for YEARS (I think about 8 now) and I know how to code. I just don't know how to compile android!
It doesn't seem that hard though, I've seen threads where people provide ROMs for the Desire HD without even having the device!
Also, how would I test this and debug it? I don't think it's safe to just flash my rom once I get it compiled to my actual device and possibly brick it.. Can I use an emulator?
I hope you will read this post before answering something alike "Plenty tutorials" or "This can be found everywhere", because it can not. I can only find AOKP or CM ways, I want neither.
Greetings Ultimate-Tester
The only time I know of that this has been achieved for this device is aospX, an ICS ROM on the Inspire 4G forums. It is much harder than you would think. Google does not support this hardware, HTC does. So there was never AOSP source for this device.
Yes, I can imagine how hard it is. As I said I have programming experience, it's just that I don't have it with Android ROMS.
I have built mainly for Windows, also on Ring0 level (which is the lowest level you can get) so I think making drivers is a task I can handle. I am definitely not underestimating it.
Could anyone give me an answer to this line:
Code:
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I am very interested in how other people knew what folders to create and what files to put in them. How would the Google Source (envsetup) know which device files to use and what not? Again, can I generate the file structure somehow?
Greetings,,
My suggestion is to use device trees from AOSP-based ROMs that already exist for this device. For example, look in the cfX manifest.xml for Ace-specific stuff (kernel, device, etc.). I personally haven't seriously tried this before, so that's all I can offer.
Okidoki, will do. Then for the last item: Testing.
What will be a safe way to test out my brew?
What will actually happen if I flash a ROM with missing files? I hope there's an underlying catcher that will send something I can see in logcat and fix it that way.. Is this the case, or will I immediately brick my phone once I do something wrong? Do I need to make sure something is 100% there in order to reach my recovery again?
Greetz,,
I'm nor aware of any safety nets. If you're developing, you probably have to be willing to take the risks.
Continuing the discussion from Firefox OS is the way to go!
Hi guys!
I am new to xda-devs, but have been visiting it for useful information in the past.
I own a FP1 (First Edition) and am seeking to port FFOS to the FP1.
I do not have any developing experience, I have just done C and Java and I am comfortable with Linux's CLI.
I am following this guide: Porting Firefox OS
Currently I am stuck at the following: Create a manifest for the new device
[edit]
Which changes do I have to make to the hamachi manifest mentioned there?
I figured out, that most of the stuff is hamachi-specific and thus not required. My current manifest is attached. Could you please take a look and tell me, if this is enough?
These files are at hand:
madde on Fairphone Forum said:
Well there already is a recovery file for the fp1 + fp1u by chrmhoffmann up and running. The MTK6589 source code is kind of released and there has been a lot of work on the android code by the omnirom project, which might come in handy.
Should be definitely manageable to build and try out Firefox OS on the FP1. UnfortunatelyI'll just don't have the time to really dig into that. Maybe someone with a bit more experience can give it a shot. I'd love to see and try out the result...
Click to expand...
Click to collapse
I am inviting @madde-, @_keesj and @chrmhoffmann, I hope you, or others, can help me out.
Thanks in advance, Stefan
PS.: As I am new to xda-devs, I do not know, if my thread is in the right position and/or tagged correctly. Please give some advice on how to improve my original post.
Edit: My current manifest is attached.
I'm very interested by a portage of Firefox OS to the Fairphone
Don't have enought time to test for now, but I stay connected
Newluck77 said:
Continuing the discussion from Firefox OS is the way to go!
Hi guys!
I am new to xda-devs, but have been visiting it for useful information in the past.
I own a FP1 (First Edition) and am seeking to port FFOS to the FP1.
I do not have any developing experience, I have just done C and Java and I am comfortable with Linux's CLI.
I am following this guide: Porting Firefox OS
Currently I am stuck at the following: Create a manifest for the new device
[edit]
Which changes do I have to make to the hamachi manifest mentioned there?
I figured out, that most of the stuff is hamachi-specific and thus not required. My current manifest is attached. Could you please take a look and tell me, if this is enough?
These files are at hand:
I am inviting @madde-, @_keesj and @chrmhoffmann, I hope you, or others, can help me out.
Thanks in advance, Stefan
PS.: As I am new to xda-devs, I do not know, if my thread is in the right position and/or tagged correctly. Please give some advice on how to improve my original post.
Edit: My current manifest is attached.
Click to expand...
Click to collapse
Did you try your file out? I's think it's probably best to cut down on just the relevant settings.
madde- said:
Did you try your file out? I's think it's probably best to cut down on just the relevant settings.
Click to expand...
Click to collapse
Yes, the config.sh got stuck at like 93%.
Also I have no idea, what exactly I have to include into the manifest file. I think I need a toolchain, but I am not sure where to get one, and how to apply it. (I somehow know what it is though, I think... )
Ok, running the config.sh comes at the very end, so I probably should continue with the configuration tree[1]...
Does everything in here [2](@chrmhoffmann's repo android_device_fp_FP1) go to the configuration tree?
[1]: https://developer.mozilla.org/en-US/Firefox_OS/Developing_Firefox_OS/Porting#Create_a_configuration_tree_for_the_new_device
[2]: https://github.com/chrmhoffmann/android_device_fp_FP1
PS.: Sorry, not allowed to post links...
Newluck77 said:
Yes, the config.sh got stuck at like 93%.
Also I have no idea, what exactly I have to include into the manifest file. I think I need a toolchain, but I am not sure where to get one, and how to apply it. (I somehow know what it is though, I think... )
Ok, running the config.sh comes at the very end, so I probably should continue with the configuration tree[1]...
Does everything in here [2](@chrmhoffmann's repo android_device_fp_FP1) go to the configuration tree?
[1]: https://developer.mozilla.org/en-US...reate_a_configuration_tree_for_the_new_device
[2]: https://github.com/chrmhoffmann/android_device_fp_FP1
PS.: Sorry, not allowed to post links...
Click to expand...
Click to collapse
any progress on that? Might be able to help you a little bit in the next few weeks.
Cheers!
madde- said:
any progress on that? Might be able to help you a little bit in the next few weeks.
Cheers!
Click to expand...
Click to collapse
No haven't been able to work on this.
I still have no idea, where and how to build this configuration tree. Do you have advice on this?
Thank you, Stefan
Fyi, a build is now available. As a new user on XDA, I can not post link here (what a ****ty rule), but check bug 1139642 on bugzilla and search Fairphone on the Mozilla Developer Network (MDN) to have more info.
Wrong phone (FP1(U) vs FP2)
The build, you are referring to, is for FP2, not for FP1.
A Firefox OS for FP1 could possibly be built using the source by @chrmhoffmann: http://forum.xda-developers.com/fairphone/orig-development/rom-fairphone-fp1-kitkat-4-4-2-t3243623
Hi
I have asked this before but I haven't gotten the answer and some things have changed.
My goal is to edit the kernel of my device to include rtl8192cu driver.
I have the sources from http://gitgub.com/puresoul/android_kernel_lge_d605 (I hope I got the link right) I am currently stuck at creating the .config file and getting the right files to include the driver. Could anyone help me out, any links to tutorials that actually tell me how to? The guides online are almost all specific to a certain device or their goal is different.