Hi there,
probably that request would make more sense in the developer forum but i didnt post enough yet
Actually i get insane battery batterylife with the bali 1.8.8 UV version, therefore i tried the non UV version with even more lowerd voltages via set cpu. it was stable but drained a lot faster. don´t know why.
so my request would be "pre-undervolted" bali kernels that might have even longer batteryliftime. Any hints on that? Someone who is able to compile something like this?
Best regards,
vibrantoparanto (from germany)
Hint' Bali X+Voltage control app= win !!!
Sent from my SGH-T959 using xda premium
^^ that is your answer....currently what im using
bali-x is what i used before - i lowered the voltages up to -150mv with some frequencies but it still gave me only about half the battery lifetime (less than 24 hours with moderate use) then i get with bali uv. What did you use to manually undervolt and how is your battery lifetime?
vibrantoparanto said:
bali-x is what i used before - i lowered the voltages up to -150mv with some frequencies but it still gave me only about half the battery lifetime (less than 24 hours with moderate use) then i get with bali uv. What did you use to manually undervolt and how is your battery lifetime?
Click to expand...
Click to collapse
i hate to burst your bubble, but youre chasing a ghost. uv'ing will not produce very noticeable changes to your battery life, especially if were are talking baout different versions of the same kernel.
take a look at this: http://forum.xda-developers.com/showpost.php?p=21024393&postcount=8
Cannot agree with that. I tried *a lot* and flashed different roms and kernels for years now. With stock kernels i get up to two days standby with low/moderate use, with bali UV i get almost three days. I have no idead why, but at least the standby time differs dramatically between kernels. At least thats for sure - under load that might be another thing. But probably you´re right and its just a "good standby behaviour" which would hardly benefit from lowered voltages. Would be still interesting to try a hardcore UV kernel
TopShelf, it is funny that you posted that note/post b/c I was just getting ready to PM you that I put part of it in my guide like I mentioned a week or so ago and the apps too.
Take a look at the Guide and maybe you will find some answers to your questions.
If you want to UV to the max, then you will have to test that yourself b/c every Vibrant reacts differently to OC/UV. Step it down -25v each day (don't set on boot until you know they work) and see where it freezes. There are OC/UV examples in the guide but beware, they are both for MIUI kernels.
Is there probably any admin out there who understands what i talk about and can move that thread to the developer forum?
this thread belongs here, you posted in the right section. posting in development will not get you answers from developers, it will only get you yelled at by hall monitors.
it is a common misconception that "developers" ONLY visit the "development" section. this is far from the truth.
sorry to say, the reason you have not gotten answers isnt because you posted in the wrong section, but because requests like these are pretty much never honored. the reason is because if a developer decides to make a slight alteration to a ROM/kernel for a member, he will then get BOMBARDED by dozens of other members who have tiny little tweaks that they would like in their ROM/kernel
Still trying to bring back some life to my request with this argument: I just checked my girlfriends device (using zendroid 2.1.2 with bali 1.8.8uv) and couldnt believe it: 3 days and 14 hours since unplugged with 8% left. The battery is a stock 1500mHa. And as its my girlfriends phone its definity not "overtweaked and calibrated". Personally i care much more about standby time than super heavy usage (guess that should be fine then too).
vibrantoparanto said:
Still trying to bring back some life to my request with this argument: I just checked my girlfriends device (using zendroid 2.1.2 with bali 1.8.8uv) and couldnt believe it: 3 days and 14 hours since unplugged with 8% left. The battery is a stock 1500mHa. And as its my girlfriends phone its definity not "overtweaked and calibrated". Personally i care much more about standby time than super heavy usage (guess that should be fine then too).
Click to expand...
Click to collapse
Since you didn't like the answer you got, for clarification purposes you are basically asking for a dev to use their time for FREE an modified/debug/test a kernel with your requirements just for your own sake ?
i wanted to point out that this is a very interesting kernel with great battery lifetime. if you have a look at all the other threads of people desperatly trying to get 24h of battery then you probably wouldnt consider this request as "wasting free time of others for my own sake".
vibrantoparanto said:
i wanted to point out that this is a very interesting kernel with great battery lifetime. if you have a look at all the other threads of people desperatly trying to get 24h of battery then you probably wouldnt consider this request as "wasting free time of others for my own sake".
Click to expand...
Click to collapse
i can prove to you that UVing does not make that much of a difference. if youre willing to learn, try this little experiment:
-UV your phone using your current settings
-put your phone in airplane mode
-turn it off
-charge it to 100% while its off
-after it boots up, leave it in airplane mode and immediately lock the screen
-let your phone sit idle in airplane mode from full charge to death (record the time)
--------------
Once youve done this, repeat all of the above steps but with STOCK VOLTAGE. record the time.
now compare the two times. i would be willing to bet a large sum of money that it is not a notable difference, if any.
my point is instead of trying to convince yourself that your theory of UVing is correct, why not do a TRUE battery life test, and simply find out for yourself. you cannot run true battery tests while you are actually using your phone becuase phone usage is massively different on a day to day basis, even if you dont think it is, it is. there is background data, text messages/calls, notifications, etc. (which is why i said to put it in airplane mode, that way its just sitting there, with little to no variables)
i guarantee you that you are putting way too much thought into voltage settings. they do not help as much as people want them to. dont say im wrong until you actually try what i said above. although youre probably nto going to.
vibrantoparanto said:
Still trying to bring back some life to my request with this argument: I just checked my girlfriends device (using zendroid 2.1.2 with bali 1.8.8uv) and couldnt believe it: 3 days and 14 hours since unplugged with 8% left. The battery is a stock 1500mHa. And as its my girlfriends phone its definity not "overtweaked and calibrated". Personally i care much more about standby time than super heavy usage (guess that should be fine then too).
Click to expand...
Click to collapse
sorry, but this does not prove anything. what are you comparing it to? your phone? you cant compare her battery life to your own unless you guys have the same exact setup, same exact apps, and same exact usage habits, etc.
you are not going about this battery things the right way. you NEED to be willing to learn more instead of trying to come up with your own reasons in your own head as to why your battery gets a specific lifespan. If getting THAT MUCH more battery life was as easy as UVing your phone, dont you think the manufacturers would incorporate that and use that as a marketing strategy?? "New from Samsung, the Galaxy S III!!! This will revolutionize the mobile industry, curing the battery woes across that smartphone world...now with lower voltage for drastically improved battery life!! Pick yours up today!!"
It's not that easy, you need to read up on what affects battery life.
thank you for your thoughts topshelf, but as i posted earlier i am on that topic for years now and i really tested a lot. not as scientific as running phone on idle with different frequenzies but trust me: I know a whole lot about this topic. Also i share your thought that the voltage is not that important in the end. On the other hand i have to say you guys are quite ignorant about my observations i did earlier:
1. The bali-x kernel with manual undervolting provides (provable) worse battery lifetime than
2. the 1.8.8uv kernel.
Conclusion: As you say it is not that much about the voltage but about the way the kernels work as a whole. On the other hand it would be *very* interesting if the insane battery lifetime of bali uv could be even further improved. And no i wont put my phone to sleep for days in order to do scientific test (whoever is willing to i will donate - battery lifetime almost like astrology)
Last but not least: It is true that different roms provide significantly different battery lifetimes - for whatever reason. Some roms turn your phone into a handwarmer, others give you almost the standby times you were used from the non-smarthpones. And i think even the big companies have a hard time to write device specific code that is highly optimized - i mean you still get new devices with gingerbread instead of ics and so on. conclusion: on the software side *is* much room for improvement if it comes to battery lifetime on most devices.
just my 2 cents
vibrantoparanto said:
i wanted to point out that this is a very interesting kernel with great battery lifetime. if you have a look at all the other threads of people desperatly trying to get 24h of battery then you probably wouldnt consider this request as "wasting free time of others for my own sake".
Click to expand...
Click to collapse
Look at your post, you and "others" are asking for some one to do research and development on their free time and for free ? little selfish on you.
Look at all the kernels thread in the development section and read thru all the comments, I bet there is far more people whining and complaining about this and that, than providing actually constructive and monetary feedback to the developers.
Its not as easy as it seams, ecotox already tried this before with his ultra low power kernels and some reported great succes while others couldnt even boot, it goes down to the quality of the silicon on each particular phone. no dev has the time/money to develop such request considering all the different variables involved.
lastly if you are so fond on this idea, why dont you take the initiative and learn to compile and patch and make your own kernel ?
Diff phone but a good simple guide to read:
http://arighi.blogspot.com/2011/08/howto-custom-kernel-on-samsung-galaxy-s.html
basic read:
http://stackoverflow.com/questions/5529470/how-to-compile-linux-kernel-for-real-android-phone
basic read:
http://igottadroid.com/wordpress/?p=61
For latest source:
http://opensource.samsung.com
"Be the change you want to see in the world." Mohandas Gandhi
Simple: If you want to change the world, start with yourself.
I'll read those links. Thanks for the info.
vibrantoparanto said:
And no i wont put my phone to sleep for days in order to do scientific test (whoever is willing to i will donate - battery lifetime almost like astrology)
Click to expand...
Click to collapse
im not trying to pick on you, but this sarcastic response shows your overall attitude that jrafael is trying to make you realize. you want somebody to take time out of their day/night to do something for you...yet you arent even willing to let for phone sit for a day in order to learn a thing or two...letting your phone sit doesnt even take any effort, compiling a kernel takes a lot more effort than that
i hate to say it, but why should someone help you, if you dont want to help yourself.
thank you jrafael for the links - thats a great read.
@topshelf: still think you overreact here. For one who has developed it and has the workflow it is a matter of a few minutes - and no one is forced to do anything unless he thinks its might be worth it - maybe its inspiring? i am just asking. not everything idea must be done by the one who thinks about it. and the quote about battery life is true i would say - we are really lacking valueable info on battery drain with different setups.
Related
Ever since I first released an undervolted kernel (can you believe that it actually used to be a new idea? Seems so normal now), its been a mad dash to see how much further down the voltage can be pushed. In light of recent events, there has been controversy regarding whether or not dropping below ~925mV actually begins to negatively impact battery life.
Without getting into the technical details behind why I believe that going that low actually does affect battery life, I'm conducting a blind study. I'm going to produce 3 kernels at three different voltages. I'm then going to send these kernels randomly to people that sign up on the attached spreadsheet in order to collect data for 7 days.
I know that this won't be 100% accurate, but I feel that if we get a large enough sample size, over 7 days, the general trend should emerge.
What I ask for you to do if you want to participate is sign up on the attached spreadsheet and try not to change your rom/usage patterns within these 7 days. Just go about your day and record your values at the end.
You will not know what the voltage of the kernel you are receiving is, so there will have to be a certain degree of trust. I promise I will do my best to not blow up your phone
This truly has to be a community effort. The more people we have, the better. Once the study has been concluded, I will reveal which kernel had the best battery life for the most amount of people.
Please spread the word about this, the more it is on blogs and the like, the greater the sample size and the more accurate the results.
Link: http://bit.ly/9YjM5X
UPDATE:
The kernels have all be emailed to people that gave me an email address. Tues-Sat, please run the kernel that is labeled CONTROL. Do not alter your day to day usage from what you always do. At the end of each day please record how long you were off charger and your percent battery left. Use your best judgement for giving statistics. The more detailed, the better.
Sunday-Thurs we will run the TEST kernel. Again do the same thing and record your usage daily.
It is VITAL that you record the statistics at the end of the day every day.
As an added bonus, I included the memory modification by coolbho3k because I know you all want the latest and greatest
Will it matter what battery we have? Or is stock battery required?
Four Fourty Four said:
Will it matter what battery we have? Or is stock battery required?
Click to expand...
Click to collapse
doesn't matter as long as you post your previous results so we have something to base it against.
This is a fantastic idea. Might actually help me recover from my kernel flashing compulsion. Prolly not though....
Persiansown, what do you mean by "record your values at the end"? Are we to take a log of battery usage or just writing down on the sheet what the usage was like each day?
thanks
jblazea50 said:
Persiansown, what do you mean by "record your values at the end"? Are we to take a log of battery usage or just writing down on the sheet what the usage was like each day?
thanks
Click to expand...
Click to collapse
Its going to be subjective but I'm trying to figure out the best way to record them right now. I don't need any feedback values until I actually send out the kernels though
persiansown said:
Its going to be subjective but I'm trying to figure out the best way to record them right now. I don't need any feedback values until I actually send out the kernels though
Click to expand...
Click to collapse
yeah, i understand that it's not needed until after we start using the kernel; just wanted to know what you were actually looking for, and if it wasn't subjective
thanks and looking forward to this
im really interested in this. would it also be possible to give feedback on reception? because as of late my signal has been worse with all the uv kernels...
How are we going to set the baseline? The best way to eliminate the potential for usage differences to skew the results is for us to all run the exact same kernel for X amount of time to set a baseline, then do the blind test of the 3 different kernels, and compare the difference between before and after.
pjcforpres said:
How are we going to set the baseline? The best way to eliminate the potential for usage differences to skew the results is for us to all run the exact same kernel for X amount of time to set a baseline, then do the blind test of the 3 different kernels, and compare the difference between before and after.
Click to expand...
Click to collapse
Yeah I've been trying to think of a way that would take less time, but I think that way would be best. Anyone have a better suggestion?
persiansown said:
Yeah I've been trying to think of a way that would take less time, but I think that way would be best. Anyone have a better suggestion?
Click to expand...
Click to collapse
We could also look at time spent "running" in spare parts... but that would be much more complicated and less accurate (I would hate to do the statistical break down on that)... but it would be much quicker and would provide some nice info as well... ie 5 hours spent running and 7 hours sleeping used 80% battery... where as 1 hour running and 11 hours sleeping used 50%... but we would also have to factor in so many other aspects and track those to get a truly accurate picture, ie WiFi or 3G or 2G... what is your screen brightness... and so forth.
Hey persian, this is a great idea!!! to get to the bottom of all this.
Can I suggest something though, and hope I don't get flamed for it, or hope you wont take it the wrong way. But will you include, an AVS kernel running 800mV as well? There have been discussions about this also. Thanks!
Each tester would have to test all three kernels and try to maintain roughly the same useage. Was this your plan?
pjcforpres said:
How are we going to set the baseline? The best way to eliminate the potential for usage differences to skew the results is for us to all run the exact same kernel for X amount of time to set a baseline, then do the blind test of the 3 different kernels, and compare the difference between before and after.
Click to expand...
Click to collapse
This is a good approach. But I think for it to be even more standardized one would need to run this completely app and theme free. THe interaction between certain apps and usage is an unknown variable. For example, how much does K-9 mail draw? It goes without saying that themes have some sort of affect on behavior. So IMO, to be as objective as possible you would need to remove all sources of ambiguity to have this test mean something. Just my two cents
pjcforpres said:
We could also look at time spent "running" in spare parts... but that would be much more complicated and less accurate (I would hate to do the statistical break down on that)... but it would be much quicker and would provide some nice info as well... ie 5 hours spent running and 7 hours sleeping used 80% battery... where as 1 hour running and 11 hours sleeping used 50%... but we would also have to factor in so many other aspects and track those to get a truly accurate picture, ie WiFi or 3G or 2G... what is your screen brightness... and so forth.
Click to expand...
Click to collapse
That would be pretty complicated and I think Kmobs would need a grant to run the statistics. I think there would have to be a baseline established like GPS off, brightness set to x percent, bluetooth off etc. And I think as Kmobs knows, each chip was not created equally.
Persiansown, I don't think you need to start with a baseline in order to compare. Once you send out the kernel and we use it for 1 week with normal usage for each user. At the end of the week, you can send out another kernel, exactly the same this time for everyone, and we can use it for few days and we will be able to notice the difference.
Correct . This is how I thought he was gonna do it. And what I think is best.
jblazea50 said:
Persiansown, I don't think you need to start with a baseline in order to compare. Once you send out the kernel and we use it for 1 week with normal usage for each user. At the end of the week, you can send out another kernel, exactly the same this time for everyone, and we can use it for few days and we will be able to notice the difference.
Click to expand...
Click to collapse
pjcforpres said:
How are we going to set the baseline? The best way to eliminate the potential for usage differences to skew the results is for us to all run the exact same kernel for X amount of time to set a baseline, then do the blind test of the 3 different kernels, and compare the difference between before and after.
Click to expand...
Click to collapse
persiansown said:
Yeah I've been trying to think of a way that would take less time, but I think that way would be best. Anyone have a better suggestion?
Click to expand...
Click to collapse
I was trying to think of a good way to get a baseline to compare to for every one and this is my sugestion. Make three kernels at 850, 925, and control/stock. Send everyone on the list two kernels, one of the two UV kernels and one stock/control. Allow them to run the first kernel for a certain number of days, record data, then send everyone the second kernel and do the same. Randomize who gets the control first or the UV first and keep it blind. (Don't tell them which of the two is the control obviously.) This way half test the 850, half test 925, and all test the control/stock, giving you an accurate baseline for everyone's individual phone usage and battery size.
Scientific Method FTW!!!
awesome idea.
Count me in...I will sign up when I get home from work tonight. This is an excellent idea. Ideas lke this is what make xda the number one source for android information.
First off, hello to everyone! First post here, even though I've been following the community for about a month now.
Now, I'm running KaosFroyo v38 on my Eris - flashed CFSv6 and all works like a dream. Hell, my camera even works perfectly so far!
But, my battery life was crappy. I just started wiped my battery stats earlier (around 11:45ish), and now at 2:00 it's around 85%. Not as bad as before, but I definitely think it could be better Anyways, after some searching, I've only found a how-to for the recalibration, but I was wondering about the proper behavior for the recalibration. Now, I don't really know how it works, so forgive me if I'm asking a dumb question or if I'm just begging for the Kracken to be released.
Part of me wants to baby the phone, not do anything with it and let it last as long as possible - this is, after all, the reason for recalibrating, right?
The other part of me wants to abuse my phone, do some web surfing, download a ton of crap, and drain my battery. My logic makes me wonder if the battery should get used to the abuse to work better during everyday use...?
There's another part of me that thinks I should just use the phone normally as I would any other day just to find a happy medium between the two.
Then there's another part of me that wonders if any of this really matters at all... and if that slightly fishy smell in the air might be the Kracken approaching....
Just wanted some opinion on how to properly get the battery up to its fullest capabilities, which method did you use when you recalibrated??? I'm planning on continuing the drain/charge cycle for the next couple of days to see what happens, and if not, I'm gonna try flashing KaosFroyo v37 and see how that works, or gonna go back to ZenEXP Eris v7 (which so far has been nice and stable and looooooong-ass battery life, but the Sense seems to be a bit sluggish :/, but overall another beautiful ROM). I'm also running setCPU back a bit at 604 from the 710 that v38 comes set with, wondering if dialing it back a little like I did would help me conserve battery, or if maybe it was overclocked to 710 for a reason and perhaps it's able to run better that way?
Anyways, thanks for taking the time to read!
come.home.astronaut said:
Then there's another part of me that wonders if any of this really matters at all... and if that slightly fishy smell in the air might be my wife approaching....
Click to expand...
Click to collapse
sry couldnt help myself
edit# 2: Thats what the thanks button is for
Thank you for your very well-informed help, kind sir.
Sent from my KrackenSummoner-3000
kpd2003 said:
sry couldnt help myself
edit# 2: Thats what the thanks button is for
Click to expand...
Click to collapse
I thought I showed her already how to get rid of that...
On topic, I followed DS36's recommendations. You can find his thread about it in the Eris Development forum.
Flash the Conaps CFSV6 or CFSV9 Kernel, it'll fix the battery drain. Go to the FAQ page for the KAOS FROYO builds:
As of V38
If you flashed v38 and your battery is Rapidly discharging, please try flashing Conaps CFSV6 kernel (just like you flashed this ROM, from recovery) Here is a link to Conaps kernels and other goodies:
Also, in the ERIS FAQs, there is a sticky that covers how to recalibrate your battery.
Was just thinking about buying the app SetCPU for root users, and was wondering if I was actually knowledgeable enough to know what I was doing. And I'm probably not.
So, could you give me the details of what this does? I know OC improves performance and UC saves battery, but is there anything else I should know?
Would this app even be necessary since the Atrix already has good battery life? I get about 18 hours with heavy use.
Basically just tell me what I need to know about SetCPU.
Ok. I guess nobody wants to help.
Never live in the past but always learn from it.
Tennis11 said:
Ok. I guess nobody wants to help.
Never live in the past but always learn from it.
Click to expand...
Click to collapse
I've never used this software before and I'm interested as well but you're jumping the gun about this... you only posted 2 hours ago...
Sorry.
Never live in the past but always learn from it.
Gotta give more time for people to reply... it's not uncommon for a thread to not have a reply for a day or 2.
As of now, it can only underclock the atrix... no overclocking really. It's a simple program in terms of ease of use. There's a minimum and maximum setting. You can lower the max to underclock if you want to save battery and you can increase the minimum performance. Someone said they felt the phone ran better when they increased the minimum, though I honestly don't see much of a difference. Increasing the minimum will cause more battery drain.
For now, I don't really see a use aside from underclocking to save battery life. I haven't personally tried that as, like you, I have been satisfied with the battery life. If I knew I wouldn't be able to charge the phone for a while, I might give it a try, but haven't really wanted to bother with it. Otherwise, you can toy around with it for a few minutes. I'm hoping we'll get an update so we can overclock sometime.
Yesturday I woke up at 5 am and flashed 1.2.6 to remove all the buggy ROM I had installed. I then rooted and downloaded a few root apps; setcpu, TI backup (for freezing some worthless moto crap), and root exporer. Then using setcpu I set my max speed to 760 and made a profile so that when the screen is off it sets the max speed to 312. I really didnt start using the phone heavily untill about 4 pm (at this time I think my battery was reading about 89%). When I say heavy, I mean more than I would normally use in one day. At 1 am this morning, still on my phone, barely able to hold my eyes open, the battery was at 10%. I really dont know if setcpu contributed to my battery length, but I'm leaving the current phone setup alone.
Hello.
I am about to buy the SGS2 and have a couple of questions before I go ahead with my purchase. Currently I have a HTC Desire, and need to know how much I need to change. Here we go:
1) Battery life: I know that it very much varies depending on the usage, but given on average how many hours/days do you actually get out of that battery. With Desire, I am getting 1.5days on medium/low usage.
2) USB: I have a few usb's that were bought for my Desire, and was wondering if I could use them with SGS2? I am specially concerned about the mini-usb ending and its shape. Could anyone confirm whether it looks similar to this or not:
http://www.universalgadgets.co.uk/images/products/Big11_e947682u6x5it.jpg
3) In terms of recoveries and etc, does such thing exist with SGS1/2? Can I use the ClockWorkMod recovery with this?
4) Is the panel full-true multi-touch? Not emulated, since I 'heard' that SGS1 was emulated, and you could only use two fingers in specific motion. This was not the case with HTC Desire, and definitely not the case with iPhone. (please don't bite me for using the 'i' word here ;P )
5) Also, any issues that you (personally) have had with SGS1/2?
I appreciate your help, since I am going to pay £500, thought I should ask my questions first.
Thank you,
Mo.
nothing against u but how can u compare skoda with latest mercedes? are u mad? if u have enough money to buy sgs2 why would u use outdated acesories?
and your questions can be answered...look futher this web site... HTC battery life sux btw...and its well known information...
regards
Hunteres said:
nothing against u but how can u compare skoda with latest mercedes? are u mad? if u have enough money to buy sgs2 why would u use outdated acesories?
and your questions can be answered...look futher this web site... HTC battery life sux btw...and its well known information...
regards
Click to expand...
Click to collapse
Thanks! I had already done a google search, XDA search and youtube search, nothing that could be found (which was proven useful for me).
Don't get me wrong, I am not comparing HTC Desire with SGS2. That would be stupid. Hence why I am buying SGS2.
About accessories: The question is, why would I need to buy more accessories - If I can use the one that I already have?! Also, since when, USB2's can get outdated??!
Battery life: On HTC website, it says that it has up to 340hrs of standby time. That's a lie. Also, the battery is only 100mA less than SGS2 battery (yes I know dual core and etc etc). So, again, how many days you are 'actually' getting from this?
Thank you,
Mo.
But the question that remains is, how much battery do you actually get?
mofirouz said:
Hello.
I am about to buy the SGS2 and have a couple of questions before I go ahead with my purchase. Currently I have a HTC Desire, and need to know how much I need to change. Here we go:
1) Battery life: I know that it very much varies depending on the usage, but given on average how many hours/days do you actually get out of that battery. With Desire, I am getting 1.5days on medium/low usage.
2) USB: I have a few usb's that were bought for my Desire, and was wondering if I could use them with SGS2? I am specially concerned about the mini-usb ending and its shape. Could anyone confirm whether it looks similar to this or not:
http://www.universalgadgets.co.uk/images/products/Big11_e947682u6x5it.jpg
3) In terms of recoveries and etc, does such thing exist with SGS1/2? Can I use the ClockWorkMod recovery with this?
4) Is the panel full-true multi-touch? Not emulated, since I 'heard' that SGS1 was emulated, and you could only use two fingers in specific motion. This was not the case with HTC Desire, and definitely not the case with iPhone. (please don't bite me for using the 'i' word here ;P )
5) Also, any issues that you (personally) have had with SGS1/2?
I appreciate your help, since I am going to pay £500, thought I should ask my questions first.
Thank you,
Mo.
Click to expand...
Click to collapse
1) My battery life has been able to last me through a full day of use. It doesn't have amazing battery life but, it doesnt have terrible battery life. I usually go through around 15-18 hours of use on it. Texts, some games, internet browsing, and a lot of music use and I still haven't had the battery die on me before the day is over.
2) That USB cord should work fine with the SGS II
3) As of right now, there isn't a CWM recovery for the SGS II but, Samsung uses a program called Odin where you can flash different things.
4) As far as I know, the SGS II supports full multi-touch. I remember seeing a video of them testing it can't find the link tho :/
5) The only issue I have with it so far is once its fully charged a notification appears. It might not seem like a problem but, it has woken me up once or twice which is annoying.
Hope this helps.
mofirouz said:
Thanks! I had already done a google search, XDA search and youtube search, nothing that could be found (which was proven useful for me).
Don't get me wrong, I am not comparing HTC Desire with SGS2. That would be stupid. Hence why I am buying SGS2.
About accessories: The question is, why would I need to buy more accessories - If I can use the one that I already have?! Also, since when, USB2's can get outdated??!
Battery life: On HTC website, it says that it has up to 340hrs of standby time. That's a lie. Also, the battery is only 100mA less than SGS2 battery (yes I know dual core and etc etc). So, again, how many days you are 'actually' getting from this?
Thank you,
Mo.
But the question that remains is, how much battery do you actually get?
Click to expand...
Click to collapse
mate u didnt do a research...if u did u will find out that SGS2 has far better battery performance then any HTC..thats mean heavy ussage - very heavy + gaming etc is around 12-16 hours - medium use is more then 24h and soft usage with 3g on and sync on + phone calls and some wifi is about 1,5-2 days..i hope thats enough ..about battery..
Super Amoled plus - latest technology display - full multi touch ..extremly well responsive - once again..latest technology!...
and if u wanna know more about battery performance there is already topic about it...but i believe u saw it..right?
regards
I have just moved from the HD2 (on Gingerbread) so a close match for your Desire. I was getting battery down to an average of 60% after 24hrs SGS2 is about 70% on the same useage. My car charger works just the same . No clockwork yet, but most devs have only just managed to get their hands on one this week and there is already one rom available. Multi touch works. I loved my HD2 (still do) but this is better.
ok, cool. Thank you guys. Answered my questions
In terms of battery life, I put a lot of effort into tweaking the crap out of my Desire. Using VillianROM and an undervolted+underclocked cpu I tended to sit around 70% after a regular workday, which was probably twice what I had on stock.
My SGS2 is completely unmodified or rooted, running stock KE2. The same usage patterns yield me around 85% battery after a full workday, and under heavy web browsing the battery life difference seems even more pronounced.
Factoring in the fact that I'm experiencing the documented battery drain bug causing aroung 50% of my battery usage to be taken up by "Android OS" and "WiFi Sharing", I would expect this battery life to improve quite significantly beyond this point once this bug is fixed.
tl;dr Battery life is acceptable, and much better than Desire. Expect it to be extremely good once a few software bugs are fixed.
Q: I WAS told this phone won't work on t-mobile. Only at&t.
Any 1 running it on tm? Advice plz
Vibrant
Okay. So I am currently running shostock3 on my sgs2 with siyah kernal. I read the article from zedomax on galaxys2root.com that it has very good battery life and very stable but when i am running it, I have terrible battery life and i am currently underclocked or whatever the word is. Is there anyway to fix this?
My advice, run SHOstock3 as it was released. It runs great as shoman94 dev'd it.
...and stay away from that web site u mentioned.
Stick to XDA. Period!
Sent from my SAMSUNG-SGH-I747 using xda premium
Yes. I'm running shostock3 with the included kernel and get good battery life.
Sent from my SGH-I777 using xda premium
Getting great battery life on Shostock3 V3.0. Flashed the AJK 1.52s kernel. Checkout Better battery stats...see if you have wakelocks killing your battery. And..I agree that website is no good..stick to XDA.
Sent from my SGH-I777 using xda premium
gainstatom said:
Okay. So I am currently running shostock3 on my sgs2 with siyah kernal. I read the article from zedomax on galaxys2root.com that it has very good battery life and very stable but when i am running it, I have terrible battery life and i am currently underclocked or whatever the word is. Is there anyway to fix this?
Click to expand...
Click to collapse
which siyah kernel u r using. as far as i know theres no siyah kernel to run with shostock 3 except for ajk's (ktoonsez stopped working on siyah kernel for jb i777 after release of 4.3.3).
EQ2192012 said:
Getting great battery life on Shostock3 V3.0. Flashed the AJK 1.52s kernel. Checkout Better battery stats...see if you have wakelocks killing your battery. And..I agree that website is no good..stick to XDA.
Click to expand...
Click to collapse
Most people get really good battery life on SHOstock3. Just search the SHOstock3 thread for the word battery to see what I mean. If you're not getting good battery life, you need to find out what in your configuration is causing the problem, and fix it. There is a thread in the general section started by Entropy512 that you should study to help you identify where the problem is.
I was on GB ShoStock for a long time thinking ICS and JB would never leave me satisfied on battery life.
http://forum.xda-developers.com/showthread.php?t=1353513
Finally came to my senses and tried out ShoStock 3 and have never looked back. To make it short the best Rom Ive ever flashed for any device I have had in the present and past.
You definitely have a rogue app killing your battery, find out which one it is and uninstall.
gainstatom said:
Okay. So I am currently running shostock3 on my sgs2 with siyah kernal. I read the article from zedomax on galaxys2root.com that it has very good battery life and very stable but when i am running it, I have terrible battery life and i am currently underclocked or whatever the word is. Is there anyway to fix this?
Click to expand...
Click to collapse
Sorry you have battery life problems.
I have been running Shostock3 since it came out (it's version 3.02 today!), but I also been on and off at least five (wow can it be that many?) JB roms on my SGH-i777 (won't even mention the # GB roms here!). After trying many, I must agree with the other posters who state that this rom delivers very good battery life when compared to stock and when compared with other custom roms.
Lately, it has delivered the best battery life I have ever had on this phone using any rom (although SlimBean JB provided very very good battery life for me recently as well! Also UnNamed was great for battery life in the old GB days )
I followed the recommendations made by creepyncrawly to read Entropy's (& others) battery notes/faqs. They provide some really good background, some with that typical "XDA flavor" (read technical!. That material, plus some more plain old simple user adjustments to how and what I use on the phone have improved my phone's battery time; and it might help you as well.
It really boils down to the fact that each phone user loads different apps and our usage patterns vary.
Assume that you've flashed it and let it settle for a few days and several recharge cycles. After doing this you can see what YOUR "norms" are. They may be good or bad, but that's the baseline for you with this rom and with the apps and usage pattern you have.
(You can tweak voltage and speed (well, not speed on SS3!), but my experience has been that the more noticeable changes will be by adjusting your pattern of use, or doing the "hunt for the app" (or apps) that are burning down your run times when not in use.
Not many here seem to like or do this, but I would also try one of those "help-you-with-battery-use" apps --like juice defender (Ok, I get that many here seem to think it a waste, but it really did help me --a little-- when I used it); or get DS Battery saver (a bit more aggressive and noticeable, but you also notice the lag while you wait for things to turn on when you want them).
Actually, these may not be precision solutions, and don't focus on your specific phone app use, but they do work in a macro way to slow battery use and simply working with them for a few days or weeks will provide you with a better a sense of what the heck is going on under the plastic; they will cause you to look at what you have/run and when.
Oh, this includes using Better Battery Stats, which is fine for reporting out exactly which the apps behave --or don't-- and by how much and when. I'm not slow (well, that slow but it frankly, it took me quite a while to figure out what I was reading in the BBS readouts and what they meant! (Now, after a year+ or so of using it, I don't even have it loaded, since I've done the fiddling I need --and BBS, plus those other battery apps, helped me to figure out what apps worked well, what apps I was willing to sacrifice battery on and what apps were useless and should be tossed.)
Finally, some roms just don't work for people! So it's not worth the frustration chasing something you may not be able to achieve with this or another rom. (You probably read how individuals have problems that you don't -yet, you run the same rom and the same phone! That is our world. So, too, you will read about some who make amazing claims on how long they continue on one charge. Some are pretty amazing, and some may even be real
My final five cents would be:
#1 run the rom a couple of days, get a baseline. Then switch from Jeboo kernel to AJK's latest for TW (I think it is 1.25ss, but I really also had great results from 1.48s) and run it a few more days. They were pretty much even for me, but others find one or the other kernel makes a real difference!). Compare after doing the same activities through a charge or two.
#2 If your battery life remains "poor," note what poor really is (ex. how much screen time? and how much total run time prior to getting to zero or 10-15%? ...something like that).
#3. Then get BBS and one of the "automatic" battery-saver programs and work with it for about 4-5 days and that many recharge cycles. See what your norms are but do it for the same type of usage!!! If better while using the battery fixers, then you can work at picking off the app or apps that are sucking your battery more than you want. Not as tedious as it sounds. Of course, staying with a rom for three weeks might be a challenge :laugh:, but this is a nice rom to work with.
#4. I don't think you will need to under-volt to get good BL. I wonder if your phone is stable in doing that? Or, does it induce additional lag? That might be a high price to pay for more run time. (You could compare the UV results with your "norm" as well!)
#5. Finally, we are on Galaxy S2 Sgh-i777 -and can change batteries all day long for not so much per battery! It is not elegant, but it works. (Done it myself several times -even with good battery life).
Good Luck!
Best ROM, Good battery life... been with Shoman's ROM since shostock2 never have a problem with the battery life...
Sent from my SGH-I777 using xda premium