[Kernel][24/04] Perseus

Search This thread

Rekoil

Senior Member
May 17, 2008
1,143
497
Göteborg
www.idroidproject.org
Just gonna post this here, I don't know exactly what has happened, but basically after using this kernel for a while I am unable to return to a stock kernel as only Perseus kernel is able to initiate my baseband. I believe I may have either backed up my modems NVDATA or restored an old NVDATA backup while running this kernel and that that is what has caused the problem.
 

Obagleyfreer

Senior Member
Jun 29, 2012
2,019
844
Wellington
Awesome new update!

Is it totally weird I actually squeeled like a girl when I saw a new Perseus Kernel version haha
Man I need to get out more!
 

omniwolf

Senior Member
Jan 13, 2005
997
474
sydney
has anyone tried using this on a phone running either CM or liquidsmooth ROMs?

The kernel is only for Samsung ROMs. Andrei has been mostly quiet on the topic of AOSP/dual boot support, and due to the fact that a million people have asked for it this can mean one of two things - he is either against the idea, or secretly working on it in the background.
 

AndreiLux

Senior Member
Jul 9, 2011
3,209
14,598
Re: [Kernel][26/02] Perseus

The kernel is only for Samsung ROMs. Andrei has been mostly quiet on the topic of AOSP/dual boot support, and due to the fact that a million people have asked for it this can mean one of two things - he is either against the idea, or secretly working on it in the background.
I'm not really against it, I just don't bother with it for now.
 

husky69

Senior Member
Oct 8, 2011
982
210
Samsung Galaxy Tab 4
LG G6
Hi,
got a bit of an emergency here. Maybe someone got a useful hint for me?
I've been running X-Power 3.0 ROM with Perseus kernel 32.1 so far and just finished undervolting the kernel via SetCPU - ROM booted up fine afterwards.
But today I decided to give Perseus 33 a try, and after flashing the TAR with ODIN mobile my phone won't boot again - it shows the "Galaxy S III" screen, blanks the screen again and then restarts again - I can't get the phone into recovery or download mode :(

Any hints on how to solve this one?
 

AndreiLux

Senior Member
Jul 9, 2011
3,209
14,598
Hi,
got a bit of an emergency here. Maybe someone got a useful hint for me?
I've been running X-Power 3.0 ROM with Perseus kernel 32.1 so far and just finished undervolting the kernel via SetCPU - ROM booted up fine afterwards.
But today I decided to give Perseus 33 a try, and after flashing the TAR with ODIN mobile my phone won't boot again - it shows the "Galaxy S III" screen, blanks the screen again and then restarts again - I can't get the phone into recovery or download mode :(

Any hints on how to solve this one?
You can ALWAYS go into recovery. Just hold Vol-Up & Home & Power longer.

33.2 contains the calibrated data for the S3 panel. Enjoy.
 
  • Like
Reactions: yshaikh01

maranello69

Senior Member
Apr 1, 2011
820
179
EU
in the About section i still get v33 for kernel, and i flashed it twice via cwm, i gues the build number is not updated?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 104
    Identical kernel to the i9300 one. Only difference is:
    • CMA device memory allocation is gone as we don't need the hacks used in it for larger memory, 2GB with the default setting will suffice.
    • You apparently have no FM radio.

    The port is trivial and everything else should work flawlessly.

    Please refer to the I9300 thread for changelogs, bug-reports and other issues. Kernel itself will be posted here.
    26
    Hello AndreiLux ,

    is this project still allive?

    Regards

    Sonic76

    +1 Been wondering the same question

    Sent from my GT-I9305 using xda premium
    I've told you guys the i9300 will always be first to get new versions since that's what I have to develop on, test, and use. Please refrain from such posts because I will update here as well (i9305 users are first in line before the 7 different Note 2 versions...). I also use the i9300 as a testbed for fast feedback in case of bugs, and that's why you people for example never get non-hotfixed versions first because things will already have been debugged on the i9300.

    So, with that in mind, uploading 30.1 now for here. Please read the changelog in the main thread.
    11
    Important security update in v29. Please update.
    9
    Basic, not very scientific UV test

    Hi Guys,

    I finished my two days of UV and non UV testing.
    TL;DR: UV seems to help a decent amount, I think it's worth the hassle.

    What did I undervolt?
    I spent weeks undervolting my CPU, GPU, internal, and memory components. I then went through each component, and used the ABB interface to see if I could further undervolt. On the CPU I could undervolt a little bit further, on the GPU and internal I could get a decent amount of extra UV, on the memory component I could gain no further UV with ABB. Please note I'm unsure about the GPU undervolting - there appears to be a bug with the GPU frequency or volt_table interfaces, more on that HERE and HERE.

    Click HERE to see my full undervolting, but for a quick idea, here are my average undervolts for each component:
    CPU: 155mV
    GPU: 147mV
    Internal: 175mV
    Memory: 150mV

    Not bad for an ASV3 chip :)

    How did I test?
    Both days I took it off the charge at midnight, and left it off the charge for the next 18 hours. Used BetterBatterStats to monitor everything, I tried to use the phone in exactly the same way both days - about 1h30m screen on time, which included about 20mins of candy crush saga, both days push syncing an exchange account from 8am - 6pm, all google services on push (google now disabled), about the same SMSs, same amount of wifi and 4G, I think I was pretty consistent.

    I wish I had more time to knock off a few more tests, but my i9505 came in, and I've already left it in the box for 2 days.. I can't resist anymore :)

    Results!
    Day 1: undervolting applied.
    Code:
    Since 17 h 59 m 12 s 
    Level lost [%]: Bat.: -70% (87% to 17%) [3.9%/h]
    Deep Sleep (): 12 h 31 m 30 s  (45090 s) Ratio: 68.1%
    Awake (): 5 h 27 m 42 s  (19662 s) Ratio: 30.4%
    Screen On (): 1 h 32 m 30 s  (5550 s) Ratio: 8.6%
    No or Unknown Signal (): 15 h 24 m 29 s  (55469 s) Ratio: 85.7%
    Moderate Signal (): 3 m 28 s  (208 s) Ratio: 0.3%
    Good Signal (): 1 m 44 s  (104 s) Ratio: 0.2%
    Screen dark (): 1 h 8 m 44 s  (4124 s) Ratio: 6.4%
    Screen dimmed (): 2 m 25 s  (145 s) Ratio: 0.2%
    Screen medium (): 19 m 10 s  (1150 s) Ratio: 1.7%
    Screen light (): 41 s  (41 s) Ratio: 0.1%
    Screen bright (): 1 m 27 s  (87 s) Ratio: 0.1%
    ================
    Kernel Wakelocks 
    ================
    "PowerManagerService" (): 1 h 34 m 12 s  (5652 s) Cnt:(c/wc/ec)6225/0/0 8.7%
    "mdm_hsic_pm0" (): 1 h 7 m  (4020 s) Cnt:(c/wc/ec)8091/427/0 6.2%
    "wlan_rx_wake" (): 42 m 18 s  (2538 s) Cnt:(c/wc/ec)2272/0/2273 3.9%
    "wlan_ctrl_wake" (): 37 m 40 s  (2260 s) Cnt:(c/wc/ec)847/0/847 3.5%
    "alarm_rtc" (): 29 m 3 s  (1743 s) Cnt:(c/wc/ec)3037/0/487 2.6%
    "hsicctl0" (): 16 m 34 s  (994 s) Cnt:(c/wc/ec)4687/0/4687 1.5%
    "alarm" (): 16 m 30 s  (990 s) Cnt:(c/wc/ec)4864/16/0 1.5%

    Day 2: stock voltages.

    Code:
    Since 17 h 55 m 26 s 
    Level lost [%]: Bat.: -85% (89% to 4%) [4.7%/h]
    Deep Sleep (): 12 h 21 m 57 s  (44517 s) Ratio: 68.2%
    Awake (): 5 h 33 m 28 s  (20008 s) Ratio: 31.0%
    Screen On (): 1 h 32 m 52 s  (5572 s) Ratio: 8.6%
    No or Unknown Signal (): 15 h 23 m 46 s  (55426 s) Ratio: 85.9%
    Moderate Signal (): 30 s  (30 s) Ratio: 0.0%
    Good Signal (): 4 m 38 s  (278 s) Ratio: 0.4%
    Screen dark (): 47 m 28 s  (2848 s) Ratio: 4.4%
    Screen dimmed (): 27 m 14 s  (1634 s) Ratio: 2.5%
    Screen medium (): 16 m 59 s  (1019 s) Ratio: 1.6%
    Screen bright (): 1 m 9 s  (69 s) Ratio: 0.1%
    ================
    Kernel Wakelocks 
    ================
    "PowerManagerService" (): 1 h 39 m 57 s  (5997 s) Cnt:(c/wc/ec)5937/0/0 9.3%
    "mdm_hsic_pm0" (): 1 h 9 m 1 s  (4141 s) Cnt:(c/wc/ec)8297/552/0 6.4%
    "wlan_rx_wake" (): 46 m 14 s  (2774 s) Cnt:(c/wc/ec)1902/0/1902 4.3%
    "wlan_ctrl_wake" (): 32 m 40 s  (1960 s) Cnt:(c/wc/ec)866/0/865 3.0%
    "alarm_rtc" (): 28 m 7 s  (1687 s) Cnt:(c/wc/ec)3281/0/377 2.6%
    "hsicctl0" (): 17 m 5 s  (1025 s) Cnt:(c/wc/ec)4627/0/4626 1.6%
    "alarm" (): 15 m 6 s  (906 s) Cnt:(c/wc/ec)5053/10/0 1.4%

    So, both days had the same:
    - Total time on
    - Screen on time
    - PowerManagerService wakelocks
    - mdm_hsic_pm0 wakelocks
    - signal variance

    The only real difference is the screen brightness, but I don't think this is enough to worry about.

    Battery level, however, the UVed config used 3.9% battery per hour, whereas the stock voltage config used 4.7% battery per hour. Over the 18 hours, this meant that with UV I had an extra 15% battery than I did with no UV.

    Caveat: I do think I used the phone slightly harder on the stock voltage test day, but only right at the end, i used google maps with GPS for about a minute, and I drove to the shops which I didn't do the day before. This may have made a % or two difference, but not 15%. To balance that a bit, I cut the test short on the second (no UV) test day, the overal % lost is probably about right.


    Hi @omniwolf,
    Thanks for sharing the profile. I tried the just the CPU and GPU settings and got a FC. Which version of the kernel are you using ? I'm using 36.2.
    Yes, this is with 36.2, but with this fix I posted to make it act like 36.3.
    8
    Hi Andrei,
    Any chance we can get the mods from alpha26 in the i9300 kernel in this one?
    Thanks :)
    Here you go. Sorry for not keeping up to date too much but some irritating people in this section and the minuscule user-base of this device makes me a bit lazy in releasing things.