hey all, couldnt search forums since its disabled. so like my title says, my phone turns off whenever. the samsung logo comes up and turns off. it happens every so often but nothing annoying. to get it back on is either take battery out or plug to charger and turn it on. when i did this, it gave me the searching for battery thing. this leads me to believe it could be battery? it happens whether the battery is 90% or 20%. anybody have this problem? my phone is rooted using juggs 5.0. phone is just over a month old so wonder if i can get a replacement battery to ruled that one? thanks for the help..
Mines does the same thing except it only reboot when its on charge, and all my contacts dissapear
@OP: Try flashing a different ROM.
Juggernaut has pretty aggressive UVing that not all phones might like.
It happened to me just today. I tried opening Facebook and for whatever reason it FCed. So I reopened it and my phone just turned off. I had to hold the power button for 15 seconds before I felt a vibration and it was alive again. Not sure what the issue is but it's safe to say you're not the only one experiencing this
NJ_RAMS_FAN said:
hey all, couldnt search forums since its disabled. so like my title says, my phone turns off whenever. the samsung logo comes up and turns off. it happens every so often but nothing annoying. to get it back on is either take battery out or plug to charger and turn it on. when i did this, it gave me the searching for battery thing. this leads me to believe it could be battery? it happens whether the battery is 90% or 20%. anybody have this problem? my phone is rooted using juggs 5.0. phone is just over a month old so wonder if i can get a replacement battery to ruled that one? thanks for the help..
Click to expand...
Click to collapse
Random reboots are usually a sign of too aggressive of undervolting. If it's not happening under heavy CPU load and is just happening during standby/sleep phases, then you're just barely on the edge of too much undervolting. Download system tuner from the market and go to voltages in the main menu then knock up the voltage one step (+12.5mV). You should be fine then.
For reference, you can compare your voltages to this list of stock voltages to see what Jugs' global undervolt is. I'm not too familiar with Jugs v5.0:
http://forum.xda-developers.com/showthread.php?t=1523064
yoft1 said:
Random reboots are usually a sign of too aggressive of undervolting. If it's not happening under heavy CPU load and is just happening during standby/sleep phases, then you're just barely on the edge of too much undervolting. Download system tuner from the market and go to voltages in the main menu then knock up the voltage one step (+12.5mV). You should be fine then.
For reference, you can compare your voltages to this list of stock voltages to see what Jugs' global undervolt is. I'm not too familiar with Jugs v5.0:
http://forum.xda-developers.com/showthread.php?t=1523064
Click to expand...
Click to collapse
cool. I give this a try. The last time it turned off was right after I used gps. yesterday I was just browsing. thanks again.
Are you overclocking? If so what freqs/governor? Mine would do this when I would clock it too high for too long. May be an undervolting problem as well.
AaronPauley said:
Are you overclocking? If so what freqs/governor? Mine would do this when I would clock it too high for too long. May be an undervolting problem as well.
Click to expand...
Click to collapse
Your overclocking issue is actually still an undervolting issue. Your phone would reboot after overclocking for long periods of time because the processor wasn't getting supplied enough voltages for those higher clock speeds.
Undervolting isn't a linear process: if you run a global -50mV undervolt and cap your processor at 1.5Ghz, that doesn't mean that you can run a -50mV undervolt at a 1.8Ghz cap. For example, I'm currently undervolted -112.5mV at 1.35Ghz but if I bump my processor to 1.8Ghz, my phone reboots immediately because -112.5mV for 1.8Ghz is way too big of an undervolt.
yoft1 said:
Your overclocking issue is actually still an undervolting issue. Your phone would reboot after overclocking for long periods of time because the processor wasn't getting supplied enough voltages for those higher clock speeds.
Undervolting isn't a linear process: if you run a global -50mV undervolt and cap your processor at 1.5Ghz, that doesn't mean that you can run a -50mV undervolt at a 1.8Ghz cap. For example, I'm currently undervolted -112.5mV at 1.35Ghz but if I bump my processor to 1.8Ghz, my phone reboots immediately because -112.5mV for 1.8Ghz is way too big of an undervolt.
Click to expand...
Click to collapse
Thanks for the clarification. I've not really dabbled in undervolting much, and haven't been too concerned with overclocking since the ol' mt3g days. I'm definitely going to read more about it. I've found that for my s2, stock kernel w/ stock frequency set and governor have worked best. Every device is different they say. Thanks your way for the knowledge. Always appreciated.
yoft1 said:
Your overclocking issue is actually still an undervolting issue. Your phone would reboot after overclocking for long periods of time because the processor wasn't getting supplied enough voltages for those higher clock speeds.
Undervolting isn't a linear process: if you run a global -50mV undervolt and cap your processor at 1.5Ghz, that doesn't mean that you can run a -50mV undervolt at a 1.8Ghz cap. For example, I'm currently undervolted -112.5mV at 1.35Ghz but if I bump my processor to 1.8Ghz, my phone reboots immediately because -112.5mV for 1.8Ghz is way too big of an undervolt.
Click to expand...
Click to collapse
Thanks for the clarification. I've not really dabbled in undervolting much, and haven't been too concerned with overclocking since the ol' mt3g days. I'm definitely going to read more about it. I've found that for my s2, stock kernel w/ stock frequency set and governor have worked best. Every device is different they say. Thanks your way for the knowledge. Always appreciated.
Related
i have used the search and not found any solid info
what are the benefits of it if any
I haven't heard of people undervolting their fone, although i haven't looked to much.
This would mean though reducing the power that the CPU gets. I would imagine this increases battery life among other things.
Your right about what it is, but almost every custom rom/ kernel is undervolted in development section.
Sent from my HTC Desire using XDA App
Undervolting means, the CPU (or hardware in the phone) gets lower voltages, thus saving more battery & not loosing performance.
Undervolting is a process which reduces the excess "voltage" given to the CPU using a software. This is widely used as a cooling solution and in my opinion more effective than any other cooling solution available (thermal paste, cooling pad, etc) at NO cost. Undervolting will NOT compromise performance at all. Underclocking and Overclocking (clock speeds) is whats responsible in regards to performance. Benchmarks will also prove that performance remains the same.
Click to expand...
Click to collapse
Not excess voltage but fully, manufacturer guaranteed, stable Core voltage to lower guesswork voltages which may or may not work and may or may not cause data loss/corruption.
------------------------------
- Sent via HTC Desire -
A cpu needs power for every 'clock cycle'. 1Ghz means there are a billion per second. IF you lower the voltage, there is less power used. But if you lower it too much, the cpu wo'nt be able to 'cycle its clock'...
So undervolting doesn't affect performance, since the cpu remains on 1Ghz. It decreases the power used, so you get better battery life.
Every single cpu is different, so HTC has chosen a default voltage that (shoud) work on all phones they sell. But your particular cpu could be able to work at a lower voltage. It's just a matter of trail and error. Decrease the voltage until the cpu stops working, then higher it a bit. That way you've undervolted your cpu so it uses the least power.
koenvbeek said:
A cpu needs power for every 'clock cycle'. 1Ghz means there are a billion per second. IF you lower the voltage, there is less power used. But if you lower it too much, the cpu wo'nt be able to 'cycle its clock'...
So undervolting doesn't affect performance, since the cpu remains on 1Ghz. It decreases the power used, so you get better battery life.
Every single cpu is different, so HTC has chosen a default voltage that (shoud) work on all phones they sell. But your particular cpu could be able to work at a lower voltage. It's just a matter of trail and error. Decrease the voltage until the cpu stops working, then higher it a bit. That way you've undervolted your cpu so it uses the least power.
Click to expand...
Click to collapse
Very sensible answer..Thanks
koenvbeek said:
A cpu needs power for every 'clock cycle'. 1Ghz means there are a billion per second. IF you lower the voltage, there is less power used. But if you lower it too much, the cpu wo'nt be able to 'cycle its clock'...
So undervolting doesn't affect performance, since the cpu remains on 1Ghz. It decreases the power used, so you get better battery life.
Every single cpu is different, so HTC has chosen a default voltage that (shoud) work on all phones they sell. But your particular cpu could be able to work at a lower voltage. It's just a matter of trail and error. Decrease the voltage until the cpu stops working, then higher it a bit. That way you've undervolted your cpu so it uses the least power.
Click to expand...
Click to collapse
How would one go about under volting .i have tried everything suggested to me and nothing really seems to make a difference
Sent from my HTC Desire using XDA App
Most kernels are undervolted and unless you can compile the kernel for yourself you are stuck with the values given by the creator. There are two exceptions for this, HAVS kernels which automaticly chose a voltage depending on temperature and some other stuff and SVS kernels with snq-'s volt selection interface (found in Leedroid and maybe some other kernels/roms).
So what exactly have you tried and what did you expect to see? Because the difference won't be that noticeable.
TheGhost1233 said:
Most kernels are undervolted and unless you can compile the kernel for yourself you are stuck with the values given by the creator. There are two exceptions for this, HAVS kernels which automaticly chose a voltage depending on temperature and some other stuff and SVS kernels with snq-'s volt selection interface (found in Leedroid and maybe some other kernels/roms).
So what exactly have you tried and what did you expect to see? Because the difference won't be that noticeable.
Click to expand...
Click to collapse
I have tried battery calibration, using app watch dog to let me know which apps are using excessive CPU. Putting my brightness down to 10%, making sure not everything is synced, the only thing synced is beautiful widgets every 4 hours. And just about everything else that has been put forward to me. Here's another example I just taken my phone off charge at 100% and wrote this and I'm now at 73 %. And its only taken2 mins to write
Sent from my HTC Desire using XDA App
adz63 said:
I have tried battery calibration, using app watch dog to let me know which apps are using excessive CPU. Putting my brightness down to 10%, making sure not everything is synced, the only thing synced is beautiful widgets every 4 hours. And just about everything else that has been put forward to me. Here's another example I just taken my phone off charge at 100% and wrote this and I'm now at 73 %.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
So in short you havent tried any kernel with undervolting at all!
Well that all has nothing to do with undervolting, but (extra) undervolting will not fix the drain problem you have.
Do you use setCPU cause your sig says you run at 1113MHz, which cause higher consumption. Also did you set your wifi sleep policy to never(setting-wireless and network-wifi settings-press menu-advanced-wifi sleep police).
At the moment I have the havs kernel that comes with oxygen 2.0 rc6. I have posted another topic about is the kendal good for battery life etc and no1 has told that another kendal would make anything better
Sent from my HTC Desire using XDA App
TheGhost1233 said:
Well that all has nothing to do with undervolting, but (extra) undervolting will not fix the drain problem you have.
Do you use setCPU cause your sig says you run at 1113MHz, which cause higher consumption. Also did you set your wifi sleep policy to never(setting-wireless and network-wifi settings-press menu-advanced-wifi sleep police).
Click to expand...
Click to collapse
@TheGhost1233, how exactly does one decide which kernel suits us best..
Eg: I see two undervolted kernels (I think) at 875 and 925 mV. I have no idea how to decide. Trial and error?
Froyo Kernel [email protected] min
Froyo Kernel [email protected] min
@droidzone Yes trial and error. The mentioned voltage is the lowest the cpu will get at 245MHz. Not all devices are stable with 875mV (you will know if your phone freezes up) so then you move up to the 925mV min. Other than the voltage there is no difference between 875mV or 925mV.
With the HAVS kernels it can take a while before you notice the freezes cause the voltage is dynamic, so be careful if you need your phone as a alarm clock.
So I just installed "SyndicateROM Frozen 1.1.1 (Hajime-taisho)". It is running great! My QS score is = 1753. So now I loaded SetCPU and tried to overclock it to 1.2ghz. Well the thing ran great and got a QS score of = 2582!! But the problem I have is as soon as the screen shuts off (either by the 30sec time out or by manually hitting the power button) it will not come back on. The thing dies! No power at all! I mean NOTHING! I have to take the battery out and restart. Then it comes up runs great... until the screen goes off. I set the screen with "Stay awake" from the market and the best works great.. it only happens then the screen goes off... and I mean the second it goes off. I don't get it? The kernel is the stock one with the rom (and it says its good to overclock with) Twilight Zone V1.1.1. Is the epic really that bad for overclocking? My nook color is running at 1.3ghz and loving it! Any help?
The answer is in the 1.1.1 post #5. Uninstall SetCPU and install Voltage Control. Set to 200-1300mhz on conservative. Please be very, very, very careful with undervolting. Some phones don't like it at all.
wow thanks man. I read that 6 times and missed that one line. I overclocked it and my QS score was - 2058. that's wayyyy under what setcpu was giving me. I wounder if useing SetCPU with conservative on wold work? I was using on demand. I'm going to leave it on 1.2ghz. no need to push it for such a low increase.
NissanNick said:
wow thanks man. I read that 6 times and missed that one line. I overclocked it and my QS score was - 2058. that's wayyyy under what setcpu was giving me. I wounder if useing SetCPU with conservative on wold work? I was using on demand. I'm going to leave it on 1.2ghz. no need to push it for such a low increase.
Click to expand...
Click to collapse
Run quadrant for a half hour, if you'd like. You'll get a dozen funky scores of which none will make any sense in relation to what you just watched. Obviously the more things you turn off, the higher it'll go. People do point out it seems relative to nothing.
The problem is you had minimum set to 100 Mhz on SetCPU and that causes sleep of death on a lot of phones. Change it to 200 Mhz. Also unless you want bragging rights, don't put much faith in benchmarks....how does the phone "feel" to you? I am on Bonsai at 1120 and it "feels" faster and smoother than an OC kernel at 1.3Ghz.
kennyglass123 said:
The problem is you had minimum set to 100 Mhz on SetCPU and that causes sleep of death on a lot of phones. Change it to 200 Mhz. Also unless you want bragging rights, don't put much faith in benchmarks....how does the phone "feel" to you? I am on Bonsai at 1120 and it "feels" faster and smoother than an OC kernel at 1.3Ghz.
Click to expand...
Click to collapse
The minimum wasn't a problem it's the "on demand" settting with the kernel SRF uses that causes the sleep of death
I had my minimum set to 100 with conservative on and it woke up evertime. The second you switch it to on demand and kill the screen its forced reboot time lol.
Edit: Even though now...I can't recreate the screen of death...even using 100 minimum on demand with SRF 1.1.1 Twilight 1.1.1.....wierd....
im now using a custom rom with the overclock kernel... i set my phone to "1.4ghz" with AnTuTu... its working great now... no more fps lags on the games i play... and no crashes... im just curious about one thing? will it break the phone in any way? its not heating up or anything atm... i mean i have experienced phone heat on my sensation xe... that phone gets really hot STOCK....
i dont want to break my play... i really like it compared to other phones in the market right now(the only one with gamepads)... its my first time ocing a phone btw...
If its not noticably hot (the battery too) constantly then your fine, just bare in mind try not to push it past 1.6ghz i found my phone didnt last very long at that speed.
The only thing with oc its that it shortens the life of your cpu obviously depending on how much you oc it....and it drains more battery but its not that big of a deal
Defy39 said:
If its not noticably hot (the battery too) constantly then your fine, just bare in mind try not to push it past 1.6ghz i found my phone didnt last very long at that speed.
Click to expand...
Click to collapse
what do you mean by it didnt last very long? did it break the phone?
Basically, my phone is overclocked to 2.0 GHz with smartass scaling with max 800MHz interactive scaling when screen turned off. It works great! Lasts 2~3 days without gaming (5 to 7 days with airplane mode on) and 4~8 hours of hardcore gaming with full charge (6~12 with airplane mode on). I recommend using an extended battery (I haven't, yet) if you are doing so. And it also involves luck. Even if it is the same model, color, etc. some CPUs are more capable than others.
still testing my phone under 1.4ghz seems stable...
DanielEGVi said:
Basically, my phone is overclocked to 2.0 GHz with smartass scaling with max 800MHz interactive scaling when screen turned off. It works great! Lasts 2~3 days without gaming (5 to 7 days with airplane mode on) and 4~8 hours of hardcore gaming with full charge (6~12 with airplane mode on). I recommend using an extended battery (I haven't, yet) if you are doing so. And it also involves luck. Even if it is the same model, color, etc. some CPUs are more capable than others.
Click to expand...
Click to collapse
is it normal for the phone to be abit hotter than when it was running stock???
btw how does smartass compare to ondemand?? smartass tends to get lower benchmark scores than on demand
seagheart89 said:
is it normal for the phone to be abit hotter than when it was running stock???
btw how does smartass compare to ondemand?? smartass tends to get lower benchmark scores than on demand
Click to expand...
Click to collapse
Yes ofc its normal - as each CPU/GPU creates heat based on the load it takes....
So the higher u OC the hotter it gets - thats why in former days OC was quite dangerous
In todays times cpu normaly 1st get unstable, and then has a safety function to shutdown if it gets too hot. (no warrenty that its the same for all chips)
smartass doesnt switch frequencies at once like on demand (e.g. instant from 200mhz to 1000mhz) but it tries to predict the needed power somehow so the whole switching is done in more steps... (as far as I remember)
So yes its performace is a bit below the on demand - but should not be that noticable - but it will also save your battery.
I'm wondering if anyone's undervolted and to what values.
I'm also wondering waht the deafult values are and if they change per kernel.
Is there a way to disable SetCPUs undervolting settings?
Has anyone improved battery life with profiles? On the Eris this was the only way to get usable battery life.
Or not. I gave up undervolting after I actually compared battery life at stock values vs undervolted (on my old phone, sgs4g) and discovered it does nothing for battery life.
Edit: undervolting "might" marginally increase standby battery life, but considering how good this phone already does... it certainly won't increase actual screen on usage.
Sent from my Galaxy Nexus using xda premium
Depends how low you under volt. Got more battery life, maybe about an hour, after finding optimal battery life on my gfs Gnex.
If you don't under volt correctly, of course it won't improve battery life.
From my sexy white, Nocturnaled HTC One X
If you're not overly comfortable with undervolting, then using one of the many kernels with Smart Reflex will do a mild undervolt for you. If you are comfortable, then the only way to find numbers good for your phone is to try and test. I tweaked mine down to the point that I was occasionally getting hot boots when the screen was off and media was playing. Tweaking the numbers back up added the needed stability. Even little things like kernel or ROM revisions can change what voltage is or isn't stable. Another example is that when I updated my Jellybro CM10 version the other night, along with updating leankernel from 4.1.0exp3 to 4.2.0, I had to increase a few of my voltages to avoid hot boots.
Just for example numbers, here are mine:
Code:
1350MHz -- 1200mV
1200MHz -- 1150mV
920MHz -- 1050mV
700MHz -- 950mV
350MHz -- 825mV
These numbers will vary from device to device and even between ROM/kernel combinations, so don't use them as hard fact.
Thanks. On a phone like this it might not make a huge difference but on the Eris (Where stock battery life could sometimes be 6 hours if you actually used your phone) an undervolted kernel with setcpu could turn those 6 ours into 48.
Thanks Cilraaz, I'll try those voltages out and benchmark a bit to see if they're stable for my system.
Two things I can say for sure:
1. you will have very limit battery gain by undervolting with Gnex, no matter how low you try.
2. undervolting will bring some stable issue if you get too low, like lose signal and reboot.
I am using Kernel Franco GPU 384 Stock rom on my 4.1.1 and did undervolting
Current configuration:
384Mhz
950mv
------------
729Mhz
1050mv
-----------
1036mhz
1125mv
----------
1228mhz
1275mv
-------------
I did not change the frequencies of overclocking, because I'm not using them.
I felt an improvement in battery consumption unless the unit is heating up.
Just curious - what kind of profiles are you using? I have a "Screen off" that's 350min and 700max. I figure that's fast enough f someone calls me.
I've read many times undervolting isn't worth it.
Hungry Man said:
Just curious - what kind of profiles are you using? I have a "Screen off" that's 350min and 700max. I figure that's fast enough f someone calls me.
Click to expand...
Click to collapse
I'm using the following with SetCPU: default (1350MHz-350MHz), charging, CPU temp > 64, and battery < 35%.
If you're using a kernel and governor that support hotplug, then you likely don't want to use a screen off profile. The combination of the two can tend to cause sleep-of-death or hot boots.
I Am Marino said:
I've read many times undervolting isn't worth it.
Click to expand...
Click to collapse
Most people don't want to spend the time to do it right.
I'm actually not used to the new kernels. I haven't messed with my eris in about a year and back them there was "smartass, on demand, performance," and some other one that clocked down instead of up
Can you explain th escreen off profile causing issues? I don't even know what hotplug is lol I've been out of Android for a long time.
Hungry Man said:
Can you explain th escreen off profile causing issues? I don't even know what hotplug is lol I've been out of Android for a long time.
Click to expand...
Click to collapse
Hotplug disables one of the CPU cores when the screen is off. Some governors, like hotplugx, will also attempt to disable a CPU core during periods of low CPU usage. For some reason, this combined with a screen off profile can cause some problems. I assume it's because of the "screen-off-max-freq" that Imoseyon mentions in the quote below.
Personally, I prefer the interactivex governor with leankernel by Imoseyon. From his kernel thread:
With interactiveX V2 (for gnexus), things are a bit different, since gnexus has built-in support for screen-off-max-freq for all its governors. I took the new interactive code in gnexus, added early_suspend support (screen off/on trigger), and then added logic to the code so the governor uses the phone's built-in hotplugging capability to turn off cpu1 when screen is off (and then turn it back on when screen comes back on). Cpu1 goes offline entirely - no idle, no sleep.
Click to expand...
Click to collapse
I think undervolting helps - my phone is running 728 - 1228 using the interactive governor, with voltages of 600 mV, 700 mV, and 800 mV (728 MHz, 1036 MHz, 1228 MHz respectively) and I haven't had any issues so far. I know there are some reports that say undervolting doesn't help much, but those are when people undervolt by like 50 mV, whereas here I'm going like 400 mV under lol. (Yes, smart reflex is off).
Thanks Cilraaz. Good to know.
So turning the screen-off profile could improve things? Honestly, my system does fine at 350mhz with screen off. Turning a core entirely off would probably help though.
If I use hotplugx governor that would disable one core when the screens off, right?
Hungry Man said:
If I use hotplugx governor that would disable one core when the screens off, right?
Click to expand...
Click to collapse
Hotplugx will disable a core when the screen is off or when there is low system load. Depending on your kernel/governor choice, other governors may do it also. On leankernel, for instance, interactivex will disable a core when the screen is off, but not on low system load.
Ok, thank you.
I haven't done any comparisons of before/ after since I undervolted/ underclocked first thing. But I was browsing for hours while listening to music while talking to a friend with GTalk. talked for about 1.5 hours with someone, Left it on overnight (10 hours), woke up, used it to talk (voice to text) to someone via GTalk, and it's 3:25PM right now and I still have a fair amount of battery life left.
I'd heard mixed things about the battery on this so I'm happy.
My voltages:
1650: 1300
1520: 1250
1350: 1175:
1200: 1125
920: 1000
700: 925
350: 900
I stress tested each one without a crash.
So I tried to underclock my One X to around 640 MHz and it was running VERY smoothly and stable with only 2 cores active. I was using the ViperX 2.2.1 ROM and the Kernel was the no OC NCX 0.99a. The battery life wasn't bad, but has anyone tried underclocking to 1 GHz or lower? If so, how is the battery life and what kernel and ROM did you use?
With SetCPU you can change the max. CPU, but why should you? When the phone doesn't need much processor power, it just scales down by itself.
So, it already has the best underclocker there is.
Mayby you could try undervolting to save even more battery, but that means the CPU can be somewhat less steady.
im trying to get my head around UVing / UCing my HOX. is there any guide around? im trying to search through the forum but still no luck.
ricopoetra said:
im trying to get my head around UVing / UCing my HOX. is there any guide around? im trying to search through the forum but still no luck.
Click to expand...
Click to collapse
underclocking means the CPU runs slower so should use less battery but slower CPU speeds also means to takes longer to preform tasks which could use more battery, check on google most places say its not worth it as that battery saved is tiny and not worth the drop in CPU performance.
undervolting however lowers the voltage that CPU uses while working this does save power and also lowers heat (less voltage less heat) but if you lower it to much then the CPU becomes unstable due to lack of power and well crashes and restarts the phone in most cases.
to get the best out of undervolting you need to lock the max CPU speed to each step (CPU speed, 300mhz, 600mhz and so on) and slower the voltage and then run a bench mark (like antutu) and see if its stable, if it is you lower the voltage again and repeat until it crashes at which point you have found the lowest voltage that the clock speed can handle so you jump up a voltage then more on to the next speed.
it takes along time but that would get you the best undervolt your phone and hardware could handle.
or you can just use the global to lower the voltage for every speed, this is much faster and much less time consuming but you don't get the most out of it.
for this you basically drop the voltage then use your phone for different things; browsing, games, benchmark and see if it crashes if not lower again till it does then go back up a step.
thanks for explaining. I'm getting some of the points that I missed Awhile ago. I guess I'm going to try the longer way of doing it.
Sent from my White HOX JB PA 2.10