Hi, I have an issue with my Leeco le max 2, when I plug the headphone to my device, nothing happen and the speaker continue to work like nothing happened..
I tried 2 adaptators (Usb-c to Jack) and both don't work. I changed the headphone and nothing changed.
With an application called "Phone Doctor", I saw that the phone don't detect anything when I plug the headphone, but the it charge correctly...
I don't know what to do, I installed a new rom (Lineage) but same problem. Can anyone help me ?
Does it work on EUI?
What about the original headset? Does it work?
The original headset don't work on my phone (I can't test on another). And it worked on eui à the first month and suddently it used to
DeazyL said:
Hi, I have an issue with my Leeco le max 2, when I plug the headphone to my device, nothing happen and the speaker continue to work like nothing happened..
I tried 2 adaptators (Usb-c to Jack) and both don't work. I changed the headphone and nothing changed.
With an application called "Phone Doctor", I saw that the phone don't detect anything when I plug the headphone, but the it charge correctly...
I don't know what to do, I installed a new rom (Lineage) but same problem. Can anyone help me ?
Click to expand...
Click to collapse
That's an old bug with lineage OS but now its fixed. But if you don't use lineage then try another ROM if that helps
I don't understand, I have the last version of Lineage OS
Heyyo, hmm can you please post a screenshot of your settings about page?
I hope this is what you are looking for
I up because I don't know what to do and if someone get the anwser
Hi. I'm not sure why but the images that you send are too blurry and I can't read anything. Can you send them again?
https://img4.hostingpics.net/pics/635589Screenshot20171030220952.png
https://img4.hostingpics.net/pics/693085Screenshot20171030220958.png
Is it better ?
Up ?
DeazyL said:
Up ?
Click to expand...
Click to collapse
Him strange. Maybe the cables are broken or something. I'm using my USB c headphones and I don't have any problems. I even tried USB c to jack and it also works.
Heyyo, hmm yeah very odd since that version does have the USB OTG and CDLA sound fixes...
Have you tried doing a fresh install of LineageOS and OpenGapps? Wipe system, data, dalvik and cache and then flash LOS 14.1 and OpenGapps.
Otherwise you could try OmniROM 7 with OpemGapps of choice as it also has those fixes implemented a while ago.
Same with SlimRoms or pretty much any recent ROM that also use the Codeworkx kernel with the CDLA and OTG paches
ThE_MarD said:
Heyyo, hmm yeah very odd since that version does have the USB OTG and CDLA sound fixes...
Have you tried doing a fresh install of LineageOS and OpenGapps? Wipe system, data, dalvik and cache and then flash LOS 14.1 and OpenGapps.
Otherwise you could try OmniROM 7 with OpemGapps of choice as it also has those fixes implemented a while ago.
Same with SlimRoms or pretty much any recent ROM that also use the Codeworkx kernel with the CDLA and OTG paches
Click to expand...
Click to collapse
I'll try it, should I do a backup of my app, pics etc?
DeazyL said:
I'll try it, should I do a backup of my app, pics etc?
Click to expand...
Click to collapse
If you want to make the transition easier yes
It didn't work, maybe should I try to wipe internal storage too ? idk what to do. Thx for help
DeazyL said:
It didn't work, maybe should I try to wipe internal storage too ? idk what to do. Thx for help
Click to expand...
Click to collapse
Well if she didn't work then yeah make sure all your stuff is backed up onto a PC and you have a PC available.
Then Format Data. Then type yes.
Wipe system, data, dalvik and cache just to be safe.
Then use your PC to transfer OmniROM or LineageOS and OpenGapps of choice onto your device. Since you've had issues with LOS I'd recommend OmniROM.
If regular usb MTP doesn't work then use...
adb push nameofthefile.zip /sdcard
Which will put the files onto the sdcard folder of your device.
I'd suggest trying the unbrick method described on the forum, using the Qualcomm flashing app. If that doesn't solve the issue, it may be a hardware problem.
The adapters you tried, were working before or were they brand new? On mine, I tried two different adapters bought on Aliexpress, and just one worked. The one included with the phone always worked, but others didn't always do.
First, if possible, try the LeEco original 3.5mm adapter. If that doesn't work, try the unbrick method and check again. If it works, then you might have a software conflict with something you had installed. If it doesn't work, then you'll have to contact the seller to see if you can get a replacement, or switch to bluetooth headphones.
ThE_MarD said:
Well if she didn't work then yeah make sure all your stuff is backed up onto a PC and you have a PC available.
Then Format Data. Then type yes.
Wipe system, data, dalvik and cache just to be safe.
Then use your PC to transfer OmniROM or LineageOS and OpenGapps of choice onto your device. Since you've had issues with LOS I'd recommend OmniROM.
If regular usb MTP doesn't work then use...
adb push nameofthefile.zip /sdcard
Which will put the files onto the sdcard folder of your device.
Click to expand...
Click to collapse
I did every step you told me, now i'm under OmniRom, but the Jack Problem persist
Related
It just stopped working. When I plug into PC, it just says it's charging? No idea what I could have done. I even tried restoring my backed up stock rom, but that made no difference. Tried two different PC's. What settings should I look for? Can I get to it via reboot, and pressing something. I seem to remember one time when my phone wouldn't boot, that I still had USB access.
big_dog1968 said:
It just stopped working. When I plug into PC, it just says it's charging? No idea what I could have done. I even tried restoring my backed up stock rom, but that made no difference. Tried two different PC's. What settings should I look for? Can I get to it via reboot, and pressing something. I seem to remember one time when my phone wouldn't boot, that I still had USB access.
Click to expand...
Click to collapse
If you have CWM installed then yes, you *should* be just fine. In mounts and storage menu, the last option i think is "mount USB storage" and it will show up in windows as removable storage then. If this doesn't work I can guess two things, one, your cable only has the power pins still connected, and not data. So try another cable. Or, on the USB connector inside your phone its not connecting both data pins, only power.
Should be able to visually check for damage to the micro usb port. Best of luck.
[r.]GimP said:
If you have CWM installed then yes, you *should* be just fine. In mounts and storage menu, the last option i think is "mount USB storage" and it will show up in windows as removable storage then. If this doesn't work I can guess two things, one, your cable only has the power pins still connected, and not data. So try another cable. Or, on the USB connector inside your phone its not connecting both data pins, only power.
Should be able to visually check for damage to the micro usb port. Best of luck.
Click to expand...
Click to collapse
I have TWRP. Does that change the suggestion?
big_dog1968 said:
I have TWRP. Does that change the suggestion?
Click to expand...
Click to collapse
not if there is an option to enable storage, I haven't used twrp in forever, so I can't tell you definitively. You could download CWM on your device and flash it in TWRP though.
USB port appears fine. Tried different cable that works on my son's phone and it still didn't work. Is there an app that is good for troubleshooting usb connections someone could recommend. Thanks.
big_dog1968 said:
USB port appears fine. Tried different cable that works on my son's phone and it still didn't work. Is there an app that is good for troubleshooting usb connections someone could recommend. Thanks.
Click to expand...
Click to collapse
According to google TWRP does have an option to mount usb storage, have you tried seeing if windows can recognize your phone storage in recovery?
An alternative solution could be to use a shared folder in windows and ES file explorer to connect to that share, and send and receive files that way, so at least you have some ability to manage the device. *through WiFi on the phone to the LAN that your PC is on*
I would suggest deleting all the drivers for your device in windows but you already said you tried on a second computer. I'm stumped on this one at the moment.
[r.]GimP said:
According to google TWRP does have an option to mount usb storage, have you tried seeing if windows can recognize your phone storage in recovery?
An alternative solution could be to use a shared folder in windows and ES file explorer to connect to that share, and send and receive files that way, so at least you have some ability to manage the device. *through WiFi on the phone to the LAN that your PC is on*
I would suggest deleting all the drivers for your device in windows but you already said you tried on a second computer. I'm stumped on this one at the moment.
Click to expand...
Click to collapse
Thanks for the suggestions. So far, none have worked. I wonder if there is an android app, that can check if the usb ports are working or not?
I had the same problem on SlimBean, Beanstalk and maybe another I can't remember. Switching to dvhexer's CM 10.2 fixed it. I THINK my problem was that those other ROMs require the phone to have been on stock 4.1.2 before flashing and dvhexer's CM 10.2 doesn't. I'm not sure, but that seems likely to me. In any case, make a backup of your current ROM and flash CM 10.2 to see if that fixes the issue. I really like Beanstalk but the ability to connect to my PC is vital to me so I'm on 10.2 for now. Hope this helps.
Sent from my Optimus G using XDA Premium 4 mobile app
Removed
Have the same problem :/ it randomly happened to me, haven't found any sort of fix.
I think I'm going to go back to stock, take it to a service center and say, "it aint workin". Still under warranty. Doubt they'll do much snooping if it appears to be running stock Rom.
Can you even flash back to stock? I tried flashing it once and it wouldn't boot, completely wiped everything and reinstalled and it still wouldn't boot, so I'm stuck on custom roms apparently with no connection to pc so no lgnpst possible
Sent from my LG Optimus G using Tapatalk 4
I suggest this ROM to everyone, is very smooth and fast, good battery life. The best I tried! Thank u madsurfer!
I found only two bugs:
1) I can't connect to my car's bluetooth, or better, device disconnects few seconds after the successful connection; (same problem in other ROMs);
2) I can't transfer files from the device to USB otg flash drive! I can only read/view files!
Thank u all for the attention.
raffa28 said:
1) I can't connect to my car's bluetooth, or better, device disconnects few seconds after the successful connection; (same problem in other ROMs);
Click to expand...
Click to collapse
Hello here!
I have the same ROM - yes, is great! But I can connect to my car's BT without any problems. Connection is stable all the time. Calls and media play are OK too.
I assume the problem is in your car wifi module or you didn't make a clean install of ROM.
Razor99 said:
Hello here!
I have the same ROM - yes, is great! But I can connect to my car's BT without any problems. Connection is stable all the time. Calls and media play are OK too.
I assume the problem is in your car wifi module or you didn't make a clean install of ROM.
Click to expand...
Click to collapse
Thank u for your answer Razor99! I did a clean install of the ROM.. Bluetooth has problems to connect only to the car... So I think there could be some incompatibility between the car and the device, because I never had problems to connect with other devices.
About the problem related to USB flash drive I solved it! Stock File manager doesn't work very well, I installed ES file manager and now I got no problems to transfer files or to make any other task.
What brand of car do you have? My is VW PASSAT, everything works well.
I also have Madsurfer's 21s and no problems too.
Control unit in car always comunicate with software in device - in this case your LeEco. If you didn't have these problems with another mobile:
1. Do a FULL WIPE including internal storage
2. Do a CLEAN install of ROM via ADB console in your PC
-> it should work
Razor99 said:
What brand of car do you have? My is VW PASSAT, everything works well.
I also have Madsurfer's 21s and no problems too.
Control unit in car always comunicate with software in device - in this case your LeEco. If you didn't have these problems with another mobile:
1. Do a FULL WIPE including internal storage
2. Do a CLEAN install of ROM via ADB console in your PC
-> it should work
Click to expand...
Click to collapse
Yes, no problem to connect with other devices.. I didn't wipe the internal storage and I flashed the ROM directly from the Recovery, could it be the problem?
I have fingerprint problem until I flashed internal memory. After than - It works. Give it a try.
Razor99 said:
I have fingerprint problem until I flashed internal memory. After than - It works. Give it a try.
Click to expand...
Click to collapse
Thank u for your suggestions! I will give a try!
XDA:DevDB Information
[ROM][7.1.1][Unofficially | LineageOS 14.1 For Huawei Ascend G760], ROM for the Huawei Ascend G7
very very thanks for:
dianlujitao
desalesouche
and others
Contributors
mparus
ROM OS Version: 7.x Nougat
Manifest: https://github.com/mparus/g760_lineageos-14.1
Downloads: https://forum.xda-developers.com/devdb/project/?id=19186#downloads
Mirror: https://androidfilehost.com/user/?w=settings-dev-files&flid=118309
Latest:
Check downloads page.
Previous: https://forum.xda-developers.com/devdb/project/dl/?id=23171 fix wifi reboot problem, fix move to sdcard apps problem, latest LOS commits
https://forum.xda-developers.com/devdb/project/dl/?id=23097 remove Gello browser - more space on /system partition, latest LOS commits, some wifi modifications
https://forum.xda-developers.com/devdb/project/dl/?id=23064 edit2: Please test the rom, maybe my tests were wrong
edit: this build is bad, random reboots often
disable CMUpdate app, update prima wifi driver in kernel (maybe fix random reboot after enable/disable airplane mode), latest LOS updates, please delete /data/misc/wifi/WCNSS_qcom_cfg.ini and /data/misc/wifi/WCNSS_qcom_wlan_cal.bin files or clean install recommended
https://forum.xda-developers.com/devdb/project/dl/?id=22978 fix restart to recovery and bootloader, latest commit from LineageOS
https://forum.xda-developers.com/devdb/project/dl/?id=22956
for root use: https://download.lineageos.org/extras (arm version)
stable twrp: https://www.androidfilehost.com/?fid=24421527759884484
new beta twrp: https://www.androidfilehost.com/?fid=529152257862699744
small google apps: https://github.com/opengapps/opengapps/wiki/Pico-Package
Issues: no gyroscope and USB otg
Version Information
Status: Stable
Created 2017-02-01
Last Updated 2018-02-18
Reserved
Having just issue with gyroscope not working properly so far everything else all good can't use file manager as won't let me access SD card so use root browser and no problem whatsoever
Thank you for your work!
So to continue from the other thread.
Seems large apps can't be moved, while small apps can.
I have 30gb free on the sdcard, but Final Fantasy 7 or 9 can't be moved there, giving the error "insufficient storage". However big files can be moved between location manually.
(Final Fantasy 7 doesn't run at all, and just instantly crashes when open. That game was always sensitive to where it was stored. It did work on your cm13, but not very well, its a bad port of the pc version I think
*Edit that, updated just got pushed by play store. What's changed state it doesn't work in 7.x Android).
Again, I am providing feedback as things happen. Not particularly asking for a solution, although maybe anything I come across can indicate issues to help with development.
Ooh another thing. In the expanded notification panel, pressing the pencil icon in order to rearrange the icon causes the phone to freeze for a minute or two, then brings up the lockscreen. Seems like SystemUI having issues but there is no error messages indicating that (but its that kind of behaviour from older Android versions that makes it seem like the case). It does not happen every time, but happens more than actually opening the rearrange page happens.
Sent from my Huawei Ascend G7 using XDA Labs
@mparus
Please always keep the first post up to date with the link for Latest Stable ROM, Latest Nightly ROM, Known Issues, Latest Recovery, Latest Kernel, etc.
Previous topic was not suitable for a new member or even an old member that didn't follow the topic for couple of days.
SD card working perfect on my G7-L01 in the 131 build.
Everything (so far) works great. Great ROM ?
Does anybody have mtp connection problem on latest build lieage rom ??
wish gapp i have to install ? lineage gapp or whatever??
Sent from my HUAWEI G760-L01 using Tapatalk
Sparko612 said:
Does anybody have mtp connection problem on latest build lieage rom ??
Click to expand...
Click to collapse
I got no problems (SD card not formatted as internal).
Although in some earlier builds when I formatted the SD card as internal storage I couldn't access internal memory from my PC.
So specify your problem a bit please?
NAJI23 said:
wish gapp i have to install ? lineage gapp or whatever??
Sent from my HUAWEI G760-L01 using Tapatalk
Click to expand...
Click to collapse
GApps 7.1 Arm.
NAJI23 said:
wish gapp i have to install ? lineage gapp or whatever??
Click to expand...
Click to collapse
Install 7.1 GAPPS on the ARM platform.
Well my SD card is showing on latest ROM but upon connection to PC it doesn't recognise internal or SD only adb connects and not sure what to do now ??
I'm still pretty new to this side of android what you mean SD card formatted as internal sorry for sounding so stupid
Sparko612 said:
Well my SD card is showing on latest ROM but upon connection to PC it doesn't recognise internal or SD only adb connects and not sure what to do now ??
I'm still pretty new to this side of android what you mean SD card formatted as internal sorry for sounding so stupid
Click to expand...
Click to collapse
Plug your phone to your PC. Then when it connects to the PC you'll have to open your status bar and see a notification saying "USB Charging this device". Click on it and you'll get a small menu with 4 options. Click on " Transfer files" (which is the second option) and then your phone will reconnect with your PC automatically and you'll be able to access the internal and SD card data from your PC.
And a feature has been added to Android ever since the 6.0 version where the users can configure the SD card to be able use it as Internal Storage. You can find that in the settings of your device?
Sparko612 said:
Well my SD card is showing on latest ROM but upon connection to PC it doesn't recognise internal or SD only adb connects and not sure what to do now ??
I'm still pretty new to this side of android what you mean SD card formatted as internal sorry for sounding so stupid
Click to expand...
Click to collapse
This is the notification
kamilb365 said:
This is the notification
Click to expand...
Click to collapse
Yes I get the notification but when I select transfer files nothing comes up and don't really know what else to do
How about lis3dh sensor devices? - working properly or have problems with gryro or screen rotation?
Sparko612 said:
Yes I get the notification but when I select transfer files nothing comes up and don't really know what else to do
Click to expand...
Click to collapse
Well what build are you running right now?
And did you clean or dirty install it?
kamilb365 said:
Well what build are you running right now?
And did you clean or dirty install it?
Click to expand...
Click to collapse
Clean install on latest lineage ROM build 131
Sparko612 said:
Clean install on latest lineage ROM build 131
Click to expand...
Click to collapse
This might be able to fix it. Go to developer options, scroll down to "select USB configuration" and change whatever setting you have to MTP. You might wanna switch modes a few times and then connect to PC with MTP active..
The bug has been active since cm13 in some cases and I personally never had the issue so I can't go into full depth of this.
kamilb365 said:
This might be able to fix it. Go to developer options, scroll down to "select USB configuration" and change whatever setting you have to MTP. You might wanna switch modes a few times and then connect to PC with MTP active..
The bug has been active since cm13 in some cases and I personally never had the issue so I can't go into full depth of this.
Click to expand...
Click to collapse
Gonna re download it tomorrow might be bad download anyway ive restored back to stock for now will look into it thank you all your tips
Edit: my model of device is G7 - L01 not sure if that may be the problem why im getting all this atm
Hello, I have problems with no audio and microphone activity when making calls or using Google Now/Assistant with a Bluetooth headset/car head unit.
The problem have persisted for some time now when making calls made via Bluetooth. At first it was limited to bad quality for recipients of my calls, and I blamed this on a new update to an unofficial Oreo ROM (Something PixelExperience).
However it has worsened, and now I cannot hear anything when making calls via Bluetooth, the microphone also seems to be cut off entirely, and the same is the case with Google Assistant.
Music and system audio seems to work just fine.
What I have tried without any luck so far:
A multitude of Oreo ROMS
Stock 26S chinese ROM (had to reinstall TWRP and everything)
Custom EUI 5.9 roms, based om 26S and 28S
A couple of different kernels
I am backup at running Resurrection Remix official Oreo atm.
I hope someone might have a clue at what to try.
If you need logs please let me know, however I am not an avid user of logcat/busybox(/others?) but should probably be able to use them og pointed in the right direction.
Lyngze said:
Hello, I have problems with no audio and microphone activity when making calls or using Google Now/Assistant with a Bluetooth headset/car head unit.
The problem have persisted for some time now when making calls made via Bluetooth. At first it was limited to bad quality for recipients of my calls, and I blamed this on a new update to an unofficial Oreo ROM (Something PixelExperience).
However it has worsened, and now I cannot hear anything when making calls via Bluetooth, the microphone also seems to be cut off entirely, and the same is the case with Google Assistant.
Music and system audio seems to work just fine.
What I have tried without any luck so far:
A multitude of Oreo ROMS
Stock 26S chinese ROM (had to reinstall TWRP and everything)
Custom EUI 5.9 roms, based om 26S and 28S
A couple of different kernels
I am backup at running Resurrection Remix official Oreo atm.
I hope someone might have a clue at what to try.
If you need logs please let me know, however I am not an avid user of logcat/busybox(/others?) but should probably be able to use them og pointed in the right direction.
Click to expand...
Click to collapse
Maybe the mic is broken. If you tried with so much ROMs that's definitely a hardware problem.
LameMonster82 said:
Maybe the mic is broken. If you tried with so much ROMs that's definitely a hardware problem.
Click to expand...
Click to collapse
Thank you for the answer, the microphone is not the problem. I have tested the bluetooth headset using another smartphone with no issues.
The issue also persists with my car head unit, it might be a faulty bluetooth unit, however it works just fine when transfering data and listening to music.
I only experience the problems when trying to use microphone or call using the bluetooth headset.
Lyngze said:
Thank you for the answer, the microphone is not the problem. I have tested the bluetooth headset using another smartphone with no issues.
The issue also persists with my car head unit, it might be a faulty bluetooth unit, however it works just fine when transfering data and listening to music.
I only experience the problems when trying to use microphone or call using the bluetooth headset.
Click to expand...
Click to collapse
I did the following:
Reset and begin from scratch....
-Install TWRP latest version if you have not.
-Make backup external of your data, media, etc.
-Wipe everything cach, system, dalvik, data, internal.
-Restart in recovery.
-Download a EUI 19s rom on PC and transfer to your TWRP map on your phone.
-Install trough TWRP the EUI Rom and let it boot.
-Make the minimalist settings, so the rom is installed on your phone.
-After that go to recovery, choose format your phone.
-Restart recovery.
-Transfer the modem firmware 26S, your choise Oreo rom, and Gapps arm 64, 8.1, nano to your phone.
( Advice: infrag AICP unofficial 20032018 version, bugless)
-install those together without reboot in between.
-After that Reboot system.
When making settings in the rom CHOOSE NEW PHONE, DO NOT DOWNLOAD YOUR SETTINGS TROUGH GOOGLE ACCOUNT and do not install other backups.
Then you will have a total clear phone.
Very much work but it helped me with camera and audio problems.
I hope it does for you too.
Thank you, I will try that when I have some time at the computer, I did All og the above except for installing 19S beforehand.
I have read about another who had similar problems to med, and Foxes them by replacing a systems file. Is there any way of optaining this file without flashing the rom and extracting it? Can I open the rom file directly to extract the file? (Filename was Bluetooth-***.so or something)
Edit: This is the post I al talking about: https://forum.xda-developers.com/le-max-2/help/issues-bt-16s-t3543635
Lyngze said:
Thank you, I will try that when I have some time at the computer, I did All og the above except for installing 19S beforehand.
I have read about another who had similar problems to med, and Foxes them by replacing a systems file. Is there any way of optaining this file without flashing the rom and extracting it? Can I open the rom file directly to extract the file? (Filename was Bluetooth-***.so or something)
Edit: This is the post I al talking about: https://forum.xda-developers.com/le-max-2/help/issues-bt-16s-t3543635
Click to expand...
Click to collapse
It is the Bluetooth file of 15S....That's a very long time ago.
I'm not sure with compatibility.
Very much so, however a similar approach might work with say 19S.
But I don't know how to get the .so file without flashing the rom and copying it from the system directory...
I have now tried installing both Chinese 15S and Indian 19S without any luck, I am still not able to use bluetooth for calling. No sound or microphone what so ever using the bluetooth headset.
Lyngze said:
I have now tried installing both Chinese 15S and Indian 19S without any luck, I am still not able to use bluetooth for calling. No sound or microphone what so ever using the bluetooth headset.
Click to expand...
Click to collapse
Does your bluetooth status says connected (no phone)
in the same post https://forum.xda-developers.com/le-max-2/help/issues-bt-16s-t3543635/page2 pn #12 there is bluetooth so file
try that... it works on every EUI version... to verify .. try EUI 16s (Indian ver) and check your bluetooth device
Thank you for pointing that out!
I have tried with a clean install of the entire 15S ROM without any help.
I tried the .so file with my Oreo system, and now I cannot event turn bluetooth on...
Regarding bluetooth status it just says "connected" followed by battery percentage.
I can turn phone audio on or off without problem, but when turned on there is simply no sound in calls...
Hello everyone!
Pls help me on this one...
I have:
- unlocked Boot loader
- installed Twrp 3.2.1 vendor patch
- installed Magisk 16.0
- flashed DotOs 2.4 treble ROM
- installed Franco kernel (fk6)
on my Redmi Note 4 (mido).
The problem is:
- whenever I reboot my device a message appears from DotOs System which says: There is an internal problem in your device. Please contact your manufacturer.
- whenever I play Pubg mobile, my phone usually reboots... And these random reboots occur not only in pubg but also in other apps if I try to multitask or click the buttons fastly or try to use my phone very quickly.
Please help me guys.
-Thank You:good:
Shoury_Jain55 said:
Hello everyone!
Pls help me on this one...
I have:
- unlocked Boot loader
- installed Twrp 3.2.1 vendor patch
- installed Magisk 16.0
- flashed DotOs 2.4 treble ROM
- installed Franco kernel (fk6)
on my Redmi Note 4 (mido).
The problem is:
- whenever I reboot my device a message appears from DotOs System which says: There is an internal problem in your device. Please contact your manufacturer.
- whenever I play Pubg mobile, my phone usually reboots... And these random reboots occur not only in pubg but also in other apps if I try to multitask or click the buttons fastly or try to use my phone very quickly.
Please help me guys.
-Thank You:good:
Click to expand...
Click to collapse
This is caused due to franco kernel on an older patch. Nothing really worth worrying about.
MyNameIsRage said:
This is caused due to franco kernel on an older patch. Nothing really worth worrying about.
Click to expand...
Click to collapse
Umm okay, so what should I do now? By the way, thanks...
Shoury_Jain55 said:
Umm okay, so what should I do now? By the way, thanks...
Click to expand...
Click to collapse
I wouldn't trust my life (android device) on franco kernel for now. If I were you I'd download latest Lineage Rom, latest gapps, Magisk vcustom version that supports treble enabled roms, then kud kernel. Put them on an external sd or file storage, completely wipe my phone except the external part of it, then flash them in the said order. Franco kernel been updated quite a while ago. Since then lots of things have changed in the aosp based roms. The kernel might cause those problems of yours. Also first of all, before doing anything I'd flash latest Orange Fox Treble enabled recovery R6 beta, which solves some flashing issues. This is what I'd do to solve those problems of yours within 10 minutes. But it's just me, a purist being real and being safe than sorry.
greenys' said:
I wouldn't trust my life (android device) on franco kernel for now. If I were you I'd download latest Lineage Rom, latest gapps, Magisk vcustom version that supports treble enabled roms, then kud kernel. Put them on an external sd or file storage, completely wipe my phone except the external part of it, then flash them in the said order. Franco kernel been updated quite a while ago. Since then lots of things have changed in the aosp based roms. The kernel might cause those problems of yours. Also first of all, before doing anything I'd flash latest Orange Fox Treble enabled recovery R6 beta, which solves some flashing issues. This is what I'd do to solve those problems of yours within 10 minutes. But it's just me, a purist being real and being safe than sorry.
Click to expand...
Click to collapse
Wow. Thanks, I would definitely try those...
greenys' said:
I wouldn't trust my life (android device) on franco kernel for now. If I were you I'd download latest Lineage Rom, latest gapps, Magisk vcustom version that supports treble enabled roms, then kud kernel. Put them on an external sd or file storage, completely wipe my phone except the external part of it, then flash them in the said order. Franco kernel been updated quite a while ago. Since then lots of things have changed in the aosp based roms. The kernel might cause those problems of yours. Also first of all, before doing anything I'd flash latest Orange Fox Treble enabled recovery R6 beta, which solves some flashing issues. This is what I'd do to solve those problems of yours within 10 minutes. But it's just me, a purist being real and being safe than sorry.
Click to expand...
Click to collapse
Bro noting hepled me... What's should I do now, it was working fine for a few days but now I m back with the same problem...
Shoury_Jain55 said:
Bro noting hepled me... What's should I do now, it was working fine for a few days but now I m back with the same problem...
Click to expand...
Click to collapse
Did you try everything I wrote above? These steps should work in case you badly messed up your system. I mean, I fiddle and meddle with my OS all the time, often rendering my phone unusable. As much that I have to clean wipe and reinstall the whole OS following the steps I provided. There was no case when a whole, system wide wipe and a clean install wouldn't solve.
greenys' said:
Did you try everything I wrote above? These steps should work in case you badly messed up your system. I mean, I fiddle and meddle with my OS all the time, often rendering my phone unusable. As much that I have to clean wipe and reinstall the whole OS following the steps I provided. There was no case when a whole, system wide wipe and a clean install wouldn't solve.
Click to expand...
Click to collapse
Yep...
Installed lineage 15.1
Kud kernel
Magisk 16.7
Orange fox recovery
Still it redboots randomly sometimes...
Shoury_Jain55 said:
Yep...
Installed lineage 15.1
Kud kernel
Magisk 16.7
Orange fox recovery
Still it redboots randomly sometimes...
Click to expand...
Click to collapse
Perhaps I can give you one more tip that you can try.
First, if you have an external SD card make sure to copy latest stable global MiUi ROM, latest Lineage OS for mido, latest open gapps, kud kernel, Magisk 16.0 treble enabled and orange fox onto it. If not then download these to your pc or laptop.
1) Make a full wipe including system, data, vendor, cache, dalvik and internal storage.
2) From TWRP flash latest MiUi stable global rom.
(if you have external SD do it from there, if you don't, since you made a full wipe, your internal SD is empty. Through USB sideload copy MiUi onto your internal SD and flash it from there if you don't have an external SD with the flashable zips on it)
3) Boot up the system, make sure everything is working.
4) Reboot to TWRP and do a full wipe again.
5) Flash Lineage OS from your external SD or copy the required zip onto your internal SD through USB sideload.
6) Now flash latest gapps (pico is far enough)
7) Flash Kud Kernel
8) Flash Magisk 16.0 treble enabled or magisk vcustom, they are the same but more stable than 16.7 which is still beta.
9) Reboot to system and see for yourself if everything is working.
I hope this solves your problem. Sometimes if you flash back MiUi it solves some crash perhaps firmware related problems. I don't know but this helped me a few times. If you messed up something USB sideload is always an option to copy any flashable zip onto your internal SD, however I always use external SD for it's easy to trust and use.
In case your data/internal SD shows 0 kb/mb free space do a data wipe and a partition from special settings in TWRP with all sizes set to 0.
I don't have any more tips to help you. Sorry.
I would say get Orangefox or Redwolf recovery if you dont have them already. Try flashing any rom and see if your problem persists,if not flash magisk and custom kernels. With the process of elimination you should know the source of the problem which i think is francokernel as it was mentioned.
greenys' said:
Perhaps I can give you one more tip that you can try.
First, if you have an external SD card make sure to copy latest stable global MiUi ROM, latest Lineage OS for mido, latest open gapps, kud kernel, Magisk 16.0 treble enabled and orange fox onto it. If not then download these to your pc or laptop.
1) Make a full wipe including system, data, vendor, cache, dalvik and internal storage.
2) From TWRP flash latest MiUi stable global rom.
(if you have external SD do it from there, if you don't, since you made a full wipe, your internal SD is empty. Through USB sideload copy MiUi onto your internal SD and flash it from there if you don't have an external SD with the flashable zips on it)
3) Boot up the system, make sure everything is working.
4) Reboot to TWRP and do a full wipe again.
5) Flash Lineage OS from your external SD or copy the required zip onto your internal SD through USB sideload.
6) Now flash latest gapps (pico is far enough)
7) Flash Kud Kernel
8) Flash Magisk 16.0 treble enabled or magisk vcustom, they are the same but more stable than 16.7 which is still beta.
9) Reboot to system and see for yourself if everything is working.
I hope this solves your problem. Sometimes if you flash back MiUi it solves some crash perhaps firmware related problems. I don't know but this helped me a few times. If you messed up something USB sideload is always an option to copy any flashable zip onto your internal SD, however I always use external SD for it's easy to trust and use.
In case your data/internal SD shows 0 kb/mb free space do a data wipe and a partition from special settings in TWRP with all sizes set to 0.
I don't have any more tips to help you. Sorry.
Click to expand...
Click to collapse
Still didn't work
Maybe there is some hardware problem...
Well, thanks for the help! ?
Shoury_Jain55 said:
Still didn't work
Maybe there is some hardware problem...
Well, thanks for the help!
Click to expand...
Click to collapse
Oh, well. Perhaps you're right. I do this every week and works. I'm sorry I couldn't help you.
Shoury_Jain55 said:
Hello everyone!
Pls help me on this one...
I have:
- unlocked Boot loader
- installed Twrp 3.2.1 vendor patch
- installed Magisk 16.0
- flashed DotOs 2.4 treble ROM
- installed Franco kernel (fk6)
on my Redmi Note 4 (mido).
The problem is:
- whenever I reboot my device a message appears from DotOs System which says: There is an internal problem in your device. Please contact your manufacturer.
- whenever I play Pubg mobile, my phone usually reboots... And these random reboots occur not only in pubg but also in other apps if I try to multitask or click the buttons fastly or try to use my phone very quickly.
Please help me guys.
-Thank You:good:
Click to expand...
Click to collapse
Wrong forum.
Go to DotOs forum, and ask your question.
Mybe your rom not compatible for mido.
Shoury_Jain55 said:
Yep...
Installed lineage 15.1
Kud kernel
Magisk 16.7
Orange fox recovery
Still it redboots randomly sometimes...
Click to expand...
Click to collapse
Probably Cpu throttling service asks for increase in cpu frequency due to the requirement , but when the cpu frequency is scaled up high , but due to some internal problem (temperature sensor failure or faulty processor etc...) the temperature detected is too high that the phone reboots.
TBH I have no idea about how android devices work but this happens on PS4 due to burnt capacitors , this can be fixed sometimes.
Buddy I will help u...
Just download the build.prop editor from playstore and grant root permission and search for ro.treble.enabled line and change it to false:fingers-crossed:
rc chanu said:
Buddy I will help u...
Just download the build.prop editor from playstore and grant root permission and search for ro.treble.enabled line and change it to false:fingers-crossed:
Click to expand...
Click to collapse
Thank you bro, works for me.
Very nice!!!