Can anyone confirm if the backlight flicker on device wake up is fixed in FXP 134 ?
If you ask me this is the best ICS rom of all ICS roms there is, at least for the WT19i. It's the fastest, smoothest and it got the best battery time. Everything is better, you won't be disappointed =)
for CM9, this one: http://goo.im/gapps/gapps-ics-20120429-signed.zip
for CM9, this one: http://goo.im/gapps/gapps-ics-20120429-signed.zip
Thank you! Just flash it via CWM or I have to do something else?
Why everytime I unlock the screen brightness is set to low and I have to set it to max again and again??? Even if I set it to minimum it dims even more after I unlock the screen...
EDIT: Can't play Temple run with this ROM... Tilting the phone lags very very very much...
Sent from my LiveWithWalkman using xda app-developers app
I think is for everyone, I'm using XM too & can't change the resolution.just flashed fxp134 with newest kernel and still there isn't an option to change video resolution
I'm using Xperia Mini
it is only me or everyone?
The brightness works fine for me.Someone else has these problems? Please test it!
Sent from my LiveWithWalkman using xda app-developers app
Can anyone confirm if the backlight flicker on device wake up is fixed in FXP 134 ?
I think is for everyone, I'm using XM too & can't change the resolution.
The brightness works fine for me.
Well I played asphault, sonic & batman without any lag, but first I flashed the accelerometer fix by ronaldvalles.
Link: http://xdaforums.com/showthread.php?t=1747267
Thanks! Accelerometer fix works for me! And about the brightness I guess I'll try to reinstall the ROM clean. :fingers-crossed:
I don't make a clean install since fxp131 & works for me. Try a clean install & report if works
Is it okay that I flashed firmware via flashtool, then flashed CM9 baseband, then flashed kernel and only then I turned on my device and booted to recovery and installed ROM? Maybe I should turn on my device after flashing firmware and then flash baseband and kernel? Does it make any sense?
Supposing you just have baseband 72 from fxp first post, you can just flash the boot.img(kernel) then flash the rom and before you reboot system make a wipe data/factory reset for a clean install.I always do that when I want a clean install. You should make a backup before if anything goes wrong. Hope this helps you
So I should wipe everyhting AFTER, but not BEFORE the installation? OMG! I always wiped everything BEFORE installation. :laugh: :laugh: :laugh:
And do I have to wipe dalvik-chache, system, cache, sd-ext after installation?
Yes, after install the kernel & rom. If you can´t see any change try wipe dalvik-chache, system, cache, sd-ext.
just flashed fxp134 with newest kernel and still there isn't an option to change video resolution
I'm using Xperia Mini
it is only me or everyone?
never wipe system!Yes, after install the kernel & rom. If you can´t see any change try wipe dalvik-chache, system, cache, sd-ext.
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.