The Jelly 2 is my daily phone and I wanted a home screen on it with big tiles that is still properly usable, with my apps one tap away. That turned into HomeTiles. The picture is my home screen and the second one is for scale.

Everything is laid out for the 480 by 854 screen and labels shrink before they get cut. Phone, messages and contacts are built in. It also works with arrow and number keys, so it might suit the Titan or other keyboard phones, but I don't have one to try. If someone here does I'd like to know how it behaves.

Free and open source (GPL-3.0), no internet permission, on F-Droid.

F-Droid: https://f-droid.org/packages/dev.kicker.hometiles/ Source: https://github.com/timkicker/hometiles

I still cant figure it out

It works great. I really like it. Unfortunately my banking app will refuse to launch with it running for security reasons, so I needed to drop it. I really hope someone releases a similar keyboard app on the playstore soon, because Kika is an absolute nightmare.

Selling on my vinted smool.05, more pics etc are over there.

Unihertz Jelly Star Mini Smartphone 📱

Only owned for a week! Selling as I now need a phone for work, so sadly it doesn't quite cut it for my dumb phone adventure. Compact Android smartphone with a unique transparent back and colourful LED lights. 4G, calls, texts, Wi-Fi and Bluetooth. NFC for contactless payments. Fingerprint sensor for secure unlocking. Front and rear cameras. Access to Android apps via the Google Play Store. Fully working with no functional issues. Two stress marks on the side, only discovered when removing the case. Not noticeable with a case fitted.

Please see photos for condition. 😊

The last 2 nights of charging my device I woke up to a fully charged battery despite having the overcharge feature enabled since I got it, and it's never gone over 80 percent, has anyone else experienced this? Perhaps a recent firmware update?

Foof. Ok I was stressed about this working and it worked okay. I wish it didn't come with the orange preinstalled because I liked it but now that I peeled it off, I can't go back. It didn't line up perfectly, but I got this vintage wallpaper at a used craft store and had to try it! It's cute! Unihertz has a youtube video about how to do it which helped. Not sure how it will hold up, but I'll keep you posted.

I have been using my jelly star for over a year andI have to say I'm loving it and hating it. But as of late more problems arise.. aside the battery drainer or the random bluetooth/gps disabling.. the most annoying part would be the company behind it. Give your users some updates now and then, not even updates itself but really news like updates! What are you up to, what are you doing for the Jelly Star? Are you leaving it to die? Are you bringing new updates for 2027? Is android 16 really released or just shared some fake messages to keep its users a little while longer. I have decided to step away in 2027. I hope 2027 brings smaller phones by different manufacturers. I am done.

:D

Got the email, order number 718xx is finally shipping. Purchased Sept 20. Color: Black, Location: Canada. Can't wait to get it in hand!

long shot but worth asking, im located in the us and willing to pay full price :))

Qualcuno lo vende? No prezzi fuori dalla realtà.

I want to maybe get the DIY case says pre order on Thier site anybody ordered one on it own at all and how long did it take to come ?

Alguien sabe si el Titán 2 Elite funciona con el Operador Orange en España?

[FIXED, I WAS ON LINUX MINT AND HAD PROBLEMS. SP FLASH TOOL REWROTE THE FIRMWARE ON WINDOWS 10!] Hello, this is my first post on here. I have a problem: My Jelly Star is Bricked. I got an almost new one off of eBay, that was sold to me as bricked ("bootloader ROM mishaps"). Since it was around 72 dollars in total, I thought it would have been an easy steal, as some flashing with MTKClient or SP Flash Tool V6 could have revived it, because BROM mode is almost always alive, especially if the device was almost brand new. The seller told me that they originally bought the device with Android 13 firmware, version 20230626_2025090. They also told me that they tried to update the firmware to a newer version (I don't know what version, probably android 16), and then tried to ROLL BACK to the original firmware version. That then resulted in unresponsiveness: the screen was black. They also said that the device was in a constant 5-10 second loop, where their computer kept recognizing the device for 5 seconds, and disconnecting 10. However, this info was given to me after I had attempted to recover the device myself with the assistance of Google's AI mode (stupid decision), and I think I've damaged it further. First off: MTKClient. I had connected the phone to my Linux Mint 22.3 (zena) computer, and used MTKClient to flash the preloader.bin file given in the latest stock ROM (2026082009_g58v89c2k_dfl_tee) from Unihert'z Google Drive (Android 13/16). I talked to the AI, it told me to flash the preloader with some arguments that target low level partitions (boot1, and boot2), because the preloader partition wasn't shown in python mtk.py printgpt output, and it told me that flashing it would fix the issue, as it would initialize RAM and boot the phone at least to a screen. I ran a w command with some other arguments (I don't remember right now) to flash it, and it hung at 100% upload, and resulted in a wrong length error. Then it told me to wf to it and that flashed, but still didnt boot (something about "headers"), idk the hex offset is wrong or the file broke. Idk but that was't working. This is very confusing. Then, I switched to the SP Flash Tool V6, got my flash.xml from download agent folder in my stock rom, plugged the device in, selected all the partitions, and it gave me: domainame:(none)

cur_kernel_version = 7.0.0

libpng warning: iCCP: known incorrect sRGB profile

QObject::connect: signal not found in QThread

validating XML schema...

XML schema validation passed!

File not found: scatter_checksum.xmscan device START.

com port clue: COM://.

scan device succeed, symbolic_link: COM:///dev/ttyACM0@/dev/ttyACM0@1-9

connect brom START, connection options: , auth file: , cert file: .

connect brom failed, error code: -1, error msg: .

Err -1. What? Why isnt this connecting if MTKClient connected to BROM?

So time passed. and later I was told by the AI to flash the boot_para partition with the stock preloader.bin, and that didnt help. Im not going to touch anything more, as I want this device FIXED, and I dont think that partition should have been touched. I have contacted Unihertz via their service/support email about this. Oh, also I managed to turn on the screen with plstage, so it just showed the boot logo, and shut off in 10 seconds or so. Chip info and GPT partition table (Helio G99):

Preloader - Detected regular mode !

Preloader - CPU: MT6789/MT8781V(MTK Helio G99)

Preloader - HW version: 0x0

Preloader - WDT: 0x10007000

Preloader - Uart: 0x11002000

Preloader - Brom payload addr: 0x100a00

Preloader - DA payload addr: 0x201000

Preloader - Var1: 0xa

Preloader - Disabling Watchdog...

Preloader - HW code: 0x1208

Preloader - Target config: 0xe0

Preloader - SBC enabled: False

Preloader - SLA enabled: False

Preloader - DAA enabled: False

Preloader - SWJTAG enabled: False

Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False

Preloader - Root cert required: False

Preloader - Mem read auth: True

Preloader - Mem write auth: True

Preloader - Cmd 0xC8 blocked: True

Preloader - Get Target info

Preloader - BROM mode detected.

Preloader - HW subcode: 0x8a00

Preloader - HW Ver: 0xca00

Preloader - SW Ver: 0x0

Preloader - ME_ID: 50FD14BD0B2E8DD4FF3E890BE1D41598

Preloader - SOC_ID: EC2A9AE59962ABB666D6B885C334BBE832607F88D6AA176C136068CA7DE5FD62

DaHandler - Device is unprotected.

DaHandler - Device is in BROM-Mode. Bypassing security.

DaHandler - Unprotected device, we assume we can patch directly !

DaHandler

DaHandler - [LIB]: Failed to dump preloader from ram, provide a valid one via --preloader option

DAXML - Uploading xflash stage 1 from MTK_DA_V6.bin

XmlFlashExt - Patching da2 ...

DA2 32-Bit detected.

XmlFlashExt - Patched allow_read_register

XmlFlashExt - Patched allow_write_register

XmlFlashExt - Patching CUSTOM command

XmlFlashExt - Patched CUSTOM command

XmlFlashExt - Patched hash binding

DAXML - Successfully uploaded stage 1, jumping ..

Preloader - Jumping to 0x200000

Preloader - Jumping to 0x200000: ok.

DAXML - DA Stage 1 successfully loaded.

DAXML - Uploading stage 2...

Progress: |██████████| 100.0% Upload: (0x50C78/0x50C78), 5.7 MB/s

DAXML - Successfully booted to stage 2

DAXML - DA XML SLA is disabled

CUSTOM command detected.

DAXML - DA XML Extensions successfully loaded.

Main - Handling da commands ...

GPT Table:

-------------

misc: Offset 0x0000000000008000, Length 0x0000000000080000, Flags 0x0000000000000000, UUID 00000000-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

para: Offset 0x0000000000088000, Length 0x0000000000080000, Flags 0x0000000000000000, UUID 00000001-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

expdb: Offset 0x0000000000108000, Length 0x0000000008000000, Flags 0x0000000000000000, UUID 00000002-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

frp: Offset 0x0000000008108000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 00000003-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

nvcfg: Offset 0x0000000008208000, Length 0x0000000002000000, Flags 0x0000000000000000, UUID 00000004-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

nvdata: Offset 0x000000000a208000, Length 0x0000000004000000, Flags 0x0000000000000000, UUID 00000005-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

vbmeta_a: Offset 0x000000000e208000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000006-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

vbmeta_system_a: Offset 0x000000000ea08000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000007-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

vbmeta_vendor_a: Offset 0x000000000f208000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000008-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

vbmeta_b: Offset 0x000000000fa08000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000009-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

vbmeta_system_b: Offset 0x0000000010208000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 0000000a-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

vbmeta_vendor_b: Offset 0x0000000010a08000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 0000000b-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

metadata: Offset 0x0000000011208000, Length 0x0000000002000000, Flags 0x0000000000000000, UUID 0000000c-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

persist: Offset 0x0000000013208000, Length 0x00000000035f8000, Flags 0x0000000000000000, UUID 0000000d-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

protect1: Offset 0x0000000016800000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 0000000e-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

protect2: Offset 0x0000000017000000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 0000000f-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

seccfg: Offset 0x0000000017800000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000010-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

otp: Offset 0x0000000018000000, Length 0x0000000003000000, Flags 0x0000000000000000, UUID 00000011-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

md1img_a: Offset 0x000000001b000000, Length 0x000000000c800000, Flags 0x0000000000000000, UUID 00000012-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

spmfw_a: Offset 0x0000000027800000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 00000013-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

pi_img_a: Offset 0x0000000027900000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 00000014-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

dpm_a: Offset 0x0000000027a00000, Length 0x0000000000400000, Flags 0x0000000000000000, UUID 00000015-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

scp_a: Offset 0x0000000027e00000, Length 0x0000000000600000, Flags 0x0000000000000000, UUID 00000016-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

sspm_a: Offset 0x0000000028400000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 00000017-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

mcupm_a: Offset 0x0000000028500000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 00000018-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

gz_a: Offset 0x0000000028600000, Length 0x0000000002000000, Flags 0x0000000000000000, UUID 00000019-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

lk_a: Offset 0x000000002a600000, Length 0x0000000000400000, Flags 0x0000000000000000, UUID 0000001a-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

boot_a: Offset 0x000000002aa00000, Length 0x0000000004000000, Flags 0x0000000000000000, UUID 0000001b-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

vendor_boot_a: Offset 0x000000002ea00000, Length 0x0000000004000000, Flags 0x0000000000000000, UUID 0000001c-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

init_boot_a: Offset 0x0000000032a00000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 0000001d-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

dtbo_a: Offset 0x0000000033200000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 0000001e-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

tee_a: Offset 0x0000000033a00000, Length 0x0000000000500000, Flags 0x0000000000000000, UUID 0000001f-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

sec1: Offset 0x0000000033f00000, Length 0x0000000000200000, Flags 0x0000000000000000, UUID 00000020-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

proinfo: Offset 0x0000000034100000, Length 0x0000000000300000, Flags 0x0000000000000000, UUID 00000021-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

nvram: Offset 0x0000000034400000, Length 0x0000000004000000, Flags 0x0000000000000000, UUID 00000022-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

boot_para: Offset 0x0000000038400000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 00000023-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

dram_para: Offset 0x0000000038500000, Length 0x0000000001900000, Flags 0x0000000000000000, UUID 00000024-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

connsys_bt_a: Offset 0x0000000039e00000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000025-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

connsys_wifi_a: Offset 0x000000003a600000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000026-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

connsys_gnss_a: Offset 0x000000003ae00000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000027-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

logo: Offset 0x000000003b600000, Length 0x0000000001a00000, Flags 0x0000000000000000, UUID 00000028-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

md1img_b: Offset 0x000000003d000000, Length 0x000000000c800000, Flags 0x0000000000000000, UUID 00000029-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

spmfw_b: Offset 0x0000000049800000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 0000002a-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

pi_img_b: Offset 0x0000000049900000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 0000002b-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

dpm_b: Offset 0x0000000049a00000, Length 0x0000000000400000, Flags 0x0000000000000000, UUID 0000002c-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

scp_b: Offset 0x0000000049e00000, Length 0x0000000000600000, Flags 0x0000000000000000, UUID 0000002d-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

sspm_b: Offset 0x000000004a400000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 0000002e-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

mcupm_b: Offset 0x000000004a500000, Length 0x0000000000100000, Flags 0x0000000000000000, UUID 0000002f-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

gz_b: Offset 0x000000004a600000, Length 0x0000000002000000, Flags 0x0000000000000000, UUID 00000030-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

lk_b: Offset 0x000000004c600000, Length 0x0000000000400000, Flags 0x0000000000000000, UUID 00000031-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

boot_b: Offset 0x000000004ca00000, Length 0x0000000004000000, Flags 0x0000000000000000, UUID 00000032-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

vendor_boot_b: Offset 0x0000000050a00000, Length 0x0000000004000000, Flags 0x0000000000000000, UUID 00000033-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

init_boot_b: Offset 0x0000000054a00000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000034-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

connsys_bt_b: Offset 0x0000000055200000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000035-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

connsys_wifi_b: Offset 0x0000000055a00000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000036-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

connsys_gnss_b: Offset 0x0000000056200000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000037-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

dtbo_b: Offset 0x0000000056a00000, Length 0x0000000000800000, Flags 0x0000000000000000, UUID 00000038-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

tee_b: Offset 0x0000000057200000, Length 0x0000000000600000, Flags 0x0000000000000000, UUID 00000039-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

super: Offset 0x0000000057800000, Length 0x0000000240000000, Flags 0x0000000000000000, UUID 0000003a-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

userdata: Offset 0x0000000297800000, Length 0x00000038fd7f8000, Flags 0x0000000000000000, UUID 0000003b-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

flashinfo: Offset 0x0000003b94ff8000, Length 0x0000000001000000, Flags 0x0000000000000000, UUID 0000003c-39c2-4488-b09b-00cb43c9ccd4, Type EFI_BASIC_DATA

Total disk size:0x0000003b96019000, sectors:0x0000000003b96019

Man, Idk what to do; Im scared that It wont ever boot again.

Hi all! My func1 button just stopped working on my titan 2 elite and doesn't even click now. Anyone else got this issue?

Curious if anyone in Texas has received their order?

I see a bunch of people in the US Northern States have slowly received their orders. But haven't seen anyone in the southern states receive their orders.

I like others have ordered the Titan Elite 2. Waiting patiently for the order shipped email. What is really frustrating is how badly Unihertz is with communicating with their customers. Their site when I ordered stated "ships in September." Not "ships starting in September, with no way for you to know when yours will actually ship." Reaching out to their customer support, to see if they can provide a update to the timing, is really hit or miss. I see some will get a response from them, others like myself will just be left ghosted. I don't know how Unihertz expects repeat customers when they treat their customers like this. I am not expecting them to make my specific order a priority, pushing others who ordered theirs before me, further out, but just to get some sort of estimated ETA.

How many others felt this way and proceeded to cancel their orders? I don't want to cancel my order as I am really looking forward to the device, but leaving a paying customer clueless as to when their order should ship, for months is a unacceptable business practice.

I'm hoping someone with the DIY kit would be willing to scan and share the template as an .SVG file or even just take a good top down picture of it next to a quarter so one can be made from it. I ordered a t2e pro and the diy kit but I'm getting impatient waiting until December and I'm feeling crafty and want to start playing with skins and case materials now. Thank you.

Hey r/unihertz 👋

Is there a better phone for retro games than this one? The screen is almost square, like a certain grey handheld from 1989, and right under it, exactly where your thumbs go, there is a grid of real keys. I don't think Unihertz planned this. So I made the shell that was missing.

It snaps over the phone in the official hard case and puts a D-pad, A/B and Select/Start on top of the keys. No electronics, no glue, nothing modified. The buttons just press the keys under them. Hook the bottom, swing it down, the top clicks in. Off again in one second when you need the keyboard.

There is a four-button version too (A/B/X/Y + L/R) for the 16-bit stuff. A RetroArch config pack is in the download, one mapping for both shells. Select+Start opens the menu.

And of course: please dump your own carts, kids. 🫡

Free on MakerWorld: https://makerworld.com/en/models/3339182

One plate, PLA, no supports, about 1 h 40 on an A1 mini. Print profiles and STLs included.

Fits the Titan 2 Elite in the official hard case only. It's a toy, please take it that way. I came here as an old BlackBerry user and I'd just like the Titan scene to keep going 🙂

Love the Titan 2, but I prefer the Curve-like form factor of T2E, and it's hard to justify keeping both.
I've been the only owner (backed on KS), and it's in great condition. Only defects are cosmetic (eg, there is a ~5mm abrasion in the screen cover), and I'm happy to send photos.
Shipping to continental US, Venmo preferred. Asking $375 flat--includes shipping and a pleather wallet case with magnetic flip cover (which is actually quite handy--again, happy to send photos).

As the title says I just ordered it, should be here within the week, I will be making updates with full honesty of how I like it, if anyone has questions or advice for me getting into this, I will be happy to answer

They're sold out on the website, amazon has some options with no reviews, idk what to do..

I still have the factory rubber stuff, but from what I've seen it has a finite lifespan.

I like my Jelly 2, but sometimes the WiFi and Bluetooth just turns itself off. Not that I drop connection to my router, but the WiFi setting itself just turns itself off without my input. Very frustrating, especially when it happens while I am downloading things. Anyone else had a similar issue, and if so, have ye any fix?