yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Themes and Apps] swieder711:
I copied the V18 Dialer.apk (was renamed) to the folder /system/priv-app/dialer.

I made the permissions -rw-r-r-. Cleared the phone app cached and did a reboot just to be safe.

I am now running the latest Google Dialer. You can get the APK from APKmirror by searching for "phone"
[X Style (Pure) Themes and Apps] Hitti2:
I had as serious problem updating after 17. 18+ had incoming calls where I could not answer if the screen was off, phone would lock up, had to do the 10 second power button hard reset, it took a lot to find out what the cause was, it was latest google dialer from play store update while I had a ton of other updates. What solved the problem for me was wipe phone data and cache, jump in twrp and wipe delvik and cache. Problem solved. I had to use google hangouts to call my phone for testing, if it wasn't for google hangouts it would have never been solved as I don't have a secondary phone. So, many suggestions to try if you run into this problem.

Edit:

I am using March 28th arm64 build latest at the time of writing.

---------- Post added at 02:11 PM ---------- Previous post was at 02:09 PM ----------

Nope not solved. I just tried and it still broke. Uhg.

---------- Post added at 02:32 PM ---------- Previous post was at 02:11 PM ----------

Ok, I just uninstalled the latest as of march 28th. Installed https://xdaforums.com/android/apps-games/app-google-dialer-t3557412/post71051142#post71051142 seems to be working.
[X Style (Pure) Themes and Apps] swieder711:
V18 of the Google Phone app is working perfectly. I didn't install the APK directly. Instead I copied it to the folder /system/priv-app/dialer, made the permissions -rw-r-r-, cleared the phone app cache and did a reboot.

Best of luck.

PS: I installed the latest Google Contacts app (2.6.4) directly by downloading it from APK mirror and installing it.
[X Style (Pure) Themes and Apps] swieder711:
Just install V19_Beta which I downloaded from APK mirror. I didn't install the APK directly. Instead i did the following:

Copied dialer.APK to the folder /system/priv-app/dialer

Made APK permissions rw-r-r-

Cleared the phone app cache

Selected Phone as the "default phone app"

Reboot

I like the new layout with Fav/History bar on the bottom of the phone screen.
[X Style (Pure) Themes and Apps] mddunner:
After reading through this thread, I opted to try the magisk module Google Framework and then installed the Google Phone app from the play store. Everything seems to be working, except the Visual Voicemail icon doesn't show up. I'm on Verizon.

With your method do you get the visual voicemail icon? Back when I was on nucleaROM, I had no issues using visual voicemail right from the phone app.
[X Style (Pure) Themes and Apps] swieder711:
Im using Google voice which I access thru the Google voice app.
[X Style (Pure) Themes and Apps] mddunner:
Thanks for the info. Sounds like a different config. I did a bit more reading and it sounds like visual voicemail for Verizon magically started working in 7.1, so that may explain the difference with nucleaROM. I thought it was simply the dialer app.
[X Style (Pure) Themes and Apps] BROKEN1981:
Can you post the dialer framework for 8.0?
[X Style (Pure) Themes and Apps] swieder711:
There is a Magisk module that can install the latest framework.
[X Style (Pure) Themes and Apps] BROKEN1981:
Can i get a link?
[X Style (Pure) Themes and Apps] lilcdroid:
Just open up Magisk and search the word "framework." Pops right up with a build date of October 3rd.
[X Style (Pure) Themes and Apps] BROKEN1981:
Ahh ok thank you
[X Style (Pure) Themes and Apps] schneid:
Somehow I broke this or Phone 24 did. Have run both TWRP firmware patch and have the Magisk module on. The phone will ring in and dial out but I can get the off-hook screen to accept, refuse, or hangup. I have tried several alternate dialers and they all work fine.

Any ideas suggestions.
[X Style (Pure) Themes and Apps] schneid:
Latest Dialer, 25.0.218361296-3118162_minAPI24(arm64-v8a)(nodpi), on APK Mirror works.
[Galaxy Grand 2 Q&A, Help & Troubleshooting] yumi14:
Hi,

I'm trying to build LineageOS 13.0 for my ms01lte but I'm stuck at resolving a compile rule missing :

make: *** No rule to make target '/home/yumi14/android/system/out/target/product/ms01lte/obj/STATIC_LIBRARIES/libinit_msm_intermediates/export_includes', needed by '/home/yumi14/android/system/out/target
/product/ms01lte/obj/EXECUTABLES/init_intermediates/import_includes'. Stop.

I've searched on the web, downloaded qcom-common & samsung-qcom-common as it is the most common answer but it doesn't look to solve my problem.

I'm on ubuntu 16.04 with fresh LineageOS 13.0 repo and my device sources are from : https://github.com/MSM8226-Samsung/

Anyone can help me solving this ?
[Galaxy Grand 2 Q&A, Help & Troubleshooting] yumi14:
Hello,

So, after some tests, I decided to just remove the lib from the build:

# file: device/samsung/msm8226-common/BoardConfigCommon.mk
TARGET_INIT_VENDOR_LIB := libinit_msm

I successfuly compiled a Kernel & TWRP Recovery and working well, now trying to build LineageOS 13.0 but I'm still curious how to build without removing 'libinit_msm' if someone knows.
[Galaxy Grand 2 Q&A, Help & Troubleshooting] Subhashis:
I also tried to compile a kernel but it shows

soc sound changed from boolean to tristate after make command?

How did you do this?Which toolchain are you using?
[Galaxy Grand 2 Q&A, Help & Troubleshooting] yumi14:
Do you have all the needed components ?

Here's my manifest for ms01lte:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="MSM8226-Samsung" fetch="https://github.com/MSM8226-Samsung/" />
<remote name="CyanogenMod" fetch="https://github.com/CyanogenMod/" />
<remote name="TWRP" fetch="https://github.com/omnirom/" />
<project path="device/samsung/qcom-common" name="android_device_samsung_qcom-common" remote="CyanogenMod" revision="cm-13.0" />
<project path="device/qcom/common" name="android_device_qcom_common" remote="CyanogenMod" revision="cm-13.0" />
<project path="external/busybox" name="android_external_busybox" remote="CyanogenMod" revision="cm-13.0" />
<project path="bootable/recovery-twrp" name="android_bootable_recovery" remote="TWRP" revision="android-6.0" />
<project path="kernel/samsung/msm8226" name="kernel_samsung_msm8226" remote="MSM8226-Samsung" revision="common" />
<project path="device/samsung/msm8226-common" name="android_device_samsung_msm8226-common" remote="MSM8226-Samsung" revision="cm-13.0" />
<project path="hardware/qcom/audio" name="android_hardware_qcom_audio" remote="MSM8226-Samsung" revision="cm-13.0" />
<project path="device/samsung/ms01-common" name="android_device_samsung_ms01-common" remote="MSM8226-Samsung" revision="cm-13.0" />
<project path="kernel/samsung/ms013g" name="android_kernel_samsung_ms013g" remote="MSM8226-Samsung" revision="cm-13.0" />
<project path="device/samsung/ms013g" name="android_device_samsung_ms013g" remote="MSM8226-Samsung" revision="cm-13.0" />
<project path="vendor/samsung/ms013g" name="android_vendor_samsung_ms013g" remote="MSM8226-Samsung" revision="cm-13.0" />
<project path="kernel/samsung/ms01lte" name="android_kernel_samsung_ms01lte" remote="MSM8226-Samsung" revision="cm-13.0" />
<project path="device/samsung/ms01lte" name="android_device_samsung_ms01lte" remote="MSM8226-Samsung" revision="cm-13.0" />
</manifest>

I'm using the default toolchains for compiling LineageOS 13.0, e.g. :

repo init -u https://github.com/LineageOS/android.git -b cm-13.0
repo sync
[Galaxy Grand 2 Q&A, Help & Troubleshooting] yumi14:
Hi,

I have successfuly built a LineageOS 13.0 but when trying to flash it, it hangs at "Patching system image unconditionally...".

Does someone know how to debug the installation procedure ?
[Galaxy Grand 2 Q&A, Help & Troubleshooting] Subhashis:
Check the zip file.It generally happens for corrupted zips. It happened once for me too.
[Galaxy Grand 2 Q&A, Help & Troubleshooting] Subhashis:
I was using linaro toolchain and had downloaded only android_kernel_samsung_ms013g not vendor,device,etc.I was using this guide:

https://xdaforums.com/showthread.php?t=2152819

Let me download all the files(might take a month due to slow internet speed) and post the result :/ .BTW if you have any suggestions for me,then you are welcome ;)
[Galaxy Grand 2 Q&A, Help & Troubleshooting] yumi14:
Unfortunatly for you, I won't be of much help for the moment, I'm pretty new to Kernel/Android stuff.

Good news, I was able to build Kernel + Recovery + LineageOS 13.0 and Flash everything to my phone, now I'll test functionnalities.
[Android Software Development] :
3. The device.mk

Let's now talk about the device.mk​

# Note: this is an example. This is uncomplete

# Include layers
DEVICE_PACKAGE_OVERLAYS += device/samsung/a3xeltexx/overlay

# Define screen size for prebuilt apps
PRODUCT_AAPT_CONFIG := xlarge
PRODUCT_AAPT_PREF_CONFIG := xhdpi
PRODUCT_AAPT_PREBUILT_DPI := hdpi mdpi

# Use dtbhtoolExynos to build dt.img
PRODUCT_PACKAGES += \
dtbhtoolExynos

# Screen size for boot animation
TARGET_SCREEN_HEIGHT := 1280
TARGET_SCREEN_WIDTH := 720

# Copying audio files
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/configs/audio/audio_policy.conf:system/etc/audio_policy.conf \
$(LOCAL_PATH)/configs/audio/mixer_paths.xml:system/etc/mixer_paths.xml

# Copying bluetooth files
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/bluetooth/bt_vendor.conf:system/etc/bluetooth/bt_vendor.conf

# Copying GPS config files
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/configs/gps/gps.conf:system/etc/gps.conf \
$(LOCAL_PATH)/configs/gps/gps.xml:system/etc/gps.xml

# Advertise we support theres features
PRODUCT_COPY_FILES += \
frameworks/native/data/etc/android.hardware.ethernet.xml:system/etc/permissions/android.hardware.ethernet.xml \
frameworks/native/data/etc/android.hardware.sensor.compass.xml:system/etc/permissions/android.hardware.sensor.compass.xml \
frameworks/native/data/etc/android.hardware.sensor.gyroscope.xml:system/etc/permissions/android.hardware.sensor.gyroscope.xml \
frameworks/native/data/etc/android.hardware.sensor.heartrate.xml:system/etc/permissions/android.hardware.sensor.heartrate.xml \
frameworks/native/data/etc/android.hardware.sensor.light.xml:system/etc/permissions/android.hardware.sensor.light.xml \
frameworks/native/data/etc/android.hardware.sensor.stepcounter.xml:system/etc/permissions/android.hardware.sensor.stepcounter.xml \
frameworks/native/data/etc/android.hardware.sensor.stepdetector.xml:system/etc/permissions/android.hardware.sensor.stepdetector.xml \
frameworks/native/data/etc/android.hardware.nfc.xml:system/etc/permissions/android.hardware.nfc.xml \
frameworks/native/data/etc/android.hardware.nfc.hce.xml:system/etc/permissions/android.hardware.nfc.hce.xml \
frameworks/native/data/etc/com.android.nfc_extras.xml:system/etc/permissions/com.android.nfc_extras.xml

# Include our GPS shim
PRODUCT_PACKAGES += \
libshim_gpsd

# Include our edited ramdisk
PRODUCT_PACKAGES += \
fstab.samsungexynos7580 \
init.baseband.rc \
init.samsung.rc \
init.samsungexynos7580.rc \
init.samsungexynos7580.usb.rc \
init.wifi.rc \
ueventd.samsungexynos7580.rc \
init.battery.rc

5. Details

Well, it's finished.

There is so much things to explain, and i maybe didn't explained well.

I really recommend you to check and look device-trees on GitHub.

Also, i didn't explained how to fill include, etc...

For that part, i recommend you to use a device-tree near from your device, you copy it, then you adapt it to your device (change codename, manufacturer, screen size, CPU, etc....)

Making a device-tree is a lot of copy from other device-tree, github commits, etc...

Hope you enjoy this tutorial.

Feel free to post any question, i'll answer to all!
[Android Software Development] McFy:
Thanks for this awesome guide ! Some good reading for those who want learn android development like me ;)
[Android Software Development] NetfariousIntent:
F a b u l o u s ( ͡° ͜ʖ ͡°)
[Android Software Development] ●CaloMarzi●:
Nice guide Kmx! You are the best:cool:
[Android Software Development] xEmre66:
Thanks for that great guide kmx!
[Android Software Development] CStadler:
Great and very usefull guide thanks, something for me and others to try and learn more, and hopefully succeed
[Android Software Development] ankk98:
The guide i was looking for :)

nice work !
[Android Software Development] ATechnoHazard:
Pretty useful, but it really doesn't cover on how to extract a skeleton tree from the device itself; for example a new device without any similar devices would need a basic skeleton. If you'd cover those things, it would make you guide that much greater, thanks! :)
[Android Software Development] androj:
Is it possible to modify the screen xdpi and ydpi values via the device tree (directly or indirectly)?

I am trying to fix those values for a custom rom and can't find any information about how to change those values or what other values are used to calculate them.
[Android Software Development] :
[deleted] (bugged http duplicate)
[Android Software Development] :
Honestly I don't know, maybe you search for this :

ro.sf.lcd_density in system.prop
[Android Software Development] ahmed gamal 1m:
Can you see my device tree & vendor tree

I made it myself

https://drive.google.com/file/d/1-fu4flbMzrwZCrXll6E7aT8mpqTfOXLh/view?usp=drivesdk

https://drive.google.com/file/d/10p8xxul_9wiUl8B1OShYRG9aX5iif7xV/view?usp=drivesdk
[Android Software Development] :
Could you use Git instead?

It will make your life really easier
[Android Software Development] The_Akki:
Thx for this tutorial. :)
[Android Software Development] RipCityBassWorks:
Hey, I am attempting to port lineagos 14.1 to the Samsung Galaxy D710, but I am struggling to get the modified i9100 device tree I assembled recognized during breakfast. I have a local manifest (roomservice.xml) that links all of the repos I'm using (and this works, everything syncs properly when I use repo sync).

But when I try

breakfast d710

I get the error

** Don't have a product spec for: 'lineage_d710'

** Do you have the right repo manifest?

I am a total noob at this, but is there any way I can get my custom device tree recognized?

Here is the git link: https://github.com/RipCityBassWorks/android_device_samsung_d710
[Android Software Development] ajituchiha:
deleted
[Android Software Development] ajituchiha:
where can I find all the files for sepolicy ?
[Android Software Development] letolkki:
related to this: I can see using PRODUCT_COPY_FILES to stage files to the root directory. but where is the directory structure created? Such as /firmware ... etc? I am trying to add a directory to the root fs. When I just create a new directory such as /foo the build fails. I want the new directory to be permanent part of the build process so solutions like unpack - modify - repack is less than satisfactory. Thanks
[Android Software Development] Ippfcox:
The index should be 4? isn't it:o

---------- Post added at 10:48 AM ---------- Previous post was at 10:23 AM ----------

Thanks for your great guide, I find that there are many diffierent variables in the example *.mk from the variables in my phone's device-tree. So I want to know if there are any way to query the unknown variables? is there wiki or doc? Thanks!
[Android Software Development] ahmed gamal 1m:
Can you see my device tree

Device tree :: https://github.com/ahmedgamal17/android_device_samsung_j1pop3g

I've made it from other phone

But I can't modify power_profile.xml to make it compatible with my phone
[Android Software Development] zhengqiming:
Thanks for this guide, However, I always have no idea about these issues. Could you answer them? I would be very much appreciated. (Sorry for my bad english)

1.How to learn? What needs to be learned? Should I start learning from old android version? Are there any good document about this?

2.How to get logs from Bootloop(maybe Kernel panic)? How to know what files is proprietary? How to know what should write in device makefiles? Is it still able to use prebuilt kernel for now? What should be done for upgrade android version(for example, is it necessary to reverse-enginnering proprietary blobs?)
[Android Software Development] chriz:
Could u tell how to upgrade nougat trees to oreo
[Android Software Development] vdhero:
Thank you very much for this great guide, I'm trying to make my own tree for Galaxy S2 variants with NFC but I have no idea how to add NFC to the tree. Could you help me, please?
[Android Software Development] bassbounce:
How add your selfmade device tree in to a rom source to compile lineage by example? Or do we need additional files from the kernel source provided by the manufacturer?
[Android Software Development] bigsupersquid:
If you can get kernel source that's great, but if not, you have to use the prebuilt kernel and modules (and dtb for newer devices than I learned on a ways back)

Test it by building a recovery like

TWRP

Recovery is way easier to boot and debug than a whole ROM.

Once you have a working recovery then you can start building a ROM.

But do your due diligence and research well before asking questions there in the TWRP thread, or you'll be ignored (or made fun of.)
[Android Software Development] krishV:
I need to upgrade mi max hydrogen tree

Sir please can you tell how to upgrade the device tree to pie
[Android Software Development] saksham_033:
Any help on a/b device tree?
[Android Software Development] weedboi6969:
Any way to get the AOSP build system build the kernel? Because otherwise I would get this error:

ninja: error: 'out/target/product/codename/kernel', needed by 'out/target/product/codename/boot.img', missing and no known rule to make it
[Android Software Development] drshaggh:
Hey, the makefile lineage.mk should be named dependent on the base Rom as is said in the guide, if however the base rom is aosp, what should this makfile be called? Thanks
[Android Software Development] anshumanxda:
aosp.mk or aosp_devicecodename.mk
[Android Software Development] dandyfarid:
nice guide thanks :D
[Android Software Development] AnantaSrikar:
So how do we get the necessary files for a device which doesn't have any source code?
[Android Software Development] Sands207:
I am also wondering the same thing
[Android Software Development] AnantaSrikar:
Is there any way?
[Android Software Development] SnowFuhrer:
It's the law to have source code. I don't know much about this kind of stuff, but you would probably have to write it from scratch.
[Android Software Development] senseijtitus:
Hi there. I need a help. I am trying to extract device tree from the source code file I got for Samsung galaxy a 70. I am new to rom development. So I need to know how to extract the device tree from the 2 .gz files I've got in the source code file.

There are kernel.gz and device.gz files. I've extracted both to their respective folders. Now I need to get the device tree. How can I do this?
[Android Software Development] Sands207:
Have you tried using dtc (device tree compiler)?
[Android Software Development] senseijtitus:
Not yet. Do I need to make any changes in the folder structure of the device source that I have extracted from the source code zip?
[Android Software Development] Sands207:
That I'm not sure of, i already had a device tree available to use for my current device. I do know that you will need a stock boot.img built and extracted to use it. I would look it up on github for a clearer explanation
[Android Software Development] senseijtitus:
Thank you very much buddy. Appreciate the assistance. Looking forward for your guidance..
[Android Software Development] Hannibal Smith:
sorry wrong post
[Tilt, TyTN II, MDA Vario III General] tai4de2:
Folks,

(I've searched around a bit and seen some reference to this problem but no definitive discussion. I apologize in advance if I missed anything and humbly request a pointer to the existing info if so.)

Just got a Tilt last weekend. On 3 occasions so far I looked at the screen and noticed that the phone had no signal (triangle with ! next to it). So for several hours each time, no one could call me. Going into comm mgr, the phone radio was still on.

This was in an area with no signal problems; soft reset or pulsing the phone radio in comm mgr would restore functionality with 3-4 bars. I finally nailed this down to having been in an area in the center of the building where I work, where signal gets lost. It appears that my Tilt never automatically recovers from a lost signal.

I saw this problem on the ROMs that came with the device and now it also continues with the new one that was just released by HTC a couple of days ago. In case it matters the phone is unlocked (using jump_spl and the other related tools and procedures found here, thanks).

Do I just have a defective Tilt? I mentioned this to others in my office and a few folks also claim to see this, and like I said I have seen *some* mention of this on the internet... I'd be astounded if this were really a problem endemic to all Tilts -- would people really put up with this?

Anyone have any additional insight?
[Tilt, TyTN II, MDA Vario III General] met3ora:
It used to happen with me when I had the stock AT&T rom. I flashed the stock HTC rom and I don't recall ever having that problem, and now I've flashed SNE v2.5 and I don't have that problem.

My suggestion is to flash a new rom and see if that helps, and to make sure you're using a correct radio.
[Tilt, TyTN II, MDA Vario III General] wsabido168:
where do I get official htc radio and rom downloads?

hi folks,

where can i get official HTC radio and ROM downloads? I have an HTC TYTN II (acquired in Hong Kong) with ROM 1.56.721.3, Radio 1.27.12.11 & Protocol 22.45.88.07H just last month and already I'm encountering problems with the phone just losing the signal and staying lost and I'm considering upgrading however since my phone is brand new (practically), i want an "official" upgrade so as not to void the warranty. any help would be appreciated.

thanks and best regards...
[Tilt, TyTN II, MDA Vario III General] tai4de2:
I'll have to decide whether I have the cohones to flash an HTC ROM. Might at least be worth a try.
[Tilt, TyTN II, MDA Vario III General] moorekyl:
try this, go into comm manager, than settings for the phone (right soft key), than over to the Band tab, if I select the network type as GSM and leave the band on auto mine will contstantly serch for signal. i know this because my office is as close to a bomb shelter as they come and it never stops searching.

another good to this is battery life is improved

the BAD, if you want to use 3G you have to turn network back to auto and band to auto. not really a big deal cuz i dont have 3G here (yet).

a little workaround that works for me.
[Tilt, TyTN II, MDA Vario III General] tai4de2:
Thanks for that... I am running an AT&T ROM and even though I've supposedly turned on the Band tab in phone settings via KaiserTweak, I do not see a band tab. Should I?
[Tilt, TyTN II, MDA Vario III General] iservealot:
I have almost this same exact problem! As of two weeks ago, my tilt started not allowing me to make calls

I then realized that it was also sending all my calls to voice mail. Thing is, the phone says that I have signal and has the Edge connection sign at the top. Whenever I try to make a call, the phone says "operation cannot be completed" or it will simply beep at me as if the call ended, right after it started.

A soft reset allows this to work. I've had this problem even happen right after hanging up with someone, and then trying to redial another number 5 seconds later. I doubt the phone really lost the signal.

Any ideas?
[Tilt, TyTN II, MDA Vario III General] Jasse:
Hello

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

Thanks
[Tilt, TyTN II, MDA Vario III General] ianhunt:
I had the same problem with my O2 XDA Stellar, it was fine for a couple of months, then I could hardly call out on it, email wouldn't send, could rarely go online etc etc. It seemed to be better on GSM/GPRS than 3G, HSDPA etc. I assumed it was a harware problem & as it was under warranty I got a replacement from O2 & it's been fine so far.
[Tilt, TyTN II, MDA Vario III General] tai4de2:
AT&T replaced the SIM card in my phone and I believe this has fixed the problem. I have lost signal many times (elevators, garages, etc) and it recovers each time.