Root [Boost Mobile] Working ROMS/MODS/KERNELS/MODEMS/ECT for the Boost S3

wetbiker7 · Jun 16, 2014

codezer0 said:
Huh... what do you know? there was an updated PRL. 33031 instead of 33030 which I recall seeing forever.

And if the signal has been that way for this long, why hasn't it been addressed across four major revisions now?

If you're talking about weak AOSP ROM signal and it being addressed, it's just one of the inherent issues with AOSP based ROMS. Bro, it's been that way for 4 years now that I know of. I noticed it with CM7 on my Prevail. If it were something simple, it would've been taken care of by now.

Rxpert83 · Jun 17, 2014

AOSP Roms don't lie about your signal strength.

Many stock roms do to make the carrier look better. Its really as simple as that in some cases

HiiiPowers · Jun 17, 2014

Rxpert83 said:
AOSP Roms don't lie about your signal strength.

Many stock roms do to make the carrier look better. Its really as simple as that in some cases

I've remember seeing that a while ago probably also read it somewhere but I've noticed in some cases Asop roms don't hold signals at all (at least the newer builds) in weak areas they disconnect and keep reconnecting and searching for the network all the time especially if I'm not connected to WiFi it wasn't an noticeable issue on the earlier builds of LS and omni but now it always happens while tw roms don't do this they lie a lot telling me I have almost 2 sometimes 3bars and 3g while I know I have 1 bar and I'm on 1x lol but they stay connected to the network

wetbiker7 · Jun 17, 2014

HiiiPowers said:
I've remember seeing that a while ago probably also read it somewhere but I've noticed in some cases Asop roms don't hold signals at all (at least the newer builds) in weak areas they disconnect and keep reconnecting and searching for the network all the time especially if I'm not connected to WiFi it wasn't an noticeable issue on the earlier builds of LS and omni but now it always happens while tw roms don't do this they lie a lot telling me I have almost 2 sometimes 3bars and 3g while I know I have 1 bar and I'm on 1x lol but they stay connected to the network

Kouma, Bloodawn, and I talked about this a few years ago when I was new to Android and they broke it down for me how AOSP based ROMS actually do provide a more accurate signal display.

The fact still remains that AOSP based ROMS do not pick up signal as well as stock based ROMS. I've flashed AOSP based ROMS and had no signal at all. I mean the big red X. No signal. I would then flash a stock based ROM and be able to make calls. I've had this happen with my Prevail, Marquee, and S3.

Thankfully new towers are being added and the older ones are being upgraded daily. They are working on the one in my area again. It looks like they've done something to help boost the signal again which is nice to see.

alpha2k · Jun 17, 2014

HiiiPowers said:
I've remember seeing that a while ago probably also read it somewhere but I've noticed in some cases Asop roms don't hold signals at all (at least the newer builds) in weak areas they disconnect and keep reconnecting and searching for the network all the time especially if I'm not connected to WiFi it wasn't an noticeable issue on the earlier builds of LS and omni but now it always happens while tw roms don't do this they lie a lot telling me I have almost 2 sometimes 3bars and 3g while I know I have 1 bar and I'm on 1x lol but they stay connected to the network

I wouldn't say either one lies or is deceiving at all, Just a simple fact, anything aside from TW roms simply just don't have the signal strength. I've tried almost every rom out for both the s2 and this s3 and everything always had a lower bar/signal than TW did. Not sure exactly or what TW does different than others do not it works whatever it is.

The fact that even the cm team can't replicate the signal the same as TW does says it's deeper rooted than they can even fix. And this is coming from a big team to, they have even expanded this last yr adding a few more people, makers of very popular big roms are in the cm team now and they still haven't fixed it like TW is.

I just ended up chalking it up to the fact that some things non TW just aren't as good as TW itself is, while they do work they just don't work as good.

HiiiPowers · Jun 18, 2014

Yeah you'll are both right I just broke it down to both roms have positives and negatives it just all depends on what you want and how much your willing to sacrifice

For example even on Android 4.4 tw wicked x my battery will drain in about 4 maybe 5 hrs if I don't underclock it and use a different launcher because tw is a battery annihilator lol but its okay I just use my battery case and keep the phone undercooked and use the Google now launcher
This doesn't mean the rom isn't any good and vice versa for Asop roms they have bugs and signals usually not picking up as good and maybe it's just me but the camera also seems to be lacking compared to tw camera

wetbiker7 · Jun 18, 2014

Hey everyone. I just found something a few of you may find helpful.

Do you have an extended battery?

Does it seem like it's not holding a charge or lasting as long as it used to?

I did.

I have a 7000mAh Zerolemon. After switching to Kit Kat, I noticed that my battery wasn't lasting as long as it did in the past. Well, I found out why. My phone registered a full 100% charge. I went into data/system / and deleted batterystats.bin. I then rebooted my phone and found that it was now registering 80% for the battery. I've left it on the charger and is now up to 90% and still charging.

My phone was registering a 100% charge when in fact its true charge was only 80%. I was losing 20% of my battery. Sucks huh? Yep. I thought so too. Lol

I just found this out and wanted to share it with everyone. All you need to do is let your phone charge until it reads 100%. Then, go in and delete the batterystats.bin and reboot.

Rxpert83 · Jun 18, 2014

alpha2k said:
The fact that even the cm team can't replicate the signal the same as TW does says it's deeper rooted than they can even fix. And this is coming from a big team to, they have even expanded this last yr adding a few more people, makers of very popular big roms are in the cm team now and they still haven't fixed it like TW is.

I just ended up chalking it up to the fact that some things non TW just aren't as good as TW itself is, while they do work they just don't work as good.

This "issue" has been around for years, and its not just on Samsung devices.

CM isn't trying to replicate touchwizs signal strength, they're trying to display it accurately. On some touchwiz Roms you'll even see signal strength indicator fixes listed in the OP to show you true strength.

Theres documented cases all over. Sprint in particular is bad about this. On stock based ROMs on many devices the signal strength displayed is actually the voice strength, not the data strength. There's even open source AOSP code for the nexus 5 detailing lying about being on 1x vs 3g, as well as cases lying about signal strength.

http://www.androidpolice.com/2013/1...r-on-your-sprint-nexus-5-may-be-lying-to-you/

http://s4gru.com/index.php?/topic/2...to-determine-your-actual-lte-signal-strength/

Flashing a Rom does not change the radios, only how they interact or display information from them. It therefore follows that a ROM by itself can't change the strength of the signal its receiving from a tower.

unotlikeme · Jun 18, 2014

wetbiker7 said:
Hey everyone. I just found something a few of you may find helpful.

Do you have an extended battery?

Does it seem like it's not holding a charge or lasting as long as it used to?

I did.

I have a 7000mAh Zerolemon. After switching to Kit Kat, I noticed that my battery wasn't lasting as long as it did in the past. Well, I found out why. My phone registered a full 100% charge. I went into data/system / and deleted batterystats.bin. I then rebooted my phone and found that it was now registering 80% for the battery. I've left it on the charger and is now up to 90% and still charging.

My phone was registering a 100% charge when in fact its true charge was only 80%. I was losing 20% of my battery. Sucks huh? Yep. I thought so too. Lol

I just found this out and wanted to share it with everyone. All you need to do is let your phone charge until it reads 100%. Then, go in and delete the batterystats.bin and reboot.

I noticed this with my new s3 my battery dies so quickly thanks for the fix biker waiting for 100% now to clear those stats and see whats up.

Thats some valuable info right there you should add it to the MISCELLANEOUS section!

wetbiker7 · Jun 18, 2014

unotlikeme said:
I noticed this with my new s3 my battery dies so quickly thanks for the fix biker waiting for 100% now to clear those stats and see whats up.

Thats some valuable info right there you should add it to the MISCELLANEOUS section!

10-4. I'll get it added to the miscellaneous section.

I knew something was up. It blew my mind to find out I was actually losing a full 20%. I'm fully charged now. It'll be interesting to see how much time I get on this charge.

___________________

UPDATE!!

UPDATED THE MISCELLANEOUS SECTION WITH INFO ON HOW TO RESET YOUR BATTERYSTATS.BIN.

Rxpert83 · Jun 18, 2014

wetbiker7 said:
Hey everyone. I just found something a few of you may find helpful.

Do you have an extended battery?

Does it seem like it's not holding a charge or lasting as long as it used to?

I did.

I have a 7000mAh Zerolemon. After switching to Kit Kat, I noticed that my battery wasn't lasting as long as it did in the past. Well, I found out why. My phone registered a full 100% charge. I went into data/system / and deleted batterystats.bin. I then rebooted my phone and found that it was now registering 80% for the battery. I've left it on the charger and is now up to 90% and still charging.

My phone was registering a 100% charge when in fact its true charge was only 80%. I was losing 20% of my battery. Sucks huh? Yep. I thought so too. Lol

I just found this out and wanted to share it with everyone. All you need to do is let your phone charge until it reads 100%. Then, go in and delete the batterystats.bin and reboot.

That is strange :thinking:

Isn't the batterystats.bin supposed to be wiped on its own each time the phone reaches a full charge?

I wonder if you might see the same results if you charged it while powered down.

wetbiker7 · Jun 18, 2014

Rxpert83 said:
That is strange

Isn't the batterystats.bin supposed to be wiped on its own each time the phone reaches a full charge?

I wonder if you might see the same results if you charged it while powered down.

I tried it powered down and it said my battery was fully charged. I turned it on and the battery immediately registered 70%.

Somehow something isn't working the way it should. The test above was done with Wicked-X.

I flashed the Singularity ROM and it registered 100%. I cleared battery stats, rebooted and the battery registered 80%.

I will continue to keep and eye on it and report.

DragonSlayer95 · Jun 18, 2014

If your using a ZL 7k battery it's a known issue that's been brought up several times around here and xda.

Only flaw ZL has.

steelyus1 · Jun 19, 2014

Sorry been on vacay driving so not able to chime in while reading the threads.

Dragon slayer is right, same issue with my ZL 7K. Will have to find the thread, but read on the ZL forum that its an issue with many models.

Its the batt and not the ROMs.

wetbiker7 · Jun 19, 2014

I

steelyus1 said:
Sorry been on vacay driving so not able to chime in while reading the threads.

Dragon slayer is right, same issue with my ZL 7K. Will have to find the thread, but read on the ZL forum that its an issue with many models.

Its the batt and not the ROMs.

The funny thing is that I didn't start having trouble until I flashed the Kit Kat update. Lol

I've been switching back and forth between my stock batteries and the ZL and I haven't really noticed it until now. Hmmmmmm.

I wonder if a battery calibration would work? Yeah, I know. Some people say that BS. I'm pretty sure most battery calibration apps just delete the battery stats. LMAO. Who knows. I do have a battery app which allows me to choose the mAh of my battery. I may try it.

smith058 · Jun 19, 2014

wetbiker7 said:
Hey everyone. I just found something a few of you may find helpful.

Do you have an extended battery?

Does it seem like it's not holding a charge or lasting as long as it used to?

I did.

I have a 7000mAh Zerolemon. After switching to Kit Kat, I noticed that my battery wasn't lasting as long as it did in the past. Well, I found out why. My phone registered a full 100% charge. I went into data/system / and deleted batterystats.bin. I then rebooted my phone and found that it was now registering 80% for the battery. I've left it on the charger and is now up to 90% and still charging.

My phone was registering a 100% charge when in fact its true charge was only 80%. I was losing 20% of my battery. Sucks huh? Yep. I thought so too. Lol

I just found this out and wanted to share it with everyone. All you need to do is let your phone charge until it reads 100%. Then, go in and delete the batterystats.bin and reboot.

Every time you flash a rom or restore a rom you should reset your battery stats file...

When you made a backup of your rom your battery was at a different charge than when you restored that same rom. Same goes for when a Dev releases a rom it was saved at a different charge than when you flashed it...

Best way to go is to always backup/restore/flash on a 100% charge or else after a flash completely charge then delete the file then run the battery completely dead then charge more than 100% again. First option is much easier and will keep it close enough to accurate.

Unless Rxpert83 is right and it does actually automatically delete the file, I never heard that myself. But I have noticed batteries not lasting as long after some flashes and restores with all my phones all the way back to the prevail. I learned this trick on the transformer, there are also apps to reset the stats too.

steelyus1 · Jun 19, 2014

wetbiker7 said:
I

The funny thing is that I didn't start having trouble until I flashed the Kit Kat update. Lol

I've been switching back and forth between my stock batteries and the ZL and I haven't really noticed it until now. Hmmmmmm.

I wonder if a battery calibration would work? Yeah, I know. Some people say that BS. I'm pretty sure most battery calibration apps just delete the battery stats. LMAO. Who knows. I do have a battery app which allows me to choose the mAh of my battery. I may try it.

My stock batt does fine. And my ZL has been doing it since the 4.3 update.

Never had a calibration do anything for me personally. But hey, means it won't hurt to try. Lol

Hopefully its just the 4.3+ firmware that is the issue. Kinda like this batt.

wetbiker7 · Jun 19, 2014

Thanks for the input guys.

Also..... I just did a little research and I was correct. Most battery calibration apps just delete the batterystats.bin. Lol. Pressing one tab to calibrate is easier than navigating to the actual bin to do it. That's for sure. LOL.

I need to cycle my battery a few times too. I say I started having this issue when I flashed the Kit Kat update. Well, that's when I started swapping from the ZL to stock batteries a lot too. It may just need a good old battery cycling.

This will take awhile but I'll report back with my findings.

Rxpert83 · Jun 19, 2014

My comments were based on those expressed by google engineer Diane Hackborn here:
https://plus.google.com/105051985738280261832/posts/FV3LVtdVxPT

In that post, she says batterystats.bin is reset every time you charge your phone to completion, and the phone does not get battery % remaining from that file. Its basically used for the app percentages used in the battery usage screen, and that's it.

It also means for most cases wiping battery stats (with an app or manually) is useless

. Its wiped each time the phone charges above 90%.
--------------------------------------------------------
Everything following ive been adding on as Edits from the comments of that post:

Okay everyone, let me say again: battery stats has NOTHING AT ALL to do with the battery level reported to you. Nothing. Zero. Nada. Zip. In fact, the code that is creating it, is actually filling in some information contained in it from the battery level that is being reported from lower-level parts of the system (to show the chart of battery level). It has NO impact on the battery level that is reported. It sits on top of what is being reported.

And why trust her on all of this?

I will say that I don't know for sure what all of the various devices are doing... however, I know exactly what the battery stats code on the G1, Nexus One, and Nexus S does. I wrote it. And I can assure you there is nothing it does that has any impact on battery level reporting or battery draining (aside from whatever work the code itself does that would use power).

Basically, battery % comes from the battery itself in "smart" batteries or from the kernel calculating it.

There are different ways that the battery level can be reported. Two major ones I know of are either an additional line with the battery allowing the battery itself to report its level (often called smart batteries), or where low-level code in a kernel driver and/or the radio processor monitors what is going on to approximate power use and thus battery level. Clearly the former is better, but there are definitely Android devices with the later. Neither of these are things anything in the Android platform itself are aware of; they come from lower-level hardware-specific parts.

Also, even with smart batteries, I believe they are not reporting the actual level but still approximating it -- they just have a power gauge on the battery to determine exactly how much power has been drawn from it, and knowing the total power of the battery can then compute how much power is left. These also may need to take into account degradation of the battery over time (as the amount of power it can hold goes down) and can misreport if something they aren't measuring happens.



- -----_------------------------------------------------

So what does all of this mean? Its likely either the zero lemon is reporting its own charge levels wrong, or the kernel is calculating the charge wrong because its expecting a different sized battery than is actually there.

Remember - battery percentages are nothing but estimates. Estimates are always based on a set of assumptions. If any of those assumptions are wrong - the estimate is wrong.

wetbiker7 · Jun 19, 2014

Rxpert83 said:
My comments were based on those expressed by google engineer Diane Hackborn here:
https://plus.google.com/105051985738280261832/posts/FV3LVtdVxPT

In that post, she says batterystats.bin is reset every time you charge your phone to completion, and the phone does not get battery % remaining from that file. Its basically used for the app percentages used in the battery usage screen, and that's it.

It also means for most cases wiping battery stats (with an app or manually) is useless

Edit: she also says this in the comments of that post

And why trust her on all of this?

Basically, battery % comes from the battery itself in "smart" batteries or from the kernel calculating it.

I'm not saying she's wrong or anything. I'm just going on what I am seeing with my phone.

My phone reported it had reached a full charge yesterday. I wipe the bin and rebooted. My battery then displayed an 80 % charge. I put it back on the charger and let it finish charging.

I've still got at least another day or so before I'll charge it again. I'm hoping it will allow a full charge this time. We'll see.

Rxpert83 · Jun 19, 2014

wetbiker7 said:
I'm not saying she's wrong or anything. I'm just going on what I am seeing with my phone.

My phone reported it had reached a full charge yesterday. I wipe the bin and rebooted. My battery then displayed an 80 % charge. I put it back on the charger and let it finish charging.

I've still got at least another day or so before I'll charge it again. I'm hoping it will allow a full charge this time. We'll see.

I'm not disagreeing with what you're seeing, my intent was just providing the background for why Im confused by that seemingly having an effect.

wetbiker7 · Jun 19, 2014

Rxpert83 said:
I'm not disagreeing with what you're seeing, my intent was just providing the background for why Im confused by that seemingly having an effect.

I'm somewhat familiar with information similar to what you provided regarding the batterystats.bin. That's why I'm confused too. The chances of it happening on 2 separate ROMS are very slim. That's why I am leaning towards an issue with the update itself. It's possible that it's having trouble gaging the larger extended batteries.

Here's the thing. I not only waited until my phone registered 100% in the status bar , I waited until the phone actually gave me the battery's full charge notification in the pull down. That's when I wiped the bin, rebooted and it was showing 80%.

wetbiker7 · Jun 19, 2014

UPDATE!!

The Conquest: Singularity ROM has been updated to v3.0.

If any of you are looking for a TW ROM that has an AOSP twist, this is a ROM you may want to check out. It comes with an Aroma installer which allows you to choose whether or not you want AOSP apps or TW apps.

I have ran this ROM and it runs great.

Comadose and Xposed Framework work well with it too.

cwhatever · Jun 19, 2014

wetbiker7 said:
I'm somewhat familiar with information similar to what you provided regarding the batterystats.bin. That's why I'm confused too. The chances of it happening on 2 separate ROMS are very slim. That's why I am leaning towards an issue with the update itself. It's possible that it's having trouble gaging the larger extended batteries.

Here's the thing. I not only waited until my phone registered 100% in the status bar , I waited until the phone actually gave me the battery's full charge notification in the pull down. That's when I wiped the bin, rebooted and it was showing 80%.

Mine did that too a while back. I got a zerolemon charger and a 2700 ZL spare battery. I use the big one till dead, then charge and then put in small one, which will last 2 days. Then put big one in (and charge little one), it will almost last a week, even with heavy use here and there. So I can't say as I have not plugged my phone in to charge in about 4 months.

HiiiPowers · Jun 19, 2014

wetbiker7 said:
UPDATE!!

The Conquest: Singularity ROM has been updated to v3.0.

If any of you are looking for a TW ROM that has an AOSP twist, this is a ROM you may want to check out. It comes with an Aroma installer which allows you to choose whether or not you want AOSP apps or TW apps.

I have ran this ROM and it runs great.

Comadose and Xposed Framework work well with it too.

I saw Asop twist downloading now lol

Root [Boost Mobile] Working ROMS/MODS/KERNELS/MODEMS/ECT for the Boost S3

Extreme Android User

Dr. Feelgood

Android Enthusiast

Extreme Android User

Android Expert

Android Enthusiast

Extreme Android User

Dr. Feelgood

Android Enthusiast

Extreme Android User

Dr. Feelgood

Extreme Android User

Resident Air Bender

Well-Known Member

Extreme Android User

Android Expert

Well-Known Member

Extreme Android User

Dr. Feelgood

Extreme Android User

Dr. Feelgood

Extreme Android User

Extreme Android User

Life Goes On

Android Enthusiast

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads