yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] VeryCoolAlan:
Hey do you have a link to loopysmooth file? Would like to insert it into a nother rom
[Vibrant Android Development] Evil Avnovice:
Cool. Thank you.
[Vibrant Android Development] Leafy_duk:
No dice man. It must be the undervolt. When you get a chance if you could upload that, that would be killer. No rush, the ROM sounds awesome though. I need to get better at this android stuff so that I could just swap out the bali kernel myself.
[Vibrant Android Development] lotherius:
http://xdaforums.com/showthread.php?t=1205744

Some customization necessary, to put the name of your launcher in the file. .. plus it needs to run near the end of your scripts, read the thread and it will tell all :)

upload was ALMOST done and I realized it wasn't the signed file... *sigh* another hour... my bad.
[Vibrant Android Development] Leafy_duk:
No worries. I just had a great idea in the shower. Flash your rom and then flash a non-UV version of Bali right over it.
[Vibrant Android Development] lotherius:
Let me know if that works! You'll need to use Bali 1.8.8 and not Bali-X as Bali-X would look for the kernel config file and apply it.
[Vibrant Android Development] Leafy_duk:
well I accidentally copied bali 1.8.6 onto my phone and not 1.8.8 and it seems to be working flawlessly so far.

What would be nice would be GB swype and a choice of normal text. But you have a life and stuff so if it doesnt happen for a while I can deal. I guess I should get a log in for swype beta anyways.
[Vibrant Android Development] lotherius:
1.8.6 is fine. If it's working for you, then that settles it, the undervolt was too much for your phone. I will put up the stock voltage version anyway for anyone who has problems with undervolting.

Swype is a gray area... Generally if you include the version of Swype that came with the ROM it is okay, but if you want to include the Swype Beta, that's a TOS violation and they do sometimes enforce that... Plus, if you want to install the latest Swype Beta with the installer, it won't work if Swype's already baked into the ROM... thus I left off Swype to make it easier to download/install the official Beta.
[Vibrant Android Development] devine might:
It would be perfect if there was a moe'ed theme:D
[Vibrant Android Development] lotherius:
Been thinking about it.... :)... I wanted to get the technical aspects down first. Did you check the default ringtone? From Haruhi Suzumiya ;)
[Vibrant Android Development] Leafy_duk:
I guess swype beta wasnt the swype I wanted. Theres one that puts the auto correct options on the top fo the keyboard like the GB keyboard does, AND it doesnt automatically add a word to the dictionary. Oh well.
[Vibrant Android Development] crazyald:
Does this have Juwe's Memory Script?
[Vibrant Android Development] duboi97:
This has been running great :)

I'm recalibrating the battery over night and sees how that goes...I've hardly noticed any bugs. But once my phone vibrated for a hella long time and then I had to reboot don't know why that happened.
[Vibrant Android Development] lotherius:
It has parts of it - it does change the minfree settings which are the biggest boosts in that department. I plan on more work on the scripts in the future.

If you have any further problems, try disabling the undervolting with Voltage Control. Run the app and select "remove boot settings" from the menu.
[Vibrant Android Development] duboi97:
I've never been a fan of Bali (only on CM lol) so I'm running SuperDragonModz with no UV only OC to 1.2 GHZ with smartass governor...but as I said this ROM is great. Pretty stable and has great battery life. I love the stock Galaxy S 4g live wallpaper. I think I might run this as my daily driver once school starts up next week.
[Vibrant Android Development] lotherius:
Glad at least one person likes it :)...

Did it as a learning experience. I really am committed to keeping it as lean and mean as possible. I really hate when I load a ROM that's be de-bloated only to find the developer has re-bloated it with all their favorite apps, most of which are out of date by the time I flash and have to be updated on the market anyway.
[Vibrant Android Development] 啊喔鹅咦呜鱼:
backlight cannot be solved?

i dont like the touchkey light at night:(
[Vibrant Android Development] lotherius:
Nobody has come up with a solution to disable the soft button lights :(.... I would love to disable them myself.

On an unrelated note... Just thought I'd share this, in case anybody thought ROM editing was easy!

Uploaded with ImageShack.us

This is what you stare at 90% of the time when you're tweaking ROMs... It's called Smali... and it sucks...
[Vibrant Android Development] maoten:
Sir!

suppose i want to add arabic patch to your rom?
[Vibrant Android Development] lotherius:
There's not an easy way to do it. I'll look at adding other languages but from what I've seen it requires some extensive work on all of the system files... not at the top of the list.
[Vibrant Android Development] crazyald:
Love this rom a lot. It's smooth and very snappy.

Only issue is the gallery. Instead of showing the latest pictures first it shows the earliest ones. But it's no biggie

Good job for your first rom btw. I'll be expecting more from you!!
[Vibrant Android Development] Leafy_duk:
The launcher is super snappy but all of my apps seem very laggy. Any ideas?

I'm going to try inserting readable fonts into the rom tomorrow.
[Vibrant Android Development] JediDru:
Great work man. My only gripe is the font is very difficult for me to read. I changed it but upon reboot it was back to "stock". Does that have something to do with the apps being installed to SD? Once I changed the font some apps when opened where still rocking the stock font. I don't recall ever having that situation before. Well thanks for all the effort and keep up the good work.
[Vibrant Android Development] nirogu325:
Use QuickPic, it's on the market. Way better/faster than Gallery.
[Vibrant Android Development] maoten:
can't i use any from other roms? or should be on KD1 as well?

2nd: for the installing on SD issue,,, you mean SD of phone or external SD?

thanks
[Desire Q&A, Help & Troubleshooting] suryclarsen:
Hello!

Here are some details:

BRAVO PVT4 SHIP S-ON

HBOOT 0.93.0001

MICORP-051d

RADIO 5.09.05.30_C

I'm rooted, and was running the latest version of Oxygen (as of a few days ago).

I did a search, but couldn't find anything.

So here is my problem: a few days ago my phone, after installing the latest version of Oxygen, I noticed my phone was shutting down after prolonged use. I thought it was because of overheating, caused by an overclocking problem or something.

Now, however, it won't get past the white loading screen with HTC on it. I can hold volume down and get into HBOOT, but as soon as I select recovery, the same white HTC screen shows up. The screen stays there until I have to remove the battery. It never boots up, and I cannot get into recovery.

I have tried:

Clearing storage from the HBOOT menu

Reflashing Clockwordmod (however, I realized you have to be S-Off to do this, and I can't find any methods that allow me to S-Off from within HBOOT or Fastboot (which is all I can get into)).

The phone is recognized via ADB when in Fastboot, but I don't know where to go from there.

Any help or suggestions would be greatly appreciated. Like I said, I did a fruitless search, but if this question has already been answered, a link would be fantastic as well. Thank you for your time!
[Desire Q&A, Help & Troubleshooting] Bouncer5:
If you boot into your HBOOT and then fastboot, You can use the revolutionary tool, to gain S-OFF from there, At the end of it, it shall even ask if you wan to install Clockworkmod, and it is 4.0.1. instead of the offical 2.5.0.7.

New features :o
[Desire Q&A, Help & Troubleshooting] suryclarsen:
I'm running the Revolutionary tool, and it's stuck at "Waiting for device..."

My phone is in Fastboot, connected via USB, and I've downloaded and installed the HTC Desire Fastboot drivers. It's showing all OK in device manager, but the revolutionary .exe won't see it. Am I doing something wrong?
[Desire Q&A, Help & Troubleshooting] Bouncer5:
I wouldnt say you were doing anything wrong, Just the phone seems a tad more broken than it looks
[Desire Q&A, Help & Troubleshooting] andQlimax:
http://wiki.rootzwiki.com/index.php/HTC_Desire
[Desire Q&A, Help & Troubleshooting] suryclarsen:
I'm following those directions 100%, but it looks like the revolutionary tool won't see my device. Are you sure it can s-off while in Fastboot?

I have no idea where to go from here - I have a useless phone that won't even go into recovery. More help would be amazing.
[Desire Q&A, Help & Troubleshooting] sm_rasmy:
IWAS HAVING THE SAME PROPLEM

thats wat i did

u can down load this file

update :: I cant put the link :S

google for PB99IMG.zip

Download it

if the name wasnt exact match rename it to PB99IMG.zip

and pull ur sd card put it in card reader

then copy it into sd card root folder

then put the memory back into the phone

press vol down and power

then relase

it will autumatic setup the stok RUU of ur HTC desire

that will remove the rooting and make ur phone brand new

N.P if the instalation didt sucess and said CID incorrect

then u need

gold card

make ur gold card then put the files in ur gold card put it in the phone and enter boot menu

instaltion will sucess this time

worked for me :)
[Nook Color General] ShotSkydiver:
Am I doing something wrong, or is this just what everyone's used to? The nook color is horrible for using for, well, anything, even when I first bought it the rom was laggy and sluggish. Rooted and wiped full, tried Honeycomb, CM7, MIUI, all overclocked to 1.2Ghz, and they're all just terribly slow. I had to return my first NC due to a yellow screen, and the replacement is rooted and on CM7 right now. Simple things like scrolling through a list of apps or contacts causes the nook to think I'm tapping on the contact rather than starting to scroll, pressing back in an app hangs forever until I press it again and then it registers both back presses and goes back twice, dragging widgets is nearly impossible due to the device being horrible with recognizing a drag, every animation, app drawer, slide, touch, drag, is painfully and horribly slow.

Again, this is the exact same experience I've had over two completely different new nook colors, with multiple different ROMs, including stock and overclocked. Please, tell me I'm doing something wrong, I hate this nook more than anything in life right now and I want to fix that.
[Nook Color General] zequav:
Well, the NC is not the fastest android device around, but with the latest CM7 nightly, at 1.2GHz, 32 bit framebuffer disabled in Nook Tweaks and some decently optimized/accelerated apps (ADW EX instead of whatever other launcher, Opera instead of any other non-accelerated browser, Mobo for videos, etc.) it's mostly silky smooth.

I say mostly because there are some things that could be smoother, like scrolling through lists (I wish they could stop the GC from freeing memory when scrolling once and for all) and some apps that are quite slow, like ES File Explorer (also related to the GC), but otherwise it's perfectly fine to use. I have an HTC Desire and I do notice that the Desire is slightly smoother in some areas (or much smoother when srcolling through lists), but the NC is not far behind for everyday use.
[Nook Color General] DiDGR8:
I would say that your experience is not typical. The only problem that some (but not all) people have reported that your problem resembles is touch screen problems reported when using the NC will the charger plugged in.

You MIGHT be having trouble with lots of static electricity due to dry Phoenix air and A/C use. It's a shot in the dark.

You'd probably need to try to reproduce the problem for somebody to observe. I have seen some really weird PEBKAC problems that took a fresh set of eyes to troubleshoot.
[Nook Color General] darkmatter34:
I'm on phiremod. I have a few issues with it (mainly apps that I've loaded disappearing). Right now I'm going to leave well enough alone until ice cream sandwich.

With ics, we'll have the aosp (since its also for phones), and its designed to work with 7" screen and with software buttons. ICS will give us a fantastic and stable nook color (I'm only guessing though, lol)
[Nook Color General] biohazrd51:
No issues here. I've been running 7.1RC for a while not and have no experienced anything like you say you have. True it can get sluggish at times, but never for an extended amount of time that has made it unusable.

When I used to run the old 7.0.2 stable, I noticed that having a fair amount of widgets running could cause the system to slow down. But even now with a few widgets, about 12 icons per page, and rotating wallpapers using three total pages, I use it daily and have no issues.
[Nook Color General] ponyboy82:
I have to admit I found CM7 pretty laggy before I started using the OC kernel. It's super easy now with it built into the nightlies, and it made a huge different in scrolling, etc.
[Nook Color General] yelloguy:
That is not typical at all. I wouldn't be using (and loving) mine if it were. I am using CM7 nightly on emmc and it is a fantastic piece of work! Very responsive for what I do even without overclocking. Your experience is bad even on the stock OS so maybe it is bad hardware?

Just for kicks, I tried HC on a SanDisk 4GB class 4 card. And it is a little sluggish like you described. But not as bad and still very usable. I went back to CM7 because it is so much more responsive.
[Nook Color General] ponyboy82:
Ok, to be fair, when I say CM7 was laggy, I mean it wasn't super-silky-smooth like it is after overclocking a bit. I don't have a lot to compare to aside from a fairly new android phone (Thunderbolt). I did try a Honeycomb preview build first and that was a frustrating experience (laggy, stuff didn't work), but it was one of the earlier *preview* builds. CM7 with tablet tweaks is awesome.
[Nook Color General] DillonBladez:
To be honest, I never thought I'd register an account on XDA. Seems like theres too many pros for the noobs to fit in. Although the XDA noob video did give me some laughs.

To the OP:

Have you switched over from an Apple device? I previously had an iPhone 3g, and then a 3gs. When I switched to the Xperia X10 I thought either it was me, or the x10 was seriously messed up. It seems like it was me. I think the reason is that to scroll on the iPhone, all you need is a tiny little swiping motion to move between screens. However, it's not the case with Android phones. I found that your swiping gestures need to be a little bigger, otherwise, it's recognized as a click/tap/whatever.

I got used to it, however, I did find that installing a custom rom (CM7) helped a little.

edit:

Also, make sure you use advanced task killer or something to get rid of stuff in the background. **** running in the background Makes it slow. If it's rooted, try SetCPU and have it so that it's not ondemand, but on performance. Or, adjust the sliders until the minimum and maximum CPU speed is the same, making it run full speed all the time (Although I recommend having it set to the minimum while the screen is off.)
[Nook Color General] swaaye:
Apparently a major cause of the sluggishness in the scrolling of various apps and things such as form lists is due to the OS's garbage collector going nuts and trying to free memory in rapid succession. No ROM available for Nook Color solves this as it's some sort of flaw with Android 2.x itself. I don't know if Honeycomb (3.x) is better but I'm guessing that it is. Honeycomb will probably never be available in source form so Nook Color will never get it in proper form. Supposedly Android 4 (Ice Cream Sandwich) will be released in source, but we're talking a ways off and I'm unsure of how well it will fit Nook Color's hardware.

But yeah Nook Color is very slow compared to say a notebook. The CPU is an Arm Cortex A8 which is very low power, but also very simplistic compared with desktop/notebook CPUs. This is a necessity with a handheld device. However, the newer tablets with the NVIDIA Tegra 2 SoC (for example) use a Cortex A9 dual core where each core is much superior to the Nook's CPU and it has two of them.

Nook Color is a cheap entry level tablet with a nice screen but it has a ton of quirks because in modded form it is a community project with limited resources behind it.
[Nook Color General] selection16:
OP, are you installing to an sd card? Maybe the card is unsuitable (quite common problem). I actually underclock mine, installed to the internal drive. Sometimes I get a menu scroll registering as a tap, but I get that on any touch device I've tried. Overall a properly tuned nook runs pretty snappy imo.
[Nook Color General] ncmt4g64:
What he said^^ are you running off SD card? I tried that at first and absolutely hated it, it was soo slow ESP. Scrolling through the interface and app drawer. I have since put phiremod 6.3 on my emc and saw a huge improvement and I'm only at 800mhz. Then I tried the v6 supercharger script and again saw an improvement in scrolling speeds and smoothness. If I OC then its very snappy! You may also try to recalibrate the screen if you are finding its not super sensitive which it is.
[Nook Color General] DillonBladez:
Oh yeah, there's also that possibility.

I don't have a nook but I've been reading up about it.

Shouldn't you have a class 4 microSD card or higher for it to run decently well?
[Nook Color General] Imbroglio:
Random block write speed is the most important thing. Sandisk 8 and 16 gig class 4 have the best performance suited to running a SD based CM7. Other brands even in class 6 or 10 have been found to be too slow and resulted in force closes and sluggish responding apps.
[Nook Color General] ShotSkydiver:
Nope, I'm not running it off an SD card. I think the screen issue is a problem with my nook itself; installing a drawing app and trying to draw never gives me a full line, and drawing in some places is just impossible.

As for the slowness... I must be doing something wrong then, because both my nooks have just been horrible.
[Nook Color General] irisclara:
That's certainly not my experience. I'm running CM7 nightly 151 off sd and I can scroll through my app drawer or through long file lists very smoothly. A simple flick moves easily through hundreds of thumbnails. The only lag I ever experience is changing web pages. Maybe I'm biased because my main computer is a netbook but I really don't think the nook is at all slow.
[Nook Color General] koopakid08:
Do not EVER use a task killer!! This is android 2.3 not 1.5. Task killers screw everything up. Android Handel's itself and apps that task killers say are running in the background are NOT really running they are cached for quicker use. Android is smart, its Linex not windows. Also do not have your CPU going full speed 24/7. Ever heard what heat does to electronics? Its not pretty.

To op:

What version of cm7 are you using? Try a recent nightly.
[Nook Color General] Taosaur:
I have to say I had touch response issues like "ghost taps" more often in the first month I had the NC, but they were never a constant thing, and usually resolved by turning the screen off for a second and back on. I haven't had any such issues in quite a while, though I do occasionally have to repeat a tap on the softkeys.

If you haven't, you should track down the touchscreen calibration app for the NC and see if it helps. Some people say a screen protector helped even out their touch response, too. The NC's touch response is not the greatest in general, but your issues sound extreme.
[Nook Color General] ncmt4g64:
If your finger can't make solid lines in canvas or Sketchbook try recalibrating the screen using nsr (I think its called nook screen recalibrate in the market) otherwise LCD density? Any ideas anyone?

As for ghost taps I used to have that and you know what fixed it? Either cleaning the screen all.day or a screen protector. Since the screen protector I haven't had ghost taps or the zoom in zoom out craziness that the tap of the power button fixed.

OP: try an install to eMMC its quite simple if you make a cwr bootable card to install it with
[Nook Color General] fattire:
To save you a search, it's here.
[Nook Color General] life64x:
How many apps do you have installed? If you have a gazillion apps, you will bring the nook to a crawl. No matter what device of android, to many will choke the system. On mine I have just what I need. The only multiple apps I have are video apps. Moboplayer, vplayer etc..

With just what I need, the nook screams.
[Nook Color General] DillonBladez:
Sorry, if some of my information was wrong. My experience on 2.1 and 2.2 on my Desire required the use of an App killer, maybe 2.3 is different.

And I do know what heat will do to your electronic device, which is why I also recommended underclocking it to the minimum whenever the screen is off. But if you use your device for long periods of time, running the processor at it's fastest speed is obviously not the way to go.

Edit: if there is an undervolt kernel, that could be useful for both battery life and hardware longevity
[Nook Color General] patruns:
The stock NC runs at 800. The CM7 CPU settings allow you to set the clock as low as 300. Not really sure what else you need.
[Nook Color General] Moshe5368:
Not sure what is going on with your nooks. I cannot reproduce any of the issues you describe. I will, however suggest the following:

NO APP KILLERS they cause more problems than they solve

Use the latest nightly buind of 7.1rc1

Do not, repeat, do not use setcpu. It is not compatable with cm7

Ensure you have a clean screen. Phantom touch is one result. I find the nook screen to be very responsive if you keep it clean (use a good non-glare screen protector).

After you have the latest nightly loaded, download nook tweeks. There are settings there that will help you set up your clockspeed to make the nook very fast. Also download the screen calibration app discussed previously.

If you still have issues, PM me and I will try to help you get the performance you want out of your nook. I attach a screen shot of my quadrant scores for compairison.
[Nook Color General] khaytsus:
I suspect the OP either has a very dirty screen, very dry fingers, is using his NC while plugged in, or is trolling. Or all of the above?
[Nook Color General] :
The touch screen isn't the best...especially in the corners but its nowhere near as horrible as you've described, especially after overclocking. There are a few quirks that I have found though:

- The stock ADW launcher is pretty laggy when its comes to the App drawer. I recommend installing another launcher from the marketplace. I personally use ADW EX and its much smoother.

- The touch screen going haywire when the device is charging is a known issue.

- Try the different governor settings available. Maybe try the performance setting?

- Isn't designed for video playback so anything higher than 480p isn't going to play very well.
[Nook Color General] nickmv:
The only real problem I've noticed that bothers me is when I'm trying to move/manipulate widgets. It seems like trying to hold down on them to get them to move is impossible sometimes., esp if theyre near the edge of the screen. Anyone else encounter this?

Other than that, for $120 newly used w/ a nice case, I can't complain about this awesome tablet.

EDIT: I just thought of one more thing, and I think this is a software or overclock issue. Sometimes when I launch an app, it'll start, and act like it's about to do something, then the screen just goes black. I can still see my soft buttons, etc, but the app is just a black screen. This has happened w/ Pandora, Opera, and XDA app so far. Anyone else?

EDIT 2: I just ran the screen re-calibration tool from the Market and it significantly improved my problem with moving items on the homescreens. Now, if I can just figure out this black screen problem. I have to kill the app in order to get it to work again, sometimes I even have to clear its data.