Related
hi out there, anyone of you facing the camera failure??
i'm currently using RC2, restarted my mobile more than 20 times, changed other ROM still cant make my camera works....
anyone hv solutions on this??
million thanks...
Hmm... do you install the rom through CWM on a proper procedure? Coz i have no problems at all...
Sent from my CSL-MI410 using XDA Premium App
It was fine when i rooted last month, only happened last 2day when i ean to use it
If u could elaborate how u install the RC2, maybe i could help n find the solution for u.... its quite simple actually... sometimes slight mistake in installing, can make it go wrong... i know coz i have been doing it since i got my xperia x8 a year ago... if u cn try to install rc1 first then upgrade to rc2...
Sent from my CSL-MI410 using XDA Premium App
ya, I'm upgrading from rc1 to rc2, as follow the step provided from lyn
blackode said:
If u could elaborate how u install the RC2, maybe i could help n find the solution for u.... its quite simple actually... sometimes slight mistake in installing, can make it go wrong... i know coz i have been doing it since i got my xperia x8 a year ago... if u cn try to install rc1 first then upgrade to rc2...
Sent from my CSL-MI410 using XDA Premium App
Click to expand...
Click to collapse
hi
this is something i have not done u mean
1.flash rc1 via CWM
2.flash rec2 via CWM from rc1
and this would make RC2 work better
i usually have flashed RC2 strait via CWM
kindly explain on the same
works fine with rc2...
sent from my Spice MI-410 XDA Premium
haree said:
hi
this is something i have not done u mean
1.flash rc1 via CWM
2.flash rec2 via CWM from rc1
and this would make RC2 work better
i usually have flashed RC2 strait via CWM
kindly explain on the same
Click to expand...
Click to collapse
flash rc1 via CWM? weird... i flash my rc1 using SUT software as the file was in .nbo then start flashing rc2 via CWM. i wouldnt dare to flash rc2 straight because from my opinion, rc1 is a base firmware and therefore i think its best and play safe to go a long way rather to be sorry.
blackode said:
flash rc1 via CWM? weird... i flash my rc1 using SUT software as the file was in .nbo then start flashing rc2 via CWM. i wouldnt dare to flash rc2 straight because from my opinion, rc1 is a base firmware and therefore i think its best and play safe to go a long way rather to be sorry.
Click to expand...
Click to collapse
install over rc1 only i suffered huge losses due to flashing rc2 over stock rom..
nd by losses i mean
camera dont work fine
fm not working "force close"
facebook not working "essential for me"
and also there are so many system issues as rc2 and stock rom are diffrently build try first rc1 and then upgrade to rc2
hmn.. i tried Cherry Mobile Magnum HD now, still the same, i deleted the stock Camera from root n installed camera360, still cant use, anyone hv stock camera.apk??
Same Here, can somebody help us
Camera suddenly stopped working tried Camera zoom fx, camera 360 etc
Using MIUI
tarunongo said:
Same Here, can somebody help us
Camera suddenly stopped working tried Camera zoom fx, camera 360 etc
Using MIUI
Click to expand...
Click to collapse
if it is MIUI,try freezing Google Talk as in the previous version. I got mine working after doing the same.
I face the same problem camera crashed when i tried to turn the front one on then right after no any camera app can open it and not responding, forceclose all the time. I use ROM CM7.1.0 by Napstar. Help me fix this pls.
Sent from my CSL-MI410 using XDA App
Why Dont You Try Reflashing Stock ROM
pittms said:
I face the same problem camera crashed when i tried to turn the front one on then right after no any camera app can open it and not responding, forceclose all the time. I use ROM CM7.1.0 by Napstar. Help me fix this pls.
Sent from my CSL-MI410 using XDA App
Click to expand...
Click to collapse
It's probably the kernel problem. Just like mine, but I'm using MIUI, MIUI kernel 1.9.30 has the same bug, the latest kernel (1.10.21) fix the camera and work again.
Just like deatbearer said, you've to flash stock ROM or Andro-ID RC2 or MIUI 1.10.21.
Thought a lot about purchasing this mobile as it known having issues with camera, however decided to get it.
Got this phone few hours back, verified at the spice outlet whether camera is working or not, was working there.. Back to office and camera got frozen, showing black screen...
In the mean time, was playing with screen (live wallpapers) and suddenly camera application got invoked (not sure how) & working fine - able to take snaps ... again after 30 mins..i tried camera and again it start showing black screen....
Upgraded to gingerbread from spice site... and camera is good now... not sure how to fix the camera if goes black again & i didn't do anything earlier to fix it... it was all by itself switching to cooperative & non-cooperative modes ...
hi i m using mi 410 my camera quality is bad, how to improve camera quality and how to change icons? i tried change icon many time but not changed....
CacingKalung said:
It's probably the kernel problem. Just like mine, but I'm using MIUI, MIUI kernel 1.9.30 has the same bug, the latest kernel (1.10.21) fix the camera and work again.
Just like deatbearer said, you've to flash stock ROM or Andro-ID RC2 or MIUI 1.10.21.
Click to expand...
Click to collapse
Thank you very much for the advice. But where can I download the kernel or do you have the link to download. One more thing, besides kernel update do I have to flash stock ROM too and how to flash it? Sorry I'm not so good at this. So beginner I am. Thank you very much.
Sent from my Triumph using XDA App
pittms said:
Thank you very much for the advice. But where can I download the kernel or do you have the link to download. One more thing, besides kernel update do I have to flash stock ROM too and how to flash it? Sorry I'm not so good at this. So beginner I am. Thank you very much.
Sent from my Triumph using XDA App
Click to expand...
Click to collapse
Yes, I think you have to flash that ROM. Just like you flash your CM7, use Andro-ID RC2.
was getting a lot of camera problems on stock firmware,
so flashed it with RC2... never had the problem again
Was working Fine on MIUI too
now using CM7 Still Working
Legend Q&A,
Q. When the status bar is hidden, how can I access the files on the device?
A. USB mass storage goes through the statusbar service, so it gets disabled too. Droid Explorer is an excellent tool to access the files on the phone, just make sure the phone has usb debugging enabled, since adb is still enabled.
Droid Explorer
we need this bumped so when people got so questions about The Legend it can be asked and answered.Thank you Crt60 for a awesome rom.
fezzy102 said:
we need this bumped so when people got so questions about The Legend it can be asked and answered.Thank you Crt60 for a awesome rom.
Click to expand...
Click to collapse
Thanks man, I appreciate it.
3.4 Beta 2
I read on the development thread that version 3.4 will be released tonight. I just finished upgrading to this (3.4 Beta 2--works great by the way!). Are you anticipating updating the zip, or will the the current "beta 2" package be the same as what is "released" this evening?
I had a weird issue after flashing 3.4 ICS. My status bar disappeared along with my Calendar app. I flashed back to 3.0 ICS and they are working again.
Thoughts?
Did you flash the wipe or no wipe to 3.4
@red81 sorry was this the ics edition crt60 and I are trying to replicate it.
robm1911 said:
Did you flash the wipe or no wipe to 3.4
Click to expand...
Click to collapse
Sorry that would have helped. I flashed the no-wipe version of the beautiful ICS version coming from Legend 3.0 ICS
BeowulfShaeffer said:
I read on the development thread that version 3.4 will be released tonight. I just finished upgrading to this (3.4 Beta 2--works great by the way!). Are you anticipating updating the zip, or will the the current "beta 2" package be the same as what is "released" this evening?
Click to expand...
Click to collapse
There are some minor differences, added the roboto font plus an ICS audible selection tone.
Red_81 said:
I had a weird issue after flashing 3.4 ICS. My status bar disappeared along with my Calendar app. I flashed back to 3.0 ICS and they are working again.
Thoughts?
Click to expand...
Click to collapse
I just reflashed again from 3.0 ICS to 3.4 ICS exactly like before. This time it worked. We'll just call the first time a bad flash (even though I flashed 3.4 over 3.4 after the error first occurred).
Weird.
Red_81 said:
I just reflashed again from 3.0 ICS to 3.4 ICS exactly like before. This time it worked. We'll just call the first time a bad flash (even though I flashed 3.4 over 3.4 after the error first occurred).
Weird.
Click to expand...
Click to collapse
Did you redownload the update or anything else different
robm1911 said:
Did you redownload the update or anything else different
Click to expand...
Click to collapse
Nope. Same file and same flash procedure. I hate not knowing a root cause.
Red_81 said:
Nope. Same file and same flash procedure. I hate not knowing a root cause.
Click to expand...
Click to collapse
Trust me that makes two of us
Red_81 said:
Nope. Same file and same flash procedure. I hate not knowing a root cause.
Click to expand...
Click to collapse
My guess is the new sigs from the 3.4 rom didnt take for some reason.
Just a glitch.
Sent from my SAMSUNG-SGH-I897 using xda premium
Just an FYI, I noticed a little glitch when you select the 4-Tap lock screen and your battery gets low and notifies you to plug it up the charge symbol shows %d%% if I remember correctly. Didn't want to post in here but I don't have enough to post in development yet. Also its a great ROM.
mschandler76 said:
Just an FYI, I noticed a little glitch when you select the 4-Tap lock screen and your battery gets low and notifies you to plug it up the charge symbol shows %d%% if I remember correctly. Didn't want to post in here but I don't have enough to post in development yet. Also its a great ROM.
Click to expand...
Click to collapse
That has been a tough one from the start, you change it and it works for the larger numbers but not smaller. Change it again and it works for smaller numbers and not the larger ones. Havent figured out the proper place holder configuration. So I opted for the larger numbers.
Sent from my SAMSUNG-SGH-I897 using xda premium
crt60 said:
My guess is the new sigs from the 3.4 rom didnt take for some reason.
Just a glitch.
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
So I just reproduced the glitch on the backup phone by restoring a nandroid and going through the same steps. I'm guessing it was just something unique to my setup.
Red_81 said:
So I just reproduced the glitch on the backup phone by restoring a nandroid and going through the same steps. I'm guessing it was just something unique to my setup.
Click to expand...
Click to collapse
A nandroid backup can bring some of the old sigs with it, causing problems, I've been using tibu with no problems. If having problems with the no wipe, the full wipe maybe what you need to do, I think the problem lies with the nandroid backup.
I really appreciate your feedback.
Well I really appreciate your work on this ROM so let's call it even. (Alright. I still owe you one)
Sent from my SAMSUNG-SGH-I897 using XDA App
Great rom and thanks for your hard work. I am having a crazy issue with 3.0 running the HSB theme. After 2 days almost exactly my phone app disapears from the dock. The icon is just gone. I tried adding the shortcut with a long press and application shortcut, but it is not even listed as an option. However if I use a direct dial shortcut it calls just fine. really weird
I went back to stock and flashed again full wipe, same thing happened. I was reluctant to go to 3.4 just yet. has anyone else reported this issue?
Geeve
This is the first report of this issue. After you reflashed 3.0 did you reflash the theme or a different kernel? I'm just checking if this might be theme related or possibly kernel related. Crt and myself are using corn 6.03 it seems some of the newer versions are doing some funky stuff. We seen random reboots, and crt's phone actually called his voicemail while on the table using one of the newer versions of the corn kernel.
I recently installed CM9 .06 on my touch pad and it was working great for a few hours. Then i restarted the device and now the wifi wont come back up and it keeps rebooting all the time. Has anyone else see this issue ?
This should be in Q&A, but yes I have, I switched to the Nightlies and haven't had it happen since.
Sent from my HP TouchPad on CM9 using Tapatalk
Thanks I will look over again the Q&A and try to download the nightlys also.
Though has anyone seen an issue with the email app ? After the app configures it just keeps saying "waiting for sync". I havent seen anyone else say anything about this
Sounds like it's either a problem with your configuration or your gapps package. Either try a new one or check your info.
Also, I highly suggest trying the nightly builds. The latest one is excellent- touchscreen is fixed, wifi strength is better, better speed, and more features. And the reboot fix is applied.
chitownevo said:
Thanks I will look over again the Q&A and try to download the nightlys also.
Though has anyone seen an issue with the email app ? After the app configures it just keeps saying "waiting for sync". I havent seen anyone else say anything about this
Click to expand...
Click to collapse
After flashing the gapps you need to flash the fix file as well. Just be sure to wipe cache and dalvik before flashing. Also, this does not belong in this section.
I saw there are a few different verisions of GApps. Is there one that i should be using ?
chitownevo said:
I saw there are a few different verisions of GApps. Is there one that i should be using ?
Click to expand...
Click to collapse
The latest one, v11.
Hi
(less than 10 posts, so i have to post it here)
i suffer from the bug which is described in the cm9 owain developer thread.
http://forum.xda-developers.com/showpost.php?p=24086754&postcount=1681
I'm not sure i really have the same bug, but something similar. Other users in a german forum also have this problem.
The Problem:
1. start phone
2. wlan is on
3. deactivate wlan -> mobile data starts
4. activate wlan -> mobile data off
5. wait about 15minutes, phone in standby
6. deactivate wlan -> no mobile data starting
7. toogle flight mode -> mobile data working again
8. wait again about 15 minutes -> mobile data fails again
Without waiting some minutes after toggling the flight mode or boot everything works as it should.
Disabling automatic time didn't work for me. Still the same issues.
I installed alogcat. can someone tell me which filter i can set to get only relevant information?
thanks
Timo
i also encountered this issue, however it started on cm 7 and even when i reverted to stock rom the issue persisted.
ive sent my device in for repair (2nd time, since they did nothing the 1st time).
so i dont think its a rom issue since it is present with all roms ive tested, also different bb (from 218 to 1120 and different ril combimations) .
so since this started happenig about 2months or so ago i dont think it is software rwlated but then that is just a guess....
would be great if you could provide some filtered logs for the devs so they can see if its software related.
Sent from my HTC Wildfire using XDA
Same issue here!
Since i have CM9, i have this issue. Baseband 218 works only perfect on CM7.
Even at stock, I have this problem now...
hmm can it be that cm9 damages the device? or does something that is not reverted when resetin the device to stock?
Sent from my HTC Wildfire using XDA
did you just restore a back up stock ROM or have you tried smartflashing the stock ROM?restoring back ups sometime are not erasing some system files...try smartflashing the stock ROM...it will wipe everything on your phone including partition...and your OS is back to stock(unrooted)
chupi_24 said:
did you just restore a back up stock ROM or have you tried smartflashing the stock ROM?restoring back ups sometime are not erasing some system files...try smartflashing the stock ROM...it will wipe everything on your phone including partition...and your OS is back to stock(unrooted)
Click to expand...
Click to collapse
i used smartflash, thats why i think its not software related or at least not cm9 related...
Sent from my HTC Wildfire using XDA
i have a same problem once in a while signal dissapears on cm9. Now testing on Kang Cm7.2 with 20c BB and 128 RIL.
I called LG, and my device is tomorrow exchanged (VIP service in the Netherlands), hope that the solution will be.
I tested my device with CM7 KANG 80 again yesterday. With CM7 data works after i disable WLAN. Back again on CM9 the data does not activate. Only after toggling Flightmode.
hm interesting... maybe there are multiple ptoblems which cause the same effect....
Sent from my HTC Wildfire using XDA
UPDATE
OWAIN 31 CM9
Baseband v10d 0725
harsh kernel
still same problems.
Phone is now exchanged (today). I think the bug is fixed now for me. Will checking out these days!
gerbenp said:
Phone is now exchanged (today). I think the bug is fixed now for me. Will checking out these days!
Click to expand...
Click to collapse
you got a new device? please let me know if you still get the problem.
Sent from my HTC Wildfire using XDA
I got the same problem since V20q BB.
Gesendet von meinem Optimus 2X mit Tapatalk
a more experienced android user/tester/.. told me, that it is a general cm9 problem. so there is nothing we can do, but waiting.
this also fits to my testings. with cm7 everything worked fine for me.
for now just deactivated wlan most of the time, my data plan is big enough.
whenever i hear something new i'll post it.
-----------------------------------
owain wrote he probably fixed it.
downloading kang 35 and testing.
Pitscho said:
owain wrote he probably fixed it.
downloading kang 35 and testing.
Click to expand...
Click to collapse
Still don't working for me (coming from full wipe)
yep, for me neither.
grognaz said:
you got a new device? please let me know if you still get the problem.
Sent from my HTC Wildfire using XDA
Click to expand...
Click to collapse
Problem is now fixed for me. Today and yesterday have been outdoors, and everything just went back the way it was!
gerbenp said:
Problem is now fixed for me. Today and yesterday have been outdoors, and everything just went back the way it was!
Click to expand...
Click to collapse
And that is with a new o2x?
Sent from my HTC Wildfire using XDA
grognaz said:
And that is with a new o2x?
Sent from my HTC Wildfire using XDA
Click to expand...
Click to collapse
Yes, that's right.
Hello xda
I know there quite a few posts out there with people detailing their phones rebooting randomly but my phone just hit a new level of weird.
My i9000 reboots randomly into cwm recovery menu for no good reason (I know there is another thread about this but that instance is on the Nexus S and the thread has basically died). This started occurring shortly after I flashed slim ROM 4.2.2 build 5 (came from CM10.1 nightlies). Flashing the rom again and updating it to build 6 has done nothing to alleviate the issue.
I'm using the Semaphore kernel with no OC or changed settings, and having recently bought a new battery, I'm really not sure where to start looking for the problem.
If anyone can give me some tips it'd be greatly appreciate, thanks in advance.
HellDiv3r said:
Hello xda
I know there quite a few posts out there with people detailing their phones rebooting randomly but my phone just hit a new level of weird.
My i9000 reboots randomly into cwm recovery menu for no good reason (I know there is another thread about this but that instance is on the Nexus S and the thread has basically died). This started occurring shortly after I flashed slim ROM 4.2.2 build 5 (came from CM10.1 nightlies). Flashing the rom again and updating it to build 6 has done nothing to alleviate the issue.
I'm using the Semaphore kernel with no OC or changed settings, and having recently bought a new battery, I'm really not sure where to start looking for the problem.
If anyone can give me some tips it'd be greatly appreciate, thanks in advance.
Click to expand...
Click to collapse
hi
randomly i will got this problem if i m flashing backward. like from 4.2.2 - 4.2.1, or 4.1.x to 4.0.x. or repeatedly changing between kernel (i always do this to modified ROM to suits my settings n need) its probably due to changing partition in system or kernel clash (even i did all wipe) in internalsd.
Sorry to say. it will come worst sometimes if u ignore da problem or keep flashing ROM to avoid it. 'Luckily' about 2 hour ago my sgs just did. Constantly booting to recovery n its juz bootloop between kernel splashscreen n sgs white splashscreen after it.3 combo button will not working for recovery n only download mode accessible.
no more method for me . Juz flashing back to stock firmware JVU +CF-ROOT with odin was da answers
but if u dont familiar with odin.seek guide here
http://forum.xda-developers.com/showthread.php?t=2149455
but use it as ur last method!
clashing between titan.....no! kernel maybe da reason.do some wiping before changing kernel or ROM. n format system if necessary before flashing!
Sent from my GT-I9000 using xda app-developers app
---------- Post added at 04:45 AM ---------- Previous post was at 04:37 AM ----------
Now i m stick with GB Saurom for a while. really tired unbricking my fone as after my sgs softbrick,my pc went crazy :what: n i m stuck with repairing my pc first. then flash my ol lil i9000
Sent from my GT-I9000 using xda app-developers app
Reboots into CMW with Slim Bean 4.3 and Semaphore
Hi guys, any news on the subject? Exactly the same thing happening to me. I did a clean installation of Slim 4.3, after using CM10 and everything seems to be working perfectly except it reboots into CWM every 1-2h!!! I haven't changed any configuration and didn't mess with the kernel that came with the ROM, which is Semaphore... Is it a kernel issue? Should I try to flash the latest version?
HellDiv3r said:
Hello xda
I know there quite a few posts out there with people detailing their phones rebooting randomly but my phone just hit a new level of weird.
My i9000 reboots randomly into cwm recovery menu for no good reason (I know there is another thread about this but that instance is on the Nexus S and the thread has basically died). This started occurring shortly after I flashed slim ROM 4.2.2 build 5 (came from CM10.1 nightlies). Flashing the rom again and updating it to build 6 has done nothing to alleviate the issue.
I'm using the Semaphore kernel with no OC or changed settings, and having recently bought a new battery, I'm really not sure where to start looking for the problem.
If anyone can give me some tips it'd be greatly appreciate, thanks in advance.
Click to expand...
Click to collapse
I run into the same problem with my current update of my I9000 to CM 10.2.1 and the Semaphore Kernel 3.3.0 (JB).
Any ideas on this issue from the pros?
I realized that it was happening to me only when I was loosing the network coverage, like being in the underground or roaming or things like that... I don't know if it happens to everyone but in my case it's definitely this. If there is no network available my phone will boot into recovery after a while. If the signal is OK, it doesn't happen. Maybe it has something to do with the modem?!
mar0ni said:
I run into the same problem with my current update of my I9000 to CM 10.2.1 and the Semaphore Kernel 3.3.0 (JB).
Any ideas on this issue from the pros?
Click to expand...
Click to collapse
mlw_es said:
Hi guys, any news on the subject? Exactly the same thing happening to me. I did a clean installation of Slim 4.3, after using CM10 and everything seems to be working perfectly except it reboots into CWM every 1-2h!!! I haven't changed any configuration and didn't mess with the kernel that came with the ROM, which is Semaphore... Is it a kernel issue? Should I try to flash the latest version?
Click to expand...
Click to collapse
mar0ni said:
I run into the same problem with my current update of my I9000 to CM 10.2.1 and the Semaphore Kernel 3.3.0 (JB).
Any ideas on this issue from the pros?
Click to expand...
Click to collapse
mlw_es said:
I realized that it was happening to me only when I was loosing the network coverage, like being in the underground or roaming or things like that... I don't know if it happens to everyone but in my case it's definitely this. If there is no network available my phone will boot into recovery after a while. If the signal is OK, it doesn't happen. Maybe it has something to do with the modem?!
Click to expand...
Click to collapse
Deactivate Deepidle in Semaphore manager app and these reboots should be gone.
Did the trick for me.
hertzschi said:
Deactivate Deepidle in Semaphore manager app and these reboots should be gone.
Did the trick for me.
Click to expand...
Click to collapse
Yes, I did this and so far no reboots anymore.