Yeah, I'm wondering, how long our phone after use need to reboot or shutdown?
I never turn it after 2 and half days now.. there is no problem so far, but I want to prevent it to auto-reboot itself.. :silly:
you can found my screenshot of my cpu-spy in attachment:
Basically, you don't. There is no absolute reason to shut down your phone time to time or to reboot it. Smartphones are made so that it can be on all the time. Even so, the cache memory of the phone will fill up in time after many processes and it tends to start lagging a little, but when another program is on the program will overwrite those unused cache memory. Rebooting clear up those cache that's all.
KiD3991 said:
Basically, you don't. There is no absolute reason to shut down your phone time to time or to reboot it. Smartphones are made so that it can be on all the time. Even so, the cache memory of the phone will fill up in time after many processes and it tends to start lagging a little, but when another program is on the program will overwrite those unused cache memory. Rebooting clear up those cache that's all.
Click to expand...
Click to collapse
Actually, the problem (auto-reboot) is just happening with stock ROM -GB 2.3.6 DXLM3-
After I decided to root my phone and update my ROM with SlimBean 3.1.0 , then Arco's CM9 beta 4, and now I'm using Arco's CM9 RC 2, that problem never happened again!
Samsung, you. . .
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.
Hi , I'm using a custom rom (Revolution 9.3) and have a strange issue.
I normally turn my phone off on a night to put it on charge. When the phone is fully charged it now turns itself back on. Is this normal and is there a way to stop it doing it. I have not had this problem either with the official rom or with other phones i have had with custom roms installed.
The other issue is when i wake the phone in the morning it has the "people" app open.To get rid of this i have to press the home button which crashes Sence .Once Sence reloads all is fine all day .Apart from this im very impressed with the Rom so dont really want to change it.
These are minor issues and not the end of the world but i would like to know if there is a cure. I'm fairly experienced in flashing roms but have been unable to locate any reference to this on this site. I have had to post on here as i havent the 10 posts to allow me to put in the developers section for this ROM. Thanks
I think it's clockworkmod recovery that turns the phone on when nearly charged.
Martintxx said:
Hi , I'm using a custom rom (Revolution 9.3) and have a strange issue.
I normally turn my phone off on a night to put it on charge. When the phone is fully charged it now turns itself back on. Is this normal and is there a way to stop it doing it. I have not had this problem either with the official rom or with other phones i have had with custom roms installed.
The other issue is when i wake the phone in the morning it has the "people" app open.To get rid of this i have to press the home button which crashes Sence .Once Sence reloads all is fine all day .Apart from this im very impressed with the Rom so dont really want to change it.
These are minor issues and not the end of the world but i would like to know if there is a cure. I'm fairly experienced in flashing roms but have been unable to locate any reference to this on this site. I have had to post on here as i havent the 10 posts to allow me to put in the developers section for this ROM. Thanks
Click to expand...
Click to collapse
did u perform full wipe, erased cache and dalvik cache before flashing ROM
vivek_bhoj said:
did u perform full wipe, erased cache and dalvik cache before flashing ROM
Click to expand...
Click to collapse
Yes did full wipe with super wipe as per instructions .Also did a cache wipe and dalvik cache wipe before and after install.
Thanks for the info about clockwork - it hasn't had this effect on previous phones plus when i flashed back to stock rom but still with clockwork recovery it doesn't turn on when it reaches full charge. Presuming it is clockwork is there a way to stop it ?
Open to any more suggestions though.
It's one of those things that is bugging the hell out of me but i can live with it for the extra functionality the rom gives me and the better battery life.
Little worried that the extra on time it is giving me will have a long term effect on battery life and also dont want the phone going off with text at two in the morning.
I tried to enable it in developer options but after reboot it gets stuck on boot logo spinning that arrow. First time i waited half an hour now whole hour, nothing happens. I had to do factory reset and wipe all to boot up.
Anyone else tried this?
DjDexter5GHz said:
I tried to enable it in developer options but after reboot it gets stuck on boot logo spinning that arrow. First time i waited half an hour now whole hour, nothing happens. I had to do factory reset and wipe all to boot up.
Anyone else tried this?
Click to expand...
Click to collapse
Read the CM11 thread, it has been discussed there quite a few times, with multiple (possible) solutions posted. Use Search tool if necessary.
Someguyfromhell said:
Read the CM11 thread, it has been discussed there quite a few times, with multiple (possible) solutions posted. Use Search tool if necessary.
Click to expand...
Click to collapse
Eventually, i found out there were newer builds which work. In case anyone else has same problem. (Always dl newest one!)
Yes, the new build's partition have been updated so that ART can be activated. Nevertheless, the dev warn you that ART is still in alpha stage, that's why it was not natively implemented in KK as the original runtime. More and more apps are being updated to support ART but on our old device, it is recommended to stay on Dalvik for now.
The problem with ART is that it's still in a testing stage, even on new models that get 4.4 as legit release.
We don't have enough cache to run it smoothly enough, and of the few people that did turn it on, most of them either saw no difference in the devices performance or thought that it was so minimal that it could well have simply been a placebo.
We all want the latest garb but there is always a point at where a line is drawn...
Funnily enough, most people that ask about ART clearly show within their reply bodies that they don't know anything about Android except how to flash a rom :-s
Nathan
Well I am not dumb as I may look, but only drawback I found for now is that I am running low on internal memory. Phone battery lasts for 3+ days in comparison with dalvik where it held for about a day, and everything runs much smoothly.
Mike says its not possible right now we only can wait right now but arc dont have much memory in data thats problem
AOKP Rom with ART enabled
It is very well possible to use KitKat 4.4.2 on our phones. Even with ART-runtime enabled. I personally use AOKP (Android Open Kang Project)'s KitKat version, and I managed to get ART-runtime enabled and running very fast and smooth.
You can find the ROM here: http://forum.xda-developers.com/show....php?t=2624761
Of course you have to first install the kernel, which is given in the zip-file. Just unzip the kernel and Flashboot it to your device. Then go into CWM-recovery and go to Mounts and Storage and activate USB-mount. Locate the full AOKP-zip and place it on your SD-Card, as wel as the minimal Gapps for 4.4.2., found here : http://forum.xda-developers.com/show....php?t=2012857. Unmount the USB, and install the zip as usual through the menu for it. Then, after installing AOKP, install the minimal Gapps.
Reboot and let your device sit for a while, or play around with it a bit....
I proceeded with installing Mounts2SD from playstore, while before having prepared my class10 8 Gb sdcard into two partitions. One partition FAT32, size about 6Gb and one partition EXT2 size around 2 Gb. Move everything to SD-card through the menu of Mounts2sd, except Dalvik-cache. NEVER MOVE THIS!!! (Don't move dalvik-cache to SD...)
Reboot at least two times to let the script (Mounts2sd) settle in... After this I installed Pimp-my-Rom from playstore and activated the nav-bar and some other scripts to improve the experience. Also I odexed (after finishing all my modifications) the phone through this : http://forum.xda-developers.com/show....php?t=2527732
I then went to CWM-recovery through a reboot and made a full backup, which I advice you to do also, in case something goes horribly wrong.
Reboot to AOKP. As you can see, this ROM is awesome-fast beyond belief already. I had benchmarks in AnTuTu of around 6000, with NoFrills-CPU at 1401 Mhz. But, it can be faster if you choose to run ART-runtime instead of Dalvik. Be sure to remove all unwanted programs before switching to ART-runtime, because it'll take a lot of space in cache, and every program you don't need (system-programs that is) will reserve more space for ART.
Only and ONLY if your system is running smoothly on Dalvik, I advise you to go to your Phone-settings, (under Settings of course) and tap on 'Build-number' like 10 times. You will now become a developer. An extra menu will appear under Settings, where you can choose to run the ART-runtime library. Choose this and you will reboot.
Wait, wait and wait a long time for reboot. After initial booting everything has to be updated to ART-compiled apps. This will take a long time per app. Just wait and don't disturb your phone. If you get to the phone after booting, then you probably succeeded... You can check under the same settings-tab under Developer-options. If ART is selected, then you have it.
I strongly advice in case of mishaps regarding loss of network etc. to just reboot. Wait, wait and eventually you'll get there. Make a backup as soon as you have a stable working system under CWM-recovery.
I have been running stable ART under this AOKP-rom for about two weeks now and I'm really happy with it. Not only is the phone lightning-fast (6417 under AnTuTu, with CPU on my Arc LT15i on 1401 Mhz), but smooth as hell! Batterytime is amazing. This is as fast as it's gonna get! (I must have tried almost every ROM out there from stock 4.0.1 to 4.4.2...)
Hope you'll try and may it work for you too...!
(BTW my ultimate thanks to the guys from Open Kang Project!)
P.S. stock-browser is lagging... as usual under 4.4, but I use Dolphin and it is fast! Some toggles require reboot to function again. Some programs might fail you due to not being ready for ART. Facebook is a mess for instance, sometimes quitting, getting unresponsive etc. Otherwise I have encountered no problems whatsoever, albeit that memory is low of course and a minimality of (system-)programs should be installed for a good functionality of the phone.
It's really important for LT15i owners, to flash the stock software for LT18i (ARC S) onto your device, at least once, before installing any custom rom, because it removes the vendor-partition, which will give you an extra 40 Mb I'm told. Also partition your SDCARD before installing the AOKP-rom, as it will use the sdcard to store information on which will be deleted when you partition your card.
mhadjih said:
It is very well possible to use KitKat 4.4.2 on our phones.
Click to expand...
Click to collapse
can confirm, i have used art on xperia arc s with carbon rom nightly from 25.3.2014 with the included kernel, and micro gapps package from paranoid android. just flashed, activated art, rebooted and waited over 9000 hours. confirmed art was enabled in the developer options.
i think it was faster afterwards, i am not sure though. it seemed to be easy on the battery, too, but again, i didn't do any benchmarks or run a battery monitor so it could very well be that everything was in fact worse ^^
what i really noticed though: i had almost no internal memory for apps left. even after installing link2sd and linking all user apps, i still had not enough room to install all the apps i consider essential (10-20 apps maybe?).
i am now back to running on dalvik, the small internal memory of the arc s doesn't seem to lend itself to the art runtime very well.
yes, i know that there are gapps packages which are only 20 mB compared to the 80 mB of the pa-gapps package, still, even with a core gapps, those 60 mb don't mean very much with art running...
My phone is freezing and stutering all the time, it's most noticeable when i press the apps key (third on the right). I've tried several different ROMs (always wipping data,cache system) as it appeared to be a software problem but it starts right off as i'm at the initial configuration, keys are not even responding properly, when i press a key it takes about 3 to 4 seconds to respond
I'm also under the impression the phone is overheating, it's getting really hot on top back near the camera. Any suggestions of what i might try?
brunobliss said:
My phone is freezing and stutering all the time, it's most noticeable when i press the apps key (third on the right). I've tried several different ROMs (always wipping data,cache system) as it appeared to be a software problem but it starts right off as i'm at the initial configuration, keys are not even responding properly, when i press a key it takes about 3 to 4 seconds to respond
I'm also under the impression the phone is overheating, it's getting really hot on top back near the camera. Any suggestions of what i might try?
Click to expand...
Click to collapse
Are you using cyanogenmod or CM-based ROM by a chance? I've had horrible lags on it, especially on the latest nightlies. If that's the case, try something light and AOSP-based like slimkat.
I have tried slimkat, aokp, cm11 and they all seem to be getting slower everytime i flash a new rom I think this started to happen when i first attempted to do a full backup, the phone froze during the process because it was running out of memory. It was a pain to get it working again because it was sooooooooooooooo slowwwwwwwww.
Then i just booted to cwm did a full system, data, cache wipe and installed a new ROM, during the initial steps phone starts stutering, no matter what rom it is.
My guess is that there are still some files somewhere causing the problem.
First thing, Always keep >4Gb of free space.
Install/run Lagfix app.
Backup all important/personal files to PC, delete all files/folder on GN, copy over only ROM/gapps zips and flash a clean install(wipe data 3 times in row) and after ROM boot up copy back your files.
Oh, in that case it is most likely a free space issue as isajoo pointed out. I suggest using clean master to free up some space and get rid of some big files you don't need.
Hello to all, I am asking for some help and advices and I think this might be an interesting problem for some of you. I can't really explain it very well, but I will try to provide as much info as I can, so let's start. Since the past 20 days, I have tried Mokee 5.1.1 Release after trying Resssurection as my first Lollipop experience and I liked it, it was stable, fluid and different. I had some bugs and issues with Ressurection which I couldn't accept, so Mokee surprised me nicely. So I arranged it all up, everything that I need and didn't face any bug or even crash for about 10 days or more. So one day I was upgrading or something like that and wiped dalvik cache and cache with TWRP 2.8.7.0. After flashing, there was that app optimization process which is normal, and after that the phone wasn't booting. It would show my wallpaper and background material for a moment or 2-3 seconds max and then rebooting again and again. So I have restored the nandroid backup and it was fine. I guess if I can remember well that I was using that backup for about a few hours and it was fine and then I did something and it couldn't reboot again and my background was blinking. So I was messing with all of that and decided to try CM12.1 R15 and Ressurection 5.3.4 i think. After wiping everything except external SD of course and flashing it, everything was fine while setting it up and restoring my apps and data. And then after some time I wiped dalvik cache and cache, for some reason I had to do it, probably to flash xcelerate kernel and boot image before it and then again the phone couldn't reboot with background blinking, so it's the same problem. But now it's even worse, when I make a nandroid backup, I can't restore it, it won't reboot which means the problem is present all the time. So I tried this :
1. Wiping everything except external SD and flashing the same or a different Rom works, but the problem appears again sooner or later after setting the ROM and apps. The last thing I tried is to wipe dalvik and other catches and rebooting few times after flashing fresh ROM without setting it up or doing anything, and everything was fine, phone rebooted every time. I am confused because I am pretty sure that the problem appeared for the first time after wiping catches and rebooting and then just remained.
2. I have tried to repair system in TWRP, didn't work. Tried wiping only system partition and catches, didn't work. So it doesn't work by wiping system, but it works after a fresh flash of a ROM. Now for the few days I am using Mokee without xcelerate and other kernels, so I guess it's not because of a kernel, which I used before when it started for the first time. I have also tried to boot without SD card, didn't work. Every time the background blinks for a few times and then it reboots from a Mokee logo, and again, and again, always the same process.
Some apps that I am using which I gave a root acess : System Tuner ( Using it only for Freezing things that I don't need, deleting things that I really don't need, managing startups, backing only apps without data and clearing cache ). For appdata I use Helium and it works every time, great program. I am 99% sure that I am not doing anything wrong with system tuner, I know what to freeze and what to delete and what to startup. And after all of that, the problem doesn't appear and appears mostly if I remember correctly after wiping Dalvik and catches. Other apps with root acess are greenify, ES file explorer, xbooster which I rarely use and maybe 1 or 2 other apps which I always use. Before I used Chainfire's SuperSU and Stericsson's Busybox too and everything was working very well till the problem appeared for some reason. I don't use xposed framework on lollipop yet if it matters. And another thing, for wallpaper I use some picture with 1600x1200 resolution or similar, but it's bigger than 1270x720. Can that be a problem ?
So, I apologize for such a long and repetitive text hehe, I am just asking what do you think why is this happening ? Should I flash a fastboot rom with MiFlash, will that fix it ? will I be able after doing that to install Mokee or another 5.1.1 rom with all my apps and settings without facing this again ? TWRP is 2.8.7.0., is this version stable enough, is that a source of a problem ?
Whatever answer I get, thanks in advance and cheers !
Hi again, I have realized what caused all of this trouble, it's a bit unusual. After flashing the stock rom via MiFlash and doing everything else, it was clear. It was all because of Apex launcher, without a custom theme. It seems that Apex was compatible with some older version of Mokee and other LP roms, but those last few updates couldn't support it anymore. Too bad, I really liked Apex, it was very practical for me with a lot of options to use, while being lightweight. Now I need to find another launcher which can offer me similar experience till Apex is updated if ever, but I am a bit sceptic. The thread can be closed, thank you.