• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Myn's RLS4

Anyone else having a problem with the wifi control in the notification panel? It seems if wifi is enabled, my notification toggle control isn't lit indicating so. So i have to press the wifi toggle, which of course states "disabling wifi", then press again and it shows "enabling wifi", at which point the toggle lights up. Anytime i try to turn off wifi using the notification bar toggle, it doesn't actually turn it off regardless of the light on/off. ie - i leave my office and turn off wifi via notification bar control, head to chick-fil-a, and notice "Wifi Networks Available" while i'm sitting in the drive thru.

I do have a wifi toggle via Extended Controls that i usually have to use to turn wifi on/off, and it reads correctly each time. Just wondering if there's a conflict with me having both toggles, or if anyone else is having this issue with the new notification controls...

It's a known issue by the guy who wrote the program. It's not so much a bother as long as you remember that if you turn it on using something else it's on. You can also customize which notifications appear and in what order. Here's mine...
dX1jr.png
 
Anyone else having a problem with the wifi control in the notification panel? It seems if wifi is enabled, my notification toggle control isn't lit indicating so. So i have to press the wifi toggle, which of course states "disabling wifi", then press again and it shows "enabling wifi", at which point the toggle lights up. Anytime i try to turn off wifi using the notification bar toggle, it doesn't actually turn it off regardless of the light on/off. ie - i leave my office and turn off wifi via notification bar control, head to chick-fil-a, and notice "Wifi Networks Available" while i'm sitting in the drive thru.

I do have a wifi toggle via Extended Controls that i usually have to use to turn wifi on/off, and it reads correctly each time. Just wondering if there's a conflict with me having both toggles, or if anyone else is having this issue with the new notification controls...

If you toggle anything that you have in the notification panel widgets with any other method, they will be out of sync. It's a known bug. You can either ignore it and accept the fact that it's a toggle, and may not always show exactly what is on/off, or you can sync it back up by toggling anything else via the notification panel toggle widgets. So, for example, when wifi ends up out of sync, toggle something simple like orientation lock. That will sync everything back up.
 
I suppose that's the idea, but it's been known to be inconsistent.



Which 4G scanning bug are you referring to, specifically?

the 4g scanning bug, where you try to turn on 4G in a known area, and it will stick at turning on , or scanning and will not connect.

I do hot restart and 9 our of 10 times it will work w/o issues, the tenth time I did full restart and it worked.
 
Do you have Vlingo InCar installed by any chance? That program was causing my phone to restart every time I disconnected from the speakerphone in my car.

Why, yes as a matter of fact, I do. I like both enough to continue using both, even with the "bug"
 
the 4g scanning bug, where you try to turn on 4G in a known area, and it will stick at turning on , or scanning and will not connect.

I do hot restart and 9 our of 10 times it will work w/o issues, the tenth time I did full restart and it worked.

Did you wipe data before flashing RLS4 or just cache/dalvik?
 
It's a known issue by the guy who wrote the program. It's not so much a bother as long as you remember that if you turn it on using something else it's on. You can also customize which notifications appear and in what order. Here's mine...
dX1jr.png

How, may I ask, do you change the order of the toggles ?
 
That's what I thought. Not every .zip file is a flashable zip :). In this case, it's just an apk file and a readme file (hint on that last one ;)). You can either install it through adb or by copying it to your phone and installing it like you would any other apk. Or, support the dev and buy it in the market.
awesome thanks, I got it installed, so it's set on "on demand" right now max 998, min 245, set on boot in unchecked, what if nay changes should I make? Look for more battery life, and don't necessarily want to blow up my phone :) Not this week anyways :D
 
That is correct....you do not have to wipe although some would recommend you do(I don't). I only do a full wipe when installing a ROM. I guess wiping caches and dalvik would be relatively painless...

There are some clear notification bars that may work as well as other themes(riptide,etc). I honestly don't knowif these would work although I don't see why not. Font packs are a good start though. Myn's font is a little skinny and hard to read so I change it out of necessity. I'm old...:-) Don't be afraid. Have fun. You can always go back to a recovery although I have never had to.

You are old? You mean you are not the chick in your avatar?...now you have spoiled it for me!!
 
awesome thanks, I got it installed, so it's set on "on demand" right now max 998, min 245, set on boot in unchecked, what if nay changes should I make? Look for more battery life, and don't necessarily want to blow up my phone :) Not this week anyways :D
follow up on my previous unanswered question, am I really limited on what I can do with setcpu becuase I am on the stock HTC #17 kernel?
I would like to get better battery life, but have no idea where to start with setcpu, so any input would be appreciated.
 
follow up on my previous unanswered question, am I really limited on what I can do with setcpu becuase I am on the stock HTC #17 kernel?
I would like to get better battery life, but have no idea where to start with setcpu, so any input would be appreciated.

Well, first, you need to disable perflock if you're going to use the HTC #17 kernel. Beyond that, I think you're only other limitations are that you can't overclock, and you don't have as many governor choices.

What you should do is set the normal min/max on the main tab. Make the min something like 245 and the max 998. If you want better battery life, you can make the max lower, but your performance will suffer if you go too low. Try it out and see. After that, set up some profiles. The most common would include 245/245 min/max when screen is off, underclocking as the battery gets lower, etc.

Your best bet is to read this thread:

http://androidforums.com/evo-4g-all-things-root/210253-setcpu-guide.html
 
ok I read through the entire setcpu post, but I'm still not sure what to setup for profiles....:confused:
I disabled the perflock, so it shows my current frequency now, but what profiles should I have...?
the setcpu guide definately helped me understand how to navigate the program, but doesnt really provide an example profiles or advanced setting examples, anyone care to share their recomendations is lameon's terms ? :)
 
ok I read through the entire setcpu post, but I'm still not sure what to setup for profiles....:confused:
I disabled the perflock, so it shows my current frequency now, but what profiles should I have...?
the setcpu guide definately helped me understand how to navigate the program, but doesnt really provide an example profiles or advanced setting examples, anyone care to share their recomendations is lameon's terms ? :)

Take a look at the second screenshot in the setcpu guide post. That is a screenshot of the profiles tab with some example profiles (which are the most commonly used ones). Basically, what it is is a set of conditions under which the cpu scaling max/min is different than under "normal" conditions, where normal is what you set on the main screen. For each profile, you have the "condition". Look at the screenshot for some examples. Take screen off, for example. This means when you turn the screen off, and are not using the phone. When that condition is met, the max/min you see directly to the right takes effect over the main setting. For that particular profile, you'd want it set rather low. Personally, I had issues with anything under 245, so I'd set that at 245/245.

There are two major things you need to keep in mind. One is that if two or more profiles' conditions are met at the same time, whichever profile has the highest priority will take effect. So, what you should do is set a "charging" profile so that when the phone is charging, you scale like normal. That way, if you're using your phone for navigation or something, and have it plugged in, you aren't forcing it to underclock even if the screen turns off. The second thing to keep in mind is if you use profiles to underclock in steps as the battery percentage goes down, the lower the battery percentage, the higher the priority must be. The reason is that if you have one set for 60% and one set for 40%, both conditions will be met at 39% and under, but you want the one with 40% to be active at that point. The profile you see with the temp greater than 40 degrees C is a failsafe to way underclock if the temperature hits dangerous levels.

Let me know if that's still a bit confusing and I'll try to explain it a little differently.
 
the 4g scanning bug, where you try to turn on 4G in a known area, and it will stick at turning on , or scanning and will not connect.

I do hot restart and 9 our of 10 times it will work w/o issues, the tenth time I did full restart and it worked.

Try these steps. it took me a while to figure it out but I had the same problem where my phone will be on "SCANNING" . The fix below definitely did the trick...

NOTE: THE Wimax MAC address can be found on a barcode in the original box or by entering ##3282#in the dial pad (select View mode, look for NAI, youll see the WIMAX MAC address followed by @sprintpcs.com)


I found these steps at xda:

gthing Wrote:

1. I ran an update of the prl just to make sure it was current.
2. I ran the profile update in the same location.
3. I then did this:

adb shell
ls /data/misc/wimax/

look for a file with your macaddress ending in .tree.xml. you want to move that to another location so it gets regenerated. (the following command basically renames it.)

mv /data/misc/wimax/(Your-mac-address).tree.xml /data/misc/wimax/(Your-mac-address).tree.xml.old

more at:
[GUIDE] Bad WiMax MAC? Broken 4G after update? Fix HERE! [Archive] - xda-developers
 
Take a look at the second screenshot in the setcpu guide post. That is a screenshot of the profiles tab with some example profiles (which are the most commonly used ones). Basically, what it is is a set of conditions under which the cpu scaling max/min is different than under "normal" conditions, where normal is what you set on the main screen. For each profile, you have the "condition". Look at the screenshot for some examples. Take screen off, for example. This means when you turn the screen off, and are not using the phone. When that condition is met, the max/min you see directly to the right takes effect over the main setting. For that particular profile, you'd want it set rather low. Personally, I had issues with anything under 245, so I'd set that at 245/245.

There are two major things you need to keep in mind. One is that if two or more profiles' conditions are met at the same time, whichever profile has the highest priority will take effect. So, what you should do is set a "charging" profile so that when the phone is charging, you scale like normal. That way, if you're using your phone for navigation or something, and have it plugged in, you aren't forcing it to underclock even if the screen turns off. The second thing to keep in mind is if you use profiles to underclock in steps as the battery percentage goes down, the lower the battery percentage, the higher the priority must be. The reason is that if you have one set for 60% and one set for 40%, both conditions will be met at 39% and under, but you want the one with 40% to be active at that point. The profile you see with the temp greater than 40 degrees C is a failsafe to way underclock if the temperature hits dangerous levels.

Let me know if that's still a bit confusing and I'll try to explain it a little differently.

that makes a lot of sense, thanks so much!!!
it wont let me go any lower than the 245 min anyways so I will just use that, thanks!!!

If I ever decide to use a different kernel then I will have to research some more about overclocking, but I think I will keep this one as long as I can get the battery to last a while.

so that means that my "charging" profile would have to have a higher priority than my "screen off" profile that way it would still work in the GPS situation that you talked about. I'll start with just a charging, failsafe, and screen off profile then, and see how the battery does. If I don't have to have a bunch of scaling down profiles that would be easier
 
I love this ROM...getting stellar battery life compared to stock...runs cleaner and smoother...looks fantastic! i did however download TypeFresh and flash the Sony Sketch font pack, but that's because that font looks beast!

over all, Myn has made EVO the phone i've always wanted it to be....i would recommend this ROM, with the HTC 17 kernal, hands-down over all other ROMs...even if you are a power user, this ROM is for you!
 
that makes a lot of sense, thanks so much!!!
it wont let me go any lower than the 245 min anyways so I will just use that, thanks!!!

If I ever decide to use a different kernel then I will have to research some more about overclocking, but I think I will keep this one as long as I can get the battery to last a while.

so that means that my "charging" profile would have to have a higher priority than my "screen off" profile that way it would still work in the GPS situation that you talked about. I'll start with just a charging, failsafe, and screen off profile then, and see how the battery does. If I don't have to have a bunch of scaling down profiles that would be easier

Well, that's what most people seem to do with a charging profile. For one, there is no reason to underclock when the phone is plugged in, and the other is you might be doing stuff (like gps) with the phone when it's plugged in, and way underclocking could interfere with that. If you're not worried about it, don't bother.
 
Anyone else having a problem with the wifi control in the notification panel? It seems if wifi is enabled, my notification toggle control isn't lit indicating so. So i have to press the wifi toggle, which of course states "disabling wifi", then press again and it shows "enabling wifi", at which point the toggle lights up. Anytime i try to turn off wifi using the notification bar toggle, it doesn't actually turn it off regardless of the light on/off. ie - i leave my office and turn off wifi via notification bar control, head to chick-fil-a, and notice "Wifi Networks Available" while i'm sitting in the drive thru.

I do have a wifi toggle via Extended Controls that i usually have to use to turn wifi on/off, and it reads correctly each time. Just wondering if there's a conflict with me having both toggles, or if anyone else is having this issue with the new notification controls...

This was a known issue with the developer of the notification bar. You pretty much need to use the notification bar exclusively, because if you toggle any of those items anywhere else the bar is not updated.
 
Back
Top Bottom