yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Accessories] BruceCLin:
Thank you for understanding. Each one actually take me 3-4 nights from start to finish, and each one is made to order. After the material cost, I make less than minimum wage per hour on these. I do them because they are the product of love. If I have to make hundreds of them, I will probably find help in mass produce them and adjust the price accordingly.
[Nexus 5 Accessories] BruceCLin:
Taking an existing charger and putting it in the wood would make it too far from the phone and will not charge well. I follow kidgenius' thread and came to a very similar way with the magnets, coil, and circuit board. This is actually a lot of prototyping and test to get this distance correct. Without the magnets it will be a lot simpler.

Originally I designed to have dovetails like how you would usually to a wood joint. But in order to have a more seamless look to it, I've changed it into them to have multiple faces at different angle as the contact for force distribution at multiple axises. On top of that, There are holes drilled through the back top piece that line up with holes on the bottom piece. Then I bolt them together right after applying adhesive at those previously mentioned faces, so the bolt action act as a self clamp for the 2 parts. I'd say they are quite strong. I have a tendency to over engineer.
[Nexus 5 Accessories] Boomslang_x64:
Is the charger tolerant of phone cases? That is, will the magnets still hold and is the charge rate acceptable?
[Nexus 5 Accessories] BruceCLin:
I can't say it is. I did a lot of testing with different cases. In the end it's just no consistently enough to claim as such.
[Nexus 5 Accessories] gvoima:
It's always good to over engineer a little bit ;)

What about trickle charging, does the board support it? And how fast is it charging from empty to full? Most QI's does it in about 2,5 hours.
[Nexus 5 Accessories] BruceCLin:
I am pretty sure all modern Li-Ion batteries in smart phone do not want trickle charge. If you mean by if when it's full, will it stop, the answer is yes. It work just like the ones from google. At least for N4 and N5, the charging is controlled by the phone itself and not the charger. As far as the speed of charging goes, that's a very good question that I have not fully tested on. I will have to try to see what the difference between using a wall charger and a usb port. An initial guess is that It will be about the same behavior like the google ones, which is slower on a usb port.
[Nexus 5 Accessories] rubin110:
Would you be willing to build one with a small shelf/lip on the bottom to hold up devices that don't have the metal discs in? Specifically a Note 2? I would be happy to draw up where the wireless charger sits on the back of the device and mail it over.
[Nexus 5 Accessories] BruceCLin:
Sounds pretty doable. I can probably design one to work with it if you can provide the correct measurements. Email me a drawing and I can check first if the coil location can work with note 2. Also, any preference what the ledge you want to look like, or it's up to me to design something look nice?
[Nexus 5 Accessories] rubin110:
Drop me an email an we'll talk. :) http://rubin.starset.net/id
[Nexus 5 Accessories] rollerdyke44:
this looks awesome!

how is the fone attached to the stand btw??
[Nexus 5 Accessories] BruceCLin:
Thank you. It's sort of like miter with rabbet joint with 2 countersunk screws for extra strength.
[Nexus 5 Accessories] bojtimoric:
That's amazing! Isn't the magnet damage the phone or the SD card?
[Nexus 5 Accessories] BruceCLin:
Magnet should not damage phone or SD card unless the magnet is so strong it physically warp any iron parts inside the phone.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] _Damian:
Hi

I wan't to install miui rom but i wasn't lost my warranty

If do i a saferoot and modify recover with root explorer or something without odin, and flash miui, the flag goes to 0x1?

Are there any way to flash rom withouth lost warranty?

Sorry for my poor english and thanks!
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Aronuser:
if you flash any custom recovery it'll knox it up, also on any custom kernel

probably when you'd flash a aosp rom without a custom kernel it can work (but most likely the system will crash)

Probably if there are any touch-wiz based roms with odin, and without a custom kernel (or with removing it from the tar) you could stay safe

but after all i'm not liable if you knox your device up

i've knoxed it up by the way ;) running cm11 with custom kernel from F4K and get up to 21333 in antutu :highfive:
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] _Damian:
Wooow, antutu is very hight! Awesome performance

Question: knox put up in any kernel mod? If it's thats right i prefer lost my warranty :(
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Aronuser:
any custom kernel will knox it up as far as i know, but this maybe doesn't go for build prop tweaks
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] _Damian:
Thanks! Last question: Can i restore stock firm? How? I have the 4.3 Movistar Argentina rom and i wan't to install MIUI
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Aronuser:
You can download stock firmware from www.sammobile.com

enter download mode

put the file into PDA or AP in odin

press start

wait until the phone restarted

then you have stock again!

/edit:

you'll probably need to enter the recovery after flashing it and do a "factory reset"
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] _Damian:
soo much thanks! And i don't have any problem? the firmware works good like now? and knox works?

EDIT: Another question: Can i use samsung software in another rom? like s voice
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] fburgos:
1, It's preferable to flash the same original firmware version.

2. Most Samsung apps won't work, watchon works
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] _Damian:
Thanks, my samsung is now rooted :)

Soo much thanks!
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Aronuser:
Congrats! :highfive:
[Moto G Q&A, Help & Troubleshooting] Roshi69:
I've been flashing ROMs, recoveries etc for years on every android device I've had, from Samsung to nexus, HTC. Everything. This is my first Motorola and I'm having a lot of problems.

Unlocked the boot loader, flashed TWRP but wouldn't backup my stock ROM so put on Pholz recovery and it wouldn't backup either.

Tried to install C-Rom after the usual wipes and just sticks at boot screen. Tried Tweakone ROM I think its called and same problem.

Any ideas? I have the XT1032

I know about restoring to factory but what I'm asking is, is there anything specific I'm doing wrong? I'm quite an experienced flasher. Research is showing me how to recover the phone but what's gonna stop it happening again
[Moto G Q&A, Help & Troubleshooting] ATRIXXIRTA:
A lot of users report issues not being able to flash rom's on 4.4.2 kitkat.

A fix is to downgrade to 4.3, then flash roms.

I dont know why. I bought my device upgraded to 4.4.2 already, and i can flash roms with no issues.

Search the forum for the topic and you will find the info you need.
[Moto G Q&A, Help & Troubleshooting] deej_roamer:
It wont backup saying what error?
[Moto G Q&A, Help & Troubleshooting] Roshi69:
Twrp just said 'failed' in red writing after the data backup I think. And philz touch said something along the lines of Not being able to write a file into the \clockworkmod folder.

I bought the device with 4.4.2 on it and followed the guides after reading up about the problems etc but TWRP 2.7.0.0 had a lot of reports that everything was working on it so went ahead with it
[Moto G Q&A, Help & Troubleshooting] ATRIXXIRTA:
Ya that's strange because philz works great for me. Do you have a USB otg to try an external backup?
[Moto G Q&A, Help & Troubleshooting] Roshi69:
I got the phone booted again by following a guide and flashing a stock rom.

Installed Philz recovery again and still getting the backup error. it says: E: Error while backing up boot image!

So understandably i am now scared to flash another rom in case i get a boot loop again.

*update* Strangely i flashed TWRP via CWM, rebooted into TWRP 2.7.0.0 and performed a backup successfully.
[Moto G Q&A, Help & Troubleshooting] srujan21:
Why dont you use Clockwork mod recovery for flashing Rom. I have flashed 10 Roms with that and all are backed up with out any problems. TWRP has no official support for moto g, and instead of all that why don't you try Cyanogenmod ?
[Moto G Q&A, Help & Troubleshooting] TheSkweed:
(sorry if my english is not perfect)

Hello,

I have exactly the same problem with my XT1032.

Bootloader unlocked, CWM (6.0.4.7) successfully installed and backup done with no issues.

But custom roms won't load...

CM11 is stuck at "bootloader unlocked warning screen" and SlimKat is stuck at slimkat logo.

I never had such problems on my Nexus..

Please help me, I don't know what's going on :(
[Moto G Q&A, Help & Troubleshooting] Ghoorg:
Same here. It may be possible to downgrade to 4.3 (see here), but would it then be possible to flash a 4.4.2-based custom ROM ? I'm not sure.
[Moto G Q&A, Help & Troubleshooting] Roshi69:
Heres the steps I took.

*******Before device was stuck at bootloop*******

1. Bought phone (XT1032)

2. unlocked boot loader

3. Rooted

4. Flashed Philz Recovery (wouldn't backup rom)

5. Flashed TWRP and CWM with same issue.

6. Flashed 2 ROMs to try it (TweakyOne + C-Rom, Both wouldn't boot. and tried on all recoveries.

********Steps after being stuck at bootloop*******

1. Followed this amazing guide here (https://www.youtube.com/watch?v=laU6NQ0LxR0)

2. Set up the stock ROM again

3. Flashed TWRP 2.7.0.0 via Fastboot

4. Backup worked successfully

5. installed CM11 and setup successfully

6. installed Lego rom just to assure myself (currently running this ROM)

I know this is no solution at all but just wanted to share my steps to see what maybe fixed my phone. possibly the stock 4.2.2 rom I flashed was the solution. Maybe the original factory ROM that came on the phone was the issue?
[Vibrant Q&A, Help & Troubleshooting] fscussel:
I've bought a software and the stupid company has a policy that if you do a factory reset you loose access to the paid program. simple as that. I have argued that it makes no sense, since its the same phone, same imei, same number, just did a system uprade but they refuse to help. I did a nandroid backup, so what I want to ask is: is it possible to retain DATA after flashing a newer ROM over the original? so that the program would recognize the phone as the same and don't lock?
[Droid Ultra Q&A, Help & Troubleshooting] SupremeOverlord:
OK Google Now, What's Up? "Hello Inigo Montoya, the time is 5:30pm. Not much going on right now".

I love that it does this, but I don't love that it uses that name. Where do I change this so it will call me whatever I want it to be? Do I have to change my whole Google+ account name to change this? Let me know if you know.
[Droid Ultra Q&A, Help & Troubleshooting] doogald:
I am 95% sure that it's the Google+ profile name, yes.
[Droid Ultra Q&A, Help & Troubleshooting] SupremeOverlord:
I am thinking that too. I wish there was another way to change that name.
[Nexus S General] oldblue910:
Hey everyone,

Would someone with a Sprint Nexus S mind flashing their device back to stock and pulling the OTA URL for the new 4.1.2/JZO54K update? You can just look in logcat after your device receives the update and the URL will be in there. Just search logcat for ".zip". Once I have the URL, I'll post it in the appropriate thread here and also on the Sprint Nexus S page on randomphantasmagoria.com.

Thanks!
[Nexus S General] smit.sanghavi:
Probably the owners have to be contacted personally. :(
[Windows Mobile Development and Hacking General] johnwhit1983:
I want to disable the external camera button on an XDAIIi to prevent the camera being activated inadvertently. Can anyone help me? Can this be done with eVC++?
[Windows Mobile Development and Hacking General] vijay555:
Should be possible with the registry. Writing an app in C++ would be overkill, but is also possible.

Check out the thread on how to ENABLE the backlight button on the universal, and reverse engineer the registry setting to see how to DISABLE the camera. I had to do the opposite on my Mio A701.

V
[Windows Mobile Development and Hacking General] levenum:
If nothing else download the app in this link and assign it to the camera button via the settings:

http://www.pocketpcfreewares.com/en/index.php?soft=382

It so stupid its brilliant :shock:
[Sprint Samsung Galaxy S III] dromango:
I am having issues using odin to flash anything. I have tried using Samsung drivers old and new and could not successfully flash md5 file using odin. I have previously been successful when 4.3 came out. and im trying to install 4.4.

It has phils touch recovery and mk3 rooted 4.3.

<ID:0/006> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> philz_touch_6.07.6-jfltexx.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/006> Odin v.3 engine (ID:6)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

<ID:0/006> Get PIT for mapping..

<ID:0/006> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Sprint Samsung Galaxy S III] bilgerryan:
Have you tried different cables and ports on your PC? Those are usually the things that cause problems with Odin.
[Sprint Samsung Galaxy S III] dromango:
I'll try that

windows looking for two drivers

samsung mobile cdc composite device

samsung mobile usb modem

both ready to use.

EDIT: I'll be damned. I was able to flash recovery file after using a different port. I have did this method before. strange.
[Android Q&A, Help & Troubleshooting] reebokhcfr:
I have a Le Pan S tablet (http://www.lepantab.com/index.php?option=com_content&view=article&id=88&Itemid=95) that works great for the first little while (20-40 minutes) when I play local video files. Then the player (both BS and MX with correct codecs) switches to software decoding from hardware, and the lag begins. I am trying to find out why it switches. Is it overheating? Something must be going wrong and it's very annoying. Thanks.
[Android Q&A, Help & Troubleshooting] es0tericcha0s:
Probably because it doesn't have the CPU power to run it well in H/W mode. Might need to find a less demanding version of the video. There's info about this stuff on MX Player's FAQ:

https://sites.google.com/site/mxvpen/faq

Section #4 has the more relevant info.
[Galaxy S III Q&A, Help & Troubleshooting] upsetshrimp:
OK so i have an I9300. for about a year now i think, maybe more.

And up until lately it worked relatively fine, but lately It started to gradually become unbearably crashy and annoying.

the camera very often crashes, leaving me with an "Unable to connect to camera" message, and only after a reboot does the camera work again. it used to happen scarcely, but now i can barely take 2-4 pictures before having to reboot.

Talking about rebooting, Not only do i get random reboots all the time, but after every reboot (not just the random ones) I get a UI crash after UI crash and the only way to fix it is by locking the screen and waiting,

Usage is extremely slow, to the point where launching whatsapp takes up to 5 seconds.

I amusing the cm11 nightlies but i get this with every ROM, I've tried updating cm11 and still nothing. wiping cache and data-also nothing.

the only escape now is full SD card format, but I'm scared to do that getting the same errors after it.

Could you help me figure out what's wrong with my phone? it's the only one i have and it's unusable.

I'm scared it's a hardware problem - that i cannot fix. but the signs are all there: the errors persist through formats (i formatted once about two months ago to no avail) and wipes and reflashes.

If you need any additional details about my system that i forgot to mention, ask me obviously!
[Galaxy S III Q&A, Help & Troubleshooting] andrewwright:
I'm guessing you have an i9300 and running cm11? That's what's in you're post so I'll go with that...cm11 is not stable enough atm. That will Explain the reboots from time to time. Best thing for you to do at this time is as always...go back to stock with Odin. Test it. Same reboots?? Back up and format you're int SD and flash again stock firmware with Odin. Still rebooting?? Possible hardware issue.
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] JoeFCaputo113:
Does anyone else keep the Toolbox feature on at all times and do you notice a battery drain? TIA!
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] JoeFCaputo113:
Anyone?
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] Ramer:
I keep it on all the time and I'm getting superb battery life on stock rooted rom, using Greenify although I was getting great battery life with Toolbox on before I rooted.
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] JoeFCaputo113:
Thanks man, so you literally keep Toolbox on 24/7 no matter what?

Anyone else too?! :good:
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] CNexus:
It doesn't matter. The service is always running regardless so leaving the toggle on versus leaving the toggle off is simply a matter of whether you'd like to see it off or not.
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] JoeFCaputo113:
Do you know the service name so I can hibernate it?
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] CNexus:
tw_toolbox
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] robbnice:
I also used Greenify, its the best battery saving app on the market, if you get the donated version it has some experimental features that can work on system apps, but I wouldn't messed with that to much on SGS5, they work perfectly on my Nexus 5, I would get easily 16 hrs used on my Nexus with Greenify and Xposed Framework working hand in hand. I Greenfiy every app thats in my toolbox, and when I used the app it comes out of hibernation and after words it goes back into hibernation, similar to freezing a app on Titianuim backup.
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] Ozpeter:
I've just spent two days on twice factory resetting then reinstalling 100+ apps on my Samsung tab to try to stop the "security storage" process pegging at about 20% whenever the screen is on, and finally I realised that having the "toolbox" switched on is the culprit. Just turning it off in the settings makes "security storage" go down from 20% to about 2%, and that makes a clear difference to battery life. Just reporting in this old thread for google to find to help others.
[T-Mobile Samsung Galaxy S 4] p012t:
Hi guys,

I am having issues with my GPS/location service. Basically it will not turn on. When I try to turn it on in settings it just freezes and I get an error saying settings has closed. When I try to use the toggle switch from the pull down menu same thing but this time the System UI has stopped.

Has anybody ran into this issue before? Please help out

if this helps i am rooted on infamous v8.0 rom / 3.4.0 kernel / andriod 4.2.2

Thank You all
[T-Mobile Samsung Galaxy S 4] Karakoram2:
Could try reflashing your ROM or Odin to stock and start over.
[T-Mobile Samsung Galaxy S 4] p012t:
Im actually trying to avoid that. You have any other ideas? I guess it has to be a software bug of some sort.

the gps just stopped working out of nowhere.

Thanks
[T-Mobile Samsung Galaxy S 4] MultipleMonomials:
Try checking the logcat after it crashes.

Sent from my Galaxy S4
[T-Mobile Samsung Galaxy S 4] p012t:
Hey, I checked the logcat as you send and I narrowed it down to this, I think this is the error im not too sure

its kind of hard to read

05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

Do you have any idea if this is the issue and how do I fix this ?

Thank you
[T-Mobile Samsung Galaxy S 4] MultipleMonomials:
Just a guess, but try fixing permissions in recovery, or open terminal emulator and run

ls -l /dev
[T-Mobile Samsung Galaxy S 4] p012t:
I already have wiped the cache and dalik cache as well as fixing permission from recovery. Nothing worked
[T-Mobile Samsung Galaxy S 4] Skipjacks:
Then you are left with no recourse other than to reflash the rom in recovery or flash back to stock using Odin and start over.

Your logcat doesn't show the cause of the problem. It just shows the result of the problem.
[T-Mobile Samsung Galaxy S 4] MultipleMonomials:
I think that reflashing the rom doesn't affect the /dev partition. Maybe fix permissions doesn't either. Would you run the ls -l command and post the output?

Sent from my Galaxy S4
[T-Mobile Samsung Galaxy S 4] p012t:
ran the command and all this shows up

sh-3.2$ ls -l

-rw-r--r-- root root 4686 1969-12-31 19:00 MSM8960_lpm.rc

drwxr-xr-x root root 1971-01-02 22:43 acct

drwxrwx--- system cache 1970-12-30 01:22 cache-rwxr-x--- root root 268108 1969-12-31 19:00 charger

dr-x------ root root 1971-01-02 22:43 config

lrwxrwxrwx root root 1971-01-02 22:43 d -> /sys/kernel/debug

drwxrwx--x system system 2014-05-16 19:34 data

drwxrwx--- system system 1971-01-02 22:43 data_1

drwxrwx--- system system 1971-01-02 22:43 data_2

drwxrwx--- system system 1971-01-02 22:43 data_3

-rw-r--r-- root root 136 1969-12-31 19:00 default.prop

drwxr-xr-x root root 2014-05-15 17:23 dev

drwxrwx--x system radio 2013-10-25 23:14 efs

lrwxrwxrwx root root 1971-01-02 22:43 etc -> /system/etc

-rw-r--r-- root root 18622 1969-12-31 19:00 file_contexts

dr-xr-x--- system system 1969-12-31 19:00 firmware

dr-xr-x--- system system 1969-12-31 19:00 firmware-mdm

-rw-r--r-- root root 768 1969-12-31 19:00 fstab.qcom

-rwxr-x--- root root 164648 1969-12-31 19:00 init

-rwxr-x--- root root 4638 1969-12-31 19:00 init.carrier.rc

-rwxr-x--- root root 2487 1969-12-31 19:00 init.goldfish.rc

-rwxr-x--- root root 6737 1969-12-31 19:00 init.qcom.class_core.sh

-rwxr-x--- root root 2320 1969-12-31 19:00 init.qcom.class_main.sh

-rwxr-x--- root root 4266 1969-12-31 19:00 init.qcom.early_boot.sh

-rwxr-x--- root root 5142 1969-12-31 19:00 init.qcom.lpm_boot.sh

-rwxr-x--- root root 22863 1969-12-31 19:00 init.qcom.rc

-rwxr-x--- root root 3045 1969-12-31 19:00 init.qcom.ril.sh

-rwxr-x--- root root 4486 1969-12-31 19:00 init.qcom.sh

-rwxr-x--- root root 3514 1969-12-31 19:00 init.qcom.syspart_fixup.sh

-rwxr-x--- root root 35297 1969-12-31 19:00 init.qcom.usb.rc

-rwxr-x--- root root 6004 1969-12-31 19:00 init.qcom.usb.sh

-rwxrwxrwx root root 38414 1969-12-31 19:00 init.rc

-rwxr-x--- root root 9193 1969-12-31 19:00 init.target.rc

-rwxr-x--- root root 1795 1969-12-31 19:00 init.trace.rc

-rwxr-x--- root root 3947 1969-12-31 19:00 init.usb.rc

drwxrwxr-x root system 1971-01-02 22:43 mnt

drwxrwxr-x root system 1971-01-02 22:43 mnt_1drwxr-xr-x system system 1971-01-02 22:43 persdata

drwxrwx--x system system 1971-01-02 22:43 preload

dr-xr-xr-x root root 1969-12-31 19:00 proc

-rw-r--r-- root root 2759 1969-12-31 19:00 property_contexts

drwxr-xr-x root root 1969-12-31 19:00 res

drwx------ root root 2013-06-06 21:35 root

drwxr-x--- root root 1969-12-31 19:00 sbin

lrwxrwxrwx root root 1971-01-02 22:43 sdcard -> /storage/emulated/legacy

-rw-r--r-- root root 1976 1969-12-31 19:00 seapp_contexts

-rw-r--r-- root root 134977 1969-12-31 19:00 sepolicy

dr-xr-x--- system sdcard_r 1971-01-02 22:43 storage

dr-xr-xr-x root root 1971-01-02 22:43 sys

drwxr-xr-x root root 2014-01-08 19:49 system

lrwxrwxrwx root root 1971-01-02 22:43 tombstones -> /data/tombstones

-rw-r--r-- root root 272 1969-12-31 19:00 ueventd.goldfish.rc

-rw-r--r-- root root 6662 1969-12-31 19:00 ueventd.qcom.rc

-rw-r--r-- root root 4794 1969-12-31 19:00 ueventd.rc

lrwxrwxrwx root root 1971-01-02 22:43 vendor -> /system/vendor

sh-3.2$

once again thank you all for helping
[T-Mobile Samsung Galaxy S 4] MultipleMonomials:
I think you ran ls -l and not ls -l /dev. My fault for giving confusing directions.

Sent from my Galaxy S4