Related
I am posting a new thread because I'm experiencing the issue with several diffrent ROMs so obviously it's a general issue not a ROM specific one. Also I have read through countless pages of posts with no luck so hopefully someone can shed some light. Over the past few days I've flashed (forgive my spelling) dude's .5, ravenge, cynogen 3.4 and I have been having issues with the phone not waking after either I put to standby myself or the screen times out. I know it's not an issue with my phone or card because I go back to virtudude's ROM without the issue. I have tried everything, formatting my partition, ext2, ext3, wipe, no wipe, everything I can think of and still have the issue accross mutiple ROMs. I know it's not just me because my friend with a G1 is having the same issue, as well as many people posting in the threads. Can someone please point me in the right direction to fix this issue please?
My phone:
G1 with JF 1.42
Newest SPL 2005
Newest 26I radio
8gb SD card, class6, ext2 or ext3 partition (same issue on either)
Thanks in advance for any help!
me too
I noticed this same problem, its related to wifi, when I disable wifi my phone wakes up, also I have searched everywhere too for a solution. I think the compiled wifi deiver in these roms are not compiled right. So its either this or some other problem.
Is your phone connected to wifi with wpa2 personal? One other thing I noticed is this happens at random, when it does happen adb and ddms say device is offline when the led is blinking, also bottom of phone gets hot.
Can any devs shed some light on what exactly happens when the phone shuts off? Because something is locking the phone up when the light goes off and is in standby.
I am doing a test, im leaving wifi on while the screen is off in settings, will report back
This happens to me also but its only with hero I also have the new radio and spl. I can run hero with no problems as long as I don't use apps to sd or lucids txt. The wired thing is that after I use any apps to sd it works great but only for a day sometimes a few hours. Then I will start to see freezing up or it won't wake up at all, unless I reboot or pull battery. I've tried to reformat my card, resize my partition I'm also lost on this one fresh out of ideas.
Do you guys think it might have somthing to do with the sdcards? Im useing a 4g class 6 transcend micro SD, its only about 2 weeks old. Jason what other roms gave you these problems?
defconoi said:
Is your phone connected to wifi with wpa2 personal? One other thing I noticed is this happens at random, when it does happen adb and ddms say device is offline when the led is blinking, also bottom of phone gets hot.
Can any devs shed some light on what exactly happens when the phone shuts off? Because something is locking the phone up when the light goes off and is in standby.
Click to expand...
Click to collapse
I personnally don't see the correlation between locking and WiFi, I was at work the other day and flashed a ROM and it was doing it. I have my WiFi off at work so that wouldn't have been the case that day. I do notice the bottom of the phone getting hot though.
In response to the other person with the sd card question I really don't think it's that as I have a class 6, have formatted every way possible. Unless the issue has to do with apps2sd, I use apps2sd on every ROM.
Glad to see I'm not the only crazy one on xda!
joe v said:
Jason what other roms gave you these problems?
Click to expand...
Click to collapse
Almost every ROM to come out in the last couple weeks has done it. TheDude's .5, Ravenge's ramjet, Cyanogen's 3.4.1, and the Cyanogenized Rogers ROM.
You know looking at these the one thing these all have in common is being Cyanogenized. And the only ROM to come out in the past few weeks that hasn't had that issue is Virtuedude's Rogers ROM, which isn't Cyanogenized.
If any devs are reading this thread if you can make a version of your most recent ROM without Cyan's build kernel and boot and see if that helps. I'd be happy to test it for you to try and get to the bottom of this. If you wanna shoot me an email hit up jasonsyn at gmail.
I've had the same problem, but for me it started after flashing Cyanogen's 3.4 release. Since then I've reverted back to his 3.3.3 release and everything is fine again. Perhaps it has something to do with the new SPL and these ROM's?
That seems to be the one constant among all of us with problems, we've all flashed the new SPL and radio.
EDIT: I asked cyanogen about it, we'll see what he says.
indiekid97 said:
I've had the same problem, but for me it started after flashing Cyanogen's 3.4 release. Since then I've reverted back to his 3.3.3 release and everything is fine again. Perhaps it has something to do with the new SPL and these ROM's?
That seems to be the one constant among all of us with problems, we've all flashed the new SPL and radio.
EDIT: I asked cyanogen about it, we'll see what he says.
Click to expand...
Click to collapse
Yeah but I've had the new SPL and Radio for a month and this just started a week or so ago...
I am having the exact same issue. I usually have wifi bluetooth and 3g disabled (saves battery) I noticed this started after grabbing the new spl, ever since it's been freezing in standby randomly. I'm going to try Virtudude's rogers rom to see if the combination of Cyanogen's boot image and the new spl is causing the freezing. Hopefully seeing as Virtududes rom isn't based on Cyanogen's boot image it won't freeze. I'll report back with my results.
I thought my button got worn out. I never had the symptoms on rc33. When I switched to cupcake back during hatkuros prime just before dudes first releases I noticed it. I thought if it wasn't my button it might be somehow related to jf kitchen since almost all my roms touch it at some point. Just speculation though, donno what causes it.
Hey what recovery image are you all running?
I'm gonna flash the new Cyanogens 1.2 Recovery image and see if that's the issue.
Ok so how gay is this? I just hung up from a phone call and the phone is stuck sleeping! I was using it and it won't wake up, this is so incredibly frustrating!!
I have the new recovery image, 3.4.1, and still issues.
Jason Syn said:
Ok so how gay is this? I just hung up from a phone call and the phone is stuck sleeping! I was using it and it won't wake up, this is so incredibly frustrating!!
I have the new recovery image, 3.4.1, and still issues.
Click to expand...
Click to collapse
try holding down menu or the power button...i had this issue and my sd card would "unmount unexpectedly" and then this ended up into my sd bein fried
for those who are having this issue, try saving a log of it from ddms after that adb shell reboot thats what ive been doing ... instead of removing the battery, though my issues seem to happen every 24 hours i was on cy's 1.1 just flashed 1.2 perhaps that was is the issue?.. either way... we should try to collect all the info we can while this is happening to us.
dbhatesyou said:
for those who are having this issue, try saving a log of it from ddms after that adb shell reboot thats what ive been doing ... instead of removing the battery, though my issues seem to happen every 24 hours i was on cy's 1.1 just flashed 1.2 perhaps that was is the issue?.. either way... we should try to collect all the info we can while this is happening to us.
Click to expand...
Click to collapse
Ok I'll be happy to but I'm a linux virgin...would you mind giving me step by step in adb and I'll give whoever the log that can make sense of it.
This happens to me also on The Dudes Roger built. I don't have WiFi enabled so it isn't that it seems pretty random and just I get no response from the phone and have to so the soft reset (Call Menu Power) and then it'll work again. Normally only happens like once a day though so I can live with it but it is a inconvenience and can be annoying if it does it when you actually need to use your phone for something with some importance.
well if you're on linux and have it to where adb runs from terminal , just type
Code:
adb shell reboot
but before all that ddms (dalvik monitor) just type ddms in terminal it will boot up and show everything your phones basically working with.. and issues,
now if your linux terminal doesnt work well with adb (cant get it to work , google "50-android.rules" and "51-android.rules" n see if those help, and also set your echo path right )
now if you're on windows just hit windows key + r type cmd , and set yourself into the sdk/tools directory, then type ddms that will start the dalvik monitor (try and save a log) make sure the log saves before rebooting the phone, when you're done you can just ctrl+c and type adb shell reboot, and your phone should reboot.
[just the basic]
i've ran into this intermittently...most of the time while using the browser or using the onscreen keypad during a phone call.
I'm on JF CRB43(which is 1.51 i think) with the Hard SPL and JF Recovery.
Only thing I've been able to do to get the phone to wake up is wait. eventually it'll come around. or pull the battery, which i try not to do.
http://forum.xda-developers.com/showthread.php?t=743506
I was wondering if anybody was willing to try this on their captivate and see if it worked for us or any dev's willing to try and port this over to our side.
seems to be working fairly well for them
edit: their hitting 1400+ Quadrant scores and all functions work on their phone from what I see
UPDATE 3:
Tutorial:
-1. Download VibrantDeodexed.zip from thread posted.
1a. Flash stock Odin3 rom. (For the Captivate).
1b. Root
2. Download ROM Manager from Market.
3. FlashClockworkRecovery for Captivate in ROM Manager.
4. Transfer the VibrantDeodexed.zip to /sdcard/ root.
MAKE SURE YOUR ext3 PARTITIONED SDCARD IS INSERTED
5. Reboot to Recovery (in ROM Manager)
6. Install zip from sdcard>choose zip>VibrantDeodexed.zip
7. After it finishes, reboot and be patient. The initial startup takes some time...
Added Fortune090 instructions on how to get this on our captivates. KUDOS to him for testing it out for us
Please note this is still very EARLY and major problems could happen if you do this wrong.
We're not responsible. This is beta
UPDATE 4: I updated the tutorial to a more extensive one, but there is another thread
http://forum.xda-developers.com/showthread.php?t=747397
that is more promising, no gps problem. Waiting for an update version for easier install
The Captivate and Vibrant function completely differently as far as those speed fixes go.
Read this:
http://forum.xda-developers.com/showthread.php?t=740747
I was hitting around 1800 in Quadrant, but the fix wasn't showing any real-world speed increases, and had some bad issues regarding the mic and voice calls, along with wake up lag.
I'm not saying this won't work, but I'm assuming it won't work well or function the same way...
EDIT: Guess I can try it though, seeing as no one else has. Glad my phone's finally communicating with Odin properly so I don't have to worry about the brick I did before... I'll update with any issues.
UPDATE1: Rebooted into recovery and tried to reinstall packages to install the update, and it failed. Trying another one of the methods described to see if they'll work.
UPDATE2: Got it installed (I think), but it seemed to go way too fast and kept going between recovery and rommanager. Phone's loaded and it's running Quadrant now to see if there's any change.... Didn't think so. Still getting in the 900's. Time to continue trying... haha. I originally used Clockwork for Captivate, so that could have been the problem trying Vibrant to see if that'll make a difference...
thanks for the try, I guess we'll just have to wait until something more substantial gets worked up for our side
nammyczc said:
thanks for the try, I guess we'll just have to wait until something more substantial gets worked up for our side
Click to expand...
Click to collapse
I'm guessing that you'd have to flash the Vibrant ROM first, and I've known that's caused issues for Captivate users. I'm still trying with the Captivate stock Odin ROM though... Will definitely post if I have any success...
EDIT: I actually think I found my mistake... hold on...
EDIT2: Yes... definitely was a dumb mistake. It's copying the files now. Waiting for it to boot. Was told it takes awhile for the initial boot...
UPDATE: Ok, everything booted up fine, and I can tell this is the Vibrant ROM. The speed fix wasn't applied though. Might be because my external is partitioned with ext4. Could that be the problem? I didn't see any script load that didn't before...
UPDATE2: Reformatted my external to ext3 and got results!!! Quadrant got to 1446! Time to check some real world applications now. (phone call, bluetooth, I know wi-fi works, etc) I'll update with news.
Keep us updated. I don't know if the ROM includes the radio firmware, so make sure to have the stock captivate radio.
I'd love to see a speedtest.net to see if HSUPA works correctly!
Ok wow. I'm impressed. I'm seeing actual speed increases and so far everything is working perfect. No wake up lag, no static in phone calls, Quadrant scores are way up, plus you get some of the advantages of the Vibrant rom without having to flash it. (ie. OPTION to allow non-market apps, unlocked Market...)
So far it's a thumbs up all the way!
Tutorial:
1. Flash stock Odin rom (For the Captivate).
2. Download ROM Manager from Market.
3. Install the Captivate Clockwork for Captivate
4. Transfer the VibrantUpdate.zip to /sdcard/ root.
MAKE SURE YOUR ext3 PARTITIONED CARD IS INSERTED
5. Reboot to Recovery (in RM)
6. Install zip from sdcard>choose zip>VibrantUpdate.zip
7. After it finishes, reboot and be patient. The initial startup takes some time...
8. ENJOY!
Currently working on getting rid of the T-Mobile startups and shutdowns, but that takes no time at all. Thanks for this!!!
EDIT: Problem. GPS no longer functions at all from what I'm seeing. When using my location in Maps, the application freezes... Going to check the *#*#1472365#*#* settings to see if anything there's causing the problem...
madjsp said:
I'd love to see a speedtest.net to see if HSUPA works correctly!
Click to expand...
Click to collapse
Did a speed test...
1898 dl
341 ul
Is that HSUPA ratings or standard? I'm not sure...
Sorry for the triple post, but another thing I noticed... Titanium Backup is not recognizing all of the T-Mo bloatware or ANY of the installed applications... Anyone have any idea why?
Also, Swype FC's after about 3 seconds, but I'm assuming a reinstall will solve the problem... Haven't checked quite yet. Still testing a bunch of things.
EDIT: TB problem solved. Go to Problems? from the main menu, Yes do it. Everything showed up after it updated BusyBox.
Still trying to figure out the GPS problem...
Fortune090 said:
Sorry for the triple post, but another thing I noticed... Titanium Backup is not recognizing all of the T-Mo bloatware or ANY of the installed applications... Anyone have any idea why?
Also, Swype FC's after about 3 seconds, but I'm assuming a reinstall will solve the problem... Haven't checked quite yet. Still testing a bunch of things.
Click to expand...
Click to collapse
I believe you have to click on "problems?" in T.B , its the middle button on the main screen i believe it say problems or in the menu
mykenyc said:
I believe you have to click on "problems?" in T.B , its the middle button on the main screen i believe it say problems or in the menu
Click to expand...
Click to collapse
Yeah, got it.
GPS, GPS, GPS...
Changed the settings in the 1472365 menu, and nothing worked. Anything that involves GPS crashes the second you tell it to use it. Phone doesn't freeze though.
QUICK: Can someone post the STOCK shutdown files? Sound: /system/media/audio/ui/shutdown.ogg Video (folder of .pngs): /system/media/shutdown
Would be greatly appreciated. Want to get rid of the T-mo branding the update applied...
WOW, I'm amazed that it works, thats great to here there have been little problems except GPS function. It could be the drivers for vibrant are different for captivate? I'm not really sure I dont know much software but that seems like the most basic explanation I can think of.
EDIT: Did you try deleting the GPS data and starting over from scratch? or gps test from the market? its possible that GPS just needs to reset itself? or something...
nammyczc said:
WOW, I'm amazed that it works, thats great to here there have been little problems except GPS function. It could be the drivers for vibrant are different for captivate? I'm not really sure I dont know much software but that seems like the most basic explanation I can think of.
EDIT: Did you try deleting the GPS data and starting over from scratch? or gps test from the market? its possible that GPS just needs to reset itself? or something...
Click to expand...
Click to collapse
Hmmm... ill try that. Thanks! I'll update with what happens.
UPDATE: Nothing... froze again and GPS Test crashes at startup...
Sent from my Captivate
Thanks for your work, looking forward to what comes from this
sidenote I would upload the sound for you but not sure where its located through astrofile...
EDIT2: http://www.mediafire.com/?tcyzaykkkfphxtg that rar is shutdown picture file and sound
Hm, could be possible we need to get the gps stuff from the captivate kernal and not the vibrants?
EDIT: so I emailed the OP from the vibrant one, for the original mod, seeing if he can help us out with ext4 problem and the GPS problem as well. Hope we can get this fully up and running
nammyczc said:
Hm, could be possible we need to get the gps stuff from the captivate kernal and not the vibrants?
EDIT: so I emailed the OP from the vibrant one, for the original mod, seeing if he can help us out with ext4 problem and the GPS problem as well. Hope we can get this fully up and running
Click to expand...
Click to collapse
Alright sweet. Hopefully we see this completely take off. Not using the GPS at all, I'm seriously enjoying it, but I know it's a problem for everyone else.
Sent from my Captivate.
question for reverting back to stock is the same method in the forums? or will it be different
Can you use ROM manager's backups to undo the ROM flash? I want to make sure that I can go back to my stock AT&T ROM after I test out this vibrant ROM.
thats pretty sweet.
just gotta get the gps up and going now.
I'm not sure... When I flash I use Odin.
Another minor bug I've noticed is that with texts, the notification doesn't go away until you clear all notifications. Not TOO big a deal, but it didn't happen with my stock firmware. Might be a Vibrant thing... idk...
So here is the problem - my sgs 4g (currently running valhalla black, earlier same problem with stock 2.3.6) turns off when someone is calling. It's not happening every time i get incoming call, just sometimes. It turns off without any sign of doing it(no vibration, no sound, not even the animation so i don't know that its happening, when the phone is in my pocket), and the caller gets voice mail.
I think the problem started after updating to 2.3.6, but it also can be caused by falling on the floor(happened few times).
What do you think? Anyone had similiar problems?
I live in Poland, so i can't get it fixed in samsung care point because they don't support SGS 4G.
sry for my spelling mistakes, i'm doing my best, but that's not my first language.
I'd say the best you can try is Gremlin Remover to see if it solves your problem.
http://forum.xda-developers.com/showpost.php?p=22596598&postcount=1
try tmo warranty after returning to stock gb
Gremlin Remover doesn't help. I flashed it only once.
I'm a bit afraid of sending it to USA Tmobile store from here, i think i'll look for some samsung magician in my country unless you have other ideas.
thanks for help and waiting for more solutions
#edit: is there any diagnostic software to check my phone hardware? Maybe something to save log of crash if its software failure?
When you say you flashed it once - do you mean Gremlin Remover or Valhalla Black?
And I wonder if it could be a modem issue for you since it started on KJ6. You might try flashing a different modem as a troubleshooting option.
http://forum.xda-developers.com/showpost.php?p=16127939&postcount=1
i had that issue on one of my sgs4g's a while back. wipe your sd card on your computer, odin back to kj6 stock. once you odin back to stock, make sure you perform a factory reset with the sd card removed. reboot and let it sit for a few min. do not sign into google or anything. have someone call you and see if the problem persists. let the phone function that way for an hour or so. then sign into google, but do not dl any apps. put back in your empty sd card and then reboot the phone. after a day, if you do not have the issue, you should be good to go. if you have the issue after a day, post back and pm me if i do not respond (i probably won't; i'm swamped at work and I am rarely on)
Ive had the same thing happen on valhalla black and I found that on my phone it was actually a skin that I had been using with adw ex. I changed my skin and cleared all my cache and dalvik cache and did not have a single problem after that. There are so many different things it could be. just experiment with it.
@lumin30: I meant stock 2.3.6 ->valhalla black (remover was the second)
That's something. I'll try everything you guys posted above and let you know the results in a few days.
Thanks for everything, appreciate your help.
#edit: LogsProvider service keeps crashing after blackout on valhalla black and i have to reinstall it. After flashing, the phone works for about 24h and then turns off. When I turn it on, logsprovider stops unexpectedly every 15 sec and i have to flash it again.
Now I am not sure if it's connected to incoming calls
After weeks of flashing and testing there is only one thing I am sure - nothing helped.. I tried many ROMs, different kernels and modems.
Now I can't see any relation to the software. Only thing on my mind is the battery, usually when my sgs turned off, the battery lvl was below 70%, so I ordered new one. I'll let you know if this changed anything.
Hello,
First off, I know its a super buggy build, but some of the problem I've encountered aren't even reported so I feel like I'm the only one having them. As well, I would have posted on the actual topic, but I don't yet have 10 posts yet, so it won't let me.
Anyway, first problem.
I can't use/ setup voicemail! I don't really care about visual voicemail, but I literally can't even access my own voicemail. Dialing my own number just gives me a busy tone, what gives?
Secondly, on that matter, every time I make a phone call from my phone, the screen goes black the second the phone screen pops up. I thought it was like a proximity sensor or something, but even with the phone on a table, I can't get it to come out of the "black mode" while on a call. If I press the power button, the screen will flash on briefly, but not long enough to do anything with it. As such I can't hang out phone calls, so I have to force reboot after every phone call.
And finally, on the matter of the phone, there are times where people call me, I'll answer (get the same black thing) but I can't hear them at all, and they can't hear me at all, but we are connected, and since I can't hang up, and on a black screen, I am helpless.
Another problem... I connected my phone to my comp today to try and grab a new ROM, thought I'd mount the SD card, but when I plugged it in, there was literally no option to mount anything. I went through all my settings, developer stuff, nothing fixed it.
As well, since I couldn't connect to my computer, I couldn't run "adb logcat" to maybe see what was going on with the phone and such. So I used a mobile terminal app I use occasionally to run "adb logcat" locally on the device. Well when I first run "adb devices" my own phone doesn't even pop up... Yes, developer debugging is enabled, and yes, the mobile terminal app had complete root access. How do you explain this? A friend of mine suggested reinstalling the rom wiping the dalvic cache, which I did, but all the problems I've been having still persist.
It makes it extremely difficult to use my phone day to day with these issues, and since I can't do a logcat, I can't really report the problems accurately, even though I seem to be the only one having them. Don't get me wrong, I love MIUI and all the work the MIUI.us team does porting, but I just don't think I should be having so many problems.
Thanks for the help guys.
Did you do a full wipe before flashing miui? I haven't updated to v4 but voicemail/phone calls work fine for me on v3...maybe you should try flashing that instead? Can't help you with the adb stuff, sorry. I did have trouble getting my phone connect to my windows 7 laptop though but adb worked fine on vista
joorie said:
Did you do a full wipe before flashing miui? I haven't updated to v4 but voicemail/phone calls work fine for me on v3...maybe you should try flashing that instead? Can't help you with the adb stuff, sorry. I did have trouble getting my phone connect to my windows 7 laptop though but adb worked fine on vista
Click to expand...
Click to collapse
Yep, I did a full wipe many times actually. Could it be that I used a backup from an order version of MIUI (2.4.x) inside that backup/restore program and it's corrupting something? At least in regards to phonecalls and voicemail...
ItWasLuck3 said:
Yep, I did a full wipe many times actually. Could it be that I used a backup from an order version of MIUI (2.4.x) inside that backup/restore program and it's corrupting something? At least in regards to phonecalls and voicemail...
Click to expand...
Click to collapse
Try testing voicemail and calls before restoring?? I restored data from some games using MyBackUp Root or something and my phone has been working fine >_< If all else fails, I can upload the 2.8.24_v3 rom for you! I think blind is gonna have a new build up today though so up to you. Sorry I haven't been much help :\
joorie said:
Try testing voicemail and calls before restoring?? I restored data from some games using MyBackUp Root or something and my phone has been working fine >_< If all else fails, I can upload the 2.8.24_v3 rom for you! I think blind is gonna have a new build up today though so up to you. Sorry I haven't been much help :\
Click to expand...
Click to collapse
I'll give it a try next time I flash. I do appreciate the offer for the v3 rom, but maybe I'll just wait for blind to get the new one up and hope I have better luck. I did a little more research on the adb thing on JB roms, and apparently there's some other driver needed or whatnot, so I'd assume that the terminal app I'm using on my actual HOX doesn't have said driver. However, that doesn't explain why I couldn't mount my SD on my computer. Like I said, maybe this next update will solve everything lol.
Hi, everyone. First I want to thank everyone who takes their time to come and help people like me who mess with things we don't know anything about - such as rooting phones, etc
I installed JellyBam 4.0.0 on my (US T-Mobile) HTC One S S4 earlier this evening. Everything so far seems to be working fine except there is no external audio - no ringtone sound, no radio or music file sound, no notification sound, etc. However, the headphones work fine. I'm not great with tech things, but I'm not a complete idiot, either. I've searched for similar issues and can't find one posted, don't see any settings that may be causing the issue... I'm at a loss.
JellyBam was installed on TWRP recovery and the boot.img was flashed immediately after installation via fastboot. I'm trying to think of what other information from me would prove helpful, but I can't come up with anything else.
So, can anyone offer any ideas as to what the problem (and solution!) may be? I will add that immediately prior to beginning the flash of the ROM and boot.img, I updated the HTC drivers through HTC Sync/Windows 7.
Thanks for any insight or ideas.
david251 said:
Hi, everyone. First I want to thank everyone who takes their time to come and help people like me who mess with things we don't know anything about - such as rooting phones, etc
I installed JellyBam 4.0.0 on my (US T-Mobile) HTC One S S4 earlier this evening. Everything so far seems to be working fine except there is no external audio - no ringtone sound, no radio or music file sound, no notification sound, etc. However, the headphones work fine. I'm not great with tech things, but I'm not a complete idiot, either. I've searched for similar issues and can't find one posted, don't see any settings that may be causing the issue... I'm at a loss.
JellyBam was installed on TWRP recovery and the boot.img was flashed immediately after installation via fastboot. I'm trying to think of what other information from me would prove helpful, but I can't come up with anything else.
So, can anyone offer any ideas as to what the problem (and solution!) may be? I will add that immediately prior to beginning the flash of the ROM and boot.img, I updated the HTC drivers through HTC Sync/Windows 7.
Thanks for any insight or ideas.
Click to expand...
Click to collapse
Change the ring volume and it should kick in.
Darknites said:
Change the ring volume and it should kick in.
Click to expand...
Click to collapse
Thank you. I just tried that and there's no change. Also went into the sound menu, turned everything down (volume settings) then opened it again and turned everything back up. No change.
I suppose I could walk around everywhere with me headphones on I love this ROM.
david251 said:
Thank you. I just tried that and there's no change. Also went into the sound menu, turned everything down (volume settings) then opened it again and turned everything back up. No change.
I suppose I could walk around everywhere with me headphones on I love this ROM.
Click to expand...
Click to collapse
Are you doing this with the headphones still plugged in?
No, I didn't. But after your question I did - still no change
david251 said:
No, I didn't. But after your question I did - still no change
Click to expand...
Click to collapse
Hmm not sure then other then doing a wipe and try the volume when it first boots.
Ok. Thanks for the time. I'll try that.
Sent from my HTC One S using Tapatalk 2
Darknites said:
Hmm not sure then other then doing a wipe and try the volume when it first boots.
Click to expand...
Click to collapse
Do you think he might have to do what I did for the sd card, maybe that will kick in what he is missing plus doing the full wipe and re-flashing the ROM just wondering?
TheCrow1372 said:
Do you think he might have to do what I did for the sd card, maybe that will kick in what he is missing plus doing the full wipe and re-flashing the ROM just wondering?
Click to expand...
Click to collapse
No its an old bug that's been there for as long I can remember lol but changing the volume should fix it.
Darknites said:
No its an old bug that's been there for as long I can remember lol but changing the volume should fix it.
Click to expand...
Click to collapse
Just to make sure I understand (because I am technology-challenged), when you say changing the volume - I assume you're talking about either using the volume rocker on the side of the phone or simply going into Settings > Sound and changing the volume sliders there.
Correct?
david251 said:
Just to make sure I understand (because I am technology-challenged), when you say changing the volume - I assume you're talking about either using the volume rocker on the side of the phone or simply going into Settings > Sound and changing the volume sliders there.
Correct?
Click to expand...
Click to collapse
Ya I mean the first but both ways should work but do it without the headphones.
---------- Post added at 04:13 PM ---------- Previous post was at 04:11 PM ----------
Oh just popped in the head but try having music playing and do it.
I did. Tried it when searching ring tones, then tried it with Google Music playing a track, tried it with local radio playing and tried it with nothing at all playing.
So let me ask you this - can I make a backup (Titanium Backup) of all my current settings so that when I wipe/reinstall, I don't have to redownload all my apps and redo everything?
Lol - I gotta say, though, as irritating as it is to have only this one issue... I love this ROM and the way my phone works with it. It's worth the hassle if I can get it fixed. (Especially considering I almost bricked it yesterday before finally finding this ROM.)
I should really not mess with stuff I know nothing about. But I just can't help it.
david251 said:
I did. Tried it when searching ring tones, then tried it with Google Music playing a track, tried it with local radio playing and tried it with nothing at all playing.
So let me ask you this - can I make a backup (Titanium Backup) of all my current settings so that when I wipe/reinstall, I don't have to redownload all my apps and redo everything?
Lol - I gotta say, though, as irritating as it is to have only this one issue... I love this ROM and the way my phone works with it. It's worth the hassle if I can get it fixed. (Especially considering I almost bricked it yesterday before finally finding this ROM.)
I should really not mess with stuff I know nothing about. But I just can't help it.
Click to expand...
Click to collapse
Load TWRP and do a backup there, then still in TWRP do factory reset and reboot and skip over the signing in stuff and then try playing with volume without plugging in the headphones and if this still don't work you could try in TWRP factory reset and then system and them reflash the rom and if this still some how don't work you can restore the backup in TWRP.
Ok, I'll do that now - but first, one more stupid question. After this, I'll leave you alone.
When I first installed this ROM, I went through Fastboot to flash the boot.img. Do I have to do that again if reflashing the ROM, or can I skip that step?
Thanks for all your guidance. Seriously.
Update on thread
So I followed the instructions above.
Went into TWRP, did a factory reset and rebooted. Played with volume. Still no external audio.
Went back into TWRP, factory reset, wiped system, reflashed ROM (did NOT manually reflash boot.img in Fastboot) then rebooted. Played with volume. Still no external audio.
Went back into TWRP and restored the backup - so I'm still left with a killer phone with no external audio, ringtone, etc.
Hmmm.... hope nobody calls when I can't hear/feel the vibrate or have my headphones in
That's strange though - I find no other threads mentioning a glitch like this and, except for this one issue, the phone/ROM works flawlessly. It even fixed the wifi connection problem that always existed with the stock phone/ROM and I know a lot of people with this phone have had that problem. With the stock, the wifi always had a problem (from the first day) connecting to my home wifi. Sometimes it would connect but normally it would take a long time (an hour or more) before finally connecting and still other times it wouldn't connect at all. Now if I leave the house, it connects as soon as I pull up in the driveway and if I power down/reboot, it connects instantly upon reloading.
Just before installing the ROM (the first time) I connected with HTC Sync via my pc/usb and made sure drivers were up to date, which is why I'm thinking it's not a driver issue. Would you agree?
david251 said:
So I followed the instructions above.
Went into TWRP, did a factory reset and rebooted. Played with volume. Still no external audio.
Went back into TWRP, factory reset, wiped system, reflashed ROM (did NOT manually reflash boot.img in Fastboot) then rebooted. Played with volume. Still no external audio.
Went back into TWRP and restored the backup - so I'm still left with a killer phone with no external audio, ringtone, etc.
Hmmm.... hope nobody calls when I can't hear/feel the vibrate or have my headphones in
That's strange though - I find no other threads mentioning a glitch like this and, except for this one issue, the phone/ROM works flawlessly. It even fixed the wifi connection problem that always existed with the stock phone/ROM and I know a lot of people with this phone have had that problem. With the stock, the wifi always had a problem (from the first day) connecting to my home wifi. Sometimes it would connect but normally it would take a long time (an hour or more) before finally connecting and still other times it wouldn't connect at all. Now if I leave the house, it connects as soon as I pull up in the driveway and if I power down/reboot, it connects instantly upon reloading.
Just before installing the ROM (the first time) I connected with HTC Sync via my pc/usb and made sure drivers were up to date, which is why I'm thinking it's not a driver issue. Would you agree?
Click to expand...
Click to collapse
Ya not sure what's up if you still got your backup you could try another rom like CM10 to see if its the same. The wifi confused me, everybody else find AOSP not as good at wifi, for me Sense let me set the router how ever I want but on AOSP I have to have it at default settings.
Final update on this thread
Earlier, I wiped everything (through hboot) and reflashed JellyBam. Once rebooted, not only did I still not have audio, but the wifi connection went back to normal - it would connect, but not without difficulty/delays. Strange,
Since I can't feasibly go without a ringtone/alarm/notifications (I use my phone for my business) I rewiped everything from TWRP and installed Dark Jelly v23 to include the Fusion Ultimate kernel. On first boot, still no sound but the notes here mention that may be an issue until it's rebooted a second time. So I set everything up, played around with the same ideas we were using earlier in this thread (to no avail) and then rebooted.
Wifi is the same as it always has been (with the exception of the glorious several hours when it worked like a champ on JellyBam). That's no big deal - I'm used to it and know it's an HTC One S quirk.
But....
Sound is back :good:
david251 said:
Earlier, I wiped everything (through hboot) and reflashed JellyBam. Once rebooted, not only did I still not have audio, but the wifi connection went back to normal - it would connect, but not without difficulty/delays. Strange,
Since I can't feasibly go without a ringtone/alarm/notifications (I use my phone for my business) I rewiped everything from TWRP and installed Dark Jelly v23 to include the Fusion Ultimate kernel. On first boot, still no sound but the notes here mention that may be an issue until it's rebooted a second time. So I set everything up, played around with the same ideas we were using earlier in this thread (to no avail) and then rebooted.
Wifi is the same as it always has been (with the exception of the glorious several hours when it worked like a champ on JellyBam). That's no big deal - I'm used to it and know it's an HTC One S quirk.
But....
Sound is back :good:
Click to expand...
Click to collapse
Lol the phone does love to be picky.