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!
I've created a fork of Quarx's Defy CM10 repository, to build the latest version from Quarx but using the Linaro 4.7 toolchain. I encourage anyone who might stumble upon this thread to go to linaro.org and read about this non-profit organization and what they are trying to do. Note that TI is a supporting member of this non-profit org, as well as Samsung, LG, ARM, etc. All of these companies have interests in optimizing code performance on ARM architectures.
Now, Quarx has already created a couple of builds using the Linaro 12.10 toolchain. These builds are available as his November 17th and 18th builds, but there was much debate in the original CM10 thread (here) as to whether or not there was (1) any benefit from using the Linaro toolchain and (2) if the Linaro toolchain was adding instability. I think after these discussions Quarx decided to revert back to the original prebuilt Android toolchain.
I've created this build as an experiment, using the latest available (12.11) version of the Linaro toolchain.
Builds are located here:
http://goo.gl/vbAKN
Changelog:
cm-10-20121215-UNOFFICIAL-mb526.zip: First build, based roughly on Quarx 05-Dec or perhaps later; I just forked his most recent repo, then added Linaro 12.11 and made a few small changes to get it to build. (Thank you Quarx)
cm-10-20121218-UNOFFICIAL-mb526.zip: Cherry picked "Volume adjust sound preference 1" and Volume adjust sound preference 2 from ICS. (StevenHarperUK)
cm-10-20121219-UNOFFICIAL-mb526.zip: wpa_supplicant_6 switched to CyanogenMod official jellybean-stable branch. This means maniac's and Quarx's commits and changes involving AdHoc are not in this version. Trying to see if this helps wifi connectivity at my gym where the phone seems to get very confused and drops/connects to wifi many times. Wifi at my home is no issue. This version also reverts a change from Quarx that may or may not have an effect on reading NTFS cards... No idea, for testing.
cm-10-20121222-UNOFFICIAL-mb526.zip: using Linaro 2012.12. Screenshot option in long press power much enabled by default, cherry pick for screen off animation (not sure what benefit this was), more debugging statements in MediaProvider to debug NTFS issue.
cm-10-20121224-UNOFFICIAL-mb526.zip: same as above, but used Linaro optimizing compiler flags from Kayant, removed the screen off animation cherry pick.
cm
cm-10-20130104-UNOFFICIAL-mb526.zip: Switch to JellyX kernel repo from Blechd0se (thanks!), kernel built with standard gcc 4.4.3 while everything else is built with Linaro gcc 4.7. Seems to be stable overnight, I had to wipe cache/dalvik/data to get it to boot. I've rebooted it several times on purpose to check stability and it is, so far, stable.
The forked repo is located here:
https://github.com/skelliam/android
If you want to try to build this yourself, you *will* encounter build errors. One in particular with Linaro is regarding strict-aliasing. There is some discussion of this on the Linaro blog here. There are several other errors that you'll enounter, but fortuantely, Quarx has already created a script that checks out fixes for most of these.
So in general, the process will be something like this:
Move to a directory that will hold the sources. I just created a directory 'cm'.
Code:
$ mkdir cm
$ cd cm
$ repo init -u git://github.com/skelliam/android.git -b jellybean
Now you need to run Quarx's script to make the fixes required for Linaro. From the ROOT of your repository (in my case the cm subdirectory):
Code:
$ ./device/moto/jordan-common/apply_linaro.sh
Now, what the heck, try to build it. You will encounter more compile errors but it is worth it to see what I'm talking about. To build:
Code:
$ source build/envsetup.sh
$ brunch mb526
You should get a bunch of errors related to strict aliasing. To fix these, right now I've applied local changes on my repo, in the remaining makefiles responsible for the errors. Here are the changes I've made locally to get around these issues. I will try to make an update to the apply_linaro.sh script as Quarx did, it was 2 am when I did this and I just wanted to get it built.
Update 5-Jan-2013 I've checked in everything now, so if you use my base manifest file (from github.com/skelliam/android) you should not need to make any changes OTHER than to run the apply_linaro.sh script.
Someone mentioned that the BBC I player app doesn't work.
First of all, are we talking about this app?
{
"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"
}
So I tried this out here. On first install, when I tried to open a program, the phone became almost unresponsive, something was hogging the CPU. I had to pull the battery.
After rebooting, this app seems to work fine:
That's my experience anyway. As far as Netflix, I've just recently cancelled my subscription, so I can't do much with that one.
Sent from my MB526 using Tapatalk 2
Nice ROM seams to be verry smooth. battery life is as far as I can say quite good.
I think I found a bug - Bluetooth is not working I think. Same behavior as on quarx' 2012-11-18 - build.
At least for me. Maybe quarx' bluetooth-fix for this build can solve the problem? Couldn't test yet.
Thread moved as your OP has no format whatsoever and the Development section isn't for discussions. If you want this in Development please make it clearer that this is an actual ROM and not just a discussion and also add all credits with links to the original work. Just look at some of the other ROM threads for an example of what should be included e.g changelog/features, what changes have been made, what you're asking people to test for you to discuss, just anything really to give more info then you have given already.
Thanks
AvRS
AvRS said:
Thread moved as your OP has no format whatsoever and the Development section isn't for discussions. If you want this in Development please make it clearer that this is an actual ROM and not just a discussion and also add all credits with links to the original work. Just look at some of the other ROM threads for an example of what should be included e.g changelog/features, what changes have been made, what you're asking people to test for you to discuss, just anything really to give more info then you have given already.
Thanks
AvRS
Click to expand...
Click to collapse
Really a PM would have been fine.
This thread was created to avoid clutter in another thread.
At the bottom of the post I'm pretty sure it says that it was posted with Tapatalk from my phone? As soon as I'm on my PC I'll add as much rich content as you desire... There is only so much I can do from my phone.
Lastly, each thread IS a discussion, I have no idea what a "forum" is for other than discussing things.
Sent from my MB526 using Tapatalk 2
I'll confirm that Netflix does not work. Stuck on splash screen with loading wheel spinning. Never tried it on quarx 0512, though.
Great build, IMO. No problems on any of my heavy use apps. No reboots or freezes yet. 20 hrs uptime.
Using my standard setup; no ksm, no zRam, no overclocking, 16 bit transparency. Interactive and noop.
Sent from my Red Lens MB525 using xda app-developers app
EldonTyrell said:
I'll confirm that Netflix does not work. Stuck on splash screen with loading wheel spinning. Never tried it on quarx 0512, though.
Great build, IMO. No problems on any of my heavy use apps. No reboots or freezes yet. 20 hrs uptime.
Using my standard setup; no ksm, no zRam, no overclocking, 16 bit transparency. Interactive and noop.
Sent from my Red Lens MB525 using xda app-developers app
Click to expand...
Click to collapse
Awesome, thanks for testing it. I've been having some instability regarding wifi and Tasker, but I experienced this also with the Nov-18 from Quarx. I will keep investigating it.
On last builds by quarx I had problems with touch screen input getting delayed/unresponsive some times. Until now I don't experience that in this build, but I should use it longer to be sure.
Oh I see now it's the same as what I did before the difference was I was trying to compile CNA with it but it broke in so many places I just gave up loool I will try again I guess and see if there is indeed some improverments in CNA because I remember full linaro CM & kernel that I tried before was a bit smoother that just having linaro compiled kernel.
Anyways thanks for clearing that up for me
wskelly said:
Someone mentioned that the BBC I player app doesn't work.
First of all, are we talking about this app?
View attachment 1568120
So I tried this out here. On first install, when I tried to open a program, the phone became almost unresponsive, something was hogging the CPU. I had to pull the battery.
After rebooting, this app seems to work fine:
View attachment 1568122
That's my experience anyway. As far as Netflix, I've just recently cancelled my subscription, so I can't do much with that one.
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
It was I. I was looking at the official BBC iplayer app which is here and requires the BBC Media Player to do the heavy lifting here
It's not as severe a crash as on the 05/12, where I had to yank out the battery, it crashes when it should hand off to the stream, the rest of app works, you can navigate the programme listings etc but just at the point when the stream starts on CM7.20 it hangs. I have access to 3 defys so I can confirm that is the point when the app crashes. I can also confirm the Netflix issue. Are these two related?
As I said in the other thread it is significantly snappier, I'll keep one defy on Quarx, one on this linaro build and one on CM7.20 for feedback (well at least until xmas when they're all being given as presents) :laugh:
The problem I get with all newer builds by Quarx , from 11/18 onwards, is this logcat entry: "E/MediaProvider( 9674): Can't obtain external volume ID even though it's mounted.", which causes process media to be killed all the time, making the user experience a true hell: camera, music player, Play Store, etc, etc, etc, i,e. practically nothing which requires access to my NTFS formatted 64GB card works! So, I'm always back to his 11/17 build (for a month now). I already posted thiis many times on his CM10 dev thread, but, as usual, I get ignored. You, most probably, have already read my posts about this issue there. Anyway, any thoughts if I would face this issue if I flashed your ROM?
Awesome job ...works fine on MB525 green :thumbup:...
Sent from my MB525 using xda app-developers app
casouzaj said:
The problem I get with all newer builds by Quarx , from 11/18 onwards, is this logcat entry: "E/MediaProvider( 9674): Can't obtain external volume ID even though it's mounted.", which causes process media to be killed all the time, making the user experience a true hell: camera, music player, Play Store, etc, etc, etc, i,e. practically nothing which requires access to my NTFS formatted 64GB card works! So, I'm always back to his 11/17 build (for a month now). I already posted thiis many times on his CM10 dev thread, but, as usual, I get ignored. You, most probably, have already read my posts about this issue there. Anyway, any thoughts if I would face this issue if I flashed your ROM?
Click to expand...
Click to collapse
Hi casouzaj... This is interesting that it started happening between 11/17 and 11/18, so it should be easy to find and fix.
Yes you should probably face this issue with this build because I'm using the repo from Quarx, all of the files are the same except for some changes to get it to build with Linaro.
wskelly said:
Hi casouzaj... This is interesting that it started happening between 11/17 and 11/18, so it should be easy to find and fix.
Yes you should probably face this issue with this build because I'm using the repo from Quarx, all of the files are the same except for some changes to get it to build with Linaro.
Click to expand...
Click to collapse
Thanks a lot, wskelly! Would you be meaning that you1ll get this issue fixed anytime soon?
wskelly said:
Hi casouzaj... This is interesting that it started happening between 11/17 and 11/18, so it should be easy to find and fix.
Yes you should probably face this issue with this build because I'm using the repo from Quarx, all of the files are the same except for some changes to get it to build with Linaro.
Click to expand...
Click to collapse
So, your rom will be 'fork with linaro' only, or you have plans to change something?
I ask, because after 18.11 Quarx builds start drain battery (Android OS takes half of usage), wipes, reinstalls, clean rom, nothing can help.
Great ROM!
Using bf5x batt have jumps
Bluetoot fix from quarx work!
Any idea for batt jumps? Installed on top from 18/11 quarx with full wipe>rom > gapps>reboot
After 24h use:
Verry smooth and in my opinion best responding CM10 I used until now. Usally I stick with quarx' build.
Battery drain about 2% per hour at light/normal use (just a little surfing, reading news, checking mails, etc)
Bugs so far:
Bluetooth disabling crashes phone app.
Bluetooth fix of quarx helps to at least solve the crash. Got bluetooth mouse correctly working. File transfer to a compueter doesn't work.
Reboot into bootmenu/recovery fails - just a reboot happens
wskelly said:
The completed build is located here:
http://goo.gl/vbAKN
Click to expand...
Click to collapse
Is there any mirror? I can not download from this link - download resetting every time when reaching ~25%.
casouzaj said:
The problem I get with all newer builds by Quarx , from 11/18 onwards, is this logcat entry: "E/MediaProvider( 9674): Can't obtain external volume ID even though it's mounted.", which causes process media to be killed all the time, making the user experience a true hell: camera, music player, Play Store, etc, etc, etc, i,e. practically nothing which requires access to my NTFS formatted 64GB card works! So, I'm always back to his 11/17 build (for a month now). I already posted thiis many times on his CM10 dev thread, but, as usual, I get ignored. You, most probably, have already read my posts about this issue there. Anyway, any thoughts if I would face this issue if I flashed your ROM?
Click to expand...
Click to collapse
Could this be the reason, that i am not able to listen properly to music anymore?
Every 5-10 minutes my mobile forgets almost every song on my sd-card, there are some left, but most have gone.
trurl3 said:
Is there any mirror? I can not download from this link - download resetting every time when reaching ~25%.
Click to expand...
Click to collapse
http://www.multiupload.nl/M1QNFOA0JS
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.
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)
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Video Playback
Audio
Sensors
GPS
FingerPrint
tap 2 wake
Known issues:
Volte
you tell me!
Follow Instructions Carefully otherwise you will get error :
Use this 64 bit twrp to flash http://www.mediafire.com/file/i1911qqxlx9v6sm/twrp-3.2-x64-ph2n.zip
Wipe cache, dalvic cache,system,data
Flash ROM-Flash Gapps [Arm64-8.1]
Done-Reboot Now
Enjoy the clean rom
Downloads :
https://www.mediafire.com/download/t9b8g097ihhu7b4
Credits:
Lineage Team
Please Consider donating if you appreciate my work
https://paypal.me/messi2050
Sources:
Device:
https://github.com/messi2050/android_device_lge_ph2n
https://github.com/messi2050/android_device_lge_msm8937-common
Kernel:
https://github.com/messi2050/android_kernel_lge_msm8937
XDA:DevDB Information
[ROM][64BIT][8.1] UNOFFICIAL LineageOS 15.1 for LG STYLO 2 PLUS, ROM for the LG Stylo 2 Plus
Contributors
messi2050
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: Nougat bootloader
Version Information
Status: Abandoned
Created 2018-05-03
Last Updated 2019-05-09
Reserved
2018-june-13 build changelog:
-June security patch
-Update power scripts from last caf
-Fix vendor mismatch error message
-enable dual wifi bands
-build using last sources
Thanks for the ROM, messi, it's greatly appreciated even if development stops cold after the post you just made.
And for those that might care, the MD5 of the archive is: 00dd56ee08963da05195915dd528d9b1
The headphone audio output on this ROM is rather weak, but that's not messi's fault, it's because of how Oreo is working on this device. There appears to be no mixer_paths.xml file in Oreo now, and I added the older mixer_paths.xml (with permissions 0644 as required) with the necessary adjustments to boost the audio output from the default of 84 to 92. It had zero effect so it seems the audio subsystem in Oreo is now working differently for whatever reason, not sure if there's a way to adjust the defaults at all.
Also, the kernel for this ROM appears to be defaults to just 6 core operation: I've installed the ROM twice now on my S2P and when I check the core activity with CPU-Z it always shows 2 little cores active, 2 offline (always), and all 4 big cores active. And of course the minimum CPU speeds are 960 for the little cores and 768 for the big cores - they should be (or at least I should say they could be set in the kernel parameters down to the minimum of 384 MHz and that would save a bit of battery life.
Overall it's been great so far, really, everything seems to work fine. The flashlight didn't work so I installed a flashlight app then suddenly the toggle started working so, there's something funky going on there but everything else so far has been great. Would be nice if there was a more customized kernel available, yes, with more governors and perhaps even some undervolting potential but I know this device just doesn't have much developer love at all.
Regardless, it's very cool to be able to run Oreo 8.1 now since I have never really given a damn about it at all previously. I may go back to running the stock T-Mobile 20a rooted ROM on my S2P however, it depends on how things work out.
:good:
br0adband said:
The headphone audio output on this ROM is rather weak, but that's not messi's fault, it's because of how Oreo is working on this device. There appears to be no mixer_paths.xml file in Oreo now, and I added the older mixer_paths.xml (with permissions 0644 as required) with the necessary adjustments to boost the audio output from the default of 84 to 92. It had zero effect so it seems the audio subsystem in Oreo is now working differently for whatever reason, not sure if there's a way to adjust the defaults at all.
Also, the kernel for this ROM appears to be defaults to just 6 core operation: I've installed the ROM twice now on my S2P and when I check the core activity with CPU-Z it always shows 2 little cores active, 2 offline (always), and all 4 big cores active. And of course the minimum CPU speeds are 960 for the little cores and 768 for the big cores - they should be (or at least I should say they could be set in the kernel parameters down to the minimum of 384 MHz and that would save a bit of battery life.
Overall it's been great so far, really, everything seems to work fine. The flashlight didn't work so I installed a flashlight app then suddenly the toggle started working so, there's something funky going on there but everything else so far has been great. Would be nice if there was a more customized kernel available, yes, with more governors and perhaps even some undervolting potential but I know this device just doesn't have much developer love at all.
Regardless, it's very cool to be able to run Oreo 8.1 now since I have never really given a damn about it at all previously. I may go back to running the stock T-Mobile 20a rooted ROM on my S2P however, it depends on how things work out.
:good:
Click to expand...
Click to collapse
Mixer is moved to vendor/etc in o
messi2050 said:
Mixer is moved to vendor/etc in o
Click to expand...
Click to collapse
Geezus, I spent an hour looking for that information on multiple forums and websites and you're the first person to point out where it is, damn.
Thank you, thank you, thank you. Adjusted the default path name="headphones" from 75 to 90 and w00t, much much better now.
messi2050 said:
Mixer is moved to vendor/etc in o
Click to expand...
Click to collapse
I want to ask a question. This Custom ROM support the LG Stylus 2 Plus K520TR model?
There are two issues I've noticed, can't say they will, would, or do affect other people and I'm using the MetroPCS model with T-Mobile (I was using the T-Mobile stock ROM originally).
- the Mobile Hotspot does not function. It says it's working in the Settings submenu but the actual hotspot never does function, it never shows up as a visible AP for another device to connect to, the SSID is not broadcast, etc
- the USB options when you plug in a USB cable will not stick, I've got into the Developer Options and I have it set to always MTP and every single time I plug in I have to go manually change it from charging to MTP to get it working
They're not massively important things but for me the Mobile Hotspot could be useful for my Wife when we're out and about; her Flex 2 doesn't have cellular service so in the past she'd just tether to my Stylo but now that's not possible.
Not sure this can even be resolved given the nature of the usage but it would be nice to have those two nitpicks working properly. Aside from that this ROM so far has been spectacular: I'm getting 7+ hours of SOT at 50% brightness, with cellular and Wi-Fi enabled constantly, and using L Speed to handle background performance.
So far so good.
I am getting a vendor ID error every time I restart the phone. T-Mobile version stylo. Clean install followed to a T. I also noticed some games aren't working either like they cannot community ate with the server mainly Paladins strike that game also starts with an error.
I'll try to screenshot the error and write it down as well as the vendor id it says I need to match
Did a full reflash and the vendor id error persists. Also not sure if its because of that but most of the apps and games I try to play are giving me network errors and not downloading the content. I can download from the app store no problem but its within the app that problems with network start. My APN is correct as well.
Wondering if I missed a nougate update that is causing the vendor id error.
rsuthers08 said:
Did a full reflash and the vendor id error persists. Also not sure if its because of that but most of the apps and games I try to play are giving me network errors and not downloading the content. I can download from the app store no problem but its within the app that problems with network start. My APN is correct as well.
Wondering if I missed a nougate update that is causing the vendor id error.
Click to expand...
Click to collapse
I believe the vendor id is used to pass safetynet easier. Expected behavior
Anything going on with this rom?
rsuthers08 said:
Anything going on with this rom?
Click to expand...
Click to collapse
@messi2050 said he was done with this phone and I haven't heard anything from him since, so no. @deadman96385 @Travisholt92 @xRaZeR_FuZioNx and @cospalet are all working on roms still. If you wanna talk to them and see what their plans are, we have a telegram group, but you'll have to find it yourself
Ya I'm not looking to pay for nightlies of an unfinished rom
The ROM works, the only thing that doesn't for me is the hotspot but that's a given anyway and nothing can really be done with it.
Only thing I wish we had at this point is a custom kernel to get the idle speeds down from the current ones of 960/768, they should be 384/384 and it would help with battery life (which is fine even in spite of this current limitation). Maybe some more governors would be nice too but so far I've been running this ROM since it was put out and haven't had a single thing to legitimately complain about unlike others it seems.
Use it, don't use it, but for Pete's Sake® STFU about it and messi, will ya?
I just got my computer up with 14.04.5 TT and set up my build envir. I just need the time. I cant leave my computer set up at home right now and thats where i have the best connection. Its my first time so i intend to do a couple dry runs first, maybe play around with the kernel. But i never have to time to get rling with it
Google lens
I can't believe it but Google Lens actually works on this ROM. I haven't done a lot of testing but so far so good.
---------- Post added at 06:08 AM ---------- Previous post was at 05:42 AM ----------
I can't believe it but Google Lens actually works on this ROM. I haven't done a lot of testing but so far so good.
Edit, I haven't found anything not working.
rsuthers08 said:
I am getting a vendor ID error every time I restart the phone. T-Mobile version stylo. Clean install followed to a T. I also noticed some games aren't working either like they cannot community ate with the server mainly Paladins strike that game also starts with an error.
I'll try to screenshot the error and write it down as well as the vendor id it says I need to match
Click to expand...
Click to collapse
Did you ever find a fix for the mismatching vendor.img? I feel dumb bit its been years since i've fiddled with android internals. They've change quite a bit since lollipop lol
lixer8 said:
Edit, I haven't found anything not working.
Click to expand...
Click to collapse
So, for you, if you have cellular service, can you test out the hotspot functionality and let me know if you're successful with getting it to work? It's the only thing that doesn't work for me, so I switched back to the 7.1.1 ROM where it works just fine. I'd love to continue using the 8.1 ROM but without that hotspot it's a problem.