İletişim


 Android indir


admin@444android.com


admin@444android.com

×

Selamun Aleykum Arkadaslar, Ne yazik ki cok az sayida Turk developerlarimiz var. bu yuzden az da olsa size ***** araciligi ile birkaç sey ogretmeye calisacagim. Ilk *****muz Nelerin gerektigi hakkinda olacaktir. (Modifye etmek icin) ve ayniz zamanda ornek olarak da Statusbar transparantligini anlatiyorum :) Bir istek arzunuz olursa soyleyin, zamanim oldugunda onuda gostermeye/ogretmeye calisirim. Haydi Bismillah.

Bu konu 13734 kez görüntülendi 37 yorum aldı ...
【T U T O R I A L 】 ★ DroidTurK ★ ---- Development! 13734 Reviews

    Konuyu değerlendir: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    5 üzerinden | Toplam: 0 kişi oyladı ve 13734 kez incelendi.

  1. #11
    AskinSavascisi - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    06.07.2013
    Nereden
    Belçika
    Mesajlar
    662
    @AskinSavascisi

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    facebook müşteri hizmetleri
    teknoloji destek
    PART 3 MODUL:



    Modul icinde kernel ile alakali bircok KOD bulunduran bir objektir. Modul'un cesitli amacli vardir bunlardan birtanesini yeni hardware'e destek. Buyuk bir ihtimal , kernelinizin icine yeni bir modul yerlestirdiginizde, kucuk olsa bazi Errorlar verecektir (benim aromada Kernel error checking'i hatirlayin). AZ daha olsa bu hatalar performansinizi dusmesine sebep olacaktir.

    Modullerinizi /lib/modules klasorunuzun icinde bula bilirsiniz. (uzanti olarak .ko sahiptir yani kernel object)

    Modul'u Yerlestirmek icin Kodlar
    Code:

    insmod /lib/modules/module-name.ko

    Bu cumleyi/sirayi init.d scriptinizin icine koyarak, modul'un her bootda yeniden kurulmasina sebep olacaksiniz.

    Default, kendiliginden olan modullerin listesini istiyorsaniz bu comand'i yazin:Code:

    lsmod

    Bir Modul'u silmek icin (Eger kendiniz birtane eklediyseniz!):Code:

    rmmod "modulename"

    1) bthid.ko* - BlueTooth Human Interface Device

    Signifies: Bluetooth
    Bthid is one of the bluetooth profiles. The module provides support for devices such as bluetooth mice, joysticks,keyboards,etc. It uses a low latency link with low power requirement to achieve the above mentioned.

    2) cifs.ko - Common Internet File System

    Signifies: Network Share
    Successor to the SMB (Server Message Block) protocol, this protocol is supported by windows servers, samba, etc. The module is responsible for managing your network shares. It is used to mount/unmount network file resources on to your device. If special characters are not properly read/displayed, download and use nls_utf8.ko module for UTF-8 character support.

    3) fuse.ko* - File System in Userspace

    Signifies: File System
    The module let the users create own filesystems without editing kernel code. Fuse module act as a bridge between filesystem code running in the userspace and kernel interface. The module is often used in our devices to support ntfs/ntfs-3g filesystem for mounting ntfs formatted hard drives and pen drives.

    4) cuse.ko - Character Devices in User Space

    Signifies: Audio Proxying
    CUSE is an extension of FUSE allowing character devices to be implemented in userspace. One of the prime motivation for developing cuse is to provide a better support for Open Sound System or OSS. Except for initialization sequence and creation of character device instead of a mount, CUSE isn't very different from FUSE. CUSE is used for tasks like proxying OSS audio from OSS apps to an audio system.

    5) dhd.ko - Dongle Host Driver

    Signifies: Wifi
    This module (from broadcom) is the wifi kernel module/wireless driver, and is responsible for wifi tethering, and such.

    6) ftdi_sio.ko - Future Technology Devices International - Serial I/O

    Signifies: USB Serial Devices
    The module is required to connect an embedded device to our device using FTDI USB-serial converter. The embedded device will be an ftdi chipset based device. Devices like an USB-RFID reader could be connected.

    7) usbserial.ko - USB Serial

    Signifies: USB Serial Modems
    This module is often used along with ftdi_sio module. It is the usbserial-generic interface for linux platform. The module is used to detect and use devices such as usb serial modems.

    8) gspca_main.ko - GSPCA Main Driver

    Signifies: Webcams
    This module is used to install gspca based web camera in our device. The module is the driver that's responsible for detecting and functioning of gspca based webcams.

    9) hfs.ko - Hierarchical File System

    Signifies: Mac Filesystem
    This module is the driver to support HFS aka Mac OS Standard file system. Try mount -t hfs "/source" "/destination" to mount. Also give USB Mass Storage Watcher App from market a try, to skip commands and mount via GUI.

    10) hfsplus.ko - Hierarchical File System Plus

    Signifies: Mac Filesystem
    This module acts as the driver for HFS+ aka Mac OS Extended file system. HFS+ is one of the formats found in iPods. Use mount -t hfsplus "/source" "/destination" for mounting drives.

    11) j4fs.ko* - Jong Jang Jintae Jongmin File System

    Signifies: File System
    J4fs is a filesystem based on LFS (Linear File Store). The bootlogo and some misc files in our device, mounted in /mnt/.lfs is formatted as j4fs filesystem by default.
    Please do not mess with .lfs folder!

    12) ld9040_voodoo.ko* - LD9040 AMOLED Driver

    Signifies: Voodoo Color
    Module/driver for voodoo color/screen tuning support for our device. Let's wait patiently until supercurio comes out with a legendary app to have full control on our amoled display.

    13) scsi_wait_scan.ko - Small Computer System Interface Wait Scan

    Signifies: Waiting During Booting
    scsi_scan_wait is responsible to wait until all the asynchronous scans are complete. It will wait after all root SCSI drivers have finished scanning their busses. Note that use of this module can increase your bootup time.

    14) Si4709_driver.ko* - Si4709 FM Radio Driver

    Signifies: FM Radio
    Si4709 is the fm radio receiver driver. Module is loaded by default by Siyah. If there are issues with fm radio in aosp roms, try inserting this module.

    15) vibrator.ko* - Vibrate Sensation on Touchsense

    Signifies: Haptic feedback
    This module from immersion corporation is responsible for haptic feedback. It senses touch as a request and sends back vibration as response. Try inserting this module if haptic feedback not working on aosp roms.

    16) logger.ko - Logger for Android

    Signifies: Logging/Debugging
    Loggers are used to log records to a variety of destinations such as log files or the console. Install this module to enable logging, if logging is disabled in your kernel by default. Logging is used to generate logcats (for debugging purpose), dmesgs (message buffer of the kernel), for proper functioning of app protectors, etc.

    17) mc1n2_voodoo.ko - mc1n2 Voodoo Sound Driver

    Signifies: Voodoo Sound
    Module/driver for Exynos Yamaha audio hardware tweaks. Provides sysfs interface for HP gain and Aout. This driver provides support for supercurio's Voodoo Louder app.

    18-25) cpufreq_ brazilianwax.ko, cpufreq_ interactive.ko, cpufreq_ interactivex.ko, cpufreq_ lazy.ko, ondemandX.ko, cpufreq_ powersave.ko, cpufreq_ savagedzen.ko, cpufreq_ userspace.ko

    Insert these module(s) to avail your favorite governor which are not loaded by default.

    *Modules preloaded in Siyah by default.


    Q&A

    Q. "I can not find a module that i need to use with the current release of my kernel. Can i use the module downloaded from internet?"
    A. Module should be binary compatible with the kernel version. So even if the module was one that came with an older version of the kernel, it's probable that the compatibility is lost.

    Q. "I feel there could be some advantage if i remove modules which is no use for me, but they're loaded by kernel during boot-up. What can i do?"
    A. Put "rmmod name-of-module" in one of your init.d script, so that it's uninstalled on every boot-up. After booting if you need to use the module, you can insmod it. Ex: rmmod Si4709_driver.ko. (If you don't use FM radio)



  2. #12
    AskinSavascisi - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    06.07.2013
    Nereden
    Belçika
    Mesajlar
    662
    @AskinSavascisi

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    PART 4 I/O SCHEDULER:



    Q. "What purposes does an i/o scheduler serve?"
    A.
    • Minimize hard disk seek latency.
    • Prioritize I/O requests from processes.
    • Allocate disk bandwidth for running processes.
    • Guarantee that certain requests will be served before a deadline.


    So in the simplest of simplest form: Kernel controls the disk access using I/O Scheduler.

    Q. "What goals every I/O scheduler tries to balance?"
    A.
    • Fairness (let every process have its share of the access to disk)
    • Performance (try to serve requests close to current disk head position first, because seeking there is fastest)
    • Real-time (guarantee that a request is serviced in a given time)


    Q. "Description, advantages, disadvantages of each I/O Scheduler?"
    A.

    1) Noop

    Inserts all the incoming I/O requests to a First In First Out queue and implements request merging. Best used with storage devices that does not depend on mechanical movement to access data (yes, like our flash drives). Advantage here is that flash drives does not require reordering of multiple I/O requests unlike in normal hard drives.

    Advantages:
    • Serves I/O requests with least number of cpu cycles. (Battery friendly?)
    • Best for flash drives since there is no seeking penalty.
    • Good throughput on db systems.

    Disadvantages:
    • Reduction in number of cpu cycles used is proportional to drop in performance.


    2) Deadline

    Goal is to minimize I/O latency or starvation of a request. The same is achieved by round robin policy to be fair among multiple I/O requests. Five queues are aggressively used to reorder incoming requests.

    Advantages:
    • Nearly a real time scheduler.
    • Excels in reducing latency of any given single I/O.
    • Best scheduler for database access and queries.
    • Bandwidth requirement of a process - what percentage of CPU it needs, is easily calculated.
    • Like noop, a good scheduler for solid state/flash drives.

    Disadvantages:
    • When system is overloaded, set of processes that may miss deadline is largely unpredictable.


    3) CFQ

    Completely Fair Queuing scheduler maintains a scalable per-process I/O queue and attempts to distribute the available I/O bandwidth equally among all I/O requests. Each per-process queue contains synchronous requests from processes. Time slice allocated for each queue depends on the priority of the 'parent' process. V2 of CFQ has some fixes which solves process' i/o starvation and some small backward seeks in the hope of improving responsiveness.

    Advantages:
    • Considered to deliver a balanced i/o performance.
    • Easiest to tune.
    • Excels on multiprocessor systems.
    • Best database system performance after deadline.

    Disadvantages:
    • Some users report media scanning takes longest to complete using CFQ. This could be because of the property that since the bandwidth is equally distributed to all i/o operations during boot-up, media scanning is not given any special priority.
    • Jitter (worst-case-delay) exhibited can sometimes be high, because of the number of tasks competing for the disk.


    4) BFQ

    Instead of time slices allocation by CFQ, BFQ assigns budgets. Disk is granted to an active process until it's budget (number of sectors) expires. BFQ assigns high budgets to non-read tasks. Budget assigned to a process varies over time as a function of it's behavior.

    Advantages:
    • Believed to be very good for usb data transfer rate.
    • Believed to be the best scheduler for HD ***** recording and ***** streaming. (because of less jitter as compared to CFQ and others)
    • Considered an accurate i/o scheduler.
    • Achieves about 30% more throughput than CFQ on most workloads.

    Disadvantages:
    • Not the best scheduler for benchmarking.
    • Higher budget assigned to a process can affect interactivity and increased latency.


    5) SIO

    Simple I/O scheduler aims to keep minimum overhead to achieve low latency to serve I/O requests. No priority quesues concepts, but only basic merging. Sio is a mix between noop & deadline. No reordering or sorting of requests.

    Advantages:
    • Simple, so reliable.
    • Minimized starvation of requests.

    Disadvantages:
    • Slow random-read speeds on flash drives, compared to other schedulers.
    • Sequential-read speeds on flash drives also not so good.


    6) V(R)

    Unlike other schedulers, synchronous and asynchronous requests are not treated separately, instead a deadline is imposed for fairness. The next request to be served is based on it's distance from last request.

    Advantages:
    • May be best for benchmarking because at the peak of it's 'form' VR performs best.

    I/O Schedulers


    Disadvantages:
    • Performance fluctuation results in below-average performance at times.
    • Least reliable/most unstable.


    7) Anticipatory

    Based on two facts
    i) Disk seeks are really slow.
    ii) Write operations can happen whenever, but there is always some process waiting for read operation.

    So anticipatory prioritize read operations over write. It anticipates synchronous read operations.

    Advantages:
    • Read requests from processes are never starved.
    • As good as noop for read-performance on flash drives.

    Disadvantages:
    • 'Guess works' might not be always reliable.
    • Reduced write-performance on high performance disks.


    Q. "Best I/O Scheduler?"
    A.There is nothing called "best" i/o scheduler. Depending on your usage environment and tasks/apps been run, use different schedulers. That's the best i can suggest.
    However, considering the overall performance, battery, reliability and low latency, it is believed that
    SIO > Noop > Deadline > VR > BFQ > CFQ, given all schedulers are tweaked and the storage used is a flash device.

    Q. "How do i change I/O schedulers?"
    Voltage Control or No Frills from market.
    Or init.d script:
    echo "scheduler-name" > /sys/block/mmcblk0/queue/scheduler

  3. #13
    AskinSavascisi - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    06.07.2013
    Nereden
    Belçika
    Mesajlar
    662
    @AskinSavascisi

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    PART 5. DUAL CORE CPU Soru&Cevap Ve TWEAKLER







    Q&A on parameters and factors that control the performance, throughput and battery-life delivered by GS2's dual-core CPU, and some CPU tweaks

    Q. "What is the basic hardware of GS2 that make all of us enjoy this phone so much and boast about benchmark scores to office-mates and friends?"
    A.
    Processor: ARM Cortex-A9 MPCore processor on Exynos 4210 SoC (System on a Chip - ICs where all components are integrated into a single chip) and 45nm semi-conductor technology. Exynos 4210 is supposed to give 6.4GB/s memory bandwidth for heavy-weight ops such as full hd ***** encoding.
    GPU: ARM Mali-400
    Memory: LPDDR2 (may be DDR3)

    Q. "What is the significance of bus frequency?"
    A. Bus speed at its simplest form determines how fast the data should travel to and from memory. Memory throughput is directly proportional to bus frequency. In tasks that includes small amount of work on every element in a data sets, lower bus speed means longer the CPU has to wait for data to arrive from memory. Because, CPU spends only little time on each of these elements, and a slow bus cannot catch-up.
    Advanced Micro-controller Bus Architecture (AMBA) is used as the on-chip bus in system-on-a-chip designs, like our device.

    Q. "What is modifying bus frequency? How do I do it? Advantages?"
    A. Stock behavior is dynamic bus frequency scaling, where in operating bus speed is dynamically calculated for each CPU frequency depending on the application/process’s requirement. We can modify this behavior by setting static bus frequency scaling, specifying at what bus speed should each CPU frequency operate. Three values/levels are possible.
    0 – 400 mhz
    1 – 266 mhz
    2 – 133 mhz

    Sample bus frequency modification:
    echo "0 0 0 1 1 1 2 2" > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static
    echo "enabled" > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static

    This means for first three higher CPU frequency steps, 400 mhz bus will be used.
    Next three, 266 mhz
    And last two, 133 mhz

    Advantages of bus frequency modification: i) Saves battery by using low bus speeds on low frequencies and ii) Prevent overheating.

    Q. "I experience some lags sometimes while playing HD *****s or playing heavy 3d games using static bus frequencies. Why?"
    A. HD *****s and some games require a minimum of 400/266 mhz bus irrespective of the CPU frequencies being used during the run. To resolve, set higer bus for 500 mhz and higher frequencies or simply disable static bus frequency scaling to switch to default.
    echo "disabled" > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static

    Q. "Our phone CPU has two cores. How are they utilized? Are the two cores ON all the time?"
    A. The stock behavior is Dynamic Hot Plug Mode where depending on the load, the second core is turned on. If the load can be handled by a single core, the second core is turned off dynamically. This behavior can be controlled by using Tegrak Second Core app from market if your kernel supports it. (Siyah, Lulz,etc supports this). Using this app you can set three modes :-
    Dynamic Hot Plug Mode: Default mode. Second core is kicked in depending on the load, and kicked out when first core can handle the load alone.
    Single Core Mode: Irrespective of the load, only first core is used always. This can lead to increased battery, but reduced performance.
    Dual Core Mode: Irrespective of low loads, both the cores are always active. Increased performance, but reduced battery.

    Recommendation: Use the stock hotplug mode during normal use. Switch to dual core mode only for benchmarking or playing some heavy 3d games.

    Q. "OK, I'm using hot plug mode, still i want to control how often the second core kicks in. To make it more aggressive/more mild depending on my usage."
    A. You can set UP & LOW thresholds for second core in Screen-On and Screen-Off states.
    Examples:
    echo "70" > /sys/module/pm_hotplug/parameters/loadh
    echo "25" > /sys/module/pm_hotplug/parameters/loadl
    echo "90" > /sys/module/pm_hotplug/parameters/loadh_scroff
    echo "35" > /sys/module/pm_hotplug/parameters/loadl_scroff

    As you can see, when load > 70% second core becomes active and when load drops below 25%, second core is turned off.
    During screen off, these values are 90 & 35 respectively. This helps in reducing unwanted kick-ins of second during screen-off state when music is playing, downloading, etc.

    Q. "Like governors, is there a sampling rate/interval also at which the load on CPU is checked for crossing thresholds to turn second core ON?"
    A. Yes there is. But it is set at kernel level in most kernels and can not be controlled at user level. Like you guessed, higher sampling rate could cause core 2 to kick in less often and thus save a little battery. In Siyah kernel though, these thresholds are configurable.

    Q. "Advantages/Disadvantages of switching to Single Core/Dual Core modes?
    A. Using only single core can save some battery, but can have some adverse effects too if there are some heavy tasks that require both cores too often: 3d games, full hd *****s, etc. So use it wisely.
    Using dual core mode can reduce latency by a tiny bit on high loads, as compared to hot plugging. But hot plugging is intelligent enough to turn second core ON really fast when load demands it. Only first core (cpu0) can enter deep-idle (LPA), so using dual core mode in an idle system cause unwanted excess-power consumption.
    Recommendation: Use Hot Plugging and tune thresholds (like mentioned above) for a better experience.

    Q. "What are these modes: IDLE, LPA and AFTR?"
    A. Between screen off and deep sleep states, there are some idle modes supported by cpuidle driver. They are IDLE aka Normal Idle, LPA aka Deep Idle and AFTR aka ARM Off Top Running. Race to idle by CPU is implemented for power management.

    In IDLE state, CPU is not clocked anymore, but no hardware is powered down.

    In deep idle (LPA),a state after IDLE, again, the cpu is not clocked anymore like we guessed but some parts of hardware are powered down. Deep idle brings in real power savings and there is no need of putting a hard limit to frequency during screen-off; using a screen-off profile. (Good practice is to use a governor with built in screen off profile, than using an user-configured screen-off profile by putting a hard limit on frequency). Deep idle is not used when device is entering deep sleep and also when device is woken from suspend/deep sleep. While entering/exiting DEEP IDLE, CPU is set statically to SLEEP_FREQ and is not clocked below or above until it exits this state.

    AFTR is a patch to support Top=Off mode for deep idle. Level 2 cache keeps it data during this mode.

    We can have IDLE or AFTR modes with LPA enabled or disabled. (Obviously it is not possible to have IDLE and AFTR together)
    Values:
    0: IDLE
    1: AFTR
    2: IDLE+LPA
    3: AFTR+LPA

    Q. "What idle modes are recommended for power saving? How do i change it"?
    A. Recommended for power saving is to enable AFTR and LPA, ie value 3
    Example:
    echo "3" > /sys/module/cpuidle/parameters/enable_mask

    Q. "What is sched_mc?"
    A. Linaro team invented sched_mc or Schedule Multi Core to make process scheduling multi-core aware. ie, utilize both cores wisely to save power and balance performance. Even though sched_mc is sort of an alternative to cpu hot plugging, we can use sched_mc with the default hot plug mode.

    Possible Values:
    0 : No power saving load balance, default in our exynos4210 Soc.
    1 : Fill one thread/core/package first for long running threads. In our single-CPU dual-core device, multithreading does not come into picture, so load balancing is almost redundant to hotplugging.
    2 : Also bias task wake-ups to semi-idle CPU package for power savings. (Bias new tasks to cpu1 if cpu0 is mostly filled with running tasks). This is 'overloading' CPU0 first.

    Q. "What value is recommended for sched_mc?"
    A. 1) If you find advantages to sched_mc, use sched_mc=1 for a possible battery saving. Anyhow since load-balancing is reduntant on hotplugging, it may not have any advantage on exynos chip.
    2) For performance use 2. But do remember that loading CPU0 and leaving CPU1 can not do justice to hitting deep idle states sooner since second core can not enter deep idle. So extra performance or no performance, value 2 will drain some more battery, in the context of delayed didle.
    3) To do justice to hotplugging, use value 0.
    Example:
    echo "0" /sys/devices/system/cpu/sched_mc_power_savings.

    Q. "What is MALI aggressive policy on GPU?"
    A. Mali aggressive scaling policy is simply lowering the up-threshold of GPU so that GPU doesn't jump to second frequency step too often. This makes more sense if lower step is under-clocked. In one release of Siyah, the threshold was changed to 55 from default 65.

    Q. "What is tree rcu, fast nohz, jrcu?"
    A. Read-Copy Update (RCU) is a synchronization mechanism added to Linux kernel. RCU improves scalability by allowing readers to execute concurrently with writers.

    Tree RCU is a new implementation of original classic RCU to achieve more scalability as the number of CPUs increase. Tree RCU fixes a performance bug in classic RCU that results in massive lock contention on the internal RCU lock on systems with large number of CPUs.

    Fast NoHz is an optimized version of the traditional Tree RCU. Many new kernels are using the Tickless NoHz design. This RCU is tailored and designed to work with the new NoHz kernel system.

    JRCU mechanism in its simplest form, runs batch operations from a single CPU relieving other CPUs from this periodic responsibility. This is important for those real-time applications requiring full use of dedicated CPUs. For our dual core single CPU, JRCU can conflict with hot-plugging, hence we will have tree rcu (with or without CONFIG_RCU_FAST_NO_HZ) in our kernels.

    Q. "What are SLAB, SLUB, SLQB?"
    A. They're three memory allocation mechanisms.

    Slab allocation is a memory management mechanism intended for the efficient memory allocation of kernel objects which displays the desirable property of eliminating fragmentation caused by allocations and de-allocations. SLAB is used to retain allocated memory that contains a data object of a certain type for reuse upon subsequent allocations of objects of the same type.

    SLUB allocator promises better performance and scalability by dropping most of the queues and related overhead and simplifying the slab structure in general, while retaining the current slab allocator interface. SLUB offers to make alignment of objects and cleaning up of caches easier, as compared to SLAB.

    SLQB - SLAB allocator with Queue. This is a slab allocator that focuses on per-CPU scaling. This memory allocator is designed for small number of CPUs system. This allocator is designed to be simple.

    Note that SLUB is significant on a system with large number of CPUs. SLAB has the advantage of being simple.

    Q. "Can i change the RCU synchronization mechanism & memory allocators?"
    A. NO. They are set at compile time at kernel level, and are not configurable from user space.

  4. #14

    Üyelik tarihi
    18.04.2013
    Nereden
    istanbul
    Mesajlar
    387
    @alpikk

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    Süper olmuş gerçekten,teşekkürler

  5. #15
    AskinSavascisi - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    06.07.2013
    Nereden
    Belçika
    Mesajlar
    662
    @AskinSavascisi

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    Alıntı alpikk Nickli Üyeden Alıntı
    Süper olmuş gerçekten,teşekkürler
    Umarim bir faydasi dokunur xD

    Verstuurd van mijn GT-N7100 met Tapatalk
    http://www.wolftech.xyz

    Webdesign | PC - Tablet - Smartphone repair



    furkey
    Nickli Üyeden Alıntı

    sen varya eli öpülecek adamsın ha :D


    Nejat Nickli Üyeden Alıntı
    "tutorial hacı " olarak yeni nick mi versek arkadaşa

  6. #16
    FatihA - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    22.07.2012
    Nereden
    Batman-Kayseri
    Yaş
    37
    Mesajlar
    10.888
    @FatihA

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    Ben anlamadım

    tapatalk
    ESKİ NICK'im ankebut2

    Hanzala Yüzünü Dönmeyecek;
    KUDÜS Özgür Olana Dek....



  7. #17
    AskinSavascisi - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    06.07.2013
    Nereden
    Belçika
    Mesajlar
    662
    @AskinSavascisi

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    Alıntı ankebut2 Nickli Üyeden Alıntı
    Ben anlamadım

    tapatalk
    Neyi anlamadin?

    Verstuurd van mijn GT-N7100 met Tapatalk
    http://www.wolftech.xyz

    Webdesign | PC - Tablet - Smartphone repair



    furkey
    Nickli Üyeden Alıntı

    sen varya eli öpülecek adamsın ha :D


    Nejat Nickli Üyeden Alıntı
    "tutorial hacı " olarak yeni nick mi versek arkadaşa

  8. #18
    FatihA - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    22.07.2012
    Nereden
    Batman-Kayseri
    Yaş
    37
    Mesajlar
    10.888
    @FatihA

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    Hiç bir şeyi.yabancı dil sıfır da bende.

    Tapatalk
    ESKİ NICK'im ankebut2

    Hanzala Yüzünü Dönmeyecek;
    KUDÜS Özgür Olana Dek....



  9. #19
    AskinSavascisi - ait Kullanıcı Resmi (Avatar)
    Üyelik tarihi
    06.07.2013
    Nereden
    Belçika
    Mesajlar
    662
    @AskinSavascisi

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    Alıntı ankebut2 Nickli Üyeden Alıntı
    Hiç bir şeyi.yabancı dil sıfır da bende.

    Tapatalk
    Ben orda turkce anlatiyorum??

    Verstuurd van mijn GT-N7100 met Tapatalk
    http://www.wolftech.xyz

    Webdesign | PC - Tablet - Smartphone repair



    furkey
    Nickli Üyeden Alıntı

    sen varya eli öpülecek adamsın ha :D


    Nejat Nickli Üyeden Alıntı
    "tutorial hacı " olarak yeni nick mi versek arkadaşa

  10. #20

    Üyelik tarihi
    12.03.2012
    Nereden
    Ankara-Zonguldak
    Mesajlar
    255
    @furkey

    Cevap: 【T U T O R I A L 】 ★ DroidTurK ★ ---- Development!

    sen varya eli öpülecek adamsın ha

Yetkileriniz

  • Konu Acma Yetkiniz Yok
  • Cevap Yazma Yetkiniz Yok
  • Eklenti Yükleme Yetkiniz Yok
  • Mesajınızı Değiştirme Yetkiniz Yok
  •  

Giriş

Facebook Baglan Giriş