yashsingh1/xdaforums huggingface dataset:
[General Topics] andytl:
Reply from the seller

This is the reply I got from the seller NOT from me personally as from following post it looks if it was me IT IS NOT just to make it as clear as day (and if the mods wish to ban the seller) they can PM me and I will send his name.

I've put an ADD on email with a step by step guide to flash the devices.I've seen a lot of "mod" people bricking their devices due to a bad explanation of the flashing process,complicated links,corrupted files and so on.IE: I myself colected information from a developer site and tried to flash an Imate Jam and after the process was done...it was bricked!!!End of story I ended up with a worthless device and no support whatsoever!!!

So I had this idea of making a friendly step by step guide and offering a support to the buyers in case the flash process goes wrong. And don't tell me it is a risk free process...For instace from the 15 roms I've sold out I had to give support for 3 buyers that even with the step by step guide they manage to not completely follow the steps and needed extra support (such as special roms that are able to recover half bricked devices).

So what I actually offer is a lower risk to the buyers.Up to 85% of my buyers know that these tool I'm selling might be "free" elsewhere. But this "free" means no support as well.So this is a great value for money choice as all the tec stuff and tools needed are gathered together with download links,explanation,step by step guide and support by email or msn or even by phone in English, Portuguese or Spanish.

So this is what I offer. Part of the money gathered are sent to the development site so we can keep improving HTC devices.

Best Regards

(I do have his name but not that evil to post it)
[General Topics] Reichi:
sure, that's why you want 8 Bucks for the Download right?

You suck guy, no one here will believe your stupid "oh i did nothing wrong" bull....

You tried to earn Money with other peoples work and with non-licensed software. You can't deny that and that's exactly why you should be banned out of every single ppc-board (this, pdamobiz, etc) forever.

Everyone gets support here within a few hours, i don't think some like you is only even almost able to replace all the knowledge of the pplz in this and other ppc-boards.

So got and tell your fairytales some who is stupid enough to believe you.
[General Topics] StellaDel:
Reply to the seller

Whether you offered support or not is not applicable, the simple fact is you tried to profiteer from other peoples work without their permission.

You broke the ethics of this board in doing so, caused a certain amount of distress - these actions you took without consideration to the developers, or board members.

If you believe you perceived intentions were honourable and justified then that is your opinion. I believe as do others that posted on this topic you were wrong to do so, as apparently do Ebay.
[Xperia Z1 General] su86bd:
HERE IS LATEST FTF FILE FOR XPERIA Z1 C6903

{FTF} C6903_14.4.A.0.157_Customized_UK

DOWNLOAD & FLASH WITH FLASHTOOL .... IF YOU WANT TO ROOT YOUR DEVICE PLEASE FIND XPERIA Z1 ROOTING THREAD FROM XDA OR GOOGLE.

DOWNLOAD LINK: MEGA

https://mega.co.nz/#!P9o3jAyY!8PtXraxVhAsvCdkjbRcHgZrk5QaJ-xR-LHe2C2DoGrA

ENJOY.....
[Nexus 7 Q&A, Help & Troubleshooting] Philip:
I have been offered a 2012 Nexus 7c (part ASUS-1B32-4G) with a Date of 2013.02 on the box.

The seller says that the "4G" at the end of the part number means that it supports 4G data (which I take to mean LTE here in the UK), but my internet research on this has been inconclusive.

Can anybody confirm or deny that this model supports 4G (LTE), or is it only 3G (HSPA+)?

Many thanks!
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] beegeero:
Request permission to modify TouchWiz UX 5.0 By NaTHaN

Hello NaTHaN,

Thanks for TouchWiz UX 5.0.

I tested several stock ROMs, but this I liked the most, and I decided to change it a little, for my future project.

Of course the ROM, because it is made by you, your name will be remembered as a developer.

Please give me the permission to modify a little this ROM.

Thank You.
[Xperia Z3 Compact Original Android Development] someone755:
༼ つ ◕_◕ ༽つIn the name of our great lord Helix!༼ つ ◕_◕ ༽つ

Welcome to the first custom CM12 kernel for the Z3 Compact

Kernel12

We're going on an adventure!​

AMAZING FEATURES:

They happen to change so often that you're better off checking the changelog, but if you're stubborn, here's the core ones:

Additional CPU and GPU steps

Faux123's Intelli_plug and Intelli_thermal

adreno_idler

Memory fixes up the arse

Countless battery life and overall performance optimizations

A reason for Myself5 to, as he says, compete

Custom installer that combines both the permissive and enforcing image in one tiny zip

Obviously there's more so go ahead and check my Github!

DOWNLOADS:

http://j.mp/kernel12-1

Generously hosted by Androidfilehost.com

Note that the newest old (stable or not) builds (CM 12.0) are still available on the original site for now: http://bit.ly/kernel12

HOW-TO:

* Use TWRP

* Flash zip

* Read what the zip tells you

SERIOUS DISCLAIMER!

I guarantee nothing except for squids taking over our planet by the year 3027. #squidmasterrace

I'd also like to point out that the kernel developers for this device are different people with different lives, schedules and priorities, which shows in many differences in their work. We are not enemies or competitors but rather friends and colleagues, but we each support what we do as we are able to and as we deem is best.​

Kernel sources: https://github.com/someone755/android_kernel_sony_msm8974 (cm12.x)

https://github.com/someone755/android_kernel_sony_msm8974-1 (cm14/lineageos 14)

༼ つ ◕_◕ ༽つPRAISE HELIX༼ つ ◕_◕ ༽つ

XDA:DevDB Information

Kernel12, Kernel for the Sony Xperia Z3 Compact

Contributors

someone755

Kernel Special Features:

Version Information

Status: Stable

Current Stable Version: r_12

Stable Release Date: 2017-10-30

Created 2015-02-22

Last Updated 2017-10-30
[Xperia Z3 Compact Original Android Development] someone755:
A quick FAQ that you'd better read before posting.

1. What was up with the nonsense naming scheme before 12.1?

A: Back then I believed people would actually test the unstable builds I pushed out very often, but I found out only a minority did so. With 12.1, I've decided to turn a new leaf and try to merge the two -- the builds won't be as extensively tested as the stable ones were before, but they will be released faster.

For now, all you need to know is that rperm means permissive and renf means enforcing builds.

2. How do I flash this?

A: Flash through recovery and read what the recovery tells you.

3. My bootloader is locked, HALP!

OR

I'm on stock/AOSP/CM7.

A: Then you don't get to install this kernel. Pretty simple but still, tough luck.

4.. What app do you recommend for dealing with CPU settings?

A: TricksterMod and Kernel Auditor work for me. Go around the internet, try different apps and see what works for you, then keep it.

5. Touch Control doesn't work in rXXX release, you suckas, fix plixe!

OR

My phone exploded, HALP!

A: Go away. I do not respond to bug reports without a proper description and log.

6. I have a bug to report!

A: Great! Unlike the guy in #5, you may submit the error either to DevDB or in the thread (just tag me if you're posting into the thread). Make sure your description of the error is detailed, and that you have a log (located in /proc/last_kmsg). It'd be best to upload the log via pastie.org If possible, please also list the way in which the error was triggered.

7. I want to support you and your work!

A: Awesome! Click thanks and/or share the thread with other guinea pigs who would like to participate!

8. OP is arrogant, I'm gonna call the Internet Police?

OR

Why are you such a derp and asshole

A: Indeed I am. Deal with it.

9. Where may I find the discussion thread?

A: This thread serves as both the development and discussion thread. Please to not litter (GTFO with "thanks" and "+1" posts), and try to keep to the topic. That said, if you're reporting a bug or requesting a new feature, you may use either DevDB or the thread, but please tag me should you opt for the latter. Just remember, reviews go in the "Reviews" tab!

Special shoutouts to (in no particular order, all help is equal help):

AndroPlus

funiewski

Myself5

sm4tik

nelvinchi

franciscofranco

Freexperia and jerpelea

faux123

Google, Sony and HTC

All Nozomi developers!
[Xperia Z3 Compact Original Android Development] someone755:
EXTREME CHANGELOG:

Releases since r_08: http://bit.ly/changelog12-1 (Nougat/Android 7.0)

Releases r_05 to r_07: http://bit.ly/changelog12 (Lollipop/Android 5.x)

Releases pre-r_05:

for a more detailed changelog, check my GitHub (although you're probably better off not doing that)

for STABLE BUILDS
[*] r_05 ### 16/8/2015	***UPDATE***
-merge upstream CM commits (more WiFi commits)
-enable adreno_idler to reduce GPU frequency spikes
-even more fixes to the installer

[*] r_04 ### 30/7/2015	***UPDATE***
-enable screen color control
-downgrade powersuspend to a version that Kernel Adiutor supports
-more memory tweaks
-fix a bug that caused the CPU to spike after thermal throttling kicked in
-enable a 2.5 GHz CPU step
-introduce some fixes to the new installer (code is _still_ dirty -- I'll be working on it)

[*] r_03 ### 29/7/2015	***UPDATE***
-enable F2FS
-fix the 268 MHz and 2419 MHz steps and allow voltage control
-use the already-existing ramdisk instead of using our own
-merge the permissive and enforcing image into a single zip -- let the user choose what to do on install

[*] r_02 ### 18/7/2015	***UPDATE***
-merge upstream CM commits (wifi updates)
-upgrade intelli_plug to 4.0
-improve GPU driver and allow apps to use more RAM
-introduce 268 MHz and 2419 MHz CPU frequencies
-disable mpdecision and enable intelli_plug in its place
-enable intelli_thermal by default, set throttling point to ~80°C and poll time to 3 seconds

[*] r_01 ### 18/7/2015	***UPDATE***
-merge upstream CM commits, update the whole thing to better work with lp-mr1
-downgrade intelli_plug to 3.9 as 4.0 was causing issues -- future TODO!
-bring kexec support to stable builds (multirom is finally supported)
-move to a new download host (androidfilehost)
-go back to CM ramdisk

[*] O3 ### 15/4/2015	***UPDATE***
-update intelli_plug
-disable Qualcomm's MP-Decision and enable intelli_plug by default
-merged CM upstream commits (including a LOT of wifi fixes)
-power (powersuspend) and fs tweaks

[*] O2 ### 12/3/2015	***UPDATE***
-Motorola memutils
-upstream CM commits
-faux123's snake charmer
-intelliactive CPU governor
-kexec_hardboot
-removed recovery from the ramdisk; we're using the FOTA partition as recovery, and we save 3MB on size

[*] O1b ### 10/3/2015	***UPDATE***
-LZ4 kernel compression
O1b	### 7/3/2015	***UPDATE***
-upstream CM commits
-asynchronous file sync (reduces IO latency by as much as 34%)
-screen color calibration (KCAL)

[*] O1 ### 25/2/2015	***UPDATE***
-GPU OC to 657 MHz, added 100 MHz step
-GPU idle set to 27 MHz
-KSM
-FSYNC
-intelli_plug
-intelli_thermal
-voltage control

I hope you like the colors.

Sorry for having 3 OPs, but I'd rather have more than 1 long one.
[Xperia Z3 Compact Original Android Development] C2fifield:
First off, thank you so much! There's been a massive lack of kernels for our device. Now for my real question, is there any chance you could make a Selinux Permissive variant so we can get xposed working? I'm only asking because you seem to be the only one with a CM12 kernel out :good:

EDIT: Never saw the tabs for feature requests in a thread before, so this should probably go there, my mistake.
[Xperia Z3 Compact Original Android Development] someone755:
Hello yes I would like to science please.

I'll see what I can do, the layout of a boot image has changed drastically since 2012. xD

EDIT: [MENTION=4543824]C2fifield[/MENTION]: No biggie, I don't mind feature requests in the thread. To be honest I don't mind anything as long as it's about this kernel/thread.

EDIT2: I've spent two hours trying to set SELinux to Permissive. What I managed to create were a handful of ramdisks that were supposed to change it to permissive (but didn't) and a zImage that completely disables SELinux.

If anyone knows what in the world I have to do for permissive, please let me know. So far everything I've found on the internet about this is how to type "setenforce 0" in a su shell.

EDIT3: I am an idiot. Continue with your lives, the Permissive image will be up in a few minutes.
[Xperia Z3 Compact Original Android Development] was12:
You can use this method.

http://xdaforums.com/showpost.php?p=58887725&postcount=230
[Xperia Z3 Compact Original Android Development] someone755:
It's alright, I already figured it out. What C2 wanted, if I understood correctly, was for init and onwards to be permissive. If I read that correctly, your proposal only turns SELinux into permissive on Android boot.

I don't know if this makes sense and it may or not be wrong.

EDIT: Also tried your suggested way, didn't work for me.
[Xperia Z3 Compact Original Android Development] was12:
Try this. Create su.d folder in /system/ and create a text file that permissive.sh and insert code in permissive.sh and give permissions 755 to both folder and file.

#!/system/bin/sh
setenforce 0

He wanted to get xposed working. This way makes system permissive on boot and lets xposed framework working properly. This way works for him.

And also thanks for your kernel. Do you consider adding more features to your kernel such as OC,KSM,etc. ??
[Xperia Z3 Compact Original Android Development] someone755:
That sounds more like it! Still though, I've found it's only one line when putting the boot.img together:

androidboot.selinux=permissive

Ofc I intend to add more, you didn't think I'd open a thread for just two cherry picks? xD

Looking into a lot of things, my GitHub isn't even half of what I decide to push. KSM is literally just one push of a button in the config, and I just need to cherry-pick others and get them to work (the latter is really where most of the work is at, there's a lot of trial and error).
[Xperia Z3 Compact Original Android Development] Zwulf:
[MENTION=4275152]someone755[/MENTION] thanks for your kernel! :)

As the script method with permissive.sh causes some serious issues with dialer and settings (FC) on my device (CM12 02/22) and this is only a not so clean workaround it would be very nice of you if you could consider a permissive variant of your kernel. Thanks in advance!
[Xperia Z3 Compact Original Android Development] someone755:
Have you tried version ZX1? It works for me but YMMV (which is also why I'm still labeling everything as beta).
[Xperia Z3 Compact Original Android Development] Zwulf:
Permissive! Gr8, thanks a lot! :)
[Xperia Z3 Compact Original Android Development] mattdm:
Thanks so much! I've been hoping for a permissive LP kernel for our device!
[Xperia Z3 Compact Original Android Development] was12:
[MENTION=4275152]someone755[/MENTION]

Oh, I agree that was a fool question :P

Ok now, I'm waiting your next works. I hope you to add new features and create a good kernel for our device.
[Xperia Z3 Compact Original Android Development] smorgar:
Maybe this is a stupid question but what kernel is this based on? The unified kernel? Or is it built from scratch?
[Xperia Z3 Compact Original Android Development] funiewski:
[MENTION=4275152]someone755[/MENTION] thx for your work. How about kexec? I know there is no multi rom for z3c yet but maybe it will come soon.
[Xperia Z3 Compact Original Android Development] someone755:
What do you mean, from scratch? o.o

It's based off the CM msm8974 repo's cm-12.0 branch. The branch unifies all Sony msm8974 devices' CM12 kernels, so I guess it's kinda unified.

I'll worry about MultiROM when it gets here. Of course, if it gets here.
[Xperia Z3 Compact Original Android Development] smorgar:
That answers my question perfecly. The 1:st post does not say wich kernel its based on so i just wanted to make sure :)

Edit: By "from scratch" i ment if you built it on your own based on nothing. It could be the case sinse you dont state wich/what kernel you based your kernel on.
[Xperia Z3 Compact Original Android Development] someone755:
But ... you have the sources right there... Says "forked from Cyanogenmod/android_kernel_sony_msm8974".

There really is only one source I could build something that boots into a CyanogenMod ROM, and it's from CyanogenMod sources.

I still don't understand what you mean by "from scratch" -- starting from either the base Linux kernel or the stock Sony ones is madness.
[Xperia Z3 Compact Original Android Development] smorgar:
Sorry to confuse you. Maybe i did not read the post as i should have... My bad.

My thaught was like you say: madness to build from linux kernel or stock sony but i had to ask to be sure what this was since i did not read the post well enough as it seems :)

Gonna try this kernel ASAP. Thank you and keep up the work!
[Xperia Z3 Compact Original Android Development] spdrfx:
Yes, i want to say that, thanks :) /the problem is that, i dont know what i want to say exactly, not even in my native language/

But after a reboot, there are the same freqs in booth list. :confused:

So its working now:)
[Xperia Z3 Compact Original Android Development] someone755:
Can Xposed modules even modify the kernel? As far to my knowledge xposed hooks into the system, not the kernel, although it is possible that the kernel offers up a device that communicates with the system, and the module then intercepts that connection.

GitHub offers a search function through repositories btw. Though most variable names usually aren't pretty enough to be found through that.

Looking at the Xposed module code it looks like it's looking at the "com.android.server.DockObserver" class to see whether the device is docked and then negates it if it is. This is a part of the system framework, and if we go and read that code we see that the device is served up at "/sys/class/switch/dock". If the magnetic thing is connected then /sys/class/switch/dock/state is 1, and vice-versa.

The gpio-keys kernel interface has some interesting instructions that you'd think would help but sadly our dock isn't a switch, so using gpio-keys won't work.

Qpnp-charger looks to have some control over the dock as well but I don't know whether that's just the charging part or not.

Honestly I'm at a loss for how we'd do this. We either have to find the part of the kernel code that controls the dock state or edit the framework dockobserver server to ignore the change (or disable the server altogether). I don't know enough C or Java to try, but I can try ripping the dock server code from the framework at build time and see if that does it but that's far from the optimal solution (with having to build our own framework every time a ROM update is released).
[Xperia Z3 Compact Original Android Development] okij:
Thanks a lot for your comprehensive answer and the research you did! :good::)

With this information I think we're almost there:

IMHO we only have to delete

static void dock_worker(struct work_struct *work)
{
struct qpnp_chg_chip *chip = container_of(work,
struct qpnp_chg_chip,
somc_params.dock_work);

if (chip->somc_params.enabling_regulator_boost)
return;

if (chip->dc_present)
create_dock_event(chip, CHG_DOCK_DESK);
else
create_dock_event(chip, CHG_DOCK_UNDOCK);
}

(at least the create_dock_event(chip, CHG_DOCK_DESK); and create_dock_event(chip, CHG_DOCK_UNDOCK); lines) from qpnp-charger.c in order to stop the magnetic charger from interfering with the dock state.

What do you think?

Could you test this?
[Xperia Z3 Compact Original Android Development] fluffi444:
[MENTION=4916555]okij[/MENTION]

[MENTION=4275152]someone755[/MENTION]

Actually I dont know how LOS handle this magnetic dock landscape mode but stock MM 23.5.A.1.291 control it this via

/system/framework/framework-res.apk

I posted the following long time ago here - maybe helpfull:

https://xdaforums.com/showpost.php?p=69803187&postcount=12
[Xperia Z3 Compact Original Android Development] okij:
[MENTION=4962787]fluffi444[/MENTION]: Thanks for your hint and the link to your post! However, I think that your method only disables the rotation, but not the desk dock mode completely. I'd like to disable it completely, since it badly interferes with the car dock mode.
[Xperia Z3 Compact Original Android Development] someone755:
Honestly if all we're trying to do is disable auto-rotation on magnetic charger this is the best solution.

Editing power management kernel code and risking hardware malfunction just to disable this seems to be a bit overboard.

That said if you insist I can give you a build with your proposed modification but I'll leave the testing and finding people to test up to you.
[Xperia Z3 Compact Original Android Development] okij:
Yes, please. :)

I would suggest to delete the lines

if (chip->dc_present)
create_dock_event(chip, CHG_DOCK_DESK);
else
create_dock_event(chip, CHG_DOCK_UNDOCK);

from qpnp-charger.c. I'm pretty sure that this won't do any harm, but will prevent the desk dock mode when using the magnetic charger.

Please PM me the build and I will test it. For this I will also need [MENTION=3816568]Myself5[/MENTION]'s new CarbonROM weekly (because of recent LOS changes which will be included then), so I will be able to test it on Tuesday.

Thanks in advance. :)
[Xperia Z3 Compact Original Android Development] okij:
[MENTION=4275152]someone755[/MENTION]: I've installed today's CarbonROM build, which means that I can now install a test build of your kernel with the above mentioned changes.

Please PM me the link, so that I can test it first before other users might try it. Thanks! :)

P.S.: The r_09 version of your kernel is running fine on the 07-11 build of CarbonROM, thanks for the good work! :good: The performance feels as good as with the default kernel. Battery seems to be better than before due to the changed min. frequency and voltages, I will keep an eye on this in the next days.
[Xperia Z3 Compact Original Android Development] killphillxr:
Hello, I tried r_09 version of this kernel with CarbonROM (last build CARBON-CR-5.1-MOO-WEEKLY-z3c-20170711-0820). After flashing zip in recovery (TWRP 3.1.0.0) I was not able to start phone. It just vibrated and nothing happened. I was able to enter recovery and flash CarbonROM again - it works without problem with default kernel.

Thank you
[Xperia Z3 Compact Original Android Development] someone755:
Cool story. I liked the character arc but you need to work on the story development -- the climax comes way too soon, and the ending leaves lots of questions unanswered.

Overall I give XDA Forum post number 73000507 a rating of 7/10. While short, with some flaws in its narrative, it is still a very satisfying read.
[Xperia Z3 Compact Original Android Development] okij:
[MENTION=4865569]killphillxr[/MENTION]: Anyway - and even if it's not of much help to you: I use the same rom+kernel combination on my Z3c and it works without a problem.

[MENTION=4275152]someone755[/MENTION]: IDK, could his problem be caused by some undervolting in the kernel, which probably is too much for his CPU batch? Just a thought.

BTW, I'm just writing you a PM with some feedback for the test build you made for me. It works like a charm! :victory:
[Xperia Z3 Compact Original Android Development] someone755:
I leave stock voltages alone; The only undervolting that happens is optional, and out of my control (if somebody really dislikes their CPU I don't have the power to prevent them from feeding it 4V).

So I'll have the next zip have two kernels to choose from, one in which your fix is present, and another where the charger is left alone. It's not like anyone uses the SELinux switch anyways (unlike Lollipop, where Xposed didn't work with enforcing selinux). At least until we figure out how (and if at all) we can get this into a nice switch using sysfs. Thanks for doing the testing, my work is just scattered everywhere right now.