Database Develop

Louder Volume Hack v1.0 by Meltus in the market now!!!

yup, it's finally in the market!
if you want to elliminate the tedious adb/terminal commands, then this is the app for you!!
updates coming soon, along with an EQ app!!
cheers for everyone who helped me with this!
everyone who did help messege me!!

cool!
Quick?, safe to use with the dudes 1.3rc2?

Yeah sorry about the force closes, I'm gonna try fixing it tonight.
Spent ages trying getting rid of the force closes, thought id sorted it but evidently not ><
Its odd because it works fine for me off the market.
I should have it sorted by tonight
Sorry again guys

Will you include V5 mod?

Yeah, will be updating it a fair bit soon, just need to get the 'basics' working first

Just read the comments in the market and this made me chuckle a bit
"How does an app that does nothing but force close get a 3 star average?"

DOHCtor said:
Just read the comments in the market and this made me chuckle a bit
"How does an app that does nothing but force close get a 3 star average?"
Click to expand...
Click to collapse
A famous quote... "The two most common elements in the universe are hydrogen and stupidity."

i've had a few people e-mail me saying that this is 'bull*hit' and 'this will never work' and someone calling me a 'scammer, trying to steal peoples money' (seriously, how could i steal people's money when there's a refund policy lol ><)
gotta love the market.
also, just bought a new sd card (because mine conveniently corrupted itself out of spite) so i'm gonna do some serious testing now.

keep up the good fight!
Looking forward to trying it out once you get it updated.

Hey dan, it force closes for me too. Try looking at the code again and see if you have any invalid pointers(?) or what not.... i dont mean pointers, but you know what I mean. Let me know when you update it again so I can run it and debug it through DDMS and so I can also run a trace on it.

Im super excited about this one! There are 2 things that bother me about my g1. Volume and Battery life. I cannot wait to try this out tonight when you get it fixed!
Whats up with the comment from the user that says you have to have Lucid's Mod? Where did he read that at?
Anyhow, Thanks Meltus! Looking forward to it.

Love the idea for the audio mod app, I've used the terminal commands in the past to get it to work (since it no longer seems to work in TheDude's releases anymore). I'd imagine it still runs through the Terminal shell?

will the eq be included in this app or in a seperate app? I will buy both when they are working for sure- i like to support developers.... eg. bought rockon etc...

People see a lot of junk out in the market, so sometimes even good devs get hit with accusations- especially if accusers do not review XDA to know what is real.
How are you getting past the SDK limits in regards to raw audio? It seems that an EQ would beat the CPU to death trying to work correctly unless more resources were made available in the recent OS update.
This is one of several big reasons Coreplayer team hit a wall with Android. Not to mention video codecs would also kill the CPU and still be a battery hoggin' stuttery mess.

the EQ is not an actual program that modifies the sound, it's a set of files that alter the 'built-in' EQ that HTC never bothered to enable.
i'm just going to make an app that can change it on-the-fly.
but atm i'm stuck at trying to push files from the app to the phone. it seems quite simple but i've been trying for about 6 hours now and got fkin nowhere
any ideas anyone?

Is it something to do with the files you are trying to access the built in EQ? The CPU on the G1 does have the function, but I would have thought a driver would be needed from Qualcomm?

i havn't even started on the EQ app yet, this is just for my audiohack app.
The 'EQ', if you can call it that, is a just file with hex values which control the various different gain settings for the different frequencies.
check my signiture for more info and a how-to.
also, my Volume Hack is now fully working, but, only if you've used my files in the past. which is quite bizzarre. it just refuses to do it with the stock files from any build, but if i replace the stock files with EXACTLY the same files but through adb, it then works fine.
i have no idea whats going on. my app sets the system in r/w mode fine so that can't be it.
i hate java

Meltus said:
i havn't even started on the EQ app yet, this is just for my audiohack app.
The 'EQ', if you can call it that, is a just file with hex values which control the various different gain settings for the different frequencies.
check my signiture for more info and a how-to.
also, my Volume Hack is now fully working, but, only if you've used my files in the past. which is quite bizzarre. it just refuses to do it with the stock files from any build, but if i replace the stock files with EXACTLY the same files but through adb, it then works fine.
i have no idea whats going on. my app sets the system in r/w mode fine so that can't be it.
i hate java
Click to expand...
Click to collapse
Just keep plugging away at it. Surely, someone around here wil be able to help you over this speed bump.

Meltus, what it sounds like is just the need for the files to be accessed in the first place. I haven't tried the app yet, but I wonder if it would work since I only used terminal for your audio mods in the past? In which case, you could probably use the same terminal code if that's possible.

I did the mod through the terminal already but I couldn't find it in the market earlier. I figure you pulled it for now due to the problems people are running into but what would I search when it is there. I want to support the community if I can, be it just a simple review.

Amiga Emulator for Android

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

[PRJ/TT/Kernel] Dynamic ramdisk.. Now with button backlight notification. z4mod.

OK, this is a little strange, but I think the idea is useful for people that want to mod the ramdisk but don't want to fiddle with compilers and such. It requires a kernel, so I'm including a proof of concept here. However, once the basic support is in a kernel, you can change anything about the ramdisk and the boot process WITHOUT changing your kernel!
For example, say you want to change init.rc... You can do that, and if it fails to boot, if you stored it on your external SD card, just pop out the card and boot up, the change won't be able to copy over at boot, so you are back where you started. No odin, no kernel mod.
The basic idea is simple. It runs init.d style scripts (if found) BEFORE the android init process starts up. This allows you to change literally anything in the ramdisk without the hassle of building a kernel. You can replace the /sbin/init binary if you want to, whatever.
This also means you could install and/or upgrade a lagfix, even voodoo, by copying a single file to /system/etc/init.d and rebooting.
This is more useful for devs I think than for end users, but perhaps users will find it useful.
NOTE: This is DANGEROUS STUFF. If you store your files in a world-writable location like /sdcard, ANY app could change your ramdisk! As it is, any root app can do it with this change. Anything run in the pre-init scripts is, by definition, run as root. So watch your permissions and don't store stuff used by the pre-init scripts in a FAT filesystem. EXT2/3/4 and RFS will work fine if you set them to root-write only. If in doubt, use "chmod 700 <file>". All of this should be obvious to most people here, but I think it's important to point out just in case.
This is based on Unhelpful's 1.7 kernel. It runs great on my Vibrant. There is one known bug, it reverts the locale to en_GB on boot, which is mildly irritating. I can't figure out why this happens. If someone knows, please post. I did write a simple app that switches it back to en_US using MoreLocale 2 (market) on boot, if people want it.
Credit to Unhelpful (kernel source and nice build scripts), JAC and Supercurio (examples for setting up the ramdisk properly for this sort of thing).
All the init scripts live in /system/etc/init.d. P*** are pre-init scripts. E*** are early-init scripts run before /data and /dbdata are mounted, allowing you to override mount options and such at that point, S*** are standard init scripts that launch right before the Android OS starts up, so the full environment is available to them. So you now have 3 hooks to start init scripts up. The boot process will wait for them to complete, so don't do anything that takes a long time if you don't have to, or start it in the background with "cmd &" or similar.
http://www.tabbal.net/files/t959-ttabbal-v1.0.tar
Flash with Odin. I'll consider putting up a ZIP later. Please, be at a computer with Odin and a known good kernel when you do this, this should be considered beta at best. Hardware locked phones should probably avoid this as well. Also, disable voodoo before messing with this, it does not include the voodoo script. If you really want to try it, you should be able to copy it to the init.d directory, but it would be better to wait a bit.
If it works well, hopefully other kernel devs will include the framework. I may also start posting updates from Unhelpful's git tree if there is interest as well now that I have a decent environment set up. See his thread in the Captivate forum for details on what changes have been done. OC/UV is supported, but I haven't worked with it much. You have to enable it by creating a config file and putting it on the phone. I'd recommend the external SD card in case you have a problem with a bad config, so you can pull the card and boot without clock changes. The OC/UV config can also be changed at runtime.
There is no need to pre-flash anything, and init.d need not exist or have any scripts in it. The system will boot fine without them.
If you try it, please post your thoughts. I'd like to see if there is interest for this line of work. If you don't understand a thing I said above, please don't install it.
Updates:
http://www.tabbal.net/files/Kernel-ttabbal-v1.2.zip
http://www.tabbal.net/files/Kernel-ttabbal-v1.4.zip
http://www.tabbal.net/files/z4mod-ttabbal-v1.1.zip

Wow, I am afraid to mess with this today. (expecting an important phone call)
I will flash it tomorrow morning however. And post some results, I have an idea about what to do with this.
Thanks Travis!

I hope you find it useful! I forgot to note one thing. If you want to see what your pre-init scripts are up to, there's some info in /init.log. Not a ton, but you can at least see if your script was started and such from there.
Also, if anyone cares, it works on Frankin-Twiz Final. I decided to check it out once I got this little project working.
I'm curious to see what people come up with, I've seen some complaints about not being able to edit the ramdisk without building a kernel. So now they can.

ttabbal said:
I hope you find it useful! I forgot to note one thing. If you want to see what your pre-init scripts are up to, there's some info in /init.log. Not a ton, but you can at least see if your script was started and such from there.
Also, if anyone cares, it works on Frankin-Twiz Final. I decided to check it out once I got this little project working.
I'm curious to see what people come up with, I've seen some complaints about not being able to edit the ramdisk without building a kernel. So now they can.
Click to expand...
Click to collapse
You mind sharing your init setup. I am familiar with Unhelpfuls method and just want to see what you have changed from his.
I stayed away from his method with Voodoo as it was causing issues at diff points of development and went with the run-parts solution. But it may be in better shape now that you have gone over it.
Most users will only need one hook but options are always good.
I've always been one the fence about the runtime OC/UV. Most people are looking for a stable voltage file that will work with their phones in the thread, but it is def awesome for those that are familiar with what they are doing.

justanothercrowd said:
You mind sharing your init setup. I am familiar with Unhelpfuls method and just want to see what you have changed from his.
I stayed away from his method with Voodoo as it was causing issues at diff points of development and went with the run-parts solution. But it may be in better shape now that you have gone over it.
Most users will only need one hook but options are always good.
I've always been one the fence about the runtime OC/UV. Most people are looking for a stable voltage file that will work with their phones in the thread, but it is def awesome for those that are familiar with what they are doing.
Click to expand...
Click to collapse
Talk to braka, we been hi-jacking the init for a bit, I've been working on getting a Desire pport working on are rom.. ( Well, barak has been hi-jacking the init ) I just build kernels.

justanothercrowd said:
You mind sharing your init setup. I am familiar with Unhelpfuls method and just want to see what you have changed from his.
I stayed away from his method with Voodoo as it was causing issues at diff points of development and went with the run-parts solution. But it may be in better shape now that you have gone over it.
Most users will only need one hook but options are always good.
I've always been one the fence about the runtime OC/UV. Most people are looking for a stable voltage file that will work with their phones in the thread, but it is def awesome for those that are familiar with what they are doing.
Click to expand...
Click to collapse
The whole ramdisk is here:
http://github.com/travistabbal/linux-galaxy/tree/ttabbal-v1.0/usr/initrd_files_t959/
The pre-init stuff is in /init.sh.
The basic stuff is the same as his really, I just put the sync hooks in to stall the boot based on an older version of his stuff. The current version didn't seem to work for me. The boot didn't wait, and I couldn't see any reason it would, so I just used the property setting style.
As I said, I haven't tried voodoo with it yet, but I don't see any reason it wouldn't work. You might want to pull the "exec /sbin/init" out if you want more pre-init scripts available, but other than that, it should work fine. A fair bit of the ramdisk came from your voodoo release, useful stuff in there.
If you see any issues with the init.d stuff, let me know and I'll look into them and if I can fix them, send a pull request over to Unhelpful.
Yeah, 3 hooks is overkill, but I figured there might be some use for them all. Most scripts can run in the "standard" hook and work just fine.
I kept the runtime OC/UV stuff just because it was more work to take it out. If you have a nice stable file, I'm happy to include it in the downloads as a default. I'm sure I could pull at least older versions from your github, I honestly haven't messed with it much beyond adding the 600Mhz step and seeing that the phone would use it. I honestly don't see much call for changing that stuff constantly at runtime, but it's nice for experimenting. If it crashes due to low voltage, just reboot and no harm done.
As I'm sure someone will ask, no I won't test it with voodoo. I can't, my phone has the extra NAND so it's not compatible with voodoo. When Beta5 comes out, I'll test it though.

I'm uploading a 1.1 now. The only big change is that I've fixed the backlight notification patch from Unhelpful's tree so it works with Vibrant now! Install the kernel, then copy lights.default.so to /system/lib/hw to get apps able to use it. Anything that can do LED notifications now turns on the button backlights instead.
See the other BLN threads for Q&A's, etc.. The big one, no, we can't flash/fade the LEDs. It would require changes to the binary firmware and nobody wants to try writing it.
http://www.tabbal.net/files/t959-ttabbal-v1.1.tar
http://www.tabbal.net/files/lights.default.so
This has been tested on my phone running Bionix 1.7 and worked with the MMS and GMail apps. I haven't tested the others.
Again, it's an Odin tar file. Put it in the PDA section and flash. If people ask for an update.zip, I'll put one together.
The warning above applies. This flashes a kernel, so it will overwrite whatever you have now. So if you have voodoo, disable it or add the voodoo script to init.d with an E prefix ie. "Evoodoo".

Thanks
I've been looking forward for a way to use the backlight buttons as notification since the phone came out and the idea was hatched a few days later. I'm admittedly new to all this so I have no idea what else this is capable of but I am VERY thankful for the button lights. Also there is another xda thread up with many replies and people offering up some rewards for making this work.

Can this be applied to eugenes froyo ?
Sent from my SGH-T959 using XDA App

dzeinz said:
I've been looking forward for a way to use the backlight buttons as notification since the phone came out and the idea was hatched a few days later. I'm admittedly new to all this so I have no idea what else this is capable of but I am VERY thankful for the button lights. Also there is another xda thread up with many replies and people offering up some rewards for making this work.
Click to expand...
Click to collapse
Rewards? Heh... I had no idea people were that interested in it. Hope it helps. My github has source, so I hope other kernel devs for vibrant add it.

skater991 said:
Can this be applied to eugenes froyo ?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Not sure. Froyo usually needs a different kernel. If JAC or KK kernels work, this one should. At worst, it will boot loop and you will have to flash a compatible kernel in download mode. So make sure you can get into download mode before trying it.

Thanks for this. It's working great, and I'm so glad to finally have backlight notifications.

Definitely would like an update.zip, just not comfortable doing it through odin...but I would love to have this
The cake is a lie!

metalfan78 said:
Definitely would like an update.zip, just not comfortable doing it through odin...but I would love to have this
Click to expand...
Click to collapse
Well, since you asked nicely.
http://www.tabbal.net/files/Kernel-ttabbal-v1.1.zip
MD5: 606a1ecaa934f97bd26f0bfb617b23b8
Tested just now via Clockwork. It even installs the library for you, so the button notification should work out of the box.
Running great for me on Bionix 1.9.1.

Wow...thanks, ill give it a go. So just flash through clockwork and good to go?
The cake is a lie!

metalfan78 said:
Wow...thanks, ill give it a go. So just flash through clockwork and good to go?
Click to expand...
Click to collapse
Yup.
Let me know what you think.

Is this ready for overclocking like JAC's OC/UV kernels? If so, any chance of posting a demo script for the OC/UV settings?
Also, can we add a user-script to enable AOSP bootanimation.zip files, or is support still commented out in this kernel?
Thanks for your time and hard work, cheers, =)

I have been wanting button notification since i got the phone. Can you choose which button lights up based on what the notification is?
for example menu = txt, home = missed call, etc....that would be awesome!

s0niqu3 said:
Is this ready for overclocking like JAC's OC/UV kernels? If so, any chance of posting a demo script for the OC/UV settings?
Also, can we add a user-script to enable AOSP bootanimation.zip files, or is support still commented out in this kernel?
Thanks for your time and hard work, cheers, =)
Click to expand...
Click to collapse
It's based on Unhelpful's way of doing OC/UV, you have to modify a file and push it to the phone to enable it, then set up the min/max settings with a script or SetCPU. There's a lot of detail over in Unhelpful's thread on the Captivate forum, so it's probably better to point you over there. They have scripts and such for it as well.
Not sure on the boot animation. I'll see if I can find it.

d_bot said:
I have been wanting button notification since i got the phone. Can you choose which button lights up based on what the notification is?
for example menu = txt, home = missed call, etc....that would be awesome!
Click to expand...
Click to collapse
That would be awesome, but it's not that complex. It's all of them for a notification. The Android API wouldn't really be able to deal with that level, but perhaps we could assign the buttons colors and use the color that the app requested? Maybe, but I'm not sure we can turn on just one of them from the code we have right now. The code looks to make a somewhat simple call that turns them all on at the same time. Hopefully as more people look into things, we will learn how to do stuff like that.

[Q] Help a total Nook/Android noob

Long story short: I bought my Nook to root it. I'm not a complete moron, but I'm a little overwhelmed by all of the options for modifying the Nook. I have tons of iOS experience since I have an iPhone business on the side, so I'm not afraid to mess around with something.
The problem is, the only Android device I've spent more than 20 minutes with is the Samsung Captivate, which was ridiculously easy to root and then unlock so I could sell it.
Other than that, not much Android experience.
I bought the Nook because I need a portable device to view documents and the occasional entertainment. I'm a pilot and instantly recognized the advantage of being able to take aviation publications with me everywhere, including the cockpit. I considered the iPad since I'm intimately familiar with iOS, but the cost was a little higher than I wanted to go.
So, here's what I need: a VERY stable Nook that can efficiently read PDF files, H.264 movies and still maintain respectable battery life. I will be heading overseas with less than dependable access to internet, so I need something that's pretty worry-free since I might not be able to worry with finding a fix online.
Where to start?
I've already rooted it using AutoNooter, but it seems wonky at best. The N button rarely works at all and SoftKeys isn't much help either. I currently haven't found a way to go "back" in the Market app, and still haven't figured out how to sign in on my YouTube account.
So, what are your suggestions for setup? Please be detailed with your suggestions and save the flaming for someone who cares.
Thanks!

I didn't like the stock rom either...
I went immdiatly to nookie froyo, which is the most stable rom other then stock.
You should try it.
You should also try cm7 and it varients, but those are less stable.
you can check out the tutorials on remapping the volume keys for back and menu, although I find soft keys a valiable option.

Can you point me to the best method of install for Froyo? Is it better on internal or keeping it on the SD card? I'm not worried about warranty or restoring the stock ROM, so which one is best overall?

LongbowFoSho said:
Can you point me to the best method of install for Froyo? Is it better on internal or keeping it on the SD card? I'm not worried about warranty or restoring the stock ROM, so which one is best overall?
Click to expand...
Click to collapse
Try it on the SD card first, just to start. If you screw up, you can just format the card and start over, it's relatively pain free that way. But it will run a little snappier on the actual Nook eMMC, but you can always do that later.
Another factor is that B&N will be updating all Nook Colors to Froyo in April. If you run off an SD card until then, then you can root the Nook after that update (with new Autonooter built for that new update), and you will have a more stable Froyo since it will be a professional kernel built for the hardware.
You'll need a Sandisk Class 4 or 6 uSD card or a Transcend Class 6 (unless you have already bought something, in which go ahead and try that card).
The build is at:
http://forum.xda-developers.com/showthread.php?t=922324

Yeah......about that "don't flash the internal memory" part.....
Everything went great until I rebooted and now its stuck at the Android screen with the flashing cursor.
Now I'm just trying to figure out how to restore it. Ugh.
I'm using a 32GB SanDisk SDHC Class 6 card, BTW.
EDIT: Well, I was able to get the build from your link running from the SD card, but all of the processes suddenly and continually fail. All I get is pop up after pop up about errors.
I'm done screwing around with this for today. If I can't get something usable by tomorrow night, I'm selling this POS and getting an iPad. This isn't worth it just to save $100.

I don't know what all you did to the internal memory, but chances are this will work to get back to stock.
http://nookdevs.com/Flash_back_to_clean_stock_ROM
If that doesn't work then
http://forum.xda-developers.com/showthread.php?t=945838
Softkeys works, and I use it, but it's...not intuitive...this page made things clear for me. Reading through this should get your n key working and whatnot.
http://nookdevs.com/NookColor_Default_Launcher
Disabling the service in the softkeys settings was good for me. That stupid little button was always in the wrong place no matter where I put it and wasn't useful anyhow. I also didn't install home switcher or whatever. If you get your n button set wrong, you can just clear the defaults from the app settings for whatever app is set to the n button.
Sounds like you got it rooted and everything, but here is a link for reference anyhow.
http://forum.xda-developers.com/showthread.php?t=942424
A note on those instructions: youtube did nothing but crash on me. The purpose of logging in with youtube is to get your device linked to your google account so you can get into the market. I didn't use youtube, i think i used gmail or the market itself or something. I don't remember. I just uninstalled youtube, you don't need it. Youtube video's still download and play in the default video player if you visit youtube.com from the web browser.
As far as your options for operating systems. I haven't used froyo, and haven't spent much time with honeycomb, so grain of salt and stuff. Plus it really depends on what you need/want.
Note: after booting a fresh burn for the first time, just walk away for five minutes. I'm not sure why (maybe something to do with the not quite jit doing it's thing?), but it will be more stable if you do.
Froyo gives flash and slightly better performance over stock. I think video is on par with stock, but it could be worse, i'm not sure. It's almost certainly not better. I can't speak for stability, as I haven't tried it. I think bluetooth is possible but not realistic? I know occip got the chip responding, but I haven't seen anything indicating it's useable. Links in previous posts so i won't make another.
Cyanogenmod gives all that froyo gives plus bluetooth support. Video framerate is poor (movies, not games and whatnot). Stability isn't as good as stock. Mostly it's fine but every once in a while things start force closing like mad and i have to reboot. Also battery life isn't good with cyanogenmod. Sleep has been disabled as there is a bug with it. It will still last over a day without a charge though. It's what i use day to day. Really amazing and fast moving. Seems like every day a new major bug is fixed or a whole new piece of hardware is working. Linkie:
http://forum.xda-developers.com/showthread.php?t=1000957
Honeycomb is really cool and it's amazing what deeperblue did (without much source omgwat?) but it's still kinda just a toy until google releases all the source code. No flash, no hardware accelerated video, no bluetooth, no reason to use it, other than aesthetics. Annoying ui glitches in portrait mode. Neat and worth an sd burn to play with, but not for using day to day in my opinion.
http://forum.xda-developers.com/showthread.php?t=936995
Of course there is no need to choose one! There are a couple option for multibooting in the forums and I intend to get around to combining a few to triple boot. Right now this is what I use:
http://forum.xda-developers.com/showthread.php?t=947698
I'm set up to boot rooted stock off internal memory and cm7 off of uSD
P.S. If you just want it to work and be a full tablet it might be worth the extra $150 or so for an IPad. The nook has been fantastically useful for my needs and I don't think i've had this much fun with a piece of kit since my first apple II. On the other hand I've wasted a fair number of hours reading about and "bricking" the thing so...ymmv depending on what your needs/wants are.

Hi, Im new here, too.
Id like to do this "Go back in Root Explorer, and in system/app, mount as r-w and rename Phone.apk and TelephonyProvider.apk to anything else (adding .bak onto the end would be fine)." But I can't change the permission...
Even I do habe only CWM 3.0.0.6 and like to have the newest one (3.0.1.0) and Iam using right now the Phirmod V5.1
Has anyone some hinds? Cheers

Can you elaborate on "can't change permissions"? Can you not find the option, or are you making the change and its not working?
For your clockwork upgrade question, is your recovery internal, or on a bootable SD?
Sent from my Nexus One using XDA Premium App

Thanks for the detailed response, ylixir. I'm attempting to go back to stock now and will definitely try your suggestions.
I'm still going to try Nookie since the general consensus is that it's the most stable. I don't care about BT or even Flash since I'll just be using this mostly for mobile document viewing in Afghanistan.
Thanks again and will update with my results.

chef123 said:
Hi, Im new here, too.
Id like to do this "Go back in Root Explorer, and in system/app, mount as r-w and rename Phone.apk and TelephonyProvider.apk to anything else (adding .bak onto the end would be fine)." But I can't change the permission...
Even I do habe only CWM 3.0.0.6 and like to have the newest one (3.0.1.0) and Iam using right now the Phirmod V5.1
Has anyone some hinds? Cheers
Click to expand...
Click to collapse
I know you're new and all, but generally its considered rude to jump into someone else's thread and ask your own question. You'll probably get a lot more visibility (and subsequently a solution to your problem) by making your own thread.
Thanks!

LongbowFoSho said:
I know you're new and all, but generally its considered rude to jump into someone else's thread and ask your own question. You'll probably get a lot more visibility (and subsequently a solution to your problem) by making your own thread.
Thanks!
Click to expand...
Click to collapse
Dude! The forum rules tell you to search and piggyback existing threads before making your own thread. The idea is that the closely related information is localized, and searching is made much more easier without having multiple threads on the same subject...
Sent from my Nexus One using XDA Premium App

Well, I've got it back to stock 1.1 now. I'm VERY happy to see that since I still might sell this thing if I can't make some headway with a usable ROM.

danger-rat said:
Dude! The forum rules tell you to search and piggyback existing threads before making your own thread. The idea is that the closely related information is localized, and searching is made much more easier without having multiple threads on the same subject...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Well, this is the first forum I've ever seen that operates that way.

Well, just tried running Froyo from the SD card and it just sits at the Android splash screen (the animated one). It also did this last night, but I thought it was because of the non-functional Froyo I had flashed internally.
I guess I'll give HC a shot to see if anything actually works on this device.

Just ran HC and although I finally got past the "decrypted data" error (after three re-images and flashing, no less), I dunno.
I'm going to try rooting the stock 1.1 again and see how that goes. If I can't get comfortable with that, then I'm done. I have better things to do besides sitting around for hours and hours trying to get something to be remotely practical for every day use.
If I wanted a tinkering project, I'd buy an old car.

Autonooker is super easy to get the stock ROM working as an Android tablet.
I'm sure it's stated on the wiki that Nookie Froyo and other ROMs are in development and not meant for stable systems.
Anyway, hope Autonooker works for you

Good news! Looks like perseverence pays off because rooting 1.1 seems to have worked perfectly this time.
I am fully signed in on YouTube and email, and all the buttons are working properly.
Now that I've finally gotten that out of the way, is there a way to OC the stock ROM? Its not really a need, just curious LOL. I've seen SetCPU mentioned a few times, but IIRC its intended for 2.2 and up only. Correct me if I'm wrong.
Also, best PDF reader for stock ROM?

chef123 said:
Hi, Im new here, too.
Id like to do this "Go back in Root Explorer, and in system/app, mount as r-w and rename Phone.apk and TelephonyProvider.apk to anything else (adding .bak onto the end would be fine)." But I can't change the permission...
Even I do habe only CWM 3.0.0.6 and like to have the newest one (3.0.1.0) and Iam using right now the Phirmod V5.1
Has anyone some hinds? Cheers
Click to expand...
Click to collapse
Get a Terminal Emulator from the Market. Now type in the following:
If running off SD
Code:
su
mount -o rw,remount /dev/block/mmcblk1p2 /system
If running off EMMC
Code:
su
mount -o rw,remount /dev/block/mmcblk0p5 /system
Hope this helps.
____________________________________________________
Sent from Nookie Froyo using Tapatalk

Everything I'm installing doesn't show up on the Extras page. If I want to open FB or Dolphin or something like that, I have to search for it.
A little help?

LongbowFoSho said:
Everything I'm installing doesn't show up on the Extras page. If I want to open FB or Dolphin or something like that, I have to search for it.
A little help?
Click to expand...
Click to collapse
Install a new launcher, such as Zeam, Launcher Pro, or ADW. I prefer Zeam myself. Then you'll be able to immediately see new apps you've installed.

[Q] Google+ on G1? Also I need a youtube.apk for G1

Hello. Well seems Google+ doesnt install to a G1... so anyone have a apk that would work for me to install it? Also my youtube for awhile has been messed up, I need to reinstall it, but dont have a apk or updated youtube apk for it if someone can point me in the right direction? Thanks. =)
(Over 2 years with my G1 and I have not had a desire to replace it yet, even tho I have higher end phones)

It doesn't? Please describe your problem in more detail, because I'm using it just fine, on the latest iteration of COS-DS.
Perhaps you need a more recent Android; if this is the case, having the apk would not help you much...

Same for me here, running G+ and YouTube, both installed from the market. Seems to me that these apps need a higher API-Level, i.e. Donut isn't supported.

Well I am still running my G1 on Enoms 1.6 build. Always worked best. So didnt change it. Granted Youtube.. Not sure WHAT happened. It just doesnt want to update the homescreen of it, getting like a parsing error on it. Thats why I am looking for that apk
As for G+ the market doesnt let me install it.
Love my G1 too much to replace it. G2 was a contender but that temp root thing turned me off.

Enom's roms were great, I liked them very much and I was using them until mid of last year. Unfortunately he stopped development and if you want to be up to date, you need to switch, and since Terry provided us with ezGingerbread, I switched to that. Performance / speed is comparable to Enom's roms and I am on the lastest Android version

Thats a great review. I may have to do that... Trick is, I worry.. I have over 100 apps installed heh. While I can download them to my PC. Just not sure what else would wipe. Or do you need to wipe for that upgrade?

Unfortunately yes, ... no chance to keep apps / data. Ok, TitaniumBackup may be an option, contacts and calander come from google, but it's still a bit of work to do.
In addition to that you would probably like to upgrade to the 1.33.0013d/2.22.28.25 combo to gain 14MB of available RAM(!), which will cause additional work and risks(?) ...

I'd have to say that as a user with over 150+ apps and no desire to trim the fat I'm very shortly back off to E-Xtreme and danger spl with 26I radio as nothing ever came close to being as good on my phone for me above 1.6 (Hell I'm even thinking of dropping back to Super D 1.9.3 with DarkStars theme if I can find it, that black google search box with the ghoshed white outer glow always was the sexiest thing ever lol) because if your a user from my experience with a load of apps and have a lot of home screens with shortcuts and widgets then Froyo and especially gingerbread just ain't for you plain and simple. I kill them all in minutes and I'm not exactly a beginner at this stuff, by no means an expert either but I know enough to know that me and gingerbread will never work and well for some of us thats just how it is.

Heh yea, same here. I love my G1 even tho its about 3 years old. 1.6 is fine for my everyday use. My HD2 tho.. just found the <3 Android I was looking for.
http://forum.xda-developers.com/showthread.php?t=957652 (Along with WM 6.5)
But then back to the main issue at hand. I need the Youtube apk for the G1 =/ Would be nice to least be able to use that again heh.

see maybe i will met

No one knows how to redo Youtube or fix it? =/

Here's a link to the Youtube.apk file. It's version 2.1.6.
http://www.mediafire.com/?rpet4zusa17xucb