Hello to you,
After doing some research without finding answers I allowed myself to create a post on the forum.
I apologize if I put my post in a bad section.
Here is my problem:
When I got home, I noticed that I did not have any sound coming from the speakers of my Xiaomi Redmi Note 4X (mido) with the LineageOs rom, that is to say at the beginning after all worked, it is not not fallen.
For the ringtone and the alarm is ok it's only for all that is music and video, I have not yet test a call in HP.
To try to solve the problem I have to reinstall my phone at 100% while updating the rom but no change is always a problem which is not dramatic the phone is usable but removes some possibility.
Would you have solutions?
Meri in advance for your help and I wish you a good day / evening
Updating is not a reinstallation. It is dirty flashing, where all your settings and modifications survive. Try to go to twrp and wipe system, data and caches. Now flashing gives you a clean installation.
Related
HI all,
I've flashed CWM5.5 from the recomended thread and installed Cyanogen 9 Alpha 1. Unfortunatly the phone seems to boot up but does never leave the boot animation screen (yes I've also flashed gapps after cyanogen).
Anyone can identify this pattern? On a normal device I could hook it up through a serial cable and try to debug the boot... Eventually how can I do that with a I8150?
Well, any help would be most welcome. I'm totally available for testing and I do have some experience with Linux even at a very low level/system space.
Install
Use CWM5.
Warning: Only use this recovery to flash CM9. Otherwise, you risk bricking your phone!
Wipe data and cache.
Flash update*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade to CM9 since /system is formatted, wiping your previous add-ons.
Reboot phone.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
Warning: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
read it thoroughly ...
1st you must flash update*.zip
2nd gapps*.zip
that just about it ....
what is your current kernel ?
That was pretty much it... I've restored not the original operator crap ROM, but instead the Value Pack ROM.
CyanogenMod9 seemed to install ok, but just looped and the phone didn't finished the boot. I'm not really sure on what happened. I'm just finishing restoring the stuff
I'm guessing you didn't wipe data/cache.
I did a factory reset, but sure, it might not have wiped the whole thing... Going to try again.
@argo68
True mate, the issue was not wiping the user cache. I've wiped the cache now from ClockWorkMod and it worked ok. Takes some time to boot compared to the stock samsung ROMs but it works fine
Anything you need tested ? I can most likely help.
I do have a problem with apps though, for example, GMAIL doesn't show the body of the message... as you can see on the screenshot, but I guess this is a app related issue maybe?
http://susepaste.org/images/39081870.png
After a reboot somehow it boots a bit faster and the gmail app is now displaying the body of the email and it seems a bit faster...
Good work, gonna ride this for a few days and see what happens.
@argo68
If you need beta testers, let me know. I'm off work this days but can't wait to get into my lab and check this stuff deeper
@argo68
he is arco68
just in case he takes offence, which I don't believe he would
Hopefully not, all the norwegians I knew personally were very nice people and always ready for some bear
ketheriel said:
Hopefully not, all the norwegians I knew personally were very nice people and always ready for some bear
Click to expand...
Click to collapse
reAdy for some BEAR ????
do you actually mean bear or beer ??
chocolemon said:
reAdy for some BEAR ????
do you actually mean bear or beer ??
Click to expand...
Click to collapse
Maybe it's the Nordic ascendance. They fight a bear with one hand while holding the beer with the other.
Hi I'm using this cyanogen mod for quite a few days now. The back side of the phone is always warm and the battery is drained very fast. Anyone have this similar problem?
I'm sure that I install the ROM correctly as i cleared everything on the phone with CWM 5.0.0.4 before and after. (Phone data / Cache Partition / Dalvik Cache / Battery Cache)
Any help would be appretiated
No such problem here. You should use an app to check what frequency the phone is running at in idle, and also how much load there is on the cpu.
I have a issue where whenever someone not in my contact list calls me I get gibberish instead of the caller id . I love this ROM and use it as my daily driver and would love to resolve, if not just remove caller I'd so if I get a call I just see the numberand not gibberish , thank you !!
I assume you've tried rebooting your phone? What happens on a reflash? My guess would be that you did a dirty flash. Paranoid Kangdroid slaps a lot of different stuff together, so even between closely related versions you often have to wipe data/cache, fix permissions, etc. There is a new version that came out yesterday and it still requires a full data wipe even if you were on the previous release. That's the only reason I haven't flashed it yet. Well, that and they seem to be having some issues that are getting sorted out.
I never do a dirty flash, I always do it all,wipe cache dalvik and format and I just got the ROM yesterday the minute it was released. If it helps I came from the liquid ROM and my current kernel is kt. If there's no fix I don't mind but it would be nice to just have the phone number show up until the bugs sort out if its possible. I love this ROM !
Re-wipe and flash
I would say that you should post this in a more appropriate thread (the PK development thread) but they're just going to tell you to rewipe, dalvik, flash etc. If it's repeatable then its a bug and you can share your info so they can work on it, but my guess is that you just need to wipe and flash again and all will be well. If it is a bug and is as simple as you describe, many more people would be reporting it.
Received Dev edition note 4 on 11/26. Put it through its paces for a day to make sure everything was good before rooting. Didn't even think to make a call on speakerphone during this time. All was good and rooted this morning using jpcalhoun's thread in the development section. Well lo and behold, made some speakerphone calls tonight and microphone is not working. I have tried the following:
Factory data reset
Restore TWRP backup I made prior to rooting
Wipe Dalvik
Wipe Cache
Flash the rom EMSpilot put together for DEV edition
various other fixes I found searching around - stuff that related to the S5 and google now - hey, I'm desperate!
Anyone have any ideas on other things to try? I am afraid that it might be a hardware issue and I may be SOL as far as warranty support goes with Samsung.
I switched to the Honor 7x from my Ascend Mate 2 a few months back, and while I love close to everything about this phone, my headphones are substantially quieter using the headphone jack on this phone. I tried fixing this originally by installing viper4android and/dolby, but neither wanted to work on the stock rom. I then tried upgrading to Android Pie, and they didn't work on that, then I tried Resurrection Remix, Omnirom and Lineage OS, and neither would work on any of those either. (I already used the Morfuz kernel to switch to permissive on each rom, didn't help).
I am about at my wit's end and really don't want to have to carry a headphone amp with me. Have any of you found a fix for this?
I had assumed that it was a limit set somewhere in it's OS or software, but could it be a hardware limit that's can't be bypassed?
There is probably some fancy way by editing system files or flashing something.
Since I'm stuck with a locked bootloader and therefor without root or custom recovery I use this app: https://play.google.com/store/apps/details?id=com.goodev.volume.booster
I know it's super nooby to solve it this way but I'm not smart enough to figure out another way. I hope this may help you.
Edit: I blocked the notification and enabled start on bootup, so I it's not bothering me. Boost is set to 8% which works fine for me.
br0wni3 said:
There is probably some fancy way by editing system files or flashing something.
Since I'm stuck with a locked bootloader and therefor without root or custom recovery I use this app: https://play.google.com/store/apps/details?id=com.goodev.volume.booster
I know it's super nooby to solve it this way but I'm not smart enough to figure out another way. I hope this may help you.
Edit: I blocked the notification and enabled start on bootup, so I it's not bothering me. Boost is set to 8% which works fine for me.
Click to expand...
Click to collapse
I was using the same app when I was on a stock rom, but had issues with it crashing constantly and having to reopen it. That and you only get a little bit of a boost before it starts clipping from my experience. I am going to do some volume tests with custom roms today and will post my findings here.
Hello,
Got an S9 wich has been smoothly running SoLdierR ROM for a couple of weeks. Until two days ago, when my phone decided otherwise. If I restart the phone, the freezing stops for a bit and isn´t noticeable until I start opening apps and that´s when it starts getting really annoying. After that the freezing starts occuring in intervals every 10sec for 3-4 sec. This is making me miss messages/voice calls if these occur during freezing intervals. If I remembers correctly, this started right after I cleared phone memory a couple of days ago. Is there any way to resolve this without me having to backup data and restoring phone?
What I've tried doing so far:
Restarts, shutting down phone for longer periods of time, booting in safe mode (still freezing), booting in recovery mode and deleteing cache/dalvik, deleting apps recently installed, inactivating google apps (google, google play, google services) and deleting cache then unstalling update and then reactivating them, removed root.
yarmannen said:
Hello,
Got an S9 wich has been smoothly running SoLdierR ROM for a couple of weeks. Until two days ago, when my phone decided otherwise. If I restart the phone, the freezing stops for a bit and isn´t noticeable until I start opening apps and that´s when it starts getting really annoying. After that the freezing starts occuring in intervals every 10sec for 3-4 sec. This is making me miss messages/voice calls if these occur during freezing intervals. If I remembers correctly, this started right after I cleared phone memory a couple of days ago. Is there any way to resolve this without me having to backup data and restoring phone?
What I've tried doing so far:
Restarts, shutting down phone for longer periods of time, booting in safe mode (still freezing), booting in recovery mode and deleteing cache/dalvik, deleting apps recently installed, inactivating google apps (google, google play, google services) and deleting cache then unstalling update and then reactivating them, removed root.
Click to expand...
Click to collapse
when you installed your custom ROM, did you delete the folder on internal storage named "android"?
youdoofus said:
when you installed your custom ROM, did you delete the folder on internal storage named "android"?
Click to expand...
Click to collapse
I believe I did, used TWRP and wiped everything before installing my custom ROM. I'am starting to think about doing a clean install all over again however, that won't mean that this issue won't come back later?
yarmannen said:
I believe I did, used TWRP and wiped everything before installing my custom ROM. I'am starting to think about doing a clean install all over again however, that won't mean that this issue won't come back later?
Click to expand...
Click to collapse
considering there arent that many variables that go into ROM installation, its likely just some one-off situation. If it wasnt, there would be a ton of folks reporting the same issue. Sometimes dropping fat man or little boy and starting over is all thats left. Been there so many times with the S3 and S5, i cant even begin to tell you.
youdoofus said:
considering there arent that many variables that go into ROM installation, its likely just some one-off situation. If it wasnt, there would be a ton of folks reporting the same issue. Sometimes dropping fat man or little boy and starting over is all thats left. Been there so many times with the S3 and S5, i cant even begin to tell you.
Click to expand...
Click to collapse
Yepp! I doing a clean install atm. Got another question wich is a bit off-topic. I'am using soliders latest ROM, I noticed he did release a new firmware update. Is it enough flashing the ROM or do I have to flash firmware by itself later? Or do I simply do nothing after flashing the ROM? Sorry if I'am asking obvious question but this a all still new to me.
yarmannen said:
Yepp! I doing a clean install atm. Got another question wich is a bit off-topic. I'am using soliders latest ROM, I noticed he did release a new firmware update. Is it enough flashing the ROM or do I have to flash firmware by itself later? Or do I simply do nothing after flashing the ROM? Sorry if I'am asking obvious question but this a all still new to me.
Click to expand...
Click to collapse
no worries mate, we all try to take a look at members post count before casting judgement on them for the question they asked. For that matter, we try to avoid casting judgement period, and im saying that as a member, not a moderator.
im not directly familiar with the soldier run of ROMs, but if the firmware version has changed, it is wise to install the full firmware.
Also, i wouldnt consider what you asked to be off topic at all.
youdoofus said:
no worries mate, we all try to take a look at members post count before casting judgement on them for the question they asked. For that matter, we try to avoid casting judgement period, and im saying that as a member, not a moderator.
im not directly familiar with the soldier run of ROMs, but if the firmware version has changed, it is wise to install the full firmware.
Also, i wouldnt consider what you asked to be off topic at all.
Click to expand...
Click to collapse
Good to know
I've run into a problem after flashing the custom ROM. I'am stuck on the Samsung logo, what should I do? Would appreciate a step by step explanation.
yarmannen said:
Good to know
I've run into a problem after flashing the custom ROM. I'am stuck on the Samsung logo, what should I do? Would appreciate a step by step explanation.
Click to expand...
Click to collapse
well, you have TWRP and magisk installed, i assume. Correct?
youdoofus said:
well, you have TWRP and magisk installed, i assume. Correct?
Click to expand...
Click to collapse
Yes! TWRP is installed. Magisk got installed with the ROM.
yarmannen said:
Yes! TWRP is installed. Magisk got installed with the ROM.
Click to expand...
Click to collapse
to be perfectly honest, if youve done all the things in the OP and its still doing that, its time to drop fat man or little boy and start from stock tar.md5. Boot to DL mode and flash the stock firmware. Obviously something is awry and the usual tricks didnt help so far. Mushroom cloud time