Related
Hi!
Since last week, I've been working on an usable kernel for the HTC Vox. I guess you've already looked at this post: http://forum.xda-developers.com/showthread.php?t=368014&page=5
More or less, I have a working kernel. I've tested some images against the modified kernel, and both Gpe and Opie get to the welcome screen (without getting stucked). Nothing is really usable, as they're not even compiled for this specific platform (cannot get to compile opie for arm by myself... yet), but as a base, it's not bad at all.
As I've seen on my previous post, there's people interested on this (3300 views make me believe that), what I would want to know is, are there more developers interested on building a linux port for the Vox? Testers will be needed also, but later, when we get to something useful for testing
If you're interested, reply!
Cannot help u develop anything here, but would be a willing tester for it... thoroughly
I'd love to help, but I'm in the middle of moving to a new place and won't have internet most of the time next 2 weeks.
Do you have a Wiki or other place for collaberating? SourceForge perhaps?
I do have a wiki, but upload is no faster than around 80kB/s
In case you haven't seen it, you have a new build of the kernel on the other post, along with links and a little manual to start a graphic environment on the vox.
@barth666, @StefanHamminga
I've been thinking about it, and... I don't know what to do I mean, I think Sourceforge is the best place to dump it all, and it gives us a wiki too. On the other side, here is the xanadux wiki, and maybe it would be a good idea to let sourceforge host the files, and leave the wiki in here with other HTC phones... what do you think?
Oh! For GPIO dumping, the only thing I've seen working is the linwizard project's Haret_Omap.exe (in case you want to try to guess where the damned keys are )
PS: Anyone has an HTC Tornado? I'd love to know if the tornado kernel makes the leds and vibrator flash, I can't find where they are!
biktor_gj said:
PS: Anyone has an HTC Tornado? I'd love to know if the tornado kernel makes the leds and vibrator flash, I can't find where they are!
Click to expand...
Click to collapse
I have a tornado (and vox and wings), so tell me what to test
I know from the ml_iPod wiki (I am the admin) that SourceForge is really slow and the Php and Sql versions are old, in case you want to set up something like MediaWiki! You might want to try http://code.google.com/ , it has a built in Wiki and you can host files!
Just a suggestion
Keep up the good work
EDIT: I could even set one up, if you want, but I am not into coding at all!
Hi! Sorry for the delay, but I'm having lots of work this week and I've been unable to keep on with this...
@Walram: On the following days I'll try to build a kernel for you, wich should put all the lights on and makes the phone vibrate until you take the battery out Obviously just for testing, it shouldn't break anything, but I need to know if the originally-made-for-the-tornado vibrator and led drivers actually work on the tornado... Thanks!
@Frauhottelmann
Didn't know that google gave that service too! will look at it this weekend and post back when I have something done with this.. thanks for the feedback!
walram said:
I have a tornado (and vox and wings), so tell me what to test
Click to expand...
Click to collapse
Hi!
Ok, here's what I want you to try. If you haven't downloaded it yet, download the Linux Test Image:
http://rapidshare.com/files/93938763/test.zip.html
Then, download the kernel for the tornado:
http://rapidshare.com/files/96145010/kernel_tornado_driver.tar.gz.html
Dump the contents of the first file to the memory card, and then overwrite the file "zImage", with the one from the second link. Run haret, and hit "Run".
It should, at least, boot. If it doesn't, tell me where it gets frozen (could be that you only se some dots on the screen, whatever appears, just tell me )
If it boots, don't stop looking at the leds (charge/bluetooth leds mainly), they should, at least, flash -theorically they should stay on all the time-. It also should vibrate, at least for a quarter of second
I just need to know what it actually does!
Thanks!
So what about a dev-page? Then you don't need to upload it to Rapidshare and you can see the progress better!
Hi frauhottelmann,
I'm going to tell you the truth. I think it would be better if it's you who admins a site for this project than if I do, for various reasons:
1. I started all this thing, but I'm no owner of anything, by now I just hacked four things to make this phone boot a kernel, but no more.
2. I've seen your work at the ml_ipod sourceforge page, and think it's usable, clean, and nice, and I think that's exactly what we would need (even if it's a little slow just as you stated in your previous post). I could make the graphics for the web (I'm quite decent at photoshop), but I have never built a wiki, or a project anywhere else, and I don't know a sh** about it, so that would be another big thing to learn, and for now, I gotta learn more about the linux kernel, and that itself it's huge.
3. I don't think I can handle work, classes, building patches, kernels and bootstrap images and administrate a site, it feels like too much for me
Conclussion? I think it's better to let people do what does better, and I'm quite sure you'll do it better than I, so if you want, it's all yours
PS: In any case, we will need a name for the project, any suggestions?
What I have heard from the ml_iPod developers is that upload to SF is not a nice process either. I still think Google code is better, although it's not as customizable as SF.net. But we could also set up a page on Googlepages (pages.google.com) and then point to the Google code site with the Wiki and downloads!
I can offer my technical know-how (SPL, GPIOs, etc.)
Since I have little time you should ask me precise questions for which I can try to find the answers.
Sorry for the delay...
frauhottelmann said:
What I have heard from the ml_iPod developers is that upload to SF is not a nice process either. I still think Google code is better, although it's not as customizable as SF.net. But we could also set up a page on Googlepages (pages.google.com) and then point to the Google code site with the Wiki and downloads!
Click to expand...
Click to collapse
So we can start using google code, and stick with it if it goes well. We can always change the hosting if something goes wrong! About the wiki, the easiest thing is start with google code too, and simply link the xda wiki to it...
i can't code, but i can keep you company maybe
i am here if help is nedeed
But what name do we want to use?
Linux for Vox?
LinVox !
how does that sound ?
just kidding
waiting to get linux running on my vox....
But what name do we want to use?
Click to expand...
Click to collapse
Hooked on Vonix!
vonix sounds ok
can also try "Mobile TUX"
wow
this is an incredible news ! linux on the Vox !
I'd love to flash mine with a movibuntu distro =)
How do you guys feel about splitting the project up in several subprojects?
Like:
Kernel and driver work: TI OMAP HTC Vox board patch and perhaps drivers
Base system: minimal rootfs and toolkit to utilize all Vox functionality
Usability: GUI and (for instance) Android support
This would also enable us to share the base system & usability work with other 'linux on smartphone' and embedded projects.
I do have a suggestion for the base system:
www.emdebian.org
Very up to date build toolchain for arm (GCC 4.x toolchains) and you can have apt support on the base rom. This would allow access to a huge amount of packages that can be used with relatively little effort. Others I've checked out are the new mobile ubuntu (system requirements way to high), MontaVista (severe lack of proper documentation to get up to speed quickly), uClinux (uses ulibc instead of the faster full fledged one, in my opinion we'd better trade some storage for more speed) and some others I can't remember now...
PS. I've got internet at my new place and I've recovered my bricked wizard from the 'spare electronics bin', so finally I can spend some more time on this
*** PLEASE READ CAREFULLY BEFORE INSTALLING OR FLASHING ANY SOFTWARE POSTED IN THIS THREAD ***
The software posted here is for TESTING purposes only, The Polaris Android Linux development team or any of the posters of software or links to software on this thread, take absolutely no responsibility or liability for damage caused by the result of installing or flashing software or links to software found on this thread - correctly or otherwise, you do so on the sole understanding that you do so at your own risk. A final version will be posted on completion of a version 1 kernel at which point testing and support for the kernel will be moved to a suitable thread. Please do NOT post support questions on this thread - this is a development thread ONLY.
Development work is sometimes done in the irc channel: #htc-linux. To follow the latest developements please read the daily logs which can be found at: http://irclog.iclem.net/?chan=htc-linux&day=13
Lastly, Please do not use bad language in your posts, I have my little girl with me most times and do not need her to read such things. Appreciate your understanding.
Update: We now have a few threads devoted to userspace (system images), This is a KERNEL DEVELOPMENT thread which is starting to get too big for devs to follow. The purpose of a good development thread is to serve as an archive and a blueprint for future developers and that is hard to do when you have hundreds of non-related posts. I have therefore asked the moderator to move all non-kernel posts to their appropriate threads.
-----------------------------------------------------------------------------------------------------------------------------------------------
01-09-08 - new link to files for working wifi
http://www.4shared.com/dir/19593527/3cb53c3a/sharing.html
24-07-09 - If anyone is interested in making themed system images, he's posted this link to help you learn how to do it:
http://forum.xda-developers.com/showthread.php?t=471586
19-07-09 - New kernel with changes from Vogue branch released. I am currently testing radios and resolutions. List of resolutions from kaiser thread
15-07-09 - A revival in our development as meant we are now catching up with the other devices with development on the project. Thank you to all who donated to the purchase of development Polaris that will be used by vilord, from vogue forum to help us with the project.
Current developers:
Life02 - Fixed GPS, Working on Battery issues.
Vilord - On holiday, now in possession of a Polaris. Also working on Bluetooth.
Newbie16 - Fixed Wifi - need to add irq's.
05-07-09 - New 1.5 ION build of Android for the Vogue has been reported to work well for the Polaris and can be found on the Google Vogue repository. The new 1.5 builds are noticeably also faster and smoother than previous builds. Some troubleshooting info can be found at the Androidhtc website for these builds (thanks freddycs). APN details can be found on Wikipedia - (thanks Mormy)
Things that do NOT work at present:
Bluetooth - No - Working partially for Vogue
Wifi - WORKING! *NEW* - thanks to a lot of effort by my friend Newbie16 - thanks mate
Camera - No - Working for Vogue
GPS - now working thanks to life02! - Well done my friend
---------------------------------------------------------------------------------------------------------------------
A new thread for budding designers has been set up by Venigo, (thanks matey!) who will lead the design side of the Polaris Android project (kind of makes you a little emotional thinking we're at that stage where we can start thinking about wallpapers and themes doesnt it?) Thread can be found here: Polaris Linux Android - Wallpapers, Themes and Icons
UPDATES: - Please check the WIKI for up-to-date progress updates here: Android on Polaris WIKI (Thanks excogitation)
NEW TESTING AND BUG THREAD ANNOUCEMENT:
marcelkordek has kindly started a thread for testing and bug reporting as we now have an almost usable Android image which can be found here: Polaris Android Project - Testing and Bug Reporting The thread will also be used to provide updates on the progress of the Android kernel as well as providing feedback to the devs on the latest posted images. Please ensure that the Testing and Bug Reporting thread is used for reporting user experiences and enable to keep the development thread cleaner and make life easier for the devs, whom you will all agree are doing an excellent job to support our beloved device.
18/1/09 - Working Radio with calls at last! Audio and SMS still not working but GPRS does but with a bit of fiddling.
16/1/09 - SMD code is nearly fixed by DZO, Rogro82 will be making a new image soon. Most of the development at this time is being reported in the Kaiser forum: UPDATED!!! - Google Android and Linux for KAISER!! as DZO was sent a Kaiser and he is working on the issues on it.
5/1/09 - DZO is working to bring the Kaiser and Polaris branches together so that the kernel will work on all our devices. Waiting to see what changes are made.
1/1/09 - Rogro82 uploaded a "booting" 1.0 SDK along with source files and instructions (below). Although this is very much a work-in-progress, it is the first bootable version of the 1.0 SDK for the Polaris.
11/12 - DZO and rolk worked out some changes that may help us resolve the SD Card stability issue. Dwaradzyne posted up a Zimage with the changes for testing.
CPLD Handbook
GPIO Manuals
LATEST FILES USED FOR DEVELOPMENT:
1/1/09 - Latest files are packed in this archive - to boot simply unpack to the root of your sd card and run haret (included).
A big THANK YOU to Rogro82 for getting the 1.0 SDK booting on the Polaris
Enjoy!
-----------------------------------------------------------------------------------------------------------------------------------------------
FIRST POST
I'll start with another simple question I cant find an answer to:
WHY CANT WE JUST PORT THE G1 ROM TO THE POLARIS?
#2 reserved for update
I will try to search too
I will try to put as simple as possible. Building a ROM requires combinig two parts:
1. Kernel/drivers part.
2. Applications and stuff.
In case of Windows Mobile part 1. in practice always comes from official HTC Polaris ROM. Part 2 comes from other official HTC ROM (could be other phone) and it can be modified by cooker.
We do not have a full working Polaris Android ROM, and we cannot just cook without part 1. Part 2 is available as Android sources are open.
The reason why we did not have 3d driver working on Polaris immediately after first Diamond ROM was available is that part 1. is not transferrable from one model to another.
Part 1. in Android is Linux kernel. We must get involved in Linux kernel developement for Polaris to bring Android to our phones.
why do we always want our phones to look like other phones. why cant we just be unique. we are windows mobile. TOP DOGG. i like windows mobile theme especially when its black. i like g1 but the design looks ancient. its not 2008 more like 1998
dortyboy said:
why do we always want our phones to look like other phones. why cant we just be unique. we are windows mobile. TOP DOGG. i like windows mobile theme especially when its black. i like g1 but the design looks ancient. its not 2008 more like 1998
Click to expand...
Click to collapse
absolutely agree. Copying iPhone was fun the first 2,3 months. Why not trying to develop really good apps with nice UIs and make own ideas into real interfaces for throttle launcher, M2D etc etc - posibilities are nearly endless.
i absolutely agree. i havent seen not one cool program thats actually usefull in our daily life for windows mobile not since i had a treo way back.
programs like directory; that could look at your number and tell u the owners name and adress
stuff like that. maybe tell u when zip code the call is coming from. useful programs. not the crappy programs that just try to make your phone look pretty.
thats why people go to iphone, the programs are useful in peoples daily life but not windows mobile
Here we go
ROM download :
Code:
http://rapidshare.com/files/155612986/Android_dump.rar
I think its a probleme with the boot loader and some part of the android code which isn't public
Have look here :
Code:
http://www.limofoundation.org/en/limo-press-releases/limo-foundation-statement-on-the-google-android-g1-handset.html
dortyboy said:
why do we always want our phones to look like other phones. why cant we just be unique. we are windows mobile. TOP DOGG. i like windows mobile theme especially when its black. i like g1 but the design looks ancient. its not 2008 more like 1998
Click to expand...
Click to collapse
Are you new to the mobile device world?
We are not trying to get it to "look like the G1". We are talking about using a completely different operating system.. lol.. and you are talking about a black windows mobile theme and how the hardware of the G1 looks ancient.. lol..
Oh.. and "being unique" in this case would be having Android on a non G1 phone.. that would be unique. Windows mobile is not unique.
m.schmidler said:
absolutely agree. Copying iPhone was fun the first 2,3 months. Why not trying to develop really good apps with nice UIs and make own ideas into real interfaces for throttle launcher, M2D etc etc - posibilities are nearly endless.
Click to expand...
Click to collapse
Developing apps and trying to use resource hog throttle launcher is nothing close to having a brand new stable device operating system.
m.schmidler said:
absolutely agree. Copying iPhone was fun the first 2,3 months. Why not trying to develop really good apps with nice UIs and make own ideas into real interfaces for throttle launcher, M2D etc etc - posibilities are nearly endless.
Click to expand...
Click to collapse
Maybe we can develop better apps under Android?
Look at the apps currently available for iphone - hopefully Android will get better market penetration than Windows Mobile, and, because it's open source it opens up a whole range of possibilities for developers.
I say if it can be done, it should be done!
dwaradzyn said:
I will try to put as simple as possible. Building a ROM requires combinig two parts:
1. Kernel/drivers part.
2. Applications and stuff.
In case of Windows Mobile part 1. in practice always comes from official HTC Polaris ROM. Part 2 comes from other official HTC ROM (could be other phone) and it can be modified by cooker.
We do not have a full working Polaris Android ROM, and we cannot just cook without part 1. Part 2 is available as Android sources are open.
The reason why we did not have 3d driver working on Polaris immediately after first Diamond ROM was available is that part 1. is not transferrable from one model to another.
Part 1. in Android is Linux kernel. We must get involved in Linux kernel developement for Polaris to bring Android to our phones.
Click to expand...
Click to collapse
Thanks for the idiots guide dwardzyne!
So that very clearly explains the kernel level requirement.
OK. Second question:
With regard to part 1 - Kernel/Drivers - Can we convert the vogue version since it seems to have the most work done to it? What would need to be done to it to make it work?
imfloflo said:
I think its a probleme with the boot loader and some part of the android code which isn't public
Click to expand...
Click to collapse
a boot loader :
Code:
http://www.denx.de/wiki/U-Boot/WebHome
bally3 said:
Thanks for the idiots guide dwardzyne!
So that very clearly explains the kernel level requirement.
OK. Second question:
With regard to part 1 - Kernel/Drivers - Can we convert the vogue version since it seems to have the most work done to it? What would need to be done to it to make it work?
Click to expand...
Click to collapse
Indeed kernel developement for Kaiser and Polaris is based on Vogue work. It slowed down because of SD stability issue.
dwaradzyn said:
Indeed kernel development for Kaiser and Polaris is based on Vogue work. It slowed down because of SD stability issue.
Click to expand...
Click to collapse
I believe the sd card issue has been resolved on vogue and they've moved onto other things (camera etc). but it seems like its the end of the road for the Polaris - apart from rumors that someones supposed to be sending a kaiser or a polaris to dzo for him to work from. This kind of points to that dzo is the only person on xdevs capable of working at kernel level with a kaiser or polaris?? That cant possibly be true - can it?
bally3 said:
I believe the sd card issue has been resolved on vogue and they've moved onto other things (camera etc). but it seems like its the end of the road for the Polaris - apart from rumors that someones supposed to be sending a kaiser or a polaris to dzo for him to work from. This kind of points to that dzo is the only person on xdevs capable of working at kernel level with a kaiser or polaris?? That cant possibly be true - can it?
Click to expand...
Click to collapse
He already has the knowledge... He wants to share his knowledge, if someone send him a Kaiser or Polaris, and will make it work... I thought there were plenty of users willing to send there old or half bricked kaiser or polaris... but still nobody send him one... as far as I know...
Nobody keeps nobody up to date in the kaiser thread... So I really don't know what is going on... But they still don't have a decent fix for the DMA (SD-Card read/write) problem (as far as I know).
Porting the G1 rom isn't a possibility, you first have to have drivers for our device, since we haven't got a driver to read/write to the internal memory (not the RAM), it still cannot boot .
I hope this project will really come of the ground finally... It's half way there... but still not finished (if you ask me, due to miscommunication and not working together of users, because they all want to be the first who got it working to show off with it... (so they are all working on the same piece of code, which is a waste of time if you ask me)).
Maybe one of us can contact DZO, check what he needs to continue our development. Because without the SD-Card driver we can't continue...
dubbeld00 said:
Maybe one of us can contact DZO, check what he needs to continue our development. Because without the SD-Card driver we can't continue...
Click to expand...
Click to collapse
I'll contact him, I dont think there are many users who would just send a device worth a couple of hundred euros to a complete stranger though many would tell you they would at the time. With the P3D driver their was only one person who was willing to loan a unit for development - and that was only because they were in the same country. I was asking for ages before that.
is their any other way we could help him? surely the internal workings of a polaris rom coupled with the specs could be used if dzo would do what NuShrike did on the p3d driver which was tell us to try things he worked on? I'm sure there would be willing volunteers including myself who he could talk through it on the forums or on the #android room.
I can't offer to donate my polaris as its the only mobile I have.. but I would be more than willing to try things out on my xda or provide any other help possible to get this project moving.
Hopefully one day a fully working Android will be a reality on polaris
As some of you probably know, the ps3 has recently been hacked, allowing us to run unsigned code. The source code for the exploit leaked and a dev called KaKaRoTo managed to get it to run from a Nokia N900. The other day, KaKaRoTo released his source code and someone already ported it to the Palm Pre. This quick port was possible because the N900 and Palm Pre both share the same USB controller(mUSB) which happens to be the controller used by the Droid/Milestone.
This has already been posted in the droid section, but I figured I would post this in here. Maybe some of you guys can get this working on our Samsung Galaxy Spica i5700!
thanks nicholasbgr for writing this up.
-------------------
Well, first, you need to figure out what controller your device uses, in the case of the N900, it’s ‘musb’.. (Luckily we have he same controller!)
Then go to the driver code for that controller (probably in drivers/usb/gadget) and look for ‘SET_ADDRESS’. In the case of musb, it was in drivers/usb/musb/musb_gadget_ep0.c. In there it was setting the address to the USB device, so just copy that code into the psfreedom_machine.c to allow setting the address, and add a similar function to be able to retreive the address.
Then add a function to return 0 or 1 depending on whether the controller supports HIGH, FULL or LOW speed mode (go to usb_gadget_register_driver for your controller, and in the first lines, it should validate the speed argument, it will tell you which ones are acceptable), set LOW speed mode to return TRUE only if FULL speed isn’t available .
Finally, add a function to return the endpoint names.. it will usually be something like ‘epXin’ and ‘epXout’ (where X is the endpoint number), or “epXin-bulk”, etc.. look at how the driver initializes its endpoints or grep for “->name” in the file to find where it sets it…
That should be enough!
-------------------
This doesn't look too hard to do either. We shouldn't need to do too many alterations to get it working on the milestone.
Here is what we apparently need to do to port it from the nokia.
And here's a link to the source code over at github:
PSFreedom
http://www.klutsh.com/
Thanks and good luck to anyone who gives this a try!
Only created my account today, so I don't have enough posts to put this in the developer section. Maybe someone can help me out.
I managed to get the Quake2 source from Ids ftp server to build (with a lot of warnings) for ARM in Visual Studio 2012.
I've attached a screen shot and the binaries to this post.
All you need to do is drop the pak0.pak and players folder into baseq2.
Enjoy!
EDIT: should also mention that this is a native port (not .net or winrt) -- props to XDA guys for the hack!
EDIT2: for those with errors, keep in mind you need the pak files and players folder from the quake2 install for this to work (or you can grab them from the demo). Google is your friend! . If you encounter the famous "water crash" then run "sw_waterwarp 0" in the quake console.
EDIT3: For a joke. I've added the OpenGL Quake2 renderer and a software based OpenGL implementation (built from an older version of Mesa3D) as attachments. Given that Windows RT doesn't have support for OpenGL this is probably as good as its going to get without a port that has Direct3D support. While the OpenGL version looks much better, be warned.. it runs __very__ slow. If you want to give it a try, just go into video options and change the 'driver' option to "default opengl". Enjoy!
EDIT4: So.. in an effort to clean up some of the bugs, I stumbled upon KMQuakeII which has an 'unofficial' 3.23 patch for the Quake 2 source. I've managed to compile that version of the source for ARM. I was hoping this would fix the full screen issues, but it didn't. Regardless, there are probably worthwhile bug fixes anyway.. so I'm posting it here. There are also extra video modes in this version (very easy to add btw!) however the 1366x768 mode didn't work correctly on my Surface.
Well done! Link added to the list. Much appreciated...
bfosterjr said:
Only created my account today, so I don't have enough posts to put this in the developer section. Maybe someone can help me out.
I managed to get the Quake2 source from Ids ftp server to build (with a lot of warnings) for ARM in Visual Studio 2012.
I've attached a screen shot and the binaries to this post.
All you need to do is drop the pak0.pak and players folder into baseq2.
Enjoy!
EDIT: should also mention that this is a native port (not .net or winrt) -- props to XDA guys for the hack!
Click to expand...
Click to collapse
cool, seems to run nicely, -just using one core.
At first : Thanks for the work!
But i get an Error :"Couldn't load pics/colormap.pcx
(on Surface Jailbrocken)
I can't manage to open it. It says there is an error.
Another question... I want to do it for Bluestacks. Do you know anyone that could've done this? Thank you.
save_jeff said:
At first : Thanks for the work!
But i get an Error :"Couldn't load pics/colormap.pcx
(on Surface Jailbrocken)
Click to expand...
Click to collapse
Make sure you have the pak files and players folder from your quake2 install in the baseq2 folder. If you don't own quake2 then you can grab these files from the quake2 demo install (google for it). Good luck!
Awesome job!
I got mine working smoothly
There is some issues that often when I load saves the game crashed (quake2.exe has stopped working)
I have no idea. Save game works perfectly and start new game works as well.
Looks like this guy back in 2005 have the same problem (except he is using... Amiga?): ht tp://eab.abime.net/showthread.php?t=17808
Tanks i did not know that ;]
I Will get a Demo right now ans try ist.
Does it work with any Version of quake II ?
---------- Post added at 10:54 PM ---------- Previous post was at 10:29 PM ----------
Okay now it works like a charm! Realy impressiv
shog7n said:
Awesome job!
I got mine working smoothly
There is some issues that often when I load saves the game crashed (quake2.exe has stopped working)
I have no idea. Save game works perfectly and start new game works as well.
Looks like this guy back in 2005 have the same problem (except he is using... Amiga?): ht tp://eab.abime.net/showthread.php?t=17808
Click to expand...
Click to collapse
Yeah, there could be several bugs in it. This is built straight from iD's source. There are many other 'ports' of quake2 that have encountered and (in some cases) fixed various bugs. Still, its extremely playable even with a few annoying bugs!
I cant get mine to go to full screen.... is this usual behaviour?
advancedservers said:
I cant get mine to go to full screen.... is this usual behaviour?
Click to expand...
Click to collapse
Yep. The pure Quake2 source has known issues with full screen on "odd" resolutions. Given the time frame for when Quake2 was developed.. the 1366 x 786 resolution that is common today doesn't make any sense that's why its "not supported". There were some unofficial patches added to Quake2 many years ago to add wide screen support and more resolutions. A lot of people also fixed the problem by just using the OpenGL version (which I could also provide binaries for.. but its _dog_ slow). What I've ported here is the 'software render' which got very little attention once the '3d boom' hit. If I get bored, I may see if I can get full screen working in the software renderer.
Joystick or Xbox Controller?
App is cool and runs well with mouse or keyboard but I have tried joystick and Xbox controller (both recognised by WinRT) and app ignores both. I have turned on Joystick under options.
I didnt get any bugs yet.
But Fullscreen would be nice
Woww this game bring me so many good memories nice work!!!
advancedservers said:
I cant get mine to go to full screen.... is this usual behaviour?
Click to expand...
Click to collapse
Same here. 800x600 is the best resolution to me..
Btw can you load your saves after close the game and restart it?
For what its worth, I've updated the original post with 'newer' binaries and software based OpenGL support. The fullscreen thing is also bothering me so I'll put some effort into that over the next couple days -- hopefully its been fixed in a different Quake2 port and I just need to migrate the code over. Cheers!
If you don't mind me asking where did you get the source files from? I would have done this two days ago but I couldn't open the project files from id's github. I then tried quake 3 and doom 3 but getting those working is a different problem entirely. Those games have inline assembly in them that I don't have the skill to replace.
johnnyfives12 said:
If you don't mind me asking where did you get the source files from? I would have done this two days ago but I couldn't open the project files from id's github. I then tried quake 3 and doom 3 but getting those working is a different problem entirely. Those games have inline assembly in them that I don't have the skill to replace.
Click to expand...
Click to collapse
The source came straight from ftp.idsoftware.com. There is a lot of pain in getting a working vs2012 solution file and convincing the source that Win32 does not imply x86! Many issues with libs and older CRT functions too. Just takes time, patience and good experience with VS & C code.
You're absolutely right about Q3 or Doom3. They will require an overhaul and will need to be ported to Direct3D10+. Sadly I don't have the spare time to get _that_ involved -- though I'm happy to help if someone wants to lead the charge.
Cheers
Game crashes sometimes when I try to load a saved game. Also performance is far from what I expected. I remember playing it on my Nokia n95 with software renderer and it was fluid, on surface higher resolutions cause serious performance degradation. The more I use desktop apps ported to Windows RT(quake, dosbox) the more I think that tegra 3 suck.
bartekxyz said:
Game crashes sometimes when I try to load a saved game. Also performance is far from what I expected. I remember playing it on my Nokia n95 with software renderer and it was fluid, on surface higher resolutions cause serious performance degradation. The more I use desktop apps ported to Windows RT(quake, dosbox) the more I think that tegra 3 suck.
Click to expand...
Click to collapse
Same loading problem here...
But it runs pretty fluid on my Surface...
Listen to live FM broadcasts on devices that don't have a built-in FM radio!
Description
SDR Touch turns your mobile phone or tablet into a cheap and portable software defined radio scanner. Allows you to listen to live on air FM radio stations, weather reports, police, fire department and emergency stations, taxi traffic, airplane communications, audio of analogue TV broadcasts, audio amateurs, digital broadcasts and many more! Depending on the hardware used, its radio frequency coverage could span between 50 MHz and 2.2 GHz. It currently demodulates WFM, AM, NFM, USB, LSB, DSB, CWU and CLW signals.
You can get a compatible USB receiver for under $20 online from eBay. Just plug in your rtl-sdr compatible USB DVB-T tuner into your Android device using a USB OTG Cable and turn on SDR Touch. For list of supported Realtek RTL2832U based dongles, please see the end of the description.
Compatible USB DVB-T tuners
- Generic RTL2832U (e.g. hama nano)
- ezcap USB 2.0 DVB-T/DAB/FM dongle
- Terratec Cinergy T Stick Black (rev 1)
- Terratec NOXON DAB/DAB+ USB dongle (rev 1)
- Terratec Cinergy T Stick RC (Rev.3)
- Terratec T Stick PLUS
- Terratec NOXON DAB/DAB+ USB dongle (rev 2)
- PixelView PV-DT235U(RN)
- Compro Videomate U620F
- Compro Videomate U650F
- Compro Videomate U680F
- Sweex DVB-T USB
- GTek T803
- Lifeview LV5TDeluxe
- MyGica TD312
- PROlectrix DV107669
- Zaapa ZT-MINDVBZP
- Twintech UT-40
- Dexatek DK DVB-T Dongle (Logilink VG0002A)
- Dexatek DK DVB-T Dongle (MSI DigiVox mini II V3.0)
- Dexatek Technology Ltd. DK 5217 DVB-T Dongle
- MSI DigiVox Micro HD
- Genius TVGo DVB-T03 USB dongle (Ver. B)
- GIGABYTE GT-U7300
- DIKOM USB-DVBT HD
- Peak 102569AGPK
- SVEON STV20 DVB-T USB & FM
Interaction with battery savers
It turns out some manufacturers such as Huawei and Samsung have very aggressive power saving policies and force close background apps without notice. If the system decides to kill the RTL-SDR (or SdrPlay) driver while SDR Touch is running, the app will stop playing and become unresponsive eventually showing a "Disconnected unexpectedly" error message.
If you are experiencing this issue, the only solution that currently exists is to manually whitelist *both* the SDR driver app and SDR Touch in your phone's power saving settings to prevent the operating system from unexpectedly stopping the apps. More information and instructions on how to do this based on your particular phone make and model can be found on this website: dontkillmyapp.com
Feedback
An article about SDR Touch - Android Meets the RTL2832U from HamRadioScience
A user submitted video showing off advanced features of SDR Touch running on a mobile phone:
Any additional feature suggestions, comments or feedback will be much appreciated!
looking good sir looking good
Fantastic work. I am excited to see squelch on the list of improvements. Is there any chance that you will ever support a plugin architecture or P25 decoding? There is a decoder called DSD which can decode P25. Squelch+P25 would make it replace my scanner entirely. I would pay additional $$ for each of these features and it would still be more affordable and interesting than carrying around a scanner.
daniel_reetz said:
Fantastic work. I am excited to see squelch on the list of improvements. Is there any chance that you will ever support a plugin architecture or P25 decoding? There is a decoder called DSD which can decode P25. Squelch+P25 would make it replace my scanner entirely. I would pay additional $$ for each of these features and it would still be more affordable and interesting than carrying around a scanner.
Click to expand...
Click to collapse
Thanks for the support! Squelch is coming soon! I will look into P25 but we might need to work together on this - you may need to provide me some I/Q recorded samples - but I would say this would be a bit later since I just started my second semester and have some studying to do as well
P.S. Squelch is now on top of my TODO list
Although this seems to be a great app, I couldn't make it to work with Xperia Ray... ("no tuner found" error)
Anyone here had success with making it work on a Xperia phone?
martintzvetomirov said:
Thanks for the support! Squelch is coming soon! I will look into P25 but we might need to work together on this - you may need to provide me some I/Q recorded samples - but I would say this would be a bit later since I just started my second semester and have some studying to do as well
P.S. Squelch is now on top of my TODO list
Click to expand...
Click to collapse
Fanastic, thank you. I can't wait for squelch!
I'll supply whatever data/info you need to implement P25. I/Q samples are no problem. I understand completely that your time is limited and there is a larger audience to serve, but if you need resources, please let me know what you need and I'll see how I can help.
My account here is new, so I can't post links, but "DSD" and "radioreference wiki" will get you to the DSD source.
Amazing work! Well worth the $9.99USD pricetag. Gave you a nice review on the Google Market/Play Store as well.
FYI: Works wonderfully on an Acer A500 w/ Android 4.2.1.
SDR Touch has been removed by Google from Google Play! I will investigate the issue and will report back as soon as I have more information!!!
If somebody needs the latest version of SDR Touch, please download it from the attachment. Keep in mind that as soon as SDR Touch goes back to Android market you might need to reinstall it in order to get the latest updates!
Ok, just to make it clear for everybody that is concerned.
SDR Touch DOES NOT violate the GPL license!
SDR Touch is merely a client for - https://github.com/martinmarinov/rtl_tcp_andro-. rtl_tcp_andro is released under GPL2+. SDR Touch and rtl_tcp_andro are separate works in the sense of GPL. They are neither statically or dynamically linked and they are two separate executables that communicate over a TCP connection. rtl_tcp_andro is bundled with SDR Touch merely to help the user and with accordance to point 2. of GPL Terms and Conditions. You can think of SDR Tocuh as an "installer" of rtl_tcp_andro. It just launches rtl_tcp_andro with Runtime.exec("");. Furthermore SDR Touch could happily work without the bundled rtl_tcp_andro in network mode by connecting to a remote computer running either rtl_tcp_andro or the original rtl_tcp.
Therefore GPL is not violated. Saying that GPL is violated would be like saying that you can't listen to online radio with your proprietary music player because the radio is being streamed with a GPL based software.
A quote from GPL-3.0:
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
Click to expand...
Click to collapse
Did you read that quote ?
... and which are NOT combined with it such as to form a larger program, in or on a volume of a storage or distribution medium ...
Click to expand...
Click to collapse
A single .APK _is_ a single distribution medium ... and they definitely _ARE_ combined to form a larger program. The "SDR Touch" .APK is the larger program, containing both your own code and the rtl_tcp_andro binary. That clause is meant for when you ship a CDRom with different stuff on it for example where they have no special relation ship. Here the relation ship and dependency is clear (even says so in the damn description of the app)
The problem is not with SDR Touch or the way it's a client for a rtl_tcp version, that's the right way to do it.
The problem is that both are distributed bundled.
SDR Touch and rtl_tcp_andro need to be two separate packages to be installed independently by the user.
There is also the requirement to make a written offer and include the full license terms when distributing rtl_tcp_andro, usual way is to include both the license in the .APK and also accessible to the user in the UI (menu often).
Cheers,
Sylvain
smunaut said:
Did you read that quote ?
Click to expand...
Click to collapse
But rtl_tcp_andro is a separate binary and the apk is just a container like a CD Rom. That's precisely the point. The binary classes of SDR Touch are separate entities in the apk file and are not linked to rtl_tcp_andro!. The GPL allows using an "installer" to install proprietary software as well as GPLed software in one go. The Android apk installer grabs the contents of the archive (which is like a rar archive) and unrars it ("installs") it onto the device. When the user is using the program, the two entities are still different and separate!
The license is linked in the Help section of SDR Touch. The thing that I haven't done is to put the license physically on the apk as well.
But that's a good point,
Thanks,
Martin
martintzvetomirov said:
But rtl_tcp_andro is a separate binary and the apk is just a container like a CD Rom. That's precisely the point. The binary classes of SDR Touch are separate entities in the apk file and are not linked to rtl_tcp_andro!. The GPL allows using an "installer" to install proprietary software as well as GPLed software in one go. The Android apk installer grabs the contents of the archive (which is like a rar archive) and unrars it ("installs") it onto the device. When the user is using the program, the two entities are still different and separate!
Click to expand...
Click to collapse
Mmm, first, I'm not sure the APK is uncompressed on the flash.
But you're missing the point that in this case it's a single "application", no matter what binaries it's composed of. It's not pulled independently (as a dependency or not) and via that "installer" you can't get it independently, it's just a single package, even presented as a single application to the user (aren't they both under the same 'title' in the "Application" tab of android ?)
So really, I don't see how you could consider this as not being a "whole" without, like I said, distribute it as two different packages (which would also allow other "users" to use the rtl_tcp_andro for eg) and give a undeniable separation between the two.
smunaut said:
Mmm, first, I'm not sure the APK is uncompressed on the flash.
But you're missing the point that in this case it's a single "application", no matter what binaries it's composed of. It's not pulled independently (as a dependency or not) and via that "installer" you can't get it independently, it's just a single package, even presented as a single application to the user (aren't they both under the same 'title' in the "Application" tab of android ?)
So really, I don't see how you could consider this as not being a "whole" without, like I said, distribute it as two different packages (which would also allow other "users" to use the rtl_tcp_andro for eg) and give a undeniable separation between the two.
Click to expand...
Click to collapse
Ok, I see your point and this looks like an option. I still can argue that they are separate but in order to prove that, as you say, I might split them into two packages.
Will see how things go, will keep you posted!
Like smunaut said, this definitely counts as a derivative work as they are being presented to the user as one cohesive application via the Play Store.
This is the same problem that SDR# had some time back, where they tried to distribute the GPL RTL-SDR with their proprietary UI. They thought that, since the UI only communicated with RTL-SDR and wasn't technically part of SDR#, they could include it; but that's not the case. (http://dangerousprototypes.com/2012/08/05/confusion-over-sdr-vs-opensdrsharp/)
The solution in this case will be the same as it was for SDR#: Either make the entire application GPL, or break rtl_tcp_andro into a completely separate package. Make sure that the description for the rtl_tcp_andro package clearly states its license, and make sure you link to the GitHub page for it so the source is clearly available. That should cover all the bases.
MS3FGX said:
Like smunaut said, this definitely counts as a derivative work as they are being presented to the user as one cohesive application via the Play Store.
This is the same problem that SDR# had some time back, where they tried to distribute the GPL RTL-SDR with their proprietary UI. They thought that, since the UI only communicated with RTL-SDR and wasn't technically part of SDR#, they could include it; but that's not the case. (http://dangerousprototypes.com/2012/08/05/confusion-over-sdr-vs-opensdrsharp/)
The solution in this case will be the same as it was for SDR#: Either make the entire application GPL, or break rtl_tcp_andro into a completely separate package. Make sure that the description for the rtl_tcp_andro package clearly states its license, and make sure you link to the GitHub page for it so the source is clearly available. That should cover all the bases.
Click to expand...
Click to collapse
Ok, this makes sense.
Actually this won't be a bad idea after all, I mean if there is a separate app "rtl_tcp_andro" that can do I/Q samples, this might help other developers write their own SDR based applications so therefore help the community.
I don't want to release the processing bit under GPL since it took me quite some time to optimize the algorithms to run on Android so I want to keep my work with this private and this is what Pro users are paying for but rtl_tcp_andro is in the public domain anyways, I will just wrap it around with an apk and release it under GPL.
Please add NetSDR support for RFSpare radios like NetSDR or SDR-IP.
I would pay 10x the Pro price for this! http://sourceforge.net/projects/cutesdr/ and http://cutesdr.svn.sourceforge.net/...face/sdrinterface.cpp?revision=36&view=markup will probably reveal how NetSDR format works.
stejc said:
Please add NetSDR support for RFSpare radios like NetSDR or SDR-IP.
I would pay 10x the Pro price for this! http://sourceforge.net/projects/cutesdr/ and http://cutesdr.svn.sourceforge.net/...face/sdrinterface.cpp?revision=36&view=markup will probably reveal how NetSDR format works.
Click to expand...
Click to collapse
I already have sever requests about this. I will keep this idea in the record. I will first need to make sure SDR Touch is working properly and implement the list of features in the first post.
Also, I was able to rapidly prototype so far but now I'm back in University and I am forced to slow down the development speed. So it may take some time.
Any chance to make the whole app Open Source? This would be a nice recognition of the hard work done by the rtl-sdr folks, and solve your packaging problem.
I have licensed APRSdroid (which btw. can modulate and demodulate Packet Radio using audio in/out) under the GPL, and I can not complain about people not getting the paid version from Google Play.
To the contrary, 80% of my users actually bought the app, and all without evil nag screens!
martintzvetomirov said:
Actually this won't be a bad idea after all, I mean if there is a separate app "rtl_tcp_andro" that can do I/Q samples, this might help other developers write their own SDR based applications so therefore help the community.
Click to expand...
Click to collapse
Absolutely. That is the idea behind the GPL in the first place, that other developers can benefit from improvements made to the code. Having a separate download for rtl_tcp_andro would definitely be a positive for the community, I could personally think of a couple interesting projects with it.
martintzvetomirov said:
I don't want to release the processing bit under GPL since it took me quite some time to optimize the algorithms to run on Android so I want to keep my work with this private and this is what Pro users are paying for but rtl_tcp_andro is in the public domain anyways, I will just wrap it around with an apk and release it under GPL.
Click to expand...
Click to collapse
Of course, it's your right to keep your own software closed source. I don't personally believe in keeping this kind of software closed, but it's your decision.
Though I would like to point out that this type of software is going to get paid downloads either way. The type of users you will attract with this kind of software are the same kinds of users who have no problem donating to open source projects. We aren't talking about some casual game here that just anyone will be downloading, this is an application developed for more technical users who have a pretty good idea of the amount of effort that goes into a project like this.
In any event, I'm glad to see you taking the proper steps to make sure your software is GPL compliant.
FUNcube Pro & FUNcube Pro Plus Support
Any chance FUNcube Pro & FUNcube Pro Plus Dongles Support can be added in the future.