Related
To all:
I am very interested in getting balls deep into the development/"porting" of the Sense UI to CM6 or a vanilla 2.2 kernel for the Moto Droid. I realize that none of the Sense UI based official source is available at this time - but it will be. I am willing to invest time and money into this effort. I think it will be a great learning experience too. Please let me know if you're interested and what your current skillset is.
My android experience is limited to compiling kernels and medicore java development. I've been doing *nix development for ~5 years now and would like transition deeper into the android (low level) development world.
Thanks.
sounds great i am a huge fan of zusedroid and 2.2 i swich between the to all the time and seeing that someone is willing to work on it is great because i saw the zd team slowly fall apart or as it seems i think they just gave up on it or somthing or they all just got a droid x but great news i would be willing to healp but i dont know what i would have to offer o well i think u should port frome the droid incredible because it is gsm and not cdma like the diser or the nexusthiss one should be hard but easyer than what zd had to put wp with
id love to see this go into a full port. i've been using the zeusdroid for now, the drawbacks suck but i love the htc sense so i put up with the flaws.
helping financially is tough as i am a full time student, however i am upon my last year of electrical engineering, but no major programing or developing experience however if there's something i can tackle i'll be happy to try
monty_boy said:
To all:
I am very interested in getting balls deep into the development/"porting" of the Sense UI to CM6 or a vanilla 2.2 kernel for the Moto Droid. I realize that none of the Sense UI based official source is available at this time - but it will be. I am willing to invest time and money into this effort. I think it will be a great learning experience too. Please let me know if you're interested and what your current skillset is.
My android experience is limited to compiling kernels and medicore java development. I've been doing *nix development for ~5 years now and would like transition deeper into the android (low level) development world.
Thanks.
Click to expand...
Click to collapse
umm i just started a thread where i have PORTED sense 2.2 to the droid it IS NOT fully working and i need more devs to help me.
Does it boot up fully or boot loop because if it fully boots I would love to try
bmx24 said:
Does it boot up fully or boot loop because if it fully boots I would love to try
Click to expand...
Click to collapse
It boots up fully to sense ui but it's not fully functional yet.
i would LOVE a completely working 2.2 sense rom for the droid. i think the droid incredible would definitely be the thing to work with to make it happen. I cant help do it, but i will definitely donate a ton AFTER a completely working rom is made, and i think a lot of other people would too.
maybe you could recruit someone from the original zeusdroid team.
please please make this work, that would be amazing. good luck, and donations would come, if its completed
Just a bit of random knowledge - CM is an EXCELLENT rom, as a project of its own. It is built from source and heavily modified. With great power, comes great responsibility. It can be further modified, but is in no way a good start point for porting a pre-built rom. I am speaking from experience in saying that it is a VERY customized build. You are FAR better starting with sense, and a stock rom to splice in. I made the mistake of thinking I could use a CM build as a start when porting sense to the mytouch. 3 Migraines later, I realized what the issue was, and while parts of CM could be ported to sense, sense was not being ported to CM.
Example - Take the stock 84B Boot image and slap it on any rom and you will see that all of them function except CM. The boot and system are built together, which is efficient when it is released as a complete package, but again, not good for using as a start to any hack and slash project.
That said, the best option is to get parts from Zeusdroid Alpha, parts from Milestone MotoSense, and have a chat with barak and eugene about how they ported the original Milestone firmware to Droid, and combine this knowledge
With the buildbots not up yet, I've been working on a little project in secret for a while. I call it Cyanobread. My plan here is to make a CM7 that has all of CM 6.1's bells and whistles before the CM7 team does. Some patches I will probably submit, and some will be only for this ROM as they go against the ideas of what Cyanogen wants. I haven't decided yet if I will keep this updated once the buildbots come back. If it divulges from the CM7 project significantly than probably.... otherwise I will just keep this as a mod for a few patches you can add to CM7.
My philosophy behind doing this ROM is the fact that I love CM6 and have used the nightlies as my daily driver and was very dissapointed 7 wasn't up on the buildbots.
Even though this is mostly a CM7Src ROM, please report any bugs here and I will do my best to either report them to the CM Team or fix them myself if I can. Same thing goes for any features you'd like to see added.
My approach to deving is a very collaborative one. Invisiblek, jladronka and DS36 will be helping me with this project. If any other devs would like to help, please shoot me a PM. The more the merrier, I really want to see a nice group project out of this.
Screenshots :Comming Soon
Version 1: Download Coming Soon!
reserved.... I've always wanted to do that
Sounds swell. Can't wait to give it a whirl! Thanks!
Sent from my Incredible using XDA App
Im all over it
I'm very interested in this.
You let me know if PSX4droid works and I'll be all over this ROM.
Ruggerxpunk said:
You let me know if PSX4droid works and I'll be all over this ROM.
Click to expand...
Click to collapse
You could also, you know, test it out yourself.
Just saying...
Interesting (but then again, I'm a ROM hua), I'm on board.
I'm also interested in Cyanocomb when it's ready. ;-)
sounds interesting, i'll definitely try it
Looking forward to it.....I know I should not ask, but.....ETA?
lol I dont go by the No ETA rule so long as you dont mind if you're wrong.
well this has been an in work project for a few weeks... finally had a full compile this morning but was missing some apps.... so i decidedd to make clean and do it again... first time my laptop blue screened, then it hibernated because I forgot to plug it in.... I'm thinking within a few hours.
I'm looking forward to this.
Back in my Blackberry days we used to call these Hybrids. Some of the most functional, stable BB OSs were patched together from different OSs or even bits and pieces from different phones.
Of course, some hybrids were the biggest train wrecks also...
I have high hopes for this. Good luck!
Heh, FrankenROM.
sorry for not getting this out tonight... I had a few minor setbacks. Teaser installer video coming in a few minutes. Right now, it is completely stock CM, and you can think of the teaser as a .5 of sorts. v1 will be out tomorrow I promise. Very minor tweaks that I am going to do to start out with.
Excuse my ignorance, whats the point? Isn't CM7 the best of 6 and 7 all rolled into one sprinkled over some Gingerbread?
joe3681 said:
Excuse my ignorance, whats the point? Isn't CM7 the best of 6 and 7 all rolled into one sprinkled over some Gingerbread?
Click to expand...
Click to collapse
This ^^ I'm running gridlock's CM 7 latest build and so far, it's got all the mods that CM6.# has, on GB.
What exactly are you planning on adding that it doesn't already have?
n1ghtwish said:
This ^^ I'm running gridlock's CM 7 latest build and so far, it's got all the mods that CM6.# has, on GB.
What exactly are you planning on adding that it doesn't already have?
Click to expand...
Click to collapse
Cause I went from Cm6.1 to to 7 up to the latest 32, and there's nothing at all that has made me say "Oh damn, I miss that from CM6". CM7 has TONS more tweaks, and a pretty bad ass music player.
Glad to see I'm not the only one wondering what the point of this is...
when i started this project that wasn't the case. a lot o the goodies in CM6 were missing... I plan to add my own little touch to it and hopefully diverge from the CM project slightly. Video's not going to happen, having some issue with the touchscreen....will look at it in the morning.
hmmm... no issue with the touch screen... but somehow this compiled lacking a keyboard... blah... i was hopeful... oh well... will deal wiith it in the morning
So CM7 was a stellar success for our tiny lil device called Tattoo.
Now that CM7 is over, we'll are eagerly waiting for CM9. I posted this thread to know if Tattoo is going to be supported in the CM9 builds. If anyone of you has an idea of what is going on, you can reply here. Also you can use this thread for dev purposes.
Others here, you can list out what features you want to see on out Tattoos running CM9. This can come of great help to the devs until the actual thread comes up.
So when many devices have got early CM9 builds, why not us? arco68 and KalimochoAz, you there?
The CyanogenMod team already announced that one phone which will not get the upgrade is the Motorola Droid because of it's outdated hardware. You know, Droid is really similar to Tattoo specwise. Same CPU specs, same RAM amount, same internal memory.....
You draw the conclusions.
pretty bleak future for us indeed. but the hero and the G1 are running early builds of it already. so if G1 can do, why not Tattoo?
sunitknandi said:
pretty bleak future for us indeed. but the hero and the G1 are running early builds of it already. so if G1 can do, why not Tattoo?
Click to expand...
Click to collapse
Any hope for us. Be patient. They only write about Droid1: http://www.cyanogenmod.com/blog/cm9-progress-update
BilboPC said:
Any hope for us. Be patient. They only write about Droid1: http://www.cyanogenmod.com/blog/cm9-progress-update
Click to expand...
Click to collapse
This blog post pretty much confirms that we won't be getting CM9.
Our goal is to provide continued support to all CM7 devices back to the QSD8250 series of devices such as the Nexus One.
Click to expand...
Click to collapse
Our device is MUCH less-powerful than the QSD8250, which is a 1.0-1.2GHz CPU and Adreno 200 GPU System-on-a-Chip.
if that is true, wildfire wont get it too.
My guess it it will run. But should be optimized heavily for a smooth experience.
Sent from my HTC Tattoo using XDA App
I'm afraid the low resolution will be the show stopper there.
Maybe possible but it will be light version of ICS a few of the ingredients may be removed.
The screen is 2.8" n this is maybe the drawback...
I have installed ICS on G1. Its horrible ROM, Very Laggy and still needs lot of development for smoother experience. They haven't fixed the rotation problems yet. It looks to me Tatto0 will have a hard time with CM 9 because of its lower quality hardwares.
Tattoo is a 2 years old phone
Once we made it 2.1/2.2
It great already
And now we even have 2.3
What are we still asking for
As google told before
4.0is for high end
So let's enjoy the extra bonus that we get
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App
There was a Christmas gift to buzz community from Arco
http://forum.xda-developers.com/showpost.php?p=20639586&postcount=61
which i think is a good news for Tattoo as well in terms of CM9
i still have hope!
it might not be a perfect version of android 4, but at least we can try and have fun a little bit while we wait for next year's christmas for a new phone!!
Look at this
http://www.youtube.com/watch?v=Ym4A82ft5pw
It's ICS running on htc g1, the first android phone! I hope we can run it also on our tattoo
mattia29 said:
Look at this
http://www.youtube.com/watch?v=Ym4A82ft5pw
It's ICS running on htc g1, the first android phone! I hope we can run it also on our tattoo
Click to expand...
Click to collapse
Yes, it's running, but as you can see it's too slow, really.
Yes but tattoo has a little better specs than G1
Hey all,
If no-one is looking at porting CM9 to Tattoo, I could have an indicative look at doing it; no promises though; as I am doing it for HD2 at the moment, where I am spending all my time
I may have a go in a few days.
Although I may need some assistance with drivers and kernel later on
arif-ali said:
Hey all,
If no-one is looking at porting CM9 to Tattoo, I could have an indicative look at doing it; no promises though; as I am doing it for HD2 at the moment, where I am spending all my time
I may have a go in a few days.
Although I may need some assistance with drivers and kernel later on
Click to expand...
Click to collapse
That's awesome, man. I would done it if I had knowlege
arif-ali said:
Hey all,
If no-one is looking at porting CM9 to Tattoo, I could have an indicative look at doing it; no promises though; as I am doing it for HD2 at the moment, where I am spending all my time
I may have a go in a few days.
Although I may need some assistance with drivers and kernel later on
Click to expand...
Click to collapse
Please do it if u have time.
Update on compilation
Hi all,
Everything I do is all open, so you will see what I have done; this also gives others the chance to contribute
If someone wants to see my progress, then you can go to the following git repo
https://github.com/arif-ali/android_device_htc_click
and when I have a build it will be located here
http://cyanogenmod.arif-ali.co.uk/rom/test
So far quite a bit compiles, working on the wpa_supplicant part now. Looks like it may be a hack or need to look somewhere else.
I've had the Tattoo for 2 years now, but don't really know the HW much, so much research will be required. I've just installed nfinityGB, as and when arco built it.
If someone can give any input, it may speed up my work; and it will be appreciated.
Edit 1:
* Got passed the wifi, just got the drivers from gingerbread (for my notes)
Code:
cd system/wlan
git clone git://github.com/CyanogenMod/android_system_wlan_ti.git -b gingerbread
mv android_system_wlan_ti ti
sed -i s/LOCAL_MODULE_TAGS.*/LOCAL_MODULE_TAGS\ :=\ optional/g system/wlan/ti/sta_dk_4_0_4_32/config/Android.mk
* Need http://forum.xda-developers.com/showpost.php?p=20737947&postcount=27 for compilation as well
Code:
unzip ../webrtc.zip -d external/webrtc/
Edit 2:
Good News; first compile done.
Bad News; it's 4am in the morning, and I can't be bothered to test
I have no idea if it is going to work or not, and if someone is really adventurous, then feel free to try flashing the file from the following URL in about 20 mins i.e. better to try 04:30 GMT to be on the safe side
http://cyanogenmod.arif-ali.co.uk/rom/test/update-cm9-click-20120101.zip
system is going to be 162M, and gapps can be downloaded from http://cyanogenmod.arif-ali.co.uk/misc/gapps-ics-20111128.zip
Personally, I won't be able to test until tomorrow now
Edit 3:
NVM, this won't work, our system is only 150M; I will give it another go later
Let's start!
So, I just want create Development Team for LG GT540 and make CM9 (ICS).
At this moment I have working version ICS, but I don't have a lot of time for this, so I think together we can make more, better and faster.
Look on other guys, for example Samsung Gio, Ace, LG P350, P500 and other cheep phone, they work together and have progress.
I need 3-5 people who know basic android, know how build the ROM from sources and can/want do something for all.
I made organization repository for work and will publish fix and config sources after create Development Team.
The main priority:
- create new kernel 2.6.35.10 from CM repository - https://github.com/mmxtrem/lge-kernel-msm7x27 (I started yet, and maybe in future we will have official support CM7 and kernel);
- create CM9 ROM usable and stable for every day with maximum functionality.
So, welcome! Let's make some rock!
P.S. I think that this idea will continuous like other "about make kernel together by Mur4ik"! Because all want just glory and money, it's woefully.
links
http://forum.xda-developers.com/showpost.php?p=21770058&postcount=20
Maybe this time it will happen... I know PCFighter had a similar idea for an ICS team so perhaps you two can work together.
Sent from my LG GT540 Swift
Why you don't want help? I saw you did something in kernel.
miroslav_mm said:
Why you don't want help? I saw you did something in kernel.
Click to expand...
Click to collapse
My computer is old & slow. Too old & slow I think to build ICS. If you need a tester or anything else...
Sent from my LG GT540 Swift
I am build on laptop in Virtualbox, 1 core, 2gb RAM for Virtualbox, its slow, but working, 10-20hour for build. its not big problem, dont listen other devs, that need super PC, they just want money for upgrade!
One dev from Modaco build ICS on netbook with Atom core.
My C++ programming knowledge is very little, I have the PC for building roms, but that's not enough. I'd like to be a tester, or smthing like that
98% forum's user think that it's very hard!
No, it's not true.
Just need have logic and interest.
One year ago I don't know what is Android, now I am feeling good in gigabytes of sources.
Everyone can do something good for development.
All devs looking on each other, modify source like other, improve, all time finding new information in Google, just one of 100 can write new driver for example.
If we have problem in build, finding in Google, 90% info can find in network, need just understand what you do and understand where is a problem!
Wow, I'm getting more and more motivated. I have some(hopefully enough) C/C++ knowledge, zero knowledge of java, unfortunately, at least basic understanding of Android, and its mechanisms and a will to learn and create. My machine is a desktop pc with AMD Athlon 64 x2 processor(2,8Ghz), 2x1GB DDR2-800 RAM, and a huge hard drive. Unfortunately, I don't have time right now, as I have exams. I should be free in two weeks, and I'll read into the links from the dev topic. My suggestion now is to figure out a good and reliable way for communication between the people on the team.
Sent from my GT.. ah, screw it!
I've a very fast pc.. 3.1 ghz with 640gb about HDD and 6 gb about memory.. but I don't know android about his developting..
Count me in.
Btw. I started to work on msm-3.0 kernel. Which maybee will be useless, when we don't get andreno 200 libs for ICS.
great idea, don't know anything about java or even rom development but or technical stuffs about android but i encourage all of you who can make this possible..
you have my support in mind
I can join, i got the kernel from cm portem to same state as mine in ICS, now just your help miroslav is to do camera and to get ris of gliches - get me on pm for now, I am on holidays till sunday after all i will be on skype etc
I also can help im dont know too much about android building but i learning fast
I have laptop(2,3GHz, 4GB RAM) and virtual box. ICS compiled in 6h
I can help, I got more skill in the development, aosp 2.3 for GS2 and AOSP 4.0.3 for GS2, I can help here.
airbus360 said:
I can help, I got more skill in the development, aosp 2.3 for GS2 and AOSP 4.0.3 for GS2, I can help here.
Click to expand...
Click to collapse
Good to see you guys working together.....
Sent from my GT540 using xda premium
i want to help.. i know java and c/c++/c# but i don't know of android... i just need a guide.. an i could help!!
---------- Post added at 06:34 PM ---------- Previous post was at 06:32 PM ----------
and my pc is an i7 950 3.33 ghz OC, 6 gb ram and 250 gb partition for linux..
Could i join, i have a prety fast pc and can quickly set up a vmware box for compiling
specs
3cores
4gb ram
prety much unlimited hd space
I love mikes ics rom and i know java already, this would be a nice project for me to learn more about android from
i want to join TeamICS
At the moment i am compiling AOSP 4.0.3
Let's party!!
Wow, amazing guys, everyone is motivated, thats great. I have little knowledge of C, C++ and Android, but if you need tester, count me in. Also my PC is Celeron E3300 @3GHz, 2GB of RAM and 500GB hard.
Nice!
Here will be official git Swift-Team
https://github.com/Swift-Team
Project IceCreamSwift is opened!
Pathes and device folder I will upload later. Manual too.
So, you can fork project, marge, edit, test, after then pull request.
little manual:
https://github.com/Swift-Team/android
P.S.
Write who is a member of team and write github profiles.
Rom Port Team Effort
Hello P880 community.
This post has the purpose to put together a group of users / developers, who are willing to participate into bringing a different set of roms into our community.
These set of roms that I'm thinking, can range from complete Sense ports to more customized and maybe less popular roms (like ColorOS, LiGux, FlymeOS, FluidUI, etc..).
What's valid on this thread:
- CM / AOSP (any base we already have) themed (like Samsung TouchUI, Optimus, Blur, etc..). So you can grab any rom (with author authorization), theme it (i mean, not just shove an apk as default theme, I mean neat theming ).
- Ports from other devices (evert port needs to have clear authors permission to port it).
- All users are very welcome, everyone can participate, users with porting / developing skills are needed as well.
The idea is simple, we're not going to use this thread to post the work, this is just a thread to talk about possible projects.
We can start by listing which devices are hardware compatible and the port is "easily" possible.
Roms that can be used as a base for eventual future ports.
CM10.2 - thanks to laufersteppenwolf for compiling this build promptly for this purpose
http://goo.im/devs/laufersteppenwolf/CM10.2//cm-10.2-20140305-UNOFFICIAL-p880.zip
- - - - -
I strongly recommend the use of MultiRom for testing ports and other roms. That way you can maintain your working rom and whenver feeling adventurous you can without going through the hassle of backup / restore / yada yada yada that we are all too familiar with.
http://forum.xda-developers.com/showthread.php?t=2655988
- - List of Devices with hardware similar / close / identical to the 4X - -
- HTC One X
- HTC One X +
- More ??
- Possible roms to port:
Right now would be nice to see a OEM rom, such a touchwiz or Sense
Work in Progress
N/A available
(awaiting sugestions
So, what do you guys think? ? Any users with good porting skills ? I know we have good developers! Ideas? Sugestions?
Write away
A few guides from XDA - They may not be all you need to get the job done, but a LOT of important information is written here. Don't forget to thanks their authors
Guides / Tutorials
How to Port Roms by @saywhatt
How to Port Manufacturer Rom. by @GalaxyUser
How to port Stock/GB/CM7/CM9/ICS/CM10/JB Based ROMs by @Peteragent5
PS - Every work that is possible to port and if someone decides to invest time in it, it needs explicit authors permission.
Sure if a few people want a particular rom i can bring it to our device, but i would much prefer helping first time rom builders do this own their own then they can maintain it also
JoinTheRealms said:
Sure if a few people want a particular rom i can bring it to our device, but i would much prefer helping first time rom builders do this own their own then they can maintain it also
Click to expand...
Click to collapse
Well, I though about some sort of "voting" to bring a "specific" rom.
Personally, I'd love to have Sense on our device. I had two HTC's before and I miss that Sense interface :b
But far as I'm aware, isn't an easy thing to port.
About your offer, this thread stands mostly with learning. The idea is everyone being able to contribute and more users start bringing roms as their first times. So, thank you so much for lending your help and know how, I'm sure we'll have a fine list of possible ports and then we can talk about how to port them over
Everyone can ask for help and the idea is to everyone who is able to - help.
I like the idea of this thread, but what would also be quite usefull is a list of available ROMs and their maintainer(s).
Also the list should include ROMs someone is working on ATM, so it cannot happpen that 2 devs are working on the same ROM
However, your idea is good, but porting a ROM not from sorce is quite hard, and might need some smali "hacking" in order to resolve bugs.
But well, we're a community, and I guess we can help each other if needed, right
laufersteppenwolf said:
I like the idea of this thread, but what would also be quite usefull is a list of available ROMs and their maintainer(s).
Also the list should include ROMs someone is working on ATM, so it cannot happpen that 2 devs are working on the same ROM
However, your idea is good, but porting a ROM not from sorce is quite hard, and might need some smali "hacking" in order to resolve bugs.
But well, we're a community, and I guess we can help each other if needed, right
Click to expand...
Click to collapse
That's correct! :good:
The main point is to learn helping each other who knows in a month or so, today's whiners are tomorrow's contributors
Jokes aside, the first post will be edited in order to structure and add information.
I'm gonna start with compatible devices (the ones that allow porting in a easy way). Ideas? Besides the HTC One X ? I'm guessing the grouper (N7 2012) besides having the same soc, doesn't have the same screen...
PS - (this would be better with an experienced porter) - Maybe we could start with a easy one, and go on from there
I know we have "how to port" threads all around xda ,but each port is different so we can't use "one hat to fit them all" ... or a ring to rule them all, so we should treat each port differently.
However.. I'm gonna put some xda links about porting to bring some light into the matter for who is "new" on this subject... or for whom's feeling adventurous and can't wait to have "their" rom on "our" device
Oh yes finally, have been waiting for a thread like this for a long time me as well would love to see a sense rom on this phone
cm/aosp roms are not that hard to port most of the time u only need the same screen resolution for it to work. (ported a nexus s touchwiz rom over to my old lg optimus 2x) but would have loved to see some oem roms ported over as well, even though it would be a lot harder to port over. but as a wonderful community as this is we might be able to pull it off
MidnightDevil said:
That's correct! :good:
The main point is to learn helping each other who knows in a month or so, today's whiners are tomorrow's contributors
Jokes aside, the first post will be edited in order to structure and add information.
I'm gonna start with compatible devices (the ones that allow porting in a easy way). Ideas? Besides the HTC One X ? I'm guessing the grouper (N7 2012) besides having the same soc, doesn't have the same screen...
PS - (this would be better with an experienced porter) - Maybe we could start with a easy one, and go on from there
I know we have "how to port" threads all around xda ,but each port is different so we can't use "one hat to fit them all" ... or a ring to rule them all, so we should treat each port differently.
However.. I'm gonna put some xda links about porting to bring some light into the matter for who is "new" on this subject... or for whom's feeling adventurous and can't wait to have "their" rom on "our" device
Click to expand...
Click to collapse
You can add the HOX+ to the list as well
About porting, you need to seperate it in two halfs, porting from source, and "winzipping". TBH, I'm no fas of winzipping at all, but some stuff (like sense or TW) can only be winzipped...
BTW, if you need a 2nd/3rd post, just let me know
Personally, I'd like to see a GFlex or even better, a G2 (/mini) ROM for our phone (KitKat, of course )
This thread has potential
I'm new to this forum,so i dont know whats going on about roms,i see there are few devs working full time.
I think this is the best way to go: Port ALL open source roms,such as we have already,but we need them all.
Second,make a badass kernel,with all features and customizations,possibly 3.4.
Third,and just a suggestion,Make a community ROM?
I really like this thread,and i even more like this OX4 community,you all get along,and i've missed that,i was on a forum that has no frendly people whatsoever.
And,about the roms,the idea is awesome,but i always think of the clash of clans rule,max everything out before going on a higher level.
Sent from my LG-P880 using XDA Premium 4 mobile app
Regarding stock roms, it's an interesting thing, but I'm guessing stock roms are more trouble to port comparing to AOSP or CM.
I remember on the HTC Sensation forums the headaches sense brought to many developers and porters, the bunch of files that needed to be edited, kernel changes (aosp kernel is different from stock / sense kernel in that case).. so Stock roms are maybe harder to port fully.
Right now we have some apks from the G2 (lock screen, messaging, etc..), maybe someone will port some things from the Flex, but the whole base.. hum
@DeHuMaNiZeD , thanks for your reply
The other roms based of AOSP and CM, in my opinion, unless they're different (modded, themed, customized - etc..) but if not, if they are "clean" roms with no changes, then - we have them already I believe you'll agree. (Unless the idea is to test something).
A 3.4 kernel would be something, but perhaps a developer can shed some light here - what benefits would we have from a 3.4 kernel ?
A community rom is indeed long due. This thread is a different subject because it's about *several* roms, ports and tutorials, maybe you would like to create a thread here on General about that? You can start with votes (i believe it's a proper way to do it) with which base should we use (Cm, AOSP, Stock, etc..), included apps (or not), possibly aroma maybe and so on
DeHuMaNiZeD said:
This thread has potential
I'm new to this forum,so i dont know whats going on about roms,i see there are few devs working full time.
I think this is the best way to go: Port ALL open source roms,such as we have already,but we need them all.
Second,make a badass kernel,with all features and customizations,possibly 3.4.
Third,and just a suggestion,Make a community ROM?
I really like this thread,and i even more like this OX4 community,you all get along,and i've missed that,i was on a forum that has no frendly people whatsoever.
And,about the roms,the idea is awesome,but i always think of the clash of clans rule,max everything out before going on a higher level.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, this sounds quite good, but the real problem is: this is a hell lot of work. Also, it needs resources. The sourcecode of a ROM is ~25-30GB. When it's compiled it's about double the size, and takes my PC (8 cores @ 4GHz) about 75Min to compile. Not to mention the time 'til the sources are Downloaded. My 500GB HDD is near to its limit very soon, so sooner or later I will need a new HDD, then I might be able to get another ROM ported, but right now, hard...
Also, why do you need a 3.4 kernel?
MidnightDevil said:
Regarding stock roms, it's an interesting thing, but I'm guessing stock roms are more trouble to port comparing to AOSP or CM.
I remember on the HTC Sensation forums the headaches sense brought to many developers and porters, the bunch of files that needed to be edited, kernel changes (aosp kernel is different from stock / sense kernel in that case).. so Stock roms are maybe harder to port fully.
Right now we have some apks from the G2 (lock screen, messaging, etc..), maybe someone will port some things from the Flex, but the whole base.. hum
@DeHuMaNiZeD , thanks for your reply
The other roms based of AOSP and CM, in my opinion, unless they're different (modded, themed, customized - etc..) but if not, if they are "clean" roms with no changes, then - we have them already I believe you'll agree. (Unless the idea is to test something).
A 3.4 kernel would be something, but perhaps a developer can shed some light here - what benefits would we have from a 3.4 kernel ?
A community rom is indeed long due. This thread is a different subject because it's about *several* roms, ports and tutorials, maybe you would like to create a thread here on General about that? You can start with votes (i believe it's a proper way to do it) with which base should we use (Cm, AOSP, Stock, etc..), included apps (or not), possibly aroma maybe and so on
Click to expand...
Click to collapse
For stock ROMs to work, it's your best bet to use AOSP as your base, and then look for what's missing/broken. This, however, means you need an AOSP base first to work with. And AOSP is not always the easiest thing to get properly running.
About the benefits of an 3.4 kernel: None IMO. All you get is a higher version-number, and that's it. We actually already have some 3.4 features backported, and also tweaked the 3.1 kernel quite a lot. So the actual benefits are all in your head (well, except you count bugs as benefits )
Community ROM? Meh, what for? We have so many ROMs already, so everyone should find the one that suits him/her best
BTW: Thread stuck
laufersteppenwolf said:
Well, this sounds quite good, but the real problem is: this is a hell lot of work. Also, it needs resources. The sourcecode of a ROM is ~25-30GB. When it's compiled it's about double the size, and takes my PC (8 cores @ 4GHz) about 75Min to compile. Not to mention the time 'til the sources are Downloaded. My 500GB HDD is near to its limit very soon, so sooner or later I will need a new HDD, then I might be able to get another ROM ported, but right now, hard...
Also, why do you need a 3.4 kernel?
For stock ROMs to work, it's your best bet to use AOSP as your base, and then look for what's missing/broken. This, however, means you need an AOSP base first to work with. And AOSP is not always the easiest thing to get properly running.
About the benefits of an 3.4 kernel: None IMO. All you get is a higher version-number, and that's it. We actually already have some 3.4 features backported, and also tweaked the 3.1 kernel quite a lot. So the actual benefits are all in your head (well, except you count bugs as benefits )
Community ROM? Meh, what for? We have so many ROMs already, so everyone should find the one that suits him/her best
BTW: Thread stuck
Click to expand...
Click to collapse
Why dont you set up that build server,i think they're cheap atm,or someone could borrow you? It would take a lot less time and effort. that's why i think offical rom support is important,once it's merged to the build bot,its their responsibility.
Sent from my LG-P880 using XDA Premium 4 mobile app
DeHuMaNiZeD said:
Why dont you set up that build server,i think they're cheap atm,or someone could borrow you? It would take a lot less time and effort. that's why i think offical rom support is important,once it's merged to the build bot,its their responsibility.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's not as easy as you might think
I do have access to a buildserver, however I only have 100GB as it's a shared one, so this is genious for official builds, or quick tests/ports. But it isn't ideal for the long terms.
Also, having it official doesn't mean you're done you need to update it, and also fix it when it's broken. 'cause when it's broken, it can mess up the whole build process of the buildbot
But in general, you're right, having it official does help a lot
{fd}ware said:
Does anyone of you have a link to the latest CM10.2 (Android 4.3) for our device?
It seems like it's not anymore on get.cm and I wanted to start porting a TouchWiz (Note 3) ROM to our phone when I have free time
Click to expand...
Click to collapse
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
MidnightDevil said:
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
Click to expand...
Click to collapse
LOL, no, I do not, but gimme a few hours and I'll have one
Syncing right now
laufersteppenwolf said:
LOL, no, I do not, but gimme a few hours and I'll have one
Syncing right now
Click to expand...
Click to collapse
Thank you
{fd}ware said:
BTW, did anyone tried to port a ROM this way? http://forum.xda-developers.com/showthread.php?t=2245786
Click to expand...
Click to collapse
Nope, I actually never "winzipped" a ROM
Lot of things to comment on here. Very good initiative I have to admit. I'm sure I'll have more ideas as the discussion evolves.
Similar hardware: You can add HOX+ as laufer said. Very minor differences are there only.
What I would personally prefer is TouchWiz, at least Nature UX 2.0, but new S5 UI is also really awesome. I liked Sense till 4.5, but 5.0+ versions are now out of my 'inner circles'. Especially what I don't like is the UI.
Few suggestions:
FlymeOS (from Meizu MX) - I got 2.0 booting last summer, but had touchkey issues (they were freezing the device lol) and never released it. Nobody ever booted 2.0+ on other Android devices yet.
Porting LG roms might be the best start, I think porting full Optimus G system wouldn't be that hard. Just a pain in the *ss merging process.
What we mainly need is same screen size (unless you wanna resizing 100+ apps ). Similar SoC is a good extra, but that's very limited. Also, it's better to avoid Qualcomm SoCs to port from, it's extremely hard, there are a lot of code changes in low-level code which just make the device get into deep segfault cycles. :cyclops: Even Exynos is easier to port from, trust me. I got SGS3 leaked 4.2 booting on the O4X last autumn.
Big issue we have to note: In 4.2, Google radically changed graphics libraries code. We have old, 4.1.2 blobs and those need hacks in libgui.so and libsurfaceflinger.so to function properly (in 4.4+ libEGL.so, libGLES_v1_CM.so and libGLES_v2.so also need a change). Here comes the problem: Manufacturers do change these libraries, mainly adding Wi-Fi display and HDMI support code which other blobs rely on. Of course we can't just replace these libs, graphics wouldn't function that way. Either we have to guess those function signatures and reimplement some stub in the code, or use new blobs, i.e. what I did in Omni. But y'all now those are not perfect _yet_.
Regarding newer kernels: If, I emphasize, IF it's properly ported, it would cause a noticeable effect on overall performance, battery life, etc. What do I mean by proper porting: All machine-specific code must be updated to Nvidia/Google upstream, no excuses! I don't say anything for sure, I didn't check it much, but kholk didn't do this merge. His kernel still uses 3.1 files with slight modifications to be 3.4-compatible. What I mean would be a very long and painful process, but would surely benefit after all. 3.4 has no Android branch, mainline Nvidia Tegra kernel does only have Linux support, it might be even harder. 3.10 is maintained by Google for Android, issues I have found so far: No graphics driver support for T2 and T3, have to forward-port it and I didn't find core Android components like wakelocks, earlysuspend, etc. Weird.
A little related story: I initially started working on MultiROM so I can test and port different roms while I can keep a stable rom for myself and there'd be no need for reflash then. That's what I can suggest. Use MultiROM, it has so many capabilities! Maybe it's better with kernel sharing so you don't have to wait for hardboot on every reboot (which one needs a lot if porting). @MidnightDevil you could add this to the OP maybe.
MidnightDevil said:
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
Click to expand...
Click to collapse
Here you are! Compiled this because wanted to start porting from Note 2, but finally worked on Omni more and abandoned it.
{fd}ware said:
BTW, did anyone tried to port a ROM this way? http://forum.xda-developers.com/showthread.php?t=2245786
Click to expand...
Click to collapse
That's way too generic unfortunately.
Quick suggestion for you port: Use Note 2 base with Note 3 features. Note 2 has the same resolution and you won't need to resize.
Adam77Root said:
Lot of things to comment on here. Very good initiative I have to admit. I'm sure I'll have more ideas as the discussion evolves.
Similar hardware: You can add HOX+ as laufer said. Very minor differences are there only.
What I would personally prefer is TouchWiz, at least Nature UX 2.0, but new S5 UI is also really awesome. I liked Sense till 4.5, but 5.0+ versions are now out of my 'inner circles'. Especially what I don't like is the UI.
Few suggestions:
FlymeOS (from Meizu MX) - I got 2.0 booting last summer, but had touchkey issues (they were freezing the device lol) and never released it. Nobody ever booted 2.0+ on other Android devices yet.
Porting LG roms might be the best start, I think porting full Optimus G system wouldn't be that hard. Just a pain in the *ss merging process.
What we mainly need is same screen size (unless you wanna resizing 100+ apps ). Similar SoC is a good extra, but that's very limited. Also, it's better to avoid Qualcomm SoCs to port from, it's extremely hard, there are a lot of code changes in low-level code which just make the device get into deep segfault cycles. :cyclops: Even Exynos is easier to port from, trust me. I got SGS3 leaked 4.2 booting on the O4X last autumn.
Big issue we have to note: In 4.2, Google radically changed graphics libraries code. We have old, 4.1.2 blobs and those need hacks in libgui.so and libsurfaceflinger.so to function properly (in 4.4+ libEGL.so, libGLES_v1_CM.so and libGLES_v2.so also need a change). Here comes the problem: Manufacturers do change these libraries, mainly adding Wi-Fi display and HDMI support code which other blobs rely on. Of course we can't just replace these libs, graphics wouldn't function that way. Either we have to guess those function signatures and reimplement some stub in the code, or use new blobs, i.e. what I did in Omni. But y'all now those are not perfect _yet_.
Regarding newer kernels: If, I emphasize, IF it's properly ported, it would cause a noticeable effect on overall performance, battery life, etc. What do I mean by proper porting: All machine-specific code must be updated to Nvidia/Google upstream, no excuses! I don't say anything for sure, I didn't check it much, but kholk didn't do this merge. His kernel still uses 3.1 files with slight modifications to be 3.4-compatible. What I mean would be a very long and painful process, but would surely benefit after all. 3.4 has no Android branch, mainline Nvidia Tegra kernel does only have Linux support, it might be even harder. 3.10 is maintained by Google for Android, issues I have found so far: No graphics driver support for T2 and T3, have to forward-port it and I didn't find core Android components like wakelocks, earlysuspend, etc. Weird.
A little related story: I initially started working on MultiROM so I can test and port different roms while I can keep a stable rom for myself and there'd be no need for reflash then. That's what I can suggest. Use MultiROM, it has so many capabilities! Maybe it's better with kernel sharing so you don't have to wait for hardboot on every reboot (which one needs a lot if porting). @MidnightDevil you could add this to the OP maybe.
Here you are! Compiled this because wanted to start porting from Note 2, but finally worked on Omni more and abandoned it.
That's way too generic unfortunately.
Quick suggestion for you port: Use Note 2 base with Note 3 features. Note 2 has the same resolution and you won't need to resize.
Click to expand...
Click to collapse
Dang, you've beaten me but mine's as fresh as it could be
HERE you guys go, for all who need the newest CM10.2
laufersteppenwolf said:
Dang, you've beaten me but mine's as fresh as it could be
HERE you guys go, for all who need the newest CM10.2
Click to expand...
Click to collapse
Just don't delete the sources, you might need them in the close future.
I think we should create a schedule about what to do. As you all know, good buildings all have good grounding. So let's get started from the very beginning I say. First fix remaining bugs in MultiROM, then create a unified kernel so users don't have to choose. Very likely this is not possible as people think different so just make all kernels hardboot compatible. After these we have a solid base for starting all the work. Of course this cannot be done if not everybody is involved. Both devs and users should share a part in this magnificent journey.
(High expectations, I know. )
Sent from my OmniROM-powered LG Optimus 4X HD