Hi there, everyone. Relatively new to all this custom rom stuff, but I have been able to change roms and such with a usable level of success. A few months ago I ran into an issue that I can't seem to fix on my own, so I'm reaching out to see if someone more knowledgeable might have some experience and can point me in the right direction.
After test-driving a few different roms for a few months at a time, I ended up trying out ArrowOS. While I really enjoyed the rom itself, my phone would only ever use the speaker phone, even when it was set to use the regular ear speaker. Recently, I changed to LineageOS thinking the issue was with the Arrow rom, but the issue persists. I figured it was a firmware issue so today I flashed the firmware package and, to my surprise, the phone is still behaving the same way.
The firmware I flashed in was (fw_curtana_miui_CURTANAGlobal_V12.5.6.0.RJWMIXM_84796eb2cc_11.0.zip). It flashed with no errors, so I assume everything is fine there.
Anyone have any tips for me to follow? Much appreciated!
EDIT: This might be a newbie mistake, but the firmware I have flashed says it's for Android11 and the LineageOS I'm using is an Android 12 base. I wouldn't think it would make such a difference, but this is coming from a long-time Windows user who is used to getting by on old drivers when necessary. The ArrowOS I was using when the problem first popped up was Android 11, but I hadn't updated the firmware of the device so it may have still been on Android 10 (or even 9, I don't know).
Double posting for clarity. After trying multiple roms and firmwares, the problem still persists. The weirdest thing is that when using a hardware testing app, the earpiece speaker works fine. I've also tried using other dialer apps and they all act the same way. I am completely stumped on this. If anyone can help I would appreciate it, otherwise I guess I give up. This is way beyond me.
Related
Hi guys, I have a rooted Bolt currently running 1.70.605.0. I rooted when i got it back in May and since then I installed a rooted update of Froyo. The phone has been dropping network connection a lot lately that it's very aggrevating. I am thinking it may help fix my problem if I update to Gingerbread with the new radio.
i downloaded the file 2.11.605.3.zip from the TeamBamF.net site last night but now I am sort stuck. It's been so long since I rooted this phone so I kinda need some help. I search everywhere but haven't found a thread where there is like a step by step direction. If someone can provide me some assistance or point me to the right thread I would so much appreciate it.
Vince
The data dropping out may be due to some work/upgrades in your area ... call VZW to see if they know anything.
As far as updating to GB, my advice is tread lightly ... especially if you're just wanting a stock version of it. There are bugs, the biggest being voice mail notifications not working, that may drive you nuts. That being said, there are several custom ROMs around that have fixes/tweaks that make this plagued GB build VZW & HTC released much more manageable. Look around and there are a few "stock" custom ROMs out there - or if you prefer a totally different look/feel there are several Sense 3.0 ports to choose from too.
As far as a how-to guide, the best one I've seen is THIS ONE. Read it and get knowledge my friend
Happy flashing!
2.11.605.3.zip is the [gb] patch - "It changes camera libs, and some insignificant
framework, and apks." as stated on teambamf.net, i did read it is running smooth,
increased battery life but,with issues pertaining to vm notification error and front facing camera
upside down. i agree with Yank talk with carrier, im currently running dasBAMF Forever
kernel 2.6.35.10 stock radios have had no issues.
vinny2006 said:
Hi guys, I have a rooted Bolt currently running 1.70.605.0. I rooted when i got it back in May and since then I installed a rooted update of Froyo. The phone has been dropping network connection a lot lately that it's very aggrevating. I am thinking it may help fix my problem if I update to Gingerbread with the new radio.
i downloaded the file 2.11.605.3.zip from the TeamBamF.net site last night but now I am sort stuck. It's been so long since I rooted this phone so I kinda need some help. I search everywhere but haven't found a thread where there is like a step by step direction. If someone can provide me some assistance or point me to the right thread I would so much appreciate it.
Vince
Click to expand...
Click to collapse
Can you link me to that download? I would like to see exactly what you are making reference to before I comment.
Some of those update .zips are the full unrooted rom. You wouldn't want to flash that. You want to make sure and look for something like...
"Rooted Debloat Blah Blah Blah"
The link provided by Yank is a good one. #3 for "Flashing a Rom".
Also another hint (just in case you are unfamiliar with recovery). the camera buttons toggle up/down and the power button is used to make a selection. you can select "go back" by toggling to it and selecting it or you can use the soft back key.
hope that helps.
As to the voicemail issue, Eris has fixed that. Took him 30 minutes, he said.
Sent from my ADR6400L using Tapatalk
Did you read this?
http://teambamf.net/showthread.php/718-How-to-flash-a-ROM
Ive used CWM to install different roms over a couple months since I have gotten my GS2. Ive never had a problem with Bluetooth connecting and playing music at all. But I find that since I started running the latest ICS XXLPH roms its been an issue.
Or can switching many roms over a course of time damage the antenna? or hardware? Any suggestions?
I am going to revert back to my stock roms after I send this message. The only reason I am sending this before I try it is because nobody else really seems to be running in to this problem after searching the GS2 thread.
Ive tried a couple ICS roms and all cause my phone to randomly reboot when using BT paired with my stereo either on a call or streaming music.
When it reboots enough times it starts to corrupt the ROM/install. Because after a while it will start to just randomly freeze on its own forcing me to reset the phone.
Ive searched all over I havent pin pointed anyone having the exact problem as me so that is why I wonder if its possible to damage the BT device after multiple custom rom installs.
Thanks in advance.
Chakker3D said:
Ive used CWM to install different roms over a couple months since I have gotten my GS2. Ive never had a problem with Bluetooth connecting and playing music at all. But I find that since I started running the latest ICS XXLPH roms its been an issue.
Or can switching many roms over a course of time damage the antenna? or hardware? Any suggestions?
I am going to revert back to my stock roms after I send this message. The only reason I am sending this before I try it is because nobody else really seems to be running in to this problem after searching the GS2 thread.
Ive tried a couple ICS roms and all cause my phone to randomly reboot when using BT paired with my stereo either on a call or streaming music.
When it reboots enough times it starts to corrupt the ROM/install. Because after a while it will start to just randomly freeze on its own forcing me to reset the phone.
Ive searched all over I havent pin pointed anyone having the exact problem as me so that is why I wonder if its possible to damage the BT device after multiple custom rom installs.
Thanks in advance.
Click to expand...
Click to collapse
You are using a leak or *beta* rom which is far from stable
And no installing many roms can not damage any hardware
Sent from my GT-I9100 using xda premium
Thanks for your response.
I am just concerned because like I said, from what I can tell, nobody else is running in to this problem.
Ive tried /format system along with full data/cache wipes. I wiped dalvik cache.
Im waiting for my phone to fully charge to put stock rom back on so I can test this completely.
But a bit nervous, because I need my phones BT as I am on the road often.
Chakker3D said:
Thanks for your response.
I am just concerned because like I said, from what I can tell, nobody else is running in to this problem.
Ive tried /format system along with full data/cache wipes. I wiped dalvik cache.
Im waiting for my phone to fully charge to put stock rom back on so I can test this completely.
But a bit nervous, because I need my phones BT as I am on the road often.
Click to expand...
Click to collapse
Having a similar, if not identical issue on latest Westcrip ROM. Near as I can tell, seems to be related to memory management: while on BT, RAM space drops almost 200Mb. While changing songs, or surfing the tracklist/phonebook, it can cause the RAM to reach a critical level. This causes the OS to crash and the phone to reboot (my case a soft reboot from the animation only) in order to create space. I would chalk this up to inefficient memory management by a beta ICS rom. Look for this to be sorted out in the future with official releases and custom kernels/roms.
Thanks for your response.
Yeah when I installed resurrection, I also ran in to that problem. I had no idea how to diagnose it. But it makes sense, bottling up the ram to the brink of reboot.
Thats what initially was happening to me, soft boot, took a few seconds and was back in. But extended crashes seemed to cause corruption.
Yeah so the XXLPH seems to have an issue. Because I also tried foxhound and got the same result.
I just got back in from testing my BT on my car stereo using my stock rom of KG2 and it played for 20 minutes and i chatted for 19 without any problems.
So I am glad it wasnt anything seriosu. But only reason I was concerned is I found nobody else to have the problem and I felt a bit isolated
But im reading the official ICS rom is out in Europe so im sure we will see some new roms out in the next little while.
Okay so this is my first post on XDA and I hope it's in the right section. Anyways I bought an HTC Incredible off a collegue of mine about two weeks ago. I got the phone and immediately rooted and installed a custom rom (MIUIv4 to be exact) I noticed after a lil while that the touch screen would randomly go berserk clicking things, calling people, etc (usually right after turning screen on) When the screen starts doing it I'd turn it off and back on and it would be completely fine. I thought to myself "maybe it's just a problem with MIUI and installed PONS CM7. I still had the same issue. Now whats strange about all of this is if I'm running an RUU or Stock based rom the screen NEVER acts up. I've read on several forums that this is a hardware issue but most people still experience it on stock roms, this is not the case with me. I won't deny that it could be a hardware issue, but it's an issue that can be solved with kerenl/dirvers/software. I'm wondering if I can use the drivers and software from a stock based rom to combat the issue and make custom roms run like they are supposed to. In all of my research I found this link which seems to be pretty promising but I don't know where to begin with it. Unfortuneately I can't post a link until I've posted 8 times, uuugh.
Edit: It seems the longer I run a custom rom the more frequently the issue happens.
If anybody is intrested in helping it would be greatly appreciated. I've been racking my head for over a week on this one. You can look up the blog I read on google. It looks like it could solve my problem.
Unresponsive touchscreen of Nexus S solved by tuning kernel
Hello friends,
I recently picked up an i717 and am in the process of sorting it out. It was originally a Bell phone, though of course it's unlocked these days. I've been hacking at various Android phones for years now and have managed to work through just about everything, but this has me stumped...
I've tried almost all the 4.4 roms, and most of the 4.3 as well. I've tried various kernels/modems/combinations/etc. I've used CWM and TWRP. They all invariably lead to the phone either rebooting constantly from the "optimizing apps" dialogue, or a few times I've made it to the welcome screen, but it's always just up for a minute or two, crashes, then reboots. I haven't found a live download for 4.2 yet, so I don't know if it would work or not. 4.1 stock and Padawan run just great. I've been doing multiple full wipes before installation, flashing the rom a few times, then hitting the caches a few more times for good measure. I can't imagine my flashing technique being at issue here.
I do know that there is at least some physical damage to the phone. The capacitive buttons don't work. But it doesn't see immediately obvious to me that these would be related. Of course, I've seen stranger things. Running Padawan the phone will hum right along at max speed all day with no apparent issues, so that side of the hardware seems okay.
Sometimes CM roms will end up at the CM welcome screen and pop up a "com.android.acore has stopped" dialogue. But the constant reboots are there on every rom I've tried.
Does anybody have any ideas?
Outside of the, every once in a while you just need to go all the way back to stock just to make sure all the garbage is taken out, have you considered the infamous stuck power button?
Though I have yet to, many have experience the stuck power button. It may feel ok and you may even hear it click, but that doesnt mean anything. Give your phone a couple good flicks to the back behind the button. Though it does seem odd that it would run one rom without issue and not others, but it is worth a shot.
Again taking your phone to 100% stock every blue moon or so can be a good remedy too.
Keep us posted. We can work you through this.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
I thought about the power button issue. However, it proceeds to boot into the OS until after a time when the screen locks then reboot, which would seem too long to be the power button in any case. Regardless, a few sharp flicks didn't help much. And, of course, it runs quite happily all day long running on 4.1.
I have restored to stock JB, though admittedly not earlier than that. I guess I could try going all the way back to GB to see if that makes any difference.
In my experimentation tonight I've found that 4.2 also does not work, while I can add 4.1 non-tw roms to the working list. My best guess seems like something about one of the many under-the-hood things that changed with 4.2 doesn't get along with something about my particular phone. But, who knows.
For now I'll try rolling back to GB in Odin and see where that gets me.
I would say ICS is about as far back as you need. Recently I was having issue getting anything 4.3 and up to work or even flash. No different recoveries had effect either.
Wiped slate clean and started over from ICS, and Bob was my uncle. Everything that failed before was not an issue. Running latest 4.4 now and might I say "Orgasmic"
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Ahh, if only I were on 4.4 on my Note, life would be good Though, to be honest, I'm quite digging this thing, even at 4.1.
Last night I rolled back to GB, and had no luck. Although the Odin tar that I found apparently didn't include recovery, so that had to be flashed separately. I don't know if that might make a difference. That might be my experiment for tonight if I can find a tar that includes everything. Might be easier to find on ICS.
Just running my mind through other stuff I've thought of, I remember reading about kitkat having some issues with SD cards, so I've mostly been experimenting with the card pulled and a fresh format on the internal storage, with no real difference. Tried safe mode, no dice (not that I would expect this to make a difference on a fresh flash, but who knows lol...).
It's just such a weird thing. It boots into the OS with seemingly no issues. On occasions when I can actually get to the lock screen, everything runs fluid as can be until it freezes and reboots. Sometimes when it gets stuck at the 'optimizing' screen it'll just restart the count every boot, sometimes the number of apps to be done go down each time until there are 3-4 left which persist through each reboot.
I wonder if I could check logcat via adb before it reboots. Might be able to find some clues there.
Here's a factory firmware image of 4.1.2 to be flashed with Odin.
http://www.mediafire.com/view/g7gn29h7nu63id5
I've used this to revert many times. Install it. Run it once, then factory reset and run it for at least a few hours. If you experience issues you probably have hardware failure. If you don't have issues you can proceed with installing the latest clockwork mod recovery. Then wipe system and internal memory 3 times with recovery. Now flash the zip of your favorite kit Kat rom. Reboot and run it. Then factory reset and hopefully run it forever! If you're on a kit Kat build and experience sd card issues, there's an xposed module that might be able to help with that.
Thanks a lot, Bro. I'm downloading the image right now and will flash it then give it some time to settle in. Fingers will be crossed!
Just to give you guys an update, I flashed that stock image, ran it that way for a day, then attempted a few different 4.4 roms. Still no lock.
But thanks for the ideas so far!
I guess it's not the worst thing in the world. At least it runs 4.1 like a top.
Bassism said:
Just to give you guys an update, I flashed that stock image, ran it that way for a day, then attempted a few different 4.4 roms. Still no lock.
But thanks for the ideas so far!
I guess it's not the worst thing in the world. At least it runs 4.1 like a top.
Click to expand...
Click to collapse
Have you tried to turn on USB Debugging and run "adb logcat" to see what errors are causing the problem? If it is an optional program or hardware feature you may be able to disable it and run the newer ROMs. I know bluetooth has been an ongoing pain point for people. Which modem are you running? I know that some of the older modems do not work with the newer ROMS.
Good luck.
Brett
corrupt radio
i had the same issue, flashed 4.4.4 and ran like a charm for 1 day them the radio took a dump. downgraded and worked for another day.
imei became unknown and the no radios were able to fix this. went as far back as 2.3.6 hoping my radios would be fixed and no dice.i have tried endless for weeks to fix my phone and seems doomed.
none of the bricked threads helped and flashing stock with odin is no help. there seems to be no fix to the null imei and unknown baseband
At some point in time my garage door opener app (MyQ by Chamberlain) stopped working. I upgraded a while ago to android 10 and have tried multiple flavors, settling on StagOS. The app now gives me a "error connecting to server" message when trying to do anything (log in, sign up for new account, forgot password, etc). Not sure what the issue is. I've tried fresh installs of StagOS and Potato with the same result. Have also recently (?) started failing safety net /CTS profile, so I'm not sure if that has something to do with it or not. No problems with my older tablet and wife's stock S9 running 10. Was hoping someone could install the app and see if they get the same issues, maybe let me know what ROM you're using. Thanks.
Anybody?
Seriously, nobody is willing to try this?
You're looking for a very specific user who 1) comes to XDA, 2) has a MyQ system, 3) has StagOS. It's not surprising you're not getting an answer, as there may not even be another person here with the exact setup you have... so how do you expect someone to test this? Your best bet is probably to ask on the StagOS thread, as you'll have more luck? (I haven't even heard of StagOS, but I also don't run a custom ROM.
Bottom line, you'll have to do the testing yourself, as you are probably too specific for others to help. For example, I don't have Pie, StagOS, or MyQ, so I can't help... I'm sure many others are in the same boat for various reasons.
Actually, I'm looking for someone who has any custom ROM to see if it's specific to this one, all lineage builds, Android 10 only, maybe a Google play services update broke it, etc. And you don't need a myq system. You just need to install the app and hit "sign up" to see if you get the error.
Ok, that wasn't clear in your request. But even still, I'm confused. You already tested this (with your wife's phone) so what are you asking people to do? You know it works on Pie (per your wife's phone), so it's clearly an issue with the two custom ROMs you tried. I'm guessing that's the issue... but I'm not sure how me testing on my VS996 Oreo will help you any more than your test on your wife's phone does? Custom ROMs often have such issues... have you tried a stock ROM instead?
schwinn8 said:
Ok, that wasn't clear in your request. But even still, I'm confused. You already tested this (with your wife's phone) so what are you asking people to do? You know it works on Pie (per your wife's phone), so it's clearly an issue with the two custom ROMs you tried. I'm guessing that's the issue... but I'm not sure how me testing on my VS996 Oreo will help you any more than your test on your wife's phone does? Custom ROMs often have such issues... have you tried a stock ROM instead?
Click to expand...
Click to collapse
I think he does need someone with an Android 10 LOS ROM. Not necessarily StagOS, but still an LOS ROM vs stock. I can't help either.
Yeah, if anyone has any other Android 10 custom ROMs it would be helpful to know if any work. I got safety net to pass, but that didn't do it either