TX users ? For FXP.....
- Thread starter BreckZeBoulay
- Start date
A poll for everyone who tried CM10 for TX
1- Your touch firmware version : a, b or c
2- Which version of FXP tested : 206. 207, 208, 209
3- Recovery upside down and artifacts : yes or no (for each version tested)
4- Screen rom upside down : yes or no (for each version tested)
1- Your touch firmware version : a, b or c
2- Which version of FXP tested : 206. 207, 208, 209
3- Recovery upside down and artifacts : yes or no (for each version tested)
4- Screen rom upside down : yes or no (for each version tested)
Last edited:
1. C
2. Tested fxp206
3. Recovery - Upside Down
4. ROM - normal, not upside down
Tapatalked from my TX
2. Tested fxp206
3. Recovery - Upside Down
4. ROM - normal, not upside down
Tapatalked from my TX
championswimmer
Inactive Recognized Developer
could you guys post similar reports for AOKP versions too ???
download either build5 or m1-r3 from here
http://goo.im/devs/kxp/hayabusa
download either build5 or m1-r3 from here
http://goo.im/devs/kxp/hayabusa
B
206-209
206-208 recovery ok
209 recovery upside down and glitches
206-209 Roms are upside down
Sent from my LT29i using xda app-developers app
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
I have tried yours before. Recovery was ok but Rom was upside down
Sent from my LT29i using xda app-developers app
206-209
206-208 recovery ok
209 recovery upside down and glitches
206-209 Roms are upside down
Sent from my LT29i using xda app-developers app
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
I have tried yours before. Recovery was ok but Rom was upside down
Sent from my LT29i using xda app-developers app
Touch FW C
All recoverys are upside down fxp 208-209 pixelsalad recovery. Keyboard errors saying it cant find android keyboard. Home button not responding in 208-209 too.
AOKP Builds same as CM same errors no differences.
All recoverys are upside down fxp 208-209 pixelsalad recovery. Keyboard errors saying it cant find android keyboard. Home button not responding in 208-209 too.
AOKP Builds same as CM same errors no differences.
You use GAPPS for version 4.2.X, download and install the GAPPS for version 4.1.2 and home button will work, and the keyboard will not show the error.
runs to check gapps...... 12-12-2012... 10.1. Ok thanks ill re test everything and the errors I find I'll put in the FXP CM10 dev thread with logcats.
Thanks nnmka for the catch.
Also a bug the speaker for the ringtones is very very very distorted and low. I don't know if that was mentioned or not.
Last edited:
FXP 210:
Recovery reversed again.
Brightness does not work.
If you do not use the phone for a long time, Wi-Fi is turned off and must be restarted manually.
Not earned headphones Sennheiser, although the drain worked fine.
No light inscription XPERIA.
Not working bistable the camera key.
Reboot into sleep mode =(
Recovery reversed again.
Brightness does not work.
If you do not use the phone for a long time, Wi-Fi is turned off and must be restarted manually.
Not earned headphones Sennheiser, although the drain worked fine.
No light inscription XPERIA.
Not working bistable the camera key.
Reboot into sleep mode =(
Nice build so far.
And mirroring via MHL is working too, sweet.
Tapatalked from my TX
And mirroring via MHL is working too, sweet.
Tapatalked from my TX
Last edited:
Can anybody running on stock Rom tell me what's their total RAM when viewed at settings-apps-running.
I'm on fxp 210 right now and it's showing me I only have 674MB RAM, is this the default for stock Rom also? TIA
Tapatalked from my TX
I'm on fxp 210 right now and it's showing me I only have 674MB RAM, is this the default for stock Rom also? TIA
Tapatalked from my TX
Last edited:
Awesome! the TX is one of the most neglected devices around
couldnt agree more!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
4
I don't see what the benefit is... From everything I've talked to, the only difference (software-wise) is the panel (display).
In short, it's looking like only a difference of a few kernel patches (some of which still need to be made) and a defconfig.
99% of development effort for the two devices looks like it'll be common. (Of course, down the line, someone could find another difference, but so far - that seems to be the only significant delta.)
Just like, had people known just how similar I777 and I9100 would be in the end, the I777 probably would not have had its own forum. The difference between I777 and I9100 at this point are a few kernel defconfig items and two keylayout files.
FYI, the reason it took so long has nothing to do with whether the device has a separate forum or not. It has to do with the fact that a single TX owner finally stepped up, attempted to build for hayabusa, and cleaned up the problems they encountered.11Wait for FXP206 build..
FXP206
CM9.1
- latest cm 9.1
- variable notification time (U,Sola,Go)
CM10.0
- latest cm 10.0
- Fix call volume bug (S, Acro S, ION)
- alpha release (TX)
CM10.1
- latest cm 10.11Inverted recovery isn't a big deal since we can still use it, just a bit harder. Auto brightness does not work, but you can set the brightness manually which wasn't doable with ics (always 100%brightness). A huge improve. My phone hasn't reboot during sleep yet.
Sent from my Xperia TX using xda premium
