Develop Bugs

[Q&A] [ROM][AOSP][Nightly/Release] CarbonRom KitKat [Hercules]

Q&A for [ROM][AOSP][Nightly/Release] CarbonRom KitKat [Hercules]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][AOSP][Nightly/Release] CarbonRom KitKat [Hercules]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

No Audio On Phone Calls
The audio for phone calls don't work on this rom. I am running the most current version along with Wild Kernel #12. Anyone care to help?

Need help i'm having the boot loop with KitKat kernels .I told about this issue to Sultan XDA ..and he replied as
Tell those kernel devs to fix their keypad driver:
[ 109.012786] Unable to handle kernel NULL pointer dereference at virtual address 0000001c
[ 109.012969] pgd = d5f14000
[ 109.013061] [0000001c] *pgd=5594e831, *pte=00000000, *ppte=00000000
[ 109.013458] Internal error: Oops: 17 [#1] PREEMPT SMP
[ 109.013580] Modules linked in: dhd vibrator frandom
[ 109.013977] CPU: 1 Not tainted (3.0.101-stock++ #1)
[ 109.014099] PC is at sec_keypad_enable_show+0x10/0x24.
[ 109.014282] LR is at dev_attr_show+0x1c/0x48...so find my problem here: http://forum.xda-developers.com/gal...t-4-3-roms-t2999362/post58093351#post58093351
I askes for a fix and he replied :
Your keypad hardware is slow to initialize at boot:
[ * *1.250640] [TKEY] get_touchkey_firmware F/W version: 0x0, Module version:0x0
[ * *1.250762] f/w read fail retry 6
[ * *1.250946] EXT_I2C No ACK
So some of the data structs in the keypad driver remain in a null state until keypad probe can complete. Some of that data is accessed before keypad probe on your specific device can finish (so it is dereferencing null data), thus crashing the kernel. It's being caused by the keypad-disabler feature, which my kernel does not have. Sorry, but I'm not really interested in fixing other people's kernels, so I can't help you with that..... Can u fix this for me plzz!!

[Q&A] [ROM][UNOFFICIAL][5.1.1_r13]BlissPop 3.9 by Team Bliss UBERTC 4.9 19/08/2015

[Q&A] [ROM][UNOFFICIAL][5.1.1_r13]BlissPop 3.9 by Team Bliss UBERTC 4.9 19/08/2015
Q&A for [ROM][UNOFFICIAL][5.1.1_r13]BlissPop 3.9 by Team Bliss UBERTC 4.9 19/08/2015
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][UNOFFICIAL][5.1.1_r13]BlissPop 3.9 by Team Bliss UBERTC 4.9 19/08/2015. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

it has s2w?

Great work muucho gracias
, y'a it's has s2w on kernel setting
can't turn on wifi after soft reboot :
E/WifiMonitor( 9156): killSupplicant p2ptrue init.svc.wpa_supplicant=unknown ini
t.svc.p2p_supplicant=unknown
E/WifiHW ( 9156): failed to translate ifname to idx
E/WifiHW ( 9156): could not remove P2P interface: -19
E/WifiHW ( 9156): Wi-Fi - could not remove p2p interface
D/WifiMonitor( 9156): startMonitoring(wlan0) with mConnected = false
E/WifiHW ( 9156): Unable to open connection to supplicant on "@android:wpa_": N
o such file or directory
after a normal reboot it's work

Super Rome so far!
I have only one problem, my email with k9 not be retrieved automatically with Pusch

It is possible to activate Double Tap2wake?
Gesendet von meinem One X mit Tapatalk

Where can I find the "sswap" utility?

Sorry if this is posted in the wrong forum. XDA's brain-damaged posting policy doesn't allow me to post in the development section.
Moderator Edit: Definitely in the wrong Forum, you're right. Should have been in Q and A... which it now is. This Post will help you understand the XDA stance on posting in Development
I've been scratching my head trying to figure out the location and purpose of a mysterious file introduced in recent Cyanogenmod builds for the Samsung Galaxy Tab S 8.4 (klimtwifi).
The file is sswap. The file is referenced in at least two files within the Cyanogenmod build directory, i.e.:
Code:
device/samsung/klimtwifi/proprietary-files.txt
device/samsung/klimtwifi/rootdir/etc/init.universal5420.rc
In proprietary-files.txt we see the following lines:
Code:
# Samsung SSWAP
root/sbin/sswap
Basically, proprietary-files.txt is the list of files that the extract-files.sh script uses to download the prebuilt binary-only vendor files (without source code) from a working Cyanogenmod installation. This appears to place the file within the /system directory. At least this is my understanding of how the extract-files.sh script works, i.e. it takes the relative paths found in proprietary-files.txt and appends the base path /system.
Code:
if [ "$SRC" = "adb" ]; then
adb pull /system/$FILE $BASE/$DEST
# if file dot not exist try destination
if [ "$?" != "0" ]
then
adb pull /system/$DEST $BASE/$DEST
fi
However the reference to sswap in init.universal5420.rc puts it in a different location:
Code:
service sswap /sbin/sswap -s
class core
user root
group root
oneshot
seclabel u:r:sswap:s0
I can only assume that sswap is hardlinked or softlinked to or from the /system directory. However, this kind of defeats the
purpose of /sbin being assigned root-only read permissions.
Finally, I've not been able to find any documentation with regard to sswap, particularly what its advantages or disadvantages are when compared to the standard Linux swapon/swapoff utility.

DisposableName said:
Sorry if this is posted in the wrong forum. XDA's brain-damaged posting policy doesn't allow me to post in the development section.
Moderator Edit: Definitely in the wrong Forum, you're right. Should have been in Q and A... which it now is. This Post will help you understand the XDA stance on posting in Development
I've been scratching my head trying to figure out the location and purpose of a mysterious file introduced in recent Cyanogenmod builds for the Samsung Galaxy Tab S 8.4 (klimtwifi).
The file is sswap. The file is referenced in at least two files within the Cyanogenmod build directory, i.e.:
Code:
device/samsung/klimtwifi/proprietary-files.txt
device/samsung/klimtwifi/rootdir/etc/init.universal5420.rc
In proprietary-files.txt we see the following lines:
Code:
# Samsung SSWAP
root/sbin/sswap
Basically, proprietary-files.txt is the list of files that the extract-files.sh script uses to download the prebuilt binary-only vendor files (without source code) from a working Cyanogenmod installation. This appears to place the file within the /system directory. At least this is my understanding of how the extract-files.sh script works, i.e. it takes the relative paths found in proprietary-files.txt and appends the base path /system.
Code:
if [ "$SRC" = "adb" ]; then
adb pull /system/$FILE $BASE/$DEST
# if file dot not exist try destination
if [ "$?" != "0" ]
then
adb pull /system/$DEST $BASE/$DEST
fi
However the reference to sswap in init.universal5420.rc puts it in a different location:
Code:
service sswap /sbin/sswap -s
class core
user root
group root
oneshot
seclabel u:r:sswap:s0
I can only assume that sswap is hardlinked or softlinked to or from the /system directory. However, this kind of defeats the
purpose of /sbin being assigned root-only read permissions.
Finally, I've not been able to find any documentation with regard to sswap, particularly what its advantages or disadvantages are when compared to the standard Linux swapon/swapoff utility.
Click to expand...
Click to collapse
When I put together the prop* there was no option to get files from the roms ramdisk (extract-files.sh assumes all needed files reside in /system/. sswap lives in /sbin/ and should be in /sbin for the source build rom, too. If you look here:
https://github.com/TheMuppets/propr...-common/exynos5420-common-vendor-blobs.mk#L25
...you'll see that sswap is copied to /root/sbin. In /root the android build environment assambles the ramdisk.
You can use mkswap on the swap partition and go ahead with swapon and swapoff. This will work. But since I havn't found any documentation of samsungs sswap partition format, I decided to use samsungs sswap instead of standard linux kernel swap interface: I have no idea hpw to "mkswap" for sswap. If you use mkswap and swapon be prepared to have a hard time to get back to sammy tw.

Trying to build lineageos 18.1 for one plus one

Hi guys!
So I was following this https://wiki.lineageos.org/devices/bacon/build wiki to build a lineageos 18.1 ROM for my one plus one.
Unfortunately, when I get to the step for "breakfast bacon", I get the following errors.
In file included from build/make/core/config.mk:291:
In file included from build/make/core/envsetup.mk:266:
build/make/target/product/product_launched_with_k.mk:2: error: _nic.PRODUCTS.[[device/oneplus/bacon/lineage_bacon.mk]]: "device/oppo/msm8974-common/msm8974.mk" does not exist.
22:35:04 dumpvars failed with: exit status 1
Device bacon not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_oneplus_bacon
Default revision: lineage-18.1
Checking branch info
Checking if device/oneplus/bacon is fetched from android_device_oneplus_bacon
LineageOS/android_device_oneplus_bacon already fetched to device/oneplus/bacon
Syncing repository to retrieve project.
sh: 1: repo: not found
Repository synced!
Looking for dependencies in device/oneplus/bacon
Looking for dependencies in device/oppo/msm8974-common
device/oppo/msm8974-common has no additional dependencies.
Looking for dependencies in kernel/oppo/msm8974
kernel/oppo/msm8974 has no additional dependencies.
Done
In file included from build/make/core/config.mk:291:
In file included from build/make/core/envsetup.mk:266:
build/make/target/product/product_launched_with_k.mk:2: error: _nic.PRODUCTS.[[device/oneplus/bacon/lineage_bacon.mk]]: "device/oppo/msm8974-common/msm8974.mk" does not exist.
22:35:05 dumpvars failed with: exit status 1
In file included from build/make/core/config.mk:291:
In file included from build/make/core/envsetup.mk:266:
build/make/target/product/product_launched_with_k.mk:2: error: _nic.PRODUCTS.[[device/oneplus/bacon/lineage_bacon.mk]]: "device/oppo/msm8974-common/msm8974.mk" does not exist.
22:35:06 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_bacon'
** Do you have the right repo manifest?
Click to expand...
Click to collapse
What am I doing wrong?
p.s. if I do a "breakfast d855", then I get no error.

My utter apologies for being so blind.
It is of course clearly written on that wiki that some devices would fail upon "breakfast" command being called due to the missing vendor files.
Hence one should first run "extract-files.sh" in the device specific folder. And indeed afterwards the breakfast command succeeds for "bacon".
I could be given a little margin for being a noob and also that my other device "d855" does not need extract-files.sh before breakfast.
Also what confused me yesterday was, that the paths contained oppo when infact I was building for bacon. I was sure something is wrong upstream.
My sincere apologies again for starting on xda with such a useless post.

no member named 'asInterface' in 'android::IGraphicBufferProducer'

Hello, I'm trying to build android 9/lineageos 16.0 and I'm encountering the following error:
Code:
frameworks/native/libs/binder/include/binder/IInterface.h:44:23: error: no member named 'asInterface' in 'android::IGraphicBufferProducer'
return INTERFACE::asInterface(obj);
~~~~~~~~~~~^
Link to the full log: https://pastebin.com/2p3d5br1
Any help is appreciated.