justbenny2k
Well-Known Member
I got errors trying to install the vm zip versus the Angry Bean vm app (which I, of course, deleted already). Otherwise the 6/7 build is working fine. I, too, am still having issues with hotplug.
-
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
justbenny2k
Well-Known Member
Ok so I must be the unluckiest. I decided to switch to HOTPLUG and it locked up my phone and went into bootloops again. I had to restore my backup :-(
Chairshot215
Android Expert
Yeah I'm still trying to wrap my head around why some users are having issues. I started using it on the 28th last month before adding it in and haven't had any issues. Still change to Hotplug every time I flash and use Battery Monitor Widget witch keeps a record of battery usage on the SD-card so its not effected by flashing an update or a different Rom. At the moment my current stat as an average is 28 hours from 100% down to 0%. It just keeps an average over time though. lost power all last night so watched Wrath of Khan on 4g and pretty much went from 90% to just making it to the end of the movie before going dead, literally died on me during the credits. Would be interested to know if those who are having issues have tried applying Hotplug before touching any other setting or installing a single app. Maybe something to try next time they flash. Would need to not allow google to restore anything during the setup wizard to do so for it to be a proper test. At least then could rule out it not playing well with a setting or app. Have seen android do some odd things one would not think is apparent. On my Triumph once had a Titanium MMs Backup that would brake wifi even when restored on the same zip the backup was made from. Drove me nuts until I made the connection. Wasn't even a corrupted backup or something like that as when I figured it out had made multiple backups after flashing the update.zip a few times and always came back with the same results. Also along the same line once had a sentinel3 backup that would brake the camera when restored. Not that I'm saying the Hotplug issue is caused by restoring data or anything like that, just examples of how things that would not seem at all related can cause conflicts. Otherwise it is just a mystery at the moment how it blows up things for one person but at the same time works well for another. Same thing with widgets disappearing on reboot. Have had 4 testers including myself set up a bunch of widgets and reboot a number of times and have not been able to reproduce the disappearing act. With that said have had the same issue on my Kindle. With the Kindle though expanding the home screen grid size fixed the issue. Seems unrelated with the Evo though as far as I can tell at this point. With the Kindle though I don't even compile the the source and just download a zip like everyone else. Is nice having a device I barley ever need to flash. With the Evo I run the last build from the previous night after setting up as many apps as I can for the next day and then end up flashing 3 or 4 builds again the next night testing different things.
thesandman6
Newbie
Ya I'm going to flash the new build again tomorrow without restoring and see what happens. I've been restoring app data on this rom for the past few builds and never had a problem unless I accidentally did a system app or data. On the widgets disappearing, i noticed it on a build shortly after the mms was fixed and only if I rebooted the phone, never when I power cycled.
Downloading now and I'll apply hotplug immediately after setup and report results
Edit: not having any of the issues I was before with hotplug, in fact it's running sexy fast as hell. So far so good thanks alot for the work.
Ps followed instructions of setting governor in cm performance settings right after setup. Using default row scheduler still too
Edit: not having any of the issues I was before with hotplug, in fact it's running sexy fast as hell. So far so good thanks alot for the work.
Ps followed instructions of setting governor in cm performance settings right after setup. Using default row scheduler still too
justbenny2k
Well-Known Member
What happened when you started reinstalling your apps? Did you find one of more that was causing conflicts with hotplug?
I have actually reinstalled all of my regular use apps and zero issues so far, performance is still fine. No hang ups or reboots, I honestly think it had something to do with kernel tuner last time things went haywire
All apps were reinstalled either from market or from the apk. Did not restore any data just re signed into everything
Only issue I had had nothing to do with the rom, I flashed a new radio and has to put my sd card in Pc to remove pg86img so I could boot to recovery again to format cache to get phone to boot again :-D
werewolfboy13
Well-Known Member
My problems have finally been resolved with the new update. Thanks! Also I found my backup of the VVM zip on my Google drive so I am good on that issue. Hotplug is now working for me. I have noticed a big improvement on battery life with the hotplug than the default one. Also I noticed that the speeds reset after a build upgrade is that normal?
justbenny2k
Well-Known Member
In the absence of Kernel Tuner, have you gone into Performance and checked the governor? I just did a clean install and skipped the Google stuff. HOTPLUG set and was running smooth until I rebooted. My phone kept defaulting to ONDEMAND.
Did you check set on boot? I have had no problems with settings sticking
justbenny2k
Well-Known Member
I didn't even think to check that. It's set now. So the conflict is with Kernel Tuner? How do I set the second core to HOTPLUG? How do I enable sweep2wake?
I believe CM performance handles that, TBH its ran just great and battery life is alot better than anything before with cm4.2.2, so set it in CM performance and forget about it. Been running this with Everything.me launcher and playing music and youtube vids off and on all day along with texting and tapatalk and im still at 50% battery. Good work Chairshot and g60 of course
As for s2w i dont use it, i dont know if its in the kernel, and youll have to figure something out guess
justbenny2k
Well-Known Member
I believe CM performance handles that, TBH its ran just great and battery life is alot better than anything before with cm4.2.2, so set it in CM performance and forget about it. Been running this with Everything.me launcher and playing music and youtube vids off and on all day along with texting and tapatalk and im still at 50% battery. Good work Chairshot and g60 of course
As for s2w i dont use it, i dont know if its in the kernel, and youll have to figure something out guess
Since flashing a fresh ROM so I could get HOTPLUG to work I had 2 random reboots. The second one froze in the middle of the reboot on the CM logo animation. Oh well... I installed my backup running ONDEMAND until I can figure out more.
justbenny2k
Well-Known Member
EDIT: I thought I'd try giving the CONSERVATIVE governor a try and that caused my phone to freeze, too. Apparently ONDEMAND is the only one that wants to run stably on my phone and I wish I knew why.
thesandman6
Newbie
I reflashed and restored again and everything has been working smoothly so far. I am getting the text notifications for voicemails again though. edit, I just noticed that the cpu frequency resets to default after a reboot
MtDewFella
Newbie
Has anyone else had issues with battery drain even though they barely use the device? what is everyone else averaging in terms of battery life?
fivestardunk
Newbie
I did a clean install yesterday, changed performance settings to HOTPLUG before signing in to Google or installing any apps. Set everything up and phone was great for the day until later last night, went to Kernel Tuner and saw the second core was set to ONDEMAND and kept turning on and off. Managed to get it to HOTPLUG the split second before it disappeared. Put the phone in my pocket and went out - the next time I pulled out my phone, it was stuck in a bootloop. Tried to reboot, still bootlooped. Reverted to previous build.
justbenny2k
Well-Known Member
Not to smile at your troubles, but I'm glad to see I'm not the only one.
As said by the dev, Kernel Tuner is going to be an issue with this ROM. Unlock Developer Settings and use the built in CM Performance to set your processor settings..
I got about 20 hours or so yesterday with pretty good usage
Chingling
Android Enthusiast
I think that hot plug is supposed to shut off the second core, so that's why cpu1 is always disappearing. And I've noticed that just setting it to cpu0 works, you don't have to set it to both cores. When I set hot plug as the governor in performance settings, only cpu0 was set to hot plug in kernel tuner. Its working fine for me now.
Also noticed that battery life seems to be shortened with the 6/7 build compared to the 5/17 build, but that could just be me.
Also noticed that battery life seems to be shortened with the 6/7 build compared to the 5/17 build, but that could just be me.
werewolfboy13
Well-Known Member
No that's only for sense (spelling might be off) based roms.