yashsingh1/xdaforums huggingface dataset:
[Ornate TrueSmart] MrTip:
I am in the same situation. I can't go to recovery, I can't end this boot loop and I don't know if it's related.

I have a backup but nothing changes. I am looking for an out of the box backup to go back to stock. Is there anyone here that can help us out ?

This is part of the looping logcat :

E/ccci_mdinit(1)( 527): open /dev/ccci_monitor fail: 2
I/AEE/AED ( 522): Built Apr 29 2013 22:05:44
E/BGWD ( 525): [BGW]init_socket: get control socket error, reason:Protocol not supported
E/[DRVB] ( 523): [libdrvb.so]mtk_drvb_do_check: DRVB CHECK PROCESS DONE ! STATUS (0x1004)
W/[DRVB] ( 523): [libdrvb.so]sec_drv_base_check: [COLOR="DarkRed"][B]platform is invalid (not MTK)[/B][/COLOR]
W/[DRVB] ( 523): [libdrvb.so]sec_drv_base_check: 5594a740 - 2201db13 - 23035823 - 0d46969d - 58b6e579 - 230c7998
W/[DRVB] ( 523): [libdrvb.a]drvb_f0: DRVB status (0x1002)
W/[DRVB] ( 523): [libdrvb.a]drvb_f0: CRE_PATTER_2 verify fail DRVB(0x46110)
W/[DRVB] ( 523): [libdrvb.a]drvb_f0: CRE_PATTER_2 verify fail (0x046110)
W/[DRVB] ( 523): [libdrvb.a]drvb_crash_heap: DRVB ADDR(0xdc) ~
W/[DRVB] ( 523): [libdrvb.a]drvb_crash_heap: DRVB ADDR(0xdc) ~
W/[DRVB] ( 523): [libdrvb.a]drvb_crash_heap: DRVB ADDR(0xdc) ~
W/[DRVB] ( 523): [libdrvb.a]drvb_crash_heap: DRVB ADDR(0xdc) ~
W/[DRVB] ( 523): [libdrvb.a]drvb_crash_heap: DRVB ADDR(0xdc) ~
W/[DRVB] ( 523): [libdrvb.a]drvb_crash_heap: DRVB ADDR(0xdc) ~
E/[DRVB] ( 523): [libdrvb.a]drvb_crash_heap: DRVB POST PROCESS DONE ! STATUS (0x1001)
E/MobileLogD/DEBUG( 523): mobilel_log_d the chip dismatch.
E/[DRVB] ( 522): [libdrvb.so]mtk_drvb_do_check: DRVB CHECK PROCESS DONE ! STATUS (0x1004)
W/[DRVB] ( 522): [libdrvb.so]sec_drv_base_check: platform is invalid (not MTK)
W/[DRVB] ( 522): [libdrvb.so]sec_drv_base_check: 5594a740 - 2201db13 - 23035823 - 0d46969d - 58b6e579 - 230c7998
W/[DRVB] ( 522): [libdrvb.a]drvb_f0: DRVB status (0x1002)
W/[DRVB] ( 522): [libdrvb.a]drvb_f0: CRE_PATTER_2 verify fail DRVB(0x46110)
W/[DRVB] ( 522): [libdrvb.a]drvb_f0: CRE_PATTER_2 verify fail (0x046110)
W/[DRVB] ( 522): [libdrvb.a]drvb_crash_heap: DRVB ADDR(0xa0) ~
W/[DRVB] ( 522): [libdrvb.a]drvb_crash_heap: DRVB ADDR(0xa0) ~
W/[DRVB] ( 522): [libdrvb.a]drvb_crash_heap: DRVB ADDR(0xa0) ~
W/[DRVB] ( 522): [libdrvb.a]drvb_crash_heap: DRVB ADDR(0xa0) ~
W/[DRVB] ( 522): [libdrvb.a]drvb_crash_heap: DRVB ADDR(0xa0) ~
W/[DRVB] ( 522): [libdrvb.a]drvb_crash_heap: DRVB ADDR(0xa0) ~
E/[DRVB] ( 522): [libdrvb.a]drvb_crash_heap: DRVB POST PROCESS DONE ! STATUS (0x1001)
E/AEE/AED ( 522): debuggerd the chip dismatch: 1
I/6620_launcher( 526): Can't open device node(/dev/stpwmt)
E/Hald ( 129): received error
E/Hald ( 129): Unable to get family id, Retry
D/AndroidRuntime( 524):
D/AndroidRuntime( 524): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit (start-system-server) <<<<<<
D/AndroidRuntime( 524): JNI trace buf :-Xjnitrace:
D/AndroidRuntime( 524): CheckJNI is OFF
D/AndroidRuntime( 524): language=-Duser.language=en region=-Duser.region=US
E/dalvikvm( 524): ERROR: must specify non-'.' bootclasspath
D/dalvikvm( 524): [COLOR="DarkRed"][B]VM shutting down[/B][/COLOR]
[Ornate TrueSmart] -Android Freak-:
I would love to install TWRP. When I tried last time is when my watch got bricked. :(

I think that back then in May there was no TWRP for my version of my watch (4th shipping list) EU version 1/8/2100.

Does TWRP work for this hardware version now?

Anyone installed/flashed TWRP to this version of watch? Any guide available?

Only guide I found was for 1/8 1900MHz and that bricked the watch. :(

Thankful for any help!
[Ornate TrueSmart] kuronosan:
Twrp should work just fine. I think it's a partition problem.
[Ornate TrueSmart] -Android Freak-:
I have tried three different "out of the box" backups... None worked. What did you do when your watch got bricked? Did you follow any specific guide? Which one? If you are in the same situation as me, it happened when flashing TWRP.
[Ornate TrueSmart] MrTip:
I installed TWRP with this method. The install failed, but I could boot normally for some time. Then, after something trivial (I think i was installing an app and deleting dalvik-cache), I entered in bootloop. Since then, wiping user data and flashing previous system backup does nothing good.
[Ornate TrueSmart] lirona:
Hi,

When I try to install the ROM I get a ERROR: update the partition.

What I need to do?

Please help.

Thanks,

Arie.
[Ornate TrueSmart] kuronosan:
Those of you with boot loop are likely using the wrong kernel.
[Ornate TrueSmart] -Android Freak-:
Ok, so the TWRP install failed. Same for me. But mine stopped booting at all after that. Did you have TWRP after this even though the install failed? I imagine you booted into recovery to wipe dalvik cache?

Seems scary to try install TWRP if it fails often. Maybe I will try again with the same guide you used.

---------- Post added at 07:56 AM ---------- Previous post was at 07:56 AM ----------

Ok.... how do we correct that? :)
[Ornate TrueSmart] MrTip:
Have you seen the logs I pasted here ? Do you have something similar ?

I would like very much to try a different backup. Do you have a recent one I could try ?
[Ornate TrueSmart] -Android Freak-:
My error log is not verh similar. Check 2 or three pages back in this thread for the log.

I have a backup I could put online somewhere during the weekend. Stay tuned...
[Ornate TrueSmart] kuronosan:
You would have to flash the original factory image.
[Ornate TrueSmart] MrTip:
OK, that was exhausting, but I could finally make it work.

To summarize, this is my undertanding :

MktDroidTools: Good to backup, very wrong to flash.

SP Flash Tool: No backup, very very good to flash.

First, I used MktDroidTools to flash TWRP recovery. The flash was succesfull, but not the recovery. Normal boot was OK, recovery was busted.

Then I used MktDroidTools to do a backup (a bit late, I assume).

Then, I used linux adb+fastboot and/or MktDroidTools to flash older stock backup (Omate_1-8_2100_TrueSmart_20140328). It ended normally: In a bootloop.

But when I tried to go back with the same methods to my previous backup there was still a bootloop. Weird.

Well, MktDroidTools is using adb, while SP Flash Tool is using the PreLoader.

I had trouble making SP flash tool working, but it's worth the pain. When I tried to flash the older stock, SP flash tool was very clear: the scatter is different.

No wonder nothing worked, it's probable MktDroidTools I messed up the partitions. It's unlikely I could restore anything with MktDroidTools.

So:

Launched SP flash tool

Choosed MT6572_Android_scatter.txt from my backup

Checked ANDROID partiton and add system.ext4.img file (This one is important, I don't know why it is not done by default, I struggled to find it)

Hit Download

Plugged in the (switched off) TS

Now, the TS boot normally.

Still no recovery, so I'm still looking for a recent 1/8/2100 stock backup . Cherry on top, I found in this very thread the stock backup I needed. Now I have the crappy basic recovery, as god intended.

Now, the difficult part: I have to do nothing and wait for TWRP and tether ROM for firmware 1/8/2100 20140513.

Hope this helps.
[Ornate TrueSmart] -Android Freak-:
Thank you for the very detailed description of what you did to make it work.

My PC has decided to not boot anymore right now so I will have to find a way for this to work on a windows 8 machine. Keep ypur fingers crossed!

Thank you again!
[Ornate TrueSmart] dragonfly1113:
not sure if this issue is rom dependant or if its general os issue if its general moderator please move it to the qa section, but just curious if offline voice recognition is possible on the device with this rom installed? every time i go to voice type it doesnt work says it cannot connect to google servers which makes me think that it doesnt have offline recognition. tried searching through the forums in the truesmart section cant find any results for it yet.

thanks.
[Ornate TrueSmart] kuronosan:
Of course it doesn't.

Google needs the internet... although I think you can download dragon/nuance and get offline recognition.

posted using my towelrooted Galaxy S5.
[Ornate TrueSmart] dragonfly1113:
I currently have dragon Swype and don't see the option in there either

sent from my note 3 running beans.
[Ornate TrueSmart] -Android Freak-:
I have now tried my own backup, a fresh backup from a freidn who just unpacked his TS and several images from XDA. My device still refuses to boot. I'm stuck at the boot logo... :(
[Ornate TrueSmart] soulcrusher:
TWRP does not work on my 1/8/2100 TrueSmart. GooManager says it cant find compatible recovery and when I flash it myself I cant boot into recovery and it reboots back into android. How do I get TWRP on the TS?
[Ornate TrueSmart] MrTip:
Sadly, it seems that last firmware (20140513) does not not work with version 1.1.1 (at least TWRP, preventing tether rom to be tested)

Is there a way to install tether rom without using recovery ? (adb or fastboot maybe)

Is there a new version of tether rom scheduled to work with firmware 20140513 ?

Thank you.
[Ornate TrueSmart] Bushrod:
The rom's creator, Dees_Troy, has not posted in this thread since April 19. I would not expect any further development or assistance with this ROM and would classify it as abandonware.

I would love to be wrong!

That being said, thank God it works on my TrueSmart!
[Ornate TrueSmart] MrTip:
I also would love you to be wrong.

If it's no more maintained, maybe Dees_Troy would allow someone else to do so. ( sadly, I'm a developer knowing almost nothing about android )
[Ornate TrueSmart] kuronosan:
Um, no.
[Ornate TrueSmart] ransoma22:
Need help from the people here.

After I flash this BT ROM, my sensors failed to work.

am using 512MB/4GB, previously coming from Loki EnSec Rom, working fine until i started to flash this BT ROM.

Any ideas how to make my sensors work again ?

:confused:
[Ornate TrueSmart] deados:
1GB/8GB/2100MHz model

Hello,

I have got a 1GB/8GB/2100MHz model and I could send you all the backup of my TrueSmart.

My device have a lot of deconnection and if you can offer to us a properly working boot.img, it could be fine !

And you will make a lot of happy geeks !!!

Thanks in advance,

PS : Sorry for my poor english.
[Ornate TrueSmart] MrTip:
Maybe it's the method, not the rom. IMHO there no reason you can't go back to stock.
[Ornate TrueSmart] Lokifish Marz:
If the backup was from the newer PCB and he has an older PCB version, it would not boot. The PCB versions have to match. Also, in some cases the MTKDroid tools backup is incomplete.
[Ornate TrueSmart] MrTip:
Answer to myself.

I managed to go back to previous firmware (physical format with sp flash tool). The device didn't boot, unfortunately.

But with latest firmware and mtkdroidtools, I managed to install CWM !

(I will describe how later, have no time right now)

With no physical button, I can't use cwm directly, but I can still backup and restore from recovery with app "ROM installer"

Also, now I can try to install BT tether rom. So... back to this thread.

This is the error I get in recovery.log when trying to install bt tether rom:

SD Card mounted...
Verifying SD Card marker...
I:Running script:
I:
run_program("/sbin/cp", "-R", "/cache/recovery", "/tmp/recovery");
ui_print("ROM Manager Version 5.5.3.7");
ui_print("July 4, 2014");
ui_print("Preparing to install ROM...");
mount("/system");
run_program("/sbin/chmod", "+x", "/tmp/recovery/11-rommanager.sh");
run_program("/tmp/recovery/11-rommanager.sh", "place");
run_program("/sbin/umount", "/system");
assert(install_zip("/sdcard/bt-rom-1.0.0-1GB-8GB-2100MHz.zip"));

parse returned 0; 0 errors encountered
about to run program [/sbin/cp] with 4 args
ROM Manager Version 5.5.3.7
July 4, 2014
Preparing to install ROM...
about to run program [/sbin/chmod] with 3 args
about to run program [/tmp/recovery/11-rommanager.sh] with 2 args
mount: mounting /dev/block/mmcblk0p4 on /system failed: Device or resource busy
about to run program [/sbin/umount] with 2 args

-- Installing: /sdcard/bt-rom-1.0.0-1GB-8GB-2100MHz.zip
Finding update package...
I:Update location: /sdcard/bt-rom-1.0.0-1GB-8GB-2100MHz.zip
Opening update package...
Installing update...
Warning: No file_contexts
script aborted: assert failed: getprop("ro.product.device") == "x201"
assert failed: getprop("ro.product.device") == "x201"
E:Error in /sdcard/bt-rom-1.0.0-1GB-8GB-2100MHz.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/bt-rom-1.0.0-1GB-8GB-2100MHz.zip")

root@android:/storage/sdcard1/clockworkmod # getprop ro.product.device
x201

root@android:/storage/sdcard1/clockworkmod #

The last assert failed is weird because a getprop gives me the correct answer.

Any idea ?
[Ornate TrueSmart] -Android Freak-:
Thanks Loki for answering!

Ok, I guess that the MTK backups I've used haven't been complete. I tried now for a month to get the watch to boot with many different versions of backups, formatting in between. I'm close to giving up now.

Anyone have a comlete working backup for the april shipment 1/8/2100 watch?

Thanks!
[Ornate TrueSmart] kuronosan:
Why are you not using Twrp for the install?
[Ornate TrueSmart] MrTip:
Because I can't. TWRP won't work with latest firmware and because TWRP team, like many, lost interest in TS before a lot of us even received the device, we have to be creative.
[Ornate TrueSmart] kuronosan:
Do tell.
[Ornate TrueSmart] MrTip:
Using this message (step 7) I managed to get CWM on my TS.

BT tether Rom fails to install with latest firmware. Previous post shows recovery.log

It is probably a change in partition, hope it won't be too hard to correct.

mount: mounting /dev/block/mmcblk0p4 on /system failed: Device or resource busy

Just saying ;)
[Ornate TrueSmart] kuronosan:
I need to pull apart the stock recovery image for 0513/0527 (which means I'll need it from someone's backup probably) so I can compare partition tables.

From there I can rebuild the recovery.
[Ornate TrueSmart] BPM:
i got my aluminum version yesterday, but i am not at home until weekend and do not have access to a useable computer.

if nobody provides the backup before weekend i will do this on sunday.

you need a backup made with MTK Tools?
[Ornate TrueSmart] MrTip:
This should be helpfull: MT6572_Android_scatter.txt files from stock 20140328 firmware and from my own backup (20140513 firmware).
[Ornate TrueSmart] kuronosan:
Yes.

I already have all the scatter files and copies of all the firmwares. What I don't have is the recovery that is on those watches so that I can see why it's so different. I can't trust the recovery image I have from the 0527 firmware because the package I received is semi-corrupt.
[Ornate TrueSmart] BPM:
will put it on my webspace and provide the link on sunday
[Ornate TrueSmart] Aerox912:
I can send you the original recovery from the 0527 firmware if you need it. Still have it here
[Ornate TrueSmart] MrTip:
I blew my own recovery before I did any backup, but Omate_TrueSmart_20140513.103530_V2.0.zip gave me a functional stock recovery. Do you have this one ?
[Ornate TrueSmart] kuronosan:
Yes. Someone provided it for me.

Actually, what I need is for someone to go into an adb shell (who owns an aluminum unit) and type this command (requires root):

adb shell

su

parted /dev/block/mmcblk0 print

And copy/paste the result here. From there I'll be able to compare and make adjustments and try to compile a new recovery.
[Ornate TrueSmart] midafaya:
edit : wrong post
[Ornate TrueSmart] techknight180:
Trojan found -Kaspersky?

Kaspersky found a Trojan in the bt-rom-1.0.0-1GB-8GB-1900MHz.zip/system.tgz/system.tar/app/SmsReg.apk/classes.dex Is this correct?
[Ornate TrueSmart] kuronosan:
No, it isn't.
[Ornate TrueSmart] agustaf:
locking for firmware/ scatter file 512/4 2100MHz

Sorry friend,

you wrote below you have copies of all scatter file and firmwares! If it's true please share the files with me.

I'am looking for the scatter files and firmwares for the 512/4 2100MHz TS.

My watch has a brocken firmware I think. Failure during flashing the firmware with sp-flash witout saving. Error message - BROM_ERROR: S_BROM_CHECKSUM16_MEM_RESULT_DIFF (2020).

I don't no how but I believe I can restor the watch with the right firmware and scatter file.

Thank you for helping
[Ornate TrueSmart] kuronosan:
That's a tough one. Let me see what I can find.
[Ornate TrueSmart] DrLex:
Tweaked APKs

I used this ROM as a basis for a custom ROM for the Abardeen F80, with success. Thanks a lot to Dees_Troy and others who contributed to this ROM, because fixing problems in the stock F80 ROM was hopeless.

I made layout tweaks to several APKs that can be back-ported to this ROM, so I thought I'd share them here.

Contacts.apk: optimized the layout of the dialer, resolution tweak is no longer needed.

Phone.apk: similar fix for in-call dial pad.

MtkBt.apk: taken from the F80 ROM. This one adds support for Bluetooth input devices. I didn't test tethering, but when comparing with the original, I am pretty sure this one only adds features without removing any.

SoundRecorder.apk: now usable without resolution tweaks.

SetupWizard.apk: made the ‘start’ button accessible so the wizard can be used normally.

framework-res.apk: improved lock screen layouts (especially pattern lock).

The APKs can be swapped on a live ROM if you know what you are doing, but the safest way is to make the modifications in the system image and re-flash it, and purge the Dalvik cache. Of course, use at your own risk.

I also found a way to make OOM settings stick: because something seems to overwrite them after init.d, do the call in a ‘delayed fork’. Add this to the end of /etc/init.d/99loki:

(
sleep 30;
echo "4096,8192,16384,32768,49152,65536" > /sys/module/lowmemorykiller/parameters/minfree;
) &
[Ornate TrueSmart] mechrekt:
Recovery problem

Hi Dees_Troy,

thank you very much for your work. For me the problem is that after installed TWRP recovery with success from SP Flash Tool I cannot go into recovery. I did not found any documentation to do this, then I tried pressing both buttons from watch turned off. The a menu appears showing me to press power button for recovery or home button for "factory": I press power but the watch normally boots and no recovery appears.

Many thanks
[Ornate TrueSmart] Really now:
You need to go into settings and turn off quick boot. Then do what you did last and you'll get into TWRP
[Ornate TrueSmart] mechrekt:
Already done without success
[Ornate TrueSmart] kuronosan:
You're probably installing the wrong recovery image.

What watch do you have, and which image did you install?
[Ornate TrueSmart] mechrekt:
I've the EU version 1/8/2100 I think the 4th shipment. I did not buy the watch from kickstarfer but from omate pre-order site.

Baseband version: MOLY.WR8.W1315.MD.WG.MP.V 4, 2013/08/14 18:16

Kernel version: 3.4.5

Custom build version: Omate_Truesmart_20140513.10 3530_V2.0

I've used both the "openrecovery-twrp-2.7.0.0-omatesmartwatch2.img" and "openrecovery-twrp-2.7.1.0-omatesmartwatch2.img" installed with MTK Flash Tool using instructions on the TWRP site.
[Ornate TrueSmart] mechrekt:
I did a test also with "openrecovery-twrp-2.6.3.0-omatesmartwatch2.img" but the same result.

If I hit power butto to enter recovery, I see omate logo for several seconds, then the watch normally boots.

---------- Post added at 12:45 PM ---------- Previous post was at 12:33 PM ----------

I found another TWRP image "twrp-2.7.0.0-omate-x201.img" into the "TS-EU-0706-May_Shipment.rar" file (I cannot remember where I found this file on xda) and it works!

This afternoon I hope to have time to install the ROM :o:o:o
[Ornate TrueSmart] mechrekt:
I did ADB sideload with TWRP with Bluetooth Theter ROM but I got bootloop...
[Ornate TrueSmart] kuronosan:
Did you wipe data and factory reset?
[Ornate TrueSmart] mechrekt:
Yes, but nothing to do...

---------- Post added at 09:07 PM ---------- Previous post was at 08:58 PM ----------

I don't know if it make sense but I solved doing this:

after installing "Bluetooth Tether ROM" I installed the "TS-EU-0706-patch" from "07.06 EnSec STOCK Secure + Root" ROM.

So I was able to boot the phone and try "Bluetooth Tether ROM"!

Now the problem is that bluetooth tether from my smartphone doesn't work. I followed instructions but no internet connection trough the smartphone also if on the smartwatch it says "Connect Group Ad-Hoc Network with smartphone Succesfully!"

I shared internet via bluetooth connection to another smarphone with success, so I think the problem is with the smartwatch :crying:

---------- Post added at 09:46 PM ---------- Previous post was at 09:07 PM ----------

I did a try with "monxDIFIED™ EZ SMART" ROM.

It works (without installing the "TS-EU-0706-patch") and also bluetooth thetering from a smartphone.

But I like to have "Bluetooth Tether ROM", because it seems more polite (less preinstalled apps) and I prefer the rotated camera.

What can I do to get "Bluetooth Tether ROM" with bluetooth tether working? :p

thank you
[Ornate TrueSmart] kuronosan:
You need to flash a kernel that's supports it.

It's no surprise that the MONX ROM works for you because it's a kang of this ROM and includes the proper boot.img.
[Ornate TrueSmart] mechrekt:
So can I try to install Bluetooth ROM then install boot.img from Monx ROM?

thank you
[Ornate TrueSmart] mechrekt:
Ok,

maybe I need some help now. If I understand correctly, I should be able to install "Bluetooth Thether ROM" and use the kernel from "Monx ROM" to get the tethering working with my specific watch?

Ho can I do please?
[Ornate TrueSmart] mechrekt:
Help [emoji4]
[Ornate TrueSmart] kuronosan:
Sorry, I was waiting to see if monx was going to answer your question.
[Ornate TrueSmart] mechrekt:
No replies for me? :silly:
[Ornate TrueSmart] kuronosan:
Install his ROM, then install this one. It's that easy.
[Ornate TrueSmart] mechrekt:
Doing this it doesn't overwrite the kernel?
[Ornate TrueSmart] mechrekt:
I've installed "Bluetooth Thether ROM" over "Monx ROM" but I got bootloop... :crying::crying:
[Ornate TrueSmart] kuronosan:
Did you factory reset?
[Ornate TrueSmart] mechrekt:
Hi Dees_Troy,

thank you very much for your work. I like your ROM very much. Sorry to be repetitive, but I'm not able to run bluetooth tethering from my smartphone: this is the only thing that doesn't works because other kind of bluetooth connections works.

can someone help me please? I'm the only person with this rom and this problem?

(sorry for my bad english!)
[Ornate TrueSmart] kuronosan:
Uh did you enable it on your phone?
[Ornate TrueSmart] nkognegr0:
yes i enabled bluetooth tethering on my phone and still nothing.
[Ornate TrueSmart] lirona:
Hi,

This ROM is very good to me, I love it very much.

How can I get the Watch faces that was on the watch before?

Thanks and have a good day,

Arie.
[Ornate TrueSmart] Bushrod:
Derp. Thought it wasn't working but I had forgotten to enable on phone! Working great!

I'm using Button Savior for onscreen back and settings soft keys to replace the swipes.
[Ornate TrueSmart] kuronosan:
What carrier?
[Ornate TrueSmart] nkognegr0:
tmobile and its a note 3. now i did put a aosp rom on it and was able to connect. doesnt matter anyway i wont have the note 3 for to much longer.
[Ornate TrueSmart] kuronosan:
That's why. Tmo doesn't allow tethering on stock Rom.
[Ornate TrueSmart] Charlie_Brown84:
Camera not working

Does anyone have issues with camera being rotated? I reinstalled factory reset clear dalvik. Am I missing something?
[Ornate TrueSmart] trent999:
I tether using T-Mobile on the $30 5gig prepaid card on my nexus devices. There was no check prior to KitKat, but there is a simple non-root workaround even for KitKat.

That is probably what the problem with the Note3 was though.
[Ornate TrueSmart] nkognegr0:
my plan comes with tethering included so that cant be true and i dot use stock roms! also there is a guy with a sony z1 who has same issue. i put a aosp rom on and it did work just not for very long.