Related
This thread is only for Developers.
If you're looking for help or download links then this is not the right place.
User Thread: http://forum.xda-developers.com/showthread.php?t=2036229
How to build:
http://teamhacksung.org/wiki/index.php/CyanogenMod10.1:How_to_build
Sources:
https://github.com/cyanogenmod/android_device_samsung_i9100
https://github.com/cyanogenmod/android_device_samsung_galaxys2-common
https://github.com/cyanogenmod/android_kernel_samsung_smdk4210
https://github.com/cyanogenmod/android_hardware_samsung
How to submit patches?
http://wiki.cyanogenmod.org/wiki/Howto:_Gerrit
No, we don't accept pull requests!
Sorry, wrong post, please delete.
When is the 911/112/Emergency call going to be solved?
http://code.google.com/p/cyanogenmod/issues/detail?id=5700
This has been an EMERGENCY issue for 7 month's, and I dont wanna disrespect you guys. But this is something what really needs to be fixed. If we wanna use the rom we can't call the emergency line in a situation.
Provider: Vodafone NL
GT9100
RR 3.1.3 (every other CM rom also gives the "invalid number" error.
domingoo said:
When is the 911/112/Emergency call going to be solved?
http://code.google.com/p/cyanogenmod/issues/detail?id=5700
This has been an EMERGENCY issue for 7 month's, and I dont wanna disrespect you guys. But this is something what really needs to be fixed. If we wanna use the rom we can't call the emergency line in a situation.
Provider: Vodafone NL
GT9100
RR 3.1.3 (every other CM rom also gives the "invalid number" error.
Click to expand...
Click to collapse
no dev is on vodafone nl or kpn so chances that this will get fixed are not very high.
reminder: nightlies are experimental.
Sent from my Nexus 4 using xda app-developers app
codeworkx said:
no dev is on vodafone nl or kpn so chances that this will get fixed are not very high.
reminder: nightlies are experimental.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This has also been a problem with STABLE roms. I've also understood that there were plans to pull the CM9 stable because of this bug, but that has not happend.
Besides this people have also mentioned it's also a problem on other networks besides Vodavone NL or KPN NL, so don't pull the excuse that there are no devs available on just these networks. I have no doubt in my mind that if it had been mentioned that there are no devs with these connections people would have been willing to help in any way possible. Instead of this the problem is just ignored for months on end.
I've found that Trebuchet launcher doesn't have those graphic artifacts, caused by the placebocomposer. However, Nova Launcher has them and that makes me think you've found a way to fix the glitches in certain apps. If so, is it possible to implement these fixes to the daydream clock app? Also, I think that the analog daydream clock doesn't always glitch because it updates the screen every second, while the digital one does so every minute. Maybe if you make the digital clock update every second, the artifacts won't show?
Can't pull files
I was trying to build cm10.1 for i9100 for the first time and I get an error message about libtvout and libcamera not being pulled from device. Is there any known issue or am I doing something wrong?
I am following the new Wiki to the letter, but I can't get it to work.
http://wiki.cyanogenmod.org/w/Build_for_i9100
Prepare the device-specific code
After the source downloads, type:
$ source build/envsetup.sh
$ breakfast i9100
Click to expand...
Click to collapse
When I type
Code:
breakfast i9100
I get this error
Code:
** Don't have a product spec for: 'cm_i9100'
** Do you have the right repo manifest?
In the older Wiki's I see they use a local_manifest.xml.
Is this still necessary? It's not mentioned in the new Wiki at all....
CRXed said:
I am following the new Wiki to the letter, but I can't get it to work.
http://wiki.cyanogenmod.org/w/Build_for_i9100
When I type
Code:
breakfast i9100
I get this error
Code:
** Don't have a product spec for: 'cm_i9100'
** Do you have the right repo manifest?
In the older Wiki's I see they use a local_manifest.xml.
Is this still necessary? It's not mentioned in the new Wiki at all....
Click to expand...
Click to collapse
Try this guide http://teamhacksung.org/wiki/index.php/CyanogenMod10.1:How_to_build
Complete error
Code:
[email protected]:~/android/system$ . build/envsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
[email protected]:~/android/system$ breakfast i9100
including vendor/cm/vendorsetup.sh
ls: cannot access device/*/i9100/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_i9100". Stop.
Device i9100 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_i9100
Default revision: cm-10.1
Checking branch info
Adding dependency: CyanogenMod/android_device_samsung_i9100 -> device/samsung/i9100
Using default branch for android_device_samsung_i9100
Syncing repository to retrieve project.
error: project device/samsung/i9100 not found
Repository synced!
Looking for dependencies
Dependencies file not found, bailing out.
Done
ls: cannot access device/*/i9100/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_i9100". Stop.
** Don't have a product spec for: 'cm_i9100'
** Do you have the right repo manifest?
What is wrong?
---------- Post added at 03:18 PM ---------- Previous post was at 02:38 PM ----------
niko0o said:
Try this guide http://teamhacksung.org/wiki/index.php/CyanogenMod10.1:How_to_build
Click to expand...
Click to collapse
Trying that now, but shouldn't CM's own Wiki have the right information?
I get the idea it is missing something, but I don't know what exactly....
CRXed said:
Complete error
Code:
[email protected]:~/android/system$ . build/envsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
[email protected]:~/android/system$ breakfast i9100
including vendor/cm/vendorsetup.sh
ls: cannot access device/*/i9100/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_i9100". Stop.
Device i9100 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_i9100
Default revision: cm-10.1
Checking branch info
Adding dependency: CyanogenMod/android_device_samsung_i9100 -> device/samsung/i9100
Using default branch for android_device_samsung_i9100
Syncing repository to retrieve project.
error: project device/samsung/i9100 not found
Repository synced!
Looking for dependencies
Dependencies file not found, bailing out.
Done
ls: cannot access device/*/i9100/cm.mk: No such file or directory
build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_i9100". Stop.
** Don't have a product spec for: 'cm_i9100'
** Do you have the right repo manifest?
What is wrong?
---------- Post added at 03:18 PM ---------- Previous post was at 02:38 PM ----------
Trying that now, but shouldn't CM's own Wiki have the right information?
I get the idea it is missing something, but I don't know what exactly....
Click to expand...
Click to collapse
Where you able to compile in the end? I have not been at all following any guide
I'm still strying!
Turned out my Repo Sync was not complete after all....
I got a tip from someone to use
Code:
repo sync -j1
And then finally it pulled in the Samsung directory as well.
CRXed said:
I'm still strying!
Turned out my Repo Sync was not complete after all....
I got a tip from someone to use
Code:
repo sync -j1
And then finally it pulled in the Samsung directory as well.
Click to expand...
Click to collapse
Hm... That's interesting. So do you have the samsung specific folder synced now? Is it the one under /devices?
Sent from my GT-I9100 using xda app-developers app
juanono said:
Hm... That's interesting. So do you have the samsung specific folder synced now? Is it the one under /devices?
Click to expand...
Click to collapse
Yes!
Could someone. please, fix the mdpi lock screen and the sim lock screen or is it not supported anymore?
Since about cm10.1 - no cm10 build downloads for i9100 are available anymore so I can't test whether it started there - the irremovable widget (by default a clock but can be altered) on the lock screen has a fixed amount of space reserved whose relative size increases by lowering the dpi. At 160 dpi it accounts for half of the screen which makes the a pattern lock and the sim lock more difficult to use.
Since it is possible to have maximized widgets, it shouldn't be that difficult to fix.
Best would be to keep the current layout but let the pattern, pin or password input get focus and maximize and adding an option to completely disable lock screen widgets. Although resizing of the mdpi layout would be nice I don't know how that would affect build configurations using other dpi settings between 160 and 200.
The "Lockscreen Policy" app which claims to disable the widgets does so only partly. Except for the default clock it disables the running of widgets and the editing of the preexisting transparent panels so it doesn't change the layout settings.
siseam said:
Could someone. please, fix the mdpi lock screen and the sim lock screen or is it not supported anymore?
Since about cm10.1 - no cm10 build downloads for i9100 are available anymore so I can't test whether it started there - the irremovable widget (by default a clock but can be altered) on the lock screen has a fixed amount of space reserved whose relative size increases by lowering the dpi. At 160 dpi it accounts for half of the screen which makes the a pattern lock and the sim lock more difficult to use.
Since it is possible to have maximized widgets, it shouldn't be that difficult to fix.
Best would be to keep the current layout but let the pattern, pin or password input get focus and maximize and adding an option to completely disable lock screen widgets. Although resizing of the mdpi layout would be nice I don't know how that would affect build configurations using other dpi settings between 160 and 200.
The "Lockscreen Policy" app which claims to disable the widgets does so only partly. Except for the default clock it disables the running of widgets and the editing of the preexisting transparent panels so it doesn't change the layout settings.
Click to expand...
Click to collapse
You can download CM10 nightly from here http://goo.im/devs/cm/i9100/nightly .
niko0o said:
You can download CM10 nightly from here http://goo.im/devs/cm/i9100/nightly .
Click to expand...
Click to collapse
Thanks, I didn't notice goo hosted so many roms.
I tested the roms and the new lock screen is introduced with the first cm10.1 nightly. So, I guess, it may be a jellybean design flaw since Google doesn't support modifications anyway.
So I hope someone picks up this bug, especially using more complex patterns is pretty tedious when they're so small.
niko0o said:
Try this guide http://teamhacksung.org/wiki/index.php/CyanogenMod10.1:How_to_build
Click to expand...
Click to collapse
This link used to work, but now seems to be redirected, with a typo that doesn't work, to the CyanogenMod wiki. So does the one on the first page headed "How To Build".
Also the CyanogenMod wiki (http://wiki.cyanogenmod.org/w/Build_for_i9100) has somewhat different instructions on downloading the source code. I've not tried them because the teamhacksung wiki worked fine for me before it was redirected.
Hey guys , on the latest nightly , 21st march , the proximity sensor and accelerometer arent always working , had to downgrade to 20 march , im on stock cm10.1. Anyone else having this issuse ?
Also , did the 22nd march nghtly was launched ? I dont seem to find any new updates.
EDIT: 23rd march update fixed everything , thanks ! you guys rock !
Sent from my GT-I9100 using xda app-developers app
MMS not working
Hi!
I installed 10.1-20130327-NIGHTLY-i9100 and MMS messages are not working (receive or send). Looking at adb logcat output, I see:
Code:
W/TransactionService( 3806): Exception occurred while handling message: { what=1 when=-14ms arg1=1 obj=transactionType: 2 uri: content://mms/6 pushData: null mmscUrl: null proxyAddress: null proxyPort: 0 }
W/TransactionService( 3806): java.lang.NullPointerException
W/TransactionService( 3806): at com.android.mms.transaction.TransactionSettings.<init>(TransactionSettings.java:92)
W/TransactionService( 3806): at com.android.mms.transaction.TransactionService$ServiceHandler.handleMessage(TransactionService.java:640)
W/TransactionService( 3806): at android.os.Handler.dispatchMessage(Handler.java:99)
W/TransactionService( 3806): at android.os.Looper.loop(Looper.java:137)
W/TransactionService( 3806): at android.os.HandlerThread.run(HandlerThread.java:60)
This pointed me in the direction of APN settings, which are all fine (they were preserved during installation, and I'm coming from stock 4.0.3 Samsung OS).
I then noticed that the default APN (used for data), had the value of "APN type" set to "default,supl,mms". I erased all of the values, hoping that the other APN will be taken -- the one with the MMS settings, but still nothing.
Any ideas what to try next? It would be great if I could debug the transaction service to see why it can't get the APN settings...
Regards,
Miha.
---------- Post added at 11:49 AM ---------- Previous post was at 11:32 AM ----------
mihaval said:
Any ideas what to try next? It would be great if I could debug the transaction service to see why it can't get the APN settings...
Click to expand...
Click to collapse
Did some more digging. Install GOSMS pro app, to try that. I got a different bunch of exceptions:
Code:
E/DatabaseUtils( 2411): Writing exception to parcel
E/DatabaseUtils( 2411): java.lang.SecurityException: No permission to write APN settings: Neither user 10035 nor current process has android.permission.WRITE_APN_SETTINGS.
And that led me to this SO question. So I guess there needs to be a way to specify those permission for the MMS (Messaging) application somehow?
Hi,
I have added the following code on my local AOSP copy (master branch) and it starts up fine but the .mp3 is not playing. After putting more logging message and looking at the logcat I notice that the code didn't continue after calling the MediaPlayer() class
mPlayer = new MediaPlayer();
if (mPlayer == NULL) {
ALOGE("Failed to create MediaPlayer()\n");
return false;
}
Anybody has any experience troubleshooting this or have successfully implemented this gerrit issue ?. I'm testing it using Nexus 7 (grouper).
I cannot post the link to this post so I'm going to spell the link to the gerrit issue out
android-review.googlesource.com slash # slash c slash 38222 slash
Cheers
Not sure how well this works now, I have not messed with the boot sounds in a while now.
https://github.com/lithid/Scripts/blob/master/Android/bootsound.sh
I used to be able to get the boot sounds working with this script I wrote.
lithid-cm said:
....I used to be able to get the boot sounds working with this script I wrote.
Click to expand...
Click to collapse
Thanks lithid-cm.
I managed to make it work, the problem was because the bootanimation.zip contains only .mp3 it should contain the bootanimation logo. I've made a short demo video of using the CyanogenMod logo on an AOSP
youtube.com <slash> watch <question mark> v <equal sign> b0uuHlrJpGI
Hi, i'm trying to compile AOKP 4.3.1 fir htc hd2. I have downloaded the device tree, kernel, and other stuff needed. But now i wan't to compile it, and i don't have full_leo-userdebug in my menu. Any help?
lolerpro8 said:
Hi, i'm trying to compile AOKP 4.3.1 fir htc hd2. I have downloaded the device tree, kernel, and other stuff needed. But now i wan't to compile it, and i don't have full_leo-userdebug in my menu. Any help?
Click to expand...
Click to collapse
Try using a local manifest and pick up the device and kernel from another project - check out github for latest repositories for htc_leo. I found device and kernel from Evervolv's repositories. Local manifest would look something like this:
<manifest>
<project name="Evervolv/android_device_htc_leo" path="device/htc/leo" remote="github" revision="jellybean-4.3" />
<project name="Evervolv/android_kernel_htc_leo" path="kernel/htc/leo" remote="github" revision="jellybean-4.3" />
</manifest>
You might also need the vendor repository for leo, in which case add another project line to the manifest for cmhtcleo/android_vendor_htc_leo (path="vendor/htc/leo" revision="jellybean").
misterjaytee said:
Try using a local manifest and pick up the device and kernel from another project - check out github for latest repositories for htc_leo. I found device and kernel from Evervolv's repositories. Local manifest would look something like this:
<manifest>
<project name="Evervolv/android_device_htc_leo" path="device/htc/leo" remote="github" revision="jellybean-4.3" />
<project name="Evervolv/android_kernel_htc_leo" path="kernel/htc/leo" remote="github" revision="jellybean-4.3" />
</manifest>
You might also need the vendor repository for leo, in which case add another project line to the manifest for cmhtcleo/android_vendor_htc_leo (path="vendor/htc/leo" revision="jellybean").
Click to expand...
Click to collapse
I have them all installed dude, i just don't have *it* in my lunch menu
Apologies for the post above if it's teaching granny to suck eggs - I only realised after I posted that you were more experienced; and also that you're using AOKP (I wrongly read it as AOSP).
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
lolerpro8 said:
I have them all installed dude, i just don't have them in my lunch menu
Click to expand...
Click to collapse
Okay, I see - in my case, I tend to use brunch to do a build when in this scenario - I don't pick from a menu, e.g.
breakfast leo
brunch leo
(My use case is not leo though!)
misterjaytee said:
Apologies for the post above if it's teaching granny to suck eggs - I only realised after I posted that you were more experienced; and also that you're using AOKP (I wrongly read it as AOSP).
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
Okay, I see - in my case, I tend to use brunch to do a build when in this scenario - I don't pick from a menu, e.g.
breakfast leo
brunch leo
(My use case is not leo though!)
Click to expand...
Click to collapse
It can't find it, seas i don't have right repo manifest. Is it possible to manualy add it by modifying files?
lolerpro8 said:
It can't find it, seas i don't have right repo manifest. Is it possible to manualy add it by modifying files?
Click to expand...
Click to collapse
Sorry, I haven't done an AOKP build, but from what I can tell it's similar to CM:
. build/envsetup.sh
brunch leo
I might try AOKP as my next build to see what the difference is in the build experience.
lolerpro8 said:
Hi, i'm trying to compile AOKP 4.3.1 fir htc hd2. I have downloaded the device tree, kernel, and other stuff needed. But now i wan't to compile it, and i don't have full_leo-userdebug in my menu. Any help?
Click to expand...
Click to collapse
Have you added your device in the vendor/aokp/vendorsetup.sh?
Roladriz said:
Have you added your device in the vendor/aokp/vendorsetup.sh?
Click to expand...
Click to collapse
Nope. Thank I will try that.
Sent from my NexusHD2 using xda app-developers app
As well as adding to the vendorsetup.sh file, you'll need to copy/create the <device>.mk in the vendor/aokp/products folder. You may also need to edit the device.mk file (e.g. change full to aokp).
AOKP on TF201 built
Thanks for the inspiration - I've now built AOKP on the Android Transformer Prime (TF201) and installed it successfully on the device
Just need to add some apps and see if AOKP is any good compared to CM :fingers-crossed:
Adding target to the Lunch-menu
misterjaytee said:
Apologies for the post above if it's teaching granny to suck eggs - I only realised after I posted that you were more experienced; and also that you're using AOKP (I wrongly read it as AOSP).
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
Okay, I see - in my case, I tend to use brunch to do a build when in this scenario - I don't pick from a menu, e.g.
breakfast leo
brunch leo
(My use case is not leo though!)
Click to expand...
Click to collapse
Hello, You mentioned pulling the repository with your local manifest. I managed to do so and I have the correct vendor android.mk, blob, and proprietary information; however, I can't seem to figure out how to add them to the lunch-menu through the vendorsetup.sh script. Could you explain what you mentioned earlier?
(I'm working with Samsung Galaxy Note 4 SM-N910T - codename trlte)
I have tried to google this question as well and that`s what I can say: you have to extract the device blobs, you`d better check up the tutorial on how to do it
OKay So I thought I would try to port the latest beta of L to our OnePlus One. Never really ported before and mainly followed this thread here: http://forum.xda-developers.com/showthread.php?t=1908008
Currently I have it installing and booting to the boot animation and playing the boot animation (whooo) but thats as far as it goes. Unfortunately usb isn't recognized when I plug it in. Is there any way I can get some sort of log?
Its based on the latest nexus 5 L rom.
here is the zip file. Its broken, under no circumstance should you install this unless you are a developer.
Code:
DO NOT INSTALL IF YOU AREN'T A DEVELOPER
AOSP BASE
PA BASE
Current logcat on boot for PA:
http://pastebin.com/c5J0cmQ8
Can't get logcat on boot for AOSP base
Instead of AOSPA try using the official Oneplus AOSP rom as base. Let me know.
Nice of you that you even tried it! Maybe you developers should port this together in teamwork? Everybody has problems with L on the OPO, maybe together you can solve them
Did you tried it with OnePlus AOSP?
You guys might benefit from the discussion here:
http://forum.xda-developers.com/showthread.php?t=2829974
Transmitted via Bacon
---------- Post added at 08:12 PM ---------- Previous post was at 08:08 PM ----------
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
phoenixita said:
Instead of AOSPA try using the official Oneplus AOSP rom as base. Let me know.
Click to expand...
Click to collapse
just tried with aosp and although file structures and update scripts seemed more similar, I can't get a logcat and I am still stuck at a bootanimation
aeppacher said:
just tried with aosp and although file structures and update scripts seemed more similar, I can't get a logcat and I am still stuck at a bootanimation
Click to expand...
Click to collapse
There are some error with camera and sound :
E/AudioDaemon( 245): Open /proc/asound/card---/state failed : No such file or directory
[...]
E/mm-camera( 243): vpe_module_create_vpe_ctrl:141, failed, cannnot create vpe hardware instance
E/mm-camera( 243): vpe_module_init:34 failed
E/mm-camera( 243): c2d_module_init:28 name=c2d
E/mm-camera( 243): c2d_module_init:67: info: C2D module_init successful
E/mm-camera-img( 243): cac_comp_load:656] Error opening CAC library
E/mm-camera( 243): module_cac_init:1028] Error rc -6
E/mm-camera( 243): pproc_module_init:2175] cac module create failed
I don't know exactly why...
Maybe tomorrow and next week I'll try too
@aeppacher are you using latest android 5.0 preview LPX13D?
eugenioxx said:
There are some error with camera and sound :
E/AudioDaemon( 245): Open /proc/asound/card---/state failed : No such file or directory
[...]
E/mm-camera( 243): vpe_module_create_vpe_ctrl:141, failed, cannnot create vpe hardware instance
E/mm-camera( 243): vpe_module_init:34 failed
E/mm-camera( 243): c2d_module_init:28 name=c2d
E/mm-camera( 243): c2d_module_init:67: info: C2D module_init successful
E/mm-camera-img( 243): cac_comp_load:656] Error opening CAC library
E/mm-camera( 243): module_cac_init:1028] Error rc -6
E/mm-camera( 243): pproc_module_init:2175] cac module create failed
I don't know exactly why...
Maybe tomorrow and next week I'll try too
@aeppacher are you using latest android 5.0 preview LPX13D?
Click to expand...
Click to collapse
yes I am. I am posting my attempt at the aosp port with the LPX13D as well. Adb isn't grabbing a logcat for me unfortunately
Hopefully devs can help this would be sweet
Hit Thanks if I Helped
-_-NAMELESS ROM 1+1-_-
Hey man i'm no dev, but I just shared your post on Reddit (r/Android and r/oneplus) hopefully more devs will see this and come assist you I would love a port!
Just like previously mentioned I think you guys would benefit from the discussion in the thread previously posted. Better yet pm the developer who recently tried so you at least rule out some things that may have been previously attempted. Good luck guys
You cant port different version of Android by drag-and-droping system folders.
It'll probably be easier once retail Lollipop is out and open sourced on AOSP project. But TBH Cyanogenmod historically has put out builds really fast for nexus devices and ours is nexus-ish. I'll try my luck with kanging CM once they put something out for the N5 or N6.
---------- Post added at 07:20 PM ---------- Previous post was at 07:19 PM ----------
CraZY_BoY^ said:
You cant port different version of Android by drag-and-droping system folders.
Click to expand...
Click to collapse
Ha, no.
CraZY_BoY^ said:
You cant port different version of Android by drag-and-droping system folders.
Click to expand...
Click to collapse
This
Sent from my X9006 using XDA Free mobile app
CraZY_BoY^ said:
You cant port different version of Android by drag-and-droping system folders.
Click to expand...
Click to collapse
suraj.das said:
This
Click to expand...
Click to collapse
Yes, this is not what they're doing. That would be idiotic. They're trying to port it.
Alzoids said:
Yes, this is not what they're doing. That would be idiotic. They're trying to port it.
Click to expand...
Click to collapse
Check the link the OP has used to port. It's exactly what he's doing!
You need more skills than that to accomplish this!
TiVON said:
Check the link the OP has used to port. It's exactly what he's doing!
You need more skills than that to accomplish this!
Click to expand...
Click to collapse
Should have included a "/s" I guess.
Sorry man, but when you are making this big of a switch. Especially different device AND different version of android, there is more that the drag and drop tutorial to this. You actually need to know the languages its developed is so you can find what's wrong with it and in turn, you can create your own fix. (Simple terms here)
Basically, you need to be able to write a compliant device tree and kernel that can compile with the new source.
TiVON said:
Check the link the OP has used to port. It's exactly what he's doing!
You need more skills than that to accomplish this!
Click to expand...
Click to collapse
sorry to go off topic but your DP suits the situation lol
Building A Kernel For A6k
Hello Folks, Looks like A6000 Forums Are On Fire So Now I AM HErE TO POuR Oil In The FIRE
Lets Get Straight To The POint
This Guide Will Help you build a kernel for our little Precious One
Requirements:
Ubuntu[DOnt Ask How]
Required Libs like libncurses, and stuff [If you face any such error realted to libs, just google Once]
Good Internet
AT least 2GB RAM and a good processor
A bit of your time
Patience and brain
Steps:
1) Create A folder anywhere with any name you want and open it
2) Open terminal in that folder and Run This COmmand Which will install all required Libs
Code:
sudo apt-get install -y build-essential kernel-package libncurses5-dev bzip2
3)After It gets done now we need a toolchain so now type " mkdir kernel" and "cd kernel" without quotes
4) Now we will dload toolchain so first install GIT and GCC libs for ex
"sudo apt get-install git"
Now Run This to clone the toolchain
Code:
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8
5)After toolchain gets downloaded now we need kernel sources, to simplify it clone the sources from my GIT using this command in terminal
Code:
git clone https://github.com/varunhardgamer/kernel_lenovo_a6000.git
6)After Dloading kernel sources open the kernel sources folder which may have name Semar Kernel or something like that and open BuildingKernel.txt and understand the way you need to edit Build.sh
Its not hard you just need to type the address to your kernel folder which you made
7)Now type
Code:
make ARCH=arm
and press enter
8)Then RUn
Code:
make wt86518_defconfig
9)THen Run
Code:
make menuconfig
and a popup will appear showing you all the tweaks that can be included in the kernel, select accordingly and save it
10)After you Finish tweaking it, open build.sh and edit it acordingly and then run the script by " .build.sh " in the terminal and wait till you get the zimage which is the kernel
8)Now download semar kernel r5zip and push your zimage inside it and flash your first Kernel
COmment here if you face any Errrors
Kernel Source _ https://github.com/varunhardgamer/kernel_lenovo_a6000
Credits to-
Me
Mr.AW
@3lambda
Orata
@mshoaib7
@dev_harsh1998
and XDA Forums
Reserved
Link To the original Thread
https://forum.xda-developers.com/android/software/guide-easy-kernel-building-tutorial-t3581057
Thanks To @3lambda
[Really THanks Man]
Just In Case
DualBoot Coming Soon By The WAy
The MErc With A MouTh is Back
The source you have mentioned isnt the proper source for Kernel and is Limpy when it comes to New stuff support better you link them to this repo :- https://github.com/dev-harsh1998/android_kernel_lenovo_msm8916
and GCC-4.7 is old and has regression bugs Better use gcc-4.8
Regards,
dev_harsh1998
dev_harsh1998 said:
The source you have mentioned isnt the proper source for Kernel and is Limpy when it comes to New stuff support better you link them to this repo :- https://github.com/dev-harsh1998/android_kernel_lenovo_msm8916
and GCC-4.7 is old and has regression bugs Better use gcc-4.8
Regards,
dev_harsh1998
Click to expand...
Click to collapse
Ok but the build.sh that i have mentioned will have to be edited again
Oh man
OK wait
Some Modifications To the guide will be done by tomorrow
No worries you doing good work
dev_harsh1998 said:
No worries you doing good work
Click to expand...
Click to collapse
Thanks Limit DOne
WIll thanks Tomorrow
You need to edit build.sh
Change -j64 to -j4 or it'll mess up for everyone.
---------- Post added at 05:02 PM ---------- Previous post was at 05:02 PM ----------
dev_harsh1998 said:
The source you have mentioned isnt the proper source for Kernel and is Limpy when it comes to New stuff support better you link them to this repo :- https://github.com/dev-harsh1998/android_kernel_lenovo_msm8916
and GCC-4.7 is old and has regression bugs Better use gcc-4.8
Regards,
dev_harsh1998
Click to expand...
Click to collapse
+1
Use this kernel it's updated nd better.
Has.007 said:
You need to edit build.sh
Change -j64 to -j4 or it'll mess up for everyone.
---------- Post added at 05:02 PM ---------- Previous post was at 05:02 PM ----------
+1
Use this kernel it's updated nd better.
Click to expand...
Click to collapse
Oh Thanks for pointing that 64 out:good:
Thanks
The Hard Gamer said:
Oh Thanks for pointing that 64 out:good:
Thanks
Click to expand...
Click to collapse
Welcome. Keep up the good work. :good:
Lol, just rechecked your git.
The kernel will not compile. You need to define the toolchain.
Has.007 said:
Lol, just rechecked your git.
The kernel will not compile. You need to define the toolchain.
Click to expand...
Click to collapse
I myself used this method and compiled a kernel
And for toolchain
I already mentioned
export cross_compile in .sh
The Hard Gamer said:
I myself used this method and compiled a kernel
And for toolchain
I already mentioned
export cross_compile in .sh
Click to expand...
Click to collapse
bad command practise..
is it work for any version of Android? currently I'm using RR 5.8.2
hayatnas18 said:
is it work for any version of Android? currently I'm using RR 5.8.2
Click to expand...
Click to collapse
Wait till i update the guide again