-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root getting multitasking for sense 5 help
- Thread starter Rush
- Start date
-
- Tags
- htc evo 4g lte
CapThrowback
Android Expert
Just grab the SystemUI from svn for the commit before I added Horizontal QS. You'll lose those but get back the Sense Recent Apps. I wasn't expecting to lose it either, so I understand what you're saying.Hey, Cap...
The Sense5 multitasking isn't available for this Rom, right? Not a big problem, but it just look a lot more refine (IMO) than the ICS version.
Now -- I'm just kicking back waiting on Zoe to be finalized.
As far as Zoe, having it will mean you lose something else. The HTC Share feature in Gallery is still pretty cool without it, though.
Rush
{<>}~{<>}
Yes, the share feature is way cool. And as far as getting something [awesome] means losing something ...then hey, sacrifice sometimes happen.
Just to explain a little more clearly to those 'who don't fully understand' exactly what that means ... speaking for my not so tech savvy members. {Wink Wink}
CapThrowback
Android Expert
Replace the SystemUI currently in the ROM with this one: https://jewel-jb-4-1-2-sense5.googlecode.com/svn-history/r7/trunk/system/app/SystemUI.apkYes, the share feature is way cool. And as far as getting something [awesome] means losing something ...then hey, sacrifice sometimes happen.
Just to explain a little more clearly to those 'who don't fully understand' exactly what that means ... speaking for my not so tech savvy members. {Wink Wink}
Rush
{<>}~{<>}
Aww, that's what I'm talking about. My not so tech savvy friend told me to say, Thanks a lot.
Rush
{<>}~{<>}
I'm having problems getting this done!
Easier said than done, I guess.
EDIT - oops, this is the SystemUI, duh. See Captain's post a few down from here.
EStrongs File Explorer, enable root access, enable read/write for /system.
Find existing file in /system/app, rename to SystemUI.apk.bak
Copy new file to same place.
Change permissions to rw-r--r--
Reboot required.
I do the following whenever tinkering with system apps -
Go to recovery, wipe cache and Dalvik, then fix permissions.
Probably isn't needed most of the time.
Make it a habit and you'll be less likely to get bit.
PS - If unhappy, the original is there as a backup, the bak file.
Personal preference, I never change rom payloads.
I keep a folder on my SD card for each rom and each mod applied to it so I don't have to remember what I have or what I've done to it.
Sure, you can do all of this through adb and a PC. Once you're there that's the fastest way if you're comfortable with a command line.
Sometimes I do. More often I'd have to get up, move my coffee and me over to the desk where all of my actual work pages are open along with whatever I've been tinkering on lately. Distraction City, USA.
The phone is a PC so I stay strictly on it whenever possible.
You can do all of this in the Terminal Emulator on the phone.
But for general advice, I always suggest EStrongs and graphical methods.
Our lurker to poster ratio here is about 10 to 1, and that advice seems safest.
CapThrowback
Android Expert
FYI - I usually just Mount system in TWRP and do all these types of operations there using the File Manager (under Advanced). It's pretty easy and you don't have to worry about ROM force closures.
Also wiping caches isn't really necessary as the system will detect an APK change and rebuild dalvik for the necessary app. Fixing permissions also does nothing useful (there's a G+ post about that somewhere by Steve Kondik of CM fame, I believe).
Also wiping caches isn't really necessary as the system will detect an APK change and rebuild dalvik for the necessary app. Fixing permissions also does nothing useful (there's a G+ post about that somewhere by Steve Kondik of CM fame, I believe).
I'll have to look for that G+ post.
I've gone by the explanation at -
https://play.google.com/store/apps/details?id=com.stericson.permissionfix
Plus, once in a while, it seems to help and I don't think I'm highly susceptible to the placebo effect...
Interesting that Kondik disagrees...
http://forum.xda-developers.com/showpost.php?p=44856825
I've gone by the explanation at -
https://play.google.com/store/apps/details?id=com.stericson.permissionfix
Plus, once in a while, it seems to help and I don't think I'm highly susceptible to the placebo effect...
Interesting that Kondik disagrees...
http://forum.xda-developers.com/showpost.php?p=44856825
Rush
{<>}~{<>}
I will try this out ...
I'm either really slow to rooting and development, or I'm just not concentrating on what I'm doing.
I am not stopping until i get the sense5 multitasking in this ROM. NY Yankee ROM keeps messing up my phone...so that ROM is not an option.
Rush
{<>}~{<>}
Now I'm stuck at the white HTC screen of death unable to boot into TWRP 
... didn't have a chance to experiment with the above steps. This wasn't caused by your ROM cap.
Edit: Still can't boot into TWRP, but somehow it comes on...and is now showing a screen that requires a Decrypt password -- Anyone know the default password (because i didn't create one), or know a way to get out of this.
... didn't have a chance to experiment with the above steps. This wasn't caused by your ROM cap.Edit: Still can't boot into TWRP, but somehow it comes on...and is now showing a screen that requires a Decrypt password -- Anyone know the default password (because i didn't create one), or know a way to get out of this.
rootlinux
Member
Now I'm stuck at the white HTC screen of death unable to boot into TWRP
Edit: Still can't boot into TWRP, but somehow it comes on...and is now showing a screen that requires a Decrypt password -- Anyone know the default password (because i didn't create one), or know a way to get out of this.
Never seen that password screen.
Have you tried holding power and volume down to get into recovery?
Don't panic.
Reset hardware by holding power for 10 seconds.
Plug into PC, go to your sdk tools folder, in command window say -
adb reboot bootloader
Don't panic.
Reset hardware by holding power for 10 seconds.
Plug into PC, go to your sdk tools folder, in command window say -
adb reboot bootloader
Don't panic.
Rush
{<>}~{<>}
So, go into fastboot usb and type in command window, right?
Error: "device not found".
Rush
{<>}~{<>}
Did all that .... keeps saying, "device not found".
I just want to reboot into TWRP so i can nandroid back to one of my stable ROMs. But the phone just won't boot into TWRP...no matter what i do.
All this happened after i tried using another Sense 5 Rom. This sucks...I'm missing a lot of important calls.
Only TWRP can get you back into a previous ROM you had before?
Did you have Fastboot turned on in settings? (That's referring to booting quickly, not the actual fastboot mode.)
If so, that's going to cause trouble getting you to boot into the bootloader.
Lets try it again.
Hold down power button until phone truly shuts down - at least 10 seconds.
If plugged in to a charger, the led will turn off.
Then hold down the volume down until bootloader boots.
If it powers down and doesn't turn back on after the 10 second reset, then, hold volume down, tap power, keep holding volume down until boot starts.
That ought to put you into the bootloader.
If successful, stop and post back.
If so, that's going to cause trouble getting you to boot into the bootloader.
Lets try it again.
Hold down power button until phone truly shuts down - at least 10 seconds.
If plugged in to a charger, the led will turn off.
Then hold down the volume down until bootloader boots.
If it powers down and doesn't turn back on after the 10 second reset, then, hold volume down, tap power, keep holding volume down until boot starts.
That ought to put you into the bootloader.
If successful, stop and post back.
Rush
{<>}~{<>}
o
Success so for ...sorry for the late response.
Dunno ...not able to pass HTC white screen ...
OK.
If the bootloader is accessible, I think you'll be fine.
Can you get from there to TWRP using volume buttons to navigate, power button to select - Recovery?
If the bootloader is accessible, I think you'll be fine.
Can you get from there to TWRP using volume buttons to navigate, power button to select - Recovery?
Ok.
I think that's a big step forward.
Do a full wipe in TWRP - data, cache, Dalvik and system - and go for a nandroid restore of something that worked before.
I forgot - are you s-on or s-off?
Rush
{<>}~{<>}
S-off.
Okay. Done. This works ...wow, it didn't the other several times I tried.
I'm still going for Jellybean Sense5 multitasking. I just need to replace the SystemUI with the one I downloaded from Cap.
Thanks a lot. (Thumbs-up)
Yep and ask away if his instructions for moving it give any grief.
Btw - two things to put on your list.
First, make sure that you've got Fastboot off in main settings, power.
Second, as soon as conveniently possible, test a simple "adb reboot" command (just that will be fine while running).
If you can get to it with adb, you can get to with fastboot and that's a must for extreme error recovery.
If not, fix your sdk tools or drivers or whatever right away so you can have fastboot and adb at your fingertips.
Hmmmm.
Also maybe a good idea to move this all out to a separate thread.
Stuff happens and I think we agree that what happened wasn't caused by the rom itself or anything like that.
If you agree and you're at a pc, please go for it.
Btw - two things to put on your list.
First, make sure that you've got Fastboot off in main settings, power.
Second, as soon as conveniently possible, test a simple "adb reboot" command (just that will be fine while running).
If you can get to it with adb, you can get to with fastboot and that's a must for extreme error recovery.
If not, fix your sdk tools or drivers or whatever right away so you can have fastboot and adb at your fingertips.
Hmmmm.
Also maybe a good idea to move this all out to a separate thread.
Stuff happens and I think we agree that what happened wasn't caused by the rom itself or anything like that.
If you agree and you're at a pc, please go for it.