[Kernel][24/04] Perseus

Search This thread

AndreiLux

Senior Member
Jul 9, 2011
3,209
14,598
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.
 

Attachments

  • Perseus-alpha36.2-i9305.tar
    5.8 MB · Views: 4,137
  • Perseus.alpha36.2-i9305-CWM.zip
    5.9 MB · Views: 5,472
Last edited:

btemtd

Senior Member
Aug 8, 2012
2,052
1,002
We are actually contemplating the fm radio because one user actually had it on his firmware working so we wanted to compile a kernel with fm radio .

Can we actually try?

Sent from my GT-I9305 using xda app-developers app

---------- Post added at 04:04 PM ---------- Previous post was at 04:02 PM ----------

I can upload if you tell me where I can get it

Sent from my GT-I9305 using xda app-developers app
 
  • Like
Reactions: jetbruceli

leamoor

Senior Member
Dec 25, 2010
300
144
hong kong
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.
  • LCDFreq might not work [WIP]
  • 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.

__________

The kernel is compiled and ready, now, if somebody would please upload the stock kernel only somewhere, so I don't have to wait 2 hours on downloading the SamMobiles whole firmware zip from Hotfile (I'm at the daily traffic limit, eh.), it would be appreciated. I just need to check the ramfs to see if there's any dramatic changes and eventually adapt that. Apparently nobody on the internet or this forum thought of uploading this yet.

I only have ZHALI8 this firmware
 

Attachments

  • boot.img
    4.8 MB · Views: 316

btemtd

Senior Member
Aug 8, 2012
2,052
1,002
This is probably the best one to use its the latest http://d-h.st/AMs Boot.img from the base firmware XXLI9 latest,

Thanks to prodigiez

I cannot wait to get our first custom kernel which we can over clock and turn our Gems into Weapons
 
Last edited:

AndreiLux

Senior Member
Jul 9, 2011
3,209
14,598
I tried to compile with FM radio but it fails due to platform dependencies, there is something weird going on with the 9305 in that regard, I'll check it out later.

Anyway, here we go: Please test and report back.
 
Last edited:
  • Like
Reactions: _ray_ and btemtd

btemtd

Senior Member
Aug 8, 2012
2,052
1,002
Thanks dude I will try this now... It would be great if someone could figure this FM thing out, As even samsung said It is up to the carrier if they wish to include FM radio which to me means there is capability
 
Last edited:

btemtd

Senior Member
Aug 8, 2012
2,052
1,002
Thanks dude I will try this now... It would be great if someone could figure this FM thing out, As even samsung said It is up to the carrier if they wish to include FM radio which to me means there is capability

ALL I CAN SAY IS IT WORKS PERFECTLY I AM NOW OVERCLOCKED TO 1704MHZ Just like I was on my favourite Nandroid I9300 ICS

Check out my Quadrant screenshot


LIKE A BOSS!
 
  • Like
Reactions: _ray_

AndreiLux

Senior Member
Jul 9, 2011
3,209
14,598
If there are no reported issues I'll put it up in the first post together with a CWM soon. Also, somebody needs to check if the partition is still mmcblk0p5 for the kernel. On the Note 2 they changed the partition to mmcblk0p8 and I didn't know about it and the CWM didn't work.
 

btemtd

Senior Member
Aug 8, 2012
2,052
1,002
If there are no reported issues I'll put it up in the first post together with a CWM soon. Also, somebody needs to check if the partition is still mmcblk0p5 for the kernel. On the Note 2 they changed the partition to mmcblk0p8 and I didn't know about it and the CWM didn't work.

how do I check? Could we also have something like stweaks so we can tweak our stuff? without the need to download other random apps

---------- Post added at 04:38 AM ---------- Previous post was at 04:32 AM ----------

So far Everyhing works perfect, AND SUPER SUPER FAST WOOOOO this is a WEAPON now...

Only thing different i noticed is a TINY (2mm) exclamation mark in the top left hand corner, when you boot up stays on for like 5 secs then goes away... It only used to show when I was going into recovery mode before
 
Last edited:

prodigiez

Senior Member
Nov 8, 2008
497
216
If there are no reported issues I'll put it up in the first post together with a CWM soon. Also, somebody needs to check if the partition is still mmcblk0p5 for the kernel. On the Note 2 they changed the partition to mmcblk0p8 and I didn't know about it and the CWM didn't work.


hope this helps you

lrwxrwxrwx root root 2012-10-08 21:43 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-08 21:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-10-08 21:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-08 21:43 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-08 21:43 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-10-08 21:43 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-10-08 21:43 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-08 21:43 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-08 21:43 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-08 21:43 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-08 21:43 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs3 -> /dev/block/mmcblk0p6
 

qwerty12

Senior Member
Jan 21, 2005
472
343
(*Europe).London
Only thing different i noticed is a TINY (2mm) exclamation mark in the top left hand corner, when you boot up stays on for like 5 secs then goes away... It only used to show when I was going into recovery mode before

Probably because you're running a kernel not signed by Samsung. This thread talks of the same happening on the I9300. Please don't flash any bootloaders from that thread...
 
  • Like
Reactions: kazuni and btemtd

kazuni

Senior Member
Aug 28, 2007
667
208
Hong Kong
Thanks for the kernel, it's a great start - and it works well on my device as well. Much appreciated!:good::good:
 

AndreiLux

Senior Member
Jul 9, 2011
3,209
14,598
Should work fine on I9305 & i9305t

Sent from my GT-I9305 using xda app-developers app
NO. It wont work on the T model, the hardware is different, it didn't have a different model number for nothing. If anything, I'll do a separate kernel, but don't try it on anything else than the I9305.
 

singlecell83

Senior Member
Sep 12, 2012
155
24
NO. It wont work on the T model, the hardware is different, it didn't have a different model number for nothing. If anything, I'll do a separate kernel, but don't try it on anything else than the I9305.

You think telstra had their own version developed? I dont think so. I installed the optus rom on my telstra phone and it worked flawless. Unless there is something very minor....
Edit: Now installed on my 9305T. Never used a custom kernal without having a whole new rom also. So not sure what its actually meant to be doing....


Sent from my GT-I9305 using xda premium
 
Last edited:

btemtd

Senior Member
Aug 8, 2012
2,052
1,002
Exactly what I thought when I had the i9300t everything worked exactly like the i9300 I was able to intexchange modem roms kernel etc.... now we have users with i9305t which flashed i9305 Rom and kernel with no problem at all. I dont see why it wouldn't work.

And the hardware is actually the same I am pretty sure of it.

Sent from my GT-I9305 using xda app-developers app

---------- Post added at 09:51 AM ---------- Previous post was at 09:44 AM ----------

You think telstra had their own version developed? I dont think so. I installed the optus rom on my telstra phone and it worked flawless. Unless there is something very minor....
Edit: Now installed on my 9305T. Never used a custom kernal without having a whole new rom also. So not sure what its actually meant to be doing....


Sent from my GT-I9305 using xda premium

Now you can modify and enhance your cpu and gpu and other tweaks best of to know what u are doin before playing.

SO THERE YOU HAVE IT WORKING ON I9305T AND I9305 JUST LIKE I THOUGHT

Sent from my GT-I9305 using xda app-developers app
 
Last edited:

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.