I know this should not be a big deal but I have an issue with EMUI on Android 6.0.1 on my P8: PowerAMP skins does not work on any EMUI based device over Android 6.0.1 (not just the P8).
Unfortunatelly I dont know much about ROM developments and the causes of the issue, or if there is a way to fix it. As some of you guys develop ROMs you might have a clue what cause this problem? Or could you consider it during the development of Your new ROM if it does not take much of your time?
Thanks.
I have a P8 with the latest firmware update (B382) & PowerAmp skins work fine.
Perhaps some other common app installed on both is causing the problem?
Are your phones with stock Huawei firmware, unrooted & unaltered in any way?
Have you tried uninstalling & reinstalling PowerAmp?
This is my present ROM's full build number (Europe/UK): GRA-L09C432B382
EMUI version: 4.0.1
Android version: 6.0 (not 6.0.1)
Related
Dear Community,
I hope that this is the right place to post and any of you can help me.
My (aktual) Hardware/Software bits:
Galaxy Note 3 (SM-N9005)
Android: 5.1.1
Baseband-Version: N9005XXUGBOD3
Kernel-Version 3.4.108-f2fs-temasek-cm12.1-hlte-v1.25+
temaseksnappy #1
Temasek unofficial version V16.4
Build: LMY48J test-keys
Recovery: twrp 2.8.7.0-hlte-4.4
My actual problem is the following: My Note 3 by default had a 4.4.2 OFW on it, which I early upgraded to Lolipop 5.0.1. Everything works for the OFW 4.4.2 and 5.0.1 fine. As soon as I try to flash it with a CFW like CM11, CM12, CM12.1, CM12.1 (temaseksnappy), Gummy 4.4.4 I am losing the feature of auto rotation.
Of cource I did a clean flash, wiping DALVIK/CACHE/DATA and system, double time even one befor the flash, one after.
I also tried to put the battery, sim and sd out for few min before rebooting, while autorotation is manualy turned off.
Even a MODEM I flushed to fix this issue, but without success. Nothing helps but going back to OFW.
My last try was downgrading to the original 4.4.2, including baseband trieing from there to go to any CFW (CM11) as well as from OFW 4.4.2 -> OFW 5.0.1 -> CFW 5.1.1 (http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375)
There was also a post about a possible missing or broken lib in /system/lib which I replaced
Nothing helps (libGNU... something). This helped me alreay once in OFW after kicking out all the junk apps, but this is a different storry and not related anyhow.
Is there anybody out there who has the same problem or even better knows a solution?
My shot would be that:
1) CM has a problem with my particular hard-/software (Kernel, Baseband, Recovery, whatever) as I just tied CM or at least CM based CFWs.
PLEASE HELP.
Thank you very much in advance.
After about almost a year I cam back, giving again a try to CM, However I still have the same issue. Finally Anybody please!
Do you have the same issue with touchwiz 5.1.1 and 6.0.1?. Not the cm/aosp roms which aren't samsung based.
Sent from my SM-N920C
Rosli59564 said:
Do you have the same issue with touchwiz 5.1.1 and 6.0.1?. Not the cm/aosp roms which aren't samsung based.
Sent from my SM-N920C
Click to expand...
Click to collapse
Hello,
Thx for your reply. Right now I am on CM13 (temasek hlte v9.6)
http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375
This might should be specially compiled for sm-n9005 like mine.
Everything expect rotation works fine. However The accelleration is also working fine as I tested with "sensor test". Even the integrated camera App is rotating, however the rest is not.
In addition I downloaded "adaptive rotationfree", If I set it "stock Auto" nothing happens, but if I set it to "force auto" the rotation will work exacly once and then stops undtil I force it to portrait again.
What do you mean exactly with "touchwiz"? Is this jus a different kernel or a whole CFW?
As I wrote in the frist post I tried already a lot of CFW and ALL had this issue, but the OFW ;(
What shell I flush to get this working, which is not OFW?
BIG THX for YOUR HELP
Touchwizz is the firmware that comes with the stock Samsung firmware .
Also in custom Samsung based roms .
Hello,
thx for the tip with TouchWiz vs aosp. At the moment I am running "DarkLord N5 Release Candidate 2.12" which can get find here: http://forum.xda-developers.com/galaxy-note-3/development/rom-darklord-s6-port-alpha-t3083087
This Rom is TouchWiz Based and guess what ....
Autorotation works.
However I do not understand what the problem realy is and would prefer to run cm13 insteat. I mean even samsung devices got a accellerator within which works also fine with AOSP software, showing numbers moving while turning the phone. In addition for example on the post http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375 it is said that this is explicite for note 3 including the model n9005. So ...
Can anybody point me to the problem or even better to the fix?
Is there any chance CM would fix this?
Regards
My Grandad's phone is a Chinese version of the Oneplus X E1001. My Grandad doesn't like the Chineese adds popping up on oxygenOS.. I have just updated it to the latest version today and removed all the apps that he doesn't use.
Is it possible to flash a ROM that doesn't involve oxyenOS ? Maybe a pure version of Android 5.1.1 would be good.
CM12 or CM13 would be the closest to stock android. Check it.
If you want message me your Skype, Telegram, etc. I can show you the best roms for your need and to walk you throw the process of flashing and unlocking bootloader.
Samtstic said:
My Grandad's phone is a Chinese version of the Oneplus X E1001. My Grandad doesn't like the Chineese adds popping up on oxygenOS.. I have just updated it to the latest version today and removed all the apps that he doesn't use.
Is it possible to flash a ROM that doesn't involve oxyenOS ? Maybe a pure version of Android 5.1.1 would be good.
Click to expand...
Click to collapse
I think if you flash stock ROM, it should remove the chinese ads. Download it from oneplus download section.
Another great option is flashing ROM. There are lots of good ROMs, try anyone.
Hello,
It's been almost a little over a year since I was last really into android customization. Since it's been so long it has become clear to me that my phone is outdated in many ways. I'm still running OxygenOS 2.2.1 with Android 5.1.1. I've been wanting to update up to Android N (7.x.x) for a long time now, but haven't seen any real stable roms or haven't really had the time to look for one. Now I've finally found my self with free time and ready upgrade my rom. I've just faced couple of problems, I can't really find what should I do when upgrading from 5.1.1 to 7.x.x since no-one is really doing that anymore. I remember reading sometime back that if you dont have the right firmwares you'll brick ur phone, and I wouldn't really want to go through that hassle at the moment. Is it still a thing or should it be just fine for me to flash a new rom just on top of this? (Ofc with clearing memory etc) Other question that is in my mind is that is there any critical bugs in Android N roms? It's bit unclear to me since there are such many roms that have their status as work in progress or beta etc, but some roms have status as stable. Are there any roms that I should clearly avoid? Im not new to this so I don't really need any deep info how to do everything etc, just a bit of a oversight on how things are going atm.
Thanks.
first of all is ur device rooted?? If yes then install the latest twrp recovery...then take a backup.. and flash any nougat rom which u like...If at all u would need Volte support then u l have to flash the 3.5.7 firmware..or else the 3.1.0 firmware works fine with most of the nougat roms..some nougat roms i would recommend are AICP, Resurrection Remix and AOSP extended .... In my suggestion u should probably first upgrade the Oxygen Os on ur device through official updates via OTA atleast upto the 3.5.6 firmware
there's no need to update until 3.5.6, unless you aren't going to plan staying with OOS [the only "stable" firmware which provides you VoLTE working, but it's still M-based and not N].
as @mhd athiq said, unlock your bootloader [just in case you still haven't done it before] then update your TWRP recovery to the latest version.
then flash the incrementals OTAs until OOS 3.1.x and you are good to go to flash any custom ROM which is N-based.
to avoid any mistake, please make a EFS backup via terminal [just to have a backup of your modems] and save the files to a safe location.
I don't have a specific ROM to suggest to you, but in my experience I have found the CAF/AOSP-based ones to be the ones with the best battery backup and less bugs then LOS-based ones.
I have used happily for a few months CypherOS version 3.5.1 [not the latest one, I find it quite unstable as the developers tried to implement OMS].
sidenote:
flashing N-based custom ROMs upon OOS 3.5.6 firmwares gives random reboots and unstable network in many cases/scenarios.
so don't update to that OOS version unless you have a mandatory VoLTE feature required [but you'll have to live with random reboots and poor network stability].
HI Guys I am a new user of MIUI (currently on stock 8.1.6.0). I have recently heard there is a nice update of the music app in latest global beta where a search function is activated. I want to update my music app only to that version, not touching the stock stable firmwire. Is it even possible? I am not willing to take risks of unlocking bootloader and switching to beta from stable etc. hence asking this.
P.S. If the latest music app with search option is available and can be installed, please mention it's version too. TIA
I have been trying to downgrade my tablet with a custom rom and stock rom.
Everything works perfectly, no issues on the rom, but when I reawake when my screen goes off, the screen just shows line for a second and closes, but the system is on.
These issues don't happen on any version newer than android 8.0.
When I try to downgrade, my main unmodified android version was 8.1.
Is there any fix to this?
diegopietro said:
I have been trying to downgrade my tablet with a custom rom and stock rom.
Everything works perfectly, no issues on the rom, but when I reawake when my screen goes off, the screen just shows line for a second and closes, but the system is on.
These issues don't happen on any version newer than android 8.0.
When I try to downgrade, my main unmodified android version was 8.1.
Is there any fix to this?
Click to expand...
Click to collapse
Can't imagine why you'd want to downgrade, must be some compelling reason... Lots of folks here using custom 9.0 (pie) roms that kick butt! Still, I don't have a proper answer-- I don't know if you can go back from 8.0 or not. Good luck, hope you get what your looking for.