I understand there are some builds available on github ( https://github.com/omnirom/android_device_oppo_n1 ). Please could anyone guide on how to build it so we can test it on our devices. Thanks.
That would be a pretty in-depth guide.
Omnirom has their own wiki page that can teach you how to compile and port to your device.
http://docs.omnirom.org/Main_Page
:good:
Thank you Harfainx for sharing the guide, I'll try following it and post my finding(s) for everyone.
Omni rom has been posted on the official oppo forums already: http://www.oppoforums.com/threads/4-4-omni.7475
nospam said:
Omni rom has been posted on the official oppo forums already: http://www.oppoforums.com/threads/4-4-omni.7475
Click to expand...
Click to collapse
Sure wish he would post them here instead, or as well. I do check both forums but like to treat XDA as the "ultimate" resource.
I'm sure there will be an official Omni thread with the links here as well.
Sent from my N1 using Tapatalk
Harfainx said:
I'm sure there will be an official Omni thread with the links here as well.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
Yeah, plodey and I will eventually get around to it... we've just been incredibly busy with getting the device running and other general omni things.
Anyone who knows me from the i777 days knows that I suck at thread maintenance.
Entropy512 said:
Yeah, plodey and I will eventually get around to it... we've just been incredibly busy with getting the device running and other general omni things.
Anyone who knows me from the i777 days knows that I suck at thread maintenance.
Click to expand...
Click to collapse
Glad to hear an official response. Thanks for the update. :highfive:
viperdream26 said:
Sure wish he would post them here instead, or as well. I do check both forums but like to treat XDA as the "ultimate" resource.
Click to expand...
Click to collapse
Maintaining a thread is more work then you would ever think
At the moment I am more then full doing that at oppoforums
I'm going to take a crack at compiling the Cyanogen Source code to take a peek at the o-click issues.
I'm fairly knowledgeable in C, but haven't done any android/bluetooth coding before, so I think I have a snowball's chance in hell.
But it'll be an interesting exercise anyway.
So I'm following random links in:
http://wiki.cyanogenmod.org/w/Development
Mainly using this:
https://skydrive.live.com/view.aspx?cid=B3BFF0D42AE1E534&resid=B3BFF0D42AE1E534!107&app=OneNote
To set up virtualBox/Ubuntu/android SDK.
Although I am a bit confused about required JDK versions.
Is there a list of prefered JDK versions for different CM versions?
I also just noticed the page for the Find 5: aka
http://wiki.cyanogenmod.org/w/Build_for_find5
So I guess I'll use that as the instructions until the actual source code pull?
- Frank
You might want to look at maxwen's github - I think he had source for a sample app for the O-Click.
https://github.com/maxwen/OClick
Entropy512 said:
You might want to look at maxwen's github - I think he had source for a sample app for the O-Click.
https://github.com/maxwen/OClick
Click to expand...
Click to collapse
This is based on the Google BLE sample. It allows pairing with the o-click and will recognise single and double clicks on the remote
Sent from my N1 using Tapatalk
I'm slowly making some progress.
I have some questions:
1) Where can I find information about how updater-script is generated?
I'd like to automatically remove that first line which is causing TWRP to complain.
2) I got a zip file but it failed to install, and just hung after reboot.
I've compared the good "signed" zip to my zip file and I seem to be missing all the vendor specific stuff.
I extracted everything and it all exists in ~/android/system/vendor/oppo/n1/proprietary .
But it's not ending up in the final zip file.
I think the problem is that ~//android/system/vendor/cm/vendorsetup.sh is choking because
there isn't an official N1 build listed on: https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets
Do I have to hack my way around that?
Any help would be much appreciated.
I'm trying to research myself but it seems like information is scattered all over the place.
ChodTheWacko said:
I'm slowly making some progress.
I have some questions:
1) Where can I find information about how updater-script is generated?
I'd like to automatically remove that first line which is causing TWRP to complain.
2) I got a zip file but it failed to install, and just hung after reboot.
I've compared the good "signed" zip to my zip file and I seem to be missing all the vendor specific stuff.
I extracted everything and it all exists in ~/android/system/vendor/oppo/n1/proprietary .
But it's not ending up in the final zip file.
I think the problem is that ~//android/system/vendor/cm/vendorsetup.sh is choking because
there isn't an official N1 build listed on: https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets
Do I have to hack my way around that?
Any help would be much appreciated.
I'm trying to research myself but it seems like information is scattered all over the place.
Click to expand...
Click to collapse
I'm in no way an expert and am currently in the process of setting up my first build environment now. In regards to #2, I noticed that in the vendorsetup.sh on the N1's github page - https://github.com/CyanogenMod/android_device_oppo_n1 - it sets up the lunch combos for you.
add_lunch_combo cm_n1-user
add_lunch_combo cm_n1-userdebug
add_lunch_combo cm_n1-eng
Click to expand...
Click to collapse
Could you just be using the wrong vendorsetup script or should that one run first? Like I said, I'm still very new to this but wanted to at least point this out.
mybrotherischad said:
I'm in no way an expert and am currently in the process of setting up my first build environment now. In regards to #2, I noticed that in the vendorsetup.sh on the N1's github page - https://github.com/CyanogenMod/android_device_oppo_n1 - it sets up the lunch combos for you.
Click to expand...
Click to collapse
You're right, the n1 directory's vendor explicitly lists them.
I was looking at the wrong one I guess. Or it's not being used for some reason.
My Brunch n1 is also complaining with:
The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.
which doesn't look right, but I'm taking stuff one step at a time.
- Frank
Related
[This is not the place to say "this is awesome" or "thanks!"]
[DEVS ONLY]
I want to start this thread to keep up the progress on the port.
the bad news is that the SDK is incomplete for now, so (like other devices)
we will have to write our own code for the OS, the nook community
has done a wonderful job writing their own libraries and stuffs, so we will have to do the same.
Instead of pursuing different goals, let's focus on one thing at a time.
since GSM and CDMA versions are already out, it seems we suffer the same bugs, so for now let's unite strength and knowledge to overcome these.
I propose that the first goal to fix is the SurfaceFlinger, so we could at least see the apps, the buttons and the notifications.
it is currently throwing this:
04-06 22:01:35.495: ERROR/Surface(2960): dequeueBuffer failed (Out of memory)
this could lead us that it might coudln't start because of some malloc malfunction or something.
also that pvrsrvinit bugs me a lot.
update:
8/APR/2011
since DiP7 could fix SurfaceFlinger and other things using a different build from the GSM kernel, we have to dig deeper
======================================
CURRENT GOAL
Rebuild Kernel
======================================
Current approaches:
*none
Post any finding, guessing or anything, and please, please don't be afraid to ask anything you have a doubt, as a Dev you should not know everything, so we can help us each other
------------------------------------------
Google Easter egg:
while searching some info about the android.mk file , I put it on the chrome bar to search for that term, but instead I went to
http://android.mk
an easter egg web page from google lol
******TOOLS*********
How to send text and Keystrokes via ADB
http://bradchow.blogspot.com/2011/02/send-intent-and-key-event-by-adb.html
use DroidExplorer to easily access your device from your computer and makes changes from it
http://de.codeplex.com/
The Android Boot Process
http://www.androidenea.com/2009/06/android-boot-process-from-power-on.html
---Kernel Tools----
CPU Datasheet
http://forum.xda-developers.com/showthread.php?t=745877
Samsung GIT
http://android.git.kernel.org/?p=kernel/samsung.git;a=summary
PowerVR SDK
http://www.imgtec.com/powervr/insider/powervr-sdk.asp
Source code of samsung firmwares(keep and eye on this)
http://opensource.samsung.com/
Asus pad honeycomb Kernel Source
http://forum.xda-developers.com/showthread.php?t=1026528
ellokomen said:
======================================
CURRENT GOAL
Find why SurfaceFlinger is not working
======================================
Click to expand...
Click to collapse
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)
updated approaches and new tools have been added
spacemoose1 said:
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)
Click to expand...
Click to collapse
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb
lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb
Click to expand...
Click to collapse
you mean that you made a port of a Linux Distro into the tab?
ellokomen said:
you mean that you made a port of a Linux Distro into the tab?
Click to expand...
Click to collapse
yes click here for the thread on the port of ubuntu
Current kernel source
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
here it is, bear in mind that this is for CDMA devices
Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??
daml said:
Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??
Click to expand...
Click to collapse
yeah but we need a place for the other devs to share their milestones, here is a place for technical discussion amongst us, to share the knowledge etc...
the other threads are flooded from non devs messages, so it´s kind of difficult to read 14 pages of information when the 80% is people complaining not making it boot
lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
Click to expand...
Click to collapse
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.
noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
D'oh! Nobody told me, LOL... I'll get another copy up.
spacemoose1 said:
D'oh! Nobody told me, LOL... I'll get another copy up.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!
Flokey said:
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!
Click to expand...
Click to collapse
Digging through it now.
spacemoose1 said:
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.
Click to expand...
Click to collapse
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb
lilstevie said:
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb
Click to expand...
Click to collapse
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.
Goal and tools updated*
spacemoose1 said:
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.
Click to expand...
Click to collapse
You don't know what a kernel panic is do you?
lilstevie said:
You don't know what a kernel panic is do you?
Click to expand...
Click to collapse
I thought that linux throws a dump log when it makes a kernel panic specifying the memory address and the cause of crash
Okay so with the help of a lot of people and hours of work I have successfully built a kernel for the sg3. I want to take the next step to roms however (I know, big step).
Using the xda-university thread I have setup a repo and am currently pulling the latest 4.3 AOSP source (will let it sit overnight, my internet isn't too amazing and I have HDD not SSD *sadface*)
As far as I understand it so far, I need to find suitable device tree sources to get AOSP sources working on the sg3 (at&t for now). I have been doing a lot of searching and reading, but as usual when you get started, its like a sea of information. If anybody could give me some reading material or direction on taking on this venture, it would be much appreciated. Feel free to be as technical or nontechnical, I will read til I get what you mean.
Thanks
EDIT: so I did some reading and decided to go with cm's d2 device tree and see if it works. I created a new directory in /root/devices/samsung called android_device_samsung_d2-common
Unfortunately when I use the lunch command, it is not one of the selectable options. I read that I need to edit my .repo/manifest.xml to include it but upon examination I tried adding the following line but it didn't help
Code:
<project path="device/samsung/android_device_samsung_d2-common" name="device/samsung/android_device_samsung_d2-common" groups="device,d2" />
any ideas?
Anyone?
If you want to build cm, look here
http://wiki.cyanogenmod.org/w/D2att_Info
It has a very good tutorial on how to build cm
mrhaley30705 said:
If you want to build cm, look here
http://wiki.cyanogenmod.org/w/D2att_Info
It has a very good tutorial on how to build cm
Click to expand...
Click to collapse
Thanks, wanted to build from source directly and just use cm device trees but I guess I should make smaller steps and try basing off of cm first. Thanks for the link, will try
It's also a good way to test your build environment. If you can build cm straight up, then you'll know if something you did broke it. And believe me, trying to chase down build errors is a pita.
Hi And Welcome To a Non-Tested Version of Android 6.0.0 on the xoom (Maybe 5.1.1 Not Sure) But back to the topic
This is mostly 5.1.1 but maybe with new of fixed features (I've never tested it as I said)
Here is how to install (I found this on another area)
1. ROOT YOUR DEVICE
2. Install BigPart TWRP
3. Wipe your system and flash the zip file
Here is the zip file
(I'm having Issues of Attaching The File So Please Wait)
XDA:DevDB Information
Android 6.0.0 or Android 5.1.1, ROM for the Motorola Xoom
Contributors
MichaelTech, Schischu, dreamcwli, michie
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 2.6.x
ROM Firmware Required: Rooted BigPart
Based On: OmniRom
Version Information
Status: Alpha
Created 2015-11-19
Last Updated 2015-11-19
so is this rom 5.1.1 or 6.0? id love to try it out...
I just resurrected my old xoom and converted it to bigpart.
waiting for the zip....
Waiting for test it.
Did you build this rom? If so, how can you not know what version of Android it is?
MichaelTech said:
(I've never tested it as I said)
Here is how to install (I found this on another area)
Click to expand...
Click to collapse
Can you provide more information please?
Just "copy n paste" from "other area" is not very trustworthy... i'm sorry to say.
I would love to have 6.0 on Xoom, but I want it to be wit ha Git Repo or anything and not only an ominous zip file from somewhere...
so please, more information is the key!
sdthelord said:
Can you provide more information please?
Just "copy n paste" from "other area" is not very trustworthy... i'm sorry to say.
I would love to have 6.0 on Xoom, but I want it to be wit ha Git Repo or anything and not only an ominous zip file from somewhere...
so please, more information is the key!
Click to expand...
Click to collapse
Based on this post, I think that, best-case scenario, he just kanged Schischu's 5.1.1 build and maybe themed it to look like 6.0. But I'm betting we never see a zip file.
As with everyone else I am curious to this. [6.0.0/5.1.1(Not Sure)] <--- this seems a little strange. It can only be one Android version. If it's 5.1.1 with some cherry picks and tweaks, that's great but just say.
Also some source would be good so we can establish what it actually is. Upload to androidfilehost or something similar if you can't attach.
P.S OmniRom wanted me to make a rom so perfectly fine
MichaelTech said:
P.S OmniRom wanted me to make a rom so perfectly fine
Click to expand...
Click to collapse
Look we shouldn't be fighting about whos rom it is It's just code that matters
MichaelTech said:
Look we shouldn't be fighting about whos rom it is It's just code that matters
Click to expand...
Click to collapse
Here is the error I keep getting
vBulletin Message
Invalid post specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post.
but nothing happened to this page so what is this problem
MichaelTech said:
Look we shouldn't be fighting about whos rom it is It's just code that matters
Click to expand...
Click to collapse
Speaking of ROM's, when can we expect yours? If the item you posted in #11 is still the zip attachment problem, have you thought about trying the suggestion from Matt4321?
brewer75 said:
Speaking of ROM's, when can we expect yours? If the item you posted in #11 is still the zip attachment problem, have you thought about trying the suggestion from Matt4321?
Click to expand...
Click to collapse
I can when you solve my problem I keep having
MichaelTech said:
I can when you solve my problem I keep having
Click to expand...
Click to collapse
The Download is now available in the downloads tab
here is info
Modified Launcher3
Modified SoundRecorder
Modified PackageInstaller
Android 5.1.1 with tweaks
gapps and super su are not included so please download them
If the OP did not do some coding on our outdated kernel and just synced omnirom sources, or even worse, just replaced some apk's in the flashable zip, all bugs are still there. If you did alter the kernel code you have to apply to GPL and post kernel sources.
I don't mean any disrespect but I kinda have the feeling that you don't have alot of experience with coding. (Please correct me if I'm wrong though) Posting untested software can give inexperienced users alot of problems and could be potential dangerous with our altered partion layout.
This wont have any benefit over Schisu's rom for now so I really have to advise you to wait for updated kernel sources before posting.
michie said:
If the OP did not do some coding on our outdated kernel and just synced omnirom sources, or even worse, just replaced some apk's in the flashable zip, all bugs are still there. If you did alter the kernel code you have to apply to GPL and post kernel sources.
I don't mean any disrespect but I kinda have the feeling that you don't have alot of experience with coding. (Please correct me if I'm wrong though) Posting untested software can give inexperienced users alot of problems and could be potential dangerous with our altered partion layout.
This wont have any benefit over Schisu's rom for now so I really have to advise you to wait for updated kernel sources before posting.
Click to expand...
Click to collapse
First yes that was very mean
second many other roms use these old kernels like OmniRom 5.1.1 for the xoom
third im a level 8 of 10 coder
Download not possible. File not found.
MichaelTech said:
First yes that was very mean
second many other roms use these old kernels like OmniRom 5.1.1 for the xoom
third im a level 8 of 10 coder
Click to expand...
Click to collapse
Like I said, I don't mean any disrespect my friend. The Xoom needs talented developers but not knowing if your rom is android 6 or 5 raises questions
You should contact the old member of team EOS or Schischu.
Good luck.
michie said:
Like I said, I don't mean any disrespect my friend. The Xoom needs talented developers but not knowing if your rom is android 6 or 5 raises questions
You should contact the old member of team EOS or Schischu.
Good luck.
Click to expand...
Click to collapse
I mostly belive its android 5.1.1
MichaelTech said:
im a level 8 of 10 coder
Click to expand...
Click to collapse
How many more XP do you need before you level up to 9?
What a joke...
As the title says. This board is created for questions and answers pertaining to getting new ROM's and ports for our P9000.
THIS IS NOT A BUG REPORT DISCUSSION.
New Development only.
If you would like to see a new ROM for the P9000? Build it, and share it. Check out some of the guides, then ask some questions on building it.
I will be staying with Mediatek devices for the long term and encourage more people like me to start bringing some development love to them.
Thank you
Some useful guides.
https://www.youtube.com/watch?v=aF--LQDgg1M
http://source.android.com/source/initializing.html
Any guides to add? I'll be glad to add them.
Credits:
@Deepflex (Active) Vendor, Device, Kernel sources
@Jonny (Active) TWRP and multiple additions to Kernel source
@skeleton1911 (Active) Stock based ROM's
@leskal (ACTIVE) device and kernel commits
Please let me know of any credits I'm missing.
Have been working on CandyRom6. Been getting a lunch error in line 234. Not quite sure how to get lunch to point to the correct mk file. candy/device/elephone/p9000/candy.mk. Any suggestions?
syncing AOKP MM. I enjoyed this rom in my samsung days.
something interesting to try for automating builds.
http://forum.xda-developers.com/chef-central/android/guide-tool-projekt-scribt-v1-33-t3503018
electrofryed said:
Have been working on CandyRom6. Been getting a lunch error in line 234. Not quite sure how to get lunch to point to the correct mk file. candy/device/elephone/p9000/candy.mk. Any suggestions?
Click to expand...
Click to collapse
Check the .mk files in the root of your device tree, I'm guessing you need to rename a reference in one of them from something like 'cm.mk' to 'candy.mk'
So far I've modified /AndroidProducts.mk cm.mk vendorsetup.sh I think I'm missing a file to modify. Just not sure which one. Unfortunately, since I didn't make a copy of the original Candy directory, I'll need to resync to get rid of my Troubleshooting changes. Good lesson. After each sync, make sure you make a backup of the original in case you forget the modifications you've made. Lol
I think I figured it out. My product name didn't match the vendorsetup.sh
Update: Nope. That didn't work. I've attached a screenshot of the changes I've made in case anyone wants to chime in.
Thank you
What lunch command are you using?
Jonny said:
What lunch command are you using?
Click to expand...
Click to collapse
I just used lunch to check the build. I used brunch for AOKP and it seems to be working at the moment. I'm going to re sync candy and start from scratch next weekend. I noticed when using lunch in AOKP, it used my git which wasn't setup when building candy.
electrofryed said:
I just used lunch to check the build. I used brunch for AOKP and it seems to be working at the moment. I'm going to re sync candy and start from scratch next weekend. I noticed when using lunch in AOKP, it used my git which wasn't setup when building candy.
Click to expand...
Click to collapse
I recomend the brunch command as on official build guide of cm
Yeah. I tried brunch and "rainbowfarts" (recommended by AOKP. Lol. It stops when calling for maven 1.6 (I'm on 2.10). I think I need to find the file that will link my builds to my build environment path.
leskal said:
I recomend the brunch command as on official build guide of cm
Click to expand...
Click to collapse
BTW. Glad to see you here. I've seen your work on git and wanted to credit you.
electrofryed said:
BTW. Glad to see you here. I've seen your work on git and wanted to credit you.
Click to expand...
Click to collapse
Nice, also check this guide: https://wiki.cyanogenmod.org/w/Build_for_huashan#Install_the_Build_Packages
Maybe you will fix the prob with the "brunch" command
leskal said:
Nice, also check this guide: https://wiki.cyanogenmod.org/w/Build_for_huashan#Install_the_Build_Packages
Maybe you will fix the prob with the "brunch" command
Click to expand...
Click to collapse
Great guide!! I see a few big differences between this guide and some of the others. The biggest is the method of getting java 7 for 16.04. I've been using Oracle and open Java 8 the whole time.
Update. I got past the initial halts in the AOKP build. When it finishes, I will be testing. (in the morning EST)
Update: spoke too soon. Kernel compiling issues. Another hurdle. Ugh
Hello,
i started my first build-experience with downloading the cm13 sources and the p9000 sources form deepflex. Since yesterday i have an successful build cm_p9000-ota.zip package but after installation it ends in an bootloop!! I have no idea where to start searching for the mistake... I get no error massage while installing it.
Could someone give me a hint?
electrofryed said:
Update. I got past the initial halts in the AOKP build. When it finishes, I will be testing. (in the morning EST)
Update: spoke too soon. Kernel compiling issues. Another hurdle. Ugh
Click to expand...
Click to collapse
You need to fix includes when building out of mtk build chain, or use other sources that already have this done
OK, i get it running!
But, is their a reason why "/android_device_elephone_p9000/mediatek_driver_nl80211.h" is missing in the repo? Sorry, but i am totally new and trying to understand how these builds work and what exactly is needed to build a bugles ROM.
Hi all,
I've created an issue on Motorola's kernel-msm repo that is a request for them to release the kernel sources for the G 5 Plus (Potter).
The post is here - https://github.com/MotorolaMobilityLLC/kernel-msm/issues/104
Please feel free to reply with similar requests so as to get Motorola moving on a proper GPL source release.
-Rob
bob2600 said:
Hi all,
I've created an issue on Motorola's kernel-msm repo that is a request for them to release the kernel sources for the G 5 Plus (Potter).
The post is here - https://github.com/MotorolaMobilityLLC/kernel-msm/issues/104
Please feel free to reply with similar requests so as to get Motorola moving on a proper GPL source release.
-Rob
Click to expand...
Click to collapse
https://github.com/MotorolaMobilityLLC/kernel-msm/blob/MMI-NPN25.137-15/arch/arm/configs/ext_config/mot8953-potter.config
:good:
The sources are already out....
Oh really? My bad... Can I just pull from that kernel-msm repo mentioned in the original post? Or is there a different repo just for Potter?
It looks like the source release for NPN25.137-15 is tagged here:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/MMI-NPN25.137-15/
It's a bit older than the version shipped with my phone but it could work. I'm going to see if I can compile it later.
bob2600 said:
It looks like the source release for NPN25.137-15 is tagged here:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/MMI-NPN25.137-15/
It's a bit older than the version shipped with my phone but it could work. I'm going to see if I can compile it later.
Click to expand...
Click to collapse
All the best. :good:
rayzen6 said:
All the best. :good:
Click to expand...
Click to collapse
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...
bob2600 said:
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...
Click to expand...
Click to collapse
Man yes let me mention the guy who successfully able to build with Alberto's sources. He is @i.snehal.kiran.
He has done this to compile but unfortunately for some reason he doesn't able to get the device to test. His msg is below
basically i have taken addison device tree ...just change the kernel path and defconfig name in boradconfig.mk ..makes it build boot.img
the source provided by motorola on github is full of errors..so use alberto's kernel for addison till you get official kernel from moto
https://github.com/Alberto97/android_kernel_motorola_msm8953
I edited the post bcz I thought u want to work with custom kernel for stock rom. And I thought this might not be useful.
bob2600 said:
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...
Click to expand...
Click to collapse
So what happened next? Did you tried something?
Edit:- btw one of the guy has replied positively on issue. :Good: I think we'll have a separate source soon.
rayzen6 said:
So what happened next? Did you tried something?
Edit:- btw one of the guy has replied positively on issue. :Good: I think we'll have a separate source soon.
Click to expand...
Click to collapse
I got as far as getting the LineageOS sources pulled for 14.1, had to do it twice since it was too big for my home directory so I had to create a new volume and run repo sync again. Took forever, but at least I have the OS sources downloaded. Now we're at the point of getting that kernel and setting up a device configuration for our device. Once we get that, then I can see if we can build and flash.
bob2600 said:
I got as far as getting the LineageOS sources pulled for 14.1, had to do it twice since it was too big for my home directory so I had to create a new volume and run repo sync again. Took forever, but at least I have the OS sources downloaded. Now we're at the point of getting that kernel and setting up a device configuration for our device. Once we get that, then I can see if we can build and flash.
Click to expand...
Click to collapse
Cool. Good work man. I'm in for testing.
Kernel sources are up
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPN25.137-33