Hi guys first sorry for post in this forum, i no have permission for write in the dev forum.
recently i get this terminal and i know it have a omap4430 and sgx540, so this hardware its similar to the galaxy nexus but jellybean 4.1.2 and 4.2.2 for my works horrible lag and unresponsive, and also something related to a fps issue that make the ui super slow.
so im working and trying to make a updated and revamped device tree for the lge p920 for jb 4.2.2, that include updated powervrsgx 540 modules and propietary drivers update to the lasted 4AJ.2.5, hwc, gralloc, libionpower, domx, libion, bltsville, etc etc. from omapzoom
at this moment i manage to get the updates for the omap44x from omapzoom, and also update the boardconfig for the new sources, its fully buildeable but at this time its not booteable and for my side adb no works for debug it.
so i have propose to all devs here for work together and try to make this work, im not a kernel dev, and my pc its so slow take 5 hours to compile the source. so for all devs here want to help and compile it for trying
this its de device tree:
github.com/samuaz/android_device_lge_p920
and also you need the updated propietary vendor:
github.com/samuaz/proprietary_vendor_lge
it can be buildable with cm10.1, aokp, pacman or whatever 4.2.2 rom
this week i try to rebuild it with a other pvrsources and boardconfig for try to make it booteable
and sorry for my english im spanish
thanks to all
it would be much easier to help you if you would fork a repo and then update the files with a new commit per file
so we can see what you've changed to what
eduzvargas said:
Hi guys first sorry for post in this forum, i no have permission for write in the dev forum.
recently i get this terminal and i know it have a omap4430 and sgx540, so this hardware its similar to the galaxy nexus but jellybean 4.1.2 and 4.2.2 for my works horrible lag and unresponsive, and also something related to a fps issue that make the ui super slow.
so im working and trying to make a updated and revamped device tree for the lge p920 for jb 4.2.2, that include updated powervrsgx 540 modules and propietary drivers update to the lasted 4AJ.2.5, hwc, gralloc, libionpower, domx, libion, bltsville, etc etc. from omapzoom
at this moment i manage to get the updates for the omap44x from omapzoom, and also update the boardconfig for the new sources, its fully buildeable but at this time its not booteable and for my side adb no works for debug it.
so i have propose to all devs here for work together and try to make this work, im not a kernel dev, and my pc its so slow take 5 hours to compile the source. so for all devs here want to help and compile it for trying
this its de device tree:
github.com/samuaz/android_device_lge_p920
and also you need the updated propietary vendor:
github.com/samuaz/proprietary_vendor_lge
it can be buildable with cm10.1, aokp, pacman or whatever 4.2.2 rom
this week i try to rebuild it with a other pvrsources and boardconfig for try to make it booteable
and sorry for my english im spanish
thanks to all
Click to expand...
Click to collapse
how far did you get with this.
in relation to hwc the ics kernel will not cut it there stuff missing i attempted to merge P920 with 3.0.31 kernel from P760
https://mega.co.nz/#!VQQw3BDS!OaeDOEaGSNE36-2ZylQVexGKqIEyrVXMSOBzH7JO2Is
need to fix errors
changes need to happen in
kernel/sound/soc/omap/omap-mcbsp.c
kernel/sound/soc/omap/omap-abe.c
kernel/include/linux/muic/muic.h
kernel/include/linux/fuel_gauge_max17043.h
kernel/include/linux/i2c/twl.h
kernel/include/linux/input/lge_touch_core.h
kernel/include/linux/i2c.h
kernel/include/linux/input.h
kernel/include/linux/cosmo/cosmo_muic.h
kernel/include/video/dsscomp.h
kernel/include/video/omapdss.h
kernel/include/net/ip6_fib.h
kernel/include/config/auto.conf
kernel/include/generated/mach-types.h
kernel/include/generated/autoconf.h
kernel/arch/arm/mach-omap2/hsmmc.c
kernel/arch/arm/mach-omap2/include/mach/lpddr2-elpida.h
kernel/arch/arm/mach-omap2/remoteproc.c
kernel/arch/arm/mach-omap2/prm44xx.c
kernel/arch/arm/mach-omap2/omap4_ion.c
kernel/arch/arm/mach-omap2/gpio.c
kernel/arch/arm/mach-omap2/lpddr2_elpida_data.c
kernel/arch/arm/mach-omap2/omap4_ion.h
kernel/arch/arm/mach-omap2/omap4-reboot-reason.c
kernel/arch/arm/mach-omap2/pm44xx.c
kernel/arch/arm/mach-omap2/lge/include/lge/board/cosmo.h
kernel/arch/arm/mach-omap2/lge/include/lge/board.h
kernel/arch/arm/mach-omap2/lge/Makefile.board
kernel/arch/arm/mach-omap2/lge/lge-common.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_i2c.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_keypad.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_cmdline.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_pdev.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_display.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_mmc.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo.c
kernel/arch/arm/configs/cyanogenmod_p920_defconfig
kernel/arch/arm/configs/cosmo_su760_defconfig
kernel/arch/arm/configs/cosmo_p920_defconfig
kernel/arch/arm/plat-omap/Makefile
kernel/fs/proc/base.c
kernel/kernel/timer.c
kernel/drivers/omap_hsi/hsi_driver.h
kernel/drivers/omap_hsi/xmd-tty.c
kernel/drivers/omap_hsi/xmd-hsi-ll.c
kernel/drivers/omap_hsi/hsi_driver_int.c
kernel/drivers/omap_hsi/xmd-hsi-ll-cfg.h
kernel/drivers/omap_hsi/Makefile
kernel/drivers/omap_hsi/xmd-ch.h
kernel/drivers/omap_hsi/hsi_driver.c
kernel/drivers/mmc/core/sd.c
kernel/drivers/video/omap2/displays/panel-lh430wv4-sd02.c
kernel/drivers/video/omap2/displays/panel-lh430wv2-sd01.c
kernel/drivers/video/omap2/dsscomp/dsscomp_adapt.c
kernel/drivers/video/omap2/dsscomp/gralloc.c
kernel/drivers/video/omap2/dsscomp/queue.c
kernel/drivers/video/omap2/dsscomp/device.c
kernel/drivers/video/omap2/vram.c
kernel/drivers/video/omap2/dss/dispc.c
kernel/drivers/video/omap2/dss/hdmi.c
kernel/drivers/video/omap2/dss/hdmi_panel.c
kernel/drivers/video/omap2/dss/gammatable.h
kernel/drivers/video/omap2/dss/core.c
kernel/drivers/input/touchscreen/lge_touch_core.c
kernel/drivers/input/touchscreen/touch_synaptics.c
kernel/drivers/input/touchscreen/lghdk_tm1709_ts.c
kernel/drivers/input/misc/twl6030-pwrbutton.c
kernel/drivers/input/keyboard/omap4-keypad.c
kernel/drivers/usb/gadget/f_mass_storage.c
kernel/drivers/rpmsg/rpmsg_omx.c
kernel/drivers/power/twl6030_bci_battery_ap_fuel.c
kernel/drivers/lge/subpmic/Makefile
kernel/drivers/lge/misc/Makefile
kernel/drivers/lge/Makefile
kernel/drivers/gpu/ion/omap/omap_tiler_heap.c
kernel/.config
kernel/.config.old
Click to expand...
Click to collapse
https://github.com/Pesach85/lge-kernel-omap4/search?p=1&q=CONFIG_MACH_LGE_COSMO&source=cc
i dunno if it would be easier to backport dsscomp to 3.0.21
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
Hello,
I recently downloaded the official AOSP source code into my machine and I want to compile it for my GT-I9300,
but before that where do I get the device blobs and properitary drivers from? Can I use CM's device tree? Are there any other device trees?
And in an addition to that how do I get the Kernel to work properly? Do I need to use the CM kernel?
A hint / tip or a link to a guide would be appreciated.
Thanks in advance
I can suggest you to go to xda university
I'm sure that you will find all you need for cooking your own build
Good luck
Hi,
I'm just starting to learn about how to compile and tweak a Linux kernel for Android devices. I'm using my old Xoom for testing. I've read a lot of tutorials/guides to build a kernel for Android, also I searched in the git history of the other kernels developed for the xoom (thanks for the developers!!) and I have a question that I can't answer. Maybe some of the kernel developers can answer it. What about the xoom's propietary drivers?
Basically I followed this guide https://source.android.com/source/building-kernels.html in order to get a kernel's image. Then I tested it and the Xoom boots and Android loads ok. Nowhere something about proprietary drivers is mentioned (https://developers.google.com/android/nexus/drivers#wingray). Are these drivers already loaded in the sources you can download from the first link?
The matter with the proprietary drivers is a lack of must guides and I want to know what's going on with drivers when you build the kernel sources for tegra devices.
I have an One s with S3 processer(villeC2).
Its specs are similar to sensation(with same cpu and screen resolution),but sensation has Android 7.1 ROM and one s only 4.4......
I would like to port a ROM for it from sensation.
Does anyone know how to do that?
Or if it is possible ?
(sorry for my bad english)
(my first post)
Some info !
Hi,
Actually I'm new in building roms and kernels, too. But i can share some info with you.
For starting this tutorial may be helpful: [Guide] Compile 4.2 & 4.3 & 4.4 Roms for villec2
As you can see, you will need "device", "vendor" and "kernel" source to build a rom.
Usually you can find source code of roms and kernels in xda threads and can start from those.
For example for Android 7.1 you can use RROS vendor and VilleC2 device and kernel sources. (Note: i don't know are these examples compatible or not?!)
And for kernel, maybe you has to upstream the kernel source to be compatible with new version of android that you want to build.
Good luck.
-----------------------------------
Edit:
After Compiling for myself, i figured out Vendor files for choosed rom (Lineage, RR, ..) will be included by their manifest files automatically. so for "Vendor" part in "local_manifest.xml" (or newer "local_manifests/roomservice.xml") we need to assign "proprietary_vendor" files related to our devices. "proprietary_vendor" files can be extracted manully if there isn't any online source.
one more useful guide: [GUIDE]Building any ROM from source for HTC One S aka ville!