Is anyone else having this problem?
I've got a Rogers HTC Magic, and whenever I've tried a ROM with Android 1.6 or greater (I've tried 3 or 4) the accessing the camera will cause the phone to reboot itself.
It doesn't happen the first time I use the camera, but it does the second time and consistantly.
Does anyone else have this problem?
1.5 ROMs are fine. I'm currently using cursorsense and it's not an issue but at some point I will want to use a newer version of Android.
I have the same problem :x
Relash the rom. If you are using any of the legal roms (cyanogen/superd) flash the base before the rom. remember to wipe before starting.
I've tried cyanogen 2.1 test2 and Smoki both causes reboot when using camera apps (barcode scanner, google goggles, fxcamera, ...).
It doesn't reboot always tho like 1/3 times i use one of these apps i get a black screen and then a reboot.
Im using CursorSense now and all the camera apps work just fine :s.
Always did a wipe before flashing the roms.
Known issue. Been dealing wirh this for a long time on my Rogers Magic. I think the trouble is the devs dont have this model, and no one has submitted useful logs. http://code.google.com/p/cyanogenmod/issues/detail?id=792
Related
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! When running ROMs that are "newer" such as 2.2 ROMs they crash/freeze for no apparent reason. With or without an SD card in, everything wiped, newly updated recovery etc etc.
However! When i run a ROM like Kimera 1.8 Cupcake ROM it all floats on perfectly.
I cant see any rhyme nor reason behind the problems im experiencing. Any thoughts? It's really killing me :/
Could you define "crash/freeze" a bit more specific please? Does the phone boot up as normal?
If it just hangs on randomly when using the phone normally, it might be a ROM specific problem (not neccesary 2.2), maybe some app who can't handle 2.2 just yet, or you configured it badly (overclocking?).
As riemervdzee says, more information required.
What ROM are you trying? What radio? What CPU settings if available?
I tried SenseHero (2.1), Froyos and currently running Fusion!ROM 2.2 and they all run perfectly on my G2 Touch (Hero)
It boots up perfectly but then either reboots after random use or just freezes in the sense that i use some app or scroll through the app list or try to make a call and it simply freezes up and is unusable until i remove the battery and reboot.
I am running FROYO_2.2.1_Special_Edition_RC1_update1 and as far as i can think of i haven't configured it anything specific. Is there perhaps a way to reset every setting such as CPU setting etc that might be wonky?
Im running 63.18.55.06PU_6.35.15.14 Radio!
lol i love you're definition of "newer roms" when you've only used 1 rom.
first i'd recommend trying some others. i'm not saying the one you tried is bad at all but it may just not agree with your phone for some reason.
Having said that - if I were you i'd check exactly what you're wiping - it sounds to be that you haven't cleared the dalvik cache or something (i.e. you've not done a full wipe before flashing a new rom).
My new bie guide has the process for flashing a new rom (part 2 i think).
I've run a myriad of roms, im just stating that this is the one im currently running and experiencing problems with.
kloggeboll said:
I've run a myriad of roms, im just stating that this is the one im currently running and experiencing problems with.
Click to expand...
Click to collapse
What exactly is the problem of running an other 2.2 ROM? It could be a ROM specific problem, which frankly occurs at your phone (egh, sometimes happens ).
If you are sure you wiped data, dalvik, cache and ext2 (if any) I really suggest you move to another ROM and see if that one works OK.
I experience exactly the same problem with every 2.1 and 2.2 ROM so i doubt its ROM specific. I've wiped everything. Im quite clueless in this case what the problem might be!
I recently flashed Myns Rom to get the latest radio, prl, etc. Afterward I re-installed CM6.1.1 and noticed my camera didn't work. Just a black screen when launched, then force close. I tried a MIUI Rom too, same story.
Here is what I updated - http://www.mediafire.com/file/9a1ju....00.11.19_WiMAX_27167_R01_PRI_NV_1.90_003.zip
After being frustrated and only being able to use camera with a Sense rom, I decided to revert back to the previous radio.
http://www.mediafire.com/file/jyedjkp1bm5amwm/EVO_Radio_2.15.00.09.01.zip
Once i did this, I was able to use the camera now with CM6. haven't tried a MIUI rom yet, but I assume the same results.
I hope this is clear, with caffeine involved, my thought to type ratio is 11.5:1
Edit: Do a battery pull after your first boot into ROM. This seems to help too.
More information now
Install a sense ROM, update PRL. According to Sprint Customer Service, they have had people call in with this camera problem and have walked people through the PRL update. This then also makes your camera work again. After the update, you can flash an AOSP rom.
I have had issues with some of the latest releases of MIUI and the camera. The camera issue I described above happened again after flashing MIUI. There are atleast 3 instances where this issue occurred. Not pointing blame, just describing what I have done to recreate and attempt to solve problem.
I have the same problem. CM 6.1.3 would be my daily driver if I could figure out how to get the camera to work. When do you flash this? before installing cm or after?
I flashed and still no luck. I have the 003 hardware with the 2.02 hboot not sure if I have the new camera
soxfan81 said:
I have the same problem. CM 6.1.3 would be my daily driver if I could figure out how to get the camera to work. When do you flash this? before installing cm or after?
I flashed and still no luck. I have the 003 hardware with the 2.02 hboot not sure if I have the new camera
Click to expand...
Click to collapse
You want to flash the radio after you have installed the ROM. It will reboot back into recovery and complete install. After doing all of of this, let phone reboot, then power off, pull battery and put back in. Then power on.
I hope this helps. I have been able to use my camera with no problems since the battery pull. I believe the new camera came with hardware 004.
Thanks.
Just wanted to say thanks for posting this thread.
Was searching the internet for a way to fix my blank screen camera for weeks and this radio downgrade did the trick! Thanks for finally putting my insanity to rest!
I am writing on this thread as i still cannot add to the development thread yet
I am using Elelinux-7.0.0-Hero-v2.0. Thanks Ele for a great rom.
So far the only problem i have had is once the unlock screen went invisible on me.
I had to use the patch which worked fine. no black screen. everything else works great so far.
Just trying to contribute to the developers what i can to help.
Any one else has any issue yet.
Elelinux-7.0.0-Hero-v2.0
RADIO VERSION:63.18.55.06SU_6.35.17.03
Kernel: Herokernel-12a
I've had the same issue with the lockscreen but like yourself it was a once off.
Generally the ROM is great (however, this is the first ROM that I've flashed to my hero)
The only other issue im getting is with linking facebook with my contacts; for some reason FB keeps crashing. But keep in mind that I'm a retard in comparison to what you lads know about custom roms etc..... but slowly learning!
Sent from my Hero using XDA App
same problems
I have had the same problems as you. lock screen went invisible a couple of times. and my facebook does not work quite right.
Apart from that has been very stable. no problems or reboots. works great.
Running gingerbread with honeycomb theme on my hero. running at 691mhz is well good.
I have got widgets running on every screen to.
Elelinux RC4 version 7.0 V2.0
kernel 12a
691mhz
clockworkmod.
Thanks Ele for a great rom
After installed 2.0 patch, I still get blank screen (wall paper ok, no any widgets).
The only way to solve is restart
Any thing wrong with my installation? (same spec as above post)
The Bug seems to affect some phones and not others. Might be due to different hardware but not sure.
I am a network engineer. Not a developer.
There is a patch that fixes the black screen bug which might help. You might have to delete dalvik cache first though. But as said not a developer.
I just wanted to try some different roms and loaded cronos rom yesterday and is very good. So running that at the moment.
It is really fast and stable. The fastest i have used so far. But i have not tested everything yet like GPS. But admit i am becoming a cronos fan.
Cheers.
P.s i always backup my phone first and do a complete wipe before trying a new rom. Otherwise could get problems.
I use clockwork mod.
Unfortunately the bug your getting with black screens, invisible menus etc.. is an aosp bug that affects some devices which Google are unable to fix, if you had read through the thread you would have seen this. Ele is working hard on a fix for this but as CM no longer support the hero, its unlikely many cm7 roms will see many updates.
Sent from my HTC Hero using XDA App
Everyone is hoping that Google will fix the memleak and invisible manus problem. To fix it, one needs to undersatand the big picture on how these things are managed. I think it can be done only by experienced coder.
It's a real shame. i love gingerbread and did not want to go back to 2.1 or 2.2.
But might have to if they do not fix it.
I know Ele is working hard on a fix. using his rom at the moment. Was using cronos. But suddenly started getting random reboots and battery started only lasting a few hours and could not find out why.
Thanks to all devs and help.
Elelinux 7.0 v2.1 GPS reboot issue
Hi all,
I found Elelinux 7.0 v2.1 to be almost perfect.
The only major issue so far for me is that when running applications such as sportstracker that use GPS and are running in the background, that as soon as the GPS connection is lost (for whatever reason) the phone always seems to crash.
I wonder whether anyone else has seen this issue and whether there's a way to investigate it.
E.g. is it possible ot redirect logcat to the sdcard and then analyze the log file?
Regards,
MJ
Her0 V2.1 - USB problem
This is a weird one...
I flashed to Elelinux 's fab 2.1 the usual way....
I booted into the ClockworkMod Recovery V2.5.0.7
-- wipe cache partition
-- Advanced - Wipe Dalvik Cache
-- reboot
Then again within Clockwork Recovery I choose 'Install zip from sdcard'
I select the Hero rom and it flashes perfectly...
Now the problem ----> I cant get the usb port working to enable transfer of files?
When the phone boots up it shows 'preparing sd card'
Then when i connect usb lead to pc it shows 'usb connected'
When i then pull the screen down, i see 'usb connected - select to copy files to/from your computer'
When i select that tab, it just crashes back to the home page?
I see the icon at the top of the screen but when i pull down the screen and select as above, it crashes back to home screen again?
In settings, i have both USB debugging and USB debugging notify - all enabled.
Can anyone provide a solution to this issue for me..
thank you
The only way around this problem i think is to mount usb storage from recovery.
Sent from my HTC Hero using XDA App
I have been searching all over for answers, but have not found any solid solutions. There was another case similar to mine, HERE but I really don't think things are quite the same. I am new to flashing with HD2, but am very seasoned with the Samsung Vibrant.
I had the phone app crashing and robot voice for a while. I have done all of the supposed fixes but nothing has worked yet. I bought my HD2 second hand, (like the big screen and more RAM better than on my TMO vibrant), but when I got it it was in great condition, completely stock. So I wanted to put android on it because MinMo is (for my concerns) unusable. SO, here is what I have done.
Started with a TMO(US) HD2 Stock
-Flashed New Radio from 2.14.50.02 to 2.15.50.14
-Flashed HD2O WM 6.5 ROM (Phone Worked fine, but decided WinMo sucks)
-Flashed MagLDR
-Flashed CWM
-FLashed BOYPPC SHIFT PDA sense&HOneycomb (FAST!)
But then whenever I tried to make phone calls I get the robot voice and three seconds later, crash. (the process phone in com.android.phone is not responding...)
-The first fix I tried was HERE for the Low volume fix. No Dice...
-Then I Tried this Volume Fix HERE, but did not fix problem.
-I tried disabling the contact sync, seen in another thread, and still nothing.
-Went into Rom Manager, Flashed Clockwork recovery, then used it to "fix Permissions"
-During the permission fixing, I received a normal clear phone call with no FC.
-Then after call it said that it was done with permissions, and asked me to restart.
-After the reboot it would just constantly Force Close every five seconds, and it was not showing any network signal.
So Then I:
-Flashed a new Radio. -2.06.50.04 -TMO US
-Still Not working
-Went back to the MAGLDR and did an AD Hardreset, and tried flashing HYPERDROID.
-Still nothing.
-Reset again and Reflashed BOYPPC SHIFT, (liked it better, I know, a lot of flashes...)
-Now getting network signal, and able to get into the phone program, but as soon as I try to make a call, same problems occur with Robovoice and FC.
Sorry so thorough, but I always feel like more info is better than too little!
I had looked at another thread that said something about wearing out the radio from flashing, but on my vibrant I have flashed over 30 ROMs and 10 or more Kernals, and it still works good, so, I dunno. Kinda stuck.
Got my finger ready for the thanks button for ANY help offered.
Also noticed that now, no sounds are playing at all. Speaker driver error? It worked ok the first time I loaded this rom.
Just installed CMYLXGO's Desire Rom Yesterday and the phone works.
Now running CMY's gingersense streak, which is also a Sense ROM, and it works too. Is there any reason that anyone can think of as to why my phone will only work with sense themes?
i'm having a very similar issue.... i've tried a few roms and i get the same thing. calls go out for a few sec then force close. ppl tell me they can't call me sometimes because of this. i even task 29'd and reflashed everything. radio, magldr, cwm and now hyperdroids latest... still get force close and an unusable phone....
wtf
2.15.50.14
The above is the recommended radio that was a good start. Now the next thing to go under settings --> sound --> Feedback. I forget which one it is that causes the phone to crash/give robot voice but that is most likely what is causing the issue for you guys. I believe non sense builds also have these options if I recall correctly. I use sense builds myself. Also be sure to restart phone after you uncheck the settings under feedback. Phone should work after that and no robot voice.
I dont have robot voice and i'm running that radio. hyperdroid was running fine until recently and i have this problem. i can't get calls it causes the phone app to crash and sometimes calls crash a little bit in.... i've task 29'd and redone a clean install with old known working hyperdroid WITH NOTHING INSTALLED still does it, tried new hyperdroid; same thing...
antiparadigm said:
Just installed CMYLXGO's Desire Rom Yesterday and the phone works.
Now running CMY's gingersense streak, which is also a Sense ROM, and it works too. Is there any reason that anyone can think of as to why my phone will only work with sense themes?
Click to expand...
Click to collapse
you can try cyanogenmod and miui by starting over again but remember to do task29 to be sure that you dont leave any traces of previous installations !
!!
good luck and regards !! !