this is a kernel that i compiled direct from toast's HTC-Supersonic-2.6.29 source. toast and netarchy all put in their fixes and enhancements so i take no credit but altering the kernel that netarchy posted in this http://forum.xda-developers.com/showthread.php?t=719763 thread.
this is based off his 3.7.1 kernel that enables around 55-57 fps on both epson and novatek screens. Like he said, it disables the HDMI so if you need that, don't use this. in fact, this kernel will have all the issues that netarchy's 3.6.2 might have, but the touchscreen does work and you should still get ~55 fps average on fps2d.
this means that the kernel also comes with overclock and undervolt, compcache modules, audio boost and everything.
the kernel that's included is only compatible with ClockworkMod recoveries, sorry for those who use Amon_RA! i can't seem to make a working boot.img, and koush's way of updating kernels also is a lot easier to use
i highly highly doubt this has the possibility to break your phone but if it somehow does, i don't take responsibility.
once again, all credit goes to netarchy, toast, and all other people who i may have missed.
if you're using this kernel and get around 40 or so frames per second, here's probably the best thing to do. go to setCPU into the Advanced tab, and set the Up threshold to a value between 65-75. I chose 65 and i consistently get 55-57 average with stdev of 4 or 5.
edit: i just compiled a new kernel straight from Netarchy's sources, as he says that he updates his to the latest at all times. so, the new version is 3.6.4, because that's what his is. remember, this is exactly the same as his kernel, except that i just modified something to make it work for Froyo ROMs.
enjoy!!
edit: wifi does work, i think it's just that for some people who are flashing it over a ROM it might not work. I re-flashed evolution v9 and wi-fi worked again
using amon ra 1.7.0.1 i got
E: Missing file:
system/lib/modules/bcm4329.ko
E: verification failed
Installation aborted
this DOES NOT work.... but thanks for playing
scooter185 said:
using amon ra 1.7.0.1 i got
E: Missing file:
system/lib/modules/bcm4329.ko
E: verification failed
Installation aborted
Click to expand...
Click to collapse
yeah i doubt it works on amon ra, cause it's something made for clockworkmod. could you flash clockworkmod and then try this kernel, and tell me if it works?
btw, the bcm4329 appears because i found a kernel that i could use so i just replaced the zImage inside it. the original one was supposed to put the bcm4329 in /system/lib but i took it out cause it wasn't necessary.
will this work on the froyo sense rom?
infamousjax said:
this DOES NOT work.... but thanks for playing
Click to expand...
Click to collapse
could you please explain a bit more what's not working?
http://www.failhorn.com/
Wow... brutal guys.
look, guys.
i'm not trying to trick you guys. why don't you guys tell me what's wrong instead of telling me "fail" and giving me some stupid crap like failhorn.com
it works 100% fine on my phone, running EVOlaunchv9 froyo. so why don't you tell me what's not working and NOT be douches about it?
Douches.
Thanks for making this, man. I've been waiting for this kernel to support Froyo. Works great so far. Only thing is Wifi Tether isn't working, despite trying to reflash the fix from ffolkes thread. Might have something to do with clockwork recovery, though.
warmthsound said:
Douches.
Thanks for making this, man. I've been waiting for this kernel to support Froyo. Works great so far. Only thing is Wifi Tether isn't working, despite trying to reflash the fix from ffolkes thread. Might have something to do with clockwork recovery, though.
Click to expand...
Click to collapse
thanks. yeah i just noticed that wifi in general isn't working... and i can't figure it out. there might be something else i missed... but i'll keep looking.
thanks I'll load this up later when I flash my froyo build again.
justinisyoung said:
thanks. yeah i just noticed that wifi in general isn't working... and i can't figure it out. there might be something else i missed... but i'll keep looking.
Click to expand...
Click to collapse
Can you not use that patch that is in the Nova FPS kernel thread for the 802.11 N and 4G. Just a thought, when I flashed to the kernel in that thread I lost my wireless too and then i flashed that patch and it started working again. I am new to this game, sounds logical to me lol.
Worked great on my phone, running Damage Control's newest. The only thing is that I had 5 points of touch with the kernel just for the novatek screen and 44fps. With this kernel I only had 3 points of touch and only 41fps. Still good work, dont let those other guys get you down. Thanks
Noticed this is based off 3.6.2
Maybe the wifi problem will go away if 3.6.3 is used instead. Looks like the audio boost patch was removed as it was causing problems with bluetooth, and no fluffy pink bunnies were harmed in the making of 3.6.3 so its peta approved
I had 5 touch points using Dotty on ffolkes kernel.. Only got two with this one.
Sent using the power of swype.
good god there are some real ******** on this board as of late !
op thx for the work when i flash a 2.2 ill give it a shot
Way to show this Guy support you tools!!!!!!!!
tried it running evolution v9. everything worked great except for wifi which was already stated. appreciate the work you've done. thx
when i get home from work i'll see if i can build the kernel again. it might be 3.6.3-based if netarchy and toast updated the kernel source on github, but otherwise we'll be stuck with this one till they do so.
sorry about the wifi guys, i spent a few hours and i could not get it to work. but if you flash the wifi/4g fix on ffolkes's kernel's page (the link is on the first post), you'll get wifi tether working at least
Related
AOSP 2.3 has been released and this thread is now useless
If you wanna follow our work with aosp 2.3.1 for dream/sapphire :
Source Code Repo for Gingerbread (Dream and Sapphire builds)
Compiled builds
MODs bootanimation, superuser, terminal emulator, live wall papers support, google apps, market 2.2.7, etc...
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Since people were asking for it, here is a quick port for the G1
Thanks and credits goes to :
-pershoot using his kernel boot-cm_2635.9_ds_32b_radio2708-oc-uv-xtra-ram-fp-120810
-seo using mostly his port for magic as base
I'm currently using the 14MB ram hack with radio 2.22.28.25 & hboot 1.33.0013d with CM6.1
If you are not you need to follow these steps first : 2708+ enabled kernel [14MB ram with radio 2.22.27.08/2.22.28.25 & hboot 1.33.0013d]
OR
you can always try to flash a non 2708 kernel from pershoot like boot-cm_2635.9_ds_32b-oc-uv-xtra-ram-fp-120810 after flashing this ROM but I have'nt tested it myself.
working : data/radio but like all other ports no mic
not working : mostly everything
seo has wifi working on magic, I'm looking into his wpa_supplicant.exec script but changing wlan.ko and driver did'nt worked.
For wiping I suggest using Ohsaka SuperWipe as the update script does'nt wipe /data partition.
Download link : here
Nice, I'll flash it shortly
Nice!!
3G connection(Magic 32B) is working!
can some one post some pics please
Unassigned file limit of 10 downloads reached.
Click to expand...
Click to collapse
would flash it, but i need a mirror
flashed it but no notifications bar? lol
bypass23 thanks your hard work
flashed already,It runs slowly...
no wifi
no BT
can not set time&date
but i believe 2.3 will come to G1 and work great
flashed, works, but sloooow, as expected
well, restoring previous rom
reiga said:
would flash it, but i need a mirror
Click to expand...
Click to collapse
updated download link sorry
komeup said:
can some one post some pics please
Click to expand...
Click to collapse
I added some, nothing special but enjoy
I've got a problem,
I nand backuped my phone, wiped, flashed 2.3, wiped, and nand restored my previous backup, and now my HOME and CALL button is not working, when I press them, no response
do you have any ideas what could it cause? how to fix this?
ra100x said:
I've got a problem,
I nand backuped my phone, wiped, flashed 2.3, wiped, and nand restored my previous backup, and now my HOME and CALL button is not working, when I press them, no response
do you have any ideas what could it cause? how to fix this?
Click to expand...
Click to collapse
I just did a SuperWipe + nand restore to CM6.1 and both HOME and CALL buttons are working properly.
I just added a link for Ohsaka's SuperWipe in the OP, use it to wipe before doing your restore. (needs to be flashed)
bypass23 said:
I just did a SuperWipe + nand restore to CM6.1 and both HOME and CALL buttons are working properly.
I just added a link for Ohsaka's SuperWipe in the OP, use it to wipe before doing your restore. (needs to be flashed)
Click to expand...
Click to collapse
thanks, but I wiped it with Ohsaka SuperWipe, before and after 2.3, I don't understand, I'll try it again, but I'll try to fix_permissions first, don't think it could have something with my issue, but it's worth trying
and one more thing, my PC now doesn't recognize my phone as USB device, will try something and post results
ra100x said:
thanks, but I wiped it with Ohsaka SuperWipe, before and after 2.3, I don't understand, I'll try it again, but I'll try to fix_permissions first, don't think it could have something with my issue, but it's worth trying
and one more thing, my PC now doesn't recognize my phone as USB device, will try something and post results
Click to expand...
Click to collapse
Flash a stock ROM? It's probably a good idea to make a new thread for your issue tbh, since it's not really that relevant to the ROM.
AdrianK said:
Flash a stock ROM? It's probably a good idea to make a new thread for your issue tbh, since it's not really that relevant to the ROM.
Click to expand...
Click to collapse
problem solved, flashed Biffmod 2.1, then nand restore, buttons work fine
can someone delete my lame problem?
You just some-what single-handedly saved the G1 from dying out. Mine was stolen a while ago, but I still check back on this Thread and I'm so happy you took the time to Port the ROM. Great job my friend.
Maybe these GApps will help: http://bit.ly/fyOUMI
Got it from: http://forum.xda-developers.com/showthread.php?t=864403
Wow, thunderspeed!Nice Work!
But wondering when would Milestone XT702 got one
Lol lucky y'all... Got ginger bread before us G2 folks
Sent from my HTC Vision using XDA App
I flashed it ,it's slowly....and can not change time setting`` it is not perfect````and now just need to wait for the new 2.3 rom for G1 and wish it more better....
Original Android <3ers! said:
You just some-what single-handedly saved the G1 from dying out. Mine was stolen a while ago, but I still check back on this Thread and I'm so happy you took the time to Port the ROM. Great job my friend.
Click to expand...
Click to collapse
It sounds more like it's on life support, and a lot of people (mainly developers) wanna pull the plug. To them, the G1 phones are nothing but a waste of time, when compared to a lot of the newer phones on the market.
The reality though, it isn't much different then a lot of new phones on the market. I gotta have a hardware keyboard, and that limits me to the myTouch 3G Slide, and the G2. Frankly, the Slide is essentially the same thing as my G1, with lots more memory, and a better camera. My friend replaced his G1 with the Cliq, and he thought it was an upgrade, but didn't understand why Angry Birds was still slow?
So long as there's App2SD applications, over priced phones, and smart coders, the G1 lives on.
I Know this should be in the Developer section, but I don't have enough posts. (Since you have to have at least 10 to do so...)
BUT, I installed a kernel from Blades which is the 1.6ghz with the latest version of CWM. The problem is that whenever I try to boot up the device it just stays on the first startup screen, and it also makes a weird popping noise from the speakers about every 10 seconds. I did wipe Dalvik Cache and I also made a back up before installing the new kernel. I've tried restoring but it does the same thing every time. Before installing the kernel I was running PRIMEORDIAL! v3.1...
Any help would be greatly appreciated....
Thanks
cdp
Hi Mate, You are not the only one. Unfortuantely 3.0.1 kernels don't work too well with 3.1 roms as you have discovered.
Not to worry though as this is an easy fix.
Simply flash the 3.1 stock kernel and you're up and running again. You can get it from here... http://forum.xda-developers.com/showpost.php?p=14283676&postcount=94
Wow, I didn't even realize that kernel was only for 3.0.1 lol. THANK YOU! Flashed it and it started right up! C:
You may now have wifi problems, since the kernel update will have installed a different module to the one you need, if this is the case just reflash whatever rom you are using.
Okay cool, I'm on wifi now and it seems to be working fine. So thanks again! :]
Some of the user's here, myself included, have been having issues installing any ROMs/ kernels built by Faux. What I'm trying to do is pinpoint the exact cause of this and hopefully rectify the issue.
I'm currently downloading all available ROMs and will install each to determine which are flashable and which are not.
Flashing Procedures
0. Boot into CMW Recovery: External with EXT 4 support using volume down + power method
1. Wipe Data
2. Wipe Cache
3. Wipe Dalvik
4. Format /System
5. Flash ROM
6. Select Power Down from CMW Menu
7. Power on phone without wall charger plugged in
ROM List:
Bionix- Confirmed as working
EagleBlood GB- Confirmed as working
EagleBlood FR- Confirmed as working
Ultimate- Confirmed as working
Light&Sinister- Confirmed as working
Dark&Sinister- Confirmed as working
Faux AOSP-NOW WORKING!!
CM7- Confirmed as working
LG Stock- Confirmed as working
Observations:
Bionix converts /system and /data to ext3. I figured that if the issue we were having with Faux was due to format errors then I could just flash Faux over Bionix and it would boot. In testing, it seems like Faux gets further when flashed this way but still refuses to boot. Before I would only get the initial LG screen and then it would black out. Now I can get to the second LG screen with blue background but it hangs there. Will run logcat to see what is causing the freeze once I get logcat running again.
My current theory is that there is a difference in the boot.img that Faux has built for his ROM that will not boot correctly. I have the same issue with his kernels as well. They boot to the first LG splash screen and then the screen shuts off. Still struggling with my logcat issue so I'm at a standstill until that is fixed.
Development:
I was finally able to get pure AOSP to boot by flashing Faux's AOSP and then flashing Morfic's CM7 kernel. I personally believe this definitely proves that there is something in Faux's boot.img that doesn't function properly on all devices.
At Faux's suggestion, I flashed his Stock Voltage kernels in order to see if I could get the phone to boot.
Kernel:
[ Start @ 1.0 GHz, Stock Voltage, Max @ 1.2 GHz ]
(Official LGE/Tegra Voltage Values, Same as STOCK LGE Kernel)
CM7 Kernel Version 0.1.9- Boots to second LG splash screen then freezes.
CM7 Kernel Version 0.1.9 With EXT4-Booted fine but still displayed Morfic boot animation for some reason. Kernel version shows as Faux's in about phone, though.
I want to flash my first ROM, any suggestions on which one is the most stable and better with battery life than the Stock ROM?
Mikeglongo said:
I want to flash my first ROM, any suggestions on which one is the most stable and better with battery life than the Stock ROM?
Click to expand...
Click to collapse
I didn't test any of the ROMs for quality but I would personally stick with a Froyo based ROM for now. Gingerbread is simply too buggy and missing a lot of features.
[B][U]SUCCESS!!![/U][/B]
I was finally able to get pure AOSP to boot by flashing Faux's AOSP and then flashing Trinity's CM7 kernel. I personally believe this definitely prooves that there is something in Faux's boot.img that doesn't function properly on all devices. That would explain why I am unable to flash any of his kernels, either.
Most likely scenario is that you have a "weaker" chip which cannot handle the default OC to 1.1 and Under volting. Because of your case and a few others like you with the "weaker" chips, I have decided from next version on to include LG STOCK VOLTAGE version of my kernel as default kernel for the ROM and it's up to the users to install the OC/UV version themselves afterwards.
My solution is while in CWM, after you flashed the ROM, before you reboot, FLASH my STOCK VOLTAGE (SV) version of the kernel, then reboot. You should have NO ISSUES with STOCK VOLTAGE kernels.
So far for MT4G and G2x, I have been lucky with my phones. Both phones I can Undervolt and overclock AT the SAME TIME with very aggressive settings and remain stable with multiple runs of stress tests and benchmarks.
faux123 said:
Most likely scenario is that you have a "weaker" chip which cannot handle the default OC to 1.1 and Under volting. Because of your case and a few others like you with the "weaker" chips, I have decided from next version on to include LG STOCK VOLTAGE version of my kernel as default kernel for the ROM and it's up to the users to install the OC/UV version themselves afterwards.
My solution is while in CWM, after you flashed the ROM, before you reboot, FLASH my STOCK VOLTAGE (SV) version of the kernel, then reboot. You should have NO ISSUES with STOCK VOLTAGE kernels.
So far for MT4G and G2x, I have been lucky with my phones. Both phones I can Undervolt and overclock AT the SAME TIME with very aggressive settings and remain stable with multiple runs of stress tests and benchmarks.
Click to expand...
Click to collapse
The only problem with that theory, Faux, is that Morfic's kernel undervolts as well. Flashing his kernel on top of your ROM is the current workaround that I've found.
hiko36 said:
The only problem with that theory, Faux, is that Morfic's kernel undervolts as well. Flashing his kernel on top of your ROM is the current workaround that I've found.
Click to expand...
Click to collapse
I don't know what Morphic is doing with his under volting, theres no source code to compare. My source is based on CM7 with my tweaks added and its available via github for inspection.
faux123 said:
I don't know what Morphic is doing with his under volting, theres no source code to compare. My source is based on CM7 with my tweaks added and its available via github for inspection.
Click to expand...
Click to collapse
Please don't view my opinions as doubting your ability. This has just been a frustrating journey for a lot of us because we want to use your kernels/ROMs. I couldn't find anywhere where this had been addressed so I decided to take it upon myself. At this time, the two options we have are flashing your stock voltage kernel or Morfic's. Now that it's booted and running, I can say that you've built a beautiful ROM and I hope you continue to support it. Amazing work.
hiko36 said:
Please don't view my opinions as doubting your ability. This has just been a frustrating journey for a lot of us because we want to use your kernels/ROMs. I couldn't find anywhere where this had been addressed so I decided to take it upon myself. At this time, the two options we have are flashing your stock voltage kernel or Morfic's. Now that it's booted and running, I can say that you've built a beautiful ROM and I hope you continue to support it. Amazing work.
Click to expand...
Click to collapse
I took NO offense of your investigation or posts. I am actually glad you did all these. You have provided me reason for using stock voltage kernel as default. I was contemplating about this change a while back, but since your post, I decided to do it so more people can try my ROM without having random reboots or issues due to UV/OC combination.
I am simply posting what I can and cannot do. I can do only what I can read and see.
faux123 said:
I took NO offense of your investigation or posts. I am actually glad you did all these. You have provided me reason for using stock voltage kernel as default. I was contemplating about this change a while back, but since your post, I decided to do it so more people can try my ROM without having random reboots or issues due to UV/OC combination.
I am simply posting what I can and cannot do. I can do only what I can read and see.
Click to expand...
Click to collapse
Glad I could help and especially glad I finally figured out a way to boot your ROM. I was feeling left out haha.
Doh! He said rectify lol
Sent from my Xoom using XDA Premium App
Hello android gurus/deities (too much?),
Just got my first smartphone, a Droid Charge. Great phone, especially for the price. The screen is freaking fantastic and of course Android is amazing as ever.
However, since first activating it, I seem to get random crashes. I can't replicate the problem, since it doesn't seem connected to anything visual. First time it happened when I decided to check out the camera, took a picture, and tried to view it. Other times have been the first time trying out netflix, first time sending a text. Seems to happen the first time I use some apps.
The crash basically consists of a short 5-10 second freeze followed by a reboot. Any ideas? Is this a hardware issue I need to have addressed or more likely a software issue that I just need to wait for updates to come along and fix it? Or is this a common occurence with Android and I just need to suck it up? lol
Edit: Has also happened 3 or 4 times while browsing the web, including this site...
charges hardware are pretty great for the price the software is a big issue for the charge whitch is why most of us myself included suggest rooting your device whitch literally a dummy could do using odin... i am running a stock based of a leak called infinity rom pretty amazing for a stockish rom for now so reboots are known at least for me but i really think the majority of the problem for this phone is the software gps loss signal going in and out as in data (this is a hit and miss) ..... hope this helped you iron things out...
Out of curiosity, what will rooting my device accomplish with respect to the reboots? Anything?
I rooted the device, then tried infinityROM but ran into so many problems I flashed back to the factory rom X(... Rooted again, but still get reboots, any ideas?
Where can I get a more solid kernel? From reading around it sounds like that "might" solve the reboots :\
RevTorA said:
Where can I get a more solid kernel? From reading around it sounds like that "might" solve the reboots :\
Click to expand...
Click to collapse
http://rootzwiki.com/topic/4847-guide-new-users-guide-everything-how-to-root-rom-kernels-radios-cwm/
Also depends what rom you are running.
If it keeps happening after you root and flash a new kernel (and maybe install a rom) upload a logcat to a filesharing place and hop on IRC to ask for help.
irc.andirc.net
#charge
Port 6666
Sent from my SCH-I510 using xda premium
Thanks... once that site's back up I'll download a the kernel from there... The kernel on that page should work my Charge if it's currently the factory rom right?
Edit: Just to check, Imoseyon's kernel (listed here is the only available kernel aside from the factory kernel? I should try flashing this to see if it fixes my problem? Where can I get the factory kernel (just the kernel :\) if things go awry?
Edit2: Also found imnut's PBJT kernel here. I'm unaware of some of the terminologies (I've only messed with a couple Ubuntu/Fedora distros of linux), can this and any other kernel for the Charge work with Gingerbread (2.3.6)?
RevTorA said:
Thanks... once that site's back up I'll download a the kernel from there... The kernel on that page should work my Charge if it's currently the factory rom right?
Edit: Just to check, Imoseyon's kernel (listed here is the only available kernel aside from the factory kernel? I should try flashing this to see if it fixes my problem? Where can I get the factory kernel (just the kernel :\) if things go awry?
Edit2: Also found imnut's PBJT kernel here. I'm unaware of some of the terminologies (I've only messed with a couple Ubuntu/Fedora distros of linux), can this and any other kernel for the Charge work with Gingerbread (2.3.6)?
Click to expand...
Click to collapse
PBJ is a Froyo kernel. It will only work with Froyo.
Help me out im unsure which one is better, as in everything works on it good battery life, least amount of bugs.
http://forum.xda-developers.com/showthread.php?t=1334493
lite^^
http://forum.xda-developers.com/showthread.php?t=1241073
crack^^
I personally have nothing but random reboots/bootloops on all of "UndeadK9's" ROMs. Some ppl say this as well, others swear its the most stable ROM out there.
MT4GS Lite 1.2.3 is going to be extremely stable... But Bulletproof uses the same ROM base and its awesome with stability and battery life with newly implemented UV/OC kernels.
Very active/ helpful dev who knows his stuff on Bulletproof.
Not trying to tell u Lite won't be stable, but bulletproof will b just as/ if not more stable and battery life will prob b better.
Just my spare change.
I recommend Bulletproof. However I dislike the green hue, so I just copied and pasted all the apk's I wished to replace from Lite.
Some of the rom threads in the dev group are freakin massive(random) any way... thinking about trying out bulletproof im reading good things, but right on the newly updated thread it seems to say s-on may be a problem.
Can somebody clarify if im using the fast boot method to flash a new boot.img prior to flashing a new rom, should i worry about not having s-off?
Side note when if at all should i be wiping the data prior to flashing a new rom?
Out of those two I suggest Rubix expresso 1.3 over on Rootz. It is the final iteration of Crack Injected. It is my go to ROM when I want to get back from the bleeding edge and go to software that just works. I have links to it on the Rootz threaad as the other links are dead. Flash 1.2 then 1.3 to get set.
It is very close to Bulletproof but it's tweaked slightly in a couple of places. Bulletproof is great too.
Sent from my RubiX CubeD Extreme MT4GS using Tapatalk
I have a problem with bulletproof 1.1 wifi keeps disconnecting and eventually disables itself. Not sure where i went wrong with the installation if i did. Reinstalled twice, did a full wipe but wifi wouldnt work.
cybot_x1024 said:
I have a problem with bulletproof 1.1 wifi keeps disconnecting and eventually disables itself. Not sure where i went wrong with the installation if i did. Reinstalled twice, did a full wipe but wifi wouldnt work.
Click to expand...
Click to collapse
Is that with the included Kernel?
Hastily spouted for your befuddlement.
Coug76 said:
Is that with the included Kernel?
Hastily spouted for your befuddlement.
Click to expand...
Click to collapse
The rom is actually fine. False alarm. I screwed up some proxy settings so it wouldn't work, but it works now. Sorry
Sent from my Bulletproof_Doubleshot using XDA
OneNawlige said:
Some of the rom threads in the dev group are freakin massive(random) any way... thinking about trying out bulletproof im reading good things, but right on the newly updated thread it seems to say s-on may be a problem.
Can somebody clarify if im using the fast boot method to flash a new boot.img prior to flashing a new rom, should i worry about not having s-off?
Side note when if at all should i be wiping the data prior to flashing a new rom?
Click to expand...
Click to collapse
Nope, s-on (unlocked) is no problem. Now that I was able to figure out how to set one of my doubleshots back to S-ON and then unlock it through HTC, i'm running fine and you should have no issues.
I will be supplying a new kernel for bulletproof when I get a chance to update the ROM again, meantime it's still the stock kernel in it but with an insecure boot image.
If you have issues right after flashing (wifi doesn't work) then you'll have to flash the kernel separately through fastboot, but again, for S-ON unlocked this is no problem.
----
You should always wipe your data and cache between ROMs, but on bulletproof (and any script i've ever released, actually) I handle all that for you so you can just flash and go.
I just think it's just good coding practice for the developer to take care of this step instead of leaving it up to the chance of the user not doing it.