yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] Journyman16:
Went and got original h/p from car and tried dialling out and back in. Headset works both ways with one odd bug - when I dial back to my phone, I don't hear the ringtone but once answered I DO hear the sound from other phone. Dialling out from my phone works fine with h/p plugged in.

v17.4 but I haven't noticed any issues with earlier versions. Mind you I don't use the headset often. :D
[Galaxy Note 3 Android Development] Pehpe:
I miss the intellidemand cpu-governor.
[Galaxy Note 3 Android Development] Sleestax:
Used OTA for 17.4. Install went smoothly, but I did get a Google Play force close on the first start. I haven't had one since.

Otherwise. Everything seems to be working fine for me.

Sent from my SM-N900T
[Galaxy Note 3 Android Development] Journyman16:
v17.4 installation is odd. I know some people have had no issue in doing dirty flash, but I have just done the following:

Wipe everything except extSDCard

Restore v17.2 and boot. = all good

Recovery, wipe Cache and Dalvik, flash v17.4, wipe C&D again = Bootloop after App Optimization

Wipe all again and Restore v17.2 and boot = all good

Recovery, wipe Cache and Dalvik, flash v17.3, wipe C&D again = All good

Recovery, wipe Cache and Dalvik, flash v17.4, wipe C&D again = Bootloop after App Optimization

Restore v17.2 and boot = all good.

Dirty Flash v17.4 with no wipes = Bootloop after App Optimization

I'm now trying DL the OTA and see if that has a problem. Note that clean install v17.4 has no problems.
[Galaxy Note 3 Android Development] ocujos:
Same here.
[Galaxy Note 3 Android Development] asusgarb:
Hi guys. 2 questions about our Note 3:

1 - I know NFC doesn't work, but do you think it will be able to work in the near future?

2- Do you think our beloved Note 3 will never see Marshmallow (custom I'm pretty sure, but official not so sure)?

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy Note 3 Android Development] Journyman16:
le sigh - Tema is just too quick for me - set the OTA download running and got 17.5 instead... :D

EDIT: I was wrong - I did get 17.4 from OTA but it didn't work - same results - bootloop after the App Optimse run... I'll restore my v17.3 and try the v17.5 OTA and see how that goes.
[Galaxy Note 3 Android Development] jisoo:
I think all AOSP-based ROMs support our bootloaders (at least they have my 900K). TW-based ROMs are a different matter, though.
[Galaxy Note 3 Android Development] Journyman16:
OTA install of v17.5 over v17.3 fails after App Optimise. Just waiting to see if the restart thing keeps happening. (in case something different in 17.4 & 17.5 is requiring a reboot after initial boot up)

Next step is to clean flash 17.4 then try OTA over it.

Phone gets quite a bit hotter than usual on a new ROM boot. And it definitely is not faster than previous builds. Gonna have to see how I can get a log of this. Maybe there's a command in TWRP terminal I can run?
[Galaxy Note 3 Android Development] Rintenfinten:
17.5 over 17.4 no problem here. I did a wipe system / dalvik / cache in twrp before flashing 17.5, tk gapps and supersu.
[Galaxy Note 3 Android Development] emannxperia:
Have the same issue, dirty update & bootloop after app optimization. Went back to 17.2.

Will try 17.5 & report back
[Galaxy Note 3 Android Development] atti003:
Hello,

Is there any possibility to enter USB Settings Mode and Service Mode on this ROM?

Thank you in advance for your help.
[Galaxy Note 3 Android Development] Amar.B:
You are absolutely right i did not tested with cellular data but now i did with the stock headphones and no issues here, no lies i had these problems in earlier builds but now it's gone, try clean install if you still facing these problems provide a log
[Galaxy Note 3 Android Development] emannxperia:
Did a clean install on 17.5, so far so good.

Did temasek removed some of the cpu governer?
[Galaxy Note 3 Android Development] emuandco:
Well, NFC works for me. It depends on the Note3 variant u use and you seem to have the same I do. NFC works really fine here.
[Galaxy Note 3 Android Development] BillGoss:
Yep, arteractive is missing.

Sent from my SM-N9005
[Galaxy Note 3 Android Development] delios:
Dirty flash V17.5 upon V17.4, all good, except battery percentage shows 3838% instead of 100%.

Did a restart, no luck.
[Galaxy Note 3 Android Development] Pehpe:
Does anybody know why temasek has removed some of the governors? I really miss my intellidemand-setting!!
[Galaxy Note 3 Android Development] mdfpido:
Anyone knows why when adding a credit card on Android Pay, Google Play Services crashes?
[Galaxy Note 3 Android Development] asusgarb:
F**k F**k F**k F**k F**k!!!!!

It's the 3rd time i have to clean install this rom because dirty flash bootloops on animation! But today was different. Animation -> App optimization -> Stuck on animation. Before it never passed animation.

It's happening since 17.2. I don't know if it's my fault, because I'm doing only 2 different things: I added TodayCalendar and freezed NFC with Titanium Backup.

And, considering I'm not the only one having this problem...

But what does can cause this problem???
[Galaxy Note 3 Android Development] Journyman16:
Do you use a non-styandard DPI? If so, you need the one to match your DPI - easiest way is to DL the 230 version, which is universal. apkmirror.com has them.

Note you have to use something like TiBu to uninstall the one you have, reboot, then Install the new apk then reboot.
[Galaxy Note 3 Android Development] jvandenbroek:
I've dirty flashed all versions since 16.7 and have no issues at all! Some flashes did indeed reboot during optimizing, however it always came back online :)

I must say that 17.5 is running very smooth again, last few updates didn't feel this way ?

Sent from my SM-N9005 with Tapatalk
[Galaxy Note 3 Android Development] Journyman16:
Well, it took some doing but I finally managed to get v17.5 to update over v17.4 with no bootloop. I could not in any form get v17.4 to dirty flash over v17.3. But a very clean flash (including internal instead of just /Android deletion) of 17.4, then rebuild everything and put all my files back on Internal got me back to my standard set up. Then I got OTA to take it to 17.5

Some observations.

non std DPI - update Google Play Services to the one to match the DPI. In my case this is the 236 version or the 230 universal which becomes 236 after reboot.

I normally have OTA frozen because some time back it gave unreliable results. If you also have it frozen you cannot just defrost it and run it. Restart THEN run it. You should get a SuperSU request when you do. If you do not it will not auto-run the install and you will boot loop.

OTA Update has hard coded path to Storage/Emulated/0/OTAUpdates - in ES File Explorer this does not exist and cannot be created so I think OTA Update needs superuser access to make the connection across to the app settings. Be nice if OTA Update allowed choices for where things are stored. I like to put such things on extSDCard just in case (such as these situations) I have to wipe Internal.

The DPI setting in Settings does not restore all the DPI settings if you use a ROM settings Restore app. I found I have to also run textdroider to get the apps bar across the bottom of screen to accept the DPI. Not sure if NOT doing that causes boot loop and can't think why it would but all the tries where I didn't do that boot looped, maybe for other reasons.

Why some people didn't have issues I haven't a clue. Those who did, can you tell me if you also have OPTA frozen? The only thing I can think is we inadvertently tried to run OTA without that essential reboot after defrost.

---------- Post added at 11:45 PM ---------- Previous post was at 11:44 PM ----------

Mine never came back online, just kept reboot after optimize. I left it so long one time I am now concerned for my battery because it got so hot. It doesn't get anywhere near that warm if the flash process works properly.

---------- Post added at 11:47 PM ---------- Previous post was at 11:45 PM ----------

My final flash worked and my battery shows as normal. I use battery bar but also have the percentage in text. Mind you it's at 100% so might have to wait for it to come back to 2 figures. :D
[Galaxy Note 3 Android Development] jvandenbroek:
Well, not the battery, but CPU / main board in the top of the phone gets very hot during optimizing (at least in my case). I always put my device on the charger while doing this, otherwise my battery drains too quick and dies, guess I've a bad battery [emoji4] Also sometimes I cool it down with a cold pack [emoji13] Doing that I've encountered no issues with updating.

Sent from my SM-N9005 with Tapatalk
[Galaxy Note 3 Android Development] mdfpido:
I'm using 420.
[Galaxy Note 3 Android Development] Pehpe:
17.4 and kernel 1.25 are for me the best choice atm. Will wait for proximity sensor fix. Then I'll update next time.
[Galaxy Note 3 Android Development] Journyman16:
Then you should use

This One
[Galaxy Note 3 Android Development] minhgi:
Same issue here to. Also the battery option in settings is missing.
[Galaxy Note 3 Android Development] thetransit123:
So the right google play services for our note 3 is the 230?
[Galaxy Note 3 Android Development] asusgarb:
Hi. Thank you for your big reflection. Now I would like to share my opinions.

1 - This problem of bootloop on dirty flash started with 17.2, so I think could be something inside the ROM to cause it, because happens to many users with different models and different GApps.

2 - Freezed OTA has never been a problem for me. With Titanium it's one of the first apps that I freeze (I always had problems with it, so I prefer manual download)

3 - Play Service could be one of the causes (remotely, IMO) because I noticed a strange thing latest ROM. At boot (clean install) is version 230 (universal, because I use GApps with universal dpi addon), but after some seconds it updates by itself (from 17.2 to 17.4) to 236. But 236 is for 420dpi (i alays set to 360). On previous roms it updated himself to 238 or 438 (for 480dpi) like did in 17.5.

But the strange thing is that it updated to 236 before the change of DPI, so "why it didn't update to the 480dpi version"? I tought it was because of the multi dpi addon of my gapps, but maybe there as an error....

4 - I started thinking I could have hybernated some system app I shouldn't have to. But I tought that on update xposed go away, as some greenify functionality. But then I realized greenify can't be the cause, because would mean than every user with this problem use xposed with greenify and same freezed apps (almost impossible)

5 - I noticed that, between users with bootloop problem there is only one common thing: the ROM. I'm saying that because:

- before 17.2 anyone had problems so seriously

- problem is on different models

- we use different configurations and elements (gapps, dpi, xposed, modules etc).

Please, before starting exclaim "if you think it's the rom, then change it" or "don't insult the developer" or something like that let me finish. I'm not accusing anybody or anything, and I'm going to keep using Tema's ROM till the end, because I totally love it.
[Galaxy Note 3 Android Development] Sleestax:
Oh hai guys! This ROM sucks. I flashed it then did a bunch of crap like change kernels and xposed and froze core apps. The ROM keeps failing. So obviously its the ROMs fault and all those people who vanilla flashed and have no issues are lying.

Sent from my SM-N900T
[Galaxy Note 3 Android Development] btvolta:
[Delete.

Sent from my unknown using Xparent BlueTapatalk 2
[Galaxy Note 3 Android Development] scoobyjenkins:
I think the post was intended to be humorous and directed at those who modify stuff then complain!

Tapatalked that shiznit.
[Galaxy Note 3 Android Development] kaos_king:
That's what I gathered from it.

A smiley at the end would have changed the tone.

☺
[Galaxy Note 3 Android Development] gencho81:
Currently running 17.4 without any issues. Clean flashed and restored apps with titanium. Proximity sensor seems to work just fine(less than 1 sec after removing from head screen light up). Google play services version 236 8.1.1.15 without FC. Using it on 320DPI. Only one lets say problem- stylus pointer. I want the dot not the arrow. Soem easy fix for it or its DPI related?
[Galaxy Note 3 Android Development] btvolta:
I'll delete my post. Sorry, kind of glanced and reacted. Now that I read again, I agree.

Sent from my unknown using Xparent BlueTapatalk 2
[Galaxy Note 3 Android Development] thetransit123:
??? :o
[Galaxy Note 3 Android Development] Wildfire-Hooves:
The update from 17.3 to 17.4 worked fine and the update to 17.5 also fine.

But battery status information is broke

Tapatalked via Lenovo Yoga Tablet 2 Pro
[Galaxy Note 3 Android Development] Bobanovicz:
Right, but screen still react to touch.
[Galaxy Note 3 Android Development] asusgarb:
But you have to admit that since 17.2 the number of people having this problem is highly increased.

Now I've clean flashed 17.5 so I can't do nothing, but with the future build I'll try dirty flash changing these things:

- uninstall xposed before update.

- remove hibernation from all system app hibernated with greenify.

- restore all apps deactivated with Titanium (this is optional) or, at least, some of them.

So I'll understand if it was fault of these things or not.

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy Note 3 Android Development] flint777:
Yeah how do se stop this??
[Galaxy Note 3 Android Development] gencho81:
So it's me again. No proximity problems at all. Dialled my wife's phone, put my finger near to proximity sensor-screen off and not reacting on touch. So can say no problems at all for me here. Except arrow when stylus is out. Really standard for Samsung dot is better. Really will appreciate it back.

About bootloops - dirty flashed 17.3 over 17.2 and 17.4 over 17.3 without any issues. After made clean flash of 17.4 bcoz i like it this way.
[Galaxy Note 3 Android Development] dprimic:
The Battery problem is related with Arter kernal. With Temasek kernal no battery problems.
[Galaxy Note 3 Android Development] hombregr:
from 17.3 to 17.4 dirty flash kernel 1.29 and i was having an issue with the phone call quality...low sound from my microphone, so the other end couldnt hear me well and with static sounds.. i try the microphone with other apps like messenger hd call , skype and the sound that was coming from my phone was crystal clear, so i assume that is something wrong with the dialler... can you plz help me????:confused::confused::confused:
[Galaxy Note 3 Android Development] Igetlaughs:
This is for the Sprint users, I was having a lot of GPS problems until 17.3 then it was simply magical. I've been on the baseband Nk4 for a long time because I couldn't get my hands on a PC. I updated to OC5 and now I'm having GPS problems. Anybody else having this problem and should I just go back to baseband NK4?
[Galaxy Note 3 Android Development] ocujos:
Anyone reporting "bugs" should do a full wipe and clean install first. I don't have any issues and I run *stock standard* Temasek's ROM on N9005. While Xposed is nice to have, it's not necessary in this fully featured ROM. Kernel too: the one built by Temasek is the best.
[Galaxy Note 3 Android Development] Sleestax:
Adding a smiley ruins the humor. I'd rather be misunderstood than add smileys.
[Galaxy Note 3 Android Development] Wildfire-Hooves:
Nope wiped Dalvik and cache.

Installed Temasek's kernel 1.29 still the problem

Did the same and installed 17.5 over the existing 17.5 no fix.

Tapatalked via Lenovo Yoga Tablet 2 Pro
[Galaxy Note 3 Android Development] ocujos:
How about a nice clean flash with full wipe as per OP and no "add-ons" eg Xposed?
[Galaxy Note 3 Android Development] BillGoss:
I installed 17.5 over 17.4 and I also did a clean install of 17.5. No problems with battery display.

Sent from my SM-N9005
[Galaxy Note 3 Android Development] Journyman16:
If you're not on 480dpi it seems the best one. For me, on 320dpi, there is a 236 one, but the 230 version seems to install the right one for your dpi - I install 230 and shortly after my version is 236.

---------- Post added at 12:51 PM ---------- Previous post was at 12:47 PM ----------

Sounds like something went wrong. Battery is present and shows correctly on my clean flash 17.5
[Galaxy Note 3 Android Development] thetransit123:
Thanks for the reply

I have the 480 dpi, so i have to install the 236 one? :D
[Galaxy Note 3 Android Development] minhgi:
You right.. I was using the arter97 kernel. I have since reverted back to 7.4. If arter kernel get updated, I am going to update the ROM as well.

Thanks for the clarification
[Galaxy Note 3 Android Development] Air-真心为你:
Anybody knows how to get audiofx working ? I tried many different methods still no luck.
[Galaxy Note 3 Android Development] Journyman16:
I'd agree except I don't use Xposed or change the kernel and frozen apps should not matter when the phone hasn't even started yet. It fails AFTER completing Apps optimse step and if you watch the apps, it is USER apps being optimised, not system ones.

But I always admire a finely tuned level of sarcasm... :D

---------- Post added at 01:37 PM ---------- Previous post was at 01:22 PM ----------

Nope. If you are on 480 dpi then the standard one should be OK. The 236 version is for 320dpi and the 230 version is for universal, i.e. any DPI
[Galaxy Note 3 Android Development] delios:
How can you say this? Have you done any testing?

Alter kernel has nothing to do with this. See the screenshot.

Back to V17.4 to have the battery display back.
[Galaxy Note 3 Android Development] Wildfire-Hooves:
The Only Way to fix it atm is a Clean Install.

Tried Serveral Ways to fix it.

Only Wipe Everything and Install Fresh without Custom Kernel. Fixed it.

P.s if the 17.5 OTA Version Fails try the Bucket Downloadet version
[Galaxy Note 3 Android Development] mdfpido:
Thanks for your patience, but it's not installing. Doesn't matter for now. Thanks again.
[Galaxy Note 3 Android Development] kaos_king:
Did you follow journyman's instruction at the end?
[Galaxy Note 3 Android Development] Journyman16:
Did you follow my steps?

1. Use Ti Bu to uninstall the current GP Services

2. Reboot

3. Use something like ES File Explorer (with Root access) to install the new one

4. Reboot.
[Galaxy Note 3 Android Development] biobee:
I have been using Temasek rom since v15.9, wonder what camera are you guys using? Quite miss Samsung Camera with good function. Is there a way to port to this rom? Thanks.
[Galaxy Note 3 Android Development] Crystylez:
Has the Kernel Option ''Intellidemand'' Been removed..? Cant seem to find it any longer.
[Galaxy Note 3 Android Development] gencho81:
Hi all,have made one small zip that will change stylus arrow with dot.hope so you will like it. I test it on 17.4 with 320DPI and all is fine. Just flash it from recovery and reboot.

https://mega.nz/#!1BJSCDQR!kPXUlbyQ4Jg3kcEoEp7MPwfntVp4n7inqySiWmM4Pv4

Just test it on 480DPI also looks fine [emoji1]

EDIT : New zip with dot for stylus pointer AND propper dot location to fit stylus end.
[Galaxy Note 3 Android Development] Pehpe:
Yes, it was also my favourite setting. I flashed kernel v1.25. This is the latest version wit intellidemand in it.

http://temasek.rajasthanautoworks.in/?dir=Samsung Galaxy Note 3 - HLTE/CM12.1/Kernel V2/Old
[Galaxy Note 3 Android Development] Rintenfinten:
As far as I know custom governors will come back in next kernel Version. Except alucart and arteractive. T said so on Twitter.

Next update eventually tomorrow.
[Galaxy Note 3 Android Development] Pehpe:
Cool, thx 4 info
[Galaxy Note 3 Android Development] expain08:
Done downloading the rom :) will give this one a try 17.5 full gaps and super su!

Does this rom include a custom kernel already or a stock kernel
[Galaxy Note 3 Android Development] Journyman16:
I use Cameringo - it was good enough I paid for the Pro version.

---------- Post added at 01:22 AM ---------- Previous post was at 01:21 AM ----------

Has it's own kernel - haven't found a reason to go for anything else.
[Galaxy Note 3 Android Development] vidwhal:
Does anybody else experience a bug where the Lockscreen wallpaper is the same as the home screen when the Lockscreen setting "Directly Show Gesture" is set on?

Or rather the Lockscreen forgets it's own wallpaper.

thanks.
[Galaxy Note 3 Android Development] Bracher:
I have the same problem made a clean installation of 17.0 now dirty flash wipe Dalvik/Cache/System with 17.5, Kernel 1.29 and the new GAPPS - but suddenly my battery symbol shows 3.728% - it's really disturbing! Any help would be welcome!!!

By the way my Tablet - Note 10.1 Edit. 2014 - works with the inofficial Temasek. Made the same and with N900 the battery is correct.

-----------

Went back to 17.4 for Note 3 and battery shows the right figures.
[Galaxy Note 3 Android Development] asusgarb:
Hi guys. I noticed casually that, even with screen off, my physycal buttons (menu and back) vibrate on touch. Nothing happens, but the phone vibrates. I never noticed before. Is it normal, happens to you too?

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy Note 3 Android Development] dprimic:
I wrote that after a test. Had arter's kerner 8.1 on 17.4 and everything was fine. After dirty upgrade to 17.5 the battery problem emerged. Deleted the script for the kernel survive of the arter's rom and refleshed 17.5 again and no the battery problem. Fleshed arter's kernel and the battery problem started again. I am sure as anyone can be that 17.5 and arter's 8.1 doesn't go along. Does something else can trigger battery problem I don't know.
[Galaxy Note 3 Android Development] DonPhelippe:
Greetings peeps, a fresh usage report from 1.4 (1.2->df 1.3->df 1.4) on N9005, and to summarise elegantly:

When using mobile data for anything (even simply sitting idle), atrocious battery drain is atrocious.

Something is definitely off because 1.2 did not behave like that. I am using battery saving location mode, every time i flashed with wiped cache and dalvik cache.

Anyone having this particular thing? I mean, 1.3 was okay-ish (and 1.2 was okay) but this is kinda ridiculous: from 1 day of use (using google's battery screen) the battery fell down to 8hrs (!) so OBVIOUSLY something went *very* wrong, can't change that much from 1 day to another, right? Right.

In general, whenever using *anything* that uses mobile data, be it facebook or firefox or what have you, or even google play music, the phone heats IMMEDIATELY and battery plummets. Fnarg! :mad:

Edit: My initial culprit was Google services. But from what I see now, *everything* that uses H/3G simply devastates the battery and the phone goes *on fire* (and not in a good way).
[Galaxy Note 3 Android Development] sarcokiller:
Wich app can i use to make a backup of my settings and apps and restore all in a clean 1.5 install? I'm having no deep sleep here on 1.4 so i think that is better to do a clean install... Thanks in advice!
[Galaxy Note 3 Android Development] BillGoss:
See this post in this thread http://xdaforums.com/showthread.php?p=57222557

Sent from my SM-N9005
[Galaxy Note 3 Android Development] j3hans:
Hi. Is there a way to install better battery stats in this rom? It cant read through the system since it requires the enable battery stats from xposed. Thus anybody know any work aroind for this app to work?
[Galaxy Note 3 Android Development] menioseten:
:laugh:

thanks.It's OK now:laugh:
[Galaxy Note 3 Android Development] rob4711:
Thank you BillGoss. I know this workaround. It would be better to integrate that in future releases. So it is more comfortable.
[Galaxy Note 3 Android Development] cuezaireekaa:
Lmao thanks for letting us know

glad that works for you and could be of some help :D
[Galaxy Note 3 Android Development] DonPhelippe:
I used to do Titanium, but apparently this is the official-ish solution to this problem by CyanogenMod himself no less:

https://play.google.com/store/apps/details?id=com.koushikdutta.backup
[Galaxy Note 3 Android Development] kaos_king:
When I installed BBS and opened it, it said that it needed to install as a system app, I did that and it all went swimmingly, reboot and app is ready for use. No xposed needed?