Hi,
I have been using Quarx's JB build on my Defy+ for a while. I have noticed a problem with this build - the button LEDs have burned out. First it was the "back" button, and now both the "back" and "home" buttons have burned out. It doesn't lit up while using my device. Only time it lits up is when I adjust the "button backlight brightness", but once I exit from the settings, again the buttons don't glow.
Wanted to know if this is a s/w issue or the hardware has been damaged ? If any of you have the same problem, can you please post the solution to fix this (if possible) ?
Thanks !
do factory reset and wipe again ...
have you flashed the right kernel ?
kernel is the problem of such problems ...
torpedo mohammadi said:
do factory reset and wipe again ...
have you flashed the right kernel ?
kernel is the problem of such problems ...
Click to expand...
Click to collapse
Yeah, everytime I update a new build I do a full data wipe, cache and dalvik wipe. And I am using GB kernel. There was no mention of problems with GB kernel, so I am using GB stock kernel.
PS: This problem started only with Quarx's build, earlier I was using "cherry picks", in that build I didn't find this problem (now they have stopped building CM10 for Defy+).
Also I had read about this LED burnout in Quarx's build long time back, don't remember the link.
Related
Hi, I have a red lense Defy and have just flashed latest Quarx nightly per http://forum.xda-developers.com/showthread.php?t=1432100 but everytime I reboot the phone it takes about 90s to start, and all my settings (wifi, baseband, email etc) have been forgotten - the phone start as if it's a brand new install. Can anyone please point me in the right direction? I have tried reinstalling a few times with no luck. otherwise the rom works perfectly.
bluballe said:
Hi, I have a red lense Defy and have just flashed latest Quarx nightly per http://forum.xda-developers.com/showthread.php?t=1432100 but everytime I reboot the phone it takes about 90s to start, and all my settings (wifi, baseband, email etc) have been forgotten - the phone start as if it's a brand new install. Can anyone please point me in the right direction? I have tried reinstalling a few times with no luck. otherwise the rom works perfectly.
Click to expand...
Click to collapse
I'm having the same problem. Anybody has any clue to fix this?
You may have to flash your stock SBF using RSDLite as upgrading to Cyanogenmod ROMS only writes the system partition. Maybe the other partitions have got corrupted.
I'm not sure though.
Did a search but have not seen any thread on this, so apologies if I have missed something.
I've just encountered this today and not sure what to make of it. i9000 been on CM9 nightly without issues until I woke up this morning, backlight was on (nothing unusual, just emails overnight), but it will not wake up no matter what I pressed (home button, power button etc.). So ended popping the battery out and start it up again.
This is when the strangest thing happen, loaded the usual Galaxy logo screen, then into the CyanogenMod screen, seconds later, it restarted. This boot loop went on forever. Doing VOL UP + HOME + POWER does not get me back into recovery. At this stage, I am on CM9 nightly 20120707, with CWM 6.0.0.3 (I think).
I ended up having to Odin flash back to GB 2.3.6 (XXJVU) and start over again. And I thought that was the end of it. Picked up the latest nightly 20120728 and RC2, and I ended up with the same symptom. I.e. post WIPE (Data / System / Cache) and loaded CM9 of both version (plus Gapps loaded), all ended in the aforementioned bootloop. Have also tried fixed permission as well in between tries to load CM9.
Spent a bit more time on this and I am now on the unofficial CM10 (not that I am complaining ), but this is very strange to me. Has anyone ever experienced this? It seems that I have no way of getting back in CM9.
I was running cm9 nightlies until I flashed cm10 (which is amazing ) and had no issues with it what so ever :S
I don't think I've heard of any cases of what happened to you, happening elsewhere
I'd just stick with cm10
Happened to me, too. I solved the problem flashing a previous build of CM9 and a previous build of Gapps - it seems like Gapps was the problem.
After popping out battery, insert batt., start download mode, Odin flash Semaphore ICS kernel as PDA, re-partition unticked.
Enjoy
The Semaphore dev has a thread about this. A number of people have experienced what you say with a combination of different ROMs and kernels. Check it out on development thread
Sent from my GT-I9000 using xda premium
Cheers for the reply fellas. Will check out Semaphore. Interesting though as I've always thought "stock" CM9 was just easy as.
Hi,
I just upgraded my phone to latest Quarx 4.2.2 build 13/04. Was using Quarx 4.2.1 before.
I installed the zip + latest gaps and did a cache wipe and dalvid cache wipe.
Install went fine and phone booted up BUT: now I can't use my hardware buttons.
Even after I wiped data and installed the 13/04 again still the same issue.
Anyone got an idea?
Have a defy green lense.
Thanks
ipana
Quick update.
I just realised that when I flash the 25/03 build the hardware buttons DO work!?!
Afterwards I flashed the 13/04 build and the hardware buttons do NOT react.
So, my assumption is that there must be something wrong with the 13/04 build...
I'm sorry to sound noobish, but every time I flash a ROM on my Nexus 4 (mako) that isn't a Cyanogenmod build (10.2-20130904-NIGHTLY-mako) , my home softkey becomes completely useless and the AOSP or AOKP keyboard constantly crashes. I was told this is a known bug in certain source codes as far as the keyboard is concerned in 4.2.2 builds, but I'm still mystified by the home button issue and as to why I other people can be using the same ROMs that I can't without a problem. Is there a certain version of GAPPS that I can flash to avoid this problem, or is there a known fix? I always wipe data and cache when flashing, so I'm pretty sure this isn't a user error, other than which version of GAPPS I'm flashing (gapps-jb-20130813-signed.zip).
trevorftard said:
I'm sorry to sound noobish, but every time I flash a ROM on my Nexus 4 (mako) that isn't a Cyanogenmod build (10.2-20130904-NIGHTLY-mako) , my home softkey becomes completely useless and the AOSP or AOKP keyboard constantly crashes. I was told this is a known bug in certain source codes as far as the keyboard is concerned in 4.2.2 builds, but I'm still mystified by the home button issue and as to why I other people can be using the same ROMs that I can't without a problem. Is there a certain version of GAPPS that I can flash to avoid this problem, or is there a known fix? I always wipe data and cache when flashing, so I'm pretty sure this isn't a user error, other than which version of GAPPS I'm flashing (gapps-jb-20130813-signed.zip).
Click to expand...
Click to collapse
The known issue you are talking about is the JSS deadlocks? if yes, then it is not the problem with you.. for you it force closes the keyboard.. are you following the procedure of installing rom properly? are you doing dirty flash (flash without wiping data)? you can find out if gapps is responsible by booting into a freshly installed rom without installing gapps and see if the problem persists..
You should also format the /system partition when you flash a new rom.
For some roms the Home button stop working for me and to fix it I had to install gapps, but most CM based roms I use don't have that issue.
As for keyboard, I always delete the default keyboard from the rom and use Google Keyboard.
Andre_Vitto said:
The known issue you are talking about is the JSS deadlocks? if yes, then it is not the problem with you.. for you it force closes the keyboard.. are you following the procedure of installing rom properly? are you doing dirty flash (flash without wiping data)? you can find out if gapps is responsible by booting into a freshly installed rom without installing gapps and see if the problem persists..
Click to expand...
Click to collapse
Please explain what JSS deadlocks are. I don't dirty flash. I always wipe data. As for the keyboard and home buttons not functioning properly,I have this problem with XenonHD, PACman ROM, AOKP and CM variants.
trevorftard said:
Please explain what JSS deadlocks are. I don't dirty flash. I always wipe data. As for the keyboard and home buttons not functioning properly,I have this problem with XenonHD, PACman ROM, AOKP and CM variants.
Click to expand...
Click to collapse
No your problem is not the jss deadlocks.. it happens when you type very fast or something.. it phone vibrates for like 5-10 sec and then restarts. I dont think its your problem. Sorry mate I have no idea why you are having the keyboard and homescreen issue even when you are are doing a factory reset every time you flash.. and why its not happening with CM 10.2..
Andre_Vitto said:
No your problem is not the jss deadlocks.. it happens when you type very fast or something.. it phone vibrates for like 5-10 sec and then restarts. I dont think its your problem. Sorry mate I have no idea why you are having the keyboard and homescreen issue even when you are are doing a factory reset every time you flash.. and why its not happening with CM 10.2..
Click to expand...
Click to collapse
Well, that's unfortunate. I've found that the RevoltHD ROM doesn't have problems, but that's because it's got integrated GAPPS.
Been having the same issue with my Nexus 4, after installing GAPPS the keyboard crashes and the home button stops responding. Did anyone figured it out by any chance? Thanks.
I still don't know what caused it, but I figured out that more recent nightly versions of those ROMs don't have that problem. I'm using AOKP currently and that used to be a problem ROM.
Take off vibration and sound and all the bells and whistles and your keyboard should be fine if the issue isn't Rom specific. Also, it could be kernel related.....try boosting touch input if nothing else
Sent by flying midget
I get the same problem, I factory reset each time I switch ROMs. I was trying with Vanir a couple of days ago and couldn't get the home button to work, tried OmniROM and it worked perfectly, went back to Paranoid it worked perfectly again, went back to Vanir and it didn't work. Was odd.
Hello Everyone,
Nexus 4
Paranoid Android 4.2Beta1
Franco Kernel
I just upgraded to PA 4.2Beta1 from PA 4.1.......
after installing the rom.....when i use my browser or messenger where we require keyboard....the Keyboard doesnt pop up....whats up with this....and also the back button of my navigation bar doesnt work.......this even happened with carbon rom a few days back...when i was experimenting with it.....but then i restored to PA4.1 due to the above given problems....plz offer a solution to this...
The same problem
keyboards not working
please help me my keyboards are not working . i have installed an custom rom.
Hello all,
My apologies if this is a common issue. I have searched but the only old thread about it is the following:
http://forum.xda-developers.com/showthread.php?t=2190960
and no real answer was suggested there, which is why I am asking it again.
So the issue is the same as in that previous thread: quite often, when I longpress the power button, the menu (to shut down, put it on vibrate mode, ...) does not pop up. The only way to get it back is to hold the power button until the phone shuts down, and then reboot the phone, after which it works again (for god knows how long).
I was rooted (with stock rom) before 4.3, but lost my root when updating to 4.3, so I was on stock ROM without root when the problem first appeared. Now yesterday I rooted again and flashed paranoid android ROM (first factory reset, clearing cache and dalvik cache), but the problem remains.
In that old thread one member solved the problem by flashing the stock kernel, however I have never flashed another kernel so I doubt the kernel is the problem?
If anybody knows the issue and a way to solve it, please let me know, it would be greatly appreciated.
Thanks,
Maarten
You did flash a kernel when you flashed the rom
Wayne Tech Nexus
Hey there
No, as in the first post, I have never flashed another kernel on the nexus. Neither did I flash a new radio.
I had not flashed anything yet when the problem started, I only unlocked the bootloader and rooted my phone when I first got it (but it worked a long time without any problems)
Delete this post
Nobody had this issue ?
Found a solution at last!!
wolfway said:
Nobody had this issue ?
Click to expand...
Click to collapse
After quite a long search and a lot of worries, I finally found THE solution...
https://www.youtube.com/watch?v=d8dbrerUacw
how to get out of factory mode for a s4 but it worked on my N7105
- efs/factoryApp/factorymode/ouvrir avec/editeur de texte/ON
- efs/factoryApp/keystr/ouvrir avec/editeur de texte/ON
I have this issue too. I'm using paranoid Android beta 4 with franco kernel and since The moment o rooted my phone this issue started
Sent from my Nexus 4 using XDA Free mobile app