yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] nkirk:
Hi,

Its not a problem with the kernel but wrong configuration, do not try to under-volt cpu,gpu, mem ect and try to achieve rbb at the same time.

For the sake of solid stability

* try setting -25 or -50 on the cpu side only on higher frequencies ( 800 and up) and leave like that, you are already headed for --ABB by 50mv compared to your stock configuration.

*Do not change anything under memory/internal settings.

*Do not change anything under ABB (for the moment)

If you find your device stable for sometime, you may do more UV and play with ABB values if you are comfortable and fully aware about the logic behind it.

ps: No .. equalizer has nothing to do with stability or boot loops.

//nkirk
[Galaxy S III Original Android Development] p33t-r:
As you guys probably read my post earlier, I get the reboots on system startup (bootanimation) and this happens also with NO UV or ABB changes.

I know that if you mess with voltages you can experience random reboots. I do know the physics behind ABB, transistors etc, I am physics graduate...

What is the main problem is the stability during booting. I am sure it's kernel-related issue and might take a shot it could be something with gpu, because today, again after few failed boots the SAMSUNG logo got some strange artefacts. Now I have gpu uv with abb tweaks (lowered actually). But the reboots happen ALSO WITHOUT ANY VOLTAGE CHANGES. I will stress that once again.

Any ideas how to get a logcat from the time when kernel and system boot?
[Galaxy S III Original Android Development] chiupc94:
I have the same problems as well so I guess it has something to do with ABB,
[Galaxy S III Original Android Development] nkirk:
Hi,

My post was not directly aimed at your issue, but my bad.. i could've read more carefully :D.

Have you tried the stock kernel?, have you tried completely deleting the stweaks folder and re-flashing the kernel?

my apologies if you have mentioned this before.

//nkirk
[Galaxy S III Original Android Development] andrewfung888:
Cannot use adb, it is for android app debug. Found two apps from chainfire in playstore

Live logcat

Live dmesg

Which display logcat and dmesg during bootup.

Free version display too small, may need to use the paid version.
[Galaxy S III Original Android Development] p33t-r:
Stock kernel works fine. I've been using Temasek's rom and kernel for a while (kernel is basically Perseus ported to AOSP) and I had no issues there, even with UV and high RBB. The reboots reappear after clean kernel flash with no tweaks, after couple of days... And one user (jinosong) reported he has the same issues with stock tweaks, but using my profile they disappear.

Thanks for that, I've found those apps earlier. They seem worth a look.
[Galaxy S III Original Android Development] Steve_max:
You don't want a logcat. You want a kernel log.

You can get that after the device boots. Whenever the boot process starts, the kernel takes the log of the previous boot and puts it on /proc/last_kmsg. This file is what you want: get it right after one of your boot-time reboots, and send it here. This way people can try to help you.
[Galaxy S III Original Android Development] tolis626:
[MENTION=4167023]AndreiLux[/MENTION]

Hey Andrei,I've been snooping around the S4 forums and stumbled upon something rather interesting in the I9505 section.There is a kernel (Don't remember which one) that allows for overclocking of the CPU's L2 cache.Now the developer said,and I tend to believe,that this does increase CPU performance enough to make a difference.Maybe such a thing is possible on the S3?Since RAM overclocking isn't entirely possible...

Thanks in advance! :)
[Galaxy S III Original Android Development] NetCopAD:
Module building problems

HI. I was hoping I'll figure it out myself, but it's been a few years since I last compiled a kernel so I need some help.

I'm trying to compile some modules for Perseus - specifically mac80211.ko and few others for a usb wifi dongle.

I'm compiling successfully using .config from my S3 as a start. The problem is I can't insmod mac80211.ko. I'm getting "unknown symbol in module, or unknown parameter" error.

dmesg -c outputs:

mac80211: c0 Unknown symbol ewma_init (err 0)

mac80211: c0 Unknown symbol ewma_add (err 0)

I'm using linaro 4.7.3 obtained from git://github.com/garwedgess/toolchains.git

I'm pretty certain I'm missing some make option (a path or something), but I can't figure it out.

Thanks in advance!
[Galaxy S III Original Android Development] yahyoh:
i think there is way to OC RAM + CPU in the same time with ocing bus

Ocing bus ( Live OC ) used in Exynos 3 devices ( Nexus S - Galaxy S1 ) and its really great but its less stable and more dangerous than normal OC u can easily fry the device component with wrong voltage :D

more infro : http://xdaforums.com/showthread.php?t=1288015

but IDK if its possible on GS3
[Galaxy S III Original Android Development] tolis626:
If we could have something like that implemented,I'd be a happier person.But I think that Exynos 3 and Exynos 4 devices are very different in how bus speeds are defined.In the S2 and S3 for one,it's a base clock (800MHz if I'm not mistaken) that's divided by an integer.Unless someone finds a way around this,I highly doubt we'll have anything close to LiveOC.I've been proven wrong enough times however,first and foremost by Gokhanmoral and AndreiLux.That's why I'm asking.I would be bothering otherwise.
[Galaxy S III Original Android Development] Frag1le:
I never touched any voltage settings. I also never experienced this issue on < 36.

So far so good on 34.3
[Galaxy S III Original Android Development] p33t-r:
I also can't remember anything like this before v36. yesterday I went back to stock settings, the bootloop dissappeared. But after changing 4 values in CPU Hotplug tab - it's back again. Only one or two, instead of 10, but still...
[Galaxy S III Original Android Development] woof123:
Im waiting for the 4.2.2 version of the kernel,your kernel is so good and with so many features that i cannot use anyone elses now.So im stuck at 4.1.2 version of android until a new one is released :good:
[Galaxy S III Original Android Development] PsychicJian:
Me too! I use Stock Rom only 4 Perseus!
[Galaxy S III Original Android Development] TheMrcool212:
Samsung didn't released yet the sources for 4.2.2 leak. So the developers can't make a custom kernel for it. You should wait for the official update.

AndreiLux had said that there are no updates for this kernel until the sources for 4.2.2 had released. You should go back few pages. But I can't remember where he post that.

Many people are asking this same question everyday. I think they didn't know how the developers make a custom kernel, that is why.

Sent from my Galaxy S3 on 4.2.2 leak
[Galaxy S III Original Android Development] funeralcrows:
AndreiLux, please oh please give us Lulzactiveq. This kernel is too awesome I can't switch to another >_>
[Galaxy S III Original Android Development] HyperCriSiS:
Will you add support for 4.2.2? :)
[Galaxy S III Original Android Development] TheMrcool212:
Two posts above you.

Sent from my Galaxy S3 on 4.2.2 leak
[Galaxy S III Original Android Development] AndreiLux:
Snapdragons have an asynchronous L2 cache block besides the CPUs, running at max 1150 mhz stock. It doesn't apply to our ARM cores since everything is on the same frequency plane here.
[Galaxy S III Original Android Development] woof123:
I know that already my friend :) The time is near tho since it wont be long until the official release now.
[Galaxy S III Original Android Development] TonyTrollsten:
Any new update??????
[Galaxy S III Original Android Development] Thin_Bezel:
Um, 7 posts above you? AndreiLux will not update this kernel till Android 4.2.2 source code is out
[Galaxy S III Original Android Development] jeebspawnshop:
Next person that blindly asks for a "new update" should get banned. For ever.

And then when he finally expires from old age, upon his tombstone it shall read;

"During his life he missed XDA the most... Because he didn't even read the previous post."

Yup, that's EXACTLY what's gonna happen.
[Galaxy S III Original Android Development] Philips9:
Hello guys, anyone tried this kernel with the latest MD3(4.1.2 sammy)? It work well in term of performance/ battery life / ram management ?

Thx in advance
[Galaxy S III Original Android Development] bajong:
nice
[Galaxy S III Original Android Development] NetCopAD:
Follow-up

So I used the original PerseusCWM.zip and injected my kernel into the boot.img and now the modules load fine, which was to be expected.

However the question remains - how do I compile them so that they are usable in the original Perseus kernel?
[Galaxy S III Original Android Development] The Broken:
In this: http://xdaforums.com/showthread.php?t=2113150

Thread the 'owner' of the thread created something to push certain modules into a kernel, I think he called it punchmod or something.

Now I must say that I don't have a clue what you're talking about but I figured that this could help you ;)

See here for his past about it:

http://xdaforums.com/showthread.php?p=41920265
[Galaxy S III Original Android Development] PsychicJian:
In my case this is the perfect combination: excelent battery life & awesome performance! You should try it!
[Galaxy S III Original Android Development] mattiadj:
With which settings? Can u share these?

From universe with my gs3
[Galaxy S III Original Android Development] NetCopAD:
Thanks! Very interesting find indeed! I'm aware of this possibility (although I didn't know tools existed), but it's not what I'm after. I'm trying to do this without any hacks. Anyway I think the specific modules I'm trying to insmod require something else compiled into the kernel and that is why I can't load them on the original Perseus. I haven't tracked it down though, this is only speculation.

Regards!
[Galaxy S III Original Android Development] omniwolf:
Hi, did you ever work this out? I am having the same issue. I haven't found the right combo, but depending on how I toggle the frequencies and voltages I can sometimes get it to take (how do I know? the phone will crash due to too much UV. But as i increase the voltage, I can't tell if it's stable or I just haven't gotten the setting to take properly :( ).

It doesn't seem to matter whether I use STweaks or use the SysFS interface via ADB, but I have been using /sys/devices/system/gpu/... as it's quicker than STweaks, and I noticed something which can prove (i think) there must be something wrong:

root@android:/sys/devices/system/gpu # cat min_freq
cat min_freq
266
root@android:/sys/devices/system/gpu # cat max_freq
cat max_freq
440
root@android:/sys/devices/system/gpu # cat time_in_state
cat time_in_state
0 54
0 108
1864545314 160
0 266
0 350
0 440
0 533
0 640
0 733
0 800
root@android:/sys/devices/system/gpu #

I've set the min freq to be 266 and the max freq to be 440, but the phone is only spending time in 160.

[edit] ok if i set the min frequency to be 266, then the time in state for 160 will increase (as if the phone is actually using 160, not 266). if i increase the min frequency to 350, then the time in state for 350 will correctly increase. So either the frequency setting is wrong, or the time_in_state thing is bugged. Either way I can confirm the above quoted oddity - I was able to set the min and max frequency to 440, and reduce the voltage for 440 to 600mV, and used the phone without issue, which just can't be right. I confirmed in STweaks and SysFS that 440 was min, max, and at 600mV [/edit]
[Galaxy S III Original Android Development] PsychicJian:
Sure: override.profile

Thanks to jinosong!

P.S. if you would to see what kind of settings there are, you can see this post
[Galaxy S III Original Android Development] jinosong:
I recently switched back to version 35 just for experimentation purposes and it seems like I am getting much better battery life.

Can anyone else out there confirm this for me? It's weird because I've been having battery issues and thought it was my custom rom which is WanamLite. Now I'm pretty sure it was v36.3 that was causing it.
[Galaxy S III Original Android Development] thechaoz:
I agree with this and posted for the previous version, Google has failed me as well...do you have this?

Jelly beans 13 with Perseus kernel banging note 2 i-605
[Galaxy S III Original Android Development] jinosong:
Here you go.

https://dl.dropboxusercontent.com/u/3234631/Perseus-alpha35-i9300-CWM.zip
[Galaxy S III Original Android Development] p33t-r:
So far I can confirm that bootloops during bootanimation for me are gone after switching back to v35. On v36.3 I kept getting bootloops even on completely stock Stweaks values.

Will monitor battery life and after applying some UV I will check the bootloop issue.
[Galaxy S III Original Android Development] Frag1le:
I lost my previously downloaded v35 so that's why i went back to 34.3, i'm also experiencing much better battery life.

With 36.3 i was getting way more wlan_rx_wake wakelocks then i'm getting now on 34.3.

Don't know if it has anything to do with it but i'm always on the same Wifi networks and my wlan_rx_wake has dropped from like ~4 hours activity to ~40 mins of activity on a 24 hour use in BetterBatteryStats.

Thanks for the v35 i'll be flashing that.
[Galaxy S III Original Android Development] PsychicJian:
I'm gonna try it!

Inviato con un SIII da Giove.
[Galaxy S III Original Android Development] andrewfung888:
I have also switched back to v35 for two days already. undervolt back to -125 and without bootloop when booting.

I also using uprate 1 and downrate 4 after seeing p33t-r profile. I used my phone a lot today and now is 32%, screen on time is 4hr 21min. I am satisfied. Battery life is better in v35 than v36.3 when using, not much diiferent when idle.
[Galaxy S III Original Android Development] chiupc94:
Deleted
[Galaxy S III Original Android Development] p33t-r:
Nice to hear you've used one of my tweaks. Personally, I find these 2 settings crucial to proper hotplugging. Default Pegasusq up and downrates are way too high.

I actually notice much better battery life, especially during idle. Using my profile I got 4 times in a row >6 hrs screen time (about 20-24 hr cycle). I am very pleased with the battery now. No swings, like I used to get on AOSP. Stable as well. I'm currently on Wanam v6.6 (MD2) + Perseus v35 + Jkay.
[Galaxy S III Original Android Development] Sc0rp10:
so you think that the instability and bad battery life could be due to ABB? because andrei introduced in v36
[Galaxy S III Original Android Development] p33t-r:
I'm pretty sure the bootloops could've been caused by ABB. No major changes from 35 to 36, apart from ABB.

About battery life - this is a whole new story. Can't and won't confirm that. It's hard to tell now. Seems much better on idle, which might somehow be related to 200000] ABB slice... No big difference noticed yet while in use. But the deep sleep is great. I have to check WiFi drain, while I'm at home. Never found a kernel which would allow me to keep WiFi on all the time. Huge idle drain - over 2%/r (comparing to 0,6% which is what I am getting with WiFi off).
[Galaxy S III Original Android Development] Sc0rp10:
but surprisingly the same ABB implementation on temasek's kernel is giving people 0.3-0.5%/hr even with wifi on. may be its something with stock roms thats keeping the phone awake.
[Galaxy S III Original Android Development] andrewfung888:
Abb in 36.3 leads to lighter uv or bootloops. But for idle current i get 0.3-0.4%/hr since v33 to v36. so i think idle current is more apps related, and screen on current is governor, uv related.
[Galaxy S III Original Android Development] Sc0rp10:
can you share your profile? and which rom are you using?
[Galaxy S III Original Android Development] andrewfung888:
Sure, i am in omega 43.3, Perseus 35,

3 curcial tweaks

1. frequency step 7 instead of 37, less aggressive , 100mhz increment only.

2. uprate 1, downrate 4 (thanks p33t-r), quicker hotplug response.

3. hotplug loadbias 3 or 4, turn on more cores if frequency is high, I think lower frequency more cores is better than high frequency less cores and frequency is more important than loading to bring up cores.

http://db.tt/lycJ5keo
[Galaxy S III Original Android Development] AndreiLux:
Wether ABB is working as intended or not is up in the air. The source code is out there and has been for over more than a month, anybody can check it for mistakes in the logic.

People claiming difference in Wifi drain or wakelocks while there has been no change to Wifi should maybe review their usages, such reports are a waste of time for me.
[Galaxy S III Original Android Development] p33t-r:
Sorry Andrei, I tried to get any log from booting, but it seems those reboots don't happen in the same time during the animation. I've checked live logcat from Chainfire and couldn't see any pattern in reboots. Also kernel lastmsg (?) didn't help me at all to post it here to resolve the problems.

I know that abb is always present, but it seems implementing the scripts to modify it somehow could cause the problems. If there are no other changes between v35 and 36 except abb, that might be the issue. I am no Dev, just trying to figure out what is going wrong with my phone. I love this kernel and I will stick to it.

Regarding wifi - I've always had lots of wlan_rx wakelocks, it might be because of my crappy router. Anyway, I noticed some improvement in deep sleep drain in general after switching back to v35...
[Galaxy S III Original Android Development] omniwolf:
Hi Andrei,

Do you have any comment (regarding GPU freq/volt) on this?

Further, it seems that the max_frequency works fine, but min_frequency has issues - if i set min_freqency to 266, I can see the 266 level in the time_in_state file increasing, but 30 seconds to a minute later the 160 level in the time_in_state file will start increasing, and min_freq still says 266.
[Galaxy S III Original Android Development] ribado09:
Hi Im new to flashing kernels so I just wanted to ask this, is it good for gaming? I mean is it better than stock samsung kernel when gaming? or is it intented for battery life? and another thing does it overclock the cpu to 1.6 Ghz? isn't that dangerous?

Thanks
[Galaxy S III Original Android Development] Sc0rp10:
The kernel is optimised for daily use including gaming and battery life and you can optimise it even more based on your usage using stweaks. OC to 1.6 is perfectly safe for most people but there are no guarantees
[Galaxy S III Original Android Development] ribado09:
Ok thanks for the response I'll flash it through recovery and see how it goes by the way do I have to wipe cache? or just install it and reboot?
[Galaxy S III Original Android Development] Sc0rp10:
Edit: No Need to clear anything. Just reboot in recovery and flash the file. Or flash the tar file through mobile odin. Make a nandroid just in case
[Galaxy S III Original Android Development] ribado09:
Ok Thanks!
[Galaxy S III Original Android Development] thechaoz:
I found version 35 googling for my i605..ive tried saber,stock and pj..this thing with uv chaotic weaponry settings gets purely disgusting (amazing lol) battery life...it's like night and day thought my battery took a poo...keep up the great work and no rush for wanting because I got it

Jelly beans 13 with Perseus kernel banging note 2 i-605
[Galaxy S III Original Android Development] Erahgon:
Yup! Same issue... never got around to solving it, neither did I get a response from anyone about it. I thought it was a bug with my setup. I have since moved to Cyanogenmod with Temasek's kernel (which, although similar to Perseus, unfortunately has no gpu control).

If you want, you could try to delete the .Perseus folder and flash the kernel again to see whether the problem persists. Note that this will return the kernel to its default settings in STweaks.

Although, since you mentioned that it occurs with the sysfs as well, the problem might be in the kernel code itself.

Sent from my GT-I9300
[Galaxy S III Original Android Development] MuertoKo:
Wtf? Just tried that and my time in state is as well ALL time in 160 MHz... something is really wrong in here, might be checking this file or might be the kernel.

[MENTION=4167023]AndreiLux[/MENTION] are we cheking this properly?
[Galaxy S III Original Android Development] omniwolf:
Yep, well it'll have to be the kernel - the kernel updates this file.

From what I can see it's one of two problems:

1. time_in_state is correct, and therefore the min_freq setting is broken. From my limited testing max_freq appears to be honoured, but min_freq is not. This allows us to think we're testing a super low voltage at a higher clock speed, but the GPU is actually running at a lower frequency, so the low voltage isn't actually being tested.

2. time_in_state is bugged. So it shows us that 160 is being used, but in actual fact the correct min_freq freqency is being used. If this is the case, then the volt_table must be bugged, as both Erahgon and i were able to tell volt_table to run the 440MHz frequency step at 600mV with no issues, which is ridiculous.
[Galaxy S III Original Android Development] MuertoKo:
There's an app called "Ajustes de CPU", I guess it's CPU adjustments in general, there you have a GPU freq. monitor and there I did manage to see my GPU go up to 266 properly! Even if it didn't raise anymore but I couldn't try to stress ir enough for it I guess...

Worth the try!

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] veteran_troller:
Is this kernel dead? I haven't seen it update in a long time?
[Galaxy S III Original Android Development] gordonx10i:
He has been Working on gs 4 kernel
[Galaxy S III Original Android Development] Philips9:
Hello guys,

I would try mattiadj's app called "bestMultitaskingFix" but I need:

Kernel with swap support

If you have Supercharger disable it!!

If you have Zram enabled, disable it!!

If you have HardSwap enabled disable it!!

This kernel has swap support and supecharger, zram, hardswap disabled?

Thx in advance
[Galaxy S III Original Android Development] reS28raM:
Yep, same here. In english it's called CPU Adjuster. My GPU goes to 266 too, I suspect the sys interface to be unreliable, but at this point some browsering into the source is unavoidable I guess. I don't have Linaro installed. :what:
[Galaxy S III Original Android Development] NetCopAD:
OK, I kinda fixed my troubles with the modules I was trying to compile, but I ran into another problem.

No matter how I compile the kernel, my camera always fails to start :( I've tried all the toolchains I could get my hands on and the result is always the same - camera failed to start. The kernel source is unmodified straight from git and the config is from 36.3 and I'm out of ideas.

Help is appreciated! 10x!
[Galaxy S III Original Android Development] p33t-r:
I don't know how much of help this could be, but I've recently came up with the same camera issue after flashing Wanam (full clean flash). Even Factory Mode got FCs, so I couldn't upgrade camera firmware. Being seriously worried I reflashed Rom and everything came back to normal. Since then - no problems with the camera.
[Galaxy S III Original Android Development] omniwolf:
Hi everyguys,

I did some battery testing on my ASV3 i9305 to see how much full UV'ing the CPU, GPU, internal, and memory (and applying ABB stuff) helps.

If you're interested in the results check it out HERE.
[Galaxy S III Original Android Development] NetCopAD:
10x, but that's not the case. It works fine with the original Perseus. It only fails with my build.
[Galaxy S III Original Android Development] AndreiLux:
Fixed the outstanding issues in 23.2.

The screen flickering is still visible on large bright areas of the screen, and especially low brightness. I changed the default settings on lcdfreq for it to be off so this thread doesn't get overwhelmed by whinning, and also more relaxed scaling. I'll see what I can do about the flickering or if there's anything at all to be done.