Related
Hello everyone!
I present to you a paranoid android 3.99 port for our Xperia SP
Changelog:
V2: Device no longer hard reboots on bootanimation
V1: initial release
BUGS:
V2: Device doesn't boot (stuck on bootanimation and ADB offline)
V1: Device doesn't boot (hard reboot after 10 seconds of showing splash screen)
Download: PA_HUASHAN_V2
Now as you can see this ROM port is not booting but at least it doesn't do a hard reboot anymore! Currently I have no ADB access as it is listed as offline when doing: ADB devices of course I can't figure out the problem myself so I'm asking you guys for help. Since there is no logcat I know that it might be nasty to determine the problem and where the phone stops booting. I hope you guys can help me get this ROM to boot so we will finally have a working PA rom
thanks to: @-NickHalden- for his nice guide on how to port ROM's
@FXP for the base rom (cm10.2)
and the paranoid android team for the ROM that was ported (pa 3.99 from nexus 4)
Why don't you simply build from source?
kamarush said:
Why don't you simply build from source?
Click to expand...
Click to collapse
I'm trying that as well but i'm having some issues getting these files working
<device>.adds
<device>.removes
pa_<device>.conf
pa_<device>.mk
If I could easily get/make these files a source build would already be here
Do you have a idea on how to create these files? or where I can get them?
for example for the .adds file I need something like this (this comes from nexus 4)
https://github.com/ParanoidAndroid/android_vendor_pa/blob/jb43/manifests/mako.adds
It's pretty simple
Adds and removes are the repos what you need and don't need. About the makefiles. You can simple use the mako files as base, only need to change the values to match for our device.
kamarush said:
It's pretty simple
Adds and removes are the repos what you need and don't need. About the makefiles. You can simple use the mako files as base, only need to change the values to match for our device.
Click to expand...
Click to collapse
OK this is the .adds file I just made can you take a look at it?
huashan.adds
kamarush said:
Why don't you simply build from source?
Click to expand...
Click to collapse
A long ago, i dont have see you on xda....
now you've back....great master
OK guys PA is currently building from source! now let's prepare to wait a long time xD
noahvt said:
OK this is the .adds file I just made can you take a look at it?
huashan.adds
Click to expand...
Click to collapse
This file will be almost the same as the cm dependencies. So this isn't good.
Levered said:
A long ago, i dont have see you on xda....
now you've back....great master
Click to expand...
Click to collapse
Yeah was long time ago i just bought this device a week ago. I just came back to Sony from Samsung
noahvt said:
OK guys PA is currently building from source! now let's prepare to wait a long time xD
Click to expand...
Click to collapse
@kamarush
damn I ran into some building issues already (hopefully nothing to serious)
Lunching device
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
Device huashan not found. Attempting to retrieve device repository from ParanoidAndroid Github (http://github.com/ParanoidAndroid).
Repository for huashan not found in the ParanoidAndroid Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
** Don't have a product spec for: 'pa_huashan'
** Do you have the right repo manifest?
i'll upload my "pa_huashan.mk" file: https://mega.co.nz/#!gZESjTKQ!ESlhCwWQROoh53SFYJ5vqyA177o5jqZdy9V688BWUNs
EDIT: I modified my huashan.adds file
EDIT2: I really needs some help with this! I'm familiar with the compiling process of cyanogenmod but this is a whole new story
I'm a huge fan of PA, I hope this one for our SP will progress nicely. Keep up the good work devs. Currently on CM coz stock is too laggy on my one.
Tapatalked from my Xperia P
noahvt said:
@kamarush
damn I ran into some building issues already (hopefully nothing to serious)
Lunching device
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
Device huashan not found. Attempting to retrieve device repository from ParanoidAndroid Github (http://github.com/ParanoidAndroid).
Repository for huashan not found in the ParanoidAndroid Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
** Don't have a product spec for: 'pa_huashan'
** Do you have the right repo manifest?
i'll upload my "pa_huashan.mk" file: https://mega.co.nz/#!gZESjTKQ!ESlhCwWQROoh53SFYJ5vqyA177o5jqZdy9V688BWUNs
EDIT: I modified my huashan.adds file
EDIT2: I really needs some help with this! I'm familiar with the compiling process of cyanogenmod but this is a whole new story
Click to expand...
Click to collapse
Just need to update/add pa_huashan to the pa vendor makefiles.
@kamarush
Remember you in developing the Xperia line 2011. Glad to see it with our Xperia SP. Some project in mind?
[QOUTE]Yeah was long time ago i just bought this device a week ago. I just came back to Sony from Samsung [/QUOTE]
Great, i really want rom by you. i hope you can make it soon..:good:
OK guys the build has started again! All my previous problems were caused by syncing the old repo (github.com/paranoidandroid) instead of the new one (github.com/AOSPA-legacy) if you get errors like I did try and use the new source (repo init -u git://github.com/AOSPA-legacy/manifest.git -b kitkat)
Just letting you guys know that this project isn't dead
noahvt said:
OK guys the build has started again! All my previous problems were caused by syncing the old repo (github.com/paranoidandroid) instead of the new one (github.com/AOSPA-legacy) if you get errors like I did try and use the new source (repo init -u git://github.com/AOSPA-legacy/manifest.git -b kitkat)
Just letting you guys know that this project isn't dead
Click to expand...
Click to collapse
When you port AOSPA to unlocked Bl's, could you make a version for locked BL's?
MrSteve555 said:
When you port AOSPA to unlocked Bl's, could you make a version for locked BL's?
Click to expand...
Click to collapse
I'm already using the locked bootloader vendor blobs
Sent from my C5303 using XDA Free mobile app
noahvt said:
I'm already using the locked bootloader vendor blobs
Sent from my C5303 using XDA Free mobile app
Click to expand...
Click to collapse
That's really good. :thumbsup: One last question, why aren't you porting the latest PA(4+)?
MrSteve555 said:
That's really good. :thumbsup: One last question, why aren't you porting the latest PA(4+)?
Click to expand...
Click to collapse
I am now! I forgot to tell you that the version updated this ROM will now be 4.4.2 kitkat!
@kamarush still getting product name not defined but build started! I'll finish it tomorrow
Sent from my C5303 using XDA Free mobile app
noahvt said:
I am now! I forgot to tell you that the version updated this ROM will now be 4.4.2 kitkat!
@kamarush still getting product name not defined but build started! I'll finish it tomorrow
Sent from my C5303 using XDA Free mobile app
Click to expand...
Click to collapse
It's really good! If you finish the build tomorrow, I'll flash it right away . I loved PA on my N7, and I think it's the one of the best ROM's on xda. Hopefully PA won't have that annoying freeze bug.
MrSteve555 said:
It's really good! If you finish the build tomorrow, I'll flash it right away . I loved PA on my N7, and I think it's the one of the best ROM's on xda. Hopefully PA won't have that annoying freeze bug.
Click to expand...
Click to collapse
Unfortunately it probably will have the freeze bug as it's based on the vendor blobs that bagyusz uses
Sent from my C5303 using XDA Free mobile app
Hi folks,
I just started to port UbuntuTouch for the Sony Xperia Z Ultra and I think I should have a *.zip ready for testing in 2 weeks.
Until then, I will use this thread as a scrap book to document all the troubles I run into, all the things that needed my special attention and fixes that are not that obvious. I hope there will be some fellas brave enough to test everything and report back or even to join me with the development.
Best regards,
Kalle
First Update:
I found that the Ubuntu Touch version that ist based on CyanogenMod was not updated to a more recent version. This means that I have to either look into AOSP or backport everything to CM-10.1. I think backporting is kinda stupid because newer we are writing new software to improve things. Sadly I don't have much experiance with AOSP so I will have to find out how everything works and what the differences to CyanogenMod are.
The good news is, that I'm catching up with the mailing list, which means I'll have a place to call for help.
Also I'm in the progress to start a git repo, but I'm unsure what I will need to add, maybe some common stuff from sony does not need to be changed.
So long,
Kalle
Update!
There is a new porting guide! See here
I already freed some space for it and ordered a bit more ram so after my exam next week, I'll pick this up/Start all over.
Hope you are as excited as I am,
Kalle
XDA:DevDB Information
Ubuntu Touch for Sony Xperia Z Ultra, ROM for the Sony Xperia Z Ultra
Contributors
KalleEatingBrain, Kohelet
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Testing
Created 2014-05-14
Last Updated 2015-02-24
freaking awesome!
freaking awesome!
i would like to test. maybe i can help with developing/porting
Thank you for your efforts. I will test if needed.
Sent from my C6806 using XDA Premium 4 mobile app
Great this would be awesome if you can make it happen. I'm here for testing if required.
Sent from my C6833 using XDA Premium 4 mobile app
In also here for testing... Ubuntu Touch has intruiged me, I would love to try it out.
Thx... (thread bookmarked)
Sent from my C6833 using Tapatalk
I keep meaning to reply to this thread... Thanks for putting the effort in to get this working. If you want any hints/tips etc from my experience in getting slim and carbon built for the ZU just ask, I'll be willing to test aswell
iBuzman said:
Thx... (thread bookmarked)
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
+1
Nice.ill be watching out everyday
Sent from my C6833 using XDA Premium 4 mobile app
blueether said:
I keep meaning to reply to this thread... Thanks for putting the effort in to get this working. If you want any hints/tips etc from my experience in getting slim and carbon built for the ZU just ask, I'll be willing to test aswell
Click to expand...
Click to collapse
Cool, thanks can you give me a hint on how to deal with new targets in Aosp? I mean setting up the files in a way "lunch" is able to find the right target.
Sent from my C6833 using XDA Free mobile app
vendersetup.sh file in vender/ might be what you are looking for?
have a gander at this http://www.kandroid.org/online-pdk/guide/build_new_device.html
How are you doing on this? I've just started working on this as well and am curious to know how far along you've gotten/what issues you've run into.
Sent from my Nexus 7 using XDA Free mobile app
So I've gotten the build to start, but I'm running into issues with libhybris:
ubuntu/hybris/compat/media/media_codec_layer.cpp:51:40: fatal error: gui/IGraphicBufferProducer.h: No such file or directory
compilation terminated.
make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libmedia_compat_layer_intermediates/media_codec_layer.o] Error
I'll post here once I've found a solution.
Kohelet said:
So I've gotten the build to start, but I'm running into issues with libhybris:
ubuntu/hybris/compat/media/media_codec_layer.cpp:51:40: fatal error: gui/IGraphicBufferProducer.h: No such file or directory
compilation terminated.
make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libmedia_compat_layer_intermediates/media_codec_layer.o] Error
I'll post here once I've found a solution.
Click to expand...
Click to collapse
Yeah, thats as far as I got, too. :-/ I tried removing all different libs or compiling different parts and leaving others out but I couldn't get any futher. Also I saw your post to the mailing list but it seems like you wont get a helpful reply either. As far a I could track this problem is the incompatibility of togari CM-11 and the ubuntu AOSP source tree. On xda-university there is a guide for porting from CM to AOSP which I will try but maybe you should take a look, too. Anyways: Great to see there is someone else except lazy me working on this.
Best regards,
Kalle
KalleEatingBrain said:
Yeah, thats as far as I got, too. :-/ I tried removing all different libs or compiling different parts and leaving others out but I couldn't get any futher. Also I saw your post to the mailing list but it seems like you wont get a helpful reply either. As far a I could track this problem is the incompatibility of togari CM-11 and the ubuntu AOSP source tree. On xda-university there is a guide for porting from CM to AOSP which I will try but maybe you should take a look, too. Anyways: Great to see there is someone else except lazy me working on this.
Best regards,
Kalle
Click to expand...
Click to collapse
I actually got past the libhybris issue. The problem was that the porting guide is out of date. It's based on using cm-10.1 whereas the current source for Ubuntu is based on cm-11.0. So if you use 4.4.2 instead instead of 4.2.2 then it works. But there are so many other issues and the documentation for fixing them is so poor. I've kept a running list of problems I've come across and the solutions for them (it's below).
Also they dropped the whole UCM thing so you should be able to get sound working once you actually get a working build, but I couldn't get it to build. The error that is currently in my way has to do with "No rule to make target signapk.jar needed by com.qualcomm.location" or something or other. And I found nothing on how to solve that online.
At this point I've decided to take a short break from the whole thing because it's so frustrating.
Once I get motivated to work on it again, I'll probably start from scratch.
Issues List (I apologize for not being specific about the errors, I didn't write them down verbatim):
If you get an error about libelf you need to add CyanogenMod/android_external_elfutils to your local_manifests/roomservice.xml and also add external/elfutils under subdirs in build/core/main.mk
Don't forget to also add device/sony and vendor/sony to build/core/main.mk as well.
The build will complain about not having a rule to make android-boot.img. To fix you have to go to device/sony/fusion3-common/custombookimg.mk and change boot.img to android-boot.img. You need to make the same change in device/sony/rhine-common/custombootimg.mk
I got an error about android.hardware.bluetooth_le.xml. If you just restart the build it doesn't complain, but I didn't find a proper solution to that.
If you get the libhybris error you have the wrong version of the Ubuntu source. Make sure you're using 4.4.2 when you phablet-dev-botstrap. It should be phablet-dev-bootstrap --sources aosp --repo-branch phablet-4.4.2_r1 [target_directory]
You might get an error about a product_config.mk and how it's missing a makefile for togari. You have to make sure that in device/sony/togari Android.mk, cm.mk, full_togari.mk, and vendorsetup.sh PRODUCT_NAME is the same. I solved this by changing PRODUCT_NAME to cm_togari in all of them and then renamed full_togari.mk to cm_togari.mk
You might get an error like MODULE.TARGET.SHARED_LIBRARIES.libOmxCore already defined in hardware/qcom/media. You should have CyanogenMod/android_hardware_qcom_media-caf-new in your repo manifest with a path of android/qcom/media-caf-new so you can safely rm -rf the hardware/qcom/media directory to get past this error.
If you get an error about dtbToolCM, add /device/qcom/common/dtbtool to your subdirs in build/core/main.mk
You may get an error about mkbootimg, that's because Sony uses a different version of mkbootimg. The only option I found was to download it from the internet (Thanks DooMLorD!). Once you get that version edit device/sony/rhine-common/custombootimg.mk and replace $(MKBOOTIMG) with the path to your downloaded mkbootimg binary.
You might get an error about no rule to make target something/something/signapk.jar needed by something/something/com.qualcomm.location. I didn't find a solution to this error.
Click to expand...
Click to collapse
Thanks for that list, it's sure to help some one. I think I have had most of those errors in trying to get aosp to build.
Can I copy those errors to my [DEV]Random thoughts thread?
blueether said:
Thanks for that list, it's sure to help some one. I think I have had most of those errors in trying to get aosp to build.
Can I copy those errors to my [DEV]Random thoughts thread?
Click to expand...
Click to collapse
Sure, feel free. I built CM for all my devices and regretted not keeping such a list when I did that. So now every time I work on a build I keep lists like that. Eventually, when I have a working build, I'll post a guide for how to build following the same steps I took.
Kohelet said:
Sure, feel free. I built CM for all my devices and regretted not keeping such a list when I did that. So now every time I work on a build I keep lists like that. Eventually, when I have a working build, I'll post a guide for how to build following the same steps I took.
Click to expand...
Click to collapse
Yeh carbon and slim were easy to build, and simple fixes. AOSP on the other hand I wish I had kept a build log
Ah nice, when I last checked CM-11.0 was not working with the 4.4.2r2 branch. I think I know how to fix the problem with the *.apk. Basically you have to remove all java dependencies from all the makefiles. I will look it up, so I can tell you what to grep for. Do you have a git repo we can work on, or should I add you to mine (which is just a fork of the CM-repos)? I will take a look at the sound in the next days. Thanks for you list!
Keep it up,
Kalle
Sent from my C6833 using XDA Free mobile app
KalleEatingBrain said:
Ah nice, when I last checked CM-11.0 was not working with the 4.4.2r2 branch.
Click to expand...
Click to collapse
That could potentially be a major source of my problems. i wasn't aware of that.
I think I know how to fix the problem with the *.apk. Basically you have to remove all java dependencies from all the makefiles. I will look it up, so I can tell you what to grep for. Do you have a git repo we can work on, or should I add you to mine (which is just a fork of the CM-repos)? I will take a look at the sound in the next days. Thanks for you list!
Keep it up,
Kalle
Sent from my C6833 using XDA Free mobile app
Click to expand...
Click to collapse
All I have at the moment is a fork of the CM repos. Feel free to add me to your repo. My username on Github is Kohelet as well. I can start to look into removing java dependencies as well.
As for the sound, the mailing list made it appear as if it was a simple matter of running
Code:
$ sudo apt-add-repository ppa:ci-train-ppa-service/landing-018
$ sudo apt-get update
$ sudo apt-get dist-upgrade
$ sudo apt-get install pulseaudio-module-droid
I could be wrong though.
Building a sweet treat for you guys, will post it in dev section assuming all goes well
Can you post link here as well when its ready?
jontr said:
Can you post link here as well when its ready?
Click to expand...
Click to collapse
sure
Wow! Excited to breathe some new life into the old manta.
Has it been two hours yet??!?!?!
I guess all didn't go too well...
how to farm upvotes this isn't reddit guys
wturner859 said:
I guess all didn't go too well...
Click to expand...
Click to collapse
Had some java issues, will be def ready tomorrow :good:
sooti said:
Had some java issues, will be def ready tomorrow :good:
Click to expand...
Click to collapse
Bad news... buillt fine, flashed it, no boot, i think our device needs a new bootloader, unless someone else has an idea? tried both otapackage and img files
sooti said:
Bad news... buillt fine, flashed it, no boot, i think our device needs a new bootloader, unless someone else has an idea? tried both otapackage and img files
Click to expand...
Click to collapse
What are you trying to build? I built Lollipop from the r2 repo a few days ago, available here: http://d-h.st/Ryr
stiggy2012 said:
What are you trying to build? I built Lollipop from the r2 repo a few days ago, available here: http://d-h.st/Ryr
Click to expand...
Click to collapse
Same here, but my device doesn't boot, is it working for you???
sooti said:
Same here, but my device doesn't boot, is it working for you???
Click to expand...
Click to collapse
Yep, works fine. Build with the latest "preview binaries". Literally all I did was repo init/sync, load the variables, run the binary scripts, chose manta with lunch and then finally run make.
stiggy2012 said:
Yep, works fine. Build with the latest "preview binaries". Literally all I did was repo init/sync, load the variables, run the binary scripts, chose manta with lunch and then finally run make.
Click to expand...
Click to collapse
Preview binaries? that must be what I am missing... anyway if you already built one no point in duplicating work, good job, ill get back to building for my G3-D855
sooti said:
Preview binaries? that must be what I am missing... anyway if you already built one no point in duplicating work, good job, ill get back to building for my G3-D855
Click to expand...
Click to collapse
Yep, these: https://developers.google.com/android/nexus/blobs-preview
I suspect that will be much, MUCH more difficult than a Manta build! Tell you what though: If you do manage to get it going well I may well buy a G3 myself as the hardware is gorgeous and they are quite cheap nowadays... Only thing that puts me off is LG's update record and (until recently) the locked bootloader
stiggy2012 said:
Yep, these: https://developers.google.com/android/nexus/blobs-preview
I suspect that will be much, MUCH more difficult than a Manta build! Tell you what though: If you do manage to get it going well I may well buy a G3 myself as the hardware is gorgeous and they are quite cheap nowadays... Only thing that puts me off is LG's update record and (until recently) the locked bootloader
Click to expand...
Click to collapse
Got mine booting pac-rom with everything working just fine, some minor issues like camera getting stuck in background sometimes but nothing major
stiggy2012 said:
Yep, works fine. Build with the latest "preview binaries". Literally all I did was repo init/sync, load the variables, run the binary scripts, chose manta with lunch and then finally run make.
Click to expand...
Click to collapse
Hi, how is it to load the variables? I tried to build lollipop for manta and I did all that you said but I don't remember that step.
tavocabe said:
Hi, how is it to load the variables? I tried to build lollipop for manta and I did all that you said but I don't remember that step.
Click to expand...
Click to collapse
"source build/envsetup.sh" from build directory.
https://source.android.com/source/building-running.html
stiggy2012 said:
"source build/envsetup.sh" from build directory.
https://source.android.com/source/building-running.html
Click to expand...
Click to collapse
OH, yeah I remember that. Didn't know the initialization/setup of the environment was actually loading the variables. Thanks!
Oh so this is the show off thread?
Well I built mine with transparent bars via linaro toolchain
Seriously though this isn't reddit...
This thread is NOT for general Q & A about using the kernel or configuring a specific version.
This thread IS for sharing source code or attempting to apply debugging to code changes.
In English: This is what a development thread really looks like. No downloads, No user manual.
Note to Mods: OT is welcome, so long as it is relevant to the kernel developer experience
Building the kernel 101:
A clean branch with only the build tools, ramdisks, and MacOS updates is at:
https://github.com/StarKissed/starkissed-kernel-trlte/tree/master
The stockish branch adds Linux patches, mainline updates, and SELinux mods
The deported branch is the customized version described in the OP feature list
You are going to need a few things, especially if building this kernel for MacOS.
GCC 4.7 (This is the version Samsung's documentation listed)
An updated mkbootimg (Must have DTS support)
A dtbtool (Included in the source, but only for Linux)
Insomnia (Not a requirement, but it will help you in the long run)
For MacOS, the tools are available from the following repositories:
https://github.com/StarKissed/android-toolchain-eabi-4.7
https://github.com/StarKissed/starkissed-build-tools
Let's jump ahead a moment for those of you who have built kernels and notice your boot.img is only around 11 MB while the versions you see listed here are all roughly 14 MB. This is where the new mkbootimg and dtbtool are necessary.
Attempting to retrieve the commandline arguments from the boot.img will not tell you one important piece:
Code:
./dtbtool -o dt.img -s 4096 -p ../scripts/dtc/ ../arch/arm/boot/dts/
chmod a+r dt.img
mkbootfs (ramdisk creation)
mkbootimg (mkbootimg params) --dt dt.img
This takes the DTSI that was built into a dtb as one of the first steps in the compile process and turns it into an image that is appended to the end of the boot.img. The dt.img just happens to be about 3 MB. (11 MB + 3 MB = 14 MB)
If you grabbed the original Samsung kernel source, you may notice that their default compile script directs the build to an "out" folder in the root of the kernel directory.
The obvious advantage to this is that their clean command runs into some errors, so the clean process is simply deleting the "out" folder and making a new one.
This doesn't work for a lot of the custom components you may want to add to your kernel, though. Some modifications, such as intelli-thermal, rely on a subdirectory that is referenced in the Makefile.
Building to this out folder will result in an error because it cannot find the output of that component, but building in the tree, or actual source, will also result in an error. The lesser of two evils is to fix in-tree builds.
Code:
Instructions for TRACE_INCLUDE_FILE in include/trace/define_trace.h say
"the path is relative to define_trace.h, not the file including it".
Fix in-tree compilation by making the path relative to define_trace.h.
What this means is that when you have a line that refers to the TRACE_INCLUDE_PATH or an include reference to a file that uses a relative location instead of a global, these need to be updated
The only two files that currently require updates in the stock source code are
Code:
drivers/scsi/ufs/ufs_test.c
#include -> #include "../sd.h"
and
Code:
drivers/video/msm/mdss/mdss_mdp_trace.h
#define TRACE_INCLUDE_PATH . -> #define TRACE_INCLUDE_PATH ../../drivers/video/msm/mdss/
If you want to be able to debug your kernel, you will need to enable last_kmsg.
Open up the arch/arm/configs/apq8084_sec_defconfig and add
Code:
CONFIG_SEC_DEBUG_NOCACHE_LOG_IN_LEVEL_LOW=y
CONFIG_PRINTK_PROCESS=y
CONFIG_SEC_DEBUG_LOW_LOG=y
More to come soon...
This is a great idea!
Looking fwd to seeing this thread take off...it will be very interesting for sure.
Sent from my SM-N910W8 using Tapatalk 2
@ktoonsez im back ready to play my man
@twistedumbrella my man i hope i dont become a ball buster on this thread but i have the 1st 2 questions on this thread:
1. How do you patch your kernels? (i use the p1 command.. is there another way?)
2. How did you manage to make the OC values show?
Disclaimer: I may have a lot of follow up questions
friedrich420 said:
@ktoonsez im back ready to play my man
@twistedumbrella my man i hope i dont become a ball buster on this thread but i have the 1st 2 questions on this thread:
1. How do you patch your kernels? (i use the p1 command.. is there another way?)
2. How did you manage to make the OC values show?
Disclaimer: I may have a lot of follow up questions
Click to expand...
Click to collapse
I use git am -3 so that any issue defaults to a merge then git mergetool to resolve it.
Switching the index in the dtsi that was modified was the only change to show it that I remember needing.
https://github.com/StarKissed/stark...mmit/695abe187620acf513b33237042925d60a99f0c1
friedrich420 said:
@ktoonsez im back ready to play my man
@twistedumbrella my man i hope i dont become a ball buster on this thread but i have the 1st 2 questions on this thread:
1. How do you patch your kernels? (i use the p1 command.. is there another way?)
2. How did you manage to make the OC values show?
Disclaimer: I may have a lot of follow up questions
Click to expand...
Click to collapse
Im back too.
ktoonsez said:
Im back too.
Click to expand...
Click to collapse
right on
any thoughts my man?
friedrich420 said:
right on
any thoughts my man?
Click to expand...
Click to collapse
Im in the process of just starting over from the "F" source and looking for testers on INTL thread. I wish I didnt have to start over but looks like Im going to have to
ktoonsez said:
Im in the process of just starting over from the "F" source and looking for testers on INTL thread. I wish I didnt have to start over but looks like Im going to have to
Click to expand...
Click to collapse
we know for sure that your source without bfq works fine... now its a matter of figuring out what of all the additions from yesterday's source to today's source caused the bootloop..
friedrich420 said:
we know for sure that your source without bfq works fine... now its a matter of figuring out what of all the additions from yesterday's source to today's source caused the bootloop..
Click to expand...
Click to collapse
I wonder if its any of the top 4 commits from here:
https://github.com/ktoonsez/KTNOTE4/commits/tw4.4?page=2
ktoonsez said:
I wonder if its any of the top 4 commits from here:
https://github.com/ktoonsez/KTNOTE4/commits/tw4.4?page=2
Click to expand...
Click to collapse
give me a little bit of time and ill revert it manually and compile again the one i compiled in the afternoon (your morning)
I got lost in Freedom Wars for a bit. I need to figure out an issue with thermal then I'll be back
friedrich420 said:
give me a little bit of time and ill revert it manually and compile again the one i compiled in the afternoon (your morning)
Click to expand...
Click to collapse
Here is a test one starting all over again, just has OC and Voltage control:
http://ktoonsez.jonathanjsimon.com/note4/TW/KT-NOTE4-KK4.4-TW-N910-11.13.2014D.zip
ktoonsez said:
Here is a test one starting all over again, just has OC and Voltage control:
http://ktoonsez.jonathanjsimon.com/note4/TW/KT-NOTE4-KK4.4-TW-N910-11.13.2014D.zip
Click to expand...
Click to collapse
Unfortunately same bahavior my man..
friedrich420 said:
Unfortunately same bahavior my man..
Click to expand...
Click to collapse
LOL, really? I just had 3 people boot up successfully, finally. You have the "F" or the "G"?
EDIT:
The guy I am testing with has the "G".
ktoonsez said:
LOL, really? I just had 3 people boot up successfully, finally. You have the "F" or the "G"?
Click to expand...
Click to collapse
the F...
friedrich420 said:
the F...
Click to expand...
Click to collapse
Just edited my post above, the guy that is answering me quick has the "G". Now Im really getting PISSED!!!!!!!!!! WTH!!
ktoonsez said:
Just edited my post above, the guy that is answering me quick has the "G". Now Im really getting PISSED!!!!!!!!!! WTH!!
Click to expand...
Click to collapse
Did anyone diff the ramdisk? If not, I can throw the two in git and see if anything lights up. I have the visual editor for Mac for exactly that.
ktoonsez said:
Just edited my post above, the guy that is answering me quick has the "G". Now Im really getting PISSED!!!!!!!!!! WTH!!
Click to expand...
Click to collapse
this may or may not confuse you more...
i made a test git repository : https://github.com/friedrich420/Note4-AEL-Kernel2
all i did was cherry pick your oc and voltage control commits..
It booted im running it @2.99ghz right now and its fine...
Could it be that you need the F source my man?
twistedumbrella said:
Did anyone diff the ramdisk? If not, I can throw the two in git and see if anything lights up. I have the visual editor for Mac for exactly that.
Click to expand...
Click to collapse
I started with stock N910F ramdisk in version "C", version "D" went back to my original universal ramdisk you can try the "C" and see if anything changes:
http://ktoonsez.jonathanjsimon.com/note4/TW/KT-NOTE4-KK4.4-TW-N910-11.13.2014C.zip
friedrich420 said:
this may or may not confuse you more...
i made a test git repository : https://github.com/friedrich420/Note4-AEL-Kernel2
all i did was cherry pick your oc and voltage control commits..
It booted im running it @2.99ghz right now and its fine...
Could it be that you need the F source my man?
Click to expand...
Click to collapse
That is exactly what I just merged in so the "D" that wont boot for you is pretty much the same thing, lol. See what happens on the "C" version which is stock N910F ramdisk.
I tried compile kernel for XRN3 Mtk
And terminal displayed this
make: *** No rule to make target '/home/Android/kernel/kernel-3.10/drivers/misc/mediatek/mach///dct/dct/codegen.dws', needed by '/home/Android/kernel/kernel-3.10/drivers/misc/mediatek/mach///dct/dct/inc/cust_kpd.h'. Stop.
I disabled needed line in defconfig, but it still not compiling
Sorry for my bad English
What can i do with that error?
Skrem339 said:
I tried compile kernel for XRN3 Mtk
And terminal displayed this
make: *** No rule to make target '/home/Android/kernel/kernel-3.10/drivers/misc/mediatek/mach///dct/dct/codegen.dws', needed by '/home/Android/kernel/kernel-3.10/drivers/misc/mediatek/mach///dct/dct/inc/cust_kpd.h'. Stop.
I disabled needed line in defconfig, but it still not compiling
Sorry for my bad English
What can i do with that error?
Click to expand...
Click to collapse
check if this file already exicst in ur kernel source or not
messi2050 said:
check if this file already exicst in ur kernel source or not
Click to expand...
Click to collapse
I am also facing the same error
can you explain the solution.
kalwardin said:
I am also facing the same error
can you explain the solution.
Click to expand...
Click to collapse
Which device are you compiling for and can you link the kernel source
messi2050 said:
Which device are you compiling for and can you link the kernel source
Click to expand...
Click to collapse
Lenovo Tab 2 A7 10 F
and the kernel source is https://github.com/KalWardinX/kernel_lenovo_tab2a710f
I m trying to port postmarketos but while building kernel i am getting this error:
'No rule to make target /home/pmos/ build/src/kernel_lenovo_tab2a710f-91effce241038f11 4faae5f80e19a94c810185e9/drivers/misc/mediatek/ mach//dct/dct/codegen.dws,
needed by
/home/ pmos/build/srckernel_lenovo_tab2a710f-91effce2410 38f114faae5f80e19a94c810185e9/out/drivers/misc/ mediatek/mach///dct/dct/inc/cust_kpd.h. Stop.
Please Help
I am stuck in this part since 5 days. :crying:
kalwardin said:
Lenovo Tab 2 A7 10 F
and the kernel source is https://github.com/KalWardinX/kernel_lenovo_tab2a710f
I m trying to port postmarketos but while building kernel i am getting this error:
'No rule to make target /home/pmos/ build/src/kernel_lenovo_tab2a710f-91effce241038f11 4faae5f80e19a94c810185e9/drivers/misc/mediatek/ mach//dct/dct/codegen.dws,
needed by
/home/ pmos/build/srckernel_lenovo_tab2a710f-91effce2410 38f114faae5f80e19a94c810185e9/out/drivers/misc/ mediatek/mach///dct/dct/inc/cust_kpd.h. Stop.
Please Help
I am stuck in this part since 5 days. :crying:
Click to expand...
Click to collapse
Well the cpu is mtk with old 3.10 kernel version, i would suggest to use a prebuilt kernel as this problem is probably related to the used toolchain to compile so if you are porting a rom with the same android version of the stock rom this will be the best solution for you, if it's a newer version you will need to upstream the kernel and apply necessary patches for the target new android version and call the correct toolchain.
messi2050 said:
Well the cpu is mtk with old 3.10 kernel version, i would suggest to use a prebuilt kernel as this problem is probably related to the used toolchain to compile so if you are porting a rom with the same android version of the stock rom this will be the best solution for you, if it's a newer version you will need to upstream the kernel and apply necessary patches for the target new android version and call the correct toolchain.
Click to expand...
Click to collapse
Thanks
I will try that