Related
I ASK THAT YOU READ ALL THIS BEFORE I GET TO THE FIX, BECAUSE THIS IS A MULTILAYERED TOPIC. I WANT EVERYONE TO READ THIS, NOT JUST DEVS OR SENIORS, BUT ALL THE LURKERS AND MEMBERS WHO'VE NEVER POSTED. I WILL ACCEPT ALL SUGGESTIONS AND IDEAS.
THAT MEANS YOU. AND YOU. AND THATS RIGHT...EVEN YOU!
IN THIS POST, I WILL DISCUSS BRIEFLY MY PLANS FOR THE FUTURE OF MY HERO, HOW I WILL BRING MY SUCCESS TO PHONES AROUND THE USA, HOW I WILL JOIN THE LEAUGES OF DAMAGE, AND FLIPZ, AND ESPECIALLY DARCH, WHO WHILE WATCHED FROM A DISTANCE, WHEN THE TIME CAME FOR IT, BROUGHT ME THE ANSWER. AT THE END, I HAVE A VERY IMPORTANT QUESTION, TO BE FOLLOWED BY THE FIX[EDIT: REALITY; COMING SOON][sooner with your support!]
3 year lurker. xda is the only forum I've taken apart of in the community, and to a small sucess. I've actaully managed to help, learn, and now its time I give back to the community.
I FIRMLY BELIEVE I HAVE THE SKILLS REQUIRED TO BRING SOMETHING NEW TO THE TABLE, AND HAVE ENOUGH TO SPLIT IT BETWEEN EVERY PERSON SITTING AT THAT TABLE. WILL YOU JOIN ME AT THIS TABLE?
If anyone has ever looked at my profile, then you know I've only been a member since March 25th, and have been made a senior in just over a week(not that I'm bragging...). I'm no spammer, all my posts have been legit, and I have actually helped people. I still consider myself a noob, but I do believe I have earned my seniority, and hopefully the support of all the main devs, who have helped me beyond belief, and have responded to any major question I had, especially with what Ive been working on lately.
If you've logged on within the past 2 weeks, and followed my posts at all, then you know that even if I dont know the answer, I offer suggestions, and more importantly support. I distinguish flames, stomp on the trolls, and still manage to bring my ideas to the table, so its time to test and see if I can make these idea's come true.
I cannot do this without your help.
I am now going to quote one the the best devs on this forum, with the fix.
darchstar said:
mountaindont said:
wanna hop over on my trackball fix thread?
im so damn close, i can see the lights!
...get it?
im uploading the directory we gotta mess with now. i just know you can help!!
Click to expand...
Click to collapse
I think you're best bet would be to write an app to keep the trackball light forever on instead of trying to rewrite most of the frameworks and deal with all the dependencies to fix the trackball light.
if you really want to go and make the trackball stay always on by rewriting some code, i'd suggest you first look inside the framework jars with baksmali and find any lines which reference to the trackball, and see if you can somehow manipulate it to constantly echo 1 to the trackball led device in /dev to constantly stay on.
Click to expand...
Click to collapse
If I'm going to start understanding the Android platform to the degree that Darch and co do, the best place to start would be writing my first application (this will expose me to the framework, the commands, and how to manipulate the OS like never before). Something I've looked into, and have tried a couple things.
-keeping in mind, that in all reality, Sprints final release will give the option to decide light or touch responsive...at least, I hope so...-
I get my laptop back tomaro, and I will be studying the SDK to the T, and with the support of you guys, I will write an app to work on any 2.1 ROM, that will give you the option to keep the trackball light on or let it remain light sensitive[beta, first release] and eventually, options that will blow your mind. Things that handcent might incorporate, so you only have to use this app to pimp out the stock messaging app. Speed of flash. Customize vibration. Haptic feedback when clicking the trackball (links, function buttons, or just sitting on your homescreen, and you get that urge to just enjoy the pleasure of your customized vibration.) [future release, always FREE]
I dont know how long it will take me to learn the SDK enough to set something up from nothing and make this farfetched idea. I was hoping that someone could give me the scource code to a related app; handcent would be amazing, but something like Trackball Alert for the nexus one (its something, not nothing :-\) would be cool too. Or if you have programming skills, please, lets team up, I'm reading tutorials now. If I can complete "Hello Android", I'm sure I can make this happen.
THIS IS THE QUESTION THAT I ASK OF THE ENTIRE XDA COMMUNITY (lurkers, seniors, devs, and members who just want to test and give feed back)
WILL YOU SUPPORT ME?
If I ask a question (dont worry, this thread your reading now has gone through four topic changes to avoid clutter, I'll be sticking with this thread for updates, releases, and changelogs -
I might start one more thread to keep up on bugs-) will you help? Will you subscribe and help my idea come to life, and bring a whole new customization option app. Will the main devs take part, seeing as how this app could very well be included in future releases of their ROMS (I'll talk about my ROM idea's in another update) Will the seniors with a sick attitude be able to put their frustrations and rude answers in their pocket while posting in this thread? Bring positive energy in, with advice and sugestions, and crys of "good luck!"?
If its a team effort, its hardly an effort at all.
the basis of what what we have so far. i know what files need to be edited, this time im sure its [sys/class/leds/button-backlight] in this directory, there are sensor files, a "trigger file"(quite sure this will play a major role) that contains a series of commands that seem to tell the backlights and sensors how and when to act. I'm sure apps like Handcent and Trackball alert mess with the same files (and if not, what do they mess with to make these changes? would installing and taking a look at the permissions be a good place to start?). Anyone know how to get in touch with the devs, or some scource code of an app that affects the trackball? This would be a great start.
[/\]
quick rundown of my rom idea's. some of you read my MAJOR INTERNAL MEMORY ISSUE thread, which you all rose magnificently to the occasion, and I couldnt be happier. It was true team work, something I know we can do if we just unite like we did yesterday. You all solved my problem, and have proven to me the members of XDA are capable of anything, especially when united.
the fact is, damages latest leaks are the best platform to build upon, as when the final release surfaces, and we get an official RUU, it will work truely flawlessly. so this is most certainly what we need to base the app off of at first, as its the only one with the closest trackball fix. if darch and flipz n fresh all want to encorporate it into their ROMS, they more than entitled too, as I hope to get help from them in certain areas. my issue with the latest sprint leak: the OS is so big, it leaves you with barely any internal memory, and you pretty much have no choice but to use a2sd. ive never had to use a2sd on my hero, and this is disppointing (damage, this is NOT a shot at you, its a fact, one I plan on helping you adress. im in the middle of working on a cleaner foundation for you to work on). the rom will be fully "sensable" with some tweaks like that of no other. i will build on the foundation you've laid, to create a new foundation for you to build on (once more leaks surface)
[/\]
im off for the day, except for occasionaly visits on my Hero, so please feel free to comment. I'm looking for someone to help build this app, so anyone with app programming skills, PM your GTALK and we can chat about idea's. in the meantime, maybe someone knows a open scource app that would allow us to build off?
dear damage, darch, and flipz, please PM me your GTALK if your interested...although I could understand if your too busy with your ROMS, I dont mind taking on the load, as long as I have your support, and can ask for help. i will not cross the line and ask for the RUU's you've been getting damage, but I would love to hear your plans for future releases, whether or not you might be interested in using my app and perhaps help developing it.
c.a.l.i.n.g. a.l.l. d.e.v.s.
It is light sensitive tested by placing finger over the sensor above the sprint logo (upper right) flicked the track ball it comes on. Hopefully that helps beleive me I know how it is when you ask a question or look for help and you get nothing
mrbook said:
It is light sensitive tested by placing finger over the sensor above the sprint logo (upper right) flicked the track ball it comes on. Hopefully that helps beleive me I know how it is when you ask a question or look for help and you get nothing
Click to expand...
Click to collapse
a quick search in damages.thread (which i hate doing, his threads fill so fast.and questions get buried, right along with the answer) gave me the same conclusion. but the fact is, i want a constant trackball led, and im sure if people had the option, more people would want it too. most view it as a minimal bug, so dont bother. i guess, for me, the other bugs are so minimal that the trackballs led has become the biggest issue.
could someone please help? i spend alot of time on here helping as much as i can, id really appreciate it if someone with the same desired goal could devote some time to it. id be willing to help in any manner.
im sitting in my basement with all the lights out posting this, just to spend time with my long lost tb led.
BUMP
Did you try to turn off the Auto brightness feature for the display to see if this stops the Trackball from not turning on?
dcdave63 said:
Did you try to turn off the Auto brightness feature for the display to see if this stops the Trackball from not turning on?
Click to expand...
Click to collapse
I have auto brightness off and it has no effect on trackball led.....
chfields said:
I have auto brightness off and it has no effect on trackball led.....
Click to expand...
Click to collapse
yes ive been playing with the power control widget since first flash. no joy. thanks for the idea, have anymore?
anyone?
bumpedybumpbump
Trackball Alert
There's a dude from the uk that builds an app for N1 that brings the ability to choose your own color and rate of the trackball lite. Try to send him an email see if he wants to jump in. The app is called Trackball alert. Its says its only for the N1 though.
Hope you can find a solution.
energizer1389 said:
There's a dude from the uk that builds an app for N1 that brings the ability to choose your own color and rate of the trackball lite. Try to send him an email see if he wants to jump in. The app is called Trackball alert. Its says its only for the N1 though.
Hope you can find a solution.
Click to expand...
Click to collapse
yeah ive seen the app. i will make sure to do that, i hope the brits want to help.
im sure us on xda.could find a solution, however.
i really hope sprint doesnt plan on releasing 2.1 like this. id be sorely disappointed.
Believe me, I understand what it's like to have a feature that's important to me and nobody else seems to care about. We all paid good money for these phones, and continue to pay good money every month for service, so I think that gives us each the right to at least ask about the things that we care about. (Well, unless you're trying to use Sprint VVM instead of GV. That's just plain dumb.....)
As far as the trackball light behavior goes, I think your probably screwed. That's something that will most likely have to be changed in the source code of whatever is controlling it. That seems to me like something that's probably coded in at a very low level of the OS itself. (Well, not the OS, actually. The OS is Linux. But it's probably hardcoded into the Android framework.)
As good a job as the rom devs on xda do, it's not like they're actually creating this software. They're just taking what others have created and packaging it in a way that works on our phones. My guess is that the people who can make the change you're asking for work in HTC's offices...
As far as the different colors, good luck. There's a reason that tweak only works on the N1. It's the only phone that has different colored LEDs back there to light up. You can be the best programmer in the world, but you still can't turn on a red light if the only light available is white......
subliminalurge said:
Believe me, I understand what it's like to have a feature that's important to me and nobody else seems to care about. We all paid good money for these phones, and continue to pay good money every month for service, so I think that gives us each the right to at least ask about the things that we care about. (Well, unless you're trying to use Sprint VVM instead of GV. That's just plain dumb.....)
As far as the trackball light behavior goes, I think your probably screwed. That's something that will most likely have to be changed in the source code of whatever is controlling it. That seems to me like something that's probably coded in at a very low level of the OS itself. (Well, not the OS, actually. The OS is Linux. But it's probably hardcoded into the Android framework.)
As good a job as the rom devs on xda do, it's not like they're actually creating this software. They're just taking what others have created and packaging it in a way that works on our phones. My guess is that the people who can make the change you're asking for work in HTC's offices...
As far as the different colors, good luck. There's a reason that tweak only works on the N1. It's the only phone that has different colored LEDs back there to light up. You can be the best programmer in the world, but you still can't turn on a red light if the only light available is white......
Click to expand...
Click to collapse
i exchanged a pm woth regaw, who is working closely with damage in building and testing the leaks. he seems fairly certain its a matter of messing with an xml file. lets cross our fingers for more information.
anyone have any clue what.xml file defines when and how the tb lights up?
mountaindont said:
he seems fairly certain its a matter of messing with an xml file. lets cross our fingers for more information.
Click to expand...
Click to collapse
That could be, too. Will be cool if it is. I'm still working on getting a full understanding of the Android framework, but that could be in an xml file now that I think about it.
That said, I stand by my point that these guys aren't exactly writing software from scratch. There comes a point where they can only do so much with the programs that they're repackaging.
Once that point is reached, it's really not fair or realistic to ask them to do much more until the real developers release new software and it gets leaked again.
subliminalurge said:
That could be, too. Will be cool if it is. I'm still working on getting a full understanding of the Android framework, but that could be in an xml file now that I think about it.
That said, I stand by my point that these guys aren't exactly writing software from scratch. There comes a point where they can only do so much with the programs that they're repackaging.
Once that point is reached, it's really not fair or realistic to ask them to do much more until the real developers release new software and it gets leaked again.
Click to expand...
Click to collapse
i comletely understand what you mean, and whole heartidly agree. damage is getting these leaks from someone and simply modifying for beytter performance, and working out the bugs sprint hasnt quite got ironed out yet.
but!
originally, these 2.1 roms were based on the eris and legend leaks, meaning the devs have a sound understanding of taking the given software and rewriting it to work on the sprint network/our hardware
it can be done, a simple edit of an xml file, and if we team up, i see no reason it couldnt be done, and rather easily at that.
i dp regret i have no knowledge in this regard, but i know its a patch alot of peoe would jump on and definatly appreciate. damage and all the rest are artists, maybe its time we give baxk, ya know? i wish i could be more of a help, but for.now, all i can do it bring the devs together in hopes to make a speedy and stable patch.
if any devs are reading this, i just want you to know us here at xda do appreciate your work, and i hope us joes.can give back in someway.
i guess edits dont bump lol
sooo...
ahem
BUMP!
bumpedybumpbump
can someone help?
is no one awake?
its fridaaaaay!
im off for the night...any late night noobs or pros wanna take a look, you can easily use root explorer to view and edit the files, hopefully youll have more luck than i have (remember its a xml file!)
sys/class/leds/button-backlight/
gnite
correct me if I'm wrong, but I didn't think Damaged2.15 even touches those portions of the OS. I think you should be looking in the /system/lib/hw/ folder.
robchaos said:
correct me if I'm wrong, but I didn't think Damaged2.15 even touches those portions of the OS. I think you should be looking in the /system/lib/hw/ folder.
Click to expand...
Click to collapse
okokokok, let me take a look
!!!!
I think that there are conflicts within there. most of those files are self explanitory, but what are the gralloc.default.so and gralloc.msm7k.so libs? IIRC the droid guys had keyboard issues and those files were included in the fix, so its possible they affect the lighting in some way. I don't think we can pull those files though, it didn't seem to want to boot after that. I think gralloc also has to do with opengl.
robchaos said:
correct me if I'm wrong, but I didn't think Damaged2.15 even touches those portions of the OS. I think you should be looking in the /system/lib/hw/ folder.
Click to expand...
Click to collapse
dammit, i was just trying to sleep.
i was told the file we need is an xml file, and i dont see any in there. HOWEVER; i do see lights.msm7k.so
and sensors.goldfish.so/sensors.heroc.so
which one should i look at first?
robchaos said:
I think that there are conflicts within there. most of those files are self explanitory, but what are the gralloc.default.so and gralloc.msm7k.so libs? IIRC the droid guys had keyboard issues and those files were included in the fix, so its possible they affect the lighting in some way. I don't think we can pull those files though, it didn't seem to want to boot after that. I think gralloc also has to do with opengl.
Click to expand...
Click to collapse
i was wondering what those two were also...no idea
i DO know the file we need to fix is xlm file...should be just a change of a command (or perhaps an addon) but i dont see a single xlm in the entire system/ folder...
suggestions?
Hi all,
This is my first post, although I have been following the group for a long time. My post is motivated by the observation that a massive imbalance exists, particularily in the Legend development community.
There is a huge mass of non-contributing users badgering a small group of hard-working developers, whilst free-loading off the many hours they spend trying to improve the Legend for all of us. (BTW - I'm not pointing any fingers that don't equally apply to myself!) The value of the hours they are putting in is huge, and the return amounts only to the occational humble click of a thanks button.
I have written to the XDA owners and proposed that they implement a system whereby users can donate to a specific thread, and that each month the proceeds of thoses donations are distributed to posters according to the distribution of new "thanks" clicks to them. Unfortunately I have not heard anything in reply, so in the meantime I propose that we start here in the Legend development forum in a less systematic way.
For example; all of us eagerly following ogo2's thread on his Alpha rom should support how we can. We have all heard BlaYO's hesitance to get too involved in that he needs another Legend to do development work on, as he can't render his own out of service for days on end. Absolutely fair point. I would suggest that all active developers in here create a donation account somewhere so that the rest of us ungrateful, free-loading scavengers (again, myself included, and meant in the most positive way! ) can contribute.
Let's get BlaYO a second development Legend, or ogo2 some resources on Linux compilation etc. It's the least we can do, even if we are just selfishly offering to help them, help us
It would not take much, and I am quite certain that anyone who can afford a Legend can also afford to donate $10-20 now and then. What a small price to pay for all the hours that our devs spend working to bring all of us the latest and greatest. Let's give something back!
There were a bunch of users that actually donated to my PayPal account (a few months ago I didn't believe this could happen by the way).
I'd personally object to such a system for various reasons, the main one being complication of something which is a pretty simple in fact: You like the work of someone, you donate (or buy).
Moreover, there are a few CM developers whose work on their device (which happens to use an msm7227 chipset) directly influences the Legend too and therefore my work as well. They are not active in the Legend forum though.
So what I basically want to say: There's a lot of work going on – not hours but weeks – which you might never see because these almost unmoderated boards here are full of you-name-it and every CM developer I know pretty much dislikes XDA for that very reason.
You don't see us (40+ developers) working, but that doesn't mean we aren't.
Edit:
Ah, and by the way, I've been busy too, so tiwlan on 2.6.35 is almost finished.
ali ba said:
Ah, and by the way, I've been busy too, so tiwlan on 2.6.35 is almost finished.
Click to expand...
Click to collapse
Is this meaning that the new CM7s will have the new kernel?
By the way, what was modified in the kernel source so the tiwlan didn't compile normaly?
I don't need a new Legend, I just need some peace...
There you go
BlaY0 said:
I don't need a new Legend, I just need some peace...
Click to expand...
Click to collapse
Peace be with you
Hmmm... OK, I get that my proposal could have some shortcomings, however the intent is good. It's great to hear that users donated to your Paypal, Ali Ba, perhaps other devs should just publish Paypal details too, and users can direct donations to where they feel they are most deserved?
It is not meant to be fair compensation for the numerous hours spent, as the basic principles of community development should still be the driving force. It could, however, be a token of appreciation from those unable to contribute in any other way.
I can't help but feel that there would be more devs involved with more and faster progress as a consequence, if only there was a little reward in there too. Surely that would be in everybodies interest.
In any event, I offer my thanks to all the devs here, and I would be happy to back that up with a contribution, should you decide to go that way
ali ba said:
Ah, and by the way, I've been busy too, so tiwlan on 2.6.35 is almost finished.
Click to expand...
Click to collapse
I was working on getting wl12xx driver working with 2.6.32 kernel but I didn't succeed yet. Is there a reason not to switch to wl12xx driver instead? It also provides soft AP support int the same driver.
Regarding donations, it would be nice if I could donate you via Google checkout.
Thanks.
Yea leave Blay0 alone man, He's getting enough hassle on the Alpha thread as it is! people say they'd like to help then just request more things like a2sd,overclocked kernel etc.If you know anything about linux try helping by trying to build drivers for the last 2 bits (i.e Bluetooth,wifi)
I must say also that there were individuals who offered me donations which I respectfully refused and instead apoint those guys to their nearest charity. I'm not doing this for money (I make money doing other things) I'm just doing it coz I like to know how things work and I always like to learn new things. So if I become bored those donations definitely won't convince me to keep on doing it.
Don't you guys ever think that I'm doing all this for you! Noooope! I'm doing it for me and my own satisfaction. Yes, that's right I'm actualy a selfish, egoistic basterd but in a process of achieving my own goals (which are also inspired by some of your suggestions) I'm really happy if someone else learn something from me. They are few but it doesn't matter... they will definitelly pass on their knowledge and that's important coz I believe knowledge is universal and must be available to anyone willing to accept it and you cannot charge for that.
Don't kidd yourselves, this Legend thingie will be among us at most for another year and then it will get its successors and its community will become even smaller and eventually it will be disbanded and some of us will find new projects, learnig new thing and again passing on all the gained knowledge.
BlaY0 said:
Don't kidd yourselves, this Legend thingie will be among us at most for another year.
Click to expand...
Click to collapse
A whole year is an optimistic approach
The main problem in the development of the HTC Legend is the device itself. It's a rare phone, and pretty much a very small group of people is using it. That also makes the group of talented developers thinner. Look at the Hero or SGS forums topic/post count. Sure - most of them are retarded, and previously answered questions, but still folks in the dev section are coding some crazy and amazing stuff. That's because those devices where popular and successful. The HTC Legend was ment to be the successor of the HTC Hero, but this ain't gonna happen. Nobody will remember this phone in a year or two. That's of course HTCs fault, not ours.
Also mentioning all the request, demands and stupid questions in the dev forum - this forum is not that bad
Go check the Nexus S section. For example the NexusSense topic (my girlfriend got a Nexus so I'm somewhat interested). Now that's pure fukcin massacre out there
Greets!
Sent from my HTC Legend using XDA Premium App
cyRq said:
A whole year is an optimistic approach
Click to expand...
Click to collapse
Agreed, I thought Legend was a kickass sucessor, but very few people actually bought it...I've deserted to Desire S, but I think that's a very similar case so far anyways...
But back on topic: The thing is, everyone has an interest in what he's doing and unless he has a gain from that work he wouldn't be doing it But the idea of donating is noble ofcourse
Let's support our developers by not asking stupid and obvious questions, using search button, hitting that freakin' "thanks" button as often as we can, and most importantly by using our own brains to gain even more from their work
Dr.Romca said:
Let's support our developers by not asking stupid and obvious questions, using search button, hitting that freakin' "thanks" button as often as we can, and most importantly by using our own brains to gain even more from their work
Click to expand...
Click to collapse
Amen! (10char )
Agree with the great Dr!
PLUS This is a General thread so should be in the general section.....Threads should go into the right forums for a start! Hate to think how many threads there are in the wrong place :/
This is a discussion thread for all things custom; Building steps and tips, problem solving and issue discussion. All questions and/or comments are welcome. Be aware, although I build and customize ROMs, I am not a professional developer and cannot promise a solution for your problem. But, hopefully, we can work together to come up with practical solutions for any problems here at m7spr.
So..The things you were shut down on. Were they CM related, or Sense stuff?
Did they involve you working solo, or with a team? Give more details, get the word out.
Felnarion said:
So..The things you were shut down on. Were they CM related, or Sense stuff?
Did they involve you working solo, or with a team? Give more details, get the word out.
Click to expand...
Click to collapse
I really am leery of pointing fingers at specific people because I'm new here and don't want to make a name for myself as a whiner. But, basically it is both. The custom ROMs I am working on have all been built before by me on other devices, so that's not the issue. I have inquired about possibly collaborating with other devs on some Sense related stuff and was looking into why there was no official or unofficial release of the current CM10.2. The sense stuff really isn't my bag as much, but i was/am interested. Others are working on the CM, but with no official release in play, no one wants to put theirs out. I have built it successfully, but have no intention of trying to lay it out there when other devs have been working on it before I got here. My thing is this: when I got tired of waiting for devs to come up with new things, I was told to put up or shut up. It was good advice; I have no coding experience specifically, but I like to learn and have been successful at not only compiling and maintaining custom builds, but also starting 'Learn to do it yourself' threads in two different device forums. I like to learn and compile and share. That's it. I don't need (or want) attention or grateful fans or any of that crap. All I want to do is open the doors for more builds and more users getting off their asses and building for themselves. It seems like a win-win to me, but I feel resistance and it is disappointing. I will get off my soapbox now
I typically touch base with any dev who is the creator/maintainer of any ROM I am interested in pursuing. My experience has been more of a quick 'try it out and see what you get' response or 'it can't be done'. This is after I have asked for not only a blessing, but for relevant information and possibly assistance. Maybe I am just hitting up devs who are already frustrated and don't want someone like me asking a bunch of questions, I don't know....
BMP7777 said:
I really am leery of pointing fingers at specific people because I'm new here and don't want to make a name for myself as a whiner. But, basically it is both. The custom ROMs I am working on have all been built before by me on other devices, so that's not the issue. I have inquired about possibly collaborating with other devs on some Sense related stuff and was looking into why there was no official or unofficial release of the current CM10.2. The sense stuff really isn't my bag as much, but i was/am interested. Others are working on the CM, but with no official release in play, no one wants to put theirs out. I have built it successfully, but have no intention of trying to lay it out there when other devs have been working on it before I got here. My thing is this: when I got tired of waiting for devs to come up with new things, I was told to put up or shut up. It was good advice; I have no coding experience specifically, but I like to learn and have been successful at not only compiling and maintaining custom builds, but also starting 'Learn to do it yourself' threads in two different device forums. I like to learn and compile and share. That's it. I don't need (or want) attention or grateful fans or any of that crap. All I want to do is open the doors for more builds and more users getting off their asses and building for themselves. It seems like a win-win to me, but I feel resistance and it is disappointing. I will get off my soapbox now
I typically touch base with any dev who is the creator/maintainer of any ROM I am interested in pursuing. My experience has been more of a quick 'try it out and see what you get' response or 'it can't be done'. This is after I have asked for not only a blessing, but for relevant information and possibly assistance. Maybe I am just hitting up devs who are already frustrated and don't want someone like me asking a bunch of questions, I don't know....
Click to expand...
Click to collapse
you can start by helping to get things working in sense 4.2.2 beta rom
flex360 said:
you can start by helping to get things working in sense 4.2.2 beta rom
Click to expand...
Click to collapse
I looked your thread up and I think we'd get along great. Anybody who says 'if you don't like me, GOOD' is someone I wanna hang with. It's also funny you should mention helping with that sense version because that's exactly what I was trying to do. Sense aint even my bag, but I was going to look into it from the SVD side to see what I could learn. Maybe I just rubbed that guy the wrong way or something. Regardless, I can't promise how much help I will actually be, but I'm willing to give it a shot. Tell me what you need and the right places to look and I'll do whatever I can. Be cool
BMP7777 said:
I looked your thread up and I think we'd get along great. Anybody who says 'if you don't like me, GOOD' is someone I wanna hang with. It's also funny you should mention helping with that sense version because that's exactly what I was trying to do. Sense aint even my bag, but I was going to look into it from the SVD side to see what I could learn. Maybe I just rubbed that guy the wrong way or something. Regardless, I can't promise how much help I will actually be, but I'm willing to give it a shot. Tell me what you need and the right places to look and I'll do whatever I can. Be cool
Click to expand...
Click to collapse
do you have google hangout?
I think one issue is that there is an update to 4.3 looking for the Sprint One. This will undoubtely contain new radios and firmware that will help our phones run on 4.3+. Since this is a know update, many devs have decided to forego work on the the current 4.1.2 Sense ROMs. Some are working on the 4.2.2 Sense ROM, but with no leak, or Sprint version it is much harder work. Also, there is only source for up to 1.29. The source from the 1.31 update is not available and it has caused issues with ROMs based on that update.
Personally I don't get your complaint though. There is a lot of development and a wide selection of ROMs available from Stock Android 4.1 to 4.3 to Stock Sense, to heavily themed Sense ROMs. What exactly is not available that you want?
flex360 said:
do you have google hangout?
Click to expand...
Click to collapse
[email protected]
raptoro07 said:
I think one issue is that there is an update to 4.3 looking for the Sprint One. This will undoubtely contain new radios and firmware that will help our phones run on 4.3+. Since this is a know update, many devs have decided to forego work on the the current 4.1.2 Sense ROMs. Some are working on the 4.2.2 Sense ROM, but with no leak, or Sprint version it is much harder work. Also, there is only source for up to 1.29. The source from the 1.31 update is not available and it has caused issues with ROMs based on that update.
Personally I don't get your complaint though. There is a lot of development and a wide selection of ROMs available from Stock Android 4.1 to 4.3 to Stock Sense, to heavily themed Sense ROMs. What exactly is not available that you want?
Click to expand...
Click to collapse
This really wasn't meant to be some complaint thread with a bunch of whining; just the opposite, really. I just wanted feedback on how I am perceiving things around here. I'm cool with being told I have it wrong; was hoping for it actually. And you pointed out exactly what I mean in part. Sense this and stock that is the rule of the day here. That's ok. Everyone is allowed to like whatever they want and if sense and stock are the most wanted builds then so be it. But, I am a self-proclaimed customization junkie, for better or for worse. Personally, I like more fully custom ROM choices and have been beating my head against the wall trying to get some Beanstalk love here but without success to this point. BS is already set in 4.3 and matched with CMs 10.2 releases, so I'm stumped. If you have knowledge, I would be happy to show you some of my errors. I do think you make a great point about the whole place being in flux due to the impending 4.3 release. Like I said before, I just want to open up some development doors and get more interest in development in general. Maybe I have hit up the wrong devs or caught them at bad times. It happens.
BMP7777 said:
[email protected]
This really wasn't meant to be some complaint thread with a bunch of whining; just the opposite, really. I just wanted feedback on how I am perceiving things around here. I'm cool with being told I have it wrong; was hoping for it actually. And you pointed out exactly what I mean in part. Sense this and stock that is the rule of the day here. That's ok. Everyone is allowed to like whatever they want and if sense and stock are the most wanted builds then so be it. But, I am a self-proclaimed customization junkie, for better or for worse. Personally, I like more fully custom ROM choices and have been beating my head against the wall trying to get some Beanstalk love here but without success to this point. BS is already set in 4.3 and matched with CMs 10.2 releases, so I'm stumped. If you have knowledge, I would be happy to show you some of my errors. I do think you make a great point about the whole place being in flux due to the impending 4.3 release. Like I said before, I just want to open up some development doors and get more interest in development in general. Maybe I have hit up the wrong devs or caught them at bad times. It happens.
Click to expand...
Click to collapse
Part of the issue might be that users are afraid of using Cm as it has a nasty habit of bricking phones that no one of notoriety has looked into, acknowledged, or found a solution to.
Kraizk said:
Part of the issue might be that users are afraid of using Cm as it has a nasty habit of bricking phones that no one of notoriety has looked into, acknowledged, or found a solution to.
Click to expand...
Click to collapse
I haven't really been looking at it after my first run (I personally like Sense a lot, and AOSP didn't have a good way of dealing with the limited hardware options for me), but wasn't the brick-spree killed a while back?
Rirere said:
I haven't really been looking at it after my first run (I personally like Sense a lot, and AOSP didn't have a good way of dealing with the limited hardware options for me), but wasn't the brick-spree killed a while back?
Click to expand...
Click to collapse
A couple of people developed a "consensus" that it had been fixed. then 2 more people bricked their phones. ALLEGEDLY the CPU has a tendency to over clock itself and lock at 1.7 Ghz
This is all fine and dandy yet no one can figure out why or how to stop it.
I thought so too
Sent from my One using XDA Premium 4 mobile app
BMP7777 said:
I thought so too
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Like I said no one ever figured out why or how to stop it. A consensus was reached but then more people bricked. No developers could be bothered to take time out of their day to look into it though.
Kraizk said:
Like I said no one ever figured out why or how to stop it. A consensus was reached but then more people bricked. No developers could be bothered to take time out of their day to look into it though.
Click to expand...
Click to collapse
I saw one guy who was addressing it and taking names and such, but then I guess it just faded away. Do you know of ongoing issues like this? Can all of the bricks be undoubtedly proven to be from no other cause? I think that would be the defining characteristic of lack of support; difficulty in proving cause. My build of CM10.2 runs fine as long as I don't try to change the font with Font Installer. And I am reasonably certain that it isn't from CM all by itself. I have the same issue with Illusion ROM 4.2.2. Anybody know why we can't change the font? My thread; I can change topic if I want to
BMP7777 said:
I saw one guy who was addressing it and taking names and such, but then I guess it just faded away. Do you know of ongoing issues like this? Can all of the bricks be undoubtedly proven to be from no other cause? I think that would be the defining characteristic of lack of support; difficulty in proving cause. My build of CM10.2 runs fine as long as I don't try to change the font with Font Installer. And I am reasonably certain that it isn't from CM all by itself. I have the same issue with Illusion ROM 4.2.2. Anybody know why we can't change the font? My thread; I can change topic if I want to
Click to expand...
Click to collapse
It is the only common factor in permanent bricks. Phone gets hot, phone wont charge. All other "bricks" are user induced because people did not understand what S-Off meant, what wiping in TWRP means, what GSM means etc etc.
So how many confirmed permanent bricks and when was the last? Has anyone proven a cause? Contacted HTC or CM or Sprint? If there were twenty cases with only 5 confirmed, then it isn't that big from a larger standpoint. See what I mean? That would explain what you see as a lack of support? Has this happened to you?
BMP7777 said:
I thought so too
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Check your hangouts.
BMP7777 said:
Why does there seem to be very little development going on here and why is the development that is taking place so closely guarded? I thought everyone wanted more choices and new options..... I see that there is current and ongoing 10.2 development (hell, I've even built it), but no one wants to release it. I'm hearing that the last guy who did that got banned. So, if everyone is waiting for OFFICIAL builds to be released first, why are there none being officially worked on? Two times in the last three weeks I have inquired about wanting to work on some new development and have either been told straight out not to release or been effectively threatened with reporting before I have even begun an attempt. I don't know if maybe there has been a rash of jerks who are trying to claim ownership of work that does not belong to them or what, but I've never seen as much negativity about new builds in any thread I have been a part of. I want to claim ownership of nothing; I only want to open doors. I guess I'll just work on things for my own use and leave this forum to the guys currently running it. HMPH :angel:
Click to expand...
Click to collapse
You could build us a GSM version ROM that works on the sprint HTC One. You'd be a hero if you could do that. We've already unlocked our phones and are able to connect to the ATT / TMO but only manually. When the signal is lost it seems to still be looking to auto connect to sprint...I would think this should be a simple setting software but I know nothing about phone ROMs.
Beck04vall said:
You could build us a GSM version ROM that works on the sprint HTC One. You'd be a hero if you could do that. We've already unlocked our phones and are able to connect to the ATT / TMO but only manually. When the signal is lost it seems to still be looking to auto connect to sprint...I would think this should be a simple setting software but I know nothing about phone ROMs.
Click to expand...
Click to collapse
Man, if I could do that I'd be a GOD. :angel:
I love lamp
Haha Naw but I see your point but I love and appreciate every devolepers effort here on this forum ..there not a a lot but a bunch of smart and quietly brilliant devs here ...I'm comfortable but the more the merrier
Sent from my HTCONE using XDA Premium 4 mobile app
CyboLabs is Proud to present
Open Bump!
What is Open Bump?
Open Bump is a recreation of the closed source Bump project run by Codefire.
It will allow you to "sign" your boot images in the same way that Codefire does it, only you don't need an internet connection.
Click to expand...
Click to collapse
What Open Bump is NOT
lets get the obvious out the way. It won't axe murder you.
It is not a direct reverse engineer of Codefire's implementation. I found the key and iv on my own
The magic bytes were taken from Codefire's method however. If anyone has insight has to how they were found, please shout up.
It does NOT take your private data so you can use it. Tin hatters feel free to double check
Click to expand...
Click to collapse
How did I find this out
I had a general idea of what to look for, having heard that the exploit is related uicc, and is signed with a cipher.
Dropping the aboot image in to Ghex led me to finding a reference to "uiccsecurity". Using the bytes around this, I found a repeat of 32 bytes, which was followed by 16 bytes which formed something that resembled "SecureWallpaper".
As you can probably guess, this was mainly trail and error backed by common sense and logical thinking.
you can programmatically find these values with the python script:
Python:
aboot_name = './aboot.img'
aboot = open(aboot_name, 'rb').read()
key_end = aboot.index('uicc')
key_start = key_end - 32
key = aboot[key_start:key_end]
sec_key_start = aboot.index(key, key_end)
iv_start = sec_key_start + 32
iv_end = iv_start + 16
iv = aboot[iv_start:iv_end]
deciphering some already generated "signatures" proved that these were the key and iv used for "signing" the images.
Click to expand...
Click to collapse
What is coming next?
Inspecting the signatures that were originally uploaded and the ones that people can generate now, I found only one pattern.
The only similarities were the first 16 bytes of each "signature". I believe that only the magic number is needed, and none of the garbage that follows. This has been confirmed by the LG G3 dev from CyanogenMod, Invisiblek Done
Click to expand...
Click to collapse
How to use it?
I don't know how well this will run on anything other than linux, so for now.. I won't talk about it.
First, ensure you are using python2
then run the script
Code:
python2 open_bump.py "/path/to/boot.img"
flash the output, and enjoy
Click to expand...
Click to collapse
Thanks to:
Obviously, this wouldn't have been possible without Codefire since I wouldn't have known where to look, or that it was exploitable. And it was them that found the magic key.
Big thank you to @pulser_g2, who offered invaluable input on cryptography
Big thank you to @invisiblek, who I mercilessly kanged the main part of the image padding script from
note:
The original part of finding this information out was done on my own with guidance from pulser. The final results of this are posted above.
XDA:DevDB Information
Open_Bump, Tool/Utility for the LG G2
Contributors
cybojenix
Source Code: https://github.com/CyboLabs/Open_Bump
Version Information
Status: Beta
Created 2014-11-23
Last Updated 2014-11-23
Thanks, thats great news to have an open source tool here!
Do you see any chance that this could be integrated into CWM/TWRP so that the recovery rom could bump the boot/recovery images before flashing?
Because the boot/recovery.img has to be extracted from the ROM-zip before flashing, bumping it here would make sure that the phone can boot the image even with the newer bootloader.
This would be great for rom-devs since they don't have to change anything and it would even bump roms that are not maintained anymore.
g4rb4g3 said:
Thanks, thats great news to have an open source tool here!
Do you see any chance that this could be integrated into CWM/TWRP so that the recovery rom could bump the boot/recovery images before flashing?
Because the boot/recovery.img has to be extracted from the ROM-zip before flashing, bumping it here would make sure that the phone can boot the image even with the newer bootloader.
This would be great for rom-devs since they don't have to change anything and it would even bump roms that are not maintained anymore.
Click to expand...
Click to collapse
simple answer, this can be added to the build step really easily. See this commit
edit:
of course it may be useful to make a c program to do this.... I shall think on it.
Propably stupid question but i ll give a shot. Since we have the magic key we cant just skip the bump stuff totally? As i can understand, i dont wait official developer team join the bump train, thats why the damn development of the device is really back while the hardware is more than capable.
**To the OP i wish i could give you a thousand likes sir!
After getting the bootloader may be open G3؟؟
Why not use the original Bump?
Quote:
Codefire has been extremely vague about their method, obviously to prevent someone else replicating their results.
They are also storing people's data unnecessarily, and even adding some information relating to the user in to the "signature", possibly for tracking purposes.
As a result of it being an external service, many reputable teams (which won't be named unless they want to be) have said they will not use it, and would rather wait till LG releases the official unlock method.
Finally, Codefire have said the sha1sum of the boot image is required. Whether they knew or not, it is NOT required, and I will be changing this tool to compensate for that.
Click to expand...
Click to collapse
Happy you found a new exploit for us builders and devs, just feel like you kinda disrespected codefire team by accusing them of things before actually talking to them, seems a bit counter productive, this may piss them off and next device you can kiss new exploits by them good-bye,
just my 2 cents on the matter,
i'd remove the line...
in any case thank you very much, i will add it to my build script
---------- Post added at 08:34 PM ---------- Previous post was at 08:29 PM ----------
nikosblade said:
Propably stupid question but i ll give a shot. Since we have the magic key we cant just skip the bump stuff totally? As i can understand, i dont wait official developer team join the bump train, thats why the damn development of the device is really back while the hardware is more than capable.
**To the OP i wish i could give you a thousand likes sir!
Click to expand...
Click to collapse
"Bump stuff" has nothing to do with users, the devs and builders do the "bumping", and development of the G series has nothing to do with bumping, it just takes time to bring everything up
Good job cybojenix. (moderator edit: watch your language please)
Way to ruin a good thing.
I'm done with Android now. You can do it all now - since you obviously know better than me and everyone else.
I don't appreciate people trying to blackmail me - EnderBlue and Cybo both.
Don't believe me? http://hastebin.com/gulumezawi.txt
Good job guys. Way to ruin unlocks for all future LG phones.
If I *EVER* decide to come back, I will not be releasing anything as free or open source. You've sullied my impression of the open source community. Anything I do will be private releases from now on.
LG hadn't patched Bump, and they were going to leave it alone for us as long as we kept it as a service.
Well, looks like that's over and done with.
Bump included a hash of the image that you uploaded and a hash of your developer ID, and some random junk bytes. That's all. It's exactly what we said it was doing.
Well, hey, now you're free to take over and write roots and unlocks for all LG phones since you obviously have the talent to do so.
Let's be honest though, without my team's hard work that you stole, you wouldn't have been able to do any of this.
But you knew that, you're just a bottom feeder.
I don't get angry often at all- but congrats! You've succeeded in making me mad! Achievement unlocked!
I'm done. Your turn.
EDIT: Also, you know you can't open source your project either considering it contains 'stolen' LG crypto keys. https://github.com/CyboLabs/Open_Bump/issues/1
Have fun with that one.
thecubed said:
Good job cybojenix. (moderator edit: watch your language please)
Way to ruin a good thing.
I'm done with Android now. You can do it all now - since you obviously know better than me and everyone else.
I don't appreciate people trying to blackmail me - EnderBlue and Cybo both.
Don't believe me? http://hastebin.com/gulumezawi.txt
Good job guys. Way to ruin unlocks for all future LG phones.
If I *EVER* decide to come back, I will not be releasing anything as free or open source. You've sullied my impression of the open source community. Anything I do will be private releases from now on.
LG hadn't patched Bump, and they were going to leave it alone for us as long as we kept it as a service.
Well, looks like that's over and done with.
Bump included a hash of the image that you uploaded and a hash of your developer ID, and some random junk bytes. That's all. It's exactly what we said it was doing.
Well, hey, now you're free to take over and write roots and unlocks for all LG phones since you obviously have the talent to do so.
Let's be honest though, without my team's hard work that you stole, you wouldn't have been able to do any of this.
But you knew that, you're just a bottom feeder.
I don't get angry often at all- but congrats! You've succeeded in making me mad! Achievement unlocked!
I'm done. Your turn.
EDIT: Also, you know you can't open source your project either considering it contains 'stolen' LG crypto keys. https://github.com/CyboLabs/Open_Bump/issues/1
Have fun with that one.
Click to expand...
Click to collapse
First off, I didn't black mail. I gave your team notice about open sourcing it after reverse engineering the LG bootloader, not your "signatures".
It's your choice if you want to leave Android. Pinning the blame on me is somewhat childish though.
LG not patching Bump? That's a ludicrous statement, and even if it's true, it's good that this script got released. That way they know it should be patched, since having it a service clearly makes all the difference to them.
The hardest part of your teams work was getting the keys. If you know where to look, then it's easy enough to get engineering builds which I suspect contain the master magic bytes which you released.
I'm honestly shocked at your reaction though. I gave your team all the credit and stated which parts I did myself. The part about the service, and the deception was justified.
You tried to obscure something which by logic can't be obscured. That's how so many people realised they can just append the bytes to the image.
So which one would you rather have, LG not patching the exploit (as you so claim), and having an unknown number of people in china running around flashing custom boot images, or have everyone know how to do it to force LG to recheck their security measures.
What I did may not have been fantastic for the community, but what you did was insanely dangerous for the 90% of LG users.
All you did was make it so LG locks down the bootloader. And really 90% of users??? There probably isn't even 3 percent of the LG base on this website. All you did was screw everybody else over so you could have YOUR OFFICIAL CM.
As well people saying you didn't do enough and are still using there signing key as well as attacking it as well.
Way to think about yourself. You didn't care about the 90% or you wouldn't have done this.
I personally hope LG locks down the bootloader now. Go the way Samsung did and put an efuse on it and prevent downgrading. Hopefully all this happens with lollipop so you can screw over the rest of the LG crowd.
cybojenix said:
it's good that this script got released. That way they know it should be patched, since having it a service clearly makes all the difference to them.
Click to expand...
Click to collapse
"Hey let's potentially close all future LG unlocks and thus the chance to use CyanogenMod on future LG devices then. Just so I can get the current CM builds to say 'Official' and get a big pat on the back from the CM dudes who probably don't care about me too much."
Is that what went through your mind? That instant gratification and ignorance really shows who you are because that's exactly what I see from this OP of yours. Enjoy your 15 minutes of fame. You probably just killed a chance for years of it.
savoca said:
"Hey let's potentially close all future LG unlocks and thus the chance to use CyanogenMod on future LG devices then. Just so I can get the current CM builds to say 'Official' and get a big pat on the back from the CM dudes who probably don't care about me too much."
Is that what went through your mind? That instant gratification and ignorance really shows who you are because that's exactly what I see from this OP of yours. Enjoy your 15 minutes of fame. You probably just killed a chance for years of it.
Click to expand...
Click to collapse
Yes, because I've been such a massive supporter of cm. (sarcasm in case you didn't realise).
I started reverse engineering the bootloader for research purposes. If it was more complex than what I have said above, then I probably wouldn't have done this thread.
If it weren't for the fact that the magic stays the same across all signatures, then I also wouldn't have done this thread.
The response I got from them when I contacted them before releasing this was pretty much one of lack of care. So I went ahead and posted it.
I couldn't care less about fame. In fact there isn't really a lot I do care about, but I won't have the community alienated in to thinking the codefire service was such a great thing.
And once again, I refuse to take the blame for their team leaving Android.
whoppe862005 said:
All you did was make it so LG locks down the bootloader. And really 90% of users??? There probably isn't even 3 percent of the LG base on this website. All you did was screw everybody else over so you could have YOUR OFFICIAL CM.
As well people saying you didn't do enough and are still using there signing key as well as attacking it as well.
Way to think about yourself. You didn't care about the 90% or you wouldn't have done this.
I personally hope LG locks down the bootloader now. Go the way Samsung did and put an efuse on it and prevent downgrading. Hopefully all this happens with lollipop so you can screw over the rest of the LG crowd.
Click to expand...
Click to collapse
See my other post, I don't care about cm.
Fair enough, 3% are here, so this benefits the security of 97% of lg uses, if the claim that lg was alright with it running s a service is true.
Either way, I did nothing wrong
cybojenix said:
I couldn't care less about fame. In fact there isn't really a lot I do care about, but I won't have the community alienated in to thinking the codefire service was such a great thing.
Click to expand...
Click to collapse
So you only care about ruining good things, and other people's work?
Lol sorry I think I'm done with you. By cybo
savoca said:
So you only care about ruining good things, and other people's work?
Lol sorry I think I'm done with you. By cybo
Click to expand...
Click to collapse
Tbh I thought it would have been clear by now what I care about. Then again I may have been wrong about considering you one of the smart android people.
I care about learning and sharing knowledge. Which is precisely what this thread did.
cybojenix said:
See my other post, I don't care about cm.
Fair enough, 3% are here, so this benefits the security of 97% of lg uses, if the claim that lg was alright with it running s a service is true.
Either way, I did nothing wrong
Click to expand...
Click to collapse
I saw your PM to autoprime in IRC, it was "I am going to post what I found or you do, either way its going there", it wasn't lack of care, it was that you just stated a fact and left, it was a very rude unthoughtful thing to do, also don't try to BS everyone with your research, you and about 100 other people found the "magic keys", the problem is those "magic keys" were placed there by team codefire, you didn't find them, you found that they were using the key and copied their work, anything else you say is a lie, at least the other 99 people who found this had the basic respect to not post it unless the original team allowed it.
There was no reason to post this, their site was working fine, and if you used the API there was no problem of tracking since it just uses a UID to identify to the server.
at least admit you were wrong and say you are sorry, they won't fix anything but will gain you a minimum amount of respect
sooti said:
I saw your PM to autoprime in IRC, it was "I am going to post what I found or you do, either way its going there", it wasn't lack of care, it was that you just stated a fact and left, it was a very rude unthoughtful thing to do, also don't try to BS everyone with your research, you and about 100 other people found the "magic keys", the problem is those "magic keys" were placed there by team codefire, you didn't find them, you found that they were using the key and copied their work, anything else you say is a lie, at least the other 99 people who found this had the basic respect to not post it unless the original team allowed it.
There was no reason to post this, their site was working fine, and if you used the API there was no problem of tracking since it just uses a UID to identify to the server.
at least admit you were wrong and say you are sorry, they won't fix anything but will gain you a minimum amount of respect
Click to expand...
Click to collapse
Wrong, I stated that I was going to open source it, meaning the work of put in to getting the key and how it's used to get the original magic.
It was after that that I realised the final magic is the only thing needed. I actually worked out how to get the magic key a few hours ago, but since I don't have the right images, it won't be globally usable.
Fair enough, I apologise for pointing out the flaws in codefires service, and that they took it badly.
cybojenix said:
See my other post, I don't care about cm.
Fair enough, 3% are here, so this benefits the security of 97% of lg uses, if the claim that lg was alright with it running s a service is true.
Either way, I did nothing wrong
Click to expand...
Click to collapse
OK. If you did nothing wrong please do explain this
Enderblue-"well, would you be willing to open source it so we can have a official cm support?"
IoMonster-"so it would make storm already worse then what it is now? *paraphrasing for language
IoMonster-"no"
Seems like be said he didn't want it open source but you still went ahead any way.
http://hastebin.com/gulumezawi.txt
And then you saying your going to push it for vs985 even after he said no.
I don't know who Enderblue is, and I'm not affiliated with him..
whoppe862005 said:
OK. If you did nothing wrong please do explain this
Enderblue-"well, would you be willing to open source it so we can have a official cm support?"
IoMonster-"so it would make storm already worse then what it is now? *paraphrasing for language
IoMonster-"no"
Seems like be said he didn't want it open source but you still went ahead any way.
http://hastebin.com/gulumezawi.txt
And then you saying your going to push it for vs985 even after he said no.
Click to expand...
Click to collapse
cybojenix said:
I don't know who Enderblue is, and I'm not affiliated with him..
Click to expand...
Click to collapse
It isn't like it matters if you are or not. It says right in the chat he doesn't want it open sourced. I'm sure about 99% of the people on here have seen that already and I'm pretty sure you have seen it as well.
It states right in the chat he didn't want it open sourced.
whoppe862005 said:
It isn't like it matters if you are or not. It says right in the chat he doesn't want it open sourced. I'm sure about 99% of the people on here have seen that already and I'm pretty sure you have seen it as well.
It states right in the chat he didn't want it open sourced.
Click to expand...
Click to collapse
but the chat wasn't with me, so your point is null
autoprime had ample opportunity to say "don't do it yet", or "go talk to IO". but no, no objections were made.
Codefire treated the service like any other company would treat their unlocking service, so I treated them like a company and showed how it was done.
Well guys, looks like Xposed for 5.0 won't ever happen.
REVISION: This edit was added on 2.13.14
The above statement was purely a joke when Xposed for LP was merely a dream. To clarify, as of now there is no ETA for Xposed. Ever. Don't ask. Stop. Don't think of it. If you ask, you shall be banned as of the words of the moderator.
I know it may be hard to read sometimes, so I started a new paragraph. If you are confused, look up. ETAs don't exist on this developer website. Thank you.
Xposed is IN THE WORKS and no, there is no beta version. If you beg to differ, post a comment. Don't flame me or anybody.
=D have a WONDERFUL, hate free day.
The full comment posted at https://github.com/rovo89/Xposed/issues/18 is:
Thanks guys. Actually, there is no need to worry about alternative approaches. It's not easy to "hack" ART in a similar way as Dalvik, but it's generally working.
What most people forget:
a) ART isn't the only new thing in Lollipop. SELinux requires a lot of extra code and even more thoughts to work around the restrictions. And 64 bit breaks the assumption that everything starts in a single process, as there are two Zygote processes now. I think it's important to consider this right from the start.
b) The actual (net) time required to write code is far away from the time that passes. It's not like I work on Xposed every evening. There are weeks when I don't look at the code at all. Yes, I do have other things in my life, and some have a higher priority. So even if something would take just a few evenings to code, it might take me a couple of weeks to actually do it. And once I publish something, you probably wouldn't like it if I took off for a few weeks.
If it was just about coding, pushing the source could be helpful. But that works best if there's already a clear concept of what is needed and an idea how this can be split up into work packages. Often it takes hours to come up with a concept that can be coded in 20 lines. Remember how many people are using Xposed meanwhile. We don't want to have some quick code that works by accident, so it's vital to think everything through carefully, and that takes time.
So yeah. It will take more time, I still don't give any ETA, but I'm quite confident that we'll have something nice some day.
Click to expand...
Click to collapse
No new "work in progress" sources = no help from other contributors. That's it.
pyler said:
No new "work in progress" sources = no help from other contributors. That's it.
Click to expand...
Click to collapse
You can probably count the people who really understand Xposed and how it works at one hand (and you'll basically have to start from scratch for lollipop).
It's not like there were hundreds of contributors in the past, so what you're trying to say here is invalid.
Yes, there would probably be some people who could help out, but keep in mind that every minute rovo is helping others to better understand what's going on isn't available for him to do some actual development (which includes research and drafting ideas).
I'm sure that any top tier dev who feels confident to actually bring xposed for lollipop forward can contact rovo anytime and get his wip code, but so far no one has spoken out.
The sad truth is that 95% of the xda users are people without any real technical knowledge - and the only thing they do is to offer to "test" something to gain access to something before it's release.
Unfortunately those testers are rarely ever needed, at least not within the core development phase, here it takes way more time to explain people what is needed than to just test it yourself.
When you're rolling something out to production and want to make sure that the last little bugs within different usage cases and configurations are squashed, sure you'll need testers, but not before.
But for now that's not the case, so it might be better to keep the unhelpful comments to oneself
KevinDixson said:
Well guys, looks like Xposed for 5.0 won't ever happen.
(To all you downers out there, its called a joke. Laugh about it. Next thread.)
Click to expand...
Click to collapse
Liar
So yeah. It will take more time, I still don't give any ETA, but I'm quite confident that we'll have something nice some day.
Click to expand...
Click to collapse
If you can't offer something better then be patient.
Primokorn said:
Liar
If you can't offer something better then be patient.
Click to expand...
Click to collapse
Just like the op stated.... Its a JOKE
He had 666 Followers and I thought it was funny and would lighten up a few peoples stress filled days. The only reason I saw this was because I was going through his posts and READING all of them to get an update as to where we stand.
KevinDixson said:
(To all you downers out there, its called a joke. Laugh about it. Next thread.)
Click to expand...
Click to collapse
I found it for you ^ since sometimes I know its REALLY hard to understand the concept of a joke.
KevinDixson said:
Just like the op stated.... Its a JOKE
He had 666 Followers and I thought it was funny and would lighten up a few peoples stress filled days. The only reason I saw this was because I was going through his posts and READING all of them to get an update as to where we stand.
I found it for you ^ since sometimes I know its REALLY hard to understand the concept of a joke.
Click to expand...
Click to collapse
Yep sorry I misread your post. I feel a little bit stressed with all this story lol
Anyways, 666 is the patience and Rovo the angel
Primokorn said:
Yep sorry I misread your post. I feel a little bit stressed with all this story lol
Anyways, 666 is the patience and Rovo the angel
Click to expand...
Click to collapse
Hahaha no worries bro just keepin the haters out of this thread :bruh:
just for waiting...
Hope xposed will be ported to lollipop eventually!!!
Hi guys! Yeah, I'm part of those 95% (I'm a lawyer), but I'm very grateful to rovo for his work. I have Nexus 5, but I'm still on Android 4.4.4 because of Xposed, and I'm not going to update to 5.0 until the new version of Xposed is done. You can see how important it is for me. @rovo89, I'm pretty sure that many people would pay you to complete your work. I understand that you have higher priorities and you are doing all of this for fun, but have you thought that you have almost 3 millions of downloads? If you create your team of software engineers and sell Xposed at 2$ (2€), you work on it every day for several months, and we assume that most of the current users buy your product, you will have enough money to pay your team and dedicate all of your time at what you want. It's just a suggestion of one of these 3 millions of users, that would pay more than 2$ and appreciate your work so much! Best regards from Spain!
rovo has said on multiple occasions that he won't take money for working on Xposed as he does not want it to become a job where he feels obligated to work on it full time.
He's working on it already. Offers of monetary gain won't make that work go any faster. Everyone will just have to be patient.
Sent from my C6603
We don't know if he is really doing on it (I hope yes but..) since we have no proofs (only claims) and no documentable code progress since August 2014. Plus, rovo89 was active here last year till August or so. Then he left.
If there are people who want work on it and have enough skills to port it, they should fork it and not wait. I saw some guys on github who want to work on ART port.
He flat out stated he would not post progress publicly either on GitHub or here and to wait until he had something worth publishing (that real contributors could help with) without bothering him. Comments on issues on GitHub do show he is/was working on it.
The real problem is that people are impatient and feel entitled to updates on progress, even though rovo explicitly stated that he wouldn't be doing that.
As for others *wanting* to work on it; nobody is stopping them forking the project and doing so. If they get it working then that would be fantastic and I'm sure everyone including rovo would be happy and grateful. That's the great thing about open source.
Sent from my C6603
1. Work hard to create something really, really useful.
2. Make it (and all the resources for re-creating it) available for free.
3. Millions of people use it.
4. Decide not to work so hard on it.
5. Get hounded day in and day out for months by thousands of people.
This is a classic example of "No good deed goes unpunished".
Rovo is a saint. In his shoes, I would have told all of the "hounders" to f**k off a long time ago.
In other words, people, learn how to be grateful, get off of Rovo's case, and move on.
.
This is sad, I would donate to help the dev, especially since all this is free
i'm a user and for me is normally this long time...the system of cache is completaly changed....and see it immediately in the booting process and the loading apps process.
Be patient!
Go On Rovo u can do that =)
I hope you are wrong
KevinDixson said:
Well guys, looks like Xposed for 5.0 won't ever happen.
(To all you downers out there, its called a joke. Laugh about it. Next thread.)
Click to expand...
Click to collapse
It is already 2015 and there is still no support for lollipop. It was working fine with jelly bean. I just installed a custom lollipop rom and I wanted to user xposed with greenify. It seems I have to wait and your saying will just be a conspiracy. You should really stop creating this kind of threads. Value people's creativity. That fact that, there is a delay doors not mean it will not be made. If for anything at all, give them some morale
Lollipop is a completely new system. The difference between KitKat and Lollipop is almost the same as between Windows 95 and Windows XP, if not larger... Lollipop looks like ordinary Android, acts like it, but it is NOT it...