I know that there are trillions of threads out of there regarding the issue, and maybe, I'll even get some people telling me off for making a new thread about this, but does anyone have any news on any NDS emulator?
I think our Galaxy S II is strong enough to emulate the NDS.. The NDS has the following specs: (According to Wikipedia.org)
Resolution of 256 × 192 pixels
CPUs: Two ARM processors
32 bit ARM946E-S main CPU; 67 MHz clock speed. Processes gameplay mechanisms and video rendering.
32 bit ARM7TDMI coprocessor; 33 MHz clock speed. Processes sound output, Wi-Fi support and takes on second-processor duties in Game Boy Advance mode.
RAM: 4 MB of mobile RAM, expandable via the Game Boy Advance slot (expansion only officially used by the Opera web browser).
OR, if anyone else is ready to continue the development, it would be really great. I know I'm being selfish here as a newbie, but I think it would be really worth the effort, as there would be many people like me dying to emulate NDS on our phones..
True. But seems to be a pain to emulate. Let's just wait, stare, and see.
Envoyé depuis mon GT-I9100 avec Tapatalk
Yeah, I know how much effort it takes to emulate stuff, but still this project could be worth it. Believe it or not, we've all been waiting for a long time for this emulator.
The last version we saw for the nds4droid was v1.3, and no updates have been released thereafter, AFAIK... So, does any know about any version later than 1.3? *resumes hoping to play Pokemon Pearl on his phone someday*
i wish i knew how to code..i badly want to this fully functional!!
So do many other people.. Is there any way we could support the original developer with his project? I mean, if the dev wants to make this app usable, there will be many people who will be ready to donate to the dev for his hard work. Any possibility we could contact them?
Erm, I don't think I'll let this thread die.. Will someone be willing to help to keep this thread alive?
I just wanted to say that I have installed this on my GS2 running CM9 and it runs smooth as gameboid!
Only thing that needs fixing... no audio... if surely someone could work out how to enable audio, that is all this needs to run on modern day droids!
hellaflush said:
I just wanted to say that I have installed this on my GS2 running CM9 and it runs smooth as gameboid!
Only thing that needs fixing... no audio... if surely someone could work out how to enable audio, that is all this needs to run on modern day droids!
Click to expand...
Click to collapse
Really? I'll have to try it out when I get home! And I'll help keep this thread alive ;-)
Sent from my GT-I9100 using xda premium
hellaflush said:
I just wanted to say that I have installed this on my GS2 running CM9 and it runs smooth as gameboid!
Only thing that needs fixing... no audio... if surely someone could work out how to enable audio, that is all this needs to run on modern day droids!
Click to expand...
Click to collapse
Not sure what game you're playing but any game I try is laggy as hell, overclocked to 1.4ghz aswel...
Sent from my GT-I9100 using xda premium
There are two emulators that were being developed but ceased; tiger nds and nds4droid.
The galaxy s2 is powerful enough to handle a nds emulator. It's not the phone that is running the games slow, and without sound, but the coding of the apks.
Jo_725 said:
There are two emulators that were being developed but ceased; tiger nds and nds4droid.
The galaxy s2 is powerful enough to handle a nds emulator. It's not the phone that is running the games slow, and without sound, but the coding of the apks.
Click to expand...
Click to collapse
I wish someone would keep up development
Sent from my GT-I9100 using xda premium
If i remember correctly the main reason NDS emulation on PCs took a while was because the coding was wonky, for example even the current NDS emulator on computers is poorly optimized
our SII's have more then enough juice to run it, but again i think adapting the code is the problem, guess all we can do is wait *waves surrender flag*
I wanted to put a list together to compare results of build times (PLEASE, no fan boys here!). The more info you can list, the better visibility is into the amount of time it takes. I'll start with my machine, what I built and how long it took.
The important parts are processor, ram, operating system, what android os you built, any tweaks you used, and if you have a ssd hdd. And, of course total time! I will list mine in a format for easy reading:
-Sony vaio vgn-nr110
-2gb of ram at 533mhz (upgraded )
-Intel pentium dual core t2310 processor
-running ubuntu at the time. I want to say it was version 10.04(been a while)
-no ssd. Regular laptop hdd
-built cm7 for Optimus s
-used the -j4 flag on make
=approx 4-6 hours (was cleaning while it ran because I knew it would take some time)
Mine was a full build/compile from scratch. Please state whether yours is or isn't, and if you used any special tweaks, etc. Do not include sync time in the total time as that is dependent on the Internet connection and not the machine itself (most people won't, but wanted to have it in here just in case)
My purpose behind this is to get a good idea of what type of system specs perform best with building android roms. If there are any tweaks or tricks that anyone would like to contribute, that would be great too! Please try to stick to the format that I have listed for my machine to make it easier for everyone to read.
As a treat: I will have more results for everyone in a week or two on a new machine.
Amd X2, 2 gb ram, 1tb hdd... Build time 4-5 hours, for cm9 for sprint sgs2, and 3-4 hours cm7
Sent from my SPH-D710 using xda premium
Asus i5 normal HDD 8GB ram
cm9= 65 - 75 min _ simple mka bacon no -j
Cna = 75 - 90 min _ simple mka squish no -j
Aokp = 65-75 min _ simple mka bacon no -j
I try to not have anything else open not even file browser or chrome (usually it will add twenty to forty extra minutes if it's on) although these are my best estimate numbers, time results vary. I use cache and restart Ubuntu before building to let it take the lead over everything else. Building while the PC has been active for over a day seems to always take longer. Aokp has been the record holder for me. Slightly quicker than cm9.
Tcp!? Where you been hiding buddy?
We got you a cake for your birthday but it rusted. We made it out of old Android parts and waited to yell surprise but you never showed. Is you okay? Brb I gotta tweet that I found you on xda! Lol B) good to see you Partna...
Sent from my SPH-D710 using Tapatalk 2
Phenom II X6 2.7GHz, 4 GB RAM, dual 640GB Western Digital Caviar Black in RAID 0.
CM7 for LS670: 18 minutes, 38 seconds. Compile options: make -j12 bacon
Cannibal Open Touch recovery for LS670: 59 seconds. Compile options: make -j12 recoveryimage
HydroKernel for LS670/VM670: 1 minute, 13 seconds. Compile options: make -j12
CM10 for Nexus 7: 48 minutes. Compile options: make -j12 otapackage
Yes it is very important to not have any other programs open (I've even crashed my machine trying to do stuff while compiling with -j12), they will take up more RAM and more CPU time.
Thanks for the responses so far. I hope this can become a list that more people can use as a reference to tweaking their machine for building purposes. I haven't seen any sort of list around and when I do read about the amount of time it takes, I usually see an answer like "it takes however long it takes" which leads to no progress. And at the very least I believe it's cool to see what other's results are.
Sent from my Super Galaxy'd SPH-D710
- Acer 5315
- Intel Celeron M 1,86 Ghz processor
- 1GB Ram
- 80GB HDD
on Ubuntu 10.04 it takes half an hour to compile a kernel with make command without any flag.
I will compile CM7 or ICS when i have free time just for fun to see the amount of time it takes, i guess it will take 22-24 hours
I am planning to change my laptop, this thread will be a good reference for me.
Core i3 2120 3.3ghz
Gigabyte Z68 mobo
8gb 1600 ram
Ubuntu 12 installed on a 100gb partition with 8gb swap on a Seagate Green (5900rpm) 1Tb DRIVE takes about 90 minutes to build CM9 for my Sensation.
I ordered a 120Gb OCZ Agility 3 SSD from tiger for $85 hopefully that will cut the time down significantly.
Sent from my Sensation using xda premium
AMD 3GHZ FX8120 Bulldozer Black Edition ;
16GB (1600) DDR3 ;
7200rpm 1TB HDD ;
Not Sure about the Motherboard without checking.
Linux Mint 13 ( 64 Bit )
EDIT: New build times.
aosp android-4.1.1_r4 ; removed previous out directory
full_panda-eng ; make -j12 49m6.429s
reboot
full_stingray-eng ; make -j16 32m47.270s
It came in around 38 minutes on a intial build of ICS time using make -j16.
Lately It's a little longer and I've been unable to get some fresh times because I don't have great cooling and it kept overheating and resetting because of hot whether.
It can be clocked to 5GHz with proper cooling and an SSD would bring the time down, I think, but given some reported times I am more than happy with that as it means I don't have to think twice about (re)building a rom.
In testing however I think this processor did fairly poor especially when up against similar Intel and looking at the couple of Intel times here I'd say they're the ones to go with.
Notes:
I always restart before building, I found it vital to restart after a repo sync as there seems to be a memoy leak in either repo or python, I don't know whether that has been fixed yet.
Incidentally I did Start a build on an Ubuntu VM which had 3 CPU Cores assigned and 4GB Ram, It was still going after 2 Days!
trevd said:
AMD 3GHZ FX8120 Bulldozer Black Edition ;
16GB (1600) DDR3 ;
7200rpm 1TB HDD ;
Not Sure about the Motherboard without checking.
Linux Mint 13 ( 64 Bit )
Incidentally I did Start a build on an Ubuntu VM which had 3 CPU Cores assigned and 4GB Ram, It was still going after 2 Days!
Click to expand...
Click to collapse
that doesnt seem right! lol.. really? not 2 whole days?
justlovejoy said:
that doesnt seem right! lol.. really? not 2 whole days?
Click to expand...
Click to collapse
Yep, You read it right lol. I went out for the weekend and when I came back it was still going I forget to add it was a dynamically sizing virtual disk which probably will account for it.
trevd said:
Yep, You read it right lol. I went out for the weekend and when I came back it was still going I forget to add it was a dynamically sizing virtual disk which probably will account for it.
Click to expand...
Click to collapse
That was with virtual machine right? Have u tried using ccache on an install of ubuntu yet?
Sent from my Super Galaxy'd SPH-D710
basketthis said:
That was with virtual machine right? Have u tried using ccache on an install of ubuntu yet?
Sent from my Super Galaxy'd SPH-D710
Click to expand...
Click to collapse
Yeah, like I put the Ubuntu VM ( Virtual Machine ). That's the day I learned to build on proper hardware, I tried the VM because I was on a later Ubuntu at the time and had run into a couple of issues so I wanted to follow google's aosp instructions to the letter and rule any versioning issues out..... schrooting is a much eaiser way of using a previous disto versions binaries, this is a great article on how build android using schroot. Good If you've ever get an urge for a cupcake or a donut one day
I do use ccache, but thanks for asking. Set in the bash profile so I never forget . Not looked into whether it should be cleared down at any point, I am on a 500GB partition though so I've not hit any limits yet.
trevd said:
Yeah, like I put the Ubuntu VM ( Virtual Machine ). That's the day I learned to build on proper hardware, I tried the VM because I was on a later Ubuntu at the time and had run into a couple of issues so I wanted to follow google's aosp instructions to the letter and rule any versioning issues out..... schrooting is a much eaiser way of using a previous disto versions binaries, this is a great article on how build android using schroot. Good If you've ever get an urge for a cupcake or a donut one day
I do use ccache, but thanks for asking. Set in the bash profile so I never forget . Not looked into whether it should be cleared down at any point, I am on a 500GB partition though so I've not hit any limits yet.
Click to expand...
Click to collapse
Setting up a box with the same processor. I expected to see better than 30 min builds for ICS. I will see what I come up with.
I am guessing that you were on windows and that's why you chose to go with virtual machine?
I have also read that different file systems read i/o faster/slower than others. Reference
Sent from my Super Galaxy'd SPH-D710
basketthis said:
Setting up a box with the same processor. I expected to see better than 30 min builds for ICS. I will see what I come up with.
I am guessing that you were on windows and that's why you chose to go with virtual machine?
I have also read that different file systems read i/o faster/slower than others. Reference
Sent from my Super Galaxy'd SPH-D710
Click to expand...
Click to collapse
Maybe on JellyBean, On ICS i'm not so sure about, From my very casual observations JB seems to be use a lot less ram in it build process, ICS always just touched swap from a start of about 15GB .
Like I mentioned earlier, from the reviews I read the processor is out perfomed by similar intels and a bit a flop apparently. ( I reads these reviews long after I had bought the processor ). Although I'm happy enough with it. Also I've only got a generic kernel installed so there's probably some AMD optimization to be had there if I really wanted to get into it.
I wasn't on windows at the time. I was just young, foolish It was when I was just getting started with building the sources and really didn't know any better....I still am foolish, just not as young.
Right, I'll be back in ( just over ) 30 mins :laugh: I've got a full_grouper-eng to compile.
Thanks for the link, Phoronix are a really useful resource, It's one I stumble upon now and again but always forget the name of it when I want to remember.
Using virtual box on my laptop at the time I was solo boot on windows, longest cm9 ever took was about 3 hours with dynamically resizing and was using two cores with less than 2 GB ram. Still, many things differ, I shut the whole thing down so only virtual box was running. I noticed lag when I would go web browsing so figured, why waste ram and disk space.
Sent from my SPH-D710 using Tapatalk 2
trevd said:
Maybe on JellyBean, On ICS i'm not so sure about, From my very casual observations JB seems to be use a lot less ram in it build process, ICS always just touched swap from a start of about 15GB .
Like I mentioned earlier, from the reviews I read the processor is out perfomed by similar intels and a bit a flop apparently. ( I reads these reviews long after I had bought the processor ). Although I'm happy enough with it. Also I've only got a generic kernel installed so there's probably some AMD optimization to be had there if I really wanted to get into it.
I wasn't on windows at the time. I was just young, foolish It was when I was just getting started with building the sources and really didn't know any better....I still am foolish, just not as young.
Right, I'll be back in ( just over ) 30 mins :laugh: I've got a full_grouper-eng to compile.
Thanks for the link, Phoronix are a really useful resource, It's one I stumble upon now and again but always forget the name of it when I want to remember.
Click to expand...
Click to collapse
Build a kernel
There are fx flags and optimizations....
Edit: If on ubuntu/Linux, you may want to check that your os is recognizing more than 3gb of ram also. I've been reading that anything newer than ubuntu 10.10 or Linux kernel 2.3.something are having issues with recognizing more than approx 3gb of ram. Also, there are issues with 10.04 and optimizations of ssd drives.
Also, I think it was 10.04 that is recognized as the better ubuntu version for building android. It is possible to use a newer (3.0+) kernel and back port it to the older ubuntu. This seems to give the best results...
Putting this info here for reference and to have it in a central location.
Lol, I've read many reviews. I am trying my hardest to keep any opinions out of here and keep it geared toward facts. It appears that Linux is better at multi-threading and we should expect to see gains when building a custom kernel (non-generic) and other things to come in the future. Whereas windows will need much more tweaking. Although I don't know why you would use windows to build android anyway....
Sent from my Super Galaxy'd SPH-D710
Takes about 20m on my pc, i7-2600K, 12GB, 7.2K HDD
real 20m14.526s
user 74m51.913s
sys 4m53.774s
^full-eng from clobber, same for other targets.
cdesai said:
Takes about 20m on my pc, i7-2600K, 12GB, 7.2K HDD
real 20m14.526s
user 74m51.913s
sys 4m53.774s
^full-eng from clobber, same for other targets.
Click to expand...
Click to collapse
I really must be missing a trick here and clearly haven't spent enough time on my considering the finer details of my hardware / kernel configuration.
basketthis said:
Build a kernel
There are fx flags and optimizations....
.....
Edit: If on ubuntu/Linux, you may want to check that your os is recognizing more than 3gb of ram also. I've been reading that anything newer than ubuntu 10.10 or Linux kernel 2.3.something are having issues with recognizing more than approx 3gb of ram
...
Lol, I've read many reviews. I am trying my hardest to keep any opinions out of here and keep it geared toward facts. It appears that Linux is better at multi-threading and we should expect to see gains when building a custom kernel (non-generic)
Sent from my Super Galaxy'd SPH-D710
Click to expand...
Click to collapse
Current Config is Linux Mint 13 x64 which is based off Ubuntu 12.04 with 3.2.0.26 kernel the Ram is Present and correct, However I have come across the 3GB Ram Limit previously so I am familiar with it. I think I must have been I had an 11.04 32bit on my machine.
PAE Extensions is the feature which needs enabling to get your full quota of ram on 32bit. Here's is an Ubuntu Help Page which gives a good explaination if any one is interested
I think there is some research followed by a rebuild on my horizon Thanks for the suggestions and the thread It's proving educational. I'll let you know how I get on, at the very least post some new build times
EDIT / UPDATE
I did some research and made some tentative first steps with my Kernel Configuration.
I decided to get on the mainline and build a 3.6-rc1. I removed a number of options I know to be redundant In my case, e.g Laptop Support, Intel Support etc
My research did throw up this Gentoo Wiki With Some useful "copy/pasta" compiler optimization, they also have a more in depth guide here.
After building this new kernel and clobbering my aosp tree I did
full_grouper-eng for JRO03L and a
make -j10 which resulted in
real 49m32.493s
user 312m45.481s
sys 17m55.599s
While this is still high, it's a step in the right direction, The times are around the same length I was getting for a full_panda with -j12 previously. I'll do a direct comparison also, Kinda Makes sense
I got quiet a lot of room for Improvement and many options, Only Clock at 2.8Ghz at the Moment.
AMD Provide an FX Bulldozer Specific GCC Toolchain which Is going to be employed when the I Rebuild the Kernel again
I Plan to tweak a bit, test a bit and see If I can get the performance some where close and hopefully learn some tricks along the way If all else fails I'll Surmerge the lot in a fishtank full of cooking oil and clock it to 5GHz
UPDATE 2
Following on from the Build Above -
Full_panda-userdebug make -j16
real 32m16.986s
user 196m34.933s
sys 13m9.521s
full-eng
aosp jellybean
fx-8120, 8gb ram, 8gb swap
make -j16
real: 34m2.641s
EDIT: about to test some tweaks! will update.
Machine: Dell Inspiron 1565
Processor: Intel Core 2 Duo 2.0GHz
Hard Drive: 320GB HDD
RAM: 4GB
OS: Ubuntu 11.04
Current Build Time: 2 1/2 +
Build: CM10 PA Source
Just added ccache. We will see on the next build if I shave some time.
I'm just gonna go out and say it. When it comes to ROM development, I'm a complete noob. However I learn extremely fast, and once I learn, I make amazing things.
I love Android. I love Android hacking. I love the utilization of custom ROMs. And now, I want to love ROM development.
But maybe my computer can't do it? Not sure. It's an Acer Aspire 5000 from 2006 currently running Windows 7 Ultimate and I keep it in safe mode to run faster. It has 512mb RAM I believe.
What are the system requirements of developing a ROM?
TrikkJames said:
I'm just gonna go out and say it. When it comes to ROM development, I'm a complete noob. However I learn extremely fast, and once I learn, I make amazing things.
I love Android. I love Android hacking. I love the utilization of custom ROMs. And now, I want to love ROM development.
But maybe my computer can't do it? Not sure. It's an Acer Aspire 5000 from 2006 currently running Windows 7 Ultimate and I keep it in safe mode to run faster. It has 512mb RAM I believe.
What are the system requirements of developing a ROM?
Click to expand...
Click to collapse
A PC for building a ROM will need to be running Linux, also it will need at the least 4GB of ram or more to help the process, as for the processor that's typically up to the user but something along the lines of an Intel core i5 or i7 are ideal for speed. Some ROMs can take hours to build and last but not least a nice big hard drive typically 500gb or more. This would typically be an ideal ROM building machine, however I'm not a ROM builder these are just what I've learned overtime from actual developers. Any other devs willing to chime in on my post is more then welcomed.
Sent from my LG-LS980 using xda app-developers app
Critical Detox said:
A PC for building a ROM will need to be running Linux, also it will need at the least 4GB of ram or more to help the process, as for the processor that's typically up to the user but something along the lines of an Intel core i5 or i7 are ideal for speed. Some ROMs can take hours to build and last but not least a nice big hard drive typically 500gb or more. This would typically be an ideal ROM building machine, however I'm not a ROM builder these are just what I've learned overtime from actual developers. Any other devs willing to chime in on my post is more then welcomed.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Hmm someone over at Android Forums told me I'd be fine as long as it wasn't from scratch.
Then they recommended that if I'm on a budget that I can look for i3 with 4gb ram?
But I know absolutely nothing about buying ram.
Hi!
I have a Samsung Rugby Smart (SGH-i847). I have look for it. It have (had?) a CM9/10 builds but kernel 3.0 have camera broken. CM9 in kernel 2.6.x just have too many bugs (battery drain and codecs mostly).
There are a couple of MSM8255T devices with KK, like the Galaxy W (witch is supose to be base for the Rugby Smart) or the Galaxy S Plus (i9001), that serves for kernel develoment to those devices. I don't wanna try anything without being sure of what I'm doing. I don't expect everything to run flawless, but at least to know how to enchanted it.
It's an old device I know, but I think that 1,4 Ghz processor and 512 Mb RAM on KK could have a shot. That or CM 7.2. If it's easy to build a CM 7.2 with the 2.6.x kernel, so be it. I don't care. I just want something funcional, and I like TW, but in this smartphone (This is my 1st Samsung) it's just laggy and horrible.
This are kernel sources for the Galaxy S Plus:
https://github.com/AriesVE-DevCon-TEAM/samsung-kernel-msm7x30/tree/cm-11.0_ion_pmem_adsp
You can find the sources from the Galaxy Rugby Smart from Samsung web site. (I find the site right here in XDA in this section, and download them).
I'm planing to use Buildbuntu to cook.
Experiences cooking before: ZERO. NULL. ILLEGAL ARGUMENT. I can code throug, I learn fast. I just need to read, at lot. Maybe twice, or threece, but I can learn, and can code. I do have experiencies with GIT, Linux, as a app developer.
Sorry for the english, it's not perfect I know that. THANKS YOU! So much. . I know there is not a lot of people with this phone, but if I can make them a KK build, I'll be happy to. .
No one? Please. I really want to learn. :-/. I just don't know what exactly have to do to make the build or the drivers. I mean, maybe the Galaxy S plus kernel work with some mods, but I don't know how to "mod" it. Or just compile CM7.2 from source and make it work with cm/stock kernel.
m1k3_ said:
No one? Please. I really want to learn. :-/. I just don't know what exactly have to do to make the build or the drivers. I mean, maybe the Galaxy S plus kernel work with some mods, but I don't know how to "mod" it. Or just compile CM7.2 from source and make it work with cm/stock kernel.
Click to expand...
Click to collapse
Start here:
http://forum.xda-developers.com/showthread.php?t=2302780
But keep in mind you will need a computer with a decent processor (core 2 dou, i5, i3, i7, etc.) and 4GB of ram or more. Also, at least a 120GB Hard drive if your planning on making multiple builds. For cm7 40GB of free space should do
Good luck
caspboy said:
Start here:
http://forum.xda-developers.com/showthread.php?t=2302780
But keep in mind you will need a computer with a decent processor (core 2 dou, i5, i3, i7, etc.) and 4GB of ram or more. Also, at least a 120GB Hard drive if your planning on making multiple builds. For cm7 40GB of free space should do
Good luck
Click to expand...
Click to collapse
I would like to just porting CM 7.2 as it seams like a easy way to start. I'm planning to use Buildbuntu (http://forum.xda-developers.com/showthread.php?t=2585828) to do it.
Thanks in any way!
I just no sure about how to do things. Or where to code. .__.