yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Original Android Development] treszerotres:
I prefer to use the Perfmon.

there you select CPU and displays it in a floating window
[Galaxy Note II Original Android Development] AndreiLux:
I introduced ABB to test out the overclocking possibilities, you'll get 2GHz eventually, but seriously, the voltage bump and power draw is big and not worth it.

Anyway, correct about what you said. I'm busy on the S4 and will be for the foreseeable future.

If Samsung updates sources for 4.2.2, I'll do an update here and on the S3 for it, but no active development until the S4 kernel is brought up to feature equivalence in the following weeks.
[Galaxy Note II Original Android Development] Suicidal Chicken:
Hi guys,

It's been a while since I posted last. Life is getting busy, but i'm not complaining!

Something which has always happened with custom roms and kernel's, is this: My battery's on 84% and when I do a reboot - it goes to 87%. This is only an example, but you get the drift.

What's the cause of this exactly? I'm thinking variations between the battery module / chip and the phone's chip. Resetting battery stats doesn't do anything.
[Galaxy Note II Original Android Development] SirCanealot:
I'm on the Note II here. You think I'm really worried about power draw? ;)

There's just so many instances where I'm waiting on single core to do something, so I'd still love to have the option.

Anyway, thanks as usual for your hard work! :)
[Galaxy Note II Original Android Development] lainemac:
Anyone having problems with their proximity sensor? Sometimes my screen doesn't turn back on after calls.
[Galaxy Note II Original Android Development] SirCanealot:
I've had a few weird problems actually. But I've always assumed it's been gmd gesture control.

My face always triggers gestures before the screen turns off. So it takes it out of the normal call behaviour sometimes... Do you use anything like that?
[Galaxy Note II Original Android Development] Arslan Manzoor:
I just flashed this kernel on my Android rev rom just like I would flash any other kernel normally. And after flashing all my apps gone and settings resetted. Almost everything reset. Wtf :mad:
[Galaxy Note II Original Android Development] tuxonhtc:
Are you sure you didn't wipe data accidentally? There's no way that could happen after flashing the kernel. Your device could get bricked at worst - but data wipe never happens without you screwing up something.
[Galaxy Note II Original Android Development] ph03n!x:
Do you have a screenguard that covers the proximity sensor?
[Galaxy Note II Original Android Development] :
Any new updates coming? Or has this been abandoned for the shiny new s4?
[Galaxy Note II Original Android Development] cadmaster83:
I have same problem with this sensor without screen protector.

Отправлено с моего GT-N7100 через Tapatalk
[Galaxy Note II Original Android Development] lainemac:
+1 I don't use a screen protector at all.
[Galaxy Note II Original Android Development] Arslan Manzoor:
Actually I didn't flash it through recovery this time, I used mobile odin. I guess that app might have messed up something which it shouldn't, principally.
[Galaxy Note II Original Android Development] tuxonhtc:
Oh that's probably it then. You flashed tar with mobile ODIN right, not zip? Either way shouldn't have happened. Use CWM/TWRP etc from now on IMO to be on the safer side.
[Galaxy Note II Original Android Development] DubelBoom:
I have this problem to.

After calls screen wont turn back on, also after pressing the home/power button. I have to take out the battery.

Now I know its kernel and not rom related :)
[Galaxy Note II Original Android Development] lainemac:
I'm sure it will be taken care of soon. Hope so, can't go without this beast of kernel for too long... ;)
[Galaxy Note II Original Android Development] xcxa23:
hi, may i know whether did u change any setting in stweak eg:eek:C/UC or UV/OV??
[Galaxy Note II Original Android Development] DubelBoom:
I did do a slight under vold and under clock. Max is 1.5GHz, and I took all voltages about 3 steps down on S Tweaks.

Max GPU is 400 and something MHz and all undervolt about 1-2 steps in S Twekas.
[Galaxy Note II Original Android Development] xcxa23:
maybe ur gn2 cant handle the voltage well, thats y the screen would not wake. restore to the original value or just simply delete /data/.perseus folder, this will reset the setting. then try to reproduce to see whether problem still on or not
[Galaxy Note II Original Android Development] DubelBoom:
I doubt it because it's a light UV, and it did survive hard benchmarks such as the new t Rex one.

I talk on my phone less than once a week, so I can live with this. I prefer to save battery with the UV.

Thanks anyway :)
[Galaxy Note II Original Android Development] gubacsek:
ad-hoc wifi

Hi AndreiLux!

I would like to request a feature, but I'm not even sure where the problem is...

I would love to use ad-hoc wifi, to connect the phone to my laptop (I can't put the laptop card into Master mode, so can't use it as a hotspot)

In the last week i was researching this topic, I installed a chroot env to be able to use the normal linux commands (wireless tools) and finally I think the bottleneck is somewhere in the driver, this means in the kernel.

I'm absolutely no expert in this, but it seems for me I can't put the card in my note2 to ad-hoc mode:

localhost / # iwconfig wlan0 mode ad-hoc

Error for wireless request "Set Mode" (8B06) :

SET failed on device wlan0 ; Operation not supported.

localhost / #

I was trying to check kernel config, and find out what is missing but I have no idea. (googling for the right options to have a wireless card "ad-hoc" mode ready wasn't really successful... It seems it should work out-of-the-box)

The only thing that is missing compared to my laptop (which i can put into ad-hoc mode) is the "Generic IEEE 802.11 Networking Stack (mac80211)" CONFIG_MAC80211

But this is only a wild guess... I can't test it because if i compile the kernel, and flash the zimage, I can't boot the phone. (not related to this setting...)

I know this is not much to start, but if you think you'll look into it, please PM me, and I will give you more details (what i tried, and so on...)

I would really appreciate your help on this!
[Galaxy Note II Original Android Development] lainemac:
I haven't done any type of underclocking. I was running at 1.8ghz.
[Galaxy Note II Original Android Development] Old faithful:
And you're wondering why its not working? Have you at least tried with default stweaks settings, or did I miss something?

Sorry for reacting so brashly... I just saw that you responded to this later on . But I can confirm that a SLIGHT voltage difference is all it takes to 'break' it ;)

PS: using the OP ' tweaks worked fine for me while testing but applying these settings on boot resulted in a boot loop. so I reverted 2 more conservative settings of two steps undervoltage for all clock speeds and it's been working fine from there on.

It seems obvious to me now that every microprocessor has slightly different needs therefore something that works for you may not work for me and vice versa.

Sent from my Samsung Galaxy Note 2

---------- Post added at 04:42 PM ---------- Previous post was at 04:07 PM ----------

While we're on the subject of feature requests... Is there a way to include into the kernel USB Mass Storage like with previous versions of Android?

I am surprised this essential feature request hasn't been forwarded before, since it has been removed from the latest versions of jelly bean and we have been forced to use workarounds, such as SGS3 UMS. As this is a klutz that is likely to stop working in future versions of Android and newer hardware, how are we going to be able to access the file system in the future?

In other words, we need a solid way to directly access ALL files on the device from the PC without all the aggravations, instabilities and date mangling problems that come with MTP.

Are there any plans for restoring it?

Sent from my Samsung Galaxy Note 2
[Galaxy Note II Original Android Development] SirCanealot:
Wow, that's amazing. You know we discussed this literally 5-10 posts up? :p

And even Mr. Andrei himself answered.
[Galaxy Note II Original Android Development] EarlZ:
No issue here.
[Galaxy Note II Original Android Development] tuxonhtc:
Had absolutely zero issues with Perseus till the last day I used it. And I'd been using it for ages. Didn't mess about with UV/OC though.
[Galaxy Note II Original Android Development] neol23:
How can I export my Stweaks settings and share them?

Or there is a file somewhere, where they are contained? :)

Everyrhing worsk perfect for me, great performance, great battery life!

Imega v16+perseus v36.3+simplistic (free, just drop-down menu)+Xposed with several tweaks activated.

Thanks XDA, I love my Note! :)
[Galaxy Note II Original Android Development] ppn7:
Hi

I have a asv1 chip. I read previously that is a bad Chip and default settings are 750mv for ABB. What should i put for the best settings? 800mv?

Thanks
[Galaxy Note II Original Android Development] tuxonhtc:
STweaks profile: http://xdaforums.com/showthread.php?t=2034981
[Galaxy Note II Original Android Development] baileyjr:
Guys, I've ordered a wireless charging coil and charger to play with. I know the kernel lets us tweak the charging currents but has anyone got any real world experience of doing this with the wireless charging? If so what results did you get?
[Galaxy Note II Original Android Development] mkanet:
I am also curious about this. From what I read, at least on the Note 2, the wireless charging rate is signficantly slower than USB charging.
[Galaxy Note II Original Android Development] baileyjr:
The hardare should support up to 1000Ma with the correct kernel. Allow 100Ma or more for built in safty variations etc... I would be more than happy with 800-900Ma just form a convenience point of view... The standard 460Ma is a bit pants though :p
[Galaxy Note II Original Android Development] tuxonhtc:
What voltages do you guys use? Input current for faster charging via USB?
[Galaxy Note II Original Android Development] pageniao:
great battery
[Galaxy Note II Original Android Development] gefilus:
This kernel works for aokp roms?
[Galaxy Note II Original Android Development] lainemac:
No.
[Galaxy Note II Original Android Development] baileyjr:
I just use the stock voltages. And I usb charge at 1000Ma.
[Galaxy Note II Original Android Development] Old faithful:
I'd be careful about that.You must make sure that your motherboard can supply the actual 1000 milliamps.

Sent from my Samsung Galaxy Note 2 using mostly Google Voice
[Galaxy Note II Original Android Development] berkos:
For now im stable with 1000mV across slices, im also on asv 1
[Galaxy Note II Original Android Development] garyd9:
It's not supposed to "save." The sysfs interfaces (and values put in there) exist only as long as the kernel is in memory. Wipe the kernel out of memory (such as when rebooting) and the values are also gone.

Want them to persist over a reboot? Then put them in a script that gets run on each reboot. Search for "init.d" for some hints.
[Galaxy Note II Original Android Development] AndreiLux:
Updated with a minor feature addition. Also uploaded N7105 version to OP.

I'm also secretly crossing my fingers in hoping I didn't mess up after the fiasco in the morning. :eek:
[Galaxy Note II Original Android Development] D3_:
Don't worry, this one boots fine :P
[Galaxy Note II Original Android Development] fishingfon:
Hi, i have sent you (the op) a pm.

Cheers

Corey
[Galaxy Note II Original Android Development] AndreiLux:
Yes, and I ignored it. I'm not a helpdesk nor am I a substitute for Google.

http://tiad8.com/threads/nand-how-to-unpack-repack-boot-img-recovery-img.839/

I didn't take terribly long to search and find that.

I'm happy to respond to advanced or more complicated kernel business but not such basic stuff.
[Galaxy Note II Original Android Development] garyd9:
(slightly off topic..)

Okay, I've seen this before in logical constructs, but I've never been given an explanation why people do double negatives in this situation:

if(!!time_enable)
do_time_slice(mali_policy.currentStep);

Why? time_enable is an int... "if (time_enable)..." evals to true if any single bit in the integer is on. So does "if (!!time_enable)..."

!time_enable == !(!!time_enable)

It might make sense if used as a rvalue (x = !!time_enable) as it would force 'x' to either be 0 or a known non-zero (usually 1) -- but why in an "if" statement?

It doesn't really matter - the compiler should optimize it out.. but in over 25 years of writing code, I can still learn something if I bother to ask. (I suppose it just might be a safety habit?)
[Galaxy Note II Original Android Development] AndreiLux:
Well it is exactly what you say, just to convert a arbitrary value into a sure boolean 0 or 1. It's the closest thing to a cast to bool in C. People generally use it if they really don't know the format of the input is in and use it as sanitation in other programming languages where the equivalent of _Bool false doesn't solely apply to 0. I guess in this particular case it's not really needed, you're right.
[Galaxy Note II Original Android Development] garyd9:
From drivers/battery/samsung_battery.c, the values used for different charging sources:

TYPE_MAINS: chg_curr_ta

TYPE_USB: chg_curr_usb

TYPE_USB_CDP: chg_curr_cdp

TYPE_DOCK: (varies on the dock type)

TYPE_WIRELESS: chg_curr_wpc

So, based on that, I think having the wpc up to 900 might be dangerous for people sticking palm pre charging coils in the back of their phone. (The verizon coil is rated for a higher current - and the source reflects that by setting wpc to 650.)

On an odd side-note: chg_curr_etc is never used anywhere in the kernel...

take care

Gary

edit: damn... I was trying to avoid messing with the kernel on this phone. See what you MADE me do??? ;)
[Galaxy Note II Original Android Development] rainyguy:
Working for my n7105.

Thanks !
[Galaxy Note II Original Android Development] garyd9:
Okay, so it's just a "good habit" type of thing. I was starting to go nuts thinking that someone added a new operator (!!) to the C language.

Another question: Do you prefer github pushes or another mechanism for suggesting code changes? I'm okay with just sticking them here in the forum - mostly because I know it annoys the moderators when actual development occurs in the development forum.

Thanks

Gary
[Galaxy Note II Original Android Development] AndreiLux:
What the hell? I know some forums here have some bit of overzealous moderators but I never heard of that.

You're welcome to discuss anything in this thread right here as you please, and so is everybody else as long as it is constructive to some topic.

If you do Github pull requests then make sure the code is fine and tested, else I prefer if you just sent me the commit/patch via PM, or just post it here if it is something minor. I want to keep the repository relatively clean.

As for the wireless charging, thank you for looking for me. One thing I do not quite understand is what exactly limits the current flowing via induction, the charger dock itself must have some kind of limitation as it cannot simply work at some silly high to medium currents and it's just the phone that limits it. Any way I'll revert that in the next hotfix version.
[Galaxy Note II Original Android Development] tdc7777_3:
Flashed 25.3, it works very well, no problems so far.

Thanks for your works, mate
[Galaxy Note II Original Android Development] aussiebum:
Hi, Does the latest perseus kernel for the N7100 support tun?

I took a look in /lib/modules and didn't see tun.ko, and didn't find the word tun or openvpn mentioned in this thread.

Thanks!

Sent from my Galaxy Note 2
[Galaxy Note II Original Android Development] garyd9:
The current has to be regulated by whatever is consuming the power while the voltage is regulated by whatever is providing the power. The charger is rated for a current, but short of certain types of protection circuitry, there's no way to prevent a device from pulling more current than the charger is rated for.

This is why the default for USB charging is usually 450 milliamps... The USB 2.0 spec only requires that the port provide 500 milliamps. If the phone tries to pull more than that, and the source can't provide it, it can damage the USB port. (Usually, it can provide it, but the components can't handle the heat generated from the power flow.)

In practice most USB 2.0 ports these days can provide quite a bit more than 500mA safely... and should contain some type of safety fusing to prevent damage to a component other than the USB system itself. I wouldn't want to try pulling 900mA from a cheap no-name budget-bin netbook, though.

In terms of the inductive coil, however, it's a good question. Wireless energy transfer from induction is a theory that I learned in order to pass my amateur radio exams, and then promptly forgot. The induction coils usually have a small circuit for regulating the voltage and "smoothing" out the power. So, if too much current is pulled, my GUESS is that either the voltage would drop or that the circuit would fail. A failed circuit might result in it just not working anymore, or it might result in a quick "poof" (and the resulting burned parts.)

Can I make a suggestion? Don't change the defaults for the charging currents. While most USB ports should be able to handle 900mA, some won't be able to. It'd suck for some clueless newbie to burn out a port on their notebook... Perhaps add something in sysfs for setting the charging current and leave people to their own follies. If people root their device and change a sysfs parameter, then any possible damage is their own damn fault...

(Pardon my paranoia here - I live in the USA which is often known as the Land Of Litigation.)

Take care

Gary
[Galaxy Note II Original Android Development] AndreiLux:
Somebody with a wireless changing kit needs to pay guinea pig with this, I'd test it myself if I had one.

We've had the USB charging rate fixed to 900 on several kernels on the S3 and had simple sysinterfaces to configuration apps setting it that high since the S2, and I haven't heard or seen in these 1.5 years campaign about anything broken. Actually I'm pretty sure USB ports have their own limitation as for example this setting on my desktop PC didn't increase the charging time by a bit. You can actually see the real charging rate by the charger chip in /sys/devices/platform/samsung-battery/power-supply/battery/current_now . So as far as that setting is concerned I prefer keeping it as is instead of people complaining at me because of slow charging.
[Galaxy Note II Original Android Development] garyd9:
On further study... It looks like the max77693 charging chip actually tries to lower the current when the power is unstable. Using the 900mA default for USB (and plugged into a cheap unpowered USB hub), I watched the kernel drop the input current to 600mA. Digging in the kernel log, I'm seeing entries like this:

[ 7445.902458] c0 max77693_charger_irq: abnormal power state: chgin(0), vb(1), chg(1)
[ 7445.902998] c0 max77693_reduce_input: 900mA to 800mA
...
[ 7445.953370] c0 max77693_softreg_work: unstable power
[ 7445.953891] c0 max77693_reduce_input: 800mA to 700mA
...
[ 7446.003328] c0 max77693_softreg_work: stable power, reduce 1 more step for margin
[ 7446.003845] c0 max77693_reduce_input: 700mA to 600mA
[ 7446.506585] c0 max77693_set_input_current: now in soft regulation loop: 600

That's pretty cool. In < 1/10th of a second, it dropped 200mA for stable power, and then another 100mA as a safety margin.

(I still think it'd be a good idea to drop the defaults back to the originals and force the user to reconfigure via sysfs if they want to push their own hardware.)

One thing that's really annoying me is that the charging chip is reporting mixed messages: The input current was dropped to 600mA (and is reported properly), but it's also reporting the charging current as 899mA at the same time (which isn't possible without an additional power source):

[10647.289987] c0 [259] bat: s(100, 18), v(4330, 19), t(27.1), cs(4, 4), cb(3), cr(899, 600), f(1), t(3201)

The "cr(x,y)" is the current values. The first is the charge current and the second is the input current. Both are pulled from the i2c interface in realtime, so I'm not seeing stale data. What does that bother me? Because it means there's no reliable way to get the REAL charging current... all I can do is guess based on the charging and input currents.

This is probably a bug in the max77693 code, but without the documentation for that chip, I'd be blind trying to fix it.

(and the current_now in sysfs also shows the incorrect value.)
[Galaxy Note II Original Android Development] lqrt:
Wow. I feel like I'm transported to another world. But nice read nonetheless :)

Question. How is it that kernels seem so universal yet the roms are not? Perseus is so easily ported from s3 to s3 lte to note 2. .
[Galaxy Note II Original Android Development] spitbull46:
overcloc gpu

someone help me with overclocking gpu and voltage..
[Galaxy Note II Original Android Development] SandeepEmekar:
@AndreiLux:

Please can you add bootanimation support? :D
[Galaxy Note II Original Android Development] Bholwell:
GPU Undervolt Overclock N7100

Are there any Apps that allow simply GPU Overclock/Undervolt? like ns tools etc?

a few people asking but no answers, does that mean it cant be done without using scripts?

My wifes S3 uses Siyah kernal that NS tools (i think or Stweeks) can adjust gpu volts and clocks, can Perseus be adapted to use something like that?

Thanks in advance
[Galaxy Note II Original Android Development] ppn7:
For those who get lag. Just try to not under clock the mini frequency from 160mhz to 108mhz and install disable scrolling cache and sqlite tweak.

Now I'm really happy. I have screen calibration, the best battery life from all kernel and no lag issues!
[Galaxy Note II Original Android Development] Old faithful:
Would you care to elaborate?

Sent from my Note 2 - Text mostly by Google Voice, accuracy not guaranteed ;)
[Galaxy Note II Original Android Development] ppn7:
I was talking about gpu frequency. I used to underclock minimul frequency of gpu from 160mhz to 108mhz and that's the reason i got lag animation. For scrolling lag just disable scrolling cache and installed sqlite tweak when i flashed phoenix rom in aroma installer.

And i read somewhere that undervolt may cause some lag issue. Don't abuser of undervolt cpu/gpu. I just did -100mv for cpu and -50mv for gpu and I'm fine.

I didn't touched frequency responsiveness. All settings are défaut except underclock 1100mhz cpu and gpu at 440mhz.
[Galaxy Note II Original Android Development] m666p:
Would someone share their edge-enhancement settings for ui...

I can't seem to reach that point where small text doesn't have fuzzy edges...

Note 2(GT-7100)

Rom = Omega latest

(Apex@onyx black,Wallpaper@galaxy pack)

Kernel = Perseus latest

(Cpu 1.7@1175000mV,Gpu 733@1075mV)
[Galaxy Note II Original Android Development] jonkers71:
Have no idea how you guys are getting 8hrs of scrwen on time. I am uv/uc and the most I can manage is about 4hrs.
[Galaxy Note II Original Android Development] Old faithful:
I understand about the GPU frequency and voltage but how do you disable the scrolling cache in the Perseus kernel itself?

Sent from my Note 2 - Text mostly by Google Voice, accuracy not guaranteed ;)
[Galaxy Note II Original Android Development] ppn7:
Sorry you can't do this on the kernel. It's a .zip you have to flash with recovery. But i installed it when i flashed pheonix rom. It's an option with aroma installer like sqlite tweak.
[Galaxy Note II Original Android Development] iba21:
Guyz.. one stupid question

Stweak.. screen.. britness reduction is 75

If i put that value to 0.. i'll have more brit under the sun? Because it's difficult to read text when i'm under the sun.. have to increase the brit.. and sure.. value is at max possible in rom choise
[Galaxy Note II Original Android Development] rowihel2012:
does the last kernel v36

fix the emmc brick problem? and the sudden death happening ?
[Galaxy Note II Original Android Development] myaslioglu:
Seriously??