Develop Bugs

Call echo on every ROM? Try this...

I have noticed a few people complaining of call echo with AOSP ROMs (even with "noise suppression" checked), as well as some stock based ROMs. I was having the same problems. Stock based ROMs were better, but echo was still there. I tried several radios without avail.
What finally worked for me was going back to stock through Kies (keep in mind this will wipe your internal sd as well, so move your backups off your phone). I have since been able to flash PACman ROM without call echo. I have not tried any others but I assume the result would be the same. If someone is willing to test other ROMs/radios and report back that would be great. I just don't have the time.
Also, I did not flash a different radio after going back to stock. I assume it would be okay to do so, but I am not a dev so that is only a guess. What I think going back to stock fixes is some missing/corrupted libraries that are somehow surviving ROM flashes (like in a protected storage or something like that).
Anyway, I hope this helps someone else.
EDIT: This doesn't work all the time, and has only really worked for me once. I have done it twice and it worked great the first time, and not really the second. It's worth a shot, but just keep this in mind.
:::Specifics:::
Essentially all I did was go to the latest stock rom image from T-Mobile. Kies upgraded my phone to UVLI1, which is T-Mobile's latest 4.0.4 stock rom. Kies essentially wiped everything from my phone (except external storage) and imaged it with the latest factory image which includes the latest radio. I have since been able to root, install TWRP and flash an AOSP based rom without degradation in call quality. I did not flash over the radio that was installed by Kies, and I did not wipe android secure in TWRP (don't know if that made a difference).
What you should try if you are having call quality issues:
1. Go back to stock unrooted (use your method of choice, I used Kies but that doesn't work for everyone so try Odin or Heimdall)
2. If you didn't go to the latest stock unrooted image from T-Mobile and Samsung, do that through Kies which should now work for almost everyone (as of Jan. 1, 2013, the latest stock image is UVLI1/TMBLI1)
3. You should now be able to root and flash any rom you like without call quality degradation (if this is not true for you please let me know --- see above for what I did at this point)
I'd be interested in getting some feedback from this. Keep in mind that I am not always available and may only be able to reply once a day or less. Again, this is just what worked for me, it may not work for you. Please give yourself plenty of time when going through this process as Kies is not very fast (at least in my opinion).
UPDATE:
Here is how I got Kies to update my phone while still rooted and even running an AOSP rom. As always, do this at your own risk. I accept no responsibility for broken devices or lost data/pictures/music/etc. However, I have done this twice now, so just read and understand what you're doing and you should be fine.
Keep in mind that this WILL WIPE YOUR INTERNAL STORAGE! You have been warned.
1. Disconnect your phone from your computer
2. Launch Kies and click on Tools>Firmware Upgrade and Installation
3. Input model number (it's case sensitive !?) and hit OK
4. Input serial number (found under battery) and hit OK
5. Hit okay on windows until it starts downloading the latest firmware for your phone
6. After it's finished downloading it will tell you to put your phone in download mode and connect it to your computer. Do it, check "I understand..." and hit OK (I also opted out of the sending of information to Samsung)
7. Wait until it's finished. It will likely launch a window saying it's downloading a file for emergency recovery of your device.
8. When it's (finally) done it will tell you it was successful (hopefully). Your phone will automatically reboot and all will be well with the world and your phone.
Hope this helps.

kies fails recognize my phone. already have the phone drivers installed.

You have an interesting post, but it would be of more use to people if you specified the exact information about what's on your phone. Such as which stock ROM version you were able to flash through Kies and what radio version you are currently using.
There are different stock ROMs and radios on the forums, so it doesn't solve anything if you haven't told us what exactly works with your phone that others should try.

Here is the rub. I haven't been on stock unrooted rom since buying the phone in March. I have bounced around roms and radios quite a bit (probably at least one or two a week on average). My wife has complained of call echo for a long time (multiple roms, multiple radios and AOSP and touchwiz based roms). Touchwiz based roms had better call quality but echo was still present. I decided to Odin back to stock unrooted and see if it was a hardware issue or not. It wasn't a hardware issue because call quality was great. So I rooted the phone, installed the latest TWRP (2.3.3), but wasn't happy with stock rooted so I decided to try an AOSP rom. I wiped only cache, dalvik cache, system and data (not android secure, don't know if that made a difference or not). It works great; i.e. no call quality issues. I did not flash a radio.
So, essentially what I did was:
1. Went back to stock unrooted (Kies put me on latest 4.0.4 from T-Mobile, which flashed a radio, the rom and cleared internal storage)
2. Rooted and installed TWRP
3. Flashed my rom of choice, but not a radio and I didn't wipe android secure (not sure if that matters)
Honestly I don't know what about that process fixed the echo issues, all I know is it did. If you can't go back to stock unrooted through Kies then use Odin. There are great threads giving step by step instructions on how to do that. I just decided using Kies would be easiest for me, and it worked for me.
I hope these are the details you are looking for FineTalent. And thanks.

Excellent lol. If you own the d30 case from tmobile take it off. Worked for me as well.

I do have the d30 case but taking it off didn't seem to make a difference. Besides, the wife didn't like the idea of my phone going commando.

I used odin to go back to stock and the call quality was great. But as soon as i installed an AOSP rom (All Star Rom V6) the echo was back.

I did not know that LI1 was the latest 404 ROM ?
I can only get VLH1 as the latest ROM.
I know there is a LI1 radio available, but have never seen the LI1 rom itself, especially not on SamMobile/Firmware site.
Any links to the "official LI1 ROM"
Thanks

bert269 said:
I can only get VLH1 as the latest ROM.
I know there is a LI1 radio available, but have never seen the LI1 rom itself, especially not on SamMobile/Firmware site.
Any links to the "official LI1 ROM"
Thanks
Click to expand...
Click to collapse
It was simply the latest one Kies found for my phone. I believe it was labeled as UVLI1/TMDLI1, but I suppose I could be mistaken. If you install Kies on your computer (shudder, I know) and plug your phone in it will compare the rom version on your phone to the latest known rom from tmobile/samsung. You will need your phones serial number I believe. At least, it was needed when I "upgraded" anyway.

whytechapel_x said:
I used odin to go back to stock and the call quality was great. But as soon as i installed an AOSP rom (All Star Rom V6) the echo was back.
Click to expand...
Click to collapse
Can you give the following information:
1. Method of obtaining root
2. Custom recovery odined when obtaining root (I assume it's cwm 5.0.2.7)
3. Custom recovery used to flash AOSP rom
4. Steps taken to flash AOSP rom (I don't want this thread to become a "this is how I flash" thread, but I want to know what was different between your experience and mine, so wipe and install steps would be great)
5. Any mods flashed/done before testing call quality (or was it completely clean, i.e. just rom and gapps)
6. Which gapps did you flash (mine was latest for 4.1.2, so gapps released on oct. 11, anything later is for jb 4.2 and not compatible with 4.1.2 according to release notes)

monkeybuttons said:
Can you give the following information:
1. Method of obtaining root
2. Custom recovery odined when obtaining root (I assume it's cwm 5.0.2.7)
3. Custom recovery used to flash AOSP rom
4. Steps taken to flash AOSP rom (I don't want this thread to become a "this is how I flash" thread, but I want to know what was different between your experience and mine, so wipe and install steps would be great)
5. Any mods flashed/done before testing call quality (or was it completely clean, i.e. just rom and gapps)
6. Which gapps did you flash (mine was latest for 4.1.2, so gapps released on oct. 11, anything later is for jb 4.2 and not compatible with 4.1.2 according to release notes)
Click to expand...
Click to collapse
1.Well i didn't root my stock phone. After using odin
2.I used cwm 6.0.1.5
3.Same.
4. Well i followed the steps in the all star thread which is wipe data/factory reset. Then flashing rom and wiping cache and dalvik cache.
5. The all star rom is heavily modded so idk. I tried it with "noise suppression" on and off.
6. All star gapps.
I want to point out that as soon as i flashed jedi knight 6, the call echo was gone but i want to be able to use my AOSP roms without call echo.

Since I'm not a dev I can't really diagnose the problem. I only hoped that what worked for me would work for others as well.
When I went back to stock I rooted, but didn't like stock. TWRP has been my go to recovery for a while now and the options available in PACman rom have me by the heart strings, so those are the first things I tried. I wish I had time to fiddle around with it and truly try to find out why it worked for me but I just don't have that option right now. Sorry I'm not of more help.

Its OK. But can a dev clarify if maybe clockworkmod is what is causing the call echo? Probably not flashing AOSP ROMs right?

whytechapel_x said:
Its OK. But can a dev clarify if maybe clockworkmod is what is causing the call echo? Probably not flashing AOSP ROMs right?
Click to expand...
Click to collapse
CWM is in no way linked to the call echo issue, however, using the latest version will assist in ensuring your ROMs installs properly. Rather than using CWM I recommend flashing ROMs through TWRP 2.3.3.0, it is the most up to date recovery system for our phones at the moment.

FineTalent said:
CWM is in no way linked to the call echo issue, however, using the latest version will assist in ensuring your ROMs installs properly. Rather than using CWM I recommend flashing ROMs through TWRP 2.3.3.0, it is the most up to date recovery system for our phones at the moment.
Click to expand...
Click to collapse
OK. I went on and installed TWRP anyways and flashed tweakwiz and got call echo once more. I am aware that it flashes the blaze radio but still. Does this mean that my phone came out defective? But why is it that i get absolutely no echo on stock ics and luckily, jedi knight 6 neither? When i was using jedi knight 6,i was using the stock radio uvlh1? But if i have this same radio on AOSP roms or in other ones, i still get call cecho.

whytechapel_x said:
OK. I went on and installed TWRP anyways and flashed tweakwiz and got call echo once more. I am aware that it flashes the blaze radio but still. Does this mean that my phone came out defective? But why is it that i get absolutely no echo on stock ics and luckily, jedi knight 6 neither? When i was using jedi knight 6,i was using the stock radio uvlh1? But if i have this same radio on AOSP roms or in other ones, i still get call cecho.
Click to expand...
Click to collapse
I am not able to exactly help you with your issue as I am using a different ROM than you. However, if you have tried different radios and they did not seem to fix the issue, can you possibly try installing a different kernel? Also, check the phone settings and see if there is an option to turn on 'Noise reduction' which has been mentioned on here before, it seemed to have worked for some people.

So i noticed that i get call echo on all jellybean roms no matter if they are touchwiz or not...frustrating

whytechapel_x said:
So i noticed that i get call echo on all jellybean roms no matter if they are touchwiz or not...frustrating
Click to expand...
Click to collapse
Keep in mind the Touchwiz jb roms are actually built off the leak for the Skyrocket. The same thing happened with ICS way back when and call echo was a rampant problem then as well. I don't recall if anyone really solved the problem before official ICS dropped for Hercules, but I know a lot of devs were working on it.
Call echo in stable AOSP based roms shouldn't be happening. That's what we're trying to correct here.
If you have the time (or are willing), go back to stock unrooted (so you get the radio and everything) and try flashing cm10 stable. Then report back and let us know if call echo still exists. I'm not trying to knock All Star roms, I am just trying to get to the root of your problem and that involves avoiding flashing a radio. As far as I can tell, the flashing of the radio is the biggest difference between your experience and mine.

monkeybuttons said:
Keep in mind the Touchwiz jb roms are actually built off the leak for the Skyrocket. The same thing happened with ICS way back when and call echo was a rampant problem then as well. I don't recall if anyone really solved the problem before official ICS dropped for Hercules, but I know a lot of devs were working on it.
Call echo in stable AOSP based roms shouldn't be happening. That's what we're trying to correct here.
If you have the time (or are willing), go back to stock unrooted (so you get the radio and everything) and try flashing cm10 stable. Then report back and let us know if call echo still exists. I'm not trying to knock All Star roms, I am just trying to get to the root of your problem and that involves avoiding flashing a radio. As far as I can tell, the flashing of the radio is the biggest difference between your experience and mine.
Click to expand...
Click to collapse
will do. but if i remember, i would still get call echo on aokp milestone 1

whytechapel_x said:
will do. but if i remember, i would still get call echo on aokp milestone 1
Click to expand...
Click to collapse
Have you tried any ICS based AOSP roms? Like cm9.1 or AOKP (I can upload the file for you if you want; it is no longer on goo.im). I think I kept ICS AOKP the longest of any rom.

[Q] Flashed update, now I have a blank screen

Hey all -
I have a T-Mobile Galaxy SIII with TWRP, AOKP JB Milestone 5 and GooManager. I got a pop-up for AOKP JB Milestone 6 this morning, so I downloaded it and added that file, Lean Kernel 2.9 and gapps (latest that could be downloaded) to the flash list. I set my Dalvik cache to clear before flashing anything, then rebooted the phone to flash everything. Immediately after the flash, the phone seemed to reboot, but with a blank screen. After a while, the capacitive buttons on the front started working and when I plugged the phone into my computer the file transfer program popped up.
However ... at no point can I ever get anything to display on the screen. I've tried rebooting into recovery (volume up, home button, power button) and nothing. I don't really care about the data on my phone, I have proper backups of everything. But what I can't seem to do is get it to a point where I can recover it. What are my options here if rebooting into recovery doesn't work?
Thanks!

As an addendum, the phone is clearly booted into the OS. I have a blinking notification LED that indicates a new e-mail, and calls placed to the phone cause it to ring. I just can't see .... anything on it.

I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.

chuffykow said:
I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.
Click to expand...
Click to collapse
so was you able to use your phone again i say go back to a nandroid you have or flash a rom that you know works good on your phone without that white screen and trouble shoot from there that it very strange indeed if you get success with the other just try posting in the ROM thread that you flashed you could possibly get more help where it happened :good:

I went back to AOKP Milestone 5 after doing a full wipe. I saw a number of graphics changes in the Milestone 6 code review, so it's possible that had something to do with it. In any case, I'm no longer panicing

Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.

Ya its all kernel related and user error.

Aerowinder said:
Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.
Click to expand...
Click to collapse
mt3g said:
Ya its all kernel related and user error.
Click to expand...
Click to collapse
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.

chuffykow said:
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.
Click to expand...
Click to collapse
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.

mt3g said:
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.
Click to expand...
Click to collapse
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.

I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.

chuffykow said:
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.
Click to expand...
Click to collapse
calm down lol, you could have read up any of the kernel threads that there are some compatible issues with kernels and roms right now.

Aerowinder said:
I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.
Click to expand...
Click to collapse
Thanks for the tip! I appreciate it.

[Q] CyangenMod 10 Issues (Install,Voicemail,Skype)

I tried to post this on cyanogen mods website but I was not allowed to post
I bought a AT&T Galaxy S III for my wife this weekend and ran into several problems installing cyanogenmod 10 on it.
Installing:
First the Heimdall program failed to "initialize interface" and no matter what I tried it failed to connect.
I managed to get it installed by using the ODIN to flash different clockwork mod (but that errored out on the when I went to flash cyanogenmod 10 )
So I used that to root it then installed cyanogenmod via rom manager by having that install the right clockwork mod then cyanogen 10.
It would be nice if they provided a ODIN Image for cyanogenmod
VoiceMail:
voicemail was missing its number after I installed cyanogen mod.
It took me forever to get this correct. Found out that you just forward to your mobile number. In the phone settings. or dial **004*PhoneNumber#
Also Google voice failed to setup correctly as well and had to use the **004 path.
Skype:
downloading via google play kept returning "package file invalid" (I cleared /cache and dalvik cache still failed) I ended up downloading it via the androiddrawer website and it installed (sideload?).
The problem with this is when using the voice or video chat the other side just hears very load static. Found someone claiming these problems came from cyanogenmod 10 not using the correct mics all the time. This is still an issue.
My questions are these issues fixed in the most recent version of Cyanogen the M releases? And if not are they known and someone working on them?
And does anyone have a fix for the static issue in skype?

JonoPorter said:
I tried to post this on cyanogen mods website but I was not allowed to post
I bought a AT&T Galaxy S III for my wife this weekend and ran into several problems installing cyanogenmod 10 on it.
Installing:
First the Heimdall program failed to "initialize interface" and no matter what I tried it failed to connect.
I managed to get it installed by using the ODIN to flash different clockwork mod (but that errored out on the when I went to flash cyanogenmod 10 )
So I used that to root it then installed cyanogenmod via rom manager by having that install the right clockwork mod then cyanogen 10.
It would be nice if they provided a ODIN Image for cyanogenmod
VoiceMail:
voicemail was missing its number after I installed cyanogen mod.
It took me forever to get this correct. Found out that you just forward to your mobile number. In the phone settings. or dial **004*PhoneNumber#
Also Google voice failed to setup correctly as well and had to use the **004 path.
Skype:
downloading via google play kept returning "package file invalid" (I cleared /cache and dalvik cache still failed) I ended up downloading it via the androiddrawer website and it installed (sideload?).
The problem with this is when using the voice or video chat the other side just hears very load static. Found someone claiming these problems came from cyanogenmod 10 not using the correct mics all the time. This is still an issue.
My questions are these issues fixed in the most recent version of Cyanogen the M releases? And if not are they known and someone working on them?
And does anyone have a fix for the static issue in skype?
Click to expand...
Click to collapse
Unless your wife can troubleshoot issues why install a custom ROM on her phone. My wife would kill me since she has no clue but I digress.
Why not flash 10.1 on the phone and download the gapps from the goo.im site and see if hat helps your issues. Maybe you got a bad flash and/or download. For the short amount of time I tried it I didn't have any of these issues you do. Those don't seem to be any bugs in the known bugs beyond maybe the static. Task's AOKP is another one to try if you want a custom stable rom.
Try another ROM or maybe a fairly stock rooted rom and see if that clears up any issues.
Are you using a Mac or a PC ? You mentioned Odin (for windows PC's) and heimdall (for all others). Honestly the best way is to flash a stock rooted ROM from the no tripping flash counter Rooting thread in Development and then flashing CWM in rom manager. Limiting having to flash in odin is the far better option. I've never ha d a bad flash in a custom recovery but everytime I have to use Odin I get extremely nervous.
Read Beerdroid's guide and you can't go wrong

hednik said:
Unless your wife can troubleshoot issues why install a custom ROM on her phone. My wife would kill me since she has no clue but I digress.
Why not flash 10.1 on the phone and download the gapps from the goo.im site and see if hat helps your issues. Maybe you got a bad flash and/or download. For the short amount of time I tried it I didn't have any of these issues you do. Those don't seem to be any bugs in the known bugs beyond maybe the static. Task's AOKP is another one to try if you want a custom stable rom.
Try another ROM or maybe a fairly stock rooted rom and see if that clears up any issues.
Are you using a Mac or a PC ? You mentioned Odin (for windows PC's) and heimdall (for all others). Honestly the best way is to flash a stock rooted ROM from the no tripping flash counter Rooting thread in Development and then flashing CWM in rom manager. Limiting having to flash in odin is the far better option. I've never ha d abad flahs in a custom recovery but everytime I have to use Odin I get extremely nervous.
Click to expand...
Click to collapse
agreed.
there are a couple good and stable stock/touchwiz custom roms as well as AOSP-based roms on this forum. i would steer clear of nightlies and super-custom roms that are always posting new updates. these are less stable imo.
put something on her phone thats solid and be sure to use the proper wiping and flashing procedures when you do so. wiping/flashing correctly makes ALL the difference on the software's performance while it's running on a device

xBeerdroiDx said:
agreed.
there are a couple good and stable stock/touchwiz custom roms as well as AOSP-based roms on this forum. i would steer clear of nightlies and super-custom roms that are always posting new updates. these are less stable imo.
put something on her phone thats solid and be sure to use the proper wiping and flashing procedures when you do so. wiping/flashing correctly makes ALL the difference on the software's performance while it's running on a device
Click to expand...
Click to collapse
Well I went with Cyanogen because I used it on my old droid incredible and its was great. I also want a stock like rom because I personally use a stock Nexus 4 and want my wifes phone to be similar and wanted to remove all the retarded extra apps atnt and samsung threw on.
So no idea if the 10.1 would fix the static issue then?

JonoPorter said:
Well I went with Cyanogen because I used it on my old droid incredible and its was great. I also want a stock like rom because I personally use a stock Nexus 4 and want my wifes phone to be similar and wanted to remove all the retarded extra apps atnt and samsung threw on.
So no idea if the 10.1 would fix the static issue then?
Click to expand...
Click to collapse
I can't say for sure but download and see if it works out of you. Thing with bugs is that they aren't always reproducible. I don;t see your issue as a known bug on 4.2.2. There are a few other ROM like super nexus in the dev section that are a practically stock nexus feel. Why not give that one a try ? Give AOKP a try as well.
Here's super nexus:
http://forum.xda-developers.com/showthread.php?t=2219944

hednik said:
I can't say for sure but download and see if it works out of you. Thing with bugs is that they aren't always reproducible. I don;t see your issue as a known bug on 4.2.2. There are a few other ROM like super nexus in the dev section that are a practically stock nexus feel. Why not give that one a try ? Give AOKP a try as well.
Here's super nexus:
http://forum.xda-developers.com/showthread.php?t=2219944
Click to expand...
Click to collapse
i'm an advocate of AOKP, but thats just my 2 cents. there is a very solid 4.1.2 milestone out and their 4.2.2 milestone will be released very soon.
although faryaab is a great kid and puts some good stuff together, remember that supernexus is a port and you could experience bugs (as i did). again, just my opinion

[Q] CWRM / TWRP Charging?

Hello,
I've read through the Everything thread on Development, as well as searched using the xda search and google site search, but come up with nothing.
The Everything thread mentions that the current version of CWRM won't charge when the phone is off or in recovery, but I can't find anything about which version is the 'latest' (6.0.1.2, 5.0.2.7), nor if this also affects the TWRP recoveries (2.6.3, 2.4.1)? For that matter, I can't find anything that even mentions the charging problems at all aside from the Everything thread!
If there is a charging problem with all of the third party ROMs, is there a method to go back to the stock recovery after flashing in a ROM and backing up /efs/? I'm basically shooting for a fully functional phone and I don't plan on changing ROMs all over the place, just root and ICS.
Help?
Thanks!

TooG435 said:
Hello,
I've read through the Everything thread on Development, as well as searched using the xda search and google site search, but come up with nothing.
The Everything thread mentions that the current version of CWRM won't charge when the phone is off or in recovery, but I can't find anything about which version is the 'latest' (6.0.1.2, 5.0.2.7), nor if this also affects the TWRP recoveries (2.6.3, 2.4.1)? For that matter, I can't find anything that even mentions the charging problems at all aside from the Everything thread!
If there is a charging problem with all of the third party ROMs, is there a method to go back to the stock recovery after flashing in a ROM and backing up /efs/? I'm basically shooting for a fully functional phone and I don't plan on changing ROMs all over the place, just root and ICS.
Help?
Thanks!
Click to expand...
Click to collapse
I think something like 6.0.4 the latest CWMR. ( you can build with http://builder.clockworkmod.com/ , Existing Device option doesnt work)
It charges in latest TWRP, you can see "+" char when on charge next to the battery level.
Stock uses recovery for official upgrade, and factory reset. We have only offline charge issue, but recovery has no effect on it. Offline charger works with a limitation. I wouldnt bother you with the explanation, since you said you would like to use stock ICS.
You can backup efs in rooted rom without recovery. You can always flash recovery with odin phone in download mode.

Thanks.
I guess I had assumed the comment was referring to the builds in the Development forum, not the overall CWMR project! Is there a currently recommended recovery, or is it a toss up to personal preference? I'm not so much tied to ICS as tied to a completely working ROM - especially as I see all the bluetooth and skype issues with the JB ROMs, which (as far as I can tell) are still unresolved / unknown?

TooG435 said:
Thanks.
I guess I had assumed the comment was referring to the builds in the Development forum, not the overall CWMR project! Is there a currently recommended recovery, or is it a toss up to personal preference? I'm not so much tied to ICS as tied to a completely working ROM - especially as I see all the bluetooth and skype issues with the JB ROMs, which (as far as I can tell) are still unresolved / unknown?
Click to expand...
Click to collapse
I make TWRP for i927, we dont have other up to date, but you can build yourself.
Dont you have issue with stock ICS? I made up to date issue list in me CM 10.2, you could decide it suit for you or not, you may know stock limitation already.
I hope voip issue would be resolved soon.

bubor said:
I make TWRP for i927, we dont have other up to date, but you can build yourself.
Dont you have issue with stock ICS? I made up to date issue list in me CM 10.2, you could decide it suit for you or not, you may know stock limitation already.
I hope voip issue would be resolved soon.
Click to expand...
Click to collapse
My only real requirement in a phone is that it be reliable - I don't want to have to pop out batteries or have no audio on calls if I get stranded in the middle of nowhere. At this point, my phone is still in the mail - got a used one from a friend, but it hasn't arrived, so I haven't had much ability to experiment yet.
My Android experience is exclusively with a Transformer TF101, which had 4.0.4 ICS stock and is currently running Katkiss JB 4.2.2_226 (Katkiss 4.3 isn't stable enough for me yet, was getting daily crashes last time I tried). All of the phone components are new to me - and the Glide seems to have a more fragmented recovery scene than the TF101, which is pretty much TWRP or nothin'
Thanks again for your help!

[Q] Questions around SPH L900 and Cyanogenmod (GPS, Camera & Call Volume)

So, I'm new to this and have a Note 2 (SPH L900) from Sprint. I am trying to learn the terminology but I'm a quick study through interactive conversations in a forum board like this. I put cyanogenmod using clockwork on my rooted phone and I've noticed that the GPS fails to get a lock, the camera goes in and out of focus while recording video and the call volume is very low when I'm making a phone call.
For the GPS thing someone said to flash a stock TouchWiz and then re-flash cyanogenmod back on it and that seems to have fixed it. In my searches on how to do this or where to even get a TouchWiz I lost that original thread. Can someone help me understand how to get the original TouchWiz?
As far as the camera thing, I'm not sure if there's a different camera app that would suffice?
And the call volume I remember reading somewhere that there's a file that you can edit to change the call volume.
I've been all over trying to get this device working with cyanogenmod and getting lost in the interwebs and the terminology that I'm not used to. I've been recently starting to wonder if I should just go back to the original out of the box installation but I don't know how to do that either!?! LOL!
Thanks in advance for any and all help!

XDKYX said:
So, I'm new to this and have a Note 2 (SPH L900) from Sprint. I am trying to learn the terminology but I'm a quick study through interactive conversations in a forum board like this. I put cyanogenmod using clockwork on my rooted phone and I've noticed that the GPS fails to get a lock, the camera goes in and out of focus while recording video and the call volume is very low when I'm making a phone call.
For the GPS thing someone said to flash a stock TouchWiz and then re-flash cyanogenmod back on it and that seems to have fixed it. In my searches on how to do this or where to even get a TouchWiz I lost that original thread. Can someone help me understand how to get the original TouchWiz?
As far as the camera thing, I'm not sure if there's a different camera app that would suffice?
And the call volume I remember reading somewhere that there's a file that you can edit to change the call volume.
I've been all over trying to get this device working with cyanogenmod and getting lost in the interwebs and the terminology that I'm not used to. I've been recently starting to wonder if I should just go back to the original out of the box installation but I don't know how to do that either!?! LOL!
Thanks in advance for any and all help!
Click to expand...
Click to collapse
For the GPS issue, Flash the rom found here http://forum.xda-developers.com/note-2-sprint/development/classic-stock-ne2-4-4-2-deodexed-t2818246 , You don't even have to set up all the accounts just go in open up MAPS get the GPS lock then Flash back to your Cyanogenmod Rom and your GPS should work.
Now for the call volume I know alot of Roms are having issues with this. When you get or make a call what i do is after the call is started I turn my volume down as far as it will go and then turn it back up and the call volume is fine. If there is a fix for this I haven't ran across it yet.
Your camera Issue i haven't ran across that myself. But i'll browse these forums and see what i can come up with.

There are several CM based ROMS to choose from. If you prefer CM over TW (Samsung's interface overlay) then you should visit the development forums and choose a ROM that you feel is right for you. Personally I like Slim ROM and Carbon ROMs. The volume bug effects CM ROMS but there are a few ROMS that volume has been "pre-tweaked". Otherwise during a call turn volume down then back up and it should be much louder.
CM cameras tend to be slightly subpar to the stock TW camera as far as picture quality, lag, and focusing, etc, but for the most part all CM cameras do work ok. I personally prefer the stock TW based camera but that's not an option if using a CM based ROM.
There's no other way around the GPS bug other than what has been mentioned. Simply flash a stock type ROM that is based off the Samsung Touch Wiz ui overlay and do as Sothus said. Get a solid GPS lock using google maps. I highly recommend doing the same thing for LTE at the same time. Get in LTE coverage and make sure your phone is connected to LTE data service then get the GPS lock with Google Maps. Then immediately reboot into recovery, wipe system, data, cache, dalvic cache, flash MK4 or NE2 modem, then flash the ROM.
Also make sure you are using a current version of Clockwork recovery or better yet use Phil's version of Clockwork recovery. You can find it in the regular development forum not original development forum. Good luck.

tx_dbs_tx said:
There are several CM based ROMS to choose from. If you prefer CM over TW (Samsung's interface overlay) then you should visit the development forums and choose a ROM that you feel is right for you. Personally I like Slim ROM and Carbon ROMs. The volume bug effects CM ROMS but there are a few ROMS that volume has been "pre-tweaked". Otherwise during a call turn volume down then back up and it should be much louder.
CM cameras tend to be slightly subpar to the stock TW camera as far as picture quality, lag, and focusing, etc, but for the most part all CM cameras do work ok. I personally prefer the stock TW based camera but that's not an option if using a CM based ROM.
There's no other way around the GPS bug other than what has been mentioned. Simply flash a stock type ROM that is based off the Samsung Touch Wiz ui overlay and do as Sothus said. Get a solid GPS lock using google maps. I highly recommend doing the same thing for LTE at the same time. Get in LTE coverage and make sure your phone is connected to LTE data service then get the GPS lock with Google Maps. Then immediately reboot into recovery, wipe system, data, cache, dalvic cache, flash MK4 or NE2 modem, then flash the ROM.
Also make sure you are using a current version of Clockwork recovery or better yet use Phil's version of Clockwork recovery. You can find it in the regular development forum not original development forum. Good luck.
Click to expand...
Click to collapse
Thanks!
Is there a screen on my phone that I go into to "Get in LTE coverage"?

XDKYX said:
Thanks!
Is there a screen on my phone that I go into to "Get in LTE coverage"?
Click to expand...
Click to collapse
no. You have to be in a geological location where Sprint provides 4G LTE. You'll need to go to Sprint.com and see what areas are suppose to have it.

And then just by turning on my phone in one of those locations is all I would need to do? Or should I make a phone call?
Sent from my SPH-L900 using XDA Free mobile app

XDKYX said:
And then just by turning on my phone in one of those locations is all I would need to do? Or should I make a phone call?
Sent from my SPH-L900 using XDA Free mobile app
Click to expand...
Click to collapse
So I did this and it works great, the volume trick works and the GPS lock worked. thank you both so much!
On a side question is there anywhere that I can download the stock "L900VPUCNE2" ROM to flash with Clockwork in case I want to go back? I found a topic on this site that talks about when the upgrade was released but I Google and can't find a solid ROM that I can use to flash back. Thanks in advance!!!

XDKYX said:
So I did this and it works great, the volume trick works and the GPS lock worked. thank you both so much!
On a side question is there anywhere that I can download the stock "L900VPUCNE2" ROM to flash with Clockwork in case I want to go back? I found a topic on this site that talks about when the upgrade was released but I Google and can't find a solid ROM that I can use to flash back. Thanks in advance!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2780984

Stock ROM?
lennykravitz2004 said:
http://forum.xda-developers.com/showthread.php?t=2780984
Click to expand...
Click to collapse
so, this link that lennykravitz2004 just posted is the stock ROM that my phone would currently have or had before I put cyanogenmod on it, right? I just want to make sure before I start messing with it that this is in fact the same as what I had. I accidentally deleted the backup that I had through clockworkmod (not that the backup worked anyway) and want to try and make a solid stock backup. Thanks in advance!

XDKYX said:
so, this link that lennykravitz2004 just posted is the stock ROM that my phone would currently have or had before I put cyanogenmod on it, right? I just want to make sure before I start messing with it that this is in fact the same as what I had. I accidentally deleted the backup that I had through clockworkmod (not that the backup worked anyway) and want to try and make a solid stock backup. Thanks in advance!
Click to expand...
Click to collapse
Yes that is pure stock ROM. Note that when you use Odin to flash this you will have stock ROM, kernel, and recovery also it will not be rooted.
Sent from my XT1045 using XDA Free mobile app