yashsingh1/xdaforums huggingface dataset:
[Huawei Ascend P7] Iv4n_1976:
Before start to build 14.1

I want to be sure to use your last source over 13.0

So i want to know after fork your kernel what is the right kernel branch

GitHub - WinSSitaly/hwp6s-kernel: Huawei Ascend P6S-U06 KitKat/Lollipop/LOS13.0 kernel

Huawei Ascend P6S-U06 KitKat/Lollipop/LOS13.0 kernel - WinSSitaly/hwp6s-kernel

github.com

13 13.0 13.0new .....

<project path="kernel/hwp6s-kernel" name="WinSSitaly/hwp6s-kernel.git" remote="github" revision="linux-3.0.101-hwp6s-android" />

i will have error

In file included from frameworks/native/libs/ui/Rect.cpp:17:

device/huawei/hi6620oem-common/include/system/graphics.h:492:4: error: unknown command tag name 'num'; did you mean 'enum'? [-Werror,-Wdocumentation-unknown-command]

* @num_points is the number of points in the list

^~~~~~~~~~~

enum

device/huawei/hi6620oem-common/include/system/graphics.h:494:4: error: unknown command tag name [-Werror,-Wdocumentation-unknown-command]

* @xyz_points is the flexible array of floating-point values.

^

device/huawei/hi6620oem-common/include/system/graphics.h:519:11: error: flexible array members are a C99 feature [-Werror,-Wc99-extensions]

float xyzc_points[];

^

3 errors generated.

make: *** [build/core/binary.mk:730: /home/ivan/Esperimenti/los13/out/los13/target/product/p7_l10/obj/SHARED_LIBRARIES/libui_intermediates/Rect.o] Error 1

#### make failed to build some targets (50:01 (mm:ss)) ####
[Huawei Ascend P7] threader:
linux-3.0.101-hwp6s-android isn't quite working yet. Actually working on that kernel now, i've just made mach-goldfish compile so it can be tested in qemu/android emulator for debugging. the cm-13.0-0 branch is what i used last time.

I see an uncommited change to device/huawei/hi6620oem-common/include/system/graphics.h

the double ** is the problem on line 480. if you remove the second * it works . I'll commit that change now.
[Huawei Ascend P7] Iv4n_1976:
On monday i will change kernel and resync device
[Huawei Ascend P7] threader:
We've got till 2038 to figure stuff out and port to a HIKEY kernel or follow Linux main until the UNIX time problem fixed, the drivers for the device will be a huge problem just jumping a few kernel versions, but If i believe 3.4 at lest should work. I'm trying to boot my re-implementation in qemu now, if i can remember the proper command.. I thought I had posted it in another post regarding a MSM kernel but noooo. Also fixed compiling the Versatile platform, so hopefully it will give some useful output soon, I pushed the changes to the linux-3.0.101-hwp6s-android branch, but initial results are discouraging if the qemu command i gave is correct i will need to attach GDB and debug an 'early boot' problem which isn't fun at all and something I needed to do with arm32 for a MSM kernel I've been working on and off on for quite some time, merging in the latest CAF/code linaro changes to a Sony Z1 to Z5 kernel. I spent a month working my ass off trying to port the Huawei stuff to a pure linux-3.0.101 so I wont give up, easily.
[Huawei Ascend P7] threader:
I'm playing around with optimization, https://github.com/threader/hwp6s-kernel/commit/5850cba817e84d1068a1a38c67dc4b045f8b21f8 mainly this, https://github.com/threader/hwp6s-kernel/commit/8c8169cf170a1bf836de3e9d53ae953e949d414f , It's hard to say if there is any improvement at all, from the benchmarks I've ran the gains seem minimal, but not I've tested much as I'm running out of time for a while, i also found the cm-13.0-0 Android.mk to be quite incorrect when it comes to compiler, i fixed this in the cm-13.0-0-memcopy branch but forgot to apply it to 13.0-0, I've tried to set it so it just works if a custom compiler is set via TARGET_KERNEL_CROSS_COMPILE_PREFIX in boardconfig.mk or not, I will change from _PREFIX to the correct variable when I'm back and have time agian. Also , pay attention when compiling drivers/hisi/ , there are comments causing issues. i just got a compiler warning from inside a comment , I've removed quite a few comments from drivers/hisi/modem prior. Since the wifi router is WPA2/3 i don't have wlan even, i think there I've read of a fix regarding the frame size or something.
[Huawei Ascend P7] Iv4n_1976:
how to solve it:?

Installing recovery patch to system partition

Warning: could not find SYSTEM/build.prop in <built-in function zip>

using prebuilt recovery.img from BOOTABLE_IMAGES...

using prebuilt boot.img from BOOTABLE_IMAGES...

Traceback (most recent call last):

File "./build/tools/releasetools/make_recovery_patch", line 55, in <module>

main(sys.argv[1:])

File "./build/tools/releasetools/make_recovery_patch", line 51, in main

common.MakeRecoveryPatch(input_dir, output_sink, recovery_img, boot_img)

File "/home/ivan/Esperimenti/los13/build/tools/releasetools/common.py", line 1537, in MakeRecoveryPatch

_, _, patch = d.ComputePatch()

File "/home/ivan/Esperimenti/los13/build/tools/releasetools/common.py", line 1222, in ComputePatch

p = Run(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE)

File "/home/ivan/Esperimenti/los13/build/tools/releasetools/common.py", line 100, in Run

return subprocess.Popen(args, **kwargs)

File "/usr/lib/python2.7/subprocess.py", line 394, in __init__

errread, errwrite)

File "/usr/lib/python2.7/subprocess.py", line 1047, in _execute_child

raise child_exception

OSError: [Errno 2] No such file or directory

make: *** [build/core/Makefile:1102: /home/ivan/Esperimenti/los13/out/target/product/p7_l10/system/bin/install-recovery.sh] Error 1

#### make failed to build some targets (11:02 (mm:ss)) ####
[Huawei Ascend P7] Iv4n_1976:
Maybe is my repsitory to create recovery broken?
[Huawei Ascend P7] Iv4n_1976:
my .repo/local has this

P7_l10.xml

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

<manifest>

<project path="device/huawei/hi6620oem-common" name="WinSSitaly/android_device_huawei_hi6620oem-common.git" remote="github" revision="cm-13.0" />

<project path="device/huawei/p6s_u06" name="WinSSitaly/android_device_huawei_p6s_u06.git" remote="github" revision="cm-13.0" />

<project path="device/huawei/p7_l10" name="WinSSitaly/android_device_huawei_p7_l10.git" remote="github" revision="cm-13.0" />

<project path="vendor/huawei/hi6620oem-common" name="WinSSitaly/android_vendor_huawei_hi6620oem-common.git" remote="github" revision="cm-13.0" />

<!-- project path="kernel/hwp6s-kernel" name="WinSSitaly/hwp6s-kernel.git" remote="github" revision="cm-13.0" / -->

<!-- project path="hardware/huawei/hi6620oem" name="WinSSitaly/android_hardware_huawei_hi6620oem.git" remote="github" revision="cm-13.0" / -->

<!-- project path="kernel/hwp6s-kernel" name="WinSSitaly/hwp6s-kernel.git" remote="github" revision="cm-13.0-0-memcopy" /-->

<project path="kernel/hwp6s-kernel" name="WinSSitaly/hwp6s-kernel.git" remote="github" revision="cm-13.0" />

<!--project path="bootable/recovery-twrp" name="WinSSitaly/android_bootable_recovery.git" remote="github" revision="lineage-13-hwp6s" /-->

</manifest>

TWRP.xml

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

<manifest>

<remote name="TeamWin"

fetch="https://github.com/TeamWin"

review="https://gerrit.twrp.me" />

<remote name="omnirom"

fetch="https://github.com/omnirom"

review="https://gerrit.omnirom.org" />

<!-- TWRP lives in TeamWin repo -->

<project path="bootable/recovery-twrp" name="android_bootable_recovery" remote="TeamWin" revision="android-6.0" />

<!-- TWRP busybox lives in omnirom repo -->

<!-- project name="android_external_busybox" path="external/busybox" remote="omnirom" revision="android-7.1" / -->

<project name="LineageOS/android_external_busybox" path="external/busybox" revision="cm-13.0" />

<!-- Include Magisk repo for resetprop support -->

<!-- <project path="external/magisk-prebuilt" name="external_magisk-prebuilt" remote="TeamWin" revision="android-7.1" / -->

<project path="external/magisk-prebuilt" name="external_magisk-prebuilt" remote="TeamWin" revision="android-6.0" />

<!-- Include forked external unzip repo from CyanogenMod for toolbox/toybox support -->

<!-- project path="external/unzip" name="android_external_unzip" remote="TeamWin" revision="cm-14.1" / -->

<!-- Include external zip repo for zip support -->

<!-- project path="external/zip" name="android_external_zip" remote="TeamWin" revision="android-7.1" / -->

<!-- Include external repos for bash & nano -->

<!-- project name="LineageOS/android_external_bash" path="external/bash" / -->

<!-- project name="LineageOS/android_external_nano" path="external/nano" / -->

<!-- project name="LineageOS/android_external_libncurses" path="external/libncurses" / -->

</manifest>
[Huawei Ascend P7] Iv4n_1976:
may u let me know if is similar to yours? or may share yours

thanks
[Huawei Ascend P7] Igi54:
Thank you for that. I have tested it. Unfortunately it is quite slower then the lasts Kostyan kernel. Even sometimes there are error messages like "operation takes too much time" and so on.

EDIT: maybe it is due to I still use last Kostyan FW..
[Huawei Ascend P7] threader:
None of that happens here. I would need to test this ofc. I thought about creating a new release of the old fw by just hacking the boot.img in there. Thanks for the tip, sorry I didn't see it sooner.
[Huawei Ascend P7] threader:
That is pretty much what I do yes.
[Huawei Ascend P7] threader:
I'd use the stock recovery to begin with. But I think at least twrp for 7.1 works out of the box, I spent a lot of time making TWRP live alongside Los 17.1 and in the end something was still wrong and if I correct it the build system breaks. Great for experience tho I realize there is something I don't understand when making changes like that as the same happened to an optimized libc routine
[Huawei Ascend P7] whiteindian:
@Igi54

Quoted form @Kostyan_nsk thread

So you need OTG cable and install i.e. Simple Keyboard from Play Store

@threader I did backup via TWRP, do I get back to stock with these backups? What about unlocked bootloader?

Still it boots up about 120 seconds, and something (GAPPS?) drains faster the battery...
[Huawei Ascend P7] schwienernitzel:
Hi, how did you resolve these jack server errors during LOS13 build?

ERROR: Communication error with Jack server (2)
make: *** [build/core/prebuilt_internal.mk:324: /home/schwiener/android/CM13/out/target/common/obj/JAVA_LIBRARIES/sdk_v18_intermediates/classes.jack] Error 255
curl: option --no-proxy: used '--no-' for option that isn't a boolean
curl: try 'curl --help' or 'curl --manual' for more information
curl: option --no-proxy: used '--no-' for option that isn't a boolean
curl: try 'curl --help' or 'curl --manual' for more information
curl: option --no-proxy: used '--no-' for option that isn't a boolean
curl: try 'curl --help' or 'curl --manual' for more information
ERROR: Communication error with Jack server (2)
make: *** [build/core/prebuilt_internal.mk:324: /home/schwiener/android/CM13/out/target/common/obj/JAVA_LIBRARIES/sdk_v19_intermediates/classes.jack] Error 255
curl: option --no-proxy: used '--no-' for option that isn't a boolean
curl: try 'curl --help' or 'curl --manual' for more information
curl: option --no-proxy: used '--no-' for option that isn't a boolean
curl: try 'curl --help' or 'curl --manual' for more information
curl: option --no-proxy: used '--no-' for option that isn't a boolean
curl: try 'curl --help' or 'curl --manual' for more information
curl: option --no-proxy: used '--no-' for option that isn't a boolean
curl: try 'curl --help' or 'curl --manual' for more information
ERROR: Communication error with Jack server (2)
make: *** [build/core/prebuilt_internal.mk:324: /home/schwiener/android/CM13/out/target/common/obj/JAVA_LIBRARIES/sdk_v20_intermediates/classes.jack] Error 255
curl: option --no-proxy: used '--no-' for option that isn't a boolean
curl: try 'curl --help' or 'curl --manual' for more information
curl: option --no-proxy: used '--no-' for option that isn't a boolean
curl: try 'curl --help' or 'curl --manual' for more information
curl: option --no-proxy: used '--no-' for option that isn't a boolean
curl: try 'curl --help' or 'curl --manual' for more information
curl: option --no-proxy: used '--no-' for option that isn't a boolean
curl: try 'curl --help' or 'curl --manual' for more information
ERROR: Communication error with Jack server (2)

Thanks in advance...
[Huawei Ascend P7] schwienernitzel:
Edit: Fixed! ;)

If someone is interested, you have to apply these two patches:

1. Update jack-server

2. Fix the broken icu classes

Just apply them to your source and you are good to go. Works with CM13 / LOS13.
[OPPO Find X3 Pro] mr.obm:
I just got the Find X3 Pro yesterday and I'm loving it except do not disturb doesn't seem to be working.

I used clone phone to transfer from my OnePlus 8 Pro if that makes any difference?

Even when I enable DND manually it makes a notification sound and vibrates to let me know it's enabled 🤦‍♂️
[OPPO Find X3 Pro] seven_tech:
Having the same issue.

You can prevent individual app notifications making noise/vibration by going into the notification settings for that app and turning both Vibrate AND ringtone off.

But this means you have to do it for every app. And that's the whole point of DND mode. I think this might be an Oppo issue.
[Nexus 9 Q&A, Help & Troubleshooting] the_nanners:
EDIT: Managed to get fastboot back, all good.
[OnePlus 6 Questions & Answers] karenmcd:
Greetings,

I had lineageos 17 on my one+6 and after making a twrp backup and making sure i had all my files that i wanted i took the plunge and upgraded to lineage 18.

This would have been great except that I didnt actually have all the files I wanted. I critically forgot to make a manual separate backup of signal messenger. I need to get the history of signal messenger back. The only way i can think to do this, is to restore the twrp backup i made before upgrading and then making a backup with signal messenger app and then restoring the signal backup in lineage 18.

I attempted to restore my TWRP backup. When I made the TWRP backup I had checked ALL the boxes and saw no errors on the screen. When i attempted to restore i checked all the boxes on the screen and got what appears to be a fairly common error (255) when attempting to restore data (not sd/usb).

After, when i went to reboot twrp notified me that there was no OS installed. I rebooted anyway. I ended up stuck in a bootloader loop. I then downloaded

Then i unzipped that file and typed in the linux terminal:

I now have a working phone again.

I would like to know how do i restore the TWRP recovery image that I made at the beginning of the whole process. I'm pretty sure if I can do that I can then make a new Signal backup and be fine.

While doing lots of trouble shooting for the last 36 hours or so, it seems relevant to mention that my phone used to require I enter a PIN in order to use it, and I had to enter that same PIN in TWRP before I made the backup. The temporary OxygenOS I installed to just have a working phone number for work does not have a pin.
[OnePlus 6 Questions & Answers] adeklipse:
I have never had any success restoring TWRP backups so I eventually gave up relying on them after the 4th failed attempt.

But I distinctly remember reading this piece of advice:

0. Copy the TWRP backups onto a separate storage (I assume you have already done that)

1. Install the original ROM that is present in the backup; don't restore the System partition

2. Once installation has completed, restore only the Data partition and ignore all the rest such as cache, system, boot, etc.

3. Reboot

Personally, I have never tried it. But just from reading it, it seems like it may just work. Or it might not.
[OnePlus 6 Questions & Answers] karenmcd:
I appreciate the reply.

It's the data partition that's throwing this 255 error, which it seems to have something to do with it being encrypted i'd guess? In the future, is it possible to just dd the whole thing somehow?
[OnePlus 6 Questions & Answers] adeklipse:
Have you tried wiping the /data partition from TWRP's Advance Wipe?
[OnePlus 6 Questions & Answers] tiga016:
For what I know you need your device to be decrypted to restore from custom recovery.
[OnePlus 6 Questions & Answers] SMcC2:
I've had some luck in similar situations using Titanium Backup to extract an app and data from TWRP backup.

Your mileage may vary.
[iPAQ rw6828, XDA Atom General] malvechaitanya:
Guys I am using O2 Xda Atom (only) as a Gprs modem through a bluetooth connection.I want to connect and use Gprs through
[Google Pixel 4a 5G Questions & Answers] bubbyj:
I'm looking at the specs of the SN 765g that we have, versus the 768g thats available. From a hardware standpoint, it appears to be virtually the same identical setup. However, its big-big core run at 2.8ghz, and its small-BIG core runs at 2.4. Compared to 2.4 and 2.2 for our phone.

what would it take in the kernel to hijack our 765 and overclock it up to the 2.8 and 2.4ghz setup in the 768g?

And before anyone says -- don't overclock it, it'll overheat -- don't. I'm not asking if its practical, or for your permission. lol. I'm asking, is it possible?
[Google Pixel 4a 5G Questions & Answers] blackhawk:
If it can run at those frequencies... each individual chipset as it's own tolerance.

Factory specs define the set frequency well below the "weakest" chipset.

May work with some but not all. The chances of errors and data corruption will increase as you push the limits. At some point it will become unstable.

These chipsets may be more uniform with tighter tolerances so that the older overclocking methods don't succeed as well as they did with older the ones.

Heat sinking capacity is a secondary issue... you can't heat sink what you don't got.
[Treble-Enabled Device Questions and Answers] SteQu:
Would anyone present be kind enough to help me install and run GSI on a Google Pixel XL? It would be a dream come true! I will be very grateful for every tip and willingness to help.
[Treble-Enabled Device Questions and Answers] LR7875:
What shows in treble check app( search on Google play)?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ron_hyatt:
Hello everyone,

Did anyone with poco f3 experience screen dimming/low brightness with heavy gaming on custom (non miui) roms??

I know there is an update for official miui that may have fixed that but does this dimming issue occur with non miui roms as well?

Thanks:)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] checkered_bro:
Not occuring on my current rom (HentaiOS) however I believe MIUI have also fixed this
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Greenspoof:
The dimming is only here when I play genshin impact. My temporary solution is to play front of the fan when I play genshin lol. The Poco stay cold and no dimming. The time I get a cooling fan for phone
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ron_hyatt:
does this occur with custom (non miui) roms or only with miui stock?

did you find a fix for the proximity sensor issues??
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] wwb051221:
MIUI官方的解释是为了确保硬件温度过高时会受到限制的安全性。

----------

MOD EDIT: English Translation Below

MIUI's official explanation is to ensure the safety of restrictions when the hardware temperature is too high.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pl1992aw:
这里只能用英文写

G Translate:

The official explanation given by MIUI is to ensure hardware safety. When the temperature is too high, the brightness is limited.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] wwb051221:
Sorry
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] superyoyea666:
solution fix-

1.root

2. install themal sd 865 module via magisk

--- i test with One Os rom it work
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] superyoyea666:
themal865

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com

themal sd 865 module
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Greenspoof:
If the module delete thermal throttling, and so screen dimming, it's a bad idea. It's the best way to kill your phone. If it's under lock Snapdragon, why not so
[Moto G5 Plus Questions & Answers] artician:
I'm updating to the latest available software for my Moto G5 Plus.

I've used the phone since 2018 with TWRP and LineageOS.

I've been more cautious about checking and verifying signatures lately.

I downloaded the TWRP App from the official TWRP site, with their public key, and the Apps' .ASC signature. Using Gpg in Windows to verify, the signature confirms authenticity.

I've not used the App in the past, and am more comfortable doing things manually, so I downloaded the latest version of the TWRP recovery along with it's ASC signature, and it *fails* it's signature check.

This was with version 3.5.2_9-0.

I tried other, earlier versions, which also failed:

3.5.1_9-0

3.5.0_9-0

3.4.0-0

3.3.1-0

3.3.0-0

3.2.3-1

3.2.2-0

3.2.1-0

and 3.1.1-0 all fail their PGP signature check against their accompanying ASC.

Anyone have any thoughts about this?
[Moto G5 Plus Questions & Answers] artician:
Additional info - This was from the TWRP website.
[Touch Diamond, MDA Compact IV General] Poker85:
Hello everyone,

I have a problem with mine Diamond.

When i try to transfer a Divx, so a file like 600 Mb, the trasfer get much slower at 50%, so that the transfer time increase rapidly from 15 minutes to hours. I tried to use even the active sync mode, than the Storage card mode with the same result. I have enought space on my internal storage, and i have had the some result with bouth 1 Gb of free memory and 3,5 Gb of free memory.

Is it an known bug? Is there a solution?

Thanks for your support and congratulation for the forum.
[Touch Diamond, MDA Compact IV General] Poker85:
Noone else has this problem?
[Touch Diamond, MDA Compact IV General] gary.bannister:
are you connecting the device to a USB 2.0 port? Because on USB 1.0 i would expect a 600mb file to take hours to copy.
[Touch Diamond, MDA Compact IV General] Poker85:
I'm using USB 2.0 port. The problem is that until 50% the time is regular, just some minutes...than it get increased to hours...
[Touch Diamond, MDA Compact IV General] gary.bannister:
The only other thing i can think of then is if you are using Vista by any chance it has been reported it has/had a problem with copying large files (not just with the Diamond, just in general)
[Touch Diamond, MDA Compact IV General] Poker85:
Ok...we should have found the problem... I use vista.

So do you know if is there any solution?
[Touch Diamond, MDA Compact IV General] gary.bannister:
I decided against running vista to be honest, but i did a quick search and found some information here: http://www.mydigitallife.info/2007/08/24/slow-file-and-folder-copy-move-transfer-or-delete-operation-speed-problem-in-vista-fix/

You can also read more if you simply type in 'slow copying on vista' into google. This is only a guess at what your problem could be though. I know that using USB 2.0 on XP transfers files for me very quickly (just wish i could get iGO to bloody work though when copied! :p)
[Touch Diamond, MDA Compact IV General] hitenpatel227:
I have a problem any high quality video files, such as DivX. Apparently there is supposed to be a version specific for the Diamond of The Core Media Player, don't know what's happening with it.
[Touch Diamond, MDA Compact IV General] Poker85:
Thank for your help gary.bannister.

I have tryied the suggestion written in the website without success...

Thank you anyway.

I only hope it's not a problem of my device because i haven't heard noone else with this problem.

Bye
[Touch Diamond, MDA Compact IV General] kiran999:
Ive had this same problem a few times, but ive noticed that if i plug the diamond in another usb slot then i get normal speeds.
[Lenovo Legion Phone Duel 2] lilo_ind:
Anyone know how to enable Low latensy at Legion 2? I use Redmagic Tws earphone but i stuck to enable low latensy.

I trying to enable at developer option but no works..