Galaxo 1.6.3.3 Bugs & Some Solutions


Last Updated:

  1. cobragti

    cobragti New Member This Topic's Starter

    Joined:
    Mar 27, 2010
    Messages:
    4
    Likes Received:
    1
    Hi Folks,

    At first ,thanks to whom participate for the development of galaxo images & all the work you have done... (firmwares)..

    I have installed my 128 mb :) galaxy i7500 galaxo 1.6.3 ( with new patch)

    I see some lags between switching programs and wait close apps messages..

    I think everyone see such mesegase...

    I tried to use beutiful widgets or some other widgets but my processing power gets high (also battery usage) and force close messages are make me nuts.

    But then I thing it must related to ram issues (after copilot usage) becouse we have limitted ram.. my firend have a hero and she uses copilot faster like google maps... :)

    So I installed root required memory programs like autokiller & minfreemanager.. and readjust memory values...


    I make

    Foreground 8 mb
    Visible App 10
    Secondary server 12
    Hidden app 24
    Content Provider 26
    Empty app 24


    when I make this changes my app launcher and other programs works faster than before and the transitions are better much better than before and less force closes...


    I write it becouse I am very happy now... & just kind of information for the pros ...


    Also I found problems ( no widgets or apps running behind) looking from System pannel monitoring is off


    - Auto Brightness option doesn't work after restart (stays same)
    - when Orientation option is selected the battery consumption is more or much more (maybe calculation)
    - when the Bluetooth wifi and gps options are seleceted (means open) battery consuption or calculation is less than close...
    - Bluetooth stereo has problems... buttons play pause not working stable
    - Wifi doesn't connect after disconnected for a while... (screen policy set to when screen turns off)

    Also advanced launcher is buggy ..

    if drakaz can install adw launcher .... I am very happy ( also we can able to update it from market) becouse if i use it or other launchers dial pad contact list comes later or take time...

    Android keybord don't have Turkish characters like Ş,Ğ, I, ş, ğ, ı if it's possible it is very good for us to have...

    Thank you ...



    Sorry for my English..
     

    Advertisement
  2. cobragti

    cobragti New Member This Topic's Starter

    Joined:
    Mar 27, 2010
    Messages:
    4
    Likes Received:
    1
    Android : memory thresholds

    http://www.drakaz.com/2010/04/30/android-memory-thresholds/

    Memory thresholds, what is it ?
    It’s the threshold from which the device will kill some process, to free memory.
    On Android, there is two memory threshold : system (/sys/module/lowmemorykiller/parameters/minfree) and dalvik (*_MEM properties).
    System thresholds looks at unix free memory.
    Dalvik thresholds looks at virtual free memory, in dalvik.
    Thresholds
    FOREGROUND_APP_MEM : below this threshold, internal task killer will kill foreground applications
    VISIBLE_APP_MEM : belowthis threshold, internal task killer will kill second plan applications
    SECONDARY_SERVER_MEM : below this thresholds, internal task killer will kill daemon applications
    HOME_APP_MEM : below this thresholds, internal task killer will kill the home
    HIDDEN_APP_MEM : below this thresholds, internal task killer will kill unvisible applications
    CONTENT_PROVIDER_MEM : below this thresholds, internal task killer will kill unvisible content provider
    EMPTY_APP_MEM : below this thresholds, internal task killer will kill ghosts application
    Exemples
    Low FOREGROUND_APP_MEM = kill active application when running internal task killer
    High EMPTY_APP_MEM = kill all useless applications
    Low HIDDEN_APP_MEM = don’t kill all application in memory = fast to re-open (but use more battery)
    High HIDDEN_APP_MEM = kill all applications, nice for battery (but applications remains slow to open)
    ect..
    Why i haven’t got any FC using a very high threshold on the 3 last parameters ?
    A FC happen when a process ask for unavaible ressources. When you kill all application in backgroun, there isn’t any application asking for ressources = no FC.
    Conclusion
    Very high threshold is useless, they must be set regarding the device ressources.
    Very low threshold provide faster reopening, but use a little more battery (not because of used ram, but because some app are running in background).
    Remember that those kind of unix device are made for keeping app in memory. Will you kill all the process runing on your laptop to save battery ? The task killer is here to kill useless app, not all. But, if killing all the application preserve some battery…why not. Battery is saved by killing CPU’s consumer, not just freeing memory.

    http://www.drakaz.com/2010/04/30/android-memory-thresholds/
     
  3. MichaelW

    MichaelW Well-Known Member

    Joined:
    Oct 6, 2009
    Messages:
    364
    Likes Received:
    26
    What are the stock Samsung settings?
     
  4. cobragti

    cobragti New Member This Topic's Starter

    Joined:
    Mar 27, 2010
    Messages:
    4
    Likes Received:
    1
    System defaults are:

    Foreground 6 mb
    Visible App 8
    Secondary server 10
    Hidden app 24
    Content Provider 30
    Empty app 45

    but it can be wrong :)
     
    MichaelW likes this.

Share This Page

Loading...