yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] uomn88:
Hello here ! I need help please if someone has the time to with my new smatphone "Conquest S11" bought from china, it's hard to found informations about this phone (there is not even one review of it yet)

So the problem is with WhatsApp application : I have delayed messages notifications and I can't take incoming calls (the phone is not ringing) ! :crying:

I did diagnostic the issue and I found that the phone's system (Conquest S11 stock ROM) kills the app by force (on boot also) and restart it after hours when it wants to, that's why I get delayed messages and can't receive calls at proper time (I get missing calls notifications a few moments later) ...

Can someone help me please !

Thanks if you give some times

Edit : I think it's the same bug with "Ok Google" voice detection because sometimes it works sometimes not (even on lock screen) :rolleyes:
[Android Q&A, Help & Troubleshooting] uomn88:
I searched more and I found that WhatsApp app is forced to stop by the system when I lock the device

I think it's the battery economy of the phone that is badly maked ...

There is 2 modes on battery settings : "high-performance" and "balanced", I set it on "high-performance" but it didn't solve the problem :(

Edit : I also set WhatsApp to "not optimized" on battery optimisation but still not working
[Android Q&A, Help & Troubleshooting] uomn88:
No one :(

It hibernates it in less than 1 minute when I lock the screen !!!! ?

Why this fuc&€#@ phone kill WhatsApp ?!!!
[Android Q&A, Help & Troubleshooting] uomn88:
I sent an email to WhatsApp Support saying this : "Hello, I really need help with your application, I explain: my new smartphone, the CONQUEST S11 (with Android 7.0), forces the application to stop when locked (in less than 30 seconds) which means I can not receive calls (video or audio) when the device is locked and I can not receive them until the system decides to re-open the application on background by itself or to open it myself manually; the same goes for messages ...

In the phone's battery settings, there is a "balance" mode and another "high-performance" mode which I opted for thinking that the problem comes from here and I also disabled battery optimization for Whatsapp (set on "Non optimized") but it not works ! Always the same worries unfortunately

That's why I'm contacting you hoping you can do something

Cordially"
[Android Apps and Games] D_Vovan_238:
Hello 👋

To bad that most of K10 Developers are Inactive 🙁

But now I want to start next level of Development, Artificial Intelligence,

Cris Kelo V1.01 is available for download ;)

Download Link :

Cris Kelo V1. 01

XDA:DevDB Information

Artificial Intelligence "Cris Kelo", App for all devices (see above for details)

Contributors

D_Vovan_238

Version Information

Status: Testing

Current Stable Version: As soon as possible

Stable Release Date: 1969-12-31

Current Beta Version: Now :)

Beta Release Date: 1969-12-31

Created 2018-03-04

Last Updated 2018-03-04
[Nexus 4 Android Development] voron00:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

IMPORTANT: You need to have a /system partition at least 1272 MB size to flash this ROM.

A few options to repartition the device:

https://xdaforums.com/nexus-4/general/guide-increase-nexus-4s-partition-space-t3800264

https://xdaforums.com/nexus-4/orig-development/repartition-nexus-4-repartition-t3844383

Also quick and easy repartitioning script for flashing on stock partition table only: https://drive.google.com/file/d/1GNbxlqG78WYOeXBxgmfGgMmsf02KMVOX/view?usp=sharing

Use at your own risk.

Any repartitioning is done at your own risk.

Works:

- WiFi

- Bluetooth

- RIL

- Camera

- GPS

- Sensors

- Audio

- NFC

Doesn't work:

- L1 Widevine DRM

- Slimport

Flashing Instruction:

1. Backup all your data (Important)

2. Wipe system, data and cache.

3. Flash the ROM and Gapps.

4. Reboot.

Downloads:

ROM: https://drive.google.com/open?id=1e-mO4qaEP1y0wrBbbPwsISdJuW_TeLQo

Gapps: https://opengapps.org/

Sources:

Device: https://github.com/voron00/android_device_lge_mako

Kernel: https://github.com/voron00/android_kernel_lge_mako

Vendor: https://github.com/voron00/proprietary_vendor_lge

Credits:

- LineageOS team.

- @Ziyan for his great work on camera and other things.

- @Clamor repartitioning scripts.

- If i forgot someone, please tell me.

Contributors

voron00

Source Code: https://github.com/LineageOS
[Nexus 4 Android Development] voron00:
Reserved.
[Nexus 4 Android Development] moriel5:
This looks great so far, enough that I am extremely tempted to switch over from CRDroid (but alas, I do not have the time).

Do you think that you may be able to take care of the GPS issue (although GPS works fine on CRDroid (perhaps you may want to take a look at whatever changes they had done in the matter from LOS).

By the way, do you have any idea why GLONASS does not work properly for me?

My phone detects GLONASS satellites, however it fails to connect to them.

This may help you out with your build of LOS15.1.
[Nexus 4 Android Development] mohsalfa:
Thanks Man! You bring back the legend (Nexus 4) phone new life

Btw can you give more detail to install Gapps on this ROM? because I've still got a problem Error #70 Insufficient Space Available in System Partition even with Pico and Gapps-Config. Thanks, Man! :)
[Nexus 4 Android Development] n0b0dy666:
Awesome work, thank you! I've successfully flashed the ROM and Pico GApps (excluding the Google Text-to-Speech as I never did, never will use it anyway) using the following config

Include

CalSync
DialerFramework
PackageInstallerGoogle

Copy this in your txt editor and save it as gapps-config.txt to the same folder as GApps zip file.
[Nexus 4 Android Development] spkvvs:
is there a "One-hand' mode?
[Nexus 4 Android Development] Wiltron:
Latest TWRP, Bootloader & Radio - Full wipe, from within TWRP and/or by manually erasing/formatting partitions using Fastboot.

Using latest OpenGapps Aroma installer, and selecting nothing from any of the lists in the installer, so that it only installs the core files required to add a Google account to the device.

Google Services Framework crash-loop - never goes away, "keeps stopping".

Tried manually installing the latest APK from APK Mirror, and it does get farther by asking me if I want to restore from a cloud, copy from iPhone or setup as new, but all three options result in the same crash.

Tried rooting with Magisk 16, and without rooting, obviously a clean flash between, and result remains unchanged.
[Nexus 4 Android Development] voron00:
No such issue here with opengapps nano + gapps-config posted above, maybe you should try that way and see if it works.
[Nexus 4 Android Development] voron00:
Update:

2018-03-07:
- March security patch.
- Ancient mako kernel that came way back from cyanogenmod days has been rebased off the AOSP upstream (3.4.113).
- Enabled F2FS support (untested).
- Fixed power hal, stuff like touch and interation boosts, low power mode freq limit works properly now.
- Very efficient interactive governor from franco kernel (works much better than ondemand, also modern devices use interactive as their default governor)
[Nexus 4 Android Development] voron00:
Video recording is fixed, but i made some other changes i want to test before releasing a new build, but that won't take too long i guess.
[Nexus 4 Android Development] nefescalanadam:
is that means, stable build coming soon?
[Nexus 4 Android Development] voron00:
Not 100% stable, there are still some minor bugs. Also enabling hardware encoder broke the built in screen recorder app so i had to temporary remove it from the build for now.

Anyway, update is up:

2018-03-10:
- Synced lastest LineageOS sources.
- Fixed video recording.
- Minor kernel tweaks to improve overall performance.
[Nexus 4 Android Development] moriel5:
Do you think that call recording will work properly here?

Since it does not work perfectly on CRDroid (the other side is heavily muffled in the recording).
[Nexus 4 Android Development] AndyYan:
Impressive work! 5 years already and N4 still keeps going and going...

Sent from Xiaomi Mi Mix 2 @ LineageOS 15.1
[Nexus 4 Android Development] voron00:
You have to pick hal1 patches to hardware/qcom/media stack before building:

cd hardware/qcom/media

git fetch https://github.com/Unlegacy-Android/android_hardware_qcom_media aosp-8.1

git cherry-pick ee3524b0c8fc84e478a3b5af6859e99be9a0cc77
git cherry-pick 6e1e771b60535deae8e6dac6f35193ca40c7dfd3
git cherry-pick fb6c95a7f31f8612171f88c92e6899627e4319d7
git cherry-pick c7202d9283cf78b6f1d5356be918d107887aa3e5
git cherry-pick 748e30c9b79a4b716df6de3067887f997774c783
git cherry-pick 77e62c0fc5b1804ccbd8a433b7b5f91056a23f29
git cherry-pick adfa23dadc4f959e5f5049f4f9b952ec363e3a58
[Nexus 4 Android Development] Islam Looca:
I had some issues with AOSP oreo builds, in nitrogen and unlegacy roms that not fixed till now, i don't know if you can fix it or not, i'll copy and paste what i reported before so you can check again if it's able to fix or not.

" Sometimes i can't end a call, i keep pressing end call and the call screen is not responding, also had another issue, sometimes when i'm in the middle of the call and want to use the phone to check another number for someone, the screen is still off and i have to press power button to get the screen back on. "

And [MENTION=8289179]Karan.S[/MENTION] reported the same issue :

" I had reported the same issue a few weeks back. Same happens with me too. As long as the call is active, it is as if the proximity sensor doesn't work. Have to use the power button to wake the screen up. It works when the call is being dialed and after the call has ended. Just to make sure the proximity sensor isn't the cause I rolled back to Nitrogen 7.1.2, on there the dialer works just as intended. Using Google Phone app if that matters. Not sure what is wrong. "

This issue was reported in nitrogen os thread, and when i wanted to check if it's rom issue i've flashed unlegacy rom and it's present too, never faced it in nougat or marshmallow.

The other one is the focus issue in google camera and it's present since nougat and still there in oreo, the focus i think sets to continuous not auto and when using flash, it keeps on for 4 seconds or 5 before capturing the photo.

Thanks in advance
[Nexus 4 Android Development] AndyYan:
Worked - thanks for the prompt response!
[Nexus 4 Android Development] chopoLet:
Thank you for this great rom, the rom will much stable when it gets mature. :)
[Nexus 4 Android Development] nitin.chobhe:
This is issue with your device's proximity sensor. I do not see any other reason for it not to work.

Regarding camera - we need to understand that this device is 6 years old and the camera original blobs are updated since long. We should be thankful that at least we have fully working camera ;)

Nitin
[Nexus 4 Android Development] voron00:
Uploaded new build, in-call volume is fixed, plus some sepolicy fixes. i have no idea why bluetooth isnt working for some people but since nobody sent proper logs i can't tell. Also note that aosp Miracast support has been completely removed from pie (new devices have their own implementations of this) and nexus 4 can't use that anymore (https://github.com/LineageOS/android_frameworks_av/commit/d0a98fa05f0f6719b93d000c4638230af06e0b99) so all related files has been removed from the device.
[Nexus 4 Android Development] Cice96:
Here is the bluetooth log at boot. I hope it's right this time.
[Nexus 4 Android Development] voron00:
02-28 17:23:32.144 257 257 I bdAddrLoader: option : f=/persist/bluetooth/.bdaddr
02-28 17:23:32.144 257 257 I bdAddrLoader: option : h
02-28 17:23:32.144 257 257 I bdAddrLoader: option : x
02-28 17:23:32.144 257 257 I bdAddrLoader: Read From /persist/bluetooth/.bdaddr by Path type(0x11), Data type (0x21)
02-28 17:23:32.144 257 257 W bdAddrLoader: There is no Address File in FTM area : /persist/bluetooth/.bdaddr
02-28 17:23:32.144 257 257 E bdAddrLoader: Fail to read BDAddr from /persist/bluetooth/.bdaddr
02-28 17:23:32.144 257 257 E bdAddrLoader: Fail to load data !!

It seems like something is wrong with your bt address file, its either missing or corrupted...
[Nexus 4 Android Development] Cice96:
Using a file explorer i see that there is no /bluetooth folder. Any suggestione on how to create that file?
[Nexus 4 Android Development] voron00:
This might help: https://xdaforums.com/showpost.php?p=65355601&postcount=2
[Nexus 4 Android Development] bgoel4132:
But my Bluetooth is working absolutely fine on NOS

If my Bluetooth folder is missing will it br specific to rom
[Nexus 4 Android Development] Cice96:
Thank you, issue solved. If anyone is interested i built ResurrectionRemix and i could share the link.
[Nexus 4 Android Development] bgoel4132:
I am interested ?
[Nexus 4 Android Development] nitin.chobhe:
Please don't discuss other ROMs in this thread. That's really a bad etiquette.

Nitin
[Nexus 4 Android Development] Cice96:
Sorry
[Nexus 4 Android Development] envieidoc:
Yes, share the link RR-P
[Nexus 4 Android Development] nitin.chobhe:
[MENTION=4634707]Cice96[/MENTION] Take that.

These days, common sense is not common after all.

Nitin
[Nexus 4 Android Development] Cice96:
Ad said before please don't ask about other roms in this thread. If i want and when i'll be able to provide a decent support, i'll create a new thread. This is the first ROM i built for this device.
[Nexus 4 Android Development] mdi9:
I'm testing rom from couple days and i notice that sms notifications comes only when i wake device. Anyone else having similar issues ?
[Nexus 4 Android Development] Holzhacker:
Awesome work voron00 & co!

I've got a question about a recommended partition scheme. On a 8-GB-model the userdata partition is only about 6 GB, so it's already quite small.

I don't want to shrink that partition further too much (best: not at all).

If I increase the size of the system partition to 1272 MB and don't change userdata, cache would end up with 128 MB.

What I'd like to know is how the regular OTA process is working. As far as I can see it copies the image to the cache partition (I can see the output in TWRP using it from there, furthermore I don't have to decrypt my data partition in TWRP, so the update image can't be on data).

If that's the case, the cache partition needs to be bigger. What would happen if it is not big enough?
[Nexus 4 Android Development] voron00:
In android 4.x era ota file was copied into cache partition but its been changed, its just a small file called block.map copied to cache partition but update file itself is still stored in data, and it works without need to decrypt yes:

https://github.com/LineageOS/androi...56406a1daffdbc70c9fb1/uncrypt/uncrypt.cpp#L22

// This program takes a file on an ext4 filesystem and produces a list
// of the blocks that file occupies, which enables the file contents
// to be read directly from the block device without mounting the
// filesystem.
//
// If the filesystem is using an encrypted block device, it will also
// read the file and rewrite it to the same blocks of the underlying
// (unencrypted) block device, so the file contents can be read
// without the need for the decryption key.
//
// The output of this program is a "block map" which looks like this:
//
// /dev/block/platform/msm_sdcc.1/by-name/userdata # block device
// 49652 4096 # file size in bytes, block size
// 3 # count of block ranges
// 1000 1008 # block range 0
// 2100 2102 # ... block range 1
// 30 33 # ... block range 2
//
// Each block range represents a half-open interval; the line "30 33"
// reprents the blocks [30, 31, 32].
//
// Recovery can take this block map file and retrieve the underlying
// file data to use as an update package.

Edit: Google recommends to have a cache partition size around 50-100 MB on modern devices: https://source.android.com/devices/bootloader/partitions-images
[Nexus 4 Android Development] Holzhacker:
Thank you very much! Then I will go with 1272/128 MB.
[Nexus 4 Android Development] voron00:
Seems to be a problem with stock sms app, using other app like google messenger works fine for me.
[Nexus 4 Android Development] :
So my two cents. It's really slick and fast. Encryption and f2fs works! No issue with the install using Clamor's repartition tool, but there seems to be a problem with outgoing audio on calls with the Google Phone app. If anyone else has the same, let me know! Really nice job [MENTION=3772648]voron00[/MENTION].
[Nexus 4 Android Development] bgoel4132:
I too has this but with carbon rom, mentioning it here as they both have same build tree
[Nexus 4 Android Development] mdi9:
Confirm, same problem for me. But happened only two times. I also used call recorder and voice was not recorded then. Reboot helps but only to next time.
[Nexus 4 Android Development] :
We need someone to try the stock android dialer without any gapps installed, check that the audio works. See if we can narrow this down.
[Nexus 4 Android Development] voron00:
Should be resolved in next build.
[Nexus 4 Android Development] :
There does seem to be a weird issue with keeping a GPS fix when navigating with Google Maps.. Works elsewhere, in maps, location tracking in timeline, etc. Not sure what the problem is.

Edit: It got fixed with the recent update. Works fine now!
[Nexus 4 Android Development] voron00:
New build uploaded.
[Nexus 4 Android Development] :
Calls work, thanks [MENTION=3772648]voron00[/MENTION]!

Maybe not. Worked the first call, then not again. Urgh!
[Nexus 4 Android Development] pxrave:
Do you think we can go official with repartition?
[Nexus 4 Android Development] nitin.chobhe:
He has removed the re-partition script since last to last build.

Nitin
[Nexus 4 Android Development] voron00:
Uploaded new build with a properly working solution this time.

We cant. 15.1 is last official update for mako.
[Nexus 4 Android Development] :
Just a question: is anyone having the notorious "sleep of death" problem (when nexus 4 randomly won't wake up from sleep and a reset is needed) on this ROM? I have it and I tried reflashing the rom, etc and it still happens sometimes. To note: on unlegacy pie rom it didn't happen but I want to continue using this one because its soooo much better :)
[Nexus 4 Android Development] voron00:
Did you flashed the latest version? Because SOD from my experience was caused by liboemcrypto (tzapps) which is removed on latest version, at least i didnt get any SOD after removing liboemcrypto.
[Nexus 4 Android Development] pxrave:
Thanks for the fast response. Would you prefer 16.0 over 15.1? Repart and other mods are well known for me ?. Do you have plans for long time support for mako?

Do you maintain 15.1 also?

Br
[Nexus 4 Android Development] DCCentR:
I have some overlaping issue in VK app:

https://www.youtube.com/watch?v=v7WF0yRxKZ8

Animation of folder opening is a bit choppy, but smooth on the overview screen:

https://www.youtube.com/watch?v=5NsqZQx2xrI

Rington app always crashes the i try to choose the ringtone
[Nexus 4 Android Development] :
Hi, yes I have the latest one. Its definitely happening less often now so thank you very much for the fix. However its still not completely gone since yesterday i got it once again... :confused: and I can't seem to find a repro since it happens pretty undeterministically :(
[Nexus 4 Android Development] DCCentR:
Also get a SOD, on second day of using this rom
[Nexus 4 Android Development] sule_krug:
I also get sod here and there ,and it always happens when I have msg or Facebook msg so I think its correlated to push notifications
[Nexus 4 Android Development] DCCentR:
Something related to LED maybe
[Nexus 4 Android Development] voron00:
Need /proc/last_kmsg after SOD ...
[Nexus 4 Android Development] :
Huh, that's interesting. I haven't experienced a hang or SOD at all.
[Nexus 4 Android Development] DCCentR:
Can we get ROOT by addonsu for this ROM?

https://download.lineageos.org/extras
[Nexus 4 Android Development] voron00:
Yes, i didnt test but should work.
[Nexus 4 Android Development] :
Ok it just happened again. Immediatelly after the reboot i checked this file but it doesn't exist. Then I checked these other locations https://stackoverflow.com/questions/6071547/where-does-android-store-shutdown-logs, but only tombstone and dropbox folders exist and contained some files which you can find attached. I don't know if it's gonna be of any help but i couldn't find much more. Thanks again.
[Nexus 4 Android Development] nitin.chobhe:
That file won't get created automatically. Follow the steps is section 3 in this tutorial:

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

And attach the generated file here.

[MENTION=3772648]voron00[/MENTION] no one reported such issue on carbon and I also don't have this issue, might be something from rom source side? (Note that I still have those extend system partitions commits)

Nitin
[Nexus 4 Android Development] DCCentR:
There is no last_kmsg file on first boot after SOD. It appears after next manual reboot for example.

Here is my dmesg, tombstones folder right after SOD and last_kmsg but after next manual reboot:

https://drive.google.com/folderview?id=1t3OOBKautnZmw3D4tqFFZmrV9BRzojc0

Also there is a problem with Play Market for me, it crashes very often. Here is 2 logcats, crashes at ~22:46 and ~22:55:

https://drive.google.com/folderview?id=1-0sN_U97OBj3f6mIe78CnKW7N7H4Q-DD

SOD happens again, and again can't generate last_kmsg on first boot. Any alternative ways to get useful info?

P.S. Похоже это происходит: "Для начала стоит отметить тот факт, что в большинстве случаев оперативная память Android устройства не очищается при рестарте SoC. Эту особенность использует механизм, который обеспечивает появление файла /proc/last_kmsg. Но порой для принудительного рестарта SoC приходится долго удерживать кнопку Power, что влечёт за собой либо полное, либо частичное изменение содержимого оперативной памяти. В данном случае я рекомендую подключать устройство к ПК через USB-кабель, что бы содержимое оперативной памяти не изменялось (по крайней мере на моём устройстве это работает)."
[Nexus 4 Android Development] voron00:
New build uploaded.

Nothing useful in logs regarding SOD unfortunately, but seems like it can be caused by some apps? Because on clean system there is definitely no SOD. Need some time to test this ...
[Nexus 4 Android Development] DCCentR:
The first thing I noticed - notifications LED not blinking, it's glow constantly now
[Nexus 4 Android Development] voron00:
Reuploaded.
[Nexus 4 Android Development] DCCentR:
Thanks :p, LED is ok now. Did you need any logs to track down Play Market crashes? It's still crashes for me on latest build.
[Nexus 4 Android Development] voron00:
Play store crash is not related to rom i think, try to clear play store data or update to latest app version.
[Nexus 4 Android Development] Giogts:
what bug has this rom?
[Nexus 4 Android Development] nitin.chobhe:
I saw similar post from you on other threads also; why not read the recent posts? or even better flash the ROM and check them yourself?

Nitin
[Nexus 4 Android Development] :
I found one more thing to add to SOD issue.

Maybe it's somehow connected to deep sleep of the device? That it doesn't wake up properly?

I usually install this app https://play.google.com/store/apps/details?id=com.franco.doze which just puts the device to deep sleep immediately when locked as opposed to default behaviour which is after few minutes of inactivity. And now i noticed that with this app in action the SOD happens much more often...
[Nexus 4 Android Development] voron00:
New build uploaded, please try this one for sod, i dropped all kernel patches except those that are needed from rom to work properly.