Related
I know there's got to be more people here capable of compiling a kernel than just the CyanogenMod team. Now that we're "official" a lot of 3rd party kernels that borrow from the d2 (Galaxy S III) CyanogenMod tree include everything you need to compile an alternate kernel for apexq. Here's 2 I found at random:
http://forum.xda-developers.com/showthread.php?t=2139055
http://forum.xda-developers.com/showthread.php?t=2226290
Also porting to other roms like AOKP or Paranoid Android is typically a matter of minor changes to the build files. Almost everyone uses CyanogenMod as a base or keeps up with CyanogenMod so the differences, if any, should be minimal.
If you are a developer, and wish to have a device merged into Omni, here is the current "temporary" process to use. There are 2 ways to do this - make your tree available on github (or a similar service), or request a new git tree be created, and submit it to gerrit.
1) Get your device working. There's plenty of help available in #omnirom on Freenode if you need assistance. An AOSP device tree is probably the best place to get started.
2) Set up your device to use the OmniROM "custom" build type, rather than full/aosp. More information will follow on this step - check device/samsung/manta or device/lge/mako for an example.
3) Make your device tree available on github or a similar git service. Please retain authorship of an original tree (if you fork it from AOSP or another custom ROM)
4) Come to #omni on Freenode, and have a chat to one of the core developers (they are listed at the top of the user list) - they will be able to help you get your device merged
Please note, in order to add a new device, we will require a maintainer on an ongoing basis for it, to ensure someone is able to investigate bugs that users report on a device. Without this, we unfortunately cannot enable nightly builds for a device.
will a cm kernel tree work for the most part with just a few changes?
azoller1 said:
will a cm kernel tree work for the most part with just a few changes?
Click to expand...
Click to collapse
yes - of course it must be 10.2 (4.3)
most likly it will work even unchanged
pulser_g2 said:
3) Make your device tree available on github or a similar git service. Please retain authorship of an original tree (if you fork it from AOSP or another custom ROM)
Click to expand...
Click to collapse
Along these lines, do NOT remove copyright attributions of a changed file. You may ADD copyrights to a header, but do NOT remove anything.
maxwen said:
yes - of course it must be 10.2 (4.3)
most likly it will work even unchanged
Click to expand...
Click to collapse
Most likely kernel change will be that reverting out that MDP sync point mess used by CM's AOSP+CAF frankendisplay. Can't link to it from my current location.
I have everything device sided transformed to Omni (m7ul,m7-common,and msm8960) and have exactly this problem now. Builds fine but Stucks after a few secs booting and hard reboots. Already looked into kmsg with maxwen but now we need to find what's causing it...
Reverted some stuff (MDP) kernel sided but haven't succeeded so far. Would be appreciated if u point us there when u back on a pc
noNeedForAsig
TF300T
OK here goes..
For the Asus Transformer TF300T the kernel forked from the CyanogenMod github:
https://github.com/scanno/android_kernel_asus_tf300t/tree/android-4.3
And the device tree, modified to get OmniROM to finish the build and get a bootable result:
https://github.com/scanno/android_device_asus_tf300t/tree/android-4.3
Hopefully it will be added to the OmniROM github.
n3ocort3x said:
I have everything device sided transformed to Omni (m7ul,m7-common,and msm8960) and have exactly this problem now. Builds fine but Stucks after a few secs booting and hard reboots. Already looked into kmsg with maxwen but now we need to find what's causing it...
Reverted some stuff (MDP) kernel sided but haven't succeeded so far. Would be appreciated if u point us there when u back on a pc
noNeedForAsig
Click to expand...
Click to collapse
I'm thinking for m7ul it would be https://github.com/CyanogenMod/android_kernel_htc_m7/commit/f2efb02581110747711c8b17f31f38fc3ed5dd1a
Don't want to hijack the thread though, so we can probably discuss this elsewhere
@Grarak Maybe you should post your edited device tree for Omni Rom =)
Sent From my i9500 With ☆★Crash Rom★☆
AL_IRAQI said:
@Grarak Maybe you should post your edited device tree for Omni Rom =)
Sent From my i9500 With ☆★Crash Rom★☆
Click to expand...
Click to collapse
Already on my github
https://github.com/Grarak/android_device_samsung_i9500
kernel tree
https://github.com/Grarak/android_kernel_samsung_exynos5410
proprietary
https://github.com/Grarak/proprietary_vendor_samsung
exynos 5410 repos:
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos5410
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos5
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos5-insignal
https://github.com/intervigilium/android_hardware_samsung_slsi_openmax
pretty much ^^
I'd like to maintain for l900 and i605 (Sprint and Verizon Galaxy Note 2).
device trees
https://github.com/omnirom-slickrick/android_device_samsung_l900 (sprint tree)
https://github.com/omnirom-slickrick/android_device_samsung_i605 (vzw tree)
https://github.com/omnirom-slickrick/android_device_samsung_t0lte (note 2 common tree)
https://github.com/omnirom-slickrick/android_device_samsung_smdk4412-common (same as tree on omnirom github but actually more updated and device settings added back)
kernel
https://github.com/omnirom-slickrick/android_kernel_samsung_smdk4412 (just have needed device settings commits added back in)
thracky said:
I'm thinking for m7ul it would be https://github.com/CyanogenMod/android_kernel_htc_m7/commit/f2efb02581110747711c8b17f31f38fc3ed5dd1a
Don't want to hijack the thread though, so we can probably discuss this elsewhere
Click to expand...
Click to collapse
we already making progress but it needs more work to be done.. at least we are now in system with working wifi, and display but modem doesent work.. something for tomorrow, and i dont want to hijack this thread too sorry if my question was in the wrong section but i thought i mention it because of the post above mine. nevermind i cann offer to maintain m7ul as already discussed with maxwen and oin IRC but a lot of work needs to be done:
here are my sources, device trees are usable but kernel needs more work as said above:
device trees:
https://github.com/n3ocort3x/android_device_htc_m7ul
https://github.com/n3ocort3x/android_device_htc_m7-common
https://github.com/n3ocort3x/android_device_htc_msm8960-common
kernel: its a modified one but its no problem to bring it back to stock features and will push as soon asap the modem stuff is sorted out
https://github.com/n3ocort3x/android_kernel_htc_m7
EDIT modem fixed, only BT left
@sykomaniac , look at first post and become a maintainer
pulser_g2 said:
If you are a developer, and wish to have a device merged into Omni, here is the current "temporary" process to use. There are 2 ways to do this - make your tree available on github (or a similar service), or request a new git tree be created, and submit it to gerrit.
1) Get your device working. There's plenty of help available in #omnirom on Freenode if you need assistance. An AOSP device tree is probably the best place to get started.
2) Set up your device to use the OmniROM "custom" build type, rather than full/aosp. More information will follow on this step - check device/samsung/manta or device/lge/mako for an example.
3) Make your device tree available on github or a similar git service. Please retain authorship of an original tree (if you fork it from AOSP or another custom ROM)
4) Post a link here to the device tree (and kernel repository) for review, and tell us what device it is (give model numbers and board names and as many details as possible )
Click to expand...
Click to collapse
We have quite a few things that aren't working like bluetooth, camera is buggy, H/W vsync, gps, and fm radio.
https://github.com/SeannyM/android_device_samsung_kylessopen
https://github.com/SeannyM/ba2x-kernel
gt-s7560m with quadband gsm and 850/1900/2100 WCDMA/UTMS
We have a MSM7227a cpu armv7 clocked at 1008mhz stock.
645mb of usable ram
4gb of storage with 1.7 usable
233 dpi 800x480 4inch screen
Adreno 200 enhanced
5mp camera 1.3 front facing
hopefully we can get something official
single sim
Gtab2 10.1 Wifi & 3G (p5110 & p5100)
There you have my device tree for omni
p5110 :
https://github.com/sevenup30/android_device_samsung_p5110
p5100:
https://github.com/sevenup30/android_device_samsung_p5100
omap4-common (had to edit it cuz of duplicate libion entry):
https://github.com/sevenup30/android_device_samsung_omap4-common
other dependencies required from CM & Themuppets
kernel :
https://github.com/CyanogenMod/android_kernel_samsung_espresso10
samsung proprietary:
https://github.com/TheMuppets/proprietary_vendor_samsung
samsung hardware:
https://github.com/CyanogenMod/android_hardware_samsung
apps samsung service:
https://github.com/CyanogenMod/android_packages_apps_SamsungServiceMode
Everything is working (sound / wifi / bluetooth / video playback) BUT!
I must edit build.prop by hand to get sound working until omni build process take care of "product_build_prop_overrides" into custom_XXXX.mk
see:
http://forum.xda-developers.com/showthread.php?t=2484747
Original Samsung Galaxy Note
Samsung n7000 initial bringup:
Modified CM n7000 device: https://github.com/chasmodo/android_device_samsung_n7000/tree/android-4.3
Modified CM galaxys2-common: https://github.com/chasmodo/android_device_samsung_galaxys2-common/tree/android-4.3
CM smdk4412 kernel: https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/tree/cm-10.2
Samsung proprietary stuff: https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-10.2
Samsung hardware tree untouched from OmniRom.
Device info:
Board platform - exynos4
SOC - exynos4210
Board name - smdk4210
Kernel specifics - unified kernel and recovery
It compiles fine using the repos listed above, but throws up a kernel assert error when flashing the Rom. Several compilers for different devices complained about it in the 'All the answers' thread. The way out of this is to flash a CM10.2 kernel immediately after the Rom flash aborts, then Omni boots up fine.
What works:
1. telephony
2. mms
3. WiFi
4. GPS
What doesn't work:
1. data
2. bluetooth turns off as soon as you turn it on
3. both sdcards are invisible from Android; all your stuff is there when you drop into recovery, though
4. Settings/Storage FC when tapped - see #3
5. Performance options also FC
6. Notification drawer cannot be pulled down
Camera cannot be tested because it shuts down as soon as you start it, saying: "No external storage available" - again, see #3
Galaxy Note II / N7100 (International)
Samsung Galaxy Note II / N7100 Bring up details.
I have a working build of the Omni rom for the N7100. Below are the details on what is working and not working. i have been using it for the last 2 days, so far not crashes or reboots all seems to be working fine. i cherry picked a few commits and included it into my build
Working :
WIFI
DATA -3G & 2G
Telephony & MMS & SMS
GPS
Sound
Camera (Both Front and Back)
SD card
Performance control
Notification drawer & Lights
Multi-Window
roadrunner
Not Working :
BT
Backlights(if i install a custom kernel then the lights work)
Device Tree for N7100 - https://github.com/tilaksidduram/device_samsung_n7100
Device smdk4412-common - https://github.com/tilaksidduram/android_device_samsung_smdk4412-common
smdk-4412 Kernel (3.0.100) - https://github.com/CyanogenMod/android_kernel_samsung_smdk4412
samsung hardware - https://github.com/CyanogenMod/android_hardware_samsung
DEVICE: GT-N7100
sources
https://www.github.com/UtkarshGupta/android_device_samsung_n7100
https://www.github.com/omnirom/android_device_samsung_smdk4412-common
https://www.github.com/omnirom/android_hardware_samsung
https://www.github.com/omnirom/android_kernel_samsung_smdk4412
https://www.github.com/TheMuppets/proprietary_vendor_samsung
Is anyone else working on d2att/d2can (Galaxy S3 I747)? I'm not overly familiar with ROM development, but I can compile CM10.2 for this device just fine, and I'm slowly working on getting Omni to compile for it as well. If someone more experienced than I is already working on it though, I'll probably just let them do it.
If I am the only one, expect some newb-ish questions in the near future.
dstruct2k said:
Is anyone else working on d2att/d2can (Galaxy S3 I747)? I'm not overly familiar with ROM development, but I can compile CM10.2 for this device just fine, and I'm slowly working on getting Omni to compile for it as well. If someone more experienced than I is already working on it though, I'll probably just let them do it.
If I am the only one, expect some newb-ish questions in the near future.
Click to expand...
Click to collapse
I think a few are... There has been chat of it in the IRC channels.
Device name: LG Optimus 4X HD
Codename: P880
Board name: X3
Chipset: Tegra 3 AP33
Everything works, except button backlight.
https://github.com/Adam77Root/android_device_lge_p880
https://github.com/Adam77Root/android_kernel_lge_x3
https://github.com/TheMuppets/proprietary_vendor_lge
Hi everyone,
I've been working on CM for the PadFone Infinity (pretty good device, only lacking a good community) for some time, and I've started to have some results now.
I've basically been using Asus' kernel sources and a custom-made device tree. I then tried to build CM and corrected every error I encountered to try to compile ROM successfully. I eventually succeded in compiling it, but it's now that I need help the most.
Why? Because I have no kernel development knowledge at all, and I really don't want this project to die.
So, let's list what does work and what doesn't:
-Recovery compiles and works just fine. I can backup, restore, flash roms, wipe, and everything that is needed.
-ROM and kernel compile without errors too.
-ROM does NOT boot at all. Getting past the Asus logo, the screen just switches off, and phone totally looks like it's shutdown. No backlight, keys are not backlighted either.
So here is what is needed to compile ROM:
-Device Tree
-Kernel sources (modified to compile without errors)
-PadFone Infinity stock ROM (if needed. Also, there are device blobs in it, so it might be useful)
-Asus untouched kernel sources
I do have the device, so if you need anything about it (hardware info, for example), feel free to ask. I'd love to help, even though I've already made some work, I've come to a point where my knowledge will be far from enough...
Thanks everyone for reading, and maybe for helping if you are interested in this project.
Contact Faux, maybe he will be interested in maintaining a Kernel base for this device.
Bumping.
If a xda recognized developer is willing to develop for this device, I'll have one sent to him.
I really want to have CM and some dev community on this device. I started a bounty to be able to have a device sent to a dev, it seems that many people also want development on it.
I'd also bump the thread. I also interested in CM on padfone, and especially after ASUS discontinued device support :-/
mva.name said:
I'd also bump the thread. I also interested in CM on padfone, and especially after ASUS discontinued device support :-/
Click to expand...
Click to collapse
cm always need alot of work and if you don't have the device it's very difficult to have a stable build .
messi2050 said:
if you don't have the device it's very difficult to have a stable build .
Click to expand...
Click to collapse
AFAIRC, topicstarter suggested to donate a device for interested cm-developer
mva.name said:
AFAIRC, topicstarter suggested to donate a device for interested cm-developer
Click to expand...
Click to collapse
Yeah but that was from 2013 look to the post date , i can do it if the offer is still there but i doubt that
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. So don't be an *** ****
*/
hi.. i'm already started make some modifications on ROM with other Brazilian DEV's for "Evertek S.A - SKMtek Genesis Tab GT7305"... we already found the source kernel from another Netbook or Development Board PC who uses the same SOC... but nothing already have been maked to kernel, we use the provided kernel from stock (Kernel 3.4.5+)... and about the ROM we already have two custom ROM's... One is Stock Modded (4.2.2) and another is KitKat Ported ROM from another Evertek Device... *Portuguese-Brazil Language Site/Forum
And we already make some modifications to this KK port...
- ROOT
- BusyBox
- Init.D support
- Build.Prop Mods
- SuperUser
- zipalign apps after boot
.. and other mods.
we already make too much on ROM but nothing about kernel... we want make a better kernel with optimizations and a better TCP/Clock Table, More Governors , More I/O Scheduler and maybe Overclock to 1600mhz to start after have a custom Kernel booting...
Now we need someone who understand about recovery's like CWM or TWRP and Kernel Compilation better than me to we can start make something awesome =D i think this can be used to another company's/Chinese tablets too, using the same SOC (WM8880) evidently... . . . (Found^^Working^^Recovery's)
i can't start testing here because if i flash this kernel using the Stock Recovery (WonderMedia Recovery tool) maybe i can possible brick my tablet... so if someone understand about CMW recovery to start would be nice =D
Update Progress / ChangeLog ¬
Code:
# 25/12:
- [STRIKE]Found Possible match [URL="http://forum.xda-developers.com/showthread.php?t=2305268"]CWM port[/URL] from [URL="http://forum.xda-developers.com/showthread.php?t=2216390"]Asus MeMo Pad 7{ME172V}[/URL] on XDA Forum[/STRIKE] #NOPE...
- FOUND WOKING [URL="http://blog.hadi-cpu.com/2013/09/cwm-recovery-6036-w8850-rc2.html"]CWM Recovery[/URL] from Malasya Blog from Generic WM8850 SOC tablet , Founded [URL="http://blog.hadi-cpu.com/2013/10/twrp-touch-wondermedia-wm8850-jb-version.html"]TWRP recovery[/URL] too but not tested (Thanks to #Rollidark to notify me about and #osinaldi to discover that from malasya blog) [Mirrors -> [URL="https://www.4shared.com/rar/2POyc0B0ba/CWM_WM8850_NSFAT-RC2.htm?sop=true"]CMW[/URL] -> [URL="https://www.4shared.com/rar/rJBfUTQF/TWRP-JB-NSFAT-WM8850.htm"]TWRP[/URL]] // [URL="https://www.facebook.com/groups/NewSmartFrenAndroTab/"]Facebook Group of Recovery Developers[/URL]
- Studying some way to introduce the missing Touch driver to kernel from [URL="https://gist.github.com/psachin"]psachin Github[/URL]|[URL="http://cdn.liliputing.com/wp-content/uploads/2013/01/rock_02.jpg"]apc-rock-II-[/URL]|[URL="https://github.com/psachin/apc-rock-II-kernel"]kernel[/URL] how already modded the Source to work with [URL="http://tinyurl.com/oqxmuam"]Generic Netbook[/URL] who uses the same SOC
-- Merry Christmas to #ALL
# ?? to 23~24/12:
- ROM JB and KK + ADV. Patch developed by Brazilian Dev's team
- found Source Kernel to WM8880 SoC
Brazilian Developers who already help this projects from forum - genesiseries :
Code:
# KK ROM:
- #paulomsilva2006 {KitKat ROM Port}
- #Rollidark {KitKat Patch}
- #Wcfuria
- #? - Pedro Alves
- #? - Pedro Victor
- #? - Walter Moretti
- #? - Moises Teixeira
Code:
# JB Stock ROM:
- #ylukasy {ROM Dev.}
- #Rollidark
- #paulomsilva2006
- +?
if i forget someone.. please comment below :highfive:
Reserved
wow there's only a handful on and off development going on for this SoC, I still keep my WM8880 tablet just in case somebody made a breakthrough in doing Custom ROM or even getting real ubuntu/debian to boot natively... are you still on this?
funtikar said:
wow there's only a handful on and off development going on for this SoC, I still keep my WM8880 tablet just in case somebody made a breakthrough in doing Custom ROM or even getting real ubuntu/debian to boot natively... are you still on this?
Click to expand...
Click to collapse
just a few Brazilian and Malasya Developers still make progress with this SoC... if you want to try install the custom ROM´s i have shared upper topic.. it will be by your won and I am not responsible for bricked devices...
i´m already started make progress with Custom Kernel but i need found the touch screen driver source and re-work the sound driver(Alsa Drivers...) and compile the recovery with kernel too.. to than have some trust on my work to flash it on tablet =#
:highfive:
DvDwx. said:
just a few Brazilian and Malasya Developers still make progress with this SoC... if you want to try install the custom ROM´s i have shared upper topic.. it will be by your won and I am not responsible for bricked devices...
i´m already started make progress with Custom Kernel but i need found the touch screen driver source and re-work the sound driver(Alsa Drivers...) and compile the recovery with kernel too.. to than have some trust on my work to flash it on tablet =#
:highfive:
Click to expand...
Click to collapse
meh, its my rom testing ground anyway not really worried .. i actually have the tablet connect directly from the battery wires(the battery removed) to the adapter(usb)... anything is better than nothing for the development hehe...wait by Malasya do u mean Malaysia? whos that developer lol..
funtikar said:
meh, its my rom testing ground anyway not really worried .. i actually have the tablet connect directly from the battery wires(the battery removed) to the adapter(usb)... anything is better than nothing for the development hehe...wait by Malasya do u mean Malaysia? whos that developer lol..
Click to expand...
Click to collapse
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/
DvDwx. said:
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/
Click to expand...
Click to collapse
what a coincidence , I was wondering today when you will reply lol
ah I see too bad, maybe you will share it at techknowme forum, ... wow Malaysian ?, Im asking because I'm Malaysian, can you pm me the link where its shared?
DvDwx. said:
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/
Click to expand...
Click to collapse
please continue developing this project..i have using acer b1 740 and it dont have android 4.4 update
tuyenat3 said:
please continue developing this project..i have using acer b1 740 and it dont have android 4.4 update
Click to expand...
Click to collapse
man... i just don't want blame anyone but... to we can do something to your tablet we need the kernel source and that don't stay open to developers... on this Chinese tablets we have some little configurations to can work with... but the custom kernel project i need to abandon for two reasons... first i don't have much time to can work to create a stable and functional custom kernel to everyone... second i don't have a kernel source compatible with tablets... what i found is from a electronics engineering Project computer Board ... and to it can fit on tablet is missing too much drivers compatibles with to can work smoothly and functional... someday if i found a new source maybe i can try comeback developer something to that =#
please continue developing this project
I use a genesis 7305 his kernel is very poorly optimized would like to make this usable tablet sorry for my bad English I use Google translator ;-;
2021... I tried to put a Chinese rom, but I brick the tablet, it only responds to fastboot, when I put the sudo command fastboot flash:raw boot uzImage.bin ramdisk.bin and plug in the charger and press power it appears a genesis screen.
Boot FOSSEE-OS from SCARD | FOSSEE-Laptop
laptop.fossee.in
GitHub - FOSSEE/FOSSEE-netbook-kernel-source: A low cost fossee-laptop based on wm8880 ARMv7 SoC
A low cost fossee-laptop based on wm8880 ARMv7 SoC - GitHub - FOSSEE/FOSSEE-netbook-kernel-source: A low cost fossee-laptop based on wm8880 ARMv7 SoC
github.com
Hello
I did Bought a Samsung Galaxy Z flip 3 demo version , i want to build TWRP for it
Spoiler: That is Done
yesterday i downloaded the Kernel source code from Samsung , now i just need TWRP Sources and and Create a Device Tree to built it
if you want TWRP for this phone , just comment down below (for some motivation)
Spoiler: that done too , look for the custom working kernel
Now For a The Custom Kernel
I Manage to Get A Custom Kernel Working with A lot Of Optimisations (Thanks @chrisaw and Others) on a Old OneUI (That System That Came with the Kernel) and it work well (it need some minor touches)
the Kernel Cant Work on Newer OneUI and Custom Roms (Pixel EXperience) because Of new Changes in Vendor Are not Compatible with the Kernel
A guess this Need A lot Of Working (Everytime Samsung do it their Way and Dont Care about The Correct Way)
ScreenShot of the Kernel
Spoiler: That is Done too too
now on Focusing on The Custom Rom , i download LineageOS 19.0 Source Code as i will build for 2 separate phones (Galaxy Z Flip3 'snapdragon 888' and UMIDIGI F1 Play 'Mediatek Helio P60') consecutively
this rom will be based on treble gsi patches but working only on Galaxy Z Flip3
i manage to build LineageOS 19.0 for Galaxy Z Flip3 , i will not share it now cause :
1 - it is not daily driver or usable , you can call it pre-alpha
2 - it has a lot of bugs that i saw , it could be other i didn't
3 - it is a Treble gsi just for testing purposes and does not have gapps (gapps needed to be included in the gsi not like a normal rom)
4 - i fix the fingerprint , now it is usable
5 - don't ask me about rear screen , it is perfectly not working at all (if you close the phone , the main display become black , rear screen have just samsung galaxy logo....)
6 - other things i forgot
Any Help will be appreciated
Stay Tune
Thanks
Yeah I'd like to see a fully functional TWRP
yes!
really appreciated!
I'm in
hells yeah
ok so i reinstall my ubuntu setup cause apt went broken , but now im good to start
my initial work is the device tree , it is still WIP
GitHub - shadowofleaf96/android_device_samsung_b2q: For building TWRP for Samsung Galaxy Z Flip 3 5G
For building TWRP for Samsung Galaxy Z Flip 3 5G . Contribute to shadowofleaf96/android_device_samsung_b2q development by creating an account on GitHub.
github.com
the kernel still not building , im working on it
thanks for waiting
GitHub - StarKissed/starkissed-kernel-b2q
Contribute to StarKissed/starkissed-kernel-b2q development by creating an account on GitHub.
github.com
I never finished it, but this may help with getting the kernel to build.
It's based on the ROG Phone 5 changes required for the isolated source.
[SOURCE] ASUS_I005_1-kernel (MacOS / Linux)
WARNING: This is NOT a custom kernel! GPL requires that source is released for Android kernels. It does not, however, require that the source is tracked. https://www.asus.com/supportonly/ROG%20Phone%205%20(ZS673KS)/HelpDesk_Download/ Each...
forum.xda-developers.com
twistedumbrella said:
GitHub - StarKissed/starkissed-kernel-b2q
Contribute to StarKissed/starkissed-kernel-b2q development by creating an account on GitHub.
github.com
I never finished it, but this may help with getting the kernel to build.
It's based on the ROG Phone 5 changes required for the isolated source.
[SOURCE] ASUS_I005_1-kernel (MacOS / Linux)
WARNING: This is NOT a custom kernel! GPL requires that source is released for Android kernels. It does not, however, require that the source is tracked. https://www.asus.com/supportonly/ROG%20Phone%205%20(ZS673KS)/HelpDesk_Download/ Each...
forum.xda-developers.com
Click to expand...
Click to collapse
thanks
samsung released android 12 kernel so i will merge the changes from your kernel to mine
Shadow Of Leaf said:
thanks
samsung released android 12 kernel so i will merge the changes from your kernel to mine
Click to expand...
Click to collapse
That kernel never booted, so that would probably do more harm than good. It does, however, include the changes to make an inline kernel build outside the source. It was more an example than a template.
twistedumbrella said:
That kernel never booted, so that would probably do more harm than good. It does, however, include the changes to make an inline kernel build outside the source. It was more an example than a template.
Click to expand...
Click to collapse
ok
yes that what i will do , i will use the samsung open source kernel (android 12) , fix to boot recovery and boot the system , when it does that i will include your changes and see if it works or not
Thanks for your contribution。
Cyanide_zh said:
Thanks for your contribution。
Click to expand...
Click to collapse
you welcome
some good news
TWRP is Booted on our Galaxy Z Flip 3 (SM-F711B) but touchscreen is not working
i think i have a problem with firmware , stay tuned
Shadow Of Leaf said:
some good news
TWRP is Booted on our Galaxy Z Flip 3 (SM-F711B) but touchscreen is not working
i think i have a problem with firmware , stay tuned View attachment 5671531
Click to expand...
Click to collapse
can you share the non-touch version?
i hope he can find the problem and fix it
Maroshall said:
can you share the non-touch version?
i hope he can find the problem and fix it
Click to expand...
Click to collapse
i think i fix the touchscreen problem and its working
there is some minor problems i will fix them and upload it here
also the kernel does not boot on oneui , i have to fix it
the work is done (or atleast it works)
you can check it here TWRP Thread
@twistedumbrella i build the kernel it works on twrp but no luck with OneUI (even with knox and other security measurements disabled) it does panic (kernel panic) i need to do some investigation regarding this , if you want to help i will upload my kernel source code soon
I have the US version, which is why I abandoned the kernel. I had no way to test the changes specific to Samsung, which would be OneUI.
Your best bet would be looking into the changes for an S21 / S22 because they are going to have the Samsung specific changes.
twistedumbrella said:
I have the US version, which is why I abandoned the kernel. I had no way to test the changes specific to Samsung, which would be OneUI.
Your best bet would be looking into the changes for an S21 / S22 because they are going to have the Samsung specific changes.
Click to expand...
Click to collapse
ah ok thanks
for now i fix to kernel panic , now kernel boot in OneUI But after the loading icon the screens went black
so thanks again and sorry for disturbing you
No worries. I would rather you know I don't know, if that makes sense. Sounds like you are more than capable either way.