So am i the only one here that notices that there hasn't been an update for a ROM in about a month? What's been going on?
Not really. IHO is still alive and well. Some of the froyo roms are at end of life and are considered more or less finished (Harmonia and Bumblebee to name a couple).
Sent from my LG-VM670 using Tapatalk
I don't think it helped that the kernel site was hacked and has been down...?
We are all waiting for kernel.org to be back up, kinda hard to build without source.
Some hackers must sit around and think "Who can I piss off today? I know, most of the android dev community." Some hackers just suck.
Sent from my VM670 using XDA App
This explains a lot.. I've been waiting for an update on IHO for a while
Sent from my LG-VM670 using xda premium
Thanks for the information I had no idea kernel.org got hacked.
Sent from my LG-VM670 using Tapatalk
It is hard waiting for kernel.org to get back up, but I'm more than willing to wait it out patiently. We are talking about the basis to the entire Linux community here, not just Android. While we are pretty sure the hackers couldn't have gotten anything in that wouldn't be noticed due to the inherent nature of the repository system, it is prudent that they do such dilligent work checking everything out to be certain. Imagine if someone was able to insert malicious code at the basis of the kernel's distribution system, botnets that instantly compromise millions of computers, all user data compromised the moment you update your system, the imaginary horror stories are all too real possibilities.
Go outside, fix that garage door, paint that fence, or at least take down last year's xmas lights. Kernel.org will be back up soon enough, and we can all go back to worrying about which color looks best on our phones buttons.
@JerryScript:
I'm guessing you didn't get the codaurora repo patched into your cm7 build system like you mentioned you were going to try?
I bet it's murder to patch CAF source addresses into the repo manifest instead of kernel.org, huh?
bummer.
that blog link you posted over in the build-your-own-rom thread on AC worked great for codeaurora by itself, which I appreciate greatly since I was already working with that before kernel.org bit the big one. then I couldn't sync it for a while until you pointed me the way.
bigsupersquid said:
@JerryScript:
I'm guessing you didn't get the codaurora repo patched into your cm7 build system like you mentioned you were going to try?
I bet it's murder to patch CAF source addresses into the repo manifest instead of kernel.org, huh?
bummer.
that blog link you posted over in the build-your-own-rom thread on AC worked great for codeaurora by itself, which I appreciate greatly since I was already working with that before kernel.org bit the big one. then I couldn't sync it for a while until you pointed me the way.
Click to expand...
Click to collapse
Blarf told me that CAF was to much of a mess to rely on. I'm currently syncing using TI's omapzoom, will let you know if I get a successful build environment setup.
Edit-- There is an easier way than manually patching the mirror, just use the following:
Code:
$ repo init -u git://github.com/inferiorhumanorgans/android.git -b gingerbread --repo-url=git://git.omapzoom.org/tools/repo.git
Notice the --repo-url appended to the normal init line, that will do all the patch magic for you. All you have to do is change the remote.
Big thanks to Sanghee Kim for posting this:
https://groups.google.com/forum/#!topic/repo-discuss/r0wkGaloA5k
@jerryscript I would highly suggest making your own thread with the above information just to make sure all of the devs see. Might help them out a little
Sent from my LG-VM670 using Tapatalk
gannon5197 said:
@jerryscript I would highly suggest making your own thread with the above information just to make sure all of the devs see. Might help them out a little
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
I plan on it, as soon as I finish a successful compile.
Sorry I hijacked your thread, to answer your op, should have some new builds soon.
Related
Just thought some might be interested in this (so sue me, i had to ask it):
http://nookdeveloper.zendesk.com/en...-updated-1-2-source-code?page=1#post_20056491
We will be publishing the updated source in the coming weeks. Thanks for your patience.
Click to expand...
Click to collapse
It will be interesting to see what their new source brings, and what we can use from it. Here is hoping that it is sooner rather than later...
EDIT: Well, i am happy to say it didn't take long.. have at it here: http://images.barnesandnoble.com/PResources/download/Nook/source-code/nookcolor-source-code.zip
Awesome news! The faster we can get dalingrin the updated kernel source the better!
Does complying with the gpl allow for a reasonable delay? Because once you get into grey areas like that, what's reasonable? 2 weeks? 3 months?
Obviously they have the source already, so I don't understand when companies release it some time afterwards.
Aye. I hate the "weeks" portion.. given that its out, i dont think its unfair to demand it now. As it is though, i think the GPL gives 60 days (??) for them to publish the code though, so it may be a while.
Not sure if I don't understand the complexities or everything all the devs here do, but what are the possibilities of the deeper-blue Honeycomb ROM being updated to use a modified version of the 2.2 Nook Color kernel instead of the current 2.1 Nook Color kernel? I assume this would help in getting some items like Flash video etc working properly in the Honeycomb ROM.
Or is the goal still to wait for whenever the 3.0 honeycomb full source is released? Just thinking out loud. Interested to see what others have to say.
ArmitageID said:
Not sure if I don't understand the complexities or everything all the devs here do, but what are the possibilities of the deeper-blue Honeycomb ROM being updated to use a modified version of the 2.2 Nook Color kernel instead of the current 2.1 Nook Color kernel? I assume this would help in getting some items like Flash video etc working properly in the Honeycomb ROM.
Or is the goal still to wait for whenever the 3.0 honeycomb full source is released? Just thinking out loud. Interested to see what others have to say.
Click to expand...
Click to collapse
There isn't much an updated kernel will do to help the Honeycomb SDK.
I don't see any schedules mentioned in the GPL http://www.gnu.org/licenses/gpl.html.
bigbob23 said:
I don't see any schedules mentioned in the GPL http://www.gnu.org/licenses/gpl.html.
Click to expand...
Click to collapse
They will do whatever they want until someone sues. What if we lost?
bigbob23 said:
I don't see any schedules mentioned in the GPL http://www.gnu.org/licenses/gpl.html.
Click to expand...
Click to collapse
I may have been wrong (and will happily say its not the first time); but i did do some reading and found this: http://gplv3.fsf.org/wiki/index.php/User:ashawley/Making_copyleft_work_with_implied_compliance
Not sure if it is totally relevant though..
Source Code
I got this:
Dear Brandon Bennett,
Thank you for your inquiry.
Barnes and Noble will post the updated source code in the near future.
There is still no specific date yet. The link will be posted under terms
of service on the website.
Please accept our sincere apologies for any inconvenience this may have
caused and we look forward to hearing from you.
Sincerely,
Ella
Customer Service Representative - Digital Support
Barnes & Noble
http://www.bn.com/
Visit our NOOK Support site for the latest updates and downloads at:
http://www.barnesandnoble.com/nook/support/
Click to expand...
Click to collapse
Hopefully the source will help dalingrin, verygreen and fattire cut through the current mysteries with the .32 development kernel for CM7.
Seems like a lot of progress was made without B&N's help (smart developers), but even if only a few optimized drivers can be poached that is better than nothing.
nemith said:
I got this:
Click to expand...
Click to collapse
Thanks for the info. The nook dev board had another update:
Well, if history is a guide, we released source of 1.0 about 2-3 weeks after launch...
Click to expand...
Click to collapse
As i replied, the anxious part of me does not understand any delay really, other than trying to keep the source code away from us "hackers" for as long as possible. The code is obviously in use, so why not release it?
Ah well..
There are probably lawyers hemming and hawing over them releasing it. They probably are trying to ensure that they haven't violated some other patent/copyright in their code which they actually might get sued over.
chadamir said:
There are probably lawyers hemming and hawing over them releasing it. They probably are trying to ensure that they haven't violated some other patent/copyright in their code which they actually might get sued over.
Click to expand...
Click to collapse
Perhaps, but the code is already shipping - its not to say an update can't get pushed out, but just because we can't see the source, doesn't mean current violations are excused.
As it is, the linux kernel is GPL; they can't not release it. So again, i am still frustrated at the hold up...
Probably just the usual corporate speed. They don't like to publish anything before they have to, if only for liability and exposure. Probably the last thing on the rollout list, too.
poofyhairguy said:
Hopefully the source will help dalingrin, verygreen and fattire cut through the current mysteries with the .32 development kernel for CM7.
Seems like a lot of progress was made without B&N's help (smart developers), but even if only a few optimized drivers can be poached that is better than nothing.
Click to expand...
Click to collapse
We are actually very close to having a good .32 kernel already. Some of us have been using .32 full time I think. Verygreen did most of the work on the port. He scrapped my .32 work and started over.
We only need a few updated drivers from them and we'll be good. So I expect a prompt release once we have B&N source.
dalingrin said:
We are actually very close to having a good .32 kernel already. Some of us have been using .32 full time I think. Verygreen did most of the work on the port. He scrapped my .32 work and started over.
We only need a few updated drivers from them and we'll be good. So I expect a prompt release once we have B&N source.
Click to expand...
Click to collapse
Rock on good sir.. That sounds most exciting indeed!
Perhaps a silly question, but to the end user- what will the difference be between the current and .32 kernel? Faster/better/stronger/able to make cappuccinos?
dalingrin said:
We are actually very close to having a good .32 kernel already. Some of us have been using .32 full time I think. Verygreen did most of the work on the port. He scrapped my .32 work and started over.
We only need a few updated drivers from them and we'll be good. So I expect a prompt release once we have B&N source.
Click to expand...
Click to collapse
I was actually using it for a while. Just needed more clock/governor steppings and the weird "broken SD" and battery fixed, as you already know. It is flying though.
Edit: forgot about sound
Nburnes said:
I was actually using it for a while. Just needed more clock/governor steppings and the weird "broken SD" and battery fixed, as you already know. It is flying though.
Edit: forgot about sound
Click to expand...
Click to collapse
The clock/governor issue is because only the performance governor is compiled into the kernel right now. The broken SD warning is mostly fixed and I believe the same for the battery.
Hey Guys,
I have been wondering why hasnt any dev(s) setup CI anywhere? I see tons of devs doing constant checkin and daily even hourly build on different roms however the end users are stuck with having to install SVN tools download the source compile and create a build? Cant we automate this process using continuous integration where we create a build script that upon each commit/checkin a build script is kicked off. Compiles the new rom zips/signs it and published it to a host somewhere that the end users (us) can just download? I am sure this would save a lot of headaches and time for everyone. Also at part of continuous integration you can also do things like setup build verfication sets (usually unit tests) to verify nothing was broken in the rom before a publish happens. This would also help to increase the quality and reduce bugs in each build.
Thoughts?
Nooooo don't post in Dev, you will be trolled. And yea nice idea btw.
Sent from my PG86100 using XDA App
Where the link at? Really wanna try it man
Sent from my super 3d running Viper RC1.3
while a nice idea .. but wrong section ..
Anyways back on topic. I think there is a script to do this burning don't think it would be as extreme as every commit. The problem is is that devs don't just make one commit at a time. It could be several in 1 min. If so it could overload the buildbot. Its better to keep it nightly to we can test more at one time and we make sure the devs make the edits they want.
Sent from my PG86100 using XDA App
clark44 said:
Off topic but really dude? I see you posting the same **** in every thread in the dev section that doesn't belong. Just because u have that recognized developer status doesn't mean u can go around ripping on users. I'm a dev to you don't see me trolling these threads. Don't reply to this just read it.
Anyways back on topic. I think there is a script to do this burning don't think it would be as extreme as every commit. The problem is is that devs don't just make one commit at a time. It could be several in 1 min. If so it could overload the buildbot. Its better to keep it nightly to we can test more at one time and we make sure the devs make the edits they want.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Appreciate the feedback Clark. I know for a fact you can configure each CI tool differently perhaps an hourly instead of commit based would be more ideal? The goal of my suggestion was really three fold. To reduce the bugs in each build, To implement unit tests in each build that could kick off to verify the build and functionality ensuring nothing got broken in the last series of commits and to get signed builds that are more stable out to the community faster. Rather than having to rely on the end user to figure out SVN. I notice there are tutorials on using SVN in here. Wouldnt that be in the wrong section too? What does that have to do with direct developing? SVN is merely version control? Anyways I believed my thread was directly target to development and all ROMs especially those that have team collaboration. I am sorry that if people dont agree and feel that I started this thread in the wrong forum. However I did want to make sure that it was visible to developers so that they would see it and possibly think it over as in the long wrong I believe it would make there lives easier. However I am sure the flaming will continue....
I think this is a horrible idea. If you don't have the ability to learn to checkout and export an svn repository, than you shouldn't be playing with an experimental nightly build. You see all the people who have issue's with STABLE builds because of stupid things like loading too many apps into memory? Imagine how many stupid questions would flood the nightly threads if there was an automated nightly build.
DeMiNe0 said:
I think this is a horrible idea. If you don't have the ability to learn to checkout and export an svn repository, than you shouldn't be playing with an experimental nightly build. You see all the people who have issue's with STABLE builds because of stupid things like loading too many apps into memory? Imagine how many stupid questions would flood the nightly threads if there was an automated nightly build.
Click to expand...
Click to collapse
This man knows what's up.
Hey guys i was wondering if anyone could point me in the right direction about building AOSP or CM for a new device HTC ONE V. i did do a search but couldnt find anything that fitted what i needed to know. so i appologize if i overlooked something.
thanks
-Lloir
Lloir said:
Hey guys i was wondering if anyone could point me in the right direction about building AOSP or CM for a new device HTC ONE V. i did do a search but couldnt find anything that fitted what i needed to know. so i appologize if i overlooked something.
thanks
-Lloir
Click to expand...
Click to collapse
Does the device have a device git yet?
If not, I am very interested in what others will answer
If it does, then just clone that git into [SOURCE DIR]/device/[YOUR BRAND]
Sent from my Galaxy Nexus using Tapatalk 2
mDroidd said:
Does the device have a device git yet?
If not, I am very interested in what others will answer
If it does, then just clone that git into [SOURCE DIR]/device/[YOUR BRAND]
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
nope no git for it...
btw im not after anyone to hold my hand etc, just want pointing in the right direction and then sort it myself
I'm pretty much in the same shoes as you OP, except with the LG Optimus Elite.
If you are like me and this is your very first time developing i would think you'd need to look here http://htcdev.com/devcenter/downloads and study the source code.
As for other details, just as lost as you not to mention each phone is a different beast making it harder for devs to give us a one size fits all answer.
How do people start device gits, is something I also wanna know..
Maybe you could ask Kousch? He has all device and/or vendor folders...
Sent from my Galaxy Nexus using Tapatalk 2
WhisperPntr said:
I'm pretty much in the same shoes as you OP, except with the LG Optimus Elite.
If you are like me and this is your very first time developing i would think you'd need to look here http://htcdev.com/devcenter/downloads and study the source code.
As for other details, just as lost as you not to mention each phone is a different beast making it harder for devs to give us a one size fits all answer.
Click to expand...
Click to collapse
tried that way, but it just went to htc.com/uk for some reason :/
Where can we get the other proprietary binaries besides those Nexus S and Galaxy Nexus?
Ok here is what I would.
1. Get a VERY detailed breakdown of your phone's specs. I.E. processors, GPU, etc, etc.
2. Find as many phones as you can that are as similar to your phone as possible.
3. Find out which one of those phones are supported by CM9, AOKP, etc.
4. Pull down their device folders and start your modifications off from that.
You are going to need someone to do the kernel however and I have no idea where to even start with that. That's still on my "to learn" list!
It takes a LONG time and a lot of scary moments with your phone, but I'm pretty close to getting my first "alpha" build here of CM9 myself!! And gosh is it a awesome feeling!
I plan to build Cyanogenmod 10 from source, however I have a few questions.
When compiling the kernel from HTC sources, I get two warnings along the line of "warning: (ARCH_MSM_KRAITMP && ARCH_MSM_CORTEX_A5)." I am assuming these are safe to ignore? Other than, it builds and completes fine.
I've never built from source any roms (and for that matter have only done minor programming some time ago), however I have an extensive experience in programming and want to give it a shot.
Is there any reason why it is not possible to build an unofficial port? Wouldn't having the kernel sources from HTC make the job easier? Anyone try this yet or have experience with porting to new devices?
I have next to no programming/hardware/software modding experience but I believe some devs are working on the RIL (radio interface layer) for this phone before they get a working CM10 on the DNA...
I could be completely wrong but just chiming in lol
You can probably build it and get it booting without too much hassle. But you won't have any connection whatsoever. That's where the ril comes in. But it hasn't been cracked yet, beck, idk if anyone's even working on it atm.
Sent from my HTC6435LVW using xda app-developers app
drewX2 said:
I plan to build Cyanogenmod 10 from source, however I have a few questions.
When compiling the kernel from HTC sources, I get two warnings along the line of "warning: (ARCH_MSM_KRAITMP && ARCH_MSM_CORTEX_A5)." I am assuming these are safe to ignore? Other than, it builds and completes fine.
I've never built from source any roms (and for that matter have only done minor programming some time ago), however I have an extensive experience in programming and want to give it a shot.
Is there any reason why it is not possible to build an unofficial port? Wouldn't having the kernel sources from HTC make the job easier? Anyone try this yet or have experience with porting to new devices?
Click to expand...
Click to collapse
You will probably get a couple errors during the build, nothing to worry about. If you get an error and the build stops then you know you have a problem.
Also, we have the kernel source from HTC. Building custom kernels is a necessary step before we can build CM, but it doesn't really make anything easier. Like Bigandrewgold said, the RIL is the most important missing link at this point.
I wish you the best on this project, and you have a great community here of people who can help you out.
I myself would love to test out CM on this beast, ril or not. It'd be nice to have a build ready that we could just drop a kernel into.
Sent from my HTC6435LVW using Tapatalk 2
Last update for CM10 is 29.12 ?
And it went straight from a nightly to "stable" build.
It is quite silly to abandon one project if yet to be completed abruptly for another.
So like 10.1 will only get three quarters completion and dumped when 4.2.2 aosp code is released?
This is quite frankly utter madness.
A very good enough reason perhaps why ios versions are better polished.
Sadly disappointing.
Sent from my SCH-I905 using xda app-developers app
nothing was abandoned. no stable release exists for this tab suite (until all bugs are squashed) as of yet. i purposefully switched to cm-10.1 for nightly on this tab suite (after various feedback/observations from people).
either move, or wait till the remaining bugs are squashed (first in cm-10.1, which i will then also try my best to apply to cm10) for a possible stable release.
if you want faster progress, start working on it. any help which re-mediates bugs which are device specific are welcomed. this is not closed source. all of this is out in the open. if you want it, make it happen.
your tab was abandoned at official ICS. anything greater is a plus and a gift as far as i'm concerned and is willed by my passion to keep working on it (when everyone else has bailed).
Serpentene said:
A very good enough reason perhaps why ios versions are better polished.
Sadly disappointing.
Sent from my SCH-I905 using xda app-developers app
Click to expand...
Click to collapse
Please go to ios if you expect things to be done for you. This is not constructive at all considering that you are bringing nothing to the table. As pershoot said, it is his passion is why we see anything past the gimped TW ICS that was official release by Samsung. Not only is Samsung done with our Tab, so is Google. pershoot worked his butt off to bring compatibility to the code that dropped support for us.
pershoot said:
nothing was abandoned. no stable release exists for this tab suite (until all bugs are squashed) as of yet. i purposefully switched to cm-10.1 for nightly on this tab suite (after various feedback/observations from people).
either move, or wait till the remaining bugs are squashed (first in cm-10.1, which i will then also try my best to apply to cm10) for a possible stable release.
if you want faster progress, start working on it. any help which re-mediates bugs which are device specific are welcomed. this is not closed source. all of this is out in the open. if you want it, make it happen.
your tab was abandoned at official ICS. anything greater is a plus and a gift as far as i'm concerned and is willed by my passion to keep working on it (when everyone else has bailed).
Click to expand...
Click to collapse
I respect your skills and passions..but
The methodology used here is illogical at best and quite confusing at worst.
BY introducing 10.1 in the same chain of nightly sequences this too is causing a havoc as well.
Users are assuming by being led to assume..this is the continued CM10 build chain of updates.
Sent from my SCH-I905 using xda app-developers app
Serpentene said:
I respect your skills and passions..but
The methodology used here is illogical at best and quite confusing at worst.
BY introducing 10.1 in the same chain of nightly sequences this too is causing a havoc as well.
Users are assuming by being led to assume..this is the continued CM10 build chain of updates.
Sent from my SCH-I905 using xda app-developers app
Click to expand...
Click to collapse
think of it this way,
i enabled this tab to allow for the latest updates, one in which it would never see otherwise. this allows me to work on the latest and the not so latest, as it pertains to the device, in the public eye to allow for collaboration and feedback.
you don't want it, you do not have to flash. nothing is forced upon you.
pershoot said:
think of it this way,
i enabled this tab to allow for the latest updates, one in which it would never see otherwise. this allows me to work on the latest and the not so latest, as it pertains to the device, in the public eye to allow for collaboration and feedback.
you don't want it, you do not have to flash. nothing is forced upon you.
Click to expand...
Click to collapse
You are absolutely right, I'm very pleased to have Your versions available to flash. We who are not so talented, should be grateful (and maybe also a little bit more humble ) Thank You! :good:
Just want to sat Thankyou to pershoot, with CM10.1 my tab is better than it has been in ages. Loads of respect for the talented people who keep our devices alive.
Sent from my GT-P7510 using Tapatalk 2
The comment is not implied to be antagonistic but rather to question the logic and intentions set forth by the developer.
We all most certainly appreciate the passions of Pershoot and his work.
I personally thank him for answering.
When his fan base and other developers like him respect the work enough to adopt and invest in its contribution it then
Initiates itself into the hands of the global user community.
The community becomes dependant upon its completion. This is an ethical responsibility.
All reputation and notoriety is won or lost in this human principle.
Sent from my SCH-I905 using xda app-developers app
Serpentene said:
The comment is not implied to be antagonistic but rather to question the logic and intentions set forth by the developer.
We all most certainly appreciate the passions of Pershoot and his work.
I personally thank him for answering.
When his fan base and other developers like him respect the work enough to adopt and invest in its contribution it then
Initiates itself into the hands of the global user community.
The community becomes dependant upon its completion. This is an ethical responsibility.
All reputation and notoriety is won or lost in this human principle.
Sent from my SCH-I905 using xda app-developers app
Click to expand...
Click to collapse
Seriously...?
Pershoot,
Thanks a million for all the amazing work you and all the other developers are doing,
If you want to change version every week I'll just say "thank you". :good:
Serpentene said:
The comment is not implied to be antagonistic but rather to question the logic and intentions set forth by the developer.
We all most certainly appreciate the passions of Pershoot and his work.
I personally thank him for answering.
When his fan base and other developers like him respect the work enough to adopt and invest in its contribution it then
Initiates itself into the hands of the global user community.
The community becomes dependant upon its completion. This is an ethical responsibility.
All reputation and notoriety is won or lost in this human principle.
Sent from my SCH-I905 using xda app-developers app
Click to expand...
Click to collapse
Did you seriously just say this?
Read the post linked in my signature please.
One should never feel they become 'dependent' on whether or not a developer who is not being paid for his time and does this work for fun 'finishes' development on a ROM based on your personal standard. If you feel that way you should probably not be modding your devices in the first place. XDA does not exist so you can imply its users have an ethical responsibility to give you what you need to make your device cooler than someone else's... It exists to inspire you to learn how to do this stuff and give back. It is a hobby, not a responsibility, and you acknowledge that fact when you flash the work.
Honestly, if you want to see something done and don't feel like waiting for the developer to address your particular concern, you have two options:
1) be prepared to donate funds in the hundreds of dollars per hour to pay the dev's bills and maybe the dev will focus on your needs
2) do it yourself...no one's stopping you
Sent from my Infamous Tab.
+1
Really!? Really!?... And you wonder why we (developers) leave...
Pershoot has done more for this device the ANYONE ! instead of complaining, how about you say thank you and maybe send him a donation.
How to get souce code?
pershoot said:
nothing was abandoned. no stable release exists for this tab suite (until all bugs are squashed) as of yet. i purposefully switched to cm-10.1 for nightly on this tab suite (after various feedback/observations from people).
either move, or wait till the remaining bugs are squashed (first in cm-10.1, which i will then also try my best to apply to cm10) for a possible stable release.
if you want faster progress, start working on it. any help which re-mediates bugs which are device specific are welcomed. this is not closed source. all of this is out in the open. if you want it, make it happen.
your tab was abandoned at official ICS. anything greater is a plus and a gift as far as i'm concerned and is willed by my passion to keep working on it (when everyone else has bailed).
Click to expand...
Click to collapse
I want to get the 10.1 source code to compile by myself. Can you tell me how to get total source code to compile and produce zip file to flash my tab?
Thanks.
wooxz said:
I want to get the 10.1 source code to compile by myself. Can you tell me how to get total source code to compile and produce zip file to flash my tab?
Thanks.
Click to expand...
Click to collapse
http://wiki.cyanogenmod.org/index.php?title=P4wifi_Info
This wasn't a complaint or rant. It is a simple question and answer of completing what the developer started.
I can ask without the need for stroking theatrics..
Sent from my SCH-I905 using xda app-developers app
Serpentene said:
This wasn't a complaint or rant. It is a simple question and answer of completing what the developer started.
I can ask without the need for stroking theatrics..
Sent from my SCH-I905 using xda app-developers app
Click to expand...
Click to collapse
you went from asking to a diatribe about philosophies and how I need to live up to one's expectations. put yourself in my shoes, then re-read what you wrote and the tact that was followed.
while i'm a very patient and passionate person, i only have one brain, two hands and only so much free time.
as stated prior, roll up your sleeves and start working on it. that is how you can make a difference and understand what a person like me goes through supporting X amount of users across X amount of devices.