Re: Interesting new 'Open' Hardware how do I build shr for it?
On Wednesday 01 December 2010, Gennady Kupava wrote: В Пнд, 29/11/2010 в 01:24 -0800, c_c пишет: Hi, I was looking at arowboat.org - which is a project at getting Android working on all TI OMAP series boards and I saw a link to opensourcemid.org. Apparently, Embest (who also make the DevKit 8000 - a beagle board like board) have made a 7 MID with GPS, camera, mini PCIe (they have a WCDMA module), WiFi and bluetooth running on OMAP 3530. I ordered a device and I find that :- 1. It's built quite well 2. It's responsive and fast (running android 2.1 as of now) 3. The hardware schematics are available online 4. The source code for kernel 2.6.29, x-loader and u-boot are also available online 5. It has a lot of space between the board and the casing - I'm thinking mods like the Freerunner Navigation board 6. The company seems responsive enough I'm now looking at getting a custom kernel (something newer) running on it. Also, I was aondering how do I get SHR ported onto such a device? I have the entire openembedded based SHR build system (something I've been using to build stuff for the FreeRunner) with me - but I'm not sure how to go about changing the target system. Hi, c_c! Thank you for link. Specifications ( http://www.armkits.com/product/k7.asp ) are not really promising fast speeds: it is only 600Mhz cpu, and 'up to' 256 Mb sdram volume is not really good for long term usage. Nothing told about graphic card, so i guess CPU managing LCD, that should eat cpu resources too. So, only caches size, memory type (unspecified) are different from FR. You'll find a more complete spec at opensourcemid.org. Spec is very similar to the beagleboard and n900 - same CPU, same RAM. The CPU has PowerVR SGX530 onboard so I'd be very surprised if it wasn't available for use as it is on the beagleboard, although the accelerated driver is closed. According to same page critical parts are missing from android like power management, bluetooth, usb device support, and mic(!) and device is mostly oriented to WinCE (notice also .asp in web address), this sounds too bad for anyone who want open device, or hackable device with linux on board at all. It may not all be working out of the box, but having the schematics is better than most of the alternatives. Regards, Gennady. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
A lead on the bluetooth audio suspend problem (QtMoko v26)
As far as I can remember there is an issue with bluetooth audio, where the FreeRunner user cannot hear audio over the bluetooth headset/handsfree device on outgoing calls until one incoming call has been received. I'm using QtMoko v26 and once in a while I can get this to happen. I have found a workaround, by accident: After pairing / connecting your bluetooth headset (handsfree in my case), go to the Profile Editor and play your selected ringtone or alarm tone (go to select a new ringtone, and let it play once.) Bluetooth audio then works for me for outgoing calls. I'm guessing the fact that the phone rings for incoming calls is what is making it work. :) Hypothesis: Some sort of initialization routine is taking place when audio is played over the sidetone. I don't have the skills to patch, but if this helps anyone, you're welcome. :) -- --Brian Kemp brian.k...@gmail.com PGP Key fingerprint: 1E5BF363 signature.asc Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Bluetooth Profile selection on Resume from Suspend (QtMoko v26)
Hello all: No clue if this is a known issue or not. I can file a bug if it is not. (I'm not sure which tracker.) I have a Plantronics Explorer 220 bluetooth headset. It supports Headset and Handsfree BT profiles. When I try to connect w/ Headset Profile in qtmoko v26, the connection fails. When I try to connect w/ Handsfree Profile, connection succeeds. When I suspend the phone, and resume it, I must reconnect manually. I assume that the phone is trying to reconnect to the plantronics headset using the Headset profile. Is the connected profile of my device saved on suspend, or simply that it was connected? -- --Brian Kemp brian.k...@gmail.com PGP Key fingerprint: 1E5BF363 signature.asc Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: A lead on the bluetooth audio suspend problem (QtMoko v26)
Brian Kemp wrote: As far as I can remember there is an issue with bluetooth audio, where the FreeRunner user cannot hear audio over the bluetooth headset/handsfree device on outgoing calls until one incoming call has been received. Yup, i remember :) I'm using QtMoko v26 and once in a while I can get this to happen. I have found a workaround, by accident: After pairing / connecting your bluetooth headset (handsfree in my case), go to the Profile Editor and play your selected ringtone or alarm tone (go to select a new ringtone, and let it play once.) Bluetooth audio then works for me for outgoing calls. I'm guessing the fact that the phone rings for incoming calls is what is making it work. :) Hypothesis: Some sort of initialization routine is taking place when audio is played over the sidetone. The problem was alsa scenario switching. I don't have the skills to patch, but if this helps anyone, you're welcome. :) Maybe you can enable logging for audio states switching. It could be obvious then where is the problem if it alsa state switching is wrong. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Bluetooth Profile selection on Resume from Suspend (QtMoko v26)
Brian Kemp wrote: Is the connected profile of my device saved on suspend, or simply that it was connected? I dont know very much about it, but IIRC sometimes it can be that the headset connects to the phone. Not sure if this is the case. It could be seen in the bluetooth log how it works. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
