yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Steel, you pull the logcat only to view what has that "for broadcast" verbage in the line. Once you determine which apps have that (those are the ones that are auto starting) then you determine which ones you want to stop from autostarting. Then you go into the shell that you've opened and enter the pm disable, etc, etc that Arrrghhh notes and Hyc references in his original post.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I have heard good things about 'autostarts'.

Honestly, that is probably the hardest part of the 'Speed Improvements' thread, and I should probably streamline it and say "just use this app". The method hyc provided, while educational, is a bit arcane :p.
[Touch Pro2, Tilt 2 Android Development] SteelLife:
Ok the 'SHELL" is the logcat? Sorry I'm lost!
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
No, you need to use ADB to run a logcat or that nifty little app called getlogs. Once you determine which apps are autostarting then you need to open up a shell and use the commands noted, however.... I've grabbed one of the free autostart apps from the play store and it's a hell of a lot easier than the method I'm referring to. Even Arrrghhh notes above that he's heard good things about it. Believe me, I'll be using one of the apps to do this rather than pulling the logs and then commenting things out in the shell.
[Touch Pro2, Tilt 2 Android Development] SteelLife:
Autostarts is a paid app can't do it now. The other ones don't allow u to stop an app from starting only allow u to start one. I found a free one trying now! Wasn't free still looking!
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Try this one, it's free, I grabbed it and I'm currently playing around with it. Although I've knocked off most apps that autostart already between just uninstalling them (amazon) or using hyc's method previously. https://play.google.com/store/apps/...lt#?t=W251bGwsMSwxLDEsImNvbS5ycy5hdXRvcnVuIl0.
[Touch Pro2, Tilt 2 Android Development] SteelLife:
Trying right now thanks!
[Touch Pro2, Tilt 2 Android Development] Slipdoozy:
ive tried that one myself... but it seems more advanced than the one i suggested.

ive heard it does a better job at killing the "new" apps that always will restart like facebook v1.9+

but i refuse to upgrade to that version so im still good :good:

also i think Autorun Manager is from XDA member support the community lol
[Touch Pro2, Tilt 2 Android Development] sera:
I am also having the same issue. On sprint using a fresh formatted 4GB card. No apps installed except led regime and getlogs. 3.4.3 kernel. Battery drain problem is due to phone never sleeping. I have verified this using led regime. Led is set to orange when active and off when sleeping. Screen turns off but phone never sleeps. Orange led is always on. Logs here pastebin.com/N14HBCM6
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I wanted to say there was a bug where if the wifi was turned on the phone wouldn't sleep with this build on the 3.x kernels.
[Touch Pro2, Tilt 2 Android Development] sera:
thanks for the tip but WiFi is turned off
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Does it happen on .27?

Did you enable any radios?

Have you tried disabling any radios?

Does the phone ever sleep?

Have you tried any other kernels?

Did you setup a GMail/Google Play account? Did you set it to sync at all?

Edit - based on your logs, the phone sleeps and then is immediately awoken by the user (to my pretty novice eyes).

Honestly, at this point there's no developers left. So if there is in fact a system issue, I'm going to have to rely on you folks to figure it out. Others (including me) ran this build for a very long time (and the phone was definitely sleeping).

So perhaps there's something you're missing.
[Touch Pro2, Tilt 2 Android Development] sera:
The phone never sleeps. Not even in airplane mode. No gmail or playstore accounts. Also disabled background sync. I have tried other kernel mostly the 3 series. I didn't recall the .27 behaviour so tried it just now. Phone does sleep with .27. I should try all the kernels one more time and post results.

Edit phone froze after an hour of no use. Led orange indicating it was awake. Further few reboot got stuck in boot animation. Looks like need to start over
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So .27 is fine. Interesting. Do you have any radios on when booting Android? WinMo should be in 'Airplane Mode' when booting Android...
[Touch Pro2, Tilt 2 Android Development] sera:
I boot from airplane mode in WinMo. I did try to boot with just cdma radio on but it did not make any difference.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
If .27 is fine, then something is wrong with how you swap kernels perhaps?

IIRC, 3.x kernels sleep just fine. Perhaps you're using the wrong LED Regime app? The APK's are different for .27 & 3.x+...
[Touch Pro2, Tilt 2 Android Development] sera:
I don't remember which ledregime I had installed. I should use XdaLedRegime_.39+.apk with other kernels. I would like to restart with formatted sd card. Do you recommend starting from GBX0C_Full_Bundle_2012.04.24.zip? Then start swapping kernels. I swap kernel by copying the zimage and corresponding module file. zimage gets overwritten but I don't delete the modules file corresponding to older kernels.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You should also delete the modules file, to avoid any confusion.

.39+.apk goes with any 2.6.39+ kernel. The other APK is for .27 only (might work for .35, but no one should be running those kernels at this point...)
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Don't forget that haret.exe has to change between the 2.6.x and 3.x kernels.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Not entirely true. GBX0C has the 'new' HaRET and it can be used on any kernel...

Just wanted to clear that up, you don't need a different HaRET for .27. You do need a different HaRET for the newer kernels, which again is included in GBX0C ;).
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Oh. Well dang. XD I somehow managed to miss that; I started playing with kernels in 0B and stopped paying attention. ^^() Heh, thanks for the clarification, and sorry for the noise.
[Touch Pro2, Tilt 2 Android Development] clarf:
Camera does not work on RHOD500

Hi,

I just installed this GBX0C 2.3.7 rom on my Touch Pro 2 (RHOD500) its working fine, Wifi works (after installed Wifi Advanced application for WEP connections), bluetooth works, etc.

But I have two issues:

1. I have a minor issue with the network configuration, I must select "GSM only" on network properties each time I boot on Android or else it does not find my network and shows the searching network message for ever. Is there any way to save this option between reboots?

2. When I try to start the camera application the device is rebooted (its shutdowns and then starts WM).

I tried the Complete FroYo Bundle** FRX07.1, but it has the same issues with the camera and the phone network. (This ROM also seems less responsive and slower than the GBX0C rom...)

Any advice about these issues?

Thank you

Regards,

clarf
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Try a different kernel please.

I'm not aware of any camera issues that pertain specifically to the RHOD500, most of the cam issues were related to the 100.

With that said, our camera libraries are pretty basic. We don't have the source for that hardware, so it's all just reverse-engineered.

As for the RIL issue you seem to be having, the RHOD500 is a CDMA device. Of course you will have to force GSM on a CDMA device...
[Touch Pro2, Tilt 2 Android Development] clarf:
Thank you for the information.

I´ll try a new kernel, as soon as I could test it I´ll feedback.

Regards,

clarf
[Touch Pro2, Tilt 2 Android Development] clarf:
Hi,

As recommended I tried other kernel versions to fix the camera issue on my RHOD500 (Verizon).

I tested two kernel packs: kernel-pack-htc-msm-3.0.18-g9299429-20120222_053626.zip, kernel-pack-htc-msm-3.3.8-ge0d700d-20120607_073427.zip.

Kernel 3.0.18:

-Using this kernel version I can open the camera application (it didn´t make the system reboot like the default 2.6.27 kernel), but after I took the first shoot the application freezes and I could not open the camera app again (it actually don´t take any picture or video).

- I tested the bluetooth function with other Android device (HTC hero stock ROM), bluettoth file transfers sometimes works but I have to enable/disbale this function many times to actually make it work, seems unstable.

- Using this kernel the OS seems slower specially opening an application for the first time.

- Good battery life

Kernel 3.3.8:

- I can open the camera application and I can take pictures and record videos without any issue...

- The Bluetooth behavior is the same than 3.0.18 (I must try it with other non- Android device)

- This kernel seems a little faster than 3.0.18

- The problem with this kernel version is that it quickly drains my battery (even faster than the 3.0.18 version)

I have made some advance with 3.3.8 sadly the battery drain is a real problem for me, I´ll try to test other kernel versions until I found one that meet my needs.... Any recommendation or advice on these versions?

Should I put this information on the TESTING kernel 3.3/3.4 thread?. Anyway the original question was posted here

Thank you

clarf
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Typically newer = better. There's an issue with tethering with 3.4.3, but other than that it *should* work fine.

Keep in mind, BT is flaky - no matter what kernel you use. Doubtful this will ever change.

Also, keep in mind - the cam is going to be flaky as well, for the reasons I listed previously. We don't have any source, all of the work done on the cam is reverse-engineered. Basically done blind.
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
I had the best luck with BT in one of the earlier 3.3.x versions, 3.3.6 I believe. Even then, it would freeze the device after a conversation or two. So I gave up on BT with SD builds.

I see little difference in battery drain between 3.3.8 or 3.4.3.

OM
[Touch Pro2, Tilt 2 Android Development] jonners59:
Hi arrghh and all

It has been a long time since I gave any feedback, appologies. My Rhod100 with the kernal in the first post in the main works fine though I still have some issues which I have provided logs for in the past.

I get all the radio types working including tethering, BT and WiFi with zero issues. The probs I do get are:

1. Camera has suddenly stopped working, don't know why or when, but neither video or stills work. It opens, but nothing appears in the viewer and to exit the app I have to reboot. It used to work as I have shots from Easter... puzzling

2. I switched to this build from F7.01 on arrghh's suggestion to get BT, camera and resolve the Android Market rebooting problem (after an install or update it would go into a series of reboots, this not being an issue in this build), this problem with Android Market has re-appeared since the change to Google Play. I now get the constant rebooting. Sometimes, if I can keep Google Play busy or at least the phone it hangs on and without rebooting. It seems to happen AFTER the install when refreshing itself, just when one thinks you got away with it! :):confused:

3. I am also finding I can not answer inbound calls in time 9 out of 10 times. When a call comes in, it rings (normally, sometimes it does not), but the phone is so busy or in sleep it does not get to the call until after the call has hung up.

I was sorry to see in one of the threads that all the developers have moved on. That is a great shame, especially when you, arrghh have done so very much on this. Always impressed in your commitment. I understand the need for us to find our own fixes for these issues and I continue to work on it. You will be pleased to learn that my drive across Europe the phone switch perfectly in all countries.... only minor switching issues at times.

I may try another kernal, perhaps something a little later.

Cheers all

---------- Post added at 02:05 PM ---------- Previous post was at 01:57 PM ----------

I'm putting this on my device as I think that some of the order in which apps load causes boot crashes and some apps just load, draining valuable power. Shall give it a crack, though arrrghhh won't be pleased. That takes my total apps to 132........ :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
And you wonder why you have so many issues?

I'm amazed bluetooth works at all. I'm betting the poor device doesn't have any RAM left to spawn the camera. My best guess without logs.

Edit - Regardless, as you noted - most developers have moved on to newer devices. So this has been a great project, I loved working on it - but remember, I did very little compared to the actual developers. I think I committed all of 5 lines officially.

Either way, I don't see how your issues would be related to anything that would be resolved with logs or patches - that stuff worked before, I'm betting some app or again lack of RAM has killed your cam, inbound calls, and Market/Play. I'm betting if you renamed your data.img to data.bak, booted again, and let it settle all those things work would like they did before you installed 130+ apps.
[Touch Pro2, Tilt 2 Android Development] jonners59:
Modesty :D

Actually, I had far more apps, I removed some to get it down to the 130. Many are the recommended or those suggested in the threads of this and other builds for management, and improved functionality, like speed and battery life... PS: Never the 10,000 you once suggested, max 150. :D

There is RAM. You maybe right, but then it is hard to say if it is enough or not or the problem

OK, as these are my only probs, and you suggest another new data.img... a couple of questions, because when I do all this it takes for ever.

If my imag is "damaged" in some way, then if I use a backup from Titanium to restore, surely I am reintroducing all the rubbish I am re-imaging to get rid of, nes pas? Or not? :silly:

It was suggested by some contributors and I agreed that the booting order may have something to play in probs. I have noticed and had a typical expeirnce of it today that su is not granted until qyuite late in the bootup and so many apps requiring su privilages do not work.... It's just a thought and may only affect a few machines - you mentioned in one reply particular issues with Rhod100s, that's what Ihave - 3 of them and they all behaved the same.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
If you have three phones, why not load one up with a freshly downloaded copy of the rom (and just the rom/gapps/market) and see if you still have your issues.

Also use a newly formatted sd card. SD card speeds can cause issues. Go read this thread for more info. http://xdaforums.com/showthread.php?p=12964262

And yes, 130 apps is a lot for these phones.
[Touch Pro2, Tilt 2 Android Development] jonners59:
:)

I gave one each to my wife and son......

Card is new and is that shown to have the best performance on the thread choosing a card. As I mentioned many of the apps are besides those I need to use I have also installed those recommended on this and other threads, as I have been through them all to get the best performance. I started this project in F6

The 3 probs I have are not unique to my device, whether it is caused by so many apps or not. I had not installed any new apps when all this started, it was fine. I ran it with GPS and CopilotLive, Radio inc data, Bluetooth, all on at once when travelling through Europe and had no issues there and back. In Titaniuam it says I have about 25% RAM spare.

I have just copied my entire SDcard to my desktop, and reformatted it and am currently, slowly copying all the files and folders back and a new data.img. I shall see what happes when I reboot. Hopefully it shall fix as suggested by arrrghhh. Lets see.
[Touch Pro2, Tilt 2 Android Development] SteelLife:
Data.img

Ok seem my data.img keeps getting messed up and keeps getting stuck in the loop when my battery dies and b/c of that I lose all my text and have to start a new data.img. I might not have explained properly. I can't get back to android it just stays on the splash screen.:confused:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Data.img corruption skyrockets when the battery dies.

Make sure you don't kill the battery... and your data.img's will last a lot longer. I used the same data.img for months on end with no issues.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
+1 to this. Shut the system down if your battery is close to being empty. Don't let the battery die with the system running. If you insist on this behavior back up the data.img daily.

---------- Post added at 01:34 AM ---------- Previous post was at 01:27 AM ----------

Just because an app is recommended does not mean that installing them all at the same time is necessarily a good idea. An app is usually suggested for a specific reason. Also I doubt there are 100+ apps recommended.

If you didn't have problems before you installed the apps and now you do, I would start by not installing so many apps. Only instal the ones you need 100%. Then add things one at time, testing as you go.

I hope you decided to format using the HP tool, and not windows format.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I used to suffer from this issue a lot too. That is why I decided to switch to the nand builds. Harder to setup the first time, but I never have to worry about needing to rebuild my phone because it stopping being able to boot up (well never the phone's fault anyway). The SD version can't unmount the SD card on shutdown. That doesn't help either.
[Touch Pro2, Tilt 2 Android Development] jonners59:
Mmm... I did not think I said there were 100+ apps recommended. :confused: I installed and used apps that were suggested to fix issues that I had experienced and to improve performance. And, again, the phone has been working well without any changes for months. As I mentioned the 3 issues have come about recently and without ANY new apps or changes bar the usual upgrades.

I think this build has been excellent to date.

I use Ubuntu/Linux and Windows based tools do not work well.

I used gparted, which I have used very successfuly for the past 2 years. That said it has all gone horribly wrong. I did have a working machine I now have a broken one.

As I mentioned I copied everything over to my desktop and then refromatted the card. I then copied the Android folder back and all the backup folders and the misc csv etc... I then added a new, clean data.img (2Gb which is the max that works on these machines, built using Toporesize - another recommended app)...

That was the plan. The first problem being that I could not copy stuff back, the permissions kept changing mid way and saying the card was read only - discovered a common prob with this on Ubuntu threads and after many attempts and a day's work I managed to get the folders and docs over as above. I rebooted and started to Restore via Titanium... then it ran out of memory. The reboot had deleted my 2Gb data.imag and replaced it with the stock c200Mg. So I tried to replace it, same thing.:confused:

Tried a new card, same thing... Tried another new card, same thing. I am now stuck.:crying:

I also noticed that the phone was very fast before I did anything to it, as soon as I added my gmail account so I could download a file explorer to search for Titanium, the phone slowed down to normal op speed. So it seems to be the account that slows it down on my phone.

I think I should have left my phone alone.:(

---------- Post added at 05:36 PM ---------- Previous post was at 05:33 PM ----------

Totally agree with this.

PS: I have only just noticed that the thread has become GBXOC I am sure it was B the last time I was here.... I must have missed the change. Is this significant or am I just imagining the change????????????????????????????
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Perhaps. Android is not for everyone. Just pull out the SD card, and magically the phone will be as though you left it alone.
[Touch Pro2, Tilt 2 Android Development] jonners59:
Sorry, I do not understand??????
[Touch Pro2, Tilt 2 Android Development] wizardknight:
If you remove the SD card the phone will boot to Windows Mobile. Just like it was before you put in the GBX SD card. I.E. your phone will be just like before you touched it.
[Touch Pro2, Tilt 2 Android Development] jonners59:
Ah, you have not read any of my replies then. I am an avid Android fan and I also love the TP2. I have used this and other builds for some time - F6.... What I was referring to was my phone work, but had a couple of issues start up, and arrrghh suggested a new data.img. I also took the op to re-format the SD Card, and now wish I had just left things as they were as it is now a mess!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So you've formatted the SD card a few times (full or quick?), and you can't get it to boot at all - on the vanilla stuff from the first post, nothing customized?

Don't do the toporesize.

Just try to boot...

If that still fails, perhaps try another SD card.
[Touch Pro2, Tilt 2 Android Development] jonners59:
I tried on a number of SD cards... What I ended up doing was putting everything back as it was, so now I have the phone working but with my probs.

What I may try is a new blank data.img as origionally suggested and not reformate the card. I store a number of empty data.img of various sizes from previous projects, so all, in theory, I need to do is copy one over. The prob is that there is an ongoing issue on Ubuntu 12.04 where by during copy to removable media it changes it to read only - not for this forum, but annoying in trying to get a fix.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ubuntu 12.10 isn't officially released yet, so I have no clue what you would be bothering with it for.

Also, "I store a number of empty data.img..." - what the heck? You can't just rename the existing data.img to data.bak and let the rootfs create a new one just to see if it's that!?!
[Touch Pro2, Tilt 2 Android Development] clarf:
Hi,

I´m still using the kernel 3.3.8 for my RHOD500 and I still have the battery drain problem. Although I have everything off (all radios for GPS, Wifi, BT, etc). It does not last more than 8 hours, Battery Use option shows that the main usage is in:

Cell Standby = 55%

Phone Idle = 40%

Even with a good reception level I have this battery usage. My Network configuration is "GSM Only" and GSM 2, does anybody know any other tip to reduce the battery drain? (I already read many topics about android battery save).

regards,

clarf
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Nope. That's it. If you want to load a nand build OMGB has a newer battery driver coding.

Maybe it is time for a new battery. I have a Rhod 400 running GBX nand kernel 3.3.6 that I can get 2-3days out of when everything is turned off and having ~2h use per day. I set it up this way as a temporary e-reader.
[Touch Pro2, Tilt 2 Android Development] Caldair:
Have you installed and run XDALedRegime_.39+.apk to see if your phone is entering sleep when it is idle?

I don't know what setting you are talking about when you say GSM 2. Is that the name of your network carrier or something? Anyway, I guess that's probably nothing.

After using XDALedRegime if you find that your phone is mostly sleeping when it is idle then this...

is probably the best advice you will get. Trust me a brand new battery makes a world of difference!
[Touch Pro2, Tilt 2 Android Development] clarf:
No, as far as I know, I only need to edit a parameter file and this software is not needed, does it install other library files needed to acomplish that?

Sorry my fault, I was talking about the option to saves battery life "Use only G2 Networks"

Thank you for the advice, Although I am not thinking on changing the battery right now, because I get easily 4-5 days of battery life using WM...

I´ll check the XDALed thing first...

Regards,