Develop Bugs

Hyper Gamer rom, screen won't wake.

I'm having this strange issue with the Rom in the following thread; http://forum.xda-developers.com/showthread.php?t=2578972.
Sometimes when I press the power button the screen doesn't wake. This doesn't happen all the time and I've been trying to work out a pattern without success. If I pull the battery and try to boot the phone, it will vibrate to show that it reached the kernel logo but again the screen isn't on so you don't see it.
The only way I've found to fix it is by removing the batter for a while, clearing some sort of temp memory. Then the phone boots as normal and i can use correct.
No other issues and I wondered if anyone had any ideas on what this could be. I would post in the development thread but I don't have the permissions. Any help much appreciated.

JimmyDeemo said:
I'm having this strange issue with the Rom in the following thread; http://forum.xda-developers.com/showthread.php?t=2578972.
Sometimes when I press the power button the screen doesn't wake. This doesn't happen all the time and I've been trying to work out a pattern without success. If I pull the battery and try to boot the phone, it will vibrate to show that it reached the kernel logo but again the screen isn't on so you don't see it.
The only way I've found to fix it is by removing the batter for a while, clearing some sort of temp memory. Then the phone boots as normal and i can use correct.
No other issues and I wondered if anyone had any ideas on what this could be. I would post in the development thread but I don't have the permissions. Any help much appreciated.
Click to expand...
Click to collapse
If you want good rom for gaming and everything else, then try gaming hybrid 2.1.2
Amazing rom with 190 mb free RAM on startup
And there is no bugs.

JimmyDeemo said:
I'm having this strange issue with the Rom in the following thread; http://forum.xda-developers.com/showthread.php?t=2578972.
Sometimes when I press the power button the screen doesn't wake. This doesn't happen all the time and I've been trying to work out a pattern without success. If I pull the battery and try to boot the phone, it will vibrate to show that it reached the kernel logo but again the screen isn't on so you don't see it.
The only way I've found to fix it is by removing the batter for a while, clearing some sort of temp memory. Then the phone boots as normal and i can use correct.
No other issues and I wondered if anyone had any ideas on what this could be. I would post in the development thread but I don't have the permissions. Any help much appreciated.
Click to expand...
Click to collapse
What kernel are you using?
When the screen goes black can you see the phone in if you run adb devices?

Jure220 said:
What kernel are you using?
When the screen goes black can you see the phone in if you run adb devices?
Click to expand...
Click to collapse
Hi Jure220, thanks for the reply. I'm using the 480p version of the one you recommended in the ROM thread here; http://forum.xda-developers.com/showthread.php?t=1804003.
I'm not able to try adb devices right now, but will do later. It's like the phone is still running but just the screen won't turn on. Sometimes I can get it to come alive with by opening the slider. When booting with the problem, I get one vibrate to show that the power has been pressed, then another for the kernal logo (used to indicate going into the recovery menu). It's very strange, I will get back to you on the adb devices but is there any other details I could get you?
Cheers for the help.

JimmyDeemo said:
Hi Jure220, thanks for the reply. I'm using the 480p version of the one you recommended in the ROM thread here; http://forum.xda-developers.com/showthread.php?t=1804003.
I'm not able to try adb devices right now, but will do later. It's like the phone is still running but just the screen won't turn on. Sometimes I can get it to come alive with by opening the slider. When booting with the problem, I get one vibrate to show that the power has been pressed, then another for the kernal logo (used to indicate going into the recovery menu). It's very strange, I will get back to you on the adb devices but is there any other details I could get you?
Cheers for the help.
Click to expand...
Click to collapse
If its posible run adb logcat when the screen still works and keep it connected until the black screen apears and post the log in a txt file. But it isnt necessary. But if you reflash the rom it shuld work fine. And if it dosent try the new update I just released

Jure220 said:
If its posible run adb logcat when the screen still works and keep it connected until the black screen apears and post the log in a txt file. But it isnt necessary. But if you reflash the rom it shuld work fine. And if it dosent try the new update I just released
Click to expand...
Click to collapse
Yes I did notice that you had posted v1.3, will give that a try. I was a bit confused as to why the ROM would affect the screen on boot, but this is me assuming that it is something to do with the ROM at all.
Out of interest, did I need to use any specific settings when formatting /system ready for the ROM? I did a full wipe and fresh Kernal install at the time so had to format it.

JimmyDeemo said:
Yes I did notice that you had posted v1.3, will give that a try. I was a bit confused as to why the ROM would affect the screen on boot, but this is me assuming that it is something to do with the ROM at all.
Out of interest, did I need to use any specific settings when formatting /system ready for the ROM? I did a full wipe and fresh Kernal install at the time so had to format it.
Click to expand...
Click to collapse
When you flash the rom /system will be formated automaticly, and I also doubt it is a rom issue I think something went wrong while flashing...

Jure220 said:
When you flash the rom /system will be formated automaticly, and I also doubt it is a rom issue I think something went wrong while flashing...
Click to expand...
Click to collapse
Hi Jure2020, so I just flashed the ROM again with v1.3, booted fine after flashing. Powered off and then black screen again. I think that it must be a Kernel issue, do you have any other recommendations for Kernels compatible with your ROM?
I tried adb devices btw, all I got was the follwing;
C:\Development\Android SDK\platform-tools>adb devices
List of devices attached
CB5A1E0AJ2 device
C:\Development\Android SDK\platform-tools>

JimmyDeemo said:
Hi Jure2020, so I just flashed the ROM again with v1.3, booted fine after flashing. Powered off and then black screen again. I think that it must be a Kernel issue, do you have any other recommendations for Kernels compatible with your ROM?
I tried adb devices btw, all I got was the follwing;
C:\Development\Android SDK\platform-tools>adb devices
List of devices attached
CB5A1E0AJ2 device
C:\Development\Android SDK\platform-tools>
Click to expand...
Click to collapse
Try to reflash the kernel or use lupus ics/gb one and if it still dosent work reflash the firmware, btw when it first happend did you drop the phone or something?

Jure220 said:
Try to reflash the kernel or use lupus ics/gb one and if it still dosent work reflash the firmware, btw when it first happend did you drop the phone or something?
Click to expand...
Click to collapse
Yeah I will try re-flashing a new kernel this evening. Will try this one; http://forum.xda-developers.com/showthread.php?t=2167766.
No honestly, just one time I noticed it didn't wake the screen. Then it got a bit more regular, now it's pretty much every time the phone is left idle for a while, the screen just won't come on. The phone is active, I can 'unlock' it by swiping; I get the haptic feedback and hear the unlock noise. The phone is running, just the screen is off. I even thought it could be a CPU clocking issue, so used SetCPU to force the minimum speed up for resumption and no luck their either.
I have been thinking that it could be a hardware issue, my phone is kinda old now, but the thing is once the phone is on, it's on. I've gamed on it for a good hour or two with no problems, then pressed power to sleep and immediately haven't been able to turn it back on again. It's just very strange, thanks for the help though.

Hi JimmyDeemo,
I think your problem is flex cable related. I've also experience this before. After I replaced the damaged flex cable, my phone just work fine....:victory:

[Q] One X takes 5 min to reboot

Hello folks,
this morning i wanted to check the watch on my phone and noticed it was very slow. As i am on a cm 11 nightly, i decided to reboot.
The phone shut down correctly but didnt come up afterwards, the screen stayed black. About 4 minutes later, the "HTC quietly brilliant" logo appears. About another 1-2 min. the cyanogenmod boot screen appears. I can repeat that behaviour every time. same with boot to recovery or fastboot. After booting up completely, the phone usage appears to be normal excep the display brightness sensor is not working automatically.
Please note that i am on the same nightly for about 10 days now without any issues except a few reboots. I didn't change anything in the last days, same setup, same usage.
I wiped the caches, installed newest nightly, nothing changed. i cant logcat during boot because adb devices says no device attached.
does anybody has any idea what i can do? i am afraid it seems to be some kind of hardware failure...?
regards,

In fastboot use
Fastboot erase cache
and also backup apps and messages and wipe everything expect battery stats and sd card I had that problem too

big noob said:
In fastboot use
Fastboot erase cache
and also backup apps and messages and wipe everything expect battery stats and sd card I had that problem too
Click to expand...
Click to collapse
Thanks for your answer. Unfortunately, as i anticipated, it did not work. I factory resetted the phone and erased all caches (not via fastboot but cwm, i guess it does the same).
I don't think it is a ROM problem as there are no issues when android is booting but at the, i will call it POST (the htc quietly brilliant logo )of the phone.
I think the proximity sensor/brightness sensor is defective and the phone recognizes it during the "POST" and runs in some kind of timeout and then starts booting.
Can somebody confirm a phone does have something like a hardware check before booting the OS?
Kind regards,

two_handed said:
Thanks for your answer. Unfortunately, as i anticipated, it did not work. I factory resetted the phone and erased all caches (not via fastboot but cwm, i guess it does the same).
I don't think it is a ROM problem as there are no issues when android is booting but at the, i will call it POST (the htc quietly brilliant logo )of the phone.
I think the proximity sensor/brightness sensor is defective and the phone recognizes it during the "POST" and runs in some kind of timeout and then starts booting.
Can somebody confirm a phone does have something like a hardware check before booting the OS?
Kind regards,
Click to expand...
Click to collapse
Are you tryed with diferent rom? I think it is not a problem if your prox sensor not working!!!

Thant said:
Are you tryed with diferent rom? I think it is not a problem if your prox sensor not working!!!
Click to expand...
Click to collapse
No, i did not try a different ROM. Why should i? it worked with CM11 before without any issues...

two_handed said:
No, i did not try a different ROM. Why should i? it worked with CM11 before without any issues...
Click to expand...
Click to collapse
Obviously, it is ROM's problem. Because it is nightly. Although I have installed nightly too, one from 23 feb. And I have no problems. By the way, snapshot built l built is released now and I'm gonna try it today.
Sent from my One X using xda app-developers app

Timofey_K said:
Obviously, it is ROM's problem. Because it is nightly. Although I have installed nightly too, one from 23 feb. And I have no problems. By the way, snapshot built l built is released now and I'm gonna try it today.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Still i really don't think it is a ROM problem. I just noticed that the phone even in fastboot behaves REALLY slow (changing the menu with volume buttons takes 1-2 minutes). And fastboot definately is independent from the ROM.
Anyways, i am just downloading CM 10.2 stable realease and flash it just to be sure.

Yep, as i thougth, still black screen for 4 minutes until the HTC quietly brilliant logo appears.
Guess it's faulty hardware then... Would be nice if someone could confirm my assumption that there is some kind of POST before the ROM is loaded.
regards

two_handed said:
Yep, as i thougth, still black screen for 4 minutes until the HTC quietly brilliant logo appears.
Guess it's faulty hardware then... Would be nice if someone could confirm my assumption that there is some kind of POST before the ROM is loaded.
regards
Click to expand...
Click to collapse
Try to flash sense rom like ARHD it is close to stock and see what will heppend then if it is the same it is hardware if not is problem it CM

Asus Zenfone 2 ZE551ML

Well, double whammy, one problem resulting from trying to fix the other.
I was having screen problems where the lower half of my screen would take a long time to refresh and followed a post to wipe the partition cache hoping to help the issue.
Well, not sure what happened with that (since I couldn't see the loading or anything because of the screen issue) but after half an hour I rebooted my phone and now it boots into an error (android logo error).
I tried flashing firmware back on and it didn't help.
Any possible assistance?
The only thing I can access is the bootloader and nothing else currently

GlitchZenfone2 said:
Well, double whammy, one problem resulting from trying to fix the other.
I was having screen problems where the lower half of my screen would take a long time to refresh and followed a post to wipe the partition cache hoping to help the issue.
Well, not sure what happened with that (since I couldn't see the loading or anything because of the screen issue) but after half an hour I rebooted my phone and now it boots into an error (android logo error).
I tried flashing firmware back on and it didn't help.
Any possible assistance?
The only thing I can access is the bootloader and nothing else currently
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
Moving your thread to Zenfone 2 Q&A,Help and Troubleshooting.Experts there may be able to help you
___
v7
XDA Assist

stuck on boot screen!help!(yes,it's a bit generic)

so,i have the ze551ml,and right now, i can boot it up,but it gets stuck at the asus logo,and the spinning circle below it. i see lots of people clearing cache,going into safe mode,or simply reinstalling the firmware.
first method doesn't work,i don't know how to clear device cache without actually being inside,i.e. actually have android properly loaded up
second method,just seems to get me nowhere.
third method,i tried power,then up rocker,then the recovery tab,just gives me the dead android thing with error written below.
help,this is my daily driver,so everything's on it!
also,forgot to mention,so this is a quick edit,i have adb installed(i think) on my pc,but whenever it launches,it justs has text running quickly,too fast for me to read,then self exits.
i also have to disconnect it from my pc or else it would not reboot.

umm..quick update,the recovery function now somewhat works, i managed to get the firmware from asus's webpage,put it in a ,microsd card,renamed it MOFD_SDUPDATE.zip. it seems to recognize it,at least no dead android with error sign,but after the install,it just does nothing.
it also never seems to actually finish the update,as it just gets about one third of the way,then vibrates twice,and reboots.
i did somehow manage to get it to boot up to the lock screen yesterday before i went to sleep,but then,after i woke up,it just seemed to have rebooted itself,and is stuck on the asus logo with the spinning wheel below again.

if u facing the continuously rotating circle problem in boot screen, then there is very easy solution. it is a very common problem happens for mainly low memory ,sometimes other.. it happens very often to me..
1.first clear user data then clear cache from recovery. u can also use adb from pc.
2. just restart.
[if you dont know how to open recovery, thenopen fastboot & select recovery as u mentioned in ur question, next when the dead android logo appears, dont worry. Then PRESS & HOLD VOL UP+POWER for 3 sec. it ll take few trying as it needs perfect timing to press those keys at a same time. from there you can clear data and cache.]
#PRESS THANKS IF IT HELPS YOU.

sounak1 said:
if u facing the continuously rotating circle problem in boot screen, then there is very easy solution. it is a very common problem happens for mainly low memory ,sometimes other.. it happens very often to me..
1.first clear user data then clear cache from recovery. u can also use adb from pc.
2. just restart.
if there is important data in internal memory,then try with flash the firmware. dont know if it ll solve or not as i always do the above steps and it becomes OK.
#PRESS THANKS IF IT HELPS YOU.
Click to expand...
Click to collapse
i'll try the first method,but i just tried the third,and that did nothing.
i also tried the second method,multiple times,nothing.
also,how could it have low memory? it's not even booted up,technically.

Jasper1224 said:
i'll try the first method,but i just tried the third,and that did nothing.
i also tried the second method,multiple times,nothing.
also,how could it have low memory? it's not even booted up,technically.
Click to expand...
Click to collapse
Try to install custom ROM, like SuperZen. I think the is when you update your ROM and it doesn't finish due to a bad download.

24imelqui said:
Try to install custom ROM, like SuperZen. I think the is when you update your ROM and it doesn't finish due to a bad download.
Click to expand...
Click to collapse
But you have to unlock bootloader for that. Not everyone wants to do that...
Perhaps it's better to install Asus Flash Tool on your computer and flash raw firmware. You could even try without clearing user data.

Jasper1224 said:
i'll try the first method,but i just tried the third,and that did nothing.
i also tried the second method,multiple times,nothing.
also,how could it have low memory? it's not even booted up,technically.
Click to expand...
Click to collapse
just delete the internal memory..then clear cache..then restart
nothing else

sorry,done that after a bit of reserach,didn't type it in...everything's fine.
but can i just clear cache next time?

sorry,done that after a bit of reserach,didn't type it in...everything's fine.
but can i just clear cache next time?

Jasper1224 said:
sorry,done that after a bit of reserach,didn't type it in...everything's fine.
but can i just clear cache next time?
Click to expand...
Click to collapse
sir can you help me with this please? i have the same problem right now with my asus zenfone 2 z00ad. im stuck on the asus logo with this circle. please help me.

Vibe K5 doesn't boot up

hi, I need some help, i'm desperate.
I was using a bad charger, when my phone was in low battery, so it turned off my phone (charging > not charging) three times. In the third boot, the CM logo just froze up, and the phone didn't boot anymore. It appears Lenovo's logo and then the screen turns black and i'm not able to press any button. I tried to: wipe everything, flash another rom, but the same still happening. I flashed stock rom too, but it gives me a bootloop. I tried to use a TWRP's backup from stock rom, but it didn't work either.
Any help? I don't know what to do

Gabriel337 said:
hi, I need some help, i'm desperate.
I was using a bad charger, when my phone was in low battery, so it turned off my phone (charging > not charging) three times. In the third boot, the CM logo just froze up, and the phone didn't boot anymore. It appears Lenovo's logo and then the screen turns black and i'm not able to press any button. I tried to: wipe everything, flash another rom, but the same still happening. I flashed stock rom too, but it gives me a bootloop. I tried to use a TWRP's backup from stock rom, but it didn't work either.
Any help? I don't know what to do
Click to expand...
Click to collapse
Since you flashed a stock rom , flash a new twrp using adb and fastboot and wipe everything except system . BTW a simple reboot (or three) cant damage system. Try checking battery too if you could

soldiersz said:
Since you flashed a stock rom , flash a new twrp using adb and fastboot and wipe everything except system . BTW a simple reboot (or three) cant damage system. Try checking battery too if you could
Click to expand...
Click to collapse
I tried that now, it didn't work, still on bootloop :/

Gabriel337 said:
I tried that now, it didn't work, still on bootloop :/
Click to expand...
Click to collapse
Use Qualcomm Flash tool or QFIL then ..

soldiersz said:
Since you flashed a stock rom , flash a new twrp using adb and fastboot and wipe everything except system . BTW a simple reboot (or three) cant damage system. Try checking battery too if you could
Click to expand...
Click to collapse
soldiersz said:
Use Qualcomm Flash tool or QFIL then ..
Click to expand...
Click to collapse
I tried that with QFIL and Lenovo Smart Assistance. and bootloop.
But I think i've made some progress:
I tried to flashed a new rom (I flashed CM/RR/AOCP before, is with these roms the frozen lenovo screen happens), CRDROID, and it appears crdroid bootanimation, and load until it frozes and phone turn off.

Gabriel337 said:
I tried that with QFIL and Lenovo Smart Assistance. and bootloop.
But I think i've made some progress:
I tried to flashed a new rom (I flashed CM/RR/AOCP), CRDROID, and it appears crdroid bootanimation, and load until it frozes and phone turn off.
Click to expand...
Click to collapse
Wipe everything except system. It should work

soldiersz said:
Since you flashed a stock rom , flash a new twrp using adb and fastboot and wipe everything except system . BTW a simple reboot (or three) cant damage system. Try checking battery too if you could
Click to expand...
Click to collapse
soldiersz said:
Use Qualcomm Flash tool or QFIL then ..
Click to expand...
Click to collapse
soldiersz said:
Wipe everything except system. It should work
Click to expand...
Click to collapse
First of all, thanks for you help!
So, I wiped, and nope, the same error happens. This is a problem that I've never seen before

Gabriel337 said:
First of all, thanks for you help!
So, I wiped, and nope, the same mistake it happens. This is a problem that I've never seen before
Click to expand...
Click to collapse
Yeah me too :crying:

Gabriel337 said:
hi, I need some help, i'm desperate.
I was using a bad charger, when my phone was in low battery, so it turned off my phone (charging > not charging) three times. In the third boot, the CM logo just froze up, and the phone didn't boot anymore. It appears Lenovo's logo and then the screen turns black and i'm not able to press any button. I tried to: wipe everything, flash another rom, but the same still happening. I flashed stock rom too, but it gives me a bootloop. I tried to use a TWRP's backup from stock rom, but it didn't work either.
Any help? I don't know what to do
Click to expand...
Click to collapse
I am facing the same problem :crying: Got any solution? How did u flash stock ROM?

I have flashed using qfil now device works fine

Hello guys,
I wanna purchase lenovo k5 plys 3gb mobile,But this one got comments from users as it got issues with battery backup,call quality & heating issues...I got very good offer on this mobile right now . Should i go for this mobile ?

kaka9876 said:
Hello guys,
I wanna purchase lenovo k5 plys 3gb mobile,But this one got comments from users as it got issues with battery backup,call quality & heating issues...I got very good offer on this mobile right now . Should i go for this mobile ?
Click to expand...
Click to collapse
You can go for Vibe k6 power. Why k5 plus?
---------- Post added at 04:03 PM ---------- Previous post was at 04:01 PM ----------
kaka9876 said:
Hello guys,
I wanna purchase lenovo k5 plys 3gb mobile,But this one got comments from users as it got issues with battery backup,call quality & heating issues...I got very good offer on this mobile right now . Should i go for this mobile ?
Click to expand...
Click to collapse
1) Main problem is Battery backup. It won't last long a day.
2) Stock ROM Really sucks
There is no heating issue though. It has been solved by latest updates

K5 Plus flash recovery
hey guys , I've been trying to flash a custom rom through TWRP recovery menu but by my mistake i wiped the system. now it just keeps booting up over and over on the lenovo logo. please help me with this

Youzpalang said:
hey guys , I've been trying to flash a custom rom through TWRP recovery menu but by my mistake i wiped the system. now it just keeps booting up over and over on the lenovo logo. please help me with this
Click to expand...
Click to collapse
Try entering to TWRP by using the hardware keys. Do this:
Pull down the battery.
Insert again.
Press power key, volume up and volume down at the same time, until lenovo logo dissappear.
If luck, you are into TWRP now.
connect phone to computer via usb cable. you should be able to access to internal memory.
So, copy into it any custom ROM previously downloaded from your computer, and flash it. That's all.

walterfuster said:
Try entering to TWRP by using the hardware keys. Do this:
Pull down the battery.
Insert again.
Press power key, volume up and volume down at the same time, until lenovo logo dissappear.
If luck, you are into TWRP now.
connect phone to computer via usb cable. you should be able to access to internal memory.
So, copy into it any custom ROM previously downloaded from your computer, and flash it. That's all.
Click to expand...
Click to collapse
Thanks man , What custom rom would you suggest? Is bootlegger OK?

Youzpalang said:
Thanks man , What custom rom would you suggest? Is bootlegger OK?
Click to expand...
Click to collapse
Bootleggers has some bugs, like WhatsApp not being able to play GIFs or videos. Also, after a while in the day, launcher becomes laggy (maybe a kernel settings issue). You have to reboot and becomes smooth and fast again.
I highly recommend LOS 15.1 or AEX 5.6 from Harry (yes, he is continuing the development!) Both of them have June updates.
I'm on AEX right now, which is such a marvelous ROM. It has a looot of customizations than any other ROM I've tried.
How to get them?
Search into the Harry8242 profile from AFH.

walterfuster said:
Bootleggers has some bugs, like WhatsApp not being able to play GIFs or videos. Also, after a while in the day, launcher becomes laggy (maybe a kernel settings issue). You have to reboot and becomes smooth and fast again.
I highly recommend LOS 15.1 or AEX 5.6 from Harry (yes, he is continuing the development!) Both of them have June updates.
I'm on AEX right now, which is such a marvelous ROM. It has a looot of customizations than any other ROM I've tried.
How to get them?
Search into the Harry8242 profile from AFH.
Click to expand...
Click to collapse
LOS 15.1 is fine but has some bugs too(camera zoomer not working).
I've finally decided to use a STOCK ROM and there is a complication, here is the problem:" I'm using lenovo downloader software to flash and once my phone is connected, the progress bar gets stuck at the begining level and says:"Flashing" below the status bar and " Sahara "- which have no idea what means- below the step bar and it also takes too much time to do the flashing which is never done! I have the same problem with QFIL( Sahara Fail )!

Youzpalang said:
LOS 15.1 is fine but has some bugs too(camera zoomer not working).
I've finally decided to use a STOCK ROM and there is a complication, here is the problem:" I'm using lenovo downloader software to flash and once my phone is connected, the progress bar gets stuck at the begining level and says:"Flashing" below the status bar and " Sahara "- which have no idea what means- below the step bar and it also takes too much time to do the flashing which is never done! I have the same problem with QFIL( Sahara Fail )!
Click to expand...
Click to collapse
I figured out , Problem solved!

Youzpalang said:
I figured out , Problem solved!
Click to expand...
Click to collapse
Glad to hear that! So, you've decided to stay on stock ROM. OK, it has sense. stock firmware is free of bugs, right? Now, do you know being on stock LL you can "update" to MM and thus get doze and adaptive storage?
How?
Follow this guide:
https://forum.xda-developers.com/k5-plus/how-to/guide-a6020l36-official-lenovo-andoid-6-t3596733
and you'll get the most updated official stock ROM available four our device. Actually, it's a backup made by an Brazilian user, where you should restore only system and boot partitions, in order to keep your data.
This update was only released for Brazil region, but, users from other regions in the thread, reported it worked for them.
I've tried it once, and worked like a charm.