yashsingh1/xdaforums huggingface dataset:
[Sprint  Galaxy Note 4 Original Android Development] GROOVYJOSHCLARK:
That sounds like to me, all you are doing is registering onto the correct /CDMA network while on TouchWiz. Do you know what I mean when I say to set to /CDMA from within AOSP (its the equivalent to registering on TW), well almost.

Before you throw your phone against the wall. Do this:

on the phone dialer, hit *#*#4636#*#* and the testing menu will open a few moments later, switch the network to CDMA/auto PRL, give it a moment and test sending texts, I betcha it works. If it doesnt work, go back to the testing menu and turn off modem, then back on and make sure you are on CDMA /AUTO PRL.
[Sprint  Galaxy Note 4 Original Android Development] youssef7:
Will lte work? Because as soon as I turn on lte I remember sending txt mgs stop working... and thats not the way it always worked for me. I never had to toggle lte to send msgs
[Sprint  Galaxy Note 4 Original Android Development] GROOVYJOSHCLARK:
If you turn on LTE through the testing menu everything will work. After you get a steady connection to CDMA, texts will work and you will be on 3G. As soon as that is connected you can switch to LTE/CDMA /Auto PRL and you will flip to LTE and texts will work.
[Sprint  Galaxy Note 4 Original Android Development] youssef7:
Yea but after a reboot this doesn't stay right I have to do it again? My way works better then because you never have to do it again. You never touch anything again to work. You go to network operators while connected to wifi do that then you will register and your all done. I just don't understand how this even happened. Does google play services have anything to do with the phones network?
[Sprint  Galaxy Note 4 Original Android Development] GROOVYJOSHCLARK:
I know your process I used to do something similar before I figured out the issue.

Dont take this the wrong way, but your way doesnt seem to be working at the moment. At least this is the normal process for our model phone with AOSP and it keeps you from feeling like throwing it against the wall.

This has nothing to do with GAPPs, this is an issue with the AOSP released from CM bound to our devices. It is the way it registers to the wrong network.

Have you tried using LTE Switcher from the playstore? It is free and with a single click it opens the dialer menu. This is what i use.
[Sprint  Galaxy Note 4 Original Android Development] youssef7:
I use lte on and off in the pull down bar. Its in the setting you can add it with out an app. But also I'm very confused on exactly what's going on. Now it seems like everything is working before I even got home to mess with it lol. I flashed the rom again and now I have everything working. I just want to make sure this works forever. I don't want to reboot my phone and not be able to send msgs. I don't have time for that and I really hope that its back to normal.
[Sprint  Galaxy Note 4 Original Android Development] GROOVYJOSHCLARK:
Dude, we ALL want that. Its not going to happen anytime soon or maybe EVER with this version of AOSP.

The notification switch does nothing more that kick in LTE but not when you are on GLOBAL or the wrong network. When you use the testing menu or LTE Switcher this is actually instructing the phone to switch to the correct network.

It sounds like to me, you should stick with TW if you need it that badly and cannot use the testing menu. This is NOT something that is going to be fixed.

This is the life of using AOSP, there ARE BUGS.
[Sprint  Galaxy Note 4 Original Android Development] SirSparkles:
I just wanted to chime in and say, this ROM has been extremely stable for me. I've been running various nightlies for a handful of weeks now. I've been a CM fan for a few years on a few devices, and am truly shocked at the lack of reboots or freezes. Great stuff. Very stable.

On another note, I started getting the skipping bluetooth connection/streaming hiccup thing a few weeks ago. I was instinctively thinking it was just 'bad' bluetooth with the ROM, but troubleshooting and forum reading found an app as the culprit...GasBuddy. I contacted the app developer and let them know, that whenever their app was active, I'd get skipping bluetooth playback, and whenever it was forced closed, the issue went away.

So, if anyone gets the skipping bluetooth 'bug', just start freezing some apps with Greenify or do some ForceStops on apps you recently installed.

The only downsides I've found so far are:

1) Camera Issues - the stock ROM camera has a bit of lag and slowness, and I've had it freeze a few times

2) Thats It! (I am somewhat rural, so I don't get into LTE areas much, so I might not be experiencing the SMS/MMS issues on 3G/LTE crossover craziness)

I have about 200 apps installed, and stability is great (yes, I'm an app hound and use most of them often enough)

What are peeps experiencing with stock camera vs google camera vs other cameras with the ROM?

are they all laggy and freeze every so often? or mostly the stock? I might want to investigate trying out some other cameras.
[Sprint  Galaxy Note 4 Original Android Development] GROOVYJOSHCLARK:
It's been really stable for me to, I'm at about 150 or so apps with zero issues. Some newbies don't like the fact AOSPs have bugs, some that are workable, some aren't. But hey that's AOSP and thankfully it's available so we aren't forced into overbloated BS from the carriers.
[Sprint  Galaxy Note 4 Original Android Development] youssef7:
umm your wrong actually there duuuuude. I never had to switch and mine was always on global. I never had to do any weird lte stuff or reset anything unless I did something. Also the method you told me was a bad idea because for me because I cant go back to defaults... I'm just going to touch wiz for now
[Sprint  Galaxy Note 4 Original Android Development] GROOVYJOSHCLARK:
LOL ok buddy, rock on DUDE, whatever floats your boat. AOSP doesn't seem to be your cup of tea.
[Sprint  Galaxy Note 4 Original Android Development] SirSparkles:
Google Camera not working nice :(

fyi... I tried out Google Camera last night, it seemed to work, and was a little faster than the stock camera. However, this morning my battery had drained substantially. My first check was to go to Settings-Battery, and voila...the culprit. The first line items was a 'process' or something with the word 'camera' embedded in it. my bad on no screen shot or writing down the process/app name. I immediately uninstalled GoogleCamera, rebooted,and so far the process has not showed up, so I assume Google Camera doesn't play nice with this ROM for now... unless someone else is not seeing this?

Anyone tried any other cameras that work besides stock?

---------- Post added at 12:44 PM ---------- Previous post was at 12:34 PM ----------

Any chance I'm missing the newest release somewhere? I see only the most recent as v1.15 circa late September on the Plasma thread.

I'm itching to try the new one for battery life.

Being somewhat green with deep coding related to battery performance and kernels, is there the chance that custom kernels don't play nice with things like xposed 'Amplified' or 'Greenify' and might interfere with them? or is blocking wakelocks and hibernating 100% independent of kernel interaction?

I just installed v1.15 earlier today, and haven't noticed anything bad yet, but Trebuchet interaction seems faster/snappier, and the S-Pen vibrates upon exit....Sweet! *fingers crossed

off to tweak S-Pen integration...
[Sprint  Galaxy Note 4 Original Android Development] nivron:
Oh hi...

Just a teaser to show you all what I've been working on lately...

No, it's not fully functional. WiFi/Mobile Data/GPS (mostly)/SMS/Text works. Phone Calls/Exfat SD Cards do not. No, I don't know when it's gonna be 100% ready.

If I get it to a point where I'm ready for some more detailed testing, I'll put up more information on a post.
[Sprint  Galaxy Note 4 Original Android Development] GROOVYJOSHCLARK:
I am read to test whenever you post it!! I will test every aspect of the ROM so let me know when you are ready! AWESOME NEWS and thank you!
[Sprint  Galaxy Note 4 Original Android Development] G U C C I:
Can test as well!
[Sprint  Galaxy Note 4 Original Android Development] javskies:
im not sure if this is rom related but i have a new issue where my phone will only charge when off and very slowly at that. i tried searching and couldnt find info on the note 4 doing this. anyone experience this too?
[Sprint  Galaxy Note 4 Original Android Development] MarkEv0:
If you need more testing lmk, good luck building
[Sprint  Galaxy Note 4 Original Android Development] sekinger:
Is there a CM13 rom for our sprint note 4s that can be installed? I'd love to give it a whirl. Anyone have a link?
[Sprint  Galaxy Note 4 Original Android Development] GROOVYJOSHCLARK:
That's marshmallow OS which is not released yet
[Sprint  Galaxy Note 4 Original Android Development] SirSparkles:
I've seen/heard some ROMs not liking 128gb (vs 64gb) sdhc cards

Anyone been using a 128gb sdhc card with this ROM working nicely?

I'm under the impression that the stock TW can handle 128gb, but wondering if the ROM here might be a limitation before I go and blow a few bucks on an SDHC card. Additionally, I'm also under the impression that the hardware would be the limiting factor for read/write to the external sdhc card (and therefore a Class 10 card would be 'wasted').

I'm looking to upgrade my size storage (for more nandroid backups! and media)

thanks for a chime in, if you got one working for you.
[Sprint  Galaxy Note 4 Original Android Development] GROOVYJOSHCLARK:
All aosp variants of our devices unfortunately have this issue
[Sprint  Galaxy Note 4 Original Android Development] _newb_:
I've noticed a few irregular things about my current build of CM 12.1. I haven't updated it in a couple weeks, as I'm on the 11/05 build. Anyway, it's been running great, but in the last few days I noticed that my phone powers off on its own when it reaches about 30-35% according to the battery meter. Very strange. IIRC, early Android phones needed their battery stats reset on occasion when switching between ROMs.

Second thing I noticed is that my data connection seems to inexplicably drop on occasion, requiring me to reboot my phone. No big deal, really, until I want to send a picture message or something, and all I can get is the signal bar icon with a (1) next to it.

I will try updating to a new build; hopefully that fixes my issues. Everything is great so far. Photo quality on TW seems better, based on the little bit I used TW before finding an AOSP build. Boot time on my N3 with SlimKat (4.4.4.) was substantially faster...but apples and oranges there.
[Sprint  Galaxy Note 4 Original Android Development] GROOVYJOSHCLARK:
I would imagine it's due to Google's recent play store update.
[Design, Prototyping, UI, Graphics] kennyung6:
i am trying to develop a college app for my university!

Please Help me with any information on the type of Layout suitable for the below image and any other help or references to carry out this type of design
[Huawei Ascend Mate 2] GadgetStrutter:
If I go to Phone Manager > Power Savings > Energy Consumption I have a huge battery drain. I need help :(
[Huawei Ascend Mate 2] ArkAngel06:
I'd say pretty much everyone is experience a degraded battery after the update. It will probably have to be fixed though an update.
[Huawei Ascend Mate 2] kimtyson:
Oh. I see. I have heard that people are not happy with the battery in Lollipop. I haven't really experienced a change that I noticed.
[Huawei Ascend Mate 2] medwatt:
When you say a huge battery drain, do you mean the battery is not lasting as long as it did or you observed a very precipitous drop in battery over a short period of time?
[Huawei Ascend Mate 2] MikeyLee:
I have noticed a slight change in battery drain but its definitely not during cell standby.
[Huawei Ascend Mate 2] notoriouspk:
lollipop needs an update real bad ...cell standby is huge in battery stats ...17% in 4 hours without WiFi and data ..this is just ridiculous ...

chrome is another big battery hog ,ever since it was released.

its a shame Google still couldn't fix its drain caused from chrome while running in background .
[Huawei Ascend Mate 2] Moody66:
Go into settings and unchecked it. Should no longer run in background. Google has several issues right now draining battery. There are some work around. But only on cm roms.
[Huawei Ascend Mate 2] GadgetStrutter:
After i restarted my phone a couple times it seemed to have fixed the problem. I've also changed my microUSB cable and AC adaptor as well... since I noticed that they actually make a difference.
[Sony Xperia M] QA Bot:
Q&A for [firmware][c1904][15.1.c.2.8] ftf file download

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [firmware][c1904][15.1.c.2.8] ftf file download. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Sony Xperia M] kjinx01:
i couldnt fine ftf file for xperi a m dual indian version??
[Galaxy Tab S Q&A, Help & Troubleshooting] razholio:
The CM12.1 thread was closed reportedly due to GPL non-compliance by the CM12.1 maintainer for klimtwifi, but no other explanation or news on future development was posted. Nightlies continue to build, but I'm concerned that there won't be any future development. If anyone knows what's going on, I'd love to hear it. thanks.
[Galaxy Tab S Q&A, Help & Troubleshooting] Lightn1ng:
Just download them from the official website http://www.cmxlog.com/12.1/klimtwifi/
[Galaxy Tab S Q&A, Help & Troubleshooting] razholio:
um... yeah, I don't have any problems with downloading the nightlies or checking the commitlog, I'm just wondering

1. if the developer is still working on CM12.1 for klimtwifi and

2. how we can report/discuss issues we come across.

I've got 7/1 on my T-700 right now and I notice that while standby battery life is excellent, the CPU seriously eats through the battery when playing games. I think I drained it from ~95% -> ~25% in <30mins of playing 'abyss attack' for eg. I suspect it's an issue with the CPU governor, hotplug, or the GPU governor, but there may also be a workaround I don't know about.
[Galaxy Tab S Q&A, Help & Troubleshooting] Thuggins2086:
I'm using 7/14 right now and it's the best CM experience I've ever had on any device. My Motorola and LG phones always had issues, as well as my ex's Nexus. I'm curious though as to why the nightlies seem to have stopped at 7/14?

I hope we eventually get a "stable" version.
[Galaxy S6 Q&A, Help & Troubleshooting] sol_671:
Ok, I came across this and have no idea why there's 2 led settings. Does anything one have an idea which works better? I know the other one lights up the led when charging and using voice rec. But both seems to notify you with other things.
[Shield Tablet Q&A, Help & Troubleshooting] joshtb86:
im loosing free space on the internal sd card and no matter what i delete, cannot figure out how or where it went

anyone have any idea or similar expieruence?

its also causing issues, such as titanium backup wont back anything up, despite that i tell it to use the external sd (which has 32 gigs free)

edit - hmm, ive noted that im deleting/uninstalling apps, and manually deleting the files, but its not registering on the tablet that there is new free space from them. this is highly unusual
[Shield Tablet Q&A, Help & Troubleshooting] Frankenscript:
Are you fully stock? Rooted? Which version of OS?
[Shield Tablet Q&A, Help & Troubleshooting] joshtb86:
woops sorry

unlocked, rooted, most recent stock OTA with stock kernel
[Shield Tablet Q&A, Help & Troubleshooting] Frankenscript:
I wonder if it is really deleting the files or just hiding them. Can you try copying over from a PC a large file , check free space, delete the file, check space again, see if it frees it up? I'm thinking it is a weird permissions issue.

Marc
[Shield Tablet Q&A, Help & Troubleshooting] joshtb86:
not sure, tried delting files on the computer also, and no change

i did a factory reset.

i think this is some sort of serious issue
[Galaxy S6 Android Development] arter97:
This is for developers, willing to contribute in for fixing Xposed on 64-bit Samsung devices.

If you're just a regular user, please don't post on this thread.

Now that deodexing Android 5.1 firmware is possible, I went on porting Xposed to Galaxy S6 Android 5.1 with almost the same procedures that I've done with Sammy's Android 5.0, but now with AArch64 compilation.

I managed to fix core-libart.jar to match AOSP's style until the point where Zygote completely dies without complaining which functions are missing or malfunctioning.

Seems like Samsung has played around ART runtime even more with 64-bit devices.

(PS, deodex'ed firmware without installing Xposed's new files boots just fine without issues)

Built with GCC 4.9:

Logcat - http://pastebin.com/WXvryB0m

Tombstone - http://pastebin.com/pKzb47nm

Sources are available at https://github.com/arter97/android_art/tree/samsung-lollipop-5.1 and

modified core-libart.jar is at http://www.arter97.com/browse/tmp/core-libart.jar

Re-building ART runtime completely with Clang compiler has revealed slight more debugging info.

Clang tombstone - http://pastebin.com/Ngemxy4H

Seems like somewhere between artAllocArrayFromCodeResolvedRosAllocInstrumented and BuildArgArrayFromObjectArray is causing boot issues.

oatdump can get somewhat debuggable info but I've yet to find a relation with the crash.

https://code.google.com/p/android/issues/detail?id=173420

[MENTION=3562083]wanam[/MENTION] also reported the almost same issue on Android 5.0 - https://github.com/rovo89/android_art/issues/9

This issue also made me think that it actually might be the Exynos 7420 issue itself, and Samsung has implemented a workaround just for it,

considering there're some AArch64 erratum fix commits - https://github.com/arter97/android_art/commit/d07021b38087ca0e385ebf46dd1b78239ed702b2 & https://github.com/arter97/android_art/commit/c5d9beb95d2c392820048ca42f582e4a50a9ca4d

I'm still working on how to fix this annoying issue.

If you have any ideas or tips, please let me know.
[Galaxy S6 Android Development] arter97:
I'm having a hard time understanding if people can't see the very first paragraph on this thread.

No testers are needed.
[Galaxy S6 Android Development] malybru:
Mod Edit

Thread cleaned.

Please read people...

Thank you

malybru

Forum Moderator
[Galaxy S6 Android Development] wanam:
[MENTION=4898097]arter97[/MENTION] did you try the Cortex-A53 Erratum 843419 workaround in OatWriter? it is already included on the M previews, i tried to merge it with 5.1.1 sources but it seems it has some dependent commits.
[Galaxy S6 Android Development] arter97:
No, I didn't saw that commit until now.

I'll try that later :D
[Galaxy S6 Android Development] arter97:
I think grepping "64", "arm64", "AArch64", "Cortex" from Google's master branch's 'git log' might get us somewhere.
[Galaxy S6 Android Development] wanam:
That's what I did, but I found only the two erratums 843419 and 835769 that seems related to Exynos, the first one was merged on the stock toolchain, but I'm not sure if there is any explicit option to enable the fix on the compilation.
[Galaxy S6 Android Development] arter97:
Merged to "toolchain"?
[Galaxy S6 Android Development] arter97:
Huh, ok, seems like Samsung is at least not using 843419.

I can't get any 843419 related fixes on built binaries.

I can't say the same thing as 835769 as its change is so minimal that it'll be hard to determine just from the binaries.

I'll try to enable 835769 later.
[Galaxy S6 Android Development] wanam:
I'm talking about this: https://android.googlesource.com/pl....9/+/6a20db030e486326e70968612662938d12d86a7b
[Galaxy S6 Android Development] arter97:
https://gcc.gnu.org/ml/gcc-patches/2014-10/msg00906.html

Passing -mfix-cortex-a53-835769 enables that workaround for GCC. I'll also try that out later.
[Galaxy S6 Android Development] arter97:
Another very interesting CyanogenMod Gerrit code review

http://review.cyanogenmod.org/#/c/103085/
[Galaxy S6 Android Development] arter97:
It's a bit unfortunate that it seems it's actually quite common on AArch64.

http://www.slideshare.net/hidenorly/arm-cortex-a53-errata-on-andoid
[Galaxy S6 Android Development] arter97:
Slide 8

Android 5.1 is MR1. So we can skip 843419 :)
[Galaxy S6 Android Development] arter97:
We're getting some progress here.

Finger crossed..
[Galaxy S6 Android Development] arter97:
Nope. Dead end.

Those erratum commits still don't fix our issue.

More digging required.. GARR
[Galaxy S6 Android Development] thereassaad:
[MENTION=4898097]arter97[/MENTION] [MENTION=3562083]wanam[/MENTION] guys i guess u need [MENTION=4696762]darkera13[/MENTION] maybe he can help u & join to urs for helping to fix Xposed for our S6 64 bit

Sent From My Awesome G920F Powered by EchoeRom
[Galaxy S6 Android Development] arter97:
lol.
[Galaxy S6 Android Development] thereassaad:
[emoji14]

Sent From My Awesome G920F Powered by EchoeRom
[Galaxy S6 Android Development] wanam:
I think we need someone with a good experience on binary analysis to decompile stock art libs and give us some hints about any specific commits used by Samsung.
[Galaxy S6 Android Development] thereassaad:
Yes wanam confirmed bro & i guess darkera13 he can help u both as he sharing guide for xposed so maybe he can help in something etc

Sent From My Awesome G920F Powered by EchoeRom
[Galaxy S6 Android Development] thatsupnow:
This guy is also trying to get xposed on 64 bit devices too

http://xdaforums.com/showthread.php?t=3165211
[Galaxy S6 Android Development] arter97:
Go check his method and tell me back if he's capable of modifying ART.

There's a reason why my method is way more popular than his.
[Galaxy S6 Android Development] arter97:
I don't think LG's stuffs will be compatible with S6.
[Galaxy S6 Android Development] thereassaad:
1st thanks for everything u did it arter & yes i know ur method its more universal then him & other things i just suggest nothing else & u know more than me that guide method unfortunately its not working on our S6 [emoji16]

Sent From My Awesome G920F Powered by EchoeRom
[Galaxy S6 Android Development] darkera13:
LOL, thanks for your trust. I dont have S6 but if someone attach logcat maybe i can help something :)
[Galaxy S6 Android Development] thereassaad:
I would but as u know your guide method doesn't work on TW ARM 64 bit so i just suggest to join to wanam & arter & make Xposed possible for S6 [emoji16][emoji16] again darkera13 thanks
[Galaxy S6 Android Development] mythos234:
Logs are in the OP ;)
[Galaxy S6 Android Development] darkera13:
Yes, it not work, i know that a long time ago. I will try look logcat in the OP.