...
GPL Stuff and Other Info:
https://github.com/VilleSensePortingTeam
Kernel and Maybe ramdisk will be there. ROM base will be uploaded there as well.
We could use SVN but I prefer git
Next post will be instructions on how to download that I'll complete when We have a booting ROM.
This thread is also where the FAQ, Download Instructions, and other general non development related info will be.
We'd like to keep the ROM Thread Clean and Focused on Development ONLY, and this thread for discussion.
Also Thanks List:
@LlabTooFeR for the base
@dd98 for the ROM Development
@javelinanddart for the Kernel Development @Zarboz for the kernel base @pirlano for the rom development
I personally WILL NOT help anyone who has not searched and thoroughly read the instructions because there will be a lot of them
There will also be no ETAs
Download Instructions: Coming Soon!
FAQ: Coming Soon!
Heres something that should help us with this rom
link
New MaximusHD for M7 is coming: https://twitter.com/LlabTooFeR/status/569807285960077312
Still no kernel sources on HTCdev...
kdd998 said:
New MaximusHD for M7 is coming: https://twitter.com/LlabTooFeR/status/569807285960077312
Still no kernel sources on HTCdev...
Click to expand...
Click to collapse
As far as I know the Ireland and UK lollipop ota is to be released on Wednesday
First kernel source archive for M7 and Android 5.0.1 is here: http://dl4.htc.com/RomCode/Source_and_Binaries/m7ul-3.4.10-g3c9a631.zip
Going to have a look at it this week-end... If anybody want a tester, I'm in
kdd998 said:
First kernel source archive for M7 and Android 5.0.1 is here: http://dl4.htc.com/RomCode/Source_and_Binaries/m7ul-3.4.10-g3c9a631.zip
Going to have a look at it this week-end... If anybody want a tester, I'm in
Click to expand...
Click to collapse
Thats strange. HTC has the source code listed for Android 5.0.1 yet the dev edition and the EU 7.19.401.2 update is based on Android 5.0.2
As I can see well, HTC put in access the kernel
I've been looking at the HTC kernel source for M7 and tried to build it for our ville. This, I managed: I got a kernel. I then tried to make a boot.img but I don't get from where to start. Which initrd should we base on?
I don't have time to work on this these days, but maybe in a week I'll have a few hours. I'm reading any pieces on advice on how I can help and which ways I can explore.
I intend to start from MaximuxHD 52.0.0 by @LlabTooFeR. Maybe we could try to start from the base he's working on instead...
Anybody else tried anything?
Take a look
http://forum.xda-developers.com/showthread.php?t=3050637
Sense 7 port for HTC One M7 is here
Inviato dal mio Nexus 7 con Tapatalk 2
Devs Please Port this to One XL (Snapdragon S4)
Devs Please port lollipop sense to One XL too
One s & XL have almost identical hardware
I'm really interested in this rom. Thank you!
I think we will never get a sense 7 port
@dd98
I got @Zarboz to help with a kernel
It's on the team github
Let's upload the MaximusHD M7 ROM and start this!
I'm compiling the kernel he gave us right now
We will use CM's Wifi Firmware and Drivers
The only thing he's concerned about is the display drivers not working
Also Ville is not my main phone anymore and I might have to give it up this summer, just fyi
I'm also undertaking porting a Linux 3.4 Kernel to the Samsung Galaxy S Blaze 4G as well as LP to it (with the 3.0 kernel atm)
@pirlano, I'll add you to the github Done
Also the kernel is not compiling atm
javelinanddart said:
@dd98
I got @Zarboz to help with a kernel
It's on the team github
Let's upload the MaximusHD M7 ROM and start this!
I'm compiling the kernel he gave us right now
We will use CM's Wifi Firmware and Drivers
The only thing he's concerned about is the display drivers not working
Also Ville is not my main phone anymore and I might have to give it up this summer, just fyi
I'm also undertaking porting a Linux 3.4 Kernel to the Samsung Galaxy S Blaze 4G as well as LP to it (with the 3.0 kernel atm)
@pirlano, I'll add you to the github Done
Also the kernel is not compiling atm
Click to expand...
Click to collapse
I think it's better to wait for T6 International LP rom
But I'll see what I can do with kernel, I was porting M7 LP kernel in private (Zarboz one is an M8 port?)
pirlano said:
I think it's better to wait for T6 International LP rom
But I'll see what I can do with kernel, I was porting M7 LP kernel in private (Zarboz one is an M8 port?)
Click to expand...
Click to collapse
OK, but why T6?
Zarboz said there's only so many device specific files: If we chose apq8064 in m8 source, and added m7 files, we could build m7 kernel
feel free to push your repo
javelinanddart said:
OK, but why T6?
Zarboz said there's only so many device specific files: If we chose apq8064 in m8 source, and added m7 files, we could build m7 kernel
feel free to push your repo
Click to expand...
Click to collapse
Because T6 international WiFi (firmware maybe not, but for example qualcomm chip hotspot framework and config yes), BT, FM Radio framework, config, app and binary files are perfect for Ville!
For example, BT and FM Radio in 4.4.2 Sense 6 were fixed with T6 files. Same for BT with "4.4.3 experimental" can be fixed with T6 BT files (FM can't be fixed because of a T6 lib that doesn't works with all others M7 libs).
javelinanddart said:
@dd98
I got @Zarboz to help with a kernel
It's on the team github
Let's upload the MaximusHD M7 ROM and start this!
I'm compiling the kernel he gave us right now
We will use CM's Wifi Firmware and Drivers
The only thing he's concerned about is the display drivers not working
Also Ville is not my main phone anymore and I might have to give it up this summer, just fyi
I'm also undertaking porting a Linux 3.4 Kernel to the Samsung Galaxy S Blaze 4G as well as LP to it (with the 3.0 kernel atm)
@pirlano, I'll add you to the github Done
Also the kernel is not compiling atm
Click to expand...
Click to collapse
Thats great, the more the better
Shona lá Fhéile Pádraig ?
Hey people!
I was trying to learn how to build AOSP ROMs for my E8, for which HTC has released the kernel source on the HTCDev website.
I feel kind of lost right now.. I have uploaded the kernel source for the device on to GitHub: [LINK] There are two archives within the source archive, where one says "platform" and the other is the kernel source.
Now, I'm syncing the AOSP source as they tell you to in the Sony Developer Portal (from HERE) to my Ubuntu VM (which is a huge download). What do I do next? Will this be enough to build the ROM or will I need other resources as well?
Sorry, I've never really done this before. So, I have some really noobish questions.
Thanks!
* BUMP *
Anyone? Please help!!
Hey,
i'm just curious about what the title describes. First of all.
What do i really need:
-kernel sources
-binary blobs (extractable)
-recovery / boot.img (extractable)
Let us just talk about the fairphone 2. Additional to the things mentioned we get the full source code of the OS (which i do not need?).
Where do the difficulties lie? For my understanding we just take the kernel sources, the official cyanogenmod (e.g.) source code, the binary blobs and the recovery / boot.img.
How difficult would it be to port Cyanogenmod to the fairphone 2.
Why is it difficult to port a device with existing (again cyanogenmod just as an example) cyanogenmod to a newer Cyanogenmod (Android) version?
I ask this to estimate/evaluate/judge (don't know the right term) the effort needed to do this. I think i'd be able to do that if i put enough work into it (i "speak" c and java), but i just need some answers.
Especially for example why it is more difficult to port Android 6 instead of Android 5 (which is the currently running Android version)
Thanks!
bigCrash
Has nobody an answer? Just one?
Im specifically interested in why it is more difficult to port e.g. cyanogenmod if there is only an older version of stock android and how important the kernel is? Why do we need kernel sources? Can't one just self-compile a kernel.
Where are the limits if i have a device running 4.2. Why can it possibly run 5.1 but not 6? Is the kernel limiting? Or only the effort to realize such a thing.
Thanks!
bigCrash
Hello there,
I am currently having a One Plus One. I have multi-rom utlity which allows me to have multiple android OS installed.
Currently the cyanogenmod based custom Marshmallow Rom I use (http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3242700) has switched over to using stable CM branch as their rom base. So this requires using Super SU for root access. Unfortunately Super Su is not compatible with Multirom implementation for OPO.
One suggestion provided was to try building the custom rom from source with user-debug flag. Meanwhile I came across two build.prop values (ro.build.type=userdebug ; persist.sys.root_access=1) which I hoped would enable inbuilt superuser without rebuilding the rom from source but they did not work.
So for now, there seems to be no other way around building from source ( I wanted to avoid this as much as possible because I have a very slow Internet access downloading 30 GB or so for the ROM alone will take a month for me).
So here are my 2 questions:
1> The rom developer in the thread mentioned in 2nd para, talks about 2 source (Kernel and the rest). When I looked at the manifest, they talk about replacing something. So does this mean I need to download the cyanogenmod sources as well or does repo sync take care of that automatically ?
2> I assume the kernel and rom need to be built separately. Can the "userdebug" mode be enabled only by rebuilding the kernel and then placing it with rest of the rom build zip provided by the developer to avoid rebuilding the whole rom ? or better yet flash the my userdebug kernel again after the normal rom installation ?
Thanks In Advance
crazydude10 said:
Hello there,
I am currently having a One Plus One. I have multi-rom utlity which allows me to have multiple android OS installed.
Currently the cyanogenmod based custom Marshmallow Rom I use (http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3242700) has switched over to using stable CM branch as their rom base. So this requires using Super SU for root access. Unfortunately Super Su is not compatible with Multirom implementation for OPO.
One suggestion provided was to try building the custom rom from source with user-debug flag. Meanwhile I came across two build.prop values (ro.build.type=userdebug ; persist.sys.root_access=1) which I hoped would enable inbuilt superuser without rebuilding the rom from source but they did not work.
So for now, there seems to be no other way around building from source ( I wanted to avoid this as much as possible because I have a very slow Internet access downloading 30 GB or so for the ROM alone will take a month for me).
So here are my 2 questions:
1> The rom developer in the thread mentioned in 2nd para, talks about 2 source (Kernel and the rest). When I looked at the manifest, they talk about replacing something. So does this mean I need to download the cyanogenmod sources as well or does repo sync take care of that automatically ?
2> I assume the kernel and rom need to be built separately. Can the "userdebug" mode be enabled only by rebuilding the kernel and then placing it with rest of the rom build zip provided by the developer to avoid rebuilding the whole rom ? or better yet flash the my userdebug kernel again after the normal rom installation ?
Thanks In Advance
Click to expand...
Click to collapse
Greetings,
Please read the Sticky threads for XDA Assist. This is not a help desk. XDA Assist is for helping new members or visitors navigate this site. You are a Senior Member and therefore you should know how to use the search feature and find the correct thread to ask your questions.
Thanks for understanding.
Thread closed.
Hi, I am currently building custom rom for my Lenovo a7000-a (aio_row) and I have a few questions regarding the device section of the AOSP build.
1. I have seen that to build the custom ROM for a device, I would need the following .mk files from topic "Android device configuration AOSP" in Stackoverflow.
However, from the device configuration/device-tree(?) from user rohantaneja in Github, I see that I would also need files that look like drivers for the devices based on the files on that github. May I ask how would I obtain these files?
2. Would flashing an arm64 generic build of custom AOSP into any Android device work or not? If so, why?
Seems like the amount of knowledge that I faced off with confused me a lot.
Any help is appreciated.
Thanks in advanced.