DMedina559
Android Enthusiast
With the new version notification toggle worked fine with me.
Try wiping both caches and fix permissions in recovery if you all ready didn't try.
-
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
- Thread starter Artine
- Start date
-
- Tags
- lg optimus elite
With the new version notification toggle worked fine with me.
Try wiping both caches and fix permissions in recovery if you all ready didn't try.
elgecko
Android Enthusiast
Here's something I can not figure out.
I think I've placed .wmv and know I have .mp4 videos on my phone that work correctly. I may have placed them on the phone with the stock OS.
I have tried placing a few new videos in different formats on my phone, using Sleipnir v2.4.0.3. None of them will play, using the gallery movie player or quickpic.
Any idea what might be going on, or how to correct the issue?
This is my video I'm trying to get on my phone....
Codorus Creek Fun - YouTube
I think I've placed .wmv and know I have .mp4 videos on my phone that work correctly. I may have placed them on the phone with the stock OS.
I have tried placing a few new videos in different formats on my phone, using Sleipnir v2.4.0.3. None of them will play, using the gallery movie player or quickpic.
Any idea what might be going on, or how to correct the issue?
This is my video I'm trying to get on my phone....
Codorus Creek Fun - YouTube
LowEndGeek
Android Expert
Gallery only plays .m4v and .mp4 I think, try using something like mobo player or mx player
Mean Dean
Newbie
I did fix permissions... you might be right about clearing the caches... but I got Elixir instead and that's working (albeit less elegantly), so I don't want to mess with it if I don't have to. Thanks though
Very glad to see the Play Store bug is fixed (not that it was that bad, you could still update apps individually, but nevertheless), and everything looks smooth.
luiscomputech
Member
Time to man up . I was having problems with 2403 but I went back and read the instructions , followed them word for word and bam! , flawless . No more power button problems and no more random restarts to the boot screen .
Instructions . 1-Make nandroid backup if you want 2-format data only and once only 3-install Sleipnir 4-fix permissions and reboot . Don't wipe everything like I was doing .
Artine
Android Expert
In all honesty, because I can play .wmv and .mp4 both on my OE on Sleipnir v2.4.0.3, I'm tempted to say that it might have been a bad flash. I would try wiping the cache and dalvik-cache, and if that doesn't work then fixing permissions might help as well. If all else fails, I would try flashing again.
I apologize if this has already been posted--I did a search a few days ago but didn't find anything--but sometimes, my sound stops working. That is, I'll use the volume rocker to increase the volume, and I won't get a confirmation beep. Also, I won't get notification sounds or incoming call sounds. It goes away if I reboot or if I wait a few hours, but there doesn't seem to be rhyme or reason to it. I don't know what causes it or what fixes it. I've tried reflashing a few times but still have the same issue. Any ideas? Thanks!
Artine
Android Expert
In all honesty, I had to get my second OE replaced because this started happening and eventually progressed to the point where the volume keys stopped functioning completely. It sounds like a hardware issue to me, which can be verified if you do an Uber Factory Reset.
Hi, I registered to say thank you for this ROM. My Elite was horrible with battery life so over the weekend I decided to see what could be done. Started with Tagged, had some issues, but was then able to follow your great instructions and get Sleipnir working well.
I am running it almost completely as-provided with no changes and it looks great. The only thing I did was download "Color Wallpaper" for a 1-color screen background. I like everything all minimal, ROM and look-n-feel!
One (maybe silly) question: is there an easy way to change the light blue accent color? I have been fumbling around in Options and just can't see how to do it. Not that it isn't a nice color... I just like a very muted look.
Again, thank you for the great work!
I am running it almost completely as-provided with no changes and it looks great. The only thing I did was download "Color Wallpaper" for a 1-color screen background. I like everything all minimal, ROM and look-n-feel!
One (maybe silly) question: is there an easy way to change the light blue accent color? I have been fumbling around in Options and just can't see how to do it. Not that it isn't a nice color... I just like a very muted look.
Again, thank you for the great work!
luiscomputech
Member
I'm also getting random reboots after I thought all was well . Maybe it's the overclock . Perhaps lowering it would help to 1.5ghz and easy on the Lysol ;- )
luiscomputech
Member
I dropped down to 1.4ghz had 2 random reboots . I have a second problem which might not even be related with the rom . I cannot format Dalvik cache . Gives me an error . Can someone here verify this. I know the installation instructions do not mention to wipe it but maybe it stays loaded with leftover data . Error says : E:unknown volume for path [/sd-ex1] Dalvik cache wiped . I'm on CWM 5.0.2.8. Perhaps when the rom installs the housekeeping part fails without prompt but fails to wipe clean the Dalvik . Just throwing thoughts out there .
starkraving
Android Expert
I think what you're seeing is the recovery looking for the ext4 partition. Do you have an ext4 partition?
Some phones can partition, and format using a linux format, the SD Card and use some of it as extra storage for apps. This is called the sd-ext partition. Clockworkmod is assuming it's there and needs formatting (or at least finding) and not finding it. This is nothing to worry about.
luiscomputech
Member
No I do not . Just thought that could cause a problem . Brainstorming and throwing it out there .
LowEndGeek
Android Expert
That was me, and I went thru at least 20 attempts before I found one that ported even partially correctly.
It's still a big wip and I hope tip have an update soon
Artine
Android Expert
The following is just getting up to speed, as well as an update while I am at work:
Thanks!
This then leads one to wonder why, when encountering errors post-installation, that wiping the cache, dalvik-cache, fixing permissions and even wiping battery stats fixes a lot of problems. That wonderment is understandable, and the best theory I have for that is when a system app updates, such as the Play Store, and the new data interferes with the new dalvik-cache that was created post-install during the initial booting phase. This creates a conflict and forces the OE to reboot in attempt to correct the issue by re-building the dalvik-cache again. This, however, to my knowledge overwrites existing dalvik-cache data, which could also create problems. As such, going into recovery and wiping the dalvik-cache manually again, typically fixes the issue altogether because instead of old data being overwritten, the up-to-date data is being written as a fresh set.
And now for the update: my apologies for having not been posting or updating lately, and admittedly ROM work has been put on hold temporarily. This is because I have been busy with work, and due to a recent bid on shifts that took place I'm working a few days more than normal without downtime. I have also been taking care of my girlfriend this past week who has been sick the whole time as well, so my apologies for there not being any updates lately. Just wanted to keep everyone informed that development hasn't died
Note for themers: I was able to successfully add in the Holo progress bars and sliders, but aside from that right now the color scheme is what is largely changing, so feel free to keep on theming. I'll try to separate any changed files from the current theme, so that you would only need to update the theme files that are actually different from the current theme instead of having to start all over from scratch again.
Made my day. Just sayin'
Thanks! Playing around with the overclock Minimum and Maximum speeds should help. The only time I have had trouble waking up my phone was when the minimum frequency was set too low. The lowest setting, which I believe is 122MHz, tends to be way too low for this phone. Try 245 or the 3xx minimum frequency instead. Also, I would try changing the governor as well. smartassv2 generally is one of the best-performing for this phone.
see:
and
Also: I myself get that error on occasion, which I typically find occurs if you've wiped /data and then try wiping the dalvik-cache, since the dalvik-cache is actually in the /data partition. It should also be noted that in the Housekeeping phase of installation, though it may be unnecessary, the dalvik-cache is wiped three times. At the end of the installation, the dalvik-cache is wiped another three times. Six times in total, to ensure it is empty.
This then leads one to wonder why, when encountering errors post-installation, that wiping the cache, dalvik-cache, fixing permissions and even wiping battery stats fixes a lot of problems. That wonderment is understandable, and the best theory I have for that is when a system app updates, such as the Play Store, and the new data interferes with the new dalvik-cache that was created post-install during the initial booting phase. This creates a conflict and forces the OE to reboot in attempt to correct the issue by re-building the dalvik-cache again. This, however, to my knowledge overwrites existing dalvik-cache data, which could also create problems. As such, going into recovery and wiping the dalvik-cache manually again, typically fixes the issue altogether because instead of old data being overwritten, the up-to-date data is being written as a fresh set.
Good to throw it out there, nonetheless.
All of the credit for MIUI goes to Ken
Yep. That is known - when you are switching between ROMs, a wipe of /data is highly recommended because problems can, and do, arise if this initial step is not performed. As for switching between Android versions entirely, I wouldn't even dream of trying to keep your /data partition intact.
And now for the update: my apologies for having not been posting or updating lately, and admittedly ROM work has been put on hold temporarily. This is because I have been busy with work, and due to a recent bid on shifts that took place I'm working a few days more than normal without downtime. I have also been taking care of my girlfriend this past week who has been sick the whole time as well, so my apologies for there not being any updates lately. Just wanted to keep everyone informed that development hasn't died
Note for themers: I was able to successfully add in the Holo progress bars and sliders, but aside from that right now the color scheme is what is largely changing, so feel free to keep on theming. I'll try to separate any changed files from the current theme, so that you would only need to update the theme files that are actually different from the current theme instead of having to start all over from scratch again.
AndroidHaCks
Android Enthusiast
The best thing CM9 has over this (minus being CM9) is that the brightness can go much lower
Well, I just switched back to Harmonia. Since then, I haven't had the issue of the sound sometimes simply not working (that I was experiencing with Sleipnir). I think that means, then, that it's not a hardware issue, correct? Or I am wrong about that? Am I the only person who has had the issue where sounds in Sleipnir simply stop working? I think it was just system sounds. That is, I wouldn't get any notification sounds. I think I could still play music when this happened (not positive though; my memory is a little fuzzy).
I'd really like to solve this problem because I would prefer using Sleipnir, but it was a pretty big issue for me because I wouldn't hear, say, text messages, emails, or phone calls.