Database Info

Cyanogen mod 7.1 with .629?

hi,
i got a warranty replacement d2g with .629 on it. can i install cyanogen 7.1 on it? thanks.

CM 7.1 will not work with .629, as it relies on an older kernel. Not even .608 works with CM 7.1.

This is a blatant lie.
Unofficial CM7 builds work fine with 4.5.x firmware, and they're usually pretty up to date.

well i couldn't get it to install the one time i tried but i have two different answers here i read that beta 9 works which is what i would rather use but i don't want to use it until it's stable.

For unofficial CM7 (currently 7.2, I think), refer to http://rootzwiki.com/topic/3069-dev-threaddroid-2-global-cm7-with-gingerbread-leak-kernel/
Check the last few pages there for most current builds.

Gasai Yuno said:
This is a blatant lie.
Unofficial CM7 builds work fine with 4.5.x firmware, and they're usually pretty up to date.
Click to expand...
Click to collapse
He asked for 7.1, I gave a response regarding just the functionality of 7.1.
He didn't ask for information regarding builds after 7.1.

I appreciate the advice. I downloaded Cyanogen mod gb kernal based Pooka-CM4D2we-GB-20120330.zip and it is running fine, hopefully cm9 will be stable soon enough because i want some ics on this phone off topic, i'm a she btw

projektorboy said:
He asked for 7.1, I gave a response regarding just the functionality of 7.1.
He didn't ask for information regarding builds after 7.1.
Click to expand...
Click to collapse
It is not a question of version number but of origin. ALL official CM 7 builds rely on Moto's Froyo kernel and cannot be installed over newer stock firmwares. But there have been lots of unofficial builds made for Moto's Gingerbread kernel that work just fine with all the newer stock firmwares (4.5.6xx)

[Q] JB MIUI For Galaxy S 4G

Hey guys, I have been looking for a jb miui ROM for this device and i cant find one, i know there are some ics miui ROMs, but i would really like a jb miui ROM.
There is one for the vibrant, can I use it for my Galaxy s 4G or can anyone port it to our device?
Vibrant MIUI JB ROM:
http://forum.xda-developers.com/showthread.php?t=2289234
Thanks

i'll build it when miui comes out with miui 4.2

airfluip1 said:
i'll build it when miui comes out with miui 4.2
Click to expand...
Click to collapse
Thank you i will be looking forward to it.

Beast said he would do it.
sent from me

that's been in my queue for a while along with aokp aries and paranoid android.

airfluip1 said:
i'll build it when miui comes out with miui 4.2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2313073

Just because there are some homebrew ports doesn't mean that MIUI is 4.2 yet.
http://en.miui.com/download.html
Official Downloads
Author : MIUI Developer Team
Kernel : Android 4.1
Latest update : 3.6.21
Download : http://www.miui.com/download.html
Language : Chinese and English
Click to expand...
Click to collapse

Why does it matter ? We use unofficial ROMs anyway...
sent from me

That's like saying that since a car, airplane, and weed-whacker all run on gas, you should just put the same stuff in each. Actually, the unofficial ROMS is a more tenuous connection than my gas connection. It's more like saying that since a bullet train, horse, and diesel bus all run on fuel, the fuel which goes into each shouldn't matter. It's all fuel.
Hey, you could (please don't) use an unofficial Vibrant ROM too. That's unofficial. What's the difference? The difference is that it won't work. And might brick your phone. That's bad.
Our only current Aries kernel is 4.2.2 and still has issues. MIUI is still 4.1.2 and would introduce an entirely new set of issues tied into GPS, Bluetooth, and so forth if/when a 4.1.2 Aries kernel was compiled. Does that make it impossible? No. But it means that as the build impetus - when MIUI is 4.2 - has not happened yet... it's not a great use of time yet. Unless one of the devs wants it. In which case, MIUI being not-updated is something they don't need to be hammered over the head with.

http://forum.xda-developers.com/showthread.php?t=2313073
4.2.2?

Port. If YOU see source linked from that page so our devs could actually do something useful to build that...

Hi Theraze
I have to disagree with you.
Port is not a dirty word and most of our ROMs are actually ports and not built from source. Furthermore, MIUI ROM is usually ported and not built from source and only recently did Xiaomi open their sources for the public. Even more than that, both MIUI versions brought to us by Beast were ports from Nexus and not built from source.
Now, regarding the incompatibility between kernel & OS - if it works on Nexus, I assume the adjustments were made, so one can enjoy both 4.2.2 & MIUI benefits. There is no logical reason why it couldn't be ported to our beloved device.
sent from me

I'm not saying it can't be done. I'm saying that our build-from-source dev who asked you to let him know when it hit 4.2 hasn't had his request met.
Does that mean that someone (him or another dev) CAN'T port it? Nope. But it makes it a lot less likely that air can just pull the source in and compile it using the Aries bits if the buildable MIUI is still only 4.1.2 and our Aries is 4.2.2 instead.
Again, I think we're agreeing on the general bits... yes, this is possible. But airfluip1 asked to be notified when buildable MIUI was 4.2.2 and that's when he said he'd build it. Not port it.

I don't care if a ROM is ported or built from source.
I will try to play with porting it myself.

What stops the developer of a ROM like LiquidSmooth from basing the ROM off GPE ?

I know LiquidSmooth is based on Slim, which I believe is based on AOSP source. Either Slim is ported to our phone and Liquid is built on top of it, or Liquid, based on Slim, is ported to our phone (or they're both the same thing). Well, what stops someone who can take Slim and make it into LiquidSmooth, from basing it off of GPE instead?
Come to think of it, I've only seen ROMs based on GPE offer a couple tweaks. Nothing as extensive as something like LiquidSmooth. Can a GPE not be modified as extensively? Isn't it required to have its source posted due to the GPL or something?

dragontology said:
I know LiquidSmooth is based on Slim, which I believe is based on AOSP source. Either Slim is ported to our phone and Liquid is built on top of it, or Liquid, based on Slim, is ported to our phone (or they're both the same thing). Well, what stops someone who can take Slim and make it into LiquidSmooth, from basing it off of GPE instead?
Come to think of it, I've only seen ROMs based on GPE offer a couple tweaks. Nothing as extensive as something like LiquidSmooth. Can a GPE not be modified as extensively? Isn't it required to have its source posted due to the GPL or something?
Click to expand...
Click to collapse
GPE isn't aosp, it's Google play edition software. It isn't open sourced to be built off of. Think of it as more of a Sense or touchwiz interface than AOSP build. A GPE rom is built specific for each device it's operating on.
A GPE rom written for an HTC m8 will not work on a samsung galaxy s5, simply because the kernels are different. AOSP roms have the same kernel for all devices. That's mainly what would keep a developer from basing a rom off of a GPE code.
Slim is built AOSP source code, along with many other roms. Liquid chooses to use slimroms as a base, but it could choose to use CM, AOKP, or another AOSP base of their choosing. This doesn't apply to GPE.
GPE roms can be modified to do whatever the developer wants them to do. However, the whole point of GPE roms is to have a very fast, debloated close to stock experience. People looking for GPE roms aren't really looking for all the bells and whistles that go with highly modified stock or aosp roms.

Whoa... There is no such thing as a ROM that will run on both an HTC One M8 and a Samsung Galaxy S5. That isn't a valid limitation of GPE. Kernels are always device specific, too. You might get a universal kernel that works across variants of one phone, but I've never heard of a kernel, an aftermarket one anyway, that will run on devices across manufacturer lines. Then again, I don't follow kernels as closely as I have ROMs.
GPE isn't open source? That's news to me. I mean, I thought all Android builds had to provide source. I mean, rule #1 of XDA is don't ask for ETAs, but I saw a moderator demand source on a ROM "sooner than later." Not naming names because I'm sure the moderator was within rights, but it seemed to at least partially contradict the spirit of the famous rule.

dragontology said:
Whoa... There is no such thing as a ROM that will run on both an HTC One M8 and a Samsung Galaxy S5. That isn't a valid limitation of GPE. Kernels are always device specific, too. You might get a universal kernel that works across variants of one phone, but I've never heard of a kernel, an aftermarket one anyway, that will run on devices across manufacturer lines. Then again, I don't follow kernels as closely as I have ROMs.
GPE isn't open source? That's news to me. I mean, I thought all Android builds had to provide source. I mean, rule #1 of XDA is don't ask for ETAs, but I saw a moderator demand source on a ROM "sooner than later." Not naming names because I'm sure the moderator was within rights, but it seemed to at least partially contradict the spirit of the famous rule.
Click to expand...
Click to collapse
Ehh, GPE may be open sourced. I think Google has to release the information for it.
AOSP though definitely isn't as specific, the kernel has to be signed for each device but it's overall much easier to port the kernel over to another device.

kernels
The Linux kernel is a monolithic kernel and all device specific drivers are compiled in the binary unless they are stand alone modules. Android itself is open source, but it does NOT use the GPL v2 licence. The code for many of the drivers and other device-specific software is closed source and only available as binaries. XDA strictly enforces providing source code for kernels because that is a strict stipulation of GPL v2. A custom ROM generally doesn't require source code since many stock-derived ROMs don't begin with source code. Sense and GPE would be varieties that don't originate from source code.

Several Noob questions about custom ROMs?

Hi guys,
I always read in the Xda forum but never wrote or asked a question...usually someone already asked them.
so I have the Mi 5S PLUS...but I hate the miui UI. can't get used to it. And yesterday I finally found that there are custom ROM for this device.
So I got few questions.
1. As far as i know, the source code hasnt been released but should be released soon. should I wait for a ROM that uses the source code?
2. I see that the most popular costum ROMs for this device are - Lineage and resurrection remix. In terms of battery life, stability and bug free rom. which one is the best?
3. I see there is one ROM with the tag [OFFICIAL]....does this mean it uses the source code? if not, what does it mean?
thanks a lot to those that answer

eliko2000 said:
Hi guys,
I always read in the Xda forum but never wrote or asked a question...usually someone already asked them.
so I have the Mi 5S PLUS...but I hate the miui UI. can't get used to it. And yesterday I finally found that there are custom ROM for this device.
So I got few questions.
1. As far as i know, the source code hasnt been released but should be released soon. should I wait for a ROM that uses the source code?
2. I see that the most popular costum ROMs for this device are - Lineage and resurrection remix. In terms of battery life, stability and bug free rom. which one is the best?
3. I see there is one ROM with the tag [OFFICIAL]....does this mean it uses the source code? if not, what does it mean?
thanks a lot to those that answer
Click to expand...
Click to collapse
1. Source code is released but rom based on source code are not released yet .You can use them but their are some bugs,
2.You can check yourself
3. Official means official rom from lineage team or other maintainers just like Global MIUI rom from xiaomi is official while xiaomi.eu is unofficial .
You can check for source in rom page for more info about what device tree and source code it uses

ashish289 said:
1. Source code is released but rom based on source code are not released yet .You can use them but their are some bugs,
2.You can check yourself
3. Official means official rom from lineage team or other maintainers just like Global MIUI rom from xiaomi is official while xiaomi.eu is unofficial .
You can check for source in rom page for more info about what device tree and source code it uses
Click to expand...
Click to collapse
Thanks for the answers. But I asked because I prefer to install one and that's it. and if someone used the both ..why not to hear opinions.

I recomend RR

eliko2000 said:
Thanks for the answers. But I asked because I prefer to install one and that's it. and if someone used the both ..why not to hear opinions.
Click to expand...
Click to collapse
The reason that people don't recommend one over the other is because YMMV. I know I came from a cyanogen ROM with my previous phone and dirty unicorns on the phoen before that (along with a whole set of custom ROMs). In the end though, I found them all to be "similar". Yes, some do some things differently like some offer a lot of CPU governors, while others keep the list pretty tight. Some default with swap space on, some don't use swap space at all (this phone shouldn't need swap space). Sometimes the difference between two ROMs is just the launcher.
For me, I don't really like the MIUI launcher. It feels a lot like an iphone. This isn't a bad thing. Some people like it. I just install Apex (from the play store) and my issues with the ROM were mostly resolved. The only remaining problem is MASS STORAGE. But, based on my experience with mly previous phone, I doubt I'll find a ROM that natively supports it. But I know how to hack my way in and get that going (just need root... which requires an unlocked bootloader... and if I am reading things correctly, you need to wipe everything which I currently not willing to do... but may have found a workaround... going to test it out tomorrow).

bmg002 said:
The reason that people don't recommend one over the other is because YMMV. I know I came from a cyanogen ROM with my previous phone and dirty unicorns on the phoen before that (along with a whole set of custom ROMs). In the end though, I found them all to be "similar". Yes, some do some things differently like some offer a lot of CPU governors, while others keep the list pretty tight. Some default with swap space on, some don't use swap space at all (this phone shouldn't need swap space). Sometimes the difference between two ROMs is just the launcher.
For me, I don't really like the MIUI launcher. It feels a lot like an iphone. This isn't a bad thing. Some people like it. I just install Apex (from the play store) and my issues with the ROM were mostly resolved. The only remaining problem is MASS STORAGE. But, based on my experience with mly previous phone, I doubt I'll find a ROM that natively supports it. But I know how to hack my way in and get that going (just need root... which requires an unlocked bootloader... and if I am reading things correctly, you need to wipe everything which I currently not willing to do... but may have found a workaround... going to test it out tomorrow).
Click to expand...
Click to collapse
Wipe everything is very simple connect the phone via USB cable to PC and via twrp wipe everything then past a Rom on the phone and flash it, that's it

venezolano69 said:
Wipe everything is very simple connect the phone via USB cable to PC and via twrp wipe everything then past a Rom on the phone and flash it, that's it
Click to expand...
Click to collapse
Wiping everything is easy, yes, but I want to avoid wiping if I don't have to.
Got the phone rooted without needing to wipe it (yay), but getting mass storage enabled failed on me. I can't seem to write to the file I need to which confuses me... but that is off topic so I'll refrain from boring you with details on that.
Back on topic, if you are switching to a custom ROM you will need to wipe things. I personally would wait for a custom kernel to come out before you start playing with custom ROMs unless the custom ROM has a feature you REALLY want. With my previous phones, the one that had a custom Kernel as well as custom ROMs was a lot more stable and had a lot fewer bugs. The one that had only factory kernel, the custom ROMs were flaky. They mostly worked, but they did have bugs. If I got a phone call or called somebody and they hung up first, it would crash the dialer and the dialer would fail to start again until I rebooted. Now a custom kernel may not have helped that, but since the kernel was based on a previous version of Android, it was unstable.
The current custom ROMs (that I have seen) are all based off of the stock kernel and not newer ones so I personally do not expect to see much benefit in changing ROMs except having different bloat and a different launcher. Well, at lest for the things I use my phone for. But YMMV.

Moto Maxx running some roms of nexus 6

Hello.. I would like to ask developers which file we need to replace for normal boot (not opposite) ..some custom rooms for nexus 6 boot on moto maxx xt 1225...please look video.
https://youtu.be/RxoNMuIPQbw

jaaa1976 said:
Hello.. I would like to ask developers which file we need to replace for normal boot (not opposite) ..some custom rooms for nexus 6 boot on moto maxx xt 1225...please look video.
Click to expand...
Click to collapse
Thanks bro...

I already knew that, but the Custom ROM developers for Quark are too proud to use what already exists for Nexus 6 in Quark. They prefer to stay back and stay on the hard way.

vinydasilveira said:
I already knew that, but the Custom ROM developers for Quark are too proud to use what already exists for Nexus 6 in Quark. They prefer to stay back and stay on the hard way.
Click to expand...
Click to collapse
You really have no idea what you are talking about. Did you even go to that link and actually read? No, you didn't or you wouldn't be making comments like that.
moto maxx (xt1225) running rom stock of nexus 6. totally unstable. stock 7.1.1
*Kernel AOSP - Quark (This is merely @bhb27 LOS kernel or his standalone, there is NO such thing as "Kernel AOSP -Quark")
*Stock 7.1.1
Click to expand...
Click to collapse
Why would we want to run something like that (unstable Nougat ROM) on our Quarks when we already have VERY STABLE Nougat custom ROMs? Why would we want to run UNstable 7.1.1?
Plus, whoever wrote that seemingly doesn't know what they are talking about either....
If it's "kernel AOSP - Quark" -- well, there's no such thing. That means it's @bhb27's kernel code. There is no "AOSP kernel" for Quark. Whoever wrote that doesn't know much about Quark dev work. No ROM can run on our Quark phones without a compatible kernel, and @bhb27 has coded both LOS stock kernel and his own advanced standalone kernel (with more features, options). All the Quark custom ROMs (including AOSP) use the LOS stock kernel -- which @bhb27 coded. All the Quark custom ROMs actually use the SAME kernel.
If he had said "LOS kernel -- Quark", that would be more accurate. Or @bhb27 kernel".
You can even run @bhb27 kernel with Motorola Marshmallow stock. You don't need a custom ROM. It's a great kernel!
All that YouTube post means is someone took @bhb27 kernel code and managed to horribly port a Nexus 6 stock-based ROM over it. They didn't do any magic -- any more than any other ROM like RR, LOS, AOSP runs on Quark right now, with @bhb27 kernel. All they did was badly port a Nougat 7.1 "stock" ROM that they say is unstable. Whoopee.
I'm all for more ROMs, but you need to understand how ROMs are made -- they are built on the foundation of the kernel. ANY Nougat ROM can be ported to our phones, as long as you use the Quark kernel.
The reason why "stock" ROMs are not done are because they are boring. You wouldn't have the LED notification for instance that @bhb27 created, nor all the options present in Revolution Remix and crDroid. Even @calsurferpunk's LOS ROM is more of a hybrid -- LOS + some of the more popular options in RR. We already HAVE up to date 7.x Nougat ROMs. And they run well. How many more do you want?
This Nougat ROM in this video is running on @bhb27 kernel code -- just like every other ROM we have. So, how is it any different?
What people WANT are Oreo ROMs. The the only reason we don't have Oreo ROMs right now, because @bhb27 has to adapt the last kernel Motorola gave us (Marshmallow) to work on Oreo, the way he did for Nougat.

ChazzMatt said:
You have no idea what you are talking about. Did you even go to that link and actually read? No, you didn't or you wouldn't be making comments like that.
Why would we want to run something like that on our Quarks when we already have VERY STABLE Nougat custom ROMs? Why would we want to run UNstable 7.1.1?
Plus, whoever wrote that seemingly doesn't know what they are talking about either....
If it's "kernel AOSP - Quark" -- well, there's no such thing. That means it's @bhb27's kernel code. There is no "AOSP kernel" for Quark. Whoever wrote that doesn't know much about Quark dev work. No ROM can run on our phones without a compatible kernel, and @bhb27 has coded both LOS stock kernel and his own advanced standalone kernel (with more features, options). All the custom ROMs (including AOSP) use the LOS stock kernel -- which @bhb27 coded. All the custom ROMs use the same kernel.
If he had said "LOS kernel -- Quark", that would be more accurate. Or @bhb27 kernel".
You can even run @bhb27 kernel with Motorola Marshmallow stock. You don't need a custom ROM. It's a great kernel!
All that post means is someone took @bhb27 kernel code and managed to horribly run a Nexus 6 stock-based ROM over it. They didn't do any magic -- any more than any other ROM like RR, LOS, AOSP runs on Quark right now, with @bhb27 kernel. All they did was badly port a Nougat 7.1 "stock" ROM that they say is unstable. Whoopee.
I'm all for more ROMs, but you need to understand how ROMs are made -- they are built on the foundation of the kernel. ANY Nougat ROM can be ported to our phones, as long as you use the right kernel.
The the only reason we don't have Oreo ROMs right now, because @bhb27 has to adapt the last kernel Motorola gave us (Marshmallow) to work on Oreo, the way he did for Nougat.
This Nougat ROM in this video is running on @bhb27 kernel code -- just like every other ROM we have. So, how is it any different?
Click to expand...
Click to collapse
Great. Amazing. You changed my mind ...
Now tell me. Why not use what we have from the Oreo of the Nexus 6 to advance the Oreo of the Maxx? Because the Nexus 6 devs already have Oreo 8.1.0 running on Nexus 6. When I talked about standing back and doing the hard way I was referring to that.

vinydasilveira said:
Great. Amazing. You changed my mind ...
Now tell me. Why not use what we have from the Oreo of the Nexus 6 to advance the Oreo of the Maxx? Because the Nexus 6 devs already have Oreo 8.1.0 running on Nexus 6. When I talked about standing back and doing the hard way I was referring to that.
Click to expand...
Click to collapse
It's about the kernel. The kernel is the foundation of all ROMs. You notice the YouTube video is merely a Nexus 6 NOUGAT ROM that doesn't run well on Quark. Because we have Nougat compatible kernel right now.
@bhb27 actually said he is using some of the Nexus 6 stuff for CLUES to adapt the Quark kernel for Oreo. But it's not easy. Until you have a compatible kernel, no Oreo ROMs will run on Quark. @bhb27 has actually gotten Oreo Resurrection Remix to run on Quark. Have you not seen the screenshots? But at this point it's still unstable.
Once you have a kernel, you can have 100 Oreo ROMs on Quark in a week -- if you find 100 people willing to port the ROMs. It's almost plug and play (for dev maintainers who have those skills). This is why we have had so many "drive by" ROMs dropped into this forum and then those people walk away without ever updating them. They were taking advantage of @bhb27's kernel work. Take ROM, plug in kernel, done. But they never stuck around to keep them updated, or even test them thoroughly, and some didn't even own a Quark phone. One of them even used @bhb27's advanced standalone kernel (not his LOS stock kernel) in their ROM without his permission, so it made their ROM seem better than the other ROMs. It's the same kernel anyone can download and install themselves, but @bhb27 wants you to install that one yourself as it's more complex. He doesn't want it installed as a default kernel -- he doesn't include it in his own ROMs.
He's working on an Oreo-compatible kernel but while everything about Moto Nexus 6 is open source (thanks to Google), it's not the same with Moto Quark. Yeah, even LG Nexus 4 has Oreo, but again, it's totally open source so easier to adapt.

Replying the OP, theoretically what is needed is:
remove the checks from the zip regarding if the devices is Nexus 6, and after installing the ROM flash a compatible kernel, and the thing may boot like that.
But is a lost cause, the only thing similar with MAXX and Nexus 6 is the cpu/gpu and Motorola build it.
All the rest is not compatible, chipset, audio, video, wifi, radio, all the firmware, etc and etc is different, there is too many hardware diference for things to work.
And all of those are supported in a combination of ROM + kernel.
The source to build for Quark and for any AOSP device is not the same, yes is all on the same main Repo but the files used are not the same, that is way it device has it's own configuration/recipe and separated sources files inside the main Repo source.
The only reason way any AOSP device have updates easier is just like Chad wrote, they have all the sources files released, plus the AOSP source is made to be used with AOSP devices, so they need to make very little changes when google releases things to build a working ROM for they devices, plus there is literally hundreds of developers building for AOSP devices simply because is that simple anyone can build and help.
On the oppose to none AOSP devices were there is only a few developers as things are very hard because we don't have sometimes a clue in what to do, as we don't have the devices source, google changes the source on a way that only works with AOSP devices, so after a new OS is released a lot of things is need to be made from scratch.
If any one think is simple to build for any device just go for it, instead of be criticizing and posting none sense about thing you don't now how works.

about the video posted on my channel, I just made a joke at home. I know the limitations, I know the hardware is different. it was only a joke of those who do not have much knowledge, but search knowledge, the kernel used is a custom ROM 7.1.1, I did not say that the kernel is stock 7.1.1.
I admire the work of the developers, when I use a custom ROM, I can imagine how much work it has done to make it functional with few bugs. :good:
---------- Post added at 04:25 PM ---------- Previous post was at 04:21 PM ----------
bhb27 said:
Replying the OP, theoretically what is needed is:
remove the checks from the zip regarding if the devices is Nexus 6, and after installing the ROM flash a compatible kernel, and the thing may boot like that.
But is a lost cause, the only thing similar with MAXX and Nexus 6 is the cpu/gpu and Motorola build it.
All the rest is not compatible, chipset, audio, video, wifi, radio, all the firmware, etc and etc is different, there is too many hardware diference for things to work.
And all of those are supported in a combination of ROM + kernel.
The source to build for Quark and for any AOSP device is not the same, yes is all on the same main Repo but the files used are not the same, that is way it device has it's own configuration/recipe and separated sources files inside the main Repo source.
The only reason way any AOSP device have updates easier is just like Chad wrote, they have all the sources files released, plus the AOSP source is made to be used with AOSP devices, so they need to make very little changes when google releases things to build a working ROM for they devices, plus there is literally hundreds of developers building for AOSP devices simply because is that simple anyone can build and help.
On the oppose to none AOSP devices were there is only a few developers as things are very hard because we don't have sometimes a clue in what to do, as we don't have the devices source, google changes the source on a way that only works with AOSP devices, so after a new OS is released a lot of things is need to be made from scratch.
If any one think is simple to build for any device just go for it, instead of be criticizing and posting none sense about thing you don't now how works.
Click to expand...
Click to collapse
perfect explanation... I admire your work