yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace S5830 General] alexzon:
Just some words from a pseudo-noob:

I've flashed two roms in my new Galaxy Ace and about 10 roms in my old HTC Touch. I've never bricked my phone and nothing never went wrong or different from the tutorials.

Maybe it's luck, but I have another guess, and I'm posting some tips here:

* I believe most of the time bricking happens is when you interrupt the flashing process;

* So, try to do the flashing process with:

- Phone with full (or almost full) battery;

- Notebook with good battery or Desktop with a good nobreak;

- An stable operating system. Be carefull with softwares that "steals" CPU in the middle of other processes or that asks to reboot your Desktop. The last thing you want is to reboot your PC while flashing a rom.

And the most important, in my opinion:

* Don't be lazy! Read a lot from the forums. Post your doubts and clear them. Be sure you're using the right software and version, the right files etc.

Sometimes we want to test a Rom or a software very quickly but the time we spent to gain some knowledge about it is worth it, it can free us from bigger problems in the future or even from a bricked device.

--

Sorry about my English.
[HTC EVO 3D] runeazn:
So i heard it got a good magnet on it, So i wanted to do the inductive magnet mod. from this here : http://www.goodandevo.net/2011/07/h...se-with-palm-touchstone-wireless-charger.html

But wont it have any negative effects?

magnet + electronics= bad results
[HTC EVO 3D] hdad2:
runeazn,

Sorry I missed it for a bit, but I did answer your question in the other thread. :)

I'd remove the magnets or plan to live without the compass (which is not a big deal really). Otherwise, no real negative effects. Keep in mind that my touchstone coil is in the hard case, not in the phone back cover. So I don't notice any bulge or anything.
[HTC EVO 3D] Drewmungus:
Heres a thread where a guy put one into his case, might be a good idea to ask him.

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

Seems cool and I've considered it before but I have micro usb cables surrounding me all day.
[HTC EVO 3D] runeazn:
i know but well i wanted thoughts of other people too
[Atrix 4G Q&A, Help & Troubleshooting] rpolansky:
Can someone tell me where to find the 2.3.4 stock webtop image? i need to flash it. I installed a rom and then used CWM to restore my basically stock GB. All was good but the webtop was gone so I installed the modified V2 per Joe Ferreira's thread. Webtop was back but the Citrix client crashes.

Thanks!

Ron
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Alright guys. Going to use this thread as a way to brainstorm about ways to improve the speed. Read up what I've posted, let me know if I did anything wrong... Also let me know what you guys do to improve speed!

Don't care about what build you're running, this thread isn't about what build is fastest - this is a how do I make every build faster thread.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I've noticed Starfox's test kernel with that turbo mode enabled actually creates quite a boon. It's RHOD-only, so I didn't include it in the first post...
[Touch Pro2, Tilt 2 Android Development] vinceweis:
I noticed that these settings are written in the /init.cfg/init.froyo.rc file. If I make the changes there, will they be permanent? Is this still the file that loads with FRX07? I am still playing with the settings so I have not tried to make anything permanent yet. I was trying to minimize the number of mini-reboots after an install. The new ext4 seems to help a lot, but I was still playing with this also.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, that will definitely make them permanent.

I also thought using the user.conf file would, but someone PM'd me and said that didn't work...

I also was shown that there might be a much easier and more thorough way of doing that step... Seriously considering redoing that whole topic because of this:

[Script] V6 SuperCharger! HTK & BulletProof Launchers! The ONLY Android MEMORY FIXER!

I still need to verify if it works on my phone, but I don't see why it wouldn't...

Bah, it seemed to work but isn't persistent on a reboot... I'll try to figure out why. I see some issues with stock ROM's, so perhaps the issue is similar...

Edit - OK, using Script Manager I think I figured it out... I will update the first post with directions on how to use that "SuperCharger" script in lieu of the manual method.
[Touch Pro2, Tilt 2 Android Development] ACoolGuy:
I went ahead and began using this script. Not sure if the phone is any speedier yet, as I just got the 99Charger script to run at boot using script manager. Will report back my findings. Im using the Aggressive 1 settings with launcher set to bulletproof.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yup, seems to reapply the settings correctly on a reboot. The only problem with Script Manager doing it is obviously the settings don't get applied until well into the boot process - well after the UI has come up.

Not the end of the world, at least it does get reapplied correctly now.

One last thing - in the article it seemed to indicate the 'bulletproof' method is no longer advisable, and the 'hard-to-kill' method should be utilized.

I'm going to rewrite the first post now.
[Touch Pro2, Tilt 2 Android Development] ACoolGuy:
I went ahead and set the launcher to hard to kill. Also I have manually editted /data/99Chargerminfree with your minfree values and it now boots with your minfree values, which im happier with. ill have to run it thru the paces to see if memory is managed as well as he claims.
[Touch Pro2, Tilt 2 Android Development] nasapunk88:
autokiller memory

I've been using this app, AutoKiller Memory, from the marketplace and it seems to be working fine. You can put in the values you want for the 6 fields and in settings enable "apply settings on boot". I've ran

# cat /sys/module/lowmemorykiller/parameters/minfree

to double check after my reboots and without touching the app these changes took affect =). Of course like you said for script, it won't happen right at the start of the boot process.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
That app seems good. It just adjusts the underlying values for Android's memory management, which is exactly what we want. Kudos.

The reason I didn't want an app was a) I don't want more overhead and b) I wanted to have control over it. I wanted to be damned sure the values that were changing were what I wanted to change, and not something else.
[Touch Pro2, Tilt 2 Android Development] großa:
Seems to work fine, so far.

Edit: Have to use "Aggressive Setting 2", otherwise Xenonia 3 won't start.
[Touch Pro2, Tilt 2 Android Development] fortunz:
No launcher redraws? Assuming that means what it sounds like, I friggin hate those. That's a huge part of my android wait time. Can't wait to try this, thanks. :)
[Touch Pro2, Tilt 2 Android Development] großa:
Found this script:

Ram Optimizer

Changed my froyo.user.conf to those settings (except lowlevelmemorykiller, using the supercharger script).
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Reading thru that, it seems redundant to that wacky SuperCharger script. OOM - already set, virtual memory - already set, and minfree - already set...

Honestly, that SuperCharger script does anything you could want in relation to memory/RAM. It's a little odd the way its laid out, and there's some qualms I have with how that guy arranged his post... but the script is all-encompassing. No need for others... they will literally bash heads with eachother... In the thread you linked to, it even mentions that if you've done other tweaks like this with other scripts, you should delete those scripts from init.d. So I would recommend the same, if you're going to use different scripts on boot, remove any other entries you have from the SuperCharger script. If you followed my directions, I use the startup script in /data/99SuperCharger.sh.
[Touch Pro2, Tilt 2 Android Development] großa:
Yes I'm using the 99supercharger.sh on boot. I missed that supercharger also changes OOM and VM (thanks for the info), so I thought it can't hurt to change the froyo.user.conf directly. It should be logic, that 2 scripts, which do almost the same, will conflict.

BTW, did you try the 3G supercharger or the kickass kernel tweak?
[Touch Pro2, Tilt 2 Android Development] fortunz:
I haven't had any launcher redraws since installing supercharger EXCEPT for keyboard induced orientation changes, which is a nice improvement for me. I'd like to get rid of the orientation change redraws too, since I gain nothing from the launcher itself going landscape anyway.

It did seem snappier, even not taking redraws into consideration. A link in the v6 thread claims the performance increase comes from the free ram being used to cache the filesystem. Not too clear on what "filesytem" means in this context (surely not the disk level filesystem, ext/ntfs/fat, I figure it must be linux terminology), still reading up on it, but if anyone felt like expounding a bit, I'd be grateful.

I seem to recall from searches yesterday that there are a couple of 3rd party launchers that will let you lock in portrait orientation for the launcher only. I'll probably try Zeam later, don't see an option to lock against keyboard slide yet, but it's worth a try. Maybe if it switches back and forth faster, I won't need the lock.

My searches for a plaintext, no icon, no wallpaper launcher have come up empty so far. Zeam looks to have the smallest footprint. I've seen plaintext theme screenshots that I think was from LP+beautiful widgets, but what good is that if your footprint is still huge?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I actually did not try those yet. It seemed like he had just started experimenting with that, and I was just trying to get the memory stuff hashed out.

Kinda wondering how it'll react with our build/kernels. But I guess it's worth a shot, worst case seems like a bootloop - might want to try it on an isolated setup before you move it to your main build ;). Let us know how it goes if you do try it!

Well, even tho we aren't using traditional file systems as you normally would, most of our files are in ext2. The data.img, the system.ext2 :p. I believe the rootfs.img is as well. They're just files that have entire file system structures and files underneath them - much like an ISO disc image if you're familiar with that concept.

I have heard good things about Zeam. I like ADW, but I haven't run much else than ADW and LauncherPro. Honestly only gave Zeam a whirl a few times, but it does seem snappy.
[Touch Pro2, Tilt 2 Android Development] fortunz:
Yikes, Zeam is snappy, right up until an orientation change redraw, then it's even slower than the default launcher. ADW might be better for me even at twice the footprint because I'm pretty sure I remember that one has an option to lock in portrait. I was at peace with redraws until I read this and managed to cut them down dramatically, and now that I have a taste of freedom, my contentment is shot and I need them eliminated entirely :o :rolleyes:

First, thanks for expounding. :) I am familiar with disk images/isos. Are you saying that underlying disk structure is what is being cached in "free" ram by linux? :confused: If so, I'm even more confused than before and maybe this is just beyond my ability to grasp. I assumed when he said the filesystem was being cached, it was a reference to actual files that happened to be called a filesystem in linuxese. Like registry type stuff or some such.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, maybe I didn't explain that right.

Cache is basically a buffer to store things in. So Android uses cache to store frequently opened programs, etc. It keeps them in memory (RAM) as long as possible before it's necessary to free up that RAM.

So nothing is actually being cached on the file system, all is being cached in RAM. The hurdle here is the stuff that is being cached in RAM normally has to be accessed from the file system - but if it's already in RAM, it's much faster to access it that way than going thru the file system to find what it needs.

It's not the entire file system, just apps or any outside things they might be accessing. To keep it simple, we'll say just apps :p.

I hope that makes sense...
[Touch Pro2, Tilt 2 Android Development] Starfox:
Actually, not quite. There's two different forces at work here.

1) Linux's own cache (called buffer). Basically, Linux (the kernel) uses any free memory to keep blocks of memory (called pages) in place. This could be anything from contents of files, program (code), working data, etc. The kernel knows which of those are expendable, ie "clean", and if more memory is needed simply discards it so there is very little penalty in keeping pages in memory as opposed to having real "free" memory. If it runs out of "clean" pages it goes to the "dirty" ones where data has to be written back to disk, either as data or as swap, which does incur a penalty.

2) Android's own cache, which is basically "keep as many app loaded as you can". This is what minfree affects, and while it's good in theory, it does not necessarily work out that way. Reason being is that while it is true that it takes time for an app to "load" from flash, truth is that the majority of the app that it picks aren't being used or will not soon. Also, apps when loaded uses CPU, and when it needs to get shut down, must do housekeeping work. Basically Android tries to use the shotgun approach, hoping that the stuff it keeps in memory happens to be app you will use next. This is why when you use a task killer, you see a list of app that aren't even being used being killed off, then reloaded again when Android "detects" it has free memory to play.

The magic is to try to find a good balance between the two. Stock FRX07 heavily favors Android's cache, and mine basically opened the headroom so Linux's cache can work it's magic.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] fortunz:
Thank you both for expounding. Starfox's discussion of the linux buffer seems to be what hardcore was discussing in the link and clarifies things for me. I'm still not clear on what linux is caching. Would elements of Android itself (the OS, settings that might look like winmo registry stuff, libraries OS services and processes etc) be juggled by kernel in that space, or does it all always fit in active memory? And when you mentioned it storing program code, would include elements called by the dalvik jvm (or routines from applications running natively) rather than actual applications themselves like android is holding in ram? So for example, I've got a dictionary that does writing recognition and does OCR from photos, pretty sure it's a native app, not java, when it reaches out to do one small task -- is that element or class one of things potentially stored by linux in case I do the same thing over a few minutes later while the application itself wouldn't be stored in linux cache? Any additional exposition is appreciated, none is expected.

Hardcore mentioned he had 90MB in use by the kernel in RAM that Android wasn't using itself. That seems like an awful lot of space, and yet I can't argue with the results. My system does feel more responsive now.
[Touch Pro2, Tilt 2 Android Development] zeppelinrox:
I think it worked...

do:

cat /sys/block/*/queue/scheduler

The unknown key means that your kernel doesn't support those particular sysctl tweaks so it's nothing to worry about.
[Touch Pro2, Tilt 2 Android Development] großa:
Ok. Gonna try it again. Thanks :)

Edit:

$ su

# cat /sys/block/*/queue/scheduler

noop anticipatory deadline [cfq]

Is that ok?
[Touch Pro2, Tilt 2 Android Development] großa:
Found the app "Autostarts" (not free, but not expensive ~1$) which is able to deactivate autostarting apps very good.

See here:

autostarts

There's also an interesting app named "Wifi Lock" :

wifilock

Or this one:

root-uninstaller
[Touch Pro2, Tilt 2 Android Development] Starfox:
Ask Dr. Google what "Linux Memory Management" is.

Android is an Linux program, just as Flash or JVM or VirtualPC is a "program" as far as Windows is concerned. Just because it does Dalvik or basically hooks into everything hardware-wise doesn't change the fact that program needs to have code and manipulate data in memory.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] fortunz:
ADW's redraw on rotations is quicker than either the stock launcher or Zeam for me, but it's still not exactly instantaneous. Hopefully System persistent (the only apparent way to disable rotation) is as good as hard to kill (which has to be disabled to use sys persist), because it would suck having to choose between random dead launcher redraws and orientation redraws. I'm so close to redraw freedom I can taste it. It tastes like strawberries. :cool:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I shuffled things up and added another topic - but it's Topic #3 because of the sufflings.

I'd really be curious to see if it does have a positive effect on the mini-resets people are experiencing in FRX07 that they did not experience in FRX06. Obviously they can still happen, but tweaking this setting seems to at least partially prevent it...

So let me know how it goes guys, enjoy!
[Touch Pro2, Tilt 2 Android Development] zeppelinrox:
Try today's update... it should have been noop but now it will be deadline if available and if not, then noop...

FYI...

Updated September 3

: - V6 SuperCharger Update9 Beta3

Fixed - Cleaning of local.prop. It was leaving a mess behind.

Enhanced - User notification of events a little more

Updated September 3

: - 98KickAssKernelTweaksInstallerUpdate3 test3

Fixed - A big error (I doubt the io scheduling tweaks were being applied in Update 3 test 2)

Improved - Application of io scheduling tweaks so that it is much more selective and safer

Runs - 98kickasskernel after creating 98kickasskernel!

Notifies - You of the I/O Scheduler in use - Before AND After running 98kickasskernel

Defaults - To using Deadline (if available) instead of Noop io schedular.

Updated September 3

: - 3GTurboChargerInstallerUpdate3 test 9

Added - Complete menu with 4 configurations!

Installs - /sdcard/3GTurboCharger.txt which has specific details of the 4 options.

This is what it looks like:

================================================
\\\\ 3 G T U R B O C H A R G E R - M E N U ////
==============================================
1. Fast?
2. Faster?
3. Fastest?
4. Experimental!
5. UnTurboCharger
6. REBOOT! (WARNING - There is NO Warning!)
7. Exit

Your Mileage WILL Vary!

View settings in /sdcard/3GTurboCharger.txt!

Test all 4 to see which works best for you!

The SpeedTest.Net app is highly recommended :)

Please enter option [1 - 7]:

Download from the usual place http://xdaforums.com/showpost.php?p=15948434&postcount=1127

All 4 updated files are 100% untested by me... so good luck :D
[Touch Pro2, Tilt 2 Android Development] großa:
Trying it, gonna tell you if my phone's burning or not :D
[Touch Pro2, Tilt 2 Android Development] zeppelinrox:
Good stuff.

Please let me know of any possible issues :)
[Touch Pro2, Tilt 2 Android Development] mgross029:
arrrghhh,

Been running SD-booster for a while now with it set to 8192 and my speed definitely did increase because of it... Also used the pm disable, and the echo to change the memory management... Between these three tweaks I feel it is the sweet spot for my Rhod500 so far.

Thanks!!!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Wow that's a huge cache size. Mind telling us the specific SD card you're using, size, class, etc? Thanks.

Glad you like it. Check out that SuperCharger script, it does some other fancy things as well... He's also working on a kernel SuperCharger script, but it's still in beta I believe...
[Touch Pro2, Tilt 2 Android Development] mgross029:
I just pulled the card and checked... 8GB SanDisk... Could not see the class kind of dark in the car right now... (Don't worry I'm not driving and posting. LOL)... I picked a few of these up on a web deal from Meritline for like 9.99 each with FS... I've been pretty happy with them so far. Nice size to keep many test builds on...

Oh... haven't tried the SuperCharge stuff yet... I'm also OC'd to about 650?hz at the moment seemed to get a good boost without compromising battery too much... I may scale that back to see if I can still hold the performance plus gain extra battery life...
[Touch Pro2, Tilt 2 Android Development] großa:
Working fine so far :) Seems to be a little faster (Xenonia 3 is now running with Agressive Mode 1, before I Agressive Mode 2)

But I think that, because we are running XDAndroid from SD-cards,

it won't be much faster. NAND will be a lot faster is suppose.

Have to test my 3G speed sometime.
[Touch Pro2, Tilt 2 Android Development] teemo:
3g/2g transitions is a huge problem for me. Internet related programs have too long delays waiting for up or down transitions. Tapatalk is really bad as it wait for data that is not coming (a refresh helps, but should not be necessary).

So I have now forced 3g on. Always.

Everything works more smooth now.

Of course, if hit a non-g zone, I will be in trouble.

So far, I can not see any other down side. Don't know about battery, I think the same, because the ud/down transitions take some power too.

Don't know if ppl in US is affected by this too ?
[Touch Pro2, Tilt 2 Android Development] [ACL]:
yes and no. Nand boot is balls fast but once we get into android the speed is about the same. Keep in mind nand uses yaffs insted of ext as the file system.
[Touch Pro2, Tilt 2 Android Development] großa:
So yaffs is slower than ext? But more secure?
[Touch Pro2, Tilt 2 Android Development] [ACL]:
nope.. just look it up. bottom line yaffs is made for nand ..
[Touch Pro2, Tilt 2 Android Development] mgross029:
Just put the SuperCharger on... All I can say is WOW... I'm running Go Weather Live Wallpaper and I thought it was pretty smooth before, but after running the script it looks better than Sense in WM!!! This thing is running better from my SD card in looped than my WM did from the internal NAND!!!

Thanks zeppelinrox!