yashsingh1/xdaforums huggingface dataset:
[AT&T HTC One (M8)] thunderdome116:
Yeah I honestly doubt it is an issue with the ROM or build seeing that I have been on 3 different firmwares and 3 different ROM bases with the identical situation. Interestingly it appears to work after a dalvik cache wipe or TWRP restore from backup for a single reboot. After that it loses connection again and will not connect via 4G to Google Services. Something that is getting rebuilt in the cache upon reboot has to be causing the issue.

I will keep you posted on what happens with Google. They ran me through a bunch of troubleshooting then told me to factory reset and get back to them so I could talk to tier 2 support.
[AT&T HTC One (M8)] trailrunnerx:
#annoyed

I'm kind of pissed right now, my LTE issue has been persistent but I'd been reading on this thread and just not had enough time to s-off and flash the required sections as another user had success doing this. Tonight I finally had a while so I attempted this well I couldn't even get s-off through firewater so what's my option, (says HTC patched) to pay the $25 for the other option? Man I'm so annoyed at HTC this being a "Developer Edition" phone and can't even flash custom firmwares/kernels. Hell at this point I'd be happy if it just worked right. I even tried restoring to an earlier recovery (2.22 I think and downgraded to 4.3 but still no dice). Looks like I may be selling this phone and getting one that works as it is supposed to. I definitely have quite the poor taste left in my mouth by this HTC experience. I love the aesthetic and performance of the phone but I don't know if I'd buy another. So lame!
[AT&T HTC One (M8)] redpoint73:
Since you have the Dev Edition, you should just be able to return to stock ROM and recovery and get the OTA to 4.4.4 and be on the proper firmware.
[AT&T HTC One (M8)] Thela7:
Hello everybody,

I have an m7 and using AT&T. Changing the mtu size seems to temporarily fix this.

http://xdaforums.com/showthread.php?p=56605666

Sent from my mobile.
[AT&T HTC One (M8)] thunderdome116:
Can confirm this fixes my issue!
[AT&T HTC One (M8)] Wonders_Never_Cease:
Att MTU should be 1410.
[AT&T HTC One (M8)] Thela7:
Hi. Is there any reference on being 1410?

I was using ping the other day to determine it and it was higher than that.

Thanks.

ping -c2 -s 1437 google.com

Sent from my mobile.
[AT&T HTC One (M8)] Wonders_Never_Cease:
The mtu they use in all ROMS is 1410.

From build prop of latest att rom...

ro.ril.oem.ecclist=911

ro.ril.enable.a52=0

ro.ril.enable.a53=1

ro.ril.enable.dtm=0

ro.ril.gprsclass=10

ro.ril.hsdpa.category=14

ro.ril.hsupa.category=6

ro.ril.hsxpa=4

ro.ril.fast.dormancy.rule=2

ro.ril.att.feature=1

ro.ril.disable.fd.plmn.prefix=23402,23410,23411,23420,23594,27202,27205

ro.ril.enable.sdr=0

ro.ril.enable.gea3=1

ro.ril.enable.ucsq=2

ro.ril.set.mtusize=1410

ro.ril.enable.r8fd=0

ro.ril.disable.cpc=1
[AT&T HTC One (M8)] Thela7:
Thank you! Do you or anyone have the latest m7 at&t stock build.prop so I can compare it to mine?

I'll add that ro.ril.set.mtumax line meanwhile.

Sent from my mobile.
[AT&T HTC One (M8)] PhillyFlyer:
How do you change the MTU size?
[AT&T HTC One (M8)] Thela7:
I explain how I did it in the link I'm quoted in your post. This is a temporary solution, and it has to be performed every time the problem arise.

My previous post seems to be a better solution.

I'll try to write something better when I get home. ^_^

Sent from my mobile.
[AT&T HTC One (M8)] trailrunnerx:
Hmm

For two days now I haven't been having any LTE connectivity issues. I ended up keeping root and TWRP and flashing a 4.4.4 Nandroid backup because I couldn't OTA. It was still giving me issues at that point but who knows maybe one of the recent play store updates somehow fixed the bug? Honestly I don't have a ton of time to troubleshoot so I just jump on/try hints in between homework and my two jobs and trying to have a bit of a social life. Honestly because there was a work-around (disabling LTE) in my network settings, it hasn't affected me using the phone but I like things to work 100% obviously. I really like the HTC One m8 it's so much better than the iPhone 5 it replaced. Thanks for all the support this community provides!
[AT&T HTC One (M8)] Thela7:
Day 2: after adding that line in build.prop, the MTU stays as 1410, even after reboots. And Google services are working fine.

How to:

# adb shell
su
# remount system as rewritable.
echo "ro.ril.set.mtumax=1410" >> /system/build.prop
# reboot
# profit

Or using Root Explorer, edit/add that ro.ril.set.mtumax line, and reboot.

PS: I still have muted calls, tho.

Sent from my mobile.
[AT&T HTC One (M8)] kikokazuma:
These problems you've been experiencing with SSL on AT&T should be clear now. Patches were implemented the past two nights to correct assembly problems for packets that exceed 1500 bytes. You'll notice the problem has disappeared.

HOWEVER

As long as MTU is higher than 1430 (most stock devices cruise around 1410 - 1430 is the edge we don't want to cross) fragmentation is likely and can cause a bit of latency or lowered throughput.
[AT&T HTC One (M8)] trailrunnerx:
huzzah

I'm really happy that this issue is fixed, however AT&T Customer Support left a LOT to be desired during this issue. Their game plan was first to scold me for buying an unlocked device, then scold me again for daring to touch the carrier setting menu, then request I try simple diagnostics that I'd already tried. They then blamed Google and HTC for the issue. I actually missed something in that there was an issue with all SSL connections not just Google services because apparently I only regularly attempted to connect with Google, though I don't remember having an issue with my bank's website. Anyway thanks for the heads up I dealt with everyone from my spouse to my grandmother telling me it was my fault for buying a used phone lol.
[AT&T HTC One (M8)] kikokazuma:
Sorry to hear that, man.

To be honest, this kind of issue is miles beyond the capabilities of a customer service rep. This is something that required massive resources to detect, let alone develop a patch to implement and fix. We're talking labs here.

Not saying it's your fault at all. But AT&T was definitely working hard on this for a while, if it helps.

Oh and I mentioned SSL because HTTPS can tack onto the payload to exceed 1500 quite easily. But anything exceeding 1500 bytes would've broken in this situation.
[AT&T HTC One (M8)] wannabegt4:
Finally! I've been stuck without LTE for a few weeks now. Using build.prop editor and setting ro.ril.set.mtusize=1410 got it working again. I did the other changes in Wonders_Never_Cease post but I'm not seeing any improvements over just changing the MTU size. Thanks!
[AT&T HTC One (M8)] Wonders_Never_Cease:
You wont see improvements really,those build prop lines I posted were just for referrence because someone decided to question where I got the info I suggested. Unless changed to a rom specifically customized for att youll not see differences. 99% of the euro based roms are not set up for att's network changes being implemented.
[AT&T HTC One (M8)] wannabegt4:
Good to know. Thanks.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] mikebz5:
There is only 1 thing I hate about my Note 4. The Flipboard Homescreen! Can it be removed or replaced with something I actually want?

I don't even see it listed as an app anywhere.

No root here yet.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] jauger:
Press your homescreen, then Home Screen Settings, uncheck Flipboard Briefing
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] mikebz5:
You are a God! Thanks!
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] photoshopgeek:
Also, you could use another launcher. My fave right now is Google Now Launcher because I use Now quite a bit. Apex and Nova are good as well.
[Moto 360] Kokanee483:
Check it out, I signed up as a backer for this;

https://www.kickstarter.com/project...dapters-for-moto360-smartwatch?ref=nav_search
[Moto 360] FusionTechFTS:
I know there is at least one other thread with this info. Should be cool though.
[Moto 360] akellar:
And another that was closed http://xdaforums.com/moto-360/accessories/steelconnect-m-adapter-moto-360-t2898908
[Moto 360] Zhou86:
This other one is much more active imo: http://xdaforums.com/moto-360/general/strap-adapter-moto-360-t2910912
[Moto 360] Diamondback:
Please use the above thread for any future discussion, we don't need two of them :)
[Moto X Q&A] djibril13:
Hello I purchased a new Moto x and recently I observed a strange spot on screen like dead pixel. When I look the screen from different angle from above for example it doesn't showing up. So it's the screen or the factory screen protector?
[Moto X Q&A] Nemosfate:
Take off the screen protector and see.

root, roms, and themes.. oh my!
[Moto X Q&A] djibril13:
I can't because I don't have another one. I just asking if it is possible to have such spots because of the protector.
[Java for Android App Development] alex-p690:
Hello guys,

I've developed an app to read business cards so this means I'm using the phone's built-in camera to take pictures store and edit them. I've encountered many problems with OutOfMemory on my test device (Nexus 5), wich i managed to solve by passing some BitmapOptions when i decode it and downscaling it to 1224x1632 wich is the ideal resolution for keeping the memory usage low and still getting high performance from OCR. I've noticed that i still get a lot of crash reports from Samsung flagship devices like GS 4/5 or Note 2/3. I've tried loading a 20 MP image from gallery on my phone and it didn't crash and worked as expected...I even tried on an Xperia Z1 wich has an 21 MP camera and my app worked fine and i couldn't get it to crash.

So here's my question: how could I avoid these OOM errors on all devices, specifically on samsung ones?

BTW, I've attatched the crash report statistic from developer console.
[Galaxy S 4 i9505 Android Development] wappla1911:
Android L Port for Samsung GT-I9505 Galaxy S 4

based on ISF's Project! http://xdaforums.com/member.php?u=4581600

What is working?

What has been done until now?

What is needed for further development?

Installation Instructions

Credits

XDA:DevDB Information

Android L PORT , ROM for the Samsung Galaxy S 4

Download

Changelog

XDA:DevDB Information

Android L , ROM for the Samsung Galaxy S 4

Contributors

wappla1911, ISF, sykopompos

ROM OS Version: 2.3.x Gingerbread

Based On: GPE 4.4.4 From Source

Version Information

Status: Testing

Created 2014-10-21

Last Updated 2014-11-10
[Galaxy S 4 i9505 Android Development] chkoon:
First,when download link come, i give try,thanks
[Galaxy S 4 i9505 Android Development] wappla1911:
I'm uploading...
[Galaxy S 4 i9505 Android Development] devilyuri:
Only booting process works at the moment :/
[Galaxy S 4 i9505 Android Development] wappla1911:
Yes i don't find any kernel :(
[Galaxy S 4 i9505 Android Development] devilyuri:
Why don't talk with a kernel developer like ktoonsez,alucard or googy?
[Galaxy S 4 i9505 Android Development] wappla1911:
I don't know if the rom works... the link is in about 10 min. online
[Galaxy S 4 i9505 Android Development] egemen1903:
screenshot or video coming?
[Galaxy S 4 i9505 Android Development] Arnibarniboy:
How can he post a screenshot when the rom doesn't even boot? :p

I hope a kernel Developer can make a working kernel for your rom. I will follow this thread now and when the rom can boot, i will also testing it :D
[Galaxy S 4 i9505 Android Development] wappla1911:
I also hope :)
[Galaxy S 4 i9505 Android Development] wappla1911:
Link

Link is online!
[Galaxy S 4 i9505 Android Development] egemen1903:
only 293 mb :confused:

---------- Post added at 04:14 PM ---------- Previous post was at 03:48 PM ----------

come on, do not return yet?
[Galaxy S 4 i9505 Android Development] pumajoe:
I have bootloop i use the newest cwm touch. Can any Help?
[Galaxy S 4 i9505 Android Development] Razov:
I think u must read a little more, the rom doesn't work, we need a custom kernel to make it functionally.
[Galaxy S 4 i9505 Android Development] chkoon:
the way to bootanim is good so maybe,odex or font issue to boot,or build prop,updater-script....Hope somone help to this ROM"just" boot
[Galaxy S 4 i9505 Android Development] wappla1911:
Yes i hope i think the first way is a custom kernel :)
[Galaxy S 4 i9505 Android Development] magikmichael:
Subscribed to this topic to see where it goes!
[Galaxy S 4 i9505 Android Development] chkoon:
of corse :) , android L is odex not slim(didn't see odex file in farmwork port),maybe odex base help
[Galaxy S 4 i9505 Android Development] wappla1911:
hmmmm... Which ROM would you take?
[Galaxy S 4 i9505 Android Development] DeathHawk:
nice i hope you will make that the rom booting into the system

when this done i will make video to push you thead a lot :)
[Galaxy S 4 i9505 Android Development] GrStorm:
Well, im going to sleep, tomorrow i will try some more. :D
[Galaxy S 4 i9505 Android Development] nadejo:
maybe some people should revert their file system back to ext4 since alot plople used f2fs
[Galaxy S 4 i9505 Android Development] BakedTator:
I haven't changed my filesystem at all...I'll try it though...could that be why it keeps telling me that it failed to execute the updater binary?

Just checked...I'm running ext4
[Galaxy S 4 i9505 Android Development] bhairavp:
i9505..
[Galaxy S 4 i9505 Android Development] wappla1911:
Hey guys! I take the link offline because it don't work, today i test my new rom and then i give it online... Have a nice day! :)
[Galaxy S 4 i9505 Android Development] nmarrufo:
Are you going to try Maltahl's kernel?
[Galaxy S 4 i9505 Android Development] Maltahl:
We have tried the kernel but so far no results that takes us beyond the loading screen.
[Galaxy S 4 i9505 Android Development] wappla1911:
Because the Ramdisk isn't correct i think -.-
[Galaxy S 4 i9505 Android Development] JohnnyBlack10:
Nope....no kidding
[Galaxy S 4 i9505 Android Development] Maltahl:
Unless you got anything to contribute i suggest you stop mocking us.
[Galaxy S 4 i9505 Android Development] nadejo:
could it be something like the surfaceflinger causing the problem?
[Galaxy S 4 i9505 Android Development] Ketelbinie971:
No OS

TWRP will tell you after flashing that there is no SO installed, but there is. It is just Google zip format is different from KitKat.
[Galaxy S 4 i9505 Android Development] marnox:
No luck unfortunately:( Even with modified boot.img!

Any help much appreciated! ;)
[Galaxy S 4 i9505 Android Development] wappla1911:
Who can build the boot.img? :)
[Galaxy S 4 i9505 Android Development] GrStorm:
Well, to build it we would need the ramdisk of the kernel that Maltahl made, the files he uploaded is just the zImage(boot.img-kernel) and modules, we need the correct ramdisk.
[Galaxy S 4 i9505 Android Development] wappla1911:
Yes i can build the boot.img but i need a correct ramdisk
[Galaxy S 4 i9505 Android Development] rvnieuwh:
Oeps. :silly:

Sorry 'bout that (fellow Dutchy). :highfive:
[Galaxy S 4 i9505 Android Development] mattia9631:
How is going the development?
[Galaxy S 4 i9505 Android Development] GrStorm:
Well, we need the ramdisk, without that we can't build the boot.img properly.
[Galaxy S 4 i9505 Android Development] mattia9631:
Is there some way to get that?
[Galaxy S 4 i9505 Android Development] GrStorm:
So, i talked with Maltahl and he said that the files he uploaded were the only one that came out when he made the kernel, so i made a boot.img using the GPedition kernel ramdisk, let's just hope that it works.

here is the link: https://mega.co.nz/#!4RZhSJiS!zBOPwI67zobZ5-9Otqvx5mGky18h5hX_VXBzeERNhi8

I added some instructions in the zip.:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
[Galaxy S 4 i9505 Android Development] Jaycobe:
:(

It doesnt work for me. Stuck on Galaxy S4 Logo :(
[Galaxy S 4 i9505 Android Development] GrStorm:
So the GPedition ramdisk doesn't work with this kernel
[Galaxy S 4 i9505 Android Development] jose5624:
Me tooo omg crazzy to flash :crying:

---------- Post added at 07:04 PM ---------- Previous post was at 06:59 PM ----------

Hard work for developers dont give up :good:
[Galaxy S 4 i9505 Android Development] devilyuri:
GPedition ramdisk contains all the files compatible with kitkat so they won't work on Lollipop
[Galaxy S 4 i9505 Android Development] sykopompos:
You know there was all kinds of changes in the ramdisk in L, right? Especially the framework loading paths in initmeviron.rc, the init.rc, the ueventd and all that other good stuff

Sent from my LG-D851
[Galaxy S 4 i9505 Android Development] malybru:
Mod Edit

Thread cleaned

Please do not ask for ETA's

I've changed the title to [R&D][DEVS ONLY]

So , unless you are a developer actively taking part in this thread , your posts may get deleted.

malybru

Forum Moderator
[Galaxy S 4 i9505 Android Development] GrStorm:
So, the ramdisk from the aosp kernel for the nexus 5 would work? im really do not understand these things much, just trying to help:)
[Galaxy S 4 i9505 Android Development] xXchrizhurtyXx:
Doesn't hurt to try. Anything done is one step closer to achieving success. From what I understand the RamDisk has properties like init.rc so trying to move it from the Nexus 5 which has all the Android L properties, should work theoretically.
[Galaxy S 4 i9505 Android Development] GrStorm:
Well, i just packed a bootimg with the nexus 5 ramdisk for lollipop, will test it later, here is the link :

https://mega.co.nz/#!JY4BVRJT!BvGw0aWbMZ-TyWyK22_JLcD19lgM1LLiRvqI6yOSFgI
[Galaxy S 4 i9505 Android Development] xXchrizhurtyXx:
Which base rom is everyone trying to boot?

Is it the OP rom or is there another one that everyone has been using?
[Galaxy S 4 i9505 Android Development] GrStorm:
Op rom
[Galaxy S 4 i9505 Android Development] xXchrizhurtyXx:
Okay downloading rom now, will let you know how it goes.

---------- Post added at 08:22 PM ---------- Previous post was at 07:53 PM ----------

Flashed and once again stuck on the Galaxy S4 screen.
[Galaxy S 4 i9505 Android Development] dawgdoc96:
Didn't flash for me either...
[Galaxy S 4 i9505 Android Development] sykopompos:
You need to have it tuned to your device. A lot has changed since kk

Sent from my LG-D851
[Galaxy S 4 i9505 Android Development] echma:
Perhaps we can ask this dev for ramdisk and other infos... He tried to port it to I9500 as you can see: http://xdaforums.com/galaxy-s4/general/android-l-discussion-cm12-aosp-builds-t2936556
[Galaxy S 4 i9505 Android Development] AntaresOne:
i9500 and i9505 are totally different. Even the camerawrapper for camera sensor is different to make the idea...

And a ramdisk took from another device can't work, init scripts are different even if same hardware.

Btw, if could be interesting for you, I'm working on Lollipop (i9505). I have AOSP built from source, currently there are init errors in kmsg.

Ramdisk stuff needs to be updated (tomorrow) to boot.

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Android Development] BakedTator:
Looking forward to this...I'm using the jflteusc and I would be more than happy to test and see if your ROM will work for my phone...are there any major differences between my phone and the i9505?
[Galaxy S 4 i9505 Android Development] AntaresOne:
Absolutely nothing except RIL blobs. This works on any jflte, including verizon and at&t variants.

RIL is surely broken by the way, since we don't have a compatible SamsungQualcommRIL source to be used with new Android release

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Android Development] GrStorm:
Cyanogenmod started their works on CM 12 , and i noticed they updated the device tree :

https://github.com/CyanogenMod/android_device_samsung_jf-common/tree/cm-12.0

So, now i think we can build for the i9505 directly from source :)
[Galaxy S 4 i9505 Android Development] nadejo:
i hope [MENTION=4899086]alucard_24[/MENTION] creates a kernel when cm12 is released :)
[Galaxy S 4 i9505 Android Development] GrStorm:
Well, the Cyanogenmod team is going all in with the CM 12 in their gerrit, i think that by the end of the month the first nightlies will go out, but certainly we will have a UNOFFICIAL build before that ( i hope):p
[Galaxy S 4 i9505 Android Development] AntaresOne:
Don't look cm-12.0 branch of jf-common tree, some important things to boot Lollipop aren't yet done.

By the way, I booted Lollipop on my i9505. :victory:

There are problems with display driver that cause weird issues, I'm trying to fix them now. :cool:

If you want, you can follow me on Twitter, I share any progress there.
[Galaxy S 4 i9505 Android Development] AntaresOne:
Will support any jflte device as other ROMs, don't worry. :)
[Galaxy S 4 i9505 Android Development] malybru:
Surely the point of this thread is to share such work...
[Galaxy S 4 i9505 Android Development] BakedTator:
Do you know of the the ril works yet?

Or does that come after the display driver is fixed?
[Galaxy S 4 i9505 Android Development] chkoon:
Any download link?please share it. let we see what we can do whise bootable base
[Galaxy S 4 i9505 Android Development] AntaresOne:
I don't understand if you're saying "well done" or "it's not the right thread" :confused:

RIL will be broken until doesn't come a SamsungQualcommRIL class Lollipop-compatible
[Galaxy S 4 i9505 Android Development] GrStorm:
Well, how did you do it ? Did you compiled it?if so what device tree did you use?

I just have one thing to say, you're awesome man, great work!!!!!!!
[Galaxy S 4 i9505 Android Development] malybru:
Yes,well done. :good:

Please post your findings/links/requirements here on XDA ,so that other users can benefit/try/test it out as well.

The whole point of this thread is to move this project forward.

Users should not have to go to twitter to find out what is going on.

:)
[Galaxy S 4 i9505 Android Development] BakedTator:
Are we going to have to hack one or do we wait until we get a google play edition of the ROM from Samsung?
[Galaxy S 4 i9505 Android Development] AntaresOne:
It's compiled from source, using CM11 kernel and modified CM11 device tree (I'll push sources on GitHub as soon as I get an usable build)

CM guys will do it...:)

---------- Post added at 17:03 ---------- Previous post was at 17:01 ----------

Thanks malybru :) :highfive:

I will surely share everything here :)
[Galaxy S 4 i9505 Android Development] tkruijer:
I think Malybru wants you to share the work you've done so far, so other devs can benefit from your development.

But I thinks that's totally up to you, and not for anyone else to decide :D
[Galaxy S 4 i9505 Android Development] noooooo:
Il primo a bootare lollipop su s4 è un italiano,pazzesco! complimenti!

The first succeded in booting lollipop on s4 di an italian, amazing!
[Galaxy S 4 i9505 Android Development] GrStorm:
So the unmodified version of the CM11 kernel works?
[Galaxy S 4 i9505 Android Development] AntaresOne:
Yep, it's needed only a little modification in defconfig, enable loadable modules support.

# CONFIG_MODULES is not set

to

CONFIG_MODULES=y

Otherwise will break the build process

EDIT: I forgot to say that the kernel from CM11 sources works, but needs to be compiled through Lollipop's build system. There are some other changes required (in device tree, ramdisk part [the rootdir folder]) to build L-compatible kernel
[Galaxy S 4 i9505 Android Development] abdo jouma:
Guys sorry but just asking :)

So now its booting ? Now we have a better chance to get more stable lollipop builds ?

Its aosp or cm ?

Thanks guys and sorry again :)

أرسلت عن طريق تابتالك من galaxy s4
[Galaxy S 4 i9505 Android Development] AntaresOne:
The one into picture is CM12, but I reached the same with AOSP 5. :)

At the moment, official CM12 is almost "pure" AOSP (i.e. a few changes only)
[Galaxy S 4 i9505 Android Development] AntaresOne:
I'm just pointing to an usable build for now (even if with broken RIL and other bugs that will be alive). :)

My CM12 will be unofficial, and will surely be available an official one, about AOSP... If boots, it's mine :)

Finalmente eh? :p

Finally? :p
[Galaxy S 4 i9505 Android Development] AntaresOne:
As soon as display driver works better and ROM is usable :)