yashsingh1/xdaforums huggingface dataset:
[Moto E Original Android Development] abacate123:
Thanks you very much, and I hope that get added soon, keep the awesome work.

And I hope the fast charge get added too, would be amazing!
[Moto E Original Android Development] gtsfreak:
Thanks Dev :)
[Moto E Original Android Development] sonrics1993:
Should I enable dt2w manually?

Or why it doesn't work, do I need to install the gesture app?
[Moto E Original Android Development] corphish:
Use the app
[Moto E Original Android Development] Adarsh1998:
Also worked for me using kernel Audituor
[Moto E Original Android Development] abacate123:
yes
[Moto E Original Android Development] Adarsh1998:
Don't ask same question in all threads
[Moto E Original Android Development] ivan290:
Only in 2 kernel's thread and why cant i do that?
[Moto E Original Android Development] abacate123:
Hey dev [MENTION=5822936]corphish[/MENTION], is it normal to keep a little red light on the proximity sensor when the screen is off? When it's on it disappear.
[Moto E Original Android Development] Adarsh1998:
U will get same answer everywhere
[Moto E Original Android Development] vkeyzzzz:
Even I wanna know this! ?
[Moto E Original Android Development] corphish:
It is.

What happens is, when the phone's screen is off, proximity sensor is on (little red light), to detect whether the phone is in pocket or not. Now for dt2w to work, touchscreen (and not the display) must be on always to read touches.

However in pocket, it should not read touches, so why should it be on while in pocket? Hence, when the proximity sensor detects whether phone is in pocket, it disables touchscreen and hence boosting battery life to some extent.
[Moto E Original Android Development] Ruvy:
[MENTION=5822936]corphish[/MENTION] Are frozen screen and deep sleep bug resolved ? or should i wait for an update ?
[Moto E Original Android Development] corphish:
Not yet.

Since many people are having issues with kernel with dt2w, I am putting up v2 link in the main thread.
[Moto E Original Android Development] vkeyzzzz:
Thanks for the info.

Anyways I am really not sure why ppl have screen freeze issue I have been using this kernel with cm12.1 and I haven't had any screen freeze not even once.

But sometimes I get in call proximity issue that's it...

Even battery life is cool with this kernel.
[Moto E Original Android Development] vinay001:
Screen freeze issues hpnd for me two times after unlocking nothing worked so a hard reboot fixed and proximity sensor pblm when some one calls screen won't turn off no pblms with outgoing , batter life is good ....

---------- Post added at 01:55 PM ---------- Previous post was at 01:49 PM ----------

V2 where I see only v1 and 1.3
[Moto E Original Android Development] corphish:
..v1.1..my bad

v1.2 had dt2w with broken accelerometer
[Moto E Original Android Development] abacate123:
Wow Thanks for the explanation, well done, now I get it.
[Moto E Original Android Development] jonaaa:
Would be nice if you do a 1.3 version with d2tw and a version without it... because i really hate dt2w, besides, your kernel is awesome :good:
[Moto E Original Android Development] abacate123:
Dev, sometimes with the dt2w I have to tap more than 2 times to unlock the screen... Fix it pls on the next release. Thanks.
[Moto E Original Android Development] vinay001:
[MENTION=5822936]corphish[/MENTION] AnTuTu Score is low compared to Stock Cm 12.1 Kernel in CM 12.1 i got around 15.2K with this 12.2K anyidea im on Zapdos v1.1
[Moto E Original Android Development] corphish:
Well, I dont believe in benchmarks, but, nothing really 'benchmark boosting' tweaks are added. But 3k difference is strange.

And if you are talking about the latest version of Antutu, many others got lesser than expected for many phones.
[Moto E Original Android Development] vinay001:
I don't know on stock Motorola 5.0.2 AnTuTu score was 14449 and on Cm 12.1 latest build it was 15200 and with Zapdos v1.1 12200..... and in stock Moto Cpu Minimum frequemcy is set to default 787MHz
[Moto E Original Android Development] jonaaa:
Don't believe on benchmarks, like i always say, benchmarks don't SHOW the real potential of the phone, if the phone is fast enough for you, benchmarks doesn't matter.
[Moto E Original Android Development] -CALIBAN666-:
at first i say,its a great kernel,but why we have no overclock at all,as far as i know it can be used for gpu+cpu oc,maybe as a test version or something,wen needed i test no problem,thanx,keep it up.
[Moto E Original Android Development] corphish:
Need to-do features for next version. I will try to update most of them (if any) and update kernel in 2-3 days. I won't be available after that for a while, however, will keep on supporting the thread when needed.

So reply with what needs to be done.

Cheers

To-Do List so far

1. Split Kernel into 2 branches (1 with dt2w and 1 without)

2. s2w+s2s and mm.

3. Charging current.
[Moto E Original Android Development] thwartfulGUY:
Charging is a bit slow... Other than that.. no problem faced.

Excellent Kernel! Waiting for s2w, s2s and music mod :)
[Moto E Original Android Development] brundark:
it's possible add suport for init.d? Thanks you for this kernel.
[Moto E Original Android Development] luvk1412:
Its already there
[Moto E Original Android Development] abacate123:
Waiting the update, it seems to be pretty good.
[Moto E Original Android Development] nisu4717:
I think that Sony kernal source is already out. It would be good to see stemina mod ported if possible. A best battery life
[Moto E Original Android Development] vinay001:
So there is no fix ? waiting for the update
[Moto E Original Android Development] abacate123:
Ok thanks for the tip.
[Moto E Original Android Development] matt4321:
Thread cleaned!

No need to argue and demand fixes for already known issues. You're always allowed to go back to stock which always works well.

Please keep it tidy in here.

Forum moderator,

matt4321
[Moto E Original Android Development] corphish:
Can anybody, if they are using Gesture Control App, post ScreenShot of the About section of the app. The SS must include device information (device name and all)?

TIA
[Moto E Original Android Development] luvk1412:
Here it is
[Moto E Original Android Development] corphish:
Okay, I admit I was busy with some other work these days, well, so busy that I missed a, er...'fight'.

As I had said earlier, upcoming updates will be pushed via OTA, and it will be done. OTA Engine is ready, and is implemented in the Gesture Control 1.5, which will be updated today.

So, today after some hours you will get an incremental update (just version change, nothing else) via OTA, to get you acquainted with OTA Update process. Don't worry, its simple. One-Click download and easy installation if on CWM based recovery.

I will notify you people when the app will be updated, and then notify you about the incremental update.

And I will also need some testers who are on Zapdos Kernel, to test OTA Update feature, just to make sure everything is alright.

Cheers,
[Moto E Original Android Development] Adarsh1998:
I'm on zapdos
[Moto E Original Android Development] abacate123:
I'm using zapdos.
[Moto E Original Android Development] luvk1412:
[MENTION=5822936]corphish[/MENTION] will this work on stock 5.1 by Motorola released recently
[Moto E Original Android Development] corphish:
Well, technically speaking, it should, but you never know.

As Zapdos uses AnyKernel Patching, so kernel is replaced, ramdisk remains as it is.

So it should work, but who knows.

And yes, I have rolled out an update to app. Please update it, as it will be used for downloading updates.
[Moto E Original Android Development] luvk1412:
Ya .. I just wanted to know whether it is compatible according to you or not... Thanks for replying will try and report
[Moto E Original Android Development] abacate123:
Yeah, I downloaded the app, waiting for the he next step.
[Moto E Original Android Development] abacate123:
Hey [MENTION=5822936]corphish[/MENTION], I received the OTA update and I downloaded and installed it, it really worked, thanks bro! Now you can push updates through that app xD a lot easier than coming here.
[Moto E Original Android Development] corphish:
You sure? As for other one, update hadn't come.
[Moto E Original Android Development] abacate123:
Yes ofc I'm sure. It even installed automatically through the open recovery script with my TWRP. Very impressive. It updated to the 1.4.

http://i.imgur.com/zd4tWHa.jpg
[Moto E Original Android Development] Adarsh1998:
U hv single sim device?
[Moto E Original Android Development] vinay001:
1.4 changelog kernel?
[Moto E Original Android Development] Adarsh1998:
Look like single sim only got update, we not got yet
[Moto E Original Android Development] corphish:
Nothing, just version incremental update, to initiate in-app updates

Can you post the ss of GC app, About section, which must show device info?

What it does is, this app detects the model from build.prop, and acts accordingly.
[Moto E Original Android Development] abacate123:
Dual sim here. You must update the gesture app to the 1.5 and then go get the ota.

And as corphish said guys, this update is just a test, nothing changed I guess.

http://i.imgur.com/cXDe2qs.jpg

---------- Post added at 06:49 AM ---------- Previous post was at 06:33 AM ----------

And [MENTION=5822936]corphish[/MENTION] is it possible to add a notification when the update is available? It can be a simple notification, just to tell us to go to the app and then update...
[General Accessories] c0nvict:
Hi guys,

This time i'm gonna review a great and very useful gadget from Hisgadget which i bought from here, it is the iClever 6-port Charger and let's get to it

The packaging is very nice and it indicates that the charger uses the SmartID Technology which means that it identifies the type of battery of the connected device and ensures rapid and optimal charging and with an input voltage of 110-220V AC this unit is also ideal for traveling

It is rated 50W 10A ensuring that you can use all 6 connections simultaneously and it also has a sturdy construction, excellent properties and reliable circuit that guarantee safe and long lifespan

Inside the package we find:

a user manual

a very cool Hiscard for the Super User Program and the Amazon Reviewer Program

the charger itself

the cable

The size is 100x69x27 mm and the weight is 180 grams

The charger is black and it has very nice velvet-rubbery feel to it incorporating the iClever logo on the side

On the front we see the 6 USB charging ports indicating the SmartID Technology, an operation led and the rating of each port which is 5V 2.4A

On the other side we have the cable input and on the bottom we find some information regarding the input and output

Input: 100-240V, 50~60 Hz 1200 mA max

Output: USB*6 5V/10A(Max); 2.4A (Max) per port

Here you can see the charger charging 7 devices. It may have 6 ports but if you have a cable like this one, you can charge even more devices and it doesn't even get warm

Pros:

6 charging ports

Very fast charging at 2.4A using SmartID Technology

No heat problems

Very Compact

Excellent build quality and feel

Relatively long cable

Price

Cons:

It only charges devices supporting 5V

Conclusion:

It is overall a great product and very useful to use when travelling replacing all the extra chargers you would have to carry with you

I personally use it on a daily basis to charge my devices and i am very satisfied by it's performance and liability so i definitely recommend it

For more info visit the Official Hisgadget Webpage

For orders visit the Amazon product link

You can watch my video review below in both English and Greek languages

English Review

Greek Review

Go here to see the review with pictures

P.S: If something is not allowed on this post, moderators please let me know and i will change it A.S.A.P
[Sony Xperia M4 Aqua] Saatvik Shukla:
Hello people.

I just came to the forums and since nothing is happening here visibly, i was wondering to do CyanogenMod bringup for the device :)

Dont forget the poll above

If there are people here, willing to help us out a bit, it would be good to do something here.

Post your hangouts here, if you are interested in what we are wanting to do.

We can use all the help available. Testing, dev-ing, etc! Just pool in everything we got and lets get rolling ;)

br

s :)
[Sony Xperia M4 Aqua] DoobyDroid:
I hope cm comes to this device I see ATM there's not a lot happening in the way of custom ROMs suppose its early days [emoji3]
[Sony Xperia M4 Aqua] jrmswell:
Yeah, although CM would be good at some point in the future, I don't know how useful it is at the moment since the phone is running pretty much stock android anyway with just minimal Sony skinning on top however it'd still be nice to see it as an option
[Sony Xperia M4 Aqua] banciii:
+1

(As soon as I will be able to buy it this week. :))
[Sony Xperia M4 Aqua] Desakato:
+1 ! Would be awesome
[Sony Xperia M4 Aqua] raymond016:
cant wait for a better rom for M4!
[Sony Xperia M4 Aqua] dongxi@:
+1

But now how can M4 Aqua ROOT ? , many root tools not support yet ?
[Sony Xperia M4 Aqua] zezadas:
have you tried kingroot? it works on z3 lollipop
[Sony Xperia M4 Aqua] banciii:
Today I bought E2303. ;)

zalcsooo@gmail.com
[Sony Xperia M4 Aqua] M4Aqua:
None of the rooting methods are working.

Cyanogen would be nice . . :)
[Sony Xperia M4 Aqua] PhilWee:
Cyanogenmod would be soooo nice to see on our phones! HW is great, but sony's software is crippling it...
[Sony Xperia M4 Aqua] ngoccong_892005:
who can root it???
[Sony Xperia M4 Aqua] ugjka:
Can't wait for CM. There is so much bloat in this phone
[Sony Xperia M4 Aqua] banciii:
Maybe in a few months :(
[Sony Xperia M4 Aqua] dadi11:
Have Sony released device/kernel sources? I'm planning to buy this phone and I can compile roms if it has open sources
[Sony Xperia M4 Aqua] Saatvik Shukla:
Nothing yet.

No BL unlock/root yet.

"Thread closed until there is something to do.
[Verizon Samsung Galaxy S 4] Surge1223:
Im requesting source for lollipop kernels for all Samsung US variants that Samsung has neglected to post. I would appreciate if other users would do the same by emailing Samsung via this link. Be sure to mention GPL requires source to be posted in a decent amount of time. Since lollipop has been out on some devices for some time I think this warrants that it be posted already. Especially with some variants (Verizon and AT&T note 4 specifically) having dm-verity activated as a kernel feature, effectively enabling write-protect on system thus stopping the ability of custom roms.

Thank you.
[Verizon Samsung Galaxy S 4] ThePublisher:
Done.

Got this email immediately afterwards.

------------------------------------------------------------

[SAMSUNG OSRC COMMENTS DELIVERY NOTIFICATION]

Dear Sir or Madam,

Thanks for your continuous interest in our products.

We received your request on OSRC.

We will provide the response ASAP, if your request is related to FOSS.

(This site is just for providing source code of FOSS Software we have used in our product.

You could contact with other types - ex. firmware - on your local Samsung support homepage.)

Thank you.

Sincerely yours,

-----------------------------------------------------------------------------------------

Samsung Open Source Release Center

E-mail:oss.request@samsung.com

* We received the request at [2015-05-25 04:28:41].
[Verizon Samsung Galaxy S 4] mike.s:
? There's no grace period at all, they're not allowed "a decent amount of time" to post source code. Simply put, any distribution of the code must be accompanied with the source. Not by the source being posted a day, week, month or year later, "accompanied." Anything else is a violation of the GPL.

These companies which don't simultaneously release source code are playing with fire. GPL2:

Almost any one of the kernel copyright holders (there are what, thousands of them?) could bring an infringement case which could terminate all rights to use the kernel. That means Samsung would no longer be able to use the Linux kernel in any product, forever. There's no mechanism to get the right to copy and distribute back. They're basically betting the future of their company on the patience and goodwill of others when they play games with not releasing source.

Someday, they are going to get sued, and when they realize the true ramifications of violating the GPL, some developer is going to get a multibillion dollar settlement to drop the case, and Samsung will start meeting its obligations.
[Verizon Samsung Galaxy S 4] PaulPizz:
Submitted request
[Verizon Samsung Galaxy S 4] CJ74753:
Submitted a request too.
[Verizon Samsung Galaxy S 4] Redflea:
Submitted.
[Verizon Samsung Galaxy S 4] liquidaluminum:
Request submitted.
[Verizon Samsung Galaxy S 4] efaden:
Done
[Verizon Samsung Galaxy S 4] KennyG123:
Actually the distribution of the binary can be accompanied with a written offer to provide source upon request. This is the part that carries no time requirement unfortunately. So what everyone here is doing is making a written request to provide source.

This is the paragraph that allows for that:

b) Accompany it with a written offer, valid for at least three

years, to give any third party, for a charge no more than your

cost of physically performing source distribution, a complete

machine-readable copy of the corresponding source code, to be

distributed under the terms of Sections 1 and 2 above on a medium

customarily used for software interchange; or

But for the most part you are correct and Samsung has in the past fulfilled their obligations by releasing kernel source before the OTA even started...that was one way we knew an OTA was coming. They have gotten sloppy probably due to so many devices still being updated. Too many manufacturers play it loose with the GPL.
[Verizon Samsung Galaxy S 4] drivel2787:
Request sent
[Verizon Samsung Galaxy S 4] mike.s:
Yes, and that's exactly what I was referring to. There's no need to get pedantic when explaining it, it's pretty straightforward and the intent is clear. Samsung obviously didn't include the source with the OTA. So, that's where the required "written offer" kicks in. (I don't see where they've included a written offer, either. But, I'll assume it's buried somewhere.) Most people fulfill the requirements by making a written offer of "go to this website to download source." As long as you can do that, it meets the requirement to

But, if you can't download the source, then it's not a valid offer, and the requirement is not being met.

The only situation in which "reasonable time" could play is when fulfillment is by physical media (e.g. by post).
[Verizon Samsung Galaxy S 4] KennyG123:
Sorry if I sounded pedantic. I do not believe there is malintent from Samsung...just sloppiness and things getting lost in the cracks when the company gets bigger and bigger.

I tore the GPL apart but could not find the phrase that used to be there...to be "released in a timely manner"...perhaps it was another site that translated the GPL into layman's terms...not sure. Hopefully this will make Samsung realize their oversight.
[Verizon Samsung Galaxy S 4] Surge1223:
Blasphemy. Samsung and Verizon are up to shenanigans again.

Formal request for new moderator to replace Kenny please.

:sly::sly:

I kid I kid
[Verizon Samsung Galaxy S 4] garyw10015:
Hey
[Verizon Samsung Galaxy S 4] drivel2787:
Got a response on this with a link but there is no code for COC4.

Mobile Phone	SM-N910A_NA	N910AUCU1COC2	SM-N910A_NA_LL_Opensource.zip	announcement	Inquiry Link

Mobile Phone	SM-N910A_NA	N910AUCU1ANIE	SM-N910A_NA_KK_Opensource.zip	announcement	Inquiry Link

Mobile Phone	SM-N910A_NA	N910AUCU1BNK3	SM-N910A_NA_KK_Opensource.zip	announcement	Inquiry Link

These are what are shown. I submitted a request again for COC4.
[Verizon Samsung Galaxy S 4] ryanbg:
It's ridiculous that the source code hasn't been released yet. While we're at it, the provided .configs are almost always NOT identical to the production .configs either. More recent kernels may have the config.gz inside the zImage, so always check, just in case. Luckily it's usually only a few causes, namely enabling Source Module Checksum or Modversions being enabled under Enable Kernel Module Support. There's a 4-byte CRC value created from the source of which it was compiled, and a SHA1 hash of the module. I personally feel that disabling kernel modules on a production device is necessary, but it's unfortunate you have no choice in the matter.

Side note:

They should separate Kernel and Platform source so I don't have to download 8 times the size of the kernel itself. On top of that, It's hard enough to connect to their circa-1990s' calculator of a server, and download at AOL 56k speeds.
[Verizon Samsung Galaxy S 4] XxD34THxX:
ROFLMAO

That said, I submitted as well. I got a crap ton of errors(it not liking my name). But I finally got a sent message...

Verizon in a few words: Amazing connections, horrid policies.

I wish I could go to T-Mobile, but the bill is the same and there isn't much of a T-mobile signal here. Only 3G.
[Verizon Samsung Galaxy S 4] XxD34THxX:
[MENTION=4939386]Surge1223[/MENTION]

Spoiler content hidden.

HAVE FUN. You probably already downloaded it and started to mess with it
[Verizon Samsung Galaxy S 4] Redflea:
Very cool! Ask and we shall receive. :)
[Verizon Samsung Galaxy S 4] Surge1223:
Nice I built after a few fix ups and flashed. Wifi works. Lol.
[Verizon Samsung Galaxy S 4] Redflea:
Fast. Are you going to put up an updated stock kernel?
[Verizon Samsung Galaxy S 4] Surge1223:
Is there demand for a stock kernel? I posted the kernel source in git so I suppose I could post it now.
[Verizon Samsung Galaxy S 4] Redflea:
Frankly, not sure...it could help w/troubleshooting issues ("is this the custom kernel I'm running, or something else"), or for those who just want a fully stock/rooted option. I was kinda asking in part since you had posted it before. :) Don't mean to add more work to your plate.
[Verizon Samsung Galaxy S 4] Surge1223:
Not at all, I had already made the kernel and zip. It's all good. I'll post it here in a sec

https://copy.com/hGorsGZxyHvqTNoQ
[Verizon Samsung Galaxy S 4] Redflea:
Cool!

So just flash it, Loki, and then give it a test drive, correct?
[Verizon Samsung Galaxy S 4] Surge1223:
No need to loki, i made the updater script check the kernel before it flashes it, and if not loki'd, it loki'es the kernel before boot.

Flash in twrp.

OC1 5.0.1 kernel for MDK. (yes wifi and bluetooth work)

https://copy.com/hGorsGZxyHvqTNoQ
[Verizon Samsung Galaxy S 4] Redflea:
Very nice! Thanks so much.
[Verizon Samsung Galaxy S 4] Redflea:
Just a note, I flashed this tonight on muniz_ri's ROM, and boot looped twice (once for 25 minutes, second time for 15 minutes).

Booted back to recovery, flashed kernel and Loki and then it booted normally and rebuilt the cache.

Maybe something in the script?
[Verizon Samsung Galaxy S 4] Surge1223:
I have his ROM flashed as well, the only difference I can think of is that I patched my linker to allow non-PiE executables... That could very well be it but I'd need to see a /cache/recovery/last_log to say for sure what the issue was... But you said it bootlooped? That suggests that the loki flash part of the script itself worked (since if you try to boot a non loki'd kernel then you'd get the firmware error screen). Maybe a permissions error on my part... Though odd I didn't have any issues in multiple flash tests. So you say it did boot for yo7 eventually though right?