INTRODUCTION
Have you ever dreamed to get not any device but YOURS on the wide screen of your computer? Create a custom ROM and emulate it, or just check another custom ROM compatibility virtually without having to flash and risk your everyday tool? Well I did and I still do!
In the old times this was possible but, unfortunately, it's no longer the case. Since our beloved mobile devices got more features, system has become also more complex. This is why we can't run a custom ROM only with system and data images as before anymore. Unless you still want to develop on Gingerbread and below — seriously? — we need to move to another solution.
And this is what this project is for!
According to the fact that we're not all pro developers and / or we're not all rich enough to buy multiple devices in case of brick, I think such project is necessary to avoid taking stupid risks like we do now.
ORGANIZATION
Currently the project is committed under the name of "AndROMega".
It is planned to work under the Windows and Linux environments. An eventual port for Mac OS isn't envisaged for now but still welcome if someone wish to work on once a version is released.
By the way, this project being free and open-source, everybody can join, improve it but thieving (including copying then claiming project as-is / unmodified is your and, worse, selling this common work) is absolutely UNALLOWED. This must still free, open-source and mention the original authors (me and other devs eventually joining) in case of copying to make custom release. All of this juridical stuff will be put in a license file as usual anyway.
The QEMU emulating software will be used to facilitate the cross-platforming of the project software. It is fast, powerful, reliable, and, moreover: FREE.
Edit: Great new! Editing a custom Android emulator from scratch won't be in the question anymore!
A Github repo has been created allowing to run a stock AOSP Android ROM, so one step is made
Link to this repo: https://github.com/aosp-mirror/platform_external_qemu
Other notes coming soon in this thread...
Reserved.
Atronid said:
INTRODUCTION
Have you ever dreamed to get not any device but YOUR on the wide screen of your computer? Create custom ROM and emulate it or just check another custom ROM compatibility virtually without having to flash and risk your everyday tool? Well I did and I still do!
In the old times this was possible but, unfortunately, it's no longer the case. Since our beloved mobile devices got more features, system became also more complex. This is why we can't run a custom ROM only with system and data images as before anymore. Unless you still want to develop on Gingerbread and below — seriously? — we need to move to another solution.
And this is what this project is for!
According to the fact that we're not all pro developers and / or we're not all rich enough to buy multiple devices in case of brick, I think such project is necessary to avoid taking stupid risks as we do for now.
ORGANIZATION
Currently the project is committed under the name of "AndROMega".
It is planned to work under the Windows and Linux environment. An eventual port for Mac OS isn't envisaged for now but still welcome if somebody wish to work on once a version is released.
By the way, this project being free and open-source, everybody can join, improve it but thieving (including copying then claiming project as-is / unmodified is your and, worse, selling this common work) is absolutely UNALLOWED. This must still free, open-source and mention the original authors (me and other devs eventually joining) in case of copying to make custom release. All of this juridical stuff will be put in a license file as usual anyway.
The QEMU emulating software will be used to facilitate the cross-platforming of the project software. It is fast, powerful, reliable, and, moreover: FREE.
Edit: Great new! Editing a custom Android emulator from scratch won't be in the question anymore!
A Github repo has been created allowing to run a stock AOSP Android ROM, so one step is made
Link to this repo: https://github.com/aosp-mirror/platform_external_qemu
Other notes coming soon in this thread...
Click to expand...
Click to collapse
So what do you mean by custom rom environment builder? Do you mean when you port a rom and it has glitches and the environment fixes it or what? I'd be happy to help with this.
NonStickAtom785 said:
So what do you mean by custom rom environment builder? Do you mean when you port a rom and it has glitches and the environment fixes it or what? I'd be happy to help with this.
Click to expand...
Click to collapse
I don't really understand your question, but I'll sum up what the project is, hoping it will help you understand.
It's nothing more or less than a tool that mimic hardware and specific components and architecture of a phone model. It is supposed to be more than an AVD, allowing you to literally flash a custom ROM and debug it virtually instead of having to buy the phone, flash it, screw everything if something goes wrong, restore backup, etc.
Back when I got this idea (before it got forgotten among the million projects I have) I thought the hardest part was to get the core component of every phone (ramdisk, ROM, bootloader — assuming it's possible, otherwise "create" a replicant) and get the hardware spec mimicked with QEMU. Now I grew a bit and got a new-featured phone (seamless partition system that was pretty new to me), I know it will be even more complicated.
Since I'm not really available this year because of my exams, this project will still idle for a while. But I won't abandon it, so if the principle interest you and you're ready to give a hand you are welcome !
I'm In!
Atronid said:
I don't really understand your question, but I'll sum up what the project is, hoping it will help you understand.
It's nothing more or less than a tool that mimic hardware and specific components and architecture of a phone model. It is supposed to be more than an AVD, allowing you to literally flash a custom ROM and debug it virtually instead of having to buy the phone, flash it, screw everything if something goes wrong, restore backup, etc.
Back when I got this idea (before it got forgotten among the million projects I have) I thought the hardest part was to get the core component of every phone (ramdisk, ROM, bootloader — assuming it's possible, otherwise "create" a replicant) and get the hardware spec mimicked with QEMU. Now I grew a bit and got a new-featured phone (seamless partition system that was pretty new to me), I know it will be even more complicated.
Since I'm not really available this year because of my exams, this project will still idle for a while. But I won't abandon it, so if the principle interest you and you're ready to give a hand you are welcome !
Click to expand...
Click to collapse
Well this is a very interesting idea. It would be very useful for the rooted phones that don't have any custom roms already built.
Maybe you wouldn't have to get the core components of every phone all at once. Maybe it you could make the program to extract a twrp or cwm backup, and have a database of all the ramdisks and chipsets that the program will have access to.
I think this project is very useful and I would like to start in the development of it or aid you in it. PM me with more details :good:.
NonStickAtom785 said:
Well this is a very interesting idea. It would be very useful for the rooted phones that don't have any custom roms already built.
Maybe you wouldn't have to get the core components of every phone all at once. Maybe it you could make the program to extract a twrp or cwm backup, and have a database of all the ramdisks and chipsets that the program will have access to.
I think this project is very useful and I would like to start in the development of it or aid you in it. PM me with more details :good:.
Click to expand...
Click to collapse
Yes, backup extraction and component database was the original idea
Thank you for your help! I'll PM you as soon as the project starts :fingers-crossed:
Atronid said:
Yes, backup extraction and component database was the original idea
Thank you for your help! I'll PM you as soon as the project starts :fingers-crossed:
Click to expand...
Click to collapse
Thanks:laugh:
Best thing ever, life saver etc, I am ready to do whatever you want just this thing to succeed!
ender1324 said:
Best thing ever, life saver etc, I am ready to do whatever you want just this thing to succeed!
Click to expand...
Click to collapse
That's very nice, thanks!
As mentionned earlier, the project won't start right now due to my work, but in theory I should be available and ready to start it in the next months! I'll DM you as soon as it gets its first kick !
Related
ubuntu can be designed from the scratch for any arm based device .
this is just a humble request to senior devs to check it out and try to port it on our wave.
even if modem would not work for arm ubuntu it would be useful in other aspects like usb hosting, full pc based firefox experience,full doc editing,and something new that our wave would have.
htc-linux.org/wiki/index.php?title=Ubuntu/Leo
https://wiki.ubuntu.com/ARM/RootStock/RunNative
https://wiki.ubuntu.com/ARM/RootfsFromScratch
even android porting is on half stage. I think dev's are gonna handle the android thing. Maybe they will after android but Android has priority
furkey said:
even android porting is on half stage. I think dev's are gonna handle the android thing. Maybe they will after android but Android has priority
Click to expand...
Click to collapse
Well, a working Ubuntu port can be easier than the Android, as one don't have to pay attention to the modem (however determining the battery level still would be a problem...). But I run some rounds with the current kernel to make console available and all my atepts failed, I was not able to get it work... What would you do without console?
anghelyi said:
Well, a working Ubuntu port can be easier than the Android, as one don't have to pay attention to the modem (however determining the battery level still would be a problem...). But I run some rounds with the current kernel to make console available and all my atepts failed, I was not able to get it work... What would you do without console?
Click to expand...
Click to collapse
may be this may help you
https://wiki.ubuntu.com/ARM
https://wiki.ubuntu.com/ARM/n900
Hmmm i think all guys are busy in porting android and making voluntas browser etc also they have their own life so let them work on other things first.
Also did u tried ubuntu through badadroid ?? Did it worked.??
Just for the fun
http://translate.google.com/transla...ation-de-le-tama-the-king-of-the-rom/&act=url
Nice
Anybody knows why google translates "firmware" to "shower"?
Nice, now we know a bit more of the guru
God, Google translation is awful
Here is my approximate translation of cajl interview:
1) Le Tama, master of archos roms, present yourself
I fall into computers when I was very young (11 year old, no personal computer at this time, I start programming on paper with a book ) and since then virus never left me. I'm 42, I'm technical director of a small software development company. As my current job don't give me much occasion to dig into code, I'm pursuing my passion as a leisure, and especially on Archos tablet these days.
2) Why Android ?
I came to Android with my HTC HD2. At that time, Android just started to show some great potential and Windows Mobile was getting old. I started to follow HD2 development efforts on Android. It was stuck on a kernel problem, it pushed me to start looking into linux kernel source code. I then took part of the desire kernel port to HD2 with Cotulla and the others and I also participated to the first Android release working on HD2.
3) Why Archos
I started looking at Archos when Google annonced ICS and annonced that they will be using Omap as reference platform. I always wanted to have a look at omap (too much qualcomm with hd2 ), so I started to look for a platform that would let me play with it without being too costly. That's why I naturally came to Archos. I started toying with my co-worker A70 and then purchased my A101G9.
The more I work on Archos, the more I like the "openness" of the platform. Gen8 bootloader is easy to crack, gen9 bootloaders are not even locked. Better, Archos thinks about us, hackers, by letting entry points like SDE, a reserved partition on gen9,...
4) By the way, what's the purpose of rooting ?
Ah! What's the purpose of root:
From a developer point of view, to give complete access to resources. With root, we can do a complete dump of disk and partitions to study firmware, install things we couldn't do without, like SDE for Gen9. It's the first necessary step to modify stock firmware. It's also mandatory if you want to do some specific operations like partitioning.
From an user point of view, it let you use application that demands root. My favorites are:
- Busybox
- Root Explorer
- Titanium backup
- Chainfire 3D
And I certainly forgot some. Just looking at market, we see thousands of applications that requires root to work.
5) Easy or not easy to find exploits ?
No, not easy with a well-made firmware. Except big mistake from manufacturer, exploits (weakness abused to obtain a temporary root) are fixed after discovery, and it's getting more and more difficult to find new weaknesses. Thankfully, our current exploit is not fixed, crossing finger.
6) What are you currently working on ?
I'm working a bit on too many fronts and not enough free time, but here is what I'm working on:
- Internal disk partitioning for g9 to let us install sde firmware on a separated native ext4 partition, without interfering with stock firmware and internal storage. It works on mine, I'm working on way to do it simply and safely to let everyone benefit from it.
- Clockworkmod Recovery. It also works on mine, but is only useful if tablet has been partitioned. It let us do complete backups, rom+apps+internal storage (nandroid backup), it let us use zips to install firmware and firmware updates, and it make our tablet feels more "android native".
- CM9: I built one for gen9 that worked not too badly, but there is a lot of work to get something completely functional.
- I also launched a first overclocked kernel for 1.0Ghz Gen9, stable on mine up to 1.2, almost at 1.3. I will have to work on this again when Archos will release a new firmware that fix current ICS problems.
- I'm working on the IT2, I activated SDE and I have a rooted firmware. I will try to port 3.0 kernel and ICS on it.
- I'd like to work on bootloader too, but this is another story...
7 How can we help ?
Explain my boss that I have to stop working on his projects! More seriously, I'll certainly need beta-testers that are willing to take risks for their tablets with partitioning, but I'm not there yet.
8 Why this nickname ?
Le Tama ? This is a wink to my wife! Sshhh!
9 Anything more ?
Nah, enough talk, back to work!
letama said:
God, Google translation is awful
Click to expand...
Click to collapse
Naaaah, it's pretty funny (I had no idea that Gen9 has a shower onboard)
letama said:
7 How can we help ?
Explain my boss that I have to stop working on his projects! More seriously, I'll certainly need beta-testers that are willing to take risks for their tablets with partitioning, but I'm not there yet.
Click to expand...
Click to collapse
Count me in
letama said:
- Clockworkmod Recovery. It also works on mine, but is only useful if tablet has been partitioned. It let us do complete backups, rom+apps+internal storage (nandroid backup), it let us use zips to install firmware and firmware updates, and it make our tablet feels more "android native".
Click to expand...
Click to collapse
Oh my god! This is by far that feature that I am missing most on my G9. I hope this dream comes true one day.
letama is great!!!
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
anyone? I am quite serious about wanting to do and go into this but I have yet one thread that anyone's ever replied to.. (or post iirc) which puts a damper on me
Snake X said:
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
Click to expand...
Click to collapse
From my limited knowledge, I think it is a huge task undertaking, you can download Android source code from Google, the hard part will be the device driver development and porting for Linux kernel (and maybe portion of Android). If you are lucky, you can use the existing phone bootloader (or you have to port one). Understanding the inner of the phone (different chip set may need different device driver) will be another challenging task.
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Snake X said:
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Click to expand...
Click to collapse
To answer you question no the drivers and lib files are different for aosp based rooms then they are for the stock OEM from. The first step will be to get a working kernel. Without anything you do will be pointless
I'm somewhat interested in the same thing, and from what I've gathered, you'll need to do these things to begin ROM development:
1. Read every page on the AOSP site and grab a copy of the AOSP source. It probably wouldn't hurt to read the regular Android developer wiki as well.
2. Learn about Linux driver development:
http://lwn.net/Kernel/LDD3/ (this is apparently considered THE BOOK on Linux driver development)
http://www.freesoftwaremagazine.com/articles/drivers_linux
3. Learn pretty much every detail about your phone and its hardware, especially when it comes to how ROMs are installed on it. For example, my phone (the Droid X2) has a locked bootloader, so 2nd init has to be used to boot new ROMs, and this makes it so that we cannot update the kernel.
You can usually find this sort of information on your phone manufacturer's website. Sometimes they even post the source code to their phone's drivers, which is helpful.
4. Look at other ROMs (preferably for your phone) and see how they work. The source code is freely available for most popular ROMs.
For example: CyanogenMod keeps their source code in a public git repository: https://github.com/cyanogenmod
5. Get to work on porting!
I would highly recommend starting with something smaller, however, just as a start. One good jumping-off point is probably this guide: http://forum.xda-developers.com/showthread.php?t=1272270
If any part of this was wrong, or if I left something out, somebody feel free to correct me, I'm still a noob.
Thank you so much for your direction, however,, android kitchen.. im not sure about that because isnt that only ment for htc devices? My phone is made by zte
what device do you even have?
if it's stuck officialy on 2.1 or 2.2 there's no hope that if you even port it that it'll work
its the zte warp from boost mobile (prepaid). Btw if I compile an aosp ics launcher and put that on my phone whats the chances of that working?
edit: it uses 2.3.5
Well Sebastian responded on android forums, apparently zte is very bad at version control with their kernel sources. So when they complete one project, they use the same source for the next project, and what they release could be for anything. Apparently the blade source had the same issues, it took him a while to get them to correct the source
Sent from my N860 using Tapatalk
Yeah I noticed that there were ppl saying there were things similar but I'm not sure what will work or what won't.. guess its time to start a petition on zte to release the source code lol
edit: seems like zte's bein a bad company and violated the GNU GPL license for not providing a complete source code.. I compiled an email and sent it to someone who can proof read it and send it to the right person for this kinda thing.. danggit zte
Hi all,
i want to start with AOSP 4.2 for our SGS3 i9300 - is anybody interested to develop and publish a AOSP based rom with me?
I'm a real application developer (C,C++,JAVA,PHP,MySQL,some Oracle PLSQL) and now its some cold out - i have time to do
some nice things
I think a team of 2 or 3 developers should be enough to develop on this rom, as we can use a lot from AOSP 4.1.2
### EDIT
As long as no one has found to help, here a short description of current progress:
- Code is pure based on AOSP 4.2 but some snippets of CyanogenMod to bring up hardware (camera,graphics,audio)
- Device is bootable (no other boot.img required anymore)
- Bootanimation is working
- Mount of partitions is working
- Deodexing is working
- adb, debuggerd and root access is working
Not working: a lot
- Graphic not working perfect, needs a kernel patch or a working gralloc/hwcomposer/hwconverter to work without laggy PMEM)
- Camera can not be activated due to a missing function call (undefined reference, maybe it can be solved with a newer driver)
- Audio: missing speaker device (Code have to reworked to work with stagefright and tinyalsa libs)
- USB/internal SDCard: cant be mounted (error message sounds like the device is mounted twice, have to find the error in init process)
- RIL not working (Java file from CM10 have to be integrated in frameworks/opt/telephony)
Currently, i'm working on the Graphic problem and USB part to bring up the device to a stable UI
Way to go man. Good luck to you!
Good luck ...!! Im waiting
Sent from my GT-I9300 using xda premium
Good evening,
Well how have you imagined that? Do you have build something like that before or would this be your first attempts to build up a rom from scratch? Do you know what's all necessary to contribute for that?
I would try to help you, but I have clearly to say that I haven't done anything like this before. I'm in the last term of my study of technical computer sciences, working in a company as application programmer for C/C++ and Java(Android). Due to my studies I have also some knowledge about hardware programming, down to read/writing some code in assembler. I would be interested to this if I get introduced to the topic and some help with the necessary tool chain wouldn't hurt too ^^.
greetings
hop3l3ss1990 said:
Good evening,
Well how have you imagined that? Do you have build something like that before or would this be your first attempts to build up a rom from scratch? Do you know what's all necessary to contribute for that?
I would try to help you, but I have clearly to say that I haven't done anything like this before. I'm in the last term of my study of technical computer sciences, working in a company as application programmer for C/C++ and Java(Android). Due to my studies I have also some knowledge about hardware programming, down to read/writing some code in assembler. I would be interested to this if I get introduced to the topic and some help with the necessary tool chain wouldn't hurt too ^^.
greetings
Click to expand...
Click to collapse
I have successfully built a rom in year 2010 for the LG-P500 device, based on CM7 and modified it in a strange way, so i included a lot of nice things
written from scratch - this rom was a unicate ... later, i developed the "Phoenix Launcher" for Gingerbread enabled devices, but its development is currently
frozen because its strange to support every or almost every device with a bugless launcher. In the last months i learned a lot about android and have to re-think about
what i'm able to do, and what i want to do. In the summer of 2011 i bought my SGS3, the first thing i was doing was to remove that samsung crap from my device and
have installed AOKP. So now it's time to do my own thing again - i want to have AOSP as i think for me its the best Android solution for myself and want to publish it
to other users who think "thats ok for me" too
In short, it doesnt matter if its your first rom - its enough if you know about basic things like "how is android doing all that nice things", "how to debug code", "how to fix
some bugs (even strange bugs)" and some experience with git and github. All other you can learn in a very short time - i've learned the most of things with try & error
andy572 said:
I have successfully built a rom in year 2010 for the LG-P500 device, based on CM7 and modified it in a strange way, so i included a lot of nice things
written from scratch - this rom was a unicate ... later, i developed the "Phoenix Launcher" for Gingerbread enabled devices, but its development is currently
frozen because its strange to support every or almost every device with a bugless launcher. In the last months i learned a lot about android and have to re-think about
what i'm able to do, and what i want to do. In the summer of 2011 i bought my SGS3, the first thing i was doing was to remove that samsung crap from my device and
have installed AOKP. So now it's time to do my own thing again - i want to have AOSP as i think for me its the best Android solution for myself and want to publish it
to other users who think "thats ok for me" too
In short, it doesnt matter if its your first rom - its enough if you know about basic things like "how is android doing all that nice things", "how to debug code", "how to fix
some bugs (even strange bugs)" and some experience with git and github. All other you can learn in a very short time - i've learned the most of things with try & error
Click to expand...
Click to collapse
This all sounds interesting for me and yes I like the idea of developing a own clean rom with some cool additional stuff, too. But what would be the first steps to a new rom? Have you begun with all the administration stuff like setting up a new gitrepo, make a to do list etc...?
I think Code debugging and writing some new stuff wouldn't be a problem for me but what are you meaning excactly with "how is android doing all that nice things"? How it build up, deep level architecture? Well, I know how the "normal" Linux system is working, how modules are getting loaded into the kernel... But how this is correctly working on android I have to learn at first and if there is a chance to do that I would do it
Currently on my S3 is SlimBean and till that there is still no update to 4.2 I'm happy with it, but exploring something new would be pretty cool
Do you have an IRC chat room or something like that? I've to go offline now, my girlfriend wants more attention.^^ But If you want, I' m willing to try to contribute to the rom
PS. I'm sorry for my bad English and hope its understandable, but outside from here you can talk to me in German ^^
If you want to help the AOSP experience on our phones the best place to do it is with the CyanogenMod guys. You'll find pretty much everything based on AOSP (including people that port Vanilla AOSP and AOKP) is using a CM kernel.
They're likely working on the merge now in terms of getting CM10.1 out (with Android 4.2) but most of our CM guys are pretty burned out on working with Samsung's subpar reference material to get basic stuff working (mostly HWC). If you think you could help with this, this would be provide a massive boost to the whole community that want to run these phones on an AOSP based ROM and they would be very grateful.
Gotta warn you though it sounds like it'll be an uphill struggle to get the rest of the stuff working right; unless Samsung release some decent sources for HWC.
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
andy572 said:
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
Click to expand...
Click to collapse
Wish i could help (just started learning JAVA ) ! gl with this awesome project
Nice to see you here, I remember you from the P500 forums.
Xda user krarvind should be able to give you some useful hints, you will have to contact him through the RD forum as his pm is locked down, or I could possibly put him in contact with you
slaphead20 said:
Xda user krarvind should be able to give you some useful hints, you will have to contact him through the RD forum as his pm is locked down, or I could possibly put him in contact with you
Click to expand...
Click to collapse
Thank you, it would be nice if you can contact him
andy572 said:
Thank you, it would be nice if you can contact him
Click to expand...
Click to collapse
Ok, will mention it to him
andy572 said:
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
Click to expand...
Click to collapse
How it's going forward?
Maybe it could be useful to publish the github link when it's ready and some more information like staus, on first post
In the next days I have some trouble with my exams ( in two weeks I'm completely finished with my studies ^^) but I think if there is something to do I'll find some time to work on.
Good Luck Dude~
I haven't tried AOSP yet.
Hope someday i can give it a go.:silly:
hop3l3ss1990 said:
How it's going forward?
Maybe it could be useful to publish the github link when it's ready and some more information like staus, on first post
In the next days I have some trouble with my exams ( in two weeks I'm completely finished with my studies ^^) but I think if there is something to do I'll find some time to work on.
Click to expand...
Click to collapse
current state:
- patched android/build so we can compile the kernel within the main compile process
- patched android/build main.mk file so we can use OpenJDK or Oracle JDK
- added android/vendor/aokp and android/vendor/samsung tree from AOKP (its the most useful directory structure)
- added android/hardware from AOKP so we have all that Exynos things that are needed, even by AOSP
- modified android/frameworks/native/include so a OMX Plugin header can be found
- modified android/libhardware and patched gralloc module
currently it compiles to the Webkit library, most of all apps, libs and binaries are building without errors - the next problem
to solve is the PRODUCT_COPY_FILES ****: nothing of proprietary files are copied to the android/out directory, seems like
a bug in android/build too.
For only 2 days trying to compile to the end without errors its a very good cut
here we go: it compiles to the end and a flashable "JOP40" zip could be created
tryed to flash, but it gives errors in CWM: have to remove the recovery folder and the recovery.sh file from etc folder in the ota zip file, but it doesnt boot up - got a black screen only.
do we need a new or patched kernel instead the CM10 smdk421x one?
Well does it have all the closed source libraries fron the phone? If not, it wont boot. Dont think i am calling you stupid, you obviously know what you are doing, but maybe you forgot. Idk. Check that. Try running a log cat and debug that.
Sent from my GT-I9300 using xda premium
b-eock said:
Well does it have all the closed source libraries fron the phone? If not, it wont boot. Dont think i am calling you stupid, you obviously know what you are doing, but maybe you forgot. Idk. Check that. Try running a log cat and debug that.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thanks for the hint, yes i have all files included - i cant connect to adb, i see only small colored point on the top left side and a sensor
is red blinking (the one to the right of the speaker.
That would be the proximity sensor near the top front speaker. Cant connect, adb binary in /system/bin or xbin?
Sent from my GT-I9300 using xda premium
NEED HELP
Hello guys, I'm working on a generic tree for our beloved device Honor 7, but not getting enough success, so each and every of you are invited to help me create a new device tree for AOSP 5.1 ROM or CM 12.1, so that we can taste the Stock Android too.
The benefits of these ROMs are that the device will get more fast and stable as there will be minimum apps and bloatwares installed.
So, it is a humble request, that whosoever have any knowledge about creating a tree from scratch please help me.
I have created a skeleton of the tree but it is not a success too as there are many things we still have to consider.
@sminki and @kenshiwara, we will setup an organization on GitHub so everyone can contribute there only.
Hi,
It will be wonderfull to have CM on our honor7.
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
sminki said:
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
Click to expand...
Click to collapse
Thanks, this will help enough and I was not aware of your troubles
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Is there any whatsapp group of honor 7.I want to join it.
udayraj99 said:
Is there any whatsapp group of honor 7.I want to join it.
Click to expand...
Click to collapse
Stop spamming
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Mee too
omkarpranavxxx said:
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Click to expand...
Click to collapse
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
asiekierka said:
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Click to expand...
Click to collapse
Hello, did any of the CM compiled fully to be a flashable zip? if yes, then have you flashed it and took logcat?
Nishadan said:
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
Click to expand...
Click to collapse
Yup lesson learnt snapdragon or nothing frm now on
maybe you know
I post link - http://download-c.huawei.com/downlo...oadId=62086&version=204465&siteCode=worldwide
Honor 7 Open Source（PLK-L01_Android5_0_2_EMUI3_1_kernel_EN)
Any progress?
I hope I can do something,it is nice to see cm for honor 7.
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
cycovision said:
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
Click to expand...
Click to collapse
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
DigiGoon said:
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
Click to expand...
Click to collapse
good luck with your exams
Until then you can use this
New ROM for Honor 7 PLK-L01.
DigiGoon said:
Until then you can use this
New ROM for Honor 7 PLK-L01.
Click to expand...
Click to collapse
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
muhammad Shohayeb said:
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
Click to expand...
Click to collapse
I will be developing AOSP 6.0, if others can give it a try then maybe we can get it.