• 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

Something wicked and white this way coming soon... :D

"P
 

Attachments

  • uploadfromtaptalk1368643356056.jpg
    uploadfromtaptalk1368643356056.jpg
    29.6 KB · Views: 131
  • uploadfromtaptalk1368643365592.jpg
    uploadfromtaptalk1368643365592.jpg
    31.1 KB · Views: 139
Are the sounds your setting located on your internal or external sdcard? I get them to stick better when I actually put them in /system/media/audio/ then the corresponding folder i want it to be either a notification sound or ringtone. :)

I'm having a problem still with my Ringtones/ alarms /notifications I somehow erased them and when I downloaded the. zips put them in /system/media/audio and respective folders to no avail any wisdom that can be shared? Does the zip have to be opened manually somehow? Also I deleted the data in the system app Android System (I think that's the name of it) it looks like a pully and fan belt HELP!!! Thank u:banghead:
 
I'm pretty sure that it has to be unzipped for the ringtones to be seen by the phone. Most root explorers have zip capabilities built in, otherwise there are apps available on the play store that can open them up for you.
 
I'm having a problem still with my Ringtones/ alarms /notifications I somehow erased them and when I downloaded the. zips put them in /system/media/audio and respective folders to no avail any wisdom that can be shared? Does the zip have to be opened manually somehow? Also I deleted the data in the system app Android System (I think that's the name of it) it looks like a pully and fan belt HELP!!! Thank u:banghead:

The .zips are flashable - you're supposed to flash them in CWM. There are non-flashable regular .zips available as well if you would prefer. :)
 
The .zips are flashable - you're supposed to flash them in CWM. There are non-flashable regular .zips available as well if you would prefer. :)

Thank u in not sure how to flash them my friend and on another note my nandroid bkup hasn't been working I have to use a previous one, like I mentioned the system app Android System has no data in it goes can I restore that?
 
Thank u in not sure how to flash them my friend and on another note my nandroid bkup hasn't been working I have to use a previous one, like I mentioned the system app Android System has no data in it goes can I restore that?

Aside from using Titanium Backup or restoring from a Nandroid backup, I'm fairly certain there isn't a way to get System data back. Since the .zips are flashable for the Alarms/Notifications/Ringtones, you flash, or install, them the same way you would a ROM, in CWM. :) What seems to be the problem with the Nandroid backup?
 
Here's another teaser, since I am able to edit .apks now, I went ahead and added the default_wallpaper for Sleipnir to the LGWallpaperPicker.apk. This means that the default wallpaper for Sleipnir is now selectable, for those of you that wanted to return to using it after switching to another wallpaper. I'm also thinking about adding in the wallpapers from Tagged, ICS Elite, and Aeneas as well - if that's alright, of course.

screenshot-1368682913966.png

EDIT: Arrgh, another double post :p
 
Here's another teaser, since I am able to edit .apks now, I went ahead and added the default_wallpaper for Sleipnir to the LGWallpaperPicker.apk. This means that the default wallpaper for Sleipnir is now selectable, for those of you that wanted to return to using it after switching to another wallpaper. I'm also thinking about adding in the wallpapers from Tagged, ICS Elite, and Aeneas as well - if that's alright, of course.

screenshot-1368682913966.png

EDIT: Arrgh, another double post :p

I know this is random, but can I format /mpt? What's in that directory?
 
All good to know, but if everything is being followed verbatim, and the first-time steps don't fix the issue, then my guess is that one of the following two things is going on:

1. The problems are device-specific. While it may not help, Uber Factory Resetting might solve the problems.
2. The /data partition became corrupted in some fashion. Factory reset or wiping /data should fix that. If not, an Uber Factory Reset might help.

And I'm terribly sorry that all of this stuff is going on with your device, man.

Okay. Wiping /data seemed to solve the issue. My notification sounds stay set after a reboot and a computer mount/unmount.

The wonky touch sensor, not so much. It's less prevalent now, but I still experience it sometimes.

also, my phone seems to be a lot more responsive now. Before, it was very slow but seems to be acting faster, at least for now.
 
I'm working on getting kernel-level init.d support now, taking a break from theming. I'm using giantpune's (kudos to him, again!) latest VM kernel for this. On the first test, the device booted a few seconds into the legacy bootanimation, then promptly rebooted, and booted into the GUI successfully but in safe mode. On a reboot, there's no longer safe mode, but init.d support appeared to not be working properly.

UPDATE: I do believe we finally have kernel-level init.d support now. A few modifications to the updater-script and getting rid of all but two init.d scripts yielded the following result:

screenshot-1368733790525.png
screenshot-1368733797067.png

It looks like init.d is working fine, and one or a few of the scripts made Android a little cross with me in the initial test. I'll be weeding down which script(s) is/are the culprit, but up to now I was never able to get the init.d testing script to generate that file before with the ad-hoc support. Looks like we have kernel-level init.d support now :D

Also, while I would love to upload the further-modified kernel to be available for download, I want to make sure everything (like overclocking, for example, and init.d scripts) functions correctly, and run some stability tests. Hopes are high though, so fingers crossed! :)

EDIT: Here is the link to the further-modified boot.img with init.d support. After several reboots, stability and CPU stress tests, and gaming on it for a while, I've had zero issues with the boot.img itself (still weeding out the problem-causing init.d scripts). Anyone up for some testing? :)

MD5: cbb610780d3de104610aaf3a5d2b7c76
 
Just a suggestion - even though I don't own the Elite anymore.

Make a CM version of Sleip. It would be really cool and you could include ICS stuff.
 
Aside from using Titanium Backup or restoring from a Nandroid backup, I'm fairly certain there isn't a way to get System data back. Since the .zips are flashable for the Alarms/Notifications/Ringtones, you flash, or install, them the same way you would a ROM, in CWM. :) What seems to be the problem with the Nandroid backup?

I make the back up in CWM all looks gud when it comes time to restore it says error and won't allow me to restore the new back up only an older one. Also my Android System is blank and I think at one point a Qualcom system app was deleted of its data too
 
I make the back up in CWM all looks gud when it comes time to restore it says error and won't allow me to restore the new back up only an older one. Also my Android System is blank and I think at one point a Qualcom system app was deleted of its data too

That's definitely weird, and sounds like there's a rogue app on the loose. As for CWM, I would reinstall it to see if that fixes the problem as long as it doesn't say there is an MD5 Mistmatch.

EDIT: It appears as though one of the scripts is creating a conflict with mass storage, forcing a soft-reboot whenever you mount/remount the internal and external SD cards for mass storage. That's an improvement, though, over booting into the GUI and having a forced soft-reboot not five seconds afterward :D

Anyway, there should be a new build up tonight when I get back home from work, after the init.d script weeding-out process has finished. The new build won't have the work-in-progress theme, however, because I would rather release that when it's finished as opposed to half done.


UPDATE: Kernel-level init.d official support is a go. Enjoy the new build everyone, and check the changelog for an extra bonus :)
 
I'm not able to access the DevHost link for the Virgin Mobile version,could u please give us an alternate download link? I also wanted to mention that with this ROM I frequently run across websites or links from within apps that I cannot access & I was wondering if that's because of the hosts files with this ROM that prevent ads?
 
I like the new build. It actually odexes post install! But not a big fan of the white messaging.. can I paste the old mms.apk in /system/app?
 
I like the new build. It actually odexes post install! But not a big fan of the white messaging.. can I paste the old mms.apk in /system/app?

Certainly, but the old one does have MMS issues. The goal is to be more bug free on flash, not more buggy, lol :p If you're going about switching the .apks, you'll want to remove the .odex file for the MMS.apk that was flashed in originally or you're gonna have a bad time.

Yeah link is no good for me

So... the link works now? :p

Also, note to self: do not post builds on 5 hours of sleep. Bad things happen.

I'm not able to access the DevHost link for the Virgin Mobile version,could u please give us an alternate download link? I also wanted to mention that with this ROM I frequently run across websites or links from within apps that I cannot access & I was wondering if that's because of the hosts files with this ROM that prevent ads?

It shouldn't cause any issues with actual links, only ads. Advertisements (most of them, anyway) should not load, but everything else should work normally. It's always possible, though, could you give me a list of websites that do not work? Everything I visit works fine for me :p
 
Installed the new build. So far so good. Completed all the steps and everything is working fine. The best thing I noticed was Play working right off the bat.

Sounds all good. Right? Well I can't have that happening. I don't want you dancing around all happy because Play was working. MMS still not flying. I can't wait for the new build.

Good work.
 
1 awesome logo

2. I'll try it soon

3. Congrats artine

4. Will you update hydra

5. You should update the screenshots in the op

6. AWESOME LOGO
 
Back
Top Bottom