yashsingh1/xdaforums huggingface dataset:
[Desire 816 Android Development] bigsupersquid:
A built in version is making right now.

It may have issues with missing caf bits in the cm kernel... Or maybe because it's built for another device.

I was surprised it worked out of the box anyway since it's from a yureka forum.
[Desire 816 Android Development] drummer1839:
Works great on a5 ul thanks for the rom

Wysłane z mojego Desire 816 przy użyciu Tapatalka
[Desire 816 Android Development] bigsupersquid:
new camera zip uploaded. I had to take out the 1440p setting for a 'quick' compile.

new rom build not ready yet though.

The new build should fix gsm problems, and, I'm hoping, the gps glitches I found yesterday.

same download folder for camera.

/edit: well I thought it uploaded.

It's there now, the _new_build zip.
[Desire 816 Android Development] Bandit Development:
Great, I try the new camera. Can I just flash over the existing camera?

Also, is it possible to build this ROM from stock using CM sources, or will that not work? Thanks.
[Desire 816 Android Development] bigsupersquid:
the one i found was in priv-app, the source built one lives in app instead.

So it won't exactly flash over, should've specified that or made the zip remove the previous version.

I should fix that. Gimme a few.

I build from cm with a few changes, and first build was from blobs pulled from my stock ROM... That's why there've been issues with gsm I think.

You can use TheMuppets/propriety_vendor_htc for blobs.

I'll post up a proper roomservice.xml when the new build goes up.
[Desire 816 Android Development] Bandit Development:
Alright, good to know.

I was just curious how much work would be required to build, since I've only done it a few times before for Nexus devices.
[Desire 816 Android Development] bigsupersquid:
I fixed the camera zip, flash it over the other.

This was nearly the easiest cm build I've done, the exception was my evo3d had a couple active kitkat repos for a while that were pure sync and go.

Hopefully once my roomservice.xml is up this one will be sync and mka bacon too.
[Desire 816 Android Development] Bandit Development:
Alright, flashing now. EDIT: Just tried after flashing, but the Snapdragon Camera still freezes after taking the first picture. Does the .zip effect any other camera apps, or just the Snapdragon one?

If building becomes easy enough, I'd like to try building so we could have more frequent builds.

What machine specs and OS do you use for building? When I built CM for Nexus I used Arch BBQ Android Linux, but the machine only had 4Gb of RAM, a 5400 RPM HDD, and a weak CPU.
[Desire 816 Android Development] bigsupersquid:
clean your dalek cache. leftovers from previous app probably.

Ubuntu 14.04, 2.9GHz dual core, 4GB RAM. Takes some hours for clean build.
[Desire 816 Android Development] Bandit Development:
Wiping the cache didn't help.

So if I clean built using my desktop (6Gb RAM, 3.1 quad core, Linux Mint) roughly how long do you think it would take to build? Just wondering in case I could build overnight since I don't use Linux as my primary OS.

Thanks.
[Desire 816 Android Development] bigsupersquid:
It should build overnight, but no telling how long to sync the huge repo.

new camera app's working ok in new build, dunno why the flashable fails.

//edit: if it matters, this one's named 'Camera' instead of 'SnapdragonCamera' in the app drawer.
[Desire 816 Android Development] bigsupersquid:
new build up, includes snapdragon camera.

should have gsm blobs too.
[Desire 816 Android Development] GreyCelt:
Are there any other changes or updates from CM in this build? I'm just trying to figure out if I actually need to flash it since I've already flashed the Snapdragon Camera and I don't have a GSM device.
[Desire 816 Android Development] drummer1839:
In new build the snapdragon camera freezes .I tryed dirty flash from previous version.

Wysłane z mojego Desire 816 przy użyciu Tapatalka
[Desire 816 Android Development] bigsupersquid:
Enough stuff showed up on repo sync that when I tried a dirty build (make installclean && mka bacon) it forced a make clean and took forever to rebuild everything on my slow old PC. But visually I don't see any changes, and the security patch level is still dec 1, so you probably don't need to update.

Did you install the first camera zip before the dirty flash? Mine works OK on a clean flash. The original zip I put up had issues apparently.

If you used it, maybe try flashing the new camera zip in recovery to remove the one in priv-app, wipe dalvik-cache, reboot, and clear app data under settings>apps>SnapdragonCamera.

I dunno. Dirty flashes cause all sorts of weird problems.

And as far as this device/kernel/ROM goes, snapdragon camera is barely tested yet.

Thanks for the report.

I forgot to mention in the op, force closes and issues are more easily resolved with logcat pastebin.com links.
[Desire 816 Android Development] ajones23:
Looks like when I installed snapdragon.zip,now it force closes.
[Desire 816 Android Development] bigsupersquid:
The new one? Maybe the add-on zip is borked somehow.

I wipe and reflash and format and tinker so much it's hard for me to tell just what combinations do what sometimes.

I do know that with a clean flash of the 12/25 on my a5 (wipe system/data/cache before flash) I have seen the freeze on the first time the camera takes a picture.

A soft reboot lets the camera hardware reconnect, and then the camera seems fine after that. So far, and I haven't extensively tested it.

When it glitches at you, post me a logcat in a quote or on pastebin.com to check out.

I accidentally wiped my internal sd partition, with my a5 backups on it :silly: so dirty flashes aren't really much of a possibility here without deliberately setting one up.
[Desire 816 Android Development] ajones23:
Yeah I do so many mods,something must have gotten borked. I was planning a clean flash later on. Got to play some BO3,great ROM. Thanks.
[Desire 816 Android Development] Bandit Development:
I want to try the new build, but don't want to lose all my app data, especially my Amplify settings. Anyone have suggestions how I could transfer this data to the new build?

Thanks, I haven't really worked with data preservation between builds before.
[Desire 816 Android Development] ajones23:
Really there is no way to do it,Titanium Backup. Usually I bite the bullet and wipe all. I just flashed 12/25 and no problems so far.
[Desire 816 Android Development] thoctor:
app data backups

I use Amplify too. it's great. The best way and the way I use to keep my app data between CM builds is Titanium Backup. Don't backup or restore any system apps as they can be different between different roms but backup your installed apps plus data to your external SD card and then restore after flashing. I also use in the initial Rom setup and before , Googles own backup features which are quite good. The last restore I did even restored my app folders and internet shortcuts on my home page but don't expect that every time it's hit or miss. Also back up in Titanium backup your texts, call logs and calender in the "export to XML file" option in Titanium's settings. Titanium tracker website has the how to and faq section for Titanium backup but it's really very simple just an older interface. Be patient and it works great. Be sure your already using Google's own backup features in your phone settings but it won't restore app data just Contacts and numbers and such. Text restore through TB and or an app called Super Backup, I do both for texts, calender and call logs and you'll be fine.

Titanium backup needs you to set the external SD card for your backups and the Titanium tracker site tells you how to do it but basically I made a folder in my external SD card called Titanium backup and inside that folder made a sub folder called Titanium backups with an s at the end and then in TB settings pointed it to this main folder using it's file explorer. Sometimes can take a few tries but it works eventually. It's just lollipops way of assigning apps folder permissions for external SD cards.

YouTube also had some good video tutorials on using Titanium backup as well. Let me know if you need any more help.
[Desire 816 Android Development] Bandit Development:
[MENTION=5979440]thoctor[/MENTION] Thanks for your thorough and helpful response. I am busy and my main computer will be unavailable for the next few days, so I don't want to attempt any kind of backup etc. at the moment, but I will let you know when I have a chance to try your advice.

[MENTION=3951714]ajones23[/MENTION] I understand the "bit the bullet" flashing mentality, and that's what I have usually gone with in the past. However, I use this device a lot for my mobile game development so I don't really have the option to lose settings, app data, etc. every time I flash. :/
[Desire 816 Android Development] ajones23:
Yeah sorry for that comment sometimes I just wipe it all. But your idea of backing up data has crossed my mind. I have a PNY 128gb SD coming in soon. Good luck.
[Desire 816 Android Development] thoctor:
"Thanks for your thorough and helpful response. I am busy and my main computer will be unavailable for the next few days, so I don't want to attempt any kind of backup etc. at the moment, but I will let you know when I have a chance to try your advice."

No problem and your welcome buddy. The thing about all the stuff I spewed is that you can do it all from just on your phone and it will survive the wipe when you reflash a new rom. I know because I've flashed everything under the sun available for my version and all my backups have survived every time. It's only if you select to wipe your internal storage or micro sd card will you run into problems but the normal factory reset is fine in most cases .Sometimes people choose to also wipe their data in custom recovery as well but that's not your personal data just the system data.

I used to also backup on my computer using HTC sync but now that I'm on custom roms that's not an option anymore so TB is my new best friend. Let me know how it goes and if you need any help let me know.
[Desire 816 Android Development] Bandit Development:
There is definitely no need to apologize, I appreciate your input. I just wanted to explain why I didn't want to use that method this time. :)

The fact that this device has a SD card slot is great; it really helps for data backup.

[MENTION=2980661]bigsupersquid[/MENTION] sorry I've gotten off topic.
[Desire 816 Android Development] exProphecy:
Is the Snapdragon camera add on zip still having first picture freezing issues? I can take a look at the .zip if need be :D Also, if it is still having issues, please leave a note in the OP about it :)
[Desire 816 Android Development] Shedal:
Yes. The checksum matches. Where should the GSM core files be located?
[Desire 816 Android Development] bigsupersquid:
Dunno. Hard for me to test further and there's only a couple reports.

The zip could be tweaked to remove remnants lurking in /data/data and /data/dalvik-cache/arm.

Try the new build, should have the gsm goodies included.
[Desire 816 Android Development] Shedal:
It installed without any errors. Thank you!!

Now I have mobile data connection, even though it doesn't always appear straight away after a reboot.

Normally, to make it work I need to turn off the phone, take out the SIM, turn on the device and put the SIM back in. Otherwise, it either doesn't recognize the Sim or can't find the mobile network.

I could probably live with that, but -

The biggest problem is phone functionality. The phone doesn't receive SMS messages and doesn't display calls. I can call another number and talk, but when I hang up, the phone app is then stuck in "hanging up" until I reboot.
[Desire 816 Android Development] bigsupersquid:
Post a logcat to pastebin.com from adb after the phone freezes and give me the link here. Without a gsm variant on hand it's hard to debug too much.

At least it's headed the right direction.
[Desire 816 Android Development] Shedal:
Log is attached.

What I did during the log collection was:

1. Connect the device via cable and start adb logcat on my laptop

2. Insert SIM card to the device

3. Enter SIM pin code

4. Start a call

5. Pick up on the other end

6. Talk for a few seconds and hang up — the Phone application "hangs" in the sense that it says "Hanging up" and I can't do anything meaningful with it. It's still responsive though, e.g. I can show the numpad, as if I'm still in a call.

7. Close the Phone app from the task switcher

8. Open it again — it still shows the text "Hanging up" and behaves as though I'm in a call.

9. ^C on the laptop to stop adb logcat.
[Desire 816 Android Development] beherit00:
I have the same situation with my a5_ul. I had stock lilipoop next I installed one ROM for dual sim version where this problem was appear. This problem is popular when u install version build for dual sim a5 on a5_ul. When I installed yesterday your ROM (20151225) I thought that problem disappear but not.
[Desire 816 Android Development] bigsupersquid:
As a workaround, maybe try this.

The very last development setting is long press back to kill apps. Turn it on.

When the dialer won't hang up, try force-closing it with the long-press back instead of just the task chooser.
[Desire 816 Android Development] Shedal:
this won't fix the other issues

i cannot receive calls or texts

UPD: killing the Phone app this way still doesn't help :( it still behaves as though I am in a call after I restart Phone
[Desire 816 Android Development] bigsupersquid:
lots of mcc mnc not found, iccid null or missing...

ril issues.

all I can think of offhand is to set props for your mcc mnc and maybe it'll grab network better. tons of failures before it gets network connected in that log.

it grabs this APN but only on the incoming call:

D/CellBroadcastReceiver( 2924): Service state changed! 0 Full: 0 0 voice home data home Mtel Mtel 28401 Mtel Mtel 28401 UMTS HSPA CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false Current state=-1

and this mcc/mnc

D/MccTable( 1280): updateMccMncConfiguration: mcc=284, mnc=1

so maybe if you mount /system in recovery and use adb shell to

echo "ro.cdma.home.operator.numeric=28401" >> /system/build.prop
echo "ro.cdma.home.operator.alpha=Mtel" >> /system/build.prop
sed -i 's/ro.product.locale.region=.*$/ro.product.locale.region=BG/' /system/build.prop
sed -i 's/gsm.sim.operator.iso-country=.*$/gsm.sim.operator.iso-country =BG/' /system/build.prop
sed -i 's/gsm.operator.iso-country=.*$/gsm.operator.iso-country=BG/' /system/build.prop

it might help.

you'll have to

rm /data/data/com.android.providers.telephony/databases/telephony.db
rm /data/data/com.android.providers.telephony/databases/telephony.db-journal

and reboot after all that mess to see.
[Desire 816 Android Development] beherit00:
The same for me. After when I reopened app there is information about 'hanging up'
[Desire 816 Android Development] Shedal:
I followed your instructions. After I rebooted and reinserted the SIM, it was searching for network even longer than before. It found it eventually, but nothing is fixed.

I'm attaching a log starting with me inserting the SIM. It includes another (successful) outgoing call. There are no incoming calls (which is also true for the previous log, by the way).

The Phone app ends up showing "Hanging up" just the same after I end the call.
[Desire 816 Android Development] bigsupersquid:
Only other thing I can find other than possible missing stock ril libraries, is another prop:

telephony.lteOnCdmaDevice=0

Sorry. Most searches say it's a problem with cm12 finding the gsm sim.
[Desire 816 Android Development] Shedal:
What about missing stock ril libraries? What are they? How can I look into this?
[Desire 816 Android Development] Alanman13:
Very nice. I see what you did there. ;)
[Desire 816 Android Development] bigsupersquid:
I'm just starting to poke at ril for mashmallow. for me coding is a learn as you go deal and ril isn't something I've put a ton of time into before.

All I can suggest is to search for similar problems and check out solutions. there may be proprietary files in your stock rom that aren't in the vendor repo, or are different from those, that you could drop in.

Check the /default.prop and /system/build.prop from your stock rom for properties that may help. Or even getprop while running stock with working telephony.
[Desire 816 Android Development] beherit00:
I think problem appeared in CM 12.1. After I'd tested your version I flashed my A5_ul with cm-12-20151011-NIGHTLY-a5.zip (256.05 MB) and phone now works great (calls, txts).... but it is 5.0.1 :(.

Maybe solution is compare props between cm12 and cm12.1.
[Desire 816 Android Development] Bandit Development:
Maybe you could try the 12 prop on the 12.1 zip and only change the build numbers etc?

Don't forget to use Notepad++ if you try to edit the props.
[Desire 816 Android Development] bigsupersquid:
I'm afraid that since I have a running marshmallow build, that needs more development to fix all the hardware access, that I can't justify putting any more time into cm12.

So unless there are new security patches released or something, the 12/25 is the last cm12 I'm building.

Gotta work on the latest and greatest, dattebayo!

See y'all over in the alpha thread.
[Desire 816 Android Development] exProphecy:
I'm not sure if anyone can help me with this issue but.. it is an issue that I've encountered in the previous CM12 thread also. At almost seemingly random times, my phone begins to reboot. This is after maybe a few months of normal usage with no issues whatsoever. All of a sudden, it reboots then after it is finished, as soon as I unlock the screen, it reboots again. It does this, oh maybe 20 times then I decide to leave it off for a few hours. Then, I decide to try clearing the dalvik-cache and cache folder. After I reboot, it seems it is fine but then none of my apps have their previously held data. I.e. everything needs to be re setup again (as if all my data was corrupted). I enter into my /internalsd/Android/data folder and seems like everything is still there (but how come it isn't being loaded by the app?). Also, all my SD apps will no longer load. I check my /externalsd/Android/data folder and seems like everything is there also. Any ideas on how to fix this issue? Nothing seems deleted; is there a way to just reload/relink the apps and their data folders somehow?

EDIT: I also tried reinstalling an app that was already installed but moved to my extSD card. The Playstore gives me an error "Can't install app" (Error code: -504). So I'm assuming the data is still there but in the way somehow. I'd rather not delete everything since I have important data on those old data folders..
[Desire 816 Android Development] bigsupersquid:
So now that I've seen Grarak's device folders, there's definite differences for dug/dwg vs the single sim models like my chl.

Most likely an updated build with his android_device_htc_dwg would work for you guys.

When I can afford the time I'll try it and post for testing.
[Desire 816 Android Development] Shedal:
That would be great! I'll be getting my USB cable ready ;)
[Desire 816 Android Development] bigsupersquid:
Don't hold your breath too long, my overtaxed old 2.* GHz 2GB RAM desktop takes quite a while to build anything past Gingerbread...

And it's crunching fresh Marshmallow now, until I have whatever was different about the single SIM between my source and Grarak's worked out.

I never had better Virgin Mobile data signal in 5 years with multiple handsets than with my 6.0 build on this phone. It never made me toggle data or airplane mode once over days of testing. And I want that plus the WiFi and Bluetooth before moving to new tests.
[Desire 816 Android Development] Bandit Development:
If you need something built, I can give it a shot. I have a Linux machine setup with all the Android build tools. :)
[Desire 816 Android Development] Bandit Development:
Trouble Building CM

So I am trying to build CM 12.1 for my 816 partly because I want a more recent build, but also because I want to learn the process for ROM building. I am working off this tutorial.

I've run into a few different problems that have kept me from getting a working ROM built from CM source. Has anyone else managed to build a ROM .zip from the Cyanogen tutorial? I've successfully built CM for a different device before, but that was CM 11.

I installed all the tools, created the folders, and repo synced many times, but I still get an error like: "Make failed to build some targets."

Here is my latest pastebin of a build failure.

Thanks for everyone's time. I posted this on the CM 12.1 thread because I think this is a 816 specific problem, but if I should post elsewhere, please let me know. :)
[Desire 816 Android Development] bigsupersquid:
Are you using TheMuppets/proprietary_vendor_htc synced to vendor/htc?

They seem to have the go-to collection of proprietary device binaries.

That's definitely a vendor/htc/a5/proprietary/<some path> file it's looking for.

And this thread is fine for building questions and answers. Getting the issues exposed on public forum allows others to search-fu the answers, and I like that.
[Desire 816 Android Development] Bandit Development:
Not sure what repository or proprietary files I'm using. :/ I just followed the CM tut which had me pull "blobs" from my device. Is that not the same thing? If there is a way to directly download the proprietary binaries, I'm happy to try that.

Thanks for your help.
[Desire 816 Android Development] bigsupersquid:
That's what I did the first build. and it seemed to be missing a couple things (including the gsm blobs I didn't need for the _chl but did for other models)

So use https://github.com/TheMuppets/proprietary_vendor_htc

You can add it to .repo/local_manifests/roomservice.xml like

<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-12.1" />

and repo sync, that'll pull it in for you.

Or if you don't wanna drag down all the current changes, you can just

repo sync vendor/htc

after fixing the roomservice.xml

I added the vendor link to sources in the OP, since I forgot. Thanks.
[Desire 816 Android Development] Bandit Development:
Thanks! I'll try that now. Anything else I should do before I try to 'brunch a5' again?
[Desire 816 Android Development] bigsupersquid:
I've never used brunch, though it's supposed to condense the command line entries.

I just change to the source directory, then

. build/envsetup.sh

lunch cm_a5-userdebug

time mka bacon

I think you can give it a spin again once the huge vendor/htc project downloads.
[Desire 816 Android Development] Bandit Development:
The HTC project already downloaded. Only took about 3min at 5mps. I think it all downloaded. . .

I'll try your lunch setup instead of bruch. I only used brunch since that was what CM tut suggested.

EDIT: I still get this after running bruch:

find: `dummy': No such file or directory
find: `../../../../../../external/hamcrest/src': No such file or directory
find: `../../../../../../external/junit/src/org': No such file or directory
find: `../../../../../../external/hamcrest/src': No such file or directory

Not sure if that matters. I'll try lunch now.

EDIT: The build seems to be working. That is, at least it's gone farther than it did before. I update when it finishes.
[Desire 816 Android Development] Bandit Development:
[MENTION=2980661]bigsupersquid[/MENTION]

The build failed again. Here is the log: http://pastebin.com/3FLibL9p
[Desire 816 Android Development] bigsupersquid:
try make bacon again, sometimes multithread compile fails at the kernel, then works the second time without changing anything.
[Desire 816 Android Development] Bandit Development:
So just run again with:

Lunch cm_a5_debug

time mka bacon

or just 'time mka bacon'?

---------- Post added at 11:08 PM ---------- Previous post was at 10:45 PM ----------

That didn't work. I am using ccaching, but I don't think that would break a build.

Here is the log: http://pastebin.com/7YChmN2H