Ok, so I'm a bit new here and I'm not sure if this is the right place to post this, but I'm gonna give it a shot anyways.
Well, I flashed it last night with the EE03 modem and I really do like it so far.
The only problem is that I can't send picture messages. The thing just hangs there.
Anybody here running this ROM running into this issue?
im running it, i havent had that problem, the only problem ive had is not being able to have an integrated facebook contact account.
Related
Hi All:
After seaching the forums all day and trying to decipher whats going on, I have to resort to noobish actions by posting a new thread.
What I have is a Kaiser, NAND flashed to Thoughtlesskyle's not so super froyo RLS18, radio ROM has been flashed from 1.70 to 1.65 and back twice, all "androidupdate.tar" files installed for the issue I'm having, and it seems to be Froyo related as I wasn't having this issue with Eclair builds.
Essentially, I don't have a data plan and would like to use the WiFi on the Kaiser, but even after Kernel replacements and ROM flashes across builds (I thought "Super Froyo" from Incubus26Jc was kinda cool, even tried a gingerbread build), I have yet to get it to work.
My guess is there's something going on in the wifi script that I'm not seeing. It has been replaced and still has an issue. I only get "Error" after trying to start it.
If anyone has a spare finger to point me in the right direction, I would be greatly appreciative. The little woman is getting lonely waiting for me to finish this...
I'm guessing by the views that this is either a still ongoing problem, or someone wanted to see what the noob posted...lol.
With an average 5 views per hour though, I would think some people are still searching for an answer.
It is strange, after my first installation, I already had the wifi, without any problem..
Maybe you have a wrong kernel, or a wrong radio? I don't know.
I will upload you my SDCard folder, then you could give it a try..
I will edit this message and give you the link when it is done
EDIT : Here we go ! http://www.megaupload.com/?d=9CBZ29P2
Wifi not working can be kernel based prob and build based too.. i suggest get a latest kernel from Kernel thread and try using another build.. mine was working fine till i used android i dont anymore coz it sucks the battery out.. still best of luck to u hope u get it to work
Ok, i got it to work... Thanks anyway Zebra...
What it turned out to be was an update overwrote another update and reinstalled the "bad" wifi script. I reinstalled the update and got it going.
BTW, I did happen to find a hardware clocking script with the wifi fix included, but the Kaiser doesn't support 600MHz clockspeeds...PFFT.
Battery has been fine for 2 days with moderate/heavy use (pandora/market/browser/txt/phone). The battery is a 1350mah type and I'm got around 11 hours on day one and so far I'm at 56% today. My day starts at 5am, and my old i930 is usually dead by now.
Before I get n00b bashed, I did "Search this thread" for the answer... (and other forums) Maybe I am just too n00b? Anyway, here goes.
Given kudos on this ROM already (Syndicate Rom: Frozen...anything is better than stock Froyo, but this is just AMAZING). But I was having some troubles with receiving incoming calls. Caller always got "All circuits busy" Or "cannot complete call as dialed".
Soooo, I wiped and reflashed. Tried to make a call (before restoring titanium backups) it worked, but my girl was still having troubles calling me...
So I restored most of my titanium backup (stuff that mattered?) and when trying to call out, I get "com.android.phone stopped working" and had to forcibly close it. So, I specifically restored phone 1.0 and contacts and all that from my titanium Backup, and still got the same issue. I am currently backing up stuff to my computer off the phone, going to format the card and do a fresh flash and see if that helps.
Thing to note, my account IS linked with Google Voice. Could that be an issue? And if not, is anyone else having this issue? Seriously the ONLY problem I am having with this rom. Thanks, guys!
Edit. Wipe and reflash did not help, however the phone is running MUCH better! Still not getting phone calls, though. Data works, MMS, etc, spotty 3G acceptance, though. Starting to get a bit aggravating. ANY help would be GRAND.
*sigh* think I got it. Flashed a different modem (EC03?) and it did not work, then flashed BACK to EC05 (AFTER the fresh flash) and it seems to have rectified the issue. HUGE thanks to QBKING77 (if that is his name on here) for the AWESOME video tuts and great linking to the site. I will update if call status changes. But I would still be interested in knowing if anyone else was having the same issues?
Sorry no one ever got to you for help. The Q&A section doesn't exactly have dedicatedhelpers. =/
I'll be trying to help this section more. So please do update if it comes again.
Sent from my Epix 4G using XDA
Shoulon said:
Sorry no one ever got to you for help. The Q&A section doesn't exactly have dedicatedhelpers. =/
I'll be trying to help this section more. So please do update if it comes again.
Sent from my Epix 4G using XDA
Click to expand...
Click to collapse
No worries. My girl and I gave it another go this morning, and all went well. Also received all my calld last night with no issue. Definitely made my girl a happy camper. Lol. Now I just have to calibrate my battery when I get to work, and all will be golden!
Sent from my SPH-D700 using XDA Premium App
the only thing I could think of is did you "freeze" any apps in titanium LOL yes I froze the wrong thing once and got the same error's I think it was the voice mail stuff seeing i went to gvoice didn't think I needed it but I did.
Nope. All apps were left unfrozen, just because I am too n00b for that chit, lol.
However, I flashed the EC05, and all incoming calls (90%) seem to be coming to me. Odd part is, it SHOULD be going to my voicemail if it cannot be dialed. I am thinkin Sprint is to blame, and I need to have it out with them.
*sigh*
Oh well, everything else is tits... Just waiting EAGERLY for 1.2... Chompin at the bit and all that!
Might get bored tonight and flash back to stock... see if I have the same problem.
Question. Let's say I want to "image" my phone the way it is right now (kinda like Norton Ghost used to do?) Flash back to stock, yadda yadda... Is there a way to RESTORE my phone as is (every byte) back with clockwork? Or is that what Nandroid does? Because if I flash back to Stock, play for a bit (see if it is sprint's fault) and want to flash back, I will have to reconvert back to EXT4... using clockwork 3.0, should I just use the .zip (.img?) that nandroid creates instead of the base ROM?
If any of that makes sense, kudos will be given for a clear answer, lol
just loaded Emerald Envy 2.0....
Absolutely love the ROM, but I can no longer receive calls. I've tried the wipe (x3), re-downloaded the ROM, no joy. no combination that I can think of. Have tried all the latest modems (EC05/EF02), no joy.
I did notice that the phone log does log that a call was received, but it never rings or brings up the phone application.
I also tried flashing the Genocide 1.1 kernal. no joy.
I'm about to go back to my Midnight ROM that I Nandroid'd earlier today before I started down this road. Really hope I don't have to, i'm hooked on this ROM!
Any help would be greatly appreciated!
-Todd
Sully1965 said:
Absolutely love the ROM, but I can no longer receive calls. I've tried the wipe (x3), re-downloaded the ROM, no joy. no combination that I can think of. Have tried all the latest modems (EC05/EF02), no joy.
I did notice that the phone log does log that a call was received, but it never rings or brings up the phone application.
I also tried flashing the Genocide 1.1 kernal. no joy.
I'm about to go back to my Midnight ROM that I Nandroid'd earlier today before I started down this road. Really hope I don't have to, i'm hooked on this ROM!
Any help would be greatly appreciated!
-Todd
Click to expand...
Click to collapse
My errors seem to be different than yours. Mine would not show up in my call log at all, nor would the calls go to voicemail. Are your callers able to leave messages?
Mine turned out to be a sprint/phone issue. Their networks have been all kinds of crappy in my area since january. Sucks, but all I could do was call, complain, and get credits.
My new epic seems to be working fine, and sprint seems to have fixed their issues in my area. I was running 1.2 up until last night with no issues callin/receiving. I only updated to the latest GB leak because it is hella stable and netflix works. Just seems to have some 3d issues. But I do not game much on here.
Keep troubleshooting, and give 1.2 a whirl. While your problem is not ROM related, I am very confident your experience (and battery) will be much better.
Oh. And call Sprint. Complain and whine. You will get credit on your bill. Lol.
Sent from my Epic. Which is better than yours.
Ok, so ive been running SkyRaider Zues for a good while, and i came to a snag, everytime i get a MMS video and trie to watch it, i can never see the video. i switch over to CM7 and MIUI and it works in both ROMs. i even switched to MikRunny and it does the same. is this just a Sense thing? can any one help
anyone please?
Zeus problems
not sure. I've been running Zeus since the preview, i've not experienced those issues. have you been to the Bamf forums directly?
I run Mik and i get MMS without any problem. Of course, I have not tried it receiving video, but I do have problems receiving voice messages done trough MMS. It's weird. Do you have this problem as well?
Long time fan; first time post.
I was hoping this posting had provided a solution, but the 'Contacts Fix' did not help with my apparent issue:
(Synergy ROM) Phone app now not working?
I'm lovin' the Synergy ROM, however every time I start up the phone, I always get the 'com.android.phone has stopped' error.
Please, would anyone like to take a look at the Logcats provided?
Attached in the zip file are two logcats. One records my attempt to make a phone call; the other I hope reflects what's happening when the phone is starting up: AttemptedPhoneCall.txt & StartingUpPhone.txt
Sure, I could go back to my High On Android ROM (Have to give a nod to its author, Max of GalaxyS3root.com), but it was Max that raved about Synergy in the first place, and it has grown on me.
Despite the fact I can't send or receive any calls. I can text and surf, but it's not a phone anymore.
I never received that error on Synergy, but I have seen it on other ROMs. Have you tried a full wipe and reflash? In my experience, flashing Synergy worked best when I flashed it from another TW based ROM.
You could try a different kernel such as ktoonsez kernel. I had a lot of issues with the standard ziggy kernel when I used synergy
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Will do
altrikdout21 said:
I never received that error on Synergy, but I have seen it on other ROMs. Have you tried a full wipe and reflash? In my experience, flashing Synergy worked best when I flashed it from another TW based ROM.
Click to expand...
Click to collapse
Thanks, altrikdout21.
Yes, I intend to. I was just curious if there were some developers out there that like to look at logcats for kicks.
Didn't think of that.
Domoo said:
You could try a different kernel such as ktoonsez kernel. I had a lot of issues with the standard ziggy kernel when I used synergy
Click to expand...
Click to collapse
Problems with the ziggy, uh?
Ok, I'll try another and let you know.
Thanks, Domoo.
Got it working...almost sort ya.
Restored my last ROM, HighOnAndroid. I did do the reflash of Synergy with a stock kernel, but there was no improvement, and so I restored my previous ROM. I can now start up the phone without the 'com.android.phone has stopped' error. However, there's a problem. I still can't make a phone call! Yikes! Now how can that be??? I did a ROM restore. Shouldn't the phone app be back as it was? It appears all the other apps are working. I can text, surf, etc. What's happening here?
I start up the phone app, select a contact, press the phone icon on the contact's screen, it comes up like it's going to initiate a call but then I see the 'end call' just as fast and the phone app then retreats back to the previous screen listing the contact I had selected to call.
As an aside, is there a place to drop off you logcats on this forum? Being an old VB programmer (what's that you ask?!), I'm curious to see what these new fangled 'android programmers' can do. However, now I'm ever more anxious to find out what's wrong with the phone app since I've restored my ROM only to find the one lone thing I do use regularly (it's a phone for pete sake!) is still not working.
Ive looked everywhere for a solution but cant seem to find one. My N7, currently running CM11, will randomly reboot for seemingly no reason. Sometimes i can go a day or two and nothing but just when i get comfortable, BLAM! Im not particularly worried just frustrated. I dont know what to do and I have read that its sort of common whether stock or custom(ROM). Im debating on trying to revert to stock because i cant seem to remember having this problem before CM, but i really cant be sure. Id rather not revert to stock if im just gonna have this issue but if it seems to work for others then id just go stock. Anyway I guess im saying that I need some advice here on what others experienced or think. Has reverting to stock worked for anyone else? Any other advice/insight would be greatly appreaciated!
-Thanks
The fix is coming, when Google releases Android 4.4.3, by the end of the month.. Sit tight
--=={BSnapp} ==--
My stock N7 reboots randomly from time to time. It might go a week or more then reboot twice in one day. No apparent pattern to it.
Sent from my BN Nook HD using XDA Free mobile app
I am experiencing precisely the same issue described in the OP. So I am also pretty interested in knowing if there's a fix.
@BSnapp, how can you be so sure of that upcoming fix? Is there a known issue with 4.4.2 for the N7 that was resolved for the next version? Any sources worth mentioning?
Thanks.
It's all over the Android news sites that Google is including a fix for the random reboot, plus several other fixes.. Just Google Android 4.4.3 update, and you will find the answers you seek...
--=={BSnapp} ==--