6 bugs so far on my Xperia Active:
- Home Button does nothing
- Bluetooth headsets won't work
I can pair and connect all of them but audio will keep playing on the phone only
BT-Heartrate strap works fine though.
- Audio Playback is stuttering (with both the default player and mortplayer)
- Browser does not work (loads for a while then crashes)
- no data connection (as stated)
- after the phone was lying around for 15m it was very unresponsive (was not able to unlock it) and rebooted by itself
Has anyone else got installation aborted on xperia mini st15i coming from .42 firmware.
I am also unable to unlock the sim-card on my sk17ii can't call, it doesn't ask for my pin code on Live with walkman
keyboard does not show space bar and others so how do i sign in.
Also the browser keeps quitting after halfway loading
Install Gapps ani5... if you install them immediately after you install the rom then it will work fine, i guess this answer will get lost within the pages, and more people will start ranting about the browser crashing..
Install Gapps ani5... if you install them immediately after you install the rom then it will work fine,
try to install any keyboard from market (like gingerbread keyboard) and it will work..Xperia MIni Lots Of Problem
Screen Buttons Menu And back Buttons Have No Light
Keyboard Has No Symbols And Space Button
When You Choose Ringtones Screen Graphics Will Break and lots of other bugs and lags.
I think there is a another philosophy and they're not lazy... As I said, please don't be personally.
First one is: I am sure they are testing. But they aren't testing the whole builds, they just flash/add their fixed libraries or modules manually and these work.
Then: The kernel thingy: they fixed their kernel... but possibly forgot to make the appropriate changes to the build scripts that run the complete builds for public delivery. This is almost also a lot of work to do. Just look yourself: hnl_dk posted threads on "how to build you own cm" sync that repos to your workarea and look at the huge amount of build scripts and how they are dependand... if you update/sync your repo regularly you will see there are at least daily changes on the build scripts... as well on the side of cm...
The cyanogenmod is very collaborative. THere are also sometimes bugs in the CM, that FXP is not responsible of (like this statusbar-bug(s)), but they take the rumors.
I agree FXP could be more "sorry" also of things they are not really responsible of... but this also would make people more happy. But the philosophy behind is: If a build gets sadly broken by a little mistake... it will get fixed with next build and they do it about every week... but you can do it yourself, too.
More or less I can also say: its the lazy people that don't go through this huge XDA community to find out how to build their own working kernel or how to fix the broken kernels with correct ramdisk... They're also too lazy to make senseful analysis and give appropriate bug reports.
I don't think your view of how they work matches the truth of how they work. Because there is no "they" there is a "we" and a main group called "FXP" that helps us with (developing) skills the most of "we/us" does not have. So in my view it is wrong to nag around. You can whine but at the same time you should give information or do something against that... this will help us making the rom complete
Aaand: nags cause lack of motivation, so the more you nag against the "we", the more you destroy it... then don't expect help... etc.
Btw: what do you mean it lags? cm9 is also very smooth now. Remember you have to fill the dalvik cache first. so there is always one or two reboots needed (after full startup) to have this smooth feeling. I also recommend ondemand or smartassV2 governor (smartassV2 has to be added to kernel manually), I also encountered lags with interactive (the default one).
FXP148 extended kernel released for Xperia Mini Pro.