yashsingh1/xdaforums huggingface dataset:
[Android] TimSchumi:
I'm building CM13 at the Moment and just want to ask, how to define ro.Hardware, which is referenced in init.rc like this:

/import init.$(ro.hardware).rc

I want to avoid hardcoding it directly into the init.rc

Methods I have tried so far (none of them worked):

Adding TARGET_KERNEL_CMDLINE := androidboot.hardware=something to BoardConfig

Adding androidboot.hardware=something to the cmdline in the kernel defconfig

Adding ro.hardware=something through ADDITIONAL_DEFAULT_PROPERTIES in the device.mk

Device tree: http://www.github.com/SiniTurk/android_device_samsung_cs02/tree/cm-13.0

Kernel source: http://www.github.com/SiniTurk/android_kernel_samsung_cs02/tree/cm-13.0

Vendor tree: Does not exist yet
[Android] psbankar:
sorry for a noob question but how are the developers developing the rom for nougat when there is no cm-14.0 branch for cyanogenmod?
[Android] MJPollard:
Actually, there is, but it's still early days, and I don't think very many devices are supported yet. It probably is also little more than AOSP in terms of features, as the CyanogenMod team usually makes things stable before they start adding their unique features to it.
[Android] psbankar:
Is it the staging/cm-14.0?
[Android] furkaan28:
can some one help me with this error ? http://pastebin.com/mGXyiNGG

thanks
[Android] nitin.chobhe:
Check if you have vendor repo for device and device/qcom/common

Nitin
[Android] aadityarulez:
How did you understand that vendor reoo was needed ? I'm trying to learn as well. Thanks.
[Android] nitin.chobhe:
I've seen this error many time and when I saw that for the first time I searched on Google for this error.

If you want to learn building a ROM you'll have to search a lot and read a lot :good:

Nitin
[Android] Infinity:
+1 for this

Very True
[Android] aoleary:
Hi. I'm trying to build a ROM for an unsupported device and I would just like to know is the XYZ.dependencies file only for XYZ repos, or should I add all the repos in my roomservice file also to the XYZ.dependencies file. I need to sync mostly non XYZ repos..
[Android] nitin.chobhe:
To start with, you can even skip the dependencies file and clone the required repos manually.

Basically this file is used to fetch the device specific repos (like kernel, common etc) which are not maintained in ROM github.

Nitin
[Android] aoleary:
@nitin.chobhe Thanks for the clarification.

I'm trying to build the d855 for DU, but I keep getting this error:

I found this commit, but it is related to the Nexus device Bullhead.

https://github.com/BlissRoms-Device...ackages/apps/CarrierConfig/res/xml/vendor.xml

So, (a) I dont know if it is relevant, and (b) how do I use it for the d855 if it is relevant :(

Any help appreciated.

By the way, my xml (borrowed from nobe1976):

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<!-- Device -->
<project name="CyanogenMod/android_device_lge_d855" path="device/lge/d855" remote="github" revision="cm-14.1" />
<project path="device/lge/g3-common" name="cj360/android_device_lge_g3-common" remote="github" revision="n7x-caf" />
<project path="kernel/lge/g3" name="cj360/android_kernel_lge_g3" remote="github" revision="n7x-caf" />
<project path="vendor/lge" name="TheMuppets/proprietary_vendor_lge" remote="github" revision="cm-14.1" />

<!-- Needed Repos -->
<project path="external/sony/boringssl-compat" name="DirtyUnicorns/android_external_sony_boringssl-compat" remote="github" revision="m-caf"/>
<project path="external/stlport" name="DirtyUnicorns/android_external_stlport" remote="github" revision="n-caf"/>
<project path="external/connectivity" name="DirtyUnicorns/android_external_connectivity" remote="github" revision="n7x-caf"/>
<project path="system/qcom" name="DirtyUnicorns/android_system_qcom" remote="github" revision="n7x-caf"/>
<project path="external/bson" name="DirtyUnicorns/android_external_bson" remote="github" revision="n7x-caf"/>
<project path="hardware/qcom/msm8x74" name="DirtyUnicorns/android_hardware_qcom_msm8x74" remote="github" revision="n7x-caf" />
<project path="vendor/qcom/binaries" name="DirtyUnicorns/android_vendor_qcom_binaries" remote="github" revision="n7x-caf" />
<project name="DirtyUnicorns/android_hardware_sony_thermanager" path="hardware/sony/thermanager" remote="github" revision="n7x-caf" />
<project name="DirtyUnicorns/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="n7x-caf" />

<remove-project name="android_external_libnfc-nci" />
<remove-project name="android_hardware_qcom_bt" />
<remove-project name="android_hardware_qcom_wlan" />
<project path="external/libnfc-nci" name="LineageOS/android_external_libnfc-nci" remote="github" revision="cm-14.1" />
<project path="hardware/qcom/bt" name="LineageOS/android_hardware_qcom_bt" remote="github" revision="cm-14.1" />
<project path="hardware/qcom/bt-caf" name="LineageOS/android_hardware_qcom_bt" remote="github" revision="cm-14.1-caf" />
<project path="hardware/qcom/wlan" name="LineageOS/android_hardware_qcom_wlan" remote="github" revision="cm-14.1" />
<project path="hardware/qcom/wlan-caf" name="LineageOS/android_hardware_qcom_wlan" remote="github" revision="cm-14.1-caf" />
</manifest>

I am at a complete loss as to what I should do :( I'm also a bit of a noob, so reply to me like you would reply to an idiot :p
[Android] TimSchumi:
Track DirtyUnicorns/android_device_packages_apps_CarrierConfig inside your local manifest

EDIT: This repository doesn't seem to exist. Track the same repository from LineageOS instead
[Android] aoleary:
God, I spent days looking for a solution :( The so much :)

By the way, can you provide me with some pointers on how you found that? I had tried searching for CarrierConfig in DU's github. Did you just do a search in the LOS github, or is there a technique to it?

---------- Post added at 23:47 ---------- Previous post was at 23:01 ----------

Hmmm. Added it to my xml, but I now get this problem.

build/core/binary.mk:1180: external/deqp/Android.mk: libdeqp: Unused source files: \
build/core/binary.mk:1180: external/pdfium/third_party/pdfiumbigint.mk: libpdfiumbigint: Unused source files: bigint/BigInteger.cc bigint/BigIntegerUtils.cc bigint/BigUnsigned.cc bigint/BigUnsignedInABase.cc
frameworks/av/camera/cameraserver/Android.mk:18: Target has integrated cameraserver into mediaserver. This is weakening security measures introduced in 7.0
build/core/package_internal.mk:143: Empty argument supplied to find-subdir-assets
find: ‘/home/antoin/DU/out/target/common/obj/SHARED_LIBRARIES/libwifi-hal-mock_intermediates’: No such file or directory
build/core/package_internal.mk:143: Empty argument supplied to find-subdir-assets
build/core/binary.mk:37: libwifi-hal-qcom uses kernel headers, but does not depend on them!
build/core/binary.mk:37: libwifi-hal-qcom uses kernel headers, but does not depend on them!
build/core/base_rules.mk:183: *** packages/apps/carrierconfig: MODULE.TARGET.APPS.CarrierConfig already defined by packages/apps/CarrierConfig.
make: *** [/home/antoin/DU/out/build-du_d855.ninja] Error 1

real	0m13.658s
user	0m11.280s
sys	0m1.672s

I tried deleting the CarrierConfig line from my manifest xml again, but then location disappears. So, it definitely did not exist before I added it to my xml.
[Android] TimSchumi:
I found this, because you always look for a repo with the same name as in the intermediates error message. And when you mentioned an overlay for packages/apps/CarrierConfig, I was sure

About the Error Message, try to delete the second file/folder called CarrierConfig.make
[Android] aoleary:
I think the error may have come from the fact that in my xml, I changed the repo to lowercase, when it is uppercase in github.

CyanogenMod/android_packages_apps_CarrierConfig

I think I will probably find two directories created, but have to verify that when I get home from work

Also, I noticed that there is a line mentioned in the output I provided last night:

find: ‘/home/antoin/DU/out/target/common/obj/SHARED_LIBRARIES/[B]libwifi-hal-mock_intermediates[/B]’: No such file or directory

I found this repo, so I guess I should add that too..

https://github.com/CyanogenMod/android_hardware_libhardware
[Android] TimSchumi:
Try to change it to uppercase then. Also, I think that the Error won't go away. Could you get the output of "ls -al packages/apps" and send me all lines of files starting with CarrierConfig (both uppercase and lowercase)?

Always remember to sync to the exact same path the repository name implies
[Android] aoleary:
Just the one occurrence:

antoin@OL:~/DU$ ls -al packages/apps
total 180
drwxrwxr-x 45 antoin antoin 4096 mars 14 20:11 .
drwxrwxr-x 9 antoin antoin 4096 mars 4 16:54 ..
drwxrwxr-x 6 antoin antoin 4096 mars 4 16:53 BasicSmsReceiver
drwxrwxr-x 8 antoin antoin 4096 mars 4 16:53 Bluetooth
drwxrwxr-x 5 antoin antoin 4096 mars 4 16:53 Calculator
drwxrwxr-x 9 antoin antoin 4096 mars 4 16:53 Calendar
drwxrwxr-x 5 antoin antoin 4096 mars 4 16:53 CalendarWidget
drwxrwxr-x 12 antoin antoin 4096 mars 4 16:53 Camera2
drwxrwxr-x 7 antoin antoin 4096 mars 4 16:53 CarrierConfig
drwxrwxr-x 6 antoin antoin 4096 mars 4 16:53 CellBroadcastReceiver
[Android] TimSchumi:
That's weird. The only thing I could fix is the first error message. But I don't really know what it complains about in the second
[Android] aoleary:
Its gone a bit weird. I renamed the CarrierConfig repo in my XML to the same as it is on github, but then when trying to repo sync I got an error mentioning a duplicates path in manifest.xml, so I deleted the line from my repo and DU another repo sync, which said it deleted CarrierConfig, but its still there in the fs.

I tried brunching, but got the original error again about the missing classes related to CarrierConfig..

So now I don't know if it existed already or not...

But it mustn't have since searching for CarrierConfig on the DU github returns nothing.

So then I deleted the line in the manifest.xml and redid a repo sync, but I still get the error:

ninja: error: '/home/antoin/DU/out/target/common/obj/APPS/CarrierConfig_intermediates/with-local/classes.dex', needed by '/home/antoin/DU/out/target/common/obj/APPS/CarrierConfig_intermediates/classes.dex', missing and no known rule to make it
[Android] aoleary:
In the end, I just repo'd back to my standard xml, and added in new repos one by one and I dont have this issue anymore, even though I have added back all the same repos as before
[Android] rajit:
i am stuck here .. its not official device.

help needed

here is my roomservice.xml https://pastebin.com/MDUxAYU9

please help :(
[Android] KazuDante:
Were you able to find a fix for that?
[Android] mrbox23:
Anyone? I got rid of the EXIDX stuff by using ubertc 4.9 arm eabi
[Android] IDontKnowMang:
. build-environment-setup.sh

bash: build-environment-setup.sh: No such file or directory
[Android] mkaraniya:
Thanks a lot
[Android] mkaraniya:
help

i think that many commands are not working now !! please help
[Android] riteshrk.aec:
how do we make proprietary-files.txt for a phone whose device tree is not available ?
[Other SmartWatches] Lokifish Marz:
Only IPx6, multiple (more than 3) actions to access key info and apps for "Probably 249 or 299"? Hard sell, even with custom ROM support.

On the square version, a bezeless display is easily possible if the PCB and battery are not larger in area than the display area.
[Other SmartWatches] raffaeu:
Hi Lokifish and thank you for your feedback.

The answer you mention is about the Black version, which is full Black Stainless Steel, including the wristband. Consider that only the wristband has a production cost of 28$ (without VAT) the price of 249$ does not look that bad to me. Think about OLIO SmartWatch, it's a full Stainless Steel watch with locked ROM and it's sold for almost 600$ a piece.

About the square version, we couldn't find ANY manufacturer in Taiwan, China and Singapore capable to produce a full baseless square display, only round can be baseless but if you know any manufacturer capable of making AMOLED display squared with Gorilla Glass I would be more than happy to get your help, we are still in the beta version of our product and any feedback is welcome and well appreciated.
[Other SmartWatches] Lokifish Marz:
The OLIO is also design by watchmakers, uses 316L SS, and has a water resistance 50 times greater than that IPx7 with no time limit like IPx7 has.

As far as the band, you can get decent quality folded SS bands for around $15-20 USD at full retail price.

A bezeless square display can be done. It requires an approach not seen in smartwatches though that makes assembly a little more difficult but is still doable. Also, "Off the shelf" designs simply don't cut it as it requires the "crystal" be cut a certain way.

Have your guys look over "U.I Design", "Why this Martian.. ", and "I bet your smartwatch..." links in my signature below. Feel free to pick my brain and use the information in the links. The minimum I ask is that you give proper credit if you use any of it.

Looking at your G+ posts, nice job with the Ingenic BTW. I designed and built a smartwatch using the same platform. Too bad I killed it during a 5 ATM water resistance test.
[Other SmartWatches] raffaeu:
Hi Lokifish, again useful details and feedback.

You are right, a nice and decent band is probably available on AliExpress for less than 20 bucks, but we made our with a different manufacturer and for the first batch we ended up with a cost of 28$.

This is another reason why we want to get this project into the community, to get feedback and suggestions from people that faced these problems before us.

About OLIO, of course they used high quality materials, a nice design, but I personally disagree about the ROM and UX choices (but this is my personal feeling). The point for me it's about the price. Pebble manufacturer their watch for 18$ and sell it for almost 199$, now dropped to 149$ if I am not wrong.

We are a startup and we will probably endup in some incubators or crowdfunding website in order to start the mass production. Probably the price will be around 199$ on retail but again, the prices and costs we are facing are a bit different than the one faced by watchmakers that have been on the market for many years.

What we believe is different between OXY and the rest of the world is the community, we want to make an open product, we want to make the customer capable to install custom ROM, customize the body and more. This is where we see the added value that other watch makers do not have at the moment.
[Other SmartWatches] simple1i:
[MENTION=3795702]Lokifish Marz[/MENTION] - thanks for the reply and pointing out OXY ... I feel like there's ... just a little hope ... maybe

[MENTION=6612616]raffaeu[/MENTION] - please take into account Lokifish Marz's advice, he will be very valuable to you, from a historical, current & future point of view. You'll save a lot of time and effort.

There are only a few people in the world that can make a decent, let alone a 'good smartwatch', due to greed/profit, but it can be done with the right goals and vision. Always know your history! Courtesy to the Martian ... again ;)

I'm not a techy as such, but an important aspect of a good product is the non-functional business aspects, how to make a robust watch and then marketing, communication, support, together with making a little profit of course. Techies alone can't do this (no offense). Out of desperation we started the Nowt Watch thread, please have read, some very interesting discussion. No doubt you're at a stage where you can't go back with your current products, but we can always better our understanding and add to our knowledge and experiences.

I purchased an Omate clone recently (I had to get it out of my system), some of the non-techy issues, charging it - a pain! Straps - awful! A companion watch, should still be like a stand-alone watch first, meaning, above all its a robust time-piece that many can/would use without a phone as maybe a sports and leisure watch.

I'm curious, what does OXY mean? You have my support if you want it. I used to be a software tester, as well as marketing, strategy, process ... all that boring important stuff. Good luck :)
[Other SmartWatches] raffaeu:
[MENTION=3795702]Lokifish Marz[/MENTION] has some interesting articles and idea that we are taking into consideration. Our primary targets are:

make an open source product

build a brand and trust from the community

make a real watch, solid, durable and with style

We designed OXY to being able to run with a phone and without, in fact without the battery stay charged for almost 1 week. Secondly is the charger which is magnetic, so that our customers are not having the frustration of the USB cable pain.

We are here to get feedback, idea and of course help. Anybody is welcome to join us, we are also hiring so anything is possible. Of course we are a startup so we still need to pay salaries and bills but we are not willing to become rich but we are willing to build a trusted brand for IoT products and more precisely for smartwatch. I always say that OXY is a mission for me and not a company.

OXY is an acronym for oxygen, something that you need and that's required to humans to live. :)

Feel free to contact me [MENTION=1938297]simple1i[/MENTION] and we can discuss further our project. In the meantime I'll have a look at your links.
[Other SmartWatches] simple1i:
Oh I see Oxy. I do like the name Horology, that's what all good (smart)watch lovers are, there's an idea for a name of a smartwatch.

Correct me if I'm wrong, but you decided to used Android because it's the cheaper/faster (way to get it up and ready) option? Do you have Playstore on the OXY? Google can be very awkward about this.

Listening to the tech' community is a good thing, but for a 'fine dining' watch the experts are few, you need the Horologists, the real trick to to know what opinions to take on and what to discard. Then its a matter of goods ideas/functions vs costs. This might be a tough one to address, but the OXY needs to be either better then the Moto 360 2's (rumoured specs) or similar with a lower cost. So far I'm impressed. I am waiting to see what Pebbles does with the I/O port on the back of their watch, what hardware add-ons will they come up with? A good future proof strategy for them to expand functionality.

I'll be in touch.
[Other SmartWatches] raffaeu:
[MENTION=1938297]simple1i[/MENTION] it was not easy, we had to search for conflicts with other trademarks, copyright and we also needed something simple to pronounce considering that our product will be sold worldwide. OXY sound easy but it is still a nice sound to pronounce

Our PCB is an extension of Ingenic Newton2. We had to modify the plug for the display because the original one was not enough for round and square displays plus we added an heart rate, a vibration motor a different Bluetooth and a Lipo battery of 400mAh. We changed the USB port and overall we came up with the cheapest but more flexible solution.

Why? Because we have a public AOSP for Android 4.4 and Linux which means that our product can fit any development configuration without any license problems. Just use git, download our AOSP and create your own smartwatch.

Google play will be added later, as I said our goal is to provide an open platform with a default set of apps but without any license or warranty limit. Our license and warranty will cover only the hardware, about the software our customers will be able to fully customize the product.

For sure v1 won't be perfect, for sure we will need time to build up a community but based on the fact that we have an AOSP on git, that you can easily make custom apps with Android studio and that our price range will be lower than other android smartwatches, I think and hope that our product will be well known very soon.

Finally, we will run a crowdfunding but our mass production is already set. A big, big advantage compared to other crowdfunding campaigns
[Other SmartWatches] Lokifish Marz:
Unless Google has retroactively changed a number of things and not published it, official Google Services support (certification, service framework, Play Store, etc) is a no go. A couple of smartwatch manufacturers found out the hard way, one of which made it into tech news because of it. That's just one of many sites that covered it and I was working directly with Omate at the time this happened. The only smartwatches with official support run Wear, which requires partnership status.

Here's a good place to start
[Other SmartWatches] raffaeu:
[MENTION=3795702]Lokifish Marz[/MENTION] partnership status is a no go. Also Pebble tried somehow to have a sort of partnership with Google, even if Pebble does not run Android at all, but they go a big no. Regarding Android WEAR, we have submitted in June 2 requests including draw, project details, hardware details and more and we never got an answer from anybody. We know that our OXY can run Android WEAR, we also took apart the SDK of Android WEAR to see how it works and at the end we choose to stay Open Source and give up on Google WEAR for now. Then in the future anything can happen, we are totally open to any conversation but our mission is to make an Open Source Smartwatch, so having a smartwatch locked down by Android WEAR .apk is not our business model right now. The giant Samsung has left Android WEAR and also OLIO did not even approach Google at all. Why? Probably because Google is taking some business decisions that cannot fit all watchmakers out there right now.

About Google Play, that's a different story. Our current hardware is better than Asus Zenwatch and the Moto 360 v1.0, the only limit for Google Play is the resolution. Our Round watch has a resolution of 400x400 while the squared has a resolution of 320x320 and we are using the same displays manufacturers used by LG and ASUS. But again, when you talk about smartwatch, you open a Pandora Box. It is the new business for any manufacturer, Forbes announced an estimation of over 30 billion dollars business between now and 2020.

But again, we can manually install Google Play and it just works fine, so what's the point here? We need first to create a community, distribute our product with a basic ROM so that users can receive notifications, phone calls, download and create watchfaces and all the things you want to achieve with a smartwatch. We have already setup an Azure play store where any developer can grab our SDK and our Genymotion virtual image, create apps and distribute them via our Cloud.

Then, probably next year, we will see how the things go and we will be able to present again a request to Google for both, Android WEAR and Google Play.

Again, I have spent now almost 1 year in R&D and I feel confident that Android WEAR is a closed business. You must be a big firm otherwise is a no go for now. About Google Play I am more positive but only time will say. For now we are focused on our website and marketing campaign, building a community and customizing our existing ROM and SDK. Btw, if you look at the potentialities of OXY, we have already a more powerful product in terms of frameworks and hardware, than a Pebble, which has sold more than 1,---,--- pieces between 2012 and 2015. We also got a conversation with Cyanogen which gave us a go to customize Cyanogen for OXY but at this point is worth to have our own Open Source Android version and move from there with the help of the community.