bradmi1984
Lurker
Thanks for the advice. I'll redownload the rom and do a md5 check. I used the cpu settings you recommend but i'll bump up the min clock setting up a notch in no frills cpu control.
-
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
LowEndGeek
Android Expert
Artine, What font did you use for the logo?
zuul
Member
i'm not bench testing this or anything but the 2.4.0.3 build appears to be running smoother and faster... also... it's smaller profile as i noticed a significant amount more space on the main partition after install... and i didn't delete anything and nothing's missing...
the white messaging is still a bit jarring but i'm living with it until i figure out wtf artine typed about installing the black...
meanwhile... i know a lot of you swear by juice defender... but i found it to be the source of a lot of my instability... once i dumped it a lot of my problems went away... i use battery doctor now and i like the 3 stage charging it offers. got a new battery recently and between that and the battery doctor i can go 24 hours without charging if i'm not surfing the web or streaming audio for half the day as i've been known to do. the handful of people i've convinced to switch seem to report similar results. the interface is a lot more user friendly for what that's worth. probably not as comprehensive but it does the job. but i'm not a power user so your result could vary widely.
meanwhile. speaking purely philosophically... is there such a thing as too much development? i think it's perfect. maybe you should finish your wish list... work out the bugs and bail. and then actually enjoy it before you get a new phone.
i worry you're obsessed. lol.
cheers.
the white messaging is still a bit jarring but i'm living with it until i figure out wtf artine typed about installing the black...
meanwhile... i know a lot of you swear by juice defender... but i found it to be the source of a lot of my instability... once i dumped it a lot of my problems went away... i use battery doctor now and i like the 3 stage charging it offers. got a new battery recently and between that and the battery doctor i can go 24 hours without charging if i'm not surfing the web or streaming audio for half the day as i've been known to do. the handful of people i've convinced to switch seem to report similar results. the interface is a lot more user friendly for what that's worth. probably not as comprehensive but it does the job. but i'm not a power user so your result could vary widely.
meanwhile. speaking purely philosophically... is there such a thing as too much development? i think it's perfect. maybe you should finish your wish list... work out the bugs and bail. and then actually enjoy it before you get a new phone.
i worry you're obsessed. lol.
cheers.
starkraving
Android Expert
Does our kernel for gb allow undervolting?
LowEndGeek
Android Expert
I.want to say no but don't quote me on that
bradmi1984
Lurker
Artine
Android Expert
How come you changed the look of the messaging? Just curious.....i liked the dark / yellow/ blue look.
No biggie
I think most of us did enjoy it
The black MMS.apk, however, has had many reports of MMS problems in the past, so I will copying over the theme from the black MMS.apk to the white (stock one) to see if that helps anything Celtic Garamond the 2nd
The logo will change in the near future as well, improving the way the text looks and adding the Android-green fire to the nostrils of the horse as well.Very true. The only possible exception to the problem caused by switching ROMs and restoring your data using Titanium Backup, is that you can go into TiB's Preferences and check "Migrate system data."
i'm not bench testing this or anything but the 2.4.0.3 build appears to be running smoother and faster... also... it's smaller profile as i noticed a significant amount more space on the main partition after install... and i didn't delete anything and nothing's missing...
the white messaging is still a bit jarring but i'm living with it until i figure out wtf artine typed about installing the black...
meanwhile... i know a lot of you swear by juice defender... but i found it to be the source of a lot of my instability... once i dumped it a lot of my problems went away... i use battery doctor now and i like the 3 stage charging it offers. got a new battery recently and between that and the battery doctor i can go 24 hours without charging if i'm not surfing the web or streaming audio for half the day as i've been known to do. the handful of people i've convinced to switch seem to report similar results. the interface is a lot more user friendly for what that's worth. probably not as comprehensive but it does the job. but i'm not a power user so your result could vary widely.
meanwhile. speaking purely philosophically... is there such a thing as too much development? i think it's perfect. maybe you should finish your wish list... work out the bugs and bail. and then actually enjoy it before you get a new phone.
i worry you're obsessed. lol.
cheers.
That's interesting, and good to know. I've heard good things about Battery Doctor as an alternative to JuiceDefender (oh, and for those of you wanting to get rid of the JuiceDefender status bar icon - you can do that in the settings, lol)
For the black MMS.apk, you'll want to do as follows:
- Download the black MMS.apk, found here.
- Copy it over to your OE if you haven't already done so, and verify the MD5Sum of the .apk.
- In a file explorer app of your choice that is root-actions capable (such as Root Explorer or Total Commander), copy the MMS.apk from its current location on your OE.
- Next, on that same file explorer, navigate to /system/app.
- In this directory, find the file explorer's Remount option, or look for text that is clickable that says R/W or R/O. You'll want to remount, or change, that mount type from R/O (read-only), to R/W (read-write).
- With /system/app remounted as RW, scroll down until you see MMS.apk and MMS.odex.
- Delete both of these files from that directory (/system/app).
- Paste the MMS.apk you copied earlier from the download, into this directory.
- Reboot into CWM and go to Advanced -> Wipe dalvik cache and Fix Permissions.
- Reboot normally through the main menu of CWM, and all should be well (and the Messaging app replaced).
However, the list at this point is not very long, and once it is complete I will be looking into trying to fix some out of the box bugs (bluetooth for example, if possible). Sleipnir does not have many improvements or updates left before it is finished, so no worries about being obsessed, lol Good question, but I don't believe so. Perhaps giantpune can confirm this?
It's no trouble at all, and I'm glad to hear that the issue is fixed
zuul
Member
success!I think most of us did enjoy it
For the black MMS.apk, you'll want to do as follows:
- Download the black MMS.apk, found here.
- Copy it over to your OE if you haven't already done so, and verify the MD5Sum of the .apk.
- In a file explorer app of your choice that is root-actions capable (such as Root Explorer or Total Commander), copy the MMS.apk from its current location on your OE.
- Next, on that same file explorer, navigate to /system/app.
- In this directory, find the file explorer's Remount option, or look for text that is clickable that says R/W or R/O. You'll want to remount, or change, that mount type from R/O (read-only), to R/W (read-write).
- With /system/app remounted as RW, scroll down until you see MMS.apk and MMS.odex.
- Delete both of these files from that directory (/system/app).
- Paste the MMS.apk you copied earlier from the download, into this directory.
- Reboot into CWM and go to Advanced -> Wipe dalvik cache and Fix Permissions.
- Reboot normally through the main menu of CWM, and all should be well (and the Messaging app replaced).
thanks for the step by step. i think in my mind i made it a lot harder than it really was... also... i use total commander with superuser access so it does all the mount/read/write stuff automatically...
as a result all i had to do was download the file... transfer the file from my laptop to my phone... delete the existing mms.apk and mms.odex and cut and paste the mms.apk you provided into system/app. with total commander it's a "ok" "cancel" command promt as far as the r/w permissions go. did the cache and fixed permissions in cwm and bam! done.i have also successfully sent and received mms in the form of jpg's. i never send video so if that's the source of the mms issue i would have not experienced it but with pictures of varying sizes i've never had a mms problem with any build of the rom.
i bet there's a common thread with the ppl who are having problems with mms. a shared app or something? is the problem isolated to the sprint build? (i use vm) it doesn't make sense that some phones are effected by it and others are not. the ones that are have to have a variable that exists outside the rom methinks.
but what do i know? pure speculation on my part based on no empirical evidence whatsoever. :smokingsomb:
quick ? do we need to use titanium backup if we use cwm? it seems all the functions are the same... and on a related topic... why is the date on the nandroid backups from cwm 1980? lol
thanks again for all your help!
Not to veer too far off topic, but I'm pretty sure that an app can't change the way the phone charges. That stuff is controlled at a far deeper level. All it's doing is showing a graphical representation of how the phone's already charging. I have no solid evidence, but much like memory boosters in windows, I'm calling shenanigans on battery doctor.
LowEndGeek
Android Expert
All we need is an android version of download more ram and our problems will be solved
luiscomputech
Member
I'm having trouble with this rom (v2403 and v2402) . Every time I press the power button it doesn't turn on unless I press it for a very long time . I'm also having trouble with randon reboots . It goes directly to Sleipnir boot screen and not to LG screen . I took the sd card (8 gb sandisk) out and the problems were solved . Can you check the sd card issue ? Seems like these 2 last roms have the same problem . Thanks Artine .
Artine
Android Expert
Glad to hear that worked for yousuccess!
thanks for the step by step. i think in my mind i made it a lot harder than it really was... also... i use total commander with superuser access so it does all the mount/read/write stuff automatically...
i have also successfully sent and received mms in the form of jpg's. i never send video so if that's the source of the mms issue i would have not experienced it but with pictures of varying sizes i've never had a mms problem with any build of the rom.
i bet there's a common thread with the ppl who are having problems with mms. a shared app or something? is the problem isolated to the sprint build? (i use vm) it doesn't make sense that some phones are effected by it and others are not. the ones that are have to have a variable that exists outside the rom methinks.
but what do i know? pure speculation on my part based on no empirical evidence whatsoever. :smokingsomb:
quick ? do we need to use titanium backup if we use cwm? it seems all the functions are the same... and on a related topic... why is the date on the nandroid backups from cwm 1980? lol
thanks again for all your help!
As for the MMS problem, it seems to be on both ends, not just Sprint or just Virgin Mobile. I believe the issues first cropped up with modified versions of the MMS.apk itself, and weren't posted about prior to this that wasn't explicitly a Sprint or VM account issue. Even though it doesn't make any sense why some phones would be affected or not, no two phones are exactly the same even if they are supposed to be. This is most evident in the fact that some OEs cannot handle 1.6GHz as a maximum frequency whereas others are able to perfectly fine, and how the White OE has numerous issues that the black OE does not have. That is good speculation though
Titanium Backup is perfect is you're not switching ROMs. If you are switching ROMs, then - as long as it is the same Android version - you should be safe to use CWM instead since TiB will fail in that circumstance. They both have their place.
As for the backups being dated to the 1980s by default (there is a fix for this in the CWM FAQ-Guide), this is because of the time.t table that is essentially the phone's clock. The starting date is back in the 1980s, as it is with all computers. However, when signal or an internet connection is given to the device, it syncs up to the current time temporarily (in other words, until it is powered off again). When you're in CWM and making a Nandroid backup, because no signal or internet connection is available it will make a backup in accordance with the time.t table, and as such the backups are dated 3 decades ago. The time fix for this tells CWM how many years/months/days/hours/seconds to turn the clock forward to create a more date-accurate timestamp on the backup.
Did you follow all of the first-time installation steps in the OP, word for word?
sinkist77
Member
I just had a very strange reboot. I was using the dolphin Wed browser and then it just rebooted to the sleipnir Boot screen. Then after it booted up a screen popped up saying "welcome to virgin mobile to get started please activate service. " well I didn't of course since my phone is activated. I cleared the message and tested everything and it all works fine. Just weird seeing that message. I just flashed this rom the other day, I came from CM9 I really missed my camera and really like this rom.
cfreeman90
Well-Known Member
Some times it's just the device itself, This release of "Sleipnir" is the only one that my device plays nice with....lol
judgebeanhead
Lurker
I dunno if this has been addressed already but when I press the volume button the screen turns back on. Its pretty easy to do this with it in my pocket. How do i make it so it only turns on with the power button?
Artine
Android Expert
I don't believe there is anything telling the phone to do that, but I can always verify this myself this evening. I can tell you though, that pressing the volume buttons on my OE while the screen is off does not turn it back on, so that's weird
But thanks for the heads up!and
Reply: Did the Play Store update again?
EDIT: I just remembered that I tried futily in the past to link dalvik-cache to /cache to utilize that free space. That was by way of init.d scripting. Since init.d scripting officially works now, this has again become possible, and I will be testing that out as well to see if it can/will be done.
Artine
Android Expert
IIRC it's the following line:
Code:
ro.config.hwfeature_wakeupkey=0That's how it appears for Sleipnir, so nothing should be waking the phone screen up in that case if you're using a hardware button. However, there is a setting for specific keys in the keymap that I will look into as well.
EDIT: Aside from the power button, of course.
Artine
Android Expert
That is correct - you do need to modify the kernel to support remapping a hard key to an app. I'm not sure how it applies to remapping a hard key to another hard key's action, though.
