Related
Hi guys
I really love my galaxy s 2 but i think also that all this power can be used to use this Smartphone as a little pc or better to use this Smartphone as a little tablet but more little and more comfortable to move..
Well i have see some details about web top application for Motorola on atrix model and i think that this is a good idea.. When i stay in office or at home i can manage my files and other with my Smartphone but with the keyboard and mouse and monitor of my pc..
I know that Motorola works in 2 different way.. One with the keyboard dedicate and one with the normal wired cable.. May be that i can use this software also for my galaxy? Is possible or not? What gs your opinion?
Thank a lot!
sam
Sent from my GT-I9100 using XDA Premium App
I think this idea has a lot of mileage, and it's something I'd very much like as well (plus many others I'm sure).
With the MHL output, something like this should be possible.
I've got an MHL cable, bluetooth Keyboard and Mouse, and it's ok, but the software is not designed for such a setup, and the screen resolution is far too low.
Sadly I'm not a dev, but in order to create something that can achieve an Atrix 'webtop' like experience for the S2, devs would need to work out how to get something other than video to be output at a higher resolution than the native 800 x 480.
Does anyone have any ideas as to how to achieve this?
Could a separate Linux based system be run in parallel to Android, but output via the MHL output?
The S2 is powerful enough, it's whether devs have the tools available to achieve something like this, which could lead to some very cool peripherals (tablet docks, net-book docks, desktop docks etc).
I've noticed this idea mentioned in a few places - are there any devs willing to take this as a project and give it a go? I'd be happy to help organise, but sadly have no programming skills.
DavidMc0 said:
I think this idea has a lot of mileage, and it's something I'd very much like as well (plus many others I'm sure).
With the MHL output, something like this should be possible.
I've got an MHL cable, bluetooth Keyboard and Mouse, and it's ok, but the software is not designed for such a setup, and the screen resolution is far too low.
Sadly I'm not a dev, but in order to create something that can achieve an Atrix 'webtop' like experience for the S2, devs would need to work out how to get something other than video to be output at a higher resolution than the native 800 x 480.
Does anyone have any ideas as to how to achieve this?
Could a separate Linux based system be run in parallel to Android, but output via the MHL output?
The S2 is powerful enough, it's whether devs have the tools available to achieve something like this, which could lead to some very cool peripherals (tablet docks, net-book docks, desktop docks etc).
I've noticed this idea mentioned in a few places - are there any devs willing to take this as a project and give it a go? I'd be happy to help organise, but sadly have no programming skills.
Click to expand...
Click to collapse
I think they simply enabled two or more resolution scaling in the android itself, or at least in the launcher, just a guess though.
But starting another application upon connecting the MHL cable should be easy (e.g. Dock station, etc.) and theoretically someone, or group of people (as I think this would be quite an endeavor) could write whatever you like application.
One tricky thing is if the resolution is at all changeable on SGS2.
But the idea is really good
cheers
How about this?
veyka said:
How about this?
Click to expand...
Click to collapse
wow! thanks for sharing this! it seems awesome
Thanks for the link. It works ok, and it's great that it is running alongside Android.
However, it seems that it's not possible to get it to work at more than 800x480 resolution, which is a shame. Increasing the desktop size just means you need to scroll around rather than increasing the resolution sent through the HDMI, which is what you'd expect as it's mirroring the GS2 display.
If we could find a way to run this so that it's not mirroring the GS2 display, but running at a higher resolution through the HDMI, that would be great.
I had more or less the same problem, (not using the hdmi cable yet) I changed the /root/bin/ui script to 1024x768 but you can put any value
enricoeb
Did you get this working on the GS2. How does it function with the lapdock? Can you use the lapdock's touchpad and keyboard? Thank you in advance for your reply
Hi Devs.
After doing a little research, its seems that USB audio support is enabled in the S3 kernel. There seems to be a fair bit of support for implenting this feature accross a range of devices.
I also note that the cheap C-media chips are recognised by the S3 kernel. So I'm going to buy one, as they are cheap as chips. I realise the sound quality won't be up to much but its a step in the right direction, as I don't currently have and other USB audio devices.
So, I fancy a little kernel compiling. I have done this on linux systems many years ago and I still compile the odd program when I have to. There seem to be some kernel compiling good guides, but I am wondering if anyone else is looking into this feature, or can suggest a good place to start. Is it worth starting with an S3 kernel, (I guess not) or should I start from scratch, or another kernel I like? Anything I compile and test will have cifs support, as its something I can't do without.
I also see the Glados kernel for Nexus already has USB audio support.
Obviously I'm aware of the emmc erase issue, so starting with sources that disable this feature would be a good idea.
Am I completely mental or is this worth having a go at? I'm willing to wait a while if its too dangerous to try until Samsung release a fix for the SuperBrick.
I'll admit I'm rusty, but I have successfully complied kernels in the past.
Any comments will be graciously be recieved!
OK, no love for USB audio. Looks like I'm on my own then!
+1 for USB audio
Galaxy note Paranoid Android 1.7ghz goodness
audio over usb
Galaxy Note has USB audio support too. Take a look at Samsung EDD-D1E1 Dockingstation for Samsung Galaxy Note. it's with Line-Out for external speaker.
The note doesn't supply much power in the USB OTG configuration so may need to be an externally powered unit, or running via a hub.
As NBLive says, the car dock has a USB --> 3.5mm option which works fine with the Note (I was using it about 2 hours ago), so the support is there, we just need driver support for "generic" units.
It's also pretty much a non-issue for the S3 anyway as it's got the good Wolfson DAC rather than the crappy Yamaha (iirc) one the Note has.
NBLive said:
Galaxy Note has USB audio support too. Take a look at Samsung EDD-D1E1 Dockingstation for Samsung Galaxy Note. it's with Line-Out for external speaker.
Click to expand...
Click to collapse
As I recall it the dockingstation only have analog audio (not usb audio but it might use the same connector), I have the dock somewhere, will check when I find it.
To OP, you are absolutely not alone on this one, It is one of the most requested features on Android (link).
There are also a few threads in the forum.
slinbin said:
As I recall it the dockingstation only have analog audio (not usb audio but it might use the same connector), I have the dock somewhere, will check when I find it.
To OP, you are absolutely not alone on this one, It is one of the most requested features on Android (link).
There are also a few threads in the forum.
Click to expand...
Click to collapse
You are correct. The dockstation is just a usb connector with the sense pin 4 having a resistor of a certain value connected to ground, telling to phone to output analogue audio to the data lines of the usb circuit. This is similar to how the phone senses a USB OTG or MHL-HDMI cable.
What I'm talking about here is USB audio device driver support at the kernel level. Currently its not compiled into the Note's but is supported for a limited number of devices in the galaxy S3 kernel. Simplistically put, the phone doesn't have the drivers.
I've looked around at various config files in the Note and am now wondering if SPDIF audio can be outputted over USB. However, I could be wrong as the there is a lot of ancient crap left over from linux configs from 10 years ago, for instance, config files for Turtle Beach sound cards!
The other option is to use the MHL-HDMI adaptor and then an HDMI to digital audio but that's a bit clunky and given that the S3 can do what we want, it shouldn't be too hard.
The advantages of this are a higher quality audio, multi channel output from DTS surround Vidoe and audio and stereo line in recording. Although android is not the greatest OS for audio work due to latency issues, USB audio support is a step towards iphone like audio recording/mixing and effects work. The S3 can also support much higher Bit rates and sampling frequencies, upto 24bit/192kHz. Far better than CD quality, let alone mp3.
Many people can't hear or don't care for higher quality audio. I for one can tell the difference between mp3 and CD or FLAC. To be honest, listening to mp3's can sometimes be painful to my ears. If you can't hear the difference, imagine being forced to listen to everything on an AM radio!
Sorry to blabber on lol
knightnz said:
The note doesn't supply much power in the USB OTG configuration so may need to be an externally powered unit, or running via a hub.
As NBLive says, the car dock has a USB --> 3.5mm option which works fine with the Note (I was using it about 2 hours ago), so the support is there, we just need driver support for "generic" units.
It's also pretty much a non-issue for the S3 anyway as it's got the good Wolfson DAC rather than the crappy Yamaha (iirc) one the Note has.
Click to expand...
Click to collapse
Reports are coming in that the Woflson DACs are not sounding so good. The Car docks do not have any kind of DAC in them.
+1, This would be great if I could use my Fiio E17 on note!
Sent from my GT-N7000 using XDA
I can build a kernel with that for you.. I guess. if nothing fails to build.
I'm using a custom kernel that I've had built for myself. Its basicly a Speedmod kernel with some modules (USB ethernet).
Do you have any chip in mind? I can make a CWM package to you.
It will be a Speedmod kernel with the modules.
Remember that Its not a kernel module thay you Want. I don't know if Android will recognize it and play out thru it.
mdrjr said:
I can build a kernel with that for you.. I guess. if nothing fails to build.
I'm using a custom kernel that I've had built for myself. Its basicly a Speedmod kernel with some modules (USB ethernet).
Do you have any chip in mind? I can make a CWM package to you.
It will be a Speedmod kernel with the modules.
Remember that Its not a kernel module thay you Want. I don't know if Android will recognize it and play out thru it.
Click to expand...
Click to collapse
Thanks a lot, saves me setting up a dev environment. I'm still struggling to get a stable laptop and I really don't wanna start doing critical stuff with it (fingers crossed, no hard video hangs with ubuntu 12.04!)
Try compiling for the cheapo c-media chipsets. They are only £1.50 and one is in the post. Think the driver is called cs4281 or something similar and are used in loads of crappy speakers/headphones.
I have read reports that these are recognised under dmesg on the S3.
If this is successful, they I might buy a better USB DAC.
I wonder if the yamaha chip can be persuaded to output spdif over usb. This would enable a wider (and cheaper!) range of DAC's to be used. There is support for ie958 under alsa in android........just a thought.
EDIT: hold off till I get the usb sound device. Some of them are using newer chipsets. I will plug it in to a linux machine and let you know what it is.
I would really benefit being able to plug my YETI microphone into my note for journalism. I remember vaguely looking at it a while ago where people were saying that you need to edit a file (to fake drivers or something) but in the end they were waiting on Google to release audio USB drivers.
I'm only a noob so take what I say with a pinch of salt.
+1
I would love to be able to plug a USB mic into the Note for audio recording.
I don't know if it will solve the latency problems that Android has, but the better audio quality would be good.
reconchrist said:
I would really benefit being able to plug my YETI microphone into my note for journalism. I remember vaguely looking at it a while ago where people were saying that you need to edit a file (to fake drivers or something) but in the end they were waiting on Google to release audio USB drivers.
I'm only a noob so take what I say with a pinch of salt.
Click to expand...
Click to collapse
richlum said:
+1
I would love to be able to plug a USB mic into the Note for audio recording.
I don't know if it will solve the latency problems that Android has, but the better audio quality would be good.
Click to expand...
Click to collapse
I currently have a logitech usb mic to test with also but I have to stress, this testing is just intitial driver support. There probably won't be any programs that will be able to select inputs for recording. I may be able to write a script to select an alternative input device but we are still quite far from this goal.
Glad to see things gaining traction. Hopefully google and samsung are already far ahead and will release something soon.
I would like to see the S3 sources though!
I've been looking through the S3 kernel source. Under /drivers/usb/gadget/ there a various drivers and headers called f_audio.c, u_audio.c, u_audio.h.
Also the Kconfig file details on how to implement these drivers into the kernel. It seems to me that if these can be compiled sucessfully for the Note kernel, it should just be a matter of changing alsa config files to at least initially get audio input/output support for usb audio devices.
Can't wait to have a go!
Someone else will have to write an app to do the device selection in a nice way. That side of things is beyond me.
Downloading the Note kernel source to compare.
Do you know if android uses any sound manager?
My worst fear is that we can't play sound thru it.
Getting a USB device to be recognized by the kernel is easy. All I need to do is to build a kernel with that extra module.
Load the module and boom. Kernel should recognize it.
How about Android sets his output to that new device?
-Zage- said:
+1, This would be great if I could use my Fiio E17 on note!
Click to expand...
Click to collapse
That's the kind of cake I wanna eat.....
Have your music in one place listen to lowQ when thats enough and highQ when you want that (with a extra box on the side, but the music and control stays in the Note).
I feel like if android natively supported exterior USB audio better. The app potential would be huge for audio out apps and simple 2-8 track recording apps among other things
Galaxy note Paranoid Android 1.7ghz goodness
Always looking to improve sound quality. Thanks for thinking outside the box. Hope it all works out in our favour. Suck it iphones xD.
Dynamano said:
Always looking to improve sound quality. Thanks for thinking outside the box. Hope it all works out in our favour. Suck it iphones xD.
Click to expand...
Click to collapse
Whilst I don't like Apple products at all, audio is the one area that an Android user just hangs his head in shame when someone with iOS shows them what they can do on their iphone or ipad.
I'm hoping Android gets a low latency solution soon, but even then, it will be a long way till Android if close to being on par with iOS for audio apps.
After trying several Android tablets, i am developing a board for DIY in-dash system which supports GPS, Music, Video, FM and maybe DVD... Any feature do you like if there is one Android system in your car?
Voice call?
Camera? :laugh:
=====================
Thanks for you guys' attention. Eventually, products are coming:
mod edit - link removed
nonstop2050 said:
After trying several Android tablet, i am developing a board for DIY in-dash system which supports GPS, Music, Video, FM and maybe DVD... Any feature do you like if there is one Android system in your car?
Voice call?
Camera? :laugh:
Click to expand...
Click to collapse
That is a genious idea!! So you plan to integrate a standard Android tablet into a car so that the front passengers can listen to music, make play lists play movies, use Google Maps based GPS (obviously this would only work for SIM card enabled tablets). I cant think of any other uses unless you really wanted to make serious modifications to the car.
Seriously, if I were you I would delete this thread until your idea has a patent or two because this idea is gold dust.
Noobie Boobie said:
That is a genious idea!! So you plan to integrate a standard Android tablet into a car so that the front passengers can listen to music, make play lists play movies, use Google Maps based GPS (obviously this would only work for SIM card enabled tablets). I cant think of any other uses unless you really wanted to make serious modifications to the car.
Seriously, if I were you I would delete this thread until your idea has a patent or two because this idea is gold dust.
Click to expand...
Click to collapse
Yes. That is what i want to do.
Basically, i developed a board and it works. Now, im thinking new features and going to complete the work. One day it may come as an open design for Android fans.
Internet on the way is possible as 3G connection(USB dongle) is ready. Google street view is an interesting app for driving.
# feature is a quality wifi antenna.. reasoning being if its parked near my house it can connect and sync media, etc. External USB ports and Host mode.
Outside of that it all really falls on software I think. One would be the ability to mount MTP devices, and find media on them to play.
I have been thinking about this for years, and originally I was just going to use a browser based UI on top of a very minimalistic linux install. At this point just a tablet minus the form factor and some of the performance (has to be snappy but no need to play angry birds at 200fps), for a bit less $ could make a killer head unit.
I love the idea of android in the car. But don't waste your time re-inventing the wheel, essentially building a custom tablet that will surely be out of date(both in hardware and in software) long before the product makes it out the door.
Compared to technology, cars last forever. *The only way to keep car electronics from feeling dated by the time the car pulls out of the lot is to have a "Dumb" car which can seamlessly integrate with user-replaceable off-the-shelf electronics.
Focus your resources on creating a device that does nothing other than act as an interface between an off-the-shelf tablet and the car. Then all that is left is a one-size-fits all frame for the console that permits you to drop in any (or a wide range) tablet the user wants. Inside the frame you could provide either both power & data over USB or power over usb and data/control over Bluetooth. Spend all of your effort in making the interface compatible with as many makes / models of cars as possible and working out how to get as much data and control over the car as possible. Don't waste your time on anything else..
Make this data/control available via a openly published API and let other developers build apps to display/use/control things and let Samsung/Asus/Apple/whoever build the actual tablets.
This approach is best for everyone. Less work for you on so many levels. And for customers it is great because it is future proof. In a 5 years (or 5 months) all you have to do to upgrade to the latest and greatest hardware is stop by best buy and pick out a tablet.
cypho said:
I love the idea of android in the car. But don't waste your time re-inventing the wheel, essentially building a custom tablet that will surely be out of date(both in hardware and in software) long before the product makes it out the door.
Compared to technology, cars last forever. *The only way to keep car electronics from feeling dated by the time the car pulls out of the lot is to have a "Dumb" car which can seamlessly integrate with user-replaceable off-the-shelf electronics.
Focus your resources on creating a device that does nothing other than act as an interface between an off-the-shelf tablet and the car. Then all that is left is a one-size-fits all frame for the console that permits you to drop in any (or a wide range) tablet the user wants. Inside the frame you could provide either both power & data over USB or power over usb and data/control over Bluetooth. Spend all of your effort in making the interface compatible with as many makes / models of cars as possible and working out how to get as much data and control over the car as possible. Don't waste your time on anything else..
Make this data/control available via a openly published API and let other developers build apps to display/use/control things and let Samsung/Asus/Apple/whoever build the actual tablets.
This approach is best for everyone. Less work for you on so many levels. And for customers it is great because it is future proof. In a 5 years (or 5 months) all you have to do to upgrade to the latest and greatest hardware is stop by best buy and pick out a tablet.
Click to expand...
Click to collapse
hi, cypho
Thanks for your advice.
Due to variety of cars(and tablets), I guess most difficult part is "a device that does nothing other than act as an interface between an off-the-shelf tablet and the car". Beside audio, power ..interfaces fitting to tablet, mounting and installation are blocking issues to make this kind of device.
There is another interface which has been widely applied in after market car head unit: standard 2DIN/1DIN stereo. Unfortunately, we have to put tablet into 2DIN/1DIN shield by this way.
nonstop2050 said:
hi, cypho
Thanks for your advice.
Due to variety of cars(and tablets), I guess most difficult part is "a device that does nothing other than act as an interface between an off-the-shelf tablet and the car". Beside audio, power ..interfaces fitting to tablet, mounting and installation are blocking issues to make this kind of device.
There is another interface which has been widely applied in after market car head unit: standard 2DIN/1DIN stereo. Unfortunately, we have to put tablet into 2DIN/1DIN shield by this way.
Click to expand...
Click to collapse
I agree that is the hard part. Unfortunately that hard part cannot be avoided, weather you use an off the shelf tablet or build your own - it still has to interface with the car.
Really the ones who should be providing that open interface is the car manufactures. But they will never do it. They want to charge you $10,000 for an upgraded electronics package and then rely on those electronics feeling dated after 3 years to persuade people into buying a whole new car. How can they do any of that if it was easy to upgrade/replace the built in electronics for the cost of a cheep tablet.
The good news for you is because of the overpriced nature of manufacturers options if done right(sufficient polish and access to sufficient data and control over the car) you should be able to sell your interface device for big $$$. If the manufactures electronics option costs $10,000 and people are willing to pay for that, why would they not be willing to forgo the manufactures package pay twice that much or more for an aftermarket one that will never get old. Or better yet, imagine how much it is worth to someone considering spending buying a whole new car because their current car feels old.
Guys look here.
this dude build his streak 7 into his car. Just a idea
user_error said:
# feature is a quality wifi antenna.. reasoning being if its parked near my house it can connect and sync media, etc. External USB ports and Host mode.
Outside of that it all really falls on software I think. One would be the ability to mount MTP devices, and find media on them to play.
I have been thinking about this for years, and originally I was just going to use a browser based UI on top of a very minimalistic linux install. At this point just a tablet minus the form factor and some of the performance (has to be snappy but no need to play angry birds at 200fps), for a bit less $ could make a killer head unit.
Click to expand...
Click to collapse
Hi,
Media Sync is a killer application comparing current head unit. :laugh: WIFI is working easily on Android. As you mentioned, quality antenna is a must. Thanks for your information.
exebreez said:
Guys look here.
this dude build his streak 7 into his car. Just a idea
Click to expand...
Click to collapse
thats something i'd do if i had the time and money
nice idea
voice controls would be really nice and an option to let it read out mails/messages you are getting while driving
There are some good voice control apps in google play. Hardware should link to an internal or external mic for the apps.
Here I put an external one for better performance.
nonstop2050 said:
After trying several Android tablets, i am developing a board for DIY in-dash system which supports GPS, Music, Video, FM and maybe DVD... Any feature do you like if there is one Android system in your car?
Voice call?
Camera? :laugh:
Click to expand...
Click to collapse
multiple cameras and external storage to store video streams from cameras
---------- Post added at 04:42 PM ---------- Previous post was at 04:33 PM ----------
user_error said:
# feature is a quality wifi antenna.. reasoning being if its parked near my house it can connect and sync media, etc. External USB ports and Host mode.
Outside of that it all really falls on software I think. One would be the ability to mount MTP devices, and find media on them to play.
I have been thinking about this for years, and originally I was just going to use a browser based UI on top of a very minimalistic linux install. At this point just a tablet minus the form factor and some of the performance (has to be snappy but no need to play angry birds at 200fps), for a bit less $ could make a killer head unit.
Click to expand...
Click to collapse
You will stay in the car listening music instead of going back home to listen on our Sofa?
FocusVideo said:
multiple cameras and external storage to store video streams from cameras
USB camera and USB storage have been applied in the design.
USB camera can be standard PC web camera.
Full function samples will be done in several weeks. :laugh:
Click to expand...
Click to collapse
hands free bluetooth profile would be good to have also.
JoelZracer said:
hands free bluetooth profile would be good to have also.
Click to expand...
Click to collapse
hands free bluetooth profile would be good to have also.
Focus on fidelity
Your early adopters would definitely be those who are already putting in custom stereos. The main thing is that you want quality audio connections via RCA connectors, and avoid ground-loop noise like the plague. Even if what you created was just a a Bluetooth transceiver in the trunk...
-Charles
FoneFill
Boll*cks I had this idea the other day.... then seen this. Guess I'll leave it to you good luck lad. :thumbup:
Sent from the moon on the back of a Yamaha
You mean something like This ?
This would be great, if you could only make a dock for ANY tablet. The tablet that comes with this isnt probably too good. Having a nexus 7 in would make things MUNCH more intersting
I'm just looking to be pointed in the right general direction here.
How would I go about hooking up an LCD and touch panel to an Android board (Raspberry PI or something similar). This is for an embedded device.
Something like a Hannstar HSD062IDW1
sbarrow said:
I'm just looking to be pointed in the right general direction here.
How would I go about hooking up an LCD and touch panel to an Android board (Raspberry PI or something similar). This is for an embedded device.
Something like a Hannstar HSD062IDW1
Click to expand...
Click to collapse
Hey, most of these ARM dev boards have raw LCD headers. If you're an electronics designer then you can go design a PCB to do things like level shift those bits and maybe convert those parallel signals to something else (LVDS or HDMI or watever). But from what I understand, you already have a video out in the form of HDMI and svideo. Some of us here at ArcDatum have done embedded systems research on a whole bunch of ARM boards (BeagleBoard, Pandaboard, the obscure ODROID-X) and almost all of them should have LCD headers. As for touch screens, that's more difficult. Chances are you'll have to use GPIOs or find a screen with HDMI input and USB output for touch sensing. Otherwise you'll have to design an touch screen input/output driver (which actually isn't that hard once you know how.....finding out how is the difficult part since so many of the chips they use have little or no documentation).
You might be in luck with iPhone screens. I personally have heard rumors of people reverse engineering the screen signals and driving them.
Edit: So i looked at your Hannstar link. Looks like you have a 10.5V LED backlight. So u'll have to drive that separately; that's easy enough. As for the actual signals. Looks like the pinouts you have all the RGB 8bit per color channels as well as your power stuff, ground stuff, and your clock inputs all of which can come from either your LCD header on ur RPi (if it has one; i know the BeagleBoard-XM has them) or an external power supply (for Vcc etc). Note you should tie all grounds together in many cases. As for the other random signals you will have to figure out if they're necessary to connect to something (Even if it's ground) or if you can leave them floating. Watch out for your voltage levels and how much current the RGB signals on the display will sink. Likely case is you have to do a level shift from something like 1.8V logic to 3.3V logic or something like that. When you're picking your IC to do that level shifting, also be very aware that the IC has to be able to change from 0 to 3.3V fast enough. You will have to verify that within one clock cycle, the slew rate of every pin (aka each bit for the RGB channels) is high enough to change from a high value to low or vice versa before the next clock edge comes along. If not you're data will be considered corrupt or just completely invalid.
Edit2: Your title states that you're trying to make this work with Android. I think in fact you are trying to drive the LCD with the System on a Chip on the RPi. Depending on the SoC and kernel, you might have to enable the LCD header pinouts in the kernel. Don't quote me on this though. I could be totally bull****ting you. My GUESS is that the same signals that go to the HDMI chip go to the header and in fact when using the header, you're just pulling the logic of those same signal lines (which also means you have to be extra careful of the current you're sourcing from those lines)
I wish to understand your motivation.
There are plenty of cheap Android tablets available with LCD touch screen. Now instead of trying to use one of these you want to get inferior "WhateverBerry" and engineer LCD interface + software stack etc spending your time and money.
Am I correct describing your intention?
Also I am not sure that Android is a good fit for embedded development which is mostly applied to some type of real-time controllers. It is not real-time OS.
If your want to build quickly an embedded controller with LCD touch you can get it done using Arduino boards. There are few LCD modules with touch capabilities available but with very poor documentation. It will require some work but it is feasible to achieve in a few days. It would cost you about $100 in components including Arduino and LCD shield and software is free.
Good luck!
sbarrow said:
I'm just looking to be pointed in the right general direction here.
How would I go about hooking up an LCD and touch panel to an Android board (Raspberry PI or something similar). This is for an embedded device.
Something like a Hannstar HSD062IDW1
Click to expand...
Click to collapse
Adapt0r said:
I wish to understand your motivation.
There are plenty of cheap Android tablets available with LCD touch screen. Now instead of trying to use one of these you want to get inferior "WhateverBerry" and engineer LCD interface + software stack etc spending your time and money.
Am I correct describing your intention?
Also I am not sure that Android is a good fit for embedded development which is mostly applied to some type of real-time controllers. It is not real-time OS.
If your want to build quickly an embedded controller with LCD touch you can get it done using Arduino boards. There are few LCD modules with touch capabilities available but with very poor documentation. It will require some work but it is feasible to achieve in a few days. It would cost you about $100 in components including Arduino and LCD shield and software is free.
Good luck!
Click to expand...
Click to collapse
I agree with this, for the most part. Although theres no reason his application wouldnt be better with Android. What if theyre making some sort of consumer friendly appliance. Android wud be a great place to start. Arduinos wud be good for tiny applications but if they want anything pretty it wont have enough horse power.
Also Im not sure how RTOS fits into this. Sure Android isnt an RTOS, but ur phone is Android and thats an embedded system too. Just because it isnt deterministic doesnt mean it isnt suited for embedded. Just go look at basically any of the Texas Instruments ARM based android/linux dev boards.
Anyway back to the topic at hand. If you want a high powered device then try a BeagleBoard with a third party LCD attachment. It wont be cheap, you would basically have an android tablet only itd be for development (and I mean product development, not just software development). But if you dont need 700+mghz of 32 bit addressing lol, then yes go with a much cheaper arduino and lcd.
Edit: Look at this, I think you'll like it (its an all in one ARM development board):
e2e.ti.com/group/universityprogram/educators/w/wiki/2252.am335x-starter-kit.aspx?sp_rid_pod4=MTk2NzAwNDYzODgS1&sp_mid_pod4=40798754
Also I should clarify Arduinos are a 'cheaper' solution, not a 'cheap' solution. Arduinos are not cheap for the amount of processing power u get and they are almost never suited for LCD applications (but there are a few).
Sent from my SGH-I747M using xda app-developers app
I am glad to have this discussion, it helps to clarify choices we make and avoid waste of time.
RTOS is needed if high rate data acquisition is the core application. If time uncertainty of Android apps execution is tolerable then it might be a good choice considering great UI and communication capabilities.
A number of projects utilize commercial Android hardware with external Bluetooth or USB accessory/ host. In this configuration external accessory acquires and stores data in a buffer, Android terminal reads this data buffer and then does data processing and visualization if necessary.
This combination looks the most efficient since it provides great flexibility with minimal resources.
Low price of Raspberry PI and good marketing attracted a lot of people but usability of this board is very limited. You get what you paid for. It is underpowered for modern Linux and Android, does not have ADC, not suitable for low power (battery) applications. Originally, its main purpose was declared to make learning of programming languages more accessible.
Cheers!
screen
hello Folks,
i even have a broken tablet, but the touchscreen is still ok.
and i still have a samsung wave s8500 with broken screen but it still running.
is there any solution how i can connect the 7 inch screen with the wave?
the 7 inch screen is a mid tablet dropad/haipad.
is there any link to hardware manuall..
and where can i get the driver of the mid?
thanks in advance
Samsung Galaxy Tab 2 7" to LCD
is ther anyone trying connect samsung galaxy tab 2 7" to LCD
or it is imposible.... (
Hello devs,
Please look into enabling the displayport alt mode!!!
Its really frustrating how this phone cuts quality (480p) when used with a 4K TV. The only way is usb to hdmi cable, but sony decided to disable this feature.
Can you please make a tutorial on how to enable this?
Bounty 100 EUR
Up
I have found this intresting information:
https://patchwork.kernel.org/patch/9195059/
It should be that easy as adding some lines of code?
Another intresting video:
https://www.ifixit.com/Guide/Sony+Xperia+XZ+Premium+USB+Port+Replacement/97361
From this video we know thatXZ premium has all the USB type c 3.1 pins connected to the motherboard and therefor to snapdragon 835 (5:07 in the video)
Also take a look at this:
https://cdn.arstechnica.net/wp-content/uploads/2015/01/type-c-pinout.png
Seems like the tx pins are responsible for Displayport alt mode
The good news is that they are soldered into the motherboard connector
Is it possible that the data pins have been disabled in kernel?
I look forward to this thing happening! (Although I'm waiting for a DRM backup method first)
as I said on the other thread, don't hold your breath, pins on a socket and PCB mean diddly squat.
Sony may very well disabled this or not even included supporting chips. I would strongly suggest if anyone wants to confirm this to find the same chipset on a different device with a working video out, then take a super high resolution photo of both sides of the PCB paying special attention to the numbers on the chips, then someone else do the same with the XZp
we will never be about to check the traces since it will be amulti layer PCB and we wont be able to check if any traces have been severed from a photo. but we will know if there are some supporting chips missing.
I disagree with you. Today chips are not just chips, are SOC.
Hardware is there. This tx prins are active for usb audio also, but not for video data transfer.
Sony hasn't implemented snapdragon 835 low cost version, because it does not exist. There are no other chips related to display port alt mode. It is done in Sd835. Simple as that.
Inerent said:
I disagree with you. Today chips are not just chips, are SOC.
Hardware is there. This tx prins are active for usb audio also, but not for video data transfer.
Sony hasn't implemented snapdragon 835 low cost version, because it does not exist. There are no other chips related to display port alt mode. It is done in Sd835. Simple as that.
Click to expand...
Click to collapse
SoC have been used for a long time mate, trust me, if Sony didn't want something there are dozens of things they can do to stop it. Its been a problem with SoC vendors for decades. a physical connection means nothing if its traces are cut
Of course its perfectly possible its just software limited but its equally possible its not physically possible. The proof will of course be if you can get it working... but They have been doing this for years now and are getting pretty good at it.
dazza9075 said:
SoC have been used for a long time mate, trust me, if Sony didn't want something there are dozens of things they can do to stop it. Its been a problem with SoC vendors for decades. a physical connection means nothing if its traces are cut
Of course its perfectly possible its just software limited but its equally possible its not physically possible. The proof will of course be if you can get it working... but They have been doing this for years now and are getting pretty good at it.
Click to expand...
Click to collapse
If you are so confident, then find out for your self, I would say.
You want me to prove that its broken or working? firstly I have no intention of putting any effort in to getting this to work, my device is perma locked and I really cant be arsed taking it apart and try to write over the ROM just to attempt to get this working.
Which leaves me with trying to prove its broken. as Ive said, multi layer PCBs will be impossible to check this without taking the device apart hell, ANY PCB will be impossible to check without checking each trace and that's not to say if QC hasn't used any fuses to blow certain circuits within the chips. If you get it working, then you will have your proof. all I'm saying is don't be surprised If it doesn't happen. it wont be the first time a manufacture has done this.
dazza9075 said:
You want me to prove that its broken or working? firstly I have no intention of putting any effort in to getting this to work, my device is perma locked and I really cant be arsed taking it apart and try to write over the ROM just to attempt to get this working.
Which leaves me with trying to prove its broken. as Ive said, multi layer PCBs will be impossible to check this without taking the device apart hell, ANY PCB will be impossible to check without checking each trace and that's not to say if QC hasn't used any fuses to blow certain circuits within the chips. If you get it working, then you will have your proof. all I'm saying is don't be surprised If it doesn't happen. it wont be the first time a manufacture has done this.
Click to expand...
Click to collapse
Nobody will be surprised, don't worry. Just that we don't know doesn't mean that we shouldn't try.
Trust me, displayport alt mode is disabled in kernel.
Tx pins are active for usb audio playback!
It seems the display link hardware is our only choice for the moment...
https://forum.xda-developers.com/oneplus-5/accessories/usb-c-to-hdmi-adapter-t3631169/page8
Inerent said:
Trust me, displayport alt mode is disabled in kernel.
Tx pins are active for usb audio playback!
Click to expand...
Click to collapse
Sorry bud, that doesn't mean anything more than USB Audio is connected...
Check this out! https://youtu.be/Ff9GfDpH42Q
Maybe some devs look into the buildprop and kernel of the s8 to search for relevant data and compare them with our xzp...
P. S. another proof that makes me think that this sh...t is disabled in software is that with the displaylink apk the one plus 5, xiaomi mi6, etc are working. The data is sent by Displaylink app to those TX usb pins and works!
So with an app it can be sent, but with our sony software not? C'mon!!! This is BS!
Inerent said:
Check this out! https://youtu.be/Ff9GfDpH42Q
Maybe some devs look into the buildprop and kernel of the s8 to search for relevant data and compare them with our xzp...
P. S. another proof that makes me think that this sh...t is disabled in software is that with the displaylink apk the one plus 5, xiaomi mi6, etc are working. The data is sent by Displaylink app to those TX usb pins and works!
So with an app it can be sent, but with our sony software not? C'mon!!! This is BS!
Click to expand...
Click to collapse
your saying that the Displaylink APK works on the Sony Xperia XZp and on the Sony XZp, data is sent to the correct PINs on the USB-C out but it doesn't display anything? on a linked display?
Need help from rooted devices.
Please add or search in buildprop for ro.hdmi.enable=true
If it's present like this #ro.hdmi.enable=true, just delete the #
If it's not present, just add this line ro.hdmi.enable=true
Save and test only with usb-c 3.1 to hdmi and display port alt mode compatibile cable!
Let me know
Inerent said:
Need help from rooted devices.
Please add or search in buildprop for ro.hdmi.enable=true
If it's present like this #ro.hdmi.enable=true, just delete the #
If it's not present, just add this line ro.hdmi.enable=true
Save and test only with usb-c 3.1 to hdmi and display port alt mode compatibile cable!
Let me know
Click to expand...
Click to collapse
yours not root-able?
Hi Dazza! Yes mine is not rooted ... yet! Enabling Display port is the final step towards rooting my phone.
For devs: BoardConfig.mk and BOARD_KERNEL_CMDLINE
Inerent said:
Need help from rooted devices.
Please add or search in buildprop for ro.hdmi.enable=true
If it's present like this #ro.hdmi.enable=true, just delete the #
If it's not present, just add this line ro.hdmi.enable=true
Save and test only with usb-c 3.1 to hdmi and display port alt mode compatibile cable!
Let me know
Click to expand...
Click to collapse
I already tested but it didn't work.