Related
I'm a big fan of the Hero slide-to-unlock function, but the only way it appears to get something like this on non-Hero builds is the Lock 2.00 app, which appears to have lots of problems since Android is not designed to have a user replaceable lock screen.
I would like to dive in to the framework and find where the (non-pattern, just push 'menu') lock screen is and see about replacing it. Things like a battery meter, emails, etc., that appear on Hero wouldn't be included since that requires tying in to all sorts of other things, as well as being a battery drain. In my mind ideally it would work as so:
1. Any key press wakes the screen
2. Slide down to unlock
The Android platform source is pretty intimidating when you don't know where to look though. Any devs want to point me to where in the tree the source for the 'Push Menu to unlock' screen is?
layout xml is in core/res/res/layout/keyguard_screen_lock.xml
some strings in core/res/res/values/strings.xml
That should get you started, I'm not sure where the rest of the code is, but this seems to be all Stericson modified.
[edit: I found the keyguard code for you. Check out various files in: android_frameworks_policies_base/phone/com/android/internal/policy/impl/ ]
Ah, OK, that helps, thanks. This will at least let me fix another pet-peeve: the giant carrier name and small date/time under it. (Because I really need to be reminded I'm on T-Mobile's service every time I unlock the phone. Just in case I miss the branding on the handset or the large text in the notification tray or something.)
pm'd you, in case you didn't notice my edit
Aha, there it is in LockScreen.java. As a test I changed it to allow a simple touch to unlock in addition to pressing the menu key. Now to figure out how to build this thing. (Even better, how to build cyanogens ROM, as I know that one works and works well.)
atomtom said:
Aha, there it is in LockScreen.java. As a test I changed it to allow a simple touch to unlock in addition to pressing the menu key. Now to figure out how to build this thing. (Even better, how to build cyanogens ROM, as I know that one works and works well.)
Click to expand...
Click to collapse
My bet would be to message Stericson or Cyanogen for some help compiling it and implementing it if you need it. To my knowledge, the Cyanogen roms still use some mods that Stericson made to the lockscreen.
I have searched the forums but cannot find a fix for this.
I am a noob when it comes to rooting/flashing but just rooted my hero and am running ddamage control v2.02, i think it is great but I have always hated the HTC lock screen, the flan one imo is much better.
I looked around and found that by entering
adb remount
adb shell
cd system/app
rm HtcLockScreen.apk
rm HtcLockScreen.odex
reboot
and rebooting the phone I get a messed up version of the flan style lock screen. It was supposed to remove the HTC lock screen and give a flan version. I am thinking that it may be because I did not type exit, but rather safely removed the hardware.
Anyway the problem is that the flan lock screen is the green lock circle that is supposed to slide to the right is in the bottom middle part of the screen, the only way to unlock it is to slide it up/the silent circle must be slid down to enable it to be silenced. Also the time is on the left side, and it is currently 12:15, however the time will show
12:1
5
because of the unusual version of the lock screen.
I looked around and found a fix that was supposed to re add the HTC lock screen, however the fix was for a 1.6 version and I cannot find the thread.
If anyone could help me either reinstall the original HTC Slider or preferably a properly working flan style I would appreciate it. I am thinking that because it is not an official ROM the developer did do a great job, but did not make it with the original flan style.
Here ya go.........................BTW there is no fix yet....
mjz147 said:
I have searched the forums but cannot find a fix for this.
I am a noob when it comes to rooting/flashing but just rooted my hero and am running ddamage control v2.02, i think it is great but I have always hated the HTC lock screen, the flan one imo is much better.
I looked around and found that by entering
adb remount
adb shell
cd system/app
rm HtcLockScreen.apk
rm HtcLockScreen.odex
reboot
and rebooting the phone I get a messed up version of the flan style lock screen. It was supposed to remove the HTC lock screen and give a flan version. I am thinking that it may be because I did not type exit, but rather safely removed the hardware.
Anyway the problem is that the flan lock screen is the green lock circle that is supposed to slide to the right is in the bottom middle part of the screen, the only way to unlock it is to slide it up/the silent circle must be slid down to enable it to be silenced. Also the time is on the left side, and it is currently 12:15, however the time will show
12:1
5
because of the unusual version of the lock screen.
I looked around and found a fix that was supposed to re add the HTC lock screen, however the fix was for a 1.6 version and I cannot find the thread.
If anyone could help me either reinstall the original HTC Slider or preferably a properly working flan style I would appreciate it. I am thinking that because it is not an official ROM the developer did do a great job, but did not make it with the original flan style.
Click to expand...
Click to collapse
u didnt do anything wrong when deleting the files. the flan screen is messed up on sprint release so far. No one has attempted or has failed to fix is so far
thanks alot, appreciate it. Obviously I would rather have the working HTC Lock screen than a broken flan one.
Did the same way. Could find no way to get the htclockscreen to install again. Pushed it, ran it, whatever...I ended up just re-flashing.
mjz147 said:
thanks alot, appreciate it. Obviously I would rather have the working HTC Lock screen than a broken flan one.
Click to expand...
Click to collapse
maybe one of the dev out there could look at it and fix it for us. maybe one day.
My HTC Sense lock screen is working again. Thanks for the link again.
I think a majority of Sense users love sense but don't like the lock screen, it is easier to open in the pocket and the flan style is smoother and more natural
mjz147 said:
My HTC Sense lock screen is working again. Thanks for the link again.
I think a majority of Sense users love sense but don't like the lock screen, it is easier to open in the pocket and the flan style is smoother and more natural
Click to expand...
Click to collapse
Yeah and flan looks better IMO. And being able to silence the phone easily is another plus.
Wasney said:
Did the same way. Could find no way to get the htclockscreen to install again. Pushed it, ran it, whatever...I ended up just re-flashing.
Click to expand...
Click to collapse
I may be a little late with this..... but i found when i removed the .apk and saved it for replacing later via estrongs I was able to simply copy and past back in /system/app and reboot. my original lockscreen was back with no problem. Although you must have the root options checked in options of estrongs file manager to be able to move the file.
Figured I post up what i found.
Bret
forgot to mention.....
I am sure others may know but you can also download lockbot from the market for free which has a few lockscreens, the pay or pro version has the flan lockscreen and have confirmed it works on DC2.1 treve mixture that I am running with no problems.... battery life good, VVM works, Location spot on, and no prl issues..(anymore)
anyway there my 2 cents And thanks to everyone out here I am starting to learn. All the devs keep it up!!!)Your Awesome
Looked at it a little bit
So, I really wanted to get the Flan Lockscreen working/appearing correctly so I started digging into the layout XMLs in framework-res.apk.
From what I can tell, it's forcing everything into the left 100 pixels of the screen causing things to wrap.
My first thought was to override the widths/heights from the -1 and -2 values to actual screen values (240x320). I updated most of the keyguard*.xml and screen*.xml files (hexedited) but the screen is still garbled. There may be a parent screen that is causing the restriction still though.
My second thought was there's an image file missing or is sized incorrectly. I pulled all the .pngs from DC1.0 (it was working there, correct?) framework-res.apk and placed them in the newer framework-res.apk. This changed the screen so that the slide buttons are at least visible (they weren't showing on DarchLegend at all) even if in the wrong place.
There might be something in the smali code that is preventing things working too... I still need to look into services.jar and policy.jar.
If anyone has any other ideas or insights, please let me know.
-Daryel
Quick question. How are you looking into the .xml files? I tried looking into this as well and got stuck at not being able to view the xmls.
daryelv said:
So, I really wanted to get the Flan Lockscreen working/appearing correctly so I started digging into the layout XMLs in framework-res.apk.
From what I can tell, it's forcing everything into the left 100 pixels of the screen causing things to wrap.
My first thought was to override the widths/heights from the -1 and -2 values to actual screen values (240x320). I updated most of the keyguard*.xml and screen*.xml files (hexedited) but the screen is still garbled. There may be a parent screen that is causing the restriction still though.
My second thought was there's an image file missing or is sized incorrectly. I pulled all the .pngs from DC1.0 (it was working there, correct?) framework-res.apk and placed them in the newer framework-res.apk. This changed the screen so that the slide buttons are at least visible (they weren't showing on DarchLegend at all) even if in the wrong place.
There might be something in the smali code that is preventing things working too... I still need to look into services.jar and policy.jar.
If anyone has any other ideas or insights, please let me know.
-Daryel
Click to expand...
Click to collapse
Good work. The heck with the Flan lockscreen, lets figure out how to remove the wallpaper to have a clear lockscreen. LOL
maxium01 said:
Quick question. How are you looking into the .xml files? I tried looking into this as well and got stuck at not being able to view the xmls.
Click to expand...
Click to collapse
There's a java utility called AXMLPrinter2 that will take the Android XML files and create a text file. Unfortunately it's only a one-way process, so editing of the XML files requires Hex-editing. That's how I edited the status_bar.xml file to change the font from white to black on the Taskbar.
-Daryel
daryelv said:
So, I really wanted to get the Flan Lockscreen working/appearing correctly so I started digging into the layout XMLs in framework-res.apk.
From what I can tell, it's forcing everything into the left 100 pixels of the screen causing things to wrap.
My first thought was to override the widths/heights from the -1 and -2 values to actual screen values (240x320). I updated most of the keyguard*.xml and screen*.xml files (hexedited) but the screen is still garbled. There may be a parent screen that is causing the restriction still though.
My second thought was there's an image file missing or is sized incorrectly. I pulled all the .pngs from DC1.0 (it was working there, correct?) framework-res.apk and placed them in the newer framework-res.apk. This changed the screen so that the slide buttons are at least visible (they weren't showing on DarchLegend at all) even if in the wrong place.
There might be something in the smali code that is preventing things working too... I still need to look into services.jar and policy.jar.
If anyone has any other ideas or insights, please let me know.
-Daryel
Click to expand...
Click to collapse
Wow, you have put in a lot for that.
I am running damage control v.2r2 and I believe that because it is not an official rom, damageless did not put in unneccesary android suff, the lockscreen being one of them. Their wouldnt be a point in installing or including in the rom a perfect standard messaging app, if HTC has their own.
However someone earlier in this thread gave me an .apk of the HTC lockscreen after installing it and rebooting it worked perfectly again.
I know this sounds stupid because I have no knowledge of developing at all but is their anyway to get an .apk of the 2.1 or even the 2.0 lock screen and just install it, it seems that it would just repair the broken version in damages rom, and all we would need to do is manually disable the HTC lock screen.
Any thoughts?
mjz147 said:
Wow, you have put in a lot for that.
I am running damage control v.2r2 and I believe that because it is not an official rom, damageless did not put in unneccesary android suff, the lockscreen being one of them. Their wouldnt be a point in installing or including in the rom a perfect standard messaging app, if HTC has their own.
However someone earlier in this thread gave me an .apk of the HTC lockscreen after installing it and rebooting it worked perfectly again.
I know this sounds stupid because I have no knowledge of developing at all but is their anyway to get an .apk of the 2.1 or even the 2.0 lock screen and just install it, it seems that it would just repair the broken version in damages rom, and all we would need to do is manually disable the HTC lock screen.
Any thoughts?
Click to expand...
Click to collapse
The Android lockscreen is part of the framework, separating it out would create other problems within the ROM. There isn't an "Android lockscreen" APK, the code is built into services.jar, framework.jar, policy.jar, and framework-res.apk.
I did have another thought, maybe there's something in the HTC code that is conflicting or overriding the stock settings. I'll take a look at some of the com.htc files tomorrow and see if anything jumps out at me.
-Daryel
daryelv said:
So, I really wanted to get the Flan Lockscreen working/appearing correctly so I started digging into the layout XMLs in framework-res.apk.
From what I can tell, it's forcing everything into the left 100 pixels of the screen causing things to wrap.
My first thought was to override the widths/heights from the -1 and -2 values to actual screen values (240x320). I updated most of the keyguard*.xml and screen*.xml files (hexedited) but the screen is still garbled. There may be a parent screen that is causing the restriction still though.
My second thought was there's an image file missing or is sized incorrectly. I pulled all the .pngs from DC1.0 (it was working there, correct?) framework-res.apk and placed them in the newer framework-res.apk. This changed the screen so that the slide buttons are at least visible (they weren't showing on DarchLegend at all) even if in the wrong place.
There might be something in the smali code that is preventing things working too... I still need to look into services.jar and policy.jar.
If anyone has any other ideas or insights, please let me know.
-Daryel
Click to expand...
Click to collapse
I luv to see someone trying to fix this.....still using the screwed up version still like it messed up more than anything else.... *** dcv1.0 it was working fine as well as some others** Thanks for keepin this going!
daryelv said:
The Android lockscreen is part of the framework, separating it out would create other problems within the ROM. There isn't an "Android lockscreen" APK, the code is built into services.jar, framework.jar, policy.jar, and framework-res.apk.
I did have another thought, maybe there's something in the HTC code that is conflicting or overriding the stock settings. I'll take a look at some of the com.htc files tomorrow and see if anything jumps out at me.
-Daryel
Click to expand...
Click to collapse
that would be great. That sounds about right perhaps their is something in damages rom that are overriding the stock setting?
I wonder though if someone running a stock rooted hero rom, could remove the hero lock screen and get the normal android "menu" lock
You know what? I bet it IS somewith with the HTC settings. Why else would they push out the ROM with all the HTC stuff working and not the Android lockscreen working? Because we're not supposed to be modifying the phone in the first place! So therefore HTC is adjusting the settings without regards to what Android stuff will be broken (because they assume we are going to only use Sense). Good thought.
if i remove it? when i unlock it will i get the animations? like on the normal htc losckreen or no?
EDIT 11/11/10: See Here for the official release thread.
EDIT 11/8/10: See Here for latest progress / update
Okay, wanted to give you guys a sneak peek of a port I just started working on this past weekend, for integrating the CyanogenMod Notification's panel power control widget into Sense based ROMs.
Short of the rotary lockscreen I originally ported back in the day, this has been one of the most intensive ports I've had to tackle, but it's getting close.
I've got the port to a point where it is mostly functionality (some buttons are not working yet, etc), but as you will see in the quick video demo, the formatting, etc, is all FUBAR'ed.
The formatting issues "should" be relatively easy to fix, my main focus to this point was to get things functional, then worry about pretty-ing it up, etc.
You can see in the video I currently have the widget set to the options for 'Lockscreen|Flashlight|GPS|Silent Mode', and you will see when I toggle the right 2, that the status bar updates accordingly to reflect the change in mode/status, based on the toggle. You can't really see, obviously, the flashlight come on, but it is working as well, in addition to the lockscreen on/off toggle.
Anyway, just a sneak peek. It may be that I never get it fully functional, and this ends up being nothing but a tease, but, I'm pretty persistent... .
Awesome. I just started working on this last week for Zen's ROM. It is a very daunting task. I got everything to show up, but wasn't able to get it functioning. Smali editing sucks. I've also been working on editing the recent apps icons in the notification menu from Zen's ROM (And Desire HD I think) and customizing them to be shortcuts that I use. The recent apps is useless and I'd love to have my shortcuts there instead.
I'll be watching this to see how you make out. I've slowed down on this since I'm waiting to get a new phone.
EDIT: GOOD LUCK!
signals23 said:
I got everything to show up, but wasn't able to get it functioning. Smali editing sucks.
I'll be watching this to see how you make out. I've slowed down on this since I'm waiting to get a new phone.
EDIT: GOOD LUCK!
Click to expand...
Click to collapse
Thanks. Yes, .smali editing sucks, especially this type, where you can't simply replace smali files and update resource ids, etc, as the two services.jar files are vastly different as it relates to the status bar, so it has been a complex merger of the two.
I'm close, but need a break! I'll probably re-visit this more over the coming weekend, when I have time to dig in. I have more hours invested in this from last weekend than I care to admit, and the wife wasn't very happy with me as a result...
wow js!!!! i really like this feature!!! hope you get it fully functional!!!
JsChiSurf said:
Thanks. Yes, .smali editing sucks, especially this type, where you can't simply replace smali files and update resource ids, etc, as the two services.jar files are vastly different as it relates to the status bar, so it has been a complex merger of the two.
I'm close, but need a break! I'll probably re-visit this more over the coming weekend, when I have time to dig in. I have more hours invested in this from last weekend than I care to admit, and the wife wasn't very happy with me as a result...
Click to expand...
Click to collapse
I've been there one too many times!
VERY cool. I would for sure use this. I'm almost surprised no one has thought of this...it's such a genius idea...for something so obvious haha
Greenfieldan said:
VERY cool. I would for sure use this. I'm almost surprised no one has thought of this...it's such a genius idea...for something so obvious haha
Click to expand...
Click to collapse
I'd have to imagine others have thought of it, now pulling it off of is a different story . It is not a simple task.
I didn't know this existed in CM until I was working on porting a mod I made for hex editing the lockscreen/notification window banner text (carrier) on Sense based ROMs over to CM, which forced me to load CM for testing, then, EUREKA!
Almost wish I hadn't come across it
JsChiSurf said:
I'd have to imagine others have thought of it, now pulling it off of is a different story . It is not a simple task.
I didn't know this existed in CM until I was working on porting a mod I made for hex editing the lockscreen/notification window banner text (carrier) on Sense based ROMs over to CM, which forced me to load CM for testing, then, EUREKA!
Almost wish I hadn't come across it
Click to expand...
Click to collapse
LMAO!!!!!
10chars
I'm so glad you got an EVO JsChiSurf. This looks very promising! I was just pouring over the code changes in your rotary lockscreen port the other day to see if I could get it working on my EVO. Long story short, I crapped a brick and put that thought to rest.
nukedukem said:
I'm so glad you got an EVO JsChiSurf. This looks very promising! I was just pouring over the code changes in your rotary lockscreen port the other day to see if I could get it working on my EVO. Long story short, I crapped a brick and put that thought to rest.
Click to expand...
Click to collapse
Thanks. Yes, the problem with the Rotary lock is, on 2.1, HTC left most of the remnants in place, in 2.2, not so much, so it is going to take more work to pull off.
I think it is possible, but I haven't had the time or motivation to dig in. If someone else doesn't get to it first, it's on my list, but it's more fun to work on new stuff, rather than something I've already done before, so I'm less motivated to do it again .
This will be sweet. I loved it on my Samsung
Sent from my PC36100 using Tapatalk
bblanski said:
This will be sweet. I loved it on my Samsung
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Thanks. Made some more head way this evening, but still much more to tackle...
This reminds me, I went digging into Sense to get the Mail widget to work in LauncherPro. Boy, what a PIA. I got it to show up and insert, but it wouldn't work. I figure there has to be a way to make it independent. I bet I'd have a lot of time to work on it if I got divorced...
i'm soo glad you got an evo bro. This will be sweet.
This looks amazing. Can't wait to see how it turns out.
Awesome man! Thanks for doing this, it is such a nice feature on the Galaxy S and CM 6.1. I hope it works out
Progress Report
Okay guys, getting real close on this port of the CM Power Control Widget for Sense ROMs. The video below will show you how far along I've come with this port. I've pretty much got most of the cosmetics corrected, but still have a few of the widgets to get functional, most notably bluetooh and wifi (don't think it will be an issue, just need to time to dig in).
This port/mod, upon release, requires changes to services.jar, and framework-res.apk, and as such, if you are using custom themes, edits, etc, you'll probably want to wait and see / request for your ROM dev or themer to take this as a base / starting point to integrate into their ROM or theme, as there is simply no way to do it the other way around. There are just too many edits involved to try and do this any other way in order to retain your previous mods / edits.
You'll see in the video that I actually moved the widget bar below the sprint banner / clear button area, rather than the default above. I think it looks better, curious what you guys think.
Also, while CM allows you to turn on/off widget options via the menu/settings area, I don't plan on going that far, and may either just fix it to 6 most popular, or provide a file on your phone that you can manually modify to specify the widgets (up to 6), you want to use.
Looking for opinions, based on the list below, if I were to fix it to 6, hard coded, what 6 in the list of available widgets would be preferred. Available widgets are:
Airplane mode
Auto rotate
Bluetooth
Brightness
Flashlight *
GPS *
Lockscreen *
Mobile Data
Network mode
Sleep
Screen Timeout
Sound (mute) *
Sync
Wifi
*Included in the video demo below.
Some of these I haven't test and am not exactly sure what they do, lol.
Also, curious what you guys think about the addition of toast notifications when a button is pressed (on screen text confirmation / message) and/or haptic feedback when pressed.
That's it for now. Again, getting close to a release soon.
WOW!
This is huge buddy
Awesome job.
My vote goes for:
Bluetooth
Flashlight
GPS
Wifi
Airplane
Brightness
Awesome work btw
I vote
Wifi
Mobile Network
Sound
Bluetooth
Auto Rotate
Lockscreen
Ok so I have decided to make my first attempt at making a Themed CM7 Rom. For my first attempt I just decided to kind of port my phones original Stock Froyo Rom onto CM7. I figured I would do this first just to teach myself how to do things and not so much worry about things like style or images as most can just be swapped over as I have decompiled all the APK’s from both Roms. I have gotten pretty good as far as doing simple things like swapping or editing images and rebuilding the APK’s but there are a few things specific to CM7 that I have not been able to figure out. At first I thought that if I just kept looking I would find answers before running through all the APK’s. Now I’m just about done with all the APK’s and everything is working and looking good but I have yet to figure out the following before putting a stamp on the project.
1, Was actually how to enable a bootsound but have just figured it out.
2, the build I used for the theme came with the Nexus Live Wallpaper as the default. I have replaced the default wallpaper in the Framework-res but can’t figure out how to set it as the actual default and not the nexus. I have read on a few forums that I should find it in a strings.xml and replace “live wallpaper” with @Null but not only can I not find the entry it just does not sound correct, but I really have no idea.
3, How to change the default lockscreen style? Looking to set the sliding tab style as the default.
4, How to disable the glowing over scroll effect as a default?
I know these are probably Rooky questions but I am by all means a complete Rooky. Otherwise I am proud I got this far, the thing looks just like the crapy old glichy Froyo Rom. Anytime I would have an idea in the past I would loose interest in the idea in trying to figure out how to apply the idea. This kind of has worked out as I’m just about done and the next time an idea hits me I can be all over it. Anyhow any advice on the above three would rock. I did not think they would be as difficult as they are but I have been unable to find anything that has worked so far.
So in my quest to make the phone more unique after rooting, I was EXTREMELY tired (after 4 days of ownership) tired of the stupid sprint sound and logo both before and after shutdown...
I found a thread where someone has the normal Samsung boot animation and right before I was about to install the 3 files into system\media. I took note of something.
We have multiple boot screens by default (or at least my Sprint phone does)
Ours are indicated by the SPR_bootfilename.
You can see the stock Samsung boot images.
Then I had BST, crypt, VMU, XAS...etc
So I first labeled all the SPR_bootsamsung images .bak hoping they would not then run, and in fact they did not. The stupid yellow spring flag logo went away and it just showed the fading sprint.
I then looked at the following and you can see where I was testing the file names and changed somethings.
VMU, is the Virgin Mobile boot screen.
BST has some super bright orange screen that says LTE.
Crypt has a really simple but cool green lock that has a circle spinning around it.
XAS didn't have anything and just defaulted to the Samsung boot.
I deleted the VMU and BST. Thinking I might run the crypt because it's super simple and clean looking.
My one question is that by default if I label anything SPR_ it will run that first, where should I look to change the script so that it would just run look at the normal Samsung file name instead of the SPR_.
Apologies if this is super old news but I thought it was interesting to say the least.
Video showing Crypt boot screen:
https://youtu.be/MnrywcfraaY
-Nigel
theyre packaged in the ROM itself and i havent been on a stock ROM in so long, i wouldnt have the foggiest whats included in one. Id have to unpack a zip and look. but if there are several in there, its probably sprint being too lazy to remove the others but virgin and boost are both MVNOs for sprint, so it kinda makes sense as the S5s available from all 3 carriers are all G900Ps, which is what you have
NewShockerGuy said:
So in my quest to make the phone more unique after rooting, I was EXTREMELY tired (after 4 days of ownership) tired of the stupid sprint sound and logo both before and after shutdown...
I found a thread where someone has the normal Samsung boot animation and right before I was about to install the 3 files into system\media. I took note of something.
We have multiple boot screens by default (or at least my Sprint phone does)
Ours are indicated by the SPR_bootfilename.
You can see the stock Samsung boot images.
Then I had BST, crypt, VMU, XAS...etc
So I first labeled all the SPR_bootsamsung images .bak hoping they would not then run, and in fact they did not. The stupid yellow spring flag logo went away and it just showed the fading sprint.
I then looked at the following and you can see where I was testing the file names and changed somethings.
VMU, is the Virgin Mobile boot screen.
BST has some super bright orange screen that says LTE.
Crypt has a really simple but cool green lock that has a circle spinning around it.
XAS didn't have anything and just defaulted to the Samsung boot.
I deleted the VMU and BST. Thinking I might run the crypt because it's super simple and clean looking.
My one question is that by default if I label anything SPR_ it will run that first, where should I look to change the script so that it would just run look at the normal Samsung file name instead of the SPR_.
Apologies if this is super old news but I thought it was interesting to say the least.
-Nigel
Click to expand...
Click to collapse
I have to thank you for the post! I renamed the SPR files with ".bak" and the boot is faster, dimmer, and quieter. Thank you!
How did you view the other animations?
tofudisan said:
I have to thank you for the post! I renamed the SPR files with ".bak" and the boot is faster, dimmer, and quieter. Thank you!
How did you view the other animations?
Click to expand...
Click to collapse
if you want some flavor choices, youre in luck! Many people make their own boot animations and some of them are pretty dang sweet!!
http://forum.xda-developers.com/galaxy-s5/themes-apps/bootanimations-samsung-galaxy-s5-bios-t2800820
http://forum.xda-developers.com/galaxy-s5/themes-apps/galaxy-s7-boot-animation-t3324518
http://forum.xda-developers.com/galaxy-s5/themes-apps/boot-animations-watchdogs-android-n-t3410400
heres a few links with some animations for ya. Ive seen tons more in the past. Sports teams themed, cars, bikes, babes, bands, android vs apple. The list goes on and on. Just takes some googleing and many of them are flashable in recovery
tofudisan said:
I have to thank you for the post! I renamed the SPR files with ".bak" and the boot is faster, dimmer, and quieter. Thank you!
How did you view the other animations?
Click to expand...
Click to collapse
No problem. I couldn't stand the stupid sprint logo because the phone would be dark, then a BRIGHT WHITE sprint yellow flag would show, which was blinding at night. I just did the above to disable them.
However to view the other ones simply add SPR_ to the front of them.
So for instance the crypt_bootsamsungloop.qmg should be renamed to SPR_bootsamsungloop.qmg.
Then just restart the phone and you will see the animation. If you like it, keep it, if not, just rename it back to the crypt*or whatever it was and you're done.
I deleted the factory SPR_ boot animations since I will never use those. I also deleted the Virgin mobile, XAS. They took up space so figured why need them.. Both the Virgin and the Sprint were something like 4mb each which is ridic.
I like the crypt though the more I look at it. Super simple, and doesn't tell you what the rom, or phone is which is cool. Very simple. I had someone with the same phone (who's had theirs for a couple years now) ask wait what is that? my phone doesn't do that..lol
-Nigel
Here is the video I made:
https://www.youtube.com/watch?v=MnrywcfraaY
-Nigel