Guys Preview 5 has been released over at XDA.......[7.03.11][ROM] BAMF Sense 3.0 GB RC4 - Page 117 - xda-developers Page 117 Post 1167....again flash at your own risk, not responsible for your phone becoming anything other then a phone!!!!
I just wiped cache partition and Dalvik cache, and flashed over RC4 without any issues. YMMV, of course.
Tried to resist, but the lure of even a preview is too great.
This one fixes the string errors in the lock screens, which is nice. Plus, a new kernel is included.[/QUOTE
It's tempting
Tried to resist, but the lure of even a preview is too great.
This one fixes the string errors in the lock screens, which is nice. Plus, a new kernel is included.[/QUOTE
It's tempting
Also fixes the Applications screen. No more crazy flashing numbers when you try to manage your apps. This alone is worth it.
Edit: Using ##778# to access the phone's system menu works now. Didn't work with RC3 & 4.
time to nandroid and flash lol
I tried waiting but to not flash a bamf ROM is like leaving a million dollars in the room and not take some money for myself
I've encountered force closes with Google Music on the last couple of release candidates. Clearing app data and cache, reinstalling, and fixing permissions hasn't helped.
Anyone else encounter this?
I've encountered force closes with Google Music on the last couple of release candidates. Clearing app data and cache, reinstalling, and fixing permissions hasn't helped.
Anyone else encounter this?
Am I the only one with realllly laggy performance with this ROM? It takes about 10 minutes after it boots to stabilize. It;s as if my phone can't handle sense 3.0
in the toolkit under cpu settings I overclock to 1.2 to make the rom run a little quicker, I also keep my minimum setting at 368 to reduce lag when waking and bc i use the phone a bunch with the screen off.
I was at 245 and 1.4 I'll try a higher minimum setting. Which governor do you use. I don't know the difference between smartass and interactiveX
i had music beta freeze a couple of times while using rc4, but it was rare and after the fc and reopen the app everything was ok again. Never needed a real fix or looked for one.
btw i also haven't needed to run fix permissions at all on rc4. did run it on all the earlier previews i tried (havent tried pre5 yet) and release candidates 1-3.