Okay so I'm currently downloading this 'Opensource_Update4.zip' file from Opensource, which I assume is the Official Kernel?
Just a few quick questions that I'd appreciate your help with guys:
1. Am I correct in what I just said above?
2. If so, do I just flash the file through ODIN?
3. Will this wipe my phone back to factory settings?
4. Will this affect my device being rooted?
Thanks in advance
New_World_Order said:
1. Am I correct in what I just said above?
Click to expand...
Click to collapse
No.
New_World_Order said:
2. If so, do I just flash the file through ODIN?
Click to expand...
Click to collapse
Again: no.
New_World_Order said:
3. Will this wipe my phone back to factory settings?
Click to expand...
Click to collapse
You will not be able to flash this, as it's not a flashable kernel, but SOURCE CODE.
So many wrong things in just one post
VAXXi said:
No.
Again: no.
You will not be able to flash this, as it's not a flashable kernel, but SOURCE CODE.
So many wrong things in just one post
Click to expand...
Click to collapse
Woaaaaaah I need a huge slap.
Would you be so kind as to explain please? :$
Sent from my GT-I9100 using XDA
Not really, as it's quite long
But the tl;dr version is: what Samsung published today is the source code (human readable code) for the ICS kernel. The ICS kernel is the "core" of the system, if you want. By compiling the source code, you obtain the machine code (specifically one zImage file) which runs on your device.
They are forced to publish the sources due to GPL requirements, but they're not very helpful in doing this. Inside the source code, there's still binary code (device drivers, etc) which cannot be published due to various agreements with the hardware manufacturers. Having this source code, even incomplete as it is, allows developers to see how the binary code is treated; this way, they can improve their code or even develop open-source replacements for the closed binary part of the kernel.
VAXXi said:
Not really, as it's quite long
But the tl;dr version is: what Samsung published today is the source code (human readable code) for the ICS kernel. The ICS kernel is the "core" of the system, if you want. By compiling the source code, you obtain the machine code (specifically one zImage file) which runs on your device.
They are forced to publish the sources due to GPL requirements, but they're not very helpful in doing this. Inside the source code, there's still binary code (device drivers, etc) which cannot be published due to various agreements with the hardware manufacturers. Having this source code, even incomplete as it is, allows developers to see how the binary code is treated; this way, they can improve their code or even develop open-source replacements for the closed binary part of the kernel.
Click to expand...
Click to collapse
Hahahaa okay thanks...
I think I'll just leave it alone! :')
Sent from my GT-I9100 using XDA
Please i need help.
After following a tutorial here on how to create a custom, i did every thing possible to create it and i got it running. I edited the build.prop and change the android level to 4.2.2 and flashed the rom into my phone, so i decided to install android version 4.0 and later apps and games only to find out i get "error parsing package" and thats my only problem.
What did i do wrong? am i missing something or what? please i need help on it.
Thanks in advanced.
Brainrex1 said:
Please i need help.
After following a tutorial here on how to create a custom, i did every thing possible to create it and i got it running. I edited the build.prop and change the android level to 4.2.2 and flashed the rom into my phone, so i decided to install android version 4.0 and later apps and games only to find out i get "error parsing package" and thats my only problem.
What did i do wrong? am i missing something or what? please i need help on it.
Thanks in advanced.
Click to expand...
Click to collapse
There are differences in package structure, minimum SDK version, API's and others factors that are preventing the package form being installed, just to clarify I assume you are trying to install Android 4.0+ apk's on an Android 2.3 or below device.
shimp208 said:
There are differences in package structure, minimum SDK version, API's and others factors that are preventing the package form being installed, just to clarify I assume you are trying to install Android 4.0+ apk's on an Android 2.3 or below device.
Click to expand...
Click to collapse
I know but i thought the rom i created was supposed to be on android 4.2.2 or do i need to edit the sdk version on the build.prop also?
please guys help me
Brainrex1 said:
I know but i thought the rom i created was supposed to be on android 4.2.2 or do i need to edit the sdk version on the build.prop also?
Click to expand...
Click to collapse
Did you compile the ROM form source or just port another ROM? Which version of Android did you use to compile with or as a base to port your ROM? Simply changing the build.prop information Android version doesn't change the version of Android your ROM is based on.
shimp208 said:
Did you compile the ROM form source or just port another ROM? Which version of Android did you use to compile with or as a base to port your ROM? Simply changing the build.prop information Android version doesn't change the version of Android your ROM is based on.
Click to expand...
Click to collapse
From source and its 2.3.6
Brainrex1 said:
From source and its 2.3.6
Click to expand...
Click to collapse
I apologize for the delay in responding if you compiled it form 2.3.6 source then that's what it will be based on you would have to compile it form 4.2.2 source if that's the version of Android you want your device to run on.
shimp208 said:
I apologize for the delay in responding if you compiled it form 2.3.6 source then that's what it will be based on you would have to compile it form 4.2.2 source if that's the version of Android you want your device to run on.
Click to expand...
Click to collapse
This is really hard than i expect, can u please throw more light about it?
Brainrex1 said:
This is really hard than i expect, can u please throw more light about it?
Click to expand...
Click to collapse
I'd be happy to what specifically do you want me to explain in more detail?
shimp208 said:
I'd be happy to what specifically do you want me to explain in more detail?
Click to expand...
Click to collapse
i would say everything concerning it or link me to the right thread.
Brainrex1 said:
i would say everything concerning it or link me to the right thread.
Click to expand...
Click to collapse
If you want to properly compile Android 4.2.2 I would recommend taking a look at this guide on compiling Jelly Bean from source. If there is something else you need me to explain please let me know.
Brainrex1 said:
i would say everything concerning it or link me to the right thread.
Click to expand...
Click to collapse
Your issue is that just changing the number in the build prop will not give android 4.2.2. This is something cheap knock devices due to fool people. You will have to compile a rom from source. If there is any for that device but as 2.3 was never officially released I'm betting you won't find any kernel source updated for the device.
shimp208 said:
If you want to properly compile Android 4.2.2 I would recommend taking a look at this guide on compiling Jelly Bean from source. If there is something else you need me to explain please let me know.
Click to expand...
Click to collapse
Thanks alot.
Seeing as this is now the official forum for Jide's Remix OS for PC, I feel this is a good point to ask some questions of the developers. Hopefully, they will take this forum seriously, and help us understand a little bit more of what the current state-of-affairs looks like. I have a few questions, and I am sure the community will have some in addition.
Question 1: What can we expect, as the testing community for Remix OS, to happen as far as your involvement with us?
Question 2: What can we expect, as the testing community, in terms of update frequency?
Question 3: What are the current plans for Remix OS for PC, short-term, intermediate, and stretch goals?
Question 4: Will you offer an official, less hackish way for us to root our installations?
Question 5: What can we expect in terms of your source code repositories for Remix OS, can we clone the repo and compile a working system?
Question 6: Can we expect uEFI support, and the ability to install permanently, in the near future?
I do hope that the devs will be involved enough to answer these questions, it would be a shame to see a beautiful piece of software released under open source licensing, and the users get left in the cold.
davenull said:
Seeing as this is now the official forum for Jide's Remix OS for PC, I feel this is a good point to ask some questions of the developers. Hopefully, they will take this forum seriously, and help us understand a little bit more of what the current state-of-affairs looks like. I have a few questions, and I am sure the community will have some in addition.
Question 1: What can we expect, as the testing community for Remix OS, to happen as far as your involvement with us?
Question 2: What can we expect, as the testing community, in terms of update frequency?
Question 3: What are the current plans for Remix OS for PC, short-term, intermediate, and stretch goals?
Question 4: Will you offer an official, less hackish way for us to root our installations?
Question 5: What can we expect in terms of your source code repositories for Remix OS, can we clone the repo and compile a working system?
Question 6: Can we expect uEFI support, and the ability to install permanently, in the near future?
I do hope that the devs will be involved enough to answer these questions, it would be a shame to see a beautiful piece of software released under open source licensing, and the users get left in the cold.
Click to expand...
Click to collapse
Honestly, I think that they should first cater to the needs of their backers, as their remix mini has still not been updated to a bug-free rom. If you ever go to remix central, they have a sort of a forum and all users keep complaining that they have forgotten about remix mini. I dont think that right now they should cater to the pc users, get one job done nicely(remix mini, namely) then go back to pc remix.
TheBasterd said:
Honestly, I think that they should first cater to the needs of their backers, as their remix mini has still not been updated to a bug-free rom. If you ever go to remix central, they have a sort of a forum and all users keep complaining that they have forgotten about remix mini. I dont think that right now they should cater to the pc users, get one job done nicely(remix mini, namely) then go back to pc remix.
Click to expand...
Click to collapse
That is part of the reasoning behind being curious of the level of involvement they expect to give us. They have a lot going on, it's not out of line to ask how much time *they* expect to be able to give us.
Question 6: UEFI is already supported, and we already can install it permanently.
Sent from my XT1095 using Tapatalk
davenull said:
That is part of the reasoning behind being curious of the level of involvement they expect to give us. They have a lot going on, it's not out of line to ask how much time *they* expect to be able to give us.
Click to expand...
Click to collapse
Truth be told, if you have ever used any rom from the android x86 project, the only difference in them is the launcher and multiwindow support. If you try the android x86 build, you will find out that they are almost identical in performance. So, that begs the question, what different work they did on the rom, apart from the launcher? What did they tweak? Honestly, I do not find any difference except the looks. So, what exactly are they burdening their minds with at the moment, considering the fact that remix is based totally on the kernel on the x86 android project. If you dont believe me, see the logcat yourself.
So, that means, what are they really wasting their time on? android x86 project supports Fat32, NTFS, ext2,ext3 and even ext4. On Fat2 and NTFS, you get around 2048 MB of space. On ext4, you get almost the full storage. Why does remix not support it is beyond me. Other thing is that newer releases are becoming more unstable than the previous release.
Look, dont get me wrong. Personally, I love remix os. It was the first reason I even took interest in the android on pc stuffs. Honestly, I knew about the android x86 project a long time back, but the multi window and other stuff of remix drew me in the most. So, the thing is, why are they not taking the best parts of the x86 project and imroving them further, rather than making it from scratch. Using that is already available and making it better is what is really needed. I think, with remix soon going open source( that is releasing it to the general public), maybe someone will get this idea and try to use it. Who knows.
TheBasterd said:
Truth be told, if you have ever used any rom from the android x86 project, the only difference in them is the launcher and multiwindow support. If you try the android x86 build, you will find out that they are almost identical in performance. So, that begs the question, what different work they did on the rom, apart from the launcher? What did they tweak? Honestly, I do not find any difference except the looks. So, what exactly are they burdening their minds with at the moment, considering the fact that remix is based totally on the kernel on the x86 android project. If you dont believe me, see the logcat yourself.
So, that means, what are they really wasting their time on? android x86 project supports Fat32, NTFS, ext2,ext3 and even ext4. On Fat2 and NTFS, you get around 2048 MB of space. On ext4, you get almost the full storage. Why does remix not support it is beyond me. Other thing is that newer releases are becoming more unstable than the previous release.
Look, dont get me wrong. Personally, I love remix os. It was the first reason I even took interest in the android on pc stuffs. Honestly, I knew about the android x86 project a long time back, but the multi window and other stuff of remix drew me in the most. So, the thing is, why are they not taking the best parts of the x86 project and imroving them further, rather than making it from scratch. Using that is already available and making it better is what is really needed. I think, with remix soon going open source( that is releasing it to the general public), maybe someone will get this idea and try to use it. Who knows.
Click to expand...
Click to collapse
You're completely wrong. First, "only the look and multiwindow" is a big and super complex difference. Resizing a window in an apk made for only one dpi isn't nothing easy. And yes, Remix OS supports EXT4, NTFS, and all other kind of partition you want. You just need to know how to do it.
Yes, it's based on Android-x86 project, and it has all the features you see there plus original and exclusive ones.
And let's be clear on this point: Remix OS is at Alpha state. Do you really understand what that means?
Sent from my XT1095 using Tapatalk
lucasdeeiroz said:
You're completely wrong. First, "only the look and multiwindow" is a big and super complex difference. Resizing a window in an apk made for only one dpi isn't nothing easy. And yes, Remix OS supports EXT4, NTFS, and all other kind of partition you want. You just need to know how to do it.
Yes, it's based on Android-x86 project, and it has all the features you see there plus original and exclusive ones.
And let's be clear on this point: Remix OS is at Alpha state. Do you really understand what that means?
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
You're completely wrong. First, "only the look and multiwindow" is a big and super complex difference. Resizing a window in an apk made for only one dpi isn't nothing easy. And yes, Remix OS supports EXT4, NTFS, and all other kind of partition you want. You just need to know how to do it
Click to expand...
Click to collapse
Multiwindow was never much of an issue. If you use xposed on the android x86 project rom 4.4 rc3, you can enable multiwindow using an exposed module. So, that goes out of the window.
Second, remix os does not support ext4 for storage officially. Android x86 project does out of the box.
Yes, it's based on Android-x86 project, and it has all the features you see there plus original and exclusive ones.
Click to expand...
Click to collapse
Exclusive? What feature is that? Look dont get me wrong, I love remix os, but what is the exclusive feature that I did not see. Please elaborate.
And let's be clear on this point: Remix OS is at Alpha state. Do you really understand what that means?
Click to expand...
Click to collapse
Derp! No idea. What is alpha, please do tell me. Dude, do you even know that the worst part of the coding was actually handled by the android x86 project. The kernel which was made by those guys is being used, even the the lesser known phoenix os uses it. So, as far as alpha is concerned, only making a launcher and adding it made it unstable to the point of calling it alpha is pretty ridiculous. You are very ignorant in this matter.
I love remix os as much as you do. Just, get your facts straight though.
---------- Post added at 06:01 AM ---------- Previous post was at 05:50 AM ----------
lucasdeeiroz said:
You're completely wrong. First, "only the look and multiwindow" is a big and super complex difference. Resizing a window in an apk made for only one dpi isn't nothing easy. And yes, Remix OS supports EXT4, NTFS, and all other kind of partition you want. You just need to know how to do it.
Yes, it's based on Android-x86 project, and it has all the features you see there plus original and exclusive ones.
And let's be clear on this point: Remix OS is at Alpha state. Do you really understand what that means?
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
And let's be clear on this point: Remix OS is at Alpha state. Do you really understand what that means?
Click to expand...
Click to collapse
To prove my point here I am posting some images to show what really a useful rom on pc should do. All of the screenshots are from my pc running android-x86-5.1-rc1 rom from the official android x86 website. This is what a real android image on pc should do.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, look at the amount of storage. I installed the rom on a 30gb hdd partition, and look at the amount of storage I got for apps, just out of the box, no extra tweaking need. Even better, it has root support. No more ads, no nothing. Pure android experience.
TheBasterd said:
Multiwindow was never much of an issue. If you use xposed on the android x86 project rom 4.4 rc3, you can enable multiwindow using an exposed module. So, that goes out of the window.
Click to expand...
Click to collapse
That stock "multiwindow" is ridiculous, it's nothing compared to what's shown in Remix OS. Stock: 1/2 or 1/4 screen windows. Remix: resizable and uncountless windows.
TheBasterd said:
Second, remix os does not support ext4 for storage officially. Android x86 project does out of the box.
Click to expand...
Click to collapse
Yes, it does support EXT4. If you enter the installation menu, EXT4 is an option. I used it myself.
TheBasterd said:
Exclusive? What feature is that? Look dont get me wrong, I love remix os, but what is the exclusive feature that I did not see. Please elaborate.
Click to expand...
Click to collapse
The mentioned true multiwindow/multitask (which is a lot different than stock one), the taskbar (which gives the OS a lot more PC feel), all the keys shortcuts, etc.
TheBasterd said:
Derp! No idea. What is alpha, please do tell me. Dude, do you even know that the worst part of the coding was actually handled by the android x86 project. The kernel which was made by those guys is being used, even the the lesser known phoenix os uses it. So, as far as alpha is concerned, only making a launcher and adding it made it unstable to the point of calling it alpha is pretty ridiculous. You are very ignorant in this matter.
Click to expand...
Click to collapse
The kernel is the same, and the system base is the same too. But no, it's not only the launcher the difference between the two OSs. Even the Android-x86 developers recognizes it and validate this "fork" (they even mention it on their official site). You think it's simple? Try to do it yourself.
TheBasterd said:
To prove my point here I am posting some images to show what really a useful rom on pc should do. All of the screenshots are from my pc running android-x86-5.1-rc1 rom from the official android x86 website. This is what a real android image on pc should do. Now, look at the amount of storage. I installed the rom on a 30gb hdd partition, and look at the amount of storage I got for apps, just out of the box, no extra tweaking need. Even better, it has root support. No more ads, no nothing. Pure android experience.
Click to expand...
Click to collapse
I have 30GB storage on Remix. Only using the installer. And I have root too, done it with simple "copy and paste".
lucasdeeiroz said:
That stock "multiwindow" is ridiculous, it's nothing compared to what's shown in Remix OS. Stock: 1/2 or 1/4 screen windows. Remix: resizable and uncountless windows.
Yes, it does support EXT4. If you enter the installation menu, EXT4 is an option. I used it myself.
The mentioned true multiwindow/multitask (which is a lot different than stock one), the taskbar (which gives the OS a lot more PC feel), all the keys shortcuts, etc.
The kernel is the same, and the system base is the same too. But no, it's not only the launcher the difference between the two OSs. Even the Android-x86 developers recognizes it and validate this "fork" (they even mention it on their official site). You think it's simple? Try to do it yourself.
I have 30GB storage on Remix. Only using the installer. And I have root too, done it with simple "copy and paste".
Click to expand...
Click to collapse
Yes! Now that is what I call a satisfactory answer/answers. Thanks bro! Shut up and take my upvote/thanks.
Now, would you kindly give me a procedure to do the same? I have tried all the method and it fails. I would prefer the grub2 method, if you must.
TheBasterd said:
Yes! Now that is what I call a satisfactory answer/answers. Thanks bro! Shut up and take my upvote/thanks.
Now, would you kindly give me a procedure to do the same? I have tried all the method and it fails. I would prefer the grub2 method, if you must.
Click to expand...
Click to collapse
You only have to boot into your USB with Remix OS image burned, press TAB when Resident Mod is selected, and add "INSTALL=1" to the end of line. There you go, the installer just like Android-x86.
Sent from my XT1095 using Tapatalk
lucasdeeiroz said:
You only have to boot into your USB with Remix OS image burned, press TAB when Resident Mod is selected, and add "INSTALL=1" to the end of line. There you go, the installer just like Android-x86.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
You mean, when it says "SRC=DATA=DATA_AS_IMG INSTALL=1". Like this?
Also, what about root access ? I need that too.
TheBasterd said:
You mean, when it says "SRC=DATA=DATA_AS_IMG INSTALL=1". Like this?
Also, what about root access ? I need that too.
Click to expand...
Click to collapse
Yes
Sent from my XT1095 using Tapatalk
lucasdeeiroz said:
Yes
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
You did not reply about the root access. How do I get that?
TheBasterd said:
You did not reply about the root access. How do I get that?
Click to expand...
Click to collapse
You only need to put an already rooted system.img in your USB installer (replace original one). The rooted system.img already comes with Play Store enabled. You can find it in the internet. I don't have the link now, tho
Sent from my XT1095 using Tapatalk
lucasdeeiroz said:
You only need to put an already rooted system.img in your USB installer. The rooted system.img already comes with Play Store enabled. You can find it in the internet. I don't have the link now, tho
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Cool. I got that. No problem.
Thanks for all the info. BTW, consider making a thread with all the info collected in it. Would help noobs like me a lot.
Regards
TheBasterd
Regarding the root method, how am I actually supposed to root the actual version of the OS if the system.img has been replaced with a so-called "system.sfs" file. Some people said I should just delete this one and add the .img file. If this works I'm more than okay with that (I really need root so I can share my windows partitions), but will I be able to install updates on the respective version of system.img afterwards? Thanks for reading.
And finally Our device, Redmi 3S (Land), with Treble ported... @TeamMex has brought in initial Treble support to Redmi 3S just like it was done on Redmi Note 4, using Cust as the Vendor partition... Hope He has great success in it...
Source: https://plus.google.com/u/0/+klozzjesus/posts/5REcrMxfq67
Let Us all hop into discussion and questions related to it here, rather than pollute other Development Threads...
Keep things polite and simple, varying opinions are all expected but lets not end up hurting anyone with Our Words... Be Responsible Guys...
Wow great news hope to see android p based roms without much problem in near future
amazing
Wow amazing
Wow ?
I need to ask something can anyone point me where are the drivers for soc lies i mean in a rom it is stored in /system/vendor folder but where does Qualcomm publishes its drivers for its different soc? Because project treble can only come to live if our land uses the project trebled compatible drivers from Qualcomm am i right? Please correct me of i am wrong and elaborate how these things goes
Ash225 said:
I need to ask something can anyone point me where are the drivers for soc lies i mean in a rom it is stored in /system/vendor folder but where does Qualcomm publishes its drivers for its different soc? Because project treble can only come to live if our land uses the project trebled compatible drivers from Qualcomm am i right? Please correct me of i am wrong and elaborate how these things goes
Click to expand...
Click to collapse
Can't get you
fxsheep said:
Can't get you
Click to expand...
Click to collapse
Look in windows we need to download drivers for windows 10, windows 7 etc etc and those are simple drivers which user can install right but in android there is vendor folder which contains all drivers for our soc camera ril etc. I want to know where does Qualcomm releases such drivers i mean in git or anywhere else. There must be a source from where mobile phone manufacturer get those vendor files and use it to build the rom for their devices Right? Take it in this way for buildings a custom rom we need source code which is available in git which devs can clone and compile to make a rom similarly where does we get these camera libs, soc, etc related files found?
Ash225 said:
Look in windows we need to download drivers for windows 10, windows 7 etc etc and those are simple drivers which user can install right but in android there is vendor folder which contains all drivers for our soc camera ril etc. I want to know where does Qualcomm releases such drivers i mean in git or anywhere else. There must be a source from where mobile phone manufacturer get those vendor files and use it to build the rom for their devices Right? Take it in this way for buildings a custom rom we need source code which is available in git which devs can clone and compile to make a rom similarly where does we get these camera libs, soc, etc related files found?
Click to expand...
Click to collapse
maybe you mean CAF(Code Aurora Forum)?
fxsheep said:
maybe you mean CAF(Code Aurora Forum)?
Click to expand...
Click to collapse
What is that and does it serves ?Okay can you tell me one thing does Qualcomm and other vendors who makes parts like soc, camera module etc for smartphone also makes drivers for the same or not? Or is the mobile phone company who makes all drivers for the components used in the phone? Intel makes processor and releases driver for the same does it gos well for manufacturer like Qualcomm?
Ash225 said:
What is that and does it serves ?Okay can you tell me one thing does Qualcomm and other vendors who makes parts like soc, camera module etc for smartphone also makes drivers for the same or not? Or is the mobile phone company who makes all drivers for the components used in the phone? Intel makes processor and releases driver for the same does it gos well for manufacturer like Qualcomm?
Click to expand...
Click to collapse
caf is the offical release of qualcomm's opensource
@TeamMex you are simply awesome dude
When we will also able to use project treble for land?
Any new about it where is @TeamMex gone?
abhishekpandey7148 said:
When we will also able to use project treble for land?
Any new about it where is @TeamMex gone?
Click to expand...
Click to collapse
Dont demand... You are not paying Him anything to ask Him like that... It will be done when He does it... Be patient...
abhishekpandey7148 said:
When we will also able to use project treble for land?
Any new about it where is @TeamMex gone?
Click to expand...
Click to collapse
Just wait for him to do the magic
abhishekpandey7148 said:
When we will also able to use project treble for land?
Any new about it where is @TeamMex gone?
Click to expand...
Click to collapse
I working in something's but I can release the old version xD presented in my screens
But have some message every boot and the camera take some time until the daemon is released
Sent from my Motorola Moto Z Play using XDA Labs
@TeamMex
Many thanks for your hard work.
Can you maybe release your software on github?
I want to used it for the Motorola G5s. Its almost the same device only I need not suc as vendor but OEM as vendor. But that can I fix if I have your code.
GoldeneyeS2 said:
@TeamMex
Many thanks for your hard work.
Can you maybe release your software on github?
I want to used it for the Motorola G5s. Its almost the same device only I need not suc as vendor but OEM as vendor. But that can I fix if I have your code.
Click to expand...
Click to collapse
Yeah I have it for Moto Z play too but u need to wait until my isp fix my internet issues , so for now I can't upload the source sorry
I hope it can be fixed in 3 days
Can somebody explain me what is treble for?
vandasche said:
Can somebody explain me what is treble for?
Click to expand...
Click to collapse
Just Google it... You can find a lot of really good explanations in it... I'll link a few in the OP very soon...