Chingling
Android Enthusiast
Wouldn't this be what mpdecision does? Or does mpdecision only put the second core to sleep when the screen is off?
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [ROM] Angry Bean / CM 10.1 [build 08.08.13]
- Thread starter Chairshot215
- Start date
-
- Tags
- htc evo v 4g
Wouldn't this be what mpdecision does? Or does mpdecision only put the second core to sleep when the screen is off?
werewolfboy13
Well-Known Member
I am using the settings app version.
MrNegative370
Newbie
So far everything is working great (mild overheating on 3g) this is my favorite rom and i appreciate your time developing it XD
scavenger55
Lurker
So since I flashed dastin1015 rom and now since he is not working on the CDMA version no more and you took over Chairshot215, what should I do? I really dont feel like re-flashing and whatnot. Is there a way to merge updates to the rom I am using?
Chairshot215
Android Expert
I think at this point I don't see any way around re-flashing. There are a decent amount of differences between the Roms. You could try using an app like Titanium and try restoring things like settings, launcher and what not but probably would be extremely problematic. Extremely being the key word, sorry. Was looking at the Team Hydra commits tonight and not sure they are sticking with just GSM. Think I saw a new commit today in the msm common device files that will allow GSM/CDMA to be set in the device specific directory but not 100% on that, was looking for something else and just read the commits header.
Asked a similar question back when I got my Kindle and Whyzor did a bit of reserch and put together a writeup for me explaining how Hotplug works. Ill look for it tomorrow and post if I can find it. Otherwise I dont think mpdecision is just a when sleeping kinda thing but can be set to do so depending. Would honestly need to do more research on that. My Kindle has both and there is a noticeable difference in battery and performance with Hotplug set but did not set as the default so will rely on user feedback from those who try it out. Otherwise based on past experience with the Kindle thought it would be a nice option.
mpdecision is acting really screwy. kernel tuner found that core 2 was shutting off with the screen on. i also changed the governor to hotplug and i ended up with core 1 STUCK on 192 mhz, core 2 off, and my phone freezing. Maybe its just me? Interesting find tho
and phone is stuck on the bootanim upon battery pull reboot
and phone is stuck on the bootanim upon battery pull reboot
werewolfboy13
Well-Known Member
What happened to the voicemail zip app?
EWhite3522
Lurker
Probably just me again but...
The past 2 updates (604 & 605) have resulted in the inability to send SMS's. They get stuck at "SENDING" and I have to reboot the phone to get them to send. After that I still cannot send newly created texts. I have tried different downloads thinking it may have been a bad flash, but the problem remains. I even tried backtracking to the last ROM I had no issues with (517) but that didn't fix it.
The only fix that worked for me was to restore an old Harmonia Backup that I had, Check to see if I can send texts, and then flash the (517) again.
Any thoughts?
The past 2 updates (604 & 605) have resulted in the inability to send SMS's. They get stuck at "SENDING" and I have to reboot the phone to get them to send. After that I still cannot send newly created texts. I have tried different downloads thinking it may have been a bad flash, but the problem remains. I even tried backtracking to the last ROM I had no issues with (517) but that didn't fix it.
The only fix that worked for me was to restore an old Harmonia Backup that I had, Check to see if I can send texts, and then flash the (517) again.
Any thoughts?
justbenny2k
Well-Known Member
I'm sorry to be such a pain but I can't seem to get the governor working.
When I set HOTPLUG for CPU0 my second core disappears from the screen and I can't do anything with it. I tried putting it back to ONDEMAND hoping the second core would reappear but it didn't. I even tried manually turning on/off the second core hoping it would stick with no luck.
I wound up reflashing the ROM so I could have access to both cores again. I'm using ONDEMAND just to be on the safe side for now.
I thought that I was the only person having this problem. On the 604 build I had this problem. I flashed back to my backup of 517 and I was able to send sms again. However I have yet to flash the newest build. So I will report back later on if I have a problem with that build sending sms also.
I'm also having the same issue. (on 0604)
Chairshot215
Android Expert
Its not just you, Cyonogen seems to have been messing with the app.
https://github.com/CyanogenMod/android_packages_apps_Mms/commits/cm-10.1
The Visual Voice Mail zip replaces the app with an older version and has been working OK so far. I did a sync this morning and the build stops with an error compiling the sms/mms app so looks like its still not fixed.
Not sure what method you are using to set the Governor but would recommend just using the built in performance settings. Being specifically designed to run both cores setting it to a specific core probably is causing the issue. Would just use the built in performance settings and pick from the list of available Governor.
werewolfboy13
Well-Known Member
I don't see the zip on your server link.
justbenny2k
Well-Known Member
I usually use Kennel Tuner so on your suggestion I used the built in and it only changed CPU0 to HOTPLUG but it didn't change CPU1. That stayed on ONDEMAND. When I opened Kernel Tuner to fix it only one core showed up. Then the screen flickered between 1 core and 2 cores. It finally stopped long enough to let me with CPU1 to HOTPLUG. Once I did that my phone froze and rebooted. Upon reboot my cores were set back to ONDEMAND.
I hope the attached screen shots help.
Attachments
coolblood2
Newbie
With the latest build I can't send either MMS or SMS. Reverted to the 5/17 build and texts send just find without any issue. The only way to send anything was to reboot and I know that nobody can spend the time rebooting to send every text lol. Keep up the good work cause I know all these random and unexpected problems can cause you to spend more of your free time trying to fix this then any of us could spare. So a huge thank you from me.
I'm having this same issue. ):
Are these just the changes? Also what do we do to fix it? Just flash the VVM fix?
Chairshot215
Android Expert
I usually flash it with the Rom but flashed it after as a test and it was working. Looks like CM fixed it as a did a sync after work and after compiling the build and flashing its working again.
Just got all excited as I made a few changes and tried HDMI, it came rite up on my TV Crystal clear. Then tried streaming some video and no audio, was very disappointed.
Are you going to put up a fixed build? Oh man that sucks. So very close though. Keep at it and you'll get it.
Couple things: FWIW, I'm having no SMS/MMS issues whatsoever, but I did start with a full wipe and carefully controlled Titanium Backup restore (in particular, no system apps or data restored).
Secondly, is anyone else dealing with perpetual widget insanity? I'm using ADWLauncher EX, which I've used for years now... at some point after switching to Angry Bean I started having issues where my widgets (HD Widgets, WiFi manager, Yatse) started randomly disappearing. From one reboot to the next, most of them will be totally gone, so I have to re-add them. Then at some point I'll suddenly realize the old widgets are back, and are stacked on top of or squished next to the new widgets... so I have to delete the duplicates, and everything's ok until the next reboot, when the cycle's liable to start all over again.
Anyone?
Secondly, is anyone else dealing with perpetual widget insanity? I'm using ADWLauncher EX, which I've used for years now... at some point after switching to Angry Bean I started having issues where my widgets (HD Widgets, WiFi manager, Yatse) started randomly disappearing. From one reboot to the next, most of them will be totally gone, so I have to re-add them. Then at some point I'll suddenly realize the old widgets are back, and are stacked on top of or squished next to the new widgets... so I have to delete the duplicates, and everything's ok until the next reboot, when the cycle's liable to start all over again.
Anyone?
werewolfboy13
Well-Known Member
I have the same problem with the system widgets. After reboot all my widgets are gone.
Chairshot215
Android Expert
Posted the build with the messenger app updates from CM. Big thanks to those who ran some tests for me why I was at the joby job.
justbenny2k
Well-Known Member
What's the difference between your voice mail app and the Angry Bean one g60madman provided?
Chairshot215
Android Expert
Nothing, its the same one g60 put together. Its a bit more then just an app though, adds a few extra files and a different MMS app besides just the Visual Voice-mail app. Is the reason flashing it fixed the sms/mms issue in the last build. The MMS app in the Visual Voice-mail Zip does not pull in changes made to the MMS app from the CM Team.
thesandman6
Newbie
I flashed the 6-7 build this morning with a full format. I got boot loops after restoring downloaded app data with tb and trying the hotplug governor @ 1296 through the performance menu.