yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Original Android Development] raschad:
I can not post a link, so I wrote in the message
[Xperia Z1 Original Android Development] munjeni:
Ok, found it, booth cm14 and aosp have working camera, broken only camcorder, in any way interesing! Thanks for info! https://www.youtube.com/watch?v=Qrlauj7Fk1A
[Xperia Z1 Original Android Development] brickhayabusa:
i think "programed obsolescence" from sony.

but they want one thing.

"they want us to buy their phones every year"

anyway if drakonizer or another devs manage to do something

with the 3.4 kernel maybe we can have an "stable" rom.
[Xperia Z1 Original Android Development] munjeni:
Its allready stable on 3.10 kernel, kamera is only which missing. Interesting thing ZR have it working, need to look into its rom zip for more info, need to find some info about which libs is used in that rom
[Xperia Z1 Original Android Development] brickhayabusa:
well you're the recognized developer

not me xD
[Xperia Z1 Original Android Development] munjeni:
Generaly I will back to stock kernel and stock blobs from, found some generic v4l2 camera hal source code... will try to make something at least to boot stock kernel on nougat. [MENTION=5075064]optimumpro[/MENTION], camera stock libs is drm protected? How you know that? How it is protected?
[Xperia Z1 Original Android Development] optimumpro:
Per CM team. See the link I sent to you a few days ago from their gerrit...
[Xperia Z1 Original Android Development] munjeni:
Ok, but I don't think like that, instead I think he no want to pay more atention to an legacy devices, he is bussy with newer devices. I will colect stock rom things, lib by lib, I will try with stock kernel and stock libs from 5.1.1
[Xperia Z1 Original Android Development] optimumpro:
That info comes from Kitkat times. So, at that point, Z1 wasn't legacy. But who knows? You can only say for sure if you try yourself. And by the way, stock kernel won't boot with custom roms...
[Xperia Z1 Original Android Development] munjeni:
Not boot? You are wrong, it boots! For example it boot on MIUI, on Ubuntu, ...worked on it allready! Even I was so close to get real Ubuntu on stock kernel copylefts by porting freedreno libs and some parts of kernel!
[Xperia Z1 Original Android Development] optimumpro:
MIUI is stock based and Ubuntu too, i.e., they don't require unlocked bootloader...
[Xperia Z1 Original Android Development] munjeni:
Ubuntu is aosp based!
[Xperia Z1 Original Android Development] ahmedzetm:
1111
[Xperia Z1 Original Android Development] brickhayabusa:
we're not talking about customize a kernel.

we're talking about how to make a stable kernel boot with the correct drivers.

and for that it needs a lot of corrections and additions to an a code.
[Xperia Z1 Original Android Development] cangreburguito:
how can i install this in my z1?, anyone help me?
[Xperia Z1 Original Android Development] ReznorNInchNails:
1. First check if your bootloader is unlockable (it should say bootloader unlock allowed: Yes) -> *#*#7378423#*#* or *#*#SERVICE#*#*. Then backup TA partition, there's a tool for Windows and Linux on xda, google it.

2. Unlock bootloader on Sony page, you will get the unlock key

3. Get a TWRP for Z1, search for it on Z1 original development section

4. Install adb+fastboot drivers

5. Enter fastboot mode by holding vol key up and plugging usb cable

6. Fire up cmd/terminal and enter unlock bootloader command you got from Sony e.g. fastboot oem unlock something

7. Wait for process to finish, it should say ok at the end

8. fastboot flash recovery twrp.img

9. Power up phone by holding power+volume down keys, you will get into recovery, or you can power up the phone and press vol down as many times until led flashes purple.

10. Flash ROM zip with adb sideload something.zip (from PC) or Install from SD card, you will need to put the zip on SD Card.

If it contains four .img files in zip, then you flash it in fastboot.

fastboot flash boot boot.img

fastboot flash userdata userdata.img

fastboot flash system system.img

You should skip recovery, as you already have your TWRP installed.

As you see this is a quick guide. There are a lot of guides around how to do it, do some research. Be smart and backup your TA partition first. Happy flashing.
[Xperia Z1 Original Android Development] munjeni:
One thing why stock kernel can't boot with nougat, got infos by uart ;) , hope it will boot very soon

[ 13.252206] init: init first stage started!
[ 13.255780] SELinux: policydb version 30 does not match my version range 15-26
[ 13.262760] init: SELinux: Could not load policy: Invalid argument
[ 13.269041] init: failed to load policy: Invalid argument
[ 13.274387] init: Security failure; rebooting into recovery mode...
[ 13.280820] SysRq : Emergency Remount R/O
[ 13.284621] Emergency Remount complete
[ 13.288433] Disabling non-boot CPUs ...
[ 13.347216] mdss_fb_release_all: try to close unopened fb 2! from init
[ 13.352735] mdss_fb_release_all: try to close unopened fb 1! from init
[ 13.359225] mdss_fb_release_all: try to close unopened fb 0! from init
[ 13.366222] Restarting system with command 'recovery'.
[ 13.370872] Going down for restart now
[ 13.375350] Calling SCM to disable SPMI PMICS1 BOOT

First of all I will update selinux on kernel to version 30
[Xperia Z1 Original Android Development] SuperLamic:
I would disable the selinux completely... https://github.com/SuperLamic/device-sony-common/commit/7120f92694a88e5730fcce0d7cbb8f0fe94ead8d (this comes from my builds of cm13, selinux is on permissive at aosp)
[Xperia Z1 Original Android Development] munjeni:
Disabled but the same thing happening! Init puts selinux parameters

[ 13.281692] init: SELinux: Could not load policy: Invalid argument
[ 13.287983] init: failed to load policy: Invalid argument
[ 13.293330] init: Security failure; rebooting into recovery mode...

which cause device reboot, probably I need to modify init or to port some things from selinux from 3.10
[Xperia Z1 Original Android Development] ahmedzetm:
Thanks guys for support Z1
[Xperia Z1 Original Android Development] SuperLamic:
Aww http://xdaforums.com/showpost.php?p=64709895&postcount=1990

edit: by the way my phone is in service center as I plugged my magnetic charger wrong side and my phone started turning off when reaching 50%... I hope they don't notice :D (I flashed back TA and flashed stock for Germany - my phone's from Germany )
[Xperia Z1 Original Android Development] munjeni:
Found that allready, need some implementations which still missing. I will disable selinux on system/core/init

diff --git a/init/init.cpp b/init/init.cpp
index 84da2b9..5394345 100644
--- a/init/init.cpp
+++ b/init/init.cpp
@@ -560,7 +560,7 @@ static void selinux_initialize(bool in_kernel_domain) {
INFO("Loading SELinux policy...\n");
if (selinux_android_load_policy() < 0) {
ERROR("failed to load policy: %s\n", strerror(errno));
- security_failure();
+ //security_failure();
}

bool kernel_enforcing = (security_getenforce() == 1);
@@ -569,12 +569,12 @@ static void selinux_initialize(bool in_kernel_domain) {
if (security_setenforce(is_enforcing)) {
ERROR("security_setenforce(%s) failed: %s\n",
is_enforcing ? "true" : "false", strerror(errno));
- security_failure();
+ //security_failure();
}
}

if (write_file("/sys/fs/selinux/checkreqprot", "0") == -1) {
- security_failure();
+ //security_failure();
}

NOTICE("(Initializing SELinux %s took %.2fs.)\n",
@@ -640,6 +640,7 @@ int main(int argc, char** argv) {

// Set up SELinux, including loading the SELinux policy if we're in the kernel domain.
selinux_initialize(is_first_stage);
+ NOTICE("Selinux disabled!\n");

// If we're in the kernel domain, re-exec init to transition to the init domain now
// that the SELinux policy has been loaded.

later I will pay atention porting the rest
[Xperia Z1 Original Android Development] SuperLamic:
and have you seen this? https://github.com/nailyk-fr/android_kernel_sony_msm8974/commits/cm-13.0_work I guess we may use the same patches or even kernel? (if it's really sony cm 8974 kernel)
[Xperia Z1 Original Android Development] munjeni:
I going to continue on sony stock kernel, lets continue tomorrow
[Xperia Z1 Original Android Development] drakonizer:
I can confirm that is a Sony cm kernel. The devs at the Z3 forums managed to get a pretty stable (minus cam) version of cm13 running using the old cm kernel.
[Xperia Z1 Original Android Development] munjeni:
I am working on STOCK kernel, not on CM kernel, which mean I going to make stock kernel boot on AOSP Nougat
[Xperia Z1 Original Android Development] drakonizer:
Isn't the cm 3.4 kernel based off the Sony stock kernel?
[Xperia Z1 Original Android Development] munjeni:
I am not sure to say that but if you look into commits you can see that that kernel is a lot diferent than sony stock. I'm using this one https://github.com/sonyxperiadev/kernel-copyleft/tree/14.6.A.0.xxx
[Xperia Z1 Original Android Development] SuperLamic:
I don't think so. There are many changes to make it work for multiple devices. But it doesn't change the fact that it's compatible with stock blobs.

(and there are some broken things that work on stock - 4-pole audio jack detection, mpdecision...)
[Xperia Z1 Original Android Development] optimumpro:
Booting stock lp or kk kernels on AOSP won't make them compatible with Nougat camera without heavy changes in Android sources. Yes, if you boot stock kernel, providing your bootloader is relocked with the original TA restored, you can go around the drm issue. But because there is no stock camera blobs for Nougat and in case of Z1 even for MM, you would still need to re-write thousands of lines of code to have a working camera. You think you can use camera blobs from a newer Sony device with a camera wrapper? Unlikely, but even if you can, what about loosing the ability to modify kernel or implement security patches (about 60% of them are in kernel)?

I think the only viable path is to downgrade framework/hardware/system files...
[Xperia Z1 Original Android Development] SuperLamic:
I think he is working on stock-based kernel, not pre-compiled stock kernel. I guess if you recompile stock kernel, you cannot use it on locked bootloader anyway. (and he is modifying the kernel)

Are blobs from stock lp after disabling drm usable on N? (with wrapper ofc, I mean if there's not an issue with renamed service or whatever with one more letter in name - so you can't hex edit it)
[Xperia Z1 Original Android Development] munjeni:
Thats no sense since camera working even on unlocked bootloader. I don't know where you gets that infos. I think we just needs generic v4l2 camera hal to start working on stock camera, or make another camera wrapper which will preload stock camera hal. For all that things we need perfect match aka stock kernel

Who cares about that, 80 percent of peoples runing stock rom and stock kernel. 3.10 kernel from jerpelea also not match upstream security, who care at all
[Xperia Z1 Original Android Development] munjeni:
Holish.. damn, I wasted my time today by porting stupid selinux from that kernel, its not aosp nougat compatible!!! :( I must port nougat compatible selinux. Did you even tried that kernel on AOSP Nougat or you just only thinked that?

Here is patch I done but its not nougat compatible, it missing extended permissions... :mad:

You will end with:;

[ 13.895618] init: init first stage started!
[ 13.900939] SELinux: avtab: invalid type or class
[ 13.906444] init: SELinux: Could not load policy: Invalid argument
[ 13.911824] init: failed to load policy: Invalid argument
[ 13.917169] init: Security failure; rebooting into recovery mode...
[Xperia Z1 Original Android Development] tomascus:
https://github.com/tunturn/z3concept/commits/n-wifi?after=7i7AeZRtH3w2f6U6y+p335SX+NkrMTA0

and https://github.com/tunturn/z3concept/commits/n-wifi?after=7i7AeZRtH3w2f6U6y+p335SX+NkrNjk=

just the selinux ones and net ones, pink ones by NicolasDichtel are optional i think

EDIT: here's a cleaner one https://github.com/tunturn/z3concept/commits/nougatselinxu

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

Anyway, [MENTION=6979267]nailyk[/MENTION] and I have been working on cm13.0 with 3.4 kernel on the Shinano platform and the barrier we face at the moment is that the old 4.3 blobs call functions which have been deprecated post-Lollipop. I managed to readd some of these functions but these other required ones need major reverts to libui and other libraries, which would take some time.
[Xperia Z1 Original Android Development] SuperLamic:
this is cm13 kernel, I never said that it's compatible with nougat, it's compatible with marshmallow. But old cm kernel doesn't even work with mm, so I thought that might help you.

by the way I said that my phone's in service center, so I don't do anything now till I get it back
[Xperia Z1 Original Android Development] optimumpro:
"camera working even on unlocked bootloader". That's my point: why kill yourself having AOSP boot on outdated and non-modifiable stock kernel, when you can do the same on custom kernel, which already boots on Nougat? Stock camera hal has to be able to work with Nougat. So, you either need Nougat stock camera hal, which we will never have on Z1-Z3 or you need to downgrade Nougat camera files to MM in case of Z2-Z3 and to LP in case of Z1.
[Xperia Z1 Original Android Development] munjeni:
No choice since we will not get good working camera on 3.10 kernel, thats the fact. Kernel camera hal in 3.10 is totaly diferent.. we need to back to 3.4 kernel if we need stock camera, we to make new wrapper or to make new android v4l2 camera hal compatible with camera blobs.. stock blobs I think is not very broken, camera hal only after lp++
[Xperia Z1 Original Android Development] optimumpro:
I am not talking about 3.10 kernel, especially that there is no stock 3.10 kernel for Z1 and Z2, and I doubt there is stock 3.10 for for Z3 either. But anyway, forget 3.10. My point is: you don't need stock kernel at all. Instead of killing yourself trying to boot stock 3.4 with non-stock AOSP, you should use a custom 3.4, which already boots on Nougat...
[Xperia Z1 Original Android Development] brickhayabusa:
Heads Up

Nothing are imposible, [MENTION=4120742]munjeni[/MENTION] if you need a tester or something i can test.
[Xperia Z1 Original Android Development] optimumpro:
Yeah. You just need to re-write a half of Android source. And you will need to do that every time there is a new Android version: all because Sony doesn't want you to have custom roms on their devices...
[Xperia Z1 Original Android Development] munjeni:
And whats a point on that? Thats the same like runing 3.10 since the thing is the same (again nothing like stock)! My point is: use stock kernel to be sure camera and other things bugs is not kernel related (for safety work on camera...etc). Situation with NO stock kernel is diferent: you don't know if bug coming from kernel or from blobs (double hard making something).
[Xperia Z1 Original Android Development] optimumpro:
That's just wrong. Custom 3.4 has absolutely no bugs related to camera. If there were any bugs, they were related to camera wrapper. Here is a camera wrapper that I heavily modified (see attachment). It is the entire camera folder from msm8974-common. My wife has a Z1c with locked bootloader. There is no difference in camera quality between her phone and my Z1 with unlocked bootloader on Jaguar LP 5.1.1 and using Open Camera app (not Sony crappy open camera)...

If you are on any custom LP 5.1.1, you can just replace CM /device/sony/msm8974/camera with my folder, compile the rom and you will have stock camera quality. And by the way, all Sony "extra" features do is make the photo look a little better on the phone screen. If you transfer the file to a PC, there is no difference in quality between stock and modified custom cameras.
[Xperia Z1 Original Android Development] brickhayabusa:
[MENTION=5075064]optimumpro[/MENTION] don't need to do that

Marshmallow have a lot of utilities that are not present on lollipop, like the sd apps, multi-window, systemless root and if you search "mods" a lot of those won't support lollipop anymore.

The point is if Sonny can't do it

We can't too?

If you ask someone here, the answer are easy, they don't need android 7.0+ they will be happy if only MM get the basic things working.

Don't get negative all the time.

Pd: I'm studying computing but it will take a while.
[Xperia Z1 Original Android Development] SuperLamic:
and is cm custom kernel compatible with lp blobs? (if you disable drm and fix wrapper)
[Xperia Z1 Original Android Development] munjeni:
Ok but who guaranting that? There is no need to be any bug, just need to be an diferencie to make thing non working corectly (and offcorse you can't notice any log if debug is 0)! If you chose stock kernel && matched blobs, than you know for sure that there is no diferencie in compatibility between kernel <-> blobs, it will for sure match !
[XDA Assist] puru9860:
can any one tell me how can i flash stock rom of samsung galaxy core 2 (SM-G355) throgh custom recovery. odin method could not me
[XDA Assist] :
Hello,

Please try posting your query here Galaxy Core 2 Forums, the experts there maybe able to assist you.

-Vatsal
[XDA Assist] markk146:
Got a new cyanogen mod on my idol 3 (4.7). Flashed it , flashed GApps and everthing was fine. Booted up my phone and a message always appeared saying google play service has stoped and it brings me back to the begginig. So i get into recovery ( TWRP ) factory resseted the phone including internal storage and system and now i cant flash anything , i cant restore anything , cant load up ADB Sideload nor do i have an OS on my phone. Any way i can recover from this ??? :(
[Galaxy S II Q&A, Help & Troubleshooting] erwinke22:
Yesterday i flashed TWRP recovery , because i wanted to try XOSP 6.3 marshmallow on my phone,so i flashed the recovery with success then after i rebooted to recovery to continue flashing the rom, the phone didn't booted naymore only bootscreen, i tried rebooting the system , the same , only Samsung logo and that's it.

The only thing works is download mode, but i can't use that ,because my computer didn't recognize the usb device despite i installed various Samsung usb drviers fro mobile devices.

-i was running MIUI v6 5.7.20 by Blackra1n

-rooted

So far i tried every possible thing.

I guess the only way is to take it to the service?
[Galaxy A3, A5, A7, A8, A9 Android Development] Jerome-X:
Clean Rom. Fully deoxed, deknoxed, rooted, debloated, tweaked. Based on latest StockRom 6.0.1
[Galaxy A3, A5, A7, A8, A9 Android Development] lixijing:
期待中，感谢大神的付出与努力！
[Galaxy A3, A5, A7, A8, A9 Android Development] rosenwinkel:
When will you release this rom?
[Galaxy A3, A5, A7, A8, A9 Android Development] Jerome-X:
rom is out, see in Original Android Development
[Galaxy A3, A5, A7, A8, A9 Android Development] :
Thread closed
[One (M7) Q&A, Help & Troubleshooting] a1gara:
Hello!

So, I am simply an indian with all the developer-things. Checked lots of the topics here, tried everything I found and nothing. Error after error. Let's jump to the problem:

- HTC ONE M7

- hboot - 1. 61

- windows 8.1 Pro x64mBit

- USB 3.0

Installed all kind of drivers I found, but nothing works when it is in fastboot mode. The phone shows that it is connected to the PC, but in the settings the PC recognise it as "Android 1.0" and nothing more. Not a folder, or some kind of connection.

Tried different computer, different cable, different USB-port and nothing. I don't know what more can I do, just to root my phone.

Thank you for your time!
[One (M7) Q&A, Help & Troubleshooting] alray:
Would help to know what error you are getting exactly

Better to use USB 2.0 ports only

Install the right drivers from HTC. Version 4.17 here: http://htcusbdriver.com/download/htc-usb-driver-v4-17-0-001

When your phone is booted in fastboot mode, you'll not see any folder from your phone and that is normal. You'll be able to use fastboot commands only.
[One (M7) Q&A, Help & Troubleshooting] a1gara:
Okay. So...I had a success, using windows 7 with USB 2.0.

Unblocked the bootloader and started to root. But when I finally got to the "Team Win Recovery Project v 2.5.0.0", there was the next surprise. Unable to mount internal storage & unable to mount data. Now what? I couldn't find the superuser zip file and couldn't finish the root. There are underwater-rocks everywhere... :(:(:(
[One (M7) Q&A, Help & Troubleshooting] alray:
Twrp 2.5 is outdated, use the latest version, same for supersu.
[Android Apps and Games] parkerwilliam713:
CallsApp On-Call Screen Widgets

Feeling bored of the usual call screen, now you can lay your hands on several exciting widgets from your call screen. Just tap on the CallsApp icon from your call screen and unveil new ways of rejecting a call with social media messages along with call recording and call reminder facilities also you can initiate a call back right away from your call screen.

You can find popular social messaging apps and various call utility features on your call screen as like,

Call Logs Backup

Now you need not worry about your call logs being deleted from your phone. CallsApp allows you to keep track of all your call logs in a more secure way, A complete backup of your call logs along with those deleted from your phone is stored here.

You can keep track of your past 30 days call log records using the free version while there is no such restriction for pro user and you can record as much as space your phone holds.

Auto Call Recorder & Playback

Now you can record all your calls on the go in a high quality audio format with much ease and also play back those call records whenever you wish to hear it back again, either it’s from your loved ones or from a business person regarding important notes & details.

You can now record and playback past 30 days call recordings in free version of the app while in the pro version you can record an unlimited number of recordings and hear them back when you need to listen.

Play Store Link: https://play.google.com/store/apps/details?id=com.insideglobe.callsapp

Upcoming Updates

Call Statistics The upcoming update will unfold call stats, which clearly show you the overall call statistics, person you called most and duration of your calls.

(Guys if you want to tel me any tips just PM me

[IMG="Call Screen by Callsapp"]http://i.imgur.com/br7fREf.jpg[/IMG]

[IMG="Social media widgets"]http://i.imgur.com/BtgM8cR.jpg[/IMG]

[IMG="Recordings"]http://i.imgur.com/Ayy1Fk0.png[/IMG]

[IMG="Call Reminders"]http://i.imgur.com/Ayy1Fk0.png[/IMG]

[IMG="Call Reminders notifications"]http://i.imgur.com/9RtWtJn.png[/IMG]

[IMG="Play Back"]http://i.imgur.com/3x1JM5Q.png[/IMG]
[Off-topic] Artuist:
Hey XDA forums,

I just got into web designing and I would like to contribute to the XDA community.

I am making a domain-less, custom, material designed webpage for app developers just to see what I can do in real life situations and maybe you guys can rate my work!

Reply on this thread if you are interested and shoot me a pm with more details if you would like me to make a you one!

Thanks in advance!

(Will check my dms and reply as fast as possible)
[Moto G 2015 Q&A, Help & Troubleshooting] hessien zaghloul:
why is that? where is the rest of it
[Moto G 2015 Q&A, Help & Troubleshooting] althafvly:
about 4gb is for system use. so u wont get that space. thats why its full. and may be the thumbnails of photos will too there.
[Moto G 2015 Q&A, Help & Troubleshooting] hessien zaghloul:
4 gb of the 16 not the 11.92
[Moto G 2015 Q&A, Help & Troubleshooting] althafvly:
yes. u used 6gb of apps. and about 3gb of other files. so the other space maybe in lost.dir or any other data . like hidden files
[Moto G 2015 Q&A, Help & Troubleshooting] hessien zaghloul:
thanks, there was a recycle bin folder that was taking 3 gb and i deleted it
[Android Q&A, Help & Troubleshooting] The Untammed:
hey guys I was messing up With my phone in engineering mode and now my dialer has stopped working can I get help from you please
[Android Q&A, Help & Troubleshooting] Artuist:
Did you uninstall the package or..?