yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Incredible 2] chillybean:
Made an update im actually getting tired from building so i put up my manifest and repo to make building possible
[Verizon Droid Incredible 2] bsmitty83:
So to build cm10 in the manifest.XML under device/htc/vivow project path , what do i change the revision "cm10.1" to ? The obvious cm10 doesn't work

Sent from my Galaxy Nexus
[Verizon Droid Incredible 2] chillybean:
Manifest is for cm10.1 only right now I'll get a cm10 repo going in the morning for ya
[Verizon Droid Incredible 2] bsmitty83:
You da man Stan :D

Sent from my Galaxy Nexus
[Verizon Droid Incredible 2] chillybean:
we have a conundrum..i already spoke with bry about it...we have 2 device trees...3.0 and 2.6 (cm10.1 vs cm10)

now we can try and work the 3.0 device tree and kernel to cm10 and patch what ever into the 3.0 kernel...OOOOR we can use the 2.6 device tree/kernel and patch it to 3.0..or use the 3.0 kernel and patch just the device tree and add whatever is missing...u get what im sayin i know its kind of confusing but we have multiple sources im just not sure which to begin with or which would be remotely easier
[Verizon Droid Incredible 2] bsmitty83:
See here :p

http://xdaforums.com/showthread.php?p=43736267

Sent from my Galaxy Nexus
[Verizon Droid Incredible 2] chillybean:
When I can I'm going to try for ion support ...much needed
[Verizon Droid Incredible 2] bsmitty83:
So i tried to build a ROM from the gnex last night and kept getting stuck at

*** cannot locate config makefile for product "cm_vivow" . stop.

**don't have a product spec for : 'cm-vivow'

** do you have the right repo manifest?

I get what its saying but i used your manifest , repo synced , saw all the files get copied ,

So what do i need to do to get build/core/product_config.mk to find the makefile for cm-vivow ?

Or what do i have to do to fix the error ? Lol BTW reposyncing for ROMs suck , it takes FOREVER :p

Sent from my Galaxy Nexus
[Verizon Droid Incredible 2] chillybean:
If your buildings carbon ROM u need to edit the vendor files go to the ROM vendor folder add vivow to the vendor setup.sh or something(not home to see then name) the make a mk file in products use an other mk file as a reference...then add it to the android mk file in the same folder
[Verizon Droid Incredible 2] chillybean:
Yea it takes for ever building does too
[Verizon Droid Incredible 2] bsmitty83:
That's pretty much how i found to do it i just wasent sure , thanks man , im hoping to get a new laptop soon cant wait to start kicking out ROMs ....

Sent from my Galaxy Nexus
[Verizon Droid Incredible 2] bsmitty83:
Compiling my first ROM right now (cm10) thanks chilly , couldn't have done it without you :beer: don't know how it'll turn out but its still building

Oh i think i changed the dependencies from ev.mk to cm.mk for it to go if it works ill commit that

Sent from my Galaxy Nexus
[Verizon Droid Incredible 2] bsmitty83:
So chilly , I'm stuck man , every ROM i try to build gives me errors .

Alot of errors involving the legacy folders redefining the regular folders.

Do you have to repo sync first , then add local manifest ? Cuz I've been repo init then add local manifest THEN repo sync . i wouldnt think it matters but i just don't know what in doing wrong . i can get a build going , but it always fails or wont make at all

Any insight would be appreciated

Sent from my Galaxy Nexus
[Verizon Droid Incredible 2] chillybean:
lol your not doing anything wrong..building roms are a pain in the ass for this phone due to display drivers and memory allocators...what is the error you are gettin ill help ya threw it...for display drivers its odd but for most cm roms evervolv display-legacy and media repos should work fine (not media-legacy) u may get a hwc_blit error that can be easily fixed
[Verizon Droid Incredible 2] bsmitty83:
I guess my biggest question is how to exclude the legacy folders or the regular folders so it will build , most of the other errors are probably from me building wrong lol trying things out

Sent from my Galaxy Nexus
[Verizon Droid Incredible 2] chillybean:
in the qcom folder just remove the media-legacy folder....u may have repeat entries for qcom gps so u may hafta del a qcom/gps (leave gps-legacy) and msm7k/librpc
[Verizon Droid Incredible 2] MoonMaster345:
since its in context, this thing is eating me alive..

CC arch/arm/mach-msm/board-vivow_ct.o
arch/arm/mach-msm/board-vivow_ct.c:174:1: error: expected declaration specifiers or ‘...’ before string constant
static void config_gpio_table (uint32_t *table, int len)
^
arch/arm/mach-msm/board-vivow_ct.c:174:1: error: expected declaration specifiers or ‘...’ before numeric constant
arch/arm/mach-msm/board-vivow_ct.c:1419:3: warning: initialization from incompatible pointer type [enabled by default]
.camera_gpio_on = config_camera_on_gpios,
^
arch/arm/mach-msm/board-vivow_ct.c:1419:3: warning: (near initialization for ‘camera_device_data.camera_gpio_on’) [enabled by default]
make[1]: *** [arch/arm/mach-msm/board-vivow_ct.o] Error 1
make: *** [arch/arm/mach-msm] Error 2

he're what it shows in the board-vivow_ct.c file from lines 167 to 185

#define PCOM_GPIO_CFG(gpio, func, dir, pull, drvstr) \
((((gpio) & 0x3FF) << 4) | \
((func) & 0xf) | \
(((dir) & 0x1) << 14) | \
(((pull) & 0x3) << 15) | \
(((drvstr) & 0xF) << 17))

this is line 174--->static void config_gpio_table (uint32_t *table, int len)
{
int n, rc;
for (n = 0; n < len; n++) {
rc = gpio_tlmm_config(table[n], GPIO_CFG_ENABLE);
if (rc) {
pr_err("[CAM] %s: gpio_tlmm_config(%#x)=%d\n",
__func__, table[n], rc);
break;
}
}
}

well i dont know where its expecting the damn specifiers...

it gives me the same using the linaro 4.6 and the 4.8 toolchain, this one i copied from the 4.8 one

Edit: interestingly enough, i added a ( before static and it changed into:
[Verizon Droid Incredible 2] chillybean:
what are you trying to build
[Verizon Droid Incredible 2] MoonMaster345:
A kernel actually, but i just need to know why the hell its telling me these things, i add random specifiers and get nowhere
[Verizon Droid Incredible 2] chillybean:
ooooo im still gettin use to kernel deving...thats the b-teams calling :good:
[Verizon Droid Incredible 2] MoonMaster345:
b-team has been helping, but bry is out for now, we're gonna work once he gets back, and bsmitty has helped aswell
[Verizon Droid Incredible 2] bsmitty83:
I just got switched from nightshift to mornings at my shop so I'm kinda useless right now I'm a zombie . but i would look at the menuconfig under gpio and if theres an option resembling the error , UN check it and see if it builds it will help narrow down errors

Still working on vivow stuff but took a break to build a 4.3 ROM for my neglected nexus lol stoked .

For the record , i don't know c very well , but i like knowledge so i pick up stuff fast , but 90% of the errors i get building kernels involved menuconfig changes

Sorry i cant help more my brain is mush right now and i shot a staple into my thumb at work today , with a pneumatic staple gun , so I'm trying not to type :thumbdown:

Sent from my Galaxy Nexus
[Verizon Droid Incredible 2] MoonMaster345:
oh great i'll check it out thanks!
[Verizon Droid Incredible 2] FordNate:
Bs I'm calling bs on you being a zombie. All this techno talk I've been scoping by y'all has made my hair want to grow back so I can pull it out. Work hard our reward shall come tomorrow (not HTC tomorrow)
[Verizon Droid Incredible 2] brymaster5000:
Chances are - the file with the errors is being called upon from another file (perhaps a "___.h" file). The parameters in the () part of the function need to match.

Just hold on for a few more days, and I will join in on the chaos!:eek::good:

PS - What toolchain are you using? You could try to switch to see if it handles code differently.
[Verizon Droid Incredible 2] weldawadyathink:
I am just wondering why nobody has pushed these changes to Gerrit? Chilly's cm10.2 is very stable and everything is working I believe. Why not put them on Gerrit and get official cyanogenmod jellybean?
[Verizon Droid Incredible 2] polymath257:
is there a manifest for any of the cm-11 builds?
[Verizon Droid Incredible 2] chillybean:
Yup cb44 branch github.com/chillybean

Should build unless there was an upstream change

Tip... the first error will be a GPS duplicate ...just delete the file in case
[Verizon Droid Incredible 2] polymath257:
I finally got around to trying to build this. It seems that there are several problems with multiple versions of the file gralloc_priv.h. The upshot is that a number of flags are not in scope when used. I have not yet been able to get a successful build. Still working, though.
[Verizon Droid Incredible 2] chillybean:
post the error
[Verizon Droid Incredible 2] polymath257:
I'm in the middle of another build right now, so I will get back to you with any more that I find, but here's what i have so far.

Two of the offending errors had GRALLOC_USAGE_PRIVATE_INTERNAL_ONLY out

of scope in frameworks/native/libs/gui/Surface.cpp and in frameworks/native/services/surfaceflinger/Layer.cpp.

Another had GRALLOC_USAGE_PRIVATE_SECURE_DISPLAY out of scope in frameworks/native/services/surfaceflinger/Layer.cpp.

Yet another had GRALLOC_USAGE_PRIVATE_CP_BUFFER out of scope in hardware/qcom/display-legacy/libgralloc/alloc_controller.cpp.

I was able to trace all of these back to different versions of the file gralloc_priv.h .
[Verizon Droid Incredible 2] chillybean:
What are you building. and just copy and paste your output error don't rewrite it
[Verizon Droid Incredible 2] polymath257:
I am attempting to build cm11 from your cb44 branch mentioned above. Here is the error that first stops the build:

target thumb C++: libgui <= frameworks/native/libs/gui/Surface.cpp

frameworks/native/libs/gui/Surface.cpp: In member function 'virtual android::status_t android::Surface::lock(ANativeWindow_Buffer*, ARect*)':

frameworks/native/libs/gui/Surface.cpp:786:29: error: 'GRALLOC_USAGE_PRIVATE_INTERNAL_ONLY' was not declared in this scope

make: *** [/home/daniel/android/vivow/out/target/product/vivow/obj/SHARED_LIBRARIES/libgui_intermediates/Surface.o] Error 1
[Verizon Droid Incredible 2] chillybean:
remove or comment out this line in the file boardconfigcommon.mk in msm7x30 common folder i forgot to revert the qbsp commit

# QCOM BSP Enabled
TARGET_USES_QCOM_BSP := true
[Verizon Droid Incredible 2] polymath257:
That seems to have worked! The ROM compiled.

Now it seems I have to find a cm11 compatible recovery. A previously installed TWRP 2.6.3.0 did not work, nor did the recovery

from the build.

Any pointers?
[Verizon Droid Incredible 2] bsmitty83:
The newest clockworkmod should work .
[Verizon Droid Incredible 2] polymath257:
The latest from CWM for vivow is 5.0.2.0, which failed to install the cm11 zip I just compiled. Every recovery I have tried,

including the one from the build, reports an error (Status 7 for CWM). Is there a more recent, unofficial, recovery for this

phone?

Edit: the CWM from the build is version 6.0.4.6 and it failed to install the build.
[Verizon Droid Incredible 2] bsmitty83:
That is strange . the version included should work . I guess you could try grabbing twrp source from github and replace your /bootable/recovery with twrp and make recovery image . maybe chilly can shed some light cuz I thought cwm 6.0.4.6 should work
[Verizon Droid Incredible 2] polymath257:
I've been playing around with the updater-script from the build by putting in progress indicators. The get.prop is not the problem. it

seems that anything involving extraction is, however. I'm not sure where to go from here: build again?
[Verizon Droid Incredible 2] bsmitty83:
Before u do , what does the recovery log say ? That might help you locate the reason for the status 7
[Verizon Droid Incredible 2] polymath257:
Here are the last few lines of the log file. If you want the whole thing, I can provide.

minzip: Extracted file "/system/xbin/su"

minzip: Extracted file "/system/xbin/vim"

ApplyParsedPerms: removexattr of /system/addon.d/50-cm.sh to 0 failed: Operation not supported on transport endpoint

script aborted: set_metadata_recursive: some changes failed

set_metadata_recursive: some changes failed

E:Error in /storage/sdcard0/cm-11-20140114-UNOFFICIAL-vivow.zip

(Status 7)

Installation aborted.

I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.4/mmc_host/mmc2

Edit: it looks like this is a common error for cm11. I found one commit that might help, but it seems a bit of a strong-arm tactic:

https://github.com/legaCyMod/android_build/commit/f0df153b707e9403a3e695f659fbfcd6417cba15
[Verizon Droid Incredible 2] chillybean:
Go to Evervolv gerrit under their android_build they should have a commit fixing said problem. Also I think 4ext just updated to support metadata not sure I could be lieing ..also try using my android build repo or look within it you'll find the commit to fix that
[Verizon Droid Incredible 2] polymath257:
Update: With the successful build, I was able to get a successful install using the update-binary from this post:

http://xdaforums.com/showthread.php?t=2532300

and a use of Android Kitchen to replace the binary in the ROM with the new one.

http://xdaforums.com/showthread.php?t=633246

I am attempting a complete re-build using the change from the link:

http://xdaforums.com/showpost.php?p=47692333&postcount=15
[Verizon Droid Incredible 2] polymath257:
I found out what the problem is with the recovery/build. The kernel needs to be built with some flags set so that it can deal with the metadata commands properly. I am not sure what the minimal changes are, but the following work (starting with the manifest from the OP):

in the file kernel/htc/msm7x30-3.0/arch/arm/configs/evervolv_vivow_defconfig, set the following flags:

CONFIG_EXT3_FS_SECURITY=y

CONFIG_EXT4_FS_SECURITY=y

CONFIG_SECURITY=y

CONFIG_SECURITYFS=y

CONFIG_AUDIT=y

I suspect that the first is unnecessary if the second is present. The second and last are necessary. With these changes, the build completes and installs with the recovery.img in the $OUT directory.
[Verizon Droid Incredible 2] chillybean:
The first is necessary for people who prefer ext3 file system...I've tried that solution but it didn't work. Did it flash four you after the build
[Verizon Droid Incredible 2] polymath257:
Yes, with the recovery made by the build, it flashed and booted. Runs nicely so far.

I know the AUDIT flag is also required. I was just guessing about the other two, but the combination definitely works for me.

Edit: I was just able to boot with ART enabled.
[Verizon Droid Incredible 2] polymath257:
Just an update:

I have been using this CM11 ROM for the last week and am very pleased with it. I do not have an activated phone, though, so while I can test wireless and BT, I cannot test how calls work.

The changes above do give a recovery (install via fastboot) that installs the built ROM.
[Verizon Droid Incredible 2] chillybean:
Up it on d-h.st

..Sure some one will give it a whirl :)
[Verizon Droid Incredible 2] polymath257:
Since I built this from your source, I want to be clear that you get the credit for the work. I only compiled.
[Verizon Droid Incredible 2] polymath257:
Thanks to chilly for the source and all the work for this ROM. I am merely a compiler.

If you need more instructions, just ask.

The recovery needs to be installed via fastboot.

Then put the zip file for the ROM on the sdcard. In recovery, the sdcard is seen as /storage/sdcard0.

Good luck!

Recovery:

http://d-h.st/ExE

ROM:

http://d-h.st/gfX
[Verizon Droid Incredible 2] chillybean:
You should start a thread if you plan on keeping it updated
[Verizon Droid Incredible 2] 121tech:
Hi polymath257,

Previously flashed Chilly's 4.4.2 Beanstalk so wanted to compare a 'stock' CM11 build. Successfully flashed your compiled rom build -- no problem using 4EXT Recovery Touch v1.0.0.6 RC1 (so didn't flash the accompanying recovery)

Working fine using GSM service

No working camera (so same as 4.4.2 Beanstalk, guessing still missing aosp source or kernel support for camera?)

The only issue I found was trying to enable the Brightness control [Settings | Interface | Status Bar : Brightness control checked]

Pulling down and sliding left or right on the status bar has no effect in brightness.

Oh, and where is the Dalvik/ART switch? I don't see a '{ } Developer options' entry in Settings?

But otherwise this rom works great. ...So I'm thinking you're either very good or Chillybean is a horrible teacher ...he even stated in his second post that "...its also a great device to start learning developement on. Other devices are cake walk but this little guy is a pain in the butt..its ok though...it opens an opportunity to dive in and do some dirty work...", I thought this was supposed to be a challenging learning experience. I mean, most of the developers I follow take months to come out with a daily driver. I'm disappointed. And very, very surprised. Great work.

Just kidding, Chilly. I think you're a great teacher.
[Verizon Droid Incredible 2] chillybean:
I'll kill you....:beer:
[Verizon Droid Incredible 2] FordNate:
Chilly for El Presidente. It could happen.
[Verizon Droid Incredible 2] polymath257:
That is my understanding.

This seems to be related to whether 'auto' is set or not. If 'auto' is not set, the brightness changes with the slide.

Under Settings>about phone, press 'Build Number' several times (I think the required number is 8) and that will open up the Developer Options

in Settings.

ART is then found under Settings>Developer Options> Select runtime> Use ART. This is down near the end of the Developer Options list.

I will second that. I have a LOT to learn, but this has been a great experience.
[Verizon Droid Incredible 2] kb8no:
[MENTION=4922966]121tech[/MENTION] I had 4ext 1.0.0.5 RC9 which I have been using for a very long time but it would not flash this ROM and deleivered the Status 7 error. Because of your tip, I updated it to the recent 1.0.0.6 RC1 and it flashed with no problems.

[MENTION=4893336]polymath257[/MENTION] (or anyone) : I think that the blue Launcher is the "Google Experience" launcher and Launcher3 is the CM launcher. Can you confirm and tell me the advantages and disadvantage of each of them and your preference?

I can confirm that this ROM works fine on Verizon CDMA. So far it seems excellent.

[MENTION=4922966]121tech[/MENTION] , can you give me a primer on how to use this ROM on GSM? I want to take it to Europe in a few months. I'd like to know the tricks. I've never used it on GSM for want of opportunity but I've read lots and lots.
[Verizon Droid Incredible 2] kb8no:
Thanks for the great info. I have unlocked the SIM card already and I'm eager to try it. I already had Network Signal Pro on the phone for other reasons (finding towers in our remote area). The thing should work fine.
[Verizon Droid Incredible 2] 121tech:
A few years ago I bought an extra DInc2 off ebay and put an AT&T SIM in to make sure I knew it would work before going overseas.

Was limited to EDGE Data (220 kbps) in the US but overseas I could get H and 3G indicators (7.2 Mbps) with the right SIM Card and HSDPA 900/2100 network operator.
[Verizon Droid Incredible 2] kb8no:
I think like you. I also have 2 x Dinc2, I got one for free from a friend that wasn't charging so they upgraded. It just had a bad battery. I got the unlock key for mine easily from Verizon. Verizon couldn't generate an unlock key for the second one becasue HTC had not somehow put the phone ID on the lists it sends to the carriers. Verizon had me send it into HTC for "repairs" and then sent me a different one back and Verizon generated an unlock key with no problems. So now I have two unlocked Dinc2's, one for me and one for my wife when we travel. I sent one to Europe with my brother and it worked fine for him so I know it works. Orange I think is what he used. Plus all the guys from Asia are crying until GSM works and they like this phone. I think that it can take some TLC to get the carrier specifics exactly correct for the SIM card to get it started. I gotta get there and get a SIM and then just figure it out. Thanks again for the encouragement and GSM details for this ROM.
[Verizon Droid Incredible 2] kb8no:
[MENTION=4893336]polymath257[/MENTION] You compiled a ROM which is an accomplshment. If you care, I had to stop using your CM11 as a daily driver. It is very laggy and Chrome is difficult to use. If rotation is on it becomes often unresponsive. It drops data intermittently at least daily.

[MENTION=4898737]chillybean[/MENTION] I went back to Beanstalk. I re-discovered the absence of a camera. I think I left Beanstalk and the Dinc2 because of similar data drops. Is this a known issue? The other problem is the absence of a camera. What are the causes of why the camera can't work on 4.4 and what is the hope for a camera?
[Verizon Droid Incredible 2] alochmst98:
Here's a recent post in Chilly's ROM thread.
[Verizon Droid Incredible 2] len207:
Installed with ex4 recovery and feel it runs more smoothly then the Beanstock 4.4 - will there be any further update for this ROM?
[Verizon Droid Incredible 2] wmsforties:
More development for the Incredible 2 than the Galaxy S4..
[Verizon Droid Incredible 2] polymath257:
Unfortunately, I do not have the skills at this point to do much. I would love to get the camera working for cm11, but that seems to be a stretch for me at this time. Of course, if chilly or anyone else has some suggestions, I would be more than happy to try them out and post anything that works.
[Verizon Droid Incredible 2] len207:
Thanks for the work you've done so far it is appreciated! I'll follow this thread and see if you and Chilly can do more magic for the inc2.
[Verizon Droid Incredible 2] Osiris19:
Slightly confused. Do you have to use this recovery or can I use my already installed EXT4?
[Verizon Droid Incredible 2] 121tech:
Many people have recently mentioned that 4EXT Recovery Touch v1.0.0.6 RC1 (released Dec 31, 2013) can be used to load this ROM without need of the included Recovery.
[Verizon Droid Incredible 2] polymath257:
Starting with cm11, there are some extra instructions in the install script. Because of this, you need a kitkat compatible recovery. It is my understanding that the most recent versions of 4EXT are kitkat compatible.
[Verizon Droid Incredible 2] alochmst98:
Between his new son and his day job, Chilly seems to be too busy to post here anymore. He also may have lost interest in the Incredible 2 after getting an HTC One. It's all understandable, but developer interest in the Incredible 2 seems to have dried up.

If you're still interested, polymath, here's what I suggest. Get in touch with [MENTION=4622338]szezso[/MENTION], who develops ROMs for the Incredible S including CyanogenMod 11. The Incredible S is a sister phone of the Incredible 2, GSM-only and made for international markets. I'm told that there are some differences, but there's enough in common that I have seen multiple threads about software ported from the Incredible S to the Incredible 2.

Szezso was able to get several features working in CM11 on the Incredible S, including camera and screenshots. Here's the full list:

Maybe szezso can help you out a bit or point you to some places to learn about ROM development for these devices, and then you can combine that with Chilly's instructions in this thread. You may also want to contact [MENTION=5167139]psone1[/MENTION] (Inc S), [MENTION=4380485]LeoPosas[/MENTION] (Inc 2), [MENTION=2780293]preludedrew[/MENTION] (Inc 2), [MENTION=5149553]Gizmo648[/MENTION] (Inc S), [MENTION=5014104]achilles08[/MENTION] (Inc S), and [MENTION=4468696]funCrash93[/MENTION] (Inc S).

Also, here's a video about demystifying custom ROM development: https://www.youtube.com/watch?v=4jKmoUo59NQ#t=408 and here are some unofficial show notes for that video.
[Verizon Droid Incredible 2] brymaster5000:
Also take a look at bsmitty's port of the kangaroo kernel. This came from poondog's IncS and I believe all he did was change out the board designation. So it shouldn't...be too much to change.

Sent from my Lunar Ecliptic One.