Related
Hello all . . . need I say it? But, I'm new. Not just to this forum, but also to pda/smart phones.
I got an O2 XDA Mini S yesterday and began playing. Firstly, quick basic question, are all these the same thing:- i-mate, K-JAM, HTC Wizard and O2 XDA Mini S?
OK, next, I've been reading some sites today and one of the most repetitive things I've found is the recommendation to remove the O2 software from my device - on the basis that it is causing it to run slowly. But, I haven't found that to be the case, but remember I'm new to these toys.
I also came across Magic Button for closing apps properly, not just hiding them.
Lastly, before I move on to the subject of this post - can someone clarify the difference between a hard reset and a soft reset. In particular, if I do a hard reset, do I loose eveyone from my Contacts?
But, here is the question that relates to the subject:-
I turned on bluetooth and tried to send a picture from a Samsung D500 to the XDA Mini, but no luck. I also tried with a Samsung E720, no luck there either. Lastly, I also tried with an Apple PowerBook G4 and it was unsuccessful also - but it was more informative - it basically suggested that the capability didn't appear to be there.
I did turn on bluetooth on all the devices and I also made the XDA Mini discoverable. The two phones could scan and find the XDA, as could the Apple, but neither of the phones could retain the name of the XDA in the list of previously identified devices (I hope that is clear what I mean). The Apple could retain the name, but still can't interact with it.
I have tried changing the COM ports round - ie COM 7 incoming COM 6 outgoing AND COM 6 incoming and COM 7 outgoing, but that didn't make any difference.
The most bizzare thing (not really all that bizzare I suppose) is that Infra-Red works, so I could transfer stuff (albeit awkwardly) from my old phone to the XDA.
I was wondering (probably stupidly) if the 02 software could be limiting the functionality associated with the bluetooth, or if Windows has restricted it to only be used with ActiveSync [I just can't think of any other reason for it not to work].
Any light that could be shed on this would be appreciated.
Cheers.
1. Yes they are all the same things.
2. The o2 software tends to be quite animated, this slows down the device a little, it also masks the way the phone was intended to be used. Its not really necessary which is why its best to remove it. Plus, it free's up memory for other stuff.
3. There is a lot of talk on these forums about different programs that can "really" close an app as opposed to "minimising" to the background. There are "for's" and "against" arguments regarding this. It is true that programs only minimise when you press the "x" button but it does state, er, somewhere, i think it was in one of the help files in the device, that memory is managed automatically by windows and that programs are shut automatically to make room for new ones if memory becomes low. So you shouldn't have to worry about running out of memory, also when minimised the programs appear quicker than if they had been shut down, usually from where you last were too. This can be a good or bad thing depending on the point of view of the user. However, from my point of view and i think i share this with many other users, i "feel better" knowing that a program shuts when i've finished with it and it will start from a common point when i next open it. I think this is more down to the fact that people are used to this than anything else.
The program i use for this purpose is called SmartSkey, made by one of the people on this forum,it can do either and you can have an exception list of apps that minimise only, which is quite useful. Also it makes navigating the device easier with one hand, which is REALLY handy, it may be worth looking into.
4. A hard reset will make your device appear exactly how it did when you first switched it on. Anything at all that was on there will be gone, so yes you will lose your contacts. There are 3rd party applications you can use that can back up the whole device though. A soft reset just restarts the device and nothing is lost. Its equivelent to restarting a windows PC as opposed to Re-formatting one.
5. As regards you bluetooth problem, the only thing i can think of is that i have noticed that the device needs to actually be "ON", not in "sleep mode" or obviously "OFF", in order to successfully receive files via bluetooth. If it is in sleep mode then devices can see it but can't connect. I can honestly say i've had no problems as you describe with bluetooth names and stuff on mine.
Sorry i can't help you more with the bluetooth, but i hope the other info was of help to you. Enjoy your new toy, they are very customisable and as a result of which can be very annoying too. :wink:
Be prepared for late nights and hair loss, else, ignorance is bliss
Thanks for the reply Clivectmob. Very informative.
I've been playing again. This time I sent a picture from the XDA to the Samsung E720 and I was successful, but it doesn't seem to want to work the other way around . . . very strange.
I might bring it back and see if they can figure it out.
If anyone else fancies a shot at a solution, just fire away, I'll take any suggestions.
Again, thanks Clivectmob
Last question.
If I take the O2 software off of this, can I return it to factory settings by doing a hard reset?
Yes you can, as I said, it will be as it was when you first switched it on.
All that software is stored on a hidden ROM on the device, when you hard reset it goes through a customization sequence afterwards where it puts it all back on. One trick is to wait until it displays the customization message, then pull out the battery. Switch back on and it will not customize it, but then you need to manually configure all your conection settings and so on, so you need to be reasonably up on the use of them for that.
Hi Guys
Been having the usual "Turn on" problem with my TyTN since having it, you know, very occasionaly - maybe once a week - you try to turn it from the button on the side and it wont. No matter what you do it stays off and you have to soft-reset.
Well, over the past few weeks its been getting MUCH worse. Im now resorting to rebooting the phone maybe 8 or 9 times a day! I have tried various diferent ROMS and the same issue keeps occuring. I've also checked the ROMS threads to see if anyone else has had this problem as severe as me and they haven't.
I REALLY like my TyTN and don't want to be forced into buying a new phone with the Ultimates just down the roads.
Any ideas???
Thanks in advance!
-------------------
Current build (remember, tried with a few diferent ROMS):
Crossbow Prof
CE OS 5.2.1236 (build 17741.0.2.1) = LVSW build
ROM: 3.30.0.1
Date: 17/4/07
Radio:1.41.00.10
Proto: 32.74.7020.18H
Monty Burns said:
Hi Guys
Been having the usual "Turn on" problem with my TyTN since having it, you know, very occasionaly - maybe once a week - you try to turn it from the button on the side and it wont. No matter what you do it stays off and you have to soft-reset.
Well, over the past few weeks its been getting MUCH worse. Im now resorting to rebooting the phone maybe 8 or 9 times a day! I have tried various diferent ROMS and the same issue keeps occuring. I've also checked the ROMS threads to see if anyone else has had this problem as severe as me and they haven't.
I REALLY like my TyTN and don't want to be forced into buying a new phone with the Ultimates just down the roads.
Any ideas???
Thanks in advance!
-------------------
Current build (remember, tried with a few diferent ROMS):
Crossbow Prof
CE OS 5.2.1236 (build 17741.0.2.1) = LVSW build
ROM: 3.30.0.1
Date: 17/4/07
Radio:1.41.00.10
Proto: 32.74.7020.18H
Click to expand...
Click to collapse
The problem is you have told us nothing about what is running whether you leave it to sleep by itself what's on the today plugins whether you have active sync turned off (ie set to manual) etc etc etc and which of the freezing fixes you have tried. Whether your plugins are on sd card whether it freezes with sd card not inserted etc etc.
Mike
right o' ... get your laughing gear round this
I let it "sleep" itself.
Im running:
Activesync (Exchange push mail - no pattern discovered with regards to receiving new emails)
SPB Weather (Today plugin)
Everything else is standard.
Connecting over 3g/HSDPA
There are other apps installed but these are always "closed" after being used. All apps are installed to the phone memory and not SD card - i've never tried without the card, guess I will try this now! Although, if this is the problem, how do I get around it???? I need my card.
Monty Burns said:
right o' ... get your laughing gear round this
I let it "sleep" itself.
Im running:
Activesync (Exchange push mail - no pattern discovered with regards to receiving new emails)
SPB Weather (Today plugin)
Everything else is standard.
Connecting over 3g/HSDPA
There are other apps installed but these are always "closed" after being used. All apps are installed to the phone memory and not SD card - i've never tried without the card, guess I will try this now! Although, if this is the problem, how do I get around it???? I need my card.
Click to expand...
Click to collapse
Well I can see why you kept those things secret. If someone asked me to compile a list of things more or less guaranteed to cause freezing and refusal to turn on, I think I'd give 'em a link to your setup!!
If you must have push mail (that requires active sync to be active) and weather applications then you will likely continue to have problems.
You may be able to reduce the number of them by NOT allowing device to sleep by itself. I have mine set to never sleep. However I do always use the on/off button when finished.
It's fine to have applications that require connection to internet and today plugins on main memory BUT others should be on SD card. The reason is that running low on main memory (and not even that low!) can cause freezing.
PIE can rack up loads of storage memory - can move storage to card.
Regularly run a third party clean out application.
Mike
PS. resisted the urge to get my laughing gear out. Think I was in shock actually. You could consider writing a "how not to setup your Hermes" guide.
mikechannon said:
Well I can see why you kept those things secret. If someone asked me to compile a list of things more or less guaranteed to cause freezing and refusal to turn on, I think I'd give 'em a link to your setup!!
If you must have push mail (that requires active sync to be active) and weather applications then you will likely continue to have problems.
Click to expand...
Click to collapse
Why would these apps cause it to lock up? One comes with the operating system and one connects to the net once a day. Surley Outlook can't be that unstable as to cause lockups on average every two hours. I doubt SPB Weather is that unstable as well!
Yes, I must have push email. Why waste battery power polling every thirty minutes or so with pull email?
The memory card is going back in. I took it out, went to Sainsburys and BAM its locked again
I will now try the "no auto sleep" thing and see how that goes so thanks for that suggestion.
i had problems like these with my Tytn and eventually upgraded to WM6 (Black 2.5). It really made a difference. Much faster, never freezes and battery life is better.
Severe fix I know but worth considering
mikechannon said:
.....You may be able to reduce the number of them by NOT allowing device to sleep by itself. I have mine set to never sleep. However I do always use the on/off button when finished. .......
Click to expand...
Click to collapse
TOTALLY agree with you there Mike. I was having some real issues with the "coma" effect once the device has automatically gone into sleep mode, this wa admittedly on the original HTC ROM, and was caused by pocketzenphone however since I have (without fail) set the device to NEVER switch off automatically and have got into the good habit of using the on/off button liberally.
warmkiwi99 said:
i had problems like these with my Tytn and eventually upgraded to WM6 (Black 2.5). It really made a difference. Much faster, never freezes and battery life is better.
Severe fix I know but worth considering
Click to expand...
Click to collapse
See my orginial post Crossbow
It has! Sadly though it was still "sleeping".
However, i have taken it out of auto sleep and put it to manual, guess what .... been a couple of hours now and NO lockup! Yay!
Monty Burns said:
Why would these apps cause it to lock up? One comes with the operating system and one connects to the net once a day. Surley Outlook can't be that unstable as to cause lockups on average every two hours. I doubt SPB Weather is that unstable as well!
Yes, I must have push email. Why waste battery power polling every thirty minutes or so with pull email?
The memory card is going back in. I took it out, went to Sainsburys and BAM its locked again
I will now try the "no auto sleep" thing and see how that goes so thanks for that suggestion.
Click to expand...
Click to collapse
Even official applications are not immune from problems. The Hermes perhaps for some configurational reasons (though it's not just Hermes)does not like running active sync from sleep mode and it does not like running other applications that require syncing (eg. weather type ones).
Active Sync is not a particularly stable app and combine this with the Hermes weakness when being allowed to sleep by itself and you end up with a lock-up. (I have seen some explanations for this but only guess work and theories)
Many people have set their devices up to run active sync in manual mode only and this does help to reduce freezing. Of course you cannot do this with push mail enabled. (It might be possible to run some script or a scheduler programme to start and stop Active sync at set times - though the complexities here are as likely to cause a freeze as anything else!!
I am pleased your SD card seems not to be the cause - it can be for some.
I see you are possibly getting some benefit from a manual shut down rather than auto sleep
You may find the odd other idea on my site - freezing/lockups:
http://michael-channon.spaces.live.com
There is a thread here somewhere but i'd need to search for the thread.
You could also try doing without the weather app for a test. However you may not see a difference as active sync is already running for the mail.
Mike
Monty Burns said:
See my orginial post Crossbow
Click to expand...
Click to collapse
Sorry, didn't notice that......
Hi Mike
Turning off the auto sleep thingy has worked a treat. I'm down to one reboot a day now and that has been related to t-mobiles 3g network failure collapse me thinks
So this tip alone is worth its weight in gold!
SPB Weather is running and so is Activesync/push email.
Also now added today plugins:
RhinoStats (CPU/memory monitor - realtime)
RhinoLaunch (custom program launcher)
All seems pukka and "coma" free
Good news, pleased things have improved.
Of course I suppose we could all agree auto sleep should not cause the device to go into a "coma", but still, I've got used to just using the on/off button. Curiously this has improved my battery life as I turn off as soon as I finish, rather than waiting for it to turn itself off (which it won't anyway as I disabled that mode).
Mike
Monty Burns said:
right o' ... get your laughing gear round this
I let it "sleep" itself.
Im running:
Activesync (Exchange push mail - no pattern discovered with regards to receiving new emails)
SPB Weather (Today plugin)
Everything else is standard.
Connecting over 3g/HSDPA
There are other apps installed but these are always "closed" after being used. All apps are installed to the phone memory and not SD card - i've never tried without the card, guess I will try this now! Although, if this is the problem, how do I get around it???? I need my card.
Click to expand...
Click to collapse
I'll share my experience so that maybe it will help. I use WM6 on my 8525 and have found the "unable to wake" problem to be related to my SPB Mobile Shell. When I have the phone set to display SPB Mobile Shell's "Now Screen" upon wakeup, it quite often will not wake. But if I manually put the phone to "sleep" mode, then it will always pop alive fine. Disabling the Now Screen all together leaves me no problem. My guess is maybe it's an SPB issue. So maybe SPB Weather is causing it. I used to use SPB Weather before Mobile Shell, but since Shell has weather built in, I don't need SBP Weather any longer.
Hope this helps diagnose the problem a bit. For the record, I never had a wakeup problem with WM5.
Since going to black 2.5 and then 3.0 I have not had any of the sleep issues.
I run SPB Weather which is set to update every 5 hours, I run activesync to the exchange server which checks emails every 2 hours. My phone auto-offs after 3 minutes.
I did have AS set to When it arrives - but found this to be bad for battery and also stability. Every ten minutes was fine when I needed more urgency. All programs are installed to the phone, exept pie cache and outlook attachments which are on the card. I have not done any special tricks to avoid any sleep/card problems.
Hi. i want to ask. what makes PDA hang?
I am currently using Atom Life.
And sometimes it hang. and i have to take out the battery and turn it on again. which is very troublesome and makes some of my sms gone as well.
it sometimes occurs when i turn it on. it also hangs there.
can anybody advice me on this?
thanks.
T3D0nG said:
Hi. i want to ask. what makes PDA hang?
I am currently using Atom Life.
And sometimes it hang. and i have to take out the battery and turn it on again. which is very troublesome and makes some of my sms gone as well.
it sometimes occurs when i turn it on. it also hangs there.
can anybody advice me on this?
thanks.
Click to expand...
Click to collapse
lol,
good question
the buggy Os makes it hang.
a Rom upgrade should solve the problem.
shaileshashar said:
lol,
good question
the buggy Os makes it hang.
a Rom upgrade should solve the problem.
Click to expand...
Click to collapse
however, i updated to the latest rom already. how is it? does RAM affect?
T300,
There are lots of things that can make your pda hang, probably too many to go into. I will try and give you the principal areas you need to address, which come from my own experience coupled to tons of reading on here.
1) Activesync - This has a habit of running all the time and is a prime cause of lockups. Use the fake server solution to solve that problem (search on here for it using google search. I will give you the google search link in a minute).
2) Software incompatibilities - You need to make absolutely sure that if you are running WM6, your apps are the latest version capable of running under WM6. I have had a lot of problems trying to run WM5 apps under WM6.
3) Battery and power locks - Make sure that all system locks are disabled. For example you can set your system to turn of the LCD screen or power of after a period of time. Make sure all of these are inactive/not set. If you want to turn your screen off then lighty touch your power switch and it will do the job for you. Touch it again and your pda springs into life; simple. You can use the device lock option on the today screen if you need to lock your screen with the pda on; no problems with this option.
4) Programmes running in the background - I strongly suggest that you set your pda to completely close down any programmes after you have run them, rather than minimise. Use the task manager option to sort this out or install the htc x-button app (search on here for that also).
5) Beams and Wifi - Make sure these are turned off unless you need to use them. Switch them off as soon as you have finished with them. Benefits are improved battery life and less freezes.
6) Inappropriate themes - Not all themes work happily with WM6. Some do lock up your machine. Keep it simple; load a standard WM6 theme that you know works and leave it at that.
There's more, but this should give you something to work on. I will add to this post as I remember other things.
Let us know how you get on. Google search for XA is:
http://www.google.com/advanced_search?q=+site:http://forum.xda-developers.com&hl=en&lr=&as_qdr=all
Cheers
WB
Happy owner of a Hero for 2 weeks now, but I have a problem with HTC Sync 2.0.4:
When the Hero is not connected to my notebook (XP SP3), there is some activity on the notebook every 4 seconds, shown as a short flash of an hourglass next to my mouse pointer.
It took me a couple of hours to pinpoint this back to HTC Sync. Apparently, one of the processes needed for HTC Sync, HTCVBTServer.exe, keeps very active all the time even when the Hero is disconnected. Every 4 seconds, it spawns and kills a new instance of an other process called FsynSrvStarter.exe.
Leading to the very annoying flashing hourglass every 4 seconds.
I found some more information on this:
http://www.htcforums.com/hero-touch-f40/htc-sync-maxes-out-memory-t2791.html
The only way of stopping the flashing hourglass is killing the process HTCVBTServer.exe in Windows Task Manager.. Of course, HTC Sync doesn't work anymore after that, even after restarting HTCVBTServer.exe.
My request:
I want to install the previous version of HTC Sync (I think it was called 2.0.2) that was on the SD card, to see if that version has the same problem. Stupidly enough, I formatted my SD card and lost the program file. I've looked around everywhere on the internet (including htc.com), without success.
Is anybody willing to help me and send the install file of HTC Sync 2.0.2 to me or provide me with a download link?
I appreciate your help!
Marc
I can't help you with the older version as I deleted it from the SD card too.
I wish they'd make HTC sync start when you plugged the Hero in, and then have it shut down (and all related processes) when you unplugged it. Surely it can't be that hard.
I don't like loads of processes running unnecessarily.
Kadison, I totally agree.
Is nobody else having the problem I described?
And nobody who has version 2.0.2 for me?
I have monitored the process HTCVBTServer.exe with Process Explorer: with the Hero disconnected from the pc, it creates two additional handles every 4 seconds (explaining the flashing hourglass). 20.000 handles per 24 hrs, if I'd leave my pc on for a couple of days XP will certainly crash.
Serious bug! And annoying hourglass every 4 seconds..
I have found a workaround by suspending HTCVBTServer when my Hero is disconnected and resuming it before I sync, but would appreciate to get version 2.0.2 from somebody and see if that works better.
BTW I contacted HTC via email: 'we do not have older version, try to get from somebody else. RE: problem described: please reinstall'. ??!!
Cheers,
Marc
marc112 said:
Is nobody else having the problem I described?
And nobody who has version 2.0.2 for me?
Click to expand...
Click to collapse
If you can wait a while, I'll have a look at my old SD card (the one that came with the phone) and see if 2.0.2 is still on it.
Ok - I looked, what I have seems to have 2 version names i.e. 12.0.0.58851 AND 2.0.2 - would that be right?
Hi Vonne,
2.0.2 is the one I'm looking for.
As the file will be around 40MB in size, can you please upload it to Rapidshare and PM the file ID that you get from Rapidshare to me?
Uploading will take quite some time I'm afraid, I hope this isn't too much of a problem for you.
Thanks for helping me out!
Cheers Marc
Well, in case somebody else has the same unwanted behaviour of HTC Sync 2.0.4:
Vonne was so kind to send a copy of her 2.0.2 version to me (thanks Vonne!), which I installed after uninstalling 2.0.4.
Result: 2.0.2 has the same problem as 2.0.4!
The culprit process HCTVBTServer.exe still leaks handles (2 additional handles every 4 seconds) when the Hero is disconnected from the pc.
As a workaround I now suspend and resume HCTVBTServer manually (well, actually via 2 tiny batch programs on my desktop), to get rid of the blinking hourglass icon and several thousands of leaked memory handles.
Cheers, Marc
Pity it didn't work! I'm curious though to know if it's HTC Sync that's causing the annoying hourglass? I use a netbook and it seems to have a million background processes that cause a spinning hourglass
I too have hourglasses flashing now and then due to background processes doing stuff, but never one at a regular interval like this (every 4 seconds).
Googled around a bit and found the link mentioned in my startpost. One of the guys in that link had discovered that one of the four HTC Sync processes (HTCVBTServer) is leaking handles when the phone is disconnected. Killing this process via the Windows Task Manager stopped my flashing hourglass, so: gotcha!
Marc
haha, well, there I was going along blithely ignoring flashing hourglasses all over the place.....turns out I do have one that flashes ever 4 seconds...just checked! Don't know if I have the energy to be turning stuff on and off though.
I'd like to know if anyone is having the same lag problems as I am getting from time to time..
The lag happens for no reason and comes at different times while doing different things.
I downloaded Watchtower from the Android Market to monitor what was happening. When the phone is running fast the /INIT process is showing as 0%..as soon as the lag starts to happen I check Watchtower again and the /INIT process is at anywhere from 70% to 100% CPU usage.
I dont use an app killer but I donwloaded one to try and see if it would correct the problem, it doesn't. The only way to solve the lag is to Restart the phone, then its fine for the rest of the day, sometimes two days but it always comes back.
I sold my SGS because of the lag issue and now it seems I have it with the DHD..
I did google this and I found that it maybe something to do with android itself..looks like /INIT is an android process..
If you notice your DHD lagging then download Watchtower and I'd bet you will see the /INIT process killing your phone..
------------------------------------------------------------------------------------------------------------------------------------
EDIT - A fix has been found to stop the /Init process lagging the phone.
On your phone go to..
Menu/settings/applications/development/now turn on Usb debugging..
This seems to keep the / init process at 0% CPU usage, it also works when the /INIT problem starts, turning USB debugging on will make the /INIT process drop back to 0%, very nice to see.
Ive contacted the Dev to find out if he can tell us why this method has fixed the problem.
Still need an update from Htc but at least we can use our phones again..
There doesn't seem to be any negative effects from turning this option on, the only thing to note is turning it off to connect to your pc could bring the /init process back and lag your phone. You can download Android Manager from the market for free which will allow you to transfer data from your pc using Wi-Fi, using this app you can keep the USB Debugging on.
-------------------------------------------------------------------------------------------------------------------------------------
EDIT 2 - It looks like you can connect to the pc via USB cable with the debugging turned on without problems, the only difference is that it will try and install additional drivers...because of the debugging mode..
Im using windows 7 and the ABD driver wont install...you need to download Htc Sync on your pc which downloads the ABD driver !!
We should also watch the battery as this may actually increase battery life...
-------------------------------------------------------------------------------------------------------------------------------------
EDIT 3 - Not one single person has come back to me and said that the /INIT problem has returned after this fix...lets hope it stays that way.. 10/11/10
---------------------------------------------------------------------------------------------------------------------------------------------------
EDIT 4 - A lot of people including myself have found that this fix improves their battery life quite a bit.
-----------------------------------------------------------------------------
Last EDIT before thread is locked just for reference and to help people !!!
For people that have the com.htc.bgp process that loads the CPU it stays at 80-90% all the time, and i have autosync on, if you stop auto sync the process goes out....
So here is the final fix in the link below (post 7)
http://forum.xda-developers.com/showthread.php?t=659325
Thank you to everyone in this thread for there efforts...amazing response.
Thanks to all the XDA Community...Including the Devs and Mods
Thread Closed
nednapalm said:
I'm getting the problem.
No apps installed except the flash and maps update, oh and OS Monitor.
Have turned off "Fast Boot" and removed battery to reset, ok for now. Very scared to start installing more apps, nearly unusable when it is lagging
Click to expand...
Click to collapse
I also tried the "turn off fast boot and it was ok for 2 days, it came back this morning though..It is very worrying and yes, the phone is unusable until it is Restarted..Thanks for the reply.
sanju007 said:
LAG WHAT?
I hope not, the samsung galaxy s have lag issus and its very bad and i sold de sgs
And now the DHD gets also lag problems ?
Ik hope not, then i will not buy this phone
Maybe an good task killer wil help ?
More people have lag issus ?
Can you make a video ?
Click to expand...
Click to collapse
An app killer doesn't solve the problem and Im unsure how many people are having this problem, to my understanding its not many...that's why I started this thread to try and find out.
I wouldn't worry yet...
I will make a video when it happens again...it may take a few days to come back....but it always does...a video added to this thread would be most useful...just have to wait till it rears its ugly head again.
So it seems that /init is a core process regarding the initialisation of the Android system and userspace hence the fact it cannot be killed using OSMonitor. It is always the first process that runs on Linux systems after boot and acts as a parent process which itself initialises then processes needed to get the OS going.
Here is a description of the Android Init Process from elinux,
'init'
A key component of the Android bootup sequence is the program 'init', which is a specialized program for initializing elements of the Android system. Unlike other Linux systems (embedded or otherwise), Android uses its own initialization program. (Linux desktop systems have historically used some combination of /etc/inittab and sysV init levels - e.g. /etc/rc.d/init.d with symlinks in /etc/rc.d/rc.[2345]). Some embedded Linux systems use simplified forms of these -- such as the init program included in busybox, which processes a limited form of /etc/inittab, or a direct invocation of a shell script or small program to do fixed initialization steps.
The init program processes two files, executing the commands it finds in them, called 'init.rc' and 'init.<machine_name>.rc', where <machine_name> is the name of the hardware that Android is running on. (Usually, this is a code word. The name of the HTC1 hardware for the ADP1 is 'trout', and the name of the emulator is 'goldfish'.
the 'init.rc' file is intended to provide the generic initialization instructions, while the 'init.<machine_name>.rc' file is intended to provide the machine-specific initialization instructions.
The Bug
The /init bug has presented itself on numerous handsets including the HTC Desire, Nexus One and Droid X models. It seems to be specific to Android 2.2 and reports the same symptoms on all handsets. Primarily this is due the 99% CPU usage causing system slowdown and left unchecked, high battery usage. It is not specific to HTC Sense ROMs as it also presents itself on stock releases. The only solution so far is a reboot. Hard Reboots and altering system settings seem to have no effect on the reproduction of this bug.
I can only speculate to what is causing the issue and hopefully a Dev can shed some more light.
Logically it seems as though a 'rogue' process is triggering /init to resume its primary function in regards to checking filesystems and attempting to spawn other system process. Due to some form of miscommunication between the processes in question, /init continues to perform these post boot tasks in a constant loop.
Think of it like this, if you try perform tasks straight after boot, the phone is unresponsive while the SD is mounted/checked and all other processes are fired up. The /init process is responsible for these tasks. If it were to loop, you would experience the symptoms we are having.
I found this on Wikipedia:
After /init has spawned all of the processes specified, init goes dormant, and waits for one of three events to happen:- processes it started to end or die, a power failure signal[clarification needed], or a request via /sbin/telinit to further change the runlevel.
So our trigger should hopefully be narrowed down to these three events.
Regarding what I posted before, the connection between sync and the bug has proven itself to be a false one.
I've also noticed that sometimes the bug can be present, however there is little impact on the responsiveness of the OS. It can seem as though everything is ok yet the CPU load can be extremely high, resulting in poor battery performance.
Anyway, hopefully more people can contribute to this thread so we can build up a better picture of what is going on. I will also try and grab a Logcat and ask anyone else near their PC when it happens to do the same.
There is a thread here which has users complaining of the same problems, yet no solutions are presented. Hopefully we can make a bit more noise and get some definitive answers.
Regards.
Hey guys some great feedback here, as with my link on starting this thread the /INIT is an android 2.2 process, auto sync on/off doesn't solve the problem neither does a hard reset, taking the battery out ect...
The guy in the link says his method worked for him, can't say the same for myself, I have a feeling his problem will be back...but if it did fix it for him then thats great, just cant say the same for me
http://forum.xda-developers.com/show...3&postcount=42
I have gone 5 days without the problem coming back and then Oh no its back, sometimes it happens twice a day, all the above doesn't fix this problem im afraid from what I have experience anyway.
The /INIT process is only 132k, something so small causes the phone to be basically unusable....very frustrating.
The 1.32.405.6 update also doesn't solve this problem, I updated yesterday and 10 min later I had the dreaded /INIT problem...
The so called "turn off fast boot doesn't fix the problem either, I have had the /INIT lag problem with it switched on and off...
What I find to be the most strangest thing is that if this is indeed an android process which it most likely is then why doesn't every DHD phone have this lag from time to time???.....why only certain phones??..
I haven't had the problem since yesterday (around 12 midday), when it occurs again I will be posting a video as requested...
The mystery continues.......There is NO solution as yet that fixes this problem.
Thanks to Lynxboy, your posts give some good information.
I wonder if this has any relevance to the problem from a linux based PC..
It seems that /INIT uses the same Process ID - 1 (found from using watchtower)
http://www.yolinux.com/TUTORIALS/LinuxTutorialInitProcess.html
BigMango said:
You purchased it from ebay, but did you buy it from a shop or from an individual (second hand)?
If you got it from an ebay shop they should give you a receipt. If it was from an individual, he should give you his original receipt (that's when the warranty started).
Anyway, the phone has a 2 years warranty, so you are covered for the next 2 years minus 1 or 2 weeks. And the paypal transaction is a valid payment receipt (it can be verified directly with paypal); so even without the receipt from the first owner HTC should cover you since the phone can't be 2 years old.
Get in touch with HTC directly, they should replace it. But the tricky part is that the problem must happen when they check it out, for this reason I would also make a video of the problem the next time it happens and send it to them by email so they can keep it on file with your RMA.
Click to expand...
Click to collapse
Thanks for the advice, Im going to contact the seller, he had it on upgrade and shipped it to me the following day..he seemed a nice guy so It should be ok...Now its just a matter of waiting for MR INIT to show up haha....wonder if he wears a hoodie LOL
bimmerfox said:
I'm not wrong because I see it with my own eyes. Even my DHD had the same problems as described. After the update no more /INIT at 90% and it keeps running smooth now.
Try to keep your patience before quoting a person who is willing to help others.
Click to expand...
Click to collapse
What?? Why do you think I made this thread...to help myself and others...as we do at XDA....the update doesn't fix the problem....just because yours hasn't lagged since the update doesn't mean its fixed....I've gone 5 days with no lag and it came back...like yours probably will.
Ridiculous....
EDIT- You can't post a statement that the problem as been fixed when numerous people have done the update and still experienced the /INIT problem...how can it be fixed??...and since the update only came out yesterday you have no way of knowing this for sure... its way to early to say that.. Try reading through posts in the forum and gather some information next time.... the update was for the youtube fix, we're not even sure that HTC were aware of the problem at the time.
Hi guys,
Just finished work and have caught up with the thread since I last posted and wanted to clarify a few things. I would also ask any new readers to find my previous post which covers much of the nature of the /init process.
The problem is solely software based. The hardware is NOT at fault!
The /init process is the parent process of Android/Linux, hence the PID 1 in OS Monitor. Imagine it as the ignition system in your car. You need to turn the ignition to fire up the other systems and that technically is the role /init takes.
It is not a rogue process in itself. It cannot be killed or closed via a task manager.
The latest update was not a fix nor does it resolve the issue.
The bug IS a Froyo bug and affects numerous devices not just the DHD although it is not present in all Froyo ROMs.
It is possible the memory management is to blame however I have run many Froyo based ROMs from FRF55 and not experienced it before; they all use the same memory management.
The three triggers for /init to awaken after its boot tasks are completed are specified in my previous post. These are the most likely causes for our issue and are in my mind triggered by some rogue process interactions.
A logcat will only really be useful if it captures the event taking place. A logcat taken when the /init process has started will report back specifically that.
Just because you haven't experienced the bug in 2days doesn't mean you are bug free, nor is there a bad batch of phones as this would indicate a hardware issue.
Continuing this thought, it is possible if you are on a branded operator ROM you may be bug free.
The /init bug is extremely annoying.
Regards.
Yes off topic...
Im asking the mod to still keep this a sticky but to lock the thread as there is really nothing left to discuss and its just here for people that are still having the /init problem as a reference...
EDIT - Thread being locked soon so....
Agian thanks to all xda community !!
Is this stickie needed anymore? Has this been corrected by any software update?
I've had this problem since the day I got the phone (December 2010) and got it again today. Once I see the obvious lag of everything, I just restart.
If it can help...
I have noticed this phenomenon the first time just after installing 2 things in my DHD :
- creating the HTCSense account (and keeping it synchronized one a day)
- installing the HTC plugin for Picasa Web Albums in the Album application.
Maybe coïncidence, maybe not.
I have disabled all HTC Sense stuff I can see. It always happens when performing some action, like opening a new app. It seems to occur so randomly, it happened again the day after my last post, but has been fine since then.
Problems with calendar after removing cache and program data.
I had major problems with com.htc.bgp using up to about 90% of my processor from time to time. When I searched the forums I found this thread.
I tried what is stated in the top post and went ahead and cleared the calendar data and the gmaill data. This is all fine, I don't seem to get any more warnings about com.htc.bgp reaching the 90% mark. One slight problem that occured though is that now when I'm syncing my calendar back to what it was, it either does not search or does not find all the other calendars that I have. The list is just totally empty. Strange as it is, It does find and sync with the default [email protected] Gmail's working fine and syncing properly though.
Since I rely on the calendar I really need this to be fixed as soon as possible.
I don't want to put words in your mouths, but I figured I might need to factory reset the phone. No biggie, but a time consumer, since I need to recustomize everything again (not rooted, not titanium).
Are there any ways of luring the calendar back on track. Jumpstarting it without a factory reset?
Thanks in advance.
Henrik
So apparently all it needed was a full night of syncing, because now it works again.
It seems though that I got rid of the annoying com.HTC.bgp that drained my processor.
Thanks to the thread
Sent from my Desire HD using XDA App
Have not experienced this since the 2.3.3 upgrade, problem solved!
I'm having this problem on my Defy after installing SetVsel, setting any values, after time the cpu stuck at 100. Watchdog lite didn't show nothing but 100%, not any process higher than 50 even. I turned on in the watchdog to show system processes and ther it showed that:
init
Linux process
Had most the time the highest percent used
I googled and found this topic. The
Menu/settings/applications/development/now turn on Usb debugging.
Click to expand...
Click to collapse
solution solved my problem. The proc isn't anymroe stuck at 100%.