By KitKat update for xt897/asanti being canceled, we're missing at least:
updated bootladers (sbl1,sbl2,sbl3 and appsboot), updated trustzone (not sure if that is an issue at this point), updated modem firmware.
Fortunately, at least the device tree for asanti seems to be ready and working fine, apart from not being handled by JB bootloader.
As a base, I'm using https://github.com/CyanogenMod/android_kernel_motorola_msm8960dt-common/tree/cm-11.0 that has been updated by dhacker for support of KitKat updated Razr HD/M.
To circumvent dt not being handled, I'm using appended dtb:
CONFIG_ARM_APPENDED_DTB=y
CONFIG_ARM_ATAG_DTB_COMPAT=y
Device tree partition check revealed that my device is p2 or p2b revision (https://github.com/MotorolaMobility...razrm/arch/arm/boot/dts/msm8960-asanti-p2.dts and https://github.com/MotorolaMobility...azrm/arch/arm/boot/dts/msm8960-asanti-p2b.dts are identical), so I'm using msm8960-asanti-p2.dtb appended to zImage.
Next issue is that bootloader is supposed to add dynamic data on runtime in addition to static ones loaded from dtb.
To get the display working, I've added:
Code:
chosen {
/* mipi_mot_cmd_auo_qhd_430 */
mmi,panel_name = [6d6970695f6d6f745f636d645f61756f5f7168645f34333000];
};
to msm8960-asanti-p2.dts.
That's where I'm currently. The next step is to add additional entries we're missing there (e.g. "mmi,mbmprotocol" etc.).
Regarding bootloaders, I see another issue - memory configuration.
There's failing shared mem allocation in mmi_unit_info_init:
https://github.com/CyanogenMod/andr...ob/cm-11.0/arch/arm/mach-msm/board-mmi.c#L433
That memory block is supposed to be reserved by sbl3, as indicated by https://github.com/MotorolaMobilityLLC/kernel-msm/commit/585b70b3fcd1af84edcb8748d1fdf190b32784af
Also, this commit https://github.com/MotorolaMobilityLLC/kernel-msm/commit/e3b9a040ca408d217a873df7994b9452ece04d16 indicates that Moto has done some tests also with older modem firmware, at least at some point...
If you need any logs or whatever from something not a Q, hit me up. Maybe something from my Atrix HD will help you out, I dunno -- AHD is stuck with JB until Q3 this year, so we're interested in this too.
Just 2 questions:
1) that moto test for older modem firmware with newer kernels, patch for asanti device tree (in which they state that device mostly works) might indicate that moto actually has updated bootloaders, etc, which we will never see?
2) this thread in development section is best left for dev disscusson? Ie, no potentially irritating stupid suggestions/questions/ideas/thoughts? (I have to ask)
mrvek said:
Just 2 questions:
1) that moto test for older modem firmware with newer kernels, patch for asanti device tree (in which they state that device mostly works) might indicate that moto actually has updated bootloaders, etc, which we will never see?
2) this thread in development section is best left for dev disscusson? Ie, no potentially irritating stupid suggestions/questions/ideas/thoughts? (I have to ask)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2778330
mrvek said:
Just 2 questions:
1) that moto test for older modem firmware with newer kernels, patch for asanti device tree (in which they state that device mostly works) might indicate that moto actually has updated bootloaders, etc, which we will never see?
2) this thread in development section is best left for dev disscusson? Ie, no potentially irritating stupid suggestions/questions/ideas/thoughts? (I have to ask)
Click to expand...
Click to collapse
1 - yes, I'm pretty sure that test builds for asanti exist somewhere in moto labs from the time before 4.4 upgrade for Photon Q cancellation, with updated bootloader images and stuff, that we will unfortunately never see (I'm not very good in social hacking, so I don't expect myself to be able to get access to that internal stuff).
I also noticed this commit - https://github.com/MotorolaMobilityLLC/kernel-msm/commit/14e5887c3db194ec1a8aa6145910f7c7b64f95dc - they did not have enough asanti p2 hw revision devices for testing, so they needed some fixes to be able to test on an older p1 revision of the hardware...
VijayKumar Gn surely wasted some of his time on 4.4 bring-up for asanti before it got cancelled...
2 - It depends on the level of stupidity Even some very bright ideas may appear stupid at first sight, but can get proved to be great in the end.
At this point, I'm still not able get the BP going, it goes to crash and restart loop as soon as it's brought out of reset by the PIL (peripheral image loader).
I've pushed the kernel commits I use so far here in cm-11.0-3.4kJBbl branch:
https://github.com/nadlabak/android_kernel_motorola_msm8960dt-common/commits/cm-11.0-3.4kJBbl
It should go with something like this kernel setting in BoardConfig.mk:
Code:
# Inline kernel building
TARGET_KERNEL_SOURCE := kernel/motorola/msm8960dt-common
TARGET_KERNEL_CONFIG := msm8960_mmi_defconfig
TARGET_KERNEL_VARIANT_CONFIG := msm8960_mmi_xt897_defconfig
TARGET_KERNEL_SELINUX_CONFIG := msm8960_mmi_selinux_defconfig
BOARD_KERNEL_IMAGE_NAME := zImage-dtb
BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 vmalloc=400M androidboot.write_protect=0 zcache androidboot.selinux=permissive androidboot.modelno=XT897 product=asanti_c androidboot.device=asanti_c androidboot.secure_hardware=1
BOARD_KERNEL_BASE := 0x80200000
BOARD_KERNEL_PAGESIZE := 2048
BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x02200000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 12884901888
OK, good news, I've got the BP running fine now, under 3.4 kernel.
Just a little off-topic:
Do we have some indicators to differentiate between p1 and p2 devices?
kabaldan said:
OK, good news, I've got the BP running fine now, under 3.4 kernel.
Click to expand...
Click to collapse
AAAAAAAAAAAAAMAAAAAAAAZINNNNNNGGGGGGGGGGGG
cant wait for some first beta/test/kernel for a try ! thanks very good news very !
Loader009 said:
Just a little off-topic:
Do we have some indicators to differentiate between p1 and p2 devices?
Click to expand...
Click to collapse
You can check e.g. /proc/device-tree/[email protected]/[email protected] on your device.
If it contains [email protected], your device is P2.
If [email protected] is missing, but [email protected] and [email protected] are there, your device is P1.
It would be useful for me to know if there's actually a P1 device running CM11 out there somewhere.
Ok, P2 also here.
Is it possible that P1 devices are prototypes?
Someone here had a prototype, I wouldn't wonder if it was a P1 device.
@kabaldan this would work also with xt925 with JB bl.. Because Motorola will not release kk for us until Q3
If you need logs or something for xt925 count with me..
Sent from my RAZR HD using Forum Fiend v1.2.8.
kabaldan said:
You can check e.g. /proc/device-tree/[email protected]/[email protected] on your device.
If it contains [email protected], your device is P2.
If [email protected] is missing, but [email protected] and [email protected] are there, your device is P1.
It would be useful for me to know if there's actually a P1 device running CM11 out there somewhere.
Click to expand...
Click to collapse
...my photon is one of first and it is P2
p2 here too
P2 too...
Just to give a 3.4 kernel on Q current status report:
It's not stable yet. Occasionally, there's a kernel panic, usually when going to suspend state.
Will need to figure out the cause.
Otherwise, everything is basically working: radio, gps, nfc, wlan (while using the new wcnss firmware), bt, audio, camera, usb...
can this commit may help for our kernel-panic problem .?
https://github.com/edoko/Air_Kernel-NOTE/commit/5cd3f27ce5373fa3e84b7916480cebaa4ebc9df1
Kernel 3.4 working?
http://review.cyanogenmod.org/#/c/67589/
gehstock said:
Kernel 3.4 working?
http://review.cyanogenmod.org/#/c/67589/
Click to expand...
Click to collapse
If the Atrix HD is not running a 3.4 kernel yet, then no, it does not work. Be patient until something is announced.
@stargo , @Skrilax_CZ , @mrvek , @arrrghhh and others:
Sorry for the delay. I've been too busy at work and home again (surprise!).
Anyway, I've finally managed to push my current local mess to razrqcom, reusing the old xt897 and msm8960-common repos for tentative 3.4 kernel on JB firmware builds.
Local manifest:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="razrqcom-dev-team/android_device_motorola_xt897" path="device/motorola/xt897" remote="github" revision="cm-11.0-3.4" />
<project name="razrqcom-dev-team/android_device_motorola_msm8960-common" path="device/motorola/msm8960-common" remote="github" revision="cm-11.0-3.4" />
<project name="razrqcom-dev-team/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="cm-11.0-3.4" />
</manifest>
The main issues remain the same:
- while the modem subsystem can occasionally work stable for tens of minutes, it can also get being restarted by watchdog bite in matter of minutes or even seconds (=too often).
- occasional kernel panic (NULL pointer dereference) at process_one_work coming immediately after hitting this warning https://github.com/CyanogenMod/andr...t-common/blob/cm-11.0/kernel/workqueue.c#L550
No worries, I'm extremely busy lately too with practically no time for this stuff. I'm in China atm. And it's very hot in here (real feel: 44° C).
Related
Hello, I have some problems while building cm9 from sources.
When I do
Code:
brunch galaxysl
I get the following:
Code:
Repository for galaxysl not found in the CyanogenMod 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:189: *** _nic.PRODUCTS.[[device/*/galaxysl/cm.mk]]: "device/*/galaxysl/cm.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_galaxysl'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
(seems like its not officialy supported by CM team)
I've tried this:
Manually downloaded files as .zip from here:
Code:
https://github.com/teamhacksung/android_device_samsung_galaxysl
and extracted here: /device/samsung/galaxysl/
Then downloaded files from here:
Code:
https://github.com/teamhacksung/android_vendor_samsung_galaxysl
and extracted here /vendor/samsung/galaxysl/
Then compiled with no errors, the output files were something like this:
Code:
cm-9-20120717-UNOFFICIAL-galaxysl.zip
and
Code:
cm_galaxysl-ota-eng.xxxx.zip
They have both different sizes (every file has different size inside .zip), if someone could tellme the difference it will be apreciated.
Tried flashing both of them, and the phone doesnt boot up, just black screen on.
CWM 6.0 works just fine.
Could someone guideme or give me any tip to make it work?
Thanks in advance.
frapeti said:
Hello, I have some problems while building cm9 from sources.
When I do
Code:
brunch galaxysl
I get the following:
Code:
Repository for galaxysl not found in the CyanogenMod 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:189: *** _nic.PRODUCTS.[[device/*/galaxysl/cm.mk]]: "device/*/galaxysl/cm.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_galaxysl'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
(seems like its not officialy supported by CM team)
I've tried this:
Manually downloaded files as .zip from here:
Code:
https://github.com/teamhacksung/android_device_samsung_galaxysl
and extracted here: /device/samsung/galaxysl/
Then downloaded files from here:
Code:
https://github.com/teamhacksung/android_vendor_samsung_galaxysl
and extracted here /vendor/samsung/galaxysl/
Then compiled with no errors, the output files were something like this:
Code:
cm-9-20120717-UNOFFICIAL-galaxysl.zip
and
Code:
cm_galaxysl-ota-eng.xxxx.zip
They have both different sizes (every file has different size inside .zip), if someone could tellme the difference it will be apreciated.
Tried flashing both of them, and the phone doesnt boot up, just black screen on.
CWM 6.0 works just fine.
Could someone guideme or give me any tip to make it work?
Thanks in advance.
Click to expand...
Click to collapse
You need to download the kernel too.
Download android_kernel_samsung_latona.
And build it separately and then build cm9.
In the evening, I will post the local_manifest.xml, copy it to the .repo folder. this will downlod the device/vendor and kernel for galaxysl automatically. Any changes by teamhacksung will also be synced automatically.
meanwhile you can refer to cm7 local_manifest.xml.
You need to make changes to it to as it is for gb.
Check this out: http://pastebin.com/Xig7BtHV
ganeshbiyer said:
You need to download the kernel too.
Download android_kernel_samsung_latona.
And build it separately and then build cm9.
In the evening, I will post the local_manifest.xml, copy it to the .repo folder. this will downlod the device/vendor and kernel for galaxysl automatically. Any changes by teamhacksung will also be synced automatically.
meanwhile you can refer to cm7 local_manifest.xml.
You need to make changes to it to as it is for gb.
Click to expand...
Click to collapse
Thanks you very much I'll sure try this tonight
Why dont u try building cm10 from sources like that on galaxy s i9000...
Thanks
Sent from my GT-I9300 using xda app-developers app
EDIT:
I didn't read Ganesh's post well enough and I din't see his attachment at first. This post is pretty much the same .
EDIT 2:
I should see better, but I think that cm-9-***-UNOFFICIAL-galaxysl.zip has all the apk with all the images optimized for size. If you take a look at the last messages in your terminal you'll see a lot of lines that start with "Optimizing ****...".
____
I usually put this local_manifest.xml inside .repo/
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="teamhacksung/android_device_samsung_galaxysl" path="device/samsung/galaxysl" remote="github" revision="ics" />
<project name="teamhacksung/android_vendor_samsung_galaxysl" path="vendor/samsung/galaxysl" remote="github" revision="ics" />
<project name="teamhacksung/android_kernel_samsung_latona" path="kernel/samsung/latona" remote="github" revision="ics-samsung-2.6.35.7" />
<project name="alfrix/buildscripts" path="buildscripts" remote="github" revision="ics">
<copyfile dest="build.sh" src="samsung/build.sh" />
</project>
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" />
</manifest>
and then run
Code:
repo sync
Everything is done automatically, all the sources are in the right place and everything is ready to be built.
As you can see I'm using alfrix's builscripts instead of the teamhacksung ones. That's because he already adapted them to work with our phone (well, codeworkx recently changed build.sh and made it a little bit more universal). So I can simply run
Code:
./build.sh galaxysl
NOTE:
By default the kernel is not built from kernel/samsung/latona, the prebuilt one in device/samsung/galaxysl/kernel is used (you'll see a warning during the building process). This kernel is old if I'm not wrong, it doesn't have all the latest changes.
I usually build it separately and then replace it and the modules inside device/samsung/galaxysl/.
(remember that if you don't set up git correctly, the next time you'll do a repo sync you'll "loose" your changes)
I am getting this warning message:
while compiling cm9, i am getting the following warning
BFD: /media/Data/cm9/system/out/target/product/galaxysl/repack.d/ota/system/lib/storage.ko: warning: sh_link not set for section `.ARM.exidx'
what is this regarding?
Can any one enlighten me?
Thanks you very much, I could compile it but with some few issues.
1.- Couldnt compile the kernel (./kernel/samsung/latona) using either latona_galaxy_defconfig / config file pulled via adb.
2.- I've replaced the prebuilt one (./device/samsung/galaxysl/kernel) with cm9a9 kernel then build the whole rom. (wifi didnt work)
3.- Replaced the new boot.img in a working cm9a9 build and works fine, cwm 6.0.7 and wifi works but the rom isnt the one that I've compiled.
Seems like there is a problem with wlan modules. :0
Btw I'll keep trying
Thanks again
frapeti said:
Thanks you very much, I could compile it but with some few issues.
1.- Couldnt compile the kernel (./kernel/samsung/latona) using either latona_galaxy_defconfig / config file pulled via adb.
2.- I've replaced the prebuilt one (./device/samsung/galaxysl/kernel) with cm9a9 kernel then build the whole rom. (wifi didnt work)
3.- Replaced the new boot.img in a working cm9a9 build and works fine, cwm 6.0.7 and wifi works but the rom isnt the one that I've compiled.
Seems like there is a problem with wlan modules. :0
Btw I'll keep trying
Thanks again
Click to expand...
Click to collapse
To compile the kernel you go to the kernel/samsung/latona folder and run the ./build.sh and then build the ROM.
Regarding the WIFI, I have the same problem. I was able to build it, but the wifi seems not to work.
ganeshbiyer said:
To compile the kernel you go to the kernel/samsung/latona folder and run the ./build.sh and then build the ROM.
Regarding the WIFI, I have the same problem. I was able to build it, but the wifi seems not to work.
Click to expand...
Click to collapse
Its nice that the build.sh script copy the modules and the kernel after build.
I've check'd the log and it seems like its using linaro toolchain and the prebuilt one is codesourcery.
Code:
make: ../../../prebuilt/linux-x86/toolchain/linaro-4.6/bin/arm-eabi-gcc: Command not found
I've checked ../../../prebuilt/linux-86/toolchain folder and there isnt any linaro-4.6 folder, maybe the scripts are out of date.
I'll try tomorrow to find that toolchain and put it there
frapeti said:
Its nice that the build.sh script copy the modules and the kernel after build.
I've check'd the log and it seems like its using linaro toolchain and the prebuilt one is codesourcery.
Code:
make: ../../../prebuilt/linux-x86/toolchain/linaro-4.6/bin/arm-eabi-gcc: Command not found
I've checked ../../../prebuilt/linux-86/toolchain folder and there isnt any linaro-4.6 folder, maybe the scripts are out of date.
I'll try tomorrow to find that toolchain and put it there
Click to expand...
Click to collapse
I think you are using Alfrix kernel.
The default kernel for galaxysl from teamhacksung git does not use linaro.
frapeti said:
Thanks you very much, I could compile it but with some few issues.
1.- Couldnt compile the kernel (./kernel/samsung/latona) using either latona_galaxy_defconfig / config file pulled via adb.
2.- I've replaced the prebuilt one (./device/samsung/galaxysl/kernel) with cm9a9 kernel then build the whole rom. (wifi didnt work)
3.- Replaced the new boot.img in a working cm9a9 build and works fine, cwm 6.0.7 and wifi works but the rom isnt the one that I've compiled.
Seems like there is a problem with wlan modules. :0
Btw I'll keep trying
Thanks again
Click to expand...
Click to collapse
Regarding wifi issue I talked with dhiru.
He says to use dhcpcd from cm7.
frapeti said:
Its nice that the build.sh script copy the modules and the kernel after build.
I've check'd the log and it seems like its using linaro toolchain and the prebuilt one is codesourcery.
Code:
make: ../../../prebuilt/linux-x86/toolchain/linaro-4.6/bin/arm-eabi-gcc: Command not found
I've checked ../../../prebuilt/linux-86/toolchain folder and there isnt any linaro-4.6 folder, maybe the scripts are out of date.
I'll try tomorrow to find that toolchain and put it there
Click to expand...
Click to collapse
I guess you are building alfrix's kernel
He switched to linaro. You need to download the toolchain separately if you want to use it.
EDIT 2:
... oh, I didn't see ganesh's post this time too...
ganeshbiyer said:
Regarding wifi issue I talked with dhiru.
He says to use dhcpcd from cm7.
Click to expand...
Click to collapse
I too had troubles with wifi at first, but I think in my case the problem was my router. It always gives me problems, I can't even keep my phone with the screen off and wifi on. It keeps the connection active with the router, but that's it, if I try to ping something out of my net, I get no response. (stock roms too)
Anyway, I was able to enstablish a connection with a static IP and now it works with DHCP too, but I didn't use dhcpd from CM7, weird.
EDIT:
Did more tests, it seems I have problems in getting the IP. Thanks for the headsup!
ganeshbiyer said:
I am getting this warning message:
while compiling cm9, i am getting the following warning
BFD: /media/Data/cm9/system/out/target/product/galaxysl/repack.d/ota/system/lib/storage.ko: warning: sh_link not set for section `.ARM.exidx'
what is this regarding?
Can any one enlighten me?
Click to expand...
Click to collapse
I had always got those warnings. You get them when you strip the modules.
Successfully built.
Wifi is working (adding the cm7 dhcpcd)
Cwm version is 6.0.7
nice
ganeshbiyer said:
Successfully built.
Wifi is working (adding the cm7 dhcpcd)
Cwm version is 6.0.7
Click to expand...
Click to collapse
nicee I hope I can make it work as yours, cheers. :highfive:
So the connection works but DHCP doesnt.
I'll try that and see what happens
Wich files did you copy from cm7 to add dhcp? / wich repo?
ganeshbiyer said:
I think you are using Alfrix kernel.
The default kernel for galaxysl from teamhacksung git does not use linaro.
Click to expand...
Click to collapse
loSconosciuto said:
I guess you are building alfrix's kernel
He switched to linaro. You need to download the toolchain separately if you want to use it.
Click to expand...
Click to collapse
Yes, I've moded the local_manifest.xml a little I'll try with the default kernel for now
There are some issues that I've found related to the cpu governors, i.e on-demand makes the battery last longer but seems like it makes the connection down or just cloud notifications down while certain amount of time with screen off. With conservative governor works just fine.
modded default.xml for cm7
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="korg"
fetch="git://android.git.kernel.org/"
review="review.source.android.com" />
<remote name="github"
fetch=".."
review="review.cyanogenmod.com" />
<default revision="gb-release-7.2"
remote="github" />
<project path="external/dhcpcd" name="CyanogenMod/android_external_dhcpcd" />
</manifest>
frapeti said:
There are some issues that I've found related to the cpu governors, i.e on-demand makes the battery last longer but seems like it makes the connection down or just cloud notifications down while certain amount of time with screen off. With conservative governor works just fine.
Click to expand...
Click to collapse
FYI dhiru's kernel has all the governors, waleedq included them when he took UC kernel sources.
Basically, after
Code:
make latona_galaxysl_defconfig
run (or edit build.sh)
Code:
make menuconfig
and under "CPU Power Management --->" do all the changes you want.
Worked like a charm thx u all!
Flawlessly built and running with the latest updates.
When I finish with exams I will look closer to that source stuff
hi friend seeing screen shot of cm9 compiled by u it looks u have got wifi icon in stautsbar working
+1 this. Is it static or working? (I saw a fake wifi signal workaround so i would rather confirm before celebrating).
Cheers. Congrats for successful compilation though
santoshsadani009 said:
+1 this. Is it static or working? (I saw a fake wifi signal workaround so i would rather confirm before celebrating).
Cheers. Congrats for successful compilation though
Click to expand...
Click to collapse
androman1507 said:
hi friend seeing screen shot of cm9 compiled by u it looks u have got wifi icon in stautsbar working
Click to expand...
Click to collapse
He posted the workaround in the "Theme and Apps" subforum, so I think it's fake
ganeshbiyer said:
Successfully built.
Wifi is working (adding the cm7 dhcpcd)
Cwm version is 6.0.7
Click to expand...
Click to collapse
I can see that CWM is under heavy developement and with your version (or maybe 6.0.6) I couldn't mount /emmc or /sdcard because of a missing trailing slash (koush fixed it now) and now CWM 6.0.0.9 erase my /system partition when I try to start a backup and I think it does something to /efs too (of course I have a backup of everything ), but I'm not sure if the problem is CWM or I did something wrong.
So, be carefull with this new recovery (anyway I like the new background :laugh
EDIT:
Ok, now I'm sure: /system, /efs and probably /sdcard (=external sd in CWM) are erased when you start a backup.
EDIT 2:
And gapps is missing after an update, it never happened. I think this is related to it.
In this post, I would like to explain what kexec-hardboot patch is and also bring it to light a bit more since until now, it was only burried in MultiROM thread.
@kernel developers: I would like to ask you to merge this patch to your kernels, because it is essential part of MultiROM - it allows me to boot any kernel without changing the boot partition. I realize that it is no small request, but the patch is not big, touches relatively stable parts of kernel and should not cause any problems. Thank you.
What is kexec?
It is syscall of Linux kernel, which allows you to boot another Linux kernel without restarting the device - "Linux boots itself". The functionality is equivalent to fastboot -c *cmdline* boot zImage initrd.img, but without PC and fastboot. It is fairly known thing, so more info at wikipedia and man kexec.
Standard kexec call unfortunatelly does not work on Nexus 7. It freezes somewhere, and it is very difficult to find out where - probably some of the drivers are not shut down/re-initialized properly, it is a commong thing among Android devices, which is why kexec-hardboot was made.
What is the difference between normal and hardboot exec?
Kexec-hardboot patch adds a real device restart to that process, so that all the drivers can be properly reinitialized. It stores new kernel to RAM, reboots the device as usual, and kernel from boot partition immediately jumps to the one which was stored to RAM before reboot.
Another difference is that both kernels must be patched. The "host" kernel requires a full patch, the one which is being kexecd' requires only two small compatibility patches.
To sumarize the process:
kexec --load-hardboot.... is called and kernel it loaded into RAM.
kexec -e is called. Special info is written to memory (to area which is not overwritten on reboot) and the device is rebooted.
After reboot, very early in the boot process, kernel checks if that special info is present in RAM and if so, it loads new kernel from RAM and jumps to it.
Kexecd' kernel starts and boots.
For more info, read the original thread.
Patches:
Full kernel patch: https://gist.github.com/4558647, 4.1 kernel repo, cm 10.1 kernel repo
This is the full kernel patch. Kernels with this patch can be both "host" and "guest" kernels.
Related CONFIG options:
CONFIG_KEXEC=y
CONFIG_KEXEC_HARDBOOT=y
CONFIG_ATAGS_PROC=y
CONFIG_GROUPER_HARDBOOT_RECOVERY=n
First three options must be enabled. Last one, GROUPER_HARDBOOT_RECOVERY, specifies if the kexec call should reboot to normal mode or to recovery. This can be useful if you don't have the kernel in boot partition but only as kernel in recovery partition. You usualy want to disable this option.
Compatibility patch: https://gist.github.com/4458581
This patch only makes the kernel bootable via kexec, ie. it can't be the host kernel. This was made for Ubuntu kernel (and it was accepted), because I did not want to drag the whole patch in there. If your kernel is for Android ROMs, you should use the full patch.
Userspace kexec binary: View attachment kexec-tools.zip
That ZIP file contains kexec source, patches and README. It is from the original patch from Mike Kasick. It also contains precompiled, statically linked kexec binary, so you probably just want to use that.
Usage:
Once you have the kernel patches and kexec userspace binary in place, just run following command to boot into new kernel:
Code:
kexec --load-hardboot zImage --initrd=initrd.img --mem-min=0x85000000 --command-line="$(cat /proc/cmdline)"
kexec -e
Note the command line parameter - cmdline from bootloader is not added automatically, you have to put it there by yourself.
Currently used by:
MultiROM - I use it to boot different kernels (eg. Ubuntu).
MOSLO - Part of Plasma Active for Nexus 7, also usefull tool for every N7 developer - read more: http://ruedigergad.com/2012/12/09/nexus-7-easily-flashaccess-entire-userdata-partition/
Authors:
This patch was made by Mike Kasick for Samsung Epic 4G. Since that, it was ported to several devices, one of them is Asus Transformer TF201 - I used patch from TF201 and modified it a bit (basically just changed few SoC specific constants). People at #ubuntu-arm helped me out with that, thanks.
Hi Tasssadar,
im trying to get this to work on the HOX in order to have a shot at multiboot,
the patched applied with no problem... however on compiling i gett this error
"Adress for kexec hardboot page not defined"
ask this error naturely defined to kick in with every device beside N7 i that comment completely....
and that ended up giving me an error about KEXEC_HB_PAGE_ADDR not defined,
so i readded it, but i removed the "#if defined(CONFIG_MACH_GROUPER)"
now trying to compile it, its gets pretty close to the end... but failed with unexpected string error at line OUTPUT_ARCH(arm) in file linux/arch/arm/boot/compressed/vmlinux.lds
Code:
/*
* linux/arch/arm/boot/compressed/vmlinux.lds.in
*
* Copyright (C) 2000 Russell King
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License version 2 as
* published by the Free Software Foundation.
*/
OUTPUT_ARCH(arm)
ENTRY(_start)
SECTIONS
{
/DISCARD/ : {
*(.ARM.exidx*)
*(.ARM.extab*)
/*
* Discard any r/w data - this produces a link error if we have any,
* which is required for PIC decompression. Local data generates
* GOTOFF relocations, which prevents it being relocated independently
* of the text/got segments.
*/
*(.data)
}
. = 0;
_text = .;
.text : {
_start = .;
*(.start)
*(.text)
*(.text.*)
*(.fixup)
*(.gnu.warning)
*(.glue_7t)
*(.glue_7)
}
.rodata : {
*(.rodata)
*(.rodata.*)
}
.piggydata : {
*(.piggydata)
}
. = ALIGN(4);
_etext = .;
.got.plt : { *(.got.plt) }
_got_start = .;
.got : { *(.got) }
_got_end = .;
_edata = .;
. = ALIGN(8);
__bss_start = .;
.bss : { *(.bss) }
_end = .;
. = ALIGN(8); /* the stack must be 64-bit aligned */
.stack : { *(.stack) }
.stab 0 : { *(.stab) }
.stabstr 0 : { *(.stabstr) }
.stab.excl 0 : { *(.stab.excl) }
.stab.exclstr 0 : { *(.stab.exclstr) }
.stab.index 0 : { *(.stab.index) }
.stab.indexstr 0 : { *(.stab.indexstr) }
.comment 0 : { *(.comment) }
}
also, im booted into windows now... so i can't provide the exact error.
I'm afraid "comment everything which doesn't work" won't work here. The KEXEC_HB_PAGE_ADDR and END_MEM is device-specific, it will most likely be different for HTC One X. You can find out what address is it supposed to be by examining /proc/iomem on your device. For example, here's memory map from grouper:
Code:
...
80000000-be9fffff : System RAM
80008000-808faba7 : Kernel text
80940000-80b8228f : Kernel data
beb00000-bebfffff : ram_console
...
So, for grouper, END_MEM is 0xbe9fffff + 1 = 0xbea00000.
KEXEC_HB_PAGE_ADDR is located 1MB before console RAM, which is in this case also immediatelly after System RAM, so for grouper, it is also 0xbea00000.
but failed with unexpected string error at line OUTPUT_ARCH(arm) in file linux/arch/arm/boot/compressed/vmlinux.lds
Click to expand...
Click to collapse
That doesn't seem to be related to this patch. Are you using correct cross-compiler?
Tasssadar said:
I'm afraid "comment everything which doesn't work" won't work here. The KEXEC_HB_PAGE_ADDR and END_MEM is device-specific, it will most likely be different for HTC One X.
Click to expand...
Click to collapse
i figured
but im walking you through what i did.
You can find out what address is it supposed to be by examining /proc/iomem on your device. For example, here's memory map from grouper:
Code:
...
80000000-be9fffff : System RAM
80008000-808faba7 : Kernel text
80940000-80b8228f : Kernel data
beb00000-bebfffff : ram_console
...
So, for grouper, END_MEM is 0xbe9fffff + 1 = 0xbea00000.
KEXEC_HB_PAGE_ADDR is located 1MB before console RAM, which is in this case also immediatelly after System RAM, so for grouper, it is also 0xbea00000.
Click to expand...
Click to collapse
Code:
7d000000-7d003fff : tegra-udc.0
7d000000-7d003fff : tegra-otg
7d000000-7d003fff : tegra-udc
7d004000-7d007fff : tegra-ehci.1
80000000-beafffff : System RAM
80008000-8094000f : Kernel text
809a8000-810b940f : Kernel data
beb00000-bebfffff : ram_console
bec00000-beffffff : fbmem
bf000000-bf7fffff : fbmem
0xbeafffff + 1 = 0xbeb00000
grrr that would put me inside the ram_console...
aaaa would it wok if i used the address before??
7d00800
Edit:
or did your ram RAM end earlier because you set you END_MEM 0xbea00000
in that case, it works out just the same with the HOX
That doesn't seem to be related to this patch. Are you using correct cross-compiler?
Click to expand...
Click to collapse
i would have guessed so, but the kernel compiled and is working before the patch.
im using the one provided by google (Android NDK r9) while it contains booth gcc 4.6/4.8 im using 4.6 (arm-linux-androideabi-)
The patch will move ram_console 1MB further, see https://gist.github.com/Tasssadar/4558647#file-n7_hardboot-diff-L387 . You'll have to modify this part of the patch, it will be in different file for your device.
Tasssadar said:
The patch will move ram_console 1MB further, see https://gist.github.com/Tasssadar/4558647#file-n7_hardboot-diff-L387 . You'll have to modify this part of the patch, it will be in different file for your device.
Click to expand...
Click to collapse
HOX is also a Tegra 3 device... so im guessing i wont need to touch a thing?
also note... that iomem provided is from an unpatched kernel (as i cant compile a patched one)
also,
im currently on freenode #htc-one-x
if you dont mind joining.
I've been looking through the kexec-hardboot patch these last few days, trying to actually understand it instead of just blindly porting it and after several hours of messing with assembler with no means to debug it, I've managed to remove the need for guest kernel to be patched. This is not really useful for grouper, since thanks to multirom and accepting kernel devs, nearly every third-party kernel has the proper patches. But, if I'll port multirom to some other device (hello, flo), it will be very useful
To know more see the changes in this commit, but you'll probably need to understand how the patch does things: https://github.com/Tasssadar/androi...mmit/2ce4130061f72430a8ddfde25346c4e528c5c30b
@mkasick: Could you please look over this? I'm afraid there's some good reason why you didn't do this in the first place, like rewriting some part of memory which shouldn't be rewritten or something like that. Thank you.
Tasssadar said:
I've been looking through the kexec-hardboot patch these last few days, trying to actually understand it instead of just blindly porting it and after several hours of messing with assembler with no means to debug it, I've managed to remove the need for guest kernel to be patched. This is not really useful for grouper, since thanks to multirom and accepting kernel devs, nearly every third-party kernel has the proper patches. But, if I'll port multirom to some other device (hello, flo), it will be very useful
To know more see the changes in this commit, but you'll probably need to understand how the patch does things: https://github.com/Tasssadar/androi...mmit/2ce4130061f72430a8ddfde25346c4e528c5c30b
@mkasick: Could you please look over this? I'm afraid there's some good reason why you didn't do this in the first place, like rewriting some part of memory which shouldn't be rewritten or something like that. Thank you.
Click to expand...
Click to collapse
Perfect timing, just finished my last exam
Edit:
Also, this applies on top of the original patch right??
Edit2:
i can't seem to get it to kexec boot, but i didn't do much testing, maybe 2morrow night!
Edit3:
fixed, it was a problem with min-addr,
changed it to 0x82000000 and it worked
One more question...
TEGRA_PMC_BASE is also device specific, ain't it???
So, for a Qualcomm device, what should I be using? I am guessing it is MSM_RPM_BASE, which I got from here: http://forum.xda-developers.com/showpost.php?p=31127486&postcount=7
Yes, it is SoC-specific. This is using some special register to reset the chip, I'm not sure if that is available on msm chips - probably yes, but in some different form. Your best chance is to examine restart sequence in arch/arm/mach-msm/restart.c and port it to assembler.
Tasssadar said:
Usage:
Once you have the kernel patches and kexec userspace binary in place, just run following command to boot into new kernel:
Code:
kexec --load-hardboot zImage --initrd=initrd.img --mem-min=0xA0000000 --command-line="$(cat /proc/cmdline)"
kexec -e
Click to expand...
Click to collapse
The address of 0xA0000000 is not necessarily the best choice going forward. It originally made perfect sense, as it is well above everything else. But now that we can boot unpatched guest kernels, we can hit the interesting situation where the guest decompression may take a full minute. At least it's when I've seen on the Ouya game console that's running the next chip after Grouper.
When I realized what's going on, I changed to 0x8E000000, as it gets me just below the 256 MB limit of cache-enabled memory that's present on a typical guest at that early decompression stage. It's enough to hold a typical 8 MB boot image kernel/ramdisk. Now the guest kernel startup is fast in all cases.
Thank you Tasssadar for continuing your work in this area, especially with finding that way to allow unpatched guests.
Indeed, that's actually what I'm using in MultiROM for flo and mako (and grouper, but it is useless 'cause not all 3rd-party kernels have been updated), I just kinda "forgot" to update these threads.
Would it work on devices with locked bootloaders (Xperias). I mean :does the idea of this patch would also work on bootloader unlock allowed :no devices?
Sent from my LT22i using xda app-developers app
I am trying to build a kexec patched kernel integrated into a ROM. I make sure that the following code is there in the defconfig:
CONFIG_KEXEC=y
CONFIG_KEXEC_HARDBOOT=y
CONFIG_ATAGS_PROC=y
The ROM works well, except that it does not boot my secondary ROMs - kexec hardboot patch missing. I have multi ROM and TWRP recovery installed
What am I missing?
Logs or it didn't happen.
Show me dmesg from normal boot into android, with MultiROM and your kernel installed.
Code:
adb shell
su
dmesg > /data/local/tmp/dmesg.txt
exit
exit
adb pull /data/local/tmp/dmesg.txt
Porting?
Tassadar which things do I need to boot kexec kernel on my device (Motorola Electrify 2) .
@Tasssadar, Sorry for picking up this kinda "old topic" but I'm sadly experiencing some problems while trying to port kexec-hardboot to the Sony Xperia Z2 (aka sirius). I applyed all needed commits (cherry-picked from a apparently working Z1 repo for stock kernel) to my CM based custom kernel (https://github.com/Myself5/android_kernel_sony_msm8974/tree/kexec-cm-12.0) and it does not boot at all. It's stuck on the Sony Logo, and it seems like I can't get any log either. I also tryed the stock cm kernel with the patch (https://github.com/Myself5/android_kernel_sony_msm8974-kexec) cause I tought it might be some incompatibility, but sadly it wasn't. Hope you have any ideas to solve my problems, cause I'm out of ideas ATM. I also checked the kexec commits for other devices (namely the One Plus One) and it seems like I got everything needed.
Thanks in Advance
Tasssadar said:
In this post, I would like to explain what kexec-hardboot patch is and also bring it to light a bit more since until now, it was only burried in MultiROM thread.
@kernel developers: I would like to ask you to merge this patch to your kernels, because it is essential part of MultiROM - it allows me to boot any kernel without changing the boot partition. I realize that it is no small request, but the patch is not big, touches relatively stable parts of kernel and should not cause any problems. Thank you.
What is kexec?
It is syscall of Linux kernel, which allows you to boot another Linux kernel without restarting the device - "Linux boots itself". The functionality is equivalent to fastboot -c *cmdline* boot zImage initrd.img, but without PC and fastboot. It is fairly known thing, so more info at wikipedia and man kexec.
Standard kexec call unfortunatelly does not work on Nexus 7. It freezes somewhere, and it is very difficult to find out where - probably some of the drivers are not shut down/re-initialized properly, it is a commong thing among Android devices, which is why kexec-hardboot was made.
What is the difference between normal and hardboot exec?
Kexec-hardboot patch adds a real device restart to that process, so that all the drivers can be properly reinitialized. It stores new kernel to RAM, reboots the device as usual, and kernel from boot partition immediately jumps to the one which was stored to RAM before reboot.
Another difference is that both kernels must be patched. The "host" kernel requires a full patch, the one which is being kexecd' requires only two small compatibility patches.
To sumarize the process:
kexec --load-hardboot.... is called and kernel it loaded into RAM.
kexec -e is called. Special info is written to memory (to area which is not overwritten on reboot) and the device is rebooted.
After reboot, very early in the boot process, kernel checks if that special info is present in RAM and if so, it loads new kernel from RAM and jumps to it.
Kexecd' kernel starts and boots.
For more info, read the original thread.
Patches:
Full kernel patch: https://gist.github.com/4558647, 4.1 kernel repo, cm 10.1 kernel repo
This is the full kernel patch. Kernels with this patch can be both "host" and "guest" kernels.
Related CONFIG options:
CONFIG_KEXEC=y
CONFIG_KEXEC_HARDBOOT=y
CONFIG_ATAGS_PROC=y
CONFIG_GROUPER_HARDBOOT_RECOVERY=n
First three options must be enabled. Last one, GROUPER_HARDBOOT_RECOVERY, specifies if the kexec call should reboot to normal mode or to recovery. This can be useful if you don't have the kernel in boot partition but only as kernel in recovery partition. You usualy want to disable this option.
Compatibility patch: https://gist.github.com/4458581
This patch only makes the kernel bootable via kexec, ie. it can't be the host kernel. This was made for Ubuntu kernel (and it was accepted), because I did not want to drag the whole patch in there. If your kernel is for Android ROMs, you should use the full patch.
Userspace kexec binary: View attachment 1653562
That ZIP file contains kexec source, patches and README. It is from the original patch from Mike Kasick. It also contains precompiled, statically linked kexec binary, so you probably just want to use that.
Usage:
Once you have the kernel patches and kexec userspace binary in place, just run following command to boot into new kernel:
Code:
kexec --load-hardboot zImage --initrd=initrd.img --mem-min=0x85000000 --command-line="$(cat /proc/cmdline)"
kexec -e
Note the command line parameter - cmdline from bootloader is not added automatically, you have to put it there by yourself.
Currently used by:
MultiROM - I use it to boot different kernels (eg. Ubuntu).
MOSLO - Part of Plasma Active for Nexus 7, also usefull tool for every N7 developer - read more: http://ruedigergad.com/2012/12/09/nexus-7-easily-flashaccess-entire-userdata-partition/
Authors:
This patch was made by Mike Kasick for Samsung Epic 4G. Since that, it was ported to several devices, one of them is Asus Transformer TF201 - I used patch from TF201 and modified it a bit (basically just changed few SoC specific constants). People at #ubuntu-arm helped me out with that, thanks.
Click to expand...
Click to collapse
I'm sorry for picking up this older topic as well, but I always played with the thought of merging kexec support into a kernel and I'm doing one right now.. But my secondary device is a LG G2 and since the era of Lollipop began, somehow MultiBoot just stopped working and nobody can figure out why. I think they even started to build some new concept now.. So before I spark a heated debated by Note 4 users I'd love to know if you have any idea if this patch is still applicable? Altough the only way to find out is to probably just try it lol.
Tasssadar said:
In this post, ....
Click to expand...
Click to collapse
Bro can you please mention on your wiki that kexec isnt supported for x64 devices? It will be great help and save developers hours! I was porting for oneplus 2 when a dev told me that kexec isnt there for x64. I was shocked
Is any alternative available for that? Please reply! Thanks.
All other devs, who cant make multirom to work (lollipop is the x64 era) stop working. Kexec isnt supported for x64. Find an alternative for it.
Can Anyone help me to port this? Here is my patched kernel (ignore arch/arm64) and this is /proc/iomem.
Code:
80000000-854fffff : System RAM
80008000-80fa43ef : Kernel code
81112000-817bf797 : Kernel data
8cb00000-9fefffff : System RAM
9ff00000-9ff3ffff : persistent_ram
9ff40000-9ff7ffff : persistent_ram
9ff80000-9fffffff : persistent_ram
a0000000-ffffefff : System RAM
For kexec_hb_page_addr the value i inseted is 85500000 coz as tasssadar said 884fffff + 1 = 85500000, but I don't know what value add for
Code:
#elif defined(CONFIG_ARCH_MSM8916)
/* Restart using the PMIC chip, see mach-msm/restart.c */
ldr r0, =MSM8916_HARDBOOT
mov r1, #0
str r1, [r0, #0]
loop: b loop
MSM8916_HARDBOOT, and if I compile the kernel it stucks on samsung logo.
If you wish to request omni forks a repository from AOSP, in order to implement a patch into omni, please post this request here. Eventually this will be carried out via jira (http://jira.omnirom.org)
When posting, please give the path to the repository, and a link to what you want to merge, or a description.
For example if you wish to cherry pick a patch into it, a link to the patch and brief description of the reason for the patch.
We'll then have that repository forked and made available on github and gerrit, permitting you to submit your change.
Before you request, please check on github to ensure it isn't already forked!
For example :
frameworks/base - Needing forked so I can introduce multi window functionality (link here to information)
hardware/broadcom/libbt - Mainly for board-specific configurations (link), but newer CM commits also look promising.
If new device bringups aren't planned yet, ignore the followings:
device/lge/p880 and kernel/lge/p880 - Device bringup (kernel has a non-standard naming at CM repo, it should be android_kernel_lge_x3 (x3 is the board name))
vendor/lge (maybe Omni should create one from scratch)
Adam77Root said:
hardware/broadcom/libbt - Mainly for board-specific configurations (link), but newer CM commits also look promising.
If new device bringups aren't planned yet, ignore the followings:
device/lge/p880 and kernel/lge/p880 - Device bringup (kernel has a non-standard naming at CM repo, it should be android_kernel_lge_x3 (x3 is the board name))
vendor/lge (maybe Omni should create one from scratch)
Click to expand...
Click to collapse
We do have a vendor/lge with just mako, although I'm not sure if its current location.
Vendor blob repos are a legal mess, which is why CM kept them at TheMuppets. We'll likely do something similar if we haven't already (I haven't synced since coming home.) Among other reasons to keep them separate is in the case of a DMCA takedown - usually that happens only to a single repo (see the HTC vendor repos earlier this year) but there's always the risk that damage might be more widespread.
android_external_clang
http://review.cyanogenmod.org/#/c/29799/2
Needed for building my msm8960 device (Motorola Photon Q, xt897c).
arrrghhh said:
android_external_clang
http://review.cyanogenmod.org/#/c/29799/2
Needed for building my msm8960 device (Motorola Photon Q, xt897c).
Click to expand...
Click to collapse
CM bootable recovery and some commits over system core
Black_Prince said:
CM bootable recovery and some commits over system core
Click to expand...
Click to collapse
No for CWM - We're working on forking TWRP in, but some fixes still need to be made to allow it to work on devices with unified recovery/boot image. (Probably one of the biggest holdups for the exynos 4210 family - Sonys with unified boot/recovery can at least use Dees_Troy's FOTAKernel trick).
Getting CWM to build in a tree requires hacks all over the tree in multiple repositories. TWRP is much more self-contained, but needs some tweaks to the build system in order to get it to build properly on a userdebug (as opposed to eng) build.
Entropy512 said:
No for CWM - We're working on forking TWRP in, but some fixes still need to be made to allow it to work on devices with unified recovery/boot image. (Probably one of the biggest holdups for the exynos 4210 family - Sonys with unified boot/recovery can at least use Dees_Troy's FOTAKernel trick).
Getting CWM to build in a tree requires hacks all over the tree in multiple repositories. TWRP is much more self-contained, but needs some tweaks to the build system in order to get it to build properly on a userdebug (as opposed to eng) build.
Click to expand...
Click to collapse
Hmm but until the twrp is ported should i test build for some galaxy devices like SG S2 note 1 with cwm ?
It will make me to push changes to git in device tree ... and will be easy to add support
Black_Prince said:
Hmm but until the twrp is ported should i test build for some galaxy devices like SG S2 note 1 with cwm ?
It will make me to push changes to git in device tree ... and will be easy to add support
Click to expand...
Click to collapse
I'll pull up a remote to use for bootable/recovery until we fork (unless plodey already forked it) from TWRP, won't be able to provide it until tonight.
However, right now, it will only build a working recovery if you do an eng build instead of userdebug. If Dees_Troy's talk at BABBQ is ever posted, that's what I was talking about when I trolled him at the end.
Something like:
Code:
. build/envsetup.sh && brunch custom_n7000-eng
or something like that.
Old
def WriteRawImage(self, mount_point, fn):
"""Write the given package file into the partition for the given
mount point."""
fstab = self.info["fstab"]
if fstab:
p = fstab[mount_point]
partition_type = common.PARTITION_TYPES[p.fs_type]
args = {'device': p.device, 'fn': fn}
if partition_type == "MTD":
self.script.append(
'write_raw_image(package_extract_file("%(fn)s"), "%(device)s");'
% args)
elif partition_type == "EMMC":
self.script.append(
'package_extract_file("%(fn)s", "%(device)s");' % args)
Requested
def WriteRawImage(self, mount_point, fn):
"""Write the given package file into the partition for the given
mount point."""
fstab = self.info["fstab"]
if fstab:
p = fstab[mount_point]
partition_type = common.PARTITION_TYPES[p.fs_type]
args = {'device': p.device, 'fn': fn}
if partition_type == "MTD":
self.script.append(
'package_extract_file("%(fn)s", "/tmp/boot.img");'
'write_raw_image("/tmp/boot.img", "%(device)s");' % args
% args)
elif partition_type == "EMMC":
self.script.append(
'package_extract_file("%(fn)s", "%(device)s");' % args)
elif partition_type == "BML":
self.script.append(
('assert(package_extract_file("%(fn)s", "/tmp/%(device)s.img"),\n'
' write_raw_image("/tmp/%(device)s.img", "%(device)s"),\n'
' delete("/tmp/%(device)s.img"));') % args)
else:
raise ValueError("don't know how to write \"%s\" partitions" % (p.fs_type,))
Flash error in write raw image ...
Also can u cherry pick these commits https://github.com/CyanogenMod/android_system_core/commits/cm-10.2/mkbootimg/unpackbootimg.c
My internal SD card isnt got recognsied , there must be some commits missing in vold ...
I dont even know it got formatted or what in flashing ...
All things working WIFI BLUTOOTH TETHERING CALL DATA MSG MMS OMNITORCH
Also u may have look over https://github.com/CyanogenMod/andr...mmit/f22626cdbecfe27c96f205710173458eab14e1a1
and https://github.com/CyanogenMod/andr...mmit/aee5f78ddec238cec016849acaf1d3007b8b1507
https://android.googlesource.com/platform/hardware/broadcom/libbt
Must haz patch:
https://github.com/CyanogenMod/andr...mmit/4028192a4fe8289bf9b7fb202a2bb2c0d85d98c3
//edit: xplod sorted it out already.
android_packages_apps_PackageInstaller
For
HALO and a feat which enables us to see version of the installed and gonna install app
I need this to make it work with my Samsung galaxy s4
I'm not sure if this is the correct thread, but the following two would be great for i9305 support
smdk4412-qcom-common -> needed for i9305 and t0lte (EDIT: I see this one has now been added)
Thanks!
Hey @pulser_g2,
wondering if i could have the following repositories added in for jf devices,
all features are fully functional with these repositories : branch: cm-10.2 for all
device_samsung_jf-common
android_device_samsung_jflteatt
android_kernel_samsung_jf
CyanogenMod/android_hardware_samsung
CyanogenMod/android_device_samsung_msm8960-common
CyanogenMod/android_device_samsung_qcom-common
@pulser_g2
I just talked to @maxwen and he told me i should post here the needed stuff:
I managed to fix the radio issues today on m7, but i need additionally these commits:
https://github.com/TheMuppets/proprietary_vendor_htc/commit/7bbbe83823525090e7d94c47b439c09a254b380f
https://github.com/TheMuppets/proprietary_vendor_htc/commit/19ed957678d13b489da78d704b27811030688078
https://github.com/TheMuppets/proprietary_vendor_htc/commit/51b006bc8f05757c7dd82361ce6d985e996af360
and please DO NOT merge this: https://github.com/TheMuppets/proprietary_vendor_htc/commit/2b86687a460030199fa42d49207957ce285c1a53
as its not needed and breaks build (I allready have everything in m7-common so no need for vendor)
Thanks in advance
@pulser_g2
we dont need to update anything, please forget my post above, i managed to get it working without all these commits and the right vendor
hardware/qcom/gps - Needing forked so I can build the needed GPS module into my Omnirom build.
The link to this repository is: https://github.com/CyanogenMod/android_hardware_qcom_gps/tree/cm-10.2
I hope it gets included, this saves me a ton of time pulling stuff from other repositories.
Greetings PsychoGame
Galaxy S I9000 (galaxysmtd)
@pulser_g2 Device repos are already forked. Kernel is missing: https://github.com/OmniGalaxyS/android_kernel_samsung_aries
It has android-4.3 and android-4.4 branches up.
Device rocking with Omni!
See you!
Fail
PsychoGame said:
hardware/qcom/gps - Needing forked so I can build the needed GPS module into my Omnirom build.
The link to this repository is: https://github.com/CyanogenMod/android_hardware_qcom_gps/tree/cm-10.2
I hope it gets included, this saves me a ton of time pulling stuff from other repositories.
Greetings PsychoGame
Click to expand...
Click to collapse
I also need android_hardware_qcom_gps (probably best from https://github.com/markcs/android_hardware_qcom_gps/tree/cm-11.0)
Xperia C3 first custom rom base original Cyanogenmod 12.1
This is just Test version
this rom release. cause I get many logs and yours participation
working now
cellurar Networking
Wi-Fi
Ambient light sensor
Magnetometer
audio
not working now
camera(i find reason why rebroken)
gps(but maybe working base ip or router)
brightness control
Accelerometer
known bugs
turn off hotspt after not working wifi(reboot please)
change dpi on settings. if you get buggy or black screen(just reboot please)
I can release possible..
but we can flash that made for c3 recovery...
so first time must use fastboot...
XDA:DevDB Information
Xperia C3 Temp ROM, ROM for the Sony Xperia C
Contributors
wwwhana
Source Code: https://github.com/wwwhana/android_device_sony_wukong
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Current Beta Version: build 151201
Beta Release Date: 2015-12-02
Created 2015-12-01
Last Updated 2015-12-07
Download Links
151201 build
media fire
Change logs
Change logs
[15/12/01]firts release
Need UNLOCK
if you not yet follow this guid
The responsibility of all problems for you.
Fastboot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot, boot.img, system.img in same folder
Click to expand...
Click to collapse
Flashtool
select button icon like thunder
select fastboot
click select kernel to flash
select boot.img
click select system to flash
select system.img
you must install fastboot driver
Click to expand...
Click to collapse
if you participation develop Xperia C3 cm?
this is my local manifest
if you try add vendor blub and resulte share please
or try driver build and after result. please share
Code:
<manifest>
<default revision="refs/heads/cm-12.1" remote="github" sync-c="true" sync-j="4"/>
<remote name="sony" fetch="git://github.com/sonyxperiadev/" />
<project name="wwwhana/android_device_sony_wukong" path="device/sony/wukong"/>
<project name="wwwhana/android_device_sony_msm8226-common" path="device/sony/msm8226-common" />
<project name="wwwhana/android_kernel_sony_wukong" path="kernel/sony/wukong" revision="19.4.A.0.xxx" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" />
<project name="CyanogenMod/android_device_sony_common" path="device/sony/common" />
<project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm"/>
<project name="CyanogenMod/android_hardware_sony_DASH" path="hardware/sony/dash"/>
<project name="CyanogenMod/android_hardware_sony_thermanager/" path="hardware/sony/thermanager/"/>
<project path="hardware/qcom/camera" name="wwwhana/android_hardware_qcom_camera" groups="device" remote="github" />
<project path="vendor/sony/system/macaddrsetup" name="macaddrsetup" groups="device" remote="sony" revision="master" />
<project path="vendor/sony/system/timekeep" name="timekeep" groups="device" remote="sony" revision="master" />
</manifest>
Reserved
Reserved
Sensor info
almost sensor is not working
this is find our device sensor list
that help find drivee.
i try build dash but that is hard....
some sensor drive in dash code ...
Sensors (14)
BMA250 Accelerometer
Vendor BOSCH
Range 39.240005 m/s²
Resolution 0.07661438 m/s²
Power 0.139 mA
Delay 8333 μs
AK8963 Magnetometer
Vendor AKM
Range 4911.9995 μT
Resolution 0.14953613 μT
Power 5.0 mA
Delay 16666 μs
AK8963 Magnetometer Uncalibrated
Vendor AKM
Range 4911.9995 μT
Resolution 0.14953613 μT
Power 5.0 mA
Delay 16666 μs
Proximity Prx_ALS Sensor
Vendor ams AG
Range 5.0 cm
Resolution 5.0 cm
Power 12.675 mA
Delay On Trigger
Light Prx_ALS Sensor
Vendor ams AG
Range 10000.0 lx
Resolution 0.009994507 lx
Power 0.175 mA
Delay 66666 μs
Gravity
Vendor QTI
Range 39.240005 m/s²
Resolution 0.07661438 m/s²
Power 5.1389923 mA
Delay 16666 μs
Linear Acceleration
Vendor QTI
Range 39.240005 m/s²
Resolution 0.07661438 m/s²
Power 5.1389923 mA
Delay 16666 μs
Rotation Vector
Vendor QTI
Range 1.0
Resolution 5.9604645E-8
Power 5.1389923 mA
Delay 16666 μs
Step Detector
Vendor QTI
Power 0.13899231 mA
Delay On Trigger
Step Counter
Vendor QTI
Power 0.13899231 mA
Delay On Trigger
Significant Motion Detector
Vendor QTI
Power 0.13899231 mA
Delay On Trigger
GeoMagnetic Rotation Vector
Vendor QTI
Range 1.0
Resolution 5.9604645E-8
Power 5.1389923 mA
Delay 16666 μs
Orientation
Vendor QTI
Range 360.0°
Resolution 0.1°
Power 5.1389923 mA
Delay 16666 μs
Tilt Detector
Vendor QTI
Range 1.0
Resolution 1.0
Power 0.13899231 mA
Delay On Trigger
Thanks, will flash this weekend.
wwwhana said:
Reserved
Click to expand...
Click to collapse
Hi, I can't seem to reboot into recovery. The phone shows the purple LED then reboots at the Sony text, then reboots again into the normal sequence. Installing XZDR recovery did not help either.
Edit: Could you repack this into a working flashable zip? That way maybe I can get the recovery to work, so reverting back to stock rom won't be so tedious.
Temporary screen brightness fix: Go to Display > Live Display > Colour calibration and set the Red, Green, Blue value at 35%. Any amount works fine as long as they are the same number.
More edit: Yup, not gonna touch until the recovery is confirmed to be working as I depend on it as a backdoor in case anything goes wrong. I lost recovery, using fastboot to get it back failed, now I'm reflashing again to stock.
recovery is later....
AutumQueen92 said:
Hi, I can't seem to reboot into recovery. The phone shows the purple LED then reboots at the Sony text, then reboots again into the normal sequence. Installing XZDR recovery did not help either.
Edit: Could you repack this into a working flashable zip? That way maybe I can get the recovery to work, so reverting back to stock rom won't be so tedious.
Temporary screen brightness fix: Go to Display > Live Display > Colour calibration and set the Red, Green, Blue value at 35%. Any amount works fine as long as they are the same number.
More edit: Yup, not gonna touch until the recovery is confirmed to be working as I depend on it as a backdoor in case anything goes wrong. I lost recovery, using fastboot to get it back failed, now I'm reflashing again to stock.
Click to expand...
Click to collapse
i'm sorry. The first goal is working all function about hardware....after support recovery.
and you say flashable zip... i will try after my This semester final exams that is next week.
so i can't do it now....
maybe possible next friday on KST
my focus is sensors
i hard working about find sensors source and build module
but that is not easy
not working sensor that
Vendor: QTI
or
BMA250
and last
i think that some differnece light sensor...
cause not working in light module on wukong
so that is not working front led and bright control....
Thank u
use my test rom
wwwhana said:
i'm sorry. The first goal is working all function about hardware....after support recovery.
and you say flashable zip... i will try after my This semester final exams that is next week.
so i can't do it now....
maybe possible next friday on KST
my focus is sensors
i hard working about find sensors source and build module
but that is not easy
not working sensor that
Vendor: QTI
or
BMA250
and last
i think that some differnece light sensor...
cause not working in light module on wukong
so that is not working front led and bright control....
Thank u
use my test rom
Click to expand...
Click to collapse
sure, take your time. I'll wait for recovery and use stock rom since I'm kinda paranoid about this stuff
Edit: Recovery is also needed to install gapps and xposed. no rush though >.>
Working: CAMERA
Click to expand...
Click to collapse
How did you manage that? We haven't got the source... Surely the libraries from the Sony ROM don't fully work with CM12.1?
Anyways, My builds from source are finally compiling without errors (so far...), so I'll post a flashable zip in my thread when they finish. I've included the qcom camera source, but I don't know if it will work yet, as it is still building... Keeping fingers crossed...
rebroken camera r-.-
while try another thing...
so camera is maybe not working
i release cause working when test..
but i try rollback but notworking;;;
i will fix after next week...
and i find some sensor and try but that not easy....
AK8963 is exist source
but have compile error;;
so that try fix next week
Testing...
Posting because the subscribed function seems bugged. Hope this resets it
@wwwhana, @Riccorbypro, @cezer kiran
I found something that works!
AutumQueen92 said:
@wwwhana, @Riccorbypro, @cezer kiran
I found something that works!
Click to expand...
Click to collapse
that is working??
i boot now that
wwwhana said:
that is working??
i boot now that
Click to expand...
Click to collapse
Yes it does. There's a build.prop file in there, replace it with the one from C3. Do not flash the t2fix.zip.
I've asked if the OP minds if I adapt this and post it on these forums, hope he says yes. Would be really nice to debloat this ROM and have xposed as well...
Sent via Carrier Pigeon
HEY BRO I AM CRAZILY
WAITING FOR THIS ROM PLEASE GIVE ME THE DATES WHEN
YOU WILL FINALLY RELEASE A STABLE ROM
MAKE IT SOON BRO
A SPECIAL THANKS TO YOU FROM ALL THE C3 USERS:good::good::good:
nihar34 said:
HEY BRO I AM CRAZILY
WAITING FOR THIS ROM PLEASE GIVE ME THE DATES WHEN
YOU WILL FINALLY RELEASE A STABLE ROM
MAKE IT SOON BRO
A SPECIAL THANKS TO YOU FROM ALL THE C3 USERS:good::good::good:
Click to expand...
Click to collapse
Project is abandoned.
AutumQueen92 said:
Project is abandoned.
Click to expand...
Click to collapse
HEY THERE AUTUMQUEEN WHY DID YOU ABANDONED THE PROJECT BRO
I FLASHED THE ROM ON MY XPERIA C3 AND THINGS ARE WORKING NICE
CAMERA, MOBILE DATA, AUDIO,WIFI, HOTSPOT ALL ARE WORKING
THE PROBLEM IS JUST WITH THE SENSORS AND THE BRIGHTNESS OF THE SCREEN
EXCEPT THAT EVERY THING JUST WORKS LIKE CHARM. :good::good::good:
Since Xiaomi released source code for kernel, I tried to build it.
https://github.com/Dhoine/android_kernel_cereus
Current status of this - it compiles, boots, but unusable.
Bugs:
Broken bluetooth
Broken wifi
Soft-reboots after some time
Propably, more bugs that remained undiscovered because of reboots.
Tested with miui 9 on cereus 3/32.
--------
You can test builded kernel using this:
GDrive
Use Carliv image Kitchen to repack your rom's boot.img, then flash it via fastboot (UNLOCKED BOOTLOADER REQUIRED). To restore working state after testing, flash stock boot image again.
WARNING
Our kernel uses android regular boot.img format, not MTK.
---------
If you want to build this, any manual for building kernel will fit. I used google's android arm eabi 4.9 toolchain, our arch is arm, defconfig is cereus_defconfig.
For now, I don't have enough time to take a closer look at this (work, university exams), so, any help (last_kmsg, dmesg, pull requests) will be appreciated.
Wait seriously? Does that mean that i can buil LOS rom now? I have my UbuntuVM with whole LOS source code downloaded but i got stuck at no kernel found for cereus. So it might work now(Im extremely new to linux) I'll try to build the rom asap
TanRayCz said:
Wait seriously? Does that mean that i can buil LOS rom now? I have my UbuntuVM with whole LOS source code downloaded but i got stuck at no kernel found for cereus. So it might work now(Im extremely new to linux) I'll try to build the rom asap
Click to expand...
Click to collapse
This kernel for now won't really help with building los. I haven't find any device tree for our SoC (or close). MTK always requre a ton of patches to android sources. But i have reference MTK 9.0 android sources for this SoC - ALPS (can't share, it's probably illegal, but you can find them on 4pda.ru, if you want). It builds on almost unmodified reference device tree, but i haven't tested it on device. First, we need to make this kernel usable.
[email protected] said:
This kernel for now won't really help with building los. I haven't find any device tree for our SoC (or close). MTK always requre a ton of patches to android sources. But i have reference MTK 9.0 android sources for this SoC - ALPS (can't share, it's probably illegal, but you can find them on 4pda.ru, if you want). It builds on almost unmodified reference device tree, but i haven't tested it on device. First, we need to make this kernel usable.
Click to expand...
Click to collapse
This may not really help, but can you try that kernel again after upgrading to MIUI 10.2.4 ?
EDIT : See https://www.kimovil.com/en/list-smartphones-by-processor/mediatek-helio-p22-mt6762 for a list of devices with MT6762. Probably we can check out their trees?
EDIT 2 : It seems like our Redmi 6 is the only device with available kernel source in that list.
EDIT 3 : Try this?
minhducsun2002 said:
EDIT : See https://www.kimovil.com/en/list-smar...lio-p22-mt6762 for a list of devices with MT6762. Probably we can check out their trees?
EDIT 2 : It seems like our Redmi 6 is the only device with available kernel source in that list.
Click to expand...
Click to collapse
Maybe them exists, but I haven't found them.
minhducsun2002 said:
This may not really help, but can you try that kernel again after upgrading to MIUI 10.2.4 ?
---------------------
EDIT 3 : Try this?
Click to expand...
Click to collapse
I finally finished my university exams, so now I have some free time to play with it.
The kernel you link is just forked xiaomi sources merged to linux 4.9 kernel. It shouldn't be buildable at all, since there is the same problem in sources I "fixed" with this.
Probably, this too.
[email protected] said:
I finally finished my university exams, so now I have some free time to play with it.
The kernel you link is just forked xiaomi sources merged to linux 4.9 kernel. It shouldn't be buildable at all, since there is the same problem in sources I "fixed" with this.
Probably, this too.
Click to expand...
Click to collapse
[email protected] said:
Maybe them exists, but I haven't found them.
Click to expand...
Click to collapse
You're right, they're identical.
By the way, I couldn't find any implementation available for our Helio P22; the chipset itself is fairly new, thus not many devices have the source code available.
minhducsun2002 said:
This may not really help, but can you try that kernel again after upgrading to MIUI 10.2.4 ?
Click to expand...
Click to collapse
Ok, i've tested it on latest GS. It seems to work a way better. At least, it doesnt reboot after few seconds of usage. It makes things a lot easier.
Tested a few more things:
-sound - works
-camera (both photo and video) - works
- mobile data - works
- phone calls - work
- dual sim -works
- all sensors work
The only thing i was unable to test is gps. It didn't worked for me, but i was inside 9-floor building near the window to inner corner of building... So idk.
And usb otg - since i don't have adapder.
After this I can tell, that there are only 2 major bugs - wifi and bluetooth.
Maybe gps, fm radio and exfat too. This is modules loading problem, I think (though, there shouldn't be any modules, drivers are marked as built-in in config, but .ko files for them exist in /vendor/lib/modules)
[email protected] said:
Ok, i've tested it on latest GS. It seems to work a way better. At least, it doesnt reboot after few seconds of usage. It makes things a lot easier.
Tested a few more things:
-sound - works
-camera (both photo and video) - works
- mobile data - works
- phone calls - work
- dual sim -works
- all sensors work
The only thing i was unable to test is gps. It didn't worked for me, but i was inside 9-floor building near the window to inner corner of building... So idk.
And usb otg - since i don't have adapder.
After this I can tell, that there are only 2 major bugs - wifi and bluetooth.
Maybe gps, fm radio and exfat too. This is modules loading problem, I think (though, there shouldn't be any modules, drivers are marked as built-in in config, but .ko files for them exist in /vendor/lib/modules)
Click to expand...
Click to collapse
Yeah, Treble definitely makes things easier.
Nevertheless I'm trying to integrate those kernel modules into the compiled zImage - there's no modprobe in Android, sadly.
Adding modules support and disabling modules versions check in config didn't help.
I can't find any source files in kernel sources, from which these modules can be built. Maybe, they are built from separate platform code (they are placed in vendor, so...) Need to download ALPS (brrr, around 50 gb of tar.bz2 archives) to check it.
I've looked into reference mediatek 4.9 kernel sources and found this:
Code:
# Do build-in for Makefile checking
# export CONFIG_WLAN_DRV_BUILD_IN=y
ifeq ($(CONFIG_WLAN_DRV_BUILD_IN),y)
PATH_TO_WMT_DRV = vendor/mediatek/kernel_modules/connectivity/common
PATH_TO_WLAN_CHR_DRV = vendor/mediatek/kernel_modules/connectivity/wlan/adaptor
PATH_TO_WLAN_DRV = vendor/mediatek/kernel_modules/connectivity/wlan/core/gen4m
ABS_PATH_TO_WMT_DRV = $(srctree)/../$(PATH_TO_WMT_DRV)
ABS_PATH_TO_WLAN_CHR_DRV = $(srctree)/../$(PATH_TO_WLAN_CHR_DRV)
ABS_PATH_TO_WLAN_DRV = $(srctree)/../$(PATH_TO_WLAN_DRV)
# check wlan driver folder
ifeq (,$(wildcard $(ABS_PATH_TO_WMT_DRV)))
$(error $(ABS_PATH_TO_WMT_DRV) is not existed)
endif
ifeq (,$(wildcard $(ABS_PATH_TO_WLAN_CHR_DRV)))
$(error $(ABS_PATH_TO_WLAN_CHR_DRV) is not existed)
endif
ifeq (,$(wildcard $(ABS_PATH_TO_WLAN_DRV)))
$(error $(ABS_PATH_TO_WLAN_DRV) is not existed)
endif
$(warning symbolic link to $(PATH_TO_WMT_DRV))
$(warning symbolic link to $(PATH_TO_WLAN_CHR_DRV))
$(warning symbolic link to $(PATH_TO_WLAN_DRV))
$(shell unlink $(srctree)/$(src)/wmt_drv)
$(shell unlink $(srctree)/$(src)/wmt_chrdev_wifi)
$(shell unlink $(srctree)/$(src)/wlan_drv_gen4m)
$(shell ln -s $(ABS_PATH_TO_WMT_DRV) $(srctree)/$(src)/wmt_drv)
$(shell ln -s $(ABS_PATH_TO_WLAN_CHR_DRV) $(srctree)/$(src)/wmt_chrdev_wifi)
$(shell ln -s $(ABS_PATH_TO_WLAN_DRV) $(srctree)/$(src)/wlan_drv_gen4m)
# for gen4m options
export CONFIG_MTK_COMBO_WIFI_HIF=axi
export MTK_COMBO_CHIP=CONNAC
export WLAN_CHIP_ID=6765
export MTK_ANDROID_WMT=y
# Do build-in for xxx.c checking
subdir-ccflags-y += -D MTK_WCN_REMOVE_KERNEL_MODULE
subdir-ccflags-y += -D MTK_WCN_BUILT_IN_DRIVER
obj-y += wmt_drv/
obj-y += wmt_chrdev_wifi/
obj-y += wlan_drv_gen4m/
endif
No such code in xiaomi's source. And this prooves my words: these modules CAN BE BUILT IN and SOURCES FOR THEM ARE IN ALPS. I have to download this ton of ****...
-------
I tried to backpors drivers from 9.0 - no success. It compiles,but doesn't boot. I tried to hack modules loading - no success too.
[email protected] said:
Adding modules support and disabling modules versions check in config didn't help.
I can't find any source files in kernel sources, from which these modules can be built. Maybe, they are built from separate platform code (they are placed in vendor, so...) Need to download ALPS (brrr, around 50 gb of tar.bz2 archives) to check it.
Click to expand...
Click to collapse
Most of the time those binaries are not open-source (you probably know vendor blobs for Google devices are too, but that is a different story). Nevertheless I don't really get why kernel modules are placed in
Code:
/vendor
- after all, mobile devices don't have hot-plugging hardware that requires dynamic LKM loading, why do they separate them out?
I'll attempt to crawl the web for those sources while waiting for Mi Unlock to allow my device being unlocked (the waiting period sucks).
[email protected] said:
I've looked into reference mediatek 4.9 kernel sources and found this:
No such code in xiaomi's source. And this prooves my words: these modules CAN BE BUILT IN and SOURCES FOR THEM ARE IN ALPS. I have to download this ton of ****...
-------
I tried to backpors drivers from 9.0 - no success. It compiles,but doesn't boot. I tried to hack modules loading - no success too.
Click to expand...
Click to collapse
1. Backports? How?
2. In which file did you got those lines?
3. Indeed those modules' source are removed from our tree - if you have the link, I don't really mind having another 50GB occupied on my PC to get those source code.
minhducsun2002 said:
1. Backports? How?
2. Indeed those modules' source are removed from our tree - if you have the link, I don't really mind having another 50GB occupied on my PC to get those source code.
Because attached below is the existence of the modules. /shrug
Click to expand...
Click to collapse
I already said that i have leaked mtk alps 9.0 sources These modules have sources, they are not prebuilt. I managed to built in them, but kernel doesn't boot at all after that. And i can't take any logs because the system dies before adb init.
Ok, after one little, but very cruel hack modules are fixed. Enjoy testing the kernel.
https://drive.google.com/open?id=1Z3p2fAWOZFyp045QMNV6vhLZvj9ZZPSY
[email protected] said:
Ok, after one little, but very cruel hack modules are fixed. Enjoy testing the kernel.
Click to expand...
Click to collapse
does it work well?
Lonewolf_1210 said:
does it work well?
Click to expand...
Click to collapse
Users from 4pda reported it fully working.
---------------------
Soon will be build with usb network adapters support enabled (requested by romanxdream from 4pda).
P.S. I'm not adding everything requested to kernel. But this was only config modification.
-------
I don't check xda often, so there can be a huge delay in my responses.
[email protected] said:
Users from 4pda reported it fully working.
---------------------
Soon will be build with usb network adapters support enabled (requested by romanxdream from 4pda).
P.S. I'm not adding everything requested to kernel. But this was only config modification.
-------
I don't check xda often, so there can be a huge delay in my responses.
Click to expand...
Click to collapse
Great job then, hope for a custom rom coming soon
Ok, download link to all versions. I'll edit the first post later.
https://drive.google.com/open?id=1yEZRS8L8bPgkk58tT5Uv2b-vsLqk7aql
Should we make a telegram group for this?