yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Exynos Android Development] kadiremrah:
fried something?

I have full wipe my sd and restore my stock rom mk2 with iks core powers 3 and test again and cpu hit 102 degree and halt my phone. At the moment my battery is 38% and i got 17% when i hard reboot.

Did i fried something. Cpu, cache, termistor.
[Galaxy Note 3 Exynos Android Development] iba21:
Ahahah how? Ahahah

Well maybe it's a rom tweak.. or you have the cortexA5000 :rolleyes:

To know if cortexA7 is really in use you should run a test with the cluster mig..

But.. as i see, cpu temp is too high for a cortexA7
[Galaxy Note 3 Exynos Android Development] kadiremrah:
same with cluster migration

I have made first test with new kernel v4 oc cluster migration.

All the wierd things start there.

I think i have cooked something.
[Galaxy Note 3 Exynos Android Development] stanley08:
If you can make me eggs with the heat from your phone, Dat would be LOVELY! :)
[Galaxy Note 3 Exynos Android Development] zeyadhan:
pekaka what have you done the new kernel has lot of problems
[Galaxy Note 3 Exynos Android Development] archer797:
I am using latest Normal kernel..
[Galaxy Note 3 Exynos Android Development] fixfox2:
I think this is the reason for the high temp of v4.

Why not leave all voltages for each freq. at default except 2.1G ?
[Galaxy Note 3 Exynos Android Development] pekaka:
4.0.1 change to default uv,running kernel on yourself ,so testing and feedback if you want,don't blame on me for high temp or something wrong for your phone,pls remember the kernel is free!

all is ok when I testing on v4.0,may the weather is cold,so I don't get hot,but default uv is suitable for almost of us.
[Galaxy Note 3 Exynos Android Development] kadiremrah:
pekaka

This is a game for fun and we have to know rules.

We can hurt. Play or not your choice.

so please don't blame game maker. Just go stock way or play after testers get fun and give ok.

Ofcourse dev must think every scenerio and be carefull.
[Galaxy Note 3 Exynos Android Development] pekaka:
try v4.0.1 if solve higt temp problem?
[Galaxy Note 3 Exynos Android Development] fixfox2:
[MENTION=458056]pekaka[/MENTION]

I was only suggesting that if you leave voltages at default, then each user can change (at their own risk) to suit their conditions.

Thank you for implementing this in version 4.0.1

Each person should know the risks and make an informed choice ....... on whether to use the kernel or not.

The developer is NOT responsible! ( as is usually stated in the first post. )

Thanks again!

update-----------------------------------

Personally, I will be under-volting ( all frequencies from .250 - 1.9G ) by at least 50mv so that the power savings gained in the lower frequencies, can be used by 2.1Ghz frequency.
[Galaxy Note 3 Exynos Android Development] iba21:
Well as i always sad.. thankyou for your free job.. i sad i'd want to buy you a beer, but..

Anyway when peoples uses OC, high temp is at the base of the OC logic due to fanless system

The core migration bug witch i have (and i'm not the only one) is a really really really bad thing, i'm meaning, no big.little, only big! :(

I'd want to know if you have the same bug.. the problem is not if you added the correct code, the problem is to fix it, and sure, i'd want to help you to fix it (if it's possible)

If you have that issue as like me, it's a code problem, if you don't have, is a chip issue..

Anyway i don't have an huge knowledge about linux compilation of the source, but i could help you to fix the code, i remember some c++ istructions

And we can look into andreilux kernel code for exy 5410, to see why it works ;)
[Galaxy Note 3 Exynos Android Development] pekaka:
overclock 2.1G,should raise mv,4-core up to 2.1G,is too huge,the best maybe 2.0G for most users,try to increase mv 25mv step by step,and you will find how much suit for your phone
[Galaxy Note 3 Exynos Android Development] kartalgurhan:
Thank You!

[MENTION=458056]pekaka[/MENTION]:

Many thanks for this work. Especially, putting the UV control abilities was brilliant!:good:
[Galaxy Note 3 Exynos Android Development] karthickkatta:
I is cluster was nice ..but I had many reboots when I set to 2.1ghz and after setting it less it was the same ..can you make iks core version ? ..henery kernel is rock stable ..but I like your kernel is better with many features ..try to fix it
[Galaxy Note 3 Exynos Android Development] iba21:
STUDY!!

Why system crashes?

Answer: cpu transistors needs a tension to permit the switching of it.. Why? Because those have a current resistence..

Frequency increasing increases the cpu current resistence, so, more voltage to be stable..

Do you have reboots? Well, it's time to low down the frequency

MY OPINION:

Why you would OC the phone?? More is the freq more and more is the power consuption: traduct: a dualcore at 500mhz absorbs less energy than a single core at 1ghz, at same arch.. why? I sad it, more freq MORE AND MORE energy consuption

In real 1.9 is the first OC freq.. look at the table freq.. look at the gap from 1.7 to 1.8 an from 1.8 to 1.9

The second one is more than the first one

so, 1.9ghz is already too high for this 5420.. and, as i can see, cortexA15 is almost powerfully capable at 1.4ghz to do all what you should do.. 2.1 is quite unusefull

Our note3 doesen't have the high battery capacity, why would you to decrease it by OC??

I really doesen't know to understand

The goal of HMP with exynos is to use cortexA7 for the most of the time + A15 less time to compile the minimum high task.. it's the opposit of overclock
[Galaxy Note 3 Exynos Android Development] karthickkatta:
Hmm good one ..but we will never get hmp
[Galaxy Note 3 Exynos Android Development] iba21:
I hope no :(
[Galaxy Note 3 Exynos Android Development] karthickkatta:
Can I use this kernel now ?..is it good ?..and **** you samsung ..5420 has a working hmp and not releasing to the current market ..
[Galaxy Note 3 Exynos Android Development] iba21:
This kernel is good.. but for me core migration doesen't work.. don't know if works with pekaka's phone

My advise is to install the cluster and put phone in batterysave (with only cpu ticked) that's due to a lower switch to cortexA15

Anyway i wrote a script witch locks the cortexA7 freq for more time.. but it has some lags, and it isn't for huge gaming.. if someone want it, i could create a zip package..

Btw samsung is the cause of it.. it's incredible.. it releases the 5420 chip ready for hmp with videos and infos, and now we are still in that situation..

I saw core migration was written in 2012, so, samsung had a lot of time to fix the code.. but not..

For me, the actual issue of core migration is in cpu and iks drivers.. probably samsung wrotes the basic code of core migration, but it doesen't modify the cpu and CCI drivers.. that's why you see the famous 650mhz in core migration, but it doesen't send the info to the chip to shut down that core and turn on the cortexA7

I don't know if it's a scheduler bug.. i don't think, scheduler sees 4 cores, it's iks issue..

As i sad, andreilux created a working core migration for s4 octa.. we could look into those code lines and try to find the possible bug..

I should do this.. but i really don't know how to compile a kernel, and i have a mac ! :D
[Galaxy Note 3 Exynos Android Development] karthickkatta:
Even if Samsung releases hmp we can cherry pic ..and for me cluster migration Is not working ..hmp would force all cortex a7 and rarely use 4 of the cortex together ..so the temperature would be less .
[Galaxy Note 3 Exynos Android Development] kadiremrah:
Video Review

Hi,

I have tested this kernel. It is said to be cluster migration.

But I see some wierd things maybe Program based maybe I have fried my Cpu last night but you have to see too.

at seconds 12~13 we see two core is 300mhz and other two is 1.9Ghz

at 1:43 to 1:46 - "1 core 800mhz 3 core 1.9Ghz" and "3 core 900mhz and 1 core 1.9Ghz"

may be I am thinking wrong way :eek:

Youtube Video Link

and too high power consuption. 1700mA wowwww
[Galaxy Note 3 Exynos Android Development] iba21:
Cluster migration is working.. maybe you mean core migration

Core mig is not working..

Hmp doesen't force ANYTHING..

It has a rewrite of linux scheduler witch chose the core witch ti send the task, it means, no task in core = core shutted down automatically..

The actual cluster mig and core mig (if it works) doesen't have this scheduling logic, so, chip doesen't shut down cores due to the base logic of the scheduler

Would you like to shut down cores? It works!

/sys/devices/system/cpu/cpu0/cpufreq/online and put 0 in it..

Sure it's the same for cpu 1 2 and 3..

If goes offline, scheduler doesen't send tasks to that core, and chip auto shut down transistors of that core by using power gating..

So.. hmp could turn on cores from 0 to 8.. yes, because if scheduler doesen't have tasks to be compiled, no cores are on, only cache ;)

As i sad, cortexA7 could compile the most of the tasks.. only a few needs more, as like pages panning, gaming.. stop..

I really hope samsung will release hmp with kitkat....

---------- Post added at 02:32 PM ---------- Previous post was at 02:26 PM ----------

It's normal.. :D

Linux governor is indipendent for each cores.. but, it preserve the same frequency since all core has the same voltage...

Sometimes 1 core has different freqs than the others..

Oh.. it happens with interactive.. ondemand doesen't have that "feature"

Could it save energy?.. NO

Cores in the cluster has the same voltage, so, it's absolutely unusefull..

As i repeat.. if you run the interactive governor it's absolutely NORMAL

It doesen't means core migration is workig.. that's what you would understand :D

Change to ondemand and look, you'll have always a fixed freq for every cores :D

EDIT: one free information.. async voltages as qualcomm's chip is unusefull too, why?

1) more transistors to have more PWM modules, more transistors = more energy dissipated..

2) linux prefere to have all cores at the same freq, so it could move tasks in the "free" core

3) async freqs = async cache.. the older scorpion arch had a direct sync with core0, i don't know if it's the same with this krait, but probably yes.. so.. async cache = bottle's neck

So.. would you like to have the good performance + less battery usage?

1) have a good freq to compile tasks with cpu time idle not so high

2) prefere a multicore system witch works at lower freqs (less freq lesser and lesser consuption)

3) turn off transistors not in use

The HMP with good governor..

:D
[Galaxy Note 3 Exynos Android Development] kadiremrah:
min_freq

hi iba21,

I see a file /sys/devices/system/cpu/cpufreq/iks-cpufreq/min_freq is set for 1800000

what is this file. And can I change it. Because when my cpu throttle 1.9Ghz and heat rise CPU get itself to 1.8Ghz so maybe I can take it to 1.4Ghz.

:confused:
[Galaxy Note 3 Exynos Android Development] iba21:
It's strange.. the official kernel has the same issue (???)

If you write a different value in it, minfreq will rize at that value..

You see 1800 but in real your minfreq is 250..

If you put the phone in battery save.. with the original kernel maxfreq will be 1.4ghz (real) minfreq will be 650mhz (but 250mhz in real)

I really don't know why minfreq value in that sysfs file doesen't change

you could test it.. write in it a value, as like 800000 and look in a daemon app (as like system tuner), the new minfreq will be 800mhz even if the minfreq sysfs write 1800000

If you rewrite it to 250000, minfreq will be 250mhz even if you see 1800000 in the sysfs file

Probably it's a bug of the original kernel.. samsung really doesen't want to write a correct code for the 5420.....

http://www.imgur.com/22dKRpD.png

Look.. it's absolutely normal
[Galaxy Note 3 Exynos Android Development] pekaka:
1800000 is ikcs cluster minfreq of ARM_INT_SKEW_FREQ_H,you can't change it,meaning,if your freq is 1900000>1800000,arm ini freq working at 400000,if <1800000,arm ini freq working at 222000 or 111000,but core kernel don't has this limit of ARM_INT_SKEW_FREQ_H
[Galaxy Note 3 Exynos Android Development] iba21:
It could be strange but i don't understand! Ahahaha

Well so it's not a bug, it's true

I only could say if i write 650000 in minfreq, the minfreq will be 650000 even if the sysfs lock the value to 1800000

Need a screenshot?
[Galaxy Note 3 Exynos Android Development] pekaka:
1800000 is a point,not a real cpu freq
[Galaxy Note 3 Exynos Android Development] iba21:
Thaanks.. anyway do you have the same issue as mine with core migration?
[Galaxy Note 3 Exynos Android Development] pekaka:
ahaha,I am busy these days,so haven't tested ,but I have different opinion from you,core kernel,A15 not always switch all freqs to A7,may the reason of performance or failse freq -switching,among the iks freq fold,you also can find a flie max_eagle_count,I think this is a key for switching,but how to work,I don't understand clearly.

another important thing is cluster kernel switch to A7 so quicking after phone reboot,but core kernel must sleep for sometime to wakeup and the sleep again,swithing take effect,but wake up,some freq switch,so A15 is always working

I don't think this is a bug,but a different way of control cpu works,so I think core kernel for performance users,cluster kernel for normal or powersaving users
[Galaxy Note 3 Exynos Android Development] iba21:
But It could be strange if core mig never switch to cortexA7.. or not?

In theory core migration has the same logic of cluster migration (from 250 to 650 A7 and the rest A15) only it changes the single core.. in theory..

Max eagle seems the number of cortexA15 could be used.. i changed that.. it's possible to write the 2-3-4.. not more than 4 or less than 2.. and it seems it force the max number of cortexA15 switching.. the problem is other 650mhz are still cortexA15! :(:(:(
[Galaxy Note 3 Exynos Android Development] kadiremrah:
I think this file make this... (video link)

/sys/devices/system/cpu/cpufreq/iks-cpufreq/min_freq

YouTube Link
[Galaxy Note 3 Exynos Android Development] pekaka:
another thing is that when I add uv control for core kernel,ondemand and ondemand-sec is not working,so I think may core kernel need a special governor to manager?
[Galaxy Note 3 Exynos Android Development] pekaka:
can't open the link?but I know this file, as I said before,it is a point,for arm int freq working,not a real cpu freq,can't change it

but for core kernel,this minfreq is 650M,real cpu freq
[Galaxy Note 3 Exynos Android Development] pekaka:
on core kernel 3.0.01,ondemand and ondemand-sec is working under control by cpuset,but under systemtuner is failue
[Galaxy Note 3 Exynos Android Development] iba21:
Nope.. probably governor tryes to load the UV table and doesen't find it

In governor's goce there is the line about the voltage table

as i sad if i wrote 300mhz in that file, minfreq will be of 300mhz even if the sysfs value is 1800000

Try ;)

I tryed to modify the value directly in sysfs file, and it crushed..

Probably there is something wrong.. but.. i could say that the main priority is to find a way to run the core migration in the correct way..

cpuld you send me the ***.c files of cpufreq and dipendencies? i'd want to compare those with the 5410 of andreilux kernel, too see the difference, and, maybe, find the BUG!!

as i can say, core migration works in 5410 in s4
[Galaxy Note 3 Exynos Android Development] iba21:
http://www.spinics.net/lists/cpufreq/msg08747.html

this is the tech comment of what i sad.. the iks is ONLY for cortexA15.. needs more code to run the cortexA7

probably it's a developer code out of samsung.. and samsung/arm/linaro doesen't want to release iks / hmp source code

so.. core migration is impossible without correct sources!!

EDIT: i extracted the n900 source code, and really there is the iks file..

it's really quite strange.. it has some dependences of exy 5410 (????) :eek:

a really base code..

[MENTION=458056]pekaka[/MENTION], what changes you did in iks file?
[Galaxy Note 3 Exynos Android Development] Crescendo Xenomorph:
[MENTION=458056]pekaka[/MENTION]: look at this source code in the links

---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------

The series of patches represent support of Exynos 5410 SoC

The Exynos 5410 is the first Samsung SoC based on bigLITTLE architecture.

Patches allow all 8 CPU cores (4 x A7 and 4 x A15) to run at the same time

Patches add new platform description, support of clock controller,

dual cluster support, device tree for Exynos 5410 and minor fixes (CCI, MCT)

Has been builded on v3.12-rc3.

Has been tested on Exynos 5410 reference board (smdk5410_defconfig).
[Galaxy Note 3 Exynos Android Development] iba21:
It's for 3.12.. we have the 3.4 ;)

go to linaro git tree.. you'll see the upgrading of MP tech over the linux 3 patch 10 (3.10) kernel

It means you couldn't add that patch without the 3.10 base kernel.. all changes.. scheduling first

Anyway MP (hmp) is under developing.. last modify of code by linaro was of 4 weeks ago.. so.. samsung probably doesen't have the perfect code.. probably the MP tested over the boards are not good, probably it has issues in voltages chosing..

Probably samsung has a "simple" code witch could works in the standard test hardware, i'm meaning the techcon tablet, probably it doesen't have the voltage scaling..

http://git.linaro.org/arm/big.LITTLE/mp.git

this is the real linaro git code.. ;)
[Galaxy Note 3 Exynos Android Development] iba21:
I'm using the 4.0.1 cluster version with conservative and huge uv.. well it's perfect.. fluid and cold..

Now the best should be core mig.. or better hmp.. :(

Damn samsung..
[Galaxy Note 3 Exynos Android Development] sco00262:
still so unstable on my phone...

reboot right away:crying:
[Galaxy Note 3 Exynos Android Development] karthickkatta:
I'm using iks core new version 1.9ghz ...This kernel is stable but when I keep the phone in sleep mode and turn it on after 5min the phone hungs did anyone have this problem ?
[Galaxy Note 3 Exynos Android Development] pekaka:
how do you keep phone in sleep mode,I mean just press power button to shut off the screen or sleep by other apk?
[Galaxy Note 3 Exynos Android Development] karthickkatta:
Power button ..its working in 2.1ghz ..but phone my went to 96 degree ..In 2.1ghz. .

---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------

And also im using henery kernel with 1900 mhz to 1200mv my cup goes upto 7 degrees but in your kernel when I use 1900mhz to 1200mv temperature goes above 86 degree why is that ?
[Galaxy Note 3 Exynos Android Development] pekaka:
I don't know why so high temp on your phone,have you wipe cache?so high temp,some apks must be running behind,I guess,if you use systemtuner apk,change the kernel,also need to clear the cache of systemtuner.apk,if you test by Antuu,alse need do that.

here are pics I have just test,from reboot phone to running Antuu.apk

1.9G default uv at 1200mv

View attachment 2468011

on screen no running any apk after reboot,temp from 61~31,due to booting,freq force runing 4cores at A15 1.2G&INT freq at 600M(this time minfreq of iks-freq must be 1.2G),so 61c high temp,but when stable,all switch to A7 650M MAX(so this time,minfreq of iks-freq must be 650M),so temp down lower 30c

View attachment 2468012

after testing by Antuu,temp from 91~28

View attachment 2468013
[Galaxy Note 3 Exynos Android Development] karthickkatta:
It's fine now ..what is the max temperature can our cpu withstand ? Can we adjust the gpu voltages ?
[Galaxy Note 3 Exynos Android Development] pekaka:
110，2.1G vl don't ext 14000mv,it is safe.I use 1325mv,all is ok by testing Antuu,3D rating,3D bentch mark
[Galaxy Note 3 Exynos Android Development] pekaka:
110，2.1G vl don't ext 1400mv,it is safe.I use 1375mv,all is ok by testing Antuu,3D rating,3D bentch mark
[Galaxy Note 3 Exynos Android Development] iba21:
Noooooooo

I'm on the 4.0.1v and now i'm having the same famouse no ca15 migration.. ahahhahah

Cluster mig doesen't mig in ca15 and core mig doesen't mig to ca7

You must mix those! Ahaahahah :(
[Galaxy Note 3 Exynos Android Development] karthickkatta:
I told you cluster had bug ..It doesn't call a15..I'm using cluster 4.0..it had a bug..when the phone was put to sleep ..when we on it ..phone hangs and cannot turn on..Henry kernel is stable .. [MENTION=229421]PEKA[/MENTION]k can you review his kernel?
[Galaxy Note 3 Exynos Android Development] iba21:
exactly the same issue.. after the screen shut down (android awake) no more ca15..

Never had this issue with henrry kernel.. so.. probably the code is bugghed

[MENTION=458056]pekaka[/MENTION], did you change the ikcs code or some dipendencies? It works until the screen off, i'm meaning, Cluster mig works until i shut down the screen

And.. umh.. i'm testing the 4.0 core.. and it still have the ca15 fixed.. no ca7 migration even if i force maxfreq to 600mhz

I only could say one thing.. F.U. samsung..

Iks is a code written 1year ago for 5410 chip.. they wrote it.. stop.. probably it has huge issues in it, but, without an high knowledge of the hardware it's impossible to fix those lines.. probably the problem of core mig are in cpu drivers witch doesen't have depemdencies of the single core "cluster"

Really F.U. samsung.

I hope they'll release hmp soon or i'll never ever buy a samsung phone.
[Galaxy Note 3 Exynos Android Development] karthickkatta:
Henry kernel didn't have any bug . [MENTION=458056]pekaka[/MENTION] can you compile the kernel from source again ? I think some thing went wrong in your kernel
[Galaxy Note 3 Exynos Android Development] kadiremrah:
perfect.

I am using 4.0.1 cluster migration.

2 day standby

3 hours screen

20 minute call

3O% remaining battery

34200 point on anTutu after5 min screen off and on test
[Galaxy Note 3 Exynos Android Development] iba21:
Do you have the ca15 issue?
[Galaxy Note 3 Exynos Android Development] kadiremrah:
how

Yes never go over 650mhz
[Galaxy Note 3 Exynos Android Development] iba21:
Oh ok.. so you have the same issue.. so only ca7

[MENTION=458056]pekaka[/MENTION] could you rewrite the ikcs file with the original?
[Galaxy Note 3 Exynos Android Development] pekaka:
I haven't changed any code of ikcs-cluster,all stock kernel,only one is add gpu 600M,I think may it is problem with some phone running condition,so next time will get rid of 600M,restore to stock gpu,lock at 480M
[Galaxy Note 3 Exynos Android Development] kadiremrah:
Cortex A15 problem

Here is the video test and video

Youtube Video Link of Review

if i made something wrong. I can try your way....

---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------

iba21 you were right.

And Cpu temp. problem comes from A7 voltage table but using A15 freq. so @ 650mhz A15 was getting 1212mV (from A7's voltage table) but need much lower.

so high temperature on low freq.'s problem occur.

I think A15 also has its own low freq's. So we can do Only A15 kernel. or Only A7 kernel.

One gives ultra high processing power.

And other gives lovely battery time. but all of them useless.
[Galaxy Note 3 Exynos Android Development] kadiremrah:
how

I think using Sytem Tuner or Cpu Tweaks locking up Cpu to cortexA7.

---------- Post added at 07:38 PM ---------- Previous post was at 07:28 PM ----------

on pekaka core.mig oc kernel

Lowered the under 650MHz voltages. But Cpu temp also rise. UV cotex.A7 does not work for A15 and A7 does not working at all.

I thing 650Mhz and under voltages for A15 is seperate.

If we have only A15 working on Core.Mig. I have tried the UV under 650Mhz freq but not do any effect.

Video Link
[Galaxy Note 3 Exynos Android Development] iba21:
[MENTION=458056]pekaka[/MENTION]

i have to send you 1 package with some files to be merged in the kernel.. but.. those are for test purpouse only, so, send me via PM an email and i'll send to you this package

i'll explain more in private..

i need you because i don't know how to compile the kernel! ahahah