[KERNEL] [N910C/H] [MM Stable] Perseus-Halaszk-universal5433 [06 May 2016]

[Gà super]

I found a rom CM12.1

All Info Can be Found here

https://github.com/halaszk/Perseus-halaszk-universal5433/wiki

.

I found a rom CM12.1 of n910c,I tested on my n910u ,it works but no network
I think the kernel,because I try to run it along your kernel
it has network but other things not work
Please help make it work on n910u
http://teameos.org
Thank you

 

[firefox1991]

I found a rom CM12.1 of n910c,I tested on my n910u ,it works but no network
I think the kernel,because I try to run it along your kernel
it has network but other things not work
Please help make it work on n910u
http://teameos.org
Thank you

the chip of modem h/c/u is different maybe that is the problem

Enviado desde mi SM-N910H mediante Tapatalk

 

[djmax81]

I found a rom CM12.1 of n910c,I tested on my n910u ,it works but no network
I think the kernel,because I try to run it along your kernel
it has network but other things not work
Please help make it work on n910u
http://teameos.org
Thank you

Halaszk kernel is only for Samsung touchwiz based roms so do not try it to use With cm12 or you might end up softbrick your N910U .

In my opinion wait for few time more till developers make more stable version for cm12 and then later it will be easy to port it to N910U coz there is not much difference between N910U and N910C (just the modem + Audio )

And kindly post on there thread over XDA for help.

 

[Gà super]

so nobody else can

halaszk kernel is only for samsung touchwiz based roms so do not try it to use with cm12 or you might end up softbrick your n910u .

In my opinion wait for few time more till developers make more stable version for cm12 and then later it will be easy to port it to n910u coz there is not much difference between n910u and n910c (just the modem + audio )

and kindly post on there thread over xda for help.

???

 

[djmax81]

???

Friend no need to be sad I see what i can do for N910U devise will pm you an test if you in.

 

[halaszk88]

The different of the N910C and U device is only modem. N910C have ST-Ericsson modem, N910U have Intel modem. Any other component is matching

Halaszk kernel is only for Samsung touchwiz based roms so do not try it to use With cm12 or you might end up softbrick your N910U .

In my opinion wait for few time more till developers make more stable version for cm12 and then later it will be easy to port it to N910U coz there is not much difference between N910U and N910C (just the modem + Audio )

And kindly post on there thread over XDA for help.

 

[djmax81]

The different of the N910C and U device is only modem. N910C have ST-Ericsson modem, N910U have Intel modem. Any other component is matching

In this case even ramdisk along with modem too and And minor changes in kernel Build config if im not wrong

 

[Gà super]

The different of the N910C and U device is only modem. N910C have ST-Ericsson modem, N910U have Intel modem. Any other component is matching

so how can I use the AOSP ROM or cm12.1 of n910c

Gửi từ SM-N910C của tôi bằng cách sử dụng Tapatalk

---------- Post added at 01:35 PM ---------- Previous post was at 01:33 PM ----------

Friend no need to be sad I see what i can do for N910U devise will pm you an test if you in.

I wait your good news

Gửi từ SM-N910C của tôi bằng cách sử dụng Tapatalk

 

[darkbahamut]

I was playing the with governor settings earlier and noticed that you can't change the target load setting. Whenever the big cluster turns on the target load setting will default back to 75 no matter what it was set to before. If you stay on only the little cluster than it will hold whatever setting you pick. Any work around for this?

 

[white7561]

Still updating? Reallyy waiting for update. And does it have like googy kernel proximity bug thing? Thx

 

[kadiremrah]

For which update?
Proximity sensor bug can only solved when BOG1 Source code is released. I have inqueried it and waiting. On BOE3 and under firmares there is no proximity problem.

Still updating? Reallyy waiting for update. And does it have like googy kernel proximity bug thing? Thx

 

[white7561]

For which update?
Proximity sensor bug can only solved when BOG1 Source code is released. I have inqueried it and waiting. On BOE3 and under firmares there is no proximity problem.

Ok thx. And are the charging current status is live? Like In real time? Cool. And can we change the fast charging current too? Thx. For the kernel btw

---------- Post added at 09:16 PM ---------- Previous post was at 09:13 PM ----------

For which update?
Proximity sensor bug can only solved when BOG1 Source code is released. I have inqueried it and waiting. On BOE3 and under firmares there is no proximity problem.

Btw. Can A53 really go above 1.5 without forcing the min freq to 1.5 on a53?

 

[kadiremrah]

Ok thx. And are the charging current status is live? Like In real time? Cool. And can we change the fast charging current too? Thx. For the kernel btw

Yes you can see charge current live.
HV/Mains Charge current settings set Fast Charge currents.

Btw. Can A53 really go above 1.5 without forcing the min freq to 1.5 on a53?

My SoC can go up to 1.6GHz stable on A53
And some users report 1.7GHz stable

 

[darkbahamut]

The only thing to watch is the perf/watt of the A53's at those speeds is often worse than the A57s, meaning it's actually better to not overclock and to move to the big cluster. 1.5GHz with a decent undervolt is pretty much the sweetspot on the A53's, any higher can you risk just wasting power without some careful voltage control. You probably need at least a -150mv undervolt minimum for 1.6Ghz to be worth any consideration unless your big cluster voltages are really poor.

 

[white7561]

The only thing to watch is the perf/watt of the A53's at those speeds is often worse than the A57s, meaning it's actually better to not overclock and to move to the big cluster. 1.5GHz with a decent undervolt is pretty much the sweetspot on the A53's, any higher can you risk just wasting power without some careful voltage control. You probably need at least a -150mv undervolt minimum for 1.6Ghz to be worth any consideration unless your big cluster voltages are really poor.

I used to oc fine. But without knowing how to watch the perf/watt and things. Can maybe u help me how to measure it? Thx. I really appreciate your help

---------- Post added at 09:24 AM ---------- Previous post was at 09:23 AM ----------

Yes you can see charge current live.
HV/Mains Charge current settings set Fast Charge currents.


My SoC can go up to 1.6GHz stable on A53
And some users report 1.7GHz stable

What your asv group? I gonna get n910h soon. So i hope getting high asv group

 

[white7561]

@kadiremrah i see ur power advantage on second post. Can i know what is ur asv group?

 

[Heroeagle]

hi all

just small question . is all A53 cores always online or depending on the load .. can one or more of them be offline ?

thanks

 

[white7561]

do we need to apply the s6 ram management fix on build.prop or the kernel already have better ram management ? @kadiremrah

 

[UpInTheAir]

do we need to apply the s6 ram management fix on build.prop or the kernel already have better ram management ? @kadiremrah

Check your default.prop . I recall halaszk88 has set the entries there in his kernel

---------- Post added at 06:01 AM ---------- Previous post was at 05:53 AM ----------

hi all

just small question . is all A53 cores always online or depending on the load .. can one or more of them be offline ?

thanks

In default hotplug, all big.LITTLE cores are on when screen is on. Use the Synapse core control to set 1>8 cores . Eg. If you set 4, all A57 cores will be offline, but I found my own Note Edge kernel to be quite laggy. If you set core control to 3, then all A57 + A53x1 cores are offline, and so on...

 

[darkbahamut]

I used to oc fine. But without knowing how to watch the perf/watt and things. Can maybe u help me how to measure it? Thx. I really appreciate your help

If you know your voltages it's possible to roughly calculate it from information helpfully provided by Andrei before. For most people the 1.5GHz is going the sweet spot on the A53's, more so since the A53's have no temp sensor (so presumably no throttling) you don't want to run them too hard.

hi all

just small question . is all A53 cores always online or depending on the load .. can one or more of them be offline ?

thanks

In default hotplug, all big.LITTLE cores are on when screen is on. Use the Synapse core control to set 1>8 cores . Eg. If you set 4, all A57 cores will be offline, but I found my own Note Edge kernel to be quite laggy. If you set core control to 3, then all A57 + A53x1 cores are offline, and so on...

All cores are 'on', but unused ones go into low power states so it isn't quite the same thing. Cores in WFI & ultimately retention use very little power so aren't a concern. This state is available to all cores in the system so the A53 cores will go in and out of retention while the screen is on similar to how systems will have hotplugged in the past, expect retention is a much faster state to enter and exit so cores can drop into low power far more often. The hard hotplugging the kernel provides is interesting as a toy to play with (for benching A53's for example), but for practical use the retention states are far more effective than actually doing hotplugging while the device is in use.