The last stage of Pulse development

[Guest DanWilson]

In all seriousness (well, the laptop seems brighter in all ways with Ubuntu), what should I install / download / read before any development begins. I have a full weekend ahead, so want to at least build a ROM that is ready and waiting. (IE, compiling a ready-made ROM)

Also - when do we start? :P

Also - would a website help?

Or maybe a group name? Like VILLAINRom has a name, we need a name.

Nothing Pulse related, we might move on. Dev-wise.

I vote PARTAYDevTeam.

Which is full of awesome. I'll make ringtones for the ROM if that is the name.

Edited November 26, 2010 by DanWilson

[Guest JimJam707]

In all seriousness (well, the laptop seems brighter in all ways with Ubuntu), what should I install / download / read before any development begins. I have a full weekend ahead, so want to at least build a ROM that is ready and waiting. (IE, compiling a ready-made ROM)

Also - when do we start? :P

Also - would a website help?

Or maybe a group name? Like VILLAINRom has a name, we need a name.

Nothing Pulse related, we might move on. Dev-wise.

I vote PARTAYDevTeam.

Which is full of awesome. I'll make ringtones for the ROM if that is the name.

That's pretty cool.

I have no dev skills and no pulse. I could make a logo though? :D

[Guest DanWilson]

That's pretty cool.

I have no dev skills and no pulse. I could make a logo though? :P

Nice.

I have no dev skills, but can cut music up and make awesome comments in the source.

:D

Any other names people? Might make the gmail account and website. Cos that'll be goooooooood.

[Guest JimJam707]

Nice.

I have no dev skills, but can cut music up and make awesome comments in the source.

:P

Any other names people? Might make the gmail account and website. Cos that'll be goooooooood.

Use google wave.

It's not dead. And it's pretty good.

[Guest AntonioPT]

Jamie and Dan,

I only proposed this new port of CM because Tom had been inactive for a long time and we didn't know when he was coming back. Now that he's back and said that he will upload the source in a short time, I don't think there's much point in this project of porting CM again.

A new Pulse/U8230 owner's guide would be a better ideia, IMHO. The old one is very outdated and doesn't include Cyanogen. What do you guys (and everyone else) thinks about that?

[Guest AntonioPT]

Yah, but I think the Pulse needs a dev / dev team of sorts to keep us going.

Well, but I am no dev and neither is any of the people who posted here (I think...).

I know we need a team / a dev to keep the Pulse community going, but right now we've got one real dev (excluding ROM cookers like JohnPorter and twrock): Tom G. And we all know that, at some point in time, he's going to leave us and jump into the San Fran bandwagon :P

[Guest spanner44]

Well, but I am no dev and neither is any of the people who posted here (I think...).

I know we need a team / a dev to keep the Pulse community going, but right now we've got one real dev (excluding ROM cookers like JohnPorter and twrock): Tom G. And we all know that, at some point in time, he's going to leave us and jump into the San Fran bandwagon :P

So should we all start jumping now ? or wait and see if there is another dev willing to take up the challenge ?

[Guest DanWilson]

Well, but I am no dev and neither is any of the people who posted here (I think...).

I know we need a team / a dev to keep the Pulse community going, but right now we've got one real dev (excluding ROM cookers like JohnPorter and twrock): Tom G. And we all know that, at some point in time, he's going to leave us and jump into the San Fran bandwagon :P

But we all want to learn. Whether or not you want to, I don't know. But I do. I'm sure others in this thread want to.

So should we all start jumping now ? or wait and see if there is another dev willing to take up the challenge ?

Hence us. Wanting to learn.

[Guest spanner44]

But we all want to learn. Whether or not you want to, I don't know. But I do. I'm sure others in this thread want to.

I would love to be able to learn, but I am afraid that my capabilities would be of no use to this development as I am still in the very early stages, being very new to Android.

If there were more development going on here, then it would be easier, but sadly most have left and to try and find any useful advice, tips etc to expand our knowledge, takes hours trying to go through large unmanageable threads.

[Guest DanWilson]

I would love to be able to learn, but I am afraid that my capabilities would be of no use to this development as I am still in the very early stages, being very new to Android.

If there were more development going on here, then it would be easier, but sadly most have left and to try and find any useful advice, tips etc to expand our knowledge, takes hours trying to go through large unmanageable threads.

True dat.

I don't know anything about developing Android yet. So I need to start somewhere.

[Guest AntonioPT]

So should we all start jumping now ? or wait and see if there is another dev willing to take up the challenge ?

I didn't say that we should do that. I'm probably using this phone for a year or more, so the more time this community lives, the better for me and for everyone else.

I'm no dev, and even if I tried to learn how to do the same work Tom G has been doing, it would probably take me a lot of time and a lot of effort. I try to learn things as often as I can, but porting CM from scratch, knowing that Tom G is going to upload the source in no time, it's too much for me...

Another person may be up to the job, and I'll support him/her in every way I can. (her? probably 99% of us is male :P)

But we all want to learn. Whether or not you want to, I don't know. But I do. I'm sure others in this thread want to.

I want to learn. Of course I want to learn! But believe me, it's no easy job. I downloaded the entire CM source (3 GB), and the second I looked into it, I saw that it would be waaay too difficult and time-consuming.

There's next to ZERO documentation on porting CM to a new device!

If you want to spend months (assuming you have the same skills than me, which are, Android-wise, low) trying to re-port CM to our devices, when Tom G will release the source in the next few days/weeks, be my guest. Seriously. I'll help you in any way I can.

When we have Tom's source, we can finally start improving the ROM. One thing is porting. Another thing is just adjusting a few files here and there.

My suggestion, for everyone here, is:

We wait for Tom's source. Once I (or someone else) diff's his source against the official source, we can start releasing frequent ROMs with the latest, best CM code. And of course, if possible, fix the bugs present in the current version (assuming Tom doesn't do that).

Also, we need a new Pulse/U8230 guide. A guide that is easy to understand for newcomers to this forum, but also a guide that provides all the info a user can need.

Cheers,

AntonioPT

[Guest DanWilson]

I didn't say that we should do that. I'm probably using this phone for a year or more, so the more time this community lives, the better for me and for everyone else.

I'm no dev, and even if I tried to learn how to do the same work Tom G has been doing, it would probably take me a lot of time and a lot of effort. I try to learn things as often as I can, but porting CM from scratch, knowing that Tom G is going to upload the source in no time, it's too much for me...

Another person may be up to the job, and I'll support him/her in every way I can. (her? probably 99% of us is male :P)

I want to learn. Of course I want to learn! But believe me, it's no easy job. I downloaded the entire CM source (3 GB), and the second I looked into it, I saw that it would be waaay too difficult and time-consuming.

There's next to ZERO documentation on porting CM to a new device!

If you want to spend months (assuming you have the same skills than me, which are, Android-wise, low) trying to re-port CM to our devices, when Tom G will release the source in the next few days/weeks, be my guest. Seriously. I'll help you in any way I can.

When we have Tom's source, we can finally start improving the ROM. One thing is porting. Another thing is just adjusting a few files here and there.

My suggestion, for everyone here, is:

We wait for Tom's source. Once I (or someone else) diff's his source against the official source, we can start releasing frequent ROMs with the latest, best CM code. And of course, if possible, fix the bugs present in the current version (assuming Tom doesn't do that).

Also, we need a new Pulse/U8230 guide. A guide that is easy to understand for newcomers to this forum, but also a guide that provides all the info a user can need.

Cheers,

AntonioPT

I'll perhaps draft up a guide if you want. What would you say is important?

[Guest AntonioPT]

I'll perhaps draft up a guide if you want. What would you say is important?

The "return to 1.5" and such parts of the old guide are ok, IMHO.

Installing CM and FLB are important.

Also, distinguishing between U8220/30 is important. (If you don't mind I'll do that part as I have a U8230 :D)

Performance tips for CM (jit, compcache, setcpu and the likes)

Whatever you feel it's important :P

When I have time, I'll probably do a video tutorial in how to do what most users want to do (Clockwork/Amon_RA + FLB + A2SD + Swap).

That should be the main thing, as it focuses on the less experienced user.

Thanks for your help Dan :D

[Guest DanWilson]

The "return to 1.5" and such parts of the old guide are ok, IMHO.

Installing CM and FLB are important.

Also, distinguishing between U8220/30 is important. (If you don't mind I'll do that part as I have a U8230 :D)

Performance tips for CM (jit, compcache, setcpu and the likes)

Whatever you feel it's important :P

When I have time, I'll probably do a video tutorial in how to do what most users want to do (Clockwork/Amon_RA + FLB + A2SD + Swap).

That should be the main thing, as it focuses on the less experienced user.

Thanks for your help Dan :D

I don't know any of the performance tips. Except from reboot every so often.

Speaking of which *reaches over to Pulse, reboots*, done.

Also, you're quite welcome. I feel I should give something big to the community.

I might ask Azurren if I can use some of his Ultimate Pulse Owners Guide. Mainly the bits that are OK, like recovery and all the 1.5 stuff.

If by Christmas you haven't made a video, I'll restore my Pulse to 1.5 and take an HD video of the process with my DZ. :D

Wonder where that's hiding just now...

Soooo tired atm.

Still, must soldier on, Clubland in the ears, keyboard in the hands, we have the war of the confusion to fight!

RAWR!

Edited November 26, 2010 by DanWilson

[Guest AdamBaker]

+1

I could live with my pulse with no problems at all if camera and getting stuck with rotation would get fixed in CM. It would be a great final step in Pulse development, and I believe that a lot of people would be happy.

Has anyone seen the rotation bug after setting up swap (I haven't so far)? If you run any apps that listen to the sensor notifications then they still worked for me when it did fail before I configured swap so the rotation failure is somewhere in the higher layers, possibly something running out of memory and getting killed.

[Guest twrock]

Have you tried using vignette? It works fine for me in full 3MP resolution?

But we still need that src, abnd try to get it in official CM development.

Who will PM Tom?

Are you sure you are using the paid version and it is set for the full 3MP resolution?

Can you take multiple pictures, one after another, and have them all turn out good, without any crashes?

The demo version appears to not have 3MP resolution, so I can't test it without buying it. [Edit: And on top of that, the demo version promptly crashed on me the first time I tried to use it! Off to a very bad start.]

The last time I tried a camera app that someone said worked at full resolution, it didn't work for me.

Thanks.

Looks like Tom is "back to work". Maybe something really good will happen! :P

But in any case, getting the Pulse port included in the regular CyanogenMod development is a very good goal.

Edited November 29, 2010 by twrock

[Guest twrock]

+1

Being myself a U8230 owner, I fully understand you. Maybe a new Pulse/U8230 guide is the way to go... :D

BTW, Tom is back! :D

I just finished reading the rest of this thread.

First, to quote Sergeant Schultz, "I know nothing!"

Seriously, I can barely tweak a rom someone else did all the work on. :P I am of no help whatsoever when it comes to development.

But, for the record, I don't have a "Pulse" or a U8230. I've got a "first-generation" CHT8000. :D

Hopefully something is coming soon from Tom G.

Has the front-facing camera gotten any attention at all? I'm guessing most of us never have a use for it (me included), but I've read something around here that leads me to believe it doesn't work.

[Guest twrock]

Has anyone seen the rotation bug after setting up swap (I haven't so far)? If you run any apps that listen to the sensor notifications then they still worked for me when it did fail before I configured swap so the rotation failure is somewhere in the higher layers, possibly something running out of memory and getting killed.

Yes, I had swap working from my first install, and the included Gallery3D app couldn't handle rotation. The replacement Starkos uploaded works fine for me (but I prefer the old, non-3D Gallery app anyway). I don't know why it works for you, but be happy it does! :P

[Guest suriya83]

Has anyone seen the rotation bug after setting up swap (I haven't so far)? If you run any apps that listen to the sensor notifications then they still worked for me when it did fail before I configured swap so the rotation failure is somewhere in the higher layers, possibly something running out of memory and getting killed.

i use swap but i still have the rotation get stuck. i will try to lower the autokill level, lets see what happens... maybe i need some days to tell if something changed

(i have the U8230 with 256MB Ram)

Edited November 29, 2010 by suriya83

[Guest twrock]

i use swap but i still have the rotation get stuck. i will try to lower the autokill level, lets see what happens... maybe i need some days to tell if something changed

(i have the U8230 with 256MB Ram)

Come to think of it, I did have something strange start a couple of days ago with rotation getting stuck. (I think I misunderstood earlier what the point of the post was.)

In my case, I hadn't ever seen it before. Then I installed Calendar Notifier, an app that keeps reminding me if a calendar notification goes off and I don't respond. I set it up to turn on the screen briefly at each notification. But, I keep my phone in my front pocket, turned top down. I found that my phone would be stuck in landscape mode each time after a notification had gone off.

I disabled the "screen-on" feature to see if that is for sure the problem, and so far the problem hasn't repeated. So FWIW, that's what I've seen.

[Guest nitko]

Are you sure you are using the paid version and it is set for the full 3MP resolution?

Can you take multiple pictures, one after another, and have them all turn out good, without any crashes?

The demo version appears to not have 3MP resolution, so I can't test it without buying it. [Edit: And on top of that, the demo version promptly crashed on me the first time I tried to use it! Off to a very bad start.]

The last time I tried a camera app that someone said worked at full resolution, it didn't work for me.

yup, I am using paid version in 3.1MP Normal mode (2048x1536 picture resolution)

I can take as many pictures in a row without any crashes (which happens in other applications).

Version is: Vignette v2010-11-04

[Guest sun lbx]

So do I. For a month already.

Vingette rulez :P

[Guest Poseidonhun]

yup, I am using paid version in 3.1MP Normal mode (2048x1536 picture resolution)

I can take as many pictures in a row without any crashes (which happens in other applications).

Version is: Vignette v2010-11-04

I give it a try and Vignette works fine! :P

So one bug is left for me now, the MAC adress problem.

I cant use the wifi in University, because it using mac filtering. :D

Edited November 29, 2010 by Poseidonhun

[Guest suriya83]

I give it a try and Vignette works fine! :P

So one bug is left for me now, the MAC adress problem.

I cant use the wifi in University, because it using mac filtering. :D

U don't have the problem with rotation getting stuck?

for me this is the most annoying bug

[Guest add.thebad]

and along came gingerbread ;)