yashsingh1/xdaforums huggingface dataset:
[Streak 5 General] RDilus:
just another error...

o year i using win7 x64 btw

###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Sun Jun 12 17:02:33 2011
Check image DBL: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\RC_us.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-5035-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Check Secure Boot is enabled
#Set Fast Boot Flag success
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#DT to DDR success
#backup FSBL to DDR success
Run HEX success
Check Secure Boot is enabled
Streaming hello success
Send Security mode success
Download partition table success
#Download DBL success
#Download FSBL success
#Download OSBL success
#Download DT success
#Download backup FSBL success
Erase EFS2 success
Wait for rebooting ....... ok
Wait for modem set up ......
Wait for ADB device .........
ERROR[D2]: wait ADB fastboot mode timeout!
Please check that device is exist and driver is properly installed.
Download Fail! - 2011/06/12 17:03:03
Elapsed Time: 29.57 sec
[Streak 5 General] vanemburghj:
There are special settings you must use for win 7 64 bit or qdl will not work. On the road right now will post them when I get home roughly 5 hours from time of this post. Think that will fix your qdl problem.
[Streak 5 General] RDilus:
no problem i will wait :)
[Streak 5 General] vanemburghj:
Sorry about the late post, the wife had other ideas for the day's activities anyways here you go:

Ok go to command prompt change directory to C:\Windows\system32.

Enter the following command:

bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS press enter

Enter next command:

bcdedit -set loadoptions testsigning on

Reboot your computer, should see something your desktop after bootup about being test mode or something like that, at that point you know you are ready use qdl.

Run qdl tool how I do it when really brick it, which I think you did is run old version, let streak reboot or get to black screen (most likely black screen), shut down Streak, most likely by removing battery, than run newer version of qdl, reboot and you should be on BB 305. All this is not a quick process so let your Streak run for awhile, before removing battery after each boot up.

Install custom rom, don’t use Steve’s 2.0.0 amss file it is corrupted use 351 or 354 amss and dsp1.

Once your streak is up and running, need to reset your PC, go to command prompt change directory to C:\Windows\system32. Enter bcdedit /deletevalue loadoptions, once complete, enter bcdedit –set testsigning off, reboot your PC and test mode warning should be gone from your desktop.

Let me know how things turn out.
[Streak 5 General] RDilus:
explain this part pls lol
[Streak 5 General] vanemburghj:
Do this first and if it works we will leave well enough alone, run version of qdl tool you downloaded from me. Let it go through the process and once it reboots, let it run for a bit, (mine usually takes anywhere from 10 to 20 minutes before OS starts up). If it worked right you are on BaseBand 305 and go from there. Am assuming since you tried once before you have the drivers set to Qualcomm HS-USB Diagnostics 9002, you will see that once you plug the streak in while holding volume up button.
[Streak 5 General] RDilus:
still get the same results

###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Tue Jun 14 07:07:34 2011
Check image DBL: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: C:\Users\RDilux\Desktop\QDLTool3rd_20101022_GAUSB1A130500\QDLTool3rd_20101022_GAUSB1A130500\images\RC_us.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-5035-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Check Secure Boot is enabled
#Set Fast Boot Flag success
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#DT to DDR success
#backup FSBL to DDR success
Run HEX success
Check Secure Boot is enabled
Streaming hello success
Send Security mode success
Download partition table success
#Download DBL success
#Download FSBL success
#Download OSBL success
#Download DT success
#Download backup FSBL success
Erase EFS2 success
Wait for rebooting ....... ok
Wait for modem set up ......
Wait for ADB device .........
ERROR[D2]: wait ADB fastboot mode timeout!
Please check that device is exist and driver is properly installed.
Download Fail! - 2011/06/14 07:08:04
Elapsed Time: 29.89 sec
[Streak 5 General] vanemburghj:
Question have you gone to Dell web site and downloaded latest drivers? When you have latest drivers let's go with my first thoughts on how to get you unbricked.

Load 2.7.4.5, holding volume up connect your usb cable, should get Qualcomm HS-USB Diagnostics 9002 next to the word port in the device section.

Run tool, hopefully it completes, now for me, when I went into Dell boot up only got a black screen. Thought it was the kiss of death, but than I ran 2.7.4.8.

My steps were, since I was at black screen, remove battery, wait about 1 minute, re-insert battery. While holding volume button on Streak connect usb cable. Again should see Qualcomm HS-USB Diagnostics 9002 by port. At that point I ran qdl, it completed, waited about 20 minutes for it to boot up and was on 305.

If it fails using 2.7.4.5, try going to http://webchat.freenode.net/ in channels enter #dellstreak and see if any of the folks there can help.

Wish you good luck, really thought I was on to something using the older version followup by the newer version of qdl to help you. Have been running and flashing for 4 months since I did that with no problem.
[Streak 5 General] Alahdal:
Search for streakflash it is an old version of QLD tool. It might solve your issue.

Sent from my Dell Streak
[Streak 5 General] vanemburghj:
He has both versions, think it is because he does not have Qualcomm HS-USB Diagnostics 9002 drivers.
[Streak 5 General] htcjikelly:
My Streak is back among the living!!!

It's like shake and bake and vanemburghj helped.

I used QDLTool 2.7.4.5 and I guess I am at baseband, well something weird now. I was trying to get back to 1.6 to totally start over, but Maybe that's not the way to go.

Alright I'm going home and then I'm going to play with this somemore.

Thanks!!
[Streak 5 General] htcjikelly:
I ran into that failed to connect Fastboot mode timeout thing today. It turned out that my computer didn't like the QDL tool's ADB driver. To fix your on a win7 64bit system do the following...

Go to your device manager (right-click over Computer and select manage, then select Device Manager)

Click "Android Phone"

Right click over "Android ADB Interface" (or whatever it says under Android Phone) and select "Update Driver"

Click "Browse my computer for driver software"

Click "Let me pick from a list of device drivers on my computer"

Select "Android ADB Interface"

Click Next

Done.

If yours is like mine then this will get you working again.
[Streak 5 General] Alahdal:
If you are still facing problem I think you need to do flash a full working backup using Riff Box " this worked with me" but you need to do it at your own risk.
[LG Optimus 2x] fallout0:
Hi guys!

This kernel is for stock/MCR ROMs only. I've tried to combine all the best bits from existing kernels into this one. This is based on the stock LG kernel.

First of all special thanks to Benee/Cpujuste since a lot the changes are from their kernels.

Features of the kernel:

* OC to 1500 mhz (minimum is 500 mhz but if you don't change it 300 mhz will work)

* GPU/AVP/VDE have been overclocked

* noop I/O scheduler

* Disabled all LG debugging messages

* 64 mb hack

* EXT4/CIFS built into the kernel

Few other misc changes to the kernel config. This is my first kernel so take it easy on me :)

Download:

[Release 1]

http://www.mediafire.com/?9g08udzg0d21fmj

[Release 2]

http://www.mediafire.com/?szkweyakk691wx2

[Release 3]

http://www.mediafire.com/?7z7rcw6x136pcaj
[LG Optimus 2x] fallout0:
Release 3

=======

- Fixed wifi thering

- Updated voltages/speeds a little bit so there aren't any > 100mv jumps as before

- Added multicast support

Release 2

=======

- Reduced AVP/VDE clock speeds

- Changed voltage/cpu tables to:

389 mhz ]

503 mhz ]

655 mhz ] Stock LG voltages/speeds

760 mhz ]

1015 mhz ]

1216 mhz - ] For overclocking

1408 mhz - ] Default voltages are higher

1504 mhz - ]

Release 1

=======

- Initial Release
[LG Optimus 2x] fajarep:
testing, hope you can release source code someday :)

info :

testing with FR18, stuck at LG logo...
[LG Optimus 2x] smokeweedevery:
do i need to make a wipe or wil this do it for me?
[LG Optimus 2x] 75markus:
no need to wipe when installing new kernel ...
[LG Optimus 2x] smokeweedevery:
ok thank:)
[LG Optimus 2x] 75markus:
applied at FR18b2, booting ok, did some testing now :

1.) very positive (for me at least) : LG Gallery works fine with this RAM hack kernel !(zooming ok without black bar !)

2.) LG videoplayer plays 1080p fine !

3.) videorecording with camera mod works fine @ highest settings

4.) quadrant @ 1000mhz : 3218, quadrant @ 1500mhz : 4761

5.) Linpack @ 1000mhz : 36.418, Linpack @ 1500mhz : 54.793

overall : phone seems very snappy even @ 1000mhz, vibration o.k.,

If it´s stable the next 10hrs, i think i will stay with this one, thx !

--------------------------------------------

bugs i found yet :

bootanimation is interrupted when starting 2.nd or 3.rd time (not a big problem)

O2X reboot is not working (reboot & reboot recovery) , or is it because of new CWM recovery 4.0.0.2. ?

tethering not working (tried wifi)
[LG Optimus 2x] peewster:
somebody tested the tethereing options with this kernel?
[LG Optimus 2x] fajarep:
wow, it seems it doesn't work with my FR18b2, may i know what do you set in your FR18b2 kernel? do you use default kernel?
[LG Optimus 2x] smokeweedevery:
will this work on stock?
[LG Optimus 2x] 75markus:
i used MCK kernel r14 without RAM hack before ...
[LG Optimus 2x] Mjuksel:
i guess so?
[LG Optimus 2x] 75markus:
couldn´t get wifi tethering to work ...

notebook connected to phone, but no internet connection ...
[LG Optimus 2x] Kenchitech:
Hiya... just wonder how do i back up the original kernal in case anything goes wrong??? I do wanna try this out on my stock ROM too...
[LG Optimus 2x] peewster:
All the froyo kernels with ramhack and oc have tethering issues, so it seems....
[LG Optimus 2x] 75markus:
just do a nandroid backup first, when you choose advanced restore, you can only restore kernel if you want, but i would advise you to make full restore if you need to, cause one module (wireless.ko) seems also different ...
[LG Optimus 2x] smokeweedevery:
not working on stock rom. cant boot
[LG Optimus 2x] 75markus:
just had some freeze when playing aroung with pimpmycpu, selecting different scheduler & undervolting,next reboot ended in bootloop -> reverted to MCK r14 ...

seems to be more stable at the moment ...
[LG Optimus 2x] thihaz:
same here

same here. freeze at LG logo.
[LG Optimus 2x] Redshark976:
Clean dalvik cache?
[LG Optimus 2x] smokeweedevery:
yes its not working
[LG Optimus 2x] Deadeye*:
Not working on [ROM] | WGSpoelstra's Gingerbread Edition | v4.3.1 | Android 2.3.4 | Based on CM7 .43 stuck on LG loading logo.
[LG Optimus 2x] smokeweedevery:
the same with fearkill rom stuck on lg logo
[LG Optimus 2x] fallout0:
Hmm that's odd that it's not booting because I am using mcry18b2 for my testing

I may update it back to 1400mhz and reduce the gpu clocks to see if that helps
[LG Optimus 2x] Redshark976:
And you're sure that it works on stock?

Would be great! Thanks alot
[LG Optimus 2x] fallout0:
Can someone please try to get the logcat output when they get stuck at the LG logo for me (if accessible)
[LG Optimus 2x] Redshark976:
Never flashed a kernel yet, not sure if i'll try it if there is a chance it won't boot..

Did you test it on u stock rom? I would try it, if it's easy to restory
[LG Optimus 2x] fallout0:
I haven't had a chance to try it on stock. If you have busybox installed in /system/xbin then it should boot

I am using Paul@Modaco init.rc file for the kernel which needs busybox to boot
[LG Optimus 2x] zarras:
runs gr8 on FR12 (fear edition)

thanks

i was using Cpujuste-Psycho kernel, but this is faster

EDIT: I can't play any .3GP (video) files :(
[LG Optimus 2x] fallout0:
I've updated the kernel - hopefully this will fix any booting issues

For now only use this kernel on MCR18 based ROMs
[LG Optimus 2x] wc326:
i have not try. but i think the reason why some of you does not work with this kernel , is mainly due to that your previous rom does not come with 64 Ram hack.
[LG Optimus 2x] fajarep:
i don't think thats true, my previous kernel is cpasjute with 64MB hack, i still can't use this kernel, gonna test new uploaded kernel..

UPDATE :

new kernel doesn't boot too, stuck at LG logo. already wipe, factory reset. using MFR18b2 from standard kernel(not overclocking kernel). i hope i can help with logcat, but i can't check logcat unless kernel boot correctly...
[LG Optimus 2x] Redshark976:
Busybox is included on stock rom? Wich means it should work I guess?
[LG Optimus 2x] 75markus:
first, thx for new version,

but could you have a look at the following bugs :

bootanimation is interrupted when starting 2.nd or 3.rd time (not a big problem)

O2X reboot (reboot & reboot recovery) or reboot to recovery with ROM manager is not working

tethering not working (tried wifi)
[LG Optimus 2x] kfallz:
Just wondering, about the overclocking of other parts than the CPU. Very interested in this, are they over/undervoltable also? Much editing needed or is it possible to make an app interface like pimpmy cpu? Haven't seen any other roms with it, so would be cool if you could say some more about it : )
[LG Optimus 2x] fallout0:
I'm trying to fix the wifi tethering at the moment :)

I managed to overclock the GPU and the other parts (video/audio engine). Then I saw the same mod on the voltKernel that was done before me ;). I also managed to overclock the system bus which overclocks the memory/2d/3d etc everything a little bit at run time. I haven't seen that on any other kernel yet. Not too sure about the safety of that one so I have left it alone for now.

It is easy enough to modify in the source code but I'm not too sure how difficult it would be to expose it to another userland for changing at runtime.
[LG Optimus 2x] fallout0:
Would anybody be interested in an AOSP release of Froyo? I managed to build one a month ago and had it up and running (with a few things not working). I thought, at the time, that LG would release gingerbread so I didn't bother continuing it.

Seeing as that may be a while away and (I believe) CM7 will be unstable until we have proper drivers, would you guys still be interested in an AOSP of froyo?
[LG Optimus 2x] Redshark976:
Can you try it yet on a stock rom?

Missing overclocking @ stock kernel

Use a recovery and flash it, than you see the result yourself?
[LG Optimus 2x] fallout0:
Sorry I don't think it is going to work on stock ROM at the moment.
[LG Optimus 2x] fajarep:
i gave up with this kernel :D

-flash with fresh FR18b2 ROM(from not overclocking kernel), it doesn't boot

-change kernel cmdline to match like cpasjuste cmdline doesn't work too

maybe you have something in your init.d directory that maybe different?, got 99compelete and 98mounts inside this directory(from FR18b2)

maybe you should release complete OS with your kernel too :D
[LG Optimus 2x] fallout0:
Bummer :) I'll try releasing an AOSP Froyo ROM in the near future with this kernel
[LG Optimus 2x] 75markus:
changelog [Release 3] ?
[LG Optimus 2x] fallout0:
Check second post ;)
[LG Optimus 2x] ilos:
flashed without issue on stock rom ( coming from cpasjuste kernel V5 )

see screenshoot :

EDIT : freeze @ 1504Mhz (must remove battery to reboot)
[LG Optimus 2x] 75markus:
ok, didn´t look at 2.nd post, thx :rolleyes:

will try out now ...
[LG Optimus 2x] peewster:
Ok, you fixed wifi tethering, how about usb tethering, somebody tested ?
[LG Optimus 2x] Redshark976:
Smoother than stock kernel? Stable?
[LG Optimus 2x] 75markus:
not for me, getting new highscores ...

haven´t tried tethering yet, but interruptions in bootanimation & no softreboot with O2X reboot still exist ...

for 1504 max i use NO undervolting for all values, (just for benchmarks)

for 1015 max (daily use) :-50mV (for 1015 & 950), -25mV (for 650 & 503)
[LG Optimus 2x] Deadeye*:
Did any one tried to flash in CM7 roms? I did and getting LG logo stuck when it shows loading bar.
[LG Optimus 2x] 75markus:
i think it´s MCR / FROYO only ...
[LG Optimus 2x] Redshark976:
Won't work on stock, just tried to instal it.
[LG Optimus 2x] kfallz:
Ok : ) Well, as far as how safe it is, overclocking & overvolting the CPU to 1.5Ghz is alot "worse" on the hardware than that :D And as long as the device is not overheated, the only result would be some more strain on the hardware, larger chance of hardware failure in maybe 5-10+ years instead of 10-15+ depending on OV/OC/etc so yea.

Mostly interested in it for the ability to slightly overclock and maybe undervolt at the same time, or just undervolt certain parts for better battery.
[LG Optimus 2x] ilos:
work on stock.... check my previous post..

EDIT : only stable value for me is 1408, bootanimation ok for me, O2X soft reboot result to a power off :D
[LG Optimus 2x] Redshark976:
Won't get pass LG logo..

How long is it stuck @ LG logo?

The bar "hangs" is this normal?
[LG Optimus 2x] ilos:
i came from cpasjuste kernel V5 , try this one before flashing this R3
[LG Optimus 2x] 75markus:
1504 mhz also stable for me, did 15 min benchmarking ... there seems to be differences in devices ...

when choosing O2X reboot to recovery-> device will turn off, but next boot will lead to recovery ...

bootanimation still interrupted, there´s a 1,5 sec break when starting again ...

but everything else is fine, stable´since 2,5 hrs for me ... running 1015 mhz / -50UV
[LG Optimus 2x] Redshark976:
cpasjuste kernel V8 works perfectly
[LG Optimus 2x] peewster:
V8 works good indeed, except for the tethering options....
[LG Optimus 2x] MadCobbler:
Doesn't there seem to be tethering problems with every OC/UV kernel at the minute or is that just me...
[LG Optimus 2x] fallout0:
If tethering fails its just because the kernel isn't compiled with the correct options. Release 3 has wifi tethering working.
[LG Optimus 2x] morfic:
I'd like to look at the source for this as thus far any oc of bus, mem, gpu for me is offset by throttling.

1.2 and 1.5 scoring identical frame rates.

Thanks in advance,

Daniel
[LG Optimus 2x] fallout0:
I'm at work at the moment but I'll post a guide on the changes I made tonight. It is hard to tell whether the clocks are modified at all. With the GPU overclocking I have noticed some difference from the default 333mhz and at 400mhz. Nenamark 2 scores change from 27fps to 32fps for example.

When changing the system bus I don't notice any difference in benchmarks even though tegrastats reports the RAM/VDE etc to be higher. But I've noticed that most of those never reach 100% usage anyway. I think it would actually be more beneficial to reduce the clocks on a a whole bunch of things and see if it is stable and battery life improves.
[LG Optimus 2x] morfic:
Thanks.

I have a solid 28fps at 1.2 through 1.5ghz.

I agree maximizing the gpu and ram throughput will be better than the 1.5ghz for a superficial 5400 in quadrant scores.

It seems the O2x dies in it's sleep at higher voltages than the/my G2x, so I upped them for Trinity O2x test kernel.

About "I'm not sure they even get used", agreed, I looked at too many places where the target frequency is compared to chip defaults and the lower of the two being used.

I added nv debug messages to show me frequencies stuck in that function, not guaranteed the boostkhz and throttlekhz functions don't reset it.

Maybe after summerbreak, right now, kid wants to be entertained.

You can later help me test public access to my new git, it's not complete, but what's not yet on there I can email you.

Thanks.