Jump to content

dfghggfgfd

Members
  • Content count

    39
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dfghggfgfd

  • Rank
    Newbie
  1. You need to reflash a stock firmware. Just download the Firmware of your choice and follow this instructions: http://forum.xda-developers.com/showthread.php?t=1093403 This procedure also won´t wipe your apps. BTW: As far as I know the problem with the OTA-updates is that they need the stock recovery to install properly. If you choose a rooting-procedure which just changes your kernel and leaves the recovery-partition alone, OTA-updates should work, but I don´t give you any guarantees. Obviously after an OTA-update root will be gone.
  2. Auto-Update currently won´t work with a rooted device, you have to unroot first, before you can install a auto-update.
  3. Simply turn your phone 180°. Landscape works in both directions, only portrait is limited to one direction.
  4. 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.
  5. dfghggfgfd

    Apps killed but still running?

    You don´t have to kill Apps on Android, the System does it for you, in fact this is counterproductive. Apps loaded in the memory don´t cause any harm and also don´t need any battery-power if they do nothing. The RAM-refresh is a hardware-circuit and the hardware doesn´t know which part of the RAM is "used" and which "unused", so it has to refresh the whole RAM. Therefore it is better to have something useful in the RAM instead of wasting much of it. The multitasking-paradigm of Android is to give the User the experience like all Apps are running constantly, so you can switch to any App without a noticeable delay. Obviously there is not enough RAM on a phone to really run every App at one time. But to get close to it, Android doesn´t really close your Apps until it is needed. This has 2 benefits: Reopening an App which is already in the RAM is faster, and this also means the App doesn´t need to be reloaded from the permanent storage, which saves energy. When you "exit" an Application it has to save its current state. This means, if you open a new Application, which needs more memory than currently available, the OS can immediately close one of the background-apps to free the memory for the new app. If you want to use the killed application again, its state is simply restored, so it appears to the user that it was never closed. You need a lot of processes to keep the phone running, so the phone can ring and answer calls when you get one, or simply receive a SMS, or to ring the alarm and show reminders from the calendar. There are also processes to run the GUI and many other things. These processes/apps will be reloaded if you force them to close to keep the phone running, otherwise the complete phone would crash. Reloading and restarting the processes of course will need some energy. If you force an application to close it also can not be guaranteed that the app already has saved its actual state, which can lead to problems with the particular app. Android also preloads often used applications to the RAM, so it will start faster when you actually use it. Constantly "cleaning" the RAM just means that Android will recognize a lot of free RAM and again preload applications, which again uses energy. So the bottom line is, don´t use any taskmanager/taskkillers or whatever, when you don´t need them. Let Android take care of the application-handling, it usually does it much smarter then any human could do. There is only one situation where a task-killer can be helpful. If an applications gets into an infinite loop it could constantly use CPU-cycles without doing anything useful. This of course will prevent the SoC from going in one of its low-power-states and can eat up your battery quite quickly. In this, and only in this situation it can be useful to kill the particular app that has gone mad. So the useful thing the taskmanagers can do is to monitor the current cpu-utilization. And if you notice an application to constantly use lots of CPU-power without doing anything you should kill it, and if it happens often with one application you should probably deinstall it.
  6. dfghggfgfd

    live wallpapers

    Live-Wallpaper won´t effect StandBy-time, where the screen is off anyway. How much it effects battery-life "in use" depends largely how you use the phone. If you spend most of the time with some applications in foreground it won´t influence the battery-life much. If you spend most of your time on the homescreens it surely will significantly effect battery-life. How much depends on the wallpaper itself, how complicated is the animation and most important what is actually shown. The phone uses an OLED-screen, so any bright background will significantly increase power-consumption compared to a black background.
  7. dfghggfgfd

    Power Off Timer

    You could have a simple "timer" by choosing the amount of music/video you want to listen/watch, and of course disable auto-repeat. Playing will stop after it reaches the end of your playlist or video. This doesn´t power off the phone, but this is not really necessary, you can switch the phone to Offline-mode when you go to sleep. A night in offline-mode is likely to draw less power then a complete booting of the phone.
  8. dfghggfgfd

    How long it takes to charge SGS2?

    If you only charge your phone, the power supply isn´t a real problem, finally [email protected] is enough to charge the battery in about 2h, well at least in theory. There are only 2 problems: The main problem might be, that you want to use your phone for something while it is charging. And the device can consume most of the power for the actual usage, so not much is left to charge the battery. A minor problem are the charging-characteristics of Li-Ion-cells. It is not possible to fully charge a Li-Ion-battery under 3h. Charging is divided in 2 stages. In the first stage charging should be done at about 0,5-1C. C in this case means the rated Capacity of the battery, so a 1,6Ah-cell should be charged with 0,8-1,6A This stage lasts until cell-voltage is about 4,2V With [email protected] the power-supply can only give about 0,8A @ 4,2V which is just the lower limit of the recommended charging-current. In reality it is a bit higher most of the time, as the voltage only tops at 4,2V. Cell-Voltage shouldn´t be under 3V, which is probably the limit where the phone switches off to prevent over-discharging. So during the first charging-stage from a completely flat battery voltage will rise from 3 to 4,2V and at 3V the power-supply can at least give about 1,3A. This first stage lasts from one (when charging with 1C) to two (when charging with 0,5C) hours. As the voltage rises quite linear, we can assume an average voltage of about 3,6V which means an average current of about 1,1A or 0,68C, so with the supplied power-adapter stage 1 (from a complete flat battery) must be at least 1,5h. But only if you are not using the phone at all. This will charge the battery to about 75-85% After this the charging-device switches into stage 2, also called the saturation-stage. In this stage the voltage remains constant at the set limit (usually about 4,2V) and the charging-current constantly drops. The saturation-stage lasts at least another 2h to get the missing 15% of charge into the battery. The conclusion is: Charging will get slower the higher the charging-level already is. In stage 1 because the voltage rises and the power-supply can not provide enough current, and if we are already in stage 2 because the battery can´t be charged any faster without risking damage. And using the phone during charging will significantly increase the charging-time significant.
  9. No, the phone won´t charge the battery anymore when it says full. Usually the battery is charged to 50% at least when you get it out of the package for 2 reasons. First the battery is tested during the quality-control after the manufacturing-process and to test the battery you have to charge it. And the worst thing you can do with a battery is to keep it somewhere completely discharged over a longer time. If the battery would lay on a shelf in a store for longer time without being charged first, the battery would be permanently damaged before the first usage, maybe even so much that it is unusable. Lithium-based batteries have a very low self-discharge-rate, so usually there will be quite a lot left of the factory-charge. Li-Ion-batteries usually need a few cycles to reach their full capacity, it doesn´t really matter if you do them with a few full charges and complete discharges or over time with some smaller charge/discharge-cycles, of course with the second option it may take somewhat longer to reach full capacity. Also the testing-procedure may have done a few cycles already, so it is possible that you reach the rated capacity pretty soon. There is not much you can do for a Li-Ion-battery to extend its life. They will wear out even if you don´t use them. The only thing you should avoid is a longer period of low charge and very high temperatures. It doesn´t matter if you use the phone until it switches off, the charging-electronic will prevent to discharge the battery so much that it causes damage, but the self-discharge may damage the battery. As I said, self-discharge is very low with Li-based batteries, so there is no hurry if your battery runs flat, it should be OK if you recharge it when you come home in the evening, just avoid longer periods in this state. There is no need to fully discharge the battery regularly, you can charge it anytime you want.
  10. dfghggfgfd

    Why does it go down to 90%

    You are saying the battery loses about 5% during one night? This seems pretty good to me, losing 5% in about a half day would mean 10 days of Standby-usage, which sounds really good. My old N900 lost about 10% a night, with all data-connections off, and 20% when it was online.
  11. dfghggfgfd

    Battery Issue

    First of all look what is consuming all your battery. I don´t know how accurate this is, but it is at least a hint. There seems to be bug in Android 2.3.3, where "Android-System" consumes a lot of power in Standby. This doesn´t happen to every device, nor all the time. Until there is a 2.3.4-update (which apparently fixes the problem) the only thing you can do is rebooting the phone. Your phone should work normally for a while, until Android-System again drains your battery. As Android-System in the power-consumption-view is essential a summery of all (non-kernel) system-related processes it is hard to tell what the exact problem is, but it seems that some hardware-driver fails going into Standby and Android constantly tries to shut it down. This prevents that the SoC can go to sleep-state.
  12. dfghggfgfd

    How long it takes to charge SGS2?

    The supplied charger is rated 700mA only, which isn´t that much more than the 500mA from USB (900mA with USB 3.0, although I´m not sure if the phone uses that). I´m using my old Nokia power-adapter, which can give 1,2A and is much faster than USB or the supplied charger.
  13. You can switch between your active languages by holding the space-bar and dragging left or right. You can also switch off the voice-recognition-button in the settings, to make the space-bar a bit bigger.
  14. dfghggfgfd

    Poor WiFi abilities

    Try to hold the phone so you don´t block the lower part (where the backside "bumps" out). At least according to the manual the antennas are supposed to be there.
  15. dfghggfgfd

    Exynos or Tegra 2

    As far as I know, no Galaxy S2 devices with Tegra2 have been shipped until now. You can easily differentiate the 2 models by the model-number, exynos is I9100, Tegra 2 is I9103. The CPUs are 2 Cortex-A9 processors in both cases, but Exynos uses the NEON SIMD-extenstions, Tegra doesn´t. The SIMD-extensions could be useful for multimedia-spplications. Tegra 2 officially only supports 1080p with main-profile, I know the Galaxy S2 with Exynos can play High-Profile videos in 1080p. I don´t know if the missing NEON-extensions are responsible for it, but more likely it is the video-processor. I also don´t know if Samsung maybe still can do something in Software to support 1080p-HP on Tegra2. On the other hand the Geforce ULP in the Tegra2 seems to be more powerful than the Mali-400 in the Exynos. There are also rumors the Tegra-version won´t use a AMOLED, but a LCD instead. So from the outside Tegra seems to be the better gaming-device, Exynos the better multimedia-device. I don´t think you will see much difference in performance, the most obvious difference might be the probably different display.
×

Important Information

By using this site, you agree to our Terms of Use.