yashsingh1/xdaforums huggingface dataset:
[LG G2 Mini] yohaim:
Yes,you've lost warranty.

Every bloody page on the net says,that root and custom roms cancel your warranty.

Better have thought before messing up.

I'm a phone tech,but before I was qualified for that,I used to read many pages over XDA and the Israeli site for Android phones.

There's a saying here,you better shave on some else's beard.

So,no offence,but now you're shaved,but butt naked.......

Try the help of the guys here.

Just for your knowledge:

You DO NOT study how to root and jailbreak phones on your phone tech studies,because on 90% of the cases,you do not need to do so.

We are past the days of Cydia,black market and custom features that require root.

I basically raped my Galaxy S2 with root and rom changes,never bricked it,but got normal results only when working with the official Stock Rom.

On my G2 mini,I don't even bother to root,and have flashed a stock rom manually through LG Flash Tool 2014.

Even if the flash went wrong,I could have tried flashing another rom,or send it for maintenance,because it was an official flash,and could have claimed it happened with PC Suite,which happnes to do so on many occasions .

I think I've made my point.

Happy post digging,my frined.

Peace! :)
[Galaxy Note 3 Q&A, Help & Troubleshooting] shanedefreitas:
need a efs folder rebuilt who does it plzzzzz help
[P3300, MDA Compact III General] Maty555:
Hello, I have big problem. I have HTC Artemis from T-mobile. How entry in the bootloader?

Thank you
[P3300, MDA Compact III General] pvdhelm:
hold the record button (left of your artemis) and with the stylus press the reset button. Hold down th erecord button and you are in the bootloader.

What do you want to do in the bootloader?
[P3300, MDA Compact III General] michielc:
offtopic: pvdhelm location Schijndel

wat is de wereld toch klein :)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] andy_from_ireland:
I had CM 10.1 for N7000 Galaxy Note for a few months - was getting on with it grand, lot faster in operation than original touchwiz samsung ROM - bluetooth was working fine , until I got meself one of these cheap bluetooth smartwatches off ebay. when I was making the voice call through the watch people could hear my voice but i could not hear people through the watch (which , I know its a gimmick, but that is what your supposed to be able to do) - so theres me blaming the watch thinking ah well its a cheap china watch and its not working properly - but then I installed samsung stock back onto my N7000 and now the watch works perfectly on handsfree people can hear me and I can hear others through the watch - so what is broken in CM10.1 bluetooth - I dont really want to go to CM11 or 12 and there was something going around abot CM10.2 ROM but I cannot find that ROM and if I did find it would the bluetooth issue be fixed in that update? Thanks.
[OS Porting] shankhy:
I want to port galaxy note 4 cm12 lollipop rom for galaxy alpha :eek: :eek: Is it worth trying??? Considering its my first port :silly:
[Ascend Mate 7 Q&A, Help & Troubleshooting] sachinwadhwa46:
Are there more than one version of MT7-TL10 model?

I have seen a few software updates of this model. But I dont receive any ota updates. And manually , it also fails by dload option?

Any info please
[Ascend Mate 7 Q&A, Help & Troubleshooting] Fooox1:
Yes, are two versions, Chinese and International. Hardware equal, software differently.
[Ascend Mate 7 Q&A, Help & Troubleshooting] sachinwadhwa46:
Thanks for the info. So this international version receive the slowest update of all. And idea when this variant will receive the lollipop update?
[Ascend Mate 7 Q&A, Help & Troubleshooting] Fooox1:
International a beta (5.1) has already received. Chinese not.

http://www.android-hilfe.de/thema/l...c900b308-european-modell.697942/#post-9000391
[Ascend Mate 7 Q&A, Help & Troubleshooting] sachinwadhwa46:
Ok. Thanks for the link. Now I understood. For eg. In my phone the current firmware is MT7-TL10V100R001C00B120SP04 and the firmware i tried installing was MT7-TL10-V100R001CHNC00B127. The difference is in the name itself . Chinese version has CHN extra in its firmware name. Right sir? :)
[Ascend Mate 7 Q&A, Help & Troubleshooting] Fooox1:
True, CHN must not be in it, then it is for Asia. Because you realize whether or Internaional Asia. If before the B look like this: MT7-TL10V100R001C00
[Ascend Mate 7 Q&A, Help & Troubleshooting] sachinwadhwa46:
As you have instructed somewhere that for installing lollipop beta phone should be running B125 update.

I downloaded MT7-TL10V100R001C00B125SP02.zip but dload option failed saying there is no update.app . software update failed.

I am currently on MT7-TL10V100R001C00B120SP04 update.

What to do ?
[Ascend Mate 7 Q&A, Help & Troubleshooting] Fooox1:
Only works with the B125.
[Ascend Mate 7 Q&A, Help & Troubleshooting] sachinwadhwa46:
yes but i am not able to update to b125 firmware. It is failing by dload method
[Ascend Mate 7 Q&A, Help & Troubleshooting] Fooox1:
Just make sure everything again, bug is mostly in detail.
[Ascend Mate 7 Q&A, Help & Troubleshooting] SawMin:
I'm also on B120SP04

bro i'm also on B120SP04 and i don't know which firmware to update :( to get lollipop ... i once tried updating B125 but failed like you bro .... if any solution found ... plz let me know ...
[Ascend Mate 7 Q&A, Help & Troubleshooting] sachinwadhwa46:
http://xdaforums.com/mate-7/help/guide-how-to-update-mate-7-getting-t3172687

Refer to this guide by me
[Ascend Mate 7 Q&A, Help & Troubleshooting] koegs:
So i have two Huawei MT7-TL10 here. How can i find out which version it is?

First one has Firmware C00B120SP04 and second one has C00B128.

Which one is a international or european or chinese version? And what about the LTE bands?
[Ascend Mate 7 Q&A, Help & Troubleshooting] SawMin:
Thanks

Thanks bro .. :laugh:
[Nook Touch General] pinguy1982:
Flash the zip in CWM to enable USB Audio.

It works its just a bit tricky to get enabled. You may have to reboot the device to get it working.

Also if you have under 50% battery life the USB sound dongle will cut out. So make sure you have plenty of battery life.

MX Player works better playing videos then QQPlayer, but the sound with MKV files cuts out. On the QQPlayer the sound works fine.

The version of MX Player I tested was 1.7.40 for Froyo/Eclair.

Mediaserver doesn't work on the NST so any MP3s you add won't show up in Music players. To get around this use ES File Explorer built in music player to play local MP3s.

[YOUTUBE]watch?v=VmJEUXFyqOQ[/YOUTUBE]
[Nook Touch General] NOOK!E:
What's going on under the hood here?

I'd like to get USB audio working on my system without using someone else's kernel, so if you could tell me what to change in mine, I'd thank you.

What other files, apps and such are necessary (so that I can add them by hand instead of flashing)?
[Nook Touch General] pinguy1982:
Just unzip the package and have a look. The only thing that may not be obvious is you need to remove /system/lib/hw/alsa.zoom2.so

Apart from that you can see the files and apps that get added just by looking inside the zip.

The main files needed are:

/system/lib/hw/alsa.default.so

/system/etc/asound.conf

/system/app/UsbMode.apk this is the app that enables host mode. Needs SU to be able to run.

Plus the kernel.
[Nook Touch General] NOOK!E:
Yes, thanks, I did that already.

I guess what I'm really asking is this: what do I need to add to my uImage and/or uRamdisk to allow USB audio? I'd prefer to just modify my kernel instead of overwrite it with a whole different one.
[Nook Touch General] pinguy1982:
Not sure where to get the audio sources for the kernel from. I just grabbed this: http://xdaforums.com/showpost.php?p=43212551&postcount=164

It has everything I need.

FastScreen

MultiTouch

UsbHost

UsbToCom

UsbSound
[Nook Touch General] NOOK!E:
[MENTION=4636254]pinguy1982[/MENTION], here's the kernel I'm using: http://xdaforums.com/nook-touch/general/nook-glow-multitouch-usbhost-files-t2846867/post54803848

The specific uRamdisk I have I also modded to mount /boot as read-write during the boot sequence, in case that matters.

The ideal thing for me to do would just be to add UsbSound to that kernel, if I can, and then release it for the Nook Touch Glow. I don't think I've seen an NTG UsbSound kernel yet, so that should be useful.

[MENTION=4474482]Renate NST[/MENTION], can you help?
[Nook Touch General] pinguy1982:
Just tested it with the your uRamdisk. It works fine. Haven't tested this with the Nook Touch Glow yet. So unsure if it works with it or not.
[Nook Touch General] pinguy1982:
[MENTION=5981373]ИΘΘK¡€[/MENTION] Here you go: http://xdaforums.com/showpost.php?p=43860186&postcount=175

All the info is posted there.
[Nook Touch General] pinguy1982:
Some apps didn't work with the sound so I have updated the USB-Sound package with a new sound engine.
[Nook Touch General] NOOK!E:
Would you give me a quick run-down of the hardware required for USB sound and how to use it?
[Nook Touch General] pinguy1982:
Sure.

Hardware you need:

USB OTG cable. I have one of these so I can charge the device while I am using it.

USB Headset or a USB Audio Adapter (I own both and can confirm they work with the Nook).

Thats it.
[Nook Touch General] NOOK!E:
Sweet, thanks! Now, all I need is to either find or make a Nook Touch Glow 1.2.1 kernel that has UsbSound included.

Can you help me with that?
[Nook Touch General] pinguy1982:
[MENTION=5128640]latuk[/MENTION] is going to be the best person to speak to about that. But its gotta be easier getting his Kernel working with the Glow light then trying to build a kernel from scratch. His kernel has everything enabled already.
[Nook Touch General] NOOK!E:
Sounds like a good idea in theory, but [MENTION=5128640]latuk[/MENTION] has not been online at XDA in over a year. How would I get ahold of him?
[Nook Touch General] NOOK!E:
[MENTION=4636254]pinguy1982[/MENTION], okay, so I just tried the kernel from your .zip (just the uImage, not uRamdisk), and it appears to not have hosed by GlowLight after all! One thing I do ask, though - is this a 1.1.5 kernel? It appears to have removed proper functionality for NoRefresh, and since I have the 1.2.x test version, I thought perhaps the kernel downgraded me.
[Nook Touch General] pinguy1982:
Its based on 1.2.1
[Nook Touch General] NOOK!E:
Ah, I figured it out. It's FastScreen's fault.

I'm running the kernel as we speak, wih FastMode2 installed. I like it, but there don't seem to be any contrast settings. Got any tips?
[Nook Touch General] pinguy1982:
FastMode2 doesn't have any contrast settings, but it shouldn't need it. The biggest issue with fastmode is with ghosting, but contrast wise it is far better then NoRefresh.
[Nook Touch General] NOOK!E:
Yeah, I've been noticing both items. Thankfully, ghosting hasn't been too terrible, but the contrast is, as you said, much better than NoRefresh.

Thanks for all your help - once I get my Sabrent External Sound Box USB-SBCV off Amazon (recommended by Renate, I believe), I should be in business for audio playback (and audio recording? is that also in this kernel?).
[Nook Touch General] pinguy1982:
Doubt it. I think the feature is kinda pointless on the NST. But if you want to enable audio recording the details are here: http://xdaforums.com/showpost.php?p=43281985&postcount=374

But audio recording may work as is. I haven't tested it but as it has a new sound engine it might work (I ported part of it from the the NOOK Color v1.1.0)

I haven't modified the framework.jar though and I am pretty sure its not going to work until AudioRecord.smali has been modified.

By the way updated the USB-Audio package. It sounds really good now.
[Nook Touch General] :
Thanks for the link. If you don't have time to mod framework.jar for AudioRecord.smali support, I can do that for you, if you want.
[Nook Touch General] Renate:
The biggest problem with all this USB host stuff is that the power is being delivered by a tiny charge pump and not a real DC converter.

A lot of things that you might want to plug in might take 50 or 100 mA.

Even if it works, it may be flakey.

My suggestion is that you can use keyboards unpowered.

About anything else you would be better off using a powered (or a back-powering) hub.

I have recorded with a cheesy USB adaptor and with a Lexicon Alpha microphone interface.

I have not found the performance of the Nook to be entirely reliable for long, high quality recordings.

I think for serious recording you'd be better off with something besides a Nook.
[Nook Touch General] :
[MENTION=4636254]pinguy1982[/MENTION], attached is the 1.2.1 framework.jar with the patched \smali\android\media\AudioRecord.smali. It also includes [MENTION=2938405]antsm[/MENTION]'s power menu mod.

Enjoy!
[Nook Touch General] pinguy1982:
Doesn't work. It stops the ROM from booting.
[Nook Touch General] :
Are you 100% sure? What type of bootloop/hang are you getting?

How did you replace the file?
[Nook Touch General] pinguy1982:
Done some more work on the sound engine. The updated package is on the first post.
[Nook Touch General] pinguy1982:
Honestly I think recording is pointless on the Nook. I own many Android devices and the only time I use the Mic is with Google Now. On the Nook I really can't think of a single usefully reason for audio recording. On the other hand I can see a use for audio. It is nice being able to listen to the audio books while I read (or just have music/radio running in the background). Granted as you have said the power-output is pretty poor but I have found it good enough to get a couple of hours of listing out of it. It is when it gets around 40-45% battery life I start having issues with the USB Audio Dongle.

I will admit the sound quality was pretty bad on the Nook. Lots of crackling. But for the most part I have fixed this. It does start becoming an issue when you get around the 50% battery life. But any thing over that the sound quality is great.
[Nook Touch General] nmyshkin:
So...if I flash this new kernal, etc., does that overwrite the current framework-res.apk and/or settings.db files?
[Nook Touch General] :
No, the .zip will only overwrite/add the files included, which can be found by downloading and unzipping the .zip.
[Nook Touch General] :
My Sabrent External Sound Box just arrived in the mail. mp3 audio and video with sound (via MX Player) are working like a charm! Big thanks to all who have contributed to the USB Audio project! :D
[Nook Touch General] nmyshkin:
My OTG cable arrived to day. Sound device should follow in a few days, so I guess I have to get serious about this :o

Just one last check: the NookManager backup is TOTAL, right? Like a clone? So if all heck breaks loose I can just go crawling back to business as usual?
[Nook Touch General] :
That's correct. Happened to me several times when I was stabilizing my AndroNook Settings project. :eek:
[Nook Touch General] nmyshkin:
something's not right...

mmm...I seem to have installed the zip file. Took a loooooong time for the marching dots on the boot screen to finally reach their destination but eventually I am back.

Can't seem to get this thing to do anything. I don't have a usb keyboard but I do have a mouse and (of course) many flash drives. So this is what I am doing:

1. Hit "off" to prevent the Nook to try to charge itself from the current it is supplying to the USB.

2. Plug in just the USB OTG adapter

3. Hit "host". Did the LED at the bottom turn green? Hit "host" again.

4. Plug device into USB OTG adapter

Nothing happens (other than the green light thing). When I look at "View USB" I see the same thing (MUSB HDRC host driver) that I see when I just open the usb utility without doing anything else. Doesn't matter what I attach. Am now searching for more info about the various options on the app.

But...I'm a little concerned about my CWM card. That last time I used it was to flash kernal 166. It had stuff on it, I just copied the zip file on and installed it. But the root directory of the card already has a uImage and uRamdisk file. Is that a problem? (seems unlikely because otherwise the NST probably would not run at all)

Edit: found a usb keypad. Still no joy. Everything else seems to work fine. Governor shows 1.0 GHz max, though. Isn't this kernal 1.1 GHz?
[Nook Touch General] Renate:
In UsbMode.apk, look at "State" at the top.

b_peripheral - you're not in host mode

a_wait_vrise - you're in host mode, but the VBUS has not risen, you still have the charging circuit enabled or too big a drain

a_host - you're in host mode and ready to go

If you are having trouble, at least start out using a hub powered by a wall adapter.

There's a new UsbMode-2.1.apk in the signature. There are no changes that will affect what you are doing. The changes have more to do with using it on Android versions to Lollipop. Although the mode controls are disabled on non-Nooks (and not needed), the diagnostic abilities are useful on my Nexus 9.
[Nook Touch General] nmyshkin:
Thanks for your help, Renate!

Here's the data from my "experiment" (battery charge at 93%):

WITHOUT powered hub

1. Plug in OTG: STATE: b_idle

2. Host: STATE: a_wait_rise (green LED steady)

3. Plug in numeric keypad: STATE: a_wait_rise

4. un-plug and replug keypad: STATE: a_host

View USB shows no driver other than MUSB host; keypad seems to have no effect on anything

WITH powered hub

1. Plug in OTG: STATE: b_idle

2. Host: STATE: a_wait_rise (green LED steady)

3. Plug in powered hub with keypad attached: STATE: a_host/a_wait_bcon switching back and forth now and then; even saw a b_idle once!

View USB shows no driver other than MUSB host; keypad seems to have no effect on anything

I repeated the experiment with a simple USB mouse. Same results.

That's what it's been doing since I flashed the new kernal, etc. I even flashed it again with no improvement. Sometimes the USB utility app causes (or is involved in) weird screen effects when I close it and go somewhere else while it is in host mode (but not working right, obviously).

SIGH.

Maybe when the audio thingy arrives it will work just fine. I'm not really interested in other USB peripherals anyway, but the behavior does not seem to bode well so far.
[Nook Touch General] Renate:
Well, that's all weird.

The first example you cited is the least abnormal.

Can you run a dmesg on ADB and see what the kernel is saying about these USB attachments?

You're saying that you have never seen any nodes on View USB besides the controller and the lone empty [1] below it?

Admittedly the whole hardware and driver on the Nook are a bit wonky.

I just tried to get a keyboard working directly on my Nook and it took a few tries.

I pretty much always use a back-powering hub.

As far as ease of use and reliability goes:

Back-powering hub

Normal powered hub

Single keyboard

Audio adapter or flash drive

For keyboards the simplest clear check is to hit the Caps Lock, Scroll Lock or Num Lock and see if the LEDs goes on and off.
[Nook Touch General] nmyshkin:
Yes, I never see anything on View USB besides the controller and that lonely [1] below it :( Now, admittedly, I only have two devices I can try: a simple mouse with scroll wheel (never elicits any response and the dmesg says over and over that maybe the USB cable is bad) and a numeric keypad (alas, no LEDs).

I surprised myself by actually obtaining the dmesg you mentioned for the keypad attached, sans powered hub, with STATE showing a_host. It is attached. Lots of hand-wringing about the USB stuff there, but interpreting it is beyond the ken of my little grey cells....
[Nook Touch General] Renate:
Ah, our old friend error -110, connection timed out.

It's clearly thrashing.

Are you sure that the current limit says "Off" in UsbMode.apk?

Are you sure that your USB OTG adapter is good?

Can you try with another keyboard?

Can you try with a hub?

Are you sure that you have the USB driver with the original fix?
[Nook Touch General] nmyshkin:
Definitely

Well, as sure as I can be. I just got it, but I suppose it could be faulty.

Alas, no. Rare as hens teeth they are around here. That's why I had to resort to the keypad. It's the closest thing I've got.

Will do, but that previously gave the weird result with the flipping back and forth from a_host to a_wait_bcon. Still, more data if I try.

Well, I downloaded the zip file at the beginning of this thread and used it. Now I did repeat the install just in case there was a hiccup, but I did not download a fresh copy of the zip. Seems like a corrupt copy would wreak all kinds of havoc, but that's just my inexperience talking.

I'll report back on the hub.

Edit: So the hub experiment went pretty much as expected (same keypad device). STATE fluctuated from a_host to a_idle to a_wait_bcon etc. dmesg is attached. I unearthed an ancient (working) Microsoft USB optical mouse. Even when plugged into the powered hub there is no activation of the internal LED and although STATE says a_host, there is no evidence on the View USB page that anything is connected.

I'm sure I should have checked this before, but I hope this current package is for FW 1.21. Surely the entire device would be non-functional now if it were not?
[Nook Touch General] nmyshkin:
Sound gizmo arrived today. Without a powered hub I got nothing, some crackling in earphones and "air" noise, but beep failed, etc. Then I tried the powered hub several times. ONCE I got an actual response with something listed and recognized in View USB (yay!). Beep passed and I was suitably deafened by the Akimbo audiobook app, MX player, the NPR News app (surprise!) and even (more surprising) a stream of NPR via Opera Mobile from knau.org. I tried Pandora but then all hell broke loose and the Nook froze.

After much holding of the power button I finally forced a reboot and everything seems to be OK, but I never again got the USB audio device to work, with or without the hub.

The good news is that none of these thingies cost much (and free shipping on all). The bad news is that this doesn't seem to be at all practical, at least not on my particular device. Don't know why. Wish it weren't so :crying:
[Nook Touch General] nmyshkin:
so here's what I've learned

My OTG cable sucks big time :mad:

After some half-hearted fooling around with the set-up I began to notice just how loose the connection was between the USB plugs and the socket on the OTG. Added to that, the socket seems really shallow so that plugs only go in about half way, not at all like on the socket of an extension cable or a computer. That means any wiggle is magnified in effect.

A few minutes with a jeweler's screwdriver and voila! It's still a dicey connection, but better. If left undisturbed all kinds of devices (keypad, hand-held wireless keyboard/mouse pad I use with Kodi, audio gizmo (!), etc.) are recognized and function--even simultaneously.

BUT.

Only with a powered hub.

This is a non-starter for me. If I am going to use the audio at all it has to be literally

OTG

. I thought I was being clever by carefully going through audio devices and finding one with no LEDs. But perhaps the one I ended up with is a current hog anyway.

Can someone recommend an audio device that works well

without

a powered hub?

I've ordered another OTG cable but now I think I need to do some more careful looking. Of course it's possible I just got a bad one but I don't expect that these cables that can be had for a song on ebay are exactly precision devices. Anyone using one that has a nice deep socket that grabs well?

One more question: who needs speakers? Seriously, the volume is either off or blasting. I thought I read somewhere that accessing the android volume controls before running any audio apps would ensure that you could adjust the volume. That actually worked the very first time I got the audio device working, then never again. Any hints on the volume issue? (my current audio gizmo does not have any controls, but I guess that doesn't matter if I'm going to get a different one).