yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] Chicago281:
I would also like to know.. Need a good kernel for UVALH2
[T-Mobile, Samsung Galaxy SIII] clinthess:
From what I understand, the source code isn't out yet. Soon as it is... boom
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Exactly! Sammy never released the source for the UVALH2 kernel, and im guessing they're not going to at this point :(. Faux really cant do much without it unfortunately. Not his fault at all. Im just hoping now that when jb is released they let go of its kernel source quickly after.
[T-Mobile, Samsung Galaxy SIII] gordonzhao:
So which radio are you guys using this kernel with? I'm using it with UVALH2. Does it matter?

Sent from my Samsung Galaxy SIII
[T-Mobile, Samsung Galaxy SIII] hawaiianboi:
Im using the UVLI6 modem with the jb-cm-017m kernel, working good so far, no reboots or issues! =]
[T-Mobile, Samsung Galaxy SIII] mobilehavoc:
Does this work with LH1 leaked Rom for att?
[T-Mobile, Samsung Galaxy SIII] fmllc:
Hey Faux....

Have you had a chance to test this kernel on any other firmware besides UCALEM? I've been running your kernel since it came out. But everytime I try to upgrade

Passed UCALEM and I try to wake my phone while connected to 4g/lte...it literally freezes for a good 20 seconds before giving me access to the phone! It does not do it if I have a wifi connection established! I've narrowed it down to a kernel issue by doing a full wipe and installing apps/tweaks/mods one by one. And have verified by installing KToonsez's kernel and can say without a doubt the problem doesn't exist on his kernel. Have you heard of this from anyone else? Am I the only one? Many thanks!

Galaxy S III I747
[T-Mobile, Samsung Galaxy SIII] mobilehavoc:
Had same problem on LH1. Had to go back to stock kernel sadly

Sent from my SAMSUNG-SGH-I747
[T-Mobile, Samsung Galaxy SIII] fmllc:
going back to UCALEM will solve the issue...otherwise why not give Ktoonsez's kernal a shot while faux irons things out? No need to be on stock ;)
[T-Mobile, Samsung Galaxy SIII] faux123:
Yeah, I need to "iron" out this issue called time. Haven't the chance to even look at the new code yet
[T-Mobile, Samsung Galaxy SIII] fmllc:
Take your time brother...your efforts are much appreciated! :good:
[T-Mobile, Samsung Galaxy SIII] ilipac:
Does this have ex fat support ?
[T-Mobile, Samsung Galaxy SIII] emichon:
Stress Test app

Does anyone have anyone good Stress Test apps to test UV's? I've tried StabilityTest and I'll let it run for 30+ mins and everything will be fine, but then sometimes I'll go do something like browsing and it'll either hang or crash.

I have the voltages set in System Tuner as well as the same Min/Max Freq so I can test each frequencies.
[T-Mobile, Samsung Galaxy SIII] Sidneymac:
Is Zram and Joe's rcu already in the kernel and if yes how can we enable or disable them?

I also notice when I set min freq to 380mhz it automatically goes to 1000mhz .. Maybe its the software of nstools because it seems to keep the min frequency I set but the app recognize the min freq at 1000mhz.
[T-Mobile, Samsung Galaxy SIII] blimblim809:
Dead Link....
[T-Mobile, Samsung Galaxy SIII] herpehancock:
I run StabilityTest in the background and go nuts with every other app haha. Throw everything you can at it, if something FC's or it reboots...you're probably too low.
[T-Mobile, Samsung Galaxy SIII] :
Mine faired a bit better

I just flashed as well and it definitely seems to have freed up some speed due to the OC. I went ahead and did a quadrant and the score jumped to 5500 from 4700 on the stock kernel. I guess Faux was right "not all chips are the same."

[UPDATE]I've been using it for a day now and the only problem I've come across is the WIFI which keeps turning off and on suddenly. It's not coming back on right now actually and I have no idea why.
[T-Mobile, Samsung Galaxy SIII] sihartley:
Seems Fine on UCALH9 Stock Rooted!

Installed this kernel on my S3 last night, and it seems pretty stable, and is BLAZING fast! I have it clocked at 1.83Ghz using System tuner. :D

NO problems to mention at the moment! Only pluses :)

I will update this if there is anything to update, other than it being nice !!
[T-Mobile, Samsung Galaxy SIII] threshold350:
JB Update

faux, I was wondering if you were planning on creating a JB version now that official has been released. Thanks in advance.
[T-Mobile, Samsung Galaxy SIII] faux123:
Introducing my secret Kernel Enhancement Project: (Total Control for your phone and tablets) now available via Google Play Market! https://play.google.com/store/apps/...GwsMSwyLDEsImNvbS50ZWFta2FuZy5mYXV4Y2xvY2siXQ..

> CPU Control:

Displays cpu core frequencies in realtime

Allows adjustment of CPU governors

Allows adjustments of CPU Min/Max frequencies

Allows for "Set on boot" feature

> Voltage Control:

Displays current voltage per frequency

Adjusts CPU voltage

Allows for "Set on boot" feature

> CPU Governor Control:

(supports ondemand, conservative, interactive, intellidemand, and pegasusq governors. More to come later!)

Allows for CPU governor specific tweaks

> GPU Control:

Displays GPU freqencies in realtime

Allows selection of available GPU governors

Adjusts GPU max frequencies

Adjusts GPU Vsync capability

Allows for "Set on boot" feature

> I/O Scheduler Control:

(Supports built-in eMMC and SDcard if available)

Allows selection of available I/O schedulers

Adjust readahead buffer size

Allows for "Set on boot" feature

> Miscellaneous Control:

(depending on device, not all features are available)

Dynamic File Sync control

TCP Congestion Algorithm control

USB FastCharge control

WiFi power management control

USB OTG charge control

Vibration Strength control

Sweep2wake control

> Color Control:

(Currently only Galaxy Nexus is supported, more models to come later on)

Adjusts RGB Color in realtime

Adjusts RGB Gamma in realtime

Adjusts Contrast in realtime

Adjusts Gamma look up table in realtime

Allows for "Set on boot" feature

> Download Control:

(available only for OFFICIAL devices)

Checks for latest stable kernel and beta kernels

> Info Panel:

Provides kernel support and social networking followings :D
[T-Mobile, Samsung Galaxy SIII] youngchris29:
Just purchased it! :D:thumbup:
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Lol
[T-Mobile, Samsung Galaxy SIII] tmobilewinguser:
will also be purchasing. really hope we get a new kernel for stock jb theres nothing better than a Faux123 kernel:fingers-crossed:
[T-Mobile, Samsung Galaxy SIII] marseillesw:
+1 on the stock jb kernel! Been using faux kernels since the mt4g/ sensation..Would love to be able to use ur kernel on TW bro!!

sent from GS3 disguised as a GNote2
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Ehhh

---------- Post added at 06:53 PM ---------- Previous post was at 06:48 PM ----------
[T-Mobile, Samsung Galaxy SIII] threshold350:
Does this mean the new JB version is available through the app now?
[T-Mobile, Samsung Galaxy SIII] youngchris29:
Hey faux...I get a fc with app every time I swipe to the governor control screen. It won't allow me to make any adjustments or scroll to any other screens after I get to the governor control screen. I've tried uninstalling and reinstalling it a couple of times and even tried it on 3 different ROMs with the same results. I've tried it on frosty v9, aeonfluxx, and the new freegs3 r7 ROMs. I've tried it with the stock kernel and with trinity alpha 10 kernel. Any suggestions?
[T-Mobile, Samsung Galaxy SIII] waiters:
Same thing happens to me.. I think it's the third swipe..
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Same..
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Last
[T-Mobile, Samsung Galaxy SIII] faux123:
Quick Announcement:

I am redoing ALL of my SGS3 kernels.. please be patient.. "I'll be back" quoting ARRRRnold!​
[T-Mobile, Samsung Galaxy SIII] DeFlanko:
Sitting patiently for the JB touchwiz xD
[T-Mobile, Samsung Galaxy SIII] clninja:
I bought his app ... cant wait to use a jb tw rom with it
[T-Mobile, Samsung Galaxy SIII] photolarry:
Just wondering

Are you planning on making a TW JB version...I like your kernels and was hoping to use with latest Stock 4.1.1 (will m013 work since not huge differences between ICS and JB? Curious and thought I should ask. :cowboy:

---------- Post added at 09:56 AM ---------- Previous post was at 09:50 AM ----------

But I need to await a JB TW Kernel before this can work for me. (Read more of the threads and see you are working on stuffs. I know its not paid job so I will patiently await an answer :D
[T-Mobile, Samsung Galaxy SIII] faux123:
Return of the Mack ;) OP is updated.. TouchWiz kernel redux is OUT!
[T-Mobile, Samsung Galaxy SIII] J-ROCK:
The Mack is mother F*****g back!!!
[T-Mobile, Samsung Galaxy SIII] clninja:
This is still ics right? No new jb twiz yet?
[T-Mobile, Samsung Galaxy SIII] faux123:
This is jb kernel
[T-Mobile, Samsung Galaxy SIII] clninja:
Loving it so far... no issues with words with friends like on morfics kernel and everything else is butter smooth as well.

Running mainline so far and using faux kernel app. Might try ultimate at a later point but my goal is better battery
[T-Mobile, Samsung Galaxy SIII] Towle:
I'm also looking to get better battery life. Currently on rooted stock JB and battery is horrid. Quick question, what is your flash counter at? Curious if it climbs over 1 with each flash.
[T-Mobile, Samsung Galaxy SIII] clninja:
I have no clue how to even check flash counter
[T-Mobile, Samsung Galaxy SIII] tmobilewinguser:
does anyone know if PTP works
[T-Mobile, Samsung Galaxy SIII] xspeed9190:
Welcome back man, was getting worried for a little bit

:good::good:
[T-Mobile, Samsung Galaxy SIII] know50:
Welcome back man! Fashionably late I see lol
[T-Mobile, Samsung Galaxy SIII] froader:
Faux

Thanks for the update! I always used your kernels on my GNex.

I am running 13m and everything is very snappy and I am seeing 384 and deep sleep slots the majority of the time, however my battery drain much faster than the stock kernel.

Using your kernel app I notice that all cpu fqs are set to 1150mv, which is probably why.

Was the voltage table setup correctly?

Edit: tested 13u and voltages are also all 1500mv.
[T-Mobile, Samsung Galaxy SIII] cobraboy85:
the voltage tables are incorrect. faux where exactly did you get these tables from? they are so far off man it aint even funny. 1150 mv at only .384ghz? you gotta slap somebody for that one man wth 0_o

^this is why your battery life is terrible compared to stock. because no matter what low end frequency you are using, you are burning the same amount of juice. i mean you might as well clock it up to 1.2 ghz min and at least get your battery's life worth in performance right?

EDIT*** this is off the top of my memory... but if i remember correctly, the stock table should look something like this according to qualcom... i'll see if i can dig it up....
[T-Mobile, Samsung Galaxy SIII] faux123:
No, the voltage table is correct depending on the revision of the chip. Qualcomm documentation stated that some revisions of their krait chips need to maintain minimum voltage. So if you see voltage tables with same voltage values means you have one of those chips. The table is correct for some people.
[T-Mobile, Samsung Galaxy SIII] cobraboy85:
gotcha. any way to know which one i need? where is this documentation? did it say why that was the case?

i'm gonna look for that voltage table i know i had a reference for it somewhere but you should prob advise people of what hardware they are on vs what their vdd tables should look like so they are aware of this.

if i can't find my own reference, would you be able to correct mine for me so i know where i need to be powerwise? i am hw rev 10

thanks man
[T-Mobile, Samsung Galaxy SIII] faux123:
https://github.com/faux123/SGH-Krait/blob/jb_cm_exp/arch/arm/mach-msm/acpuclock-8960.c#L1694

Here you go! You will NEVER find any relevant document for Qualcomm chipsets. They are EXTREMELY secretive. The only documentations you would ever find is from the opens source kernel unfortunately. AND often, they are NOT commented, just some code that checks CPU ID and applying min voltage (you HAVE to read to code and figure out what it was trying to do).
[T-Mobile, Samsung Galaxy SIII] cobraboy85:
i see. that is a reference to your own git, however. still doesn't give me a reference for the voltage levels per device HW (according to QC as you stated your source came directly from them)... if i understand correctly then, based on the hw you have, then your kernel should adjust vdd levels accordingly upon boot, correct? reason i ask is because my brother's device, this previous user's device, and my other friend's device all are difference hw versions than me yet their vdd levels on your kernel are exactly the same with the 1150 min, and likewise, all of them run perfectly fine with something more similar to the table i posted. i guess i would simply ask where you originally saw this implemented this way?

thanks for your quick feedback by the way. really just more intrigued by this concept than anything
[T-Mobile, Samsung Galaxy SIII] faux123:
Read the code, Again there are NO hardware reference manual for Qualcomm chipsets ANYWHERE. They are super SECRETIVE!

The code is 100% from Qualcomm. The kernel adjust the vdd table based on CPU ID revisions. If your CPU falls within those IDs, the kernel will apply the minimum voltage required for those revisions. It's a hardware bug that they are fixing using software (kernel in this case). The reference HW voltage level is irrelevant for those CPU IDs with this bug.

I don't want to change it in my kernel because Qualcomm put it there for a reason (exactly why or what the bug is we will NEVER KNOW because Qualcomm does NOT publicly state anything about the inner workings of their chips).
[T-Mobile, Samsung Galaxy SIII] cobraboy85:
finally found it here... check this out man.. funny because mine defaulted to the 1150 voltage applied by those 3 lines of code, but i have been running this voltage here for a lonng time... with absolutely no issues. i would encourage anybody here to give these a shot and they will work perfectly fine. :silly:

"384000 850000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "432000 875000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "486000 875000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "540000 900000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "594000 900000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "648000 925000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "702000 925000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "756000 975000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "810000 975000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "864000 1000000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "918000 1000000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "972000 1025000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "1026000 1025000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "1080000 1075000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "1134000 1075000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "1188000 1100000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "1242000 1100000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "1296000 1125000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "1350000 1125000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "1404000 1137500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "1458000 1137500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "1512000 1150000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "1674000 1200000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "1728000 1250000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "1809000 1275000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;

echo "1890000 1300000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
[T-Mobile, Samsung Galaxy SIII] bofiana:
So should I set this in System Tuner Pro or is there a way to make a script to add into system/etc/init.d?
[T-Mobile, Samsung Galaxy SIII] cobraboy85:
do it in system tuner pro, should work perfectly fine.

that is straight from qualcom source, not samsung.

EDIT*** hey faux, another question for ya man, so with that line of code to check for hardware, shouldn't any changes be reverted by the kernel? mine are holding true and i can verify that they are not just getting reapplied constantly because sys tuner is not even showing up once in cpu threads.

they stuck after a reboot as well, applied through init.d

what are your thoughts?

EDITTTTT*** and bofan.. after you set it up this way, add 25mv across the entire map just for good measure. wouldn't hurt, but def would still save you power in those lower frequencies man. not sure why samsung implemented this into their source, but qc did not.
[T-Mobile, Samsung Galaxy SIII] bofiana:
Ok, will do man. Good looking out!
[T-Mobile, Samsung Galaxy SIII] froader:
I am in agreement with your voltage table and think I was successful in the past with 75mv less. At least I remember 192 or 384 running at 800mv.

Not sure that I understand why it would be 1150mv across the scale, which obviously burns up the battery.

Did you modify the init.d script in the kernel zip to get what you want? I am curious how I can also do this. init.d is obviously new to me...

Thanks
[T-Mobile, Samsung Galaxy SIII] cobraboy85:
I'm gonna give you the easy method and just say download system tuner, don't need the pro version. Adjust the tables to match what I posted, run it for a day, see how it performs, and then if all seems well, have it apply the cpu values upon boot complete.

Or if you want a direct copy of my init.d folder I can zip it up and send it to you. Let me know.
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Only will show flashes through Odin.. Not rom or kernel flashes through custom recoveries
[T-Mobile, Samsung Galaxy SIII] jdidtht:
What kernel is this

Infected with anthrax
[T-Mobile, Samsung Galaxy SIII] honover:
Is two way call recording working on this kernel?
[T-Mobile, Samsung Galaxy SIII] faux123:
is there a two-way recording kernel patch you can point me to? I can add it if you can point me to a working kernel patch for it.
[T-Mobile, Samsung Galaxy SIII] Towle:
That's no longer true with JB. Just booting into a custom recovery can/will trip the counter.
[T-Mobile, Samsung Galaxy SIII] froader:
Yeah, I have a few apps that I can use to adjust the voltages. I've just never seen a voltage table like this and was wondering how the scripts can be used to fix this.

I think that I will keep my eye on this thread for a bit longer before investing more time in testing. I would really like to know how battery life is with the voltages set properly.

Please keep us posted and I'll let you know when I am ready to take you up on that offer.

Much appreciated!
[T-Mobile, Samsung Galaxy SIII] DeFlanko:
Loaded it for JB Touchwiz... AMAZING... i highly recommend buying the app to not only support the dev, but to get the latest updated kernels lol
[T-Mobile, Samsung Galaxy SIII] cobraboy85:
Been running this voltage table for a long time... you are fine man

Edit** easy on the new guy
[T-Mobile, Samsung Galaxy SIII] CousinMikeyP:
Hey faux...

Running this on Frosty v11 ROM, and it has been flawless. Thanks man! :victory:

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

Hey cobraboy85...

I just installed system tuner FREE version

I really want to give this a shot, but where in system tuner do I add/edit these values. I dont want to do something to "eff" up my SGS3. I never used system tuner b4. just want to be cautious. I do have ROM toolbox would I be able to use that, btw sorry 4 all the noob questions, we all started out as noobs after all lol :p

Thanks in advance
[T-Mobile, Samsung Galaxy SIII] CousinMikeyP:
cobraboy85...

I'll take that init.d ZIP file if you don't mind :o

Thanks cobraboy85!
[T-Mobile, Samsung Galaxy SIII] Earthdog:
Compatibility

So I just want to make sure it will work. Does version 13m support the Official ATT TW JB release Current I747UCDLK3 (JB 4.1.1) ? I am stock rooted on this build.
[T-Mobile, Samsung Galaxy SIII] cobraboy85:
When you open system tuner there is a tab on the left side that says "voltage"

If your kernel does not support UV, that tab will not be there.

And I'll zip up my init.d folder right now and send it to you
[T-Mobile, Samsung Galaxy SIII] CousinMikeyP:
It's there, but I'll wait for you to zip that file for me I had a bad experience with system tuner that's all. I just did a

nandroid

to be safe so I can flash your .ZIP Thanks again Bro! your da man :cool:
[T-Mobile, Samsung Galaxy SIII] Babyj303:
Ill take a copy as well if you can kind sir
[T-Mobile, Samsung Galaxy SIII] freeza:
Dude, this is not true. There is no way there are versions of the krait chips that differ that much that one would allow 1.15v at a low MHz like 384 and the other 850mv. It was a simple flaw in the Samsung source and nothing more. The battery life difference would be too huge for that to make sense. There would be no reason to downclock if your processor was sucking up the same juice at 384MHz as it does @ 1.2GHz.
[T-Mobile, Samsung Galaxy SIII] faux123:
The problem is we are second guessing Samsung/Qualcomm. Because there are no documentation stating either way. Samsung has kept this code from ICS to their JB branch. If it was a mistake on their part, I am sure they would have removed it, but they didn't. From our perspective, we will never know the reason for it in the first place. We have to give Samsung/Qualcomm some credit, they are NOT as stupid as some other people have claimed here.

I may remove the check in a beta version to test them out.
[T-Mobile, Samsung Galaxy SIII] se1000:
Hey Faux! Good to see you over here I finally moved on from my Sensation!
[T-Mobile, Samsung Galaxy SIII] Orical:
Just flashed, I am usually nerved by some of the kernels released but I've been using your work since the mytouch era and I've never had a bad experience. Thanks for taking the time to support the device.

Sent from my GS3
[T-Mobile, Samsung Galaxy SIII] clninja:
Been using mainline and all is great... gonna move on to ultimate and see how it does
[T-Mobile, Samsung Galaxy SIII] waiters:
Are there any plans to support higher oc like 2.1ghz?
[T-Mobile, Samsung Galaxy SIII] cobraboy85:
the maximum frequency during boot needs to be addressed first. not everybody's device can boot at 2.1 ghz... mine can, i know for a fact. but my handset is a freak among monsters. go figure. when i was testing morfics alpha 18 kernel (1.944 GHz, and not available to the public) i was able to boot it, and he was not. odd.

anyways, faux, i have another question for ju... or rather, a suggestion... since voltage is flat across many of the tables (not mine obviously but your mainline ones, unaltered) i would recommend raising the min screen off profile to something a little more aggressive. lots of skipping and blipping when playing bluetooth audio through pandora radio while connected to wifi. 594 doesn't seem like enough to handle a lot of load like that while the screen is off... when the panel is on, issue goes away almost immediately. and even with the voltage tables from QC (assuming based on what you said - chips will vary in voltage based on rev) 702 makes a little more sense as the power draw is exactly the same as 594 under that unique voltage table. 594 just doesn't seem logical in any case. :highfive:

:good: