Jump to content


Photo

Android 2.3.4 Firmware leaked i9100XXKG1

- - - - -

  • Please log in to reply
8 replies to this topic

#1
Breit

Breit

    Newbie

  • Members
  • Pip
  • 45 posts
  • Location:Germany
  • Devices:Samsung Galaxy S II GT-I9100
  • Twitter:@McBreit
samfirmware.com got the news (as always): http://www.samfirmwa...or-galaxy-s-ii-

:blink:

firmware code is: i9100XXKG1 with Multi CSC.
download-link: http://hotfile.com/d...0XXKG1.rar.html

...downloading as we speak!

Edited by Breit, 09 July 2011 - 01:20 AM.

  • 0

#2
NZtechfreak

NZtechfreak

    Regular

  • Members
  • PipPip
  • 87 posts
  • Devices:Samsung Galaxy SII

samfirmware.com got the news (as always): http://www.samfirmwa...or-galaxy-s-ii-

:blink:

firmware code is: i9100XXKG1 with Multi CSC.
download-link: http://hotfile.com/d...0XXKG1.rar.html

...downloading as we speak!


I've been on it about 8 hours (went for Darkys, its just stock, but no wipe involved). Seems largely the same, except in silent/vibrate modes the camera shutter sound is off (sounds like a job for Tasker!), can take pictures <15% battery without flash, google video chat is there.

  • 0

#3
amitsharma.atc

amitsharma.atc

    Diehard

  • Members
  • PipPipPipPip
  • 351 posts
  • Gender:Male
  • Devices:omnia, galaxy tab & galaxy s2

I've been on it about 8 hours (went for Darkys, its just stock, but no wipe involved). Seems largely the same, except in silent/vibrate modes the camera shutter sound is off (sounds like a job for Tasker!), can take pictures <15% battery without flash, google video chat is there.


could you plz explain its advantage over last 2.3.3 rom
like...
battery improvements
lock screen lag prob and any other improvement
any new apps
thanks

  • 0

#4
Breit

Breit

    Newbie

  • Members
  • Pip
  • 45 posts
  • Location:Germany
  • Devices:Samsung Galaxy S II GT-I9100
  • Twitter:@McBreit
lock screen lag issues should be resolved, at least for the homescreen-button unlock (not sure about power-button unlock)...
unfortunately its to early to tell if the android os bug is resolved, this will need some time with regular usage and not constantly fiddling around installing and configuring all the stuff... :blink:

  • 0

#5
guy.user

guy.user

    Newbie

  • Members
  • Pip
  • 47 posts

lock screen lag issues should be resolved, at least for the homescreen-button unlock (not sure about power-button unlock)...
unfortunately its to early to tell if the android os bug is resolved, this will need some time with regular usage and not constantly fiddling around installing and configuring all the stuff... :blink:


I never had any AOS "bug" issue. My Android OS battery consumption is always around 10%.....I'm still on KF3 now.

  • 0

#6
Breit

Breit

    Newbie

  • Members
  • Pip
  • 45 posts
  • Location:Germany
  • Devices:Samsung Galaxy S II GT-I9100
  • Twitter:@McBreit

I never had any AOS "bug" issue. My Android OS battery consumption is always around 10%.....I'm still on KF3 now.


This is the 'Android OS Bug' on KF3 on my SGS2: ~16h since full charge with ~1:45h runtime fpr 'Android OS' (47% battery). I guess you are just lucky... :blink:

Attached Files


  • 0

#7
NZtechfreak

NZtechfreak

    Regular

  • Members
  • PipPip
  • 87 posts
  • Devices:Samsung Galaxy SII

This is the 'Android OS Bug' on KF3 on my SGS2: ~16h since full charge with ~1:45h runtime fpr 'Android OS' (47% battery). I guess you are just lucky... :blink:


Doesn't look like the Android OS bug to me at all - the AOS bug isn't just about having high AOS usage, its about having high battery drain also. The AOS usage with16hrs battery, including nearly two hours screen on and about 40-50% battery remaining, is utterly irrelevant.

  • 0

#8
Pentiboy

Pentiboy

    Newbie

  • Members
  • Pip
  • 9 posts
I just got an OTA update, but it did not do anything, it only made two empty spaces in my applications menu....

Can this be some sort of pre-release for 2.3.4?

Edited by Pentiboy, 12 July 2011 - 01:29 PM.

  • 0

#9
dfghggfgfd

dfghggfgfd

    Newbie

  • Members
  • Pip
  • 39 posts

This is the 'Android OS Bug' on KF3 on my SGS2: ~16h since full charge with ~1:45h runtime fpr 'Android OS' (47% battery). I guess you are just lucky... :blink:

This is not the "Android-OS"-Bug, with this bug your battery would be almost flat after 17h without using the phone at all.

You used the phone for almost 2h and still have about half the battery left, which is depending on your usage, quite normal.

When the screen must display mostly white and is on high brightness you can expect a maximum of about 4h screen-usage.




I think "battery-usage-meter" is somewhat incorrect as well, and so confusing people if the really have the famous "bug" or not.

There are different types of people that claim to have the bug.

First the ones, who really have the bug, they can barely use the phone half a day without recharging (even if they don´t actually use it)

Second the ones, who get confused by the high relative percentage of the "Android OS" in their battery-usage-statistics, without actually having that much battery-use at all.




I bought my phone with KE2-firmware, which always showed very low usage of Android-OS. Especially noticeable was that Andoid-OS almost always showed less usage than Android-System.

Now I´m on KF3, which shows quite high battery-usage from Android-OS, when I´m not doing anything with the phone. Android-System on the other hand is very low. It is still quite confusing, as you expect cell-standby to use most of the power when you don´t do anything with your phone.

I also noticed some difference in actual battery-usage, but not nearly as bad as the quite high percentages from Android-OS might suggest. 10h of Standby used about 2-3% of battery on KE2, now on KF3 it is more like 4-5% (although last night it also used only about 2% in 10h).

The only difference I noticed, is that WiFi connects much faster with KF3, despite using the same policy (sleep when screen off).

With KE2 it took a few seconds until WiFi was connected when I was waking up the phone. Now with KF3 it connects almost instant to WiFi, after waking up the phone. It also seems to me, that the timeout to actually disable WiFi after locking the phone is longer.

So this might explain the slightly higher Standby-usage.




I don´t know what exactly counts to "Android OS", "Android System" and also some other packages.

Maybe Samsung moves around some processes between Android-System and Android OS, or even puts some processes in the Android-OS package, which rather should have their own.

So in the end a lot of things count up to Android-OS, resulting in a very high relative percentage, yet with a pretty normal battery-usage.




Some really have this Android OS-bug, but most like you are only confused by the (maybe inaccurate) battery-statistics.

You certainly don´t have the bug, just look how flat your battery-graph is, when the phone is actually in standby.








Edited by dfghggfgfd, 14 July 2011 - 08:15 AM.

  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users