Toggle sidebar

Homebrew [WIP - ALPHA 1] Android3DS - Android 2.0 Eclair on the Nintendo 3DS

Octoblimp said:
If trying to turn it off and on again doesn't work, its possible your files didn't transfer over correctly (this is more common than you think). You may need to try transferring them again.
Click to expand...
I will most likely post an update tomorrow if I cannot get it done as I'm typing this right now. I am attempting your suggestion first though before I copy files tomorrow.
 
When I register for the mobile data, it says "Regristration received, but mobile_regristration.conf could not be saved." Any fixes? The dialer says to check SD card, but I have no idea what I need to look for.
 
The Real Jdbye said:
I can't imagine o3DS being a very usable experience, with its 128 MB RAM, not to mention potato CPU compared to even the earliest Android phones.
New 3DS might actually do pretty well though, 256 MB is more in line with what Android phones at the time would have had and none of those had more than a single core CPU. Quad core should make the experience much smoother than it ever was on Android phones back then.
Click to expand...
does android 2.x even support multi-core CPUs? not to mention if any apps of the time supported them either. The potential performance benefit from that won't mean much if 3 of the cores sit unused, though the n3ds still has an l2 cache and higher clocks than the o3ds so there's still a speed benefit
 
Latiodile said:
does android 2.x even support multi-core CPUs? not to mention if any apps of the time supported them either. The potential performance benefit from that won't mean much if 3 of the cores sit unused, though the n3ds still has an l2 cache and higher clocks than the o3ds so there's still a speed benefit
Click to expand...
Apps I highly doubt are designed to take advantage of multiple cores but it is Linux based so it should support it on the OS level which will benefit multitasking and general system responsiveness (since your background apps are not fighting with the foreground app for CPU time)

Worth noting that the 3DS is ARM11 (ARMv6), which some Android smartphones used, but it was not very common. So some apps might not work or will run slower than you'd expect because they were designed for ARMv7.
 
Latiodile said:
does android 2.x even support multi-core CPUs? not to mention if any apps of the time supported them either. The potential performance benefit from that won't mean much if 3 of the cores sit unused, though the n3ds still has an l2 cache and higher clocks than the o3ds so there's still a speed benefit
Click to expand...
It may not have on the devices of the time, but here it is supported. On Old 3DS it has two cores, on New 3DS it has 4 cores (so New 3DS mode is supported and it takes full advantage).

notthefbi said:
I posted my repo, but its not compilable right now. Posting this because it's a different codebase and a newer android and ill update it tomorrow. https://github.com/roastme/cyano3ds
Post automatically merged:

Also OP isn't the claim that its gpu accelerated false (like in scope.md)
Click to expand...
If SCOPE.MD still says that (I know README.MD did initially) its false. It is in fact GPU-accelerated. If it wasn't, Global Time wouldn't work as it requires OpenGL and to get OpenGL, GPU acceleration must work.

rockhardsausage said:
When I register for the mobile data, it says "Regristration received, but mobile_regristration.conf could not be saved." Any fixes? The dialer says to check SD card, but I have no idea what I need to look for.
Click to expand...
The mobile_registration.conf, along with wpa_supplicant.conf files are stored under sdmc:/linux/android/persistent/shared so try looking there
 
Octoblimp said:
If SCOPE.MD still says that (I know README.MD did initially) its false. It is in fact GPU-accelerated. If it wasn't, Global Time wouldn't work as it requires OpenGL and to get OpenGL, GPU acceleration must work.
Click to expand...
Dude did you read that document yet? (I read the docs on my own project)
 
notthefbi said:
Dude did you read that document yet? (I read the docs on my own project)
Click to expand...
I read the README.MD document yes, which is how I knew to remove that line and make a couple of other adjustments. The SCOPE.MD was back from when GPU acceleration did not work, and it didn't work because the code at the time it tried to talk to the GPU and it just crashed the whole system. When GPU acceleration finally did work, Claude did not update SCOPE.MD. That is not really my fault honestly. I'm shocked it didn't update the scope but then again, its irrelevant anyhow as other documents that may not have been attached with the repository give the AI the information it needs, so its not solely relying on the SCOPE, if its even relying on it at all.
 
notthefbi said:
I posted my repo, but its not compilable right now. Posting this because it's a different codebase and a newer android and ill update it tomorrow. https://github.com/roastme/cyano3ds
Post automatically merged:

Also OP isn't the claim that its gpu accelerated false (like in scope.md)
Click to expand...
I didn't believe the other post with angry birds running until you posted this. Thank you for your effort.
Post automatically merged:

MattTheTekie said:
I will most likely post an update tomorrow if I cannot get it done as I'm typing this right now. I am attempting your suggestion first though before I copy files tomorrow.
Click to expand...
I will update later today.
Post automatically merged:

Its too slow to use. It takes minutes to get to the wifi settings, and I can't try with this. I've waited at least an hour trying copying over and over onto my enterprise 32gb known working and tested card. It connects to the WiFi now at least but I can't get into the browser or settings without waiting insaine loading times. I know it's because this hardware can't handle it but I've tried. Thanks for the insaine project tho!
 
Last edited by MattTheTekie,
MattTheTekie said:
I didn't believe the other post with angry birds running until you posted this. Thank you for your effort.
Post automatically merged:


I will update later today.
Post automatically merged:

Its too slow to use. It takes minutes to get to the wifi settings, and I can't try with this. I've waited at least an hour trying copying over and over onto my enterprise 32gb known working and tested card. It connects to the WiFi now at least but I can't get into the browser or settings without waiting insaine loading times. I know it's because this hardware can't handle it but I've tried. Thanks for the insaine project tho!
Click to expand...

No problem! Sorry its too slow on your Old 3DS. It DOES run, and I did say to expect it to be slower. Perhaps in future builds I can optimize it? Not sure by how much though. Honestly Android 1.X would run best for Old 3DS.
 
  • Like
Reactions: MattTheTekie
Octoblimp said:
It may not have on the devices of the time, but here it is supported. On Old 3DS it has two cores, on New 3DS it has 4 cores (so New 3DS mode is supported and it takes full advantage).


If SCOPE.MD still says that (I know README.MD did initially) its false. It is in fact GPU-accelerated. If it wasn't, Global Time wouldn't work as it requires OpenGL and to get OpenGL, GPU acceleration must work.


The mobile_registration.conf, along with wpa_supplicant.conf files are stored under sdmc:/linux/android/persistent/shared so try looking there
Click to expand...

Octoblimp said:
I read the README.MD document yes, which is how I knew to remove that line and make a couple of other adjustments. The SCOPE.MD was back from when GPU acceleration did not work, and it didn't work because the code at the time it tried to talk to the GPU and it just crashed the whole system. When GPU acceleration finally did work, Claude did not update SCOPE.MD. That is not really my fault honestly. I'm shocked it didn't update the scope but then again, its irrelevant anyhow as other documents that may not have been attached with the repository give the AI the information it needs, so its not solely relying on the SCOPE, if its even relying on it at all.
Click to expand...

I am pretty sure that the SCOPE.MD is actually the correct one here and the driver only does gpu certification and doesn't actually work yet
 
Octoblimp said:
No problem! Sorry its too slow on your Old 3DS. It DOES run, and I did say to expect it to be slower. Perhaps in future builds I can optimize it? Not sure by how much though. Honestly Android 1.X would run best for Old 3DS.
Click to expand...
I think you can but it's completely unusable. I expected it to be more like a PoC but not like one frame every 20seconds to 10+ minutes.
 

Site & Scene News

New Hot Discussed User Submitted

Go to forum More news

Popular threads in this forum