For all to see and understand why I've stepped away from the Umeox x201.
Here's the problem. The broken and unsecure firmware affects every x201 Umeox makes. So it doesn't matter if it's a TS or a Callisto 100 or a Pearl AW-414/420/421. The firmware is broken on all of them. So it's not a TS issue, it a Umeox issue.
The unsecure status of the firmware is not a simple set ro.secure to 1 as it's already ro.secure=1. This is something completely different as even with that it still runs in an unsecured mode. Here's the thing, this has been an issue for over four months. If who ever is compiling the firmware can't fix this in four months, fire them.
Here's another example. The "EU 2100 working sensors" firmware I released was after ditching the Omate TS kernel and using one I was able to get my hands on from the Callisto 100. It is still not fixed in the official firmware and forces the end user to flash firmware to their device to get working sensors. Some of these folks have problems with even basic computer usage leaving it to independent devs to fix and provide technical support for a Umeox created problem with no direct access to the resources needed. At this time, iconBIT is the only one that even posts their firmware with at least partial change logs and makes it publicly accessible.
Now before the "different B2B partners require different setups" is said. All those changes are in the system partition. If anybody with a copy of SP Tool and two different firmware releases can can swap out the system partition images and make it flashable then there is no reason that Umeox can't do the same. You build one, maybe two, fully working base firmwares and have a system partition image with the needed changes for each of you B2B partners. This eliminates having to build a full firmware for every individual model for every B2B partner.
I'm burnt out from supporting ALL your B2B partners customers as well as KS backers, trying to fix broken firmware with little resources on top of trying to have a life with my family.
So it comes down to this. Umeox either needs to fix the problems they created or ditch there own firmware and replace it with properly supported, secure and working firmware or I will not be coming back. This doesn't apply to just the TS but all x201s being sold.
I will continue to update the [INFO] Everything for folks but as far as any active development on any x201 running broken Umeox firmware. I'm done.
Just for the record, I can understand your frustration (and I've just been following along the story, I still haven't even gotten my KS reward watch yet), and think you've gone above and beyond the call of duty on this one. That you've had to do it in your spare time, and acted as an intercessionary figure between the "manufacturers" (particularly Omate) and the public is an incredible act of generousity towards the end users, and I don't know about everyone else, but I appreciate it; it was one of the few bright lights shining in an increasingly murky and regret-tinged Kickstarter backing.
So thank you, Lokifish, for your hard work, and if I should ever meet you in person, first round's on me.
@Lokifish Marz
Mate - you are totally right and I support you.
You were here, buying devicesand fixing their faults...why?
You worked so they could relax?
All developers should stop everything related to Umex - I'm sure someone will finally react...
You/we could offer support and help but that's not our company and our obligation, especially if they totally ignore they obligation and don't offer any support...
Two years...yeah...my a*s
I still haven't got my device - early October devs edition (O.K that's Omate, but still) and when it finally arrive in may I should work "for them" - NO, ABSOLUTELY NO
Such thing like that what LLP said - to use custom ROM, and to said that to all who wants working device is ridiculous and wrong...
O.K for us backers, that's KS but some guys actually ordered and paid that watch in "store"...
O.K now I'm talking about Omate but I understand what you are saying and support you, actually I'm not supporting you, I beg you - stop with support - they must get what is their job and obligation.
Sent from my C6903 using Tapatalk
Lokifish Marz said:
For all to see and understand why I've stepped away from the Umeox x201.
Click to expand...
Click to collapse
Disappointed by your decision Lokifish but fully understand your reasons, haven't received my TS yet and so haven't really benefited from your work. But without the work you have done that device won't succeed, not sure it will succeed at all now unless Umeox take note and act on this.
Thanks again for the work you've put into this, and just to emphasize and echo your priorities; THERE'S NOTHING MORE IMPORTANT THAN FAMILY.
Totally support you.
It's always a difficult decision whether withdrawing will force vendors to get their act together or redoubling efforts to engage will get results from vendors. You really can't know.
But you can make yourself happy, and that's what counts the most.
Thank You!
Lokifish Marz said:
For all to see and understand why I've stepped away from the Umeox x201.
Here's the problem. The broken and unsecure firmware affects every x201 Umeox makes. So it doesn't matter if it's a TS or a Callisto 100 or a Pearl AW-414/420/421. The firmware is broken on all of them. So it's not a TS issue, it a Umeox issue.
The unsecure status of the firmware is not a simple set ro.secure to 1 as it's already ro.secure=1. This is something completely different as even with that it still runs in an unsecured mode. Here's the thing, this has been an issue for over four months. If who ever is compiling the firmware can't fix this in four months, fire them.
Here's another example. The "EU 2100 working sensors" firmware I released was after ditching the Omate TS kernel and using one I was able to get my hands on from the Callisto 100. It is still not fixed in the official firmware and forces the end user to flash firmware to their device to get working sensors. Some of these folks have problems with even basic computer usage leaving it to independent devs to fix and provide technical support for a Umeox created problem with no direct access to the resources needed. At this time, iconBIT is the only one that even posts their firmware with at least partial change logs and makes it publicly accessible.
Now before the "different B2B partners require different setups" is said. All those changes are in the system partition. If anybody with a copy of SP Tool and two different firmware releases can can swap out the system partition images and make it flashable then there is no reason that Umeox can't do the same. You build one, maybe two, fully working base firmwares and have a system partition image with the needed changes for each of you B2B partners. This eliminates having to build a full firmware for every individual model for every B2B partner.
I'm burnt out from supporting ALL your B2B partners customers as well as KS backers, trying to fix broken firmware with little resources on top of trying to have a life with my family.
So it comes down to this. Umeox either needs to fix the problems they created or ditch there own firmware and replace it with properly supported, secure and working firmware or I will not be coming back. This doesn't apply to just the TS but all x201s being sold.
I will continue to update the [INFO] Everything for folks but as far as any active development on any x201 running broken Umeox firmware. I'm done.
Click to expand...
Click to collapse
:good: Thank you sir for all you have done, even with all the BS from backers, OEM's & general support help requests. I hope someday they will just release all info on anything using Umeox.
I have just received my shipment from TS today & now read you are out, I wish you return someday.
Thanks for what you have done. Just got my TS the other day, so aside from the minor stuff I have figured out, not yet comfortable giving big time advice.
I do thank you for the patch & the root. Helps those out who do need it.
Good luck with your endeavors. Hopefully you will find what you are looking for. I am sure there will always be some of us here.
The Shagg said:
:good: Thank you sir for all you have done, even with all the BS from backers, OEM's & general support help requests. I hope someday they will just release all info on anything using Umeox.
I have just received my shipment from TS today & now read you are out, I wish you return someday.
Click to expand...
Click to collapse
They know what they need to do. It's a matter of will they do it and how long will they take. Til then I'm just a guy updating the info index thread and popping in from time to time.
I'm selling my watch to someone who has the patience. Loki you have been a great help to us all Thank you.
Sent from my SM-N900V using Tapatalk
This is an absolute travesty
But thank you for all you have done!
Sad to see you go before I even got my Omate. But as everyone else has said, I completely understand your reasons. Thanks so much for all your hard work
Thank you.
Thank you for all your work. Selfishly, I am very sad to see you leave the project, but support and understand your reasons. All the best with your baby girl.:good:
Thanks for all your work. Hope to see you back if they ever get sorted out.
Hi Locki, said to see you go but I am sure you will be back soon. Bin there, done that.
Some other company I will not mention did the same. Well, eventually they stopped production for 6 months due to well, uhmm, me making some phone calls and writing the detailed truth on forums. Got a personal call from EMEA production manager (which I didn't even knew) a few days later to solve this "problem". And we did. I am sure something like that will happen with you.
And if not, then OmateUmeox will soon be just another startup who failed big time and LLP will have a lot to think of.
But they are not stupid, money will soon be running out otherwise.
If we (Backers, supporters, owners of a Umeox/TS/Pearl whatever) want Locki back and want a good Firmware then it's up to US (as in WE) to make that happen. Locki's leaving is a big sign to LLP, Umeox and whoever is involved. And to us it's the same big sign.
Let's give back what Locki did for us and what Locki's intention still are. We all want a better product.
WE can make a difference. Let's get creative and find ways how we can convince Omate/LLP/Umeox that this is NOT how we want to continue.
WE made the TS by funding it. So WE have the power to do that too.
Thanks Lokifish, seriously. I don't have my TS yet, but I am relying on your patches and stuff to get it working properly when I do get it.
Thank you very much for your hard work, and though it's sad to see you go, I can totally see why it has happen. Take care and enjoy the time with your family =D
I am really greatful for all Locki's work, but now what? What can WE do? What's Laurent LePen plans? Where can I get any information about what's cooking?
I'm still providing low level support but deving has stopped. there is only so much that can be done with the current firmware. Until source code is obtained from MediaTek, do not expect to see any CM/AOSP/AOKP releases. At least for now folks on the patch or are properly rooted are safe. I know it's not perfect but please keep in mind the ROMs and MODs of any sort are a very rare thing on Mediatek powered devices.
Lokifish Marz said:
I'm still providing low level support but deving has stopped. there is only so much that can be done with the current firmware. Until source code is obtained from MediaTek, do not expect to see any CM/AOSP/AOKP releases. At least for now folks on the patch or are properly rooted are safe. I know it's not perfect but please keep in mind the ROMs and MODs of any sort are a very rare thing on Mediatek powered devices.
Click to expand...
Click to collapse
thanks a lot,
I guess my lesson will unfortunatly be never buy a Mediatek device, never again. I got a nexus 4 with OmniROM on it, and I thought something similar could eventually be possible on my TS. Anyone knows where can I transmit my disappointement to Mediatek and let them know that for this prevoius reason, I will never their product again?
Related
The Cingular forums are now shutting down discussion re the new ROMS ... nice ... just trying to keep us from helping each other out (you would think it would be to their benefit, so folks don't bug their non-existent customer service)
see here for all the gory details.
This is getting more and more ridiculus by the day
Hallllllo M$ and providers. when we buy a device we ALREDY get a licenced WM, what's your problem???????????????????????????????????????
weinson said:
The Cingular forums are now shutting down discussion re the new ROMS ... nice ... just trying to keep us from helping each other out (you would think it would be to their benefit, so folks don't bug their non-existent customer service)
see here for all the gory details.
Click to expand...
Click to collapse
the thread has been resurrected for the time being...no idea how long that will last though.
This is just like Cingular, I have been told that this update would be out since Dec. by Cingular sales and it never has. We cannot help it if Cingular is so slow on getting updated services out. If they would put more effort in service and less on what they are going to call them selfs maybe they could supply better service. I have 19 cingular accounts and may move all of them if they don't get there act together.
Steven -
Do what my wife did, she is part of the State of FL gov contract on Cingular and she has a fair bit of power in moving accounts so she basically said if you can't support your gear with updated ROMs maybe she would move accounts somewhere else.
I doubt they care but who knows...
so many dumb-ass flashed their phones w/o reading the instructions, bricked their phones and start to call Cingular/ATT for help/repair/replacement. Next thing we know, MS is trying to remove all ROMs, ATT removing thread about new ROMs....
That's y we should make this community go underground, ban the suckers who don't read, link ROMs to rapidshare or other similar sites instead of this site's FTP server.
It's sad to see we have to remove the ROMs but I wouldn't blame MS or ATT for asking XDA-developers to do so.
Oh, btw, if you guys care go sign the petition, show us some supports even if we dont get what we want.
peace.
It's the War on Common Sense. And since all of us are a minority here, ignorance and misinformation prevail.
The main reason Big Business does this is because the executives are a much older generation that is scared and terribly confused by the Internet. So to them, we're all looking to ruin their business by making their phones work in ways they didn't intend for them to be used. What they don't know is, our solutions are much better than the ones they provide (hence the void we're filling by being here, supporting, and working out their phones for free) and if they were to release even just half of the ROMs the XDA community cooked up, they'd have a much happier customer base.
steven814 said:
This is just like Cingular, I have been told that this update would be out since Dec. by Cingular sales and it never has. We cannot help it if Cingular is so slow on getting updated services out. If they would put more effort in service and less on what they are going to call them selfs maybe they could supply better service. I have 19 cingular accounts and may move all of them if they don't get there act together.
Click to expand...
Click to collapse
Cingular/AT&T is pretty much the only carrier with even a _leaked_ rom... so how are you going to say that they're slow? They're actually ahead of the curve, in my opinion.
The 8525 came out in November. I'm pretty sure that there must have been some miscommunication if you recall someone in December told you the Rom would be out tomorrow (or any specific immediate timeframe). "Soon" is not necessarily "one month" or less. I think sometimes we hear and preceive what we WANT to be the truth based on what we actually _did_ hear. I mean, as far as I can tell, HTC just released the 3.3 rom to carriers a matter of weeks ago. Cingular has been working on things other carriers aren't doing, too (PTT, Cingular Video, etc.) So they're putting more into the rom than most of our European counterparts need to (with the exception of video calling... yet.)
I guess what I'm saying is that we, as enthusiasts, expect more than the average customer. And as for Cingular / AT&T, of course they don't want to be providing support for an unofficial and likely unfinished rom. Honestly, having inexperienced and impatient Cingular customers reading about this leaked rom and trying to put it on their devices prematurely would certainly cause a terrible amount of problems. Again... it's _leaked_ and _unofficial_, so they should not feel like they have to support it.
Just my 2/3 of a nickel.
GliTCH82 said:
It's the War on Common Sense. And since all of us are a minority here, ignorance and misinformation prevail.
The main reason Big Business does this is because the executives are a much older generation that is scared and terribly confused by the Internet. So to them, we're all looking to ruin their business by making their phones work in ways they didn't intend for them to be used. What they don't know is, our solutions are much better than the ones they provide (hence the void we're filling by being here, supporting, and working out their phones for free) and if they were to release even just half of the ROMs the XDA community cooked up, they'd have a much happier customer base.
Click to expand...
Click to collapse
I disagree. I believe the truth is if they released half the roms on here, they're customers WOULD be confused, scared, and lost because they have no idea what rom they should be running. They'd have no idea why something doesn't work perfectly on one rom and better on another. Or why one radio may or may not be better. Think about how many people on here aren't reading everything they need to and bricking or nearly bricking their devices. And these are the ones SEEKING the information. The average 8525 user on Cingular's network isn't quite as interested in this stuff as we are here.
Knowledge is power, but unstable power is chaos.
Think about it.
Xda-Developers is a great source for those seeking to know more about their devices than just its typical uses. But anyone who really wants the knowledge will seek it out and find it (just as we all did). Throwing an incomplete rom at the average lawyer who needs Microsoft Direct Push and not much more is likely to cause more problems than it's worth for AT&Tingular as well as for us (because we'll be the ones trying to clean up the mess).
I think I should sign off on this before I infuriate some of those out there who just want to vent their frustration. And we all know the company with the dollars is always a great target to do that.
Does't surprise me in the slightest.
I am sure many OEMs and phone companies are sick of people bricking their phones and claiming warranties (of course they never admit to using cooked ROMs or even trying to upgrade them - 'Just woke up one morning and it wouldn't boot up').
I enjoy this forum too but don't tell me it doesn't encourage people to do things they shouldn't, and are not willing to take responsiblity for.
esseff said:
I enjoy this forum too but don't tell me it doesn't encourage people to do things they shouldn't, and are not willing to take responsiblity for.
Click to expand...
Click to collapse
I have to disagree with that statement... I wasnt aware that giving warnings to the users that flashing their phone could brick it and that they need to read and make sure they fully understand what they are doing before they do it was encouragement... I know that when i came to this board and saw the warnings about flashing cooked roms it freaked me out.. i was registered for several months before i ever made a post, spent countless hours reading all the threads to make sure i fully understood my device before i did anything to it.. its the people that dont read and brick their phone that want to come back and blame us for their mistake.. This is a developers board and quite frankly alot of us go out of the way of development to help people in need... we especially go above and beyond any kind of help that you would recieve from your provider
My 2c
I have to agree with shogunmark. I know I made very sure I read every last thread and wiki before I attempted anything as rash as upgrading a Radio stack. This was because of my fear of bricking the unit, because so many people warned it could. I was even willing to endure the mass "RTFM" and "RTFW" flaming if i wanted to make sure I understood everything correctly before risking my device.
I believe the largest part of this community are users that gather here in the spirit of sharing the knowledge about the device to encourage greater growth of the community- the more people, the more mods & hacks & cracks and experiences will become part of the knowledge base.
yet im still trying to figure out how "MAY BRICK YOUR DEVICE" warnings are encouraging...
Come on guys!
Sure there are countless warinings but simply the enthusiasm and excitement amongst the experienced crew, when a new possibliity appears (GPS, WM6, AKU this, AKU that) causes less experience people to get caught up in it.
I'm not for one minute discouraging XDA developing, just TAKE RESPONSIBLILITY IF YOU BRICK YOUR DEVICE AND DON'T GO CRYING TO THE OEM OR TELCO FOR WARANTY. Pay for your mistake and buy another.
I have seen, on this forum people advising others to go back to their supplier with bricked devices and try to get a warranty. It is hard for the supplier to argue with someone who says their device 'Just stopped working', when infact they bricked it, and in the spirit of good customer relations they often replace it. Why wouldn't suppliers be negative toward forums like these when they are placed in this situation.
Sigh... I've been told that HTC's single greatest returned device is the Wizard followed closely by the Hermes. Reason: bricked.
We post the warnings, but plenty of people don't take the time to fully understand then brick their devices anyway (hermes is especially bad in this respect). Then they try to return them.
In many ways, this is the manufacturer fault b/c they are trying to thwart users who try to upgrade or change their devices. Hermes development feels like spy vs. spy sometimes as we crack something and then the next bootloader/radio bootloader comes out. Consequently pre sspl hermes flashing was damn near rocket science. Problems were rampant. Heck, I even saw one poster try to flash the original signed_nbh into the OS area with the 1.01MFG bootloader
They're all gonna try it. There's no minimum IQ required to be a member here.
Ideally, we need to find a way to bring any HTC device back to life from brick status. It's only corrupted memory after all. If the correct bytes are written, the software works. When I did SE phone hacking, there were such devices. Because of this, users with bricked phones could take them to their nearest SE phone center and they would re-flash and un-brick (for a price of course).
This ridiculous swapping of bricked devices is what needs to change. Posters need to take financial responsibility for phones they brick. HTC needs to make their hardware flashing system available to Operators at phone centers.
Unfortunately, this won't be the case. Instead, they'll go after us because they can see an ROI impact in terms of bricks. What they can't see is the intangible increase in sales that we stimulate or the intangible loss of future revenue that shutting us down represents.
Sign the petition. Get your friends to sign it. Get it posted on other forums. Get it into the news. Operators and M$ need to be able to see this intangible.
on the other hand with the hermes and returns... we just got to a point to where we could brick them less than a month ago... most of the returns before then was by manufacturer fault, i know this because i was one of them, i had a ton of bad blocks in the wrong spot....
its to bad we dont have an easy rom kitchen for these.. something that would make it damn near impossible for the person who cant read to brick their device.. i dont know.. im tired and going back to bad, my post isnt making much sense to me right now
but i do agree with you sleuth!
Wow... check out the attitude here...
http://forum.xda-developers.com/showthread.php?t=294365
Kinda proves my point.
Add a success story here - mainly because I am competent enough to read and ask the right questions when there was vague information.
I am not new to flashing/modding, but the Hermes definately takes it to a new level.
The difference with me, should I ever brick my device - I would just deal with it. I came here with the understanding that the tools available to us come with an increased risk should you not actually understand what you are doing. You need to be aware that you should own up to the possible mistakes and not try to send a bricked device back for warranty....
Two individuals who make this place so great - Pof and Sleuth. Pof has done such a great job with the wiki and his tools - all you need to do is take a few days to read about the device and the steps you need to make. Sleuth brings a different element (and his programs) to the forums and has the patience to point questions to the right areas of the wiki.
My advice - if you plan on unlocking/upgrading take at least a week and read the wiki. Make sure you have all the pieces needed to complete what you want to do. Sync your device and backup all your info - be prepared to hard reset and start from scratch - twice in some cases.
Set aside plenty of time that your phone will be down during this process.
This site is by far the best there is - it's a shame that people rush into things some times.
Sleuth255 said:
Ideally, we need to find a way to bring any HTC device back to life from brick status. It's only corrupted memory after all.
Click to expand...
Click to collapse
HTC should put JTAG out in its new models
Seriously, it's a big flaw that every official ROM image overwrites th bootloader, even with the same version. The whole firmware history teaches that the bootloader should not be touched by end user.
So, the solution is to make custom ROMs flashable by parts, w/o affecting the bootloader. This should prevent bricking... does not revive existing bricks though...
But your overall point is good: manufacturers get angry because of a lot of returns, and care shell be taken to calm them down.
on another note about the cingular boards... i got banned there was a thread about the lack of good moderation in the HTC board over there, i spoke my piece and got banned... it wasnt even bad, just offered some suggestions.. so much for contructive criticism and free speech..
Hi all!
I sent DJ_Steve money for coffee a while ago, and I was hoping he would get us a nice ICS build for our devices. I still hope him to do so, but I want to ask two related questions here:
How many of you Streak 5 owners would chip in, say... 5 or 10 USDs to get us an ICS upgrade?
And for you skilled developers out there: how much money and kudos would you think would be necessary for you to continue the development?
I have two of these beasts. I really enjoy the user experience, and I don't want to have to buy a new device in a while. I would gladly put down another 5 or 10 bucks to see this happen.
Would you?
Cheers!
I'd already donated to djsteve when he got gingerbread out so I'd be down for another 20 bucks.
ye id sling him a 20
I would gladly donate 20 dollars to the developer who makes a working ICS port and disables the capacitive buttons.
Pledges like this have gone around and around for the last 6 months....
AFAIK ICS wont make it to the Dell Streak 5 any time soon because the drivers still need to be reverse engineered to make it work.
Unless Dell release the drivers ICS on the 5 wont happen
ashr said:
Pledges like this have gone around and around for the last 6 months....
AFAIK ICS wont make it to the Dell Streak 5 any time soon because the drivers still need to be reverse engineered to make it work.
Unless Dell release the drivers ICS on the 5 wont happen
Click to expand...
Click to collapse
Ashr is on target (straight from DJ_Steve's twitter to this thread), unless there is somebody out there with lots of time on their hands to crunch code, not going to happen. Plus Steve said the other day he is getting close to the boiling point, because too many people are bugging him, that he might just stop ICS development all together. Good thought and all that, but think it is a bridge too far to see ICS on Dell Streak 5 and the fault clearly falls on Dell's shoulders. Dell could have released the code a long time ago, but chose’s not too and hides behind very weak excuses. Other companies have released their source code and very good ROMs are the result of it.
Is there an easy way to publicly ask Dell to provide all the necessary tools and code to allow the devs to get us an ICS for our Streaks?
The way I see it, Dell looses nothing by providing with such tools, and although indirectly continue to support the device which is a good thing. Not doing it doesn't make much sense, and I'd see it as *bad business policy*.
Obviously you hadn't seen the press release from Dell where they slammed their Android devices because of their unrealistic expectations regarding Android as well as their lack of any marketing whatsoever.
Dell doesn't care about "bad business policy" regarding Android, and even if they did there's nothing they can do about it. Reason why is they didn't develop the Streak. It was developed for them and the company that did the developing has shown absolutely zero interest in releasing the sources for their drivers. Sorry, but the only way the Streak is going to see ICS is if the drivers are reverse engineered.
It's really dell's job to get the whole driver source mess sorted out.
While Qisda did build the hardware and make the rom, they did it on contract for dell. Even if they wanted to they couldnt do it without dell's blessing.
It's the equivilent of flying on a plane, if your service was bad, something went wrong, plane crashed; you dont contact/blame boeing/airbus, you blame the carrier. Even if it was boeing/airbus's fault you're still supposed to blame the carrier as it's their problem. The only time you'd lay the blame on the plane maker directly is the short window (in a perfect world) where an issue is found but they have yet to notify the carriers that run that specific model.
Though there's also the fact that dell may not have the rights to release it, as who knows what the ownership situtation is with it.
A similar example would be if planes had some small piece of classified tech so that it cant be fixed by their guys, they'd have to mail it in and get a new one or something.
Keep in mind both examples are of course gross oversimplifications, there's always gonna be exceptions and whatnot.
The majority of the sources for each individial component is available in one form or another due to other devices using the same parts, but having the source and being able to glue them together into something worth using are two entirely seperate worlds. The gap to bridge is still pretty damn big. (also keep in mind drivers still have to be updated for ICS, gb source level drivers still arnt enough by themselves unless they're coincidentially unchanged from GB -> ICS)
Bump for some ics
I working since a few weeks on an ics rom, but I can't say how long it will take because I don't have much time to make further
I'm down, I'm holding off on getting the Note for two reasons... 1. Of the wack a** posts and newbies w/ the note that just refuse to believe the device has a flaw... The "Shipping" Thread/ Post had to be one of the g**** post I ever witnessed lol!... Plus the folks that swear its worth $300 bucks but cried a river to ATT/BB when it dropped to $150 within a day but then say they would pay $300 for it again : /
2. The Streak has served me well for the past 2yrs...I'm loyal to things that are loyal to me.
I want ICS on this Device big time... If not, further dev on CM7 and/or CM9.. If someone can make it happen, I will make that individual a happy person..pz
I'd happily donate $20+ for ICS or CM9!
Thanks to all the developers out there that have kept the streak alive!
bauner said:
I working since a few weeks on an ics rom, but I can't say how long it will take because I don't have much time to make further
Click to expand...
Click to collapse
Any updates to your status? I'm holding off for dear life for a upgrade/update for CM7/CM9 or ICS..If not then it's fine and I greatly appreciate everyone's efforts, this just may be the last night I use my beloved streak as a full time phone... almost 2yrs, same device the entire time..
I'm bumping this thread because it looks like DJSteve may be up for the task. http://forum.xda-developers.com/showthread.php?t=1992263&page=2
It has come to my attention that a few people have been misunderstanding a few recent posts by myself. This is post is to clear the waters up a bit and to explain my position as a developer here on XDA.
As many of you guys know, we're probably the most lively "dead" device on XDA. At least in my opinion that is. We have been through a lot as a community but we still manage to survive. But recently things have been getting a little tense.
I received this device last summer like most of you have. When I got it, I immediately started figuring out how to get CM7 on it. Problem is that it was my first Android phone and with all the ways that Motorola locked it down I had a lot to learn and no time to learn it. After I learned off and on how to get things working on the X2 during the NO free time I had last fall I cranked out a pretty much solid CM7 in a week.
Now for the explanation for CM9/ICS. Most people probably think that since I could crank out CM7 so fast that I would be able to do the same with CM9 and make it just as good and amazing as CM7. Although I had it booted on the first build, it was FULL of errors and the touch screen didn't even work. ICS and CM9 is definitely not as easy as CM7. CM7 was already a year and a half in the making and had most of the problems worked out on all the devices that when it finally came time for us, it would just as smooth as butter as soon as it was booted. CM9 hasn't had time to develop into a "smooth" ROM for most devices; especially non-official like ours. The code for the touchscreen to work wasn't even in CM9 on my first build, for example. The problems for CM9/ICS can be narrowed down to a few things:
Graphics Memory
No Official ICS
Kernel Improvements
Graphics Memory and No Official ICS: Due to the way that ICS handles the way it puts stuff on our screen we run into Video RAM (VRAM) problems on our device. Basically the routines that control it are expecting the memory to be mapped (stored) in a certain way in VRAM. On a device that has ICS officially, this isn't as big as a problem as the proprietary files (props) are coded to respond to those requests and mappings and as such run smoother. If a device doesn't have ICS, most it usually has a similar device in which props can be pulled and ran accordingly.
This is not the case for Tegra 2 phones as no Tegra 2 device has official ICS. In fact the Tegra kernel (just looked this up) is only at 2.6.34-rc3 officially and have a 3.1.10 kernel in developement (Motorola can update it again to .35 if they wish to do so like for the ATRIX). Because of the lack of an official Tegra 2 kernel for Linux 3.X, and likewise the props for such kernel, we can't have props that handle the requests the system is asking for. And even if another phone gets updated, we're locked and stuck, so It doesn't matter either way. This means that VRAM problems will probably always be there and that there is nothing that I can do for it. Best thing I can hope for (and this is slowly making it's way through CM9) is that the code in CM9 is updated to allow us to handle the VRAM differently like in CM7/GB.
Kernel Improvements: The kernel (that's supposed to be) for ICS is 3.0 or higher. This includes changes in memory as stated above, touchscreen handling, device interaction with the kernel and many others. That being said, we don't have those improvements thus causing problems. These include memory as stated above, touchscreen not working (obviously fixed), data usage not working, data monitoring not working, and a few various ways other routines to draw to the screen and handle other things (such as why Chrome is picky). Some of these can be backported (downgraded) to our kernel with mixed results.
Problem is they have to be complied with our kernel and must match the kernel version in every way. That is why the kernel check is in CM7 and CM9. I can slowly work through implementing these routines through drivers known as kernel modules (mods). I have made mods for data usage (with a few issues) and another one (which not sure what it's supposed to do yet). I cannot (as in it's impossible) write them to change the memory handling. If I could even build them the kernel won't let me load them due to routines of same name fighting for control.
Think of it like the phone is a car and you and your friend are in the front (the kernel routines) and you have the exact same name. Meanwhile, you have another friend in the back (the OS). The OS says, "Hey Routines Named the Same, grab the wheel and turn turn left!" You would turn it to your left, but your friend (the other routine) has a different view of what left is and instead wants to go to your right. Obviously some problems arise.
Regarding the Soft Keys Issue: I know a few of you guys are a little upset regrading the fact that I won't add the soft keys in there by default. I have a justifiable reason behind not adding them: our phone already has buttons.
Our phone was designed to have hardware buttons that separate from the screen. Adding more buttons to the screen for buttons that already exist is not advantageous. It also unnecessarily takes up screen space that makes our phone our phone. Now you may be thinking, "Well the GNex has the soft keys on the screen..." You are correct. But the screen itself has actually been extended (as in a non-standard physical height) to accommodate for the soft keys and also has no hardware buttons for the menu and home, etc. In fact! The Nexus S (a still HIGHLY developed for, supported device and previous "Google Phone") doesn't even have the soft keys enabled from the software directly available from Google themselves.
With that being said, XDA user csking33 has made the option of softkeys available to the public should you choose to enable it. He has it working on the current Alpha 4 and I look forward to him getting them working on Alpha 5 when I release it. You can download it here: http://forum.xda-developers.com/showthread.php?t=1727680.
That is just a short (believe me when I say it's short) explanation as to why ICS is just a FUN FUN FUN thing to work with.
Personal Problems (I have a lot): This is not meant to be a whine-a-thon, more of an explanation of why I can't be as dedicated as I'd like to be. I have explained why ICS is a pain, I'm here to give you a brief rundown as to why I (personally) can't just make things work. I am a student studying Aerospace Engineering (not Computer Science or whatever else). It has kept me so insanely busy that I can't even begin to describe how much little time I have. I spend all day at school and all night doing the homework for it. I was lucky (once) when my Flight Structures II homework only took 5 hours to do. With so many long homework assignments and group projects it's a miracle I even survive. Next semester will be worse because now I have to actually design and build a model plane from scratch that does whatever my professors says it has to do. This is includes the whole design, approval process, building, testing, breaking, fixing, getting approved again, get it flown, doing it's mission and presenting our project. All that on top of the homework I have to do.
Whenever I do get free time during the day, I try to spend it with my girlfriend and/or friends or (if it's a few days) I go to visit my family (this weekend I am, for example). Family and friends have always a top priority of mine since forever and I won't let a phone be the reason why I don't see them IF I see them. In fact the donation money you guys have supported me with is going to get new tires for my car before I go visit my family. It has also bought me spare batteries and cables for when I really mess things up.
After all this is said and done, I stay up to 4 am working on the phone so that you guys can have a semi-legitimate Android experience. I do it because I want to and because we as a community deserve it.
It saddens me to know that I'm (essentially) the only one left working on the X2. Others pop their head in every once and awhile to help or to do what they want and that is GREAT. I love it. I'm always more than willing to help others out if they ask. And all they have to do is ask. PM me here on XDA, join me in the IRC or tweet me on Twitter. I'll be sure to get to it eventually.
TL;DR:
CM9/ICS will be unstable for as long as I can see in the future. There is not much I can do.
No I won't enable soft keys, there is no point in a default build. See the post if you wish to enable them.
I'm a really, really busy man but I do what I can. You guys have helped tremendously in supporting my work and helping me live a little easier
Thanks for the explanation. At this point I guess all we can do is hope that someone at Motorola feels sorry for us and leaks us some goodies. I bet with the unlocked goodness ICS would scream on this phone, even with it's less-than-optimal amount of RAM.
I just want to personally thank you for everything you have done with this phone. I still use CM7 as my daily driver and love it despite the Wifi and the root issues and will continue to use it until I say F you to Motorola and get a different phone a little more dev friendly.
You are doing a great job keeping the DX2 afloat. If you can get ICS in this phone you'll have a very bright future ahead of you. I wish you the best of luck but I don't think you need it
I don't know anything about developing, modding or themes and I won't imagine how hard it must be to do what you have done for the DX2. For that and more: Thank You! Im sure we'll be happy to throw a dollar or two your way.. it's the least we can do. :good:
M-
question
you say no tegra2 has i c s
what about xoom?
was just asking in case that could give you done ideas
good luck DZK, keep killing it
I'm glad you came out with this post. I have had this phone since last summer like you and since then I have used both of your ROMs and have followed your work. Mainly because there are not very many developers still developing for this phone. Lol. I think a lot of people needed to hear this. you don't come in here that much and are not very active in the forums. Not that it's your fault or anything. we all know that you're busy. But people are used to regular updates. Even if they are just verbal ones. So when a dev takes their time and no one hears anything, they don't understand. Most of us in here explain your situation when someone comes in here asking about stuff. We are all grateful for what you have given us so far and the things that are coming down the road. Without you there would be no development for this phone. As much as everyone would like to believe, we all know you are not just some guy sitting behind a desk all day working for us. By the sound of it, it looks like school is going to be getting a lot more busy for you which means less updates for us. By the time you get around to developing again for this phone I may have moved on to another. Just want to say again. Thanks :good:
also just wanted to add that I'm surprised you felt the need to explain yourself, pretty stand up thing to do,
i would HOPE no one gives you guff for having a real life with , priorities, but then again this is x d a haha
this is something you do for fun, we all should realize that, and it's awesome that you have gotten as far as you have
keep plugging away bro (at real life)
ashclepdia said:
also just wanted to add that I'm surprised you felt the need to explain yourself, pretty stand up thing to do,
i would HOPE no one gives you guff for having a real life with , priorities, but then again this is x d a haha
this is something you do for fun, we all should realize that, and it's awesome that you have gotten as far as you have
keep plugging away bro (at real life)
Click to expand...
Click to collapse
I would think this is more for the newcomers here that don't know what's going on behind the scenes. Have you SEEN the kind of things people ask him on twitter? Lol
+1
ashclepdia said:
also just wanted to add that I'm surprised you felt the need to explain yourself, pretty stand up thing to do,
i would HOPE no one gives you guff for having a real life with , priorities, but then again this is x d a haha
this is something you do for fun, we all should realize that, and it's awesome that you have gotten as far as you have
keep plugging away bro (at real life)
Click to expand...
Click to collapse
Sent from my DROID X2 using xda app-developers app
I'm not a dev, but I am a project manager who works very closely with them, on very large scale deployments. Something that has always impressed me about you Bryan, is your prioritization and time management. Knowing where to focus energy in order to achieve maximum result, especially when strapped with limited resources, is a skill not as common as one might think--you've got it in spades.
I guarantee when you enter the work force, it's going to be something that sets you apart from a group of otherwise smart guys. Project managers and directors will LOVE you for that skill set.
That being said, thanks for giving us a portion of a sorely needed resource, it's appreciated.
DK you are the man! Thanks for everything!!! You and nitro saved the x2 without you two the x2 would be crap! Family is always first. Good luck with everything!
---------- Post added at 02:58 AM ---------- Previous post was at 02:54 AM ----------
ashclepdia said:
also just wanted to add that I'm surprised you felt the need to explain yourself, pretty stand up thing to do,
i would HOPE no one gives you guff for having a real life with , priorities, but then again this is x d a haha
this is something you do for fun, we all should realize that, and it's awesome that you have gotten as far as you have
keep plugging away bro (at real life)
Click to expand...
Click to collapse
+1000
Edit: I can't believe the asterisks...lol
**** whoever said what, ungrateful bastard!
Life first, just include Android in it
You are the miracle maker dragonzkiller, if anyone ever says less keep your head high and **** em...never a need to explain.
Keep doing what your doing, it rocks!!!
Ps sorry bout the language, it's a Jersey thing...lol
DROID DOES, Apple did...like I forgot when
I'm with the others, it's always nice to hear what's what, but you should never have felt it any kind of explanation was owed to us.
Even if you suddenly had to put it all to the side permanently, you'll always have my gratitude.
Droid X2 > Eclipse 2.2.1 > Tapatalk
Cheers DZK!! Thanks for your time which is not owed to anyone. Side projects are good esp. when going into difficult job fields. The distractions are going to be what keeps you going. Best of luck to you!
I do wonder now though if it makes more sense to continue to tweak CM7 than CM9.
jsgraphicart said:
I would think this is more for the newcomers here that don't know what's going on behind the scenes. Have you SEEN the kind of things people ask him on twitter? Lol
Click to expand...
Click to collapse
i don't think i HAVE seen what is said to him in twitter...Hope it ain't some crazy crap
Sent from my Galaxy Nexus using Tapatalk 2
Hey just want to stop in and say thanks for the work you do on this phone. And I agree with the what others have said you don't owe us anything we are just greatful with what ever time we can steal from you.
Sent from my Incredible 2 using xda app-developers app
Look, thanks every and as such. For those of you who think that I have to explain myself, I pretty much do. A lot of you guys know the basics behind what it is I'm dealing with, but don't KNOW. If that makes any sense. I really enjoy working on this device and working with the community. I know it seems like I might get snappy sometimes or I'm short with my answers, but please just keep in mind that I have a lot of things on my plate and that I mean well.
Someone pointed out that the XOOM is running a Tegra 2. I did forget that fact, however even with that being the case, it has helped us very little in our endeavors. In fact it's still on 2.6.35 if I remember correctly and the props are still designed with that in mind. However it is still an updated kernel to work with ICS and such still causes some problems.
DZK, man I appreciate all your efforts! I don' t have the plate you do to deal with but I can surely understand where you are coming from.
I do believe that the majority of the community appreciates tremendously what you do for us, and the ones that can't be patient and understand well they can just flip off!
Thanks man!
Dragonzkiller you have done so much for this community and our X2. Would you be interested in a 2 month old PERFECT condition Dinc2? At least you would get a phone with official ICS and it actually already does since UKB is using the official kernel from the China released OTA. Its a great phone with great battery life just a smaller screen. You have done so much for us I would be happy to hook you up with a great deal. One I won't be able to tell my wife about lol
DZK, I too am an engineering student currently, and I fully understand what you are/will be dealing with. Free time is something we engineering students don't have the luxury to afford
With that being said, I truly appreciate what you have done in the development of this phone and how much time you have devoted to doing so. Keep your head high and let the haters hate.
Travisdroidx2 said:
Dragonzkiller you have done so much for this community and our X2. Would you be interested in a 2 month old PERFECT condition Dinc2? At least you would get a phone with official ICS and it actually already does since UKB is using the official kernel from the China released OTA. Its a great phone with great battery life just a smaller screen. You have done so much for us I would be happy to hook you up with a great deal. One I won't be able to tell my wife about lol
Click to expand...
Click to collapse
HEY!!! I see what you're trying to do! Quit trying to kang our dev for the Dinc2 community!!!
Language warning! Don't open in front of boss or kids!
http://i.imgur.com/dWZMF.jpg
Just Received my TS. Although I like it I am wondering if there is any future for this device. The 6+ months delay seem like an eternity and what looked like a promising novelty is already lagging behind. And what makes me wonder is the apparent separation between the company and the first batch of users. How come that not one single bug seem to have been fixed? How come that there is still no OTA updates? Omate closed their official forum and is redirecting to xda for support, but where is Omate in this forum? And what about the possibility of switching to Android Wear, that looks like it will be the standard for this type of devices? I was a happy backer of their Kickstarter project, but at this point all I think is that I bought myself a Xmas present that was delivered at Easter!
Omate, obviously totally abandoned this project.
Rumors are thet they are preparing TS2 so TS is something that used that as a learning base...
Don't know did you followed g+ but I talked much about exactly the same problem months ago...
I said: (in December 2013): when we get TS that device will be old and many other device will be released.
We'll have expensive project that will be just overpriced and unusable...
I'm very sorry to see that but even then while community attacked me -I was right...
We'll try to give our best and try to adapt it but TS is dead and that's, unfortunately, something Omate admitted long time ago...
There's no Omate on XDA, no support, no answers or anything...
We are alone mate...
Sent from my C6903 using Tapatalk
funky0308 said:
Omate, obviously totally abandoned this project.
Rumors are thet they are preparing TS2 so TS is something that used that as a learning base...
Don't know did you followed g+ but I talked much about exactly the same problem months ago...
I said: (in December 2013): when we get TS that device will be old and many other device will be released.
We'll have expensive project that will be just overpriced and unusable...
I'm very sorry to see that but even then while community attacked me -I was right...
We'll try to give our best and try to adapt it but TS is dead and that's, unfortunately, something Omate admitted long time ago...
There's no Omate on XDA, no support, no answers or anything...
We are alone mate...
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Agreed. Omate is done. They were done before they started shipping.
1. Warranty- HA! Null and void
2. OTAs, support, service- LOL
..... U get the picture....
If something goes wrong with your TS...I guess your only choice would be to contact Omeox. Omate certainly won't do anything and most likely won't be around to help. This has been their MO from the beginning. For example, the infamous BT problems and Omate's lack of dev support. This alone spelled disaster for the company and sealed the coffin for any future "free" help from the dev community. Lesson learned: ANY start-up MUST have, keep and strengthen the full support of the community devs.
And lastly, the Omate disaster has laid a major wake to future smartwatch, IGG or KS, campaigns. Its a real shame...now, for any fledgling tech trying to grab a foothold in this market, that truly has something new and innovative, will have to work twice as hard to get noticed.
All due to Rocki and LLP's lies, misleading marketing and "bait'n switch" game.
Thanks Omate!
NO SOUP FOR YOU!
Sent from my HTC One_M8 using Tapatalk
While all this is definitely a shame, one bright side out of this is that I have a damn cool watch, and I paid about fair market value for it (the other Umeox watches go for similar prices). I guess I'm lucky in that mine works fine, so I don't have to deal with Omate again.
I realize that some specs have changed which kinda sucks. But I never intended to go swimming or anything with this, and the other spec changes are minor to me and don't really reflect anything in real world usage. The patch available really make this thing a good, usable, android watch phone (thanks again, Loki!). So I'm at least happy with what I got out of this whole ordeal.
Will I back anything on kickstarter (or others) again? Hell no! But at least I don't feel like I got screwed out of my money.
LLP was bragging on his g+ account about Omate's skills. While I think it is impressive they managed to produce a product, the fact remains that the hardware they used is debatable theirs and if what Loki has said is true, the software is Omate's main field of expertise and that in itself is of a questionable quantity.
I just do not understand Omate. I am not fussed about waterproofing and what not, but not being open about it until after the orders were taking just isn't cricket.
And then this whole lark about not having service centers in your country bla bla bla. Omate should just accept some things will break and have made back up watches to replace those which do. Those which are broken could be shipped back, repaired and resold.
The lack of anyone from Omate here seems really odd. I guess it could be a language issue but I doubt it.
What puzzles me is what did Omate expect to happen? For XDA to do all the work? For the project to develop a life of it's own?
I do think Kickstarter has lost an awful lot of credit, but I do not think the blame should be theirs. Omate just caused PR disasters one after another. Even now, the manner of the conduct online is extremely unprofessional.
Would I buy another Omate (TS2)? Most likely not. I love my TS and think it is super cool, but I want a device which will grow and has a loving community behind it. It is clear there is no love for this device now.
Unless Omate have some secret stuff going on in the background such as a huge update and a ton of new features, I don't see anything special about the Omate. I had an EC309 and with the exception of Omate's sd slot, it could do everything the TS could.
Personally, I think Neptune Pine will win people's hearts. It has had a bumpy ride but recently started being VERY open about production problems and delays. Perhaps it takes an Omate to get these Kickstarter companies to step up a notch.
I'll probably buy a Neptune Pine and other smartwatches. I don't think Omate has killed people's love for the concept, but it has left a bitter taste in many peoples mouths regarding crowd funded projects.
Hyperthetically say if we were to developer/begin a new Smartwatch or smartwatch company. Thru market research we established that there was a massive demand for something similar to the Omate or the A.I. Watch, I.e. a mobile notification and stand alone Android with a sim card wifi, gps BT ...etc.
First we started to source the unit (as designing a new one would take too long and cost too much and it would be copied) what would be the 'do's & don'ts'?
Keep it civil pls and dont say do the exact opposite of Omate... although that would probably go a long way.
It's more of about the way Omate managed the release rather than the product. I accept there would be issues in development.
What is odd is that the watch seems to be available to buy on their China site with no mention of it being a pre-order/ waiting God knows how long till it turns up. Does this mean that they're actively selling them now in China before sending the backers theirs?
Like their Chinese site though. At least it gives info about the company.
http://china.omate.com/
Have they (Omate.com) removed the specs info'?
simple1i said:
Have they (Omate.com) removed the specs info'?
Click to expand...
Click to collapse
Doesn't seem like it. They still have that annoying avatar with the Omate being splashed. Their Chinese site still has the specs up. I think they still say the camera is 5 mega pixel.
http://china.omate.com/smart.php
Well, this is an attempt to possibly access more information. I may have read somewhere that stated in so many words, a little participation, or, even just an introduction, may get you a long way here on XDA. Now, whether or not there's any truth to this, isn't really of any importance. What's of importance, is how unimportant one may consider what someone else views as important. Setting that aside for a moment, what about the the truth that's actually quite commonly found leaving the liars mouth? I'll give examples in a moment but before I do, ask yourself if one were to actually tell the truth but believing it to be a lie, would what was said be considered by you, to be honest? I mean it is the truth, just delivered with dishonest intent, right? I am a newb, on an iphone 6+...iOS 11.2.5 just until I can put together the $100 deductible for the MOTO Z I dropped. I haven't been very active in these past years being with Verizon, but I wasn't very active before i made the switch. I was a DROID X2 bricker and I will always be. Just recently found a junkyard of old phones, that I or friends bricked, or dropped without insurance, cracked screen, no battery, etc.
What I am and have been working on, with no success is an On5 SM-G550T (A.R. MMB29K.G550TUVU2AQC4 samsung/on5ltetmo/on51tetmo) updated to 6.0.1/MMB29K/G550TUVU2AQC4
FRP and can't enable debugging with anything I have found thus far...I have used the enabler but may be flashing the wrong files as I have come across plenty G550TUVU1?????? but nothing found for G550TUVU2??????? I'm sure my recovery (TWRP) file is correct but until I can enable USB it's really not doing me any good. Any chance of someone(anyone that made it this far is respected!) possibly shootin me instructions or even just pointing me in the right direction. I have attempted flashing with odin and even OTG with other suggested files. Objective is to bypass frp by enabling debugging and flashing stock 5.0 firm so I may then install twrp and depending on my mood and position of the moon, maybe a super user and some ROM tryouts. You guys are awesome, even if you decide not to help. Developers, my thanks only goes so far and so do the rest of these words, so Ill be about it soon and wont talk about it now. But seriously, hat's off and I appreciate the countless hours, painful blinks and most importantly, the late arrivals and drop offs associated with such sacrifice. Thank you!!!