i tink that LG was waiting for cooking a stock rom based on android 2.4 (instead of the 2.3 promised) because of their similarities, in fact the gpu accelerations for 2D, rumored for the 2.4, can only help our P500 performance.
i hope this, and you?
Ps: i tink that a P500 at 150$ with 2.4 in the very next month can bring android for many doubtful people..
I'm not really keeping my hopes up. I bet the last official update we'll receive is Gingerbread. Most companies focus on their flagship phones, and despite the O1's popularity, I don't think it'll receive much.
Also, IMHO, Google is going too fast. Manufacturers are having a hard time catching up and stuff.
But if you ask me, I'm contented with Froyo. Unless, of course, there's a really badass killer feature available only to future releases.
And I think this should be in the General category
kpbotbot- It's more like manufacturers use the differente Android os'es for marketing uses . Look at samsung , they're waiting to release the native 2.3 devices and bearly then will they release gingerbread for their current flagship : Galaxy S . It's a dirty world .
Yeah. Here's a super thank-able screenshot I took weeks ago
LG and Samsung seem like very different companies. The Optimus line is a very good buy for most carriers. It will convert a lot of users to the Android world like me. LG seems to catter to their users too.
The manufacturers should understand Android devices should follow Googles releases. It seems like most manufacturers just barely make the software and communities like xda do the actual bug fixing and create a more robust system with the custom kernel & ROM releases.
Sent from my VM670 using XDA App
why would companies spend money and time in the software when
communities like xda do the actual bug fixing and create a more robust system with the custom kernel & ROM releases.
Click to expand...
Click to collapse
@orlox - Imagine buying a phone that doesn't come with an operating system.
I prefer if companies release only the lifeless phone, and xda would give life to it.
So androids will be much cheaper
ccdreadcc said:
I prefer if companies release only the lifeless phone, and xda would give life to it.
So androids will be much cheaper
Click to expand...
Click to collapse
I like the idea!
Post delivered via piece of paper tied to a brick... sorry 'bout the window! XD
The reason I chose this phone is because, for me, it's a small portable computer. If only every bit of hardware of this phone had a corresponding device driver (that we can get hold of), I think there's nothing stopping us from using a full Linux desktop, or other operating systems capable of running on the ARM architecture.
Not so relevant note: Some say the bootloader is locked. True?
kpbotbot said:
The reason I chose this phone is because, for me, it's a small portable computer.
Click to expand...
Click to collapse
So true!
I am very satisfied with my first Android experience, in spite of all the bugs and hardware limitations of this cheap phone. Almost anything I needed but couldn't do before on my "dumb" phone became possible with this micro computer. So I don't really care if it's running Eclair, Froyo, Gingerbread, Ice Cream or Milk & Toast & Honey.
You would care if it was running Cupcake.
P.S There really is a possibility for us to get 2.4 on our phones. It is still called Gingerbread but it will support Honeycomb apps.
Sent from my LG-P500 using XDA App
there are some questions to answer, why people buy a smartphone in general. We must see the differences between users who "use" the mobile as a daily instrument, users who use the mobile to play 3D games, users who read in the internet and communicate with it and users who are tweaking/hacking (not so sad as i write here). Most of users are using their device for communication, and so the manufacturers can say "why we should develop so fast as google? Our users doesn't need the new features like NFC or other". When communities like XDA, Cyanogen,CodeAurora,androidcentral or others develop their ROMs to their needs, they should do that - they are users who "want" the features. So, manufacturers can invest more time and money in new devices for more experience and for advanced users (like technical freaks). We (users who are lucky for while) can buy the "new" device at a later time, so we can save some money. Nothing other does LG,Samsung or HTC - they are developing for the feature. The money and time to invest in updates or bugfixes are too much for the most - this could be one reason for hold back updates or dont develop. As a developer i can say, the time to spend for Gingerbread development is not small - i have needed 3 monthes to develop a rom, that have just some bugs, and i've do that for fun. for a manufacturer this is not fun
kpbotbot said:
Yeah. Here's a super thank-able screenshot I took weeks ago
Click to expand...
Click to collapse
This makes perfect sense from the carrier's perspective. If people had to pay to upgrade to the next version the carriers might have more incentive; as it is now they aren't seeing any more money so why bother investing time on something that could blow up in their face.
andy572 said:
there are some questions to answer, why people buy a smartphone in general. We must see the differences between users who "use" the mobile as a daily instrument, users who use the mobile to play 3D games, users who read in the internet and communicate with it and users who are tweaking/hacking (not so sad as i write here). Most of users are using their device for communication, and so the manufacturers can say "why we should develop so fast as google? Our users doesn't need the new features like NFC or other". When communities like XDA, Cyanogen,CodeAurora,androidcentral or others develop their ROMs to their needs, they should do that - they are users who "want" the features. So, manufacturers can invest more time and money in new devices for more experience and for advanced users (like technical freaks). We (users who are lucky for while) can buy the "new" device at a later time, so we can save some money. Nothing other does LG,Samsung or HTC - they are developing for the feature. The money and time to invest in updates or bugfixes are too much for the most - this could be one reason for hold back updates or dont develop. As a developer i can say, the time to spend for Gingerbread development is not small - i have needed 3 monthes to develop a rom, that have just some bugs, and i've do that for fun. for a manufacturer this is not fun
Click to expand...
Click to collapse
Yeah , bro , but you're one man fighting against the tides . It's bound that LG has at least a reminder of 5 man cell team working on getting gingerbread out . And besides they have other ways of getting info and ironing out bugs faster then you can .
Sad that they didn't place on the internet a god damn ETA by now .... thus I guess may or june might a realistic launch date
Oh and to be on-topic with the thread , I guess we'll see 2.4 by CM7 if any of the legendary devs still take interest in this phone ofc
+1 i second that...plus i heard that not all the code used is even OPEN..I mean mik somewhere mentioned that some libraries had no corresponding code in the source code archive....thats gotta stink plus porting of android is different than developiing Linux Distro..I mean no mailing lists and not such a big community of "porters"....but tahts just my take..
sarfaraz1989 said:
+1 i second that...plus i heard that not all the code used is even OPEN..I mean mik somewhere mentioned that some libraries had no corresponding code in the source code archive....thats gotta stink plus porting of android is different than developiing Linux Distro..I mean no mailing lists and not such a big community of "porters"....but tahts just my take..
Click to expand...
Click to collapse
you're right:
many libraries are closed source, it's like a driver from nvidia for Linux X.org.
The only way to port it to a new android version is to test if it works - if not, we have a problem. manufacturer does not support communities, so we have to build many workarounds or rewrite the code so that it works. i would wish, the manufacturers opens their drivers and codecs for playing audio and video - so we can develop faster, more stable and uncomplicated:/
back to topic:
i've readed the last days that gingerbread 2.4 is the internal 2.3.3 - let's check, if apps for honeycomb work on this version: in 2.4 there should be compatibility for the honeycomb apps^^
andy572 said:
you're right:
many libraries are closed source, it's like a driver from nvidia for Linux X.org.
The only way to port it to a new android version is to test if it works - if not, we have a problem. manufacturer does not support communities, so we have to build many workarounds or rewrite the code so that it works. i would wish, the manufacturers opens their drivers and codecs for playing audio and video - so we can develop faster, more stable and uncomplicated:/
back to topic:
i've readed the last days that gingerbread 2.4 is the internal 2.3.3 - let's check, if apps for honeycomb work on this version: in 2.4 there should be compatibility for the honeycomb apps^^
Click to expand...
Click to collapse
if everything's open then it is unlikely they make money. Then they close down and there won't be any phone.
Sent from my LG-P500 using XDA App
@yanuk... seems to be like u have not used linux before...Let me tell you how it works...Theres tons of companies (apart from thousands of enthusiasts) that write OPEN SOURCE DRIVERS for their hardware and submit it to the LINUX KERNEL maintainers(Linus torvalds included) example INTEL..If i m buying an ANDROID phone, i only want to pay for the hardware and not software..All drivers developed by the manufacturer shud be open source ..BUt instead its more like an abuse of the OPEN SOURCE community ..HOw CAn devs go ahead and hack the crap out of their phones, when they have trouble even porting newer OSes because of "some f****** proprietary driver" ...Screw the manufacturers ..I wish OPENMOKO had taken off when it had the chance..OPENMOKO = OPEN SOURCE OS +OPEN SOURCE HARDWARE with all datasheets, spec, circuit diagrams available..RUn whatever u possible can run on an it !!! My dream of having a completely Open (gtk runnin) geek device is still very distant..
sarfaraz1989 said:
@yanuk... seems to be like u have not used linux before...Let me tell you how it works...Theres tons of companies (apart from thousands of enthusiasts) that write OPEN SOURCE DRIVERS for their hardware and submit it to the LINUX KERNEL maintainers(Linus torvalds included) example INTEL..If i m buying an ANDROID phone, i only want to pay for the hardware and not software..All drivers developed by the manufacturer shud be open source ..BUt instead its more like an abuse of the OPEN SOURCE community ..HOw CAn devs go ahead and hack the crap out of their phones, when they have trouble even porting newer OSes because of "some f****** proprietary driver" ...Screw the manufacturers ..I wish OPENMOKO had taken off when it had the chance..OPENMOKO = OPEN SOURCE OS +OPEN SOURCE HARDWARE with all datasheets, spec, circuit diagrams available..RUn whatever u possible can run on an it !!! My dream of having a completely Open (gtk runnin) geek device is still very distant..
Click to expand...
Click to collapse
Seems like you have not worked in and managed any technology firms before.
I'm sincerely hoping your dream come true where you will own a successful openmoko company develop cutting edge technology with over 100 staff and offer your sw and hw for free with no claims to patent rights. All the best!
Sent from my LG-P500 using XDA App
Related
I have with all three OSs but somehow iOS and WP7 feel much more stable. They never crashed yet, iOS can't even crash I think, while Andoid crashed many times. It it because of the linux based kernel?
Your question doesn't really make sense. Android is not unstable. It just depends on your rom and hardware capabilities. If they are good, your device will be fine, if not, then of course it's not going to be the smoothest thing in the world. So blame your device (even if it's a good device, you still need to make the best out of it), not Android.
Run the latest iOS on the original iPhone. Tell me its stable
ugothakd said:
Run the latest iOS on the original iPhone. Tell me its stable
Click to expand...
Click to collapse
Classic .
Android seems pretty stable to me, I've never had any crashes on my SGS2, I've had a couple force closes but I'd imagine that's down to apps being bad rather than the actual OS.
This sounds like it was started as a troll thread by the OP to me
Given the right conditions, any piece of software can crash and do so hard
http://cdn2.iphone4jailbreak.org/forum/wp-content/uploads/mobile-substrate-crash-iphone-4.jpg
http://gradly.net/wp-content/uploads/2011/02/20110215_ibook_crash.png
iOS is a very modified verison of unix/bsd (well unix serves somewhere under it as the base), which is what linux is modeled after. Take that as what you will.
Neither iOS or wp7 allow users the chance to screw up your phone nearly as much as android does as well (well unless you have one of those android phones with a locked bootloader).
Another thing you need to take into account is the hardware restrictions used by WP7 and IOS. With WP7 you have to meet the minimum requirements set by Microsoft. IOS hardware is only built and created by Apple and each model is now only being supported for so many years before they won't allow it to be updated to the most recent IOS version.
With Android, you have multiple manufacturers creating a variety of devices where there is almost no hardware restrictions except whether the phone will run the ROM or not. Android phone hardware can vary by huge amounts of memory, CPU speeds, and GPUs.
if there are problems it has to do with the manufacturer of the phone and the rom they developed, not android. Get a nexus phone, stable, fast, smooth, and it has the vanilla version of android. After I removed all the bloatware off my phone and installed cm7, my captivates been a different phone. Makes me remember why I went with android over IOS or wp7.
Everyone seems eager to fork over their hard earn money to be Google's beta tester. But I'm more surprised at how people take pride in how "stable" android is, while they have to hack the beck out of it for it to be a decent phone.
otnos said:
Everyone seems eager to fork over their hard earn money to be Google's beta tester. But I'm more surprised at how people take pride in how "stable" android is, while they have to hack the beck out of it for it to be a decent phone.
Click to expand...
Click to collapse
Look at the nexus line, Pure Vanilla android. I don't hear too many crashes from the stock users.(if any at all)
otnos said:
Everyone seems eager to fork over their hard earn money to be Google's beta tester. But I'm more surprised at how people take pride in how "stable" android is, while they have to hack the beck out of it for it to be a decent phone.
Click to expand...
Click to collapse
Did you expect everyone to say android sucks on an android subforum? I think you would want to head to the apple subforum if you want to hear that.
People use android because it works for them. However, it may not work for everyone and those that it does not, are more than welcome to use a different phone
Hi,
first of all i want to say that this thread is in no way meant to offend or me being impatient about anything. I am just asking the question to know the answer.
I noticed, that many dev´s for the SGS2 (such as codeworkx and others) have big/giant trouble to bring a new Version to our Phones.
The problems seem to be that big that they have to wait for a Kernel from Samsung to make it even work a bit.
From my other/previous Phone, the HTC Dream i know that there weren´t such big problems.
It got 4 perfectly stable main iterations (2.0 2.1 2.2 2.3) of Android after its updates were discontinued and it already has a 4.0 version that has only 2 issues left to fix. All that without a kernel beeing released from HTC for the specific OS version. (i remember that the Camera drivers for 2.x were completely created from scratch to make it work [or so] )
My question is:
Why is it so much easier/less complicated to make a total new version run on the HTC Dream than on the SGS2? without the help of the manufactor
I'm not sure but I think its because other phones get source code releases for all the hardware or at least most of it to make porting/dev easier. Whereas Samsung hasn't released source for all the hardware in the sgs2 because of contractual obligations/restrictions from other hardware vendors that provide some the chips inside...
I also believe Samsung has modified Android quite heavily and badly in their quest to have the touchwiz interface, which also makes things difficult to reverse engineer etc...
I don't its anything actually difficult about the actual hardware itself
Sent from my GT-I9100 using XDA App
Hi everyone,
I'm a writer for LockerGnome.com and currently putting together an article exploring Google's new Android strategy. I'm looking for some opinions, particularly from developers, about what Google's new strategy portends for ROM development.
In a nutshell, here's Google's new strategy for Android: It will be giving multiple mobile-device makers early access to new releases of Android and to sell those devices directly to consumers. (Search "site:wsj.com google" for the Wall Street Journal's report. Hopefully you'll be able to access the link I've provided, but if not: Essentially, Google will be offering consumers more phones to purchase with a "vanilla Android" experience; they will then be able to take these phones to the cellular carrier of their choice. A researcher quoted in the article believes that Google is moving toward a more iOS-like experience, with less variance among devices.
What I'd like to know is what those in this community feel will result due to this new strategy. Since they're may be less variances among future Android devices, will there be less of a demand for "vanilla-ized" Android ROMs? My understanding of CyanogenMod is that one of its main appeals is that it allows for users to experience a plain, "vanilla" Android on devices -- with enough new devices already offering a pure, bloatware-less Android, will the CyanogenMod scene begin to fade in relevance?
Please let me know if I can use any of your comments in my article, and let me also know how you would like to be attributed if I use your comment(s). (Private message me, if you'd like, with a link to one of your online profiles or a website that you run, or some such thing.)
Thanks!
I'm a writer for LockerGnome and
well i dont think its gonna be an iOS-like experience at all, its all gonna be pretty much the same cept we'll have 5 nexuses, manufacturers are still gonna be making their devices with their 'OEM skins' just the like theyre doing it now. i also can feel like manufacturers are gonna release same device theyll have as nexus with their skin on top (picture the One X with the option to choose if you want it with sense or with vanilla/stock android) kinda like the Desire Z and the T Mobile G2, its gonna be even better for us flashaholics cause well be able to flash more ROMs
also Cyanogenmod its gonna keep growing cause even if its AOSP based they add their own optimizations making the experience even better, every more and more people are flashing that particular ROM even if their device has vanilla android already in it
nonione said:
well i dont think its gonna be an iOS-like experience at all, its all gonna be pretty much the same cept we'll have 5 nexuses, manufacturers are still gonna be making their devices with their 'OEM skins' just the like theyre doing it now. i also can feel like manufacturers are gonna release same device theyll have as nexus with their skin on top (picture the One X with the option to choose if you want it with sense or with vanilla/stock android) kinda like the Desire Z and the T Mobile G2, its gonna be even better for us flashaholics cause well be able to flash more ROMs
also Cyanogenmod its gonna keep growing cause even if its AOSP based they add their own optimizations making the experience even better, every more and more people are flashing that particular ROM even if their device has vanilla android already in it
Click to expand...
Click to collapse
Thanks for your comments. So with the introduction of more "Vanilla" Android devices, you believe the "flashaholic" community will continue to grow? Won't the majority of consumers who purchase the unlocked Android devices no longer have a reason to flash their devices? It's obvious that "flashaholics" enjoy optimizing and overclocking their phones (even at the expense of other things, such as battery life) -- but don't you think most consumers would prefer not to void their warranty (and would generally opt for better battery duration rather than a speed boost)?
You can use anything. Please attribute me as "lalop".
Note: An important distinction to make (not having the article at hand, I'm not sure if the researcher made it himself): Google is attempting to reduce the variance in the software of Android phones. In terms of hardware, it is the complete opposite. Encouraging competition between multiple Nexii will ensure that only the most cutting-edge designs are sent in. Without any OEM differentiation on the software, the contest truly becomes that of the best manufacturing. (This means no more half-assed Nexus specs/accessories *cough Samsung cough*.)
charssun said:
What I'd like to know is what those in this community feel will result due to this new strategy. Since they're may be less variances among future Android devices, will there be less of a demand for "vanilla-ized" Android ROMs? My understanding of CyanogenMod is that one of its main appeals is that it allows for users to experience a plain, "vanilla" Android on devices -- with enough new devices already offering a pure, bloatware-less Android, will the CyanogenMod scene begin to fade in relevance?
Click to expand...
Click to collapse
CyanogenMod turns OEM skins into AOSP, that is true, but the result can hardly be called "vanilla". The "Mod" itself adds so much customization and speed that, as I noticed firsthand from using the Galaxy Nexus, the stock ROM and CM9 aren't really comparable at all.
Now, you talk about "vanilla-ized" ROMs, but I would suggest this is a misnomer. Yes, anyone can compile AOSP if they just want a "vanilla" ROM, but there's almost no point to just stopping there and going no further. The ROM and/or kernel are just begging for your tweaks, your mild improvements, and this is precisely what drives the homebrew developer.
As such, it turns out that almost every custom ROM has something differentiating it from the original; even the so-called "vanilla experiences" are generally designed to be smoother and have better battery life. No number of stock phones from Google could possibly reduce the demand for (nor the incentive to create) such things. So I would say that the answer is "no" on all accounts.
---
Now, the effect of multiple Nexii on homebrewing that would worry me is "fragmentation" (though not in the usual sense of the word). Having five Nexuses would effectively detrone each one from its former pedestal as the (no pun intended) Nexus of development. Since most homebrew developers would probably not purchase all five (and would have a harder time maintaining all versions even if they did), this could end up having an adverse effect on their development. Although having a fleet of Nexus is practically a dream come true, I fear that five may be too many, and may unintentionally compromise their development as a whole.
Now, as pointed out by lazaro here, this would not affect ROM development per se, only low level stuff like kernels. The obvious way I can think of to avoid the issue is to mandate similar hardware for all the Nexus - and yet I feel this is undesirable. After all, competition is key here, and I'm sure we're also all waiting for our Nexus Note™, of course! *hint hint*
http://t.co/9rTNXkvM
Here are some of my thoughts on the matter.
I am more excited about this than I have been for any other Android news ever! I am ready to get out of the continuous contacts and upgrade dates, especially the high prices for service.
As far as development goes, some of the best development has been done on Nexus devices, except of course the hd2... What will be good for manufacturers is that they will receive earlier updates for android allowing them to tweak their proprietary versions sooner allowing quicker updates!
For custom rom's you will see a lot of activity.
Sent from my PC36100 using xda premium
thebobp said:
You can use anything. Please attribute me as "lalop".
Click to expand...
Click to collapse
Thank you for taking the time to post your comments; my own response to yours is below.
thebobp said:
Note: An important distinction to make (not having the article at hand, I'm not sure if the researcher made it himself): Google is attempting to reduce the variance in the software of Android phones. In terms of hardware, it is the complete opposite. Encouraging competition between multiple Nexii will ensure that only the most cutting-edge designs are sent in. Without any OEM differentiation on the software, the contest truly becomes that of the best manufacturing. (This means no more half-assed Nexus specs/accessories *cough Samsung cough*.)
Click to expand...
Click to collapse
I was vague in my description of what was mentioned about device variance in the article. Here's exactly what the writer of the article stated:
Rajeev Chand, head of research at Rutberg & Co., said Android has become a kind of "Wild West" in which app developers have struggled to make sure apps are compatible with hundreds of different Android-powered devices. Both device makers and carriers have left their imprint on devices, meaning the "customer experience is highly variant", he said.
Mr. Chand said Google's shift appears to be a move "to create a more standardized experience for consumers and app developers," similar to that of Apple.
Click to expand...
Click to collapse
Does that fit what you're asserting?
thebobp said:
CyanogenMod turns OEM skins into AOSP, that is true, but the result can hardly be called "vanilla". The "Mod" itself adds so much customization and speed that, as I noticed firsthand from using the Galaxy Nexus, the stock ROM and CM9 aren't really comparable at all.
Now, you talk about "vanilla-ized" ROMs, but I would suggest this is a misnomer. Yes, anyone can compile AOSP if they just want a "vanilla" ROM, but there's almost no point to just stopping there and going no further. The ROM and/or kernel are just begging for your tweaks, your mild improvements, and this is precisely what drives the homebrew developer.
Click to expand...
Click to collapse
The term Vanilla is how the CyanogenMod "look" is described at http://www.cyanogenmod.com/about. I should have recognized that there is a world of difference between aesthetics and performance. Thanks for pointing that out.
thebobp said:
As such, it turns out that almost every custom ROM has something differentiating it from the original; even the so-called "vanilla experiences" are generally designed to be smoother and have better battery life. No number of stock phones from Google could possibly reduce the demand for (nor the incentive to create) such things. So I would say that the answer is "no" on all accounts.
Click to expand...
Click to collapse
I don't have any experience with iOS devices; is there a similar incentive to modify iPhones and iPads purchased directly from Apple?
thebobp said:
Now, the effect of multiple Nexii on homebrewing that would worry me is "fragmentation" (though not in the usual sense of the word). Having five Nexuses would effectively detrone each one from its former pedestal as the (no pun intended) Nexus of development. Since most homebrew developers would probably not purchase all five (and would have a harder time maintaining all versions even if they did), this could end up having an adverse effect on their development.
Although having a fleet of Nexus is practically a dream come true, I fear that five may be too many, and may unintentionally compromise their development as a whole.
Click to expand...
Click to collapse
One thing to note: Google will be working with "as many as five manufacturers at a time to create a portfolio of 'Nexus' lead devices that include smartphones and tablets." To me, this doesn't necessarily imply just give devices -- there could be a few devices from each manufacturer.
thebobp said:
Now, as pointed out by lazaro here, this would not affect ROM development per se, only low level stuff like kernels. The obvious way I can think of to avoid the issue is to mandate similar hardware for all the Nexus - and yet I feel this is undesirable. After all, competition is key here, and I'm sure we're also all waiting for our Nexus Note™, of course! *hint hint*
Click to expand...
Click to collapse
Thanks again for your views. If I use your comments I'll be sure to attribute them to "lalop"; is there also a URL you are associated with that I may link to? If you prefer privacy, that's perfectly understandable. Also: Are you a developer?
Please help me to understand this..........
If android runs on top of lunix
and all android versions eclair gb, ics etc start off as basically aosp then get maufacturer specific things like blur and sense.
Why is it so hard for CM9 and 10 to fully work on the E3D when CM7 worked perfectly on the Evo4g which are both htc phones?
Its a random question and even though I just recently became a member here, ive been with XDA since i hade the original moto click which was 2 yrs ago.
Also,
What do I need to do to create themes? Ive been wanting to for a while.
Thx in advance
Deep breath. It basically comes down to the huge variety of hardware. Linux has to support hardware in it's kernel (basically a software layer that tells the operating system how to use that hardware) and each new variant of the kernel is supposed to be backward compatible (though support for very old hardware is dropped so the kernel doesn't get out of control). Now Android is a completely different branch of linux (at the moment), and each manufacturer further branches aosp and creates a different kernel for every mobile phone with different hardware. The manufacturers have to release the kernel back to the community after they upgrade but this is slow and even when they do the kernel only supports the variant of android (in this case sense). Finally if they don't release an OS upgrade at all then the kernel becomes outdated and won't support features in the new OS.
Devs feel free to correct me...
Sent from my Evo 3D GSM using xda app-developers app
CM7 is by now quite old, meaning developers have had A LOT of time to test, modify, run and perfect it, even several years ago a lot of phones had perfect CM7 ports/builds.
Both CM9 and CM10 are still quite new, and thus developers have not had that much time to modify it to run as well as CM7, but in time it'll get there, no doubt about it.
And it also depends on which developers are actively working on developing for a specific phone. As for example we now have Agrabren working on a CM10 build (GSM side) doing amazing work, while other phones do not have such developers, thus it will take longer time for those phones to get perfected.
As for the themes, it depends on what ROM you're using. There are several different ways to theme something, and they're very different if you're running either Sense 3, Sense 3.6, Sense 4, CM7, CM9, CM10 or MIUI 2.3 or MIUI 4 (etc.), so you'll have to be more specific. But it would be a good start to look in the "Themes and Apps" sub forum.
grrratt said:
Deep breath. It basically comes down to the huge variety of hardware. Linux has to support hardware in it's kernel (basically a software layer that tells the operating system how to use that hardware) and each new variant of the kernel is supposed to be backward compatible (though support for very old hardware is dropped so the kernel doesn't get out of control). Now Android is a completely different branch of linux (at the moment), and each manufacturer further branches aosp and creates a different kernel for every mobile phone with different hardware. The manufacturers have to release the kernel back to the community after they upgrade but this is slow and even when they do the kernel only supports the variant of android (in this case sense). Finally if they don't release an OS upgrade at all then the kernel becomes outdated and won't support features in the new OS.
Devs feel free to correct me...
Sent from my Evo 3D GSM using xda app-developers app
Click to expand...
Click to collapse
Moonbloom said:
CM7 is by now quite old, meaning developers have had A LOT of time to test, modify, run and perfect it, even several years ago a lot of phones had perfect CM7 ports/builds.
Both CM9 and CM10 are still quite new, and thus developers have not had that much time to modify it to run as well as CM7, but in time it'll get there, no doubt about it.
And it also depends on which developers are actively working on developing for a specific phone. As for example we now have Agrabren working on a CM10 build (GSM side) doing amazing work, while other phones do not have such developers, thus it will take longer time for those phones to get perfected.
As for the themes, it depends on what ROM you're using. There are several different ways to theme something, and they're very different if you're running either Sense 3, Sense 3.6, Sense 4, CM7, CM9, CM10 or MIUI 2.3 or MIUI 4 (etc.), so you'll have to be more specific. But it would be a good start to look in the "Themes and Apps" sub forum.
Click to expand...
Click to collapse
Hey thx guys, I got a better understanding now. I appreciate you taking the time to explain that to me.
As far as themes, i will look into that thread.
BTW this site is awesome. You guys have done a great job making all of this accessible for people who refuse to hampered by the limits of a locked s-on phone.
i have heard that Sailfish os is being built for sony X right? So when will it release....im so exciting....
Who you heard it from that it's being built
fezta said:
Who you heard it from that it's being built
Click to expand...
Click to collapse
Mate, check this Link for further information.
If you're a fan of Jolla (a mobile platform that's part Linux, part Android and loosely based on Nokia's MeeGo project), good news. The company has announced it will be releasing an official version of its Sailfish operating system for a number of Sony Xperia handsets. The news came from the firm's press event at MWC this morning, and adds a big-name brand to the currently mixed list of devices that the plucky (persistent?) mobile software has officially been ported to.
The first device to work with Sailfish, or rather, the first handset to be shown running it at MWC, is the Xperia X. Jolla says that there will be more compatible models, but the X is what it chose to show it off. Of course, Sailfish is technically available on many devices already, if you're willing to work with an unofficial port, but this time Jolla's partnered with Sony and its Open Device Platform for better compatibility.
Despite Jolla showing Sailfish on a working handset here in Barcelona, it seems there are still a few kinks to iron out. A representative told me features like "double tap" (to wake the device) aren't working yet, and support for 64-bit devices isn't as comprehensive as it is for 32-bit models (if you're into custom software, you'll likely know which yours is).
It's always nice to see alternative operating systems finding their way to mainstream phones, and seeing a Sony Xperia X running something other that the default Android certainly makes it a little bit more eye catching. I tried it for a few minutes and could see that the basic navigation was working no problem. But mostly, if you're into Jolla (which enjoys a steadfastly loyal community), then this is above all a good sign that Jolla's still committed to what it's doing.
Click to expand...
Click to collapse
If you want the official version, you'll still have to wait though. Jolla says it won't be out until late spring/early summer.
Regards
Very nice going to have a read up on this later then see what I can find out
I'll have to make my rom quick enough for people to try
No one on xx device will know me but I'm festa20 and can't get on my account. I did team Xperia roms was a long time ago but with the lack of support for this device I'm guna have a dig around with some stuff see what I can make