yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] laureanop:
@comradesven I've spent well over 2 hours playing with ram values using auto killer memory optimizer and comparing to the ramdisk file you pointed me to yesterday and I've come up to the following conclusions:

1- The phone has 347 mb of available memory (ram). Any time there' s less than 48 mb of ram available the phone comes to a halt and it takes a while for the android memory killer to free up ram. This is the true lag of this phone if it's not addressed.

2- The default values for android for hidden app, content provider and empty app are 6144, 10240, and 12880 respectively, in pages . When you change these values to 10240, 12800, 15360 which is the optimal setting the phone becomes virtually lag free. These values translate to 40, 50and 60 mb. This keeps the free ram always above 50 mb which means no delays.

3- Imo, given the above findings, the last three values in the file src /ramdisk /init.rc line 567 should be 10240, 12800, 15360 or similar.

4- Perhaps we're paying a little price in battery and in apps being killed a little faster but the benefits outweigh the cons.

5- By changing these values, we're building the memory optimizer in the kernel. I cross checked these findings with my wife' s Continuum which has the same specs, with the same results.

6- After months of debating with different people in the forums and in my personal life, and in spite of opposition from devs, the memory optimizer plain and simply WORKS on this phone when it runs TW

Let me know what you think

@ Mtd people: out of curiosity, what are these memory values on aosp? If these values are the same: is this where mtd excels and reigns supreme over BML ?

PWGB,TKSGB10-12, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] jcurley:
OK, I have been having that problem with MASSIVE lag when too many programs are running, but now I have installed this Optimizer. I will see how this goes. I am running your Value Laureanop.

Comrade: I have one small bug. When the phone gets below 10% battery - if I am on a call, the call lasts for only a couple seconds and I get a reboot. Almost as if the low batt notification is causing the phone to reboot. I am not sure if that is it, but when I plugged the phone in, I talked for over 30 minutes. This was not a one time occurrence, happened 3 or 4 times, before I plugged it in.

I am running 10-12 with Adrenaline XIX on Honeycomb theme. I did not have the Optimizer installed when this was happening.

Let me know if it is me, or the Kernel.

Thank you for all your help on this. You guys have made me get excited about my phone. That is as fast as anything out today.
[Fascinate Android Development] comradesven:
Thanks for doing the experimentation. I'm definitely going to look into the memory problems later this weekend. The values you discovered may be as good as any.

As for MTD, I think this is it:

# Define the oom_adj values for the classes of processes that can be
# killed by the kernel. These are used in ActivityManagerService.
setprop ro.FOREGROUND_APP_ADJ 0
setprop ro.VISIBLE_APP_ADJ 1
setprop ro.PERCEPTIBLE_APP_ADJ 2
setprop ro.HEAVY_WEIGHT_APP_ADJ 3
setprop ro.SECONDARY_SERVER_ADJ 4
setprop ro.BACKUP_APP_ADJ 5
setprop ro.HOME_APP_ADJ 6
setprop ro.HIDDEN_APP_MIN_ADJ 7
setprop ro.EMPTY_APP_ADJ 15

# Define the memory thresholds at which the above process classes will
# be killed. These numbers are in pages (4k).
setprop ro.FOREGROUND_APP_MEM 2048
setprop ro.VISIBLE_APP_MEM 3072
setprop ro.PERCEPTIBLE_APP_MEM 4096
setprop ro.HEAVY_WEIGHT_APP_MEM 4096
setprop ro.SECONDARY_SERVER_MEM 6144
setprop ro.BACKUP_APP_MEM 6144
setprop ro.HOME_APP_MEM 6144
setprop ro.HIDDEN_APP_MEM 7168
setprop ro.EMPTY_APP_MEM 8192

# Write value must be consistent with the above properties.
# Note that the driver only supports 6 slots, so we have combined some of
# the classes into the same memory level; the associated processes of higher
# classes will still be killed first.
write /sys/module/lowmemorykiller/parameters/adj 0,1,2,4,7,15

write /proc/sys/vm/overcommit_memory 1
write /proc/sys/vm/min_free_order_shift 4
write /sys/module/lowmemorykiller/parameters/minfree 2048,3072,4096,6144,7168,8192

but I might be wrong so maybe someone actually running it can confirm. Yeah, I know. Really low values all around if that's what it really is.

I'll have to look into this as well. Might be a ROM issue, my gut with this one is again that it probably isn't a kernel issue.

Annnnd...

I've done a test build with the in-call boost values lowered one notch across the board. I don't feel like calling it a release because almost nothing has changed besides that so if you guys want to try it out and see if the volumes have lowered to your satisfaction here you go:

Odin tar.md5 http://www.mediafire.com/?307gvkf2dq77a1a

CWM zip http://www.mediafire.com/?kia3518ceent88h
[Fascinate Android Development] jcurley:
I don't remember this happening before this recent Kernel. (I was on 9/27 before) BUT, I could be wrong, just because I did not notice, does not mean it was not there. Battery life with this ROM and Kernel are so good, I rarely get the opportunity to use the phone when it is that low.

Let me know what you think.
[Fascinate Android Development] comradesven:
By the way I think I may have discovered part of the reason for the slowdown. The Samsung MFC (Multi-Format Codec) has the highest priority in the dvfs lock scheme (pegs CPU at a certain performance level). This is normally a good thing because it means that when we watch videos with hardware codecs the phone is sipping a dainty 400MHz worth of power. (And for Bluetooth I guess it sips 200MHz worth, l0l. I'm bad at explaining this so Google DVFS and come back when you're convinced it is a good thing too, hey?) But what happens when you're not watching a video and the phone memory is getting all full and bottlenecked? For some reason the MFC sometimes activates and the frantic work of clearing RAM just got anywhere from 2.5 (if it was at 1000) to 4 (if phone was at 1600) times slower as it exerts its right to a 400MHz clock rate. Clusterfuck ensues, then the MFC realizes it isn't supposed to be there and turns over control of CPU frequency. Eventually it all gets sorted out but from the perspective of the user he/she just had to deal with a good 5 or 30 seconds of unresponsiveness. So now you know a small part (very small part) of why battery life on TW is a little better than on MTD. We underclock our processors all the time without even knowing it.

Anyway that was my incredibly intoxicated theory. If MFC is lying in wait for some reason to rear its ugly head when there's low RAM, someone smarter than I should probably look into it on the ROM side of things and fix the bug.
[Fascinate Android Development] comradesven:
Oh yes. Rest assured I will attempt to duplicate this with my phone hooked up to a logcat/dmesg etc.
[Fascinate Android Development] laureanop:
@comradesven. Interesting theory. I wish all that stuff wasn't outside of the realm of my knowledge.

Btw, in call volume levels have improved on 1014.

PWGB,TKSGB10-12, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] AtropineNa:
Yeah maps issue is still there, not sure if its rom/kernel related. Easily fixed by hitting power button on/off

Edit: did some research... supposedly uninstalling/removing updates from Google Maps => Clear Data => Reupdate is supposed to help... first 5 after doing that seems to be better... might be a placebo

Edit #2: nvm got another lockup
[Fascinate Android Development] Dj-Dubster_TN:
lol..Clusterfuck
[Vibrant Q&A, Help & Troubleshooting] mgiusto:
My Vibrant fell this morning face down flat on the screen, I picked it up and was happy to see that the gorilla screen was perfect, not a scratch on it, but that turned to disappointment when I went to turn on the phone and saw a purple hue across my screen, but things were still visible but barely.

About 30 mins later, the screen is now not visible at all except for a small line near the bottom that is very bright (almost seems like the entire image of the screen is squished into this thin line).

Here is the problem. I need some of the stuff that is on my phone but have a pattern lock-screen on it and I cannot see the screen to put the pattern in, I have tried numerous times and get nothing. I was thinking if I can get it hooked up to a PC I can copy everything off. Is there some other way to maybe boot the phone in a mode to connect to a PC?

Other alternative is to buy just a screen and replace it with my broken one. Does anyone know where I can buy just a screen? I don't want to spend too much because I am a couple weeks away from getting the new Galaxy S II when it releases on T-Mobile Oct. 12th, I don't care to completely fix this Vibrant, I just want my data/apps off of it.

Thanks for any help.

mgiusto
[Vibrant Q&A, Help & Troubleshooting] mgiusto:
I just need instructions on how to boot into ADB mode without being able to see the screen at all. Can someone please help?

Thanks!
[Vibrant Q&A, Help & Troubleshooting] Merio90:
Assuming your phone is rooted and have USB debugging enabled you can always try using "Droid Explorer" for windows. Within this program you can copy files without having to mount your sd card...you just need to have USB debugging enabled though otherwise it will not work. You can also access an emulator within this program called android screencast which will basically emulate your phone allowing you to navigate through your phone with ease. Your best option will be to download this Droid Explorer program for windows or you can also try adb but I don't know the commands so sorry.
[Nexus S General] j_r0dd:
I just tweaked the recent ota to just patch the radio since I don't want to change the rom I'm on, but I did want the radio. Since we don't have the full rom to get the radio.img from this is the next best thing.

*****THIS IS FOR THE 9020T*****

Flash with CWR

KD1 -> KF1 Patch

http://www.mediafire.com/?k0gdlbf423540m3

KF1 pulled from the full OTA update.zip

http://www.mediafire.com/?phxp9xnerhdr0ob
[Nexus S General] droidance:
So do I just flash this zip file on CWM for i9020T?

What do you think about KF1? I have bad signal in my area so I was wondering if KF1 would improve my situation. Thanks!
[Nexus S General] j_r0dd:
just flash in clockwork. can't judge the signal quality just yet. just flashed 30 minutes ago
[Nexus S General] lvnatic:
would it work on 9023?
[Nexus S General] rob77:
Thanks for providing the zip. Tried flashing this in clockwork and it came back bad and aborted. Anything I'm doing wrong?
[Nexus S General] jungbum:
Redownloading will probably do it. It's likely that the file is not completely downloaded. I was able to flash via CWM successfully.
[Nexus S General] rob77:
Thanks ill try on my computer when I get home. My phone isn't allowing me to download it again for some reason
[Nexus S General] j_r0dd:
I was lazy and didn't sign the zip. Make sure to toggle signature verification to off.
[Nexus S General] vstudio3k:
I am on kd3 (Tweaked and getting HSPA) with nightly 206 + voodoo patch. No problem with this combinations yet, any improvement with this radio? Thanks
[Nexus S General] Luxferro:
It updated mine just fine. thanks!
[Nexus S General] beanx:
what does this do exactly? Possibly improve your connection? Will it work on CM7.1?
[Nexus S General] noobiekins:
So far nothing amazing but nothing bad as well. Really nothing really happened to where I live (Canada) signal wise. I can't comment on speeds yet. I'll try it later tormorrow
[Nexus S General] shweta245:
s works well on i9023
[Nexus S General] unforgiven512:
Two things here:

One, let's hope this increases stability!

Two, I'm creating a full radio image file, I will be uploading it to my website, and posting it in a new thread. Keep your eyes open for it!
[Nexus S General] brainmaster:
Look here.
[Nexus S General] rob77:
I've noticed it seems to hold on to a HSPA signal better than KD1. With KD1 mine would always revert back to 3g but now it is showing a H most of the time.
[Nexus S General] challl88:
you right, much more better signal stability with new radio...
[Nexus S General] j_r0dd:
I will say it did break wifi tether on mine with miui 1.99.23. I am sure I can just push the updated ril files and fix if I wasn't so lazy :P
[Nexus S General] azulay4u:
Thanks

Thanks :)

Its switching from 3G to WIFI faster than KD1
[Nexus S General] Fidel Cashflow:
I just tried to use the update pulled from the OTA and it aborted both times. The patch seemed to work.
[Nexus S General] mike_art03a:
My Nexus S came with KF1 out of the box and all I can say is that Wifi to 3G switching is relatively quick and smooth, though apps that are streaming things will stop and you'll have to restart them for those of you who might encounter such issues. Especially with Winamp streaming any shoutcast station... God I hate having to back out the to main menu and having to dive through 3 levels of stuff just to restart my stream. Apparently pressing 'play' won't restart the playback, dumbasses.
[Nexus S General] S7icky:
Thanks lol took me hours of searching to find a wind user
[Nexus S General] .:Crack:.:
Hey,

what does this radio.img.p actually do? Whats the patch?

Thanks!
[HTC EVO 3D] subaochen:
RUU will restore the phone to the store state, but I'm not sure:

* Will RUU clear the cache and dilvik-cache?

* Will RUU reproduct boot and recovery partition?

* Will RUU will delete all the userdata?

Thanks in advance!
[HTC EVO 3D] joeykrim:
Yes, RUU will clear /cache partition and the /data (userdata) partition which contains the /data/dalvik-cache directory that will also be erased as part of the /data partition.

RUU will also reload stock boot and recovery partitions.

Hope that helps!
[HTC EVO 3D] subaochen:
First, thanks a lot! So that means, RUU will restore the phone to the factory status? But I'm confused that after RUU I can not boot into the OS and jut stuck at boot loop. In fact, because I don't know why my phone become boot loop(always stuck at splash screen), so I have to ruu, but still boot loop.

I have guested that the boot partition is currupted, but as you said, ruu will restore the boot partition also...

so confusing....
[HTC EVO 3D] rhedgehog:
Not necessarily. If you're using an older RUU with a hboot that is an earlier version of the one you have installed I believe it won't overwrite it.

Find the most recent RUU you can. You may end up with a later hboot like 1.49.000012 that hasn't been S-offed yet, but hopefully it will bring your device back to life.
[HTC EVO 3D] joeykrim:
quickly, to clear up some terminology.

1)the boot partition (stores kernel and ramdisk) will be restored by an RUU. bootloader/radio partitions are sometimes objectable based on version and determined by thte bootloader.

2)bootloader partition is separate from the boot partition.

3)boot loop is generally used to refer to the stage of the booting process when android is displaying a boot animation but due to an error in an android booting required file the android system will fail to boot and continue playing the boot animation indefinitely which results in the boot animation looping visually to the end user. hence the name, boot looping, referring to the boot animation continually looping as android repeatedly tries to load the file which contains a serious error.

4)stuck at the splash screen is due to either a kernel or ramdisk issue (both stored in the boot partition). the kernel loading first and then handing off to the ramdisk which if executed successfully will hand off to the android system including the boot animation.

In my opinion, the most thorough and detailed way of restoring the device using the RUU would be to extract the rom.zip file the RUU.exe contains and which the RUU.exe sends to the device.

Once the rom.zip is extracted from the RUU .exe, rename rom.zip to PG86IMG.zip. Store this file on the root of the sdcard and boot into the bootloader. The bootloader always scans the sdcard on every boot to the bootloader for specific files and PG86IMG.zip is one of them. It will verify the .zip file and then ask whether or not you want to process. Select yes and this will give you a status as it goes through flashing each partition of the device with the partition files located in the .zip. It will tell you whether or not it skips a partition, usually with some type of reason.

Hope that helps and good luck!
[HTC EVO 3D] subaochen:
Thanks joeykrim for clarify some terminologies that I'm confused before!

And I extract rom.zip from RUU 2.08.652(the latest RUU for EVO 3D) to restore my phone, all successful except TP said bypassed(there are two TP items in the update list, one update ok, on said bypassed). That is ,bootloader, boot, recovery, system, userdata and etc almost updated from RUU.

But when I reboot the phone, it stuck at the splash creen with HTC logo for a few seconds and then go dark and then reboot into the splash screen again and again.

My question is:

* what is TP mean? bypass TP will cause stuck at the splash screen?

* Any possibility of hardware crash? according to joeykrim, stuck at splash screen due to kernel or ramdisk missing or corrupted. I think kernel is restored with RUU, but ramdisk will created in the memory, what if the memory chip or eMMC chip was destroyed? my phone was ever falled to the ground before:-(

Anyone can give me some hints? thanks very much!
[HTC EVO 3D] joeykrim:
this is all off the top of my head, hopefully its helpful:

very interesting. it is unusual/uncommon for the device to reboot from the htc logo screen splash screen. i don't think i've ever had an android device reboot on the splash screen, only during the boot animation. generally issues with the kernel/ramdisk during booting will just cause the device to display the splash screen indefinitely.

my guess would be if the device is rebooting from this part of the boot process (splash screen) that would indicate a kernel panic. a kernel panic could be caused by an almost infinite amount of reasons ...

if you were able to have it boot loop on the splash screen, pull battery, then boot into the bootloader and select recovery. does it successfully boot into recovery mode or does it reboot on the htc splash screen there also?

if you're able to boot into recovery, there should be a /proc/last_kmsg file which should have the kernel debug output showing more details around the kernel panic/boot looping on the splash screen.

if you're not able to boot into recovery, the next suggestion would be to attempt flashing an older version of the RUU. although at this point, i would start to think there might be some type of hardware failure causing the kernel panic/reboot at the splash screen.

sorry there isn't anything more positive or any better methods i'm aware of. hopefully you're able to boot into recovery and resolve the issue!
[HTC EVO 3D] subaochen:
Thanks first!

In fact, when I select recovery from fastboot, it just stuck at the splash screen immediately, and then boot looping ...

And unfortunetely, I can not flash an older version or RUU. I have tried to flash the RUU 1.3 and RUU 2.0, only RUU 2.0 can update successfully.

Someone on the freenode suggested that maybe EMMC chip damanged, but I don't know the relationship between EMMC chip and ramdisk? If we can say EMMC is similar to the memory of PC? if so, then EMMC chip failure may cause boot loop(can not create ramkdisk when booting)?

But I'm confused that:

* if EMMC chip damaged, why I can flash the RUU smoothly?

* When select recovery from fastboot, It just entering normal boot immediately. So I guest that the hboot has something wrong, although hboot is also restored from RUU. Maybe HTC unlock method don't allow update hboot?

Thanks again!
[HTC EVO 3D] joeykrim:
to be honest, once you've flashed an RUU the device still doesn't boot, that is a very bad sign. generally, after flashing an RUU the software on the device should be pretty close to 100% stock which also means everything should work.

if something isn't working with near 100% stock software, it generally will indicate some type of hardware failure whether that is the emmc chip or some other component.

the only other suggestion i can think of is to follow the htc steps for locking the device. try booting after locking the device. if that doesnt work then flash the latest RUU and try once more after having locked the device.

the official RUU will flash on a locked device because the .zip file is signed.

if that doesn't work, you're beyond any type of troubleshooting i've been through as generally the device will get exchanged/returned at this point since the issue appears to be at a fairly low level (hardware related).

sorry i can't offer much more guidance. i'm sure there are people out there who have some low level hardware experience and perhaps somebody has been through this issue before but i've tried my best to cover all the basic and extended troubleshooting steps. good luck and keep us updated!
[Android Apps and Games] curiologix:
Few new features have been added to Droid Alarm Clock application. Curiologix is committed to provide best in the market. New features are as follows:

“i” sign on the bottom left corner of the main screen. Touch on it will pop up a window with title “Contact us”, containing company main branch address, email address, phone number and website URL addresses. Touch on email will pop up a email text editor where you can compose email, touch on phone number will initiate a call, touch on URL will direct you to company website

Bell sign on the bottom right corner will appear in case of any active alarm

Showing date on the main screen just below the week days

Alarm creation with a beep sound and alarm notification will appear on status bar on the top

Flash light can enable/disable according to your choice. By default it is disabled

Stay tune for upcoming builds... cheers!

We will appreciate your feedback in form of comments for improvement of our application

Download: Open "Market" from your android phone and look for Droid Digital Alarm Clock (Curiologix). Easy to install and completely free.
[General Questions and Answers] Bigal77:
Hello there,

Im using a Samsung Infuse 4g, and wanted to know if there is a way to save a theme, so I can use it again later. This way I can switch between several. Now i use ADW launcher EX, and change several icons, so its custom made. I download themes, but sometimes change icons and wallpaper to my own liking. The thing is, sometimes i want a dark one, black icons, dark wallpaper, and sometimes i use colors, like green/white combo, and change my icons. Is there any app or way to save a theme, so if i want to switch from one to another, i dont have to manually change al my icons all over again?

I hope there is an easy way

many thanks for any help
[General Questions and Answers] Dirk:
I can't think of any way really. Unless you actually created a 'Theme Chooser' compatable Theme from your look so that you could switch between them.

If you are using ClockworkMod Recovery you could do a nandroid backup with each set up and just flash to whichever one you want at any given time?

It would be a nice addition to Launchers if you could save a particular set-up as a profile, wouldn't it? Perhaps if it were suggested enough somebody might take up the challenge!