Hey guys, so I was looking into buying the a used Motorola Defy since the TMOUS version can work on AT&T's 3G. I was just wondering if there are any general hardware-related problems that are common for Defy users.
For example, I know the LG Optimus 2X/G2X had a lot of problems with freezing and stuff, and my old Samsung Vibrant was known for having terrible GPS connection.
On a side note, how is CyanogenMod (either 7, 9, or 10) as far as bugs are concerned? I tried looking into the bugs but it's kinda hard to tell without being familiar with the Defy dev scene.
Thank you!
There was a problem with early defy where the phonespeaker doesn't work. The newer ones doesn't have this problem.
Cyanogenmod 7 is really stable and bugfree.
cyanogenmod 9 isn't in development anymore, so it isn't really stable or bugfree.
Cyanogenmod 10 works really good and is bugfree for me, however aokp jb works even better for me.
Exactly what I wanted to know. Thanks!
Sent from my HTC Sensation using xda app-developers app
Sorry for double-posting but there was another thing I was wondering. I keep reading about Red/Green Lens models, and how Green lens ones won't have a working camera if it's upgraded to gingerbread or something like that. Is that still true, or has it been fixed?
I can confirm the speaker problem. the stock ROM had Bluetooth problems too. Although that might just be a anti piracy measure butI couldn't send/ receive apks and later I couldn't send any files without using third party Bluetooth applications (Bluetooth File Transfer). But now I am running CM10 ( Hail quarx!!) The Bluetooth issue is solved but the speaker still stops playing music suddenly.
I wonder if there is a fix??
Sent from my MB525 (Running quarx's CM10 0912 nightly) using xda app-developers app
phantomsniper773 said:
Sorry for double-posting but there was another thing I was wondering. I keep reading about Red/Green Lens models, and how Green lens ones won't have a working camera if it's upgraded to gingerbread or something like that. Is that still true, or has it been fixed?
Click to expand...
Click to collapse
There are actually 3 Versions. The Defy MB525 with the Green Lense, The defy MB526 (the defy +), and the Defy MB525 with the redlense.
The redlense defy and the defy + are pretty much the same except the battery. The Greenlense defy is different because it has a different camera module. For some reasons motorola only gave an update to gingerbread for the defy+ and the redlense.You can also flash it on a green lense def but your camera wont work(kernel related issues).But if you choose to run a custom firmware you wont have those problems. Due to the fact that we found a way to run custom kernels some days ago, the problems with the camera module are gone in the future.
Oh, I see. So from what I understand after reading up a little bit more, the green lens camera should be working identically to the red lens, except only the red lens can do 720p. Is that correct?
But if 720p recording isn't all that important to me, the green lens should be fine for running all custom ROMs as well as the red lens, right?
my phone ran in to a problem where the search buttons led would not work however gave it to the service center and they replaced the part,i thing it was only my phone having this problems, anyways go ahead and buy the defy
Some
Hey there,
The common problems i can confirm is the ear piece speaker problem still occurring on the MB526's (Defy+).
The only other problem i occur qua hardware is the digitizer freaking out from time to time. it's usually fixed with a lock/unlock.
That's all i can tell from my experience with my defy+ for over a year
Related
I.m not a dev.
Just wandering why it's harder to make green lens work well than red lens.
Sent from my MB525 using XDA App
Would CM9 surpport both green&red lens?
Sent from my MB525 using XDA App
I think it's because Defy+ (where the Gingerbread kernel comes from) has basically the same hardware as the red camera Defy, but the green camera one is different.
I think he meant 'why' is it difficult to make Gingerbread work(with all the features) on the green lens. I'm not a dev either but afaik the Green lens(SOC module) is actually better than the Red lens(BAYER module) since the SOC module/OmniVision OV5642 sensor is also used in Iphone 4 and Iphone 4 has one of the best 5mp cameras around. Its Motorola who screwed up with the drivers for this module and tried to cover up their failure by changing the Defy+ module. Kinda gives you feeling that we Defy owners are the abominated human test subjects of a failed experiment doesn't it?
Anachronizer said:
Kinda gives you feeling that we Defy owners are the abominated human test subjects of a failed experiment doesn't it?
Click to expand...
Click to collapse
Not really, no. It's just a product. A product that does things which your grandparents would not have believed possible. And yet we complain about it. Talk about ungrateful!
Anyway...the only hardware difference between the red and green lens Defy is the camera module. The stock Eclair and Froyo ROMs for the Defy included software modules for both camera types - it you look in logcat you can see the logs of the camera application detecting which hardware module is present, so it can call up the correct software modules to make it work.
The Defy+ is only manufactured with the red lens camera - Motorola have obviously given up on the green lens one following their failure to get it working properly with their chosen processor. (It does work, they just didn't manage to get all the features of the module to work properly with the OMAP processor - Apple use the same Omnivision camera module for 720p recording in the iPhone 4!) Thus the stock Gingerbread ROMs for the Defy+ do not include any support for the green lens camera. AFAIK you can put a Defy+ ROM on a green lens Defy and it will work except for the camera - I think someone tried it on this thread. Thus for developers to make a Gingerbread ROM which works on a green lens Defy, they have to integrate the green lens software modules from a pre-Gingerbread ROM along with the stock red lens stuff - but that's all. Everything else is the same.
Actually, developers don't necessarily even have to do that - the greenbread mod is designed to be installed on phones running Gingerbread ROMs to make the green lens camera work with no other changes required to the ROM.
ejstubbs said:
Not really, no. It's just a product. A product that does things which your grandparents would not have believed possible. And yet we complain about it. Talk about ungrateful!
Click to expand...
Click to collapse
Really? Defy has features my grandparents would not have believed possible? You knew my grandparents that well? Well then no wonder someone of your age would be so impressed by the Defy..you just never thought it was possible back in your time.
Know what, if you were so miffed at me for criticizing Motorola there are better insults available..try googling a few. Regardless, I wasn't exactly criticizing the Defy as a phone, au contraire, its one helluva phone, I use it myself and I love it. I was rather critical of the way Motorola handled it. Instead of making this already great device even greater with further software updates, they dumped it for a slightly improved iteration of the exact same thing with total disregard for the Defy's existing customer base. I don't know how you feel about it and frankly I don't care but I myself feel betrayed as a customer and nothing anyone can say will make me feel otherwise. For some further enlightenment on this topic pay a visit to the official Motorola support forums.
Hello, I have been following the development of CM9 for a while now. Almost all roms can not get the camera working. I read there is a change in the framework and that is why it is now hard for older phones. But what has changed to stop the camera? Is the camera a hard device to get drivers for? Any clarity would be amazing just so I can understand the issue. Many thanks
It's only a matter of time I think before they get it sorted.
I just tried my first ICS based rom yesterday on my SGS2 and it is almost perfect, really good.
Camera works, but no video function (for me anyway!)
Exciting times.
I agree with thomss79. "Only a matter of time". Also the drivers are important. Looking through the threads on here, some drivers, and or source code, has been released for the Atrix from Nvidia and Moto. Not sure if that will help ICS, camera (and kernel) tho. Anyway, the devs on here should sort it out before too long. Thought i would be stuck on Froyo ( 2.2.2 ) forever. Unlocked and tried nearly all roms now, including early ICS
I heard drivers were an issue for CM9. I'll wait A LOT before installing ICS anyway, CM7 took a long time to get to this (awesome) point, and I will NOT switch to a less functional ROM just because it looks prettier. I'm extremely happy with CM7 for the time being.
I understand that the camera is not working on CM9 build....and that's ok for now but is there a reason why my gallery is not working?
I can't seem to view mms messages or downloaded pics
ramier said:
I understand that the camera is not working on CM9 build....and that's ok for now but is there a reason why my gallery is not working?
I can't seem to view mms messages or downloaded pics
Click to expand...
Click to collapse
Try using quickpic.
When i was on my captivate camera (video and image) worked great on CM9.
Sucks that i'm using a nokia dumbphone atm.
They've had their hands full.. in due time we will have a 100% functioning rom.
Sent from my MB860 using xda premium
JaronBang said:
They've had their hands full.. in due time we will have a 100% functioning rom.
Click to expand...
Click to collapse
I hope so.
Kayen said:
Try using quickpic.
When i was on my captivate camera (video and image) worked great on CM9.
Sucks that i'm using a nokia dumbphone atm.
Click to expand...
Click to collapse
thanks for the tip. quickpic works great. have access to my pics
Regarding why, as far as I know it's due to camera API changes in ICS. This causes troubles for the way cameras work earlier, and requires new driver. Again I'm not completely sure, this is just something I picked up in other threads. On a side note, the camera is mostly working in turl's new builds (and jokersax's) over at http://forum.xda-developers.com/showthread.php?t=1445052 as I'm sure you're aware . Hope that clears some confusion!
Issues when downgrading
Though I was just fiddling around with CM9 and Ice cream sandwich, when I downgraded back to 2.3.4(stock), the camera app refused to work. Camera app just crashes. Is there any permanent change that CM9 does to the device interface that may be causing this.
Thanks
Shouldn't be anything permanent. How did you revert to stock?
Sent from my MB860 using xda premium
Running CM9 with camera & video camera
I am running CM9 Turl's V8 and have installed camera 360 which runs great. found that in Turls CM9 thread. And people are using video illusion for video recorder. Problem solved
LeonIrv said:
I heard drivers were an issue for CM9. I'll wait A LOT before installing ICS anyway, CM7 took a long time to get to this (awesome) point, and I will NOT switch to a less functional ROM just because it looks prettier. I'm extremely happy with CM7 for the time being.
Click to expand...
Click to collapse
You really just dont know what you're missing. The camera DOES work...to everyone saying it doesnt...well, thats just not 100% true. There are significant problems, some lag and delays, but it IS functional.
Using a camera app usually cures all the problems tho.
gastromagig said:
Though I was just fiddling around with CM9 and Ice cream sandwich, when I downgraded back to 2.3.4(stock), the camera app refused to work. Camera app just crashes. Is there any permanent change that CM9 does to the device interface that may be causing this.
Thanks
Click to expand...
Click to collapse
I'd suggest formatting /system and then do a regular data wipe then reinstall and see if that works.
+1, camera is working, running cm9 as my daily
Reverting breaks camera
ehvio said:
Shouldn't be anything permanent. How did you revert to stock?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
KH_Lionheart said:
I'd suggest formatting /system and then do a regular data wipe then reinstall and see if that works.
Click to expand...
Click to collapse
I flash the stock rom using fastboot, i.e. fastboot flash system system.img, so I'm assuming that would format the /system directory. Im still a noob at this so any advice would be much appreciated. Also, the camera does not work in the new cm9 beta, so I am assuming there is some sort of firmware issue with the camera.
Thanks
I would definitely try reflashing, cause the camera is working for me on Jokersax's latest build.
front camera
Also, the front camera works when I use camera 360, so it seems to be a device driver/ firmware issue. Anyone else having similar problems?
My Atrix was having issues while on stock 2.3.6 with initializing the camera and the led. Now I can sort of activate the led with the stable CM7 release. But still no camera, it says it can't connect. Could this be a hardware issue?
Try flashing some other roms first and see if that fixes it but it does sound like a hardware issue from what you said. After all, the atrix was designed by high school kids so you can't expect a lot from it.
I have this same issue.
Atrix_Owner said:
Try flashing some other roms first and see if that fixes it but it does sound like a hardware issue from what you said. After all, the atrix was designed by high school kids so you can't expect a lot from it.
Click to expand...
Click to collapse
Still a really good phone design overall, much better than the highly educated "geniuses" at Apple. The front camera works with all my current rom setups, so does this mean that I just buy a new camera?
I have the same problem for cm7
Hey guys,
I am the Android engineer responsible for the video playback and recording components on the Vine for Android app. We noticed that there is a bug on a rooted 4.2.2 ROM (mostly S2, prob CM related) that it did not implement one of the camera method (specifically, onPreviewFrame, the data returns null when using image buffering) that we are relying on to work properly. Just want to let you guys know what the problem is.
Best,
Edison Wang
Vine Labs (Twitter Inc.)
I'm on CM10.1 (4.2.2) on my Nexus S and I still have the "Initializing" problem after the update.
@op you do know about the open source camera s2 use ,you can look into that
Replicant guys made it
Sent from my GT-I9100 using xda app-developers app
Recording worked when I was on stock 4.1.2 rom, but it force closes upon recording when I'm on cm10.1. Is there an easy fix for this?
wzsddtc2 said:
Hey guys,
I am the Android engineer responsible for the video playback and recording components on the Vine for Android app. We noticed that there is a bug on a rooted 4.2.2 ROM (mostly S2, prob CM related) that it did not implement one of the camera method (specifically, onPreviewFrame, the data returns null when using image buffering) that we are relying on to work properly. Just want to let you guys know what the problem is.
Best,
Edison Wang
Vine Labs (Twitter Inc.)
Click to expand...
Click to collapse
Any news on this bug fix?
Vine crash
I'm on latest update of Vine.
It still crashes less than a second after recording. I keep on sending crash reports hoping they can fix it.
I am running X-treme JB rom v9 with Dorimanx kernal. Android 4.2.2.
Best ROM I've ever used. Everything else works great but I just want Vine to work!
wzsddtc2 said:
Hey guys,
I am the Android engineer responsible for the video playback and recording components on the Vine for Android app. We noticed that there is a bug on a rooted 4.2.2 ROM (mostly S2, prob CM related) that it did not implement one of the camera method (specifically, onPreviewFrame, the data returns null when using image buffering) that we are relying on to work properly. Just want to let you guys know what the problem is.
Best,
Edison Wang
Vine Labs (Twitter Inc.)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=43063033&postcount=24753
Cheers!
Enviado desde mi GT-I9100
new update
vine has updated.
they say its the biggest update yet for android and has new shooting options ansd camera options etc.
might be worth trying again with a 4.2.2 rom to see if it works.
i am sticking with neatrom for the min (4.1.2) as it works with instagram and vine. once both aps work with 4.2.2 aosp and aokp based roms i will go back. i miss halo and pie
hetster said:
vine has updated.
they say its the biggest update yet for android and has new shooting options ansd camera options etc.
might be worth trying again with a 4.2.2 rom to see if it works.
i am sticking with neatrom for the min (4.1.2) as it works with instagram and vine. once both aps work with 4.2.2 aosp and aokp based roms i will go back. i miss halo and pie
Click to expand...
Click to collapse
Thanks for the info. Just updated and it still crashes. Unlike last time it would be half a second, now it's instant.
However! Using the front facing camera works! Progress?
jkne said:
Thanks for the info. Just updated and it still crashes. Unlike last time it would be half a second, now it's instant.
However! Using the front facing camera works! Progress?
Click to expand...
Click to collapse
i think its going to be a long wait. most aosp roms are based on CM. the problem is CM use a hacked rear camera with higher resolution. aps are created using normal android firmware so dont take into account the new hacked camera. unfortunately i think the makers of vine will see modified firmware user base as quite small so not bother to change their app and CM is unlikely to undo a better camera for the sake of 2 aps (same bug is in instagram video for the very same reason as vine)
neatrom works with them all as they are based on original samsung firmware but i prefer aosp roms but till the bugs for these 2 aps are sorted i'll have to stick to neatrom as 80% of what i do on my phone is instagram or vine related. oh well
full explanation from dorimax here
http://forum.xda-developers.com/showpost.php?p=43063033&postcount=24753
WTFFF
wzsddtc2 said:
hey guys,
i am the android engineer responsible for the video playback and recording components on the vine for android app. We noticed that there is a bug on a rooted 4.2.2 rom (mostly s2, prob cm related) that it did not implement one of the camera method (specifically, onpreviewframe, the data returns null when using image buffering) that we are relying on to work properly. Just want to let you guys know what the problem is.
Best,
edison wang
vine labs (twitter inc.)
Click to expand...
Click to collapse
how can you not fix this? We are waiting!!!!!!!!!!!!!!
bombsofgold said:
how can you not fix this? We are waiting!!!!!!!!!!!!!!
Click to expand...
Click to collapse
I wish either Vine or CM and X-treme could come up with some kind of workaround.
I am missing a lot of moments that a standard photograph cannot capture and a video is too cumbersome.
I'm having to use my girlfriends iPhone when I have perfectly good Android hardware in my pocket!
By the time I have the iPhone in my hand and unlocked the precious 6 second moment is gone, FOR EVER.
Come on Vine! Can't you enable a compatibility mode or anything? :crying:
X-treme Rom v10 will be ready soon by the looks of things. Looking forward to it!
Does anyone know if this will fix the problem? (cannot currently write on all threads as I haven't enough posts)
@wzsddtc2
Nasty bug. Vine seems to be the only app on cm 10.2 that does not work..
with the latest update they outright claim your device is not supported. (It worked perfectly on Official 4.1.2 roms)
is this going to be fixed?
chuckiler said:
@wzsddtc2
Nasty bug. Vine seems to be the only app on cm 10.2 that does not work..
with the latest update they outright claim your device is not supported. (It worked perfectly on Official 4.1.2 roms)
is this going to be fixed?
Click to expand...
Click to collapse
That's be cause we are probably the only app that uses that special method that Samsung broke.
The same bug happens on S4's front facing camera driver, but Samsung has provided a workaround for that (we post-process the images).
On Cyangenmod, the problem is they don't even pass back a bad frame, it just passes back nothing, so we can't apply any workarounds there.
hetster said:
i think its going to be a long wait. most aosp roms are based on CM. the problem is CM use a hacked rear camera with higher resolution. aps are created using normal android firmware so dont take into account the new hacked camera. unfortunately i think the makers of vine will see modified firmware user base as quite small so not bother to change their app and CM is unlikely to undo a better camera for the sake of 2 aps (same bug is in instagram video for the very same reason as vine)
neatrom works with them all as they are based on original samsung firmware but i prefer aosp roms but till the bugs for these 2 aps are sorted i'll have to stick to neatrom as 80% of what i do on my phone is instagram or vine related. oh well
full explanation from dorimax here
http://forum.xda-developers.com/showpost.php?p=43063033&postcount=24753
Click to expand...
Click to collapse
That's not true. We saw the log from CM's bug tracker, it is entirely on their side and they just won't admit it.
Apps will request 640x480 preview size, but CM will report it succeeded but record at 720x480, which is a higher resolution.
We use onPreviewFrame() to get video frames and expect 640x480 frames, but CM will give frames at 720x480.
Because we give buffer frames at the smaller size, CM will treat them as invalid buffers and then just drop the frames.
Totally insane.
I'm using a t0ltetmo with the newest Carbon Nightly and Vine recording doesn't work.
Do you guys have a list of custom ROMs that is compatible with your app?
This is a bit annoying.
Hi there, Vine still doesn't work
Did you give up ?
(Sorry wrong thread)
orangeraf said:
Hi there, Vine still doesn't work
Did you give up ?
(Sorry wrong thread)
Click to expand...
Click to collapse
Yeah I gave up. I got an S4, running AOSB and everything is working well.
The S2 is a backup phone now.
ok so apparently no one fixed this issue.. i tried a bunch of cm based roms and different versions of android and ive found problems with video upload to instagram (upload bar just stuck at middle and wont go on), vine app wont work (it just tells me that im using custom rom and there's a problem with camera), upload videos to twitter also stuck.. so it seems to me that the problem is with CM kernel and video format.
still cant believe that no one addressed this issue over 2 years now, im stunned
Hi guys, just jumped to android from ios and im having some issues (camera has black screen and freezes with camera failed), front facing camera works). Basically ive seen a lot of fixes for the rear facing camera on the S4, clearing the cache etc. None of them work, i was planning on rooting the phone as well, ive seen a few posts saying this sometimes fixes the issue with a new rom and kernel.
Does anyone have experience of this working and can recommend a custom rom for me? Just before i start ordering parts for it.
Thanks in advance!
What firmware are you on?
Sounds like the flex cable for the camera is not seated correctly. Depending on your firmware, you will not be able to flash any new roms for awhile. I suggest warranty replacement if you are on MF3. If you are on MDL, read up on rooting and ROMs. There is vital info you need to know. A new ROM might fix it if it isn't a flex cable issue.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app