Kang-aroo V2.0 1/27/2014
WHAT IS IT?
A kernel built from source and released as a daily driver, based on kangs of other proven code which has been known to be both useful and stable. It's name implies that this work is the hard work of others, not mine and I do not claim credit other than updating, merging it, and building it. I do this as a hobby and because I support open source... I have no donate button but will assist you in any way I can. Please just ask any question in the thread no need for PM, even simple questions are ok.
FEATURES:
-OC of CPU up to 1600mhz, Oc of GPU as high as you dare, with trickstermod
-mpdecision from showp1984, and custom ondemand governor (default)
-OTG hostmode and simultaneous charging/fastcharge, switchable
-hotplug DAC support, ALSO NEEDS ROM patch, more info in 3rd post
-Smartmax governor via Oxydo kernel
-ROW,CFQ,DEADLINE, and new BFQ IO scheduler implemenation per mkernal
-firm sleep rtc driver, switchable
-support for most common usb wifi adapters, including rt2800(rt3070), ath9k, rtl8187, rtl8188, rt73, so many i forget, can add any requested if they're not there
-support for all easycap devices with backported drivers from linux 3.4 via linuxtv media git, see 3rd post
-kexec multirom support as a primary and or secondary rom
CREDITS/SOURCES:
*kang of bricked kernel- uses showp1984's custom mpdecision and custom ondemand governor, as well as his implementation of CPU/GPU OC
https://github.com/showp1984/bricked-grouper-3.x
*hotplug dac and otg fastcharge, firm sleep from usbrom
https://www.github.com/mehrvarz
*Kexec support from Tassadar
https://github.com/Tasssadar?tab=repositories
*smartmax governor from sgt. meow
https://github.com/souljaboy11792/oxydo-grouper
*BFQ IO scheduler, all other IO scheds updated
https://github.com/metallice[url]
.../github.com/lostdeveloper/bricked-grouper-3.x
DOWNLOADS
V2 with all modules, SELinux disabled:
http://d-h.st/LZq
V2 minimal install, just tun and cifs modules, SELinux disabled
http://d-h.st/H5U
XDA dev crue has taken the time to make an advanced power manager. With it you can control fixed install, firm sleep, and other kernelnsettings as well as control firm sleep and change the timers for audio focus and deep sleep. I HIGHLY recomend it for this kernel and/or oxydo. Latest version:
http://forum.xda-developers.com/showpost.php?p=49854315&postcount=256&nocache=1&z=9045582152903080
http://forum.xda-developers.com/showpost.php?p=49814629&postcount=242
*****new releases can mean undiscovered issues. If you have any, please let me know so they can be fixed...ENJOY!!!!!!
__________________________
SELinux enabled: I forgot, give me a day or two, Ill get one up. this build still just changes zimage, so works on kitkat or JB4.3.
__________________________
CHANGELOGS:
Kang-aroo V2.0
1/27/2014
bugfix: trickstermod thinks the minimum touchboost freq of 910mhz is the minimum system freq....NOT ANYMORE!
bugfix: tons of dmesg errors from touchboost in franco's interactive governor...governor pulled for now
bugfix: laggy and slow aroma installer which causes black screen from twrp screensaver...GONE!!!
NEW:
-completely replace old GPU OC interface with new one from franco kernel. Users can now set GPU OC right from trickstermod, and go as high as they want.
-cgroups timer slack
-BFQ IO scheduler from mkernal, all others updated
-smartdimmer as implemented by mkernal
Kang-aroo v1.2
1/04/2014
-built wifi back into kernel, no more module
-removed init.d script for hostmode controls, too many issues, use gscript or terminal instead, more info 3rd post
-removed governor option from aroma installer, still can't solve bootloops
-Now has support for all easycap devices, tho improvement is still needed, see 3rd post for more info
-set SELINUX to disabled for now to allow cifs mounting, solve some other issues
-smartmax from oxydo, and interactive for N5 from franco kernel, use trickstermod to change, smartmax is feeling very nice
whats coming:
support for r820t dvb sticks, and hopefully also support atsc tuners and US OTA TV.
*************************************
FULL build with 307 modules:
http://d-h.st/fnw
Kernel and just cifs/tun modules:
http://d-h.st/YHM
*************************************
______old changelogs________________
Kang-aroo kernel 1.1 (12/12/2013)
-Fully updated to 4.4mr1, minus the battery driver changes.
- removed em28xx.ko for now, its not working
- smaller size, will eventually build wifi back in, but its still in module form to save size
-tested with purity rom 12/8 release, wifi is now working on this rom, and should be for all 4.4 roms now.
-Also tested purity rom with ART, reboot was slow, but subsequent reboots are taking about 20 seconds from the multirom boot screen, so all seems normal for kitkat now. ART was switched on BEFORE adding gapps, if it makes a difference.
-still running fine on smoothrom 5.3, which is android 4.3, but I will leave the older build up in case these updates cause any issues for older roms.
- everything else is the same, but DAC hotplug mod on the rom side kind've needs to be done in the source before ROM build to ensure functionality.
______________________________________________
Kang-aroo kernel 1.0:
"Kang"ed from proven sources
*Tested with smoothrom 5.3, android 4.3.1, should work with 4.4, will be updated for 4.4.
*multirom kexec code.....credits to tassadeur.
*CPU OC to 1.6, GPU OC to 484, set during install or with trickstermod
*OTG+fastcharge simultaneously, requires otg y cable for power
*USB DAC support, with hotplug (please read below)
*Usb wifi support: ath9k,rt3070,rt73,rtl8188, others
*over 200 remote controls
*easycap dc60, also included is the em288 module which supports the newest genuine easycap device, but this is a work in progress
*usb webcam as a rear system camera
*media playback after deep sleep, even with externally mounted drives
USB webcam as a "rear" camera:
Add a usb (uvc compatible) webcam as the tablets "rear" camera. The webcam must be plugged in at boot time, but is hotpluggable after that. It will apear to camera apps as a built in rear cam, the only downside to this is that the image will be off 90 degrees if you have the tablet in landscape mode, because it doesnt know that the cam is not really built in. I hope at some point to fix this, but for now i just use my webcam mounted on its side.
http://d-h.st/x5t
Autoplayback after system sleep for mounted drives
This mod is not mine, the source is here:
https://github.com/clarejor/android_packages_apps_Apollo
This is a modded version of apollo that allows autoplayback even from otg mounted drives after waking the tablet from sleep. It is a link to the authors direct download link.
https://docs.google.com/uc?export=download&id=0B8Al2jKfBcTiNUtSdkQtaEZ5MlE
DAC info:
To support DAC hotplug in your rom, you must apply a patch based on code at github.com/jacknorris. this one works for me:
http://forum.xda-developers.com/showpost.php?p=48720356&postcount=89
thanks -crue- !!!!!!
If you need, you can go into the "patches" folder and rename to 4.3,4.4.2, etc. as you need, it still works.
EASYCAP info:
These drivers were added with help from a russian thread which I was using google translate:
http://translate.google.com/transla...l=en&u=http://pccar.ru/showthread.php?t=19390
http://translate.googleusercontent....=17970&usg=ALkJrhiZTqApR8tUiNrNMyIEIk2qBxWobg
But there is easier english info about it here:
http://rootzwiki.com/topic/39717-kernel-module-cm-101-easycap-module/page-35
*the script I use for loading the modules is here:
http://d-h.st/z2g
it needs to be pushed to system/etc/init.d AND have the right permissions (RWX,R-X,R-X I think) ....... or just use it to see which modules need to be insmodded.
*and the program I used to view the device is here:
http://rghost.net/51160971
keep in mind, I tested with the cheapest one on fleabay, 5 bucks shipped and it works, but when I tested with my real EZCAP the picture is much better. see below for the results...and...read the whole thread I linked. the guy is workin like crazy on it, and it will only get better I think.
is multirom 'kexec' support included?....thx
Hi
This Kernel looks the business.
Can u tell me though is it overclock-able?
bonzer2u said:
is multirom 'kexec' support included?....thx
Click to expand...
Click to collapse
yes, I forgot, the proven tassador code is there....it DOES multiboot.
Sharpy1964 said:
Hi
This Kernel looks the business.
Can u tell me though is it overclock-able?
Click to expand...
Click to collapse
yes, CPU up to 1.6, and GPU to 484, options can be set with aroma installer, or later on with trickstermod.
I'm going to use the USB otg charging and DAC bits. Thanks.
Sent from my Nexus 7 using Tapatalk
sgt. meow said:
I'm going to use the USB otg charging and DAC bits. Thanks.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
excellent. I want to use your d2w code......gotta work out some wakelock issues tho. If you look at the main commit.....you'll see its not that many files for the DAC stuff. where you need to pay attention is the defconfig...... as usbhost is actually NOT set.
Also, there are about six or seven commits to bricked kernel from Timur mehrvarz from a few months back. All of them were cherry picked in order, and you'll need those cherrypicks first before you pick mine. just ask if you have issues..... more than happy to help.
I'm working on a sysfs interface system to make s2w completely configurable. I plan to work on touchwake as well later. I'll start tomorrow.
Sent from my Nexus 7 using Tapatalk
Mate, I added the USB hostmode patches, but now USB OTG doesn't work. I'm a complete noob to this (only adding it because of user request); any help is appreciated.
The same otg cable is used (not y cable). It worked before, but now it's borked.
Never mind. Turns out I just had to disable Fixed Install in sysfs.
sgt. meow said:
Mate, I added the USB hostmode patches, but now USB OTG doesn't work. I'm a complete noob to this (only adding it because of user request); any help is appreciated.
The same otg cable is used (not y cable). It worked before, but now it's borked.
Never mind. Turns out I just had to disable Fixed Install in sysfs.
Click to expand...
Click to collapse
Yea......I meant to tell you......you can change the default in the source. Also, as I'm sure you know, you can look at the init.d script I made for making changes stick on reboot. Of course, this is really just: 'echo "1" > /sysfs/usbhost/usbhost_fixed_install'
It's better to have found out on my own though. Thanks for all your help.
Thank you
Wow Increadible! Please keep updating it
SlavPala4a said:
Wow Increadible! Please keep updating it
Click to expand...
Click to collapse
no prob, 4.4 ipv6 updates coming soon, the "battery" driver updates I'll prolly skip.
So i've just downloaded & installed this kernel. Mainly for it's USB DAC feature...dying to have this since 4.2.2 kernels.
Sadly, not working out for me as audio is still routed to internal speakers, plugged in DAC before boot.
Wifi too cannot be turned on. Stuck at 'turning wifi on'
Came from franco r76 on purity 4.4 (2/12/13 build)
It's recognized on boot tho, and doesnt crash the table when hotplugging.
Also, i did not install the 'hotplug mod', i was testing this without it.
[ 4.442281] usb 2-1: New USB device found, idVendor=08bb, idProduct=2704
[ 4.442604] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4.442779] usb 2-1: Product: USB Audio DAC
[ 4.443084] usb 2-1: Manufacturer: Burr-Brown from TI
[
Click to expand...
Click to collapse
and here's the whole last_kmsg attached...
andrew9292 said:
So i've just downloaded & installed this kernel. Mainly for it's USB DAC feature...dying to have this since 4.2.2 kernels.
Sadly, not working out for me as audio is still routed to internal speakers, plugged in DAC before boot.
Wifi too cannot be turned on. Stuck at 'turning wifi on'
Came from franco r76 on purity 4.4 (2/12/13 build)
It's recognized on boot tho, and doesnt crash the table when hotplugging.
Also, i did not install the 'hotplug mod', i was testing this without it.
and here's the whole last_kmsg attached...
Click to expand...
Click to collapse
wifi is in module form....to help with size of kernel. ill look at log and see if it was loaded. for usb dac hotplug, the rom must also be modded via the link in op. or if u build roms, you can go to jacknorris github, and pull those changes into your source. must do both.... but ill look at log and see whats goin on. only got phone right now. forgot to mention......the aroma installer doesnt wipe /system/etc, so if u got other kernel init.d scripts, they need to be removed. if you have any wifi init.d scripts, they need to occur AFTER the wifi module loads, so jusr rename them with a 90 infront. get back to you.
ok....looked at log from phone, unless I missed it I didnt see wifi module load, make sure the init.d script is there. the dac is there....and burr brown is a nice amp, use them in my guitar effects, not ssure if rom can pass audio to dac with no mods, could be wrong. the jacknorris mod works well, and the "wiredaccessorymanager.java" or whatever hasnt changed, so you should be able to do this on upto 4.4, but ive only tried smoothrom 5.3. which is android 4.3.1.
redeyedjedi said:
wifi is in module form....to help with size of kernel. ill look at log and see if it was loaded. for usb dac hotplug, the rom must also be modded via the link in op. or if u build roms, you can go to jacknorris github, and pull those changes into your source. must do both.... but ill look at log and see whats goin on. only got phone right now. forgot to mention......the aroma installer doesnt wipe /system/etc, so if u got other kernel init.d scripts, they need to be removed. if you have any wifi init.d scripts, they need to occur AFTER the wifi module loads, so jusr rename them with a 90 infront. get back to you.
ok....looked at log from phone, unless I missed it I didnt see wifi module load, make sure the init.d script is there. the dac is there....and burr brown is a nice amp, use them in my guitar effects, not ssure if rom can pass audio to dac with no mods, could be wrong. the jacknorris mod works well, and the "wiredaccessorymanager.java" or whatever hasnt changed, so you should be able to do this on upto 4.4, but ive only tried smoothrom 5.3. which is android 4.3.1.
Click to expand...
Click to collapse
Nope, no leftover init.d scripts except a 99supersu script.
Just did a clean flash with the same rom straight to kangaroo and wifi does not work either.
Cant seem to get the jacknorris patch to work on my Win7 laptop.
ADB problem solved. It was due to ADB.exe and some of it's .dll were outdated for 4.4. Got the new files from the SDK and now ADB works.
But the patcher gives this error: Checking BOOTCLASSPATH: error: Unable to parse shell output
Appearantly the patcher has to be modified for 4.4: http://rootzwiki.com/topic/37176-mod-usb-audio-support/page-4
Also, anyone has a working 4.4 rom with this kernel combination that works internal wifi and usb dac?
Appearantly folks at CM11 got the dac bit goin for N7-2013 and N5. Not on our 2012 though. Wonder if it was a kernel change or rom framework or both... http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/3615
Support for USB Audio, 3rd most starred issue on aosp: http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars
For those wondering what's this about:
What is a USB DAC?
A USB Digital-to-Analogue Converter is a plug in USB device that converts digital bitstreams into analogue audio wave to be transmitted in the cables leading up to your headphones, speakers etc. It's a soundcard so to speak, but specializes higher quality audio output only and wont have any recording capabilites.
Why?
The DAC chip (that conversion chip) is usually of superior quality to that embedden internally on your motherboard or device. In layman terms, it converts more accurately, over a wider ranger of frequencies. Being an external device, it would be less suspectible to internal electronic noises and advance DACs have noise, jitter reduction methods, sometimes even its own clocksource. Different DACs have different sound signatures for different ears and taste.
Another advantage is that users may not need to alter the audio in the digital domain (EQ, Compressors, Volume, Effects) which induce losses due to poorly designed algorithms and the nature of 16/24-bit consumer audio. Most music today is processed in a 64bit domain over a very high sample rate, from the first souce to it's final output.
Why manufacturers dont slap one of these on the boards/device?
Simple business/economics, the Nexus 7 2012 sold 7 million devices.
A better chip may cost an extra dollar or lesser since they purchase in bulk.
Example, $1 increased cost x 7 million devices = $7 million lesser in profits!
Where is Android on USB audio then?
Usually not available on Nexus aka google-high-involment devices. Some vendors like Samsung, LG, HTC take it further and has usb audio support at least. It can be further improved with bit-perfect streams, higher sample rate with 64-bit float PCM decoding and effect processing, exlusive application access, low latency framework, DSD etc.
Comparision?
I know Windows, Linux, OSX has it, used it before.
iOS has it too. Ehem, my ipad1 could do it.
{
"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"
}
andrew9292 said:
Nope, no leftover init.d scripts except a 99supersu script.
Just did a clean flash with the same rom straight to kangaroo and wifi does not work either.
Cant seem to get the jacknorris patch to work on my Win7 laptop.
ADB problem solved. It was due to ADB.exe and some of it's .dll were outdated for 4.4. Got the new files from the SDK and now ADB works.
But the patcher gives this error: Checking BOOTCLASSPATH: error: Unable to parse shell output
Appearantly the patcher has to be modified for 4.4: http://rootzwiki.com/topic/37176-mod-usb-audio-support/page-4
Also, anyone has a working 4.4 rom with this kernel combination that works internal wifi and usb dac?
Appearantly folks at CM11 got the dac bit goin for N7-2013 and N5. Not on our 2012 though. Wonder if it was a kernel change or rom framework or both... http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/3615
Support for USB Audio, 3rd most starred issue on aosp: http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars
For those wondering what's this about:
What is a USB DAC?
A USB Digital-to-Analogue Converter is a plug in USB device that converts digital bitstreams into analogue audio wave to be transmitted in the cables leading up to your headphones, speakers etc. It's a soundcard so to speak, but specializes higher quality audio output only and wont have any recording capabilites.
Why?
The DAC chip (that conversion chip) is usually of superior quality to that embedden internally on your motherboard or device. In layman terms, it converts more accurately, over a wider ranger of frequencies. Being an external device, it would be less suspectible to internal electronic noises and advance DACs have noise, jitter reduction methods, sometimes even its own clocksource. Different DACs have different sound signatures for different ears and taste.
Another advantage is that users may not need to alter the audio in the digital domain (EQ, Compressors, Volume, Effects) which induce losses due to poorly designed algorithms and the nature of 16/24-bit consumer audio. Most music today is processed in a 64bit domain over a very high sample rate, from the first souce to it's final output.
Why manufacturers dont slap one of these on the boards/device?
Simple business/economics, the Nexus 7 2012 sold 7 million devices.
A better chip may cost an extra dollar or lesser since they purchase in bulk.
Example, $1 increased cost x 7 million devices = $7 million lesser in profits!
Where is Android on USB audio then?
Usually not available on Nexus aka google-high-involment devices. Some vendors like Samsung, LG, HTC take it further and has usb audio support at least. It can be further improved with bit-perfect streams, higher sample rate with 64-bit float PCM decoding and effect processing, exlusive application access, low latency framework, DSD etc.
Comparision?
I know Windows, Linux, OSX has it, used it before.
iOS has it too. Ehem, my ipad1 could do it.
Click to expand...
Click to collapse
So, the kernel is booting 4.4, but this ROM mod needs to be reworked a little. It seems like a ROM needs to be built with the source manually modified. Its gotta be do-able, I'm just such a fan of tabletui, that I'm not running 4.4. But I'm sure this problem can be figured out. The WiFi thing bugs the **** out of me, haven't had this issue regardless of ROM I've tried......can you look in system/lib/modules and see if "bcmdhd.ko" is there? I will go and see about 4.4 ROM mod.
well, on the same rootzwiki page you linked, there is a guy who says he used that mod on a 4.4, with a modded installer, I see that now. So, the bootclasspath errors need to be corrected, but the mod can still be done. I hate to just tell you to go ask that guy, already done that to a couple of people via PM.... Id like to see this work for everyone. ill wait to see if you found the "bcmdhd.ko" for the wifi issues, but Ill go ahead and look into making the jacknorris mod-installer work for 4.4 roms.
on second thought, the guy got those same errors, but the mod worked anyway....so it seems. See if it worked in spite of your error.
Related
2.2 released!
In the news!
Current features:
Based on Asus 9.2.1.27 WW kernelsources
Backported all Linux 3.2 USB LAN drivers (bandwidth up to 250 MBit/s! tested with a SMSC LAN7500)
ISO9660 (+Joilet), UDF, FAT12 and Apple HFS file system support (USB CD\DVD access! See notes)
Voodoo Sound support!
Turned a few unneeded kernel features off and compiled with Linaro GCC, it's smaller and boots quite a bit faster than other kernels!
Installable using your favorite recovery (tested on CWM v6.0.1.4 v2)
New versions of Tegra 2 codecs for ICS based ROMs (will be provided within a separate installable .zip)
Kernel manager application to manage loaded drivers and file system modules!
Supports almost all current ICS and JB ROMs
Compatible with:
[ICS] Asus official firmware (with root)
[ICS] Android Revolution HD
[ICS] Energy™
[ICS] Revolver
[JB] LiquidSmooth
[JB] RaymanFX's CM10
[JB] ParanoidAndroid:CM10 Hybrid
If you tested this with any other unlisted ROM, please drop some feedback!
Note 1: Some USB devices may need additional power, if so, get a Y cable from eBay so you can power a USB device using a external USB power source
Note 2: External optical drivers and floppy drives will not be mounted automatically, as Android doesn't officially support them
Note 3: CSS protected DVDs are not supported (e.g. Retail movies), due to Linux kernel limitations
Note 4: NTFS is not supported 'out of the box', please use Paragon driver from Google Play
Downloads:
https://www.dropbox.com/sh/gxi0gsl0tdfapgi/Ja19Exs4Sz
(PLEASE install Busybox 1.20.2 using one of the installer apps from Google Play, it is needed for the Kernelmanager application to function properly)
Source:
https://github.com/sander-ashwin/tf101-allinone-kernel
Please report if something does not work!!
Mounting optical drives:
1: First make sure your device is proper rooted (the "mount" command we'll use needs root)
2: Install Android Terminal Emulator from Google Play and open it
3: Type "su" and press enter, you should be asked if you would like to give root access, say Yes
4: Make a mountpoint directory, e.g. "mkdir /Removable/opticaldrive"
5: Mount your optical drive (make sure it gets enough power and something is inserted in the drive) using this command: "busybox mount /dev/block/sr0 /Removable/opticaldrive"
6: You're done! If you inserted a DVD movie, you might want to install Wondershare player or some other player that is capable of playing DVDs with menus
7: If you encounter any difficulties, please reply on this thread or send me a message
Connecting your TF101 to wired ethernet:
1: Buy a TF101 USB Host connector if you don't already have one (they are very cheap online, around 12-15 dollars)
2: Connect the adapter to your TF101, plug in your USB ethernet adapter
3: Android will display a message in the lower right corner of the screen that an ethernet adapter has been connected
4: Connect the LAN cable
5: Android will display a message that your device is connected using DHCP, you can now use internet using LAN
6: If you require manual IP settings, please go to Android's settings, there you can set manual IP or DHCP (OPTIONAL STEP)
Thanks to:
RaymanFX - for inspiring me with his own kernel, and for porting CM10
Asus - for making a pretty good device
prendomiao - for beta testing
Changelog
v1.0:
First release!
v1.1:
Removed some more junk from kernel
Now actually added new filesystem drivers!
v1.2:
Backport of Linux 3.6 I2C core
A little more cleanup of unneeded features
v1.3:
Backported all Linux 3.2 USB LAN drivers
Kernel now includes support for Voodoo Sound!
v1.4:
I2C fixes + Tegra I2C driver ported from kernel 3.6
Tweaked I2C timeout, hopefully our touchscreen won't lag anymore
(this may fix the problem that the touchscreen sometimes doesn't respond for a second, because of an I2C timeout)
v2.0:
Fixed sound
Now compiled using latest Linaro GCC 4.7.2 compiler
New kernel manager application to manage loaded drivers! You're in control, so the kernel doesn't load unneeded modules anymore!
Reverted I2C changes, as they didn't really help
v2.1:
Now compatible with ROMs based on RaymanFX's CM10
Updated BCMDHD WLAN driver for CM10 kernel
A little cleanup to synchronise both ICS and CM10 versions
Updated Linaro compiler to 2012.10
v2.2:
Added some new releases for more compatibility
i tried it. there is a little change, it is a bit speedly... i don't tried videos... but it is good good work
Thank you! Hope videos will play better as Tegra 2 is really picky with HD videos.
I'm now writing a tutorial for mounting optical discs, fortunately it's not really difficult.
but drivers must support them
Well, I included them already They are in your device if you still have my kernel installed.
But Android doesn't support automounting optical drives, so we have to mount the optical disc ourselves, until someone writes an app to do it (automatically).
EDIT: please install v1.1 if you would like to use your optical drive, as I forgot to include the drivers while compiling v1.0
Outstanding kernel. The first one I've run without SoD so far. I don't need OC, so the extra freq.'s are not important. Super quick, reliable so far for a few hours. I'll continue to report back, especially if I get SoD's. They are the bane of my existence. Keep up the good work.
Sent from my Transformer TF101 using xda premium.
Thanks! Hope you can enjoy your device again
I would like to implement overclocking though, but only if the kernel is still 100% stable for everyone.
Stil need to find out how, as I'm still learning C and kernel hacking.
The main problem at the moment is that all different hardware revisions have different issues.
Mine has touchscreen issues with a lot of kernels for example, your device may freeze when sleeping, but with a lot of testing and debugging we might be able to create a kernel that works for everyone.
When having any problems, please keep reporting!
poppajules said:
Outstanding kernel. The first one I've run without SoD so far. I don't need OC, so the extra freq.'s are not important. Super quick, reliable so far for a few hours. I'll continue to report back, especially if I get SoD's. They are the bane of my existence. Keep up the good work.
Sent from my Transformer TF101 using xda premium.
Click to expand...
Click to collapse
sainthout said:
Thanks! Hope you can enjoy your device again
I would like to implement overclocking though, but only if the kernel is still 100% stable for everyone.
Stil need to find out how, as I'm still learning C and kernel hacking.
The main problem at the moment is that all different hardware revisions have different issues.
Mine has touchscreen issues with a lot of kernels for example, your device may freeze when sleeping, but with a lot of testing and debugging we might be able to create a kernel that works for everyone.
When having any problems, please keep reporting!
Click to expand...
Click to collapse
To avoid SoDs, you need to set the lower voltage higher.
The standard voltages I'm using should be ok, but mine still SoD's sometimes.
With stock kernel as well as with other kernels, as well as with my own kernel..
Unfortunately it always happens when I'm not at home, so I can't directly debug using ADB (if possible at all).
So I can't easily find out wether it's a hardware issue, kernel issue or software issue.
If anyone has a clue about this, please reply!!
K900 said:
To avoid SoDs, you need to set the lower voltage higher.
Click to expand...
Click to collapse
sainthout said:
The standard voltages I'm using should be ok, but mine still SoD's sometimes.
With stock kernel as well as with other kernels, as well as with my own kernel..
Unfortunately it always happens when I'm not at home, so I can't directly debug using ADB (if possible at all).
So I can't easily find out wether it's a hardware issue, kernel issue or software issue.
If anyone has a clue about this, please reply!!
Click to expand...
Click to collapse
Is it SoD with dock connected or tablet alone? I'm sure you're familiar with the SD card removal thing from the dock to prevent SoD with guevors kernel? That wasn't my issue anyway, but it's just one I've heard of...
edit: you know, I didn't even think about the voltages being the issue with the other kernels... Is there an automated program to adjust voltages? I used QuickClock Overclock for my Droid X, but I'm not familiar with changing voltages on any other devices...
---------- Post added at 11:42 AM ---------- Previous post was at 11:33 AM ----------
I wouldn't MIND having OC, but I hardly use it. I got out of the OC game after watching it kill batteries on multiple phones and devices..
No one really NEEDS to OC, but for some reason people feel the need for it. The only phone I really NEEDED OC was my Droid Eris to play Angry Birds when that first came to Android... anyways, off topic...
I messed with the tablet last night, and still had no SoD.. I'll report back again tonight when I get home from work.
do you make it for jb please ?? we need it
Good to hear that the kernel works so far, hope it won't SoD.
I don't have the dock, the SoD's are just random it seems.
I'm also not working on overclocking anymore, too much files are involved which make it difficult to understand and fix.
It's also a pretty big risk, you could burn your CPU or GPU if using wrong values or something like that.
I'll leave the stock voltages and stock frequencies.
I'm now trying to fix the touchscreen issue that happens after some time. Not many people have the problem, so this won't do anything to other people.
Just updating the Linux I2C core to new 3.6 and backporting some newer touchscreen drivers.
Maybe I can also include some newer USB Ethernet drivers and backport other things.
When I implemented something that's worth trying out, I will put a new kernel version online
poppajules said:
Is it SoD with dock connected or tablet alone? I'm sure you're familiar with the SD card removal thing from the dock to prevent SoD with guevors kernel? That wasn't my issue anyway, but it's just one I've heard of...
edit: you know, I didn't even think about the voltages being the issue with the other kernels... Is there an automated program to adjust voltages? I used QuickClock Overclock for my Droid X, but I'm not familiar with changing voltages on any other devices...
---------- Post added at 11:42 AM ---------- Previous post was at 11:33 AM ----------
I wouldn't MIND having OC, but I hardly use it. I got out of the OC game after watching it kill batteries on multiple phones and devices..
No one really NEEDS to OC, but for some reason people feel the need for it. The only phone I really NEEDED OC was my Droid Eris to play Angry Birds when that first came to Android... anyways, off topic...
I messed with the tablet last night, and still had no SoD.. I'll report back again tonight when I get home from work.
Click to expand...
Click to collapse
Different JB ROMs may require different ramdisks, so it will take a little time to get it done properly and stable.
For which JB ROM would you like to use it? I might be able to take a copy of the ROM's kernel's own ramdisk and combine it with my kernel
I'm also thinking into making one for RaymanFX's new LiquidSmooth ROM, anyone interested?
prendomiao said:
do you make it for jb please ?? we need it
Click to expand...
Click to collapse
I am sorry if i sound stupid, but where do i extract files to? I have a flashing red light on my USB ethernet but no connection
Hi, does Android display a notification that you connected an USB Ethernet device?
And for which ROM are you trying?
mazimo said:
I am sorry if i sound stupid, but where do i extract files to? I have a flashing red light on my USB ethernet but no connection
Click to expand...
Click to collapse
USB Ethernet works on Android 2.3 with icon...
Ethernet doesn't have anything to do with Android at all.
The Linux kernel provides drivers which will provide Android a universal interface to control Ethernet devices.
When you plug in your USB ethernet device, the kernel will create an eth0 interface (first ethernet device interface).
Android sees that immediately and will show a little message that an ethernet device is detected.
With very old Android versions, Android doesn't really support ethernet, but some kernels do.. in that case ethernet support will be provided automatically without any notifications.
So for example, if Samsung want to support every USB ethernet device, they can, by building support into the Linux kernel.
If Asus doesn't, they don't build any support in the kernel, so the devices won't be recognised and so they will not work.
Except 1 or maybe 2 devices, the original Asus kernel doesn't support ANY Ethernet device, but my kernel supports them all
prendomiao said:
USB Ethernet works on Android 2.3 with icon...
Click to expand...
Click to collapse
new release
Everyone on older versions, please upgrade to v2.0 and try my new kernel manager application!
(Which is also my very first Android application)
Enjoy and please post feedback
If anyone would like to tryout a JB version of my kernel, please pm me!
I ran your 1.0 version, and it's great. I have MASSIVE battery life compared to before. The only issue I have noticed is with wifi reconnecting after deep sleep. It disconnects when screen is off (i verified the settings), but it has a difficult time reconnecting. I usually cycle the wifi toggle and it connects, or I click on my wifi and it connects. It's clearly not a major issue, just a little extra thought when I wake it up.
I read through and no one reported anything like this, so I figured it might be something to keep your eye out for in your later builds. I will install the 2.0 today and give feedback later. Thanks for your hard work!
Current state of 3.0 Kernel
WiFi/Thether/p2p - 100%
TouchScreen - 100%
Video Codec/hw 720p/ION stuff - 100%
Display/DSS - 100%
Phone/3G data - 100%
Sound/FM-Radio - 100%
F2FS support - 100%
GPU OC 266mhz - 100%
Bluetooth - 95%
USB - 98%, otg bugged.
Sensors - 98%, Need test all sensors, looks like all sensors works
Camera - 85%, Preview/Photo(Red have random problem)/Panorama works for both lenses. Video rec not work yet.
Overclock CPU- 0%, not implemented.
For CM10,10.1,10.2 < 07.11.13 users:
To install KitKat, need update recovery. Do not forget reboot, after install recovery.
http://defy.bytekiste.de/cm11-nightly-defy+/update-recovery.zip
Tips:
Do not format System and Cache to F2FS!!!
1. To use f2fsl "/system/bin/mkfs.f2fs /dev/block/mmcblk1p25" or format via TWRP (Advanced wipe menu).
2. To restore ext4, in recovery unmount data, mount system, and do via adb shell /system/bin/make_ext4fs /dev/block/mmcblk1p25 or format via TWRP (Advanced wipe menu).
3. If you have 0 bytes free bug, reformat data to f2fs or ext3/4.
4. 1.1 Ghz can be enabled in performance settings.
Click to expand...
Click to collapse
If you liked this project, you can donate
Donate to Quarx
PayPal: [email protected]
---------------------------------------
Donate to Blechd0se
PayPal: [email protected]
Click to expand...
Click to collapse
Download: http://quarx2k.ru/index2.php?dir=buildbot/roms/defy-cm11.0-3.0
Sources of kernel availabe here(branch p-android-omap3-3.0): https://github.com/Quarx2k/jordan-kernel/tree/p-android-omap3-3.0
Changelog:
17.11:
Added timer slack controller
Added dynamic fsync
Added proportional rate reduction for TCP
Added opensource camera driver (mt9p012)
Added syspanic driver for panic_daemon
Added sync framework (together with ION its part of androids graphical "project butter")
Switched to SLUB allocator
Enabled ram console Support
Synced binder to mainline version (~3.10)
Fixed reboot while incoming or outcoming call (fix proximity sensor in general)
Many small performance patches and fixes for better android support all over the place
Logs or it didn't happen! If you want to report a problem, be sure to post a log file!
Here is a small guide when we need which log file and how to get it.
Old Changelog;
Added new extra_free_kbytes tuable (4.4 compatibility)
Added our Interactive Governor from 2.6.32 for additional performance
Added a basic display control driver
Added a dynamic writeback control interface
Enabled cgroups for memory (4.4 compatibility)
Enabled deadline and changed tunables to the same as on 2.6.32
Enabled xattr and fs security for ext3/4
Patched up trim (ext3/4) to the latest mainline version
Switched to XZ compression for a smaller kernel image
Reclaimed some RAM from logger and vram
*Fixed the wakeup delay and the "funny" screen on resume
TODO:
Add Overclock driver
Fix kpanic with pvr and dss (solved?)
Fix sleep problem
How To Build
Code:
git clone https://github.com/Quarx2k/jordan-kernel.git
cd jordan-kernel
git checkout --orphan p-android-omap3-3.0
git pull https://github.com/Quarx2k/jordan-kernel.git p-android-omap3-3.0
export CROSS_COMPILE=/path/to/your/toolchains/arm-eabi-4.6/bin/arm-eabi-
export ARCH=arm
make mapphone_defconfig
make -j12
Sys-Values explanation;
Let me explain some of this features a little bit. 3.0.8 offers completely new opportunities to do some magic stuff.
One thing i developed a while back ago is a dynamic writeback driver with a sys-interface. It uses the earlysuspend kernel api
to flush dirty pages more frequent when in suspend, while display is on it avoids it to give a more fluid user interface.
Can be controlled via the following command;
echo 1 > /sys/devices/virtual/misc/writeback/writeback_enabled
(1 for enabled = default, 0 for disabled)
Click to expand...
Click to collapse
Also new; a basic display driver! As i tried to fix some things in our dss driver i noticed that we have different panel configurations.One is for all defy green and one for defy red lense users. I exposed those values to user space so that they can be changed. The
new default one are those, which are used on the red lense defy. In theory there could be 256 values (0-255), however could only find the
following as useful. This is not the final gamma control i wanted to have, but at least it gives some control. If someone knows the proper
addresses for gamma values, i can add them too
echo xx > /sys/class/misc/display_control/display_brightness_value
(0 will set the screen to almost 0,
9 will set the screen to some kind of blue-washed colors,
31 will set the screen to more warmer colors = default)
Click to expand...
Click to collapse
In order to run 4.4 more fluid, google made a guide and also published some recommended patches. One of them let you change
the VM's behavior to have a minimum amount of free memory. Also controllable over a interface;
echo 8192 > /proc/sys/vm/extra_free_kbytes
Click to expand...
Click to collapse
8192 means 8 MB of free ram (in any case).
Thanks for this information
Gesendet von meinem Nexus 4 mit Tapatalk 2
If I may ask, @Quarx and @Blechdose: which one of these items are the hardest to solve at the moment?
a separate thread was really needed for 3.0.8 kernel.
thank u quarx and Blechd0se
matiasrey said:
If I may ask, @Quarx and @Blechdose: which one of these items are the hardest to solve at the moment?
Click to expand...
Click to collapse
I am guessing it's the Camera?
Honestly, i think its time to stop working on the 2.6.32 kernel and focus on 3.0.x, looking as an atrix user, its definetly the best choice devs could do. Hehe
Sent from my LG-E975 using Tapatalk
Once again, thanks!!!
@Quarx @Blechd0se About the camera... Quarx, you asked in a post somewhere about our opinions on whether you guys should try to set it up with an open-source driver or with the old Moto driver. Maybe you could tell us what would be the advantages and disadvantages of which one and we could even vote if you want us to?
I'm guessing that we could get more out of the camera with an open-source driver, but it would be harder to set-up than the Moto driver?
niksy+ said:
@Quarx @Blechd0se About the camera... Quarx, you asked in a post somewhere about our opinions on whether you guys should try to set it up with an open-source driver or with the old Moto driver. Maybe you could tell us what would be the advantages and disadvantages of which one and we could even vote if you want us to?
I'm guessing that we could get more out of the camera with an open-source driver, but it would be harder to set-up than the Moto driver?
Click to expand...
Click to collapse
its a 5mp camera, so we should go for the old moto drivers, easiest stuff to do right?
Once it works with open source driver for camera, free forever...
Sent from my Nexus 7 using xda app-developers app
I shouted "YES!!" out loud when I saw the commit about headset and microphone fixes! *edit* But the call speaker maybe isn't fixed just yet :/ Still, gotta try the new build when it shows up ^_^
(that's this one - https://github.com/Quarx2k/android_...mmit/8f5a44ca04ba1c005cb1ac2409639b62f6260d4e )
Combined with Blechd0se's stability fixes (especially this one that fixes the "deep sleep death" - https://github.com/Quarx2k/jordan-kernel/commit/f6b6de228a09f46ab7d6eff70f9225f88e7d3515 ) the next build is going to be very usable imho
niksy+ said:
I shouted "YES!!" out loud when I saw the commit about headset and microphone fixes! *edit* But the call speaker maybe isn't fixed just yet :/ Still, gotta try the new build when it shows up ^_^
(that's this one - https://github.com/Quarx2k/android_...mmit/8f5a44ca04ba1c005cb1ac2409639b62f6260d4e )
Combined with Blechd0se's stability fixes (especially this one that fixes the "deep sleep death" - https://github.com/Quarx2k/jordan-kernel/commit/f6b6de228a09f46ab7d6eff70f9225f88e7d3515 ) the next build is going to be very usable imho
Click to expand...
Click to collapse
Yes Quarx is doing a very good job here, still struggling with a last few bugs. Anyway, its progress! Also the huge battery drain should be fixed,
i disabled kmemleak. 3.0 is such a nice base to work with, no need to do hacky things, it just works out of the box.
Next version will have timer_slack controller (its working perfectly). Also many fixes for crashes and memory leaks.
One big thing is still the display. Although wakeup delay is gone for me, dss/pvr crashes sometimes. Its very random.
Also overclocking has two sides; on the one side its much easier to understand, on the other side it doesn't work as expected (can't overclock
to 1200mhz for example). But we have finally a nice voltage/frequency table.
Glad to read the good news, doesn´t seem too far from a usable kernel!
Have you decided what camera drivers you´ll go for?
F* yeah! "isl29030: fix reboot of proximity sensor" commit signed off by Blechd0se
Quarx has been focusing on the in-call sound issue today, so things are looking brighter by the day
*edit* I'm guessing more and more people use the thanks button as the like button
When I wake up in the morning and read Quarx github , appear "Add Micron MT9P012 sensor driver" , so I think we can hope at an camera soon...
OTG!!
In the description it says USB: 98%, "OTG" bugged. Does this mean we can connect pen drives, mouse and keyboards to our defy with this kernel?
mayur2j said:
In the description it says USB: 98%, "OTG" bugged. Does this mean we can connect pen drives, mouse and keyboards to our defy with this kernel?
Click to expand...
Click to collapse
Yes, but with external power.
major9 said:
Yes, but with external power.
Click to expand...
Click to collapse
So it's of almost no use then..
External power? I can conenct mouse/keyboard or flash drives, no need external power.
Thread is under construction.
WARNING: There have been 3 reports so far of failure to boot after installing the Shim HAL. This sort of problem should be assumed possible at this early "Alpha level research project" phase.
Please don't install if you have stock recovery or don't know what recovery is.
Please don't install if you are nervous. Wait a while for the bugs to get worked out and info compiled.
Don't install if not confident in your technical skills.
Don't install if you might freak out if your phone gets disabled for a little while.
For bootloops or to fix or remove: http://forum.xda-developers.com/showpost.php?p=52931431&postcount=67
Post #2 has download links and instructions: http://forum.xda-developers.com/showpost.php?p=52765309&postcount=2
Since interest has ramped up quickly, I've published a 99 cent "donate" version on Play: https://play.google.com/store/apps/details?id=fm.a2d.av (Wait until the $200 placeholder price disappears, LOL.)
I'm not sure "donate" is the right word, but it's the exact same app I'm distributing and will continue to distribute for free (for at least X months to a year ??), so nobody is under any obligation to buy to get the app. Updates will be automatic via Play though.
============================================================
AudioTricks / VolumeTricks is a new kind of "audio mod" that is HAL Shim based.
At present, it can raise or lower output volume and microphone input gains digitally.
Only works on ICS Android 4.0.3 and later. AOSP ROMs such as CM11 or other KitKat very much preferred. Many stock ROMs 4.1-4.3, won't work, especially HTC.
Post 2 has download link and instructions.
Disclaimer: Please understand that this is the first public release of this app. Although I endeavour to make my apps as safe as possible, one never knows whether or not some silly bug or unusual interaction might pop a speaker, headset or whatever. I have over 20 devices that I use for testing my apps and I try to "torture test" as much as possible. So if something goes pop, I'll be very sorry and do everything I can to analyze and fix any problems. If you're "not sure", just wait and more adventurous people will do the early testing needed to help ensure nothing breaks.
By it's very nature, any app that can boost volume creates risk for audio output devices as well as your ears.
For those who know my Spirit FM apps, this is a bit of a move for me. Spirit1 and Spirit2 both are alive and well, but the future of FM radio on Android seems to be dimming the last few years. I'll be splitting my time between apps based on the support I get.
Making this HAL Shim based provides some advantages and disadvantages over other methods of changing volume or gain.
Advantages include:
- Audio modification even for apps, games, etc. that use the low level Android NDK OpenSL ES API.
Disadvantages:
- Analog controls, if available, may be better.
AudioTricks is intended to be my name for a group of small apps, and/or a "master app" that includes the features of them all.
VolumeTricks is the first such small app to be released, and is focused on output volumes and input gains.
VolumeTricks may not be limited to the "HAL Shim" approach to audio mods. It may also include ALSA, ALSA UCM, and other methods to manipulate audio.
At this time, the app is free, but Copyright Me. I'll likely maintain a free version for some time, but I gotta eat too so there will be a paid version on Play when it seems ready.
At this time, this app has been tested mostly on CM11 and a few other AOSP ROMs. Many stock ROMs won't work, especially HTC.
The app is currently set to only work on Android KitKat 4.03+.
I haven't tested ART much yet, mostly Dalvik, but it's working OK on my One M7 w/ ART. Shouldn't be too hard to fix any ART issues.
So what the heck is a "HAL Shim" ??
Android uses HALs (Hardware Adaptation Libraries) as an API between Google's Android code and the phone OEMs hardware specific code. Android Audio has at least 2 HALs, one for "Policy" (selects outputs, inputs and some other stuff) and one for the audio transfers. The HAL Shim in this app works with the latter "Primary" HAL for audio transfers.
A SHIM is a component that sits between 2 other components and pretends to be the higher component as well as the lower component. Hierarchy:
Android AudioFlinger
------------------------
HAL Shim
------------------------
Primary Audio HAL
So, the HAL shim pretends to be an audio HAL to Android's AudioFlinger. AND it pretends to be Android AudioFlinger to the Primary Audio HAL.
The HAL shim acts as an intermediary. It can pass everything back and forth unmodified which makes it invisible. Or it can modify anything passing between, including the audio data.
Isn't there a better way to do this ? No, I don't think so. I don't want to be modifying a bunch of HALs on thousands of ROMs. I also don't want to be modifying AudioFlinger on those same hordes of ROMs.
What else can be done with the HAL Shim concept, besides "Volume Tricks".
I think some of these may be feasible:
- Recording all inputs and/or outputs. Maybe even both sides of phone calls.
- Analyze, Visualize, Equalize, Effects-ize all or many inputs and outputs.
- Bypass DRM.
- Maybe a method to modify (eg. encrypt / decrypt) phone call audio, inbound and outbound; possibly via pretending to be a BT headset....
Note that, at present, the HAL shim only works with the "Primary Audio Interface". Small-ish mods could do the same for HDMI, A2DP / BT, USB Audio, "Remote Submix" and whatever new audio devices Google defines.
Post 2 download link and instructions.
If a boot loop would ruin your day, please see warnings at top of post #1 and don't install this app until more mature.
Disclaimer: Please understand that this is the first public release of this app. Although I endeavour to make my apps as safe as possible, one never knows whether or not some silly bug or unusual interaction might pop a speaker, headset or whatever. I have over 20 devices that I use for testing my apps and I try to "torture test" as much as possible. So if something goes pop, I'll be very sorry and do everything I can to analyze and fix any problems. If you're "not sure", just wait and more adventurous people will do the early testing needed to help ensure nothing breaks.
By it's very nature, any app that can boost volume creates risk for audio output devices as well as your ears.
Android seems to have a ridiculously / hilariously complex audio system... LOL.
v140530: http://d-h.st/2lc#.U4hLA3KBugY
Fixes a LOT of issues, especially SU / mount issues with stock restrictive SELinux like Samsung stock 4.2+.
As always, Press Update/OK to update Shim HAL each new release.
- SU / root fixes, especially for SELinux Samsung 4.2+.
- Fine control removed.
- Coarse control range changed from -60 to +60 db ; now 0 to +36 db. Maybe I'm the only one w/ a need for gain reduction below 1.0 or 0 dB.
- Many other fixes.
Version av-140526:
- Fix the /system/addon.d/ ROM update backup/restore script used during ROM updates.
Version av-140525:
- Automatic gain reduction is now sticky, so reduces distortion when maxed. Touch sliders to reset.
- Numbers for VU.
- After amplification VU display.
- Sliders caiibrated in dB.
May not work on stock ROMs, especially older Android versions and HTC stock ROMs.
Starting this app for the first time should request root and prompt to install the HAL Shim and an addon.d backup/restore script to allow it to survive ROM updates.
After the Shim is installed, the "system_server" is killed in order to activate the Shim. Sometimes it may be better to completely reboot the phone, especially with effects, visualizers and player apps running at install time.
Once the app and Shim are installed, the app shows a "Remove" button that removes the Shim, should it be causing you problems or you just don't want/need it. The button will change to "Update" with newer versions of the app/Shim.
Sometimes, like on ROMs with old Legacy HALs, state detection won't work and the button will only offer to Install with no way to remove. As of v1.0.3 go to the 2nd tab (swipe from right to left) and there is a permanent Remove button.
If you remove the app without removing the Shim, the shim will remain, but should be mostly dormant. The easiest way to remove the Shim would be to reinstall the app and select the Remove button.
To manually remove the Shim and addon.d script, something like this should work from a connected PC with adb shell:
Code:
adb shell
su
mount -o remount,rw /system
ll /system/lib/hw/audio.primary.*.so
# !!!! Note the name of the HAL, like audio.primary.msm8960.so and use this name in next line. (If only audio.primary.default.so exists, use that.)
mv /system/lib/hw/audio.primary.orig.so /system/lib/hw/audio.primary.msm8960.so
rm /system/addon.d/99-audiotricks.sh
mount -o remount,ro /system
reboot
Using the app:
See post #3 for usage instructions.
Usage:
If a boot loop would ruin your day, please see warnings at top of post #1 and don't install this app until more mature.
Disclaimer: Please understand that this is the first public release of this app. Although I endeavour to make my apps as safe as possible, one never knows whether or not some silly bug or unusual interaction might pop a speaker, headset or whatever. I have over 20 devices that I use for testing my apps and I try to "torture test" as much as possible. So if something goes pop, I'll be very sorry and do everything I can to analyze and fix any problems. If you're "not sure", just wait and more adventurous people will do the early testing needed to help ensure nothing breaks.
By it's very nature, any app that can boost volume creates risk for audio output devices as well as your ears.
To select output volume or input gain, swipe left or right or use the tabs. The primary/left screen is for output volume.
Set the enable switch to ON to enable volume/gain adjustments.
The Left and Right indicators are logarithmic/DB audio level indicators, updated every 0.1 seconds with the peak audio level. These show the signal level before amplification. If they are VERY near the full width of the screen, there is little amplification that can be reasonably done. (But 80-90% leaves some room, given the exponential nature.)
For no boost, IE an amplification factor of 1.0, the Coarse and Fine controls should both be set to 0 at centre.
Setting Fine all the way right to +6 dB doubles audio power, setting to -6 dB halves audio power.
Setting Coarse to +30 dB creates an amp factor of 32, assuming Fine is set to 0. Setting -30 dB is about 0.03.
Note that an amp factor of 32 is very high, unless you are dealing with very low input signals.
The Shim detects when the signal will overload, and reduces the amp factor as needed to prevent overload/distortion. To raise it again, use the UI to reset.
There are some "streams" for which amplification will not work. I will support as many stream flags (such as Fast) as I can; remains to be seen; this is still kind of a "research project" at this stage.
At present, all streams are amplified the same amount. Per stream or stream type amp factors will be supported.
Just go to post #11 on next page.
Nothing to see here, move along.
Technical info to fill in later.
Pay no attention...
... to the man behind the curtain...
8 is lucky 7 + 1; even better.
Trouble-shooting info.
#10 is always "Future".
Comments and questions start here.
Volume control?
Hi Mike,
You are making me curious about this new project of you.
I bought a long time ago this app for level control. It is doing his job, but has lack of storing the settings and sometimes still adjust (unwanted) the volume.
Count me in for testing :fingers-crossed:
Edit: get an error parsing the apk :crying:
Rinoceros said:
Hi Mike,
You are making me curious about this new project of you.
I bought a long time ago this app for level control. It is doing his job, but has lack of storing the settings and sometimes still adjust (unwanted) the volume.
Count me in for testing :fingers-crossed:
Edit: get an error parsing the apk :crying:
Click to expand...
Click to collapse
Welcome to my new thread and app.
AFAICT, that app mostly just manipulates standard Android volume levels, which is fine, but not much different than the standard volume control.
I just downloaded my new app linked http://d-h.st/plb myself (7 downloads in first 2 hours now), and it installs fine on my One M7, and matches bit for bit the 1.0 version installed on my test phones.
So you're on stock based InsertCoin ROM ?
As long as it's Android 4.4 KitKat (API Level: 19), it SHOULD parse and install OK.
The binaries are for ARM devices only (ie 99+% of Android devices). Intel x86 or MIPs can't work (at present.)
I can't think of any other reason it won't parse, unless your copy is corrupted. This is the MD5 I get:
Code:
md5sum ~/Downloads/av-release.apk
2c8328e8cbe1f585f3b1634e36200c8f /home/mike/Downloads/av-release.apk
I'm happy to hear anyone else's stories of success or failure, but I'll need a good 7 hours of sleep first.
------------
Happy Victoria Day to all fellow Canadians & CommonWealther's, and Good Long Weekend to all those with a day off of work this Monday. Finally nice weather here lately...
mikereidis said:
I just downloaded my new app linked http://d-h.st/plb myself (7 downloads in first 2 hours now), and it installs fine on my One M7, and matches bit for bit the 1.0 version installed on my test phones.
So you're on stock based InsertCoin ROM ?
As long as it's Android 4.4 KitKat (API Level: 19), it SHOULD parse and install OK.
Click to expand...
Click to collapse
Aha, here might be my problem. My InsertCoin is still the good old JellyBean 4.3 (I am happy with this version and had nearly no problems and all the stuff is working on this one. So if it ain't broke; don't fix it )
The binaries are for ARM devices only (ie 99+% of Android devices). Intel x86 or MIPs can't work (at present.)
I can't think of any other reason it won't parse, unless your copy is corrupted. This is the MD5 I get:
Code:
md5sum ~/Downloads/av-release.apk
2c8328e8cbe1f585f3b1634e36200c8f /home/mike/Downloads/av-release.apk
I'm happy to hear anyone else's stories of success or failure, but I'll need a good 7 hours of sleep first.
Click to expand...
Click to collapse
Got the same MD5: 2C8328E8CBE1F585F3B1634E36200C8F
I am confused or it doesn't work on 4.3
Sleep well!
4.4
Does it work on Android below 4.4?
Can't wait to try it. Your work with Spirit was amazing, so I am sure this is too.
Thanks for the effort, but it ain't working on i9100, cm 11/kk 4.4.2. Tried to increase volume a little (level was about 3, but as you know, first written value is 5), there was a very strange noise as I tried to.increase volume via volume buttons while listening music via headphones. It was a crackling noise, looked to me like the phone is going to get damaged, so I removed HAL and uninstalled your app.
Rinoceros said:
Aha, here might be my problem. My InsertCoin is still the good old JellyBean 4.3 (I am happy with this version and had nearly no problems and all the stuff is working on this one. So if it ain't broke; don't fix it )
Got the same MD5: 2C8328E8CBE1F585F3B1634E36200C8F
I am confused or it doesn't work on 4.3
Sleep well!
Click to expand...
Click to collapse
Here's a v1.0.2 test release that will install on Android 2.2+: http://d-h.st/QfV
Draw Em! said:
Does it work on Android below 4.4?
Click to expand...
Click to collapse
It may. Here's a 2.2+ test release: http://d-h.st/QfV
Chances are lower the lower the Android version. I'd recommend 4.1+, but it may work on some Android 4.0 as well. Android 2.3 GB and older used a "legacy HAL API" which won't work.
At this time it's a "bleading edge" release, and most people comfortable with that have been running 4.4 the last 6 months, I'd think.
pilgrim011 said:
Thanks for the effort, but it ain't working on i9100, cm 11/kk 4.4.2. Tried to increase volume a little (level was about 3, but as you know, first written value is 5), there was a very strange noise as I tried to.increase volume via volume buttons while listening music via headphones. It was a crackling noise, looked to me like the phone is going to get damaged, so I removed HAL and uninstalled your app.
Click to expand...
Click to collapse
It sounds like it was working then, as it does for me on my 9100 with CM11.
In many circumstances audio amplitude will already be maxed out, and trying to increase volume will only result in the automatic gain control kicking in with a different value many times per second, thus leading to distortion and other audio "artifacts".
This solution is more helpful when, for some reason, the audio source material doesn't use the full 16 bits of amplitude. If the VU indicators in the app are showing peaks around 80-90% of the screen width, when the normal volume control is maxed, then amplitude is probably above 16,000 and could be near the absolute peak around 32,000.
For example, some audio may have been recorded that only peaks around 4,000 - 8,000, and for this, and amp factor of 4 may be useful. Another possible solution for this scenario is to enable Compression in DSP Manager or whatever. As with everything, this has pros and cons.
In many circumstances, when possible, it's better to raise analog gain, like Voodoo sound does on the Galaxy S GT-I9000. I'm going to look into this, but this sort of solution is very audio chip dependent.
Due to modem-induced crashes that I am unable to fix, this is discontinued.
This is an unofficial CyanogenMod 11 ROM with the first 3.4 kernel for any Galaxy S2 variant. The kernel is based off of the most advanced kernel source available from Qualcomm (CAF) for MSM8660/MSM8960 CPU architectures. Please note that this kernel is still a work-in-progress, so you may experience some issues while using it.
ROM features:
Fully-functional camera and camcorder
Fixed available front-facing-camera camcorder resolutions (so it can record at higher resolutions)
Disabled LPA (as it isn't functioning correctly on MSM8x60)
Enabled Qualcomm BSP (Board Support Package)
Enabled Qualcomm bionic optimizations
Uses CAF media HAL (media-caf)
USB mass storage mode (disabled by default; enable it in Settings -> Storage)
Kernel features:
First-ever 3.4 kernel for any Galaxy S2 variant
Based off of the latest CAF kk_2.7 kernel source available (source tag: AU_LINUX_ANDROID_KK_2.7_RB1.04.04.04.007.067)
Uses Qualcomm's latest drivers and enhancements available for our architecture
Performance is over 9,000
Upgraded the amount of REAL RAM by 44MB (userspace now has 829MB of RAM, as seen in Settings->About Phone)
Removed LOTS of excessive debugging and other garbage (a lighter kernel is a faster kernel)
Newest WiFi drivers from Samsung's Galaxy S5 kernel
WiFi direct works
WiFi hotspot works
No 5-second delay in camcorder
Fixed cable-type 6 charging wakelocks (cable-type 6 = unknown charger)
Fixed slow charging speed with some chargers
Ultra-fast charging over USB (up to 1200mA, regular fast charge in all other kernels is 900mA)
Increased maximum current for AC charging to 1200mA (it is 900mA in all other kernels)
Improved screen colors via HTC MDP color enhancement (screen colors are less saturated)
Note that the kernel does not contain advanced features like overclocking at the moment as overall stability has yet to be confirmed. Overclocking will be added in the future if feedback is positive after the first few weeks of testing.
Screenshot:
{
"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"
}
Source code:
My manifest (cm-11.0 branch): https://github.com/sultanxda/Android
Kernel source (cm-11.0 branch): https://github.com/sultanxda/sultan-kernel-skyrocket-pure-CAF-3.4
Vendor binaries (cm-11.0 branch): https://github.com/sultanxda/android_vendor_samsung_celox
Device trees (cm-11.0 branch):
https://github.com/sultanxda/android_device_samsung_msm8660-common
https://github.com/sultanxda/android_device_samsung_celox-common
https://github.com/sultanxda/android_device_samsung_skyrocket
https://github.com/sultanxda/android_device_samsung_qcom-common
Known issues:
Mobile data
In-call microphone
USB OTG (plugging in a USB OTG device crashes the phone)
Modem init takes 1 minute longer than it should
Modem init fails if the device is put to sleep before mobile network is detected when you first turn on the device (If the device is completely powered off and you turn it on, unlock the device and wait for mobile network to be detected before putting the device to sleep. Once mobile network is detected for the first time after boot, you can forget about this bug)
Device does not always reboot successfully when the kernel crashes
Overall stability is not guaranteed as this is a work-in-progress
Credits (in no particular order):
Team Chopsticks
CyanogenMod and its contributors
CAF (Code Aurora Forum)
PA for the gapps
bryan2894
Flemmard
If I forgot you, slap me and force me to use an iPhone
Downloads:
Mirror 1 (AndroidFileHost):
ROM: https://www.androidfilehost.com/?w=files&flid=19081
Gapps: http://www.androidfilehost.com/?w=files&flid=15801
Kernel standalone installer (this installs only the kernel): https://www.androidfilehost.com/?w=files&flid=19120
This kernel can be flashed over my other CyanogenMod 11 ROM if you want nightly ROM updates
XDA:DevDB Information
CyanogenMod 11 with CAF 3.4.0 kernel, ROM for the AT&T Samsung Galaxy S II Skyrocket SGH-I727
Contributors
Sultanxda
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2014-09-16
Last Updated 2014-11-29
Reserved
Changelog:
September 17, 2014:
ROM:
*Latest upstream CyanogenMod changes
*Fixed Bluetooth
Kernel:
Sultan kernel CAF 3.4 Pure v1.0.1:
*Fixed Bluetooth clock name
September 16, 2014:
ROM:
*Initial release
Kernel:
*Initial release
Reserved
TAKE THAT, SHAMSUNG!
#rekt
Amazing!!! Can't wait to try it out. Hopefully you sort out Bluetooth as well.
Thank you!!!!!!
Downloading now. I'll test it later tonight when I don't need my BT
Wow this is amazing... But what does over 9000 performance mean? What is the performance now when I'm running your other ROM + 1.3.4 kernel?
I mean, the current ROM of yours is running great so am I gonna see even more improvement in speed?
X
Sent from my Nexus 7 using XDA Premium 4 mobile app
xxboarderxx said:
Wow this is amazing... But what does over 9000 performance mean? What is the performance now when I'm running your other ROM + 1.3.4 kernel?
I mean, the current ROM of yours is running great so am I gonna see even more improvement in speed?
X
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Make a nandroid and try it
Sent from my Nexus 5 using XDA Free mobile app
Sultanxda said:
Make a nandroid and try it
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This is exactly what I am doing right now!
Sent from my SAMSUNG-SGH-I727 using XDA Premium 4 mobile app
It's definitely more responsive and smooth. Didn't think that was possible based results with your previous kernel. Is there some sort of app that can actually test the responsiveness so I can see a comparison (not just here, but compared to other kernels)? Or is it only based on 'feel'?
I initially tried a dirty flash, but after 5 or 6 mins in the boot animation, i just ended up doing a clean flash and all installed perfectly.
I'm not sure what a USB OTG is, but the only thing I noticed with USB, is the mass storage wasn't recognized; only MTP.
xonelith said:
It's definitely more responsive and smooth. Didn't think that was possible based results with your previous kernel. Is there some sort of app that can actually test the responsiveness so I can see a comparison (not just here, but compared to other kernels)? Or is it only based on 'feel'?
I initially tried a dirty flash, but after 5 or 6 mins in the boot animation, i just ended up doing a clean flash and all installed perfectly.
I'm not sure what a USB OTG is, but the only thing I noticed with USB, is the mass storage wasn't recognized; only MTP.
Click to expand...
Click to collapse
USB OTG = USB On-The-Go
USB OTG allows you to plug in regular USB flash drives and keyboards to your phone via a USB OTG cable. The performance increase can definitely be quantified. Just try a benchmark like Antutu or something; however, keep in mind that some kernels use different CPU governors and governor configurations than others (as well as different hotplug methods), so your benchmark results will probably be inconsistent. Benchmark results will be consistent if you want to compare this kernel with my 3.0 kernel. Also keep in mind that there are some performance aspects that a benchmark cannot measure.
I just tested USB mass storage and it worked on my computer (my computer is running Linux). I'll go try mass storage mode with a Winblows computer to double-check.
Sultanxda said:
USB OTG = USB On-The-Go
USB OTG allows you to plug in regular USB flash drives and keyboards to your phone via a USB OTG cable. The performance increase can definitely be quantified. Just try a benchmark like Antutu or something; however, keep in mind that some kernels use different CPU governors and governor configurations than others (as well as different hotplug methods), so your benchmark results will probably be inconsistent. Benchmark results will be consistent if you want to compare this kernel with my 3.0 kernel. Also keep in mind that there are some performance aspects that a benchmark cannot measure.
I just tested USB mass storage and it worked on my computer (my computer is running Linux). I'll go try mass storage mode with a Winblows computer to double-check.
Click to expand...
Click to collapse
Thanks!
I am using Windows. It's common to have intermittent recognition issues with USB. Sometimes it all works great and other times... well. However, normally it's both MTP and UMS. In this case MTP had no issues, even when switching back and forth between the 2.
Sultanxda said:
Make a nandroid and try it
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So... I installed ROM with be kernel and I honestly do not feel any difference between this and the other one.
I'm sure benchmarks don't lie but I've based this on my purely qualitative observations.
This is why I ask what 9000 means and how is it relative to the other kernel.
Sent from my SAMSUNG-SGH-I727 using XDA Premium 4 mobile app
Is the kernel standalone ready for release?
I saw it in the changelog but not in the downloads area.
xxboarderxx said:
So... I installed ROM with be kernel and I honestly do not feel any difference between this and the other one.
I'm sure benchmarks don't lie but I've based this on my purely qualitative observations.
This is why I ask what 9000 means and how is it relative to the other kernel.
Sent from my SAMSUNG-SGH-I727 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I guess you're not very picky about performance. I experienced a night vs. day performance difference. Games that would lag on the 3.0 kernel are now fluid for me. Apps are opening faster and the UI as a whole feels much more fluid.
From a coding standpoint, 3.4 makes 3.0 look weak. Some of the many, many improvements in 3.4 include completely new ARM drivers, Ion memory drivers, MMC drivers, power-management architecture, generic Linux drivers, etc.
anomalya said:
Is the kernel standalone ready for release?
I saw it in the changelog but not in the downloads area.
Click to expand...
Click to collapse
This kernel is still in an experimental phase; installing it on another ROM would compromise feedback on its stability/functionality.
Sultanxda said:
This kernel is still in an experimental phase; installing it on another ROM would compromise feedback on its stability/functionality.
Click to expand...
Click to collapse
Understood. I was looking to install it on the latest CM11/SoCal's nightlies.
Sultanxda said:
I guess you're not very picky about performance. I experienced a night vs. day performance difference. Games that would lag on the 3.0 kernel are now fluid for me. Apps are opening faster and the UI as a whole feels much more fluid.
From a coding standpoint, 3.4 makes 3.0 look weak. Some of the many, many improvements in 3.4 include completely new ARM drivers, Ion memory drivers, MMC drivers, power-management architecture, generic Linux drivers, etc.
This kernel is still in an experimental phase; installing it on another ROM would compromise feedback on its stability/functionality.
Click to expand...
Click to collapse
I think I am just not as observant as some of you. But then again, small changes are sometimes not noticeable to the 'untrained' person. It also is somewhat relative unless we are talking about a total game changer. I also don't game on my skyrocket so that could be another reason why I don't notice the difference that you do.
Don't get me wrong... Once the bugs are all worked out on this kernel, you can bet I will switch over if everyone else does because the majority are almost always right.
Thanks for sharing your work.
X
Sent from my SAMSUNG-SGH-I727 using XDA Premium 4 mobile app
Thanks @Sultanxda for the great work! Hope you continue making awesome modifications for the device. Let me know if you want me to help with some extensive testing.
New build uploaded with Bluetooth fixed. @anomalya I have also added a download link to install only the kernel (no Aroma installer). The kernel is only compatible with my other CM11 ROM (http://forum.xda-developers.com/showthread.php?t=2718129). This is useful if you want to get nightly ROM updates and continue using the 3.4 kernel. Feedback is welcome if you decide to use this kernel over my other ROM.
Bluetooth is fixed? () Are you sure¿ I'm gonna spank BT senseless and see.
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Sultanxda said:
New build uploaded with Bluetooth fixed. @anomalya I have also added a download link to install only the kernel (no Aroma installer). The kernel is only compatible with my other CM11 ROM (http://forum.xda-developers.com/showthread.php?t=2718129). This is useful if you want to get nightly ROM updates and continue using the 3.4 kernel. Feedback is welcome if you decide to use this kernel over my other ROM.
Click to expand...
Click to collapse
Thanks. Downloading the kernel with the nightlies.
Messing around with it more tonight, and definitely a huge difference loading apps, but really noticeable on games. :highfive:
I'll mess with BT and GPS tomorrow.
Code:
*** Disclamer ***
[U][COLOR="red"]NOTE: This is an experimental build with some bleeding edge features enabled.[/COLOR][/U]
I'm not responsible for anything that may happen to
your tablet as a result of installing custom roms and/or kernels.
You do so at your own risk and take the responsibility upon yourself.
CREDITS:
Ziyan , Sheffzor for setting up their Unlegacy Android project, which is the base of this experimental build.
If you can afford to support some of the developers, please donate to them instead of me.
Shout-out to:
AndDiSa, ParrotGeek, daniel_hk, and franciscofranco for their involvement in Nexus 7 kernel/ROM development.
Features:
The same as Unlegacy Android's kernel, with the addition of ZRAM & ZSMALLOC from upstream kernel 3.10 , and with the addition of SDCARDFS.
Installation:
0. MAKE A BACKUP
1. This kernel is compatible with Unleagcy Android's ROM only, and nothing else.
2. If you have the above mentioned ROM installed, boot in to bootloader mode and flash the boot.img with the following fastboot command:
Code:
fastboot flash boot boot.img
3. If you were previously rooted, don't forget to re-apply root to avoid any related boot loops.
4. Altough ZRAM is added as a feature you have to actually set a size to it in Kernel Adiutor (or some other similar kernel manager app)Download#1/Download#2 and tick "Apply on boot" and reboot your device to turn it on.
Or alternatively create an init.d script to enable it with your desired size at boot.
You can verify if your swap/zram device is working by typing "free" or "vmstat" into a terminal emulator.
If the size of the swap device is anything but 0, it will work.
{
"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"
}
Zram is set to LZ4 compression and 4 streams by default, swappiness is set to 50.
5. [Optional] SDCARDFS is enabled by default , you can verify that its working by typing the following commands into a terminal emulator:
Code:
su
df -t sdcardfs
If some lines shows up like on the picture below then SDCARDFS works just fine.
6. Various ramdisk scripts like re-mounting the drives and trimming are currently not added, to avoid any bug reports related to these additions. You can still use SSD Boost or FSTrimmer app to achieve these effects. If this build proves to be stable enough we can look in to adding the scripts to the ramdisk.
7. Have fun
Bugs:
Same as on the base 3.4, for example I rarely encounter a hang/freeze with some graphical glitches, but it's pretty much the same with the unmodified base version.
Due to the lack of a Tilapia device, I was only able test the kernel on a Grouper.
SDCARDFS is highly experimental, it caused some issues on other devices for some users (like space not freeing up after deleting some files), although it works fine for me, you should bear this in mind when you install this kernel.
As mentioned above, you have to either enable swap for zram via an init.d script or via a kernel manager app like Kernel Adiutor.
This is despite the fact that the block device is added to the fstab and swapon_all is added to the init.grouper.rc . Still have to figure out how to get around this, but currently i don't have the time to do so.
Downloads:
Check the downloads tab at the topic title, or
click here for the download link
Sources:
https://github.com/csabaszalonna/android_kernel_nvidia_tegra3
Changelog:
2017.06.26
Initial release
Added and enabled ZRAM & ZSMALLOC from upstream 3.10
Added and enabled SDCARDFS
Enabled F2FS for both Cache & Data
XDA:DevDB Information
[TEMPORARY HALT][ALPHA][3.4][ZRAM][SDCARDFS]Experimental Nexus 7 kernel build, Kernel for the Nexus 7
Contributors
namerke, Ziyan, Sheffzor
Source Code: https://github.com/csabaszalonna/android_kernel_nvidia_tegra3
Kernel Special Features: SDCARDFS, ZRAM, F2FS CACHE/DATA
Version Information
Status: No Longer Updated
Created 2017-06-26
Last Updated 2017-11-10
Reserved
Looking forward to trying future versions of this kernel, but unfortunately on a talapia device it currently never leaves the bootloader screen (Google and the unlocked icon).
Geko45 said:
Looking forward to trying future versions of this kernel, but unfortunately on a talapia device it currently never leaves the bootloader screen (Google and the unlocked icon).
Click to expand...
Click to collapse
Well, as said in the list of bugs, tilapia is not tested at all due to lack of device.
But if you didn't perform a clean install than it can take it's time to get through the bootloader screen, even on grouper. So make sure you wait there for a while.
On clean install I didn't encounter this issue.
Aside from the freezing issue, this is way smoother than stock.
My current config includes
200MB Zram (swappiness 100 - like Andisa's)
CPU quiet policy: runnable (experiment in reducing the freezes)
interactive perameter 'midrange_go_maxspeed_load' reduced to 90 from its default of 95.
Root Killing SystemUI when the screen is off (Again to try to prevent freezing/need for manual reboot)
SSD Boost
Running this command at startup :
Code:
service call SurfaceFlinger 1009 i32 1
(old habit - suggestion of parrotgeek's to speed up rendering of transparency)
Current result: freezing maybe eliminated, time will tell...
Current theory: Freezing may be due to excessive background cpu load, ie. the system trying to do too much at once. SystemUI may have nothing to do with it, but I still have my suspicions.
35hrs uptime with the above config + forced GPU 2D rendering, frequent use, so far so good...
adstraylight said:
35hrs uptime with the above config + forced GPU 2D rendering, frequent use, so far so good...
Click to expand...
Click to collapse
why the force gpu 2d rendering?
abhifx said:
why the force gpu 2d rendering?
Click to expand...
Click to collapse
It was a thought to take some load off of the CPU, bear in mind I'm not a developer, so am working from basic principles, but it did seem to make everything run smoother. Could be wrong though, what do you think?
I should also add that /sys/block/zram0/max_comp_streams is set to 2, I don't remember doing this, but it could have changed when I was playing with bits of the parrotmod script file, and may have some bearing on the situation. In fact I think it was when I was trying to find an alternative to using Kernel Auditor to initiate the zram...
Uptime 58.5 hrs ?
adstraylight said:
It was a thought to take some load off of the CPU, bear in mind I'm not a developer, so am working from basic principles, but it did seem to make everything run smoother. Could be wrong though, what do you think?
I should also add that /sys/block/zram0/max_comp_streams is set to 2, I don't remember doing this, but it could have changed when I was playing with bits of the parrotmod script file, and may have some bearing on the situation. In fact I think it was when I was trying to find an alternative to using Kernel Auditor to initiate the zram...
Uptime 58.5 hrs
Click to expand...
Click to collapse
well 2d gpu acceleration should on by default, However the developers can use software rendering. This setting just overrides software rendering.
just to add that i am also not a developer.
abhifx said:
well 2d gpu acceleration should on by default, However the developers can use software rendering. This setting just overrides software rendering.
just to add that i am also not a developer.
Click to expand...
Click to collapse
Amateurs of the world unite!?
It was something I remembered from trying to optimise MM on grouper that made a lot of difference at points.
So I've stopped killing the systemui, rebooted, and have had 19hrs of uptime since, so I think we can discount that as a cause.
I have to say that the battery life with this configuration is extremely good. Do you think it would be possible to enable some overclocking?
The stability issue seems to be sorted now, and I see there's a commit under evaluation on the UA Gerrit that might consolidate things further, with regards to a possible memory leak. So it's all looking rather good ?
adstraylight said:
I have to say that the battery life with this configuration is extremely good. Do you think it would be possible to enable some overclocking?
The stability issue seems to be sorted now, and I see there's a commit under evaluation on the UA Gerrit that might consolidate things further, with regards to a possible memory leak. So it's all looking rather good
Click to expand...
Click to collapse
you should post your findings on main ulegacy thread too. maybe this will prompt the devs to incorporate these settings.
this thread has been great and i have finally fixed my broken grouper to try these roms and kernel again
abhifx said:
you should post your findings on main ulegacy thread too. maybe this will prompt the devs to incorporate these settings.
this thread has been great and i have finally fixed my broken grouper to try these roms and kernel again
Click to expand...
Click to collapse
My guess is that they're already aware of what's been posted here, how are you finding it?
adstraylight said:
My guess is that they're already aware of what's been posted here, how are you finding it?
Click to expand...
Click to collapse
they are relying more on changes pushed to their gerrit rather than tracking all the thread. so i dont know posting in their thread is also a good idea.. but hey its better than nothing.
@namerke great to see someone build something off of the work the 3.4 guys achieved. This was the sort of thing we hoped for from the beginning and I really am surprised that you're the only one so far, years after the project started, to brave the source code and use it for a project.
Also, does the original kernel not have zram at all, or have you simply updated the current code to upstream? Cheers
I am running @adstraylight suggested tweaks and its running Rock Solid. The only thing I did not do was reformat for F2FS since it wont work by default with Unlegacy. After the initial start the tablet stops having any system ui, force close, or mtp reboot issues. Boot is much faster and functions more like a normal tablet. I would recommend these changes to be incorporated into grouper unlegacy because as of now, running stock unlegacy with updated builds still has freezing, random rebooting and general issues with slowdowns. Honestly I still don't know why F2FS got scrapped for data and cache. I get that they are working on adding support for a lot of devices but it's just not useable in its current form with stock Unlegacy, unless you are okay with systemui freezes and random reboots.
New version is up, please refer to the #1 post for the updated changelog.
adstraylight said:
My current config includes
200MB Zram (swappiness 100 - like Andisa's......
Click to expand...
Click to collapse
Hi @adstraylight , thanks for all the feedback, it's been helpful , really, since i don't have much time to pressure test our device.
New version is including some of your suggestions to the interactive governor + some adjustments to it from Unlegacy-Android gerrit.
Also, @AndDiSa uses 250MB of ZRAM with swappiness of 60 by default , therefore this is the way I have configured the latest version since it seems to work just fine on 3.1 .
Number of ZRAM streams have been reduced to 1, just like @AndDiSa 's config, again , to reduce CPU load.
HTCDreamOn said:
Also, does the original kernel not have zram at all, or have you simply updated the current code to upstream?
Click to expand...
Click to collapse
Hi @HTCDreamOn , to be honest i didn't even really checked the capabilities of the base 3.4 regarding ZRAM.
I followed a simple logic when I decided to go with the 3.10 upstream version: it proved itself fast and reliable on my Nexus 5, and also since it's from the upstream, it's more recent
All these said, I suspect that the base is lacking some files to enable ZRAM by default but I'm not sure since as I mentioned I didn't really checked the base source regarding ZRAM.
chosin137 said:
The only thing I did not do was reformat for F2FS since it wont work by default with Unlegacy.
Click to expand...
Click to collapse
@chosin137 , thanks for the feedback. As it turns out, based on my experience F2FS on cache causes some instabilities on this version too, therefore I have removed the option to use in in fstab.grouper on the updated version.
Also, this way it will be closer to the base , which can help with merging if @Ziyan and @sheffzor decides to go that way.
Thank you all for the feedback, happy testing
Hi @HTCDreamOn , to be honest i didn't even really checked the capabilities of the base 3.4 regarding ZRAM.
I followed a simple logic when I decided to go with the 3.10 upstream version: it proved itself fast and reliable on my Nexus 5, and also since it's from the upstream, it's more recent
All these said, I suspect that the base is lacking some files to enable ZRAM by default but I'm not sure since as I mentioned I didn't really checked the base source regarding ZRAM.
Click to expand...
Click to collapse
Makes sense, I've seen a lot of kernels using zram and similar from 3.10. That could be it, it doesn't look like zram is enabled at all in the default kernel but I find it odd that it would be missing the files. I only just flashed the recent version of the ROM a few days ago so it's running fine on the stock kernel, will give yours a go once I've bogged it down with some more apps though.
sadly my experience is on the negative side as i can easily completely freeze my tablet. only reboot is the solution. i guess i have seen this issue more in the stock 3.4x kernel too so i guess its more of a rom / memory leakage issue. However the tab does feels smother than other 3.1x kernel based rom. so the tweaks does seem to help more. i might try flat rom+kernel for while, if things are better then i can blame gapps and remove it altogether (although i do want maps for navigation purpose)