hey guys
so there is a solidly large amount of new devices being ported to ubuntu touch and as the app has been in development hell i would like to bring it back and rework it to allow the great new devices thats been ported to it to use the app. I ran across team humpolecs original source code and i have it downloaded and ready to upload back to github.
i have been working on it and its pretty old stuff dating back to kitkat. wow. any way so adding new devices to the java and changing the adress to the ubports system-image site is pretty steaight forward. but im having trouble with a couple code snippets that are erroring my compilation but still to make it fully worthwhile i need to know how to get the boot and recovery partitions of the new devices that are popping up.
Also considering my own device has avb partitioning will this be a problem getting going. looking for volunteers to help me reboot the app any takers?
the main problem im having is fixing the deprecated progressDialog snippet. ive seen some examples and fixes but no matter what i try i get errors
Related
So I'm a bit of a android build system newbie - I can get as far as getting the source properly downloaded, and even compiling. In looking at the source for CyangenMod I notice that when you run lunch after calling . Build/envsetup.sh it has several options. It seems that all the "supported" devices have build configuration selections that start with cyanogenmod_*. So far the ones for the mecha/thunderbolt are only listed under htc_mecha-eng and htc_mecha-userdebug. I'd like to help port over cyanogenmod to the thunderbolt if I can, and at the very least be a fly on the wall so to speak to learn a bit about the android build system in general. My native development background is C#, so java comes naturally to me however ubuntu is a whole new beast for me and I'm trying to learn as I go and find out as much as I can - unfortunately I haven't found much about the different settings from lunch and ultimately what they produce once you run the configuration and then 'make' the build. Thanks for any info!
check out this change from the cm gerrit. http://review.cyanogenmod.com/#change,4618
It includes the files you need to get the mecha to show up in the lunch menu as cyanogenmod_mecha.
edit - in case you dont know otherwise cm is still quite broken for the mecha at this point. Everyone is still waiting around for the ril commits to come in
Thanks for the reply, I've heard of the garret system in passing but haven't actually used it yet - and I know the RIL is MIA - really just curious in getting my feet wet with the source - I have my old incredible if I want a totally functioning device, the mecha is just a chance I guess to poke around on my own.
Alright side question - so far I've just been using repo sync to get the source down - seems this was checked into the gingerbread branch on github, why wouldn't specifying -g gingerbread on the repo init pull down this change? Is it not actually committed yet? Excuse the ignorance - I appreciate the help!
I want to attempt to mess around with the Github source for the team win recovery project, to see if I can make a version for our Shift. I have the android sdk set up on my laptop (win7 home 64 bit), and I have downloaded the TWRP source from github (https://github.com/androidrbox/Team-Win-Recovery-Project).
I was looking at the "guide" here:
http://forum.xda-developers.com/showthread.php?t=1198420
Which points me to set up Eclipse IDE, but do I need that? What programs, other than the android sdk, do I need? I'm no java programmer. I come from a vb.net background, so I'm familiar with following code, so it's just a matter of learning the syntax of whatever language TWRP is coded in.
I just need to get off the ground, and running. If you guys/gals can help me get this started, I will get started, and see how I can help the shift community. We are short on developers, compared to the evo, and the evo 3d.
I'm not making any guarantees I can get anything done, but I won't know if I don't try.
Sounds like Eclipse IDE would be required to do the coding since an IDE is a tool such as Visual Basic for writing programs
*EDIT* I found the one I need. I read the ADT wiki a little more carefully, and it gave a recommendation...
Sweet 7lb 8oz baby jesus!! There are a ton of links for IDE tools. Which one do I need? I'm thinking the second one, but am looking for a second opinion...
http://www.eclipse.org/downloads/
That's the only thing I hate about developing...the setup. That takes forever, and is always filled with headaches. But once that's done, it's smooth sailing...
Here's what I know, hopefully it helps:
Apparently the reason it's not available for the Shift yet is that it doesn't support ext3 which the Shift uses (at least on Sense ROMs, CM7 may or may not mount as ext4.) I forget who it was but I guess someone on the Desire Z forums has modded it to work on the Desire Z which is basically the same phone as the Shift.
^ Shift Faced
I would guess motodev suite. Says its for android right on it...
<Blaze One>
Here is a link to someone who ported it over to the thunderbolt don't know if maybe someone there might be able to help you out on what you need to do.
http://rootzwiki.com/showthread.php...ery-Project-for-Thunderbolt-(8-2-1.0.2-rbox.1)
I have the Eclipse IDE up and running. I started a project, initially, I tried setting up an Android project, but it was looking for a missing target, and I didn't have a place to look for a target. I changed the project type to java, and I could open some files (.mk), but chouldn't open other files (.h). I still have some learning to do, so I appreciate the assistance that has been given so far.
I'll reach out to the developers of the Desire Z port, and the Thunderbolt port, and hopefully can get some more assistance.
*edit, nevermind... tried it and something was amiss
Sorry for posting a whole new thread for this. I poked around with the search, however I figure the developers that are doing stuff for the Infuse have a lot on their plates to be able to write out a tutorial for this individual phone forum.
But, I have absolutely 0 experience in making a rom for anything. I have flashed Infused on my Infuse. This is my first Android device and I really love the customizability over the iOS software (previous phone). I know Gingerbread is just around the corner but I would love to take my first few steps towards developing with a rom thats been out already. This way by the time I get a better grip of things I can maybe transfer these skills to the new version.
If anyone can be so kind, Ide appreciate it if the helpful devs could maybe point me to some links with the necessary files and programs/files that are needed to build a custom rom. As well as maybe some tutorial threads or videos.
Anybody feel free to shoot me some useful links if possible. Thanks so much in advance! Cant wait to contribute.
Mikeymike had something you're looking for in the Captivate forum. Can't find the thread on my phone but it was basically a how to thread. Good stuff if ur interested
This should be in Q&A. But yeah, MikeyMike has a tutorial somewhere.
In my opinion - start off small. Get familiar with making customizations to a ROM (theming, app replacement, etc) and then grow from there. Don't bite off more than you can chew.
tazbo28 said:
Sorry for posting a whole new thread for this. I poked around with the search, however I figure the developers that are doing stuff for the Infuse have a lot on their plates to be able to write out a tutorial for this individual phone forum.
But, I have absolutely 0 experience in making a rom for anything. I have flashed Infused on my Infuse. This is my first Android device and I really love the customizability over the iOS software (previous phone). I know Gingerbread is just around the corner but I would love to take my first few steps towards developing with a rom thats been out already. This way by the time I get a better grip of things I can maybe transfer these skills to the new version.
If anyone can be so kind, Ide appreciate it if the helpful devs could maybe point me to some links with the necessary files and programs/files that are needed to build a custom rom. As well as maybe some tutorial threads or videos.
Anybody feel free to shoot me some useful links if possible. Thanks so much in advance! Cant wait to contribute.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=928955
remember to post in the right section next time bud.
Thanks so much guys. Sorry I was totally debating on whether to post this there but I thought that maybe the devs dont frequent that section.
Please do move this thread if possible.
Sent from my SAMSUNG-SGH-I997 using XDA App
Ok so I have one last question.
Is it better/easier to build the rom using an ubuntu virtual machine, dual boot ubuntu, or a Mac OSX Lion virtual machine in Windows 7?
I have the option to run any one of these types of systems. Unfortunately I do not have a Mac available, so Im wondering if it is even possible to build the source using a Mac VM seeing as how there are certain types of partitions necessary.
Thanks in advance.
tazbo28 said:
Ok so I have one last question.
Is it better/easier to build the rom using an ubuntu virtual machine, dual boot ubuntu, or a Mac OSX Lion virtual machine in Windows 7?
I have the option to run any one of these types of systems. Unfortunately I do not have a Mac available, so Im wondering if it is even possible to build the source using a Mac VM seeing as how there are certain types of partitions necessary.
Thanks in advance.
Click to expand...
Click to collapse
I'd dual boot windows and Linux
Samsung infuse running gingerbread!
Dual-booting Linux is your best bet. VMs mean that if you eventually get as far as doing kernel or AOSP/Cyanogenmod compiles, you'll have less RAM available, and also sometimes accessing USB devices (such as to use ADB or Heimdall) is a bit of a pain with VMs.
Awesome thanks a bunch guys i just got my ubuntu dual boot set up but i don't seem to have a working Linus driver for my trendnet wifi adapter.
But i have downloaded the infuse 4g source and im about to start setting up the build components from the android website.
Sent from my SAMSUNG-SGH-I997 using XDA App
tazbo28 said:
Awesome thanks a bunch guys i just got my ubuntu dual boot set up but i don't seem to have a working Linus driver for my trendnet wifi adapter.
But i have downloaded the infuse 4g source and im about to start setting up the build components from the android website.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Well, there are two routes to building ROMs right now:
1) Start from a Samsung ROM - there is source to the kernel and a few small parts of the userland stack available, but most of it is lacking source. Most custom ROMs available here are created by taking the stock Samsung ROM and tweaking them - removing apps, adding others, or attempting to bring apps from other devices to ours.
2) Cyanogenmod 7 - this is a source build, HOWEVER - it is not complete, open-source reimplementations of some Samsung stuff is not complete, so some features (like Bluetooth) are broken
A lot of ROM devs (those that work on Samsung-derived ROMs) don't even have a copy of Samsung's source code release as it's not useful to them. (Exception are those of us who do kernel work.)
It's not something you can just jump into. To do it properly, you need patience and a willingness to spend a lot of time researching a lot of different things.
1) Some things are easier to do in Linux and other things are best done in Windows due to some tools only being available for Windows. It's best to have both.
2) Learn how to dump the system partition (using the dd command) and mount/extract the resulting factoryfs.rfs on your computer.
3) Learn the /system folder structure. Explorer the files in each folder and try to figure out what those files are.
4) Find and learn how to use a script or program that can deodex the apps and framework from the extracted system image.
5) Learn the structure of flashable zips and what all of the commands in updater-scripts do. Easiest way to do this is to download a bunch of roms and look at their folder structure and updater-scripts. Google commands in them that you do not understand.
6) Learn which apps can be removed and replaced without consequence. If you can't figure out exactly what a particular apk does, best to leave it alone.
7) Experiment with changing build prop entries to see what some of them do.
8) Learn how to manually decompile and compile the dex portion of apk and jar files. Use smali and baksmali for this. This lets you modify app and framework code, but the decompiled smali can be a bit confusing. Try to learn how to read it. Try this AOSP lockscreen mod tutorial.
9) Learn how to use a program that can decompile and compile entire apps, including resources. Apktool is a good program and APK Manager is a good front end for it. Look through all of the folders in the resources (res) directory of a decompiled app. Learn which images and types of files are in each folder. There are a ton of xml files that do various things in the resource folders. Open a bunch of them up and learn some basic xml structure so you can see what all that xml is doing. Most visual app mods are done via xml. Here's a slightly more advanced mod tutorial than the AOSP lockscreen was: http://forum.xda-developers.com/showthread.php?t=811532
10) Learn proper apk compression techniques. Though it works, just dropping images into apks via 7zip and calling it a day isn't really the right way to theme. The default Android Asset Packaging Tool (used by the Android SDK to package apps) does not compress certain file types, including images. This is because images, especially pngs, typically do not compress a great deal anyways and the added cpu time it takes to decompress those images at app launch makes the total app loading time longer than if the images were uncompressed, even if they are slightly larger. Also, compressing some file types, like oggs and system objects, too much can even cause the app to not be able to load them. See here for a handy script to repack apks with proper compression: http://forum.xda-developers.com/showthread.php?t=1123463
I could go on forever, but that should point you in the right direction. At least you know some of the basics you need to learn now even if I didn't tell you exactly how to do each thing. Remember, Google will be your best friend. Use it. A lot.
Man I really appreciate this so much gtg. Its exactly the kind of encouragement i was hoping for. I just get a general sense of excitement when thinking of all the different possibilities in both Rom and app development. And seeing as how im and artist first, its awesome to know that ill down be able to be a double threat in both designing the look of, and building the Rom myself.
I can't thank you enough for pointing me in the right direction. Maybe one day someone will put together a kitchen for the Infuse. Until then ill be happy to dive into all the nitty gritty.
Sent from my SAMSUNG-SGH-I997 using XDA App
First, yes, I checked what the auto title search pulled up when I made the title, and they have no relevance to what I'm doing.
Second, while it's still very much a work in progress, I have managed to devise a derivative of Ubuntu whose only usefulness is in building Android. I call it... ANDROIDER!!!
It's a live system, meaning that you will either need to burn it to a CD, then boot from said CD, or use something like YUMI to shove it onto a USB stick. Installation is impossible, unless you decide to remaster it and include Ubiquity. It's good for people who want to build Android, but don't want to hassle around with trying to install Ubuntu (or get rid of Unity if you install 11.04 desktop or later).
The only language available is English, because that is my native language and I was trying to get as small as possible. There's no accessibility featuring either, again for the size.
Booting still has issues to work out; it does try to ask what language you want with ISOLINUX, and as of yet I don't know how to stop it from asking. Verbosity is enabled (I like seeing what's happening, even if I don't have a clue about it) so you'll get to see how it doesn't necessarily like trying to configure the network (at least in a VM), and how buggy-ish the boot process still is at this point.
The bugs are why it's at version 0.01. The x86 version can be downloaded, but I'm still working on the x86_84 version.
On a sidenote, I have made a remix of a remix. It is called Squishbuntu and it is at the same Sourceforge project as ANDROIDER and it is squishy and pokable. Only x86 is available as of yet.
The project is at {sourceforge . net / projects / androider} if you think you're interested. I won't cry if you're not.
(Yikes this is a long-winded post.)
All,
As most of you are aware, I've been slowly chipping away at porting open source apps/libs to Windows RT when I can. In an effort to encourage more people to port things (and comply with licensing requirements), I've decided to put all the source code changes I've made on Codeplex.
You can find all the of the source code and binaries for the apps/libs I've worked on here:
https://windowsrtdev.codeplex.com/
Please read the notice on the front page. I hope some of you find this useful.
Keep in mind that I do this in my spare time so I haven't had a lot of time to keep things clean. So I apologize for the various quick hacks and lack of documentation. Speaking of documentation, I'm going to look at typing up some kernel driver porting notes. I've successfully ported a few drivers (not in the SVN repo yet) without requiring the WDK and I've worked out a several of the kinks in the process -- so I'll try to share that soon-ish.
As always, I'm happy to field questions and help others when I can but please do not contact me to port apps. I generally only work on the apps that _I find useful_ and I've already started or looked at many of those.
Cheers!
EDIT: I've converted the codeplex project to git and have also mirrored the effort on github ( https://github.com/bfosterjr/windowsrtdev )
Much appreciated! Your work has made the whole ecosystem better.
GoodDayToDie said:
Much appreciated! Your work has made the whole ecosystem better.
Click to expand...
Click to collapse
Likewise man! I wouldn't being doing this without the support and encouragement of people like you and the rest of the XDA community. Props to everyone who contributes and especially for those that have contributed to the jailbreak! (clrokr and netham45 in particular!)
Just a question, how do you deal with porting these libs? I'm familiar with compiling stuff with GCC but I assume those tools still aren't available for WinRT?
Actually, it looks like the VLC for Windows 8 / RT / WP8 project is or will be releasing updates to MinGW (which uses GCC on Windows) to add support for targeting Windows RT. However, at this time, all of the RT-ported desktop apps that I'm aware of were compiled using Visual Studio or other Microsoft development tools.
ausshir said:
Just a question, how do you deal with porting these libs? I'm familiar with compiling stuff with GCC but I assume those tools still aren't available for WinRT?
Click to expand...
Click to collapse
Nope, GCC building for NT_ARM isn't there yet - but its coming. I managed to port the binutils a while back, but gave up on GCC because I couldn't devote enough time to it.
Most of the smaller libs are pretty easy to convert from makefiles to VS2012 projects. Just takes patience. Best thing to do is to build it using GCC/Mingw for x86, capture all the logs, then recreate the build using VS. I've ran into a few libs that were much more difficult ..and I just gave up. Sometimes you can also find others that have shared VS2005/2008/2010 solutions/project files and then just upgrade those to VS2012.
I've got some more libs I need to commit to the SVN repo - WxWidgets (i think someone else also did this) and Qt4. They're both pretty huge and took quite a bit of fiddling. I'm only one lib away (libeffi) from having a full build of GTK+ build for Window RT as well.. which will have a domino effect on another set of open source apps I'd like to port.
Cheers!
waiting for the qt4 port.So I can try mumble(voice chat tool)http://www.mumble.com/
windowsrtc said:
waiting for the qt4 port.So I can try mumble(voice chat tool)http://www.mumble.com/
Click to expand...
Click to collapse
I'll see what I can do about getting it up soon. Its a beast of a code base
bfosterjr said:
I'll see what I can do about getting it up soon. Its a beast of a code base
Click to expand...
Click to collapse
I've got an older version of Mumble running (A 1.2.4 beta), but I lost my codebase and didn't get around to posting it.
If you're interested in getting it running the main things I had to do were disable all SSE optimizations (It assumes Win32 has SSE) and disable the hooking system.