Database Users

[Q] Nexus 7 Sleep of Death

Hi, I got my Nexus 7 yesterday. Everytime I leave it in sleep mode for more than 10 minutes it shuts down and i need to hard reboot. I've read somewhere that its possibly Sleep of Death. I tried shutting wifi of during sleep, installed an auto airplane mode app, reset to factory settings about 5 times but nothing seems to help. I run stock rom, not rooted. Do you think i should return it or is there a possible sollution? Greatings

I'd return it

What build number are you in? Settings/about tablet maybe its somthing to do with JR3O0S?
Sent from my Nexus 7 using Tapatalk 2

leelaa said:
What build number are you in? Settings/about tablet maybe its somthing to do with JR3O0S?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Build number is JRO03D

Goldcell said:
Build number is JRO03D
Click to expand...
Click to collapse
I'm the same build JRO03D and I can say that mine dies sometimes after I press the power button to turn the screen off.
I've noticed it happens when I'm reading a pdf book on adobe reader and when I turn my screen off it just doesn't turn on and I have to hold it so it resets and turns on.
Is this a bad build number? The one that ends with a D?

kris4o2 said:
I'm the same build JRO03D and I can say that mine dies sometimes after I press the power button to turn the screen off.
I've noticed it happens when I'm reading a pdf book on adobe reader and when I turn my screen off it just doesn't turn on and I have to hold it so it resets and turns on.
Is this a bad build number? The one that ends with a D?
Click to expand...
Click to collapse
Are you guys using a custom rom, or stock? I am showing JRO03D (MoDaCo Custom Rom Jr7) and have no issues.. so either his rom fixed the issue of the build, or perhaps the update you received is bad?
I asked somewhere else the best way to go back to stock, a way that re-writes the partitions.. like flashing a RUU with HTC, or using Odin on Samsung.. but never got an answer. I would recommend you find a way to get back to stock firmware, then allow it to update again, or update it yourself- or get a custom rom..
And what hardware version are you on? Mine is C80.. no issues whatsoever.

Silentbtdeadly said:
Are you guys using a custom rom, or stock? I am showing JRO03D (MoDaCo Custom Rom Jr7) and have no issues.. so either his rom fixed the issue of the build, or perhaps the update you received is bad?
I asked somewhere else the best way to go back to stock, a way that re-writes the partitions.. like flashing a RUU with HTC, or using Odin on Samsung.. but never got an answer. I would recommend you find a way to get back to stock firmware, then allow it to update again, or update it yourself- or get a custom rom..
And what hardware version are you on? Mine is C80.. no issues whatsoever.
Click to expand...
Click to collapse
I'm stock. I've never used a custom ROM or rooted my devices.

Silentbtdeadly said:
Are you guys using a custom rom, or stock? I am showing JRO03D (MoDaCo Custom Rom Jr7) and have no issues.. so either his rom fixed the issue of the build, or perhaps the update you received is bad?
I asked somewhere else the best way to go back to stock, a way that re-writes the partitions.. like flashing a RUU with HTC, or using Odin on Samsung.. but never got an answer. I would recommend you find a way to get back to stock firmware, then allow it to update again, or update it yourself- or get a custom rom..
And what hardware version are you on? Mine is C80.. no issues whatsoever.
Click to expand...
Click to collapse
I'm running the stock rom from google. I don't know what hardware version I'm on. Thanks for the replies so far!

If the device is otherwise perfect and free of any defects, I might take a stab at trying to fix it by wiping it and reflashing the stock Image. If you can't get it to work you can always return it then.

Goldcell said:
I'm running the stock rom from google. I don't know what hardware version I'm on. Thanks for the replies so far!
Click to expand...
Click to collapse
The first few letters on the sticker on the back of the tablet, at the bottom, will tell you the hardware version..
And you have a choice, if you just got it and can return it, it is unlikely you will have the issue with a new one.. if you can't, you may want to figure out how to flash a stock firmware, as I have a feeling the OTA update may have went wrong. Resetting your tablet(factory reset) just deletes your /data partition, the system partition is not rewritten.. so if there was something wrong with the update in the system files, that won't help.
I am pretty damn sure it is likely kernel related, yet another option to look into.. the nook color(I used to use) has that issue, so it is sad to hear anyone hear have that issue too.
If you are willing to root, you may want to try increasing the minimum clock speed just one step, or if you have undervolted(which I don't think you've said) you may want to raise the voltage or allow stock voltage, as that can also be the issue.

irishrally said:
If the device is otherwise perfect and free of any defects, I might take a stab at trying to fix it by wiping it and reflashing the stock Image. If you can't get it to work you can always return it then.
Click to expand...
Click to collapse
Is reflashing the stock rom the same as resetting it to factory settings?

Silentbtdeadly said:
The first few letters on the sticker on the back of the tablet, at the bottom, will tell you the hardware version..
And you have a choice, if you just got it and can return it, it is unlikely you will have the issue with a new one.. if you can't, you may want to figure out how to flash a stock firmware, as I have a feeling the OTA update may have went wrong. Resetting your tablet(factory reset) just deletes your /data partition, the system partition is not rewritten.. so if there was something wrong with the update in the system files, that won't help.
I am pretty damn sure it is likely kernel related, yet another option to look into.. the nook color(I used to use) has that issue, so it is sad to hear anyone hear have that issue too.
If you are willing to root, you may want to try increasing the minimum clock speed just one step, or if you have undervolted(which I don't think you've said) you may want to raise the voltage or allow stock voltage, as that can also be the issue.
Click to expand...
Click to collapse
I don't have my box anymore. Is there another way to see what your hardware number is?

kris4o2 said:
I don't have my box anymore. Is there another way to see what your hardware number is?
Click to expand...
Click to collapse
I'm not exactly sure, I know the sticker on the back of the tablet itself, toward the bottom has it.. I'm still somewhat new to this tablet yet.
Goldcell said:
Is reflashing the stock rom the same as resetting it to factory settings?
Click to expand...
Click to collapse
I said in my last post, restoring to factory just deletes the /data partition, and leaves the /system files exactly the same. Reflashing actually overwrites the system files.

I get it occasionally but I'm running a CM nightly and Clemsyns elite kernel so I chalk it up to that.

I've flashed stock rom and several other roms, but it did not help so I've returned it for a new device, i have to wait 3 weeks for a new one . Thanks for the replies!

Bootloader Loop problem

Hi, my phone acted weird today, been running custom room for over couple months without any problem, but then when i resart my phone today it got to the bootload screen and stuck there ever seen. I can able to go into custom recover and did a full wipe but nothing change, could anyone help me out? I have loki also. Using S4 ATT version.

Try wiping cache in your recovery

i did that, always do that after install a new rom, don't know why my phone is soft bricked now...

akahimaro said:
i did that, always do that after install a new rom, don't know why my phone is soft bricked now...
Click to expand...
Click to collapse
if you've done a full wipe and tried either re-flashing your rom or restoring a nandroid and neither was successful, you may need to consider going back to stock via odin and starting over.
i've never seen a phone run on the same rom and kernel settings for months and then just shut down and softbrick without something having been changed recently.

xBeerdroiDx said:
if you've done a full wipe and tried either re-flashing your rom or restoring a nandroid and neither was successful, you may need to consider going back to stock via odin and starting over.
i've never seen a phone run on the same rom and kernel settings for months and then just shut down and softbrick without something having been changed recently.
Click to expand...
Click to collapse
yes, i'm doing that right now, thanks for the tips, i had that happen to my s2 before. Really weird...

Before ODIN'ing back to MDL/MDB...
akahimaro said:
yes, i'm doing that right now, thanks for the tips, i had that happen to my s2 before. Really weird...
Click to expand...
Click to collapse
What recovery image are you running? You are not the only one that had this problem. I am trying to piece this together.

[[SOLVED]] Process system isn't responding

Hi,
I rooted my phone 2 days ago and installed custom ROM everything went well, except for today my phone start to lag too much, so I decided to flash back the stock ROM that I have downloaded from Sam-mobile using Odin 3.08, but now my device not responding to anything and even I get "Process system isn't responding" in Samsung wizard installation also the sound disappeared and when try lunch any app like camera I get message "camera failed" and keep getting "Process system isn't responding".
[[The Solution]] for Process system isn't responding follow the steps: ((ONLY SM-N9005))
1-Unroot your phone if you are rooted.
2-Factory rest your phone and clear cache. .
3-Flash the Stock rom for your device.(if this fixed the the problem stop here if not continue to step 4)
4-Download this ROM and flash it by Odin 3.04.(this rom somehow managed to restore my EFS files and fixed the problem)
and that's it.

root is bad
bad root it is for you

dancapitan said:
bad root it is for you
Click to expand...
Click to collapse
I don't think so because I used this root http://forum.xda-developers.com/galaxy-note-3#root

Hi, I have the exact same problem and I can't seem to figure out how to fix it either

Dahdoul said:
Hi,
I have rooted my phone 2 days ago and installed custom rom everything went well except for today my phone start to lag too much,so i decided to flash back the stock rom that i have downloaded from sam mobile using odin 3.08 but now my device not responding to anything even i get not responding message in samsung wizard installation and sound disappeared and when try open any app like camera get message camera failed and keep getting process system isn't responding.
i do not know what to do,please help me.
thank you.
Click to expand...
Click to collapse
Oh man, I though I was the only one having this problem. I really don't now how to fix it at all, I've tried flashing stock ROM and I still get the same problem. If anyone can help, I'd be so grateful.

This sounds a lot like the issue I've been having (see details in the thread I posted here).
Any insight would be very welcome.

Yup bad root (it can and does happen the odd time!), clear cache etc in download mode, then reflash the new Stock ROM, then wipe cache etc again in download mode. See if that helps.
Similar issue I had previously after I originally rooted was apps kept closing and saying stopped working. When I wiped the ROM and updated via KIES to MJ7 with wiping cache etc, it seems to have done the trick.
EDIT: Also try ODIN 3.07 rather than 3.08

radicalisto said:
Yup bad root (it can and does happen the odd time!), clear cache etc in download mode, then reflash the new Stock ROM, then wipe cache etc again in download mode. See if that helps.
Similar issue I had previously after I originally rooted was apps kept closing and saying stopped working. When I wiped the ROM and updated via KIES to MJ7 with wiping cache etc, it seems to have done the trick.
EDIT: Also try ODIN 3.07 rather than 3.08
Click to expand...
Click to collapse
I have already done everything you mentioned by clearing cache,wipe system,clear data,flash new stock rom but nothing fix the issue

Dahdoul said:
I have already done everything you mentioned by clearing cache,wipe system,clear data,flash new stock rom but nothing fix the issue
Click to expand...
Click to collapse
Yep, I've done the same and nothing helps either

Maybe just return it, play stupid with the phone shop staff, probably won't notice the flashing anyway.

radicalisto said:
Maybe just return it, play stupid with the phone shop staff, probably won't notice the flashing anyway.
Click to expand...
Click to collapse
LOL i will:cyclops:

radicalisto said:
Yup bad root (it can and does happen the odd time!), clear cache etc in download mode, then reflash the new Stock ROM, then wipe cache etc again in download mode. See if that helps.
Similar issue I had previously after I originally rooted was apps kept closing and saying stopped working. When I wiped the ROM and updated via KIES to MJ7 with wiping cache etc, it seems to have done the trick.
EDIT: Also try ODIN 3.07 rather than 3.08
Click to expand...
Click to collapse
Unfortunately I've tried all of this too (except using Kies, it won't recognise my phone though I'd never tried it before now) to no avail.
I might try a warranty swap, but I'm concerned because the system status shows custom and I'm unsure there's any way to reset it. I suppose my only chance is to try for an on-the-spot swap for a new phone, because if it gets sent back to Samsung I expect they'd reject it due to the system status.
Still can't understand why the issue persists beyond reflashing the stock rom...

sexbot3000 said:
Unfortunately I've tried all of this too (except using Kies, it won't recognise my phone though I'd never tried it before now) to no avail.
I might try a warranty swap, but I'm concerned because the system status shows custom and I'm unsure there's any way to reset it. I suppose my only chance is to try for an on-the-spot swap for a new phone, because if it gets sent back to Samsung I expect they'd reject it due to the system status.
Still can't understand why the issue persists beyond reflashing the stock rom...
Click to expand...
Click to collapse
I don't understand why the issue persists after flashing stock either but I doubt it is hardware fault. I hope someone knows how to fix this

Solution
Guys finally i found the solution for Process system isn't responding follow the steps:
1-Unroot your phone if you are rooted
2-Factory rest your phone.
3-Flash the Stock rom for your device.
4-Download this ROM and flash it by Odin 3.04.
and that's it.:laugh:

Dahdoul said:
Guys finally i found the solution for Process system isn't responding follow the steps:
1-Unroot your phone if you are rooted
2-Factory rest you phone.
3-Flash the Stock rom for your device.
4-Download this ROM and flash it by Odin 3.04.
and that's it.:laugh:
Click to expand...
Click to collapse
Hi, the link for "downloading this" doesn't work, I don't suppose you could re-post it please?

luke05dee said:
Hi, the link for "downloading this" doesn't work, I don't suppose you could re-post it please?
Click to expand...
Click to collapse
Already updated http://forum.xda-developers.com/showthread.php?t=2461929

Dahdoul said:
Already updated http://forum.xda-developers.com/showthread.php?t=2461929
Click to expand...
Click to collapse
Thank you so much, just trying this now although which rom out of the one's in that thread did you use please? Just to confirm this fixed all your problems including the "failed camera"

luke05dee said:
Thank you so much, just trying this now although which rom out of the one's in that thread did you use please? Just to confirm this fixed all your problems including the "failed camera"
Click to expand...
Click to collapse
I installed the first rom under SM-N9005 Official Stock ROM's for Odin (KNOX 0x1).and yes it fixes camera failed and the issues i had before like it never happened.oh BTW i downloaded the preRooted if you don't wanna mess with knox just download the stock rom.:laugh:

Dahdoul said:
I installed the first rom under SM-N9005 Official Stock ROM's for Odin (KNOX 0x1).and yes it fixes camera failed and the issues i had before like it never happened.oh BTW i downloaded the preRooted if you don't wanna mess with knox just download the stock rom.:laugh:
Click to expand...
Click to collapse
OMG thank you so much, I mean thank you so inanely much this worked. I've been so upset all week thinking my note was dead and you have fixed it. Oh man thank you, thank you, thank you!

luke05dee said:
OMG thank you so much, I mean thank you so inanely much this worked. I've been so upset all week thinking my note was dead and you have fixed it. Oh man thank you, thank you, thank you!
Click to expand...
Click to collapse
No problem, am so happy for you :highfive:

Weird issues after kitkat upgrade

Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,

Riimez said:
Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,
Click to expand...
Click to collapse
Let's start from the beginning.
Can you describe your method of flashing in case you are doing something wrong? Please describe as much information as possible.
What is your phone model?

y2kkingboy said:
Let's start from the beginning.
Can you describe your method of flashing in case you are doing something wrong? Please describe as much information as possible.
What is your phone model?
Click to expand...
Click to collapse
9005. sorry it was a couple of days ago so I dont really remember. I flashed a 4.4 bootloader (standalone) then tried flashing a 4.4 rom i believe it was sweetrom.

Riimez said:
9005. sorry it was a couple of days ago so I dont really remember. I flashed a 4.4 bootloader (standalone) then tried flashing a 4.4 rom i believe it was sweetrom.
Click to expand...
Click to collapse
I believe the best thing to do now is to flash stock ROM and make sure to full wipe everything even internal memory.
If you have external memory, back up what ever you think necessary to it, the remove it from the device and keep it out.
That clean start well give you a good indication whether the problem is based on a bad flash or there is something wrong with the device.
If everything is running smoothly, we will see about flashing custom ROM.

y2kkingboy said:
I believe the best thing to do now is to flash stock ROM and make sure to full wipe everything even internal memory.
If you have external memory, back up what ever you think necessary to it, the remove it from the device and keep it out.
That clean start well give you a good indication whether the problem is based on a bad flash or there is something wrong with the device.
If everything is running smoothly, we will see about flashing custom ROM.
Click to expand...
Click to collapse
Yep its what ive done, reflashed stock completly and removed sd card. Still no dice - running complete stock 4.4 still with this problem.
Could this be an EFS problem?

If it were an efs problem you wouldn't even boot in most cases.
Can you describe how you flashed stock ROM? Maybe you did it wrong.
Sent from my SM-N9005 using Tapatalk

Sorry to hear that..base on my experienced happened also on my S4..luckily still under warranty..have to wait for 2 weeks...company says faulty mother board and speaker. Hope this helps....
Sent from my SM-N900 using xda premium

Riimez said:
Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,
Click to expand...
Click to collapse
NEE region? - if so it has issues with 4.4.2, @nex7er had the same issues, and if you're using SweetROM I believe he pm'd not-i the fix for it. -- It can be fixed though.

Maybe completely wipe it (System, Data and all) and then Flash stock with Odin?

After kitkat upgrade.. if i use camera app such as camera 360 Or picsart, i can't save my photo to sdcard. It's error, Has anyone had or know how to resolve this problem???

Blancos4Lyf said:
Maybe completely wipe it (System, Data and all) and then Flash stock with Odin?
Click to expand...
Click to collapse
Yep. Still no dice.

Riimez said:
Yep. Still no dice.
Click to expand...
Click to collapse
I did post the reason on the last page what I think it might be...... if you're in a Nordic region or even have a nordic model it's a common problem, if you search around you'll see others that have the same issue (notably ne7xer). -- If it's not that, then it's a warranty job due to faulty HW
EDIT: you could try a complete wipe including re-partitioning, but that's a bigger job that you'd want to do in all honesty.

radicalisto said:
I did post the reason on the last page what I think it might be...... if you're in a Nordic region or even have a nordic model it's a common problem, if you search around you'll see others that have the same issue (notably ne7xer). -- If it's not that, then it's a warranty job due to faulty HW
EDIT: you could try a complete wipe including re-partitioning, but that's a bigger job that you'd want to do in all honesty.
Click to expand...
Click to collapse
Could be my last option considering knox is tripped..
Got a link to a tutorial for re-partitioning?

Grab a PIT file for your device; - then you flash firmware with Odin / PIT file. - I have never done it, nor do I fancy doing it, but have a read (journeyman posted asking how and done it, it's in this section Q+A) - I can never remember whether you flash the PIT first then the firmware or both together. I wouldn't want to hazard a guess just in case though.
But if you've tripped KNOX, then yes, seems like it could be your last option, unless you have tried some various custom ROMs? ( I know sweetROM seems to be the master fix for any issues peple have on KK atm) could just be a stock issue currently that will more than likely get a fix at some point.
EDIT As yours is an AU phone, possible it could be a HK model? - from KOGAN? I know some AU users have had HK models from them.
EDIT2: When I flashed HAL ROM, @theresident stated in his how to OP that we needed to format /system during install - It's possible this may also fix it, but that wipes your entire system obviously and *IF* it doesn't boot up you then have issues
EDIT3 : quote from HAL ROM OP
Instalation:
1. Copy the zip to the phone
2. Reboot to Recovery/CWM
3. Wipe Data/Factory Reset
4. Wipe Cache
5. Wipe Dalvik Cache
6. Mounts and Storage then click "Format /System" (This won't delete any of your data)
7. Install.. wait one minute and ROCK !!!
Click to expand...
Click to collapse

crazy_777 said:
After kitkat upgrade.. if i use camera app such as camera 360 Or picsart, i can't save my photo to sdcard. It's error, Has anyone had or know how to resolve this problem???
Click to expand...
Click to collapse
You are hijacking.
Anyway,
1. Install es file manager or any file reader with root.
2. navigate to /System/etc/permissions
3. open "platform.xml" file to edit
4. look for the stack that has "WRITE_EXTERNAL_STORAGE"
you will find something like <group gid="sdcard_r" />
5. make sure these lines are there, if not, add them
<group gid="sdcard_rw" />
<group gid="media_rw" />
That's it

Help, lost my sound!

Hello fellow romers!
I recently decided to go back to Touchwiz but I failed. So then I went back to Temasek's CM12.1. Everything was fine until I decided to go full wipe and go v.15 (I was previously on 12.4 I think) and then I did something wrong. I went and did a full wipe on System (don't ask me why, I'm just stupid). So now I have no sound! Everything works as it should but the sound is completely gone.
I have tried reinstalling the phone to complete stock via odin but nothing works. I tried go back to a previous working backup that I have saved but it didn't solve the problem either.
So, to me it sounds like my drivers to my sound is gone or corrupt. Can I reflash it or something? This is really screwing me over since I really don't have the money to buy another Note 3. Help would be greatly appreciated! Thank you in advance.

BunnyPig said:
Hello fellow romers!
I recently decided to go back to Touchwiz but I failed. So then I went back to Temasek's CM12.1. Everything was fine until I decided to go full wipe and go v.15 (I was previously on 12.4 I think) and then I did something wrong. I went and did a full wipe on System (don't ask me why, I'm just stupid). So now I have no sound! Everything works as it should but the sound is completely gone.
I have tried reinstalling the phone to complete stock via odin but nothing works. I tried go back to a previous working backup that I have saved but it didn't solve the problem either.
So, to me it sounds like my drivers to my sound is gone or corrupt. Can I reflash it or something? This is really screwing me over since I really don't have the money to buy another Note 3. Help would be greatly appreciated! Thank you in advance.
Click to expand...
Click to collapse
What version of tw did you try to flash?

kenny1991 said:
What version of tw did you try to flash?
Click to expand...
Click to collapse
5.0.2

BunnyPig said:
5.0.2
Click to expand...
Click to collapse
Thought maybe you flashed a lower version.
Why don't you give it a fresh start? Absolutely cleaning whole internal memory. With latest cm12.1

kenny1991 said:
Thought maybe you flashed a lower version.
Why don't you give it a fresh start? Absolutely cleaning whole internal memory. With latest cm12.1
Click to expand...
Click to collapse
Well, that's what I'm trying to do right now. But ever since I installed the stock firmware my computer refuses to connect to my phone. So I can't do a backup of all my files. This is just getting weird now. The phone is extremely slow and it keeps saying "Music has stopped working." and it won't let me do anything because of that window... I am seriously thinking about breaking the phone in half at this point. I don't even know if my modem works, and I'm going back to work tomorrow! Damn, I'm getting really stressed out because of this.

Alright, I am in deep **** here and I really need help! How do I do to go back to complete stock?! Like, totally cleaning out my device and reinstalling it?! The phone is absolutely useless and I need to go back to a working state with everything working.
How do I hard reset my phone using odin?

Just got it to work. Apparently I had a bad version of Odin which made it impossible to flash a rom. After I redownloaded Odin to 3.04 it worked perfectly.

BunnyPig said:
Just got it to work. Apparently I had a bad version of Odin which made it impossible to flash a rom. After I redownloaded Odin to 3.04 it worked perfectly.
Click to expand...
Click to collapse
All good now?

kenny1991 said:
All good now?
Click to expand...
Click to collapse
Yeah, everything is working now. I flashed the stock firmware with the right region code and everything went back to normal. Why I couldn't flash it was because of a bad version of Odin. Felt kinda stupid for not trying that before I posted here. Thank you for the replies!

BunnyPig said:
Yeah, everything is working now. I flashed the stock firmware with the right region code and everything went back to normal. Why I couldn't flash it was because of a bad version of Odin. Felt kinda stupid for not trying that before I posted here. Thank you for the replies!
Click to expand...
Click to collapse
NP
So it may help others.