Develop Bugs

Combining FRX03 with Neopeek FRG83.R5 with working Bluetooth ?

Dear Reefermattness and arrrghhh !
I apologize for making a new thread but I just want have your attention on the Neopeek Release for Rhodium.
In this forum stays that in FRG83.R5 release
http://www.neopeek.com/en/forum/Android-ROMs/2183-ROM-FRG83-Build-Froyo221-05-11-2010
Bluetooth IS WORKING !
I have no idea what this release can, but I saw its structure. Basically EXT2 Partition for Neopeek is the same thing that system.ext2 file for FRX03 !
And in andoidinstall.tar.gz file is the same stuff as in system.ext2 and roofts.img together.
Why we just not pick the working Bluetooth "driver-package-what-ever" from Neopeek and combine it with FRX03 ? I could do it by my self, but I don't have deep system structure know-how.
I must say that FRX03 is lot easier to handle (getting ready, install, edit etc) thats why I'd prefer working with it as with Neopeek.
And besides I just reached almost 8 hrs of working time with one charge on it with new kernel and startup change. Thats why I want to improve it. Can you help me to understand the structure of driver packages for BT ?
Thank you
-------------------------------------
----------------
EDIT:
Here it is, a repack of SuperFroyo in system.ext2 file.
http://narod.ru/disk/27385762000/system.zip.html
I didn't test it yet. But if some one want to try out - please download and report back !

d0nate110 said:
Dear Reefermattness and arrrghhh !
I apologize for making a new thread but I just want have your attention on the Neopeek Release for Rhodium.
In this forum stays that in FRG83.R5 release
http://www.neopeek.com/en/forum/Android-ROMs/2183-ROM-FRG83-Build-Froyo221-05-11-2010
Bluetooth IS WORKING !
I have no idea what this release can, but I saw its structure. Basically EXT2 Partition for Neopeek is the same thing that system.ext2 file for FRX03 !
And in andoidinstall.tar.gz file is the same stuff as in system.ext2 and roofts.img together.
Why we just not pick the working Bluetooth "driver-package-what-ever" from Neopeek and combine it with FRX03 ? I could do it by my self, but I don't have deep system structure know-how.
I must say that FRX03 is lot easier to handle (getting ready, install, edit etc) thats why I'd prefer working with it as with Neopeek.
And besides I just reached almost 8 hrs of working time with one charge on it with new kernel and startup change. Thats why I want to improve it. Can you help me to understand the structure of driver packages for BT ?
Thank you
Click to expand...
Click to collapse
1) as far as I understand Neopeek uses large parts of Xdandroid projects, starting from the kernels/rootfs. This is not hidden/secret, so he and xda devs may know each other pretty well.
Therefore I can't understand how he can have bluetooth working and Xdandroid not.
then ...
2) maybe he shares branches of code and patches with our devs, but while our devs decided that the code to make bluetooth working is still too buggy, he could have decided to shoot it in for good. In fact reading comments on the thread you posted you will see that at the end the people crying for not-working BT are a lot ...

I'd be interested to see if BT works fully. I've seen some where they scream that BT works, but then when they actually try to use BT... it fails. So if it pairs and nothing else, that's what state our build is in as well.

I just installed it, on a blank 2Gb I had spare.
At start it's quite a pain in the arse ...
cmdline was a little different, I just set correct keyboard.
But I immediately put the latest kernel (24.11.2010). Both in installer and main.
Much faster than Xdandroid. Much faster at boot, much snappier in launcher etc., but this may be related also to the age (of the FAT32 file system) of the other SD I use for Xdandroid. Will format it and see what happens swapping.
But then, when it went to sleep it just crashed.
I tampered with the startup, added pmsleepmode=2, this worked, tried =1 and works quite well.
As I expected, BT doesn't work on my RHOD100.
This neopeek build comes nearly all from xdandroid, so it seems it's not as up to date.
But while that guy takes most of development from XDA, he must work a lot on tweaks, therefore XDA should take something back ...
I'll try cleaning the other SD and check what happens.

Installed on extra card. Rhodium 400 . It is fast. Boots quicker. The initial setup screens are very friendly. Power off and other buttons work more like winmo. Bluetooth will not turn on. Phone works. Data does not work. Have to use WiFi for data. USB while in Android does work (sweet). Key board backlighting not working. I am going to reinstall with bluetooth enabled initially in winmo.

Neopeek SuperFroyo Repack into system.ext2
arrrghhh said:
I'd be interested to see if BT works fully. I've seen some where they scream that BT works, but then when they actually try to use BT... it fails. So if it pairs and nothing else, that's what state our build is in as well.
Click to expand...
Click to collapse
Here it is, a repack of SuperFroyo in system.ext2 file.
http://narod.ru/disk/27385762000/system.zip.html
I didn't test it yet. But if some one want to try out - please download and report back !

reinstalled Bluetooth not working. Rhodium 400
Only things that could make improvements to XDA android are Speaker phone is working. USB in android does work. Buttons function as they should. It works with SIM card installed. Speed. Boots faster. Screen adjusts to right profile on start lockscreen.USB headset works without line in startup.
Still not working
Data does work but have to manually set APN. Headset does not work ( Does work with line in Startup and calling during boot). Problems with the market downloading.
Does work tethering. pretty much everything
One nice thing is they have a seperate install folder so if your system is corrupted you just reinstall with file manager in winmo. It reformats the ext2 partition on the card. I assume the sizing of partition is in place of the sizing the data.img file on the card.
Being open source borrowing a few items should not be considered crossing a line.

d0nate110 said:
Here it is, a repack of SuperFroyo in system.ext2 file.
http://narod.ru/disk/27385762000/system.zip.html
I didn't test it yet. But if some one want to try out - please download and report back !
Click to expand...
Click to collapse
wait a minute.. you didnt test it and are spreading it like wild fire ?
before you cry wolf, at least pretend you saw one ..

First Full Day Of Testing
[ACL] said:
wait a minute.. you didnt test it and are spreading it like wild fire ?
before you cry wolf, at least pretend you saw one ..
Click to expand...
Click to collapse
I've tested this strange build a whole day today... I must say...I'm confused...
First of all I charged my battery to full 100% in WinMo. Then I've just replaced old system.ext2 with this one (my other files incl. kernel were untouched) and booted a clean Haret and saw, that this Android Learning Demo just didn't want to go on if I taped on it...
My device was locked and I must reboot it...then I delete my data.img file and tried again... success - SuperFroyo booted well.
- Bluetooth doesn't work as pessimistically expected
Other stuff works same like in our Froyo Reference.
- flash 10.1, loudspeaker, camera, usb connection and headphones don't work
- sleep_mode=1, wifi, phone, wake up on call and Market are working.
But Battery life was little better according to JuicePlotter... and I had a feeling, that all the system works little bit faster... I don't know if it is just placebo effect, but I thing its true...
I'll keep testing it for another 3-5 days and report back... and BTW you can test it too.

d0nate110 said:
I've tested this strange build a whole day today... I must say...I'm confused...
First of all I charged my battery to full 100% in WinMo. Then I've just replaced old system.ext2 with this one (my other files incl. kernel were untouched) and booted a clean Haret and saw, that this Android Learning Demo just didn't want to go on if I taped on it...
My device was locked and I must reboot it...then I delete my data.img file and tried again... success - SuperFroyo booted well.
- Bluetooth doesn't work as pessimistically expected
Other stuff works same like in our Froyo Reference.
- flash 10.1, loudspeaker, camera, usb connection and headphones don't work
- sleep_mode=1, wifi, phone, wake up on call and Market are working.
But Battery life was little better according to JuicePlotter... and I had a feeling, that all the system works little bit faster... I don't know if it is just placebo effect, but I thing its true...
I'll keep testing it for another 3-5 days and report back... and BTW you can test it too.
Click to expand...
Click to collapse
I'm on nand, so i cant run that abomination. However i did run the real cyanogen and it was a lil faster. But it took too many changes to the rootfs to get it to run.. i havent tried it since..
Also im not sure why neopeek isnt using our rootfs structure so you can swap the system.imgs easier .. maybe you should ask him

too buggy things would work then stop working. I could plug in a usb headset have it work in a call or music unplug it then plug it back in and it does not work. Many other things like that. Same with the 3.5 jack trick it would work sometimes then sometimes not. If u left it stock it works great and is very fast. Diamond users were happy. I have a diamond that I will try it on sometime next week, but it is not good for rhodium. It did something to the usb on my Rhodium in winmo would not work so gave me a chance to jack in energy rom like that so far.

[ACL] said:
I'm on nand, so i cant run that abomination. However i did run the real cyanogen and it was a lil faster. But it took too many changes to the rootfs to get it to run.. i havent tried it since..
Also im not sure why neopeek isnt using our rootfs structure so you can swap the system.imgs easier .. maybe you should ask him
Click to expand...
Click to collapse
Sorry for silly question, but what do you mean with "being on nand"?
And, lol, why abomination!?!?!?
It's clearly taken from FRX02 Xdandroid build, but tweaked to be more speedy.
These tweaks are something that Xdandroid should port back to main project.
I have only one crash a day with Neopeek's FRG83.R5, while Xdandroid FRX03 is not only slower on my TP2 rhod100, even with around 100Mb ram free, but keeps slowing down even more while using, so that I have to restart.
In the last week this led to process ".acore" crashing almost immediately after boot, with no solution known to me except reinstalling.
That's once a day.
Neopeek did this only once.
Still have to understand what leads to ".acore" process chain crashes.
I would prefer to use Xdandroid FRX03, because it's more up to date and standard compliant, but, strangely, it's not as stable as Neopeek's FRG83, on my phone.
Cheers.
EDIT:
uh, oh, d0nate, I think we are messing it a little bit here. I am testing FRG83.R5, not SuperFroyo.
They are 2 different builds.
What are you effectively testing?

Sorry about that
sad0felix said:
EDIT:
uh, oh, d0nate, I think we are messing it a little bit here. I am testing FRG83.R5, not SuperFroyo.
They are 2 different builds.
What are you effectively testing?
Click to expand...
Click to collapse
First of all I AM NOT Donate - I'm donatello written with numbers
I don't want any donations and hate money
Second I apologize, but I can't implement FRG83.R5 to use without formating my SD-card thats why I use a SuperFroyo. The member DmK75 gave me this link to system.ext2 file with SuperFroyo release in it...
I try though to repack FRG83.R5 also in system.ext2 file later... I just don't have the know-how yet...

sad0felix said:
Sorry for silly question, but what do you mean with "being on nand"?
And, lol, why abomination!?!?!?
It's clearly taken from FRX02 Xdandroid build, but tweaked to be more speedy.
These tweaks are something that Xdandroid should port back to main project.
I have only one crash a day with Neopeek's FRG83.R5, while Xdandroid FRX03 is not only slower on my TP2 rhod100, even with around 100Mb ram free, but keeps slowing down even more while using, so that I have to restart.
In the last week this led to process ".acore" crashing almost immediately after boot, with no solution known to me except reinstalling.
That's once a day.
Neopeek did this only once.
Still have to understand what leads to ".acore" process chain crashes.
I would prefer to use Xdandroid FRX03, because it's more up to date and standard compliant, but, strangely, it's not as stable as Neopeek's FRG83, on my phone.
Cheers.
EDIT:
uh, oh, d0nate, I think we are messing it a little bit here. I am testing FRG83.R5, not SuperFroyo.
They are 2 different builds.
What are you effectively testing?
Click to expand...
Click to collapse
Ahh you poor soul.. nand meaning i no longer have wince so i cant run his installer. Abomination is a strong word.. so i take it back . But i do think it's wicked and it's not a child of xdandroid like you think. The main chunk of the project comes from cyanogen. The only parts that were pillaged from xdandroid appear to be some of the roofs files (including the hardware libs). And of course, our kernel runs the whole show.
Now why would i run some hacked up version if i can run cyanogen directly? Plus cyanogen has everything open, so we can easy work and modify it as we need. I have not seen anything shared by neopeek, so i dont feel its fair to the xdandroid team since we pretty much share everything.
If it's stable for you.. awesome.. maybe there is future for it.

[ACL] said:
Ahh you poor soul.. nand meaning i no longer have wince so i cant run his installer. Abomination is a strong word.. so i take it back . But i do think it's wicked and it's not a child of xdandroid like you think. The main chunk of the project comes from cyanogen. The only parts that were pillaged from xdandroid appear to be some of the roofs files (including the hardware libs). And of course, our kernel runs the whole show.
Now why would i run some hacked up version if i can run cyanogen directly? Plus cyanogen has everything open, so we can easy work and modify it as we need. I have not seen anything shared by neopeek, so i dont feel its fair to the xdandroid team since we pretty much share everything.
If it's stable for you.. awesome.. maybe there is future for it.
Click to expand...
Click to collapse
Woah ... I am feeling soooo noob ... dang you!!!
Since I wrote my previous post my knowledge grew about ten times ... from 0.001% to 0.01%, so now I can see what you mean about Cyanogen and all the rest.
I know it's everything but a good excuse, but please notice that I got to Android just in the form of Xdandroid, and only in the last few weeks.
So I am learning. Maybe faster than mean people, still much slower than hardcores like you or the other devs.
----------------
In the meanwhile I reverted back to FRX03.
Mainly because of stabilities (better, instabilities are regular so that can be forecasted and behaviors provoking them can be avoided with good success rate).
Still I think that maybe (and I cap it, MAYBE) Xdandroid could (I don't say should, it would be excessive) benefit from the Neopeek/Cyanogen "thing".
You know, like when you have a crate of stuff, you dive hands in it and choose and pick up just the good things/those you like.
I just dream a Xdandroid snappy like Neopeek's whatever build (I tried 2).
... the speed ... the speed .... (put here Marlon Brando's voice in Platoon, when he repeats "the horror" ... ).
Cheers!
EDIT:
I fear that you did it all by yourself, but in any case I ask you.
Is there any public documentation about going nand? What are the advantages?
You put a thermite in my left ear, you know?!?!?!

Here's the PPCG thread on NAND boot testing. Not for the faint of heart...

sad0felix said:
Woah ... I am feeling soooo noob ... dang you!!!
Since I wrote my previous post my knowledge grew about ten times ... from 0.001% to 0.01%, so now I can see what you mean about Cyanogen and all the rest.
I know it's everything but a good excuse, but please notice that I got to Android just in the form of Xdandroid, and only in the last few weeks.
So I am learning. Maybe faster than mean people, still much slower than hardcores like you or the other devs.
----------------
In the meanwhile I reverted back to FRX03.
Mainly because of stabilities (better, instabilities are regular so that can be forecasted and behaviors provoking them can be avoided with good success rate).
Still I think that maybe (and I cap it, MAYBE) Xdandroid could (I don't say should, it would be excessive) benefit from the Neopeek/Cyanogen "thing".
You know, like when you have a crate of stuff, you dive hands in it and choose and pick up just the good things/those you like.
I just dream a Xdandroid snappy like Neopeek's whatever build (I tried 2).
... the speed ... the speed .... (put here Marlon Brando's voice in Platoon, when he repeats "the horror" ... ).
Cheers!
EDIT:
I fear that you did it all by yourself, but in any case I ask you.
Is there any public documentation about going nand? What are the advantages?
You put a thermite in my left ear, you know?!?!?!
Click to expand...
Click to collapse
nand is for the brave.. so if you are just starting. then stay away since we already had a brick happen. I also corrupted something myself so it can get nasty. Once we stabilize it will get better. The main advantage is that you no longer have windows. lol.. but the disadvantage is that you dont have windows to fall back on. It also lets us develop as if the phone would be native to android. Believe it or not but wince does alot of the dirty work for us. So the nand project lets us recreate all that ourselves.
Cyanogen is just a different animal. Xdandroid is based of pure google code as it was meant to be. It also lets us modify it for our devices that were never meant to have android. Cyanogen only supports devices that already came with android. You can modify it to run on other devices, but the main builds themselves are for specific devices. Xdandroid supports all with just 1 build. We forget sometimes about our other winmo htc brethren like topaz and blacstone. But they need a build too.. .
If you are really interested in this, you can clone both codes and compare just how different we are. If you find something you think will benefit, try it out and see what happens. Gotta love opensource.

[ACL] said:
nand is for the brave.. so if you are just starting. then stay away since we already had a brick happen. I also corrupted something myself so it can get nasty. Once we stabilize it will get better. The main advantage is that you no longer have windows. lol.. but the disadvantage is that you dont have windows to fall back on. It also lets us develop as if the phone would be native to android. Believe it or not but wince does alot of the dirty work for us. So the nand project lets us recreate all that ourselves.
Click to expand...
Click to collapse
Hep, I am just a curious guy.
One of those many that want to put their nose everywhere, but also one of the few that:
a) most of the times will need to read the guide just once (if guide isn't enough there are FAQs and Google),
b) will follow instructions easily because normally understands what they mean/what they are for
c) will never give it up until success
d) will never come to the forum writing: "I have a phonez, tried to put some android on it, doesn't work HELP1!!1!!1!"
Moreover, my TP2 is just 6 months old, is a gift, I use it for work, so to not void the warranty I didn't even install HardSPL on it.
So do not worry.
I am just curious to read how you can do it.
But will not die if I don't know yet
Cyanogen is just a different animal. Xdandroid is based of pure google code as it was meant to be. It also lets us modify it for our devices that were never meant to have android. Cyanogen only supports devices that already came with android. You can modify it to run on other devices, but the main builds themselves are for specific devices. Xdandroid supports all with just 1 build. We forget sometimes about our other winmo htc brethren like topaz and blacstone. But they need a build too.. .
If you are really interested in this, you can clone both codes and compare just how different we are. If you find something you think will benefit, try it out and see what happens. Gotta love opensource.
Click to expand...
Click to collapse
Basically you are suggesting me that all the (amazing) speed of Neopeek's builds comes just from using direct EXT/SWAP partitions on SD.
So, is there anyone trying to build a Xdandroid with EXT/SWAP structure?

sad0felix said:
Basically you are suggesting me that all the (amazing) speed of Neopeek's builds comes just from using direct EXT/SWAP partitions on SD.
So, is there anyone trying to build a Xdandroid with EXT/SWAP structure?
Click to expand...
Click to collapse
Not to my knowledge. I guess we should *try* it just to see if there's a big difference... perhaps Neopeek can help us here muhahahahaha!
But I think the theory was the tradeoff would be small - a lot more work for very little reward. However, I would be interested to see if there is a difference, and if it is big or not. At the very least just to know if it's our build or just the ext2 partition that's making it feel snappier.
In addition, AFAIK swap partitions on SD cards should be avoided, unless they have a write-levelling scheme (I believe they only put these in SSD's... I don't think any SD card has this tech because it's typically unnecessary) - I've heard swap partitions can just destroy a normal SD card because of writing and re-writing to the same area of the card many, many times... I mean physically on the card, not just logically in the folder hierarchy.

Just installed it on my diamond Bluetooth does work but it doesnt pair. The screen eventually graduates to the center dividing it in opposite. I thought maybe because I was running the hot version. Repartitioned reinstalled the normal clock version runs for a time then the same. Its no better than XDA

[Q] Review of current roms?

Just curious, I've been scouring the various threads and just figured I would post a separate thread to try and figure this out...
has anyone
1)side-by-side compared Vipers current EXT4 rom (released 1/5) vs Mammons current rom on EXT4 released 1/3) and performance gauged it ? Thoughts ?
2) If so, did you move any cache or programs to the SD card, and did you notice any increases?
3) are you using a class 6 microsd card or better ?
4) journaling - was it off or on, and did it make any difference performance wise?
5) is wifi tether working on either of them?
Thanks in advance for your help)

I'm curious on some direct comparisons as well between these ROM's, but also toss in Nebula ROM. I'd love nothing more than to be able to flash all of them and do my own benchmarking, but lack of time + my Epic is my only point of contact and i need to be reachable by my job 24/7 prevents me from getting too crazy with this stuff

Mammons 1.1.3 w/ext 4 is sweet. Coming from a stock Dk28 rom and this is amazing! No comparisons to other EXT4 roms though. Also, wireless tether 2.0.5 seems to work. A little flaky at times to connect but nothing a restart wont fix. After connecting it seems fine. Havent tried the new tether 2.0.6 released today yet.

Please post questions in General section.

sorry about that----i figured that general was just nonspecific stuff...and questions like this were about developing roms, so went there my bad )

I have tried both of these. Both are great ROM's. I am currently on Mammon's for personal preference. I have had no stability issues what so ever.
-I am still on RFS, so I cannot comment on the ext4 stuff.
-I have the stock SD card.
-No programs on SD card unless it does it automatically.
-Wifi tether works amazing, I use barnacle free though. the android-wifi-tether was too flaky for me. barnacle allows me to work off the wifi connection for a long time ( I have tested up to 5 hrs without problem, haven't had time to test longer)
I don't have performance programs to test. From real world perspective, Mammon's seem slightly more stable to me. And what I mean by that is, it feels snappy all the time. Sometimes with Viper, when I would go to make a phone call, I would get a tiny bit of lag etc. I don't know if it was me or the actual rom. I wouldn't take anything away from Viper though, it is a really nice rom.
All I know is, with either Viper or Mammon, my phone was running far better than it ever was at stock or any 2.1 rom, and it had more features! These guys make high quality, feature rich roms. They should be working for google or samsung or something.

[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] Which version should i use? (Not asking which rom is better)

Hello guys! I need your help and advise.
I need to use my kaiser to work. That's uhh.. receiving calls, making calls, sms, WiFi @ night to sync new contacts to my Google account... you know, small tasks.
I'm using as of yet CM7 with 2.3.32 (#63 IIRC) Data on SD Partition. Now.. although stable (no reboots, no crashes... seems OK) Its painfully slow.
If someone calls me, i have to wait about 7 ringtones before i know who's calling me. So.. i need your advise! Should i use a Donut ? perhaps a 2.6.25 ?
Please be honest, state your opinion and its basis
UPDATE 20110304:
I'm using as of yet:
VaniljEclair RLS11 - A fast & stable CM 5.0.8 for Vogue/Kaiser/Polaris [2010-08-19]
Battery rocks (i'm using a 2.8Ah).
Calls work pefectly.
SMS's work perfectly
Some apps apear to have a .... strange issue. They simply... don't open. But thats temporary. And a reboot fixes.
WiFi works (using latest from liquid with module update).
Quite happy
UPDATE 20110306:
Still no issues. One thing is granted, when i turn the WiFi on and let it sync... bogs down considerably. OC via atools to 490.
Will try the other option now, incubus26c's versions.
UPDATE 20110309:
Using incubus26c's with kernel .25 downloaded and edited through atools.
Been sufering from random phone problems. Simply shutdown. Cannot enable AirPlane mode. Have to reboot.
BTW, anyone has any other sugestions about roms ??
UPDATE 20110310:
Noted that my hardware keyb is sometimes eating letters... notably.. space.
Will check settings to see if disabling something helps.

Try using builds like those by incubus26c's or VaniljEclair. I've had both and enjoyed them greatly, going back to WM for the only reasons of better camera (autofocus never worked on droid for Kaiser) and ad-hoc WiFi support.
And... a few tips.
1. Use phone prioritizer (probably in VanilJEclair). This cuts delay between calling and receiving a call by two times.
2. Odexed firmware is faster, than deodexed. Yeah, no themes anymore, but you want a working device, not a box for bells and whistles, aintcha?
3. 2.6.25 is still up to date. Sometimes you'll need a patch to make wifi work, but that is a reasonable price for better speed.
What about donut? No, it is not faster then any 2.x droids.

StripezZ said:
Try using builds like those by incubus26c's or VaniljEclair. I've had both and enjoyed them greatly, going back to WM for the only reasons of better camera (autofocus never worked on droid for Kaiser) and ad-hoc WiFi support.
And... a few tips.
1. Use phone prioritizer (probably in VanilJEclair). This cuts delay between calling and receiving a call by two times.
2. Odexed firmware is faster, than deodexed. Yeah, no themes anymore, but you want a working device, not a box for bells and whistles, aintcha?
3. 2.6.25 is still up to date. Sometimes you'll need a patch to make wifi work, but that is a reasonable price for better speed.
What about donut? No, it is not faster then any 2.x droids.
Click to expand...
Click to collapse
Clear enough.
Will report back with more info
Thank you

1st Post updated.

And again.

Still no issues. One thing is granted, when i turn the WiFi on and let it sync... bogs down considerably. OC via atools to 490.
1. get RogueTools from Market to overclock the device without atools
2. a question from my side: are Gingerbones worth it?

I actually used and tweaked a Gingerbones. Was quite good, not as fast of course, but then again, more eye candy.
I'm not getting any instability, just plain ... slow during sync. But this as been a standard with any version i've tested.

wifi sync lagging seems to be quite common for all low-end droids, both native and cooked. As long as it happens mostly with encrypted networks, i would suppose the reason is some sort of cryptographic calculations MSM72xx delegates to CPU.
Though, since all unsecured networks I encountered were very slow (256k or so), there's a chance the lag nests in higher bandwidth, causing data to be downloaded a bit too fast to be processed - sometimes HSDPA connection makes the gadget lag, too.

daedric said:
UPDATE 20110310:
Noted that my hardware keyb is sometimes eating letters... notably.. space.
Will check settings to see if disabling something helps.
Click to expand...
Click to collapse
There is strange polling behavior with hardware keyboard on 2.6.25
Though I love stability in 2.6.25 kernel, the Eating of Space button is quiet frustrating when I am texting my boss :| (which I often do) and I press Enter to send right away (just as I am chatting).

StripezZ said:
wifi sync lagging seems to be quite common for all low-end droids, both native and cooked. As long as it happens mostly with encrypted networks, i would suppose the reason is some sort of cryptographic calculations MSM72xx delegates to CPU.
Though, since all unsecured networks I encountered were very slow (256k or so), there's a chance the lag nests in higher bandwidth, causing data to be downloaded a bit too fast to be processed - sometimes HSDPA connection makes the gadget lag, too.
Click to expand...
Click to collapse
So... if the massive slow(ness?? is this a word??) is coming for a bogged CPU on SSL encode/decode, we could... say... use OsMonitor to check?
Which process should be giving lots of CPU usage ?? Android System ?

dark_prince said:
There is strange polling behavior with hardware keyboard on 2.6.25
Though I love stability in 2.6.25 kernel, the Eating of Space button is quiet frustrating when I am texting my boss :| (which I often do) and I press Enter to send right away (just as I am chatting).
Click to expand...
Click to collapse
So... perhaps moving to 2.6.32 should provide me with it a better keyboard polling, at a stability price ??
P.S.
Anyone else would like to suggest another rom ?? BTW... i'm going to try and strip a gingerbones (by Aceyome if i remember his nick right) to gain extra stability.

I think yes. Though I have used .32 kernel for so less time than .25 so as I need the Mass storage functionality, which works perfect with dual mount on .25 kernel. Try Fat Free Froyo by thoughtlesskyle, if you really want a vanilla build

dark_prince said:
I think yes. Though I have used .32 kernel for so less time than .25 so as I need the Mass storage functionality, which works perfect with dual mount on .25 kernel. Try Fat Free Froyo by thoughtlesskyle, if you really want a vanilla build
Click to expand...
Click to collapse
Hey dark_prince, OFF TOPIC question:
How is the Froyo 2.2 x86 ?

daedric said:
Hey dark_prince, OFF TOPIC question:
How is the Froyo 2.2 x86 ?
Click to expand...
Click to collapse
Still not to be used as Primary OS. Alot of things don't work and force close on my D420. Though x86 build works pitch perfect with an EEEPC. It's blazing fast and stripped down to just 80MB and has Hardware OpenGL ES support for intel 915,945,965 chipsets. 1280x800 isnt supported fully as of yet (You can run HDPI one). Market doesnt work, but a proprietary App downloader is provided. Also, keyboard works perfect and mouse emulation is nice. Ethernet + Wifi support depends if kernel supports.

Why doesn't the market work??
(market! y u no work?)

daedric said:
Why doesn't the market work??
(market! y u no work?)
Click to expand...
Click to collapse
It crashes randomly with the build, thats why it was removed. But there is another handy app installer which comes with every x86 build

[Q] ics-deck-inc vs Evervolv vs OMX?

I've been following OMX and ics-deck-inc and I'm wondering which people think is better.
EDIT: Since I posted this, the Evervolv ICS ROM (posted on Twitter only) has gained popularity. It was the first to bring partial camera support, and although ics-deck has since added it, it seems most new features show up in Evervolv first. OMX is also fading away into obscurity.
These are my impressions based on the comments...
ics-deck-inc has been updated more recently (12/25), while development on OMX seems to be at a standstill (going on almost a month). I'm assuming the OMX standstill was related to the holidays though, since before that it was being updated very often.
EDIT: ics-deck-inc is now up to Alpha 5 as of this edit, while OMX is still at a standstill. It seems from this post that there is only 1 person working on OMX
OMX seems to be more further along, but maybe it's an illusion due to the fact that OMX has a much more detailed change log and explains the updates much more clearly (i.e. ics-deck-inc seems to be in "aplha1" still even through I know there have been a few updates)
EDIT: ics-deck-inc and Evervolv have far surpassed OMX. Personally,I prefer Evervolv, but I go back and forth between it and ics-deck-inc.
I see a lot of talk in the comments for ics-deck-inc about having to install Ext4 and Incredikernel, which adds more work for me and a higher chance of messing something up. I don't know about Ext4, but OMX already includes Incredikernel at least (although neither of them explain why I need Ext4 or Incredikernel).
EDIT: ics-deck-inc, Evervolv, and OMX all include incredikernel.
ics-deck-inc has a "Calendar fix" posted but I see a lot of commenters still having problems. Not sure whether or not this is a problem in OMX, but I haven't seen many people complaining about it (at least not lately).
EDIT: It's actually a lot simpler than that calendar fix... you just need to do this and all is well. There's also a fix for exchange calendar sync issues posted a little later in this thread
ics-deck-inc lists Wimax as something that's broken, but since when does the Incredible have Wimax anyway? Anyone know what the deal is with that?
EDIT: It seems this is there because the developer makes ROMs for other devices as well. Inc uses can just ignore it
So most of the above comments are obsolete at this point, but you can still feel free to use this thread to discuss changes and such. There is a separate feedback thread somewhere, but (a) that's just for deck, and (b) this is more about discussion than feedback.

I can just wait

demarcmj said:
I've been following OMX and ics-deck-inc and I'm wondering which people think is better.
These are my impressions based on the comments...
ics-deck-inc has been updated more recently (12/25), while development on OMX seems to be at a standstill (going on almost a month). I'm assuming the OMX standstill was related to the holidays though, since before that it was being updated very often.
OMX seems to be more further along, but maybe it's an illusion due to the fact that OMX has a much more detailed change log and explains the updates much more clearly (i.e. ics-deck-inc seems to be in "aplha1" still even through I know there have been a few updates)
I see a lot of talk in the comments for ics-deck-inc about having to install Ext4 and Incredikernel, which adds more work for me and a higher chance of messing something up. I don't know about Ext4, but OMX already includes Incredikernel at least (although neither of them explain why I need Ext4 or Incredikernel).
ics-deck-inc has a "Calendar fix" posted but I see a lot of commenters still having problems. Not sure whether or not this is a problem in OMX, but I haven't seen many people complaining about it (at least not lately).
ics-deck-inc lists Wimax as something that's broken, but since when does the Incredible have Wimax anyway? Anyone know what the deal is with that?
Has anyone out there used both RECENTLY and have some thoughts?
Or does anyone who has only used one or the other want to agree or disagree with any of my impressions above?
Click to expand...
Click to collapse
I've only used OMX. I got hooked on it, but unfortunately just flashed back to CM7.1 today. In OMX, calendar does not sync with google. Wifi tethering works. Cam no work. Can't use phone as external storage when connect to computer. Also, the ring tones and volume controls are all messed up: phone never rang, just vibrates. When playing pandora, sound is very low, even at max setting. Headphones are not recognized. When I connected to bluetooth in the car, i could make a call and talk over the bluetooth, but pandora or other media would not play through bluetooth.
Unfortunately it sounds like OMX will not be getting another update any time soon. And CM9 is probably still another several months away for INC, if they release it at all. So....looks like i'm stuck with stupid CM7.1 (or maybe MIUI) until i get my tegra3 ice cream phone!

I have been running ics-deck-inc since yesterday morning and here are some things I can tell you:
-Well, first off ics-deck-inc got updated a couple of days ago with loads of fixes including the camera. There are still some strange issues with the camera, but hey, it works.
-As far as incredikernel, ics-deck-inc already has it in the ROM. Therefore you don't have to flash it. There is a new incredikernel from 1/2/2012, while the one in the ROM is from December. Flash the new one if you want, but you don't have to.
-My calendar has worked without issue since I installed it. I think the issue is that calendars from Exchange and such don't sync with it.
-I think the Wimax thing is for another phone and not the incredible.
-Bluetooth works great. Syncs up with my head unit in my truck just fine. Pandora over bluetooth works great as well. The only thing is I can't get the metadata to stream to my head unit.
Hope that helps.

Well, I'll put my own experiences in now that a couple people have replied...
A couple days after posing the question, CyanogenMod decided to stop working for me (as others have noted that it tends to do after a period of time) so I decided to give some of these ICS ROMs a try since I was going to have to reflash anyway
I started with the Evervolv 2.1.0 Preview3 build posted on twitter so far [twitter.com]) because it was the first one to have camera support, which was one of the things keeping me from making the jump in the first place. The Evervolv build worked great for me. There was the occasional force close, but that is to be expected.
Then ics-deck-inc was updated to Alpha 4 yesterday to include, among other things camera support. I decided to move to deck since many people had noted that it was a bit better all-around than Evervolv. And now that it had camera support, there was no reason not to switch.
A few notes:
As awesomeo3000 pointed out, incredikernel is included. It's not the most up-to-date, but nobody has given any compelling reasons that you absolutely need the latest. (this was the case with Evervolv and OMX also)
I haven't really noticed a significant difference in battery life over my other ROMs, but that is probably because I am pretty much always around a charger so I don't really notice.
ics-deck comes with the Trebuchet (CM9) launcher, which is essentially stock ICS with some enhancements. It allows things like changing the # of homescreens, resizing any widget (stock only allows some), and other tweaks that are very useful but at the same time won't bother anyone who wants pure stock. Unfortunately, there seems to be two significant bugs in the app drawer in both the stock launcher and Trebuchet: (1) often times the next page of apps or widgets will show up in the background before you even attempt to switch pages, and (2) the launcher force closes very often when paging though the widgets. To alleviate that, I have switched to Nova Launcher which, like Trebuchet, is based on the stock ICS launcher but offers many helpful tweaks. I I still have had the occasional force close related to selecting widgets, but Nova also restores the long-press on the homescreen for widgets functionality, which can be used as another option if you experience force closes.
There are some small bugs that I have noticed here and there (like this one), but nothing really major, other than the well-known issues like calendar syncing and usb-host (see below). I also haven't yet tested a lot of things, like bluetooth for one.
My calendar syncing issues were solved by doing this: link. There was no need to replace the calender apps or anything like that. I can't speak for the Exchange Calendar syncing though. I can say that I was able to get an Exchange email account to work fine, but I don't use the calendar for that account.
As many people in the forums note, the multi-mount widget in the Android Market can be used to get usb-host support. Hopefully something will be built into the ROM in the future, but for now this should work. Alternatively, you can try what I use, the Samba Filesharing app. It's not as fast as USB, but wireless has it's own convenience advantages.
These are just some things I have noticed. There are some great features in ics-deck that I haven't even listed, and also some minor bugs. Alpha 5 is out now, only one day after Alpha 4, and I am excited to give it a try. I have to say that at this point I think they could drop the "Alpha." I think it could at the very least be considered "Beta" but that is just my opinion.
The important thing is this, anyone who is still using CM7 or any other ROM because they are waiting for an ICS ROM that is reasonably stable to use as a daily driver, I think ics-deck-inc has reached that point.

awesomeo3000 said:
Unfortunately it sounds like OMX will not be getting another update any time soon. And CM9 is probably still another several months away for INC, if they release it at all. So....looks like i'm stuck with stupid CM7.1 (or maybe MIUI) until i get my tegra3 ice cream phone!
Click to expand...
Click to collapse
You should definitely try ics-deck (see my post above)

Does MMS work? how partially working is the camera? can u at least take pictures and video

Evervolv has a build going as well, and they have 8 MP camera functional as well as USB mass storage. I'm going to try it now to see how it works.

TeeRom said:
Evervolv has a build going as well, and they have 8 MP camera functional as well as USB mass storage. I'm going to try it now to see how it works.
Click to expand...
Click to collapse
Yup, I mentioned Evervolv's ROMs. I can definitely say the 8MP camera is working (video and panorama modes still aren't). I haven't tested out USB storage yet but they swear it works.
Right now Evervolv is my favorite, but they seem to go back and forth (hence both in my signature). Best to keep an eye on both (I've given up on OMX, big time)
EDIT: I have now also added Evervolv to the title of the thread.

I've tried both ICS deck and Evervolv, but neither display my exchange calendar in the calendar app, which is a showstopper for me. Unfortunate, as I likes me some sammich. Exchange syncs fine, and sync settings claims the calendar is up to date, but the calendar app says "no calendars" for the exchange account. Anyone had any luck with this or have a workaround that you like?

Exchange calendar issue fixed in Evervolv by flashing the zip from from this tweet.

There is a fix for the exchange.apk with the evervolv ics rom peview 5. I have it posted in rootzwiki. i had someone try it out and they confirmed it did work. Just look for post by apophis9283 in rootzwiki

Actually no need to install ext4 on any of them. Its not required.
Sent from my Galaxy Nexus using Tapatalk

http://twitter.com/MongooseHelix
Here is a link to the next preview build from the evervolv guys.

ralph0015 said:
http://twitter.com/MongooseHelix
Here is a link to the next preview build from the evervolv guys.
Click to expand...
Click to collapse
Thanks... here is the link to the actual twitter post: https://twitter.com/#!/MongooseHelix/status/160269895265828864
Direct Link to the ROM: http://t.co/btSyQQ0o (MD5 Sum e193f7bf9eb83233bff02aa40bb84fd0)
Direct Link to their new gapps: http://t.co/m3DOolG8
Direct Link to their exchange fix: http://t.co/IIALIskJ
(Note: they say not to flash the new gapps if you're using the exchange fix)
P.S. I updated the main thread to add Evervolv to the title... I didn't realize I could do that when I last updated it. (I also updated some of the text in there)

demarcmj said:
Direct Link to their exchange fix: http://t.co/IIALIskJ
(Note: they say not to flash the new gapps if you're using the exchange fix)
Click to expand...
Click to collapse
Note that the exchange fix isn't needed for Preview 6 anymore, they apparently baked it in. Installed P6, latest gapps and ext4 mod from a full wipe and all is well.

"Haus" said:
Note that the exchange fix isn't needed for Preview 6 anymore, they apparently baked it in. Installed P6, latest gapps and ext4 mod from a full wipe and all is well.
Click to expand...
Click to collapse
Does this one have panoramic for the camera? its probably the only thing keeping me from using any ICS at the moment (I could care less about video.. I think I've taken 4 in since I had the phone.. and I got it day 1)

Not sure, i went back to cm7 atm only because certain apps fc with ics

I couldnt stay away from the ics goodiness. Went back to evervolv preview 6. Hope these devs get these market apps compatible with ics soon

I loved Evervolv p5 but it still felt unfinished to me. Didn't have any FCs but after running MIUI for so long, I was missing the customization options. I'll probably be back soon though...