** Standard Disclaimer **
====================
I am not responsible for your actions. If by flashing/installing this file you somehow break your device, I am not liable. You do this, like many things on this forum, at your own risk.
====================
EVO View Kernel with 1.8Ghz Overclock
Thanks:
LeeDroid for the overclock source
snq- for the vdd sysfs interface
The kernel:
- Overclockable to 1.8Ghz -
** Use at your own risk **
- Edited voltage tables for at least a useable environment for most users -
** I tested the max overclock on my device and it did not reboot. However, not all devices are equal and I did not keep my device overclocked for an extended period of time. YMMV **
- Enabled deadline scheduler -
- Available governors: smartass, interactive, conservative, performance, ondemand with smartass set to default -
- Added snq-'s vdd_levels sysfs interface which allows the user to edit the cpu voltage levels -
See here for instructions on how to use the interface
-- This is a "base" kernel. Not much has been done/added to it due to my impending overseas relocation. Because of this, I will be without my linux box until February of next year. This means that there will be limited to no support or updates to this kernel in that time frame. --
Why release something if I can't support it? I saw the rising want for developers on the EVO View tablet. I may not have time to devote to developing for this device at the moment but I figured I can at least share what I have to give devs (or aspiring devs) something to start off of. This will at least give view owners something new to play with for the time being.
Download kernel | Source code | Stock kernel
express-oc.smartass.zip | evo_view_gb.release.zip | express-stock.kernel.zip
*** I have personally flashed both zips (oc kernel and stock kernel) successfully on my device and retained all data connections. However, I am using my twrp recovery port for the htc express. I can not speak for the results of cwm users. That being said, the zips are scripted with edify which I believe cwm supports. I will do my best to help with any issues. I just will not be able to compile any new builds until next February. ***
Thanks mate, don't own the View but this is good. Finally some devving for the view.
Also, if mods see this, they could go ahead with the possibility of making a whole new fora for the View instead of just a subsection.
ikingblack said:
Thanks mate, don't own the View but this is good. Finally some devving for the view.
Also, if mods see this, they could go ahead with the possibility of making a whole new fora for the View instead of just a subsection.
Click to expand...
Click to collapse
I agree, nice work.
Sent from my HTC Flyer.
Thanks! Going to give it a try...
nice work !!! might give this a go..
tried to flash through clockwork and it failed a few tries. Then it seemed to have borked my wifi anyone having any luck?
matthewallen72 said:
tried to flash through clockwork and it failed a few tries. Then it seemed to have borked my wifi anyone having any luck?
Click to expand...
Click to collapse
I personally flashed the zip on my device...although I use my twrp recovery port.
As for wifi, I confirmed that the modules (specifically the bcm4329.ko) were being written to my device successfully.
Could you please get me a log after the flash failed.
Also, I uploaded the stock kernel to the first post for people who want to revert.
I will give this a try tomorrow. Thanks for posting it. Been waiting for a kernel that could be oc'd for the view
nevermind (edited)
Not be rude or anything, but out of curiousity.... why are View Developments being posted in the Flyer Forums?
How is battery life? I tend to prefer more stamina the speed. It would be nice to get iPad battery life or better. I'm still waiting to receive my view so I can not play yet.
canthonyza said:
Not be rude or anything, but out of curiousity.... why are View Developments being posted in the Flyer Forums?
Click to expand...
Click to collapse
Because there is not a view forum and they are essentially the same product
Sent from my PG41200 using Tapatalk
thank you!!
i needed this.....
now besides the turkey a have something to cook....hahahhahaha
i wish to all of you
{
"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"
}
It flashed fine for me using cmw. I wiped the cache first. First boot took awhile but it came up. Got it working with setcpu. Thanks a lot for this kernel.
can this be flashed on the Flyer?????????????
JK, couldnt resist
gedster314 said:
How is battery life? I tend to prefer more stamina the speed. It would be nice to get iPad battery life or better. I'm still waiting to receive my view so I can not play yet.
Click to expand...
Click to collapse
You don't have to overclock it but the option is there. Also the vdd sysfs will allow you to edit the cpu voltages for even more power savings (undervolt). I suggest not changing the voltages for the oc freq's below what they are already set unless you intend on seeing how much you can undervolt.
Remember too that the voltage level affects performance as much as the cpu frequency.
On that note if any view users experiment with the voltage levels please feel free to pm me your voltage settings so I can put together an average voltage table. Thanks to all.
i am still getting an error flashing through cwm its says assert failed: write_raw_image("/tmp/newboot.img", "boot")
E: Error in /sdcard/ex[ress-oc.smartass.zip
thoughts anyone?
and yes I have tried wiping even wiping all
matthewallen72 said:
i am still getting an error flashing through cwm its says assert failed: write_raw_image("/tmp/newboot.img", "boot")
E: Error in /sdcard/ex[ress-oc.smartass.zip
thoughts anyone?
and yes I have tried wiping even wiping all
Click to expand...
Click to collapse
That's weird indeed. ElAguila flashed the kernel through cwm with no errors. Perhaps try redownloading the kernel zip again and check the md5. Also try the stock kernel and see if it throws the same error.
i did get the same error with the stock one as well. Ill mess around with it. now that i know someone got it to work, I am sure i will figure it out. thanks for the kernal and the work!!!!!
I hope it works for you matthew.
Related
{
"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"
}
by @Amethystxx (capsuledna.com)
For everyone who want nexus one roms with all feature of CyanogenMod and Gingerbread OTA look&Feel.
If you love this rom,Buy me a beer.
Features
- Based on CyanogenMod 7 Nightly Build
- Original Google's Gingerbread UI
- Original Nexus Boot Animation
- Original Gingerbread Launcher
- TrackBall Wake / Notification Sleep (No need to push power button)
- Even Faster With a New 1.15 GHz Wildmonks kernel (1600+ On Quadrant)(Optional)
- Long Lasting Battery Life
- Less Wonk
- Rock stable system
- Original Google's Gingerbread UI
Requirement
- Nexus one (Absolutely !!)
- ClockworkMod Recovery or RA-Passion Recovery
- Hboot-0.35
- Radio 5.12 (Threads)
Installation
1 Boot to Recovery
2 Wipe All
3 Toggled Signalture
4 Flash a rom
6 reboot
Thank to
- All CyanogenMod Dev Team for your great work
- Google for Android
- nicandris for his tutorial threads
- Mediafire
- XDA-Developer
Downloads
Roms
PureGoogleMod v0.8
Optional
1.15 GHz Kernel by wildmonks (Threads)
Google Apps
Darktremor Apps2SD 2.7.5.3 Beta 04 (If you found A2SD Flash This Thanks tkirton for this fix & kitman8888 for solution) Thread
Arabic Support (Thanks ardoid.com) (I doesn't test it. Please reports) ardoid.com
Change Log
Pure Google Mod V 0.8
- Fix 0.7 stability issue. (frequency random reboot on my n1)
Pure Google Mod V 0.7
- based on CyanogenMod 1.0.
Pure Google Mod V 0.4
- 20/03/2011 CyanogenMod Nightly.
- Fixing Permission. (That may cause GPS, A2SD problem in 0.3)
- Add new options.
Screenshot
ill try er out
what kernal should i use?
and hows battery life?(cause battery is my biggest concern)
Does it also feature the wonk?
squidbutt said:
ill try er out
what kernal should i use?
Click to expand...
Click to collapse
Same here.
BackfireNL said:
Does it also feature the wonk?
Click to expand...
Click to collapse
Isn't this being too persuasive to put faults which have not yet been proven wonking on this rom . Really love the effort though
It wonks by the way
Sent from my Nexus One using XDA App
It's from the future? Are we already in April? 13-04-11
Obsy said:
It's from the future? Are we already in April? 13-04-11
Click to expand...
Click to collapse
I was about to post the same thing
He apparently went at 88mph with 1.21 jiggawatts
- Kernel include in this rom is default CM7 nightly build (OC MAX 1.13 GHz)
- I have no idea on battery life, assuming same on CM7 build,
testing on my n1 (Always on 3G), it gets around 5-6 hrs, to 35% drain battery
- I still not found bug on CAM, Video CAM etc.
- but found a memory leaks when connected to usb for transfer big files.
- I 've correct the date on this thread, ha-ha-ha
How are you getting quadrant scores like that? I'm running the latest CM nightly and I rarely get above 1300
Amethystx said:
- Kernel include in this rom is default CM7 nightly build (OC MAX 1.13 GHz)
- I have no idea on battery life, assuming same on CM7 build,
testing on my n1 (Always on 3G), it gets around 5-6 hrs, to 35% drain battery
- I still not found bug on CAM, Video CAM etc.
- but found a memory leaks when connected to usb for transfer big files.
- I 've correct the date on this thread, ha-ha-ha
Click to expand...
Click to collapse
What do you mean you found a memory leak when connected to USB ? You sure this hasn't crept in from CM7 Nightly ?
Does it have track ball wake? is HSPA working?
tks great work
The download link of configuration.zip has been died. Plz check it.
stewartk said:
It wonks by the way
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Please exactly what is Wonk?
lcchan1 said:
Please exactly what is Wonk?
Click to expand...
Click to collapse
Below is an explanation of "the wonk" provided to me by Redstar, who is a close bud here on XDA and is a kernel developer too that provides great support here.
Per Redstar:
<<Don't know how much you've read about the wonk, so I'll try to briefly explain things...
It has to do with when you answer an incoming call (or make a call) after the phone has been asleep for some time and it either freezes and reboots or you won't be able to hear anything.... We've been able to trace it to a race in the i2c bus so that the a1026 chip isn't getting initialized correctly... what that translates to is that something is keeping the i2c bus busy, and when the voice processor chip tries to start up, it can't... so that's where you get the "wonk" from... >>
Nevermind
Docmjldds said:
Below is an explanation of "the wonk" provided to me by Redstar, who is a close bud here on XDA and is a kernel developer too that provides great support here.
Per Redstar:
<<Don't know how much you've read about the wonk, so I'll try to briefly explain things...
It has to do with when you answer an incoming call (or make a call) after the phone has been asleep for some time and it either freezes and reboots or you won't be able to hear anything.... We've been able to trace it to a race in the i2c bus so that the a1026 chip isn't getting initialized correctly... what that translates to is that something is keeping the i2c bus busy, and when the voice processor chip tries to start up, it can't... so that's where you get the "wonk" from... >>
Click to expand...
Click to collapse
Thanks and I did have "wonk" many many times regardless what GB 2.3.3 I tried.
lcchan1 said:
Thanks and I did have "wonk" many many times regardless what GB 2.3.3 I tried.
Click to expand...
Click to collapse
OTA doesn't have it!
when i try to install the configuration zip file, i get an 'install aborted' message. anyone else getting that?
unknownrebelx said:
How are you getting quadrant scores like that? I'm running the latest CM nightly and I rarely get above 1300
Click to expand...
Click to collapse
are you using quadrant advanced or the new one from the market? ive noticed benchmarks to be 200-300 points lower with the new one from the market. dont know why quadrant advanced benches higher. also, if you have a2sd or data2sd enabled your scores will be lower. changing setcpu scaling to performance while overclocked would help. so would closing all running processes
Yes!! My first release. (another kernel )
To keep it simple; this is a basic kernel, compiled from Samsung source.
My target was to keep it fast, stable and improve battery life at the same time.
Features:
Disabled unnecessary debugging and logging (logcat/dmesg) - for increased smoothness
OC/UV - CPU Freq range is 7 now (200/500/800/1000/1200/1400/1600)
Supports BLN
Touch sensitivity fix
Minor performance tweaks
CWM4
ROOT
Using Samsung Update2 source code
Using Chainfire's initramfs
Recommended Voltage:
OC/UV available with SetCPU or Voltage Controller.
1600MHz: 1350mV
1400MHz: 1250mV
1200MHz: 1200mV
1000MHz: 1100mV
800MHz: 1000mV
500MHz: 950mV
200MHz: 850mV
Screenshots:
Quadrant is not an accurate benchmark tool, but on an average with this kernel (Scaling: ondemand), I'm able to achieve ~4200 to ~4400.
{
"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"
}
Note: This is a hobby for me and I do this in my free time. If you like my work, you can always say thanks .
I would like to thank the following members of this community: chainfire, creams, hacre, codeworkx, hardcore, netarchy and vitalij.
If I forgot to mention someone - apologizes.
Disclaimer: Flashing could break your hardware. Use at your own risk!
Updates:
FD-Kernel_SGS2_v1.0b:
Updated initramfs to KI4
Oh a new kernel, cheers mate will try this out.
Sent from my GT-I9100 using XDA App
is this KH3?
Thanks man, another good kernel for us for testing and improving our phone's experience
Some questions :
1) root is an "auto-root" or it has to be installed using CWM?
2) BLN support includes correct libraries installation or it depends by specific rom (lights.GT-I9100.so modified)?
3) That quadrant score in the figure is high...on what build you were when you have obtained that result?
4) I often use GPS, have you planned for the future some kind of features to improve it?
Thank you for your work, i'll test it with pleasure.
Good luck! I wish you all the best!
A good idea would be to post what version's initramfs you're using. I suppose this is for XWKI4?
pan466 said:
is this KH3?
Click to expand...
Click to collapse
Its a kernel, you can use it with any build.
I'm using KG3 initramfs from Chainfire though.
HTCDevil said:
Thanks man, another good kernel for us for testing and improving our phone's experience
Some questions :
1) root is an "auto-root" or it has to be installed using CWM?
2) BLN support includes correct libraries installation or it depends by specific rom (lights.GT-I9100.so modified)?
3) That quadrant score in the figure is high...on what build you were when you have obtained that result?
4) I often use GPS, have you planned for the future some kind of features to improve it?
Thank you for your work, i'll test it with pleasure.
Click to expand...
Click to collapse
1) Auto-root
2) Kernel has the support, you should have compatible ROM or if required, I can provide the cwm zip to install the .so file.
3) Stock KG3
4) There is no point in releasing updates and making the users the guinea-pigs. If I'm able to achieve performance improvement without sacrificing battery and stability, I'll update and release a new version. But, yes, I plan on continuing the development.
Thanks for your support.
FrozenData said:
Its a kernel, you can use it with any build.
I'm using KG3 initramfs from Chainfire though.
1) Auto-root
2) Kernel has the support, you should have compatible ROM or if required, I can provide the cwm zip to install the .so file.
3) Stock KG3
4) There is no point in releasing updates and making the users the guinea-pigs. If I'm able to achieve performance improvement without sacrificing battery and stability, I'll update and release a new version. But, yes, I plan on continuing the development.
Thanks for your support.
Click to expand...
Click to collapse
Thank you for your answers. I'll test it on XWKI4 Odexed and then on my Deodex version. BLN libraries could be important but not needed (if everyone knew what to do ).
Have you provided any kind of script in etc/init.d?
Nice work, i've subscribed your 3D for following it
Battery calibration done now will discharge to 100% like a mad man today lol to test this out. Not had much luck with previous update2 kernels in relation to battery but lets see what this baby can do. UV settings so far stable, slight sensitivity issues whilst in charge. Will report my findings in due course.
Thanks again mate.
Sent from my GT-I9100 using XDA App
HTCDevil said:
Thank you for your answers. I'll test it on XWKI4 Odexed and then on my Deodex version. BLN libraries could be important but not needed (if everyone knew what to do ).
Have you provided any kind of script in etc/init.d?
Nice work, i've subscribed your 3D for following it
Click to expand...
Click to collapse
I'm guessing everyone knows about BLN library. Incase if someone asks for help, I'm sure either me or someone else will jump in to help.
No, I've not added any scripts.
Thanks.
nikzDHD said:
Battery calibration done now will discharge to 100% like a mad man today lol to test this out. Not had much luck with previous update2 kernels in relation to battery but lets see what this baby can do. UV settings so far stable, slight sensitivity issues whilst in charge. Will report my findings in due course.
Thanks again mate.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Thanks for the support.
Sourcecode?
FrozenData said:
Yes!! My first release. (another kernel )
To keep it simple; this is a basic kernel, compiled from Samsung source.
My target was to keep it fast, stable and improve battery life at the same time.
Features:
Disabled unnecessary debugging and logging (logcat/dmesg) - for increased smoothness
OC/UV - CPU Freq range is 7 now (200/500/800/1000/1200/1400/1600)
Supports BLN
Touch sensitivity fix
Minor performance tweaks
CWM4
ROOT
Using Samsung Update2 source code
Using Chainfire's initramfs
Recommended Voltage:
OC/UV available with SetCPU or Voltage Controller.
1600MHz: 1350mV
1400MHz: 1250mV
1200MHz: 1200mV
1000MHz: 1100mV
800MHz: 1000mV
500MHz: 950mV
200MHz: 850mV
Screenshots:
Quadrant is not an accurate benchmark tool, but on an average with this kernel (Scaling: ondemand), I'm able to achieve ~4200 to ~4400.
Note: This is a hobby for me and I do this in my free time. If you like my work, you can always say thanks .
I would like to thank the following members of this community: chainfire, creams, hacre, codeworkx, hardcore, netarchy and vitalij.
If I forgot to mention someone - apologizes.
Disclaimer: Flashing could break your hardware. Use at your own risk!
Updates:
FD-Kernel_SGS2_v1.0b:
Updated initramfs to KI4
Click to expand...
Click to collapse
May I tell you that is a little bit stupid for disabling debugging tools?
Now users can not do bugreports, cannot use adb for pushing files.
Cannot use adb in recoverymod for fixing a bad script, nothing.
ObihoernchenDE said:
Sourcecode?
Click to expand...
Click to collapse
I'll up it sometime next week. My bandwidth limit has almost reached for this month.
netchip said:
May I tell you that is a little bit stupid for disabling debugging tools?
Now users can not do bugreports, cannot use adb for pushing files.
Cannot use adb in recoverymod for fixing a bad script, nothing.
Click to expand...
Click to collapse
All final releases are supposed to have them disabled. Debugging is left on only for development purposes.
BTW, adb install/push/pull will still work. That isn't disable.
FrozenData said:
I'll up it sometime next week. My bandwidth limit has almost reached for this month.
All final releases are supposed to have them disabled. Debugging is left on only for development purposes.
BTW, adb install/push/pull will still work. That isn't disable.
Click to expand...
Click to collapse
Okay, but you can disable adb.
Debugging is also handy for people who make a own app, or ROM.
Ex. ROM chefs.
netchip said:
Okay, but you can disable adb.
Debugging is also handy for people who make a own app, or ROM.
Ex. ROM chefs.
Click to expand...
Click to collapse
Yes. But, disabling adb completely isn't a wise choice. In-case a user is facing problem with their ROM and data-wipe doesn't help, they will need to push in a clean ROM to flash from CWM, it is important to have adb then.
Developers should use another kernel. This is meant for end-users who likes their phones fast and stable.
Hi
I found a problem - i cannot use QtADB software ( hxxp: // qtadb.wordpress.com ) with his Kernel. Right now just SiyahKernel works great. Can you please take a look and see how to add the use of this software correctly under your system.
hxxp: // forum.xda-developers.com/showthread.php?t=683223 Some explanation of problem and how to fix it.
Thanks a lot for your help
Hey all, I thought I would put together a quick guide on how to port modules built for other devices. Since we share the same CPU as the One X and many other phones it's possible some of the mods for them are compatible with our phones too. In this case I was wanting to give coolbho3000's overclock module a try to see if it would work.
Please keep in mind that this will not always work and it's still better to try and use a module built specifically for your setup. Using a module that's not made for your device can cause all kinds of issues and seriously affect system stability. Always make sure you read the original instructions to make sure you understand how it works and how it's intended to be used.
Neither me, XDA or the module's author are responsible for anything that happens to your device. You and you alone are responsible for your actions.
First thing you'll want to do is try to load it as is, it probably won't work but it'll at least give you a place to start. In this case I'm using the overclock module from the One X so I used:
Code:
adb push krait_oc.ko /data/local/krait_oc.ko
adb shell
su
insmod /data/local/krait_oc.ko
{
"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"
}
If it is successful it won't say anything, but there you can see it failed as expected. In order to find out why it failed we'll need to run dmesg and look for where it tried to load it.
Code:
dmesg | grep "krait_oc"
There we can see module_layout is where the issue is. What we can do now is pull one of the already installed modules off of the device and use it as a reference, in this case I used lcd.ko since it has an easy name to type. Grab your two modules and using linux run modprobe to find a value for module_layout. (If you only have Windows available skip to next step)
Code:
modprobe --dump-modversions lcd.ko
Now that we know what to look for open up the module in a hex edit and search for "module_layout." Immediately before it you will see the value that needs to be changed, but, keep in mind that it is little endian so the bytes are read backwards. In the view of lcd.ko on the right you can see the value we previously got of '37 19 bc d3' is saved as 'd3 bc 19 37'.
Change those four bytes to match and then save the module under a new name so it is not confused with the original.
Once you save the edited module its time to push it to the device again and try once more.
And success! Sometimes you'll also need to edit the module to accept the current kernel version you are using, but the process should be similar as to what's here.
So, uhhhh . . . you gonna share that modded kernel?
utnick said:
So, uhhhh . . . you gonna share that modded kernel?
Click to expand...
Click to collapse
Kernel is still the same, this is just for the modules
*sigh* I wish I knew what that meant. Can I ask to you to explain it to me please? And does this mean you have the ability to port the kernel to OC an EVO LTE?
Got overclock working fine. Great thanks Haus
Can anyone make a zip? Pretty please.
You can't make a zip. you have to mod the ko file yourself and launch it yourself.
utnick said:
*sigh* I wish I knew what that meant. Can I ask to you to explain it to me please? And does this mean you have the ability to port the kernel to OC an EVO LTE?
Click to expand...
Click to collapse
Think of modules as sort of like an add-on for kernels, except that they're saved as part of the ROM instead of on boot. I used the one-x overclock module here, but since it's not made for the evo it may not be completely stable. Plus there are other changes that need to be made to the thermal profiles according to his original post.
Ideally coolbho3000 will be willing to create one for us and officially support it. I've already reached out to him about it so hopefully we'll hear something back soon.
Hey I know quadrants don't mean much but do you think you could get us a screenshot of our phones scores when overclocked?
Thanks for the guide by the way I will definitely try this when I have time...
Red.
So glad you're here haus :thumbup:
Sent from my EVO using xda premium
it there a way to remove a module, and replace a new edited ported *.ko?
all of this is done in recovery?
if trying to replace a module should just get to modding the kernel itself?
Great guide, I've been looking for something like this. So could I use this method to get USB hosting working? I know the one x (AT&T), has a custom kernel that supports it.
XDA University is Coming! Can't wait to learn more...
Immediately before it you will see the value that needs to be changed, but, keep in mind that it is little endian so the bytes are read backwards. In the view of lcd.ko on the right you can see the value we previously got of '37 19 bc d3' is saved as 'd3 bc 19 37'.
Click to expand...
Click to collapse
That's not little endian and reading backwards is not little endian when the original is not big endian. Little/big endians are in terms of byte size orders.
Good tutorial.
exSD said:
That's not little endian and reading backwards is not little endian when the original is not big endian. Little/big endians are in terms of byte size orders.
Good tutorial.
Click to expand...
Click to collapse
Thank you, but "byte size orders?"
xHausx said:
Thank you, but "byte size orders?"
Click to expand...
Click to collapse
Byte value order. Hex value.
thanks a lot
thanks a lot for your tutorial, and congrats,
i tried your tutorial and i cant modprob on linux, i atached the screenshot of what happenz,
i try "modprobe --dump-modversions usbhid.ko" and i receive a blank line with nothing, i tried with other modules and it do the same, but for the one who was extracted from my phones modules folder, it works,
and i also have a daught, i search for "module_layout" only or any other values?
hackerse7en said:
thanks a lot for your tutorial, and congrats,
i tried your tutorial and i cant modprob on linux, i atached the screenshot of what happenz,
i try "modprobe --dump-modversions usbhid.ko" and i receive a blank line with nothing, i tried with other modules and it do the same, but for the one who was extracted from my phones modules folder, it works,
and i also have a daught, i search for "module_layout" only or any other values?
Click to expand...
Click to collapse
Make sure you have spaces between your arguments. It also depends on what value it's telling you is incorrect, it may be different depending on which one you're trying to use.
xHausx said:
Make sure you have spaces between your arguments. It also depends on what value it's telling you is incorrect, it may be different depending on which one you're trying to use.
Click to expand...
Click to collapse
i already did that i think itś something wrong with the module because i put them i the same directory and the exact same commands and it just dont work, i atached some screenshots and the modules.
thanks for helping me
hackerse7en said:
i already did that i think itś something wrong with the module because i put them i the same directory and the exact same commands and it just dont work, i atached some screenshots and the modules.
thanks for helping me
Click to expand...
Click to collapse
i just cant undestand, if someone can help me.
based on Stock kernel amazon 514006420 sources with just the following 2 features added:
Overclocked to 1890MHz
init.d support (place files in /etc/init.d/ folder)
Since there is no known way to get into recovery with a bad kernel (yet), therefore it flashes only to the recovery partition for your safety. When you are done testing flash rbox's recovery back to the recovery partition.
prerequisites:
rbox's unlocked bootloader
rbox's latest recovery
instructions:
in CWM - flash zip
advance -> reboot recovery
When you boot into recovery the new kernel will boot, when you boot normally your stock kernel will boot. You will not have recovery until you flash rbox's recovery again.
Flash at your own risk!
Curious, what are the benefits of overclocking the Fire TV?
mjbxx said:
Curious, what are the benefits of overclocking the Fire TV?
Click to expand...
Click to collapse
Well it is called FIRE tv... so you can hope it lives up to it's name and catch on fire... Of course it's partly joking...
The FireTV has a MASSIVE heatsink.
What about the Adreno GPU?
Can you overclock Adreno320 from 400MHz to 450MHz or 500MHz?
retroben said:
The FireTV has a MASSIVE heatsink.
What about the Adreno GPU?
Can you overclock Adreno320 from 400MHz to 450MHz or 500MHz?
Click to expand...
Click to collapse
That's a good idea, i'll look into it when i have some spare time.
Can you notice any performance increase?
Here is an old topic I made which has a directory I found that contains the Adreno clocking files...
http://forum.xda-developers.com/fire-tv/help/overclocking-t2845001
ahoslc said:
Can you notice any performance increase?
Click to expand...
Click to collapse
I don't really use it that much and it wasn't slow before, so not really but here are my antutu benchmarks with GPU OC to 450, post yours and we can compare:
{
"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"
}
retroben said:
Here is an old topic I made which has a directory I found that contains the Adreno clocking files...
http://forum.xda-developers.com/fire-tv/help/overclocking-t2845001
Click to expand...
Click to collapse
Thanks, i got it up to 450, but i'm going to see if i can get it any higher.
Can you try out Mupen64Plus AE with those overclocked rates?
You can get a nice dev build in this thread to test (I also have it) that fixes DK64 collisions and stops Banjo-Tooie from crashing.
http://www.paulscode.com/forum/index.php?topic=1797.0
Try running Banjo-Tooie with my "no frameskip" code.
There is now a cheat editor built-in on this dev update,so you can easily add it to the cheat list.
No Frameskip
8007913F 0001
It normally lags quite a bit for me,please tell me how well it runs for you with overclocked CPU and GPU rates.
@jmandawg Hi, If it possible for you to enable the kernel exec (kexec) to allow us run linux kernel and I did asked @rbox to add the kexec support for CMW recovery. I think the kernel with kexec enable so it will allow cmw recovery with kexec enable boot linux kernel. rbox still figure how do it. I couldn't risk overwrite recovery partition with linux kernel due the kernel itself tend over 20mb which is the recovery partition only has 10mb space.
Otherwise I tested benchmark on my AFTV got 29301 score (stock) and am going test this overclock kernel to see how much improvement.
thanks again...
*UPDATED* I ran your overclock kernel, It apparently that benchmark went decreased to 26414 score vs amazon stock 29301. I puzzled. Something is going wrong. Maybe I should reset factory and reinstall fresh rbox's pre-rooted then re-test benchmark stock rbox pre-rooted vs overclock kernel again.
There's a pre built fedora kernel that works already in the fedora thread.. No need for kexec or unlocking either..
@nhumber Does pre-built fedora kernel size byte under 10mb? Let me read fedora thread again. thank you letting me know.
nhumber said:
There's a pre built fedora kernel that works already in the fedora thread.. No need for kexec or unlocking either..
Click to expand...
Click to collapse
No you'll have to do some playing with partitions, diag partition is what I tested, renamed to recovery.
jmandawg said:
I don't really use it that much and it wasn't slow before, so not really but here are my antutu benchmarks with GPU OC to 450, post yours and we can compare:
Thanks, i got it up to 450, but i'm going to see if i can get it any higher.
Click to expand...
Click to collapse
can you try running 3dmark benchmark with the modded kernel and gpu clock? might give a good indication on if theres any real world performance gains for gaming, i dont game on my firetv at all but i ran the benchmark just to watch and get a "stock" score for comparison, i scored 10958 on icestorm unlimited, i took a screenshot with the FPS of the different tests i can upload later, my galaxy s4 scored 10650 but i noticed google play was downloading stuff in the background..
side load from here.
http://apps.evozi.com/apk-downloader/?id=com.futuremark.dmandroid.application
Question: I get the fact that having an OC kernel is cool, but is it really needed? This thing runs very smooth, and I'm unsure if the extra load on the CPU is worth it... Even the potential shorter life to the CPU.
Also I don't know how efficient the thermal pad ( uses a pad not paste ) is under normal circumstances let alone when its going to be OC'd.
mroneeyedboh said:
Question: I get the fact that having an OC kernel is cool, but is it really needed? This thing runs very smooth, and I'm unsure if the extra load on the CPU is worth it... Even the potential shorter life to the CPU.
Also I don't know how efficient the thermal pad ( uses a pad not paste ) is under normal circumstances let alone when its going to be OC'd.
Click to expand...
Click to collapse
its probably not needed, i agree with the device being fast enough already, i dont play games on it, but for someone who does there could be some improvements noticed in things like emulators where you might already be seeing FPS drop here and there. 1.9ghz is the stock clock speed for these CPUs in some smartphones so i doubt its doing the hardware any damage at all.
Fire TV really does have a massive heatsink,which should help greatly when CPU and GPU are overclocked.
I'm talking about the heat... Sure it has a nice heatsink, but it can and will heat soak sooner or later...
Have you seen the aftv internal? They got darn excellent heat sink fully aluminum enough handling the heat soak absorb.
I have tested clocking over clock CPU and surprised that the heat is normal range yet hit overheat!
However I tested the benchmark yet beat the pre-rooted stock benchmark. We still tweaking like we still in baby mode
mroneeyedboh said:
I'm talking about the heat... Sure it has a nice heatsink, but it can and will heat soak sooner or later...
Click to expand...
Click to collapse
Fair enough..
Hi all.
Compatibility:
Builds from r1 to r5 are for Android 7.1 Nougat only.
Builds starting with r6 are for Android 7.1.1 Nougat only.
Builds starting with r12 are for Android 7.1.2 Nougat only.
Builds starting with r19 are for Android Pie only.
Download:
https://francokernel.app
Installation:
Flash the zip in your recovery
or
Auto-flash from FK Kernel Manager app, it's magical
Changelog:
https://francokernel.app
Scroll down, choose your device & select the latest release to see the changelog.
Source:
https://github.com/franciscofranco/marlin
Follow me on socials for updates and interesting tidbits
Twitter
FK Kernel Manager video
https://www.youtube.com/watch?v=ARdNqh71D0E
Disclaimer to moderators:
Slight OT is fine, but when users decide to act stupid they should be dealt with with the appropriate means - its really annoying for me when OT turns crazy. Please put the warning/ban hammer anytime any of you think there's lack of respect and/or too much unwanted OT crap - but if it doesn't meet this criteria let the OT posts alone. Thank you.
Cheers!
I think the only thing I haven't merged yet is controls for headphone volume boost. Other standard things are already there. Due to the unfortunate fact that we still don't have a custom recovery I haven't touched the ramdisk, so you're just flashing the actual Kernel binary (plus the device tree files that are bundled to it) through the bootloader. It's really straight forward though.
I wouldn't expect any magical battery improvements yet. Although I've made some custom patches to reduce needlessly cpu idle wakeups (don't confuse this with wakelocks, totally different things), and reducing the load average, I doubt there will be any magical enhancements. Though, I wouldn't be surprised if you get 5-10% better screen on time.
Also merged some upstream patches which gave me roughly 5-10% better Geekbench results on both single and multi threaded tests due to lower lock contention & reduced overhead.
Made sure ZRAM was properly set up too, which didn't seem to be the case by looking through the entire Google's device tree.
There's other things on my patches, but nothing groundbreaking.
Everything is in my github too. You know my approach, no bull****, so don't ask me for merge/add retarded crap.
Runs badass! Can't wait for more
Is there a feature list for this kernel? The change log 404s currently.
Nice!
Can we root with this kernel....thanks for your work
NoValidTitle said:
Is there a feature list for this kernel? The change log 404s currently.
Click to expand...
Click to collapse
Literally in the second post. I haven't added the changelog file yet.
cwalker0906 said:
Can we root with this kernel....thanks for your work
Click to expand...
Click to collapse
Yes... Why couldn't you?
franciscofranco said:
Literally in the second post. I haven't added the changelog file yet.
Click to expand...
Click to collapse
I read the second post. There isn't a feature list just says what you didn't include. I also looked at git hub and didn't see anything there either. Sorry.
franciscofranco said:
Yes... Why couldn't you?
Click to expand...
Click to collapse
Thought there was a patch that had to be made in kernel...wasn't sure
NoValidTitle said:
I read the second post. There isn't a feature list just says what you didn't include. I also looked at git hub and didn't see anything there either. Sorry.
Click to expand...
Click to collapse
I wrote a lot about what I included. I don't usually write feature lists, most of the words are just buzzwords for users to feel amazed but not actually know what they mean, so for a less biased experience I just don't have feature lists.
cwalker0906 said:
Thought there was a patch that had to be made in kernel...wasn't sure
Click to expand...
Click to collapse
Nah, you can root it.
franciscofranco said:
I wrote a lot about what I included. I don't usually write feature lists, most of the words are just buzzwords for users to feel amazed but not actually know what they mean, so for a less biased experience I just don't have feature lists.
Nah, you can root it.
Click to expand...
Click to collapse
Already running and rooted, thanks
cwalker0906 said:
Already running and rooted, thanks
Click to expand...
Click to collapse
Awesome!
Ok, I know... I am a newb! But I got a question for you Franco....
When I download the kernel I try to extract it using 7zip and get an error.
Should I not try to extract? What am I doing wrong here? Never had any issue like this before. Used your kernel on lots of devices and this is the first time I got this issue.
Anyone feel free to chime in...
{
"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"
}
-Scott
Scott said:
Ok, I know... I am a newb! But I got a question for you Franco....
When I download the kernel I try to extract it using 7zip and get an error.
Should I not try to extract? What am I doing wrong here? Never had any issue like this before. Used your kernel on lots of devices and this is the first time I got this issue.
Anyone feel free to chime in...
-Scott
Click to expand...
Click to collapse
It's not a zip, it's the Kernel binary.
Just seen this came out! Rooted and flashed FK1 Loving it so far Franco can't wait for more features! Any change of getting rid of the screen before the boot logo for it being modified? As always great work Fransisco
xReaper7x said:
Just seen this came out! Rooted and flashed FK1 Loving it so far Franco can't wait for more features! Any change of getting rid of the screen before the boot logo for it being modified? As always great work Fransisco
Click to expand...
Click to collapse
Nope not possible
franciscofranco said:
It's not a zip, it's the Kernel binary.
Click to expand...
Click to collapse
Ahhh, Thank you! I am running it now!
Sorry for being a newb, lol
-Scott
Scott said:
Ahhh, Thank you! I am running it now!
Sorry for being a newb, lol
-Scott
Click to expand...
Click to collapse
It's ok, we don't born knowning it all
The Android subreddit would always rave about your kernel during the Nexus 4 days. Excited to see future development.