...of the year 2015.
moderators: I'm very sorry (not really) for the sarcastic spam, but I've grown more and more unhappy with Samsung in regards to them keeping their promises. At this point, other than my P6210 tablet, I've sold every single one of my android devices that are controlled by samsung.
I still have a galaxy nexus, but thankfully the source for that is controlled by google - not samsung.
Q1 has come and gone. No ICS. Hell, they STILL won't release the source for the damn wifi driver! The same source that qualcomm (who owns atheros) released under the GPL, but samsung says that they (samsung) get to choose between GPL and BSD and they are choosing BSD. Why? What good does it do Samsung to NOT release the source? If Apple.. er.. samsung wants to treat their customers this way, I can take my future business elsewhere.
If I wanted a closed platform, I'd buy an iphone or ipad.
Gary
I agree
And I feel that with the increasingly number of similar tablets that Samsung puts in the market, the hopes for further updates are extremely low. Maybe we will have a first revision of ICS, but better it is good, because I don't think they will fix whatever is wrong.
I will agree with Gary in terms of how closed Samsung is making their "open" device. Though that is coming from a developer. From a consumer perspective having or not having ICS makes no difference to them. Unfortunately as our world becomes more tech illiterate the more these devices will become more and more locked down and cause stagnation in innovation.
Sorry to hear you leaving though you were a great help here.
I'm not leaving the p6210... its the only samsung device I'm keeping. However, until and unless Samsung gives me something more than incomplete and outdated source, there's nothing else for me to do. I can't fix the wifi bugs, because Apple..er..Samsung won't release the source.
If they ever get around to pushing out ICS (big "if" there) AND they release the source, I'll play with that. I might even find the time to just port AOSP (or even better - AOKP) over.
After using a galaxy nexus for a few days, I don't miss touchwiz at all.
Well that's good to hear... It sounded as if you were leaving us there. Though supposedly someone is making headway with wifi with the cm9 ics build. You might want to check in there.
What's with the driver? Does the GPL driver not support our cards, is it just missing the pci id? I'm new to this slate, so I don't have much exposure to the current issues like this.
Sent from my GT-P6210 using Tapatalk 2
Even Huawei Springboard (my 2nd tablet) already received ICS, I also disappointed a bigger company like Samsung get update slower then Huawei
Sent from my GT-P6200 using XDA App
fewt said:
What's with the driver? Does the GPL driver not support our cards, is it just missing the pci id? I'm new to this slate, so I don't have much exposure to the current issues like this.
Sent from my GT-P6210 using Tapatalk 2
Click to expand...
Click to collapse
GPL is not a driver, GPL is a open source licence.
Yes, I know the difference between GPL & BSD (both are OSS licenses.) I was asking if the GPL version would work if it was updated with the p6210 WIFI PCI ID.
Sent from my GT-P6210 using Tapatalk 2
fewt said:
What's with the driver? Does the GPL driver not support our cards, is it just missing the pci id? I'm new to this slate, so I don't have much exposure to the current issues like this.
Click to expand...
Click to collapse
For doing an AOSP type implementation where 100% of the source is available, yes - it might.
For trying to do a kernel that would work with the rest of the samsung firmware, no - it won't. There are 3 parts that have to work together here: the actual driver (ar6003.ko in samsung's firmware), wpa_supplicant (which, on stock p6210 implementations has a ar6003 specific interface compiled in) and the rest of the firmware (settings page, etc.)
The "rest of the firmware" calls wpa_supplicant to do the dirty work of the wifi driver, and wpa_supplicant makes calls directly into the driver.
I'm sure I typed all this before, in another thread months ago, and went into great detail. The short version is this:
I need the source for the ar6003 driver and the source for wpa_supplicant (for the ar6003 interface.) Both of these are released in "GPL/BSD" dual licenses by their authors, meaning that samsung can, in theory, choose which license model to use when they include that code. Samsung has told me that they are claiming BSD for both and therefore will refuse to release the source to any modifications that might be included.
I've tried pulling in the generic ar600x code from mainline linux, but it wasn't working for me with the rest of the samsung stuff... and I simply don't have the time to mess with that for endless hours just because samsung is trying to be apple-like and make android a closed platform.
garyd9 said:
For doing an AOSP type implementation where 100% of the source is available, yes - it might.
For trying to do a kernel that would work with the rest of the samsung firmware, no - it won't. There are 3 parts that have to work together here: the actual driver (ar6003.ko in samsung's firmware), wpa_supplicant (which, on stock p6210 implementations has a ar6003 specific interface compiled in) and the rest of the firmware (settings page, etc.)
The "rest of the firmware" calls wpa_supplicant to do the dirty work of the wifi driver, and wpa_supplicant makes calls directly into the driver.
I'm sure I typed all this before, in another thread months ago, and went into great detail. The short version is this:
I need the source for the ar6003 driver and the source for wpa_supplicant (for the ar6003 interface.) Both of these are released in "GPL/BSD" dual licenses by their authors, meaning that samsung can, in theory, choose which license model to use when they include that code. Samsung has told me that they are claiming BSD for both and therefore will refuse to release the source to any modifications that might be included.
I've tried pulling in the generic ar600x code from mainline linux, but it wasn't working for me with the rest of the samsung stuff... and I simply don't have the time to mess with that for endless hours just because samsung is trying to be apple-like and make android a closed platform.
Click to expand...
Click to collapse
wpa_supplicant is what's probably killing you if it has been forked, more so than the driver itself. Makes perfect sense why it is such a pain.
Do you know of a thread somewhere that describes how to get started building kernels for these things? I'll play around with it, I don't have much experience with Android outside of some hacking with adb but I know my way around Linux as well as most.
I'll start poking around more, but thanks for the short version it is appreciated.
Zadeis said:
I will agree with Gary in terms of how closed Samsung is making their "open" device. Though that is coming from a developer. From a consumer perspective having or not having ICS makes no difference to them. Unfortunately as our world becomes more tech illiterate the more these devices will become more and more locked down and cause stagnation in innovation.
Sorry to hear you leaving though you were a great help here.
Click to expand...
Click to collapse
I disagree that consumers don't care. Call me naive that I didn't scour the internet deep enough to find good, honest feedback, but the only reason I chose the more expensive Samsung 7.0 was its IR blaster and its advertised ability to control the home theater components with it. That feature is bolded and blaster all over Samsungs feature list and descriptions.
So I get me GT7+ 2 months ago and how does it work? It doesn't do what I want. Peel, the only IR app available for the tablet force closes every time, and updates have proven fruitless. I email the developers of Peel and what do they tell me? They won't fix (or can't fix) the problem until they get updated ICS drivers for the SG7+. So for now I am **** out of luck until Samsung updates. I try to get a hold of Samsung tech support and get nowhere. The best I got was from a "Live Chat" bot that said ICS will be available in the future. No more specifics could be given.
And to add insult to injury, the screen on my Tab is fritzing out and needs to be sent back for service already. On paper the SG7+ looks great but for me it's been nothing but a hassle.
I want ICS so I can have everything work as advertised. It probably never will so I'll chalk this one up to experience and sell the POS.
Just remember that samsung never actually promised ICS for this device. There were "leaks" (completely unofficial) and "targets", but never any legally binding promises.
Why should samsung spend the money developing ICS for people who own a device when that device is ALREADY 6 months old? At the rate samsung is coming out with new devices, they need that money developing for newer devices.
In a sick kind of way, this makes sense to me. (Samsung seems to be forgetting, however, that I buy a new tablet every 6-12 months and my next one will NOT be a samsung device due to the experience I'm having with them over this one.)
What doesn't make sense to me is the way that they are withholding source code. It just doesn't profit them or even save them money. There isn't even anything proprietary in the ar6003 drivers and wpa_supplicant code. No trade secrets. It's almost as if they are deliberately chasing AWAY technical people... but that just doesn't make sense when your primary OS is an open one that depends on geeks.
The only thing I can figure out is that they are, in fact, hiding something. Perhaps they are embarassed about the programming? Perhaps they cut corners and don't want it to become public knowledge? Maybe they just have a nasty streak and are deliberately trying to prevent any repeat customers. I'm just taking wild guesses here - I honestly don't know.
The flip side to that is that you are aware of the fact ICS will have an impact to functionality on a current situation. Most people won't, as you put it, scour the internet to find the solution or future solution, to a problem and actually understand that an OS update will have a great impact on their experience with their current product. I had a discussion with someone the other day on this mindset and how it has been driving me nuts. (This person also considers them self an average user and not like most of us on this forum) You know that android 3.2 is on your your Tablet. YOU know what android 4.0 ICS is and how it impacts you. Most don't. That is what I was trying to conveying.
Though I am surprised that you are having issues with it on account I have had no problems with it (even though I haven't used it much).
P.S. Sorry about the irritated tone I do not mean any harm it's just a sore subject with me :/
Zadeis said:
The flip side to that is that you are aware of the fact ICS will have an impact to functionality on a current situation. Most people won't, as you put it, scour the internet to find the solution or future solution, to a problem and actually understand that an OS update will have a great impact on their experience with their current product. I had a discussion with someone the other day on this mindset and how it has been driving me nuts. (This person also considers them self an average user and not like most of us on this forum) You know that android 3.2 is on your your Tablet. YOU know what android 4.0 ICS is and how it impacts you. Most don't. That is what I was trying to conveying.
Though I am surprised that you are having issues with it on account I have had no problems with it (even though I haven't used it much).
P.S. Sorry about the irritated tone I do not mean any harm it's just a sore subject with me :/
Click to expand...
Click to collapse
The latest release od Peel finally has it working on such a basic level that's it is no more useful that the remoate that shipped with my television. It can tuen my TV on & off, it can change channels, and it can adjust the volume of the television. When I want to add another device such as a cable box or AV receiver? No go. It will power the device in setup but it will not save it to the application for future use. I blame buggy peel software. It can obviously fire the codes it needs but they're going to blame Samsung and say it's a driver issue. The only way I could believe that possible is if the radio frequencies vthe two devices used were too close together to be discerened by the GT7+. Regardless, it's a feature which does not work as it explicitly advertises and, as Gary points out multiple times, they refuse to release the source code so crafty & eager developers (which I am not) can make their own functional software.
Peel doesn't use RF... it fires the infrared emitter on the device. I actually played with the "peel" software once. For about 10 minutes. I found it a complete joke and froze the software. I never really cared much about that aspect of the tablet. To me, its for reading ebooks, playing games, and "tinkering." Okay, more for tinkering - but don't tell my wife that. She already yells at me about how expensive my toys are.
garyd9 said:
Peel doesn't use RF... it fires the infrared emitter on the device. I actually played with the "peel" software once. For about 10 minutes. I found it a complete joke and froze the software. I never really cared much about that aspect of the tablet. To me, its for reading ebooks, playing games, and "tinkering." Okay, more for tinkering - but don't tell my wife that. She already yells at me about how expensive my toys are.
Click to expand...
Click to collapse
I bought this Tab for the exact same reasons, I was actually going to get the Kindle Fire as all I really wanted was an e-reader, but the IR Blaster changed my mind. I set up Peel for my home theater and used it once than decided my universal remote for my dish actually works better and haven't used it since. I came in knowing from reading teh threads that Samsung wasn't the greatest at support or putting out updates but all I wanted really was the ability to root it to remove bloatware. IMO HTC devices are much better and easier to customize as HTC is more open about sharing the source code and also provide their own program to unlock their devices. But they at one time were as tight fisted as Samsung and getting updates out of them is still excruciatingly slow. Hopefully Verizon will be getting a One X device soon as I'm up for an upgrade in July and right now the best HTC device they have is the Rezound.
fcorona76 said:
The latest release od Peel finally has it working on such a basic level that's it is no more useful that the remoate that shipped with my television. It can tuen my TV on & off, it can change channels, and it can adjust the volume of the television. When I want to add another device such as a cable box or AV receiver? No go. It will power the device in setup but it will not save it to the application for future use. I blame buggy peel software. It can obviously fire the codes it needs but they're going to blame Samsung and say it's a driver issue. The only way I could believe that possible is if the radio frequencies vthe two devices used were too close together to be discerened by the GT7+. Regardless, it's a feature which does not work as it explicitly advertises and, as Gary points out multiple times, they refuse to release the source code so crafty & eager developers (which I am not) can make their own functional software.
Click to expand...
Click to collapse
Why would Peel blame Samsung? From what you described, the hardware is working properly but the functionality to save multiple devices is missing in software.
I think this is what Zadeis is trying to get at with regards to expectations - Peel sounds like it's either broken or not designed to meet your expectations. Either way, it's not something that's going to be addressed by an ICS update.
I think you hit the nail on the head when you say that the GT7+ doesn't work as advertised. But the proper course of action here is to seek remedy with Samsung, not wait for a software update. When you get a bad meal at a restaurant, you send it back. You don't eat it, then hope dessert will be better.
Apologies if my tone comes off as harsh or unsympathetic, I do not intend to be either, but pinning too many hopes on to an OS update is just setting yourself up for more frustration down the road when it doesn't match your expectations.
---------- Post added at 06:21 PM ---------- Previous post was at 06:13 PM ----------
garyd9 said:
What doesn't make sense to me is the way that they are withholding source code. It just doesn't profit them or even save them money. There isn't even anything proprietary in the ar6003 drivers and wpa_supplicant code. No trade secrets. It's almost as if they are deliberately chasing AWAY technical people... but that just doesn't make sense when your primary OS is an open one that depends on geeks.
The only thing I can figure out is that they are, in fact, hiding something. Perhaps they are embarassed about the programming? Perhaps they cut corners and don't want it to become public knowledge? Maybe they just have a nasty streak and are deliberately trying to prevent any repeat customers. I'm just taking wild guesses here - I honestly don't know.
Click to expand...
Click to collapse
I think you already answered this question in what you meant as a joke earlier... Apple.
Samsung makes Apple's SoCs. GT7+ uses Samsung's own Exynos SoC. I think chances are good that Exynos and the A5 share IP and therefore, Samsung might be withholding the source code because the modifications they've made include IP that is covered by whatever NDA exists between Apple and Samsung.
so what is the latest news on ics update for the 6210 ? , guessing samsung said no ics love for us ? , or .... just wondering what latest news is ..
h2g2 said:
Samsung makes Apple's SoCs. GT7+ uses Samsung's own Exynos SoC. I think chances are good that Exynos and the A5 share IP and therefore, Samsung might be withholding the source code because the modifications they've made include IP that is covered by whatever NDA exists between Apple and Samsung.
Click to expand...
Click to collapse
You are a bit confused, I think. The exynos isn't the problem. While samsung hasn't exactly given us full technical documents on it, they added support for it in the mainline linux kernel - publishing enough source. They pretty much HAD to do that, as CPU support in linux can't be done as a module, and therefore must be opensourced in order to run linux at all.
The issue, at least in the case of the 7+, is the wifi chip/driver. It's an atheros 6003 chip. Qualcomm (who owns atheros) released the driver for that under the GPL. Samsung has claimed to me that they (samsung) are licensing it from Atheros under terms that allow them to choose to re-release the driver under either GPL or BSD terms and that they (samsung) are choosing the BSD model (which doesn't require the release of source.) In theory, Qualcomm could FORCE samsung to release the source, but I doubt qualcomm really cares too much. In fact, the module itself as released in binary form in the 7+ firmware (at least up to LA1) actually claims GPL licensing. (Can be verified by using modinfo on ar6000.ko) However, only the copyright holder can enforce the licensing.
A nearly identical situation exists with wpa_supplicant and the intergration between ar6003 and wpa_supplicant. In that case, I know for a fact that the author allows either GPL or BSD terms so wouldn't force the issue.
Those are the only two things I, personally, care about right now. If I had the source for those two parts, I'd be able to not only FIX the wifi issues on the p6210, but also enchance the functionality. I'm also unable to make certain unrelated changes to the kernel, as doing so without being able to recompile the ar6003 driver will render the existing ar6003 non-functional.
Related
I am genuinely pissed after they postponed the ICS event because I felt like that would be the infuses' time to get current with its OS. Maybe I'm venting my frustration a bit but 500K+ devices are turned on per day(at least for the next few months). I see that version pie chart and Froyo is still number 1 despite GB releasing roughly 10 months ago(not to mention a new version is weeks from releasing) . It's exactly why I come here.
I would also like to point out that the Fragmentation also causes what I like to call a popularity contest. Yes you have a crap ton of device options but guess what the carriers and manufacturer are making sure the cash cows are first in line. Do you think they have as many engineers/developers working with the ChaCha as they do on sgs2? Hell no
Why is Google shooting themselves in the foot in staying current? Why on earth haven't they sat down with the phone manufacturers and hammered out some sort of standard to speed up adoption of new OS?
Android has a wide array of devices and that makes them unique and better than the competition by offering choice.
I understand that the burden of keeping up to speed primarily falls to the manufacturer/carriers which blows for us. The maker/google contract states the carrier only has update the device for 18 months. The definition and or frequency of an update is obscure at best.
I don't even want to guess how much money is being wasted on development overlapping costs because of the hodgepodge of devices. I tried to find out exactly how many hardware devices are currently supported. I found a list of everything but no summary I didn't feel like counting the but a good estimate is 350 + worldwide.
I understand the development life cycle as well as a hardware life-cycle. I fail to understand why integration of an update takes longer than one quarter to apply.
Google develops tests and releases system updates. The manufacturers takes that update and tests it with their bull**** on top (IE touch wiz and sense) then they test on devices.
Carriers finally now test the update, certify it, and push to users(never pushed at one time because they would never risk any downtime or damage to their network).
Wtf google step your game up and reduce the impact of Fragmentation because its only going to get worse and worse.
I'm the kind of device user that makes a well informed decision and won't get a new device until it breaks or I lose it(wow thinking about it I really am horrible with phones).
I have had this phone since it came out in April and I love it (I left it in a cab during the first 2 weeks I had it but was able to get my replacement soon after). Basically I'm a day one Adopter I had my original rooted and rom'd. It drastically improved the general usability of the phone. I decided to wait to mod the phone until I got the official gb to see what it could bring to the table. I really like the one click update with no issues but my hand has been forced. My device has been becoming noticeably slower and i find myself pulling the battery at least once every 2 days. To use it as a phone like it was intended I need to port to a mod. The
Thank you developers for implementing what the billion dollar corporations could not in literally 1/10 of the time.
Sorry if I ranted I'm pissed and there's no way I'm going down to wallstreet lol I'm lazy.
Jason
Note: I also read that it could reach nearly 1 million devices a day by the end of Oct/Nov.
Sent from my SAMSUNG-SGH-I997 using XDA App
Trust me I understand your frustration! According to google ICS was supposed to be that game changing release but honestly marketing is what is stopping companies from unifying. A majority of people who get an Android device don't know what the hell to do with it, how it works, or in the most part don't care (or at least don't seem to understand the difference between froyo and GB) they just want a functioning
phone. Then comes ios, that's why it's so popular.
Sent from my SGH-I997 using xda premium
I do venture to say that android developers are hurting as well with having to unnecessarily cater to multiple versions of the same OS. I was under the impression that ICS was that as well and will be a step in that direction. Once again how long will that take to push out to consumers? Are we supposed to wait until then? Google just needs to grow some balls and steer the proverbial green bull by the horns before the amount of devices becomes the reason we dont run with the bulls anymore.
jasonk1229 said:
I do venture to say that android developers are hurting as well with having to unnecessarily cater to multiple versions of the same OS. I was under the impression that ICS was that as well and will be a step in that direction. Once again how long will that take to push out to consumers? Are we supposed to wait until then? Google just needs to grow some balls and steer the proverbial green bull by the horns before the amount of devices becomes the reason we dont run with the bulls anymore.
Click to expand...
Click to collapse
Quite frankly your frustration (and mine) is backed by the dev community; to atleast some extent. Although, I still believe google saw the bright green money tree right above their noses and since then, can not let go of the smell! In other words, there wont' be a solution in the near future.
Android has become more like Linux in terms of fragmentation!
diablo009 said:
Android has become more like Linux in terms of fragmentation!
Click to expand...
Click to collapse
I couldn't name to you all the releases that are out there
Yes I love my Infuse but Fragmentation really move my temper gauge over the top. Still loving the infuse 4g screen, but the apps almost all force close error, and my facebook app sometime does not notify me on the notifiction bar and so is textfree app, i am really getting frustrated even yahoo a very big company the video call is a mess, i am in the edge of going back to iPhone which is not my choice, but google make this on OS, stop fragmentation.
spirikitik said:
Yes I love my Infuse but Fragmentation really move my temper gauge over the top. Still loving the infuse 4g screen, but the apps almost all force close error, and my facebook app sometime does not notify me on the notifiction bar and so is textfree app, i am really getting frustrated even yahoo a very big company the video call is a mess, i am in the edge of going back to iPhone which is not my choice, but google make this on OS, stop fragmentation.
Click to expand...
Click to collapse
Are you running a custom rom, kernel, radio, are you OC/UV?
Any and all of these things can and will give you instability. I had a cm7 theme that kept crashing the system on my backflip.
The only way to do away with MOST not all issues is to live in "the box".
Android fragmentation is a big problem.
You're kidding yourself if you think the Infuse will ever get an update to ICS.
MikeyMike01 said:
You're kidding yourself if you think the Infuse will ever get an update to ICS.
Click to expand...
Click to collapse
Lol. By the ICS is out on a couple phones he would've switched to a different phone.
MikeyMike01 said:
Android fragmentation is a big problem.
You're kidding yourself if you think the Infuse will ever get an update to ICS.
Click to expand...
Click to collapse
There comes devs who may port it (hopefully). Ics is supposed to get rid of the fragmentation, and maybegoogle has something up there sleeve to combine all phones and most get ics who knows. Google and Sammy have just hired cynagen (sorry bad speling) and other major devs. They may just help figure out this problem, where they are actually smart and put this into consideration.
I want my freakin Gingerbread! Stupid fragmentation! (╯°□°）╯︵ ┻━┻
Kevinr678 said:
I want my freakin Gingerbread! Stupid fragmentation! (╯°□°）╯︵ ┻━┻
Click to expand...
Click to collapse
Really missing my old HTC phones right now. Hell, one official rom could be easily ported over to like six others with those phones. Samsung has fantastic hardware but HTC dev support is superior.
Sent from my Samsung Infuse
slapshot30 said:
Really missing my old HTC phones right now. Hell, one official rom could be easily ported over to like six others with those phones. Samsung has fantastic hardware but HTC dev support is superior.
Sent from my Samsung Infuse
Click to expand...
Click to collapse
Completely agreed. Phone's that will never officially have things like Sense 3.5 have it, and the same with firmwares. I do love my Samsung though.
Ryanscool said:
There comes devs who may port it (hopefully). Ics is supposed to get rid of the fragmentation, and maybegoogle has something up there sleeve to combine all phones and most get ics who knows. Google and Sammy have just hired cynagen (sorry bad speling) and other major devs. They may just help figure out this problem, where they are actually smart and put this into consideration.
Click to expand...
Click to collapse
Problem is that every phone has vendor-proprietary bits to handle specific hardware support that aren't portable. The Apache license of the Android userland stack makes this possible. Also the ability to have proprietary modules loaded by the kernel doesn't help - for example the FSR and RFS drivers in the Infuse. The same reason you'll likely never see ICS for the Infuse is the same reason you didn't see CM7 until Rogers Gingerbread dropped. (It existed, but it was in a barely usable state until the vendor-proprietary stuff from Rogers GB could get pulled in.)
The good news is that I think Google is forcing vendors to "play nicer" as far as the low-level vendor-proprietary code in order to make AOSP bringups easier. They enforced a LOT of standardization with Honeycomb - the question is can they keep that going with ICS without witholding source like with HC? I think that by exercising tighter control over Google Apps licensing they can.
The Galaxy S II is a hint of things to come - while it still has vendor-proprietary libraries in the userland stack, it has zero closed-source components in the kernel, unlike previous Samsungs.
Motivation and $.
my opinion only...but, phone carriers have no motivation* to update the o.s. of phones already sold.
Just a few random thoughts...
1. Limited $ to be made from you (the customer waiting for an upgrade)
....a. sale of the device is already made.
....b. buyer is already locked into a long-term contract.
2. they are a phone company not a software company...thus any software developers they might have are probably focused on future sales and testing.
3. they don't make money releasing updates to already sold phones.
4. support staff would have to be pretty good size.
I wonder if the phone providers keep software upgrade staff or do they contract that out??? say to the phone manufacture (i.e. samsung, htc)? I have no idea.
(I am assuming it's the phone carriers who are the primary cause of delays in releasing software updates...not necessarily the
* what's more important to them? Future repeat customers due to good service OR simply getting them locked into longterm service contracts? Obviously point 2.
I wish fragmentation was decreased to that of the IBM compatibe market. (Am I the only one that still calls them that?)
Sent from my SGH-I997 using Tapatalk
Interesting point I would have to say they contract the work out to upgrade versions. If they haven't already I wouldn't be surprised to see full teams being hired as android becomes more permanent.
Sent from my SAMSUNG-SGH-I997 using XDA App
Great post
Sent from my SAMSUNG-SGH-I997 using XDA App
The debate continues on TechCrunch:
http://techcrunch.com/2011/10/27/charted-android-fragmentation/
I really want some ICS love! Anyone know any thing about any ROMs based off of ICS or.... even better.... CM9? I am new to this rooting thing so...
Wow. Just search through all the topics in the skyrocket forum and you'll find your answer
Sent from my SAMSUNG-SGH-I727 using xda premium
This is like some kind of Platonic Ideal of a post here.
But, I'm pretty sure they're going to release ICS at the big Samsung/AT&T/Google event tomorrow.
Savitt said:
I really want some ICS love! Anyone know any thing about any ROMs based off of ICS or.... even better.... CM9? I am new to this rooting thing so...
Click to expand...
Click to collapse
Before you ask a question, please search the forum first, therefore other members will not give you harsh answers.
If you are looking for answers to rooting your device, please go here:
http://forum.xda-developers.com/showthread.php?t=1383464
If you are searching for rom developments, please go here:
http://forum.xda-developers.com/forumdisplay.php?f=1383
If you are searching for information on Ice Cream Sandwich, best luck is to search google or in the general section. There is NO certain release date of when ICS will be available, but there are rumors and some information that states it will be in Q1 of 2012.
Good luck to you.
Please press "Thanks" if I have helped you in anyway.
What event? Do you have a link. ?
I think he's referring to the CES 2012 event on January 9th.
Oh thats not tomarrow lol tomarrow is the 5th . Darn i was hoping there was some att/sammy event tomarrow.
Phoneguy589 said:
I think he's referring to the CES 2012 event on January 9th.
Click to expand...
Click to collapse
Indeed. That is the only upcoming event that I am aware of.
I wasn't...LOL. I can't afford to buy another phone. I just pre-ordered the Transformer Prime so I'm out of money...so my wife says.
silver03wrx said:
Oh thats not tomarrow lol tomarrow is the 5th . Darn i was hoping there was some att/sammy event tomarrow.
Click to expand...
Click to collapse
Haha me too my friend l lol the hope jumped up through my body!
Sent from my SAMSUNG-SGH-I727 using xda premium
No, I was being mean. There's not event tomorrow and ICS is but a distant dream. Enjoy your device now and don't sweat the OS version number. ICS is not going to give much more over what you have now.
I'm sort of with the OP in wanting to know about any rom based on ICS. I've searched the forums and google to no avail. I'm seeing other devices getting a version of CM9, but nothing for the Skyrocket yet.
So, my question is this: Is anyone working on an ICS rom for the Skyrocket such as CM9? If I had the know-how I'd be all over that since we have such a great and powerful phone. I know AT&T and Samsung will eventually release ICS, but it'll never compare to the likes of CyanogenMod.
No no ones working on it. Why make a hacked up version. Thats not very functional. When our update is just around the corner. We will see ics, and mabye cm9 but.not until theres a leak for the skyrocket or the actuall update.
silver03wrx said:
No no ones working on it. Why make a hacked up version. Thats not very functional. When our update is just around the corner. We will see ics, and mabye cm9 but.not until theres a leak for the skyrocket or the actuall update.
Click to expand...
Click to collapse
Thanks. Like some others I'm an impatient type...especially after using ICS on my HTC Incredible. Can hardly wait to have it on my Skyrocket, but will sit quietly (maybe) and wait.
Not saying this to start a flamewar or anything but why are so many people with talent focusing on old roms and tweaks and not ICS? IMO this is what is hurting Android with better development etc, it seems like iOS hacking and tweeking seems to be more tight-knit and innovative, where Android seems to just have (almost) the same thing over and over again.
Now, I am not saying it is the same, there are obviously very difficult functions and programming that needs to be done, but I don't get why all efforts by everyone wouldn't be focused on ICS since it is what Android needs, a fresh new OS that could change the game.
Turbojugend said:
Not saying this to start a flamewar or anything but why are so many people with talent focusing on old roms and tweaks and not ICS? IMO this is what is hurting Android with better development etc, it seems like iOS hacking and tweeking seems to be more tight-knit and innovative, where Android seems to just have (almost) the same thing over and over again.
Now, I am not saying it is the same, there are obviously very difficult functions and programming that needs to be done, but I don't get why all efforts by everyone wouldn't be focused on ICS since it is what Android needs, a fresh new OS that could change the game.
Click to expand...
Click to collapse
so you want us to randomly pull kernel source for ICS (linux kernel 3.0+) out of our ass?
samsung has not provided us with enough driver libraries/binary blobs that work properly with AOSP GB, let alone ICS.
the problem here is the manufacturers. they control the proprietary hardware/drivers we need to focus attention on something. we could hack something together, but it wouldnt be worth a crap, and by the time we got something working half decent, Official would be dropped on us with source and we would have to basically start fresh....
tl;dr: it is not worth the time it takes to try to hack something together until we have 'something' from samsung.
Pirateghost said:
so you want us to randomly pull kernel source for ICS (linux kernel 3.0+) out of our ass?
samsung has not provided us with enough driver libraries/binary blobs that work properly with AOSP GB, let alone ICS.
the problem here is the manufacturers. they control the proprietary hardware/drivers we need to focus attention on something. we could hack something together, but it wouldnt be worth a crap, and by the time we got something working half decent, Official would be dropped on us with source and we would have to basically start fresh....
tl;dr: it is not worth the time it takes to try to hack something together until we have 'something' from samsung.
Click to expand...
Click to collapse
Exactly its not as simple as ics source code being out, you also need proper drivers for the hardware
Pirateghost said:
so you want us to randomly pull kernel source for ICS (linux kernel 3.0+) out of our ass?
Click to expand...
Click to collapse
That answers a lot for me, like I said I am not too familiar coming from Iphone (day one, I just got a Samsung Galaxy S II LTE (Skyrocket))
So obviously you need the kernel to work with the OS, I didn't know they were not released.
draztikrhymez said:
....you also need proper drivers for the hardware
Click to expand...
Click to collapse
Is it harder for phone hardware? Seems to be a lot of open source, or scene made drivers for, say video cards.
Turbojugend said:
That answers a lot for me, like I said I am not too familiar coming from Iphone (day one, I just got a Samsung Galaxy S II LTE (Skyrocket))
So obviously you need the kernel to work with the OS, I didn't know they were not released.
So what exactly is open about Android then? If you are at the mercy of the manufacture's to release the kernel, how is that open?
Click to expand...
Click to collapse
Android itself is OPEN. you can go and build your very own version of 4.0 ICS right now from source code. there are very few phones you can STABLY and RELIABLY run it on though.
The NEXUS line of phones exists for a reason. they are untouched by carriers (verizon teabagged the Galaxy Nexus a little), and do not have some stupid overlay on them. they are developer devices in that it is the first phone to get android updates straight from google (no manufacturer interference required).
every other phone is tainted with a manufacturer's UI. Touchwiz on Samsung phones (galaxy nexus is a samsung but they provided the hardware not the software), Sense on HTC, 'non-blur' on Motorola, whatever Sony calls theirs...lol, LG, etc
on top of that tainted Android interface is a carrier branding or lockdown (doesnt apply to the entire world, but im only referring to US here)
so google releases new version of Android
manufacturers build phone, and customize android to fit their model (this is where android almost stops being OPEN)
carriers get a hold of the manufacturers build of android and tweak and modify it themselves (more than likely they just tell the manufacturers what they want), as you know they love to include bloat and lock it down from the user
you receive your android phone after it has gone through all those steps....long process huh? we dont get updates to newer versions as quickly because of that long process...and they would rather us buy new phones instead of improving perfectly good hardware.
Android is open in the sense that manufacturers can use it however they wish, within reason. it is not necessarily meant to be 'open' to the average end user, and manufacturers dont want you messing with the phone they built. its the reason XDA is what it is today, albeit with roots deep in WinMo hacking.
Hey Pirateghost Really great in-depth info with your permission I would like to add this info for noobs here.
Pirateghost said:
Android itself is OPEN. you can go and build your very own version of 4.0 ICS right now from source code. there are very few phones you can STABLY and RELIABLY run it on though.
The NEXUS line of phones exists for a reason. they are untouched by carriers (verizon teabagged the Galaxy Nexus a little), and do not have some stupid overlay on them. they are developer devices in that it is the first phone to get android updates straight from google (no manufacturer interference required).
every other phone is tainted with a manufacturer's UI. Touchwiz on Samsung phones (galaxy nexus is a samsung but they provided the hardware not the software), Sense on HTC, 'non-blur' on Motorola, whatever Sony calls theirs...lol, LG, etc
on top of that tainted Android interface is a carrier branding or lockdown (doesnt apply to the entire world, but im only referring to US here)
so google releases new version of Android
manufacturers build phone, and customize android to fit their model (this is where android almost stops being OPEN)
carriers get a hold of the manufacturers build of android and tweak and modify it themselves (more than likely they just tell the manufacturers what they want), as you know they love to include bloat and lock it down from the user
you receive your android phone after it has gone through all those steps....long process huh? we dont get updates to newer versions as quickly because of that long process...and they would rather us buy new phones instead of improving perfectly good hardware.
Android is open in the sense that manufacturers can use it however they wish, within reason. it is not necessarily meant to be 'open' to the average end user, and manufacturers dont want you messing with the phone they built. its the reason XDA is what it is today, albeit with roots deep in WinMo hacking.
Click to expand...
Click to collapse
Is it just me, or does it seem that the fragmentation of android has finally cost the android rom development community. Many phones have very little development while many developers are jumping ship the first chance they get to move to something like the Samsung nexus. This leaves many android users with limited options and the ability to see what this proud community can do.
There are phones out here that have unlocked bootloaders but yet they still receive very little development. I dont understand that as I've seen a lot of developers complain about locked bootloaders but yet when they move on to a new phone, they don't support some of the phones with an unlocked bootloader.
I understand as more androids hit the market that it will dilute rom development some, but it's grown into something similar to certain phones have developers gathering to them the way apple fanboys gather to iPhone. I'm disappointed in that as I always thought of android as being the anti apple.
Sent from my DROID BIONIC using XDA App
Care to give some examples? We're still seeing ROM releases for the G1, even.
The LG revolution is one example. Unlocked bootloader and not too much development.
Sent from my DROID BIONIC using XDA App
Guys please understand that this site was built in the believe that if you wanted something for your device then dig in and make it. Only developer you can relay on is the one on the other end of your keyboard.
The knowledge is out there. Don't relay on someone else do make something for your device. That will only lead to disappointment.
How do you think most of us got started?
People are only going to develop for devices they own, which means devices that they like and more often than not they are the same devices which are most popular over-all.
If dev support is what you want then choosing the device with the most support should be part of your decision making process when buying a new phone. If you buy one with little support it's on you!
lol idiots and android fragmentation. Stop speaking of it. Some ****er said something about android fragmentation and the noobs are talking about that without reading any articles, without searching themselves etc etc. There's no such thing. And just because the app drawer icon and the notification bar are placed in different placed on Tablets, doesn't mean the platform is fragmented.
Personally I would love to learn how to do something like porting my own roms onto devices, but of course I would have to be a skilled programmer. Just as a general question, how hard is it to create your own rom for a new device? Do have to do a lot of coding from scratch, or do you just sorta copy and paste a lot of stuff already out there?
Middle East Guy said:
Personally I would love to learn how to do something like porting my own roms onto devices, but of course I would have to be a skilled programmer. Just as a general question, how hard is it to create your own rom for a new device? Do have to do a lot of coding from scratch, or do you just sorta copy and paste a lot of stuff already out there?
Click to expand...
Click to collapse
I'd also like to know this. What would it take to port something like CM9 (something where the majority of the actually ROM is made by proper devs), and port it to something like the Razr dev edition (a device I know won't get any love from the community but should actually be relatively easy to develop on)? What would someone with zero coding experience actually be able to do if they had the phone, the sdk and access to CM's GitHub?
You would most likely start with CM7 and use your stock roms kernel, replacing the userland. By far the hardest part about doing a port is getting a kernel, once you have a kernel that boots the rest is mostly tweaking build props.
Simple solution. If development is that important to you, check out the forum for the device before purchase. And actually support the devs for your device.
Sent from my HTC Flyer P510e using xda premium
Konstantinos said:
lol idiots and android fragmentation. Stop speaking of it. Some ****er said something about android fragmentation and the noobs are talking about that without reading any articles, without searching themselves etc etc. There's no such thing. And just because the app drawer icon and the notification bar are placed in different placed on Tablets, doesn't mean the platform is fragmented.
Click to expand...
Click to collapse
I believe CNET coined this in regards to Android. I saw an interview with one of the CNET "yackers" and Androids big cheese.
Konstantinos said:
lol idiots and android fragmentation. Stop speaking of it. Some ****er said something about android fragmentation and the noobs are talking about that without reading any articles, without searching themselves etc etc. There's no such thing. And just because the app drawer icon and the notification bar are placed in different placed on Tablets, doesn't mean the platform is fragmented.
Click to expand...
Click to collapse
I certainly agree that "fragmentation" is used too often as a buzz-word to show the instability of Android OS. This use is really misleading. IMO fragmentation does exist in the Android OS, though, in that there are still iterations of Donut and Eclair in usable devices alongside Froyo, GB and the newer, each having it's own device/manufacturer -specific user interface as well.
Seems to me that they all do pretty much the same thing, tho. The Android core (Linux-based, right?) is the software foundation that allows the hardware drivers to work together to do the same thing device to device: make phone calls, access the internet, and play games. (Ok ... run apps)
Since the aOS core is fairly similar across devices, the bigger "fragmentation" comes from the hardware. As hardware changes, the driver support changes as well, and may become obsolete, therefore negating any upgrade options. So, if your device used a video chip from some Asian company that was destroyed in a typhoon, for example, you might never see another driver made, and also never see an upgrade to the next letter of Android.
Fits with what others have said: If you want to upgrade the OS later, either choose a very popular device, or at least one with very common parts.
Even then, there's no guarantee.
I was an iOS user for 3 years. I hacked the hell out of it. Now its been over a month I am a Galaxy Nexus user and I hack the hell out of it too, (still learning tho...) and I love it. Having said that, and having deep knowledge of both platforms, I DO believe that there is fragmentation in the Android platform.
The next step, is each one of us to think for himself what does he mean exactly by saying fragmentation. After we establish a common base, so that we all speak the same language we can continue.
My opinion is that not only there is fragmentation, but it comes in different fields. There is fragmentation in the Android versions still used, there is fragmentation in the UI,there is fragmentation in hardware, software and pretty much everywhere. Why today there are so many versions of Android apps that are still not compatible with ICS. Lazy developers? I dont know. What I do know is that if I was in iOS most of the Apps would got updated before the next version got released...
Anyway I really do not want to start a flame war. I absolutely love my Galaxy Nexus and I will continue to hack it. I also love Android 4.0. But saying whats wrong with what we like is the only way it will get better. By denying it it will only get worse. Is there a possibility I am wrong? Of course. But nevertheless, this is my opinion and I am expressing it.
My biggest gripe with Android is the inconsistency with the UI,which really degrades the experience compared to iOS. Since Google has no review process for apps I find that most Android apps are ugly compared to iOS and since the developers aren't forced to adhere to any UI guidelines there's zero consistency across the board. IMO Google really needs to be a little more evil when it comes to Android otherwise they will be in big trouble once WP7/8 gain traction,which is just a matter of time. I've used every mobile OS out there and to me Android has by far the worst user experience due to inconsistent performance,abysmal battery life and the aforementioned UI inconsistencies.
Fragmentation is exsistent. My little brother bought the LG Marquee as I told him, since the specs are similar to my galaxy S Epic 4G. Despite that, the release hasn't brought much attention since it wasn't well advertised and it paled in comparison to the Epic 4G touch being released. Even apps are fragmented, not over android version I.e. froYo, gingerbread. But over the phones themselves, since the LG marquee has a different GPU than my phone, many 3d games are similar incompatible, despite it being run by a 1ghz processor. And yes the resolution on both phones is the same. It's the only thing I don't like about android, apps take forever to update to support all platforms of hardware and software, while iOS is all the same across the board making updates faster and easier.
Sent from my SPH-D700 using xda premium
i thought this was common sense
when i wanted to buy a new android i wanted a phone that had a big following in the community
first was the nexus line
then HTC
then samsung
i went with Samsung since it was the smoothest one out there
and then it became the the most popular phone on XDA
Konstantinos said:
lol idiots and android fragmentation. Stop speaking of it. Some ****er said something about android fragmentation and the noobs are talking about that without reading any articles, without searching themselves etc etc. There's no such thing. And just because the app drawer icon and the notification bar are placed in different placed on Tablets, doesn't mean the platform is fragmented.
Click to expand...
Click to collapse
Word. Fragmentation isn't the problem... the problem is that every device needs a rom tailored specifically to it, and installing the wrong rom can brick your phone.
Sent from my Hercules using XDA App
fucxms said:
Care to give some examples? We're still seeing ROM releases for the G1, even.
Click to expand...
Click to collapse
Skyrocket.
Sure, there are a few ROMs/devs there (seanzscreams is a phenomenal guy). Cyanogenmod? Nothing. MIUI? Nothing. ICS? Nothing. Any word on any of these being available on the Skyrocket? No, with the exception that Samsung will provide and ICS kernel for the Skyrocket eventually. Will there be any ICS ROMs developed for the Skyrocket then? Who knows.
Isn't that basically supporting the notion that Android is "fragmented" on some level, in some area? That you need to custom tailor roms individually to meet the needs of each device (due to drivers, hardware, whatever) under the encompassing umbrella that is Android. Is that not a form of fragmentation? Maybe one that doesn't bother you at all, which is understandable, but has certainly ruffled the feathers of other users?
Aside from that I agree with other elements of fragmentation that members have posted about here sso far. Frag in UI is one that particularly irks me the most.
Sent from my LG-P999 using XDA App
How can people say fragmentation is not a problem? Or worse, that it doesn't exist?
I suppose this is why Google is allowed to continue this charade of an open OS.
Sent from my SGH-I897
Can anyone answer me these 2 questions? They're just eating away at me right now and its making me so confus.
1) Why does each Android device need to be individually updated to the latest OS? I mean they say its because the hardware is different on each device but look @ desktops and laptops, there are so many variable hardware parts yet every time Windows updates the old hardware is compatible with the new OS and updating is a breeze. Why is this so different for Android?
2) Why do manufacturers feel the need to lock phones down so much? For example, the only thing holding us back from having a functioning ICS ROM is the RIL, which Sammy refuses to release. Carriers and manufacturers alike get so much hate for always lagging on updating our phones to the latest OS, but if our phones werent so locked down they would never have to worry about updating a phone again because the dev community would take care of all of that for us. And if they decide that one of the 3rd party dev releases should be released OTA instead of forcing us to go online and do it ourselves then they could contact the developer and compensate them for their work so they could get permission to release it. They save time and the devs get money for something they normally do for free. Win win from my perspective.
It comes down to drivers. Computers are a mix of parts that weren't necessary built to work together in the exact combination, so all of the manufacturers provide drivers to make their parts talk to the OS in a common language. Android phones have this too, but the drivers aren't generally available to us a users; they're only provided to the manufacturers, or written specifically by the OEM, and may be under various types of NDAs or close sources licenses. Android as an OS isn't written for a specific phone or device combination (save for the Nexus releases) and does not include the drivers, so it's up to the OEM to compile it with all the drivers needed to run on a particular piece of hardware. Without those drivers, the OS won't work with a particular device.
As for the RIL, it's my assumption that it's under a closed source license provided to the OEM. Samsung has been pretty open about things, so it's more likely it's Qualcomm/VIA that has the controls in place and completely out of Samsung's hands.
Shrike is dead-on with drivers. Lockdown is also a support issue. Support a couple hundred desktops where every tom **** and harry can do whatever they want? Service packs, patch Tuesdays. fun fun fun. lock it down and only deal with apk's that don't work or don't play well together. manageable chaos is the goal.
I've been following, off and on, the struggle Entropy and other devs have been having with Samsung to ensure clearer documentation and accurate source files. It seems like Samsung may have opened up a little with their Insignal repositories. What I'd like to know - and haven't been able to discover - is if Samsung has already (or intends to) release the same for Exynos 3 (hummingbird). The source up on their regular opensource site is clearly not complete. Also, have Samsung opened up enough that Cyanogenmod will continue developing for Samsung devices?
I have a few reasons for asking. One is that I have another year on my contract with the Infuse and feel pretty annoyed that Gingerbread is as high as they'll go (my fault, but before this, I really had no concept of how primitive Gingerbread is). I'm happy that development has lived on here on xda, but I'd like to have a properly working camera. I don't think that's going to happen until Samsung open up.
The other reason is that, having read all Entropy has had to say on the matter, I won't buy another Samsung phone for me or family members until I know development can continue beyond AT&T and Samsung's arbitrary schedules.
Whizzpopper said:
I've been following, off and on, the struggle Entropy and other devs have been having with Samsung to ensure clearer documentation and accurate source files. It seems like Samsung may have opened up a little with their Insignal repositories. What I'd like to know - and haven't been able to discover - is if Samsung has already (or intends to) release the same for Exynos 3 (hummingbird). The source up on their regular opensource site is clearly not complete. Also, have Samsung opened up enough that Cyanogenmod will continue developing for Samsung devices?
I have a few reasons for asking. One is that I have another year on my contract with the Infuse and feel pretty annoyed that Gingerbread is as high as they'll go (my fault, but before this, I really had no concept of how primitive Gingerbread is). I'm happy that development has lived on here on xda, but I'd like to have a properly working camera. I don't think that's going to happen until Samsung open up.
The other reason is that, having read all Entropy has had to say on the matter, I won't buy another Samsung phone for me or family members until I know development can continue beyond AT&T and Samsung's arbitrary schedules.
Click to expand...
Click to collapse
You think samsungs bad...wait till you get an HTC lol they are even worse
Every manufacturer is bad with source unless its a nexus...if its not a mexus then they do the bare minimum
Anyways...I have no actually answer for your question...just felt like letting you know they are all bad...
Sent from my HTC Holiday using Tapatalk 2
mg2195 said:
You think samsungs bad...wait till you get an HTC lol they are even worse
Every manufacturer is bad with source unless its a nexus...if its not a mexus then they do the bare minimum
Anyways...I have no actually answer for your question...just felt like letting you know they are all bad...
Sent from my HTC Holiday using Tapatalk 2
Click to expand...
Click to collapse
I know! Afterlife development is what Android has going for it over iOS (IMHO). I guess Moto, Samsung, HTC, etc - just like every freaking retailer in America - really want everyone to buy into iOS? Had I opted for an iPhone 3GS, I'd still be eligible to upgrade to iOS 6. & I would have been able to copy and paste a tracking number the day I booted up my phone! LOL! Now, do I want a walled garden to enclose all my other walled gardens? Or do I want a walled garden with a gate?
Whizzpopper said:
I've been following, off and on, the struggle Entropy and other devs have been having with Samsung to ensure clearer documentation and accurate source files. It seems like Samsung may have opened up a little with their Insignal repositories. What I'd like to know - and haven't been able to discover - is if Samsung has already (or intends to) release the same for Exynos 3 (hummingbird). The source up on their regular opensource site is clearly not complete. Also, have Samsung opened up enough that Cyanogenmod will continue developing for Samsung devices?
I have a few reasons for asking. One is that I have another year on my contract with the Infuse and feel pretty annoyed that Gingerbread is as high as they'll go (my fault, but before this, I really had no concept of how primitive Gingerbread is). I'm happy that development has lived on here on xda, but I'd like to have a properly working camera. I don't think that's going to happen until Samsung open up.
The other reason is that, having read all Entropy has had to say on the matter, I won't buy another Samsung phone for me or family members until I know development can continue beyond AT&T and Samsung's arbitrary schedules.
Click to expand...
Click to collapse
Have you looked at the JB Roms for the infuse? I'm loving The ParanoidAndroid port Scott's done.. I've also put the AOCP rom on there as well as an AOKP rom but I always go back to PA..
as soon as the infuse was in my hands I installed a JB Rom I never had to deal w/ Gingerbread or Froyo or even ICS.. I did the same for my captivate and my 2 Skyrocket 2's as well..
_oxygen_ said:
Have you looked at the JB Roms for the infuse? I'm loving The ParanoidAndroid port Scott's done.. I've also put the AOCP rom on there as well as an AOKP rom but I always go back to PA..
as soon as the infuse was in my hands I installed a JB Rom I never had to deal w/ Gingerbread or Froyo or even ICS.. I did the same for my captivate and my 2 Skyrocket 2's as well..
Click to expand...
Click to collapse
I'm not sure why you ask. Yes, is the answer, but I don't know what that has to do with the topic. The camera doesn't work properly on JB and I don't think it will until either a) a developer with particular expertise in digital recording has time to spare or b) Samsung releases the source. I've tinkered enough with the source to know more or less what the main problem is, but where it is and how to solve it is well beyond me. There are other little problems too, but they may not be important in the long run.
I often wondered why Entropy called the Infuse, the Confuse. When I started rifling though the source, I found out: the Infuse is a Frankenphone.
I wasn't thinking of the video recording functionality w/ regards to the camera. Apart from that, it all works quite well for me. I haven't tried the 4.2 AOSP based ROMs so I don't know about the video recording functionality of that. I highly doubt Samsung is interested in furthering the development of the infuse as its getting pretty old.
_oxygen_
Sent from my SGH-I897 using xda app-developers app