I am having some trouble getting the camera working on a mytouch3g I have been working on. I have Engineering SPL 1.33.2004 installed with CM-recovery 1.4 installed. Have tried several 32B roms but always get a force close. Have wiped, restored nandroid backup, used clean sd, and even tried pushing the stock camera and 3rd party camera apps. Is there something I'm missing? I have rooted a few Dreams, but this is the first Sapphire I have dealt with. Any suggestions?
try flashing the stock mytouch rom. its on here some where. if that works then just try a cyanogen rom. i refer the 4.0.4 rom. if this works then you had corrupt files on dl. if this is the case then try using a dif os. if continues then your sd and or file reader is trying to filter content. so use something else. let me know. rockin...
Thanks for the reply. I have tried cm 4.0.4 as well as several of the 32B roms from the Sapphire board. In fact 4.0.4 is what I flashed it to as soon as I finished the rooting process the first time. The camera worked fine that night, but has since crapped out. None combo of roms/spl/radio seem to do any good. Even wiped, and unrooted w/ sappimg.nbh and started over a time or two. Then I read earlier someone on the Dream board had a similar problem, and fixed it by re-formatting SD. So I gave that a shot (even used a different SD that is known to work fine) but still no luck.
So now I have put the phone back to stock. I figured since every partition we change by rooting has been wiped and rewirtten to it's original state, it's best to just call it a hardware issue & have t-mo swap it out. I don't see anyone else having these kind of issues on here. So I'm thinking this phone must have met the floor somewhere between the time I flashed it and the time camera issues started. Nothing else can seem to explain it. Hopefully I'll have better luck with the next one.
gurnted said:
Thanks for the reply. I have tried cm 4.0.4 as well as several of the 32B roms from the Sapphire board. In fact 4.0.4 is what I flashed it to as soon as I finished the rooting process the first time. The camera worked fine that night, but has since crapped out. None combo of roms/spl/radio seem to do any good. Even wiped, and unrooted w/ sappimg.nbh and started over a time or two. Then I read earlier someone on the Dream board had a similar problem, and fixed it by re-formatting SD. So I gave that a shot (even used a different SD that is known to work fine) but still no luck.
So now I have put the phone back to stock. I figured since every partition we change by rooting has been wiped and rewirtten to it's original state, it's best to just call it a hardware issue & have t-mo swap it out. I don't see anyone else having these kind of issues on here. So I'm thinking this phone must have met the floor somewhere between the time I flashed it and the time camera issues started. Nothing else can seem to explain it. Hopefully I'll have better luck with the next one.
Click to expand...
Click to collapse
Hate to say bro, but ya has to be hardware. Everyone has messed with cam software and had success. So you have done right and reverted to stock. Send that bad boy back and get a newer exchange. Sadly to say my orig. spl was broke and had to send back. I tried talkin tmobile service techs thru the steps but they only were like "ahhhh ummm" lol. do the dew and get a newer hardware softer g2. fosho. . . . .
Yeah that's what I figured. At least the folks at t-mobile didn't give much hassle. It was within the 14 days so they were pretty quick to agree to the swap out. New one will be here next week, and I'll give it another go. Thanks for the help.
camera force close
hey great guys
i have x18i (china clone) mtk 6573 mobile. recently camera is force closing
and its flash is also not working. i tried factory reset also .... fone is rooted
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?
Hi everyone.
Since the time I tried Cyan 5.0.8 for a while my phone started to give me "Wifi could not be activated"-errors. ADB told me that "init-driver" failed, so after a while and a lot more trouble I went back to Super-D. It worked well for a whole lot of time but now I also get these errors on Super-D.
I reflashed radio: nothing got better.
I wiped data, reflashed rom (all that defanged-stuff + the rom): nothing got better.
I tried to take out the battery and everything: nothing got better.
I still cannot enable WiFi. I fear it's a hardware problem, maybe caused by the UV/OC? I had it running for a whole lot of time stable at 650Mhz. It's really weired, I hate my Dream now =(.
Anyone has an idea how to get it up running again?
Update: I just tried to start tethering via WiFi. It works!? WTF? What is my Dream doing!? So after stoping tethering and everything's fine again Ô.Ô. Could anyone try to explain what happened? Me Have No Clue =(
This doesn't belong here, but my lack of writing stuff prevents me from posting this where it is supposed to be
If possible, move this post into this thread: http://forum.xda-developers.com/showthread.php?t=1115958
So. JV5/JV9/JVO builds from kitchen with CF and HC kernels cause soft-reboots on my SGS I9000. I tested all of them by now. Tried the Talon Kernel 0.2.1 with JV5 and JV9, which caused boot-looping.
So I kept reading and found out that I was not the only one having this problem, but it seemed to be solveable by flashing a stock JVO first.
I already had Gingerbread Bootloaders, flashed JVK a while back, so I tried a few no-wipe ROMs as I mentioned above. All with the same problem. I lost connection to my cell network and it didn't come back. Somehow connected to the WiFi, I suppose. I could reproduce it by getting a GPS fix. But that was more or less related to my phone using wireless networks for positioning, which means that it switches on WiFi for just a second but without telling me.
Anyways, I thought I might have been wrong about the bootloaders being the reason to flash the stock firmware, so I did as it said: it specifically said JVO+ in the tutorial, so I went through the hassle and did the following:
- Flash an entire JVO firmware
- Reboot
(that one took a while)
- Full factory reset via dialer code
(that one took a while, too)
- reboot again, this time into bootloader, to flash a hc-speedmod kernel, to have root access and CWM
- reboot again, into CWM, to flash one of the ROMs I tried earlier
I ran back into my old trouble. So this is not an issue of the GB bootloaders or a previously installed version. The phone keeps soft-rebooting.
I re-installed the stock JVO firmware and flashed the speedmod kernel again, rooted via CWM menu and now I am just recovering my important applications via Titanium. Nothing bad happened yet, and it would have, with any of the kitchen ROMs Trust my, I almost tried them all
Nobody else wrote anything on that, so I thought I'd let you know there's no need to wipe all your data (like I did) and hope for the soft-reboots to be gone.
There's something seriously wrong there.
Anybody else having the same issues?
Cheers.
Andreas
Yep, I had a whole lot of trouble with the Kitchen JV5 release yesterday, ended up giving up and goind back to Darky's 10.1. Mine would boot, and when doing a media scan, would soft reset itself. I could get it to work eventually by powering down before media scanner completed then powering up. Bit odd - tried three builds of JV5 with different kernels but they ended up all being screwy. Ah well, will see what JVP brings...
glad to hear that I'm not the only one crazy enough to wipe his entire phone for a new (and fast) operating system.
Anyways... I am now back to my old status. Re-installed most of my apps, sync behavior, BT devices, wireless APs, etc. blayallah...
JVO with a hc speedmod kernel is by far the best and fastest ROM I have run so far.
Kitchen builds are dead to me until some of the people who ran into the same problems as I did confirm that those issues have been dealt with.
Just for your information:
- battery life seems amazing, at least regarding to the sensor. Hope it's any accurate. Had it unplugged over night and lost 22% battery life with WiFi on in a bit more than 10 hours
- it responds VERY fast, compared to any other ROM I had before
- bluetooth devices have to be set up again, for some reason my phone doesn't like my headset any longer. I can hear people talk but they can't hear me. However, the microphone does work when I use my headset for text2speech. Weird.
Anything else seems just the way it was before. Just faster.
I'd be glad to hear if someone could still help me out with the soft-reboots, if somebody else decides to use the kitchen builds either way I won't until somebody else tells me it's working now
Andreas
Why would u need to SOFT reboot ?
I don't *need* to soft-reboot. It just does that. Modem crashes, lost network connection. The phone doesn't actually entirely crash, it just restarts the network service and your phone is going to be offline.
That's a soft-reboot. No entire system crash or kernel panic, just the modem crashing.
That does happen when things are messed up
I'm having the same issue: on a JV5 and JV9 RomKitchen build with a JVO modem, as soon as I get a GPS lock, the phone soft-reboots.
paour said:
I'm having the same issue: on a JV5 and JV9 RomKitchen build with a JVO modem, as soon as I get a GPS lock, the phone soft-reboots.
Click to expand...
Click to collapse
guys, why dont you try the JVP v7 builds, its much better.
also, please select the default boot animation, else it will go into bootloop.
I can confirms that doing a no-wipe upgrade to JVP v7 fixed this soft-reboot issue.
Thank you for that information. I'm not in a flashing mood right now JVO is running just fine right now. Anything about JVP v7 that's worth the try?
JVO is running fine for now. So I'm not feeling like flashing everything over again.
Is there a simple way to just dump my current phone status, its ROM and everything somewhere to my harddrive and re-flash all of that over in case anything goes wrong?
andreas1979 said:
Thank you for that information. I'm not in a flashing mood right now JVO is running just fine right now. Anything about JVP v7 that's worth the try?
JVO is running fine for now. So I'm not feeling like flashing everything over again.
Is there a simple way to just dump my current phone status, its ROM and everything somewhere to my harddrive and re-flash all of that over in case anything goes wrong?
Click to expand...
Click to collapse
its pretty much the same stuff except very good speed optimizations, 2.3.4, and few UI tweaks.
its been the same since the first gingerbread leaks. we flash it for new builds dont we
...and now it's just pissing me off. JV9 Kitchen Build. On GPS Lock I get soft reboots. What the hell?!
Trying another one now... crap. I thought That would be fixed by now.
So. Kept me busy, just to be sure: Each and every combination I tried using 2.3.3 from the kitchen caused soft-reboots on GPS fix. The phone was very fast with the Talon Kernel and Ext4 FS, but I can't live without GPS
So I tried a non-wipe install over one of the not working 2.3.3 roms.
I'm on JVP now, not as fast as Talon, so it seems, but GPS works, getting a fix at my window within 5-10 seconds, no crashes whatsoever.
So. If anybody else experiences crashes like the ones I mentioned in the opening post, I can also confirm that the JVP ROMs seem to fix the problem.
Andreas
...as much as I hate talking to myself, it's still regarding the same issue, so I have to ask:
Saw the new kitchen build (JVR).
Two questions:
1. Is the soft-reboot issue finally fixed?
2. Is there a little language-switcher-button on the bottom left of the swype keyboard?
I use the JVO swype, and it has that button, and the new ones don't seem to have it any more? It's really nice if you need to switch between two languages all the time and you don't want to go into settings every time you need to switch.
Anyone know that? http://t1.gstatic.com/images?q=tbn:ANd9GcQC6orm5ZMAju2VzczB3MCbwEPeSH9yrYI6wxfdDGFCvkdpe7lQRg <- that one right here has it. Took me a long time to find that, because no swype version but JVO seems to have that feature.
I'd be glad about any answers to those two questions.
Andreas
andreas1979 said:
...as much as I hate talking to myself, it's still regarding the same issue, so I have to ask:
Saw the new kitchen build (JVR).
Two questions:
1. Is the soft-reboot issue finally fixed?
2. Is there a little language-switcher-button on the bottom left of the swype keyboard?
I use the JVO swype, and it has that button, and the new ones don't seem to have it any more? It's really nice if you need to switch between two languages all the time and you don't want to go into settings every time you need to switch.
Anyone know that? http://t1.gstatic.com/images?q=tbn:ANd9GcQC6orm5ZMAju2VzczB3MCbwEPeSH9yrYI6wxfdDGFCvkdpe7lQRg <- that one right here has it. Took me a long time to find that, because no swype version but JVO seems to have that feature.
I'd be glad about any answers to those two questions.
Andreas
Click to expand...
Click to collapse
I have tried the JVR base available in the kitchen---nothing to write home about,went back to STOCK--far better!I imagine the Kitchen as we used to know and use way back is now a thing of the past and the last nail was Tricky also leaving...
andreas1979 said:
glad to hear that I'm not the only one crazy enough to wipe his entire phone for a new (and fast) operating system.
Andreas
Click to expand...
Click to collapse
Guess that makes me crazy too
I've also been tinkering with customising ROM's myself to get to the boot-loop - getting pretty proficient at it now (guess I should read up a little more first)
Hello everybody,
I'm relatively new to the world of ROMs and I'm hoping some people smarter than me can help.
A few weeks ago, I started having issues with my phone, on the stock ROM for Wind Canada, restarting continuously. It would sometimes work for up to 10 hours, but sometimes no longer than 10 seconds. There didn't seem any rhyme or reason to it doing so. I figured that it was a good time to play around with a new ROM, and I took a backup (of a faulty operating system). It's been a bit of a ****show since then, and I don't remember exactly everything that I've tried, but here is a sampling:
CM13.1 - the ROM successfully loads, but then I get stuck in a reboot loop.
CM12.1 - I figured that if 13.1 didn't work, I shouldn't try 14.1, so I went down to 12.1. This worked beautifully, until I tried to make a call - and I can't hang up. To hang up, I need to reboot the phone. Annoying, to say the least. Everything else seems to work really well, other than a slightly shortened battery life, but I can live with that, if everything else works.
CM14.1 - I tried loading it, but it says right off the bat that the L03 isn't part of the compatible list and doesn't process. I know I can suppress that message, but I figured that if it was meant to be on that list, it would be.
Resurrection 5.1 - I don't remember what happened here, but I think it ended up in a bootloop.
I can't find the original ROM on Huawei's site, and the one that seem similar for different countries are meant to be done within the OS as an update (Update.app).
So, I'm stuck here - I can't seem to revert back to the original ROM (which was Android 4.4.4, which was fine), and I can't seem to update to any other ROMs. I want to fix this, because as far as I'm concerned, the hardware is pretty good and I can make this phone last. However, my wife is pushing me to replace it...
Does anybody have any advice as to what I should try next? I really don't feel like using CM12.1 in its current state, which is what is installed now, since I need to reboot between phone calls, but it seems to be my only option for now.
Three notes - 1) I am currently on my 5th or so install of CM12.1. I have tried to look for ways to replace the dialer, since that seems to be the problem, but I haven't found a way. Can one replace the stock dialer?
2) I have tried installing multiple GAPPs packages, including ones that supposedly replace the dialer, but this hasn't helped.
3) I don't know if this is relevant, but in CM12.1, under "About phone", my Device model is "unknown". Is that always the case?
Somebody out there must have a better solution and my hair's all gone now, from me pulling it out...
Any help you can give me is appreciated!!!
Thanks,
Steve
UuUuPpPp....
Exactly in the same boat as Steve...... "Cant hang up" is seems to be the only major problem.....i have the exact phone too.....and tried same things too to no help....any help wud be appreciated...