back to OTA or ??? - Droid Eris Android Development

filks, having major issues, third eris with this same issue. any BT audio plays HORRIBLY, sounds like a compression/buffer issue, tried with 1.40, 1.41, 1.42 radios, and tried multiple roms, evil, senseable, etc, all of them repeat this issue. my Original load didn't have this problem so I'm considering going back to OFW, if I could find out how to do it (download the 2.1 OTA)

Related

Rogers HTC Dream issues

My girlfriend has the Rogers HTC Dream, while I have the T-Mobile G1.
I was able to properly root both phones (although I had mine longer) and I have tried several different roms on both. When we were both running TheOfficial Rogers 1.8.4 and I think 1.9.1, everything was ok. TheOfficial AOSP 1.6 came out, so I took the plunge and tested it on my phone. It was fine.
She kept complaining that her phone was slow and non responsive at times, and indeed it was. I tried flashing the same TheOfficial AOSP 1.6 on her phone and did a wipe. I believe her phone was still non responsive at times, although I can't seem to remember exactly what it was this time.
I then proceeded to install the latest Cyanogen because I was curious and hoping that it could resolve the problems. -My amnesia kicking in again.. wtf?-
I decided to go back to TheOfficial AOSP 1.6. I do the wipe, flash the base rom, then the expansion, then reboot. On first boot, it connects to the GPRS fine. Connecting to the internet will cause the phone to hang. Only way to use the phone is keep it from connecting to 3G/Edge. If I reboot the phone, sometimes it gets stuck on the Rogers screen. When it does boot, it won't connect to GPRS. The only way to use her phone is to wipe and do a fresh flash. Then I won't be able to reboot or else I have to flash again. I have reflashed and rewiped this rom several times already and it's the same.
Anyone know the reason why? I have the correct radio and spl flashed. I have no idea why this is happening. I have flashed my T-Mobile G1 many, many times and, well.. she's using it now. I'm going to try Dwang's rom to see if the same thing happens.
So far it worked. I'm not getting any force closes. I can't figure out why I can't install TheOfficial Donut AOSP on this phone. Dwang's rom doesn't come with terminal or maps. I'm not sure if it's supposed to be like that. I tried the Google Navigation update mod and for some reason that just restored the normal Google Maps on her phone. I'll try it on my own phone later. I'll just leave it at that and won't update anymore unless someone can figure out for me how to install TheOfficial Donut AOSP.
Bye.
Hate to ask you something you might have answered, but are you sure that you have used the EBI1 radio image on the Rogers Dream?

[Q] ROMs work great, except...?

Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
JustinHTC said:
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
Click to expand...
Click to collapse
Sounds like a dying battery to me.
It worked fine in the original Windows though so that's why I am a bit baffled.
what happens if you put your device in bootloader and try to flash to stock? Error 262 is a connection error. basically happens whenever some event interrupts the flashing process (a dead battery will cause this). If you haven't yet, try to flash to stock via the method in this post (bootloader and then flash)
Tried that, didn't work. Just gets to 31% and pops 262 no matter how I try to do it.
The odd thing is though that I can flash any other ROM just fine.
Would reformatting the SD card work?
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
JustinHTC said:
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
Click to expand...
Click to collapse
0.41 was reportedly having tons of issues, you should have started from there
Glad you got it working.

[Q] my A500 got some problems, help !

before this , my a500 is on HC 3.2. because of HC 3.2 doesnt have root access yet , so i downgraded it to 3.0.1 using this and update to 3.1..
and because of that , my media directory can't be played by default music player or any media apps and my pics can't be displayed at gallery. But the media file is still intact in my storage. what happened ?
and it kept showing my "Maps" has stopped unexpectedly , i never used that app ! T.T
Are you still on the unstable 3.0.1 that you downgraded to, or did you flash a new rom? If you're still on 3.0.1 with root, then flash a new custom rom and see if that fixes your issues. If you're still experiencing random force closes, I'd try reflashing the rom. Had to flash mine three times before everything got ironed out.
Still new at this myself, but hope that helps...
Since you downgraded and rooted, I would suggest trying a 3.2 ROM and see if that fixes your problems. Sounds like your ROM is in an unstable state. Also as smhism stated, sometimes you have to try more than once to get everything working. Also make sure you follow all the steps carefully in CWM so that you wipe everything before upgrading and installing new ROMS, otherwise you could experience issues like that one.
i'm on 3.1 (stock rom) rooted 4.010.40_COM_GEN1..
i did upgrade it using unstable updates on the link above..
but i guess i dont want to flash some new roms now , coz i got a lot of other things to take care of..
or maybe it can't be played and detected because of i'm updating using unstable updates ?
I would try to do the downgrade to 3.0.1 again and then upgrade to 3.1 once more and see if anything gets changed. Also, did you root 3.0.1 before updating to 3.1?

Sound/Wifi woes

Hello all,
So I've read the threads about the issues with no wifi/sound when people have rooted. I've spent the last 2 days flashing and re-flashing attempting to get these to fix themselves.
I have reflashed, what I believe, is the stock version of 4.2.2 to my sg4 sgh-i337m. After reflashing I noticed I never had wifi. So I reflashed a few times, as others had suggested, but still nothing. I then tried the cm 11 through the windows installer, then I was without sound or wifi. Now when I flash back to stock (maybe I'm not using the original rom?) I don't have sound, or wifi. I tied both CM12.1 optimized and Pacman, and for some reason they get wifi, but still no sound.
Could this be a modem issue?? It's making me crazy. I've reflashed and reflashed my phone with 2 seperate stock roms thinking perhaps I was using the wrong one, but nope. Tried the wipe caches before/after and still nothing.
I have the sg4 sgh-i337m, bought it in Nov 2013. Does anyone know what kernal/broadband we originally use? I lost mine before I had a chance to write it down (kicking myself in the face ever since).
If anyone knows how to fix this - I've tried all the usual fixes (sound about, pulled battery numerous times, multiple reflashes).
Thanks.
http://www.sammobile.com/ has all of our firmware for our phone just make an account and search firmware for your model number and flash threw odin.
i havent heard anything about sound issues i have heard about some wifi. i have the same phone as u and have flashed alost all the roms for it with out issue. maybe its a hardware failure i sure hope not for your case but it might be another problem to look for.

Issues with service on latest radio

So I have flashed multiple roms and I keep getting the same error. I will randomly lose my service after a boot and then a few minutes later the phone will say no sim and reboot itself. This has happened on two different roms (one AOSP based, one CM based.) Both time the roms were clean flashed perfectly. I have been forced to revert back to an earlier radio (from 3.61 to 2.15) just to keep my service. Has anyone else had this issue and is there any fix for it?
when did it start? because we have been on the 3.61 radio for about 2-3 updates already..
(cant remember exact date, would have to check my factory images to determine )
messiahfreedom said:
So I have flashed multiple roms and I keep getting the same error. I will randomly lose my service after a boot and then a few minutes later the phone will say no sim and reboot itself. This has happened on two different roms (one AOSP based, one CM based.) Both time the roms were clean flashed perfectly. I have been forced to revert back to an earlier radio (from 3.61 to 2.15) just to keep my service. Has anyone else had this issue and is there any fix for it?
Click to expand...
Click to collapse
The latest Radio doesn't assure a benefit for everyone, and might not be suitable for your region. In my case it has boosted my reception, but that might not be the case for you. So, just roll back to a previous radio that offers better compatibility.

Categories

Resources