[ROM] [ROM] Droid Concepts Froyo Releases [BETA versions]

[DucksDroid]

Did you have any issues restoring from titanium? Any soft reboots? What kernel did you use?

It sounds like you had a similar experience to mine. When I tried to restore an app from Titanium, there was a soft reboot. No problem installing from Market or using Appbrain. However, if I then used Titanium to restore data, the app would not open (had to force close). I was coming from Gimpsquad, which is Froyo.

Sent from my Droid1 using DroidForums

 

[ecsnead69]

I will look through my old files and find the original wallpapers. If I can't find them I will find the images and make new ones.... may take a couple days, I am out of town again working 12 hour days....

 

[JStandiford21]

Did you have any issues restoring from titanium? Any soft reboots? What kernel did you use?

It sounds like you had a similar experience to mine. When I tried to restore an app from Titanium, there was a soft reboot. No problem installing from Market or using Appbrain. However, if I then used Titanium to restore data, the app would not open (had to force close). I was coming from Gimpsquad, which is Froyo.

Sent from my Droid1 using DroidForums

Yes, that's exactly what is happening. I too came from Gimp, and wiped. Did you figure it out?

Sent from my OG Droid using DroidForums

 

[DucksDroid]

Did you have any issues restoring from titanium? Any soft reboots? What kernel did you use?

It sounds like you had a similar experience to mine. When I tried to restore an app from Titanium, there was a soft reboot. No problem installing from Market or using Appbrain. However, if I then used Titanium to restore data, the app would not open (had to force close). I was coming from Gimpsquad, which is Froyo.

Sent from my Droid1 using DroidForums

Yes, that's exactly what is happening. I too came from Gimp, and wiped. Did you figure it out?

Sent from my OG Droid using DroidForums

Not really. I also wiped before installing and just reinstalled apps using AppBrain, after getting the soft reboots, and then set them up manually. It takes more time, but is a clean install. (Same thing I had to do after trying a couple of GB roms.)

On a positive note, this rom runs so much better on my OG Droid than those ever did! The only other thing I've noticed is that the Bluetooth symbol doesn't change to show when you are connected. I'm using ChevyNo1's 1.0Ghz-lowV kernel and this rom is fast and good with memory management.

Thanks to the DC team!

Sent from my Droid1 using DroidForums

 

[kratos]

Ok, just wanted to follow up with this since built 7 has come out.

I am still losing text messages from time to time. Since build 7, it seems to only happen while charging or for about 1-1 1/2 hours after a charge. However, I haven't noticed any lost messages at other times.

Kratos

 

[JayR_]

Ok, just wanted to follow up with this since built 7 has come out.

I am still losing text messages from time to time. Since build 7, it seems to only happen while charging or for about 1-1 1/2 hours after a charge. However, I haven't noticed any lost messages at other times.

Kratos

is any one else experiencing this problem?

also, kratos, do you have any form of task killer that may be interfering with your messaging service?

do you live in a spotty coverage area? or travel to one frequently? in the past ive noticed that if i leave my coverage area and come back i miss out on voice mails and texts, etc...

i wish i had an easy answer for you, but at the same time i really dont think its a problem with the rom and its memory management.

That being said though, ive been wrong on several things in the past and this could very well be one of them So please anyone else reading this thread experiencing the same issue, let it be known.

 

[woodyman]

I guess that is better news, still not as I hoped.. good news is I added options to lock home and lock mms app in memory in the new build of the settings app.

Ok, just wanted to follow up with this since built 7 has come out.

I am still losing text messages from time to time. Since build 7, it seems to only happen while charging or for about 1-1 1/2 hours after a charge. However, I haven't noticed any lost messages at other times.

Kratos

 

[kratos]

Ok, just wanted to follow up with this since built 7 has come out.

I am still losing text messages from time to time. Since build 7, it seems to only happen while charging or for about 1-1 1/2 hours after a charge. However, I haven't noticed any lost messages at other times.

Kratos

is any one else experiencing this problem?

also, kratos, do you have any form of task killer that may be interfering with your messaging service?

do you live in a spotty coverage area? or travel to one frequently? in the past ive noticed that if i leave my coverage area and come back i miss out on voice mails and texts, etc...

i wish i had an easy answer for you, but at the same time i really dont think its a problem with the rom and its memory management.

That being said though, ive been wrong on several things in the past and this could very well be one of them So please anyone else reading this thread experiencing the same issue, let it be known.

No Task Killer... I had one when the Verizon Rep installed it more than a year ago, but quickly uninstalled it due to the Android being based on Linux.

Nope, I'm right in the center of major coverage. I do travel in this area, but never leave major coverage area.

I honestly think that it is due to Droid RAM period. I had this problem on stock, BB, Ud, and even CM, among other ROMs. Then when the option to lock sms/mms in memory, it literally went away. Granted it's not as bad as it was on build 6, it is still present.

I guess that is better news, still not as I hoped.. good news is I added options to lock home and lock mms app in memory in the new build of the settings app.

Ok, just wanted to follow up with this since built 7 has come out.

I am still losing text messages from time to time. Since build 7, it seems to only happen while charging or for about 1-1 1/2 hours after a charge. However, I haven't noticed any lost messages at other times.

Kratos

That is good to hear. I really hope that this is what is needed. I also really hope that it doesn't have anything to do with me flashing so many ROMs in such little time...

Kratos

 

[JayR_]

yes i used titanium with this build

Did you have any issues restoring from titanium? Any soft reboots? What kernel did you use?

And, are you in Missouri?

Sent from my OG Droid using DroidForums

i didnt have any issues with titanium, i restored only a few user apps/data, im using raid zeros low voltage 1100 kernel, and havent experienced any reboots...

i dont know if this helps, but when i wipe before installing a rom, i go to the partitions menu (i use clockwork by the way) and format boot, then in the same menu, i format system....then i go back and wipe the data and cache 2 times...like i said though i dont even know if this matters, woodyman may have even put scripts in the install to format the boot and system, and what im doing is just over kill lol

and yes im in missouri, st louis to be exact

 

[woodyman]

SOME UPDATES:

I'm still working on the issue with the built in CPU clock, but a lot of additions have been put into build 08 so far and because of the extent of things that have been done, I think I will build and release 08 tomorrow. most likely CPU clock will not function unless I can get it fixed tonight.

now for that explanation.
The code itself for the CPU over-clock built in came from CVPCS and it got refined a little by the CyanogenMod team. It was back-ported to the ROM for me by MisterE. The code end of the CPU stuff is solid and functioning. We know that cause it doesn't put out any FC errors and it does function with another over-clock app installed, but even without another over-clock app it still will not FC. So because of that I had a good guess that the problem wasn't with the app code. So to confirm this I hooked up to ADB pulled the logcat and tried to change the clock. The logcat output states permission denied, so I know what the problem is, but not exactly how to fix it. It may seem like something easy to fix, but its harder than you would think, MisterE was working on it and trying to fix it, and now I am going to start on it too. So it should be fixed soon, but I'm not going to say it will work in B-08. So I'm going to try to workout permission problems tonight with that, hopefully it all goes well and it is working for B-08, but no promises.

as for other updates, here's just my thoughts on a few things I've noticed reading the posts..

mms issues I have no explanation for, me and davros talked last night and neither of us have ever had any problems with it, and from the posts it seems like most of you haven't either, but a few have had some issues, but say the OTA one works perfect. I believe you and don't doubt what your saying, but one thing to note is the code base of this ROM is the latest Android Froyo version. 2.2.2 so it working on the OTA but not here doesn't make sense to me because all the code is the same. I have added parts of code to the app, but have not re-done or messed with anything that deals with message sending/receiving. I've simply added more options to vibrate and LED, and others that improve the app. So if you are having issues, please report them so I can see how big of a problem this is, and if you can try to get the problem to happen while running 'adb logcat' and get me the output. There may be an error on your device of some sort or with the app that is only showing up rarely, and the only way of me fixing it is if I know what to look for. otherwise trying to review all the messaging code is like trying to shift through all the sand on a beach in order to find a blue grain of sand. If an error was significant then source WILL NOT compile the app, Android was set up to check it self like that, it doesn't get everything, but all major things are caught when compiling.

NOTE ABOUT RESTORE/TITANIUM
personally I have never used titanium or any other backup feature other than the Google/Android provided ones. I'm not saying not to use them or anything, but I never used them because I liked the getting the clean install like you guys mentioned. The fact that your getting soft reboots is because titanium messes with the device /data directory and most of the time there are no issues, but you need to remember when you backup your app it may be named 'com.example.app.1' but when you re-install if from the market it may be downloaded as 'com.example.app' I've noticed that when apps install usually they look like com.example.app and some apps when they update put a 1 after the name. that happens because you can't have 2 folders with the same name, and when you update the app, it will build the dependencies it needs on your phone, but it does it in a new directory then moves your files into the new one. So my guess which could be wrong is that your apps all say .1 or whatever in your backups but the phone is then having a directory for com.example.app and com.example.app.1 which it doesn't need, because after it moves everything to the .1 folder when an app updates it removes the old com.example.app folder so you dont have 2. so this could explain the soft reboot issues you are having. idk if that made sense but i tried.. lol its been a long day.

Please continue to report issues and if you can get me the logcat of your problem please do and send it my way so I can fix the problem if there is one for everyone.

Thanks..

 

[JayR_]

Ok, just wanted to follow up with this since built 7 has come out.

I am still losing text messages from time to time. Since build 7, it seems to only happen while charging or for about 1-1 1/2 hours after a charge. However, I haven't noticed any lost messages at other times.

Kratos

is any one else experiencing this problem?

also, kratos, do you have any form of task killer that may be interfering with your messaging service?

do you live in a spotty coverage area? or travel to one frequently? in the past ive noticed that if i leave my coverage area and come back i miss out on voice mails and texts, etc...

i wish i had an easy answer for you, but at the same time i really dont think its a problem with the rom and its memory management.

That being said though, ive been wrong on several things in the past and this could very well be one of them So please anyone else reading this thread experiencing the same issue, let it be known.

No Task Killer... I had one when the Verizon Rep installed it more than a year ago, but quickly uninstalled it due to the Android being based on Linux.

Nope, I'm right in the center of major coverage. I do travel in this area, but never leave major coverage area.

I honestly think that it is due to Droid RAM period. I had this problem on stock, BB, Ud, and even CM, among other ROMs. Then when the option to lock sms/mms in memory, it literally went away. Granted it's not as bad as it was on build 6, it is still present.

I guess that is better news, still not as I hoped.. good news is I added options to lock home and lock mms app in memory in the new build of the settings app.

Ok, just wanted to follow up with this since built 7 has come out.

I am still losing text messages from time to time. Since build 7, it seems to only happen while charging or for about 1-1 1/2 hours after a charge. However, I haven't noticed any lost messages at other times.

Kratos

That is good to hear. I really hope that this is what is needed. I also really hope that it doesn't have anything to do with me flashing so many ROMs in such little time...

Kratos

i see, well lets hope woodymans new feature takes care of it for yadancedroid
i feel for you though, i felt pretty silly for the first time i was using gingerbread and i was missing all kinds of calls texts, etc

 

[woodyman]

It very well could be, I think we all lost sight of the time when the Original Droid launched, it was amazing, but phones have come a long way since, and its incredible that the Droid got froyo, because most phones don't get as many updates as the Droid has had, and each new version uses more RAM and the tasks become more demanding, and our hardware is outdated. I've made some RAM tweaks and I plan on making more just to try to do what I can to compensate and try to fix any issues.

I honestly think that it is due to Droid RAM period. I had this problem on stock, BB, Ud, and even CM, among other ROMs. Then when the option to lock sms/mms in memory, it literally went away. Granted it's not as bad as it was on build 6, it is still present.

That is good to hear. I really hope that this is what is needed. I also really hope that it doesn't have anything to do with me flashing so many ROMs in such little time...
Kratos

No, I wouldn't think it came from flashing, I couldn't tell you how many times I've flashed.. lol or broken had to RSD, and yet I don't experience any of these mms bugs that people have.

like I said man everyday these phones do something new to amuse me.. lol

thanks for the support and constant feedback man, i really appreciate it..

 

[woodyman]

I can't remember what it wipes in the install, but wiping all of them is not a bad idea, I do that each time I flash, unless its for a quick test of something. I may add scripts though to wipe everything in the next build just to see if that helps anything, because it very well could be the fact that pieces are mix and matching which is defiantly not a good thing..

thanks for the reminder.. lol.. looking forward to the blue, its been awhile since i've had a nice blue theme..

i didnt have any issues with titanium, i restored only a few user apps/data, im using raid zeros low voltage 1100 kernel, and havent experienced any reboots...

i dont know if this helps, but when i wipe before installing a rom, i go to the partitions menu (i use clockwork by the way) and format boot, then in the same menu, i format system....then i go back and wipe the data and cache 2 times...like i said though i dont even know if this matters, woodyman may have even put scripts in the install to format the boot and system, and what im doing is just over kill lol

and yes im in missouri, st louis to be exact

 

[JayR_]

woody- excellent write up , especially the part explaining titanium and how it works in conjunction with the market updating apps and such...ive never thought about that before, and i have noticed that the com.android."app name"etc....with often change slightly when the app is updated like you said. im always looking through my /system and /data im kinda funny like that lol.

anyway thanks for the info ive never put 2 and 2 together in this sense

 

[kratos]

It very well could be, I think we all lost sight of the time when the Original Droid launched, it was amazing, but phones have come a long way since, and its incredible that the Droid got froyo, because most phones don't get as many updates as the Droid has had, and each new version uses more RAM and the tasks become more demanding, and our hardware is outdated. I've made some RAM tweaks and I plan on making more just to try to do what I can to compensate and try to fix any issues.

I honestly think that it is due to Droid RAM period. I had this problem on stock, BB, Ud, and even CM, among other ROMs. Then when the option to lock sms/mms in memory, it literally went away. Granted it's not as bad as it was on build 6, it is still present.

That is good to hear. I really hope that this is what is needed. I also really hope that it doesn't have anything to do with me flashing so many ROMs in such little time...
Kratos

No, I wouldn't think it came from flashing, I couldn't tell you how many times I've flashed.. lol or broken had to RSD, and yet I don't experience any of these mms bugs that people have.

like I said man everyday these phones do something new to amuse me.. lol

thanks for the support and constant feedback man, i really appreciate it..

I too am surprised at how far my OG Droid has made it! I'm a little sadden as well to know that the chances of having a fully unlocked/unencrypted bootloader combined with Vanilla Android for Verizon again are basically non-existent.

I would hope that flashing wouldn't have any effect on the hardware, but who knows... LOL

I'm happy to give my feedback and support! This ROM rocks, even with this ONE very small issue. And i mean this is the only issue I have with build 7 and it really isn't that big because it only happens when charging and for a short while after a charge. Since I have been constantly getting 18-22 hours ber charge with moderate to heavy use, I can't complain, only report!

Thank you for everything!

Kratos