Related
Well... I did it for Hermes, tomorrow I'm doing it for Trinity, this is just here to make sure I get round to it... and to let you folks know it's in the pipeline
I was going to ask you if you had any plans for us. Thanks for the hard work
Olipro: this will take you to the hall of fame together with Des, Pof, Lvsw, Dutty and some others.
Looking forward for your news. Thanks.
According to hermes thread this is simple rip of SSPL bootloader (my appologies to Olipro if it is not). Shuch tool exist for a long time but there are some reasons why it is not released to public. However now I'm forced to do so, use at your own risk. Development of better tool was in progress but now I'm not shure if I wish to continue with it.
Hi, what's the difference between this SPL and the SSPL-TRIN.exe available in this thread http://forum.xda-developers.com/showthread.php?t=293632 ?
Des said:
According to hermes thread this is simple rip of SSPL bootloader (my appologies to Olipro if it is not). Shuch tool exist for a long time but there are some reasons why it is not released to public. However now I'm forced to do so, use at your own risk. Development of better tool was in progress but now I'm not shure if I wish to continue with it.
Click to expand...
Click to collapse
Thanks for your contributions . I hope that you are not getting put off by the whole "pay for services" thing that seems to be going on. You are the one that came up with the SSPL utility and we are very grateful. You were the first to make a Trinity ROM change possible without a CID unlock. Keep up the great work it is appreciated.
Matt
Hi, what's the difference between this SPL and the SSPL-TRIN.exe
Click to expand...
Click to collapse
This one is bootloader image for flashing in to device, SSPL is the same image wrapped with stuff needed to start it from WinCE.
This is for those users who want SSPL functionality in flashed-in bootloader. Most average users (don't playing dangerous games with flashing probable crap to radio) won't need this.
Des said:
According to hermes thread this is simple rip of SSPL bootloader (my appologies to Olipro if it is not).
Click to expand...
Click to collapse
Technically it is half a rip off: Olipro "backported" your bypass-signature patch to hermes SPL-1.04, but he had to reimplement the "show itself as SuperCID" patch because this on 1.09 just requires a NOP, but the default on 1.04 is to assume CID (remember the CID checking bug in that bootloader?), so implementation is different. The good thing of having it on 1.04 is that it allows to access the radio bootloader and 1.09 doesn't.
Des said:
Shuch tool exist for a long time but there are some reasons why it is not released to public. However now I'm forced to do so, use at your own risk.
Click to expand...
Click to collapse
I think Olipro released the SPL in the aim of helping, and also because he learned from you and had fun extracting it... this doesn't force you to release the Trin SPL, but I see it as a good thing... can you be more specific on these reasons why this has not to be released?
Des said:
Development of better tool was in progress but now I'm not shure if I wish to continue with it.
Click to expand...
Click to collapse
err... I hope you continue with it, don't want to discourage you on that... you made it possible the best it could ever happen to Hermes & Trinity, and you have all the support and respect of xda-dev community for that. Hope you continue with the development whenever you have time to do it, as you are a very valuable piece of the puzzle here
Matterhorn said:
Thanks for your contributions . I hope that you are not getting put off by the whole "pay for services" thing that seems to be going on. You are the one that came up with the SSPL utility and we are very grateful. You were the first to make a Trinity ROM change possible without a CID unlock. Keep up the great work it is appreciated.
Matt
Click to expand...
Click to collapse
Matterhorn is absolutely right. Great work! We all are very thankful. Keep it up!
well, I'd just ripped the Trinity ROM to upload it...
but it's identical to Des's (except the version number) so no worries...
on another note; I think you'll find that I haven't actually released your SPL Des, I still have that on my computer; currently I've only sent it to pof and some guy who intends to play around with it... it's a shame someone has to be so petty as to decide to up and stop development of something just because someone ported their work to an earlier ROM, but if that's the way it's going to be then I guess it means that development will be slower as others are left to pick up the gauntlet
I dont understand Des behavior... what's the deal of Olipro rip/port/transform Des's code to an earlier version ?!
Isn't this supposed to happen in an open minded/source community ?!
I thought you were all here because you share the same interests... This new "wave of paid services" is really messing up things among you all and specially the free open source filosophy.
We're very thankful for all your hard work so all you can expect from us is a deep respect. I really hope that you can cut the crap of your divergences to continue providing your amazing solutions.
Des's not hyping up his contribution to the community and is trying to be cautious with releasing something potentially harmful. Nobody wants more bricks here...
Rip-off or not, if it's likely to cause problems (and Des probably knows better than others), it's not safe to make it public.
There's a lot of buzz lately in Trinity WM6 thread and now with patched SPL here. A lot is yet to be done, probably more than already done, why the buzz?
this on 1.09 just requires a NOP, but the default on 1.04 is to assume CID
Click to expand...
Click to collapse
I know this issue. Similar one exist on breeze bl.
can you be more specific on these reasons why this has not to be released?
Click to expand...
Click to collapse
From technical side mostly because of that flashing without any integrity check is dangerous. It works for sspl but just because sspl is used by most users to flash shipped or somebodys cooked (and tested) updates. Potential users of standalone bl (wich claims to be crashproof but if signatures are fu*ked up or absent it is NOT) are seems to be more hackers than consumers wich means that they would flash not just shipped updates. I know about dozen of devices bricked (full of bads) due to incorrect signature size or absence of it. Do you whant more ?
this doesn't force you to release the Trin SPL
Click to expand...
Click to collapse
"tomorrow I'm doing it for Trinity" (c) Olipro.
So while it would be released I prefer to release it myself.
Hope you continue with the development
Click to expand...
Click to collapse
it's a shame someone has to be so petty as to decide to up and stop development of something just because someone ported their work
Click to expand...
Click to collapse
Looks like my position need be explained bit clearer.
At first - here I do not hack or code for resulting effect or profit (I have a job for such things). I do this just for my own fun. And yes, for comunity benefit as well (because making community happy is a fun too).
And it is more fun for me to make things more featureful rather then make them fast (While community may benefit more from fast one. In short term.).
Surely you have noticed long pause between my promise to bring SSPL to all platforms where such tool is needed and present days. And that SSPL was not introduced even for platforms I have access to (and where it is actualy working as a proof of concept). And why standalone bootloaders for trinity and hermes was not released while it would not take any time for me at all. What happened ?
Does I have no time to code during last month ? Or have I been bribed by HTC not to do so ? Or maybe I'm going to post "give me 1000$ and you would get SSPL for your device" ?
No.
After some feedback 'bout several bricks and thoughts about new wave of upcoming HTC devices I came to certain decisions about what future version of SSPL would look like. It was designed that there would be no device speciefic versions of SSPL and SSPL itself would not contain any (HTC copyrighted) binary blobs. Instead it would be universal (PXA/OMAP/S3C) loader and universal patcher (which (with some good luck) may be able to produce patced bl for new device in couple of clicks) and set of romimage manipulating tools (to [re]sign and check for software bads) too. I do not mention bootloader patches improvement for more safe flashing and may be software bads recovering. As you can see this is quite complex job wich can not be done in couple of hours. And more - hacking is almost always fun for me, coding - just when I'm not too tired with my main job
Many (if not most) parts of this is done: loader successfully works on all three platforms, fuzzy ARM patcher algo is near to completion, image manipulating tools are not a problem at all (but even so they need to be coded and this needs time).
But as for now I lost fun in providing universal solution - most users won't notice any difference and developers... now there is a porter among us so there is no need to worry about new device support any more
(non-universal) SSPL for breeze and wizard as well as standalone bootloaders (with slightly renewed patches) would be released in days, for other devices as soon as I'll get access to them for testing purposes. As this is much more sooner than planned release of universal loader+patcher then community benefit (for now).
I dont understand Des behavior... what's the deal of Olipro rip/port/transform Des's code to an earlier version ?!
Click to expand...
Click to collapse
Let me explain: I have some relations with darker side of the force than hacking htc pda is. Among siths taking somebodys ***ck or ****en and "porting" it to newer(older) version of program called ripping. Siths do respect copyrights in their odd way and pay no respect to rippers. Nothing more
Des said:
Do you whant more ?
Click to expand...
Click to collapse
I do see your point here, obviously it is a double edge knife because it allows to easily brick the device if the flashed file is not well formated, but on the other side it also prevents the device to completely brick because of a bad radio flash which seems to be the most common brick for hermes devices, and it is starting to happen on trinity too. That's why first thing I asked was if it is possible to implement something to prevent bad blocks in NAND.
Des said:
Many (if not most) parts of this is done: loader successfully works on all three platforms, fuzzy ARM patcher algo is near to completion, image manipulating tools are not a problem at all (but even so they need to be coded and this needs time).
But as for now I lost fun in providing universal solution
Click to expand...
Click to collapse
That's amazing, I hope you reconsider your decision as I (and sure a lot of other individuals too) would really like to see something like this happen.
We are curious by nature, I must admit second thing I did after you released SSPL was loading it on IDA (first was trying it on my hermes) and try to see exactly what you did. I just did it out of curiosity and trying to learn something from your impressive work. I was a bit disappointed because you didn't release the patches so I "had to" reverse what you did in order to understand it, but this was also challenging and fun for me. I for sure learned something on the process and finally I left it because there where some sections I couldn't re-base correctly on IDA.
I think Olipro just had the same feeling as I had, and he didn't release the Hard-SPL in the aim of ripping your work, but in the aim of helping the community reduce the number of bricks because of a bad radio flash, and he also gave you credit for your work, so I see this as a team work and not as ripping. I hope you can see my point too and forgive Olipro's audacity, and of course continue the development of such universal bootloader tool... in the end we're all here because we love to squeeze the devices and we all do this for fun and learning, don't you think?
second thing I did after you released SSPL was loading it on IDA
Click to expand...
Click to collapse
I is perfectly normal. Moreover if I were you that would be the first thing I'l done (to look what piece of s**t I'm going to run on my hermes)
I was a bit disappointed because you didn't release the patches
Click to expand...
Click to collapse
Why don't you asked me then ? I rarely refuse to explain how things works. But of course I'll ask you for some sort of NDA for a while
and finally I left it because there where some sections I couldn't re-base correctly on IDA
Click to expand...
Click to collapse
Rather strange. SSPL is ordinary executable produced by VS 2005. No disasm/debug protection. Loaders code is packed mainly to save 100kB of space and to hide code from too curious but unexpirenced eyes for their own sake as a second task.
so I see this as a team work and not as ripping
Click to expand...
Click to collapse
Look... I'm not a DMCA, software patents, etc fan at all. But things should be called by their real names. Derivative work is something that utilises somebodys code but brings many very own features to it. I hardly could avowe hermes 1.04 bl as derivative work because it contain at least single additional bit of patch. But bit-to bit exact copy (except the version number) announced as
Olipro said:
Hard-SPL, Or Flashing any ROM, and staying Brick-safeWell... I did it for Hermes, tomorrow I'm doing it for Trinity, this is just here to make sure I get round to it... and to let you folks know it's in the pipeline
Click to expand...
Click to collapse
is no more then a rip.
Well now everyone knows that Olipro isn't the master mind behind the solution (because you're).
So, now we all know that the copyright is yours and we're thankful for that. And you've the respect of alot of other users as well .
Des said:
Why don't you asked me then ? I rarely refuse to explain how things works. But of course I'll ask you for some sort of NDA for a while
Click to expand...
Click to collapse
Because I prefered to have some basic understanding of it before asking, and wanted to find out by myself... I tend to learn more by looking than by just asking and of corse i feared the NDA
Des said:
Rather strange. SSPL is ordinary executable produced by VS 2005. No disasm/debug protection. Loaders code is packed mainly to save 100kB of space and to hide code from too curious but unexpirenced eyes for their own sake as a second task.
Click to expand...
Click to collapse
Yes, that was not the problem... if I recall correctly I managed to extract IPL and SPL with PE explorer, but then I wanted to compare the extracted SPL with an unmodified SPL, I set the base address to 0x8c080000 and found something around 0x8c040000 which I did not know how to interpret correctly... probably I was one of those curious but unexperienced eyes
pof said:
and wanted to find out by myself...
Click to expand...
Click to collapse
then you should be glad to find it bit scrambled - there is no fun in reversing easy things
and of corse i feared the NDA
Click to expand...
Click to collapse
Dealing with sensitivity material require some level of conspiracy I wonder how long security bypass patch would work now (not closed in future roms). Of course there are many other ways to bypass [almost any] sec check but that was realy funny like a good joke
Des said:
no more then a rip.
Click to expand...
Click to collapse
Sorry, that's out of context; I'm not inferring anything more than that I extracted your patch, which might I add consists of a single NOP and two address deletions (although of course, identifying them is the kicker).
A while back... I asked you about it and was stonewalled by you; you offered me nothing, just some info that you were working on something or other further to it... I can only guess you assumed I'd be unable to extract the clean bootloader image and thus discounted me.
resultantly, I recently got tired of waiting and dumped the SPL. I suggest you head over to the Hermes forum where you will find that I haven't secretly ripped off your work and then called it my own.
I ripped the SPL out for myself, spoke to pof about it, and then decided that it'd be a good idea to port it back to the old SPL and release that, which I did.
I never got a chance to release this one, but all I was going to do to it was remove the button press patch... I did not plan to take any credit for this Trinity ROM whatsoever.
anyway enough of the *****ing and ranting. I hope we can move on; I appreciate you're clearly pissed that it got released as a regular NB Image but I only hope you'll get over it.
Also... I've made a modification to the SPL to ignore bad NAND blocks... not a clue if it works, need someone who's bollocked up their NAND to test it... obviously you need a way to get it on your phone first.
Olipro said:
Sorry, that's out of context
Click to expand...
Click to collapse
I've intentionaly quoted whole topic-starting post to not to be out of context.
which might I add consists of a single NOP and two address deletions
Click to expand...
Click to collapse
the smaller is patch - the better it is. And those are not addresses btw.
of course, identifying them
Click to expand...
Click to collapse
You've got the point.
ps: Same things can be done in different ways. And I can't say that I respect ways you choose to help the comunity (this relates not only to ripping sspl). I do believe that you have good intentions in your mind but hell is paved with them. This is only my own opinion wich is not subject to discussion.
pps:
anyway enough of the *****ing and ranting
Click to expand...
Click to collapse
surely.
i need a guidance on how can i work with the kitchen rom cooking or what ever you called it. and one last question, after i used the hardspl file, my camera arent working, is that common problem>...
Before you go any further, do some more research. There are too many details, and everything you need is in the device sub-forums, wiki, and else where.
You don't even know what it is you are referring to!
TheChampJT said:
Before you go any further, do some more research. There are too many details, and everything you need is in the device sub-forums, wiki, and else where.
You don't even know what it is you are referring to!
Click to expand...
Click to collapse
2nd, when the question starts with "kitchen rom cooking or whatever you called it", the next post is "my phone won't respond to anything, the screen is black and I don't know why".
Black93300ZX said:
2nd, when the question starts with "kitchen rom cooking or whatever you called it", the next post is "my phone won't respond to anything, the screen is black and I don't know why".
Click to expand...
Click to collapse
Black are you causing trouble again?
Good Good!
And Black is 100% right, read everything 2134i932041234234 times before you make yourself an expensive paperweight.
PS. Moved to Kaiser General, Redirect Dies after two days.
Question for the Android gurus out there:
Is there any inherent reason we can't have network location and/or aGPS running on Android? I love all of the apps available that use my location to find restaurants, etc. But these are essentially useless with the current state of the GPS, which takes several minutes to achieve a lock, and loses it as soon as it goes to sleep.
Are these things inherently unachievable, or is it just something we haven't delved into yet?
TIA
Mike
golfnz34me said:
Question for the Android gurus out there:
Is there any inherent reason we can't have network location and/or aGPS running on Android? I love all of the apps available that use my location to find restaurants, etc. But these are essentially useless with the current state of the GPS, which takes several minutes to achieve a lock, and loses it as soon as it goes to sleep.
Are these things inherently unachievable, or is it just something we haven't delved into yet?
TIA
Mike
Click to expand...
Click to collapse
you have to tell us what build you are running. agps works fine for me with myns warm dount. google location does not. has to be unchecked
golfnz34me said:
Question for the Android gurus out there:
Is there any inherent reason we can't have network location and/or aGPS running on Android? I love all of the apps available that use my location to find restaurants, etc. But these are essentially useless with the current state of the GPS, which takes several minutes to achieve a lock, and loses it as soon as it goes to sleep.
Are these things inherently unachievable, or is it just something we haven't delved into yet?
TIA
Mike
Click to expand...
Click to collapse
i guess you didnt read my search before asking thread
cp0020 said:
i guess you didnt read my search before asking thread
Click to expand...
Click to collapse
I guess you didn't read my question. It has not been answered anywhere here before, I follow these forums daily.
But thanks, anyway, for the useless and douchebaggy post.
golfnz34me said:
I guess you didn't read my question. It has not been answered anywhere here before, I follow these forums daily.
But thanks, anyway, for the useless and douchebaggy post.
Click to expand...
Click to collapse
As incubus pointed out, aGPS works fine with Myn's Donut build. It lacks Location though, but the port is still not perfect, which is why we still have some features that might not work properly or at all.
As much as I don't agree with the tone in your post, I have to agree with you in the sense that cp0020's answer was a bit out of place. Having said that, try to ask the cook for the particular build you are concerned with about the issue that you are having by posting in the respective thread, rather than opening new threads. This way, it will make the forum cleaner as threads with questions have a bad tendency of repeating. Thank you for understanding.
golfnz34me said:
I guess you didn't read my question. It has not been answered anywhere here before, I follow these forums daily.
But thanks, anyway, for the useless and douchebaggy post.
Click to expand...
Click to collapse
dude if your gonna act like a little kid and have no respect for anyone, especially in this forum then you shouldnt be here. and there are tons and tons of posts about this so dont even sit there and get an attitude with me cause i said to search. if your gonna put a new thread out then you need to say that you have searched the forum and cant find anything. that simple. now if your gonna continue to to be apart of this community then you need to change your attitude and have some respect for others. hope im being clear enough!!!!
THis thread has been reported and due to the lack of respect to other users (against xda rules) this thread is now closed.
Several people have stated that this subject has been covered previously.
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?
beginning to think this phone ant going to get any development from the activity ive been seeing on this site
Do we really need a second thread about exactly the same as your thread at https://forum.xda-developers.com/moto-g6/help/dose-one-phone-t3816584 ???
development is there, follow the treble roms.
timelessxiii said:
beginning to think this phone ant going to get any development from the activity ive been seeing on this site
Click to expand...
Click to collapse
I know someone who can develop on your phone