So the thing is, most JB ROMs for TF101 (I think that's actually all ROMs but AOKP) use a userspace hack to invert the dock lid state before propagating it to the power management code in the framework. It is, of course, a solution, but it's rather ugly and it clutters the global framework with code that's actually needed for one or two devices in total.
So I suggest that instead of messing around with the userspace, we need to fix the bug in device specific code, i.e. the kernel. I've made a kernel patch long ago for AOKP, but now I'm experiencing problems with other kernels on unmodified userspace, so I decided to post it here and see if other developers/ROMs accept it.
There is already a framework for 'inverting' the result in the kernel, so I reused that, and that made a very simple patch. All it does is check for any switch input (a.k.a. the dock lid) and set its active_low flag to 1, which makes the kernel invert the received data. Since the code is in gpio-keys, it's very unlikely to conflict with any external devices.
The source for the patch is available on my GitHub, it should work with kernel, though I built it for AOKP kernel, which is stock .39 + bcmdhd.
So, framework hacks vs. kernel hacks, discuss.
K900 said:
So the thing is, most JB ROMs for TF101 (I think that's actually all ROMs but AOKP) use a userspace hack to invert the dock lid state before propagating it to the power management code in the framework. It is, of course, a solution, but it's rather ugly and it clutters the global framework with code that's actually needed for one or two devices in total.
So I suggest that instead of messing around with the userspace, we need to fix the bug in device specific code, i.e. the kernel. I've made a kernel patch long ago for AOKP, but now I'm experiencing problems with other kernels on unmodified userspace, so I decided to post it here and see if other developers/ROMs accept it.
There is already a framework for 'inverting' the result in the kernel, so I reused that, and that made a very simple patch. All it does is check for any switch input (a.k.a. the dock lid) and set its active_low flag to 1, which makes the kernel invert the received data. Since the code is in gpio-keys, it's very unlikely to conflict with any external devices.
The source for the patch is available on my GitHub, it should work with kernel, though I built it for AOKP kernel, which is stock .39 + bcmdhd.
So, framework hacks vs. kernel hacks, discuss.
Click to expand...
Click to collapse
Nice to see you again, old friend.
I have already developed like the same hack for my new CyanogenMod kernel, just that I am using a seperate c class to perform the switch each time the native asus code does receive a signal requesting to change the dock status.
So, generally, I would say this is a good idea and the way this problem should be solved.
The whole problem should stay in a low-level kernel space and never ever even require a userspace fix.
We just have to keep this on track, and maybe do a collection of how to-compile-kernels and some collection of tweaks, e.g. I can share my governor's code and so on. This should be a sticky then, so no developer for the TF101 can ever miss it.
If people request this I can do this. Just need some opinion.
So, after all, +1 to your (and mine, not yet shared) solution.
RaymanFX said:
I have already developed like the same hack for my new CyanogenMod kernel, just that I am using a seperate c class to perform the switch each time the native asus code does receive a signal requesting to change the dock status.
Click to expand...
Click to collapse
The logic's already there, just use my patch, seriously. Also, that's why you read kernel docs before coding stuff, toldya
Also I never really disappeared, you have my GTalk and I have the thread on Rootz. Don't want to post it here though, because XDA is, well, messy. And Rootz, at least for now, is less messy. Kinda. That's what I was thinking. Also keeping close to AOKP official forums.
Related
This is just a thread to offer a consolidated place for update notifications and such for alternative kernels. I will try to keep the most recent versions in this post but you should always check the end of the thread just to make sure.
Consider these experimental, use at your own risk, no ones responsible for anything, blah blah blah.
For best results, always use cyanogenmod roms
Most recent kernels:
pershoots Kernels
http://droidbasement.com/db-blog/
ezterrys kernels
http://forum.xda-developers.com/show...&postcount=670
dumfuqs OC (Requires setting scaling_max_freq in order to boot)
cm-5.0.8
32B/32A
cm-6.0.0
32B
32A
newest (10/14/2010):
2.6.35.7 32A/B (only oc710 so most of you will need to set your max frequency in init.d or whatnot)
archive:
http://www.mediafire.com/?6paej1h9tpkif
dumfuqs github
hey dumfuq, can you create a blog, I like following your work, would be nice to see it all elsewhere. Are you on github?
thanks, your work is appreciated
thx for posting this
Nice to see this here.. It would be nice to further explain, I searched else where but could not find....
I know
OC---IS OVER CLOCKED
UV---IS UNDER VOLTED
FP---????
Not to be rude but this is the third kernel thread on Page 1 of G1 Android Development. Hope a mod consolidates the three into one.
On another note, thanks for your kernels.
dumfuq said:
This is just a thread to offer a consolidated place for update notifications and such for alternative kernels. I will try to keep the most recent versions in this post but you should always check the end of the thread just to make sure.
Consider these experimental, use at your own risk, no ones responsible for anything, blah blah blah.
For best results, always use cyanogenmod roms
Most recent kernels:
pershoots Kernel 2.6.34-OC-UV-FP – Dream/sapphire(32B/A)
http://droidbasement.com/db-blog/?p=538
dumfuqs OC -Dream/Sapphire(32B) (requires setting scaling_max_freq in order to boot)
oc825-cm-2.6.34-8t3-signed.zip
Click to expand...
Click to collapse
with oc825-cm-2.6.34-8t3 im not getting full multitasking, im able to multitask 3-4 apps but the kernel isnt utilizing all the swap before killing processes
I think it's rather nice to have an OC kernel that doesn't require swap though.
just updated with changes from cm-5.0.8-t4
defconoi said:
with oc825-cm-2.6.34-8t3 im not getting full multitasking, im able to multitask 3-4 apps but the kernel isnt utilizing all the swap before killing processes
Click to expand...
Click to collapse
They make it use all the swap, and people complain, they tone it down, and people complain.
Seriously though, adjust swappiness and perhaps use AutoKiller to set the settings LOWER than default. That should keep more apps around. Note that doing that may cause extreme slowness, so if it breaks, you get to keep both parts.
When I fool with those types of settings, I like to disable "set on boot" type options so that a reboot clears them if I screw something up. Then I can tune away till I get what I want, then set them on boot. Of course, just as I figure out how I like it, a new release comes out. owell, I do so love flashing my phone. I feel like I need a .sh file with "adb shell "reboot recovery"" in there on my computer's dock.
new dream/sapphire kernel images posted - http://droidbasement.com/db-blog/?p=546
Any chance on someone uploading the oc xtra v4 with lower frequencies please.. I don't know how to change the userinit or resign =P thank you. Last time with test2 cyanogen, it booted up fine leaving the frequencies on my old settings but now test4 it just won't boot because frequencies got over written this time and set825 which I know why but I don't know how to resign and stuff..
rahuljj said:
Nice to see this here.. It would be nice to further explain, I searched else where but could not find....
I know
OC---IS OVER CLOCKED
UV---IS UNDER VOLTED
FP---????
Click to expand...
Click to collapse
FP = floating point optimized
32a test
I have no way to test this myself but...
It looks like it is fairly trivial to make a 32A port (since cyanogen has already patched the source). So here is a version of my latest that might work on 32A. If you try this, please let me know if it works or not.
Same as my others in that it requires you to set the scaling_max_freq in order to boot.
oc825-32A-cm-2.6.34-8t4-signed.zip
2.6.34 BFS kernel. I found it in the cyanogen forums.
http://www.4shared.com/file/BmZU6db6/BFS508t4.html
I went from 23 to 24 fps on neocore benchmark. Not really that much of an increase but 5% is 5%. I know some people hate BFS with a passion but I like the extra frame=p.
Link to OP
So I tried you kernel (was too lazy to make my own) and everything works (it boots) except the wifi, either due to the fact that I'm running 5.0.7 or the slight possibility that you put the wrong kernel module for wifi because 32A and 32B don't use the same one, will compile my own to see if it's just the kernel module...
rps13 said:
So I tried you kernel (was too lazy to make my own) and everything works (it boots) except the wifi, either due to the fact that I'm running 5.0.7 or the slight possibility that you put the wrong kernel module for wifi because 32A and 32B don't use the same one, will compile my own to see if it's just the kernel module...
Click to expand...
Click to collapse
This might fix the wifi.
yup wifi is fixed, so was it the kernel module?
rps13 said:
yup wifi is fixed, so was it the kernel module?
Click to expand...
Click to collapse
Yup...that wass it. Thanks.
825 isnt stable for me , how about turning out a optimized 710 or 670 build ?
mejorguille said:
2.6.34 BFS kernel. I found it in the cyanogen forums.
http://www.4shared.com/file/BmZU6db6/BFS508t4.html
I went from 23 to 24 fps on neocore benchmark. Not really that much of an increase but 5% is 5%. I know some people hate BFS with a passion but I like the extra frame=p.
Link to OP
Click to expand...
Click to collapse
Why do people dislike BFS? I don't really see much of a reason for the hate (but I also don't really know the difference)
I'm very new to android dev, not new to dev in general, though.
I hear ROMs being talked about quite frequently, not sure if I'll get into it, can't seem to find an address of the specific issue:
- What is a ROM?
In the sense, is it the entire OS? Is it the OS + UI? Does it include local apps & contact storage? Like, obviously apps and contacts wouldn't be read-only, but typically ROM means PROM (or some variation (EPROM/EEPROM/FROM, whatever), so I take it with a grain of salt.
From what I gather it's the entire OS + UI, and that's all? But I'm not sure.
Also, is there ways to replace specific parts of the ROM? Ie. Say I want to make modifications to the thread scheduler but I don't want it to touch some of the reliant modules..is it possible to just drop in a new scheduler by overwriting part of the binary image? Or are these things whole-sale?
Reason simply being is I don't like the idea of some random ass ROM that somebody cooked up with god knows how much OS exp controlling everything, as it's a binary it's not like you can crack it open and diff it or anything...or there's no official forks or branches to look at, y'know? Do people just "trust" all these ROM modders/creators?
Sorry for the over-abundance of questions :-X
Oh my god it's already on page 7...bump...?
Take a look at cyanogen mod. It comes with the source which you can fork if you'd like.
Sent from my HTC Desire
ROM - its the entire visible OS that you tend to interact on your phone + the kernel (shipping just the ROM would be useless). Its pretty much every software that you need to get your work done on the phone. You may chose to install additional's but thats just accessorizing your phone. Its called ROM since once you install the OS image over the phone, the region of sd-card is generally marked read-only & you are not expected to make changes to it (concisely /system partition & also /data where the OS can do write operations but again, there are exceptions to this rule too in custom ROMs).
As for Custom ROMS, they are generally forked of the AOSP except for the little nuances the rom maker's add to them (mostly those changes are in form of theme, few apps here & there, icons, wallpapers). I think your question is more specific to custom kernel instead because thats the entity which help/harm your device.
For that, I would suggest you to pick a particular custom release (such as Netarchy, popular for Nexus S)
& read over their change-logs. The kernel devs generally do a great job of maintaining those logs precisely. The initial fork of their kernel too comes from AOSP to which they add specific features such
as ext4 fix a.k.a Turboboost, Voodoo color & sound enhancement, BLN & odd.
Hope I have allayed some of your fears regarding customs software.
Thanks.
Yeah, I just get nervous installing an OS/Kernel blindly.
Changing themes would be nice, and I'd like the ability to do so without dropping in a ROM that can potentially have changes made to the Kernel. I don't like the fact that the ROM encompasses EVERYTHING, therefore it's coupled to the fact that you need a different ROM regardless of what you change.
It should be modular enough that you can modify themes without flashing an entire OS onto it.
Also, what's the chances that if a ROM install fails, you can re-load it (ie. what are the chances of you bricking your phone)? I don't have time for that.
Next to none if you make a nandroid, which is a backup.
Sent from my myTouch 4G using XDA App
rockstarar said:
Next to none if you make a nandroid, which is a backup.
Sent from my myTouch 4G using XDA App
Click to expand...
Click to collapse
It says that only works for the G1.
I completely forgot to ask, apps should stay, right?
I mean they're all in user land, shouldn't have anything to do with the ROM nor actual OS....right? (probably wrong... )
Hello,
I other android kernels, you can switch on/off the back light of the keys (menu, search, back,home) just by switching to 0 and 1 the value of a file.
However, I would like to know how to do it in Nexus S kernel.
Please, notice that I am not interested in getting a kernel which is already capable of doing this back light blinking stuff for notifications, whatever,
What I want to know is if anyone could give me a hint about where it is set in the kernel so that I can develop my own stuff.
I have seen that there are many kernels with this stuff implemented around the internet, but noone explains a little bit how it is done. So what I am asking for is not for a kernel doing this, rather for a brief introduction on how to do it.
Thank you !!!
Not sure myself, but fine an open sourced kernel which allows this feature and look through the commits (GitHub or something) to see if its obvious.
Good luck!
Sent from my Nexus S
I read somewhere that this isn't possible with the NS, might be wrong though.
Good luck either way
I don't think it's possible to do, because they are always on then the screen is.
But your best bet might be to ask Neldar about it.
according to this thread: http://forum.xda-developers.com/showthread.php?p=14350642
that reffers to this app: https://market.android.com/details?id=net.geekherd.softbuttonshack
that contains thit text:
*ALERT: The Samsung Nexus S will NEVER be supported. Not because I don't want to, but because it is not possible, I own one and I have tried and tried. Samsung (or Google) have decided that the bottom LEDs will always be on as long as the display is on, powered at the same time. Obviously breaking a few APIs as well as the ability to turn those LEDs off based on the light-sensor.*
it is not possible at all!
=o\\\
It's possible on both i9020 and i9023, but through slightly different methods. This is how Neldar's BLN works.
My understanding is that on i9020, the button backlights are not individually controllable (that is, you either have all 4 on or all 4 off) but on the i9023 it is possible to individually control each LED.
Have a look at this patch for generic BLN on my github or neldar's github as a starting point. It doesn't have a /sys or /proc file interface to control the LEDs individually but one could be hacked in relatively easily.
https://github.com/akent/samsung-kernel-crespo/commit/374edad6f03fb04b6a9e4522519df69ea5f9795b
akent said:
It's possible on both i9020 and i9023, but through slightly different methods. This is how Neldar's BLN works.
My understanding is that on i9020, the button backlights are not individually controllable (that is, you either have all 4 on or all 4 off) but on the i9023 it is possible to individually control each LED.
Have a look at this patch for generic BLN on my github or neldar's github as a starting point. It doesn't have a /sys or /proc file interface to control the LEDs individually but one could be hacked in relatively easily.
https://github.com/akent/samsung-kernel-crespo/commit/374edad6f03fb04b6a9e4522519df69ea5f9795b
Click to expand...
Click to collapse
Thank you !! I will go through it
I checked but...
I was checking that patch for the supposed Nexus S kernel...
However, after downloading the original source from source.android.com I see that the source code that this guy tweaks is completely different from the one I get from the official repository.
Does anyone knows somewhere else about how the backlights of the keys are controlled ?
duendecito_vivo said:
I was checking that patch for the supposed Nexus S kernel...
However, after downloading the original source from source.android.com I see that the source code that this guy tweaks is completely different from the one I get from the official repository.
Does anyone knows somewhere else about how the backlights of the keys are controlled ?
Click to expand...
Click to collapse
You want the kernel source, not the android source. Find Netarchys or Supercurios GitHub account and then I think it is called linux-samsung or something.
Sent from my Nexus S
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!
Hi all,
As you may assume, I'm the owner of an ASUS TF300TG, since summer'12. During this time, I kept the device updated only with official ROMs. This leads to have currently Android 4.2.1 with what I consider low performance. This pushes me to think on a new ROM, maybe KatKiss with Lollipop or Marshmallow, or even Xubuntu.
The things that take me back from this are the following:
1. I use this device to connect to my company's network. The policy for connecting to such network is no root and no jailbreak. Would it be possible to install a rom without root? I assume so, indeed xubuntu should be recognized as Linux PC.
2. I'm not a programmer, but not only a user. I have installed several PC (window and linux), and flashed once a mobile phone. I'm able to open a command line window and write some commands. But I started to read the xubuntu post, and I wasn't able to follow the messages (at least, the first pages). Is there any place to follow the detailed steps to install a new rom?
3. I would consider a pitty to loose the 3G functionality. Here, I find some kind of contradictions.
a) http://forum.xda-developers.com/transformer-tf300t/accessories/tf300tg-rom-3g-t3270011
Here it's said that asus hasn't released the source code for the 3G module.
b) http://forum.xda-developers.com/showthread.php?t=2190847
But there's also the xubuntu post, that is stated (if I understood it properly), that 3G module is working. This totally misleads me...
4. After all this, will the effort worth it? I mean, I don't know if the performance improvement will be enough to make up the risk of loosing functionality (or even make it as usable as a brick). I saw some videos over Marshmallow, and it totally encourages me (have to further consider three topics above); I don't find some over xubuntu, and I don't see them so promising...
Thank you in advance for your time reading and answering. I expect your coments [emoji1]
Enviado desde mi ASUS Transformer Pad TF300TG mediante Tapatalk
After more than 150 reads, and no reply, I asked myself what went wrong. I realized that a post with title "Update for TF300TG" that maybe most users would open the post only to check if the there's any update they would like to know. That's the reason why I edited the title into something that avoid misleading.
If this is not the reason not to answer, please let me know.
Regards.
Update TF300TG?
I think you answered your own question in #1. You need it for work, unchanged.
If you were to do anything in the way of changing your ROM, even to xubuntu, then your TF300 would need to be rooted.
Your Asus is old and slow. Nothing you can do will change that.
Maybe you need to get something new and much faster and use it for work.
Then you will still have your TF300 to play with and learn how to root and change roms...
just my opinion,,,, Bob
YMMV but not many custom TF300 ROMs actually lead to a performance gain in the long term (although most may seem very fluid on first few uses). Mostly what they provide is a way to run a more recent Android version on the aging TF300. Gray-Beard phrased this painfully well. It's old and there's nothing you can do to change that.
At the end of the day, Cromi-Xenogenesis 5.4 may just be the best TF300 ROM around. It's great, but make no mistake: this also is just Android 4.2.1
I must say this company policy of "no root, no JB" is absolutely ridiculous. Not only do I doubt this to be verifiable from network perspective, but is the infrastructure THAT insecure that your machine-local EP may pose a security threat to the extent that such a policy is pertinent? And if there IS a BYOD mechanism in place, what happens if you have a windows machine with local admin? Is that also a big no-no? I mean ,God forbid you should have EP on your own bloody device....
On the other hand, xubuntu (or most other linux) isn't that great on TF300, you won't be able to run recent Xorg due to limited ABI support of NVidia's closed-source Tegra3 drivers (thanks NVidia!), probably won't be able to use kernels beyond 3.1.10 (if you do then pls show me how) and the whole thing is just not that stable.
chemizt said:
YMMV but not many custom TF300 ROMs actually lead to a performance gain in the long term (although most may seem very fluid on first few uses). Mostly what they provide is a way to run a more recent Android version on the aging TF300. Gray-Beard phrased this painfully well. It's old and there's nothing you can do to change that.
At the end of the day, Cromi-Xenogenesis 5.4 may just be the best TF300 ROM around. It's great, but make no mistake: this also is just Android 4.2.1
I must say this company policy of "no root, no JB" is absolutely ridiculous. Not only do I doubt this to be verifiable from network perspective, but is the infrastructure THAT insecure that your machine-local EP may pose a security threat to the extent that such a policy is pertinent? And if there IS a BYOD mechanism in place, what happens if you have a windows machine with local admin? Is that also a big no-no? I mean ,God forbid you should have EP on your own bloody device....
On the other hand, xubuntu (or most other linux) isn't that great on TF300, you won't be able to run recent Xorg due to limited ABI support of NVidia's closed-source Tegra3 drivers (thanks NVidia!), probably won't be able to use kernels beyond 3.1.10 (if you do then pls show me how) and the whole thing is just not that stable.
Click to expand...
Click to collapse
I will share my experience.
I'm on the Cromi-Xenogenesis 5.4, with standard configuration I got a flawless system at the begging, but after few months I got a laggy device, so then I made a full wipe then I reinstalled everything from the scratch. I did it two times in 2 years.
The last time, before I was willing the third wipe, during first days of January 2016, I tried to make some change in the config with Kernel Adiutor and Developer option.
In kernel Adiutor:
- Governor CPU: perfomance
- Internal Memory => Scheduler: cfq
In Developer option:
- disable animation: Window animation scale, Transition animation scale and Animator duration scale
- force rendering on GPU.
Other important suggestions could be:
- use stock browser
- use Nova launcher
- use Twlight for night use (it's a red filter for screen)
- use Swifteky and reduce the keyboard dimension
- use Adaway to remove useless banner
- kill autostart app (like Amazon, Aliexpress, Weather app... etc)
Now maybe my little guide it's useless, but I have a usable tablet still in 2016 for Web, Gmail, little editing of documents, Telegram, Imgur, Youtube (maybe it has little problem here) and Netflix.
I tried KatKiss 6.x (don't remember the exact version number) for TF300T without 3G, then installed "ppp widget 2" (or "ppp widget 3"?) from Google Play and started 3g manually from this application (widget). Android will not automatically switch from Wi-Fi internet to 3G internet (as like in stock), you must switch it manually. Some bugs discovered, for example, I could connect 3G and disconnect only once, when I want to connect 3G again, I had to reboot. device. Maybe will work on some other firmwares?