Related
Since the development thread is closed by OP request( sad but true ), and personally building a "port" of the ROM, i'm glad to help everybody as i can, with this thread.
It doesn't mean to be a development thread since i only build and implement some changes, but just to share comments, issues( like xposed one ) or just ideas to people who own this device ( CN or ROW ).
As a reminder you can find my builds here: LINK or just use OTA function in ROM.
And a big thanks to @frantisheq and @Electry for the works on CM13, and for the next, CM14.
reserved
Are someone try to flash Vibe Z2 (NON PRO) with this ROM?
don't do it, you will probably brick the phone.
K920/Z2 PRO only
Uploaded new build!
Should have Dec 5 patches, have a nice day
Try to install the latest build together with xposed. There is a boot loop with CM logo...... It seems to me there was such kind of problem......
That should be fixed by cm ? . Will apply the xposed fix in next build.
Thanks to inform me about this!
Tapatalk
updated build, with xposed patch, hoping now works fine
The latest build works fine for me. I installed it with xposed.
Hey @malaga82
I have a strange feeling that the new ROM is worse in performance compared to the previous build. It has way more stutters and sometimes the system UI resets and changes my wallpaper to the stock one. Anyone else facing such issues?
Saamyo said:
Hey @malaga82
I have a strange feeling that the new ROM is worse in performance compared to the previous build. It has way more stutters and sometimes the system UI resets and changes my wallpaper to the stock one. Anyone else facing such issues?
Click to expand...
Click to collapse
Could you please provide more details about this behavior and I try to reproduce it? Now I have not such kind of problem. But I can say that the UI sometimes has strange behavior. For example, the horizontal size of quick settings can be more widely than the size of the screen.
maybe it's something related to CM repo's and they will fix "soon".
give some days to see if they fix anything, i'll provide a new build.
In additional to my previous report I would like to add that the latest build cannot hold loading. At the previous build from 16 Nov I can run at the same time a navigation application and a video registration application. Now I cannot do the same because the device is rebooting due to overheating. I tried to figure out what is going on and found that the high limit of CPU0 temperature is set up to 85 C (it seems to me it is low....) and I cannot change it – try several tuning tools. And it is not only one reboot – there are several reboots….. After its a Bluetooth pairing was lost….. And I can repair a normal work only wipe cache & dalvik through TWRP and pair a Bluetooth once again…..
i'd like to have more feedback if possible.
i'm thinking to try to build with the "old" kernel that have cpu voltage control and other features i included times ago.
atm we are a bit stuck with development.
malaga82 said:
i'd like to have more feedback if possible.
i'm thinking to try to build with the "old" kernel that have cpu voltage control and other features i included times ago.
atm we are a bit stuck with development.
Click to expand...
Click to collapse
What information could I provide to you to help?
i just want to know if someone else have that overheating issue
Could you please prepare a build with "old" kernel? Who does not face the overheating problem can stay on the previous one
Solved games issue.
Hello!
Sorry for my English, I from Russia.
On roms later CM 13 2016.03.07 in file: build.prop, increase the value: dalvik.vm.heapsize= from 512m to 768m. This led to the errors in game Real racing 3 (insufficient free memory, missing textures, game crashes). With value 512m games work fine.
If install Adreno drivers from ROM CM 13 2016.03.07, game Gear.club also work fine. The difference can be noticed immediately after starting the game.
I also sent this message to frantisheq.
Happy new year!
Solved games issue.
Additional information to the previous post.
I was looking the file: default.prop, and the parameter ( dalvik.vm.dex2oat-xmx ) is set to =512m. System parameter ( dalvik.vm.heapsize=768m) overlap kernel parameter. Possible, if rebuild kernel with the value 768m, all be fine? I don't test this.
I've tried posting this in MIUI forums and haven't gotten any replies. I'll try my luck with XDA.
How do you correctly identify Redmi 2?
I've got a RM2 that has the 2014811 variant when I check it onscreen.. But I'm skeptic that it's correct. All I know is 2014811 is suppose to be a normal Redmi 2 with 1 gigs of RAM and 8 gigs of ROM. But mine's a 2 gigs RAM & 16 gigs ROM. If I'm correct, with specs like those, my RM2 is suppose to be a RM2 enchanced variant (Pro, Prime, etc). What I can't figure out is which variant is it that I'm dealing with. Another thing that I know is that the RM2 version of mine isn't the global one because I didn't buy it from an official shop, I bought it from an external distributor. The RM 2 box is written in chinese and the characters underneath the battery are full chinese (except for the S/N and IMEI). Is my RM 2 a 2014818 or 2014819? How can I find out which variant is it that I have with me.
Thank you.
2014819- Brazilian variants
2014818- Redmi 2 prime variation of 2014811
ezrawk said:
I've tried posting this in MIUI forums and haven't gotten any replies. I'll try my luck with XDA.
How do you correctly identify Redmi 2?
I've got a RM2 that has the 2014811 variant when I check it onscreen.. But I'm skeptic that it's correct. All I know is 2014811 is suppose to be a normal Redmi 2 with 1 gigs of RAM and 8 gigs of ROM. But mine's a 2 gigs RAM & 16 gigs ROM. If I'm correct, with specs like those, my RM2 is suppose to be a RM2 enchanced variant (Pro, Prime, etc). What I can't figure out is which variant is it that I'm dealing with. Another thing that I know is that the RM2 version of mine isn't the global one because I didn't buy it from an official shop, I bought it from an external distributor. The RM 2 box is written in chinese and the characters underneath the battery are full chinese (except for the S/N and IMEI). Is my RM 2 a 2014818 or 2014819? How can I find out which variant is it that I have with me.
Thank you.
Click to expand...
Click to collapse
for me device name is beneath the battery.
hopefully for you also it must be given.remove back cover and check.
wt88047 - 2014811/12/17/18/19/21
wt86047 - 2014813/816/2014112
TecnoTailsPlays said:
2014819- Brazilian variants
2014818- Redmi 2 prime variation of 2014811
Click to expand...
Click to collapse
sarath67 said:
for me device name is beneath the battery.
hopefully for you also it must be given.remove back cover and check.
Click to expand...
Click to collapse
raymond_bqg said:
wt88047 - 2014811/12/17/18/19/21
wt86047 - 2014813/816/2014112
Click to expand...
Click to collapse
Guys thanks for your replies. After intensive research, I have concluded that: yes, my device is totally a WT88047 - HM201411 - HM 2 LTE-CU (China Unicom) variant. But now I've found out something else that's got me hooked up on finding out. I'm using latest stable stock rom (MIUI 8 - 8.2.1.0), and I checked out my Mi-Account menu in settings, snooped down to devices and... My RM2P is named Redmi 2W..... So... What the heck is Redmi 2W? I've been searching here and there with no luck on finding out what a Redmi 2W is (Haven't checked the chinese sites though). Does anyone know what it is?
ezrawk said:
Guys thanks for your replies. After intensive research, I have concluded that: yes, my device is totally a WT88047 - HM201411 - HM 2 LTE-CU (China Unicom) variant. But now I've found out something else that's got me hooked up on finding out. I'm using latest stable stock rom (MIUI 8 - 8.2.1.0), and I checked out my Mi-Account menu in settings, snooped down to devices and... My RM2P is named Redmi 2W..... So... What the heck is Redmi 2W? I've been searching here and there with no luck on finding out what a Redmi 2W is (Haven't checked the chinese sites though). Does anyone know what it is?
Click to expand...
Click to collapse
what's your purpose, flashing custom roms? simply flash twrp for wt88047 and flash whichever rom you want
ezrawk said:
Guys thanks for your replies. After intensive research, I have concluded that: yes, my device is totally a WT88047 - HM201411 - HM 2 LTE-CU (China Unicom) variant. But now I've found out something else that's got me hooked up on finding out. I'm using latest stable stock rom (MIUI 8 - 8.2.1.0), and I checked out my Mi-Account menu in settings, snooped down to devices and... My RM2P is named Redmi 2W..... So... What the heck is Redmi 2W? I've been searching here and there with no luck on finding out what a Redmi 2W is (Haven't checked the chinese sites though). Does anyone know what it is?
Click to expand...
Click to collapse
shyampandey said:
what's your purpose, flashing custom roms? simply flash twrp for wt88047 and flash whichever rom you want
Click to expand...
Click to collapse
Just take a backup your current ROM by t.w.r.p before flashing ROM(if something goes wrong).
shyampandey said:
what's your purpose, flashing custom roms? simply flash twrp for wt88047 and flash whichever rom you want
Click to expand...
Click to collapse
I've got: touchscreen issues, wake up issues, twrp issues, kernel issues and proximity issues. I'm guessing even if I tell you what I'm experiencing, you won't be able to find a solution for it (please don't say I've got defective hardware, because I don't. Why? Because 3 of my friends bought the same device as mine, in the same online shop and all of them have the same issues). But even so I'll just post all of em and cross my fingers:
TWRP's bugged, needs to timeout (screen off) first before I'm able to responsively use it (touchscreen bugged, tried all latest TWRP versions, including kumajaya's old twrp builds. Touchscreen does work on several 2.8.7.0 and below versions for KK bootloader).
Any custom rom I've flashed will always face lockscreen issues (waking up device using power button leads to unresponsive and un-swipe-able touchscreen, that means I can't unlock my device, seems like it has to do with with proximity too, and please don't ask me about gestures and modified navigation buttons, because I don't use them at all: dt2w, s2w, etc).
Any custom kernel used will always lead to device not being able to wake up (pressing power button doesn't wake up the screen, stays black, have to reset device by force, still happens even though I'm using stock CPU govs *interactive* and I/O scheds *noop* not using hotplugs, doesn't change anything)
I still even face all those problems in Stock MIUI (KK or LP.. 7, 8)
Try downloading china developer ROM? Yeah. I've done that.. Even went to the Chinese download page of miui to download the exact recommended MIUI 8 C-Dev ROM for my HM 2 LTE-CU variant, and still the same bugs occur.
Xposed? I've experimented using stock and custom roms (below API 24) that are Un-Xposed. They still exhibit the same problems as above.
Clean flash dirty flash? I totally understand what those are.
Wipe dalvik cache and cache.. Don't even dare ask about those.
Fix Permissions? Yeah.. It didnt make a difference..
Post dmseg and logcats? Trust me, you devs will probably mark my device as a different type of WT8847 (and by saying that means even if you succeed to find the problems, to fix them means you gotta totally change the 'insides' of roms and stuff to make it compatible with mine. It'll probably be a waste of time if I post those 2 guys here.
Can you help me, bro?
raymond_bqg said:
Just take a backup your current ROM by t.w.r.p before flashing ROM(if something goes wrong).
Click to expand...
Click to collapse
Yeah, I know where you're getting at bro. Let me ask you this, does it not annoy you to death when you're restoring the same backup ROMs frequently just because suddenly your device can't use wi-fi (bugged) or tether, or maybe one of the issues above occur and you just gotta try your best to keep it 'clean'.. again.. and again.. and again? I just need a damn good daily driver without issues for crying out loud :cyclops:
ezrawk said:
I've got: touchscreen issues, wake up issues, twrp issues, kernel issues and proximity issues. I'm guessing even if I tell you what I'm experiencing, you won't be able to find a solution for it (please don't say I've got defective hardware, because I don't. Why? Because 3 of my friends bought the same device as mine, in the same online shop and all of them have the same issues). But even so I'll just post all of em and cross my fingers:
TWRP's bugged, needs to timeout (screen off) first before I'm able to responsively use it (touchscreen bugged, tried all latest TWRP versions, including kumajaya's old twrp builds. Touchscreen does work on several 2.8.7.0 and below versions for KK bootloader).
Any custom rom I've flashed will always face lockscreen issues (waking up device using power button leads to unresponsive and un-swipe-able touchscreen, that means I can't unlock my device, seems like it has to do with with proximity too, and please don't ask me about gestures and modified navigation buttons, because I don't use them at all: dt2w, s2w, etc).
Any custom kernel used will always lead to device not being able to wake up (pressing power button doesn't wake up the screen, stays black, have to reset device by force, still happens even though I'm using stock CPU govs *interactive* and I/O scheds *noop* not using hotplugs, doesn't change anything)
I still even face all those problems in Stock MIUI (KK or LP.. 7, 8)
Try downloading china developer ROM? Yeah. I've done that.. Even went to the Chinese download page of miui to download the exact recommended MIUI 8 C-Dev ROM for my HM 2 LTE-CU variant, and still the same bugs occur.
Xposed? I've experimented using stock and custom roms (below API 24) that are Un-Xposed. They still exhibit the same problems as above.
Clean flash dirty flash? I totally understand what those are.
Wipe dalvik cache and cache.. Don't even dare ask about those.
Fix Permissions? Yeah.. It didnt make a difference..
Post dmseg and logcats? Trust me, you devs will probably mark my device as a different type of WT8847 (and by saying that means even if you succeed to find the problems, to fix them means you gotta totally change the 'insides' of roms and stuff to make it compatible with mine. It'll probably be a waste of time if I post those 2 guys here.
Can you help me, bro?
Yeah, I know where you're getting at bro. Let me ask you this, does it not annoy you to death when you're restoring the same backup ROMs frequently just because suddenly your device can't use wi-fi (bugged) or tether, or maybe one of the issues above occur and you just gotta try your best to keep it 'clean'.. again.. and again.. and again? I just need a damn good daily driver without issues for crying out loud :cyclops:
Click to expand...
Click to collapse
that's all are happening 'cause of source code modification of lineage from cyanogen which caused your device unfavorable base code modification, only thing can be done is flash stock rom, bootloader, recovery, modem, everything using fastboot.
shyampandey said:
that's all are happening 'cause of source code modification of lineage from cyanogen which caused your device unfavorable base code modification, only thing can be done is flash stock rom, bootloader, recovery, modem, everything using fastboot.
Click to expand...
Click to collapse
So in other words "bye-bye" to custom roms right? I'm in latest stable global miui 8 btw (LP), I clean flashed it via download mode, those problems still show up though. Okay let me just try to flash miui via fastboot or download mode again.
ezrawk said:
So in other words "bye-bye" to custom roms right? I'm in latest stable global miui 8 btw (LP), I clean flashed it via download mode, those problems still show up though. Okay let me just try to flash miui via fastboot or download mode again.
Click to expand...
Click to collapse
yeah, after problem bring fixed completely, you can come back to custom roms.
I rolled back to oxygen is 4.5.14 ROM ...whos link is given by one plus support. From open beta 3.
Now I am facing problems
WiFi is not connecting to any device.
And no device found my hotspot..means my device is not visible to anyone on hotspot.
Please help me in that.
Yashvendra.singh.raghav said:
I rolled back to oxygen is 4.5.14 ROM ...whos link is given by one plus support. From open beta 3.
Now I am facing problems
WiFi is not connecting to any device.
And no device found my hotspot..means my device is not visible to anyone on hotspot.
Please help me in that.
Click to expand...
Click to collapse
This has been common. Take a look here (https://forum.xda-developers.com/oneplus-5/help/wifi-completely-broken-t3721004), some users like me have managed to solve the situation.
Yashvendra.singh.raghav said:
I rolled back to oxygen is 4.5.14 ROM ...whos link is given by one plus support. From open beta 3.
Now I am facing problems
WiFi is not connecting to any device.
And no device found my hotspot..means my device is not visible to anyone on hotspot.
Please help me in that.
Click to expand...
Click to collapse
After flashing the roll back version, you need to go to recovery and wipe everything(the third option in stock recovery).
lvints said:
This has been common. Take a look here (https://forum.xda-developers.com/oneplus-5/help/wifi-completely-broken-t3721004), some users like me have managed to solve the situation.
Click to expand...
Click to collapse
The problem has been solved after installing open beta3 on one plus 5.
I think the problem was only with that rom only.
Now my one plus 5 is working fine.?
As written here: https://forum.xda-developers.com/oneplus-5/how-to/guide-fix-fingerprints-wi-fi-failed-t3731059
You need to delete /data/misc/wifi/wpa_supplicant.conf. No need to wipe anything else.
Hi Devs and users,
I wanted to start this thread so that developers and users can see and investigate audio issues on the le_x2 device. Personally, I encountered several audio hiccups and issues since Nougat and audio was never the strongest feature of our device, which is mainly related to the headphone jack removal mostly and the lack of support from the device manufactured (Leeco)
I had several issues especially with the CDLA headphones which never worked correctly in custom ROMs. The headphones with the USB-C adapter worked but there were some hiccups (plugging them with one usb-c orientation etc ...
Recently I started having issues without headphones in phone calls where the caller can hear himself through the noise cancelling mic. The issue was reported and fixed in the LOS device tree but several custom ROMs have this issue. I personally tried to use the files from the commit in AOSP Extended but it didn’t work. Also, from my experience, changing the device firmware (baseband) will impact these issues in some way.
Based on the feedback that will be collected from users, I hope that this thread will contribute into solving these audio related problems for the le_x2 device.
leptdre said:
Recently I started having issues without headphones in phone calls where the caller can hear himself through the noise cancelling mic. The issue was reported and fixed in the LOS device tree but several custom ROMs have this issue. I personally tried to use the files from the commit in AOSP Extended but it didn’t work. Also, from my experience, changing the device firmware (baseband) will impact these issues in some way.
Click to expand...
Click to collapse
Same problem here, can you tell me the meaning of "The issue was reported and fixed in the LOS device tree but several custom ROMs have this issue" . I don`t know what is the LOS device tree, and I need a room that doesn`t have this issue. Can you help me or tell me a link to the thread where this issue is solved , please?
Thanks!
Hi everyone
Same problem and also I seen that battery going down also when charging on and off.
Some fix for these or a rom that works as before this problem?
My problem appears after revenge os
Before with other roms nothing happened
Hi until one I tried an old backup of pure nexus rom nougat and works as before. Then I tried to restore a miui backup with nougat and first time audio and debug problem returns. After that I flashed the same miui from 0 and works well without any app for audio fix.
Now i wiped all and flashed miui 10 Android pie and also works until this moment without issue to fix.
Regards
TarAntonio said:
Hi until one I tried an old backup of pure nexus rom nougat and works as before. Then I tried to restore a miui backup with nougat and first time audio and debug problem returns. After that I flashed the same miui from 0 and works well without any app for audio fix.
Now i wiped all and flashed miui 10 Android pie and also works until this moment without issue to fix.
Regards
Click to expand...
Click to collapse
You mean the echo problem during calling is solved now?
I have wiped the device fully and installed RevengeOS:RevengeOS-2.2-pasta-official-x2-201903*.
Audio problem with echo still remains!
3578761 said:
You mean the echo problem during calling is solved now?
I have wiped the device fully and installed RevengeOS:RevengeOS-2.2-pasta-official-x2-201903*.
Audio problem with echo still remains!
Click to expand...
Click to collapse
Echo during calls on the miui 10 Android 9 still not tested
My problems were
-no debugging my pc not recognize leeco only in Fastboot
-No audio during multimedia
-battery going down also during charge and with smartphone off.
I'm worried to try revenge os for not have another one the same problem as described
TarAntonio said:
Echo during calls on the miui 10 Android 9 still not tested
My problems were
-no debugging my pc not recognize leeco only in Fastboot
-No audio during multimedia
-battery going down also during charge and with smartphone off.
I'm worried to try revenge os for not have another one the same problem as described
Click to expand...
Click to collapse
Hello
I have exactly the same problems.
every pie roms (not tested oreo) have audio problems since revengeos
- No audio and power drain/not charging issue
--> it seems the phone switches to headphone audio though no headphones are connected (eg.: pushing the volume up shows warning message that increasing more might lead to problems...)
--> plugging/unplugging the phone to pc with usb sometimes switches the audio back. --> double check your usb-c cable. Be sure to use the one provided with your phone. I used 2 or 3 other and some did not work correctly with leeco
==> only possible fix for me : with audio routing app (audio route/less audio switch)
- caller hears himself in echo and I cannot hear the caller
--> no solution so far
==> only fix was to go back to eui rom (whith qfil or bootloader flash methods) though I now still have the above problem
Please, what exactly did yo do to resolve both issues in any miui and/or post oreo/pie rom ?
Although could you please share rom links and/or procedures you used to bring sound back ?
Thanks in advance
Regards
Arnaud
Hi I've solved until this moment with miui 10 pie. The first flash successful was restoring pure experience nougat than restoring miui 9 and then miui 10. All restoring was without audio issue.
With magnetic USB adapter I seen that in one direction says headset plugged on other direction charges normally.
TarAntonio said:
Hi I've solved until this moment with miui 10 pie. The first flash successful was restoring pure experience nougat than restoring miui 9 and then miui 10. All restoring was without audio issue.
With magnetic USB adapter I seen that in one direction says headset plugged on other direction charges normally.
Click to expand...
Click to collapse
Hello,
please can you help me and give some more info about how
you solved the problem.
Do you use this rom:
https://forum.xda-developers.com/le-max-2/development/rom-miui-10-8-12-7-based-pie-t3883744
But first you install MIUI 9?
In MIUI 10 the audio issue is then solved?
By the way what do mean :"restoring pure experience nougat"?
Thank you.
Hi I used old backup in twrp of pure experience and miui 9. After that I flashed miui 10 of your topic.
TarAntonio said:
Hi I've solved until this moment with miui 10 pie. The first flash successful was restoring pure experience nougat than restoring miui 9 and then miui 10. All restoring was without audio issue.
With magnetic USB adapter I seen that in one direction says headset plugged on other direction charges normally.
Click to expand...
Click to collapse
TarAntonio said:
Hi I used old backup in twrp of pure experience and miui 9. After that I flashed miui 10 of your topic.
Click to expand...
Click to collapse
Hello,
so what you mean can i go straight to miui 10 when i dont need any backup recovery?
Restoring my 2 old twrp backup. The problem is fixed but don't know if flash from 0 miui 10 can fix the problem.
Perhaps you can try to flash pure experience than miui 9 and for the last miui 10.
TarAntonio said:
Restoring my 2 old twrp backup. The problem is fixed but don't know if flash from 0 miui 10 can fix the problem.
Perhaps you can try to flash pure experience than miui 9 and for the last miui 10.
Click to expand...
Click to collapse
Sorry for my question but what do you mean with "flash pure experience"?
Is this a pure Rom version?
TarAntonio said:
Restoring my 2 old twrp backup. The problem is fixed but don't know if flash from 0 miui 10 can fix the problem.
Perhaps you can try to flash pure experience than miui 9 and for the last miui 10.
Click to expand...
Click to collapse
Hello
could you please provide a small guide to do this with the twrp/rom/modem links you used for this ?
it seems you could help a lot of people here with your knowledge
Thanks
regards
3578761 said:
Sorry for my question but what do you mean with "flash pure experience"?
Is this a pure Rom version?
Click to expand...
Click to collapse
sirnono said:
Hello
could you please provide a small guide to do this with the twrp/rom/modem links you used for this ?
it seems you could help a lot of people here with your knowledge
Thanks
regards
Click to expand...
Click to collapse
Pure nexus is a nougat unofficial rom.
I'm not an expert for the guide. I've tried many experiments until now without successful. Until restoring an old backup through twrp.
---------- Post added at 08:38 PM ---------- Previous post was at 08:03 PM ----------
I've now try unsuccessful treble rom flash follow the guide on xda forum. And restoring miui 10 backup my le max not goes up.
Then I wipe all and restoring pure nexus backup with an error "non hlos" in twrp by cuoco92 after that restart normally in pure nexus. After that I wipe all and restored miui 9 (official twrp 3.2.2 with error to locate fs1 and persist) but normally started. Then wiped all and restored miui10 without error in twrp but device goes in bootloop. At this point in twrp I wiped all flash miui 10 and the wiped cache dalvik and data and restored miui 10 backup successfully.
I have many complaints regarding this echo during calls, i was going to try other Pie roms, but i see i have to go back to EUI.
bluetooth qualcomm aptx codecs not working and audio delay in pubg mobile while using with bluetooth headphones any solution guys?
Anyone can confirm that miui 10 solves audio issue?
Milanche78 said:
I have many complaints regarding this echo during calls, i was going to try other Pie roms, but i see i have to go back to EUI.
Click to expand...
Click to collapse
Same issue here, I thought my mic is broken.
Hello,
Recently i've root and install the lightrom nfe port on android 9.0 and wasn't aware of the snapchat issue, i know that few people are interested about the app but it's very important for me :crying: . Is there a solution, the issue come from the rom itself or the root? I'm wondering to downgrade to oreo, if it's the only way, wich rom can you advise me?
Thank in advance for your answer .
Flashby said:
Hello,
Recently i've root and install the lightrom nfe port on android 9.0 and wasn't aware of the snapchat issue, i know that few people are interested about the app but it's very important for me :crying: . Is there a solution, the issue come from the rom itself or the root? I'm wondering to downgrade to oreo, if it's the only way, wich rom can you advise me?
Thank in advance for your answer .
Click to expand...
Click to collapse
Hi I have same problem I searched and tried a lot of potential solutions without resolve it, the problem come from the rom (all roms based on Note Fe have this problem)
I also contact Snapchat """support"""" (because it was very bad) and I talk with a bot a lot of time always saying that it's my fault if my account is locked (Wow, excelent...)
And recently with a human who send me a copied text who say me that is my fault if my account is locked (so, it's perfect)
So I don't know what phone do you use ?