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

Root [ROM][PORT][FINAL] MIUI 1.11.25-Triumph | 113011-2 (GB 2.3.7 based)

shinew said:
So for someone who needs instant data notification(google voice for texts), which of the 2 options saves more power when there is always wifi available?
1) keep wifi on and 3g off(automatically), but system stays one level above deep sleep
2) automatically turns Wifi off when the screen is off(using Juicedefender would probably do it), but keep 3G on and allows system to go into deep sleep
Click to expand...

AFAIK, as long as the wifi driver is loaded (with the kernel patches I cherry-picked from TG), the phone will stay in the level right above deep sleep. I haven't made these changes that TG did in the current CM7 release: https://github.com/tickerguy/WX_435_Kernel-Tickerguy/commit/c0d8dab553858ac660393430a1505830fc59f3bb

My guess is option 2 would be the best solution for saving power. My understanding is that JD will shut down the data connection, but bring it back up periodically to check for any new notifications.

Since WIFI isn't something I use very often, I only pulled the fix for the WIFI lockups for users who need it. I haven't really looked into WIFI power consumption because I rarely ever turn on WIFI. I used to use JD as a remedy for the stale data connection issue, but since that was fixed, I removed JD.
 
isaacj87 said:
My guess is option 2 would be the best solution for saving power. My understanding is that JD will shut down the data connection, but bring it back up periodically to check for any new notifications.
Click to expand...
With the Ultimate edition, you can customize a lot more. Since I need constant data connection for GV notifications, I've installed Juice Defender and have set it to keep "data" on. So far the phone has been successfully going to sleep, turning off wifi and turning on 3G when the screen is off, then turn on wifi and turn off 3G when I turn on the screen. All without any lockups!

If the wifi got turned off, does that meant the wifi driver has been unloaded for sure, thus allows the system to go into deep sleep mode?
it would be nice if anyone knows any app that can reliably log the overall power usage of the phone, then I can check which method is more power efficient.
 
isaacj87 said:
AFAIK, as long as the wifi driver is loaded (with the kernel patches I cherry-picked from TG), the phone will stay in the level right above deep sleep. I haven't made these changes that TG did in the current CM7 release: https://github.com/tickerguy/WX_435_Kernel-Tickerguy/commit/c0d8dab553858ac660393430a1505830fc59f3bb

My guess is option 2 would be the best solution for saving power. My understanding is that JD will shut down the data connection, but bring it back up periodically to check for any new notifications.

Since WIFI isn't something I use very often, I only pulled the fix for the WIFI lockups for users who need it. I haven't really looked into WIFI power consumption because I rarely ever turn on WIFI. I used to use JD as a remedy for the stale data connection issue, but since that was fixed, I removed JD.
Click to expand...

Issac,

Just updated to the new ROM 1.10.28. What ever you cherry picked from Ticker Guy it looks like connecting to Hidden SSID Wireless networks no longer works anymore on MUIU. Is this possibly a driver issue more than an upstream problem? Since this problem is also effecting CM7 I am guessing what ever code you snagged from TickerGuy also now affecting MUIU.

***UPDATE: Just to verify I started broadcasting my SSID and it connected perfectly.
 
The sleep change has nothing to do with hidden SSIDs - it only impacts the driver during the suspend sequence. My understanding is that CM7 has always had problems with hidden SSIDs so I wouldn't expect anything based on it to work with that.

Basically, the original lockup fix simply prohibited deep sleep suspends by holding a wakelock. This prevented the CPU from going to S3, which is the "deep sleep." Theoretically it should be ok to do that as there's a poll set so suspending the ISR should (in theory) be ok, the linkage is there, but the libra.ko driver appears to hang somewhere internally - probably due to improperly shutting power off to the chipset somewhere and not properly waking it up on a poll. This could be as simple as not waiting the requisite time after power is turned back on to perform an operation and hanging as a consequence, but I have no way to know since I have no source to the libra.ko module.

The later changes (the commit Isaac linked to) is a bit more intelligent about it - that maintains a flag in the librasdioif module (which we do have source to) that notifies the sdio code if the wireless module is loaded. If it is, then we prohibit deep sleep as before. But if it's not, then it's perfectly ok to permit S3, thereby allowing entry into the deep sleep mode.

Note that there's a FURTHER power problem in the radio code (!!!) in that when data connections are up the phone wakes up at a ridiculous rate, effectively rendering your power consumption roughly ~35ma when "asleep." Juice defender fixes this by suspending the data connection most of the time (it wakes it up every 15 minutes for a bit) which in turn allows the CPU to REMAIN asleep most of the time, radically extending the available idle time (the difference here is NOT small.) This looks to be a CDMA radio "gotcha" but again with no source (and this is not Android stuff, this is the proprietary code that runs on the CDMA chipset itself) there's little if any hope for that ever being fixed; it bites on the stock load as well, but the good news is that Juice Defender is very effective in taking care of by tearing down the data connection most of the time when idle.
 
isaacj87 said:
New build is posted. Check changelog for details. I've removed some of the older builds from the first post. If, for some reason, you want an older build, you'll have to personally request a link.

It should be noted that this build is closer to the ROM found in the official MIUI phone (MI-One). While I still used a MIUIandroid port as a base, this build is technically a more "pure" version of MIUI. There were some kinks introduced in 1.10.28 that weren't caused by me. These upstream issues will probably be fixed later. I haven't noticed any showstoppers.

The work I did for GPU is not in this kernel. It still needs some work as it was hit-or-miss.

Happy MIUI-ing.
Click to expand...


What ended up getting removed
 
I love this new build! Thanks Isaac! :D

You said you were working on some stuff with the GPU... what's that all about?
 
Where's that new bootup sound kept in MIUI?

I have to get rid of it, it's not as annoying as the Virgin Mobile lady but still can't have the loud bootup sounds when starting up at work...
 
mantera said:
Where's that new bootup sound kept in MIUI?

I have to get rid of it, it's not as annoying as the Virgin Mobile lady but still can't have the loud bootup sounds when starting up at work...
Click to expand...


Have you tried applying a theme and making sure the boot sound is unchecked? Haven't tried it yet but I'd assume it would work.
 
mantera said:
Where's that new bootup sound kept in MIUI?

I have to get rid of it, it's not as annoying as the Virgin Mobile lady but still can't have the loud bootup sounds when starting up at work...
Click to expand...

go into settings - themes - edit theme - scroll to the bottom and you should see an option for bootup sound just click it and choose "none" and then apply
 
mantera said:
Where's that new bootup sound kept in MIUI?

I have to get rid of it, it's not as annoying as the Virgin Mobile lady but still can't have the loud bootup sounds when starting up at work...
Click to expand...

It can be disabled via the theme editor. If your phone is set to vibrate or silent, it shouldn't play. If you want to remove it completely, it's in /system/media.

It will be removed in the next build. I just left it this time for the sake of it.
 
isaacj87 said:
It can be disabled via the theme editor. If your phone is set to vibrate or silent, it shouldn't play. If you want to remove it completely, it's in /system/media.

It will be removed in the next build. I just left it this time for the sake of it.
Click to expand...

is there anyway to add a toggle function to the settings app? so that you can keep it in there for the people that want it... also, i like the old boot animation.
 
What's the word with WIFI? Has the WIFI lockup issue finally been put to bed?

I haven't had a lockup for a whole day now.
 
OK really crazy bug. I started to play music n my phone went crazy going through every song playing about half a second just flying thru everything on my card. I remember this bug on a rom on my mytouch4g. It basically doesn't let me do anything so I have to pull the battery
 
isaacj87 said:
What's the word with WIFI? Has the WIFI lockup issue finally been put to bed?

I haven't had a lockup for a whole day now.
Click to expand...

It's been a day for me without lock up as well. The battery does seem to go down pretty fast in standby though regardless it's the 3g or wifi...

Here is my not very elegant solution for anyone else who might also be using GV for text and needs instant notification, but want to conserve battery at the same time:
1) let JD automatically turn on/off 3g & wifi periodically for battery conservation;
2) forward GV text to phone and turn off GV status notification;
3) create a tasker profile to launch GV then kill "messaging" app once the native messaging app is launched.
Basically the result is that when there is GV text message coming in, I get notified through the cell service without the need for data, once I click to launch the message app, it clears the unread notification in the status bar, then switch to GV app and kill the messaging app in the background(it'll restart itself right away). As I said, not an elegant solution but so far it seems to work fine for me.

I'm also going to try to make a tasker replacement profile for my JD settings so that I won't need to run both JD & tasker in the background.
 
bigvandal said:
OK so it only happens when I plug my headphones in. If I take them out music plays fine. In my music goes crazy
Click to expand...

I can't reproduce this. I added some songs to the phone, plugged in headphones and started playing music. Everything seems fine.
 
Just for hahas, I decided to download Chainfire 3D and try out ShadowGun 1.0. This is using my latest version (unreleased) of MIUI (10312011-1). I have made no new changes to the kernel:

20111031_184629.jpg


P.S. Thanks Rain for the sticky!
 
im putting sacred odyssey on my phone right now with chainfire and the nvidia plugin. gonna test it out and report back.
 
You must log in or register to reply here.
Back
Top Bottom