alright, so I spent the day installing custom roms to see what I liked. After all was said and done though, I decided to revert back to the stock android 4.4.2 (I know android lollipop is out, but I prefer Kit Kat's speed). after spending 4 painstaking hours getting the rom to work, it finally went through odin without any errors. I booted up the phone, and everything is perfect, except for the wifi. Bluetooth is fine as well, but wifi always resets the button position to "Off" whenever I try turning it on. I would appreciate any help possible.
BTW the variant is the bell mobile canadien s4
Related
Well I have been trying lots of different roms and finally decided to go back to hyper drive and use it for a while. Well I couldn't get data. So I Odin the original mdk that came with my phone and I still couldn't. So I take the phone up to Verizon have them program me a new SIM and it still doesn't do it. He said he could send it off if I had the warranty which I don't but I took it home and played some more.
The only time I can get Verizon signals is on kitkat roms now that I have tried them. I am being completely retarded and missing something easy. Like I'm supposed to flash something special when coming back from kitkat that I'm not doing or am I seriously ****ed until all the bugs get ironed out?
The kit Kat roms are starting to kick some ass though. I noticed tonight the verizon signal I do get though is much weaker than on my dad's stock rom. So I'm really looking for a clue or a future fix.
Maybe a radio flash or kernel I could flash on 4.4.2 it is the cyanogen nightly but I can switch roms if necessary also.
Running cm 10.2 and I can't seem to get WiFi tether to work..running the 3.3. The built in cm hotspot seems to work..devices connect but get no internet
Sent from my EVO using xda app-developers app
wifi
Ya i ran to this issue for the last year. Some peoples phones work with the native wifi mine never has. I have tried the trevemod, wifi was less then 2mb. Then i found the 3.2 and 3.3 versions of tether. It takes a lot of tweaking to finally to get it to work but they do work. Problem i always had is if i used my phone as it was going sometimes it would turn it off. And after an hour the data would be less. So i would have to reboot phone then i would get over 20mb again.
So not sure if it works on 10.2 but i came a crossed a thread in the OMni 4.4.2 Rom posed by SIlentstyder. found here http://forum.xda-developers.com/showthread.php?t=2495109&page=24
He came a crossed it for use with the NExus 5 via sprint. There are step by step screen shots how to do it. I gave it a shot and it worked like a charm. I have full 30Mb LTE + utilizing the native tether. It worked on the OmniRom. Then i went back to see if worked on DirtyUnicorns 4.4.2 and it worked there as well. Havent tried it on the sense roms but would assume it works there as well.
Only issue i had found is with dirtyunicorns rom, which i like the best out of the kit kat roms, is the internet works fine. i can connect any device but i cannot open my work email on any device connected to it. as well as that vpn doesnt work. So i went back to OmniRom and i can do this no problem. So not sure what thats about. I havent seen any post that have that same issue. So hopefully there will be an update soon and i can try it again.
Give it a shot, just make sure to save a copy of the settings.db if it doesnt work.
-Pulltab
I had an unlocked S4, which took an unfortunate dive and ended up non-functioning. I used my phone insurance to acquire a new (unfortuantely) updated phone running the full MK2 suite. First order of business was a root & install of SafeStrap, followed by installation of Hyperdrive to Rom Slot 1. I use my phone with my 2013 Subaru XV Crosstrek's bluetooth handsfree for both calling and media playback, and I use this feature EVERY SINGLE DAY. Unfortunately, not any more. I cannot get more than 15 seconds of connected time over bluetooth with the phone. I've tried multiple wipes. I'm fairly certain the issue doesn't exist on stock rom; so I may end up just customizing a stock rom in slot 1 by removing absolutely everything and building it from the ground up, since I don't have to use the (apparently buggy) mk2 modules.
Edit:
I'm seriously considering selling this phone and getting something more friendly to modding, this is a repeat of the Droid Bionic at this point.
Is there a question here? Did the stock rom blue tooth work ok?
Sent from my SCH-I545 using XDA Premium 4 mobile app
And this is why I shouldn't hastily write a post.
Yes there should be a question:
What can I try to fix the issue of frequent (alarmingly) bluetooth disconnects?
What kind of logging can I do to try and help provide developers with the information to fix this?
Anybody else have this problem? Any experience fixing it?
If I can't get this fixed, I have no choice but to move to another phone. Preferably at Verizon's expense.
Even more irritating: The phone is listed as compatible with the Crosstrek. I'm going to test that it works fine using the stock rom and bluetooth, and factory resetting my head unit.
Did you install the MK2 modules after installing Hyperdrive?
s.whiplash said:
Did you install the MK2 modules after installing Hyperdrive?
Click to expand...
Click to collapse
Yes. Originally when I installed it WiFi and Bluetooth didn't work at all. I realized quickly my error was the lack of installing the MK2 modules. I wiped and installed again, this time ensuring the MK2 modules followed the rom install. I got everything set up the way I like to, and began day to day use of the phone. Since then I have had the bluetooth connectivity problems I described above.
Bluetooth is rock solid on stock. I'd really rather not have to play this game where I can install stock or.... basically stock... and now that I'm locked kernel and radio wise if I have issues further with OTAs I'm just as stuck with a near useless phone as I was with my Bionic
I'm afraid that I don't have anything else for you, except try a different ROM. Bonestock or Eclipse? Bluetooth works pretty good for me with multiple headsets and vehicles. My only issue with Bluetooth is not all the apps will pass metadata to my truck. This happens with all 3 of these ROMs and I think it is a TW 4.3 limitation.
Are you doing anything to boost the Bluetooth volume? With my previous phone I boosted the Bluetooth volume via some hacks and my truck would not like it.
I know what you mean about having a locked down phone. I came to the S4 via a warranty replacement from an unlocked S3 running SlimBean and SlimKat.The problem is that most of the new phone that are coming out all have bootloader hurdles.
I'm having the same issue with my SGH-M919 (T-Mobile) running rooted stock TW. I've documented my issues and a few LogCats here. Have you figured out a solution?
Hi everybody,
I'd like to hear your thoughts on my problem.
I have been flashing my i9300 since the day I have it. I wasn't impressed with stock TouchWiz (4.1 I believe?) I have been switching between TW based and AOSP roms alot. I just never found the rom I liked. All of them began to run slow, if they were not already slow. (I do not blame any of the roms I have used, I want to point that out)
Recently I sent the phone back for repair, because it had a burnt in screen. So I went ahead and flashed full stock and reset the counter and all the fun stuff. When I rebooted the phone (100% clean wipe, flashed a Netherlands rom) I noticed that the phone was slow as living h*ll. I had flashed it to a "out off the box" experience but the phone was just about useless. I went ahead and flashed a different Netherlands rom, which was a tad bit faster. I went with it and sent it back.
When I received the phone back in my mailbox, they had flashed stock again (why would one flash stock if just the screen had to be replaced?). I noticed that the phone was extremely slow again!
I decided to believe that it was TW to blame, and flashed Omni KitKat. This was fine for about a week, after which the phone would randomly lock up and system.apk began to crash every 30 minutes or so.
I then decided to start with a clean plate and flashed CM11 (full wipe, including media and all). I have been using that for a little over 2 months now, but the same issues are starting to occur. I have tried it without any 3rd party apps installed, without success. The phone locks up about every 5 minutes with the screen on, I can't listen to music (Google Music or PowerAMP) and then switch to another app, because the music will then stop. If I press the home button, there is an 3-10 second delay, after which system.apk decides to reload along with the launcher (Google Now Launcher), things like that. Sounds like a memory problem to me.
I think it might have something to do with a baseband issue, because of the fact that I have had problems similar before, which were (sort of) solved by flashing a different baseband. But I don't think that Sammy's basebands are compatible with CM11, and I have yet to come across a problem with a CM11 baseband on the internet.
Do any of you experts know an explanation to my problem? Would you suggest sending the phone back for repair?
Thanks in advance
FistFull95 said:
Hi everybody,
I'd like to hear your thoughts on my problem.
I have been flashing my i9300 since the day I have it. I wasn't impressed with stock TouchWiz (4.1 I believe?) I have been switching between TW based and AOSP roms alot. I just never found the rom I liked. All of them began to run slow, if they were not already slow. (I do not blame any of the roms I have used, I want to point that out)
Recently I sent the phone back for repair, because it had a burnt in screen. So I went ahead and flashed full stock and reset the counter and all the fun stuff. When I rebooted the phone (100% clean wipe, flashed a Netherlands rom) I noticed that the phone was slow as living h*ll. I had flashed it to a "out off the box" experience but the phone was just about useless. I went ahead and flashed a different Netherlands rom, which was a tad bit faster. I went with it and sent it back.
When I received the phone back in my mailbox, they had flashed stock again (why would one flash stock if just the screen had to be replaced?). I noticed that the phone was extremely slow again!
I decided to believe that it was TW to blame, and flashed Omni KitKat. This was fine for about a week, after which the phone would randomly lock up and system.apk began to crash every 30 minutes or so.
I then decided to start with a clean plate and flashed CM11 (full wipe, including media and all). I have been using that for a little over 2 months now, but the same issues are starting to occur. I have tried it without any 3rd party apps installed, without success. The phone locks up about every 5 minutes with the screen on, I can't listen to music (Google Music or PowerAMP) and then switch to another app, because the music will then stop. If I press the home button, there is an 3-10 second delay, after which system.apk decides to reload along with the launcher (Google Now Launcher), things like that. Sounds like a memory problem to me.
I think it might have something to do with a baseband issue, because of the fact that I have had problems similar before, which were (sort of) solved by flashing a different baseband. But I don't think that Sammy's basebands are compatible with CM11, and I have yet to come across a problem with a CM11 baseband on the internet.
Do any of you experts know an explanation to my problem? Would you suggest sending the phone back for repair?
Thanks in advance
Click to expand...
Click to collapse
The problem might occur because of memory which one of my friend had earlier. Can you tell me how long copying files into phone storage takes?? Do you feel like ROMs are geting installed slowly than previous, slow copying of files?
ASOP Roms like CM never come with baseband. they use the same baseband that you already have in your phone. Only Stock based comes with baseband in their firmware. Sometimes(not most of the time) it can be if you are using different baseband than the one of the firmware, like if you have 4.1.2 and installed baseband of older version like of 4.1.1 but this is exceptional..
Thanks for your reply!
I don't think the internal sd has gotten slower tbh. I tried to copy an 2gb dummy bin from the extsd to my infernal sd, which copied with an average speed of 9mb/s.
I have tried experimenting with different TW based roms in the past, so I might still have a wrong baseband / ril. Is there a way of checking this?
Sent from my GT-I9300 using XDA Free mobile app
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