Develop Bugs

[Dev] Custom roms cooking and developpement status

Hi Cookers and Devs,
We face a set of problems with Hero custom roms. The fact is that nobody has been able to port another device's rom, even a cupcake rom. We always face the same main problems: no bluetooth, no trackball, no camera, no accelerometer and, most of the time, no GPS. We all tried lots of cooking (changed many files, libs etc...) with no success.
That is why we thought we were missing kernel sources. Now we have them, we have noticed that the customization of stock android-msm sources by HTC is huge compared to, for example, the small kernel patch for sapphire 32a devices. To port the changes to 2.6.29 kernel sources, we need an expert kernel developer witch our hero dev community lacks. But, the fact that we face the same problems for porting cupcake and donut roms make me think that the kernel version is NOT the problem.
My thought is that HTC's android customization may be huge too... (android framework may have been modified) But because of android's apache license they don't have to release sources. It is a hard and long work to guess all those changes...
Concerning rom cooking, Sapphire/Dream Cookers faced the same problems porting Hero roms to there devices for a long time. Drizzy has got bluetooth fixed no so long ago.... I am sure they have the knowledge we miss. But we then face an other problem, most of those Cookers think Hero is ****,or don't want to know anything about non google branded devices, or, coming from WinMo world, have lots of difficulties sharing their knowledge...
I suggest that we, all Hero rom cookers and devs, try to port Sapphire AOSP Cupcake to Hero. Why cupcake? Because we can be sure kernel version 2.6.27 is ok with it. I am pretty sure that, once done, we will be able to port other roms.
The progress of that work would go to this thread.
What you (devs and cookers) think ?

The 3.03 ROM I posted once was based on a Sapphire.
The easiest to port is the 32A.
Though a few things weren't working as planned, and the rom was plagued with speed issues, it worked.
(sometimes, it's a matter of coupling the right init from the initrd - kernel part)
The harder part is porting ROMs which are meant to be run on a 2.6.29 kernel.
My guess?
I've taken a look at the 2.6.27/29 diff, and it isn't worth the time, to get a community-driven 2.6.29 tree.
HTC will long before that release the 2.6.29 kernel.

adwinp said:
The 3.03 ROM I posted once was based on a Sapphire.
The easiest to port is the 32A.
Though a few things weren't working as planned, and the rom was plagued with speed issues, it worked.
(sometimes, it's a matter of coupling the right init from the initrd - kernel part)
Click to expand...
Click to collapse
Was it cupcake? Did bluetooth, accelerometer, Gps worked? Any link to it?
adwinp said:
The harder part is porting ROMs which are meant to be run on a 2.6.29 kernel.
Click to expand...
Click to collapse
Well, sure it is harder, but we face about the same as porting ROMs which are meant to be run on a 2.6.27 kernel. That is what makes me think kernel version may not be the solution for most of the problems we face.
adwinp said:
My guess?
I've taken a look at the 2.6.27/29 diff, and it isn't worth the time, to get a community-driven 2.6.29 tree.
HTC will long before that release the 2.6.29 kernel.
Click to expand...
Click to collapse
Yes it worth the time. Creating a 2.6.29 branch on github easy, applying patch isn't: many rejects. And yes we'll have to wait a long time for HTC to release 2.6.29 Hero kernel sources

we need an expert kernel developer witch our hero dev community lacks
Click to expand...
Click to collapse
regarding that issue, maybe we could setup some kind of donation and give the donation as a "reward" to the "expert" dev who first can provide a working kernel...?
i know its a long shot...
and it all depends on how willing the HERO community is willing to donate...

nice going guys. i was really getting tired to see no remarkable development in hero and was planning to get an additional dream just for playing. and i was really dissappointed seeing hero cookers not giving much **** about roms and releasing nice stuffs.
now i understand what the barricades are. and yeah its true that dream and sapphire cookers really dont give **** about hero. i am creating a theme of my own and wanted to have a transparent top taskbar and top clock color black and i asked several time sin dream and sapphire threads but dint get a SINGLE reply.
however, its really true that HTC wont be giving us 2.6.29 any time soon rather will make it as longer as possible. so it would be best to try ourselves to make it ourselves. and as its really a troublesome work it wud be really great if u guys cud have worked together to get it quickly.
and as we all know none of u live on cooking roms i wud really to contribute in the donation thing as much i can. a $20 donation doesnt really hurt much to get my $700 phone going.
last but not the least... request to other fellow hero users....... please help ourselves by rising a fund of donation for our cookers so that they get enough encouragement for cooking hero roms.
regards

have you taken into consideration that eclair is about to come? i don't want to take the fun out of it, in fact i think it is a very good idea what lox proposed here. but i myself find myself rather reluctant to try to mod anything except tweaking mcr2.9 a little more... not that i had the capabilities to seriously do some kernel hacking/modding/developing, but at least i was able to compile my own working kernel, so i am not completely clueless.
again, don't want to take the fun out of it, i would just imagine that you have a hard time motivating members to donate 1.5/1.6 improvement, when eclair is just around the edge...

kendong2 said:
have you taken into consideration that eclair is about to come? i don't want to take the fun out of it, in fact i think it is a very good idea what lox proposed here. but i myself find myself rather reluctant to try to mod anything except tweaking mcr2.9 a little more... not that i had the capabilities to seriously do some kernel hacking/modding/developing, but at least i was able to compile my own working kernel, so i am not completely clueless.
again, don't want to take the fun out of it, i would just imagine that you have a hard time motivating members to donate 1.5/1.6 improvement, when eclair is just around the edge...
Click to expand...
Click to collapse
bro dont get me wrong......... but do u really beleive that htc is going to give us eclair in 1-2 months? i mean if they were this kind then why they dint kernel or source code for hero earlier? do u think htc will release better os for a phone which is already 7 months old rather upgrading the new released phones and releasing new handsets? bro those phone companies are here for doing business , not serving customer's after sales needs.
if u still want to wait believing that htc is ur friend then its ur call and best of luck with that. but after buying these costly handsets for last 6-7 years i know it very well that nokia, samsung, htc never going to keep their promises regarding firmwares.

dying4004 said:
bro dont get me wrong......... but do u really beleive that htc is going to give us eclair in 1-2 months? i mean if they were this kind then why they dint kernel or source code for hero earlier? do u think htc will release better os for a phone which is already 7 months old rather upgrading the new released phones and releasing new handsets? bro those phone companies are here for doing business , not serving customer's after sales needs.
if u still want to wait believing that htc is ur friend then its ur call and best of luck with that. but after buying these costly handsets for last 6-7 years i know it very well that nokia, samsung, htc never going to keep their promises regarding firmwares.
Click to expand...
Click to collapse
well obviously you have more experience with the smartphone stuff, my (first and) last one (before the hero) died in 2005... but i won't give up the hope
all i am saying is that this should be taken into consideration, before anyone starts a donation run that ends up having collected 160$ and a whole bunch of disappointed members...

kendong2 said:
well obviously you have more experience with the smartphone stuff, my (first and) last one (before the hero) died in 2005... but i won't give up the hope
all i am saying is that this should be taken into consideration, before anyone starts a donation run that ends up having collected 160$ and a whole bunch of disappointed members...
Click to expand...
Click to collapse
bro i completely understand what u wanna say as the money we want to donate has to be earned by hard work by us. but u be sure that it will be at least 4-5 months before u get full eclair for hero. and i recon if our devs work unitedly and gets some expert help from outside then its possible to get 2.6.29 kernel and other things in 1-1.5 month.

Lox_Dev said:
And yes we'll have to wait a long time for HTC to release 2.6.29 Hero kernel sources
Click to expand...
Click to collapse
Given that HTC haven't shipped a Hero with a 2.6.29 kernel, they have no requirement to do so!
HOWEVER......
What about the Tattoo? That's Donut, so it will have a 2.6.29 kernel, and therefore HTC must provide the kernel source. I'll wager there is some significant similarity between the kernel modifications required for Hero and those required for the Tattoo.
Perhaps it is time for us to start badgering HTC for the Tattoo kernel source!
FWIW, I've been trying to build a 2.6.29 kernel using a diff patch for AOSP 2.6.27 vs Hero 2.6.27, but I seem to be thwarted at every turn.
Regards,
Dave

dying4004 said:
bro dont get me wrong......... but do u really beleive that htc is going to give us eclair in 1-2 months? i mean if they were this kind then why they dint kernel or source code for hero earlier? do u think htc will release better os for a phone which is already 7 months old rather upgrading the new released phones and releasing new handsets? bro those phone companies are here for doing business , not serving customer's after sales needs.
if u still want to wait believing that htc is ur friend then its ur call and best of luck with that. but after buying these costly handsets for last 6-7 years i know it very well that nokia, samsung, htc never going to keep their promises regarding firmwares.
Click to expand...
Click to collapse
Ok i am speechless now .... i mean i have to agree with "dying4004"... These companies are really only making money and dont give a rat's ass about customer services and after sales... i mean thats the real logic behind it right... WOW u have opened my eyes dude ....
but BRO i wanted some insight into something that has been induced into our brains for so long... Without customers companies cant make money... i mean any one with a brain would obviously not go for a company that has screwed him over with false promises, right? Yet all the companies ( or should i say SATAN WORSHIPERS ) are still in the bidnes and still making money and people ( minions ) are still buying products from these companies...
i did some thinking and i remember i had a HTC diamond and the track pad was a bit faulty so i took it to the Htc service center and they REPLACED the trackpad !!! i mean what atrocity innit... EVIL EVIL EVIL ...
lolz ... dying4004 why are you against these companies and more so why are u hell bent on preaching a March-April release of Eclair for Hero.... i have seen u do that in other threads as well....
If u have had a bad experience with one of these companies, please do share coz i am begining to think that it will make for an interesting listen.

nadeemhasnaat said:
Ok i am speechless now .... i mean i have to agree with "dying4004"... These companies are really only making money and dont give a rat's ass about customer services and after sales... i mean thats the real logic behind it right... WOW u have opened my eyes dude ....
but BRO i wanted some insight into something that has been induced into our brains for so long... Without customers companies cant make money... i mean any one with a brain would obviously not go for a company that has screwed him over with false promises, right? Yet all the companies ( or should i say SATAN WORSHIPERS ) are still in the bidnes and still making money and people ( minions ) are still buying products from these companies...
i did some thinking and i remember i had a HTC diamond and the track pad was a bit faulty so i took it to the Htc service center and they REPLACED the trackpad !!! i mean what atrocity innit... EVIL EVIL EVIL ...
lolz ... dying4004 why are you against these companies and more so why are u hell bent on preaching a March-April release of Eclair for Hero.... i have seen u do that in other threads as well....
If u have had a bad experience with one of these companies, please do share coz i am begining to think that it will make for an interesting listen.
Click to expand...
Click to collapse
bro i am not against all those companies. i mean then i cant use any mobile phone. i am just practical. just see how the nokia users r complaining about firmwares for their high end phones. how much craving is going within the 5800 users for kinetic scrolling. check how much impatience is going through the samsung omnia i8910 users for a single new rom. see how u guys did for the source code for hero. what i am saying is simple......... it wont be a good idea to stop development of recent hero roms just for the sake of eclair which we dont know when gets release. rest is upto u. i cant force any1 to do anything. this is simply my personal experience with mobile phone manufacturers for last 7-8 years. cheers

Great post Lox_Dev and thank you for bring all the problems to our attention. It is heartbreaking to see such a great little phone be left to stew on the few HTC "released" roms out there. I dont confess to know that much about kernel building so I wont be much help there however I do believe we as a community can get there in the end! What I'm trying to say is dont give i
Lox_Dev
behnaam
adwinp
and of course Paul from MoDaCo who first started the ball rolling
we are all behind you guys!
I know its so different from cooking Windows rom (because I've tried myself) but I think in time anything can be done and please dont be put off by the lack of responses you get on this forum.
Now onto the positive .................... Once my internet connection at home gets sorted (VirginMedia to send me a replacement modem) I'll have another look at building a linux environment and jump aboard.

dying4004 said:
it wont be a good idea to stop development of recent hero roms just for the sake of eclair which we dont know when gets release. rest is upto u.
Click to expand...
Click to collapse
If you are *so* concerned, what precisely is stopping you from doing this yourself?
Note, saying you don't know how is not good enough, because it can be learned.
Regards,
Dave

foxmeister said:
If you are *so* concerned, what precisely is stopping you from doing this yourself?
Note, saying you don't know how is not good enough, because it can be learned.
Regards,
Dave
Click to expand...
Click to collapse
hey bro.... exactly where did i say that i dont know how to do and stuffs?? at 1sy read then post ur comments......... and in this thread i said i am willing to donate for the work and i asked others to donate as well to contribute in the way we can.
and i have made and posted 1 theme for hero and i have made another theme and i will post it tomorow. so read before u speak.

dying4004 said:
hey bro.... exactly where did i say that i dont know how to do and stuffs?? at 1sy read then post ur comments......... and in this thread i said i am willing to donate for the work and i asked others to donate as well to contribute in the way we can.
and i have made and posted 1 theme for hero and i have made another theme and i will post it tomorow. so read before u speak.
Click to expand...
Click to collapse
(My emphasis!)
You should follow your own advice!
I asked a question:
If you are *so* concerned, what precisely is stopping you from doing this yourself?
Click to expand...
Click to collapse
And then said:
Note, saying you don't know how is not good enough, because it can be learned.
Click to expand...
Click to collapse
This is merely pointing out that if your *answer* to my question is "I don't know how to do it", you could always learn!
Nowhere do I say that you "dont know how to do and stuffs??".
And you still haven't answered the question!
Regards,
Dave

yes i am learning and i am excercising my knowledge in makling theme for the community. at least i am doing what i can. i am even willing to donate for the devs.
and what u r doing? shouting on ppl who can do sumthing and doing nothing urself as u cant even learn and want to use others works.
go learn sumthing, show us and then shout at others.

dying4004 said:
yes i am learning and i am excercising my knowledge in makling theme for the community. at least i am doing what i can. i am even willing to donate for the devs.
and what u r doing? shouting on ppl who can do sumthing and doing nothing urself as u cant even learn and want to use others works.
Click to expand...
Click to collapse
I thought that was what you were doing?
I've never "shouted" at any one, or tried to push any one into doing something that is likely to be a waste of time due to the arrival of an HTC built 2.0 and which I personally *know* is extremely difficult.
How do I know?
Because I've tried it!!!!
Here's what I have done:
1. Built an Ubuntu development environment *expressly* for these purposes.
2. Downloaded the Hero kernel sources and the stock 2.6.27 sources.
3. Diff'd the two trees to see what needs patching
4. Downloaded the 2.6.29 kernel sources
5. Attemped to apply the patch from (3) to 2.6.29
6. Built the kernel
7. Put in on my phone, with the CleanION ROM.
8. Watched in awe as it just hung as the boot splash screen until I pulled the battery out.
Note that even getting the AOSP kernel source from the git repos proved to a hellishly time consuming task because the repos kept timing out and/or refusing connection!
Despite my efforts, I've not turned up *any* tangible results, which is why I've not bothered to mention them here. I'm at the point now where I don't know if I want to commit any further time and effort on what is essentially a fools errand. I'm not saying that my efforts were anything particularly "special", but certainly I can say with absolutely honesty that I've tried!
When Lox_Dev says "To port the changes to 2.6.29 kernel sources, we need an expert kernel developer witch our hero dev community lacks", I know for a fact that this is true, so it is getting quite irritating to keep hearing people who "don't know" telling those of us who "do know" that we should all be getting together to make it work!
So, in absolutely no way am I "shouting on ppl who can do sumthing and doing nothing urself as u cant even learn and want to use others works", because I have already expended far more time and effort than most.
go learn sumthing, show us and then shout at others.
Click to expand...
Click to collapse
Once again, I suggest that you take your own advice!
regards,
Dave

I'm all for working on porting AOSP Sapphire to the Hero, but some of us need a bit more guidance on getting their development/cooking environment set up. There's a shocking amount of information out there, and it makes breaking into the 'scene' a bit difficult.
Accelerometer should be the focus of our work (in my opinion) since without the keyboard, it's really hard to get some things done in the portrait mode. I'd love to focus on that, since the Google ION Rom with Donut makes me incredibly happy, with that exception.

okay, bros, just to contribute a little bit:
http://www.youtube.com/v/FLRqOuB798A
Seeing that, and imagining it's working 100% and running on our Hero's, really makes me hard.
We will get there. But yes, the path will be difficult. I also want to donate btw.
Anyway, HTC indeed doesn't give a F--- about our android OS. they will release 800*480 handsets in 1-3 months, and maybe won't even port the UI elements to our resolution/hero.
In a way, we are F---ed, we have a very old android handset, with not even half the capabilities of new ones like the droid or upcoming x10 or HTC handsets. And without the knowledge to port all of the new kernels (with parts missing, ie; the hero kernel supposedly had parts missing) they phone might even grow older every month. I a way I should be happy I payed 340 Euro instead of 480 or something..
So yeah, in a way I believe that the handset will be discontinued very shortly. The G1 has the community to back it up, people had it for more than a year and grew attached to it. The Hero does not have that luxury.
So while the hope lies in you, developers; aside from 'homebrew' i'm afraid the future is very bleak. HTC wants your money. They can target little girls tomorrow and kids who just want a 'cool' phone, and we will be left in the cold for children who get a new phone with the contract every year.
So power to the developers!

3d Enhancement (dev only)

Ok, so my last gralloc test failed because i didnt allocate memory properly. But if yo u want o build your own gralloc for wvga.. this is what you need.
Increasing ALLOCATORREGION_RESERVED_SIZE from (2400<<10) to (3000<<10) is a must (800x480x4x2) = 3000<<10 which matches qcom lib i modified.
My main goal now is to see if we do benefit at all from a 2+13 mem configuration on pmem. Also people reported sound going out with these changes. Anyone care to help debug ?
Also look at the gralloc line
#define FB_ARENA HW3D_EBI
We can specify here if we want to use ebi or smi. Since we do have 7mb on smi, why not test it out

bump to keep it in view

no one gives a f*ck...

actually it more like us non devs dont post in threads like this as its for dev purposes only while the devs seem to be busy. Hopefully someone will have some free time and look into this and give us that last but of juice. BTW i tried tiads latest package with ur lib and grallock and i dunno whatelse he did got a quadrant score of 594 so things are looking up for us ( too bad neocore still is 18.1)

docnas said:
actually it more like us non devs dont post in threads like this as its for dev purposes only while the devs seem to be busy. Hopefully someone will have some free time and look into this and give us that last but of juice. BTW i tried tiads latest package with ur lib and grallock and i dunno whatelse he did got a quadrant score of 594 so things are looking up for us ( too bad neocore still is 18.1)
Click to expand...
Click to collapse
devs are busy? that explains it.. i wonder when these busy devs will make some time and work

[ACL] said:
devs are busy? that explains it.. i wonder when these busy devs will make some time and work
Click to expand...
Click to collapse
I give a f*ck but I don't know sh*t about this stuff...

@ACL hmm i should have added the fact the devs (besides you oh great porter of the .35 fb) are doing other projects btw im not being sarcastic im amazed at the work and effort you actually put into this too bad my coding skills are limited to following directions and usually getting that wrong too

docnas said:
@ACL hmm i should have added the fact the devs (besides you oh great porter of the .35 fb) are doing other projects btw im not being sarcastic im amazed at the work and effort you actually put into this too bad my coding skills are limited to following directions and usually getting that wrong too
Click to expand...
Click to collapse
..
its all good. Actually the reason for the post was to encourage others to join the devs. The kernel team is actually a tight group who communicates almost on a daily basis, so i know who works on this and who doesnt. But it never hurts to ask the crowd. Thats how i met wozzer and nate actually so i'll do it from time to time in hope someone has some free time and programming experience to help.
Sorry for my sarcasm.. its a gift and a curse..

CM will not support HERO until we have an active developer....

CM will not support HERO until we have an active developer....
http://forum.cyanogenmod.com/forum-78/announcement-16-hero-gsm-cm-7/
We knew that this could happen soon or later so..... who's gonna move next?¿?, Erasmux, Elelinux, ....., Feeyo??¿?¿, We really need a CM maintainer...
Perdita2000
Thanks to All

Oh no
bad news !

I guess our Hero is at the end of his life...

yukinok25 said:
I guess our Hero is at the end of his life...
Click to expand...
Click to collapse
The twilight years are offering fine fruits....2.3 with sens is getting there, and an miui port..
my device holds optimism, no redundancy just yet

I do not think the Hero is dead. There are still actively maintained ROMs for the Hero.
CM for Hero is dormant because it is lacking a maintainer, nothing more.
It now becomes more important for the active maintainers of the Hero ROMs to contribute their Hero-specific patches back upstream to Cyanogen. Or hopefully one of maintainers of the other ROMs steps up to take over the maintenance of CM for Hero.

I have a 2.2 Rom thats stable and smooth and honestly I would like to see devs continue to work on our devices but I personnally do not see a need for it...surely one or two nice updates are always nice to have around but I think software wise we are at the end of what the hero can handle anyways (though I am not an expert at all)

Funny that everyone thinks its over for the Hero. The CM6 Dev was crap to. But it was easier since there where way less starter problems. But Ninpo was the one who fixed a lot of stuff for that. And send it upstream to CM. Not Loxdev or someone else. ATM we dont have any dev that is sending stuff upstream.
Feeyo fixed a lot. But he is not sending it, I must say I Agree in some points with him. Elelinux his build is still with the annoying bug so that is a no go, and as far as I know not really sending stuff their way.
In short the hero dev is ran, and has been ran a long time from the individuall devs for a long time.

my god,i like cm's rom,it's so good
Sent from my HTC Hero using XDA Premium App

i didn't know none of them where sending it back to cyanogen, but the thing is look at hero cdma thread and you'll see the huge difference in support than ours :/

keyra74 said:
i didn't know none of them where sending it back to cyanogen, but the thing is look at hero cdma thread and you'll see the huge difference in support than ours :/
Click to expand...
Click to collapse
CDMA is different at all, cuss a lot in the USA got that phone and well most of the EU guys got a new one. So that is a small prob there.

There is no valid reason for not sending any changes upstream rdejager

riemervdzee said:
There is no valid reason for not sending any changes upstream rdejager
Click to expand...
Click to collapse
well, laziness maybe. but I'm quite certain that isn't the motivating factor for feeyo and some others ;-)

I agree riemervdzee, why not sending bugs fixes back to CM?¿?¿?, In fact, I think we really need a good base ROM and others around making changes for getting better, but CM is the base ROM after all...
Perdita2000

I think it is time to start thinking of a phone replacement. Incredible S maybe?

wdaccache said:
I think it is time to start thinking of a phone replacement. Incredible S maybe?
Click to expand...
Click to collapse
Which you can not root....

erasmux said:
Which you can not root....
Click to expand...
Click to collapse
Lol I keep coming back to my hero for my Rom fixes as my se arc is rooted but not getting much Dev love think I have been spoilt Here ;-)
Sent from my LT15i using Tapatalk

erasmux said:
Which you can not root....
Click to expand...
Click to collapse
indeed, i'm gonna go for the Samsung Galaxy SII...root is just around the corner, and an unlocked bootloader

erasmux said:
Which you can not root....
Click to expand...
Click to collapse
Any suggestions erasmux? what phone are you going to be packing?

i think best are:
1. Samsung Galaxy S II (Maybe Galaxy S 3 coming this year ^^)
2. HTC Sensation
3. I think this one can be realy nice: LG Optimus 3D
my 3 favorites atm

ggrammer said:
Any suggestions erasmux? what phone are you going to be packing?
Click to expand...
Click to collapse
I have no idea. Samsung seems like a logical choice because it have good specs and does seem like its not impossible to unlock it Still I find that the Samsung quality is at least one level down from HTC.... But HTC is bootloader locking their newer devices.
So it really is a tough call. Anyway don't have the money for a new device now anyway, so for now I'll stick to the good old hero

miui port

http://forum.xda-developers.com/showthread.php?t=1827256
http://forum.xda-developers.com/showthread.php?t=1483332
http://forum.xda-developers.com/showthread.php?t=1957219
I know this is a question but I'm hoping to get some help on development for this and the info I gather may be usefuluseful for other ROM development

I guess what I'm mainly asking for is someone with dev experience to help me walk through setting up my environment and getting this going, and someone who doesn't mind endless newbish questions. And possibly doing a little bit of development along side of me if I run into something I can't handle

idontwanttobeanoob said:
I guess what I'm mainly asking for is someone with dev experience to help me walk through setting up my environment and getting this going, and someone who doesn't mind endless newbish questions. And possibly doing a little bit of development along side of me if I run into something I can't handle
Click to expand...
Click to collapse
I should have a disclaimer that I am not a full developer really and anything I say can and should be corrected by a real dev but I tend to know a good deal more than the average end user so therefore I try and help where I can
That said, from what I've seen from other devs getting the ROM on the device isn't that hard once you know how and assuming it's not some tricky ROM meant for a specific device (that said, MIUI is the kind of ROM that to me seems like it should be easy to get on a wide number of devices). So, if you want MIUI, it's probably best to ask for someone to port it and if it isn't too hard (I don't think it is) it's just a matter of the dev being nice enough
Teaching you to compile the ROM on your own though, may actually take a lot more time and effort. If you want to learn to make ROMs, which actually is rather easy compared to other parts of developing if you're not making your own from scratch, you could learn to do that, but it's probably better to learn the basics and go to a thread for it.
If you just want MIUI for your KF2, it's probably easiest to ask a dev to do it for you.
As always, any dev feel free to correct me if I'm wrong

iytrix said:
I should have a disclaimer that I am not a full developer really and anything I say can and should be corrected by a real dev but I tend to know a good deal more than the average end user so therefore I try and help where I can
That said, from what I've seen from other devs getting the ROM on the device isn't that hard once you know how and assuming it's not some tricky ROM meant for a specific device (that said, MIUI is the kind of ROM that to me seems like it should be easy to get on a wide number of devices). So, if you want MIUI, it's probably best to ask for someone to port it and if it isn't too hard (I don't think it is) it's just a matter of the dev being nice enough
Teaching you to compile the ROM on your own though, may actually take a lot more time and effort. If you want to learn to make ROMs, which actually is rather easy compared to other parts of developing if you're not making your own from scratch, you could learn to do that, but it's probably better to learn the basics and go to a thread for it.
If you just want MIUI for your KF2, it's probably easiest to ask a dev to do it for you.
As always, any dev feel free to correct me if I'm wrong
Click to expand...
Click to collapse
I'm actually finishing up my college work then I'm setting up my environment. I don't believe getting at least an alpha build up and running will bentha hard, I just need someone to double check my work so that no one is bricking their device due to a mistake I make
On the note of questions, is it possible to make a suitable Linux environment with the wubi installer?

Setting up Ubuntu now

base and port rom downloading now, ill keep everyone up to date with progress

Any update? para would be a nice port also! I tried but couldn't get it to boot...

Chrisbabs85 said:
Any update? para would be a nice port also! I tried but couldn't get it to boot...
Click to expand...
Click to collapse
Biggest issue I'm having is finding the tools and getting the drivers to work on Ubuntu. Its a bit of a learning curve but no worries I'll get this baby working. Also got a project I'm helping a friend with for the nook.

idontwanttobeanoob said:
Biggest issue I'm having is finding the tools and getting the drivers to work on Ubuntu. Its a bit of a learning curve but no worries I'll get this baby working. Also got a project I'm helping a friend with for the nook.
Click to expand...
Click to collapse
Also what device does para run on? Easiest way to port a ROM is make sure its one that already works on a similar device ( porting miui for kindle fire to the kindle fire 2) also the ROM your trying to port should have the same screen density. The three links up top seem to be excellent sources of information

for anyone thats interested i believe im almost done with an alpha version of the port, im asking a few newbish questions as im teaching myself as i go and im gonna try to have some people take a look at what i did just to make sure theres no insta brick on flashing it.

idontwanttobeanoob said:
for anyone thats interested i believe im almost done with an alpha version of the port, im asking a few newbish questions as im teaching myself as i go and im gonna try to have some people take a look at what i did just to make sure theres no insta brick on flashing it.
Click to expand...
Click to collapse
Hi mate, I'll test it! thanks for links going to check them out, I know paranoid runs on nexus 7 I will have to check
Cheers!

Chrisbabs85 said:
Hi mate, I'll test it! thanks for links going to check them out, I know paranoid runs on nexus 7 I will have to check
Cheers!
Click to expand...
Click to collapse
Once I get some help with the update script and have someone take a look at the files to see if they can see any major issues I'll upload it and send you a link. However basic disclaimer around here applies.... If the world ends etc I take no responsibility. Ie don't sue me lol. But that being said can't wait to finish this.

idontwanttobeanoob said:
Once I get some help with the update script and have someone take a look at the files to see if they can see any major issues I'll upload it and send you a link. However basic disclaimer around here applies.... If the world ends etc I take no responsibility. Ie don't sue me lol. But that being said can't wait to finish this.
Click to expand...
Click to collapse
Oh wow. Nice progress! It's good to see more development around here! I'm glad you found the help you need and everything went smoothly (so far)
Best of luck!

iytrix said:
Oh wow. Nice progress! It's good to see more development around here! I'm glad you found the help you need and everything went smoothly (so far)
Best of luck!
Click to expand...
Click to collapse
Thanks
So far I'm stuck until I can either a figure out update scripts myself or I get some help. Everything seems OK but till I can try to boot this myself I can't really tell. Also once the HD codec issue is fixed I'll be merging that, I'll also be taking suggestions for fixes.

idontwanttobeanoob said:
Thanks
So far I'm stuck until I can either a figure out update scripts myself or I get some help. Everything seems OK but till I can try to boot this myself I can't really tell. Also once the HD codec issue is fixed I'll be merging that, I'll also be taking suggestions for fixes.
Click to expand...
Click to collapse
Update script should be fairly easy just compare the base and port I guess?
I got Ubuntu set-up and I'm going to begin porting paranoid. Also don't worry I have a few test devices

idontwanttobeanoob said:
Thanks
So far I'm stuck until I can either a figure out update scripts myself or I get some help. Everything seems OK but till I can try to boot this myself I can't really tell. Also once the HD codec issue is fixed I'll be merging that, I'll also be taking suggestions for fixes.
Click to expand...
Click to collapse
Oh I forgot about HD....hmmm. I am not sure how difficult patching things from other ROMs in is, but it seems like the next hascode release should fix most if not everything majorly wrong and I think that would be a better base point for building ROMs. It could be easy though and the thing is pretty damn stable. I've only ever had one issue beyond HD and re-flashing fix it so, possibly this is a good build to work off of
Yeah, it seems no one is really on right now but later they may be able to help, especially in IRC

Chrisbabs85 said:
Update script should be fairly easy just compare the base and port I guess?
I got Ubuntu set-up and I'm going to begin porting paranoid. Also don't worry I have a few test devices
Click to expand...
Click to collapse
One would assume but with semi limited knowledge on them I come to two assumptions, first off is the simple fact that I know the partition tables are different. So if the script tries to send something somewhere it doesn't belong it could be bad, second I see some differences in the scripts that I don't understand and there for do not want to mess with them until I do or someone who does will explain.
My goal is to not brick any testers kfires just seems bad for business

idontwanttobeanoob said:
One would assume but with semi limited knowledge on them I come to two assumptions, first off is the simple fact that I know the partition tables are different. So if the script tries to send something somewhere it doesn't belong it could be bad, second I see some differences in the scripts that I don't understand and there for do not want to mess with them until I do or someone who does will explain.
My goal is to not brick any testers kfires just seems bad for business
Click to expand...
Click to collapse
:good:

Chrisbabs85 said:
:good:
Click to expand...
Click to collapse
After looking more in depth at the update script I saw one major difference...
Which is to do with the dev/block
So I went with the previous ROMs update script and I'm making the zip for initial testing now.
Fingers crossed

idontwanttobeanoob said:
After looking more in depth at the update script I saw one major difference...
Which is to do with the dev/block
So I went with the previous ROMs update script and I'm making the zip for initial testing now.
Fingers crossed
Click to expand...
Click to collapse
Good luck mate, if you think it's OK send me the link for testing...
Cheers!

why are we waiting...

Waiting for the sources that is, what are porters planning on sticking on this? Personally I want the sources to attempt to port Sailfish, only reason I bough the phone. I currently have the Nexus 5 and the OS runs buttery smooth thanks to the porters over at #sailfishos-porters
Am even wondering did I make a mistake buying this device when the Nexus 5, is more than enough omph to power the OS. But I've got it and gotta try, to atleast expand my own knowledge base.
also do you guys know how chainfire managed to build the kernel for it without the sources?

WTF?
The phone has been out for less than a month. Have some patience or start learning to develop yourself, rather than creating a useless thread, just to whine.

I got my 5x last Tuesday and forgot how little I like "pure" android. I think the usual progression is flash aosp then flash cyanogenmod once the nightlies start to stabilize. I know I'm in the minority but the nexus phones usually have too much Google on them for my taste. I like the hardware, but the software is another story.
At any rate, I'm also waiting for the binaries and device tree so that I can start building my own.

m4r0v3r said:
Waiting for the sources that is, what are porters planning on sticking on this? Personally I want the sources to attempt to port Sailfish, only reason I bough the phone. I currently have the Nexus 5 and the OS runs buttery smooth thanks to the porters over at #sailfishos-porters
Am even wondering did I make a mistake buying this device when the Nexus 5, is more than enough omph to power the OS. But I've got it and gotta try, to atleast expand my own knowledge base.
also do you guys know how chainfire managed to build the kernel for it without the sources?
Click to expand...
Click to collapse
If you knew much about how android works, you'd know that chainfire didn't make a kernel. He took the boot image and modified some fstab, prop, and sepolicy stuff, repackaged it, and released it. He didn't build his own kernel.
In any case, I'm curious about this, how long does it usually take google to release their sources?
Sent from my Nexus 5X using Tapatalk

sn0warmy said:
WTF?
The phone has been out for less than a month. Have some patience or start learning to develop yourself, rather than creating a useless thread, just to whine.
Click to expand...
Click to collapse
oh yeah Ill just go and create a kernel, and while am at it, I may as well write my own drivers. Maybe I'll call my kernel linox, and adopt this policy of sharing my source code so other people could collaborate. Maybe using some sort of version control, call Hit or something, maybe on some website called HitHub.
Yeah that sounds like a good way to develop it...Or Google could hurry the **** up and release the sources and binaries so I wouldn't have to.
Well if you read my post you'd see I was curious about what people wanted to port.
drsn0w said:
If you knew much about how android works, you'd know that chainfire didn't make a kernel. He took the boot image and modified some fstab, prop, and sepolicy stuff, repackaged it, and released it. He didn't build his own kernel.
In any case, I'm curious about this, how long does it usually take google to release their sources?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Not make but people have been saying it was built with forceencrypt disabled so I thought he built the kernel with that flag, (ie he had the sources). But it seems thats not the place to change it

Wow the self-entitlement is real nowadays, patience bro. You cant have everything instantly when you want it.
m4r0v3r said:
oh yeah Ill just go and create a kernel, and while am at it, I may as well write my own drivers. Maybe I'll call my kernel linox, and adopt this policy of sharing my source code so other people could collaborate. Maybe using some sort of version control, call Hit or something, maybe on some website called HitHub.
Yeah that sounds like a good way to develop it...Or Google could hurry the **** up and release the sources and binaries so I wouldn't have to.
Well if you read my post you'd see I was curious about what people wanted to port.
Not make but people have been saying it was built with forceencrypt disabled so I thought he built the kernel with that flag, (ie he had the sources). But it seems thats not the place to change it
Click to expand...
Click to collapse

timjp692 said:
Wow the self-entitlement is real nowadays, patience bro. You cant have everything instantly when you want it.
Click to expand...
Click to collapse
what to expect an open source based phone to have the sources with it?
No I know I can't have everything when I instantly want it, but really what could be the reason for the delay. Since am already pretty pissed about the force encryption.

m4r0v3r said:
what to expect an open source based phone to have the sources with it?
No I know I can't have everything when I instantly want it, but really what could be the reason for the delay. Since am already pretty pissed about the force encryption.
Click to expand...
Click to collapse
I'm sorry, but you sound like a whiney little 12 year old who is used to having everything they want RIGHT when they want it. Kind of sums up the turn this forum has taken over the past couple of years.
In the real world you'll learn that good things take time. The phrase, "patience is a virtue" holds true merit.

Offer a bounty if you're that impatient.

sn0warmy said:
I'm sorry, but you sound like a whiney little 12 year old who is used to having everything they want RIGHT when they want it. Kind of sums up the turn this forum has taken over the past couple of years.
In the real world you'll learn that good things take time. The phrase, "patience is a virtue" holds true merit.
Click to expand...
Click to collapse
Apology accepted.

bblzd said:
Offer a bounty if you're that impatient.
Click to expand...
Click to collapse
For what exactly? Someone to break in Google servers and take the source code? lol

m4r0v3r said:
For what exactly? Someone to break in Google servers and take the source code? lol
Click to expand...
Click to collapse
I'm waiting too- it's not like google is still working on the binary drivers and just building the production rom with hacked up device trees until they get the real ones. I could be mis-remembering, but in the past, I thought the factory roms and binary drivers were available the day the devices were released.
I can certainly understand being patient with devs who are working on roms (for free/beer/donations), but google is done with the rom and has already released it to production. The factory image for the 6p was delayed as well. It's not a secret- they are going to push it to every one who bought a phone. My conspiracy theory is that google is trying to bury aosp, and merging android and chrome will be another stab into the heart of both privacy and freedom.

and its outtt

m4r0v3r said:
and its outtt
Click to expand...
Click to collapse
Waiting for some real nexus thing then