yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Ra1n3R:
Sorry Yank555, my bad. DL working and kernel update too. Thank you for sharing again :)
[Galaxy S III Original Android Development] Yank555:
No problem, glad it works ;)

You were totally right, OP updated ;)

JP.
[Galaxy S III Original Android Development] rezapatel:
After using many others and getting great benchmark scores and still looking for the one, decided to try this.

It is just super fantastic, the difference in how snappy the phone has become is way beyond being noticeable. It scored low on the benchmark but that doesn't matter even one bit.

Had to share my joy with the developer and say a humble thanks!

Cheers!

Sent from my Galaxy S3

---------- Post added at 04:44 AM ---------- Previous post was at 04:42 AM ----------

Just a quick question though, it scored low on the benchmark because of the low score on the cpu, wonder why that would be? Never OCed with others, nor this kernel.

I repeat, it doesn't matter so please don't get offended, just intrigued.

Thanks!

Sent from my Galaxy S3
[Galaxy S III Original Android Development] sotmax:
Benchmarks are really have nothing to do with real life my friend.

I saw a device having 2000 more than me in antutu and lag like crazy.

You can just reboot and leave it for aa while and then check again but really is not that matters.

Yank made a perfect job on this with realtime performance and great battery life ;)
[Galaxy S III Original Android Development] nfsmw_gr:
Hmm...when you mean low,how low?

Care to give us a number?Also what rom are you on?

I get great benchmark results with this kernel so i'm thinking that maybe the rom you're using is the issue...:)
[Galaxy S III Original Android Development] rezapatel:
I totally agree, I have no issues with a lower benchmark and specially when the real life difference is much more substantial and noticeable on this kernel.

Like I said, just intrigued because it was only the cpu that was the denting difference.

Sent from my Galaxy S3

---------- Post added at 07:06 AM ---------- Previous post was at 07:03 AM ----------

I will do the exact scores later again.

On Omega 33.3 with Siyah, the score was a little over the HTC One X.

On Omega 33.2 with stock, the score was almost the same or a little less than One X.

On Omega 33.3 with this kernel, the score was substantially lower than One X. The only variable that changed the result was the CPU.

All above on Quadrant.

Thanks!

Sent from my Galaxy S3

---------- Post added at 07:06 AM ---------- Previous post was at 07:06 AM ----------

And pls, don't consider the lower score as criticism. I am loving the kernel.

Sent from my Galaxy S3
[Galaxy S III Original Android Development] nfsmw_gr:
I see...

Well,i never liked omega at all,it just didn't feel very good for me like others i've tried(that's only my opinion).

Consider trying Ultima or wannamlite roms.

Those are the best ones for me.

Some say that Android Revolution HD is also very good.

For example in ultima with cpu at 1.6ghz i get around 6500 points in quadrant.

Anyway give it a go for yourself and see which rom fits you the most. :)
[Galaxy S III Original Android Development] Pretzel Kleo:
The sound is AWESOME! Thank you for this awesome kernel :fingers-crossed:

Working on Android Revolution HD v16 :victory:
[Galaxy S III Original Android Development] MuertoKo:
Just try using Antutu :) quadrant it's quite outdated and isn't reliable (you can get more than 1000 of difference doing same test!)

Antutu 3 is working quite nice and stable indeed ;)

And as said, just for curious!

Btw Yank, sio might be a bit better on battery (though hard to assure) but I had some nearly umpercived lags that I hadn't on cfq when using hard i/o ;) what about you on the testing?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] 37_:
anyone noticed the benefits of sio?
[Galaxy S III Original Android Development] Kaboosey:
@Yank,

Tried sio since it is out up till now. Got some reports though:

- When I woke up just now, the phone stucks on black screen only and I have to reboot it.

- One of my app suddenly force closed when I scroll through it. After reboot, it solves the problem.

Weird thing is, my set up is the same as before. CFQ doesn't give any problem though. But still, now i'm still running sio. Battery life is improved I guess. (maybe placebo? Lol)

Will continue testing it.

All in all, good job. Still happy with this kernel. :)
[Galaxy S III Original Android Development] sotmax:
Sio seems to perfoming well in my builds with slightly better battery life.

Have no strange problem in my builds but i m feeling more responsive with cfq.

Small tip.

If you change your governor via clocking app make a reboot to have better effect.

) ) ) over the air on Galaxy SIII ( ( (
[Galaxy S III Original Android Development] Yank555:
So far to be honest, I can't conclude to anything, I can't feel or see any noticable difference.

On the other hand, a scheduler won't make a huge difference and I'm my benchmarking tool, so with a very subtle difference, I may not really persive it...

Will keep using it for now, if I feel anything 'bad' I'll revert to cfq.

JP.

Sent from my custom Paranoid Android 2.54 / Yank555.lu CM10 kernel v1.2a Aroma (Linux 3.0.53) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] unholygid:
I'm not sure... it maybe just me.

I usually benchmark performance on asphalt 7 on "Shanghai map". Because that map is !@#@$ in terms of fps

Stock 1.4 pegasusq + cfq = Major lag. Cant even drift properly.

OC 1.6 pegasusq + cfq = Still lagging and phone gets to 60 degrees heat

Stock 1.4 Lulzactiveq + cfq = Major lag

OC 1.6 Lulzactiveq + cfq = lag + phone heats up to 60 degrees heat

Stock 1.4 pegasusq + sio = Lag is still there but its playable! Finally got first in that stupid map lol :D

Then out of curiosity I undervolt to -100mv with same settings.

Hp hanged while running stability test for 30mins. (Battery temp 42 degrees)

Then i UV to -75mv with same settings

Hp was fine after 45mins of stability test. (Temp never got above 42 degrees)

Ran asphalt 7 in shanghai map. Surprisingly, no noticeable change in performance.

So I guess I've found my perfect combo. Stock 1.4 cpu + pegasusq+ sio + UV -75mv = perfectly stable phone with much less heat and no dip in gaming performance.
[Galaxy S III Original Android Development] enigma1981:
@Yank, since flashing your kernel I'm having a strange issue with Widget Locker - the lockscreen wallpaper is showing as transparent and I can see my homescreen widgets and icons through the lockscreen...

It doesn't seem to me that it SHOULD have anything to do with the kernel, but it's only started since I flashed v2.7a so I thought I'd mention it here and you could take a look at it for me :)

Thanks in advance.
[Galaxy S III Original Android Development] sotmax:
Did you wipe dalvik n cache before flashing?

Also to avoid any problems reflash jernel also not only configuration.

And after first boot reboot once for the scripts to took place ;)

) ) ) over the air on Galaxy SIII ( ( (
[Galaxy S III Original Android Development] Yank555:
Lulzactiveq ... UV ... neither exists in my kernel ??

Sure you're in the right thread ? ;)

JP.
[Galaxy S III Original Android Development] Yank555:
Agree, don't see the direct correlation between kernel and that issue :confused:

Flashing 2.7 back (or whatever version you had previously) resloves the issue ??

JP.
[Galaxy S III Original Android Development] nfsmw_gr:
Excuse me but this kernel doesn't support undervolt or lulzactiveq so you must be using another kernel?
[Galaxy S III Original Android Development] unholygid:
Lol oops. Sorry. Cos i constantly flip both siyah and yank's kernel thread. Think I clicked on the wrong thread :laugh::laugh:
[Galaxy S III Original Android Development] Yank555:
Thought so :cool:

No problem ;)
[Galaxy S III Original Android Development] unholygid:
My gf is still on your V2.5 and she loves it. I was wondering if you would consider having UV support in your future builds?

I understand undervolting has minimal or no impact on battery life but it helps to keep the phone cool.
[Galaxy S III Original Android Development] Yank555:
So far still not, as it has a downside, that's instability and that's something I'd really not want to see reports of popping up in the thread :(

It's kind of on my roadmap eventually, but not really a priority...

JP.

Sent from my custom Paranoid Android 2.54 / Yank555.lu CM10 kernel v1.2a Aroma (Linux 3.0.53) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] enigma1981:
Yeah, flashing back to siyah 1.8 fixes it

Swyped from my Galaxy S3
[Galaxy S III Original Android Development] unholygid:
Maybe you can consider using 2 steps like -25mv & -50mv which i think is quite mild. But yeah I can understand how annoying it can be to see those kind of reports popping up in the thread. Because sometimes I play games on my phone for an hour straight or more, the phone gets really hot. Anyway cheers mate and thx for the awesome kernel.
[Galaxy S III Original Android Development] Yank555:
Hmm ... well then it must be linked, but then again, stock kernel should produce the same issues then, as this one's pretty close to stock.

JP.

Sent from my custom Paranoid Android 2.54 / Yank555.lu CM10 kernel v1.2a Aroma (Linux 3.0.53) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] MuertoKo:
Could be nice if you could try with some kernel like Siyah to do some realtime testing with PerfMon from Chainfire could help to test about heating with UV :)

We'd appreciate it much :)

Just saying so because you seem to be quite serious with testing stuff :P

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Highlander11:
I've been a firm supporter of the Perseus kernel - in fact, I was one of the first to recommend inclusion thereof in AROMA with ARHD.

However, for some reason, my phone kept getting slower and slower after a few days (anything from a day onwards), until I rebooted. Then it would be speedy and "back to normal" again.

So I decided to try out Yank's kernel. I've been on that for a week now without any need to reboot my phone - and no slowdown or lags. It seems that Yank's KISS principle is working! :D

I will always be a fan of Andrei's work with the Perseus kernel, but will stay on Yank's for now ;)
[Galaxy S III Original Android Development] jayden2009:
Btw also working with [MIUI] [RAYGLOBE V. 7]
[Galaxy S III Original Android Development] sotmax:
You wont be disappointed ;) ;)

**sorry Yank...jealus of the tux icon so i grab one also ;)

) ) ) over the air on Galaxy SIII ( ( (
[Galaxy S III Original Android Development] Yank555:
Thanx, OP updated ;)
[Galaxy S III Original Android Development] yo_7:
It is posible to have some little GPU OC for the benchmarks? :laugh:
[Galaxy S III Original Android Development] Yank555:
I'm really not into benching :cool:

And adding a potential battery drainer / instability source just for benching ... nah, not on my roadmap, sorry ;)

JP.
[Galaxy S III Original Android Development] corrsea:
Battery life is excellent once again.:)

ROM Sotmax Ultimate V8

Kernel Yank555.lu-V2.7a
[Galaxy S III Original Android Development] BelJanss:
How can i undervolt cpu? Via script?
[Galaxy S III Original Android Development] corrsea:
Misread the question
[Galaxy S III Original Android Development] AW079:
Issues Charging

Hi, from stock kernal [using Sotmax v8 ROM] I flashed v2.7 and am finding that:

a) the battery discharges alarmingly fast.

b) takes 1 hour to charge 10%, and

c) still discharges whilst connected to mains charger. :confused:

I was pretty concerned and so done a search on here and have found that others have encountered the same problem with earlier versions of kernal.

I have since deleted dalvik and cache, reflashed v2.7 leaving everything stock, clock speed, charge current and all other settings, and its still the same 1 hr for 10% charge, 2% drop in 5mins usage.

Battery stats shows everything is normal so I know its not that something is keeping the phone awake.

Can someone please offer any suggestions?
[Galaxy S III Original Android Development] corrsea:
If you have a different charger or USB cable try them.

Check the connections on both the phone and cable for dust or debris, blow into both or try cleaning gently with something dry that won't damage the pins or leave residue.

Flash the stock kernel again to see if this persists. You can find it on the OP of Sotmax's ROM.

If all this fails try flashing the ROM again.

Good luck

ROM Sotmax Ultimate V8

Kernel Yank555.lu-V2.7a
[Galaxy S III Original Android Development] sotmax:
What number do you hunting ??

This is with stock settings

No need of more oc my friend ;)

) ) ) over the air on Galaxy SIII ( ( (
[Galaxy S III Original Android Development] Yank555:
Well using my kernel, you just can't since it's not helping with battery life and bringing potential stability issues, I do not provide UV capability.

May be added sometime later, it is supposed to keep device cooler... but it's not on my priority list.

JP.

Sent from my custom Paranoid Android 2.54 / Yank555.lu CM10 kernel v1.2a Aroma (Linux 3.0.53) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] Yank555:
Been reported, but cannot be linked to the kernel, if you disable fastcharge, you're using 100% stock Samsung kernel code :(

Does your AC get detected as AC or USB ? Ha e seen that happening sometimes...

JP.

Sent from my custom Paranoid Android 2.54 / Yank555.lu CM10 kernel v1.2a Aroma (Linux 3.0.53) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] MuertoKo:
Afaik it's not kernel related at all, as it started happening since the first JB Leaks. At least not custom-kernel related but maybe something left behind in Update 5 (or 6?) of kernel... Anyway, it was solved by reflashing like crazy other kernels and rom's with wipe or without in most cases, no "standard" procedure I think :)
[Galaxy S III Original Android Development] AndreiLux:
That was a problem of the CMA allocation page handling and was present in all kernels. It's fixed in the latest version with the new Samsung sources.
[Galaxy S III Original Android Development] AW079:
Thanks for your replies.

I confirm the following:

Its reading as AC.

4.101v - 4.301v with charger in,

Temp, 29.5c

With logo upwards, looking from left to right, my stock Samsung USB cable seems to have only 4 pins.

looking like this: [ I0III ] with 1 groove empty, can someone please confirm if their cable is same?

Another non-standard [blackberry] micro USB cable I have has 5 pins, 1 in each of the grooves.

I have blown into and checked both for any debris, plus tried another 2 USB cable and 1amp charger plug, but the results are still the same.
[Galaxy S III Original Android Development] corrsea:
There is a whole thread about the 4 pin cables that have been supplied by Samsung and charging problems that have arisen.. Apparently they will change

them under warranty.

Personally I had issues with 2 Samsung chargers. These were intermittent and unpredictable when they would occur. Both chargers worked perfectly for 2 months before becoming problematic. I have never had an issue with a non Samsung cable / charger combination.

Other things you could try are to charge via USB on your computer. Also try charging while switched off.

There is a way to reset battery stats by dialing a secret code which might possibly help. I can't remember it at the moment but you may find it on one of the threads, (I think it's been mentioned on the sotmax ROM thread.)

ROM Sotmax Ultimate V8

Kernel Yank555.lu-V2.7a
[Galaxy S III Original Android Development] sotmax:
Solution is preety much simple.

Get the charger from note 2 that is 2amps and get a good usb cable from after market companies.

Personally note 2 charger with dexim visible ...combination beyond perfect... ;)

) ) ) over the air on Galaxy SIII ( ( (
[Galaxy S III Original Android Development] enigma1981:
Doesn't the extra ampage cause problems? or will the phone only draw 1a (or 1.2a depending on kernel settings...)
[Galaxy S III Original Android Development] sotmax:
The device will only draw the specific current that is needed or set by the kernel.

But more amperage will charge device quicker as many of the enrgy will not change to heat.. ;)

) ) ) over the air on Galaxy SIII ( ( (
[Galaxy S III Original Android Development] enigma1981:
Yeah true, if the charger is rated at 2A then drawing 1.2+A won't put excess load on the charger will it...

Good thinking, Batman!!

**heads off to eBay for a Note2 charger**
[Galaxy S III Original Android Development] Yank555:
The device will only draw up to what is configured, and the charger willing to deliver. If the charge has more, it will only hold more ready.

This is why setting AC to more then 1000mA makes little sense on stock charger ;)

And beware, while setting USB up to 1000mA will not tear on your battery life (since it's designed to be charged at 1000mA/h rate anyways), in theory it's life may be shortened if charged faster than this 1000mA/h max.

On the other hand, I so far have not seen a report on a problem, but in theory it's possible.

The fast charge interface allows (though not though Aroma) to disable the failsafe and to set AC charge level at any value up to 2300mA/h if you have a corresponding charger.

One user here (who asked for this possibility) tested this with a 3A/h charger (iPad I believe) and it worked fine at 2300mA/h, no specific battery heating or anything, and charge current is being gradually lowered to 100mA/h as charge level gets closer to 100%.

JP.
[Galaxy S III Original Android Development] corrsea:
I'm using an iPhone charger.:) it works very well. Picked it up for next to nothing in a parallel import shop. They have lots just lying about as here in NZ they legally have to swap them out for a local charger. They can't just use an adapter. I of course can:)

@AWO79

Here's the thread about the charging problems and the various solutions people have found. (There is a small sub group for whom none of the solutions worked and who have had their phones replaced by Samsung under warranty) However from your description of your symptoms I think you fall into the main group like myself.

http://xdaforums.com/showthread.php?t=1727540

ROM Sotmax Ultimate V8

Kernel Yank555.lu-V2.7a
[Galaxy S III Original Android Development] Yank555:
And at what rate do you actually charge on AC ?

JP.
[Galaxy S III Original Android Development] corrsea:
@1200

A full charge takes about 2 hours. I have tried higher values but the benefits were minimal. I rarely do a full charge cycle though (except to check battery life with new kernel or ROM version)

I also only charge to about 97 or 98% as I'm petty sure the battery is already at capacity by this point.

ROM Sotmax Ultimate V8

Kernel Yank555.lu-V2.7a
[Galaxy S III Original Android Development] Yank555:
As I posted earlier, will work on that tonight and keep you posted.

JP.

Edit : --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

The bad news is, I can reproduce the use of higher frequencies.

The good news is, I have sth. to work with ;)

As far I see this is only during the boot-phase of the system... I limited the CPU to 1.2GHz for testing purposes.

1.5GHz has been used 27s930, 1.6GHz 7s120 and those values are not changing any more.

So I guess where is set the boot frequency in the kernel to 1.4GHz must be somwhere late in the code (in terms of execution time on kernel initialisation).

Time to dive in the code now :D

JP.
[Galaxy S III Original Android Development] Yank555:
What has changed is AndreiLux's commit to solve the black crush issue (missing dark grey shades that are actually displayed in full black on the stock kernel, as well as added sharpness, which I can't really I noticed any difference. Resolution will remain untouched, that is a setting in the ROM (build.prop, density).

JP.
[Galaxy S III Original Android Development] Rikul:
After flashing this kernel my ext sd card wont get detected.... it is not abke to mount.. not using zram or swap.. can anyone help.. amazing kernel by the way...
[Galaxy S III Original Android Development] Yank555:
Is your sd card formated in exFAT ? If so, there is no exFAT support in this kernel (see FAQ for details).

You'd need to reformation the card in FAT32 and it will work again.

JP.
[Galaxy S III Original Android Development] Rikul:
Is there a way that i could do this without erasing data and without using computer :P i know i am asking for too much... i want to stay on this kernel.. plzzz
[Galaxy S III Original Android Development] Yank555:
Not that I know of, unfortunately :( But I have close to no experience with exFAT, I really don't like the idea of using closed source stuff, so the day I'll get a 64+Gb card, I'll either use it in FAT32, or better in NTFS or even ext4 linux file format...

I'm afraid you'll have to backup all the data, reformat the card (Windows won't allow you to reformat to FAT32 if the partition size is above 32Gb ! You'd need to google a little to find a different way to do this...) and copy the data back, I'm afraid.

JP.
[Galaxy S III Original Android Development] Rikul:
Thanks for ur reply.... i will search and find a way to solve it.. nd will post it if it is successful... i really like this kernel
[Galaxy S III Original Android Development] Yank555:
OK, I've been fiddling with this, and I've changed the code slightly, setting the default frequency at an earlier step, but still almost same kind of behaviour.

I've chatted with faux, and he told me on the Krait S3 (US version) it is the same behaviour. He pointed me towards where to look, might be Sammy's code somewhere messing with us...

Now it'd be interesting to see if this is a general thing with all OC kernels. Fact is that this is hard to track, you'd need to check CPU times right after booting (since the longer you wait, the smaller the % will be as it's only a few seconds) and the kernel needs to set freq. as default to stock 1.4GHz, which I don't know if that's the case on other custom S3 kernels.

Will keep you posted anyway as I get further with this ;)

JP.
[Galaxy S III Original Android Development] shtipu1111:
The only problem is I use a 32 Gb micro sd & used this 11extsd2internalsd_gs3_fat32 mod to change this card as my primary.After installing the kernel it reverts back to my 16 Gb internal. Any solution for this?? Tried 11extsd2internalsd_gs3_fat32 both stock & custom.
[Galaxy S III Original Android Development] Yank555:
Quick question, can you check if you still have init.d support, that these scripts are actually still executed ?

The ramdisk I use with the kernel does not handle init.d script execution, so if the ROM you're on relies on the ramdisk to do that, that would explain your issues.

I use ARHD, which handles init.d script execution on the ROM side (at the very end of /system/etc/init.post_boot.sh).

JP.
[Galaxy S III Original Android Development] Yank555:
Too late tonight, been looking for the cpu freq. thing all evening, nothing conclusive yet.

I'll add explanations about the Aroma options tomorrow evening.

JP.

Sent from my custom ARHD 13.0 / Yank555.lu JB kernel v1.6 Aroma (Linux 3.0.38) powered Samsung Galaxy S3 using xda premium
[Galaxy S III Original Android Development] shtipu1111:
how do I check that? Works fine with Siyah kernel.