I updated to EB13 from DI18 originally using ODIN and the eb13.tar. Things were fine, no real bugs except the known video camera bug and screen lag. I was able to fix the screen lag once I rooted and ran the sensorcalibutil_yamaha scrpit. My TWS was only 2% and had no 3G data problems whatsoever.
Recently I decided to try out the deodexed rom from the dev section, but when I started it up I kept getting the "buz...buzz-buzz-buzz" over and over. I though I must have done something wrong, so I formatted my sd card, wiped my phone, cache and dalvik cache. I then used ODIN to re-install the eb13.tar and I re-rooted using oneclick root.
This time around, I now have 55% TWS in the same location as before and 3G data drops like crazy. Also for some reason the market app won't update itself to the new version and is stuck on the original, old style. Also interestingly, on this flash I had zero lag problems and my compass and gps work flawlessly.
I'm not sure what is going on or why this would happen, anybody else experience something like this??? I am worried because I have a phone interview in the morning and can't afford signal drops when I have full coverage. I am going to re-do the whole process and hope that fixes it
I odin'd two times trying to fix this again, no dice. I never should have messed with things because all was good until I started messing about.
Found a solution for now though, I Odin'd back to DI18 and am calling it a night. I can't afford a spotty data connection for my interview in the morning. I'll report back once I start tinkering again
Odin to DI18 and don't do anything. Just turn off your phone.
Copy the EB13 update.zip to the memory card and delete your "Android" folder as well as any app specific folders for cache or whatever.
Put in your memory card and boot into recovery. Flash the update.zip and reboot.
Once the phone is on you can use the OneClickRoot 2.5.5 to get root and recovery.
I still get the TWS problem but airplane mode fixes that.
arashed31 said:
Odin to DI18 and don't do anything. Just turn off your phone.
Copy the EB13 update.zip to the memory card and delete your "Android" folder as well as any app specific folders for cache or whatever.
Put in your memory card and boot into recovery. Flash the update.zip and reboot.
Once the phone is on you can use the OneClickRoot 2.5.5 to get root and recovery.
I still get the TWS problem but airplane mode fixes that.
Click to expand...
Click to collapse
thanks, tried this but it didn't correct any of the problems. My market refuses to update to the new version for some reason. When I Odin'd back to DI18, the market ap updated itself on the second launch, no problem.
As far as TWS goes, the issue is still persisting. I did notice that if you are using the data connection for something like shoutcast radio (internet radio) there is no drop at all, and the signal is almost boosted. But if you aren't actively using the connection it drops, connects, drops, connects, over and over. It is absolutely killing my battery life.
Edit: Fixed the market update problem by clearing market cache and data. Now if we can find a fix for the camera lag and TWS problem, I will be a happy camper
Related
A little over a week ago I upgraged to a 2.2 ROM on my Epic (DK28.) I was getting all sorts of weird, random issues. Sometimes LauncherPro would force close (almost always after a reboot,) sometimes my wifi would lock up when trying to turn it on (only fixable via reboot...which then caused the aforementioned LauncherPro force close..) and my log viewer would fill up with thousands of errors in just a couple hours...most of them said "AudioDeviceManager" or something like that.
So last night I decided to go back to DI18, and now I'm having worse problems. I flashed it with Odin, and it seemed to be fine at first, but then a little while later I kept getting android.acore.process force closes every five seconds, making my phone completely unusable. I did another reset to DI18 with Odin, and this time it worked fine the rest of the night and into today, although I was still getting thousands of errors an hour in my log...
About an hour ago today, I went to just open my calendar and it force closed every time I tried...so I rebooted, and since that reboot I have gone back to having android.acore.process force closes every three to five seconds. I have rebooted several times, pulled the battery and left it out for a while before rebooting, rebooted without the SD card, every time I get that. I'm at work so I can't try another reset back to DI18, but I'm afraid I'll have the same problems...should I attempt to exchange the phone with Sprint?
I would boot into clockwork and delete dalvik cache and data.
Then I would do ODIN again.
Then I would re-root with clockwork and wipe again X3
Good luck!
brian_hoffman said:
I would boot into clockwork and delete dalvik cache and data.
Then I would do ODIN again.
Then I would re-root with clockwork and wipe again X3
Good luck!
Click to expand...
Click to collapse
No, he shouldn't have to do any of that, cuz Odin will overwrite everything on the phone. Try downloading the DI18 Md5 tar file again and re-flashing..
On another note, you got this thead in the wrong section. It should be in "General" or "Questions"...
VIPERrom [TRiNiTY] 3.0.3 DK28 FroYo by XDA's "BThomas22x" and "Viper Team"
sniperkill said:
No, he shouldn't have to do any of that, cuz Odin will overwrite everything on the phone. Try downloading the DI18 Md5 tar file again and re-flashing..
On another note, you got this thead in the wrong section. It should be in "General" or "Questions"...
Click to expand...
Click to collapse
Sorry about the wrong section, didn't realize.
I'll re-download DI18...I flashed this exact file before though and didn't have problems with it the first time around.
I have great copy of the DI18 file that works fine for me whenever I flash back if you're still looking for it. I can pm you the link.
Hi guys
So I installed Nero v3 on my Vibrant, and all is well. I followed the steps on the Nero thread. I like it very much.
Then I decided to flash my gf's phone. It seemed to go well at first, but then some odd stuff started happening. First, I can't open the "Settings" menu - nothing happens. Second, lots of stuff force-closes all the time.
Those two are minor issues, though. Somewhere between 5-15 minutes after flashing, the entire GUI will force close. The phone will vibrate, then the Team Whisky logo will appear again (as if rebooting), and the GUI will appear and begin the regular startup procedure. It will get as far as "Preparing internal SD card" before the GUI will crash again. This cycle continues indefinitely. Once it has begun, not even pulling the battery and rebooting it will solve the problem.
Any advice?
My plan is to find a way to back up the SD card data and format it, since it always crashes on "Preparing internal SD card." However, I doubt this will help, since the other issues (constant force-closes) don't seem to have anything to do with that.
stoanhart said:
Hi guys
So I installed Nero v3 on my Vibrant, and all is well. I followed the steps on the Nero thread. I like it very much.
Then I decided to flash my gf's phone. It seemed to go well at first, but then some odd stuff started happening. First, I can't open the "Settings" menu - nothing happens. Second, lots of stuff force-closes all the time.
Those two are minor issues, though. Somewhere between 5-15 minutes after flashing, the entire GUI will force close. The phone will vibrate, then the Team Whisky logo will appear again (as if rebooting), and the GUI will appear and begin the regular startup procedure. It will get as far as "Preparing internal SD card" before the GUI will crash again. This cycle continues indefinitely. Once it has begun, not even pulling the battery and rebooting it will solve the problem.
Any advice?
My plan is to find a way to back up the SD card data and format it, since it always crashes on "Preparing internal SD card." However, I doubt this will help, since the other issues (constant force-closes) don't seem to have anything to do with that.
Click to expand...
Click to collapse
Was her phone stock before you started tinkering with it?
In any case I'd suggest re-download nerov3 (to avoid corrupted download issue), ODIN back to JFD (remove the ghosts from the past ROM's) and reflash.
Phone was stock aside from rooting for the purpose of TitaniumBackup. It has never had anything installed on it.
I'm currently Odin flashing back to stock, and I'll give it another shot.
stoanhart said:
Phone was stock aside from rooting for the purpose of TitaniumBackup. It has never had anything installed on it.
I'm currently Odin flashing back to stock, and I'll give it another shot.
Click to expand...
Click to collapse
Good luck!
Well, I did the Odin flash to stock, then installed Nero. After first boot, I left it untouched for 20 minutes or so, and then did a clean reboot. Upon starting up, I was once again stuck in the loop.
Boo
stoanhart said:
Well, I did the Odin flash to stock, then installed Nero. After first boot, I left it untouched for 20 minutes or so, and then did a clean reboot. Upon starting up, I was once again stuck in the loop.
Boo
Click to expand...
Click to collapse
Did you re-download nero? It might be a corrupted download, I haven't seen anyone with the same symptoms.
Does it happen if Voodoo is disabled?
EDIT: Saw that you didn't even have a chance to enable it, hmm, try a different ROM? Axura or Eugene's work.
No, I didn't try re-downloading it. Perhaps I'll give that a try, although it is the same file I flashed onto my phone.
After a bit of time playing with Nero, though, I'm considering going back. The parts that work are slick and wonderful, but it very much feels like beta software. In particular, scrolling lists or web pages is choppy. I've heard this criticism of Android before, but I've never experienced it with the original Vibrant software. It was always so smooth. It makes me think that maybe Samsung was using GPU acceleration in some places. Also, I seem to have some problems with the touchscreen becoming unresponsive, especially in the browser if it's blocked waiting for data (another bug...).
Is it possible to run the JL5 modem on the stock image? That would be great.
I can't begin to describe how frustrated this phone has made me. I am not an Android "n00b" by any stretch. I have had 4 different Android phones, have flashed at LEAST 100 different roms, made complete rom themes, and even glued together one of the first complete Gingerbread roms to flash from recovery for the Motorola Droid (not from source, but first posted rom with working camera, Gapps, and all from standard recovery - not nandroid). With that being said, this phone is next to impossible for me to use. I've lost track of all of the problems I have had with this thing. Everything from CWM not being able to restore any backups, horrible battery life, boot loops galore, the phone freezing anytime it is plugged into the computer or wall (not the car charger, oddly enough), boot loops, tried the Yellow Clockwork (and everything failed that could on that), flashing roms that would work great until you reboot the first time, and so on and so forth. WHEN the phone works, it's great. However, that is starting to become quite rare. Most recently I have been stuck on trying to get either Evil Fascinate to work or MIUIWiz with no luck for either. EF works great...until I restore my apps. Once I reboot, it's all over. EVERYTHING force closes and it becomes completely unusable. Doesn't matter what kernel I use, it always happens. And this is now happening with both 3.5.1 and 3.6.0. Plus I could just watch the battery life plummet as I was using it. I even tried the EC01 radio with it, as it was suggested that might be better. So, I decided to try MIUIWiz. Followed the directions perfectly. Wiped everything, flashed a JT Kernel from 4/15, flashed rom, and...guess what? Boot loops. I am on ClockworkMod 3.0.2.7. I am familiar with how to wipe data/cache/dalvik. There were no voltage settings to wipe. I did check to see if Voodoo was enabled before booting. I just don't know what else to do. This isn't exactly rocket science and I really feel it can't just be user error at this stage with all of the different issues I have ran across. I'm pretty much at the stage that I am gonna return it to stock and sell it, but would really like to enjoy it for a little while longer... Thoughts?
Just for laughs, I downloaded Community Rom 1.3. Was on EF 3.6 (with nothing restored, just signed into Google). Rebooted to Recovery, wiped everything, installed Comm Rom and never got past the Samsung screen. *sigh* Seems odds since they are based on the same base, but yea, that's how it's been going for me.
I think since you are so god awfully experienced that you are looking over something that probably seems useless to you, ive NEVER experienced any of your problems and I can tell you its not the phone.. I would read up about your specific problems or ask a specific question and you might get the help you need.
Edit:Bootloops are user error nearly every time. Unless you have a corrupt download or something.
Sent from my SCH-I500 using XDA App
As much as your sarcasm warrants a rude response, I'll choose not to stoop to that level. The point of the post was that there is not a "specific" problem. Hence the title, "Nothing works as it should..." Not every phone is the same, and just because you have experienced any of these problems does not determine whether my issues are phone related or not. Battery life issues are very common place, which is evident in many threads. The phone lagging when plugged in is most CERTAINLY a phone issue and has nothing to do with rom flashing. It appears this is a firmware issue and is not likely to be fixed at all. Also, I pointed out the steps used to flash the rom, which are posted in the thread, and still have problems with boot loops. So, I guess every rom I download is corrupted? Even though on different networks and computers? That's some luck I have...
Are you referring to "download" mode when you said yellow cwm? If so then maybe reinstall the samsung drivers and give it a clean flash including the pit with voodoo disabled. If you have bad problems like you are having that fixes anything I encounter.
Edit: if you use odin, try heimdall
Sent from my SCH-I500 using XDA App
The newest imnuts kernel installs a yellow CWM, and nothing worked right at all on that. Every verification failed. SO I ODINed back to stock and retried everything anew. Anytime I restore my apps with Titanium, the next reboot fails. I even just went back to stock again, flashed CWM Red 3.0.2.8ti and the stock kernel with recovery fix, restored apps again and rebooted and it did the same thing. I didn't have any issues with Titanium restoring stuff before, having successfully used it on EF 3.5.1 and ComRom 1.3 but not those don't work for me either anymore. I've tried restoring just the apps with no data and that doesn't seem to make a difference either.
EDIT - It must have something to do with Titanium. Gonna try an older version and see if that works. It looks like they updated it recently and maybe it is just not playing nice with anything for my phone.
When you restore try not restoring system data, that is check the box for user applications only. That might be the issue.
yea, I'm going to say Ti backup is the problem because you mention ti every time you have a problem. personally I don't use ti cause its never played nice for me, but did you try manually reinstalling a couple of apps reboot and see if the same problem happened? that would really narrow it down almost completely to ti.
Fascinate 2.2 1.2GHz(uv)
download the imnuts peanut butta jellytime kernel of choice and put it on your sdcard. Odin back to the stock rom of your choice (i recommended eb01 as other odin packages cause bad music quality.), and let the phone boot up.
Next, pull the battery and go back into download mode. Odin one of times_infinity's cwm packages. Then replace the battery and boot straight into CWM. Wipe data, cache, and dalbik and then flash community rom 1.3. IMMEDIATELY AFTER (meaning in the same cwm as when you flashed comm rom 1.3) flash the imnuts kernel that you put on your sdcard. Phone should boot up fine and be fully functional. As mentioned earlier by someone, dont restore system data with titanium backup.
It's not just the system data that is causing issues, as I have tried it both ways, and of course, only restoring system data that is labeled green when attempting to do so. And, it did work previously on EF 3.5.1 but no longer does. I'll give it another shot using thefunkbot's directions. Still confused as to why EF is the only rom that boots normally.
Alright, so that did get Com Rom running. I had actually tried that method before, but it took so long on the Samsung screen that I was sure that it was froze. I just let it go this time, and after about 5 minutes it finally started. None on the other roms I tried took that long, but whatever works...
that's probably due to voodoo, which takes about that time to install/initiate.
Yea, you can hear the creepy robot lady telling you what's going on, but it took a couple of minutes after that even. Also, I skipped Titanium and restored the apps manually. Some were from my SD card and some from the Market, and only about half of them worked after rebooting. Meh
Flash com rom, then flash the otb kernel. Comrom will boot and you will enjoy your phone.
I got Com Rom to boot, but alot of the apps won't reinstall without force closing after rebooting. Not being able to use Titanium is a major PITA to me. But it's not just Com Rom, it's EF, and even the stock rom. Just never had an issue with it before now. But even installing apps through the Market or from the SD card also created issues, so I dunno what is going on.
If you're getting a **** ton of FCs, try fixing permissions via Terminal Emulator. Run 'fxpms' and it *should* solve some FC issues. Also, the phone generally takes much longer than a couple minutes to boot up after doing a full wipe, because the dalvik cache has to be rebuilt. Guarantee that if you had just left the phone alone the first time it was stuck on the Samsung screen, it would've booted just fine.
There are many guides that should help if you run into problems. First odin back to stock update to get new modem (doesn't have to be the newest but might a well), use the pit as well. Second odin cwm. Then flash kern and rom with a voodoo conversion if desired.
At first don't restore any backups. Don't use any themes. Or make any other changes until you see how out runs. Also don't play with the under volting until you've used it a while.
After running it awhile "stock" a it were then start making your changes one by one. This way at least you will know what its causing the trouble.
That happened to me as well when flashed com rom. I took 3 batt pulls before I just let it go to find it was working all along just took its sweet time on first boot. Was not voodoo here. I also agree with your charger problem, but for me its reversed, only happens on the car charger. And I hate to say it but no froyo rom, stock or otherwise, plays nice with my fascinate. I get all kinds of weird bugs. And battery life got worse. Since I have come to the realization that no fascinate aosp or cm rom will ever have bluetooth headset support, I finally threw in the towel and spent an hour on the phone with verizon to get an upgrade. Sad but after all this time it was time to give up.
Sent from my SCH-I500 using XDA App
Wiping Davlik causes unusually long boot times on Froyo ROMs on the Fascinate. If you just wait it out (if it's more than 15 minutes, though, something's wrong) you should be golden. By the way, PBJ 5/23 is literally a non-starter, so I would suggest nemesis2all's OTB kernel until imnuts updates.
Another Fascinating post by my XDA app...
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
es0tericcha0s said:
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
Click to expand...
Click to collapse
Blackhole 4.4? Or an earlier version? I miss SonOfSkywalker's work since he added the Thunderbolt to his arsenal (he also devs for the Vibrant)
Another Fascinating post by my XDA app...
4.4. Haven't had any issues with it so far. Battery life is probably not the best so far it seems, however I don't even care at this stage as long as everything works. I also have not run it down and reset the battery or played with many settings yet so not ready to say it is the rom or anything of the sort. Everyone has their deal breakers with their phone, and not having Titanium work is one of my biggest things. I love that app. I didn't donate for it to not use it, you know? I'm a themer, and I have a lot of themed apps saved with it that makes the Market pretty much useless to reinstall stuff for me. Plus it is an easy way to uninstall system apps without screwing anything else up.
I was wondering if anybody else is having an annoying issue I have been having with my epic lately. On pretty much every rom (even cm7 to my surprise) and every kernel but stock for some reason the status bar keeps showing usb connected on and off again nonstop!!! Only way I've got it to stop is by rebooting the phone over and over until eventually it goes back to normal. Is there a fix for this that maybe I've missed. I've tried turning usb debugging on and off but to no avail
raphi809 said:
I was wondering if anybody else is having an annoying issue I have been having with my epic lately. On pretty much every rom (even cm7 to my surprise) and every kernel but stock for some reason the status bar keeps showing usb connected on and off again nonstop!!! Only way I've got it to stop is by rebooting the phone over and over until eventually it goes back to normal. Is there a fix for this that maybe I've missed. I've tried turning usb debugging on and off but to no avail
Click to expand...
Click to collapse
Not a bug. More than likely your USB port is going bad. To confirm you should Odin back to EC05 stock and see if it is there. Then move forward with rooting and flashing checking it each step. Then do not restore nandroid data or system data from Titanium. Just restore what you absolutely must have.
I have odin'd back to ec05 and it doesn't happen, it doesn't do it on stock ei22 either, that's why I was wondering if maybe it's something the developers have been implementing lately. And I never use titanium, great app but I like to avoid all issues when switching roms, even on the new clockwork I still wipe data and clear cache 3x before flashing lol.
Then that makes it more peculiar. So if you flash a ROM fresh from rooted EC05 it does this?
Sent from my SPH-D700 using XDA App
Yup, I've been switching around between cm7,cleangb,legendary,sleeper and rebuilt (all on as clean as an install can be). Switching up the kernels between shadow and samurai and still no luck. But odin back to boring old stock ec05 or ei22 and it's all fine and dandy . I remember reading one of the rom threads that another member was having the same problem, but I"m surprised most people aren't so its driving me mad! I can't even check the time without having to wait for the split second that it shows
I just got this for the first time. Running shadow kernel on legendary 2.1 reboot fixed it.
Sent from my SPH-D700 using Tapatalk
im getting the same
This is also happening to my phone but if I unmount the sd card and take it out it stops. When I put the card in it mounts and starts doing it again. I formated the card after backing up to my pc but it keeps sayin usb connected
Hello I have a rooted Galaxy S5. My bluetooth was working fine as of yesterday now today when I go to turn it says turning on and then just goes back to off...the only thing I've done as of late is edited a system file to allow write capabilities to the SD card and installed pandora patcher...please let me know if you have any suggestions to a fix...thanks!
Ps I've tried reboot, clearing cache, and taking the battery out
Ace71425 said:
Hello I have a rooted Galaxy S5. My bluetooth was working fine as of yesterday now today when I go to turn it says turning on and then just goes back to off...the only thing I've done as of late is edited a system file to allow write capabilities to the SD card and installed pandora patcher...please let me know if you have any suggestions to a fix...thanks!
Ps I've tried reboot, clearing cache, and taking the battery out
Click to expand...
Click to collapse
I'm actually experiencing the same problem.
I don't know how long it's been going on, as I typically don't use BT. I'm experiencing the same symptoms as the OP - I try to turn it on - it tries to come on - then goes back off.
I've disabled much of the bloatware, so I opened TiBu to see if there's anything that I've frozen that might cause BT issues. None of them would seem to cause the BT issues I'm experiencing.
Any ideas for me/us to try?
Ace71425 said:
Hello I have a rooted Galaxy S5. My bluetooth was working fine as of yesterday now today when I go to turn it says turning on and then just goes back to off...the only thing I've done as of late is edited a system file to allow write capabilities to the SD card and installed pandora patcher...please let me know if you have any suggestions to a fix...thanks!
Ps I've tried reboot, clearing cache, and taking the battery out
Click to expand...
Click to collapse
How did you get this fixed, I'm having the same problem: Edited file to allows 3rd party apps to write to the SD card, but had issue so reverted to backup file I created prior to editing original. But BT still not functioning even after numerous reboots.
same here
Same problem here. I noticed bluetooth stoped working after installing juice defender. Dont know if thats the cause. But clearing cache, factory reset, uninstalling apps, etc. Hasnt worked.I read where someone reflashed in odin and it worked. Will an odin flash void knox or my warranty? Sprint galaxy s5 rooted. Stock rom
Same problem here...
I have done factory reset, clean wipe via recovery and reinstalled rom.
Still the Bluetooth acts as if it is goona turn on but does not.
Problem fixed but at a cost
I had the same problem thats being discussed in here.
I was rooted with stock rom on the latest build NK2, I also modified the xml file so I could write to the ExtSdCard and it didnt work so I put it back to original and somehow my bluetooth got messed up after that. I would attempt to turn on but would only go back to off.
What I did was I unrooted by going into CF SU settings and chose the unroot option, I flashed the stock nk2 firmware and did a factory reset and that got bluetooth working for me again.
I'm going to stay unrooted until lollipop drops for Verizon S5.
Hope this helps somehow.