Database Info

is it ahome????????????????

after installing ahome my touchscreen was a little to responsive when i dialed 1 pressing once it would dial it 2 times so i thought a factory reset would fix it when i did the factory reset my phone wont get past the flashing android im probably just going to flash back to rc29 and check with if the touch screen works like it should if it doesnt i can take it to t-mobile for a fix if it does work ill go back to jf rc33 1.42

Oh. Ok. Thanks for telling us.

nabzilla1990 said:
after installing ahome my touchscreen was a little to responsive when i dialed 1 pressing once it would dial it 2 times so i thought a factory reset would fix it when i did the factory reset my phone wont get past the flashing android im probably just going to flash back to rc29 and check with if the touch screen works like it should if it doesnt i can take it to t-mobile for a fix if it does work ill go back to jf rc33 1.42
Click to expand...
Click to collapse
First of all... let me address this before someone rips you apart here. Your question (if it is one) is a bit difficult to read. I am certainly not an english teacher but maybe a period here and there would make it easier to understand. Because I honestly don't know if you are asking a question, stating that you're having a problem with reflashing, going back to factory settings or other. I mean I had to read it 5 times!
Secondly... if you do a factory restore from the settings and you get the flashing android on boot you should let it keep flashing for a few minutes. You need to be patient because it is wiping all of your previous data/settings and restoring them to default.
Third. If it stays on the flashing android for longer then say three to five minutes (depending on how much you need to wipe) then go ahead and boot up in recovery mode and do a wipe from there. If you still get stuck on the flashing android then yes... reflash.
Fourth. Do not assume it is an app that causes this problem unless you are CERTAIN of it. Hundreds if not thousands of people have downloaded this app (including myself) and have not had a similar problem. Maybe do a search for the app name and read what people are saying about it. If it is the app then believe me you won't be the only one commenting. If you're lucky there will be a fix so you won't have to wipe or reflash.
Finally... every so often (especially before making a major change like apps to sd, themes, etc) it'll be a good idea to do a backup with Nand so even if you do end up messing something up (by app or user error) you can always reflash your image to your phone.
Good luck!

EDIT: Whoops! Wrong thread!

I'm very sorry for my poor English but my story is after installing ahome
everything was fine until I rebooted my phone. After rebooting the phone I
tried dialing a number and when I pressed a number once the it would dial
the number twice for example when dialing 7 instead of only dialing the
number 7 it would dial 77, or when using useful switchers turning off the wifi I
would try to check the wifi on but with one push it would check and uncheck
the wifi. Later I did a factory data reset and rebooted the phone I couldn't get
past the flashing android. I reverted back to stock rc33 just in case its a
hardware problem I can let t-mobile know thanks for the replies

i doubt it's a hardware problem.
i had the same problem, coincidentally after installing aHome; i was unable to get past the "flashing android" screen. The first reboot that i did, though, was after using the JF auto-updater app, so i'm not entirely sure where the problem lies.
long story short, i wiped my system, and am now in the process of installing Windows and the Android SDK to my system so i can do a restore.

thanks im gonna go back to root then

yeah, aHome still has lots of thigns to be fixed specially that force close issue every time u return to home :/ i liek dxtop better dont feel like scrolling tru 10 pages like the iphone..

NExus S Zulugen Rom: story then ?????

So the excitement of the nexus s is still flowing through my veins. I have now switched 2 radios and 3 roms.
I recently went from SuperOSR to Zulugen. Yesterday I had a MAJOR crash. My google voice froze up sending a text. Even after a reboot it was stuck in a sending loop. I then decided to turn off data and see if that worked but that only made it worse as i couldnt turn my data back on. I then force closed it which started bombarding my phone with force close errors.
THEN CRAAAAAAAAAAASH force close errors every 2 secs, no data (even after the *#*# reset.
I tried restoring to an earlier image i took but forgot it crashed during that too and the image was bad. I then just restored back to the base rom and redid my phone after doing the *#*# baseband settings just for good measure.
these are the apps i THINK were responsible for the crashing. Proton Voltage, Cache Cleaner NG, PREY
I will stay away from Proton for now, and have put CC NG back on but removed certain system actions and apps i DONT want it to touch. As of now prey is on it but not active.
anyway here is my question
When you change your base-band radio do you ALWAYS have to do the *#*# or just if you lose your 3?
Can the wrong radio cause issues with a certain ROM? I am running UCKD1 as of now with zulugen. second time around it seems good but who knows and I always wipe data between roms.
I have asked the question earlier but in the wrong section, as Im still getting the hang of where to post things here but anyone from the New England area have a good suggestion on a specific radio? Im in ct near the water, the dead zone of signal ESPECIALLY for ATT
If I flash my E! radio back (either the image i took or the one form the thread) it states to back up your EFS which i did. But why does it ask this, should i worry going back to the original E1 radio?
Do i have nice shoes?
thanks

[Q] strange turning off when incoming call

So here is the problem - my sgs 4g (currently running valhalla black, earlier same problem with stock 2.3.6) turns off when someone is calling. It's not happening every time i get incoming call, just sometimes. It turns off without any sign of doing it(no vibration, no sound, not even the animation so i don't know that its happening, when the phone is in my pocket), and the caller gets voice mail.
I think the problem started after updating to 2.3.6, but it also can be caused by falling on the floor(happened few times).
What do you think? Anyone had similiar problems?
I live in Poland, so i can't get it fixed in samsung care point because they don't support SGS 4G.
sry for my spelling mistakes, i'm doing my best, but that's not my first language.

I'd say the best you can try is Gremlin Remover to see if it solves your problem.
http://forum.xda-developers.com/showpost.php?p=22596598&postcount=1

try tmo warranty after returning to stock gb

Gremlin Remover doesn't help. I flashed it only once.
I'm a bit afraid of sending it to USA Tmobile store from here, i think i'll look for some samsung magician in my country unless you have other ideas.
thanks for help and waiting for more solutions
#edit: is there any diagnostic software to check my phone hardware? Maybe something to save log of crash if its software failure?

When you say you flashed it once - do you mean Gremlin Remover or Valhalla Black?
And I wonder if it could be a modem issue for you since it started on KJ6. You might try flashing a different modem as a troubleshooting option.
http://forum.xda-developers.com/showpost.php?p=16127939&postcount=1

i had that issue on one of my sgs4g's a while back. wipe your sd card on your computer, odin back to kj6 stock. once you odin back to stock, make sure you perform a factory reset with the sd card removed. reboot and let it sit for a few min. do not sign into google or anything. have someone call you and see if the problem persists. let the phone function that way for an hour or so. then sign into google, but do not dl any apps. put back in your empty sd card and then reboot the phone. after a day, if you do not have the issue, you should be good to go. if you have the issue after a day, post back and pm me if i do not respond (i probably won't; i'm swamped at work and I am rarely on)

Ive had the same thing happen on valhalla black and I found that on my phone it was actually a skin that I had been using with adw ex. I changed my skin and cleared all my cache and dalvik cache and did not have a single problem after that. There are so many different things it could be. just experiment with it.

@lumin30: I meant stock 2.3.6 ->valhalla black (remover was the second)
That's something. I'll try everything you guys posted above and let you know the results in a few days.
Thanks for everything, appreciate your help.
#edit: LogsProvider service keeps crashing after blackout on valhalla black and i have to reinstall it. After flashing, the phone works for about 24h and then turns off. When I turn it on, logsprovider stops unexpectedly every 15 sec and i have to flash it again.
Now I am not sure if it's connected to incoming calls

After weeks of flashing and testing there is only one thing I am sure - nothing helped.. I tried many ROMs, different kernels and modems.
Now I can't see any relation to the software. Only thing on my mind is the battery, usually when my sgs turned off, the battery lvl was below 70%, so I ordered new one. I'll let you know if this changed anything.

Issues with calls and various other things.

Hello! Here I am with my Q.
I got it last week, rooted w/o BL unlock, then a few days later I went to Moto to unlock the boot loader. all went well. (AHAHA, They worded the terms for the unlock as if EVERYTHING at ONCE will break. It seems to me that this has become reality.)
Then I had issues with GPS and Camera not working at all.
With each flash I got one or the other working, not usually both.
Now Both Camera and GPS are working wonderfully. Here's the kicker, I've found that calls are not working well.
I make calls, they go through but end shortly after they start with silence. when you attempt to end the call, it wont do it, or it will about 5 minutes after end has been pressed.
On receiving calls, often times it wont come through at all, if it does there's a chance that you wont get to pick it up. It will act like the caller has hung up. Missed call. Some times it will let it through, and a few seconds in and go to silence.
Here was my process.
1. Rooted with Motochopper. Played around in stock for a while then got fed up with it and all of it's bloat. Not to mention horrible batterylife.(Still has horrible battery life on CM, even when underclocked.)
2. Unlocked bootloader via Motorola.
2a flashed OpenRecovery, CM10.1 (Yes the CDMA version)and gapps.
3. Yay CM. Sadly, nothing works right. (Yes there were wipes.)
4. Was suggested to flash JB FXZ, did that.
5. Flashed TWRP and CM+Gapps. (No camera, but GPS worked.)
5a. Flashed 5/20 Build. Camera worked but no GPS.
5b. Flashed 5/26 build over 5/20 and both Cam and GPS work now.
The call issues were persistent throughout all of the builds I tried.
5/20 5/23 5/26
Sys info screenshot
lionspaws.net/android/ignoreme/Screenshot_2013-05-29-21-48-50.png
Please help me diagnose this.
I'm not looking for "It's you/your device/doin' it wrong/works for me" or "go back to stock"
I'm looking for help. I need a working device.
Here's some logs with a test call.
it failed about 2 sec in. Skype hung up due to dead line. Phone wont hang up.
Radio reset, data resync.
then I powered off the device after it 'hung up'(radio reset)(If I dont hit hang up, the call timer will continue count up)
lionspaws.net/android/ignoreme/logs.zip (zip,bzip2)
Halp!

Bump?

I've been having the same call issues, with every rom except stock.

Sounds like you tinkered alot.
I suggest you do a full reflash with rsd/ stock rom. Since u have unlocked bootloader I suggest you to install custom recovery like twrp or cwm. That will also root your device. After that retry flashing cm10.1 nightly and gapps exactly as described in their threads.
Everything else would be tinkering around broken builds. So start with fully clean device through rsd.
Also about the gps problem: it is suggested to get a gps lock on stock rom before installing aftermarket rom.

I'm having the same problem, I've RSD'd to stock and all that stuff too. I ALWAYS clean install. Yet I'm having this problem on most roms. I haven't tried any kernels yet, so maybe that would help things but I dunno. I'm gonna play around with that some time and figure it out.

xLoveHateLegend said:
I'm having the same problem, I've RSD'd to stock and all that stuff too. I ALWAYS clean install. Yet I'm having this problem on most roms. I haven't tried any kernels yet, so maybe that would help things but I dunno. I'm gonna play around with that some time and figure it out.
Click to expand...
Click to collapse
This is the first I have ever heard of this type of issue...
Logs please, with thorough detail on what happened. I can't recreate this, and 99% of others can't either (or just put up with a non-functional phone. Seems doubtful...)
Edit - as far as I know, the OP has fixed all of the issues they were having... maybe they can chime in with the process, but my kernel would have nothing to do with cell service.

Alright, here's a logcat... it's weird, I can only hear the first word they say and vice versa. Then the call gets quiet but stays connected. Then after clicking hang up, the call isn't really hung up. I have to go back to the dialer and click hang up again. Then, after a minute or so I'll hear the hang up tone and it'll finally hang up. I'm doing clean installs so I'm not sure what's going on here. Hopefully this will help resolve this issue, 'cus it's a huge problem for me :/
EDIT: Just flashed a stock rom and I'm not having this issue at all.
Sent from that one MoPho... Q

Anyone have a clue what's going on with my phone?

[Q] Lag

I have the charge running FP5 firmware and the Tweaked ROM 3.0.
I've run into a situation where the phone has become rather laggy and buggy.
Example: Click the notification for voicemail...wait 30 seconds and phone dials. or Phone battery dies. I plug it in and it charges up to 30%, then starts getting very laggy and non responsive. I reboot and am told battery power is really 50% and phone is good to go.
I'm used to rebooting the phone at least once a day or more. I'm looking for a way to correct the problems and bring the phone back to how it was when I last upgraded and and loaded the ROM... too bad I didn't backup the phone at that point. Anyways...I know that if I reload the firmware and apply the ROM, everything will work correctly again but I'll spend hours tweaking the settings to add custom ringtones and photos to contacts.
Is there some cache or data I can clear to fix this without clearing everything and starting over?
Mike
P.S. I'm keeping this phone until Verizon allows me to upgrade and keep unlimited data or the phone dies and I have to get another.

beavermjr said:
I have the charge running FP5 firmware and the Tweaked ROM 3.0.
I've run into a situation where the phone has become rather laggy and buggy.
Example: Click the notification for voicemail...wait 30 seconds and phone dials. or Phone battery dies. I plug it in and it charges up to 30%, then starts getting very laggy and non responsive. I reboot and am told battery power is really 50% and phone is good to go.
I'm used to rebooting the phone at least once a day or more. I'm looking for a way to correct the problems and bring the phone back to how it was when I last upgraded and and loaded the ROM... too bad I didn't backup the phone at that point. Anyways...I know that if I reload the firmware and apply the ROM, everything will work correctly again but I'll spend hours tweaking the settings to add custom ringtones and photos to contacts.
Is there some cache or data I can clear to fix this without clearing everything and starting over?
Mike
P.S. I'm keeping this phone until Verizon allows me to upgrade and keep unlimited data or the phone dies and I have to get another.
Click to expand...
Click to collapse
You mean Tweaked 3.2, right... if not first upgrade to the 3.2 version of the ROM... it is the current FP5 option.
There is a build.prop thing commented out at the bottom that should force launcher into memory (supposed to help with screen redraw issues, but might also help with general responsiveness). I think you could do it from root explorer, just edit the file, scrool down, read comments, when you find one that sounds like what I said just remove the "#" from the line below it.
re-installing tweaked might really help...
but you might try going into CWM and wiping cache only... NOT data & cache... JUST CACHE... that helped me when i had "funky" things going on on a different device/ROM worth a try.
Finally, you should always take a CWM backup, Nandroid, before poking around....
Also... check swappa for relatively cheap phones with no ties to VZW contract it is where i picked up the GN2 (if it is rooted and you don't want to show it off at the corp store, just call customer support say you are too busy store hours. They will send you the micro/mini SIM via FedEx.
Of course take what I say with a grain of salt... I am just a crazy guy from the internet
(oh great XDA... please correct me if I've misspoken)

Thanks for the info. I never did load Tweaked 3.2. I will put that on the back burner as I don't want to reload all the settings. Maybe I can load it without wiping data. Do you know? For now I will try wiping the cache and see if the phone improves.
Someday I'm gonna have to explore the latest OTA and a new ROM. I'm getting tired of ignoring the update message. either that or learn how to shut the message down. any recommendations on a ROM for the new OTA?

beavermjr said:
Thanks for the info. I never did load Tweaked 3.2. I will put that on the back burner as I don't want to reload all the settings. Maybe I can load it without wiping data. Do you know? For now I will try wiping the cache and see if the phone improves.
Someday I'm gonna have to explore the latest OTA and a new ROM. I'm getting tired of ignoring the update message. either that or learn how to shut the message down. any recommendations on a ROM for the new OTA?
Click to expand...
Click to collapse
I will never tell someone "don't say it click the button"... However, I'm like pavlov's dog clicking the button is appreciated...
Not sure about a dirty flash... Never tried it. I got turned on to Root and Such well after FP5 and Tweaked 3.2 came out.
If you give it a go... You could retain much via Titanium Backup. Or just send a CWM Backup/Nandroid on the SD Card before playing around.
Either way...
There has to be a proper stop notification how to thread around here somewhere!
Cliffs Notes:
From a Root Friendly File Explorer (Like Root Explorer HERE, it is worth the $)
edit a line in "/system/build.prop"
Find
ro.build.fingerprint=verizon/SCH-I510/SCH-I510:2.3.6/GINGERBREAD/FP5:user/release-keys
replace the FP5 with FP8 so it reads:
ro.build.fingerprint=verizon/SCH-I510/SCH-I510:2.3.6/GINGERBREAD/FP8:user/release-keys
NOTE: BE VERY CAREFUL NOT TO HOSE THE PERMISSIONS (If I recall some of the other "freebie" root file explorers break the permissions... Best to find that a real thread with all the details if you are not 100% confident.)
Also feel free to double check my facts... I'm just a crazy guy from the internet!
Good luck!
Edit Alert:
PS. While poking around at the tweaktools back-end, I noticed there were some mods that specifically addressed lag (I have little to no experience with them though... Just FYI...

beavermjr said:
Thanks for the info. I never did load Tweaked 3.2. I will put that on the back burner as I don't want to reload all the settings. Maybe I can load it without wiping data. Do you know? For now I will try wiping the cache and see if the phone improves.
Someday I'm gonna have to explore the latest OTA and a new ROM. I'm getting tired of ignoring the update message. either that or learn how to shut the message down. any recommendations on a ROM for the new OTA?
Click to expand...
Click to collapse
yes, you can flash tweak 3.2 over 3.0 without wiping data. not sure if it comes with the updated kernel, but I would certainly do that as well.
in terms of lag, try the crossbreeder mod on XDA - worked for my charge!