Hello all.
Seems that some of us are facing problems with NFC with the new batch of PIE ROMS.
https://forum.xda-developers.com/showpost.php?p=80552395&postcount=59
https://forum.xda-developers.com/showpost.php?p=80522209&postcount=98
https://forum.xda-developers.com/showpost.php?p=80521379&postcount=32
In my experience, there is not a single flavour ROM problem, but involves all the versions here.
Is there any hope this will be treated by any of the devs? This is not a request but a pray...
Regards, and thank you
Correct me, if I'm wrong, but since all those pie ROM's are built with OrdenKriegers device tree, they all should have that same problem...but maybe he will fix it...
Occam razor would say it is the most probable source. ..
Let's hope @OrdenKrieger (or another one) identifies the problem
Regards
nice nick nickuyist....
Just a quick follow up, I'm still experiencing issued with NFC on Resurrection Remix Pie. Has anyone successfully gotten NFC to work on Pie? If so, did you do anything special such as flashing a different vendor?
Related
Hey guys,
with RR being the rom i like best (mostly due to its insane custom features), and because i don't really know how to build from source, i attempted to port it by merging the RR of my 6p with the cyanogenmod for the z4 tab( following this guide: http://forum.xda-developers.com/chef-central/android/guide-how-to-port-lollipop-marshmallow-t3283452 ) . I was expecting it to work without major issues due to the hardware of both devices being mostly the same, but on the first try i got a "systemUI has stopped" and nothing else. Then i replaced systemUI with the version of cyanogenmod and got it to show the navbar and notification bar but it reboots if i try to push any buttons (video: https://www.youtube.com/watch?v=64ez0TpIrf0). At this point i'm pretty much out of ideas, so if maybe some of you know about anything useful for such issues or maybe someone knows of a guide or some general directions for building roms from source i would be very happy. (BTW, tried running adb logcat with it plugged in and it doesn't find the device but i'm not sure if its the problem with android or my setup because i haven't tried with other devices)
EDIT:
got a great offer for my z4 and sold it, getting a windows tablet/laptop, so this post can be ignored as i will no longer be trying to port RR
Oh wow. It would be awesome to have Resurrection Remix on the Z4T. Sounds like you'll need help from an experienced dev though.
EDIT:
got a great offer for my z4 and sold it, getting a windows tablet/laptop, so this post can be ignored as i will no longer be trying to port RR
Click to expand...
Click to collapse
Lol. Ah well.
Hello, I should be buying a Swift 2 Plus soon, and as a complete noob, I don't know what the death of Cyanogen is going to do to my device. Obviously it won't instantly brick it, but how am I gonna get future Android updates without installing a custom rom?
have a sexy christmas
Please, read my post here, and the (unconfirmed) Wileyfox's response to Cyanogen move here. It should be enough to clear your doubts
linuxct said:
Please, read my post here, and the (unconfirmed) Wileyfox's response to Cyanogen move here. It should be enough to clear your doubts
Click to expand...
Click to collapse
One thing relating more to the custom ROM area. So some of the CM team (not COS) are rebranding as lineage OS right. And they are continuing off the codebase of CM however we don't have a build of CM so how will and developer , from lineage or anywhere else, build a custom ROM without code from CM or AOSP. Unless Cyanogen Inc release the source code for our phone which I'm not sure they will. (Sorry if this is a noob question)
person123321 said:
One thing relating more to the custom ROM area. So some of the CM team (not COS) are rebranding as lineage OS right. And they are continuing off the codebase of CM however we don't have a build of CM so how will and developer , from lineage or anywhere else, build a custom ROM without code from CM or AOSP. Unless Cyanogen Inc release the source code for our phone which I'm not sure they will. (Sorry if this is a noob question)
Click to expand...
Click to collapse
You're absolutely correct. We can't start with the development with no sources. However, I don't think Cyanogen would do that at the moment, and, after seeing Wileyfox's response to Cyanogen moves, I think (and actually hope) they'll switch to an AOSP-based ROM with Android N 7.0 upgrade, and if that happens I'm really sure they'll have no problem on releasing the source code (remember Wileyfox devices tend to be quite developer-friendly). From that, we can work on bringing Lineage...
SlimRoms is a custom android operating system. Our main goal is to offer users a slimmed down yet feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by our public Gerrit to submit patches of any type.
Slim7 is the project name for SlimRoms based on Android 7.1.1 Nougat and offers the following original features:
Slim Navbar & Hardware key rebinding
Single tap action, long press action, double tap action!-We’ve got you covered.
Slim Actions & Chamber of secrets
Customise your device to the fullest -You’re a wizard!
SlimRecents
A Faster alternative to stock recents -Your device, your choice.
SlimLauncher
An Open source, feature filled launcher! -Make yourself at home
Status bar customisations
Clock and Date? Battery? -More fun than you can shake a stick at.
Important links:
slimroms.org - Our official website and your source for anything SlimRoms related.
Downloads - Slimify your device!
Unofficial Downloads J500F and M - Build0.13
Unofficial Downloads J500FN - Build0.13
For information on bugs, requirements, notes and more, read the second post.
Installation instructions - Follow these steps if you want SlimRoms on your device.
FAQ - Have a question? Consider reading our FAQ first, you might find your answer there!.
Report-bugs - Found a bug? Send it our way!
Kernel Source - The source of your device's kernel.
Get in touch! - You can contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Disclaimer: We are not responsible for any damages to your device.
Can you pour me some coffee?
XDA:DevDB Information
SlimRoms Slim7 Android Nougat, ROM for the Samsung Galaxy J5
Contributors
EsromG5
Source Code: https://github.com/SlimRoms
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Bootloader LP and Modem MM (modem mm for FM works)
Based On: Aosp, Slim
Version Information
Status: Testing
Current Beta Version: Build0.13
Beta Release Date: 2017-02-15
Created 2017-02-15
Last Updated 2017-03-04
Reserved
What works?
RIL (Calls, sms, data)
Bluetooth (also with audio)
Camcorder
Camera general (1080p works fine)
Video Playback
Dados and RIL
Wifi
Audio
Sensors
LED
Flash
Hostpot
InCall
GPS
OTG
FM (use modem MM)
What does not work?
No, you tell me
Notice:
n/a
First
Good job, waiting for FN
second ....
good job bro.. i m so lucky that I own j5f :fingers-crossed:
wooow j5 developement is skyrocking this month, i will install it when theres the proper incall audio (im not crying for fix, just sayin)
Why don't you concentrate first resolving issues on the other roms? What is the sense of releasing every kind of roms but with the same issues?
Booted on FN, but System UI has stopped
Telepracity said:
Booted on FN, but System UI has stopped
Click to expand...
Click to collapse
Without patch?
Deleted
JosephDM said:
Why don't you concentrate first resolving issues on the other roms? What is the sense of releasing every kind of roms but with the same issues?
Click to expand...
Click to collapse
WelI think it is just as good making normal roms. The in-call isue and other bugs are related across all N roms so that means that if it gets fixed on one then you'll have all the other roms fixed in a small matter of time and now you have 3 working Nougat roms instead of one non functioning rom
EsromG5 said:
Without patch?
Click to expand...
Click to collapse
With a patch from lineage os
MM kernel
Amarius1 said:
WelI think it is just as good making normal roms. The in-call isue and other bugs are related across all N roms so that means that if it gets fixed on one then you'll have all the other roms fixed in a small matter of time and now you have 3 working Nougat roms instead of one non functioning rom
Click to expand...
Click to collapse
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
Well... You are right sir. In-call audio is really really important and I wish someone knew why it was happening..
I didn't mean in call audio. I meant this ROM doesn't even boot normally and they have no clue why, yet instead of trying to debug they release bunch of not working builds. Camera doesn't work and it will not work since you'd either have to use updated open source HAL or revert Nougat media changes and it won't be a surprise if I'll tell you they have no idea how to do it. The only real devs, who knew what they were doing left because their work was posted by someone else and now he's making blind commits in hope that things will magically fix themself. They won't. I might as well tell you that development on J5 is dead unless someone new with actual knowledge steps in. Don't expect any significant changes. We can't even take patches from any other msm8916 devices, because they have more advanced development and use a lot of open source projects instead of prebuilt libs like we do. Even camera in CM13 is not fully fixed because open source cam doesn't work for us and after debugging it for 3 weeks I've still didn't come up with reliable solution to make it work (only made some errors dissapear).
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
You're not totally sure.
Creating new roms is just to try to see if there are different results and not just to flood the forum with crap.
The name of the forum is XDA - DEVELOPERS, this means that it is of full use to developers, if the person does not know how to help, it just stays silent while someone else can do it. Your help in testing is much appreciated since we are trying to do something free for you, and still prefer to say things like that.
I thank you and respect your concept, but try to help instead.
Amarius1 said:
Well... You are right sir. In-call audio is really really important and I wish someone knew why it was happening..
Click to expand...
Click to collapse
The problem with incall and other stuff is already encountered by SoUnd001, but the big problem is that we're not hitting what it does so it's not booted, you're getting errors with incall and stuff because of the patch you're installing, not because of Rom or current kernel.
NOTICE:
I'm finishing a build for J500FN, we know it may not start properly, but I want to know the result for these users. I hope the sooner I have it all working.
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
Considering our device only has Marshmallow we can afford to deal with some bugs. If i read correctly RR 6.0.1 only has the radio bug so we have a working Marshmallow rom. The next logical step is to make Nougat and they do not have a kernel thats Nougat based so thats why they are running into problems and why we have to use patches. Im almost 100% sure that once we get official Nougat to our device, 99% of the bugs in these roms will disappear
[email protected]@!3Z said:
Considering that they have built nougat from source when our device only has Marshmallow we can afford to deal with some bugs. If i read correctly RR 6.0.1 only has the radio bug so we have a working Marshmallow rom. The next logical step is to make Nougat and they do not have a kernel thats Nougat based so thats why they are running into problems and why we have to use patches. Im almost 100% sure that once we get official Nougat to our device, 99% of the bugs in these roms will disappear
Click to expand...
Click to collapse
I think there will not be an official nougat firmware from Samsung.
Gent' said:
I think there will not be an official nougat firmware from Samsung.
Click to expand...
Click to collapse
In the Skies telegram group there was confirmation for official Nougat
EsromG5 said:
You're not totally sure.
Creating new roms is just to try to see if there are different results and not just to flood the forum with crap.
Click to expand...
Click to collapse
FYI: ALL custom ROM are using the same hardware repo's maintained by CAF, CM(Lineage now) or AOSP. There won't be any different results. The most important repos are all the same. The fact that you don't know that and your friend's github sources show that there is nothing to be helped. You're just playing games with users pretending you could make things work. What for? In the end they will be the ones left with nothing but promises. People, who could actually do something left, because someone took their work and published it to take all the applause for it and now you're blindly trying changes hoping they would somehow fix things.
[email protected]@!3Z said:
Considering that they have built nougat from source
Click to expand...
Click to collapse
They built from the source already made by ganesh. Their own changes are blindly trying things that have no right to work in the first place. Builiding android from someone's ready sources is like walk in a park.
Gent' said:
I think there will not be an official nougat firmware from Samsung.
Click to expand...
Click to collapse
Certainly not for J5 2015, maybe 2016 but it could benefit us anyway since these devices are similiar.
I'm done, Moderator will probably soon come and delete my posts since all they care about is keeping forum clean. You may consider this device dead at the moment.
[email protected]@!3Z said:
Considering that they have built nougat from source when our device only has Marshmallow we can afford to deal with some bugs.
Click to expand...
Click to collapse
I understand from your post that Sound001 or EsromG5 did the hard work, but its not like that.
@Nick Verse and @ganesh varma were the ones who built cm12.1 and cm13 from source. They were also working on cm14 source while they were working on cm13.
So, please edit your post and dont mislead people.
Koloses said everything.
Since Nick and Ganesh left J5 development because their project which were working on was posted by someone else, the issues of Nougat CM/AOSP based roms wont be solved.
This:
I might as well tell you that development on J5 is dead unless someone new with actual knowledge steps in.
Click to expand...
Click to collapse
This is unofficial lineageos 16 for Motorola Clark. It is only compatible with nougat firmware - you must have the nougat bootloader and modem flashed on your device.
Tons of thanks to hashbang for all of his work
Kernel Source-
https://github.com/randomblame/android_kernel_motorola_msm8992
Device tree-
https://github.com/randomblame/android_device_motorola_clark
Current status of rom-
Daily Driver
Broken-
Camera post processing- rotation is not accounted for in hal with latest round of hacks credit to AgathosAnthropos for fixing image capture by disabling the calls to pp, hold device in landscape for photos
Tethering - it works but device will soft reboot when tethering stops
Dual sim variants are NOT supported! I do not have the hardware to test and fix at this time - bugreports appreciated
Working - everything else?
Try it yourself (Requires Nougat Firmware and as always wipe data+cache)
Latest Releases:
1/12/2020 https://www.androidfilehost.com/?fid=4349826312261700035
8/1/2019 https://www.androidfilehost.com/?fid=6006931924117928331
Don't forget to grab a compatible version of gapps for 9.0
https://opengapps.org
Once again this rom REQUIRES that the stock nougat firmware was properly flashed to work correctly... It will check before installation that you have the correct modem version installed.
*If your radio does not work you may have the wrong modem
*If you can not switch lockscreen to pin or pattern you may have the wrong modem.
*Modem flashes fail quietly sometimes please make sure you have properly flashed it before reporting issues.
Great! [emoji6]
Enviado desde mi Nexus 5X mediante Tapatalk
I'll be happy to test once there is a working rom
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Can't wait to see more from this
We wait impatiently.
Spent a couple more hours going through init narrowing it down failure happens just before zygote startsI currently have my pure propped up in charging position so I can work more on it it's had a hard life
Thank You so much
randomblame said:
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Click to expand...
Click to collapse
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Moto X Pure XT1575 said:
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Click to expand...
Click to collapse
Hi, I have the Lineague 14.2 installed. What I did to eliminate the bootloader check was to edit the uptader-script
Fixing error caused by missing taskstats kernel feature
Hi randomblame,
A quick review please, could you tell us the intended purpose of your project.
Meaning like I'm thinking it's for a "Moto X Pure 2015 (clark)" device isn't it?
Would that be for everyone on this XT1575 device which has upgraded to a stock Nougat kernel and modem?
Or could/would others benefit from it as well with your research here - other moto's?
Any and all answers - thoughts are welcome in understanding the project...
Thanks for the lady power on XDA,
RIF
This device can have a new future. Think about it !
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
randomblame said:
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
Click to expand...
Click to collapse
I'm trying to follow along with your posts best as is possible for me - but, so sorry I and as well many others are lame to understand the under-the-hood workings of Android.
Are you saying in such a way that the Moto Pure XT1575, will maybe and with your research efforts move forward to a true PIE OS possibly?
Maybe I'm reading to much into your words.
But, as I follow your posts, you'll advance us Pure device owners beyond the Nougat kernel - or at least try too?
Or yet with your efforts will this yield something like HashBang did for the XT1575 device when a Nougat OS wasn't even a thought of possibility from Motorola for us.
Back then, HashBang had worked the Nougat OS on the Marshmallow kernel and modem - I'm very green to all of this - but that's what I understood.
Still that's good none the less if that will come here from you with PIE on Nougat internals...
Beings Motorola support is dead for our device for anything future of an OS update - not to mention security patches.
If you would spell it out better as any interested XT1575 owners now could grasp the concept here in your efforts - create a buzz for a greater community following. More MXP owners to jump on board as gained support from well wishers.
Is it to early yet for that? Is there a fear that someone could steal it out from under you? Unexpected negativity, or is it just the way you wish to present this to us for the present.
I'm still going to watch and support this project with high hopes no matter what may come in the end...
Could you benefit knowledge from a LineageOS 16 for Moto Z. download?
https://www.cyanogenmods.org/forums/topic/download-moto-z-lineage-os-16-android-9/
For people like me,
Device Tree = https://source.android.com/devices/architecture/dto
and on XDA
https://forum.xda-developers.com/android/software/guide-how-to-make-device-tree-phone-t3698419
As for any active developers still left for the XT1575 a big thank you to you all, seems to me like a daunting task to crawl inside of android moreless understand things once your there...
Kernels are only loosly linked to Android versions, Google maintains the Android-common kernel repos which are usually quite far behind mainline Linux, and caf who maintains Qualcomm specific kernels are further behind in general. Literallyany feature required by Android can be backported to an old kernel I'm sure 2.6.27 could run pie but it would need so many patches it would be an unrecognizable mess. It will become progressively more of a nuisance as time goes on to keep patching up 3.10 Pie "requires" 4.4 for new devices but only needs kernel features from 3.18 which I've backported to 3.10. with each new version of Android more assumptions are made about how modern the devices kernel is and what features it has so moving to a newer kernel would be nice and like I said 3.18 seems doable but it will still be quite a bit of work.
Thank you @randomblame I was able to grasp most of that...
Maybe it's too early but, how does Googles Android security patches figure into this - if they are possible to bring us forth from Oct 2017?
Remembering I'm a laymen to the nuts and bolts of android.
I understand your post #16 - Super !
Security patch version is irrelevant when you are building from the latest source
Obnoxiously after a few builds the dedicated 250gb SSD is full and I have to make clean which takes ages, I nooped every thing but the basics didn't include telephony or wifi, ril, audio, Bluetooth GPS nfc etc and left it to build overnight will test after work trying to narrow down the problem
Surface flinger is the culprit
I have the device laying around and getting no use. Will sure donate some $$$. Seeing a los16 with all working hardware would be great.
Only got a couple hours to work on it this weekend, there is an issue where /system/vendor is not symlinked to /vendor early enough and calls for things in /vendor fail thus the issue, since we don't have a physical /vendor partition it can not be mounted immediately via the kernel. Tis annoying. I can change the calls to /system/vendor or maybe make it symlinked earlier when I get a chance
Hello community! I'm here to inform you some users (especially rooted ones) facings random touch issue after rebooting on OSS vendors roms. led Developers are trying to figure & fix it. so there is no fix for now. I had opend this thread to make it clear to all of you.
besides, Could you provide us if you faced this issue with your device info (ram capacity and variant) , please ?!
• Hit "Watch" button to get all news of This thread, I will inform you if there is a fix or solution.
• Touch Issue has been fixed thanks @MPK99 & regards to @ZIDAN44 . Now wait for your rom maintenaner to update his rom. thanks
Thanks in advance
Stay safe
Regards
Spoiler: What is OSS build?
- Stock-vendor refers to the firmware for the phone that is developed by the manufacturer of the phone.
Currently it is believed to be more stable than the OSS-vendor. The problem with the stock-vendor is that in time the support will stop (no more upgrades to newer Android versions), because the manufacturer prefers you to buy a new phone instead of using your phone for years.
The OSS-vendor refers to a firmware developed by the open source community.
It is expected that the OSS-vendor will be supported for much longer than the stock-vendor.
As per our lead devs, it's been reported that the issue is the lack of touch fw within the kernel. As all rom maintainers use pixel experience kernel source, face this problem. Even custom kernel devs had the same commits from pixel experience, brought the issue even there. So oss roms with custom kernels included will probably have it too.
Afaik, I believe there's some issue with stock vendor too. We're investigating it & will let you guys know soon.
Abdullah.Csit said:
Hello community! I'm here to inform you some users (especially rooted ones) facings random touch issue after rebooting on OSS vendors roms. led Developers are trying to figure & fix it. so there is no fix for now. I had opend this thread to make it clear to all of you.
besides, Could you provide us if you faced this issue with your device info (ram capacity and variant) , please ?!
• Hit "Watch" button to get all news of This thread, I will inform you if there is a fix or solution.
Thanks in advance
Stay safe
Regards
Click to expand...
Click to collapse
Yes , i got the touch issue in my RN10 4+64 Global Variant ... on all OSS ROMs i tried .... after 2 or 3 reboots , touch is not responding anymore and i need to force reboot. So for now i will avoid oss builds because i reboot the phone too often (why? idk)
Thanks to our developers for the hard work
So, I've myself managed to find a loophole in vendor fw, & I've fixed the touch issues. Being testing this patch with multiple reboots & flashes, & haven't got touch issues on oss test build so far. Will let you know after some rigorous test, whether it's got rid or not.
Abdullah.Csit said:
• Touch Issue has been fixed thanks @MPK99 & regards to @ZIDAN44 . Now wait for your rom maintenaner to update his rom. thanks
Click to expand...
Click to collapse
This issue has been fixed
@shadowstep Now can close "Lock" this thread
Regards
thanks
Abdullah.Csit said:
This issue has been fixed
@shadowstep Now can close "Lock" this thread
Regards
thanks
Click to expand...
Click to collapse
Thanks to our great developers... Waiting for crDroid
THREAD LOCKED
Requested by OP.
Regards,
shadowstep
Forum Moderator