Related
anyone want to go through all the modules and try to figure out which rom they were pulled from
I don't really understand your question. Some modules have some tweaks adapted from various ROMs, but not all. If you have a more specific question, maybe someone can help you out. Otherwise there's this index.
GermainZ said:
I don't really understand your question. Some modules have some tweaks adapted from various ROMs, but not all. If you have a more specific question, maybe someone can help you out. Otherwise there's this index.
Click to expand...
Click to collapse
Example xprivacy Cyanogenmod
mikeyb1216 said:
Example xprivacy Cyanogenmod
Click to expand...
Click to collapse
What…?
So I'm using one of the kitkat roms and I can't seem to get USB OTG and USB charging to work at the same time? Is this just not possible? Or do I need to do something special? I bought one of the OTG Y cables that allows the hookup of a charger and a USB device and it's still no go, it'll show it's charging for a minute or so after a USB device is mounted but then the charging icon goes away?
Someone had mentioned to me that a custom kernel may be needed?
Yep you would need a custom kernel.
ThatFrigginAzn said:
Yep you would need a custom kernel.
Click to expand...
Click to collapse
Any documentation around on how to build this kernel to do what I need?
Hdale85 said:
Any documentation around on how to build this kernel to do what I need?
Click to expand...
Click to collapse
Look in my signature for a guide. For the specifics, you will need to find a kernel on github that has what you are looking for and port it to your build. My roll your own kernel guide will get you started. You will need a partition with Debian Linux to complete the guide. I suggest AntiX.
sleekmason said:
Look in my signature for a guide. For the specifics, you will need to find a kernel on github that has what you are looking for and port it to your build. My roll your own kernel guide will get you started. You will need a partition with Debian Linux to complete the guide. I suggest AntiX.
Click to expand...
Click to collapse
Can it be a kernel from another device? or does it need to be similar?
Also how about Ubuntu? I'm familiar with Ubuntu, but I'll look at AntiX
From what I gather I only need USB host mode so that the USB port is not outputting power.
Hdale85 said:
Can it be a kernel from another device? or does it need to be similar?
Also how about Ubuntu? I'm familiar with Ubuntu, but I'll look at AntiX
From what I gather I only need USB host mode so that the USB port is not outputting power.
Click to expand...
Click to collapse
Ubuntu should work, though the names of the dependencies might be off. Easier to just partition off and install Antix. Damn good distro. I went with stable for the guide, but you can easily switch later to testing or unstable by changing up the sources list.
For what you need, you may find it as an option when adjusting the menuconfig during the make process.
The second post in the thread tells a bit about changes necessary for the 500 device, as I originally made the guide for the 510.
There are currently two other kernels for the 500 that were successfully made using the guide. One of them also has a decent install through recovery script
sleekmason said:
Ubuntu should work, though the names of the dependencies might be off. Easier to just partition off and install Antix. Damn good distro. I went with stable for the guide, but you can easily switch later to testing or unstable by changing up the sources list.
For what you need, you may find it as an option when adjusting the menuconfig during the make process.
The second post in the thread tells a bit about changes necessary for the 500 device, as I originally made the guide for the 510.
There are currently two other kernels for the 500 that were successfully made using the guide. One of them also has a decent install through recovery script
Click to expand...
Click to collapse
What's the difference between the 500 and 510?
Hdale85 said:
What's the difference between the 500 and 510?
Click to expand...
Click to collapse
The 510 is the Google play edition, whereas the 500 is the lg version. If you didn't buy it through the play store, you have the 500.
The best way to learn would be to follow the guide all the way through, copy and paste, and then figure out what you are doing while you are doing it!
Also, this should be posted in the questions thread rather than development if a moderator would be so kind to move this post.
Oh ok the 510 is the google play edition. Either kernel should work right? They are the same device... I'm not running the stock rom as I wanted a basic 4.4 rom as this is eventually going in my car.
Well you posted right before me lol, but I made the post here because I know there are a couple other people looking for the same thing so I was hoping we could develop a kernel for everyone.
Hdale85 said:
Oh ok the 510 is the google play edition. Either kernel should work right? They are the same device... I'm not running the stock rom as I wanted a basic 4.4 rom as this is eventually going in my car.
Click to expand...
Click to collapse
Unfortunately no, there are some differences, mostly with naming, but that can be important.
There are two parts to the boot image for our device, the ramdisk, and the kernel itself. The ramdisk plays a key roll in deciding certain options for the device, while the kernel controls more common options you may find on any device.
Most of the install from recovery scripts, repack the kernel zimage with the existing ramdisk from the device. But this doesn't really matter either.
All of the multi device kernels tend to be larger than necessary and have problems they shouldn't.
Long story short is that each device has it's own kernel source, which has supposedly been optimized for its device. This isn't exactly true, and the list of changes I've made to better the 510 device's kernel is astounding.
If you follow my guide, all of this will become apparent.
Alright thanks I'll look over it.
So what makes the510 different?? Is the firmware different? Obviously they didn't change the hardware so could one somehow convert the 500 to a 510? Only reason I'm interested is because some of that stuff you said doesn't work on the 500 it seems? Such as fastboot?
Hdale85 said:
So what makes the510 different?? Is the firmware different? Obviously they didn't change the hardware so could one somehow convert the 500 to a 510? Only reason I'm interested is because some of that stuff you said doesn't work on the 500 it seems? Such as fastboot?
Click to expand...
Click to collapse
Lg specific drivers mostly. Fastboot requires an unlocked boot loader, which the V500 does not have. An exploit is used to bypass the boot loader on the 500. Loki.
The gpe is pure android, with just a couple of perks thrown in, as it uses an Lg platforms. Our device , that being the V510 most closely resembles the Nexus 4 (Mako) version, and was probably based off that device. The items I have added to the 510 kernel as enhancements, mostly came from a mako kernel with the rest simply being tweak corrections to the existing source code.
Those changes alone made huge improvements in performance and battery.
sleekmason said:
Lg specific drivers mostly. Fastboot requires an unlocked boot loader, which the V500 does not have. An exploit is used to bypass the boot loader on the 500. Loki.
The gpe is pure android, with just a couple of perks thrown in, as it uses an Lg platforms. Our device , that being the V510 most closely resembles the Nexus 4 (Mako) version, and was probably based off that device. The items I have added to the 510 kernel as enhancements, mostly came from a mako kernel with the rest simply being tweak corrections to the existing source code.
Those changes alone made huge improvements in performance and battery.
Click to expand...
Click to collapse
Yea I just found the long thread about converting, its strange they can't seem to get it to work? Quite strange... Well I'll have to research the other bits I guess from others that have made V500 kernels or something.
maybe this commit is what you need
https://github.com/oubeichen/android_kernel_lge_v500/commit/ee86db750adf2bb7b4f7b988ba6937d92551373b
I havent tested yet but this is ported from a nexus4 kernel thread. v500 and nexus4 have the same power management ic
Sent from my LG-V500 using XDA Premium 4 mobile app
oubeichen said:
maybe this commit is what you need
https://github.com/oubeichen/android_kernel_lge_v500/commit/ee86db750adf2bb7b4f7b988ba6937d92551373b
I havent tested yet but this is ported from a nexus4 kernel thread. v500 and nexus4 have the same power management ic
Sent from my LG-V500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If anybody wants this, I'll compile it into the V510. Looks pretty straightforward. Thank you for the link.
Hdale85 said:
Well you posted right before me lol, but I made the post here because I know there are a couple other people looking for the same thing so I was hoping we could develop a kernel for everyone.
Click to expand...
Click to collapse
Indeed! :fingers-crossed:
treetop777 said:
Indeed! :fingers-crossed:
Click to expand...
Click to collapse
I'm going to take a stab at a custom kernel, but I have to setup linux on my desktop again so I'm not sure when I'll get around to it lol. Might be able to this week sometime.
If I can't get USB Host mode with charging enabled I'm going to have to look into a wireless HD solution or something, and even then that won't fix the setup I wanted to use for high end sound.
news ????
I modified some frameworks of the Tablet to enable Advanced Power Menu...I posted it in General section of the forum but looks like it isn't visible there.
I also need a tester more things (a whole new rom!). @Aeyan Ashraf used to be my tester, but it looks like he isn't, anymore.
Anyone interested in testing can lead to here for more informations http://forum.xda-developers.com/galaxy-tab-3/general/mod-advanced-reboot-menu-tab-3-10-1-t2983139
If u need a tester for P5200 i could help u
xTear said:
If u need a tester for P5200 i could help u
Click to expand...
Click to collapse
Provide android.policy.jar; services.jar; framework-res.apk and twframework-res.apk from your current ROM please.
I will try to patch it, but it's not guaranteed. Cause both devices are a bit different.
Not to be a downer, but this is already easily accomplished by installing the xposed framework, and APM.
cmlusco said:
Not to be a downer, but this is already easily accomplished by installing the xposed framework, and APM.
Click to expand...
Click to collapse
Ikr, I used that module in AmatROM v1.0
Don't be mean!
Here, sorry I saw this post a little bit late.
cmlusco said:
Not to be a downer, but this is already easily accomplished by installing the xposed framework, and APM.
Click to expand...
Click to collapse
XPosed is cool, and great. However wouldn't it be great if the features we wanted were already part of a ROM and we didn't need to install addons just to customize how we want?
I install xposed. I see a module I like. Then I try to find how to hard code so I don't need xposed.
Thank you Nonta. I will try this when possible.
CAG-man said:
XPosed is cool, and great. However wouldn't it be great if the features we wanted were already part of a ROM and we didn't need to install addons just to customize how we want?
I install xposed. I see a module I like. Then I try to find how to hard code so I don't need xposed.
Thank you Nonta. I will try this when possible.
Click to expand...
Click to collapse
Thank you CAG-man
I had made a thread about creating a custom ROM for Android over here: http://forum.xda-developers.com/general/xda-assist/building-custom-android-rom-t3526514#post70277383 and Art Vanderlay suggested I post here, so here it is.
I own the BLU Energy X 2, and I am in need of the Device Tree and Vendor Blobs for the phone to create a custom ROM based off of CyanogenMod. My device currently has CyanogenMod on it, however it's an unofficial port for the BLU Studio Selfie. I am not sure how the dev of that ROM got these files, however the Infinix Hot 2 is a "clone" of that device, so he may have just ported it from there, or it may have not even needed porting at all Anyways, for me to create a custom ROM based off of CyanogenMod, I need the Device Tree and Vendor Blobs. I do have the ProjectConfig file if that helps.
These files are usually somewhere on GitHub, but due to the development community for BLU devices in general being almost non-existant, these files are nowhere to be found. So, how can I get these files for my device to start building a custom ROM? Thanks
If you need any other information, please reply.
Device Specs:
BLU Energy X 2
Model #: E050U
Android Version: 5.1 Lollipop
Kernel Version: 3.10.74+
Chipset: MT6580
Use Device and Vendor trees from similar devices, change names and other stuff like your device in the configs...
I'm noobie too, but this is how people make it for MTK devices
Audriuskins said:
Use Device and Vendor trees from similar devices, change names and other stuff like your device in the configs...
I'm noobie too, but this is how people make it for MTK devices
Click to expand...
Click to collapse
Ok, thanks, I'll look for some similar devices. Will any similar MTK device work? What needs to be similar? OS versions? Chipset? Kernel version?
What do I need to look for?
Thanks
NateDev473 said:
Ok, thanks, I'll look for some similar devices. Will any similar MTK device work? What needs to be similar? OS versions? Chipset? Kernel version?
What do I need to look for?
Thanks
Click to expand...
Click to collapse
Must be on the same chipset from my experience, Kernel and OS doesn't matter.
Audriuskins said:
Must be on the same chipset from my experience, Kernel and OS doesn't matter.
Click to expand...
Click to collapse
So all I need to do is find a device with similar specs, and same chipset that has device tree and vendor blobs already created? And then I just modify it to fit my specific device?
NateDev473 said:
So all I need to do is find a device with similar specs, and same chipset that has device tree and vendor blobs already created? And then I just modify it to fit my specific device?
Click to expand...
Click to collapse
Something like that, you should look up :
http://forum.xda-developers.com/showthread.php?t=2274332
Audriuskins said:
Something like that, you should look up :
http://forum.xda-developers.com/showthread.php?t=2274332
Click to expand...
Click to collapse
Do the devices need to be officially CM supported, to get the device tree and vendor blobs? Because I found a couple of devices like the ZenFone Go that has an unofficial version of CM, but I can't find the device tree for that device.
These come from the oem. While the directions posted sometimes work it is dirty hacking at best and never stable. This is why developers stay away from mtk devices and they are really only used in cheap devices.
NateDev473 said:
Do the devices need to be officially CM supported, to get the device tree and vendor blobs? Because I found a couple of devices like the ZenFone Go that has an unofficial version of CM, but I can't find the device tree for that device.
Click to expand...
Click to collapse
Search on Github
Audriuskins said:
Search on Github
Click to expand...
Click to collapse
Ok, so I've discovered that the Infinix Hot 2 has mostly the same specs as my device, and that it's basically a clone of the Studio Selfie, which is the device that I used to unofficially port CyanogenMod to my device, so that's a good sign. Anyways, CyanogenMod was built for the Infinix Hot 2 from source, and they provided links to GitHub. It does say though that the Infinix Hot 2 is Android One. Is that a big problem?
Thanks
NateDev473 said:
Ok, so I've discovered that the Infinix Hot 2 has mostly the same specs as my device, and that it's basically a clone of the Studio Selfie, which is the device that I used to unofficially port CyanogenMod to my device, so that's a good sign. Anyways, CyanogenMod was built for the Infinix Hot 2 from source, and they provided links to GitHub. It does say though that the Infinix Hot 2 is Android One. Is that a big problem?
Thanks
Click to expand...
Click to collapse
No idea x)
I guess you can try xd
Audriuskins said:
No idea x)
I guess you can try xd
Click to expand...
Click to collapse
Ok, thanks
Audriuskins said:
No idea x)
I guess you can try xd
Click to expand...
Click to collapse
I found this on GitHub, is that what I am looking for in terms of the vendor files and stuff like that? http://imgur.com/a/KUcxC
NateDev473 said:
I found this on GitHub, is that what I am looking for in terms of the vendor files and stuff like that? http://imgur.com/a/KUcxC
Click to expand...
Click to collapse
Clone whole tree, rename everything to yours.
In device tree check if configs are like your device
Audriuskins said:
Clone whole tree, rename everything to yours.
In device tree check if configs are like your device
Click to expand...
Click to collapse
Ok, I will. If some of the configs are different for my device, I can just replace the values with the ones that work for my device right? Also in that other device's lib volder, they have a lot less stuff then my stock ROM lib folder, is that fine?
NateDev473 said:
Ok, I will. If some of the configs are different for my device, I can just replace the values with the ones that work for my device right? Also in that other device's lib volder, they have a lot less stuff then my stock ROM lib folder, is that fine?
Click to expand...
Click to collapse
I can't help you very much, because I'm new in MTK development ://
Audriuskins said:
I can't help you very much, because I'm new in MTK development ://
Click to expand...
Click to collapse
Would it be possible to then just upload my own files? Because on my phone I have all those files that are there for the other device. That would be better, I think, because they would be specific to my phone... If you don't know it's fine
NateDev473 said:
Would it be possible to then just upload my own files? Because on my phone I have all those files that are there for the other device. That would be better, I think, because they would be specific to my phone... If you don't know it's fine
Click to expand...
Click to collapse
I dont know
Note To Developers :
I have tried to install so many treble roms in my Galaxy J6 Infinity and always failed to install. Can any developer please provide us a full guide on how to install treble roms in samsung exynos devices using TWRP or anything else. Please help us.
I tried to install the following roms
1. OmniP-arm64_aonly_vanilla_nosu
2. PixelExperienceP-arm-aonly
3. dotOS-O-v2.4-santoni-OFFICIAL-20180723
All the above roms are treble roms and I failed to install.
My device also supports Project Treble.
Please Help:crying::crying::crying:
Nitin devarapalli said:
Note To Developers :
I have tried to install so many treble roms in my Galaxy J6 Infinity and always failed to install. Can any developer please provide us a full guide on how to install treble roms in samsung exynos devices using TWRP or anything else. Please help us.
I tried to install the following roms
1. OmniP-arm64_aonly_vanilla_nosu
2. PixelExperienceP-arm-aonly
3. dotOS-O-v2.4-santoni-OFFICIAL-20180723
All the above roms are treble roms and I failed to install.
My device also supports Project Treble.
Please Help:crying::crying::crying:
Click to expand...
Click to collapse
Which twrp? and give forum link for your device....
In 3rd option santoni is a Xiaomi mobile i think....
I also have samsung galaxy j6 2018 and have project treble support so tried flashing
PixelExperienceP-arm-aonly gsi system image but failed. I flashed through twrp given in following thread
https://forum.xda-developers.com/galaxy-j/development/recovery-twrp-3-2-2-0-galaxy-j6-on6-t3819751
Any help ?
Is there even some way to install treble roms on tje j6? I could really need a different rom
Nitin devarapalli said:
Note To Developers :
I have tried to install so many treble roms in my Galaxy J6 Infinity and always failed to install. Can any developer please provide us a full guide on how to install treble roms in samsung exynos devices using TWRP or anything else. Please help us.
I tried to install the following roms
1. OmniP-arm64_aonly_vanilla_nosu
2. PixelExperienceP-arm-aonly
3. dotOS-O-v2.4-santoni-OFFICIAL-20180723
All the above roms are treble roms and I failed to install.
My device also supports Project Treble.
Please Help:crying::crying::crying:
Click to expand...
Click to collapse
Dude, there IS a tutorial on how to flash treble GSIs! You're just not willing to use a simple thing like GOOGLE!
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
Now, from what I read here is that a perquisite is that you don't have a patched boot/ramdisk aka a rooted phone.
If you have a rooted phone, you're going to have to install a fresh, unmodified kernel (boot.img) and then try it
I'll give it a try and try to post back results. I'm not familiar with how project treble works, but I doubt it's as easy as it sounds
@ShaDisNX255 plz share the result. I too have a Galaxy J6 and wanted to have an AOSP based rom in it. If u succeed, plz post it here. Not a big fan of Touchwiz.
hmm i failed myself, tried system-180818-arm-aonly-gapps.img without succes.
1. i've installed TWRP https://forum.xda-developers.com/galaxy-j/development/recovery-twrp-3-2-2-0-galaxy-j6-on6-t3819751
2. install Resurrection Remix ARM A Only Devices (system-180818-arm-aonly-gapps.img)
3. on system image
4. reboot
result endless reboot
Samsung probably went out of their way to make it harder.
Too busy to experiment myself but from my first tests I didn't get it to work.
Oh well, so much for "Project treble making it easier"
lol
ShaDisNX255 said:
Samsung probably went out of tbeir way to make it harder.
Too busy to experiment myself but from my first tests I didn't get it to work.
Oh well, so much for "Prohect treble making it easier"
lol
Click to expand...
Click to collapse
Trust me when i say this but i really want u to succeed. Touchwiz is too damn heavily bloated to use. Really hope u make it work!
adityam0338 said:
Trust me when i say this but i really want u to succeed. Touchwiz is too damn heavily bloated to use. Really hope u make it work!
Click to expand...
Click to collapse
It's fairly easy to debloat using something like Super R's kitchen.
Why would you buy a J6 if you hate Touchwiz?
There are waaaaay better options that have closer to stock Android experiences than a Samsung phone
ShaDisNX255 said:
It's fairly easy to debloat using something like Super R's kitchen.
Why would you buy a J6 if you hate Touchwiz?
There are waaaaay better options that have closer to stock Android experiences than a Samsung phone
Click to expand...
Click to collapse
Lol that's the issue. Got the phone from my parents. Never would've bought this myself. I like AOSP based roms. Yeah i know its easy to debloat but i just count it as a con of toucwiz(weird as it may be). So here i'm scratching my head and looking all round the internet to find a possible way to turn this to my liking. 4pda also gave negative results, so replying to some recently created threads seemed like my last resort. Btw have u found a working GCAM port for this phone. Tried 6-7 ports but none of them even got installed.
adityam0338 said:
Lol that's the issue. Got the phone from my parents. Never would've bought this myself. I like AOSP based roms. Yeah i know its easy to debloat but i just count it as a con of toucwiz(weird as it may be). So here i'm scratching my head and looking all round the internet to find a possible way to turn this to my liking. 4pda also gave negative results, so replying to some recently created threads seemed like my last resort. Btw have u found a working GCAM port for this phone. Tried 6-7 ports but none of them even got installed.
Click to expand...
Click to collapse
Nope, I'm not much of a picture taker.
Lol a lot of people get phones from their parents, just be glad you're not stuck with a phone with a ****ty processor like Mediatek.
And well, I'm not an experienced person, so I wouldn't even be able to port something like Lineage or the like, sorry
ShaDisNX255 said:
Nope, I'm not much of a picture taker.
Lol a lot of people get phones from their parents, just be glad you're not stuck with a phone with a ****ty processor like Mediatek.
And well, I'm not an experienced person, so I wouldn't even be able to port something like Lineage or the like, sorry
Click to expand...
Click to collapse
Yeah, I'm grateful to them. And i don't expect u to port a rom. Nonetheless im grateful to u for trying treble. Just hope u get positive results. Cheers! ?
adityam0338 said:
Yeah, I'm grateful to them. And i don't expect u to port a rom. Nonetheless im grateful to u for trying treble. Just hope u get positive results. Cheers! ?
Click to expand...
Click to collapse
Hopefully somebody figures it out
ShaDisNX255 said:
Hopefully somebody figures it out
Click to expand...
Click to collapse
Yep, hope somebody does. ??
I failed again, had to stop,out of options. This phone is my only device atm. Kicked back to original stock rom.
KRiST0F said:
I failed again, had to stop,out of options. This phone is my only device atm. Kicked back to original stock rom.
Click to expand...
Click to collapse
I think the problem is with TWRP cause i read in some other threads that u need some vendor partition enabled( or sthng like this) TWRP to flash Pie GSIs. Not sure if im right or wrong. But this is the first thing that comes to mind.
adityam0338 said:
I think the problem is with TWRP cause i read in some other threads that u need some vendor partition enabled( or sthng like this) TWRP to flash Pie GSIs. Not sure if im right or wrong. But this is the first thing that comes to mind.
Click to expand...
Click to collapse
that was also something i thought of, because in some procedures they speak of a trebel recovery mode
TWRP on the J6 DOES support the vendor partition, so I don't understand what you're trying to say
ShaDisNX255 said:
TWRP on the J6 DOES support the vendor partition, so I don't understand what you're trying to say
Click to expand...
Click to collapse
Ok. I didn't know that. Thnx for the info. Then what is going wrong with the treble GSIs??