Related
I ported my ReelPortal video conference to Android recently. It's reported to be working on the Viewsonic G Tablet with certain ROMs, as well as the Archos 70/101.
I had one Samsung Galaxy Tab user reported his device bogged down badly when running my software. Initially I thought it may be because it doesn't have a Tegra-2 cpu, but so is the Archos. So I'm not sure why. Also, currently on Android 2.2, my app can only access 1 camera, and the user reported it was the back camera. The Viewsonic/Archos only have 1 (front) camera, so it works great for them. However, Android 2.3 will provide access to multiple cameras.
Anyhow, I want to see if other Galaxy Tab users can run my app. It is published on AppLibs, or you can get it from the Viewsonic G Tablet thread here:
http://forum.xda-developers.com/showthread.php?t=908613
I suggest test the tablet with another PC/Mac/Linux machine (vs tablet to tablet), so it's easier to figure out problems.
Please provide feedback if you try it. Thanks.
Would love to test this with my linux server, but can't find the download for that on your site. If this works well on my Tab, it might replace my need for OpenMeetings.
agentdr8 said:
Would love to test this with my linux server, but can't find the download for that on your site. If this works well on my Tab, it might replace my need for OpenMeetings.
Click to expand...
Click to collapse
I will release the server executable in a couple days. Right now, you can test the client using my server. Some Viewsonic user was able to do a conference between his tablet and 3 other PC's, and said it works as well as dimdim.
Tested the reelportalX on the Tab and it worked ok. Video was from rear camera only (known issue though), and the interface was a bit slow to respond. It FC'd a few times while fiddling with the camera resolution, and also when initiating a P2P session from my netbook to the Tab.
agentdr8 said:
Tested the reelportalX on the Tab and it worked ok. Video was from rear camera only (known issue though), and the interface was a bit slow to respond. It FC'd a few times while fiddling with the camera resolution, and also when initiating a P2P session from my netbook to the Tab.
Click to expand...
Click to collapse
Curious...can you try the web client (via browser) on the tablet, to see if the interface behaves the same? note: the web client can't access camera/mic on the tablet, but it can do everything else. If its different, then perhaps AIR somehow runs slower than Flash. If not, then I guess it's just slow .
Sorry I don't know what FC'd means. Crashed? For camera resolution, I suggest sticking to standards like 640x480, 320x240, etc. Other non-standard resolutions could mess things up (codec, driver). But I don't think the tablet can handle 640x480 encoding (while also decoding incoming streams).
BTW, did the netbook crash too?
FC = Force Close. The default resolution was 320x240 @6fps, and it seemed ok, although it never updated the image on the Tab (seems like it took a static picture, not streaming constantly).
The netbook was fine. It's running Win7 and I tested it with Firefox 3.6.13 on a Lenovo Ideapad S10-3.
Running the browser on the Tab and going to reelportal.com seems to work fine, without camera of course.
agentdr8 said:
FC = Force Close. The default resolution was 320x240 @6fps, and it seemed ok, although it never updated the image on the Tab (seems like it took a static picture, not streaming constantly).
The netbook was fine. It's running Win7 and I tested it with Firefox 3.6.13 on a Lenovo Ideapad S10-3.
Running the browser on the Tab and going to reelportal.com seems to work fine, without camera of course.
Click to expand...
Click to collapse
that's interesting...somehow the back camera is not feeding video streams continuously...i don't think its the cpu then, because the resolution is low...perhaps the camera driver is not compatible with Air...maybe it thinks the software telling it to take a picture, instead of streaming. I didn't have a problem with the back camera on the Droid 2...are you running on the stock ROM or something else?
BTW, is there some other external controls (software) for the back camera on the tablet? Like driver settings on the PC.
I'm running the Euro JME rom (Roto-JMEv4 specifically). There's no special controls for either of the cameras. If you're planning on supporting the Tab, Samsung offers some APIs specific to the Tab for 2.2 development via the SDK which should include front cam support.
Hmm....looks like someone also encountered the same issue...and there's a work around (inconvenient)
http://stackoverflow.com/questions/...py-on-samsung-galaxy-tab-with-air-application
Have you tried using Pocketcloud/another RDP app on the Nexus 7? I'm looking for a new tablet to replace an ipad 2 that I use heavily to remote back to my VPS while I'm out of the office. I'm concerned the Nexus 7's 16:9 ratio makes it difficult to remotely control a Win7 desktop. The ipad2's 4:3 ratio is not bad while using Pocketcloud; even with the soft keyboard up in landscape orientation, I still have enough vertical space to be able to access menus, buttons and programs on the VPS. Using it in portrait format is a bit better (in that the "clipped" screen space is almost 1:1) but doesnt give me much lateral space to work with.
I understand the Nexus 7 runs on a higher resolution (1280x800) so even the landscape format should have more "vertical space" than the iPad, but just wondering how y'all feel about this. Whats your mobile VPS platform of choice?
I use an app called "2X client" to regulary RDP to my Windows boxes.
No real issues here. Of course it's not comparable with using a remote client on a PC, but IMO really OK.
HellcatDroid said:
I use an app called "2X client" to regulary RDP to my Windows boxes.
No real issues here. Of course it's not comparable with using a remote client on a PC, but IMO really OK.
Click to expand...
Click to collapse
tks hellcatdroid, i've tried 2x client too. you dont find the screen size too small for controlling menus, screens etc?
ngmic said:
tks hellcatdroid, i've tried 2x client too. you dont find the screen size too small for controlling menus, screens etc?
Click to expand...
Click to collapse
The virtual mouse works pretty well for me, if things do get too tight i use the pinchzoom.
Not sure about office machines, but...
I use Splashtop for connecting to my machines at home. The need for connecting to my work machine hasn't arisen yet, so I cannot vouch for that case.
Honestly, the 1280x800 resolution is perfect for the Nexus 7 in this case. Both our home media server and my programming box run at that resolution, making it feel slightly small, but still big enough to be functional. I can imagine that things will feel "smashed" if the machine you are connecting to is set at a higher res.
Have not tried using a mouse or keyboard over the connection yet, only their touch-based controls. Their interface does have a slightly noticeable lag, which can be confusing when typing/programming remotely.
Food for thought.
Side Note: I also own and use Splashtop on the iPad (1st gen). Using it on the Nexus 7 feels far more natural, less forced.
So I've discovered that a simple terminal command fixes the black bars on the left and right when outputting through HDMI. It's caused by the tablet outputting a 1280x800 display to a 1280x720 signal. This is easily fixed by changing the device's resolution with the following command:
wm size 720x1280
To revert to the tablet's original resolution, use:
wm size reset
You may need to run the "su" command first for these commands to work, and you do need to be rooted in order for it to work. This will cause some things to get wonky, like the nav buttons disappearing in landscape orientation or the status bar being hard to pull down (perhaps solvable with a change to the DPI), but if you're planning to use this trick for gaming (which was my reason), using something like Smart Launcher 2 with a controller makes this a non-issue. If you want a quick and easy way to switch back and forth, try QuickTerminal on the Play Store and set up both terminal commands as "Quick Commands", or at least that's how I've done it. Now, the picture on your TV will fill the screen. This is as close to Console Mode as we'll probably ever see on this device, so I thought this might help a few people out!
rchrdcrg said:
So I've discovered that a simple terminal command fixes the black bars on the left and right when outputting through HDMI. It's caused by the tablet outputting a 1280x800 display to a 1280x720 signal. This is easily fixed by changing the device's resolution with the following command:
wm size 720x1280
To revert to the tablet's original resolution, use:
wm size reset
You may need to run the "su" command first for these commands to work, and you do need to be rooted in order for it to work. This will cause some things to get wonky, like the nav buttons disappearing in landscape orientation or the status bar being hard to pull down (perhaps solvable with a change to the DPI), but if you're planning to use this trick for gaming (which was my reason), using something like Smart Launcher 2 with a controller makes this a non-issue. If you want a quick and easy way to switch back and forth, try QuickTerminal on the Play Store and set up both terminal commands as "Quick Commands", or at least that's how I've done it. Now, the picture on your TV will fill the screen. This is as close to Console Mode as we'll probably ever see on this device, so I thought this might help a few people out!
Click to expand...
Click to collapse
I've been doing something similar with the NOM Resolution Changer app but I can't get the DPI settings right to match the 720x1280 res. It gets a bit tricky getting back into settings etc after changing the res as my app drawer is inaccessible after doing so. I always just resort back to default with the fail safe timer, I really don't want to get stuck in a resolution which i can't get back out of.
Andy4Shurr said:
I've been doing something similar with the NOM Resolution Changer app but I can't get the DPI settings right to match the 720x1280 res. It gets a bit tricky getting back into settings etc after changing the res as my app drawer is inaccessible after doing so. I always just resort back to default with the fail safe timer, I really don't want to get stuck in a resolution which i can't get back out of.
Click to expand...
Click to collapse
I haven't had that probably making the change manually, and I do believe I tried the app you mention and had the same issue, so you might wanna try testing the terminal command out; if it messes up, you can always reboot the tablet and everything will properly reformat for the lower resolution and then you should be able to change it back with "wm size reset".
rchrdcrg said:
I haven't had that probably making the change manually, and I do believe I tried the app you mention and had the same issue, so you might wanna try testing the terminal command out; if it messes up, you can always reboot the tablet and everything will properly reformat for the lower resolution and then you should be able to change it back with "wm size reset".
Click to expand...
Click to collapse
Thanks rchrdcrg, yeah I'll give it a whirl that way. It is really annoying having those black end sections on the output!!
I've got a chromecast and been trying to get the 'cast screen' option to work using r3pwn's method here http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193/page167#post55119152
I thought that might be worth a shot to see if the output res remains at 1200 x 800 for the mirror but I can't get a picture to display, only sound, when it connects and tries to cast screen. I'm thinking it probably won't make a difference though as I have just bought a miracast ezcast m2 dongle too and that still displays at the 1200 x 800 resolution when miracast is used. It probably is just a rom limitation at the moment.
Andy4Shurr said:
Thanks rchrdcrg, yeah I'll give it a whirl that way. It is really annoying having those black end sections on the output!!
I've got a chromecast and been trying to get the 'cast screen' option to work using r3pwn's method here http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193/page167#post55119152
I thought that might be worth a shot to see if the output res remains at 1200 x 800 for the mirror but I can't get a picture to display, only sound, when it connects and tries to cast screen. I'm thinking it probably won't make a difference though as I have just bought a miracast ezcast m2 dongle too and that still displays at the 1200 x 800 resolution when miracast is used. It probably is just a rom limitation at the moment.
Click to expand...
Click to collapse
Yeah, I "borrowed" a Chromecast from Best Buy and could never get screen casting to work. You might want to see if changing the resolution fixes this issue with Miracast as well... I have a suspicion it will, and that might be useful to some folks. I sure wish I knew how to force the HDMI output to 1080p; it switches over when playing a 1080p video, so I know it's possible, but I don't know enough about development stuff to know how it's doing that, and forcing the resolution to 1080x1920 with the "wm size" command just displays a 1080p picture downscaled to 720p.
try vlc beta off the play store
here's a sort of rant and with a video playback only solution. Not sure how to hide the rant part. I don't forum anything much.
I bought a Belkin miracast adapter off amazon, and have had trouble getting videos playing properly in full screen. It would mirror the 1280x800 with videos played with regular video apps ( MX player, Archos player, stock) which would be 16:10, and would have those bars on either side on both my 1080p insignia tv and our pseudo 720p panasonic (actual res was 1024x768, but at 16:9, which should be illegal to market as a hdtv). I know from previous experience with my galaxy s4, which the samsung video app would mirror only the video at the correct tv resolution, leaving the phone as the remote. You could also use other apps while any video was playing through the samsung watchon (video) app. So randomly downloaded the vlc beta off the play store. It works for the tegra note 7 the same way samsung set up theirs, minus the multitasking(so far). It took me weeks on and off being frustrated with apps that wouldn't recognise that mirroring was enabled to take advantage of the external display. It's kinda whatever now seeing how much time I spent trying to get the video to play properly by itself, for my s4 I tried mhl cables, chromecast, dlna. this works a lot better
So if you just want videos to play, use the vlc player beta. you can use miracast or hdmi. works the same with both. Only if I could miracast surround sound. that would be nice.
I've just started using my tablet and a HDMI cable to run XBMC. This tip has saved me much frustration.
I already use Tasker which can send terminal commands as an action to make it easier. Tasker does have a HDMI plugged state which should allow this to be automated but for some reason tasker doesn't seem to detect it, not sure why yet.
So I've been fiddling a bit more to optimiser the HDMI experience. I've discovered an app called second screen that let's you sert display profiles and launch then the HDMI is plugged in. Thee app sets the size, resolution, dims the screen and force closes the UI to make sure the new settings actually come into effect. It will also revert the changes when the cable is removed. Does need to run on a rooted device but mine is already.
Can somebody please tell me whether it is possible to use the yotaphone 2's EPD as a (small) display to do some basic word processing outdoor out in the sun? I.e. to attach a keyboard/mouse to it (e.g. via bluetooth), to open some simple word processing app or even sthg like google docs, and then to just start working.
I have actually been looking for quite some time for some way to do this and I can't for the life of me understand why there aren't better solutions out there. I am always pleasantly surprised when I type notes on my Kindle Paperwhite. Of course it's a lot slower than on an LCD, but I am not a fast typer anyway, and I could live with some lag - if that's the price I'd have to pay to finally be able to work outside. I have thought of the Raspberry Pi x Kindle solution (but you can only type on sthg like vim); of ebook readers with an open OS that you can attach a keaboard/mouse to (like Onyx Boox that runs on Android 4.0 - and I'm still thinking about that); or of an e ink monitor (too expensive). But it is time for me to change phones, and if this works, I might actually consider it.
If anybody has any experiences or thoughts or - better yet - videos to share on this, I'd be very grateful... Thanks!
-Stephan
I haven't tried this personally, but I am fairly certain that this would work. Android supports bluetooth keyboards. The only limitation would be that you have to use mirrored mode, because there are no proper word processing apps made native for the EPD. Plus the system might not enable external keyboard for EPD apps only. Not sure on the latter though, I don't have any bluetooth keyboard/mouse to test this with.
Jeopardy said:
I haven't tried this personally, but I am fairly certain that this would work. Android supports bluetooth keyboards. The only limitation would be that you have to use mirrored mode, because there are no proper word processing apps made native for the EPD. Plus the system might not enable external keyboard for EPD apps only. Not sure on the latter though, I don't have any bluetooth keyboard/mouse to test this with.
Click to expand...
Click to collapse
Thanks Jeopardy. Can you (or anybody else) tell me whether there is an active developer community working on those EPD apps? And also - if you have to use mirrored mode, does this mean you have to open the phone and the AMOLED screen has to be 'on'? On can all of this just stay in the 'background'? And does mirroring to an additional lag beyond the usual - and much slower - e-ink refresh rate? If anybody has any first-hand experience with this, I'd really be curious... Thanks!
sdspieg said:
Thanks Jeopardy. Can you (or anybody else) tell me whether there is an active developer community working on those EPD apps? And also - if you have to use mirrored mode, does this mean you have to open the phone and the AMOLED screen has to be 'on'? On can all of this just stay in the 'background'? And does mirroring to an additional lag beyond the usual - and much slower - e-ink refresh rate? If anybody has any first-hand experience with this, I'd really be curious... Thanks!
Click to expand...
Click to collapse
Well there are some developers, myself included, working on EPD applications. But not a lot. There should be more once Yota releases the device in USA around mid-August.
Mirrored mode does not need the color screen to be turned on. Of course behind the scenes it will wake up the system to similar state as if the AMOLED screen was on, but that's handled automatically. This means more battery use, but you should get a lot more out of it than using the color screen, especially on static apps like word processors which don't update often.
You can handle everything from the EPD. You can, for example, create a shortcut on the EPD for a word processing app, which will automatically enable mirroring and open that application. The lag on EPD when mirroring should be about the same as on native EPD applications, but of course you will notice it more because you can easily compare it to the non-laggy color side. There's only a few extra algorithms for turning the color image to nice greyscale, and some logic for creating additional "flashes" to fix ghosting when switching between apps etc. Should be fine for word processing, especially on external keyboard, provided you can write without constantly checking which letter you just pressed. The refresh rate on the EPD is about 8 frames per second, or one frame every 0.12s.
If you're seious about outdoor word processing may I suggest a rooted Nook Simple touch? It is small and light and a fraction of the price of a Yotaphone... as well as having a much bigger screen! You can pick these up for around 40GBP in good/new condition and although it will be a fair bit of messing around with rooting you are unlikely to come totally unstuck, and there is a lot of support on XDA to get you help if you do. With the NST device, you use the OTG USB mode to attach a bluetooth dongle, hard wired full sized keyboard or whatever to your desire. Pop over to the NST forum and there are many threads on this topic, but to whet your appetite here's someone who is doing that with a solar panel to power the setup!
http://forum.xda-developers.com/nook-touch/general/nook-simple-touch-solar-power-t3068849
Hi All
Anyone having this problem where the Dex resolution is only showing FHD and HD+? 1440p, WQHD+ is not even showing on my phone. I saw many other users their selection is greyed, while mine is not showing up at all.
Just FYI, it seems that other folks are saying after updating to Andorid 12, it works
https://www.reddit.com/r/SamsungDex/comments/quqowj
Guess i'll have to wait till Jan to know.
Update. Finally updated to Android 12 One Ui 4.0
Even with Multistar installed and I love Dex setting enabled for higher resolution. My DeX Resolution itself is still only showing 16:9 available.