yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] The Solutor:
No need to complicate your life with an USB keyboard

An Iphone sliding bt keyboard, the right sized android phone, some tasker rules and a bit of fantasy are more than enough to build your own qwerty phone, in half an hour or so.

This is what I did more than one year ago, when I had to use a dual sim phone.

For the record the phone was an Alcatel One Touch Star

+

a NUU keyboard

=

[YOUTUBE]mRFTN_9Sj0M[/YOUTUBE]
[Motorola Droid 4] godneps:
But then you need to have BT on all the time and even with some extra battery power hidden away in the keyboard that'd be a power killer no?

Or am I looking at this all wrong? Should we just be taking a BT slider case and adding more battery life?! I mean it'd be pretty cool to have a phone where you could leave BT on at all times and still have power at the end of the day...
[Motorola Droid 4] StevePritchard:
Odd - I do have BT on all the time, and have power at the end of the day. BT is never at the top of the usage list for me.
[Motorola Droid 4] The Solutor:
BT is almost unnoticeable on the battery economy of a big sized android phone.

A keyboard does way less traffic than a BT headset, so way less battery consumption.

Th BT keyboard goes automagically in sleep mode when it's closed.

And, if you are picky, you can turn OFF the BT on the phone with a simple Tasker rule. (tasker is needed anyway to automate the screen rotation, the screen unlock when the keyboard is slided out and so).

If the above is not enough for you, I must add that the keyboard backlight, unlike a native one, is powered by its own battery.

So, the short answer to the question is absolutely not.
[Motorola Droid 4] godneps:
Now that I did not know. Every day is a school day...
[Motorola Droid 4] Flash-A-Holic:
I modded iPhone 6 bluetooth keyboard case to Xiaomi Mi4C. It was pretty easy job. I am using that as a daily driver now. If you are interested take a look from here: Qwerty Keyboard Slider [DIY]
[Motorola Droid 4] mifritscher:
I would buy it at once, honestly. I loved my Psion 5 MX.
[One (M8) General] Psosmith82:
The camera won't connect anymore, Wi-Fi won't turn on and the SD card wont mount. How did this get approved by google??

Edit:

To get the OTA to work properly and flash the correct kernal, your CID must be changed to GOOGL001. If you have the GPE device, you don't need to do anything, but if you have a converted GPE then you must change your CID if you want OTA's. This was not made clear in the RUU thread, it was mentioned that changing your CID was optional if you had one of the listed CID's, but it is not optional, but a requirement if you want the OTA's to work.

Everyone that has changed there CID's reflashed the OTA and everything flashed fine, whereas anybody that had not modified there CID had the problem with the kernal.
[One (M8) General] HRodMusic:
maybe you had a bad download?
[One (M8) General] Psosmith82:
I used the download linked from the discussion thread. Put on phone storage, rebooted into recovery and applied the update from phone storage.
[One (M8) General] TheriaultAJ:
Same results with OTA.

Sent from space.
[One (M8) General] Extremer2903:
Checked the MD5 before? :D
[One (M8) General] Psosmith82:
Used the OTA provided by graffixnyc
[One (M8) General] Archon810:
The signature verification wouldn't apply the update if it saw mismatches.
[One (M8) General] graffixnyc:
Odd.. I had no problems using the OTA zip.. Did you guys try wiping data?
[One (M8) General] Psosmith82:
I tried wiping data, still had the same problem. I am reflashing the RUU and will try the ota again. If it doesn't work after the 2nd try, i will just wait for google to send the OTA to me. Wiping data sucks, have to redo everything
[One (M8) General] willverduzco:
I wonder if this is also being experienced by any other users or if this is specific to your software config and/or some glitch while writing the firmware. I assume you haven't yet tried wiping your /data partition, right?
[One (M8) General] Psosmith82:
I wiped data and still had problems. I'm working on starting over right now
[One (M8) General] Extremer2903:
Then problem should be wiped/not wiped, I think. Anyway, trying with this error stuff is always an excited challenge with me, try to deal with it like that to reduce percentage of throwing your devices away :D.
[One (M8) General] graffixnyc:
Also you need to be FULLY stock.. that includes the stock kernel. If you are running a custom kernel some kernels flash libs and modules. EVERYTHING NEEDS TO BE STOCK
[One (M8) General] Psosmith82:
Mine is fully stock. I have an unlocked HTC one, and i flashed the GPE conversion RUU. Does the CID need to be changed to the Google CID
[One (M8) General] angeltouch 4g:
that's a really good question Psosmith
[One (M8) General] TheriaultAJ:
Only thing I can think of on my example is I had 'CF.lumen' installed... Other than that, I had (your) completely stock GPE conversion.

Troubleshooting...

Sent from space.
[One (M8) General] Android The Greek:
Is the problem from the update zip or ota+
[One (M8) General] Psosmith82:
I figured out the problem. I flashed the new RUU that graffix posted with 4.4.3. The Kernal in the OTA is not updating like it should, it stays on the kernal that was made in March. The new Kernal has a date of Thursday May 22nd. So for whatever reason, the OTA is not flashing the new Kernal, which is why all those things were broken. If you use the RUU update, it will flash the new kernal, and everything works as it should.

You'll know right off the bat at first boot. With the OTA, the boot animation hangs and it hangs on the home screen. With the RUU flash, everything is buttery smooth.
[One (M8) General] oldblue910:
Something tells me this problem is occurring for people who actually have a retail M8 that they dirty-flashed using a GPE RUU.

Does anyone with an honest-to-God GPE that was purchased from Google have this problem? If so, this is huge.
[One (M8) General] graffixnyc:
The update worked fine on my device and I used it for the conversion RUU. odd.. I used that very same OTA file. very odd...
[One (M8) General] Funkym0nkey:
Update went smoothly on actual GPE. No issues.
[One (M8) General] oldblue910:
That's what I figured. I guarantee you that's what it is, then. The update will work fine on a Rolex, but not the Rolecks. Go figure. :/

This same thing happened with the M7 when people tried to convert their retail devices to GPE. The conversion was only about 99%. If you flashed a GPE RUU, it would work fine and act totally converted, you could apply OTAs, the whole 9 yards. But, if you ever tried to lock your bootloader and go S-ON (the way a real device comes out of the box), your phone would boot into Android, then as soon as your lock screen showed up, it'd reboot again.

The lesson to take away here is that if you try and bend the rules and live in the gray world, these are the things you're going to deal with, unfortunately. This update was only tested on real GPE devices so if you flash it onto anything else, Google and HTC have precisely zero cares about it.
[One (M8) General] Psosmith82:
The OTA is not flashing the new kernal, that's the problem, but you could be right, in that it's only an issue on GPE converted phones. Hopefully not, because i don't want to RUU everytime a new OTA comes. Maybe the devs could figure out why the kernal wont flash in the OTA

Weird though that everything worked good with graphix phone, as he is GPE converted.
[One (M8) General] mikeyinid:
I have a T-mo M8, took the OTA with no issues. Boot flashed and everything.
[One (M8) General] Funkym0nkey:
It looks like it. Just updated another GPE and that too went smoothly. Had bought total 3 GPE M8s for my friends and family. 2 are in Family including mine and so far no issues on both with the OTA update.
[One (M8) General] clubtech:
Not sure what the OP and others are doing wrong but the OTA worked perfectly fine for me.

I have a developer HTC one M8, converted to GEP with the original RUU. Rooted, everything else is stock.

I applied the OTA manually through recovery and everything is working and the kernel flashed just fine, so not there is nothing wrong with the OTA that was posted or the original GPE RUU.
[One (M8) General] OctoberNexus:
The OTA flashed the new kernel fine for me. I'm on T-Mobile converted M8 with GOOGL001 cid and S-OFF but relocked bootloader.

Sent from my Google Play Edition M8
[One (M8) General] graffixnyc:
It wasn't mentioned in the RUU thread(it is now) because it wasn't known :P Remember, this was the first OTA.. I could only go on the experience I had with the m7 which the cid and even the mid didn't matter. Up until a first OTA everything is theoretical. This explains why I had no issues with the OTA. lol I have had my CID set for a while.
[One (M8) General] graffixnyc:
Guess you would have lost on that guarantee, good thing you didn't bet money on that.. hahaha :laugh: And odd.. because in all the time I have been doing the conversions (for both the m7 and m8) and the countless times I have flashed it and updated devices (more than any one person just from my testing alone) I have never experienced the issues you speak off. I have unlocked and relocked the bootloader many times. s-on? Why would anyone want to go s-on on a converted device? The only way you'd want to s-on it is if it was going in for warranty repair and since it's not technically a GPE device it shouldn't be going back in with a GPE bootloader..
[One (M8) General] oldblue910:
The point is, if you're going to call it a 100% conversion, you should be able to lock and S-ON it without issue. If you can't, it's not a 100% conversion. S-ON is the ultimate test of whether it's a real conversation or not. Pass or fail, the end. To me, it's no more or less complicated than that. It's not a matter of why you'd want to do S-ON. It's a matter of truth in advertising. ;)

For most, a "converted" device will do the trick just fine. I'm just calling a spade a spade. That's all. :) I have no interest in unlocking bootloaders, root, or anything of that sort. For me, I read "100% conversion" and my mind instantly went to locking it down to factory state to see what happens. That was all the proof I needed that the differences between GPE and US retail variants go beyond the ROM.

Don't take what I said personally. I know you've done a lot of work on this. I just think it's grossly irresponsible for people to go around claiming an OTA is busted and warning people not to update when said update works perfectly fine. If the update works on the device it's intended for, that's the only thing that's important. The fact that it doesn't with on a "converted" device is irrelevant and should be taken as a given with each new OTA until it's been tested and proven to work.
[One (M8) General] graffixnyc:
Anything that ever gets update by Google is converted.. And yes, you can s-on. I know because I did it on my m7 the first time and couldn't get s-off again on that device for a very long time.. And I'm not going to do it now just to prove a point and be stuck s-on. In all intensive purposes it's a full conversion. The only partitions not touched really are ones that contain the serial, imei and a few others with sensitive data but any partition that's ever included in an Ota (which is why you're really converting, to get the Ota updates) is converted to gpe partitions. So I'm kinda insulted a second time by you.. You belittle what I do and I have done it way many more times than you. OK so it's a fake conversion that's why I got my Ota and had it successfully installed before some "real" gpe got the update.

You guaranteed the reason the Ota update was failing was it was because it was a converted device.. But you were wrong.. So sorry if I don't put too much stock in what you say
[One (M8) General] oldblue910:
Well:

a) With the M7, you could S-ON with 4.3 but if you took the OTA to 4.4/KRT16S or anything after that, the reboot issue will show up every time. This was true even with your CID and MID set to match the GPE.

b) While yes, I was wrong about it failing due to being a converted device, the fact is that the update works for devices for which it was intended. That's the only place it needs to work and the only place where Google and HTC have a responsibility to ensure that it works. If the update doesn't work with devices for which it WASN'T intended, that's the individual user's problem and not a cause to start a thread claiming that the update is no good.

c) I'm sorry you took my comments as insulting. They certainly weren't intended that way. I was more taking issue with the whole point of this thread.
[One (M8) General] Stephen:
Thread closed. There is a stickied thread here: [REF][GPE] HTC One M8 Google Play Edition Stock OTA URLs to do with GPE update issues.

Many thanks,

Ghost
[General Questions and Answers] aman765:
Hello I have a rooted Wikipad 7" tablet (wpt005) but unfortunately nothing support my device. Is there a way to get cwm or twrp on ANY device?

Note: please keep it somewhat noon friendly
[Nook HD, HD+ Q&A, Help & Troubleshooting] Mf123:
I have an issue that seems to be similar to those suffered by a number of people. I'm just having difficulty understanding the cause of it, and the solution. I have a nook hd+ that no longer boots as a result of trying CM11 on an SD card.

I installed CM11 to an SD card (as I was nervous of altering my nook) using bokbokan's excellent instructions. Initially it seemed fine but this morning it was unexpectedly out of battery and will no longer boot.

The symptoms are similar to this: http://xdaforums.com/showthread.php?t=2611769, this: http://xdaforums.com/showthread.php?t=2736347 and this: http://xdaforums.com/showthread.php?t=2649061&page=2 except that the posters there had previously replaced the stock software and overwritten the emmc.

When the SD is in, it locks up on the Cyanoboot screen, when the SD card is out I only get to the black screen with 'Nook' on it and no further. It looks like the SD install has messed something up on the internal emmc. Hard resets and multiple failed boots don't appear to help.

I can occasionally (but not always) get it to reboot to CWM recovery by reinserting the card and holding down N and lock, but I get a lot of errors such as "E:Can't open /cache/recovery/last_log", "W:failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/cache on /cache failed:No such file or directory" and "I:Can't partition non-vfat: /emmc (ext4)". When I go to 'Mounts and Storage' in CWM, I cannot mount anything (e.g. "Error mounting /boot!").

I chose to go down the SD card install route (using ) in order to avoid touching the stock install on the emmc, but now the whole thing is dead.

Reading other threads, it sounds like either:

1. The emmc is bricked due to some firmware bug. The impression I get from reading around is that CM11 was supposed to incorporate a workaround for the issue. If the emmc is the problem, I have to return the Nook and hope to get a working one.

2. The emmc has (somehow) become corrupted, I have to put a different version of CWM on my SDcard (so it will install to the EMMC rather than the SDcard, and because CM11 uses a different version), using the instructions here: http://xdaforums.com/showthread.php?p=35811322 and then reinstall a stock rom to my emmc. I then have to reregister the Nook (not sure if this is essential) before being able to use my CM11 SDcard install again.

If it is the first problem, I would like to know how I can check to see if the emmc is indeed broken.

If it is the second, I would be grateful for any help in understanding how and why the SD install has messed up the emmc, and whether the steps above are likely to bring it back to life.
[Nook HD, HD+ Q&A, Help & Troubleshooting] leapinlar:
It sounds like your emmc is indeed bricked. I would go for the warranty exchange now. Just because you installed CM11 to SD does not mean it does not use emmc partitions. It still accesses and uses many of them (cache, rom, bootdata, /data/media, etc.). So there is opportunity for a brick. I would exchange it now while the cyanoboot logo does not show when booting without the SD.
[Nook HD, HD+ Q&A, Help & Troubleshooting] Sherip:
You may find links and info in this post helpful http://xdaforums.com/showthread.php?p=44810400
[Nook HD, HD+ Q&A, Help & Troubleshooting] Mf123:
Thanks to both for replying. I feared that was the case.

I'm a bit disappointed that the SD card install (generally the option for those who want to leave the nook untouched) can in fact ruin the machine.

I've contacted the Nook website and will see what happens.
[Nook HD, HD+ Q&A, Help & Troubleshooting] leapinlar:
Just take your device to a store. They will exchange on the spot once they verify your registration on their computer. Of course don't tell them you were running CM, even on SD.
[Nook HD, HD+ Q&A, Help & Troubleshooting] Mf123:
Thanks, but there are no BN stores in the UK. They don't even sell the Nook directly from their uk website anymore. I have to post it to the Netherlands and see what happens.
[Nook HD, HD+ Q&A, Help & Troubleshooting] Mf123:
So, after 2 months, and a lot of arguing with customer services, I have finally got a replacement Nook through the post.

I am still keen to try CM, but want to be really sure that my Nook doesn't get bricked again. Is there any way of checking whether an sd card install is likely to trigger an emmc failure on my new Nook?
[Nook HD, HD+ Q&A, Help & Troubleshooting] leapinlar:
The best way to avoid bricking by CM11 is to not try CM11. I run CM 10.1.3 and have heard of no one bricking when running that.
[General Questions and Answers] shadyraver:
When Going through a forum and I come across a post that has a number on the far left on the header bar. When I click on that number It takes me right back to the post.. What I'm wondering is there a way that there is a way to save that post number some how so I can go back to it later on. Like is there a way I can keep a list on the site somewhere. I just wanted to know if it was possible somehow. I hope I explained it well

Thanks
[MDA II, XDA II, 2060 ROM Development] married_jedi:
This is based on another thread at the Blue Angel Upgrading Section.

Supposedly, Increasing the Paging Pool value, allows for smoother speeds at wm5... at the cost of RAM in the Programs area.

Just thought I'd share it here...

Here’s how I did it…

1. Extract NK.nba

> xda2nbftool -x NK.nbf NK.nba 0×20040304

2. Open with a Hex Editor

3. Go To Address 0×00404650

It should look like

64 00 00 00 D8 FF 21 80 01 00 00 00 00 00 50 00

yung pagin pool size is

00 00 50 00 or reversed 00 50 00 00 w/c is 5,242,880 bytes

I changed it to

00 00 00 01 or reversed 01 00 00 00 w/c is 16,777,216 bytes

4. Update Image Check Sum

> xda2nbftool -c -u NK.nba

5. Repack as NK.nbf

> xda2nbftool -x NK.nba NK.nbf 0×20040304

6. Put in the same directory as HimaUpgradeUt.exe

7. Flash as you normally would.
[MDA II, XDA II, 2060 ROM Development] shein:
Supposedly, Increasing the Paging Pool value, allows for smoother speeds at wm5... at the cost of RAM in the Programs area.

I do not think that we will have to reinstall the progs.

2Jedy: Did you noticed any improvement in the speed? Which rom did you used? Is the method you described suitable for all roms?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] dead4ngel:
hi is there a kernel that can support fast charge? i also have an s3 and that has boeffla kernel. with that i can change the value form 1000mv to 1200mv. only problem is that kernel doesnt support the n7000. let me know thanks.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Azeazezar:
Yes.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] dead4ngel:
link?

hi. thanks for reply. have you got a link?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Azeazezar:
http://xdaforums.com/showthread.php?t=2192893
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] dead4ngel:
thanks you so much
[T-Mobile Samsung Galaxy Note 3] markysd:
hey guys been a while but back it it..im on jelly still and rooted and i cant get the OTA update.. can i just flash the kit kat? not sure what one to download.. i just want a stock base rooted version..im on att but have tmo note 3 and going back to tmo later this month..

do i have to factory restore clean via kies first?

thanks guys
[T-Mobile Samsung Galaxy Note 3] jdidtht:
Yea, if you wanted the ota, in short you would have to grab the stock non rooted firmware kies , I prefer Odin and just get back to stock stock. You may be able to hide root, and grab the ota but I've never got into that. I prefer to back up whatever needs it via titanium saved to ext card, wipe completely and just start fresh with the kk update. That way you getbthe modem, you get the boot loader, the new partitions etc etc and IMO a more solid user experience. Some may beg to differ, but, updates are updates for a reason and ne6 is far more stable and reliable than nb4 was. Kernel source is cleaner, ROM bits were cleaned up, volte was added and its just better. If you've never checked tweaked ROM out before man, you are missing out. Its the way touch wiz was meant to be, dwitherall is a friggin smali destroyer, and his work is the work others strive to do. Thats just my two cents and what I would do, but if you wanted to just flash a kk ROM right now, ya probably could, but you aren't getting the benefits of why is was the upgrade in the first place. Users may disagree with my statement but, the real devs, would agree ne6 is a far more solid base to be on, and once tweaked is done is game over. Thanks for the time man
[T-Mobile Samsung Galaxy S 4] dagentooboy:
Please note the same information used to develop the app is in the guide for free... the app just makes it easier

You can find the app here

CALIBRATION REQUIRES ROOT... PLEASE GO GET ROOT ON YOUR PHONE AND THEN COME BACK.

Oh and BTW... I cannot be held responsible for anything that happens to your phone.... EVER!

use "adb shell" or a terminal emulator to get a terminal prompt and run the following commands

Step 1. - Save old calibration value (Optional)

su
mkdir /sdcard/S4data/
cat /efs/prox_cal >> /sdcard/S4data/prox_cal

Step 2. - Edit calibration value and update permissions

Grab the current value with everything clear of the proximity sensor.

cat /sys/devices/virtual/sensors/proximity_sensor/state

The value on mine was between 45 and 55. If you a lot higher then there might be something wrong with your phone. I used 150 for my value. You can use whatever you want but 150 is working great for me.

Convert your calibration value to hex (The windows calculator works great for this... use programmer mode). Put your calibration value in place of the 96 in the command below.

su
echo -en $'\x96' > /efs/prox_cal
chown system:system /efs/prox_cal
chmod 644 /efs/prox_cal
sync

Now reboot and your proximity sensor should be working.

Big thanks to greaty for his post here
[T-Mobile Samsung Galaxy S 4] PanchoPlanet:
Does this app remove dirt/lint from your proximity sensor?

Pp.

Sent from my Touchwiz device that never forgets gapps and everything works the way its supposed to.
[T-Mobile Samsung Galaxy S 4] dagentooboy:
I took my phone all the way apart and cleaned the sensor and it still had the issue. It seems that the sensor reads about 50 all the time and that is where they have the trip point set. This guide and the app just move that trip point.
[T-Mobile Samsung Galaxy S 4] Armandopjr:
This saved my phone! Thank you!

Sent from my SGH-M919 using Xparent Red Tapatalk 2
[T-Mobile Samsung Galaxy S 4] dagentooboy:
Glad it worked for you!
[T-Mobile Samsung Galaxy S 4] Kriomag:
because you dont know how to clean... i had 46 all the time and now i have 11-12 for month or two and it is not increasing anymore because i shielded it with silicone/rubber and no more dust come inside - thats the only permanent way to fix this.
[T-Mobile Samsung Galaxy S 4] nitinvaid:
I dont think its for CM11 also
[T-Mobile Samsung Galaxy S 4] fincan:
FYI, this file (/efs/prox_cal) does not exist in Google Edition S4.