Related
Until yesterday I used several different ROMs, without having any sound problem.
The problem started when I flashed Syiah kernel 1.2.6 (which might be a coincidence), while being on OMEGA-ROM. Thereafter I couldn't hear anything in phone calls any more (but others can hear me) on any ROOTED firmware or ROMs.
Reverting back to Syiah 1.1 (or switching to any other kernel) didn't help, neither did flashing any other rom.
Full wipe (including all storage space) solved the problem temporarlily. But after reboot no sound in phone calls again. Also changing the modem first helped, but the problem re-appeared after the first reboot.
Finally I flashed stock rom (LF2) via ODIN. Now the problem was solved - I believed. I could hear people in phone calls even after several reboots. But as soon as I rooted the phone with CF-Root AND changed some files on /system/media/ui the call sound was gone again after the following re-boot.
I reflashed again to stoch firmware via ODIN and now I have to live with an unrooted phone, which is not the worst thing in the world. But I really would like to be able to use custom ROMs again...
Anyone with similar experiences or with any idea about possible causes and/or solutions???
*** via Tapatalk ***
citronbitare said:
Until yesterday I used several different ROMs, without having any sound problem.
The problem started when I flashed Syiah kernel 1.2.6 (which might be a coincidence), while being on OMEGA-ROM. Thereafter I couldn't hear anything in phone calls any more (but others can hear me) on any ROOTED firmware or ROMs.
Reverting back to Syiah 1.1 (or switching to any other kernel) didn't help, neither did flashing any other rom.
Full wipe (including all storage space) solved the problem temporarlily. But after reboot no sound in phone calls again. Also changing the modem first helped, but the problem re-appeared after the first reboot.
Finally I flashed stock rom (LF2) via ODIN. Now the problem was solved - I believed. I could hear people in phone calls even after several reboots. But as soon as I rooted the phone with CF-Root AND changed some files on /system/media/ui the call sound was gone again after the following re-boot.
I reflashed again to stoch firmware via ODIN and now I have to live with an unrooted phone, which is not the worst thing in the world. But I really would like to be able to use custom ROMs again...
Anyone with similar experiences or with any idea about possible causes and/or solutions???
*** via Tapatalk ***
Click to expand...
Click to collapse
Really nobody who could help???
Can you record sound with other apps?
That should see if its a problem with just the phone apk or a more native problem.
Sent from my GT-I9300 using xda premium
Well, others can hear me but I can't hear them in phone calls. There is no problem with the phone speaker, because I can use viber without problems.
*** via Tapatalk ***
BUMP! I'm having the same problem!
I'm hoping it's not a hardware problem.
I wonder if any dev can chime in.
Well, it shouldn't be hardware related, because there is no problem on unmodified stock firmware.
*** via Tapatalk ***
Zabalba said:
BUMP! I'm having the same problem!
I'm hoping it's not a hardware problem.
I wonder if any dev can chime in.
Click to expand...
Click to collapse
You have the same problem, but after flashing syiah?
If yes it is not coincidence i think.
Kernel has sound modifications for last version 1.26
Sent from my GT-I9300 using xda premium
I noticed I had the problem intermittently when I first started using Foxhound on Saturday. Foxhound comes bundled with Syiah.
I thought it was something else all together. I asked in the Foxhound thread and only one other person +1'd my post. Today I switched to Omega hoping it the problem would go away and it was actually worse.
I was testing just now and every time I called my phone I could hear nothing on my handset or through headphones. Just in case I did't accidentally flubbed anything else up I unfroze all the TB apps I had frozen to see if it was working. Interestingly after defrosting and rebooting I can hear again. Attached are the apps I had frozen.
But this has not been the first time it was working correctly and then go back to not hearing calls.
JJEgan said:
Kernel has sound modifications for last version 1.26
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I strive for that. What I would do:
Flash stock rom
Factory reset via stock recovery
flash stock
cfroot
and then check if it is still a problem.
That is why the topic OMEGA asked that the next versions were the stock kernel.
That is why in order to avoid such problems.
marcinrek21 said:
You have the same problem, but after flashing syiah?
If yes it is not coincidence i think.
Click to expand...
Click to collapse
Yes, it all started after flashing syiah 1.2.6. So maybe it's not a coincidence after all.
*** via Tapatalk ***
Zabalba said:
I noticed I had the problem intermittently when I first started using Foxhound on Saturday. Foxhound comes bundled with Syiah.
I thought it was something else all together. I asked in the Foxhound thread and only one other person +1'd my post. Today I switched to Omega hoping it the problem would go away and it was actually worse.
I was testing just now and every time I called my phone I could hear nothing on my handset or through headphones. Just in case I did't accidentally flubbed anything else up I unfroze all the TB apps I had frozen to see if it was working. Interestingly after defrosting and rebooting I can hear again. Attached are the apps I had frozen.
But this has not been the first time it was working correctly and then go back to not hearing calls.
Click to expand...
Click to collapse
For me it has also been an intermittent problem. Kernel changes, modem changes, wipes, etc often temporarily helped - but only for one boot cycle. A reboot always brought the problem back. Only on stock firmware I can always hear.
*** via Tapatalk ***
marcinrek21 said:
I strive for that. What I would do:
Flash stock rom
Factory reset via stock recovery
flash stock
cfroot
and then check if it is still a problem.
That is why the topic OMEGA asked that the next versions were the stock kernel.
That is why in order to avoid such problems.
Click to expand...
Click to collapse
I have done exactly that - and the problem is gone as long as you only do these steps. But modifying the system partition in any way (changing, deleting or adding files or flashing custom rom) brings you back to square one.
*** via Tapatalk ***
citronbitare said:
I have done exactly that - and the problem is gone as long as you only do these steps. But modifying the system partition in any way (changing, deleting or adding files or flashing custom rom) brings you back to square one.
*** via Tapatalk ***
Click to expand...
Click to collapse
And may you have an earlier backup? Stock with cfroot or similar?
marcinrek21 said:
And may you have an earlier backup? Stock with cfroot or similar?
Click to expand...
Click to collapse
The sound problem is there even when I restore earlier backups. Now I am on stock firmware and everything is okay.
But I would like to use custom ROMs again with working phone call function, which is not possible for now.
*** via Tapatalk ***
This is the weirdest problem that I have seen here.
Just a status update. I have done some more testing and obviously what makes call sounds not to work is certain changes to the system partition (as compared to stock firmware).
In my case call sound works as long as I am on stock firmware (no matter what stock firmware; I have tested three or four different ones). If I root stock firmware with CF-root I still have call sound. I also can change kernels and it is possible to modify host files with ad-free.
However, as soon as I manually change or modify anything on the system-partition with root explorer or when I install custom ROMs the call sound disappears after the next reboot - no matter what radio I use. I also have tested the radio from the newest malaysian firmware which has surfaced today.
citronbitare said:
Just a status update. I have done some more testing and obviously what makes call sounds not to work is certain changes to the system partition (as compared to stock firmware).
In my case call sound works as long as I am on stock firmware (no matter what stock firmware; I have tested three or four different ones). If I root stock firmware with CF-root I still have call sound. I also can change kernels and it is possible to modify host files with ad-free.
However, as soon as I manually change or modify anything on the system-partition with root explorer or when I install custom ROMs the call sound disappears after the next reboot - no matter what radio I use. I also have tested the radio from the newest malaysian firmware which has surfaced today.
Click to expand...
Click to collapse
Thanks for your testing!
Like I mentioned in my earlier post I unfroze all of the apps and I have not run into the issue. My phone is running Omega 5.2 with Siyah 1.2.6. I'm totally expecting the problem to return but it has not so far. I wish it was consistent and reproducible.
Zabalba said:
Thanks for your testing!
Like I mentioned in my earlier post I unfroze all of the apps and I have not run into the issue. My phone is running Omega 5.2 with Siyah 1.2.6. I'm totally expecting the problem to return but it has not so far. I wish it was consistent and reproducible.
Click to expand...
Click to collapse
I'll keep my fingers crossed and hope that you have finally gotten rid of this problem. And thanks btw for asking Chainfire and Indie too look at this thread!
*** via Tapatalk ***
I got that problem myself, the only thing that really helped for me is to
flash my Stock Rom that where on the Phone out of the Box... since 2 Days
the Bug is gone. But havent tried any other Stock Rom.
I want to try Omega 6.0 Rom...(now)
I was thinking about flashing CF-Root and do those steps before custom:
1. Wipe Data/Factory Reset
2. Wipe Cache Partition
3. In Advanced ---> Format System/Cache/Data (someone tried this before?)
4. Flash the Rom.
My Question is for those guys like me where the only solution is to stay on
non rooted stock rom, have you tried flashing a custom rom with step 3. from above and still encounter the call issue?
I read somewhere that with step 3. the Phone is really FULL WIPE.
Sorry for my bad english :silly:
*READ BELOW FOR A GUIDE TO FIX*
I've had my note for over a year now and i have had it rooted pretty much the entire time. Never any problems with it up until recently it started doing this thing where it would keep restarting. It would boot up and less than a minute later just restart. Off and on for a few days it was doing this. I was still running 2.3.6 at that point. So i decided to push 4.0.4 via odin since kies didnt support the firmware. Everything was working fine for a few hours then all of the sudden "the ring of death" showing me no service. Went through the phone and noticed it was saying there is no sim inserted. Tested sim on another phone. Works fine. Since then ive figured out via kies i can recovery and update firmware. Tried that. No Bueno. Now im to the point where im on 4.0.4 with no service. I've scoured through forums trying all kinds of different things, pushing different roms and modems via odin and cwm. Still no bueno.
Baseband version
Unknown
Kernel Version
3.0.8
Build Number
IMM76D.UCLF6
If anyone can give me ideas im willing to try them out.
Thanks.
I got it working so heres a direction for anyone else who has this issue!
Replaced Sim&SD card reader-No fix
After flashing all kinds of roms & modems still same issue saying no sim inserted.
Do a hard reset through your settings.
Flash cwm and put the radio from this link on your sd card. Use cwm to flash the radio.
Flash rom http://forum.xda-developers.com/showthread.php?t=2261598 via odin.
The first try i got an error during flash and got stuck on the software download error screen.
Reflashed the JB rom.
After its flashed flash clockwork recovery.
Enter cwm and do a factory reset. Clear cache. Clear dalvik cache. Reboot system.
If you get service, turn off phone. enter cwm and do a backup.
Reboot system.
It should be working.
If not restart and make sure to do a factory reset through your settings in the phone before reflashing rom.
Got the Phone up and running for about 30 mins.
After battery removed it reverted back to no sim card inserted.
Kept reflashing rom until it worked again.
Flashed cwm.(ClockworK recovery mod)
Deleted cache, dalvik cache
Backed up via cwm
If it reverts back to no sim after that restore using the cwm backup.-it worked for me
Now for the tricky part, my phone was getting crappy service...
So heres what i did to fix it.
Settings-more settings-mobile networks-access point names-click on the apn.
Name-
ATT Phone
APN-
Phone
Proxy-
Not set
Port
Not set
User Name-
Not set
Password-
Not set
Server-
Not set
MMSC-
http://mmsc.mobile.att.net
MMS Proxy-
proxy.mobile.att.net
MMS Port-
80
MCC-
310
MNC-
410
Authentication type-
None
APN type-
default,admin,fota,mms,supl,hipri,internet
APN protocol-
IPv4
Enable/disable APN-
(check mark)
Bearer-
Unspecified
Hope this helps anyone else having this issue.
I believe I've read something like this before. I think they fixed it by starting over from scratch. Try returning to stock thru Odin. Then root and flash rom of choice.
440bro said:
I believe I've read something like this before. I think they fixed it by starting over from scratch. Try returning to stock thru Odin. Then root and flash rom of choice.
Click to expand...
Click to collapse
I Started from scratch via "kies emergency recovery".
No luck.
dweeezy said:
I Started from scratch via "kies emergency recovery".
No luck.
Click to expand...
Click to collapse
did you try rolling back to GB? it could be a bad port on your phone. that was my problem.
Stuck power button. Your pants are too tight.
Theoriginalgiga said:
did you try rolling back to GB? it could be a bad port on your phone. that was my problem.
Click to expand...
Click to collapse
i ordered a new sim port to see if that works. what is gb?
Same situation...finally went to ATT and had a "new" phone sent under warranty. Of course NOW I'm pulling my hair out trying to migrate everything over to the new phone. I rooted and every ROM I try and install aborts. **** me. I don't even know where to start anymore
dweeezy said:
i ordered a new sim port to see if that works. what is gb?
Click to expand...
Click to collapse
GB stands for Gingerbread which was the first version of the OS that came with the phone. I believe the number was 2.3.6 (you can take a look in the about section in the settings and it'll tell you what you're currently running). ICS is Ice Cream Sandwhich which for our phone was 4.0.4 i believe. Jelly bean just came out today which you can use Kies to upgrade to and that I believe is 4.1.2. The numbers don't really mean a think, just the classification of what the OS is so if your phone reads something else (say 2.3.4) assume your phone is right and I'm wrong. I can't remember OS versions to save my life haha.
But you can use Kies to do an emergency recovery and I THINK it'll install Gingerbread. that's where I'd start, then test it, and then move to ICS and test, and then move to JB and test. I know long tedious process, but sometimes it's necessary. Imagine how fun I am to talk to on the phone while troubleshooting a computer :laugh:
redman9 said:
Same situation...finally went to ATT and had a "new" phone sent under warranty. Of course NOW I'm pulling my hair out trying to migrate everything over to the new phone. I rooted and every ROM I try and install aborts. **** me. I don't even know where to start anymore
Click to expand...
Click to collapse
what I use to migrate, and I between roms at least once a week with a full wipe because I rely on my phone being stable.
SMS and call logs: SMS Backup + (saves your call logs and sms to your gmail account. Makes a label for it and everything, pretty sweet. You can also restore from it. it takes about an hour for me to restore at 7000+ text messages).
pictures/media: stored on SD card
apps: if rooted and rommed I use titanium backup and run 2 sets. those which I want to keep my data like sms backup + to make restore easier and those I don't care about the data like google voice. If you're stock, just remember to check the little box in the beginning saying backup this phone to google (or something like that) and the next time you have to restore tick the box that says restore from google (or something like that) and it'll reinstall your apps. Mind you not the info, but it'll give you a head start.
As with your issue with installing roms. If you're using CWM i highly recommend switching to TWRP, not saying it's better in fact I like CWM better, but TWRP is the best for our roms and phone. If you have no clue what I mean by CWM or TWRP, read the all info sticky about how to rom thy phone.
I hope that helps.
Thanks OG. Yes, I know CMW and TWRP. I used to switch ROMs a lot. Finally stuck with Collective's latest (the orange one) pretty happy with it except that it's major glitch seems to be reboots whenever an app updates. So I figured unchecking auto update in Gstore should handle that.
You're saying I should try rooting w Odin again, install Superuser, then use TWRP to flash with? I'll be happy to read another 4 hrs of posts/stickies if that'll get me sorted out. I don't expect people like yourself to spend your day helping me. I'm very thankful for your tips here.
I've poured thru the "All things Gnote" threads and Noob Guides. They can be confusing as they always link out to many different threads. There is hardly ever a "Here are the steps 1. 2. 3. 4. 5.
Thanks again OG.
redman9 said:
Thanks OG. Yes, I know CMW and TWRP. I used to switch ROMs a lot. Finally stuck with Collective's latest (the orange one) pretty happy with it except that it's major glitch seems to be reboots whenever an app updates. So I figured unchecking auto update in Gstore should handle that.
You're saying I should try rooting w Odin again, install Superuser, then use TWRP to flash with? I'll be happy to read another 4 hrs of posts/stickies if that'll get me sorted out. I don't expect people like yourself to spend your day helping me. I'm very thankful for your tips here.
I've poured thru the "All things Gnote" threads and Noob Guides. They can be confusing as they always link out to many different threads. There is hardly ever a "Here are the steps 1. 2. 3. 4. 5.
Thanks again OG.
Click to expand...
Click to collapse
No problem always happy to help. since you're used to this sorta thing you don't need to use odin again and reroot. What you can do is either install TWRP through CWM using this file here:
http://goo.im/devs/OpenRecovery/sgh-i717/openrecovery-twrp-2.5.0.0-quincyatt.zip
Or you can install Goo manager, click settings and select Install OpenRecoveryScript (though that's only 2.4.4.0 the link above is 2.5.0.0)
That should change you over to TWRP. and like always do a nandroid backup and then flash to your heart's content!
fixed!
dweeezy said:
fixed!
Click to expand...
Click to collapse
How ?
galinha said:
How ?
Click to expand...
Click to collapse
i have the same issue.....i kn0w its n0t an hardware issue....my ph0ne is fairly new never dr0pped and this started happening 3 days after i p0rted black star jb alpha
I have this same issues ive tried flashing everything ive tried a new sim and replaced the card reader.
What works consistently for me if to flash the latest modem everytime i have to reboot or boot the note. Its my daughters phone now and she drains the battery regularly if it boots after charging or it needs to be rebooted for whatever reason it will come up with the no sim card error. If i flash the modem thru recovery it will work for that boot but only as long as I dont reboot or shut the phone off, then i will have to flash the modem again.
Not fixed
All. This is not fixed. I am having the same issue and if you follow the guide, it works for a day maybe regardless of what rom is loaded or what modems. Has anyone found a real solution to this yet??
i717 running stock GB or ICS or JB roms...
Thanks!
I have the exact same issue. Replaced the sim/sd card slot and still no dice ): Flashed to stock and back. Nope. Still won't work
Kraize said:
I have the exact same issue. Replaced the sim/sd card slot and still no dice ): Flashed to stock and back. Nope. Still won't work
Click to expand...
Click to collapse
I'm having the same problem. There seems to be no set way to get it back to working. Basically any reboot of the phone produces a no sim card error. I have tried flashing the modem through recovery as it was mentioned that will fix the problem. That did not work for me. What does work, sometimes, is one of the following:
1. Full wipe and reinstall
2. Restore backup from Recovery
3. Fix permissions
I just keep doing one of the above listed and eventually it works. However if the phone reboots then it's back to the carousel of trying these options to get it back to working.
I'm running Padawan JB V2
I honestly have no idea what's causing it. I haven't tried to fix permissions before to fix this issue, but if I go into recovery and install the modem again and reboot, it works fine for a while (and by a while, I mean like a few hours at max).
Just started having this issue, myself...after flashing Tmo_SGH-T989_VKL1_radio_ATTNOTE.zip modem on my phone...restoring from a prior backup...
Restoring a backup will not change your modem.
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
PS: One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor(currently using this setup on my phone). Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
Click to expand...
Click to collapse
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Hamza18 said:
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Click to expand...
Click to collapse
Yes, and not just once, but every time I flashed a new ROM. I'm thinking my only option now is to unroot and go back to stock but i am unable to find my country's rom. (found one on sammobile but the download speed refuses to go beyond 2-3kbps).
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
Click to expand...
Click to collapse
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Hamza18 said:
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Click to expand...
Click to collapse
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
pertsky makes
newoverhere said:
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
Click to expand...
Click to collapse
See, most of the things in your phone are software related. It is very very rare that you might have damaged the hardware. I see mismanagement of the resources by the ROM or kernel in your phone. What are the steps you are doing when installing a new ROM and which custom recovery are you using?
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
JJEgan said:
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
Click to expand...
Click to collapse
I did a full wipe, flashed everything again, did the emmc check as well as the dummy file generator thing....the hangups have reduced to 2-3 per day from 2-3 per hour but are still there. Should I downgrade my cwm recovery?
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
~DemonLord~ said:
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
Click to expand...
Click to collapse
Hi guys, I experience the same problems: I'm in any app and I press home to go back to the home menu => my phone's freezing for 5 seconds and then I see all my icons/folders/widgets slowly appearing. I would like to know how to complete format my internal SD card like you said. Thanks in advance.
by pressing the powerkey+homebutton+volume up for about 8-10 seconds you are taken to a recovery menu. You can choose to factory reset over there. That fixed problems in most cases. The only way to wipe the internal partition as well would be to install stock firmware which is a part of unrooting, this will erase everything and put a original rom in your phone.. You can follow the unrooting processes written in many posts in xda
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Radder124 said:
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Click to expand...
Click to collapse
As far as i know yes. Its not any trouble at all, wont take much time, except the firmware you would have to download. Its not needed in most cases. As i said before you may only need a factory reset so try that before! And just hit the thanks button
Hello, forum members!
I'm in dire straits right now.
I upgraded my Samsung Vibrant T959 from the original stock version 2.1 to the following:
CM-10.1.3-stable-for-vibrant and gapps-jb-20121212-signed
I like it pretty well, except for the issue described below:
I do not hear incoming calls as there is no ringtone being emitted.
When I go to settings' menu, where one picks the melody, I used to be able to click on it and then hear it right away before selecting: now nothing happens.
Moreover, when I navigate to /system/media/audio/ringtones, where the files seem to be sitting, I can play a ringtone file in a player other than Apollo, but when picking Apollo, it does not play correctly.
So what it going on there, any ideas? And how can I fix it?
Thank you.
ldashevskiy said:
Hello, forum members!
I'm in dire straits right now.
I upgraded my Samsung Vibrant T959 from the original stock version 2.1 to the following:
CM-10.1.3-stable-for-vibrant and gapps-jb-20121212-signed
I like it pretty well, except for the issue described below:
I do not hear incoming calls as there is no ringtone being emitted.
When I go to settings' menu, where one picks the melody, I used to be able to click on it and then hear it right away before selecting: now nothing happens.
Moreover, when I navigate to /system/media/audio/ringtones, where the files seem to be sitting, I can play a ringtone file in a player other than Apollo, but when picking Apollo, it does not play correctly.
So what it going on there, any ideas? And how can I fix it?
Thank you.
Click to expand...
Click to collapse
did you go straight from 2.1 to cm10? if you skipped cm7 that can cause some issues
RudeBwoy said:
did you go straight from 2.1 to cm10? if you skipped cm7 that can cause some issues
Click to expand...
Click to collapse
I sure did go pretty much straight from rooted stock 2.1 to CM10.1.3, except for the part, where I first loaded ClockworkMod Recovery from method B of rooting from here: http://forum.xda-developers.com/showthread.php?p=9375927#post9375927
I think, it was version 2 something. Then I went straight to flashing the ROM (did that replace the kernel as well?) and I think it had an even later version of CMR (6.0.3.6), which was installed before proceeding with the actual ROM flashing.
Any advice and/or links are highly appreciated!
Is "installing from zip" of CM10.1.3 once again safe? Will it wipe everything I already managed to install?
Should I try and install CM7 and then come back to CM10?
Thanks.
ldashevskiy said:
I sure did go pretty much straight from rooted stock 2.1 to CM10.1.3, except for the part, where I first loaded ClockworkMod Recovery from method B of rooting from here: http://forum.xda-developers.com/showthread.php?p=9375927#post9375927
I think, it was version 2 something. Then I went straight to flashing the ROM (did that replace the kernel as well?) and I think it had an even later version of CMR (6.0.3.6), which was installed before proceeding with the actual ROM flashing.
Any advice and/or links are highly appreciated!
Is "installing from zip" of CM10.1.3 once again safe? Will it wipe everything I already managed to install?
Should I try and install CM7 and then come back to CM10?
Thanks.
Click to expand...
Click to collapse
Going straight from 2.1 to cm10 causes issues. You should odin back to stock 2.1 and then you can flash cwm and then flash cm7 > cm10. Thats the recommended thing to do.
RudeBwoy said:
Going straight from 2.1 to cm10 causes issues. You should odin back to stock 2.1 and then you can flash cwm and then flash cm7 > cm10. Thats the recommended thing to do.
Click to expand...
Click to collapse
I see, well thanks, RudeBwoy, will do!
hello, im just recently flashing FTF files to my z ultra, and its works fine until i left my phone idle for a while, and when checking back all sound input / output is gone. Totally gone, cant receive a call, no sound all only vibrate, mic also disabled, i must restart then the sound will back.
I already try to flash another FTF and it also having the same problem. Is it bug from 5.1.1 ? what should i do ? im not to advanced in android. Thanks
what FTF files that I used : C6802_Customized+TH_14.6.A.0.368.ftf and C6802_14.6.A.0.368_1275-8963_Customized-MEA.ftf
both of them sharing the same problem, randomly no sound after idle ( screen of for a while )
Do you wipe before/after you've flashed it/them? Also, I would probably have flashed an older FTF just to check that it's a software issue and not a hardware one (not that any hardware issue would do these things), but just to be sure. If the same issue happens on a lower firmware, then it's a little harder to determine what the issue might be.
Also, try to flash an FTF from your region or one that's fairly close. I flashed a Saudi Arabian .368 FTF the first time, and I had major issues with battery and other smaller bugs, but when I flashed one from my region (Europe), it solved itself. I just think you're having some bad luck, and it sounds like some software issues. Don't forget to wipe the system before or after you've flashed it.
Im flashing using flashtool, i suppose i already wipe, and im trying to find the stock version, but it seem i cant find a proper one, im trying to find the unmodifed / original one. but it seem all dead link, when i found one, i flash and it stuck at bootloop. So i just go back to the 5.1.1, which have the bug like that.
Anyway, the C6802 tft is limited, can i use another C6833 ftf ?
Shigeur said:
Im flashing using flashtool, i suppose i already wipe, and im trying to find the stock version, but it seem i cant find a proper one, im trying to find the unmodifed / original one. but it seem all dead link, when i found one, i flash and it stuck at bootloop. So i just go back to the 5.1.1, which have the bug like that.
Anyway, the C6802 tft is limited, can i use another C6833 ftf ?
Click to expand...
Click to collapse
Do you have the C6833? Or the C6802?
Klaos3000 said:
Do you have the C6833? Or the C6802?
Click to expand...
Click to collapse
i have the C6802
Shigeur said:
i have the C6802
Click to expand...
Click to collapse
Okay, I'm going to make an Indonesian C6802 FTF for you, so just hang tight for a little while and I'll have it for you soon (20-30 min).
Here you go: https://drive.google.com/file/d/0B_VjBcIjyoZDX3BFQ0hpeHJHbHM/view?usp=sharing
thanks, ill try, i hope its working...
Hello, im upping this thread...
its still not working, the sound still have same bug...
it seem something weird around bootloader stuff, i find my phone is unlocked bootloader.
is anyone know that unlocking bootloader can make sony xperia z ultra no sound bug like this ?
anywork around ?
i already try installing custom rom, but all my custom rom i try is stuck at bootloop, or just wont stick ( it detected as no OS and just keep on SONY logo )
any recommendation of custom rom that i should try ?
and im really newbie here, all recovery that i install is gone after i flash custom rom, so its really hard to flash rom, root, install recovery and install custom rom which is a dead end ( bootloop )
*its really weird bug...
sometime sony camera app also wont open ( app crash ) + no sound
after rebooting 2-3x its fix both of them, after screen go to sleep
sound is gone, and the camera still works fine until i reboot or no battery ( repeat reboot and it fix the camera and sound ( temporary )
>> relock bootloader, and restore with official software ( pc companion ) still not fix this bug.
You use Google play "soundabout" app .workaround. will restore sound
rockky said:
You use Google play "soundabout" app .workaround. will restore sound
Click to expand...
Click to collapse
im trying, ill post later... for now my phone is muted, i only use it for reading news only
Shigeur said:
im trying, ill post later... for now my phone is muted, i only use it for reading news only
Click to expand...
Click to collapse
it still cant, it seem something wrong with audio engine / system files. when i press 'play' button on walkman it didnt changed.
all sound app didnt work and saying something wrong
as for camera, i cant use sony default camera, but i can use other camera app, such as google camera. but as the audio all 3rd party app not working either directly crash or just stay still play button can be pressed.
up again...
trying installing custom rom ( resurection remix ) now it success, with xz dual recovery
but still no sound comming out, camera is working fine.
anyone experience the same problem ? sony rom and stock make camera app crashed and no sound
custom rom, still no sound.
the same error, when i press play button on any audio player, it just back to paused and the time still in 00:00
it seem something wrong in the system, but i just fresh install
The bug sounds very strange (haven't experienced it on C6802/HK or C6833/DE) but will give you some recommendations for flashing:
1. Download the TWRP recovery from this thread and flash it:
http://forum.xda-developers.com/xperia-z-ultra/development/twrp-togari-t3197082
If you are on a stock based ROM, do step 1b. Otherwise flash a stock/based ROM first since it is necessary for extraction of those particular files.
1b. Before flashing anything, download Root Explorer or another file manager with root access and copy the files inside /Data/etc to the memory card. This is a way of avoiding the MAC address issue on some custom ROMs.
2. Download a ROM of choice. I would recommend BlissPop or Resurrection Remix but try the 20151007 build (the newer ones suffer from a WiFi issue).
2b. Check this thread for a fix for lost IMEI on C6802:
http://forum.xda-developers.com/xperia-z-ultra/general/guide-stock-to-custom-rom-t2901739
3. Boot into TWRP and wipe everything. Wipe system, data, cache, Dalvik cache and the internal storage.
4. Flash the ROM and the IMEI fix.
5. Wipe cache and Dalvik cache again.
6. Boot the ROM, let it settle for 5 minutes (after seeing the setup guide) and reboot, then do the setup.
7. Install a file explorer and copy the files from /Data/etc back into its place. You will notice that the folder is empty on a ROM such as BP so you will put the files back in place.
8. Reboot the device.
If the problem persists despite those steps, I would assume that something is corrupted and I would do a full wipe, flash a stock ROM and then repeat the steps again. I know that some root methods such as KingRoot can leave trash files which can interfere with ROM flashes and updates but doing a full wipe should clear those things out.
One option is a downgrade to a KitKat stock ROM such as 108 followed by rooting with Easy Root Tool and then making an update by flashing a new stock ROM with the /system partition excluded followed by reflashing of TWRP and flash of a custom ROM.
If nothing helps, then there is a possibility of some kind of hardware issue. I am supporting four Ultra's in total (one C6802 and three C6833s) and have never encountered such a problem. I have experienced BT dropouts on early LP ROMs and also phone FCs after kernel experimentation but everything has been cleared up by doing a clean flash with a full wipe.
A last long shot would be to try a different SIM card. Not that I suspect it but it has happened that some SIMs have been problematic thus causing strange behavior with the device. I don't think it is the SIM but it is just a way of excluding the possibility. Even far-stretched solutions can work when issues are very strange.
E90 Commie said:
The bug sounds very strange (haven't experienced it on C6802/HK or C6833/DE) but will give you some recommendations for flashing:
1. Download the TWRP recovery from this thread and flash it:
http://forum.xda-developers.com/xperia-z-ultra/development/twrp-togari-t3197082
If you are on a stock based ROM, do step 1b. Otherwise flash a stock/based ROM first since it is necessary for extraction of those particular files.
1b. Before flashing anything, download Root Explorer or another file manager with root access and copy the files inside /Data/etc to the memory card. This is a way of avoiding the MAC address issue on some custom ROMs.
2. Download a ROM of choice. I would recommend BlissPop or Resurrection Remix but try the 20151007 build (the newer ones suffer from a WiFi issue).
2b. Check this thread for a fix for lost IMEI on C6802:
http://forum.xda-developers.com/xperia-z-ultra/general/guide-stock-to-custom-rom-t2901739
3. Boot into TWRP and wipe everything. Wipe system, data, cache, Dalvik cache and the internal storage.
4. Flash the ROM and the IMEI fix.
5. Wipe cache and Dalvik cache again.
6. Boot the ROM, let it settle for 5 minutes (after seeing the setup guide) and reboot, then do the setup.
7. Install a file explorer and copy the files from /Data/etc back into its place. You will notice that the folder is empty on a ROM such as BP so you will put the files back in place.
8. Reboot the device.
If the problem persists despite those steps, I would assume that something is corrupted and I would do a full wipe, flash a stock ROM and then repeat the steps again. I know that some root methods such as KingRoot can leave trash files which can interfere with ROM flashes and updates but doing a full wipe should clear those things out.
One option is a downgrade to a KitKat stock ROM such as 108 followed by rooting with Easy Root Tool and then making an update by flashing a new stock ROM with the /system partition excluded followed by reflashing of TWRP and flash of a custom ROM.
If nothing helps, then there is a possibility of some kind of hardware issue. I am supporting four Ultra's in total (one C6802 and three C6833s) and have never encountered such a problem. I have experienced BT dropouts on early LP ROMs and also phone FCs after kernel experimentation but everything has been cleared up by doing a clean flash with a full wipe.
A last long shot would be to try a different SIM card. Not that I suspect it but it has happened that some SIMs have been problematic thus causing strange behavior with the device. I don't think it is the SIM but it is just a way of excluding the possibility. Even far-stretched solutions can work when issues are very strange.
Click to expand...
Click to collapse
ill try, and will post the update, but maybe next month, i hope this work.
a bit busy this month preparing other stuff... thanks for helping
Shigeur said:
hello, im just recently flashing FTF files to my z ultra, and its works fine until i left my phone idle for a while, and when checking back all sound input / output is gone. Totally gone, cant receive a call, no sound all only vibrate, mic also disabled, i must restart then the sound will back.
I already try to flash another FTF and it also having the same problem. Is it bug from 5.1.1 ? what should i do ? im not to advanced in android. Thanks
what FTF files that I used : C6802_Customized+TH_14.6.A.0.368.ftf and C6802_14.6.A.0.368_1275-8963_Customized-MEA.ftf
both of them sharing the same problem, randomly no sound after idle ( screen of for a while )
Click to expand...
Click to collapse
Have you tried to flash the correct ftf? I don't have time to read through the thread.
Have you tried Sony repair tool?
What I would suggest is trying a different mixer path
Root directory>system>etc>mixer_paths.XML make a copy somewhere, delete the file and insert a new one.
I've owned a white 02 model and had similar issues I just ended selling it and getting a 06 model.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
Shigeur said:
up again...
trying installing custom rom ( resurection remix ) now it success, with xz dual recovery
but still no sound comming out, camera is working fine.
anyone experience the same problem ? sony rom and stock make camera app crashed and no sound
custom rom, still no sound.
the same error, when i press play button on any audio player, it just back to paused and the time still in 00:00
it seem something wrong in the system, but i just fresh install
Click to expand...
Click to collapse
Ahh yes read your last part.
Try to switch out mixer path
My 02 had same issue but I was to impatient to bother.
RealityFails said:
Have you tried to flash the correct ftf? I don't have time to read through the thread.
Have you tried Sony repair tool?
What I would suggest is trying a different mixer path
Root directory>system>etc>mixer_paths.XML make a copy somewhere, delete the file and insert a new one.
I've owned a white 02 model and had similar issues I just ended selling it and getting a 06 model.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
Ahh yes read your last part.
Try to switch out mixer path
My 02 had same issue but I was to impatient to bother.
Click to expand...
Click to collapse
how to create a new mixer path ? just delete the old one ?
Shigeur said:
how to create a new mixer path ? just delete the old one ?
Click to expand...
Click to collapse
Make a back up, then delete it.
Once deleted add this one to the same location device>etc>mixer_path.XML
RealityFails said:
Make a back up, then delete it.
Once deleted add this one to the same location device>etc>mixer_path.XML
Click to expand...
Click to collapse
or it seem a hardware issue... just realised after doing a lot of fix..
if it shaked or pressed in some kind area of the screen the sound will gone for a while...
it seem the component are a bit loose inside.
you can see in video below
https://www.youtube.com/watch?v=kO8zN-v9b_w&feature=youtu.be
if someone can confirm this hardware issue, this thread can be closed, thanks a lot for those who help me
Merry Christmas !