Actually, I don’t like java either 
I just used code from this guy:
projectproto.blogspot.com/2010/0 … scope.html
It seems that he is not very familiar with java too, because his project is heavily based on Bluetooth Chat example from android webpage. I simplified his project, removed all the controls and placed there only three buttons which send simple commands over bluetooth to expression evaluator. The commands looks like normal C language functions:
Beep(100);
Print(‘Hello’);
CH1::Resolution=2;
OSC.GetDataView();
It should be easy to extend the functionality of the evaluator and make a java application providing full control over oscilloscope.
About the aluminium casing - I was wondering, who the hell would like to buy such thing. At first I thought that they sell it because they had problems with exploding battery, to prevent the user from injury
That was only a joke Ok, this leads me to a different idea. We could use the USB connector for connection to the bluetooth module. It has 5 pins, the extra pin could be used for powering the module and USB lines could be shared with UART module. I have experience with PIC microcontrollers and some of them had very nice feature which allowed to remap internal peripherals to different MCU pins. I was looking at the datasheet I found out that pins PA11 and PA12 can be mapped as following:
PA11: USART1_CTS / USB D- / CAN_RX / TIM1_CH4
PA12: USART1_RTS / USB D+ / CAN_TX / TIM1_ETR
Sad, but it’s still possible to implement the USART in bit-banging way, where the PA11/PA12 pins can be used as digital I/O pins. Stupid and slow but it should work.
And finally - multiple endpoints for USB descriptor, this should be nice feature. But I don’t want to damage my device by messing up the USB driver, because I dont have any JTAG programmer… So I will wait until someone will implement this. Anyway, bluetooth connections is safer, the oscilloscope is galvanically isolated from PC/tablet and you don’t have to face ground loop problems.