[ROM][DEV-WIP][Unofficial]Liquid Smooth

[ROM][DEV-WIP][Unofficial]Liquid Smooth - HTC Rezound

I'm working on getting Liquid Smooth running on the Rezound. PM me if you're interested in working on this.
Liquid comes setup to build with linaro and a 4.7 toolchain so it's being kind of a PITA.
I'm using the manifest here:
Code:
repo init -u git://github.com/LiquidSmooth/android.git -b jb2
and this is my local_manifests/vigor.xml file
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="gh" fetch="git://github.com/" />
<!-- Use iHateWEBos Hiro Kernel -->
<project path="kernel/htc/hiro" name="iHateWEBos/vigor_aosp_kernel" remote="gh" revision="cm-10.1" />
<!-- Use Flyhalf205 Vendor Tree, msm8660 Common Tree, and Media Legacy Tree -->
<project path="vendor/htc/vigor" name="Flyhalf205/vendor_htc_vigor" remote="gh" revision="cm-10.1" />
<project path="device/htc/msm8660-common" name="Flyhalf205/android_device_htc_msm8660-common" remote="gh" revision="cm-10.1" />
<project path="hardware/qcom/media-legacy" name="Flyhalf205/android_hardware_qcom_media-legacy" remote="gh" revision="cm-10.1" />
<!-- Liquid Smooth Device Tree -->
<project path="device/htc/vigor" name="dlumberg/device_htc_vigor-liquid" remote="gh" revision="4.2.2" />
<!-- Made a few changes to display legacy to get it to build on gcc 4.7 -->
<project path="hardware/qcom/display-legacy" name="dlumberg/hardware_qcom_display-legacy" remote="gh" revision="gcc-4.7" />
<!-- Oprofile was throwing errors looking for a header file that didn't exist. This may be fixed upstream, if not comment oprofile in
the default.xml file and uncomment this.
<project path="external/oprofile" name="dlumberg/external_orpofile-liquid" remote="gh" revision="4.2.2" /> -->
</manifest>

So far I'm still getting build errors but making progress. Yesterday I had it building up to the kernel using Flyhalf's kernel tree but it was erroring out on some gcc 4.7 differences so I switched to Hiro. Then it was erroring out on some java/apps stuff but it looks like they pushed a lot of changes last night so I did a fresh repo sync and I'm trying to build now to see where it's at.

I'll look later. Too many projects on my plate.
Sent from my ADR6425LVW using Xparent ICS Tapatalk 2

Snuzzo said:
I'll look later. Too many projects on my plate.
Sent from my ADR6425LVW using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
No worries, I just didn't want to clog up the Hiro thread with liquid questions and comments.

dlumberg said:
No worries, I just didn't want to clog up the Hiro thread with liquid questions and comments.
Click to expand...
Click to collapse
Yup exactly. Either way, I miss LS from my old OG Droid1 days when it was the top notch gingerbread rom. Hell I sometimes load up good ole LFY 1.9.6. Wish RaidZero continued his developments cause his Froyo rom was top notch also.

Snuzzo said:
Yup exactly. Either way, I miss LS from my old OG Droid1 days when it was the top notch gingerbread rom. Hell I sometimes load up good ole LFY 1.9.6. Wish RaidZero continued his developments cause his Froyo rom was top notch also.
Click to expand...
Click to collapse
That's why I was asking well :thumbup: liquid was one of the smoothest roms I ran on my OG Droid.
Sent from my ADR6425LVW using Tapatalk 2

To get by the build errors in msm7k change the LOCAL_CFLAGS line in /hardware/msm7k/librpc/Android.mk to
Code:
LOCAL_CFLAGS:= -fno-short-enums -fno-strict-aliasing
It's being caused by strict-aliasing being turned on by default in linaro level 3 optimization.

dlumberg said:
To get by the build errors in msm7k change the LOCAL_CFLAGS line in /hardware/msm7k/librpc/Android.mk to
Code:
LOCAL_CFLAGS:= -fno-short-enums -fno-strict-aliasing
It's being caused by strict-aliasing being turned on by default in linaro level 3 optimization.
Click to expand...
Click to collapse
Have you looked into the Help thread for Linaro building that is in this forum? Might come in handy. We have a script with cherry-picks for building Linaro. May help to you?

dlumberg said:
I'm working on getting Liquid Smooth running on the Rezound. PM me if you're interested in working on this.
Liquid comes setup to build with linaro and a 4.7 toolchain so it's being kind of a PITA.
I'm using the manifest here:
Code:
repo init -u git://github.com/LiquidSmooth/android.git -b jb2
and this is my local_manifests/vigor.xml file
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="gh" fetch="git://github.com/" />
<!-- Use iHateWEBos Hiro Kernel -->
<project path="kernel/htc/hiro" name="iHateWEBos/vigor_aosp_kernel" remote="gh" revision="cm-10.1" />
<!-- Use Flyhalf205 Vendor Tree, msm8660 Common Tree, and Media Legacy Tree -->
<project path="vendor/htc/vigor" name="Flyhalf205/vendor_htc_vigor" remote="gh" revision="cm-10.1" />
<project path="device/htc/msm8660-common" name="Flyhalf205/android_device_htc_msm8660-common" remote="gh" revision="cm-10.1" />
<project path="hardware/qcom/media-legacy" name="Flyhalf205/android_hardware_qcom_media-legacy" remote="gh" revision="cm-10.1" />
<!-- Liquid Smooth Device Tree -->
<project path="device/htc/vigor" name="dlumberg/device_htc_vigor-liquid" remote="gh" revision="4.2.2" />
<!-- Made a few changes to display legacy to get it to build on gcc 4.7 -->
<project path="hardware/qcom/display-legacy" name="dlumberg/hardware_qcom_display-legacy" remote="gh" revision="gcc-4.7" />
<!-- Oprofile was throwing errors looking for a header file that didn't exist. This may be fixed upstream, if not comment oprofile in
the default.xml file and uncomment this.
<project path="external/oprofile" name="dlumberg/external_orpofile-liquid" remote="gh" revision="4.2.2" /> -->
</manifest>
Click to expand...
Click to collapse
I have been working on this but stopped a month ago due to life getting in the way. You have to disable the -O3 optimizations to get it to build. I'll have to look at my files when I get home. I redid a bunch but didn't get to see how far my build gets.
Sent from my Rezound using xda app-developers app

Flyhalf205 said:
Have you looked into the Help thread for Linaro building that is in this forum? Might come in handy. We have a script with cherry-picks for building Linaro. May help to you?
Click to expand...
Click to collapse
I'll definitely keep my eye on it. Liquid has linaro built into their manifest so it might be useful to check their default.xml file for git repos that already have cm-10.1-linaro optimizations. It looks like there's a ton of them here: http://github.com/loosethisskin/

tburns said:
I have been working on this but stopped a month ago due to life getting in the way. You have to disable the -O3 optimizations to get it to build. I'll have to look at my files when I get home. I redid a bunch but didn't get to see how far my build gets.
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
I didn't have to disable -O3 to get it to build for my tf101, granted there's no soft keys and it's running slow as hell but it built. I'm wondering if they may have changed some things since you last synced... After I changed the -fno-strict-aliasing (which can also be changed to -Wstrict-aliasing) it's just been chugging away.
What kernel were you trying to build with before? I know that a lot of the errors that I saw were in the kernel and I haven't had them since I switched to Hiro.

dlumberg said:
I didn't have to disable -O3 to get it to build for my tf101, granted there's no soft keys and it's running slow as hell but it built. I'm wondering if they may have changed some things since you last synced... L
What kernel were you trying to build with before? I know that a lot of the errors that I saw were in the kernel and I haven't had them since I switched to Hiro.
Click to expand...
Click to collapse
Yea it was awhile ago and I got Werrors. I posted my initial errors in the build your own CM10.1 thread.
I tried 3 different kernels. Funky wouldn't build and reverted back to flyhalfs.
I'll test another build this weekend.
Sent from my Rezound using xda app-developers app

tburns said:
Yea it was awhile ago and I got Werrors. I posted my initial errors in the build your own CM10.1 thread.
I tried 3 different kernels. Funky wouldn't build and reverted back to flyhalfs.
I'll test another build this weekend.
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
Need to use Sabermod 4.8 gcc arm eabi or a patched version of CodefireX 4.8 gcc arm eabi.
Sent from my ADR6425LVW using Xparent ICS Tapatalk 2

THIS IS VERY VERY EXPERIMENTAL, I AM NOT RESPONSIBLE FOR YOUR PHONE... I haven't even tested it yet...
On second thought... I'll PM the people from the other thread. PM me if you want it...

Non booting but I am getting a last_kmsg at least. Unable to pull a logcat.

Snuzzo said:
Non booting but I am getting a last_kmsg at least. Unable to pull a logcat.
Click to expand...
Click to collapse
I was just about to post that it's not booting...
Is that the kernel that's built in? Interesting that it says funkybean if it is. Otherwise did you try flashing another kernel? I'll try tomorrow but I've gotta crash now for today.
Sent from my ADR6425LVW using xda app-developers app

I tried the built in Hiro, Ion funkybean, and fastbooting Funkybean 3.6. That txt was from the fast boot.
Sent from my Nexus 7 using Tapatalk HD

Snuzzo said:
Non booting but I am getting a last_kmsg at least. Unable to pull a logcat.
Click to expand...
Click to collapse
It's hard to read through. looks like there is some USB errors, but it looks like the fatal error occurred while trying to connect to data.
Sent from my ADR6425LVW using xda premium

iHateWebOS said:
It's hard to read through. looks like there is some USB errors, but it looks like the fatal error occurred while trying to connect to data.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
That's what i was thinking but wasn't quite too too sure.
Sent from my Nexus 7 using Tapatalk HD

Snuzzo said:
That's what i was thinking but wasn't quite too too sure.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I wonder if it's the audio system... here's a dmesg from cm10-1... if you search for "Dongle Host Driver, version 5.90.195.75" (where the WiFi comes up) that's pretty much where the 2 diverge. In CM I'm seeing a bunch of USB stuff coming up then a bunch of Audio stuff that doesn't seem to be in the Liquid one.

Related

[4.2] [QuickSettings] How to add new toggles to 4.2 Android

This is just going to be a quick rundown on what do to add new toggles to android new QuickSettings system. This will take place in SystemUI.
Custom QuickSettings Toggles
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Path: frameworks/base/packages/SystemUI
Files:
src/com/android/systemui/statusbar/phone/QuickSettings.java
There are two options when creating a toggle.
addSystemTiles:380 - Static tiles with useful information.
addTemporaryTiles:571 - This type of tile will get removed without activity, for example, the alarm quick setting is a temp tile.
I used SystemTiles
Code:
// CpuInfo tile
QuickSettingsTileView cpuInfoTile = (QuickSettingsTileView)
inflater.inflate(R.layout.quick_settings_tile, parent, false);
cpuInfoTile.setContent(R.layout.quick_settings_tile_cpuinfo, inflater);
cpuInfoTile.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {
startSettingsActivity(Intent.ACTION_POWER_USAGE_SUMMARY);
}
});
mModel.addCpuInfoTile(cpuInfoTile, new QuickSettingsModel.RefreshCallback() {
@Override
public void refreshView(QuickSettingsTileView view, State state) {
ImageView iv = (ImageView) view.findViewById(R.id.cpuinfo_image);
TextView tva = (TextView) view.findViewById(R.id.cpuinfoa_textview);
TextView tvb = (TextView) view.findViewById(R.id.cpuinfob_textview);
Drawable d = mContext.getResources().getDrawable(R.drawable.ic_settings_performance);
String GOV = fileReadOneLine(GOV_FILE);
String FREQ = fileReadOneLine(SCALE_CUR_FILE);
iv.setImageDrawable(d);
tva.setText(GOV);
tvb.setText(FREQ);
view.setContentDescription(
mContext.getString(R.string.accessibility_quick_settings_cpuinfo, GOV));
}
});
parent.addView(cpuInfoTile);
src/com/android/systemui/statusbar/phone/QuickSettingsModel.java:174
This is needed for the widget inside the toggle to get updated. You can view other definitions in here to update various states.
Code:
private QuickSettingsTileView mCpuInfoTile;
private RefreshCallback mCpuInfoCallback;
private State mCpuInfoState = new State();
res/layout/quick_settings_tile_cpuinfo.xml
This is where we create the layout of the tile and call it from java.
Code:
<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2012 The Android Open Source Project
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<LinearLayout
xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_gravity="center"
android:orientation="vertical">
<ImageView
android:id="@+id/cpuinfo_image"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_gravity="center"
android:paddingBottom="10dp"
/>
<TextView
style="@style/TextAppearance.QuickSettings.TileView"
android:id="@+id/cpuinfoa_textview"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_gravity="center"
android:textColor="#287AA9"
android:gravity="center"
/>
<TextView
style="@style/TextAppearance.QuickSettings.TileView"
android:id="@+id/cpuinfob_textview"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_gravity="center"
android:textColor="#287AA9"
android:gravity="center"
/>
</LinearLayout>
res/values/strings.xml
Needed to setContentDescription()
Code:
<string name="accessibility_quick_settings_cpuinfo">CpuInfo <xliff:g id="meminfo" example="CpuInfo">%s</xliff:g>.</string>
I know this is a very general overview, but the actuality is there is so much that can be done with this, it would be hard to go into extreme detail. Would be better to just simply leave that stuff for questions in this thread.
If you want to know more, please just ask. Lets make android OURS!

Would root be required to implement this?
Sent from my SGH-I997 using xda premium

marty331 said:
Would root be required to implement this?
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
It would be since you have to push the file back onto the system.

Hi , great tutorial:thumbup:
Can you show us the smali version?
Thanks

Ofeliax said:
Hi , great tutorial:thumbup:
Can you show us the smali version?
Thanks
Click to expand...
Click to collapse
No idea, I have no experience using smali. You can just compile SystemUI from source.

Lithid ur the man. Once I can get this inline kernel building accomplished for aosp for my device, I can compile it. Then I will be playing with this for sure!! I can't wait!

lithid-cm said:
It would be since you have to push the file back onto the system.
Click to expand...
Click to collapse
Or just create a flashable zip. Then flash the new modded app

Peteragent5 said:
Or just create a flashable zip. Then flash the new modded app
Click to expand...
Click to collapse
Not really the point of this thread.

Geest tutorial, this is gonna be my first thing to do when I come back from school lol!
Sent from my Galaxy Nexus using Tapatalk 2

How did you decompile your SystemUI?
When I try to do that with mine it's giving an error ..
Sent from my Galaxy Nexus using Tapatalk 2

mDroidd said:
How did you decompile your SystemUI?
When I try to do that with mine it's giving an error ..
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
From source.
Code:
time make -j8 SystemUI

Will this work with CM10 4.1.2?

No, 4.2 only, as stated by OP
Sent from my Galaxy Nexus using Tapatalk 2

Mlopik said:
Will this work with CM10 4.1.2?
Click to expand...
Click to collapse
mDroidd said:
No, 4.2 only, as stated by OP
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'd assume he process would be very similar as cm is based off aosp...
Anyways I'm currently downloading the 4.2 aosp, gonna be making (trying) my own rom and will definitely be using this guide in the near future after Im sure I can get everything built. Thanks for the guide, if I'm successfully with what I plan to do, you will definitely be linked and credited.
Sent from my SGH-I997 using Tapatalk 2

mg2195 said:
I'd assume he process would be very similar as cm is based off aosp...
Anyways I'm currently downloading the 4.2 aosp, gonna be making (trying) my own rom and will definitely be using this guide in the near future after Im sure I can get everything built. Thanks for the guide, if I'm successfully with what I plan to do, you will definitely be linked and credited.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
I was thinking about putting myself in front of a rom recently. If you are at all interested in teaming up for a rom project, PM. You seem legit and wouldn't mind it one bit.

This is badass!! Thank you so much lithid!!!!
EDIT: Question, What are the numbers representing?
addSystemTiles:380
addTemporaryTiles:571
Click to expand...
Click to collapse
I assumed they were line numbers but when I checked source it didn't look like anything was referring to addSystemTiles or addTemporaryTiles on those line numbers.

I might have to revisit that, those line numbers are from my file, which is already been edited.
Sent from my Galaxy Nexus using xda premium

lithid-cm said:
I might have to revisit that, those line numbers are from my file, which is already been edited.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Makes sense. Thanks.

nice tutorial
btw, 4.1.2 and 4.2.1 quicksettings are not same dear Mlopik.

You can do this with stock 4.2.1 (rooted) ?

Ubuntu Touch port being worked on for quincyatt

It looks like our phone just won't die! Which is AWESOME!
https://wiki.ubuntu.com/Touch/Devices
Head to the above link and scroll down to where it shows the work in progress devices and we're listed. Pretty cool.

Cool! quincyatt right there under work in progress. I'll give it a try if it gets loosed.

A dev would have to make a flashable ROM out of it
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

it is out for the galaxy nexus now.
no data though

That is the thing. Read the working/not working sections. No 3G/4G. Which means no data, calls or texting. Basically making your smartphone a dumb paper weight.
While I would love to see it, until they can get something working so that it can be used it is nothing more than a fancy.
Sent from the Note-rix

KSoD said:
That is the thing. Read the working/not working sections. No 3G/4G. Which means no data, calls or texting. Basically making your smartphone a dumb paper weight.
While I would love to see it, until they can get something working so that it can be used it is nothing more than a fancy.
Sent from the Note-rix
Click to expand...
Click to collapse
hmmm as far as I read over in the g nexus section calls, texts and wifi work, just not data.

KSoD said:
That is the thing. Read the working/not working sections. No 3G/4G. Which means no data, calls or texting. Basically making your smartphone a dumb paper weight.
While I would love to see it, until they can get something working so that it can be used it is nothing more than a fancy.
Sent from the Note-rix
Click to expand...
Click to collapse
since when does a phone need 3g or 4g to make a phone call, send a text or have data? data speed has nothing to do with calls and texting and there is still an EDGE network out there....not fast but it IS data (not saying that this would even support a data connection at all....just saying that it's not needed for voice and text...thought that was common sense)

So... What's going on with this... I've read news that ubuntu touch has gone stable for nexus devices along with working builds for the n7000 note - is there someone working on an i717 / quincyatt build? I'd really like to play with this but i'm not hardcore enough of a developer to build a port...

Awesome. I'm ready to retire the i717 of its primary phone duties now that I have a Note 3 so an Ubuntu build to play around with sounds awesome. I really want desktop Ubuntu to test out the open source Freedreno drivers though.
Sent from my SM-N900T using xda app-developers app

I too am interested in this. Started some research tonight, but I don't even see it listed on their Device page. Correct me if I overlooked it.

They're not developing it for our device. I emailed the dev a long time ago. He said he sold his device and is no longer working on it.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

Attempted Ubuntu Touch port
I saw this thread a couple days ago and decided to try and port it. It boots up to the Ubuntu Phablet Login: prompt and then just sits there. I can't access it over adb to figure out why it is failing to load the GUI. It does display text on the screen when I tap the screen or unplug the usb cable so it isn't frozen.
I added a kernel cmdline parameter to stop it at the bottom of the initrd sequence and was able to pull the attached kmesg over adb.
Maybe someone can look at it and see why it is failing.
Thanks,
Troy

I'll play with it this weekend, at least they have a kernel with working framebuffer, maybe a USB keyboard with OTG cable could switch into a VT and do something. If it's Ubuntu I wouldn't expect adb to do anything since that's an Android component, but it's also not impossible to use on a non-Android distro.
Sent from my SM-N900T using xda app-developers app

If someone can do this that would be so awesome

CalcProgrammer1 said:
Awesome. I'm ready to retire the i717 of its primary phone duties now that I have a Note 3 so an Ubuntu build to play around with sounds awesome. I really want desktop Ubuntu to test out the open source Freedreno drivers though.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Quincyatt used to be on the dev list. It seems that it was removed at some point.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

GPFerror said:
I saw this thread a couple days ago and decided to try and port it. It boots up to the Ubuntu Phablet Login: prompt and then just sits there. I can't access it over adb to figure out why it is failing to load the GUI. It does display text on the screen when I tap the screen or unplug the usb cable so it isn't frozen.
I added a kernel cmdline parameter to stop it at the bottom of the initrd sequence and was able to pull the attached kmesg over adb.
Maybe someone can look at it and see why it is failing.
Thanks,
Troy
Click to expand...
Click to collapse
Do you have a link to your build and the instructions you're basing your port off of? I see you have at least got a kernel that prints out to the fbconsole which is great. I'm really interested in running this, or at least the kernel to boot a desktop rootfs from. Don't really care if it's not totally useful since my i717 is no longer my primary device, just looking to hack it into an Ubuntu machine.
EDIT: Going to attempt my own port, the instructions on the Ubuntu Touch porting wiki page are pretty straightforward, looks like they build off of CM10.1.
EDIT 2: I got my work tree all checked out, trying to build fails with:
Code:
make: *** No rule to make target `/media/RAID5/AndroidCode/ubuntu_quincyatt/out/target/product/quincyatt/obj/lib/libaudioalsa.so', needed by `/media/RAID5/AndroidCode/ubuntu_quincyatt/out/target/product/quincyatt/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/LINKED/audio.primary.msm8660.so'. Stop.
I have tried switching from cm10.1 branch to cm10.2 branch for the quincyatt stuff but that still failed on libaudioalsa.so. I also removed the Device Settings folder from msm8660-common since it was failing inside of that folder bulding the Advanced Settings/GalaxyS2Settings app.
EDIT 3: You need the proprietary vendor files. Either follow the extract procedure or just simply pull in the proprietary_vendor_samsung github repository to your local manifests file. I had a personal copy from when I ported AOKP but you can use the CM one:
Code:
<project name="CalcProgrammer1/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.2" />
I put that in roomservice.xml.

CalcProgrammer1 said:
Do you have a link to your build and the instructions you're basing your port off of? I see you have at least got a kernel that prints out to the fbconsole which is great. I'm really interested in running this, or at least the kernel to boot a desktop rootfs from. Don't really care if it's not totally useful since my i717 is no longer my primary device, just looking to hack it into an Ubuntu machine.
EDIT: Going to attempt my own port, the instructions on the Ubuntu Touch porting wiki page are pretty straightforward, looks like they build off of CM10.1.
EDIT 2: I got my work tree all checked out, trying to build fails with:
Code:
make: *** No rule to make target `/media/RAID5/AndroidCode/ubuntu_quincyatt/out/target/product/quincyatt/obj/lib/libaudioalsa.so', needed by `/media/RAID5/AndroidCode/ubuntu_quincyatt/out/target/product/quincyatt/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/LINKED/audio.primary.msm8660.so'. Stop.
I have tried switching from cm10.1 branch to cm10.2 branch for the quincyatt stuff but that still failed on libaudioalsa.so. I also removed the Device Settings folder from msm8660-common since it was failing inside of that folder bulding the Advanced Settings/GalaxyS2Settings app.
EDIT 3: You need the proprietary vendor files. Either follow the extract procedure or just simply pull in the proprietary_vendor_samsung github repository to your local manifests file. I had a personal copy from when I ported AOKP but you can use the CM one:
Code:
<project name="CalcProgrammer1/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.2" />
I put that in roomservice.xml.
Click to expand...
Click to collapse
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_quincyatt" path="device/samsung/quincyatt" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_quincy-common" path="device/samsung/quincy-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.1" />
</manifest>
Is what I used, and had to remove the building of the same settings apk.
I'll try to post a diff later tonight when I'm home. Hard to copy and paste via terminal emulator on phone
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

GPFerror said:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_quincyatt" path="device/samsung/quincyatt" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_quincy-common" path="device/samsung/quincy-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.1" />
</manifest>
Is what I used, and had to remove the building of the same settings apk.
I'll try to post a diff later tonight when I'm home. Hard to copy and paste via terminal emulator on phone
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I left my version of the proprietary stuff in but went back to 10.1 for the others and it built successfully. I haven't edited fstab or kernel config yet though, going to make those edits and build again.

CalcProgrammer1 said:
Thanks, I left my version of the proprietary stuff in but went back to 10.1 for the others and it built successfully. I haven't edited fstab or kernel config yet though, going to make those edits and build again.
Click to expand...
Click to collapse
Ok I have attached my repo.diff, I have a couple other changes that I found on the ubuntu maillist and on other ports.
Thanks,
Troy

GPFerror said:
Ok I have attached my repo.diff, I have a couple other changes that I found on the ubuntu maillist and on other ports.
Thanks,
Troy
Click to expand...
Click to collapse
Ok, I'm getting to the same point as your dmesg log shows, it doesn't boot up just hangs after it mounts the filesystem. I tried a USB keyboard with OTG and it worked fine so if you can get it back to where it shows a login prompt you might be able to plug in a keyboard and login with that.
http://imgur.com/XUtb5aH
http://imgur.com/a/u0EM4

[ROM][GT-I9100][WIP] Ubuntu Touch Developer Preview

Ubuntu Touch Developer Preview
for GT-I9100
Keep in mind that this is only a developer preview, and will probably not function as an everyday ROM.
I will not be responsible for any damage caused by flashing this ROM or anything related.
Downloads:
Download the following and put them on your sdcard:
(deprecated) saucy-preinstalled-touch-armel-i9100.zip / (Google Drive mirror)
cm-10.1-20131129-UNOFFICIAL-i9100.zip (Diamond5170's build)
trusty-preinstalled-touch-armhf.zip
Optionally (but preferably) control the md5 checksums:
(deprecated) saucy-preinstalled-touch-armel-i9100.zip.md5sum / (Google Drive mirror)
MD5SUMS
Flashing instructions:
wipe data/factory reset (Make backup first)
flash cm-10.1-********-UNOFFICIAL-i9100.zip
flash trusty-preinstalled-touch-armhf.zip
reboot
(optional) Try to enable 3G data (link)
Current status:
Not working (specific to this device):
Calls/SMS
Audio
Sensorservice problem after reboot
solve by adding to /etc/rc.local:
Code:
./system/bin/sensorservice &
(Diamond5170's original post)
3G data might work if you follow this guide:
https://plus.google.com/100264483712374857174/posts/3o1tjYo9Ghx
Click to expand...
Click to collapse
Please report what's working and not in this thread to complete this list.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshots by IconRunner, see http://imgur.com/a/LL53v for more.
Screenshots by aryan1312, see http://forum.xda-developers.com/showpost.php?p=39087781&postcount=11 for more.
Repos:
The Github repos for this device can be found here:
https://github.com/UbuntuTouch-smdk4210
If you wish to build an image yourself, do the following:
Set up your build environment
Run:
Code:
$ cd <project root>
$ repo init -u git://phablet.ubuntu.com/CyanogenMod/android.git -b phablet-trusty
Create file <project root>/.repo/local_manifests/roomservice.xml with the following contents:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="UbuntuTouch-smdk4210/android_device_samsung_i9100" path="device/samsung/i9100" remote="github" revision="refs/heads/phablet-saucy" />
<project name="UbuntuTouch-smdk4210/android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" remote="github" revision="refs/heads/phablet-saucy" />
<project name="UbuntuTouch-smdk4210/android_kernel_samsung_smdk4412" path="kernel/samsung/smdk4412" remote="github" revision="refs/heads/phablet-saucy" />
<project name="UbuntuTouch-smdk4210/android_hardware_samsung" path="hardware/samsung" remote="github" revision="refs/heads/phablet-saucy" />
<project name="UbuntuTouch-smdk4210/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="refs/heads/phablet-saucy" />
</manifest>
Run:
Code:
$ repo sync
$ . build/envsetup.sh
$ brunch i9100
Now your flashable .zip file should be in <project root>/out/target/product/i9100/cm-10.1-********-UNOFFICIAL-i9100.zip
To update your working tree, run the following commands:
Code:
$ repo sync
$ . build/envsetup.sh
$ brunch i9100
You should now have a new flashable .zip file <project root>/out/target/product/i9100/cm-10.1-********-UNOFFICIAL-i9100.zip.
You might want to run 'make clean' or 'make clobber' before 'brunch i9100' to be certain that each change gets compiled.

MaxWallstedt said:
Ubuntu Touch Developer Preview
for GT-I9100
Keep in mind that this is only a developer preview, and will probably not function as an every-day rom.
I will not be responsible for any damage caused by flashing this rom or anything related.
Download the following and put them on your sdcard:
Code:
https://dl.dropbox.com/u/44436922/cm-10.1-20130312-UNOFFICIAL-i9100.zip
and
Code:
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/quantal-preinstalled-phablet-armhf.zip
or
Code:
http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/quantal-preinstalled-phablet-armhf.zip
Flashing instructions:
1. install CyanogenMod 10.1 on your device, if not already installed (http://forum.xda-developers.com/showthread.php?t=2036229)
2. wipe data/factory reset (Make backup first)
3. flash cm-10.1-20130312-UNOFFICIAL-i9100.zip
4. flash quantal-preinstalled-phablet-armhf.zip
5. reboot
Click to expand...
Click to collapse
Do we need to install hdpi_overlay?

alien0101 said:
Do we need to install hdpi_overlay?
Click to expand...
Click to collapse
There should be need for that anymore!

https://dl.dropbox.com/u/44436922/cm-10.1-20130312-UNOFFICIAL-i9100.zip
http://cdimage.ubuntu.com/ubuntu-to...urrent/quantal-preinstalled-phablet-armhf.zip
Just make the links work so people can use it directly.....thx...keeping this updated makes it much easier.
Sent from my GT-I9100 using xda premium

I don't mean to spam threads, but since all the action seems to have moved here I will repost. Do we keep recovery? Can we go back to cm10.1 without using Odin/Heimdall?
Enviado desde mi GT-I9100 usando Tapatalk 2

Awesome! Great job!
It would be nice to have a changelog tracing what works and what doesn't and what are the known issues.

juanono said:
I don't mean to spam threads, but since all the action seems to have moved here I will repost. Do we keep recovery? Can we go back to cm10.1 without using Odin/Heimdall?
Enviado desde mi GT-I9100 usando Tapatalk 2
Click to expand...
Click to collapse
Yes, you keep recovery (but with a nice ubuntu logo) and can restore your backups through it.

juanono said:
I don't mean to spam threads, but since all the action seems to have moved here I will repost. Do we keep recovery? Can we go back to cm10.1 without using Odin/Heimdall?
Enviado desde mi GT-I9100 usando Tapatalk 2
Click to expand...
Click to collapse
Since it's cm based, you'll keep recovery, so if you're done playing around with this, just wipe data & flash new rom!
Greetings
Sent from my GT-I9100 using xda app-developers app

any known bugs?

Fulfen said:
any known bugs?
Click to expand...
Click to collapse
Issues fonts and wifi are solved...its awesome
Sent from my GT-I9100 using xda premium

Snapshot
Here are few snapshot of Ubuntu touch :
I jst installed to files :
1st https://dl.dropbox.com/u/44436922/cm-10.1-20130312-UNOFFICIAL-i9100.zip
2nd http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/
*Daily update files are causing some problem*
Even though gmail and facebook app opens, but they don't let u log in how much u try u will " error in password "
browser is working, from u can login in gmail but facebook opens in simple text format
Two finger gesture works fine on notification bar
app manager work fine

I think we have to move this to development section.

liawim said:
Issues fonts and wifi are solved...its awesome
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
phone and messaging works normally?
---------- Post added at 01:35 PM ---------- Previous post was at 01:27 PM ----------
deedii said:
I think we have to move this to development section.
Click to expand...
Click to collapse
+1

Just mailed to ubuntu touch dev team to update touch/devices site.
Sent from my GT-I9100 using xda premium

I added the original entry into the wiki.
I'll change it later on.
Max: can I add you as a contact ?

This is the third thread of Ubuntu Touch for the S2.......
Mine has been out for ages, look in my signature for the link.
Let the grown ups develop son.
You didn't even say what file they must download from the Ubuntu server.........

phablet.zip links
please dont link to the mwc-demo, it is highly outdated, if you use the daily builds and find bugs please report them, we will try to fix them (like we fixed the browser issue over night in the last daily)

ogra-ubuntu said:
please dont link to the mwc-demo, it is highly outdated, if you use the daily builds and find bugs please report them, we will try to fix them (like we fixed the browser issue over night in the last daily)
Click to expand...
Click to collapse
Removed in my post.
Sent from my GT-I9100 using xda premium

Bubble-be said:
I added the original entry into the wiki.
I'll change it later on.
Max: can I add you as a contact ?
Click to expand...
Click to collapse
Yes, you can.
ogra-ubuntu said:
please dont link to the mwc-demo, it is highly outdated, if you use the daily builds and find bugs please report them, we will try to fix them (like we fixed the browser issue over night in the last daily)
Click to expand...
Click to collapse
Ok, I will remove the link in the first post!

Hey max if u want u can add my screenshots ... i don't even need credit for that u are free to use them...
and thnx for the great work...:highfive::good:
I will add a video asap... i was recording a video but sadly my camera was not focusing so i decided to upload jst snapshot...

SEMI-PURE AOSP ROM - 5.1 LMY47I (06.04.2015)

PURE AOSP ROM FOR NEXUS 5
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is pure AOSP rom for Nexus 5 build straight from google source(latest revision 5.1.0_r1)
Removed some stuff(live wallpapers)
This project is in learning mode,which means i will try to explain all stuff i do with rom,
including building,modifying,github stuff,etc.
ROM DOWNLOAD:
06.04.2015
Latest source built 5.1
Stock kernel included.
AOSP bootanimation included(credits to guerreromanuel).
Banks gapps minimal included (credits to euroskank).
Unique set of ringtones played on Ibanez RG 350DX.
Rom flash takes 5 min to flash.DO NOT PANIC!!!!
Rom is named aosp SEMIPURE 20150406 .zip.
ROM Download on GDrive
ROM Download in DEVDB
INSTALL INSTRUCTIONS:
1.Download rom
2.Download Supersu(in same folder)
3.Reboot in recovery
4.Full wipe
5.Install rom and supersu.
7.Reboot
Thanks and credits:
Google for source
chainfire for supersu
guerreromanuel for bootanimation.
euroskank for gapps.

Random videofrom my YOUTUBE channel
XDA:DevDB Information
SEMI-PURE AOSP ROM - 5.1 LMY47I (06.04.), ROM for the Google Nexus 5
Contributors
malcho
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Alpha
Created 2014-12-26
Last Updated 2015-04-07

GUIDE 1
Initiate build enviroment and download source.
This link contains all that is needed to initialize source build on ubuntu.I suggest use LTS(long term support) versions of ubuntu.
https://source.android.com/source/initializing.html
Here is the link where you can find how to download source and initialize repo.
https://source.android.com/source/downloading.html
Pay attention on how to choose the right branch.You can find all info about branches here.
https://source.android.com/source/build-numbers.html
For example if you want to build from the latest brunch choose android-5.0.2_r1.
After this download binaries(drivers)for your device.
You have to download three files.Broadcom,LG and Qualcom.
Copy three files to your build directory.If you create folder /build/aosp copy files to that directory nad extract it.
Run all file with following commands,for example ./extract_broadcom_hammerhead.sh.
Now it's time for building.
. build/envsetup.sh
lunch - Choose the device you want(hammerhead is 14)
make otapackage
GUIDE 2
Ok let's spice up thing a little bit.
I want to remove and add some stuff to rom.First thing i need to do is to enable Show hidden files and folders in ubuntu.
In your build folde go to folder .repo(this folder is hidden).
In that folder create folder local_manifests.
After that create file roomservice.xml
Here is example of my file:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!--Please do not manually edit this file-->
<manifest>
<remote name="github"
fetch="https://github.com"
/>
<remove-project name="platform/packages/apps/Gallery" />
<remove-project name="platform/packages/apps/Browser" />
<remove-project name="platform/packages/apps/Calendar" />
<remove-project name="platform/packages/apps/Camera2" />
<remove-project name="platform/packages/apps/Gallery2" />
<remove-project name="platform/packages/apps/Music" />
<remove-project name="platform/packages/apps/MusicFX" />
<remove-project name="platform/packages/apps/QuickSearchBox" />
<remove-project name="platform/packages/wallpapers/HoloSpiral" />
<remove-project name="platform/packages/wallpapers/Galaxy4" />
<remove-project name="platform/packages/wallpapers/MagicSmoke" />
<remove-project name="platform/packages/wallpapers/NoiseField" />
<remove-project name="platform/packages/wallpapers/PhaseBeam" />
<remove-project name="platform/packages/apps/VoiceDialer" />
<project path="packages/apps/Camera2" name="CyanogenMod/android_packages_apps_Camera2" remote="github" revision="cm-12.0"/>
<project path="packages/apps/Browser" name="CyanogenMod/android_packages_apps_Browser" remote="github" revision="cm-12.0"/>
<project path="packages/apps/Gallery2" name="CyanogenMod/android_packages_apps_Gallery2" remote="github" revision="cm-12.0"/>
</manifest>
Like this i removed package Camera 2 for example and added Camera2 package from Cyanogenmod github.
Pay attention that i have to add remote github at the start of file and also i have to add revision on end of package.
How to add bootanimation into build.
I downloaded bootanimation.zip file.I create folder in vendor/lge/hammerhead and i named it bootanimation.
I copied zip file there.
Then i go to folder vendor/lge/hammerhead and open file device-partial.mk.
Use right click and open file with gedit.
I add this on end of the file.
Code:
vendor/lge/hammerhead/bootanimation/bootanimation.zip:system/media/bootanimation.zip:lge \
Like this i can have bootanimation directly built in my otapackage.
GUIDE 3HOW TO ADD LAYERS SUPPORT TO ROM
Go to this site
http://forum.xda-developers.com/android/apps-games/official-layers-bitsyko-apps-rro-t3012172?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+xda-developers%2FShsH+%28xda-developers%29
First you need to go on second post on this thread and open all links from android-review.googlesource.com
Cherry pick this in your source.
Go to respective folder in this case go to frameworks/base and paste cherry-pick link here.
Next you need to add cherry picks from https://github.com/bgill55.
Go to respective folder for example for this case Exposing hard coded resources for type 2 overlay access [3/6].
This have to go to packages/apps/Contacts
Next add remote like this:
git remote add layers git://github.com/bgill55/platform_packages_apps_Contacts.git where layers is a name of remote branch.
git fetch layers
git cherry pick number of commit which you can find bellow
Exposing hard coded resources for type 2 overlay access [3/6]
Have to expose hard coded hex coding to changeable resources for theming purposes. For the Layers type 2 overlays
frankie-mr-1 (#1)
commit 888a7be7ec16960cb80fd8371ff694b9dacb9002 1 parent 5402f10
bgill55 bgill55 authored 23 days ago
Repeat these steps for every project.

More info in OP in next few days.
Don't have so much time.

You should put that this is a ROM and not a question in the subject line. Thank you though!
Sent from my Nexus 5 using XDA Free mobile app

Thanks

Great to see you over here, Malcho! I have your rom for Galaxy S i9000 in pretty good memory. Looking forward to this project!

derboedi said:
Great to see you over here, Malcho! I have your rom for Galaxy S i9000 in pretty good memory. Looking forward to this project!
Click to expand...
Click to collapse
Thanks man.
I will do my best.
Sent from my AOSP on HammerHead using XDA Free mobile app

If pure and straight from google[emoji25] why you add cm camera and gallary. Keep it pure [emoji19]
[emoji51] wait for info

7sen said:
If pure and straight from google[emoji25] why you add cm camera and gallary. Keep it pure [emoji19]
[emoji51] wait for info
Click to expand...
Click to collapse
I had to add some things i like
Sent from my AOSP on HammerHead using XDA Free mobile app

very good project, I would like to learn as you go changing the rom, so you'll have my full attention, some tutorial you refer me which programs I need, thanks in advance.

New AOSP rom is out.
First PrimaL is out.
First guide on second post.
Enjoy

thanks a lot, i like the pure aosp rom

@malcho.Welcome, I remember the time of i9000.long time.Good work.

V3 is up.
Added bootanimation and calendar removed.
Use slimroms gapps.
Happy new year
Sent from my AOSP on HammerHead using XDA Free mobile app

malcho said:
New AOSP rom is out.
First PrimaL is out.
First guide on second post.
Enjoy
Click to expand...
Click to collapse
Thanks dude

Is the memory leak fixed in this rom because i want a clean aosp ROM with that bug fixed.

cpvm said:
Is the memory leak fixed in this rom because i want a clean aosp ROM with that bug fixed.
Click to expand...
Click to collapse
I'm running it for few days haven't notice any problems.
Try it and tell us how it goes
Sent from my AOSP on HammerHead using XDA Free mobile app

The memory leak seems to be fixed but power saving location doesn't work otherwise great work, thank you.

cpvm said:
The memory leak seems to be fixed but power saving location doesn't work otherwise great work, thank you.
Click to expand...
Click to collapse
Try to use gps status for playstore to pull gps locations and then see if it works.
Sent from my Nexus 5 using XDA Free mobile app

New version is up!

[ROM][7.30.17]DK11:US - Ground Zero v0.5 // Nougat 7.1.1 * 1.16.617.6 * USonic Boom

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download DK11US(v.05)
For older versions
Download DK11US: Deodex(v0.4)
Download DK11US: Odex(v0.4)
Download DK11US: Deodex(v0.3)
Download DK11US: Odex(v0.3)
Download DK11US: Deodex(v0.2)
Download DK11US: Odex(v0.2)
Download DK11US: Deodex(v0.1)
Download DK11US: Odex(v0.1)
Download DK11US: Odex(v0.0)
ABOUT
- based on US Unlocked 1.16.617.6
- complete stock ROM
- native audio modifications
- Usonic audio boost
This is the 11th installment of the DigitalKarma Rom series. 
CHANGELOG
7.30.17
- v0.5
- modified dtp, tasha, tavil mixer
- modified ACC, CID resource folder(manage ads, turn off report)
- modified build.prop(multi window support)
7.28.17
- v0.4
- modified i2s & tavil mixer, increase sound db for Usonic
- modified MNS file. MMS msg size 2K default
- modified build.prop. adb debug enabled/disabled notification
7.27.17
- v0.3
- fixed updater script
- modified tavil mixer path, using default i2s path again(for test purposes)
7.26.17
- v0.2
- deleted Touchpal language paks except for English, Spanish
- modified i2s mixer path
7.24.17
- v0.1
- added deodexed version
- delete config folder
- modify update-script & build.prop
- removed Demo.apk
7.23.17
- ROM base 1.16.617 US Unlocked RUU
- remain odexed
- rooted with latest Super SU v2.82 SR1
- removed PCTool.iso & DemoFlo
- raw & fresh straight from the kitchen(no modifications and still very bloated)
WHAT'S WORKING:
I don't know.. You tell me?
notes:
this ROM has not been fully tested. It also does not help that I do not yet own an U11 device but this is where you, the user come in. The more feedback, screenshots and logcats to report bugs and other things then the better I can get an idea of where I am going with this project and to make improvements along the way. Right now i am starting over from ground zero. I like the idea of starting all the way from the bottom again and working my way back up it's a re-learning process. I'd like to get a working ROM up and running ASAP so I can hopefully contribute something and add to the growing collection of U11 roms. Until then, witness the growing pains and thanks for trying Ground Zero.
Warning: Install at your own risk. I am not responsible for any damages that may occur to your phone, but as a friendly reminder in case you didn't already know... always remember to backup your data first before you flash
Thanks:
Kisakuku(RUU)
OMJ(ROM Q&A)
chdloc(Audio Q&A)
Galactus(audio testing)
Super R(kitchen)
and many others I'll add later
Tutorial: How to adjust the decibel levels of the U-Sonic headphones
open the rom.zip of your choice that you are planning to use with 7zip. go to the system/etc directory and drag out the mixer_paths_tavil.xml onto your desktop. open the file with notepad++ or any xml editor and make the following changes..
to change the decibel volume of U-sonic with noise cancellation enabled look for the path name: anc-headphones inside tavil..
Code:
<path name="anc-headphones">
<ctl name="COMP1 Switch" value="0" />
<ctl name="COMP2 Switch" value="0" />
<ctl name="ANC Function" value="ON" />
<ctl name="ANC Slot" value="0" />
<ctl name="SLIM RX2 MUX" value="AIF4_PB" />
<ctl name="SLIM RX3 MUX" value="AIF4_PB" />
<ctl name="SLIM_6_RX Channels" value="Two" />
<ctl name="ADC MUX10" value="AMIC" />
<ctl name="AMIC MUX10" value="ADC3" />
<ctl name="ADC MUX12" value="AMIC" />
<ctl name="AMIC MUX12" value="ADC4" />
<ctl name="ANC0 FB MUX" value="ANC_IN_HPHL" />
<ctl name="ANC1 FB MUX" value="ANC_IN_HPHR" />
<ctl name="ADC3 Volume" value="8" />
<ctl name="ADC4 Volume" value="8" />
<ctl name="RX INT1_1 MIX1 INP0" value="RX2" />
<ctl name="RX INT2_1 MIX1 INP0" value="RX3" />
[B] <ctl name="RX1 Digital Volume" value="76" />
<ctl name="RX2 Digital Volume" value="76" />[/B]
<ctl name="ANC OUT HPHL Enable Switch" value="1" />
<ctl name="ANC OUT HPHR Enable Switch" value="1" />
</path>
change the RX1 and RX2 digital volumes to the number of your choice. the registered values are between '0' to '124'. '0' equals to -84 db's and '124 equals to +40 db's. I do not recommend you putting this at 124 or any number over 100 unless you want to risk damaging your ear or your headphones. :highfive:
on my rom i have it set at '84' but HTC set the default values at '74' or '76' depending which software version you are coming from.
to change the decibel volume of U-sonic with noise cancellation disabled look for the path name: headphones inside tavil..
Code:
<path name="headphones">
<ctl name="SLIM RX2 MUX" value="AIF4_PB" />
<ctl name="SLIM RX3 MUX" value="AIF4_PB" />
<ctl name="SLIM_6_RX Channels" value="Two" />
<ctl name="RX INT1_2 MUX" value="RX2" />
<ctl name="RX INT2_2 MUX" value="RX3" />
[B] <ctl name="RX1 Mix Digital Volume" value="76" />
<ctl name="RX2 Mix Digital Volume" value="76" />[/B]
</path>
once again change the RX Mix Digital Volume values to your liking from 0 to 124. i have also set these in my rom to '84' which is 0 db's, to get a louder but more neutral sound without compromising sound quality anything higher and you will get start to get distortion.
after you have made your changes save it then drag and drop your edited tavil.xml file back into the same directory where you extracted it from and overwrite the file inside your rom.zip with 7zip. close and reflash the rom.zip.
I'm sure there are some people in here who have used their U-sonic earphones and find that the default settings may not be set to their liking which is why i am sharing my findings with you. I have heard some say these earbuds are not loud enough and so i have worked on a solution. it's been almost two month since i discovered it. thanks to galactus for confirming and testing that it worked.
on a sidenote, if you want to change external speaker volume although i don't see why you will need to since the U11 speakers sound loud enough already as it is. You'll have to open up Mixer_Paths.xml and make the changes there. Look for speakers path and edit the values there, once again they are 0 to 124. HTC set it at 84 which is optimal level. i am not sure what speaker fluid and speaker db does. haven't had much testing done on that but if you want to test be my guest. Thanks to Galactus for confirming and testing the USonics
XDA:DevDB Information
DigitalKarma's 11, ROM for the HTC U11
Contributors
Digitalkarma
ROM OS Version: 7.x Nougat
Version Information
Status: Testing
Created 2017-07-24
Last Updated 2017-07-24

Great. I've been hoping somebody would do this. Thanks!

jhill110 said:
Great. I've been hoping somebody would do this. Thanks!
Click to expand...
Click to collapse
You're welcome.
Maybe I'll have better luck with testing and feedback from the T-mo, Verizon and AT&T crowd. Worth a shot I suppose.

Digitalkarma said:
You're welcome.
Maybe I'll have better luck with testing and feedback from the T-mo, Verizon and AT&T crowd. Worth a shot I suppose.
Click to expand...
Click to collapse
Is this for sprint only? The linked file says sprint.
I unzipped it and saw all the sprint, boost etc stuff.

jhill110 said:
Is this for sprint only? The linked file says sprint.
I unzipped it and saw all the sprint, boost etc stuff.
Click to expand...
Click to collapse
I put the wrong link there lol. Found out and corrected it 30 minutes later. That's what I get trying to put this out shortly before falling asleep:laugh:
The non-Sprint version is up now. Sorry about that!

Nice! Thanks for the rom!
BTW is the u11 able to float in water?

tbalden said:
Nice! Thanks for the rom!
BTW is the u11 able to float in water?
Click to expand...
Click to collapse
Thank you tbalden, your welcome!
If the U11 is possessed by a witch or a devil, then maybe it will float

v0.1 uploaded. Deodex and Odex versions up.
will probably put out a new test build every night until i can hit the jackpot. would be awesome to know if ROM works, a screenshot of the software or build version in Settings menu would be nice proof. but if it doesn't work then a logcat of the bootup would certainly be of much help to me.

test v0.2 uploaded.
the first wave of sound modifications starting with i2s. not sure if it will have any affect on the 3.5 mm headphones but that is the goal.

v0.3 is up.
fixed update script permissions for possible bootup issues
testing modified tavil mixer sound path for headphones anc and 44.1 but removed i2s modifications for a later build.

:good:v0.4 is up
i can trust Galactus' word that modifying tavil can control the sound of the U-sonic buds. 3.5 mm headphones results still pending. thank you for testing. :good:

Digitalkarma said:
:good:v0.4 is up
i can trust Galactus' word that modifying tavil can control the sound of the U-sonic buds. 3.5 mm headphones results still pending. thank you for testing. :good:
Click to expand...
Click to collapse
I wish I had an extra U11 just to test for you, but life hit me hard late, and too busy to do a lot of testing.
Then again...I would just mail you the extra U11 and call it a day! ?

AarSyl said:
I wish I had an extra U11 just to test for you, but life hit me hard late, and too busy to do a lot of testing.
Then again...I would just mail you the extra U11 and call it a day!
Click to expand...
Click to collapse
hey man no rush bud. i think i fixed the bootup issue on the Sprint version. it's there whenever time allows for you to try it. life happens, and that takes higher priority over a phone. appreciate the response :good:

v0.5 up

Digitalkarma said:
v0.5 up
Click to expand...
Click to collapse
So....I finally tried to do a logcat, and it failed. Adb didn't even recognize the device. The orange light doesn't come on to show that the phone is charging. Most importantly, my phone doesn't prompt me for the pass code to decrypt it and proceed to boot...instead, it reboots itself once (after about 5mins), then hangs until kingdom come.
I thought it was kernel related, so I flashed a custom kernel, ad t sill did tell same thing.
The last step would be to download and flash each upload from the most recent to find the last bootable version.

@Digitalkarma , I hope you keep up the good work here. This is perfect for my needs.
Thanks!

Goggles_Pisano said:
@Digitalkarma , I hope you keep up the good work here. This is perfect for my needs.
Thanks!
Click to expand...
Click to collapse
hey @Goggles_Pisano . thanks for giving my rom a go!
i'm just curious since it's so hard to get feedback around here...
does it fully work? and if it does can you screenshot the software rom build version in About Settings? i'd just like to see my name in there with my eyes as proof that my effort wasnt all for nothing. thanks again:good:

Digitalkarma said:
hey @Goggles_Pisano . thanks for giving my rom a go!
i'm just curious since it's so hard to get feedback around here...
does it fully work? and if it does can you screenshot the software rom build version in About Settings? i'd just like to see my name in there with my eyes as proof that my effort wasnt all for nothing. thanks again:good:
Click to expand...
Click to collapse
Works great. Thing I like about flashable zips is I can lighten them up and add some of my own stuff (custom Boot ani's and sound etc) as I like.
I come from several Samsung devices so there's a learning curve with this stuff for me... Like, I don't know how to change the initial splash screen (HTC powered by Android) or the shut down image. I have some cool one's I like.
BTW, You have any experience with services jar? An extended Power menu would be nice.
Thx
EDIT: This is my daily driver now.

Goggles_Pisano said:
Works great. Thing I like about flashable zips is I can lighten them up and add some of my own stuff (custom Boot ani's and sound etc) as I like.
I come from several Samsung devices so there's a learning curve with this stuff for me... Like, I don't know how to change the initial splash screen (HTC powered by Android) or the shut down image. I have some cool one's I like.
BTW, You have any experience with services jar? An extended Power menu would be nice.
Thx
EDIT: This is my daily driver now.
Click to expand...
Click to collapse
that is so effin awesome, so it works after all! after all this time i was wondering if it was booting or not. now that i know it works i can start adding some features that's the only reason why i've held back on doing anything.
to change the splash screen or mess with the shutdown animation it's all in the customize/resources folder in the zip.
and i have messed with services.jar back in the day to get CRT animations and a few other things, but if you want APM menu i believe you will need to edit framework-res, framework.jar and android.policy.jar. it's been awhile since i messed with that stuff back in the HTC M7 and EVO days. i can attempt to incoporate that n a future update, it should be standard for custom roms anyway.
thank you for the feedback :good:

Digitalkarma said:
that is so effin awesome, so it works after all! after all this time i was wondering if it was booting or not. now that i know it works i can start adding some features that's the only reason why i've held back on doing anything.
to change the splash screen or mess with the shutdown animation it's all in the customize/resources folder in the zip.
and i have messed with services.jar back in the day to get CRT animations and a few other things, but if you want APM menu i believe you will need to edit framework-res, framework.jar and android.policy.jar. it's been awhile since i messed with that stuff back in the HTC M7 and EVO days. i can attempt to incoporate that n a future update, it should be standard for custom roms anyway.
thank you for the feedback :good:
Click to expand...
Click to collapse
Hey, that sounds awsome. Sorry I haven't left any comments but this rom is working perfectly. I too would like to see this endeavor continue.
I've tried a couple of different roms but I keep coming back to this 1.16.617.6 based stock. I'm a bit spoiled from my N4 days with all the fantastic work done by @tx_dbs_tx and others for that last of the GREAT samsung phones.
Keep up the good work and I'll hang around if there's anything I can help you with.
J. A. (JA)

Better Mobile App

welcome