yashsingh1/xdaforums huggingface dataset:
[Vibrant Q&A, Help & Troubleshooting] Saiboogu:
Well, not sure how useful my guide would be - I cheat a bit.

I use Titanium Backup.

After I restore my backed up applications I go to the Backup / Restore tab.

Menu > Filters

Select "Not backed up" under "Filter by status:"

Apply

Now I'm just looking at the apps not in my backup set - things that were installed by the new ROM.

Personally I drop just about anything in the ROM that didn't come from Google, with the exception of the video player (better codec support), Bluetooth bits and pieces (since Samsung uses a different Bluetooth stack) and the Samsung music player.

I think I'm going to be rooting the wife's phone later to upgrade her to JL5 - I'll try to make an exhaustive list then.
[Wildfire General] droidd3v:
Hey guys,

I am still awaiting Froyo to be officially available for my phone (been checking it ever so frequently but the update isn't just available :( )

Anyways, until I do get the update, a few quick questions:

1. Before the update, how/where do I back up all the apps, contacts and the like?

2. Is the update reversible? I mean once I move on to Froyo, can I get back to Eclair (for whatever reason!)

3. Apart from the backup, is there anything that needs to be done?

4. And honestly, how much of an improvement is Froyo on Wildfire as compared to Eclair? {basically is it worth the pain?}

I'm sure these questions are around on the forum but I just wanted them to be under one thread. So please do take time off and reply to these Q's and bring in all your suggestions related to the update.
[Wildfire General] rmittal:
This genrally applies to unrooted stock ROM

1. You can use Backup apps like My Backup Pro to Backup your Apps, data & Settings.

2. I believe the update will not be reversible.

3. If you are ready to start afresh Hard reset your phone. *** (Will wipe everything on your phone and make it brand new on the software side)

4. On stock ROM there should be some improvement in speed and you get App2SD, Wifi Tethering etc.
[Wildfire General] Alex_GP:
Yes, the update is now irreversible. Maybe in the future months when unrevoked will be updated.
[Wildfire General] droidd3v:
Hi,

First up: sorry to bump this old thread of mine.

As evident by this thread I was very curious to upgarde to Froyo. I had been checking for updates on my phone and it was always displaying the "No updates available" message.

Then I looked up this thread: http://xdaforums.com/showthread.php?t=889734

and first upgraded to the 1.25.720.1 version and immediately an update was available. I updated, did a factory reset and now have FROYO.

But the one thing I notices is that the SENSE UI hasn't changed at all. I mean its the same boring thing that came with the stock ECLAIR. Now I was wondering if:

1. There is some other update that I'm yet to complete?

2. There is actually only one SENSE UI across all versions of Android?

I'm currently using launcher pro and I have currently removed SENSE from the defaults (settings->Applications->Manage applications->look for HTC Sense->Clear Defaults). With this setting, earlier I used to get 3 options when I pressed the HOME screen on the phone:

1. Android screen (or so I thought it was)

2. SENSE

3. Launcher Pro

but now I'm getting only 2 options: SENSE and LP. Is there any way by which I can get back the original Andorid (?) home screen?

Thanks a lot for all your help.
[Wildfire General] rmittal:
Default Android Home screen has been removed in Wildfire Froyo.
[Android Software/Hacking General [Developers Only]] STLKeeper:
when trying to root device, i'm to the part where you use adb to push the recovery.img Instead of successfully implementing this i get this error:

error writing recovery: no space left on device.

wtf?? Anyone??
[HTC Aria Q&A, Help & Troubleshooting] bcarruth62:
I am having problems viewing videos off of websites like ESPN or CBSSPORTS, I can get the sound fine but it says "no video signal". The video comes up fine on the iPhone 3g but not on my Aria. Talked with my AT&T rep and he said could be a problem with the media player and would get back to me when he found an answer. Anyone have any ideas where to look for an answer?

Thanks
[HTC Aria Q&A, Help & Troubleshooting] sagerox:
Use skyfire as your browser, it lets you watch most flash video.
[HTC Aria Q&A, Help & Troubleshooting] bcarruth62:
Getting the same results using the Skyfire browser. I'll get audio but no video. I've tried the Rockplayer media player and I get video but no sound. Any other ideas?
[EVO 4G Q&A, Help & Troubleshooting] postwick:
Since I installed the OTA update yesterday, I no longer have the problem where my Evo doesn't play any notification sound, but it plays the wrong one.

After a reboot it plays the right one for a while, then starts playing the wrong one again.
[EVO 4G Q&A, Help & Troubleshooting] Greenfieldan:
Are you using a separate app (Like handcent) to do the notification sound, or did you do it in settings?
[EVO 4G Q&A, Help & Troubleshooting] postwick:
I use Handcent. Open it up, go to menu/settings and do it in there. It used to be that it worked for a while and then stopped playing a notification sound altogether. And this was before I installed Handcent.
[Galaxy Tab General] newsoundwave:
I wasn't doing anything special with my Tab, just browsing some sites, put it away for maybe an hour, then brought it out. Hit the power button on the side and... nothing.

I held it, thinking maybe it turned off. I also charged it for a while, thinking maybe the battery turned off.

Nada.

Anyone experience something like this and have a fix?

Thanks in advance.
[Galaxy Tab General] rodnav:
try a long press on the power button.. maybe 10 secs... it might have frozen on the last software and that will turn it completely off. let me know if it works.
[Galaxy Tab General] newsoundwave:
nvm... as soon as i finished typing this, the damn thing roared back to life..

mod, please delete~!
[Galaxy Tab General] newsoundwave:
lol thanks anyways. it suddenly turned on for no reason >-<

didn't even press the buttons...
[Galaxy Tab General] marjibis:
That has happened to me 2 or 3 times during the past one month. I guess it is a feature (!) of the Tab
[Galaxy Tab General] sillyrabbitt123:
LOL :D neat feature.

I have had this happen too. I just held the power button down too for 5 secs and it worked.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Downloading and testing now...

UPDATE: Sorry this is taking so long but strangely I've had 5 boots in a row that have resulted in that slow, 100% cpu issue...I've never had that many in a row but can't say that it's the test kernel...I'll keep trying...btw is this built off of the 1245 kernel or an older one?
[Touch Pro2, Tilt 2 Android Development] the.decoy:
Yep, testing now.

Incidentally, with both this and 1245 I cannot seem to boot my neopeek system. They fail to see the root partition at /dev/mmcblk0p2 and either hang or reset.

The 1242 kernel still works fine . Weird :confused:

Anyway, I will test this out with my XDAndroid setup.

Cheers!
[Touch Pro2, Tilt 2 Android Development] DopeyOne:
Sorry to be an echo of the others... before I test it, is it built from the 1245 kernel?

1245 seems to be working sweet for me so far....
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This should have all the newest commits + WisTilt2's modifications. He said all but bzo's latest commits... I guess git died on him. I'll upload a new one if he builds another.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
First impressions on Rhod400:

Speakerphone volume is still fairly low for my taste...when the volume setting is at 1/3 it is barely audible...at full I have to hold it fairly close to hear all words clearly...

Also there is a lot of background "noise" when the external speaker is on...sounds like white noise or static...

Otherwise everything is running smooth...
[Touch Pro2, Tilt 2 Android Development] F22:
New Test Kernel (WisTilt2) - 2nd edition - Rhodiums Only

Info: WisTilt2 has another test kernel he'd like some helpful volunteers with rhodiums to test. This test kernel is based on the previous test kernel posted by Arrrghhh earlier in this thread. In addition, it adds bzo's overclock with pm.sleep_mode=1 patch for even better battery life when you're overclocking. So set pm.sleep_mode=1 in your startup.txt when trying this, regardless of whether or not you're overclocking. It also adjusts the volume level of the speakerphone mic to make it easier to hear. Please report any problems you encounter with these kernels, including but not limited, to battery life and speakerphone. Please also mention your rhodium model. They may not all behave the same. Thanks.

WARNING: This kernel is for RHODIUMS only. This kernel could potentially -BRICK- a non-rhodium. So only try this out if you have a rhodium.

Wifi:There is a possibility that rhodium wifi is broken in the stripped version. (WisTilt2 and I use different toolchains. He built it, I stripped it to reduce its size. Our toolchains should theoretically be interoperable, but the resulting modules file is half the usual size. So I'm not entirely sure about that.) If rhodium wifi doesn't work with the stripped version of the modules file, please give the fatter non-stripped version a try. Either way wifi isn't what we're testing here.

Rhodium Only - Kernel & Stripped Modules File(1.94MB version):

wistilt2-kernel-pack-stripped.zip

Rhodium Only - Kernel & Non-Stripped Modules File ("fatter" 8.69MB version, grab this only if you use wifi and the stripped version doesn't work):

wistilt2-kernel-pack.zip
[Touch Pro2, Tilt 2 Android Development] XirXes:
@pdawg17 the static is expected atm, but how loud is it compared to the actual call. same volume or pretty quiet?

People that post here, make sure to specify which model you have, eg. 100, 300. If you don't know you likely shouldn't be testing experimental kernels.
[Touch Pro2, Tilt 2 Android Development] thomas d:
Hey just to report back both kernels do not load it keeps saying that the sd card didn't mount then when I go back to an old kernel it works perfectly so i didn't even get a chance to test the new kernel. Hope it can get fixed so I can start testing for you guys. Thanks and sorry about the bad news
[Touch Pro2, Tilt 2 Android Development] solevi:
I have RHOD100_de with pm.sleep=1

Well i can say that:

1) The screen is not coming back from stand-by, it remains black while i will nor swipe the unlock pattern (from left to right). It was so on the first stages of kernel with screen turn off feature. UPD: actually screen backlight turns on, but screen doesn’t come back from black...

2) WiFI shows error

3) The in-call/speakerphone volume seems OK

4) Auto backlight function seems to be OK, since it was OK in other kernels.

5) unfortunately currently I don't have enough time to check how battery usage is, i will try to post later.

If You say me on what exactly to focus i'll give more info :-)
[Touch Pro2, Tilt 2 Android Development] pdawg17:
So far testing the Rhod kernel:

1) Wifi shows "error" with stripped or "fat" module...I have never had a problem with this on past kernels...

2) In-call volume is great...speakerphone volume is still low to me...the "noise" is lower/better than before but it was be nice for the voice to be a bit higher as in WM it is definitely louder...

3) A couple of times when I woke the phone from sleep the screen was very dim and did not adjust...it was like the auto backlight did not kick in...

4) Sleep mode=1 with my overclock is fine so far...it has woken up all 20 times or so...

5) Occasionally when waking the phone everything is slow/stuttery for a few minutes afterwards...this has occurred the last 3 kernels or so...

I'll keep it running today to see how battery life is...

Otherwise it is great! I'll keep testing!

UPDATE: Just realized my data at some point stopped working too...turning airplane mode on and then off fixed it...

UPDATE 2: Weird...once I did the airplane mode trick my wifi now works AND immediately the stuttering/slowness disappeared and my smooth phone is back!

Rhod400 (Sprint TP2)
[Touch Pro2, Tilt 2 Android Development] vnes1984:
Rhod 400. LED is not solid green but occasionally will turn on/off. SOD occured after sleeping for 30 minutes. Speakerphone is much louder but still has static
[Touch Pro2, Tilt 2 Android Development] F22:
This isn't built off of 1245. I believe it's built off of 1238 with WisTilt2's modifications on top as well as some of the newer patches like 1239 and 1241 added into the mix. I don't believe commits 1243-1245 made it into this test kernel.
[Touch Pro2, Tilt 2 Android Development] F22:
Rhodium 100 Panel Issue

Most rhodiums have an EID panel. Some rhodium 100's however have an AUO panel instead. The kernel doesn't properly initialize the AUO panel yet, it only worked before because Win Mo set it up and the kernel never fully turned it off. So now that the kernel is turning it off some rhod 100's aren't waking up. This issue isn't limited to just this test kernel, but exists in all recent kernels. ACL is working on getting the init info for your panel into the kernel. Hopefully it's just the two panels. Should there be a 3rd panel out there it will still be screwed until we can get a volunteer to grab the panel init info from it via haretconsole for us.

Both the stripped and non-stripped versions of the modules file? And are you getting the same stuttery slowness that pdawg17 is experiencing?

Good. That was one of the new things in this test kernel.

Good.

Get back to us on that one when you can. That's one of the new modifications that WisTilt2 is specifically testing in this kernel.

Battery. :)
[Touch Pro2, Tilt 2 Android Development] F22:
SD Card Issue

Back up your data via Titanium Backup (downloadable from the market) and try renaming your data.img file to something else. Android will recreate it the next time you boot and hopefully your sd card issue will be gone.
[Touch Pro2, Tilt 2 Android Development] F22:
Stuttery Slowness

The stuttering slowness means system_server was running amok on your handset. When it goes berserk, it puts a stranglehold on the cpu, preventing wifi and other things from getting their fair share of resources. This issue has existed for months, but it used to be much less common. It appears to be occurring far more frequently in newer kernels with the latest system.ext2.

Thanks for the feedback!
[Touch Pro2, Tilt 2 Android Development] F22:
Sleep of Death

Has the SOD occurred again since? Have you experienced this problem with any other recent kernels? Has anyone else experienced Sleep of Death with this kernel? (Not counting rhod100 users whose panels won't reinitialize after going to sleep. That's a separate issue.)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
LOL, thanks for takin care of mah thread F22 :D

Not much for me to do there tho :p
[Touch Pro2, Tilt 2 Android Development] solevi:
Already uploaded to ppcgeeks. :-)

And I did some more testing:

1) I've renamed data.img file and commented lines in froyo.user.conf (from tiad8's 3D Package post) to have a clean system.

2) Tried with stripped modules: Wifi shows error.

3) Deleted this newly created data.img file and tried to boot with not stripped kernel modules: Wifi seems OK.

As told pdawg17 screen lights up, then dim out. Sometimes it is working OK. This behavior exist either with autobacklight enabled or disabled.

Still not enough time to check battery :-(
[Touch Pro2, Tilt 2 Android Development] vnes1984:
I haven't experienced this with other kernals. well for awhile. I've since updated to the most recent kernal after the SOD. (working very well btw) It seemed the test kernal had very inaccurate battery readings compared to other kernals. I would hit the power on button to wake and the screen would flicker slightly, it wasn't until I swiped my thumb across the bottom of the screen that the phone would wake up. Once I left it sleeping for about an hour and tried everything to wake it up but no such luck. (rhod400)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Even if you turn it all the way up...? If you're just talking about initially, then I wouldn't worry about that.

Also, are you talking about in a phone call or just in general...? Music, ringtones, what?

I believe this kernel is specifically working on the speakerphone volume while in a phone call...
[Touch Pro2, Tilt 2 Android Development] pdawg17:
I can't speak for him but I think he means it is too quiet in phone calls...at least that is what I notice...when in the car and volume turned all the way up I can't leave the phone on my lap like in WM...has to be held up at about chest level to hear clearly....
[Touch Pro2, Tilt 2 Android Development] outerdepth:
Hey,thanks for all your hard work Arrrghhh! Just got a question. I have been using this kernel with great success on my Rhodium 210,but I tried that kernel that gets the camera working. It works on my TP2!! Are you gonna merge this working camera kernel with yours? It would be great to run that hybrid. I just don't wanna give up my camera now that its working on XDAndroid.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ha, I think this was asked already. Fairly simple answer, no. It's not my code... and WisTilt2 can't commit it until it's cleaner.

Same goes for viruscrazy - he can't commit his camera code until it's cleaned up & functioning.

So, there's some good news. viruscrazy said he'd do a git pull and grab the stuff from 1250 - which means at least the kbd backlight & camera :D

However, WisTilt2 has not committed his panel commits, as he still needs to get the AUO panel on-board (mostly RHOD100's). I have a feeling WisTilt2's will probably work out the panel stuff pretty soon, so hopefully it won't matter as viruscrazy has some serious work ahead of him getting the remaining camera sensors working. Sounds like the Blackstone's are going to be difficult, and AFAIK RAPH still has those colors reversed.

But, camera does work - and it's awesome. Deposited a check with USAA's Deposit@Mobile... freakin amazing. Just need an IPv6 kernel and Google Goggles will be good to go!
[Touch Pro2, Tilt 2 Android Development] Naadi900:
Backlight issues

Hey have been doing a bit of testing on my rhod100_uk (normal use) and find it to run great!

Keyboard backlight functions good, would love to have the light sensor integrated, that it only turns on in the dark like with winmo, but thats for later.

One thing that is different with this kernel in comparison with others is that autobacklight seems to be broken. Also if I do not have auto backlight turned on, the phone always goes to a middle brightness setting after it wakes up. So turning the lcd off and on resets the brightness to a lower level.

Problem is probably that this kernel had some problems with rhod100s, so can be ignored if thats the case!

Thanks for the fast progress lately everybody!
[Touch Pro2, Tilt 2 Android Development] vnes1984:
Yes that is exactly what I meant. Speakerphone volume in call is still too low and has some fuzz on my end. Music and ringtones are perfect.
[Touch Pro2, Tilt 2 Android Development] jchutch2:
My experience is the same. So I just don't use speakerphone. :)
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
1 week

I have been using this for about 1 week and this is what i can report.FROX3 Rhodium 400 Sprint overclocked to 700. Using the phone call haret startup to force usb headset (speakerphone still works). Sleepmode 2. No game applications. Just some standard apps like moviephone and skyfire for video and flash.

1.The keyboard lighting is great and continues for as long as you type. No hang ups or any problems.

2. Have had a bunch of complete reboots from turning on from sleepmode and not touching the slider area of the screen. Usually when this happens only the backlighting comes on for a few seconds then it reboots.

3> I have had several android only reboots while in the middle of screen or program transtion. Your guess is as good as mine.

4. If while making a phone call or receiving one the screen goes into time out it will reboot after the call, about one out of three calls. I confirmed this by setting the timeout to ten minutes and my phone calls lasting less it does not reboot.

5. I have had 2 days with good operation no reboots for the entire day.

6. The speakerphone works. I have only used this in phone calls since I am slaved to the usb headset. If I turn up the volume it is noisy. There is always some background noise on speakerphone. otherwise audio sounds great with usb headset.

7. Last night I left the phone off of the charger to see if it would last the night. It was off this morning no power. I recharged it and rebooted. It crashed once in boot to android from Harret. Wifi was knocked out. and titanium backup and my clock widget crashed over and over after each reboot. I rebooted 4 times each time was extremely slow had to do a server reset by activating google maps. Finally uninstalling and reinstalling both applications to get normal operation. It has been working well since then.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Unfortunately in California if I'm going to use Android in the car I have to use the speakerphone...that's why I'm thrilled it's working now and why I'm excited to try any new kernel that "tweaks" it...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Crap, meant to hit quote not thanks :p Can't unthank on XDA yet evidently, so free thanks for you ;)

I was going to suggest not using your phone while driving lol! Seems simple to me...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ah, about time I bumped this thread... first post updated guys.

Here's what's new - fixed touch to wake, caps/FN lights. More panel deinit stuff - should get significantly better battery drain compared to 1253 (assuming both kernels are sleeping - LED=GREEN!)

Enjoy, let me know how it goes!

EDIT:

I did find an issue, at least on my RHOD400 - caps/FN LEDs are reversed, and the caps lock doesn't necessairly always show the correct state. I'll let WisTilt2 know... other than that, let me know what you guys find!

I'd also be curious if the buttons are reversed for all devices - or if it's just the 400. I'm betting the 300 will be flawless, I'm curious about the 100/210 guys.

Update - Seems the touch to wake issue is still present for me as well... again, I'd be curious to see if anyone else experiences this - when the phone is sleeping (green LED) you have to touch the panel where the lock swipe is to wake the phone.
[Touch Pro2, Tilt 2 Android Development] SirBuzz:
Hey arrrghhh, I'm running the updated kernel you posted today on a 210 the caps/FN LEDs are reversed. However the buttons themselves are funtioning correctly.

I'm still have the wake up issue if I let the phone sit for over a min, but the response time is better then the last update.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Good to know, thanks for your feedback.

I noticed on the touch-to-wake issue if I let it sit, the screen usually does come on - but sometimes it takes so long it just turns right back off lol.

I'll pass on this info to him, thanks!
[Touch Pro2, Tilt 2 Android Development] SirBuzz:
LOL, same here...
[Touch Pro2, Tilt 2 Android Development] hdurina:
Apart from the issue that the lights are reversed, I have a problem where I don't have any signal reception. Can't blame the settings in startup.txt cuz it does work with other kernels. Am I doing something wrong here - is this kernel carrier specific? I'm on Rhod210 with TMobile

EDIT: arrrghhh is right. Don't think the kernel had anything to do with my call errors. The 1253 kernel was working perfectly - zero hangups and perfect wrt calls for 24 hrs....noticed the issue of no incoming / outgoing calls when I switched to the test kernel. Still doesn't work when I revert back to 1253
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm assuming you mean 210.

And this kernel has no effect on cell data... so there's something you're doing wrong.