Related
edit: Just found out it is is ALREADY DONE! Well, that was sort of a lie, but it is already possible, and will hopefully evolve into the easiest way of testing ROMs ever. ROM-whores, enjoy! Changed the topic title to spread the happy news. Go give him useful feedback and coding help!
While I am not as big a ROM-slut as many other, I do like to check things out. The Eclair-ROM by manup456 is high on my list now, for example, and while I'm swapping ROMS, I would like to test whats happening with the Hero ones.
And one thing strikes me: It would be extremely convenient to be able to launch the ROM right from the sd card. unpacking the ROM-zip to a partition on the sd card, and then launch it directly from there, would be much easier than having to flash it to the phones flash. And also, people would avoid to wear the poor nand flash out. Being able to boot from SD would also allow us to have more than one ROM installed, and switching at reboot.
Have anyone got any idea of how much work this would take? Would the ROM need to be customized for this? (I hope not.) An more importantly: Does anyone with any coding skills like the idea, and care to give it a shot? I know the OpenMokmo-projects used U-boot, and some Debian derivative projects uses Qi. I have no idea, however, if there is a small, moderate or huge amount of work to make those work on the Dream/with Android, or if customizing tthe existing is easier (if at all possible).
While this can be setup, it would require alot of work, and all devs would have to change the format of the boot.img they are using. So... probably not going to happen
naguz said:
While I am not as big a ROM-slut as many other, I do like to check things out. The Eclair-ROM by manup456 is high on my list now, for example, and while I'm swapping ROMS, I would like to test whats happening with the Hero ones.
And one thing strikes me: It would be extremely convenient to be able to launch the ROM right from the sd card. unpacking the ROM-zip to a partition on the sd card, and then launch it directly from there, would be much easier than having to flash it to the phones flash. And also, people would avoid to wear the poor nand flash out. Being able to boot from SD would also allow us to have more than one ROM installed, and switching at reboot.
Have anyone got any idea of how much work this would take? Would the ROM need to be customized for this? (I hope not.) An more importantly: Does anyone with any coding skills like the idea, and care to give it a shot? I know the OpenMokmo-projects used U-boot, and some Debian derivative projects uses Qi. I have no idea, however, if there is a small, moderate or huge amount of work to make those work on the Dream/with Android, or if customizing tthe existing is easier (if at all possible).
Click to expand...
Click to collapse
Hi folks, I spent a good part of my sunday (and friday night, let's be honest) to port UAE4All for Android. So here's UAE4Droid. Most games are working fine, don't expect killer framerates though (it should be faster on a Droid). I don't plan to actively support this app, so here's the catch:
-no sound
-physical controls only (that's why I post here, you can configure them btw)
-no save states (the original project does not implement them, and I'm no good at understand basics of the 68000 emulation)
-should be ok starting from Android 1.5 but I didn't test it (Dream on Cyanogen here).
You need to own a rom copy and some disks to use this legally, of course. If there's some good feedbacks, maybe I'll put it in the market (already done a couple of emulators there). Enjoy !
Edit 12/27 : Now with sound and touch controls on the Android Market
damn you did this in one day?
make it one and a half
It's a port, not that hard, once you got some Android knowledge, the basics of the SDK-NDK interaction, and the open source works from several people. And I left some parts (sound and touch controls), quite buggy/boring to code
Did you ever know that you were my hero? Seriously, great stuff! If you could add sound this would be the best thing I have on my phone!
Amazing. Superfrog works pretty well. If I could just insert all floppies at once it would be completely awesome.
If you're not planning on supporting this too much in the future would you consider making it open source?
It's completely fun to put android next to my old ami500, old 1200 and turn on superfrog on each
Oh wow...that's pretty impressive. Superfrog on my phone would be awesome! I'll have to try it.
Ok, hate to leave work unfinished so I added the sound and touch controls. Watch the Market, it should appear there soon.
btw to enable the sound on a HTC Dream makes the emulator a little more sluggish, well now at least you'll have the choice (or buy a 2nd gen Android device )
Not working properly. App asks me to force close when I'm pressing MENU button... Previous build (from first post) works properly. Can I please to fix this bug?
After all, great job
Damn, I didn't make that much changes, could you get me a log trace ?
Hmm It's weird... After a couple of restarts of phone, the app is working correctly... I will leave a post (and logcat) when this problem come back.
Sadly doesn't Install on Eclair.
adb install gives Error Message "INSTALL_FAILED_CPU_ABI_INCOMPATIBLE"
Kubax83 said:
Sadly doesn't Install on Eclair.
adb install gives Error Message "INSTALL_FAILED_CPU_ABI_INCOMPATIBLE"
Click to expand...
Click to collapse
looks like a modded ROM issue to me (this emulator is compiled for ARM, no doubt about it). Try the one from the market
Wow this works really well, playing Superfrog on it now Any plans to add save states to this?
I wonder how much better performance is on the droid. Superfrog plays perfectly on my G1 with frame skip disabled and sound off, having it on made it more jerky.
Also would it possible to have the escape key mapped to something, like the shutter button or as a menu item, i'm sure some games needed it to get into the menu.
Thanks for porting this!!
5 stars from me
works great, played with it a little. kickstarted 3.0 ROM, loaded game with no problems - but Hero's hardware isn't up to it. Maybe on my next android, with faster CPU and proper keyboard...
Only problem I have had is it doesn't seem to like some of my Kickstart rom files, it works fine with one of the 1.3 roms I had with WinUAE, but says Invalid for most of the others including 3.1, all of which work in WinUAE, any ideas?
what's the exact size of the non working roms ?
Non working rom size is as follows:
3.1 - 524,299 bytes
Just thinking could it be because it is a rom from Amiga Forever from Cloanto, do they use a keyfile for the rom?
No, because I thought every roms was 524288 bytes long. Will update the market version tonight
Blazing fast on a Droid/Milestone! Thanks a lot. Just the Mouse-Control is still a little buggy. For Disk-Activity you could use the green/red led! =)
how keyboard is emulated
Hi,
I have successfully set-up UAE4Droid, tried my favorite game, but it(Pinball Fantasies) needs alt or shift to control the game. I could not figure out how to play the game because of this. (Pressing alt or shift on the G1 does not work. )
Anybody know how to use these keys?
Thanks
Sandor
This is mainly for other newbies when it comes to custom boot animations so you can learn from my mistakes.
I spent a couple days, off and on, working on a boot animation for my captivate and after a few snags I got it to work. Joy of joys. After achieving this small feat I decided to one up by making a longer animation.
It was over 200 frames and it paused halfway through before it would continue and then after that, the animation was choppy/lagging.
I tried messing with the frame rate to no avail. Really bummed out, I checked some other custom boot animation and saw that some where png and some were jpg.
Hmmm... mine were all png. I converted them all to jpg and as an added measure I converted the resolution down from 480x800 to 240x400.
That did the trick... in fact, the whole animation was able to loop 4 times or more with subsequent plays being a bit faster.
Another thing, IrfanView (free) is your friend and so is RootExplorer (money well spent) and Samba (free).
I am going to tweak my creation a bit more to make it a little smoother, but mostly I am happy with it. Basically it is the Android mascot trying to catch a bee which he ends up eating and turns into the Honeycomb OS mascot.
An earlier version is on Youtube, minus the catching the bee sequence and other stuff.
Any helpful hints are appreciated.
Why not post your boot animation, too? Unless it has your phone number or something on it, I'm sure there are folk who would love to use it! It sounds (how do those kids say it...) whack!
Hello all,
so I was living the life with my new rooted nook color, when suddenly i pulled it out of my pack and found the entire screen was dead. There is a black blotch at the bottom so i am quite certain the LCD is cracked and not coming back.
SO now I THINK I desperately need to unroot. I am VERY scared of doing this with NO screen though. Do you think I even need to unroot, as you can only really see splotches of color when the NC is turned on? Can anyone give me some advice as to a good SAFE way to get my nook back to a state that i can send it into barnes and noble (i have the extended warranty so they will cover ONE damage replacement)?
I wouldn't worry about it. Somebodies going to pull it out of the package, see the screen and toss it on the pile. *If* it is refurbed it'll be wiped and reloaded as a matter of course.
Thanks for your reply. Yeah its pretty hard ro tell that anything has been done to it. When it boots up a solid flickery green bar (which would have been the cynogen logo) goes across the whole screen. Other than that its basically just dark. I don't know, if I knew what cynogen mod looked like I would think it might be fishy, as the nook boot screen is all white.
I'm really not sure what to do. I suppose I could break it more so the screen is completely incomprehensible, but id really rather just unroot it, I'm just really not sure how to navigate clockwork without a screen
see if you can adb into it when its booted... if you can then there are options to install stock back.... let me know if you can adb... i'll give you links to images to dd back to eMMC.
Ok, after a good googling and an hour of tinkering with device manager got the usb drivers working and adb can see my nook color. What exactly did you have in mind to test the functionality of adb? should i try pushing files or something?
0point said:
Ok, after a good googling and an hour of tinkering with device manager got the usb drivers working and adb can see my nook color. What exactly did you have in mind to test the functionality of adb? should i try pushing files or something?
Click to expand...
Click to collapse
You can download 7zipped images of /dev/block/mmcblk1,4,5,6,7 and 8 from my depositfiles...
There is a md5mmcblk_md5's.txt to verify the downloads against.
There is also a partitions.txt files that describes how to image them to your device... the commands are available for you to copy and paste into a command window or terminal screen. It might work as a dos batch file if renamed .cmd... but I don't recall if the commands will run in the adb shell when executed that way.
extract them with 7zip or winrar... copy the .img files to the root of sd card... preferably one and 8 GB or larger... so you can put them all on at once... perform the commands you will find in the partitions.txt file.
Ok so,
not to be ungrateful, but is there anyway you could put these up on maybe mediafire or some other service where there isnt a free download limit? I'd really like to avoid paying 12 bucks just to get six files in under a day (it's probably just going to shut me out after a couple anyway)
If you can see the display well enough to see when it starts to boot up.......then you can always do the 8 interruped boots. This will take it back all the way back to 1.0.1 stock.
0point said:
Ok so,
not to be ungrateful, but is there anyway you could put these up on maybe mediafire or some other service where there isnt a free download limit? I'd really like to avoid paying 12 bucks just to get six files in under a day (it's probably just going to shut me out after a couple anyway)
Click to expand...
Click to collapse
Will setup account and upload to mediafire for you...
EDIT: I have to create a pro account to upload the files... since free mediafire has 200 MB size limit... and 8 of the partition files are MUCH larger than that.
EDIT2: Uploading to mediafire now... You will see the .7z files and files named mmcblk0p5-8.partX.rar... after you have all the rar's... they will extract to the .7z files for each partition... sorry... was just easier for me to split the .7z's I already created this way.
dparrothead1 said:
If you can see the display well enough to see when it starts to boot up.......then you can always do the 8 interruped boots. This will take it back all the way back to 1.0.1 stock.
Click to expand...
Click to collapse
That may or may not work... depending on recovery.img on the eMMC...depending on the condition of /dev/block/mmcblk0p3... these are a couple of reasons I made the recovery files available.
Just a Tip for DizzyDen:
I recommend a site called FileTrip for future uploads. It's owned by the guys that run GBATemp. For Personal Uploads you get 100gb of Storage and 4gb per file, all for Free!, No Upload Limits, No Download Limits, very few Ads(no Annoying ones), Viewing of Documents Online, Streaming of Web Browser(HTML5) compatible Media files, and more. Only Con I find with it is that You can't resume Uploads and it lacks Batch Uploading(Although you can open Multiple Tabs of the Uploader) but nothing that would annoy Downloaders.
@DizzyDan
you are a boss man. Thank you so much for throwing these on mediafire, and the fact that you split them up actually means that with my weak wifi signal i can still dl the whole thing without having to constantly start over.
you're a cool guy man :cyclops:
I've been working on a ground-up port of Jelly Bean for the Fascinate (to be called "GeeWiz Player" when it's ready), and one of my final clean-up steps has been to fix the battery charger services. As it turns out, the AOSP charger works fine on the Fascinate and you don't even need the silly Samsung QMG files and binaries. However, you do need some graphics to at least somewhat match the in-built JPG on the LFS partition if you don't want to change that.
I'm no graphic artist, but I spent some time on this and came up with a set of what I think are generally decent replacements for the Samsung charger QMG file images. They are not green, but ICS/JB blue instead. Figured I'd share in case they could come in handy for someone else. I have extra ones for the 10-30-50-70-90 percentages that aren't used by AOSP charger, and I suggest changing the code such that it doesn't skip the 80% animation, but I digress.
Attached to this post in a zip file. Not a perfect match for Samsung's, but I'm running with them for now. Spent far too much time on these already - these are the fourth iteration, and I'm mostly happy with them.
If anyone that's actually good at this stuff picks these up and runs with them, would you mind letting me know if you improve them? I kinda doubt this is something anyone else would be working on, but you never know! :laugh:
- djp
djp952 said:
I've been working on a ground-up port of Jelly Bean for the Fascinate (to be called "GeeWiz Player" when it's ready), and one of my final clean-up steps has been to fix the battery charger services. As it turns out, the AOSP charger works fine on the Fascinate and you don't even need the silly Samsung QMG files and binaries. However, you do need some graphics to at least somewhat match the in-built JPG on the LFS partition if you don't want to change that.
I'm no graphic artist, but I spent some time on this and came up with a set of what I think are generally decent replacements for the Samsung charger QMG file images. They are not green, but ICS/JB blue instead. Figured I'd share in case they could come in handy for someone else. I have extra ones for the 10-30-50-70-90 percentages that aren't used by AOSP charger, and I suggest changing the code such that it doesn't skip the 80% animation, but I digress.
Attached to this post in a zip file. Not a perfect match for Samsung's, but I'm running with them for now. Spent far too much time on these already - these are the fourth iteration, and I'm mostly happy with them.
If anyone that's actually good at this stuff picks these up and runs with them, would you mind letting me know if you improve them? I kinda doubt this is something anyone else would be working on, but you never know! :laugh:
- djp
Click to expand...
Click to collapse
So we download and flash in cwm?
Sent From my recently converted Paranoid-Android Deviled up 1.4.1 100% supercharged Fassy
vrahn said:
So we download and flash in cwm?
Sent From my recently converted Paranoid-Android Deviled up 1.4.1 100% supercharged Fassy
Click to expand...
Click to collapse
No, these are just PNG images for modders in case they come in handy. Completely useless by themselves.
For what I'm working on, I didn't like or want to continue to use the Samsung proprietary battery charger and switched to the stock android one. The graphics were to make it look more like Samsung's with the big sideways battery that matches their power-on screen.