Related
I dont know if this has been asked and fixed, i did the rom update, and i still having camera problems , it freezes and its lags can someone help
thaks in advance
You're gonna have to give us more information than this.
You've told us absolutely nothing else but "i did the rom update".
Rooted? S-OFF? Which ROM? Got ClockWorkMod Recovery installed?
Are you underclocking? might explain the lag.
If you got CWMR installed, try and run the Fix Permissions in recovery mode, helps with alot of FC's and general problems (it does for me atleast).
Hey, My wi-fi/hotspot shows up as error when i go to settongs and wireless networks. i had the problem with alien#4 so i decided to switch to cynanogen 7.1 and still nothing :/ is it a hardware problem or i need to flash a different baseband/kernel or what? thanks for the help in advance if anyone reples. it would mean alot haha
I had that issue when I installed one of faux123 kernels.I re-flashed the kernel wipped cache and dalvik and rebooted.I didn'tn have the issue afterwards,hope this helps out.
thanks. I tried flashing a 1.30 ghz kernel by faux123 and i have a bootloop :/
try flashing a different kernel.I notice the 1.3 works better than 1.45 for me no bootloops.try going into cwm and clear cache dalvik and fix permissions.
ok,im using tenfars recovery. should i be using clockwork mod?
i don't know what the problem is :/ i still have error for wi-fi.. but i flashed 145 cause that's all that would work
Atrixn00b said:
i don't know what the problem is :/ i still have error for wi-fi.. but i flashed 145 cause that's all that would work
Click to expand...
Click to collapse
Tenfa'rs recovery is outdated. Use romracer's instead (he just updated today).
*Edit* I ran into this same problem early on when I started flashing customs mods. Ended up having to go back to my "stock" backup before wi-fi started working again. After that, I haven't had it re-occur. That might be your best bet to get it functioning again. If not, it may be a hardware issue.
haha I just got this thing 3 months ago...hopefully it's not a hardware issue. but i'll try that
MY phone is completely effed right now..like the "soft keys" on the bottom don't work and the screen sensitivity is really low..it's like my phone is destroying itself or something.
Sounds like a hardware issue. I had the same exact issue.
Wifi error, some random reboots especially after trying to turn it on.
after much testing, reading, and playing around i started getting constant reboots. You could get too the lock screen, then it would reboot.
Before jumping to conclusions about hardware go back to your stock backup.Also use RomRacers newest recovery.then start flashing kernels again and see if the problem persists.Its easy to blame everything on hardware issues but often that's not the problem.
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Atronid said:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I do have used ROMs compatible with my device as they've all are made for espresso3g (which is my device).
I know it's not really the best way but I'll keep on trying with custom recovery for some more time and then perhaps try buying a new cable, and see if that works.
Tried installing Google Play Store from APK both on a clean ROM without GApps and with, but it still doesn't run and keeps on saying that either Google Play Store or "com.google.process.gapps" has stopped.
Alright...
I'm out of idea x/
lordquestionmark said:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
r&xp said:
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
Click to expand...
Click to collapse
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first seems to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
lordquestionmark said:
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
Click to expand...
Click to collapse
Ok...
This is what I would do if it was my device and I was facing what you are describing. It might take some time and a little patience to do everything described here, but it might also work.
1. Usin Odin, flash latest available official rom for the device. Let it boot and complete setup.
2. Use odin and use CF autoroot to root. Again boot and complete setup.
3. Flash Twrp. Enter Twrp and flash latest flashable supersu.zip. At this time I believe is version 2.82. Again boot and let it reach your welcome screen.
4. Enter Twrp. Enter advanced wipe. Wipe everything except external SD and usb at least 3 times. Do not exit twrp.
5. Install you rom. Do not exit Twrp.
6. After installing your rom, Twrp will ask you if you want to wipe cache/dalvik. "Yes" but DO NOT reboot.
7. Install correct version of gapps for your custom rom (correct both android version and architecture version). Again twrp will ask you to wipe cache/dalvik. "Yes" and this time reboot.
See what happens. If it gets stuck, try entering twrp again and do a factory reset only, only once and reboot again.
If that fails again... I will at a loss here myself too...
I did a quick search here on xda on P5100, I am providing some links that you can take a look at. You probably already searched yourself but you never know...
https://forum.xda-developers.com/ga...-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-blissmallow-t3312320
https://forum.xda-developers.com/showthread.php?t=1686514
https://forum.xda-developers.com/showthread.php?t=2581782
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candy-5-v2-5-5-t3136904
If nothing else helps, perhaps the best way to go around this would be to find a custom rom with at least some google apps pre-installed, in order to save you the trouble you are currently facing.
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
did you find a solution
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hey, just try uninstalling Google play services and install them again. I faced the same issue and now it's all working on my Samsung Galaxy Core 2
Hey guys! I recently downloaded Lineageos 14.1 Rom on my Meizu M2 Note, but after the upgrade, the sound volume is very low that i can barely hear anything from my earphones. I even googled this bug and founds out that After latest build? for 14.1 and 13.0 Lineageos has some kind of newest sound update that makes the sound more quiter. There were even 2 guides about fixing this.
The first one was by changing configurations in /device/etc/sound and changing to3g file, but sadly i do not have sound folder with to3g file.
The second one was by changing configurations in device/etc and changing this mixer_paths.xml file, but again i do not have it.
Is there any fix to this? because this low sound audio is annoying.
bump
emils2235 said:
Hey guys! I recently downloaded Lineageos 14.1 Rom on my Meizu M2 Note, but after the upgrade, the sound volume is very low that i can barely hear anything from my earphones. I even googled this bug and founds out that After latest build? for 14.1 and 13.0 Lineageos has some kind of newest sound update that makes the sound more quiter. There were even 2 guides about fixing this.
The first one was by changing configurations in /device/etc/sound and changing to3g file, but sadly i do not have sound folder with to3g file.
The second one was by changing configurations in device/etc and changing this mixer_paths.xml file, but again i do not have it.
Is there any fix to this? because this low sound audio is annoying.
Click to expand...
Click to collapse
Were you able to solve it? I'm the same situation. I don't have any of these folders or files... and it's really annoying
mdabar said:
Were you able to solve it? I'm the same situation. I don't have any of these folders or files... and it's really annoying
Click to expand...
Click to collapse
Nah, as much as i tried, unfortunately i couldn't solve it. Probably because it was custom rom idk really. I tried all the possible roms that i could use but no one didn't helped me to fix it. Later i tried to get back to stock rom, so i had to reinstall stock recovery. In the end I hard bricked my phone (completely dead, not a chance even by customer support because phones mobo died) Because of the stock recovery which i got Anyways i now have Xiaomi Redmi 4A, really cheap phone but at the same time even better than meizu m2 note. The only cons are that camera is bit worse, screen is smaller by .5 and screen can only support up to 720p. Anyways, maybe you could try to fix it by getting the phone to stock rom, but don't screw up like i did!
emils2235 said:
Nah, as much as i tried, unfortunately i couldn't solve it. Probably because it was custom rom idk really. I tried all the possible roms that i could use but no one didn't helped me to fix it. Later i tried to get back to stock rom, so i had to reinstall stock recovery. In the end I hard bricked my phone (completely dead, not a chance even by customer support because phones mobo died) Because of the stock recovery which i got Anyways i now have Xiaomi Redmi 4A, really cheap phone but at the same time even better than meizu m2 note. The only cons are that camera is bit worse, screen is smaller by .5 and screen can only support up to 720p. Anyways, maybe you could try to fix it by getting the phone to stock rom, but don't screw up like i did!
Click to expand...
Click to collapse
Thanks for your answer. I'm sorry you had the hard brick Did you trying re flashing everything with SP Flash Tools? It happened to me in the past and I was able to solve it with an old ROM v4.5 or so.
Now I'm with Lineage 14.1-20180523 and despite I followed all the steps (Magisk + Dolby...) The sound is still way too low :crying:
I've tried manually searching the files and sound config, but nothing, they're not. And even tried modifying some of the existing files related to volume... But no changes either.
So I'll keep looking and trying for the moment.
mdabar said:
Thanks for your answer. I'm sorry you had the hard brick Did you trying re flashing everything with SP Flash Tools? It happened to me in the past and I was able to solve it with an old ROM v4.5 or so.
Now I'm with Lineage 14.1-20180523 and despite I followed all the steps (Magisk + Dolby...) The sound is still way too low :crying:
I've tried manually searching the files and sound config, but nothing, they're not. And even tried modifying some of the existing files related to volume... But no changes either.
So I'll keep looking and trying for the moment.
Click to expand...
Click to collapse
Well, i did try to unbrick it, but since the mobo was dead, even the usb port didnt gave me any life. The phone was just bricked so bad that it wasn't possible to revive it. Atleast in my case. One thing that you could try is to check the motherboard of your phone(thats is if you are willing to) and see if you have anything damaged from the software. Because software can damage hardware. I was gonna say if you want you could actually change the motherboard with new replacement, but then it would probably ruin the Rom itself, because the system storage itself is built in the mobo. At this point im just clueless. Anyways good luck solving it!
emils2235 said:
Well, i did try to unbrick it, but since the mobo was dead, even the usb port didnt gave me any life. The phone was just bricked so bad that it wasn't possible to revive it. Atleast in my case. One thing that you could try is to check the motherboard of your phone(thats is if you are willing to) and see if you have anything damaged from the software. Because software can damage hardware. I was gonna say if you want you could actually change the motherboard with new replacement, but then it would probably ruin the Rom itself, because the system storage itself is built in the mobo. At this point im just clueless. Anyways good luck solving it!
Click to expand...
Click to collapse
At the end I could solve it by trying and trying...
Yesterday I found out that once I installed the last version of Magisk (the suggested one) it's when the some things didn't work properly. Following some other user advice I used an older version of Magisk.
Summary: with Magisk 16 I can download the Atmos package but cannot apply anything because the root was lost. With Magisk 14 the root works well, but then Atmos cannot be installed because of dependencies... finally Magisk 15.3 maintains the root and let you install and apply Atmos :highfive:
I just explained all that in case anyone else is having the same trouble.
Steps:
Install TWRP on your Meizu m2 Note
Install Lineage OS last version. I have 14.1-20180523 -> check here
Flash GAPPS (check your version on Open-GAPPS -> Arm64) -> here
Flash Magisk 14 (not a newer one! it lost the root for me) -> Magisk versions here
Wipe cache and Dalvik
Reboot the phone (it takes a few minutes)
Open Magisk (don't update it!) and check the root is ok, you can validate by opening ES Explorer or other app that asks for root permission
Reboot in recovery and flash Magisk 15.3
Wipe cache and Dalvik, it will take a few minutes again
Open Magisk (dont update!) and go to Modules (left menu)
Click on "+" and with the browser go to "Downloads"
Select the Atmos downloaded file, press and hold over the file until it's selected, then "Open" it. It will flash the version and reboot. You can download it from here
After Rebooting. Open "Audio FX" and disable it on top right. Then close the app.
Open "Dolby Atmos" enable the options you want/like and you'll see the difference
After rooting my s9+ with the modified Magisk, my phone sometimes becomes unresponsive. I cannot identify any sort of trigger for this to happen, it just does. The AOD displays but does not update. The notification LED still blinks, but when I go to unlock the phone it freezes and I am forced to soft reset it. I am root with Magisk and have TWRP installed. I followed Max Lee's tutorial on how to root the S9+. Any ideas on why this is happening and how to fix it?
Hey, Did you have any luck with this, i am having the exact same issue?
having the same problem i followed Max Lee video and everything work fine until the phone started freezing
same issue on the G960F/DS....
wonder who can help us regarding with this issue.
For everyone having this freezing after rooting...attention to detail is absolute paramount, go back and re-read the twrp thread by jesec. For those (possibly those having freezing issues) who find that challenging, here is a snippet of jesec exact words..." Samsung implemented security measures such as "Real-time Kernel Protection (RKP)" and "RKP Control Flow Protection".
Those security measures are intended to block control flows such as privilege escalation, memory kernel code modification, etc which are not authorized by Samsung.
If those are not disabled, processes (such as daemon of root solutions) that violated those security rules will fall into deadlock.
Deadlocked processes will then consume large amount of resources (leads to performance issues, battery drains) and eventually crash the system.
Technically it is possible to disable those security measures by hex editing stock kernel but just simply flash a custom kernel is better in my opinion.
TL;DR: Flash custom kernel before root or be screwed.
To reiterate...flash a custom kernel before root or be SCREWED
I'm not saying this is 100% u guys issue, but seems kinda likely?
can someone post links or steps on how to fix this freezing lock screen issue, i tried reading the threads but did not find anything, thanks
I was facing the exact same issue after using his tutorial.
I've tested SOD Killer from the Playstore so far it's working fine! No freezes anymore .
Installing a custom kernel like elementalX should also work.
crs_dev said:
I was facing the exact same issue after using his tutorial.
I've tested SOD Killer from the Playstore so far it's working fine! No freezes anymore .
Installing a custom kernel like elementalX should also work.
Click to expand...
Click to collapse
Can we flash this Elementalx over the N965F_Root_for_OEM_issue_devices/Magisk we already installed ?
I already installed the TWRP, No-verity opt encrypt and the N965F_Root_for_OEM_issue_devices package on my friend's 960F.
I would be really greatful if anyone could help me with this.
I had the same issue after having troubles initially getting Lineage flashed and working on my S9.
I removed Magisk, reset and it still was freezing after a lock.
I reflashed Lineage through TWRP and now all seems to be back to normal with no freeze after lock.
Possibly try the steps I did and see if they worked out for you.
hey guys, you solved the issue?
i experience same Problem..
Any one notice , this issue occurs after we apply lock screen password or biometric security. in my device i notice, when i apply lockscreen password or biometric lock my phone freeze. after i remove all lock and set default to swipe...its not freezing. anyone sees that
I solved the same issue (1 hour ago, so I hope it's fixed now) installing first:
ElementalX Kernel
and than installing:
G965_Root_for_OEM_issue_devices_V5 (the lastest available right now)
Following the instruction on the XDA Thread
Hope this can be helpfull to solve it
Its because of dm verity issues...i assume that you rooted the phone over an odin flashable stock rom. To fix this try installing either a patched stock kernel from Soldiers website or other custom kernels if you consider doing over(under)clocking.
KevAngelo14 said:
Its because of dm verity issues...i assume that you rooted the phone over an odin flashable stock rom. To fix this try installing either a patched stock kernel from Soldiers website or other custom kernels if you consider doing over(under)clocking.
Click to expand...
Click to collapse
What is the different in Soldie between Patched Kernel and ELS custom kernel?