yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] NAZUnlimited:
Optical Fiber still havent reached this part of portugal and 3g data plan is absurd. That example was using the phone and a (lets say) "public" wireless with 10% signal strenght reception. i dont know the up/down capacities of that one ( i just detected it and the rest is history. Lets say i have allways access to the net and never used the 3g data) but most people here buy the 2mb pack (2 mb down / 256kb up) argh, stone age! Normally, at home, i can download 1gb in less than 10min and upload about 2x longer.

I considered swap and and a ram module (zram.ko) too but i hadnt much time to try it.

I am not worryed with the flash memory, like u said, we have app2sd and link2sd. What is annoying for me is seeing all that mb just sitting there un-used

edit: use the sdcard for swapping?

process

- creation of a 3rd sdcard partition for swap

- adapt a script to format that in recovery and other to enable the swap partition at phone boot ()

results so far

pro-swap

- no battery drain resulting from doubled sd-card read/write (none that can be noticed even using other means to check battery outputs)

- phone seems more responsive and the benchmark test results were more stable than the previous ones without swap, in fact, increased an average of 14~20 total points in ram/cpu integer

- still havent noticed much improvement (there is some) in multi-tasking but the phone isnt loaded with much apps (read downside why) and that will tested again when i have loaded the phone

downsides

- according to any devs of swap scripts, Swapping decrease Micro SD's life but it is easier and cheaper to buy and replace a new sdcard than a new internal memory (no argument there, done a quick search and realised that for the price of a memory chip + repair, u can almost buy a phone). in fact, according to one dev, he is still using the same card for 2 years (almost year and half using swap) and he still didnt see any wearing problems in that sd-card area (swap partition) or any other.

- the reason why the phone isnt loaded with much apps is because for the creation of a 3rd partition, i wiped and divided the 2nd partition (link2sd partition) in 2. that interfered with the link2sd script in system and didnt let me either activate swap or link2sd partition or replace the link2sd scripts in system, so i did a fast solution for that, full wipe :rolleyes: . what i should've done back then was modify the size and create a new partition using the free space of the 2nd partition and no problems after but some ideas only come after the previous ones failed. lol :D

- i dont know which is better for swap, if the swapper app in store or just a init.d script at boot. <- tests for later
[Miscellaneous Android Development] znelis:
I have been using swapper 2 for a few days now, and while it works fine, and hasnt caused any problems, it also hasn't improved anything that i could notice.

What size and swappines settings do you use?
[Miscellaneous Android Development] NAZUnlimited:
125mb swap partition (so i have 3 physical partitions in sd-card, 1-fat32 (data), 2-ext4 (link2sd), 3-linux swap (swap partition))

swappiness=100

vfs_cache_pressure=25

apparently, most of the swappers agree that less than 100 almost dont do anything

my previous was 60

"A low value means the kernel will try to avoid swapping as much as possible where a higher value instead will make the kernel aggressively try to use swap space. The default value is 60, and for most desktop systems, setting it to 100 may help to improve overall performance, whereas setting it lower (even 0) may improve interactivity (decreasing response latency.)[1]"
[Miscellaneous Android Development] znelis:
Changin the minfree values to 6,8,16,20,22,24 is giving some truly amazing multitasking!

I can now have about 8-12 apps in the "memory", with nearly instant switching.

My vfs_cache_pressure is at 10, which i think is default, i have 256MB of swap, enabled with swapper 2, but on a seperate partition. swappiness=100

This phone has newer been so fast :)

Edit: I was voting for stock browser because i want a vanilla experience. But i use Opera Mini 95% of the time, and sometimes Opera Mobile.
[Miscellaneous Android Development] NAZUnlimited:
tx for the info, silas

i had changed a "bit" those values and oom priorities, etc

vm.min_free_kbytes=18400;

mine were :̶8̶,̶2̶0̶,̶4̶5̶,̶6̶5̶,̶9̶0̶,̶1̶0̶0̶ 10, 16, 55, 70, 85, 100

i'm still testing those for side-effects

View attachment 1127656View attachment 1127657

in the pic above, i used v6 script for tests. even though i changed all values, it still said 50% supercharged. then i figured out why, the script couldnt find the supercharged adj file nor the minfree. v6 puts them in /data to read them at boot start but since i didnt supercharged, my /data didnt have them. (i just altered the rom defaults making a more cleaner version - less files in /data and /init.d - and 100% tweak stick. on the opposite, v6 values didnt stick every 2 boots - dont know why that happened)

i love zepp's work but i dont use v6 supercharger for, mainly, two reasons

1- slows down boot proccess (dont know why), it can be noticed in the boot animation, it becames slower

2- some tweaks in the script block the light, orientation, gps, data toogles (one cant change those if the wifi or data is connected)

what i changed in rom defaults (these are only if using swap)

OOM_MEM_Settings, OOM_ADJ_Settings -> build.prop

minfree 2560,4096,14080,17920,21760,25600 -> (10, 16, 55, 70, 85, 100)

adj 0,3,6,10,12,15

swappiness 100

vfs_cache_pressure 25 -> yeah, the default is set to 10

dirty_expire_centisecs 500 -> will test other values later

dirty_writeback_centisecs 1000 -> same here

dirty_ratio 95

dirty_background_ratio 60

̶l̶e̶a̶s̶e̶-̶b̶r̶e̶a̶k̶-̶t̶i̶m̶e̶ ̶1̶0̶ -> this one is giving me lots of trouble, wont stick

vm.min_free_kbytes=18400;

vm.oom_kill_allocating_task=0;

vm.panic_on_oom=0;

vm.overcommit_memory=1;

kernel.panic_on_oops=1;

kernel.panic=30;

net.core.wmem_max=1048576;

net.core.rmem_max=1048576;

net.core.optmem_max=20480;

net.ipv4.tcp_moderate_rcvbuf=1;

net.ipv4.route.flush=1;

net.ipv4.udp_rmem_min=6144;

net.ipv4.udp_wmem_min=6144;

net.ipv4.tcp_rmem='6144 87380 1048576';

net.ipv4.tcp_wmem='6144 87380 1048576';

this i what i like

View attachment 1128242View attachment 1128243View attachment 1128244

View attachment 1128246View attachment 1128247View attachment 1128248

a good memory management
[Miscellaneous Android Development] znelis:
It seems like you are trying to get as much free memory as possible. Which isnt exactly what i want to do. Unused memory is always just wasted memory.

The perfect memory management would be when we can have all the memory filled up, but always have something that can be cleaned up when needed.

I havent tried all your values yet, might do that when i have more time, and a computer. Right now im testing out these values: http://xdaforums.com/showthread.php?t=1227269

Also, Rom Toolbox is fantastic for this kind of tweaking, just a tip :)
[Miscellaneous Android Development] NAZUnlimited:
That will be a yes and no. I am trying to keep free some internal memory to use when its needed by the current aplication or the os and load up all the rest in swap. Just like what u are doing but using swap as loaded "ram" to give some slack to internal ram for when we need it. I found out that the internal taskkiller kills apps after some time in internal ram, cached or not, even if tricking it to think we have more than 178mb ram ( the oom adjustments) but it doesnt kill the ones mostly present in swap (funny stuff). Other reason was because the phone couldnt reach deep sleep with a loaded internal ram and with taskkiller seeking for terminable apps, all that increased the battery drain. Since i never turn off wifi nor data, i noticed some power drain, higher than the ones before

rom toolbox, i used it a lot before when i was on adrenalin update 2 but it cant alter the lease value too. I can do most of the stuff by head now, in part tx to rom toolbox :rolleyes:
[Miscellaneous Android Development] znelis:
I must say, your settings work ok too, pretty much the same result as my earlier settings.

I found something interresting :)

I was replacing some system apps with the ones from Cyanogen 7.2, and i suddenly noticed that the auto brightness option was back. (I love that feature, relly usable :D ) It must have been eather Settings.apk or Settingsprovider.apk that did the magic.

But it introduced one bug, which also was on adrenalin earlier, I have too open the wifi settings to make it scan and connect. Could maybe be fixed by changing some scan settings?

Also, replacing some other files made a difference in performance. (Maybe just an illusion...) I think it must have been framework-res.apk and systemUI.apk. Maybe some other apps where optimized too.

And that gave me the stock look back. Nothing back about your theme, but stock looks much better :)

Replacing camera fixes the menu, (not transparent and horrible to read anymore). Image is still rotated, I might look into that later

All my files are available here:

http://silenz.se/owncloud/public.ph...dddf22a07966e8b75&file=/ownCloud/huawei_tweak

It does really seem a little bit smoother now :)
[Miscellaneous Android Development] znelis:
Yes i have those from u8150, because its 90% the same hardware. Just another screen and no keyboard. (and maybe some internal stuff like the acelerometer, but those should "always" work).

But cmparts.apk is just for cyanogenmod, and other roms, even plain android source, has this feature. A fun little fact, even the stock rom could read light sensor data, but the auto brightness feature was missing.

Is it epilepsy you have? Its when you react to fast color/light changes?

It's possible to change the brightness values, and some other nice settings, in the cyanogenmod settings>Display>Automatic backlight

So your framework-res.apk is smaller? (don't have your files left, and rapidshare is still slow :p ) I might try to write a small python script that decreases the quality of the images.

Could you explain what i have disabled, because everything is still running, that i can notice. Or have you added some services that i disabled? (i get that the battery is updating less often but that shouldn't make a noticeable difference?)

I read your post a few times, and i think i got most of it now. But you should sleep a little bit now. And fondle the cat from me :)

The conflicts are just some things owncloud (my hosting service, similar to dropbox, but on your own server) messed up. It's not the most stable peace of software ever written ;)

Cmscreenshot was not exactly the same size, so the might have optimized something since the last release.

Ok, the perfect thing for me would be a smaller stock theme.

Battery stats never worked for me, it always blames some random app like youtube for 99% of the usage, even if it was running 5seconds :p

But at least battery life is ok for me, usually enough for a school day.

Edit: I will try to build some apps from source, and maybe reduce the size if possible. Might also try to take a look at the camera.

Edit 2:

I fixed the camera rotation :)

Available here:

http://silenz.se/owncloud/public.ph...31c0170c4d0dddf22a07966e8b75&path=/Camera.apk

Also i'm working at reducing the memory usage of the framework.

Could someone (NAZUnlimited) please check how much memory "Android System" and the service com.android.systemui is using?

Mine is currently at 21.48MB (was at 20MB directly after boot) and the systemui at nearly 6MB

You can use https://play.google.com/store/apps/details?id=com.rs.autokiller to check that.
[Miscellaneous Android Development] NAZUnlimited:
no, not that. a sleeping brain couldnt find the right word or expression

photophobia or light sensitivity. i have cat eyes or bilateral coloboma (cat eyes is cooler, lol). my sight is fine, i just have to wear glasses with lenses that change color with light (i dont know the name of that, photo lenses or something). my coloboma problem is more of a cosmetic thing but it leave me with a high sensitivity to light.

ok. after install the program

free ram -> 96MB

Android System -> 20.11MB

com.android.systemui -> 4.53MB

after reboot (here the program changed my oom settings without asking and i didnt apply nothing)

free ram -> 67MB

Android System -> 18.79MB

com.android.systemui -> 4.82MB

reboot 2 (with deny permissions for autokiller and keeping my settings)

free ram -> 85MB (with time or use, some apps will be cached to swap and will free ram)

Android System -> 19.26MB

com.android.systemui -> 4.07MB

i tested the cam. great job on that. now the only thing that remains to fix in that is to unsquare the img we see in the app. there was a cm's cam app that didnt have that problem, only the rotated save problem. dont remember if was in the htc or xperia cm gb.

one thing, reducing with high compression the size of the app is great for the amount of space it occupies in memory ("physically") but it forces the use of more ram to read the app, reducing performance. that is why odexed apps grant more performance (but they grant other problems). the trick is to set the right compression and/or reducing the amount of space the app occupies unpacked (pngs, code, etc). thats why zipalign is very important to deodexed roms

no, my frameworks is in fact bigger than the one from sources, it has more files stored inside (if i recall right, something between 260 and 330) (used the trick above).

dont worry about what u have disabled. for stock looks, it wont cause any problems. but just in case, u should do a factory reset (data or just a dalvik reset) and check. if nothing force closes at start, u are fine. most services are in the jar files. u wont have any problems unless u replace those.

about the quality of the images, u need to be carefull there. most pngs stored have visual indicators. if a pixel is missed on those indicators, u'll have visual bugs or worse, the os could stuck at the end of boot and stay there, never starting to the actual interface. i had those problems in a lewa rom (hdpi)
[Miscellaneous Android Development] znelis:
Ok, mine are at 16.73 and 3.37

I also removed the fotakill app. Huawei will newer send us an OTA-update ;) and it was runnning in the background all the time

That image in the top right?

I also noticed that video recording is broken, no idea why.

Well, why not try to odex all the apk's. The stock rom was odexed. Which problems should it introduce?

I'll do that now and see if i get any performance boost, or bugs :)

Also, i think the cm7-compiling process is zipaligning system apks automatically.

I have wiped data since my big changes, and no problems.

My framework-res.apk is currently 3.9MB, the same size as yours. But i have no idea where i got that from :p

I have actually replaced my framework.jar, with no problems at all. Mine is ~0,2MB smaller, most likely why my memory usage is lower. Also, some of my other .jar files are smaller, but i haven't tried those yet.

I had changed my images, and saved ~0.2MB there with no problems that i could find.

But the thing i wanted to do was to use a higher compression, but it was already as small as possible. So i reduced the resolution to 70% of the original (in each direction).

Reduced the size of drawable-mdpi to 976.0 kB from 1.1MB. No big changes. I might try to do that again with my new framework-res.apk (the one i don't know where it comes from :p ) and all the png's.

But i don't think we can save much there.

Edit:

I odexed a few system apps. Settings, systemui, holo launcher, camera, root explorer and play store

I noticed a little bit better performance with the launcher and the play store, but it's nothing revolutionary.

My system files are available here: http://silenz.se/owncloud/public.ph...dddf22a07966e8b75&file=/ownCloud/huawei_tweak

Also the new framework.jar is available there
[Miscellaneous Android Development] NAZUnlimited:
lol. i never noticed fotakill running but its good to know that

but unfortunately i have some bad news

yesterday my phone went missing. i was sure left it at home in a bookshelf but, just in case, i searched it everywhere i had been but no luck, it was nowhere to be found. calls were bypassed directly to voicemail. i was already sure by then, that it was stolen or someone found it and keep it. this morning, i noticed some marks of splashed water in the floor next to the bookshelf and found the phone inside the fish bowl.:eek: my guess is that Vicky (the cat) went into a turf war and sent my u8300 to scuba diving in the fish bowl (half a meter down and a bit to the left from where i placed the phone). really bad luck and poor choice of spot to leave the phone.

i disassembled, dried and cleaned it but no luck. the repair guy said it most definitely cant be repaired, it was dead (on the water :rolleyes:), but it was sent to repair anyway.

so while i am preparing for more bad news, i started looking for a replacement for that one (i still have my gio and u8500).

buying a u8300 here in portugal is out of question, it costs more than 100€ and is blocked to the network and for that money i can buy better phones even though, the u8300 came to my hands almost for free.

so i am asking if someone knows a good website or anything else that sells that model and for a good price to place the address here or pm me.

meanwhile, development from my part is suspended for a while (at least until i know if it can be repaired (lol. in this case, is more resuscitated) or have a replacement)

and no, i didnt do anything to the cat. it was my fault (laziness) that the phone was in that spot. sh€€t happens sometimes.
[Miscellaneous Android Development] znelis:
I can't help, but I where laughing when i read what happened :p

You can get one from china for ~87euro, but thats still no good price. You could get it for about 56 euro here in sweden a year ago.

I will get a new phone at fall, or the end of the year. When new Cortex A15 are coming out, and maybe a bunch of nexus phones.

The u8300 is really becoming out of date (it was old even in december 2010 when i got it for 113 euro ;) ).

Good luck finding one, maybe on ebay, or what you have in portugal?
[Miscellaneous Android Development] NAZUnlimited:
i'll probabily wait till the end of summer and see if the prices drop or wait for the stock off. since that is a discontinued phone, the price is droping. a couple of months ago, it costed 139€, now is at ~109€ but still pretty expensive for a 3rd phone (a use only when the others dont have energy).

in worst case scennario, my gio becames the 3rd and the 1st will be... lets see what will be available by then.

olx and miau.pt (<---- lol)

the u8500 is close enough to continue developing but it is not the same thing and i dont want to erase all the work envolved in it

lets wait and see, by the end of the week, i'll get an answer about the repair

-----------------------------------------------------------------------------

:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:

edit: apparently, huawei made a pretty though s.o.b. when created u8300. :highfive: repair guy just called 15 min ago and believe it or not (i still cant believe it myself), the bastard is still alive :victory: and didnt needed any kind of repairs (except for new speakers, old ones were damaged from the water). apparently, after it really dried itself, it just turned on when they tested if it could power on. all other hardware tested just fine. it was cleaned and they even put a new display protector. monday it will return to my hands and them the real tests will begin :rolleyes:.

5€<price repairs<~15€

how much i payed for the phone when i bought it = 10€

still a good investment (not as good as my mitsubishi m320, the battery still lasts 5 days with calls and gprs after 11 years of constant use :cool: :p)
[Miscellaneous Android Development] znelis:
Not bad to survive a day in a fish tank :)

Maybe mine will go to be repaired too. The plastic is cracked on the front between screen and keyboard again (same problem last summer). At least I have warranty left for ~5 months more ;) Also the battery seems to be getting damaged slowly, will see if they swap that out for free too...

If the plastic cracks one more time until December they have to give me the money back, or another, better phone (they have three times to repair the same issue), which would be pretty nice :)

The only problem is that the phone is unlocked, which would cost me 10 USD to do again, if they don't unlock it again for free.

Edit: I have been experimenting a bit with Ice Cream Sandwich.

http://xdaforums.com/showthread.php?p=19941500#post19941500 with kernel up to 9B works okay, screen flickers, but is a known problem.

Boot with our GB kernel always stuck at "Android is upgrading, starting applications".

The kernel everyone uses (including the one above, after version 10) is rotating the image, and shows just the top of the screen. (Like if you take the screen like it should be, and rotate it 90 degrees without changing the resolution)

All of the kernels, except the GB kernel (which i'm sure would work ok if we can get it behind the upgrading ;) ), show a white screen after turning it off and the on again. Sounds like https://github.com/psyke83/android_...mmit/564c62dbbc39304270b36553b663ff64f8bc9f82 would fix it, but i couldn't get the kernel to compile.

The source for both ICS and the kernel they use is available, so it should be possible to get it running.

When judging from the few minutes i played with the actual UI, it is actually pretty fast. (And of course ICS is still really good in any way ;) )
[Miscellaneous Android Development] NAZUnlimited:
i had tried that half a year ago, updates 2 and 3, if i am not wrong. i experienced all those bugs and no physical keyboard with the previous kernel(s). i had found a no-90º rotated kernel that booted perfectly ics on u8300 but unfortunately when i had sd-card problem (files disappearing in my u8500 for no known reason), i lost that kernel and the dev's page. i remember it just had a problem with a no-working bt.

after that, i stopped doing tests with ics, most of the results were unstable, 90º rotated, white screen of death, half screen interfaces. most of todays bugs were present back them. even with all those problems, i agree with u, the u8300 can work properly with ics, the ics ui worked well and fast in every test i ran. like u said, with the right kernel, we can use ics in landscape, but unfortunately (for now) we still face another problem, the same as u8120, graphic drivers and the eternal discussion of either u8120 have or dont have adreno gpu but this only line present in u8300 and u8350 stock kernels (probably in u8120 too but i dont know) makes me wonder

# gpu driver for adreno200 is globally accessible

/dev/kgsl 0666 root root

the real problem is, if the u8300 / u81x0 series really dont have a gpu or wont have 100% working graphic libs, then we will be stuck with an o.s. that cant play videos, games or anything related with the use of a gpu and we will end up with half a phone (less smartphone stuff). i have read this line in some place and for the time being i agree with the author,

but on the other hand, my jelly bean tests might start this summer and kernel dev/config learning too