Hello,
I flashed this kernel http://forum.xda-developers.com/showthread.php?t=1468043 for FXP - stuck on fxp logo
flashed http://forum.xda-developers.com/showthread.php?t=1566871 for CM 128 - boot ok, but no wifi
of course I'm using CM9 129 rc1
Where I have made mistake?
Problem SOLVED reinstall and reinstall and reinstall finnaly wifi work fine
Related
Not sure if I have missed it on the download page or not but I can not find it.
We have to use the kernel from FXP115.. So you need to download both 115 & 116.
It is included in the FXP#115 download which doesn't seem to be available for D/L and can't be mirrored. However, I am running Champkernel fxp113-cm7, (download link (http://hotfile.com/dl/150248726/e4051be/fxp113-KCernel-beta1.ftf.html)) from http://forum.xda-developers.com/showthread.php?t=1564056 on FXP116-CM7.2.0 and it works Great. Give it a try.
tal333
omg_hacker said:
Not sure if I have missed it on the download page or not but I can not find it.
Click to expand...
Click to collapse
Changed from FXP cm7.2 to cm9, now stuck on Bootscrenn
I thougt cm7.2 and cm9 use the same Kernel. So i was on fxp cm7.2 116 and installed xrecovery cm9 116. Now im stucked on bootscreen. What to do now? Install cm9 Kernel via Flashtool?
Hi,
I'm trying to run CyanogenMod 9.0 at my X10, but after I flash new ROM (FXP116) it just stucks on fxp logo. Tried everything, wiping data, cache, dalvik but didn't help. I use the kernel from CM 7.2. Do You know how to make it work?
jakuburban said:
Hi,
I'm trying to run CyanogenMod 9.0 at my X10, but after I flash new ROM (FXP116) it just stucks on fxp logo. Tried everything, wiping data, cache, dalvik but didn't help. I use the kernel from CM 7.2. Do You know how to make it work?
Click to expand...
Click to collapse
No use only the kernel provided for CM9 .For FXP 116 use FXP115 kernel.
http://www.mediafire.com/?odc6xu2sbk67q6s
Vasishta Reddy said:
No use only the kernel provided for CM9 .For FXP 116 use FXP115 kernel.
http://www.mediafire.com/?odc6xu2sbk67q6s
Click to expand...
Click to collapse
Thanks. That worked I just can't wait when the ROM will be fully working
This thread is for general question about Cyanogenmod9 from FreeXperia Project so that people stop asking on the development thread
Post any questions you have followed by CM version and the release number and if it is possible cpu freq and if you flashed any other tweaks/changes
e.g. CM9-fxp134 with [email protected]+ V6supercharger tweak
All credit goes to FXP team for supporting our phone!
FreeXperia Project
Bin4ry, Defer, Kali, Jerpelea
Latest releases
CM7.2 - http://code.google.com/p/freexperia/wiki/CyanogenMod7
CM9.0 - http://code.google.com/p/freexperia/wiki/CyanogenMod9
CM10 RC0 - http://code.google.com/p/freexperia/wiki/CyanogenMod10
GOOGLE APPS - http://goo.im/gapps/
CM9 Baseband (recommended for 2011 devices)
http://ul.to/folder/um2ivw
mirror
http://fiberupload.com/users/jerpelea/8291/CM9_Baseband
BUGTRAKER & CHANGELOGS @ http://code.google.com/p/freexperia/
SUPORTED DEVICES http://code.google.com/p/freexperia/...dXperiaDevices
This:
[Q] [DEVS] Touch Screen Issue/Bug with CM/AOSP Based ROMs. NEO V MT11a
Jonfensu said:
This:
[Q] [DEVS] Touch Screen Issue/Bug with CM/AOSP Based ROMs. NEO V MT11a
Click to expand...
Click to collapse
Are you sure the kernel is flashed. you can check this in fastboot when flashing it or turn on the phone and you'll see the FXP logo.
Try again with fxp134 CM9
-reboot recovery
-whipe everything(data,cache,dalvik,system)
-flash rom and successfully install kernel via fastboot(doesn't really matter wich is first rom or kernel)
-reboot via recovery or fastboot comand.
-turn on the phone and check again if touch works.
Or you can try This and I also recomend to run a logcat or check if the device encounters errors via Dalvik Debug Monitor(located inside the android-sdk folder/tools/ddms.bat)
paul678 said:
Are you sure the kernel is flashed. you can check this in fastboot when flashing it or turn on the phone and you'll see the FXP logo.
Try again with fxp134 CM9
-reboot recovery
-whipe everything(data,cache,dalvik,system)
-flash rom and successfully install kernel via fastboot(doesn't really matter wich is first rom or kernel)
-reboot via recovery or fastboot comand.
-turn on the phone and check again if touch works.
Or you can try This and I also recomend to run a logcat or check if the device encounters errors via Dalvik Debug Monitor(located inside the android-sdk folder/tools/ddms.bat)
Click to expand...
Click to collapse
I tried everything (Except the last link) and Nothing..... Some users are facing the same problem so.... its not a isolated case
Jonfensu said:
I tried everything (Except the last link) and Nothing..... Some users are facing the same problem so.... its not a isolated case
Click to expand...
Click to collapse
I really think it's a kernel problem, the kernel controls the touch area, but i can't see an answer hmm
Battery drain
I have installed cm9 stable version today and it's battery backup sucked..... 25% battery is drained in just 1 hour.....
Here's what I did
1)flashed baseband .72 provided by fxp (I was on .64)
2)flashed kernel provided by fxp
3)wiped and formatted data,cache,davik cache, system from recovery
4)installed rom and gaaps
Plz help me on this battery issue....
(I was on official 2.3 with night elf kernel)
First flash of ROM your battery will get hammered its after a day its ok
neo is tiny little poo phone
Off topic
Can't seem to make WiFi Tether work in cm10 fxp135. It's on but other devices can't see it.
---------- Post added at 09:42 AM ---------- Previous post was at 09:37 AM ----------
Barnacle WiFi Tether and other Tether apps show error. I just want you to know. That's all. BTW, this won't stop me from using this ultra smooth rom. Not even the Camera thingy. FXP rocks!:highfive:
Edit: CM10-fxp135
akash77 said:
I have installed cm9 stable version today and it's battery backup sucked..... 25% battery is drained in just 1 hour.....
Here's what I did
1)flashed baseband .72 provided by fxp (I was on .64)
2)flashed kernel provided by fxp
3)wiped and formatted data,cache,davik cache, system from recovery
4)installed rom and gaaps
Plz help me on this battery issue....
(I was on official 2.3 with night elf kernel)
Click to expand...
Click to collapse
Battery calibration may help
Is there any difference between "FXP136- CM9.0" and cm-9.1.0 stable (from get.cm)
prasan2014 said:
Is there any difference between "FXP136- CM9.0" and cm-9.1.0 stable (from get.cm)
Click to expand...
Click to collapse
The unofficial one from FXP has FMradio built in and some tweaks to memory management. Those are the most important ones
Hi all,
I could not find the FXP rom for neo v(haida). I know it is 2019 But need it so much.
Neo v (Haida) is not listed here:
http://uploaded.net/f/59w3fb
Thanks.
is thr any1 try this new rom ad?
before v2.55, 2.54 had a lot of problem
tis problems MAYBE cum from CM10
i dun noe which version of CM10 can be used
is any1 had used the latest paranoid without problem? ( wifi, camara and etc)
[sry for my bad english]
you can flash lastest ver cm10
PA Haida v2.55 in Xperia Neo V
arch_saiful said:
you can flash lastest ver cm10
Click to expand...
Click to collapse
I flashed CM10 151 ... wifi not working ... even in setup process, mobile data auto turned on ... any fix?
you have to use fxp 145 kernel..latest kernel (146 onwards) are not working...not even PACman kernel or LUPUS...
tried myself..I am on fxp 145 kernel with PA 2.55..
XperiaNeoVNoob said:
you have to use fxp 145 kernel..latest kernel (146 onwards) are not working...not even PACman kernel or LUPUS...
tried myself..I am on fxp 145 kernel with PA 2.55..
Click to expand...
Click to collapse
I had installed CM10 fxp 203 and PA 2.55 but my phone
doesnt used to boot sometimes and i had to take out d
battery then it used to start and CM 10 wifi and front Cam
were not working!!!
Plz help
So, I updated my SK17i from FXP 151 CM10 to FXP 152 CM10 but when I wanna turn on my wifi it won't turn on, it got stuck at wifi enabling..
Help?
Its a bug in the latest FXP 152 version...
You better switch back to FXP 151 for a stable wi-fi...
I see its your first so you can't post in development forum...
But next time try reading the feedbacks on the ROM thread... :thumbup:
Many users have faced the problem... In the current release
Yeah I managed to bypass this problem, for I use Flykernel V0.8.
I re flashed the wifi Module and voila.
all4flex said:
So, I updated my SK17i from FXP 151 CM10 to FXP 152 CM10 but when I wanna turn on my wifi it won't turn on, it got stuck at wifi enabling..
Help?
Click to expand...
Click to collapse
In flashtool flash the 'boot.img' in fastboot, than update FXP 152 and it should work
Sent from my Xperia Active using xda app-developers app
dcf007 said:
In flashtool flash the 'boot.img' in fastboot, than update FXP 152 and it should work
Click to expand...
Click to collapse
Wow this worked :laugh: thanks! :good: