Instructions:
1. Download ZIP file and flash it (Cyanogenmod 12 is what i tested it on).
2. Install in recovery and reboot
3. Voila
Downloads:
nvsystemservices.zip Download here.
Bugreport: Report in this thread. This is still in testing.
Known Problems:
Issues connecting the controller (reboot works sometimes)
No console mode
Audio only routed to controller (and it is bugged aswell)
My thanks goes to:
Steel01
Version Information
Status: Testing
Created: 2015-04-01
Last Updated: 2015-04-01
XDA:DevDB Information
SHIELD Apps for Cyanogenmod 12, Device Specific App for the Nvidia Shield Tablet
Contributors
silasje1, Steel01
Version Information
Status: Testing
Created 2015-04-01
Last Updated 2015-05-26
Reserved
Awesome!!
Current info is going here since I can't truly edit the OP or reserved posts.
Several apps work out of the box on any ROM with correct vendor blobs. The only blobs I've seen have issues are the OMX libs. The ones from Nvidias AOSP work correctly. The easy apps are:
Shield Hub (this includes gamestream and Grid)
Dabbler (full stylus support with palm detection and all that fancy stuff)
No support (yet):
Controller Mapper (I don't personally care to work on this)
Game cast (or whatever the stream to Twitch and such thing is called)
Partial Support:
Wireless Controller Pairing (see explanation below)
Console Mode (see explanation below)
Wireless Controller Pairing:
As of this last edit, all ROMs based on my CM-Shield repo have this functionality. That's virtually all custom ROMs now. Though support may be too strong a term. It kind of works, but with a few caveats.
1. Pairing can now be started from the SHIELD Controller app icon. After pairing, the app will not close, so just hit home or back to get out of it. If the light stops blinking on the controller, it's connected.
2. In Development Settings, the disable usb audio routing option needs to be enabled otherwise the tablets internal speakers will be disabled due to a lib misreading something. I have yet to find a workaround for this. Headphones plugged into the tablet work fine and headphones on the controller work, but is crackly. I expect HDMI audio will work as well, but that is not tested.
3. If the wireless band changes (connecting to a 5 GHZ band from a 2.4 GHZ one or vice versa), the controller will drop and you'll have to reboot to get it back. Not certain what can be done about that yet.
4. Occasionally, I have seen the controller fail to reconnect after both the shield device and the controller have gone to sleep. It didn't happen every time, though, and rebooting will cause an auto reconnect.
Console Mode:
The official app works as expected with one small caveat. If the hdmi cable is disconnected while in console mode, the display will rotate to landscape, but the touch orientation will still be portrait. This should be able to be fixed with another small patch once I know what the app is expecting.
Previously, I made a script that toggles console mode that might still be useful. Touch goes to portrait mode while in console mode and I haven't figured out how to rotate that yet. Other than that, it seems to work pretty well. It just isn't terribly useful until wireless controller pairing works unless you have a bluetooth controller or a keyboard/mouse combo plugged in. I'm also restarting all services and that probably isn't necessary, but I don't know how to track down which ones really need restarted. For general use, this should be put into the control app with a section watching hdmi. And when hdmi is disconnected (and isn't reconnected within 5 seconds or so), switch back to the internal display.
Code:
#!/system/bin/sh
# Toggle console mode
DEVICE=$(getprop ro.product.device);
CONSOLE_RES="1920x1080";
WM_RES="1200x1920";
if [ "${DEVICE}" == "roth" ]; then
WM_RES="1280x720";
fi;
if [ "$(getprop persist.tegra.stb.mode)" == "1" ]; then
# Switching console mode off. Window Manager uses default resolution.
setprop persist.sys.display.resolution "";
setprop persist.tegra.hdmi.primary 0;
setprop persist.tegra.hdmi.resolution Max_60;
setprop persist.tegra.stb.mode 0;
if [ "${DEVICE}" == "roth" ]; then
setprop persist.tegra.panel.rotation 90;
fi;
else
# Switching console mode on. Window Manager uses console resolution.
WM_RES=${CONSOLE_RES}
setprop persist.sys.display.resolution ${CONSOLE_RES}
setprop persist.tegra.hdmi.primary 1
setprop persist.tegra.hdmi.resolution Max;
setprop persist.tegra.stb.mode 1;
if [ "${DEVICE}" == "roth" ]; then
setprop persist.tegra.panel.rotation "";
fi;
fi;
wm size ${WM_RES};
restart;
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------OLD POST:
Alright, info dump.
@OP: you should link or copy over the patches I made to cm to allow controller pairing. And more may be needed to make it stable.
Grid should work out of the box on any ROM that has the vendor blobs set up properly. More or less, just needs the OMX libs from nvidias aosp. Just download from the play store and go, don't bother with anything here. Same for Dabbler.
Controller mapping is pretty much entirely framework and internal ROM changes. To me, this seems pointless to replicate since Tincore does the same thing and is free. But if someone else want to implement it, go right ahead.
Console mode. I have posts for the tablet and the portable in my cm threads about this. I can set some props and reboot a couple times to make it work. It just isn't clean yet. I'm wanting to make this part of an open source control app. I'll add the info here when I have a fewxminutes at my desktop (which might be a few days...)
Controller, the one most people (and me) really care about. Yeah, I kinda made it work, but it's flaky. What really needs to happen is for someone to decompile the official pairing app and figure out the pairing sequence. Then it can be implemented in an open source app and for Linux. I haven't had time to get to that yet. Side note: I've had issues with the controller on stock when booting through multirom. If you have problems, try with a bare metal install, no kexec, nothing extra.
Thanks for the continued efforts to get this working.
The zip was installed with a clean flash, but I have no controller app for me to pair it.
ah ... if they worked. Then im keep stock rom and flashing cm 12.1
On cm 12 the flashable zip works on cm12.1 i dont get the app icon (but the APK are there)
silasje1 said:
On cm 12 the flashable zip works on cm12.1 i dont get the app icon (but the APK are there)
Click to expand...
Click to collapse
Noticed that too. When I did get mine working on CM12 there is no audio on GRID games.
Yeah the audio is routed to the Controller (and the audio that comes from the controller is bad )
I don''t know why the apps don't work. I will wait for the next OTA from nvidia and see if i can make it work then. I anybody wants to try feel free to
The only reason I still like stock is the gamepad mapper. This zip does't seem to fix it on CM12 or 12.1
FoxyDrew said:
The only reason I still like stock is the gamepad mapper. This zip does't seem to fix it on CM12 or 12.1
Click to expand...
Click to collapse
It is advertised as having issues with all the stock features besides GRID, we're all working on this right now though.
CM12.1 will soon reign!
berryman13 said:
It is advertised as having issues with all the stock features besides GRID, we're all working on this right now though.
CM12.1 will soon reign!
Click to expand...
Click to collapse
Legendary
I've been just waiting on someone saying this very thing. Thank you.
Cool, I'm waiting your result (hope dabler and controller paring will be work)
Pardon me for my stupidity. I made an error in the flashable zip. BUT, i fixed it and i uploaded a new version in the Downloads Tab
Please try and report.
on cm 12.1 and 12 does not work, even in the list of applications installed no
Would it be possible to do a TiBu or Parcel backup then just restore them back on the ROM you're using? Is it a vendor issue not allowing everything to work?
Not that easy, unfortunately. The apps that would work like that are already on the Play Store. The controller app requires framework changes like I mentioned in post #3. The controller mapper is integrated into Nvidias Android release, there isn't even an icon to run it. I'm planning on trying to reverse engineer the controller and console apps, but that's after I solidify my CM and Multirom releases. Might be a while yet...
It probably doesn't work in cm12.1 for one of two reasons. 1, the signing keys changed between cm releases. 2, those builds don't have my wifi changes to hackishly support the controller. If it doesn't even show in the list, it's likely the first.
Steel01
romixer said:
on cm 12.1 and 12 does not work, even in the list of applications installed no
Click to expand...
Click to collapse
Don't know what is going wrong but i delete the download untill i have more time to look into it.
Edit:
i will come back when Nvidia has the new ota 3.0 (based on 5.1) ready and add the files then
Sounds good
silasje1 said:
Downloads:
See Downloads Tab (empty for now)
Click to expand...
Click to collapse
Derp, can't find no Download Tab. Yes, I'm that dumb .
Btw, so this on 12.1 is a go?
Related
NOTE TO MODERATORS: I have discovered a workaround solution to a bug that plagues many android devices running 2.3.5 and 2.3.6, however I cannot post in the development forum. If this thread is moved to the development forum please unlock my ability to post in that forum.
Like many of you I was extremely excited to learn that android now supports HID devices and immediately rushed out to purchase a HID-BT Keyboard. Getting home, I fired up the phone and keyboard, entered the 6 digit code to pair them and saw the device connecting and disconnecting in an infinite loop. I was crushed and disappointed.
What went wrong? As stated above this is merely a workaround. But the problem lies somewhere between the kernel and broadcom chipset. This fix will reset your bluetooth pairings. It has been tested on my Samsung Galaxy SII I727 but it should work with any other device.
-----------------------
The Fix (Workaround)
-----------------------
While this works for me it is not guaranteed to work for you, and while it is unlikely to brick your phone, you could be left with non-working bluetooth. So please make sure to backup all files, especially /system/bin/btld This tutorial assumes a certain level of knowledge about android, if this does not make sense to you PLEASE do not try this!!
1. Make sure that your bluetooth is turned off under settings
2. Download a file manager like ES File Explorer with root capabilities
b. Optionally you can push your files over adb, but I will not cover that in this tutorial.
3. Backup /system/bin/btld to a safe location on your device.
4. Backup /data/misc/bluetoothd/XX:XX:XX:XX:XX:XX/ (where XX:XX... is the MAC of your device)
5. Delete the folder titled with your MAC under /data/misc/bluetoothd/
6. Download the zip file contained as an attachment to this thread
7. Extract btld anywhere on your device.
8. Copy btld from the zip to /system/bin/btld (you must have root access)
9. Set btld permissions to 0755
10. Restart your device.
11. Go into bluetooth settings, pair the phone with your HID device.
b. You might get a prompt to enter a keycode on device 00:00:00:00:07:00; this is a ghost device, harmless but a bit annoying, just hit ok and ignore it
12. Your phone should pair and connect with your HID device.
b. If your phone does not connect, stop here and post back on the forum.
13. Turn off bluetooth DO NOT TURN IT BACK ON UNTIL COMPLETING THE FINAL STEPS OR YOU MIGHT HAVE TO START OVER
14. Open your file explorer, go to /data/misc/bluetoothd/XX:XX.../
b. You should see a file titled hidinfo, open it with a text editor
c. Delete the CONTENTS of this file and save the file
d. Set permissions to 0444 (read only) for hidinfo
15. Restart your device
Bluetooth should be working properly with your HID device. You might continue getting a prompt to pair with a ghost device, just hit ok and ignore it.
Reserved....
Working on Samsung Galaxy i8150
Confirmed working for my mouse on Galaxy Wonder I8150. Android 2.3.5. I do however see the ghost device, but that's not a problem.
Although it seems to be working for a single device at a time, I have trouble using a mouse together with a headse. The pairing process had to be done a number of times before succeeding. It requested the pairing pin code, but sometimes requests the pin code for a "" device. (the headset is a Phillips SHB6017 and supports a2dp audio profile + headset profile)
Sometimes both devices won't connect at all, sometimes the status is connected, but it doesn't actually work.
All in all to much trouble for me. I'm reverting back. Thanks for the effort so far.
Although I have not tried pairing multiple devices, I'll try with a headset and keyboard tomorrow, you can ignore pair requests from device "". I only paired my keyboard once and it just works, although I do get requests from "" whenever I turn on bt that I ignore.
I was in a situation where hid wasn't working at all though, so the trouble is worth it for me
I'll test with two devices tomorrow
Just want to report that I have no trouble connecting with my Blueant BT and Logitech for Android KB on my I727 Samsung SII LTE. I find that once I pair the devices they connect automatically most of the time once turned on. My BT didn't pair automatically once but I just power cycled it and hit the connect button and it worked.
If anyone else has tried this fix please report your results so others can learn from it
Glad it works for you. Here are the devices I used.
My mouse is a Logitech Laser Travel Mouse (blue). The Headset is a Phillips SBH6017.
I did try to power cycle and ignore the "" requests, and I eventually could get both devices paired and connected. But the sound will not play over the headset. Reconnecting didn't help much. When I reverted back it worked instantly(headset) but the mouse (as expected because of the HID bug) doesn't work after reverting back.
thank you so mutch... i bought an A4Tech Mouse BT-630 to use it whit Samsung GSII I9100, MHL and an LG LCD TV to watch videos on Youtube when my brother is at the PC and it would paire but not connect... i was so dissapointed thinking that the mouse is not good and i just wasted my money on it. I folowed your tutorial and i can confirm that it works! Thanks againe !!! PS: english is not my native language...
I was really excited when I saw this post. But it didn't seem to work. I got to step 4. There was no file showing up with my MAC address... no files at all in that directory.
I went ahead anyway. One thing to check: I set the permissions of the btld to:
user: read, write, execute
group: read, execute
other: read, execute
Is that right? There are no numbers in the choices.
Also should the btld file go directly into /system/bin/ folder? Or should there be another folder there: /system/bin/btld/btld
SPH-D700, Samsung Epic
2.3.6, EL30
SleeperRom
zeckwoy said:
I was really excited when I saw this post. But it didn't seem to work. I got to step 4. There was no file showing up with my MAC address... no files at all in that directory.
Click to expand...
Click to collapse
If you've used bluetooth on the device even once those files should be automatically generated by the bluetooth driver. Please confirm that you are in the root directory under /data/misc/bluetoothd/ It should be a folder with your MAC and files inside, this folder needs to be generated for the fix to work.
zeckwoy said:
I went ahead anyway. One thing to check: I set the permissions of the btld to:
user: read, write, execute
group: read, execute
other: read, execute
Click to expand...
Click to collapse
Those are the right permissions for btld, btld should go under /system/bin/ directly. You should backup the old file before doing this so that you can revert if needed.
jaapsen said:
Glad it works for you. Here are the devices I used.
My mouse is a Logitech Laser Travel Mouse (blue). The Headset is a Phillips SBH6017.
I did try to power cycle and ignore the "" requests, and I eventually could get both devices paired and connected. But the sound will not play over the headset. Reconnecting didn't help much. When I reverted back it worked instantly(headset) but the mouse (as expected because of the HID bug) doesn't work after reverting back.
Click to expand...
Click to collapse
Could you describe the order that you power on your devices when they don't work, or the order that you've found has worked? I do find that sometimes my BT headset won't connect automatically but if I go under settings/bluetooth and hit to pair with it it connects successfully and works.
The fix isn't overly complicated, all you're doing is really replacing the bluetooth stack with an older version. Did you delete the contents of hidinfo under data/misc/bluetoothd/XX:XX:XX../ and set permissions to read-only?
Sorry, it doesn't work for me. I get the same message as always:
"Sorry, but HID device is not supported on this phone."
I get that when I try to pair. I have two different keyboards, and both get the same response.
The one keyboard did work when I was running ICS Cyanogen Mod (without your fix), but doesn't work when I run Sleeper Gingerbread (with your fix.)
Thanks anyway. Wish it worked!
Hello,
i have a same problem with my 2.3.6 on my Galaxy note N7000
my HID bluetooth device Also Samsung .. after upgrade to the new 2.3.6 version
my Headset cannot pair ..
please i think i need your BTFIX file .. but it seems i'm not be able to use it .. it said " CRC error " the file was corrupt ..
please i need your new file ..
Worked
Awesome, thanks! (galaxy note 2.3.6)
Did not help me on Galaxy W
This did not help me on Black Notes Hybrid 2 nor Bionic Cow 2. Interestingly - Bluetooth works great on stock ROM.
Re: Did not help me on Galaxy W
dushino said:
This did not help me on Black Notes Hybrid 2 nor Bionic Cow 2. Interestingly - Bluetooth works great on stock ROM.
Click to expand...
Click to collapse
Update from me: After some experiments I found that the problem was in kernel! (Samsung Galaxy W, Bionic COW ROM or Black Notes Hybrid 2) When I installed
stock kernel, Bluetooth started to work without modififying any configuration files or replacing a single binary.
Please note that there is a lot things what can go wrong when something does not work. It means that I am not saying kernel replacement solves it all - receipt mentioned here still might work for you.
Galaxy Exhibit
I have an Exhibit II, now called Galaxy Exhibit in its new 2.3.6 firmware. The 2.3.5 firmware actually worked well with my Logitech Android Tablet Keyboard but 2.3.6 didn't. Following the lead of this post I replaced btld with the version from the previous firmware and that worked -- once. Now that I have also made the changes to hidinfo.txt it seems to be working better -- EXCEPT that I am getting the Settings app crashing nearly every time Bluetooth is turned on or off.
Also I think the Home button on the keyboard was working that first time, but it isn't working now... and the keyboard is not listed under paired devices.
it woked for me.thank u very very much genius.
I can't overwrite btld... How do i overwrite it?
Close, but no cigar ... (SGT P1000 running 2.3.6)
tommystery said:
NOTE TO MODERATORS: I have discovered a workaround solution to a bug that plagues many android devices running 2.3.5 and 2.3.6, however I cannot post in the development forum. If this thread is moved to the development forum please unlock my ability to post in that forum.
Like many of you I was extremely excited to learn that android now supports HID devices and immediately rushed out to purchase a HID-BT Keyboard. Getting home, I fired up the phone and keyboard, entered the 6 digit code to pair them and saw the device connecting and disconnecting in an infinite loop. I was crushed and disappointed.
What went wrong? As stated above this is merely a workaround. But the problem lies somewhere between the kernel and broadcom chipset. This fix will reset your bluetooth pairings. It has been tested on my Samsung Galaxy SII I727 but it should work with any other device.
-----------------------
The Fix (Workaround)
-----------------------
While this works for me it is not guaranteed to work for you, and while it is unlikely to brick your phone, you could be left with non-working bluetooth. So please make sure to backup all files, especially /system/bin/btld This tutorial assumes a certain level of knowledge about android, if this does not make sense to you PLEASE do not try this!!
1. Make sure that your bluetooth is turned off under settings
2. Download a file manager like ES File Explorer with root capabilities
b. Optionally you can push your files over adb, but I will not cover that in this tutorial.
3. Backup /system/bin/btld to a safe location on your device.
4. Backup /data/misc/bluetoothd/XX:XX:XX:XX:XX:XX/ (where XX:XX... is the MAC of your device)
5. Delete the folder titled with your MAC under /data/misc/bluetoothd/
6. Download the zip file contained as an attachment to this thread
7. Extract btld anywhere on your device.
8. Copy btld from the zip to /system/bin/btld (you must have root access)
9. Set btld permissions to 0755
10. Restart your device.
11. Go into bluetooth settings, pair the phone with your HID device.
b. You might get a prompt to enter a keycode on device 00:00:00:00:07:00; this is a ghost device, harmless but a bit annoying, just hit ok and ignore it
12. Your phone should pair and connect with your HID device.
b. If your phone does not connect, stop here and post back on the forum.
13. Turn off bluetooth DO NOT TURN IT BACK ON UNTIL COMPLETING THE FINAL STEPS OR YOU MIGHT HAVE TO START OVER
14. Open your file explorer, go to /data/misc/bluetoothd/XX:XX.../
b. You should see a file titled hidinfo, open it with a text editor
c. Delete the CONTENTS of this file and save the file
d. Set permissions to 0444 (read only) for hidinfo
15. Restart your device
Bluetooth should be working properly with your HID device. You might continue getting a prompt to pair with a ghost device, just hit ok and ignore it.
Click to expand...
Click to collapse
Sadly, no luck on my SGT P1000 running Overcome(4.1.0) GB 2.3.6. Most of the steps work fine, but at the moment of connection the tablet reboots and I must start over. I really was hoping this workaround would work as I am very happy with my current configuration, and perfection would be being able to connect to my HID keyboard. Thanks anyway for the post! :good:
Getting same type of problem
I have a Galaxy Nexus and I CAN pair with a Dell BT mouse but I don't get a pointer. Would this fix work on my phone or is there another problem. I looked all over for a fix and I seem to be the only one with a GNex having this issue. Mouse tested and works on Thunderbolt. My Bluetooth works with BT headphones. Any help is greatly appreciated.
Samsung Galaxy Nexus
android version: 4.1.1
Base Version : FF02/FG02
Kernal Version : 3.0.42-Air_kernal_stable_G512mhz_for_JBN
AOKP version : AOKP_toro_jb-build-1
build number : JRO03H
Android 4.2.2 / Jelly Bean for Toshiba Folio 100
This is the current state of CyanogenMod 10.1 for the Toshiba Folio 100
READ THIS:
This version used a different partition layout from all previous ROMs. The /sdcard partitions is now emulated on the /data partition like on all current ROM's.
All your data will be lost when updating to this ROM. You will also have to reformat the /data partition our you will have issues.
If your device should not boot after formating the partion and flashing everything then go to recovery and format the data and media partition again.
DOWNLOAD:
Alpha 2:
cm-10.1-20130530-UNOFFICIAL-betelgeuse.zip
MD5: c368ffb6330f469032c49b39ce78f233
Changes:
* Fixed 3G connectivity
* Upsteam CM fixes
Alpha 1:
cm-10.1-20130217-UNOFFICIAL-betelgeuse.zip
MD5: 0239505b69312c082b70404c2f839ca9
Recovery:
recovery-cwm-CM10.1.zip
MD5: 50ea4efaf05a2c5ba61cf92c406788a7
GOOGLE APPS:
Please download the last non-neon gapps from here:
http://goo.im/devs/tonyp/non-neon-gapps
SOURCE CODE:
The git tree is here:
https://github.com/DerArtem/android_device_toshiba_betelgeuse
https://github.com/nopy/android_device_toshiba_betelgeuse
Kernel sources:
https://github.com/DerArtem/android_kernel_toshiba_betelgeuse
Things that work:
Kernel 3.1 - rel-15r7
HQ Video acceleration
Audio over Speaker
Audio over Headset
Audio over HDMI
HDMI Video
Camera - reported as front and back camera
3D acceleration
LP0 Suspend
Wakeup from LP0 Suspend
Internal USB
USB Host Port
Acceleration Sensor
Power Button
Volume Keys
Touch Screen
Wifi
Brighness regulation
Internal and external SD
Vibrator
miniUSB Hotplug
Docking station
Audio jack switch
Internal microphone (sound is little quite yet)
Touch Buttons
Voice and Data connections using Huawei 3G dongles (UMTS only)
Things that don't work yet:
Bluetooth
A2DP Audio over Bluetooth
SCO Audio over Bluetooth
Digital Compass (Android lib not finished yet - Kernel part finished)
Remote control - initial support added - need more inventigation
Power cable plug detection can take up to 10 seconds
Device may hang during reboot / shutdown - long press the power button to shut it down
Installation:
Install the correct recovery using fastboot or zip file.
Copy everything on the the SD card and install the ROM using the recovery.
You must do a full wipe and format the data and media partition (/sdcard) before installing the ROM using CWM recovery.
Do a full wipe before installing this ROM the first time.
Credits:
DerArtem
Nopy
The Cyanogenmod Team
The other Tegra Dev Teams where we have borrowed code (Adam, GTab, Vega, AC100)
And everybody else who I might have forgotten.
If you like this ROM please don't hesitate to hit the donate and thanks button.
The build target for Folio 100 was submitted upstream to Cyanogenmod:
http://review.cyanogenmod.com/#/c/22586/
RESERVED
Awesome, I'll try later today.
Did I miss something ?
Where are the files to download...
dot251 said:
Did I miss something ?
Where are the files to download...
Click to expand...
Click to collapse
I can´t see it too
maybe it's a early easternegg
Good job.
As I see we will have some new updates to our Folio 100. Keep it up.
Sorry, had some troubles with file hosting, as hosting on github is not possible anymore. The files are available now.
thanks, for this download and for this job, !
Thanks DerArtem, Downloading......
Great! Thank you.
Can we change the status bar? I like the old one...
why is it notcould it be running in tablet mode by default?
wake-up sometimes does not work (especially after plugging USB)
keyboard crashes(hides) when typing fixed after reinstall
Oh and thanks o (◡‿◡✿)
Nice work !!
It's a nice rom !!
The rom works smooth.
Also panorama photo works with external cam !!
DEMO of the rom: http://www.youtube.com/watch?v=qz4fNxZkAYo
DEMO of multiple users : http://www.youtube.com/watch?v=hHnKA4BJ83c
Only one word : great
Thanks very much for this 3 years of work, always better and, safe my folio...
Goo.im server Offline! Could upload on Dev-Host?? Thanks
Ok...working again!
Hello DerArtem,
As usual, very good job. The rom is smooth and very responsive. Navigation is as smooth as Nexus.
I hide the navbar since physical buttons still work (expandable desktop). To replace it, Deskbar is good.
The multi-user works very well I configure with Multi-User App.
I did some tests:
AnTuTu: 6369
High quality FPS: 40.4 on Epic Citadel
Played GTA VC, The Bard's Tales but Jet Set Radio did not seem to get started.
The partitioning is great. This is better than 4.1.2, great! We have all the internal storage for data.
The wifi was temperamental in the first start, but he looked into now.
But I often SOD.
It's great to see that you continue to work on Folio. Thank you very much.
Good luck for the future.
USB 3G dongle doesn't work. I have a huawei K3715. In Android 4.1.2 is it working. It is strange I can find nortwork providers and also connect but the internet doesn't work. He said that i'am connected with Proximus (My provider in Belgium). But internet is not working.
Can anyone help me? Or ist it a bug DerArtem?
Sometimes my folio don't wake up from hibernate.
But it is a good rom for the begin of android 4.2.2 !!
GO DerArtem !! You can it.
I read that CM does not have and does not support Tablet UI. It damage not to find the status bar and notification bar in the navbar. It's more convenient, you can expect a small patch homemade?
Otherwise, I tried the 160 and 213 dpi, it works.
PS : The Google translation makes me very scared.
probleem with power button. folio doesn't wake op after 10 seconds or more.
keyboard disappears after keypress. I don't no how to swipe correctly.
perhaps we need a detailed instruction how to wipe the memory completely and further installation, like the one in version 4.1.2
did a reinstall of 4.1.2 and will wait for the next version.
12/3: had to install 4.2.2 again. same problems but found some workarounds. for the keyboard i disabled the automatic text correction. no more sod after installing advanced wifi lock. this way 4.2.2 is great.
Kang-A-rom
What is it?
a kang of purity rom with a few added functions. It is based on the hard work of others and no credit to me is implied, other than merging and building. All sources are available at:
https://github.com/lostdeveloper
Features:
* Full dac support, on boot, hot plug, volume control
*OC of CPU and GPU
*OTG while charging, fastcharging
*support for most dvbt tuners including the newer r820t tuners.
*automatic mounting of ntfs and exfat storage drives with read and write support
*easycap support, plug n play (requires carcam app)
*firm sleep
*wakelock blocker
*usb/bluetooth tethering (unconfirmed)
*more, and more coming....
Kangarom V2 03/09/2014
Changes:
*plug and play any easycap device (needs carcam app, and one model also needs firmware)
*added support in ramdisk and frameworks/base for USB tethering and bluetooth tethering. I have no way to test this, it needs testing, and I need logcats with any issues. I am completely unsure If I have everything here.
*included dashclock and simple explorer, both open source and useful, while not consuming a lot of space
*Wakelock Blocker, selectively prevent certain wakelocks to save battery
*all purity rom updates from DariosF
Download
http://d-h.st/qOT
________________________________________________________________________________________
Older Changelogs and
Downloads:
Kangarom v1, initial release
http://d-h.st/QXB
_____________________________________________________________________________
other info:
-some models of easycap may also require a firmware to function properly. These firmwares must be obtained by the end user and cannot be included by me for legal reasons. However, they can be downloaded freely from proper sources.
-use of dvbt tuners requires a script to load the needed modules and set up for chrulri's droidtv app.
-firm sleep, and dac on boot require crue's powermanager app to set options for firm sleep, fixed install mode, and fastcharge in hostmode
**The latest version of crue's app may be found here:
http://forum.xda-developers.com/showpost.php?p=50265682&postcount=411
Credit is his, so hit his thanks button.
More INFo about this can be found in my kernel thread, as well as links to the source code used for this:
http://forum.xda-developers.com/showthread.php?t=2558717
Im working on a tilapia build.....not yet.
feel free to ask any questions... Im not too concerned about hardcore dev stuff only. Anything that helps others find answers works for me.
reserved
one more.
would be cool if you could post more information for the dvbt driver
i used mine on usb rom as radio with wavesink and this driver: https://play.google.com/store/apps/details?id=marto.rtl_tcp_andro&hl=de
do i need the driver app now or only wavesink? or wavesink and a script?
EDIT:
and should i flash your kernel over the rom or is includet?
Awesome. Going to try this out right away. Thanks.
michiil said:
would be cool if you could post more information for the dvbt driver
i used mine on usb rom as radio with wavesink and this driver: https://play.google.com/store/apps/details?id=marto.rtl_tcp_andro&hl=de
do i need the driver app now or only wavesink? or wavesink and a script?
EDIT:
and should i flash your kernel over the rom or is includet?
Click to expand...
Click to collapse
Yea....I wanted to get the build up for you all, but I need to set up the OP properly just really busy. Kernel is included already...... dvbt will work as it use to with sdrtouch and other radio apps that use the userpace driver. To watch tv youll need to use a script to insmod the right modules....again ill link to the exact post when I have time, just search my kernel thread for r820t you will find it.
While these modules are loaded, your radio app wont work....it depends on that userspace driver and it wont have a device to "drive" because it is already loaded at the kernel level. So, the solution is a "load" script for kernel modules, then watch tv, then, an "unload" script...... and now your radio app will work again.
I will seriously fill those first three posts will all the needed info, but Im swamped right now with work. All the info is there in the kernel thread for now just need to search.....sorry.
Flashed this and worked right out of the bag, no need for external OTG apps. Ran PAGAPPS mini modular and is perfect for my needs. This came just in time as I'm getting my DAC in the mail tomorrow and plan on putting this in the dash of my car very soon thereafter. Thanks for all your hard work!
The only thing I think would be awesome is if you could incorporate volume buttons on the nav bar. I've never used Timur's rom but saw some videos and saw he had those. If not it'll be easy enough to get by. Thanks again!
sreister said:
Flashed this and worked right out of the bag, no need for external OTG apps. Ran PAGAPPS mini modular and is perfect for my needs. This came just in time as I'm getting my DAC in the mail tomorrow and plan on putting this in the dash of my car very soon thereafter. Thanks for all your hard work!
The only thing I think would be awesome is if you could incorporate volume buttons on the nav bar. I've never used Timur's rom but saw some videos and saw he had those. If not it'll be easy enough to get by. Thanks again!
Click to expand...
Click to collapse
Yes, its kindve on the list......sort of. The new kitkat framework only supports five total buttons on the navbar. Purity allows you to add two more already, but due to framework limitations I think it will be difficult to do this in a stable way. I was browsing around and i noticed that carbon ROM has a more involved navbar framework where you can set the navbar to launch volume control via "slim shortcuts." I got excited and thought it just needed to be cherry picked but....... I downloaded carbon ROM to try it and when i set it up the systemui crashed and repeatedly crashed until I rebooted. Once rebooted it once again crashed, I had to re flash the ROM and the same thing happened, so no go. This behavior is what I read should be expected if you try anything other than a menu button or a search button, or keyboard cursors on the kitkat navbar. In other words, any other button type would need to be fully implemented into the framework, no shortcuts. Im still researching this.....as time permits
The more likely scenario involves the quick launch shortcuts. With this ROM you can set up the home button for three on screen shortcuts via long-pressing the home button. If you download a volume control app, not a widget, an app, then you could use this quick launch method to access it. Or, you can already set it to open up settings>sound with the activity picker. I use "slider widget" for now.....simple desktop widget for volume control.
Super super suuuppperrrr silly question, but this is 4.4.2 right?
ZenInsight said:
Super super suuuppperrrr silly question, but this is 4.4.2 right?
Click to expand...
Click to collapse
Absolute latest from Google, yes.
This works pretty good on my in dash nexus 7. Couple of issues though... I use Bluetooth tethering from my phone, the tablet will connect but I have no internet connection. Also, I use an external microphone for voice commands, but it doesn't work on this ROM. I normally use AOKP ROM with Timur's kernel, this disables the internal mic and allows me to hook my external mic directly to the inputs of my Behringer UCA202 DAC. Also, the easycap issue that you've already mentioned in your kernel thread. Good work so far!
Sent from my SGH-I747 using xda app-developers app
And it goes in as the daily driver. Thanks for your efforts.
Sent from my SM-N900T using Tapatalk
gregthomas129 said:
This works pretty good on my in dash nexus 7. Couple of issues though... I use Bluetooth tethering from my phone, the tablet will connect but I have no internet connection. Also, I use an external microphone for voice commands, but it doesn't work on this ROM. I normally use AOKP ROM with Timur's kernel, this disables the internal mic and allows me to hook my external mic directly to the inputs of my Behringer UCA202 DAC. Also, the easycap issue that you've already mentioned in your kernel thread. Good work so far!
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I did not know about the external mic in usbrom.... Im not sure how easy it will be to figure out, but usb tethering and bluetooth tethering I can kang from cm11....
Ive got a fix for easycap devices as well..... if tilapia build tests well then ill try the tethering thing next.
redeyedjedi said:
I did not know about the external mic in usbrom.... Im not sure how easy it will be to figure out, but usb tethering and bluetooth tethering I can kang from cm11....
Ive got a fix for easycap devices as well..... if tilapia build tests well then ill try the tethering thing next.
Click to expand...
Click to collapse
Its actually a combination of Timur's kernel and AOKP ROM, not USBrom. So I guess the kernel is what makes it work because if I run plain AOKP and the kernel that comes with it, then it operates the same as your ROM does... internal mic works, DAC inputs do not. I install AOKP and then Timur's kernel over top of it. Not really sure if it was intended that way but its the only way I've been able to get the DAC inputs to work. I'm more than happy to do any testing you need... I'd love to see an in car useable 4.4 rom as I'm sure a lot of the other "android in car" crowd would too!
Sent from my SGH-I747 using xda app-developers app
So I've tested this a little today and DAC is working on boot every time which is awesome! One thing I did notice is if I boot with DAC and flash drive my flash drive isn't recognized until I unplug the flash drive and replug it in. Anyone else notice this?
I'll have to do more testing after my exams but just thought I'd see if anyone else has experienced this.
Sent from my Nexus 7 using xda app-developers app
Kuchar09 said:
So I've tested this a little today and DAC is working on boot every time which is awesome! One thing I did notice is if I boot with DAC and flash drive my flash drive isn't recognized until I unplug the flash drive and replug it in. Anyone else notice this?
I'll have to do more testing after my exams but just thought I'd see if anyone else has experienced this.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I noticed this too. I installed Stickmount and it seemed to work OK after that.
Sent from my SGH-I747 using xda app-developers app
Kuchar09 said:
So I've tested this a little today and DAC is working on boot every time which is awesome! One thing I did notice is if I boot with DAC and flash drive my flash drive isn't recognized until I unplug the flash drive and replug it in. Anyone else notice this?
I'll have to do more testing after my exams but just thought I'd see if anyone else has experienced this.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hmmmm..…...does it remount for you after deep sleep?? Or do you have to replug after that too?
I guess I'll add this to the list. I'll go test this out. I think we could use the jellybean vold if it mounts on boot.
redeyedjedi said:
Hmmmm..…...does it remount for you after deep sleep?? Or do you have to replug after that too?
I guess I'll add this to the list. I'll go test this out. I think we could use the jellybean vold if it mounts on boot.
Click to expand...
Click to collapse
Haven't tried deep sleep but I just tried booting it up and it didn't show so I unplugged power for my y-charge cable let the screen turn off then reconnect power and the the flash drive showed up in the file system. So this isn't a huge issue just looks like a little something might be missing.
Sent from my Galaxy Nexus using xda app-developers app
does this kernel extend otg+charge functionality to properly sense charging after boot (exactly as plugging in a wall charger)?
I've tried several kernels and they all have the same behavior in that they do not show a charging battery, (only in the pull down notification). this makes Tasker unable to know that power is actually plugged in.
issue is described here in relation to USB Accessory Charger
http://2dindroid.wordpress.com/2013/09/01/more-notes-on-usb-otg-charging-nexus-7-2013/
http://en.wikipedia.org/wiki/USB_OTG#OTG_micro_plugs
EDIT: just realized i was linked here from the Nexus 2013 forum.. ignore the question.
This is not directly rom related but since I assume most people here are doing a fixed install I will ask here.
So during the average commute I am running waze, torque, and Spotify.
I can't seem to catch my tablet up on the charging. During the drive it just slowly goes down while (maybe 1% over a hour). I am using a startech powered USB hub with a powered otg cable going to the tablet. The power side of the otg is plugged into the hub which should provide ample power to charge the nexus.
Is it possible for the nexus to draw more than it is capable of charging? Should I be focusing on my charging selection? Anyone else having a similar issue?
Can anyone tell me an accurate way to measure the draw being used by the tablet and the charging current?
My next option is a hardwired 3amp charger with a toggle switch that will either route the power to a source that is only on when the car is running and the other side of the switch will route it directly to a lead I have coming from the battery (attempt to get ahead while I am grocery shopping or times when I am only out of the car for an hour or so.)
Sent from my SM-N900T using Tapatalk
This all relates to my experimental Android-x86 (x86_64) builds (http://forum.xda-developers.com/win...-jun-2015-android-x86-lollipop-5-1-1-t3125035). Any and all help is appreciated!
One interesting note is that if I use the debug boot item, I cannot boot as the type cover keeps disconnect and reconnecting in the console, or at least, some of the devices inside of it do.
Sensors output (from Linux, using an iio service for systemd - github.com/hadess/iio-sensor-proxy ):
http://pastebin.com/raw.php?i=Jf2MX3Kt
Could someone please tell me how to get those sensors working under Android? I believe the magnetometer is used to detect if the type cover/keyboard is attached or not, which may relate to the crash when it is removed or reconnected to the device
The NTRIG devices are related to the bluetooth pen, which I believe we should be able to also get working, since I think some examples of pressure sensitive pens are out there
dmesg (android):
http://pastebin.com/raw.php?i=e0gmP91R
note the i2c issues and others - there's an LKML topic about the i2c errors, and it implies they aren't truly fatal
audio devices are detected, but I get no sound output on my builds...older kernels had working audio
DRM is loaded but opengl is null under the tablet information tab
Logcat, with the keyboard disconnect/reconnect crash:
http://pastebin.com/raw.php?i=fzgSabgV
Halp! I have no idea what I'm doing yet, especially with Android and it's codebase, as I'm more of a vanilla Linux person at the moment. I really want to learn and help and get this thing working!
Thanks everyone!
Just so you all know, rbg's 32 bit build of Kitkat is rock solid and only lacks support of sensors and volume rockers: https://groups.google.com/d/msg/android-x86/q-B7lrRzeiM/5IJ-J_J13s0J
I tried rbg build(android_x86-5.1.1_r13-20150831.img) from a live usb(SP3 i5 4gb ram), made the usb with rufus; Rotations wasnt working. Rotations+pen input broke touch input alltogether. And i could not see if the tablet was going to deep sleep or if it scaled cpu frequencies. Any ideas or sugestions for someone that even though loves windows for desktops is really looking for android on a tablet? Would i get better results if i install? How would i install to get completely rif of windows 10?
Edit: Found the 7 September build with bluez integration.
https://groups.google.com/forum/#!p...aZ7E2pFh/android-x86/F4IVDDuul2w/8Tt1Mz67FgAJ
Ill see if it works better.
This is a windows tablet, but I think it would be cool to have this run android as well, so I tried a few emulators running under windows 10, but they are very slow, unstable or didnt run at all. Doid4X, an Nox worked, Andy refused to start).
I kept the Nox App Player, cause that was the one I found most responsive of these.
Perhaps the fact that they barely meets the minimum RAM requirement is a major cause for it being slow.
Then I decided to try the android-x86, which is not an emulator, but an andoid port to x86, and will run natively.
The Lollipop EFI image does work as a live usb media , and I was able to install it to another usb stick, but that got stuck on the aandoid logo when booting. The 4.4r3 EFI image did work better, and was able to install to a second usb stick and boot up into android.
I must say that android-x86 did impress me. It feels quite quick and responsive, and any app I have tried so far does run. Even MineCraft PE works well. The display and touchscreen works well, and volume buttons works.
There are a few driver related issues though, here is a list of some things not working:
- onboard wifi
- onboard Bluetooth
- Sensors (auto rotate will not work)
- Audio out and mic
- Power button
- Battery status
- Camera
I did a few tests, and as a workaround I did use an external usb wifi adapter to get internet working. Also connecting a usb headset with mic did work fine, external keyboard. Also a non branded bluetooth adapter was accepted and the BT icon was enabled, but it didnt find any devices when searching. Even a logitech webcam did work with opencam.
Given the current state of andoid-x86 on this tab, it doesnt make sense to partition the disk to get a dual boot. But if there was working drivers for wifi and audio etc, this could be a decent android system.
Now the android version of the tab 8 looks quite similar to the w1-810, so that makes me wonder how much of the hardware components that are the same. And if it may be possible to get the drivers from the original android to work on android-x86.
I will try to list the hw configuration as I can read from devicemanager/drivers in win10:
wifi: broadcom 4330 / Sound: intel SST audio device / camera: Intel Imaging signal processor 2400 / Bluetooth: BCMBTBUS / Sensors: BMA2x2 ( BMA250E) / Battery control hardware ID is PNP0C0A
Any ideas on how to get these things working would be great.
forum administrators:
I did tag this thread with iconia-tab-8, but for some reason it will not show under "Acer Iconia Tab 8 Discussion" list.
Did I miss something, or doesnt the tag system work properly.
Is there anything I can do to fix this?
I also have this tablet and I am also eager for installing fully functional Android on it. Please guys help us on this. Thanks in advance.
News about Acer Iconia Tab W1-810 with Android
Hi guys, some new about it?