yashsingh1/xdaforums huggingface dataset:
[Off-topic] LumpiStefan:
Or maybe George W. Bush... ;-)

*SCNR*

Stefan
[Off-topic] AVP:
Noway!!! He means me!

---

Aliens are coming...
[Off-topic] ajong:
Yes, you're !!

and he is going to waiting SRS for 'Christmas Edition'

(me too)
[Atrix 4G Q&A, Help & Troubleshooting] jakuri:
Hello! I'm having an issue with both cm 9 and 10.1, i can't access to 3G, everything is fine (I checked if something was wrong) and I can see someone issued that at github, but i see that it's no problem now, so i don't know what to do! Help please!
[Atrix 4G Q&A, Help & Troubleshooting] quetzalcoatl2435:
3G works. Check your APN.
[Atrix 4G Q&A, Help & Troubleshooting] jakuri:
Thank u very much! I just checked APN configuration in an official forum of my phone company. Now I have th efull experience!=D
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] TechNexus:
I'm running the 4.2.2 PAC ROM (Paranoid + AOKP + CyanogenMod), the only listed issue is a minor screen error when using the Pi feature, however I've noticed that my cellular signal is frequently dropping, and when I do have reception, it only lasts for about 5 seconds. Bell is my service provider so I know it's definitely not poor signal that is causing this. I was also running a previous custom rom by AOKP and everything was working perfectly fine so I know that I don't have any hardware problems. I really enjoy all the features of this custom rom but it's destroying my phone, even though it's updated nightly, I am not sure how much progress is made per update. The rate of battery drain is ridiculously high, about 1% every 2 minutes. It could just be that i'm being impatient considering the ROM is fairly new. Anyone else dealing with these issues? Has anyone found a solution? I don't know if it's the rom or if I'm doing something wrong, any sort of guide or analysis and response would be greatly appreciated!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xcrazydx:
Make sure you're using ucmc1 radio.
[HTC Pico (Explorer)] salil.bajaj:
I installed a custom contacts.apk and changes the permissions using root browser.I rebooted my phone but it stuck on the htc splash screen.I removed the battery,reinserted it,pressed the power button but again it got stuck on the splash screen.

So i thought to delete the contacts.apk i replaced.So i rebooted into bootloader and chose recovery.

But now i am not able to get into recovery.Whenever i try to,the screen goes black for a second and again displays the teamwin blue colored screen.

I got cm10 beta6 installed on my phone.

Please reply ASAP.

Thank you.
[HTC Pico (Explorer)] akashpatel:
Happened to me too a few days ago..i think the bug is in TWRP recovery cause sometimes it just gets stuck on the blue logo and sometimes the touch doesnt work.....so what i did to splve the prob is that i jst went back to yannou's recovery and flashed another rom....hope i helped
[Verizon Samsung Galaxy S III] Volvogia:
Get Xda app off play store. Go to the verizon s3 section and get the stock rom and flash it. Thats about all i would think you could do. With the usb broken only thing you could maybe do is a jtag
[Verizon Samsung Galaxy S III] bobloblaw1:
Mobile Odin from the play store?
[Samsung Captivate Glide] S-trace:
Hello!

I'm trying to repartition internal memory of Captivate Glide. Downloaded PIT file from device using latest GIT version of heimdall, but trying to flash it back to phone (even unmodified) I'm get error:

sudo ./heimdall flash --repartition --pit pit.pit --13 recovery.img
Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Uploading PIT
ERROR: Failed to confirm end of PIT file transfer!
ERROR: PIT upload failed!

Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
Re-attaching kernel driver...

Using Odin3 v3.04 with PIT file set and Repartition checkbox checked I'm get next error:

<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

Below attached photos of phone's display after errors.

How can I flash PIT file into Glide?

Thank You.
[Verizon Samsung Galaxy S 4] chrisjm00:
I have noticed through the course of the day that my battery keeps getting drained by maps. I'm not using maps at all but it keeps opening itself up. Is this from location services? Or is it from something else?
[Nexus 4 Q&A, Help & Troubleshooting] Shank09:
Ok, I am a student of a university in Canada. I want to buy the Nexus 4 and the Wired Headset together.

In Canada the Wired Headset with Microphone is coming as

TEMPORARILY OUT OF STOCK
We are out of inventory. Please check back soon.

The Shipping for the phone is $16, not sure about the headphones.

What will i be charged if i buy them separately? and together?

Will i save some money if I buy togeather? [ON SHIPPING]

Thanks!
[Nexus 4 Q&A, Help & Troubleshooting] Ichiban Rei:
I'm not in Canada, but if I go to the check out, it tells me my total including shipping and taxes after you select your ship to address. You can easily just do one for each item. When I check, I see that my shipping total for nexus and headphones is 13.99USD Same as shipping just the Nexus. If the headphones are shipped to me separately I'm charged 5.99USD.

Hope that helps.
[AT&T Samsung Galaxy S 4 Android Development] Scarchunk:
Here is a link to the most recent CM nightly for the ATT S4. All credit goes to CM team and djrbliss. I just ran the loki patch against the stock jfltecan CM kernel and edited the build.prop and updater-script for our devices. Of course you'll need custom recovery and the usual wipe/gapps routine for CM.

Please feel free to mirror.

5/24 Nightly:

https://truck.it/p/aELheGFdu8

gapps:

http://goo.im/gapps
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
You're the man now, dog.
[AT&T Samsung Galaxy S 4 Android Development] eighty1:
Thanks!
[AT&T Samsung Galaxy S 4 Android Development] Dallenn:
Hmmm this or slim bean? I am really liking slim bean
[AT&T Samsung Galaxy S 4 Android Development] Relys:
How is this comparable to SlimBean? :) What should I use?
[AT&T Samsung Galaxy S 4 Android Development] flinttownbrown:
MIRROR:

https://truck.it/p/YX-QrCrKn6

Feel free to add to OP
[AT&T Samsung Galaxy S 4 Android Development] rob_rector:
Slim Bean seems to be pretty cool, but I gotta try this out too... I have a feeling I am going to be spending a lot of time flashing this weekend :)
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
Boots like a champ. Good work.

There seems to be a problem getting LTE to connect though. Anyone know about this?

EDIT: Ooop, nevermind! Network mode has to be set to LTE / GSM/WCDMA!
[AT&T Samsung Galaxy S 4 Android Development] hyelton:
Here is a Mirror on my Server :)

http://storagecow.eu/index.php?dir=Xda/AT&T+S4/CM+10/
[AT&T Samsung Galaxy S 4 Android Development] rob_rector:
You need to change your Mobile network Network Mode to LTE\GSM\WCDMA and APN to: ATT LTE

Works for me :)
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
Yup! Got it!
[AT&T Samsung Galaxy S 4 Android Development] drdingo21:
Love every one of you.

Are we able to just flash Slim bean as well?
[AT&T Samsung Galaxy S 4 Android Development] drewdatrip:
Would you mind outlinine the steps you took in the command line process? Im attempting to complete this myself and i am running into errors

Thanks

Drew
[AT&T Samsung Galaxy S 4 Android Development] SysAdmNj:
So how is this cm 10.1 running on your at&t sgs4's?

Better than the nexus 4?
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
One thing I'm noticing is even without Samsung's bloat, there's still only 9.57GB usable space out of 16GB.

Perhaps the device needs to be re-partitioned somehow?
[AT&T Samsung Galaxy S 4 Android Development] jetlitheone:
Yes the device needs to be re partitioned.

And as far as I know its not possible yet.
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
It's running like a dream.

Also, the phone has better specs than the Nexus 4, so I would say yes it's better.

The advantage of the Nexus 4 is still getting updates straight from Google though.
[AT&T Samsung Galaxy S 4 Android Development] nakedninja42:
Disadvantage is lack of LTE :D
[AT&T Samsung Galaxy S 4 Android Development] Scarchunk:
I pulled my aboot.img using the instructions on djrbliss's github:

adb shell

su

dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img

chmod 644 /data/local/tmp/aboot.img

exit

exit

adb pull /data/local/tmp/aboot.img

Then downloaded the CM build and the loki_patch-linux-x86 files. Extracted the boot.img from the CM zip and moved all three files over to a Cent box.

./loki_patch-linux-x86 boot aboot.img boot.img boot.lok

That's it for command line. Everything else was notepad++ and winrar. :good: Noticed I forgot to change the model in the build.prop from the SGH-I337M to the SGH-I337. So you might wanna fix that while your at it.

What error you getting?
[AT&T Samsung Galaxy S 4 Android Development] neincraft:
Once I get this, would I able to update using the in built updater, or would the updates also have to be loki'd?
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
I would not suggest using the built-in updater as all builds have to be Loki'd in order to work. We will have to stick with this build until CyanogenMod team starts compiling builds for this phone.
[AT&T Samsung Galaxy S 4 Android Development] 02busa:
Running great here (so far) and zero lag for me... Thanks again!
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
Hmm, I just noticed the camera app is a bit funky. It won't take widescreen pics and when you change to the front camera, the image lags and is a bit distorted.
[AT&T Samsung Galaxy S 4 Android Development] 02busa:
If you mean "panoramic pics" mine is working fine.. As is my front camera.
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
I mean with the normal camera, not panoramic. Unless I've been in Samsung-land too long and forgot the normal camera doesn't do widescreen pics. Does it? :eek:
[AT&T Samsung Galaxy S 4 Android Development] 02busa:
Only setting I see for widescreen is panoramic.. Just tried calls after an hour of setting it up.. Calls are delayed a while before they connect also sound mic nor ear speaker are working... Already changed my APN and network mode... :banghead:
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
Hmm, I just made a call and was able to hear through the ear speaker fine.
[AT&T Samsung Galaxy S 4 Android Development] sam3000:
I have a working device tree here that probably achieves almost exactly what you already have:

https://github.com/sam3000/android_device_samsung_jflteatt

I imported the one of the existing jf device trees as a starting point so you can see the exact changes. If you have one too, let me know so I can see that the delta is.

Thanks to this thread, I've just added setting the default apn to pta. If anyone knows how to set the network mode, feel free to point it out (I'll look tomorrow if no-one knows off the top of their head).

I think we should disable the cm updater before requesting pull of a working device tree. I also think it would be well worth looking to see if we can integrate loki within cm recovery. ie autopatch on flash to boot/recovery partitions.
[AT&T Samsung Galaxy S 4 Android Development] 02busa:
Thank God, just figured out what was wrong... I had enabled "Extra gain in voice calls" under the Advanced Settings menu.. I just disabled it and it's working fine now. :D

---------- Post added at 02:05 AM ---------- Previous post was at 02:03 AM ----------

Set Network Mode to LTE/GSM/WCDMA in order to get LTE
[AT&T Samsung Galaxy S 4 Android Development] sam3000:
Sure but that won't fix it in the device tree which is where it needs to be done. We want a prop or overlay fix.
[AT&T Samsung Galaxy S 4 Android Development] 02busa:
Gotcha, My fault. I skimmed over your post quickly.. Regardless, Thanks for trying to help get the ball rolling with development.:highfive:
[AT&T Samsung Galaxy S 4 Android Development] eyi:
Works great. Thanks!!!

EDIT: There seems to be some lag when scrolling homescreens, but it comes and goes.
[AT&T Samsung Galaxy S 4 Android Development] jjgrantham:
I'm confused guys sorry - are you saying 4G LTE is

not

working on this rom??
[AT&T Samsung Galaxy S 4 Android Development] iSaint:
Read the last line in the op
[AT&T Samsung Galaxy S 4 Android Development] jjgrantham:
Yeah I read that but some posts above me had me confused. Thanks.
[AT&T Samsung Galaxy S 4 Android Development] romracer:
Try adding this to system.prop (or build.prop on the device):

# Default to LTE, GSM/WCDMA Network Mode
ro.telephony.default_network=9

Assuming that works, then you can change the options in the network mode menu. The overlay bit is (overlay / packages / apps / Phone / res / values / network_mode.xml):

<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2007 The Android Open Source Project

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->

<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
<!-- Mobile network settings, network mode choices for a device supporting GSM and LTE [CHAR LIMIT=25] -->
<string-array name="preferred_network_mode_choices_lte">
<item>LTE, GSM/WCDMA</item>
<item>GSM/WCDMA</item>
<item>GSM only</item>
</string-array>
<string-array name="preferred_network_mode_values_lte" translatable="false">
<item>"9"</item>
<item>"3"</item>
<item>"1"</item>
</string-array>
</resources>

I'm not sure you would need the overlay if the menu already has the right options and is just defaulting to the wrong one. I'm on call for a few more hours so I won't be able to flash CM10.1 on my device just yet to test myself. Please let me know though!
[AT&T Samsung Galaxy S 4 Android Development] shabbypenguin:
thats going to be in the next version of oudhs recovery
[AT&T Samsung Galaxy S 4 Android Development] greenzone560:
I was gonna do this today :) thanks for saving me time!
[AT&T Samsung Galaxy S 4 Android Development] yeahmann:
Damn. No NFC yet.

Anybody know of a way to take widescreen photos?

Any way to get the Play Store to stop blocking Galaxy apps like WatchON as incompatible? Or where can I get the latest WatchOn? Does the IR work?
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
Haven't tried NFC, but wouldn't surprise me if it didn't work yet.

No way that I have found to take widescreen photos outside using panoramic mode.

If WatchON is a Samsung Galaxy-only app, it won't be available from Play Store as you no longer have a Samsung Galaxy OS.

IR Blaster or any additional Samsung hardware will not function without a Samsung Galaxy OS.
[AT&T Samsung Galaxy S 4 Android Development] zaures:
No to everything
[AT&T Samsung Galaxy S 4 Android Development] JJ5150:
It installed flawlessly, but in my haste I forgot to DL the Gapps, Gotta start over... but it works, and works well.
[AT&T Samsung Galaxy S 4 Android Development] sam3000:
This was all that was needed (verified by doing a factory reset). Thanks for the pointer!

https://github.com/sam3000/android_...mmit/6d5c44e70eb621c5a0cb05b73e9f3f8144d4325e
[AT&T Samsung Galaxy S 4 Android Development] plwalsh88:
romracer is a genius, isn't he? The best.
[AT&T Samsung Galaxy S 4 Android Development] RicoStang:
Ugh this is killing me. I love CM10 and I've used it forever, but I don't think I wanna go away from Slim Bean now. Decisions decisions...:confused:
[AT&T Samsung Galaxy S 4 Android Development] yeahmann:
Okay so I'm taking widescreen pics with Camera JB+ from the app store. The WatchON app "works." No IR so it's just a TV guide with a non-functional remote.

Presumably the Google Edition will include Photosphere and NFC with Google Wallet so we'll probably get those working eventually. I wonder what will happen to the IR though. WatchON is the only app that uses it and presumably Google Edition won't come with it.
[AT&T Samsung Galaxy S 4 Android Development] Scarchunk:
Hey guys here's a link to the 5/24 nightly with the appropriate changes for our device. Updated the OP with the newer link. I built this because there were quite a few interesting changes, including some that seem to deal with the BT audio issues.

http://10.1.cmxlog.com/?device=jfltecan

Also I corrected the SGH-I337M reference and added the LTE build property that romracer suggested. Confirmed working. Thanks romracer.

https://truck.it/p/aELheGFdu8

I'll probably keep posting updated builds whenever I build for myself until an official thread is opened.

EDIT: Not sure why from the changelog, but this build definitely seems smoother. Course I'll need to give it some time. Built this at work during lunch and haven't had a ton of time with it.
[AT&T Samsung Galaxy S 4 Android Development] JJ5150:
Where is the Gapps download for this rom?

Sent from my Super Smooth SAMSUNG GALAXY S4
[AT&T Samsung Galaxy S 4 Android Development] Scarchunk:
Same place as always

http://goo.im/gapps
[AT&T Samsung Galaxy S 4 Android Development] sam3000:
http://goo.im/gapps
[AT&T Samsung Galaxy S 4 Android Development] JJ5150:
thanks guys, I'm new to CM10.1

Sent from my Super Smooth SAMSUNG GALAXY S4
[AT&T Samsung Galaxy S 4 Android Development] Scarchunk:
Why does everyone seem to think the Google Edition won't have the IR blaster? IR blasters are becoming more common on phones and Samsung would have to make a new model sans IR just for Google. I think it's more likely that the Google edition will be identical except software, which would be great for hardware support in CM.
[AT&T Samsung Galaxy S 4 Android Development] yeahmann:
If Google Edition will be identical except software, that could mean no IR support. The only software to support it is Samsung's WatchON.
[AT&T Samsung Galaxy S 4 Android Development] rodger-sp:
Does this have the Bluetooth problems?
[AT&T Samsung Galaxy S 4 Android Development] Scarchunk:
There's other software besides WatchON:

https://play.google.com/store/apps/...t#?t=W251bGwsMSwyLDEsImNvbS5yZW1vdGVmYWlyeSJd

That means there must be documentation out there somewhere on the IR hardware in our phones
[AT&T Samsung Galaxy S 4 Android Development] Scarchunk:
Don't know, can you try it out? There were quite a few commits that referenced Bluetooth fixes. I don't have a BT headset to test with
[AT&T Samsung Galaxy S 4 Android Development] ksbarnz:
I tested it out and my device will connect however you cannot hear call audio. Good to know it sounds like this could be fixed in an upcoming release.
[AT&T Samsung Galaxy S 4 Android Development] _Dennis_:
Samsung Remote by Touchsquid works to. May want to search xda or play store before making claims.

I don't have CM10.1 installed, I assime it wont work there do to drivers but it works on Stock ROMs, along with other remote apps.
[AT&T Samsung Galaxy S 4 Android Development] ralliart2k4:
I think something is seriously wrong with whatever kernel is being used here. On mostly stock rom, I'm seeing the following specs in Quadrant:

12690 on the stock rom

CPU 40584 Mem 11881 IO 8246 2D 501 3D 2238

On CM10.1

6509 total

CPU 15274 other specs similar
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
I'm seeing an odd issue with Bluetooth reporting taking up 80% of the battery, but Bluetooth is not turned on. I even turned it on, then back off again to make sure it was off.

Anyone else seeing this?
[AT&T Samsung Galaxy S 4 Android Development] Scarchunk:
Just got similar results in quadrant. Guess I hadn't done anything too cpu intensive to notice. Unfortunately it's because I'm just taking the Canadian kernel and running loki against it, then fixing the build.prop and updater-script. :( I'm no dev, just doing it for fun and sharing. We'll probably have to wait for an official release to get any real fixes.
[AT&T Samsung Galaxy S 4 Android Development] eyi:
I am seeing the same. 79%.

Also, I don't think the device was recognizing my stock headset/earphones in call. That was for the first build. Will try again after installing new nightly.
[AT&T Samsung Galaxy S 4 Android Development] Scarchunk:
Just checked tasks aokp thread and I guess people are getting similarly low quadrant scores over there. Weird. Mine was around 7200 total.

Sent from my SGH-I337
[AT&T Samsung Galaxy S 4 Android Development] Scarchunk:
My usage said 80% and 49 days usage right after rebooting from installing the update. Reporting must be borked due to the BT commits.

Sent from my SGH-I337
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
I don't notice battery life decreasing any because of it, and BetterBatteryStats doesn't detect anything weird. It must be a visual bug in the reporting. I hope they take care of it in the next nightly.

By the way, I want to thank you very much for converting nightlies over to AT&T for us. To keep the trend going, if you want a break please feel free to message me your procedure and I'll take over.
[AT&T Samsung Galaxy S 4 Android Development] lordpelvis:
+1

My car stereo works with music but not phone audio. Same problem with AOKP. Otherwise good ROM. Not sure why quadrant scores were lower.
[AT&T Samsung Galaxy S 4 Android Development] geokhentix:
Small issue but...the dark theme in mms doesn't work. :(
[AT&T Samsung Galaxy S 4 Android Development] ralliart2k4:
And thanks for your work on it!
[AT&T Samsung Galaxy S 4 Android Development] SysAdmNj:
So do you guys recommend this rom? I just installed TWRP, thats all I need to install this right?

Also, not so much concerned about the lower quadrant scores, but is it faster than the stock rom from what you guys have noticed?
[AT&T Samsung Galaxy S 4 Android Development] spectrumfox:
I recommend CM over Task's AOKP simply because it has the option to customize the hardware buttons on the GS4.

Yes, it appears to be much faster than stock ROM. Battery life is better too. And yes, if you've installed Loki'd TWRP, then that's all you need to apply this. Apply it the same way you would regular CM 10.1 and don't forget the Gapps.
[AT&T Samsung Galaxy S 4 Android Development] romracer:
NFC support coming in tonight/tomorrow's builds for jf devices. I think I've worked out my build issues and I've got a jflteatt building now from the ground up. I'll share my results if they're favorable.
[AT&T Samsung Galaxy S 4 Android Development] sam3000:
Fwiw, NFC support was pushed to jf-common in cm earlier today.

Edit: no-matter, I think that's what you were saying. Anyway, NFC seems to work, which is nice.
[AT&T Samsung Galaxy S 4 Android Development] SysAdmNj:
So far so good. Not too sure about battery life, I'll know better by tomorrow night.
[AT&T Samsung Galaxy S 4 Android Development] sholsten:
I installed this and I couldn't hear anyone on the phone and nobody could hear me. I had to switch over to Slim.