Related
I realize it's still on the horizon and I am not asking when. I have tried FRX06 and updated the kernels and rootfs as they became available. Two things I have not done is use the new RIL2 or try the new audio routing patches.
My setup - VZ TP2/Rhod500. Without looking, I can't tell you which kernel or rootfs I am using. If I were are my home computer where I do the installs, I could tell in a second.
My question is this - in all likelihood, will FRX07 incorporate the new RIL and the BT/audio fixes? I'm not familiar enough with ADB or some of the other things mentioned in the audio routing thread to attempt them at this time.
For the most part, FRX06 is workable for me. I can run it for several days without SODs or random reboots. Other times, it might be a day or two. I do use my BT when in WinMo so it would be nice to have it in FRX0_.
Kudos to the various devs here for their hard work. I hope to be able to use FRX07 in the near future or at least until the company I work for upgrades my phone (wish list - Samsung Fascinate).
Thanks again to the devs and other testers! I have learned a good deal from the posts.
I can't say for sure until it's released, but I'm pretty confident that:
a) The new RIL will most definitely be in FRX07.
b) The BT/audio routing stuff needs some work yet, and to prevent from further delaying FRX07, it probably will not make it.
Feel like this is the place to mention this.
Some posts I read people are testing Bluetooth.
Are they confuzzled users with a different phone or is there something I am missing?
ryannathans said:
Feel like this is the place to mention this.
Some posts I read people are testing Bluetooth.
Are they confuzzled users with a different phone or is there something I am missing?
Click to expand...
Click to collapse
You are missing something.
Check out the "new audio routing" thread, it includes instructions (not for the weak kneed) how to get BT up and running. I've done it on a clean FRX06 install and successfully done several file transfers.
ryannathans said:
Feel like this is the place to mention this.
Some posts I read people are testing Bluetooth.
Are they confuzzled users with a different phone or is there something I am missing?
Click to expand...
Click to collapse
LOL!!!
That's awesome. I think you're the confuzzled one...
[TESTING] New audio routing for Froyo
If we could just get that ril packed in there I'd be happy, bluetooth isn't that important in the grand scheme of things. My wife is incredibly jealous of my inspire and I don't have the money for another. frx05 was her last attempt to use android and she just got tired of sods and poor battery life. For some reason her rhod300 never worked as well with these builds as mine. Hopefully gsm nand will be working soon so I can just wipe out windows mobile and not give her any choice
arrrghhh said:
LOL!!!
That's awesome. I think you're the confuzzled one...
[TESTING] New audio routing for Froyo
Click to expand...
Click to collapse
Heh, thanks.
Saw that but wasn't going to test it, now I see bluetooth in it.
Testing tonight
do any of the custom kernels currently developed for the Thunderbolt, support wireless "N"? Thanks in advance.
The phone supports the wireless n protocol by default out of the box. If it's not working, it's you, not the phone.
Kenerls help support the wifi. If the kernel does support "N", the the phone will not. Thanks for ur support tough guy.
Sent from my ADR6400L using XDA App
I wasn't being a jerk, you're just overreacting and assume my short answer was being rude and some sort of attack on your intelligence. I didn't see a point of giving a tl;dr answer you probably aren't interested in.
But here's the tl;dr version:
Instead of jumping on me, you could look up how drivers work. Your phone supports wireless n because the kernel in the phone has the proper wireless driver for it compiled in. On linux, there aren't a lot of choices for wireless drivers and since there's most likely only one choice for the wireless driver with this hardware and revision type (and it comes linked and ready to compile with the kernel source given from HTC that all the kernels listed in the developer forum are using). The phone's hardware supports wireless n and any drivers made for it by default will have it as well. So by that, if wifi works at all on your phone, so will wireless n--unless someone was specifically screwing with you and ripped out the wireless n protocol support in the driver source code, but happened to leave g and b, which most likely be a pain and be hard to do without breaking the entire driver itself.
If you want to be technical, all the kernels are based off the one that came with your phone in some way and have the same drivers compiled in; hence, they support the wireless n protocol. No developer is going to remove the wifi drivers to a kernel on purpose and if it were missing, someone would quickly notice. With that in mind, if the phone doesn't seem to pick up a wireless n signal, it's not the phone, it's you (or indirectly your router/hotspot location).
Honestly though, if a short answer doesn't work for you and assuming you are going to take a long answer at face value because it has some big technical words thrown into it that make it look credible and don't want to dig up an answer by googling or flashing one of the kernels to see for yourself, what is the point of writing it all out?
If that was all too tl;dr, the short answer is once again, yes, they all have "Wifi N kernel support."
Also, my answer is free, no need to donate to me
Not all customs kernels support wifi N. Ask a couple devs.
Sent from my ADR6400L using XDA App
Please do not rehost the testing software over at infectedrom - I would like to maintain some control if possible to ensure things do not get out of hand going forward. I am not trying to write viruses, just show how the issue works so we can all protect ourselfs. While I cannot stop anyone from turning the code malicious I highly frown upon modifying this to write values in any way. Trust me from experience, you dont want to play anyway you will probably just bork your own wimax.
Note: Please be aware that rooting your phone to install this patch will void your warranty with HTC. You should all already be aware of this when you unlocked your bootloader. As with anything posted in these dev boards this patch may also affect the functionality of your device, so proceed at your own caution!!!
What are we patching?
This post is a call to arms for help from devs on patching the issue shown in PoC#2. You can read the vulnerability report and find test software to see if you are effected over on infectedrom. HTC has been notified on this particular issue on October 20th so they will be working on an official patch.
Download
http://www.androidfilehost.com/main/.TrevE/PoC2/TrevE_WiMAX_Patch.zip is an unofficial patch I started that anyone can use / modify / whatever attached to this post. Its crude but its an immediate quick fix that cuts the negative implications down by manually stop & start wimax services / show 4g settings.
Using Patch:
In a nutshell these 3 binaries do not need to always run, and them being flawed we want them off all the time. When you want to use 4g, start the above app and turn on the binaries then 4g radio like usual.
If you do not want to edit ramdisk you should be able to use the app just to stop the binaries each boot.
To disable these binaries completely and only start when there needed edit init.shooter.rc to appear as below (or wherever binaries are started in ramdisk) and manually start them when you are going on 4g with attached app.
Code:
service wimaxDaemon /system/bin/wimaxDaemon
user root
group root
disabled
oneshot
# setWMXPropd daemon
service setWMXPropd /system/bin/
setWiMAXPropDaemond
user root
group root
disabled
oneshot
# getWMXPropd daemon
service getWMXPropd /system/bin/getWiMAXPropDaemond
user root
group root
disabled
oneshot
Big thanks to the help getting in touch with HTC from egzthunder1!
Other Possible patch solutions
The other issue I would like to bring to attention is the code was 99% the same from PoC#1 - connecting to 127.0.0.1. Is there anything we can do to make some kind of ipchain firewall blocking apps from access to certain resources? I would think this would be important for all rooted users especially having some type of easy firewall, and everything Ive seen seems primitive. Mobile malware is coming and we should be ahead of the tides.
Non Root solutions?
Non root users may be able to kill the PIDs or stop the services, I have not had the time to try.
TrevE said:
As always I think its a good general warning to stay away from shady apps, things arent always as sandboxed as you would think. While HTC is already working on an official patch for this and other issues where theres a will theres a way with malware. I think firewalls and protective measures need to start stepping up before things get worse, its a linux pc in our pockets with a radio - not just a phone anymore.
Click to expand...
Click to collapse
You always know how to keep us one step ahead, Thanks for this info
This is def way over my head...but I thought I should ask b/c im sure others will probably ask the same. Should I worry about this if I am not in a Wimax market? No Wimax within a 100+ miles from me at least (San Diego). I'm guessing not, but what do I know??
Thanks for looking out for us n00bs!
MFD00M said:
This is def way over my head...but I thought I should ask b/c im sure others will probably ask the same. Should I worry about this if I am not in a Wimax market? No Wimax within a 100+ miles from me at least (San Diego). I'm guessing not, but what do I know??
Thanks for looking out for us n00bs!
Click to expand...
Click to collapse
the issue effects all 3ds with wimax and more, I actually had mine in airplane mode with all radios off for video and was able to crash phone and read / write values.
videos rotating guys, sorry shot it alittle funny and running around right now....
Very interesting. Going to sit down and read real quick!
Gonna use it either way, but lets see whats we got going.
Thanx buddy!
hTc
I didn't really understand that, but it looks important. I'm not really sure but I think that the video meant that the wimax can be accessed when its not on. Something like that?
Read the article on this.... Sprint deserves a wag of the finger from Colbert. Its just dirty. Back doors like crazy. And why the **** would HTC not pro actively remove all the crap in the first security patch. They KNOW everything before we FIND it.
Sent from my PG86100 using Tapatalk
TrevE, would that LBE tool be enough to revoke privilege for network access?
not an expert, but we could probably port over the iptables and add some default configuration for our phone.
Heck, maybe I just build one. Ha.. MOM.
Thanks TrevE for being on this!
TrevE, thank you for putting this out there. And thank God you aren't a maligned dev, or we'd all be in trouble. HTC should be paying you for doing QC on their code. Oh, wait... I forgot, all this was on purpose.
Warm & cozy.
Always treve you are one step ahead of the dictatorship known as HTC and Sprint I am grateful your on our side man thank you
Sent from my PG86100 using xda premium
Well isn't this lovely, they set that up for debugging and forget to disable it or something?
Just read about this on Phandroid. Kinda crazy. Thanks Treve for all you do.
Sent from my SPH-D710 using xda premium
xHausx said:
Well isn't this lovely, they set that up for debugging and forget to disable it or something?
Click to expand...
Click to collapse
those binaries are actually whats called if you logcat connecting to wimax. While I cant say for sure my guess is it wasnt left open for debugging, more hey nobody will look here. The wimax monitoring port is very curious as well - if you look at the poc app it can query DUN state, release keys and rom versions among other things.
These ports look like they are never used until you connect to 4g, so the best solution I came up with is just shutting them off all the time and turning them on with an app before you connect 4g. This atleast limits vulnerability time from any random app reprogramming your wimax values to only be possible when your on 4g.
As always I think its a good general warning to stay away from shady apps, things arent always as sandboxed as you would think. While HTC is already working on an official patch for this and other issues where theres a will theres a way with malware. I think firewalls and protective measures need to start stepping up before things get worse, its a linux pc in our pockets with a radio - not just a phone anymore.
huytrang90 said:
TrevE, would that LBE tool be enough to revoke privilege for network access?
not an expert, but we could probably port over the iptables and add some default configuration for our phone.
Heck, maybe I just build one. Ha.. MOM.
Click to expand...
Click to collapse
Not sure, I kinda see this as a problem in android - local and internet arent really separated. I cant say for sure if revoking will work, download the proof of concept app and try This is one of the reasons i feel strongly about demonstrating issues like this, everyone can learn from it how it works and how to squash this stuff and protect ourselves. The last thing we need is winnuke/sasser/whatever on android.
Forgive for the noob??? But I'm just trying to gain an understanding of how to use this. Do I just edit the int file or use your app before I turn 4g on?? Also since Im in an area that has little to no 4g is there a quick way to completely disable the 4g antenna untill I want to use it??
Locked & Loaded
""shooter on Deck""
HTC loves you TrevE!
Good work again!
TrevE, I just gotta say, because it's not said enough, thank you. You are afaik the ONLY low-level dev still working for the end user in public, and I for one find it both heartening and praise-worthy. With all the drama we see around here, and get involved in, you still keep on pushing forward. I'm thoroughly grateful that you are doing this and not some douchebag hacker who wants to nuke our phones from the cloud
#idrankthekoolaid
Hi,
I'm interested in purchasing a Nexus 4 I have no cellphone plan, nor do I want one; instead I intend to use the phone as a tablet or PDA.
I would like to hear some feedback on how feasible it is to low-level remove the cell and gps antennas' capabilities. Is there a driver or kernel module of some sort that could be removed to 'neuter' the phone? Can the hardware run the antennas without the ROM or kernel's consent?
I've already read about the code to reach a developer menu and 'disable radio' as well as 'airplane mode'. Neither of these fit the bill, I want the phone to be incapable of transmitting cell/gps information.
I would love to join the android community, but I will not feel comfortable until I know that the device isn't going to hand over my location to anyone with a crafty enough story at the police department, which I believe makes this question one of security rather than battery life or functionality.
My apologies if this is posted in the wrong section, I decided that the android forum would be most appropriate because I'm curious about how android manages the cellular antenna rather than something specific to the Nexus.
Thanks!,
BigBubbaX said:
Hi,
I'm interested in purchasing a Nexus 4 I have no cellphone plan, nor do I want one; instead I intend to use the phone as a tablet or PDA.
I would like to hear some feedback on how feasible it is to low-level remove the cell and gps antennas' capabilities. Is there a driver or kernel module of some sort that could be removed to 'neuter' the phone? Can the hardware run the antennas without the ROM or kernel's consent?
I've already read about the code to reach a developer menu and 'disable radio' as well as 'airplane mode'. Neither of these fit the bill, I want the phone to be incapable of transmitting cell/gps information.
I would love to join the android community, but I will not feel comfortable until I know that the device isn't going to hand over my location to anyone with a crafty enough story at the police department, which I believe makes this question one of security rather than battery life or functionality.
My apologies if this is posted in the wrong section, I decided that the android forum would be most appropriate because I'm curious about how android manages the cellular antenna rather than something specific to the Nexus.
Thanks!,
Click to expand...
Click to collapse
I am also interested in this...
I bet if one can compile a kernel for his own device, it is possible to disable the GPS and related drives in the module/kernel config.
and this would completely kill the feature... so no risk of any spyware app triggering it etc...
however it may not make sense to use maps on the device... unless you want to bluetooth pair it to another GPS device.
Nexus is great... but I want to be able to do this for a different phone which may not be as popular on here.. than what ?
G
ghatothkach said:
I am also interested in this...
I bet if one can compile a kernel for his own device, it is possible to disable the GPS and related drives in the module/kernel config.
and this would completely kill the feature... so no risk of any spyware app triggering it etc...
however it may not make sense to use maps on the device... unless you want to bluetooth pair it to another GPS device.
Nexus is great... but I want to be able to do this for a different phone which may not be as popular on here.. than what ?
G
Click to expand...
Click to collapse
Hi ghatothkach,
I'm still working on this. First I need to assemble a x64 computer capable of compiling a ROM from source, then I'll see if I can find a way to nullify the radio drivers. If it's possible for the Nexus, I'm pretty sure a similar workflow will be available for your phone.
There are also some other aspects of Android that I'd like to look at for security concerns, such as the way that the phone currently broadcasts a list of wireless networks which it is associated with.
I apologize for digging up an old thread, but has there been any development on this subject? Or physically removing or disabling the GPS receiver on a phone?
6 years later..
Question remains.
Is that possible to root the device and delete the gps driver/kernel completely?
If yes which of the file as to be removed
0
All checks and analysis were done to fresh installs only. No additional apps were installed except for those required for the security checks. The analysis is of currently active projects ONLY.
[ROM] Stock official firmware 20140513
Security Check Results;
CVE-2013-6271
CVE-2013-7373
CVE-2014-1939
CVE-2013-7372
CVE-2014-1600
Masterkey 9950697
Masterkey 10148049
USSD
Optimizations;
CPU Governor- Stock
SDCard Cache- Stock
OOM- Stock
SYSCTL- Stock
Network- Stock
Build.prop- Stock
BT Tether (watch>phone>internet);
Not working
BT Companion;
Not working
Kernel
Whatever kernel is provided.
[ROM] monxDIFIED™ SMART ROM ? SECURE + BT TETHERING v01-04
Security Check Results;
CVE-2013-6271
CVE-2013-7373
CVE-2014-1939
CVE-2013-7372
CVE-2014-1600
Masterkey 9950697
Masterkey 10148049
USSD
Optimizations;
CPU Governor- Stock
SDCard Cache- Stock
OOM- Stock
SYSCTL- Stock
Network- Stock
Build.prop- Minimal edits (Density config, Enable USB debugging, Disable debugging notify, Disable Bytecode, Disable sending data and logging)
BT Tether (watch>phone>internet);
Not properly working. Blue icon, no connection. Browser, Play Store, Voice Search, Google Now, Maps, etc., all fail to find a connection.
BT Companion;
Not properly working
Kernel
Whatever kernel you have prior to flashing is what you get.
[ROM] 07.06 EnSec STOCK Secure
(Continuation of the, Omate officially supported and approved, EnSec Project by Adam Outler, ClearD , Dees Troy, kuronosan and others.)
Security Check Results;
CVE-2013-6271
CVE-2013-7373
CVE-2014-1939
CVE-2013-7372
Masterkey 9950697
Masterkey 10148049
USSD
Optimizations;
CPU Governor- Tuned for lower CPU clocks under load to save battery
SDCard Cache- Tuned for optimal R/W speeds
OOM- Stock
SYSCTL- Tuned
Network- Tuned
Build.prop- Multiple edits (Density config, Network, playback, etc....)
BT Tether (watch>phone>internet);
Not working
BT Companion;
Not working
Kernel
Device specific matched kernel.
[ROM] mystery companion ROM
(if you don't know, don't ask. If you do know, don't tell)
Security Check Results;
CVE-2013-6271
CVE-2013-7373
CVE-2014-1939
CVE-2013-7372
Optimizations;
CPU Governor- Tuned for lower CPU clocks under load to save battery
SDCard Cache- Tuned for optimal R/W speeds
OOM- Tuned
SYSCTL- Tuned
Network- Tuned
Build.prop- Multiple edits (Density config, Network, playback, etc....)
BT Tether (watch>phone>internet);
Not properly working
BT Companion;
Mostly functional. Working notifications, working contacts sync, working remote app management, working speaker phone. Remote camera control not working,
Kernel
Whatever kernel you have prior to flashing is what you get.
How did you perform these security checks? I would like to check my own device.
Belarc
Bluebox
Dou Security XRay
Eeye
Secunia
SRT App Integrity
(all in attached zip)
USSD can be checked by going to ESET. You can also create your own page to check USSD and have it issue more aggressive codes, that what I've done. CVE-2014-1600 has to be checked by hand.
I'm still running EnSec + Operative Casual Edition 20140318 20140120 firmware ONLY!
It suits my purposes. The watch does what it's supposed to do. Tethering would do me no good unless I could tether to Maemo 5 or Meego Harmattan, which seems singularly unlikely.
Should I be worried and reflashing to something else, or is there no real point in a change from what I'm running right now?
EnSec STOCK Secure is a continuation and is based on newer firmware. There may be some sensor fixes and a couple of other things but other than that is very close to the original EnSec. Even though neither are perfect, both are still the best choice for security at this time. I personally would suggest flashing kuronosan's EnSec simply because it is a current and active release.
I have not tested the current version of monx ROM as every dev that was here prior to monx has quit releasing on xda for this device. I have quit dev support for the device on xda as well. You can pretty much thank monx for that.
So ClearD is gone, kuronosan is only providing support, and Dees wasn't surprised at what happened. Adam Outler is off on other projects. Any other dev I've talked to also found monx's kanging, games and insults a bit offensive. Enjoy your monx flavored icing as, from what we can tell, there is almost no real ROM work and mostly themeing. But what do we know, we are nothing but wannabe devs according to monx anyway.
You guys are so pathetic, NO ONE CARES ABOUT YOUR ISSUES
Focus on your own roms and ignore the rhetoric, because no one actually cares.
xcooling said:
You guys are so pathetic, NO ONE CARES ABOUT YOUR ISSUES
Focus on your own roms and ignore the rhetoric, because no one actually cares.
Click to expand...
Click to collapse
If you want to support somebody that stole Adam Outler, Dees Troy, kuronosan, ChiefzReloaded, ClearD and my work then calls the very same people whose work he stole fakes and wannabe's go ahead. Enjoy your easily hacked, unoptimized theme being passed off as a ROM.
And it wouldn't have been a problem if he had simply done the proper thing and asked and credited and not called everybody else a fake and wannabe. Not a problem though as of 8/7/2014 I have rescinded any and all permissions for xda and it's members to use my works, reference my works and mirror my works.
awesome, what a helpful person.
Thanks for standing by the community.
xcooling said:
awesome, what a helpful person.
Thanks for standing by the community.
Click to expand...
Click to collapse
Adam Outler, Dees Troy, kuronosan, ChiefzReloaded, ClearD and myself all work(ed) together on the TrueSmart/x201. Almost all work released on xda and any other forums, English or otherwise, is either based on our work, or authorized mirrors of our work. Some of our work is even in official firmware as we have worked with Omate since October of last year on issues.
I maintained an updated archive of almost every firmware and ROM released for not only the TrueSmart but the entire x201 platform and did security checks on all of it as well as look for any changes that may benefit all x201 users. I was also responsible for the core ROM work as well as being part of the early TWRP development and assisting the other devs with their work. Adam Outler, Dees Troy and kuronosan have all referenced my work at one point or another for their own works. In fact my work was called "amazing" by Adam Outer and "required" buy multiple other devs.
monx STOLE the work of at least five other devs and never even so much as apologized, then have repeated called other devs wannabe's.
And as far as the security and optimizations analysis, those results are after a peer review in which all the results matched. monx has called it b$ and and yet again called multiple devs wannabes.
I have better things to do than be part of a community that allows an ass like monx to kang, distribute an admitted trojan infected ROM and call multiple devs that came before him wannabe's and be a general ass with little repercussions.
In short. This section would not even be here if it was not for myself and a couple others. Also, the vast majority of the work, support and info would not even exist. This is not the first device I've done this for either. I did my part, and more.
xcooling said:
awesome, what a helpful person.
Thanks for standing by the community.
Click to expand...
Click to collapse
When several MTK developers (who have coded custom ROMs, kernels, and firmwares for MTK devices) tell you that your ROM has issues and you call them wannabes or haters, you really don't deserve any sort of adulation.
Besides, I'm still here providing support. Much of what I've discovered while working with other developers has become commonplace on future firmwares. I don't appreciate being called a "wannabe" or "hater" when calling people out on stupid mistakes.
XDA is not a place for Solid Snakes. It's a place for developers to work together. Not helping others is the peak of asshole-i-tude and accepting contributions to your work while not contributing to that of others is the antithesis of XDA.
Loosers attitude: give up and run away, complain because you were not given enough credit or fame
Winners attitude: would be to make your rom better, keep helping the community as you have done.
xcooling said:
Loosers attitude: give up and run away, complain because you were not given enough credit or fame
Winners attitude: would be to make your rom better, keep helping the community as you have done.
Click to expand...
Click to collapse
Cool story bro
So you support lying, theft of intellectual property and copyrights and acting like an 3 year old by calling people names? If that's the case then let me steal his work, improve it and call it my own vs trying fixing real problems like the ability to erase the IMEI with nothing more than a webpage or destroy the partition map with an email. Themes are the least of this devices problems.
Awesome. This device already had a bad rep with the devs for various reasons, then this monx guy swoops in to crush any remaining hope we had. Oh well, I'm thankful for what you guys have done, I actually enjoy my TS because of you guys, and that's all I could have asked for.
speedyink said:
Awesome. This device already had a bad rep with the devs for various reasons, then this monx guy swoops in to crush any remaining hope we had. Oh well, I'm thankful for what you guys have done, I actually enjoy my TS because of you guys, and that's all I could have asked for.
Click to expand...
Click to collapse
I'm still working on quite a few projects. Stay tuned. They likely won't end up here, but you never know.
Glad to hear kuronosan! I understand if you don't want to release it here, maybe you could PM me where you plan to release it or something? I've been interested in what you've been doing, and you have said some things in the past that sound promising (like news of KK and the like).
Thanks for sticking with it, and again to all the devs for all the previous work that helped us get as far as we are.
Lokifish Marz said:
Adam Outler, Dees Troy, kuronosan, ChiefzReloaded, ClearD and myself all work(ed) together on the TrueSmart/x201. Almost all work released on xda and any other forums, English or otherwise, is either based on our work, or authorized mirrors of our work. Some of our work is even in official firmware as we have worked with Omate since October of last year on issues.
I maintained an updated archive of almost every firmware and ROM released for not only the TrueSmart but the entire x201 platform and did security checks on all of it as well as look for any changes that may benefit all x201 users. I was also responsible for the core ROM work as well as being part of the early TWRP development and assisting the other devs with their work. Adam Outler, Dees Troy and kuronosan have all referenced my work at one point or another for their own works. In fact my work was called "amazing" by Adam Outer and "required" buy multiple other devs.
monx STOLE the work of at least five other devs and never even so much as apologized, then have repeated called other devs wannabe's.
And as far as the security and optimizations analysis, those results are after a peer review in which all the results matched. monx has called it b$ and and yet again called multiple devs wannabes.
I have better things to do than be part of a community that allows an ass like monx to kang, distribute an admitted trojan infected ROM and call multiple devs that came before him wannabe's and be a general ass with little repercussions.
In short. This section would not even be here if it was not for myself and a couple others. Also, the vast majority of the work, support and info would not even exist. This is not the first device I've done this for either. I did my part, and more.
Click to expand...
Click to collapse
Could just not ignore him,,, I only flashed the rom to see what the BT tethering was like out of curiosity (its very slow and useable)... will be ditching the ROM when I can get round to it... been annoying me all week I can't wear my watch has it just drains flat with this ROM....
speedyink said:
Glad to hear kuronosan! I understand if you don't want to release it here, maybe you could PM me where you plan to release it or something? I've been interested in what you've been doing, and you have said some things in the past that sound promising (like news of KK and the like).
Thanks for sticking with it, and again to all the devs for all the previous work that helped us get as far as we are.
Click to expand...
Click to collapse
I've personally approached monx about sharing work and ideas but he clearly has no intention of doing so; he has not responded but he continues to post in his topics.
That's fine. I'm only interested in continuing to better this watch and I have my own things to work on. As far as battery tweaks, I've managed to stabilize that (one of my users mentioned battery life 4-5 days with regular use) and I've managed to make quite a few gains.
Some of the things I would like to share involve making BT more stable and accessible across all ROMs, but again... he has no interest in sharing.
So while some of you hang from his beard as though Loki is the bad guy here, remember the ROM you love so much came from Loki's work and from the relationship I continue to foster with the CEO of this company.
But hey, no worries. Keep on praising a glorified themer who won't share his work with anyone else.
I'll be back here when I get my hands on the KK build.
Well, I'm gonna stick to my MotoACTV for a little longer. Planned on buying a TS secondhand, but hardware issues, software issues, and the current bout of drama, are very well keeping me from upgrading.
I understand your (TS devs) positions and motives. I know that there's a reason why you left the development on this device, and I'm glad you've simply quit development, rather than fighting and starting a riot.
However, with nearly all of the developers having abandoned the device, I don't see a good future coming from this.
I was hopeful through the kickstarter phase, and it's a pretty cool piece of tech, but, chances are, Omate will support it better than the community, until someone stands up, starts their own thing, and isn't afraid of getting their work ripped off.
Anyway, thanks for the development it did get, and all the cool things you guys do. If it weren't for you, this device would probably be dead in the water unless the OEM goes above and beyond to support it for a while.