Yesterday night I tried to flash AC!D sound mod using twrp..
first of all it took more than 10mins to flash that file!
after that it showed android is upgrading screen and it took lot of time.
after it got finished.. it showed "starting applications" and it stuck on that for the next 6-7 hrs!!
after 11 hrs my phone switched off and while charging the orange light was blinking..
Anyone else who has problem with acid audio?
hell_lock said:
Yesterday night I tried to flash AC!D sound mod using twrp..
first of all it took more than 10mins to flash that file!
after that it showed android is upgrading screen and it took lot of time.
after it got finished.. it showed "starting applications" and it stuck on that for the next 6-7 hrs!!
after 11 hrs my phone switched off and while charging the orange light was blinking..
Anyone else who has problem with acid audio?
Click to expand...
Click to collapse
If you have JB will not work system will crash. There is a lib that is in conflict. If I find it I will upload fixed version without it.
xpirt
Related
I was using nims MIUI GB RC2 before no problem no nothing.. After few days i tried CM9 beta 8... It was nice and smooth.. But i wanted to revert back to MIUI GB RC2 so i flashed again doing all wipe.. Now the problem started while applying a lockscreen(Yes it worked earlier) after applying the phone stuck. So i left it and went to cabin to my work.. Just saw the phone it was stuck at bootscreen.. Waited more than five min.. So removed the battery and tried no luck.. So reflashed the ROM.. Now one more problem "SOFT REBOOTS".. I installed play music if i keep some song to repeat for long time, and phone is locked it waits till the song gets over as soon as it gets over the phone gets back to boot screen surprisingly EDGE converts to 3G!!! Its doesnt ask for PIN also(So its a soft reboot)... ny solutions for this isssue? I have one doubt did i needed to do a format/system after cm9??
Thanks in advance,,
Last night my phone grew legs and ran all the way across the room while i was sleeping. When i woke up, after searching for my phone for 10 minutes, the vibration no longer works. I didnt know if it was a software or hardware problem. So, I flashed a backup from the day before (where vibration was working) and still no luck. So i flashed back to my current backup, when i rebooted, right before the bootanimation, it vibrates. Odd? It works when the phone is booting up, but not when the phone is booted. I'm running houstonn's Vanilla RootBox (4-20 v1) with houcha kernel. All help is appreciated!
Tyler44346 said:
Last night my phone grew legs and ran all the way across the room while i was sleeping. When i woke up, after searching for my phone for 10 minutes, the vibration no longer works. I didnt know if it was a software or hardware problem. So, I flashed a backup from the day before (where vibration was working) and still no luck. So i flashed back to my current backup, when i rebooted, right before the bootanimation, it vibrates. Odd? It works when the phone is booting up, but not when the phone is booted. I'm running houstonn's Vanilla RootBox (4-20 v1) with houcha kernel. All help is appreciated!
Click to expand...
Click to collapse
Thanks for everyones help...
I was able to fix this, and find the root of the problem (for me atleast). Everytime i click the Dark RootBox, vibration stops working. To fix, you must wipe the device completely, and reflash the rom.
Hello,I searched before but i couldn't find an answer.
I got a problem here,I installed yesterday a modified version of NeatRom 5.6(comming from infected 4.4.2 with gstavo kernel),by me to look like the S4 UI,I modified only framework-res.apk,SystemUI.apk and some system apps like sms,contacts etc.. No modification in init.d folder or build.prop,kernel etc. Yesterday I got into recovery and this were the steps I followed: 1. Flashed ROMNukeScript 2. The modified version of NeatRom aroma installer went great,I rebooted and BOOM the phone was stuck at Samsung Galaxy S2 logo for like 10 minutes,I was like OK maybe something went wrong,rebooted the phone and I couldn't enter recovery mode(VOL. UP + HOME BUTTON + POWER BUTTON),I tried several times,took the battery out ,waited for several minutes and tried again,nothing...(the phone was soooo hot during this attempts to enter the recovey), I went down and flashed with odin a frimware,rooted the phone again,and flashed again the same modified neatrom(this time with PhilZ rom wipe),this time it worked,the phone booted up,setup everything was OK. I gone ahead and installed V6 supercharger + the patched services.jar, and greenify.
Now the problem is,even if you don't belive me(BUT IS TRUE), this mornig at 11:30 I put the phone at charging and it finished charging at 8 PM,thats like 8 hours of charging...(with the charger not with the usb plugged into the computer,and the 2000 mAh battery from Samsung),and while charging the phone was very very hot(no apps in background ,because of greenify),not to talk about the battery life,its HORRIBLE.
With neatrom 5.5 I did the same thing(greenify + V6 supercharger at 100%,and the stock PhilZ kernel),modified(to look like the S4 UI) the exact way as the 5.6 version and worked like a charm,the phone finished charging in 3 and a half hours,no overheating,the battery was superb,5 hours of screen time with 1 and a half day of standby and I kept that rom(5.5 version) for like 2 months.
The question is what to do?? Do I have to go to a samsung center is a hardware problem,or software? I use the stock kernel that comes with the rom(XWMS2 5.15.9 PhilZ).
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Have you performed a factory reset? (It will delete all your data and apps)
rp-x1 said:
Have you performed a factory reset? (It will delete all your data and apps)
Click to expand...
Click to collapse
Yes, when the phone was new and the restarts were annoying. It fixed it for 1 day. The next day it was restarting again.
This would point to an app you've installed causing the issue. Factory reset again and install each app one by one until the restarts happen to find out which.
SteveTM said:
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Click to expand...
Click to collapse
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
cmstew said:
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
Click to expand...
Click to collapse
Will try it when I'll have time for it, thanks for the help!
Hello,
As we know Marshmallow update arrived , I had no problem recieving MM update to my E2353. i updated the phone using sony companion and it updated normal, nothing occured , i didn't made any mistakes..nothing.
So after update it turned off and boot up like normally it do,
First boot up took long time , like 20-30 mins and phone heated for some extent.
I did normal stuff such as connecting wifi etc, after that i restarted and it took around 20-40 mins to turn on again...
after turning on battery life is very poor..also every sensor of the phone are not working, no auto rotation, nothing.. now every time i turn it on it take 20-40 mins, battery is awful, it feel like its dieing after the MM update
couldnt find anyone with this problem with official update at all.
NOTE : i did rooted this an year ago without any problems and unrooted it after doing so without any problems.
i recieved MM original update.
current build no - 26.3.A.0.131
i've reinstalled (resetted) using sony update service which redownload the MM . it had no effect
Thank u very much !
Try flashing the marshmallow rom from XperiaFirm, it's a pretty easy process, look it up on google
DarkerJava said:
Try flashing the marshmallow rom from XperiaFirm, it's a pretty easy process, look it up on google
Click to expand...
Click to collapse
Did that, it's still the same... boot up takes long ass time still :/
factory reset
and if not working, try to shut down your phone for a minute and power on again