yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] DrawnToLife:
Please read this.

I feel like I need to bring this up, not only for my sake, but for all of this rom's users as well.

This is still a development thread of Temasek's ROM. It should be a place of meaningful discussion about the ROM to promote it's development and to encourage sound bug tracking.

There was a brief period in time where bug tracking was going great; people were using the system that I had set in place, and logs were being generated. Real reports meant that issues were more easily identified and could actually be worked on. Simply saying that you're experiencing an issue and asking for a solution, without providing the documentation necessary to diagnose the issue is useless. You need to attach logs and explain your steps thoroughly so that the issue can actually be looked at. Hence was the purpose of the bug reporting form. But now no one uses it. Instead they come here and just say, "X isn't working, please fix," or even ruder things as we've seen over the past few days. May I advise all of you to go back to reporting bugs the way I have it set up in the OP.

Also, for anyone new here, please actually read the OP. I didn't make it for you to just scroll past. It also bugs the hell out of me when people say they've read the OP but only mean the first post. I spread the information out to categorize it. I don't know how much simpler it can get.

Regarding off-topic discussion. Some of it is fine. But talking about other roms or comparing roms in this thread is rude and offensive; these conversations should take place elsewhere.
[Galaxy Note 3 Android Development] marbulas:
Is there someone knoe how to gather the logs about the tile Flashlight on QS?

I tried to do grep with the words 'torch' and 'flashlight' via Syslog but I couldn't :(
[Galaxy Note 3 Android Development] G U C C I:
After flashing the newest kernel on top of the official CM12 nightly I get a constant systemui crash, is this happening for anyone else?
[Galaxy Note 3 Android Development] marbulas:
If you guys facing the problem about theme(V4A icon in Settings doesn't change), you'd ask the theme developers to add these 'ic_setings_viper.png' and ic_settings_viper.png' both.

I asked a theme developer and we found why :) enjoy
[Galaxy Note 3 Android Development] BillGoss:
You should ask this in the official CM thread, not here.

Sent from my SM-N9005
[Galaxy Note 3 Android Development] kamikaze2112:
5.8 worked fine for me.

5.9 I'm getting this behaviour. Going back to 5.8 for now.
[Galaxy Note 3 Android Development] marbulas:
And the problem about sticking profile of FauxClock is not related with this rom and any other roms.

Plz ask it at Paul Reioux's Google+ community. You don't have to ask here and you won't get any soultions about that in here.
[Galaxy Note 3 Android Development] G U C C I:
Wouldn't this be the correct thread though since it's Temasek's kernel?
[Galaxy Note 3 Android Development] kamikaze2112:
Just tried to go back to 5.8 and everything is screwed now. Random reboots galore. Back on 5.9 for now.

Also, home button not working at all and can't pull down quick settings either.
[Galaxy Note 3 Android Development] ZDeuce2:
Systemui is rom, that is not his rom, so he can't fix it...

Common sense isn't all that common
[Galaxy Note 3 Android Development] cuezaireekaa:
Wow. I hope we don't have to post Drawntolifes' awesome and nice post every other page just so some of you guys get what they're trying to accomplish here and what a development thread is all about.

Folks with problems and ten minutes of extra time; learn how to take a logcat (OP explains, and Google is great with directions also) and that will HELP the dev immensely.

It takes a very low skillset to do this. If you know how to toggle a setting, you can get a logcat.

Telling dev you're going back to another ROM/build is not as helpful as you think without giving him some details why (so the fixes can be implemented, hence a 'logcat').

He really doesn't have time to find every bug. -That's where we come in. There is a responsibility we have when flashing these development builds everyday ... That is IF WE WANT to aid in development.

DTL has outlined what is useful from us in the first posts, the least we can do is let them help us BY helping them also.

Sorry to the users that know this by now, I know I'm only repeating what has been said many a time now, and I hope new users will read these two posts and get familiar with the OP.

Thanks and happy flashing.. er, bug reporting. :)
[Galaxy Note 3 Android Development] tdgillihan:
For those looking for an easier way to pull logs and submit them for bug reports this might be helpful.

https://play.google.com/store/apps/details?id=com.tortel.syslog

Always thank those who are helpful... and just ignore those who aren't.
[Galaxy Note 3 Android Development] G U C C I:
I understand, but this doesn't happen on the ROM until after I flash the kernel and reboot.
[Galaxy Note 3 Android Development] ZDeuce2:
It's so easy, even I can do that... [emoji1]

Common sense isn't all that common
[Galaxy Note 3 Android Development] cuezaireekaa:
his kernel is meant to run on this ROM, and any other ROM is not fully supported right now but may work fine. If it's not working, I doubt tema has the time to make it compatible ATM ( but I'm sure he'd ask other kernel devs about it if it was a dire problem, because he's a very nice and thorough guy)

I hope that makes sense. :)
[Galaxy Note 3 Android Development] dramitt_live:
Do not miss this one [MENTION=5292771]DrawnToLife[/MENTION] it would be nice in the op for future recommendations
[Galaxy Note 3 Android Development] G U C C I:
Thanks! Its just that I used his kernel on stock cm11 and never had issues, so I figured cm12 would be the same. Maybe there was a commit in cm12 that his kernel doesn't have yet that is causing issues?
[Galaxy Note 3 Android Development] erdemc:
Dude cm12 is still on the beta stage. Wait for the milestone
[Galaxy Note 3 Android Development] cuezaireekaa:
that could very well be one of the issues. you might have better luck with one of the next builds. cm12 is just getting its legs, so things will mellow out soon once devices release their OFFICIAL ROMS and we get Source. :)

hey we just got theme engine so its progressing nicely. we just have to take it day by day. good luck man
[Galaxy Note 3 Android Development] chazey2:
V5.9

Just thought I'd post my findings on v5.9.

Dirty flash from 5.8 been using approximately 5 hours now,4 hours of heavy use at work have not found one problem at all. Solid, stable, smooth and fast as normal.

Many thanks temasek another great update.

Hlte

twrp 2.8.0.4

dirty flashed from around v3
[Galaxy Note 3 Android Development] Fulfen:
Can temasek be dirty flashed over cm12 nightly
[Galaxy Note 3 Android Development] cuezaireekaa:
dirty flashes are only suggested for upgrading to the same rom.

with that said, this is a cm12 based rom so you might not have issues but do a nandroid just in case! ;)

-why i never jump roms with a dirty flash is because, later down the road new issues might crop up, and you forget that you have jumped roms in the past. that leads to having/posting problems others dont have from recent upgrades and makes it hard to troubleshoot in the thread. saves you and others a headache for sure.

what i do is titanium backup from the play store. best app ever. and just restore your data apps from titanium after a flash of a new rom.
[Galaxy Note 3 Android Development] android.zealot.fervor:
Thanks for sharing brother :)

Btw, which note 3 variant do you own ? N9005 ?

Thanks
[Galaxy Note 3 Android Development] pyrotechr:
I am on n900w8 and when i install the cm spen addon... I get an error on first boot saying "my device is not compatible"... is there any way around this?

All i want is to be able to take the pen out and take a quick screenshot
[Galaxy Note 3 Android Development] chazey2:
Yep n9005.
[Galaxy Note 3 Android Development] Fulfen:
How to set lock screen wallpaper. I can't see this option in rom
[Galaxy Note 3 Android Development] scoobyjenkins:
You can try this: http://xdaforums.com/showthread.php?p=58321078

(backup first) It didn't work for me but others have had luck. Also someone else mentioned having a Titanium Backup of wallpaper from CM11 and restoring that restored their lock wall. Also didn't work for me but you can try!

Tapatalked that shiznit.
[Galaxy Note 3 Android Development] drew071:
Just flashed back to temasek after a spell n tw lolipop. Got to say the speed of this ROM is astounding even with all my apps installed its snappy as hell.

Thanks again [MENTION=2332422]temasek[/MENTION]

Drew
[Galaxy Note 3 Android Development] Jazz__75:
Is possible add a button in the navigationbar for expand the notitification bar?
[Galaxy Note 3 Android Development] Barmenchik:
gianton-gapps-lp-mini-20141217. I try to flash gapps over, again but nothing happen.. :(
[Galaxy Note 3 Android Development] Jazz__75:
News, please?
[Galaxy Note 3 Android Development] jivankovich:
Dirty flashed from 5.7 to 5.9 on sprint note 3 and it is working like a charm. Wonderful work!
[Galaxy Note 3 Android Development] Jose Reyes:
Clean and dirty flash 5.9 Sprint and it freezes and reboots by itself back to 5.5.
[Galaxy Note 3 Android Development] Phazonclash:
5.9 runs great on my HLTECAN device. No reboot or anything, but the weather icon / temperature don't appear anymore on my lockscreen, and can't find a setting to enable it?!. :p
[Galaxy Note 3 Android Development] kamikaze2112:
I'm wondering if I just had a bad flash. Clean flashed 5.9 after a botched dirty flash last night (see my previous posts about all manner of things not working) and all seems to be good. In a case like mine, I don't think a logcat would have helped much since there was soooo much stuff that was messed up.
[Galaxy Note 3 Android Development] weavr:
I haven't had problems with hltespr v5.9. Dirty flashed from v5.8. Any logs that you could provide Tema so that he could take a look?
[Galaxy Note 3 Android Development] GavinMazey:
Running 5.9 sprint since last night with no issue. Wiped dalvik, cache and flashed over 5.8. Maybe you got a bad download have you checked the md5?
[Galaxy Note 3 Android Development] Bucika:
Working smooth. Only thing need is the option to change the lockscreen wallpaper, when this is done - merged into CM12, it will be perfect.
[Galaxy Note 3 Android Development] pyrotechr:
what's a good screenshot app to replace the native samsung screenshot/edit?

I saw someone suggest the screenshot ultimate app in the play store but I used it and it wasn't that great unless I am setting something up wrong
[Galaxy Note 3 Android Development] dave7802:
Copy your data to your External SD Card, and format internal memory and re-flash.

Warning, All data / Files on the internal Memory will be wiped

(Do this via recovery CMW / TWRP )

Really.......... This warrants a post in the Dev thread *Face Palm*
[Galaxy Note 3 Android Development] Xenomorph:
V5.8 is Great Thanks for this. My Battery no Drain. All Works for me Good.
[Galaxy Note 3 Android Development] Jose Reyes:
When I do clean installs I always clear all data and format internal to start clean. ROM works fine for like the first 30 minutes then while browsing Google+ and or Facebook it freezes and then it reboots. I will download ROM again and do another clean install. This happened on Sprint 5.8 and 5.9.
[Galaxy Note 3 Android Development] dave7802:
Facebook has it been recently updated? (I dont use it) If so it may use the correct API for lollipop SD.

In that case it may not have write access..... maybe?

Without logs this really is a guessing game sorry.

Its a pain in the butt to do, But how about formatting External Storage too?
[Galaxy Note 3 Android Development] Fulfen:
do many people us f2fs? and is it worth to format to it?
[Galaxy Note 3 Android Development] dschr:
CM S-Pen

Ignore the message. It works.
[Galaxy Note 3 Android Development] Phazonclash:
My /Data and /Cache partitions are formatted with f2fs (/system still using ext4). TBH, it makes a difference in benchmarks, but it doesn't make a big difference in day to day usage. I'm using f2fs at the moment cause I gave it a try some weeks ago but I'm a lazy ass and I don't feel like reformatting/reinstalling everything, but I wouldn't mind going back to ext4 either. Overall I'm happy with f2fs and it works great, but ext4 does to, so...

If your partitions are ext4 at the moment, I don't think it's worth reformatting/reinstalling everything just for that. If you need to reformat your partitions and reinstall from stock, give it a try. At best, you'll notice a small speed increase, at worst it will be exactly the same as with ext4 partitions.
[Galaxy Note 3 Android Development] Fulfen:
i formated /system also everythings fine. no bricks.
[Galaxy Note 3 Android Development] mumbai52:
So I had the same issue again with sound distortion and reboots on 5.9, except this time it was so bad that I couldn't even use the phone, the instant it would boot up and any sound was played it would distort and hard reboot the phone, so now I'm back on 5.7, although I'm gonna have to clean install because my home button doesn't work and qs tiles are broken I will report back in a little while
[Galaxy Note 3 Android Development] pyrotechr:
Thanks... did just that and works without any problems so far

what was so wrong with the question?

I don't see a "take a screenshot" shortcut in the shortcut options of notebuddy and the app option of "screenshot ultimate" takes 5-10 secs before it takes the actual screenshot.... I am just looking for an alternative
[Galaxy Note 3 Android Development] Medic1013:
I just press volume down+power button.
[Galaxy Note 3 Android Development] Jose Reyes:
Clean install Sprint 5.9 and has frozen 5 times while setting apps.

---------- Post added at 11:29 AM ---------- Previous post was at 11:24 AM ----------

Since my last post it ha frozen 3 more times.
[Galaxy Note 3 Android Development] GavinMazey:
Damn could the kernel be defaulting to overclocked instead of 2.2ghz thus causing your reboots? Cause I'm running 5.9 on sprint with no reboots or freezes. Ill ask again have you checked the md5?
[Galaxy Note 3 Android Development] Jose Reyes:
Yes md5 matches... Checking CPU clock.... down clock to 1958400 and see what happens. How do I uload a catlog?

Edit: Since down clocking to 1958400 phone has not froze yet.... so far it looks like the cpu speed may have been the issue in my case.
[Galaxy Note 3 Android Development] Barmenchik:
Hi All.

Yesterday on v 5.8, on Lockscreen I have Weather icon, today on v 5.9 I can't find how to set up that!!?:confused:
[Galaxy Note 3 Android Development] vivabonito:
After upgrading from 5.0 (very solid build IMO) to 5.7, I'm experiencing micro stutters and pitch increases while playing music over Bluetooth in my car (something I've never experienced before with Tema's Lollipop and ICS builds). Is anyone else having this issue? I'm guessing CM has updated the Bluetooth stack in the latest Lollipop builds and these two bugs came with that update. Hopefully, it gets resolved soon. By the way, I'm using a Canadian Rogers N900W8.
[Galaxy Note 3 Android Development] azngujuonfire:
Is there anyway I can get the CM12 cyanogenmod camera app?

The stock google camera is just too slow and does not really result in the clear pictures that I desire.
[Galaxy Note 3 Android Development] Jose Reyes:
I've been using this one from CM works like a charm for me: https://www.dropbox.com/s/k8eb9fl9a0suzys/CameraNext-2.apk?dl=0
[Galaxy Note 3 Android Development] azngujuonfire:
Thanks i'll give it a try! I wwas thinking maybe since i flashed minimal x+ gapps it removed the aosp camera.
[Galaxy Note 3 Android Development] Calen77:
You can put the shortcut for screenshot in the powermenu...
[Galaxy Note 3 Android Development] SEB1109:
[MENTION=4741987]Barmenchik[/MENTION]

Hi All.

Yesterday on v 5.8, on Lockscreen I have Weather icon, today on v 5.9 I can't find how to set up that!!?

system settings...Temasek Spare Parts...Clock widget...weather panel
[Galaxy Note 3 Android Development] Calen77:
...go in to configure/buttons/power ... Select screenshot and then the powermenu change:
[Galaxy Note 3 Android Development] DrawnToLife:
Why don't you post a logcat of the FC that you're getting instead of commenting with the tone of it being missing.
[Galaxy Note 3 Android Development] SEB1109:
Huh? I was just trying to tell him where I thought he could find the settings he was looking for. If that isn't what he meant, sorry. You are correct that if it is missing after setting it up he should definitely post the log cat for someone (with the know how) to use it to better the ROM.
[Galaxy Note 3 Android Development] dschr:
Weather in clock

Same here, I'm also on 5.9. 5.8 was the only one, it worked for me.

Calendars never did so far. And yes both are activated in settings;)

Oh, and I don't get FCs.

Apart from that, ROM is really miles ahead of CM12.
[Galaxy Note 3 Android Development] DrawnToLife:
Oh. You quoted him.. It didn't look that way.
[Galaxy Note 3 Android Development] rrichards:
I've a big problem

This morning i flashed 5.9 (i came from 5,1-2-3-4....8) and it went well until 10 mins ago when i found the phone off. I tried to restart and for a few seconds, after the bootanimation, the home appears and then all black with only the status bar and the only thing i can do is to access to the power menu. Itried to ri-flash the 5.9 but nothing. What i can do?
[Galaxy Note 3 Android Development] topherk:
I'm assuming these are all dirty-flashes? This is not the recommended way of updating the ROM. When you say you "reflashed" it, was it a clean flash? Did you check the downloaded file's md5 to make sure it wasn't a corrupt download?
[Galaxy Note 3 Android Development] mattg1234567:
5.9 chrome doesn't at web videos. All greened out. When is the last version that this worked fine?
[Galaxy Note 3 Android Development] rrichards:
Yes dirty.

I've to wipe every nightly i flash?:confused:
[Galaxy Note 3 Android Development] Jose Reyes:
Watchin videos on Chrome on Sprint 5.9 Clean Flash is working fine....
[Galaxy Note 3 Android Development] topherk:
You don't have to do a clean flash for every nightly, but post #3 clearly says:

Typically, it's fine to dirty-flash, but this ROM (and, in fact, all ROMs) can only be realistically developed as stand-alone "clean" flashes. While most-of-the-time, dirty-flashing won't result in too many errors, it's almost impossible for a independent developer to engineer a nightly that will work as "updates." How would they design it to guarantee that an update from 5.1 -> 5.9 works the same as from 5.3 -> 5.9?

So, my advice to you would be: Feel free to dirty-flash, but be aware that errors and FCs will be more likely to happen and are not inherently the fault of the ROM.
[Galaxy Note 3 Android Development] ZDeuce2:
I understand that, but temasek's kernel is for temasek's rom... If it works on other Roms so be it... If it doesn't then it's not compatible... The real question is when temasek's rom is far superior to base cm, why would you not use his rom as well????? Any who, your choice are temasek's rom and kernel, or cm base and their kernel...

Common sense isn't all that common

---------- Post added at 07:50 PM ---------- Previous post was at 07:35 PM ----------

A little help would be great, rom build? Kernel settings? A logcat for real support? Anything really? This isn't the psychic hotline ...

Common sense isn't all that common
[Galaxy Note 3 Android Development] Jose Reyes:
Found the problem with suggestions from another user. Tuns out the CPU's where being over clock on initial setup. Lowering the max CPU clock solved the problem for me.
[Galaxy Note 3 Android Development] ZDeuce2:
Sorry, I didn't catch the build at first... But your kernel settings could be the problem, the best way, as stated in the OP , is to pull a logcat, and file a report... That way it get looked into...

Common sense isn't all that common

---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------

I'll post this again since some seem to have forgot between last night and now...

PER; [MENTION=5292771]DrawnToLife[/MENTION] ...

Please read this.

I feel like I need to bring this up, not only for my sake, but for all of this rom's users as well.

This is still a development thread of Temasek's ROM. It should be a place of meaningful discussion about the ROM to promote it's development and to encourage sound bug tracking.

There was a brief period in time where bug tracking was going great; people were using the system that I had set in place, and logs were being generated. Real reports meant that issues were more easily identified and could actually be worked on. Simply saying that you're experiencing an issue and asking for a solution, without providing the documentation necessary to diagnose the issue is useless. You need to attach logs and explain your steps thoroughly so that the issue can actually be looked at. Hence was the purpose of the bug reporting form. But now no one uses it. Instead they come here and just say, "X isn't working, please fix," or even ruder things as we've seen over the past few days. May I advise all of you to go back to reporting bugs the way I have it set up in the OP.

Also, for anyone new here, please actually read the OP. I didn't make it for you to just scroll past. It also bugs the hell out of me when people say they've read the OP but only mean the first post. I spread the information out to categorize it. I don't know how much simpler it can get.

Regarding off-topic discussion. Some of it is fine. But talking about other roms or comparing roms in this thread is rude and offensive; these conversations should take place elsewhere.

Common sense isn't all that common
[Galaxy Note 3 Android Development] Imppy:
Does anyone have battery drain on 5.9?
[Galaxy Note 3 Android Development] topherk:
That's a very good point. It's sad that a majority of the questions on this thread are from users that are dirty-flashing and asking why they are getting FCs and random reboots. The issue is that if we ignore these "petty" issues, the community around this ROM will be seen as unhelpful and indignant. I try my best to look through and answer these questions as quickly as possible, so that other conversations could go back to the ROM. And as long as I'm not too-indignant in my responses, I believe that the user has learned something.

While getting a logcat isn't too difficult, I've found that there are many people who are here to get a daily driver ROM, not to actually troubleshoot the issues hey might get. This attitude is difficult to change in the user and, sadly, has to be accepted to some degree.

I understand that there's a dedicated thread in the Q&A section that's meant to deal with the types of issues these people are having. I've never really seen these secondary threads get used to the extents that the Dev's hope they would.

Maybe I'm just feeling pessimistic about the community right now, but I feel like it's a difficult thing to change.
[Galaxy Note 3 Android Development] TrypelZ:
Surprisingly not. I had battery drain on EVERY build till i flashed 5.9
[Galaxy Note 3 Android Development] jpeckinp:
You are forgetting one thing. Temasek has stated repeatedly that you don't need to clean flash and that dirty flashing is OK. So don't go bashing them just because they dirty flashed.

I'm not here to defend these people that are rude or anything like that. It has has got on my nerves also and I wish they would learn to be patient and read.

I have used the bug report system and have had good luck with it. If I do have a problem I will check the site and read from the posting of the new release to the end to see if anybody has reported what I am seeing if they haven't I will ask. Then if it is duplicated by others then I will see if it has been reported on the bug report.
[Galaxy Note 3 Android Development] sevenslugs:
Everything works great for me on 5.9 just had a small issue where I would swipe the lockscreen to unlock the phone and the screen would just turn black again. Even restarting the phone would not fix this issue.