yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
V7.7 is up on shares and basketbuild
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Yes, you need to get a logcat.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] jsonder:
Battery drain even while (supposedly) idle is really bad. Went from 92% charge to 69% in a few hours when I was not even using the tablet. Any suggestions? Maybe the default battery settings are hosed?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] yusoffb01:
Use samsung stock lollipop ROM then. I get 1% drain per day
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ViRuS-MaN:
what new 's form the v7.8
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Some fixes that were introduced in v7.7
[Galaxy Note 10.1 (2014 Edition) Android Developmen] pentiger:
On version 7.6 I drained the battery completely from 100% in 40 minutes, while drawing in sketchbook on 50% screen brightness. Something is definitely not right. I will now see the 7.8 (installing now)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Whistler1813:
Flashed 7.8 this morning but I'm not noticing anything drastic between it and 7.6 subjectively speaking.

I don't use the pen much. I use the tablet for watching movies quite a bit with MXPlayer and I'm dropping about 10% battery life every 40-50 minutes. This is with the screen at ~75% to 80% brightness.

The absolute best battery life I've ever had was with the later versions of KitKat and Lollipop once the ROM devs worked out most of the kinks and bugs. With those ROMs I would get the 10% loss every 60-75 minutes with the same basic usage.

You probably should try a full wipe and flash 7.8.

Unless out of immediate necessity I perform a full wipe with every major release just for good measure.

I hope you're able to get it worked out. Maybe it is something to do with the pen or an errant app.100% drain in 40 minutes is huge and I bet that tablet is quite warm during those 40 minutes.

---------- Post added at 04:34 PM ---------- Previous post was at 04:22 PM ----------

To everyone else:

I haven't heard about it in a while but I remember that some folks who went with the official Lollipop upgrade were having problems associated with the upgraded boot loader. I haven't been on stock since KitKat but I know a lot of people installed the official L ROM when it came out.

Just out of curiosity, is there still an issue with older vs. newer boot loaders and if this could be introducing problems that seem unique compared to the rest of us? Or am I barking up the wrong tree?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi Pentinger!

I have found that the CPU is sometimes locked at a maximum frequency and permanently clocked at 4x 1.9GHz.

The back is quite warm left next to the camera in this case. (SoC temps can be above 90°C!)

This error mostly occurs after heavy load situations and only a reboot helps to keep them back to normal behavior with idle mode(250mhz)!

I've also observed that the A7 cluster is more or less unused in cm13/mm roms. I think the SOC is only running in a way quadcore mode and the interactive governor seems also set to high performance!

Frequncies jumps only between 250(idle) and 1900mhz(max.) and the all other frequency steps are mosly unused!

Wondering if he was ever written for Exynos 5420, LOL!?

Certainly in the current state the kernel must be revised again because he works more bad than good. No question, he is quite powerful but with realy poor efficiency!

I have only 4-6 h of screen on times with MM against 8-10h under 5.1.1 / LP, with more or less the same tweaks!

Currently I have underclocked to 1500MHz and the interactive governor was slightly tweaked(go_hispeed_load set from 99 to 90 and target_load from 90 to 80) what gives me an additional hour without noticeable loss of performance.

I think, as long as the small a7 cluster is only clocked at 650mhz max. speed(normal behavior is 1300mhz, lol!) and is not used to safe battery we will not achieve the maturities like on kitkat and lollipop roms!

I see also lots of warnings and errors in life kmsg each second.

I dont know who has build the kernel(maybe chefT) but it seems the kernel need a lot of work so that we can really enjoy the benefits of android 6.0.

Also BBS reports lots of background services and activities during display off times(over night) sometimes 30-40% of the time which will additionally drain the battery.

The most tests are done with 3C Toolbox, Better Battery Stats and Kernel Adiutor from plays.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ViRuS-MaN:
v7.9 install and all it s ok
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tony66:
all it s ok ???

Camera? Infrared?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ViRuS-MaN:
only the camera no work but all cyanogend dont have camera only the galaxy tab s have
[Galaxy Note 10.1 (2014 Edition) Android Developmen] tincmulc:
The A7 cluster is not clocked at 650 MHz max, it is the same 1300Mhz as in stock roms. That is because frequencies 250-650Mhz represent A7 cores at 500-1300 MHz(so displayed x2), and frequencies 800-1900 MHz represent A15s at 800-1900Mhz. This is done because or tablet can't use both clusters at the same time, so this is a sort of hack so we can use both. Everything I have written so far is also exactly the same on stock roms.

What is different on this rom is the configuration of the interactive governor. So far I found the best thing to do is to set hispeed_freq to 650000 (which is the maximum A7 cluster frequency of 1300MHz), which mostly solves the "only using 250 and 1900".
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Charging is slowwwww
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tony66:
Charging normaly - original charger

V7.9
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
I've been closely following this ROM and running a dirty flash each time. I can get the flash done in under 10 min.

I have not had any problems and my battery is performing great as usual. Two quick questions: Is therea more recent stable super su available? I've been running 2.65, but I have a beta 2.68. Anyone find newer releases?

Last question slightly o/t: Is there a reliable source online for original spen relacements. Getting tired of back fakes offered as oe. Thanks ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
I am running stable su as well and probably will until a new version is released or stable doesn't work for some reason. I initially ran the beta releases but at times had issues with not getting su

It seems this charging thing is spotty.. I've charged once this week yet some are having issues. Might make a poll to see what bootloader people are running
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Zionator:
Omg the volume in this ROM is to low. I can almost not hear the videos I watch nor the TV I stream.

Anyway to increase it ?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] josepr2012:
Camera is a known issue...or at least I searched and found that some post behind as I did a clean installation and it never worked for me.

http://xdaforums.com/showthread.php?p=58357184
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Camera is broken in device tree even base cm build. It worked at one stage however the cm maintainer is attempting to get official status and there for had to change the was the camera was initially implemented. This causers it to break but will be better in the future once he has a little more time to work on it
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Build v7.4 is up on basketbuild I haven't looked at the nav bar yet I shot this build off by remoting in while at work
[Galaxy Note 10.1 (2014 Edition) Android Developmen] josepr2012:
Help: How I put the tablet in TWRP recovery mode with volume buttons ? Everything was perfect but root..flashed su update and now tablet do not reboot...Need to restore from TWRP but cant make it goes to recovery:confused::confused:

Thanks

Sent from my klte
[Galaxy Note 10.1 (2014 Edition) Android Developmen] FiDuS80:
Hi guys, I need your help please.

I flashed the ROM (ver. 6.3) on my P600, and now when trying to flash 7.4 I get this message that Root is required.

I unlocked Developer Options, did Developer Options>Root Access>Apps and ADB, but I continue to get the same error... As if the device is not rooted.

Someone experienced the same?

Thank you!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi Josepr2012!

Press power and vol+ button at the same time. Release power button when bootscreen pops up, but hold vol+ until recovery starts! You can restart into recovery from power menu also or take an app like Quick reboot therefor.

Also make sure you are on TWRP2.6.3.3 because all others like 2.7 or 2.8 are buggy!

---------- Post added at 03:57 PM ---------- Previous post was at 03:53 PM ----------

Hi FiDuS80!

Try install SUsuperuser2.45 as app from playstore and make sure you update the binaries on normal way! And also make sure you are on TWRP2.6.3.3, because all other recovery's are buggy! And if you coming from 6.3 I would also recommend a clean install!

Here is TWRP2.6.3.3.zip for flashing in recovery. After flashing reboot into recovery, should say 2.6.3.3:

https://mega.co.nz/#!GZ8EHAiK!jeohl1juFhkB6V-4NL19JhCu-4Uwts7W__d6M7CplFE

Here is TWRP2.6.3.3.tar file for flashing via Odin3.09 if your recovery is broken:

https://mega.co.nz/#!mc0WBASI!12T9Khs53UzNvLFGPohfJhuTQ6YyTxKsEx_hiTV8-c0
[Galaxy Note 10.1 (2014 Edition) Android Developmen] FiDuS80:
Thank you very much! Everything is working now :D
[Galaxy Note 10.1 (2014 Edition) Android Developmen] josepr2012:
I was In TWRP 2.8.4 when it happened..My tablet don't pass the letters galaxy note..don't get to boot animation either, just stay in a loop so cant turn it on to use power button to recovery and vol+ power don't work...I will try to odin the TWRP recommended here and hopefully that makes the trick to be able to restore, otherwise will have to look for stock rom and start all over :(:(:( wish me luck and will report back...was the longest day at work looking forward to get home and fix this. Thanks for the support.

Sent from My SGH I317
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Seriously you shoukd use twrp 6 as indicated by olli as the latest versions will mess your device up, mainly by not flashing anything to partitions causing your boot loops
[Galaxy Note 10.1 (2014 Edition) Android Developmen] josepr2012:
Aleluya....MY tablet is back. It works flashing TWRP again with odin...PLEASE STAY AWAY FROM 2.8.4....The only reason I used is because was included in the instructions I used to root my tablet..Now back to 2.6.3 As suggested.. What a bad time, thought everything was lost

THANKS

Sent from my SM-P600
[Galaxy Note 10.1 (2014 Edition) Android Developmen] josepr2012:
Hmmmm...cant find the SuperUser app and when go to playstore to install it it doesnt give me the choice to install or open :confused:

EDIT: FOUND SU IN SETTINGS ...SORRY

Sent from my SM-P600
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
There u go.. Haha
[Galaxy Note 10.1 (2014 Edition) Android Developmen] josepr2012:
Can add Power Menu and Screen Record to Notification Drawer Tiles ?

Sent from my SM-P600
[Galaxy Note 10.1 (2014 Edition) Android Developmen] josepr2012:
Screen Record/Power Menu
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
V7.5 will have more qs tiles
[Galaxy Note 10.1 (2014 Edition) Android Developmen] temasek:
I was trying out Omni screen recording but it didn't have audio. Thus I'm staying put at the current screen recording for now - it has audio. With that no QS screen recording tile (for now).
[Galaxy Note 10.1 (2014 Edition) Android Developmen] josepr2012:
Just notice that my screen has been a little different than before...in someway I feel it less responsive, in other words is not smooth and sensitive as used to be...Not sure slaggy is the right word but it feels strange.

Sent from my SM-P600
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Can't answer for that. Mine seems alright to me
[Galaxy Note 10.1 (2014 Edition) Android Developmen] josepr2012:
Will follow up, otherwise will do a clean installation. I added a Tempered Glass Screen Protector but it was ok...anyway thanks for confirm.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi Tincmulc!

I think you got it!:highfive:

Thanks for the enlightenment! I never understood whats really wrong with the behavior and how to solve it!

I have played for weeks with the governor settings, incl. the hi_speed_freq. but never changed down to 650MHz, Lol! :eek:

I had planned to restore a 5.1 backup and wanted to make a screenshot from the governor table and then compare it with the table under 6.0, but that has no need now.

I was so close to a solution, but I think I would never got the secret without your help, Lol!

Many thanks! :good::good::good:

Immediately after changing the hi_speed_freq to 650 the CPU seems abruptly to use all frequencies and all seems solved for the time!

I'll have a futher look on this and if it's really solved all issues like battery drain, heating up problem and locked at max. freq. I would suggest to joshndroid setting this as a standard in the rom/kernel source.

If I could I would press thank button three times!

You can not imagine what I've tried everything?!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Zionator:
This ROM is crap I searched all over the net and all guides says the following :

: With system mounted in Read/Write (modification) mode, navigate to the folder: "/device/etc/sound". Find the file named "to3g" and tap on it, and then select to open the file as 'Text'.

The folders don't match any guides I can find. Has anyone found a way to increase ¿
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Speaker boost is your friend
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi DeanoD!

2.65 is the last stable version for 6.0 roms!

2.68beta and 2.71beta is build for android n roms what can cause some issues under 6.0! :(

So probably the best solution in the moment is to further use 2.65 stable!:good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] haimann95:
There are already Android N roms available?

Gesendet von meinem SM-T705 mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Android Developmen] 7786:
Android N preview roms are available for select Nexus phones and tablets.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] israel_andrade:
Looks like someone did his homework on this. BUT, how does the average person apply these same settings to their tablet. What, where, how did you make the changes? what app did you use? Help us NOOBS out once in awhile... :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
Can anyone check if infrared is working again and give a feedback?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
2.68 is for marshmallow, not Android n.

Open kernel adiutor, go to the CPU tab/section, open the governor turntables and then make the mentioned changes.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tony66:
no, no reaction
[Galaxy Note 10.1 (2014 Edition) Android Developmen] douger1957:
For what it's worth...

I have a Tab S and have CM13 on that as well. In that thread, the developer is insisting not to flash SuperSU, as it is not needed, at least in his implementation of the ROM. Enabling root in developer options should be all one needs to do for all root activities. Might that be part of the reason for the problems with this ROM?

I've only been on that ROM for a day, and the only problem I've noted was issues with screen rotation, which the dev says he thinks he has a fix for.

http://xdaforums.com/galaxy-tab-s/development/rom-cyanogenmod-13-0-sm-t700-16gb-t3310730
[Galaxy Note 10.1 (2014 Edition) Android Developmen] KingMooCow:
Has anyone else noticed 5ghz wi-fi being spotty? My lt03wifi doesn't see some 5ghz ssids at all, and it usually takes 3 or 4x longer than scanning 2.4, to see the one that it does. This wasn't a problem under temasek lollipop releases, wondering if I've missed a patch. clean flashed.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi KingMooCow,

wifi fully works on my side. :good:

I'm using 5,0ghz only with all my three devices running android 6.0 (2x Temasek/1x AICP)

Wlan scanning and connection is much faster as with Temasek 5.1, maybe two times faster.

Must be something on your side. :(

Are you coming from 5.1 touchwiz or have you ever flashed it?

I ask because the new bootloader, which can cause some issues on mm roms.

I know there is a how-to in this thread to switch back to 4.2.2 bootloader.

If needed you can take the search function therefor!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] KingMooCow:
it appears to have started seeing 5ghz networks after I sent into Wifi Settings>Advanced, and selected US Bands. Either that or it was completely coincidental and was a 8 hour lag in wanting to work. Dunno, works great now.

I was previously on a 5.1 version of Temasek. Thanks for the reply though.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] r4yN:
Try the following (you need a root file browser/explorer):

1. Replace the code within the /system/etc/wifi/nvram_net.txt file with the code inside of the /system/etc/wifi/nvram_mfg.txt file

OR (this is probably easier): Delete the original nvram_net.txt file, create a copy of nvram_mfg.txt and then rename the copy to "nvram_net.txt"

2. Reboot & Re-Connect to your Wi-Fi (this should happen automatically)

3. Choose the correct Wi-Fi Region/Country Code within the Advanced Wi-Fi Settings

4. Post your results (did this break/fix/improve/worsen your wi-fi)

The 2 files are very similar, yet have different values and I assume (I'm not a developer, I'm just trying to help!) that the _mfg file has the default (global) broadcom values, while the _net file contains samsung's own values (which differ from region to region)

(The _mfg file is also where I originally found the "ccode=ALL" & "regrev=0" values that made it into the rom)

If you're worried about breaking stuff, don't be. You can always just wipe system & re-flash the rom to restore the original values

Or you can create a copy of the original nvram_net.txt file, just in case ;)

In fact, it'd be great (& very helpful) if everyone could try these values and post their results (= if this broke/fixed their wifi and/or improved/worsened their wifi performance) :fingers-crossed:

I just did it myself and my wi-fi subjectively feels a little faster (but maybe that's just because I haven't rebooted in a while :angel:)

Edit: (it took me 30 minutes to write this, so I missed your last post, sry)

Alright, nevermind then... would be great if you could test the values anyway (and report if they improved/worsened your wifi performance)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Whistler1813:
In the US it's the upper 5GHz band (149-161) that it won't see with ccode=ALL. Never has.

As a routine when I flash a new version of the ROM and after it boots I go in and change the nvram_net.txt then reboot.

I don't consider my flash to be complete until I do that one last thing.

People who have their routers set to the lower 5Ghz band won't have to do this.

Also people who do use the high band 5GHz but have the same SSID for both 2.4 and 5GHz are falling back to 2.4GHz and they might not even notice it.

I use ccode=US and regrev=5 and everything works fine in 5Ghz.

AFAIK, If the ROM is set to ccode=US it will accept all but two 5GHz bands both of which only apply in Japan.

Of course some agencies might not like you using channels that aren't allowed in your country.

Source: http://en.wikipedia.org/wiki/List_of_WLAN_channels
[Galaxy Note 10.1 (2014 Edition) Android Developmen] r4yN:
1. ccode=US & regrev=5 breaks some of the 2.4GHz channels in Europe

2. When you tested ccode=ALL & regrev=0, did you set your country/region code to US (in the advanced Wi-Fi settings)?

3. Have you tried what I suggested above (it changes more than just the ccode and the regrev)?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Whistler1813:
I reverted to ALL and 0 manually, rebooted, set the US setting in Advanced, rebooted and 5GHz works fine.

I honestly never even thought to look in the advanced settings since I've been editing the txt file on auto-pilot since the HyperROM days. ;)

I did notice that the net.txt file still shows ALL and 0 when using the Advanced settings.

On the next ROM update I'm going to copy the net.txt file at default then choose US in Advanced and compare the two files along with the mfg file to see what changes. Just for curiosity's sake.

Thanks for your info on the Advanced settings!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hey R4yN,

I've done nothing special. Simple change county code to germany and choose "5ghz only".

I'm using channel 48 right now but I can "see and choose" all channels up to channel 161. (Look at the screenies below)

The connection speed is definately much faster as in 5.1(50-100%) and there's also a good performance boost but unfortunately also a lot more battery drain with marchmellow!!! (mabye +30-40%)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] yudi123:
Sound and screen distortion

This is very annoying i have a lot of distortion in sound and distortion in screen when i rotate it any fixes are there
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi Yudi123!

Welcome to the forum! You should read at least the OP, the first and the last few pages and/or use the search function in front of posting something! your questions are already answered several times!

BTW, screen distorsions are well known!

And about your crackling sound, if you ever have installed latest 5.1 touchwiz rom you have to revert from 5.1 to 4.2.2 bootloader to solve it!

There is a how-to in the thread!

The search function will friendly help to locate it!:highfive:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] yudi123:
Thanx man and sorry for the incovienience
[Galaxy Note 10.1 (2014 Edition) Android Developmen] r4yN:
I know, I read your post ;)

What I'd like to know is whether or not the additional changes (like I said it's not just the ccode & regrev) make any difference in terms of stability/speed/etc.

While I haven't noticed higher download/upload speeds per se, I have a feeling that the initial lag/latency is lower (e.g in the Google Play Strore & YouTube App there used to be like a 3-4 sec. delay before it started loading the content, now it's down to only 1-2 secs :D)

PS: I just realized that I have never actually told anyone about having to select the right country code in the advanced wi-fi settings, I've only ever mentioned changing ccode & regrev...

Apologies, that explains why some people were still having issues with their wi-fi despite the ccode=ALL & revreg=0 :silly:

(But in my defense: I thought that is was my excessive experimenting with different wi-fi values that broke my country code and not just the change to ccode=ALL & regrev=0 :angel:)

Maybe josh could add this to the OP? (FAQ: "Q: Have problems connecting to your Wi-Fi router? -> A: Make sure you have selected the correct region/country code in the advanced wi-fi settings!")
[Galaxy Note 10.1 (2014 Edition) Android Developmen] israel_andrade:
I just did a search for "revert from 5.1 to 4.2.2 bootloader". I found no such reference in this thread this ROM. Where specifically are you referring to.

Thanks in advance,

Israel
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tony66:
http://xdaforums.com/showpost.php?p=65631142&postcount=2293

Does that help?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hey Israel!

Already answered from [MENTION=4464885]Tony66[/MENTION]!

Thanks to him!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] edmondt:
Would it be possible to have a CM12 build where everything works? This is good as a beta?