[beagleboard] Re: BeagleBoard-XM support to android
On Monday, January 26, 2015 at 11:09:56 PM UTC+5:30, jainni...@gmail.com wrote: Hi, Just wanted to know whether BeagleBoard-XM can be used for Android KitKat? Or is it only used for Android Jellybean? If you are ok with using sw graphics, it is possible to run KitKat. I don't think the SGX graphics libraries are available for KitKat. The system would run a bit slower in absence of graphics acceleration though. -Vishveshwar How do i know which beagleboard supports which Android version? Thanks -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: How to compile the android source code on Beaglebone black board
On Monday, April 7, 2014 3:48:28 PM UTC+5:30, pushpendra singh wrote: Hello , I am newer in android, Welcome to the exiting world of Android! i have a source code of android , but i don't know how to compile that code Where did you get this android source from? Generally, there should be instructions accompanying the source for compiling. 1. How to compile the android source code , 2. I am using Ubantu12.04 If you are using the latest TI DevKit android sources, the build instructions are here: http://processors.wiki.ti.com/index.php/TI-Android-JB-4.2.2-DevKit-4.1.1_DeveloperGuide -Vishveshwar -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Android running on BBB with Linux 3.8
On Saturday, March 1, 2014 5:58:09 AM UTC+5:30, Daniel Delgado Terán wrote: I'm currently having a lot of problems here. If I use Andrew's pre-built image I get support of the LCD3 Rev. A2 with the BBB Rev. A6A but no support to miniUSB+ADB, the device is not even recognized as an actual device when I connect it (not even with a missing driver, it's just a ghost device when connected). If I use the TI pre-build image is just the opposite. I get support to ADB but I can't see anything on the LCD3 Rev. A2 screen. LCD3 A2 revision did not exist when the TI Android 3.2 kernel was developed. I have not seen any recent development activity on that tree so I don't think LCD3 A2 support is going to get added anytime soon. You would need to add it yourself if you wish to continue using the 3.2 kernel. -Vishveshwar I have Linux only on a Virtual Machine so compiling an new image is a bit difficult here. I tried adding some parameters to uEnv.txt but nothing worked. Not to mention the FTDI cable that is not showing anything, and became useless since I booted Android. I also have a big question: OTG support is gone with this pre-built images? I can't read any memory stick or to use a USB Bixolon printer. It's possible to connect a USB fingerprint reader, Smart Card reader, RFID Card reader or Camera as input? Another thing how about configuring the GPIO of the BBB to use a keypad? Thanks in advance. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Android running on BBB with Linux 3.8
On Thursday, February 27, 2014 6:09:34 AM UTC+5:30, paccer wrote: Strangely, I've been unable to make touchscreen work with andrews jb on 4D systems 4DCAPE_70T I've tried with the prebuilt image, and also tried building from source, using the instructions on Andrews webpage, using latest 3.8.x kernel sources. Touch screen works fine on TI_Android_JB_4.2.2_DevKit_4.1.1 image, so it's definitely not an hardware issue. I'm currently baffled, since its reported that LCD7 works, and the 4DCAPE_70T should be similar, it appears. Any help/suggestions highly appriciated - maybe there's some patches available i need? There are two things w.r.t touchscreen: - The touch operation itself - is the driver loaded? are you getting touch interrupts? - Calibration - mapping the usable area so that the touch interacts with the correct display element (icon etc) Some information is at the AOSP page: http://source.android.com/devices/tech/input/touch-devices.html FYI, In the TI DevKit kernel (3.2) the touch calibration data is part of the platform data for the touch driver. See my post in android-porting for more information about this: https://groups.google.com/d/msg/android-porting/CpP4xCk0U_g/DaCoAmqj6FwJ -Vishveshwar I did manage to get GApps (google play etc.) + SuperSU working on the TI_Android_JB image, and i'd gladly provide details if requested. Thanks paccer -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Change Real Screen Resolution
On Tuesday, February 11, 2014 3:14:31 PM UTC+5:30, Efecan Yilmaz wrote: Hi, I'm trying to use a 5.7 LCD screen with Beaglebone Black. I connected the pins and it's working but there is a problem. LCD's resolution is 640x480 and doesn't have an EEPROM. So Beaglebone is setting itself to its defualt resolution, which is 1280x720. I'm trying to change the resolution with: am display-size 640x480 But it doesn't realy change the resolution. It just configure the resolution to look like a 640x480 in a 1280x720 screen. When I look at dumpsys with: dumpsys window it gives me: DisplayContents: Display: mDisplayId=0 *init=1280x720 160dpi* base=640x480 160dpi cur=640x480 ... I think I need to change that init value. I think that value is being set by communicating with LCD's EEPROM. Because when I connect a LCD3 Cape dumpsys window gives init=320x240. Or if LCD doesn't have an EEPROM Beaglebone set itself to its default resolution. I need to change that default resolution. Is there a adb or shell command I can use? Or should I change something in kernel? That depends on which kernel you are using. If you have the 3.2 android kernel from the TI Android DevKit, you need to tinker with the kernel sources. With the community 3.8 kernel you could get by with passing a kernel parameter. Do go through the beagleboard and rowboat forums. You would get your answers there. -Vishveshwar -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: PWM and Analog ins on TI Android with BBB and Kernel 3.2
On Tuesday, February 11, 2014 4:15:52 AM UTC+5:30, Ernesto Gigliotti wrote: Hello, I have I2C,SPI and GPIOs working on TI Android with 3.2 Kernel (without device tree) but I have no clue about PWM and Analog inputs, I don't know where I can start looking. I would appreciate any help. Thanks LCD backlight uses PWM, that should get you started. Not sure about analog inputs. Touchscreen uses the same subsystem though. You can try the TI Linux SDK user guide/release notes for more details. The TI Android 3.2 kernel is based on this. -Vishveshwar -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: OSX not detecting BBB with Android on USB
On Wednesday, February 5, 2014 12:43:00 PM UTC+5:30, Malcolm Groves wrote: Hi, I'm successfully booting into Android on the BBB (using the image at http://icculus.org/~hendersa/BBB_JB_Android_3_8_13.img.bz2), and can navigate to Settings | Developer Options and enable USB Debugging. However, OSX Mountain Lion (10.8.5) doesn't recognise it when I plug it into the USB port. I've read a few pages on how to make it show up for linux and windows, but the consensus for OSX is it should just work. Any ideas? Check this post and later followups https://groups.google.com/d/msg/beagleboard/Yc8CdtU5MEs/JW0PBagAanEJ -Vishveshwar Cheers Malcolm -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Setting a MAC address on beaglebone cape.
On Wednesday, February 5, 2014 8:39:38 AM UTC+5:30, ccsb...@gmail.com wrote: Hi, not sure if I am posting in the right place (please let me know if I wrong!) I have two (white)beaglebones, each of them have the wifi cape with the TiWi-5 chips (http://elinux.org/CircuitCo:BeagleBone_TiWi-5E_w/_EXT._Antenna) Getting them to connect to the network was no problem at all, it is after that the the problems occurred. Only one of them would show up on the network at a time. They had the same hostname and were being assigned the same IP address by the router, so after changing the host name and setting a static IP, I notice that the MAC addresses for both boards are the same, and the router is still only picking up one board at a time. Checking both boards ssh over USB shows that they believe they each have a separate IP address and are connected. So I was wondering if anyone knew how to change the MAC address for the beaglebone with wifi cape. (I have a feeling it might involve EEPROM changes?) IIRC the MAC is stored in an .nvs file. If so, you might be able to modify it using the calibrator tool. But I'm not sure if this is available in the angstrom image. http://processors.wiki.ti.com/index.php/WL12xx_NLCP_Calibration_Process -Vishveshwar I have not been able to find any information in relation to changing the MAC address with a wifi cape installed, yet alone much information for the wifi cape itself. Any help, or links to resources would be appreciated. Thanks Chuan -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Enabling adb on Beaglebone Black
On Saturday, February 1, 2014 2:58:14 AM UTC+5:30, Mahendra Gunawardena
wrote:
I have successfully loaded TI-Android pre-built image on a BBB which was
downloaded from
herehttp://downloads.ti.com/sitara_android/esd/TI_Android_DevKit/TI_Android_JB_4_2_2_DevKit_4_1_1/index_FDS.html.
Everything works well on the device. I have been trying to enable adb
without much luck. Basic HW and SW is as follows
*Hardware*
- Beaglebone black.
- 4DCAPE-43T.
- 5V power supply.
- mini usb connection to Ubuntu 12.04 LTS host system.
*Software*
- TI-Android JB image
(TI_Android_JB_4.2.2_DevKit_4.1.1_beagleboneblack.tar.gz).
- Ubuntu 12.04 LTS host system.
On the BBB I have turned on USB debugging by
- App Launcher - Settings - Developer options
This should have been enabled by default. Was this not the case?
On the Host side
lsusb output is
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp.
Bus 001 Device 004: ID 10f1:1a52 Importek
*/etc/udev/rules.d/51-android.rules*
SUBSYSTEM==usb, SYSFS{idVendor}==18d1, MODE=0666
SUBSYSTEM==usb, SYSFS{idVendor}==0451, MODE=0666
I have executed the following two commands
chmod a+r /etc/udev/rules.d/51-android.rules
sudo service udev restart
When I do an
adb devices
I don't see the BBB, but when I have HTC phone attached I do see a valid
response.
What I am doing wrong?
Also I plug the mini-usb to the host machine. Is this correct?
Yes, you need to connect the mini-usb cable which came with BBB to access
adb.
Recheck the connections. You should get an entry for VID 18d1 once adbd is
up on BBB.
-Vishveshwar
Or do I have connect to the serial debugging port.
Thanks
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Boot Android (TI-JB) on beaglebone black from SD card
On Saturday, February 1, 2014 3:03:49 AM UTC+5:30, Mahendra Gunawardena wrote: @Vishveshwar On the 4DCAPE-43T this two jumper that need to be placed. When the both jumpers were connected the BBB started to work. More information can be found herehttp://4d.websitetoolbox.com/post/boot-android-tijb-on-beaglebone-black-from-sd-card-6738480 . Good to know. Thanks for the update. -Vishveshwar Thank you for you response. Mahendra On Thursday, January 30, 2014 8:34:05 AM UTC-5, Mahendra Gunawardena wrote: I am trying to boot Android (TI-JB) on to a Beaglebone Black system. I am referencing the TI Android JB-4.2.2http://processors.wiki.ti.com/index.php/TI-Android-JB-4.2.2-DevKit-4.1.1_DeveloperGuide *Hardware:* - Beaglebond black Rev A5C with Angstrom loaded - 4D system resistive touch LCD cape (4DCAPE-43Thttp://www.4dsystems.com.au/product/22/125/Beagle_Bone_LCD_Capes/4DCAPE_43/ ) - 5V power supply - USB connected to Host PC (Ubuntu 12.04 LTS) *Software* - Beaglebone black has the stock Angstrom Linux - uSD card has JB 4.2.2, I have built the kernel *Connections* - 5V power supply - mini-USB connected to Host PC (Ubuntu 12.04 LTS) On boot/power up I held the S2 (uSD boot) button and release the button. I was expecting the system boot from the uSD card with Android. I don't see any of the USERx LED's illuminated. Do I need to make change to the display resolutions? What am I doing wrong? Any suggestions? Attach few pictures of the hardware too . http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/791/7115.IMAG0214.jpghttp://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/791/5164.IMAG0215.jpg I have read the following post toohttp://e2e.ti.com/support/embedded/android/f/509/t/282310.aspx . I have ordered the Serial to USB cable will post the log when available -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Boot Android (TI-JB) on beaglebone black from SD card
On Thursday, January 30, 2014 7:04:05 PM UTC+5:30, Mahendra Gunawardena wrote: I am trying to boot Android (TI-JB) on to a Beaglebone Black system. I am referencing the TI Android JB-4.2.2http://processors.wiki.ti.com/index.php/TI-Android-JB-4.2.2-DevKit-4.1.1_DeveloperGuide *Hardware:* - Beaglebond black Rev A5C with Angstrom loaded - 4D system resistive touch LCD cape (4DCAPE-43Thttp://www.4dsystems.com.au/product/22/125/Beagle_Bone_LCD_Capes/4DCAPE_43/ ) I don't think this cape is supported in the TI kernel - 5V power supply - USB connected to Host PC (Ubuntu 12.04 LTS) *Software* - Beaglebone black has the stock Angstrom Linux - uSD card has JB 4.2.2, I have built the kernel *Connections* - 5V power supply - mini-USB connected to Host PC (Ubuntu 12.04 LTS) On boot/power up I held the S2 (uSD boot) button and release the button. I was expecting the system boot from the uSD card with Android. I don't see any of the USERx LED's illuminated. Do I need to make change to the display resolutions? What am I doing wrong? Any suggestions? Attach few pictures of the hardware too . http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/791/7115.IMAG0214.jpghttp://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/791/5164.IMAG0215.jpg I have read the following post toohttp://e2e.ti.com/support/embedded/android/f/509/t/282310.aspx . I have ordered the Serial to USB cable will post the log when available You could try to see if you are able to connect to BBB using ADB. It works for me. Wait 2-3 minutes after booting and then try and open the adb shell. You can refer to the TI user guide for configuring ADB. -Vishveshwar -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: problem booting android 4.2.2 on baglebone
On Monday, January 27, 2014 10:26:41 PM UTC+5:30, Mihir Jariwala wrote: I recently started working on baglebone. I followed the steps on http://processors.wiki.ti.com/index.php/TI-Android-JB-4.2.2-DevKit-4.1.1_UserGuide http://processors.wiki.ti.com/index.php/BeagleBone-Android-DevKit_Guide#Hardware_setup After establishing serial communication the window starts as recommended. As instructed I insert the bootable sdmmc card into the beaglebone. Android starts booting and in the end the log stops... snippet of the log is as below. Now i dont know what i have to do. Please provide some support regarding it. I am using ubantu 11.10 using VMware on windows7 64bit log.. root@android:/ # [3.365753] android_work: sent uevent USB_STATE=CONNECTED [3.371520] android_work: sent uevent USB_STATE=DISCONNECTED [3.379119] Disabling lock debugging due to kernel taint [3.435455] android_work: sent uevent USB_STATE=CONNECTED [3.784362] warning: `rild' uses 32-bit capabilities (legacy support in use) [3.845520] android_work: sent uevent USB_STATE=DISCONNECTED [3.890869] android_work: did not send uevent (0 0 (null)) [3.955291] android_work: sent uevent USB_STATE=CONNECTED [4.109863] android_work: sent uevent USB_STATE=DISCONNECTED [4.141540] android_work: sent uevent USB_STATE=CONNECTED [4.147369] android_work: sent uevent USB_STATE=DISCONNECTED [4.211578] android_work: sent uevent USB_STATE=CONNECTED [4.377655] gadget: high-speed config #1: android [4.397521] android_work: sent uevent USB_STATE=CONFIGURED [ 20.203216] request_suspend_state: wakeup (3-0) at 20170814787 (2000-01-01 00:23:56.3389) [ 21.057922] net eth0: CPSW phy found : id is : 0x7c0f1 [ 21.064208] PHY 0:01 not found [ 21.076110] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 21.768341] acc_open [ 21.773101] acc_release [ 25.053070] PHY: 0:00 - Link is Up - 100/Full [ 25.069183] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 33.759277] init: sys_prop: permission denied uid:1003 name:service.bootanim.exit Congratulations! Android booted up. If you did not attach a LCD cape, that's all you get.. a working console with shell prompt. The shell prompt got lost in the kernel boot messages, but it is there. Press Enter key again and you should see it. -Vishveshwar -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Beaglebone Connection
On Tuesday, January 14, 2014 4:42:42 PM UTC+5:30, william...@gmail.com wrote: I have a problem with the u-boot of my Beaglebone black. Actually when i set up Android on my Sd card, i wasn't able to detect the serial device USB anymore . Before that i installed Angstrom and everythings work well so the Beaglebone isn't the problem but only the boot. Is there some configurations for the device in so far as i can't work, and download some fichier to my Beaglebone from my computer. Need help thank you USB serial is not working in Android or u-boot? AFAIK, USB serial is not supported on the BBB android image. Android prefers to use adb, but that may not be working well either. (depending on which of the various Android images you are using) -Vishveshwar -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Windows adb driver issue
On Wednesday, January 8, 2014 9:57:40 PM UTC+5:30, Doug Nappier wrote: I am working with Android Jelly bean and am having some adb issues when it comes to Windows 7. I can not get windows 7 to recognize the device as an Android device and can not find it with adb. When I boot into my linux host machine I can use adb to find the beagleboard. I ran lsusb on the device in my linux host and got the following output: Bus 001 Device 011: ID 18d1:9018 Google Inc I read in the TI ADB install guidehttp://processors.wiki.ti.com/index.php/Android_ADB_Setup that you need to add the following lines to you the .inf file: %SingleAdbInterface% = USB_Install, USB\VID_18D1PID_9018 %CompositeAdbInterface% = USB_Install, USB\VID_18D1PID_9018MI_01 That guide is quite old and probably not up-to-date. Have you checked the information the the TI User Guide for the Android version you are using? I think the PIDs have changed. -Vishveshwar When I go to my device manager, where the device is mistakenly being established as a mass storage device, and attempt to point Windows at this new .inf file it gives me the error Windows could not find the driver software for your device Does anyone have any ideas how to fix this. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Beaglebone Black CPU speed
On Tuesday, November 26, 2013 4:13:18 PM UTC+5:30, Efecan Yilmaz wrote: I have a Beaglebone Black which runs Android.As you know, it has a 1GHz CPU. Bu when I read it's clock speed from adb I got 300MHz. I'm using following commands: cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq All of them returns 30. I'm using Android image from Texas Instruments. Is tehere a problem? Is my Beaglebone Black running on 300MHz or is it just a system error? I try couple of apps to learn my CPU speed. All of them says 300MHz. But i think they are reading those files too. I am assuming you are using the image from the following page: http://downloads.ti.com/sitara_android/esd/TI_Android_DevKit/TI_Android_JB_4_2_2_DevKit_4_1_1/index_FDS.html How are you powering up? If BBB is powered from USB it is throttled to consume less power. Use a 5V DC supply. Also make sure that you are completely booting from the sdcard. This way you can be sure that the u-boot you are using supports 1GHz operation. Refer the User Guide for details. -Vishveshwar -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: BB black LCD and Android (repost)
On Friday, November 22, 2013 3:44:23 PM UTC+5:30, Pierre Ficheux wrote: Hi, I've bought a LCD screen for my BB black : http://www.logicsupply.com/components/touchscreen-displays/4dcape-43t/http://www.google.com/url?q=http%3A%2F%2Fwww.logicsupply.com%2Fcomponents%2Ftouchscreen-displays%2F4dcape-43t%2Fsa=Dsntz=1usg=AFQjCNE1BQXnk_fRUdLEIPJXUrckaXn-2A It works fine with Linux but Android display is still on HDMI output. Check the EEPROM DIP switch, it should be in OFF position for the TI Android distribution to detect the LCD Cape. Please post the kernel log if the Cape is not detected even after this. -Vishveshwar Any idea to fix it ?? regards Pierre -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Issues building Android
On Thursday, November 7, 2013 9:36:35 PM UTC+5:30, Doug Nappier wrote: I am trying to build the Android ICS filesystem for the BeagleBoard-xm and I have been running into the following issue: frameworks/base/include/utils/KeyedVector.h:193:31: error: ‘indexOfKey’ was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] frameworks/base/include/utils/KeyedVector.h:193:31: note: declarations in dependent base ‘android::KeyedVectorandroid::String8, android::spAaptDir ’ are not found by unqualified lookup frameworks/base/include/utils/KeyedVector.h:193:31: note: use ‘this-indexOfKey’ instead make: *** [out/host/linux-x86/obj/EXECUTABLES/aapt_intermediates/AaptAssets.o] Error 1 The x-loader, u-boot, and kernel are built correctly but this is failing. I got the source from the rowboat repo using the link in the TI-Android-ICS-4.0.3-DevKit-3.0.0_DevelopersGuide found here: TI ICS developers guidehttp://processors.wiki.ti.com/index.php/TI-Android-ICS-4.0.3-DevKit-3.0.0_DevelopersGuide#Build_Procedure I am using Ubuntu 12.04 LTS and I installed all of the needed packages as recommended by the google android initialization site. The ICS sources are not directly buildable on Ubuntu 12.04. The sources need to be patched. You may find some forum posts on this. google around for this. For ICS, ubuntu 10.04 is the best option. -Vishveshwar Any help is greatly appreciated -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: Android software buttons are missing
On Tuesday, October 29, 2013 10:12:39 PM UTC+5:30, douglas...@gmail.com wrote: I recently got tasked with getting Android working on the Beagleboard xm with the xm lcd7 touchscreen. A well documented problem is that the display resolution is too high and mirrored when you boot up android with this screen. Also touch does not work. I remedied the display issues by altering my bootargs which mirrors the display and changes the resolution to 800x480. When this is done the three Android software buttons (back, home, running apps) are no longer visibile. Does anyone know how to get them back? I will worry about the touchscreen for later. Android does not display the NavBar by default for 'low' resolutions like 800x480. You need to force it in the build. Refer the following post on rowboat: https://groups.google.com/d/topic/rowboat/_9IYwTL4y84/discussion -Vishveshwar The bootargs are: setenv bootargs 'omapfb.mirror=y console=ttyO2,115200n8 androidboot.console=ttyO2 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait init=/init ip=off omap_vout.vid1_static_vrfb_alloc=y vram=8M omapfb.vram=0:8M omapdss.def_disp=dvi omapfb.mode=dvi:800x480-24' any help is appreciated -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: List Capes in Android
On Monday, October 14, 2013 5:06:50 AM UTC+5:30, Terry Storm wrote: Sorry, that meant to say Kernel 3.2 On Monday, 14 October 2013 12:35:31 UTC+13, Terry Storm wrote: Hello Can someone help me find out how to list the capes detected by the BBB in Android? I am running the TI build with 3.8 Kernel, and I want to see what it thinks is plugged into the BBB and what ID it has. I have found the LCD7 does not work on the BBB with Android if the address is 0x57, and I had to change the ID to be 0x54 and it worked. Cape would not be detected if I used 0x57, however that works fine for Angstrom and Debian. The TI 3.2 Android kernel expects the LCD capes only at 0x54. https://gitorious.org/rowboat/kernel/source/03f2a1e9ea7f8b11ff6809f5a75b614011f8adb6:arch/arm/mach-omap2/board-am335xevm.c#L2610 -Vishveshwar I know in Linux you can list the capemgr slots, however I am unsure how to do the same in Android. Can someone please give me a command I can type somewhere? Thanks Terry -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
