yashsingh1/xdaforums huggingface dataset:
[Shield Android TV General] CableBurner:
Hi,

it looks good so far, but the USB 3.0 sometimes don't come up properly, but as soon as you unplug one device every device comes up. I think its more often with a warm boot (power not unplugged). The device on the OTG port always works. I thinks its due to power management, and kernel disables USB voltage in an early state. Note that also Ethernet does not work in this state as its hooked to internal USB. I will look into this today.

Edit: you must flash: tegra210-foster-e-p2530-0930-e02-00.dtb

reference: http://nv-tegra.nvidia.com/gitweb/?...ob_plain;f=README_SHIELD;hb=rel-22r18-partner

I do not build modules. And i use a customized version of your config, with some camera driver disabled und the most important thing: the Tegra Watchdog which cause a freeze followed by a reboot after 1minute or so. It seems also safe to disbale most of the Android stuff linke BINDER, LOWMEM_KILLER etc... but it does not boot if CONFIG_ANDROID is disabled in general. I will also look into this. But highest priority is USB.

My defconfig is attached.

I use the 1.3 bootloader :)
[Shield Android TV General] yahoo2016:
I believe the key to solve stability issues of L4T kernel is to make some changes to "tegra21_defconfig" as you did.

I'm glad you are using 1.3 bootloader, I have not seen SATV being bricked with 1.3 bootloader as long as bootloader (staging) partition is not overwritten.

Current Android will not work with new L4T dtb, but the next Android update might.

Those L4T modules are not needed since L4T rootfs has already have those modules after "apply_binaries".
[Shield Android TV General] CableBurner:
Hi,

if you select yes (=y) in the kernelconfig, a particular driver is built hard into the Image, so you dont need it in userspace. If you select m for module just a reference to the module is built into the kernel, than you need a module in userspace/rootfs.

Have you built with my recipe? Can anybody confirm that usb behaviour?

Udo
[Shield Android TV General] yahoo2016:
I'll try to built L4T kernel with your "config" and try to append dtb to kernel. Since my SATV was bricked recently I'm still hesitating to touch dtb partition after reading at least 2 members bricked their SATV by replacing dtb.
[Shield Android TV General] CableBurner:
I understand your concern :) I was also quite stressed during the first dtb flashing ;)

How did the "dbt brick" manifest? Was there black screen or were the 2 members just not able to get into bootloader? Do you remember the name of them? I would like to discuss this, because its and interesting and important topic.

Anyway, there is an BUILD_ARM64_APPENDED_DTB_IMAGE option in the kernel, there is also a BUILD_ARM64_APPENDED_DTB_IMAGE_NAMES with a string to specify the name of the dtb. The old method ARM_APPENDED_DTB_FILE and then CAT is not supported in ARM64 although there is an inofficial path from a huawei employee.

But afaik this all works only with a compressed zImage, and i was not able to boot a zImage. Maybe i had the wrong config for compression mode set...

Best Regards,

Udo
[Shield Android TV General] yahoo2016:
The first reported brick by replacing wrong dtb is:

http://xdaforums.com/showpost.php?p=64722462&postcount=82

The OP of the original utoic thread also bricked his SATV by testing different dtb:

http://xdaforums.com/showpost.php?p=64727652&postcount=215

Neither member reported back if the was able to recover their SATV.

Neither member mentioned which bootloader was used.
[Shield Android TV General] raubtier2:
I was not able to recover my shield. But I got a new device from NVIDIA yesterday.

My bootloader came from installation of 2.1.

Maybe this helps.
[Shield Android TV General] CableBurner:
Hey,

but did you see the nvidia logo? Or just black screen?

Regards,

Udo
[Shield Android TV General] yahoo2016:
Thanks for the update. Nvidia has the best warranty.

When I had my SATV back I could not find ways to bypass OTA, it automatically updated to 2.1, . Recovery mode was hardly working for 2.1 and I reflashed it to 1.3 to have recovery mode working reliably.
[Shield Android TV General] raubtier2:
There was a discussion a few weeks ago in this thread. I saw the logo, but I was

not able to log into fastboot. I tried a lot, without success.
[Shield Android TV General] CableBurner:
Suspicious...

Btw is there any way to see what bootloader version is installed? I want to doublecheck which version i am on.

Regards,

Udo
[Shield Android TV General] raubtier2:
Yes it was a long journey, but in the end it was no problem to get another box. from NVIDIA.

So I am very happy with NVIDIA to get a new box.
[Shield Android TV General] yahoo2016:
I used "sudo fastboot getvar all", the following is what I got for ROM 1.3:

$ sudo fastboot getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version-mts: NO SUPPORT YET!
(bootloader) version: 0.4
(bootloader) mid: 001
(bootloader) product: t210ref
(bootloader) secure: No
(bootloader) unlocked: Yes
(bootloader) partition-size:bootloader: 0x0000000000200000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000001980000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000001980000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:dtb: 0x0000000000400000
(bootloader) partition-type:dtb: basic
(bootloader) partition-size:system: 0x0000000080000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x0000000010000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000002d8e63e00
(bootloader) partition-type:userdata: ext4

I do not have ROM 2.1 and not sure what's the difference between bootoaders of 1.3 or 2.1 from the print out of "sudo fastboot getvar all".

It's interesting that "product" showed as " t210ref".
[Shield Android TV General] liamvanunu1:
cool

cool
[Shield Android TV General] yahoo2016:
I compared your "shieldTv_L4T_defconfig" with my "shieldTv_defconfig" and noticed you have "CONFIG_ANDROID_PARANOID_NETWORK=y".

I had to change it to "CONFIG_ANDROID_PARANOID_NETWORK=n" to make Ethernet working, I have comment at top of my "shieldTv_defconfig".
[Shield Android TV General] CableBurner:
Does USB work? Sometimes it does not work. Especially wenn its a warm boot (not unplugged before)
[Shield Android TV General] yahoo2016:
Have you tried a powered USB hub? I have been using powered HUB for KB/mouse.

Other members have reported USB issues for different kernels/rootfs. Powered USB hub seems solved the issues.
[Shield Android TV General] CableBurner:
So when a powerd hub is plugged in, will also the Ethernet Chip stay alive? Because its also powered off together with the external mouse and keyboard.
[Shield Android TV General] yahoo2016:
I don't believe Ethernet issue is related to USB issue.

Changing your defconf to "CONFIG_ANDROID_PARANOID_NETWORK=n" may fix your Ethernet issue.
[Shield Android TV General] CableBurner:
For me it's usb related: The Ethernet nic is connected to the Tegra XHCI controller and doesn't even show up in lsusb or kernel-log. As soon, as i plug the mouse and the whole usb is powerd up, i see the realtek nic in usb and kernel-log....

Edit: the CONFIG_ANDROID_PARANOID_NETWORK just prevents certain user groups from creating sockets, but my problem is hardware related.
[Shield Android TV General] yahoo2016:
Can you try L4T R23.1 stock kernel to see if you have USB/Ethernet issues? Other members have reported L4T R23.1 stock kernel/dtb works for SATV, but unstable. None seems to mention Ethernet issue.

"tegra21_defconf" is very different from "shieldTv_defconf". "tegra21_defconf" is for new kernel source, "shieldTv_defconf" is for old kernel source. I would modify "tegra21_defconf" for L4T R23.1 instead of modifying "shieldTv_defconf".
[Shield Android TV General] CableBurner:
Hi,

i tried tegra21_defconf and tegra21_android_defconf but i couldn get it working during acceptable time...

As i need the shield with stable USB etc working on my robot because i will head to a competition i switched to 22r18 now. This one works very well, except poweroff after shutdown. I removed most of the Android stuff and i am quite happy with it so far. I will stick into L4T kernel again if i have some time soon :)
[Shield Android TV General] yahoo2016:
I'm pretty happy with CM1.2 kernel and L4T 23.1 rootfs. My main purpose using Shield is for Cuda development. All Cuda samples ran except some performance issues may be due to 32 bit rootfs.
[Shield Android TV General] CableBurner:
Same for me, i just switched to 22r18, because i wanted a original git source to feel better ;)

22r18 works as good as cm12.1, maybe monitor stability (detection) has improved. USB performance is awesome, tested two usb cameras simultaneously which deliver uncompressed video stream. One of them overloaded my i5 Sandy Notebook's USB controller.

The only thing is when calling shutdown it does not power off the board. sudo poweroff -f works, but doesn't unmount the filesystems and stop services :D

Regards,

Udo
[Shield Android TV General] yahoo2016:
Do you need to replace stock dtb to use 22r18 kernel?

I'd like to keep stock dtb to run Android.
[Shield Android TV General] CableBurner:
Hi,

22r18 is the Kernel used in Shield 2.1 Software. I compiled the dtb and flashed it. If you are afraid maybe you can flash the ready compiled dtb from nv? :)

I think this is safe, as nvidia describes it without warning: http://nv-tegra.nvidia.com/gitweb/?...ob_plain;f=README_SHIELD;hb=rel-22r18-partner
[Shield Android TV General] yahoo2016:
Great work! Do you mind to post you configuration file? I have a question:

You mentioned "USB UART adapter connected on shield TV's USB port". As I understand, USB UART adapters are used to connect PC's USB port to serial console port of ARM CPUs, SATV does not have serial console port, do you mean you used USB/micro USB cable to connect PC to micro-USB port of SATV?
[Shield Android TV General] anchung.chen:
The USB-to-UART adapter has USB port on one end and DB9 com port on the other end. I use two USB-to-UART adapters and a null modem cable to connect shield-tv to PC.

I like to post my modified .config, but could not find the way to add attached file, and since I am new to this forum, I am not allow to post external link of google drive. Any suggestion ?
[Shield Android TV General] yahoo2016:
That's interesting, that means with PCs with serial port, only a USB/serial adapter is needed.

To post link, other members had adding spaces to link to post.
[Shield Android TV General] anchung.chen:
Here is my modified .config, https: //drive.google.com/file/d/0B21oxu5PY4SGTFpIeVRSN0tYU0k/view?usp=sharing

Here is the original one, https: //drive.google.com/file/d/0B21oxu5PY4SGRXZFWXpuVDlLZjg/view?usp=sharing

Please remove the space just after https:
[Shield Android TV General] yahoo2016:
This is very helpful.

I noticed you were able to use "CONFIG_CMDLINE" in kernel configuration file to set boot options such as:

"console=ttyUSB0,115200n8 earlyprintk=serial,ttyUSB0,115200n8".
[Shield Android TV General] anchung.chen:
I guess that we could apply the same method on u-boot, So debugging u-boot and kernel without internal UART of tegra soc is possible.
[Shield Android TV General] rxg846zebra:
Hi yahoo2016,

Have you tried mounting to USB? Apparently when I tried to mount to my SanDisk extreme 3.0 64 gb USB, the screen just freezes at "Booting recovery kernel ...". I know my kernel Image should be good because the same kernel image worked with miniSD. Could it be the problem of the USB drive?

Thanks!
[Shield Android TV General] yahoo2016:
I have not tried USB but I can try it late this afternoon.

Have you uncommented "mount("/dev/sda1", "/dest", "ext4", 0, NULL);", commented the other "mount" and verified the USB port you use is "/dev/sda1"?
[Shield Android TV General] rxg846zebra:
Hi,

Yes, I have modified the init.c file accordingly. Regarding to verifying the USB port, how should I come about doing it? When I booted off the miniSD, I see /dev/sda1 shows up when the USB is plugged in. Is that the way to do it?

Thanks.
[Shield Android TV General] yahoo2016:
I'd do the same to verify partition 1 of USB drive is "/dev/sda1".

Did you format the USB drive as ext4? Can you try a power USB HUB to make sure USB drive is ready when SATV is powered up?
[Galaxy Note 3 Q&A, Help & Troubleshooting] Shadowguardian:
Hi guys.

Today I tried to unroot my phone and put it like factory to do the lollipop upgrade but I can't do it.

I used Super SU to completely remove root and do a factory reset using the key combination mode.

The problem is that my phone status is custom and I can't flash the original ROM because my pc doesn't recognize the phone.

I tried other computer, other cable, all USB doors and installing the last usb drivers on both computers and nothing solve the problem. It charges but doesn't connect to the computer.

I probably will send the phone to warranty this weekend wich ends on 23rd this month.

Please help me!
[Galaxy Note 3 Q&A, Help & Troubleshooting] Rosli59564:
Try to install kies. If it can detect the phone then the drivers you installed earlier isn't working and your usb is fine.

Sent from my SM-N920C
[Galaxy Note 3 Q&A, Help & Troubleshooting] Shadowguardian:
I already have kies installed but the problem persists....
[G2 Q&A, Help & Troubleshooting] Beast-Warrior:
Hi, guys, it has been a while since I've had this ROM but I've just recently got an update for Blisspop v4.0.3 or something like that. It automatically installed it. Now I can't use the smart lock feature and I heavily rely on it. Also, Play Store isn't working. I have yet to see what else is not working. Any help would be great.

Thanks

Also just noticed I am not receiving any notifications. I have to go directly into the app to see I have received a message.
[E 2015 General] triggerlord:
PLEASE NOTE: THIS IS NOT MADE BY ME. I JUST FOUND IT IN THAT REPO THAT HAS A BUNCH OF SURNIA ROMS.

moto . shreps . fr / ? dir = Moto % 20 E % 2 0 2 0 1 5 % 20 LTE % 20 % 28 surnia % 29 / r o m / pac

USE AT YOUR OWN RISK! :P

This seems to be made by Shreps. So go thank him! :D
[E 2015 General] mateo121212:
i own an xt1526 and this rom seems to work well with gsm.i dont use cdma
[E 2015 General] debojyotidey:
RIL is working?
[E 2015 General] mateo121212:
I have gsm voice and text I don't have a data plan so I can't test any data. The picture from my sim menu is themed with layers, I took all the other screen shots before themeing. It works about the same as CAF for me.
[E 2015 General] atomomega:
I don't want to be a jerk but did you ask [MENTION=4493088]Shreps[/MENTION] if you could post this? If he hasn't posted it yet maybe it's because he didn't want to make it public just yet?

Again, it's just a friendly question, not trying to bash or anything.
[E 2015 General] Agusyc:
Why did you write the link like that?
[E 2015 General] dandrumheller:
He appears to only have one post, so I don't think he can post links yet.
[E 2015 General] sirhc:
How are you using GSM on the XT526? Are you using a domestic US carrier?
[E 2015 General] mateo121212:
its a us cellular xt1526 so its completely sim unlocked apparently. i have an at&t mvno sim and it works. l originally followed the guide for the verizon version to make it work
[E 2015 General] hydroman202:
I wonder if flashing the modem from the us cellular version would allow an unlock for the xt1526 sprint version? Just a thought. I might try it, seeing as how both devices are the same hardware, I think.
[E 2015 General] mateo121212:
let me know if you need me to do anything. i think sim unlock may be an nv item....but let me know if i can help. would love to help sprint users who cant use domestic carriers
[E 2015 General] hydroman202:
I think I actually may have found something posted for another device by samwhatthegreat concerning nv. According to this link:

http://xdaforums.com/moto-x/general/guide-success-sim-unlock-sprint-xt1056-t2825155

You could potentially remove the sim lock. The only problem is the particular values that are mentioned in the above link are read only. If there was a way to change that, sprint users would be in luck for an unlock. I'm not entirely sure its possible, but in the chance that it is, maybe it could work.
[E 2015 General] mateo121212:
would an nv dump from my us cellular sim unlocked xt1526 help? or anything that i could provide? on the nv item stuff they may be different values for our device. check out this http://xdaforums.com/showthread.php?t=2166542 its the same kind of idea as your link
[E 2015 General] LenAsh:
There are numerous threads by Shreps already in the Original Android Dev Forum for this device, so this is largely irrlevant.

Thread closed.
[T-Mobile Samsung Galaxy S 4] Mr.LinK:
Hello I flashed my t-mobile SGH-M919 with this ROM( http://xdaforums.com/showthread.php?t=2539361 ) and noticed that it changed the model number from SGH-M919 to GT-I9505G. I didn't mind it and I was very satisfied with the ROM's performance. However, recently my phone would randomly restart and I seem to have stopped receiving messages and phone calls but I can send them. I checked my APN and it was set correctly. Does anybody know what's causing these problems and how I could fix them?

Also, is there a way to go back to a complete SGH-M919 stock version from GT-I9505G?

Any help would be greatly appreciated.
[T-Mobile Samsung Galaxy S 4] lordodin912:
[MENTION=6967331]Mr.LinK[/MENTION] Try a different kernel if you don't want to switch os, GPE kernel: http://xdaforums.com/galaxy-s4/i9505-develop/kernel-hulk-kernel-v1-stweaks-based-t3050469

To return to stock, download stock firmware and flash via Odin. (you could flash stock, debloat, set it up how you like, then back it up via recovery so you can always return to it if you need to, without odin)
[T-Mobile Samsung Galaxy S 4] Mr.LinK:
Will it work if I flash an SGH-M919 variant stock firmware from my current GT-I9505G? I just want to go back to the factory setting with the SGH-M919 variant and go from there.
[T-Mobile Samsung Galaxy S 4] lordodin912:
You can change model name to anything ha (use buildprop editor). Don't worry about it. As long as you have a m919 then yes you can flash the stock firmware.
[ZenFone 2 Q&A, Help & Troubleshooting] NeWcS:
So anytime I install a CM based rom I can no longer send or recv MMS. I have ran bliss pop, res.remix. cm 12.1 plain and 13 plain. None of which will allow for MMS. Even installing a 3rd party sms app and manually inserting APN values does nothing. All apn's are correct in system settings.

But as soon as I go back to stock, or a modded/slim version of stock, everything works just fine.

Is there an issue w/ CM and MMS? And if so id there a fix?

thx!
[ZenFone 2 Q&A, Help & Troubleshooting] Christopher876:
Delete all of the default APNs available and then create a new APN with your APN settings, It should work fine because from my experience any other similar APN settings to the one that you create interferes with your custom made one.
[ZenFone 2 Q&A, Help & Troubleshooting] NeWcS:
Already did that. Manually added along side default APNs. Added APN alone. Restored default APNs. Nothing.
[ZenFone 2 Q&A, Help & Troubleshooting] Christopher876:
I have no clue then, this was the only method I did to get my APNs working.

You could try every custom rom until there is one that gets the APNs working
[ZenFone 2 Q&A, Help & Troubleshooting] bmwkeith:
I am on Cricket Wireless and ran into the same issues, even after entering the correct apns and deleting the other ones. This occured on every rom except stock based roms. I have solved the MMS issue by toggling airplane mode on and off every time that I restart the phone, and that pretty much fixes the issue.
[ZenFone 2 Q&A, Help & Troubleshooting] NeWcS:
I too am on Cricket.

I am now running Super Zen which works great. Just wondering why this seems to be a CM issue that hasn't been addressed. I guess not enough people are having the issue. Which in the end could be a Cricket/AIO issue, who knows.

Thanks for the reply. cheers
[ZenFone 2 Q&A, Help & Troubleshooting] raynan:
I have the same issue on ATT. I haven't tried the suggested fix above, but will and see what happens.

Update: neither fix listed here works for me.
[ZenFone 2 Q&A, Help & Troubleshooting] bmwkeith:
It is a CM issue, but the airplane toggle always seems to fix it
[ZenFone 2 Q&A, Help & Troubleshooting] NeWcS:
So, you just let your phone fully boot, turn airplane mode 'on' for a few seconds than turn it back off. And its all good until the phone is re-booted? Thx
[ZenFone 2 Q&A, Help & Troubleshooting] bmwkeith:
Yes
[ZenFone 2 Q&A, Help & Troubleshooting] NeWcS:
Thanks for the update. Wonder why some people have issues and others don't. Seeing how there are so many CM based roms for this phone, I guess it's only effecting a small amount of us.
[ZenFone 2 Q&A, Help & Troubleshooting] raynan:
Who knows... I've tried every CM based ROM for the Z00A and all of them give me this issue. Good thing I don't use it much.
[ZenFone 2 Q&A, Help & Troubleshooting] joe460:
I'm running BlissPop on my Z00A in Australia with two SIM cards as a daily driver. Vodafone (SIM1) for personal and Telstra (SIM2) for work.

Firstly I'm pretty pissed I can't do MMS on SIM2. I thought I could at least do it slowly over 2G. Now I find I can't at all. My priority however, is to get MMS working on SIM1 since most people can email me at work instead.

Toggling airplane mode doesn't work for me either. In addition SIM2 doesn't reconnect until I manually search "Network operators" or reboot.

Unless the MMS on CM issue gets fixed soon I'll be heading to a stock/slim ROM.
[ZenFone 2 Q&A, Help & Troubleshooting] NeWcS:
Wonder why this has gone on for as long as it has. 12.1 has been out for a long enough time that it should have effected the masses. Unless enough people don't care about MMS.
[ZenFone 2 Q&A, Help & Troubleshooting] NeWcS:
Has anyone tried a cm13 rom and does the problem still exist?
[ZenFone 2 Q&A, Help & Troubleshooting] raynan:
Yes. I gave up and did a clean flash, and now the aeroplane mode "fix" works for me. Not sure what i did, but my setup now is exactly the same. Restored everything from TiBu.
[ZenFone 2 Q&A, Help & Troubleshooting] NeWcS:
Hmmmmmmmmmm, strange
[ZenFone 2 Q&A, Help & Troubleshooting] NeWcS:
Im going to to try a couple 13 roms and see if any will work. Ill report back
[Xperia Z1 Q&A, Help & Troubleshooting] shefys:
Hi folks,

I've upgraded/replaced the original TMobile firmware (14.5.B.0.247) on my Xperia Z1s (c6916) by c6906 Customized US (14.6.A.0.368). Everything works fine except few things like:

1) screen rotation - when i try to rotate the screen into the landscape mode - it turn the screen in opposite direction/backwards. Looks like the sensor readings get reversed? It was working fine before the upgrade, hence it looks like a software issue. Any ideas how to fix it?

2) device memory is twice less but it is kind of expected because original Z1 has only 16 Gb of storage onboard. Is there any way to fix that?

Thanks.
[Xperia Z1 Q&A, Help & Troubleshooting] shefys:
ok, here is a "solution":

The C6906 "/etc/sensor_def_qcomdev.conf" must be replaced by C6916 version. The same applies to CyanogenMod 12.1. C6916 have different settings for few things.

I downloaded TMO firmware, extracted system.sin and replaced the file on my phone running CyanogenMod 12.1 - after reboot rotation works perfectly but it will get broken as soon as i upgrade the firmware :(
[Xperia Z1 Q&A, Help & Troubleshooting] Helgaiden:
how did nobody catch that this dude managed to flash a different firmware on a phone that is supposedly NOT unlockable? Shefys, you need to explain exactly what you did. In another thread you said you unlocked your Z1s c6916 on developer.sony.com and i tried it, but there was no Z1s option. Followed the steps anyways by selecting Xperia Z1 but the unlock command failed citing not allowed.
[Xperia Z1 Q&A, Help & Troubleshooting] Ksix007:
How you did this? I hard bricked my Xperia Z1S putting the 5.1.1 fimware, I needed to buy a new board because I had no solution.