Database Info

[Q] Rewinding sound while speaking.

Hi, I recently started messing around with my sgs4g and installed a custom rom using the GB Stater Pack and flash the KJ6 AOSP, everything is working flawlessly except that everytime I'm talking to someone I suddenly hear a rewinding-kind of sound and the other person can hear it too, it happened to me using octane rom, stock GB update and AudiophileFTW edition, can someone please help me get rid of that sound it's getting really annoying, I would really appreciate any help given. Thanks in advance

dude, you hurt your hardware.
Go back to stock KD1, and see if you still have the issue, If you do, go to the tmobile store.

airfluip1 said:
dude, you hurt your hardware.
Go back to stock KD1, and see if you still have the issue, If you do, go to the tmobile store.
Click to expand...
Click to collapse
If I Odin the stock one the rewinding sound goes away, I already did that, but I really want to try a few custom roms because the battery consumption of the stock one is awful.
I have 2 galaxy s 4g both of them are having the same problem one is running the kj6 aosp and the other one is running stock gingerbread leak rooted

ajtorres14 said:
If I Odin the stock one the rewinding sound goes away, I already did that, but I really want to try a few custom roms because the battery consumption of the stock one is awful.
I have 2 galaxy s 4g both of them are having the same problem one is running the kj6 aosp and the other one is running stock gingerbread leak rooted
Click to expand...
Click to collapse
When you flash the GB ROMs, are you doing a factory data reset, clearing caches, etc?

stephen_w said:
When you flash the GB ROMs, are you doing a factory data reset, clearing caches, etc?
Click to expand...
Click to collapse
Factory reset, wipe cache & wipe davlik and my mount settings are u,m,m,u..

ajtorres14 said:
Factory reset, wipe cache & wipe davlik and my mount settings are u,m,m,u..
Click to expand...
Click to collapse
Weird issue. I know you didn't mention it in the OP, but are you over or under-clocking at all?
I'm somewhat with airflup on this - it seems to be a hardware issue. I am saying that based on the fact that I've not heard of anyone else having this issue on GB ROMs. It could be something funky with one of the chips in the phone but only manifests in the GB ROMs. It's weird but not unheard of.
I've not attempted this so someone tell me I'm an idiot for thinking about this, but what if you flash a stock GB ROM followed by the modem from KD1 or whatever Froyo ROM you're using to see if the problem is still there?

If you have the same issues on 2 different devices, you should redownload the roms(cwm and odin), maybe its a download issue i.e. mds5 error
Tell me if that works
Sent from my SGH-T959V using XDA App

As of today I have rooted my phone with different methods, re-downloaded everything, used different versions of Odin, went back to stock, install official GB, it's still doing it, also with the stock Gingerbread leak I noticed that besides the rewinding nose every 4-5 minutes, also the call log doesn't work and while I was watching a movie at work the phone light stayed lit during the whole film... I don't know what to do, is either go back to stock and recharge my phone every 4 hours or go back to kj6 aosp and deal with that annoying sound ..

stephen_w said:
Weird issue. I know you didn't mention it in the OP, but are you over or under-clocking at all?
I'm somewhat with airflup on this - it seems to be a hardware issue. I am saying that based on the fact that I've not heard of anyone else having this issue on GB ROMs. It could be something funky with one of the chips in the phone but only manifests in the GB ROMs. It's weird but not unheard of.
I've not attempted this so someone tell me I'm an idiot for thinking about this, but what if you flash a stock GB ROM followed by the modem from KD1 or whatever Froyo ROM you're using to see if the problem is still there?
Click to expand...
Click to collapse
Kernel is stock no under nor overclocked, btw what's the modem's role on the galaxy s 4g can this be the issue, I have never changed it but what if I do, can it help in any way, thank for all the help...

The modem is the radio for your phone to communicate with the cellular service. People change the modem file to see if they get better speeds in their area. Check the dev section, there's a whole thread containing just the modem files to flash.
I don't know if it will makea difference but it certainly couldn't hurt to try.
Sent from my SGH-T959V using XDA App

[QANDA] for the ICS base Rom by The Collective.

Also good for general purpose.
here is the main thread
[ROM]*ICS *solid base-glitch free (3/30) for development <The Collective>
we may discuss things here!
Thank you for understanding and helping

Doc I am ready for some how to's!!!!!!!!!!!!

been trying to install this rom, but for some reason keep getting boot loop, went ahead and restored and tried again but same boot loop. currently on Sky-ICS 2.3.6, any suggestions

"Do not do any wiping or formating or resets before or after the flash."
-Why? I am used to using darksides wipe before flashing any roms.

orlandoxpolice said:
"Do not do any wiping or formating or resets before or after the flash."
-Why? I am used to using darksides wipe before flashing any roms.
Click to expand...
Click to collapse
your also used to roms rom that only delete recursive pn partitions.
This is diffternt.
Non of that wiping stuff was ever nessary on my captivate.
And now...not here.
Sent from my SAMSUNG-SGH-I727 using Tapatalk

dragonfuego said:
been trying to install this rom, but for some reason keep getting boot loop, went ahead and restored and tried again but same boot loop. currently on Sky-ICS 2.3.6, any suggestions
Click to expand...
Click to collapse
tested.
It works.
U must either not be following direction
Or have a bad download
Sent from my SAMSUNG-SGH-I727 using Tapatalk

QUESTION= who is the man
ANSWER= Johnsondr80

I just tried it coming from GB NexusMod 4 and just got the boot loop as well. It is a little tricky getting back into recovery - you only get about a second in the CWM menu before the phone spontaneously reboots.

sacberg said:
I just tried it coming from GB NexusMod 4 and just got the boot loop as well. It is a little tricky getting back into recovery - you only get about a second in the CWM menu before the phone spontaneously reboots.
Click to expand...
Click to collapse
Performed it fine here with zero issue.
If your cwm is acting up, may be lot more going on here.
I suggest a return to stock
Reflash cwm
Then flash this build.
Wish I could say more but UN able to see or confirm your issue.
TheCollectives' SolarisPrime on my i717 via Tapatalk

Tmo
Hey, great base.
I have flashed this, the leak and a few other ics roms. On this rom I cannot get my phone to hook up to tmo 4g, edge works fine, but it wont jump from edge to 4g. I tried flashing a tmo radio but no dice.
The leak worked fine in that regard. Consistently connected to highest available signal.
what can I tweak in order to re-establish connection to tmo 4g.
I tried to go into mobile network settings and all of the settings there seem consistent with the stock tmo settings. But when i try to change network operator settings from automatic to manual it never gets past "searching"
Thanks for any help you might be able to lend

Also, i think this guy should credit The Collective.
http://forum.xda-developers.com/showthread.php?t=1574675
From what I'm looking at, its very similar

All good. Found out how to make it work
chasport said:
Hey, great base.
I have flashed this, the leak and a few other ics roms. On this rom I cannot get my phone to hook up to tmo 4g, edge works fine, but it wont jump from edge to 4g. I tried flashing a tmo radio but no dice.
The leak worked fine in that regard. Consistently connected to highest available signal.
what can I tweak in order to re-establish connection to tmo 4g.
I tried to go into mobile network settings and all of the settings there seem consistent with the stock tmo settings. But when i try to change network operator settings from automatic to manual it never gets past "searching"
Thanks for any help you might be able to lend
Click to expand...
Click to collapse

chasport said:
All good. Found out how to make it work
Click to expand...
Click to collapse
Thanks. Just got in and saw this mind sharing so others can learn from your experince?
Sent from my SAMSUNG-SGH-I727 using Tapatalk

Stock jelly bean very laggy, should I switch to cyanogen mod?

I'm running stock jb and sadly its very laggy and many taps will result in many second of waiting. Even Google search takes ages to start.
Are the cyanogen Roms better? Is there already a working cm10 rom available?

Shahpur.Azizpour said:
I'm running stock jb and sadly its very laggy and many taps will result in many second of waiting. Even Google search takes ages to start.
Are the cyanogen Roms better? Is there already a working cm10 rom available?
Click to expand...
Click to collapse
I would give Jellybro a try. Seems to be fairly popular ROM based on CM10
http://forum.xda-developers.com/showthread.php?t=1791751
Make sure you make a nandroid backup and know how to flash beforehand.

i agree! jellybro is the sastest jb rom here !

I'm using paranoidandroid 1.9.5 its very smooth and fast but WiFi tethering is not working
Sent from my Nexus S using Tapatalk 2

Since you need to wipe the phone either way, have you tried a factory reset yet? It's worth a shot. You never said whether or not you did. But if you're looking for more features all baked in, go with a custom ROM

I think CM9 is still faster overall although it isn't buttery smooth like JB or CM10.

chronophase1 said:
Since you need to wipe the phone either way, have you tried a factory reset yet? It's worth a shot. You never said whether or not you did. But if you're looking for more features all baked in, go with a custom ROM
Click to expand...
Click to collapse
My boot loader is already unlocked so I shouldn't have to wipe for root, right? I'm just not sure if CM10 is worth it. Don't know if nexus s is capable of keeping it fast with Android 4.x...

You should try the jellybro rom because its super fast.
Sent from my Nexus S using xda premium

Try doing a full wipe/system reset. My Nexus S OTA to JB a few weeks ago. Even at stock, it was fast. No lag.
If you are experiencing lags, it is likely your phone's filled with resource contending stuff.
BTW, I've seen flashed in CMREX Beta9 JB. Boot up is insanely fast. Everything works.
Also you can try the V6 Supercharger mod. It helped my other phone - Gingerbread equipped XT615 Motoluxe speed up quite nicely.

Shahpur.Azizpour said:
My boot loader is already unlocked so I shouldn't have to wipe for root, right? I'm just not sure if CM10 is worth it. Don't know if nexus s is capable of keeping it fast with Android 4.x...
Click to expand...
Click to collapse
Mine runs very well on JB. You're already rooted and whatnot, all you need to do is backup via recovery. Properly wipe the phone and flash. There's a few 4.1 ROMs out there. Give them a shot and see what you like. The phone is still pretty quick despite its age. Like I said. The phone may just need to be cleaned up. I've never had mine lag, personally.

Should I wipe SD partition too? It takes ages to backup the SD partition to a PC first...doesn't seem to support USB 2.0...
I would try a factory reset first to see what happens...

Shahpur.Azizpour said:
Should I wipe SD partition too? It takes ages to backup the SD partition to a PC first...doesn't seem to support USB 2.0...
I would try a factory reset first to see what happens...
Click to expand...
Click to collapse
From my understanding just do a factory reset/wipe, wipe the dalvik cache and then flash your ROM.

Shahpur.Azizpour said:
I'm running stock jb and sadly its very laggy and many taps will result in many second of waiting. Even Google search takes ages to start.
Are the cyanogen Roms better? Is there already a working cm10 rom available?
Click to expand...
Click to collapse
First try change kernel..
Nocerino's Rulez with RAScarlo's ROM features TriNitY

I've had the same issue and came here to see if others shared. JB was initially pretty solid (I initially did a full wipe), but now it lags real bad. Google Now is the worst offender. It takes at least 5 seconds to appear, and then a good chunk of time to allow me to input text. It's too much.
I'm going to keep looking for another ROM, but honestly, I was counting on the fact that stock would be the most reliable. I've also had trouble using my radio to make calls / use data. I'm disappointed as I figured these problems were previously mostly due to custom ROMs. All I want is a stable, simple ROM that functions consistently.

Google Now was fast for me initially but it's super slow now but I doubt this is a ROM issue.
Everything else is fast and smooth.
Sent from my Nexus S using xda premium

I think its time to upgrade...just waiting for a nexus without pentile screen.

Do a full wipe, clear cache
This is the best time to check as many roms as possible. no need to worry about losing anything as you should of backed it all up by now. So clean slate and try some different Roms. To say stock is laggy does sound strange. So back up everything, even whats on your SD.
Clean start.
Best backup program to save apps and data - Titanium backup
Best app for everything else (app manager, processes etc..) - Romtoolbox.
Now go have fun!
try Xenonhd v6.0 and Air kernel JB weekly.
My phone is better than new with this combo. I am not going to try anything else until these give me a serious issue (I dont think they will)

Back to stock..

My maps gps lock got totally f*cked by synergy 1.7 so it was suggested to go back to stock and reroot since flashing new rom from clean wipe did not work.
A lot of links and methods are out of date, so I was wondering what the best way to get back to stock at this point.
I have the latest odin on my computer, I guess I'm looking for the most recent or most reliable stock image to flash.
Thanks
SGS3 production
SGS3 production

I think a lot of people recommend the root66 stock..... But I'd try noSympathy's image
Sent from my SCH-I535 using Tapatalk 2

I'm rooting immediately after so whatever is a proven version will make me happy
SGS3 production

They're both rooted so no need to do after. Both are tried and true, noSympathy's is based off the last OTA but some people like to start from scratch so that would be root66.
Sent from my SCH-I535 using Tapatalk 2

I want to get back to unrooted stock.
I can't seem to locate the route66 stock image
SGS3 production

http://forum.xda-developers.com/showthread.php?t=1762204
It's up to you but it's just more work to go unrooted then root yourself. Check the development threat there maybe an un rooted image there
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 07:36 AM ---------- Previous post was at 07:27 AM ----------
http://forum.xda-developers.com/showthread.php?t=1755386
Thought there would be a newer one but here's unrooted...
Sent from my SCH-I535 using Tapatalk 2

My main reason to flash stock was I was told that would be the only way to restore my faulty gps lock.
Do you think flashing a stock rooted image would do the same for me? Or should I flash unrooted image then start fresh? Time is not a concern, im patient
SGS3 production

FormeriPhoney said:
My main reason to flash stock was I was told that would be the only way to restore my faulty gps lock.
Do you think flashing a stock rooted image would do the same for me? Or should I flash unrooted image then start fresh? Time is not a concern, im patient
SGS3 production
Click to expand...
Click to collapse
Flash back to stock then root. Click link in sig.

i tried this......still having the same issue, switched from CM10 back to stock and had issues with my GPS being way off, like by 3300 meters off haha.....so flashed back to stock, still had the issue, so i used the rooted stock image and flashed that and i'm still off by about over 2k meters.....don't use my navigation or maps all that much but when i do need it i'll have a bit of an issue lol

I had issues with my gps for a few days. If was real flaky but got better with synergy 1.5. I have since move to 1.6 with a fresh install and am still okay. Check out a app called gps status. See if you can see any gps satellites. Maybe in that app clear your agps state in tools. Then if that doesn't work try to download gps assistance with the same app in the same settings. Make sure your out side for this stuff with your gps. It's probably not gonna hit ya sitting on the couch.
Sent from my SCH-I535 using Tapatalk 2

FormeriPhoney said:
My maps gps lock got totally f*cked by synergy 1.7 so it was suggested to go back to stock and reroot since flashing new rom from clean wipe did not work.
A lot of links and methods are out of date, so I was wondering what the best way to get back to stock at this point.
I have the latest odin on my computer, I guess I'm looking for the most recent or most reliable stock image to flash.
Thanks
SGS3 production
SGS3 production
Click to expand...
Click to collapse
I used the stock image from here:
http://samsung-updates.com/device/?id=SCH-I535
and used this method for rooting:
http://forum.xda-developers.com/showthread.php?t=1792342

my gps doesnt work at all

After Odin back to stock, non rooted image my GPS is fixed.
Now on CM10, loving it. Not sure if I'll ever try synergy again bc of that nightmare situation.
I use my gps pretty much all day. I needz it
SGS3 production

New AOKP JB issue with radio
Well I am trying to get something fixed and I am going through a complete restore to do this.
But just so you are aware the new AOKP JB release will kill your data. I learned a hard lesson with this when trying to recover and nandroid back to my previous rom. It killed my data completely and would not allow me to do anything with data in any rom. I used the root66 stock rom in hopes it would work, and that didnt even solve the issue.
Right now I am restoring a factory image through kies and seeing if that will do what I need. If it does, I am sticking with stock roms for awhile until AOSP roms have more time to develope with less bugs.

douglasf01 said:
Well I am trying to get something fixed and I am going through a complete restore to do this.
But just so you are aware the new AOKP JB release will kill your data. I learned a hard lesson with this when trying to recover and nandroid back to my previous rom. It killed my data completely and would not allow me to do anything with data in any rom. I used the root66 stock rom in hopes it would work, and that didnt even solve the issue.
Right now I am restoring a factory image through kies and seeing if that will do what I need. If it does, I am sticking with stock roms for awhile until AOSP roms have more time to develope with less bugs.
Click to expand...
Click to collapse
It sounds like you may have lost your IMEI or MEID. I hope you made a backup with QPST.

still had IMEI
toy028 said:
It sounds like you may have lost your IMEI or MEID. I hope you made a backup with QPST.
Click to expand...
Click to collapse
Well it turns out I still had my imei present on my phone and even after a factory reset like I did wit kies it still didnt work. Initially I wasnt able to get past the activation screen on the root66 rom, but I was able to with the stock factory image from kies in which case this allowed me to follow the steps in this link.
http://forum.xda-developers.com/showthread.php?t=1838791
Once I did that my phone rebooted and everything came back as it was never gone, well except for all of my data on the internal sd card, but that is to be expected.
After 2 hours of going through numerous steps I finally found a fix, mind you not the most simple of fixes, but a fix none the less.
I think I am just going to stay stock for awhile like I mentioned and wait for the OTA that comes out in 2014 lol, unless in review of AOSP roms the issues present now are gone after sometime.

Tks
Nice. Tks

Gps works like a champ on beans!

Gps seems to work substantially better on cm10 than on stock....ran the GPS test and i locked onto 14/19 satellites.
Beamed via NFC through the local store to the internet from my SGS3.

Re: [BeanStalk][1.179] Phone freezes after call

Re: [BeanStalk][1.179] Phone freezes after call
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app

bretcb said:
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over

qkster said:
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over
Click to expand...
Click to collapse
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.

bretcb said:
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.
Click to expand...
Click to collapse
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.

qkster said:
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.
Click to expand...
Click to collapse
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.

bretcb said:
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.
Click to expand...
Click to collapse
yeah...for the most part, while in cwm, factory reset, wipe system, data, cache, dalvik and then flashing a new rom work very well.
occasionally, for what ever reason that i'm not sure, going back to stock..changing file system back to rfs and then changing back to ext4 may be needed to fix certain problems...not common and not routine practice, but is needed...at least imo

OK, fair enough. I will read up more on going back to stock so I'm not unfamiliar with it. Which tool do you prefer?
For completeness of troubleshooting info for anyone else who may be reading, I received a phone call yesterday while the lock screen was disabled, and the phone still froze after the caller hung up. I received another call today, and made sure I hung up first, and no freeze, my phone was fine.
Sent from my SGH-I997 using xda app-developers app

bretcb said:
I will read up more on going back to stock..
Which tool do you prefer?
Click to expand...
Click to collapse
Everyone has their own prefs...I prefer heimdall. It doesn't matter. Whatever it takes to get the job done. You prolly should buy a usb jig too.
http://forum.xda-developers.com/showthread.php?t=1437548