Develop Bugs

[Q] ViciousMIUI-V4 bug or purpose?

Hey guys!
I just downloaded ViciousMIUI and installed on to my GNex, first the contacts app kept on crashing (Android.Process.Acore) but we all know how to fix that...
And then I noticied, that my on-screen controls had gone... I'm currently restoring my codename Android ROM, so I have got enough time to ask, if anyone else has had this problem with this ROM, or is it just my phone, again...
I would appreciate quick answers...

Your buttons should be there.. maybe a bad dl
Sent from my Galaxy Nexus using xda premium

joshnichols189 said:
Your buttons should be there.. maybe a bad dl
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Can't have been a bad dl... I downloaded using ROM Manager....
That's why I'm asking... I always dl my ROMs using ROM Manager, or with FF... And I have never had problems before...

Don't use ROM Manager - it's ****. Download it from the ROM thread, compare the md5 and flash it yourself. Don't rely on an app

Have you tried wiping everything and installing again. Sometimes all it need is flashing again for an error free rom
Sent from my Galaxy Nexus using XDA App

EddyOS said:
Don't use ROM Manager - it's ****. Download it from the ROM thread, compare the md5 and flash it yourself. Don't rely on an app
Click to expand...
Click to collapse
I've never had any problem using the app... And I haven't yet found the thread...

Move outside XDA once and a while
http://rootzwiki.com/topic/12774-rom-viciousmiui-v4-galaxy-nexus-223-weekly-02-05-2012-133pm-est/

Emhalwis said:
Have you tried wiping everything and installing again. Sometimes all it need is flashing again for an error free rom
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I have tried doing a factory reset... The flash was good, everything successful... I guess it just didn't copy the SystemUI Apk properly... I'll try it again, later on...

EddyOS said:
Move outside XDA once and a while
http://rootzwiki.com/topic/12774-rom-viciousmiui-v4-galaxy-nexus-223-weekly-02-05-2012-133pm-est/
Click to expand...
Click to collapse
Yeah and that link brought a **** load of ****! Buttons still not there, flashed it 5 times!!!! Pissed off, the only way I can use my phone, is by rebooting it, after I have exited an app... -.-" Seriously pissed off now! And this goes to any/everyone who is going to promote anything different than XDA:" **** YOU!"
Guess what I can do now... Reboot my phone, reinstall CND, flash the franco kernel again and why? Becuase this **** load of **** ROM doesn't work, like it should...
(Sorry for swearing so much, I'm pissed off)

familyguy59 said:
Yeah and that link brought a **** load of ****! Buttons still not there, flashed it 5 times!!!! Pissed off, the only way I can use my phone, is by rebooting it, after I have exited an app... -.-" Seriously pissed off now! And this goes to any/everyone who is going to promote anything different than XDA:" **** YOU!"
Guess what I can do now... Reboot my phone, reinstall CND, flash the franco kernel again and why? Becuase this **** load of **** ROM doesn't work, like it should...
(Sorry for swearing so much, I'm pissed off)
Click to expand...
Click to collapse
Its just you. Works for me.
Sent from my Galaxy Nexus using Tapatalk

XAviierG said:
Its just you. Works for me.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Well, that's great.... Then I'ts probably because I've got a contract device...
Well anyways, thx for answering ^^

familyguy59 said:
Well, that's great.... Then I'ts probably because I've got a contract device...
Well anyways, thx for answering ^^
Click to expand...
Click to collapse
It has nothing to do with being on contract. Basicly it is one if these options:
1) Bad download. This CAN happen from ROM manager also.
2) You messed up the install, you said something about messing with SystemUI so that may have been it.
3) Your phone is borked.....not likely at all.
My bet is 1 or 2.
Sent from my Galaxy Nexus using Tapatalk

What should i do with my brick?

So, i think i bricked my device. Downloaded caulkin rom and tried to flash it. when i booted into rogue rootbloater i flashed the rom from my downloads. my bad. why does it matter though whether or not i flash from internal or external memory. annnd ?

It doesnt matter if the rom is in the internal or sd unless dev says something about it in op. As far as your brick, im not understanding fully what you mean
Sent from my SPH-D710 using xda premium

What makes you think you're bricked? What happens when you try to power the phone on?

Rob4828 said:
It doesnt matter if the rom is in the internal or sd unless dev says something about it in op. As far as your brick, im not understanding fully what you mean
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
If I would have had a sd i would not have a brick right now though :/
I think. cause the new rom switched bootloaders and the new one only recog'ed the sd i think.

undefine4 said:
So, i think i bricked my device. Downloaded caulkin rom and tried to flash it. when i booted into rogue rootbloater i flashed the rom from my downloads. my bad. why does it matter though whether or not i flash from internal or external memory. annnd ?
Click to expand...
Click to collapse
what happens when you try to boot your phone?

_MetalHead_ said:
What makes you think you're bricked? What happens when you try to power the phone on?
Click to expand...
Click to collapse
It means my phone is locked in a "permanent" state of existence.

undefine4 said:
It means my phone is locked in a "permanent" state of existence.
Click to expand...
Click to collapse
so lets say after you pull battery you press the power button....nothing happens?

Pull the battery
Put it back in
press power and see what happens
-- You can also...
Pull the battery
Put the battery back in
press vol down + power and try to get into odin mode
If you can get into Odin mode, then you're not bricked.

no phone - cake.

undefine4 said:
no phone - cake.
Click to expand...
Click to collapse
Do you speak English ? They have ask what happens when you power on the phone and you respond with idiot junk .... Congratulations throw your phone out of a moving car jack a$$
Sent from my SPH-D710 using xda premium

undefine4 said:
no phone - cake.
Click to expand...
Click to collapse
Do you want help or not? The E4GT is a very difficult phone to brick and 9 times out of 10 when a noob thinks their phone is bricked, it's actually easily recoverable. But if you don't help us help you, you might as well just toss the phone down the garbage disposal.
Can you get into download mode?

Hahhahhahahahaa that's all I wanna say
Sent from my SPH-D710 using Tapatalk

Lol if you don't want to be helped then sell the phone to me. Should the bidding be started at ummm lets say $20.
$20 is a very expensive paperweight I think I'm offering more then enough lol
Epic 4G Touch perfected by Calk!

I think we're being trolled.

Great add one more thread that made me dumber for reading it. Stop it guys the last thing I need more of is dumb.
Sent from my SPH-D710 using Tapatalk

_MetalHead_ said:
I think we're being trolled.
Click to expand...
Click to collapse
We got samsunged
Sent from my SPH-D710 using Tapatalk

35$
10char...

Oh so you didnt want actual help, great thread OP.
Sent from my Galaxy Tab 10.1 using XDA Premium HD app

Is this sextape's way of leaking a new FC** ICS ROM?

sfhub said:
Is this sextape's way of leaking a new FC** ICS ROM?
Click to expand...
Click to collapse
LMFAO ha +1 made my day. Still, I think it must be hard to drop to this level of brain capacity.

How to brick Gnex?

I want to test something, and I have done it before on Skyrocket Galaxy, but forgot exactly how.
I think I used Odin to flashed a modified pit file, and I successfully bricked the SR.
I can't find a gnex pit file to test.
http://forum.xda-developers.com/showthread.php?t=1586807
The rom there doesn't have pit file. I can't seem to able to open the img files in there.
Do you guys have a PIT for me to play?
I think I add "1" in one of the partition address in the PIT for SR before.
Thanks

I found this.
I will test it soon.
http://www.mod2xtreme.com/showthread.php?t=11722

What is it that you want to test?

Theshawty said:
What is it that you want to test?
Click to expand...
Click to collapse
Insurance fraud
Sent from my Nexus S 4G using Tapatalk 2

jesusice said:
Insurance fraud
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Lolol. Insurance fraud..... you gonna go try to get it replaced?
Sent from my Galaxy Nexus using Tapatalk 2

jesusice said:
Insurance fraud
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
You sound like you have experience.
I am going to brick it that way and unbrick it afterward.

I'm not sure how to brick the GN, but maybe you can try that format the whole internal flash memoryvia ADB, and unplug while you flashing this...

Pull the battery while flashing the radio.
Brick city.
Sent from my Galaxy Nexus using xda premium

El Daddy said:
Pull the battery while flashing the radio.
Brick city.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That always works. Lol.
bow chicka wow wow.

Pull the battery while flashing the radio.
Brick city.
Click to expand...
Click to collapse
That didn't work for me last time for Skyrocket.
I could still go into Odin and flash again.
Need to go deeper into low level like pit or before odin.

superprelude said:
That didn't work for me last time for Skyrocket.
I could still go into Odin and flash again.
Need to go deeper into low level like pit or before odin.
Click to expand...
Click to collapse
Pull the battery while flashing a pit file?

El Daddy said:
Pull the battery while flashing the radio.
Brick city.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You are coming from an HTC device, yes?
A bad radio flash on HTC devices will certainly brick your device.
That is not the case with Samsung devices though. I've seen some individuals with bad radio flashes, and fastboot still works fine to flash a new one.

efrant said:
You are coming from an HTC device, yes?
A bad radio flash on HTC devices will certainly brick your device.
That is not the case with Samsung devices though. I've seen some individuals with bad radio flashes, and fastboot still works fine to flash a new one.
Click to expand...
Click to collapse
Yeah I've never owned an android phone that wasn't HTC.
I thought it was an android thing. My bad.

lol, put it in microwave for 2 seconds.
Sent from my HTC Sensation using xda premium

cenwesi said:
lol, put it in microwave for 2 seconds.
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
LOL!!!!!!!!!!!!!!!!!!!!!!!!

I don't know if if the Galaxy Nexus suffers from the same issue as the Samsung Moment, but with that phone, flashing a boot.png (on the GN it's the very first static, black and white 'Google' screen when the phone turns on) larger in size that the existing one, or having too many colors, etc would cause an instant perma-brick. I don't know if we're to the point with the GN where we can freely flash that sort of thing, but I know it worked (didn't work?) on the Moment.
The first post here has the list of guidelines for flashing boot.png images that were discovered trial-by-fire by Moment users.

So, are you guys saying it's next to impossible to brick the Galaxy Nexus if just flashing the basic stuff?

Theshawty said:
So, are you guys saying it's next to impossible to brick the Galaxy Nexus if just flashing the basic stuff?
Click to expand...
Click to collapse
Yea to brick it actually takes effort.
Sent from my Galaxy Nexus using XDA

Gahh Its Lee said:
Yea to brick it actually takes effort.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
You have no idea how relieved that makes me.
I come from an HTC Nexus One and I never once flashed a radio on it, and I didn't wanna mess too much with bootloaders as an incorrect flashing of the two would acquire a brick.
I'm only on user-level (and flashing, of course) so I don't think I'll ever manage to brick it.

Theshawty said:
You have no idea how relieved that makes me.
I come from an HTC Nexus One and I never once flashed a radio on it, and I didn't wanna mess too much with bootloaders as an incorrect flashing of the two would acquire a brick.
I'm only on user-level (and flashing, of course) so I don't think I'll ever manage to brick it.
Click to expand...
Click to collapse
Yea I came from an HTC incredible so radios scared me like crazy
Sent from my Galaxy Nexus using XDA

Splash top 2 brick?

Guys -
I installed the Splashtop 2 on my Nexus 7 running AOKP and Trinity Krenel, and it bricked my device twice. Just running the software and suddenly it crashes, then no buttons work. Then the screen starts to flash and it shuts down. I was unable to get into recovery. I need to push a new recovery to get it running back again. This has happen twice today. Anyone else having this issue?

Its bricked?
So you put it in the trash or sent it back to ASUS?

I'm going to go out on a limb here and say this is not related to splashtop.

I had an issue using Splashtop 2 today that freaked me out a little. Going from Sharp to Smooth froze my N7 and when it booted back up, which took longer than usual, the speaker made a faint but distinct "hissing" noise then a louder "tap"
Everything is working again but that's never happened before. Not sure I liked Splashtop 2 enough to bother with it after that.

Hemidroids said:
Its bricked?
So you put it in the trash or sent it back to ASUS?
Click to expand...
Click to collapse
No.. I know how to get out of a jam. The device would not boot afterward the system froze, then rebooting I got stuck at Google screen. Then it wouldn't get into recovery from bootloader I had to flash a new recovery and flash back up. Sounds like it was bricked at the time to me.
Sent from my Nexus 7 using xda premium

tdrussell said:
I'm going to go out on a limb here and say this is not related to splashtop.
Click to expand...
Click to collapse
I would see why you would say this....however this happened twice when using the new splashtop. My set up or system has not changed in days. Only thing that changed was me installing splashtop. Once I stopped using it and went back to the old one. No issues. Someone else n the market review described the same thing to a t.
Sent from my Nexus 7 using xda premium

Installed HD2 this morning and same problem, freeze when changing from sharp to smooth. Hard reset twice, to get it to boot now the speaker sounds like its blown, was streaming some video from the PC. Running EOS + stock kernel.
Something isn't right with it that's for sure, avoid for now is my advice.
Sent from my Nexus S using xda premium

Knether said:
No.. I know how to get out of a jam. The device would not boot afterward the system froze, then rebooting I got stuck at Google screen. Then it wouldn't get into recovery from bootloader I had to flash a new recovery and flash back up. Sounds like it was bricked at the time to me.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Oh......so its not a brick. Might want to change the title.

Splashtop also froze my Nexus 7, fortunately hasn't knackered the speaker or anything. I was going to blame my undervolt though...

sensory said:
I had an issue using Splashtop 2 today that freaked me out a little. Going from Sharp to Smooth froze my N7 and when it booted back up, which took longer than usual, the speaker made a faint but distinct "hissing" noise then a louder "tap"
Everything is working again but that's never happened before. Not sure I liked Splashtop 2 enough to bother with it after that.
Click to expand...
Click to collapse
I had this same thing happen to me. Everything froze up then my Nexus rebooted itself. Other than that the app runs pretty damn good for me. No rooting or roms on mine.

PA 1.97a, Trinity Kernel @ 1640 (ondemand/deadline), Nova Launcher, Dark Jelly Theme.
Daily use out of Splashtop with absolutely no issue. It's one of the things I like best about this tablet.

my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.

xxmonsterx said:
my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.
Click to expand...
Click to collapse
The only reason he can't access recovery is because of a bug in boot loader 3.34 so its even less of a brick and more of a don't OV and OC
Sent from my Nexus 7 using xda app-developers app

xxmonsterx said:
my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.
Click to expand...
Click to collapse
Influx of noobs? I've been around XDA a bit longer than you. I am deeply sorry forum wordsmith for using the word brick not in the fashion you so desired.
Moving on:
I just wanted to get this word out there and just making sure its not my device. I spoke with Splash top and "they're on it." So we'll see :highfive:

Sorry good sir. I do suppose that was a bit rude. I may have taken out my dissapointment with what xda is becoming on you. My bad bud. I'm not here to compare the d!cks bro. I just can't stand seeing all these help I'm bricked threads.

xxmonsterx said:
Sorry good sir. I do suppose that was a bit rude. I may have taken out my dissapointment with what xda is becoming on you. My bad bud. I'm not here to compare the d!cks bro. I just can't stand seeing all these help I'm bricked threads.
Click to expand...
Click to collapse
No harm no foul. I don't hold grudges. Conflict resolution at its best. Thanks for that, means a lot and restores my faith in people. :laugh:

Harry GT-S5830 said:
The only reason he can't access recovery is because of a bug in boot loader 3.34 so its even less of a brick and more of a don't OV and OC
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What is this bug you speak of?
Also, OC and OV is causing issues? Sorry If i dont know about this just yet, is there a thread that speaks about this?

Knether said:
What is this bug you speak of?
Also, OC and OV is causing issues? Sorry If i dont know about this just yet, is there a thread that speaks about this?
Click to expand...
Click to collapse
Try acessing recovery through boot loader on a healthy N7 and not plugged in, you will find that you can't access recovery. There's quite a few "Q" threads saying that I OC to 1600 and overvolted by 50MHz across the board, and my nexus fried? Why is this??
Sent from a Nexus 7 using my fingers

I've got the same problem with Splashtop and Nexus 7. Original ROM, no root. After switching smooth<>shart Nexus just reboots. Also there seems to be nothing interesting in logcat.

qrees said:
I've got the same problem with Splashtop and Nexus 7. Original ROM, no root. After switching smooth<>shart Nexus just reboots. Also there seems to be nothing interesting in logcat.
Click to expand...
Click to collapse
I seems to be fixed after todays update, but it's still strage that single app could crash the whole device.

Stuck in boot loop

Phone was working fine and I went to switch to airplane mode. All of a sudden it rebooted itself and got stuck on the spinning CM startup screen cirlce, I let it sit for about 10 minutes and never booted. Only option was a battery pull and after doing that I tried starting it up again and same thing, it sat at the spinning CM cirlce for about 10 minutes. Went into recovery and restored a nandroid from a few weeks ago that I know was working well and after start up it still got stuck at the spinning CM startup cirlce.
Before this issue the screen would dim after about 7 seconds while on the spinning CM cirlce then start up. Interesting thing I noticed is every time it would get stuck on the spinning CM startup circle the color never dimmed like usual to indicate the Nitest kernel kicked in. Any ideas on what to do besides odin back to fc09 and re-root? I'm at work right now so can't odin. Any advice is greatly appreciated!

Try wiping everything in recovery, then restore your backup.
Sent from my SPH-D700 using Tapatalk 2

Thank you for the response, going to try that right now.

Jeffreyjicha you're a life saver! I wiped cache, dalvik, data, and system...profit! Thank you a million! So i'm guessing somewhere in the system there was corrupt data?

DynamicN said:
Jeffreyjicha you're a life saver! I wiped cache, dalvik, data, and system...profit! Thank you a million! So i'm guessing somewhere in the system there was corrupt data?
Click to expand...
Click to collapse
Yes.
Friendly Neighborhood Moderator

kennyglass123 said:
Yes.
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
Thank you for that response Kenny.

DynamicN said:
Jeffreyjicha you're a life saver! I wiped cache, dalvik, data, and system...profit! Thank you a million! So i'm guessing somewhere in the system there was corrupt data?
Click to expand...
Click to collapse
No problem
Sent from my SPH-D700 using Tapatalk 2

jeffreyjicha said:
No problem
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
What rom are you running right now?

Effsi's modded Pac-man v20.1 with one of didhiy's latest nitest kernels
Sent from my SPH-D700 using Tapatalk 2

jeffreyjicha said:
Effsi's modded Pac-man v20.1 with one of didhiy's latest nitest kernels
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
How's that rom? Everything working on that Pac v20.1? I'm gonna try and find a new daily driver this week on my days off. I've always been a CM kind of guy cuz I don't use bluetooth so everything that I do use works flawless.

similar problem, but I think the microSD card is where my corrupted data lies
DynamicN said:
Jeffreyjicha you're a life saver! I wiped cache, dalvik, data, and system...profit! Thank you a million! So i'm guessing somewhere in the system there was corrupt data?
Click to expand...
Click to collapse
I'm having a similar problem; I'm way too ignorant to diagnose such problems using logs, so I have to resort to options that do not involve comprehension of Android. I'm running SlimBean 2.1; for the first few days it was brilliant, the best ROM I've tried yet. Then it got stuck in boot-up. I tried popping the battery, reflashing the ROM, wiping the three memory caches and reflashing the ROM, and met with minimal success. Sometimes it would boot, but usually it locked up first.
At a loss for what to try next, I popped out my microSD card and it booted fine. I then put the card in while the phone was running. Again, no problems yet. So now I'm backing up the card and I plan to reformat it and then see if the phone can reliably boot with it in. If so, I'll start re-adding data to the card from my backup until it stops being reliable again.
I'm posting these comments on the off chance that someone else is having these problems and reflashing the ROM doesn't help them.

Cincinnatux said:
I'm having a similar problem; I'm way too ignorant to diagnose such problems using logs, so I have to resort to options that do not involve comprehension of Android. I'm running SlimBean 2.1; for the first few days it was brilliant, the best ROM I've tried yet. Then it got stuck in boot-up. I tried popping the battery, reflashing the ROM, wiping the three memory caches and reflashing the ROM, and met with minimal success. Sometimes it would boot, but usually it locked up first.
At a loss for what to try next, I popped out my microSD card and it booted fine. I then put the card in while the phone was running. Again, no problems yet. So now I'm backing up the card and I plan to reformat it and then see if the phone can reliably boot with it in. If so, I'll start re-adding data to the card from my backup until it stops being reliable again.
I'm posting these comments on the off chance that someone else is having these problems and reflashing the ROM doesn't help them.
Click to expand...
Click to collapse
Try wiping data, cache, dalvik cache, and format system then install the rom. If that doesn't work then you may need to delete the boot animation and I can walk you through how to do that but try wiping all 4 and flashing the rom first.

DynamicN said:
How's that rom? Everything working on that Pac v20.1? I'm gonna try and find a new daily driver this week on my days off. I've always been a CM kind of guy cuz I don't use bluetooth so everything that I do use works flawless.
Click to expand...
Click to collapse
It's not too bad. Just gets a bit sluggish if there's too many apps in the multi-task list. I went into the performance settings and made it attempt to keep 100mb of RAM free at all times. Doesn't really keep all 100 free, it just keeps about 40-60 free. Also Bluetooth is flakey like any other 4.2.2 rom. (But i just remembered you don't use it.) Other than Bluetooth being flakey, it's a pretty stable DD. I was thinking about updating to v22.0.1 though. Or maybe i just might go back to v18 where Bluetooth works lol. Also I posted in this thread: http://forum.xda-developers.com/showthread.php?t=2197759
Cause people were having GPS problems and I don't have any with my setup.
Sent from my SPH-D700 using Tapatalk 2

jeffreyjicha said:
It's not too bad. Just gets a bit sluggish if there's too many apps in the multi-task list. I went into the performance settings and made it attempt to keep 100mb of RAM free at all times. Doesn't really keep all 100 free, it just keeps about 40-60 free. Also Bluetooth is flakey like any other 4.2.2 rom. (But i just remembered you don't use it.) Other than Bluetooth being flakey, it's a pretty stable DD. I was thinking about updating to v22.0.1 though. Or maybe i just might go back to v18 where Bluetooth works lol. Also I posted in this thread: http://forum.xda-developers.com/showthread.php?t=2197759
Cause people were having GPS problems and I don't have any with my setup.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Sounds like a stable rom, aside from bluetooth I don't use gps often either but thank you for that link I actually just flashed Slim Bean and got it all set up how I want it so i'm gonna give Slim a week or so to see how it is. Pac will be my next rom after Slim

DynamicN said:
Sounds like a stable rom, aside from bluetooth I don't use gps often either but thank you for that link I actually just flashed Slim Bean and got it all set up how I want it so i'm gonna give Slim a week or so to see how it is. Pac will be my next rom after Slim
Click to expand...
Click to collapse
No problem. This is probably going to sound a bit like a stalker, but I clicked on your name, and it went to your profile(obviously). Anyway, I saw that it said your location is Reno. Just thought it was a bit crazy, cause mine is too.
Sent from my SPH-D700 using Tapatalk 2

jeffreyjicha said:
No problem. This is probably going to sound a bit like a stalker, but I clicked on your name, and it went to your profile(obviously). Anyway, I saw that it said your location is Reno. Just thought it was a bit crazy, cause mine is too.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Haha it's cool no stalker status perceived. Actually i'm in Carson, don't like putting the real location lol.

DynamicN said:
Haha it's cool no stalker status perceived. Actually i'm in Carson, don't like putting the real location lol.
Click to expand...
Click to collapse
Gotcha
Sent from my SPH-D700 using Tapatalk 2

jeffreyjicha said:
Gotcha
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Not bad weather over here today, it's finally in the 70's. Back to android related stuff, there's so many roms out now for our 2 and a half year old phone it's crazy!

DynamicN said:
Not bad weather over here today, it's finally in the 70's. Back to android related stuff, there's so many roms out now for our 2 and a half year old phone it's crazy!
Click to expand...
Click to collapse
For real. When my dad had this phone, he didn't want much done to it because he couldn't have something not work. But it's mine now, and I love it.
Sent from my SPH-D700 using Tapatalk 2

jeffreyjicha said:
For real. When my dad had this phone, he didn't want much done to it because he couldn't have something not work. But it's mine now, and I love it.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Sounds like he would have been a tpr kind of guy lol. This was my first smartphone 2 and a half years ago and it was definitely money well spent! It's crazy that this phone can run ics and jb thanks to awesome devs of course; speaking of which i'm going to start workin on some stuff myself soon.