Vicky
Current: [Vicky v2.5.5] - Jul/24/2013
Lite Version: [Vicky v2.5.5 Lite v1] - Jul/24/2013
What is Vicky?
- Vicky is a mixed Gingerbread rom based on Cyanogenmod's sources stable/nightly/experimental, for now...
Some Screens
DISCLAIMER:
I'm not responsible for any damage you can do to your phone using my rom nor it is my fault your phone dumped you and loves your cat more than he loves you
Changelog
[Vicky v2.5.5]
Code:
- Slimmed a bit
- Fixed a few typos
- Updated some system apps
- Updated HoloLauncher_2.0.2
- Added Holo notifier and locker
- Adw.Launcher
- Tweaked some more
- Random bootanimation support without using apps
(just place your favorite bootanimation zip at bootanimation's folder in your sdcard)
- Modded kernel with hwuserdata support
- Replaced stock mms app with Huawei SMS/MMS app
- Huawei file explorer
- Latest huawei gb launcher
- Swap support (check Extras section for info)
- fixed problems related with changing phone settings while/after Wi-Fi was on (ex. toggles getting stuck)
- fixed layouts
- themes added
- stock dalvik cache bypassed to cache partition to grant extra space in data partition. new installed apps dalvik cache will be placed on data as usual
(if you need to wipe dalvik cache by necessity of something, in recovery select wipe dakvik cache and select wipe cache)
- Downloads cache moved to /obb (bigger partition and dont require cleanning)
- Some surprises
- Stuff i cant recall now
- Fixed a few typos
- Updated some system apps
- Updated HoloLauncher_1.0.2
- Replaced gps configs (enable internal gps in settings/location and security/gps source) - didnt noticed but since v2.0 the gps.conf was set to Portugal, now is for europe
- Fixed MagicSmokeWallpapers (now there is fog and not moving squares) -> finally no more apps to fix (i hope!)
- Tweaked some more
- Defaults settings changed - only noticed if doing a clean install, wont affect the ones already made
- Latest CM 7.2 sources for Huawei + for Samsung
- Lightly themed
- 60% Tweaked (battery, camera, network) (still no Supercharged script added)
- Increased performance
- Optimized All Apks
- Fixed some bugs
- Improved some libraries
- Improved MDPI layout
- Default kernel set to 600Mhz -> (U can choose other values)
- Original Network Operator Names -> back from the dead (If u find a problem, report)
- Battery PowerBar added
- Fixed Deskclock display size
- Crt animation on/off activated by default
- Bravia Engine added
- ICS Rotation added
- Beats Audio added -> might change that to XLoud, if it doesnt give any problem (battery drain, audio issues or force close)
- Updated APNs and fixed Optimus, Vodafone, Tmn MMS -> if anyone still has problems with the MMS, report it
- 3 Launchers (Adw, Huawei and Holo V1.0.1)
- TouchScreen, compass and battery calibrators
-> Wipes Required - Dalvik, Cache
-> Formats - Boot, System
-> Data Wiping / Factory Reset - no problems were reported by not wiping data but, if u encounter problems (bootloop, FCs, apps not working, etc). u'll need to do a wiping data + dalvik and reinstall all your apps
--> if ur apps are linked, unlink them. After flash/reboot, dalvik cache will rebuild itself with all apps info, including the linked ones. this way, wont exist conflicting doubled dalvik's
- CM 7.2 RC1 sources for Huawei u8150
- Lightly themed
- 40% Tweaked (0% Supercharged)
- Increased performance
- Screen, compass, battery calibrators
- Other Stuff i can't remember now
What do you need to install Vicky
- Vicky ->> [Current version]
- SuperSU [ Tx to Chainfire ->> [v2.82] | | old versions ->>[v1.01] |
- modded Lite GAPPS + Last Playstore for GB ->>[2016/09/22]
- Google Play Services ->>[2016/09/22]
What do you need to install Vicky Lite Version
- Vicky Lite ->> [Lite]
- SuperSU [ Tx to Chainfire ->> [v2.82] | | old version ->>[v1.01] |
- modded Lite GAPPS + Last Playstore for GB ->>[2016/09/22]
- Google Play Services ->>[2016/09/22]
Extras
- [Boot Sound Remover] -> not found
- [TSReset - Screen calibration reset]
- [Mac Address Patcher]
- [On-Screen Keyboard enabler] -> not found
- [On-Screen Keyboard enabler -> Vicky 2.5.4] -> not found
- [Huawei Keyboard] -> not found
- [Ascend ClockWorkMod Recovery 3.0.2.8]
- [Huawei ClockWorkMod Recovery 4.0.1.5]
- [Swap installer] -> Tx to Yank555
How to change ClockWorkMod Recovery
I made it simple by using the same proccess of flashing a rom. you just put the cwm zip file in your sd-card. Reboot to CWMod recovery, select "install zip from sdcard", select your new cwm zip file. After flashing, go to advanced and select "Reboot Recovery". Now you can see your new Recovery.
How to change MAC address
Method 1- unzip MacAdress.zip, go to system\etc\firmware\, open with notepad++ this file "nvram.txt", find this line of code:
macaddr=00:90:4c:14:43:26
write your own mac-address found inside the phone in the battery case, save.
go all the way back, zip META-INF and system folders with Store compression.
or just open MacAdress.zip (not unzip), go to system\etc\firmware\ and drag-and-drop to that folder ur edited "nvram.txt".
flash the new MacAdress.zip, fix permissions, reboot.
Method 2- open RootExplorer in system\etc\firmware and open "nvram.txt" with text editor, locate this line
macaddr=00:90:4c:14:43:26
and write your own mac-adress (like 11:22:33:44:55:66), save and close, reboot.
To install from stock rom you need these ones too
- [z4root]
- [rom manager]
Info
Code:
[COLOR="Red"][B]What is Working[/B][/COLOR]
Apparently almost everything
[COLOR="Red"][B]Bugs/Not Working[/B][/COLOR]
[COLOR="Red"]what are the drawbacks? The bugs that i need to live with of i update?[/COLOR]
FM Radio not working. Almost all phones that had FM Radio, updating to Cyanogenmod made them lose FM Radio because of certified drivers and other issues
Keyboard - some keys that used the double function, like the ".com" key or the "smiley" key, are stuck to using only one function, ".com" stays just "@". if u have keyboard issues (keys switched or something), flash the correct version for your phone. more info at the 2nd post.
TouchScreen calibration - it is not the best compared to the one used on u8300 eclairs, but is something almost as good.
Onscreen Keyboard - since most users use the hardware keyboard, the onscreen keyboard is purposely disabled. so if u want back the onscreen keypad (to use other soft keyboard like go keyboard or, i dont know... tswipe), just ask for a patch enabling it, otherwise i'll keep it disabled as a reminder of the keyboard issues. By request of songrak, a patch enabling the on screen keyboard is available for download, plus a Huawey Keyboard app (tx to RedDeviL). Check the Extras section.
[COLOR="Cyan"]Remember this is not an update for the stock rom, it's a new OS. [/COLOR]
Keyboard access Keys for a turned off phone
Call button + volume up + power -> turn on phone in CWM recovery
Hang up + power -> turn on phone in Bootloader mode (fastboot)
Hang up + volume up + power -> activate the huawey stock rom flashing, it will wipe everything in your phone and flash the stock rom back to phone (if you have a dload folder in your sdcard)
Flashing Requirements
- Rooted phone
- ClockWorkMod Recovery
- Rom files
- Partitioned SD-Card -> Read post 2 for more info
- 100% battery charge (in reality you just need something between 40% and 100%, but this way if u encounter problems, u'll still have energy in the phone to solve them and it will avoid a miss-install resulting from the power ended during flash)
Flashing Procedure
note: - Put the files into the root of your sd card or any other folder of ur liking.
just by my experience, i advice u to put also the dload folder at the root of ur sdcard, with just the updata.app inside. its just in case u experience something (phone not coming out of bootloader after restart or something) and this way u can go back to stock easy and start again
[Stock - 1 to 20] / [Others -> 5 to 20]
1- Install z4root and do a Permmanent Root to the phone
2- Install rom manager and open it
3- Select "flash ClockworkMod Recovery" to install the custom recovery from rom manager, choose huawei ascend recovery
4- go to "all clockworkmod recoveries" and flash a previous version of ClockworkMod Recovery, after finish, do step 3 again and go to 5. (its to avoid conflitcs with the huawey recovery and to avoid no access to CWM recovery)
5- select Reboot into recovery and do a full backup of your current rom (optional, but if u dont do it, u'll lose everything u had - if u want to go back to your previous rom)
In CWMod recovery Menu u use the trackball to go up/down (press it results in a "enter key"), the go back buttom is a go back buttom (lol) and return (enter) key is a enter
6- select wipe data/factory reset from the menu
7- go to advanced and select wipe dalvik cache
8- go to mount and storage and select format boot and format system (use the keyboard enter key to avoid selecting and entering the wrong one with the trackball)
9- Choose "install zip from sdcard" and select Vicky from the menu, go on with the process
10- Once done, again Choose "install zip from sdcard" and select gapps from the menu, go on with the process and again choose "install zip from sdcard" and select SuperSu
11- go to advanced and select fix permissions
12- go back and select reboot system now (remove ur sim card before)
the first boot it should take between 1 to 4 minutes (the phone is in bootloop if u see the animation or the boot sound restarting itself - the screen goes black and the android in a circle appears again, if it does this again and again, its on bootloop. if u dont see that it is fine (since it doesnt stay there for 15 min))
13- Calibrate screen and it will reboot as soon u finish. (read bellow if u miscalibrate screen)
14- insert the sim card before the phone enters the boot animation
15- turn on wifi, check if it is activating, if u dont use the 3G data, turn data off. Configure everything u want to be set ( like the crt animation or the buttons on the status bar or the allow unknown sources install - this one is a must), dont open link2sd nor set the cpu to 710 (or other) yet
16- reboot into recovery (long press the power button and select Reboot and Recovery mode)
17- Choose "install zip from sdcard" and select Boot sound Remover then reboot system, if u want to remove the boot sound
18- go to apps drawer, open No-frils CPU control, there should be there 2 frequencies, 245 and 600, change the 600 (it is the higher frequency the phone is working after reboot) to the value u want (dont worry, all of them were tested and none will grant problems, dont go bellow than 600, u'll slow down the phone and drain battery faster, 710 grants more performance and the battery drain is almost the same as 600), apply and grant superuser permissions
19- Open link2sd, grant permissions and select ext4.
20- Reboot
21- Install Google play Services (com.google.android.gms-7.8.95_(2113048-032)-7895032-minAPI9.apk) <- i don't know if Google PS will update itself for the most recent one (and bigger one) but it can be denied by going inside the playstore, searching for Google play Services and in the options, de-select auto-update.
22- Enjoy
(one thing, after the 1st boot and after the sim pin screen - if u have the sim card inserted -, let the phone stay a while in the touchscreen calibrator, there is chance that u need to insert the pin again and that will restart the calibration and could miscalibrate the screen. if u dont that to happen, insert the sim card before the 2nd boot)
If by any chance u miscalibrate the display - Go back in recovery mode and flash TSReset, reboot and go to Calibration app in Cyanogenmod settings
advice for a perfect install/config
- 1st boot - before calibrating screen wait till holo locker locks screen, then unlock, give a few seconds, then calibrate, this way u'll avoid the restarting of the calibration app. if, cant reach the unlock button, rotate phone
- 3rd boot - [Very important] Give 2 minutes before entering pin because file system is being changed (dalvik cache is being recreated on cache partition and if the OS is loading apps, the dalvik wont be perfectly moved)
- after selected the home launcher, you can freeze the other ones, using link2sd (selecting the launchers that you dont want, long pressing them and freeze) ou by using the applications section in settings.
p.s. u can disable the holo locker when u want to
- the boot sound is activated, i let it stay because, this way, u can see if the phone enters in boot loop after install (the music restarts). when u are done with the configs, u can delete it.
dont bypass the google apps or it will result in no-lockscreen and no receiving calls/sms bug.
(just kidding but they are really, really necessary)
any opinion, bug report, other things about the rom is welcomed to improve the rom
lol. +6k views and only one thanks
Settings
How to partition a SD-Card and how to work with Link2SD + Swap
Using this you can add more apps to your phone and keep a lot of internal memory free
[link2sd]
[XDA - sdcard partitioning]
[how to partition sdcard using windows]
[[GUIDE] Link2SD for Dummies] -> it wasnt me who named it
[[Video] How to Partition Your SDCARD using CWMod Recovery]
[[Video] Partitioning SD for Apps2sd and Swap]
[[GUIDE] Increase RAM using Swap File and Swap Partition] -> it has a text guide for Minitool partition wizard
~Values for the partitions: (as allways, its your choice to increase or decrease those values)
Swap - Max 64mb (initially i had 256mb (too much). even at 128mb and 100% swapiness, it was much. so i tested with 64mb and got the perfect partition size for swap, leaving a couple of free mb if wanted to increase swapiness)
SD-Ext - depends on the size of your sdcard and if you install lots of apps and want to link them so, minimum - 128mb
The rest is for sdcard data
Remember to backup your sdcard before partition it
----------------------------------------------------------------------------------------------------------------------------------------------------------
After flashing the rom, you'll need to calibrate battery.
use the batterycalibration app or the built-in app in CM settings to calibrate battery.
let the phone charge to 100%, wait 10-15 min, open batterycalibration, the battery values should be around 4120 and 4167mv, press battery calibration (do not unplug the phone yet). shutdown the phone, let it stay in charging mode for 5 min. reboot, check the new battery values at batterycalibration (the new ones should be between 4170 and 4270mv), let it sit there for another 5 min and, finally unplug the phone.
-> sometimes after doing the calibration, the battery 1st charge drains in a few (between 8 and 16) hours, but its normal. <-
even it drains the 1st charge, dont worry about doing a 2nd battery calibration. just do a normal charging, after one or two charging/draining cycles the battery will work properly.
----------------------------------------------------------------------------------------------------------------------------------------------------------
keyboard files for other languages
tuono in Adrenalin's thread made several keyboard installers, they work in Vicky's too, they are on the 1st page, 1st post.
u just need to download it, place it at ur sdcard, reboot to recovery, choose "install zip from sdcard", select the language file, after finish, fix permissions and reboot.
----------------------------------------------------------------------------------------------------------------------------------------------------------
GPS settings
the actual gps settings are for europe.
if u are from outside that area or u want a more specific area, u can use the fasterfix app. on its menu there are some gps servers and a custom option. by selecting it, u can write the one gps server u want (if it wasnt on the list). basically, it is just writing down the country abrv.
(france is fr, united kingdom is uk, etc) before the gps server adress.
something like this
uk.pool.ntp.org
for more info, visit http://www.pool.ntp.org/
using gps status app (its on google store), u can see if ur internal gps hardware is working and ur actual location
Note: u8300 huawei's gps was made to be an online gps (a gps assisted by internet), meaning, for it to work with google maps, ndrives and others, it needs to be connected to the internet to work properly (unless u use an off-line gps app that saves the maps in the sdcard and uses the tracking system to navigate, there are a few in google store and they work great without internet)
----------------------------------------------------------------------------------------------------------------------------------------------------------
Important
for the ones that dont like being at the spotlight
(just kidding)
the beats audio boot sound was supposed to delete itself after that 1st boot but apparently busybox (i think?!) cant remove it while the phone is booting
use some root explorer app and delete this file (android_audio.mp3) from this folder "system/media/audio/ui"
or replace it with the sound u like. (needs to be renamed android_audio.mp3) <- i did that and some guys hate my guts
or if u are a windows user, go google (lol ) and search for android commander, or go to the creator thread here in xda, its a very usefull tool and u can use it to delete that file and to do other stuff with ur phone. there is also a linux version but i think its a dead issue, but if anyone want a peek, go see it
----------------------------------------------------------------------------------------------------------------------------------------------------------
TouchSceen Calibration
if the display miscalibrates it self by bad calibration input or other stuff, go to recovery and use the TSReset to reset touchscreen calibration
the rom has some TS values by default, that allows you to go to the screen calibrator and calibrate again without any problems and with more accuracy. this way the old bad calibration input wont interfere with the new one
----------------------------------------------------------------------------------------------------------------------------------------------------------
For just the portuguese users
[Mini-Tutorial] Configurar MMS em Android
os apns foram actualizados com as modificações necessárias mas se, por algum acaso, (ainda?!) não funcionarem as mms, façam o seguinte:
- Instalar APN Portugal
- Abrir o APN Portugal e seleccionar "Configurar APNs"
- (opcional) Colocar o widget do APN Portugal no homescreen (recomendado)
- (opcional para controlar acessos indevidos à internet) Garantir que o widget está vermelho e não verde, ou seja, a internet está desligada OU abrir o APN Portugal e garantir que a internet está desactivada
- Ligar dados no smartphone (Definições - Sem fios e Redes - Redes Móveis - Check Dados activados)
- Testem enviando uma MMS para vocês mesmos.
NOTA IMPORTANTE: Se colocaram o widget, sempre que quiserem aceder à internet sem ser por wi-fi, TÊM que carregar no widget para ele ficar verde, senão não vão conseguir aceder à internet. Se não colocaram o widget têm que ir à app APN Portugal e activar o acesso à internet.
NOTA IMPORTANTE 2: Com a instalação do APN Portugal é possivel permitir/negar o acesso à internet (excepto wi-fi) por parte do smartphone, por isso não há problema de ter sempre os dados activados desde que se faça um bom controlo na APN Portugal para activar ou negar o acesso à internet. Eu tenho os dados sempre ligados e quando necessito de aceder à internet 3G basta-me tocar no widget e voilá. Quando termino a navegação, toco outra vez no widget e a internet fica inactiva.
Click to expand...
Click to collapse
Issues and/or updates info
An annoying "bug"
Only 3 users complained about this <- i thank you for reporting problems, without those reports i'ld assume everything is fine and could neglect bugs or errors and i dont want that
"I have a problem with receiving messages... they come with big delay and/or I receive it multiple times, even though it's not sent to me more than once."
apparently its an occasional memory problem (at least that was my case but i am using dev version 2.5) but could be related to the phone app (no need to explain since i'll see if i can fix it in the next version)
this fixed mine
(the names may be different but i think u know what i am talking about)
go to settings / cyanogenod settings / performance / lock messaging app in memory (<-- check this box)
other fix
uninstall the message aplication, u can use the link2sd to do that, its quicker and easy
install go sms or handcent sms or someother messaging aplication
reply back which one fixed your problem so i can see where exactly is the problem and fix that in the next version
what is to do for next updates
make the keyboard be more like the stock keyboard
add a battery power bar - 90% done but v2.2.7 has an app for that purpose
add a cpu bar - 60% done
fix network tweaks - 80% done - only a few conflict with the cmparts settings and others with the network, so they are not implemmented in v2.0 or v2.2.7 but dont worry the important tweaks are already running at the boot start
fix camera saving 90 degrees rotated files or fixing adrenalin camera transparency menus problem - i will do the one that is quick and wont be more a pain in the a**
fix the camera and gps battery drain that results from their using - that comes from the sources, the problem isnt after their use, is while we are using those apps. a friend is already trying to make them a little less energy drainners, lets see if he can do that
FM radio -> still a pita but dont force close the fm radio app anymore
modding
fix some icons that overcome the text bellow in buttons -> done
a bug resulting in a fc on the config of the light button at cmparts, options are already configured but if we want to change it, it forces close
fix the size of some menus (bigger than adrenalin and some bigger than stock), its a problem because this is an mdpi rom now instead of a ldpi like adrenalin -> 30% done
p.s.- i will try making those fixes not requiring any wiping, its a bummer doing wipes everytime and it wears the nand memory (from what i could investigate, only after 100k wiping cycles, lol, still have lots)
i will put more after
Click to expand...
Click to collapse
Just wanted to report back on version 2.2.7.
It seems to keep more apps in the memory and multitasking is for the first time kinda usable on gingerbread.
Menu buttons are fine now
ICS rotation is awesome!
Still cant notice a difference with beats audio, because our soundcard just sucks more then can be fixed by software, even stock wasn't good.
Bravia engine, can i turn that on and off at some place or is it enabled by default?
Only problem i noticed, after upgrading, the gmail app was gone and if i installed it from the play store it just crashed. Could be fixed by moving the apk to /system/app and fixing permissions.
Seems like its slowly getting better and better.
Thanks for your work!
Silas
that was my fault. i posted the wrong updated gapps (missing facebook, gmail, etc), tx for reporting
later i'll fix that
bravia is on by default in build.prop
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
Click to expand...
Click to collapse
to disable, 1->0
i tried to add an on/off to settings but... (i'll work on that later again). i noticed a difference in the taken pics, not on the camera display (stock cam app sucks, try the sleek cam and see the difference, clear img)
is hard to notice beats audio but u can tell if u put full volume that it doesnt distort audio like stock eclair. try setting a preset in the dsp manager
but that is one of the reasons i'll try xloud or megabass
edit: gapps fixed
edit2: lol
weird stuff
trying to add an Bravia on/off to settings, managed to fc wireless setting in the proccess. the surprising stuff was the free ram it left available.
135/178 mb (available/total) ->>>> something to lookup. to see if it can be managed to have all that free ram and have a full working O.S. <- that would be something really big to this little device (gameboy, lol)
btw, Silas, have u done a data wipe before fashing 2.2.7?
NAZUnlimited said:
edit2: lol
weird stuff
trying to add an Bravia on/off to settings, managed to fc wireless setting in the proccess. the surprising stuff was the free ram it left available.
135/178 mb (available/total) ->>>> something to lookup. to see if it can be managed to have all that free ram and have a full working O.S. <- that would be something really big to this little device (gameboy, lol)
btw, Silas, have u done a data wipe before fashing 2.2.7?
Click to expand...
Click to collapse
We do have 256MB of ram built in, right? Should the os itself really take more then 100MB, as it doesn't even has a GPU to keep up and running?
It actually quite noticeable how much faster the HTC Wildfire is, with the same CPU, but more RAM.
Nope, i didn't do a data wipe, just cache and dalvik. But my phone has now started to behave the same way as with your first patch, it doesn't keep the settings (for example the screen brightness resets itself) and i cant go to airplane mode.
I will see if your latest gapps update fixed that, and then report back. When the always terribly slow rapidshare has finished downloading
funny. my downloads and uploads are fast from rapidshare. i uploaded gapps from my u8300 in 4min. (i might switch to dropbox the big files and leave rapidshare for the stuff with 2mb or less)
according to http://whirlpool.net.au/wiki/huawei_u8300, we have 256mb, but unless the 178mb that appear in status are the ammount of ram available for the user and the missing rest (that dont appear anywhere) for the o.s. ,.... u get the idea.
512mb of memory flash
192mb- data
170mb- system
70mb - cache
3-4mb- boot
1mb- splash screen ( bootlogo)
(the rest for mombo-jumbo partitions like OTA)
the day i figure how to change partitions size without messing the phone internals.... that will be a good day
i was affraid of that. i do not experience that but i flashed with full wipe. not using data wipe was only tested with users that dont keep much stuff in data (almost nothing only apps) and i dont know if they changed the default settings and since none reported any problem, i figured it was fine.
like i said, v2.2.7 is a new rom, only the looks is the same as v2.0. that bug now (since i still didnt put the super 3g tweaks that busted those settings) is probably resulting from the saved settings/info/etc in data partition.
since i removed those tweaks, i have not seen that bug again and i am using v2.2.7 for almost 2 weeks now.
NAZUnlimited said:
funny. my downloads and uploads are fast from rapidshare. i uploaded gapps from my u8300 in 4min. (i might switch to dropbox the big files and leave rapidshare for the stuff with 2mb or less)
Click to expand...
Click to collapse
4min for a 15MB file is not fast for me, im used to about 15seconds for that. (and i still have one of the slowest broadband connections here in sweden )
NAZUnlimited said:
according to http://whirlpool.net.au/wiki/huawei_u8300, we have 256mb, but unless the 178mb that appear in status are the ammount of ram available for the user and the missing rest (that dont appear anywhere) for the o.s. ,.... u get the idea.
512mb of memory flash
192mb- data
170mb- system
70mb - cache
3-4mb- boot
1mb- splash screen ( bootlogo)
(the rest for mombo-jumbo partitions like OTA)
the day i figure how to change partitions size without messing the phone internals.... that will be a good day
Click to expand...
Click to collapse
Running aplications is showing about 50-70MB in total, so the OS must use ~200MB for something
Another thought, would it maybe help us if we use the sdcard for swapping? I'll try that today and look if i can notice any difference
Flash memory is not that much of a problem, as we have app2sd.
NAZUnlimited said:
i was affraid of that. i do not experience that but i flashed with full wipe. not using data wipe was only tested with users that dont keep much stuff in data (almost nothing only apps) and i dont know if they changed the default settings and since none reported any problem, i figured it was fine.
like i said, v2.2.7 is a new rom, only the looks is the same as v2.0. that bug now (since i still didnt put the super 3g tweaks that busted those settings) is probably resulting from the saved settings/info/etc in data partition.
since i removed those tweaks, i have not seen that bug again and i am using v2.2.7 for almost 2 weeks now.
Click to expand...
Click to collapse
It's a pretty random problem. Yesterday the bug was there, but after reflashing the new gapps and replacing superuser with supersu, it's fine again
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 . 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
- 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
Sent from my U8300 using xda premium
NAZUnlimited said:
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 . 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
- 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
Sent from my U8300 using xda premium
Click to expand...
Click to collapse
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?
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]"
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.
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
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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
a good memory management
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://forum.xda-developers.com/showthread.php?t=1227269
Also, Rom Toolbox is fantastic for this kind of tweaking, just a tip
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
Sent from my U8300 using xda premium
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 ) 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
nice to see that someone is making stuff for our phone. like tuono once said, "i was starting to feel a little lonely here"
if u are using the ones from u8150, its normal they work good with vicky. like most roms made from cyanogen sources for huawei phones (u81xx/u82xx/u85xx/u88xx/m86x, etc), they all use the official u8150 code and part of vicky's code is also based on those sources, the rest is based on samsung.
about auto-brightness, u replaced the cmparts.apk. the "bug" is on that apk. its not an error in the code but something else interfering with the openning of that setting. i've tried the lux app and it proved me that auto brightness is working. activating the brightness icon (not the app in drawer but the toogle like the wifi, bt) in the toolbar (systemui.apk) and then pressing it until it reach auto, showed that too. i wasnt much concerned with that because i think it works backwards, when in sunlight it reduces the brightness and in darkness is the opposite, it burned my eyes when i used (i have photo-sensitivity <- i think thats the right name in english for that) and u8300 display is hard to see with sunlight and low brightness. but everyone is free to use what they see fit to it.
about performance, u are right. most performance increased is an illusion and its not. i did a couple of tests before i succumbed to the urge to change the stock looks (lol. i was forced by u know who ). i tested with stock look, mod look and stock look with a theme applied (using theme chooser). the results were pretty much the same but only modded looks got allways higher scores. most definitely because most pngs are smaller in kb than the ones from sources and the ones in the theme apk, that size makes all the framework (i'm not just talking about framework-res.apk here but all that is loaded for the display view) to occupy less in memory therefore granting more performance. but all that is if using vicky's apps, generated from vicky's mixed sources. now the reason that u have or appear to have an increased performance is because u replaced most system apps except the jar files. most of them dont make a difference but systemui, settings, cmparts and frameworks-res make. a quicky way to explain is if u think those apps as computer hardware and programs that run at windows start. if u disable some hardware and block some services and programs to start at boot, u will notice an increased performance in the pc, that is what u did. by replacing those apps u disabled some "instructions", since they wont run, more performance. just like when i crashed the network settings and freed a lot of ram. the jar files in frameworks folder use those instructions to make run some stuff like the 1% battery. stock only has 10% battery indicator.
i hope i explained myself well. its 6h in the morning here and i dont sleep for almost 34h. and i have to feed Vicky (btw, Vicky is the cat)
i am a bit curious about some things. why the rom manager and cmwallpapers conflict? those apps are universal. (cmscreenshot, u did have to replaced it, its universal, same code for every gb rom)
about the looks, i am making it a theme chooser app. it will make more easier for me to do the needed stuff in system apps without having to concern about the looks and the ones that dont want that look can easily change it or delete.
other thing, battery seems mor stable now. heres a screenie
NAZUnlimited said:
nice to see that someone is making stuff for our phone. like tuono once said, "i was starting to feel a little lonely here"
if u are using the ones from u8150, its normal they work good with vicky. like most roms made from cyanogen sources for huawei phones (u81xx/u82xx/u85xx/u88xx/m86x, etc), they all use the official u8150 code and part of vicky's code is also based on those sources, the rest is based on samsung.
Click to expand...
Click to collapse
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).
NAZUnlimited said:
about auto-brightness, u replaced the cmparts.apk. the "bug" is on that apk. its not an error in the code but something else interfering with the openning of that setting. i've tried the lux app and it proved me that auto brightness is working. activating the brightness icon (not the app in drawer but the toogle like the wifi, bt) in the toolbar (systemui.apk) and then pressing it until it reach auto, showed that too. i wasnt much concerned with that because i think it works backwards, when in sunlight it reduces the brightness and in darkness is the opposite, it burned my eyes when i used (i have photo-sensitivity <- i think thats the right name in english for that) and u8300 display is hard to see with sunlight and low brightness. but everyone is free to use what they see fit to it.
Click to expand...
Click to collapse
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
NAZUnlimited said:
about performance, u are right. most performance increased is an illusion and its not. i did a couple of tests before i succumbed to the urge to change the stock looks (lol. i was forced by u know who ). i tested with stock look, mod look and stock look with a theme applied (using theme chooser). the results were pretty much the same but only modded looks got allways higher scores. most definitely because most pngs are smaller in kb than the ones from sources and the ones in the theme apk, that size makes all the framework (i'm not just talking about framework-res.apk here but all that is loaded for the display view) to occupy less in memory therefore granting more performance. but all that is if using vicky's apps, generated from vicky's mixed sources. now the reason that u have or appear to have an increased performance is because u replaced most system apps except the jar files. most of them dont make a difference but systemui, settings, cmparts and frameworks-res make. a quicky way to explain is if u think those apps as computer hardware and programs that run at windows start. if u disable some hardware and block some services and programs to start at boot, u will notice an increased performance in the pc, that is what u did. by replacing those apps u disabled some "instructions", since they wont run, more performance. just like when i crashed the network settings and freed a lot of ram. the jar files in frameworks folder use those instructions to make run some stuff like the 1% battery. stock only has 10% battery indicator.
Click to expand...
Click to collapse
So your framework-res.apk is smaller? (don't have your files left, and rapidshare is still slow ) 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?)
NAZUnlimited said:
i hope i explained myself well. its 6h in the morning here and i dont sleep for almost 34h. and i have to feed Vicky (btw, Vicky is the cat)
Click to expand...
Click to collapse
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
NAZUnlimited said:
i am a bit curious about some things. why the rom manager and cmwallpapers conflict? those apps are universal. (cmscreenshot, u did have to replaced it, its universal, same code for every gb rom)
Click to expand...
Click to collapse
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.
NAZUnlimited said:
about the looks, i am making it a theme chooser app. it will make more easier for me to do the needed stuff in system apps without having to concern about the looks and the ones that dont want that look can easily change it or delete.
Click to expand...
Click to collapse
Ok, the perfect thing for me would be a smaller stock theme.
NAZUnlimited said:
other thing, battery seems mor stable now. heres a screenie
View attachment 1135355View attachment 1135356
Click to expand...
Click to collapse
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
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.
Is it epilepsy you have? Its when you react to fast color/light changes?
Click to expand...
Click to collapse
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.
Could someone (NAZUnlimited) please check how much memory "Android System" and the service com.android.systemui is using?
Click to expand...
Click to collapse
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
So your framework-res.apk is smaller? (don't have your files left, and rapidshare is still slow ) 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?)
Click to expand...
Click to collapse
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)
NAZUnlimited said:
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
Click to expand...
Click to collapse
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
NAZUnlimited said:
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.
Click to expand...
Click to collapse
That image in the top right?
I also noticed that video recording is broken, no idea why.
NAZUnlimited said:
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
Click to expand...
Click to collapse
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.
NAZUnlimited said:
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)
Click to expand...
Click to collapse
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
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 ) 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