Related
My camera works meaning it opens but the image looks off colored. Its like all the colors are separated. I have checked the modes on the camera while it is open. Is there anyone who knows how to fix this. Posted a picture I took and it had all the basic settings but pictureis still off. Running fasttest 2.9 and its freakin awesome.
I'd wish people would stop posting non-android development stuff in the android development thread...Most likely a hardware issue, you can prove me wrong though. I want to really punch someone in the face right now...Imma punch my own, STOP POSTING IN THE WRONG SECTION D:
would attempt to help if you posted in the right sub section.
new to xda
I didnt know there was a different place to post. What is it?
Just4MyDroid said:
My camera works meaning it opens but the image looks off colored. Its like all the colors are separated. I have checked the modes on the camera while it is open. Is there anyone who knows how to fix this. Posted a picture I took and it had all the basic settings but pictureis still off. Running fasttest 2.9 and its freakin awesome.
Click to expand...
Click to collapse
not going to flame ya......
ya, i had the same problem too, and no switching roms does not help.
its more likely a hardware problem, and i just sent it to t-mobile and got a new one back even though the phone was rooted........
you the same guy who contacted me on the cmupdater support?
i already told you it was hardware, not software related
garok89 said:
you the same guy who contacted me on the cmupdater support?
i already told you it was hardware, not software related
Click to expand...
Click to collapse
Oh the pain of denial...
garok89 said:
i already told you it was hardware, not software related
Click to expand...
Click to collapse
so with the little knowledge i have, i was right?
no i am not. just signed up today..
2 people, 3 days, 2 diff roms, 2 diff phones, similar issues....the plot thickens....
this is the pick i was sent
garok89 said:
2 people, 3 days, 2 diff roms, 2 diff phones, similar issues....the plot thickens....
this is the pick i was sent
Click to expand...
Click to collapse
it looks kinda cool though
same issue
my camera started suffering from the same issue...
i have a rooted g1 running cyanogen 5.0.7
im assuming the camera is busted...but if a solution arises it would be great to hear it...i didnt even see any g1 camera parts on ebay
Just saw it
"unrevoked: A warning: the SkyRaider for the inc has a higher then average chance of causing "USB bricked" devices, we will try to work on a fix."
--http://www.twitter.com/unrevoked/status/20736784251
Sent from my ADR6300 using Tapatalk
Sheesh man! That is scary! Makes me feel like one of those people who come home and find out that the bank they were at an hour ago got robbed ten minutes later!
The tweet has nothing to do with unrevoked's releases.
The skyraider rom appears to use a slightly broken update-binary. When you flash skyraider rom, it writes stuff to misc that it shouldn't, as far as I can tell. This may cause a USB brick (ie, phone is not accessible via USB)
I didnt know for sure what it meant. Just thought I'd share it. I havnt had problems connecting via usb
Sent from my ADR6300 using Tapatalk
So don't use SkyRaider 2.2 from 8/5? I was literally seconds away from doing this...
Is this "USB Brick" something that can be reversed with a Nandroid restore if I decide to take my chances?
It sounds to me like it's an issue with running Unrevoked after you've already installed SkyRaider. I haven't seen any posts in the 231 page SkyRaider thread that report their phone was USB-bricked.
How would that make sense though, like if you are running a ROM you are already rooted, why run unrevoked again?
Θmega said:
It sounds to me like it's an issue with running Unrevoked after you've already installed SkyRaider. I haven't seen any posts in the 231 page SkyRaider thread that report their phone was USB-bricked.
Click to expand...
Click to collapse
This is the opposite of true.
SoccerCore11 said:
How would that make sense though, like if you are running a ROM you are already rooted, why run unrevoked again?
Click to expand...
Click to collapse
Maybe we're finally getting s-off
Sent from my ADR6300 using Tapatalk
rpearl said:
This is the opposite of true.
Click to expand...
Click to collapse
Any ideas on what the criteria would be for this to happen? Is it the process of flashing, our can this happen through a certain process while running the rom?
Sent from my ADR6300 using Tapatalk
rpearl said:
This is the opposite of true.
Click to expand...
Click to collapse
Then why have so many people not had issues with SkyRaider bricking their phones? So far the only place I've heard this is from the unrevoked team and plenty of people are apparently not having the issue at all.
I'm certainly not saying you're wrong—you're more knowledgable than me—but a lot of us are curious as to why this is suddenly an issue even though unrevoked is the only one who's had it happen. If it's because of unreleased software by unrevoked then what was the point in tweeting, since everyone who has it would be able to be contacted personally?
Θmega;7586637 said:
Then why have so many people not had issues with SkyRaider bricking their phones? So far the only place I've heard this is from the unrevoked team and plenty of people are apparently not having the issue at all.
I'm certainly not saying you're wrong—you're more knowledgable than me—but a lot of us are curious as to why this is suddenly an issue even though unrevoked is the only one who's had it happen. If it's because of unreleased software by unrevoked then what was the point in tweeting, since everyone who has it would be able to be contacted personally?
Click to expand...
Click to collapse
Unrevoked never said that it would definately brick your phone. They said it has a "higher than avarage chance of USB bricking due to a broken update-binary"
I've personally never had problems with sky raider, but then again, I haven't used adb in a while, and I use card reader to mount my sd, so this wouldn't affect me that much
Sent from my ADR6300 using XDA App
Fact:
Without unrevoked we still might not have root.
Fact:
There is no known issue among the general public (us) of SkyRaider bricking the usb. Its possible this has happened to 1 or 2 people sure, but that would be a very isolated incedent and does not mean its a common or uncommon bug - more like so super rare none of us have heard about it.
Now you said in your tweet:
unrevoked: A warning: the SkyRaider for the inc has a higher then average chance of causing "USB bricked" devices, we will try to work on a fix
Click to expand...
Click to collapse
Has a higher than average chance.
this leads me to believe that if the chance is .5 now its .6 - again not making it common.
we will try to work on a fix
Click to expand...
Click to collapse
Now maybe its just me but trying to fix something that you didnt break wouldnt that be considered taking responsibility for whats wrong??
Why would you not contact ihtfp69 about this directly? Sorry to say but your tweet is not very tactful and is now causing panic across multiple boards.
Just a word of advice, before basically saying, hey this ROM could break your ****, maybe in the future talk with the dev of the ROM before causing a panic..
Not trying to bash ya, just dont want unneeded panic especially for someone who has done a great job like ihtfp69 in creating a great ROM for us all to use.
btw thanks for the root!!!!!
jdkoreclipse said:
Unrevoked never said that it would definately brick your phone. They said it has a "higher than avarage chance of USB bricking due to a broken update-binary"
Click to expand...
Click to collapse
I'm sorry if I implied they did, but "higher than average" doesn't explain much.
Again, plenty of people never had this issue. It'd be nice for a bit more clarification instead of worrying a lot of current/future SkyRaider users without further explanations of how it happens…
djkms said:
Now maybe its just me but trying to fix something that you didnt break wouldnt that be considered taking responsibility for whats wrong??
Why would you not contact ihtfp69 about this directly? Sorry to say but your tweet is not very tactful and is now causing panic across multiple boards.
Click to expand...
Click to collapse
This is basically what I'm trying to say, but perhaps it's not coming across that well. If it's a very rare bug then the tweet could have been worded differently, or linked to more information.
Its not about running the rom now, its about how the next unrevoked will brick if you use it with this rom.
"@theozzeh After talking with @koush, we've determined that the "SkyRaider" rom is going to be a major bricking risk with the next unrevoked release."
bhazard451 said:
Its not about running the rom now, its about how the next unrevoked will brick if you use it with this rom.
"@theozzeh After talking with @koush, we've determined that the "SkyRaider" rom is going to be a major bricking risk with the next unrevoked release."
Click to expand...
Click to collapse
Thank you! I hadn't seen that tweet, and which goes back to my (sorta?) original question: if it's not an issue with a current release then why is there a need to panic everyone?
So what is the consensus on this info? Important or not? Does it need to be here in development?
OP can you update the first post with what we've gathered and what this all means?
Thanks
Θmega said:
Thank you! I hadn't seen that tweet, and which goes back to my (sorta?) original question: if it's not an issue with a current release then why is there a need to panic everyone?
Click to expand...
Click to collapse
Im not sure its made to panic everyone .. just informative if we are running skyraider which I am we have to be careful with the new version of unrevoked ... which we must use if we want the new version of cwm
I installed the latest vanilla skyraider, didn't like it so I wiped it and then put on the aiccus ROM. When I attach my phone to my computer it will not bring up the SD card or internal storage in my computer. Instead it brings up a CD drive. In the USB tray icon it still shows two removable disks and the CD drive does skip the letters that were assigned to those two drives. I can still take screenshots of the phone using the SDK.
I think this is the brick, if it's not I'd appreciate someone telling me how I can get my computer to recognize the phone again.
If its an update binary issue, then the author of SKyRaider merely needs to replace it, or remove it, as we don't really need the binary in the first place.
I'm not entirely sure if this is an issue with my hardware or software which is why I'm asking where I should look (or start a thread) first. I've had sound before but now there is nothing, not even crackling or popping. I'm using Cyanogenmod 11 on a Samsung Captivate. I read a thread about loosening a screw near the speaker and tried that (along with a not-so-deep tear-down), but still not a peep (or beep). Something I should mention is that headphones DO work when they're plugged in. Additionally I've done some scouring of the Internet for a fix but I can't find any problems truly similar to mine.
Hi
Thanks for writing to us at XDA Assist. It seems to me like you have a hardware failure. Which version of the Captivate do you have? Unbranded or AT&T?
Hi to you too
Thank you for replying. I believe it is the at&t version, although I'll admit I wasn't aware there was a Captivate that wasn't an at&t version. That would be found in the info part of the phone as the model number right?
Kangarooster said:
Hi to you too
Thank you for replying. I believe it is the at&t version, although I'll admit I wasn't aware there was a Captivate that wasn't an at&t version. That would be found in the info part of the phone as the model number right?
Click to expand...
Click to collapse
That's right, and most at&t phones actually have the at&t logo somewhere on the phone, as well as the at&t logo during the boot animation. If it has either of those we can safely assume that is the at&t model, otherwise please let me know what the model number is.
Transmitted via Bacon
Wow, I can't believe I didn't notice it at the top of the phone, yes it is an at&t model.
Kangarooster said:
Wow, I can't believe I didn't notice it at the top of the phone, yes it is an at&t model.
Click to expand...
Click to collapse
Thanks for the extra information. I'm going to have this thread moved to the AT&T Captivate q&a section here:
Captivate Q&A, Help & Troubleshooting
That way it'll reach the people who are most experienced with your device, so if it is a common bug they should be able to walk you through it. It sounds hardware related to me but lets see what the Captivate experts say.
Good luck!
Transmitted via Bacon
Okay.
Thank you for the help
Kangarooster said:
I'm not entirely sure if this is an issue with my hardware or software which is why I'm asking where I should look (or start a thread) first. I've had sound before but now there is nothing, not even crackling or popping. I'm using Cyanogenmod 11 on a Samsung Captivate. I read a thread about loosening a screw near the speaker and tried that (along with a not-so-deep tear-down), but still not a peep (or beep). Something I should mention is that headphones DO work when they're plugged in. Additionally I've done some scouring of the Internet for a fix but I can't find any problems truly similar to mine.
Click to expand...
Click to collapse
It does sound like hardware. Have you tried slightly pushing on the speaker? I tends to come loose.
If you have any flashing experience, you can try flashing stock to completely rule out software issue but since the aux works, I'm pretty sure it's hardware.
I have tried pushing on the speaker. The only reason I was thinking it might be a software issue is because I changed some of the settings in what I believe is called dsp. Before I flash it back to the stock software (firmware?) is there any other troubleshooting I could try? Putting Cyanogenmod on it was somewhat of a process and overall I like it. And if it is a hardware problem how much would it cost to fix (not that I have any money to do so anyway )? And before I end this reply, thank you for your help.
Kangarooster said:
I have tried pushing on the speaker. The only reason I was thinking it might be a software issue is because I changed some of the settings in what I believe is called dsp. Before I flash it back to the stock software (firmware?) is there any other troubleshooting I could try? Putting Cyanogenmod on it was somewhat of a process and overall I like it. And if it is a hardware problem how much would it cost to fix (not that I have any money to do so anyway )? And before I end this reply, thank you for your help.
Click to expand...
Click to collapse
You could always flash CM over and that would rule out the system file possibility.
Was the problem there before flashing CM? And I have a neat little guide on how to flash in my "most thanked" posts if you need it to get back to CM after flashing stock.
BWolf56 said:
You could always flash CM over and that would rule out the system file possibility.
Was the problem there before flashing CM? And I have a neat little guide on how to flash in my "most thanked" posts if you need it to get back to CM after flashing stock.
Click to expand...
Click to collapse
I actually don't remember if the problem was there or not as I flashed CM on it pretty much as soon as I got it. Can I just start from the "install from zip" process to reflash CM on it? In the meantime I'll see if I can do that without there being any potential problems with bricking the phone etc. And thank you for being patient with me .
Kangarooster said:
I actually don't remember if the problem was there or not as I flashed CM on it pretty much as soon as I got it. Can I just start from the "install from zip" process to reflash CM on it? In the meantime I'll see if I can do that without there being any potential problems with bricking the phone etc. And thank you for being patient with me .
Click to expand...
Click to collapse
Yeah, just flash the ROM zip and the Gapps over your current one. It's called a "dirty flash" and will only wipe your system settings.
I was celebrating St. Patrick's day which is why I haven't replied sooner, apologies. Anyway, I will do that, although I learned from the previous owner that the sound was going out so now I'm 99% positive that it's the hardware. Is it okay for me to mention that replacement speakers appear to be relatively cheap (and possibly easy to install)? And one last question, for the future, is it more polite to leave the quote in the reply rather than take it out?
Kangarooster said:
I was celebrating St. Patrick's day which is why I haven't replied sooner, apologies. Anyway, I will do that, although I learned from the previous owner that the sound was going out so now I'm 99% positive that it's the hardware. Is it okay for me to mention that replacement speakers appear to be relatively cheap (and possibly easy to install)? And one last question, for the future, is it more polite to leave the quote in the reply rather than take it out?
Click to expand...
Click to collapse
You should keep the quote, it notices the user you quote and that way, he can reply faster (me in this case).
And yeah speaker replacement is definitely an option. You should be able to find a quick video guide on youtube, I believe it's fairly easy to do.
BWolf56 said:
You should keep the quote, it notices the user you quote and that way, he can reply faster (me in this case).
And yeah speaker replacement is definitely an option. You should be able to find a quick video guide on youtube, I believe it's fairly easy to do.
Click to expand...
Click to collapse
I put an older CM version (that was under the stable category) on to see if it was the software and I checked with the previous owner to see if the sound was going out (it was). There still isn't any sound so it's definitely the hardware. Now the question is; do I spend money to replace the speaker on an old phone that I don't really need?
That'd probably be a different thread though.
Thank you for your help!
Kangarooster said:
I'm not entirely sure if this is an issue with my hardware or software which is why I'm asking where I should look (or start a thread) first. I've had sound before but now there is nothing, not even crackling or popping. I'm using Cyanogenmod 11 on a Samsung Captivate. I read a thread about loosening a screw near the speaker and tried that (along with a not-so-deep tear-down), but still not a peep (or beep). Something I should mention is that headphones DO work when they're plugged in. Additionally I've done some scouring of the Internet for a fix but I can't find any problems truly similar to mine.
Click to expand...
Click to collapse
flash neatkernel with cm11 rom http://forum.xda-developers.com/samsung-captivate/development/recovery-cwm6-philz-touch-t3030931. solved my speaker problem. stock cm11 kernel has speaker bug.
brandonabandon said:
flash neatkernel with cm11 rom http://forum.xda-developers.com/samsung-captivate/development/recovery-cwm6-philz-touch-t3030931. solved my speaker problem. stock cm11 kernel has speaker bug.
Click to expand...
Click to collapse
Does it really? I thought for sure it was hardware related, but if there's a way around spending too much money I'm all for it, thank you!
So I installed it and still nothing. But still thank you.
Kangarooster said:
So I installed it and still nothing. But still thank you.
Click to expand...
Click to collapse
cappy speakers on ebay for next to nothing.
brandonabandon said:
cappy speakers on ebay for next to nothing.
Click to expand...
Click to collapse
So, I think I know how to replace/install the speaker and I've watched a video or two on the process. Would you have any do's or don'ts, tips, et cetera?
I got my hands on an old Incredible S and found this great forum. I started following the steps in http://forum.xda-developers.com/showthread.php?t=1705913, but stuck on the section 2 because revolutionary.io is unreachable atm and the key cannot be generated (though I got the revolutionary-0.4pre4.zip file from somewhere by googling it). I have no idea if I'm forsaken... It looks like the site has also been gone up and down a few times before, but I'm not sure if it's going to come back to life again.
1. Did anyone experience this before? How many days did you wait for revolutionary.io to come back up?
2. If revolutionary.io is really gone for good, can I still write a custom ROM on my Inc. S? If so, what are my options? (Many custom ROMs seem to require S-OFF...)
3. Assuming revolutionary.io comes back again later, I'm thinking of using one of ARHD 6.0, VivoKat, CyanVivo X Reborn, or even the old cm-7.2.0-vivo.zip one. My No.1 priority is stability and battery life, but I'll be keeping wireless on most of the time (without automatic syncing). I don't value eye-candies or animations (I'll turn them all off), and want maximum free memory. Still camera and FM radio should work flawlessly. What will be the right choice in such a case?
Got the same problem here, although I want to S-OFF a Desire S. But this time there is no DNS-record for the website, which looks more like "someone hasn't paid their bills" than "the server is just offline". I hope it will come back shortly!
OK, I gave up on S-OFF path and took the other path described here. I tried ARHD 6.0, VivoKat, CyanVivo X Reborn, and also the original ICS rom from HTC. All worked fine.
Edit: sorry, wrong information
poondog said:
I know this is a bit late
The team took down their old services and are only supporting the newest sunshine which is a $25 cost
Its for newer devices idk if it works on vivo and saga but thats why you dont get the connection anymore
Click to expand...
Click to collapse
neither beaups nor myself had anything to do with revolutionary, nor did we have anything to do with (nor even know) it being taken down
spreading erroneous info like this, just pisses people off, and makes me deal with drama that has absolutely nothing to do with me. Something that i would rather not have to deal with.
http://rev.alpharev.nl/ <<<< try this <<
tkMOK said:
http://rev.alpharev.nl/ <<<< try this <<
Click to expand...
Click to collapse
yes but do it from a linux box, or else you will get the wrong site from some reason.
http://imgur.com/647I8bP
So i rooted my new nexus 6 and installed chroma rom. every thing was fine till i noticed a small part of the screen flicker. it was like a black line coming and going as soon as i took it off charging it was fine. this was after i installed the rom there was nothing like this on the stock one. also when i open the camera app i can hear a small click/ crackle sound. this happened in the stock rom too but with the snapchat app. its irritating and i cant find a fix anywhere. and lastly whats with the network issue? it suddenly comes and goes. i checked it and it showe 0dbm and 99 asu?is this common? tried to find a fix but all i got was lots of unanswered threads. as being a student who need to use this phone for a long time can anyone tell me if all this is fixable ? or do i need to get a replacement as im still in my 30 day return period. thanks in advance and sorry if all this issues are already in a post and have fixes just post me the link as i could find it
being a student who needs the use of the phone for long periods of time.. what are you foing moddifying your device. no custom rom will be bug free. even though whtyever bugs dont bother me, they seem to bug you. why dont you just stay stock with root if those issues are bugging you.
simms22 said:
being a student who needs the use of the phone for long periods of time.. what are you foing moddifying your device. no custom rom will be bug free. even though whtyever bugs dont bother me, they seem to bug you. why dont you just stay stock with root if those issues are bugging you.
Click to expand...
Click to collapse
I know no roms are bug free, just wanted to know if these are common software issue and not a bad device that i got. And on the other hand i used my s3 for 2.5-3 yrs with custom roms and stuff simply as i enjoy running them and seeing all the amazing stuff people can do with skill that was the main reason i got a nexus
about_99_ninjas said:
I know no roms are bug free, just wanted to know if these are common software issue and not a bad device that i got. And on the other hand i used my s3 for 2.5-3 yrs with custom roms and stuff simply as i enjoy running them and seeing all the amazing stuff people can do with skill that was the main reason i got a nexus
Click to expand...
Click to collapse
honestly, ive never run into the issues that you decribed.
simms22 said:
honestly, ive never run into the issues that you decribed.
Click to expand...
Click to collapse
So i should request for a replacement ?
about_99_ninjas said:
So i should request for a replacement ?
Click to expand...
Click to collapse
give motorola a call for sure, they themselves might suggest a replacement.
simms22 said:
give motorola a call for sure, they themselves might suggest a replacement.
Click to expand...
Click to collapse
Well i bought online from someother store so I'll get it changed. Need to flash the stock rom first thanks anyways