Developers - Merging Your Working Device

Search This thread

mcampbellsmith

Senior Member
Jul 1, 2010
815
1,128

Attachments

  • Screenshot_2013-10-22-22-15-58.jpg
    Screenshot_2013-10-22-22-15-58.jpg
    27.5 KB · Views: 453

xHausx

Inactive Recognized Developer
Jul 5, 2010
6,778
4,519
Central Florida
The Sprint HTC Evo LTE (qcom One X variant) is booting and runs decently, it still needs a lot of work before it's fully functional but it's off to a pretty good start.

Device: https://github.com/Haus1/android_device_htc_jewel
S4 common: https://github.com/Haus1/android_device_htc_s4-common
Kernel: https://github.com/Haus1/android_kernel_htc_msm8960
Blobs: https://github.com/Haus1/proprietary_vendor_htc

Thread: http://xdaforums.com/showthread.php?t=2495109

Some of the proprietary libs needed to be changed from the ones on the muppets. I manually edited my roomservice.xml to include the ones from my repo but haven't added it to the dependencies list yet.
 

Attachments

  • device-2013-10-22-215042.jpg
    device-2013-10-22-215042.jpg
    27.5 KB · Views: 307
Last edited:

superSUnoob

Senior Member
Aug 26, 2013
103
8
I hope there will be a OMNI rom built for the Samsung Galaxy Tab 2 :( as there are only 4 official builds for Samsung devices.


I have my fingers crossed :D
 

kalaker

Senior Member
Feb 23, 2012
490
290
Sprint HTC One

Sprint HTC One (m7spr, m7wls): http://xdaforums.com/sprint-htc-one
Existing thread: http://xdaforums.com/showthread.php?t=2500013

Device Folder: http://github.com/kalaker/android_device_htc_m7spr

Already forked by omni: android_device_htc_msm8960-common, android_device_htc_m7-common, android_kernel_htc_m7

Either this will need to be merged, or the overlay will need to be added to base: https://gerrit.omnirom.org/#/c/1757/

Edit:
Vendor files can be found at https://github.com/TheMuppets/proprietary_vendor_htc and m7-common and m7spr are required
 
Last edited:

mo976

Senior Member
Jun 17, 2008
1,144
1,170
Jerusalem Israel
The Sprint HTC Evo LTE (qcom One X variant) is booting and runs decently, it still needs a lot of work before it's fully functional but it's off to a pretty good start.

Device: https://github.com/Haus1/android_device_htc_jewel
S4 common: https://github.com/Haus1/android_device_htc_s4-common
Kernel: https://github.com/Haus1/android_kernel_htc_msm8960
Blobs: https://github.com/Haus1/proprietary_vendor_htc

Thread: http://xdaforums.com/showthread.php?t=2495109

Some of the proprietary libs needed to be changed from the ones on the muppets. I manually edited my roomservice.xml to include the ones from my repo but haven't added it to the dependencies list yet.

Hey do you think this would work for the One S? If you wouldn't mind sharing which are the changed libs as well as the edited roomservice that would be great.
I tried, but had all sorts of device config errors at the build menu so maybe what you have will do the trick.

Sent from my One S using XDA Premium 4 mobile app
 
Last edited:

xHausx

Inactive Recognized Developer
Jul 5, 2010
6,778
4,519
Central Florida
Hey do you think this would work for the One S? If you wouldn't mind sharing which are the changed libs as well as the edited roomservice that would be great.
I tried, but had all sorts of device config errors at the build menu so maybe what you have will do the trick.

Sent from my One S using XDA Premium 4 mobile app

Should be able to, if you want to pm with a link to your github I can take a look at it.
 

Gandalf

Inactive Recognized Developer / Retired Forum Mod
Mar 29, 2011
3,523
6,659
Philadelphia
Last edited:
  • Like
Reactions: Vcolumn and CNexus

zxc2622010

New member
Sep 21, 2012
1
0
I'd like to maintain for Xiaomi-M2

I'd like to maintain for Xiaomi-M2

device trees
github.com/mitwo-dev/android_device_xiaomi_aries

kernel
github.com/MiCode/mi2_kernel
 

Top Liked Posts

  • There are no posts matching your filters.
  • 41
    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.
    17
    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
    13
    @XpLoDWilD:

    For GalaxyR I9103(Tegra 2 Device)

    Device source : https://github.com/karthik050782/android_device_samsung_i9103

    Kernel Source : https://github.com/karthik050782/android_kernel_samsung_n1

    Its working great, no major bugs, Here is the unofficial development & discussion thread

    And I am fully available for the device support. Please let me know if any more information required..
    13
    It's time to spread the Christmas cheer, and share with all a gift
    For now, today, we shall go merge, the repos in this list.
    We thank to thee, for porting these, and raising up the call
    So git init, and repo sync, we'll bring omni to all.

    On behalf of everyone here at Omni, we wish you a happy Christmas.

    I have started the process with xplod of getting all these devices merged :)