rubiX Focused 1.9.5

[afripino]

Ok...Noob Alert!



I'm on RubiX 1.8.6, System Version 2.3.20. What do I need to do to update to 2.3.340? Really trying to upgrade to 1.9.5

Thanks!

 

[cpjr]

What is the easiest way to get your apps back in place with all your data after moving to this ROM?

I thought I read someplace that even with USER apps, you shouldn't restore APP+DATA from TitaniumBackup, but should just choose APP. Is this true? If so, what could happen if you restore both?

I understand that system apps shouldn't be restored because they can cause problems.



Also, I am noticing the issue previously mentioned where the SCREEN display timeout is now apparently tied to the keypin timeout, where they were separate before. This is also a bother for me because while I appreciate a 1 minute timeout on my screen, having to re-enter my pin every single time gets a bit grating. I don't believe I was able to find out, based on the previous discussion in this thread, if there was a way around this.

Also, my video camera does not work. FC when I switch to video, and blank pictures taken with the camera itself. I'm just about to wipe/reset everything and apply it again.

And finally, I notice that scripts are included. But I've never run a script before on the phone and wondered what the general method and commands were for running these scripts? Thank you.

I haven't been able to restore apps with Titanium since I went on .340. The phone just reboots. It appears to make backups on schedule, only they are no good. When I was able to use Titanium, I restored apps + data so I didn't have to re-enter everything. Since this behavior happened on 3 different .340 ROMS, I switched to MyBackupPro and it restores without a hitch.

GummyJAR, and therefore RubiX 1.95, did not keep the ability to set the lockscreen timeout. This is somewhat of a bummer.

This has been stated many times before, but Titanium backup screws things up....dont use it.

 

[cpjr]

Ok...Noob Alert!



I'm on RubiX 1.8.6, System Version 2.3.20. What do I need to do to update to 2.3.340? Really trying to upgrade to 1.9.5

Thanks!

There are several threads on here about updating if you search. There is also info in this thread if you search. Your gonna have to sbf and update first if your using a custom ROM...or OTA update if your stock, then load Rubix.

 

[akiles]

That's what I told her :icon_ banana:

I know it is smaller but you do get used to it.
Marc

 

[mcp770]

What is the easiest way to get your apps back in place with all your data after moving to this ROM?

I thought I read someplace that even with USER apps, you shouldn't restore APP+DATA from TitaniumBackup, but should just choose APP. Is this true? If so, what could happen if you restore both?

I understand that system apps shouldn't be restored because they can cause problems.



Also, I am noticing the issue previously mentioned where the SCREEN display timeout is now apparently tied to the keypin timeout, where they were separate before. This is also a bother for me because while I appreciate a 1 minute timeout on my screen, having to re-enter my pin every single time gets a bit grating. I don't believe I was able to find out, based on the previous discussion in this thread, if there was a way around this.

Also, my video camera does not work. FC when I switch to video, and blank pictures taken with the camera itself. I'm just about to wipe/reset everything and apply it again.

And finally, I notice that scripts are included. But I've never run a script before on the phone and wondered what the general method and commands were for running these scripts? Thank you.

I haven't been able to restore apps with Titanium since I went on .340. The phone just reboots. It appears to make backups on schedule, only they are no good. When I was able to use Titanium, I restored apps + data so I didn't have to re-enter everything. Since this behavior happened on 3 different .340 ROMS, I switched to MyBackupPro and it restores without a hitch.

GummyJAR, and therefore RubiX 1.95, did not keep the ability to set the lockscreen timeout. This is somewhat of a bummer.

This has been stated many times before, but Titanium backup screws things up....dont use it.

Titanium works fine for me, restored several apps without issue. It just updated to 340 support so you may try it.

 

[sephtin]

You mean the application permissions?
QuickOffice has permissions to everything but "Network communication".

If it helps, here is how I installed quick office:
1.- copied /data/rubix/quickoffice.bak
2.- navigated to /system/app/ and mounted folder as rw
3.- pasted quickoffice.bak in /system/app
4.- renamed quickoffice.bak to quickoffice.apk
4.1.- I can't remember if I ran quickoffice.apk first...
5.- after a reboot, quickoffice is working ok.

I think you want to make sure the permissions are correct if you follow the above.. (??).

I meant file permissions. As in, read,write, and executable. It needs to be
User: R,W
Group: R
Other: R
Permissions in /system/app. If it's not, it probably won't work correctly.

 

[sephtin]

Can anyone post the original themed keyboard. I know it is smaller but you do get used to it. Were there any other reasons it got pulled besides the size?

Thanks

Marc

Dang, Akiles beat me to it!

How was it pulled? If you load the themed version, it should still be there?
I believe it's also still there in the patch I listed to go from plain to themed... ??

(I DID however remove it from ROM Manager, if you choose the Themed version from ROM Manager, it's not there.)

 

[sephtin]

Ok...Noob Alert!

I'm on RubiX 1.8.6, System Version 2.3.20. What do I need to do to update to 2.3.340? Really trying to upgrade to 1.9.5

Thanks!

As previously stated, you'll need to get back to a clean 2.3.15, and take the OTA update to get to 2.3.340... then re-root (z4root works great for this), load droidxbootstrapper, and then load Focused again.

That should do it!

 

[akiles]

Yes, quickoffice.apk is set as rw--r--r. Hopefuly that's the same order you stated below so that the permissions match (user, group, other). So far Office is working ok. I think I may have attempted to run quickoffice.apk after I moved it. I do remember that the installation went ok, but I could not see the app in the drawer until after a rebot.
Thanks, Septh.

You mean the application permissions?
QuickOffice has permissions to everything but "Network communication".

I think you want to make sure the permissions are correct if you follow the above.. (??).

I meant file permissions. As in, read,write, and executable. It needs to be
User: R,W
Group: R
Other: R
Permissions in /system/app. If it's not, it probably won't work correctly.

 

[akiles]

Answer: Carefully.

Lol, sorry, I could not resist. I'm having too much fun with this thread. I'll stop now before a forum moderator bans me.

 

[Inkarnit]

Yes, quickoffice.apk is set as rw--r--r. Hopefuly that's the same order you stated below so that the permissions match (user, group, other). So far Office is working ok. I think I may have attempted to run quickoffice.apk after I moved it. I do remember that the installation went ok, but I could not see the app in the drawer until after a rebot.
Thanks, Septh.

You mean the application permissions?
QuickOffice has permissions to everything but "Network communication".

I meant file permissions. As in, read,write, and executable. It needs to be
User: R,W
Group: R
Other: R
Permissions in /system/app. If it's not, it probably won't work correctly.

Regarding QuickOffice... there's an easier way to get that working than manually adjusting things. If you copy the .bak file into your /system/apps folder then run the script, it takes care of everything for you. The script works, it just requires a QuickOffice.bak file be in /system/apps first.

Edit: Correct command to run once QuickOffice.bak is copied to /system/apps is in terminal emulator type office -rs

 

[Kuonji]

GummyJAR, and therefore RubiX 1.95, did not keep the ability to set the lockscreen timeout. This is somewhat of a bummer.

Is there any way this can be adjusted somehow with a patch or whatnot? I think at least a few of us would be forever grateful if this was possible.

 

[Jordan8]

GummyJAR, and therefore RubiX 1.95, did not keep the ability to set the lockscreen timeout. This is somewhat of a bummer.

Is there any way this can be adjusted somehow with a patch or whatnot? I think at least a few of us would be forever grateful if this was possible.

I agree, I had to remove my lock because of this. :/

Sent from my DROIDX using DroidForums App

 

[drod2169]

GummyJAR, and therefore RubiX 1.95, did not keep the ability to set the lockscreen timeout. This is somewhat of a bummer.

Is there any way this can be adjusted somehow with a patch or whatnot? I think at least a few of us would be forever grateful if this was possible.

No.. unfortunately there were more asking for it off then on. In AOSP there isn't a timer, and i'm guessing people weren't used to there being a timer and considered it a "bug". This isn't a feature I use (and I'm sure Kejar neither, the one who was able to remove it) so I didn't even notice it. It was a good amount of framework work to be done. If it were patched in, there wouldn't be any themes you could use other than whatever it comes with without bootlooping.

 

[akiles]

I knew there was a script for it, but I couldn't find it mainly because I did not know where to look -or what the command for the script was.
But since you are sharing, could you tell me where the script is at? -I did a search in the entire / but could not find anything. Then again, I did not really know what to look for...

Yes, quickoffice.apk is set as rw--r--r. Hopefuly that's the same order you stated below so that the permissions match (user, group, other). So far Office is working ok. I think I may have attempted to run quickoffice.apk after I moved it. I do remember that the installation went ok, but I could not see the app in the drawer until after a rebot.
Thanks, Septh.

I meant file permissions. As in, read,write, and executable. It needs to be
User: R,W
Group: R
Other: R
Permissions in /system/app. If it's not, it probably won't work correctly.

Regarding QuickOffice... there's an easier way to get that working than manually adjusting things. If you copy the .bak file into your /system/apps folder then run the script, it takes care of everything for you. The script works, it just requires a QuickOffice.bak file be in /system/apps first.

Edit: Correct command to run once QuickOffice.bak is copied to /system/apps is in terminal emulator type office -rs