yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
Yes, that seemed to do it. HD 720 video records and plays back like it should. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Ran into some difficulties, this is going to take a little bit more work than I initially intended :silly:

And thanks Quantum for the new kernel. I was going to report on the previous version I had some BSOD's but that was DEFINITELY because of my underclocking and nothing else. I'm gonna do some tweaking to governer/scheduler settings this time around because I'm curious.

Any news on moving this thread from Android Development to ORIGINAL Android Development? I think it's warranted because of the custom kernel. People tend to follow the "Original" ROM's moreso than the ones in regular dev, at least I know I used to until I came along this puppy once 10.2 dropped....I'd love to see this thread mature into that section, just my personal opinion.

Is there any way from stopping Trickster from wiping all my settings once I flash a new kernel? Even the profiles I have save get wiped! I have to turn off MP-Decisions, undervolt, and tweak some stuff and save new profiles all over again. How can this be prevented? Also upon flashing the newest kernel my voltages changed to 1150 across the board, I know that can't be right.

Could we have a changelog for the 1.95 test build? You know by now I'm a flashaholic, I found it and I'm getting my phone ready to flash it right away.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
FWIW, I'm running the latest update to Trickster. I've noticed that every time I flash a new kernel, it now shows a notification instead of just blindly wiping all my settings; the notification gives me the option of doing that or retaining my previous settings (with all dire warnings of the Coming Of The Apocalypse, of course).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Running the latest version I do not get this prompt :(

What are the stock voltages? I know it's not 1150mV accross the board like I have right now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
Oh wow. I just noticed my voltages are 1150 from 1200mhz down to 384mhz. That doesn't seem right.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tybalt:
I don't know if these are the exact stock voltages... but this is what I am running:

1512	1200

1458	1187

1350	1175

1242	1150

1134	1125

1026	1075

918	1050

810	1025

702	975

594	950

486	925

384	925

It may help to give you a starting point instead of having all those ugly 1150s.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Wipe it? Idk mine start at 850 so maybe something weird happened during flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] curls00:
I'm running the latest Trickster and my voltages stayed stock. They are as follows:

MHz = Voltage

1512 = 1150

1458 = 1137

1350 = 1125

1242 = 1100

1134 = 1075

1026 = 1025

918 = 1000

810 = 975

702 = 925

594 = 900

486 = 875

384 = 850

I've never touched my voltage settings, so these 'should' be stock voltages.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Strange. I'm pretty sure it was Trickster giving me this notification in the status bar. I'll do a test later and make sure I'm not talking out of my ass. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
I wiped, installed 1.9, and let it boot up. Here are the voltages that came up:

1512 - 1200

1458 - 1187

1350 - 1175

1242 - 1150

1134 - 1125

1026 - 1075

918 - 1050

810 - 1025

702 - 975

594 -> 384 - 950

Then I installed the 1.45b kernel, wiped cache/dalvik, and rebooted. The voltages that came up were the same as above down to 1134. Beginning with 1242 down to 384 the voltages were all set to 1150.

<shrug> Beats me.... I've reset all my voltages to the defaults and everything is running fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Just tested it by flashing kernel 1.45 over 1.45b. I do get a notification in the status bar from Trickster MOD about the changed kernel, and whether to retain the previous settings. Note that the notification is due to my having "set on boot" enabled. FWIW, I'm running Trickster MOD v2.6.770.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I'd rather not wipe my phone just for the voltages, I just inputted the ones provided above. Hey Pwn, could you post a changelog of the 1.95 test?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
I agree. I did it just to see if it was something I (and you) may have done that caused the voltages to be set that way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I use some interactive tweaks from this thread: http://xdaforums.com/showthread.php?t=1369817

i) For battery:- [Interactive and battery?!! I'm capping the highspeed_freq in the hope of saving battery]

echo "95" > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
echo "1024000" > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
echo "10000" > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
echo "40000" > /sys/devices/system/cpu/cpufreq/interactive/timer_rate

Also there are these:

ii) For performance:- [Assuming your scaling_max_freq is equal to or above 1400 mhz)

echo "80" > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
echo "1400000" > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
echo "40000" > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
echo "20000" > /sys/devices/system/cpu/cpufreq/interactive/timer_rate

but I have not tried the performance tweaks, only "for battery."

Here is an explanation of the settings:

i) hispeed_freq - Hi speed to bump to from lo speed when load burst. (Default value is scaling max freq)

ii) go_hispeed_load - Go to hi speed when CPU load at or above this value. (Similar to Up-Threshold in other governors)

iii) min_sample_time - The minimum amount of time to spend at a frequency before we can ramp down. (Sounds like Lazy governor?!)

iv) timer_rate - The sample rate of the timer used to increase frequency.

And for ROW scheduler, I use the settings from BalancedBullV3:

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

Scheduler: ROW
Scheduler Adjustments:
> hp_swrite_quantum = 3
> low_starv_limit = 8000
> rd_idle_data = 5
> rd_idle_data_freq = 15
> reg_starv_limit = 4000
> rp_swrite_quantum = 2
> rp_write_quantum = 2

Maybe somebody could get some use out of this or Pwn could let me know if some of these settings are not a good idea or whatnot. I have yet to go a full day with them as I've been home all day plugged in but once I get a charge cycle in I'll let you guys know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I haven't touched the ROW scheduler, only used Seeder to extend I/O. I was planning on tweaking interactive for the next release, I use 810 as hispeed, and target loads at 95. That's all I touch. I'm getting amazing battery on the latest kernel release, so I've been sticking with interactive.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I changed target loads to 95 and hispeed to 810MHz, thanks for the tips.

Do you know anything about the ROW scheduler tweaks I posted? A lot of people love balancedbullv3 for kt747 so I figured i'd try the ROW settings out.

If it's redundant I might as well just flash the kernel again and just stick to tweaking interactive.

Also what's your opinion on build.prop tweaks? I use a handful of them (maybe a dozen lines or so) that someone PM'ed me, he nitpicked them from a handful of guides and they're supposed to increase battery, performance and network speed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
Never knew what any of these really did. Thanks for the link! I'm gonna mess around with these a bit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Awesome rom, upping voltages by 50 fixed my problem, but now I'm going into withdrawal from not flashing something in two days :laugh:

Just a question: How come Quantum has different notification toggles than the current CM 10.2 nightlies? Aren't they being made from the same source? Just a question I've had for a while, not a biggie, I've actually grown to like them...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
http://d-h.st/bQW

That's a new kernel, should have fixed the voltage issues hopefully. I also tweaked interactive as much as I could, along with asswax.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Awesome, i'll give Interactive a shot, usually I try conservative but I never really found a governer for battery life that won't give me SOD but also won't lag the hell out of my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
I installed the new kernel and it still had all lower voltages set to 1150. Also, according to BBS my phone is not sleeping. Other than correcting the voltages and disabling MP decision I'm using stock settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Did you wipe cache and everything? If it's an issue I'll just completely remove the undervolting feature and so on. I'm using the stock clock table.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I'll flash it and see if it messes with my voltages and sets them to 1150 again...my trickster settings and saved profiles don't carry over anyways, so it'll be stock/your settings.

Pwn what's your say on build.prop tweaks? I use a handful of 'em!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Depends. I only mess with build prop to fix audio and such. Which tweaks are you talking about?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
These are the ones I picked so far:

#TWEAKS

#Power Saving
wifi.supplicant_scan_interval=420
pm.sleep_mode=1
ro.ril.disable.power.collapse=1
ro.mot.eri.losalert.delay=1000

#3G/Signal
ro.ril.hep=1
ro.ril.hsxpa=3
ro.ril.gprsclass=12
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
ro.config.nocheckin=1

#Boot Time
ro.config.hw_quickpoweron=true
persist.sys.shutdown.mode=hibernate

#Telephony
ro.telephony.call_ring.delay=1000

#Better Scrolling
ro.max.fling_velocity=25000
ro.min.fling_velocity=20000
windowsmgr.max_events_per_sec=90

#Proximity
mot.proximity.delay=25

#Disable Error Reporting
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1

#Photo/Video Quality
ro.media.enc.jpeg.quality=100
ro.media.codec_priority_for_thumb=so
persist.sys.use.dithering=1

ro.vold.umsdirtyratio=20
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Any chance of dnscrypt working itself into the kernel?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Newest kernel still has 1150 as the default voltages, had to load up stock on my own.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
Yes, in recovery after I installed the kernel I wiped cache/dalvik. This morning BBS is reporting that the phone *is* entering deep sleep again. So maybe it was just an issue with kernel 1.45b. I'll report back later today on how 1.45d is doing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Volume

Is there a setting to get more volume (speaker) on the ROM? Or a script to do so? I can't seem to find anything. Some of the other ROMs have a volume boost setting.

My ears still ring from Ft. Sill artillery shells!!!! :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Gah. Well if it makes you feel any worse it's because you have an earlier revision of the processor, slow. I have a rev4 processor, check in about, and that means that I have a normal cpu. If your voltages default to 800 then you have a fast cpu.

Was never worried about this, sometimes after a cache/dalvik wipe the phone has to reconnect to GPS and google services and such.

Use Nova, Go to shortcuts, activities, advanced settings. All the way on the last tab should be Extra Gain for earpiece. It will stick after a reboot so don't worry! I've been playing drums for a long time so my ears are probably as worse as yours :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Volume

Thanks!! Works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibilln:
Pls translate for this dumb-ish follower.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
Bah. That's what I get for buying the S3 when it first came out. I must have the earlier / slow processor. lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Check in your about. It should say rev(x) somewhere.

Anyways I'll be off this for a litte bit. Just remembered I have a paper on the New Deal due at 530! Oops! :cyclops:

I've also been looking into removiing MP-Decision and replacing it with Thalamus auto_hotplug. How does anyone feel about that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
Yes, rev 0 (v71) is what it says. Good luck on your paper! :good: :victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
So we've officially moved! This is great news!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Same here. I should know by now to never buy the first model year of a new car. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
What is new in the QuantumKernel-v1.45d?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Tried the new kernel somehow murdered 11% in 20 minutes of light usage :confused: I'm going to install BBS today, but for some reason there's no wakelocks and no rogue apps running haywire...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I've been noticing a much larger battery drain. Maybe I should revert the interactive tweaks?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Finished my paper early, working on a new kernel with some nice new features. OC is making a comeback once more! I also fixed Interactive and included a secret goodie (see if you can find it). This should fix voltage issues as well.

Here you guys go:

http://d-h.st/T77

Let me know of issues ASAP!

Check on gpu sticking at 400, and see if my decision comes pre disabled or not
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
MP Decision was on by default for me. Using Trickster.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Is GPU sticking at 400 MHz?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
GPU is set at 480 by default but device status shows it at 400.

Edit: I've seen it hit 200 and 300 in device status.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
What I meant is that does it actually stick at 400 when you're idling. It seems like default behavior to me.

Also are your voltages fixed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
I was at idle when I seen it dip down to 2 and 3 hundred. My voltages look like they were okay. I hadn't touched them. I actually installed trickster to get the information for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
thank you very much, I'm trying to make sure I'm not about to pop out some buggy POS kernel release :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
No sweat. I love what you do and am more than happy to help when I can.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
1.45e seems fine to me. whats this little something you speak of pwn? cant find it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
GPU Overclock! I just want to make sure that everything works before releasing it fully.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I removed GPU overclock until you guys tell me if it goes down past 400 when idle.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
It's weird. Once I stop touching the screen it drops to 200 for one or two seconds then goes back to 400 and stays there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dieselrellim:
Mine drops to 128
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Does it drop to 128 or so permanently or stay on 400?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dieselrellim:
When I am not touching the screen it stays on 128 and jumps up to 300 then 400 when I touch the screen
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
So it works like it should? Does it ever go to 480?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
I thought there was something wrong with the build till I found out that Rogers is out across Canada. Imagine what a steaming pile of shut a network has to be for them to lose it all at once.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
I never seen it hit 128. If I had to guess a percentage, it was at 400 probably 97 percent of the time. I also never seen it hit 480.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
What kernel were you using previously? I'm running stock CM kernel and even that one runs at 300 on standby! I mean... it makes no sense....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dieselrellim:
No mine is set at 400 max
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
I did a clean install of 1.9 last night along with 1.45b. Touched nothing kernel settings wise. Installed 1.45e kernel today and installed trickster to get you the information you requested. I've never touched anything GPU related ever.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
For some reason, I've been getting terrible Google Service battery drain 4 and half hours awake? :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It's not connecting to GPS. Just make sure your RIL isn't giving you wakelocks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Got some goodies for you guys, I can revert anything if needed.

First of all, for testers and I guess for public release is now QuantumROM v1.98. It features the newest kernel and a newer CM base, as well as a foothold into the future of Quantum.

First up we have QuantumROM v1.98, which is a test. It features the 1.46 kernel as well as upstream CM changes.

Then we have Quantum(Kernel)-v1.46. It features:

Overclock added back in and fully stable!

Voltages should be fixed

GPU overclock to 480 Mhz.

Tweaked Interactive and Asswax for battery life

Debug stuff removed for a faster kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Downloading now, will share my experience!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmorris003:
1.98 working good here but anything above 1.9 for me has the screen waking up every 5 minutes or so, is there a fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Happening on 1.98 also?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmorris003:
Yes, I only find 1.9 and below don't have this issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Best battery life I've had so far with my tweaks and Quantum 1.95 and 1.45d kernel.

What interactive tweaks did you take out/put in? I'm getting ready to flash 1.98 and 1.46 right now!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dieselrellim:
My gpu is stuck at 400 at idle with the new ROM and kernel

---------- Post added at 06:31 AM ---------- Previous post was at 06:02 AM ----------

I flashed 1.45e and my GPU is dropping and holding at 128 at idle
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alkiter:
Same here. 1.98 running great, only GPU doesn't go below 400 at idle. Still, battery usage looks good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Dirty flashed v1.98 and kernel v1.46 this morning and I too am experiencing the random screen on every so often with GPU OC'd to 480. I also noticed TricksterMOD won't allow me to change the GPU gov to interactive; it automatically reverts to ondemand.

However, when I drop the max GPU freq to 400, the screen stays turned off...

^Add to that - GPU is stuck at 400

Just had the screen turn on randomly again with GPU max at 400...

Edit: Reflashed v1.98 after wiping cache & dalvik; still getting a random screen on...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It has absolutely nothing to do with GPU, it has everything to do with CM. I don't know what's causing the random wakes for you guys, as I honestly haven't seen a single one on 1.98. It seems to happen very very sporadically
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
You mentioned the older processor model, maybe that has something to do with it?

Mine shows the old type (I think): rev 0 (v71)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
No that's what had to do with stability and voltages. Are your voltages at least fixed>
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
If I can switch gears for a moment here... ;) I've noticed this Bluetooth issue on recent builds of Quantum (which tells me that it's an issue with recent CM10.2 nightlies). I have my phone paired to my Dodge Dart's Uconnect system. It's configured as a phone device only,

not

as a media device (my Dart has an SD card slot for my MP3s, and I don't need to stream music via BT thanks to SiriusXM's variety). What I've noticed is that when the phone is connected, there's absolutely no audio going out the phone at all--no ringtones, no notification sounds, and most important to me, no Google Navigator turn-by-turn audio. I know that this is a recent development because older Quantum releases did not have this problem: the phone could be connected, but sounds were still coming from the phone's speaker. I also know that the audio is indeed being forced through Bluetooth, as I was talking to my girlfriend the other day via BT while Navigator was directing me to her son's hockey rink, and Nav's turn-by-turn voice was coming through the car speakers.

Has anyone else noticed this particular issue, or is it just me? Because to my thinking, if you pair BT as a phone but

not

as an audio device, ringtone/notification/media sounds should be coming through the phone, not BT.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
They switched it a little while ago to route all sounds through active audio connection. So that means everything will play, and they made it as a way to cut down on choppiness when music plays. It's been like this since v1.9 I believe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
So in other words, they've broken correct functionality in order to try to fix something else. Real brilliant move, CM team. :p