[KERNEL]TEMASEK ONLY CM10-10.1-10.2

TEMASEK KERNEL

ONLY CM 10-10.1-10.2





Chi usa le ROM AOSP, spesso va in contro al problema di trovare un KERNEL settabile secondo le proprio esigenge

Ecco il KERNEL che fa per voi

Grazie alľapplicaziond STweaks è possibile agire sui vari settaggi e configurarlo nel modo migliore alle esigenze del proprio terminale






More Info on Andreilux Charging Control

Anticipazione (Spoiler)

Directory
/sys/devices/platform/samsung-battery/

Charging Currents

Charging currents are dictated by input and charging current limits. The input current is the current flowing into the device through the USB port at 5V. The charging current is the current delivered to the battery at usually 4.35V. The device can have a higher charging current than input current because of the voltage differential, usually a 15% discrepancy. You can also have much higher input currents than charging currents, this can be useful when you are using the device in situations like gaming and charging your battery at the same time, provided your charger actually can provide the power.

There are 3 USB charger type categories

Dedicated Charging Ports (DCP)
- includes AC chargers, but also special USB plugs

dcp_ac_chrg_curr
- default 1000
- max 1200 (specification max is 1500)
- min 500

dcp_ac_input_curr
- default 1000
- max 1200 (specification max is 1500)
- min 500

Standard Downstream Ports (SDP)
- usually includes almost all data enabled USB ports

sdp_chrg_curr
- default 475
- max 900
- min 475

sdp_input_curr
- default 475
- max 900
- min 475

Charging Downstream Ports (CDP)
- includes also data enabled USB ports but which are designed to provide more power, usually on newer laptops where the USB port has a lightning logo next to it

cdp_chrg_curr
- default 1000
- max 1200 (specification max is 1500)
- min 500

cdp_input_curr
- default 1000
- max 1200 (specification max is 1500)
- min 500

Voltage control
- Hard voltage control: 4.20, 4.35V, and 4.40V charging voltages are available. This is included for anybody running on third-party batteries, whom most of them have a 3.7V battery chemistry as opposed to the 3.8V on the stock battery. These batteries should be charged at 4.2V instead of 4.35V.

batt_chrg_hard_volt
- default 4300000
- alternative value 4200000
- user can choose only either 4200000 or 4300000

- Soft voltage control: As opposed to the hard voltage control which is the voltage which the charger chip provides to the battery while charging, the soft-voltage is the battery voltage itself. 3.7V batteries have a top-off voltage of 4.2V and 3.8V again 4.35V. The default limit on the stock battery is 4.30V before the charger logic stops and considers the battery as full. This is also merely provided for 3rd party batteries which should be charged at lower voltages. If you overcharge your battery beyond these what are safe considered voltages, such as raising the default 4.30 top-off voltage to the design 4.35V or even higher, you are running into the risk of damaging the battery or even causing it to melt-down.

batt_chrg_soft_volt
- default 4300000
- alternative value 4200000
- user can choose only either 4200000 or 4300000

CHANGELOG

Anticipazione (Spoiler)

4 Apr 2013
040413-0910-cm-10.1-i9300-linaro-temasek.zip
040313-0916-cm10.1-i9300-linux3071-temasek.zip
- bcmdhd: squash updated bcmdhd stack from google
==> net: wireless: bcmdhd: Update to Version 1.28-27
- bcmdhd: reenable IPv6, disable multicast in suspend
- bcmdhd: disable GAN_LITE_NAT_KEEPALIVE_FILTER
- tmpfs: fix mempolicy object leaks
- kernel:sched: LOAD_FREQ (4*HZ+61) avoids loadavg Moire
- lib/lzo: Update LZO compression to current upstream version
- timer: optimize apply_slack()
- slub.c: little tweak for performance improvements
- usb-gadget: Booting from g_file_storage in cdrom mode
- Si47xx: properly free resources if failure to initialize
- usb gadget: update back to newest sources
- enable discard feature if emmc is 4.41+ Toshiba eMMC 19nm
- sdhci: deploy delay on host power down for all configs
- RTC and alarm changes
- usb: host and net related USB changes

Two versions, one compiled with linaro 4.6.2 toolchain & the other with cm default toolchain. Pls feedback which is better.

30 Mar 2013
300313-0745-cm10.1-i9300-linux3071-temasek.zip
- Updated to use Linaro GCC 4.7.3 20130226
- Update wifi config
==> DHD_USE_STATIC_BUF=y
==> DHD_USE_SCHED_SCAN=y
- Some misc config changes


150313-1122-cm10.1-i9300-linux3069-linaro462-temasek.zip
150313-1143-cm10.1-i9300-linux3069-default-temasek.zip
- Updated to linux 3.0.69
- usb gadget: update back to newest sources
- enable discard feature if emmc is 4.41+ Toshiba eMMC 19nm
- max77693-muic.c: misc changes
==> CONFIG_MUIC_MAX77693_SUPPORT_CAR_DOCK
==> CONFIG_MUIC_MAX77693_SUPPORT_OTG_AUDIO_DOCK
==> CONFIG_MUIC_MAX77693_SUPPORT_SMART_DOCK
- sdhci: deploy delay on host power down for all configs
- misc: modem changes
- RTC and alarm changes
- usb: host and net related USB changes
- media: MHL driver update
- keyboard-cypress: driver update

13 Mar 2013
130313-1756-cm10.1-i9300-linux3068-temasek.zip
- Compiled using linaro 4.6.2 toolchain
- Updated config.version for stweaks to enable the settings of Flexrate Settings in CPU Scaling section



10 Mar 2013
100313-0857-cm10.1-i9300-linux3068-temasek.zip
- Update on ROW IO scheduler
==> Device driver will be notified of an urgent request
* pending under the following conditions:
* 1. The driver and the current scheduler support urgent request handling
* 2. There is an urgent request pending in the scheduler
* 3. There isn't already an urgent request in flight, meaning previously
* notified urgent request completed (!q->notified_urgent)
- Deadline i/o scheduler - added morfic's 1:1 secret sauce
- Added optimized ARM RWSEM algorithm
- Staging: android: binder: Fix memory leak on thread/process exit
- hashtable: introduce a small and naive hashtable
- block,elevator: use new hashtable implementation

TEMASEK per CM 10.1
DOWNLOAD CENTER

http://temasek.hopto.org/?dir=Samsung Galaxy S3 - i9300/CM10.1/





TEMASEK per CM 10.2
DOWNLOAD CENTER
http://d-h.st/users/temasek/?fld_id=22184#files





ATTENZIONE
CHE NE IO NE IL FORUM SIAMO RESPONSABILI PER EVENTUALI DANNI AL VOSTRO DEVICE​

Thread Ufficiale XDA


Inviato dal mio GT-I9300 utilizzando Tapatalk