Below you'll find two new boot animation clips I've made (it's the android on a skateboard jumping through a hoop of fire) to replace boot1.gif and boot2.gif in the /system/media/bootscreen folder on the filesystem. Can anyone tell me why they don't display properly at boot time?
files:
boot1.gif : http: //picasaweb.google.com/lh/photo/5EPOtJXhVOw1_CIeg6h9Vg?authkey=Gv1sRgCOip8ui3kt7JtQE&feat=directlink
boot2.gif : http: //picasaweb.google.com/lh/photo/BuL7-g9IZnDZ7VE--NI2fA?authkey=Gv1sRgCOip8ui3kt7JtQE&feat=directlink
Are they in the same resoultion (Width by Height) as the originals?
Seems like flash was packing the frames weirdly. After repacking them with another program, it works fine.
Well like the title states, I would like to see the kernel messages instead of a boot animation. Just for the geeky look of course ^__^
So is there a way of doing that?
I'm using a German Vodafone Magic 32B, running Cyanogenmod 5.0.8.
I think you can't put the boot in verbose mode, you could do an animated sequence with PNG files to emulate the verbose mode but it won't be the real boot messages of course, just images
Yeah I'm using a boot animation that imitates the BIOS POST-screen on a PC, it's nice but the verbose mode is much cooler
The boot animation I'm using:
http://forum.xda-developers.com/showthread.php?t=648555
What I'm after:
http://www.youtube.com/watch?v=HQKfeDnMVQ8 (about 2 minutes into the video)
If there was a simple setting in a configuration file, it would be awesome, if it required modifing the boot loader, it would suck
From what I understand, you need to change the init.rc file in \
setprop ro.kernel.android.bootanim 0
setprop debug.sf.nobootanimation 1
or simply change export ANDROID_BOOTLOGO 1 to export ANDROID_BOOTLOGO 0 also in init.rc
However, all changes to init.rc are gone after restarting the phone....
Any ideas?
Hm, it seems like the init.rc we see in our rootfs is part of a ramdisk. A ramdisk created from an image in our boot image, i guess a modification of the boot image would help the cause, but that's way too much trouble
quazar666 said:
From what I understand, you need to change the init.rc file in \
setprop ro.kernel.android.bootanim 0
setprop debug.sf.nobootanimation 1
or simply change export ANDROID_BOOTLOGO 1 to export ANDROID_BOOTLOGO 0 also in init.rc
However, all changes to init.rc are gone after restarting the phone....
Any ideas?
Click to expand...
Click to collapse
I modified the boot.img with the first changes but it just broke it. Apparently the setprop method won't work. I'll try the export suggestion sometime in the next couple days and report back.
Awesome, thanks for trying
No problem. If I get it working I'll post a tutorial on how to rebuild the boot.img to do this. I'll also post a premade boot.img for the latest CM release candidate.
Any news ?
nattiii said:
Well like the title states, I would like to see the kernel messages instead of a boot animation. Just for the geeky look of course ^__^
So is there a way of doing that?
I'm using a German Vodafone Magic 32B, running Cyanogenmod 5.0.8.
Click to expand...
Click to collapse
What you want is this http://www.youtube.com/watch?v=7u6qNzsgbxY
As you indicated yourself.......they are messages from the kernel. You would need a kernel that's verbose instead of having a logo.rle. Kernels have specific headers & hashes so its really hard to just 'add' or 'remove' stuff inside. You would need to compile a special kernel to achieve this. I'm pretty sure the permissions & logo.rle are in the initrd which is 1/2 of the Boot.img alongside the zImage. Hope that helps
Any updates on this? This would be killer!
92drls said:
Any updates on this? This would be killer!
Click to expand...
Click to collapse
Try chainfire's "live dmesg" and " live logcat" boot animations, should be available on the market
Sent from my HTC Desire using XDA App
I just tried the live dmesg. That's absolutly brilliant! Thanks for the tip!
Sent from my XT894 using xda app-developers app
Has anybody ever figured out a method to ditch the splash and boot screens and get a descriptive loader, like a diagnostic boot? AKA a no-GUI boot?
I have one, but need help!
I made one! But I need help on it, :-(
Here's what I did and what I need help with:
I looked up the boot process for Android and what happens in what order. So I made a "descriptive boot" screen for it. But now, here is my problem:
My DESC.TXT won't play the second folder! It's written as follows:
320 480 4
p 1 20 part0
p 0 0 part1
If someone can please tell me how to fix it so the second part works, I will DEFINITELY upload it for all to share.
These are git repos for the initramfs that I pulled from the Austria Firmware and the Kernel Source downloaded and reuploaded to github. I'm going to fork and start working on a kernel for when I get the 7.7 myself, but if anyone else wants to start working on it and use them, feel free.
Kernel is still uploading, mistakenly reuploaded the initramfs twice. (Facepalm)
https://github.com/bedwa/P6800-Kernel
https://github.com/bedwa/P6800-initramfs
Enjoy guys!
I have a 6800 device imported from Hong Kong and have been trying to figure out how to port CWM recovery to it. I work as a developer but I haven't looked at this before as I haven't needed to
So far I have rooted the device and had a dig around the filesystem. The partitioning looks similar to the 7 plus:-
179 1 20480 mmcblk0p1 /efs
179 2 1280 mmcblk0p2 /boot
179 3 1280 mmcblk0p3 /mnt/.lfs
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6 / recovery
179 7 204800 mmcblk0p7 /cache
179 8 16384 mmcblk0p8 <radio/modem>
179 9 851968 mmcblk0p9 /system
179 10 13791232 mmcblk0p10 /data
179 11 458752 mmcblk0p11 /preload
179 12 8192 mmcblk0p12
I'm trying to figure out what's in 4,5 and 12.
I have the kernel source code downloaded and buildig and I'm now looking at where to go next. If anyone can post any links to resources on the web which might speed up the process then it would be most appreciated. I don't have a lot of time to spend on this.
Could you "if dd" them and send me a link? I'll be able to find out which is the recovery.img. ;-)
P4 - https://rapidshare.com/files/2298175628/mmcblk0p4.img?bin=1
P5 - https://rapidshare.com/files/2298175628/mmcblk0p4.img?bin=1
P6 - (/recovery) https://rapidshare.com/files/1289796625/recovery.img?bin=1
Let me know what you find and if you don't mind how you went about it. Have got to go and be sociable now
looking in /sys/block/mmbclk0/
gives all the partition info - name,size,ofset, corresponds with pit info from heimdall.
also interested in this
Heres the info (not sure if it helps):
mmcblk0/mmcblk0p4
alignment_ofset 0
discard_alignment 4265607168
inflight 0 0
partition 4
partition_name param
size 16384
start 57344
stat 25 118 1144 0 0 0 0 0 25 40
mmcblk0/mmcblk0p5
alignment_ofset 0
discard_alignment 4257218560
inflight 0 0
partition 5
partition_name kernel
size 16384
start 73728
stat 0 0 0 0 0 0 0 0 0 0
mmcblk0/mmcblk0p6
alignment_ofset 0
discard_alignment 4248829952
inflight 0 0
partition 6
partition_name recovery
size 16384
start 90112
stat 0 0 0 0 0 0 0 0 0 0
mmcblk0/mmcblk0p7
alignment_ofset 0
discard_alignment 4240441344
inflight 0 0
partition 7
partition_name cache
size 409600
start 106496
stat 11 128 20 6 2 64 465 0 280 485
mmcblk0/mmcblk0p8
alignment_ofset 0
discard_alignment 4030726144
inflight 0 0
partition 4
partition_name modem
size 32768
start 516096
stat 58 2560 20944 380 0 0 0 0 330 380
mmcblk0/mmcblk0p9
alignment_ofset 0
discard_alignment 4013948928
inflight 0 0
partition 9
partition_name factoryfs
size 1703936
start 548864
stat 8796 407 701658 31365 0 0 0 0 15540 31325
Thanks - that helps confirm what I had found by digging around and completes the list of partitions.
I have now extracted initramfs from both the runtime and recovery kernels.
Now I need to find time to do some reading on how to port CWM recovery.
Anyone know whats in the param partition?
A quick update....
The partitioning for the 7.7 is very similar to the 7plus.
I have been in contact with the garyd9 who ported CWM to the 7plus and he has given us a few pointers including his github username.
See:-
http://forum.xda-developers.com/showthread.php?p=21717604#post21717604
Interestingly he says that it's likely that the samsung's kernel source release will not have the correct defconfig so we are going to need to tweak it.
The recovery binary gets compiled from the Cyanogenmod sources which are easily obtained.
Unfortunately I'm going to be tied up with my day job for most of this week but will try and look at this again on Friday.
Is there anyone that can keep the ball rolling while I'm busy?
Thanks
Ddraig
I'm getting this one and selling my Note. I'm so excited to see you guys working out of something for P6800 here.
Thanks to all devs in advance!
...........
Dark-Master said:
I'm getting this one and selling my Note. I'm so excited to see you guys working out of something for P6800 here.
Thanks to all devs in advance!
Click to expand...
Click to collapse
+1 here
Anybody want to buy my outdated,used Note?
Hehehe.. well, at least I just *seconds ago* ordered my Tab 7.7 from ebay uk.
Let the modding and ROM flashing begin!
@Lucid what's wrong with your Note..?
Sent from another Galaxy...
Nexus
There is nothing wrong with my Note, it is the best phone I've ever had.
So I went ahead and bought the 7.7 to see if that one is even better. Needs to arrive still.
I intend to use it as a daily phone and will keep it to my ear if needed,
no matter the reactions of other people.
Gadgetwise, I live for myself, not the general public.
I might sell on of them, but history shows I keep all my "old" phones.
I use my galaxy nexus for day to day but since finding out about phoneleash i dont really touch my phone anymore.. check out phone leash if you have two SIMs.. although i guess it can work with GV also..
Sent from another Galaxy...
Tab 7.7
I placed my 7.7 next to my Titan, Sensation and the Galaxy Note today to see how it fares, no way is it practical to put to the ear and it is pretty ridiculous to carry. It's a compact device but not THAT compact. My Kindle Fire was more handy. The bezel is too large.
However, the phone functionality is superb and if one can find an unobtrusive way to carry it, we could finally unify our communication requirements in one device.
lucid said:
There is nothing wrong with my Note, it is the best phone I've ever had.
So I went ahead and bought the 7.7 to see if that one is even better. Needs to arrive still.
I intend to use it as a daily phone and will keep it to my ear if needed,
no matter the reactions of other people.
Gadgetwise, I live for myself, not the general public.
I might sell on of them, but history shows I keep all my "old" phones.
Click to expand...
Click to collapse
monakh said:
.However, the phone functionality is superb and if one can find an unobtrusive way to carry it, we could finally unify our communication requirements in one device.
Click to expand...
Click to collapse
Check out the Samsung HM5000 Bluetooth pen thingy.
Y Ddraig Goch said:
A quick update....
The partitioning for the 7.7 is very similar to the 7plus.
I have been in contact with the garyd9 who ported CWM to the 7plus and he has given us a few pointers including his github username.
See:-
http://forum.xda-developers.com/showthread.php?p=21717604#post21717604
Interestingly he says that it's likely that the samsung's kernel source release will not have the correct defconfig so we are going to need to tweak it.
The recovery binary gets compiled from the Cyanogenmod sources which are easily obtained.
Unfortunately I'm going to be tied up with my day job for most of this week but will try and look at this again on Friday.
Is there anyone that can keep the ball rolling while I'm busy?
Thanks
Ddraig
Click to expand...
Click to collapse
Ddraig - I have been trying to get this get up and running.
So far I have managed to compile a zImage (recovery.img) using pretty much with the default config. Flashed through heimdall
I have used garyd9 recovery_initramfs, used his /sbin folder as is. The rest of the files are taken from the stock gt-6800 ramdisk inc modules. Where necessary make changes to partition entrys.
It boots in to clockworkmod recovery fine. It can mount all partitions but not /cache partition properly. I have checked the path and it seems correct ??
(I can mount via adb but cwm says it cant find it)
I will try building recovery binary at some point but will be busy for some days now.
I can you sent you some of my config files / recovery.img if it helps.
ezynow said:
Ddraig - I have been trying to get this get up and running.
So far I have managed to compile a zImage (recovery.img) using pretty much with the default config. Flashed through heimdall
I have used garyd9 recovery_initramfs, used his /sbin folder as is. The rest of the files are taken from the stock gt-6800 ramdisk inc modules. Where necessary make changes to partition entrys.
It boots in to clockworkmod recovery fine. It can mount all partitions but not /cache partition properly. I have checked the path and it seems correct ??
(I can mount via adb but cwm says it cant find it)
I will try building recovery binary at some point but will be busy for some days now.
I can you sent you some of my config files / recovery.img if it helps.
Click to expand...
Click to collapse
Sounds like you have made some progress with custom recovery, you need to be careful if you are using garyd9 recovery_initramfs on your device, note one i think this for a wifi device being p6210 if you device is a p6800 check all the mounting points as there are some slight differences between wifi and 3g devices. how did you compile your source and make compatible odin file. i'm on a mac and so far i can't get heimdall to work with p6810.
kassemja said:
Sounds like you have made some progress with custom recovery, you need to be careful if you are using garyd9 recovery_initramfs on your device, note one i think this for a wifi device being p6210 if you device is a p6800 check all the mounting points as there are some slight differences between wifi and 3g devices. how did you compile your source and make compatible odin file. i'm on a mac and so far i can't get heimdall to work with p6810.
Click to expand...
Click to collapse
After 2 days of kernel building and insmod, I've finally got a P6810 module to insmod successfully into my stock device. This is the config. It comes from the samsung source (GT-P6810_HC_Opensource) download with some DEBUG params turned off, and the local version set for the Australian DTKL5 firmware. I hope it can help someone avoid some trial and error pain. The p6800 guys may be able to turn off similar debugs and get theirs working. This is not fully tested, if you find other params that need changing please advise.
EDIT: I flashed this kernel to my device and it worked.
Here is more information on the environment.
CodeSourcery toolchain arm-2009q3-67-arm-none-linux-gnueabi.bin
Change the supplied Makefile CROSS_COMPILE to point to installed toolchain (eg, /home/davp/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi-)
Copy the supplied file to .config in the directory where you unpacked the kernel source, then run make
Links http://forum.xda-developers.com/showpost.php?p=21870378&postcount=23 for how to do a basic initramfs to go with the new kernel (the result of this is running a command like: make -j5 CONFIG_INITRAMFS_SOURCE=initramfs_root, and then tar and flash the zImage).
Copy of the .config file (from the kernel directory):
Can you confirm you have suscessfully compiled and flashed a working kernel?
I want to have a crack at custom recovery for the p6810, i'm pretty confident we can getting going using a blend of sources from https://github.com/garyd9/initramfs_recovery_GT-P6210 and our kernel stuff.
davp said:
After 2 days of kernel building and insmod, I've finally got a P6810 module to insmod successfully into my stock device. This is the config. It comes from the samsung source (GT-P6810_HC_Opensource) download with some DEBUG params turned off, and the local version set for the Australian DTKL5 firmware. I hope it can help someone avoid some trial and error pain. The p6800 guys may be able to turn off similar debugs and get theirs working. This is not fully tested, if you find other params that need changing please advise.
Click to expand...
Click to collapse
Oh great - the 7.7 also has binary-only modules?
Freaking Samsung, I thought they were making progress with the I9100/I777 (100% open-source kernels, no proprietary modules).
Good luck bedwa - feel free to browse my github for Exynos tips (although much of it will not directly patch onto HC kernels), garyd9 knows what he's doing too.
Can someone help and tell me if this boot animation works for Oxygen OS on the Oneplus 3t? If not, can anyone tell me how to fix it?
P.S. Please be a good doggy and DO NOT steal my animation.
P.P.S. Except for the water drip part. The idea came from: https://forum.xda-developers.com/android/themes/bootanimations-50-flashable-t3059659
Boot Anim. Link: http://bit.ly/KairuBoot
Theoretically it should.
Just place the zip to system/media (Replace the excsisting one.
pahapoika91 said:
Theoretically it should.
Just place the zip to system/media (Replace the excsisting one.
Click to expand...
Click to collapse
Thanks, needed to make sure that my desc.txt and things we're correct before I try it and possibly brick my phone.
opsElyK said:
Thanks, needed to make sure that my desc.txt and things we're correct before I try it and possibly brick my phone.
Click to expand...
Click to collapse
No worries. You can't brick a device with a buggy bootanimation.
At the worst case you'll have a black screen instead of the animation (but the phone will boot to Android).
EDIT @opsElyK
here is your desc.txt:
Code:
1080 1920 30
p 1 0 Transition
p [B][COLOR="Red"]0[/COLOR][/B] 0 Pixeldrip
p 1 0 Kairu
This 0 means that your folder 'Pixeldrip' will loop until Android is ready. In other words, Kairu won't be used.
More information
Primokorn said:
No worries. You can't brick a device with a buggy bootanimation.
At the worst case you'll have a black screen instead of the animation (but the phone will boot to Android).
EDIT @opsElyK
here is your desc.txt:
Code:
1080 1920 30
p 1 0 Transition
p [B][COLOR="Red"]0[/COLOR][/B] 0 Pixeldrip
p 1 0 Kairu
This 0 means that your folder 'Pixeldrip' will loop until Android is ready. In other words, Kairu won't be used.
More information
Click to expand...
Click to collapse
Crap. How would you make it so that Kairu will play last?
It's definitely possible because it does it with the oxygenos boot animation.
opsElyK said:
Crap. How would you make it so that Kairu will play last?
It's definitely possible because it does it with the oxygenos boot animation.
Click to expand...
Click to collapse
Replace 0 by 1 or higher
Code:
1080 1920 30
p 1 0 Transition
p 1 0 Pixeldrip
p 1 0 Kairu
It depends on what you want. 'p' can also be replaced by 'c' and so on...
Primokorn said:
Replace 0 by 1 or higher
Code:
1080 1920 30
p 1 0 Transition
p 1 0 Pixeldrip
p 1 0 Kairu
It depends on what you want. 'p' can also be replaced by 'c' and so on...
Click to expand...
Click to collapse
Thanks, I got it now.