[ROM] Bluetooth Tether ROM for Omate TrueSmart 1.1.1 [2014-04-25]

[kuronosan]

Because it's a custom ROM.

Sent from my Galaxy Nexus using Tapatalk 2

 

[figers]

from the watch on wifi I installed framaroot and rooted the device

then I installed goomanager from the play store and installed the recovery with this. With Root access this app boots you right into recovery mode.

My issue is that after using this ROM and bluetooth internet sharing flawlessly for most of the day the watch no longer has internet access even though it all still shows it's connected correctly. The phone even shows one device is connected over bluetooth internet tethering.

I wish there were easy steps to reconnect. turn off bluetooth, unpair, repair, allow bluetooth tethering, use phone as internet access, reboot, many combinations and I still don't have internet on the watch.

Loved it while it was working!!!

 

[lirona]

At a guess, because unless things have changed, the oStore contains only broken apps, apps without descriptions and copies of apps available from the play store. Is there something specific you are looking for from the oStore?

jd

Hi,
Thanks, Yes I want games that I can play on the watch and the OwatchOn app and watch faces.
Thanks,
Arie.

 

[Lokifish Marz]

@lirona

OwatchOn. Won't find it, it's been pulled.

There are hundreds, if not thousands, of games that work on the x201 that you can install from the Play Store.

 

[Bushrod]

My issue is that after using this ROM and bluetooth internet sharing flawlessly for most of the day the watch no longer has internet access even though it all still shows it's connected correctly. The phone even shows one device is connected over bluetooth internet tethering.

I wish there were easy steps to reconnect. turn off bluetooth, unpair, repair, allow bluetooth tethering, use phone as internet access, reboot, many combinations and I still don't have internet on the watch.

Loved it while it was working!!!

I just did a dirty flash, wiped cache/dalvik and rebooted. Came back up and tethering is working again. I'm thinking in the future to try the cache/dalvik wipe alone and see if that works.

 

[kuronosan]

I've never had an issue unpairing, turning off Bluetooth on both devices, rebooting the watch, pairing again, and re-enabling tethering and access with regards to restoring internet.

It's a pain in the ass but then again my connection doesn't drop often.

Sent from my Galaxy Nexus using Tapatalk 2

 

[jwheeler73]

PSA -
Don't accidentally push the "switch to front camera" button in the camera app like I did. It just pops up an error that the camera cannot be found and sticks so that just closing and reopening the app does not switch it back to the rear camera. You have to force stop and clear data for the Gallery app for it to reset.

 

[figers]

I just did a dirty flash, wiped cache/dalvik and rebooted. Came back up and tethering is working again. I'm thinking in the future to try the cache/dalvik wipe alone and see if that works.

This worked for me, but what a pain, on reboot it has to rebuild all the apps again...

Then I lost bluetooth internet again 30 minutes later...

---------- Post added at 02:33 PM ---------- Previous post was at 01:56 PM ----------

I've never had an issue unpairing, turning off Bluetooth on both devices, rebooting the watch, pairing again, and re-enabling tethering and access with regards to restoring internet.

It's a pain in the ass but then again my connection doesn't drop often.

Sent from my Galaxy Nexus using Tapatalk 2

Thanks for the suggestion, sadly that didn't work for me...

 

[Bushrod]

This worked for me, but what a pain, on reboot it has to rebuild all the apps again...

Then I lost bluetooth internet again 30 minutes later...

---------- Post added at 02:33 PM ---------- Previous post was at 01:56 PM ----------


Thanks for the suggestion, sadly that didn't work for me...

Yeah, that's why I abandoned this rom. I'm back to using EasyTether with Operative. 4 hours 10 minute connection that I broke manually when I went into a non-wireless office. Only have to reboot watch once to regain ability to tether after dropping connection.

 

[sickysickybrah]

I installed this ROM last night and so far I am really liking it - Thank you very much! :good:

My only issue that I am thus far seeing is that the keyboard UI takes up almost the entire screen so you cannot see what you are typing into. Also, the Phone UI does not allow you to see the numbers "1, 2, 3"

Bluetooth works well and this is the first fix that allows my computer to connect properly to my TS. I like fitting more apps on my home screen too and when I turn my screen on it doesn't start with that goddamn stupid watch face :laugh:

Awesome

 

[Nick123194]

I installed this rom this morning and it's working smoothly!

Thank you!

 

[Dees_Troy]

from the watch on wifi I installed framaroot and rooted the device

then I installed goomanager from the play store and installed the recovery with this. With Root access this app boots you right into recovery mode.

My issue is that after using this ROM and bluetooth internet sharing flawlessly for most of the day the watch no longer has internet access even though it all still shows it's connected correctly. The phone even shows one device is connected over bluetooth internet tethering.

I wish there were easy steps to reconnect. turn off bluetooth, unpair, repair, allow bluetooth tethering, use phone as internet access, reboot, many combinations and I still don't have internet on the watch.

Loved it while it was working!!!

I put some steps in the OP:
"Bluetooth on MTK is somewhat unstable. If it disconnects, especially due to a driver crash, you'll probably have to reboot the device to get Bluetooth working again. You may be able to get it working by power cycling Bluetooth or turning off/on airplane mode."

No other steps are needed. I have run into a few cases where I had to power cycle Bluetooth on my Nexus 5 and re-enable tethering on the Nexus 5. Apparently Bluetooth on even the Nexus 5 isn't completely 100%, but this is rare, once every week or so.

I've thought about spending some more time trying to make the Bluetooth connection faster and more reliable, but I'm unsure of how I want to continue. The ROM base I'm using was intended for a completely different MTK 6572 device. The source code that Omate gave us is supposed to be for the TrueSmart, but when I compiled the full ROM and flashed it, the device fails to boot so badly that adb never starts up. No adb means no logcat which means that it's going to be nearly impossible to troubleshoot. It's pretty sad that the source code that Omate gave us works worse than source code intended for a completely different device.

I was hoping to be able to port my changes into the Omate source code and build something that's closer to stock. Now I'm stuck wondering if I should continue trying to develop on a different base that's basically going to be a dead end. Honestly, better devices like the Moto 360 are coming soon and I'm not sure that the Omate TrueSmart is worth all the trouble.

 

[rhineymac]

I put some steps in the OP:
"Bluetooth on MTK is somewhat unstable. If it disconnects, especially due to a driver crash, you'll probably have to reboot the device to get Bluetooth working again. You may be able to get it working by power cycling Bluetooth or turning off/on airplane mode."

No other steps are needed. I have run into a few cases where I had to power cycle Bluetooth on my Nexus 5 and re-enable tethering on the Nexus 5. Apparently Bluetooth on even the Nexus 5 isn't completely 100%, but this is rare, once every week or so.

I've thought about spending some more time trying to make the Bluetooth connection faster and more reliable, but I'm unsure of how I want to continue. The ROM base I'm using was intended for a completely different MTK 6572 device. The source code that Omate gave us is supposed to be for the TrueSmart, but when I compiled the full ROM and flashed it, the device fails to boot so badly that adb never starts up. No adb means no logcat which means that it's going to be nearly impossible to troubleshoot. It's pretty sad that the source code that Omate gave us works worse than source code intended for a completely different device.

I was hoping to be able to port my changes into the Omate source code and build something that's closer to stock. Now I'm stuck wondering if I should continue trying to develop on a different base that's basically going to be a dead end. Honestly, better devices like the Moto 360 are coming soon and I'm not sure that the Omate TrueSmart is worth all the trouble.

you are one of the last remaining dev to say that. At this rate theres going to be no devs left. Yet llp still believes this is the best thing since sliced bread. I say bring on the Moto 360 and the ts can go in the drawer with my other useless KS devices where it belongs

 

[sickysickybrah]

you are one of the last remaining dev to say that. At this rate theres going to be no devs left. Yet llp still believes this is the best thing since sliced bread. I say bring on the Moto 360 and the ts can go in the drawer with my other useless KS devices where it belongs

It's awful the way this turned out. I was excited about supporting a smaller startup company instead of giving my money to the majors. Promises were made and not kept.

Regardless, thanks for all your hard work Dees_Troy and thank you to all the other developers helping out. With any luck things will be made right, but if not, I learned a lesson about jumping on the bandwagon too early.

 

[agaruut]

driver for windows 8.1?

driver for windows 8.1?

 

[cyrilp]

adb means no logcat which means that it's going to be nearly impossible to troubleshoot.

hi, is it still the case ? i was about to install your ROM to be able to work on The bt conection for SWApp Link, but not having any logcat would be damn annoying !

Envoyé de mon D5503 en utilisant Tapatalk

 

[Dees_Troy]

hi, is it still the case ? i was about to install your ROM to be able to work on The bt conection for SWApp Link, but not having any logcat would be damn annoying !

Envoyé de mon D5503 en utilisant Tapatalk

I've been using SWApp the last couple of days and it works fine. The cloud based messaging works since the device has an Internet connection when tethering over Bluetooth.

 

[cyrilp]

I've been using SWApp the last couple of days and it works fine. The cloud based messaging works since the device has an Internet connection when tethering over Bluetooth.

great i'm in the middle of installing your ROM right now

is logcat really broken ? it wouldn't help for developing...

 

[vapermonkey]

so every thing seems to be working great but Bluetooth tethering it looks like it connected great but there is no data being shared i am going to call t-mobile but all them jerks are going to tell me is to wipe my phone lol running n5 with Mahdi ROM so i don't know

 

[firfist_ace]

Google play prob

Awesome . Only have one problem. Google play isn't working. Keeps saying "unfortunately Google play has stopped." Have rebooted and reinstalled but still encountering the same problem. Any solutions? Everything else is amazing