CERCA
PER MODELLO
FullScreen Chatbox! :)

Utente del giorno: paolothlw8 con ben 27 Thanks ricevuti nelle ultime 24 ore
Utente della settimana: ste22032 con ben 99 Thanks ricevuti negli ultimi sette giorni
Utente del mese: Pierdebeer con ben 542 Thanks ricevuti nell'ultimo mese

Pagina 1 di 256 1231151101 ... ultimoultimo
Visualizzazione dei risultati da 1 a 10 su 2557
Discussione:

[KERNEL JB dual boot] SIYAH - one kernel to rule them all (GS3)

  1. #1
    Super Moderator L'avatar di JacOcaJ
    Registrato dal
    Jun 2011
    LocalitÓ
    A volte qua, a volte la ...
    Messaggi
    29,472
    Thanks
    1,370
    Thanked 11,783 Times in 7,929 Posts
    Predefinito

    [KERNEL JB dual boot] SIYAH - one kernel to rule them all (GS3)

    Sito di gokhan: QUI

    Thread su xda: QUI





    1. POST 1) INDICE DISCUSSIONE
    2. POST 2) DESCRIZIONE KERNEL
    3. POST 3) CHANGELOG
    4. POST 4) DISCUSSIONI DI INTERESSE AMBITO KERNEL
    5. POST 5) VERSIONI BETA
    6. POST 6) GUIDA DUAL BOOT BY ILLUMINATO67 (IN ITALIANO)
    7. POST 7) FAQ AND MORE BY DROIDPHILE (IN INGLESE)
    8. POST 8) DUAL BOOT BY DROIDPHILE (IN INGLESE)
    9. POST 9) CONTINUA DUAL BOOT BY DROIDPHILE (IN INGLESE) + BNL BREATHING BY DROIDPHILE (IN INGLESE)
    10. POST 10) SETTAGGI BATTERIA: BY ALEGU --- SETTAGGI PERFORMANCE: BY LUCALIVI




    FUNZIONA SOLO SU FIRMWARE JB O CYANOGENMOD 10







    SOLAMENTE VOI SIETE RESPONSABILI DEI MALFUNZIONAMENTI AL VOSTRO CELLULARE, QUINDI PENSATE BENE A QUELLO CHE FATE.
    Ultima modifica di JacOcaJ; 07-12-12 a 10:16
    Sono un clown, e faccio collezione di attimi ....

    Spoiler:

  2. I seguenti Utenti 17 hanno ringraziato JacOcaJ per il post:

    AlbertoSONIC (13-02-13),dobion (01-04-13),Emans (23-11-12),Fastwebnico (11-04-13),gabrylele (14-05-13),illuminato67 (09-10-12),marlboro528 (13-02-13),N1m0Y (07-12-12),NIPO (17-11-12),nowhereland63 (04-11-12),pappo63 (06-04-13),PatrickBateman (28-02-13),Ragz (05-02-13),savioonline (30-04-13),Steccas (13-12-12),ZioSte (11-11-12)

  3.  
  4. #2
    Super Moderator L'avatar di JacOcaJ
    Registrato dal
    Jun 2011
    LocalitÓ
    A volte qua, a volte la ...
    Messaggi
    29,472
    Thanks
    1,370
    Thanked 11,783 Times in 7,929 Posts
    Predefinito

    POST 2


    Sito di gokhan: QUI

    Thread su xda: QUI






    FUNZIONA SOLO SU JELLY BEAN




    Quote Originariamente inviato da GOKHANMORAL
    FEATURES:


    Features :-
    • Samsung and CM10 support with a single kernel image
    • based on i9300 update7 sources
    • CPU OC/UC/UV
    • GPU OC/UC/UV (5 step GPU clock)
    • Audio enhancement and sound boosting for great headphone experience (partial-port of wm8994 based implementation from project-voodoo)
    • init.d support
    • Triangle-away app support
    • Auto-root
    • Adjustable charging speeds for AC and USB
    • Automatic EFS Backup
    • Samsung proprietary ExFat modules are loaded. Don't ask about ExFat support for aosp roms in this thread.
    • Kernel based gestures support by Tungstwenty. See http://forum.xda-developers.com/show....php?t=1831254
    • NTFS automounting for USB sticks, mounted to /mnt/ntfs folder in Read Only mode.
    • mDNIe negative effect toggle with 4 consecutive press of home button
    • mDNIe values can be adjusted using the interfaces in /sys/class/misc/mdnie.
    • Almost everything is configurable via simple and free STweaks (included in the kernel or from Google Play)
    • Dual-booting. You can have Samsung JB and CM10 ROMs on a single device at the same time.
    • slide2wake (WIP, still incomplete)








    N.B.
    La recovery del dual boot Ŕ accessibile SOLO dal men¨ dualboot dell' applicazione stweaks. Il kernel siyah NON CAMBIA LA RECOVERY CHE AVETE SUL TELEFONO
    L'applicazione STWEAKS Ŕ scaricabile dal market.

    ISTALLAZIONE versione .ZIP da CWM:

    • Inserire lo zip scaricato nella memoria del telefono e mettere il telefono in recovery mode con la sequenza di tasti VOLUME SU + POWER + HOME
    • Scegliere "install zip from sd"
    • Flashare la versione del kernel siyah
    • Riavviare il telefono

    ISTALLAZIONE versione .TAR da ODIN:

    • Mettere il .TAR scaricato nel desktop del pc
    • Spegnete il vostro SGSIII e mettetelo in download mode con i 3 tasti (premendo VOLUME GIU + POWER + HOME)
      avrete un messaggio di attenzione "WARNING" premete il tasto volume SU e continuate altrimenti premete il tasto Volume GIU per uscire....
    • Avviate Odin
    • Selezionate il file .TAR del siyah in PDA di Odin
    • Connettete il cavo USB al SGS IIl e attendete che ODIN lo legga
    • Premete START e inizia il FLASH
    • Non disconnettere il SGSII finchŔ non si riavvia da solo ed entra di nuovo in funzione


    Quote Originariamente inviato da GOKHANMORAL
    RINGRAZIAMENTI:

    • Chainfire, AndreiLux, Tegrak, Entropy512, Netarchy, Pikachu, Tungstwenty, Codeworkx, XploDwilD

    • This part will be expanded. most of the patches I applied are coded by someone else. please remind me if I forget to give credits to anybody..

    Quote Originariamente inviato da GOKHANMORAL
    IN PREVISIONE:

    Alcune cose sono ancora sogni ...

    • fix bugs
    • add optional teamwin recovery
    • implement BFN (BackFlashNotification)


    SOLAMENTE VOI SIETE RESPONSABILI DEI MALFUNZIONAMENTI AL VOSTRO CELLULARE, QUINDI PENSATE BENE A QUELLO CHE FATE.
    Ultima modifica di JacOcaJ; 02-04-13 a 09:20
    Sono un clown, e faccio collezione di attimi ....

    Spoiler:

  5. I seguenti Utenti 6 hanno ringraziato JacOcaJ per il post:

    Calidreaming (28-02-14),Emans (23-11-12),PatrickBateman (26-02-13),Ragz (06-02-13),ZioSte (11-11-12)

  6. #3
    Super Moderator L'avatar di JacOcaJ
    Registrato dal
    Jun 2011
    LocalitÓ
    A volte qua, a volte la ...
    Messaggi
    29,472
    Thanks
    1,370
    Thanked 11,783 Times in 7,929 Posts
    Predefinito

    post 3............


    N.B.
    La recovery del dual boot Ŕ accessibile SOLO dal men¨ dualboot dell' applicazione stweaks. Il kernel siyah NON CAMBIA LA RECOVERY CHE AVETE SUL TELEFONO
    L'applicazione STWEAKS Ŕ scaricabile dal market.


    Quote Originariamente inviato da gokhanmoral

    changelog VERSIONE DUALBOOT:


    SiyahKernel s3-v1.9.1
    Posted on april1, 2013

    Dualboot anche con aosp 4.2.2

    based on GT-I9300_JB_Opensource_Update9
    updated mali driver to support latest CM-10.1
    some ramfs changes/fixes/tweaks
    tested only on Samsung 4.1.2 latest official ROM and CM-10.1 nightly (30/3/2013). Samsung 4.2 leaks are not supported.
    v1.9.0->v1.9.1: fixed hw acceleration problems (samsung roms only). enabled zram (500MB with swappiness of 100).


    Download: http://d-h.st/users/siyah/s3




    SiyahKernel s3-v1.8.9
    Posted on January 18, 2013
    Changelog

    rebased on i9300 update7 sources (sudden-death issue is supposedly fixed in this source drop)
    reverted temporary fix for exynos-mem exploit as i9300-update7 sources already fix that
    cm10.1 is now supported in dual-boot configurations
    1.8.7->1.8.8: fixed cm10.1 not booting when installed as 2ndROM (a tiny typo in ramfs)
    1.8.8->1.8.9: fixed the problem when installing cm10.1 directly as 2ndROM. fixed bluetooth issue in cm10/cm10.1 (credits to Entropy512, just cherrypicked his commit from CM10.1 kernel repo). added profile support back to support droidphile’s STweaksProfiles app. Updated CWM-based recovery to 6.0.2.7.

    TAR
    http://d-h.st/yGl


    CWM
    http://d-h.st/dfI



    Versione 1.8.6

    v1.8.6 -> v1.8.4:
    fixed dualboot problem when having Samsung ROM as the 2ndROM.
    a temporary kernel-side fix for exynos-mem security hole until Samsung fixes it
    added ROW I/O scheduler and set it as default
    lowered GPU thresholds a bit
    fixed GPU voltage initialization (thanks to AndreiLux)
    fixed power saving mode not working (thanks to AndreiLux)
    changed “pleasant for ears” preset and set it default
    boots on cm10.1 but do not use dual-boot support. it will not work yet.

    v1.8.4 -> v1.8.3
    reverted VM_MAX_READAHEAD commit. adjusted cpu hotplug in/out rates in pegasusq because they were just too low after decreasing the sampling time


    v1.8.3 vs 1.8.2
    fixed problem of fb earlysuspend delay not being persisted across reboots. removed automatic installation of stweaks (you can find it on google play).

    v1.8.2 -> v1.8.1
    fixed gpu voltage problems

    V 1.8.1
    Ported CPU UV tab from AndreiLux’s STweaks configDynamic generation of STweaks config and initial GPU voltages are set correctly (mostly based on AndreiLux’s uci.sh script interface while trying to keep the changes minimum to support other guys using my scripts as base)Workaround for CRT animation problem (at the bottom of the screen tab in STweaks)fixed the problem of copying large files that some users experienceremoved custom modifications from pegasusq governor and changed the tweaked values a little


    Download: http://d-h.st/users/siyah/s3



    Versione 1.8

    - rebased on Samsung’s N8020 sources (mainly some CMA_DMA changes/fixes/optimizations, driver & platform code changes and some additional pegasusq logic)
    - fine tuning on pegasusq governor
    - some tiny ramfs changes such as adding governor selection back to STweaks

    Download CWM
    Download Odin



    Versione 1.7

    dual-booting (supports only jb roms: Samsung jb and cm10)
    fixed a ump related bug in v1.6.8 that was causing lags for cm10 users
    removed cpu locking when gpu freq >=440mhz
    alternate touch recovery for secondrom related operations
    alternate cwm-recovery based 2ndrom utils which can be used via stweaks. No more custom recovery.
    Added “no boot logo”, “reboot into 2ndrom utils”, “reboot into first rom” and “reboot into second rom” options to stweaks.
    “black crush fix” by andreilux.
    Car dock support.
    Added this to ramfs (thanks to oranav@xda) to fix easyums compatiblity in cm10.
    Reverted cyanogenmod mdnie scenario commit. Reverted wireless driver and added cm10′s wireless driver as a separate module.
    New stweaks (500% faster startup, retouched ui ) which is also available on Google Play, applied wifi changes in cm10 repo to fix wifi tethering problem. Based on update6 sources. Added discrete wakelock stats and gestures (both by tungstwenty) back. Dns_resolver and md4 modules are linked into the kernel, so loading cifs will be enough to use smb shares. Single image for kernel and recovery, if you flash it to boot partition it is a kernel, if you flash it to recovery it is a cwm-based custom recovery (hijack-recovery will be available in stweaks to flash a custom recovery).
    added cm10′s wireless driver as a separate module.increased mmc timeout even more. added default ROM selection in STweaks.disabled gpu resume freq and gpu boost completely.tweaked pegasusq a little more. ramfs updates for samsung and cm10.ported slide2wake from fluxi’s implementation (WIP. still need some more work).back to new MTP driver.

    Tar per Odin
    http://d-h.st/SiG
    Zip per CWM
    http://d-h.st/37D



    Quote Originariamente inviato da gokhanmoral
    changelog VERSIONE SINGLE BOOT:


    v1.6.7->v1.6.8: Fixed mdnie sharpness tweaks causing strange artifacts on boot animation. Removed process priority tweaks. Removed some unnecessary patches. Enabled gentle_fair_sleepers in default profile (either enable yourself if you are an existing user or reset stweaks if you want it to be enabled). You will see siyahkernel logo as i made this release while working on dual booting and did not spend any time to remove those, create “.nobootlogo” file in your internal sdcard if you find it too disturbing. Fixed setcpu showing 1704 when overclocked to 1700.
    1.6.8 zip

    v1.6.6i -> v1.6.7: Removed last remaining module and linked it into the kernel (mdnie_mods). Made all mdnie variables configurable via misc device (all in /sys/class/misc/mdnie). Hardcore’s sharpness tweaks are converted into a script to use the new interface as an example.

    V1.6.6 -> v1.6.6i: One line fix for freq being stuck at 1704mhz. Changed process thresholds a little.

    V1.6.5 -> v1.6.6: Changed tmu thresholds a little. Fixed freq scaling stuck at some frequencies. Removed cfs tweaks from stweaks. Some experimental process priority modifications to have better ui experience. Most of the custom modules are now linked into the kernel and not loaded as modules.

    V1.6.4 -> v1.6.5 re-adjusted regulator constraints which were lost because of the removed module. Fixed touch boost setting. Enabled swap

    v1.6.3 -> v1.6.4: New cpu steps (1700mhz & 1800mhz). Fixed mali module related problems. Fixed lockup problem while charging the device when it is off. Reverted most of the changes back to v1.5 state which were removed during the lag-hunting process (discrete wakelocks, gestures, voltages…etc).

    V1.6.2 -> v1.6.3change packet filter settings to block multicast (thanks to entropy512). Fixed mali ump mistakes which might be causing problems on samsung roms. Reverted mali cpu lock levels to stock.

    V1.6.1 -> v1.6.2: Cleaned ics leftovers from ramfs. Adjusted maximum gpu voltage constraint (1075mv->1400mv). Increased default gpu voltages by 25mv. This version will reset all your stweaks settings to defaults. Enabled swap (still no zram).

    V1.6 -> v1.6.1: Reverted mtp driver to fix mtp problems on osx. Removed some tweaks which were suspected to degrade performance. Reniced kswapd0 to have lower priority. New wifi driver from n7105 sources.


    Charge boost (for ac: Up to 1200ma, for usb: Up to 900ma)
    auto ntfs mounting to /mnt/ntfs after attaching an ntfs formatted usb stick
    audio enhancements, call it scoobydoo sound, eargasm or whatever (fully functional in v1.6b3)
    overclocking (changes 1400 step to 1500 or 1600, available in v1.6a5)
    some tiny script based tweaks…
    undervolting support, but works with nstools only. Used ezekeel’s customvoltage interface. It is very similar to netarchy’s uv_mv_table and you can use your existing scripts with some little modification. I have also added vdd_levels (don’t know who implemented this) and andreilux’s uv_uv_table interfaces but they are in /sys/class/misc/customvoltage. Lowest voltage level is 850mv until the sources are released. Disabled some logs(available in v1.6a6)
    added lulzactiveq (not tweaked for s3 yet) and hotplug governors (v1.6a7)
    removed the settings which are not available yet from stweaks (1.6a8)
    mdnie sharpness tweaks from hardcore (1.6a9)
    added kernel version to version string to let you see which siyahkernel version you have. 4-step gpu clock settings (clock and thresholds), with 533mhz option and with some limitations because of the lack of voltage settings*(v1.6beta10)
    mdnie sharpness tweaks made optional, in stweaks/screen tab (v1.6beta11)
    sio and v/r i/o schedulers, cifs and nfs modules.*gpu undervolting (lower limit:850mv, upper limit: 1075mv until the kernel is compiled from the sources) (v1.6beta12)
    support for setcpu, voltagecontrol and similar apps which are using universal uv interfaces. Added 1.6ghz and 1.5ghz cpu freq steps. No longer modified 1.4step for overclocking.*(v1.6beta13)
    fixed some modules not being loaded (v1.6beta14)
    fixed vdd_levels path to fix stweaks undervolting settings not being applied ,*adjusted regulator limits (850mv -> 600mv), configurable touchboost freq**(v1.6beta15)
    added gesture support, *mdnie toggle with home button,**swap & zram*(v1.6rc1)
    5-step gpu, new frequency steps for gpu, gpu boost on touch and*some other gpu related modifications/cleanup. Removed zram settings from samsung’s init.rc and added it back to stweaks. (v1.6rc2)
    mali as module (this version supports both samsung jb and cm10 roms). Removed swap & zram. Fixed gpu clock setting problem. Removed gpu boost temporarily. Updated ump driver. Added arm topology support again with cpupower driver. Better loadavg calculation (thanks to andreilux for his merges from upstream) (v1.6rc3).
    Removed 900mv gpu voltage limit. Fixed gpu voltage settings not being applied on boot. Initramfs updates. Fixed audio enhancements reset in some conditions. (v1.6)
    Ultima modifica di JacOcaJ; 02-04-13 a 09:19
    Sono un clown, e faccio collezione di attimi ....

    Spoiler:

  7. I seguenti Utenti 3 hanno ringraziato JacOcaJ per il post:

    Emans (23-11-12),ZioSte (11-11-12)

  8. #4
    Super Moderator L'avatar di JacOcaJ
    Registrato dal
    Jun 2011
    LocalitÓ
    A volte qua, a volte la ...
    Messaggi
    29,472
    Thanks
    1,370
    Thanked 11,783 Times in 7,929 Posts
    Predefinito

    POST 4


    Discussione relativa all' Undervolt S3 Con Siyah Kernel:
    Massima durata batteria e massima stabilitÓ.




    Come avere tre rom contemporaneamente con Siyah Kernel:
    [MOD APK] Tre rom contemporaneamente




    DISCUSSIONE IN INGLESE SU XDA:
    Govermor, scheduler.... Ecc ecc

    [REF][TWEAKS] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App ConfigsReorganized overflowing Posts to fit into 5*

    Tradotta qui

    [Kernel Governors] [Modules] [I/O Schedulers] [CPU Tweaks]




    [GUIDA][STWEAKS] ATTENZIONE E' UNA GUIDA PER GALAXY S2 DELLA SEZIONE S2
    [REF][TWEAKS][GUIDA][STWEAKS] Traduzione completa e aggiornata del menu impostazioni


    Quote Originariamente inviato da illuminato67 Visualizza il messaggio
    Interessante apk per modificare il valore di zRAM
    http://forum.xda-developers.com/show...php?p=39824301
    Ultima modifica di JacOcaJ; 02-04-13 a 09:17
    Sono un clown, e faccio collezione di attimi ....

    Spoiler:

  9. I seguenti Utenti 6 hanno ringraziato JacOcaJ per il post:

    Emans (23-11-12),leolamontagna (31-01-13),marlboro528 (14-02-13),Ragz (06-02-13),ZioSte (11-11-12)

  10. #5
    Super Moderator L'avatar di JacOcaJ
    Registrato dal
    Jun 2011
    LocalitÓ
    A volte qua, a volte la ...
    Messaggi
    29,472
    Thanks
    1,370
    Thanked 11,783 Times in 7,929 Posts
    Predefinito

    POST 5

    VECCHIE VERSIONI BETA e RELEASE CANDIDATE Dual boot


    N.B.
    La recovery del dual boot Ŕ accessibile SOLO dal men¨ dualboot dell' applicazione stweaks. Il kernel siyah NON CAMBIA LA RECOVERY CHE AVETE SUL TELEFONO


    Quote Originariamente inviato da gokhanmoral Visualizza il messaggio


    siyahkernel s3-v1.7rc3
    Nov 10th
    v1.7rc2 -> v1.7rc3: *reverted cyanogenmod mdnie scenario commit. reverted wireless driver and added cm10′s wireless driver as a separate module.
    TAR
    ZIP

    Quote Originariamente inviato da gokhanmoral Visualizza il messaggio


    siyahkernel s3-v1.7rc2
    Nov 10th
    v1.7rc1 -> v1.7rc2: new STweaks (500% faster startup, retouched UI ), applied wifi changes in CM10 repo to fix wifi tethering problem. Based on update6 sources. added discrete wakelock stats and gestures (both by Tungstwenty) back. dns_resolver and md4 modules are linked into the kernel, so loading cifs will be enough to use smb shares. single image for kernel and recovery, if you flash it to boot partition it is a kernel, if you flash it to recovery it is a CWM-based custom recovery (hijack-recovery will be available in STweaks to flash a custom recovery).
    TODO:
    Add timeout setting for 2ndROM boot logo
    Make exfat work in AOSP ROMs
    implement more accurate space requirement checks in 2ndROM utils.
    TAR
    ZIP

    Quote Originariamente inviato da gokhanmoral Visualizza il messaggio


    siyahkernel s3-v1.7rc1
    oct 16th
    v1.7b6 -> v1.7rc1: car dock support. reverted TMU modifications. some fixes for backup/restore for 2ndROM and internal/external confusion is resolved. default I/O scheduler is set to deadline. default gpu boost is set to disabled. Added this to ramfs (thanks to Oranav@XDA) to fix EasyUMS compatiblity in cm10.
    TAR
    ZIP
    Quote Originariamente inviato da gokhanmoral Visualizza il messaggio

    siyahkernel s3-v1.7beta6
    oct 14th
    v1.7b5 -> v1.7b6: (not released yet) added backup/restore to 2ndROM utils. Make sure you backup your 2ndROM before you flash v1.7rc1 because there will be some radical changes in dual booting and you will have to restore your 2ndROM backup after flashing it.
    TAR
    ZIP


    Quote Originariamente inviato da gokhanmoral Visualizza il messaggio

    siyahkernel s3-v1.7beta5
    oct 12th
    v1.7b4 -> v1.7b5: added (again) gpu boost on touch. Set touch boos default back to 800MHz. Updated bcmdhd driver to the one in korean s3 driver. Mali refactorings (new_* interfaces removed from /sys/module/mali/parameters. this will fix malistatus problem).
    TAR
    ZIP

    Quote Originariamente inviato da gokhanmoral Visualizza il messaggio

    siyahkernel s3-v1.7beta4
    oct 10th
    v1.7.3->v1.7.4: replace the recovery image with the new one which was forgotten in the previous release. fix permissions on 2ndROM should be working now. Made a change in wifi offload filtering to deny muticast packets but allow multicast DNS packets.
    TAR
    ZIP
    Quote Originariamente inviato da gokhanmoral Visualizza il messaggio

    siyahkernel s3-v1.7beta3
    oct 10th
    v1.7b2 -> v1.7b3: Recovery is merged with the kernel, no more separate recovery. Flash back your favorite recovery and use STweaks to boot into 2ndROM-utils (which is another CWM-based recovery built into the kernel). Added “no boot logo” option to STweaks. Added “Reboot into 2ndROM Utils”, “Reboot into First ROM” and “Reboot into Second ROM” options. Added “Fix 2ndROM permissions” and “Wipe 2ndROM cache” (wipes only cache partition, not data) to 2ndROM-utils. Fixed some bugs in 2ndROM-utils. Added “Black Crush Fix” by AndreiLux. lcd freq is decreased just a bit to save a little power.
    TAR
    ZIP

    Quote Originariamente inviato da gokhanmoral Visualizza il messaggio

    v1.7b2 is up.
    oct 8th, 2012
    it is distributed as kernel+recovery together. so, flashing cwm or tar package will install both.
    if you prefer another recovery then you will have to flash it after flashing v1.7b2
    I tested installing cm10 and some samsung roms (with or without aroma installer) to 2ndROM.
    you have to remember one thing: you will have to "Format 2ndROM system" if you are installing a new ROM.
    why? because updater scripts format system partition but I have no control on the updater binary and it makes system.img size 0.
    I prevented the formatting part but you have to do it yourself if you are installing a ROM but not an update or a theme.
    TAR
    ZIP

    Quote Originariamente inviato da gokhanmoral Visualizza il messaggio
    siyahkernel s3-v1.7beta1
    oct 6th, 2012 @ 01:04 am › admin

    changelog:

    Dual-booting (supports only jb roms: Samsung jb and cm10)
    fixed a ump related bug in v1.6.8 that was causing lags for cm10 users
    removed cpu locking *when gpu freq >=440mhz
    alternate touch recovery for secondrom related operations
    some 2ndrom features are missing. Implemented features are: Clone 1strom to 2ndrom, clone 2ndrom to 1strom, swap roms, delete 2ndrom.
    Todo:
    Implement missing 2ndrom features
    make a cwm-flashable 2ndrom-utils app
    implement more accurate space requirement checks
    some recovery details:
    Cwm-based recovery v6.0.1.4
    default backup format is set to tar (you can set it to dedupe)
    in kernel recovery optionsdelete stweaks defaults or remove init.d scripts
    in dual booting menu: Swapping, cloning and other 2ndrom related options
    swipe gestures support (up/down to choose menu items and right/left to select/back)
    doubletap to select (needs a little more tuning though)
    uses samsung jb stock kernel recovery as the base
    some details about dual-booting:
    2ndrom system partition will be kept in /sdcard/.secondrom/system.img. You will need 1.5gb space for the 2ndrom system partition in your internal sdcard.
    Both data partitions in 1strom and 2ndrom *will use the same space. Make sure you have enough space to hold both system and data when you clone 1strom to 2ndrom.
    Hidden partition is used as 2ndrom cache partition.
    Flashing a new rom may flash another kernel and you will not be able to boot into 2ndrom anymore. But you will not lose it unless you delete “.secondrom” folder in your internal sdcard. So, flashing back siyahkernel will let you boot into 2ndrom again.
    See this post for more details. It is for s2 but still useful to understand what dualbooting is about.
    xda-developers - View Single Post - [REF][ICS] Kernel Stuffs - How is ICS Kernel Different | updated may-28-2012


    recovery
    Dev-Host - - The Ultimate Free File Hosting / File Sharing Service


    kernel
    tar..... Dev-Host - Siyah-s3-v1.7b1.tar - The Ultimate Free File Hosting / File Sharing Service
    zip.... Dev-Host - - The Ultimate Free File Hosting / File Sharing Service
    Ultima modifica di JacOcaJ; 12-11-12 a 11:57
    Sono un clown, e faccio collezione di attimi ....

    Spoiler:

  11. I seguenti Utenti 3 hanno ringraziato JacOcaJ per il post:

    Emans (23-11-12),ZioSte (11-11-12)

  12. #6
    Super Moderator L'avatar di JacOcaJ
    Registrato dal
    Jun 2011
    LocalitÓ
    A volte qua, a volte la ...
    Messaggi
    29,472
    Thanks
    1,370
    Thanked 11,783 Times in 7,929 Posts
    Predefinito

    post 6

    GUIDA DUAL BOOT DELL' AMICO ILLUMINATO67 (SEZIONE S2).
    QUESTA
    SE VOLETE RINGRAZIARE QUALCUNO RINGRAZIATE LUI NEL SUO THREAD


    Quote Originariamente inviato da illuminato67
    A. Cosa si intende per Dual Boot?

    Alcuni kernels offrono la possibilitÓ di far convivere ed utilizzare due ROM (AOKP, AOSP o Samsung-based) decidendo volta per volta quale avviare.
    Dalla release 1.7 del Siyah Ŕ possibile installare 2 ROM su base Jelly Bean.
    Subito dopo il logo di boot, abbiamo un time-out di 3 secondi, che ci permette di avviare la ROM secondaria premendo il tasto home oppure il tasto volume gi¨. Per avviare la ROM primaria, invece, o attendiamo i 3 secondi oppure possiamo premere il tasto volume su.


    B. Quale architettura di base sottende la dinamica dual boot?

    Ogni ROM avrÓ le proprie partizioni /system, /data e /cache autonome e distinte.
    La Rom primaria avrÓ tutte queste partizioni sulla stessa posizione e si comporterÓ come se fosse in single-boot.
    La Rom secondaria utilizza una partizione nascosta (/dev/block/mmcblk0p9) per /system, e utilizza la SD interna (NO la SD removibile) per memorizzare le partizioni /data e /cache.
    Le partizioni /data e /cache sono conservate nella cartella nascosta /sdcard/.secondrom come immagini montabili a blocchi in formato ext4 (data.img e cache.img).
    La partizione del Kernel Ŕ condivisa tra le due ROM, cioŔ un unico Kernel Siyah si occupa del boot di ogni singola ROM.
    Se si passa dal Siyah ad un kernel diverso, il dual boot ovviamente non sarÓ pi¨ disponibile, anche se rimane un clone della ROM secondaria in .secondrom.
    Rimane quindi "in letargo", pronta ad essere riutilizzata ad un nuovo flash del kernel Siyah.
    La SD interna, la SD removibile, le cartelle /EFS e /EMMC e le altre directory virtuali di file system correlate al kernel verranno condivise tra le due ROM.




    PREMESSE IMPORTANTI:


    La recovery del dual boot Ŕ accessibile SOLO dal men¨ dualboot dell' applicazione stweaks. Il kernel siyah NON CAMBIA LA RECOVERY CHE AVETE SUL TELEFONO
    E'necessario avere almeno 2,5 Giga liberi sulla SD interna (NON la SD removibile).
    La prima volta che andiamo a creare la Secondary ROM, ricordiamoci di fare questo passaggio indispensabile:
    >>>> Selezionare l'opzione format 2ndrom system.
    Ci˛ preparerÓ il telefono alla secondary rom, creando la cartella nascosta .secondrom​ (che ospiterÓ la secondary ROM).
    Da Recovery Ŕ possibile flashare esclusivamente ROM (in formato ZIP), NON i Firmware (che sono in formato TAR).
    Possono essere flashate esclusivamente ROM su base Jelly Bean sia come primary che come secondary.




    DUAL BOOT: Guida per il Flash di una ROM come "secondary".

    Credits:
    Phistachio (XDA)
    [GUIDE] How to Dual Boot using the Siyah Kernel - xda-developers


    1. Bisogna ovviamente avere il kernel Siyah, dalla versione 1.7 in poi.
    2. Controlliamo di avere il terminale carico (90%) e di avere a disposizione almeno 2,5 Giga di spazio libero sulla SD interna (NO SD removibile) per permettere la creazione della cartella nascosta .secondrom​ che ospiterÓ la secondary ROM.
    3. Scaricare la ROM (in formato .zip) che si vuole rendere secondaria, e collocare il file nella scheda SD interna o esterna.
    4. Successivamente aprire STWEAKS e portarsi sul men¨ Dualboot
    5. Premere su reboot into 2ndrom utils e si riaccenderÓ nella recovery siyah
    6. Portarsi nel men¨ del dual boot
    7. Selezionare l'opzione format 2ndrom system
    8. Selezionare l'opzione Wipe 2ndrom data/cache.
    9. Successivamente eseguiamo wipe 2nd rom Dalvik cache
    10. Dopo aver eseguito questo procedimento, dobbiamo ora installare il file ZIP della ROM: selezionare "Installa un file ZIP sulla ROM 2 da scheda SD interna" (Install zip to 2nd ROM from Internal SD card) o "Installa un file ZIP sulla ROM 2 da scheda SD esterna" (Install zip to 2nd ROM from External SD card)a seconda di dove si trova lo zip della ROM
    11. Attendere il termine del flash
    12. Reboot
    13. Premere il pulsante Home o tasto volume gi¨ per accedere alla ROM secondaria.



    Per montare una seconda ROM potremo anche utilizzare un nandroid backup ed utilizzare il comando Ripristino backup come ROM secondaria (Restore as 2nd ROM ....)




    Analizziamo il Men¨ opzioni dual boot





    • Visualizzare lo stato corrente (View current status) - Questa opzione mostrerÓ le caratteristiche della ROM secondaria.

    • Clonare primary ROM sulla secondary ROM (Clone 1st ROM to 2nd ROM) - Questa opzione consente di copiare (clonare) la ROM corrente (ad esempio CM10) nella directory ROM 2. Dura circa 7-20 minuti. Risultato: Avremo 2 ROM uguali.

    • Clonare secondary ROM sulla primary ROM (Clone 2nd ROM to 1st ROM) - Questa opzione copia la ROM 2 (dopo averla installata ovviamente) al posto della primary ROM, sostituendola. Avremo 2 ROM uguali.

    • Rimuovere ROM secondary (Remove 2nd ROM) - In questo modo si cancella completamente qualsiasi file e cartelle della ROM 2

    • Scambiare primary ROM con secondary ROM (Swap 1st ROM with 2nd ROM)- Questo cambierÓ la ROM primaria con la ROM secondaria, rendendo la ROM primaria -> secondaria e la ROM secondaria -> primaria = inverte le ROM. Il processo di swap dura circa 10 minuti, non occorre nessun wipe (anzi: non si deve fare!) preliminare in quanto si viene a creare un file immagine temporaneo della ROM I per poi scambiarlo con la II. Quindi Ŕ importante avere ALMENO 5,0 GB liberi nella memoria SD INTERNA (procedimento un p˛ laborioso e lungo)

    • Installare un file ZIP sulla ROM 2 dalla scheda SD interna (Install 2nd ROM from Internal SD card) ľ Cosý installiamo la ROM (ma possiamo installare anche aggiornamenti della ROM o mod, come verrÓ spiegato meglio nel secondo post)

    • Installare un file ZIP sulla ROM 2 dalla SD card esterna (Install 2nd ROM from External SD card) ľ Cosý installiamo la ROM (ma possiamo installare anche aggiornamenti della ROM o mod, come verrÓ spiegato meglio nel secondo post)

    • Wipe secondary ROM data/cache - Questo cancellerÓ i dati della ROM 2 e la relativa cache. Quando il procedimento viene fatto per la prima volta, verrÓ creato data.img e cache.img e verranno create le cartelle all'interno di /sdcard /.secondrom, preparando il telefono per la ROM 2.

    • Wipe secondary ROM dalvik cache - Questo cancellerÓ la cache Dalvik della ROM 2

    • Fissare i permessi (Fix Permission) della ROM 2 - Fix permission Ŕ uno script che assicura che le applicazioni e i dati corrispondano a vicenda. Solitamente si utilizza quando si hanno FC (Force Close) inspiegabili (per es. dopo aver installato rom)

    • Backup della ROM 2: Permette di creare un backup della ROM secondaria (sulla SD removibile)

    • Ripristino backup come ROM 2 (Restore as 2nd ROM): Permette di ripristinare un nandroid backup tramutandolo in ROM 2

    • Backup della ROM 2 sulla SD interna (Backup 2nd ROM to internal SD): Permette di creare un backup della ROM secondaria sulla SD interna

    • Ripristino backup come ROM 2 dalla SD interna (Restore as 2nd ROM from internal SD): Permette di ripristinare un nandroid backup tramutandolo in ROM 2, utilizzando il file dalla SD interna



    ALCUNE NOTE DI CONTORNO


    1. IMPORTANTE: Dominanza del kernel Siyah

    Se la ROM che dovrÓ essere flashata come secondary prevede nel package un kernel (lo chiameremo xxx) diverso dal Siyah, xxx non sostituirÓ il Siyah, perchŔ il kernel xxx NON verrÓ flashato.
    Il kernel Siyah Ŕ sempre dominante.


    2. RECOVERY DUAL BOOT:

    La recovery del dual boot non Ŕ flashata al momento del flash del siya come recovery di base; se la volete come recovery di base la potete mettere da men¨ dual boot dell' applicazione STWEAKS


    3. Impostazioni ExTweaks

    Le due ROM possono avere impostazioni e settaggi di ExTweaks differenti.
    Nello specifico i settaggi effettuati sulla primary ROM saranno esclusivi per essa e non influenzeranno quelli della secondary. Lo stesso ovviamente vale per la secondary.

    Per ripristinare le impostazioni ExTweaks sulla 1ROM: men¨ "kernel specific options">Reset ExTweaks profiles
    Per ripristinare le impostazioni ExTweaks sulla 2ROM: dovete disinstallare ExTweaks sulla secondary ROM, riavviare e reinstallare ExTweaks sulla secondary


    4. Titanium Backup.

    Pu˛ essere tranquillamente utilizzato per installare le applicazioni utente della primary ROM sulla secondary (io l'ho usato e su XDA viene consigliato).
    E' invece opportuno NON ripristinare le applicazioni di sistema.
    Ovviamente il Titanium della ROM secondaria deve puntare la propria cartella di backup (da dove attingere i files) alla stessa cartella di backup utilizzada da Titanium installato sulla ROM primaria (si modifica dalle impostazioni).
    Perci˛ io vi consiglio di avere una sola ed unica cartella di backup e di NON fare i backup delle applicazioni della ROM secondaria, se no si genera una enorme confusione.
    Eseguite solo i backup dalla ROM primaria e ripristinateli, all'occorrenza, sulla primaria o sulla secondaria.
    Fate attenzione, quando cambiate cartella, se vi appare un messaggio di richiesta di importare/unire i backup: rispondete NO!
    Ultima modifica di JacOcaJ; 27-11-12 a 10:31
    Sono un clown, e faccio collezione di attimi ....

    Spoiler:

  13. I seguenti Utenti 11 hanno ringraziato JacOcaJ per il post:

    Brio94 (04-05-13),Emans (23-11-12),Fastwebnico (11-04-13),giorgione98 (16-02-13),illuminato67 (09-10-12),lorenzosicilia (06-09-13),maxmonta18 (15-11-12),TopoMonko (19-03-13),Zangetsu (09-02-13),ZioSte (11-11-12)

  14. #7
    Super Moderator L'avatar di JacOcaJ
    Registrato dal
    Jun 2011
    LocalitÓ
    A volte qua, a volte la ...
    Messaggi
    29,472
    Thanks
    1,370
    Thanked 11,783 Times in 7,929 Posts
    Predefinito

    post 7

    ......




    Quote Originariamente inviato da droidphile Visualizza il messaggio
    FAQS and More

    In no particular order.

    1. "How the heck do i flash the kernel.tar within device. I see a boot.img and recovery.img in the tar and not zimage like before?? I don't wanna increase flash counter by using odin from PC!"

    A. Use mobile odin. (Paid on market, free on xda).
    Open the app, Click on "kernel", select the kernel.tar. Click on "recovery", select the same kernel.tar.
    Scroll down, select "flash firmware". Reboot.
    If you find only kernel.img in the tar, select only kernel in mobile odin and "flash firmware". (If size is less than 8 MB, there is only kernel inside the tar. Don't bother about opening the .tar)

    2. "Why two mountable image files in tar?"
    A. GS3 has separate kernel and recovery partition.
    Kernel partition : /dev/block/mmcblk0p5
    Recovery Partition: /dev/block/mmcblk0p6
    Both partitions has a max size limit of 8 MB each.

    3. "Does that mean i can flash only kernel/only recovery if i don't need the other?"
    A. Yes. However, if recovery was modified to support a new feature in kernel, you may want to flash both.

    4. "If i flash tar from Odin on PC, both kernel and recovery is flashed and i can't choose to flash only one?"
    A. Yes, both are flashed.

    5. "How to flash only kernel/only recovery with cwm flashable zip?"
    A. If you know what you're doing, open updater-script in the zip and comment out the line that starts with write_raw_image for the one you don't need - kernel or recovery.

    6. "Should i wipe cache and dalvik before flashing kernel?"
    A. NO

    7. "Best governor, best i/o scheduler for this kernel?"
    A. Define best governor and best i/o scheduler!
    Pegasusq is good enough to be responsive, battery friendly and quad core friendly if tweaked properly. Use any i/o scheduler. Sio/deadline are good.

    8. "Why is Idle+Lpa default on STweaks/ExTweaks and recommended settings. In Siyah kernel for GS2, Aftr+Lpa was recommended!"
    A. Aftr ofcourse saves more power than Idle if you consider what each of those low power state modes do. But combination of quad core architecture and pegasusq governor (or any external hotplugging logic combined with other governors) which need to respect rq values along with load thresholds makes it a little slower to turn off last 3 cores (if all the cores are ON obviously). AFTR requires that all cores except first (cpu0) be turned off - to kick in. So we're better off with Idle+Lpa.
    However if you're using forced single core mode always (which is non sense in this powerful device), you can go for Aftr+Lpa.

    9. "How do i overclock/underclock/undervolt GPU?"
    A. Either use STweaks/ExTweaks app or use a script
    Ex:
    #Frequency steps
    echo 160 > /sys/module/mali/parameters/step0_clk
    echo 266 > /sys/module/mali/parameters/step1_clk
    echo 350 > /sys/module/mali/parameters/step2_clk
    echo 440 > /sys/module/mali/parameters/step3_clk
    echo 533 > /sys/module/mali/parameters/step4_clk


    #Voltages
    echo "875000 900000 950000 1025000 1075000" > /sys/class/misc/mali_control/voltage_control

    10. "My device is not stable at 1.8 Ghz. But i still wanna overclock the device to possible maximum and show off to friends"
    A. Try setting last frequency as 1750 mhz. (Modify 1.8 to 1.75 ghz with 1.7 ghz still in place)
    Use kmemhelper interface. Put this line in your initd script.

    kmemhelper -n exynos4x12_apll_pms_table -t int -o 0 14353152

    11. "I OCed to 1.7/1.8 Ghz. My device is able to handle it. But i can't get high benchmark scores. Why?"
    A. Your CPU is getting throttled during benchmark during benchmarking because of heating. This is a thermal safeguard measure. It might be getting throttled to 800 mhz or so.
    Forget benchmarks, treat the overall responsiveness in daily usage as the criteria to determine if the device is fast enough for you or not.

    12. "Any rule of thumb to increase life span of the battery? And I see percentage drops to 99 immediately after a charge till 100%"
    A. Do not recharge to 100% often and even if you do, don't keep it plugged in 100% for long time. Best is to charge till 98%. And make sure charge does not drop below 10% while on normal use.
    Charge dropping to 99% swiftly is a protection mechanism, not a fault with your battery or kernel or rom.

    13. "I adjust the voltage by some mV in STweaks/Extweaks. I checked SetCpu and voltage has not changed!"
    A. Voltage settings in STweaks/ExTweaks follow VDD interface. They're applied ONLY during boot time. Why? The code is to reduce X mV specified by you in STweaks/ExTweaks, for all voltages. If the settings is applied real time, it will cause reduction of voltage every time and instabilities.

    14. "If I have no root, and flash this kernel using desktop odin will i get root?"
    A. YES. However, if you don't see a CWM recovery, download and flash a recovery from Chainfire thread.

    15. "Does the kernel backup EFS partition automatically?"
    A. YES.

    16. "Is there NTFS support?"
    A. YES. Mounted to mnt/ntfs in Read only mode. Unmount and remount in Read Write mode if you need to.

    17. "What voltage step does GS3 support while UV/OV?"
    A. Regulator supports increments of +/-12.5 mV (Those who had GS2 will remember it's regulator supported +/- 25mV)

    18. "Why is resetting STweaks/ExTweaks profile recommended sometimes after a kernel flash?"
    A. Your profiles are stored under /data/.siyah with ".profile" extension. ".active.profile" file under the same directory stores the name of your active profile. Contents in profiles are in the format parameter = <default_value>
    There could be changes in Stweaks/ExTweaks interface for a new build:-
    i) Some new tunables were added
    ii) Some tunables were removed
    iii) Transposition of some tunables
    iv) Default value of some tunable was changed.
    When such a change occurs, your profiles should know it too so that it can contain all the parameters. That's why you have to reset profiles after a new kernel flash if it changes something in STweaks/ExTweaks.
    Resetting simply copies .profile files from /res/customconfig to /data/.siyah . You can do it manually using a file manager to avoid a reboot to recovery and back to rom. Kernel already detects STweaks/ExTweaks changes to reset profile automatically on first boot after flashing.

    19. "How to insert a module that's available in /system/lib/modules?"
    A. Safe to be root. In terminal or adb
    su
    insmod /lib/modules/<module_name.ko>

    20. "How to know which modules are pre-loaded by kernel?"
    A. Terminal or adb:
    lsmod

    21. "I don't see an init.d folder in my rom. I wanna create some initd scripts. What to do?"
    A. Using a root explorer create init.d directory under /system/etc. Set perm 777.

    22. "After flashing a new kernel i see there are some stuffs missing from STweaks/ExTweaks"
    A. Either the support for those missing tunables were removed or just the STweaks/ExTweaks interface was removed. The parameters might still be accessible through scripts. Check the file path to make sure.

    23. "Does notification LED cause wakelock and lot of drain?"
    A. Hm Yes and No. CPU has to wake to help turn on notif led and to turn off when it's timeout. When LED is blinking, no wakelocks are held. Notif led is controlled by a diff h/w and not directly by CPU.

    24. "How do I know if my modified charge current settings (using STweaks/ExTweaks) are effective?"
    A. Use CurrentWidget from playstore. Monitor the reading while charging.

    25. "What happens if my smooth scaling frequency is greater than my scaling max frequency?"
    A. Smooth scaling will be inactive/disabled.

    26. "Can I flash this kernel on a non-international variant - At&T/Korean/Japanese...?"
    A. NO. Don't risk 800 dollars. Dev might release different variants for these devices later.

    27. "I tried setting a negative value for a symbol using kmemhelper interface. I see the value is not applied properly. What could be wrong"
    A. The negative value might be detected my kmemhelper as an argument. To prevent that, use two minus signs (--) before the negative value.
    Ex: "kmemhelper t int -n touch_boost_level -- -1" (This resets touch boost frequency to default).

    28. "I wanna disable all the audio enhancement stuffs. How?"
    A. In your script
    echo 0 > /sys/class/misc/scoobydoo_sound_control/enable

    29. "Least voltage for a CPU frequency I can undervolt to?"
    A. 600 mV. Maximum = 1500 mV

    30. "Does sound enhancements in stweaks applies to bluetooth headsets?"
    A. NO. Only for wired headphones.

    31. "Do we have temperature sensor in our CPU?"
    A. YES

    32. "I have this habbit of unknowingly pressing home button multiple times and that result in inverting colors on my screen."
    A. Disable "mDNIe negative toggle under Screen tab in STweaks.

    33. "I sometimes get unexpected reboots. What could be wrong?"
    A. Number of reasons.
    - Problem from ROM side - wrong dpi setting for an app, wrong build.prop tweaks, etc.
    - Too much UV on CPU/GPU
    - Too much CPU OC/GPU OC
    - CPU/Battery heated up too much because of weather/benchmarking/faulty charger, etc

    34. "I want to help dev debug an issue providing a kmsg. How to?"
    A. After the problem (random reboot/freeze/lockup), do not pull out battery to recover. Just long press power button so that device can reboot. Then connect device to PC, (provided you have setup adb), type
    adb pull /proc/last_kmsg
    Save the file as .txt and post in the thread along with description of the problem and possible way to reproduce it.
    If you can't use adb from pc, just copy last_kmsg file from /proc directory to internal sd, copy it to your PC and post in the thread.

    35. "I'm not able to copy Person X's undervolting settings. Why? Sometimes, across different builds of Siyah, my UV settings are stable in one version and not in another. Why?"
    A. One or more of the following
    - Every device is different - diff grades of CPU
    - CPU drivers might change across different builds
    - Power requirements may differ depending on the temperature, altitude or the defaults.

    36. "GPU OC/UC range?"
    A. 54 to 700 mhz. With voltage range of 600mv to 1200mv at 25mv steps.


    more might follow..
    Ultima modifica di JacOcaJ; 08-10-12 a 20:53
    Sono un clown, e faccio collezione di attimi ....

    Spoiler:

  15. I seguenti Utenti 2 hanno ringraziato JacOcaJ per il post:

    Emans (23-11-12)

  16. #8
    Super Moderator L'avatar di JacOcaJ
    Registrato dal
    Jun 2011
    LocalitÓ
    A volte qua, a volte la ...
    Messaggi
    29,472
    Thanks
    1,370
    Thanked 11,783 Times in 7,929 Posts
    Predefinito

    POST 8

    Guida dualbooting BY droidphile



    Quote Originariamente inviato da droidphile Visualizza il messaggio
    We will explore some of the exclusive features in ICS kernels, ofcourse brought in by XDA devs and not Samsung themselves.
    Any feature is best explained through answers for different kind of questions. Atleast, that's what i believe
    We have dual-booting and bln breathing to start with. Features are originally brought in by gokhanmoral and is available in a few kernels like Siyah as of now.


    1. Dual Booting

    1) "So what's dual booting?"
    A. Option to boot into either of two ICS roms - aosp or sammy. Immediately after the boot logo, there is a 3 seconds time-out where you can boot into secondary rom by pressing the home key/volume down key. To boot into primary rom, wait for 3 seconds time-out to complete. If you don't like to wait - touch the screen, or press power key or press volume up key.

    2) "What's the basic architecture behind dual booting?"
    A. Any rom will have /system, /data, /cache partitions and requires a kernel to boot. Primary rom has all these partitions on the same location and partitions as if you were single-booting. ie, /dev/block/mmcblk0p12 for /system and rootfs for /data and /cache. Secondary rom uses a hidden partition (/dev/block/mmcblk0p9) for /system and sdcard to store /data and /cache partitions. They're stored in /sdcard/.secondrom directory as mountable ext4 block device images (data.img and cache.img).
    Kernel partition is shared, so same kernel boots both the roms. If you switch from Siyah to a different kernel, dual booting will not be available even though there's a clone of secondary rom. Internal sdcard, external plastic sdcard, /efs, /emmc, other kernel related virtual filesystem directories, etc are shared among roms.

    3) "I have just one rom now. How do i setup one more rom to dual boot?"
    A.
    -To use current rom as primary: Assuming the other rom is downloaded and copied to phone memory

    Easy Method
    i) Flash latest Siyah that supports dual boot.
    ii) Wipe data and cache of second rom using format /secondrom_cache and format /secondrom_data options under dual boot menu in recovery.
    iii) Flash rom zip as second rom directly using "Install zip to 2ndROM from internal SD" or "Install zip to 2ndROM from external SD" under dual-boot options in Recovery.

    Old/Alternative Method if Easy Method fails
    i) Flash latest Siyah that supports dual boot.
    ii) Nandroid backup your existing rom.
    iii) Full wipe, install the rom you need to dual boot into.
    iv) Boot into that rom, perform initial setups, flash whatever zip you need to flash on that rom - gapps, themes, mods, etc.
    v) Flash latest Siyah on this rom.
    vi) Boot into recovery, under dual-boot options, select "Clone Primary ROM to Secondary". Be patient and wait about 6-7 minutes. Now the new rom is secondary rom.
    vii) Within recovery, restore nandroid backup. Now, the existing rom becomes primary.
    viii) Just to be sure, flash latest Siyah again.

    -To use current rom as secondary: Assuming the other rom is downloaded and copied to phone memory

    Easy Method
    i) Flash latest Siyah that supports dual boot.
    ii) Boot into recovery, under dual-boot options, select "Clone Primary ROM to Secondary". Now your existing rom becomes secondary.
    iii) Full wipe and install the Rom you want to use as primary.
    iv) Flash latest Siyah just to be sure.

    Alternative Method
    i) Flash latest Siyah that supports dual boot.
    ii) Wipe data and cache of second rom using format /secondrom_cache and format /secondrom_data options under dual boot menu in recovery.
    iii) Flash rom zip as second rom directly using "Install zip to 2ndROM from internal SD" or "Install zip to 2ndROM from external SD" under dual-boot options in Recovery.
    iv) Select "Swap 1st Rom and 2nd Rom" under dual-boot options in recovery.

    Now you have two roms. Press home key to boot into second rom when time-out is displayed.

    4) "How much time was it to clone a rom?"
    A. There's /system, /data/ and /cache to clone. 2 GB data + 103mb cache + 513 mb system = 2.6 gb
    Shell prompt read speed = 7mb per second.
    Total Time = 2.6*(1024/7) = 380 secs = 6/7 minutes.

    5) "If i reboot to recovery from power-off state using 3 button method, to which rom's recovery it's booted into?"
    A. Unified kernel, same recovery. And remember - flashing zips to second rom is not possible as of now.

    6) "Any solution to flashing zips to secondary rom?"
    A.
    Yes. Use Install zip to 2ndROM from internal SD" or "Install zip to 2ndROM from external SD" under dual-boot options in Recovery.
    Alternative 1:
    If you know what the updater script in the zip is doing, you can do that manually using Root Explorer (replacing/copy files, setting permissions, etc).
    Alternative2:
    i) Swap 1st Rom and 2nd Rom using Dual-boot options in recovery. Now your 2nd rom becomes primary for time being.
    ii) Install zips like normal.
    ii) Swap again.

    7) "Should i have same versions of kernels on both roms? If not, from which rom should i flash the kernel"
    A. Flash kernel from any rom (if cwm app/darkyota is used). Both uses the same kernel partition anyway.

    8) "Will i get a prompt to dual-boot if i'm not using dual boot, as in i haven't cloned any rom to use as secondary?"
    A. NO

    9) "I don't like waiting for 3 seconds to boot into primary rom."
    A. Touch the screen/press volume up key immediately upon prompt.

    10) "How to undo dual booting?"
    A. Use "Remove 2ndRom" from dual-boot options in recovery.

    11) "How to remove secondary rom if "Remove 2ndRom" in touch recovery fails for some reason?"
    A. Format 2nrom /system partition from dualboot options in recovery, remove data.img and cache.img under /sdcard/.secondrom directory manually by booting into primary rom. Also delete /secondrom directory.

    12) "So if at all i format /sdcard, my second rom is gone?"
    A. Yes

    13) "Is the size of /system partition of secondary rom re-sizable from user space?"
    A. NO

    14) "Can i have both aosp roms/both samsung roms/first aosp, second samsung/first samsung,second aosp?"
    A. Yes

    15) "Can i have one GB rom and second ICS rom?"
    A. No

    16) "Why?"
    A. Kernel partition is shared between roms. Dual boot functionality is implemented in ICS kernel. ICS kernel can run only ICS roms.

    17) "Can i have different kernels for the two roms?"
    A. NO. Kernel partition is shared.

    18) "USB mass storage works?"
    A. Yes. Both cards will be mounted for primary and secondary roms. MTP works too.

    19) "If i had the same /data partition shared between roms, i could use same apps on both roms."
    A. Data partition can not be shared as they're incompatible between roms. (Sometimes dev asks you to perform full wipe even if you're switching between versions of the same rom right). Even if they were shared, separate dalvik caches has to be used and hence every boot will take a long time to rebuild dalvik.

    20) "How do i swap primary and secondary roms?"
    A.
    Easy Way:
    In recovery, select "Swap 1stRom and 2ndRom". It may take upto 20 minutes. Be patient and watch the progress bar.

    Difficult way: If the "swap" in recovery fails,
    i) Select "Backup secondary rom" under dual boot options.
    ii) Under original Backup and Restore option, select "Backup" to nandroid backup your primary rom.
    iii) Under dual boot options, "Restore as secondary rom" or "Restore as secondary rom from internal sd" and select the nandroid backup of what was actually your primary rom.
    iv) Under original Backup and Restore option, select "Restore" to restore the rom you backed up as secondary.

    21) "How to upgrade primary rom?"
    A. As usual, goto recovery, wipe whatever you need to wipe and install the new version. Remember to flash latest Siyah after upgrading if the Rom comes with a different kernel.

    22) "How to upgrade secondary rom?"
    A. Use "Install zip to 2ndROM from internal SD" or "Install zip to 2ndROM from external SD" under dual-boot options in Recovery. to flash the Rom zip. If any wipe is required, use format /secondrom_cache, format /secondrom_dalivkcache, format /secondrom_data and format /secondrom_system under Mounts & Storage in recovery.
    Alternative 1, if the above fails:
    Temporarily convert secondary rom to primary (by swapping them in recovery), flash rom zip revert primary back to secondary by swapping again. Remember to flash latest Siyah after upgrading. (This is just to be sure. Flashing zip to second rom does not change kernel)

    23) "How to replace secondary rom with another?"
    A.
    Easy Way:
    i) Wipe second rom partitions using format /secondrom_cache, format /secondrom_dalivkcache, format /secondrom_data and format /secondrom_system.
    ii) Install Rom zip using Install Zip to 2ndROM from internal SD or external SD from dual-boot options in recovery.
    Difficult Way:
    Perform the steps to setup dual boot as if you had only one rom which is going to be used as primary rom.

    24) "How to replace primary rom with another?"
    A. Normal procedure - wipe, install from recovery.

    25) "Are init.d scripts and extweaks profiles shared across the roms so that i can make changes by booting into any rom and the other rom automatically inherits the settings?"
    A. NO. Roms have differet /system partitions so different init.d directories. Roms uses different /data partitions so different extweaks settings since extweaks profiles are stored under /data/.siyah. Configure both separately. Initramfs scripts are shared anyway because Roms use the same kernel.
    Ultima modifica di JacOcaJ; 08-10-12 a 12:51

  17. I seguenti Utenti 2 hanno ringraziato JacOcaJ per il post:

    Emans (23-11-12)

  18. #9
    Super Moderator L'avatar di JacOcaJ
    Registrato dal
    Jun 2011
    LocalitÓ
    A volte qua, a volte la ...
    Messaggi
    29,472
    Thanks
    1,370
    Thanked 11,783 Times in 7,929 Posts
    Predefinito

    POST 9

    Continua guida dualbooting




    Quote Originariamente inviato da droidphile
    26) "Can i use titanium to backup and restore apps on both roms?"
    A. Yes. With the default settings of titanium backup, it uses /sdcard/TitaniumBackup directoryto backup apps. Assume you have the same app installed in both roms and you backed up the app from both roms. Then when you restore app+data, the last backup is restored. (regardless of from which rom was it backed up last. Because the app database is overwritten for each backup). If you want to maintain exclusiveness between apps in the two roms, use a different backup directory in second rom. Reason for exclusivity could be - you need different settings for same app in the roms OR you have reached level 2 of a game in rom1 and level 6 in rom2 and you need to maintain that, etc.

    27) "What're the Dual Boot options available in touch recovery?"

    A.
    i) View Current Status
    Displays secondary rom info if found.
    ii) Clone 1stRom to 2ndRom
    First time, you will have only one rom. You may clone it as secondary rom (so that another rom can be used as primary). Note that what was Primary rom will remain as Primary after this. In short - you will copy of same rom and 1st and 2nd.
    iii) Clone 2ndRom to 1stRom
    Whatever has been cloned as second Rom is cloned to first rom. Note that what was Second rom will remain as Second after this. In short - you will copy of same rom and 1st and 2nd.
    iv) Remove 2ndRom
    Remove second Rom by Deleting /system, /data and /cache partitions of second rom. You will have normal booting.
    v) Swap 1stROM and 2ndROM
    Swaps primary and secondary roms by exclusively overwriting /system /data and /cache of both roms. This is a time consuming process. Be patient.
    vi) Backup 2ndROM
    Nandroid backup secondary rom to external sd.
    vii) Restore as secondary rom
    Restore any nandroid backup as secondary rom from external sd.
    viii) Backup 2ndROM to internal SD
    Nandroid backup secondary rom to internal sd.
    ix) Restore as 2ndROM from internal sd
    Restore any nandroid backup as secondary rom from internal sd.
    x) init second rom data
    Initialize /data parition of secondary rom to resize the partition to make it bigger in case you run out of space for apps. Init also wipes all the data in /data partition. So your existing apps in secondary rom will be gone.
    xi) wipe second rom davik cache, xii) fix permissions in second rom - self explanatory
    xiii) Install Zip to 2ndROM from Internal SD xiv) Install Zip to 2ndROM from External SD- self explanatory
    xv) Wipe options for Second ROM can be found under Mounts and Storage - / format /secondrom_cache, format /secondrom_dalivkcache, format /secondrom_data and format /secondrom_system.
    Mounting partition options for 2nd ROM can also be found there.

    28) Why is "cloning 1stROM to 2ndROM" slower than "cloning 2ndROM to 1stROM"?
    A. While cloning primary to secondary, it writes data.img and cache.img to internal sd card. While cloning secondary to primary, the images are written to device memory or rootfs. This is faster than writing to a mounted storage.

    29) "Why can't internal SD be mounted with secondary rom whether it's sammy or aosp?"
    A. It works now.
    /data and /cache partitions of secondary rom resides in the internal sd. (/sdcard/.secondrom). So internal sd can not be unmounted to mount it to the PC. MTP works for internal SD too. Even though slower, that's the only option we got.

    30) "After setting up Second Rom, i don't see a prompt to boot into second rom".
    A. Try wiping Second Rom Cache and Dalvik.

    31. "Before wiping 2ndROM data/cache, i had some free space on internal sdcard. During wipe it failed and that space has dissipated. Even after a successful wipe, the space is still lost."

    A. Try (1). If it fails, try (2)
    1) Delete files in /sdcard/.secondrom directory.
    2) The space was occupied by lost.dir in /sdcard. Delete contents in that directory and you have the space back now.

    32. "What's happening when i wipe /data and /cache of 2ndROM during the first time setup of dual boot?"
    A. Two empty mountable EXT4 images - data.img and cache.img are created in /sdcard/.secondrom. While flashing zips to second rom, /data and /cache of second rom needs to be mounted in respective mmcblk. This empty .img files helps zip flashing without having the trouble to create them first.

    33. "Will flashing a rom zip to second rom (when i already have dual booting) change kernel? I may lose dual boot if so."
    A. NO. Flashing kernel is prevented for second rom if the zip contains a kernel.

    34. "I lost dual booting after i flashed primary rom via odin". I flashed kernel again. I could see files in /sdcard/.secondrom. But no dual boot. Help"
    A. Some carrier branded firmwares and such may wipe and push some apks and csc stuffs to the hidden partition used as /system of second rom. About 100 MB is used i think. After first reboot, it's never used again, but now you have lost /system of second rom even though data and cache are intact in SD.
    Copy data.img and cache.img of secondrom from /sdcard/.secondrom to PC. Then modify your zip installer of your second rom to install only /system of second rom. (Edit updater-script in the zip to comment out lines that write to /data).
    Now full wipe second rom /data and /cache. Format second rom /system. Flash the modified zip to second rom. Copy back and replace data.img and cache.img from your PC. Second rom should be intact now.



    Quote Originariamente inviato da droidphile
    2. Bln breathing

    q. What's bln breathing?
    a: with bln apps like bln control pro, we could set lights to be statically lit or blink when a notification arrives. A third effect could be achieved - breathing. Lights can follow a pattern to fade in and fade out. Infinite possibilities exist for pattern since the tunables that control breathing can be set from the user space.

    q. How is breathing achieved?
    a: a series of incidents using three principles: Vary led voltage level from a min to max and then max to min, pause between voltage changes, supply a different voltage as next voltage defined by a voltage step.

    q. Make it more clear?
    a. Let's take an example.
    Echo "2500 3300 70 50" > /sys/class/misc/notification/breathing_steps
    echo "3300 2500 70 50" > /sys/class/misc/notification/breathing_steps

    first two parameters defines star and end voltages/ min and max voltage (unit millivolts). Third parameter is the period or pause (in milliseconds) between voltage changes. Last parameter is the voltage step in millivolts.
    As you notice, there's on more echo statement which reverse the voltage limits. This is because breathing is asymmetric. So commands for fade in (light on) and fade out (light off) need to be written separately.

    Some points to note:
    -2550 is the minimum voltage to turn leds on.
    -3300 is the maximum voltage that's supported by regulator.
    -2500 is the minimum voltage supported by kernel as the least among valid voltage.
    -period should be echoed as milli seconds.
    -voltage step should be a multiple of 50.

    small tutorial: suppose you need a pattern - short, long, short breathes. Let's call this .._ when a notification arrive, it will repeat until notification times out .._ .._ .._

    #first enable breathing:
    Echo "1" > /sys/class/misc/notification/breathing
    #reset existing pattern:
    Echo "reset" > /sys/class/misc/notification/breathing_steps
    #now echo as many fade ins and fade outs you need. The file will parse all these without overwriting. (if you cat the file, it may return only last echoed line. Don't worry)
    echo 2600 3300 30 150 > /sys/devices/virtual/misc/notification/breathing_steps //short breathe achieved using lower period and higher voltage steps
    echo 3300 2600 30 150 > /sys/devices/virtual/misc/notification/breathing_steps //fade out for short breathe by swapping voltage limits
    echo 2500 3300 60 50 > /sys/devices/virtual/misc/notification/breathing_steps //long breathe achieved by increasing period and decreasing voltage step
    echo 3300 2500 60 50 > /sys/devices/virtual/misc/notification/breathing_steps //fade out for longer breathe
    echo 2600 3300 40 150 > /sys/devices/virtual/misc/notification/breathing_steps //another short breathe
    echo 3300 2600 40 150 > /sys/devices/virtual/misc/notification/breathing_steps //fade out
    echo 2500 2500 400 50 > /sys/devices/virtual/misc/notification/breathing_steps //having same voltage limit (that too 2500 which won't turn on led) and some period means a pause between breathing cycles. This will give a relaxed effect.

    q. How can i achieve blinking?
    a. echo same voltage as min and max voltage for fade in and fade out effects.
    Echo "2500 2500 500 100" > /sys/class/misc/notification/breathing_steps
    echo "3300 3300 500 100" > /sys/class/misc/notification/breathing_steps

    reducing the period to a smaller number say 100, gives you a faster blinking - a pulse effect.
    Ultima modifica di JacOcaJ; 12-11-12 a 10:22

  19. I seguenti Utenti 2 hanno ringraziato JacOcaJ per il post:

    Emans (23-11-12)

  20. #10
    Androidiano VIP L'avatar di alegu
    Registrato dal
    Jun 2011
    LocalitÓ
    MILANO
    Messaggi
    4,496
    Smartphone
    S3/NOTE3
    Thanks
    371
    Thanked 2,293 Times in 1,568 Posts
    Predefinito

    DI SEGUITO UN PAIO DI SUGGERIMENTI PER SETTARE IL KERNEL SIYAH


    SETTING DI DROIDPHILE DIRETTAMENTE DA XDA(SU CONSIGLIO DI ILLUMINATO67)

    http://forum.xda-developers.com/show...php?p=35149008


    PER CHI FOSSE INTERESSATO A MAGGIORI PRESTAZIONI ECCO IL SETTAGGIO DI LUCA_VIVI (RINGRAZIATE LUI MI RACCOMANDO)(CLICCA SU SPOILER)


    Spoiler:



    PER CHI FOSSE INTERESSATO A MINORI PRESTAZIONI MA UNA LEGGERA AUTONOMIA IN PIU' ECCO IL SETTAGGIO DI PINCOPALLINO(CLICCA SU SPOILER)

    Spoiler:


    IMPOSTAZIONI DI RICCARDOPOLARIS (CLICCA SU SPOILER)






    PER CHI VUOLE CONDIVIDERE LE PROPRIE IMPOSTAZIONI SENZA SCRIVERE TROPPO...


    1)Scaricate "stweaks profile 0.xx" da qui
    http://forum.xda-developers.com/show...php?p=35149008
    2)Scaricate "profilesforsiyah" e lo flashate in cwm
    3)Poi riavviate "stweaks profile 0.xx" e dal menu "restore" vi trovate 5 profili...il nome Ŕ molto intuitivo dei profili e scegline uno...ecco fatto.
    4)Per chi vuole condividere con tutti...fate cosi...aprite l'apk "stweaksprofile0.xx" ed effettuate il backup delle vostre impostazioni col vostro nick androidiani e numero del kernel...
    5)ora andate con programmi tipo root explorer in "data/siyah" e copiate il file col vostro nick nella sdinterna e mettetelo in un cloud.
    6)Copiate il link nel cloud e me lo mandate in pm che aggiornero' questo post con quelli di chiunque.
    7)Viceversa se vi interessano quelli di qualcuno qui postato...non fate altro che fare il download e mettere il file sempre in "data/local" e avviate l'apk "stweaksprofile 0.xx" e selezionate il nome del profilo predownloadato...


    1)kelevra989 https://www.dropbox.com/s/atpd1hw4br...yha188.profile
    Ultima modifica di alegu; 26-01-13 a 20:24

  21. I seguenti Utenti 20 hanno ringraziato alegu per il post:

    AldoGS3 (08-03-13),Beo8513 (29-11-12),bick96 (25-03-13),blasf70 (26-01-13),Bricktom (29-11-12),daneel62 (21-11-12),enzoroot (07-12-12),ilovehc (14-01-13),kelevra989 (18-01-13),kingalessandro (31-05-13),Locaa92 (16-01-13),lorenzo63 (03-12-12),mythos (18-03-13),Pietrone94 (18-01-13),Ragz (06-02-13),Steccas (13-12-12),stefal639 (15-01-13),thespeed20 (11-12-12),TopoMonko (18-01-13)

Pagina 1 di 256 1231151101 ... ultimoultimo

Permessi di invio

  • Non puoi inserire discussioni
  • Non puoi inserire repliche
  • Non puoi inserire allegati
  • Non puoi modificare i tuoi messaggi
  •