[KERNEL] Perseus alpha 36.3

Discussione in 'Modding - Samsung Galaxy Note 2 GSM (N7100)' iniziata da Odino, 23 Mar 2013.

Condividi questa Pagina

  1. Odino

    Odino Baby Droid

    Iscritto:
    28 Gen 2013
    Messaggi:
    9
    "Mi Piace":
    14
    Ritengo questo uno dei migliori kernel in circolazione per il Note 2. Perseus è sviluppato AndreiLux e trovate il link originale qui: xda

    ATTENZIONE  

    Questo kernel è compatibile solo con rom "based samsung".


    Requisiti:
    - Note 2 (N7100)
    - Custom recovery
    - Root

    Download:
    In fondo a questo thread. Attenzione, prendete i file per il modello N7100

    Passaggi via recovery: Io personalmente ho fatto pure i wipe cache e dalvik prima di mettere il kernel :)
    • Scaricare l'ultima versione del kernel e copiarla sulla memoria del telefono
    • Entrare in recovery (VOLUME UP + HOME + POWER)
    • Scegliere Install zip from.. (a seconda se l'avete messo sulla memoria interna o esterna).

    Passaggi via Odin:
    • Aprire Odin
    • Assicuratevi che vi siano le spunte SOLO su Auto Reboot e F. Reset Time
    • Avviate il telefono in modalità download ((VOLUME DOWN + HOME + POWER)
    • Connettete il telefono al computer e aspettate che Odin riconosca il telefono
    • Premete su PDA e selezionate il file .tar del kernel
    • Premete su Start
     
    Ultima modifica di un moderatore: 4 Mag 2013
    A innovo, japoco_poz14 e Morissio piace questo elemento.
  2. Odino

    Odino Baby Droid

    Iscritto:
    28 Gen 2013
    Messaggi:
    9
    "Mi Piace":
    14
    Changelog:

    Perseus alpha35 (06/04)

    Codice:
    Further rewrote the in-kernel audio controls:
    Threw out the old detection methods for something more robust.
    This particularly enables non-cellular applications such as Skype, Viber, and so on to be detected correctly. A "calling" state now includes any and all use-cases where the audio is outputted via the phone's earpiece. This fixes microphone levels for such apps to correctly use the calling sensitivity value.
    Added microphone level for camera use, this state is enabled whenever a camera stream is active. It should give more options into adjusting things to your likings.
    By now the sound engine has only little similarities to Boeffla, any bugs and feedback now go directly to me.
    Developers only: MHS: Added a new small tool for tracking media use and reporting it to other in-kernel drivers. Capable of detecting video recording, decoding and camera streams for now. See commit for more info.
    mDNIe control changes:
    Removed several controls in STweaks simply because people misunderstood them or misused them, or they simply had no rational use.
    Video detection, now with the help of MHS, is no longer limited to the stock video player. Any video players using hardware decoding will now be able to make use of edge enhancement, HDR and DNR, this includes any web-based players and the YouTube app.
    Custom LED controls implemented; Exposed most variable controls for the notification LED via sysfs and STweaks (LED tab). :
    Control LED brightness. Currently the OS dictates, depending on brightness detected by the light-sensor, wether to run the LED in a low-power mode or in a high-power mode, you can now set brightness for both.
    Blinking control, this is basically the shape of the wave-pattern that the LED blinks in, you have several controls, best described the data-sheet description:
    The fade-in time period is TT1 in the graph, while the fade-out period is TT2.
    Slope (1/2/3/4) detention time represents DT1,2,3,4 in the graph, it controls how "steep" the four different curves are.
    The LED fading checkbox simply switches between having the detention times controlled by the sliders to having them to 0 (Stock blinking behaviour).
    The ZRam control is found in the I/O Tab in STweaks. Set it to 0 to turn it off completely, any other value to turn swap on. Changing value takes about ~10-20 seconds depending how loaded the disk is with swap pages so don't piss your pants if it doesn't react immediately.
    

    Changelog precedenti:

    Perseus alpha34 (22/03)
    Codice:
    Updated sound engine. Based on Boeffla (Andip71)sound but custom fork with rewritten system interface and some other code re-factorings.
    Should fix all FM Radio issues.
    Brings us saturation prevention for the equalizer.
    Privacy mode.
    Microphone level control
    You now have control over the speaker equalizer via sysfs, please visit /sys/class/misc/wolfson-control/ the controls are self-explanatory.
    I removed the equalizer pre-sets from STweaks, if you want, set them manually:
    
    Bass-extreme: 12 8 3 -1 1
    Bass and Treble: 10 7 0 2 5
    Treble: -5 1 0 4 3
    Classic: 0 0 0 -3 -5
    Pleasant for ears: 4 3 2 3 1
    Eargasm: 12 8 4 2 3
    Enabled ZRam by default with disk size of 200mB and swappiness of 90%.
    Applied a requested patch which allows PCs to be booted off from the phone storage.
    

    Perseus alpha33 (26/02)
    Codice:
    Perseus alpha33 (26/02):
    Revamped and hopefully final version of mDNIe controls:
    The controls work now on two levels: First we have a master sequence that overrides any and all of Samsung's settings; The master sequence is calibrated to sRGB norms on a precision level equalling and even surpassing the iPad3/4 with help of professional equipment (Spectrophotometer) and professional hands. All credit goes to Slimer777 for his incredible job in doing this.
    
    Calibration data:
    
    
    
    Simple report: Download
    Detailed calibration report: Download
    Advanced colour management report: Download
    
    (Please note that the "before" values represent the raw screen output without use of mDNIe, these values don't represent any of the live profiles)
    
    The master sequence works as as the calibrated base; for people not wanting to bother further with any more controls, you simply enable this and you're done. Please keep in mind that every screen is slightly different and variations in manufacturing affect image output; this works as a base calibrated as close as possible to sRGB / Rec. 709 specifications.
    
    Second part is the register hook, it catches effect values and modifies them by applying delta values available as controls in STweaks and in /sys/class/misc/mdnie/hook_control/. 
    
    Leaving both these options will give you Samsung's default values, plus the black crush fix.
    
    The register hook, while used on Samsung's profiles, is not capable to alter effects which are not integrated in that screen profile's value sequence, the "Movie" profile for example lacks some effects present in the "Dynamic" profile. The same is valid when having different scenarios, the "Camera" scenario will use different effects in its base than the "UI" scenario. To fully explore all possible effects, use the Master profile as it integrates all effect values known.
    Each control has a master kill-switch which enables or disables the effect. This varies by profile and scenario, so you have control to only "toggle" the switch, whatever its state may be in.
    Digital noise reduction - Reduces and flattens out grain. Advanced controls are found in the hook_control folder with the dnr_ prefix.
    High dynamic range - A HDR effect which brings out details in dark and extremely bright scenes.
    Digital edge enhancement - An edge enhancement effect. What we previously called "sharpening". Divided in controls for radius, amount and threshold. Read the Wikipedia page for more information. More advanced controls found in the sysfs under the de_ prefix.
    For the above three effects, scenario consideration is taken into account. You can enable/disable them depending when you want it to be applied. Please be aware only the stock applications trigger the scenarios. I will try to enable at least the video scenario depending on when the hardware decoder is active in the future so that they are enabled also in third-party video players.
    Chroma saturation control - Same as in previous version but with fixed labels.
    Colour temperature control - By default this is disabled on all profiles, however, if your screen has a tint to it, this is the first control you should try to fix as it alters temperature on all channels.
    The SCR controls are colour channel filters working on the Red, Green, Blue, Yellow, Cyan, Magenta, White, and Black channels.
    Imagine the controls as manipulating the corners of the RGB cube:
    
    (Credit to Wikipedia for the graphic)
    
    By controlling the RGB coordinates of each corner/channel we can mould the cube into a different shape. At the same time the cube is projected onto a hexagon; the perimeter / angle of the hexagon represents the colour hue, the radius of the hexagon from the middle represents chroma. We can use the chroma saturation controls to "push in" each corner of the cube, while moulding the corner's directions with the RGB controls. The RGB coordinates can be transformed into the HSL space space if needed, however I didn't include this function yet as I don't feel the need for it.
    
    STweaks has controls for the RGBYCMW channels, the K (Black) channel I left out because it makes no sense in altering it, but can be found in the sysfs folder.
    Several controls have a "factory setting" switch, this are the burned in-hardware values for some controls, they overwrite the controls themselves.
    Additionally to the controls exposed to STweaks, there are several other effects and modifiers exposed in the sysfs interfaces. This also includes the gamma curve controls for levels 0-255 in steps of 16.
    
    There are also some additional unidentified configurables which I wasn't able to properly give a name to or had no effects: Dithering, ABC (Seems to give a gamma brightness boost), SCC, UC, and MCM (Colour temperature) configurables whose exact effect isn't documented.
    

    Perseus alpha32 (29/01)
    Codice:
    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.
    
     
    Ultima modifica di un moderatore: 20 Apr 2013
    A japoco_poz14 piace questo elemento.
  3. japoco_poz14

    japoco_poz14 Bronze Droid

    Iscritto:
    19 Mag 2012
    Messaggi:
    723
    "Mi Piace":
    128
    grande:)sulla omega e su molte altre rom che ho provato va benissimo!per ora è il mio kernel standard!peccato solo che è da un pò che non lo aggiorna:(
     
  4. simoscorpion

    simoscorpion Administrator Membro dello Staff

    Iscritto:
    26 Lug 2012
    Messaggi:
    45.604
    "Mi Piace":
    11.830
    R: Perseus alpha33

    È uscita la 34.2

    Inviato dal mio GT-N7100 con Tapatalk 2
     
    A japoco_poz14 e Morissio piace questo messaggio.
  5. japoco_poz14

    japoco_poz14 Bronze Droid

    Iscritto:
    19 Mag 2012
    Messaggi:
    723
    "Mi Piace":
    128
    ahahah giusto perchè ho detto che non l'ho aggiornavaaaa:) lo provo:)
     
  6. simoscorpion

    simoscorpion Administrator Membro dello Staff

    Iscritto:
    26 Lug 2012
    Messaggi:
    45.604
    "Mi Piace":
    11.830

    poi dicci come va soprattutto i consumi ;)
     
  7. japoco_poz14

    japoco_poz14 Bronze Droid

    Iscritto:
    19 Mag 2012
    Messaggi:
    723
    "Mi Piace":
    128
    Il comparto audio in stweaks è stato nettamente migliorato! Cosa molto positiva! Mi sembra che come reattività siamo molto vicini alla versione 33. Ora rimangono da vedere i consumi!
     
    A Morissio piace questo elemento.
  8. Morissio

    Morissio Guest

    Se ha i consumi della 33 lo metto... uso poco il comparto audio ma il consumo della batteria è fenomenale, soprattutto con l'UV ;)

    Doppio grazie! :beer:
     
    A japoco_poz14 piace questo elemento.
  9. japoco_poz14

    japoco_poz14 Bronze Droid

    Iscritto:
    19 Mag 2012
    Messaggi:
    723
    "Mi Piace":
    128
    Domani sera vi farò sapere perché per ora come sapete è troppo presto. Ho appena flashato e devo fargli fare qualche ciclo! Cmq io sto usando la cpu a 1500 di max sempre con i settaggi che ti ho passato morissio
     
  10. japoco_poz14

    japoco_poz14 Bronze Droid

    Iscritto:
    19 Mag 2012
    Messaggi:
    723
    "Mi Piace":
    128
    R: Perseus alpha34

    [​IMG]
    Direi molto buono:)

    Inviato dal mio GT-N7100 con Tapatalk 2
     
  11. Morissio

    Morissio Guest

    Abbiamo praticamente lo stesso consumo, quindi direi che con l'ultima versione di miglioria c'è la parte audio ma a consumo è uguale alla precedente. :)

    Ed io ho un UV di -37mV mentre ho visto che te hai un -50mV
     
  12. japoco_poz14

    japoco_poz14 Bronze Droid

    Iscritto:
    19 Mag 2012
    Messaggi:
    723
    "Mi Piace":
    128
    R: Perseus alpha34

    Si io ho -50 ma 3g sempre attivo e questo test l ho fatto con cpu max 1600 e display auto con luminosità massima sulla barra:)

    Inviato dal mio GT-N7100 con Tapatalk 2
     
  13. simoscorpion

    simoscorpion Administrator Membro dello Staff

    Iscritto:
    26 Lug 2012
    Messaggi:
    45.604
    "Mi Piace":
    11.830
    R: Perseus alpha34

    Io come consumi non ci sono...:mmm:

    C'è un bluetooth test che mi consumo un po ma non capisco cosa sia visto che il bt non lo accendo mai

    Inviato dal mio GT-N7100 con Tapatalk 2
     
    Ultima modifica: 27 Mar 2013
  14. japoco_poz14

    japoco_poz14 Bronze Droid

    Iscritto:
    19 Mag 2012
    Messaggi:
    723
    "Mi Piace":
    128
    R: Perseus alpha34

    Mmm. Adesso ci guardo pure io.

    Inviato dal mio GT-N7100 con Tapatalk 2
     
  15. simoscorpion

    simoscorpion Administrator Membro dello Staff

    Iscritto:
    26 Lug 2012
    Messaggi:
    45.604
    "Mi Piace":
    11.830
    R: Perseus alpha34

    :mmm: sembra essere l'app smartconnect o smartwatch perché adesso eliminandole il consumo di bttest è calato

    Inviato dal mio GT-N7100 con Tapatalk 2
     
  16. japoco_poz14

    japoco_poz14 Bronze Droid

    Iscritto:
    19 Mag 2012
    Messaggi:
    723
    "Mi Piace":
    128
    ragazzi io riscontro una lentezza assurda per caricare il telefono. sono tornato al 33.2 perchè in 4 ore dal 10% di batteria è arrivato al 65% rimesso il 33.2 che mi trovavo strabene:)
     
  17. Morissio

    Morissio Guest

    R: Perseus alpha34

    Come sempre sei un grande :) io l'avrei messo sabato ma a sto punto evito xD

    Fatto qualche wipe per il downgrade?

    Inviato dal mio GT-N7100 con Tapatalk 2
     
  18. japoco_poz14

    japoco_poz14 Bronze Droid

    Iscritto:
    19 Mag 2012
    Messaggi:
    723
    "Mi Piace":
    128
    si!appena sono tornato con il 33.2 la batteria ha preso a caricarsi come si deve:)
    si i soliti cache e dalvink:) quando flasho qualcosa la faccio sempre:)
    ora metto su la nuova phil:)
     
  19. japoco_poz14

    japoco_poz14 Bronze Droid

    Iscritto:
    19 Mag 2012
    Messaggi:
    723
    "Mi Piace":
    128
    uscito kernel 35:) io li sto usando sia questo e sia il 34.2 e mi trovo strabene:) adesso sto testando il 35:)
     
  20. Morissio

    Morissio Guest

    R: Perseus alpha34

    Io sono ancora fermo a 2 versioni fa xD domani leggo il changelog ;)

    Inviato dal mio GT-N7100 con Tapatalk 2