After upgrade, BT works. But after restart, do not! (T8 Allwinner) - Android Head-Units

Hi,
I upgraded another firmware in HU just to change the main colors of the apps radio, eq, bt e video.
The end in my OEM firmware is KEB8. Other ones with this still is blue theme.
I look for one red.
After research, I figured out that firmwares with TW2 are the red I want. I got some ones, upgrade ok, everything works great. But after first restart, bluetooth stops pairing. Every time I restart, it lost the name and pin code.
At first time after upgrade, it worked fine. I had made calls, listen musics.. everything ok...
Someone have any idea in what I can do?
I use Iphone

go to extrasettings, config and see what BC you have enabled. I had same problem after i checkout one of BC's

vulcaneanul said:
go to extrasettings, config and see what BC you have enabled. I had same problem after i checkout one of BC's
Click to expand...
Click to collapse
I've tried it lot of times. And I will continue trying.
How the problem is not firmware, I came back to the firmware I prefer. After do it and boot, BT is fine for the first time. But after reboot the system, stops working.
Can it be MCU update? I did not.
{
"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"
}

I've tried doing lot of things. And had came back the original firmware and BT comes back working, even after restart.
After it, I tried to update another firmware without erase data, and the things continue the same, BT just works after update. After reboot, no more.

I will post my config later. I had same problem bună but i fixed by check and uncheck some modules from this setting

Related

Any WIFI hangs in Saved, but it wont connect.

It's been 48 crazy hours since I'm having this annoying issue, and after Google even my soul and read the same amount of words as 180 bibles... I give up and write down what's happening to my Note 4.
I have an international Note 4 (N910F), with stock Android 5.0.1 (N910FXXU1ANK4), which was working 100% normal until 2 days ago where - just for curiosity - I installed Cyanogenmod 12.1 to see how it runs on my phone. After 30 or 40 minutes I returned to stock using the same stock Android 5.0.1 which I have previously downloaded from Sammobile.
Before install I did a clean full wipe, root again, and put it just like I did 48 hours ago. The only difference is now wifi scans for connections, it sees wifi connections, but it wont connect. I've flashed the whole firmware countless times, did a full wipe with TWRP and stock recoveries like 15 times, format partitions countless times, forgot connections, put details from scratch again and it just put them as Saved, but it wont connect. I tried to make a totally open connection and nothing... so I'm really out of ideas here.
{
"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"
}
Any suggestions? Any miraculous app? Please guys help me.
Thanks in advance.
King regards.
PD: FYI I'm the only one in my wifi channel.

Black screen of death since 5.1.1

Ok guys it started since I migrate to 5.1.1 ROM, flashed clean DN 0.3 note 5 port, and the phone would just go black at least once per day, nothing seems to work even a hard restart (volume up + power button for 20 sec) only a battery pull would restart the phone. So I figured it must be the ROM ( noone in DN 0.3 thread seems to have this problem) . So I flashed the original 5.1 firmware for my country, rooted it and used it for a day to find out it does the same! I'm really not sure what seems to be the culprit. I couldn't find a conclusive pattern on the bsod however last time I noticed it happened right before I was disconnected from public wifi, perhaps it is the modem? Maybe it's root and bootloader conflict with 5.1 firmwares? (the phone boots up, so it cannot be bootloader? Or I don't understand something about what bootloader does?) Any one has encountered the same problem? Any clues on how to fix it?
Just happened again while wifi connection was weak and I think it happens right before it got disconnected or switched to other connection mode or different wifi
Read around the forums that people are having bsod in combination with Tasker and secure settings to switch off secure keyguard, I never use this option, just use Tasker to automate sync processes, Uninstalled it nevertheless. Will see if it helps
Happened again... Noticed that the battery percentage drops quote significantly after the battery pool, here is the screenshot
{
"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"
}

Nexus 4 only working on Jellybean (4.2.2)

This is very strange...
Okay, it's the second Nexus 4 that I own (my other one works well, even has Nougat installed on it)
For some reason, it only works on Jellybean version 4.2.2, I've tried to update it to all of the factory updates and yet it gets stuck on a endless boot loop at the start. Very weird.
I've tried to wipe the cache: it does nothing.
I've also tried to Side-load a custom ROM: it still does not work.
I've tried to update it via 4.2.2: it still does not work
I've made a 3 hours research on the internet and yet I found nothing. It's very weird that it does this, and I'm probably the only one who has this problem.
The reason why I am working on making this phone work, despite having a working one with version 7, is because I wanted to gift it to my sister. Yet, I find Jellybean a bit too old for this phone, and would also be cool to have all the features that is include in either Lollipop or Marshmallow.
It would be awesome if someone who found a solution to this problem, to share it with us.
{
"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"
}
:
Thanks!
Have you tried flashing factory images? I think that must work
Nitin
Fix
I just just fixed it!
I've realized that the screws where missing on the bottom, so I've opened the phone. I took the plastic shield off and realized that the Earphone Jack was not plugged. After plugging it back, I tried the update thinking it might be the solution and it is!
So basically what android does, it initializes the hardware while booting. It discovered that there is a component missing, so it got stuck on the initialization.
Thank you for trying to help c:
I still appreciate it!

NFC Issues - Doesn't turn on

Hi,
I have an issue with my OP5. I'm rooted with Magisk and I tried to use Card Emulator Pro app.
I think the app changed the NFC configuration of the OP5 and I can't turn on the NFC.
I tried to restore to NFC configuration back to default but it doesn't change.
Does anyone here has the same issue ?
Here is my log with the error
{
"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"
}
Regards,
Same issue
Today suddenly nfc stopped working. Can't turn it on in the settings. Have not done anything to it. No root no custom rom.
Fix found
AnthonyLebleu said:
Hi,
I have an issue with my OP5. I'm rooted with Magisk and I tried to use Card Emulator Pro app.
I think the app changed the NFC configuration of the OP5 and I can't turn on the NFC.
I tried to restore to NFC configuration back to default but it doesn't change.
Does anyone here has the same issue ?
Here is my log with the error
Regards,
Click to expand...
Click to collapse
Hey, i just fixed it by downgrading it to a earlier version. It must have something to do with the latest version firmware. try with 5.0 it worked for me. https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190 download it from here. It should fix it but it will perform a factory reset. but no media data will be lost. once downloaded place it on the phone and head to settings->update_then little ... menu and local file.
hope this helps. I use google pay alot so a fix is a must, thought it was hardware issue

Flashing a custom ROM on a ZED AN817DK?

Hey fellas,
I've done some flashing on android before, but only on smartphones, instead of a car multimedia. My model is ZED AN817DK.
It looks like this:
{
"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"
}
The launcher it came with is kinda disgusting, so I installed Nova Launcher instead.
Regardless, the system barely works, even on the stock settings / factory reset status.
Apps are crashing, changing the audio option in Waze takes a whole 2 minutes to even open up the menu for the option
(the app works but the input is unresponsive for 2 minutes until the menu appears).
I've tried contacting the shop I bought it in and they sent me a "firmware" update in the form of an APK file that will not launch in the device. I don't think I saw an option in it's administrator settings or anywhere else to update firmware via file (only check for firmware update - and it's always "up to date").
So I think I'll resort to flash a custom rom on this. I'm a bit worried since in the scenario where things go wrong I rely only on a pen hole style reset button which I don't fully trust to reset successfully if a custom rom is installed.
Is there a general flashing guide for these devices? How safe is it, as in what are the chances of completely bricking the device?
Are there general or common roms that work well on these devices?

Categories

Resources