I have flashed my N1 as following sequence:
Desire R21>Stock Rom>Froyo 2.2>New fastboot & Recovery
Now, I find no auto focussing of camera. Is it the bug of this testing Froyo 2.2? Or my phone has to be repaired? Anyone could help me? Thanks~
Did you flash the new radio? Also, are you turning the Focus mode to Infinity or on Auto?
Also, download and try Barcode Scanner to assure that your hardware is not faulty, this APP autofocus's pretty efficiently
wesbalmer said:
Did you flash the new radio? Also, are you turning the Focus mode to Infinity or on Auto?
Click to expand...
Click to collapse
new radio? yes, i think. and certainly turn it to auto~
wesbalmer said:
Also, download and try Barcode Scanner to assure that your hardware is not faulty, this APP autofocus's pretty efficiently
Click to expand...
Click to collapse
can use barcode scanner, but the image is blur...
I don't have the same issues as you do, I would try going back to another rom just to be certain the hardware isn't bad. If you have a Nandroid of your R21, then use that. Sorry couldn't be of more help, hopefully this is just a problem with your flash of 2.2 and not with your hardware. I don't see how a flash could ruin your Auto-focus, but I could see the Auto-focus functionality corrupting during an install.
wesbalmer said:
I don't have the same issues as you do, I would try going back to another rom just to be certain the hardware isn't bad. If you have a Nandroid of your R21, then use that. Sorry couldn't be of more help, hopefully this is just a problem with your flash of 2.2 and not with your hardware. I don't see how a flash could ruin your Auto-focus, but I could see the Auto-focus functionality corrupting during an install.
Click to expand...
Click to collapse
Thanks. in fact, i also find some problems abt the camera during using R21. the image is blur and it is normal when i flash back to stock rom.
Related
Lately I've been having problems with the audio on my G1 and I'm not sure if it's the rom I'm using or if it's the phone.
Here is the problem...
When i'm on a call there is noise in the background as if the I'm standing in front of a fan and the caller goes in/out and can't hardly hear me.
Does anyone know what this could be?
I've noticed this using Super D 1.6 and WG Y2.6 CFS.
I have tried the audio hack previously but not with these roms and I've wipe several times but the problem is still there.
I don't want to have to unroot to send my phone back, if anyone know what I can do to fix this problem I would greatly appreciate it.
When using the Audio hack you must:In order
1.Flash Install old V1/V2/V3 first,Kill media then reboot
2.Now you can flash V2R2 or other one <--Best one and kill media and reboot
I think you kill media before doesnt really seem to matter for me, works fine for me.Are you using the hack or doing it the ol-fashion way?
Ace42 said:
When using the Audio hack you must:In order
1.Flash Install old V1/V2/V3 first,Kill media then reboot
2.Now you can flash V2R2 or other one <--Best one and kill media and reboot
I think you kill media before doesnt really seem to matter for me, works fine for me.Are you using the hack or doing it the ol-fashion way?
Click to expand...
Click to collapse
If you kill the mediaserver then you shouldn't need to reboot.
And i don't think it's a software problem. You could test by doing a backup, switching ROMs and seeing if the problem persists. If not, then it's a problem with the audiofiles, but if it does it's most likely a hardware problem.
Meltus said:
If you kill the mediaserver then you shouldn't need to reboot.
And i don't think it's a software problem. You could test by doing a backup, switching ROMs and seeing if the problem persists. If not, then it's a problem with the audiofiles, but if it does it's most likely a hardware problem.
Click to expand...
Click to collapse
Thanks i wondered what that did, wasnt too sure just randomly tried it didnt know it stopped the need for rebooting.
Ace42 said:
When using the Audio hack you must:In order
1.Flash Install old V1/V2/V3 first,Kill media then reboot
2.Now you can flash V2R2 or other one <--Best one and kill media and reboot
I think you kill media before doesnt really seem to matter for me, works fine for me.Are you using the hack or doing it the ol-fashion way?
Click to expand...
Click to collapse
I don't quite get what to do. I'm such a noob, where do I find these files? I think my audiofiles are messed up.
can you point me in the righ direction please?
thanks
just update to the latest radio
http://code.google.com/p/sapphire-port-dream/
nicostar said:
just update to the latest radio
http://code.google.com/p/sapphire-port-dream/
Click to expand...
Click to collapse
I do have the latest.
I don't know what it could be.
nicostar said:
just update to the latest radio
http://code.google.com/p/sapphire-port-dream/
Click to expand...
Click to collapse
He/she already has it they're rooted with 26i radio since they have Wes rom.The radio allows custom roms to be installed.
@OP theres a market app i use from meltus, but files are here
http://meltus.androidftw.com/
http://forum.xda-developers.com/showthread.php?t=517745
Ace42 said:
He/she already has it they're rooted with 26i radio since they have Wes rom.The radio allows custom roms to be installed.
@OP theres a market app i use from meltus, but files are here
http://meltus.androidftw.com/
http://forum.xda-developers.com/showthread.php?t=517745
Click to expand...
Click to collapse
maybe its just faulty hardware like the speaker.
I'm in Canada using Bell (i9000m)
I have rooted my phone. I've used the 1 click lag fix. I've overclocked it a bit using an app/widget.
Other than that, I haven't done anything else to my phone.
I know these are noob questions, but i just hope someone can help me.
I can't for the life of me access Keis (tried everything)
I am curious: how do I update my firmware? what about the 2.2 froyo update? will it be OTA? will I still get it? What about the GPS fix?
Basically im wondering how will I be able to get these updates and fixes if I can't access Keis -- and my phone is rooted (does that even matter?) ?
Thanks in advance guys
No one?
Just basically wondering about future updates (gps fix / froyo 2.2) --- will I still be able to receive these if I rooted my phone?
What if I can't access Kies ?
I don't think the Galaxy S has an OTA function
Which means, it's either KIES or Odin
Arkanius said:
I don't think the Galaxy S has an OTA function
Which means, it's either KIES or Odin
Click to expand...
Click to collapse
Christ. This phone is bar none the best avail. But easily has the WORST software I've ever seen.
KIES is messed and will never work with my phone/computer. It doesn't recognize anything.
So my only option is ODIN? is there anything I should be worried about with ODIN? is it really simple to flash? or do I gotta make partitions etc.
Any chance you have launcher pro installed?
im a newbie so im just providing info i have read my self and so far that ive seen odin is very simple to follow proper instructions theres a youtube video when ur flashing something your given step by step instructions by who ever uploaded the file and if you have the 3 button combo working your good to go as you can always reflash
The phone actually does have software capable of doing OTA updates. It probably isn't set up to work yet though.
The lagfix won't affect your upgrading though, just remember to uninstall it before doing the upgrade!
Root will have zero effect too, as it is just an extra (special) application at it's core.
it needs to switch back to TwLauncher for KIES to work
you can use Home Switcher
link http://forum.xda-developers.com/showthread.php?t=765081
Bobler420 said:
im a newbie so im just providing info i have read my self and so far that ive seen odin is very simple to follow proper instructions theres a youtube video when ur flashing something your given step by step instructions by who ever uploaded the file and if you have the 3 button combo working your good to go as you can always reflash
Click to expand...
Click to collapse
I'm with Bell - my 3 button combo DOESN'T work
ivanchin99 said:
Any chance you have launcher pro installed?
Click to expand...
Click to collapse
Yes.
Do i have to uninstall it? or just use TW as my default ?
RyanZA said:
The phone actually does have software capable of doing OTA updates. It probably isn't set up to work yet though.
The lagfix won't affect your upgrading though, just remember to uninstall it before doing the upgrade!
Root will have zero effect too, as it is just an extra (special) application at it's core.
Click to expand...
Click to collapse
What happens if you DONT uninstall the lag fix before the update ?
I used Ryan's 1-click lag fix --- is there a one-click to reverse it ?
is it easy to reverse the lag fix?
cheers
Funkadelick said:
Yes.
Do i have to uninstall it? or just use TW as my default ?
Click to expand...
Click to collapse
No you don't have to uninstal just go to settings>applications>manage applications
select launcher pro and then click on the clear defaults button. Next press the home key, it will ask you to choose a home app, choose TW.
Kies does not work untill you do that.
Other things to check is go to settings>status>usb mode select kies
Usb debuging should be OFF
Try to have the pc and phone on a fresh restart before trying to connect.
Basicly it should work.
Yes, Kies works only with TW. Also with the latest Froyo JPC firmware you get yor GPS fixed already.
Sent from my GT-I9000 using XDA App
Funkadelick said:
Yes.
Do i have to uninstall it? or just use TW as my default ?
Click to expand...
Click to collapse
Yes, you need to use the default TW. I had the exact problem as yours, uninstalled my launcher pro then Kies is able to detect the phone from there.
Allgamer made a good point. I cant find anyway to return to the default screen so i just click uninstall
OlegZh said:
Yes, Kies works only with TW. Also with the latest Froyo JPC firmware you get yor GPS fixed already.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Well this is the problem: I don't know how to flash (yet) so I'm just trying to learn slowly.
I am not sure if i want to flash it with Froyo FW's -- I kinda wanna wait for Bell to release their 2.2 froyo update (b/c my 3 buttons don't work and hopefully it will fix it AND the GPS)
So basically you guys have helped me with the Kies. But I am curious about the 1-click-lag-fix (I found the APP on the market and it worked) -- i don't wanna mess up my phone cuz the 3 button thing don't work.
So I just use the APP again to Un-root, use the APP again to remove/uninstall the lag-fix, then use Keis (or odin) to install/flash the new 2.2 froyo Bell update (when it comes out) ? then im good to go ?
After I update to 2.2 -- then I root again, and lag fix?
Funkadelick said:
Christ. This phone is bar none the best avail. But easily has the WORST software I've ever seen.
KIES is messed and will never work with my phone/computer. It doesn't recognize anything.
So my only option is ODIN? is there anything I should be worried about with ODIN? is it really simple to flash? or do I gotta make partitions etc.
Click to expand...
Click to collapse
I have a Bell i9000m, rooted, unlocked and on Rogers.
After installing Samsung drivers ( PRIOR TO connecting via usb) Kies worked on first attempt (Win7 64bit). The driver pack is 18 mb and I found it somewhere here on the forms (looking for the link).
Hope that helps.
Hi, I also having GPS problem previously and I hated samsung which produce so bad gps phone but after a while I think I finally found why causes the gps issues. Ok if you go into the GPS test mode by *#1472365*# you will notice that we are using SUPL. SUPL true GPS which will in coorporate with the compass and stalite to fix our position and direction. But our phone compass some how need to be calibrated. Just key in *#0*# then click on sensor. If your compass showing need to be calibrate then just hold your phone by verticaly and rotate it untill you get 3. Now reboot it and try the GPS.
OK guys, I own a Heroc and spend all my time over in that area of XDA and the IRC.. BUt i have quick question about a friends Samsung Captivate... He is running a custom rom and is wanting to unroot and go completely back to stock.. Can you lead me in the right direction please..
Edit*** the reason he is wanting to go back is because GPS is not working...
Here ya go...
http://forum.xda-developers.com/showthread.php?t=731989
i noticed alot of people on there are saying this dont work or there are major issues and complications.. you have to forgive me.. I run a hero and going back stock is a simple as running the RUU and i dont have to do a thing but watch the progress and waalaa its done..
BUMP... OK the reason for this is because GPS and camera are not working.. He is running cognition2.6 or something like that... i figure its a kernel problem but your guys could tell me more...
I've screwed up using odin several times but it was always user error. What your friend needs to do is follow the instructions exactly step-by-step and they'll be fine.
hatchguy06 said:
Edit*** the reason he is wanting to go back is because GPS is not working...
Click to expand...
Click to collapse
Going back to stock isn't going to make gps any better. Best to flash jm9 fix, should work with any rom.
Sent from my SAMSUNG-SGH-I897 using XDA App
hatchguy06 said:
BUMP... OK the reason for this is because GPS and camera are not working.. He is running cognition2.6 or something like that... i figure its a kernel problem but your guys could tell me more...
Click to expand...
Click to collapse
Don't know why your friend's captivate has no functional camera when he is on cognition. Make him flash the latest cog? Like the person above, GPS is as good as crap on stock as well. Do jm9 fix and see if that fixes it. If you need the jm9 file, PM and I will send you the flashable zip file.
Also if he wants to go back to stock, ODIN is pretty simple too. Open up ODIN, go to download mode (from cog I think there is a reboot to download option. If not just shut down the phone, press both vol up+down and hold them and plug in USB cable.) Once ODIN says "added!", press start, and just let it be. Your friend's phone should be back to stock in just a few minutes.
EDIT: Also tell your friend to read more. It's way better to do stuff knowing what you're doing
I don't have any issues with my vibrants GPS. I got the OTA and wallah no more sh-tty GPS. I use it everyday for work. Now I just need to do RyanZa's OCFL and I'm good.
Sent from my SGH-T959 using XDA App
Hi there,
I'm having a bit of trouble with my HTC One. I received it yesterday, and I believe that the GPU memory is getting corrupted when loading large images. I've uploaded a video:
HTML:
videobam.com/rzFTy
(xda won't let me link unless I make ten posts)
It has happened on both stock sense and CyanogenMod 10.1.3-RC2 and today's CyanogenMod 10.2 nightly.
Has anyone experienced a similar problem, and does anyone know how to proceed with fixing this? It is just the graphics buffer - if I take a picture on the camera, it's fine. When I zoom into an image in the gallery, it's fine. When I have the camera open under low light conditions, it's fine. But give it a detailed image and it goes crazy.
What's even more interesting is that if I drag down the notification bar, the notification bar doesn't get corrupted, it's fine. Underneath, the corruption still goes on.
Please help?
tauovertwo said:
Hi there,
I'm having a bit of trouble with my HTC One. I received it yesterday, and I believe that the GPU memory is getting corrupted when loading large images. I've uploaded a video:
HTML:
videobam.com/rzFTy
(xda won't let me link unless I make ten posts)
It has happened on both stock sense and CyanogenMod 10.1.3-RC2 and today's CyanogenMod 10.2 nightly.
Has anyone experienced a similar problem, and does anyone know how to proceed with fixing this? It is just the graphics buffer - if I take a picture on the camera, it's fine. When I zoom into an image in the gallery, it's fine. When I have the camera open under low light conditions, it's fine. But give it a detailed image and it goes crazy.
What's even more interesting is that if I drag down the notification bar, the notification bar doesn't get corrupted, it's fine. Underneath, the corruption still goes on.
Please help?
Click to expand...
Click to collapse
I remmember this happening to me with a custom rom. Try the stock rom and it will probably be fixed.
muayyadf1 said:
I remember this happening to me with a custom rom. Try the stock rom and it will probably be fixed.
Click to expand...
Click to collapse
I'll try it out - on the stock ROM I was on yesterday (before unlocking the bootloader), it still had the same issue. Disappeared after a pending update, but I never tested that update very thoroughly. I'll post back after I try this out.
Do you know of any reason why this could be happening? I like AOSP better than Sense, so I'd rather stick with CM or equivalent, but if it becomes unusable because of this I'll be forced to switch back to sense.
tauovertwo said:
I'll try it out - on the stock ROM I was on yesterday (before unlocking the bootloader), it still had the same issue. Disappeared after a pending update, but I never tested that update very thoroughly. I'll post back after I try this out.
Do you know of any reason why this could be happening? I like AOSP better than Sense, so I'd rather stick with CM or equivalent, but if it becomes unusable because of this I'll be forced to switch back to sense.
Click to expand...
Click to collapse
Check the developer options and make sure the show screen updates option is turned off. Food for the thoughts.
muayyadf1 said:
Check the developer options and make sure the show screen updates option is turned off. Food for the thoughts.
Click to expand...
Click to collapse
Don't worry, I've made sure that the show screen updates option is disabled. If it were on, this problem would happen all over the place, instead of intermittently when loading large images or under non-low-light conditions. There's nothing in the logcat when this glitch happens either, which makes it difficult to track down.
tauovertwo said:
Don't worry, I've made sure that the show screen updates option is disabled. If it were on, this problem would happen all over the place, instead of intermittently when loading large images or under non-low-light conditions. There's nothing in the logcat when this glitch happens either, which makes it difficult to track down.
Click to expand...
Click to collapse
I would try another rom or even stock RUU.
EDIT: Stock RUU will delete everthing!
muayyadf1 said:
I would try another rom or even stock RUU.
EDIT: Stock RUU will delete everthing!
Click to expand...
Click to collapse
I don't mind about everything being deleted. I haven't got anything important on the device - I have yet to transfer my files from my old one.
Could you please link to a stock RUU for hboot 1.54?
tauovertwo said:
I don't mind about everything being deleted. I haven't got anything important on the device - I have yet to transfer my files from my old one.
Could you please link to a stock RUU for hboot 1.54?
Click to expand...
Click to collapse
Check out the sticky thread and choose the correct ruu for the cid you have or do a super cid.
muayyadf1 said:
Check out the sticky thread and choose the correct ruu for the cid you have or do a super cid.
Click to expand...
Click to collapse
There isn't a RUU available for later versions.
RUU files aren't released by HTC as they're intended for service centre use.
The ones that are accessible to xda community were leaked versions.
The source of these leaks seems to have "run dry"
Sent from my HTC One using xda app-developers app
Leaked or not, they are there in case we need them
I suggest to s-off and flash newest firmware and maxiumusHD ROM
I've tried 6.1 and 7.0 (currently) and the camera quality is way worse than when I had 5.1
Obviously I don't want to go back to the 5.1, so what are my options?
All I care about is to don't lose the security and battery improvements that 7.0 brought to my phone.
Thanks in advance
EDIT: Example -> imgur. com/a/nD4qW (without the space, I can't post links yet)
I'm on 7.0 too and have same issues with camera. It's really bad from Samsung to do that with their software
Mind telling how its bad? Examples? Usual stuff like that
Porcupineomg said:
Mind telling how its bad? Examples? Usual stuff like that
Click to expand...
Click to collapse
Sure.
imgur. com/a/nD4qW (without the space, I can't post links yet)
As you can see the "before" pics have the average quality for a Note 5, but the other 2 are way below the quality one would expect from this phone
It happened right after I updated, that's why I think that's the reason. But maybe it was just a coincidence and my camera got broken.
mihajlo1 said:
I'm on 7.0 too and have same issues with camera. It's really bad from Samsung to do that with their software
Click to expand...
Click to collapse
I updated the OP with an album with pictures before and after.
Mind telling me if the quality of your pics are similar to mine?
I think its more of a hardware issue than a software. If you haven't rooted your phone yet i will recommend you to do so. Flash TWRP and wipe data, system, cache, dalvik cache, Internal Storage and then Flash a new ROM with tge corresponding Kernel for your phone model. After all those steps check if your phone's camera got fixed. Btw when wiping internal storage you should backup everything from your phone and have an OTG cable with a USB thumbdrive to flash the downloaded ROM & Kernel for your phone.
luisoriera said:
I think its more of a hardware issue than a software. If you haven't rooted your phone yet i will recommend you to do so. Flash TWRP and wipe data, system, cache, dalvik cache, Internal Storage and then Flash a new ROM with tge corresponding Kernel for your phone model. After all those steps check if your phone's camera got fixed. Btw when wiping internal storage you should backup everything from your phone and have an OTG cable with a USB thumbdrive to flash the downloaded ROM & Kernel for your phone.
Click to expand...
Click to collapse
Thanks for the answer.
I will try all that right away.
EDIT: my note 5's bootloader is locked (At&t). Will I be able to do that?
EDIT2: aparently not
Well... Your only chance is to go to AT&T and make a claim to repair it. Or better, change it. Good luck man.
I have the same problem, first it thought it's only me.. but after I saw your uploaded photos .. I started to think it's a software issue.. I'll try a downgrade and I'll inform you with the results.
bassam M said:
I'll try a downgrade and I'll inform you with the results.
Click to expand...
Click to collapse
Yes please!!
I cannot downgrade my phone to Lollipop because my bootloader is locked (AT&T) so it would be nice if you could confirm that this problem is related with the android version.
Pictures are exactly like mine. We have same problem.
from the photos I see the image is blurred because the glass on the camera is scratched or has oil,moisture on it try to clean the glass of the camera well then try to recapture the photos I don't think it's a software issue
Hi again, Sorry for being late,
I was able to downgrade only to Marshmallow due to Binary issue (can't downgrade to smaller binary number),
the photos are better now but from time to time I got this Fairy tale blurred effect (and believe me the camera cover is clean).. but if I lowered the lighting (long press on the screen and slide down) the image return to normal.. !!!
so.. the downgrade helped but didn't solve the problem 100%.. and I'l stick with marshmallow for now..
Same issue with Camera quality when upgraded to 7.0 from a custom rom based on 7.0