Add driver and rebuild kernel. - Huawei P9 Plus Questions & Answers

Hi, i would like to know how to add drivers to stock kernel, rebuild and flash on stock rom. I was able to do it on my old Samsung S5 with cyanogenmod 12.1 using cyanogen repo and menuconfig gui where i checked rtl8187 driver etc etc...
Now, i found THIS guide on developer section but i'm stuck... i can't understand the right procedure couse it's different from the one i followed for the S5. Can you suggest me something? Thank you all :fingers-crossed:

Related

[Q] Stock Android

Hi guys,
I am really interested in figuring out the steps that should be followed in order to compile a stock android rom for i9000.
I find the phone amazing but really hate touchwiz and all samsung's applications.
Thanks in advance
compile a stock android rom for i9000.
Stock as in stock rom supplied by Samsung or do you mean a Custom Rom .
Custom roms are in the development section as are the guys that build them .
jje
JJEgan said:
compile a stock android rom for i9000.
Stock as in stock rom supplied by Samsung or do you mean a Custom Rom .
Custom roms are in the development section as are the guys that build them .
jje
Click to expand...
Click to collapse
I meant vanilla android, i am aware of resources where you can find stock samsung compilations (namely samfirmware -sorry but as a new user i cannot post links- although there's also an updated list in a thread somewhere in xda forums) and i also follow some of the custom made roms (currently i'm using Darky's v9.3).
I would like to get to know how to get my custom rom compiled and packged so i9000 can load it, the reason: i really dislike samsungs additions to android (touchwiz) and i haven't found a custom rom similar to what i am seeking.
For the first steps i suppose i should grab the code from aosp but i just don't know if i need some drivers (i suspect i do), and if so... where can i get these?
Then... once all that stuff is compiled, what are the steps that should be followed to make the compiled image flasheable?
Thanks.
I really thought that the custom ROMS in the dev section could be built as custom as you like via the kitchen. First take the bare Android 2.2.1 JPY/JS5 system and add the Gingerbread launcher as well as the market then off you go. Can't get anymore vanilla than that ?

Milestone + Cyanogenmod is compatible with ADK?

I have the latest Cyanongemod (Android 2.3.4) and i wish to know if it is compatible with Android Open Accessory Development Kit (ADK).
ADK is compatible only with Android 2.3.4 and 3.1 but im not sure if Cyanomgemod include the required libraries.
Hi!
I´ve been searching this for a while, and yes, cyanogenmod (at least nightly builds) support - you might have trouble getting other customs roms.
You need 2.3.4+ and 2.6.35+ kernel with CONFIG_USB_ANDROID_ACCESSORY flag set. Instructions about xml, permissions, here (sorry, cant post full urls):
github.com/ezterry/manifest-gingerbread-DS/issues/32
Push nexus files from here:
forum.cyanogenmod.com/topic/26339-usb-accessory-mode-is-adk-supported-in-cm-7/
And upload demokit via eclipse.
Regards
Robson
robsondantas said:
You need 2.3.4+ and 2.6.35+ kernel with CONFIG_USB_ANDROID_ACCESSORY flag set. Instructions about xml, permissions, here (sorry, cant post full urls):
github.com/ezterry/manifest-gingerbread-DS/issues/32
Click to expand...
Click to collapse
There is one problem - you cannot flash custom kernel on Milestone that is not signed by Motorola (locked bootloader). And the latest kernel that we have is 2.6.32.9, so that will not work.
If you want custom kernel (but without radio) you can try to have a fun with 2nd boot - http://droid-developers.org/wiki/2ndboot

[Q] Can't build CM6 from sources. Help please!

Hi,
I'm trying to build cyanogenmod 6 (froyo) from sources on github for G1.
Sidenote. The reason I'm trying to do this is i'd like to modify kernel parameters. I'm trying to make the phone talk to external device using built in serial port. I can do it with my current CM6, but it looks like serial debugger engages and starts responding to the device and also steals some of the data being sent to phone.
To build I used instruction posted at cyanogen wiki "HTC Dream & Magic: Compile CyanogenMod (OS X)" which covers gingerbread but checked out froyo-stable branch at first. I know that gingerbread version stopped supporting G1 at some point last year.
Without much success even after fixing manifest to point to updated repo urls from kernel.org to googles repo etc. The problem is that apache-http seems incompatible with old sources and it is referenced by head.
I also tried froyo branch, but it doesn't build as well because something seem to be broken for dream_sapphire, and it is not present in the devices anymore.
I've tried searching for compilation errors, and general build questions/instructions here and on cyanogen's forum, but looks like CM6 is not very active these days.
Can someone point me into right direction where to search for relevant info on building it? Would getting a proper revision help or should I combine stuff from several branches to make it work?
I've already spent quite a lot of time figuring out how build is being configured and how things stitch together but without much progress on the actual build.
And with times required to sync a whole repo and build it, it is becoming frustrating.
Any help would be muchly appreciated!
Regards,
Oleg
It's dead.
I also wanted to make a cm6 rom, but I couldn't get anything to work.
I got the addresses all updated but it looks like a bunch of the files have completely dissappeared. You may be able to make it skip those, but then it may not work completely.
Go for AOSP?
Now that's a shame. I wanted to build CM because I'm familiar with it and the other thing is that they have reasonable instructions about building it. But at least I don't need to waste my time trying to figure out how to fix it.
In fact I don't need any extras they provide, a bare android would suffice to me if all the sensors and connectivity would be available. But I'm not familiar with internals of building vendor specific stuff. My understanding was that I need proprietary parts together with AOSP to build a working ROM and that's one of the things CM guys did. Correct me if I'm wrong.
aliher1911 said:
Now that's a shame. I wanted to build CM because I'm familiar with it and the other thing is that they have reasonable instructions about building it. But at least I don't need to waste my time trying to figure out how to fix it.
In fact I don't need any extras they provide, a bare android would suffice to me if all the sensors and connectivity would be available. But I'm not familiar with internals of building vendor specific stuff. My understanding was that I need proprietary parts together with AOSP to build a working ROM and that's one of the things CM guys did. Correct me if I'm wrong.
Click to expand...
Click to collapse
Nope AOSP is as easy to build now
Go to the android site and follow directions
Google for "build android"
At the part when doing repo init you need to get the right branch
Go to "build for devices" then scroll down for recommended branches and look for the dream
One thing you'll need to do differently is do "make otapackage" instead of plain "make"
And once that's done you'll need to tweak the zip and get rid of the "recovery" folder and tweak the updater-script
Oh yeah, and I don't know exactly how you would do this part, but you'll need to get the source for a newer kernel in there, like ezterry kernel and use it with 2708+ radio/spl
Unless you wanna use the AOSP kernel & spl & radio which is old
What I did is just flash his kernel after the rom, but you want to do kernel stuff so yeah...
Sent from my HTC Dream using Tapatalk

CM7 on New Bootloader - Feasible?

Hi All
I am not really a developer at all but I have had loads of experience messing around with ROMs to improve them (such as changing rils manually, using my own updater scripts, creating my own nvflash layouts and images, etc).
Recently I have been trying out CM10.1 again (mivvs ROM) on the new bootloader and also paranoid android. But both are too buggy for me and the battery life is really bad. So I am thinking to revert back to CM7 again.
I am planning to *TRY* and build my own CM7 rom from source using these fixes by Pengus (http://forum.xda-developers.com/showpost.php?p=35661482&postcount=100) to try and make it boot and run on the new bootloader. I know the advantages are very little but its just a "to see if I can" thing. It will also mean others wanting to go back to CM7 won't have to flash the old bootloader again.
I am planning just a one-time build as CM7 has pretty much reached completion.
I am posting this up to:
Make sure no-one else has already done it
Make sure one of the devs doesn't know of a reason this 100% will fail
To see if anyone else would be interested in such a ROM
To know if its possible to build from Windows (if I need Linux then so be it)
Let me know what you think
hy
I have mivvs rom and the battery life in not bad.
however, your idea is interesting .. good job!
Well, I think this is quite interesting. However, I am a big fan of PA10 and Pengus work... for me they beat GB in all aspects at the moment. However, one of the greatest pro's of having a CM7 on the new bootloader is the ability to have dual boot with CM7 + CM10.1 (or something else), since dual boot only works for roms with the same bootloader.
So far I have:
Set up Ubuntu x64 VirtualPC
Installed Android SDK and all Dependancies
Sync'd the CyanogenMod 7 Source
Sorted out the P990 Proprietary libs
Made MOST of the changes Pengus lists (although some bits are in different files)
It turns out the kernel source isn't downloaded automatically with CM7 so I need to find out how to build the kernel from source (in order to make the rest of the changes on the list Pengus made) but I think its looking good..
CM7 also doesn't have fstab.p990 but these lines can be found in init.p990.rc. Until I have the kernel source I am stuck on point 6
And I didn't mean to knock Pengus/TonyP/Mivv's work. They have helped this phone come a really long way especially now acree seems to have dropped support for it.
Just FYI
I tried this, making all the changes above, compiled the build.... but it doesn't boot.
Just gets stuck on the red lg logo.
I think the old CM kernel will not run on the new boot loader at all.
Was worth a try!
rlees85 said:
Just FYI
I tried this, making all the changes above, compiled the build.... but it doesn't boot.
Just gets stuck on the red lg logo.
I think the old CM kernel will not run on the new boot loader at all.
Was worth a try!
Click to expand...
Click to collapse
Maybe your last resort, try the excellent CM7 ETaNa kernel (link is in my signature).
But, I guess it won't work; kernels are bootloader specific.

[Q] Compiling AOSP 4.2.2 for galaxysmtd?

Hello,
I searched through a lot of threads on how to compile CM, also checked CM wiki, but I want to compile AOSP, not CM. I want to compile it and maybe add some little tweaks to it. How do I compile it? I mean the device-specific part - which repositories, where do I put them (device, kernel,...) and so on?
I'm new to this, and also there's a problem with Ubuntu in VirtualBox, I cannot get my Galaxy S recognized via ADB in the virtual machine (Ubuntu). Just VirtualBox fails at connecting. So I want to ask also if there is any way to get proprietary vendor stuff from phone without using the extract-files.sh script? (another repository for this?)
I'm sorry if I'm starting a question that has been discussed before, but I couldn't find a thread about compiling AOSP for the galaxysmtd. I also checked malcho's thread for building unofficial nightlies and I'm lost there. Still don't know how...
Thanks in advance.

Categories

Resources