Related
Hi , lot of developper Jerpelea , Zdzihu & TripNRaVeRs and i dont forget Binary & Maxrfon & goroh "
try hardly to put custom rom for our X10 ,
strategy : why focusing on 2.2 or 2.1 AOSP : 2.3.1 is more attractive we have a lot of delay stop viewing the past :
Synergy : each developer work hard but alone "not enough fast" maybe the creation of one Dev-team & one project " avoid the personal conflicts" is a better way to escape from SE Curse they develop 2.1 and 2.2 is already in the Market
PS: i am very proud by our Devs , I only think that 1+1+1+1 ..... is better than BIG One
its a democracy but consensus is better
+1
agree with u , all of them are proffisor alone but if thy work together we don`t know what they can do !
I support your initiative. I would love to have ONE great ROM (with full hardware support) rather than several "half implemented" ROMs like we have today.
IMO most developers here prefer to work alone (don't know if it's related to donations...), but it's really easy to see that if all of them join a single project we would definetly have a better and more optimized ROM.
One good thing is that Google seems to slow down the new major releases to two a year, so our developers will also have more time to debug and keep up.
I can only assume that they have put a lot of time looking at and understanding how the previous versions run, now they have an understanding they are putting it to good use and developing us a custom rom free of charge. To inhance our phones
I dare say they are probably looking at the gingerbread stuff now but you can only you can only do what you can do, there is no point stopping a development everytime new software came out because that way you would never have anything finished.
Patience is key, these guys do have lives, there is a order to everything and just because you dont understand it doesnt mean it is wrong
the dev's are amazing and i wish i had the knowledge to help more, icecream is coming out in the summer will the devs be expected to down tools and move on from gingerbread then?
just be patient and let the devs do their magic
My (limited) understanding is that since the bootloader is still locked, they are developing these custom ROMs on the existing 2.1 kernel that SE has put out for the X10. That means that certain core components are Android 2.1, and can't be replaced without bootloader access.
As such, it makes sense that the further an OS version is from 2.1, the more likely it is that it will require specific features not available in the 2.1 kernel.
So developing stock 2.1 for the X10 would be easiest, 2.2 would be more difficult, 2.3 even moreso, and so on.
maybe its true but developing 2.1 AOSP or 2.1 with sense take a ot of time and confir the stupid idea from SE Eclair 2.1 plus SE soft is better than Froyo ,
Creating a team will reduce time of developement and may be improve the quality of the rom build , my idea it just to say that and unify the X10 community in supporting one effective project thant wasting a lot of creativity & effort in incomplete work its easy to say the difficulty is to DOING the Job
Just a little bit of insight here from someone who isn't a developer of ROMS....
I agree that combining their efforts would most likely give us better results with regards to hardware. Here's what I think may be happening. Now that they're able to create functioning ROMs, they're each taking the time to hammer out their skills. When you learn something new, you generally spend your time redoing the same thing over and over until you've got it down pat.
That being said, they're each learning more and more as they attempt new ROMs. I think once the fascination of "Hey I got a working port of *this* ROM first!" wears off, maybe they'll work together to create a fully functioning ROM. Who knows, one of them may actually sit still for a moment and finish up one of their own ROMs.
I hope that all of the developers working on different ROMs at the very least keep a line of communication open between them so as to share fixes and work arounds.
speaking of GB
http://forum.xda-developers.com/showthread.php?t=911364
Yes! I Agree With You!!!!
+1
I love all the dev here, but i too just don't get it..
either i get a working camera or working wifi ? Come ON...
i hope you guys see this posts as friendly talk, we are so lucky that we have all of you here you all understand the need of one functional AOSP Rom 2.2, 2.3 whatever
I feel the same way maybe the devs should team up and create a monster ROM that works.
I agree. It's been proven time and time again, teams work better than individuals. Please unite Devs! Think of what could be accomplished
I havn't even tested a ROM yet since their all incomplete, simple as that.
All the different ideas and "wishes" posted on this thread are of course appealing but until the bootloader is cracked it's practically impossible to have a fully working ROM on any other version other than the 2.1, at least from a short term perspective.
Correct me if im wrong, but from my understanding they started to work with 2.1 just to make it simpler to mod the code to 2.2 later.
The reason is that SE have released some code for 2.1, but of course not for 2.2. So they used SEs 2.1 code to develop the 2.1 AOSP rom. And could therefore much easier convert the code to 2.2.
It seems like you guys haven't been paying attention to dev work for the x10. Maybe it's because you didn't lurk the sub-forum since the beginning or maybe you don't understand what the devs are actually doing.
The devs ARE working together. jerpelea, zdzidu, bin4ry, goro-kun, maxfron, and many others DO communicate.
What one person said about having 2.2+ functions are strictly related to the kernal and bootloaders is the final word. Sony implemented special drivers for the camera and video decoding.
Until someone writes the drivers from scratch AND unlock the bootloader, we will have less than 100% functioning 2.2+ roms.
on that 2.3.1 HTC rom camera is working ... if they can get the BT and Wifi working it will be awesome . but i have a question . will we get the (MT) on these roms after SE release? i mean for 2.2 and 2.3
robbyf66 said:
I havn't even tested a ROM yet since their all incomplete, simple as that.
Click to expand...
Click to collapse
Yep.
Me neither.
And only because the camera and HD are not working
hemo1001 said:
on that 2.3.1 HTC rom camera is working ... if they can get the BT and Wifi working it will be awesome . but i have a question . will we get the (MT) on these roms after SE release? i mean for 2.2 and 2.3
Click to expand...
Click to collapse
The htc rom mentioned by you is 2.1. That thread is for 2 roms. 2.1 htc and gingerbread. So no, camera is not working on 2.2+ yet. Z got some progress making the camera atleast respond, but so far, if he implements full camera function, he looses other key functions in the rom. Not a good trade.
Sent from my x10 running 2.2
No pressrue on the devs and they can do what they please with their work. But as other have said it sounds like a great idea. Any devs care to comment on this idea?
Sent from my X10a using XDA App
Hey there,
I just exchanged my LG O2X to S2, and was wondering if you could recommend a good, stable, battery-efficient rom+kernel+whatever? I haven't found a thread like this so that's why I'm asking.
Is CM9 any good on S2, or should I stick to CM7? Or maybe Samsung ICS roms are the way to go?
Thanks in advance and have a great day : )
No. We don't recommend roms. For several reasons. Nobody has their phone setup the same as anyone else, nobody uses their phone in the same manner, and phones come out of the factory slightly differently component-wise.
You are very unlikely to have exactly the same experience with a given rom/kernel as me for those reasons.
I suggest you root your phone (if you haven't already), preferably with a method that installs CWM as part of the deal. Then you will be able to backup, restore & install roms or kernels within minutes. If you try a rom you don't like, it's easy to restore your previous setup & try another rom.
Edit to add - Also, many people on here who use a particular rom or kernel become utter fanboys, rendering any suggestions they give you useless due to their biases.
Ok, I get it - Could you just give me a quick intel on how's CM9 on S2 regarding what's working and what's not? That was a big issue on O2X due to nVidia not releasing Tegra2 drivers, and I can't find a thread listing working and not working features.
http://forum.xda-developers.com/showthread.php?t=1612881
Please just try the ROMs until you find one you like. Thanks
Closed
Good morning or evening to all,
this is my first post on the forum, so please by patient. I am new to the world of custom ROMs and I tried to educate myself by reading the noob guides. However, my questions become more and more widespread, and I am not sure where to try to find the answers.
To be clear: I am NOT asking about 'what ROM is best' and such. I would like to know more about the following:
1) There are CM7 ROMs (Netrino for example), CM9 and CM10 ROMs. As I understand it, because there have been stock files from MOTO, CM& ROMs can have stable kernels, hardware acceleration etc etc. However, if there is no hardware acceleration, how can CM9 ROMs be smoother?
2) In the same vain, how can CM9 and 10 ROMs have kernels? Where they written from scratch? And how can they be faster than stock?
3) Due to my SOD problems, I flashed several ROMs and currently have a CM9 one, which is stable so far. If I go back to a CM7 one, such as Netrino 2.9, what differences would I see? Will the latter be faster or more efficient? Smoother? Or should I just leave it alone, since it works?
4) And to reverse the question, how can a CM10 ROM be smoother, if it does not have hardware acceleration and drivers?
I am sorry about the bombardment. I do not want to waste anybody's time, but some pointers would be helpful. Thanks in advance!
to give you a shorter answer for better understanding:the stock roms are mostly based on android 2.3.6 which is the newest firmware.the roms only differ from the regions and mostly have battery tweaks or connection tweaks etc...
lets go to cm 9 and 10.cm9 is basically android4.0 and cm10 android 4.1.these are faster because they do not have many unnecessary apps like stock roms do.
i hope this explains a bit...
peddarson said:
to give you a shorter answer for better understanding:the stock roms are mostly based on android 2.3.6 which is the newest firmware.the roms only differ from the regions and mostly have battery tweaks or connection tweaks etc...
lets go to cm 9 and 10.cm9 is basically android4.0 and cm10 android 4.1.these are faster because they do not have many unnecessary apps like stock roms do.
i hope this explains a bit...
Click to expand...
Click to collapse
Thanks for the answer, peddarson.
Can it be that the only difference between roms is the absence of apps? Then, netrino should be the fastest of them all. And where does the absence of hardware acceleration and drivers factor in?
A few of your questions could be easily answered just by flashing the roms and seeing for yourself. Or Googling.
For example, you keep asking about hardware acceleration without knowing what it does or what it means. If you did, you'd know it plays a much bigger role with how apps function than the UI. The "smoothness" described in CM10 is with the UI and not the apps themselves (hint), while certain programs like the camera app, Chrome, etc. have a tendency to be unstable (hint.) You might be able to piece together that the UI isn't as ha-dependent as you thought. Maybe the visual experience has more to do with the actual software than hardware.
The answer to a few other of your questions is that these ROMs play off an original source and then tweaked to be optimized to the author's liking. Kernels can be overclocked, memory management can be altered, etc. If you want to know specifics, look into what each specific ROM does. It's right there in black and white.
nh777 said:
A few of your questions could be easily answered just by flashing the roms and seeing for yourself. Or Googling.
For example, you keep asking about hardware acceleration without knowing what it does or what it means. If you did, you'd know it plays a much bigger role with how apps function than the UI. The "smoothness" described in CM10 is with the UI and not the apps themselves (hint), while certain programs like the camera app, Chrome, etc. have a tendency to be unstable (hint.) You might be able to piece together that the UI isn't as ha-dependent as you thought. Maybe the visual experience has more to do with the actual software than hardware.
The answer to a few other of your questions is that these ROMs play off an original source and then tweaked to be optimized to the author's liking. Kernels can be overclocked, memory management can be altered, etc. If you want to know specifics, look into what each specific ROM does. It's right there in black and white.
Click to expand...
Click to collapse
The thing is that, as I said, I do not want to flash the ROMs (again) and see. I am not interested in learning the specific merits or disadvantages of each. I just want some pointers on what hardware acceleration does, how it synergizes with the UI, how different ROMs come about with or withoit drivers etc. And because I don't know, I ask (hint). Your post, for example, clarified some of these things, sarcasm aside. It would clarify even more if you could provide some links for me to pursue.
Haha. Welcome to XDA. People are quite unforgiving and harsh with noobs, I appologize on their behalf. I am still pretty new myself but for the past 4 months, I have read and learned quite a lot and have flashed many roms.
My first love was actually neutrino. I always seem to crawl back to neutrino rom because it is ridiculously smooth and stable for me. I've seen many people have issues here and there but I really have no complaints about neutrino. I have tried CNA, which is a port by Bill based off of CM10. I was quite impressed with how nicely it ran. The battery life wasn't as good as I'd like and I require a camera so I flashed back to neutrino.
There are two new cm7 based roms that have surfaced recently, Atrix MRom and TopSmarts. I tried MRom and it is quite a nice rom. I wasn't a fan of the Holo Launcher that it uses so now I'm on TopSmarts. This rom has been great for me. Like I said, I always end up back with neutrino but this is quite the contender. It's pretty new and only the first version so it will most likely be updated often.
I'd give a couple cm7 roms a go, if I were you. Just make sure you make a Nandroid backup of your current rom so you can always restore. I feel that Cm7 roms have much better battery life and tend to be more stable. The only issue I have with cm7 is there's no webtop option. Other than that, I couldn't be happier with TopSmarts or Neutrino. Both of the devs are also really friendly and quite helpful.
Hope this helps. If you have any questions, you're welcome to PM me.
Sent from my MB860 using xda app-developers app
ProudGrognard said:
The thing is that, as I said, I do not want to flash the ROMs (again) and see. I am not interested in learning the specific merits or disadvantages of each. I just want some pointers on what hardware acceleration does, how it synergizes with the UI, how different ROMs come about with or withoit drivers etc. And because I don't know, I ask (hint). Your post, for example, clarified some of these things, sarcasm aside. It would clarify even more if you could provide some links for me to pursue.
Click to expand...
Click to collapse
Wait, what? Then what's this?
"If I go back to a CM7 one, such as Netrino 2.9, what differences would I see? Will the latter be faster or more efficient? Smoother?"
Come on, guy.
Google hardware acceleration and you might find out that, like I suggested with my previous post, it doesn't necessarily have to do with the UI. Sorry, but I'm not spoon-feeding you links that you could have found in less time than making this post.
I've already explained the different ROMs are based on current software and then ported/tweaked. If you looked at the bugs with each ROM, you'd figure out the holes that drivers would fix.
nw21st (Alphabet district, amirite?) had a great suggestion which was that cm7 roms were easily the most stable. Why? Atrix has drivers up to 2.3.6 so nothing's missing. If you're wondering what differences you'll see in cm7 vs cm9 then you aren't using your phone enough, eg, camcorder. That's fine. Loads of people are on cm9/10 and accept the bugs and limitations. But hands down, cm7 ROMs will remain the most stable.
ProudGrognard said:
Good morning or evening to all,
this is my first post on the forum, so please by patient. I am new to the world of custom ROMs and I tried to educate myself by reading the noob guides. However, my questions become more and more widespread, and I am not sure where to try to find the answers.
To be clear: I am NOT asking about 'what ROM is best' and such. I would like to know more about the following:
1) There are CM7 ROMs (Netrino for example), CM9 and CM10 ROMs. As I understand it, because there have been stock files from MOTO, CM& ROMs can have stable kernels, hardware acceleration etc etc. However, if there is no hardware acceleration, how can CM9 ROMs be smoother?
2) In the same vain, how can CM9 and 10 ROMs have kernels? Where they written from scratch? And how can they be faster than stock?
3) Due to my SOD problems, I flashed several ROMs and currently have a CM9 one, which is stable so far. If I go back to a CM7 one, such as Netrino 2.9, what differences would I see? Will the latter be faster or more efficient? Smoother? Or should I just leave it alone, since it works?
4) And to reverse the question, how can a CM10 ROM be smoother, if it does not have hardware acceleration and drivers?
I am sorry about the bombardment. I do not want to waste anybody's time, but some pointers would be helpful. Thanks in advance!
Click to expand...
Click to collapse
1) Optimization, mainly
2) Motorola released the sources of each Atrix kernel (International, EMEA, ATT etc...). Devs can use it to make tweaked, optimized versions
3) By flashing a CM7, you will go back on Gingerbread (GB). CM9 = ICS and CM10 = Jelly Bean (JB). The main differences you can see are the different interfaces (GB looks ugly to me now...) and some apps like Chrome are missing on GB. Also CM7 is super stable, if you want a stable and customizable ROM then you should try it.
4) CM10 had a lot of optimizations all based around apps preloading/compiling (To be verified), also the animations were changed to make it look smoother. Stuffs like scrolling, animations are smoother on ICS/JB than GB because of optimizations too. If you flash CM7 you'd have the same kind of "smooth feeling" because of a high framerate but the apps won't load as fast as with CM9/10.
Personally I use CM10 even if it's not well supported (Not as well as GB) but ICS/JB is coming soon so I'm trying to get used to it for when it officially comes. I consider GB as a legacy OS, there won't be anything really new/innovative on it since Google doesn't develop any new app on it.
I know this is utter noob question but can't really help it ! In this part (and i assume that in many others parts too) of the world there are still people stuck with devices running on GB not even cyanogen or other after market rom support !
This is the main reason i was wondering whether whether goodies like 'project butter' can be ported to 2.3.6 gingerbread !
Me being a noob i don't know the technical aspects of what i just said so don't pick on me please ! This might seem like a joke to devs, if any ,who read this ! And i don't expect anybody to work on this after seeing this ! All i want to know is whether its possible ? Will there be any benefit ?and if so what would it take ?
Sorry if posted in wrong section !
nikufellow said:
I know this is utter noob question but can't really help it ! In this part (and i assume that in many others parts too) of the world there are still people stuck with devices running on GB not even cyanogen or other after market rom support !
This is the main reason i was wondering whether whether goodies like 'project butter' can be ported to 2.3.6 gingerbread !
Me being a noob i don't know the technical aspects of what i just said so don't pick on me please ! This might seem like a joke to devs, if any ,who read this ! And i don't expect anybody to work on this after seeing this ! All i want to know is whether its possible ? Will there be any benefit ?and if so what would it take ?
Sorry if posted in wrong section !
Click to expand...
Click to collapse
Yes it's probably possible but it would not work very well due to the major differences in the way hardware acceleration works in gingerbread compared to ICS and up. Like I said if you could get it to work the instability it would cause would far outway the performance gains. As far as what would it take, libraries and binaries would have to be heavily modified and reverse engineered, then patched it would be a big undertaking. Hope this clears things up .
Sent from my SCH-I535 using xda premium
shimp208 said:
Yes it's probably possible but it would not work very well due to the major differences in the way hardware acceleration works in gingerbread compared to ICS and up. Like I said if you could get it to work the instability it would cause would far outway the performance gains. As far as what would it take, libraries and binaries would have to be heavily modified and reverse engineered, then patched it would be a big undertaking. Hope this clears things up .
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Okay thank you very much this was the kind of reply i was looking for !
How possible does the Atrix collective development community think it would be to get some proper Tegra 2 drivers and libraries working on Jelly Bean? Impossible? Too much work? Not enough people?
With how smooth ICSROM seems to work on my Atrix, albeit with random charging and unplugging related reboots, I can only imagine that JB with hardware support would futureproof this device for a few years yet. Not everyone needs to run Unreal Engine 3 on their phone, but this handset has real potential to stay relevant.
LobotomyTH said:
How possible does the Atrix collective development community think it would be to get some proper Tegra 2 drivers and libraries working on Jelly Bean? Impossible? Too much work? Not enough people?
With how smooth ICSROM seems to work on my Atrix, albeit with random charging and unplugging related reboots, I can only imagine that JB with hardware support would futureproof this device for a few years yet. Not everyone needs to run Unreal Engine 3 on their phone, but this handset has real potential to stay relevant.
Click to expand...
Click to collapse
this thread is useless for me... Really if u keep reading on the development section u would already know that the devs have a kernel for ics. Its booting its running but not perfect so they need time for the bug fixes.
We are going to get perfect ICS maybe JB but it takes time for the Devs to create a perfect Kernel. I hope this thread is going to be closed because there engouh threads with asking about ICS/Kernel and complaining about unstable ICSROM.
@OP, I suggest next time you at least skim through the relevant topics and educate yourself. That should prevent you from doing something stupid such as opening useless threads like this.
Reported.
OP, TBH, questions go in the Q&A...and please do some research and homework regarding this Topic. Thank You.