Related
hy all
this is an project starter for android 3.4 kernel development for all msm7x30 mogami devices
sources are hosted on
https://github.com/freexperia/android_kernel_semc_msm7x30
br
J
Project Status
- we got initial branch after diffing lost of branches
M7630AABBQMLZA203029A
https://www.codeaurora.org/gitweb/q...it;h=4b2b84c6a0b6d29864e982a7aecc223acfd2eaa1
forked to our git and with mogami patches aplied
https://github.com/freexperia/android_kernel_semc_msm7x30/tree/M7630AABBQMLZA203029A
latest CAF tag for 7630 not usefull for now
https://www.codeaurora.org/xwiki/bin/QAEP/release
"November 16, 2012 M7630AABBQMLZA40701070 - msm7630 - M7630AABBQMLZA40701070.xml - 04.01.02" android 4.1
ETA
depending on problems and developers that will join
from 6 months to NEVER
This is a bold task. Perhaps you could look at the developments of irii-soft (and some others), they have replaced some crap Sony-specific code with generic wrappers. Main obstacle if I remember is memory maps now, there was an issue with partition maps but ATAG can be easily over-ridden via kernel command-line.
Getting it to boot should be trivial, sound and video will be difficult, and RIL may be never working due to lack of sources. Regardless, all the best. When I have more time I plan to help irii with his work on a "generic" 2.x kernel newer than what we have (because 3.x seems outrageous at this point).
Is there a wiki, a forum or something like that lists all the non-standard things that have already been found ? (some base of work to do)
Boudin said:
Is there a wiki, a forum or something like that lists all the non-standard things that have already been found ? (some base of work to do)
Click to expand...
Click to collapse
Easy to do yourself - download official SEMC kernel source and diff it with the same version of the linux baseline kernel. So to port to newer kernel you can isolate or "extract" the specific code that has been added and changed, and merge or "inject" that into a newer kernel. Easier said than done though, there are massive changes even in linux kernel revisions (0.0.x.0) - let alone alone new majors and minors (x.x.0.0).
There wouldn't be a wiki or anything of this research, because documenting it all would take an unrealistic amount of labor. Considering there are only a small handful of developers capable of it, there's no point. Besides, that's what GitHub and commit logs are for.
To FXP team,
I don't know if you know or not or even got this far in the development stage but I just wanted to point out a couple of things which may or may not help you...
So with the 3.4 kernel brings newer WiFi drivers which will give a better connection signal on wpa2 security but you might find that devices won't be able to connect to open security networks and WiFi hotspot will probably be broken. I'm posting this as on my gnex using custom kernel (FrancoFransico) he incorporated the 3.4 WiFi drivers a few times and broken hotspot and not being able to use open security WiFi networks were repeatedly reported problems.
I think it may be something hardware specific which allows these features to work on the 3.4 WiFi drivers specific to the nexus 4? You may have more luck trying the 3.0.xx WiFi drivers and getting those to work fully.
Best of luck to you guys!
Sent from my Galaxy Nexus
I'm pretty sure wifi is way down on the priority list, not to be rude but really - who cares about that now. Priority list would be like this:
(1) Get it to boot
(2) Fix primary/critical hardware-specific code for msm7k and qcom platform (display, audio)
(3) Fix RIL
(4) Fix secondary hardware (sensors, bluetooth, wifi)
One step at a time. Getting wifi will probably be trivial because bcm sources are part of the mainline kernel.
With that said, I'm unsubscribing from this thread now. There is massive work to be done and I can see this thread is just going to be filled with posts that have nothing to do with actual development.
All non-dev related posts, and especially "Thank You" posts, will be deleted without further notice. If I have to delete 5 pages of useless posts again, this thread will be locked.
Thank you!
We have tried for a long time already (as you may already know).
https://github.com/adridu59/semc-msm-3.4/commits/master
https://github.com/adridu59/semc-msm-2.6.35
https://github.com/adridu59/android-msm-2.6.35
https://github.com/ExPeacer/CAF_android-msm-3.0/commits/master
https://github.com/ExPeacer/CAF_android-msm-2.6.32
Have fun with it anyways.
adridu59 said:
We have tried for a long time already (as you may already know).
https://github.com/adridu59/semc-msm-3.4/commits/master
https://github.com/adridu59/semc-msm-2.6.35
https://github.com/adridu59/android-msm-2.6.35
https://github.com/ExPeacer/CAF_android-msm-3.0/commits/master
https://github.com/ExPeacer/CAF_android-msm-2.6.32
Have fun with it anyways.
Click to expand...
Click to collapse
Whats the progress so far on this? Bootable already?
CosmicDan said:
Easy to do yourself - download official SEMC kernel source and diff it with the same version of the linux baseline kernel. So to port to newer kernel you can isolate or "extract" the specific code that has been added and changed, and merge or "inject" that into a newer kernel. Easier said than done though, there are massive changes even in linux kernel revisions (0.0.x.0) - let alone alone new majors and minors (x.x.0.0).
There wouldn't be a wiki or anything of this research, because documenting it all would take an unrealistic amount of labor. Considering there are only a small handful of developers capable of it, there's no point. Besides, that's what GitHub and commit logs are for.
Click to expand...
Click to collapse
I was asked by some user of this forum to give some kernel porting guidelines in this thread, so let me introduce myself first. I'm the developer of 3.0.x kernel for Samsung Galaxy Spica (also several other projects for Spica and Galaxy Apollo/Galaxy 3) and currently also Linux kernel developer at Samsung Poland R&D Center. Porting the kernel for Spica was a difficult task, because of poor quality of original kernel code, which required rewriting from scratch most of it, but it was very educational.
It's not easy to give advice, but I'd say that taking all the differences from clean kernel and applying all of that on top of newer version is what should be avoided. Of course those differences should be collected to see what was changed by the manufacturer, but this should be only used for further analysis, not as a ready code.
Another thing, rather than using the mainline Linux kernel to compare your phone sources with, it should be better to use Android kernel from Google's kernel/common tree (see https://www.codeaurora.org/gitweb/quic/la/?p=kernel/common.git;a=summary for older version archive) bumped to the same minor version using minor patches (found on kernel.org) or, possibly even better way, by pulling appropriate version tag from kernel.org git on top of proper branch of Android kernel tree. This will elminate Google's changes (that would be already available in your new base - android-3.4 branch of kernel/common) from the diff.
For getting the diff, I would personally also use Git. If you create a branch in your working tree which contains Android kernel in the version corresponding to your device kernel (using the way I described in previous paragraph), then copying your device kernel sources onto your working tree (remember to make distclean both trees to remove any compiled/generated files) will allow you to see the differences using git status and git diff. (See http://gitimmersion.com/ if you want to learn more about Git.)
Now it's important to split the changes into logically separate parts, for example core changes in arch/arm/mach-whatever_suitable_for_your_device, adding of particular drivers in drivers/, sound/ and include/, modifications to core kernel code in any other directories. It's essential to check whether all the changes are really required or not and why, because minimalizing the set of changes required to be replayed on top of your new base kernel sources will simplify your work.
After collecting all the changes, it's the time to apply them on top of your new kernel sources. All the changes should be applied one by one, checking how much the component that is being touched has changed since your old kernel and adjusting the changes properly. After applying each change, it should be verified that the kernel at least compiles, although it would be even better if you could get the kernel without any (or almost any) modification to boot to some state, e.g. showing something on the console (any chance to get access to serial console on your device?), and then check if it still boots after applying each next change.
Some links that might be useful:
- Linux cross reference, for comfortable reading of kernel code - http://lxr.linux.no/+trees
- Linux Device Drivers, a book about kernel programming - http://lwn.net/Kernel/LDD3/
- Git Immersion, a great Git tutorial - http://gitimmersion.com/
- Android kernel/common repository with full archive - https://www.codeaurora.org/gitweb/quic/la/?p=kernel/common.git;a=summary
- Linux stable repository, with all version tags - http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
Hopefully what I wrote will be helpful in your project. Good luck and best regards.
Hey tom3q,
thanks a lot for leaving some useful statements here!
tom3q said:
Another thing, rather than using the mainline Linux kernel to compare your phone sources with, it should be better to use Android kernel from Google's kernel/common tree (see https://www.codeaurora.org/gitweb/quic/la/?p=kernel/common.git;a=summary for older version archive) bumped to the same minor version using minor patches (found on kernel.org) or, possibly even better way, by pulling appropriate version tag from kernel.org git on top of proper branch of Android kernel tree.
Click to expand...
Click to collapse
I digged for some base kernel for a while.
Found a chromium msm kernel 2.6.32.9 at codeaurora (i know this is not Android).
Anyway, the diff against stock was ~30MB... quite too much.
Like i assumed many basic things are missing as well, so too much to start from.
I guess, i'll step through the other projects... might try 2.6.32-rc8 from the msm tree... just for fun of course :angel:
tom3q said:
After applying each change, it should be verified that the kernel at least compiles, although it would be even better if you could get the kernel without any (or almost any) modification to boot to some state, e.g. showing something on the console (any chance to get access to serial console on your device?), and then check if it still boots after applying each next change.
Click to expand...
Click to collapse
Nice point... i like these hardware hacks and asked about testpoints for UART3 on the Pro mainboard a few days ago.
It's mentioned and so far i got it, initialized in stock kernel as well. Unfortunately no-one seems to know anything about these testpoints.
Anyway i don't want to spam this thread, so thanks for your attention
Regards,
scholbert
hy
scuse my ignorance
but
HOW do you compile an kernel ?
and maybe someone can explain what is the difference between bring-up and port
scholbert said:
Hey tom3q,
thanks a lot for leaving some useful statements here!
I digged for some base kernel for a while.
Found a chromium msm kernel 2.6.32.9 at codeaurora (i know this is not Android).
Anyway, the diff against stock was ~30MB... quite too much.
Like i assumed many basic things are missing as well, so too much to start from.
I guess, i'll step through the other projects... might try 2.6.32-rc8 from the msm tree... just for fun of course :angel:
Nice point... i like these hardware hacks and asked about testpoints for UART3 on the Pro mainboard a few days ago.
It's mentioned and so far i got it, initialized in stock kernel as well. Unfortunately no-one seems to know anything about these testpoints.
Anyway i don't want to spam this thread, so thanks for your attention
Regards,
scholbert
Click to expand...
Click to collapse
FXP said:
hy
scuse my ignorance
but
HOW do you compile an kernel ?
and maybe someone can explain what is the difference between bring-up and port
Click to expand...
Click to collapse
I would say that porting is moving and correcting sources from 2.6.32 kernel in our case into 3.x. And bring up is writing particular drivers from scratch?
Sent from my Nexus 7
voyteckst said:
I would say that porting is moving and correcting sources from 2.6.32 kernel in our case into 3.x. And bring up is writing particular drivers from scratch?
Sent from my Nexus 7
Click to expand...
Click to collapse
ok
nice explanation
look on first page
diff is 5mb on proper tag
pushed on github
nice to see so many developers trying to help
FXP said:
diff is 5mb on proper tag
pushed on github
Click to expand...
Click to collapse
Sorry to throw my 3 cents again, but seeing the repository on github, I'd recommend you to use some time to go through Git Immersion. Even if it takes some time, it will simplify your further work, as Git used properly can really make many things easier.
Otherwise, the diff itself looks mostly fine as a starting point, although some of the differences can be probably eliminated.
tom3q said:
Sorry to throw my 3 cents again, but seeing the repository on github, I'd recommend you to use some time to go through Git Immersion. Even if it takes some time, it will simplify your further work, as Git used properly can really make many things easier.
Otherwise, the diff itself looks mostly fine as a starting point, although some of the differences can be probably eliminated.
Click to expand...
Click to collapse
sony added too many changes to be usefull
since there are several api changes on 32->3.x diff is no good
we have to start from clean board-7x30 and populate devices porting drivers 1 by 1
we have to try an device bringup based on sony changes
This thread is intended for developers and others who can contribute to the project
If you think you can contribute, please do so
Standard disclaimer:
I am not responsible if anything happens to your device
Status:
Device specific build of Ubuntu's minimal cm10.1 build ready
Ready for flashing
Working:
Touch screen
ADB
Browser (Although no net access yet)
You can browse and get a feel of the entire OS, including the homescreen (unity desktop), multitasking (the cool new way to switch between apps), etc.
Since it is a preview, many apps are dummy apps.
Screenshots:
Check them out here
Video:
Here is a video of the fresh new OS in action on the O2x made by JordanRulz
Download links:
Ubuntu touch preview (raring ringtail)
Current build of Ubuntu-CM10.1 (old bootloader)
New bootloader build by delaya73:
cm-10.1-20130604-UNOFFICIAL-p990.zip
Older Ubuntu phone quantal image
older build 2 of Ubuntu-CM10.1 by delaya73
older build 1 of Ubuntu-CM10.1 by delaya73 for the new bootloader
TWRP latest version is recommended (CWM 6.x may work too)
Note:
The raring/quantal image is large, but thankfully gets installed on the data partition, thus saving our small system partition the burden
Source:
Ubuntu-cm10 source
Building instructions:
Building instructions are similar to building CM10 (refer Raum's guide) till repo sync (instead of official cm10 repo, use above source during repo init)
Dont forget to add device props in "local_manifests" (local_manifest.xml is deprecated). Add the following in local_manifests:
Code:
(Taken from Raum's guide, thanks to him)
After syncing the repo,
1. cd device/lge/p990, connect your device running cm10.1 with usb debugging on, and then ./extract-files.sh
2. In device/lge/p990/fstab.p990, remove "nosuid" from data partition
3. In kernel/lge/star/arch/arm/configs, in cyanogenmod_p990_defconfig, add the following:
Code:
CONFIG_SYSVIPC=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_DEVTMPFS=y
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_FANOTIFY=y
CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
CONFIG_FSNOTIFY=y
CONFIG_SWAP=y
# CONFIG_ANDROID_PARANOID_NETWORK is not set
4. Go to ubuntu folder inside your source folder and do
Code:
bzr branch lp:phablet-extras/libhybris hybris
bzr branch lp:platform-api platform-api
If you didnt have bzr, get it first using
Code:
sudo apt-get install bzr
Now you can build. This build would be for the old bootloader. For the new one, make these changes said by pengus77 here
Flashing instructions:
1. Make a full wipe (wipe data + format /system)
2. Flash the current build and raring/quantal image
Then flash this afterflash.zip
3. Reboot
Credits:
Ubuntu dev team (Canonical)
Ricardo and the rest of the CM team
delaya73 for the new bootloader build
pengus77 for bringing cm10 to the new bootloader
Adam77Root for helping find the missing components stopping it from booting
All other contributors
AW: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
You rock man!
Gesendet von meinem LGP990 mit CM10.
Good luck with your job, Buddy, and Congratulations for all your interest/performance for our machines!
Regards.:good:
Thnx, I downloading, after a try, I will post some feedback
R: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
Can i have some screenshot?
Sent from my LG-P990 using xda app-developers app
rugglez said:
"...If you think you can contribute, please do so ..."
Click to expand...
Click to collapse
I have not had time to install this ROM ... I have been testing other, but lack little longer to do so!
Once you have news post here the results.
Thank you all for the effort made
Thank you man you're doing a really good job
Very good job rugglez bro. cant wait for bootable version to test it on my self
Well, I tried to make some tests to see if he could complete the boot ... unfortunately without success after six or seven attempts.
Enough for today testing, hahahaha! ...
So finally your Repo synced! I've left Hope here! And yea, Rugglez Bhai, you are great! )
rugglez said:
This thread is intended for developers and others who can contribute to the project
If you think you can contribute, please do so
For now, this is only for the new bootloader. If the project is successful, it would be made available on the old one as well
Standard disclaimer:
I am not responsible if anything happens to your device
Status:
Device specific build of Ubuntu's minimal cm10.1 build ready
Ready for flashing
Does not complete the boot yet
Download links:
Current build of Ubuntu-CM10.1
Ubuntu kernel for O2x
Ubuntu phone quantal image
TWRP latest version is recommended (CWM 6.x may work too)
Instructions:
1. Make a full wipe (wipe data + format /system)
2. Flash the current build, Ubuntu_kernel and quantal image
3. Reboot
Note:
The quantal image is large, but thankfully gets installed on the data partition, thus saving our small system partition the burden
To do:
There is no "logcat" in Ubuntu (may be some other way to debug), so need another way to look at what is preventing the boot
Credits:
Ubuntu dev team (Canonical)
CM team
All other contributors
Click to expand...
Click to collapse
have u tried dmsg/kmsg?
how did u get a bootanimation on there ?, my nexus 7 with ubuntu phone os, dont have one, on the nexus 7 there is only a black screen for a seconds then it boots up
Re: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
Never got around to syncing myself, I'm a bit confused regarding the post, so is it usable?
Sent from my LG-P990 using xda app-developers app
JordanRulz said:
have u tried dmsg/kmsg?
Click to expand...
Click to collapse
Will try that today. Not sure if ill get time, but if you could also have a look, it would be great. Saw that you have some experience with this
FettleifIsMyUserName said:
how did u get a bootanimation on there ?, my nexus 7 with ubuntu phone os, dont have one, on the nexus 7 there is only a black screen for a seconds then it boots up
Click to expand...
Click to collapse
Boot animation comes from the Ubuntu-cm10.1 build and is the default cm10 boot animation. Since your tablet's Ubuntu image was released directly by canonical, they must have removed the cm10 boot animation before releasing it
Neefy said:
Never got around to syncing myself, I'm a bit confused regarding the post, so is it usable?
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
If you read the first post, it's written there that it does not complete the boot yet, still a WIP.
The reason I posted was that if more contributors join in, more expertise, more time, better debugging and much higher chance of project success
Jishnu Sur said:
So finally your Repo synced! I've left Hope here! And yea, Rugglez Bhai, you are great! )
Click to expand...
Click to collapse
Thanks
Come online later, I'll help you fix that issue. Install and keep team viewer ready
After watching some vids about this OS, it trully have a great potential. gonna watch this thread closely for progress
Re: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
rugglez said:
Thanks
Come online later, I'll help you fix that issue. Install and keep team viewer ready
Click to expand...
Click to collapse
Nice to know that the team is joining up and viewing to do great things
Great going guys
O2X with Magical ICS ROM and magnificent kernels from my buddies
rugglez said:
Will try that today. Not sure if ill get time, but if you could also have a look, it would be great. Saw that you have some experience with this
Boot animation comes from the Ubuntu-cm10.1 build and is the default cm10 boot animation. Since your tablet's Ubuntu image was released directly by canonical, they must have removed the cm10 boot animation before releasing it
If you read the first post, it's written there that it does not complete the boot yet, still a WIP.
The reason I posted was that if more contributors join in, more expertise, more time, better debugging and much higher chance of project success
Thanks
Come online later, I'll help you fix that issue. Install and keep team viewer ready
Click to expand...
Click to collapse
M always ready!!!!!!!!! =D
The Credits list looks too small.
Maybe you can add Ricardo Cerqueira (for ahem) and TonyP for porting TWRP.
jasjeev4 said:
The Credits list looks too small.
Maybe you can add Ricardo Cerqueira (for ahem) and TonyP for porting TWRP.
Click to expand...
Click to collapse
......and so on...!...
jasjeev4 said:
The Credits list looks too small.
Maybe you can add Ricardo Cerqueira (for ahem) and TonyP for porting TWRP.
Click to expand...
Click to collapse
Ricardo is always a name in every project of the O2x, and he is a part of the CM team, in case you didnt know
But thanks for the reminder, I explicitly specified his name too now, deserves so much credit for bringing CM10 to our device.
Tonyp is a great contributor and we are thankful for all his work. But this is a ROM, and TWRP is a recovery used to flash a ROM, they have non-overlapping work. What I mean is, this ROM doesnt use TWRP's work, rather it can be flashed in TWRP or CWM6.
By your logic, Koushik Datta (developer of CWM and one of the best android devs) should be included in every ROM's credits here. Also, creators of USB, personal computers, internet, world wide web, which are also tools used in the process of flashing it.
(No offense meant to any of the above, they are all revolutionary people whom I greatly respect)
My point is, if I am using someone's work in this project/ROM, thats the person whose name goes in credits, not the one who is creating the tools to install it.
It's better if the discussion doesnt go further about this off-topic thing, if you find that I have used anyone's work in this ROM and not given credits, please let me know, thanks
Let's try to make Ubuntu Phone OS boot on our phone. Thats the priority here. Didn't get much time today, got college this week too, will see if I get time to work on it soon
Hi all,
I will be building cm-10.2 from source nightly and posting it here. These builds are straight from the CyanogenMod Github repo.
These are Unofficial Builds, built by me, from the nightly sync with the source repo. I am not part of the core CM dev team, but I do contribute to the Code Review: http://review.cyanogenmod.org/#/, I'm just a man with a compiler.
After you flash the rom please open up settings / developer settings and then set root access to ADB and Apps. You can access developer settings by tapping the build number 7 times on the about screen.
Thanks Codeworkx!
---------------------------------------------------
P3110/P3113=====>: http://d-h.st/DTz - 20130919 Posted!
TabletUI Patch===>: http://d-h.st/Z1E
ChangeLog====>: http://changelog.bbqdroid.org/
P3100========>: http://d-h.st/eP4 - 20130919 Posted!
TabletUI Patch=>: http://d-h.st/32y
Espresso10++ Kernel: http://d-h.st/UPc - 3.0.96 - p31xx
- Compiled with Linaro 4.7 toolchain. (13.08)
- Overclock and Variable Voltage control - credit to: @ketut.kumajaya & cmenard.
- Xbox 360 wired / wireless controller + LED support.
https://github.com/codyf86/android_kernel_samsung_espresso10/tree/cm-10.2
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?h=linux-3.0.y
http://releases.linaro.org/latest/components/android/toolchain/4.7
Gapps 4.3: http://d-h.st/NhB
Explore my Dev-Host: http://d-h.st/users/codyf86
ClockWorkMod Recovery P3110/P3113: http://d-h.st/vZi - 6.0.3.7 - Tar!
ClockWorkMod Recovery P3110/P3113: https://www.file1.info/gmsY2BC - Zip!
ClockWorkMod Recovery P3100:====> http://d-h.st/eKO - 6.0.3.7 - Tar!
ClockWorkMod Recovery P3100:====> https://www.file1.info/PACugfc - Zip!
---------------------------------------------------
IR has been merged into official nightlies!!!
Special thanks @ketut.kumajaya!
https://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.2
---------------------------------------------------
Shinobisofts' Universal Tar to Flashable Zip Program. (Python)
http://forum.xda-developers.com/showthread.php?t=2419920
Android-Andis' recovery.img to Flashable Zip Script:
http://forum.xda-developers.com/showpost.php?p=44725849&postcount=390.
xNiiCADEMUS' ROM Installation video.
http://youtu.be/uooLuG0Ydr8
---------------------------------------------------
Thanks to Caldair for ApG!
Thanks to Jiangyi for IR insight and general awesomeness!
Thanks to Kenundrem for pulling blobs and other files for me!
---------------------------------------------------
CMAcount:
http://www.cyanogenmod.org/blog/cyanogenmod-account
https://account.cyanogenmod.org/login
I have also compiled in the following from the CyanogenMod Code Review:
If you saw something listed below, that is no longer listed, it has been merged.
SystemUI: Add ADB over WiFi QuickSettings Tile
http://review.cyanogenmod.org/#/c/50211/
http://review.cyanogenmod.org/#/c/50210/4
USB audio support [1/2]&[2/2]
http://review.cyanogenmod.org/#/c/49295/
http://review.cyanogenmod.org/#/c/49296/
usbaudio: Fix output device routing
http://review.cyanogenmod.org/#/c/49292/
Allow showing statusbar on top of fullscreen window.
http://review.cyanogenmod.org/#/c/48352/
Add configuraion for showing statusbar on top of fullscreen window.
http://review.cyanogenmod.org/#/c/48359/
Add the possiblity of using secondary storage for user 0.
http://review.cyanogenmod.org/#/c/47918/
To use the above patch, if you choose to:
Go into Settings / Storage and cycle the check box once.
After you cycle the setting once, choose on or off and reboot.
Recovery: support format external storage to custom fstype using vold.
http://review.cyanogenmod.org/#/c/49899/
Recovery/Vold: Use quick format for NTFS volumes.
http://review.cyanogenmod.org/#/c/49920/
Hit thanks if I helped!
------------------------------------------------------------------------
My Fast and Helpful Socket API for Python 3.2.2+Android:
https://github.com/codyf86/fahsocket-py3-android
You build fast.
But you also build only for one device (or 2 really).
Sent from my LG-P690b using Tapatalk 2
I can build for anything if you ask nice enough. I'd like to stick to samsung devices though.
Luigi asked if I can add the IR blaster changes for the p3113 that had been patched into cm 10.1 on a few unofficial builds. Let me get the 0804 build out of the way; as I will start building it in about 6 hours or so. Then I'll look into adding support for it.
CodyF86 said:
I can build for anything if you ask nice enough. I'd like to stick to samsung devices though.
Click to expand...
Click to collapse
Wow! thanks.
Anyway whats the different from this to codeworks build?
I mean i can build for the supported devices. I'm not trying atm to add support to unsupported devices.
These are from the same source I'm just building them nightly and posting them. The last p3110 build was from 0730, so I built / will build the latest ones everyday.
CodyF86 said:
Luigi asked if I can add the IR blaster changes for the p3113 that had been patched into cm 10.1 on a few unofficial builds. Let me get the 0804 build out of the way; as I will start building it in about 6 hours or so. Then I'll look into adding support for it.
Click to expand...
Click to collapse
can't wait!
Sent from my TouchPad using xda app-developers app
I flashed the 3110/3113 on 3113 works well thank you sir
If I could add a +1 to the IR addition
If you need a tester for a 3113 cm ROM let me know
Sent from my GT-P3110 using xda premium
CodyF86 said:
I can build for anything if you ask nice enough. I'd like to stick to samsung devices though.
Click to expand...
Click to collapse
Thanks..!!
thanks +1
Sent from my GT-P3100 using XDA Premium HD app
Not waiting for a new constructor of cm, but ok, let's see What do you have to offer us ...
Lol I think you may have misunderstood. This isn't a spin off of cm-10.2 or another version of it. This is literally cm-10.2 compiled from the repo sources and I usually sync after midnight then build. The last cm-10.2 build for both p3110 and p3100 was 20130730.
I compiled the latest from the repo and posted it and I'm just going to keep on rebuilding everynight and post it until cm-10.2 starts building automatically at night for all devices with a build server; Like they do with 10.1 atm,
CodyF86 said:
Lol I think you may have misunderstood. This isn't a spin off of cm-10.2 or another version of it. This is literally cm-10.2 compiled from the repo sources and I usually sync after midnight then build. The last cm-10.2 build for both p3110 and p3100 was 20130730.
I compiled the latest from the repo and posted it and I'm just going to keep on rebuilding everynight and post it until cm-10.2 starts building automatically at night for all devices with a build server; Like they do with 10.1 atm,
Click to expand...
Click to collapse
then my confusion be gone
so this is excatcly like what codeworkx create.
glad to have two mainteners for this device:good:
antutu said:
then my confusion be gone
so this is excatcly like what codeworkx create.
glad to have two mainteners for this device:good:
Click to expand...
Click to collapse
He builds more often. Not only that but he will try to implement IR Blaster funtionality for P3113.
P3100 boots up without problems
You can't control the wind, but you can adjust your sails
Sent Form My Galaxy Tab 2 GT-P3100 ,Dual booted using Black Hawk Kernel
Luigi2012SM64DS said:
You build fast.
Click to expand...
Click to collapse
damn fast!! TabletUI patch run perfect :angel:
http://forum.xda-developers.com/sh....1/CM10.2/SlimBean] Tablet UI - Auto-Patcher
On p3100
Here is 20130804 for p3110. p3100 is building right now. I fell asleep last night or I would have already posted both lol. I'll update the first post also.
P3110: http://d-h.st/TAe
P3100: Building Now!
Ok so p3100 is building now and will be done in an hour or two, but I have to run some errands and won't be back for 3 or 4 hours. I'll post p3100 when I get back, sorry for the delay.
I'm using next kernel 1.7 + CyanogenMod 4.3. Runs great i can't detect any trouble. Just edited build.prop file to fix bootanimation
Sent from my GT-P3100 using xda app-developers app
Why no credit´s to @codeworkx or CM-Team in OP? Nobody really thought codeworkx would work for us on CM10.2 ... but he did!!! And thats why i think credits should be added....!
Thank´s for the daily nightlys.
THIS THREAD IS WIP & FOR DEVELOPERS ONLY !
Technical information with sources & binaries is in post #2. It includes kernel building, kexec-module, kexec-tools, hijack script, required patches & current problems with logs.
Click to expand...
Click to collapse
What is kexec?--------------------------------------------------------------------------------------------------------
kexec or kernel execution is a module/mechanism of the kernel that allows live/hot booting of a new/custom kernel "over" the currently running kernel. For more info, read the useful threads/links bellow.
kexec could be used to load a custom kernel into memory & yes, we'll then be able to install AOSP ROMs or in general run a custom kernel compatible with our device.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Updates:--------------------------------------------------------------------------------------------------------
[09/01/2014]:
kexec module has been successfully patched & loaded/inserted into both NC2 & NC4 stock kernels. Now, I'm working on compiling/loading a guest kernel & fixing possible problems/bugs.
Click to expand...
Click to collapse
[08/31/2014]:
Two versions of HLTEVZW KK kernel have been compiled from source: one uses the default configurations & the 2nd adds custom capabilities & kexec boot options. Moreover, kexec-tools & module have been cross-compiled. Now, I'm working on patches for kexec module & guest kernel (the hardest part).
Click to expand...
Click to collapse
[08/01/2014]:
I've successfully flashed a custom kernel on my device. This trips knox flag & isn't 100% related to kexec, but it has the same objective (loading custom kernel on the locked-bootloader devices). However, the bootloader makes security check & blocks the installed kernel with the "unauthorized software by VZW" warning. Then, I tried to patch the bootloader to remove this security check, but my device was HARD BRICKED. Now, I've created a General thread for how to recover from a HARD BRICK. This is promising info for testing bootloader exploits.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Status
--------------------------------------------------------------------------------------------------------
Supported NC2 & NC4 kernels
Working kexec-tools
Loaded kexec module
WIP kexec/guest kernel
Click to expand...
Click to collapse
Thanks to / Credits:
--------------------------------------------------------------------------------------------------------
@sextape - for the leaked NC2 firmware
@Hashcode - for his great work on kernel/recovery
...
Please PM me if I forgot to add proper credits for your work!
Click to expand...
Click to collapse
XDA:DevDB Information
KEXEC, Kernel for the Verizon Samsung Galaxy Note 3
Contributors
hsbadr, CalcProgrammer1, ryanbg
Kernel Special Features:
Version Information
Status: Testing
Created 2014-07-11
Last Updated 2015-02-15
Technical Information
This post is reserved for technical information with sources & binaries. This includes kernel building, kexec-module, kexec-tools, hijack script, required patches & current problems.
Kernel Building:
--------------------------------------------------------------------------------------------------------
The first step for building working kexec-module & tools is to cross-compile the kernel from source with the correct configurations. I won't describe how to build a kernel from source, but you may find this thread very useful.
I've used two different sources for the NC4/NC2 HLTE_VZW KK kernels. The 1st one is a part of SM-N900V_NA_KK_Opensource.zip released by Samsung for N900V NC4 kernel while the 2nd is available on @Hashcode's Github profile with 3 branches: hltevzw-kk-nc2 branch is modified for N900V NC2 kernel + 15 commits for compiling kexec as a module & other kexec patches.
The instructions provided by Samsung to build the NC4 kernel are to update CROSS_COMPILE toolchain environment variable in the Makefile & build with the default configurations as follows:
Code:
export ARCH=arm
make VARIANT_DEFCONFIG=msm8974_sec_hlte_vzw_defconfig msm8974_sec_defconfig SELINUX_DEFCONFIG=selinux_defconfig
make
However, I've patched the sources & used menuconfig interface to customize kernel configurations as follows:
Code:
export ARCH=arm
make VARIANT_DEFCONFIG=msm8974_sec_hlte_vzw_defconfig msm8974_sec_defconfig SELINUX_DEFCONFIG=selinux_defconfig menuconfig
make
(menuconfig is added in the second line)
The default output is the kernel image (arch/arm/boot/zImage) & modules (drivers/*/*.ko). The kexec-module(s) will be built if you patched the sources & configured it as a module.
You may then use dtbTool to generate device tree dt.img & mkbootimg to pack the kernel in boot.img.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kexec Module:
--------------------------------------------------------------------------------------------------------
There're many different flavors of kexec-mod sources. @delewer in this thread uses a standalone kexec-mod source MOD'd for Sony Xperia Z1 to be cross-compiled against the precompiled kernel source while @Hashcode in his sources on Github patches the kernel source to cross-compile kexec-mod with the kernel. Some modules may or may not use/port the hardboot patches. The output for kexec module/drivers have different names (the standalone kexec-mod source generates kexec_load.ko & procfs_rw.ko while the kernel source patched by @Hashcode generates 3 modules: arm_kexec.ko, msm_kexec.ko & kexec.ko).
To test if the cross-compiled modules are loadable & have the correct kernel headers, use insmod in terminal emulator (or a safe point with terminal like Safestrap) to insert the module into the kernel (assuming you've kexec.ko in /system/lib/modules/):
Code:
insmod /system/lib/modules/kexec.ko
Then, use lsmod to list & show the status of loaded modules:
Code:
lsmod
Alternatively, you may check if system call of the kernel includes kexec functions using:
Code:
cat /proc/kallsyms | grep kexec
The kexec-modules I've compiled are loadable & have been successfully inserted into both NC4 & NC2 kernels.
I'm using my own sources for kexec-module based on others & I'll share the sources with binaries & modules after making some required tests.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kexec Tools:
--------------------------------------------------------------------------------------------------------
I'm using the latest version of kexec-tools from here (currently, kexec-tools-2.0.8.tar.gz) cross-compiled for arm with custom configurations. Three binaries are generated including kexec (directly boot into a new kernel) & kdump (display kernel trace data). For more info, check the manpage of each binary & kexec/kexec-tools manuals/guides.
To test your kexec-tools cross-compiled binaries for arm,
Code:
kexec --help
assuming that they're in your PATH (e.g., /system/xbin) with executable permissions (e.g., 755).
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hijack Script:
--------------------------------------------------------------------------------------------------------
will be updated soon...
Click to expand...
Click to collapse
Required Patches:
--------------------------------------------------------------------------------------------------------
will be updated soon...
Click to expand...
Click to collapse
Current Problems/Logs:
--------------------------------------------------------------------------------------------------------
will be updated soon...
Click to expand...
Click to collapse
Sent from my SM-G900V using Tapatalk
jr_718 said:
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
My eyes about popped out the side of my head when I saw this! It says your in testing have you had any luck at all? Thank you thank you thank you BTW!
amebiasis said:
My eyes about popped out the side of my head when I saw this! It says your in testing have you had any luck at all? Thank you thank you thank you BTW!
Click to expand...
Click to collapse
I've tested several binaries for the same kernel version, but none works for now. I'll compile from source & see. However, please keep this this thread for devs discussions only until we release working kexec & guest kernel.
Trying to keep the n3 alive before the n4 arrives? Lol seriously though congrats and thank you. Hope you and the devs here the best of luck. We, the re owners, appreciate all you have done already for us.
bmwh0r3 said:
Trying to keep the n3 alive before the n4 arrives? Lol seriously though congrats and thank you. Hope you and the devs here the best of luck. We, the re owners, appreciate all you have done already for us.
Click to expand...
Click to collapse
Note 4 is useless until it gets root & custom ROMs. For me, it'll be better ONLY IF we can break its security & unlock bootloader!
What about surge & ryanbg and e.v.a. I been following them and they both have a good idea on how things work well I think they are good for the job
Just a thought I had when unlocking my spare RAZR hd, but the kernels on the Razr and my note 3 are 3.4.97 and 3.4.0. Is the exploit part of the kernel or is there a reason I'm a user and not a Dev? If it is, motopacalypse.apk is what unlocked my RAZR. I'm just trying to learn so please don't think I'm a moron. I just don't know the coding aspect of android at all.
Have you got an irc or hangout open for discussion?
Thanks for your efforts! !
tpike said:
Have you got an irc or hangout open for discussion?
Thanks for your efforts! !
Click to expand...
Click to collapse
There is #Galaxy-Note-3 on Freenode but it's really quiet in there most of the time.
Many forum lurkers like me have been anxiously waiting for this breakthrough! Don't give up! I also believe in donating to hardworking devs like you guys! Good luck...
I was an owner of a Motorola Defy and the day that it got KEXEC I was so exited.. so good luck for you guys! Nothing is impossible. :victory:
Feche said:
I was an owner of a Motorola Defy and the day that it got KEXEC I was so exited.. so good luck for you guys! Nothing is impossible. :victory:
Click to expand...
Click to collapse
Who was devs on kexec on defy?
ironfisted said:
Who was devs on kexec on defy?
Click to expand...
Click to collapse
Not sure
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
ryanbg said:
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
Click to expand...
Click to collapse
Good luck! Lots of us are waiting for this!
ryanbg said:
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
Click to expand...
Click to collapse
Keep it up man, I understand the hard work involved in doing something like this, but it will definitely pay of in the end!!! Thank you for your hard work and dedication, you got a lot of people counting on you
Sent from my BajaRom "L" Themed Note 3
ryanbg said:
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
Click to expand...
Click to collapse
I see. Let me know if you'd like to contribute to this thread. I'll update it soon with more details about the required patches & the preliminary results of my tests ––after releasing a new version of JasmineROM.
ryanbg said:
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
Click to expand...
Click to collapse
I was told by a defy dev that we would have better luck contacting hp touch pad kernel devs. I guess their kernel is more like ours I guess. Idk. I never tried contacting dev from their yet
Introduction
Hello everyone, this is a thread to introduce both users and kernel developers to the concept of linux-stable as well as give developers some tips and a tree to either merge into their own, use as a base, or just as a reference. Feel free to ask questions and enjoy!
What is it?
linux-stable is, as the name implies, the stable branch of the Linux kernel, the base of Android. The phone could not run without the Linux kernel (at least not without reworking a lot of stuff). The Android kernels are based on the longterm stable trees:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Click to expand...
Click to collapse
Source: https://www.kernel.org/category/releases.html
All Linux development happens on the master branch, which is governed by Linus Torvalds. When issues are discovered there, the fixes are applied then backported to these various stable trees for consumption. It is not uncommon for a fix to need to go back a few years.
There is a LOT more information available in the notes repo in the android-linux-stable organization if you care to learn more in-depth: https://github.com/android-linux-stable/notes
What does this mean for me?
If you are a developer, this means you should be merging these changes into your own tree. These are vetted, stable fixes to real world problems and they are being handed out for free. It does not take long to get up to date (as you can just merge this tree directly into your own or do it yourself using the tree as a reference) and once you are up to date, there is usually a release once every two weeks, give or take. I provide a rebuttal to a lot of various complaints here. If you still feel like there is a good reason not to do this, please let me know, I'll be happy to try and debate on it!
If you are a user, it means that you should be looking for and using kernels that have these fixes, as it shows the developers care for your security and stability. The current version for this device is 3.18.100 and the current version upstream is 3.18.124 so all you need to do is go into Settings > About phone and look at the kernel version to know if you are up to date.
How do I use?
If you are a developer, the reference tree is located in the android-linux-stable organization: https://github.com/android-linux-stable/marlin
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, use a kernel that has the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The linux-kernel-announce mailing list: http://vger.kernel.org/vger-lists.html#linux-kernel-announce
The android-linux-stable Telegram channel: https://t.me/alsupdates
Subscribe to this thread
Follow me on Google+ or Twitter
Getting help
If you have any issues with getting these changes into your tree or want to ask a question, there are a few different ways to do it:
Post in this thread
Join the linux-stable support chat on Telegram: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
File an issue either in the android-linux-stable notes repo or the android-linux-stable repo for this device
When requesting help, please give some solid details as to what you are struggling with, as I am happy to provide assistant and clarity but not to do something for you (unless I screwed up).
3.18.88 has been merged in.
3.18.89 has been merged in.
3.18.90 has been merged in.
3.18.91 has been merged in (conflict notes).
Hi Nathan, thanks for the code - built the kernel and flashed (wasn't easy at first). All working well, will use it at a later stage when I build the ROM. BTW, I am running the factory image. Credit also to Anykernel for the zip file
GeyerA said:
Hi Nathan, thanks for the code - built the kernel and flashed (wasn't easy at first). All working well, will use it at a later stage when I build the ROM. BTW, I am running the factory image. Credit also to Anykernel for the zip file
Click to expand...
Click to collapse
Not a Dev, but totally would like to give this a try if you have a zip. On the factory image + twrp 3.2.1
Sent from my [device_name] using XDA-Developers Legacy app
Hi, No problem. There you go... Just flash in TWRP and feedback if all went ok
3.18.92 has been merged in.
Hi, thanks for the code, compiled it against linaro 6.4 (built the cross-compiler following your thread). Tested for one day. All smooth. Sharing the job for those who might be interested. BTW, flashed it directly from fastboot....
Code:
fastboot flash kernel Image.lz4-dtb
Hi, added WireGuard support.
@ nathanchance, sorry, do not mean to hijack your thread...
GeyerA said:
Hi, added WireGuard support.
@ nathanchance, sorry, do not mean to hijack your thread...
Click to expand...
Click to collapse
No worries lol, gives it some life :silly:
Sent from my Pixel 2 XL using XDA Labs
GeyerA said:
Hi, added WireGuard support.
@ nathanchance, sorry, do not mean to hijack your thread...
Click to expand...
Click to collapse
Running this now, so far so good! Thanks!
Definitely interested in wire guard, but currently use WindScribe and am not sure how to properly configure it.
Will try and Frankenstein a config file together tonight and report back [emoji106]
Thanks again
Sent from my [device_name] using XDA-Developers Legacy app
Hi, question. Added DSPManager to my ROM and see that it always gets killed. Can you support the idea to build the kernel with
Code:
CONFIG_SECURITY_SELINUX=n
. Will this get me the kernel permissive and any disadvantages with this? I also see that Viper4android needs a permissive kernel.
3.18.93 has been merged in.
Somebody willing to do a build of the update to flash with fastboot?
I would if I could (still learning how to build myself)
Thnx in advance.
Cheers
Sent from my Google Pixel using XDA Labs
Sgace said:
Somebody willing to do a build of the update to flash with fastboot?
I would if I could
Thnx in advance.
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Was just going to ask if someone could point me to a good resource on how to do so. Will post anything I manage to do [emoji106]
Sent from my [device_name] using XDA-Developers Legacy app
jimbub said:
Was just going to ask if someone could point me to a good resource on how to do so. Will post anything I manage to do [emoji106]
Click to expand...
Click to collapse
Hi,
I used this for the most part: https://forum.xda-developers.com/yureka/help/guide-compiling-64-bit-android-kernel-t3352728
And this:
https://forum.xda-developers.com/an...-how-to-compile-android-kernel-t3627297/page1
Was very helpful and am building right now
Credits to those guys offcourse.
Sent from my Google Pixel using XDA Labs
Sgace said:
Hi,
I used this for the most part: https://forum.xda-developers.com/yureka/help/guide-compiling-64-bit-android-kernel-t3352728
And this:
https://forum.xda-developers.com/an...-how-to-compile-android-kernel-t3627297/page1
Was very helpful and am building right now
Credits to those guys offcourse.
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
If it's ok, here is my personal first ever self built kernel from source. It's 3.18.93 and flashable in fastboot (unzip the zip and then: fastboot flash kernel Image.lz4-dtb)
Offcourse thnx to @nathanchance for the source and all the work!
Cheers
Sgace said:
If it's ok, here is my personal first ever self built kernel from source. It's 3.18.93 and flashable in fastboot (unzip the zip and then: fastboot flash kernel Image.lz4-dtb)
Offcourse thnx to @nathanchance for the source and all the work!
Cheers
Click to expand...
Click to collapse
Thanks for doing this, very much appreciate it! For some reason though, this prevented my phone from booting. Ended up restoring my boot partition and things are well now!