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!
Related
FOR 32A, RADIO 6.35 and SPL 1.76
this port only have very little modification from original official ROM, some kernel driver tweaks, camera libs replacement, our bt firmware, sensors files and root.
first boot could be not very smooth. screen may go blank, if you would encounter this problem, just wait for a while, and press some keys. when you make all your settings done, a reboot is highly recommended. I have used it daily now.
download:
latest update [Jun 26]::
OC: http://forum.xda-developers.com/attachment.php?attachmentid=349885&d=1277499752
non-OC: http://forum.xda-developers.com/attachment.php?attachmentid=350638&d=1277631885 , under testing, plz report bugs.
changes:
HTC's battery driver
a new driver extension to support default USB netshare *
a newer sanpei helper which is reimplement **
non-OC version: screen on 528/352, screen off 240/176 ***
OC version: screen on 576/384, screen off 245/176 (4.0 in Linpack with JIT)
other fixes, many error reports in aosp kernel (which version > 2.6.29) have gone, we have a clean dmesg now
ROM itself:
apply update after you flash the ROM:
http://www.4shared.com/file/XHlI-Kdl/3pei_hero_21_alpha.html
mirror: http://www.multiupload.com/RRWFEYLPP1 , by malachaskos, thank you
wipe and flash in recovery, and you should delete the generated files (by android) in your sd card.
please make sure that you have installed driver properly. a little more details: http://forum.xda-developers.com/showpost.php?p=6180261&postcount=986
addition:
for JIT, download this: http://forum.xda-developers.com/attachment.php?attachmentid=345213&stc=1&d=1276842897
you have to set your Home Wallpaper and Lockscreen Wallpaper to something on sdcard before the first boot with JIT enabled, (and you can set them back after that: I have tried other HTC wallpapers except default). the workaround is found by klothius, thx .
if you encountered any trouble, and want it disabled, flash this: http://forum.xda-developers.com/attachment.php?attachmentid=345214&stc=1&d=1276842897
for Gallery3D, download this version: http://forum.xda-developers.com/attachment.php?attachmentid=338391&d=1275828997 , it could work with HTC Camera app in most HTC's ROM.
known issues and workaround:
keyboard light and some other led features : flash update plz
gps may need to boot with gps setting on, or you could try capychimp's gps files
official USB netsharing: flash update plz
if you find infinite logs about database queries which are generated by bt components, what I know is a reboot, or kill the bluetooth process
APN list shows nothing (unless your mobile operator is Chungwa in Taiwan), plz manually add your APN
* it could work under windows, but you must enable netshare in settings, and not in notification area. and you must disable netshare in settings if you want to use DiskDrive.
plz don't turn mobile network setting off when wifi is on. HTC's software will disable netsharing and uninstall the driver when you turn off mobile network.
** dev could set the button led timeout now.
just setprop sanpei.buttonlight.delay 20 (in sec) when phone is running, or set it in build.prop. plz report any issues.
*** I don't test the non-OC version myself yet, if you encountered any problem plz tell me, since it have lower frequency when you don't touch the phone.
and if the screen doesn't turn on during boot with OC version, plz press red button to close screen then press any other button to active the screen.
this issues happened once when first time I used this ROM after it was ported, though we don't have a kernel OCed that time. so I had said "first boot could be not very smooth" before. now I found that with higher CPU freq, it will happen more frequently.
so I won't support higher frequency at current. they are not so stable as I considered before. maybe you think that we could boot it with a lower frequency then use higher after boot. but I think if it have troubles when booting, it will have more troubles in heavily usage.
old changes:
some new commits to aosp kernel are included
qdsp driver changed to htc 2.6.29 version with some hacks
other little tweaks, not very important
for developers, many modules are included, you could check the modules folder. but I don't enable things like compcache by default. OC is not included, my phone is heated and I don't want to take a risk before I could have time to verify it carefully.
HTC Sync will work with with version 2.0.25, you can find it here (thank paultoan): http://www.htc.com/us/support/magic-rogers/downloads/ .
other pure ports:
you can find them here: http://forum.xda-developers.com/showthread.php?t=642125 .
legend port is a bit slow, but it have more features: the new way of select text、copy、wiki、translate and dictionary, etc.eris port may be faster then this one, and has been tested for a long time, but with old looks.
could someone test for us, if the new kernel binary and boot.img (in update.zip) could work with legend/eris ports? then we could use it to upgrade these ports too.
sanpei,好久不见啊，这个是基于昨天hero官方发布2.1移植的版本吗？
wuguohui109 said:
sanpei,好久不见啊，这个是基于昨天hero官方发布2.1移植的版本吗？
Click to expand...
Click to collapse
是。在这最好说英文，不然版主说不定对咱们有意见了...
yes, please write in English here, otherwise moderator may have some thoughts...
ok，Download now，thanks，haha
Can You check what languages does it have?
i think both “繁体中文&english”，thats all
sanpei how about rc e100 ? does it work?
Welcome back Sanpei!
Great thanks to sanpei
thanks
Bug ：
Footprints cam Preview no work (photo OK after shooting)
edit---
First Preview rotating, right and bottom Flicker
Second Preview rotating
looking forward to a more stable version
Nice to see you back sanpei.
Would there be any point in trying to throw your new kernel build into one of the older roms (like the legend or eris)?
@Sanpei
are you using your own kernel? cause i think bluetooth drain battery issue still exists on this rom
account1 said:
@Sanpei
are you using your own kernel? cause i think bluetooth drain battery issue still exists on this rom
Click to expand...
Click to collapse
you should turn off bt after using it. a component of bt will prevent the phone going to sleep when bt is turned on. I will try to find a solution when I have time.
I don't want to use HTC's kernel. because they have some other bugs too. fixing bugs in HTC's kernel is less valuable than our current way. and you know, maybe we should try android 2.2 later.
so we must stay at aosp kernel and adapt it to run both AOSP and HTC's ROM. and I think these jobs could be done. all the problems are just time, time and time.
btw, it's not "my own kernel", it is the aosp kernel, I just did some repairing for our purpose
and to others:
sorry, I couldn't do works which would take a lot of time at current. but I won't stop.
sanpei, there's an ongoing effort on porting the 2.6.33 kernel to the new radio, with some work already done. Maybe you could give some help to the people doing that job
sanpei said:
you should turn off bt after using it. a component of bt will prevent the phone going to sleep when bt is turned on. I will try to find a solution when I have time.
I don't want to use HTC's kernel. because they have some other bugs too. fixing bugs in HTC's kernel is less valuable than our current way. and you know, maybe we should try android 2.2 later.
so we must stay at aosp kernel and adapt it to run both AOSP and HTC's ROM. and I think these jobs could be done. all the problems are just time, time and time.
btw, it's not "my own kernel", it is the aosp kernel, I just did some repairing for our purpose
and to others:
sorry, I couldn't do works which would take a lot of time at current. but I won't stop.
Click to expand...
Click to collapse
we thank you all for your effort Sanpei
but by saying "turn off bluetooth after using it" makes me quit of trying all those custom roms with this particular kernel
bluetooth, its a feature i use all the time, every day, so i personally quit flashing until problem is solved
again, thank you for your great work here
Re: [ROM][6.35] a very pure HERO 2.1, new look and eris ...
Sanpei, can we use the cpu clock on some later phase of your rom/kernel ?
-------------------------------------
Sent via the XDA Tapatalk App
helderp said:
sanpei, there's an ongoing effort on porting the 2.6.33 kernel to the new radio, with some work already done. Maybe you could give some help to the people doing that job
Click to expand...
Click to collapse
.33 is a experimental project by Google, and our device won't get benefits from the increased digit. I will only work on kernels which will be chosen by Google and other manufacturers. and sadly, for some nonsense reason, I and some people couldn't work together.
account1 said:
we thank you all for your effort Sanpei
but by saying "turn off bluetooth after using it" makes me quit of trying all those custom roms with this particular kernel
bluetooth, its a feature i use all the time, every day, so i personally quit flashing until problem is solved
again, thank you for your great work here
Click to expand...
Click to collapse
i am really sorry for that. when I was fixing the battery drains, I don't know much about the right behaviors that bt features should have. so I just leave the prevent-sleep mechanism there because I think it is necessary.
and now I don't have enough time as before. but from you and others, I know what the right behaviors are. I will try to fix it in next release, for people who use bt heavily.
Bladyle said:
Sanpei, can we use the cpu clock on some later phase of your rom/kernel ?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
yes (we should make more things could be controlled by users in the long run), but not now.
we still have some issues that are important to other users, though personally, I don't use those features heavily.
my order:
1. lights in Sense ROM for other devices and battery drains when bt is on
2. android 2.2 or big improvements in android 2.2 (port them to daily usable ROM)
3. default USB netsharing, netsharing under windows and other features like this
4. other hardware supports and features like CPU freq control.
5. some hidden bugs in aosp sources or htc drivers we used (though they don't affect anything in most cases)
hope I could get enough time end of this month and next month, then I could repair/add one or two of them.
I only referenced the .33 kernel since that's what's used on cyanogen 5 series mod, and if it could be adapted to the new radio it would be a good way for us to have CM5 with the modifications cyanogen and otheres sometimes do to the kernel. Just my 2 cents
Hi everyone
I've managed to get a fairly good working build now of FRF91 from AOSP. I was inspired mainly by both AdamG and meLIanTQ for there excellent work on both there AOSP built ROM's, so thought I'd have a go at it myself, so here is the result
I'm building this ROM to suit my own personal needs, with various little things thrown in for good measure, but it will remain 100% AOSP source. No APK's will be modified *after* the build, all customisation on my part will be done via the overlay.
THIS IS NOT A SENSE-BASED ROM
ROM Details
Built from latest AOSP source. (FRF-91 2.2-r1.1)
2.1Mb Kernel Image Size so hopefully no problems for people with Bad Blocks
Kernel Base - 2.6.32.9 configured and compiled by myself (UV Support, no OC)
Self-modded Kernel Fix to keep phone charged at 100% while plugged in (used to drop to 89% and charge) (details >here<)
ext2, ext3 and ext4 support
cifs.ko, tun.ko and openvpn
Classic A2SD+ from my original dalvik-cache mod from Rooted 2.1 Eclair for Desire (details >here<) Copies Apps, App-Private and Dalvik-Cache to SD.
A2SD Fixed to help prevent White Screen Hangs (working with ext2 and ext3 partitions, needs testing with ext4)
Latest BusyBox (1.16.2)
Rooted with latest SuperUser 2.2 apk
Massive APN List
h264 Camcorder
Latest FRF91 Google Apps
3G/H Icon Fix to display H during HSDPA connection.
Default Launcher is LauncherPro Beta
WaveSecure installed to /system/app
setcpu.txt copied to sdcard JUST incase you want to use SetCPU to ramp down the CPU Speeds to help conserve battery life (remember, no OC or UV support in kernel, but I do intend to patch UV support in future releases)
The following items have also been removed:
Facebook (Installable from Market)
Twitter (Installable from Market)
Original Android Launcher
Amazon MP3 (Installable from Market)
Whats Working (currently from what I can tell as its what I use)
Facebook Sync (including profile pictures displaying in Phone App and Message App)
WiFi
USB & WiFi Teather
Notification LED's
Camera
NO ECHO
I've also not included items such as SpareParts, or LeoParts... SpareParts and LeoParts can be had from the Market.
Please refer to the 2nd post for a breakdown of changes/fixes/known issues with the ROM
Installation
Fresh Install
I recommend you do a FULL WIPE before you install this ROM if you are coming from another ROM.
Future Upgrades
No wipe is explicitly required in order to use this ROM, however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Just to say. Whenever I release a new Update, I always just "flash over" the existing one without a Wipe and go from there. I'm building each release with this ethos in mind, as its pretty annoying having to do a Wipe on each update!
DOWNLOAD
YOU WILL NEED THE 5.xx RADIO ROM FLASHED TO USE THIS ROM - 4.xx RADIOS ARE NOT, AND WILL NOT BE SUPPORTED SORRY!!
Get the latest RADIO's >HERE<
Also, remember this is a ROM I'm making for myself and a few friends, so I will try to sort out bugs as-and-when they are found, but as I'm still learning how to do this well, it may take a little time for me to sort!
Also during the FIRST initial boot after a fresh install, it can take about 30 seconds for LauncherPro to start responding. THIS IS NORMAL. Any further reboots by yourself, or upgrades in future (without wipes) don't have this issue.
FroYo-Desire 0.4b
Thanks & Credits
st0kes for all the info and tips in the Building Android from AOSP thread.
deovferreira/Kali- for the vendors which make all of this possible.
meLIanTQ for the invaluable help when I ran into a few issues during my initial build
AdamG & meLIanTQ for there inspiration
IntersectRaven for his HAVS Kernel Modifications
Anyone and everyone else who I've forgot to mention
Want to buy me a Toastie?? Can if you want But I'm not in it for the food
Future Additions
Add support to dynamically check and change the keys binded for unlocking the phone
Current Known Issues
Auto Brightness may not be to everyones taste.
Version History & Changelog
0.4b
Kernel UV Values tweaked to 925mV min, 1225mV max.
Conservative Power Governor now set on boot. (can be changed using SetCPU)
Updated LauncherPro to latest release
0.4a
Removed HAVS Additions from Kernel - caused problems with Trackpad & Light Sensor (CM3602).
New Kernel UV-Only based on Pershoots N1 Modifications. 950mV - 1275mV (for stability)
0.4
Recompiled Kernel with HAVS Support (925mV MIN, 1250mV MAX) - Credit >IntersectRaven<
0.3
Added SIM Toolkit
Final 100% Battery Charging Modification in place (keeps battery at 100% while plugged in)
WiFi Sleep now fixed (using own method based loosely on the official Google patch)
WiFi Sleep also fixed in respect to extremely high pings and regular dropped packets still compared to being in a Woken state (pings and packet consistency will remain constant regardless of screen being on or off)
AutoBrightness now set back to original FroYo values. Sense values used in 0.2 were draining the battery and keeping the screen far too bright in dark conditions.
0.2
Re-synced against latest AOSP Release & Kernel_MSM
Further-optimised Charging functions in Kernel
Fixed button backlight (full brightness)
Fixed Notification LED
Fixed Auto-Brightness
0.1b
Re-compiled Kernel enabling "Conservative" mode for (hopefully) better battery saving! (use SetCPU to enable this)
Added fixes to try get 3G working on Orange networks (for those who are fully unlocked with latest Radio's ONLY)
Corrected the order at which kernel modules load. Also sorted out module issue with FileSystem modules loading in the proper order.
No longer clear Vendor cache from Market (causes slowdown on initial use after flashing as upgrade)
0.1a
Initial Public Release
0.1-prerelease
First Initial Build
Fixed LED's
Added Camera Profiles
Fixed Facebook Sync
Fixed Teather
i dont suppose you can tell me where i can get the kernel fix that stops the battery from draining while charging? that is a HUGE problem for me
i will flash your ROM asap but i dont have enough time atm
thanks very much for your ROM looks really good
cgrec92 said:
i dont suppose you can tell me where i can get the kernel fix that stops the battery from draining while charging? that is a HUGE problem for me
i will flash your ROM asap but i dont have enough time atm
thanks very much for your ROM looks really good
Click to expand...
Click to collapse
Updated first post with a link to the modified source file
You sir are an absolute saint
Thanks so so much
5 STARS!
very very nice work.. good job.. i love AOSP rom.. i'll try it tomorrow.. one question. the biggest problem is wifi on OD and AOSPDesire (sleep mode). wifi is working on this rom when goes to sleep? Thanks
How would we go about manually installing the kernel fix? do we flash it?
Thanks again and sorry for my ignorance
cenkaan - What exactly is the WiFi sleep problem? I go into Settings -> Wireless & Networks -> Wi-Fi Settings.
Press Menu key, choose Advanced
Set Wi-Fi sleep policy to Never... Doesn't disconnect for me, but it does run in a low-power mode.
I've noticed using something like SpareParts, has *no* effect on this setting what-so-ever. It only works for me by doing it this way.
cgrec92 - thats the source file for the battery driver which must be compiled in with the kernel from source. As far as I know, the boot.img (my kernel) is compatible with OpenDesire (used it on there myself). It is already included in DeFrost, AOSPDesire, and I think AdamG might be adding it to his future updates as he did ask me where he could obtain the mod
i use wifi policy and set to never but this is not solution for me on other AOSP mods. Thanks for the quick reply
Well I've had the desire running all night and it kept its connection But if it is an issue, please let me know what you do for the issue to show (any other apps used to manage it) and I'll see what I can do
can't wait and i'll try it now
Last question I promise
So the boot.img contains the kernel (you have modified this)
I can use your boot.img on other ROMs such as AdamG's seeing that yours is based on this?
no it's not working...full wipe and later set to never but it's not working..
-sleep mode-
Destination address 192.168.1.86
Packets sent 10
Packets received 0
Average round-trip time 0.000 ms
in the meantime rom is very nice. great job.. Pls help me.. I want to use this rom. i loved it
cgrec92 said:
Last question I promise
So the boot.img contains the kernel (you have modified this)
I can use your boot.img on other ROMs such as AdamG's seeing that yours is based on this?
Click to expand...
Click to collapse
I modified the *source* at which the kernel is compiled and built from. I then configured the base options for the kernel, compiled it, modified the various init scripts (which are supplied via the AOSP source build), and made the ramdisk, packed the boot.img... etc etc
If you wish to use this kernel on another rom (such as OpenDesire), then you will also need to copy the folder /system/lib/modules from my ROM to OpenDesire also. You will also need to manually edit /system/etc/init.d/**** script (whatever it is loading modules) or if there isn't one, create one to load ext2, ext3, ext4 and ipv6...
Bit more involving than I first made out really lol! Sorry...
cenkaan said:
no it's not working...full wipe and later set to never but it's not working..
-sleep mode-
Destination address 192.168.1.86
Packets sent 10
Packets received 0
Average round-trip time 0.000 ms
in the meantime rom is very nice. great job.. Pls help me.. I use this rom. i loved it
Click to expand...
Click to collapse
Strange indeed...
I've been reading a bit in other threads, does your WiFi MAC start with something other than 00:23?? As from what I read in AOSPDesire thread, it occurs to phones whose MAC starts with different numbers to that... Again, sorry its not working for you...
Did some digging, looks like a fault which is also apparent on other HTC devices, including the N1
http://code.google.com/p/android/issues/detail?id=9781
According to that (or so I think it makes out) it's also dependant on the make/model/type of Router which you also use...
So us Desire owners are most definitely not alone...
Ok that's enough hassle for you
Thanks so much for all your help
Fantastic developer will download your ROM as soon as i get home, thanks
thanks for the help and great rom.. and yes, what a pitty my wifi mac address is begin with 38:E7..
PaulW21781 said:
Strange indeed...
I've been reading a bit in other threads, does your WiFi MAC start with something other than 00:23?? As from what I read in AOSPDesire thread, it occurs to phones whose MAC starts with different numbers to that... Again, sorry its not working for you...
Did some digging, looks like a fault which is also apparent on other HTC devices, including the N1
http://code.google.com/p/android/issues/detail?id=9781
According to that (or so I think it makes out) it's also dependant on the make/model/type of Router which you also use...
So us Desire owners are most definitely not alone...
Click to expand...
Click to collapse
The same issue does NOT occur on any HTC ROMs so am wondering what HTC has done specifically to address the problem...
hello sorrry i'm new.... (sorry for my bad english)
in this rom is not sense installed? Can someone upload pictures.
bobo26 said:
hello sorrry i'm new.... (sorry for my bad english)
in this rom is not sense installed? Can someone upload pictures.
Click to expand...
Click to collapse
Sense is not installed, no...
Pictures - couple are in the first post of this thread (at the bottom of it)
*update*
Updated to v0.1b, enabled new "Conservative" power governor for the CPU in the Kernel. Use SetCPU to enable this in the phone itself, will hopefully improve battery life, but will have a slight effect on performance when this option is enabled.
Ok,
here is our new release.
Well... Here we are at last! Whole new ROM, whole new thread
For a long time we have been working to build the best possible version of HoneyComb to the Advent Vega. It has been a LONG road, with many hacks and pitfalls along the way. We started with the messiest set of files anyone has ever seen, and we have now progressed to this. Full-fledged, GPU accelerated, NATIVE, Honeycomb 3.2 on the Advent Vega.
There's no going back now. I'm so happy with this ROM that I'm actually going a little crazy with affection. There are still some bugs... Rebooting to CWM causes a stale boot, you have to hold power to turn the tab off, then on next bot you get CWM. Still no camera, bluetooth isn't working. But other than that... Well, I'll let you guys see for yourself.
On the speaker issue, I feel I must put a quick note here... We BELIEVE that the "Overheating speaker" issue is now resolved. Audio levels are now well within the safe limits, and voltages are back at what should be a very safe level. But as always, please be VERY careful, unfortunately we cannot be responsible for any hardware failures resulting from using a custom ROM, but we are very confident that this issue should now be totally resolved.
VegaComb 3.2 Build 9b und 9n Update3 Features:
Update1+2 included
The clock and date issue should now been fixed for all
GPU RAM reduced to 96MB , more RAM for Apps
support for high Wifi channels like 12 + 13
new Honeycomb market
support for the soon coming GPS App included
Downloads, please choose the right Version (original ROM download is at the bottom of this thread!)! (or you Bootloop) :
Update 3 for Build9n: VegaComb_HC3.2_Build9n_update3.zip
Update 3 for Build9b: VegaComb_HC3.2_Build9b_update3.zip
VegaComb 3.2 Build 9b und 9n Update2 Features:
Fix for Bluetooth MAC addressing to hopefully make BT work correctly now.
Above fix should now also make WiFi considerably more stable.
Fix for people who were experiencing issues with the Market not being able to install apps.
Downloads, please choose the right Version (original ROM download is at the bottom of this thread!)! (or you Bootloop) Update 2 can be installed directly over 9n OR 9n-Update1 (it includes all of the Update 1 and Update 2 changes in a single package):
Update 2 for Build9n: VegaComb_HC3.2_Build9n_update2.zip
Update 2 for Build9b: VegaComb_HC3.2_Build9b_update2.zip
VegaComb 3.2 Build 9b und 9n Update1 Features:
Working Deep Standby
Updated camera lib
Re-added App Drivemount
VegaComb 3.2 Build 9b Features:
•Coarse location discovery (based on WiFi connection) is now working correctly.
•Updated camera libraries to the latest version thanks to the development effort by many (including Eduardo and Redscorpion) over at MoDaCo. Google Talk video chat should now be working, as well as the stock Camera app. Other apps have been tested but there is a possibility that not all of them work (please test and let us know!), but we felt that it was more important for Gtalk to work as the camera isn't much use for actually taking pictures
•Added Eduardo's accelerometer patch. This should allow much more responsive accelerometer with no lag.
•Power management for bluetooth/wireless has been fixed. Hopefully this should stop them interfering with eachother when one is disabled.
•Screen calibration functionality built in to the kernel to calibrate on the fly.
•USB on-the-fly host/slave switcher integrated in to the kernel, this should allow switching between USB host/slave on the tablets side USB port without the need to reboot!
•Disabled device suspend when the tablet is connected to an active USB connection, preventing the USB connection from being severed.
•Added a brand new app called: Shuttle Tools which includes the toggles for the above two options. Allowing you to calibrate the screen or switch USB modes from within Android.
• Better language support then 9n, newer Gapps
• No apps are moved to data
• It have a bigger system partition then 9n, so when you have bad nand blocks, this could be work better for you
• When you use the Full Rom Installer you don´t need to flash ModdedstockV2 (Beware when you flash the new full rom it is like the ModdedStockV2 install, you loose all data)
• All future updates after this Full ROM will come as CWM update zip, so that your data are save
VegaComb 3.2 Build 9n Features:
Please be aware that although there was a "version 9" release on some German forums, this update was never integrated into the full build process, and was a side-project by rebel1 to acheive 2 goals. 1) To greatly increase the /system partition size (from 150mb to 200mb) and use that size to add larger apps that have increased language support for non-english speaking users. This build is unrelated to the previous "build 9" and as such has been labelled 9n (new, or newbe5, meaning that it has gone through the usual build and testing processes by myself), an alternate installer based on THIS build will also be provided by rebel1, including the expanded /system partition and enhanced language capability, this alternate build will be labelled 9b (bigger system, alternate build) and will be an nvflash installer rather than a CWM image.
•System image has been shrunk considerably, this should help people who have a lot of random lockups / install issues due to bad NAND blocks. Build 8.1 was using 149.5mb of the allocated 150mb provided by ModdedStockv2, Build 9n is only using 139.8mb allowing much more room to avoid bad blocks if you have them.
•Google Books has been removed entirely. It looks nice, but it's pointless as you can't even access the Store outside of the US. Install this manually if you want it for some reason.
•Google Maps and Street View have been moved in to /data to save space and because they can both be installed/updated from the market, so there is no need for them to be in /system.
•Coarse location discovery (based on WiFi connection) is now working correctly.
•Updated camera libraries to the latest version thanks to the development effort by many (including Eduardo and Redscorpion) over at MoDaCo. Google Talk video chat should now be working, as well as the stock Camera app. Other apps have been tested but there is a possibility that not all of them work (please test and let us know!), but we felt that it was more important for Gtalk to work as the camera isn't much use for actually taking pictures
•Added Eduardo's accelerometer patch. This should allow much more responsive accelerometer with no lag.
•Power management for bluetooth/wireless has been fixed. Hopefully this should stop them interfering with eachother when one is disabled.
•Screen calibration functionality built in to the kernel to calibrate on the fly.
•USB on-the-fly host/slave switcher integrated in to the kernel, this should allow switching between USB host/slave on the tablets side USB port without the need to reboot!
•Disabled device suspend when the tablet is connected to an active USB connection, preventing the USB connection from being severed.
•Added a brand new app called: Shuttle Tools which includes the toggles for the above two options. Allowing you to calibrate the screen or switch USB modes from within Android.
Current issues:
On rebooting to recovery, the tablet will "hang" on a stale boot. Hold down the power button until the screen goes completely off, and then power back on to get to CWM.
More? Probably! You tell us
SO many people have worked on this, and are now part of the team, but everyone who uses and loves VegaComb have the following Droid Soldiers to thank:
Ejtagle
Rebel1 / [email protected]
Corvus
HomerSp
Cass67
a_appleby
BillyBobJoe (Also BillyTheFish I believe?)
stiggy2001
Oh... I might have done some stuff too
Remember, this MUST be flashed over ModdedStock v2 or it will not work!
This is the one and only way to move to our image:
modstock -> data wipe -> vegacomb 3.2.
Dont ask for help if you dont follow this steps.
Download VegaComb_HC3.2_Build9n.zip NOW! This is for all users that comes from an previous build like 8.1 or ModdeStockV2
For users that comes from my Build9 they can download and flash it with CWM recovery Download VegaComb_HC3.2_Build9b.zip HERE!
And the last file:
Download VegaComb HC3.2 9b Installer.zip HERE!
This is a windows installer for the 9b Full ROM, you don´t need to install ModdedStock before, it makes it all for you
We hope you enjoy VegaComb.
If you are feeling very generous and wish to donate to the people who put in a lot of hard work for this ROM, please:
DONATE TO TeamNewCo HERE!
newbe5 and the Team.
Have fun.
rebel1
Great job guys!
I can hardly wait to test this one out!
Very very speed rom..
Thanks
This week, I'm going to receive my Advent Vega. I believe this is the best Honeycomb ROM available (better than Vegacomb 1.7), is it correct?
Thanks!!
wow, loving this as it really does fly, very impressed.
I've just installed it. It really does fly. Just installing my apps now. Will let you know if I come across any problems.
Sent from my GT-I9100 using XDA App
SHWIINNGGGG!!!
Thank you gtablet gods!!!!
I must say i just installed it and its fast!!!
Faster then my gtablet on gtabletcomb 3.3.
OK so you vega gurus. whats the difference between advent vega/viewsonic viewpad 10s and the gtablet.
why can the roms be ingterchanable and whats the difference.
thanks for the roms guys, Now I dont have a reason to sell it.
youtube restarts itself when you rotate the screen.
Apps from market forcloses...
was using opera for a bit with some flash content, went to the home screen and went back to opera and the tablet resetted itself.
what do you mean by "Native App2SD has been added back in (is not present on 3.2 ROMS as standard)."
Does that mean we dont have to get the app2sd app?
I looked for the app2sd in the settings and is unable to find it.
can you please explain..??
I love it, thanks for your hard work.
awesome build
much much better than beta 1.7
thank you so much for that.
just one question, compare to 1.7, all icons look too big.
different resolution or different density?
I don't think we can change the resolution.
Thanks.
Edit: I use LCD density to make the icons smaller, got wifi error, after uninstall lcd density and reboot, no error.
aarrggg... I'm at work and can't get this till I get home.
5pm can't come quick enough now
Been playing with this since yesterday evening.
You can change the screen Res in your build.prop file. I'm on 140dpi at the moment, many people seem happy with 127
USB host mode doesn't work yet, hopefully not too far away
Everything is really fast. No lag at all. There are a few little oddities here and there but nothing too drastic. An amazing release really.
HDMI out is working? My TV didn't recognize it. Pretty fast. I set the density to 140. Looks better now. Thanks.
Sent from my VegaComb 3.2 using XDA Premium App
cant get to recovery, tried everything, holding powerbutton while reboot, nothing helps, it just reboots...
freddje said:
cant get to recovery, tried everything, holding powerbutton while reboot, nothing helps, it just reboots...
Click to expand...
Click to collapse
You need to hold power button until you see the power down menu, select recovery then it'll hang on reboot, hold the power then until the tablet is forced off and when you power back up, it'll boot into cwm recovery
could someone with an official dock please try and see if they can still connect usb peripherals on this rom, I know you can't directly until they fix it, but was wondering if it still worked via the dock. If so i'll buy one
thanks,
malty
Hi there.
I have been running this for a few hours, i have got to say, its fantastic. So quick and smooth. I think i will be running vegacomb from now on.
Just curious about the keyboard, it seems very small. Is that the stock one for 3.2? No major problem just installed hackers keyboard.
Still not sure about the pixel density, but i can easy change that.
Love the first boot screen, should make it more difficult to bang out a vegacomb clone on ebay
Any tips on getting the accelerometer working properly with games?
Many thanks to you and TeamNewCo, this is a fantastic ROM
Legendary. This rom is awesome.
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.
It seems that contributing to LOS building ROM is not anymore tolerated, this post is deleted.
Maybe @Scavenger87 wants to take a look here ;-)
I guess it's better to have an own dedicated thread.
Thanks for setting up a distinct thread. Things were getting confusing!
john_matrix said:
Maybe @Scavenger87 wants to take a look here ;-)
I guess it's better to have an own dedicated thread.
Click to expand...
Click to collapse
Hey John great idea with opening a new Thread because i also think its really confusing already
john_matrix said:
@Scavenger87: Steel01 advised to let 15.1 (I think he is right because it's too old and because lot of changes have been done between 15.1-16.0)
Also have found this during LOS 16.0 debugging and when application is crashing:
Starting from Android 9, LMK can be implemented in userspace and needs new optimization settings:
Low Memory Killer Daemon | Android Open Source Project
source.android.com
Will see if this new userspace LMKD can be tuned.
@Trevor_g: can't say... I don't have an Nvidia controller to test.
Click to expand...
Click to collapse
Ok yeah i think he's right for multiple reasons
- 15.1 had still unsolved issues aside of broken omx like the crashing nv games app and not working screen mirroring which is working so far on 16.0
- 16.0 is Android 9.0 based which is the same as the actual Software for the Shield TV. That means there is maybe a chance they can use some Codes or even Apps like the Shield Accessories to makes things like the First Controller working again over WIFI.
I even found a lot Nvidia OEM Apps here on APK Mirror : https://www.apkmirror.com/apk/nvidia/
I think i start testing around with those apks as soon i installed the lasted 16.0 build
@Trevor_g
For your question i have to check that again on 16.0 with the old Controller but i think its still only working over a OTG Adapter.
Like i mentioned above maybe the Shield TV Accessories App is working.
mirhl said:
https://gist.github.com/webgeek1234/8ef1bd105d2add3aa9c29028c2befbb0
https://github.com/vartom/drivers-kernel-nvidia-49/tree/smaug49/drivers/hid
https://github.com/devmapal/nvidia-shield-controller-driver
Click to expand...
Click to collapse
Someone even mentioned this Linux Driver for the Controller
But to be honest dont suspect too much on lets say all this bonus functions because first the LOS Team have to work on the base build to make it stable and running right
Ok i installed the latest build (4/1/21) yesterday on my LTE Tablet over sideload because i had no extra SD Card to format it to FAT32 and with the new TWRP 3.5-9.0.
I installed also the Pico Gapps and then TWRP said when i was about to Restart that there's now OS installed.
But thats seems to be a bug with TWRP itself because after the restart there was the LineageOS screen waiting for me and after a freeze for about a minute or two i was able to complete my installation.
After this i now can say its the most stable LOS 9.0 Rom so far !
It has very less apps crashing so far i only had to start them twice sometimes and also the hw acceleration working now most of its time at Chrome and on the Youtube App.
I can really see there has going again a lot of work into this Rom and its really a pleasure now to see how it get more stable everytime.
Big thanks to @Steel01, @npjohnson, the whole LineageOS Team and of course to @john_matrix
Btw @john_matrix did you change anything on the partitions you mentioned earlier on this build ?
@Trevor_g
I did a short test yesterday with the controller and as suspected it doesnt recognize by the tablet. I soon test out those Android 9.0 based Accessories App from the Shield TV
Thank you for the rom
Can I just flash this over Lineage 14.1 or do I need a factory wipe?
Did anybody test gamepass streaming yet?
danielandross said:
Thank you for the rom
Can I just flash this over Lineage 14.1 or do I need a factory wipe?
Did anybody test gamepass streaming yet?
Click to expand...
Click to collapse
Yes you have to wipe the device first in TWRP to install this rom.
Maybe a little general guide for everyone here who want to try this build in this early state and help tracking bugs
For an clean Installation its important to wipe the device first with TWRP like shown on the first Screenshot.
After this go to Advanced and choose everything choosen on the second Screenshot.
Now you shutdown the Tablet and insert the SD Card or plug in the cable for sideloading.
After turning on the Tablet and choose Recovery Mode again, first install the Rom of course then choose Wipe cache/dalvik.
Now you have to install Gapps if you want to use it. Its recommend to use only the Pico Package.
Wipe cache/dalvik again and restart the device.
If you use Sideload it might says in the Shutdown Menu :
No OS installed !
Which is a bug in my opinion of the new TWRP 3.5-9.0 Package but please use this Version of TWRP in any case that the basement of the installation is everywhere the same !
This is IMHO the way to install a Rom in a clean way and helps tracking down bugs better when everyone used the same methodes.
@john_matrix
I installed the Rom today on a K1 16GB with the methode i described above and did it with my regular SDCard i use in all my Tablets. In comparsion to installing over sideload it didnt get the No OS installed! message at TWRP and i didnt had that 1 minute freeze at begin of the install-wizzard after the LOS Logo.
Also the Rom seems to be same stable as the one on the 32GB model.
But i have to test it a bit more side by side to make valid statements
Also Nvidia Games working nice as you can see on the Screenshots
Hi guys, so, long story short i got scammed on a dutch advertising portal and ended up with one of them shield tablets which were recalled a few years ago. Yep, those with the defective battery that may burst in flame one day
Anyways, i figured that since it hasnt happened until now, i might just be lucky and give it a shot.
Its great to see that there is still some active development of this device! flashed this rom and i gotta say im positively surprised. Its running nice and smooth and even though it crashed on me a few times after the first boot, but a few reboots later and its running like a charm! i didnt bother with gapps, root or anything yet though. really great job devs!
Scavenger87 said:
I installed the Rom today on a K1 16GB with the methode i described above and did it with my regular SDCard i use in all my Tablets. In comparsion to installing over sideload it didnt get the No OS installed! message at TWRP and i didnt had that 1 minute freeze at begin of the install-wizzard after the LOS Logo.
Also the Rom seems to be same stable as the one on the 32GB model.
Click to expand...
Click to collapse
My tablet was completely wiped with no OS so I just pushed the ROM, pico gapps, and magisk over USB onto internal storage with MTP/TWRP. Flashed it all from there and it worked fine. No issues or errors. I don't think it's at all necessary to sideload to use an external SD.
Jackill said:
Hi guys, so, long story short i got scammed on a dutch advertising portal and ended up with one of them shield tablets which were recalled a few years ago. Yep, those with the defective battery that may burst in flame one day
Anyways, i figured that since it hasnt happened until now, i might just be lucky and give it a shot.
Its great to see that there is still some active development of this device! flashed this rom and i gotta say im positively surprised. Its running nice and smooth and even though it crashed on me a few times after the first boot, but a few reboots later and its running like a charm! i didnt bother with gapps, root or anything yet though. really great job devs!
Click to expand...
Click to collapse
In this Thread beginning from here i share my informations so far about the two type of batteries and changing them out if you interested:
Finding Replacement Battery in 2017?
Anybody know where to find a battery that will fit in the Shield Tablet? I know there are several threads online (here on xda, on GeForce forums, and other places) that discuss replacing the shield tablet battery and a few different part numbers...
forum.xda-developers.com
airtower said:
My tablet was completely wiped with no OS so I just pushed the ROM, pico gapps, and magisk over USB onto internal storage with MTP/TWRP. Flashed it all from there and it worked fine. No issues or errors. I don't think it's at all necessary to sideload to use an external SD.
Click to expand...
Click to collapse
I did these two type installation because @john_matrix mentioned to use a SD Card which is formated with FAT32 instead of exFAT. I didnt had one lying around so i used sideload this time.
Thank you everyone and Scavenger87 for your feedback! ;-)
About stability, I guess the culprit is the fact I have played with the new userspace LMK but for me it's not stable enough to be used as daily.
For example, Youtube often continue to play videos greeny and blocky and this is annoying
I will try to fine tune the best settings for LMK.
About battery, I have changed mine too with this one:
https://fr.aliexpress.com/item/32807531204.html
It works good but require to use the board of the original battery.
Seems to be going well so far for me, battery life seems good and for the general use I have had time to do it's worked well.
One crash that caused a reboot, after testing the hdmi output the tablet rebooted when I unplugged the hdmi cable from the tablet.
john_matrix said:
Thank you everyone and Scavenger87 for your feedback! ;-)
About stability, I guess the culprit is the fact I have played with the new userspace LMK but for me it's not stable enough to be used as daily.
For example, Youtube often continue to play videos greeny and blocky and this is annoying
I will try to fine tune the best settings for LMK.
About battery, I have changed mine too with this one:
https://fr.aliexpress.com/item/32807531204.html
It works good but require to use the board of the original battery.
Click to expand...
Click to collapse
Ok that means there is still some kind of memory leak problem with our tablets or is the memory managment on android 9 and higher not really suited for our low ram devices ?
I also read something about drawbacks with the in-kernel LMK as you can see here :
Drawbacks of in-kernel LMK driver
Android deprecates the LMK driver due to a number of issues, including:
Low-RAM devices had to be tuned aggressively, and even then would perform poorly on workloads with large file-backed active pagecache. The poor performance resulted in thrashing and no kills.
The LMK kernel driver relied on free-memory limits, with no scaling based on the memory pressure.
Because of the rigidity of the design, partners often customized the driver so that it would work on their devices.
The LMK driver hooked into the slab shrinker API, which wasn't designed for heavy operations such as searching for targets and killing them, which slowed down the vmscan process.
Is the zRam function now activated by standart on Android 9 and higher to compress amount memory is needed ?
I try to stresstest it today with a website that have a lot pictures sadly i cant use instagram anymore because you need a account now
Shield Tablet can't be considered as a "low ram device" as Google defined them with up to 512MB (Android Go?)
Android Performance Optimization | Android Open Source Project
source.android.com
I also have devices with 2GB that are currently performing Lineage 17.1 very well (Sony Z3C and Nexus 4)
I don't know if zRAM is activated by default in Android but you still have the choice to activate it or no (in the kernel or in the fstab.
Additionnally, I don't know what is the policy to activate zRAM (my Mi9 have 6GB RAM and have zRAM activated by Xiaomi so...)
Another thing about zRAM is there are lot and lot of options you can activate such as compression, lz4, clear caching, etc... depending of your needs and I am not skilled enough to say exactly what will be the consequences of these options (but it cost nothing to try).
You also have to keep in mind that zRAM will consume more CPU times (as KSM).
Similarly, you can fine tune the CPU governor and IO scheduling (often I see CFQ by default but on the other way I have saw that Noop and Deadline gives best results).
Feel free to share your experience and if you have other ideas on what you would like to integrate in this ROM (as the best possible).
You are right to stress test the OS, you can also debug the memory and the weight attributed on the processes.
Ok but 2GB is really not much these day also this article from android source is really old i think i read there something about kitkat or so
But your right i also was suprised to see that my xperia z3 compact i have lying around is able to run lineageos 17.1 and even is supported by the LOS Team
Which leads me to the question is the memory managment on the Qualcomm SOC so much better ? Ok the Ram there is on the SOC itself instead of external like on our Tegra based devices.
I think i install tonight Triodexes 15.1 with zram to compare the effect it has.
I also noticed the hw acceleration crashes the most on the firefox browser like i told in the 15.1 Thread you can start one video and it runs if you leave everything untouched but your not able to start a second one even with autoplay.
Btw about the LMK i know its maybe a dumb question but did you try the original settings from the Oem Rom ?
Edit : The original values in minfree are: 18432,23040,27648,32256,36864,46080
And zRam is already activated on the LOS 16.0 Build with 511MB same like the oem rom
Scavenger87 said:
I did a short test yesterday with the controller and as suspected it doesnt recognize by the tablet. I soon test out those Android 9.0 based Accessories App from the Shield TV
Click to expand...
Click to collapse
Thanks SO much for looking into this for me! You mentioned later that the controller wasn't recognized by the tablet, however I'm also curious if the Accessories app from the ShieldTV might help. Thanks again, in advance!
Fwiw, there's a bunch of framework patches needed for the wifi direct controller to work. I've yet to get them all straight. Haven't had that working since cm-12.1. See the incomplete set for 16.0 here:
https://review.lineageos.org/q/topic:shield-blake-p
That's on top of:
https://review.lineageos.org/q/topic:nvidia-shieldtech-p
And there's no nvidia pairing app that works with a touch interface. It's a mess atm. I did get blake to pair to foster on 15.1, but only while the pairing wizard was open. As soon as I hit back to close it, the autonomous group goes down and the connection is lost. And now, it's close to impossible since nvidia didn't release the nvwifi prebuilt jar to link against. And the one from O doesn't work on P.
Hi @Steel01
Thank you for keeping us updated on your work with the controller and also for your work for this device in general
I already tought its not easy to bring wifi support back for the old controller but i think also there is no high priority since the second gen is working fine over bluetooth and they already cheap to buy used.
Other than this the rom is suprisingly good running for this early stage and most of the stuff is working
Is there something that needs special attention for testing at the moment to help you developing ?
Like i mentioned in a other Thread i have every generation of the Shield Tablet and Controller. Only on my LTE Modell the SIM Card Reader is unfixable broken
But i still hunting for a fully working device.
Before I flash this Rom: Why do I habe to wipe internal storage?
danielandross said:
Before I flash this Rom: Why do I habe to wipe internal storage?
Click to expand...
Click to collapse
Well i dont know if its really needed to wipe the internal storage but i think by the reason we testing here a new Rom in a really early stage we should give it the cleanest basement as possible to exclude problems that might caused by left over data that interference with the Rom