As the name implies, would like to know if the banding issue has been addressed in the OMAP4430 variant of the SGS2.
Since the entire circuitry has essentially been replaced, i would assume so.
Thinking of swapping my i9100 for an i9100g, since i heard it has better acoustics, less heating issues, longer battery life and pretty much the same real time performance ( i couldnt care less about synthetic benchmarks).
So as long as the interface remains lag-free just like the original, and banding issue fixed, im getting the i9100g.
Maybe you considering this as an issue (like myself) but for Google is not.
I can't answer your question because i dont have i9100g but im afraid it has no difference. I was hoping ICS will correct the whole situation but as far as i see from the videos has been posted around, is the same sh1t. We have to live with less than 24bit
What you heard was probably placebo. Longer battery life? Really? Also don't why you would switch to a phone with such a limited development community.
I have it and it has no color banding, at all. But DO NOT swap your I9100 for a G, as it has way more community support than the G version.
Longer battery life? Really?
Click to expand...
Click to collapse
It has longer battery and less heating, thanks to processor being capped at 1008 Mhz.
Related
Hey peeps,
Currently I'm in the possession of an HTC Sensation XE, but thinking about making the switch to the SGSII. However, some questions are still there and I was hoping that the helpful community here could help me answer some of these.
How is the Earphone quality? Anyone tried it with some decent pair of headphones yet and is able to tell me their experience?
Could someone with a "stock" SGSII (International model preferably) tell me about the gaming performance on the SGSII? I'm talking about games such as Dungeon Defenders, Wind-Up Knight and PSX/N64 Emulation. If entirely possible with a recorded video.
Same request above for a person who flashed a ROM
How does the SGSII perform with Tegra 2 games through Chain-something?
How is the battery life for both the "stock" SGSII and the Lite-ning ROM?
Could a person with a "stock" SGSII show me their benchmark scores after a reboot of the phone?
Same for a person running the Lite-ning ROM
The standard hardware acceleration which is present on the SGSII. Is the hardware acceleration only being applies to browsing and the UI? or also to applications and games?
In addition to the above questions, how will ICS affect the hardware acceleration on the SGSII? Will it be disabled in favor of the ICS style hardware acceleration or will they live together happily ever after?
My apologies for the kind of weird requests. But I do sincerely hope you guys can help me decide whether to get this device or stick with the Sensation XE.
Regards,
Vex
-=Vex=- said:
Hey peeps,
Currently I'm in the possession of an HTC Sensation XE, but thinking about making the switch to the SGSII. However, some questions are still there and I was hoping that the helpful community here could help me answer some of these.
How is the Earphone quality? Anyone tried it with some decent pair of headphones yet and is able to tell me their experience?
Could someone with a "stock" SGSII (International model preferably) tell me about the gaming performance on the SGSII? I'm talking about games such as Dungeon Defenders, Wind-Up Knight and PSX/N64 Emulation. If entirely possible with a recorded video.
Same request above for a person who flashed a ROM
How does the SGSII perform with Tegra 2 games through Chain-something?
How is the battery life for both the "stock" SGSII and the Lite-ning ROM?
Could a person with a "stock" SGSII show me their benchmark scores after a reboot of the phone?
Same for a person running the Lite-ning ROM
The standard hardware acceleration which is present on the SGSII. Is the hardware acceleration only being applies to browsing and the UI? or also to applications and games?
In addition to the above questions, how will ICS affect the hardware acceleration on the SGSII? Will it be disabled in favor of the ICS style hardware acceleration or will they live together happily ever after?
My apologies for the kind of weird requests. But I do sincerely hope you guys can help me decide whether to get this device or stick with the Sensation XE.
Regards,
Vex
Click to expand...
Click to collapse
Oh man, many questions and I can only give a few answers:
1. Earphone quality is IMO good. As I do not have a Sensation XE, I can not compare it directly. There are some tests (Google search is your friend ;-) which might give a more experience-based opinion.
2. + 3. + 4. Can't say much about gaming performance, as I am not a gambler.
5. I am running a stock ROM (XWKJ1, Android 2.3.5) and battery life is OK for me. With permanent wifi on, no bluetooth, no GPS, permanent Skype and Google Talk, some email, often internet news and looking into xda-developers forum, a nightly charged battery has about 50% in the evening. So, with less usage my phone could work for about two days.
There are many custom ROMs, which are specialized for optimizing battery life.
You have to set your priority between battery life and performance.
6. Benchmark scores ... which benchmark?
On Quadrant Standard, I usually have 3000-4000 with the stock ROMs.
My actual score is about 3400 as I am running CF-Root kernel XWKI8, which is not based on the real stock kernel of my ROM (XWKJ1).
But to have more than 4000 points in Quadrant, I think you have to use a custom ROM specialized for performance or at least overclock the CPU.
7. No custom ROM.
8. Good question. I think that hardware acceleration is in general available for any app too ... but ... if any app will use it, I really don't know. Each manufacturer ans even each phone has a different hardware and therefore need a different hardware acceleration, so that would be a very hard job for a developer to get familiar with all available hardware-specific APIs. At least the app of the manufacturer itself (=> Samsung) should use hardware acceleration.
But I am not sure about even this.
9. Hmm ... complicated question. I heard that the SGS2 or better the hardware of the SGS2 is 100% compatible with IceCreamSandwich. And that's it. I have got no more infos about this topic.
I will think about such issues just before getting ready for flashing ICS onto my SGS2. Hoping that there will be more and official statements up to this moment.
Regardless of the fact that you aren't able to answer all the questions, I really do appreciate your reply to these matters.
2 Days on battery, that's quite amazing seeing as my XE only lasted for about 8-10 hours on normal use with Wifi on.
Quadrant scores are also quite impressive, even at stock.
I really do hope that someone can clarify more on the amtter of ICS' hardware acceleration. I'm eager to find out how it differs from the acceleration currently present on the SGSII
bump
10chars
I'm on Androidmeda 2.5 with Siyahkernel 2.0. I can typically get about 4.5 to 5 hours of screen time.
It's my theory that the basic ROM itself shouldn't affect the battery life. It's the different init.d scripts of optimization and the kernel that will have *some* effect given that you don't OC/UC or OV/UV. Mostly it should be what apps you run in the background like facebook, skype, etc.
Also I find that having wifi and data always on doesn't affect my battery life too much if I disable background sync.
Thanks for that reply.
4-5 hours does seem a little meager though. Then again my Sensation lasted for about as long as that, if not less.
Eager to hear more opinions!
Basically, i got this phone(GS2 i9100M) a week ago and found way too many problems that i cannot fix. So, why exactly does so many people like about this phone compared to other variant, e.g. GS2 T989 with snapdragon processor? I mean, my brother has the T989 and i also had it before too until i sold it to get this. It seems like i've been experiencing a lot of problem from this phone that does not really occur on the T989. The default music player is faulty which causes auto reboot, and the phone constantly heats up; even when viewing photos from the gallery! What attracted me to get this phone was people's opinion about the CPU and GPU also the gorilla glass, but i dont really notice a big differences in speed between the two phones. The T989 also doesn't heat up this much or this often. Feel free to share your experience people, and would appreciate if someone can offer me some advices on how to fix the heating up issues.
First, its better to talk n read at 9100 forum section but since im a 9100 user, ill share it here
Yes, on day one i got my 9100, it gets really warm even when not charging and got a lot worse when on charge. Its mostly the media scanning process which seems unstoppable on the earlier build when the SGS2 was released
I first noticed that its solved when using XXKG3 firmware and above. And also, undervolting to around 50mv reduces the heat too. A normal 9100 is capable of undervolting up to 175-200mv but it depends on phones are some silicones are made better and its not a constant result. What samsung made is setting the voltage at all the same safe level to avoid reboots. U have the option to undervolt it to reduce heat or even underclock to 1Ghz since 1.2ghz is quite overpowered and u want to conserve the battery and make it last longer.
Try Siyah kernel and learn to tweak using voltage controller and extweaks. There r guides given in SGS2 section here on XDA and it is well compiled.
Cheers
Sent from my GT-I9100 using xda premium
bershote Legiflature;
Thanks for your reply. I've posted in the wrong section by mistake. Someday I'd consider rooting the phone, but at the moment I don't want to take the risk because I'm still kind of new to smartphones and don't know much about it. What's your opinions on ICS? Do you think ICS OS release will solve most of these problems?
Hello I own the Samsung Vibrant for two years now and even though I was a bit reluctant to overclock the phone at first as new phones were coming out in the market and its (Vibrant's) performance deficit was becoming all the more significant (in comparison to newer phones) I "succumbed to the temptation". At first by a little margin (no more than 20% overclock) but eventually -as I was seeing my phone to be capable for it- for even greater ones. There was a time that I was using my phone at 50% over-the-stock clocks.... those were the days
Eventually -it seemed- as if it somehow starting becoming less and less capable holding the clocks so I started lowering my clock thresholds eventually killing the overclock altogether. Mind you the grand total of the time(s) that I had my phone overclocked (up until then) was not that great...
But then ICS came out with all its fancy tools and the "temptation" overcame me again and as if from a miracle I was able to maintain 50% overclocks like the good ole days (1512Mhz to be exact). To be sure -that time around- that that is a stable clock I devised a slew of different test from extensive software decoding, to 3D and CPU rendering. My phone was rock solid. To address the battery issue I bought an extended battery and all was well in "Vibrant-Ville"...
To my dismay though even though my phone seemed rock solid I seemingly starting losing my overclocking capacity (once again) as I migrated into Jelly Bean, so I said to myself "oh no, no, I'm not going through this again, I'd choose a moderate overclock and I'll leave at that". So I disabled Live-OC, custom voltages, hell even deleted NSTools and used the standard 1.2GHz setting, my battery was better, my phone was rock solid once again and thanks to jelly bean my phone was still fast enough...
Two days ago -though- the ghosts of the past reared their ugly head once again, out of the blue my phone lost its stability. Anytime I was trying to do anything remotely complex and it would reboot (BTW I'm using Helly-Bean right now, using the "Smooth" setting, Smartass governor @ 1.2ghz, pretty standard stuff).
I love this phone but I feel it's nearing its death-bed, what's your opinion guys?
I'll prolly remove the oc altogether but I fear it won't be enough, I fear that instability would start encroaching the 1ghz setting as well one of the days and then it would be game over. I want to avoid this fate at all costs, so anything you could recommend I would try, even changing my rom.
Also to those who used overclocks in the long term what was your own experience?
Thanks for your attention
No response(s)?
Sorry for the bump but I take it none of you guys ever have/had any of the problems I'm describing. Hmm, that means that I was unlucky with my piece of hardware it seems... pity :/
More than likely an aging chip is the case. Personally my phone runs smooth at 1GHz, so I don't see the need to unnecessarily overwork the CPU. After reading your original post, one line stuck out to me in particular. You mentioned that you ran the CPU at 150% for a time, and to me that sets off a red flag. Setting the CPU at 1.5GHz is risky and can cause some major wear on the CPU. Not to say I've never overclocked that high, but I usually only set it that high when playing a high graphics game. Even then, 1.5GHz is not recommended if you wish to use your device long-term. Even 1.4GHz is considerably pushing it. Although our devices can handle it, eventually, they're going to tire out. Now some phones may be able to last longer than others, it depends on the amount of iron in the sand used to make the silicon processors or other minuscule things could play a role. Essentially, it's random. No two chips will be exactly identical nor run exactly the same. So in your case, that may be the case. Perhaps your device really is nearing the its end. Considering that your phone was made to last only a few years at stock speeds, you should still be pleased with how long it's lasted. However, it is understandable if you're upset with this. The only thing I can suggest is to not overclock anymore and to try and keep its temperature low. Perhaps try undervolting? But if you want your phone to last, don't overclock (if your phone's processor is already starting to fail at 1.2GHz, when it used to run rock solid at 1.4 or 1.5GHz, then you definitely need to stop overclocking entirely). More than likely you won't hear other Vibrant users discuss similar problems because they've already moved on to new devices, before the long-term effects of high overclocking began to take its toll. But if you do a little research, you'll find other users on other devices having similar problems to what you are having.
Wish you the best in your efforts, and hopefully you'll get a year or two more out of the device... Hopefully someone will come forward with a better recommendation/solution to your problem. Since I pretty much stated what you probably already knew.
I'm not for overclocking, nor have i overclocked my vibrant.
With that being said, i have never had any performance issues, and I'm having difficulty recalling any issues with stability either..
I hope you treat your new phone with more respect..
I'm sure it will live you much longer for it.
Sent from my amazingly stable SGH-T959 using SlimICS
Hi.
I am totally new to the Android phone tweaking phenomenon. Been reading and testing many of the tips, tricks and such on the forum here. I must say, I was about to ditch the trusty Atrix 4g when I came upon this forum. I can't thank XDA enough for being the informative and authoritative website that it is.
On another forum I saw someone ask if they should upgrade to a SG3 or unlock/root their Atrix 4g. I though about it a bit. My "answer" was simple: I am a cheapskate. Forking out $200 for a new SG3 (my phone of choice right now to be honest) is a bit rough on my pocket. Unlocking/rooting is for free. Try unlocking/rooting "responsibly" first. If it doesn't work out to my satisfaction, then upgrade the phone. At least you make sure you are squeezing the max out of your Atrix 4G, right?
I unlocked... rooted... and I could not be happier. Only problem now is that I want more! I OC PC's for a hobby so squeezing more is second nature to me right now. Cell phones are way different to PC's though. Quickly saw you can't water cool then effectively and retain its mobile nature. Now my phone has a new life in it that I think could be improved even more. Therefore, I pose two simple questions here now:
1) Extended battery... worth the investment or not? I rooted to MROM and find I have excellent battery life in comparison to before but I wouldn't mind extra life via the battery itself. Investment would be around $20 tops for a 2800 mAh battery. That's about 33% more mAh if that's the correct way of looking at this...
2) If I were to get the extended battery, I was thinking of upgrading my kernel to the Faux123 1.3 ghz version. Would I "really" notice the difference in terms of performance? (am presently running the MROM ver. 43 SV kernel which is 1.0 ghz - "sv" means software voltage "tweaked" for better battery life if I am not mistaken)
Thoughts?
Signed,
Uncle Kah
1.) If you really want the extended battery it is only worth it if you can handle the extra bulk. Buy only what feels comfortable to you. (And that's the only thing that you should be considering on this subject)
2.) Depends a lot on what you're doing. The things that are already running fairly fast and feel snappy probably won't feel much different, but you will see an improvement on things that are/feel a little sluggish at times.
Right now we're on a turning point as far as development goes, since the new leak has been released there will be a slew of new builds coming our way very soon (I am hoping within the next few days), so sit tight and watch (maybe help test too?) closely, because even the current incomplete ICS/JB builds are, in my opinion, superior to any other Gingerbread build.
littleemp said:
1.) If you really want the extended battery it is only worth it if you can handle the extra bulk. Buy only what feels comfortable to you. (And that's the only thing that you should be considering on this subject)
2.) Depends a lot on what you're doing. The things that are already running fairly fast and feel snappy probably won't feel much different, but you will see an improvement on things that are/feel a little sluggish at times.
Right now we're on a turning point as far as development goes, since the new leak has been released there will be a slew of new builds coming our way very soon (I am hoping within the next few days), so sit tight and watch (maybe help test too?) closely, because even the current incomplete ICS/JB builds are, in my opinion, superior to any other Gingerbread build.
Click to expand...
Click to collapse
I agree on the battery thing being more a matter of bulk. That's why I was looking at the 2800 mAh battery instead of the 3500+ mAh. I believe the bulk should be less. I have big hands anyways so it shouldn't be much of an issue BUT, if I need to put the phone on a pocket fort example, that might be an issue.
I see your point on the sluggishness of apps and such. I really can't complain that much of anything being slow or stuttery. Netflix works just fine. I don;'t game on my phone. I mainly surf, email and chat. Those functions are doing just fine. In essence, it's much like a computer. You can reach 4.5 ghz overclock and taking it up to lets say 4.7 may not be noticeable in any way other than bench marking and such and we are not doing that continuously as it is.
Interesting point on the leak and the possibility of new ROM's hitting the threads soon. Not used to how those innovations work in the cell phone world. If that's the case, then I feel that I should wait a bit and then play around with the new ROM's that are soon to be born.
Thanks for the insight...
Kahbrohn said:
I agree on the battery thing being more a matter of bulk. That's why I was looking at the 2800 mAh battery instead of the 3500+ mAh. I believe the bulk should be less. I have big hands anyways so it shouldn't be much of an issue BUT, if I need to put the phone on a pocket fort example, that might be an issue.
I see your point on the sluggishness of apps and such. I really can't complain that much of anything being slow or stuttery. Netflix works just fine. I don;'t game on my phone. I mainly surf, email and chat. Those functions are doing just fine. In essence, it's much like a computer. You can reach 4.5 ghz overclock and taking it up to lets say 4.7 may not be noticeable in any way other than bench marking and such and we are not doing that continuously as it is.
Interesting point on the leak and the possibility of new ROM's hitting the threads soon. Not used to how those innovations work in the cell phone world. If that's the case, then I feel that I should wait a bit and then play around with the new ROM's that are soon to be born.
Thanks for the insight...
Click to expand...
Click to collapse
I actually think the overall feel of GB to be slow and the browser in particular sluggish at times when compared to other devices (not necessarily with better hardware, just with newer software). I guess it comes with territory after tinkering with fully working JB builds on other devices. To be fair, I didn't see it as much until I tried it out... It's kinda like giving a blind man a brand new pair of eyes.
On the overclock thing, 4.5 to even 5 Ghz the difference is very negligible as you say, but a 1Ghz to 1.3 or 1.5 GHz jump is very noticeable. Remember we're talking an extra 30-50% in CPU cycles.
How do you all find the new Jellybean update's battery life? Better or worse than ICS? I'm guessing worse because of Google Now, but just wondering...(I don't have phone yet)
seems worse to me i was gettinf better battery life on ICS.. my battery drops from 100% to 50% way to fast..
Battery life on the new JB update is amazing!
Even MeanROM never was this good with battery life!.
After a couple of days and restarts its looking good
Sent from my EVO using xda premium
evo401 said:
seems worse to me i was gettinf better battery life on ICS.. my battery drops from 100% to 50% way to fast..
Click to expand...
Click to collapse
If you were not such a FLASHAHOLIC just sayin
There is actually a logical and technical reason as to why JB have worse battery life than ics.
As many people probably know, JB focuses on project butter which aims to make the android experience smoother.
Unfortunately, Google's philosophy is about brute forcing into the problem by relying on raw cpu and gpu power instead of fixing their shaddy code.
The most noticeable difference on JB is UI becomes smoother but that smoothness came at a price, the cpu and gpu has to work harder to maintain 60fps with added vsync triple buffering on top of it.
I also noticed that HTC has boosted the.default 3d gpu clock of adreno 225 on their latest kernel to compensate for the additional workload to maintain smoothness. Some people that is familiar to overclocking knows that if the clocks are increased, the power consumption also increases. It is also not help by the fact that EVO 4g LTE can't always maintain 60fps so it has to work extra hard.
Probably not a lot of people know this but android has abysmal input lag and Google tried to address the issue(in which imo they horribly failed) by boosting the cpu clocks everytime you touched the screen. Obviously, raising the clocks would have negative impact on battery life so if you type a lot or Swype a lot or scroll alot, the cpu would get raised everytime. You could see it yourself by installing a program called micro cpu monitor.
The most obvious way to see the input lag in action is try playing a music then replicate the beats on apps like real drums. The lumia 900 which has single core or even the iPhone 4 which has single core 800mhz cortex a8 does not suffer from horrible input lag.
I was really disappointed with Google and it seems like they have no plans to really fix the core problems in the near future.
Sent from my EVO using xda premium
bigdaddy619 said:
If you were not such a FLASHAHOLIC just sayin
Click to expand...
Click to collapse
hahahah!! u are so rite!! i do have a problem with flashing