Related
Hey people,
following on from artisticcheese's thread about battery consumption Ive performed a few tests on some different radio versions to see what the actual difference in battery consumption is.
Right now (as of 16-01-2008) I recommend the following radios:
1.47.30.10 with an overall score of 1.22 (the highest in the test)
or
1.54.30.10 with an overall score of 1.21 (2nd place).
Remember people, if you are planning on changing your radio version, flash hardspl, and make sure nothing is running which will interrupt the flash process. The radio flash is still the most risky of all flash processes and it is possible to kill the device so be sure before you flash. In doing these tests I performed over 10 radio flashes in a day and i made usre nothing CPU intensive was running on the PC and that i wasnt going to unplug the USB by accident etc...
-------------------------------------
Test Run 16-10-08:
Before running these tests the phone was soft reset, ALL today plugins shut off (apart from x button), internet explorer for downloding and acbPowerMeter for power monitoring.
All tests again running on WM6 "V3 cabb'd III".
This set of tests is the following:
Test 1: GSM mode, backlight off, downloading for 5 minutes.
Test 2: UMTS mode, backlight off, downloading for 5 minutes.
The results vary and a pattern ive noticed is radio versions 1.47.30.10 and 1.54.30.10 seem to have the same behaviour in GSM modes, perhaps the extra ".30" in the version number denotes a particular tweak or feature??
Radio_Power_Tests_16012008.zip
Enjoy.
-------------------------------------
Inital test run:
Using a freshly flashed version of my "V3 cabb'd" ROM which is a tweaked version of pandora naked 6 3.60 ROM with nothing installed so a lean install and using acbPowerMeter I ran the following tests on each radio rom:
Test 1: Backlight off, automatic standby disabled, all processes stopped using start>settings>system>memory. GSM only and phone left on idle.
10 minutes and average current consumption recorded.
Test 2: Same as test 2 , UMTS only.
Ive taken a screenshot of the data with magicss and normalised the results so the earliest radio version tested is the baseline score.
The results of the first test are in the attached spreadsheet and screenshots.
Conclusions:
The results show that overall the differences are neglegable for these tests, however I still believe there is a major difference in practice. So the next load of tests I propose will test the power consumption with data connection attached. Somehow I want to test during a call or download since the HSDPA power consumption is likely to be a BIG number.
how comes you didnt test the latest radio versions? *waits for more results*
nice idea though
each test involves flashing a new radio (20 mins-ish) and two ten minute test runs...I need to use my Tytn today so can probably try the other radios later on, it takes a fair ammount of time for each one so i only went from the ground (1.43.00.00) to the one currently on my device (1.47.30.10) last night. I abandoned doing the later ones until ive figured out a worthwhile test to run for ALL versions. Ive presented my findings so far to show that essentially the 4 versions i tried are identical under idle conditions...not really a true to life test.
..big thanks to u bro! ..awesome work as usual..
mrvanx said:
each test involves flashing a new radio (20 mins-ish) and two ten minute test runs...I need to use my Tytn today so can probably try the other radios later on, it takes a fair ammount of time for each one so i only went from the ground (1.43.00.00) to the one currently on my device (1.47.30.10) last night. I abandoned doing the later ones until ive figured out a worthwhile test to run for ALL versions. Ive presented my findings so far to show that essentially the 4 versions i tried are identical under idle conditions...not really a true to life test.
Click to expand...
Click to collapse
Yeah, I think it will be the 3G call and HSDPA tests where the benefit of testing will be found.
My own tests show little difference in the idle power consumption.
I made very good experience with 1.41.00.10.
Good signal and low power consumption!
I've changed from 1.54 to 1.48 and I can honestly say my phone goes another day or two without charging!!!!!!!
Im gonna do some more tests tonight on the new format probably with some sort of download running (web n walk is usefull hehe).
So i'll post some more results later on if i can.
The best radio rom I've ever used
I tried many different radio roms for my Jasjam, believe me the best radio rom I've used regarding to power usage and signal is 1.46.00.11.
Even when using UMTS and 3G, in other radio roms; when connecting to internet with my laptop, I mean using Jasjam as access point to internet , the battery drains fast even if the Jasjam is connected to charger. but in this radio rom, when the charger is on, the battery stays stable and the Imate can also get charged. I know that this radio rom is designed for Trinity which is GPS enabled, but I am telling my experience. THANKS
For your testing goodness, here are pretty much all the radio roms I have ever come across.
http://www.crc.id.au/files/xda/Radio_Roms/
They are in .nb format - so you'll need to use Duttys tool to get them into .nbh files.
The power consumption is definately related to voice call usage.
My normal usage in a day means I use about 50 - 80% of my battery.
Whilst away in Tenerife I used my phone exactly the same but without making voice calls and I only used 50% after 3 -4 days.
This is certainly true. I was away in a place with no mobile coverage (no GSM or UTMS) and using the device for GPS navigation only I was able to get 2-3 full days out of the standard battery.
What is necessary to detect the correct battery consumption?
Something like this: http://www.vandenmuyzenberg.nl/PowerGuard/ ???
Should I use this tool?
matar said:
What is necessary to detect the correct battery consumption?
Something like this: http://www.vandenmuyzenberg.nl/PowerGuard/ ???
Should I use this tool?
Click to expand...
Click to collapse
Both threads you have posted in have shown you the program that is to be used. Why do you keep asking?
Starfury said:
The power consumption is definately related to voice call usage.
My normal usage in a day means I use about 50 - 80% of my battery.
Whilst away in Tenerife I used my phone exactly the same but without making voice calls and I only used 50% after 3 -4 days.
Click to expand...
Click to collapse
Experienced exactly the same thing when I was in Majorca. Even though I did use the phone a lot for sending as MMS (as that was free for me) I still got more usage out of the phone in Majorca if I had done pretty much the same usage pattern over here (UK) and that is because I suspect there transmitters put out a stronger signal, which means the phone has to 'work' less to get a stronger signal.
Starfury said:
Both threads you have posted in have shown you the program that is to be used. Why do you keep asking?
Click to expand...
Click to collapse
Sorry for double posting, but I read that those tools doesn't show the correct consumption because they needs power themselves and therefore distort the result... Maybe somebody can confirm this? Thank You.
A very good point. I've known the radio kicks up the power when you have a low signal, and if it's lost - I turn off the radio until I get back to a good area or it really kills the battery fast.
Just thinking here, but to add another level of complexity to the testing - while statically measuring power drain without moving the device will give repeatable results, could a radio power draw "react" differently to signal strength variations, and not be as "efficient" compared to others while on the move (typical usage)?
For example, if the signal goes above 50db (no idea if I'm even using the correct scale here ) it incrementally increases power by 20% for 10 seconds each until an "acceptable" signal level is reached. Once this is achieved, will it reduce back down - say you came around a building an now have a better signal? How long will that take? Will some radios respond more rapidly than others - optimizing power usage vs signal strength?
Dammit Matt! Now you've really got me thinking
In a bit of the background on this, the GSM/UTMS protocol allows the base station to tell the mobile to increase or decrease the transmit power of the phone. This allows it to tune the performance of the phones radio to get the optimum signal level at the cell site. It also helps a heap in deciding what cell towers to jump between and all the critical handoff levels and names.
Much more info can be found:
http://www.patentstorm.us/patents/5357513-description.html
There's a lovely paper about it all here - but I don't want to pay for it
http://www.actapress.com/PaperInfo.aspx?PaperID=18185&reason=500
power useage is down to lots of different factors, one of the main culprits is use of HSDPA/3G and it bounsing up and down between it and GSM when the local Cell doesnt support it or has a weak signal.
I can't believe the statement made above about the battery being used quicker when you talk, of course its going to drain quicker, its permanently transmitting for gods sake
It also depends on how strong the signal to the nearest cell/Base Station is, if its a week signal then the radio/phone will bounce around to find a stronger one, I believe typically a phone will register with up to 3 base stations to enable you to auto switch between cells when you move.
if you're really bored and want to dig into how GSM works heres a starter for 10
http://www.fci-cu.edu.eg/INFOS2005/presentation/GSM_Concepts.pdf
If you want to test weak signals stick your phone in a tin box, assuming this doesnt kill the signal totally then the phone should start ramping up its power output and sucking the battery dry quicker.
My point was made in reference to the testing of the phone to see what uses the most battery and indicating that we should direct our testing at the phone application over any others.
Now that the HTC One X has been out for a couple of weeks in both International (Asia / European) version and North American (Rogers, T-Mobile, AT&T) does anyone know the verdict on which version has the better battery life?
I suppose this would be heavily based on usage, but I've read some contradicting things.
The quad core processor (in the International version) is suppose to be good on battery, but I've also seen (both reports coming from Engadget) that the North American version seems to be a bit preferred (because of the LTE, despite the 12GB usable memory).
Can anyone speak on this, and maybe let me know which one seems to fair better battery life?
I use the camera a lot, I don't game on my phone, I listen to music a lot, and I like to text quite a lot.
LTE would be handy, but seeing as I'll also be traveling with my phone and won't see that functionality be useful abroad... I'd be (and currently am) happy with the International version in a Slate color, and in 32GB (26GB usable memory space) form.
I'm getting 8-10 hour days on my HOX International version. If anything, I'd be eying the Rogers HOX if I were looking to get a North American version.
I have the International Version and I seem to get very good battery life. It last all day. Im rooted and running a custom rom. I browse the website and use it all day long. Don't really stream movies or youtube but it will last me about 12 consistent hours. Although a lot of people are complaining about the battery I don't see the problem on my end. Hopefully that will help a little.
For now the S4 Krait version has better battery life. As stated in Anandtech's review, there will be an update available for the Tegra 3 version that they are currently reviewing that will sort this out. According to Nvidia, it's a software issue, so hopefully the update will improve battery life somewhat.
ArmedandDangerous said:
For now the S4 Krait version has better battery life. As stated in Anandtech's review, there will be an update available for the Tegra 3 version that they are currently reviewing that will sort this out. According to Nvidia, it's a software issue, so hopefully the update will improve battery life somewhat.
Click to expand...
Click to collapse
Yes, S4 Krait is 32nm, while Tegra 3 is 40nm, so the smaller it is the better battery life (but then there is LTE in S4 which I don't know how much will make it worse compared to non-LTE phone).
Tegra 3 - I don't have high hopes for battery life improvement fix, but we will see, I'd love to get it and have that "amazing battery life" advertized by nvidia reps.
I know they already announced Tegra 3+ for later this year which is 32nm so that should help with battery life.
The T3 version takes almost 0 power during standby, it's the power draw during light use that is causing the lower battery life compared to the S4 US version.
ArmedandDangerous said:
The T3 version takes almost 0 power during standby, it's the power draw during light use that is causing the lower battery life compared to the S4 US version.
Click to expand...
Click to collapse
Why is this the case?
Btw, you mean North American version. We Canadians had the phone launched first in North America.
Can anyone else speak on this query?
Maiesta_Miyabi said:
Why is this the case?
Btw, you mean North American version. We Canadians had the phone launched first in North America.
Can anyone else speak on this query?
Click to expand...
Click to collapse
My guess is something from Sense isn't playing nice with the Tegra chip. My phone doesn't seem to lose power in standby but when I start using it after substantial standby time the battery level plummets. This leads me to believe that despite the fact my phone says I'm not losing much juice while in standby, I'm actually losing a fair amount.
Sent from my HTC One X using xda premium
I'm getting 4.5 hours screen time with heavy use on the international version, auto brightness and 1.28 stock.
I consider this great considering the screen is a battery hog.
What sort of screen time is the S4 getting?
So it really comes down to the fact that SLCD2 is a power hog?
I'm wondering if I should just return the HOX and wait out for the S3.
But I do like the aesthetics, and camera on the HOX.
I've had the Note, and it has had a better battery life, plus a brighter LED flash.
But as I travel a lot with my phone, its starting not to make sense to have something that big with me.
Maiesta_Miyabi said:
So it really comes down to the fact that SLCD2 is a power hog?
I'm wondering if I should just return the HOX and wait out for the S3.
But I do like the aesthetics, and camera on the HOX.
I've had the Note, and it has had a better battery life, plus a brighter LED flash.
But as I travel a lot with my phone, its starting not to make sense to have something that big with me.
Click to expand...
Click to collapse
I made the same switch as you. I really miss the battery life from the Note, but the phone was just a bit too big. I'm really banking on HTC growing up and releasing the kernel source for the One X sooner rather than later. Once custom kernels start being built I'd be willing to bet we're going to see much improved battery life.
Sent from my HTC One X using xda premium
Maiesta_Miyabi said:
Why is this the case?
Btw, you mean North American version. We Canadians had the phone launched first in North America.
Can anyone else speak on this query?
Click to expand...
Click to collapse
I'm not sure whether the Canada version is the S4 or T3 version
On why it is so, it's not known yet but I read somewhere that Nvidia says its a software issue, so hopefully some kind of update will tweak some settings to lower power usage while on light usage
Hi All,
I'm thinking of getting a new phone at some point or another and the acro s seems perfect for me!
But I have a few questions before I waste my money,
The yellow tint issue - Does it still exist on newer devices? (I Know what Sony said but what do you lot say?)
Unlocking the BL - Do I lose any funtionality? Except for TrackID, Shazam is so much better Haha!
Battery life - Any complaints?
Thanks muchly in advance,
Actually BL Unlocking increase functionality a bit, since u have Custom ROM. But Bravia Engine and Track ID will be gone. Also there's a Warranty issue also
However upon Re-locking the BL, you may avail Track ID and BE again, but some were complaining that BE isn't working.
Battery Life is decent but it depends on you, But it should be fine for a day under normal use.
Some experienced Yellow Tint after a long time like 7-8 months and some almost immediately like within 3 weeks -1 month. But i think this problem occurred with first several units manufactured. New devices after that should not have this problem. Still check well before buying.
And Yes I think ACRO S is still in the New Phones league at lest up to December 2013. And don't know about SONY's support but in XDA there will be Devs alwz for this.
Savage thanks for the info!!
I have an Acro S since December 2012 and I gotta say this smartphone still kicks!
Green tint - No I don't have this issue, even if I full load the phone... straight 1 hour gaming... no
Unlock BL - I unlocked my bootloader 2 months ago and it was great, although I lost Bravia Engine and download music info services which I felt somehow bad... but the added functionality like flashing custom kernels/ROMs is just awesome! I love flashing custom kernels!
Battery life - Nope no complaints, should last a day (or even 1½ day) of normal use (like an hour of browsing, 1 hour of facebook, 1 hour of gaming/video... stuff like that)
Here are my complaints:
- Device gets hot so fast: In my opinion it's the Snapdragon S3 chipset inside our device, it's too old (2010 model), it has 45nm semiconductor technology which causes the heating I guess. Even if you're just browsing the net or doing facebook, device will get hot in about 10mins of use, but does not reduce performance. When gaming, when your device gets too hot (like 40 degrees celsius), it will slow down like a turtle, CPU clock will reduce down to 810MHz, if you're rooted you can prevent this by modifying a file, but I advice you to don't do this to prevent hardware damage/failure.
- Somewhat outdated chipset: Uses old 2010 Snapdragon S3, dual Scorpion cores on our device is good but Krait architecture is still A LOT BETTER, it beats Samsung's chipset on the Galaxy SIII, and of course does not overheat because of the 28nm manufacture process. About GPU, Adreno 220 runs smooth on our device, browsing and navigating around is buttery smooth, BUT is not powerful enough to power our 720p screen when it comes to heavy games, lags can be experienced in some famous games like GTA 3, Asphalt 7 (HORRIBLE LAG and ugly graphics for our device), Temple Run 2 (lags on Best graphics preset but doesn't on Better preset (although it still stutters which may disturb gameplay; but stil.... my highest was 22 million xD ).
That's all, Good Luck friend!
Hi,
I'm planning to buy LG G3 (32 GB version). It's very cheap right now considering it's specs but I have some questions before buying it.
1- How is general performance and gaming on stock ROM (lollipop or kitkat)?
2- Does it overheat or force the screen brightness to be lowered?
3- How is battery life (screen-on time) with moderate to heavy usage?
4- How is development going? Does it have stable AOSP ROMs without major issues or camera problems?
5- Are there any problems or any thing that I need to know before buying?
I would really appreciate it if some one can help me. Thanks in advance
1- I don't game
2- Overheat yes but it never forced me to lower the brightness
3- It's not bad, I can last 2 day with it
4- LG G3 camera is bad in every custom rom (unless you install the moto cam, or another (I don't remember witch one))
5- Overheat is the biggest downside for this device, I can go to 75C+ easily
75 c with general usage?! Does it affect perfermance or cause lagging?
Navios92 said:
75 c with general usage?! Does it affect perfermance or cause lagging?
Click to expand...
Click to collapse
The phone overheats but it isn't causing any performance or lag in my case. It is not getting up to 75. Also the gaming is very good. The battery gives me about 5+ hours of SoT.
Sreerag ag said:
The phone overheats but it isn't causing any performance or lag in my case. It is not getting up to 75. Also the gaming is very good. The battery gives me about 5+ hours of SoT.
Click to expand...
Click to collapse
On stock or custom rom? And what is your brightness settings?
Sent from my SM-G313HU using XDA Free mobile app
Navios92 said:
On stock or custom rom? And what is your brightness settings?
Sent from my SM-G313HU using XDA Free mobile app
Click to expand...
Click to collapse
On stock I got about 4+. Using custom ROMs like cloudy and exodus gives me much more. My brightness is at 50% auto.
Navios92 said:
Hi,
I'm planning to buy LG G3 (32 GB version). It's very cheap right now considering it's specs but I have some questions before buying it.
1- How is general performance and gaming on stock ROM (lollipop or kitkat)?
2- Does it overheat or force the screen brightness to be lowered?
3- How is battery life (screen-on time) with moderate to heavy usage?
4- How is development going? Does it have stable AOSP ROMs without major issues or camera problems?
5- Are there any problems or any thing that I need to know before buying?
I would really appreciate it if some one can help me. Thanks in advance
Click to expand...
Click to collapse
1) According to my experience, stock rom is a bit laggy, but absolutely tolerable.
If you flash an AOSP rom, lags should completely disappear, you can find the difference in heavier games.
But I can't compare the old KitKat rom to Lollipop one, since I immediately upgraded my device.
2) Yes, one of the worst problems of this phone is the overheating.
If you reach high temperatures (70 °C and above), device become to be laggy, as CPU need to be cooled by a process called "throttling".
On stock rom the maximum brightness is automatically decreased to 90%, or to 80% in very hot conditions, in AOSP roms brighteness is untouched.
3) It strongly depends by installed apps and mainly by the "damned" Google Play Services, which often cause a quicker battery drain.
During standby, the autonomy is excellent, during the utilization it's similar to the other devices, probably "a bit" longer.
4) The stock development is stopped to the February release (20H), but is also true that G3 was the first terminal to receive the Lollipop update.
On stock camera, 4K video recording is laggy, personally I prefer the excellent and smaller Full HD recording.
On AOSP roms (Resurrection Remix in my case) camera app is qualitatively comparable to the stock one... except for the audio quality in videos: volume become inexplicably lower and suffocated after some second of recording, it sounds me like a microphone which is turned off.
If you accept this issue (hope it will be solved) or you prefer to use a 3rd-party camera, I strongly suggest you to flash an AOSP rom, but be careful about rooting, if your intention is to immediately flash a custom rom, do not upgrade to Lollipop, or you'll have problems with "non-bumped" recoveries.
5) You have to know that G3 (according to many amateur crash videos) has a weak digitizer (so I suggest you to buy absolutely a proof cover like my Ringke Max).
Then... the already cited overheating, which would be a problem only for the laggy experience, no damage risks.
If you want to flash a custom rom, prevent to upgrade to Lollipop.
For the rest... you'll have a great device [emoji41]
I have found AOSP roms to be quite flakey, ive tried many of them and keep going back to stock - random reboots, crap battery etc.
Thermal throttling mod def helps with heat.
Simone98RC said:
2) Yes, one of the worst problems of this phone is the overheating.
If you reach high temperatures (70 °C and above), device become to be laggy, as CPU need to be cooled by a process called "throttling".
On stock rom the maximum brightness is automatically decreased to 90%, or to 80% in very hot conditions, in AOSP roms brighteness is untouched.
Click to expand...
Click to collapse
Honest question... do people actually use their devices at 100% or even 90? I currently have my G3 set to 67% and I never really change it. My Nexus 7 I keep at around the same unless I'm reading in bed and it's too bright, so I knock it down some. The only situation I could see using it at 100% would be in direct sunlight, but the glare makes this a bad idea in general.
Just curious I guess.
Simone98RC said:
1) According to my experience, stock rom is a bit laggy, but absolutely tolerable.
If you flash an AOSP rom, lags should completely disappear, you can find the difference in heavier games.
But I can't compare the old KitKat rom to Lollipop one, since I immediately upgraded my device.
2) Yes, one of the worst problems of this phone is the overheating.
If you reach high temperatures (70 °C and above), device become to be laggy, as CPU need to be cooled by a process called "throttling".
On stock rom the maximum brightness is automatically decreased to 90%, or to 80% in very hot conditions, in AOSP roms brighteness is untouched.
3) It strongly depends by installed apps and mainly by the "damned" Google Play Services, which often cause a quicker battery drain.
During standby, the autonomy is excellent, during the utilization it's similar to the other devices, probably "a bit" longer.
4) The stock development is stopped to the February release (20H), but is also true that G3 was the first terminal to receive the Lollipop update.
On stock camera, 4K video recording is laggy, personally I prefer the excellent and smaller Full HD recording.
On AOSP roms (Resurrection Remix in my case) camera app is qualitatively comparable to the stock one... except for the audio quality in videos: volume become inexplicably lower and suffocated after some second of recording, it sounds me like a microphone which is turned off.
If you accept this issue (hope it will be solved) or you prefer to use a 3rd-party camera, I strongly suggest you to flash an AOSP rom, but be careful about rooting, if your intention is to immediately flash a custom rom, do not upgrade to Lollipop, or you'll have problems with "non-bumped" recoveries.
5) You have to know that G3 (according to many amateur crash videos) has a weak digitizer (so I suggest you to buy absolutely a proof cover like my Ringke Max).
Then... the already cited overheating, which would be a problem only for the laggy experience, no damage risks.
If you want to flash a custom rom, prevent to upgrade to Lollipop.
For the rest... you'll have a great device [emoji41]
Click to expand...
Click to collapse
That was really helpful. Thanks alot.
I just have three more questions.
1- Does it reach 70c if I don't game?
2- Why shouldn't I upgrade to lollipop if I want to install custom ROMs? I've seen root method here for lollipop, what will be the problem exactly? And can't I just roll back to kitkat?
3- I've read some reviews saying that the screen is dim and has a low contrast ratio. Is it true? How does it compare to other LCDs like M8 and Z2 or the older G2?
Navios92 said:
That was really helpful. Thanks alot.
I just have three more questions.
1- Does it reach 70c if I don't game?
2- Why shouldn't I upgrade to lollipop if I want to install custom ROMs? I've seen root method here for lollipop, what will be the problem exactly? And can't I just roll back to kitkat?
3- I've read some reviews saying that the screen is dim and has a low contrast ratio. Is it true? How does it compare to other LCDs like M8 and Z2 or the older G2?
Click to expand...
Click to collapse
1. Yes it does. I get 70C while using facebook and similar apps within 15mins of usage. Still not too much lagg even with high temperatures.
2. You will probably be able to achive root on lollipop but the problem is the aboot(bootloader) that comes on lollipop. It's not compatible with bump that needs to be applied to recovery and boot partitions so you would recive Secure Boot Error.
Although you could use benders autorec app on lollipop which flashes kitkats aboot and laf imgs along with TWRP.
3. While I can't compare the screen with any of these phones as I have not used them, personally I don't have issues with my contrast. I can see things well under suns reflection as well.
Navios92 said:
That was really helpful. Thanks alot.
I just have three more questions.
1- Does it reach 70c if I don't game?
2- Why shouldn't I upgrade to lollipop if I want to install custom ROMs? I've seen root method here for lollipop, what will be the problem exactly? And can't I just roll back to kitkat?
3- I've read some reviews saying that the screen is dim and has a low contrast ratio. Is it true? How does it compare to other LCDs like M8 and Z2 or the older G2?
Click to expand...
Click to collapse
1) It may happens in every CPU stress condition, when device works at maximum clock (2.5 Ghz). Mostly in heavy games, but in other scenarios too, like continous switch between mobile data and Wi-Fi, or accidental screen on in pocket (which I encounter on my AOSP rom).
2) The Lollipop update enable the Secure Boot, which verify the signature of some critical partition of your device: if it find any inconsistency, the phone won't boot and send an alarming "blue-red" sequence of LED colours like a police light.
I've tried that on my device, I still get shivers!
Since you do the update, nor the downgrade to KitKat want to reverse the existence of Secure Boot, so you'll need to install only "bumped" recovery to prevent the issue.
It means that you have to manually flash TWRP recovery, since the standard "no-bumped" version will get your device in those terrible conditions.
3) I can't do a comparison since I'm not informed about these devices.
Personally for a long time I've disliked the "weak" colour intensity of G3, but after 6 months of experience I've understand that was the LCD of my old SGS3 to be abnormal, with a graceful but false contrast.
The real problem is not the contrast ratio, but the low brightness which you'll surely note in sunny conditions.
In the successor G4 the screen brightness is fixed by an increasing of almost 25%.
Simone98RC said:
1) It may happens in every CPU stress condition, when device works at maximum clock (2.5 Ghz). Mostly in heavy games, but in other scenarios too, like continous switch between mobile data and Wi-Fi, or accidental screen on in pocket (which I encounter on my AOSP rom).
2) The Lollipop update enable the Secure Boot, which verify the signature of some critical partition of your device: if it find any inconsistency, the phone won't boot and send an alarming "blue-red" sequence of LED colours like a police light.
I've tried that on my device, I still get shivers!
Since you do the update, nor the downgrade to KitKat want to reverse the existence of Secure Boot, so you'll need to install only "bumped" recovery to prevent the issue.
It means that you have to manually flash TWRP recovery, since the standard "no-bumped" version will get your device in those terrible conditions.
3) I can't do a comparison since I'm not informed about these devices.
Personally for a long time I've disliked the "weak" colour intensity of G3, but after 6 months of experience I've understand that was the LCD of my old SGS3 to be abnormal, with a graceful but false contrast.
The real problem is not the contrast ratio, but the low brightness which you'll surely note in sunny conditions.
In the successor G4 the screen brightness is fixed by an increasing of almost 25%.
Click to expand...
Click to collapse
Screen quality is very important to me as I watch a lot of videos.
But heating problem is a turn off. I live in a hot country and had the same problem with Optimus 4X which was unbearable.
I might wait till G4 price goes down and buy it or get A5 and wait for a proper flagship next year.
Does anybody else on the Android 12 V632 (probably also V732) firmware get lower performance than previously in 3D Mark etc.? It looks like GPU clocks are no longer locked to 840 MHz but instead drop below 840 all the times. Diablo Mode shows the same behavior for me. Rolling back to V420 and everything is locked again and performance as expected.