What's the status of an ics port now that there is cwm for the u.s ago 5.0?
Seriously? You think CWM is going to bring us ICS?
CWM is probably 1% of the work required to port ICS. ICS may not even be possible.
CM7 is more likely, but even a CM bringup to a device is tough.
People need to realize that a bringup of a newer version of Android on a device that hasn't been released for that device is almost unheard of. Even AOSP bringups for a device to the same version as what is available often fail (see Bluetooth on many CM7 ports to Samsung devices.) The GalaxyS ICS success is the exception not the norm.
I know its tough but there is still the possibility of it happening even cm7 would be great on this device
CM7 might happen... I'm not sure if I really have the time for it though.
ICS is highly unlikely unless Samsung upgrades the Player to ICS. Keep in mind that even when not trying to version-jump, I believe that CM7 doesn't have working hardware accelerated video playback on a lot of devices that have it stock - An annoyance on a phone but a killer on a dedicated media player.
Do you think its possible to port touchwiz 4.0 on the device? Is it faster than cm7?
Related
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 all,
First of all, I'm amazed and gobsmacked at how much work all the devs put into their respective ROM's, it's amazing the effort and hard work ppl put in. Passion is alive and well on XDA
Now, to business. I have my Galaxy SII, a Galaxy S, and an Acer Iconia A500. I've flashed them all with their respective ICS. I would think (and hope) that probably out of all of them, the SII has the biggest dev base and most power. The ICS ROMs for the A500 and S are almost perfect. They run completely vanilla with no or almost no bloat, they look and behave the same (icons for network activity inside the bars for example, contacts app looks the same) and have had no hiccups whatsoever.
Come the SII, the only ROMs I've seen are cooked from Samsung sources with their phone and contacts apps, they crash and reboot and if it weren't that I have gone past the point of no return in regard to effort I'd have gone back to Gingerbread days ago.
Is anyone out there developing a completely vanilla "Google" rom that isn't themed to look like ICS, but actually uses the ICS apps etc. I can't understand how the Iconia and SI can have this while the SII seemingly doesn't.
Can anyone open my eyes on this? I'd love to get something as stable onto my SII as I have with my other devices, ICS is brilliant to use on them...and barely bearable on my beloved SII.
Cheers
<:3)~
Ummmm correct me if I am wrong but that's exactly what the CM team are trying yo to do....
And you can already download and install that, so long as you are happy with the bugs at present.
Unless you meant something else???
Sent from my GT-I9100 using XDA App
You miss reading the cm9 thread. Check it out....its still alpha.
Sent from my GT-I9100 using Tapatalk
I'm more curious about the fact I would have thought the SII having a bigger user and dev base...certainly more than the A500 I thought it would have the most stable and mature code base - yet it seems the opposite is true.
I've been running 4.0.3 on my SI for weeks now and its never bugged out. Installed the A500...and Oh wow its like a brand new tablet!! I wonder is it because of Exynos or some other reason we can't have the same stability and performance right now.
Sent from my Acer Iconia A500 using Tapatalk
Your ignorance and disrespect is pretty bad (even if you don't mean it). I think you should do some reading for a while and get yourself acquainted with what's involved.
I didn't ask this to be dissed by someone...I'm sure even you would agree the development cycle and challenges for all three devices would be similar given they all use different processors. So is it easier to compile for the A8 and Tegra than the A9?
I have been looking and downloading a number of ROMs...and if someone has created a ROM in a similar vein to Thor's on the A500 and Onecosmic's on the SI, well I'd be grateful for the heads up...in fact I'm just about to download and test the Pure ROM I just spied over in dev...so see how that goes. Still I'd be happy for someones *constructive* input.
Of course I'm claiming ignorance...if I knew I wouldn't ask...geez lol
Sent from my Acer Iconia A500 using Tapatalk
It's a wonder no one bothers doing a straight AOSP compile for any device, really. CyanogenMod comes the closest. There are a few people who played with doing a straight AOSP, but they base it off CM's work and strip out the extras.
When I wanted the AOSP experience with Gapps, I installed CM7 on my SGS and installed the stock Gingerbread launcher. It was the closest I got.
Trebuchet is basically the stock ICS launcher with features added, so it won't be so bad. You can also replace it with the stock launcher as well.
Try Airbus 360s ics rom that's aosp and is fantastic he should be releasing beta 2 tonight.
sent from my iPhone 4S.
haha I bet that confused ya
You're question is a bit noob so don't expect much answers.
Here is a short one to sum it for you:
AOSP - Pure android base without modification.
CM - almost pure with modifications.
STOCK - Hardware Manufacturer (eg. Samsung's) "official originated" release.
Stock - can have it all. CAUSE - Samsung has sources and support/docs for ALL hardware API of the device.
CM/STOCK - While there are some changes BOTH use the same origin.
To sum it, for proper functionality BOTH use SAME kernel/libs base.
So if some hardware functionality broken in one it'll be broken in other =
If CM9 haz no h/w decoding === APPLIES for AOSP.
Another thing to keep in mind, CM9 currently is in the process of adding CM features so current builds are very close to AOSP with functionality.
SUM IT UP:
if (CM9 != working) AOSP.isNotWorking()!
ttg said:
if (CM9 != working) AOSP.isNotWorking()!
Click to expand...
Click to collapse
That's a piece of horrible code, dude
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.
Any odds of some dev porting this ROM to our phone? http://goo.gl/U2GMQ
onex+ uses tegra 3 processor
nearly impossible
odds are so slim it cannot be seen
I'm well aware of the processor differences, that tends to be more kernel sided though, does it not. Look at the EVO 3D, sense 4 and ICS were ported to that in just a couple of weeks and at that time there wasn't even anything close to a functional ICS ROM or kernel. Here we already have a fully functional JB ROM and kernel.
Your comparing a qualcomm device which had a port most likely from another qualcomm device to porting from a tegra device to a qualcomm device. It's not impossible but it's damn time consuming. Especially if anything is proprietary, it would have to be reverse engineered. It's sense and it's similar hardware but the rom is built around the way the hardware works, changes to the kernel to support our phones will most likely break other things in the rom since it is two different chipsets
Yeah I'm not sure what device that pretty was from, I think it was the One S though. Still the S4 and S3 SoCs are vastly different.
Alright though, I just thought it was worth bringing up while waiting for an official build for our device or a leak for ours, or I suppose the One S or AT&T.
Maybe the ROM can help toast with porting the imagesense libraries though at least. Last I heard he we was still working on finishing that up, wasn't he?
A backport on similar architecture is still easier then porting between 2 different architectures
it could be done but odds of fully functional are not promised mostly sound calls wifi etc would be broken, not to mention you'd need a sense kernel built for the port specifically. It can be done but porting something over that wouldn't work completely and spending hours, day's months getting things to work. it would most likely be abandoned.
Hello guys, I've recently upgraded from a Galaxy Nexus to a Galaxy S III, skipping the Nexus 4 for reasons I should explain only if asked.
I've been reading a lot of posts from AOSP advocates defending Samsung's TouchWiz, which makes for a rather worrying reading.
Now, I'm quite pleased with stock TW Jellybean, it's really smooth, fast, stable and not bloated at all. However, I wanted to try some AOSP roms since developers clearly had some time to work on them, and Samsung has certainly released JB source code to overcome some driver-related issues that there might have been. My question is: is TW still the best option or are there some AOSP roms that are stable, fast and working on every aspect? I'm talking about tethering, data connection, auto-brightness, battery life, bluetooth, camera... the stuff meant to work at its best on a stock TW rom.
Thanks for your help.
Well actually for me the AOSP ROMs are smoother and have all the features I could probably need....but
Samsung didn't released the sources as they told us and because of that (and a couple of proprietary reasons with Microsoft)
We can't make a fully functional camera(slight camcorder/flash stuff that have never affected me)
Can't have exfat sdcards
Can't have native FM radio
(Reason why we are not really officially supported by Cyanogenmod in their M builds)
But that's about it...I would really recommend you to try them...unless you need a Samsung specific feature like AllShare or AllShare control if you have a SmartTV...or want the extra features in the camera (BurstShot ShareShot) that I really never used..... and a lot of those features are now in CM10.1 like HDR and that stuff.
Those are my two 2 cents of the theme
Sent from my GT-I9300 running AOKP Build 6