[ROM] Rumm Rx v1.0 - First dose of awesomeness ;)

[Steady Hawkin]

For those afraid of the update it works fine without it just did it at work and no problems. Just my two cents for what its worth

Have you been able to flash back to a non leaked nandroid?

 

[castxaway]

For those afraid of the update it works fine without it just did it at work and no problems. Just my two cents for what its worth

Have you been able to flash back to a non leaked nandroid?

No, don't try it. You will probably brick.

 

[Droid74]

For those afraid of the update it works fine without it just did it at work and no problems. Just my two cents for what its worth

Have you been able to flash back to a non leaked nandroid?

There is no flashing back once you install the leak...sorry.

 

[djdlite512]

Hey, for those having PowerAMP issues, you can fix this by removing (or commenting out) a few lines in the build.prop. They're towards the end. They are:

debug.mot.extwmlog=1
debug.mot.extamlog=1

ro.kernel.android.checkjni=1

Sorry for the newbieness, but how do you do that?

Probably easier just to do this:

Download the build.prop.txt file I attached to this post. Remove the .txt appended (had to do this to let the forum let me attach) and place the build.prop file on your sdcard.

Then, in terminal emulator:

su
sysrw
busybox cp /sdcard/build.prop /system/
reboot

and your PowerAMP should work after the reboot.


The other method would be to edit the existing build.prop, which is located in /system

You'll need something like root explorer to do it, or you can pull the file, edit on your computer, and push it back on.

BEAUTIFUL! That got it going! Thanks guy!

 

[Aixelsyd]

For those afraid of the update it works fine without it just did it at work and no problems. Just my two cents for what its worth

Have you been able to flash back to a non leaked nandroid?

No, don't try it. You will probably brick.

Exactly, that is a bad bad plan

 

[djdlite512]

Here's a fix for the FC's that occur when trying to add a new calendar event:

1. Download BlurEmailEngine.apk to your sdcard.

3. Copy BlurEmailEngine.apk to /system/app (this will require making /system/app writable. In Root Explorer just press the R/W key when you're exploring /system/app).

4. You now need to change the app's permissions. In Root Explorer, long press on the app (in /system/app) and click on "permissions". Then make sure that only the following boxes are clicked: User Read, User Write, Group Read, Others Read.

5. Make sure you make /system/app read only again by clicking that box in the top right while you're exploring the folder.

6. Reboot phone.

You can now add new calendar events without getting FC's.

Still force closing...followed all the steps.

 

[Steady Hawkin]

Forgive me if I am a complete idiot, but I thought he was saying he flashed the rom without flashing the leak file on the first page?

 

[humungus]

Here's a fix for the FC's that occur when trying to add a new calendar event:

1. Download BlurEmailEngine.apk to your sdcard.

3. Copy BlurEmailEngine.apk to /system/app (this will require making /system/app writable. In Root Explorer just press the R/W key when you're exploring /system/app).

4. You now need to change the app's permissions. In Root Explorer, long press on the app (in /system/app) and click on "permissions". Then make sure that only the following boxes are clicked: User Read, User Write, Group Read, Others Read.

5. Make sure you make /system/app read only again by clicking that box in the top right while you're exploring the folder.

6. Reboot phone.

You can now add new calendar events without getting FC's.

Still force closing...followed all the steps.

This should work. I actually installed Rumm RX, checked that new events in calendar FC'd, and then installed bluremailengine to verify the fix before posting. This is the same problem that Tranquility ran up against before switching to the AOSP calendar, and I noticed it in my own debloating efforts, so I'm almost certain that this is the cause of the problem.

Check to see if the emailengine is in /system/app, and check permissions again. To verify whether it installed or not click on it and try to install it. It should, I believe, say "Replace Application" or something like that if it's installed. If it's not installed, it won't say "Replace." Also, you rebooted, right?

 

[molivas37]

Have you been able to flash back to a non leaked nandroid?

No, don't try it. You will probably brick.

Exactly, that is a bad bad plan

Don't try Flashing back or don't try installing without the leak? LOL I think i confused myself reading this....

 

[millbean]

Installed per instructions running very smoothly at ulv 1.25 was just wondering if something went haywire could I just flashback to my Rubix backup with no problems ? can't wait til a black bar themes hits this bad boy! Great rom

You can only flash back to a nandroid that was running on the leak. Flashing back to a nandroid that is not on the TBH leak will likely leave you with a very expensive paper weight.

Sent from my DROIDX using Tapatalk

so no going back to rubix or.fission after flashing this? Not sure or how to tell if they are based on the leak?

 

[Droid74]

Installed per instructions running very smoothly at ulv 1.25 was just wondering if something went haywire could I just flashback to my Rubix backup with no problems ? can't wait til a black bar themes hits this bad boy! Great rom

You can only flash back to a nandroid that was running on the leak. Flashing back to a nandroid that is not on the TBH leak will likely leave you with a very expensive paper weight.

Sent from my DROIDX using Tapatalk

so no going back to rubix or.fission after flashing this? Not sure or how to tell if they are based on the leak?

Rubix has 2 versions based on this leak you can install...one that is blurry and one that is blurr-less. I dont know about fission.

 

[djdlite512]

Here's a fix for the FC's that occur when trying to add a new calendar event:

1. Download BlurEmailEngine.apk to your sdcard.

3. Copy BlurEmailEngine.apk to /system/app (this will require making /system/app writable. In Root Explorer just press the R/W key when you're exploring /system/app).

4. You now need to change the app's permissions. In Root Explorer, long press on the app (in /system/app) and click on "permissions". Then make sure that only the following boxes are clicked: User Read, User Write, Group Read, Others Read.

5. Make sure you make /system/app read only again by clicking that box in the top right while you're exploring the folder.

6. Reboot phone.

You can now add new calendar events without getting FC's.

Still force closing...followed all the steps.

This should work. I actually installed Rumm RX, checked that new events in calendar FC'd, and then installed bluremailengine to verify the fix before posting. This is the same problem that Tranquility ran up against before switching to the AOSP calendar, and I noticed it in my own debloating efforts, so I'm almost certain that this is the cause of the problem.

Check to see if the emailengine is in /system/app, and check permissions again. To verify whether it installed or not click on it and try to install it. It should, I believe, say "Replace Application" or something like that if it's installed. If it's not installed, it won't say "Replace." Also, you rebooted, right?

Made a booboo and copied the zip file....hehe. I'm good to go now dude! Thanks!

 

[brandegy]

Force Close on Dialer lcd density

Any eta on the fc on the dialer when using lcd density. LOVE 190 density. But will be patient LOVE THE ROM. PURE Greatnessdancedroid:icon_ banana:

 

[WACOMalt]

I cant seem to flash the stock animations from the toolbox, I get a failed to flash animations error.

Also on restoring stock M logo I get something like logo not found.

EDIT: and more: dialer is closing on me. I am on 190 density.

This seems like an awesome rom, but it still has it's issues.

 

[brandegy]

EDIT: and more: dialer is closing on me. I am on 190 density.

This seems like an awesome rom, but it still has it's issues.

The FC on the Dialer is known just awaiting a fix for it.