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

Root [Boost Mobile] [ROM] n00b (B10 based) VIII.II FULL Install 1/23/2013

After first flashing VII there was unseen before snappiness and responsiveness which of course made me very happy. However, I'm noticing lag after certain amounts of time and now I'm not getting texts on a daily basis. I flashed my girlfriends phone with VII and now she's missing texts as well. After reboot new texts begin to receive again but the old ones that were missed remain missed. I need to reflash noob VI I think on both phones. I won't know I missed them until getting phone calls that I never respond to texts so I restart my phone and then get new ones but not the ones I missed. This zram just might be the culprit and is too unreliable I think... I've never had this problem before. Very confused and uncertain of what to do. Not panicing though! Haha Very annoyed would be more accurate. My girlfriend was sending me mms photos while out shopping for our son this morning but I never knew. Because I didn't respond she thought that she shouldn't buy the items and now she has to drive all the way back to get the stuff because I do, in fact, want her to get the stuff. Grrrr

Update : I disabled all three zram, sd readahead, and voltage scripts. Zram to see if it's my lag culprit, sdreadahaed because the kernel already has it built in (what I'm using anyway), and voltage control because I set my own anyway. I'll let ya know how it goes but so far so good. Getting texts!

I was going to suggest it may be boost/network related as far as the mms issues, we saw that two weeks ago across the country and different phones/roms on boost.

for the lag, I would recommend a reflash of VII, if that doesn't change it, then you could go back to swap like noob VI by flashing this zip.

It sounds like you are using a different kernel than what I put out, if so all bets are off LOL

FYI if you flash alien kernel on this ROM you are asking for issues since I have conflicting scripts running and that kernel is bundled with it's own scripts/build.prop tweaks etc. Not knocking it but it's more than just a kernel you are getting in those zips.

EDIT: Reflashing VII Update will clear the scripts and build.prop that alien kernel installed so that's a good starting point FYI.
 
I'm running that kernel that DTM gave you and I a couple of days ago. I took heed of your advice on the alien kernel awhile back so I've never tried it. It's weird that when I reboot the sms's start pushing thru. What do you think?
 
I'm running that kernel that DTM gave you and I a couple of days ago. I took heed of your advice on the alien kernel awhile back so I've never tried it. It's weird that when I reboot the sms's start pushing thru. What do you think?

I actually called boost mobile on this a couple of days ago and was told by a tier 3 tech it was the network here in Portland that was having issues(don't know if its the same issue your having in your area) and I was told there working to correct the problem....;)
 
the new update is amazing..., it feels like i have a brand new phone. one question..., what do you guys say is the best voltage control setting? right now the best one i've found is the smartassv2 with max cpu speed of 1804... works flawless.
 
I'm running that kernel that DTM gave you and I a couple of days ago. I took heed of your advice on the alien kernel awhile back so I've never tried it. It's weird that when I reboot the sms's start pushing thru. What do you think?

If my phone goes to sleep data disappears. So does my service. No text. Only calls and after 3-4 rings. Its weird. And I've been thru 4 ROMs lately and can't fix it or MMS issue. Had to download live profile and whatsapp.
 
the new update is amazing..., it feels like i have a brand new phone. one question..., what do you guys say is the best voltage control setting? right now the best one i've found is the smartassv2 with max cpu speed of 1804... works flawless.

A lot of us are running smartassV2/sio :) I have mine backed off to 1612.
Nice to see you like your phone so much better now!!:D
 
If my phone goes to sleep data disappears. So does my service. No text. Only calls and after 3-4 rings. Its weird. And I've been thru 4 ROMs lately and can't fix it or MMS issue. Had to download live profile and whatsapp.

no issues like that here, not sure what to tell you.
 
Reflashed the newer VII update on both phones last night. Everything seems to be working as planned and as expected. Does it seem to anyone else that snappiness eventually deteriorates after a couple days. I'm hoping it doesn't this time :D Don't know how I feel about zram yet. The ROM is awesome as usual and I'm not going anywhere.
 
Reflashed the newer VII update on both phones last night. Everything seems to be working as planned and as expected. Does it seem to anyone else that snappiness eventually deteriorates after a couple days. I'm hoping it doesn't this time :D Don't know how I feel about zram yet. The ROM is awesome as usual and I'm not going anywhere.

good to hear... I may need to rethink my approach to versioning and what zips I leave up on this thread for the ROM... what I think happened is you downloaded and updated to a version when I hadn't put in the minfree values, I caught that after some discussion here and added it back in. It may just be my fault... I try very hard not to put out links to test/updates etc in the thread except in the OP, it just leaves room for confusion about what's the latest and greatest... clearly you all underestimate my sneakiness LOL

I think zRam is the way to go after the reading on it I have done, it might take me a couple iterations to get it spot on. I am talking to DTM about an option that may be good for us and he's already got a test kernel out that speeds it up some, as soon as we settle on something stable I will put out a zip to update to that new config. Hang with me, I will keep working on it until it's smooth as silk. I posted a zip a few posts to switch back to the n00b VI setting for the swap instead of zRam if you do see issues come back in a day or two like before.
 
good to hear... I may need to rethink my approach to versioning and what zips I leave up on this thread for the ROM... what I think happened is you downloaded and updated to a version when I hadn't put in the minfree values, I caught that after some discussion here and added it back in. It may just be my fault... I try very hard not to put out links to test/updates etc in the thread except in the OP, it just leaves room for confusion about what's the latest and greatest... clearly you all underestimate my sneakiness LOL

I think zRam is the way to go after the reading on it I have done, it might take me a couple iterations to get it spot on. I am talking to DTM about an option that may be good for us and he's already got a test kernel out that speeds it up some, as soon as we settle on something stable I will put out a zip to update to that new config. Hang with me, I will keep working on it until it's smooth as silk. I posted a zip a few posts to switch back to the n00b VI setting for the swap instead of zRam if you do see issues come back in a day or two like before.

You're right...zram is the way to go. It's much faster and takes up less space than a conventional swapfile. The downside is that as zram gets full it will eventually start causing system lag and the only real cure for that is a reboot which people should be doing every 1-2 days anyway.

Most likely you don't see these issues yourself because you're constantly rebooting and flashing as you develop and test your rom.
 
I agree that zram is the way to go but it is higher maintenance. I wish I knew more about the inner workings of it so I can contribute (I'm researching) but as MrBobo says it's not there quite yet in that "sweet spot". I have to say though that it's comforting knowing that it's continuously worked on and that's the reason MrBobo has so many fans, myself included of course. I'm sure hanging in there. Now that the most updatedest VII gives me an out and literal reset I'll be here for the loooooooong haul! Haha I don't think that was in question anyway. Is there a way to place an auto dump in the script when zram fills to a certain point of causing lag? That would alleviate the reboot every one or two days which drewhill is absolutely accurate on in my experience thus far. It's almost there!
 
This post is kinda of topic, but not really...What is the best way to calibrate batteries with twrp? After getting my new phone and installing n00b my battery drains rapidly...I can be playin around on the phone, and I can watch it drain... But I've got extended life batteries which before I was getting at least a day, usually a day and a half, if not more. I'd like to get back to that...
 
Unfortunately there's no such thing or user function out there that can calibrate the battery. The makers of Android @ Google confirmed on an article I read that even clearing battery cache does nothing except clear the logcat entries for devs to use in determining problems of apps and functions being the cause of draining battery life. I too was wondering the same thing a couple of weeks back and this is what I found. DL an app to read logcat entries so you can determine which app(s) is your drain culprit. There are many on the Play Store for free. When you start seeing your battery drain really bad, logcat it. :D
 
Unfortunately there's no such thing or user function out there that can calibrate the battery. The makers of Android @ Google confirmed on an article I read that even clearing battery cache does nothing except clear the logcat entries for devs to use in determining problems of apps and functions being the cause of draining battery life. I too was wondering the same thing a couple of weeks back and this is what I found. DL an app to read logcat entries so you can determine which app(s) is your drain culprit. There are many on the Play Store for free. When you start seeing your battery drain really bad, logcat it. :D

I'm running the same apps as before just the Diff ROM and wiping battery stats worked with cwm...
 
Battery stats clear when you hit 100 % charge. Charge to 100 then unplug fora couple minutes until the percentage drops to 95, plug in and charge again until 100, unplug until it drops again, charge to 100, repeat until it stays at 100 after unplugging it for a couple minutes. I have a 2200mah battery that lasts 24 hours normally with my rom
 
Battery stats clear when you hit 100 % charge. Charge to 100 then unplug fora couple minutes until the percentage drops to 95, plug in and charge again until 100, unplug until it drops again, charge to 100, repeat until it stays at 100 after unplugging it for a couple minutes. I have a 2200mah battery that lasts 24 hours normally with my rom

Alright, I'll give that a try, I usually don't use my charger on the phone, but hopefully I can get the stats clear that way thanks.
 
http://forum.xda-developers.com/showthread.php?t=1635980

shows a nice bit o code
Code:
 #!/system/bin/bash

 #Created by Dorimanx for cron ram managment
 CPULOAD=$(cat /proc/loadavg | cut -d " " -f1)
 sleep 1
 while [[ ! $CPULOAD < 2.00 ]]
 do echo "Waiting For CPU to cool down"
 sleep 30
 CPULOAD=$(cat /proc/loadavg | cut -d " " -f1)
 sleep 1
 done
 #Boosting CPU
 CHECKMAXFREQ=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq`
 CHECKMINFREQ=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq`
 echo 998400 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
 echo 998400 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
sync
  ZRAMUSE=`cat /proc/swaps | grep -v /dev/block/mmcblk0p3 | grep -v /sd-ext/swap | grep -v /sdcard/mnt/swap | grep -v /sdcard/swap | grep -v Used | cut -s -f3`
 if [[ $ZRAMUSE < 10000 ]]
 then
 echo "no need to clean zram"
 else
 if [ -e /dev/block/mmcblk0p3 ]
 then
 sysctl -w vm.drop_caches=3
 swapoff /dev/block/zram0
 sleep 2
 swapon /dev/block/zram0
 sleep 2
 swapoff /dev/block/mmcblk0p3
 sleep 2
 swapon /dev/block/mmcblk0p3
 elif [ -e /sdcard/swap ]
 then
 sysctl -w vm.drop_caches=3
 swapoff /dev/block/zram0
 sleep 2
 swapon /dev/block/zram0
 sleep 2
 swapoff /sdcard/swap
 sleep 2
 swapon /sdcard/swap
 elif [ -e /sd-ext/swap ]  
then
 sysctl -w vm.drop_caches=3
 swapoff /dev/block/zram0
 sleep 2
 swapon /dev/block/zram0
 sleep 2
 swapoff /sd-ext/swap
 sleep 2
 swapon /sd-ext/swap
 fi
 fi
 #In case no secondary SWAP detected and ZRAM use lower than 80MB then we can safely clean it. 


ZRAMUSE=`cat /proc/swaps | grep -v /dev/block/mmcblk0p3 | grep -v /sd-ext/swap | grep -v /sdcard/mnt/swap | grep -v /sdcard/swap | grep -v Used | cut -s -f3`
 if [[ $ZRAMUSE < 80000 ]]
 then
 swapoff /dev/block/zram0
 sleep 2
 swapon /dev/block/zram0
 fi
 sync
 sysctl -w vm.drop_caches=3
 date > /data/cron-clear-swap
 echo "runing clear swap every 4:20AM" >> /data/cron-clear-swap
 echo "ram and swap cleared"

 #Restoring CPU
 echo $CHECKMAXFREQ > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
 echo $CHECKMINFREQ > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
might work to use it
 
never really realized the mms issue until now. can't download or view mms. I remember a fix for this in this thread, can't seem to find it. can anyone help out?
 
never really realized the mms issue until now. can't download or view mms. I remember a fix for this in this thread, can't seem to find it. can anyone help out?

There shouldn't be any issues with mms on the rom, but there have been issues the last few weeks on the boost network side. You can try a clear cache and dalvik through recovery.
 
http://forum.xda-developers.com/showthread.php?t=1635980

shows a nice bit o code
Code:
 #!/system/bin/bash

 #Created by Dorimanx for cron ram managment
 CPULOAD=$(cat /proc/loadavg | cut -d " " -f1)
 sleep 1
 while [[ ! $CPULOAD < 2.00 ]]
 do echo "Waiting For CPU to cool down"
 sleep 30
 CPULOAD=$(cat /proc/loadavg | cut -d " " -f1)
 sleep 1
 done
 #Boosting CPU
 CHECKMAXFREQ=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq`
 CHECKMINFREQ=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq`
 echo 998400 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
 echo 998400 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
sync
  ZRAMUSE=`cat /proc/swaps | grep -v /dev/block/mmcblk0p3 | grep -v /sd-ext/swap | grep -v /sdcard/mnt/swap | grep -v /sdcard/swap | grep -v Used | cut -s -f3`
 if [[ $ZRAMUSE < 10000 ]]
 then
 echo "no need to clean zram"
 else
 if [ -e /dev/block/mmcblk0p3 ]
 then
 sysctl -w vm.drop_caches=3
 swapoff /dev/block/zram0
 sleep 2
 swapon /dev/block/zram0
 sleep 2
 swapoff /dev/block/mmcblk0p3
 sleep 2
 swapon /dev/block/mmcblk0p3
 elif [ -e /sdcard/swap ]
 then
 sysctl -w vm.drop_caches=3
 swapoff /dev/block/zram0
 sleep 2
 swapon /dev/block/zram0
 sleep 2
 swapoff /sdcard/swap
 sleep 2
 swapon /sdcard/swap
 elif [ -e /sd-ext/swap ]  
then
 sysctl -w vm.drop_caches=3
 swapoff /dev/block/zram0
 sleep 2
 swapon /dev/block/zram0
 sleep 2
 swapoff /sd-ext/swap
 sleep 2
 swapon /sd-ext/swap
 fi
 fi
 #In case no secondary SWAP detected and ZRAM use lower than 80MB then we can safely clean it. 


ZRAMUSE=`cat /proc/swaps | grep -v /dev/block/mmcblk0p3 | grep -v /sd-ext/swap | grep -v /sdcard/mnt/swap | grep -v /sdcard/swap | grep -v Used | cut -s -f3`
 if [[ $ZRAMUSE < 80000 ]]
 then
 swapoff /dev/block/zram0
 sleep 2
 swapon /dev/block/zram0
 fi
 sync
 sysctl -w vm.drop_caches=3
 date > /data/cron-clear-swap
 echo "runing clear swap every 4:20AM" >> /data/cron-clear-swap
 echo "ram and swap cleared"

 #Restoring CPU
 echo $CHECKMAXFREQ > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
 echo $CHECKMINFREQ > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
might work to use it

funny, just ran across this friday. This is a timed nightly dump of zram. I think there should be an easier way to have the system automatically manage the zram just like every other kind of swap/temporary memory.

In the dev thread I think I am close now, added some more settings and adjustments, just need some people to give it a try and let me know if the lag comes back or not, so far I haven't been able to get it to come back (but I do reboot more than average).
 
When ever I try to zoom in with the app it force closes on me btw im running VI NOT the latest I haven't had time to backup
 
Am I the only one who can't play music now? I hope it's something I can fix... I deleted the folder from my sd card and put the files back on but notta
 
Back
Top Bottom