• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] Sleipnir v2.4.0.5 - 10/24/13 - VM & SPRINT

giantpune said:
Dear god no. Somewhere in that thread is a post from me (post #234), where I added in extra logging into the kernel for this very phone and proved that this entropy-seeding is BS. All it does is keep the cpu busy so it doesnt idle down to its lower settings as much, and is then less time for the thing to respond when you need it to. If you want the same effect, set your governor to "performance".
Click to expand...

Thanks for that info. I did give the app a try, and I noticed a minor improvement, but nothing that couldn't be associated with a placebo effect.

Further proof confirming giantpune's comments:
http://www.xda-developers.com/android/entropy-seed-generator-not-all-its-hacked-up-to-be/
 
Is there anyway to remove the original clock and use the Jellybean+ Clock? Just downloaded and don't like having to clock apps..
 
kaivorth said:
Is there anyway to remove the original clock and use the Jellybean+ Clock? Just downloaded and don't like having to clock apps..
Click to expand...
I picked it up too, very nice.

Use "app quarantine" to freeze the stock clock, then it won't be visable or run. If you have issues unfreeze it. If you run a while with no issues, use Ti backup to backup and uninstall the stock clock app.

I run my stock clock app frozen, with Clock JB+ as my daily user.
 
Its just personal perference. I may unistall it after a few more days, I might not (just got the JB clock yesterday). Deleting system apps doesn't free up any usable room, even if it did I dont need it.
 
sneaky_1 said:
Its just personal perference. I may unistall it after a few more days, I might not (just got the JB clock yesterday). Deleting system apps doesn't free up any usable room, even if it did I dont need it.
Click to expand...

Looks like Im in the same boat as you. LOVE this clock app tho. Everything in one place.
 
Just started getting a force close when trying to add or edit a contact.

android.process.acore has stopped unexpectedly
 
Welp, I'm back from the trip. Now time to respond to some stuff :)

sneaky_1 said:
I picked it up too, very nice.

Use "app quarantine" to freeze the stock clock, then it won't be visable or run. If you have issues unfreeze it. If you run a while with no issues, use Ti backup to backup and uninstall the stock clock app.

I run my stock clock app frozen, with Clock JB+ as my daily user.
Click to expand...

Titanium Backup freezes apps as well.

OptimusV123 said:
Just started getting a force close when trying to add or edit a contact.

android.process.acore has stopped unexpectedly
Click to expand...

Since I'm on the 2.3.9 test build, I must have fixed this somewhere along the way - right after seeing your post I just now created two contacts, one unsynced (phone only) and one synced (to gmail/Google), and both saved just fine.
 
Been running 2.3.8 for a few days.

My first flash I had an issue of the phone working after booting up. After a minute or 2 it would reboot.
Then I remembered I had move a app or 2 to the system. Formatted everything and used TiB to place all my apps back on the phone. :o

Running great Artine! Keep up the great work!
 
Hi everybody, this is my first post here. I've been lurking around these forums since I got my elite back in September. I first rooted when I got my phone with Hashtag's click-root method, flashed CWM as soon as it became available, and I've been using Sleipnir since it's been available. I've got precious little free time to dabble with my phone, but recently I was messing around with some init.d scripts and I discovered that the phone doesn't seem to be running any scripts at all.

The zipalign script included in Sleipnir should drop two files in /Data/ when it's run; zipalign.db and zipalign.log. This happens when I run sh /system/etc/install-recovery.sh in terminal emulator, but not when the phone boots. That's the most obvious way for me to know that int.d scripts aren't running on startup, but the fact is; from what I've seen none of the scripts seem be doing anything at all on startup. I even installed an app called "Universal Init.d Support 1.0" I found onthe XDA forums that basically uses the same install-recovery.sh trick and drops a few simple scripts into the init.d folder. one of the scripts writes a test.log file to /data/ to verify init.d but that file isn't created either.

I've tried wiping data, cache, and dalvik and flashing a completely clean install of Sleipnir 2.3.8 and had the same results. I've tried troubleshooting it myself to the best of my knowledge and ability but the only way I can get it working is to manually run the script myself. I managed to get my cheap Chinese tablet running init.d scripts with no problem, but the same efforts here do not produce the same effects. So I was just curious if this issue is only affecting me or if it's some greater issue with the Elite running init.d scripts. Either way some help would be appreciated.

Otherwise I love the ROM, especially the new options in the power menu, it makes booting into recovery that much easier.

Thanks

edit: also, when I ran install-recovery.sh in terminal it spit out quite a few errors while running the init.d scripts. I don't know if it'll be any help but I'll put my log up here so you can have a look:

[HIGH]$ export PATH=/data/local/bin:$PATH
$ su
# sh /system/etc/install-recovery.sh
mount: mounting none on /acct failed: Device or resource busy
mount: mounting none on /dev/cpuctl failed: Device or resource busy
/sys/block/stl*: No such file or directory
/sys/block/bml*: No such file or directory
/system/etc/init.d/01edt_tweaks: cannot create /sys/block/mmcblk0/queue/iosched/fifo_batch: directory nonexistent
/system/etc/init.d/01edt_tweaks: cannot create /sys/block/mmcblk1/queue/iosched/fifo_batch: directory nonexistent
sh: Can't open /system/bin/userinit.sh
run-parts: /system/etc/init.d/01edt_tweaks exited with code 2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
tune2fs 1.41.14 (22-Dec-2010)
tune2fs 1.41.14 (22-Dec-2010)
The needs_recovery flag is set. Please run e2fsck before clearing
the has_journal flag.
tune2fs 1.41.14 (22-Dec-2010)
tune2fs 1.41.14 (22-Dec-2010)
The needs_recovery flag is set. Please run e2fsck before clearing
the has_journal flag.
tune2fs 1.41.14 (22-Dec-2010)
tune2fs 1.41.14 (22-Dec-2010)
The needs_recovery flag is set. Please run e2fsck before clearing
the has_journal flag.
LG Optimus Elite data_writeback enabled
run-parts: can't execute '/system/etc/init.d/07tweaks': No such file or directory
Starting FV Automatic ZipAlign 01-07-2013 11:38:50
( Removing List of Zipaligned APKs to save space )
touch: no such tool
Automatic ZipAlign finished at 01-07-2013 11:38:51
run-parts: can't execute '/system/etc/init.d/09setrenice': No such file or directory
vm.drop_caches = 3
vm.drop_caches = 0
Caches are dropped!
run-parts: can't execute '/system/etc/init.d/14enable_touchscreen_1': No such file or directory
run-parts: can't execute '/system/etc/init.d/15cleanup_init_ram': No such file or directory

*********************************************
Optimizing and defragging your database files (*.db)
Ignore the 'database disk image is malformed' error
Ignore the 'no such collation sequence' error
*********************************************

Error: no such collation sequence: PHONEBOOK
Error: no such collation sequence: PHONEBOOK
Error: database disk image is malformed
Error: database disk image is malformed
rm failed for /data/local/tmp/*, No such file or directory
rm failed for /data/tmp/*, No such file or directory
rm failed for /data/system/usagestats/*, No such file or directory
rm failed for /data/system/appusagestats/*, No such file or directory
rm failed for /data/system/dropbox/*, No such file or directory
rm failed for /data/tombstones/*, No such file or directory
rm failed for /data/anr/*, No such file or directory
chmod: /data/system/userbehavior.db: No such file or directory
chmod: /data/anr/: No such file or directory
chmod: /data/system/appusagestats/: No such file or directory
chmod: /data/data/com.google.android.location/files/cache.cell: No such file or directory
chmod: /data/data/com.google.android.location/files/cache.wifi: No such file or directory
mount: mounting /dev/block/mmcblk0p13 on /data failed: Invalid argument
mount: mounting /dev/block/mmcblk0p6 on /cache failed: Invalid argument
/system/etc/init.d/17speedy_modified: cannot create /sys/block/mmcblk0/queue/iosched/fifo_batch: directory nonexistent
/system/etc/init.d/17speedy_modified: cannot create /sys/block/mmcblk1/queue/iosched/fifo_batch: directory nonexistent
net.ipv4.tcp_timestamps = 0
net.ipv4.tcp_tw_reuse = 1
net.ipv4.tcp_tw_recycle = 1
net.ipv4.tcp_sack = 1
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_keepalive_probes = 5
net.ipv4.tcp_keepalive_intvl = 156
net.ipv4.tcp_fin_timeout = 30
net.ipv4.tcp_rmem = 6144 87380 524288
net.ipv4.tcp_wmem = 6144 131072 524288
net.ipv4.tcp_ecn = 0
net.ipv4.tcp_max_tw_buckets = 360000
net.ipv4.tcp_synack_retries = 2
net.ipv4.icmp_echo_ignore_all = 1
sysctl: error: 'net.ipv6.icmp_echo_ignore_all' is an unknown key
net.core.wmem_max = 524288
net.core.rmem_max = 524288
net.core.rmem_default = 110592
net.core.wmem_default = 110592
net.ipv4.route.flush = 1
sysctl: error: 'kernel.sched_features' is an unknown key
run-parts: /system/etc/init.d/17speedy_modified exited with code 1
LST Debug: Done

run-parts: can't execute '/system/etc/init.d/98SDfix': No such file or directory
#[/HIGH]
 
miediev said:
Hi everybody, this is my first post here. I've been lurking around these forums since I got my elite back in September. I first rooted when I got my phone with Hashtag's click-root method, flashed CWM as soon as it became available, and I've been using Sleipnir since it's been available. I've got precious little free time to dabble with my phone, but recently I was messing around with some init.d scripts and I discovered that the phone doesn't seem to be running any scripts at all.

The zipalign script included in Sleipnir should drop two files in /Data/ when it's run; zipalign.db and zipalign.log. This happens when I run sh /system/etc/install-recovery.sh in terminal emulator, but not when the phone boots. That's the most obvious way for me to know that int.d scripts aren't running on startup, but the fact is; from what I've seen none of the scripts seem be doing anything at all on startup. I even installed an app called "Universal Init.d Support 1.0" I found onthe XDA forums that basically uses the same install-recovery.sh trick and drops a few simple scripts into the init.d folder. one of the scripts writes a test.log file to /data/ to verify init.d but that file isn't created either.

I've tried wiping data, cache, and dalvik and flashing a completely clean install of Sleipnir 2.3.8 and had the same results. I've tried troubleshooting it myself to the best of my knowledge and ability but the only way I can get it working is to manually run the script myself. I managed to get my cheap Chinese tablet running init.d scripts with no problem, but the same efforts here do not produce the same effects. So I was just curious if this issue is only affecting me or if it's some greater issue with the Elite running init.d scripts. Either way some help would be appreciated.

Otherwise I love the ROM, especially the new options in the power menu, it makes booting into recovery that much easier.

Thanks
Click to expand...

I appreciate the feedback. A few of the scripts are - or were - in fact running. Namely the SD Card Cache script is solid and works just fine (this can be verified by using an app to see the sd card speed cache). As for the rest, I'll see what I can do. However, init.d scripting does work and is functional.

This was actually perfect timing as I was going to break open the scripts and see what I could modify/update before v2.3.9 is out. Thanks again!
 
The init.rc should be running the install recovery file.

init.rc comes from the kernel and is created every time the phone boots.

You may want to check init.rc just to make sure it's being called. Although if it isn't being called from init.rc, there might be an issue with whatever version of the kernel Sleipnir is using.

I know on my device, the init.d scripts are running, but I'm not even using Sleipnir.
I'm using Tagged 1.0.5, and not even using the latest kernel.
I haven't yet tried the latest Sleipnir so I can't say one way or the other about whether or not the scripts are still working on it and all of the above is just speculation. You'll have to wait on Artine for the real answers.
 
I took a look at init.rc and it does call install-recovery.sh. It still doesn't seem to run at boot. I can run install recovery.sh from the terminal and it appears to run the init.d scripts. I checked for all the necessary files, folders and permissions. Everything looks good, but I can't get any scripts to run at boot.

I've got a full time+ job and a wife that gets bothered when I spend the few remaining hours of the day (what does the sun look like again?) troubleshooting my phone, so any troubleshooting tips would be much appreciated.
 
miediev said:
I took a look at init.rc and it does call install-recovery.sh. It still doesn't seem to run at boot. I can run install recovery.sh from the terminal and it appears to run the init.d scripts. I checked for all the necessary files, folders and permissions. Everything looks good, but I can't get any scripts to run at boot.

I've got a full time+ job and a wife that gets bothered when I spend the few remaining hours of the day (what does the sun look like again?) troubleshooting my phone, so any troubleshooting tips would be much appreciated.
Click to expand...

At least some of them are running as I can verify the SDCard init.d script is working just fine. That could just be due to how it was written, however. I'm testing a build with Hashtag's modified kernel, and more seems to be working in the way of init.d scripts and I do, for sure, have the search button -> camera button remap working as of right now. So, some init.d scripts do work, and some don't.
 
Also, development for v2.3.9 will be on a short pause as I root my new replacement phone - unrelated to development, my volume keys stopped working (could only reboot into ADB if a test build went wonky, and sound for calls and alarms, etc., was blaring and non-adjustable). It's now rooted and on the test build once again, just fine. Pilot03 is once again kind enough to lend his time to testing the Sprint version as I work on the Virgin Mobile version - it's coming, don't worry. It should be up definitely before the end of the week (since updates are pretty frequent), if not tomorrow (hopeful). As it stands, there may have been some app recompression issues ( being that they may have been recompressed in the first place) that were causing various things to blow up on the Sprint version. Also, I would rather release both builds simultaneously as it keeps things cleaner and easier to keep track of (for everyone, and myself).

As far as one of the main features remaining to implement - the search button remap to camera works perfect on the Virgin Mobile build (not so on Sprint). As usual, I will keep you all posted. There was also a minor revision to the CWM FAQ-Guide adding a section for BYORs, moving Aeneas there and adding Hydra there as well.

Yellowone said:
Didn't work :smokingsomb:
Click to expand...

I should clarify - you can follow one of two methods. The first, is to open the .zip of the ROM with WinRAR (default compression set to Normal), and navigate to /system/media. Next, drag the bootanimation.zip you have, from its location into the /system/media folder you've navigated to in WinRAR. Note that it's only /system/media, not /system/media/audio. Next, transfer the now-modified ROM .zip file to your phone, reboot into recovery and flash it. When the phone boots, the bootanimation should cover up the Sleipnir bootanimation.

Or:

Transfer the bootanimation.zip to your phone. Navigate to /system/media (not /system/media/audio) in a file explorer such as Total Commander (easiest) or Root Explorer, making sure that /system/media is remounted as R/W, not just R. Next, copy or move the bootanimation.zip into this directory. Reboot your phone, and the bootanimation should cover up the Sleipnir bootanimation.
 
You must log in or register to reply here.
Back
Top Bottom