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.
Related
What is cynagenmod and what's so "great" about it?
Thanks!
Sent from my SGH-T959 using XDA App
At the time cyanogen brought a lot of features we now use everyday. Os optimizations apps to sd. Things lf that nature. It is fully opensource and open to anyone to use.
I am fascinated and captivated by the vibrant screen on my epic galaxy s.
Nabeel10 said:
What is cynagenmod and what's so "great" about it?
Thanks!
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
The ability to customize the phone, the stability, the speed, the battery life, and it gives phones the the g1/dream froyo which I guess was deemed impossible. It also gives users great support and updates quite frequently.
duboi97 said:
The ability to customize the phone, the stability, the speed, the battery life, and it gives phones the the g1/dream froyo which I guess was deemed impossible. It also gives users great support and updates quite frequently.
Click to expand...
Click to collapse
Plus it is a large group of people that work collectively together, they along with a few others are the ones that the leading "cutting edge" devs........ they blazed the trail and now all of us and the current devs benefit from their work.
Yea. Since its built from scratch it is faster than any roms here.
The g1 roms were same speed rooted or not
When cm came it was fast! And then a rom based on cm called super d was even faster and then a european rom was fastest!
So what I'm trying to say is, CM is and will be faster than the ROMs built here overclocked or not because the ROMs found here are based on the Official Froyo made by Samsung not a Vanilla Gingerbread rom built from scratch
So I think something built frrom scratch is better than something just modified and themed
Sent from my SGH-T959 using XDA App
It's built from scratch using the AOSP source, which a lot of ROMs are not (many ROMs are merely modified versions of existing stock ROMs).
It has an extensive amount of customization and flexibility beyond any other ROM I've ever used on an Android device.
I don't mind the ROM I'm running on my Vibrant, but I miss CyanogenMod. Since the CM7 release candidate for the MT4G just hit, I think it's time for me to change it up a bit. I'm tired of my short-range wifi (seriously, less than full bars when I'm only six feet away from my 802.11n router?), non-functional GPS and totally wonky compass, anyway.
I think one of its advantages is the sheer size of the community, if you've ever used various Linux distributions the same concept applies. When your user base expands to the point where you've got dozens if not hundred of loyal users posting guides, reporting bugs, requesting features, and answering new user's questions the community really feeds on itself and builds momentum. Cyanogen is largely responsible for a lot of the momentum in the rom community, and I know it's brought more people to the community than almost any other project.
A lot of things.
The cyanogenmod options alone are worth it - VM Heap, swap, JIT, compcache, et cetera. Granted these things are more relevant to lower end devices. Then there's the native ADW launcher integration. I've never been about to replace the stock launcher with ADW and get the same results.
It's really just its use in practice. Everything works, the interface is very instant/responsive (no jagged animations/scrolling, ever), no force closes, lots of mods/hacks for it from the community, which in general is very scrutinous about performance/stability hangups. Battery life twice what you're use to.
They're the only ROM team I've donated to. I flashed hundreds of roms when I had my Magic (one of the hardware-weakest android phones) but CM is what kept it up to par, giving me an extra generation's life out of it.
I personally love all the features built in, like pulldown menu modifications, as well as pretty much customizing every aspect, NO roms like that exist for our Vibrants..
It is Cyan in color, and mod like the british music scene duh!
hmm... I might have to give cm7 a try once they get it working on the vibrant. They are working on it right? If the manufactures were smart, they would give a pre-release phone to those guys before it's available to the public. Of course, the carriers may not like it. I just purchased my vibrant 3 weeks ago (former iphone 4 user). I tried a few darkyy's roms, then toxic, then finally I stuck with trigger. I'm very satisfied with it - mainly b/c everything works nice and smooth.
I see I'm a bit late but yes, Trigger is awesome. I tried flashing others and I always come back after 2days tops.... For some reason, Trigger runs so much smoother than the other ROMs on my phone... And I have tried 2.2.1(Honestly I dont get the difference) and I am not a fan of the 2.3.3 because most say the GPS doesn't work and I use my GPS at work, yes through my phone(I'm cheap). Plus that is one of my reasons for buying a "smart phone" It has everything at your finger tips, or supposed to at least right. Hope your having fun.,..... BTW, CM is freaking awesome on every device I have seen it on...... I'm actually curious to know why it's not on the Vibrant as an official build but eh..... It will come when it's ready I suppose
It seems that cyanogenmod is very popular with other phone users, and everyone seems to want it for the vibrant as well... but can i just ask what differs cyanogenmod from say trigger bionix or eugebes rom?
It seems like there is a crapton more work involved and that you could possibly brick your phone.
Sent from my SGH-T959 using XDA Premium App
It's a pure aosp rom, that's why people go crazy about it. I ran cm on my g1 back in the day and it made it a completely different phone.
Sent from my GT-I9000 using XDA Premium App
http://lmgtfy.com/?q=whats+so+good+about+cm7+mod
Go there
How you comparing trigger with cm7... think man, gb 2.3.3 and aosp... builded from scratch... code by code... it dont have a bit of tw. Well it dont even contain 2 frameworks like tw or any other...
Sent From My CM7 HTC Glacier Running @1.401 GHz
**delete **
Sent from my GT-I9000 using XDA Premium App
Because it's a pure AOSP ROM. Build from scratch (well, a base).
Try it if you really want to know, except for GPS issues and not so good battery life, it is AMAZING.
cashyftw said:
http://lmgtfy.com/?q=whats+so+good+about+cm7+mod
Go there
Click to expand...
Click to collapse
Lol i fount it funny, never knew about that kind of searchs, haha nice...
Sent From My CM7 HTC Glacier Running @1.401 GHz
CM is the granddaddy of AOSP ROMs. Cyanogen and his team are devs cutting actual code, writing their own device drivers and system apps. The entire CM ROM is compiled from customized source code.
Contrast this with the approach taken by ROM chefs who largely assemble their ROMs out of precompiled components borrowed from different releases of the vendor's ROM binary plus some configuration hacking where the odd component has been successfully decompiled.
That's not to belittle the achievements of the top chefs in any way - it's frankly astonishing that this school is viable at all, they seem to be operating mostly blind so it's more art than engineering in some respects.
But both approaches have their strengths. OEMs like HTC with access to detailed specs for their own hardware and low-level API's can produce better drivers and better apps that work closely rough drivers (like the camera app), but at the other extreme, AOSP code can sometimes include features the vendor left out or even implement a completely rethought and altogether superior design.
It's unfortunate that the closed source strategy of vendors with their signed modules often denies us the opportunity to combine the best of both. I'm particularly thinking of how juice defender can only control the toggling between 2G/3G radio on AOSP ROMs because the radio driver will only respond to code signed with the same key as itself. Aint signed code wonderful, eh?
Sent from my Desire HD using Tapatalk
Another reason is quick updates.
CM has updates before any major manufacturer and they're updating phones that manufacturers abandoned a long time ago.
I ran CM on my G1 and I've been seriously considering making the jump with my Vibrant any day now.
for me, it's long term support. once cm adds a phone, then that phone is typically going to be able to easily be upgraded to the newest android os and typically very shortly after it comes out. like many others, i had a g1 and because i cm i was able to get more life out of the device by ocing it and updating it 2.1 and 2.2.
go install cm7 and you will see what's good about it. the only major problem with it right now is no gps. after running cm7 i went back to biwinning and bionix, but that was short lived, i'm back on cm7 because having 2.3.3 > gps, for me.
Yep, CM7 4/21 nightly + cm7 Kang kernel, overclocked to 1.2 GHz + ondemand Governor equals the fastest I have gotten my Vibrant.
I have a Nexus S, right now it's stock 2.3.4 but when Cyanogenmod gets updated to 2.3.4 then for sure I will flash it. Why? When I already have stock? Well have you seen the the things you can do on that thing? You can add a music widget built right into the lockscreen, change themes with ease, change what the search key does, change the lock screen style, and the browser is improved ( incognito mode for one) you also get some fixes that Google almost never fixes, plus stock 2.3.3-2.3.4 disables Facebook sync with your contacts, however Cyanogenmod removes this thing that Google put... basically you can customize the thing like crazy. Plus it still remains stock, but the entire experience can change. I made my Nexus S look like Sense, changed how the notification bar and other aspects of the UI looked, changed the launcher to a themed launcher pro and changed the lockscreen to lense style, boom Sense style completely. Also if your device isn't stock you can install it and you make it stock, a problem with Sense is that a lot of the time the software disables things that some apps might need ( making things like wiimotes not work on it) but if you have Cyanogenmod, it eliminates that.
Sent from my Xoom
How is the battery life when using cm7 on our vibrant?
Too bad it doesnt have gps i actually use it so ill have to wait until gps works on it
Sent from my SGH-T959 using XDA Premium App
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
ION vs PMEM
What is the difference?
Google is your friend - http://lwn.net/Articles/480055/
In the case of the Rezound specifically, ION is generally faster and less laggy, but has a purple tinted camera, and no working front camera (for now).
To quote shrike (I hope that's alright)
Originally Posted by shrike1978 View Post
ION is the new unified memory management architecture that Google is advancing. Prior to ION, every SoC manufacturer had their own way of doing memory management. Qualcomm's was pmem, Nvidia's was nvram, etc. It made it's debut as an option in ICS and is preferred in JB. Being unified also means that it is a good candidate for integration into the Linux kernel mainline, which would mean that Android would no longer require it's own separate branch of Linux.
So I've read this but what would that mean in terms of developement? If Android didn't have to be a separate branch of Linux, would it be easier to spread ROMs to all the different phones?
regnsy pronounced
noo_too_droid said:
To quote shrike (I hope that's alright)
So I've read this but what would that mean in terms of developement? If Android didn't have to be a separate branch of Linux, would it be easier to spread ROMs to all the different phones?
regnsy pronounced
Click to expand...
Click to collapse
I'm not a dev, but in my understanding the biggest hurdle for porting ROMS is device drivers. It is relatively easy to port a ROM from the HTC One X to the HTC Rezound, because they are made by the same manufacturer, have the same system-on-a-chip manufacturer (Qualcomm) and have a similar stock kernel based on different versions of HTC Sense.
But porting a ROM from, let's say a Samsung Galaxy III is nigh impossible, because it uses a different system-on-a-chip exclusive to Samsung phones and its stock kernel is based on TouchWiz. And even though Android is based on Linux, each of the phone manufacturers have slightly different ways of organizing system files that set the various system options. So a kernel patch that works on one device probably won't work on another. (kernel level features such as GPU overclocking, two-way call recording etc. rely on these system setting files).
Even among phones made by the same company, you may have hardware differences such as different camera technologies, different screen resolutions, etc. that make porting harder.
That's why cyanogenmod, AOKP and MIUI are so valuable and appreciated, because they organize porting of a ROM that, as far as the kernel and GUI are concerned, vary little between devices. However those projects still have to rely on what manufacturers choose to release as open source to develop hardware device drivers to port the ROM to each device.
And then you have the problem of, what level of Android is officially supported by the manufacturer? The Droid Incredible 2, for example, is still waiting for an official ICS release it may never get, which means running Jellybean as it is meant to be run is that much harder. It's hard enough on the Rezound, where we have official ICS kernel source.
That's why I give lots of kudos to people who take custom ROMs like BAMF paradigm, paranoid android and the like that were developed for other devices and port them to the Rezound. And mega kudos to people like chad who can port/re-factor underlying hardware code originally developed for another device to work on the Rezound. We're talking crazy wizard-level stuff like memory management, camera, hardware graphics optimization (Project Butter).
It makes stuff awesomer
wildstang83 said:
It makes stuff awesomer
Click to expand...
Click to collapse
An answer i can understand.....thx!
Dcnovicky said:
An answer i can understand.....thx!
Click to expand...
Click to collapse
Ha, anytime my friend
Sent from my ADR6425LVW using Tapatalk 2
brenuga said:
I'm not a dev, but in my understanding the biggest hurdle for porting ROMS is device drivers. It is relatively easy to port a ROM from the HTC One X to the HTC Rezound, because they are made by the same manufacturer, have the same system-on-a-chip manufacturer (Qualcomm) and have a similar stock kernel based on different versions of HTC Sense.
But porting a ROM from, let's say a Samsung Galaxy III is nigh impossible, because it uses a different system-on-a-chip exclusive to Samsung phones and its stock kernel is based on TouchWiz. And even though Android is based on Linux, each of the phone manufacturers have slightly different ways of organizing system files that set the various system options. So a kernel patch that works on one device probably won't work on another. (kernel level features such as GPU overclocking, two-way call recording etc. rely on these system setting files).
Even among phones made by the same company, you may have hardware differences such as different camera technologies, different screen resolutions, etc. that make porting harder.
That's why cyanogenmod, AOKP and MIUI are so valuable and appreciated, because they organize porting of a ROM that, as far as the kernel and GUI are concerned, vary little between devices. However those projects still have to rely on what manufacturers choose to release as open source to develop hardware device drivers to port the ROM to each device.
And then you have the problem of, what level of Android is officially supported by the manufacturer? The Droid Incredible 2, for example, is still waiting for an official ICS release it may never get, which means running Jellybean as it is meant to be run is that much harder. It's hard enough on the Rezound, where we have official ICS kernel source.
That's why I give lots of kudos to people who take custom ROMs like BAMF paradigm, paranoid android and the like that were developed for other devices and port them to the Rezound. And mega kudos to people like chad who can port/re-factor underlying hardware code originally developed for another device to work on the Rezound. We're talking crazy wizard-level stuff like memory management, camera, hardware graphics optimization (Project Butter).
Click to expand...
Click to collapse
I'll hit that thanks button just for that essay you typed
Sent from my ADR6425LVW using xda app-developers app
Hi,
I've read that KitKat would need less resource compared to JB.
Since there are already ROM's based on JB for the Legend, do you think that a custom ROM will rapidly appear based on KitKat for this phone?
Thanks.
No.I don't think there are any developers left on this forum.
I too believe this won't happen, sadly. JB for Legend wasn't such a good idea, it simply can't run smoothly on that device. But, if what google says is true (about the hardware requirements), then 4.4 could be the greatest thing that has happened to this phone in a while. I still use my Legend as an mp3 player, but i would just love it if it was more functional, so i could use it in some high-risk situations (to avoid breaking my GN4). This could be Legends last chance to die with honor
Personally I have the Baked Blackbean Rom on my Legend (JB thus) and I'm rather satisfied of this Rom (thank you to the team BTW).
It lags a bit and there are some bugs but it allows me to play with the latest versions of the apps (I love the latest version of gmail for example).
Give it a try if you haven't already. The Legend deserves a better end than as a mere MP3 player .
mr.death7 said:
Personally I have the Baked Blackbean Rom on my Legend (JB thus) and I'm rather satisfied of this Rom (thank you to the team BTW).
It lags a bit and there are some bugs but it allows me to play with the latest versions of the apps (I love the latest version of gmail for example).
Give it a try if you haven't already. The Legend deserves a better end than as a mere MP3 player .
Click to expand...
Click to collapse
I'm also using JB on my Legend, but it is not really that stable (don't get me wrong, congrats to the developers, they did a great job), but it just feels too "heavy" on the phone. My biggest problem was the low amount of internal memory - yes, i know you can create a partition on the sd card, but i've never managed to accomplish it. Tried everything, just wouldn't work. So I really can't use the latest app version, as i can have about three apps installed at a time xD
Yeah, I know exactly what you mean. The app that launches 10 sec after you put your finger on it...
For the internal storage, I use Link2SD, which actually works pretty well. When I check, it tells me that I got something like 280MB in use and still have 70MB free.
I just created like you said a second partition (using a soft [named Mini-Tool if I remember correctly] in Windows while my phone was plugged in USB) and then using this second partition to install my apps.
Are you interested in trying again ? You have another phone but, anyway...
I've been part of legend community for about 2 years now, never got into full blown deving, rather doing relatively small mods, tweeks and stuff for personal use only (read, cutting my teeth with android).
Activity in legend has unfortunately died over the past 3-6 months and I haven't seen much from our last major Dev zeubea for long time, so unless there is a skilled Dev equal or better than zeubea out there that loves the HTC legend, its not going to happen. Even then given that jb version never really got finished to stable version, I very much doubt KitKat would come anywhere near the level that jb reached simply due to lack of source code for the required harware drivers...
Ya never know your luck in a big city...
Sent from my GT-I9505 using xda app-developers app
Well, let's hope such a developer exists than...
KK has been ported to the HTC Desire so there's hope
and sorry to hijack, but is anyone willing to test some gapps? Would be appreciated, cheers!
http://forum.xda-developers.com/showpost.php?p=47101145&postcount=204
Ah cool! That's indeed a good news!
Thanks for the info.
KK was said to be optimized for devices with 512 MB+ RAM via Project Svelte. The Legend unfortunately doesn't even have that much.
But, I ask, why would everyone ideally want to have their Legends running Android 4.x? I don't understand why because although Gingerbread is now running on less than half of all Android devices, it was the last OS on our phone to run fluidly and with stability. With JB and above, Google's cramming more and more features into Google Play services, which really brings down the space the Legend has in its internal memory for apps. KK just won't run like Google intended to on this device. I just don't understand why people want the latest and greatest on a ~4 year old device. Maybe you have your reasons, and I'll respect that, but I can't think of any reason why personally.
It hurts to say, but with the Legend nearing four years since announcement, this phone isn't worth being developed for anymore. It wasn't that huge of a hit, like the original Desire or the Sensation. Therefore, it tends to be more forgotten. It doesn't have the computing power of neither of these devices, nor does it even come close to it, so while the aforementioned devices are slowly getting the bleeding edge, we'll be getting it slower, if at all.
It's a harsh reality, but if you want the best experience in Android possible, it's time to upgrade. ~Four years, that's around two two-year contracts. For Legend owners in Canada, your contract should have been up just this past summer.
This phone will always be a classic, guiding HTC through its brilliant design language with the HTC One flagship and its variants. Its legacy is shown on the devices that succeeded it. Unfortunately, I don't believe it has anything more to bring.
Hi Asovse1,
Thank you for your opinion.
You're right when you say that 4 years are an eternity for a smartphone but personally right now I can't afford a new device that would have for example the screen quality of the Legend (which has an amoled screen while even recent phone still use LCD). If I buy a new phone around 99 $ (my budget) I would have a screen with a poor resolution so the change is not worthy.
I have a JB Rom on my Legend and I can enjoy the last version of GMail for example that has really cool stuff. And this version of gmail runs rather smoothly on my phone, so why not ?
The Legend doesn't have 512MB RAM, for this reason he wasn't supposed to support ICS, but it worked, so while it works with the new version of Android, I will hope that a talented developer will build a Rom for this fantastic phone .
Or maybe I can wait just a few days ans see what the Moto G has to offer...
Cheers.
Hear hear, someone in the same boat as myself. Still using my Legend for daily use. I am on CM7.2 stable. Only GPS is not reliable. Tried a lot higher roms, never worked out well.
I am looking into importing a Chinese phone. Nice specs and an affordable price. Only risk is a broken phone within 2 years...
Sent from my Legend using xda app-developers app
Hi Wim,
Have you ever tried the Baked one as I mentioned earlier?
I have it on my Legend and use it daily without any problem. And the GPS works too, even if sometimes it needs some time to find itself, once it's done, it works perfectly.
Hello there,
I have great news for all the fans of the Legend: it might get KitKat !
http://forum.xda-developers.com/showthread.php?t=1905588&page=28
Let's cross our fingers !
Cheers!
It's been 5 years, any news?