[KERNEL] Semaphore N4 3.4.2

Search This thread
By:
Advanced…
thracemerin

thracemerin

Senior Member
Oct 19, 2011
5,458
5,764
Toronto
coloxim said:
So Waiting for semaphore on stock rom...
;)

Inviato dal mio Nexus 4 utilizzando Tapatalk
Click to expand...
Click to collapse

The J version of Semaphore is fully working on 4.4 stock, don't even need to flash the WiFi fix.

dmourao said:
Ehmmm... No translucent navbar and status bar. Firstly the exclusive GEL and now this... Bah! :(
Click to expand...
Click to collapse

This is because the transparent status bars are a feature of the Google Experience Launcher which is exclusive to the N5, if you sideload the Google Now and Launcher from the Nexus 5 you will have this, the N4 uses the older Launcher2 even for KitKat.
 

Attachments

  • Screenshot_2013-11-14-19-33-43.jpg
    Screenshot_2013-11-14-19-33-43.jpg
    70.4 KB · Views: 406
Last edited:
C4SCA

C4SCA

Senior Member
May 2, 2012
2,333
1,026
28
Samsung Galaxy Note 10.1
OnePlus One
thracemerin said:
The J version of Semaphore is fully working on 4.4 stock, don't even need to flash the WiFi fix.



This is because the transparent status bars are a feature of the Google Experience Launcher which is exclusive to the N5, if you sideload the Google Now and Launcher from the Nexus 5 you will have this, the N4 uses the older Launcher2 even for KitKat.
Click to expand...
Click to collapse

No need to side load google search (google now) its already updated on the factory images... Only sideload the launcher

sent from my NEXUS 4 tasting Kitkat for the first time.
 

Attachments

  • uploadfromtaptalk1384475909078.jpg
    uploadfromtaptalk1384475909078.jpg
    117.3 KB · Views: 408
Barbatos19

Barbatos19

Senior Member
Oct 3, 2012
602
80
Cotabato, City
DontPushButtons said:
^^^
Nope, edit: what fast-fingers there said ;)

I think kernel devs are still waiting for kernel source though..

Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse

thracemerin said:
The binaries are for building AOSP, you can ignore them entirely if you flashed the factory images.
Click to expand...
Click to collapse

thanks a lot for replying :). I downloaded the occam 4.4 and edited the flash-all.bat and remove the -w. does it mean that im good to run the flash-all.bat and my files wont be remove? got this tutorials here " http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/ "
 
thracemerin

thracemerin

Senior Member
Oct 19, 2011
5,458
5,764
Toronto
sushibabaes said:
thanks a lot for replying :). I downloaded the occam 4.4 and edited the flash-all.bat and remove the -w. does it mean that im good to run the flash-all.bat and my files wont be remove? got this tutorials here " http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/ "
Click to expand...
Click to collapse

Possibly, if you were on stock then it should be fine. If you are coming from a custom ROM (anything other than the stock factory images for 4.3) there is a good chance it either won't work or you will run into issues in the long run so it would be better to wipe.
 
Kocai

Kocai

Senior Member
Oct 24, 2011
1,476
690
thracemerin said:
Possibly, if you were on stock then it should be fine. If you are coming from a custom ROM (anything other than the stock factory images for 4.3) there is a good chance it either won't work or you will run into issues in the long run so it would be better to wipe.
Click to expand...
Click to collapse

It won't pass the boot animation if you're not on stock factory images. I tried that method before.
 
Barbatos19

Barbatos19

Senior Member
Oct 3, 2012
602
80
Cotabato, City
thracemerin said:
Possibly, if you were on stock then it should be fine. If you are coming from a custom ROM (anything other than the stock factory images for 4.3) there is a good chance it either won't work or you will run into issues in the long run so it would be better to wipe.
Click to expand...
Click to collapse

Kocai said:
It won't pass the boot animation if you're not on stock factory images. I tried that method before.
Click to expand...
Click to collapse

how about sideloading the factory image? does it go well? im on PA 3.99rc 2? any suggestions? or should i restore my stock rom first then do the flashing>?
 
A

aLPaSLaN07

Senior Member
Oct 5, 2010
436
65
Istanbul
1/10 , when recieving or making a phonecall, my phone reboots. I click "call" button and reboots. Same happens when somebody calls me. Before the screen turns on, phone rings, no screen on and reboot.. It happened after 1.7.6. Last kernel message log can be usefull to detect the bug?
 
B

beje86

Senior Member
Sep 2, 2010
179
66
sushibabaes said:
how about sideloading the factory image? does it go well? im on PA 3.99rc 2? any suggestions? or should i restore my stock rom first then do the flashing>?
Click to expand...
Click to collapse

I did exactly that with that ROM removing the "-w" in the KK factory image script to avoid the wipe and it went to crap. Looked like it worked nice for a moment but I instantly noticed that the Home button didn't work and that GEL (that I had installed previously) was FC'ing every few minutes. Tried to reboot and then it rendered itself unusable as GEL was FC'ing nonstop, not allowing me to do anything at all.

Long story short, make a backup of your stuff and then install cleanly.
 
You must log in or register to reply here.

Similar threads

franciscofranco
[KERNEL][GPL][N4] franco.Kernel - r217
Replies
58K
Views
11M
D
Draketech
CallMeAldy
  • Poll
[KERNEL] [N4] [6.0][3.4.0][AOSP/CM] [10/26] [M2] - AK
Replies
10K
Views
1M
RASTAVIPER
RASTAVIPER
faux123
[Kernel] (ver 041) Mako KK 4.4 (UV/OTG/CPU/GPU OC/Hybrid Linux 3.4+) [08-02-14]
Replies
17K
Views
3M
B
bubbleguuum
morfic
[DER KERNEL] Trinity Four (4.2/4.3)
Replies
27K
Views
2M
albundy2010
albundy2010
C
[ROM][Official][4.2.2] CyanogenMod 10.1 Nightlies for the Nexus 4 (mako)
Replies
14K
Views
3M
VinceCZ
VinceCZ

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 635
    stratosk
    stratosk
    semaphore_logo.png



    This is a kernel based on stock one, tested on stock KK 4.4.3, JB 4.2.2, CM10.1, JB 4.3, Lollipop 5.0


    Versions >= 3.0.0b are for Lollipop 5.1.x
    Versions >= 2.2.0 are for KK 4.4.3
    Versions >= 1.8.5 are for KK 4.4.1 / 4.4.2 only
    Versions >= 1.8.0 are for KK 4.4 only
    Versions >= 1.5.0 are for JB 4.3 only

    More features will be added soon. Please don't ask for ETA.


    Features
    - Linux kernel 3.4.112
    - built with Linaro gcc 4.8.2 201306
    - enabled O2 optimizations
    - ondemand (Changed calculation of frequency, tweaked)
    - conservative
    - mpdecision dropped
    - dyn_hotplug driver
    - Noop scheduler (default)
    - SIO scheduler
    - Touch wake
    - Double Tap to Wake
    - Gamma control
    - LED triggers: touchwake, thermal
    - Undervolting
    - removed many debug options

    For more information check the semaphore kernel website: www.semaphore.gr

    Please use Semaphore Manager application to control every kernel's feature.

    Thanks to
    - Linux developers
    - faux123 for ideas about gamma tables
    - Ezekeel for touchwake
    - my wife who always supports me
    - a German friend who helped to buy N4

    All people who support this kernel by testing, reporting issues, donating or simply using it.

    Thanks italia0101 for his review.

    Change log

    3.4.2 (19/05/2016)
    - Linux kernel 3.4.112

    3.4.1 (24/03/2016)
    - Linux kernel 3.4.111

    3.4.0 (02/11/2015)
    - Linux kernel 3.4.110

    3.3.0 (23/09/2015)
    - Linux kernel 3.4.109

    3.2.6 (16/08/2015)
    - Merge Android 5.1.1_r0.14 changes

    3.2.5 (21/06/2015)
    - Linux kernel 3.4.108

    3.2.0 (21/05/2015)
    - Merge Android 5.1.1 changes

    3.1.5 (20/04/2015)
    - Linux kernel 3.4.107
    - Double tap to wake: add option to temporarily disable after power key pressed. Auto enabled again after device resumed. Enable this feature using the command:
    echo 1 > /sys/devices/virtual/input/lge_touch/dt_wake_pwr_disable

    3.1.0 (15/04/2015)
    - Merge Android-5.1.0_r0.9 changes

    3.0.5 (22/03/2015)
    - cpufreq: new per cpu tunable util_threshold (default 25)
    - Dynamic hotplug: Change algorithm. If CPUs have different util_threshold, the CPU with the greater one will be chosen
    - ondemand: new tunable down_threshold. If load below this threshold lowest frequency will be user.

    3.0.2 (18/02/2015)
    - Linux kernel 3.4.106

    3.0.1 (11/12/2014)
    - Merge latest changes from Android source (5.0.1)

    3.0.0
    - Linux kernel 3.4.105
    - Fix initramfs issues (mpdfake, initscripts) due to SELinux. Semaphore init script uses Chainfire's supolicy tool (included in latests SuperSU) to patch sepolicy

    3.0.0b (18/11/2014)
    - Lollipop release
    - Merged latest lollipop branch
    - Linux 3.4.104

    2.4.0 (19/08/2014)
    - Linux kernel 3.4.103
    - ondemand: a small fix in check load condition (thanks to moddingg33k)
    - tick-sched: Remove unnecessary statistics calculation required by mpdecision (thanks to moddingg33k)
    - tick-sched: A couple of fixes from mainline

    2.3.3 (19/07/2014)
    - Linux kernel 3.4.99

    2.3.0 (27/06/2014)
    - Linux kernel 3.4.95
    - ondemand: Change the calculation of next frequency to utilize lower frequencies more (the governor will be more sensitive to lower loads)
    - ondemand: Change default touch load to 65 to keep the touch frequency to 1134MHz (because of the change in calculation)
    Please note that you have to change the touch load to 65 in Semaphore Manager until the app update.

    2.2.5 (15/06/2014)
    - Linux kernel 3.4.93
    - ondemand: Be friendly towards latency-sensitive bursty workloads (backport 2 patches that intended for 3.16)

    About Double Tap to Wake.
    Implemented from scratch and hints from show-p1984 and LG G pad kernels (thanks).

    The basic idea is known: touchscreen remains _always_ powered to handle input events
    and wake up the device with a double tap.
    User have to double tap on the _center_ of the screen (to limit accidentally wake ups).
    Double tap is disabled by default. To enable it run the command bellow as su:

    echo 1 > /sys/devices/virtual/input/lge_touch/dt_wake_enabled

    If you run the above command during screen off, the command will remain pending until
    the next power on. Then it will be actually executed.

    Touchwake functionality is still implemented and it should be disabled if double tap to wake
    is enabled.


    1.8.8 (22/12/2013)
    - Linux kernel 3.4.75
    - dyn_hotplug: Activate the driver 1min after boot (because during init scripts execution all CPUs should be online to get initial settings. Fixes issue where a CPU governor could be set with default performance governor. Thanks to ihancioglu for reporting and reproducing the issue).
    - cpufreq: set initial utilization to zero on device CPU addition

    Full changelog: http://www.semaphore.gr/changelog/n4-version


    Sources
    Semaphore kernel sources


    Please use it at your own risk!


    Zip files in download section are for flashing from CWM recovery.

    'j' versions are for JSS15J ROMs only
    The normal files are for JWR66V &JWR66Y ROMs only

    Alternative download from http://www.semaphore.gr/downloads/nexus-4

    XDA:DevDB Information
    Semaphore, Kernel for the Google Nexus 4

    Contributors
    stratosk
    Source Code: https://github.com/stratosk/kernel_msm

    Kernel Special Features:

    Version Information
    Status: Stable
    Current Stable Version: 3.4.2
    Stable Release Date: 2016-05-19

    Created 2013-07-30
    Last Updated 2016-05-19
    View
    189
    stratosk
    stratosk
    About undervolting

    As you may know, APQ8064 comes to 4 versions (PVS bin): Slow, Nominal, Fast, Faster.
    Every bin has it's own voltage table. Nominal bin chips use lower voltages than Slow bin,
    Fast lower than Nominal and finally Faster even lower voltages.

    Stock kernel uses a paramater boost_uV. By default, is added in voltages but it can be disabled.
    The value of boost_uV is 0 for Slow bin chips and 25000 uV = 25 mV for Nominal, Fast and Faster.

    The boost_uV may be disabled (= undervolting by 25000 uV in Nominal, Fast and Faster) using this command:

    Code: 
    echo n > /sys/module/acpuclock_krait/parameters/boost


    I implemented 3 more paramater that handle undervolting:
    - lower_uV: undervolting value for lower frequencies
    - higher_uV: undervolting value for higher frequencies
    - higher_khz_thres: above this frequency (default 1350000KHz) higher_uV will be used. Else lower_uV will be used.

    Undervolting value is subtracted from stock voltage. The final voltage for each frequency is calulated:
    Vdd(final) = Vdd(core) + boost_uV - uV

    So, to undervolt frequencies 384000-1242000 by 25mV and the other frequencies by 12.5mV use these command:

    Code: 
    echo 25000 > /sys/module/acpuclock_krait/parameters/lower_uV
echo 12500 > /sys/module/acpuclock_krait/parameters/higher_uV

    The higher_khz_thres maybe changed using this command (for example to use higher_uV from 981000KHz):

    Code: 
    echo 918000 > /sys/module/acpuclock_krait/parameters/higher_khz_thres

    Also, I added a debugfs file (acpuclk/acpu_table) to show the acpu table frequencies and voltages.
    For example to get the information about the current status use this command:

    Code: 
    cat /sys/kernel/debug/acpuclk/acpu_table

    and the output:

    Code: 
    CPU PVS: Fast
Boost uV: 25000
Boost uV enabled: No
Higher KHZ threshold: 1350000
Lower under uV: 37500
Higher under uV: 25000

CPU KHz  VDD(stock)  VDD(final)  Difference
 384000      875000      812500      -62500  
 486000      900000      837500      -62500  
 594000      925000      862500      -62500  
 702000      950000      887500      -62500  
 810000     1000000      937500      -62500  
 918000     1025000      962500      -62500  
1026000     1050000      987500      -62500  
1134000     1100000     1037500      -62500  
1242000     1125000     1062500      -62500  
1350000     1150000     1100000      -50000  
1458000     1162500     1112500      -50000  
1512000     1175000     1125000      -50000

    Please note that undervolting may cause instabilities in your phone. Be careful!
    View
    126
    stratosk
    stratosk
    reserved for future use
    View
    84
    stratosk
    stratosk
    New version 1.8.8
    - Linux kernel 3.4.75
    - dyn_hotplug: Activate the driver 1min after boot (because during init scripts execution all CPUs should be online to get initial settings. Fixes issue where a CPU governor could be set with default performance governor. Thanks to ihancioglu for reporting and reproducing the issue).
    - cpufreq: set initial utilization to zero on device CPU addition
    View
    79
    stratosk
    stratosk
    New version 2.1.1
    - Linux kernel 3.4.87
    View

New posts