[Q] This is driving me nuts..CM9/FXP123 - Xperia Play Q&A, Help & Troubleshooting

Hi all,
Just recently flashed the new FXP123 build and the newest CM9 nightly. I am having an issue with both. As some may or may not know, the new FXP123 build came with a new kernel. This new kernel doesn't allow overclocking and seems a little sluggish.
My solution was to flash a different ICS kernel (KeICS v2, Darkforest v5, DooMKernel v3). Upon flashing a different kernel, WiFi would be broken. When I would attempt to turn it on, it just stays at "Turning Wi-Fi on..." indefinitely. When I reflashed the new FXP123 kernel, WiFi would be restored.
Are these new CM9 builds not compatible with other kernels? It seems odd that both FXP and the new CM9 nightly both have this issue. I've tried flashing the kernel before and after wiping data for a new ROM install, wiping after flashing, etc. I've tried using the different command in fastboot (fastboot -i 0x0fce flash boot <boot>.img). Nothing has worked.

Apparently FXP has changed the way wifi modules are loaded pax has said. Guess we just need updated kernels or patches. Solved?
Sent from my R800x using Tapatalk 2

Sluggish doesnt even begin to describe my experience with FXP123. It's my first time using CM9 so I can't compare it to previous builds, but holy crap is it slow.
Coming from CM7, I expected a small hit to performance but not to this extent. Everything takes 2-3 times longer to load or react on CM9 compared to CM7.
I hope this is just a problem with FXP123.

3dawg said:
Sluggish doesnt even begin to describe my experience with FXP123. It's my first time using CM9 so I can't compare it to previous builds, but holy crap is it slow.
Coming from CM7, I expected a small hit to performance but not to this extent. Everything takes 2-3 times longer to load or react on CM9 compared to CM7.
I hope this is just a problem with FXP123.
Click to expand...
Click to collapse
Try Aokp, it's latest build is based on fxp123 and is running smoothly without over clock, although I only have a few apps installed to prevent sluggishness
Sent from my Xperia Play using XDA

Nabeel_Nabs said:
Try Aokp, it's latest build is based on fxp123 and is running smoothly without over clock, although I only have a few apps installed to prevent sluggishness
Sent from my Xperia Play using XDA
Click to expand...
Click to collapse
I really love CyanogenMod and after seeing the behaviour of some AOKP devs, I'd rather not support them.
http://www.reddit.com/r/Android/comments/uj5bc/dont_bother_reporting_bugs_to_the_aokp_team_they/
Unfortunately the chat log was deleted but I'm sure if you dig into the comments, people have logs.
EDIT: I understand this is an unofficial AOKP port for the PLAY and is not developed by the assholes in the provided link (the same asshole who essentially stole a HP Touchpad and HTC resound from the dev community) , perhaps I should leave my prejudices at the door and try it.

3dawg said:
I really love CyanogenMod and after seeing the behaviour of some AOKP devs, I'd rather not support them.
http://www.reddit.com/r/Android/comments/uj5bc/dont_bother_reporting_bugs_to_the_aokp_team_they/
Unfortunately the chat log was deleted but I'm sure if you dig into the comments, people have logs.
EDIT: I understand this is an unofficial AOKP port for the PLAY and is not developed by the assholes in the provided link (the same asshole who essentially stole a HP Touchpad and HTC resound from the dev community) , perhaps I should leave my prejudices at the door and try it.
Click to expand...
Click to collapse
I agree with trying it don't let the conduct of one or two of them take away from romans amazing talent. And as you said it's unofficial, so support our devs here.
Sent from my R800x using Tapatalk 2

Pax will be releasing new ROMs and Kernals shortly I believe that hold the old WiFi modules which should work for you guys. But noticed since I flashed the last kernal provided by FXP I have seen massivve improvement. Litrally my phone was on 30% battery. Put my phone next to my bed and today morning woke up seeing the battery was only down to 25 percent. So then I put it in charge and in 1 hour I see the phone's led is green indicating fully charged and surprizingly enough it was fully charged.

Related

[Q] CM7 ROM Questions

Long time lurker first time poster... so don't beat me up too bad.
I'm looking at jumping into the CM7 world and am looking for some input.
I've used multiple versions of Skyraider up to 3.5 and loved them until they began getting a bit laggy (tried multiple kernels). I'm now using myn's warm 2.2 and ziggy's kernel with great success. Phone operates VERY smooth and all features work (not even sure why I want to try something new... guess I'm bored?).
Long story short, my phone is a daily driver and needs good battery life and all features to work (BT, camera, data, WiFi, etc...). I don;t mind flashing a few ROM's but it gets quite time consuing setting up the desktop screens, apps, calendars, etc...
I see that some builds break things, some fix things and it's hard to know which build does what. Many folks feel CM7 is the greatest thing since the Atari 2600; so here's my question:
What build are you using?
Does the phone scroll and transition smoothly?
All features working?
Getting FC's?
And yes... I have done quite a bit of reading on the CM7 nightly thread and others as well. People have a tendancy to post issues, not sucesses so it's difficult to find a good stable GB ROM.
Im on the latest release #37 I believe Using slayhers .37 kernal.
Love it. Altho, ever since I installed .37 kernal I've had my phone randomly reboot between 7:30 am - 9:00 am
I have yet to find out why... and it's only durring those hours too
I'm loving this ROM. Every time i go back to a sense, rom, i end up flashing cm6/7 back.
There are good things about cm6 and cm7... cm6 has a better camera app, probably more stable, but cm7 brings all the little things together, like multitouch keyboard + maps, it's snappy, the txting lag has been much improved. I think they are going to drop RC1 tonite..
I'm using build #33 with Chad's.37 kernel and everything's been running perfectly for the past few days. I don't think I've had a single FC or reboot. Battery life has also been very good, been using it pretty heavily all day and I'm down to 50%.
Just flashed 38, Have also used pretty much all the 20's 31 and 32. .37 Slayher Homebrewed #14
No reboots. I would say I could count the FCs on one hand easily and honestly don't blame the build I blame the app.
I used a number of roms before. Most of them from Rom manager. Now I am strictly a CM guy. Love these builds. I don't use Rom manager anymore either, just manually flash.
Personally, I'm someone who generally avoids experimental roms that still have incomplete functionality. Like you, my phone is a daily driver and I need to be able to rely on it. But CM7 was getting such rave reviews, I started to read up on it. It seemed that by the time I was hopping onto the bandwagon (nightly build 27 or so), everything was functional, there were just some things to be polished here and there.
It would be an understatement to say that I've been pleased.
To answer your questions specifically:
What build are you using? - Just flashed to #38, but have used a number of the builds
Does the phone scroll and transition smoothly? - Yes. For whatever its worth, I use LauncherPro Plus rather than ADW (which is what CM7 comes with)
All features working? - Yes. At least everything that I use.
Getting FC's? - Nothing that can't be traced back to another issue besides CM7
Don't get me wrong, I've had some tiny issues here and there, and some weird interactions, but nothing critical, and nothing that has stopped me from using this as my only rom.
I still keep old nandroids of the last two roms I used before CM7, but unless something drastic changes, they will just collect dust.
I've been using CM7 as a daily driver since like build 11, I haven't had any problems at all and its nice seeing new things added with each build
My dinc runs CM7 with the modified slayher .37 kernel. I runs super fast, but I haven't really noticed a significant increase in battery life. It used to crash, but since I set the wifi sleep policy to never, I have not had any problems.
build#38 ran awesome. no force closes and great battery life 20 hours or more. id say give it a try.
Just flashed RC1. Going great so far with only a few FC's that were solved with a simple reinstall.
Sent from my ADR6300 using XDA App
Did RC1, shaky, but amazing. Running 39 and it is better, has a lot of fixes that RC1 was plagued with. Like the rotary lock in the call screen.
I've been following CM7 development since Crackflashers. The rom has come a long way. Many people had problems with the first RC1 release because a mistake was made and those who did a clean wipe were locked out of the system. -Guess that should serve as a lesson to always nandroid first-
My advice is to continue flashing nightlies. As previously mentioned, the code will continue to improve and you will receive the latest fixes and features. Save yourself the trouble and clear cache and Dalvik before every flash. No need to wipe data.
Does anybody happen to know if there is a .37 version of the invisiblek kernel that includes the wifi sleep policy fix?
Its been working fine for me. The only problem I am having is that trackball wake doesn't function. I've made sure its selected int he CM settings, but I can press the trackball until kingdom come and it won't do anything. Looking at the dev. thread, I'm either the only one experiencing it, or the only one who cares.
SD card not mounting
flashed CM7 yesterday, really like how it runs. problem is my SD card won't load on the phone! I tried two different cards but no luck. recovery won't mount them either so I can't restore a nandroid backup. help!
also when I reboot most of the time, it'll show the htc incredible screen then go black and vibrate 5 times.
I'm running CM7 nightly #2 with the 2.6.37 incredikernel and it's great. Everything is very smooth and I can't seem to find anything that refuses to work. I had fc's when I first flashed the rom but fixing permissions in rom manager did the trick, since then I've had no problems.
I flashed CM7 as soon as they posted RC1 to ROM manager. I was skeptical at first and had a bunch of FC issues until I ran fix permissions (AFTER you install all apps). Haven't had issues since and my battery is lasting longer than ever, even without Juice Defender. Performs great. Can't wait until they get to adding more features like 6.1 had.
Sent from HTC Incredible [CyanogenMod 7 RC1]
Is it just me, or did Cyanogenmod lose some customization options from CM6.1 to CM7?
I dont see many editing options under CyanogenMod Settings and miss the ones from CM6.1
I'm on Build #41 and I can say a few things:
1) Battery life sucks on the Incredible no matter what. So just accept that. That being said, with Incredikernel .37 and CM7 Build 41, my battery life is "acceptable" compared to completely unacceptable with any other kernel or Sense Rom combination.
2) Random reboots. I don't know if it's just my phone, but even after trying three different .37 kernels, fixing permissions and re-flashing, my phone will go through "reboot anxiety attacks" where it reboots once every 10-12 minutes and then it will be fine for a whole day. It's not at specific times either.
3) Honeybread Theme - Get it. That's all.
4) Turn off wifi sleep completely. It seemed to curb some battery issues I was having.
Thanks All...
I went ahead and took the plunge and I don't regret it
I had some issues with RC1 and had to go to nightly #38. Everything has been solid with the exception of 2 random reboots (in the last 3 days). Not sure why but this isn't a show stopper.
I'll likley wait a while before flashing another nightly build.
So far so good. Batter life is ok... I know the Inc isn't the best for battery life but I got a bit better with Myn's ROM.
My quadrant numbers have improved (I know... relatively meaningless) and the UI is quite smooth.
Thanks to the development team... You've done a great job !!!

[Q] CM 7 Problems

O.k so here is the thing guys. I'm no noob but I'm no master either. Ok so I have a Evo 4G. It's been hacked since the first day that I got it (unrevoked). I'm currently running CM 7 RC 2 I believe and It's not that bad. The thing is that I always get these kind of weird bugs. I know I should be posting this in the CM7 forum but it wont let me because i'm fairly new to the site. Anyway I have always used CM and it's always been super buggy; even with the RC's. So my question to all of you is, am I doing something wrong when i install? I mean I used rom manager to install the rom, I do a backup and everything. Am I nandroiding wrong or something. For ex. my main android keyboard always freezes or just doesn't show up or I just get the most random force closes and other things like that. Help please because if I have to I will dump this CM, I'm getting kind of tired of it, but I just want to make sure it's not me that has the problem. Thanks in advance.
First of all, flash the latest nightly or the latest stable release, with a clean install and gapps, and that could fix things right there. Just backup your apps in titanium.
And make sure you're wiping properly. Instead of flashing the newer version as an update, do a full wipe. The last time I had issues like that with a rom, I went back and wiped everything multiple times and flashed a format all zip. Everything ran flawlessly after that.
I'd ditch Rom Manager too, and learn to flash manually. I don't fully trust Rom Manager to do what I would do, so I've never used it.
My Evo + xda Premium App = This post.
Both of the above posts are correct. Also add to them, CM7 is NOT meant for the Evo, meaning there is always bugs in it. The CM team does a great job, but there is no way to get rid of all bugs when porting a rom to many different phones. This is why there is a nightly release every night, fixing little things in each release.
sitlet said:
CM7 is NOT meant for the Evo.
Click to expand...
Click to collapse
Pretty sure Toast and Cyanogen would disagree.
What I meant was, it wasn't made for the evo. It's a port that has been coded to work, meaning there will be bugs.
Sent from my PC36100 using XDA App
sitlet said:
What I meant was, it wasn't made for the evo. It's a port that has been coded to work, meaning there will be bugs.
Click to expand...
Click to collapse
By that logic, it's not made for any device and won't work smoothly anywhere. It's AOSP, with a bunch of improvements. AOSP starts out as device independent and has to be tailored (or "ported") to any of the devices it runs on. I'm not saying there aren't bugs, but it's not that it "isn't made for it." It's just not perfected yet. It's pretty darn close though.
sitlet said:
What I meant was, it wasn't made for the evo. It's a port that has been coded to work, meaning there will be bugs.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
it's technically only 'meant' for nexus s, yet the team supports it on like 30 phones. the evo is fully functional on it, with 4g and hdmi and everything. i'd say it's pretty smoothly fit.
btw you are on pre-7.0. cm7 is now on stable version 7.0.3, with nightlys for 7.1 that only have a small mms bug (can't recieve them).

R800x data/3g stops working in cm

So I have this problem where when I am running Cyanogen Mod (currently 128 of ICS) on an R800x and the data will randomly just stop working, and the only way to fix it is to reboot the phone. Everything else appears to be working perfectly. I am running the latest firmware from that stickied thread in the developer's section. Any ideas why this is happening and how i can fix it? Btw as far as I can tell it's only the data that stops working, not sending/receiving calls/texts or wifi.
xrishox said:
So I have this problem where when I am running Cyanogen Mod (currently 128 of ICS) on an R800x and the data will randomly just stop working, and the only way to fix it is to reboot the phone. Everything else appears to be working perfectly. I am running the latest firmware from that stickied thread in the developer's section. Any ideas why this is happening and how i can fix it? Btw as far as I can tell it's only the data that stops working, not sending/receiving calls/texts or wifi.
Click to expand...
Click to collapse
Yeah, It's like that with all us cdma users. I've brought it up and fxp doesn't even acknowledge it. All you need to do is turn the mobile data off then on again. It's annoying, but until a decent dev looks into it it's the only workaround
ive tried putting it into airplane mode, and taking it back out, but that doesn't fix the problem. how do you do it?
and is there a way we can politely point this out to them, without acting completely entitled? like if its effecting all cdma users that's a pretty large group.
xrishox said:
ive tried putting it into airplane mode, and taking it back out, but that doesn't fix the problem. how do you do it?
and is there a way we can politely point this out to them, without acting completely entitled? like if its effecting all cdma users that's a pretty large group.
Click to expand...
Click to collapse
Well nobody on the fxp team has an r800x, I think two of them have gsm versions. So they can't test it out, and with my history with fxp himself he doesn't seem to really care about cdma at all (doesn't least show he does). People have mentioned it before and nothing comes from it. So it's a lack of caring about our type of issues, they don't have time, or it's beyond their comprehension. Your best bet is to mention it to Pax, since he does a lot of things for cdma. Here's a link to his profile
http://forum.xda-developers.com/member.php?u=4234200
Here is Keiran's profile also (he's on the fxp team)
http://forum.xda-developers.com/member.php?u=4344506
Oh, and the way I do it is: setttings>more..>mobile networks> Check data enabled off (wait 5sec) then check it back on. If that doesn't help then you can try a fresh install to see if it does anything
agraceful said:
Well nobody on the fxp team has an r800x, I think two of them have gsm versions. So they can't test it out, and with my history with fxp himself he doesn't seem to really care about cdma at all (doesn't least show he does). People have mentioned it before and nothing comes from it. So it's a lack of caring about our type of issues, they don't have time, or it's beyond their comprehension. Your best bet is to mention it to Pax, since he does a lot of things for cdma. Here's a link to his profile
http://forum.xda-developers.com/member.php?u=4234200
Here is Keiran's profile also (he's on the fxp team)
http://forum.xda-developers.com/member.php?u=4344506
Oh, and the way I do it is: setttings>more..>mobile networks> Check data enabled off (wait 5sec) then check it back on. If that doesn't help then you can try a fresh install to see if it does anything
Click to expand...
Click to collapse
thanks for the quick fix. worst case scenario that isn't too inconvenient of a fix. i tried sending both of them a polite message, and we'll see if anything comes of it, though probably not.
Hey,
Although I'm not on FXP team anymore (working with AOKP now <3 unicorns haha) I looked into this issue once.
Any AOSP based ROM (CM, AOKP) for zeus and zeusc use prebuilt radio interface layer libraries, which is a problem, because the ones we are using in CM9 are gingerbread, not made for ICS.
I tried reverse engineering it once but I seriously need to work more on that kinda stuff
I'll tell jerpelea (FXP) of this issue and what he wants to do about it, its not really in my power now. Although if I do find a fix then I will be sure to push it to gerrit, regardless of FXP's opinion on the issue.
J is the only one I know with an R800x (he has whole 2011 line + S + P + x10)
Hope I could be of any help,
Keiran
KeiranFTW said:
Hey,
Although I'm not on FXP team anymore (working with AOKP now <3 unicorns haha) I looked into this issue once.
Any AOSP based ROM (CM, AOKP) for zeus and zeusc use prebuilt radio interface layer libraries, which is a problem, because the ones we are using in CM9 are gingerbread, not made for ICS.
I tried reverse engineering it once but I seriously need to work more on that kinda stuff
I'll tell jerpelea (FXP) of this issue and what he wants to do about it, its not really in my power now. Although if I do find a fix then I will be sure to push it to gerrit, regardless of FXP's opinion on the issue.
J is the only one I know with an R800x (he has whole 2011 line + S + P + x10)
Hope I could be of any help,
Keiran
Click to expand...
Click to collapse
Ah ok I can see the issue now, I honestly never even considered that. I deved on gb for many years and I'm still not use to ics yet lol. I seriously thank you for responding. From what I can tell gsm users don't have this issue (maybe they do but the ones I've talked to don't) and even though it's not major to me it'd be nice to be on the same level you know? Since you're on aokp I may jump onto that soon, but thanks again Keiran, I hope you stick with developing you got a knack for it that most people don't.

[ROM][14-02-13][Flinny] Andromadus - AOSP4.2.2[9]

Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.
Reserved
Hi Flinny, great job on the AOSP builds they are running perfect. I only had one satback sins build 4. Suddenly my gallery stopt working and dropbox to. Because of the gallery problem my camera won't boot either. I flashed build 5 but I had the same problem. Build 4 was flashed with a full wipe and build 5 was flashed as update that the reason of course why the problem didn't left but sometimes it helps Does this sound familiar? Greetz Munky
I tested it last evening but have many FC message about "aosp keyboard" even with the physical keyboard
I wiped all but still the same message going back to cm10.1
Ok I'm a little rusty on the details at the moment but: AOSP means that you want it to get as close as stock experience as you can get right? (I'm really looking for a G-lite thing but then with ICS/Jelly Bean, sort of Nexus feel but then for our Desire Z)
What's everyone's opinion on these AOSP builds? To me they seem more stable and faster than CM. I kinda miss CM a little though, but not the lag.
Sent from my HTC Vision using xda app-developers app
I know that this is a dumb question and the answer is probably within the other thread, but... Ah heck, now it's just that I'm too lazy to look for the solution LOL...
But I installed AOSP 4.2 v6 last night and so far I'm not experiencing any major problems (except for FCing when I edit a picture and a bit of confusion adjusting to some new features LOL)... But when is this project going to be merged with CM? There are LOTS of creature comforts (e.g. silence during night hours, T9-style contact search, etc.) that I'm used to with the CM-optimized version that I kinda miss and only noticed that it was gone when I flashed it (I was under the impression that those features were all standard?)
Sorry to pester and thanks in advance.
EdWaRdW818:
Here you've got CM10.1 which is based on AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=2031678
Flinny:
Could you add init.d support to the rom or fix it? I see that there is a placeholder for scripts and there is one script, but it's not executed on boot (with 755 permissions).
Eddy130306 said:
What's everyone's opinion on these AOSP builds? To me they seem more stable and faster than CM. I kinda miss CM a little though, but not the lag.
Click to expand...
Click to collapse
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
google ears
EDIT: Sorry wrong thread
BTW: how can I delete my post?
I can't find changelog in your site flinny can you link it ?!
Inviato dal mio HTC Vision con Tapatalk 2
zofox said:
I can't find changelog in your site flinny can you link it ?!
Inviato dal mio HTC Vision con Tapatalk 2
Click to expand...
Click to collapse
http://andromadus.flinny.org/?q=node/2
This is absolutely the smoothest 4.0+ ROM I have ever used. Might switch to CM10.1 though for more features.
adamz667 said:
EdWaRdW818:
Here you've got CM10.1 which is based on AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=2031678
Flinny:
Could you add init.d support to the rom or fix it? I see that there is a placeholder for scripts and there is one script, but it's not executed on boot (with 755 permissions).
Click to expand...
Click to collapse
catachresistant said:
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
Click to expand...
Click to collapse
Oh jeez... Either I had a total brain fart and completely missed the link or it got posted anywhere from the time I posted it to the catching up of 14+ hours of sleep (I only slept 7 hours across 3 days LOL), but I guess CM10.1 is already posted. I'll download it and see what's up. Thanks for not flaming me guys. I would've gotten the N4 but I'm not a big fan of LG (had countless bad hardware experiences) and my phone is somewhat last on my "to upgrade list", so thanks for everybody's help and keep up the good work! There's some top quality Münchner Bier mit your name on it once I get some disposable income
catachresistant said:
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
Click to expand...
Click to collapse
No I have not.
Sent from my HTC Vision using xda app-developers app
---------- Post added at 02:11 PM ---------- Previous post was at 02:00 PM ----------
LAMER_CZ
That is strange. Which recovery are you using? Don't use clockworkmod as they're always full of glitches and bugs. Don't use ROM Manager to flash ROMs either as they as well have glitches. I recommend doing everything in recovery. If you do have clockworkmod I recommend flashing 4ext as it has more features and can make your phone a little faster
Sent from my HTC Vision using xda app-developers app
Ok I just went ahead and installed it. This is exactly what I need for a ROM on my Desire Z! Thanks Flinny, and keep up the good work!
Now my experience with this ROM:
- I just fly trough my home screens and menu's, it runs fluently!
- When at stock speeds (so 1Ghz) I sometime run into problems booting up the settings. I just hangs there for 4+ seconds untill it actually shows the settings. Setting clockspeeds to 1,8Ghz fixes this most of the times, but it's something you might want to look into (Or don't, it's your ROM)
- The above also happens with some apps.
I don't run swap or any other optimization, so I don't know if it's my problem or a ROM problem, but if you want me to do some more testing just tell me what I need to do
Boot Loop
Thanks for the work, this is a great ROM, just thought I would pitch my issue I had.
Im currently testing an app and set the device to use 2g only as I wanted so see how quickly it pulled in my data on a slower connection. If you leave it in 2g mode and reboot it appears to get stuck in a boot loop.
Hope this is helpful.
Cheers
usc911 said:
Thanks for the work, this is a great ROM, just thought I would pitch my issue I had.
Im currently testing an app and set the device to use 2g only as I wanted so see how quickly it pulled in my data on a slower connection. If you leave it in 2g mode and reboot it appears to get stuck in a boot loop.
Hope this is helpful.
Cheers
Click to expand...
Click to collapse
I doubt that has anything to do with the "2g" setting since the radio doesn't come on until after it is booted up. Maybe that application you're testing screwed something up?
Authorita said:
I doubt that has anything to do with the "2g" setting since the radio doesn't come on until after it is booted up. Maybe that application you're testing screwed something up?
Click to expand...
Click to collapse
The app is fine, I have been building it for a few weeks and runds fine on a nexus one, and a sapphire. I have tried flashing the 4.2.1 AOSP build and the CM10 build and exactly the same is happening.
Guess I'm just missing something :s
usc911 said:
The app is fine, I have been building it for a few weeks and runds fine on a nexus one, and a sapphire. I have tried flashing the 4.2.1 AOSP build and the CM10 build and exactly the same is happening.
Guess I'm just missing something :s
Click to expand...
Click to collapse
Do you think you could get a log of the reboot? Might help in figuring out why it is rebooting like that.

[Q] Current fastest/most stable ROM?

Just a quick question for everybody! I've been using Liquid Nitro for a while now, but I'm getting a bit frustrated with the occasional spontaneous resets, and how slow it is. What does everyone here use, and what do you think is the best in terms of stability and speed?
Currently I am using sphinx rom. It is snappy ,good on battery, jelly bean. Be sure to apply both patches. I have found the kitkat to be unstable.
Sent from my LG
notzippy said:
Currently I am using sphinx rom. It is snappy ,good on battery, jelly bean. Be sure to apply both patches. I have found the kitkat to be unstable.
Click to expand...
Click to collapse
You have an LG P930, right? is it this one?
i also use liquid nitro, and tried most other jb,kk roms, but always back to liquid for its stable.
the next stable rom for *my* p930 is cm 10.1.3.
Sent from my LG-P930 using xda app-developers app
I used the version in this thread
http://forum.xda-developers.com/showthread.php?t=2294709
Sent from my LG-LU6200
notzippy said:
I used the version in this thread
http://forum.xda-developers.com/showthread.php?t=2294709
Click to expand...
Click to collapse
So it's fast, and works with my p930. Is it stable for you (no random restarts?)
It is better then CM, but it still has random reboots. I did not find the reboots to occur as frequently as CM
Nz
So far, after changing the default language from Russian, I am finding Sphinx to be a lot faster and smoother than liquid nitro, though that might be because I don't have all my apps loaded yet. I also just experienced my first random reset (not even 6 hours! not looking good,) which put my phone into a boot loop (it gets to the lock screen, give a "system UI has crashed" error, and reboots,) that I fixed by pulling the battery.
AND SPEAKING OF THE BATTERY my phone now thinks my battery is at ~ %1-%5 power (it was at about %60 when I installed the ROM,) and is constantly telling me to plug it in, and the phone refuses to charge (it won't charge with any cable or wall adapter I have, and won't even recognize when I plug it into a computer.)
In short: lots of problems, but if I can fix them, I will probably keep sphinx.
*Edit: I just went and wiped everything (including battery information) in CWM and installed the "official unofficial" ROM from the same post. It seems so far to be decent (and it's charging the battery!) It's a bit laggy (like the stock ROM, but not as bad a Liquid Nitro got for me.) Tomorrow I will do the full data wipe again (including the battery info) and re-install sphinx to see if it helps.
In my P930, I use the last PAC-ROM, it gets me stability, battery friendly, smooth, it doest get lagged.
It's fully customizable, I recommend it.
The last version I installed is the nightly of 2014-03-28 or so.
[emoji41]
Send from my SGH-I337M using Tapatalk.
Don't forget to install both patches for sphinx.
Sent from my Nexus 7 using XDA Premium HD app
---------- Post added at 04:30 AM ---------- Previous post was at 04:29 AM ----------
Also you should never need to yank battery, just unplug USB then hold Power down for 20 seconds.
Sent from my Nexus 7 using XDA Premium HD app
I'm looking at the Pac ROM releases, but I'm not sure which one to download (I'm not going to do nightly releases.)
keboose said:
I'm looking at the Pac ROM releases, but I'm not sure which one to download (I'm not going to do nightly releases.)
Click to expand...
Click to collapse
Why dont you try the RC1?
because there are two labeled RC1?
Not the Milestone, but the pac-p930-22.2.0-rc1.zip
Send from my SGH-I337M using Tapatalk.
ultimate_neet said:
Not the Milestone, but the pac-p930-22.2.0-rc1.zip
Click to expand...
Click to collapse
Well, it's going (somewhat) well. With the stable release, I haven't had to restart yet, but there are still problems: mainly that the home button doesn't work. along with that, the "cLock" app keeps crashing, and gapps looks like it wasn't installed properly (no gapps except gmail are there, and it doesn't work.) Did you experience any of this with the nightly build you use?
I made doubly sure I installed the correct gapps zip, could it be I have an old version of CWM that's messing it up? I have CWM v6.0.1.5
Installl the gapps core only.
I didn't have any problems with the clock.
You did full swipe?
Send from my SGH-I337M using Tapatalk.
gapps core? I installed the gapps they linked to in the official thread.
I followed their instructions as well: factory reset, flash ROM, flash gapps, reboot.
Never mind! I installed the nightly you said you use (03/29/2014) and it works! I'm loving kitkat. It's being a bit slow right now, but I'm hoping that's because the phone's been downloading the files for GTA 3 since I installed the ROM (and linked my google account) earlier today.
hey, I don't know what is going on, but I'm not finding any of these ROM's to be stable at all. They seem to work alright at first, but once I get my apps back, it all goes down the tubes. Even the Pac ROM, which so far has been the MOST stable, is frustrating to use. I found that my music player (PowerAmp) causes it to be a bit more unstable, but both it and the default music player often crash 'android.process.media' and then I have to reboot my phone.
Along with that, randomly, and frequently, when I try to wake my phone up from sleeping with the power button, the screen will just go black, the buttons will stop responding, and I have to pull the battery. This one is particularly frustrating because this morning my phone tried to turn on the screen to play an alarm and the phone locked up!
I've wiped my phone again and haven't installed any apps. Let's see if the problems still happen.
keboose said:
hey, I don't know what is going on, but I'm not finding any of these ROM's to be stable at all....
Click to expand...
Click to collapse
I've had this phone since it came out. From my experience, ICS ROM's are the most stable, followed by JB ROMS, then KitKat ROMs. If you want the best stability, battery, and for daily use go with either stock ICS or one that's based on stock. The only problem with that is that you miss out on any of the new improvements in JB and KitKat. For daily use, non of the KitKat ROMs are stable enough. Currently, I'm running CM 10.1.3 with Wind Kernel 2.6. It's not as stable as ICS stock. I get random locks/restarts about once or twice a week. It does however offer the best compromise in stability and features/improvement over just running ICS ROMs. Specwise, this phone was ahead of the curve when it came out. But battery and performance issues kept this from being a good phone. Because it's not well used, there's very little support and development for this phone.

Categories

Resources