yashsingh1/xdaforums huggingface dataset:
[LG V20 Questions & Answers] Aljecama12:
Hello guys, I have a LS997 and it was unlocked and was useful with my carrier (Telcel) until today.

I accidentally choosed "CDMA+/LTE EVO" on the "Select Preferred options), on settings -> more -> mobile networks -> set Preferred network.

The signal went out and I'm unabled to make calls and use Data (I can receive SMS, and also it detects Telcel on AIDA64). And I'm unabled to enter the "Mobile Networks" menu now.

I had tried the HiddenMenu app, but I get this result:

BTW I have Security Patch February 2018

Can anyone please help me? I think is not a big issue but I'm running out of ideas.
[LG V20 Questions & Answers] hyelton:
Why post the same again?
[LG V20 Questions & Answers] CradBron:
Where does it store the firmware and bootloader? What if we change that on the ls997 zvd then flash the international firmware? Would that work?
[LG V20 Questions & Answers] hyelton:
No
[LG V20 Questions & Answers] hkassem:
Hello

Lg v20 sprint ls997zvb if unlocked ( gcpro)it will relock after update or it ispermanent thanks
[LG V20 Questions & Answers] a_jalambadani:
no show lte

Hi

I have lgv20 h910pr with software version v10j-clr-pr

and android 7.

I insert sim4g but no show in preferred network type 4g it is only 2g/3g/auto.

I see in hidden menu lte and i change to only lte but yet no show lte.

How i can getting lte.

Sombody tell me you must root device and delete config lte then in update center come update config lte when update it so add lte to network.

Is it correct?

Plz help
[LG V20 Questions & Answers] hyelton:
Are you sure it supports the lte bands of your carrier? And since your selecting LTE only which will only give you data did you set the correct APN for your carrier??
[Non-Touchscreen Windows Mobile Other] Widgetdude:
At this point we've figured out how to completely get rid of the startup video and sound and replace that with default images.

That was done with quksilver's post here:

http://www.modaco.com/content-page/263811/TheLostSouls-Thread-of-Tips/page/20/

It may have been originally some where else but that is the first time I saw it.

The startup option where you delete the entire value displays three images:

Mystery Image (This may also be called ms_splash.png but in a different location)

/windows/ms_splash.png

/windows/carrier_splash.png

I have a few questions. The first image displayed is not ms_splash.png unless it is somewhere different as I have replaced that file and confirmed that it is indeed different. So I'm wondering where that image is and if we can somehow manipulate it.

Second, I'd like to not just remove the startup animation but change it entirely if that could ever be a possibility

Third, I'd like to be able to bring the sound back in if we can't change the animation. Manipulating the sound isn't hard as it's just a matter of changing start.wav to something else, same with the shutdown sound.

If this is making any sense let me know if you guys have any ideas, if it isn't I'll clarify, I can also post the details of the posts that I have read if that helps pull it all together.
[Non-Touchscreen Windows Mobile Other] thomandjerry:
BlackJack or I600?

i haw i600 it no BlackJack version! BlackJack not wifi and other more functions.
[HTC One Mini 2] nailyk:
Amazing! Thanks for your dev!

As you know I don't own this device but is good to know 8974 is not dead ;)

Feel free to highlight me here or on IRC if you need something. Also I have some contacts which can help to become official when you will be ready :)
[HTC One Mini 2] Andruxcx:
Cool. gonna try this

---------- Post added at 03:35 PM ---------- Previous post was at 03:30 PM ----------

Is it 7.0 or 7.1?

---------- Post added at 03:36 PM ---------- Previous post was at 03:35 PM ----------

oh nvm

---------- Post added at 03:59 PM ---------- Previous post was at 03:36 PM ----------

When theres a new update will i have to wipe data? I am kind of a newbie to roms.
[HTC One Mini 2] nightcore500:
7.1.2

If you are already on lineageos 14.1 you don't need a full wipe.
[HTC One Mini 2] Andruxcx:
Thanks. So i tried the rom and everything seems fine for now except that i cant get out of strict mode with dev options. Is there a way to turn strict mode off?

---------- Post added at 05:45 PM ---------- Previous post was at 05:43 PM ----------

For those who want root dont install super su it will bootloop your device. just download it from this link ~ https://download.lineageos.org/extras ~ and flash it in twrp :good:

---------- Post added at 06:04 PM ---------- Previous post was at 05:45 PM ----------

Not sure if this is a bug but i cant see any contacts when i go to the import from sim window
[HTC One Mini 2] nightcore500:
No, its a debugging feature thats automatic enabled on eng builds. This build is currently only for development purposes. I switch to userdebug on the next releases.
[HTC One Mini 2] Andruxcx:
Okay
[HTC One Mini 2] tryllz:
Does this need TWRP version 3 to flash or the 2.8.5.0 flashes as well ?
[HTC One Mini 2] stkl:
Awesome. Did a clean install after full wipe (using TWRP 3) and started testing.

Working:

System UI, GApps

Stable networking (WiFi 2.4 + 5 GHz), Cellular 3G and 4G

Bluetooth (audio, data)

Simple NFC tag

Camera, flash, torch

Audio in/out (loud and clear)

GPS

Sensors (magnetic, light, proximity - proximity little buggy, but that problem existed before)

Running much smoother than the latest CM13 build overall

Problems / Not Working:

DT2W

16GB SanDisk SD card not working - worked before and also with another Android 7.1 device (older 8GB SanDisk works - have to figure out why)

Some root issues, most lilkely due to eng build incompatibilities with my apps

Just played around for an hour and so far it's running pretty stable (not a single app crash). Looks like we're on the right track.

The issued I experienced before (CM13) with OTG are still the same - surprise - but that's not of priority.
[HTC One Mini 2] tryllz:
Received ERROR when flashing via twrp, both 2.8.5.0 and 3.0.2:

Can't install this package on top of incompatible data. Please try another package or run a factory reset.

Updater process ended with ERROR: 7

ERROR installing zip file '/externl_sd/lineage_memul-ota.zip'

I tried dirty flash with STOCK ROM installed, so I did a complete wipe of SYSTEM, CACHE, DALVIK CACHE and DATA and installed successfully.

Also I have this Red Screen border flash when touching screen at times, NOT always but mostly, I have checked developer options all settings are off but still it wont go away. I read about strict mode but there is no options in settings, any ideas, I even turned off developer options but still remains.

INITIAL REVIEW.

Way better than CM13

Slightly laggy, I will assume due to alpha state

Crystal clear audio

Camera is crisp clear with photos compared to CM13

Boot/reboot more than once tried is a bit slow

SD read in gallery is too slow could be due to slow MMC read/write and first time reading too many images - fine after it loads all images
[HTC One Mini 2] nightcore500:
Look at https://xdaforums.com/showpost.php?p=72190216&postcount=7
[HTC One Mini 2] tryllz:
Thanks, missed that.

:good::good::good: ROM
[HTC One Mini 2] stkl:
Seems to be an issue with die SD card driver, UHS-1 cards (tested with SanDisk Ultra) are not supported by our current kernel.

The same card (verified genuine btw.) has been working with CM13.

kmsg:

[ 7841.388709] c0 22066 mmc1: slot status change detected (0 -> 1), GPIO_ACTIVE_LOW

[ 7841.775759] c0 18205 mmc1: new ultra high speed DDR50 SDHC card at address aaaa

[ 7841.781131] c0 18205 mmcblk1: mmc1:aaaa SU16G 14.8 GiB

[ 7841.803148] c0 0 mmc1: data txfr (0x00200000) error: -84 after 16 ms

[ 7841.803201] c0 0 sdhci: =========== REGISTER DUMP (mmc1)===========

[ 7841.803247] c0 0 sdhci: Sys addr: 0x00000000 | Version: 0x00003e02

[ 7841.803292] c0 0 sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000008

[ 7841.803336] c0 0 sdhci: Argument: 0x00000000 | Trn mode: 0x00000033

[ 7841.803381] c0 0 sdhci: Present: 0x03f80206 | Host ctl: 0x00000017

[ 7841.803425] c0 0 sdhci: Power: 0x0000000f | Blk gap: 0x00000000

[ 7841.803469] c0 0 sdhci: Wake-up: 0x00000000 | Clock: 0x00000007

[ 7841.803512] c0 0 sdhci: Timeout: 0x00000008 | Int stat: 0x00000000

[ 7841.803557] c0 0 sdhci: Int enab: 0x03ff800b | Sig enab: 0x03ff800b

[ 7841.803600] c0 0 sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000

[ 7841.803645] c0 0 sdhci: Caps: 0x2329c8b2 | Caps_1: 0x00008007

[ 7841.803689] c0 0 sdhci: Cmd: 0x0000123a | Max curr: 0x00000000

[ 7841.803734] c0 0 sdhci: Resp 1: 0x5b590000 | Resp 0: 0x00000900

[ 7841.803779] c0 0 sdhci: Resp 3: 0x0a404012 | Resp 2: 0x76b27f80

[ 7841.803820] c0 0 sdhci: Host ctl2: 0x0000000c

[ 7841.803859] c0 0 sdhci: ADMA Err: 0x00000003 | ADMA Ptr: 0x2e300008

[ 7841.803909] c0 0 mmc1: clk: 50000000 clk-gated: 0 claimer: mmcqd/1 pwr: 14

[ 7841.803957] c0 0 mmc1: rpmstatus[pltfm](runtime-suspend:usage_count:disable_depth)(0:0:0)

[ 7841.804003] c0 0 sdhci: ===========================================

[ 7841.810959] c0 27665 mmcblk1: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00

[ 7842.098945] c0 18205 mmcblk1: p1
[HTC One Mini 2] nightcore500:
Thanks, I have fixed the problem yesterday evening: https://github.com/nightcore500/and...mmit/08a899fdb120982aaad42c6c6ea9315a60a908e5

Its included in the next release.
[HTC One Mini 2] stkl:
OK, I should have pulled fresh sources... anyway, great ;)
[HTC One Mini 2] Finusfix:
As far as I can judge, nightcore uses the latest msm8974 kernel source from lineage? Invisiblek has here synced the mmc driver some time ago to caf/LA.BF.1.1.1_rb1.26. (https://github.com/LineageOS/androi...mmit/b7a99c094be02d78d1a9f7f8e5898bd702df82c7) That problem was already announced by some people to the devs. But nobody had ever cared about it. Or what do you mean stkl?
[HTC One Mini 2] stkl:
Yes, exactly. Same code snippet referenced be nightcore. Should be fixed now. Just started a new build, will test tomorrow.

The UHS problem has been fixed and reverted numerous times in the past, not only for CM/LOS...
[HTC One Mini 2] tryllz:
When I select image(s) for deletion, sometimes the delete button shows sometimes it doesn't.

Anyone knows how to make a flashable zip of stock apps, Thanks..
[HTC One Mini 2] Soenisti:
Yeah the git entry I always revert when building the One Mini 2 is the following commit:

b7a99c094be02d78d1a9f7f8e5898bd702df82c7

This is when all the MMC stuff changed to fit the M8 and similar and stopped working for the Memul.
[HTC One Mini 2] Andruxcx:
I think so. Yeah
[HTC One Mini 2] tryllz:
Wouldn't that impact the battery..
[HTC One Mini 2] stkl:
Negligible. It doesn't matter if you spend CPU time on compression or on recreation when using less memory. The overheads just cancel each other out.

From my recent practical tests I also did not notice any difference in battery lifetime between 0, 256 and 384.
[HTC One Mini 2] xxxmadraxxx:
Can you post the terminal command for adjusting the zRAM? [assuming this can be done on the fly]. So I can check it out, in advance of the changes being written to the next release.
[HTC One Mini 2] stkl:
Sure. First you should close all unncessary apps, because you have to disable swap as part of the process and need some free memory in the meantime. (first step fails if not enough). Execute as su. Everything's gone after a reboot

# Disable swap
swapoff /dev/block/zram0

# Reset ZRAM
echo 1 > /sys/block/zram0/reset

# Unallocate memory
echo 0 > /sys/block/zram0/disksize

# Allocate new memory (size in Byte)
echo 402653184 > /sys/block/zram0/disksize

# Make it a swap partition
mkswap /dev/block/zram0

# Enable swap
swapon /dev/block/zram0

You can always verify the current state with the following (sizes shown in KB):

cat /proc/swaps

If the first step always fails, either reboot or add an additional swap file in the disk and remove it afterwards.
[HTC One Mini 2] xxxmadraxxx:
Thanks. The commands all seem to execute OK, but the zRAM size doesn't seem to change [or am I just misinterpreting the last few terminal messages?]:

1|memul:/ # swapoff /dev/block/zram0
Killed
137|memul:/ # echo 1 > /sys/block/zram0/reset
1|memul:/ # echo 0 > /sys/block/zram0/disksize
1|memul:/ # echo 402653184 > /sys/block/zram0/disksize
1|memul:/ # mkswap /dev/block/zram0
Swapspace size: 262140k, UUID=65bdac7f-6fdd-4a3f-917f-07d84b28c973
memul:/ # cat /proc/swaps
Filename	Type	Size	Used	Priority
/dev/block/zram0 partition	262140	45104	-1

I suspect nothing has changed as first camera launch is still taking ~30 seconds.
[HTC One Mini 2] stkl:
First command has been killed. As I said, this might happen, if the system is not able to disable swap without running out of memory. If everything was OK, the command should not provide any output. Just try multiple times.
[HTC One Mini 2] xxxmadraxxx:
Ah. Silly me! --I did wonder, as that command seemed to hang for a few seconds. But I thought [hoped!] that the "killed" might be referring to the fact that the swapping process had been killed.

OK. I'll give it another go.

---------- Post added at 20:15 ---------- Previous post was at 19:48 ----------

OK. I had another go and it [sort of] worked this time:

memul:/ $ su root
memul:/ # swapoff /dev/block/zram0
1|memul:/ # echo 1 > /sys/block/zram0/reset
memul:/ # echo 0 > /sys/block/zram0/disksize
1|memul:/ # echo 402653184 > /sys/block/zram0/disksize
memul:/ # mkswap /dev/block/zram0
Swapspace size: 393212k, UUID=38e3e75c-b702-4b40-9fe4-a28e2bf503a1
memul:/ # swapon /dev/block/zram0
memul:/ # cat /proc/swaps
Filename	Type	Size	Used	Priority
/dev/block/zram0 partition	393212	28	-1

I say "sort off" because I seem to have ended up with a 393MB zRAM rather than 402. Or is it 39,3MB! I'm not sure what the unit of measure is here ???

Anyway, I've done a very brief test and am seeing the following:

* Camera: ~3 secs for anything to happen after tapping icon to launch. But then viewfinder image appears and overlaid buttons/icons etc. appear almost instantly

* Shooting speed seems similar to before. I was able to take 5 shots in quick succession

* Gallery opening after tapping thumbnail in camera GUI still sluggish [somewhere around 5-10 secs to open] but not as bad as before, when I was left with a black screen for so long I started wondering if the phone had crashed.

* Camera not so reluctant to quit now. Shut down seems to take only a couple of seconds.

So, all-in-all, that very superficial test seems encouraging to me. Although, as per above, I'm a bit wary of the placebo effect, given I seem to be either running 393MB or 39,3MB zRAM --depending on what those figures mean!
[HTC One Mini 2] stkl:
What you entered are Bytes, what is display are KiB (binary Kilo-Bytes), so 1024 Byte. If you divide by 1024, is results in 402653184 B = 393216 KiB = 384 MiB ;)

I think I remember that you can also add suffixes directly, e.g. "echo 384M > /sys/block/zram0/disksize" for more readybility, but I never tried on Android.

You might also try 400 MiB (419430400) which is what nightcore set in his device repository. Don't expect much of a difference though.

Don't expect too much of the effect. Loading Apps like albums also relies on reading image data from emmc/sdcard, rather than profiting from RAM. Most notable effect is faster re-opening and switching between apps, when larger parts of the data needed are still in memory.
[HTC One Mini 2] xxxmadraxxx:
No worries. I wasn't expecting miracles. I'll be happy enough with getting those delays down to ~3-5secs, as seems to happen with this modification.

And thanks for taking the time to work on this. For a while there, I felt I was pissing in the wind, when people kept telling me the camera behaviour I was seeing was only to be expected from a device with 1GB of RAM. But I knew that ~30secs to launch the camera and have it become responsive [with no other apps even running] wasn't normal behaviour --even allowing for underpowered hardware. Glad you seem to have proved I wasn't talking complete drivel.
[HTC One Mini 2] Opteronix:
Maybee a bug...

I'm new here...

First, thanks to nightcore500 for this rom :good: :).

I've installed it last week. It works very fine.

But maybe I have found some bugs. The clock app (in german Uhr) can't started up, it crashes.

As well the Battery-Management works not allways correctly, I've had some problems, the Battery shows lower than 10% and after a restart it was 85%. So, the phone needs sometimes a lot of power, not allways, but sometimes I must load it twice a day.
[MENTION=7570463]nightcore500[/MENTION]: If you can tell me, which error-logfile you need and where I can find it, I will send it to you.

Sorry for my broken english...:(
[HTC One Mini 2] Marvbox:
Sounds like battery issue. My last mini has the same, and a new battery have solve this.
[HTC One Mini 2] petie2106:
I have the same problem and it is quite annoying. Sometimes I do not notice it and my battery is empty.

Do you work on a solution?
[HTC One Mini 2] ExB:
Yeah, I can confirm this problem as well on my wifes memul.. Eagerly awaiting the new build :)
[HTC One Mini 2] city2026:
I hope there'll be working gps and coarse location functions.

Love the camera app, yet, had reverted to M (cm13) cause of needs to have proper & reliable location func.

P.s. Probably, internet is faster on M.
[HTC One Mini 2] Andruxcx:
Gps works fine for me

---------- Post added at 11:11 AM ---------- Previous post was at 11:10 AM ----------

Or maybe not
[HTC One Mini 2] di1100:
Works or no?
[HTC One Mini 2] city2026:
That is incredible!

I couldn't use Uber app even on cm13, as well as it was hard to use any navigation.

Now it's on! It's snappy again. (best snappiness with the background process limit)

I'll put the zram=400.sh to su.d and say if it's fine on bootup

Up: it works

Thank you for your tips and best regards
[HTC One Mini 2] Andruxcx:
Under wifi it does but with mobile data it doesn't. Maybe because i have a crappy​ connection... Needs testing

---------- Post added at 10:52 AM ---------- Previous post was at 10:16 AM ----------

Ok tested with 4g mobile data on gmapps seems to work
[HTC One Mini 2] tryllz:
Seems battery is bulged slightly if screen has not pop out, battery must be replaced, no other solution.
[HTC One Mini 2] stkl:
I'm currently on vacation in France (Monaco) and use GPS with mobile data services daily. Despite needing up to 30s to lock the current position sometimes (aGPS issue), it works without any drawbacks, both on GMaps and Navigon.

Took some risk by relying on the phone (GPS, mobile flight ticket, ...), but so far I'm confident enough to trust our ROM as a daily driver. Didn't even use my external battery til now, fine with 40-60% battery per day.
[HTC One Mini 2] Andruxcx:
Ok the camera refuses to work at all now
[HTC One Mini 2] Andruxcx:
Nevermind (again) it works whenever i restart my phone when it is charging but if i disconnect the charger after about 5 minutes of not using any camera apps it stops working. This is a really odd problem. Is there any way i could see what happens when the camera shuts off? Any hidden logs or some way to see?
[HTC One Mini 2] petie2106:
Now i have this problem every day. Logcat on attachments.

It seems that this is related to my problem.
[HTC One Mini 2] Rhioun:
Seeing how this phone is so similar (in specs) to the SHARP Aquos Crystal, I'm thinking of porting this ROM.

However, would there be any drawbacks in porting the ROM?

What things would I have to edit?
[HTC One Mini 2] Andruxcx:
Any info on when the next update is coming out?
[HTC One Mini 2] stkl:
Could potentially be at any time. I got my own builds keeping up with latest Android/LOS development (and security patches). I got my own builds keeping up with latest AOSP/LOS development, no problems so far. But despite the ZRAM change nothing really new....

As June is already over, I'd suggest scheduling the next "official" release for the end of next week (next Android Security Bulletin likely on July 5).
[HTC One Mini 2] Andruxcx:
What about the camera, gps, wifi/radio signal and etc. Fixes?
[HTC One Mini 2] stkl:
I personally do not have any of those issues and my time's short at the moment, so I didn't spent effort on this, sorry.... If [MENTION=7570463]nightcore500[/MENTION] did so, at least it's not published.

Some WiFi drivers received an update in the latest official Kernel upstream though. They work fine, but I can't tell if any of these changes fixes your issues.
[HTC One Mini 2] Andruxcx:
Oke. Thanks for the info.
[HTC One Mini 2] HandyBesitzer:
I saw this is Android 7.x how stable is it?? Does everything work?? SD, WiFi, Radio, LTE, Camera,..?
[HTC One Mini 2] Marvbox:
All problems were already discussed here.

My recommendation, use gapps pico!
[HTC One Mini 2] Andruxcx:
Augmented reality doesn't seem to be working correctly
[HTC One Mini 2] Andruxcx:
[MENTION=1199534]stkl[/MENTION] could you please upload your updated version? I cant deal with the bs the current one is giving me
[HTC One Mini 2] xxxmadraxxx:
Well, after all the probs I had with general sluggishness [especially with the camera] of this ROM, as outlined in my many previous posts in this thread, I finally bit the bullet a couple of days ago and rolled back to stock ROM [rooted].

It was quite a battle to get things returned to stock and everything working properly [I had no end of probs getting Google Play to download *anything*]. But the Mini2 is now running like a dream and the camera launching in a couple of seconds.

I don't know what magic HTC worked when they built the original ROM for this phone but the bottom line is "it just works" whereas all of the custom ROMs I've tried on it have been, frankly, unusable due to sluggishness and freeze-ups. I'm not wanting to denigrate the efforts of the people who've put so much time into trying to bring these newer versions of Android to the Mini 2. They deserve a pat on the back for their efforts. But, bottom line is; if you want the Mini 2 to perform smoothly, just settle for KitKat and stock ROM.
[HTC One Mini 2] tryllz:
[MENTION=516742]skt[/MENTION]l Is your LOS version off the CM13 build as well ?!
[HTC One Mini 2] stkl:
My version is based on nightcore500's 14.1 device tree, but I'm currently rebasing our Kernel on top of the latest official LOS kernel sources. This includes some drivers (e.g. WiFi), that have been updated while our 0.2 release still uses older versions from CM13 (always have to figure out why we used those and if an updates causes trouble).

I just built a release 5 minutes ago. Let me test a little and if it's fine I will upload it tomorrow. Btw. Android bulletin 07/2017 has been published today, will grab the upstream as soon as available.
[HTC One Mini 2] Finusfix:
I've seen Nightcore yesterday in the dev chat. Looks like he's actually working on the USB mode problem :fingers-crossed:

If I have understood correctly he will publish 0.3 this weekend
[HTC One Mini 2] stkl:
[MENTION=8229529]Andruxcx[/MENTION] here is my latest build...

I don't want to compete against nightcore, so I might remove the upload at any time, when the next version is released. All changes are OpenSource (forked repos on GItHub).

Edit:

Some devices experience boot loops with this build, don't flash if you don't accept the risk!

-- down --

0.3 is out, use that build
[HTC One Mini 2] nightcore500:
No problem.

We can't use the newer prima source. It looks like that older models have a different chipset (or it is related to the older baseband version). The newer version lead to a kernel panic during the cold start phase on these models, which ends in a bootloop. That was the first problem with CM13. You can find the discussions about this problem in the CM13 thread on the first 10 pages.
[HTC One Mini 2] Finusfix:
Yup, I can confirm this. My device stucks in bootloop with this build :/

Can you tell us when the next release will come? :)
[HTC One Mini 2] Andruxcx:
Thank you :good:
[HTC One Mini 2] nightcore500:
I think tomorrow evening. :good:
[HTC One Mini 2] Andruxcx:
Happened to me too
[HTC One Mini 2] stkl:
Interesting. I'm using the linked ROM's kernel for two days now and neither got Kernel Panics nor boot loops... Getting the feeling I got damn luck with my hardware.