More on the Radio & Under-volting - Nexus One Android Development

So I have no been using a kernel patch that is giving the radio full voltage as opposed to under-volting the phone.
My results are:
Before: -111dB to -101dB with 1-2 ASU
After (same EXACT location) -97dB to -83dB with 10 ASU.
This is literally without moving the phone an inch. I patched it with a boot command so I could go back and forth and it seems to be directly related. If anyone else would like to test,
Cheesebaron has been kind enough to write this up....
http://dl.dropbox.com/u/2991343/zImage

Will this patch overwrite any other values besides getting more juice to the radio on an undervolted kernel?
For instance, if running pershoots oc-uv kernel then applying this patch would it give the benefits of both kernel and radio?

Can you post the patch itself so we can see what you're doing? All you provided is a zImage which will overwrite any kernel currently on the phone.

Yes, patches please...
How about the standby battery life ?
FYI, fastboot boot zImage will not replace/reflash the zImage in the ROM. It just boot and load to the new zImage. Rebooting will use back to original zImage in the ROM.

momentarylapseofreason said:
So I have no been using a kernel patch that is giving the radio full voltage as opposed to under-volting the phone.
Click to expand...
Click to collapse
I wonder what happens if you give it just a "little" more juice
Other than my brain will get fried quicker ...

wonder what effect this has on the SAR value. Harder to test ofc :/

Code:
creating boot image...
creating boot image - 2146304 bytes
downloading 'boot.img'... OKAY
booting... OKAY
** EDIT **
Got stuck on first boot, its ok now...
Kernel: [email protected] #1 (-81 16)
Kernel: [email protected] #1 (-81 16)
Same result on Cyanogen 5.0.7 test2 on desk have not moved, maybe I will test this in a hard reception spot.

nandroid restore?

pls provide patches/source.
thx.

1wayjonny said:
Code:
creating boot image...
creating boot image - 2146304 bytes
downloading 'boot.img'... OKAY
booting... OKAY
** EDIT **
Got stuck on first boot, its ok now...
Kernel: [email protected] #1 (-81 16)
Kernel: [email protected] #1 (-81 16)
Same result on Cyanogen 5.0.7 test2 on desk have not moved, maybe I will test this in a hard reception spot.
Click to expand...
Click to collapse
If it got stuck on boot and you rebooted, the reason you're seeing the same results is because you have the stock kernel again. The command you sent does not FLASH the kernel. It only boots with it.
To all those asking for the patch, it's in the first post
EDIT: Didn't see that you indeed had different kernel numbers

momentarylapseofreason said:
If it got stuck on boot and you rebooted, the reason you're seeing the same results is because you have the stock kernel again. The command you sent does not FLASH the kernel. It only boots with it.
To all those asking for the patch, it's in the first post
Click to expand...
Click to collapse
No they are talking about the uncompiled source files not the Zimage.

Refer to this thread then because I don't have the source
http://forum.cyanogenmod.com/index.php?/topic/3368-power-for-radio/?
Here are the freq tables though....
struct clkctl_acpu_speed acpu_freq_tbl[] = {
{ 19200, CCTL(CLK_TCXO, 1), SRC_RAW, 0, 0, 1000 },
{ 128000, CCTL(CLK_TCXO, 1), SRC_AXI, 0, 0, 1000 },
{ 245000, CCTL(CLK_MODEM_PLL, 1), SRC_RAW, 0, 0, 1000 },
{ 256000, CCTL(CLK_GLOBAL_PLL, 3), SRC_RAW, 0, 0, 1000 },
{ 384000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0A, 0, 1000 },
{ 422400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0B, 0, 1000 },
{ 460800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0C, 0, 1000 },
{ 499200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0D, 0, 1025 },
{ 537600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0E, 0, 1050},
{ 576000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0F, 0, 1050 },
{ 614400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x10, 0, 1075 },
{ 652800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x11, 0, 1100 },
{ 691200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x12, 0, 1125 },
{ 729600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x13, 0, 1150 },
{ 768000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x14, 0, 1150 },
{ 806400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x15, 0, 1175 },
{ 844800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x16, 0, 1200 },
{ 883200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x17, 0, 1225 },
{ 921600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x18, 0, 1275 },
{ 960000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x19, 0, 1275 },
{ 998400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x1A, 0, 1275 },

there is nothing new here. you've just increased the voltages back to shipping stock.

I think that's his point that if under volt then that's where bad reception comes from?

So my question is will this still give us the performance we want from the processor while not juicing our batterys while improving reception..

pershoot said:
there is nothing new here. you've just increased the voltages back to shipping stock.
Click to expand...
Click to collapse
Thank you Captain Obvious. The point is that while we are getting better battery life, we are losing reception. So we can have a fully charged phone that can't make a call. Logical to me?

pistol4413 said:
So my question is will this still give us the performance we want from the processor while not juicing our batterys while improving reception..
Click to expand...
Click to collapse
Eh!? Performance (if you are referring to processing speed) wasn't affected by voltage changes in the way that Cyanogen/pershoot were modding them.
As for "juicing" our batteries, yes, it will take more power to keep the voltages up. I'd much rather have to charge my phone more often than not be able to make a call.

yes I noticed this too with the latest cyan release my signal is crap all the time, now.

momentarylapseofreason said:
Eh!? Performance (if you are referring to processing speed) wasn't affected by voltage changes in the way that Cyanogen/pershoot were modding them.
As for "juicing" our batteries, yes, it will take more power to keep the voltages up. I'd much rather have to charge my phone more often than not be able to make a call.
Click to expand...
Click to collapse
hey i can dig it. i dont mind having to charge more often seeing as i have two batteries.

ianandamy said:
yes I noticed this too with the latest cyan release my signal is crap all the time, now.
Click to expand...
Click to collapse
edit your build.prop
current values:
ro.ril.gprsclass=10
ro.ril.hsxpa=1
new values:
ro.ril.gprsclass=12
ro.ril.hsxpa=2
push back to phone in system directory, reboot
made a huge difference to me - I think I found that info on the cyanogen forums
In fact, my nexus now has better reception than my N96, same mobile provider, same location. And i'm using pershoot kernal currently, latest testing cyanogen

Related

[Q] acpuclock-7x30.c modification wont boot.

hello so recently i decided to compile a custom over-clocked kernel for the mecha the first modification was to change some of the cpu frequency's but after doing so and compiling when i try to boot with the kernel installed my phone just seems to lock up and never boot. the code seems good to me but i figure ill let you all have a look.
Code:
static struct cpufreq_frequency_table freq_table[] = {
{ 0, 250000 },
{ 1, 350000 },
{ 2, 450000 },
{ 3, 550000 },
{ 4, 650000 },
{ 5, 750000 },
{ 6, 850000 },
{ 7, 950000 },
{ 8, 1050000 },
{ 9, 1150000 },
{ 10, 1250000 },
{ 11, 1350000 },
{ 12, 1450000 },
{ 13, 1550000 },
{ 14, 1650000 },
{ 15, 1750000 },
{ 16, 1850000 },
{ 17, 1950000 },
{ 16, CPUFREQ_TABLE_END },
};
/* Use negative numbers for sources that can't be enabled/disabled */
#define SRC_LPXO (-2)
#define SRC_AXI (-1)
static struct clkctl_acpu_speed acpu_freq_tbl[] = {
{ 24576, SRC_LPXO, 0, 0, 30720, 900, VDD_RAW(900) },
{ 61440, PLL_3, 5, 11, 61440, 900, VDD_RAW(900) },
{ 122880, PLL_3, 5, 5, 61440, 900, VDD_RAW(900) },
{ 184320, PLL_3, 5, 4, 61440, 900, VDD_RAW(900) },
{ MAX_AXI_KHZ, SRC_AXI, 1, 0, 61440, 900, VDD_RAW(900) },
{ 250000, PLL_3, 5, 2, 122500, 900, VDD_RAW(900) },
{ 350000, PLL_3, 5, 1, 192000, 950, VDD_RAW(950) },
{ 450000, PLL_1, 2, 0, 192000, 950, VDD_RAW(950) },
{ 550000, PLL_3, 5, 1, 192000, 975, VDD_RAW(975) },
{ 650000, PLL_2, 3, 0, 192000, 1000, VDD_RAW(1000) },
{ 750000, PLL_2, 3, 0, 192000, 1025, VDD_RAW(1025) },
{ 850000, PLL_2, 3, 0, 192000, 1050, VDD_RAW(1050) },
{ 950000, PLL_2, 3, 0, 192000, 1050, VDD_RAW(1050) },
{ 1050000, PLL_2, 3, 0, 192000, 1100, VDD_RAW(1100) },
{ 1150000, PLL_2, 3, 0, 192000, 1150, VDD_RAW(1150) },
{ 1250000, PLL_2, 3, 0, 192000, 1175, VDD_RAW(1175) },
{ 1350000, PLL_2, 3, 0, 192000, 1225, VDD_RAW(1225) },
{ 1450000, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1300) },
{ 1550000, PLL_2, 3, 0, 192000, 1400, VDD_RAW(1400) },
{ 1650000, PLL_2, 3, 0, 192000, 1400, VDD_RAW(1400) },
{ 1750000, PLL_2, 3, 0, 192000, 1450, VDD_RAW(1450) },
{ 1850000, PLL_2, 3, 0, 192000, 1450, VDD_RAW(1450) },
{ 1950000, PLL_2, 3, 0, 192000, 1450, VDD_RAW(1450) },
{ 0 }
};
before I modified this area the kernel booted fine.
the rest of the code is a clone of adrynalyne's master source.
Adryn's new kernel supports changing that information on the fly. Also, why would you want so many frequencies? That would actually make it less effiecent.
I wanted to test certain speeds/voltages on my phone still why won't it boot up the voltages and clock speeds as so.
Sent from my ADR6400L using XDA App

[KERNEL][2011-11-23]kAmMa's Lightweight Kernel for EVO3D GSM v1.0

Use at your own risk
I take no responsibility for any demage, which this kernel can cause
Key kernel features
- OC MAX to 1.836GHz
- UV default freqs
- VDD via sysfs (fraux123) - UV compatible with System Tuner
- DEADLINE as default IO sched
- BFQ, VR IO Schedulers
- SLQB allocator
- Lagfree governor
- 2-Way Call Recorder support
- lower WiFi voltage
- Bluetooth HID
- TUN module
- CIFS module
- button backlight set to 2 as default
[size=+1]Donations - Thanks to all[/size]
Code:
redeyes717 - $30
fendy.riyanto - $5
iamdarren - $10
Code:
v1.0
----
- button backlight set to 2 as default (less battery consumption)
- L2CAP removed (not working)
Download here: [url]http://www.multiupload.com/X349UFSSFJ[/url]
v0.9
----
- new freq. table (listing bellow)
- L2CAP enabled (PS3 sixaxis controller)
- SMARTASS2 governor removed
- DEADLINE IO Scheduler as default
Download here: [url]http://www.multiupload.com/A2CPN8ECTB[/url]
v0.8
----
- new freq. table
- code cleanup
Download here: [url]http://www.multiupload.com/ID5NIY8URV[/url]
v0.7
----
- Lagfree & SmartassV2 governors
- some tweaks
Download here: [url]http://www.multiupload.com/MWOK4ILD5T[/url]
v0.6
----
- UV default freqs (to 1.18GHz)
- VR as default IO sched
- 2-Way Call Recording support
- Bluetooth HID enabled
Download here: [url]http://www.multiupload.com/2AKMG2SS3W[/url]
v0.5
----
- VDD via sysfs (fraux123) - UV compatible with System Tuner
- lower WiFi voltage
Download here: [url]http://www.multiupload.com/MNQ4WNHLOJ[/url]
v0.4
----
- added SLQB allocator
Download here: [url]http://www.multiupload.com/IMNDM92Z31[/url]
v0.3
----
- added BFQ IO scheduler and set as default
Download here: [url]http://www.multiupload.com/EHC5BMKXN1[/url]
v0.2
----
- NOOP as default IO sched
- TUN module
- CIFS module
- flashable via CWM package (Clockworkmod Recovery)
v0.1
----
- test release
- overclockability to 1.836GHz
How to install
1. copy downloaded ZIP file to phone://sdcard
2. reboot phone into recovery mode
3. select "install zip from sdcard"
4. select "choose zip from sdcard"
5. browse for downloaded file
6. wait for installation
7. go back to main menu in recovery
8. select "reboot system now"
9. profit and [size=+2]CONSIDER DONATION[/size] : https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
If you experience any issue (reboot, freeze...) you can try to wipe your Cache partition and Dalvik-cache with this CWM package : http://www.multiupload.com/HTLG2S2UOU
Code:
Freq. table
-----------
{ {0, 0}, MAX_AXI, ACPU_AFAB, 1, 0, 0, 0, L2(0), 837500, 0x03006000},
{ {1, 1}, 384000, ACPU_PLL_8, 3, 0, 0, 0, L2(1), 837500, 0x03006000},
{ {1, 1}, 432000, ACPU_SCPLL, 0, 0, 1, 0x08, L2(1), 850000, 0x03006000},
{ {1, 1}, 486000, ACPU_SCPLL, 0, 0, 1, 0x09, L2(2), 875000, 0x03006000},
{ {1, 1}, 540000, ACPU_SCPLL, 0, 0, 1, 0x0A, L2(3), 887500, 0x03006000},
{ {1, 1}, 594000, ACPU_SCPLL, 0, 0, 1, 0x0B, L2(4), 900000, 0x03006000},
{ {1, 1}, 648000, ACPU_SCPLL, 0, 0, 1, 0x0C, L2(5), 912500, 0x03006000},
{ {1, 1}, 702000, ACPU_SCPLL, 0, 0, 1, 0x0D, L2(6), 937500, 0x03006000},
{ {1, 1}, 756000, ACPU_SCPLL, 0, 0, 1, 0x0E, L2(7), 962500, 0x03006000},
{ {1, 1}, 810000, ACPU_SCPLL, 0, 0, 1, 0x0F, L2(8), 975000, 0x03006000},
{ {1, 1}, 864000, ACPU_SCPLL, 0, 0, 1, 0x10, L2(9), 1000000, 0x03006000},
{ {1, 1}, 918000, ACPU_SCPLL, 0, 0, 1, 0x11, L2(10), 1025000, 0x03006000},
{ {1, 1}, 972000, ACPU_SCPLL, 0, 0, 1, 0x12, L2(11), 1050000, 0x03006000},
{ {1, 1}, 1026000, ACPU_SCPLL, 0, 0, 1, 0x13, L2(12), 1087500, 0x03006000},
{ {1, 1}, 1080000, ACPU_SCPLL, 0, 0, 1, 0x14, L2(13), 1100000, 0x03006000},
{ {1, 1}, 1134000, ACPU_SCPLL, 0, 0, 1, 0x15, L2(14), 1125000, 0x03006000},
{ {1, 1}, 1188000, ACPU_SCPLL, 0, 0, 1, 0x16, L2(15), 1150000, 0x03006000},///
{ {1, 1}, 1242000, ACPU_SCPLL, 0, 0, 1, 0x17, L2(16), 1175000, 0x03006000},
{ {1, 1}, 1296000, ACPU_SCPLL, 0, 0, 1, 0x18, L2(17), 1200000, 0x03006000},
{ {1, 1}, 1350000, ACPU_SCPLL, 0, 0, 1, 0x19, L2(18), 1225000, 0x03006000},
{ {1, 1}, 1404000, ACPU_SCPLL, 0, 0, 1, 0x1A, L2(19), 1250000, 0x03006000},
{ {1, 1}, 1458000, ACPU_SCPLL, 0, 0, 1, 0x1B, L2(20), 1250000, 0x03006000},
{ {1, 1}, 1512000, ACPU_SCPLL, 0, 0, 1, 0x1C, L2(21), 1250000, 0x03006000},
{ {1, 1}, 1566000, ACPU_SCPLL, 0, 0, 1, 0x1D, L2(22), 1275000, 0x03006000},
{ {1, 1}, 1620000, ACPU_SCPLL, 0, 0, 1, 0x1E, L2(23), 1300000, 0x03006000},
{ {1, 1}, 1674000, ACPU_SCPLL, 0, 0, 1, 0x1F, L2(24), 1325000, 0x03006000},
{ {1, 1}, 1728000, ACPU_SCPLL, 0, 0, 1, 0x20, L2(25), 1350000, 0x03006000},
{ {1, 1}, 1782000, ACPU_SCPLL, 0, 0, 1, 0x21, L2(26), 1375000, 0x03006000},
{ {1, 1}, 1836000, ACPU_SCPLL, 0, 0, 1, 0x22, L2(27), 1400000, 0x03006000},
Kernel source : https://gitorious.org/htc-shooter-kernel
Nice~
supporting all dev !
But my phone was still locked
downloadit and installit
AND WORKS
So, finally, the first working GSM custom kernel?
congrats to kamma for the first ever gsm kernel for our phones!
Sent from my GT-I9100 using XDA Premium App
kamma said:
Use at your own risk
I take no responsibility for any demage, which this kernel can cause
Key kernel features
- OC MAX to 1.836GHz
- you need SetCPU application to change OC settings
Code:
Changelog v0.1
- test release
- overclockability to 1.836GHz
How to install
1. unpack downloaded ZIP file (for example to d:/temp)
2. connect device with computer with Android SDK tools (adb, fastboot)
3. reboot to bootloader
4. flash new kernel
5. restart device
6. push new wifi module
This kernel is based on klquicksall's RCMIX kernel
[size=+2]PLEASE CONSIDER DONATION[/size] : https://www.paypal.com/cz/cgi-bin/w...63663d3faee8db2b24f7b84f1819390b7e2d9283d70f1
Click to expand...
Click to collapse
Can the zip be flashed from clockwork recovery
Sent from my HTC EVO 3D X515m using XDA App
not understand how to install it..
-Ho- said:
Nice~
supporting all dev !
But my phone was still locked
Click to expand...
Click to collapse
You can't flash a Kernel this way unless you have S-OFF
thre3aces said:
Can the zip be flashed from clockwork recovery
Sent from my HTC EVO 3D X515m using XDA App
Click to expand...
Click to collapse
no it cant...
i will prepare CWM image tomorrow, probably...
thre3aces said:
Can the zip be flashed from clockwork recovery
Sent from my HTC EVO 3D X515m using XDA App
Click to expand...
Click to collapse
No. You need S-OFF and flash it via ADB in a terminal/command prompt
---------- Post added at 01:52 PM ---------- Previous post was at 01:45 PM ----------
kamma said:
Use at your own risk
I take no responsibility for any demage, which this kernel can cause
Key kernel features
- OC MAX to 1.836GHz
- you need SetCPU application to change OC settings
Code:
Changelog v0.1
- test release
- overclockability to 1.836GHz
How to install
1. unpack downloaded ZIP file (for example to d:/temp)
2. connect device with computer with Android SDK tools (adb, fastboot)
3. reboot to bootloader
4. flash new kernel
5. restart device
6. push new wifi module
This kernel is based on klquicksall's RCMIX kernel
[size=+2]PLEASE CONSIDER DONATION[/size] : https://www.paypal.com/cz/cgi-bin/w...63663d3faee8db2b24f7b84f1819390b7e2d9283d70f1
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
too bad that I have bootloader 0012
I can't achieve s-off with HTC's unlock method
which means I wont have chance to try this nice thing out?
kamma said:
no it cant...
i will prepare CWM image tomorrow, probably...
Click to expand...
Click to collapse
Thanks. I'll be waiting for that since I have s-off
Sent from my HTC EVO 3D X515m using XDA App
cant install
I stuck @ fastboot flash zimage D:\ ...
sending 'zimage' (3193) ....
OKEY [0,797s]
writing 'zimage' ...
FAILED (remote:unknown fail)
finished. total time blablabla
i have s-off rooted device (my Bootloader says s-off)
TommyX235 said:
I stuck @ fastboot flash zimage D:\ ...
sending 'zimage' (3193) ....
OKEY [0,797s]
writing 'zimage' ...
FAILED (remote:unknown fail)
finished. total time blablabla
i have s-off rooted device (my Bootloader says s-off)
Click to expand...
Click to collapse
You sure? That's the error (remote:unknown fail) you get when you don't have S-OFF. Have you got the USB drivers installed? Did you run as administrator?
Okey
my Bootmenu looks like:
-Revolutionary--
Shooter_U PVT SHIP S_OFF RL
HBOOT-1.49.1107
RADIO-10.13.9020.08_2M
eMMC-boot
Jul 12 2011 ---
Fastboot USB
..
..
..
i tryd fastboot reboot-bootloader .. and the device rebooted
to the OP: thanks! first custom kernel for our device.
by the way: I'm trying to make my donation but this link doesn't work for me
https://www.paypal.com/cz/cgi-bin/webscr?cmd=_flow&SESSION=my4Re7f1YA_jrHVvPAoQUk3FgXX3-F1WjMcYmxpw45V-XixVGJnWKOo3kIK&dispatch=5885d80a13c0db1f8e263663d3faee8db2b24f7b84f1819390b7e2d9283d70f1
signature verify fail
My HBOOT is 1.49.0012, and I use hTC Unlock, and use Crypt0's RUU V.1.3 ROM, but I got this........
sending 'zimage' (3193 KB)...
OKAY [ 0.724s]
writing 'zimage'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.146s
signature verify fail how to fix it?
kamma said:
Use at your own risk
I take no responsibility for any demage, which this kernel can cause
Key kernel features
- OC MAX to 1.836GHz
- you need SetCPU application to change OC settings
Code:
Changelog v0.1
- test release
- overclockability to 1.836GHz
How to install
1. unpack downloaded ZIP file (for example to d:/temp)
2. connect device with computer with Android SDK tools (adb, fastboot)
3. reboot to bootloader
4. flash new kernel
5. restart device
6. push new wifi module
This kernel is based on klquicksall's RCMIX kernel
[size=+2]PLEASE CONSIDER DONATION[/size] : https://www.paypal.com/cz/cgi-bin/w...63663d3faee8db2b24f7b84f1819390b7e2d9283d70f1
Click to expand...
Click to collapse
Does this Kernel have the Virtuous OC Daemon? So it should allow us to UV, etc?
antutu bench
very good result for the fisrt gsm custom kernel
thanks you sir
redeyes717 said:
to the OP: thanks! first custom kernel for our device.
by the way: I'm trying to make my donation but this link doesn't work for me
Click to expand...
Click to collapse
link changed...
thx for donation...

GXkernel1.0.3.5

Update 12-19-11
Compatibility fix in CPU table, for non booting devices
1.0.3.5
Flashable zip:http://db.tt/QwfI7iaH
For Developers:http://db.tt/qAuFGoSg
Featuring:
2.6.35.14
GXkernels will be considered experimental, and should be viewed as a work in progress
For use with Gingerbread roms for Dell Streak
1.0.3.1
For flashable zip:http://db.tt/E098hb8X
For Developers:http://db.tt/YenTO0s4
Larger cpu table 245 - 1286.8
Safe recommended settings are 245 - 1045
Potential wifi fix for some users, special thanks DSC-Team
CIFS is included, ipv6 is removed, scsi support in kernel removed.
more voltage work on the table, for those of you interested in GXkernel table
GXkernel flexes through these frequencies-
here it is!
Code:
struct clkctl_acpu_speed acpu_freq_tbl_998[] = {
{ 0, 19200, ACPU_PLL_TCXO, 0, 0, 0, 0, 14000, 0, 0, 1000},
{ 0, 128000, ACPU_PLL_1, 1, 5, 0, 0, 14000, 2, 0, 1000},
{ 1, 245760, ACPU_PLL_0, 4, 0, 0, 0, 29000, 0, 0, 950},
/* Update AXI_S and PLL0_S macros if above row numbers change. */
{ 1, 384000, ACPU_PLL_3, 0, 0, 0, 0, 58000, 1, 0xA, 1000},
{ 1, 422400, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xB, 1075},
{ 1, 460800, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xC, 1100},
{ 1, 499200, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xD, 1125},
{ 1, 537600, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xE, 1150},
{ 1, 576000, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xF, 1175},
{ 1, 614400, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x10, 1200},
{ 1, 652800, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x11, 1225},
{ 1, 691200, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x12, 1250},
{ 1, 729600, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x13, 1275},
{ 1, 768000, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x14, 1300},
{ 1, 806400, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x15, 1325},
{ 1, 844800, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x16, 1350},
{ 1, 883200, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x17, 1375},
{ 1, 921600, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x18, 1375},
{ 1, 960000, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x19, 1400},
{ 1, 998400, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x1A, 1400},
{ 1, 1036800, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x1B, 1400},
{ 1, 1075200, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x1C, 1400},
{ 1, 1113600, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x1D, 1425},
{ 1, 1152000, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x1E, 1425},
{ 1, 1190400, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x1F, 1425},
{ 1, 1228800, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x20, 1450},
{ 1, 1262800, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x21, 1500},
{ 1, 1286800, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x21, 1550},
{ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0},
};
1.0
Based on the Dell source 4.05
a modified CPU table which scales through 18 frequencies;
245 to 1152
Voltage is tweaked higher, on higher frequencies, up to 1450
All 18 frequencies select-able
Download links---
For recovery, the flashable zip: http://db.tt/vGRN98hq
For devs: http://db.tt/PR8xaBTJ
Best wishes, and thanks to all Developers and to you the user!
-Greg
Using this kernal on dsc rom. So far so good.
Sent from the SuperStreak! ;-)
borijess said:
Using this kernal on dsc rom. So far so good.
Sent from the SuperStreak! ;-)
Click to expand...
Click to collapse
+1 trying it on DSC 62b. Seems rock solid so far
Another great kernel. Awesome work, thanks Greg!
greg9100 said:
Featuring:
2.6.35.14
GXkernels will be considered experimental, and should be viewed as a work in progress
For use with Gingerbread roms for Dell Streak
Based on the Dell source 4.05
a modified CPU table which scales through 18 frequencies;
245 to 1152
Voltage is tweaked higher, on higher frequencies, up to 1450
All 18 frequencies select-able
Download links---
For recovery, the flashable zip: http://db.tt/vGRN98hq
For devs: http://db.tt/PR8xaBTJ
Best wishes, and thanks to all Developers and to you the user!
-Greg
Click to expand...
Click to collapse
Great work, nice to finally see the overclockable Gkernel, will you be extending the frequency range past 1152mhz?
Does this kernel contain all the tweaks and features from the original gkernel?
Dsc 0.62b rom + GXkernel 1.0 + Overclock.
Good. Nice. Wonderful. Perfect. Great!!
Thank you so much Greg T_T.
My streak is very smooth. Thank you.
sharptv said:
Does this kernel contain all the tweaks and features from the original gkernel?
Click to expand...
Click to collapse
Yes, all tweaks from Gkernels project reside inside GXkernels
(InsertNameHere) said:
Great work, nice to finally see the overclockable Gkernel, will you be extending the frequency range past 1152mhz?
Click to expand...
Click to collapse
I am going to try it!
installed over 0.62b noting same set of max-min frequencies selectable in cpu master pro
add contact not working
dsnreddy said:
add contact not working
Click to expand...
Click to collapse
working for me, whant language r u using?
GXkernel1.0
Working great for me, no issues.
nice kernel, work awesome in mine
questions :
whats the difference between gxkrnel vs gkernel vs sd kernel?
thanks greg, u & your kernel is rock!
All of the changes to Gkernel are included into GXkernel; you can see the list of changes at Gkernels 1st post in the forums,
The main difference from SD kernel is that it is the dell 4.05 source, patched up to 2.6.35.14, including the changes to the .config,
I believe SD kernel to have been made mostly from the Olleh sources(I may be wrong) or possibly from amalgamated sources, probably including a host of tweaks by DJ Steve and or Fards;
The progenitor config was pulled from SD kernel as a base with which to work on, for which I give thanks to DJ Steve, and also for his tip regarding wifi practices-
GXkernel is basically Gkernels project with overclocking-
It has a modified CPU table
I am also still collaborating with DSC-Team on other DSC kernels, you can follow our work on that thread;
-G
Better system responsiveness and at this moment I don't see any problems. Realy like it! Good work!
Can't stand without trying ~~
Hello, I‘ve tried with GS 2.4.4 as HD games use to be too slow and when start a game or a few minutes after got stuck and have to remove battery.
Any explanation? Thank you
greg9100 said:
All of the changes to Gkernel are included into GXkernel; you can see the list of changes at Gkernels 1st post in the forums,
The main difference from SD kernel is that it is the dell 4.05 source, patched up to 2.6.35.14, including the changes to the .config,
I believe SD kernel to have been made mostly from the Olleh sources(I may be wrong) or possibly from amalgamated sources, probably including a host of tweaks by DJ Steve and or Fards;
The progenitor config was pulled from SD kernel as a base with which to work on, for which I give thanks to DJ Steve, and also for his tip regarding wifi practices-
GXkernel is basically Gkernels project with overclocking-
It has a modified CPU table
I am also still collaborating with DSC-Team on other DSC kernels, you can follow our work on that thread;
-G
Click to expand...
Click to collapse
thanks greg, will always excited to use your next project
great job
Does GXKernel have the VPN, CIFS modules ready ?
Also, I'd like to ask, has anyone tried GTA3 on Streak ? (with or without GXKernel)
which version should I try ?

[aospa 4.4.2 kvt49l] paranoidandroid 4.3+ GEEB [05/20]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AOSPA 4.3+ PARANOIDANDROID
Kitkat 4.4.2 KVT49L android-4.4.2_r2.1
Download ROMS from DOWNLOAD HERE
1. DOWNLOAD YOUR ROM
2. DOWNLOAD THE LATEST PA GAPPS PACKAGE - always check/use up to date Gapps unless otherwise noted
http://goo.gl/mYKmfL - RECOMMEND mini modular PA Gapps
or BANKS - if having issues with PA Gapps
Wipe Fresh Clean Install (you all know the procedure)
3. COMPLETE CLEAN WIPE - *includes system*
4. FLASH ROM & GAPPS
5. WIPE CACHE & DALVIK
5. RUN INITIAL SETUP & REBOOT
Let boot take as much time as needed. This will help avoid boot issues.
GIT
GERRIT
FAQ + HELP
BUG TRACKER
COMMUNITY + CHANGELOGS​
Disclaimer / Warning!: I'm not responsible for any reason should you bork your phone
Donations
If you want to donate, feel free to do so otherwise don't forget to hit thanks and show your appreciation for all the hard work that goes into this.
My Github Sources
Please stick to development here!!! Take all questions to Q&A thread - thanks Pony Express!!!
RULES
You must read the OP & Installation Instructions before installing this ROM or posting in this thread
If you don't like how I run this thread. Leave. You do not have to be here and you are not forced to read it. You are doing so on your own free will.
Search before posting here. You are most likely not the only one to have the question/issue.
Have fun in this thread. I don't mind if we have some fun, joke around, or whatever. As long as it's fun.
If you're going to post here, keep it to this ROM and this ROM only (unless its fun as mentioned above). It is useless to compare to Stock ROMs, CM10 ROMS, ect...
Please watch the 2 videos provided below before posting in this thread. thanks
Thank g33k3r for TOT file or whoever else involved in getting it.. You can go to HIS THREAD HERE to get the official lg image..
This is an paste from Harsh from his thread here
Well, our cpu are made at some quality standards. We have 4 different quality of cpu for apq8064 from Qualcomm. so depending on which one is on your phone it selects frequency table from slow, nominal, fast and faster.
Google kernel source have same frequency table for fast and faster. So those with faster are not getting their extra advantage
You can identify you CPU chip by below command in terminal.
adb shell dmesg | grep PVS
It will give you some output as given example below
Click to expand...
Click to collapse
Code:
adb shell dmesg | grep PVS
[ 0.873920] acpuclk-8064 acpuclk-8064: ACPU PVS: FAST
And faster binned CPU has lot to do with UV, when you look as frequency table of faster, it is already preconfigured to have lower voltages than fast, and lot lower than slow binned.
Phones with faster binned should have better battery than slower binned phone out of box without any other configuration.
And for UV its already hardcoded and can be adjusted by System Tuner app further. And OC I am not willing to add. ( I don't think there's any gain in running our phones hotter with higher voltages by OC'ing)
Click to expand...
Click to collapse
default voltages for SLOW:
{ 1, { 384000, PLL_8, 0, 2, 0x00 }, L2(0), 950000 },
{ 0, { 432000, HFPLL, 2, 0, 0x20 }, L2(6), 975000 },
{ 1, { 486000, HFPLL, 2, 0, 0x24 }, L2(6), 975000 },
{ 0, { 540000, HFPLL, 2, 0, 0x28 }, L2(6), 1000000 },
{ 1, { 594000, HFPLL, 1, 0, 0x16 }, L2(6), 1000000 },
{ 0, { 648000, HFPLL, 1, 0, 0x18 }, L2(6), 1025000 },
{ 1, { 702000, HFPLL, 1, 0, 0x1A }, L2(6), 1025000 },
{ 0, { 756000, HFPLL, 1, 0, 0x1C }, L2(6), 1075000 },
{ 1, { 810000, HFPLL, 1, 0, 0x1E }, L2(6), 1075000 },
{ 0, { 864000, HFPLL, 1, 0, 0x20 }, L2(6), 1100000 },
{ 1, { 918000, HFPLL, 1, 0, 0x22 }, L2(6), 1100000 },
{ 0, { 972000, HFPLL, 1, 0, 0x24 }, L2(6), 1125000 },
{ 1, { 1026000, HFPLL, 1, 0, 0x26 }, L2(6), 1125000 },
{ 0, { 1080000, HFPLL, 1, 0, 0x28 }, L2(15), 1175000 },
{ 1, { 1134000, HFPLL, 1, 0, 0x2A }, L2(15), 1175000 },
{ 0, { 1188000, HFPLL, 1, 0, 0x2C }, L2(15), 1200000 },
{ 1, { 1242000, HFPLL, 1, 0, 0x2E }, L2(15), 1200000 },
{ 0, { 1296000, HFPLL, 1, 0, 0x30 }, L2(15), 1225000 },
{ 1, { 1350000, HFPLL, 1, 0, 0x32 }, L2(15), 1225000 },
{ 0, { 1404000, HFPLL, 1, 0, 0x34 }, L2(15), 1237500 },
{ 1, { 1458000, HFPLL, 1, 0, 0x36 }, L2(15), 1237500 },
{ 1, { 1512000, HFPLL, 1, 0, 0x38 }, L2(15), 1250000 },
default voltages for NORM:
{ 1, { 384000, PLL_8, 0, 2, 0x00 }, L2(0), 900000 },
{ 0, { 432000, HFPLL, 2, 0, 0x20 }, L2(6), 925000 },
{ 1, { 486000, HFPLL, 2, 0, 0x24 }, L2(6), 925000 },
{ 0, { 540000, HFPLL, 2, 0, 0x28 }, L2(6), 950000 },
{ 1, { 594000, HFPLL, 1, 0, 0x16 }, L2(6), 950000 },
{ 0, { 648000, HFPLL, 1, 0, 0x18 }, L2(6), 975000 },
{ 1, { 702000, HFPLL, 1, 0, 0x1A }, L2(6), 975000 },
{ 0, { 756000, HFPLL, 1, 0, 0x1C }, L2(6), 1025000 },
{ 1, { 810000, HFPLL, 1, 0, 0x1E }, L2(6), 1025000 },
{ 0, { 864000, HFPLL, 1, 0, 0x20 }, L2(6), 1050000 },
{ 1, { 918000, HFPLL, 1, 0, 0x22 }, L2(6), 1050000 },
{ 0, { 972000, HFPLL, 1, 0, 0x24 }, L2(6), 1075000 },
{ 1, { 1026000, HFPLL, 1, 0, 0x26 }, L2(6), 1075000 },
{ 0, { 1080000, HFPLL, 1, 0, 0x28 }, L2(15), 1125000 },
{ 1, { 1134000, HFPLL, 1, 0, 0x2A }, L2(15), 1125000 },
{ 0, { 1188000, HFPLL, 1, 0, 0x2C }, L2(15), 1150000 },
{ 1, { 1242000, HFPLL, 1, 0, 0x2E }, L2(15), 1150000 },
{ 0, { 1296000, HFPLL, 1, 0, 0x30 }, L2(15), 1175000 },
{ 1, { 1350000, HFPLL, 1, 0, 0x32 }, L2(15), 1175000 },
{ 0, { 1404000, HFPLL, 1, 0, 0x34 }, L2(15), 1187500 },
{ 1, { 1458000, HFPLL, 1, 0, 0x36 }, L2(15), 1187500 },
{ 1, { 1512000, HFPLL, 1, 0, 0x38 }, L2(15), 1200000 },
default voltages for FAST & FASTER:
{ 1, { 384000, PLL_8, 0, 2, 0x00 }, L2(0), 850000 },
{ 0, { 432000, HFPLL, 2, 0, 0x20 }, L2(6), 875000 },
{ 1, { 486000, HFPLL, 2, 0, 0x24 }, L2(6), 875000 },
{ 0, { 540000, HFPLL, 2, 0, 0x28 }, L2(6), 900000 },
{ 1, { 594000, HFPLL, 1, 0, 0x16 }, L2(6), 900000 },
{ 0, { 648000, HFPLL, 1, 0, 0x18 }, L2(6), 925000 },
{ 1, { 702000, HFPLL, 1, 0, 0x1A }, L2(6), 925000 },
{ 0, { 756000, HFPLL, 1, 0, 0x1C }, L2(6), 975000 },
{ 1, { 810000, HFPLL, 1, 0, 0x1E }, L2(6), 975000 },
{ 0, { 864000, HFPLL, 1, 0, 0x20 }, L2(6), 1000000 },
{ 1, { 918000, HFPLL, 1, 0, 0x22 }, L2(6), 1000000 },
{ 0, { 972000, HFPLL, 1, 0, 0x24 }, L2(6), 1025000 },
{ 1, { 1026000, HFPLL, 1, 0, 0x26 }, L2(6), 1025000 },
{ 0, { 1080000, HFPLL, 1, 0, 0x28 }, L2(15), 1075000 },
{ 1, { 1134000, HFPLL, 1, 0, 0x2A }, L2(15), 1075000 },
{ 0, { 1188000, HFPLL, 1, 0, 0x2C }, L2(15), 1100000 },
{ 1, { 1242000, HFPLL, 1, 0, 0x2E }, L2(15), 1100000 },
{ 0, { 1296000, HFPLL, 1, 0, 0x30 }, L2(15), 1125000 },
{ 1, { 1350000, HFPLL, 1, 0, 0x32 }, L2(15), 1125000 },
{ 0, { 1404000, HFPLL, 1, 0, 0x34 }, L2(15), 1137500 },
{ 1, { 1458000, HFPLL, 1, 0, 0x36 }, L2(15), 1137500 },
{ 1, { 1512000, HFPLL, 1, 0, 0x38 }, L2(15), 1150000 },
So glad to see this here, houstonn! Excellent job my friend.
:good: :highfive:
Sent from my Optimus G using xda app-developers app
Agreed. I'm still rocking the 3/29 build haha
Pie Control works fine for me. It only gave me issues when I flashed the build from 4/2
____
Sent from my LG Original Gangsta
And here we go! Comm. take off time!:crying:I'm so happy!!!
Wow for a moment I was confused whether I was looking at N4 forums...
Great work Devs! You guys are awesome!
Sent from my LG-E970 using xda premium
This is awesome, I'm loving it. Thanks to all the devs involved, great work.
Sent from my Optimus G using xda app-developers app
Curious as to why it will not let me lower min frequency. I lower it but it always puts it right back at 1026....killing my battery.
Sent from my Optimus G using xda app-developers app
Look at cpu spy, I think you will find it actually is going below and just not reporting correctly.
Edit: I just looked at cpu spy and you are in fact correct. Holding steady at 1026+...getting great deep sleep though!
Sent from my Optimus G using xda app-developers app
Jank4AU said:
Look at cpu spy, I think you will find it actually is going below and just not reporting correctly.
Edit: I just looked at cpu spy and you are in fact correct. Holding steady at 1026+...getting great deep sleep though!
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Deep sleep is good here as well. Seems like it would be amazing if it would allow itself to clock down. Nothing I do will get my settings to persist. Neither in built in performance control or when I tried setcpu.
Sent from my Optimus G using xda app-developers app
pfoxdizzle said:
Deep sleep is good here as well. Seems like it would be amazing if it would allow itself to clock down. Nothing I do will get my settings to persist. Neither in built in performance control or when I tried setcpu.
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Blame Google. Its called touch boost
Sent from my Nexus 7 using xda app-developers app
Never heard of this and found nothing on the internet. Would appreciate a pm if you get the chance.
Sent from my Optimus G using xda app-developers app
pfoxdizzle said:
Never heard of this and found nothing on the internet. Would appreciate a pm if you get the chance.
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Chad explained it to me. Its built in to boost up the CPU upon touches to prevent lag. Found it in some n4 threads too
Sent from my Nexus 7 using xda app-developers app
It states that this comes with a modded
Faux kernel. Use fauxclock to disable mpdecision and you'll be able to go below 1GHz. Hopefully the intellidemand governor is present or all 4 cores might be forced online by this.
Sent from my LG-E970 using xda premium
pfoxdizzle said:
Deep sleep is good here as well. Seems like it would be amazing if it would allow itself to clock down. Nothing I do will get my settings to persist. Neither in built in performance control or when I tried setcpu.
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
What governor are you using? After experimenting with it a little, it appears that Conservative is locked to a low of 1026, but the others like Wheatley and OnDemand behave normally...
Jank4AU said:
What governor are you using? After experimenting with it a little, it appears that Conservative is locked to a low of 1026, but the others like Wheatley and OnDemand behave normally...
Click to expand...
Click to collapse
I tried all the governors. Was also sent to the glorious demigod screen after a reboot so reverting back to my CM backup for now.
Sent from my Nexus 4 using xda app-developers app
Hmm idk about this build, but I'm on the 3/29 build and I'm running the interactive governor clocked to a max of 1512 and min of 288
Deep sleep over night was around 7 hours and 35 minutes out of 7 hours and 38 minutes or something.
blenkows said:
Hmm idk about this build, but I'm on the 3/29 build and I'm running the interactive governor clocked to a max of 1512 and min of 288
Deep sleep over night was around 7 hours and 35 minutes out of 7 hours and 38 minutes or something.
Click to expand...
Click to collapse
It goes down to 288. Just a display bug in apps. The phone scales down.
Sent from my Nexus 4 using xda app-developers app
nygfan760 said:
It goes down to 288. Just a display bug in apps. The phone scales down.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Edit: I shouldn't be posting here yet. I'm still on the 0404 build and running the 0408 kernel so I don't know if everything is the same kernel-wise. So excuse me while I bow out for a bit until I'm up to date.
Sent from my Optimus G using xda app-developers app

[C#]ROund FoRM

Hey guys, I recently found this. Add this to your Form this code will turn your form into a rounded one.
For more things, just comprehend the code and edit whatever you need :good:
Code:
protected override void OnPaint(PaintEventArgs e)
{
//base.OnPaint (e);
GraphicsPath p = new GraphicsPath();
p.StartFigure();
p.AddArc(new Rectangle(0, 0, 40, 40), 180, 90);
p.AddLine(40, 0, this.Width - 40, 0);
p.AddArc(new Rectangle(this.Width - 40, 0, 40, 40), -90, 90);
p.AddLine(this.Width, 40, this.Width, this.Height - 40);
p.AddArc(new Rectangle(this.Width - 40, this.Height - 40, 40, 40), 0, 90);
p.AddLine(this.Width - 40, this.Height, 40, this.Height);
p.AddArc(new Rectangle(0, this.Height - 40, 40, 40), 90, 90);
p.CloseFigure();
this.Region = new Region(p);
SolidBrush oBlackBrush = new SolidBrush(System.Drawing.Color.Black);
System.Drawing.Pen borderPen = new System.Drawing.Pen(oBlackBrush, 4);
e.Graphics.DrawPath(borderPen, p);
borderPen.Dispose();
p.Dispose();
}
HAPPY cODing!!!

Categories

Resources