yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] jschill31:
I wonder if it has something to do with DRM? I remember some time ago having something like this come up on the EVO threads. There was a mod floating around that fixed DRM on HTC devices. I will do some digging but it may not have anything to do with this issue.
[HTC Droid DNA] phabulous:
Love your work Jamie, thanks for bringing us such wonderful ROM. Jschill too thanks for the V6.6 build. Mine is working great.

Any chance we are going to see V7.0
[HTC Droid DNA] jschill31:
Hello,

Actually Jamie did the port, I just dusted off my build machine. I see they did merge so I will clobber tonight and build. Looking at the change notes if you use Halo better cast your vote on their G+:

I will drop a link hopefully in the morning if everything goes OK;)

Cheers

Whats On New Base?

NO HALO! WHY ?? THAN GO HERE : https://plus.google.com/+CromOrgSeries/p...itmMfjaztB

BATTERY SAVER MODE

THEME ENGINE

PEEK

NOTIFICATION REMINDER

SHAKE EVENTS

INIT.D TWEAKS

ON-THE-GO MODE

CUSTOM TILE

APP SIDEBAR AND APP CIRCLE SIDEBAR

LOCKSCREEN NOTIFICATIONS

ACTIVE DISPLAY

OMNISWITCH

GESTURE ANYWHERE

DRIVING MODE

RECENTS OPTIONS

AND MANY MANY MORE...
[HTC Droid DNA] mywebslave:
Thanks for helping keep us up to date with the builds. I tried out Liquid Smooth today and I'm already missing c-rom. Flashing back after I get my phone charged up. Definitely looking forward to 7.0
[HTC Droid DNA] d08speed3:
I flashed Liquid and it seems faster and smoother IMO. All the same features as C-Rom minus the On-The-Go Mode....

HTC DNA

LG Optimus G
[HTC Droid DNA] mywebslave:
It does seem pretty smooth. Just some minor things I'm having issues with. Battery seems to drain pretty quick, yes some say it needs a few days to smooth out. The DSP manager crashes when I try to use it, which I Also cannot switch as I prefer viper4android. Some of the spins on features are different, but I guess it's more of a personal preference. Mainly been trying out a few different ROMs to see about improving the battery life. Seems that lately the battery dies faster and faster. I always try to maintain my battery properly. Maybe it's time for a new phone.
[HTC Droid DNA] d08speed3:
Is 7.0 Android 4.4.3?

HTC DNA

LG Optimus G
[HTC Droid DNA] d08speed3:
Try these settings using Jamie's latest kernel. Don't mind the intelliplug since he uses Simple plug now. If you don't use the Exposed Module use ART instead of Dalvik. I get amazing battery life. 3+ hours of Screen time no matter what CM/AOSP ROM I'm on.

HTC DNA

LG Optimus G
[HTC Droid DNA] jschill31:
OK, not sure why but even after a clobber when I sync and start to build it still shows as 6.6. It is possible that everything is not fully up, will try again later.

Jamie,

Seems my make file has issues, did you make any changes?

make: *** No rule to make target `external/chromium_org/v8/tools/gyp/generate_trig_table.host.linux-arm.mk'. *Stop.

Cheers
[HTC Droid DNA] phabulous:
Thanks Guys for the hard work. I have tried liquid and vanir the 4.4.3 builds but back to C-Rom cuz I miss the features of it, even though I love the new dialer and contacts app of 4.4.3 it's refreshing. Will wait patiently for the new build.
[HTC Droid DNA] jamiethemorris:
I'm guessing everything hasnt been fully uploaded. Look at the git log for that folder and see if anything was changed recently that might have caused it, and if so revert the commit(s), also do the same thing by just looking at the most recent commits on their github.

Edit: it's also possible it could have something to do with some recent cm commits to the device tree... There's only 2 I think that i haven't done yet. They were committed in the past week.
[HTC Droid DNA] jschill31:
I am terrible with git... It is like reading a different language to me. All of the errors reference external/chromium_org, does this have something to do with my build tools? Remember my entire machine took a dump earlier in the week, I guess that it is possible I forgot to load something? I tried to get the BBQ to load but after 3 tries moved back to Ubuntu. It just would not boot, I think there is something wrong with their recent live disk and installer. If you figure something out please let me know.

Edit:

Does it have something to do with this: https://android.googlesource.com/platform/external/chromium_org/v8/ .

Cheers
[HTC Droid DNA] :
You guys should contact/pm [MENTION=4336480]aways[/MENTION]
[HTC Droid DNA] jamiethemorris:
I sent him a pm yesterday asking if we could get official support. This was before jschill had this build error of course lol.

I take it since you responded to the thread this is a device specific build error?
[HTC Droid DNA] jamiethemorris:
It could be your build tools actually. I forgot you redid your install. I can't tell you off the top of my head what it might be missing, but I seem to remember with recent versions of Ubuntu you had the install procedure for the android tools was a little bit different? Look at one of the guides for your version of Ubuntu and make sure you got everything, have the correct version of java, etc
[HTC Droid DNA] jamiethemorris:
I got the same error...
[HTC Droid DNA] jschill31:
Yep I was thinking you would. I am seeing pastebin scattered with pastes about these chromium errors for multiple devices as well as roms. Seems to be a lot of people are having different references to errors dealing with: https://android.googlesource.com/platform/external/chromium_org/v8/+/c8ac6d . I did read that someone kept reverting line for line until he got past them. They all seem to be directly in the beginning. Could it be possible that we need to compile using GCC 4.X tool chain?

Update:

I am finding out just how little I know... Need to do something different for a while. If you figure something out please let me know. BTW did you add what you referenced before to your device tree? Looks like people started to have issues building around June 7th, I suck at git so bad.

Cheers
[HTC Droid DNA] jamiethemorris:
GCC 4.7 or 4.6 maybe, I had problems with other ROMs that were sometimes solved by doing that. AFAIK Google uses 4.6.
[HTC Droid DNA] phabulous:
Any success guys? Thanks by the way for all the effort and time spent in making us this beautiful rom.
[HTC Droid DNA] jamiethemorris:
I haven't tried again yet, hopefully the problem will resolve itself... If I have time I'll try again today.
[HTC Droid DNA] jschill31:
FYI, I tried again yesterday afternoon...no go. I have deleted all of my source files and am starting over with a fresh CM pull. If that builds with no errors I will pull the Crom files and try again. There is more going on than just the Crom stuff. Nothing I tried to build yesterday worked, all had various versions of the same errors.

Edit:

Still no luck building...I am not sure what to think at this point. It seems that my other repos have been updated and build again but Crom just seems stuck? In fact if you look here https://github.com/X-ROM it looks to me like nothing has been updated in 22 days except for their OTA app. Jamie, I am confused at this point. I do not see where anything has been forked and all of their supported devices have 7.0 builds. Where is this coming from if the repo reflects the 6.5 sources? I am an old man and may be missing the obvious...any help?

Cheers
[HTC Droid DNA] jschill31:
Hello,

Well finally one step closer to 7...found a recent repo. Hopefully there will not be many errors. May need your help Jamie if this doesn't build.

Cheers

Update, already failed. The repo I used is also building TWRP at the same time and something in one of the make files conflicts with the recovery gui. Not exactly sure where to look so I can remove the screen reference, this should get past this first error. Anyone know where to go or how to skip the recovery warning? Here is the error:

============================================

bootable/recovery/gui/Android.mk:87: ***********************************************************************************************

bootable/recovery/gui/Android.mk:88: * YOU SHOULD BE SLAPPED FOR NOT SPECIFYING THE SCREEN DIMENSION FOR BOOTANIMATION AND RECOVERY*

bootable/recovery/gui/Android.mk:89: ***********************************************************************************************

bootable/recovery/gui/Android.mk:90: *** stop. Stop.

It is late and this one should be easy but I am tired of flipping through folders...and my command line is poor. Looks like it will be 4.4.4 already if I can get it to compile but I suck with errors...any help?
[HTC Droid DNA] jamiethemorris:
What do you mean by you found a recent repo? Are you saying you're using a different chromium repo?
[HTC Droid DNA] jschill31:
I think it is actually the master branch? Not sure but it is being updated every few hours: https://github.com/C-RoM-KK Maybe this is already where you are working from but it is not the source I used for the 6.6, that one was: https://github.com/X-ROM but it has not been updated in 24 days. I think it will build fine if I can rm all references to building TWRP or add whatever device specific items needed to build TWRP. I have tried to build TWRP in the past but never really was successful. Most of this is way over my head, probably better for you to look into it. Basically all I have done is scrapped my entire crom folder, switched to the C-RoM-KK repo, synced and then added back in the dlx device with kernel common stuff. I removed the entire recovery folder and it will start building without any of the chromium errors but will stop once it hits references to recovery.

Hopefully you have time to peek at it?

Cheers
[HTC Droid DNA] pyroguysf:
I haven't built much or recently, so it could be something else entirely or you might've already checked, but does the device makefile define the screen dimensions? I'm not great with the lingo either, but for an example it's lines 23-25 in the M7 version here - android_device_htc_m7-common/m7-common.mk

If not, no idea, ignore me - good luck, haha.
[HTC Droid DNA] jamiethemorris:
Oh, I see. Yeah I was using the old one as well. Hopefully I'll have time today to take a look. Things have been very busy lately.

Twrp specific device tree stuff isn't too hard. here's some commits you might want to take a look at:

https://github.com/jamiethemorris/du_device_htc_dlx/commit/ffc140133fe36257b2d5ea79ec806170c4aae156 this one shows the necessary changes to boardconfig.mk and full_dlx.mk, and the addition of recovery/init.twrp.rc.

You also need the twrp.fstab in this commit https://github.com/jamiethemorris/du_device_htc_dlx/commit/6360b6a6a499ff7d33ad6594719737d9a9bbea13

That should allow the device tree to be fully twrp compatible. If I have time today I'll update the device tree with these changes.
[HTC Droid DNA] jschill31:
You rock!

---------- Post added at 02:08 PM ---------- Previous post was at 02:06 PM ----------

I am sure that this is the case, just didn't know exactly where to look for it.

Thanks

OK so by adding the TWRP items to the device tree it does get past the first error and builds for a good amount of time before failing again. Still issues with the screen res, I think recovery is working but now the boot animation is holding things up. Is there a way to query all "1080x1920" statements? Then I could address them all at one time instead of this BS... I am pretty sure this will build and boot.

make: *** No rule to make target `vendor/crom/prebuilt/common/media/xxhdpi/BOOTANIMATION-1080x1920.zip'
[HTC Droid DNA] jschill31:
Hello,

Well this is starting to piss me off... I fix one error then build for a while before another error. I think I have had at least 4 now but it is soooo close I can taste it. This last one may be the stopping point though:

make: *** [/home/jim/crom/out/target/common/obj/APPS/TeleService_intermediates/classes-full-debug.jar] Error 41

I have tried with my alternate jar tool and that did not help.

Any ideas?
[HTC Droid DNA] d08speed3:
Patiently waiting for v7.1 :)

HTC DNA

LG Optimus G
[HTC Droid DNA] jamiethemorris:
That's not the error. The actual error is somewhere before that but obviously you can't see it it the terminal window. When you build, do it like this (for example): brunch dlx 2&>1 | tee crom_build.txt then when it fails, look at that file and search for error starting from the end of the file and going backwards.

Sorry I haven't had any time to put into this, i promise i haven't abandoned android development, life is pretty hectic right now. Today I have to change a head gasket, which I've never done before, and I don't have anyone to help. :(
[HTC Droid DNA] jschill31:
Hello,

Head gasket no fun by yourself...good luck. So I assume these are the actual errors but I still have no idea what to do with them?

packages/services/Telephony/src/com/android/phone/CallFeaturesSetting.java:641: cannot find symbol

symbol : variable DIALKEY_PADDING

location: class android.provider.Settings.System

Settings.System.DIALKEY_PADDING, val);

^

packages/services/Telephony/src/com/android/phone/CallFeaturesSetting.java:2041: cannot find symbol

symbol : variable DIALKEY_PADDING

location: class android.provider.Settings.System

Settings.System.DIALKEY_PADDING, 0);

BTW, it did go to 7.1. All of you out there who have any java knowledge chip in on these. I have spent more than 12 hours on this build and still have nothing but a hot mess.

Cheers
[HTC Droid DNA] jamiethemorris:
Yeah those are the actual errors. Look at this commit https://github.com/C-RoM-KK/android...mmit/52fb21b81b15917f426b211a5c8505e31c994735

That's where the dialkey padding thing was added.

See how it says 3/3? I've had this happen a few times with multi-part commits like this where the other parts of it haven't been committed yet. It happens a lot in between ROM versions. I don't have a real efficient technique for doing this, but here's a couple things you could do:

-It's forked from slimrom, so look at slimrom's github and see if you can find the other 2 parts of the commit. They should be roughly around the same time. If crom is missing one of them, cherry-pick the commit.

-this is probably the easier way: just revert that commit and see if it builds. It doesn't look like a crucial feature to me so it shouldn't be a big deal not to have that change.

Edit: here's the problem. Frameworks_base is missing this commit: https://github.com/SlimRoms/frameworks_base/commit/8618304dca5947b12864ae6a09ebe8b91c90cb41

So once you make that change it should get past the error.
[HTC Droid DNA] orangechoochoo:
Changing a head gasket is a big task, good luck! I remember when I used to work on my cars I would always have "leftover" screws and bolts lol
[HTC Droid DNA] jamiethemorris:
Me too. Every time lol
[HTC Droid DNA] phabulous:
Thanks Jamie... You show us far too much love. Hope this will give Jc some breakthrough.

All the best Man.
[HTC Droid DNA] jschill31:
How did you come out on the head gasket? Hope all is well, scraping the old one off is always fun. So you were right on target on that last error, wish I knew how to search better. I added those lines and it did indeed get past but only to stop yet again on something else. I had to take a break last night, my eyes were bugging. I do not remember the new error but it was a combo of 5 individual ones which I assume will be similiar to the last one. Maybe you can teach an old dog how to search commits? I expect it will be another Slim change. I find it kinda funny because I used to build Slim as my primary for all my devices. I have never had this hard of a time building a rom from source...even back in the old Nook days. When I get home from work I will update this post with the new error to see if you have further advice. This build is turning into "Frankinrom", seems to have CM11, CRoM, AOSP and Slim...not even sure if I want to be the first to flash.:cyclops:

Cheers
[HTC Droid DNA] jamiethemorris:
Haven't gotten far with the head gasket :(

Searching commits is pretty straightforward, just see what file throws you the error, and then check the github commits to see if that was sonething that was changed recently.
[HTC Droid DNA] jschill31:
Hello,

Well I just didn't find much last night and had to walk away. The errors that it is stuck on now all deal with the new Theme Engine but looks like Crom & Slim went back to the Tmobile one. I rather like the new one since I like to change icons and it was working in 6.6. If you have a solution to keep it here are the errors:

target Java: ThemeChooser (/home/jim/crom/out/target/common/obj/APPS/ThemeChooser_intermediates/classes)

packages/apps/ThemeChooser/src/org/cyanogenmod/theme/util/IconPreviewHelper.java:19: cannot find symbol

symbol : class ComposedIconInfo

location: package android.app

import android.app.ComposedIconInfo;

^

packages/apps/ThemeChooser/src/org/cyanogenmod/theme/util/IconPreviewHelper.java:160: cannot find symbol

symbol : class ComposedIconInfo

location: class org.cyanogenmod.theme.util.IconPreviewHelper

ComposedIconInfo iconInfo = mIconPackHelper.getComposedIconInfo();

^

packages/apps/ThemeChooser/src/org/cyanogenmod/theme/util/IconPreviewHelper.java:160: cannot find symbol

symbol : method getComposedIconInfo()

location: class android.app.IconPackHelper

ComposedIconInfo iconInfo = mIconPackHelper.getComposedIconInfo();

^

packages/apps/ThemeChooser/src/org/cyanogenmod/theme/util/IconPreviewHelper.java:163: cannot find symbol

symbol : variable IconCustomizer

location: class android.app.IconPackHelper

return IconPackHelper.IconCustomizer.getComposedIconDrawable(baseIcon, res, iconInfo);

^

packages/apps/ThemeChooser/src/org/cyanogenmod/theme/util/IconPreviewHelper.java:169: cannot find symbol

symbol : class ComposedIconInfo

location: class org.cyanogenmod.theme.util.IconPreviewHelper

ComposedIconInfo iconInfo = mIconPackHelper.getComposedIconInfo();

^

packages/apps/ThemeChooser/src/org/cyanogenmod/theme/util/IconPreviewHelper.java:169: cannot find symbol

symbol : method getComposedIconInfo()

location: class android.app.IconPackHelper

ComposedIconInfo iconInfo = mIconPackHelper.getComposedIconInfo();

^

packages/apps/ThemeChooser/src/org/cyanogenmod/theme/util/IconPreviewHelper.java:185: getDrawableForDensity(int,int) in android.content.res.Resources cannot be applied to (int,int,boolean)

d = resources.getDrawableForDensity(iconId, mIconDpi, false);

^

Note: packages/apps/ThemeChooser/src/com/viewpagerindicator/CirclePageIndicator.java uses or overrides a deprecated API.

Note: Recompile with -Xlint:deprecation for details.

7 errors

make: *** [/home/jim/crom/out/target/common/obj/APPS/ThemeChooser_intermediates/classes-full-debug.jar] Error 41

make: *** Waiting for unfinished jobs....
[HTC Droid DNA] jamiethemorris:
Okay it sounds like sort of the same thing as before most likely. There's probably another multi-part commit that isn't complete and that's why it doesn't know what to do with those symbols. I'll see if I can find anything tomorrow.
[HTC Droid DNA] jschill31:
Jaime,

I have spent several hours trying to get 7+ to build and I am just hitting a brick wall after the recent changes... I have not found any issues with the 6.6 build as of yet. Have you ever done what I call a "dirty port" meaning using either CM11 (base) or the working CRoM 6.6 and swapped out files from the M7 7.1 build (port)? Obviously this may have some graphical issues but aren't we using the same kernel anyway? Maybe there is a closer match to our DNA that CRoM is building as an official device that would work better for this type of port. I know you were going to look at it when you had time but did you get anywhere? I am at the point of throwing in the towel and trying this, any advice?

Cheers
[HTC Droid DNA] jamiethemorris:
I don't know how to do that, but it's more than just swapping out the kernel. There would probably be a lot of stuff broken. It's not really worth the effort. I just did a repo sync of the new repository, but I forgot to add my device specific stuff so I added my local manifest, and it decided to give me a repository not found error for platform/external/chromium_org/third_party/mesa/src. Wtf. :(
[HTC Droid DNA] jschill31:
Jamie,

The only way I have been able to get past the chromium errors is to use a combo of Slim & CM repos. Try Slim for kernel and CM for device. You will get more device errors down the road, I have moved past 4 so far but still no output. On device ports there are a lot of files you move over, usually most options if not all work as long as you pick like devices and base. My thoughts are to start with CM11 and migrate in CRoM. No worries if you have never ported Luke this...I prefer to compile but tired of the errors.

Cheers
[HTC Droid DNA] jamiethemorris:
I don't understand why the device files have anything to do with the chromium repo, if I don't have my local manifest it syncs fine. Weird. I'm just going to git clone that stuff manually I guess.
[HTC Droid DNA] jschill31:
Not sure either, if you get it to build I know there will be several happy users.[emoji14]
[HTC Droid DNA] jamiethemorris:
It didn't like the way I had the local manifest set up, I figured it out. Here is the new one, you can see what I changed it to, I just commented the old ones out. Both TheMuppets and CyanogenMod repo already had remote names listed in the default manifest, so I used those.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="cm-github"
fetch=".."
review="review.cyanogenmod.org" />

<remote name="jamiethemorris"
fetch="https://github.com/jamiethemorris" />

<project path="device/htc/dlx" name="crom_device_htc-dlx" remote="jamiethemorris" revision="kitkat" />
<project path="vendor/htc" name="proprietary_vendor_htc" remote="tm" revision="cm-11.0" />
<!-- <project path="vendor/htc" name="TheMuppets/proprietary_vendor_htc" revision="cm-11.0" /> -->
<project path="device/htc/msm8960-common" name="android_device_htc_msm8960-common" remote="cm" revision="cm-11.0"/>
<!-- <project path="device/htc/msm8960-common" name="CyanogenMod/android_device_htc_msm8960-common" revision="cm-11.0"/> -->
<project path="kernel/htc/m7" name="android_kernel_htc_m7" remote="cm" revision="cm-11.0"/>
<!-- <project path="kernel/htc/m7" name="CyanogenMod/android_kernel_htc_m7" revision="cm-11.0"/> -->
</manifest>
[HTC Droid DNA] jamiethemorris:
Dammit. Now it wants me to change my java version and my make version. I had to change java to 1.7 for another ROM a while back, now I have to change it back..
[HTC Droid DNA] jschill31:
Yea, forgot about that. Some if that looks similar to my manual edits. It would be outstanding if your repo edits work. I will clobber and try myself later. Do you remember the command that destroys any manual edits and resets?
[HTC Droid DNA] jamiethemorris:
I don't know how to do it for the entire repo, but for the individual git repos you can cd to them and just do

git reset --hard

Also, I was lazy and didn't feel like changing my java version, according to the android website 1.7 is recommended anyway. So I opened build/core/main.mk and changed line 181 from this

$(error stop)

to this

$(warning whatever)

I suppose I could have just deleted that whole section too, I just wanted to leave it to give myself a reminder that technically it's wrong for this ROM.

EDIT: nevermind. Ran into a java error right away.
[HTC Droid DNA] jamiethemorris:
Okay, I'm back at java 1.6 and make 3.8.1. It's building now. I must say, one really annoying thing about arch is that python 3 is the default python and make 4.0 is the default make. Every time I update it I usually have to change them both back otherwise nothing will build.

Progress:

Ran into an error about the resolution, so I fixed that. I don't know why that wasn't in there, I must have accidentally deleted it or something.