This needs its own thread.
So far, I've found the location of the boot screens and sprint animation. I shelled into /system/media/bootscreen
In there I found:
boot.gif
boot2.gif
boot_animation.xml
boot.mp3
boot_bg.gif
sprint.gif
Removing all of these files still takes just as long to boot, and all the screens go blank. Recovered, and still waiting on another solution. Anyone know if there is more to this?
Have you tried editing the xml? Also, did the sounds still play?
shameless bump
Why would the animations make booting slower?
The phone has a lot of stuff to do. The animations don't add to the boot time, they're just something to have on the screen instead of a bunch of linux system messages and commands.
I did remove the MP3 because it was annoying
jonnythan said:
Why would the animations make booting slower?
The phone has a lot of stuff to do. The animations don't add to the boot time, they're just something to have on the screen instead of a bunch of linux system messages and commands.
I did remove the MP3 because it was annoying
Click to expand...
Click to collapse
Did you guys figure it out? I made a custom rom by taking MoDaCo's removing anything I didnt want and then editing the build.prop file. At the end of that file if you add these two lines:
Code:
ro.kernel.android.bootanim=0
debug.sf.nobootanimation=1
It will skip the boot anim. It will just show the HTC logo and boot A LOT faster.
is there any way to do this without rolling our own ROM / build.prop file?
chuckhriczko said:
Did you guys figure it out? I made a custom rom by taking MoDaCo's removing anything I didnt want and then editing the build.prop file. At the end of that file if you add these two lines:
Code:
ro.kernel.android.bootanim=0
debug.sf.nobootanimation=1
It will skip the boot anim. It will just show the HTC logo and boot A LOT faster.
Click to expand...
Click to collapse
It actually boots faster? Could you post some stopwatch times or something for it and perhaps we can get that optimization included in a kernel release!
It doesn't actually boost faster.. I took out every single gif out of the XML file, and it took a minute 8 to boot.. I put them all back in and it took a minute 3 to boot (5 seconds is nothing) so it makes absolutely no difference
nelson8403 said:
It doesn't actually boost faster.. I took out every single gif out of the XML file, and it took a minute 8 to boot.. I put them all back in and it took a minute 3 to boot (5 seconds is nothing) so it makes absolutely no difference
Click to expand...
Click to collapse
That's because it is still trying to do the boot sequence even if the files are removed. You have to modify the build.prop file to actually have the system skip the boot animation sequence altogether. I am at work right now but hopefully on my lunch break I can flash MoDaCo's rom and then my rom and I will post boot times.
chuckhriczko said:
That's because it is still trying to do the boot sequence even if the files are removed. You have to modify the build.prop file to actually have the system skip the boot animation sequence altogether. I am at work right now but hopefully on my lunch break I can flash MoDaCo's rom and then my rom and I will post boot times.
Click to expand...
Click to collapse
Edit : I did a bad copy back.. I added those 2 lines and it took 50 seconds instead of a minute 3, not a huge difference, but not bad
chuckhriczko said:
That's because it is still trying to do the boot sequence even if the files are removed. You have to modify the build.prop file to actually have the system skip the boot animation sequence altogether. I am at work right now but hopefully on my lunch break I can flash MoDaCo's rom and then my rom and I will post boot times.
Click to expand...
Click to collapse
Sweet! That's exciting news! Can't wait to see the results.
Okay. Just flashed MoDaCo with the boot images and anims still on. Then I flashed my rom which is MoDaCo but has a bunch of apps removed AND boot animations off in the build.prop file. The results are below:
Code:
Boot anims on: 102 seconds
Boot anims off: 72 seconds
30 seconds isnt too shabby if you ask me
chuckhriczko said:
Okay. Just flashed MoDaCo with the boot images and anims still on. Then I flashed my rom which is MoDaCo but has a bunch of apps removed AND boot animations off in the build.prop file. The results are below:
Code:
Boot anims on: 102 seconds
Boot anims off: 72 seconds
30 seconds isnt too shabby if you ask me
Click to expand...
Click to collapse
Sweet, I just echo'd the commands in and I get: (Time until lock screen)
Boot Animations off: 63 seconds (HTC Logo, then "No service for a few seconds, then lockscreen)
Boot Animations on: 68 seconds
----------------------------------
(Feel free to confirm my math, I wrote down the start/stop times)
No Anims
start: 9:30:10
end: 9:31:13
Anims
start: 9:32:47
end: 9:33:55
----------------------------------
The commands I issued were: (after remounting the filesystem read/write)
Code:
cp /system/build.props /system/build.props.old
echo "ro.kernel.android.bootanim=0" >> build.prop
echo "debug.sf.nobootanimation=1" >> build.prop
Then to test animations back on, I just copied the .old file back into it's place.
Hmm...a very small difference in my testing. Was there anything else you did? (Be aware, the first boot of MoDaCo takes significantly longer than subsequent boots as it's setting a bunch of things up.
That appended the commands to the end of build.props
Mine was only about 10 seconds the first boot difference, and 5 seconds the second time, so this isn't a huge boot difference, but I don't exactly miss the sprint.gif
chuckhriczko said:
Okay. Just flashed MoDaCo with the boot images and anims still on. Then I flashed my rom which is MoDaCo but has a bunch of apps removed AND boot animations off in the build.prop file. The results are below:
Code:
Boot anims on: 102 seconds
Boot anims off: 72 seconds
30 seconds isnt too shabby if you ask me
Click to expand...
Click to collapse
why is your phone taking so long to boot? mine's never taken better part of 2 minutes
nelson8403 said:
why is your phone taking so long to boot? mine's never taken better part of 2 minutes
Click to expand...
Click to collapse
102 seconds is 1 minute, 42 seconds.
72 seconds is 1 minute, 12 seconds.
2 minutes is 120 seconds.
thecodemonk said:
Sweet, I just echo'd the commands in and I get: (Time until lock screen)
Boot Animations off: 63 seconds (HTC Logo, then "No service for a few seconds, then lockscreen)
Boot Animations on: 68 seconds
----------------------------------
(Feel free to confirm my math, I wrote down the start/stop times)
No Anims
start: 9:30:10
end: 9:31:13
Anims
start: 9:32:47
end: 9:33:55
----------------------------------
The commands I issued were: (after remounting the filesystem read/write)
Code:
cp /system/build.props /system/build.props.old
echo "ro.kernel.android.bootanim=0" >> build.props
echo "debug.sf.nobootanimation=1" >> build.props
Then to test animations back on, I just copied the .old file back into it's place.
Hmm...a very small difference in my testing. Was there anything else you did? (Be aware, the first boot of MoDaCo takes significantly longer than subsequent boots as it's setting a bunch of things up.
That appended the commands to the end of build.props
Click to expand...
Click to collapse
Mine are actually part of the rom on install but thats houldnt make any difference. I will see what other testing I can get done to help with this.
Thanks codemonk.
Just thought I'd mention that your commands are a little off. It's build.prop not props... I got some error messages until I saw it.
Code:
cp /system/build.prop /system/build.prop.old
echo "ro.kernel.android.bootanim=0" >> build.prop
echo "debug.sf.nobootanimation=1" >> build.prop
mercado79 said:
Thanks codemonk.
Just thought I'd mention that your commands are a little off. It's build.prop not props... I got some error messages until I saw it.
Code:
cp /system/build.prop /system/build.prop.old
echo "ro.kernel.android.bootanim=0" >> build.prop
echo "debug.sf.nobootanimation=1" >> build.prop
Click to expand...
Click to collapse
DOH! Thanks for the fix...I was typing it while watching the reboot. I'll uhm...edit the post so people don't get confused.
The cp command will not work for me! I'm on a bloatware free rooted stock rom...
Related
D//After all, Thank you for your great work, Skrilax_CZ!.
//And also, thank you tenfar, your defy bootstrap apk!
2011.01.09.
Totally new version is released, so this page is re-written.
Now, you can use recovery mode when your phone is bricked!
-No need to boot to android. just press button to go to Recovery mode.
/***********************************************************/
// OpenRecovery_Bootstrap_Glam
// 헌진([email protected])
// OpenRecovery by Skrilax_CZ
// Androidiani OpenRecovery 3.3 by Androidiani
// 2011.01.05 (last modified 2011.01.09)
/***********************************************************/
Source code, binarys are available.
Download link : code.google.com/p/openrecovery-for-xt800w/downloads/list
It's another version of sh hijacking bootstrap openrecovery.
The original one 'Skrilax_CZ' made doesn't works for xt800w (moto glam), so I changed 'sh' binary.
1.How to install
-If you are using old version, please remove it before you install.
2.1
(You have to be rooted, busybox had installed.)
Copy OpenRecovery.zip and OpenRecovery directory to your sdcard root.
Install XT800W_OpenRecovery.apk
Run XT800W_Recovery on your phone.
Click Install button.
2.2 (alternative method - via adb shell or ssh (not recommend))
(You have to be rooted, busybox had installed.)
Copy OpenRecovery.zip and OpenRecovery directory to your sdcard root.
$su
#cp /sdcard/openrecovery/orbootstrap/install_script.sh /tmp
#cd /tmp
#chmod 755 install_script.sh
#./install_script.sh
Click to expand...
Click to collapse
2. How to use
2.1
Run XT800W_Recovery on your phone.
Click Recovery button!
2.2
Reboot your phone.
When the phone vibrate or led backlight is turned on, press any button(ex, Volume, power, search, camera)
2.3
(alternative method - via adb shell or ssh(not recommend))
$su
#/system/persistent/orbootstrap/openrecovery.sh
-If you want to add custom script, add it to scripts directory or
See files in amenu directory and mod directory.
Click to expand...
Click to collapse
3. Vibration, led button backlight, waiting time while boot setting.
Open /system/persistent/orbootstrap/bootToRecoveryOption
1st line : vibration time in second. min 0, max 10
2nd line : 0 - led off, 1 - led on
3rd line : waiting time for detrmine go to recovery or not. in seconds. min 1, max 10
Initial Value is
2
1
2
it means, 2seconds vibrate(first line), led back-light is on(second line), 2seconds wait for pressing key(third line)
To set no vibration, led is off, 2 seconds to wait,
0
0
2
(all lines have no blank, no alpahbet, no tab ect...
just type numbers and go next line!)
Click to expand...
Click to collapse
4. What's different?
4.1. XT800W_Recoery app design and recovery running method changed.
4.2. sh binary changed(only do exec >> shell + hijacking)
4.3. Now you can use this with out boot in android! just press the button.
5. How does it working?
install_script.sh - backup orignal sh to sh.bin, copy custom implementated sh binary.
When you press any key while phone is vibrating or led backlight is on in booting,
(or there exsist /system/persistent/recovery_mode file)
sh runs /system/persistent/orbootstrap/utils/a.sh
a.sh sets recovery environment and calls 2nd-boot.
2nd-boot restart init process
init process boot into recovery mode.
hounjini said:
D//After all, Thank you for your great work, Skrilax_CZ!.
//And also, thank you tenfar, your defy bootstrap apk!
2011.01.09.
Totally new version is released, so this page is re-written.
Now, you can use recovery mode when your phone is bricked!
-No need to boot to android. just press button to go to Recovery mode.
/***********************************************************/
// OpenRecovery_Bootstrap_Glam
// 헌진([email protected])
// OpenRecovery by Skrilax_CZ
// Androidiani OpenRecovery 3.3 by Androidiani
// 2011.01.05 (last modified 2011.01.09)
/***********************************************************/
Source code, binarys are available.
Download link : code.google.com/p/openrecovery-for-xt800w/downloads/list
It's another version of sh hijacking bootstrap openrecovery.
The original one 'Skrilax_CZ' made doesn't works for xt800w (moto glam), so I changed 'sh' binary.
[/SIZE]
4. What's different?
4.1. XT800W_Recoery app design and recovery running method changed.
4.2. sh binary changed(only do exec >> shell + hijacking)
4.3. Now you can use this with out boot in android! just press the button.
5. How does it working?
install_script.sh - backup orignal sh to sh.bin, copy custom implementated sh binary.
When you press any key while phone is vibrating or led backlight is on in booting,
(or there exsist /system/persistent/recovery_mode file)
sh runs /system/persistent/orbootstrap/utils/a.sh
a.sh sets recovery environment and calls 2nd-boot.
2nd-boot restart init process
init process boot into recovery mode.
Click to expand...
Click to collapse
Xt800w already have the 2.2?
big thx ~~~
what about the system?
I dump the system with your recovery but failed.
Have you decided to dump the system?
motoxt800w said:
Xt800w already have the 2.2?
Click to expand...
Click to collapse
moto said that 2.2 is planned to be released in q1 2011
2.2....When brush ah 2.2？
hounjini said:
/***********************************************************/
// OpenRecovery_Bootstrap_Glam
// 헌진([email protected])
// OpenRecovery by Skrilax_CZ
// Androidiani OpenRecovery 3.3 by Androidiani
// 2011.01.05 (last modified 2011.01.09)
/***********************************************************/
Click to expand...
Click to collapse
I can't use apply update.zip in OpenRecovery to uprom
or because I use Cygwin to cook rom fails?
any one was like me?
sorry for a very noob question, but how to root xt800w. I just got this phone today and i search there is no specific subforum for this one. Thx for the clues...
I can't go into bootloader so please guide me slowly ...any video for bootloader?
[Q] How to increase vibration duration of soft keys
HELP!
I have Motorola Glam XT800W running MIUI.1.5.27.Ko Android 2.3.4 and I love everything about it except the limited personalizing options.
My main concern is how do I increase the vibration duration in pressing the soft keys? They are set so low that I can barely feel it.
Another is my notification led lights are not working at all, its not that its defective. I think it has to do something with the rom. How should I fix this?
Is there a way that I can upgrade my phone to MIUI 4.0 ICS? Please advice. Thank you very much!
need help
can anyone here help me on how to unbrick my xt800w?it is always stuck up on booting please someone help me on this thing :crying::crying::crying::crying::crying::crying::crying:
I hold no responsibility to how you use or not use this info and if you brick phone - you do this at your own risk
Mini How To
How to install recovery and custom ROMs
Changelog and Downloads
2011-02-11
IMPORTANT NOTE: I have not tested this ROM as I not own U8150 anymore
FILENAME: U8150V100R001C191B822_021211_094422.zip
MD5: 110c084c71729aca1ea8361dcb5fe5f5
* Reverted back to Launcher2
* Added Apps2SD
* Add couple apps I think is useful: wifi analyzer, android terminal, alogcat, cache cleaner-ng. (these can be easily uninstalled)
* Built with latest kitchen 0.120
* Removed Gingerbread keyboard and Google Goggles
2011-01-15
FILENAME: U8150V100R001C191B822_011511_221843.zip / Mirror
MD5: 357e5efb21d3272bb0820c0e14cfe913
* Added Boot Animation - Android Scribble 2.0 no flare
* Added Gingerbread Keyboard - Renamed Gingerbread Keyboard - updated 2010-12-28
* Unlocked Market - thanks xxhp for the package
* Added Google Goggles and AdFree
2011-01-09
This ROM should have overall better performance(hopefully)
Note:
Do a wipe of data and must clear dalvik-cache because of JIT being enabled (under 'wipe' in AmonRA Recovery 1.6.2 ROM)
FILENAME: U8150V100R001C191B822_010911_182214.zip
MD5: d8fae03567ebfa1602a116cc9e5aa587
* Added more ring tones from CM rom
* Ring delay fix
* CDRom symlink fix
* Fixed proximity delay (phone come off of the "black screen" faster)
* Turned Automatic brightness ON
* Now wifi will scan once every 1 minutes when not around a known location.
Help minimize battery drain.
* Added JIT
* Set Setup Wizard to run 'Optional'
2011-01-05 Initial Release
FILENAME: U8150V100R001C191B822_010511_014603.zip
MD5: 059fe7693164b1031a63fce373d57717
* Rooted (Superuser.apk + su)
* BusyBox installed
* /system/framework is deodexed
* /system/app is deodexed
* twitter/facebook/documents2go moved to /data/app
* swapped out Launcher 2 for Zeam Launcher
* Apps like Gmail, Maps, Vending etc updated.
If you like my work please make a donation via the Donate to me button on the left
Enjoy
Thanks for the update quail!
Do you have the AUS version of the Ideos? If so, who'd you get yours from?
Also, can we use this thread as a ROM request? (i.e. overclocking ability, gingerbread development)
Thanks. But can you plz post a guide or give a link on how to install the modified ROM in IDEOS for noobs like me
hachoo said:
Thanks for the update quail!
Do you have the AUS version of the Ideos? If so, who'd you get yours from?
Also, can we use this thread as a ROM request? (i.e. overclocking ability, gingerbread development)
Click to expand...
Click to collapse
Yes I have the AU version and I bought a Crazy Johns pack with 4GB micro HCSD carded included from Aus. Post for 159AUD. I was luck and go one that was not locked to any network.
Yes you can use the thread for ROM requests, I personally will be ignoring requests for OCing, as there is a very nice little app called setCPU which works great on the U8150.
[How to] install recovery and custom ROMs
I hold no responsibility to how you use or not use this info and if you brick phone - you do this at your own risk
Part 1 Installing Recovery ROM
Please refer to this post before flashing Recovery ROM - AmonRA Recovery 1.6.2 and BLUE Screen
The custom recovery allows you to do all sorts of lovely things such as installing ROM update zips (for the forthcoming custom ROMs), wiping various parts of the device, backing up and restoring and much more.
You can enter recovery mode - turn it off, then press the power button while holding the 'volume up' and 'send' (green).
Downloads
AmonRA Recovery 1.6.2 - DOWNLOAD (MediaFire Pro) / MIRROR (CoBlitz / ROMraid) - MD5: 65d4dcbbedb956a9f88dd1981fb31ef8
How to install - Windows, Linux and OSX
Download the recovery image of your choice above and extract the zip file
Put your device in bootloader mode - turn it off, then press the power button while holding the 'Volume Down' and 'End (Red)' keys
WINDOWS - double click 'install-recovery-windows.bat'
MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-mac.sh' followed by './install-recovery-mac.sh'
LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-linux.sh' followed by './install-recovery-linux.sh'
Part 2 Installing Custom ROM
Note: When using the Custom Recovery image use the Trackball to move up / down and press to select. Use the volume down button to go back.
Download a Custom ROM of your choice and place the ENTIRE ZIP (Do not extract it) onto the root of your SD card. By "Root" I mean do not place the file in any subfolders
Enter recovery mode - turn it off, then press the power button while holding the 'volume up' and 'send' (green).
From Custom Recover Main menu and select the 'Backup/Restore' option. Choose a 'Nand backup' and let it run it's course
Return to the Custom Recover Main menu and select the 'Wipe' option. Choose the First option 'Wipe data/factory reset' and confirm. <- this is optional after installing one of my ROMs. I personally have not bothered with it with my ROMs
Return to the Custom Recover Main menu and select the 'Flash zip from sdcard'. Select the custom rom you wish to flash, confirm and wait.
Part 3 Restoring back to original ROM
Note: Upgrade operations will erase the user data.
Find and Download ROM from Link provided on WiKi that you want to install
Copy the entire dload folder (with UPDATE.APP in it) to the root directory of the MICRO SD card.
Make sure your handset is power off. Insert the MICRO SD card into the handset. Pressing the END key and VOLUME UP key, and then press the POWER key to power on the phone and enter the Software Upgrade Mode.
You can see process bar start from 0 on the screen. (this take a few minutes)
Then the handset will restart automatically. Then it is OK.
Reference:
Part 1 info taken from here
quail said:
Yes I have the AU version and I bought a Crazy Johns pack with 4GB micro HCSD carded included from Aus. Post for 159AUD. I was luck and go one that was not locked to any network.
Yes you can use the thread for ROM requests, I personally will be ignoring requests for OCing, as there is a very nice little app called setCPU which works great on the U8150.
Click to expand...
Click to collapse
I got the same deal!
Have you played around with the kernel at all? I'm not experienced in programming etc. but apparantly to OC the IDEOS U8150 more than 600mhz (setcpu does this automatically), it needs a kernel hack like other phones do.
Trekker56 said:
Thanks. But can you plz post a guide or give a link on how to install the modified ROM in IDEOS for noobs like me
Click to expand...
Click to collapse
Sorry I did think to add a how to install recovery/custom ROM how to, well there is one now.
Thanks
hachoo said:
I got the same deal!
Have you played around with the kernel at all? I'm not experienced in programming etc. but apparantly to OC the IDEOS U8150 more than 600mhz (setcpu does this automatically), it needs a kernel hack like other phones do.
Click to expand...
Click to collapse
I have played around with Linux Kernels in the past just not the Android kernel yet... but I am sure it not that hard to patch it and recompile.
I am happy with the 600MHz that setCPU unlocks it too.
quail said:
You can enter recovery mode - turn it off, then press the power button while holding the 'volume up' and 'send' (green).
[*] Put your device in bootloader mode - turn it off, then press the power button while holding the 'Volume Down' and 'End (Red)' keys
Click to expand...
Click to collapse
The Main thinkg about these two parts here, when i enter recovery mode i get a blue screen is that right... nothing BUT a blue screen.
When i try to enter the bootloader mode it stays on the IDEOS logo, the first one when you turn it on...
Also im guessing it has to be plugged into the usb at all times for these.
tankknat said:
The Main thinkg about these two parts here, when i enter recovery mode i get a blue screen is that right... nothing BUT a blue screen.
When i try to enter the bootloader mode it stays on the IDEOS logo, the first one when you turn it on...
Also im guessing it has to be plugged into the usb at all times for these.
Click to expand...
Click to collapse
You should not be getting a blue screen, you sure your using the correct key combination?
Yes you need the USB cable plugged in to use the bootloader. Yes the bootloader is ment to just sit at the IDEOS logo
yeah im 100% sure i used the correct key combo for the restore recovery mode, and sweet as for the bootloader, just wasnt 100% sure on that one.
Thank you OP for the info here, I used them to flash the recovery and I'm going to flash your ROM.
Having a Desire from the very first day I'm not new to these things, but this little boy is in my hands since this afternoon and it's amazing that you came with this just in time.
Will report back in a while with impressions.
OK, here I am. Just attempted to flash the ROM (after a full wipe), but it fails with an "Installation aborted." message just after the ISO symlink one. Looking at the update script, I guess there was a problem while flashing the BOOT partition.
Rebooting into the OS result in the new (rooted) ROM, but something is missing: the build.prop is likely the old one (I still see the old build string) and I have only 118 MB of free NAND space.
Coming from the Vodafone Italy ROM.
Any hint?
@ngel said:
OK, here I am. Just attempted to flash the ROM (after a full wipe), but it fails with an "Installation aborted." message just after the ISO symlink one. Looking at the update script, I guess there was a problem while flashing the BOOT partition.
Rebooting into the OS result in the new (rooted) ROM, but something is missing: the build.prop is likely the old one (I still see the old build string) and I have only 118 MB of free NAND space.
Coming from the Vodafone Italy ROM.
Any hint?
Click to expand...
Click to collapse
What package did you download? I forgot to test one my builds and aborted installation on me, but I have fixed it and already put up a work version. Please try the newer version
quail said:
What package did you download? I forgot to test one my builds and aborted installation on me, but I have fixed it and already put up a work version. Please try the newer version
Click to expand...
Click to collapse
Hi, I flashed "U8150V100R001C191B822_010711_042603", the one I guess is the newest (despite the "2010" typo on the first post ).
Is there a newer one?
@ngel said:
Hi, I flashed "U8150V100R001C191B822_010711_042603", the one I guess is the newest (despite the "2010" typo on the first post ).
Is there a newer one?
Click to expand...
Click to collapse
thanks, fixed the typo.
ATM there is no newer version.
@ngel said:
OK, here I am. Just attempted to flash the ROM (after a full wipe), but it fails with an "Installation aborted." message just after the ISO symlink one. Looking at the update script, I guess there was a problem while flashing the BOOT partition.
Rebooting into the OS result in the new (rooted) ROM, but something is missing: the build.prop is likely the old one (I still see the old build string) and I have only 118 MB of free NAND space.
Coming from the Vodafone Italy ROM.
Any hint?
Click to expand...
Click to collapse
Another thing I am not sure what the diff is between the Italian ROM and the Australian ROM. I wonder if you phone is not fully compatible with the Australian ROM?
ARGH, ok not good...
booted up to flash my loving ideos and i think i killed it...
'Firemware update step 1/2
Unpacking
[=============] (thats a progress bar
!
update failed
and all my buttons are blinking...
First version working
I had the same problems as @ngel using the newer version. Fail with the iso symlink.
Used the first version you posted up and that worked without a problem.
Zeam Launching is really snappy. Or I just haven't bogged down my phone with a whole bunch of crap yet.
Thanks for your work I bought my Ideos through 2 Degrees in New Zealand.
Request:
I quite like the look of the black notification bar and green icons. Would you be able to theme this rom with those? Also could you include the gingerbread keyboard. I know I can install it separately but would be cool to have Touch Pal and the original keyboard removed and replaced with the gingerbread one.
tankknat said:
ARGH, ok not good...
booted up to flash my loving ideos and i think i killed it...
'Firemware update step 1/2
Unpacking
[=============] (thats a progress bar
!
update failed
and all my buttons are blinking...
Click to expand...
Click to collapse
Did you power on your unit holding the 'volume up' and 'red' key?
Hello and welcome to Androtility 0.7!
***S-OFF Required!***
***Mac***
Features:
Push Files
Pull files
Flash Recovery
Flash Radio
Flash HBOOT
Flash Splash
Automatically converts BMP to compatible Splash NB (using nbimg)
Replace Bootanimation
Backup Bootanimation
Enter in Fastboot
Logcat!
Enter in Recovery
Reboot
It should be fairly easy to use, it explains everything.
Let me know what you would like in this app, and i will do it.
Instructions:
Code:
cd [DRAG_ANDROTILITY_FOLDER_HERE]
./Androtility
Then choose your option.
Download: http://d-h.st/hv0
Change Log:
V0.7
Fixed bug causing error on entering the menu.
Fixed bug causing error on choosing recovery commands
Added logcat feature!
V0.6
Bugfixes
Code VERY Optimized
Flash HBOOT option
In previous versions, there were some junk files. Not anymore!
You can choose if you have your own NB file, or if you want it to convert the photo to a NB file.
V0.5
Bugfixes
Code cleaned
V0.4
Name changed to "Androtility", because it's not just flashing images, so it's a utility
After the app finishes a task, it returns to the menu.
Now you must push/pull files/bootanimations via recovery, for more safety + reliability
Some grammar corections
Code cleaned up
V0.3
Added "Push files" and "Pull files"
Code cleaned up
Bugfixes
V0.2
Added "Do you want to reboot?" after flashing splash/radio/recovery
Bugfixes
V0.1
Initial Release
andreigherghe said:
Change Log:
V0.1
Initial Release
Click to expand...
Click to collapse
download link?
Oops, forgot to upload
It's in the first post.
Bump!
0.2 is out!
Great.
Will try this out.
Thanks.
Bump!
0.3 Is out!
Bump again!
0.4 version just cooked!
Also, thank you guys for 100 downloads
What does the Pull files do?. Does it remove it from the phone and "put" it somewhere on your PC instead or?
MeX_DK said:
What does the Pull files do?. Does it remove it from the phone and "put" it somewhere on your PC instead or?
Click to expand...
Click to collapse
Downloads a file from the phone into the "Data" folder.
so this is only for mac?
Yes, why?
You need it for another OS?
I tried to port it to Linux, but there were too many permission problems with adb and fastboot
how about windows version?
bradputt said:
how about windows version?
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=794638
Bumpy BUMP! 0.6 is out!
great... thx
Glad you like it
PS: Looking forward to feature-requests!
it's perfect for me that i have volume button broken (flat cable )
could i get a mirror on the link ... proxy at work blocks that one
Hey there, just about to flash a splash Screen was wondering you if anyone has ever found many problems with it?
as ive used android flasher and ADB at my friends house (dont own a windows computer) but is this as stable ect as android flasher?
(dont my phone in already this phone dont fancy doing it again for a while :L)
looks very promising
Original Post | CWM
Guys check this out
Best result on Android 4.+
Description
Hey everyone,
So, I was experiencing significant lag as we all do from time to time, and decided I was going to get to the bottom of it.
After tracing and debugging for hours, I discovered the source of 90% of Android's lag. In a word, entropy (or lack thereof).
Google's JVM, like Sun's, reads from /dev/random. For all random data. Yes, the /dev/random that uses a very limited entropy pool.
Random data is used for all kinds of stuff.. UUID generation, session keys, SSL.. when we run out of entropy, the process blocks. That manifests itself as lag. The process cannot continue until the kernel generates more high quality random data.
So, I cross-compiled rngd, and used it to feed /dev/urandom into /dev/random at 1 second intervals.
Result? I have never used an Android device this fast.
It is literally five times faster in many cases. Chrome, maps, and other heavy applications load in about 1/2 a second, and map tiles populate as fast as I can scroll. Task switching is instantaneous. You know how sometimes when you hit the home button, it takes 5-10 seconds for the home screen to repopulate? Yeah. Blocking on read of /dev/random. Problem solved. But don't take my word for it .. give it a shot!
Update!
I've built a very simple Android app that bundles the binary, and starts/stops the service (on boot if selected). I'll be adding more instrumentation, but for now, give it a shot! This APK does not modify /system in any way, so should be perfectly safe.
This is my first userspace Android app, so bear with me!
Note that this APK is actually compatible with all Android versions, and all (armel) devices. It's not at all specific to the Captivate Glide.
Click to expand...
Click to collapse
Quote Original Post link - Click Here
UPDATE: Seeder_v7 is out, as suggested by pepoluan, it now detects for qrngd (built in rngd for Qualcomm Snapdragon-based devices), if it is there, then it will not start as rngd may conflict with it...the rngd binary is also using the latest version (it is turned off when screen is off)...users of previous versions can just flash it over...
INSTALLING
You need init.d support for this!
Download and flash:
http://www.androidfilehost.com/?fid=9390248398092764755
Here is a mirror... http://d-h.st/REX
How to use this script?:
After flashing, launch terminal emulator and type
Code:
su
seeder
You will get a menu like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE: There will be NO app after flashing! This only installs the necessary binaries and scripts...
For those who cannot install via recovery:
You get a status 0 error -> replace the update-binary in Seeder_v6.zip with one from another zip that works with your device
OR
Use the new installation method!
Instructions:
1. Download Seeder_v7_non-CWM.zip from here:
http://www.androidfilehost.com/?fid=9390248398092764756
2. Extract the zip, you will get a folder named "install"
3. Place the folder in the root of your sdcard (/sdcard)
4. Launch terminal emulator, type:
Code:
su
cd /sdcard/install
sh install.sh
5. Ignore any error messages (those are only warnings, only happens to current users)
6. You are done! The script will auto-delete the "install" folder as it is not required anymore...
Sample output:
UNINSTALLING:
And now for the way to clean up Seeder_7:
Via recovery:
Flash Seeder_v6&7_Uninstall.zip:
http://www.androidfilehost.com/?fid=9390248398092764753
Via terminal:
1. Download Seeder_v6&7_Uninstall_non-CWM.zip:
http://www.androidfilehost.com/?fid=9390248398092764145
2. Extract it to the root of your sdcard (/sdcard), you should get a file named uninstall.sh
3. Launch terminal emulator and type this:
Code:
su
cd /sdcard
sh uninstall.sh
4. You are done! Everything gets cleaned up, including uninstall.sh...
Click to expand...
Click to collapse
Flash now works, you can now type in terminal to turn off/on and also easier remove. Up to u if ud like to try. Note" it may drain battery more" so please do not be going all against tweak. Thanks
FLASH THIS ON GINGERBREAD!?!?!(v1.4.0)
Thanks to Zen Arcade for making a flash for Gingerbread! His Post Here!
I took a look at the original CWM package and made the following changes:
1 - swapped in our update-binary
2 - changed the mount command in edify script (not really needed since system is already mounted in gb voodoo CWM recovery)
3 - removed all mount commands from init.d script (not required since you have to have /system mounted just to read the script)
Here's a link to the CWM flashable: http://d-h.st/Kaq
I'm running this on both my Infuses - no problems noted. At work now so will not have a chance to try with games for a couple more hours at least. Only down side I can note is that the rngd binary is about 1MB in size - a small sacrifice if it does eliminate lag events
Note that this package is for GB, but should work fine for 4.x roms as long as /system is mounted as part of recovery startup. Can someone test on a 4.x (CWM9/10) rom by flashing the zip and then checking /system/etc/init.d for a file named 91RNGD or /system/xbin for rngd? I've already tested on GB and it works fine there.
Thanks bradman for posting this - all credit and thanks to the original devs who posted this.
Click to expand...
Click to collapse
Sorry if this is a n00b question, but if you just install the .apk do you still need to change the permissions or does it take care of it for you?
dginsd said:
Sorry if this is a n00b question, but if you just install the .apk do you still need to change the permissions or does it take care of it for you?
Click to expand...
Click to collapse
Is best to just fix Perm to brr safe, easiest way to do so if you just install the app is to go to recovery/advanced/fix permissions and reboot
Sent from my SGH-I997 using xda premium
I stumbled upon this myself a few days ago and have been looking into it... I can easily implement it into my source builds, but want to see how it reacts first before doing so. And btw bradman... CM10.1 is smooth as **** with nothing needed... but if this makes it even better, then thats good to hear.
Anyone tried this on 2.3.6?
im aware its smooth good job! i was just testing it on infuse and i currently had ur rom so i just gave it a try to confirm it working on infuse
wawaweewa said:
Anyone tried this on 2.3.6?
Click to expand...
Click to collapse
ive heard it works on gingerbread. never tried. try a backup in recovery then flash. if anything goes wrong restore
bradman117 said:
ive heard it works on gingerbread. never tried. try a backup in recovery then flash. if anything goes wrong restore
Click to expand...
Click to collapse
I updated OP so that if flash doesn't work i have download files to manually do
bradman117 said:
ive heard it works on gingerbread. never tried. try a backup in recovery then flash. if anything goes wrong restore
Click to expand...
Click to collapse
that is what i am doing now! im on saurom jvu atm thanks for the quick reply ill let you know how it turns out
EDIT: i hope it works so my online game will run smoothly!
I must say, this relatively minor tweak provides a noticeable boost. I'm currently using Liquid Smooth RC9.11 with no further tweaks. After applying this tweak I've noticed faster loading times for a couple games, Google maps is much more responsive to massive view changes, web browsing is snappier, and as stated above almost no redraw delay when returning to the launcher after running a large app (like a game). I must say this under-powered and under-RAMmed little Infuse just keeps getting better and better thanks to all the work the devs here. Keep up the good work!
deathblade said:
Is best to just fix Perm to brr safe, easiest way to do so if you just install the app is to go to recovery/advanced/fix permissions and reboot
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Thanks for the tip
dginsd said:
Thanks for the tip
Click to expand...
Click to collapse
so i just have to flash the zip in recovery then fix permission and that's it?
just flash it will do permission
Working CWM Flashable for Infuse GB
I took a look at the original CWM package and made the following changes:
1 - swapped in our update-binary
2 - changed the mount command in edify script (not really needed since system is already mounted in gb voodoo CWM recovery)
3 - removed all mount commands from init.d script (not required since you have to have /system mounted just to read the script)
Here's a link to the CWM flashable: http://d-h.st/Kaq
I'm running this on both my Infuses - no problems noted. At work now so will not have a chance to try with games for a couple more hours at least. Only down side I can note is that the rngd binary is about 1MB in size - a small sacrifice if it does eliminate lag events
Note that this package is for GB, but should work fine for 4.x roms as long as /system is mounted as part of recovery startup. Can someone test on a 4.x (CWM9/10) rom by flashing the zip and then checking /system/etc/init.d for a file named 91RNGD or /system/xbin for rngd? I've already tested on GB and it works fine there.
Thanks bradman for posting this - all credit and thanks to the original devs who posted this.
UPDATE - 2012/01/03
I've confirmed the documented improvement in speed at which Maps re-tiles the map display when making big location changes. Still testing other apps. Some games appear a big less laggy, although some disruptive lag events still occur (I suspect due to file system i/o scheduler delays rather than from lack of random/entropy data as addressed with this enhancement). I'll do some benchmarking over the weekend and report back with results.
Zen Arcade said:
I took a look at the original CWM package and made the following changes:
1 - swapped in our update-binary
2 - changed the mount command in edify script (not really needed since system is already mounted in gb voodoo CWM recovery)
3 - removed all mount commands from init.d script (not required since you have to have /system mounted just to read the script)
Here's a link to the CWM flashable: http://d-h.st/Kaq
I'm running this on both my Infuses - no problems noted. At work now so will not have a chance to try with games for a couple more hours at least. Only down side I can note is that the rngd binary is about 1MB in size - a small sacrifice if it does eliminate lag events
Note that this package is for GB, but should work fine for 4.x roms as long as /system is mounted as part of recovery startup. Can someone test by flashing the zip and then checking /system/etc/init.d for a file named 91RNGD or /system/xbin for rngd?
Click to expand...
Click to collapse
I currently cant test this but if it turns out to work ill put it on OP. i did hear from someone that the biggest difference on GB but i cant say that for y self because i have not tried yet
I gotta say, it's very smooth so far.
Works fine on Scott's CM10. PS shows the rngd process running. Thanks
Zen Arcade said:
Note that this package is for GB, but should work fine for 4.x roms as long as /system is mounted as part of recovery startup. Can someone test on a 4.x (CWM9/10) rom by flashing the zip and then checking /system/etc/init.d for a file named 91RNGD or /system/xbin for rngd? I've already tested on GB and it works fine there.
Thanks bradman for posting this - all credit and thanks to the original devs who posted this.
Click to expand...
Click to collapse
Sent from my SGH-I997 using xda premium
Heyyy Scott, check out this guys find
lordvincent 90 posted it..
Originally Posted by zeppelinrox
So I did a bit of digging and a bit of research and a bit of testing.
I really dunno if the tweak makes that big of an effect but I did discover a nice trick to have a nice fat entropy_avail with zero overhead.
One of the first pages I skimmed was http://linux.die.net/man/4/random which mentioned at the bottom these other files:
read_wakeup_threshold contains the number of bits of entropy required for waking up processes that sleep waiting for entropy from /dev/random.
write_wakeup_threshold contains the number of bits of entropy below which we wake up processes that do a select() or poll() for write access to /dev/random.
Normally, read_wakeup_threshold is 64 and write_wakeup_threshold is 128
I also wondered why most users report that their entropy_avail was by default in the 200ish range while mine was always by default over 300.
I had also found this page at linuxinsight. I had used that site alot when researching Kick Ass Kernelizer's sysctl tweaks.
So I thought, hey I wonder if I can use sysctl to set good values and low and behold, I looked in my script and I already have settings for both lol:
Code:
busybox sysctl -e -w kernel.random.read_wakeup_threshold=128;
busybox sysctl -e -w kernel.random.write_wakeup_threshold=256;
As you can see, I had doubled the default values - and that's why my entropy_avail was always over 300.
So I decided to mess with sysctl a bit.
Connected the phone to the laptop.
In one command prompt I watched the entropy_avail with this one liner:
Code:
while :; do cat /proc/sys/kernel/random/entropy_avail; sleep 1;done
In a second command prompt I did the sysctl thing...
I found that write_wakeup_threshold didn't effect entropy_avail at all.
But read_wakeup_threshold is a totally different story
I did
Code:
busybox sysctl -w kernel.random.read_wakeup_threshold=2048
The entropy_avail just started climbing....
All the way up to 3600+ and just stayed there. Never went down at all.
Actually, the more I did stuff with the phone, the faster the level would climb.
So it would never go down and would never get used.
I thought well maybe I should lower it so it does get used.
I kept lowering read_wakeup_threshold until it got down to 1200 and finally entropy_avail dropped to 2400+ and kept climbing until 3600 and then would drop to 2400 immediately and up again and so on...
I played with different values.
Setting it to 1000... entropy would go up to 3000 and then drop to 2000 and up to 3000 again....
Setting to 750.... entropy would go up to 2250 and drop to 1500 and up to 2250 again...
So the pattern is:
max entropy_avail=read_wakeup_threshold * 3
min. entropy_avail=read_wakeup_threshold * 2 (ie. read_wakeup_threshold * 3 - read_wakeup_threshold)
So it builds up 3 times the read_wakeup_threshold and then when it hits that limit, it drops the value of read_wakeup_threshold.
If you want to lock it it at the highest possible value (4096), you'd do:
Code:
echo 1366 > /proc/sys/kernel/random/read_wakeup_threshold
Or
Code:
busybox sysctl -w kernel.random.read_wakeup_threshold=1366
You can add either of those to any init.d script.
However, on my device, it won't go over 3600 so you can test for yourself how high yours will go.
If all you can get is 3600ish just go with 1200 (ie. 3600/3)
In Kick Ass Kernelizer I'm gonna make it like so:
Code:
busybox sysctl -e -w kernel.random.read_wakeup_threshold=1024;
busybox sysctl -e -w kernel.random.write_wakeup_threshold=2048;
That will make it bounce between 3072 max and 2048 min.
I'm making write_wakeup_threshold twice the amount of read_wakeup_threshold simply because that's what it is by default.
But hey, maybe I can save battery life if I make it 1280 just so it stays locked in at 3600+ and it doesn't have to keep rebuilding entropy_avail lol
So conclusion is: since there is a definite pattern on how entropy was being built up to a pre-determined level and dropped to a pre-determined level, it wasn't actually being used. That's just how it's programmed.
If the setting isn't there to "hold" all the entropy, it just drops/flushes it and force feeding it entropy won't make it not spit it out
So at least I found the setting that will make it hold it in lol
Maybe somebody would like to give it a try and test to see if it actually saves battery by setting read_wakeup_threshold to 1366.
Click to expand...
Click to collapse
lordvincent 90 posted it..
Just adding this, after reading the whole thread here it seems like this may be a simpler solution (and better on battery life)
Click to expand...
Click to collapse
Post Link -- http://forum.xda-developers.com/showpost.php?p=36208713&postcount=32
Zen Arcade said:
I took a look at the original CWM package and made the following changes:
1 - swapped in our update-binary
2 - changed the mount command in edify script (not really needed since system is already mounted in gb voodoo CWM recovery)
3 - removed all mount commands from init.d script (not required since you have to have /system mounted just to read the script)
Here's a link to the CWM flashable: http://d-h.st/Kaq
I'm running this on both my Infuses - no problems noted. At work now so will not have a chance to try with games for a couple more hours at least. Only down side I can note is that the rngd binary is about 1MB in size - a small sacrifice if it does eliminate lag events
Note that this package is for GB, but should work fine for 4.x roms as long as /system is mounted as part of recovery startup. Can someone test on a 4.x (CWM9/10) rom by flashing the zip and then checking /system/etc/init.d for a file named 91RNGD or /system/xbin for rngd? I've already tested on GB and it works fine there.
Thanks bradman for posting this - all credit and thanks to the original devs who posted this.
Click to expand...
Click to collapse
Anyone tried this?
Btw brad im on jvu saurom and flashed it fix permission but this is what i get
Tweak
This relatively minor tweak provides a noticeable boost. I'm currently using Liquid Smooth RC9.11 with no further tweaks. After applying this tweak I've noticed faster loading times for a couple games, Google maps is much more responsive to massive view changes, web browsing is snappier, and as stated above almost no redraw delay when returning to the launcher after running a large app (like a game). I must say this under-powered and under-RAMmed little Infuse just keeps getting better and better thanks to all the work the devs here. Keep up the good work!
BR
Hey everyone!
I've been trying to get a custom kernel working on my S21 Exynos. I am able to build but I cannot get it to be stable.
When the phone is in the lock screen, after a minute or so it will reboot and checking the log, there is a kernel panic.
Here's what I've done :
Got boot image from device with DD and extracted with AIK.
Built latest kernel with these settings (G991BXXU3AUIE) :
build_kernel.sh :
Bash:
#!/bin/bash
export ARCH=arm64
export PLATFORM_VERSION=11
export ANDROID_MAJOR_VERSION=r
export LLVM=1
export CROSS_COMPILE=/home/kali/Projects/Toolchains/aarch64-linux-android-4.9/bin/aarch64-linux-android-
export CLANG_TRIPLE=aarch64-linux-gnu-
make ARCH=arm64 exynos2100-o1sxxx_defconfig
make ARCH=arm64 -j16
arch/arm64/configs/exynos2100-o1sxxx_defconfig modification (So I can set selinux permissive in runtime) :
Code:
CONFIG_SECURITY_SELINUX_DISABLE=y
security/selinux/Makefile modifcation (Allow selinux to be set to permissive) :
Code:
ccflags-y += -DCONFIG_ALWAYS_ENFORCE=false
Thats the only thing I have changed just so I can disable selinux for use with frida framework for memory hacking.
After replacing the stock image from extracted AIK with custom one, repacking with --origsize I tar it and flash with odin in download mode.
I then go into twrp, wipe cache and dalvik. (I have tried many full factory resets, just not worth the hassle when trying to figure out what is causing this)
I boot into my phone and things seem normal. Then I lock my phone or let it lock itself then after 30 seconds to a minute, the phone will reboot with a kernel panic and for the life of me I cannot figure out the cause.... Why isnt the samsung firmware working? All it has is the option to use setenforce.....
I have also tried to disable "panic on oops" but it doesn't seem to work, other than delay the inevitable.
Also every time I switch between stock and custom kernel, I be sure to delete the passcode and fingerprint lock to prevent weirdness.
Also reguardless if magisk is installed or not, it still happens. Same thing with having a passcode enabled, same thing will always eventually happen.
Can someone please try and make sense of my kernel log to see what is causing the error?
Im fairly new to kernels . . .
I have attached my last_kmsg.
Thank you in advance
https://ghostbin.com/bYNJO
link for kernel dump just in case you cant see attached file ^
Indica0 said:
https://ghostbin.com/bYNJO
link for kernel dump just in case you cant see attached file ^
Click to expand...
Click to collapse
Don't understand any of this... but I have s21 ultra rooted and willing to try kali, as I use it on desktop, and wold be useful to have a portable one... if for some reason you find more please say... and if you need some help within my limits I'm here