Hi everyone
Voodoo kernels
I've finally been able to add support for Voodoo Sound into 2.6.39.x kernels, starting with Roach EOS3 #56 & guevor JB kernels.
With a kernel that has Voodoo Sound support added you can simply use the latest free version of the VoodooSound Market app, and it should work fine. (that shouldn't stop you from buying the voodoo sound pro licence to show your support to supercurio )
The 2 kernels zip are tailored specifically for the TeamEos3 JB rom, for other roms someone will most likely have to edit the ramdisk / scripts or simply use the patch posted into post #2 to add support into the kernels.
Please report if the kernels works for you too
This had been bugging me for a while, as the status of voodoo sound for our TF101 has kinda been on hold for a while.
Sure there is the beta app but it doesn't have most of the features from the original app.
And with the recent craving from the voodoo market app to want to overwrite the beta app, it's quite annoying
So now we can simply use the regular Voodoo app.
How to flash the kernels:
Just like any other kernels, use CWM or another recovery tool to flash the zip, then wipe /cache and reboot.
Disclaimer: The usual
Use at your own risk, I won't be responsible for any damages caused to your Transformer or to your ears.
Makes sure to test it carefully with the headphones not on your ears, before using it.
KatAudio KatAudio has now been moved into the android app See dedicated thread: http://forum.xda-developers.com/showthread.php?t=1841851
Since our current kernels can access the WM8903 registers directly through alsa and don't even require a voodoo kernel module for that, I've added a few "KatAudio" zips to get better sound at boot time directly without the need of voodoo sound.
If you're not only after max power, I'd suggest to flash the default script "Tim_KatAudio01_Enhancer.zip"
I find it to be the best compromise between quality and power myself.
The KatAudio zip will install the command line alsa mixer "tinymix" for you and activate more or less boot scripts automatically depending on which zip you choose, so that you don't have to play with command line
(About alsa see more info in this post: http://forum.xda-developers.com/showthread.php?p=29908141)
When I get more time I'll make an android app that can make it even more powerfull, flexible, and easier for you
I'll also create a new thread at that time, since these scripts are not using anything "Voodoo".
KatAudio Zips
just flash using CWM or another recovery
Tim_KatAudioXX_Enhancer.zip
Speakers: left speaker fix (induce volume boost too)
Headphones: volume boost
Other registers forcing, to make sure they are at their correct values.
Tim_KatAudioXX_Higher.zip
Same as _Enhancer
+ increase the headphones higher to 0dB
+ increase the speakers higher to +3dB
Tim_KatAudioXX_Max1.zip
Same as _Enhancer
+ increase the headphones to max analog +6dB
+ increase the speakers to max analog +6dB
Note that some of the scripts are maxing the volume, which might introduce clipping
If at max digital android volume you ear saturation, just decrease the android volume slightly for those cases.
All scripts above include the "Left Speaker fix", what it does is that it re-routes both LR channels through both Speakers,
that is not considered "hifi" anymore, but I don't think it matters much with that kind of speakers, compared to the benefits:
Lower Left speaker fixing + increase of volume.
From msg #2:
Tim_KatAudioXX_RemoveSpeakerFix.zip
If you prefer not to have the speakerFix activated by default, flash this script after flashing one of the above.
Tim_KatAudioXX_Removal.zip
If you want to remove KatAudio and go back to like it was before.
You can also flash any new rom on top and it'll get rid of it.
Credits:
- Supercurio for the original Voodoo Sound GPL patches I based this one onto.
- Roach and teameos for TeamEOS3 JellyBean Kernel
- Guevor for his awesome kernels
Sources:
For Guevor JB Kernel #696 branch: https://github.com/timduru/tf101-kernel-test
For TeamEOS3 Roach kernel: https://review.teameos.org/#/c/904/
Compatibility report from users:
Tim_VoodooV3_JBKernel_EOS3_Roach56.zip: JB - TeamEOS3
Tim_VoodooV3_JBKernel_EOS3_Guevor696.zip: JB - TeamEOS3
For other roms you should try to flash the "Generic enabler" zip, it seems to work fine with most 2.6.39.x kernel flavors so far, ICS or JellyBean.
For the generic enabler I've moved the kernel side code into a module and it will try to add the module for you at boot time.
(Pending that the rom has init.d support, but most custom roms should have it)
It might be a hit or miss but that shall add support for most kernels in a more generic way
EDIT: Generic enabler zip removed as to respect Supercurio's wish and preferences.
You can check our discussions in his thread if you want to see our views on that subject: http://forum.xda-developers.com/showthread.php?p=29940776
You can still use the specific kernels that have the modules inside, since for him it's not the same and is ok...
Tim_VoodooV3_2.6.39_Kernels_GenericEnabler_2.zip:
ICS - ARHD 3.5.1 - Stock Kernel
ICS - Revolver 4.1.1 - Guevor Kernel V22.6
ICS - ARHD 3.5.1 - test kernel #689
ICS - Megatron 116 - guevor kernel #657
ICS - CM9 Nightlies - Rayman Harmony kernel
JB - TeamEOS3 - GuevorKernel#696
JB - TeamEOS3 - RoachKernel#56
JB - JELLYBRO-cm-10-20120804.1329 - Default rom kernel
JB - RaymanFX-AOSP #3- Default rom kernel
(Working - Works with manual insert - Not Working)
For roms that require a manual insert of the module (rom doesn't support init.d)
do the following:
- launch a terminal
type the following commands:
su
insmod /system/lib/modules/voodoo-sound.ko
kill / relaunch voodoo app.
Please make it compatible with the rayman 33 asop jellybean build!!
excellent work ! working like a charm with the latest Voodoo app from the market and EOS3-N56.
Thank's!!!!!!
what change with this voodoo sound respect to normal sound?
is more hight?
Finally, thanks.
Inviato dal mio Transformer TF101 usando XDA Premium HD app
Can it be OC'ed ???
alizafar said:
Please make it compatible with the rayman 33 asop jellybean build!!
Click to expand...
Click to collapse
Never tried his rom, but I might have a look after I'm done with adding Voodoo to Guevor's kernel..
It should be about the same if rayman has kernel source posted.
cbrox said:
excellent work ! working like a charm with the latest Voodoo app from the market and EOS3-N56.
Thank's!!!!!!
Click to expand...
Click to collapse
perfect, thanks for the report
acquariusoft said:
what change with this voodoo sound respect to normal sound?
is more hight?
Click to expand...
Click to collapse
Supercurio's thread will explain it better than me. check there:
http://forum.xda-developers.com/showthread.php?t=1132875
sagar_tiru2006 said:
Can it be OC'ed ???
Click to expand...
Click to collapse
Yes, for the 1st kernel I posted, the base is EOS3 #56 Roach's kernel.
I see that you are using Guevor V23 kernel, I'm currently trying to get his #696 to compile with Voodoo sound, I'll post it too when I'm done if you prefer to wait for that one
it works very well!!
Good work!
Can you try to solve the problem with audio problem with hdmi output with your kernel?
Inviato dal mio Transformer TF101 con Tapatalk 2
acquariusoft said:
Can you try to solve the problem with audio problem with hdmi output with your kernel?
Inviato dal mio Transformer TF101 con Tapatalk 2
Click to expand...
Click to collapse
It's a userspace issue, we're working on it.
@OP: If you ever want to do one for AOKP, don't. I'll be adding Voodoo soon anyway.
K900 said:
It's a userspace issue, we're working on it.
@OP: If you ever want to do one for AOKP, don't. I'll be adding Voodoo soon anyway.
Click to expand...
Click to collapse
The voodoo beta or pre-alpha (or whatever it is called) for ICS works just fine on JB aokp, aosp or cm10 based ROMs that I've tried, as long as you own the paid Voodoo Plus license. No kernel support needed by design.
K900 said:
It's a userspace issue, we're working on it.
@OP: If you ever want to do one for AOKP, don't. I'll be adding Voodoo soon anyway.
Click to expand...
Click to collapse
good, i hope you can work together for solve this big problem ;D
Inviato dal mio Transformer TF101 con Tapatalk 2
sidneyk said:
The voodoo beta or pre-alpha (or whatever it is called) for ICS works just fine on JB aokp, aosp or cm10 based ROMs that I've tried, as long as you own the paid Voodoo Plus license. No kernel support needed by design.
Click to expand...
Click to collapse
The beta app just turns voodoo sound on but it doesn't have any features though, and it doesn't seem to go anywhere unfortunately.
I've paid for the licence myself, but in EOS3 the beta app is not even able to map the analog gain with the volume slider anymore in the latest versions.
If you get a compatible kernel you can simply use the regular Voodoo app that works fine and has all the features.
You will also benefit from the voodoo market app updates as it seems Supercurio is still updating that one at least.
timduru said:
Yes, for the 1st kernel I posted, the base is EOS3 #56 Roach's kernel.
I see that you are using Guevor V23 kernel, I'm currently trying to get his #696 to compile with Voodoo sound, I'll post it too when I'm done if you prefer to wait for that one
Click to expand...
Click to collapse
Looking foward to it I flashed this kernel either wayz
timduru said:
The beta app just turns voodoo sound on but it doesn't have any features though, and it doesn't seem to go anywhere unfortunately.
I've paid for the licence myself, but in EOS3 the beta app is not even able to map the analog gain with the volume slider anymore in the latest versions.
If you get a compatible kernel you can simply use the regular Voodoo app that works fine and has all the features.
You will also benefit from the voodoo market app updates as it seems Supercurio is still updating that one at least.
Click to expand...
Click to collapse
I'm not knocking your work or anything, good to see things progress, as long as you have supercurio's blessing. He got mad at me for posting a link to the app on my dropbox trying to help someone out. I was just saying that the ICS app w/license works on JB seemingly the same as it does on ICS, lacking the same features it lacked there. Still, it does improve the sound if you already own the license. I see that supercurio posted that he is going to update the market app (bug) and also update the beta app soon.
sidneyk said:
I'm not knocking your work or anything, good to see things progress, as long as you have supercurio's blessing. He got mad at me for posting a link to the app on my dropbox trying to help someone out. I was just saying that the ICS app w/license works on JB seemingly the same as it does on ICS, lacking the same features it lacked there. Still, it does improve the sound if you already own the license. I see that supercurio posted that he is going to update the market app (bug) and also update the beta app soon.
Click to expand...
Click to collapse
No offense taken
I just wanted to add precisions for those who've not tried the beta app yet, that way they know what to expect.
As for the kernel well, I just did it the way supercurio wanted it to work and how it was working previously, so I don't see why there would be a problem:
supercurio said:
Free version requires a kernel implementing Voodoo sound GPL patches as you'll find plenty on XDA.
Click to expand...
Click to collapse
And well you can still buy the licence even if you have a kernel supporting voodoo, voodoo is definitely a great sound enhancement for the TF101, so it's a good move to thanks supercurio for bringing it originally too
First post updated with Guevor's JB #696 kernel voodoo support.
I've also added a Generic 2.6.39.x kernel enabler.
Depending on your rom and kernel it *might* work.
It might actually work for ICS roms too if they use 2.6.39 kernels...
Please report the rom - kernels combinations that are working with it.
See 1st post for updated instructions.
alizafar said:
Please make it compatible with the rayman 33 asop jellybean build!!
Click to expand...
Click to collapse
Try the generic enabler and report
It *should* work, unless Rayman has made major changes to the tegra sound files.
Generic enabler report: running ARHD 3.5.1 with stock kernel..... voodoo-sound module does not load with provided script. Changing the init script commandline to "insmod /system/lib/modules/voodoo-sound.ko" the module loads at boot and the old app works fine. Thanks for this.
Sent from my Transformer TF101 using xda premium
OK, so I flashed the voodoo enabled guevor JB #696 kernel on eos3. It didn't really change anything with the beta app and license setup, other than loading the additional module, sound and control were the same. But, it did let me update to the latest market app and now I don't have to keep dismissing the notification about an update. A few more control settings than the ICS app. Looks pretty good. Thanks. I also reflashed DSP Manager from the Revolver thread which gives pretty good control and results for shaping the resultant sound further.
bkmo said:
Generic enabler report: running ARHD 3.5.1 with stock kernel..... voodoo-sound module does not load with provided script. Changing the init script commandline to "insmod /system/lib/modules/voodoo-sound.ko" the module loads at boot and the old app works fine. Thanks for this.
Click to expand...
Click to collapse
Ah good news then, thanks for the info
That means that it's working with ICS roms too, which is good
I've updated the Generic enabler zip in the first post.
Do you mind retesting it to make sure it works with ARHD too now ?
Using insmod is definitely better, and should be more compatible with the different roms.
The default android one lacks the -f option though, but it shouldn't be too much of a problem unless the kernel is of too different version and uses the module magic version.
sidneyk said:
OK, so I flashed the voodoo enabled guevor JB #696 kernel on eos3. It didn't really change anything with the beta app and license setup, other than loading the additional module, sound and control were the same. But, it did let me update to the latest market app and now I don't have to keep dismissing the notification about an update. A few more control settings than the ICS app. Looks pretty good. Thanks. I also reflashed DSP Manager from the Revolver thread which gives pretty good control and results for shaping the resultant sound further.
Click to expand...
Click to collapse
Okie, sound good
Related
I've recently Installed Netarchy Nexus - 1.3.4-cfs-2.3.4 (For stock 2.3.4 roms) on my Rooted Stock Nexus S i9020A running 2.3.4 and suddenly my phone refuses to load the voodoo sound driver.
Voodoo Control Plus say that My Nexus S doesn't run a kernel supporting extended sound controls. My phone Loads the voodoo video drivers just fine however. Voodoo Control Plus has SuperUser permissions, so I'm interested if anyone has any ideas regarding what could be causing the conflict with the sound driver. I read somewhere that widget locker can cause problems so I disabled it. I would have posted this question in the Netarchy forum, but apparently I don't have the required number of posts just yet, because I'm pretty self sufficient and relatively decent at hacking my phone most days.
Any ideas or help would be greatly appreciated. Netarchy worked fine until I migrated to stock 2.3.4
Netarchy Nexus - 1.3.4-cfs-2.3.4 (For stock 2.3.4 roms) may simply not support Version 9 of the Voodoo Kernel Module just yet. It appears it was compiled with version 8. However, this still doesn't explain the module refusing to load at all from time to time.
Voodoo likes the stock Kernel for sound. Of course the stock Kernel doesn't support the video drivers.
guppetto said:
I've recently Installed Netarchy Nexus - 1.3.4-cfs-2.3.4 (For stock 2.3.4 roms) on my Rooted Stock Nexus S i9020A running 2.3.4 and suddenly my phone refuses to load the voodoo sound driver.
Voodoo Control Plus say that My Nexus S doesn't run a kernel supporting extended sound controls. My phone Loads the voodoo video drivers just fine however. Voodoo Control Plus has SuperUser permissions, so I'm interested if anyone has any ideas regarding what could be causing the conflict with the sound driver. I read somewhere that widget locker can cause problems so I disabled it. I would have posted this question in the Netarchy forum, but apparently I don't have the required number of posts just yet, because I'm pretty self sufficient and relatively decent at hacking my phone most days.
Any ideas or help would be greatly appreciated. Netarchy worked fine until I migrated to stock 2.3.4
Click to expand...
Click to collapse
Voodoo sound works fine in 1.3.4. Voodoo plus does not need to load a driver on my builds because the driver is already built in. If you are seeing the generic module load error, just hit continue and you should be fine. The bundled driver in voodoo plus only applies to kernels that dont have voodoo sound in them already.
Sent from my Transformer TF101 using Tapatalk
Beware of Voodoo Plus Upgrades
netarchy said:
Voodoo sound works fine in 1.3.4. Voodoo plus does not need to load a driver on my builds because the driver is already built in. If you are seeing the generic module load error, just hit continue and you should be fine. The bundled driver in voodoo plus only applies to kernels that dont have voodoo sound in them already.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
You're correct, it's not the Beta Kernel that has the issue. The most recent update of Voodoo Plus causes a conflict that prevents the voodoo sound driver from loading period. You're current Beta Kernel comes with version 8 of the sound driver and the recently updated Voodoo Plus now comes with version 9, but apparently, during the boot process a conflict is occurring on my Nexus S i9020A Stock 2.3.4 between you're Kernel Driver and the Latest Voodoo Plus Kernel driver because neither version of the sound driver is being loaded. The video driver loads just fine.
To make sure this was the issue, I used Titanium Backup to restore a previous version of Voodoo Plus and sure enough, while I received the module message, I could indeed hit continue and verify that version 8 of the driver baked into your Beta Kernel had in fact loaded. I'm not sure if Supercurio is aware. I doubt he tests Voodoo Plus against the various versions of kernels out there. You may want to make note of the potential issue in you're release notes if more of these questions pop up from those that have upgraded Voodoo Plus
Do you have any plans to update the voodoo sound driver to version 9 in one of your beta builds or will you stick with version 8 until you release your next stable build? Version 9 has Direct Hardware Amplification (Hardware based Bass Boost) that Many devices will greatly benefit from sound wise.
Oh yeah, thanks for the great Kernel work. You're Kernels gives amazing battery life and Keep My Nexus S running like a champ. I haven't even bothered to overclock my device because everything's running so smoothly with your kernel.
guppetto said:
You're correct, it's not the Beta Kernel that has the issue. The most recent update of Voodoo Plus causes a conflict that prevents the voodoo sound driver from loading period. You're current Beta Kernel comes with version 8 of the sound driver and the recently updated Voodoo Plus now comes with version 9, but apparently, during the boot process a conflict is occurring on my Nexus S i9020A Stock 2.3.4 between you're Kernel Driver and the Latest Voodoo Plus Kernel driver because neither version of the sound driver is being loaded. The video driver loads just fine.
To make sure this was the issue, I used Titanium Backup to restore a previous version of Voodoo Plus and sure enough, while I received the module message, I could indeed hit continue and verify that version 8 of the driver baked into your Beta Kernel had in fact loaded. I'm not sure if Supercurio is aware. I doubt he tests Voodoo Plus against the various versions of kernels out there. You may want to make note of the potential issue in you're release notes if more of these questions pop up from those that have upgraded Voodoo Plus
Do you have any plans to update the voodoo sound driver to version 9 in one of your beta builds or will you stick with version 8 until you release your next stable build? Version 9 has Direct Hardware Amplification (Hardware based Bass Boost) that Many devices will greatly benefit from sound wise.
Oh yeah, thanks for the great Kernel work. You're Kernels gives amazing battery life and Keep My Nexus S running like a champ. I haven't even bothered to overclock my device because everything's running so smoothly with your kernel.
Click to expand...
Click to collapse
Ok, an update of SU seems to now allow Version 9 of the sound driver to load using you're Beta Kernel. This is weird, but the desired result. An update of Voodoo Plus still breaks voodoo sound though.
Please read this post through thoroughly before downloading.
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!
NOTE: The settings in the general tab are only functional in kernels that have implemented the simple sysfs interfaces for usb fast charging and audio boost. If you toggle them, its not going to break anything, but they won't work and the app may crash. If you would like your kernel dev to implement the interfaces, please direct them to these two commits:
https://github.com/Chad0989/android_kernel_common/commit/a7c21fa0391c225900f93960362535179c0cecc9
https://github.com/Chad0989/android_kernel_common/commit/41dc138bae23dc7582de72a4d9895aaa8e1f8b2d
NOTE2: It is a requirement of the HAVS adjustment that the kernel you are using has the HAVS sysfs interface implemented. If it does not, it will not work.
NOTE3: Before using, please delete any boot scripts you may have in /etc/init.d that toggle any of the settings this app controls.
Get it at http://www.incredikernel.com
Restore script - use this if you went too low and find yourself in a boot loop. Flash through recovery:
http://www.incredikernel.com/?p=229
Froyo/sense kernels modified to work with the interface:
http://chad0989.dyndns.org/mirror/toastmod-4.3.4-cfs-havs-sysfs-less-nosbc-universal-signed.zip
http://chad0989.dyndns.org/mirror/toastmod-4.3.4-cfs-havs-sysfs-more-sbc-universal-signed.zip
Is this compatible with sense?
biglilsteve said:
Is this compatible with sense?
Click to expand...
Click to collapse
It should be as long as your kernel supports HAVS + sysfs. Feel free to test and provide feedback, it's greatly appreciated.
Giving it a whirl now! Been waiting for a voltmod or sense!
Won't start up on my device. I know my kernel is a HAVS kernel...not sure how to verify sysfs though...
biglilsteve said:
Won't start up on my device. I know my kernel is a HAVS kernel...not sure how to verify sysfs though...
Click to expand...
Click to collapse
What kernel are you running? Unfortunately I'm not familiar with the selection of kernels for the EVO. If you kernel supports HAVS the developer should be able to easily implement the sysfs interface if he is so willing. You can direct him to the following commit which he can pull a patch from, it will have to be modified because its for the inc, but it should be fairly easily patched in:
https://github.com/Chad0989/android_kernel_common/commit/4625ffe10406626c2a3cbf31236c889395f0e9d4
If the developer doesn't want to add it in, let me know and I will pull his source, add it, and post a build that does support it for you.
Yeah, I figured being an inc developer you wouldn't be too familiar with EVO kernels. I'm using netarchy-toastmod 4.3.4. It's a HAVS sense kernel. Today the developer discontinued support for it since it is a froyo kernel and just about everyone (not me) has moved onto gingerbread...
I'm using myn's Warm TwoPointTwo RLS5 rom
Kernel thread is here:
http://forum.xda-developers.com/showthread.php?t=719763&highlight=netarchy
EDIT: I forgot to say THANK YOU for offering your help and even your willingness to take a shot at adding sysfs to that kernel
Hope this wasnt taken from Vipermod...
Regardless of whether or not it was taken from Vipermod, if it works for sense then it does something Vipermod can't.
Don't get me wrong, I rock Vipermod when I'm running MIUI and love it...but we need a solution like that for sense.
This has absolutely nothing to do with vipermod. In fact I was releasing undervolt scripts before viperboy was. I just stayed incredible only for a long time.
Sent from my ADR6300 using XDA App
workin nice on aosp (cm7) SZ kern thx very convenient
biglilsteve said:
Yeah, I figured being an inc developer you wouldn't be too familiar with EVO kernels. I'm using netarchy-toastmod 4.3.4. It's a HAVS sense kernel. Today the developer discontinued support for it since it is a froyo kernel and just about everyone (not me) has moved onto gingerbread...
I'm using myn's Warm TwoPointTwo RLS5 rom
Kernel thread is here:
http://forum.xda-developers.com/showthread.php?t=719763&highlight=netarchy
EDIT: I forgot to say THANK YOU for offering your help and even your willingness to take a shot at adding sysfs to that kernel
Click to expand...
Click to collapse
Here you go. I'd highly recommend that you nandroid beforehand because I have no device to test it on.
http://www.incredikernel.com/wp-con.../download.php?id=netarchy_sense_havssysfs.zip
Looking forward to trying this out when we get a gb kernel tossed our way.
androidsupra said:
Looking forward to trying this out when we get a gb kernel tossed our way.
Click to expand...
Click to collapse
Shouldn't need one. As far as I can tell, there are gb kernels with havs and sysfs for the evo already.
Sent from my ADR6300 using XDA App
chad0989 said:
Here you go. I'd highly recommend that you nandroid beforehand because I have no device to test it on.
http://www.incredikernel.com/wp-con.../download.php?id=netarchy_sense_havssysfs.zip
Click to expand...
Click to collapse
I tried flashing this (I also run netarchy's latest) sent me into bootloops. I didn't nandroid back but I did have to reflash my kernel to get it to boot up. When I open the app all I get is a black screen. Hope this helps.
Sent from my PC36100 using Tapatalk
mrcrptguy said:
I tried flashing this (I also run netarchy's latest) sent me into bootloops. I didn't nandroid back but I did have to reflash my kernel to get it to boot up. When I open the app all I get is a black screen. Hope this helps.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Try this one:
http://chad0989.dyndns.org/mirror/netarchy_sense_havssysfs-2.zip
FYI on Sense: This probably won't work with 2.3.3 [Gingerbread] *YET* for the following reason:
No source from HTC. No HAVS kernels yet. Known fact that kernels for 2.2 [Froyo] won't work (or don't work well) with 2.3.3 [Gingerbread].
github said:
FYI on Sense: This probably won't work with 2.3.3 [Gingerbread] *YET* for the following reason:
No source from HTC. No HAVS kernels yet. Known fact that kernels for 2.2 [Froyo] won't work (or don't work well) with 2.3.3 [Gingerbread].
Click to expand...
Click to collapse
That's how it is with the inc as well. So at least everyone is on the same page there.
chad0989 said:
Try this one:
http://chad0989.dyndns.org/mirror/netarchy_sense_havssysfs-2.zip
Click to expand...
Click to collapse
Fantastic! This kernel boots and the app runs on myn's Warm TwoPointTwo!
I wish I were more specific on which variant of the kernel I am using:
netarchy-toastmod 4.3.4. cfs havs more sbc
Are you able to implement the sysfs on that variant?
Another question...after setting the voltages, is there a way to actually verify the new voltages have been taken?
biglilsteve said:
Fantastic! This kernel boots and the app runs on myn's Warm TwoPointTwo!
I wish I were more specific on which variant of the kernel I am using:
netarchy-toastmod 4.3.4. cfs havs more sbc
Are you able to implement the sysfs on that variant?
Another question...after setting the voltages, is there a way to actually verify the new voltages have been taken?
Click to expand...
Click to collapse
Open a terminal and type:
cat /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
Alternatively you can just open and then close the app, when the app opens it reads the current voltages and displays them. So if the voltages remain at what you set them too, they took.
Also if you could confirm that the sysfs interface is definitely working for me that would be great. To do this I would like you to set the min and max voltage for whatever max frequency you use to something low and definitely unstable, lets say 1000, click apply (make sure set on boot is unchecked) and load your phone (open a game or something). It should lock up and/or reboot pretty quickly. If it doesn't lock, then the voltages might not actually be being set. In this case, let me know.
I used the most vanilla variant of the kernel, havs, nosbc, if you confirm it working I'll build an sbc version.
This kernel aims to improve performance, while still maximizing stability (and getting rid of reboots and SODs). It's working on all ROMs so far, so here it is for your approval. It can overclock to 1704Mhz, but doesn't override your user limit. I've added SIO and Init.d support and some various tweaks, and rebased to the newest source. Next is more cpu governors and general tweaks. Thanks to Roach for his commits from github, and guevor for new suspend code to imitate.
Some ROMs use a different build config, so Use The Right Version Below! Please Wipe Cache in CWM before flashing.
Update 4/11/12: Added test version of Veno, read about it at: http://www.ie.cuhk.edu.hk/fileadmin/staff_upload/soung/Journal/J3.pdf1.0 is up for All testers. Voodoo should be supported, please report. Wifi has been tested on Stock/ARHD/Revolver/Megatron/CNA/AOKP, but please test with other ROMs. I'm trying to compile one kernel for all ROMs, but EOS is still separate. Mega props to Guevor for the new suspend code. I'm trying to implement it without directly copying him though, so I need testers again. I will compile for other ROMs if necessary.
Update 4/7/12-2: 0.8 Added OC up to 1704mhz, Under/Overvolt support, made some changes to error handling for wifi stack, tweaked default voltages, and some stuff I can't remember right now. For testing, 0.8 downloads are in green. CIFS, TUN, and NTFS are cooked in, you should not need to load modules. There is a download link provided below for people who want the modules anyways.Personally tested on all ROMs listed, haven't had time to try Frozn.
Install with CWM or Rogue
Download 1.0(All ROMs, except EOS):http://db.tt/nNEbqufy
Download 1.0 With TCP_VENO(All ROMs, except EOS):http://db.tt/CqEqLMDQ
Download 1.0(EOS):http://db.tt/nnn4x9mN
Download 0.8(Stock/ARHD/Revolver/Megatron):http://db.tt/XyxW8WTK
Download 0.8(CNA/CM9Mar29/AOKP):http://db.tt/fiOXe16e
Download 0.8(EOS)http://db.tt/rcUAfPjz
Download 0.6 (Stock/ARHD/Revolver):http://db.tt/YDIInoKn
Download 0.6 (CNA, CM9, AOKP):http://db.tt/wdwPhWVt
Download 0.6 (EOS):http://db.tt/1yAOB7tq
Download 0.7 (Stock/ARHD/Revolver):http://db.tt/YsOdC3Tk
Download 0.7 (CNA, CM9, AOKP):http://db.tt/91iLDpKq
Download 0.7 (EOS):http://db.tt/HVY81MUQ
CIFS/NTFS Modules: http://dl.dropbox.com/u/21284412/modules.zip
You shouldn't need these, but I'll leave the link for old time's sake.
This is still beta. You must have balls to flash this(metaphorically speaking). Don't rip mine off if you have to reflash something else.
I had a couple requests for a donation link, so I'm posting one below. Feel free to buy me a beer if you want, but most of the work was done by the source code and people before me.
Click Here To Donate To My Delinquency
Github is at: https://github.com/msticninja/asus_kernel_tf101
Changelog:
Code:
1.0-Veno Add TCP_VENO as default ipv4 Congestion Control Method
1.0 Change suspend code to be closer to guevor's. Hopefully fix reboots again. Add post_boot exec for ARHD.
0.9 Change clk_disable_locked code to be closer to Nvidia source. Hopefully fix reboots.
0.8 Add BFQ, Over/Undervolt support, wifi patches, OC to 1704, etc.
0.7 Rebased off Asus March 29th Kernel Source. SIO/Init.d is now included in all kernels.
0.6 Fixed Wifi on CNA SIO Version(still getting the hang of using git branches, sorry)
0.5 Add Init.d support to ramdisk
0.4 Add SIO IO Scheduler
0.3 Add EOS Version
0.2 Add CNA/CM9/AOKP Version
0.1 Add OC and compile tweaks
Compatible with cyanogenmod?
psyk974 said:
Compatible with cyanogenmod?
Click to expand...
Click to collapse
Depends. Try it. The worst thing will be that the wifi doesn't work. I'm working on the bcmdhd version for people with AOSP roms, that may use the same driver.
Thx. I will try it !
Thank you , but can u chack if the dock 2xUSB (removable disk) is working?
Because on every OC ICS kernel that i tried so far on the tf101 , the dock USB stop working
psyk974 said:
Thx. I will try it !
Click to expand...
Click to collapse
Let me know what happens. If anything isn't right, give me as much detail as you can.
i9apps said:
Thank you , but can u chack if the dock 2xUSB (removable disk) is working?
Because on every OC ICS kernel that i tried so far on the tf101 , the dock USB stop working
Click to expand...
Click to collapse
Just checked with a couple of flash drives, works perfectly.
msticninja said:
Let me know what happens. If anything isn't right, give me as much detail as you can.
Click to expand...
Click to collapse
Okay ! I inform you
msticninja said:
I just compiled this from my github, which is forked from Roach's(He's working on EOS, so I'm filling in the void for now, with his permission). It's working beautifully for me on stock ROM and ARHD so far, so here it is for testing. It can overclock to 1600Mhz, but doesn't override your user limit. Blades' test kernel "meh" overrides the user limit once the screen is off, which makes my TF reboot constantly. That's really the only reason I compiled my own kernel, but I know other people have this issue, and Roach said he doesn't have time to compile and post it for us. Thanks to Roach of course, and Blades, because I used his "meh" updater-script (because I forgot which partition the kernel was supposed to be dd'ed to.)
Install with CWM, (or Rogue(untested though))
Download:http://db.tt/wKQ6ho2h
This is still beta. You must have balls to flash this(metaphorically speaking). Don't rip mine off if you have to reflash something else.
Going to bed now. Will respond to responding responders in morning. Seriously. Me So Tired.
P.S. @guevor Didn't mean to post this right after you merged Roach's fix, we must've been compiling at the same time, little did we know.
Click to expand...
Click to collapse
Dont forget the source or patches main rule !!!
Could you list the Core mV per frequency too please?
Jhinta said:
Dont forget the source or patches main rule !!!
Click to expand...
Click to collapse
Grrr...lack of sleep. I thought I did. Appended.
cspiby said:
Could you list the Core mV per frequency too please?
Click to expand...
Click to collapse
https://github.com/msticninja/asus_kernel_tf101/blob/d1da185880877e22c7881fe69d4cb650e7a84ba5/arch/arm/mach-tegra/tegra2_dvfs.c
Too sleepy to make a table out of it. I'll do it tomorrow if you can't figure it out from the source.
Just flashed the kernel , got a first reboot after 4 seconds
will try again now
i9apps said:
Just flashed the kernel , got a first reboot after 4 seconds
will try again now
Click to expand...
Click to collapse
Like I said, if you have issues, give as much info as possible. ROM, frequency settings, etc. I only have one TF to test on, so you'll have help me out.
initd support?
drakal said:
initd support?
Click to expand...
Click to collapse
Haven't had time yet, just made it for my own purposes originally. I'll put a new ramdisk together and repack tomorrow if someone else hasn't done it by then.
msticninja said:
Like I said, if you have issues, give as much info as possible. ROM, frequency settings, etc. I only have one TF to test on, so you'll have help me out.
Click to expand...
Click to collapse
I am running Revolver rom 1600 GHz and the kernel not working for me , the tf freeze or reboot, on the other kernels i manage to OC to 1.68Ghz stable
i9apps said:
I am running Revolver rom 1600 GHz and the kernel not working for me , the tf freeze or reboot, on the other kernels i manage to OC to 1.68Ghz stable
Click to expand...
Click to collapse
I haven't tested on Revolver. I didn't add init.d support yet, so it could be that. Can you run at lower frequencies without rebooting? Mine can't handle 1600 on any kernel, so I can't really troubleshoot that, but if it still reboots at 1000 or 1200, then it's probably a ROM incompatibility. We'll see if anyone else can test it on Revolver in the mean time.
Hi,
tested your kernel with CNA 1.5.5.3 sadly no wifi.
Now I'm back on stock
Greetings
Nice to see more kernels popping up
I would help you test it, but frankly Im not in the mood to troubleshoot (if needed) today
Been screaming at a PC all day that refused to work properly hehe
First off, here is the github
https://github.com/pio-masaki/at100-kernel.git
Everything I do for this kernel is done there.
Now that's out of the way, here are some highlights:
Beginning of OC code (yes, an OC ICS kernel)
Added a slew of governors for your choosing
Added a couple i/o schedulers
Slight CFLAG tweaking
This is a work in progress!
If you have issues feel free to report, but this is my first ever kernel project, and it may take some time for me to address them!
Dos and Dont's in this thread:
No flaming, please. If someone asks a question thats been asked before, simply remind them and if you would, link the post or thread containing the answer. Replies like "Use search" don't help at all. Saying "Next time, use the search, the information is here" is of course what I would like to see. XDA will be better for this.
No ETAs! I can not, and will not, make any promises on when I can fix, build, or otherwise even think about this kernel, or any rom, period. Asking for ETAs, even politely, will either go unanswered, or reminded of this note.
Issue reporting: I always welcome issue reports, of course, however keep in mind, the point made above is also covering this, I may not have time to address an issue immediatly, though I will try to post back and acknowledge that I have seen the issue, or to ask further questions. Please include as much information as possible, settings for speed, governor, IO, profiles in use for screen off (which I advise against), cpu control app in use, etc. Dmesg would be nice as well, use pastebin, we don't want to see an 8K line post of a log
Changelog:
Experimental V0.1 10-02-12
First "release" for testing. This is internal build 8, and from this point on, will be labeled and numbered as releases, IE if this does ok, next will be Alpha 1, or experimental V0.2, etc.
Added OC code
Experimental V0.2 10-05.12
Second release for testing. Does now include the CODE for voltage control, but is not enabled yet. I didn't enable it to help prevent issues with instabilities from UV being confused with kernel issues. GPU OC is active, 320/400 MHz 2D/3D. Does not play well with ICS, CM10 use only.
Experimental V0.3 10-06-12
Rewrote alot of the upper end speed/voltage/timing code from 1.508 to 1.472, VT, haptic feedback fix? Proved unstable to the point of being unusable. Pulled.
Stable V0.4 10-06-12 "Caspar"
Reverted to V0.1 OC code after the disaster of V0.3. Left out voltage control code, implemented GPU OC as previous in V0.2, VT is enabled, possible haptic fix (not likely). Governors and IO schedulers should remain as before, min/max settings should remain as before. 1.5 is likely still broken.
Experimental V0.5e "Melchoir" 10-18-12 ICS only
All new CPU Speed tables, overall max is lowered from 1.5 which froze to 1.478, and more speeds in between. Those who used the Shiva Kernel will be familiar with the speed range. GPU OC is bumped up 20mhz in 2D/3D. SmartassV2 code added. The kernel has branched since V0.4 and is now a JB and an ICS specific design, one doesn't work for the other anymore, sorry to say. "Melchoir" is the ICS branch kernel, "Balthesaur" is the JB branch kernel which is included in the CM10/Kuroikaze builds.
"Melchoir" V2.4 ICS
Experimental support of CIFS and slight config changes to maybe improve kernel performance. Branch from "Caspar" and includes speeds, governors, IO schedulers and any previous bugs. 1.5Ghz is likely still broken.
"Balthesaur" V2.75 Linaro JB NON OC
Experimental fixes for ExFat corruption issues.
No CPU or GPU OC
Built with Linaro 4.7 toolchain with some optimizing tags turned on
Retains Governors and IO Schedulers from the OC version
Instructions
Download the zip from the link given below
Boot into CWM
Wipe cache
Wipe dalvik cache
Install from zip
Install the kernel zip
Reboot
First boot will take longer as the caches are being rebuilt
Let kernel settle for 10 minutes
Reboot
Let kernel settle for 5 minutes
Begin normal usage and setting up
System Tuner has been reported to work with great success.
Downloads
Experimental OC 1 | Mirror
*note* 1.5Ghz is unstable, please limit to 1.4Ghz for testing.
Experimental V0.2
*note* 1.5Ghz is unstable, please limit to 1.4Ghz for testing. Only for CM10.
Experimental V0.3
*note* completely unstable, pulled.
Stable V0.4 "Caspar" ICS
*note* 1.5Ghz is unstable, please limit to 1.4Ghz for testing.
Experimental V0.5e "Melchoir" ICS
*note* does not boot. See change log for information. ICS only kernel. Please have V0.4 zip handy in case this kernel goes ballistic or doesn't boot, etc.
Experimental V2.4 "Melchoir" ICS
*note* likely retains the 1.5GHz lockup issue.
Balthesaur V2.75 Linaro No OC JB ONLY
Non OC kernel by request. Built with Linaro and current 2.75 source. For use with Jellybean ROMs only. Retains IO Schedulers and Governors, just no CPU or GPU overclock at all. Possibly includes fixes for exfat corruption (planned for U6, but may as well)
Revert kernel
Favum ICS kernel | Mirror
Use this in CWM, same as before, to restore the boot.img and modules for Favum ICS, it may work for other Official based ICS, may not, untested.
Notes and Updates
Mirrors added, V0.1 initial release
V0.2: GPU OC 320/400 MHz 2D/3D. Does not play well with ICS, use only with CM10.
Kernel naming and what they mean:
As the kernel development for Jellybean gained momentum, changes to the kernel source and drivers made the kernel no longer compatible with BOTH ICS and JB, so a new branch needed to be built, one for each android version.
Caspar = The trunk kernel, the first base which all other kernels are built from, contains the original OC settings, governors and schedulers, but not much else, pretty stock.
Melchoir = The First branch, this is for ICS only, and is slightly more updated then the JB kernel, but not by far, is pretty stale development wise while I work on the JB kernel.
Balthesaur = The second branch, this is for JB only, and is the more updated and recent and heavily developed kernel by far.
Each kernel release is still compatible with ANY ROM, however it MUST be of the proper android version, Meclchoir should be flashed only to ICS and Balthesaur should only be flashed to JB. Caspar, should you choose to use it, is ICS only as well.
Do not flash these to other android versions, including Honey Comb, they may boot but they will certainly not function correctly.
FAQ
Q: How does this work with any ROM?
A: Installs by taking apart the current boot image, replacing the kernel binary, repacking then reflashing the boot image, and copies the matching modules into your system/lib folder. It keeps the existing ramdisk, which is why it works in between both ICS and JB.
Q: Where did you get your source changes from?
A: Source changes are coming from ezTerry and Godmachine, with guidance from Godmachine. Changes by ezTerry may come from other places, however I can not verify that, and its from his github.
Q: Is this included in any ROM?
A: Yes, this kernel is included with my CM10 builds, including Kuroikaze-Thrive
Thanks go out to:
First off, godmachine / linux society! We've had our spats (rather, I've had mine) however his guidance made this possible.
ezTerry: for giving us the first modded Acer Iconia kernels, also basing some of this work on his work on ezT20 kernel.
Da-pharoah for as always encouraging my work and to try new things.
tybar over at thriveforums.org (he may also be here?) for his work on CM10 and supplying the initial source this began with.
The rest of the guys pitching in over there!
Very excited to see a kernel! Could you possibly post a stock kernel as well that can be flashed back to if needed as this gets refined? Just trying to cover all contingencies.
Sent from my AT100 using Tapatalk 2
wigginst said:
Very excited to see a kernel! Could you possibly post a stock kernel as well that can be flashed back to if needed as this gets refined? Just trying to cover all contingencies.
Sent from my AT100 using Tapatalk 2
Click to expand...
Click to collapse
That depends on the ROM being used so no, I hadn't planned on it. I probably could but its per ROM which is quite a few lol
Sent from my Galaxy Nexus using Tapatalk 2
Ok. Was just thinking of a backup in case. Flashed it to favum and letting it settle right now.
Sent from my PG86100 using Tapatalk 2
On jbreezy darkside ROM v2 he modified the ram disk a bit would that interfere with installing this kernel?
Edit: nevermind you said it keeps the existing ram disk
Could you make a revert for his darkside ROM? Sorry for being a pain
Sent from my AT100 using xda app-developers app
stevie13.xo said:
On jbreezy darkside ROM v2 he modified the ram disk a bit would that interfere with installing this kernel?
Edit: nevermind you said it keeps the existing ram disk
Sent from my AT100 using xda app-developers app
Click to expand...
Click to collapse
Yeah unless something is different with the kernel binary as well, which I doubt, it shouldnt cause a problem.
As far as I know its the first kernel from source for ics so I don't think any issues will come up.
Edit: I'll try to get a revert zip up for dark side as well, the favum won't work, different ramdisk I think.
Sent from my Galaxy Nexus using Tapatalk 2
Are u saying I can use this kernel on my phone or some specific phone only?
ramoneC said:
Are u saying I can use this kernel on my phone or some specific phone only?
Click to expand...
Click to collapse
For the device this forum is for? In other words its for the Toshiba thrive 10" tablet. Flashing this on anything else can lead to no boots or even bricks. Its for any ROM, not device.
Sent from my Galaxy Nexus using Tapatalk 2
I nearly was going to brick my phone /: maybe not cos your updater-script might have been aborted but the main thing was I could not download it because of some sqlite error
God damn goo.im I've been waiting for an oc ics kernel for a minute.. A long minute
me checking the site every minute isn't helping probably either
Can I flash a kernel for similar phone which has similar buttons and screen resolution and sensors but different board base and hope it works?
ramoneC said:
Can I flash a kernel for similar phone which has similar buttons and screen resolution and sensors but different board base and hope it works?
Click to expand...
Click to collapse
Generally speaking, no. What device are you talking about?
Sent from my Galaxy Nexus using Tapatalk 2
old galaxy s5830 < wont matter if it bricked
ramoneC said:
old galaxy s5830 < wont matter if it bricked
Click to expand...
Click to collapse
This kernel won't flash let alone boot on that lol
Sent from my Galaxy Nexus using Tapatalk 2
I have decided to buy googles phone henceforth so I wont have to worry about updating
stevie13.xo said:
God damn goo.im I've been waiting for an oc ics kernel for a minute.. A long minute
me checking the site every minute isn't helping probably either
Click to expand...
Click to collapse
Mirrors are up.
Boeffla Samsung Kernel by AndiP
Ported and compiled by Hbohd and P$T
For i9305
Introduction
Note: The 4.x kernels are only for Samsung based 4.1.x roms!!! Do not install it on CM or AOSP based roms!!!
The 5.x kernels are only for Samsung based 4.3 roms!!! Also do not install it on CM or AOSP based roms!!!
After ausdim's contribution to porting variety of kernels to our phone, I am here to continue his work (he won't maintain it any longer because he simply doesn't own this phone now). Updates will be made as soon as Andi will push them to github.
Here is original thread of i9300 boeffla kernel - CLICK
Here is thread with boeffla ported by ausdim - CLICK
Info
Kernel is compiled using Linaro 4.9.1 with some required changes for our i9305:
No FM radio
No CMA_DMA
No flash and load in Boeffla App
New 'Hbohd preset' and 'PST preset' which are just our everyday use settings.
New 'Hbohd' and 'PST' equalizer preset - just our favorite.
Apart from that, everything is same as in i9300 version.
Please for any questions problems or anything else ask here and not on I9300 thread.
Credits
P$T (for helping hand with compiling and endless patience and time)
Ausdim (basing on his work and he always gives helping hand)
Yank (his endless patience and knowledge to help with any issue)
AndiP (for kernel base and another kind help)
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in CWM recovery and safely store your personal data before you flash a new kernel.
Source:
Here it is, github link! - CLICK
5.2 STABLE compiled with linaro 4.8.3 toolchain -->HERE
Newest version 5.3-beta7 compiled with linaro 4.9.1 toolchain (new ramdisk NE4) --> HERE
Camera bug info:
It appears that some people (like me) have problem with camera. In exactly THIS situation: do full wipe, flash sammy rom+boeffla kernel, reboot and launch camera. Effect? Camera closes with "camera failed" popup.
Possible solution:
1. Read this thread and follow steps --> click
2. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, then reboot to recovery and flash my ported kernel
3. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, grab file (SlimISP_XX.bin, where XX differs between phones) from /data/cfw/ and backup it where you want. Then if you can always copy it to /data/cfw if your camera doesn't work with my ported kernel. (ATTENTION: Unfortunately this file does not always appear - still don't know why )
Possible explanation, my own research:
I found out that people with ZD and GD will have camera working always. Why? Because these (SlimISP_XX.bin, where XX differs between phones) files are packed within kernel (zImage exactly) and ONLY THESE two are provided by Samsung in their opensource release... Interesting, isn't it? For example, I have GH version, which I may add to zImage manually, however adding more of them breaks the size limit for boot partition, so it's impossible to have all these versions together. However, stock kernel somehow has them, don't know how because zImages aren't extractable.
And just to confirm my theory, I've compiled a kernel with mine version of camera firmware, made full wipe, installed sammy rom+my kernel, rebooted, launched camera and voila - it worked
Thus, we has to live with this bug unless Samsung do something about it or someone else proves me that I'm wrong
Hbohd said:
I compiled it after adding my own script for zzmoove 0.5 settings, so you all have them in boeffla app. Therefore I need to explain what i changed (it is just for testing purposes, I don't know yet if it is better/worse etc).
I enabled early demand (new feature from 0.5 version):
And also enabled lcdfreq scaling with standard values:
Click to expand...
Click to collapse
Installed let see how it goes...
Good work
Tank's
Sent from my GT-I9305 using Tapatalk 2
Hbohd said:
I compiled it after adding my own script for zzmoove 0.5 settings, so you all have them in boeffla app. Therefore I need to explain what i changed (it is just for testing purposes, I don't know yet if it is better/worse etc).
I enabled early demand (new feature from 0.5 version):
And also enabled lcdfreq scaling with standard values:
Click to expand...
Click to collapse
Thanks.
Do you have any link or something where we can read about zzmoove governor tunables? I was searching, and searching and nowhere have I found a good explanation of all parameters.
I should probably look into sources you just gave a link for, but I am too tired atm.
Edit:
Oh that wasn't link to sources, but it doesn't matter, there has to be one somewhere in Boeffla thread.
Sent from my GT-I9305 using Tapatalk 2
My 'sources' are only one file - defconfig. The rest is completely same as Andi's sources
And for any explanation of zzmoove configurables - there is some documentation, quite well explained: https://github.com/andip71/boeffla-...48257af1b13/drivers/cpufreq/cpufreq_zzmoove.c
Cheers
Thanks for the port.
Over night I find this one better on battery than the last port. See how it goes with a bit of heavy usage today.
Sent from my GT-I9305 using Tapatalk 2
Hi Hbohd. So, let me see if I get it: this port will no longer be updated, and you are now the good guy that will continue to update Boeffla kernel to our beloved I9305?
kazoum said:
Hi Hbohd. So, let me see if I get it: this port will no longer be updated, and you are now the good guy that will continue to update Boeffla kernel to our beloved I9305?
Click to expand...
Click to collapse
Yes, you are completely right Ausdim has even mentioned in his thread that he no longer owns our device (i9305) so I decided to ask for his permission to continue his job here !
I am quite in love with usage results of Boeffla kernel, therefore you do not have to worry about frequent updates
Hbohd it will continue the port of the boeffla kernel since i moved to the i9505.
Also i see Andip make some changes to the boeffla sound driver so it will work better.
Thank's
After 1 day with new kernel I can say the battery improve are the best an till now. Great job
Sent from my GT-I9305 using Tapatalk 4 Beta
Nice.. good job man..
Sent from my GT-I9305
Hbohd said:
Yes, you are completely right Ausdim has even mentioned in his thread that he no longer owns our device (i9305) so I decided to ask for his permission to continue his job here !
I am quite in love with usage results of Boeffla kernel, therefore you do not have to worry about frequent updates
Click to expand...
Click to collapse
Well, I'm sad that a developer leaves this phone, but it is awesome to know that Boeffla will continue to be ported to I9305! The best part is the frequent updates Thumbs up!
I'm gonna try your port and will say something later.
beta6
I found 2.12beta6 very smooth on my wife's s3 (i9300) - is it possible to have beta6 for our device? (i9305)
dyy said:
I found 2.12beta6 very smooth on my wife's s3 (i9300) - is it possible to have beta6 for our device? (i9305)
Click to expand...
Click to collapse
What if I told you...
Beta7 is better than beta6
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
kazoum said:
What if I told you...
Beta7 is better than beta6
Click to expand...
Click to collapse
Beta7 is with zmoove 0.5 which is unstable at the moment - beta6 with 0.3
Besides beta6 is so great on my wife's phone that I'm afraid of changing anything
Sent from my GT-I9305 using Tapatalk 2
!crazy said:
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
Sincerely, I haven't experienced any random distortions of sound, everything works great. Obviously, if you raise headphone or speaker volume too high, it may be distorted, but it is understandable.
Or did you want to mention the problem with distorted/freezing/stuttering audio on screen-off? That was discussed and it might be caused due to too low screen-off frequency or too high sampling_rate and sampling_rate_sleep_multiplier. If it's the problem, try to change to zzmoove-optimised as it has this values changed a little bit.
About Perseus' screen calibration settings... As for now, introducing such thing would require adding multiple scripts to support variety of configurations for it (in boeffla app), change app to stweaks (which is quite tough task) or wait for new app which will come in some time, made by Andi (and in my opinion, will let us easily configure what we want).
What's more, personally I liked these calibrated colours, however, original colours also seem good to me So nowadays, I do not need it, although I might look at it in my free time and see what can I achieve
dyy said:
Beta7 is with zmoove 0.5 which is unstable at the moment - beta6 with 0.3
Besides beta6 is so great on my wife's phone that I'm afraid of changing anything
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
The fact is, that ausdim released beta4 or 5, I don't remember exactly, and then was my release beta7. And we somehow skipped beta6, you are right! However if I were you, I wouldn't take zzmoove 0.5 as 'unstable'. It introduces a great deal of new configurables that, I suppose will be really beneficiant in the future (when we all will learn what they mean ).
Version 0.5 is ONLY unstable when you are changing governors frequently. Otherwise, it is really efficient and bettery-friendly one (same as 0.3). In addition, it's my beloved governor since its start
Furthermore, new betas always consist of other updates (like Linux kernel upstream to 3.0.82, fixes, optimizations) so it is always worth to use the newest one!
As for now, you may stay with your actual beta version or wait for next update. Andi is testing comparison between zzmoove 0.3 and 0.5 right now, so he haven't pushed any sources, therefore I can't release any new update We are all impatiently waiting for the results i think!
Anybody experienced a problem when the phone CPU is stuck in the max CPU frequency when the phone is plugged in to the PC using USB connection?
I'm using zzmoove battery profile..
Sent from my GT-I9305 using xda app-developers app
inzomnia said:
Anybody experienced a problem when the phone CPU is stuck in the max CPU frequency when the phone is plugged in to the PC using USB connection?
I'm using zzmoove battery profile..
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Have the same problem, no matter the governor i choose.
I try zzmove battery and pegasusq boeffla battery saving
!crazy said:
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
I had this issue with boeffla but only when i used rxtreme rom, i never have it with ripper rom!