Hello everyone, I was thinking to buy a Moto 360. But no threads in the development sections gave me a setback. The question is - 'Why?'.
I could see in the previous edition's XDA section, TWRP and other mods are available. Just curious to know.
DJBhardwaj said:
Hello everyone, I was thinking to buy a Moto 360. But no threads in the development sections gave me a setback. The question is - 'Why?'.
I could see in the previous edition's XDA section, TWRP and other mods are available. Just curious to know.
Click to expand...
Click to collapse
As far as i have seen, On the old Moto 360 there was a usb interface hidden under a single sticker where the strap connects to the watch.
This easily enabled fastboot access which led to TWRP etc.
On the new Moto 360 it would appear that the only physical connection requires removing the back of the watch.
This causes damage to the watch.
The contacts under the watch back also appear to require a special dock and no one has traced/figured out how these are wired.
Well, then I guess the upcoming wifi functionality in fastboot is going to be a lot helpful ) Thanks for the heads up, though.
Related
Can't post this in the forum it belongs, so I'm asking here; using the latest itineration (FRX 7.1), the only real problems/bugs/still being worked on; are these
1. BT constantly cycles on/off
2. USB OTG to transfer files doesn't work.
3. Can't remember the 3rd.
Are there work-arounds for these, or are they still being ironed out.
If this wasn't the right place to ask, please direct me to the right place.
RBraverman said:
Can't post this in the forum it belongs, so I'm asking here; using the latest itineration (FRX 7.1), the only real problems/bugs/still being worked on; are these
1. BT constantly cycles on/off
2. USB OTG to transfer files doesn't work.
3. Can't remember the 3rd.
Are there work-arounds for these, or are they still being ironed out.
If this wasn't the right place to ask, please direct me to the right place.
Click to expand...
Click to collapse
Your best bet is to try and build your post count with constructive stuff, like helping other people in general and Q&A sections, and then when you've got enough and understand not to start non-development threads in the dev forum, ask the question in the ROM thread. XDA likes contributors
johncmolyneux said:
Your best bet is to try and build your post count with constructive stuff, like helping other people in general and Q&A sections, and then when you've got enough and understand not to start non-development threads in the dev forum, ask the question in the ROM thread. XDA likes contributors
Click to expand...
Click to collapse
I realize that but as I'm new to Android (Unix programmer from the 70's though) I do not use the phone with Droid as the BT earpiece is too important. With that in mind, I've little to offer.
Sounds like you're stuck with RTFM for now...
1. There is a thread for the BT, I don't recall the specifics but it's something about audio threading/routing I think?
2. Not sure on that one...
3. No help for Oldtimer's disease.
Keep in mind all of the efforts you see here are done by volunteers, there are no hard and fast release dates or etas for any of it. If you want to know when something will really be finished then you're going to need to brush the cobwebs off those programming skills and kick in some keyboard time. Based on what I've seen these guys are more than willing to help you get up to speed on that but I'd guess most of that is identifying who you need to PM to get the answer you need on specific questions.
You might also want to pick up a spare phone from craigslist and use it as a tester. You can get one for $100 or less if you're patient. I've found that to be the best way for me to learn what's really happening, then if you screw it up you're not scrambling around looking for a replacement while your wife's trying to get ahold of you.
They have threads in the dev section. BT routing is in a testing kernel. as for the PC connection google Droid Explorer. it will allow you to connect to it through adb instead of clicking usb mass storage.
I too am in the same boat as you. I've been using the FXR07 for a while and the BT was working fine (even for audio routing) and then all of a sudden it stopped working. First it quit detecting my device and I had to manually re-pair it each time, then it started doing the auto toggle on.off that you're talking about. So I tried updating to the FRX07.1 build and had the same issue. I also tried the GBX0A (Gingerbread) build and had the same issue. Though when I tried the GB build, I did carry over my data.img and my rootfs. I'm going to play with this some more and see if I can't get to the bottom of it, but I too am too new to be allowed to participate in the dev thread where this conversation really belongs.
I'll keep you posted if I find anything useful...please update us if you do also.
Don't use the same data.img when switching between builds. Use titanium back up to back up and restore data when switching between froyo and gingerbread.
Sent from my MSM using XDA App
Well, I went with the overkill approach and reformatted my SD card then put a clean copy of FRX07.1 on it. The bluetooth stopped cycling and half works. I can hear my audiobook playback and phone calls, but they can't hear me on a call. Also, I had to manually un-pair and re-pair the device this morning after having tested it yesterday. Not sure what help that gives...if any...
Hello everybody.
Simillar situation with my TP2. Can speak thru headset, but cannot listening to the music.
Succesfully instaled adb and connect, found in logs that I've no device /dev/htc-acoustic
adb shell ls -h /dev
or
adb shell ls /dev
But why before each device is 1;35m...
I will keep on working on it, my similar post is her (cannot post as link, grrrrrrrrr!!)
forum.ppcgeeks.com/showthread.php?p=2145085#post2145085
I'm the moderator of russian forum about ASUS Prime.
See: http://4pda.ru/forum/index.php?showtopic=308957
Unfortunately I have not yet 10 posts.
So I ask here, and not in the development section.
Many people have a problem after replacing the touchpad as follows:
After buying a Chinese touchscreen for Asus Prime TF201 and installing it - they received the "inverse" reaction to touching:
if press on the left side of the screen - displayed click on the right side, and vice versa.
More information can be seen on the videos:
http://youtu.be/XUN_0q5I4ng and http://youtu.be/diIBdD5yMSI
Obviously, there are different revisions of tablet.
Has anybody any Idee how to fix it?
Can this be fixed by software or need a soldering-iron?
Apparently this is not fixable, since when Asus replaced screens, some users had their motherboards replaced too, so it's probably because the screens are of a batch that have the inverted axis problem and Asus replaced the motherboards to undo the invert.
I honestly have no idea, but just so you know this definitely shouldn't have gone in the Dev section like you wanted it to. If you have a ROM or kernel to post, put that in the Dev section. If you have anything other than those two things, it goes in one of the other sections accordingly. Under no circumstances should a question be in the Dev section. Questions in the Q&A section, general discussions about the tablet in the General section, etc.
Just trying to save you from getting yelled at in the future
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app.
I have the same question, or rather a problem with the "inverted-screen." Tell me where I can buy a normal version of the touchscreen? thanks
SteveG12543 said:
I honestly have no idea, but just so you know this definitely shouldn't have gone in the Dev section like you wanted it to. If you have a ROM or kernel to post, put that in the Dev section. If you have anything other than those two things, it goes in one of the other sections accordingly. Under no circumstances should a question be in the Dev section. Questions in the Q&A section, general discussions about the tablet in the General section, etc.
Just trying to save you from getting yelled at in the future
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app.
Click to expand...
Click to collapse
I would have thought the dev section also.
They're sourcing a non-original part that nearly works just that the touch screen data is backwards.
It would almost be trivial to rectify this if the drivers source was available.
In actual fact if you knew as much as a dev would know about the OS you could write an app that could do it without touching the drivers
my 2 cents
abazz said:
I would have thought the dev section also.
They're sourcing a non-original part that nearly works just that the touch screen data is backwards.
It would almost be trivial to rectify this if the drivers source was available.
In actual fact if you knew as much as a dev would know about the OS you could write an app that could do it without touching the drivers
my 2 cents
Click to expand...
Click to collapse
It's not as easy as you think. I've played around with the screen properties on some chinese tablets. Since it's an area the dev rarely messes with, I don't know how much they could do. Especially without a source for the driver. Anyone have the schematic for the touchscreen PIN out? It might be easier swapping wires around then screwing with the software.
Parastie said:
It's not as easy as you think. I've played around with the screen properties on some chinese tablets. Since it's an area the dev rarely messes with, I don't know how much they could do. Especially without a source for the driver. Anyone have the schematic for the touchscreen PIN out? It might be easier swapping wires around then screwing with the software.
Click to expand...
Click to collapse
Actually the drivers source is freely available as it is in the kernel.
you could probably fix it in kernel, but this would mean being forever stuck running a custom kernel.
There is another thread in this section also discussing this http://forum.xda-developers.com/showthread.php?t=1837997 See if post 29 helps http://forum.xda-developers.com/showpost.php?p=31850738&postcount=29
Does anyone here maybe know if there are plans for the "old" Gear Fit to support non Samsung devices? Since I upgraded my phone (HTC One M7) to Lollipop I can't use the smatchwatch anymore. I know there are solutions to connect it to non Samsung devices but most of all I use App Connect applications. They are almost not working and every version needs to be patched for my devices - that's not a proper solution for me.
So I'm slowly thinking of selling / throwing away my handy watch :crying:
I recently sent a mail to assistance....It was unexpected but they answered to me
Unfortunately they go on with their politics and FIT will remain where it is. It must be connected to a samsung device to be fully functional.
Read the forum, every single thread, and you will find a lot of solutions, also patched apps for APP manager, I did it and now I like my FIT.
garrax said:
I recently sent a mail to assistance....It was unexpected but they answered to me
Unfortunately they go on with their politics and FIT will remain where it is. It must be connected to a samsung device to be fully functional.
Read the forum, every single thread, and you will find a lot of solutions, also patched apps for APP manager, I did it and now I like my FIT.
Click to expand...
Click to collapse
Thank you for your response! Too bad Samsung is not going to support it. Patching all the apks I need every time an update occures is just too time-consuming for me - but thank you for your answer!
Ok guys been a while since I've been on here, so I'm sure this is answered elsewhere but need some good advice.
I have an S5 on Verizon my wife and I have been using as our primary source of internet using tethering for the past several years. Obviously the phone is rooted and still running KitKat 4.4.4 on the NI2 kernel. When phone updates and loses root I just roll it back.
So long story short and to the point, we are needing a new phone. This one's performance is degrading and a new battery is still not holding a complete charge for very long.
Looking at the newer Galaxies but needing to continue to be able to root and use the hotspot feature as we use nearly 100GB per month in data. Any suggestions on hardware, etc. is appreciated.
My go-to sources are:
www.kimovil.com / www.devicespecifications.com / china-prices.com (They got Band support in the US covered as well, but ALWAYS check by yourself too) -> https://willmyphonework.net/
I can easily list a bunch of devices, but it'll be your task to figure out if they are supported band wise in the US. Battery/price/quality-ratio-wise:
Le Pro 3 Elite
Coolpad Cool1 Dual
Xiaomi Redmi Note 4X
hurdlesemo said:
Ok guys been a while since I've been on here, so I'm sure this is answered elsewhere but need some good advice...
Click to expand...
Click to collapse
Your best bet is to post this question within one of the following threads that is specific to your question.
http://forum.xda-developers.com/showthread.php?t=1846277
http://forum.xda-developers.com/showthread.php?t=1620179
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Has anyone recently converted an spare android device to a stand alone music player? and when i say this i dont mean just reflash the OS and go aeroplane mode, im wanting basically the music player only like an IPOD touch or old school MP3 player from back in the day.
i have a couple of oneplus ones that i think would be great for this, but not sure if anyone has/have tried and sucessfully done this.
I bought an old sharp 40 year ghettoblaster so wondering if i could incorporate something like this into the existing tape deck, (or even my smaller sharp phone) and it would be powered off a 12v power supply that would need to be stepped down to 5v, i dont need the rest of the functionality either, just a basic player.
Poweramp plus a device that supports large expandable storage and 24+ bit digital output.
blackhawk said:
Poweramp plus a device that supports large expandable storage and 24+ bit digital output.
Click to expand...
Click to collapse
i use poweramp on my devices, love it, but was thinking something light weight as an OS would be cool, as it one without the phone functionality
3rutu5 said:
Has anyone recently converted an spare android device to a stand alone music player? and when i say this i dont mean just reflash the OS and go aeroplane mode, im wanting basically the music player only like an IPOD touch or old school MP3 player from back in the day.
i have a couple of oneplus ones that i think would be great for this, but not sure if anyone has/have tried and sucessfully done this.
I bought an old sharp 40 year ghettoblaster so wondering if i could incorporate something like this into the existing tape deck, (or even my smaller sharp phone) and it would be powered off a 12v power supply that would need to be stepped down to 5v, i dont need the rest of the functionality either, just a basic player.
Click to expand...
Click to collapse
@3rutu5
Hello and good morning.
I hope you'll always find and get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
3rutu5 said:
i use poweramp on my devices, love it, but was thinking something light weight as an OS would be cool, as it one without the phone functionality
Click to expand...
Click to collapse
I wouldn't go too nuts or you'll end up with broken stuff that will suck up time.
Just try using the stock firmware and maybe use adb edits to disable any battery hogs if needed. Dependencies... edit with care.
Simply disabling Google play Services in settings will be enough to keep some of the other Google crapware from running in the background.
Whatever you do, it's a cool project