all my test builds will be for GB rom's only, once we get something final I'll do one for JB too.
If your going to be testing these please make sure after you flash it you leave your phone on for at least 3 full days without any reboots to make sure its fully stable.
added governor's
added scheduler's
disabled fsync
added zram and enabled it
added init.d support
renamed S07HYPER to S07HK and cleaned it up a little (delete the old file if you have it)
ext4 tweaks
The Following User Says Thank You to Bloodawn For This Useful Post:
Device(s): LG Marquee running Megatron, Samsung Galaxy S III running Jellybam, LG Optimus G, LG Viper
Carrier: Sprint
Thanks: 60
Thanked 29 Times in 22 Posts
Thanks
I am flashing it now. I think it might have been all the stuff I had running in the background. I turned alot of that off and have not had to a pull since.
I am flashing it now. I think it might have been all the stuff I had running in the background. I turned alot of that off and have not had to a pull since.
zram in the current build will help with that too.
Quote:
Originally Posted by jsmz
I just checked, and the governor is still changing when the phone app releases its wakelock.
I don't know whats going on with that. it seems to be the OS that sets it back to ondemand when the call ends, and if thats the case I don't know if theres anything I can do.
Yeah, i think it is the system. I have been using "no frills cpu" it has an option in settings to make that file read only. It doesnt seem to be causing any issues. Im not too worried about it, was just letting you know.
I just had my cpu stick on my max setting (1200) while charging. just so happened to have it on my lap & felt it getting hot. All I had to do was unplug it, turn the screen off then back on then plug it back in and it was back to acting normal.
I just had my cpu stick on my max setting (1200) while charging. just so happened to have it on my lap & felt it getting hot. All I had to do was unplug it, turn the screen off then back on then plug it back in and it was back to acting normal.
what gov?
edit: I put together a fix for your gov switching problem for the next build btw. It will have to be manually enabled in the init.d script tho.
Last edited by Bloodawn; February 1st, 2013 at 11:59 PM.
The Following 5 Users Say Thank You to Bloodawn For This Useful Post:
Device(s): LG Marquee - Current,
HTC Inspire 4G - Former,
HTC HD2 - Superphone that got me into the rom scene
Carrier: Ting
Thanks: 7
Thanked 1 Time in 1 Post
Beta 2 Ran well
I have had beta 2 running since it was released - haven't had to force a reboot in that time. I did drop my phone and have the battery fall out though, so it wasn't running the entire time. I'm about to flash Beta 3b, and I'll try to avoid turning it off. Thanks for the builds!
The Following User Says Thank You to joshk1025 For This Useful Post:
I had to do a battery pull this evening after running 3b since friday evening. I was reading some threads in tapatalk and it locked up and I got a black screen. Waited a while but it wouldn't come back.
I had to do a battery pull this evening after running 3b since friday evening. I was reading some threads in tapatalk and it locked up and I got a black screen. Waited a while but it wouldn't come back.
Mine also just locked up on me. listening to pandora with the screen off, the music stopped and the screen wouldnt come on. right around the 50 hour mark. Same cpu settings as before ondemandx/ sio 220/1200 no profiles.
Also had the cpu stick on 1200 again while charging last night.
The Following User Says Thank You to jsmz For This Useful Post:
Device(s): LG Marquee running Megatron, Samsung Galaxy S III running Jellybam, LG Optimus G, LG Viper
Carrier: Sprint
Thanks: 60
Thanked 29 Times in 22 Posts
I had to do a battery pull. It has locked up while initiating a call, adding a calendar event, and while starting google talk. SmartassV2 with SIO. 1200 Max 220 Min.
Last edited by inkrypted; February 4th, 2013 at 11:00 AM.
Have no had a full lockup yet but significant near lockups with 3b using ondemand gov 1000. Screen taking time to turn back on/no response from any apps/audio stopping.
Device(s): LG Marquee running Megatron, Samsung Galaxy S III running Jellybam, LG Optimus G, LG Viper
Carrier: Sprint
Thanks: 60
Thanked 29 Times in 22 Posts
Lockups
Add me to the list blood. I made all the adjustments as you suggested but had lockups when answering calls. I have also had sluggish performance when waking. The phone not me I am always sluggish after waking.
all my test builds will be for GB rom's only, once we get something final I'll do one for JB too.
If your going to be testing these please make sure after you flash it you leave your phone on for at least 3 full days without any reboots to make sure its fully stable.
added bfq scheduler
removed ramzswap since its not used
removed some ext4 tweaks for now
cleaned ramdisk a little
undervolted wlan
added PermaGov to S07HK (follow the instructions in the file to enable it)
the kernel installation now gets rid of any script in /system/etc/init.d except for HK's that way I know they aren't causing the lockups. so DO NOT add anything to init.d and DO NOT use any apps that change or tweak anything other than the frequency/governor/scheduler while using my beta kernels.
Last edited by Bloodawn; February 6th, 2013 at 03:40 PM.
The Following 7 Users Say Thank You to Bloodawn For This Useful Post:
Device(s): LG Marquee running Megatron, Samsung Galaxy S III running Jellybam, LG Optimus G, LG Viper
Carrier: Sprint
Thanks: 60
Thanked 29 Times in 22 Posts
It Begins
The test begins now so hurry get to the chopper!. 5:18PM Wednesday February 6. Oh Blood I always wipe cache and Dalvik Cache when I update the new kernel is that going to interfere with testing and can we use different governors and schedulers now cause I’m using savagzen and noop.
The test begins now so hurry get to the chopper!. 5:18PM Wednesday February 6. Oh Blood I always wipe cache and Dalvik Cache when I update the new kernel is that going to interfere with testing and can we use different governors and schedulers now cause I’m using savagzen and noop.
The wipes are fine and you can use what you want now. I just had to make sure it wasn't a governor problem you guys were having with beta 3.
Small update, my homescreen has become unresponsive while playing music. I can still pull down and work the lock screen, unlike HK v3, and just told it to reboot from the pull down menu.
all my test builds will be for GB rom's only, once we get something final I'll do one for JB too.
If your going to be testing these please make sure after you flash it you leave your phone on for at least 3 full days without any reboots to make sure its fully stable.
added bfq scheduler
removed ramzswap since its not used
removed some ext4 tweaks for now
cleaned ramdisk a little
undervolted wlan
added PermaGov to S07HK (follow the instructions in the file to enable it)
the kernel installation now gets rid of any script in /system/etc/init.d except for HK's that way I know they aren't causing the lockups. so DO NOT add anything to init.d and DO NOT use any apps that change or tweak anything other than the frequency/governor/scheduler while using my beta kernels.
Something I made up lol. Ever time a phone call ends android sets the governor back to ondemand. Setting and enabling PermaGov keeps the governor at whatever you set it to.
Device(s): LG Marquee running Megatron, Samsung Galaxy S III running Jellybam, LG Optimus G, LG Viper
Carrier: Sprint
Thanks: 60
Thanked 29 Times in 22 Posts
OK
Quote:
Originally Posted by Bloodawn
Something I made up lol. Ever time a phone call ends android sets the governor back to ondemand. Setting and enabling PermaGov keeps the governor at whatever you set it to.
Ok now I get it for a second there I was worried. When you go to making stuff up I think you might need a few days off.
Edit: I havnt had the cpu max out when charging since the second time. I flashed this kernel twice, just because I think my phones a bitch and it doesnt listen very well when i tell it to change kernels haha
Last edited by jsmz; February 7th, 2013 at 02:14 AM.
Having some pretty bad battery life, lost 15-20ish % in 6 hours while i slept. also cannot connect to my router unless im standing right next to it. Literally I am 4 feet away getting a -85dbm signal. I have tx on my ddwrt cranked up to 90, so I usually can grab a signal a block down the street.
Having some pretty bad battery life, lost 15-20ish % in 6 hours while i slept. also cannot connect to my router unless im standing right next to it. Literally I am 4 feet away getting a -85dbm signal. I have tx on my ddwrt cranked up to 90, so I usually can grab a signal a block down the street.
Nothing has been changed related to either wifi or anything that would drain the battery.
Also, the dbm signal in settings is your cell service.
Did you reboot your router and modem? That will usually fix any wifi problem unless it's the Internet itself.
Yeah, I usually reboot all my stuff once a week. I have it plugged into an outlet thats connected to a light switch on the wall so its pretty painless for me to do lol.
It seems to either be an issue with my phone, or with interference in the neighborhood because I cant find any wifi signals at all (usually i can see at least 8 to 10 routers) unless Im right next to the router, and then the signal is super low.
So yeah, pretty sure that someone around here got themselves a new shiny wifi buster.
Device(s): LG Marquee running Megatron, Samsung Galaxy S III running Jellybam, LG Optimus G, LG Viper
Carrier: Sprint
Thanks: 60
Thanked 29 Times in 22 Posts
WOW
Quote:
Originally Posted by jsmz
Having some pretty bad battery life, lost 15-20ish % in 6 hours while i slept. also cannot connect to my router unless im standing right next to it. Literally I am 4 feet away getting a -85dbm signal. I have tx on my ddwrt cranked up to 90, so I usually can grab a signal a block down the street.
I am a novice at working with android but I do know alot about networking and open source router firmware and I believe that 70-84 mW is the recommended Transmit Power setting in DD-WRT and for good reason. Depending upon your brand of router and version of DD-WRT. I hope your not cooking your router. I have the Asus RT-N16 running Tomato Toastman Build and a setting of 60 mW works great.