Hi I have a lg p500 and Nokia su-8w don´t work for me on froyo 2.2 (amberhome-1.1)
but I test on with blueinput on lg gw620 froyo 2.2.1 and work without sync.
if you start adb logcat can you see this on lg p500 with froyo 2.2 :
I/BTL-IFS ( 2439): main_server_thread: [CTRL] Client connected (22)
I/BTL-IFS ( 2439): attach_client: multiclient index 0
I/BTL-IFS ( 2439): attach_client: ######## Attached client subsystem BTS (22) ##
######
I/BTL-IFS ( 2439): btl_if_notify_local_event: Notify local event BTLIF_SUBSYSTEM
_ATTACHED
D/ ( 2439): btlif_bts_api_ctrl_cb: btlif_bts_api_ctrl_cb : id BTLIF_SUBSY
STEM_ATTACHED (4112) on hdl 22
I/ ( 2439): btlif_rfc_ctrl_chan_attached: client attached ctrl handle 22
D/BTL-IFS ( 2439): send_registration_rsp: send_registration_rsp [0]
I/BTL-IFS ( 2439): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_REGISTER_SUBSYS_RSP
(CTRL) 2 pbytes (hdl 22)
E/BLZ20_WRAPPER( 2476): ##### ERROR : blz20_wrp_connect: protocol BTPROTO_L2CAP
not yet supported#####
E/BLZ20_WRAPPER( 2476): ##### ERROR : blz20_wrp_close: protocol BTPROTO_L2CAP no
t yet supported#####
I/BI::GUI ( 2476): Connect to (Nokia SU-8W) res=-2 (0=SUCCESS)
I think the problem is the l2cap protocol is not suported well on 2.2
Can anyone help me?
I thing this can solve update the aosp to 2.2.1 on lg p500.
If you can try Prime v2 ROM, it's 2.2.1
http://forum.xda-developers.com/showthread.php?t=881045
what BT stack does Prime use? I've asked LG and they told me, that the do not plan to support HID on Opimus One.
SUCCESS
Already I could have connected it but not with android I using the bluez tools:
here the steps(root needed):
in terminal or adb shell(wifi, usb generate problems):
echo 1 > /sys/class/rfkill/rfkill0/state
hciattach -n -s 115200 /dev/ttyHS0 any &sleep 5
hciconfig hci0 up
hcitool scan (for device address)
hidd --connect (device address in format 00:00:00:00:00:00)
great!
which rom do you use?
could work with this keyboard?
thanks
My ROM amberhome-1.1
I think yes working with this method teoricaly with all hid keyboards but i don't sure only have Nokia keyboard I don't try with other.
But dont power on the bluetooth with android frezze the phone.
Whem I have time develop an android apk.(comming soon)
Bye
Works even with Bluetooth mini keyboard! THANK YOU!!!!
cant wait it to get ready.
I also you amberhome 1.5 on my LG P500. And have a chinfai keyboard.
Perhaps curvin (maker of amberhome) could directly integrate it?
hello, i tried the above steps but when i start hciconfig it returns me that:
hcitool scan
Code:
link_image[1997]: failed to link hcitool
CANNOT LINK EXECUTABLE
it seems the hcitool executable doesn't want to run in my phone...
stock rom?
Trying on an Optimus T with stock ROM (v10l). hciconfig and/or hciattach gives a device not found error.
Will it be possible to get this working with just a kernel upgrade or is there something else needed?
Trying with a different kernel, I don't get the device error anymore, but connectbot says the shell disconnected after I run hidd. At any time after connecting hid0 if I try to do something bluetooth-related, such as turn bluetooth on if it was off, or scan for devices if it had already been on, the phone locks up. Sometimes it reboots in a minute or two after that, sometimes I have to pull the battery to get it to reboot so I can try again.
The kernel I am using at the moment is the "touchscreen issues" kernel.
CM7 - IT WORKS THERE LIKE A CHARM !
I had some conversation with LG earlier and they do not plan the HID support in their android phones.
Success at last
I have no intention currently changing my current stock (+rooted) software and risk losing functionality or stability - the 2.3.3 LG stock currently works perfectly. On the other hand, I'm using francos kernel, so I can have overclock and the tun module I'm planning to change those few lines of code into a simple app so I can easily activate my BT keyboard (sold on DX) quickly on the road. If I manage to do that, I might go ahead and create the ability to change the layout, so the keyboard(s) could be used to full potential. Probably will get some free time in the end of the month.
@ahvenas, so you are saying it works better with 2.3.3 LG stock than it did with 2.2.1?
HID BTKB for P500/P509 update ?
aaopt said:
Trying with a different kernel, I don't get the device error anymore, but connectbot says the shell disconnected after I run hidd. At any time after connecting hid0 if I try to do something bluetooth-related, such as turn bluetooth on if it was off, or scan for devices if it had already been on, the phone locks up. Sometimes it reboots in a minute or two after that, sometimes I have to pull the battery to get it to reboot so I can try again.
The kernel I am using at the moment is the "touchscreen issues" kernel.
Click to expand...
Click to collapse
kokesh said:
CM7 - IT WORKS THERE LIKE A CHARM !
I had some conversation with LG earlier and they do not plan the HID support in their android phones.
Click to expand...
Click to collapse
I'm currently using void#forever, does that mean HID BTKB works with CM7 for P500/P509 out of the box ? at least in your experience. Or do I still need to run those codes >> n00b alert <<
ahvenas said:
I have no intention currently changing my current stock (+rooted) software and risk losing functionality or stability - the 2.3.3 LG stock currently works perfectly. On the other hand, I'm using francos kernel, so I can have overclock and the tun module I'm planning to change those few lines of code into a simple app so I can easily activate my BT keyboard (sold on DX) quickly on the road. If I manage to do that, I might go ahead and create the ability to change the layout, so the keyboard(s) could be used to full potential. Probably will get some free time in the end of the month.
Click to expand...
Click to collapse
You guys got any news on the progress with creating the app ?
Thanks much!
patpads said:
I'm currently using void#forever, does that mean HID BTKB works with CM7 for P500/P509 out of the box ? at least in your experience. Or do I still need to run those codes >> n00b alert <<
Click to expand...
Click to collapse
I flashed mik's version of CM7, my cheapo bluetooth keyboard worked very well, even my WiiMote works also (with additional apps).
jomarx said:
I flashed mik's version of CM7, my cheapo bluetooth keyboard worked very well, even my WiiMote works also (with additional apps).
Click to expand...
Click to collapse
Thanks a bunch for the quick reply
1. Are you referring to this one:
http://forum.xda-developers.com/showthread.php?t=946354
If so how's the ROM compared to past ROMs you've used ? I read lots of people having problem with GPS either not working or failed to lock satellites.
2. Btw are you using P500 ? I have P509, should work though right? Sorry n00b has too many questions before proceding lol.
Terrific news though with HID BTKB working
3. Were the additional apps needed for the wiimote only, BTKB worked w/o any additional drivers ?
=================================
4. And while we're at it, I might as well ask you if this is correct procedure to switch to a new ROM
(1) nandroid/Backup&restore (using CWM) old ROM >> reboot
(2) Wipe every single thing wipe-able (data, cache, dalvik cache, batt stats)
& to be sure it's shiny clean use this:
http://forum.xda-developers.com/showpost.php?p=11785758&postcount=557
to wipe the system as well
>> reboot
(just to confirm, once rooted, always rooted, even after wiping all those right ? )
(3) Partition SD card so that it'd work well with Link2SD (unless there are better alternatives)
(3) flash mik's new CM7 port stable 6.5.8 >> reboot
(4) flash gapps >> reboot >> DONE.
(5) -optional- if GPS has issues back to recovery and flash this:
http://forum.xda-developers.com/showthread.php?t=1287931
Is there anything else you'd like to add ? please elaborate if you get a chance, much much appreciated
Related
This post is now irrelevant, Alex put these commands into the main program. See second post for links.
I figured out how to get it fully working. Big thank you to tonyb486 and canteenboy for figuring out that you need to disable adb and usb mass storage for tethering to work. That only left the problem of disk mounting not working after you are tethering. Here are two scripts to get the whole thing running smoothly and without a problem.
First, if you haven't already, install android-wired-tether. Next install GScript Lite (on the Market) which will let us automate toggling the USB function switch.
Create a new script with SU enabled and use this as the code.
Code:
echo 0 > /sys/devices/platform/msm_hsusb/usb_function_switch
That command shuts off usb_mass_storage and adb so everything is disabled and ready for Wired Tether to come in and do its job. Your usb_function_switch will look like this after running the command.
usb_mass_storage:disable
adb:disable
diag:disable
serial:disable
ether:disable
modem:disable
nmea:disable
When you are done tethering, use this command to re-enable adb and usb_mass_storage:
Code:
echo 3 > /sys/devices/platform/msm_hsusb/usb_function_switch
If for some reason you don't use USB debugging (adb), you can use this command to turn on usb_mass_storage by itself.
Code:
echo 1 > /sys/devices/platform/msm_hsusb/usb_function_switch
For those of you new to GScript, you can place shortcuts to scripts on your home screen. To simplify my life, I put them in a folder with Wired Tether so I have everything in one place. It's not an elegant solution, but you won't need to reboot your phone to get SD card mounting to work again. Perhaps someone with more knowledge of GScript can write some code that will automate running the first script, starting Wired Tether, and then running the last script after it notices that tethering has stopped. (Or better yet, get these commands into the actual program itself.)
(Optional)
For completeness, if you use any of the other usb functions listed above, you can use other 'echo #' commands to find the right combination. They don't toggle individual settings, but rather represent entire combinations of settings. I think around 32-33 it cycles back to 0 (everything off), I didn't have time to figure out if there is a pattern. You can find out what each number does by using another script to read out the switches.
Code:
cat /sys/devices/platform/msm_hsusb/usb_function_switch
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Thanks! I'd like to add that the scripts and the patched app are both working great on my Incredible.
O Whoa, Wired Tether works on my stock Eris now Thank You
Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
Same. I was going to try the app on the Eris because the same manual fix works :\
jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
yeah me too cant find it
Wow, I thought nobody gave a **** about this. Here it is, all compiled and ready to go.
Thanks duder, works like a charm...
Sent from my phone.
THANKS!!!!
Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.
dalstrs said:
Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.
Click to expand...
Click to collapse
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.
I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App
striker012 said:
I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App
Click to expand...
Click to collapse
The problem with that is having to install stuff on the computer. With wired tether you don't have to install anything on the computer.
XevoX said:
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.
Click to expand...
Click to collapse
I'm running the same kernel on evio rom and it's working fine for me...
Sent from my phone.
I've been able to make this work on my stock kernel, rooted FroYo Evo, so this is indeed possible and I've narrowed it down to what is necessary. Please star/follow issue 23 in the Google Code tracker for updates.
Unsupported Kernel message...
Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E
Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E
Click to expand...
Click to collapse
Hi EindhovenOne, I responded to you on the issue tracker for Wired Tether, but I'll respond here just for some others to know the situation.
I found a fix that worked for me on my stock, rooted FroYo Evo and I coded the change and sent Harald a patch. He incorporated the patch and did the build for Wired Tether for me to test, which I have done (and it does indeed work for me, but does currently have the unsupported kernel dialog*). At the same time, though, it is listed in the downloads (you have to select all and then search), but this is in beta state for the changes (hence the deprecated tag I believe).
* I have fixed the unsupported kernel message and sent Harald a patch on this as well, so when he finds time to build it, that should be corrected, too.
So back to the "it's not working" portion, since I'm not running anything but stock (ROM and kernel), my system won't be the same as everyone's. I have no problem with other variations of ROMs and kernels (Evo's and non-Evo's) trying the 1.3 APK, giving feedback, and I'll try to do what I can (and someone else can step in if more suited than me even).
If you do run into issues, you can tag them in the issue tracker, which I try to follow frequently right now. Also, most importantly, if you can provide as much information as possible (what ROM and kernel you're using, a LogCat run just after the error occurs, any other pertinent information we can use to diagnose the problem, etc.), that helps tremendously in tracking down the problem and identifying a fix.
Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO
superevilllama said:
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO
Click to expand...
Click to collapse
The beta-in-progress version 1.3 is located here. It still warns about the kernel currently but you can ignore it (simple lapse in patching that as well at the time). It works perfectly for me (starting and stopping), but there are a couple of issues outstanding right now that I'm working through with the users.
If you do run into a problem, though, just let me/us know through the issue tracker preferably, but you can also contact me directly (here, or my email via the issue tracker).
PS: I have patched the kernel message already, but I don't have write access to the project yet and I don't have the build system in place to handle the native code just yet, so I have been handing builds off to Harald who graciously has done the 1.3 so far for me. When he has time to do the one including the kernel warning fix, I'll post again with an update on that.
Climbing Mount Impropable beta 2
DOWNLOAD: CMI_beta2.zip
Tested on U8100 but propably works on U8120 aswell. Doesn't work well on T-mobile pulse mini but may work on other U8110 phones.
Kernel
- 2.6.32.9
- Based on source for U8150
- Tweaked touchscreen driver calibration to work fine on my U8100.
- Enabled swap
- Enabled EXT3 (if I add a2sd later)
- Added swap_notify support for compcache
- Added LZO support for compcache
- No overclocking yet (will have a look at it later)
Android
- Android 2.2 based on Australian U8150 ROM
- Support for tons of languages
- HVGA hacked Market
- Updated/added several Google apps (Gmail, VoiceSearch, GestureSearch, Street view, Maps)
- root:ed
- Added busybox, nano, bash etc...
Not working
- Wifi (U8150 has a BCM chip, U8100/10/20 uses an Atheros chip, I'm working on it)
- FM Radio (no app was included and 2.1 app depends on stuff in the framework)
Compcache
See post #3
Swap
To enable swap on partition 3 or partition 2 (it will check partition 3 first and if it doesn't exist it will try partition 2)
$ su
# sdswap.sh enable
$ su
# sdswap.sh disable
Installation
1. Flash a recovery image (tested with AmonRA.)
2. Copy the .zip file to your MicroSD card and boot the phone into recovery mode (call+volume-up+power)
3. Choose "Flash zip from sdcard" and choose the zip you just copied.
4. Wipe data+cache before rebooting if it the first install of this ROM. When upgrading with future updates you propably won't need to wipe again.
Compcache
If you are using are allready using a swap partition on your SD-card, then you most likely shouldn't enable compcache. But if you do not want to partition your SD-card then compcache can be a good alternative.
Read more about how Compcache works here: http://wiki.cyanogenmod.com/index.php?title=Compcache
Enable compcache
In a terminal or using an adb shell type this:
$ su
# compcache.sh enable
Type free to confirm you now have 32Mb swap
Disable compcache
In a terminal or using an adb shell type this:
$ su
# compcache.sh disable
Type free to confirm you now have 0Mb swap
Advanced users
Compcache size, settings and swappiness is setup in /system/bin/compcache.sh
If you are an advanced user, you'll know how to proceed from here...
Reserved for the future part 3
Is the Vodafone 845 One of them?
biggerbigboy said:
Is the Vodafone 845 One of them?
Click to expand...
Click to collapse
Vodafone 845 is a U8120 and I believe it should work on it.
I installed on a U8110 from Yoigo (Spain) and It worked all except the sound, which allways sound as a white noise and the wifi wasn't work either.
I had to remove the rom because of the sound. I'll try it again in the next beta.
Best Regards
Hi Kalt_Kaffee..
by my Vodafone 845 is by beta2 the same. Booting ok. Tutorial ok. Phone after first boot freeze. After second boot i can a little bit longer test. Phone and gprs working. After open Devtools freeze and reboots.
Waiting to Beta3
Christian
the u8120 get crashed when i touch the touchpad...all other keys working fine
wildgunman said:
the u8120 get crashed when i touch the touchpad...all other keys working fine
Click to expand...
Click to collapse
With touchpad you mean the optical d-pad?
simple disable d-pad
Hi kallt_kaffe,
On my u8120, i got the same crash, when i touching the d-pad. There is a package which can disable the d-pad, but its only for 2.1. Is that possible to disable d-pad, until the final solution comes? The rom would be much more usable witout this kind of crashes.
Thank you for your great work!
yes, i mean the d-pad
where can i calibrate the touchscreen ? downer part of touchscreen is very bad calibrated on u8120
wildgunman said:
yes, i mean the d-pad
Click to expand...
Click to collapse
I'll try to make a kernel without the d-pad driver. That may stop the crashes (but you'll have to do without the d-pad for now)
where can i calibrate the touchscreen ? downer part of touchscreen is very bad calibrated on u8120
Click to expand...
Click to collapse
Sorry, you can't. I haven't managed to get the calibration app to work with the Froyo build even though the touchscreen driver is pretty much the same as with the old kernel. I had to hardcode the calibration that worked fine on my phone.
Well, sure, of course you can do it but you'll have to recompile the kernel every time you change a value.
U8120 (Vodafone 845) users, try the attached update. It should disable the optical d-pad and hopefully stop the crashes.
Hi Kallt_Kaffee...
fix for Diapad not working. One klick and than freeze and reboot.
It is correkt.. If i dont touch the dialpad the froyo 2.2 works fine and fast no freeze. Camera working. Wifi not. I test now Market and take same Benchmark over SetCpu.
Christian
The CMI_no_optical_dpad_update.zip working perfectly for me, when i touching the d-pad. But if i pushing the d-pad (as a button), ist still crashing. Anyways, its much more better already. Thx.
The rom looks stable, and faster than custom V845 2.1 roms.
Sound ok
Wifi no
Bluetooth ok
HSDPA/GPRS ok
GSM ok
Touchscreen calibration not so good in portait, better in landscape, but useable
Camera ok
SetCpu long test: 12000 (same as on 2.1 @528MHz)
Linpack benchmark: 3.3 MFLOPS (2.2 MFLOPS on 2.1 @528MHz)
I am unable to install the Adobe Flash 10.1. Any idea?
sorry...
gprs not working stable by me. apn are correct.
Test tomorrow again.
Kalt_kaffee very good work... )
Only fix wifi and d-pad and i am happy...
Christian
Can it work with my HK version's U8110?
Can u let me know how to tweak the driver w/ my hk version's u8110?
thanks.
waijeff said:
Can it work with my HK version's U8110?
Can u let me know how to tweak the driver w/ my hk version's u8110?
thanks.
Click to expand...
Click to collapse
Tried w/ HK version's 8110. Wifi is still not work, can anyone tell me how to fix the Wifi function? thanks.
waijeff said:
Tried w/ HK version's 8110. Wifi is still not work, can anyone tell me how to fix the Wifi function? thanks.
Click to expand...
Click to collapse
be patient, wifi's under working (from kallt_kaffe )
;-)
Here is something iv been working on for a while now. Its a custom kernel for STOCK vega roms. It has a lot that the original kernel doesnt.#
(Not For CyanogenMod)
it has :-
-- EXT4 support
-- TAP/TUN driver module
-- CIFS module
-- SLAB memory management
-- CFS
-- CFQ
-- In line with latest .32.x kernel from kernel .org
I have added a few modifications that should make the vega a little better to use
-- Latest AR6k wifi module
-- Tweaked wifi module to stop the module force unloading, this makes the wifi connect A LOT quicker after sleep. (also allows wifi sleep never with a bit more work)
-- Camera is now controlled via kernel sleep/wake (better support for third party camera apps)
-- Ability to flip orientation ( in src )
-- USB host/slave mode switching without flashing kernel
As always although i test my changes as much as possible, im an not responsible for any bricks / fires / invasions that this causes :-D
[ChangeLog]
0.3
-- Fixed All Bugs tha 0.2 introduced (as far as i can tell)
-- Host/Slave now switchable without flashing a new boot.img (See USB HOST section for info )
0.2
-- Add Host Mode Version
-- Tweaked Scheduler
-- Added NTFS module
-- Added UTF8
-- Added pl2303 module
0.1
initial release
[Install]
1) download zip from below
2) copy to sdcard
3) flash in Clockwork recovery
[FAQ]
Q : Hay my wifi isnt working ... what gives ?
A : Manualy Push the AR6000.ko from the .zip to /system/lib/hw/wlan/
[USB HOST]
To boot into usb host mode hold back while booting (best method iv found is)
1) hold pwr untill screen comes on
2) hold back and release pwr untill device is fully booted
A quick demo can be found here
For slave mode just boot normaly
[Download]
0.3 HOST+SLAVE
0.2 [HOST] --- [SLAVE]
0.1
[Credit]
Paul For Hosting the original src
[SOURCE]
HERE
Sweet.
You say this isn't for the CM7 rom though right? It will work with stock and MCR and derived roms?
Any how top stuff!
Not for CM7
But MCR + Stock will run fine
Flashed no problems, running stock 1.09 with the market patch. Quadrant returned 2236, not sure if that's good or bad. Seems to run as smoothly as before.
Sent from my Vega using Tapatalk
I can't say for sure yet, may be the placebo effect but it feels a little smoother in use. Not that it was sluggish before mind. 2350~ in Quadrant.
theatomicfart said:
Flashed no problems, running stock 1.09 with the market patch. Quadrant returned 2236, not sure if that's good or bad. Seems to run as smoothly as before.
Sent from my Vega using Tapatalk
Click to expand...
Click to collapse
Use Smartbench 2011, that's just been released - it supports multithreading which is needed to benchmark dual-core (or more) processors, properly.
Don't use quadrant anymore, unless it gets updated to support multithreading too.
Hmmm, I can only seem to find smartbench donate version in the market?
Same with quite a few other apps as well, I worked around those by installing them on my galaxy s and transferring to the vega but that isn't ideal. Also in the webbased market I get a 'device not supported' message...
Any clues or ideas? (Market enabler doesn't help either)
*EDIT*
Nevermind, fingerprint was already fine in build.prop (which is why I didn't understand why it wasn't working) but after following the steps from this thread:
http://forum.xda-developers.com/showthread.php?t=861044
It's working again
Smartbench 2011 gave a mark of 3113.
Sent from my Vega using Tapatalk
0.2 is out have fun with host
Apache14 said:
0.2 is out have fun with host
Click to expand...
Click to collapse
Hi Apache,
thanks for your work! What's that thing about the host vs slave mode? Does that relate to USB or wifi?
If it's about USB, do you think it will be possible to switch between host and slave mode without flashing a new kernel?
skyball
sent from my mobii
I was giving the first version a run before and initially it seemed to be smooth but after a day I started getting a lot of application issues where they'd stop responding or take up to a minute to respond. I only had the MoDaCo ROM installed with the 0.1 kernel from here so that left me only two things to check. With the Vega stock ROM I immediately noticed it felt much more responsive. I don't know for sure that it was the kernel but that's why I'm posting. Is there any reason why I might get those issues from the kernel?
No root after flash 0.2 slave. Back to 0.1.
brotbuexe said:
No root after flash 0.2 slave. Back to 0.1.
Click to expand...
Click to collapse
I had some root issues too, however a reboot solved it.
Thanks, reboot fixed it.
0.3 is out with slave / host mode switching without needeing to flash boot.img
Apache14 said:
0.3 is out with slave / host mode switching without needeing to flash boot.img
Click to expand...
Click to collapse
I just finished installing the 0.2 when I saw this new one out, 0.2 was definitely faster, and now 0.3 my vega won't event boot up. Just a plain black screen
I already tried the Fix BSOD from HERE with no success.
Now the only option I see is to re-install 0.9, then Clockwork then restore my previous save.
= /
Humm ill look into the black screen of death stuff I think I know how to fix this.
Sent from my Desire HD using XDA App
Worked fine for me
Apache14 said:
Humm ill look into the black screen of death stuff I think I know how to fix this.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Hi,
After the backup I reinstall 0.3 and it does work fine BUT the boot is taking a bit longer and the green droid is not showing up, maybe the other time was just that, but it defo looks weird thise first 10 to 15 seconds of black screen with backlight on.
Apart from that, pretty sweet kernel, and stuff is running fast to the point that i double checked on the spare parts if the animtion was off. It was not.
Thanks
Hi,
Tried this new kernel.
Instal via CWM, all was good, but I tried to switch to host mode just to test it.
Powered it, presset back for about 10-15 segs and tablet got stuck in the Booting screen. Tried to restart, power off ,etc.. but no joy, the tablet still stuck in booting screen.
Hi all.
I make a new kernel based in Buzz Vega, but with some changes.
1) All modules (but wifi) are now integrated into kernel, so no more insmod modules.
2) Added support for PL2303 and FDTI usb to serial chips (Usb Gps, usb-serial cable, etc.)
3) Added support for Xbox 360 PAD (wired or wireless with pc adaptor)
Notes:
1) To boot in host mode, press on, once you have black iluminated, release on button and press back until boot finished.
2) Usb Gps and Xbox pad are detected by kernel but not useable in android by now. I'm working on it.
3) To mount CIFS shares, you can use Mount Manager or Cifs Manager from market
4) To use NTFS (and possibly EXT4) you must mount manually. I'm working in do it automatically. Using ConnectBot:
Code:
$su
#busybox mount /dev/block/sda1 /mnt/usbdisk
And you get yout memory at /mnt/usbdisk and can access it with any file manager.
INSTALL:
This must be installed using CWM, and use this zip as update. MAKE ALLWAYS A NANDROID BACKUP BEFORE
If you was using Buzz Vega, can delete .ko files from /system/lib/modules, because they are not used (now integrated into kernel).
http://dl.dropbox.com/u/13580211/corvusKernel_01.zip
Thanks Buzz, Paul "Modaco", Koush, and all great helping people at #tegratab.
Corvus.
PS: If you prefer speak spanish with me, please PM.
Awesome work with the Xbox360 controller. What kernel module did you use to achieve that? Just getting in to kernel stuff with the Vega so please excuse if my question is a little basic.
You can search for Xpad in .config or advent_vega_defaultconfig.
corvus said:
...I make a new kernel based in Buzz Vega...
Click to expand...
Click to collapse
Hey corvus,
I just wanted to say thanks! Your kernel is running great on my POV mobii and I don't experience the root- or bsod-problems I had with buzz-vega kernel. Also the cifs integration works fine.
greetings...
Great to see developers starting to work on the Advent.
Installed this kernel on my Advent Vega. It seems the device came to live. Performance is much better now. Suspending and resuming now works better. Wifi resuming works great. Very nice job with this kernel, very nice indeed
what adapter do you use? using xbox remote would be amazing
None by now... they are detected by kernel, but not used by android... working on it.
Corvus.
i thaught as much. good luck with that using an xbox remote on a ps1 emulator would rock!
hi! what about the kernel source + config?
like to add dvb-t and bluetooth hid (doesn't detect that my bt keyboard is a keyboard..)
and ive got some strange issues with the orientation sensor, seems like its shifted to the left so when i want to get into landscape mode i must rotate it much more to the right side (so i used the lock that i can work with that). No issue with CM7.
EDIT: ive got an xbox 360 wireless controller for windows (with the usb reciever), do i need to have some external apps or something to use this?
corvus said:
Hi all.
I make a new kernel based in Buzz Vega, but with some changes.
1) All modules (but wifi) are now integrated into kernel, so no more insmod modules.
2) Added support for PL2303 and FDTI usb to serial chips (Usb Gps, usb-serial cable, etc.)
3) Added support for Xbox 360 PAD (wired or wireless with pc adaptor)
Notes:
1) To boot in host mode, press on, once you have black iluminated, release on button and press back until boot finished.
2) Usb Gps and Xbox pad are detected by kernel but not useable in android by now. I'm working on it.
3) To mount CIFS shares, you can use Mount Manager or Cifs Manager from market
4) To use NTFS (and possibly EXT4) you must mount manually. I'm working in do it automatically. Using ConnectBot:
Code:
$su
#busybox mount /dev/block/sda1 /mnt/usbdisk
And you get yout memory at /mnt/usbdisk and can access it with any file manager.
INSTALL:
This must be installed using CWM, and use this zip as update. MAKE ALLWAYS A NANDROID BACKUP BEFORE
If you was using Buzz Vega, can delete .ko files from /system/lib/modules, because they are not used (now integrated into kernel).
http://dl.dropbox.com/u/13580211/corvusKernel_01.zip
Thanks Buzz, Paul "Modaco", Koush, and all great helping people at #tegratab.
Corvus.
PS: If you prefer speak spanish with me, please PM.
Click to expand...
Click to collapse
nobody in here?
Sorry by the delay.
Sources and default config are here: https://github.com/BuzzBumbleBee/android_kernel_advent_vega/
For dvb-t you will need some kind of program to reproduce video...
Corvus.
No problem
There is an DVB project for Archos devices, maybe this is a start..
http://code.google.com/p/archos-gen8-dvb/
EDIT: Maybe i got some tomatoes on my eyes, but i dont find the config file
corvus said:
Sorry by the delay.
Sources and default config are here: https://github.com/BuzzBumbleBee/android_kernel_advent_vega/
For dvb-t you will need some kind of program to reproduce video...
Corvus.
Click to expand...
Click to collapse
brunsbanjo said:
No problem
There is an DVB project for Archos devices, maybe this is a start..
http://code.google.com/p/archos-gen8-dvb/
EDIT: Maybe i got some tomatoes on my eyes, but i dont find the config file
Click to expand...
Click to collapse
search for defconfig_adventvega or similar.
do you know where the kernel looks for firmware files?
/lib/firmware no luck
/lib/firmware/[KERNELVERSION]/ no luck
...
brunsbanjo said:
do you know where the kernel looks for firmware files?
/lib/firmware no luck
/lib/firmware/[KERNELVERSION]/ no luck
...
Click to expand...
Click to collapse
i think that you refer to wifi firmware...
I found this problem too...
You must edit wifi sources (/drivers/networking/wireless/ath/ath6k/.../ar6000.c, if i remember correclty). Search for firmware and change all paths to /system/lib/hw/wlan (if i remember correctly, search in this path for files).
you can recompile only wifi module, not need to recompile all kernel.
If you have any other problems with firmware, you need to change sources, because /lib/firmware is a bad place, because /lib is not created. Is better to point to /system/lib.
Corvus.
Hello.
I´m new owner of Xoom "refurbished by motorola" bought on Don´tRetail.
With serie rom, updated by OTA to 3.2, all run perfectly. Enough smooth and run, but Quadrant give me a poor results (1700 points).
After unlock, flash recovery clothwork (3.2.0.0 rc4), I flash tiamat roms (2.0, updated 2.01, and later 2.1 hammerhead).
In all this scenaries, when just flash the new rom, work correctly, but when I installa any application...oh oh...
...when I press power button to suspend it, after eight second Xoom automatic reboot.
I back to stock status (reflash serie rom, serie recovery...all serie) and xoom work correctly.
when I reflash to use another time Tiamat´s rom...here is the problem...when I installed any application, if I suspend Xoom reboot automatically after eight second.
If I plug xoom to pc, and in "cmd terminal" I made:
adb logcat
I can suspend xoom without it reboot.
I tried to elevate minimal frecuencyes in setcpu, but same results.
I tried to do a logcat > logcat.txt in terminal emulator, and suspend the xoom...same result...reboot after eight second.
Any sygestions for I can use Tiamat roms???? With stock rom I have 1700 point in quadrant...with Tiamat without overclock (my xoom don´t let me overclock ) I have 2800 points.
A lot of thanks....Im so frustrated
Ok, I am just asking this to make sure I am 100% clear with this story.
Everytime you do an image with no apps and you shut down, the Xoom doesn't restart, but when you download applications it does... If this is so, I would suggest that you list the applications that you put on your tablet when it does restart, because to me, it sounds like it is an application that is bugging out on the Xoom.
Android systems are set up to force a restart if there are too many system resources being chewed up by applications that are a "High Priority" status and this causes a system resource lock up, and unfortunately, the only way to fix that is to force restart the system. IF it is a app that is doing it, all you need to do is make sure that app is not running to allow it to do so. Good ways of finding out is to use Titanium Backup (Marketplace) to freeze the apps (but that is only for a paid version...) or as someone else just previously suggested in another forum post is Autorun Manager where it allows you to freeze applications from starting up.
I would also suggest that you use the LogCat function in the SDK Tools that is stored in DDMS (aka ddms.bat located in the SDK TOOLS Section). This little program will allow you to do LogCat on your computer as well as save the log as a txt to upload to us (or for easy copy and paste) and as well as allows you to take screen shots and so forth. This might help you out finding the problem too as well as help us
So could you please give us these details to help you out even more?
Is this a Wi-fi only or 3g model that you bought?
Current Rom and Kernel (if I am wrong on the next two posts)
~Guess on Rom is: 2.1 hammerhead
~Guess on Kernal is: (I did not see where you said what the current Kernel was...)
Current Application List that Forces the Xoom to kill itself and reboot, even if it is just one... it might allow us to help you obtain a compatibility issue (if others are having the trouble with the same applications)
You had this trouble after you flashed the new ROMs, are the correct version? (aka Wi-fi only vs 3g romsm, cause there are 3g roms for Tiamat)
Did you clear the cache before and/or after you put the new ROMs on?
I hope we can get this resolved as soon as possible for you!
(links)
to get DDMS if you do not have it yet, please go here -- http://developer.android.com/sdk/index.html -- and you will be able to get step by step walk through to get the SDK. You will need to launch in Terminal/Command Prompt (depending on the Computer Operating System that you use.)
Firts...a lot of thanks for your answer.
With original-stock rom all work all right. My machines arrived with 3.1 Honeycomb, and via OTA updated to 3.2 (HTJ85B).
With this roms, all work correctly. I installed a lot aplications and work allright. I root this rom, and all are working well.
If I try to install any rom from Tiamat, doing previous wipe, the rom runs perfect. I install Titanium to reinstall all my aplications, and all work well. I can work about hours without problems...but with this roms (with all tiamat´s kernel and launpad kernel...) in the moment I suspend, after 8 or 9 second the tablet reboot automatically.
I tried to do a clean install, and only install one aplication, like flash player...and all are ok. After it, install another one, and after it another...but at tirth or fourth there is the problem another time...and tried with diferent aplications. Sometimes the problem go after install flasplayer, sometimes after install RepliGo, sometimes after install dolphinHd...
The more stranger thing is that if a plug the tablet to pc, and make a "adb logcat"...if I suspend de tablet...no problem, no reboot.
It´s possible that mi gpu aren´t righ? I say this because I guess that when the system go suspend, the gpu frecuencies go down (or gpu voltajes) and this made machine reboot... and it´s possible with tiamat´s kernel voltajes and/or frecuencies GPU are diferent than in stock rom.
It´s possible flash a tiamat rom without customiced kernel??? If I could try a tiamat with stock kernel, or with gpu without variation in voltajes or frecuencies.
NOTE: sorry for my english
So could you please give us these details to help you out even more?
Is this a Wi-fi only or 3g model that you bought?
Current Rom and Kernel (if I am wrong on the next two posts)
~Guess on Rom is: 2.1 hammerhead
~Guess on Kernal is: (I did not see where you said what the current Kernel was...)
Current Application List that Forces the Xoom to kill itself and reboot, even if it is just one... it might allow us to help you obtain a compatibility issue (if others are having the trouble with the same applications)
You had this trouble after you flashed the new ROMs, are the correct version? (aka Wi-fi only vs 3g romsm, cause there are 3g roms for Tiamat)
Did you clear the cache before and/or after you put the new ROMs on?
Click to expand...
Click to collapse
Some of my normal aplications:
Beautiful widgets
RepliGo
Documento2go
EzPdf
Titan¡um Backup
SeriesAndroid
Dolphin
Quick Boot
EsTaskManager
Astro, EsFilexplorer, rootexplorer, file manager
Aptoide
Pulse
I tried a lot combinations: for example with or without wifi, changing wifi suspend policy, with or withou configure gmail counts...with or without lock screen...
My Xoom are only WIFI 32gb (MZ604).
anfederin said:
Some of my normal aplications:
Beautiful widgets
RepliGo
Documento2go
EzPdf
Titan¡um Backup
SeriesAndroid
Dolphin
Quick Boot
EsTaskManager
Astro, EsFilexplorer, rootexplorer, file manager
Aptoide
Pulse
I tried a lot combinations: for example with or without wifi, changing wifi suspend policy, with or withou configure gmail counts...with or without lock screen...
My Xoom are only WIFI 32gb (MZ604).
Click to expand...
Click to collapse
I would actually ask if you have your wifi set to go off when the screen is off. This is a known issue...unless the wifi sleep policy is set to Never, the Xoom may reboot when the screen is off. It could be as simple as that.
Oh oh...so many probes that I don´t Know if I change wifi policy or not
But I remember dont change this between flash and install all apks.
At this weekend I´ll probe it and say you, now I need stable tablet to work.
A lot of thanks.
anfederin said:
Oh oh...so many probes that I don´t Know if I change wifi policy or not
But I remember dont change this between flash and install all apks.
At this weekend I´ll probe it and say you, now I need stable tablet to work.
A lot of thanks.
Click to expand...
Click to collapse
You can set it under wifi in Settings--->Networks...
Good luck!