Genesis Version 1 (Overlay themed CM ROM)

[Porterhouse0]

when i opened root explorer it gave me the allow or deny option...but i was picking up the phone as i was going to hit allow...but it switched to landscape mode and i think i hit deny...now root explorer wont open. if i clear data from superuser will this clear any problems?

Yup - it should...can't remember, but I think you can clear permissions indvidually...

thanks man i appreciate the response. i cleared superuser data and i was golden. the fix that was posted also worked. thanks everyone

 

[slayher]

Any plans on updating this to reflect Test1 build that is out? Believe this is based off Test0.

There is no real change between the 2. Test0 is fine for now. I dont think there are gonna be any other changes heading into 5.0.7 for the droid, so all we are waiting on is the libopencore fixes to go in, so HQ recording is not broken.

5.0.7 is mainly a catchup release for Dream/Sapphire, since they have been on donut for so long.

On a good note though, as soon as i get the word that the recording fix is in the code, i can update in about 15 minutes

 

[Redflea]

Any plans on updating this to reflect Test1 build that is out? Believe this is based off Test0.

There is no real change between the 2. Test0 is fine for now. I dont think there are gonna be any other changes heading into 5.0.7 for the droid, so all we are waiting on is the libopencore fixes to go in, so HQ recording is not broken.

5.0.7 is mainly a catchup release for Dream/Sapphire, since they have been on donut for so long.

On a good note though, as soon as i get the word that the recording fix is in the code, i can update in about 15 minutes

I tried the two optional Video settings in build.prop and got a complete lock-up of my droid after 10s of recording....

Going to try now w/just 30fps and back to lower bit rate...have you tried the optional settings, Slayher?

 

[Redflea]

Hmmm....tried 30fps only and also locked up and then rebooted spontaneously.

Not normal...also noticing that when I launch the camera the first time it makes the sounds that indicates it's launching but it never launches, the second time it does launch.

Set fps back and things work fine again...

Just me?

Anyone else with similar issues if you try the fps or bit rate hacks?

 

[slayher]

Hmmm....tried 30fps only and also locked up and then rebooted spontaneously.

Not normal...also noticing that when I launch the camera the first time it makes the sounds that indicates it's launching but it never launches, the second time it does launch.

Set fps back and things work fine again...

Just me?

Anyone else with similar issues if you try the fps or bit rate hacks?

There is definitely issues with the libs that allow for recording. This was just a temporary fix that can't be completely relied on. Its kinda like a slow leak in your tire, if you can air it back up, it will work for a little while, but until you fix the leak, you still have a problem with the tire.

Don't worry I am sure we will find a fix soon. If you need it bad enough, Cennis91 reported you could take all the libopencore files from 5.0.6.2 and push them into the test, and it works/fixes the issue.

 

[Redflea]

Hmmm....tried 30fps only and also locked up and then rebooted spontaneously.

Not normal...also noticing that when I launch the camera the first time it makes the sounds that indicates it's launching but it never launches, the second time it does launch.

Set fps back and things work fine again...

Just me?

Anyone else with similar issues if you try the fps or bit rate hacks?

There is definitely issues with the libs that allow for recording. This was just a temporary fix that can't be completely relied on. Its kinda like a slow leak in your tire, if you can air it back up, it will work for a little while, but until you fix the leak, you still have a problem with the tire.

Don't worry I am sure we will find a fix soon. If you need it bad enough, Cennis91 reported you could take all the libopencore files from 5.0.6.2 and push them into the test, and it works/fixes the issue.

OK, great, thanks for clarifying, appreciate it. I'll leave things as they are for now and await the final fix, not like I'm filming a movie for theatrical release or anything...

 

[jmart8684]

Hmmm....tried 30fps only and also locked up and then rebooted spontaneously.

Not normal...also noticing that when I launch the camera the first time it makes the sounds that indicates it's launching but it never launches, the second time it does launch.

Set fps back and things work fine again...

Just me?

Anyone else with similar issues if you try the fps or bit rate hacks?

I have the same problem. If I remember correctly, some devs had the same prob going too high with the fps, so it's not just you..lol

 

[mjh68]

Hmmm....tried 30fps only and also locked up and then rebooted spontaneously.

Not normal...also noticing that when I launch the camera the first time it makes the sounds that indicates it's launching but it never launches, the second time it does launch.

Set fps back and things work fine again...

Just me?

Anyone else with similar issues if you try the fps or bit rate hacks?

I have the same problem. If I remember correctly, some devs had the same prob going too high with the fps, so it's not just you..lol

I was able to use 30fps and 80000 changes without an issue . I did it in the Genesis build and also the plain test1 build and both hacks worked just fine . Granted I didn't record alot of video , but about 30 seconds and played it back properly.

 

[Jus Cruisin]

Tried to add Smoked Glass-esque theme v1.5.2. Boot loop...... And guess who didn't backup Genesis... Also switched to P3Droid kernel.

?????? Just re-booted and everything was saved (applications, screens, etc) weird.

 

[slayher]

Tried to add Smoked Glass-esque theme v1.5.2. Boot loop...... And guess who didn't backup Genesis... Also switched to P3Droid kernel.

?????? Just re-booted and everything was saved (applications, screens, etc) weird.

Sounds like a bad install of the smoked glass /shrug

**ETA**
I take that back, Smoked glass v1.5.2 is based off 5.0.6.2, so you tried to flash an older Rom over a newer one, I am sure some stuff with the framework was not compatible, and thats why you got boot loops. Why it went back after a reboot, no idea

 

[Redflea]

Hmmm....tried 30fps only and also locked up and then rebooted spontaneously.

Not normal...also noticing that when I launch the camera the first time it makes the sounds that indicates it's launching but it never launches, the second time it does launch.

Set fps back and things work fine again...

Just me?

Anyone else with similar issues if you try the fps or bit rate hacks?

I have the same problem. If I remember correctly, some devs had the same prob going too high with the fps, so it's not just you..lol

I was able to use 30fps and 80000 changes without an issue . I did it in the Genesis build and also the plain test1 build and both hacks worked just fine . Granted I didn't record alot of video , but about 30 seconds and played it back properly.

Odd...maybe one of those issues similar to kernels working for some and not for others.

 

[bodean]

Noticed no wireless tether in this ROM.
Will that be added soon?

 

[LrdElderon]

Hi slayher, I've been a bit out of the loop lately. Haven't been on the koush irc chan for a bit (personal issues and stuff going on) but I checked on the cm forums looking nextheme since it's gone

(found it, really needs to go back on RM imo. Hax seemed to do ok and manup456 as awesome as he is seems to have a bit much on his plate. should have just kept hax as the droid port maintainer unless he didn't want to anymore)

anyways, so I stumbled across your rom+theme. Was a bit hesitant. I like to stick with the pure CM rom build and just theme it and I didn't know how or what changes you made in the source when you built it, but my 506-2 + nextheme was starting to really bog down and I was itching to test a 507 test out.

Frankly I'm floored. I backed up wiped everything and installed. I'm using the 1ghz 7 slot kernel and this thing just flies. I don't know if it's the theme, or just 507 or what but it just seems like responsiveness went up like 5 notches. Very nice rom. Hope to see it updated for stable 507.
----------------------------------------------

Ok, now question. I see a big thing for this was that you compiled it and the kernel to have compcache. Has that been fixed or even worth using? Last time people were using it there were problems all over the place, especially I believe a memory leak where the phone would get exponentialy slower as you used it. I haven't heard anything since then. I think cyanogen mentioned it wasn't worth using... or at least not yet.

What are your experiences with it on? I'm running without it and with autokiller helping clear memory im running idle at 60-70MB free and with apps 30-40mb. Haven't really seen a need for extra cache.

 

[slayher]

Noticed no wireless tether in this ROM.
Will that be added soon?

Its there, the app should even be there, if its not, D/L it and it will work.

Hi slayher, I've been a bit out of the loop lately. Haven't been on the koush irc chan for a bit (personal issues and stuff going on) but I checked on the cm forums looking nextheme since it's gone

(found it, really needs to go back on RM imo. Hax seemed to do ok and manup456 as awesome as he is seems to have a bit much on his plate. should have just kept hax as the droid port maintainer unless he didn't want to anymore)

anyways, so I stumbled across your rom+theme. Was a bit hesitant. I like to stick with the pure CM rom build and just theme it and I didn't know how or what changes you made in the source when you built it, but my 506-2 + nextheme was starting to really bog down and I was itching to test a 507 test out.

Frankly I'm floored. I backed up wiped everything and installed. I'm using the 1ghz 7 slot kernel and this thing just flies. I don't know if it's the theme, or just 507 or what but it just seems like responsiveness went up like 5 notches. Very nice rom. Hope to see it updated for stable 507.
----------------------------------------------

Ok, now question. I see a big thing for this was that you compiled it and the kernel to have compcache. Has that been fixed or even worth using? Last time people were using it there were problems all over the place, especially I believe a memory leak where the phone would get exponentialy slower as you used it. I haven't heard anything since then. I think cyanogen mentioned it wasn't worth using... or at least not yet.

What are your experiences with it on? I'm running without it and with autokiller helping clear memory im running idle at 60-70MB free and with apps 30-40mb. Haven't really seen a need for extra cache.

Lrd I am very happy to hear your words about my ROM. I appreciate your feedback. And Yes it will be updated for full 5.0.7 when its released.

As for the compcache, it has received some improvement, and appears to be working well now. I know that Cyanogen has already committed it to the N1 builds of CM. I have been using it since my first compile of the source, and have not seen any issues with it whatsoever.

I have been playing with JIT too, but its still just too unstable for 2.1, but it looks like 2.2 will breathe some new life into it. I will be happy when the 2.2 source gets released.

 

[bodean]

Noticed no wireless tether in this ROM.
Will that be added soon?

Its there, the app should even be there, if its not, D/L it and it will work.

Hi slayher, I've been a bit out of the loop lately. Haven't been on the koush irc chan for a bit (personal issues and stuff going on) but I checked on the cm forums looking nextheme since it's gone

(found it, really needs to go back on RM imo. Hax seemed to do ok and manup456 as awesome as he is seems to have a bit much on his plate. should have just kept hax as the droid port maintainer unless he didn't want to anymore)

anyways, so I stumbled across your rom+theme. Was a bit hesitant. I like to stick with the pure CM rom build and just theme it and I didn't know how or what changes you made in the source when you built it, but my 506-2 + nextheme was starting to really bog down and I was itching to test a 507 test out.

Frankly I'm floored. I backed up wiped everything and installed. I'm using the 1ghz 7 slot kernel and this thing just flies. I don't know if it's the theme, or just 507 or what but it just seems like responsiveness went up like 5 notches. Very nice rom. Hope to see it updated for stable 507.
----------------------------------------------

Ok, now question. I see a big thing for this was that you compiled it and the kernel to have compcache. Has that been fixed or even worth using? Last time people were using it there were problems all over the place, especially I believe a memory leak where the phone would get exponentialy slower as you used it. I haven't heard anything since then. I think cyanogen mentioned it wasn't worth using... or at least not yet.

What are your experiences with it on? I'm running without it and with autokiller helping clear memory im running idle at 60-70MB free and with apps 30-40mb. Haven't really seen a need for extra cache.

Lrd I am very happy to hear your words about my ROM. I appreciate your feedback. And Yes it will be updated for full 5.0.7 when its released.

As for the compcache, it has received some improvement, and appears to be working well now. I know that Cyanogen has already committed it to the N1 builds of CM. I have been using it since my first compile of the source, and have not seen any issues with it whatsoever.

I have been playing with JIT too, but its still just too unstable for 2.1, but it looks like 2.2 will breathe some new life into it. I will be happy when the 2.2 source gets released.

Where do I download the wireless tether app?