Develop Bugs

[Q] Defy2ndInit??

Have a Defy with stock 2.2 Froyo dutchversion and have rooted it as i wanted to make some overclock. I also installed Defy2ndInit so i can use the multitouch app thats availble on market but i get some problems with that. When i have it installed my camera wont work as i should! When i open the camera i can't see any preview on the screen! When i take a picture it works but the display is always black.
So black display when recording or taking pictures with Defy2ndInit installed. When i unistall it the camera works fine! Anyone having a clue?

You have to restart your phone once you're entered and you've modified something in 2nd Init.

Buchko said:
Have a Defy with stock 2.2 Froyo dutchversion and have rooted it as i wanted to make some overclock. I also installed Defy2ndInit so i can use the multitouch app thats availble on market but i get some problems with that. When i have it installed my camera wont work as i should! When i open the camera i can't see any preview on the screen! When i take a picture it works but the display is always black.
So black display when recording or taking pictures with Defy2ndInit installed. When i unistall it the camera works fine! Anyone having a clue?
Click to expand...
Click to collapse
I had the same problem, and found a excellent explanation and workaround here (sorry for not pointing to the original thread, I have lost it):
the bootmenu contained in Defy2ndinit has a bug (afaik still not corrected even in newer versions) that cause mis-initialization of video4linux. This leads to black screen in camera viewfinder, but also all video playback (media playback will also lead to a black screen).
The workaround is to boot your defy without lauching bootmenu, i.e. use the default boot feature.
If you need to change something in bootmenu, change it, test it after the reboot, and if everything is ok (except video4linux of course), reboot another time using default boot ( WITHOUT entering bootmenu (do not press volup/down when blue led is on)). As bootmenu was not started, video4linux will initialize correctly and you will have a working cam preview and video playback...

gkai said:
I had the same problem, and found a excellent explanation and workaround here (sorry for not pointing to the original thread, I have lost it):
the bootmenu contained in Defy2ndinit has a bug (afaik still not corrected even in newer versions) that cause mis-initialization of video4linux. This leads to black screen in camera viewfinder, but also all video playback (media playback will also lead to a black screen).
The workaround is to boot your defy without lauching bootmenu, i.e. use the default boot feature.
If you need to change something in bootmenu, change it, test it after the reboot, and if everything is ok (except video4linux of course), reboot another time using default boot ( WITHOUT entering bootmenu (do not press volup/down when blue led is on)). As bootmenu was not started, video4linux will initialize correctly and you will have a working cam preview and video playback...
Click to expand...
Click to collapse
so you mean to say we have to set the boot to normal from 2nd init . and then reboot again so that we bypass the bootmenu ???
Edit : yes you were right . The bootmenu is causing the problem i had set the bootmenu to boot normally (Normal in menu) and hence my camera is working again . is there any workaround for that ? as of now ?

joydeep1985 said:
so you mean to say we have to set the boot to normal from 2nd init . and then reboot again so that we bypass the bootmenu ???
Edit : yes you were right . The bootmenu is causing the problem i had set the bootmenu to boot normally (Normal in menu) and hence my camera is working again . is there any workaround for that ? as of now ?
Click to expand...
Click to collapse
None that I am aware of. You can still install cm7 or other custom rom though, just have to select 2nd init booy as default boot...and always default reboot after using bootmenu. More an annoyance than a critical bug imho...
Sent from my MB525 using XDA App

gkai said:
The workaround is to boot your defy without lauching bootmenu, i.e. use the default boot feature.
Click to expand...
Click to collapse
Thanks, fixed my "black" camera problem too

Excuse me! joydeep1985, I've fixed the problem, but how do I access to the Android Boot Menu again? Because default boot now is normal, the device will not pause at Android Boot anymore.

My Defy+ suffered the blank screen using camera and video after applying 720p patch I tried to reboot in normal way but there was no effect. I tried to unnstall 2ndinit and now it works!

When you reboot defy, immediately after you See the blue led press volume down which will then boot into boot menu. Enjoy!
Sent from my MB526 using XDA App

[ROM][CM7] Defy Pro XT560 Support Thread

This is a support thread for the ROM posted here.
http://forum.xda-developers.com/showthread.php?p=49394355
* It is very important to clear factory data/cache after installing the CM7 rom.
* If your stuck on the android boot screen, connect usb and do a logcat to see what it is crashing on.
* The battery_charger has been replaced in this build as a safety backup to get into bootmenu. Anytime the phone is powered off and then plugged in it will boot to bootmenu instead of the charging screen.

* It is very important to clear factory data/cache after installing the CM7 rom.
Click to expand...
Click to collapse
I make all wipe data/cache and even Dalvik cache before and after install CM7 - but I stuck on the android boot screen.
But note: I made all wipes from CWM, because stock recovery is not works on my phone (only green robot and yellow triangle and that's all - nothing key works, only pull battery helps).
* If your stuck on the android boot screen, connect usb and do a logcat to see what it is crashing on.
Click to expand...
Click to collapse
How can I make this (run logcat)?
Thanks for the advices.

Im not sure the clear data/cache works right in CWM. I have not tested it. To access the menu in the stock recovery hit the Home key.
To output a logcat open a command prompt and run "adb logcat"
If you want to output it to a file use "adb logcat > filename.txt"

so there is some querrys:
- torch app does not work as a flashlight, while it stay in status bar and even task killer wont help
- led notification light does not work at all, i guess there is no app for that and original is missing
- it wont unlock sim card, or lock it while it's unlocked. message is "incorrect pin". previously unlocked on other phone sim works fine. pin correct.
- the reboot menu list wont operate with joystick, only touch.
- both cameras wont work in skype, when forced induce crash.
- dev tools options become a force close
- voice dialer started by long press call button opens in wrong screen orientation and does not work. it work if started from all apps.
- superuser does not ask about allowing su permissions, there is no app listed as allowed su perm. while all super su apps works fine as usual.
- yandex maps app issue. rendering map result is quite not what it should be

I did it! Thanks for stock recovery main key (Home) .
And now some my notes (first, I use Russian language and CM7 has it).
- torch app doesn't work - this right for me too;
- about led - not work too;
- about sim - not check this yet;
- the reboot menu OPERATE for me with D-Pad;
- I don't use Skype;
- dev tools work in full for me;
- all correct about voice dialer;
- it's right too;
- don't install yandex maps yet.

wifi is not work

clxer said:
wifi is not work
Click to expand...
Click to collapse
was't been working for me too, but first reboot solved it
a lot of apps that uses the hardware gpu does not work properly, i guess this is same as camera driver problem and it can't be resolved till motorola releases it freely(only if)
also i am having issue with call ringtone - it rings for fraction of a second and then goes silent

I missed some egl librarires in the build, copying the attached files to /system/lib/egl should correct some of the graphic issues.
retr13 said:
was't been working for me too, but first reboot solved it
a lot of apps that uses the hardware gpu does not work properly, i guess this is same as camera driver problem and it can't be resolved till motorola releases it freely(only if)
also i am having issue with call ringtone - it rings for fraction of a second and then goes silent
Click to expand...
Click to collapse

superdave said:
I missed some egl librarires in the build, copying the attached files to /system/lib/egl should correct some of the graphic issues.
Click to expand...
Click to collapse
antutu now running, mx harddecoding on the other hand dont
yandex. maps still weird

Good Job, and thank you
By the way, Pls tell me how to root defy pro.
I had tried many tools but both fail.

jimway said:
By the way, Pls tell me how to root defy pro.
I had tried many tools but both fail.
Click to expand...
Click to collapse
With poot.apk
http: / / ofimatica-programacion[dot]blogspot[dot]com/2014/02/rootear-telefonos-android-sin-necesidad[dot]html

Any updates?
edit- specifically, does CM7 fix the poor bluetooth A2DP quality of the stock ROM?
Sent from my XT560 using xda app-developers app

No usable phone, no icons, no task-statusbar, only background

Hey Everybody
I have troubles since i clicked a button in my status bar. I removed EVERYTHING from my home and lock screen (i cant even tell witch one i see). There are no Icons at all. only my desktop background is visible and working (animated bubbles). there is no button working except from power button (and its menu to restart). a friend of mine was able to get a screenshot with some button-combination (vol+ + home?)
first: i am not an expert with android, but have a lot of experience in working with Linux shells.
what i have done:
maybe it has something to do with it or not, i don’t know:
i enabled multi view / multi window or extended desktop (sorry i don’t know the name, and as there is nothing shown...)
i opened my status bar and there were some new icons (next to the small watch in the right corner), witch i haven’t seen so far and clicked it. than it opened a "new" screen with only my background.
as i thought it is maybe only a "dead" app i tried to restart my phone. but: there is only that screen working. no PIN question, or something.
i tried to reset dalvic and normal cache. -> no change.
i use RESURRECTION REMIX 5.7.3. on N7100
Recovery TWRP 3.0.2-0 is still working and
i hope somebody can help me to solve my problem without factory resetting. i wont reinstall everything.
thanks a lot

Are you able to restore a TWRP back up? You could try flashing the ROM again without wiping.

theoretically, yes, but i did not have on. so i cannot flash it.

i am searching for an commandline option to change the settings. but i have no clue where to search, and in what files the configuration lies...

LG G4 half-bricked / full unusable

Hi everybody !
I usually (always normally) succeed myself at resolve my phone problems, but this time I can't do anything.
My problem :
I have a LG G4 ; I saw an update of Imperium Rom (v8) this morning, so I installed it, everything worked well until I decided to install a, apparently, ****ed mod on xposed ; and since I have rebooted I can't do anything ; the LG logo shows and just after "UI system as stopped", just one time but, then I can't do anything, screens over screens, can't access parameters, password required, "flex mode" (never saw this before), re-password, system UI restart, loading background, restart system UI; and this in a infinite loop SOOOOO
I decided to reset it, yeah... But I can't access my recovery, wow o/
I followed the step to access it by switch it off and press volume down etc --> It just boot normally, or best in safe mode by magic but same problem ; via parameters but I can't access parameters ; and via ADB buuut my phone isn't recognized even with the complete sdk, drivers, everything you want, there's nothing to do because --> while restarting system UI it deconnects so of course it can be recognized
I removed xposed (while I could still access recovery, as I was thinking it was coming from the xposed module) and so now I can't even access recovery via shutdown menu (as I had put "reboot to recovery" in via Xblast, a xposed module) ; and of course it doesn't change anything
I neeeeed your help so much, I don't mind losing what's on it :crying:

Naerade said:
Hi everybody !
I usually (always normally) succeed myself at resolve my phone problems, but this time I can't do anything.
My problem :
I have a LG G4 ; I saw an update of Imperium Rom (v8) this morning, so I installed it, everything worked well until I decided to install a, apparently, ****ed mod on xposed ; and since I have rebooted I can't do anything ; the LG logo shows and just after "UI system as stopped", just one time but, then I can't do anything, screens over screens, can't access parameters, password required, "flex mode" (never saw this before), re-password, system UI restart, loading background, restart system UI; and this in a infinite loop SOOOOO
I decided to reset it, yeah... But I can't access my recovery, wow o/
I followed the step to access it by switch it off and press volume down etc --> It just boot normally, or best in safe mode by magic but same problem ; via parameters but I can't access parameters ; and via ADB buuut my phone isn't recognized even with the complete sdk, drivers, everything you want, there's nothing to do because --> while restarting system UI it deconnects so of course it can be recognized
I removed xposed (while I could still access recovery, as I was thinking it was coming from the xposed module) and so now I can't even access recovery via shutdown menu (as I had put "reboot to recovery" in via Xblast, a xposed module) ; and of course it doesn't change anything
I neeeeed your help so much, I don't mind losing what's on it :crying:
Click to expand...
Click to collapse
Please ensure you REALLY use the correct key combo! Just saying bla does not tell us what exactly you tried.
If you really can't get in you can try to Boot into download mode
https://m.youtube.com/watch?v=0cbLhpWq5C8
Then use lgup to reinstall stock ROM and do all the stuff again to get twrp, root and a custom ROM.

Naerade said:
Hi everybody !
I usually (always normally) succeed myself at resolve my phone problems, but this time I can't do anything.
My problem :
I have a LG G4 ; I saw an update of Imperium Rom (v8) this morning, so I installed it, everything worked well until I decided to install a, apparently, ****ed mod on xposed ; and since I have rebooted I can't do anything ; the LG logo shows and just after "UI system as stopped", just one time but, then I can't do anything, screens over screens, can't access parameters, password required, "flex mode" (never saw this before), re-password, system UI restart, loading background, restart system UI; and this in a infinite loop SOOOOO
I decided to reset it, yeah... But I can't access my recovery, wow o/
I followed the step to access it by switch it off and press volume down etc --> It just boot normally, or best in safe mode by magic but same problem ; via parameters but I can't access parameters ; and via ADB buuut my phone isn't recognized even with the complete sdk, drivers, everything you want, there's nothing to do because --> while restarting system UI it deconnects so of course it can be recognized
I removed xposed (while I could still access recovery, as I was thinking it was coming from the xposed module) and so now I can't even access recovery via shutdown menu (as I had put "reboot to recovery" in via Xblast, a xposed module) ; and of course it doesn't change anything
I neeeeed your help so much, I don't mind losing what's on it :crying:
Click to expand...
Click to collapse
can it enter download mode.. if so use LGUP and KDZ file.
to enter download mode press vol key up connect usb. youll see it on screen. then flash it using KDZ

raptorddd said:
can it enter download mode.. if so use LGUP and KDZ file.
to enter download mode press vol key up connect usb. youll see it on screen. then flash it using KDZ
Click to expand...
Click to collapse
Thank for your answer ! No it couldn't even boot in download mode
I resolved my problem by forcing again the buttons to reset completely, it finally showed me after about 30 boots or more the reset screen, I said "ok" ; and in fact it just rebooted saying "updating Android", I did not lost anything.
I still don't understand how it happened but anyway !
I don't know if it's possible to set the topic as resolved ? I don't find it

Black lockscreen after reboot

I just rebooted today without making any changes, and once my OP3 finished rebooting, I just got a black lock screen with no response whatsoever. If I hold the power button, I get the reboot dialog, I can take screenshots and they save, and the capacitive buttons react to input. When I reboot into safe mode, the exact same thing occurs, except the lock screen isn't black and says "safe mode". I literally just can't use my phone, period. If I boot into TWRP, I can still access my files after decrypting. It just seems like systemui refuses to start, and I'll have to reset the phone. Has anybody else experienced this?

Could you solve the Problem? Had the same. Only solution for me was full reset.

Flash a newer Rom and see