Hello fellow M8 users, I would get a error message "unfortunately android system has stopped" every time I flash a custom kernel either on faux or elementalx. This is usually rom related but I am on rooted stock sense, s-off. I have a good backup copy of the rom before any changes but I would really like to get the benefits of a custom kernel without this message.
I am not running any overclock or undervolt. I think this is because I am running the ATT version of this phone but there are users who are running custom kernels with no issue. The only other thing I can think of is that I edited platform.xml to modify the WRITE_EXTERNAL_STORAGE permission so I can write to the ext sd card.
Anyone got any ideas for what I can do to get rid this message on startup?
Related
Hello,
I am using cm7, but this is a general question about replacing files in roms. I have been working on an issue that involves opening the zip file and then edit and replace certain files. I have seen a few posts in the past where it says to replace certain files in a rom, but everytime that I do I get an error after flashing. After flashing and boots to the main screen that asks you to touch the android, I get an error that says "Sorry, the process com.android.phone has stopped unexpectedly" and the only option is to click on Force Close, but it just keeps coming back. Something is definitely not right with replacing files in a rom, but Im not sure if there's even a correct way. Im using winrar as everyone has mentioned. I have tried using the Fix Permissions option in the Clockwork Recovery also, but no luck. Only option is to reflash. Anyone have any ideas? Does the whole rom need to be recompiled?
aa
aa
I have rooted my phone but not flashed the stock rooted ROM onto it yet. If I want to use wireless tethering on my phone do I need to have a custom kernel installed or am I able to use it with the stock system and kernel?
The reason I am asking this is because I honestly do not feel like installing the stock rooted ROM just yet as I am currently in the middle of configuring a lot of things on my launcher, lockscreen, etc. I would like to wait until those configurations are complete and saved onto my SD card before I flash a different ROM. That way I can flash, load saved settings, and go about my business.
Supposedly there is something within the kernel associated with a netfilter that the tethering apps use for the exploit. Does anyone have any insight into this?
Concordium said:
I have rooted my phone but not flashed the stock rooted ROM onto it yet. If I want to use wireless tethering on my phone do I need to have a custom kernel installed or am I able to use it with the stock system and kernel?
The reason I am asking this is because I honestly do not feel like installing the stock rooted ROM just yet as I am currently in the middle of configuring a lot of things on my launcher, lockscreen, etc. I would like to wait until those configurations are complete and saved onto my SD card before I flash a different ROM. That way I can flash, load saved settings, and go about my business.
Supposedly there is something within the kernel associated with a netfilter that the tethering apps use for the exploit. Does anyone have any insight into this?
Click to expand...
Click to collapse
You can do it fine with the stock kernel
Awesome!! Thanks!!
Sent from my V6 Supercharged Evo.
May i ask which wifi tethering app would work with the stock kernel?
thank you
https://play.google.com/store/apps/details?id=com.googlecode.android.wifi.tether
In settings change device profile to generic ics
Can anyone tell if there is a quick and easy fix to call lag - force incallui to memory or something in stock Sony JB ROM? I know in some 4.4 AOSP roms it is fixed, but do you know how can I interpret it in stock rom?
There's xposed module called 'App settings' that supposedly let's you lock certain apps into memory (along other features), but it doesn't seem to work. Any help appreciated
Would love a fix for the Xperia U to, but I'm afraid that the stock roms will never get a decent Phone. Devs have gone a long way with the sources, but they are only used in the next versions. Blame Sony for never fixing the Phone. It's broken since ICS. They never bothered to fix it.
After looking into several tricks to get the PhoneApp locked into the memory, I tried to install xposed framework with the module "app settings". In this module I've made com.sonyericsson.android.socialphonebook and com.android.phone resident. This means these two apps should be locked into the memory. The most recent calls I've received went smooth without any lagg. Testing further if this is a permanent solution for stock rom. I'm running devswifts v7 light stock jb.
old method:
creating local.prop in /data and adding the following lines
- sys.keep_app_1=com.android.phone
- sys.keep_app_2=com.sonyericsson.android.socialphonebook
did not work for me
When you have a custom kernel you can try to play with different governers and schedulers, this worked for me.
Hi all, not sure where I should post this so I am going here for a safe bet.
Basically, a lot of the time when I plug my earphones (MDR-NC31E) I get a pop up from the android system notifying me that DSP Manager has crashed. I am unsure of what is causing this problem. I have taken a logcat and the only thing I can see is there is apparently a 'missing' file, however it is there (with the permissions RW-------). It is also happening on my primary ROM (check my device setup for details).
The last thing I did before this problem came about was undervolt, I can't see that causing any problems however. I'll attach my logcat to the post too.
Device Setup:
D6503
AndroPlus Kernel (unsure of version)
MultiROM TWRP installed onto the FOTA Kernel partition
MultiROM installed
Existenz 4.5.0 as Primary ROM
Infected's CM12 as Secondary ROM
Root on both ROM's
SuperUserMod on my primary ROM
Deodexed on primary ROM
Xposed (no changes have been made with xposed for some time) on primary ROM.
@Envious_Data @niaboc79 Any ideas on the problem?
no ideas aside flash a stock rom and see if its a hardware response issue.
I'm running Thor 4.5.5.1 with Kingroot (Now Superuser)
I have elevated privileges but I can't move/copy or anything to /system
I can delete things without issue but I can't seem to get rid of that issue, and this isn't new. Even on 4.5.2 I started having issues. Did Amazon changed something?
Remounting /system as RW in ADB shell doesn't resolve the issue.
Any help is appreciated.
Luxen said:
I'm running Thor 4.5.5.1 with Kingroot (Now Superuser)
I have elevated privileges but I can't move/copy or anything to /system
I can delete things without issue but I can't seem to get rid of that issue, and this isn't new. Even on 4.5.2 I started having issues. Did Amazon changed something?
Remounting /system as RW in ADB shell doesn't resolve the issue.
Any help is appreciated.
Click to expand...
Click to collapse
To my knowledge nothing has changed regarding FireOS system partition allocation/utilization. Might give some consideration to installing SafeStrap v4 flashing a custom rom (Nexus Fire ROM or CM11) which will overwrite the contents of the System partition. You can also use Safestrap to perform a 'clean' install of FireOS 4.5.2 (here). Either option will trash your apps and data. Note a custom ROM also provides access to the Google Play Store without compromising the functionality of your device (possible exception if equipped with a mobile radio).
Thank you but I'm already aware I can run a custom ROM. I got the Google play working on stock without any issues (download, update , etc) but I'm fond of the carousel since I know how to change the icons and stuff and do not have much need for a custom ROM.
I'm running CM11 right now but I still can't seem to modify the file system. I'm definitely rooted and able to delete/ adb etc but the file system remains read only. I'll probably look into the clean install. Thank you.
Update: I didn't realize I had been running a custom rom with Fire OS (the carousel everything ) but it was still a custom rom. Apparently the file system would remain read-only unless you use a custom rom or edit the boot.img. I'm sticking with a custom rom
I am running CM11 now ; Modified the boolprop to allow 1080p in youtube and market helper to spoof tablet as a nexus 7 to get higher quality in Netflix. All is good, thanks for the help!
Luxen said:
Update: I didn't realize I had been running a custom rom with Fire OS (the carousel everything ) but it was still a custom rom. Apparently the file system would remain read-only unless you use a custom rom or edit the boot.img. I'm sticking with a custom rom
I am running CM11 now ; Modified the boolprop to allow 1080p in youtube and market helper to spoof tablet as a nexus 7 to get higher quality in Netflix. All is good, thanks for the help!
Click to expand...
Click to collapse
Glad you found a path that worked. There are components/files/partitions that can't be modified on a device with a locked bootloader. You should be able to gain unrestricted access to the system partition but I would not revisit if everything is functioning properly. Yes, every rom is a 'custom' build of vanilla Android although people tend to refer to stock (eg: FireOS) differently than roms developed/packaged by 3rd parties. Semantics.
Davey126 said:
Glad you found a path that worked. There are components/files/partitions that can't be modified on a device with a locked bootloader. You should be able to gain unrestricted access to the system partition but I would not revisit if everything is functioning properly. Yes, every rom is a 'custom' build of vanilla Android although people tend to refer to stock (eg: FireOS) differently than roms developed/packaged by 3rd parties. Semantics.
Click to expand...
Click to collapse
What I meant was it was a custom version of the Fire OS, despite being nearly stock? It had the google play and other things. I would like to point out that I'm met with no restrictions when trying to add/remove things from the system by using a custom rom. Sadly, from what I read and what you said, it seems to be a limit imposed by the locked Bootloader.