yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 General] lieti:
Hi I still have problem with low space for application. I have prerooted XPF ultraclean, with one of first lagfix (by gsam101?). Because of lagfix I'm not able to estimte how much of free system space have. But I can see this problem for instance when I'm trying to update biger application (>1 Mb) via market, or install new app.Many time I'm unsuccesfull, only with FC (and then fc in many aplications in row and manual reboot). I'm pretty sure that is because of space for data. But I'm suprisef how this should be, because I don't have so much app, and also I removed big apps (like swype, all games). All apps whete it was possible I have on SD (via app2SD).

So I suspecting system that somewhere are unusefull temporal data stored (for instance .apk from many unsuccesfull updates). It is something like this possible? Can I fix it (via root explorer)?

Or,if is true that i really don't have free space. Can I extend it with fix for system data to converted SD partition (from developer forum) without necesarity of reinstaling all aplication?

I don't want to reinstall because for me it take so much time to get all app with configuration back, specially launcher with many preconfigured widgets. I will wait with reinstal,till some new custom rom based on source codes of 2.2 will be relased.

Thanks for any advice ;)
[Galaxy 3 General] rogue93:
try cachemate really helps me when in space crisis!
[Galaxy 3 General] lieti:
Thx for advice, but unfortinately it seems that I really have internal memory full.

So now is actual for me second part of question. Is it possible to use SD like internal memory without necessarity of reinstall?
[Galaxy 3 General] szewc1:
Sure is, sir: http://xdaforums.com/showthread.php?t=937328, post 170 for fix itself.

If you didn't already try it - app2sd http://www.appbrain.com/app/app-2-sd-free-(move-app-to-sd)/com.a0soft.gphone.app2sd, works only on android 2.2.
[Galaxy 3 General] lieti:
Hi, dakujem :)

I aalready using app2SD, but unfortunately still no place left.

I know abou this fix from your link (via XDA app is har to attach link). But my problem is that I have lagfix V2 by Gsam101 a I'm not sure if I can aply it with this fix.

Also I have many apps on SD (via app2sd) and I'm not sure if I can aply apollo's fix without necessarity of reinstal. And that is my problem and question.
[Galaxy 3 General] szewc1:
Nie ma za co ;) Well, you should try and ask about it in aforementioned topic. You can try (different lagfixes may be quite... different) apollo's remove_lagfix batch file (it shouldn't mess up with SD card, it just converts /system back to rfs). Quick way of backing up apps is using Titanium Backup, no need to move them to phone/to sd card. Of course copying all important user files from sd + titanium backup files is highly recommended precaution.

"Note: If your card is already partitioned into ext2 and fat32, rexecuting the lagfix providing the same amount of space for apps doesnt format the fat partition." - I'm afraid the same can't be said about creating ext2 partition (not sure though, lagfix may be smart enough to use free space only).

It's well worth giving it a try ;/ If it doesn't work out, you will know what you are standing at (reflashing to get it up and working).
[Galaxy 3 General] lieti:
Yes, that is true, but till now I wasn't able to write to developer section (10 post limit).

Second problem is that I don't have place even for titanium backup (but solution is simple..temporaly renove of few apps)

Bigger problem is that for few reasons (hospital) I cant make experminets.

But probably I will wait till new rom, based on source codes will by relased.

Present roms are +/- same, and also lag fixes.

But still, thanks for usefull advices ;-)
[Galaxy 3 General] lieti:
But anyway, still big thanks to all developer for custom roms and lagfixes :-)
[Fascinate General] diver47591:
After having rooted my Fascinate and installing ClockWork Mod Recovery, Rom Manager Premium, and Titanium Backup, I cannot get ROMs to download to my SD. I was only successful in getting one ROM on my card and as newbie I don't know why. Please provide list of settings to accomplish downloading to SD, Also when trying to install ROMs when booted to ClockWork Mod Recovery, phone displays:

In yellow:

--Install from package...

Finding update package...

Opening update package...

Verifying update package...

In red:

E:failed to verify whole-file signature

E:signature verification failed

Installation aborted

Please help
[Fascinate General] jenisiz:
Random, but did you flash the correct modem first?
[Fascinate General] nitroglycerine33:
Are you sure that you are in clockwork recovery and not the Samsung recovery? Have you flashed the correct clockwork through Odin? You need to have the odin flashed clockwork recovery to be able to install test zips. If you are trying to flash a froyo rom you will need to flash the red (voodoo) clockwork recovery.

Can you describe what steps that you have taken when clockwork was installed and what Rom you are trying to download/install. Thanks!
[Fascinate General] diver47591:
Install ROM abort

Frustrated and bummed. Would it cause problems or damage my phone to root phone again and re-install Odin 1.3, ClockWork Mod Recovery (voodoo or non voodoo?)? Already installed ROM Manager Premium and Titanium Back-up from Mkt.

Lost!
[Fascinate General] ziggy484:
Why don't you just do the all in one eb01 Odin? Then you don't have to even mess with clockwork, it's super easy. Look for it in the development section

Sent from my rooted froyo Fascinate
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] darkowler:
To start off with I am impressed with some of the newer builds of the wp7 os on hd2 as they have included the hd7 phone id built into rom making the Chevron mod very simple, but there are few more issues

1 there are many issues with live services even after u input os key

2 there are errors when it come to communicating with live services to download apps

3 phone still restart many times and will some times go into what i call a dead sleep ( its where phone goes into standby and will not go back into unlock screen) you have to wait 3-4 minutes and even then u r lucky if u don't have to pull out battery and reset phone.

4 although newer builds often allow u to have more unregistered apps working they still have communication issues with wifi/network

5. camera is working on some builds but after picture is taken it comes out a bit green

The point for this thread is for u to post your links to your favorite builds of the wp7 and help future development buy discussing pros and cons to different builds
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] darkowler:
my fav build

[19 Feb][ROM] blackSideSeven v1.2.7004

LINK: http://hotfile.com/dl/106013534/837ae7f/elMInStER.blackSideSeven.1.2.7004.rar.html

rom has built in Chevron

and phone id is HD7

when u install language is in Polish so just change it to English or what ever language u want

I have had more luck with this build than any other one i have used it is much less buggie than the other builds i have tried, if u don't mind changing the language give this rom a try
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] TheATHEiST:
All the builds are more or less the same at this point, this thread is completley useless. Future rom dev is helped by replying to the devs topics with issues etc.

I have none of teh issues you have, everything worked fine and no restarts. The green issue though is a well known bug.

PS. How has the rom got a built in "kitchen" :confused:, A kitchen is what is used to build a rom, So im confused on how the rom could have a kitchen built in?
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] zarathustrax:
+1.... I completely agree.

The only difference between roms right now is the lockscreen and maybe a theme color or 2. They all have same tweaks and features.

I think a lot of the issues that the op is having sounds like they may be cause by a sd card that wp7 doesn't like... try using a different sd card. Class 2 or 4 sandisk are usually good.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] darkowler:
I meant to say chevronWP7 sorry, i had a long day...
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] dazza9075:
pretty much everything on your list is SD card related and effects all ROMs if you have a dodgy card, available ROMs are just clones of the original release with a few mods which they all use, the reason for this is its virtually impossible to make the same kind of changes as in android or WM..

the green tint on camera is a driver issue, which can not be solved with cooks, the market place issues are largely SD related but the freeze is very much a MS bug, the main battery issue which you didnt mention is driver related

im not saying this thread has no point, but i am saying your a bit too early,

but in the spirit of the thread

Dont bother with any other rom just now, there is no point with patches just around the corner that no one on here is capable of using, other than the DFT team, many of the bugs on these other roms were created only after the rom was fiddled with in the first place, however, if your not capable of following the instructions and installing the DFT release than use one of the newer ones as its much much easier
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] zarathustrax:
There are no pros and cons to the different roms because they are all the same... same build, same tweaks... only difference is maybe lockscreen and theme colors. Thats why there is no point to a thread like this yet... not until there is a difference between roms.

Also, if your phone is restarting and having issues with it going to sleep like you said, that is caused by using a sd card not compatible with wp7. Many of your other problems are probably also caused by that. Try a different SD card. Anyone having problems with the phone restarting ever or any lag or freezing should try a different sd card. Problems like that are not from specific roms... like I said, all the roms work pretty much exactly the same.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] hatehaterz144:
all you have to do to fix the random restart is go to this link ( http://xdaforums.com/showthread.php?t=918993 ) that will fix it at least it did for me its a memory card problem
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] TheATHEiST:
@ zarathustrax

Can you please fix your quote in your post, Its making it look like I said all that silly **** instead of the OP lol
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] zarathustrax:
Ok, i edited my post a little to make it more clear that I was agreeing with you.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] orangekid:
agreed @ this thread is pretty pointless until there are actual differences in the ROMs. Otherwise there is no actual use to anyone.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] TheATHEiST:
hmm, no you didnt, still exactly same. No real harm, its just that I dont like been misquoted. :p
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] zarathustrax:
Oh, sorry. :o I thought you were talking about post#4.... I was wondering how that was not clear that I was agreeing with you... didn't even notice the other post til now. Your request makes much more sense now... sorry about the misunderstanding... it's fixed now. :)
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] CrAzYiaN:
i agree to, all the roms are the same expect some language. other the that

you still have to do the same

Problem with phone shuting off? it's your memory card

can't use marketplace? activate you phone that's it.

Problem with one side working on your headphones when

talking on the phone? Shut off xbox live restart phone that should work.

well it works for me.
[Fascinate General] rivaaaa253:
Whemever I flash a new theme on superclean 2.1 I run into bootloop?? Its so annoying! Is there anything causing this?
[Fascinate General] toastedoats:
are you flashing with ClockWorkRed?

I was getting bootloops using CWGreen, once i went to CWRed themes applied fine.
[Fascinate General] nitsuj17:
clearly this belongs in development...read the forum rules :rolleyes:
[Fascinate General] italysfinest327:
same thing happens with me but im not using superclean im using the debloated deodexed tar thats out there. and can confirm using xultimate i am deodexed
[Fascinate General] rivaaaa253:
I'm using clockwork red?? Its just so annoyingg!
[Epic 4G Android Development] amosher13:
Here you go, just ported to EB13, all 3 versions of this mod, flashable via CWM2 or CWM3 but you MUST be on a deodexed EB13 ROM. Will cut off the clock if you use 24hour/military time!

These 3 are NOT for Bonsai 3.0.1 OR SRF 1.0.1

Kill battery full popup only - Download

Remove AM/PM from statusbar clock - Download

Both mods together - Download

For Bonsai 3.0.1 (SRF already has both included)

Remove am/pm from Bonsai 3.0.1 - Download (For Bonsai 3.0.1 ONLY, ROM already has popup surpressed, this mod is retained)
[Epic 4G Android Development] greezestain:
Thank you! I've been waiting for this.
[Epic 4G Android Development] JudasD:
Very, very nice! Thank you!

JD
[Epic 4G Android Development] edonnelly:
Much thanks. The battery popup is incredibly annoying. The am/pm didn't bother me until you mentioned a fix for it, so now I want it gone, too. Looks like I'm downloading "Both mods together."
[Epic 4G Android Development] ericizzy1:
thank you for this. much needed
[Epic 4G Android Development] Nextelian:
You...are....da....MAN!

As a budding developer, do you mind if I ask how you did it?
[Epic 4G Android Development] amosher13:
not at all, truth be told i dont know crap about the actual coding behind it but i've search for how to's and use winmerge frequently to see how others have done it. i actually posted a how to for the am/pm thing for DK28, the steps were exactly the same:

http://xdaforums.com/showthread.php?t=954400

for the popup removal, i used this post, the line numbers are all different but if you search for text you can find what to remove:

http://xdaforums.com/showthread.php?t=793653

pm me if you need any additional help, or heck, just post back here so all can benefit
[Epic 4G Android Development] tmuka:
Excellent, thanks!
[Epic 4G Android Development] roghaj:
I applied this and now my phone won't boot. It does the thing like when you have a rfs kernel on a ext4 system (I was running ext4).

Time to wipe and reflash :(
[Epic 4G Android Development] styckx:
I installed this with zero issues on SuperNova ROM (EXT4/EB13) while using the Gingerbread theme. Flashed and worked flawlessly.

Thank you!
[Epic 4G Android Development] roghaj:
Knowing that this is possible, I decided to give it a try again. This time I entered recovery by way of the normal 3 finger method and it worked just fine. I don't know if the 4 finger method is what killed me, but I don't think I am using it anymore.

(4 finger method - press vol up dn camera and power while phone is on)
[Epic 4G Android Development] amosher13:
updated with Bonsai 3.0.1 compatible zip!
[Epic 4G Android Development] Kitteh298:
what is deodexed and how do i know if i am? also what deodexes me?
[Epic 4G Android Development] galaxyd700:
as of right now i am running bonsai 3.0.1 and gingerbread 2.1 but when i flash the no bat pop up and boot it up it just boot loops ...any idea why?
[Epic 4G Android Development] amosher13:
honestly, no offense at all intended, but if you do not know the answer to this question, you need to search and read up more, but it is likely that you are not deodexed unless you are on a custom ROM.

I updated the OP to make it more clear, sorry. the no-battery fully popup mod is not needed on Bonsai since its already included. and you cant use the standard version since the CIQ is now removed. only the bottom zip is for Bonsai 3.0.1. you might have to reflash the ROM if you didnt take a nand backup. hopefully you did.

either that or flash the bonsai 3.0.1 zip which will remove am/pm but should boot.
[Epic 4G Android Development] galaxyd700:
Yeah I did a nand backup and I reflashed bonsai 3.0.1...the am/pm and the no bat popup is still there
[Epic 4G Android Development] jocala:
Could you please share how to recompile/reodex services.* ?

Thanks!
[Epic 4G Android Development] amosher13:
sure, the original how-to is here but the command is

java -Xmx512M -jar smali.jar classout/ -o new-classes.dex

then just replace the classes.dex with the new one, renamed into the jar file with 7zip.
[Epic 4G Android Development] jocala:
Thanks for the tip and the link amosher!
[Epic 4G Android Development] jocala:
Ok, I added the new classes.dex into services.jar. It's 777,554Kb vs the original 313Kb. Does services.jar need to be re-odexed? This is going to be plugged back into a stock system.
[Epic 4G Android Development] amosher13:
Doesn't sound right, should be very close to original. Yes if its going in stock you should re odex. Try tanimns script if you don't know how. Deodex the stock system with script. Flash mod, reodex with script. But make sure you did everything right , I don't think file size should be so far off

sent from my mind to yours
[Epic 4G Android Development] jocala:
Thanks for taking the time to help! I'm doing this under Linux, btw.

1. I decompiled services.odex

java -Xmx512m -jar baksmali-1.2.6.jar -x services.odex

2. Made the changes to StatusBarPolicy.smali

3. recompiled the classes.dex

java -Xmx512M -jar smali-1.2.6.jar out/ -o new-classes.dex

4. Renamed new-classes.dex to classes.dex

5. Added classes.dex into services.jar

zip services.jar classes.dex

The original services.jar just contains a META-INF/MANIFEST.MF , hence the small filesize of 313kb. classes.dex zipped into services.jar = a final filesize of 777554.

Did I misunderstand the process?

edit: does the recompiled classes.dex = services.odex? I'm so confused :)
[Epic 4G Android Development] mkasick:
Perhaps this helps:

Attached is the battery popup kill patch I use. It works on EB13 & EC05. I'm not sure of the status of the other popup patches, but this one eliminates the popup and prevents the screen from turning on (if it's off). It preserves the notification and sound, which I find harmless. If you want to get rid of the sound too, you can replace /system/media/audio/ui/TW_Battery_caution.ogg.

First, you'll need smali/baksmali, as well as copies of services.jar and the existing framework odex files from your phone: /system/framework/{core,ext,framework,android.policy,services}.odex. Put them in a folder on your workstation along with the patch. Then run:

baksmali -x services.odex
cd out; patch -p 1 < ../platform_battery_full_smali.diff.txt; cd ..
smali -o classes.dex out
zip -9 services.jar classes.dex

Next, you'll need a copy of dexopt_wrapper, which I've also attached. If you want to build it yourself, the sources are in the AOSP repos. "adb push" dexopt_wrapper to /data/local/tmp on your phone, and the updated services.jar from your workstation to a folder on your SD card. Pull up an "adb shell" and cd to that folder. Then run:

/data/local/tmp/dexopt-wrapper services.jar /data/local/tmp/services.odex
busybox dd if=/system/framework/services.odex of=/data/local/tmp/services.odex conv=notrunc bs=1 skip=52 seek=52 count=20
rm services.jar

The "dd" step (make sure to use all the options, scroll the "code" box sideways) copies the SHA-1 signature of the stock services.odex, so that all of the odexes dependent on services.odex don't attempt to rebuild on reboot. This is safe to do as long as none of the method signatures in services.odex are modified.

Now, reboot into ClockworkMod, or another recovery that boots adbd. Pull up an "adb shell" again. Then run:

cat /data/local/tmp/services.odex > /system/framework/services.odex
rm /data/local/tmp/services.odex

which replaces the stock services.odex with the modified version.

Some notes: if you attempt to replace services.odex during a normal boot, the phone might flip out since services.odex is replaced while actively being used, which is why I recommend doing it in a recovery. You also can keep "services.odex" on the SD card instead of /data/local/tmp, but you might have to mount the SD card in the recovery then.

Also, keep a copy of the original services.odex and Odin tar files handy, just in case something goes horribly wrong you can reflash back to stock.
[Epic 4G Android Development] k0nane:
There's another item somewhere else that needs to be changed - I don't recall off the top of my head exactly where, but removing it kills the screen-on and sound associated with the popup. I want to say the method is notifyPlugCharger().

EDIT: Looking at my post vs. mkasick's above... o/` One of these things is not like the other... o/`
[Epic 4G Android Development] jocala:
Very interesting. I wasn't aware that cwm allowed access to adbd!

Edit: This appeared to work, thanks again! As an experiment, I took the services.jar I ended up with at the end of amosher's procedure and ran it through dexopt-wrapper. I'll give it a shot too.
[Epic 4G Android Development] mkasick:
Removing the call to StatusBarPolicy::showFullChargePopup is pretty much what everyone does to get rid of the popup, I think.

Probably where mine is different is in calling "PowerManager::userActivityWithForce" with the third "force" argument as false instead of true.

"PowerManger::userActivity" is the method that is responsible for brightening the screen & keyboard buttons and resetting the screen-off timeout. It's called by most (all?) notifications, but the difference is that for most notifications, if the screen is off, the "user activity" is ignored and the screen doesn't suddenly come on. The full battery notification, however, calls "PowerManager::userActivityWithForce" which does force the screen on even if off. Which is silly.

I don't really mind the notification itself. I don't think it's really necessary, but I could imagine a situation where I'm topping off my battery and would want to be notified that it's at full so I can unplug and go. A standard notification with sound is appropriate for that, although an option to turn it off would be nice.

But a "special" notification with a popup that screws with the alarm clock and throws the screen at full-bright in the middle of the night is outright obnoxious. Goal of that patch was to turn the "special" full charge notification into something that behaves like a standard one.
[Epic 4G Android Development] jocala:
mkasick's patch worked great.

I'd still like to learn how complete amosher's procedure.

And it failed. Upon reboot, the screen booted to the Samsung "S", eventually went black and vibrated a few times. Never booted fully up.

To recap:

1. Make edits to StatusBarPolicy.smali

2. java -Xmx512m -jar ../smali.jar -o classes.dex out

3. zip services.jar classes.dex

4. dexopt-wrapper services.jar services.odex (this was done on the phone)

5. copy services.odex to /system/framework

I feel like I'm right on the edge of grasping this. Thanks for the help!
[Epic 4G Android Development] mkasick:
Did you do the "busybox dd" bit on services.odex before copying it to /system/framework?

Odex files are dependent on each other. When one of them is modified, any dependent ones have to be reoptimized and cached. This is why booting the phone after an upgrade or new ROM takes a while.

The problem is that, with an odexed ROM, /system odexes can't be rebuilt because their respective jar/apks lack the original classes.dex. Which is probably why it crashed.

The two options are to run a deodexed ROM, so that the Dalvik cache can always be rebuilt from the original classes.dex. Or, if you're running an odexed ROM, to fake the signature (the dd bit) on any modified framework odex so that odexes dependent on it don't attempt to rebuild.
[Epic 4G Android Development] jocala:
Running dd did the trick for the amosher, et al edit, thanks. So, with any framework odex, when you tweak it you must run dd against the original odex to make sure the replacement has the same signature?

I feel like I really went to school in this thread :) I now have three working stock EC05 cwm zips, one with your patch, one with the delete showFullChargePopup() patch and one to restore stock.