1. Nimm jetzt an unserem Uhans - 3. ADVENT - Gewinnspiel teil - Alle Informationen findest Du hier!

[KERNEL-ICS] franco.Kernel | [05 Juni - #Milestone 4] [NIGHTLY - 196]

Dieses Thema im Forum "Custom-Kernel für Galaxy Nexus" wurde erstellt von gknnn, 26.11.2011.

  1. gknnn, 26.11.2011 #1
    gknnn

    gknnn Threadstarter Android-Lexikon

    Beiträge:
    1,031
    Erhaltene Danke:
    480
    Registriert seit:
    09.01.2011
    franco.kernel


    franco.Kernel features:
    • THIS IS ONLY FOR 4.0.3 or 4.0.4. If you ask if it works on older roms I will shoot you
    • Overclock up to 1350mhz
    • Custom Voltage Control from Ezekeel
    • Completely updated CRC32 library that is used for a lot of core functionaties of the system
    • CFS scheduler tweaked for the best user experience
    • Stock GPU clock - reason(http://forum.xda-developers.com/show...postcount=4731)
    • CFQ I/O scheduler is default
    • CFQ I/O scheduler tweaked for flash devices and backported from 3.1
    • Ext4 tweaked and patched up for performance
    • I/O writeback backported from 3.2
    • SLQB memory allocator as default
    • USB HOST enabled
    • TUN enabled
    • ColorControl from Ezekeel
    • Command: echo "-10 0 -2" /sys/class/misc/colorcontrol/v1_offsets
    • this is just an example, values range between -255 and 255. If you want the values to stick on reboot create an init.d script or use my app
    • Hotplug mod added. Works independently of the governor. Shuts down cpu1 on screen_off and wakes it up again on screen_on
    • To disable: echo 0 > /sys/module/dsscomp/parameters/hotplug_enabled
    • To enable: echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled
    • Custom ramdisk included with proper ext4 mounts for performance
    • Kernel config stripped out from debug shit (only logcat and dmesg stayed)
    • A lot more stuff that can be seen on my repo
    • /sys/class/misc/colorcontrol/multiplier
    • color multiplier triple (default = factory settings; set with 'echo "2004318071 2004318071 2004318071" > multiplier' for example; if the safety is enabled the color multipliers cannot be raised above the factory settings)


    Downloads:
    Milestone 4 (stabile Version): Index of /franciscofranco/Galaxy Nexus
    Download Milestone 4 (stabile Version) bei World-of-Nexus
    Nightlies: Index of /franciscofranco/Galaxy Nexus/nightlies
    franco.Kernel updater app: https://market.android.com/details?id=com.franco.kernel
    franco.Kernel updater app from AndroidPit: franco.Kernel updater - Android Apps and Tests - AndroidPIT

    franco.Kernel updater app features:
    * Downloads the kernel directly from the ftp
    * Checks for updates directly from the ftp
    * Checks and downloads Imoseyon's kernel (new feature)
    * Kernel auto-flash
    * Cpu frequencies changer
    * Governor changer
    * Voltage control interface
    * Kernel settings:
    * Hotplug enabler
    * Color Control - You're able to change GAMMA values and Color Multipliers to achieve the best color profile
    * Sound Control - Increase the max volume of your device
    * Download special franco.Kernel boot animation
    * Wi-fi special mode to boost signal during streaming while on screen off
    * Custom download path
    * Live calibrated voltages panel
    * Disable logger
    * SQlite defrag on boot
    * Dedicated milestone and nightly kernels changelogs

    Source: https://bitbucket.org/franciscofranc...oid-tuna-omap/


    F.A.Q:
    1. My device rebooted or crashed, how can I help?
    A: Get me /proc/last_kmsg or logcat.
    2. Battery sucks, my device is not entering deep sleep. FIX PLOX!
    A: Fix it yourself, it's an app waking your device up not the kernel's problem
    3. Signal is dropping since I flashed the kernel, amg u sucks!
    A: The kernel has nothing to do with gsm/cmda signal. Make sure you have the latest radios
    4. Do I need to wipe anything when flashing this kernel?
    A: No.
    5. Does this kernel has X or Y mod?
    A: Learn to read, everything you need to know is in the features list, changelog or public repo.​
     
    Zuletzt bearbeitet: 01.07.2012
    picard782000 und boshot haben sich bedankt.
  2. gknnn, 26.11.2011 #2
    gknnn

    gknnn Threadstarter Android-Lexikon

    Beiträge:
    1,031
    Erhaltene Danke:
    480
    Registriert seit:
    09.01.2011
    Changelogs:

    Milestone Versionen:
    Code:
    [B]05.06.2012 -  Milestone 4[/B]
    [LIST]
    Changelog since Milestone 3
     Added 192Mhz slot
     Reverted all previous OMAP4 patches forked from Texas Instruments to fix most of the bugs coming from them
     Interactive governor patches from android-omap-3.0
     Screen_off_max_freq re-enabled and available here: /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq
     Lowmemorykiller driver updated to 3.4 version
     Fix for random mac id address for some users - from Imoseyon
     Special compiler flags to get some extra bits of performance
     Wi-Fi voltage back to stock to prevent signal issues
     Fix a crash present on stock kernel on i2c remove - patch from TI
     Remove generic_hotplug and Hotplug governor. The device shuts down cpu1 as it see fits so to prevent instabilities what so ever this function is now gone
     Fix to boosted sound when a notification was received - from Ezekeel
     Some OMAP4 patches from android-omap-3.0 for stability purposes
     Kernel 99% cleaned up from warnings that were present on stock kernel for stability purposes
     VDD_MIN voltage back to stock to prevent data loss or any other instability
     Add OMAP GAMMA interface - values range from 1.0 to 2.0 and are to be echoed to this file: /sys/devices/platform/omapdss/manager0/gamma
     Some MUSB patches from mainline kernel to improve battery life calling the correct pm_runtime functions on USB functions
     GPU clock is now 384Mhz by default because it can use the same amount of voltage and the same OPP as the 307Mhz giving us extra performance without taking a battery hit
     Other bunch of smaller patches and fixes that can be seen on my bitbucket repository
    
    [B]26.04.2012 -  Milestone 3[/B]
    [*]This is the perfected version of the last 35 days of testing of roughly 1 nightly build a day. The most important changes from Milestone 2 are:
    [*] Merged 4.0.4 kernel patches from Google (IMM76D and IMM76I)
    [*] Data dropouts is fixed
    [*] Interactive Governor patched up to be in line to android-3.0 branch
    [*] Hotplug governor added and tweaked for stability
    [*] Merged a lot of patches from omapzoom.org for battery and performance improvements in our OMAP4 board drivers
    [*] Hotplug_mod renamed to Generic Hotplug and changed paths to: /sys/module/omap2plus_cpufreq/parameters/generic_hotplug
    [*] Added BLX from Ezekeel. The default value is 96. Path: /sys/kernel/fast_charge/force_fast_charge
    [*] Reduced VAUX3 and VUSIM voltages for more screen_on time at the end of the day
    [*] Simple IO scheduler added and made default
    [*] EXT4 patches from 3.0.2X kernel.org patch
    [*] Lots of small tweaks and improvements that are available on my bitbucket git repository
    [/LIST]
    
    [B]19.03.12 - Milestone 2[/B]
    [LIST]
    [*]Frequency table re-worked to be fully multiple of 38,4 for perfect rounding
    [*]Stock GPU clock - stability is everything in the Milestone releases
    [*]Some Ondemand governor tweaks
    [*]Android OS consumption is much less
    [*]Screen on battery usage is much reduced
    [*]700mhz as minimum frequency is now removed - I don't want to force users to use an higher minimum frequency, everyone is free to choose what they like to use
    [*]Fix some higher IRQ load
    [*]Stock colors - no more blueish color
    [*]Added Sound Control from Ezekeel
    [*]Add PM_FAST/PM_MAX userspace module - this is a nice toggle that is helpful if you want to stream media during screen off. If thats the scenario PM_FAST will give you a smooth experience during streaming on screen off.
    [*]Lots of small tweaks and optimizations
    [/LIST]
    
    [B]05.03.12 - Milestone 1[/B]
    [LIST]
    [*]Volume hack value is set to 13 by default to provide a lot less hassle to everyone
    [*]USB fast charge from chad added
    [*]My config is now exported to /proc/config.gz - you can now build my kernel from my sources with my own config
    [*]Bye Memory Compaction shit - it's enabled by default and I don't see why we need it in this kind of devices
    [*]CIFS is gone too - according to nikademus explanation CIFS has a number of problems to us: if the device stays mounted somewhere it will kill your battery life to oblivion and two, it creates some extra memory footprint. I don't want any of that crap so CIFS is now removed and I won't probably add it again
    [*]Security exploit from /fs/proc/base.c is now fixed
    [*]Change ondemand up_threshold to 98 so it ramps up even less - more battery
    [*]Revert "Proportional Rate Reduction for TCP - by Google" - This is a milestone build so we can't afford having data losses or data instability
    [*]For everyone that tested nightly 19 this Milestone is exactly the same, but with stock GPU frequencies
    [/LIST]


    Nightly Versionen:
    Code:
    [B]r196[/B]
    * Remove 576Mhz entirely - it was causing some undesired instability
    * Add toggle to turn on/off fsync: echo Y > /sys/module/sync/parameters/fsync_enabled (it's disabled by default which means that enabled = less IO speed while having data integrity; disabled = more IO throughput but less data integrity)
    * Add morfics contrast interface. To change the value: echo X > /sys/module/panel-s6e8aa0/parameters/contrast (change X to the desired value; the default is -24 so don't cry if you think your device is too contrasted) 
    * Change some ramdisk tweaks for better end-user experience
    * Change BLX default value from 96 to 100 - this allows the users to use all range of 0-100 values for the BLX interface
    
    [B]r194[/B]
    * Add extra mV to 576Mhz step, it was too low on r192 causing some instability
    
    
    [B]r192[/B]
    * Fix support for slide2wake app
    * Add 576Mhz and 1651Mhz frequencies
    
    [B]r191[/B]
    * Revert CPUIDLE patch from Android team
    * Add ethernet interface support by user request
    * Add KALLYSMS_ALL for compatibility with one app
    * Tweaks and optimizations in the ramdisk
    
    [B]r190[/B]
    * Revert to stock Wi-Fi driver to fix high wlan_rx_wake wakelocks on some users and to fix Wi-Fi tethering using wpa and wpa2
    * Merged a patch for Interactive governor from TI that should boost interactivity and battery life using that governor
    [B]r189[/B]
    * Add CPUIDLE coupled state interface from Google Android team. This is for stability purposes so if you want to know what this is visit my repository and read the documentation
    * A little change from fugumod repository to decrease or even eliminate wlan_rx_wake wakelocks because of the noisy environment
    * A little config change - Wi-Fi tethering works now on my device with WPA2 security protocol
    
    [B]r186[/B]
    * Fix non-bootable kernel for some ToroPlus and other rare cases
    * Wi-Fi tethering fix attempt
    * Another Wi-Fi patch from android-omap-3.0
    
    [B]r185[/B]
    * New Wi-Fi driver from android-omap-3.0 repository - may contain bugs because it's around a 30 patches merge
    * Decreased a little bit the nominal voltages to accommodate the change to the smartreflex driver change for the 1.5Ghz and 1.4Ghz steps
    * SR now skips calibration if the nominal voltage is >= 1300mV instead of the previous 1350mV value
    * New toggle to disable thermal throttle: echo N > /sys/module/omap_temp_sensor/parameters/throttle_enabled (need testing on this, might or might not work as I can't achieve higher temperatures than 68ºC no matter what I do)
    * Small tweaks and optimizations - check repo
    
    
    [B]r181[/B]
    * Some stability fixes when using 1.536Ghz step
    * Add 1.420Ghz step for users that can't run higher
    
    [B]r180[/B]
    * Added 1.536Ghz CPU step
    * Enabled trim_override to make 1.536Ghz step usable without lagging
    * Added a routine check inspired from one of Imoseyon's commit for Smartreflex not to calibrate any step that uses nominal voltage above 1350mV (in this case only 1.536Ghz does)
    * Added Wheatley governor and made it default (been giving me awesome results) - from Ezekeel
    * Removed -fno-strict-aliasing flag from the Makefile (should give some extra bits of performance)
    * Add a static 5% overclock to the board (RAM/IVA/CORE) - GPU is not affected by this 5%
    * CPU hotplug routines patches from mainline kernel to improve stability
    * omap2plus-cpufreq driver improvements on screen on/off routines and also a little change from Linaro on the thermal_throttle driver initialization
    * Change wifi_pm type from int to bool (as suggested by morfic and it makes sense) to enable it echo Y > /sys/module/bcmdhd/parameters/wifi_pm - app will be updated with this until the end of today
    * Several OMAP patches individually picked for selected improvements - cpuidle driver/DSSCOMP driver (responsible for the display/graphics)/power management routines
    * Change exit_latency of C4 state to be faster (specially important now that we're using Wheatley that uses and abuses C4 state)
    * 1.536Ghz CPU frequency uses 1400mV voltage and it won't be calibrated by Smartreflex so be careful here. I tried to undervolt it on my app to 1350mV and my device crashed. You've been warned
    
    
    [B]r175[/B]
    * More changes to attempt to minimize the sudden data drops issues
    * For more information visit my repository, it's too technical to write here
    
    [B]r174[/B]
    * Another attempt to kill (or minimize at best) the recent surge of data losses
    
    [B]r173[/B]
    * OMAP Gamma settings works again
    * Color Multiplier won't turn the screen green if we set all the entries to >240 anymore
    * voltage.h: increase VDDMIN from 800mV to stock 830mV to reduce the chance of data loss
    * opp4xxx_data.c: add a new OPP core entry for OPP25 to fight the recent surge of data losses. Also increase 192mhz slot nominal voltage to 900mV from 820mV. Smartreflex still calibrates it to 840mV, but at least we're sure the data losses are not due to extreme nominal undervolt
    
    [B]r169[/B]
    * I present you the FIRST and only kernel for the Galaxy Nexus completely free of compiler warnings/errors - it's completely clean!
    * Added a fix from Ezekeel to fix the sound boost being reset when we receive a sound notification while listening to music
    * Added a fix found by Imoseyon to fix a long lasting bug in the stock kernel that random rebooted our devices in some rare cases - more information visit my repository
    
    [B]r166[/B]
    * Wi-fi voltage back to stock - this should fix the signal issues from the last builds because it seems this might be connection to some power rail related to the GSM/CDMA chip - thanks Greg for sharing your experience with me
    * GENTLE_FAIR_SLEEPERS by default
    * HID devices drivers added again to the kernel
    * A small OMAP patch to fix a bug in the DVFS interface
    
    
    [B]r165[/B]
    * OMAP patch to fix "SYNC_LOST" dmesg errors
    * Increase wi-fi voltage by another 0.25mV (I'll be increasing this until we find the sweet spot)
    * Revert "A patch to recalculate the loops_per_jiffy logic from TI"
    * A small patch from Google to fix a division by 0 if dhd_watchdog_ms is 0 on the wi-fi driver
    
    [B]r163[/B]
    * A patch to recalculate the loops_per_jiffy logic from TI
    * Tweaked CFS parameters from ch33kybutt - thanks for the research, they work wonders
    * Fixed false detection of IO wakeup event from TI
    * Some other small optimizations
    
    [B]r162[/B]
    * Fix USB bugs introduced on r161, specially losing ADB on screen off and some other perks that are now fixed
    * Corrected compiler flags
    * Removed generic_hotplug and hotplug governor for good as we don't need this anymore. The system does its power management by itself, including shutting down cpu1 during screen_off if it thinks its a good idea. (note to self: open my eyes when reading dmesg logs)
    
    [B] r161[/B]
    * Increased wi-fi voltage from 1.8V to 1.825V for stability purposes
    * Merged the latest init:calibrate.c changes from kernel 3.4
    * Attempt to fix USB tether not working for some users (I believe its a CM9 nightly issue, but nevertheless lets just make sure its not my derp)
    * Disable GENTLE_FAIR_SLEEPERS for testing purposes
    * Add back screen_off_max_freq sysfs entry. By default it caps at 729mhz on screen_off, but you can change it in this file /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq
    * Added special compiler flags for some extra bits of performance
    * OMAP4 DSS errata i733 workaround
    
    [B]r160[/B]
    * sched: Fix nohz load accounting -- again! - from 3.0.31
    * OMAP4: Workaround the OCP synchronisation issue with 32K synctimer. - reintroduced (I reverted it in r158)
    * 10 OMAP4 patches that were merged in android-omap-3.0
    * usb: musb: handle nuked ep dma interrupt
    * cpufreq: interactive: restart above_hispeed_delay at each hispeed load
    * cpufreq: interactive: fixup trace of string params
    * tuna-wifi: do not randomize MAC if bootloader doesn't pass it - patch from imoseyon
    * LMK pushed to 3.4 kernel version. Picked from Fugumod repository.
    * board-tuna.c: VAUX3 and VUSIM voltage increase a little bit to get rid of dmesg error logs
    * RCU Boost enabled again

     
    Zuletzt bearbeitet: 26.06.2012
    boshot bedankt sich.
  3. myx0r, 09.12.2011 #3
    myx0r

    myx0r Erfahrener Benutzer

    Beiträge:
    188
    Erhaltene Danke:
    25
    Registriert seit:
    14.12.2009
    Phone:
    Galaxy Nexus
    UPDATE:

    Changelog:

    9th December
    * Added two versions - one CPU/GPU OC free and another with CPU/GPU overclocked
    * Slightly undervolted
    * Add dynamic writeback feature from 3.1
    * block: strict rq_affinity
    * vmscan patched up with some fixes
    * arm: Allow CPU-supported unaligned accesses
    * Graphical glitch should be now fixed
     
  4. escrivel, 10.12.2011 #4
    escrivel

    escrivel Android-Experte

    Beiträge:
    894
    Erhaltene Danke:
    293
    Registriert seit:
    23.06.2011
    Phone:
    Nexus 6
    Ich werde noch etwas warten bis noch andere Kernel verfügbar sind! Kann jemand berichten ob sich etwas spürbar geändert hat im Gegensatz zum Stock Kernel?
     
  5. androidwissen, 10.12.2011 #5
    androidwissen

    androidwissen Android-Guru

    Beiträge:
    2,374
    Erhaltene Danke:
    463
    Registriert seit:
    20.03.2011
    Erfahungen wären mal nicht schlecht. Nutzt den denn niemand?
     
  6. agor, 10.12.2011 #6
    agor

    agor Android-Hilfe.de Mitglied

    Beiträge:
    48
    Erhaltene Danke:
    8
    Registriert seit:
    03.11.2011
    Ich teste ihn zur Zeit, mit der Version vom 9. Dec. hatte ich nach einiger Zeit dann Grafik glitches mit dem man das Telefon nichtmehr bedienen kann.
    Nun schaue ich wie es mit dem von heute läuft.

    Könnt es ja easy selber testen ohne zu flashen, einfach "fastboot boot boot.img" ;)

    Habe zudem noch die Voltages noch ein wenig weiter runter gesetzt
     
  7. erwi5, 10.12.2011 #7
    erwi5

    erwi5 Android-Experte

    Beiträge:
    537
    Erhaltene Danke:
    51
    Registriert seit:
    30.08.2010
    Phone:
    Oneplus 3
    Wearable:
    Huawei Watch
    Was heißt testen ohne zu flashen? Risikolos zum alten Kernel zurück möglich ohne Datenverlust? nach Neustart? Wie?
     
  8. agor, 10.12.2011 #8
    agor

    agor Android-Hilfe.de Mitglied

    Beiträge:
    48
    Erhaltene Danke:
    8
    Registriert seit:
    03.11.2011
    Bootloader muss natürlich unlocked sein, dann in den fastboot Modus und wie geschrieben
    "fastboot boot boot.img"

    Damit bootet er nur den Kernel, überschreibt nicht den in der /boot partition und nach Neustart ist alles weg. Besonders beim undervolten empfehlenswert zum testen, was möglich ist ;).
    Natürlich alles ohne gewehr :D
     
    Michael M. bedankt sich.
  9. Michael M., 11.12.2011 #9
    Michael M.

    Michael M. Android-Experte

    Beiträge:
    579
    Erhaltene Danke:
    69
    Registriert seit:
    13.07.2011
    Die Grafik glitches wurden gestern abend angegangen:

     
  10. agor, 11.12.2011 #10
    agor

    agor Android-Hilfe.de Mitglied

    Beiträge:
    48
    Erhaltene Danke:
    8
    Registriert seit:
    03.11.2011
    Habe nach ein paar Stunden immer noch das Problem dass Grafik Glitches kommen, lasse jetzt mal ohne laufen um zu checken obs evtl doch am ROM liegt.
     
  11. Punisher, 11.12.2011 #11
    Punisher

    Punisher Android-Experte

    Beiträge:
    869
    Erhaltene Danke:
    264
    Registriert seit:
    24.03.2011
    Hatte das Problem heute morgen auch zum ersten mal. Bilde mir ein das es davon kommt das ich bei Set CPU Display "Aus" 350mhz max gestellt hab. Auch einer dabei mit den Einstellungen?

    Gesendet mit der Android-Hilfe.de-App
     
  12. agor, 11.12.2011 #12
    agor

    agor Android-Hilfe.de Mitglied

    Beiträge:
    48
    Erhaltene Danke:
    8
    Registriert seit:
    03.11.2011
    Ne, sowas hatte ich nicht eingestellt. Nach der Nacht war auch immer noch alles in Ordnung, scheint also am Kernel zu liegen. Oder an der Kernel/ROM Kombi
     
  13. Punisher, 11.12.2011 #13
    Punisher

    Punisher Android-Experte

    Beiträge:
    869
    Erhaltene Danke:
    264
    Registriert seit:
    24.03.2011
    Welche Rom läuft bei dir? Ich hab die aktuelle Modaco drauf...
     
  14. Gis

    Gis Android-Hilfe.de Mitglied

    Beiträge:
    93
    Erhaltene Danke:
    10
    Registriert seit:
    17.11.2010
    Also mit der Version vom 9. hab ich auch die grafik probleme aussedem läuft er recht unrund. bin dann wieder zurück auf den 7. weil die bis jetzt am besten und stabilsten läuft. Hab ARHD drauf. 10 werd ich heut abend mal testen.
     
  15. agor, 11.12.2011 #15
    agor

    agor Android-Hilfe.de Mitglied

    Beiträge:
    48
    Erhaltene Danke:
    8
    Registriert seit:
    03.11.2011
    Hab auch die aktuelle MoDaCo @ Punisher
     
  16. agor, 12.12.2011 #16
    agor

    agor Android-Hilfe.de Mitglied

    Beiträge:
    48
    Erhaltene Danke:
    8
    Registriert seit:
    03.11.2011
    11th December
    * Around 10/15 Power Management patches from the Linux Mainline
    * USB HOST disabled as it was the cause of battery drain - more research when I have the device
    * Few reverts to make sure the graphic glitch was fixed

    Jmd schon probiert?
     
  17. boshot, 12.12.2011 #17
    boshot

    boshot Android-Guru

    Beiträge:
    3,462
    Erhaltene Danke:
    997
    Registriert seit:
    22.12.2010
    Jap hab ihn seit gestern drauf..
    Naja, drained immer noch mehr als der Stock :(

    Liegt wohl auch an irgendwelchen Bugs die im Logfile auffallen..
    (näheres dazu im xda Thread)

    Auch sonst seh ich nich den Wahnsinnsvorteil des Kernels gegenüber Stock.
     
  18. agor, 12.12.2011 #18
    agor

    agor Android-Hilfe.de Mitglied

    Beiträge:
    48
    Erhaltene Danke:
    8
    Registriert seit:
    03.11.2011
    Da hast du recht.. werde heute nachmittag mal den Stock Mod Kernel von faux123 in Verbindung mit dem Android Revolution HD Rom anschauen
     
  19. scimitar, 12.12.2011 #19
    scimitar

    scimitar Android-Experte

    Beiträge:
    754
    Erhaltene Danke:
    175
    Registriert seit:
    24.02.2010
    Phone:
    Mate 7
    Habe beide Versionen vom 10 und 11.12 getestet. Beide hatten einen sehr hohen Batterieverbrauch im StandBy. d.h. ca. 3-4% pro Stunde. Das ist leider zu viel. Ich bin zurück auf den StockKernel. Basissystem Android Revolution HD Rom1.3.2
     
  20. Grisu122, 14.12.2011 #20
    Grisu122

    Grisu122 Android-Hilfe.de Mitglied

    Beiträge:
    130
    Erhaltene Danke:
    7
    Registriert seit:
    18.08.2009
    Hat zufällig jemand einen Link zum Stock Kernel?
    Lg
     

Diese Seite empfehlen

Besucher kamen mit folgenden Begriffen auf unsere Seite:

  1. mod kernel ics