hi guys im on latest JB mod by Quarx and i got some issues with my buttons, the Search button on my defy is noticesably more brighter than the other 3 (which always happens when i flash kernel other than froyo).. i tried to edit light sensor but it always "force close" when i try to apply the new settings... any suggestion that would help?
thanks Guys!
trixhammerbord said:
hi guys im on latest JB mod by Quarx and i got some issues with my buttons, the Search button on my defy is noticesably more brighter than the other 3 (which always happens when i flash kernel other than froyo).. i tried to edit light sensor but it always "force close" when i try to apply the new settings... any suggestion that would help?
thanks Guys!
Click to expand...
Click to collapse
Read on my older posts. if you have read you would have found a solution.
Sent from my MB526 using xda app-developers app
Related
does anybody know app (or any other way) to test if trackball LED is working?
i want to check wether my trackball does not lit because it's broken or maybe because of some SW bug.
please, don't tell me to flash stock rom
thanks in advance
deadwilder said:
does anybody know app (or any other way) to test if trackball LED is working?
i want to check wether my trackball does not lit because it's broken or maybe because of some SW bug.
please, don't tell me to flash stock rom
thanks in advance
Click to expand...
Click to collapse
What kernel are you using?
and which rom?
I know that in some roms/kernels the LED just doesn't work.
i'm on froyd 1.6 with fly 11c. Pulser said it's working for him...
Its working now... after a reboot and double checking all my settings.
Hi guys u have a standard t mobile mb525 defy rooted with 2ndinit installed the problem i have is i have no camera preview when i open the camera its like theres something over the lens its just black but if i take a picture and go to the gallery its taken the picture fine it also does the same when trying to play videos
Can anyone please help?
Sent from my MB525
Anybody?
Sent from my MB525
What ROM are you on?? Since when you are having the problem??
Just the standard t mobile on that came with the phone i only noticed the problem few days after i rooted it :'(
Sent from my MB525
m0nk3yb0y94 said:
Just the standard t mobile on that came with the phone i only noticed the problem few days after i rooted it :'(
Sent from my MB525
Click to expand...
Click to collapse
Try to re-flash your stock sbf. And root it again..
Doesn't matter from where I send it, what matters is written above
@m0nk3yb0y94
Have u tried to delete data of the camera under
settings >apps >manage apps > all > camera > delete data
Also try some other camera app.. 'Camera360' for example.
Doesn't matter from where I send it, what matters is written above
m0nk3yb0y94 said:
Hi guys u have a standard t mobile mb525 defy rooted with 2ndinit installed the problem i have is i have no camera preview when i open the camera its like theres something over the lens its just black but if i take a picture and go to the gallery its taken the picture fine it also does the same when trying to play videos
Can anyone please help?
Sent from my MB525
Click to expand...
Click to collapse
This is caused by 2nd-init
Did you flash 720p patch?? If you did then you wil get black screen for preview. Go to 2nd-init and select boot as normal boot. It should work
PS. I had to reflash stock rom, root, install 2nd-init and then NOT apply the 720p patch!
Can anyone tell me what are the bugs for CM9 on galaxy y? And can I use 3rd party apps to solve the bugs??
Sent from my GT-S5360 using xda premium
please refer to the official CM9 beta thread by whitexp,
if he did not post any fix then it is not yet resolved,
don't create threads for this
Hey bro............it's to buggy to mess with...
humaid.locastic said:
Can anyone tell me what are the bugs for CM9 on galaxy y? And can I use 3rd party apps to solve the bugs??
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
Bro we only have 1 working version of cm9 by white xp and that also in a pre-beta stage , I would be unable to tell u the bugs as there are only few things working. Here my gusses:-
touch screen working in v0.3
booting successfully :silly:
pre installed apps can be opened without any force close bug.
auto rotation fixed (in 0.2)
nothing else is working even the network isn't coming , the phone has a colour tint after installing it and each and every other thing is full of bugs.............................
but cheer up atlast we have a bootable version of cm9 on our tiny phone.
thx to whitexp
shivamsejal said:
Bro we only have 1 working version of cm9 by white xp and that also in a pre-beta stage , I would be unable to tell u the bugs as there are only few things working. Here my gusses:-
touch screen working in v0.3
booting successfully :silly:
pre installed apps can be opened without any force close bug.
auto rotation fixed (in 0.2)
nothing else is working even the network isn't coming , the phone has a colour tint after installing it and each and every other thing is full of bugs.............................
but cheer up atlast we have a bootable version of cm9 on our tiny phone.
thx to whitexp
Click to expand...
Click to collapse
hey you finally posted,
good luck,
get 10 posts and release your rom in the dev section,
I am running CM10 latest Quarx build on my Defy+ with bl7 after installing the update, menu button light is not working :crying: Is there any way to get it back I tried rolling it back to the CM7 but no use. Any help is really appreciated. Sorry for my bad English...!!
I have the same problem, and the exact same button
I think the led behind that button is not working anymore...
Try to install the CM as indicated in the topics (respect the steps). Do it from begining carefully (flash the stock ROM).
Same here
Sent from my MB526 using xda app-developers app
Started from the scratch by flashing SBF-->> rooting--->> Installed Cm7 (Quarx build) But still no luck...!!! :crying: Back to Awesome Cm10 by Quarx
hacktheheaven said:
Started from the scratch by flashing SBF-->> rooting--->> Installed Cm7 (Quarx build) But still no luck...!!! :crying: Back to Awesome Cm10 by Quarx
Click to expand...
Click to collapse
If I understood right you wanna install CM7.2. For that to work is good that after flashing stock ROM and installing 2ndinit to reboot and from stable recovery to format data/cache and dalvik on ext3 followed by flashing custom CM7.2 (I suggest you to try another CM7.2 mod).
Thanx for the reply
pgreed said:
If I understood right you wanna install CM7.2. For that to work is good that after flashing stock ROM and installing 2ndinit to reboot and from stable recovery to format data/cache and dalvik on ext3 followed by flashing custom CM7.2 (I suggest you to try another CM7.2 mod).
Click to expand...
Click to collapse
My actual problem is not with the Rom. Menu button light stopped glowing right after shifting from cm7 to cm10 :crying: Sorry for my bad English.
hacktheheaven said:
My actual problem is not with the Rom. Menu button light stopped glowing right after shifting from cm7 to cm10 :crying: Sorry for my bad English.
Click to expand...
Click to collapse
I think the high brightness settings would have burned it
Then there is no way to get it back......!! Wish I didn't mess with that settings....
Sent from my MB526 using xda app-developers app
hacktheheaven said:
Wish I didn't mess with that settings....
Click to expand...
Click to collapse
I didn't messed with buttons lights, and still got 3 burned LEDs. The first to go was "search". A month after that, the "menu" button went dark. Now the "back" is gone too. Just "home" remains with light. I don't think it's a software issue... More likely a project flaw or bad manufacturing (I still use CM7, no tweaks).
Last week I also got a "stain" (a lot of bad pixels) on the center of the screen. Just turned the phone off and put it in the freezer for 12 hours. After that, it was new again (lucky me). Yeah, the famous trick works folks (unfortunally, not for the capacitive LEDs though).
Floripa said:
I don't think it's a software issue... More likely a project flaw or bad manufacturing
Click to expand...
Click to collapse
I'm inclined to agree. It seems fairly common. My menu button LED failed when my Defy+ was around 6 months old and completely stock. I put it down to a hardware failure.
Time for me to claim the Warranty
I will unroot the device and will claim the warranty...!! :good: But only problem is I have to wait untill the device returns back and have to use that ****sung again sorry Typo Samsung* :crying:
Hi All,
I am one of the victims who mistakenly flashed defy+ sbf on a normal defy with green lens. It was bricked for quite some time and then later magically one day DEFYPLUS_U3_4.5.1 134_DFP-231 SBF worked. Now the phone (orginally MB525) only accepts custom ROMS made for MB526 with camera not working. the message i get is "Can't connect to camera". Recently i tried Quarx build made for MB526 (4.1.2) and suprisingly my camera was working fine. The only problem i was having is my phone would not give me a ringtone music when a call comes and the moment i make a call the screen goes off. It will only come back ON when the other party disconnects. Sometimes that will also not happen and i will have to totally restart my phone (i am guessing the sensors are also not working). For some time I tried using option in Accessability saying power button ends call. Volume rocker turn of doesnt work.
Finally, now i am using a WakJIUI Rom based on GB. Everything works perfectly except for camera and sensor. I have a workaround of sensor where i can choose not to have the screen turned off while on call and volume rocker key works like a charm.
Now, the reason why i started this thread is a vauge idea came to me where i am thinking of having a WakJIUI Rom as stable and use Quarks 4.1.2 build as second boot. I have no idea how to use dual boot. i have read forums but they are confusing.
Anybody who can help...
You cannot dual boot Quarx's CM10.
You can flash Quarx's CM10 and Jelly X kernel to fix ringtone bug, and to fix proximity issue there is an option for "Inaccurate proximity sensor" in Settings > Display under CM10
You can try to fix proximity sensor issue, watch the following video: http://youtu.be/uMk1S90MjbY
Sent from my MB526 using xda premium
hackergnome said:
You cannot dual boot Quarx's CM10.
You can flash Quarx's CM10 and Jelly X kernel to fix ringtone bug, and to fix proximity issue there is an option for "Inaccurate proximity sensor" in Settings > Display under CM10
You can try to fix proximity sensor issue, watch the following video: http://youtu.be/uMk1S90MjbY
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks for the insight. One question again : In past when i tried flashing kernal of CM7 and CM9 my phone gets into soft brick mode. where i again have to flash the sbf i mentioned above. i am guessing thats because these kernals are made for MB525. Now that my phone identifies itself as MB526 will this jelly X kernal work....
JadhavN said:
Thanks for the insight. One question again : In past when i tried flashing kernal of CM7 and CM9 my phone gets into soft brick mode. where i again have to flash the sbf i mentioned above. i am guessing thats because these kernals are made for MB525. Now that my phone identifies itself as MB526 will this jelly X kernal work....
Click to expand...
Click to collapse
no, no need to flash any sbf, because it's 2nd-boot
Flash rom, flash gapps, flash jellyx
if you get black screen after bootmenu pull the battery and restart
Sent from my MB526 using xda premium
hackergnome said:
no, no need to flash any sbf, because it's 2nd-boot
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks for the advise man. I did complete data wipe and cache partition. Flashed the Jelly X Kernal, then installed the sister JB. My camera is working fine. Ringtone issue fixed and also thanks to that video maker, my proximity sensor issue is also resolved.
JadhavN said:
Thanks for the advise man. I did complete data wipe and cache partition. Flashed the Jelly X Kernal, then installed the sister JB. My camera is working fine. Ringtone issue fixed and also thanks to that video maker, my proximity sensor issue is also resolved.
Click to expand...
Click to collapse
:thumbup:
Sent from my MB526 using xda premium