{Mini/MiniPro/Active/Live}[DEVELOPMENT] - CM9.1 - FreeXperia Project

Search This thread

lokaltrafik

Member
Jan 14, 2011
20
3
Last edited:

Maceee

Senior Member
Jul 2, 2012
712
104
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
 
Last edited:

Maceee

Senior Member
Jul 2, 2012
712
104
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

Someone else has these problems? Please test it!

Sent from my LiveWithWalkman using xda app-developers app
 

mauam

Senior Member
Jan 26, 2011
7,353
12,932
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?
I think is for everyone, I'm using XM too & can't change the resolution.
Someone else has these problems? Please test it!

Sent from my LiveWithWalkman using xda app-developers app
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
 
Last edited:
  • Like
Reactions: Maceee

Maceee

Senior Member
Jul 2, 2012
712
104
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:
 
  • Like
Reactions: mauam

Maceee

Senior Member
Jul 2, 2012
712
104
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?

EDIT: Just did the clean install as I said and the same problem with display brightness exists. I set it to max, but after I lock and unlock my screen the display is dark and I have to set it to max again and again and again. I'll try first turn on my device after flashing firmware. Maybe this will help.
 
Last edited:

mauam

Senior Member
Jan 26, 2011
7,353
12,932
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:)
 

Maceee

Senior Member
Jul 2, 2012
712
104
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?
 

mauam

Senior Member
Jan 26, 2011
7,353
12,932
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.:)
 
  • Like
Reactions: Maceee

Maceee

Senior Member
Jul 2, 2012
712
104
Yes, after install the kernel & rom. If you can´t see any change try wipe dalvik-chache, system, cache, sd-ext.:)

Thanks. I'll try this and report. :)

---------- Post added at 06:57 PM ---------- Previous post was at 06:46 PM ----------

Thanks. I'll try this and report. :)

I installed the ROM, then did wipe data/factory reset, rebooted phone but the same problem exists. I set screen brightness to max, lock, unlock my screen and the dislpay is really dark, but when I touch the brightness bar the display immediately turns to very light, but after locking the screen it turns to dark again...

Even when I'm in CWR the display is darker than before installing the ROM!
The screen turns dark when the CM9 is booting after first installation and after then the screen is always dark. Even in CWR!

---------- Post added at 07:23 PM ---------- Previous post was at 06:57 PM ----------

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?

I can change the resolution between 480p and 720p with FXP134.
 
Last edited:
  • Like
Reactions: mauam

Top Liked Posts

  • There are no posts matching your filters.
  • 99
    WORKING
    AUDIO - ok
    GPS - ok
    WIFI - ok - new wl12xx_mac80211
    TOUCH SCREEN - ok
    CWM RECOVERY 5.5 - ok
    BT - ok
    GSM - ok
    VIDEO DECODER - ok
    3D - ok
    GRALLOC - ok
    HOTSPOT - ok
    USB UMS - ok
    CAMERA - ok (including video recording)
    ANT+ - ok
    HDMI - disabled
    FM - ok
    CAMERA - ok

    NOT WORKING
    look on bug tracker for remaining bugs
    74
    DOWNLOAD
    http://unrestrict.li/FXP

    IMPOTANT
    Unlocking device on unlock website or by testpoint voids your waranty !
    18
    hy all

    1. we explained serveral times that even if an kernel is tested after all patches are merged there can be upstream changes that break it (no boot bug)
    we test every release when we work on something and then build is started for all devices

    2. we release weekely so that we can test togeter for bugs and try to please everybody that is asking for new roms as soon as old one is released (we get mails for new release on monday morning at 5 min after previews rom is released)

    3.MOST IMPORTANT - this is an development thread
    if you want to join us you can anytime contribute and fix things but all your pushes are useless unless those are pushed to cyanogen review system so that everybody can test and merge them upstream

    4.STOP advertising other roms "i will move to xxx ROM wich is better"
    this is an development thread, you are free move to any rom you wish,

    5.STOP asking for SONY features or camera
    those are prop stuff and are not open source
    if you need them move to stock rom

    6.DELAYS and BUGS
    we are 4 people maintaining 12 devices and adding 6 new devices
    we have jobs and families, we have our own life and we do the work done usually by hundred people

    7.DONATIONS
    we want to thank to all donors wich donated an total amount of supported our work

    WE WORK IN OUR FREE TIME AND WE ARE NOT PAYED SO STOP ASKING US FOR DEADLINES, FEATURES, AND BUGS (we will fix/add them in time)
    br
    J
    FreeXperia Team



    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).
    15
    FXP148 released
    upload will take 1h
    FXP148 extended kernel released for Xperia Mini Pro.

    I will release a kernel for the Xperia Mini too later, but please note it is untested, because I don't have such a device.

    I will try to release an extended ROM for the Xperia Mini Pro today and one for the Xperia Mini tomorrow (last one untested).

    The kernels will have the latest FXP fixes (if they were all released) and the ROM's will now have ALS enabled and a backported CMFileManager included.

    See the links in my signature for details.

    Edit: kernels for both devices and ROM for one device available, ROM for Xperia Mini is being uploaded now.