|Latest product reviews|
Damo, here is a new boot.img. If you cant get Market working try this one.
You should only have to flash this not the other stuff. Sorry it does not have your boot image but if it solves your problem I will make you a new one.
Let me know when you have downloaded it so I can delete it.
So the new boot.img worked no problem then?
OK I am going to leave out Admins idea of writing a ID to IMEI file.
Can you please test boot time for me?
THIS WAS MY ORIGINAL TEST ON FRESH INSTALL OF ROOT 1.2
Go Launcher Ex V2.70
Swiftkey Tablet X
Generic Grass live wallpaper
This gave me boot time of 48 seconds.
TEST ON ROOT 1.2 WITH NEW PERIMETER FILE 1GB SYSTEM STORAGE
Same apps as above fresh install
This gave boot time of 41 seconds.
I ran 3 boots in the test and the times where as follows
I think Android boot time is a bit up and down, but with all them Apps installed I have 879MB of internal storage space left!
Been A Windows man like yourself I am so used to disabling Programs and services and have done for years to speed up boot time, and if I ever had a problem than I would install a boot logging program to see exactly Is running and how long it takes. Android is a whole new thing, and I find it ridiculous that the boot time increases every time you install something and these programs that say that they disable them, they just dont make any difference. I installed one program that showed you what processes run with a program at boot and for some it was crazy, Google plus for example had about twelve separate processes that run on boot so it is no wonder that the boot process is poor. And daft things like the media library getting updated every time you boot does not help.
Anyway my Windows 8 developer boots in less than ten seconds so I am glad Android is not my main device, well it my daughters but I love to mess on it.
Anyway enough ranting it is still great once it has booted
I am running the custom rom 1.1 and I am now having issues. I keep getting force close error messages for the Android framework. Is this a known problem? Also ihave seen posts about a 1.2 version. is there a newer version out there. If so can it be just flashed to the existing setup or does it have to be installed like the custom firmware. If I continue to have issues how do I revert back to the original firmware, I have kept a copy of it on my pc.h
Going to bed now.... Here is the bummer.
I cannot seem to make a update.img that works even using the RK tools or Wendals tool. So it turns out this is not a Wendal tool issue. It looks like its the AFPtool (comes with the RK29 kit) issue. The stock RK29 tools and Wendals tool uses the RK29 AFPtool to pack the update.img. When thats done then the loader is handled and a MD5 checksum and the final update.img if finished.
Alas, the update.img hangs just like before. However if I flash using the RKAndroid tool 1.29 using all the same files, no issues. So to me it appears the AFPtool will not pack this update using the edited boot.img and system.img.
I think the issue is the boot.img when it is repacked is not 100% correct. Remember I am using some tips I read on how to unpack and repack the boot.img. Anyway I think the repacked boot.img and the AFPtool is having some compatability issues. I remember a few days ago I read about boot.img having a footer on it and people said it was not needed. I do not believe I am rebuilding that footer and it is missing thus screwing up AFPtool's ability to repack a proper update.img.
Anyway I will work on this more but it may be my rom comes out with having to use the RKAndroid tool which means people will have to install the drivers to get into "flash" mode. My thoughts are so what! as they should have the drivers installed anyway incase they need to recover! Look how many posts are about just that! A bad flash and having trouble getting the drivers installed to go into "flash" mode. Maybe first having the drivers installed and working before you update will save some people some grief if they need to recover.
Well it will be what it will be but I will try to make a update.img that works so people that are lazy don't have to worry about drivers 😉 No gaurentees but I will try.
Hello Bob, have finally found a way to make an update.img starting from ext3 system.img?
I have your same problem 🙂
Most Users Ever Online: 749
Currently Browsing this Page:
Devices in use: Desktop (99), Phone (4)
Guest Posters: 43
Moderators: globula_neagra, exelletor, JochenKauz, Oma7144, cracktech