yashsingh1/xdaforums huggingface dataset:
[Acer Iconia A500] HD87:
Mine takes 2 mins & 30 seconds.

Starting count during vibration when initially powering on, through the splash screen & boot animation, ending count when the lock screen comes on.

How long does it take yours?
[Acer Iconia A500] synapses11:
Wow really that long? I just tested it. It was exactly 1 minute from power up to lock screen.
[Acer Iconia A500] erica_renee:
humm .I have never turned.mine off other then going into recovery. So no big deal to me.guessna minute or so
[Acer Iconia A500] shabushi54:
It was exactly 1 minute
[Acer Iconia A500] kjy2010:
42.39 seconds timed with the stopwatch on my phone, vibrate to unlock screen.

To the OP, I'm not sure it should take 2 minutes too boot?!?!?

:eek:
[Acer Iconia A500] HD87:
Yeah thats why I posted this thread.. Im running custom 3.2, richardtrips 3.4 kernel, got bout 1 gig of space left on the internal SD card.. What can cause the boot time to be so long?
[Acer Iconia A500] kjy2010:
1Gb space left?!?!? What the heck do you have on your tab. I've got tons of apps and have 11.59Gb free.

If a lot of it is music, movies, etc., you might want to store them on your external? Just a suggestion. ;)
[Acer Iconia A500] bazzan:
Boot up with same set up

Running the Taboonay 2.0 (Android 3.2) and richardtrips 3.4 kernel. Get to the lock screen in 52 seconds. Have 9.51 GB of space left. Maybe not the same ROM. Which custom 3.2?
[Acer Iconia A500] sensei22:
I have a similar issue, mine takes more than 2 minutes and using stock 3.2 ROM, no mods or anything. Does anybody think his can be caused by an installed app?
[Acer Iconia A500] godashram:
I have the same issue, with about 2gb free... Doesn't really bother me though

Sent from my PI39100 using Board Express
[Acer Iconia A500] TLSS:
All the bloatware that comes installed stock on the tab slows it down considerably. What many custom roms do is rip out a lot of the bloatware so there are less running services, which means both a smoother experience while turned on, and faster start-up/shutdown times. Which is why you see some people getting sub-1 minute boots.

@op, what custom rom are you using? You stated that you're using a custom kernal, but if it's not made for the rom you're using, then you can run into problems, a longer boot time more than likely being one of them.
[Acer Iconia A500] timmyDean:
Yes, you are starting something that is causing your problem. However, I would suspect it's something outside the normal apk applications. Normal apk applications are forced to timeout after so many seconds and killed by the engine. So, something taking too long to load normally is killed and you are shown an error about the program. Since you're not mentioning seeing errors, I would suspect an application outside the normal user interface. Just a guess.

In the past, I've seen this were the Linux kernel is trying to init hardware you don't have which waits for a timeout to occur.
[HTC Sensation] Dekr:
My sensation has a low voltage current running through the cover while charging. When holding the device while plugged in you get "shocked" (its better described as a tingly feeling). I did not have this problem before but i first noticed it after i got my sensation fixed by Vodafone. I send it in for repair and i don't know wat the exact problem was but they replaced the whole motherboard.

Does anyone have or had the same problem or have any ideas what i could do about it because i don't really want to sent it in again after last time when i had to go without my phone for 3 weeks.
[HTC Sensation] Gunkk:
Charger is probably defective. AC current should never get to the phone, but is coming in thru the ground in the charge cable.

Sent from my Bricked Energy ROM Sensation.
[HTC Sensation] anarchyuk:
or as the antennas are in the back cover this could be another issue?
[HTC Sensation] The_Worst:
I have the same issue when I charge the phone with a 3rd party dock. I can't remember having the issue with the AC charger. I'm going to test this tomorrow. However, I don't see this as a problem.
[HTC Sensation] Dekr:
I dont think it is the charger because it also accurs when charging via my usb port on my laptop with a different cable. Its just so weird lol:D.

Maybe it is indeed the antennas. I will try with a backcover of the sensation of a friend of mine, when i have the chance, to see what happens. It is not really a big problem but i'm worried this will lead to other problems.
[HTC Sensation] naimmkassim:
I also facing the same problem since beginning of buying this sensation. I'm using the stock charger that come with the phone. I think this is normal. Its happen to all my phone before (HD2, Desire, DHD and now sensation).

:D

No others side effect happen from this tingly feeling to the phone.
[HTC Sensation] xaccers:
Stock psu provides 5V DC.

One suggested solution is carefully bend up the silver contact on the back of the phone.
[HTC Sensation] awesam:
yes bending the contacts works, and you're good with soldering iron try putting some solder on the housing itself to give full contact to the back housing. works for me and there's a thread on this (with pictures too) try a search for that thread
[HTC Sensation] raybez:
I get it too charging via USB. Its like a static shock in the wintertime when you scuff your shoes on carpet and touch a doorknob.

I don't really think its a problem, but energizing to say the least.
[HTC Sensation] T-Macgnolia:
This issue may be due to it being repaired, I mean everyone has an off day and makes a mistake. But also you are not the first person that has posted noticing the tingling sensation you get when you are charging your Sensation either. So who knows this could be yet another small problem us users are finding with the device, I have not passed judgment yet.

This is highly unlikely, most standard USB wall chargers do not have a ground prong to connect to insert into the ground terminal of a wall receptical. Also a USB cable only has two wires for power transfer. Meaning one is for the positive and one for the negative to complete the circuit. Not to mention if this was the cause the OP would not be complaining about getting a tingle, but of constantly having to re trip a breacker or replace a blown fuzz.
[HTC Sensation] apex84:
I don't get shocked if I touch the phone while it's charging but if I touch it with the dorsal side of my finger/hand there is a slight buzzing feeling, like a high frequency, low amplitude vibration. This only happens if I touch it with only one hand/finger. If there are more contact points, the buzzing feeling disappears. So when I pick up the phone the buzzing disappears.
[Nexus One Android Development] dla5244:
BlackRose

This is Nexus One custom bootloader(Based on HBOOT 0.35.2017)

Lecahel
[Nexus One Android Development] dla5244:
Supplement
[Nexus One Android Development] akirajds:
maybe its too early in the morning,.... but huh?
[Nexus One Android Development] Jack_R1:
It means - a hack that allows flashing anything anywhere as long as the hack is present. So, theoretically, if anyone would modify the bootloader code (done earlier in this thread, AFAIK) to allow bypassing security, this hack will allow flashing it. Also, possibly, this hack will allow flashing engineering bootloader.
[Nexus One Android Development] blunden:
Impressive! A really interesting approach. Even though Radio S-OFF would be preferred a modified hboot that unlocks more commands than the current stock-unlocked hboot does, right?
[Nexus One Android Development] dla5244:
Yes, we can do anything(except radio)

I found hidden functions during disassemble hboot

saveprt2sd, savemem2sd, mw etc...

i temporary changed oem lock function to saveprt2sd and it worked.

I found 0.33.2012 hboot(ENG) image

but since I use SLCD Nexus One, I couldn't flashing

Blackrose has potential
[Nexus One Android Development] dla5244:
Post Changed.
[Nexus One Android Development] maddie:
doesn't work, still fails the signature verification.
[Nexus One Android Development] rjmohit:
It doesnt work. It shows a 'failed' result, saying that the file couldnt be verified or something. I tried out three different hboots, including the one you've provided, but it shows the same error every time. :-/

EDIT: Works perfectly. Got an S-off. :-)
[Nexus One Android Development] maddie:
didn't see anything to bypass the signature verification during the process.. i thought the only way to let the bootloader accept the image is that the file itself has a valid signature? how can you flash the image directly then..? o_o
[Nexus One Android Development] dla5244:
mistake

OOPS, I made mistake.

I uploaded again.

Maybe this worked well...

Please report to me.
[Nexus One Android Development] maddie:
OK, it works now. Bootloader now S-OFF!

Great work! ;-)

BTW my Nexus One is unlocked.
[Nexus One Android Development] dla5244:
Congratulations!

also you can flash hboot, splash1, etc via fastboot flash command.
[Nexus One Android Development] maddie:
Yes, I'm aware of that. It's good enough for me to just get rid of the annoying lock icon on the boot screen. ;-)

And what is the gate.img exactly? I noticed that it was flashed as "boot" in fastboot, so I flashed my original kernel afterwards without booting into system. Will it in any way affect the original system?
[Nexus One Android Development] dla5244:
sorry my english.

No, 'fastboot boot' command not affect original system.

boot command means what copy kernel image to RAM and execute.

gate.img is exploit image(not kernel).

As soon as gate.img executed, it change bootloader codes on RAM

that's why you can flashed custom-hboot on stock hboot.
[Nexus One Android Development] maddie:
Your English is good enough to understand!

I see, I thought it was "flash" instead of "boot".

Thanks for your great work!
[Nexus One Android Development] intersectRaven:
Thanks for this! I now have S-OFF on my N1. I wonder if the MTD partitions could be resized now like in the Desire? Hmmm... :)
[Nexus One Android Development] daveid:
When I first saw this progress, that is what I was hoping would come of this...
[Nexus One Android Development] uoY_redruM:
Uh oh! IR has some ideas brewing...
[Nexus One Android Development] DeTool:
S-off success :D
[Nexus One Android Development] dla5244:
RADIO S-OFF

Maybe I am blocked last step.

almost code(AMSS on,MMU control,Patch routine and address,send AT-CMD, etc) is perfect but disable MPU code.

even try to write byte on AMSS Code area in RAM, it failed due to MPU(actually).

Hmm...

test.

If you are radio s-off user, please test for me

(Don't worry, your phone is still safe)

First, enter shell (using adb shell,terminal emulator)

su

stop ril-daemon

echo -e 'AT@SIMLOCK=7,0\r' > /dev/smd0

Is your phone reboot after typing above command?

Thanks.
[Nexus One Android Development] gregferns:
After flashing Blackrose, it shows

Nexusone Pvt Eng S-Off

Want me to try your above commands ?

Let me know.

EDIT : -- No reboot. Nothing happened.
[Nexus One Android Development] cyberon:
I have a 30Mb cache partition, and today while downloading Angry Birds Seasons (22.05Mb), an error occurred, and the file who was being downloaded to cache, just got stuck there, even with a reboot.

When retrying the download, the phone kept giving me a "not enough space" error, the only solution was to wipe cache trough recovery.

My question to the devs is, how can we download anything bigger than 5Mb if we create a 5Mb cache partition as seen on CM7/r2?

Thanks.
[Nexus One Android Development] maxib123:
mine does reboot yeah
[Nexus One Android Development] DeTool:
Put your cache on sdcard.
[Nexus One Android Development] dla5244:
You must Full wipe(once).

Don't restore nandroid.

My cache size is 5mb and downloaded apps(temporary) is located /data/local/download
[Nexus One Android Development] dla5244:
Is your n1 radio s-off?

Check '/' and '\'

Hmm. Thanks.
[Nexus One Android Development] dla5244:
Is your phone radio s-off(available relock bootloader)?

thanks.
[Nexus One Android Development] efrant:
I have radio S-OFF, and after entering your commands, my phone does NOT reboot. Nothing happens after the echo -e command.
[Nexus One Android Development] maxib123:
no its is not
[Nexus One Android Development] dla5244:
Thanks
[Nexus One Android Development] dla5244:
Yes, not reboot is successful.

Now I confirm that the last step is disable mpu. :)

Thanks.
[Nexus One Android Development] sl8125:
Does it automatically move to /data/local/download?

I have 25 MB cache some apps won't install. I did the full wipe and install fresh copy if rom.
[Nexus One Android Development] efrant:
Excellent. Good luck, and great work dla5244!
[Nexus One Android Development] bwilliams1:
My phone did nothing.

# stop ril-daemon

stop ril-daemon

# echo -e 'AT@SIMLOCK=7,0\r' > /dev/smd0

echo -e 'AT@SIMLOCK=7,0\r' > /dev/smd0

#

Edit: sorry guess I should have looked up a bit.
[Nexus One Android Development] samarium:
CM7.1 has the following init script to deal with the small cache problem:

# cat /etc/init.d/06mountdl
#!/system/bin/sh
#
# bind mount /data/local/download to /cache/download if cache
# partition is too small
#

CACHESIZE=$(df -k /cache | tail -n1 | tr -s ' ' | cut -d ' ' -f2)
if [ $CACHESIZE -lt 20000 ]
then
mount -o bind /data/local/download /cache/download
fi

rm /cache/download/downloadfile*.apk >/dev/null 2>&1

exit 0
#

If you are using CM7.1 then you made cache too big to benefit from it's automatic work around.
[Nexus One Android Development] sl8125:
Got it Thx. I updated the blackrose and repartitioned and all good.

With blackrose and cm a2sd I don't need any script to apps to SD or such. It runs smoother without any script.
[Nexus One Android Development] gregferns:
Hi,

In which mode was the phone when you flashed the repartitioned HBOOT ?

Fastboot mode, recovery mode or normal mode ?

Thanks and sorry for the noobish question.

regards

greg
[Nexus One Android Development] cyberon:
Fastboot USB mode.
[Nexus One Android Development] houzuoguo:
I previously have unlocked bootloader, yesterday I flashed Blackrose HBOOT and noticed that lock icon disappeard when the phone is booted. I imagine that the lock icon appears if S-off, my bootloader is certainly not re-locked so I wonder if this is an expected behaviour?

Thanks.
[Nexus One Android Development] uoY_redruM:
I've been following this forever but I finally decided I want to do this.

I just want to get this straight before I do it.

-Do you flash the 0.35.2017 bootloader first? ( http://xdaforums.com/show...&postcount=116 ) If so, is that a flashable zip?

Then what?

Sorry for the noob questions, I followed so closely and thought I understood...but now that I'm trying to do it, I'm really confused as to what steps you take to flash the engineered bootloader.
[Nexus One Android Development] cyberon:
Yes it is, as written on the 1st post. ;)
[Nexus One Android Development] dla5244:
That was my intend.

Padlock show routine is disabled.

You can't see a padlock mark, even you are unlock user.
[Nexus One Android Development] cyberon:
You don't need to flash engineering HBOOT, if you are on 0.35.0017 HBOOT, just download the zip, unpack, execute BlackRose.exe then folow the steps.

Ps: i am assuming you have AndroidSDK installed.
[Nexus One Android Development] uoY_redruM:
I on HBOOT 0.33.0012

In that case, what do I have to do?
[Nexus One Android Development] dla5244:
No it's not a flashable zip.

There is no need to flash 0.35.2017 before install blackrose.

You must install blackrose on 0.35.0017

Edit: update hboot 0.35.0017 via flashable zip
[Nexus One Android Development] uoY_redruM:
Where can I find the hboot 0.35.0017 flashable zip? I don't see it in the OP...or am I over looking it?
[Nexus One Android Development] efrant:
You need to upgrade to 0.35.0017. Just download it directly from Google's server here: http://android.clients.google.com/packages/ota/passion/d6096cac5e9f.signed-hboot-0.35.0017.zip and flash it via recovery.
[Nexus One Android Development] uoY_redruM:
Perfect, thank you. I don't know how all this time I never noticed I never updated my HBOOT lol.

So then, after that, its as simple as hooking up to the PC via Fastboot mode, execute blackrose.exe and that's it?

Then, if I want to do custom partitions (which I plan on doing) just follow the steps in the OP using IRs application?
[Nexus One Android Development] uoY_redruM:
Cool, I got BlackRose HBoot now :)

About to do partitions. Was WAY easier then it seemed by reading it lol.

Thanks for the help everyone.

---------- Post added at 10:21 PM ---------- Previous post was at 09:42 PM ----------

I was wondering the same thing as asked a few pages back.

What is a good partitioning for an MIUI ROM?
[Nexus One Android Development] DeTool:
I just reduced my cache to 5mb and gave the rest to data. Worked like a charm for me. Didn't even need to wipe and reflash miui.
[Nexus One Android Development] samarium:
If I don't do a full wipe of CM7, I get a loop where system keeps trying to recreate /cache/dalvik-cache and runs out of space.

I found that I could get away making a similar kludge to /system/etc/init.d/06mountdl, do a bind mount of /cache/dalvik-cache into /data.

I'll post further instructions on how to do this after I let it run for a day.

Ideally I'd like to find out where /cache/dalvik-cache is saved in /data and change it, as that way I could get rid of the kludge and also would not have to arrange for it to be in the custom_backup_list.txt so it survives an upgrade.
[Nexus One Android Development] intersectRaven:
This is controlled in CM7 by the verify_cache_partition_size.sh file in system/bin directory. :)
[Nexus One Android Development] dla5244:
Maybe you are right. :)

In CM7

Dalvik-cache script = /system/bin/verify_cache_partition_size.sh

Download folder script = /system/etc/init.d/06mountdl

As you know, when rom update, verify_cache_partition_size.sh is executed.

this script is that if cache size less then 60mb, execute "setprop dalvik.vm.dexopt-data-only 1" and if above value is 1, dalvik-cache is stored in data partition.

I will say again for everyone.

I don't confirm that this script is executed when rom update only, but to avoid possible problem, I recommand full wipe before first boot.
[Nexus One Android Development] pckeung:
How to remove the lock watermark on the bootscreen?
[Nexus One Android Development] samarium:
If you are running blackrose hboot then it chooses not to display the lock watermark.
[Nexus One Android Development] samarium:
I just finished some testing.

Once /system/build.prop contains dalvik.vm.dexopt-data-only=1 then on boot CM7.1 places system and data dalvik-cache in /data/dalvik-cache.

It doesn't matter how build.prop is updated. I updated manually using /system/bin/verify_cache_partition_size.sh, and I also updated by reloading my current CM nightly, either way build.prop got updated and the phone booted OK. When you load a CM7.1 update zip, build.prop gets reloaded from the zip, and then updated by /system/bin/verify_cache_partition_size.sh.

Much better than my interim kludge of /system/etc/init.d/07mountdc like 06mountdl.

My process for repartitioning and restoring CM7.1 went like this:

0 ensure you have the appropriate zip file on your sdcard for the version of CM7.1 you are currently running.

1 prepare blackrose hboot with your preferred partition map. I just used the standard of leaving system untouched, shrinking cache to 5M, and giving the rest to data.

2 boot into recovery and make a nandroid backup

3 install blackrose hboot / partition map

4 boot into recovery

5 wipe cache

6 wipe system and install zip from sdcard of same CM7.1 update as you were running. Alternatively, if system size didn't change mount /system R/W and manually execute /system/bin/verify_cache_partition_size.sh, which would be quicker than installing the update.

7 wipe data; restore data

8 reboot

I've run this and a couple of variants, and my phone boots OK.

FYI adb logcat shows you the dalvik-cache rebuild happening while the boot animation is running, it also showed me the dalvik-cache generation loop when I didn't update build.prop.
[Nexus One Android Development] daveid:
Only one question, and I apologize if it has been addressed - I have tired to follow the thread closely, what about the Market's download cache? As I was waiting for a wipe-free method, and knew it would surface ...
[Nexus One Android Development] intersectRaven:
The market cache in /cache/download is controlled by 06mountdl. As long as it's less than 20MB, it will remount it in /data. :)
[Nexus One Android Development] uoY_redruM:
Sorry to back track a little, but when it comes to custom partitions, a 5MB cache all the rest to data is safe to use? I've seen a few people say that's what they use.

I want to make sure if I start exploring ROMs again outside of one developer, I won't screw something up only having 5MB cache.

(145/5/286)
[Nexus One Android Development] intersectRaven:
I've recently converted to the 5MB cache thing and it seems to work fine. Having a bit of a problem with Market downloads stalling after pressing install but before being shown the accept privileges page but it might just be a Market quirk. :)
[Nexus One Android Development] uoY_redruM:
I've not changed my partition at all yet, and I've noticed this as well the last ~2 days with it stalling. Probably is a Market quirk.

Thanks for the response, IR. Time to try this thing out, hopefully all goes well.

---------- Post added at 08:32 PM ---------- Previous post was at 08:25 PM ----------

One last question.

Do you place the custom partition on your SD card, or keep it on your PC?

Also, do you boot into Fastboot to flash the custom partition?

fastboot flash hboot /sdcard/

Would be the command to input if the custom partition is placed on the root of the sdcard?
[Nexus One Android Development] DeTool:
Reboot into bootloader. All files remain on pc. Fastboot looks for the files in the directory you're running it from.

I ended up using a 50 mg partition for cache as the market did need to use it... I'm on Miui.us rom.
[Nexus One Android Development] efrant:
I don't want to sound unhelpful, but if you are asking those questions, I would highly recommend that you do a bit more reading before messing around with custom partitions.

In any case: to use fastboot commands, your device needs to be booted in fastboot mode. And yes, the hboot file needs to be on the computer.

If you want to flash partitions via an adb shell instead of fastboot, you need to use a utility called flash_image, and the command would be flash_image hboot nameofyourhboot.img
[Nexus One Android Development] uoY_redruM:
The issue I'm having is I've never used fastboot. I always did everything through terminal and adb. I didn't have SDK on my PC anymore, so I reinstalled everything. When I go to my bootloader and click fastboot it changes on my phone to show fastboot USB but my PC reacts in no way at all. I'm confused as to where I type in the commands when nothing is happening.

I have flash_image on my phone (flashable zip) as like I said, I did everything through terminal emulator...but its telling me its no longer supported and install is aborted when trying to flash flash_image.zip (never seen that before, I'm assuming maybe its because of the new recovery I'm using).

So, I'm stuck right now.
[Nexus One Android Development] MaDInDy:
On your PC, typing command "fastboot devices" for check list connected devices.

If your phone connected, You will see your phone's serial number.

So, you can't see your phone's serial number. try check fastboot.exe path in sdk and reinstall android usb driver.