Database Users

newbie question

after sometime i notice my wifi dont work, cant seems to on the wifi even if i cold boot the blueangel.
anyone got bug fix for this?
used to work perfectly last time.
PS: if i hard reset it, it work for awhile again, but after few days, it hard a hard time stating up again

Please refrain from opening new threads for questions. New threads can only be open for contributions to the site (roms, apps, kitchens, themes, fixes, etc). If you have to ask something, please use the Q&A thread which is monitored constantly by Seniors as well as some other members as well. I have transferred your question over to the Q&A section of this forum. Thanks.

Strange Issue with ALL* (*that I have tested) Current builds.

I would just like to make a thread to see if anyone else has been getting the same problem with all the current version of the builds being released. I maybe wrong but this was not happening with some of the older builds, but ever since subcraft 1.5, and including current* Mattcleo, Froyostone, Bangsters, and Mccmioons FRG33 are having this weird issue.
*(current meaning as of 9/7/10)
Here is the best that I can explain it.
When locking the phone the screen slowly fades to black (no bigge I actually kind of like it, just did not do that with the earlier builds) then when unlocking the screen the screen would fade back in to the lock screen, but 5 out of 10 times the backlight would turn on, but the screen would still stay black and not display the lock screen. Its not frozen because if I drag my finger along the place where the unlock swipe gesture is placed the phone will unlock and go back to normal operation. I am just perplexed on why this is happening now and not on the early builds. Could it have something to do with all the new builds moving on to PPP?

No offence to the OP, but can you please read other threads or try searching in future? This is one of many known problems which are trying to be dealt with, just be patient.

I did a search, but all I could find were SOD related topics and posts, I did not know how to word it in the search and like 5 searches in I couldnt find anything relative. Digging through hundreds of pages of thru several threads is not easy, and I tried it, but couldnt find this specific problem.

Well okay then, but now you know, and just to let you know in future, don't post in this channel, post in the general android developers forum and not this one please!

[Q] Keyboard random unresponsiveness fix

We all know that there is a random issue with the keyboard letters being unresponsive randomly (and on random handsets). Sometimes its a delete (backspace) button, sometimes its a letter A or P. The only way to fix it would be putting the phone to sleep and waking it up.
I tried to search for the solution and did not find an answer. I tried different keyboards - the issue persists.
I am running RoyalGinger 3.0
Does anyone know how to fix it? I really love Royal Ginger, but this issue is quite annoying.

I've experienced it too. I made a thread about it, don't know if you've seen it.
But you may wanna take a look as dozens of other people have reported it. Some have found temporary fixes and such.
But here it is.

mackster248 said:
I've experienced it too. I made a thread about it, don't know if you've seen it.
But you may wanna take a look as dozens of other people have reported it. Some have found temporary fixes and such.
But here it is.
Click to expand...
Click to collapse
If you could post your input there as well as to which ROM it has happened to you and anything else would be nice. That way we can kinda have a consensus on what ROM's it's occurring.

[Q] Having a couple problems with AOKP. Insight appreciated.

I've browsed some pages back and also tried search, so forgive me if my questions have been answered already. I was hoping somebody had similar problems, accompanied by actual solutions unlike myself.
Using the MK2 benchmark, I'm having problems with MTP not working. I have another way to move crap to my microSD, but it's far less convenient. Does anyone else have this problem? The phone says 'connected as a media device' or whatever, and my drivers definitely are installed correctly. USB debugging isn't on. I don't have this issue with any other 4.3 ROMs I've tried.
Also, with absolutely no apps other than PA modular mini Gapps installed whatsoever, I've been having pretty frequent reboots on the Kit Kat nightlies. Also I believe some people on the official thread in the original development sub-forum were having similar issues. Flashing a different kernel fixes the reboots, but then I can't have wifi. I'm just sitting on MK2 until them Kit Kats are a bit more stable, unless somebody knows why I'm having the issue.

Make sure under setting/storage/USB connection MTP is ticked. It sounds like you're doing a good job if eliminating variables. I use CM11 and don't have a problem connecting to a computer so maybe its just the ROM.

touchscreen unresponsive while dt2w/sweep2wake enabled

Hi. I come from a6020 forum. I write here because I've discovered we have a very common bug on ROMs with kernels that support dt2w/sweep2wake features.
The issue is as the title says: touchscreen won't respond after waking up from deep sleep, while having dt2w/sweep2wake features enabled.
Only the volume +/- and pwr buttons will work.
I just have to reboot the phone and the touchscreen will work again, but after a while the issue comes back.
The only way to get the phone working normal, is disabling those features from Kernel Adiutor.
I'm part of a telegram tester group for my device, but developers there can't find where the issue is.
my question here is:
Do you have a fix/workaround, other than just disabling? Or at least do you know why dt2w causes the touchscreen to bad working, specifically?
Surely, you know what I'm talking about, cause I've seen reports for this bug on some a6000 threads.
If you could response me, @dev_harsh1998, @ED300, @rohitsinha12, or @IvanHephaestus, I'll be grateful, for sure. thanks in advance.

I have same problem please help

walterfuster said:
Hi. I come from a6020 forum. I write here because I've discovered we have a very common bug on ROMs with kernels that support dt2w/sweep2wake features.
The issue is as the title says: touchscreen won't respond after waking up from deep sleep, while having dt2w/sweep2wake features enabled.
Only the volume +/- and pwr buttons will work.
I just have to reboot the phone and the touchscreen will work again, but after a while the issue comes back.
The only way to get the phone working normal, is disabling those features from Kernel Adiutor.
I'm part of a telegram tester group for my device, but developers there can't find where the issue is.
my question here is:
Do you have a fix/workaround, other than just disabling? Or at least do you know why dt2w causes the touchscreen to bad working, specifically?
Surely, you know what I'm talking about, cause I've seen reports for this bug on some a6000 threads.
If you could response me, @dev_harsh1998, @ED300, @rohitsinha12, or @IvanHephaestus, I'll be grateful, for sure. thanks in advance.
Click to expand...
Click to collapse
This is seen to happen on the devices with non original vendor panel or on those panel which fail to pass the firmware check btw if that happens upload the kernel logs i will write an patch to fix the issue prolly we need a condition resched somewhere. I haven't much bothered upon fixing it on our device because its seen happening only for people with damaged or non original panels

dev_harsh1998 said:
This is seen to happen on the devices with non original vendor panel or on those panel which fail to pass the firmware check btw if that happens upload the kernel logs i will write an patch to fix the issue prolly we need a condition resched somewhere. I haven't much bothered upon fixing it on our device because its seen happening only for people with damaged or non original panels
Click to expand...
Click to collapse
Here you are, bro. A lot of thanks: