Related
Hello developers,
I'm starting this thread because I'm interested in designing a development environment for the Samsung Galaxy Tab so that developers, like myself, can have an easy environment for modifying the Android OS. I'll be aiming this environment at all Android Devices but I want to start with the Samsung Galaxy Tab.
At the moment I don't have much of a structure for this project, nor much direction, so if anyone has any ideas for what tools etc I should include in this please let me know. If anyone wants to get on board with the project it would also be appreciated. Send me an email.
tool ideas:
- integrating the GCC and Javac compilers into the environment.
- integrating a way to generate make files and to build from these files.
- GUI for editing files from the kernel and application framework.
- easy to use way of setting up branches for projects with the Repo and Git included in the Android Source Code.
Count me in. I am getting a Tab tonight and I plan to develop for it. Currently, I have got the froyo source on my machine and want to integrate the open source code that Samsung released for this device.
Has anyone successfully built a custom ROM using the Samsung source code? Any help on this will be appreciated.
Awesome!
I've got Froyo working on the Tab, which I built from the source code from the android open source project website but it's just a generic build from the straight source, nothing special. not with the samsung code though. do you have any links for it?
I've put a small amount of stuff into the Dev Environment, most just shell files etc to make installing everything easier. One click sort of thing.
My first task though is going to be to try and fix the failure that is the Samsung display driver. Most noticeable are the 4 by 1 widgets that don't stretch across the whole screen.
After that I'm going to start work on a GUI for the environment and the iOS Emulator.
thoughts?
Whats wrong with Android SDK and Eclipse?
It's not the most straight forward thing. I'm looking to make something that includes its own libraries too. It's aimed at beginning developers mostly, so you can literally download one file which includes everything you'll need then start editting and then one click to compile and have it all work. Simplicity
I'm also interested in this... The SGT is my first android device, and my company will want android apps for internal and external uses... and a one click dev environment would be a most welcome option!
DevShroom said:
I've got Froyo working on the Tab, which I built from the source code from the android open source project website but it's just a generic build from the straight source, nothing special. not with the samsung code though. do you have any links for it?
Click to expand...
Click to collapse
Straight up AOSP? Could you have a crack at CM?
Anything you need, including testers, I'm in.
I have programmed some programs in android. If you need my help, i will be glad to help,
Sent from my GT-P1000 using Tapatalk
i'm currently setting up a new galaxy Tab ubuntu 10.10 VM but I always fail at installing java5-jdk, but when im ready i'm going to have a look at the CM and AOSP source and i !try! to port CM to the tab!
I am working on a custom rom , if you need any help do not hesitate
yann06 said:
I am working on a custom rom , if you need any help do not hesitate
Click to expand...
Click to collapse
are u building from source or are you modifing a stock rom?
DevShroom said:
Hello developers,
I'm starting this thread because I'm interested in designing a development environment for the Samsung Galaxy Tab so that developers, like myself, can have an easy environment for modifying the Android OS. I'll be aiming this environment at all Android Devices but I want to start with the Samsung Galaxy Tab.
At the moment I don't have much of a structure for this project, nor much direction, so if anyone has any ideas for what tools etc I should include in this please let me know. If anyone wants to get on board with the project it would also be appreciated. Send me an email.
tool ideas:
- integrating the GCC and Javac compilers into the environment.
- integrating a way to generate make files and to build from these files.
- GUI for editing files from the kernel and application framework.
- easy to use way of setting up branches for projects with the Repo and Git included in the Android Source Code.
Click to expand...
Click to collapse
I'll be interested in getting involved in a community driven project for the SGT. I'm a unix admin with lots of experience in the OS and system development field. Interested in what ideas you have on this.
Try using openjdk. It works for me.
Sent from my GT-P1000 using Tapatalk
Thanks everyone for the positive feedback on all this! it'll be good to have as many people on board as possible.
if you have troubles downloading the sun-java5-jdk there is a good tutorial on it on this site, it doesnt come as part of the repository by default so until you add it in sudo apt-get install sun-java5-jdk will not work.
atm i am only working with AOSP not CM, i am trying to set this dev environment up for a nice simple build and then i'll start working on more complex builds so we can start developing custom roms.
@paulshields - do you know much about linux/android drivers? i wanna fix the widget sizing problem on SGT but my driver knowledge is limited
[This is not the place to say "this is awesome" or "thanks!"]
[DEVS ONLY]
I want to start this thread to keep up the progress on the port.
the bad news is that the SDK is incomplete for now, so (like other devices)
we will have to write our own code for the OS, the nook community
has done a wonderful job writing their own libraries and stuffs, so we will have to do the same.
Instead of pursuing different goals, let's focus on one thing at a time.
since GSM and CDMA versions are already out, it seems we suffer the same bugs, so for now let's unite strength and knowledge to overcome these.
I propose that the first goal to fix is the SurfaceFlinger, so we could at least see the apps, the buttons and the notifications.
it is currently throwing this:
04-06 22:01:35.495: ERROR/Surface(2960): dequeueBuffer failed (Out of memory)
this could lead us that it might coudln't start because of some malloc malfunction or something.
also that pvrsrvinit bugs me a lot.
update:
8/APR/2011
since DiP7 could fix SurfaceFlinger and other things using a different build from the GSM kernel, we have to dig deeper
======================================
CURRENT GOAL
Rebuild Kernel
======================================
Current approaches:
*none
Post any finding, guessing or anything, and please, please don't be afraid to ask anything you have a doubt, as a Dev you should not know everything, so we can help us each other
------------------------------------------
Google Easter egg:
while searching some info about the android.mk file , I put it on the chrome bar to search for that term, but instead I went to
http://android.mk
an easter egg web page from google lol
******TOOLS*********
How to send text and Keystrokes via ADB
http://bradchow.blogspot.com/2011/02/send-intent-and-key-event-by-adb.html
use DroidExplorer to easily access your device from your computer and makes changes from it
http://de.codeplex.com/
The Android Boot Process
http://www.androidenea.com/2009/06/android-boot-process-from-power-on.html
---Kernel Tools----
CPU Datasheet
http://forum.xda-developers.com/showthread.php?t=745877
Samsung GIT
http://android.git.kernel.org/?p=kernel/samsung.git;a=summary
PowerVR SDK
http://www.imgtec.com/powervr/insider/powervr-sdk.asp
Source code of samsung firmwares(keep and eye on this)
http://opensource.samsung.com/
Asus pad honeycomb Kernel Source
http://forum.xda-developers.com/showthread.php?t=1026528
ellokomen said:
======================================
CURRENT GOAL
Find why SurfaceFlinger is not working
======================================
Click to expand...
Click to collapse
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)
updated approaches and new tools have been added
spacemoose1 said:
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)
Click to expand...
Click to collapse
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb
lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb
Click to expand...
Click to collapse
you mean that you made a port of a Linux Distro into the tab?
ellokomen said:
you mean that you made a port of a Linux Distro into the tab?
Click to expand...
Click to collapse
yes click here for the thread on the port of ubuntu
Current kernel source
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
here it is, bear in mind that this is for CDMA devices
Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??
daml said:
Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??
Click to expand...
Click to collapse
yeah but we need a place for the other devs to share their milestones, here is a place for technical discussion amongst us, to share the knowledge etc...
the other threads are flooded from non devs messages, so it´s kind of difficult to read 14 pages of information when the 80% is people complaining not making it boot
lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
Click to expand...
Click to collapse
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.
noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
D'oh! Nobody told me, LOL... I'll get another copy up.
spacemoose1 said:
D'oh! Nobody told me, LOL... I'll get another copy up.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!
Flokey said:
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!
Click to expand...
Click to collapse
Digging through it now.
spacemoose1 said:
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.
Click to expand...
Click to collapse
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb
lilstevie said:
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb
Click to expand...
Click to collapse
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.
Goal and tools updated*
spacemoose1 said:
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.
Click to expand...
Click to collapse
You don't know what a kernel panic is do you?
lilstevie said:
You don't know what a kernel panic is do you?
Click to expand...
Click to collapse
I thought that linux throws a dump log when it makes a kernel panic specifying the memory address and the cause of crash
compiling AOSPA 3.+ for HTC ONE V (primou)
hello everyone as we all know now all developers are busy with there own rom and many of them left this HOV thread.
We don't have many developers to build a new rom for us, that's why we people are having less number of rom in HOV's thread.
So i have decided to start a new project in which we will c compile the AOSP3.+ rom from the source, but the problem is I am not a developer or programmer or any kind of genius.
so what i am going to do is i need a team in which we all can work together and try our best to port this rom from source successfully
anyone who is interested in this can reply to this thread, I'll be glad to having as much as people possible
If i get a team then, we all gonna work according to this guide -> http://forum.xda-developers.com/showthread.php?t=1863547
4.2.2 or 4.3?
well 3+ is 4.2.2
Seraz007 said:
well 3+ is 4.2.2
Click to expand...
Click to collapse
The lateset for many devices is running on 4.3.x, but I'm assuming it's 4.2.2 since the branch for 4.3.x is jb43.
MameTozhio said:
The lateset for many devices is running on 4.3.x, but I'm assuming it's 4.2.2 since the branch for 4.3.x is jb43.
Click to expand...
Click to collapse
3+ and 3.40 are two different versions
anything above 3.40( i think that is the version) is 4.3
Seraz007 said:
3+ and 3.40 are two different versions
anything above 3.40( i think that is the version) is 4.3
Click to expand...
Click to collapse
PA 3.60 for hTC Desire is 4.2.2
Anyway,back on topic.
so you joining @MameTozhio
Sure, I also found a device tree on github.
MameTozhio said:
Sure, I also found a device tree on github.
Click to expand...
Click to collapse
awesome! now the thing is we need atleast 2-3 people so that we can start our project and i hope you have Ubuntu 12.04 (Precise Pangolin) 64-bit in pc
gulsher said:
awesome! now the thing is we need atleast 2-3 people so that we can start our project and i hope you have Ubuntu 12.04 (Precise Pangolin) 64-bit in pc
Click to expand...
Click to collapse
Linux Deepin 12.12.1 (Raring based) 64-bit
Java 6 from Webupd8 ppa.
:good: I'm interested
i m also very new to Android rom development
but will try my best (100%) to support the project
i don't have ubuntu but i can get ready in a VM..do we need x64..x32 wont suffice
blade22 said:
:good: I'm interested
i m also very new to Android rom development
but will try my best (100%) to support the project
i don't have ubuntu but i can get ready in a VM..do we need x64..x32 wont suffice
Click to expand...
Click to collapse
It's harder with 32-bit, I believe. But I know you can build on 32-bit.
blade22 said:
:good: I'm interested
i m also very new to Android rom development
but will try my best (100%) to support the project
i don't have ubuntu but i can get ready in a VM..do we need x64..x32 wont suffice
Click to expand...
Click to collapse
great but i suggest that you make space for ubuntu it would be a better option, if you can or else vm is fine
Vm is fine if you have a LOT of ram, because otherwise the compiling process will take days lol..
If you make a partition, make it at least 70gb, some sources are even 50gbs..
mr_nooby said:
Vm is fine if you have a LOT of ram, because otherwise the compiling process will take days lol..
If you make a partition, make it at least 70gb, some sources are even 50gbs..
Click to expand...
Click to collapse
50 gbs wth in it
I really want to join , but my pc are windows 32bit and 2gb ram D:
sent from my Sensation XE
Mine is 4gb ram dual core 2.4ghz, and it goes pretty well. But school is starting soon so I have no more time to join the team..
Oh.. school...
I start next week.. I can't join unless I get free time..
danishaznita said:
50 gbs wth in it
I really want to join , but my pc are windows 32bit and 2gb ram D:
you can join even my pc config also is same 32bit with 2gb ram , if it will cause problem we will other members of the team for compiling ]
Click to expand...
Click to collapse
@MameTozhio even I am also having college infact the exam are coming soon, but we could do work slowly accordingly , we don't need to do anything in hurry so @mr_nooby you can also join
gulsher said:
@MameTozhio even I am also having college infact the exam are coming soon, but we could do work slowly accordingly , we don't need to do anything in hurry so @mr_nooby you can also join
Click to expand...
Click to collapse
Okay but our timezone.........
Hmm
sent from my Sensation XE
mr_nooby said:
Vm is fine if you have a LOT of ram, because otherwise the compiling process will take days lol..
If you make a partition, make it at least 70gb, some sources are even 50gbs..
Click to expand...
Click to collapse
70gb need to free some space then
is there a specific version of Linux OS needed..as suggested by OP ubuntu..can't we use redhat,linspire etc etc
Hi guys- I have seen a website or page on how to build your own rom.
how difficult is it on 1 to 10?- 10 being very difficult.
what tools do I need?
many thanks
Well it depends how you create the rom and what type of ROM you are creating.
If you plan to simply take an already made rom.zip, make a few little modifications, and zip it back up...it obviously isn't very hard, and likewise its not very satisfying.
If you want to compile a rom from source, then its a bit harder than the process above. To be more specific let's first talk about android versions that are officially supported by the desire: froyo, and gingerbread. Compiling roms based on those honestly isn't that hard. You just need some basic Linux/terminal knowledge. The device and kernel source is actually meant to work by default so you don't need to make any further adjustments. It as simple as opening terminal, downloading the source, and running a build command. Give it an hour (more or less depending on how food your PC is) and you should have a freshly made ROM that you built from source. Yay...some satisfaction.
The hardest thing in my opinion (I've tried all three of these) is compiling a rom based on an android version that isn't officially supported by the desire. (Ice cream sandwich or jellybean). With roms based on these android versions you will have to scour to internet for a working device, vendor and kernel tree. (Hint, hint: WoH and evervolv/nikez). Even once you get the right device tree it probably won't work. You will have to make further adjustments, and even then I'm sure you will be bombarded with build errors. But eventually once you get it to compile successfully....most satisfying thing ever
So yea thats my answer. Keep in mind that I've tried (and eventually succeeded) with all three of the above, and that I've got quite limited programming knowledge. (2 high school comp sci courses, where I learned some java.)
Sent using xda-developers app
building your own rom
Chromium_ said:
Well it depends how you create the rom and what type of ROM you are creating.
If you plan to simply take an already made rom.zip, make a few little modifications, and zip it back up...it obviously isn't very hard, and likewise its not very satisfying.
If you want to compile a rom from source, then its a bit harder than the process above. To be more specific let's first talk about android versions that are officially supported by the desire: froyo, and gingerbread. Compiling roms based on those honestly isn't that hard. You just need some basic Linux/terminal knowledge. The device and kernel source is actually meant to work by default so you don't need to make any further adjustments. It as simple as opening terminal, downloading the source, and running a build command. Give it an hour (more or less depending on how food your PC is) and you should have a freshly made ROM that you built from source. Yay...some satisfaction.
The hardest thing in my opinion (I've tried all three of these) is compiling a rom based on an android version that isn't officially supported by the desire. (Ice cream sandwich or jellybean). With roms based on these android versions you will have to scour to internet for a working device, vendor and kernel tree. (Hint, hint: WoH and evervolv/nikez). Even once you get the right device tree it probably won't work. You will have to make further adjustments, and even then I'm sure you will be bombarded with build errors. But eventually once you get it to compile successfully....most satisfying thing ever
So yea thats my answer. Keep in mind that I've tried (and eventually succeeded) with all three of the above, and that I've got quite limited programming knowledge. (2 high school comp sci courses, where I learned some java.)
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks for that-
Sound very complicated
I am a webdesigner but have no knowledge of developing.
Wanted to try and build a really good rom to make the desire a really good phone for photography.
I have on my phone your rom and RSK supersense 3.5 rom running - coz I like the camera
and I would like to make a rom to turn it into a photography rom for my phone.
any advice??
creating your own rom
Chromium_ said:
Well it depends how you create the rom and what type of ROM you are creating.
If you plan to simply take an already made rom.zip, make a few little modifications, and zip it back up...it obviously isn't very hard, and likewise its not very satisfying.
If you want to compile a rom from source, then its a bit harder than the process above. To be more specific let's first talk about android versions that are officially supported by the desire: froyo, and gingerbread. Compiling roms based on those honestly isn't that hard. You just need some basic Linux/terminal knowledge. The device and kernel source is actually meant to work by default so you don't need to make any further adjustments. It as simple as opening terminal, downloading the source, and running a build command. Give it an hour (more or less depending on how food your PC is) and you should have a freshly made ROM that you built from source. Yay...some satisfaction.
The hardest thing in my opinion (I've tried all three of these) is compiling a rom based on an android version that isn't officially supported by the desire. (Ice cream sandwich or jellybean). With roms based on these android versions you will have to scour to internet for a working device, vendor and kernel tree. (Hint, hint: WoH and evervolv/nikez). Even once you get the right device tree it probably won't work. You will have to make further adjustments, and even then I'm sure you will be bombarded with build errors. But eventually once you get it to compile successfully....most satisfying thing ever
So yea thats my answer. Keep in mind that I've tried (and eventually succeeded) with all three of the above, and that I've got quite limited programming knowledge. (2 high school comp sci courses, where I learned some java.)
Sent using xda-developers app
Click to expand...
Click to collapse
htc_desire_luke said:
Thanks for that-
Sound very complicated
I am a webdesigner but have no knowledge of developing.
Wanted to try and build a really good rom to make the desire a really good phone for photography.
I have on my phone your rom and RSK supersense 3.5 rom running - coz I like the camera
and I would like to make a rom to turn it into a photography rom for my phone.
any advice??
Click to expand...
Click to collapse
any software needed ??
htc_desire_luke said:
any software needed ??
Click to expand...
Click to collapse
here is a summary of what you need and main steps, from hd2 forum.. next time do a search before post.
Obviously you have to use a desire device tree.
http://forum.xda-developers.com/showthread.php?t=2488670
There is an entire section dedicated to this subject, found in
creating your own rom
paolo-red1 said:
here is a summary of what you need and main steps, from hd2 forum.. next time do a search before post.
Obviously you have to use a desire device tree.
http://forum.xda-developers.com/showthread.php?t=2488670
Click to expand...
Click to collapse
sound very difficult-
my laptop is running linux and i think 64bits- I am running opensuse 12.1 KDE
but thats all i know
will have to do some more reading on this, I dont think I will be able to just pick it up and go.....
You are kiddin' me
Enviado desde mi HTC Desire
creating your own rom
Jack4L_ said:
You are kiddin' me
Enviado desde mi HTC Desire
Click to expand...
Click to collapse
what do you mean Im kiddin you?
http://symphonyos.com/screenshots/
What do you think? I believe it'd be a very proper fit if we could get it going, four menu corners, sort of an android'ish app drawer, lightweight and I think it's still Ubuntu based...
Hello
I run the SymphonyOS project. We are based on Ubuntu and our desktop itself is written in interpreted languages like perl and php combined with packages like fvwm and tint2 that are available in the official repos so it is cross platform. While we havent done any work on touchscreen compatibility i do have the desktop running under ubuntu arm on an mk802. There wouild likely be some issues with some parts of the interface with touch but if you want to give it a try, get in touch and i can provide some details on how to copy the desktops cvomponents iknto a vasnilla ubuntu-arm system.
I think I'll add a poll to see how many are interested in seeing this on our Note 2...
I'd love to see it ported over, can someone link me to how to do linux on our devices, I seen it before but forgot what it was and what exact search phrase to use. Would it be SELinux and porting or isnt there an app for that too? I'm clueless! LoL
Okay now I found the app... Can't create polls in a already existing thread! errr
http://forum.xda-developers.com/showthread.php?t=1585009
Q&A Thread for that---^ http://forum.xda-developers.com/showthread.php?p=38340817
And this thread over at SysmphonyOS forum for easier communication with @ryanpq
I see @gregsarg is or would also be interested in this according to all his thanks in this thread. Speak up man!!
n1nj4Lo said:
Okay now I found the app... Can't create polls in a already existing thread! errr
http://forum.xda-developers.com/showthread.php?t=1585009
Q&A Thread for that---^ http://forum.xda-developers.com/showthread.php?p=38340817
And this thread over at SysmphonyOS forum for easier communication with @ryanpq
I see @gregsarg is or would also be interested in this according to all his thanks in this thread. Speak up man!!
Click to expand...
Click to collapse
This can be used to mount any Linux chroot
It can build a few also .
I will see what i can do to add this to the supported install distros
http://forum.xda-developers.com/showthread.php?t=2627255
userdelroot said:
This can be used to mount any Linux chroot
It can build a few also .
I will see what i can do to add this to the supported install distros
http://forum.xda-developers.com/showthread.php?t=2627255
Click to expand...
Click to collapse
Cool sounds good... Thanks
___
SymphonyOS Thread: http://symphonyos.com/forums/topic/symphonyos-on-android/