yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL Guides, News, & Discussion] knopie:
After flashing the July Ota and kernel my pixel was not certified, clearing Play store and Play services it is ok.

Face-unlock was also not working, after installing the full image and no extra kernel it was working(removing the -w).

This morning Face-unlock is working, but my Pixel 4 xl in Play Store is not certified, after clearing the Play store and service it is certified.

Someone else also this issue?

Jos
[Google Pixel 4 XL Guides, News, & Discussion] Trusstopher:
I've got some bad news for you.... looks like you've been hit with a hardware problem that just happened to coincide with doing this update. Take a look at this thread for some details:

https://support.google.com/pixelphone/thread/25796722?hl=en&dark=1

I'm just a few days into my second Pixel 4 XL (refurbed unfortunately) because of this issue. There is a "squeeze" trick to get the battery to operate normally, but I've yet to see it do anything but buy a little extra time.
[Google Pixel 4 XL Guides, News, & Discussion] Skimpy007:
Might be temporary or just luck.

Upgraded to 11 beta 2 was still doing it. So smacked it off my dash while driving ( pissed of course ), restarted and.... So far so good...? Lol
[Google Pixel 4 XL Guides, News, & Discussion] crypt0kiddie:
Is there a guide for doing this on MAC OS?
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Update:

SDK Platform-Tools: r30.0.4
[Google Pixel 4 XL Guides, News, & Discussion] Frischifrisch:
Thank you for this understandable step by step guide!

Your instructions are golden.

It was the first time that I managed to update my Pixel 4 with the Android 11 beta without having to set everything up afterwards ... You saved me a weekend of work.

Once again many thanks :good:
[Google Pixel 4 XL Guides, News, & Discussion] elkay:
August images out. Any chance of a premodded boot image?
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
just started the thread. editing the guide part right now ;)

https://xdaforums.com/pixel-4-xl/how-to/update-root-guide-aug-2020-qq3a-200805-t4142635

I haven't updated to that yet, but thanks for the heads up. I was able to update with 30.0.1 with no problems, but I'll do it now. Thanks.

I don't own a single Mac, but I'm pretty sure it's the same command line commands, except you would run them in terminal. Just make sure you have the sdk command line tools properly set up. You can download them directly from Google: https://developer.android.com/studio/releases/platform-tools

There's a version specifically for Mac OS.
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
:good:
[Mogul, XV6800 ROM Development] fb.knight:
hey guys im sorry i know there is a page for this in the wiki but i read it and there is no mention of my spl (2.07.0000)

my phone is the sprint version of the titan the mogule

so i got stuck when i tried flashing from dcd's latest rom 3.2.3 to the new sprint 6.1 as i understand it i was supoosed to relock the device so i did using the titan_relocker file. every thing seemed good so i tried to install the new rom 3.56.651.0_RS_TITAN_3.42.02_SPCS2.04_PPST_0718_Ship and it acts a little weird the load bar shows up on the computer and then about a half a minute later on the screen of the phone it loaded up to about 8 percent or so and then gave an error and some recovery steps that didnt do any thing.

so now im stuck in the flash scren and i have tried flashing a bunch of roms

an old stock sprint rom

the spritn 6.1 i mentioned earlier

and then dcd's 3.2.3 (this one dose not do the strange thing where the load bar shows up on the computer first then the phone but it still does not work)

and nothing works. i cant find any mention of my spl 2.07 and i dont know how it got on my device. as i understand it your phone has to boot up to be able to put a new spl on there so im at a loss if any one could help i would be very greatful.

im new to the 8900 so i dono who the gurus are around here i was a tilt and hermes guy so i dont even know who to ask.
[Mogul, XV6800 ROM Development] fb.knight:
dang i have a theory i think i may have only goten to the step where it flashes like a temp spl on to the device on the relock?... that sould right to any one?/ slash know how to fix it

edit: cant re-run the relock app it crahses and goes to the recovery steps before hitting 1 percent
[Fire TV General] spyderdsn:
Hi Guys,

So, I spend a few hours reading many posts regarding recovery of the Fire Stick 4K.

I'm in the infinite boot stage and trying to reset to the factory settings after Google Services fu*** up everything.

What I tried:

- adb connection from MacBook

- keyboard recovery

ADB Method Issues

When I connect via adb I get Device Unauthorized and don't really know what to do next. I tried to run fastboot but it stuck on Waiting for any device...

Screenshots:

Keyboard Method Issues

I tried the combination of Alt+I+PrintScr many times. None of the sources specifies if I should hold the buttons or keep pressing them on/off during the boot (eg 15x) or at which point I should start or finish pressing. So success here either.

I also tried to use remote but every source shows different buttons to press. Power + Volume Up, Middle Button + Arrow RIght etc.

What should I try next, I'm on OSX?
[Fire TV General] Sus_i:
Here is the unbrick thread.
[Fire TV General] spyderdsn:
Ok, so I need Windows PC to start with...any other options?
[Fire TV General] brick00444:
You can use the iso listed in that thread to do the unbricking and you will be left with a firestick that boots to twrp . Then you can follow this thread: https://xdaforums.com/fire-tv/orig-development/newbie-guide-how-to-unlock-bootloader-t4015273 . Good luck
[Fire TV General] spyderdsn:
From what I see this is all custom firmware. I would like to restore to factory box standard. There is so many steps to unlock the device. What should I do to restore original firmware after twrp?
[Fire TV General] brick00444:
I'm almost sure there is a factory rom posted here somewhere. Just use that instead of the rbox rom.
[Fire TV General] SweenWolf:
A good reminder to everyone, don't try anything with your device with debugging disabled.
[Fire TV General] Sus_i:
It isn't a cfw, but the stock recovery gets replaced during the unlock. Therefore the stock update app in fireOS won't work as expected, you need to use TWRP recovery and do all updates manually.
[Fire TV General] spyderdsn:
So the steps in other post are not exactly clear as I'm using the iso

https://github.com/amonet-kamakiri/fireiso/releases

.

I run the ISO from USB stick on my MacBook and what do I do next I have two opinions Default & Load to Memory...do I have to have firesick connected at this point...with the foil in it? Is there any step by step for the ISO setup? Can I use MacBook to rin the ISO at all?

Thanks
[Fire TV General] brick00444:
I don't own a macbook but I would think you can because you have to boot to the usb stick and I just use the default option. Wait until you see the desktop. Then go to the internet and look up the unlock thread. You may need to have an ethernet cord plugged into your mac to access the internet (my wifi doesn't work in the iso).

1. Download kamakiri-mantis-v1.2.zip from the link in the original thread.

2. Extract the kamakiri-mantis-v1.2.zip somewhere you will remember. I extract to desktop.

3. Open the kamakiri-mantis-v1.2 folder and then open the kamakiri folder and right click inside that folder and choose open terminal.

4. enter this command in terminal " ./bootrom-step.sh " minus the quotes and click enter. It will say something to the effect of "waiting for device".

5. Short the correct point to the tin casing. It looks like you are shorting it correctly by your pic.

6. Connect the stick to your computer (while keeping it shorted).

7. The script should tell you to release the short and hit enter,. Just pull the tinfoil off the stick . Then click enter (after removing short).

It will take awhile to finish so if it looks like it stalled out give it time.

8. When it is finished enter the command : " ./fastboot-step.sh " and click enter.

9. It will now reboot into TWRP.

10. You can now install the rom. If you don't know how you can follow this guide "https://xdaforums.com/fire-tv/orig-development/newbie-guide-how-to-unlock-bootloader-t4015273" .

Hopefully this helps you. Anyone can add to it or correct it if I missed or forgot something.
[Fire TV General] spyderdsn:
Thanks guys for the help. I managed to unbrick my Firestick 4K. and after brick00444 steps I followed this steps:

adb push <your download location you decided earlier here>/mantis-6.2.6.8-rooted_r1.zip / sdcard/
adb reboot recovery

adb shell
twrp install /sdcard/mantis-6.2.6.8-rooted_r1.zip
twrp wipe cache
twrp wipe dalvik
reboot -p

Worth mentioning. Since I used Mac I downloaded https://unetbootin.github.io/ to do the fat32 bootable stick. The stick runs to the menu but is not able to load Linux. I had to find Windows 10 machine and use https://rufus.ie/ to install the iso and everything worked. All other steps I followed brick00444

My Firestick did not had enough space to push the room zip above so I used Adblink http://www.jocala.com/ to remove some apps.

One more question.

I decided not to block amazon update services via adb. At the moment I’m on Fire OS 6.2.7.1. and fire stick is downloading some updates. I only wanted to unbrick the device not root. Can I apply the update on the top of mantis? Would this work. I’m happy to have stock. At the moment download kind of stuck on downloading system components 70%.

Thanks for your help.
[Fire TV General] Sus_i:
Only app updates are working, all OS updates (reboot to stock recovery required) won't work.
[Fire TV General] spyderdsn:
The sick has been updated now. The update took whole night and it has downloaded 1GB of stuff as my storage was very low at the time. Now I have the latest update and everything seems to work fine.
[Fire TV General] spyderdsn:
Ok I noticed now when I power off the device and run again I get the recovery mode and reboot after that everything is fine until I power off the stick. What should I do to prevent this?
[Fire TV General] Sus_i:
It's like I said, I guess there is a (partial or full) fireOS update pending ;)

The OTA-update app downloads the update to /cache and place also some recovery commands for the stock recovery.

This is why your stick boots into recovery.

The stick will do that again and again and again, until the update is installed (won't work without the stock recovery).

Take a look on /cache with TWRP. There should be the latest update for your stick (it's a .bin file). In case it is a full update (~600MB in size), rename that file to zip and flash/install it with TWRP. Make sure you don't flash one of the smaller 'partial' updates (If there is a smaller update bin file, delete it... then the stick will download a full bin). After the install, wipe cache, reboot and your stick should be on the latest OS version. You have to do this erverytime you see that the stick boots into recovery ;)

Another option, disable updates and keep the OS version on the stick (for now).

pm disable com.amazon.device.software.ota
pm disable com.amazon.device.software.ota.override
pm disable com.amazon.tv.forcedotaupdater.v2
pm clear com.amazon.device.software.ota

But for this option you need magisk installed...
[Fire TV General] theflashfromthecw:
Actually you don't need Magisk to disable packages. Input disable-user after putting adb shell and the package can disable without root. Only works on Fire OS 6 and above
[Fire TV General] spyderdsn:
Ok so if I understood this correctly. If I don’t bother with the updates for 1-2years. All I do is to delete the update files from the temp folder and prevent the updates by running this commands and I’m good to go.
[Fire TV General] theflashfromthecw:
Yes and its all preferred to rename otacerts.zip to otacerts.zip.bak in TWRP by mounting the system as read write and hovering over to system/etc/security and you'll see otacerts.zip. The otacerts is certifying the update that's being rolled out properly and since you renamed it to .bak, you can no longer have it applying the update. It still will update but not apply it if you do end up keeping devicesoftwareota. Only disable the override and leave the rest alone for factory reset reasons because it needs the devicesoftwareota enabled to go through the wizard
[Fire TV General] Sus_i:
Personally, as soon as system modifications come to mind, I preffer a magisk install, just to avoid verity issues. ;)

but renaming just one zip on system won't trigger dm-verity I guess!?
[Fire TV General] Skel40:
It won't. Fire TV devices don't have dm verify at all and it's safe to rename the zip however you want. Because of this, Amazon doesn't have oem unlock and a setting to enable it, there's no official way for the device to check for dm verify and because the bootloader unlock isn't modified to have its own recovery. I have an LG unlocked device that supports oem and after I unlock it, it tells me to relock the bootloader since the manufacturer allowed my device to be oem unlocked.
[Fire TV General] Sus_i:
That isn't correct.

The 4k stick has dm-verity enabled, like almost all devices running android 7.0 nougat and above.

It gets triggered if you mess with system and you try to boot without a installed magisk.zip.

In case the zip is installed, magisk takes care about that and ofc there aren't verity problems at all and you can do whatever you want on system.

The first prerooted rom from rbox for the 4k stick had such issues without a flashed magisk.zip behind the rom. Thats one of the reasons why rbox included a full magisk install into the rom.

You can read all about that in the 4k unlock thread...

That isn't correct too. All fireTVs have the option for a bootloader unlock built-in...

Only thing you need for this is the propper unlock code from the manufacturer, flashed with fastboot into boot1 region.

A tool for editing that code is also in-build, called idme.
[Fire TV General] spyderdsn:
So strangely enough even with the custom firmware and ADB debugging enabled I still get "Device Unautorized".

Tried:

- Flick ADB debugging On/Off

- Update ADB Tools to the latest

- Kill/Start ADB server

Got the message in the terminal and ADBlink?
[Fire TV General] Sus_i:
Have seen that too with adblink. Sometimes you have to connect twice...

Whats about the adb prompt on the TVscreen? Access allowed?
[Fire TV General] spyderdsn:
I don’t have it connected to the tv when connecting via adb. My OTG, USB splitter does not work well. Do I need to have hdmi connected and follow the screen?
[Fire TV General] brick00444:
Yes, you need to allow the adb on screen then the "unauthorized" will be solved.
[Fire TV General] spyderdsn:
So I need a new OTG cable which can get power from the charger and data from the computer...
[Fire TV General] brick00444:
You should be able adb wirelessly.
[Fire TV General] Sus_i:
adb over otg won't work ;)
[Fire TV General] spyderdsn:
Oh no I just purchased another cable ?, ok I’ll try wifi than.
[Fire TV General] spyderdsn:
Unable to run as SU...?
[Fire TV General] Pretoriano80:
To run it as SU you need to have Magisk installed and give root permissions to adb shell when Magisk will ask you to.
[Fire TV General] Sus_i:
You have to grant root access in the popup window on your TV screen.

It is a 10 seconds timer. In case you missed that screen, take a look in the magisk manager app and grant root access for the shell there :good:
[Fire TV General] spyderdsn:
This is the final story...

I did manage to install Magisk via Recovery and then I went to the Magisk app and installed updates to the manager and magisk itself. After this updates Firestick does not load to the white Fire TV screen anymore just stuck on the black one with the Fire TV logo. I tried to adb to it but device is dead. Tried again repeated the whole process again with the TWRP mode, aluminium foil etc. No connection with the device. :( This is the end...

What I learned:

You can run kamakiri ISO on Macbook Pro 13"

- wifi works

- build in keyboard, touchpad won't work (you can use USB keyboard, mouse)

- USB-C adapters works fine

- You can load whole Linux to RAM no issues

Most importantly this process takes loads of effort and time ;) and there are loads of little things to consider. Thanks again for your help guys...
[Fire TV General] Sus_i:
Hi there^^

If I remember correct, there is a warning in the unlock thread OP, about not to update magisk from the manager ;)

But ofc that isn't the end, a magisk update can't damage your stick.

You should be able to re-do the exploit in order to unbrick, then flash magisk zip with TWRP and your issue is fixed.

Just make sure that you don't miss any requirements from unlockOP, use the amazon cable and apply a propper short.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
​

Changelog

SOLVED ANY PROBLEMS WITH NETFLIX

SOLVED USSD CODES

SOLVED PROBLEMS WITH BANKING APP

SOLVED MAGISK DETECTION WITH THE DESIRED APP

REMOVED GPU BOOSTER

BIONIC MOD FOR THE CPU

SOLVED SOME INCOMPATIBILITIES WITH GEAR

SIGNATURE VERIFICATION WAS DISABLED AGAIN

24-BIT SOUND QUALITY

ONE UI 2 MESSAGING

KEYBOARD ONE UI 2

ONE UI 2 GALLERY

SOLVED WIFI CALLS

SOLVED GESTURE USE WITH ONE HAND

VIDEO FIX OPTIMIZER

SOLVED EXAGGERATED HEATING WHEN SHARING INTERNET

THE HEATING HAS BEEN CONSIDERABLY IMPROVED

SMALLER ROUNDED

SMAR VIEW FIX

REMOVED DOLBY 2.5 NOW THE SOUND IS HAS 24BIT NO NEED

THE DIGITAL DOLBY WAS LEFT WITH IMPROVEMENTS IN THE BIT RATE

FIX BIXBY VISION

ADDED SAMSUNG PASS

ADDED SAMSUNG MEMBERS

FIX SECURE FOLDER LOCK

FIX SECURITY COPY

STOCK START LEFT

KERNEL CRONOS V5

KERNEL HELIOS 2.5

KERNEL MORO 8.4

KERNEL JACK ONEILL V1

THIS UPDATE OFFERS YOU A BALANCED ANDROID 9 STOCK EXPERIENCE, INSTEAD THE ALPHA X IS FOCUSED FOR GAMES

BUT WITH SOME SLIGHT ERRORS TO NOT REMOVE MORE RESOURCES, THIS UPDATE ALSO IMPROVES THE HEATING OF THE MOBILE

THEREFORE IT IS IDEAL FOR DAILY USE AND NOT SO HEAVY TASKS, IT CAN TEST IN GAMES BUT AS I SAID IT IS MORE FOCUSED

WHAT ALL FUNCTIONS.

BEFORE FLASHING YOU MUST DO TOTAL CLEANING FROM THE TWRP AND DO NOT FLASH ON THE ALPHA X, IF YOU DO SO IT WILL NOT START

FOR THOSE WHO SELECT CRONOS 2.5, MORO 8.4 CAN CHANGE THE FORMAT TO F2FS BOTH DATA AND CACHE IS OPTIONAL,

INSTEAD THOSE WHO CHOOSE HELIOS 2.5 AND JACKONEILL SHOULD NOT CHANGE FORMAT OTHERWISE IT WILL NOT START

Credit

@morogoku

@ananjaser1211

@MKUltraBlack

@yash92duster [MOD]

CHANNEL TELEGRAM: https://t.me/ALPHAX1991

Group telegram: https://t.me/joinchat/Lo6j_EYgW9zyIfwtkr4O7w

PAYPAL: https://www.paypal.me/ChadUx1991?locale.x=es_XC

Link Mega: https://mega.nz/file/BnpRkDgJ#w0ggglcgiddGcHTrfbbYK_J_xG9TMi6oUm6-WFhIo-Y

Link Drive: https://drive.google.com/file/d/12W8WejgZbMSmuYoddZXB-j0tOchy8y99/view?usp=drivesdk
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
Ready
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] acadiantoast:
Installed a day ago, battery life is awesome, nice clean stock experience. Good job
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
exellent
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] acadiantoast:
Been running this the last 4 days, best pie stock rom imo. Battery life is well optimized as well. Waiting to find errors or faults and so far I've been unsuccessful.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] MostaphaHida:
whats the difference between gpu booster and gpu booster dual in aroma?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
the difference is that the dual is for the s7 dual sim only the gpu booster do the same
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
Very good friend
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] msamymiyagi1:
turkish language?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
install a compatible csc if you don't have it
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] appetitefordestruction:
Very good!!

Unfortunately Wi-Fi calls does not work for me. I tried two different networks in Germany, telekom and telefonica. Any chance to activate wificalls?

Btw. Volte works perfect.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] msamymiyagi1:
how to do
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] biloool:
Nice rom, great job ?

I just wanna ask, how can i change the battery color ?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
I'll see what I can do to solve that problem
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
you can't it's part of the system
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] amazinglife612:
I'm just waiting for alpha x NFE...
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
today it will come out
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Fire1511:
Is android Q?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
no pie
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
released the latest alpha version
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] themrperfecto:
What are the changes in the latest version?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] faizansabri:
Magisk Camera 4k Mod is not working
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] llmiller:
Does the 24 bit audio work for bluetooth also ?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
read the first post
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
do not try it and tell me
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] z3r0tl:
How to make the heart rate sensor work
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Jean456:
important doubt?

best rom i've ever used in almost every way, the only bad thing i found was the audio that looks pretty bad on the bluetooth headset, would there be any way to get back to the default sound without this 24 bit?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] juh07:
Fingerprint isn't working

i installed the rom, it's working fine but i'm facing a problem with the fingerprint. i can't add or setup, when it just pop a message to press the button and it closes then. There is a way to fix it?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] blazko93:
I'm giving a try to this rom but it look that the Samsung Wearable app is not pairing with my Galaxy Watch, even after trying the build.prop tweak.

Any fix for this?

Thanks in advance
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] ZINZIRIO:
This ROM also has the problem when you make a call on Whattaps and the other person listens to himself? I tried 3 roms and it happens to me with them but in stock it disappears.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
Alpha Thunder X is coming soon fixes several super alpha bugs
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
[QUOTE = "ZINZIRIO, publicación: 83884055, miembro: 9569333"]

Esta ROM también tiene el problema cuando haces una llamada en Whattaps y la otra persona se escucha a sí misma. Probé 3 roms y me pasa con ellas pero en stock desaparece.

[/CITAR]

fixed for next update

Translation: fixed for next update
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
[QUOTE = "blazko93, publicación: 83500277, miembro: 11060887"]

Estoy probando esta rom, pero parece que la aplicación Samsung Wearable no se empareja con mi Galaxy Watch, incluso después de probar el ajuste build.prop.

¿Alguna solución para esto?

Gracias por adelantado

[/CITAR]

fixed for next update
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
[QUOTE = "biloool, publicación: 83134379, miembro: 6837561"]

Buena rom, gran trabajo?

Solo quiero preguntar, ¿cómo puedo cambiar el color de la batería?

[/CITAR]

fixed for next update
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] luis taylor:
[QUOTE = "apetito por la destrucción, publicación: 83068963, miembro: 10491381"]

¡¡Muy bien!!

Lamentablemente, las llamadas Wi-Fi no me funcionan. Probé dos redes diferentes en Alemania, telekom y telefonica. ¿Alguna posibilidad de activar wificalls?

Por cierto. Volte funciona perfecto.

[/CITAR]

fixed for next update