• 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

The status bar was the only thing i didn't really like, everything else is great.
Right now i have Holo Launcher set to hide status bar when i swipe up on the main menu but it only works on the main menu, when i open an app it reappears.
Is there a way to disable it even while running apps?

I don't see a way to have that setting persist while in another app, which I believe is because the effect only stays while the launcher is active, because it can't modify the statusbar itself to allow this to persist across apps.

Here's an update: the system settings icon is not nearly as blurry as it used to be, there is a charging animation now, pop-up dialog windows and the notifications panel were updated and should look better (by a lot), there is a new downloading animation, a new loading icon, and the charging icon on the lock screen is now the same icon that is used for the battery (two different icons was weird). My girlfriend even helped to pick out between a couple of options (like the panel where the carrier's name is listed on the notifications menu) when I couldn't decide, lol.

I've also found a way to update GPS locks, from XDA, and I should have a chance to implement that tonight. I'll also see if I can't add the default wallpaper in Sleipnir to the wallpaper chooser system app, as well as inverting the text on those other apps mentioned.
 
Another small update that may excite some people: Swype is going to be left in this time. Also, despite using Fix Permissions a few times, it seems as though I kept getting random reboots and super-lag until I factory reset for some reason. This could just be due to my use of LBE Security Master and Lucky Patcher, though.
 
I flashed your ROM, but had to flash back to CM9 because the play store would force close if I clicked on any app to download. I flashed it correctly, cleared the data multiple times, updated to the newest play store, all with no avail. Also, I was going through your init.d, and you have a tweak for dual core phones, at least the different tweaks where you set the SD card cache to 2048 KB, and a few of the same (or slighty changed) internet tweaks. Not trying to be too critical, just pointing a few things I saw out :)
 
I flashed your ROM, but had to flash back to CM9 because the play store would force close if I clicked on any app to download. I flashed it correctly, cleared the data multiple times, updated to the newest play store, all with no avail. Also, I was going through your init.d, and you have a tweak for dual core phones, at least the different tweaks where you set the SD card cache to 2048 KB, and a few of the same (or slighty changed) internet tweaks. Not trying to be too critical, just pointing a few things I saw out :)

Did you reboot at all? Slipinir needs a reboot before the play store works for whatever reason
 
I flashed your ROM, but had to flash back to CM9 because the play store would force close if I clicked on any app to download. I flashed it correctly, cleared the data multiple times, updated to the newest play store, all with no avail. Also, I was going through your init.d, and you have a tweak for dual core phones, at least the different tweaks where you set the SD card cache to 2048 KB, and a few of the same (or slighty changed) internet tweaks. Not trying to be too critical, just pointing a few things I saw out :)

Those are issues that haven't come up before, so it does sounds like it didn't flash correctly. I've been using the same build I posted and have had zero issues with it, so that's weird. Did you try using Fix Permissions after installing? Did you verify the MD5 as well? Also, the Play Store is already updated. So... yeah. That's weird. And unique, lol.

In any case, I'd be more than happy to look through the init.d scripts again - Hashtag modified most of them to work with this phone, and I'm not sure how the SD script is particular to dual-core phones either (works just fine for me). I'll have to do some searching for the dual-core script, thanks for clearing that up for me! And thanks for the feedback! :D

Did you reboot at all? Slipinir needs a reboot before the play store works for whatever reason

It shouldn't - I never had to for the new Play Store to work properly. Same case for the test build, no problems so far.
 
Those are issues that haven't come up before, so it does sounds like it didn't flash correctly. I've been using the same build I posted and have had zero issues with it, so that's weird. Did you try using Fix Permissions after installing? Did you verify the MD5 as well? Also, the Play Store is already updated. So... yeah. That's weird. And unique, lol.

In any case, I'd be more than happy to look through the init.d scripts again - Hashtag modified most of them to work with this phone, and I'm not sure how the SD script is particular to dual-core phones either (works just fine for me). But thanks for the feedback!



It shouldn't - I never had to for the new Play Store to work properly. Same case for the test build, no problems so far.

I've only seen that issue with a "dirty" flash. That's why I always wipe cache and dalvik at a minimum. Anyway a quick fix is to clear data and cache from market and google services framework, reboot and sign back in.
 
Great ROM all in all. Only bug for me is that if I am connected to my laptop via usb, I get a message when I toggle the status bar saying, "with one more failed security code, all the data..." I googled it and it seemed to pop up in the Aeneas Build thread but I couldn't find a fix. Any ideas?
 
How do I debug this? I'm fairly convinced that one of my apps is causing this to reboot, although it works on Ecksperia (which I keep going back to). I have just tried Hydra, restored my apps, rebooted and it reboots every few mins. I would like to find out what is causing the reboots. Any ideas?
 
If you are restoring apps using Titanium Backup that is probably the cause of your problem. Restoring apps this way has been known to cause random reboots. It's better to do and advanced data restore from a nandroid or to reinstall all your apps manually from the play store.
 
Am still at early stages, but it looks like (from alogcat and dmesg) it was my battery stats. I just erased them in CWM and life seems happier.
 
If you are restoring apps using Titanium Backup that is probably the cause of your problem. Restoring apps this way has been known to cause random reboots. It's better to do and advanced data restore from a nandroid or to reinstall all your apps manually from the play store.

I used to use MyBackupPro. Would this be a better idea, or would it create the same problems?
 
How do I debug this? I'm fairly convinced that one of my apps is causing this to reboot, although it works on Ecksperia (which I keep going back to). I have just tried Hydra, restored my apps, rebooted and it reboots every few mins. I would like to find out what is causing the reboots. Any ideas?

As Dark One said, try reinstalling your apps one by one - however, there is a known problem with a known fix as to restoring your apps after switching ROMs (don't do it normally, you have to do an advanced restore in CWM for things to work properly). The fix is also in the OP, in the installation steps.

I wasn't saying saying the SD card script had anything to do with the dual core script :P

Oh, lol. Well, good to know! But I agree with starkraving below, since what happened to you sounds like the following:

I've only seen that issue with a "dirty" flash. That's why I always wipe cache and dalvik at a minimum. Anyway a quick fix is to clear data and cache from market and google services framework, reboot and sign back in.

Yep.
 
I've never heard of battery stats causing problems like that, but it's good to know that wiping battery stats can be a fix for random reboots. I've never used MyBackupPro, nor have I heard anything for or against it's use. Your best bet would be to try it out and see if it works.
 
I was doing continual dmesg's in adb. The thing would reboot just after reading the battery stats. I guess they were corrupted, for some reason, which sleipinir cared about but ecksperia didn't. It's been stable for about an hour, which is 54 mins longer than last time.. Am using Google Play Music at the moment without problems.
 
I read that article beforehand, however, I think mine were actually corrupted. I never checked my battery usage so never realized. If your monitoring app is expecting something in a format it can parse, it may seg fault and take the frontend with it.
 
It's possible. I think I'll do for the SystemUI.apk and framework-res.apk what I did with the entire build last time - open them up, and add only what was modified to the stock Aeneas .apks.

EDIT: I'm rebuilding the entire theme from scratch with UOT, and I might be able to edit xml files in APKs, finally, too. The status bar is going to change, as well as the blank/solid-black category spacers on the notifications menu too. I'm going to try for a more-holo look.
Hey Artine, I need your expert advice,..I'm wanting to switch back to "Sleipnir" until the camera fix comes along for CM9,...What steps do I take exactly??
Thanks in advance sir!!!
 
Back
Top Bottom