Samsung Galaxy Note II - [N7100 N7105] Perseus

[Smokey Skull 19]

https://forum.xda-developers.com/showpost.php?p=35410521&postcount=1151

[andreas02 1.338]

Update auf v28.2

Post 1 ergänzt

LG

Andreas

[andreas02 1.338]

Update

Perseus alpha29 (18/12):

I'm doing a quick release because of the security fix, not very feature rich.

Fixes the exynos-mem security hole. This is my own fix and will not break camera. Read about it here. You don't need to use Chainfire's or Supercurio's fixes, in fact, you shouldn't use them because of the camera.

Updated Wifi drivers.

Increased max brightness by 50 candela. (Thanks nebkat)

Added GPU utilization control to sysfs and STweaks.

Changed default GPU thresholds to more relaxed values (75/17)

Added block device read-ahead control to STweaks. Additionally set the default read-ahead for internal memory to 256kB and 1mB for SD cards.

Post 1 ergänzt

LG

Andreas

[Guest Don Hugo alt]

Keine Ahnung wieso, aber mein Telefon wollte nach dem flashen nicht mehr starten. Habe dann den alten Kernel geflasht, danach ging es wieder.

Gesendet von meinem GT-N7100 mit Tapatalk 2

[andreas02 1.338]

Update auf v29.1

Downloadlinks ergänzt

LG

Andreas

[Smokey Skull 19]

Perseus alpha29 (18/12):

I'm doing a quick release because of the security fix, not very feature rich.

Fixes the exynos-mem security hole. This is my own fix and will not break camera. Read about it here. You don't need to use Chainfire's or Supercurio's fixes, in fact, you shouldn't use them because of the camera.

Updated Wifi drivers.

Increased max brightness by 50 candela. (Thanks nebkat)

Added GPU utilization control to sysfs and STweaks.

Changed default GPU thresholds to more relaxed values (75/17)

Added block device read-ahead control to STweaks. Additionally set the default read-ahead for internal memory to 256kB and 1mB for SD cards.

29.1: - Reverted the Wifi drivers back.

[andreas02 1.338]

Danke für die Info. War ich wohl zu schnell...aber

DAS ist auch neu

Updated Wifi drivers. zurückgenommen.

LG

Andreas

[andreas02 1.338]

Update

Changelog

Perseus alpha30 (06/01):

Internal and memory voltage control. This is the first and only working implementation out there. Memory interface voltage is exactly what it the name implies, the voltage on the chip-to-chip interface from the SoC to the memory chip. Internal voltage is the whole SoC voltage excluding CPU, GPU, and the MIF. This includes all auxiliary function blocks such as the ISP/Image signal processor, camera interfaces, I/O interfaces, display controller and the MFC/Multi function codec hardware video de-/en-coder.

- Internal voltage respectively memory voltage table is found in /sys/devices/cpu/busfreq/ as int_volt_table or mif_volt_table

- The frequencies are defined as OPP's (Operating performance points), internal frequency and memory frequency (And voltages) together as a pair form an OPP. If you want to change the voltages through the sysfs files, keep in mind how you change them. MIF voltages are stored independently with each OPP step. INT voltages are stored in respect of their frequency key.

- Default OPP steps are: 440220, 293220, 293176, 176176, 147147, 110110. The first three numbers represent the memory frequency, the other three the internal base frequency. For example 293220 means the memory interface is at 293MHz (586MHz DDR) and the internal frequency is 220MHz.

- The voltages in STweaks are sorted out through some magic and are frequency unique, I recommend using that for controlling them.

Busfreq logic control added into STweaks, this includes all the already available configurables in the stock kernel with added explanations and I supplemented it with a sampling rate parameter.

Sensorhub driver and firmware updated.

Touchscreen driver and firmware updated.

Replaced pegasusq's runqueue detection logic with a new more superiror and precise in-scheduler collection logic, I found that the real runqueues are much less than what was previously reported. This should help a lot with hotplugging.

Enabled AFTR by default since we are now running very often in single-core mode. Keep in mind this mode is WFI Idle + LPA + AFTR.

Fixed a kernel bug which was eating up randomness entropy. This is related to that whole seeder business - please don't use any of those fixes. I also disabled virtual addresss randomization and at the same time disabled entropy generation from the block layer, which should avoid I/O overheads.

I raised the LPA CPU idle target residency, and fixed a bug in the ABB control for voltages for 900 and 1000MHz. I suspect these two to be causes of the sudden reboots for Note 2 users, and may fix them.

Post 1 ergänzt

LG

Andreas

[DakiX 36]

Der aktuellste läuft wirklich sehr gut. Hier meine Einstellungen mit der App STweaks:

ACHTUNG: Da jede CPU anderst ist kann diese Einstellung einen Reboot hervorrufen und deshalb NIE ,,Set on boot'' aktivieren! Für Schäden und Co. seid Ihr selber verantwortlich.

CPU

MAX FREQUENCY, 1200MHz

MIN FREQUENCY, 200MHz

Undervolting:

200MHz, 837500

300MHz, 837500

400MHz, 850000

500MHz, 850000

600MHz, 850000

700MHz, 887500

800MHz, 912500

900MHz, 975000

1000MHz, 987500

1100MHz, 100000

1200MHz, 102500

CPU SCALING

Governor: pegasusq

SAMPLING RATE: 28000

UP THRESHOLD 81%

FREQUENCY FOR FAST DOWN, 1000MHz

CPU HOTPLUG

CPU UP RATE: 19 SAMPLES

HOTPLUG FREQ FROM 1 CORE TO ONLINE: 600MHz

HOTPLUG FREQ FROM 3 CORES TO OFFLINE: 400MHz

MEMORY/INTERNAL

INTERNAL VOLTAGE: 176MHz STEP, 950000

MEMORY VOLTAGE: 440MHz STEP, 1000000

GPU

UP THRESHOLD: 75%

DOWN DIFFERENTIAL: 17%

GPU VOLTAGE CONTROL:

160MHz, 925

266MHz, 925

350MHz, 975

440MHz, 1025

533MHz, 1125

I/O

INTERNAL STORAGE SCHEDULER: SIO

SD CARD SCHEDULER: CFQ

DYNAMIC FSYNC: ENABLE DYNAMIC FSync

AUDIO (individuell)

Speaker Tuning aktivieren

SPEAKER AMPLIFICATION OFFSET: 1

STEREO EXPANSION GAIN: 16

BAND1 GAIN, 4

BAND2 GAIN, 3

BAND3 GAIN, 2

BAND4 GAIN, 2

BAND5 GAIN, 3

OTHER SETTINGS: FLL TUNING, ENABLED

Natürlich bei jedem Reiter ganz unten auf ,,Apply'' um es zu speichern Garantiert über 10h Display-on. (Was nicht erwähnt wurde bleibt Standard)

Mit SysCtl noch paar Tweaks und die Reaktionszeit ist einfach genial

[Smokey Skull 19]

Der aktuellste läuft wirklich sehr gut.

Mit SysCtl noch paar Tweaks und die Reaktionszeit ist einfach genial

kannst du das genauer erklären?

[DakiX 36]

Mit dem Android Tuner. Die MS hoch oder runter drehen - je nach dem.

Hier acht Screenshots als Beispiel.

[Smokey Skull 19]

Mit dem Android Tuner. Die MS hoch oder runter drehen - je nach dem.

Hier acht Screenshots als Beispiel.

also nen großen unterschied merk ich nich...

bearbeitet January 11, 2013 von Smokey Skull

[andreas02 1.338]

Update

Perseus alpha31 (09/01):

Removed my own security fixes and replaced them with the official Samsung one. I guess it can now be disclosed: exynos-mem was only one of multiple entry-points for the memory exploit. We discovered the s5p-smem exploit ourselves back in December but kept it quiet, I fixed that one back in version 29.2 without mentioning. Nobody was secure from a smart exploiter up until then, SuperCurios or Chainfire's software fixes are also just patching a single hole in what is a Swiss cheese. Kernels >v31 and beyond stock LLA are now the only truly protected ones.

Samsung's fix for the sudden death syndrome (SDS) included. It is caused by eMMC failure on phones with VTU00M 16GB internal memory chips with revision 0xF1. You can check your phone with the "eMMC Brickbug Check" in the Play Store (Ignore the message if it says you're not affected, the type and revision is what matters). The patch is a firmware soft-patch that is applied on every boot and MMC resume, it is not a permanent fix. You will need to stay forever on kernels which include the patch, this also includes updated recoveries and their embedded kernels.

Some other minor MMC changes extracted from Update 7 sources.

Post 1 ergänzt

LG

Andreas

[spikehansley 0]

hallo zusammen,

ich habe jetzt die letzte version von dem kernek geflasht, bin ich jetzt vor dem sudden death geschützt oder muss ich noch eine andere cwm flashen ? sonst muss ich nichts einstellen oder beachten ?

danke

[andreas02 1.338]

Schau hier im Post 1.

https://www.handy-faq.de/forum/samsung_galaxy_note_2_forum/276837-samsung_galaxy_note_ii_ploetzlich_defekt_sudden_death.html

LG

Andreas

[andreas02 1.338]

Update

Changelog:

Perseus alpha32 (29/01):

Charging control implemented. This is my own version.

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: DCP / Dedicated Charging Ports which also includes AC chargers, but also special USB plugs; SDP / Standard Downstream Ports which usually includes almost all data enabled USB ports, and CDP / Charging Downstream Ports which 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. More info here. - Technical explanation here.

Charging logic:

Stable margin removal option. The charger chip is capable of detecting unstable charging sources; it dynamically reduces the input current in 100mA steps until it detects a stable voltage input [We don't have the charger chip datasheet, so the technical explanation is a bit blurry here on how it decides that it's unstable]. It further reduces it by 100mA as a safety margin, you can disable this now.

Complete disabling of unstable power detection. This simply ignores unstable power sources and leaves the input current limit at its set up value. This will fix charging problems people have been reporting. However, please use it at your own risk, the S3 chargers which have had these symptoms clearly have some issue in their hardware so you might actually kill them with this option enabled as there is no protection from the phone's side anymore.

The actual input current limit can be read out in /sys/devices/platform/samsung-battery/power_supply/battery/current_max, so you can see the real limit there, it's the closest thing we have to the actual charging current on stock values since there is no hardware to read out the live currents.

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.

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. Use at your own discretion.

mDNIe sharpness and RGB/YCM chroma saturation control in STweaks:

I started implementing sharpness control in STweaks and went a bit over-board instead of a simple checkbox; You now have controls over the mDNIe registers as a delta offset value compared to the stock register values. I'm applying the offset to all mDNIe profiles and scenarios which have the specific post-processing effect active in that specific scenario. Meaning, that you start with the default profile; Dynamic / Standard / Natural / Movie and have the delta offset applied on top of that.

Sharpness delta. This is what brought most of the quality difference in hardcore's original tweaks. You can now fine-tune it to your own taste, and also take into regard that it produces a different effect for each screen profile while having the same delta - the base values between the profiles are different.

DE control - I don't know what this actually does and I couldn't discern much difference between the values, but it used to be disabled in hardcore's tweaks.

Chroma saturation control: This is composed of 2 values for each RGB/YCM channel. See the Munsell color system for a visual representation of the values controlled here. The chroma curve control describes the curve weight based on chroma intensity, the chroma gain is the chromatic gain that is being applied on the respective channel. Chromatic saturation weight is again another multiplier for all channels combined. I have not managed to properly identify the chroma grey threshold and its effects.

Basically this is like an RGB control on steroids, and enables you to tune your screen to your own liking and calibrate it as you wish. Please note that not all scenarios in the profiles have chroma saturation effects, the Movie profile for example has no effect applied to the UI so chromatic control has no effect on it.

I also want to state that the above are my deductions and theories on the descriptions of these controls, I'm not familiar enough on colour theory to be able to confidently say that these descriptions are correct, and the controls are a work-in-progress for now. Experts are welcome to contribute here.

Front buffer early suspend delay option for those who have issues with the CRT animation.

Did some refactoring on the Mali drivers and fixed a bug which may have caused less capable undervolting than the stock implementation.

Post 1 ergänzt

LG

Andreas

[Hoppel2580 6]

Der neue Kernel hat noch fehler. Sobald man die Galerie oder die Kamera öffnet wird der Bildschirm dunkel und bleibt es auch bis man die Tastensperre rein und wieder raus macht.

[andreas02 1.338]

AndreiLux auf XDA arbeitet daran....

LG

Andreas

[viper_86 479]

Der neue Kernel hat noch fehler. Sobald man die Galerie oder die Kamera öffnet wird der Bildschirm dunkel und bleibt es auch bis man die Tastensperre rein und wieder raus macht.

Ich habe den Fehler nicht. Zumindest ist mir nichts aufgefallen.

Gruß

Gesendet von meinem GT-N7100 mit Tapatalk 2

[andreas02 1.338]

Bei manchen ist das so...liegt wohl an der jeweiligen ROM und dem "Zusammenspiel".

LG

Andreas