yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] RyanTX:
Im not seeing anything, but thanks for the reply, it was a good idea.
[Droid Incredible Android Development] Metallice:
The issue with the gingerbread keyboard is apktool decodes & as amp; so & becomes &amp; and thats where the issues arise. you just have to change it back before recompiling.
[Droid Incredible Android Development] sk806:
I will make a zip for you shortly. I am making a few others to fulfill requests, as well. I have the Rosie.apk's already done, so just need to make the zips and post them up with screenshots....
[Droid Incredible Android Development] mrcrusha829:
Solid ROM man...... working beautifully so far. Bluetooth is working without issue as well. Tested streaming music and all the functions work. Definitely a keeper. Keep up the good work.
[Droid Incredible Android Development] sk806:
Thanks! Glad you like it.
[Droid Incredible Android Development] radiohead14:
hey man.. is it possible to have up to 5 apps on the dock like adw or lp? or are we limited to just phone, app drawer, and a 3rd mappable one?
[Droid Incredible Android Development] sk806:
Yeah, only 3 allowed if you want the sense widgets...
[Droid Incredible Android Development] sk806:
First, did you install the full or flashed? The flashover does not wipe you system.

The only way I know how to see what might be causing such high system usage is with a task manager.

I can make you a special version that will format everything (not sdcard) before flashing.

Let me know. Thanks.

Steve
[Droid Incredible Android Development] m1rked:
Awesome! Thanks again
[Droid Incredible Android Development] VZYGuy:
The 5x5_naf_camera is only 4x
[Droid Incredible Android Development] hgoldner:
I liked DevilDog's theme, but it was a little *too* dark for my eyes; I'd sorta like to see what your clear theme looks like. If flashing the color icons has to wait, that's okay by me; I'll just do the blue battery for now.

So far 1.3.2 runs smoothly, and I've got Ziggy's 3/18/11 beta kernel going for a test ride too.
[Droid Incredible Android Development] jdmba:
Ugh

Steve - I do not run task managers of any kind. I did the flashover and the problems started. I then did all wipes possible (CWM and HBOOT) and tried the full. That didn't help. Then I tried all wipes and did v1.3.1 with a nandroid restore. It is possible (with the exception of the nandroid; although not if Nandroid simply augments as well) that all the Magnolias are just upgrading each other, and nothing is actually really refreshing the phone.

I do not mind RUU'ing or PM31whatevering back to stock if necessary so as to force a complete actual rewrite (if it does it). If you can make a Magnolia 1.3.2 which does a COMPLETE rewrite of the system (except for the SD) card, that would be great too.

Regardless, I just am hoping for SOME solution which does a full install, in case some remnants are surviving. If no remnants could survive, then I can try a RUU.

Any thoughts are appreciated.

Thanks

Edit: I am trying a Virtuous flash which will be followed by a nandroid restore of my prior virtuous, which I will then use to check. Virtuous formats system and cache, and wipes dalvik cache and boot cache. Fingers crossed.
[Droid Incredible Android Development] sk806:
Please check you PMs, as I sent you a link to a ROM that will wipe data, as well, which is more likely your issue.
[Droid Incredible Android Development] sk806:
Yeah, the clear theme has a "bug" that cannot be fixed, as it would seem. Namely, the notification pulldown is semi-transparent with white text, but that text turns black if you press it. So lets say you press "charge only" to turn on disk drive" the text for "disk drive" would then be black and REALLY hard to see.

This is keeping me from releasing the theme. Devildog and another dev are currently trying to figure this out (I know a way, but it requires making all menus black, as well as all popups, which may look good, but I dread doing).

I will re-post the color notifications with a strong warning about mixing and matching with circle batteries and Devil's themes.

I will also send you the clear theme again, just in case you want to see.

Look for both tomorrow.

Steve
[Droid Incredible Android Development] Devildog8791:
I will put a disclaimer on my thread about the remappings. I haven't had a chance to theme the new ones yet. If I remember right, you told me that should be the only thing I would have to update.
[Droid Incredible Android Development] sk806:
Wow, my brain really must have been mush by the time I put these together. All those mix and match classes.dex and resources.arsc files. Sigh...I am pulling the mappings until I go over them tomorrow. Sorry about that, everyone.

Also, I pulled the flashover for a bit, just to test something that may be related to jdmba's issues with 3g that then led to his flashing fiasco. I do not believe it is the cause, but I want to be VERY sure before I re-release.

Steve
[Droid Incredible Android Development] Devildog8791:
One word: Dedication

Thanks for this.
[Droid Incredible Android Development] VZYGuy:
I flashed the full and I also am seeing high system use.

from the op - This ROM is compatible with clockwork recovery 3.x, but it is recommended that users use 2.x to flash this ROM, as the 3.x version does not always perform wipe functions properly.

[Testing Update]

(1) I flashed 1.3.2_full using ROM Manager with the 3.0.0.8 recovery, wipe and backup up. Had high system use draining the battery.

(2) Used recovery 3.0.0.8 did system wipe and davik cache wipe - reinstalled 1.3.2_full - still had high system use.

(3) Reflashed recovery 2.5.1.2

(4) Used recovery 2.5.1.2 did system wipe and davik cache wipe - reinstalled 1.3.2_full - ALL IS WELL
[Droid Incredible Android Development] sk806:
Anyone else?
[Droid Incredible Android Development] m1rked:
Nope, I used the flashover and everything seems fine.
[Droid Incredible Android Development] sk806:
Thanks. Please keep input coming everyone.

Sent using XDA Premium App
[Droid Incredible Android Development] hgoldner:
I did a full flash, thought things were good, but, yes, it's behaving like it did on 1.3.1 before the battery fix.

Android System running near 60%.
[Droid Incredible Android Development] jdmba:
Welp

I was closer to 80%, which caused SpeedTest.net to be jumpy (work in spurts). I am going thru a lot of different types of installs and restores trying to get a working system. Steve is helping and I will report back.
[Droid Incredible Android Development] Wishka233:
Flashed over and have had no problems. Battery life seems great and no unusual system usage.

Thanks Steve
[Droid Incredible Android Development] inspeckta_dek:
Installed the bnb theme n it threw it into a loop. Anyone else with the same problem?
[Droid Incredible Android Development] jdmba:
Hmmm

Anyone know if you can do a nandroid restore of a custom ROM (e.g., Magnolia) over a pure stock ROM (without installing the custom ROM first)? Thanks
[Droid Incredible Android Development] LlirasChosen:
1.3.2 seems to be working fine for me and I did a flashover, usage doesn't seem to be abnormally high (cell standby 32%, android system 29%, phone idle 27%, display 10%), nor does battery drainage. One thing I don't see is the app for the power widget settings that you have starred in the changelog. Actually download speeds seem slow, will test in the morning.
[Droid Incredible Android Development] jdmba:
Grrr

OK - I went nuclear here.

First, since I was S-Off I went to Doug Piston's site and got the RUU and the CWM

http://dougpiston.com/?p=133

Then, I ran the RUU, restored to pure stock (I think it does the OS, the Kernel, the Radio, and the HBOOT)

Then I put back CWM through HBOOT from Doug Piston's site.

Then I checked speedtest.net which seemed to run MUCH better (although I do remember higher readings). I suspect NOTHING should have survived the RUU.

I then restored my Magnolia v1.3.1 Nandroid Backup (without installing Magnolia 1.3.1; is that ok). The upload is still jumpy, the download seems ok. I think I will just have to live with things in hopes someone else figures this out.

If I MUST install Magnolia v1.3.1 before I can restore a nandroid of Magnolia 1.3.1, please someone speak up; and I will redo the process.
[Droid Incredible Android Development] LlirasChosen:
Nandroid is a full image backup, it shouldn't matter where your coming from. So whether your from a fresh stock root or a 40 flash run, it should work the same. At the same time nothing should be touching the nandroid backup, but it does become corrupted sometimes as it is just a bunch of files on your sd card.Have you tried a *228 for the PRL update and not just a reprogram?
[Droid Incredible Android Development] edbro9:
I also did a full flash. With 1h 10m since unplugged: Battery at 84%

Android System - 46%

Cell Standby - 16%

Wifi - 16%

Display - 14%

Idle - 8%

That is with very heavy usage.
[Droid Incredible Android Development] edbro9:
I am experiencing a weird issue with the market that I have never seen before installing 1.3.2.

I have installed several apps since the flash and about half of them will download and then disappear. I see them downloading in the notification bar but after that the download icon disappears and nothing happens. I don't get any error msgs and the app isn't in the drawer. When I select it again in the market, it will redownload then install. I've seen this happen about 3 times now with around 6 different apps.
[Droid Incredible Android Development] jdmba:
My Take

Steve (and everyone else) - I am not a rom cooker by a long shot, but I suspect I have figured out why what is happening, is happening.

Magnolia is a great ROM not only for stability but because Steve is so responsive. We have a lot of great lockscreen mods, dialer mods, battery mods, etc., and Steve has been bending over backwards to make sure that no one has to reinstall anything.

I think that may be the problem. With each ROM release simply being an overlay over the last, we may be suffering from an inbreeding situation. No old junk gets cleaned out, and the same stuff keeps getting laid over existing stuff.

I am wondering if it would be best for Steve to release 2 versions of his ROM: the overlay for those who feel that is a good way to go, and for the rest of us (and certainly for those coming from another ROM), a release which does what Virtuous does ... format system, format data (but not datadata; a directory name I just got, and its kinda funny), format dalvik cache, and format boot cache. THEN write out system, kernel, etc.

Since we can all use CWM to format (not wipe) data, datadata, cache, etc., there is really only one thing we can't do, and I believe THAT is the problem which can underly the symptoms. We can't erase system to clean out the bad DNA. SOME version of the ROM release should format system (and data and dalvik and boot cache).

Thoughts?
[Droid Incredible Android Development] caleris:
Why not go into Recovery and do all the Wipes manually instead of letting CWM do them? There is a lot of annecdotal information on this forum that CWM is not doing complete wipes.
[Droid Incredible Android Development] edbro9:
I did the "Clear Storage" on the bootloader page then I wiped all the caches in Recovery. That might have been redundant but I'm not sure. I had to reactivate the phone but it did clean out everything.
[Droid Incredible Android Development] rfarrah:
Yeah, that's what I do, too: manually wipe data, cache, and dalvik.

Although I've never felt like I had to do it, I've seen in other threads where users wipe several times just to make sure its a clean install.

Also, a previous post suggested doing a *228 prl update RATHER than the "Option1 - program". FWIW I've been told that Option 1 checks for programming AND PRL update.
[Droid Incredible Android Development] Taebom:
no one likes to be dirty, i make sure to wipe twice :)
[Droid Incredible Android Development] BSquaredB2:
I agree. Isn't it just good practice to manually backup and then wipe everything, at least once, before flashing anything (ROM, mod, or theme)? A flash-over-the-top-of-something version seems redundant to the normal full ROM flash (unless it serves some other purpose for Steve).
[Droid Incredible Android Development] jdmba:
Welp

I think the point that continues to stand, even with all the above .... since this is not an update to angry birds, but is an update to an operating SYSTEM; perhaps wiping the \SYSTEM as part of the install might be a way to avoid this potential (well, not potential here) problem in the future, at least in the form of a second release????

(Oh, and to the prior posts, CWM *is* Recovery so I am guessing you meant to wipe in HBOOT?)
[Droid Incredible Android Development] hgoldner:
I think the difference is doing "recovery" tasks from ROM Manager, versus doing them from Recovery directly. The troubles I have heard described with CWM are almost exclusively related to 3.x.x.x iterations of the recovery, or doing things via Rom Manager (i.e. sending commands to recovery through ROM Manager) such as wipes, etc.

For now, based on the complaints, I've stuck with 2.5.1.8 and I don't let ROM Manager do anything at all. I've even had a Nandroid started in ROM Manager go south.
[Droid Incredible Android Development] nervana1:
I flashed the rom and everything but some of the trash was left over, like failbook and quitter and that peep crap, and tard stream. I removed them with Titanium but this cause my menu to not work, is there a way to remove all this social network crap?
[Droid Incredible Android Development] jdmba:
Yup

Don't want to start a flame war, but I wouldn't let Rom Manager tell me what time it was, much less do anything else. CWM is the only place I do anything (possibly augmented by cleaning through HBOOT), and I am sticking to 2.5.1.2 because of problems with 3.x.x.x. Even with all that, the Magnolia problems struck me so ...

... still hoping to hear back from Steve re my theory :)
[Droid Incredible Android Development] edbro9:
Correct me if I'm wrong but ROM manager won't even work with CWM 2.x. I tried it a couple of times but it always broke. I uninstalled ROM Mgr and never looked back.
[Droid Incredible Android Development] jprow507:
I've gotten ROM Manager and CWM 2.x to work fine. My only issue (depending on the ROM) is that with some ROMs, ROM manager will not automatically reboot the phone after I choose an option like backup or install ROM from SD card. I have to manually reboot into recovery and then the whole process begins without any intervention from me.
[Droid Incredible Android Development] hgoldner:
No, ROM Manager "works" with CWM 2.5.1.8, which is a modded version of CWM (by kernel developer Chad0989), who enabled it to support multi-touch (3+) on the Incredible.

I say it works, but fact is it's just taking up space. It made sense when I ran Virtuous ROM. It is completely unnecessary under Magnolia and any other ROM that doesn't download via ROM Manager. No disrespect to Koush intended, but it's just not very useful at this particular stage.
[Droid Incredible Android Development] edbro9:
I just checked mine and I have 2.5.1.2. Maybe that's the difference. I think I'll try to find a source for 2.5.1.8
[Droid Incredible Android Development] edbro9:
Is there a way to update Appfolders? It won't update or uninstall. No script in GScript.

Second question. What is the GenieWidget that has an uninstall script?
[Droid Incredible Android Development] nervana1:
So any idea on how to remove the Bloat?
[Droid Incredible Android Development] Devildog8791:
I was using CWM 2.5.1.2 for a while, but I started noticing remnants from the prior install still present in a fresh install (I never do a flashover and I always do all the wipes three times). I tried going to CWM 3.0.0.8, but I was not trusting the nandroid backups with that version. I tried going to CWM 3.0.0.7, but that was not wiping correctly as well.

I am now using Chad's modded CWM 2.5.1.8 effective this morning (since hgoldner seems to have no problem with it) and the jury is still out on that one. So far it looks like it is doing the job. I had no remnants from my prior install that I could see at this point.

I am with jdbma on the wiping commands being present in the rom. I think that a lot of the problems that Steve has to deal with branch from the fact that it does not do it when someone installs the rom. When I ran Redemptive rEVOlution, it wiped with every update, but he started including a flashover version with a disclaimer about doing it at your own risk. HeyIt'sLou always recommended using the rom with the full wipe.

I know that it is a pain in the ass to set up your phone again, but I would rather have a phone that works than to have one that is easy to get up and running again.

I believe that when Magnolia 1.4 comes out, Steve could do one version where it wipes everything and see how many problems he faces at that point. Then after that, future updates that he releases could have two versions: a flashover and a full rom that wipes.
[Droid Incredible Android Development] Devildog8791:
You would have to go in with Root Explorer and physically remove App Folders and then reinstall it from the market. You will lose the transparency that Steve has added to it though. It is located in /system/app. That is why you can't uninstall it.

The Genie Widget is the news and weather widget from Google.
[Droid Incredible Android Development] Devildog8791:
Which bloat are you referring to? There are scripts in the Magnolia folder that were pushed to your sd card during installation that has removal scripts for some of the apps. Use GScript to remove them. Directions are in the post #3.
[Droid Incredible Android Development] nervana1:
I am referring to Fail book, Qwitter and that failstream social bloatware. I removed it but it killed my menu button on the home screen
[Droid Incredible Android Development] edbro9:
Did you remove them with GScripts? I also removed them and I have no problems.
[Droid Incredible Android Development] nervana1:
yes I did use Gscript
[Droid Incredible Android Development] jdmba:
More and More

Virtuous does it too. Now I am wondering if Magnolia is the only ROM that DOESN'T format the system, data, etc.

While we still haven't heard back from Steve, I wouldn't mind if v1.3.2 was re-released with the formatting in the install script.
[Droid Incredible Android Development] edbro9:
Would having the ROM do it's own wipe be any different than the wipe we can do manually through CWM?
[Droid Incredible Android Development] Devildog8791:
Yes. Depending on what version of CWM you are using, it may not be wiping correctly. This would ensure that the proper caches are being wiped in preparation for the rom install. This could possibly be the reason for al the problems that are reported.

Having the update wipe everything would put everybody on the same playing field and would alleviate any questions as to whether someone did the proper procedures before installation.
[Droid Incredible Android Development] rbt2:
Regarding system usage, and note I'm using Chad's 2.6.32.27 Incredikernal 1232010 which may make these stats invalid. Not sure if these stats just complicate the discussion.

I flashed the 132 Flashover using CWM 3.0.0.8 thru ROM Manager. Don't know if these stats indicate good or bad performance. Comments?

At rest (sleep):

Cell Standby 32

Bluetooth 29

Phone Idle 31

Android System 6

Display 2

After use:

Android System 51

Display 18

Cell Standby 14

Bluetooth 14

Phone Idle 3
[Droid Incredible Android Development] sk806:
Hullaballoo

OK, so I see a lot of conversation about formatting, wiping and whatnot. Well, I can tell you this: ALL Magnolia releases, except for the flashover version of 1.3.2 (which, I admit, was a failed experiment), wipes your system, cache, dalvik cache, boot cache, and battery stats, just like every other ROM does. The only thing it is does not wipe is data (again, just like pretty much every ROM). Why? Because people would have to reinstall all their user apps (Ti-backup) and restore their settings (manually) every time. Now, I personally would LOVE it if I could just add delete_recursive("data", "/data") to the script, and clean the whole damn thing out. In fact, I spent at least 2 days trying to figure out how to get android to recognize the flash 10.2 upgrade with working Hulu without wiping data/app/, at least. Wiping data also clears up any market-related goofiness (apps installed are not under myapps, etc). The whole ROM works so much better/easier with a data wipe (or at least /data/app), it's ridiculous.

I am happy to make my ROMs that wipe all partitions including data (wouldn't wipe sdcard, or course), and you, the user will be responsible for backing up your apps and re-entering your settings after each flash. Or, I can do like everyone else does and keep my updater-script as-is (wipe all but data) and say a full wipe is strongly recommended, which perhaps I should have done all along. Given the problems with clockwork recovery, a third option is to make a full-wipe version (so you don't have to rely on cwr to wipe data) and a version that wipes all but data and post a strong warning about using the latter (which I believe jdmba is suggesting).

So, in the end, we cannot have our cake and eat it, too, which is unfortunate, because never-ending cake would be nice. You, as the users, decide, and let me know.

Steve

PS - Is that how one spells hullabaloo?
[Droid Incredible Android Development] sk806:
Hi, happy to help, but I am confused; your earlier post said you used Titanium backup to remove the apps, but it was gscript? Also, do you mean the actual menu soft key (the one that says menu and is under the screen) is not working?

Thanks.

Steve
[Droid Incredible Android Development] sk806:
Is there a newer version of AppFolders (post 1.5)? 1.3.2 has 1.5 in it...

I am going to move AppFolders to data/app for the next release. Basically the developer did nothing for months and months with the app and suddenly is going nuts with updates (a good thing). If the app is in data, it will allow you to upgrade on your own, though you will lose the theme.
[Droid Incredible Android Development] edbro9:
I've got 1.1.1. I bet what happened was I overwrote it with my older version when I did a Titanium BU restore.
[Droid Incredible Android Development] Devildog8791:
I vote for a version that wipes everything but the sd card. I do it on my own now, but I do not have the faith in CWM that I used to. I have no problem setting my phone back up after a backup.
[Droid Incredible Android Development] caleris:
For what it is worth, I always do all the wipes through recovery and then use My Backup Pro to backup and restore apps and user data for them. It is slow but it works very well.
[Droid Incredible Android Development] sk806:
OK, here is a flashable zip of the latest app folders (1.5) themed and all. Don't forget to redo your Titanium backup ;).

http://dl.dropbox.com/u/22769554/Misc/New_AppFolders.zip
[Droid Incredible Android Development] LlirasChosen:
I concur, until the flashover update for 1.3.2, I've always done a full wipe including data, then would just reinstall TiB and reinstall all my apps that way, not settings as that can cause problems. I'm in the mindset of some of the mainstream devs on XDA with the whole if your not willing to rebuild your device every time you put in a ROM than rooting isn't for you. To make it easier for those who don't speak up and for those who are mixed is there anyway to run script prompting the user to either allow a full wipe or not? That way they can decide if they want to wipe /data or not, or have the script wipe it for them.
[Droid Incredible Android Development] BSquaredB2:
Agreed.....but because I am me, I'll probably manually wipe everything too since I'm Incredi-anal. :)