[ROM] LineageOS 14.1 (official) - ZTE Trek 2 ROMs, Kernels, Recoveries, & Other Deve

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First time install Instructions
Use these instructions when coming from any other ROM (stock, aokp, etc.)
Download ROM.
Download GAPPS if desired.
Boot into recovery.
Backup your current data.
Format/Wipe data.
Flash ROM.
Flash GAPPS if desired.
Reboot.
Upgrade instructions
Use these instructions when upgrading from a previous Lineage build.
Download ROM.
Boot into recovery.
Backup your current data.
Flash ROM.
Reboot.
Flashing instructions
There are two main ways to flash files onto your phone: local and sideload. Most people are only familiar with local, but sideload is much quicker and easier if you are at a PC.
Sideload
Download the ZIP file(s) to your PC. In TWRP, select advanced and then sideload. Swipe the slider to begin, then on your PC run "adb sideload <filename>".
Local
Download and/or copy the ZIP file(s) to your phone. Note whether they are on internal storage (the default) or the sdcard. In TWRP, select install, find your file, and select it.
Status
Current status: Stable
Known issues
None (hopefully).
Download
LineageOS Downloads - jasmine
Tested with opengapps arm64 7.1 micro.
Sources
Device Tree
Kernel

remover post

I've flashed this rom and am very happy with it. Looks like it'll take some time before people find out the device is bootloader unlockable and be able to flash roms. Thank you OP for working hard on this one. I use my K88 everyday for watching youtube vids and reading books via 'coolreader' app.

Maybe my question here maybe out of place, but is it possible that we will see an update to Lineage OS 15.1 on our Beloved AT&T Trek 2 HD in the for see able future?, @tdm. Any plan in the pipe line for Oreo?
Thanks to the entire community here.

I'm working on it. Hopefully in the next few weeks.
ativi said:
Maybe my question here maybe out of place, but is it possible that we will see an update to Lineage OS 15.1 on our Beloved AT&T Trek 2 HD in the for see able future?, @tdm. Any plan in the pipe line for Oreo?
Thanks to the entire community here.
Click to expand...
Click to collapse

Hello. Is it stable to use? Any bugs noticed?

It is 100% stable, without errors
-danger- said:
Hello. Is it stable to use? Any bugs noticed?
Click to expand...
Click to collapse
Sent from my K88 using Tapatalk

Been using this for a week or so, it's entirely stable and has breathed new life into this tablet.
FYI, if anyone else uses AT&T service on this, you may need to change the default APN from "AT&T GoPhone (pta)" to "AT&T Broadband (broadband)" for cellular data to start working.
Getting Oreo on here would be icing on the cake, thanks so much for your hard work @tdm

Finally took the plunge and rooted and installed LOS yesterday. Happy to find the guide, and that there's an official LOS build for it. I was about ready to give the tablet to my kids (not anymore!). Anxiously awaiting a 15 build. Thanks to @tdm and the others who are working on this!

I liked it, this excellent 100% stable, good sound, works send and receive message, excellent to read book, comics and news, watch 1080p movie and 60fps videos,good internet connectivity both wifi and mobile data
good job @tdm
but I know that the phone call does not work, maybe one day I'll make it work
Sent from my K88 using Tapatalk

Hi, tried following the instructions and have run into an issue. Tablet is out of the country USA variant.
my current recovery is this:
ZTE/K88/jasmine
6.0.1/MMB29M/20160928.115457
I tried running jasmine-tool to install jasmine-twrp. It appeared successful, but the recovery remains the stock recovery instead of twrp.
Some back reading led me to believe that I could only install twrp recovery if my tablet was updated to stock K88V2.0.0B17.
So I tried to 'Apply update from SD card' the "343410B1702K88V2.0.0B17(SD card software).zip" file.
I get the error: 'Couldn't mount /sdcard. Installation aborted.'
So I attempted adb sideload P895A80V1.0.0B31_SD.zip
got the error: 'This package is not ks package! Installation aborted.'
So I can't update from stock 6.0.1 via SD card because stock recovery won't mount SD card.
I can't update recovery to TWRP because jasmine tool require 7.0.X recovery.
Any suggestions or have I missed something? Can i use jasmine tool to write the recovery from "343410B1702K88V2.0.0B17(SD card software ).zip" inside the update.zip ? TIA

Grab the b17 update file (which it sounds like you did), extract the update.zip file and throw that on clean SD card. Put that in the tablet, and then run the update utility from the 6.x stock rom. Should get you updated to the necessary 7.x stock, so you can then do jasmine, twrp, and LOS. That worked for me.

cwassman said:
Grab the b17 update file (which it sounds like you did), extract the update.zip file and throw that on clean SD card. Put that in the tablet, and then run the update utility from the 6.x stock rom. Should get you updated to the necessary 7.x stock, so you can then do jasmine, twrp, and LOS. That worked for me.
Click to expand...
Click to collapse
Yes correct. My googleFu of "Couldn't mount /sdcard." led me to a few posts citing file system issues and recommended reformatting. I backed up and then reformatted my SD card using the stock Marshmallow 6.x. Dropped the "update.zip" file from the K88V2.0.0B17 archive into the SD card root directory and booted into stock Marshmallow 6.x recovery. Performed the 'Apply update from SD card' and it mounted the SD card and proceeded with the update.
Perhaps we could specify in the instructions that K88V2.0.0B15-17 (Nougat) is a Pre-req before proceeding with the jasmine-tool. Thanks again :good: :highfive:

Display sleep issue
Just installed this today using the 8-31 build. I am having an issue where the display timeouts at 15 seconds no matter what I have the setting at.

Audio Issues
I installed this LineageOS version, everything seemed to be working fine, but I noticed in the kid's game Endless Alphabet, it appears that the audio is very messed up(didn't occur in stock ROM), during normal gameplay it's very quiet, but at the end of each section a small MP4 video plays, and it's full volume.
Not sure what would cause application volume to fluctuate like that.

BSPEAR44 said:
Just installed this today using the 8-31 build. I am having an issue where the display timeouts at 15 seconds no matter what I have the setting at.
Click to expand...
Click to collapse
Having basically the same issue. Timeout is set to 1 minute, and goes into a deep sleep. Requires holding the power button and reboot.

footwork* said:
Having basically the same issue. Timeout is set to 1 minute, and goes into a deep sleep. Requires holding the power button and reboot.
Click to expand...
Click to collapse
So I fixed my issue of the device turning the screen off after 15 seconds, by doing a factory reset and when setting up the tablet selecting new device instead of restore from backup.
However it was also suggested to me that I try reinstalling the b17 firmware again. I never did try that since the issue was resolved with the reset. It sounds like your issue is completely different, but you could try these.

this is interesting https://medium.com/@gael_duval/leaving-apple-google-e-first-beta-is-here-89e39f492c6f
/e/ OS Available now

Question to everyone. Will Lineage OS fixed the 128G max mSD or this is a hardware limitation?
I just got a 200G mSD today, original ATT 7.1.1 won;t recognized it - micro SD exceed.

siaopao said:
Question to everyone. Will Lineage OS fixed the 128G max mSD or this is a hardware limitation?
I just got a 200G mSD today, original ATT 7.1.1 won;t recognized it - micro SD exceed.
Click to expand...
Click to collapse
on the LOS page of our device it says it supports 256GB SD
https://wiki.lineageos.org/devices/jasmine

Related

[Q] how to root and installing CM 10.1.2 on i9000

I searched for more than 3 hours to root and install CM 10.1.2 on my Samsung Galaxy S i9000
but i dont find anything good i lost my mobile :crying: then it works again :silly:
my mobile information:
GT-I9000
Firmware Ver: 2.3.3
Baseband Ver: I9000JHJV9
Build number: GINGERBREAD.JHJVG
Thank you.
i found it to use these files and kernels
https://app.box.com/shared/z2jmmzres0
a video but in Arabic
http://www.youtube.com/watch?feature=player_embedded&v=6WiuaSlKYC8#t=244
is it right????
sycolon said:
GT-I9000
Firmware Ver: 2.3.3
Baseband Ver: I9000JHJV9
Click to expand...
Click to collapse
Follow this and root only after your firmware is 2.3.6
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​
Use Samsung Kies and update your phone to a newer build.
Download a root package from here (search for your build after the update) : http://forum.xda-developers.com/showthread.php?t=788108
Download odin3 1.85 and flash the rom (in odin only put the tar file in the pda box - the phone has to be in download mode {volume down+power+home pressed}) .
Go online (google play) on the phone and download the clockwork mod and install it.
Download the latest stable CM10.1.2 from here: http://download.cyanogenmod.org/?type=stable&device=galaxysmtd
Put the cm10 archive on the sd card and power off the phone.
Enter in the recovery mode (volume up + power + home) and using the volume select Wipe Data/Factory Reset and in advanced Wipe Dalvik Cache. Go back and select install zip from sd card. If it's done quick do the install from zip again.
The full tutorial here: http://forum.xda-developers.com/showthread.php?t=1494493
Do the root like i said because it's easy and then follow the guide from point 4 "• Using the volume buttons to navigate up and down select..."
After search for a google play app pack (gapps) and put it in the sd card and install it using recovery mode.
I did this yesterday and it works great.
i made the same as i told you in the last post
"i found it to use these files and kernels
https://app.box.com/shared/z2jmmzres0
a video but in Arabic
http://www.youtube.com/watch?feature...uaSlKYC8#t=244
is it right????"
and i installed CM 10.1.2
and all i s ok for now, i have 2 problems no service and the mobile reboot from its own when i dont use it....crazy
is it possible that i have the problem cuz i didänt make Lag Fix for it????
do you have the clockwork mode installed?
go back in recovery mode and wipe data/dalvik again and install cm10 again.
sycolon said:
is it possible that i have the problem cuz i didänt make Lag Fix for it????
Click to expand...
Click to collapse
yes i have it... i will try .... do i install CM 10.1.2 ?
Yes.
i tried to make it but still the same problems
i made the CM 10.1.3 and still the same problem, automatic rebooting wjen i dont use the mobile and no service .....
yes finally i fix it, thanks guys for all, but i did it in my way yeaaaaaaaaaaaah
Does it work? Are you happy with CM?:good:
sycolon said:
yes finally i fix it, thanks guys for all, but i did it in my way yeaaaaaaaaaaaah
Click to expand...
Click to collapse
yes i'm using the CM 10.1.3 Rc2 and its fantastic........... i love it
the only thing i found weird in the CM that he mentioned that the memory is 368MB just of 512MB !!!!
sycolon said:
the only thing i found weird in the CM that he mentioned that the memory is 368MB just of 512MB !!!!
Click to expand...
Click to collapse
Don't worry about that. Part of memory has been reserved by the CM. You may like the CM10.2, it is in nightly stage but even faster than 10.1.3 and you will have about double battery life. But read very carefully whole first post before installing it. It is bit odd way comming from cm10.1.3
Or quote my text (reply this e-mail) and I will send you the workflow, it isn't absolutely clear written in the opening post ofnthe thread.
tetakpatak said:
Don't worry about that. Part of memory has been reserved by the CM. You may like the CM10.2, it is in nightly stage but even faster than 10.1.3 and you will have about double battery life. But read very carefully whole first post before installing it. It is bit odd way comming from cm10.1.3
Or quote my text (reply this e-mail) and I will send you the workflow, it isn't absolutely clear written in the opening post ofnthe thread.
Click to expand...
Click to collapse
thanks you so much then i wish to have the instructions about upgrading to 10.2
Update-Desc http://forum.xda-developers.com/showthread.php?t=2385178
The rest of RAM is reserved for audio/video coding ,example camera for HD-mode and kernel for the linux system
Some Kernel support RAM up to 408MB but with no HD-support then...
sycolon said:
the only thing i found weird in the CM that he mentioned that the memory is 368MB just of 512MB !!!!
Click to expand...
Click to collapse
More information about RAM (in example the semaphore kernel ...http://www.semaphore.gr/how-to/use-semaphore-jb
"Bigmem
When the kernel boots, it reserves some RAM to be used by some drivers (video, capture, JPG) for DMA (Direct Memory Access). In Linux kernel this reservation have to be done only during boot. It was found that using less reserved memory for video capture, the kernel can operate normally without issue with the only regretion that 720p video recording is not possible. Enabling this option will leave ~13MB more available RAM.
Phone must be rebooted to enable this feature. After the device powers down the information about this option is lost and you have to reboot the phone again.
Default: Disabled"
freakymod2120 said:
Update-Desc http://forum.xda-developers.com/showthread.php?t=2385178
The rest of RAM is reserved for audio/video coding ,example camera for HD-mode and kernel for the linux system
Some Kernel support RAM up to 408MB but with no HD-support then...
Click to expand...
Click to collapse
Upgrade workflow to the CM 10.2
sycolon said:
thanks you so much then i wish to have the instructions about upgrading to 10.2
Click to expand...
Click to collapse
Ok, from CM10.1x it should work like this:
This is the thread of CM10.2 development for the i9000:
http://forum.xda-developers.com/showthread.php?t=2385178
Read whole the first post there.
Preparation:
Before upgrading, first prepare all this for the case anything goes off the plan (it shouldn't, but who knows...):
make nandroid backup
download zip files of your presently used ROM (cm10.1.3) and gapps for Android 4.2.2 and save them in your phone
download zip files of the new ROM you want to install (cm10.2) and gapps for Android 4.3 and save them in your phone
boot your phone into the recovery mode (CWM) and check if all zip files are visible
Now if all the files are visible you can upgrade (some CWM recovery versions can read zip files only from the external SD, some other versions only from the internal SD card, some both). If they are not visible, don't even try upgrade (and don't wipe any data) but reboot phone and move the zip files to another place (for example if they were not visible on internal SD, move them to the external SD card) and after you moved the files, do again the check like I wrote you above.
Upgrade:
make factory reset/wipe data
wipe cache
wipe dalvik cache under "advanced"
install zip of the CM10.2 nightly build (possibly you need to install twice, as it uses different re-partition and only warns the first time)
install the Gapps for 4.3 right after, while still in recovery
while still in recovery go to "advanced restore" and restore only /data from your last nandroid backup of the cm10.1.3
go back to first menu, reboot
enjoy, all your data from presently used cm10.1x build should be there, including Google account
If anything should go wrong, make the same procedure like you did for the installing CM10.2, wipe all and make factory reset, after that just instead of the CM10.2 zip flash your CM.10.1.3 zip and gapps for Android 4.2.2, reboot, boot again to recovery, restore your whole nandroid backup of the CM10.1.3 build.
Let me know if it worked well

[ROM][9.0.0][UNOFFICIAL]LineageOS 16.0 [SERRANOVELTE GT-I9195I]

LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed.
All the source code for LineageOS is available in the LineageOS Github repo.
Whats working?
WiFi
RIL
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
IR
Lights
All Sensors
Sound / vibration
Mobile data
LiveDisplay support
Selinux enforce
Installation:
Download the zip(s)
Install a compatible Recovery (TWRP 3.2.x or higher is recommended)
Perform a backup of your current ROM (Optional)
Make a full wipe (system, data, cache, dalvik)
Flash LineageOS
Optional: Install the Google Apps
Reboot
Source code:
https://github.com/lineageos
https://github.com/Galaxy-MSM8916
Download:
rom: lineage-16.0
XDA:DevDB Information
LineageOS, ROM for Samsung Galaxy S4 mini VE(GT-I9195I)
Contributors
mernurisha
ROM OS Version: 9.0.0_r46
Security patch level: August 2020
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2019-08-17
Last Updated 2020-08-15
I'm going to try this rom. thank you very much mernurisha
ps: so far everything i need works properly. perfect rom!
Apart from not detecting my SD-card your ROM is the best LineageOS I have ever used.
ffox.pl said:
Apart from not detecting my SD-card your ROM is the best LineageOS I have ever used.
Click to expand...
Click to collapse
Thanks for your feedback.
Can you please test this kernel and say if this recognizes your sd-card?
(Wipe cache, dalvik after kernel installation).
mernurisha said:
Thanks for your feedback.
Can you please test this kernel and say if this recognizes your sd-card?
(Wipe cache, dalvik after kernel installation).
Click to expand...
Click to collapse
1. full wipe
2. install lineage-16.0-20190816-UNOFFICIAL-serranovelte.zip
3. wipe cache/dalvik
4. install LineageOS_Pie_Kernel.zip
5. wipe cache/dalvik
6. reboot system
and... ...no effects, this does not recognize my sd-card.
ffox.pl said:
1. full wipe
2. install lineage-16.0-20190816-UNOFFICIAL-serranovelte.zip
3. wipe cache/dalvik
4. install LineageOS_Pie_Kernel.zip
5. wipe cache/dalvik
6. reboot system
and... ...no effects, this does not recognize my sd-card.
Click to expand...
Click to collapse
I always use Samsung SD card for Samsung smartphone and never had a problem also with other rom either. try that who knows
ffox.pl said:
1. full wipe
2. install lineage-16.0-20190816-UNOFFICIAL-serranovelte.zip
3. wipe cache/dalvik
4. install LineageOS_Pie_Kernel.zip
5. wipe cache/dalvik
6. reboot system
and... ...no effects, this does not recognize my sd-card.
Click to expand...
Click to collapse
Unfortunately, I can not help you anymore. I have no problems with my sd card from Kingston 64GB.
It is difficult for me to understand. Because I don't have this problem.
Maybe you need to format your card with GParted or another software. Sorry.
miccca said:
I always use Samsung SD card for Samsung smartphone and never had a problem also with other rom either. try that who knows
Click to expand...
Click to collapse
I have no idea too. Others roms work perfect with this SD-card. I am going to buy a new one. I will give a report when I get it.
---------- Post added at 05:24 PM ---------- Previous post was at 05:20 PM ----------
mernurisha said:
Unfortunately, I can not help you anymore. I have no problems with my sd card from Kingston 64GB.
It is difficult for me to understand. Because I don't have this problem.
Maybe you need to format your card with GParted or another software. Sorry.
Click to expand...
Click to collapse
I have no idea as well. Others roms detect this SD-card. I have just ordered Samsung Evo Plus 64GB MicroSDXC. It will come out soon.
@gdynia don't forget format every time you sd card before using, but I assume you know
No problem with my 64GB Samsung EVO+ removeable memory card formated FAT32 with 32,768 allocation, using guiformat.exe (which is a free Windows app).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Great work, thank you!
The proximity sensor appears to work fine for ambient display, however some options are missing from the ambient display settings, that were present in danil_e71's builds: there is no option to show notifications on remove from pocket (it appears to only show them for a "wave" gesture) and also there is no option to use the proximity sensor to prevent the power button from waking the screen while it is in a pocket. These would be very handy if they could be added!
Thanks again.
MrGoodtunes said:
No problem with my 64GB Samsung EVO+ removeable memory card ...
Click to expand...
Click to collapse
Maybe I spoke too soon, because of trouble after 3 days with everything working fine.
Problems started when I tried to install my favorite old version of Firefox from removeable SD card. Install went okay, but Firefox had some problem and could not open. So I uninstall'd it and went to PlayStore for latest version. But its download show'd only pending, same for any PlayStore download. So I clear'd PlayStore cache, data, and restarted device. This brought notification indicating my SD card had corrupted, needed formating! But desktop PC shows card is totally okay, and TWRP see's card as okay too.
For now, I've gone back to Danil's j33 Pie. Will try another clean install of this build when I find time, because it starts more smoothly (doesn't have the sudden bright screen flash that Danil's has) and mainly because @mernurisha is being very conscientious about making it work properly.
I've switched over to using this as my main phone now, no issues with SD card (64GB Samsung EVO Plus) so far. It is formatted to expand internal storage.
Unrelated to the above: I have no idea if this is a LineageOS problem, a device problem, or other, but Telegram video selfies have a squished aspect ratio. I've created a ticket on the Telegram-FOSS github: https://github.com/Telegram-FOSS-Team/Telegram-FOSS/issues/358
I don't really expect anyone to know how to fix that, but I thought I'd mention it in case anyone else has a similar issue
mernurisha said:
Unfortunately, I can not help you anymore. I have no problems with my sd card from Kingston 64GB.
It is difficult for me to understand. Because I don't have this problem.
Maybe you need to format your card with GParted or another software. Sorry.
Click to expand...
Click to collapse
A new Samsung Evo Plus 64GB MicroSDXC has been detected and worked fine so far. Kingston memory has never let me down but this time my Kingston microSDXC 64GB UHS-I Class 10 has failed. Probably it has a hidden defect. Thank you all for help.
---------- Post added at 12:25 PM ---------- Previous post was at 12:23 PM ----------
MrGoodtunes said:
Maybe I spoke too soon, because of trouble after 3 days with everything working fine.
Problems started when I tried to install my favorite old version of Firefox from removeable SD card. Install went okay, but Firefox had some problem and could not open. So I uninstall'd it and went to PlayStore for latest version. But its download show'd only pending, same for any PlayStore download. So I clear'd PlayStore cache, data, and restarted device. This brought notification indicating my SD card had corrupted, needed formating! But desktop PC shows card is totally okay, and TWRP see's card as okay too.
For now, I've gone back to Danil's j33 Pie. Will try another clean install of this build when I find time, because it starts more smoothly (doesn't have the sudden bright screen flash that Danil's has) and mainly because @mernurisha is being very conscientious about making it work properly.
Click to expand...
Click to collapse
While zipping and unzipping a file Samsung Evo Plus 64GB MicroSDXC was corrupted for me once as well. It had to be formatted to work. It was on danil_e71's LOS 16 so this is probably not the mernurisha's LOS 16 fault.
ffox.pl said:
... this is probably not the mernurisha's LOS 16 fault.
Click to expand...
Click to collapse
Agreed. My SDcard issue appears to simply be Google's way of assuring safety, security; by ruling out a card that contains old unsupported software causing issues with latest OS.
Mernurisha's rom is one of the best I have used. One bothers me. Although the call volume is set to the maximum, the caller can be heard very quietly. Any ideas?
The second disadvantage is that in the mode when the loudspeaker is switched on, the interlocutor hears feedback so loud and conversation is practically impossible.
ffox.pl said:
Mernurisha's rom is one of the best I have used. One bothers me. Although the call volume is set to the maximum, the caller can be heard very quietly. Any ideas?
The second disadvantage is that in the mode when the loudspeaker is switched on, the interlocutor hears feedback so loud and conversation is practically impossible.
Click to expand...
Click to collapse
Try to install the sound-fix of PixelExperience thread over TWRP. Is the same for all pie roms.
Maybe this helps.
my only problem is when i switch on the loudspeaker then my conversation partner suffers from reverberation
I already flashed sound fix but the problem is still there I sincerely hope that mernurisha can tackle this problem
miccca said:
my only problem is when i switch on the loudspeaker then my conversation partner suffers from reverberation
I already flashed sound fix but the problem is still there I sincerely hope that mernurisha can tackle this problem
Click to expand...
Click to collapse
I've never used a loudspeaker on until now. I'll take a look.
Can i found somewhere rom to GT-I9195? no VE model.. - because i get "updater process ended with signal 4" error message

[ROM][OFFICIAL][voyager][11] LineageOS 18.1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/voyager
Downloads :
https://download.lineageos.org/voyager
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
[ protip: These builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261777345 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Reboot to recovery mode (both Lineage recovery and TWRP will work)
6. Flash https://androidfilehost.com/?fid=4349826312261712574
7. Profit?
First things first...Thank you!
Also, probably a noob question but, I am on 17.1 already, will I have to flash it via Lineage recovery or twrp to test it?
I suppose the update will only work when there is an official version.
hamirali said:
First things first...Thank you!
Also, probably a noob question but, I am on 17.1 already, will I have to flash it via Lineage recovery or twrp to test it?
I suppose the update will only work when there is an official version.
Click to expand...
Click to collapse
Official lineage recovery won't accept my dev-keys so you need to go with TWRP. I don't recommend trying to update data from 17.1 tho.
LuK1337 said:
Official lineage recovery won't accept my dev-keys so you need to go with TWRP. I don't recommend trying to update data from 17.1 tho.
Click to expand...
Click to collapse
I was able to flash Lineage 18, everything seems ok except that the SD card is not visible when in system, however can access it if removed and reinserted.
Can manage.
hamirali said:
I was able to flash Lineage 18, everything seems ok except that the SD card is not visible when in system, however can access it if removed and reinserted.
Can manage.
Click to expand...
Click to collapse
Are you on first or second build?
LuK1337 said:
Are you on first or second build?
Click to expand...
Click to collapse
Oops! first build. Didn't realise there was another. Btw can you please advise on the gapps version. Thanks!
hamirali said:
Oops! first build. Didn't realise there was another. Btw can you please advise on the gapps version. Thanks!
Click to expand...
Click to collapse
No idea about gapps, I don't have them on my current R devices.
LuK1337 said:
No idea about gapps, I don't have them on my current R devices.
Click to expand...
Click to collapse
Successfully flashed and running well without any issues. Thanks!
LuK1337 said:
No idea about gapps, I don't have them on my current R devices.
Click to expand...
Click to collapse
On the 4th build, all seems to be working fine, apart from a small issue that when making calls the dialling screen doesn't appear, but it does successfully place the call. The issue is when I want to close the call (hang up) as that screen hasn't loaded.
Can manage, as usually I just let the other person hang up. Receiving calls is fine.
Otherwise, great work!
hamirali said:
On the 4th build, all seems to be working fine, apart from a small issue that when making calls the dialling screen doesn't appear, but it does successfully place the call. The issue is when I want to close the call (hang up) as that screen hasn't loaded.
Can manage, as usually I just let the other person hang up. Receiving calls is fine.
Otherwise, great work!
Click to expand...
Click to collapse
This sounds like gapps issue. Make sure that phone app is set in Settings -> Apps & notifications -> Default apps.
LuK1337 said:
This sounds like gapps issue. Make sure that phone app is set in Settings -> Apps & notifications -> Default apps.
Click to expand...
Click to collapse
You were absolutely right...issue resolved. Thanks!
Currently on lineage-18.0-20201011 and enjoying the slide out volume panel and enhanced display size setting. Great!
Testing lineage-18.0-20201019 and all seems good. The only small issue I keep having is with the camera, it freezes.... but I do not use it that much anyway.
how to update lineage-18.0-20201019 on LineageOS 18.0 20201018 without deleting
jacky51 said:
how to update lineage-18.0-20201019 on LineageOS 18.0 20201018 without deleting
Click to expand...
Click to collapse
I am no expert, but I don't think we can at this moment update without deleting or wiping out. Usually it takes less than 30 mins for me to update, flash gapps and restore everything else. If you use WhatsApp a lot, remember to back it up.
I will wait for LineageOS 18.0 20201018 to work fine thanks
hamirali said:
I am no expert, but I don't think we can at this moment update without deleting or wiping out. Usually it takes less than 30 mins for me to update, flash gapps and restore everything else. If you use WhatsApp a lot, remember to back it up.
Click to expand...
Click to collapse
lol, just do the same thing as in initial installation except no wipes. Make sure to not skip rebooting to recovery between flashing Lineage and gapps.
LuK1337 said:
lol, just do the same thing as in initial installation except no wipes. Make sure to not skip rebooting to recovery between flashing Lineage and gapps.
Click to expand...
Click to collapse
OK, I was rebooting to recovery between flashing Lineage and gapps, but I was doing an initial wipe before flashing the newer build...
Everything works fine. Thanks for your work!

[ROM][UNOFFICIAL][12.1][DISCONTINUED] LineageOS 19.1 for Galaxy Tab S6 Lite Exynos

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Follow the instructions here
Downloads:
Builds: https://lineage.linux4.de
GApps: MindTheGapps
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
DO NOT Report bugs while having Magisk installed (especially with Zygisk enabled)
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4, programminghoch10
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_gta4xl/tree/lineage-19.1
Requirements:
Any R based firmware installed on your device.
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk
Magisk
I strongly recommend to use Lygisk instead,
which is a fork of Magisk that aims to improve support for devices with FBE that can't (and shouldn't anyways!) decrypt userdata in recovery,
this will also fix OTAs getting stuck while having installed Magisk.
Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
Known issues
LineageOS specific features like livedisplay (for now)
You tell me
I am on your unofficial 18 and this just pop up in updater, is it safe to do OTA? Thanks for your efforts!
fzzt said:
I am on your unofficial 18 and this just pop up in updater, is it safe to do OTA? Thanks for your efforts!
Click to expand...
Click to collapse
Always follow this rule of thumb: it is never safe to dirty flash a completely different build on top of an older build (i.e. flashing 19.0 on top of 18.1, or 18.1 on top of 17.1, etc.). At best, you'll find yourself having random problems all over the place; at worst, the ROM will refuse to load. Best thing to do whenever going from one major release to another (or from one completely different ROM to another) is backup your apps and data, wipe data and caches and perform a clean flash, then restore your apps and data. It's a fair bit of work, to be sure, but it's the best way to avoid problems.
Sim card dont work, IMEI dont show, gapps cant install. Any ideas?
electro_vinyl said:
Sim card dont work, IMEI dont show, gapps cant install. Any ideas?
Click to expand...
Click to collapse
About the SIM issue, there's two things:
1. (more likely) You flashed the wrong build (gta4xlwifi instead of gta4xl) or in other words, flashed the WiFi only version firmware.
2.(Unlikely but could happen) You corrupted your baseband somehow as I had a similar situation with my Redmi Note 9 with a corrupted baseband so basically the IMEI was all zeros. That was also the reason why the SIM card didn't work.
You could try to install the original firmware with odin and check functionality and try again.
About the gapps issue
Did you install it for the correct architecture (arm64 not arm)?
Does it show error messages?
Macuway said:
About the SIM issue, there's two things:
1. (more likely) You flashed the wrong build (gta4xlwifi instead of gta4xl) or in other words, flashed the WiFi only version firmware.
2.(Unlikely but could happen) You corrupted your baseband somehow as I had a similar situation with my Redmi Note 9 with a corrupted baseband so basically the IMEI was all zeros. That was also the reason why the SIM card didn't work.
You could try to install the original firmware with odin and check functionality and try again.
About the gapps issue
Did you install it for the correct architecture (arm64 not arm)?
Does it show error messages?
Click to expand...
Click to collapse
With the latest build, it's all fixed!
Installed Lineage 19 last weekend on my P-610. You can flash the rom.zip, GApps and Magisk in Recovery from SD-card, so no need to sideload with adb. I have a problem with Google Playstore, it lags a lot (pending...) and installing an app like Gmail takes a long time. Now it even stopped working. Will try it later with NikGApps for Android S
Hi, it seems audio is not working.
It's just me?
Any help please.
M
minoltista said:
Hi, it seems audio is not working.
It's just me?
Any help please.
M
Click to expand...
Click to collapse
Are you on today's build already?
If so try again with that please - your device might be hw revision 9 which uses different audio drivers and wasn't supported in my kernel until today
Also could check the output of adb shell getprop ro.boot.revision to confirm it's rev 9
Linux4 said:
Are you on today's build already?
If so try again with that please - your device might be hw revision 9 which uses different audio drivers and wasn't supported in my kernel until today
Also could check the output of adb shell getprop ro.boot.revision to confirm it's rev 9
Click to expand...
Click to collapse
Just installed and it works! Thanks !!!
guys how do you flash this? I follow all the steps and when I do adb sideload <lineage os> it fails at 47%?????
error 21 log on the tab
langamer101 said:
guys how do you flash this? I follow all the steps and when I do adb sideload <lineage os> it fails at 47%?????
error 21 log on the tab
Click to expand...
Click to collapse
got it working guys. no need to help anymore.
Does anyone know why gboard force closes every time i try to install? I cleared all storage, played with permissions. Nothing worked.
First of all, I want to say thank to @Linux4 for this release Secondly, I want to ask comrads how to install MicroG on this build? If you can step by step, I'm new to custom firmware
how is newest recovery
Screenshots please
Working nicely, I'm currently getting a weird issue with the 2021-11-27 gta4xl build.
It's extremely weird but with quiet songs there's some kind of audio ducking going on.
Song it was most obvious on was Air - Bad and Sad 4.2 Vagabond Demo for example but it sounds like it's trying to cut out the audio or something.
Device was bought a few days ago so I'm guessing it'll be the latest hw revision.
lobotomite said:
Working nicely, I'm currently getting a weird issue with the 2021-11-27 gta4xl build.
It's extremely weird but with quiet songs there's some kind of audio ducking going on.
Song it was most obvious on was Air - Bad and Sad 4.2 Vagabond Demo for example but it sounds like it's trying to cut out the audio or something.
Device was bought a few days ago so I'm guessing it'll be the latest hw revision.
Click to expand...
Click to collapse
I have the same thing with any sound on the tablet This is especially noticeable when playing songs on spotify.

Development [ROM][OFFICIAL][12.L] DerpFest Shinju for Redmi Note 11 [SPES|SPESN]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device.
You have been warned.
DerpFest Shinju | OFFICIAL | Android 12.1
Build date: 07/06/22
Device: Redmi Note 11 (spes/spesn)
Download ROM 07/06/2022
Changelogs :
- Fixed overlay
- Fixed long boot
- Fixed mic
- Added refresh rate
- Lag fix
- Launcher fix
- Fixed some more bugs
- Fixed offline charging
- No bugs.
- More Changes
Flashing steps :
Download TWRP (first time needed)
• Formate data
• Reboot to recovery
• Flash rom (ignore red lines)
• Wipe data , cache & dalvik , metadata
• Open avdance menu install twrp in install ramdisk option
• Reboot to system
Bugs none for now, feel free to report if you find any in the comments below.
Kernel source Link
Support Group
Redmi note 11 Spes/Spesn Group
The process for 4/128 variant is the same as 4/64, right?
canIchangemyname said:
The process for 4/128 variant is the same as 4/64, right?
Click to expand...
Click to collapse
yes the same
NamCap said:
yes the same
Click to expand...
Click to collapse
That's good to know! Thanks.
Thank you so much for this Official Build. I'm using it as a daily driver.
Will May build come out?
xx_yolonoob_xx said:
Before flashing the rom, here's some bugs I've faced (will update as they come up, could be because of the kernel and not the rom itself):
Restoring from a backup on Google results in fingerprint not working for screen unlock. Restore at the setup on first startup or after continuing setup from the notification, same result. Fingerprint does work for payment apps.
Really jumpy adaptive brightness.
Cannot file transfer in USB, in ROM and recovery. USB controlled by setting stuck to "this device", won't switch. Only way to flash for me was to adb sideload. SD card or OTG might be easier.
Unable to flash twrp to ramdisk as of now, system/data partition is only available after format data in twrp.
And for the not bug but annoying during flashing, there's no recovery partition. Recovery is loaded into the boot partition. And there's two fricking slots. It's nice that we can have two recoveries, TWRP and crdroid, but annoying nonetheless.
Ported over from MIUI Global 13.0.9.0, I'd stay with MIUI and wait for the kernel to be released if I knew the drawbacks beforehand.
Click to expand...
Click to collapse
Same bugs as above, including:
Stock camera app broken
Personal pet peeve, derpfest recovery doesn't allow switching slots
Can't get SD card to work. I setup the SD card in SPES as portable storage, format, move it to another Android (RN3), copy a file from pc to RN3 through file transfer mode, shows up in files app, SD card back to SPES and asks for a format to use the SD card. (It sucks that there's no file transfer nor a way to send files from PC to SPES using an SD card. Don't have a type c OTG lying around)
Plus points:
Great idle battery management so far, attached a pic below. Haven't seen deep sleep after setting up all of my apps, hope disabling a few wakelocks will increase idle time further (faq about wakelocks in this, there's a guide linked in that post)
Unlimited photos storage, toggle to show device as pixel by default
Change ambient display notification style to that of AOD, it's really clean if you don't want notifications filling the lockscreen
Turn off volte icons
Refresh rate toggle in quick settings
xx_yolonoob_xx said:
Same bugs as above, including:
Stock camera app broken
Personal pet peeve, derpfest recovery doesn't allow switching slots
Can't get SD card to work. I setup the SD card in SPES as portable storage, format, move it to another Android (RN3), copy a file from pc to RN3 through file transfer mode, shows up in files app, SD card back to SPES and asks for a format to use the SD card. (It sucks that there's no file transfer nor a way to send files from PC to SPES using an SD card. Don't have a type c OTG lying around)
Plus points:
Great idle battery management so far, attached a pic below. Haven't seen deep sleep after setting up all of my apps, hope disabling a few wakelocks will increase idle time further (faq about wakelocks in this, there's a guide linked in that post)
Unlimited photos storage, toggle to show device as pixel by default
Change ambient display notification style to that of AOD, it's really clean if you don't want notifications filling the lockscreen
Turn off volte icons
Refresh rate toggle in quick settings
Click to expand...
Click to collapse
Can you attach Logs when you try to get your SD card to work? it works fine for me as a portable storage, i can as well transfer files from pc to the sdcard via cable while phone is plugged.
is fast charge work ?
Guan Yu said:
is fast charge work ?
Click to expand...
Click to collapse
Yep works.
NamCap said:
install ramdisk option
Click to expand...
Click to collapse
what is the difference between flash recovery and flash ramdisk option
Guan Yu said:
what is the difference between flash recovery and flash ramdisk option
Click to expand...
Click to collapse
The first option flashes the current recovery you are using to ramdisk, while the second option allows you to pick the recovery img you want to flash to ramdisk, it can be twrp, orangefox, or any other recovery img.
NamCap said:
The first option flashes the current recovery you are using to ramdisk, while the second option allows you to pick the recovery img you want to flash to ramdisk, it can be twrp, orangefox, or any other recovery img.
Click to expand...
Click to collapse
thanks
Can anyone tell if the firmware will go to spesn (with NFC) model?
habloid said:
Can anyone tell if the firmware will go to spesn (with NFC) model?
Click to expand...
Click to collapse
No problems with NFC, used a bunch today alone
Can anyone send me the official discussion telegram group for redmi note 11 spes|spesn?
Momin_brur said:
Can anyone send me the official discussion telegram group for redmi note 11 spes|spesn?
Click to expand...
Click to collapse
It's In the first post.
If you set the setting "wake the lock screen with notifications", then when a notification arrives and the screen lights up, the lock screen wallpaper is not displayed.
Rafiul Bari Chowdhury said:
Thank you so much for this Official Build. I'm using it as a daily driver.
Will May build come out?
Click to expand...
Click to collapse
Could you possibly give some screenshots of battery usage graphs, and further your overall experience using the rom
rom spesn and spes are the same, right?
Bruh i cannot unlock, it says to wait for 168hours

Categories

Resources