Related
Firstly, I'd like to make the standard "I love our devs" statement. When I first purchased my Vibrant, I loved the hardware, and absolutely hated the software.
Freezing, glitching music, non functional GPS, you name it; a myriad of issues. Then I flashed my first ROM, and fell in love with it. You guys turn a very mediocre phone, into arguably one of the best phones available, including what's been released after.
This post is more out of curiosity than anything. I currently have Darkies 2.2.1 ROM and it runs like a dream-
How far are we, realistically speaking, to a stable Gingerbread ROM? I follow the current Gingerbread alpha rom threads, and it seems like they aren't making a whole lot of progress. I assume this is because of roadblocks? What is keeping us from moving forward with a Gingerbread rom? Do we need the source released?
Thanks guys.
CM7 beta is now out for the Vibrant. However, that's not what's got me the most excited. The i9000 has recently got a gingerbread ROM leaked from Samsung. This should mean we should see the forums flooded with gingerbread ROMs in the coming days/weeks as soon as somebody can port the kernel over to the vibrant.
i'd say the cm7 is dd-able. no gps is the only real problem i've had, which isn't enough for me to go back to nongingerbread. the external sd doesn't mount, either, but i never used it anyway.... otherwise, sound works, haven't had a problem with data/calls/reboots, camera and video recording work, etc.
funeralthirst said:
i'd say the cm7 is dd-able. no gps is the only real problem i've had, which isn't enough for me to go back to nongingerbread. the external sd doesn't mount, either, but i never used it anyway.... otherwise, sound works, haven't had a problem with data/calls/reboots, camera and video recording work, etc.
Click to expand...
Click to collapse
I would go out on a limb here and say that this is pretty close...
It might be a while before it gets to be a care free DD. The whitehawx and CM iterations both work in theory but they are still pretty raw in terms of total useability.
I say give it a while and we'll see more true GB progress.
Sent from my SGH-T959 using XDA App
Like I said, the leaked i9000 2.3.2 ROM should have a great effect on the 2.3 GB ROM dev community for the Vibrant.
CM7 is my dd right now, and it actually seems more stable than any other rom I've tried (I had reboots and lockups with bionix when using gps). The tower-based location isn't as accurate as real gps, but is good enough for pulling up directions most of the time. Gps is also supposedly fixed on github, but I think they were saying to hold off on flashing anything from github until they get some issue with the new touchkey driver sorted out.
What are the benefits of GB over Froyo as a daily driver at this point. From what I've read, there's not likely to be any significant performance increase and most of the new features are minor. Other than the cosmetic differences, what's so bad about being stuck on Froyo?
Shrivel said:
What are the benefits of GB over Froyo as a daily driver at this point. From what I've read, there's not likely to be any significant performance increase and most of the new features are minor. Other than the cosmetic differences, what's so bad about being stuck on Froyo?
Click to expand...
Click to collapse
nothing is bad about being stuck on froyo. i thought people making a big deal about the lock screen animation were being ridiculous, but it really is damn cool. it's just the little things like that, just like it's the little things that make you like a certain rom over another.
that, and 'why not'? they keep making new versions, and we'll keep finding a way to get it on our phones.
i went on i9000 forum and flashed insanity 7.1 gingerbread and it ran fine ...makes me thin we are soooo colse to get it on vibrant hmmmm i say two more weeks ......thats what methink.
bartek25 said:
i went on i9000 forum and flashed insanity 7.1 gingerbread and it ran fine ...makes me thin we are soooo colse to get it on vibrant hmmmm i say two more weeks ......thats what methink.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=976318
pretty much there
Alright everyone, time for the important question that no one wants to ask.
Since we have devs already working on ICS, we all know our hardware is a little bit dated which means it's likely we will have to remove some of the cooler features in the roms so, what do you think we might have to sacrifice to get a taste of that nice green-blue goodness?
ICS will run fine on our phone. AOSP does not take the latest hardware to run. It just has to be optimized to run on our phones. Google says our phones are to old cause they do not want to take the time to make it work on older phones.
Manufacturer bloat will have to be stripped or slimmed out an ICS/sense port will either lag horribly or sense will have to be seriously stripped or be ported back to an older less resource hungry version like 1.0/2.1 as all new ICS/sense roms will have 3.5+ which is already laggy on our hardware with out heavy mods. So don't expect to be running a full blown Ics/sense 3.5 port from a newer phone like the edge or radar. If and this is a BIG IF we are graced with one last official update on the OG don't expect sense to be upgraded they didn't upgrade it for gb, and if it does get a sense upgrade it won't be above 2.1 and it may have some of the major features removed or slimmed, such as the social integration may be downgraded and not have as many features available as it does now. Think of it like a race car if its big and heavy like a muscle car its gotta have a lot of HP to go fast if its small and heavy its gotta be stripped of all non essentials to go fast like taking all the seats but the drivers seat out and replacing as much metal with plastics and composites as possible.
Sent from my -EViLizED-EVO-
dabbill said:
ICS will run fine on our phone. AOSP does not take the latest hardware to run. It just has to be optimized to run on our phones. Google says our phones are to old cause they do not want to take the time to make it work on older phones.
Click to expand...
Click to collapse
I still have my G1 (wife is using it), and I use an EVO 4G. Any chance ICS will run on the G1?
dabbill said:
ICS will run fine on our phone. AOSP does not take the latest hardware to run. It just has to be optimized to run on our phones. Google says our phones are to old cause they do not want to take the time to make it work on older phones.
Click to expand...
Click to collapse
from what i understand, ICS heavily utilizes the GPU in regards to rendering images/3D, and our GPU is going to bottleneck ICS to the point where it is laggy. someone correct me if i'm wrong.
I loaded the SDK dumb ICS rom on the evo4g going through the menus and swiping the screens ran just fine. So i would have to say once all the drivers get loaded and the rom tweaked it will be the same as running GB.
dabbill said:
ICS will run fine on our phone. AOSP does not take the latest hardware to run. It just has to be optimized to run on our phones. Google says our phones are to old cause they do not want to take the time to make it work on older phones.
Click to expand...
Click to collapse
Google has nothing to do with releasing OS updates for our phones. That is 100% up the the phone manufacturers, so don't blame google.
-EViL-KoNCEPTz- said:
Manufacturer bloat will have to be stripped or slimmed out an ICS/sense port will either lag horribly or sense will have to be seriously stripped or be ported back to an older less resource hungry version like 1.0/2.1 as all new ICS/sense roms will have 3.5+ which is already laggy on our hardware with out heavy mods. So don't expect to be running a full blown Ics/sense 3.5 port from a newer phone like the edge or radar. If and this is a BIG IF we are graced with one last official update on the OG don't expect sense to be upgraded they didn't upgrade it for gb, and if it does get a sense upgrade it won't be above 2.1 and it may have some of the major features removed or slimmed, such as the social integration may be downgraded and not have as many features available as it does now. Think of it like a race car if its big and heavy like a muscle car its gotta have a lot of HP to go fast if its small and heavy its gotta be stripped of all non essentials to go fast like taking all the seats but the drivers seat out and replacing as much metal with plastics and composites as possible.
Sent from my -EViLizED-EVO-
Click to expand...
Click to collapse
The evo design is only a single core running 1.2, I would say there's a fair chance we can get a pretty good sense port from it.
nothing will need to be stripped. ASOP roms are tiny compared to Sense. Google already said that if your phone can run GB, It can run ICS. The only reason we won't get a official update is because HTC has moved on to newer phones and supporting us makes no money.
cnstarz said:
from what i understand, ICS heavily utilizes the GPU in regards to rendering images/3D, and our GPU is going to bottleneck ICS to the point where it is laggy. someone correct me if i'm wrong.
Click to expand...
Click to collapse
Here to happily correct you.
Actually, rather than ICS "heavily utilizing the GPU to bottleneck the EVO", it's the reverse. Android 1.0 - 2.3.7 all currently use software acceleration. This means the CPU has to pull double duty: It has to run the OS in the background, and render everything you see in the OS.
(Games and other applications, of course, use the GPU if designed to do so.)
The departure now is that ICS uses the GPU to leverage all of the UI, taking that strain off of the GPU. The result should actually be that the EVO runs better than ever, with a slicker, smoother UI to result, and better performance from the OS in general.
Also, all of that business about having to strip-out components for the EVO is nonsense. The EVO has a 1GB ROM; it has more than enough room for ICS in it's entirety, and all the horsepower necessary to make it run really well.
It seems like in theory the og evolution should get a little better battery life too since the workload will be split instead of all dependant on the CPU. The clockspeeds should have less full throttle time than previous versions right?
Sent from my PC36100 using xda premium
dills2214 said:
Google has nothing to do with releasing OS updates for our phones. That is 100% up the the phone manufacturers, so don't blame google.
Click to expand...
Click to collapse
I wasnt blaming google. I just ment google is not going to take the time and optimize AOSP for every phone out there. Its up to phone manufacture and other devs to do that.
dills2214 said:
Google has nothing to do with releasing OS updates for our phones. That is 100% up the the phone manufacturers, so don't blame google.
Click to expand...
Click to collapse
Not true for Nexus devices, and I think dabbill was referring to their statement about the Nexus One being too old for an ICS update.
If Wikipedia is accurate, the N1 only has 512MB of storage, while the Evo has 1GB of storage. On the Evo at least that 1GB is split between system, data, and cache partitions. If the N1's 512MB number is accurate and similarly is a total amount for all three partitions, than their statement would make sense for the N1. Our 1GB total should be enough. CM7 only uses 40% of the system partition on the Evo.
When I bought the Xoom last year I installed the latest Tiamat rom (now Nandroid' at 2.2.2) and it ran really well, although the limitations of the hardware occasionally reared it's ugly head; I guess tablets can't come close to laptops at the mo now matter what mega ROM is installed.
I'm running Miui on an HTC DHD and it is an AWESOME Rom and nothing at all like vanilla Honeycomb, just on another level. I was hoping that when ICS came out there would be something similar for the Xoom. So I waited like a hungry dog for ICS to land and a stable(ish) build to come out and have now tried both EOS and Kang CM9 and both run well but how are they so vastly different from Vanilla ICS? I do really appreciate all the effort that's gone into getting these roms to us but if they're the same (or similar) in terms of looks, performance, usability etc what's the advantage with ICS over Honeycomb apart from a pretty small performance upgrade? Sure ICS does look a little different but only a bit, nothing drastic.....so can someone who knows more about these things tell me, what's the biggy with ICS?
Perhaps I'm expecting too much here but it seems a lot like the forums just got crazy giddy waiting for ICS to come out so then whipped themselves up into a lather (for maybe no valid reason) and that now the insanely mad push to get ICS working efficiently across the Android universe is more of a case of why man went to the Moon?.....because it's there, not because we needed to.
I think your sort of neglecting the big picture. Your looking at it from the perspective of someone who is already running Honeycomb on your Xoom. I think if you were running a HP Touchpad (for example) with Gingerbread you would be warming up a lot closer to ICS. Not every tablet has honeycomb on it so lets face it you are spoiled by the Xooms OS.
Oh and ICS has some nice features for example I can remove app from the recent app list by dragging it out of the list.
HC was a beta; ICS is a stable release
GrandMasterPlank said:
what's the advantage with ICS over Honeycomb apart from a pretty small performance upgrade?
Click to expand...
Click to collapse
Its not small by any means. The performance increase is night and day.
A lot of the hype in general for ICS is for previous gingerbread users. Its a huge change for them in terms of UI. For honeycomb users, ICS is more like finally getting a stable release of the OS; honeycomb was IMO a beta test. Limited to tablets (which was a pretty small portion of Android users) and very buggy with quite a bit of work that needed to be done. Now we have a full release with some nice new features, proper performance and support for tablets and phones.
As for the custom roms, I'm pretty certain stock ICS Xooms don't have face unlock. The EOS settings are nice as well as built-in overclocking. I'm sure somewhere down the line the ad-hoc support will be sorted out and I remember reading a post by one of the EOS devs that they haven't even begun to work on performance optimization so this ROM could get even faster/smoother/better on battery.
The biggest reason to move is that ICS actually takes advantage of your second (or more) cores more efficiently than HC 3.x ever did.
Gingerbread for the most part, will not utilize a 2nd core at all even if you had one. That 2nd core would sit there idle. AFAIK.
So, ICS on Xoom is a huge boost in performance. You can see this as you use the device. Lag is completely removed from almost all tasks. With EOS Wingray/Stingray, you can even over clock to get even more performance out of the old Tegra 2.
Stability, smoothness in the UI, and overall polish. The browser is also WORLDS better.
+1 on previous comments RE: smoothness, performance. I was able to start playing with official ICS a couple of Thursdays ago when it rolled onto my Xoom as I was introducing myself to my nursing students.
AFAIK, and have tested, read/write to "external" SD card issue is partially fixed from the standpoint of apps directing r/w to the actual name Xoom gives the ext SD... with HC, the only way I could get it working was by using the File Manager for Honeycomb (can't recall the dev's name off the top of my head). Now, as more devs are updating their apps for ICS tablet compatibility, some are making the change and some aren't.
~ BereanPK
anyone knows when the 3g version in europe will get ics?
Well for one thing we won't really see all the benefits of ICS for awhile.
Remember ICS is the attempt to standardize App compatability between Phone and Tablets.
Until more phones get ICS we won't truly see the entire benefit of it.
And it's still relatively new and not fully fleshed out by the community yet.
They are still struggling with getting it up and running on devices (like ours which Team EOS is doing a great job with!)
HC was specifically written for Dual Proc units.
ICS' main goal is to support ANY number of internal procs which is a boon to Single proc devices and future multicore devices.
It also allows consistency of OS so that cheaper android tablets can be made. I can see single proc bargain Tablets on the way soon now that ICS doesn't care how many cores you have!
And the fact that it runs on phones and tablets just means easier coding for App developers because they can write one set of code to work on EVERY android device and have better compatability.
ICS was a very smart move by Google and provided the Manufacturers don't mess it up with bloatware creating problems we are all better off having it!
I don't think ICS has even scratched the surface of what it can do!
HC may be a bit more mature and stable but thats only because it's been in development longer...ICS will get there and more!
So, now that we've had JB on our KF for about a month, I'm wondering why Google made 4.1 Jelly Bean, instead of just updating ICS to v4.1. Don't get me wrong, JB is fine but aside from Google Now, I don't see any real benefits of JB over ICS. I guess it's nice that on some JB roms, you can have either a tablet or phone ui but I just have the rom I'm using on tablet and haven't had any need to switch to phone. I'm on twa_priv's CM10 SGT7 rom and it runs great but so did his CM9 rom.
I guess it's no big deal but you would think that to go from ICS to JB, the corresponding version number would be Android 5.x. but IMO, I don't think this "update" warranted going up a full version number, or from ICS to JB. In my everyday use, I really don't see a difference between the two. Google talks about Project Butter, well ICS ran damn smooth for me, so I'm really not noticing the butter.
To sum it up, while there's nothing really wrong with JB, for me, it's pretty underwhelming to be considered a major revision update. Any and all opinions are welcome, especially those pointing out specific JB features/benefits that I'm not seeing.
Mike T
There's enough changes under the hood for it to be a newer version.
veeman said:
There's enough changes under the hood for it to be a newer version.
Click to expand...
Click to collapse
That's a very general statement. What are some of these changes that may make a difference to allow it to be a whole new version, as opposed to an updated version of ICS?
Mike T
Because it sounds better from a marketing stand point?
I see your point that to a front end user not an whole lot of differences. But I think they did a lot of optimization and performance enhancements that the developers considered to be worthy of an upgraded OS rather than a patch to the old version.
Sent from my CM10 KF w/ Tapatalk
sweeds said:
Because it sounds better from a marketing stand point?
I see your point that to a front end user not an whole lot of differences. But I think they did a lot of optimization and performance enhancements that the developers considered to be worthy of an upgraded OS rather than a patch to the old version.
Sent from my CM10 KF w/ Tapatalk
Click to expand...
Click to collapse
Very good point re: Marketing. I would think Google introducing the Nexus 7 with something "different" in JB makes sense. For me, after playing around with it and looking through the file structures, it feels like an updated ICS with a nicer notifications interface and a cool new killer app in Google Now. IMO, there's very little difference both visually and performance-wise from ICS. Maybe rightfully so, because ICS is a very good OS on its own.
I'm all for progression and I think that Google Now has tons of potential. GN is a big selling point for me with JB, I just hope that Hashcode, or some other programming genius finds a way to get a mic working, so we can take advantage of its capabilities. Of course, regardless, I'll still want to be on the cutting edge, using the latest and greatest OS...unless it's a total dud!:laugh:
Mike T
I think that between Project Butter, new notifications and Google Now that there's enough to call it a new version ie JB, but it's just not big a change according to google for a major version change, just a minor one.
Just imagine what's going to be needed for the next major version change
Hello, I am a user of XSP since August 2013, I have been using this device as my only device since then, and I can tell that I tried every ROM that came out for this device, maybe I can share a little bit of my experience if you let me ..
I am not a developer or anything, but I can help with something at least
Since we got our device we couldn't stand for one particular ROM, we always had to keep changing ROMs so we can get "better" performance, and frankly that wasn't great for most of us, I mean who would want to see his device not in a good performance where we can see lots of lower-price-devices like Xperia M (that has nearly the same support from SONY) get a better performance, and for the word "performance" here I mean RAM management, touch response, the use of those amazing LEDs... etc and didn't mean the performance of heavy games..
we had 4.1.2 and XSP was one of the best 4.1.2 devices out there, then we got the 4.3 and we struggled to get that without any problems in the latest 205 and 207 versions, right? and here I am talking about the flickering issue of the screen, then again we had that poor RAM.. some devs made great CM11 LBL ROMs that were amazing knowing that the kernel is 4.3 and it has some limitations, they made that "High Touch Sensitivity" option, even though it did turn off every now and then but it was great, then there was this HUGE step in XSP life, which was the official support of CM and other big names .. we had an official CM11, it wasn't that great since its was never built on .207 sources (always was on .201) that means it had flickering screen problem and never had the Glove Mode high touch option, so it was petty much unusable.. the CM12.1 was another huge move, it was built on 207 and had that option....... BUT.... it is lollipop! don't you guys think that it is a little too much for XSP? I know it can be buttery smooth and great, especially with latest builds of ALL ROMs from our amazing devs, but as soon as you install facebook and some big apps on that, you go back to the bad 4.3 again, sorry for talking so much, what I am trying to say is, can't we have a UBL CM11 (4.4.4) with 207 kernel sources AND the latest glove mode implementation (of the 5.1.1 in all ROMs) ? think about it, amazing performance, no flickering, no bad RAM management, no horrible touch sensitivity.. pretty much all we need in a smartphone, isn't it? yes it's not Lollipop, yes it's not Marshmallow, but it's an idea, like any other ROM we have, I guess it would be great to have that, and a it's worth a try, I guess
thank you all for reading this (or some of it ) I was just trying to give you my idea.. and I ALWAYS appreciate all the devs work, you gave XSP a shot that SHE can never imagine (that's right, XSP is a she and I am in love with her )
Im thinking the same thing I think devs shouldnt gave all their all time to creating new roms. We have a lot of Lollipop roms, but nothing different between them.
I think, devs should improve 4.3 experience,(or 4.4 you say).
And i think, they should spend much more time to improve the SP's software limitatioms or etc like Gamma/Display Settings, 720p 60 fps camera or something like that. Because our SP can handle it but nobody creates it or works for it. Im sorry about this..
Or the SP's most important thing, The LED's We have only Discolight app (sagar29) for this beautiful LEDs, i think they can improve and create different things about LEDs and give them a life again.
But i appreciate all developers, Thank u guys, you gave a life this phone...
Same line of thinking here! When I was with an Xperia PLAY at the time we heard we didn't was going to have ICS update with is can be equal to no KitKat for the SP, so then the devs work hard and brought ICS, JB and even a working KitKat for that amazing device, but come a time that all we wanted was a powerful and optimized OS and mostly of the devs focus on bring a powerful fricken as hell optimized GB version for the XPLAY with almost 320mb of free ram on a device with less then 512 of total amount of ram, I must say I kind miss this on the SP foruns, as you said, yes its amazing that we have even in alpha state a 6.0 ROM. But I want a fully lag free ROM, ram free with better ram management that I can use for months and not changing from one sluggish ROM to other whitin a week. A thing that always get me is that on the XPLAY we have a 720p record on most kernels (Lupus Kernel, DoomKernel etc.) and for better performance (say to get more free ram and better performance) the devs created a 480p version of the kernel and was fully functional, if someone with more knowledge can answer this for me, That would be possible on the XSP?