Not the scripts causing the FC. You didn't add the required library to the /system/lib folder
yep :-) that's right...
that apk really should be removed from the rom.
will be removed within the next release.
After having R3b running for most of the day, the phone started to re-boot or after the screen turned off it wouldn't wake up again, taking the battery out was the only solution. I tried to reflash after wiping everything, but it looped after the re-booting once I'd installed from the recovery mode. I wiped everything again and successfully installed, however, during the configuration of the google account I got this message :- android.process.acore has stopped unexpectedly
Hmm..I'm running r3b on my pulse too at the moment. Hadn't had these issues yet but will see if it occurs again. Sorry for that!
hi bit of a newbie great work on the rom it looks great i tried to upgrade to r3b (ive been using r3) and when its loaded i get a message about core cant remember all the message and also when i upgrade do i follow all the instructions or do i just flash the rom (i just flashed r3b without wiping data)-(not keen on the menu)
also got that core message once
. As it didn't come back then, I ignored it.
One request, is it possible it make the pattern lock screen bigger ?
Hmm I don't know in which APK the pattern lock is stored. Anyone knows? By modifying it, we could make it larger perhaps.Again some hints
if you should run into problems:
- If changing the microsd card, use the recovery partioning tool. I tried partitioning using gparted and linux, but that caused many FCs.
- To have a full fresh install, partion the sd card (all data on it will be lost), wipe data/factory rest, wipe dalvik-cache
- Then copy the rom over to the sd card again and flash it.
If you still encounter problems then, I am sorry for that. Maybe someone finds fixes for these problems.
Or stick with the original rom. But I bet you won't
Or try mikes rom...!