Doesn't your phone get sluggish after 2 to 3 days? Mine does.... Nothing runs properly because of memory leak
No, it runs fine. Maybe a tiny bit less smooth, but everything runs fine.
Doesn't your phone get sluggish after 2 to 3 days? Mine does.... Nothing runs properly because of memory leak
Phone rebooted into recovery on its own. Following settings:
OC 1140
Governor Save Battery
Smooth UI
Lock Min Scaling Frequency
Scheduler Simple I/O
DeepIdle
Bigmem
Auto Brightness Dark
Vibrator Minimum
SD Card Read Ahead 256Kb-64Kb
Have now changed the governor to OnDemand, see how it goes. Anyway its a great kernel Stratosk, using it with Slim ICS 4.01.
i use the same settings and rom and i have same problem cant oc.
My endurance test ended after ~140 hours. Phone rebooted into recovery - I guess from bootloop detection. Too bad that I lost the last_kmsg file (my stupidity!).
I was trying to listen to the radio today (with Spirit FM), and I got this weird message "No FM accessible". I enabled the "FM Radio" script through the Semaphore app, but no luck.
It has been a while since I listened to the radio, but I'm pretty sure it did work on older Semaphore versions.
I researched a bit and I found out it is a known issue with some kernels (including Semaphore I suppose), and it has been reported many times before, both on this thread, and on mikereidis' thread.
I then tried Devil3 0.79 and the radio worked just fine
Any ideas on that?
By the way I'm using AOKP build 40, Semaphore 1.2.5, and Spirit FM Unlocked vJun15.
My test ends after 100H but because I must flash a new b40 AOKP...
But yesterday I found some strange fail. I was trying to send 70MB HD video to Google Disk but phone start to ending all gapps and notificate that there is no another free space in phone internal memory... maebe its fail of GD app or b40 build... next time I post screen of my endurance test ;-)
With youtube sharing there wasnt any problem later...
Sent from my GT-I9000 using XDA
stratosk This is wierd . But it doesn't seem kernel's issue to me.
I have never understood why Nightly-flasher are so much waiting for RC's. It's a good sign things are progressing, but I don't think it is that "special".
Boot splash can only be changed before compiling the kernel, so to change your own boot splash you have to compile your own kernel.
So can I normaly wipe them in cwm? Thx - i never do that...
(Sorry for spaming)
Sent from my GT-I9000 using XDA
I won't do this if I were you,you'll probably ended forced to wipe all data (factory reset) after to regain stability.Better search on the datafix side and for the moment just check what's happening in your datadata folder/partition.So can I normaly wipe them in cwm? Thx - i never do that...
(Sorry for spaming)
Sent from my GT-I9000 using XDA
Phone rebooted into recovery on its own. Following settings:
OC 1140
Governor Save Battery
Smooth UI
Lock Min Scaling Frequency
Scheduler Simple I/O
DeepIdle
Bigmem
Auto Brightness Dark
Vibrator Minimum
SD Card Read Ahead 256Kb-64Kb
Have now changed the governor to OnDemand, see how it goes. Anyway its a great kernel Stratosk, using it with Slim ICS 4.01.
No, it runs fine. Maybe a tiny bit less smooth, but everything runs fine.
I had the same settings except didle and also rebooted into recovery.
Hrm how do you manage that? Checking my RAM after say 2 days of uptime, I have little apps open in the background, and RAM is at roughly 330/390MB (give or take). Try to open Facebook, automatically closes. Try to open browser, automatically closes.
#!/system/xbin/busybox sh
while true; do
cat /sys/devices/virtual/misc/deepidle/dflags
sleep 1
done
mkdir /tmp/semaphore
cd /tmp/semaphore
git clone https://github.com/stratosk/samsung-kernel-aries
git clone https://github.com/stratosk/ics-ramdisk
cp config_sema .config
make CROSS_COMPILE=/kernels/semaphore_cap/android/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- ARCH=arm menuconfig
./sbuild.sh
I'm sorry for your issues.
And I have no more desire to build new versions. At least for now.