Develop Bugs

CM7 and battery

Hi,
I find battery usage a bit high on CM 7(RC1 and nighly).
Batter Montor widget or CurrentWidget shows values from 6-12 mAh.
With same radio i have 3-5 mA when using default HTC Sense ROM.
I did full wipe factory reset, dalvik, cache etc..
I need some tips how to diagnose the problem and eventually file a bug report.
I am using lates radio 32.54.00.32U_5.14.05.17, but the problem is the same with older one 32.49.00.32U_5.11.05.27
I don't think the problem is with the radio itself, because it will be problematic with all ROMs (?)

You do realise that you can post in the CM7 thread. You also realise that RC and nightly builds arn't stable releases?

You also realise that RC and nightly builds arn't stable releases?
Click to expand...
Click to collapse
ofc i know that . I also know that if it is a bug, someone will have to report it. That's the goal of RC after all . May be you should read the whole post after all.

I seem to be having a similar experience with oxygen rom so would be interested in investigating what is causing this. Tried looking at all the usual stuff in QSI to weed out programs that may be causing this problem but nothing jumps out at me. Plus, i'm having the problem with completely clean rom without any apps installed.
j0r01 said:
ofc i know that . I also know that if it is a bug, someone will have to report it. That's the goal of RC after all . May be you should read the whole post after all.
Click to expand...
Click to collapse
Don't think that sort of response if going to help your cause tbh

I also know that if it is a bug, someone will have to report it. That's the goal of RC after all . May be you should read the whole post after all.

p5x said:
I seem to be having a similar experience with oxygen rom so would be interested in investigating what is causing this. Tried looking at all the usual stuff in QSI to weed out programs that may be causing this problem but nothing jumps out at me. Plus, i'm having the problem with completely clean rom without any apps installed.
Don't think that sort of response if going to help your cause tbh
Click to expand...
Click to collapse
same here. battery just runs dry very fast! (after playing a song on youtube, battery goes down for about 6%)

Try a different kernel. I recommend ManU kernel (the CFS-HAVS-AXI-version).

Same comments in spanish forum:
http://www.htcmania.com/showthread.php?t=303281&page=21#402
This guy is recommending aEVViollet (..35) kernell.
I'm thinking about changing into Oxygen.
Best regards

It is getting better, isn't it?

[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).

[Q] At 11:45pm New Years Eve my CM7 Incredible went haywire....need help!

So strangely at 11:45pm last night my phone went absolutely nutty... Can't figure it out but all of my apps keep crashing. Gmail, Maps, etc.
I haven't updated CM7 since it came out months ago so I need a bit of help upgrading all of what needs to be done... I figure this is a good reason to bring things up to speed.
Ideally I'd like to get 7.1 on here. I also can't remember all of what I need to download to do this process. Not as brilliant as the rest of you!
Can anyone give me (or point me in the direction of) some step by step instructions of what I need to do? Real layman's terms...
Currently:
Android 2.3.3
Model number ADR6300
Kernel 2.6.37.6-incredikernel-gb-04192011+
CyanogenMod 7.0.0-Inc
Build Number GRI40
Help me get this puppy up and running!
Thanks all and Happy New Year!!!

Go to cyanogenmod.com and click on devices. Scroll down until you see the HTC Droid Incredible and click on it. Click on the wiki link. Everything you need to know will be there. Use the via clockworkmod recovery method.

Get 7.1 stable, the gapps for it, incredikernel ext4 and the adrenaline shot. That's should be good.
-My life is a shooting range, people never change-

I hate bad mouthing projects that people have worked so hard on. But, CM 7.x stable is NOT stable on the Dinc.
If you want to keep using CM 7.x (stable)...
expect this problem to keep happening. If you are a CM 7.x (stable) user and it hasn't happened to you yet, great. But, don't be surprised when it does. Yeah, check out the CM forum for 7.x stable on the Dinc... you will find many others who have the same problem (works great for some amount of time, and then constant FC's and freezes). I also just ran across another person in the Incredible discussion forum who had the same thing a few days ago. It happened to me after about a week on installing CM 7.1 stable, so I changed to Inc Deck (gingerbread) 1.3 stable. You can reinstall CM and it and it will work for some amount of time (completely unpredictable how long it will work). But someday, sometime...whammo... you will have useless phone, and you will need to reinstall again.
Some folks have said that the problem never goes away after a fresh install... I don't know about that. My phone screwed up, I searched and found many others with the problem, tried a quick fix, then abandoned CM 7.x stable immediately.

iowabeakster said:
I hate bad mouthing projects that people have worked so hard on. But, CM 7.x stable is NOT stable on the Dinc.
If you want to keep using CM 7.x (stable)...
expect this problem to keep happening. If you are a CM 7.x (stable) user and it hasn't happened to you yet, great. But, don't be surprised when it does. Yeah, check out the CM forum for 7.x stable on the Dinc... you will find many others who have the same problem (works great for some amount of time, and then is completely fubar'd). I also just ran across another person in the Incredible discussion forum who had the same thing a few days ago. It happened to me after about a week on installing CM 7.1 stable, so I changed to Inc Deck (gingerbread) 1.3 stable. You can reinstall CM and it and it will work for some amount of time (completely unpredictable how long it will work). But someday, sometime...whammo... you will have useless phone, and you will need to start over again.
Click to expand...
Click to collapse
Hmmm interesting. Out of all the roms I have tried for the droid Incredible, CM7 has by far been the most stable. Never had any trouble with it and I have, at times, used it for months before trying a different rom.

Oh I know! It seems to catch everyone off guard because it works fine for X number of weeks or months and then... FC and freeze hell!
A lot of the folks found it happened shortly after upgrading from 7.0 to 7.1. But just in the last couple of days I have run across a couple of people that were still using 7.0 and now seem to have the issue.
The guy at CM who does most everything for the Dinc seems to think it was related to a full /data/data partition. I reinstalled fresh and did the ext4 "no data limit" mod, after first having the issue, and it made no difference at all. So, I gave up on CM the same day.

CM7 nightlies have actually been my daily driver for most of my time having service on the Incredible.
I've heard the force close issues have been due to /data/data filling up. If you keep 20MB free or more you should be fine. Root explorer is one app that will list how much free is on /data/data and a recommended app for any rooted phone. the CM7 nigthly thread has a few suggestions on how to free space. Search not enough space on the nightlies thread.
Edit: I see you posted about the /data/data partition already.

Thanks for this tidbit... I haven't had the issue, nor do i plan on getting it.. I'm pretty adamant about keeping a certain percentage of free space on all partitions, so hopefully everything runs smooth.
Thanks again for the heads up.
tiny4579 said:
CM7 nightlies have actually been my daily driver for most of my time having service on the Incredible.
I've heard the force close issues have been due to /data/data filling up. If you keep 20MB free or more you should be fine. Root explorer is one app that will list how much free is on /data/data and a recommended app for any rooted phone. the CM7 nigthly thread has a few suggestions on how to free space. Search not enough space on the nightlies thread.
Edit: I see you posted about the /data/data partition already.
Click to expand...
Click to collapse
Sent from my VS910 4G using XDA App

iowabeakster said:
Oh I know! It seems to catch everyone off guard because it works fine for X number of weeks or months and then... FC and freeze hell!
A lot of the folks found it happened shortly after upgrading from 7.0 to 7.1. But just in the last couple of days I have run across a couple of people that were still using 7.0 and now seem to have the issue.
The guy at CM who does most everything for the Dinc seems to think it was related to a full /data/data partition. I reinstalled fresh and did the ext4 "no data limit" mod, after first having the issue, and it made no difference at all. So, I gave up on CM the same day.
Click to expand...
Click to collapse
Don't let this Guy talk you out of cm7. I've been running the same kang for almost a month. And I ran the stable from October 9th til December 19th. It was always my fallback. I've never had issues, and as big as the nightlies/stable threads are. Why would you let one sway you?
-My life is a shooting range, people never change-

Correct, don't let one guy do that.
Certainly don't allow your own haywire experience affect your judgment.
And certainly don't allow these dozens of folks who posted on the CM incredible forum to have any influence on your decision.
http://forum.cyanogenmod.com/topic/32784-consistent-freezingfc-after-update-to-71/
Only listen to one guy who is running some OTHER build, that everything is perfect.

Your sarcasm is too advanced, my friend... ;] lol
iowabeakster said:
Correct, don't let one guy do that.
Certainly don't allow your own haywire experience affect your judgment.
And certainly don't allow these dozens of folks who posted on the CM incredible forum to have any influence on your decision.
http://forum.cyanogenmod.com/topic/32784-consistent-freezingfc-after-update-to-71/
Only listen to one guy who is running some OTHER build, that everything is perfect.
Click to expand...
Click to collapse
Sent from my ADR6300 using XDA App

Use Pons 7.2 kang. I've been since he started and all is well. I was running the nightlies before that and have never had any issues.

Ahhhhhhh
Sent from my HTC Incredible S

[Q] Hi! T-mobile GS III Question

i am a super omega ultimate noob lv. -99. i am wondering how to check on the latest status of the GSIII stable roms. i would like to know if/when CM will get the roms first or if xda gets them first. i like stable roms because i am a noob. my noobness knows no bounds. please help. i do dontate. thank you.

Right now, CM10 nightly 25 is working great
26 has exhibited a few irritating bugs but I haven't had any problems with nightly 25
Give it a run, it's phenomenal IMO

o-k said:
i am a super omega ultimate noob lv. -99. i am wondering how to check on the latest status of the GSIII stable roms. i would like to know if/when CM will get the roms first or if xda gets them first. i like stable roms because i am a noob. my noobness knows no bounds. please help. i do dontate. thank you.
Click to expand...
Click to collapse
Xda is just an outlet where people choose to post roms.
To check on the latest status of roms, you need to open the threads and read the OP. You also need to spend at least ten minutes reading each thread, That will tell you how stable each rom is and what kind of results people are having.
Sent from my SGH-T999 using xda premium

Is there a place for specific roms that we can see a list of all known bugs? I've been trying to check on, for example, CM10, paranoid android, and AOKP in particular and havent been able to find any bug trackers at all. Without knowing what bugs there are and what will/wont affect me, I'm too hesitant to try any of the roms and have been suffering through t-mobile's dual "update ready" and "update needed" constant un-clearable notifications. I cant even apply the stock updates because I debloated and applying the update fails because I dont have the apps that the update is attempting to update. Updating would involve doing a full factory reset back to stock and THEN updating, which means i'm probably better off simply waiting for samsung's official JB update to roll out in the first place

shrimants said:
Is there a place for specific roms that we can see a list of all known bugs? I've been trying to check on, for example, CM10, paranoid android, and AOKP in particular and havent been able to find any bug trackers at all. Without knowing what bugs there are and what will/wont affect me, I'm too hesitant to try any of the roms and have been suffering through t-mobile's dual "update ready" and "update needed" constant un-clearable notifications. I cant even apply the stock updates because I debloated and applying the update fails because I dont have the apps that the update is attempting to update. Updating would involve doing a full factory reset back to stock and THEN updating, which means i'm probably better off simply waiting for samsung's official JB update to roll out in the first place
Click to expand...
Click to collapse
Actually that would be a great idea. It would help out the entire community.
Right now the way things exist, you pretty much have to read through an entire rom thread to determine the benefits/bugs of any given rom.
You could, for example, start a list for any particular rom.. read the entire thread, then make your own thread detailing current known bugs and post it in the same forum. Then the OP of the rom thread could post your link in the first post making it easy for everyone to find.
That would serve two purposes - you would learn the information you're seeking and also become an instantly appreciated contributor to the site.
Sent from my SGH-T999 using xda premium

I'm surprised the rom developers dont already have a system in place, though. The scope of the projects are presumably gargantuan collaborative works. i kind of assumed that they must have some sort of a bug tracking thing that they use between them. That bug tracking thing is what i've been venturing to find. There are a ton of user-specific bugs that I have no problem digging through the forums and figuring out myself, but what i'd love to see with roms is a list of "this is what we know isnt working yet. dont talk to us about this. we are working on it." or at the very least, "when you flash this rom, if you would like to help, run this command and upload the output HERE so we can fix some bugs we know about".
I'm coming from a linux world and it is very disconcerting to me to flash a rom, encounter a bug/error, and not be able to look at any sort of an error message or do anything to fix the problem except reboot/wipe/reflash and hope for the best. thats a very windows-y mentality to the whole thing, and i feel like if we're running linux on the phones we should be able to get a bit more involved in fixing our own problems a bit better too.
I guess what i'm trying to say is, i'd like to help and i have no clue where to even begin. with archlinux theres a beginners guide but with these roms its more of a "watch this youtube video and follow this tutorial but god help you if anyone thinks you are complaining about what people are doing for you for FREE".
EDIT: I found CM10's issue tracker, but there isnt anything specific for the GS3 there. The flicker and picasa sync issues arent even mentioned. Obviously Paranoid Android and Kang will have the same bugs as CM10, but im assuming that they'll have their own bugs introduced after they add in their own features and such.

ok.
ingenious247 said:
Right now, CM10 nightly 25 is working great
26 has exhibited a few irritating bugs but I haven't had any problems with nightly 25
Give it a run, it's phenomenal IMO
Click to expand...
Click to collapse
thanks! will it be on the CM website or here?

o-k said:
thanks! will it be on the CM website or here?
Click to expand...
Click to collapse
Two things - one, if you're going to do a lot of flashing, and especially with CM10, you will want to install ROM Manager from the Google Play Store. It will make managing your updates/downloads easier
Two, there is a dedicated thread to CM10 in the "T-Mobile Galaxy S III Original Android Development" forum here:
http://forum.xda-developers.com/showthread.php?t=1778217
Read a lot first - before you do anything.. unless you are a very experienced user.
If you have specific questions I will be happy to help

i have a question
ingenious247 said:
Two things - one, if you're going to do a lot of flashing, and especially with CM10, you will want to install ROM Manager from the Google Play Store. It will make managing your updates/downloads easier
Two, there is a dedicated thread to CM10 in the "T-Mobile Galaxy S III Original Android Development" forum here:
http://forum.xda-developers.com/showthread.php?t=1778217
Read a lot first - before you do anything.. unless you are a very experienced user.
If you have specific questions I will be happy to help
Click to expand...
Click to collapse
i've downloaded the CWM pro and the TB pro. i was wondering what exact ROMS i can use. There is also the difficulty of understanding which rom is exactly which. Is there a way to view the Change log? i'm a super noob. i'm really sorry.

Changelogs won't do you much good.
I recommend flashing everything through CWM (make sure you have 6.0.1.2 Touch - in my signature if not). I wouldn't use ROM Manager at all. Having automated tools is great, but learning how to do it yourself is even better. Plus, if you break something, knowning what you are doing makes it easier to fix. Automated tools hurt more than they help.
As for roms, your options pretty much are as follows:
CyanogenMod: AOSP, the closest thing we have to the stock Google firmware.
AOKP: Pretty much CyanogenMod with some extra options. Nothing extraordinary about those extra options, just some nice things like center clock, swagger toggles, and unicorns.
MIUI: iPhone look for Android.
ParanoidAndroid: Scalable - for tablets (imo).
Then you have the neverending amount of customized stock (TouchWiz) roms.
They are all under constant development. If you want "stable", stay on your stock firmware. All of the roms listed above are stable enough to use as a daily driver. They all have threads in the two Dev forums. But if you don't know what to pick, use CyanogenMod.

I still think ROM Manager is a great tool, it's how I started years ago and I still managed to learn what I needed to over time flashing manually
Sent from my SGH-T999 using xda premium

[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.