yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device Development Themes and Apps] Cromwellfenix:
HI,

I have for you a new version of a theme created by me.

Is based in walkman old style with two versions with background settings differents choose your favorite (but yous can install both

Including iconpack

Now version gold:

Now version orange pure

I hope you like

Only rom stock from kitkat

Please hit thanks and share

Walkman orange :

https://drive.google.com/file/d/0BzPuZ8q4_N4kZmVZano2bXp0WjQ/view?usp=drivesdk

Walkman gold :

https://drive.google.com/file/d/0BzPuZ8q4_N4kTk1JTHdzUE5UM28/view?usp=drivesdk
[Sony Cross-Device Development Themes and Apps] FalleN_lMaster:
Good work bro
[Sony Cross-Device Development Themes and Apps] Cromwellfenix:
Thanks

Your comments are valious for me
[Sony Cross-Device Development Themes and Apps] Siełhu Aung:
Very Nice Themes! Thanks :)
[Sony Cross-Device Development Themes and Apps] Cromwellfenix:
Thanks for comments
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] thetastycat:
Hey all - I've become aware that my phone will answer calls unbeknownst to me while in my pocket. For the life of me I can't figure out a way to add anything else to the act of answering - would love to maybe have to draw my pattern. Any ideas?

Many thanks!
[Note 7 Accessories] smeddy:
It's not the end of the world - but - as I am using cheap-ish QI chargers, I'm wondering if the official (or other third party vendor) has the POWER to do this?

Thank you, I love wireless charging, but it defeats the purpose if I'm taking my phone out of the case each time.
[Note 7 Accessories] rcobourn:
I'd be surprised if it didn't work with the Samsung or Seneo fast charge cradles.
[Note 7 Accessories] pyraxiate:
This is the charger and case I'm using. No problem going through all the layers and it works in portrait and landscape.

Fast Wireless Charger, YOUSHARES [Fast Charge] 2-Coil Qi Wireless Charging Stand for Samsung Galaxy S7 S7 Edge, S6 S6 Edge S6 Edge + Active, Note 5 Note 7, Nexus 6 5, Moto Droid Turbo 2 1, Maxx, More https://www.amazon.com/dp/B01GGYTNGA/ref=cm_sw_r_cp_apa_t5G0xbJ2T0SY7
[Note 7 Accessories] edwardob:
I'm using Samsung fast charger with sview case.... it does have to be placed perfectly even with Samsung charger or it won't work
[Note 7 Accessories] Boy Bisaya:
I am using the Galaxy S6 Wireless Charger (EP-PG920i) for my N7 with S-View Cover. It works.
[Note 7 Accessories] i killed tupac:
some crappy chinese charger doesnt work right?!?! I don't believe it.
[Note 7 Accessories] Boy Bisaya:
I used 3rd party Qi module in my Note 3 and it also works. You just need to make sure that the wireless charger and phone are resonant or "matched".
[Note 7 Accessories] Shofar1:
How does the S-View cover work with SP?
[Note 7 Accessories] edwardob:
what is SP?
[Note 7 Accessories] Shofar1:
Screen Protector - Glass or plastic
[Note 7 Accessories] Boy Bisaya:
I was able to get from a local shop a screen protector they claimed to be "tempered glass" for around $27. The SC sits well with a good gap from the S-View case edge. No SC pushing and pop sound as others have experienced. S-View cover doesn't sit well though with a small negligible gap due to the added thickness of SC on the screen. This is still a common curved glass SC where adhesives are only along the edges. Tap sensitivity is affected randomly across the screen area. Some are as responsive as the screen itself but some feel like you are tapping a resistive touch screen. :p
[Note 7 Accessories] Itchiee:
I have both the official Samsung wireless and the Seneo charger (which I prefer more) and both work with my Caseology case on the Note 7. So it won't work "unless you've got POWER!"
[Note 7 Accessories] Femmetechstic:
I have an S-view but no wireless charger, will see if I know anyone who does to test this.

Really, Samsung should just offer these for free to make up for the batteries exploding :P

http://www.mobilefun.com/60297-official-samsung-galaxy-note-7-starter-kit.htm
[Sony Xperia L] xperiajack28:
Yesterday I flashed CM-12.1-20160822-NIGHTLY without any issues...followed by Gaaps.

I am using ThunderZAp-4.16 kernel.

I found no significant bug other than that I

can't switch on the WIFI now

. I am sure there is no problem with my WIFI because I have been using it for the past one year.

I did a clean re-installation but the problem with the WIFI still persists.

Can anyone please help?
[Sony Xperia L] newguyknowsnothing:
What stock rom version were you on before? And don't use tz, it is outdated now.
[Sony Xperia L] xperiajack28:
so, first, i flashed the basic taoshan kernel that comes along with cm12.1

i read in one of the xda threads that the wifi problem can be fixed by flashing stock rom and then flashing cm12.1. i tried to flash C2104_15.3.A.1.17_Generic, but there are some issues with my Flash Tool because, in the flash window I can only see the device name. All the other options are greyed out. Even the contents section is empty.

Now i recoverd a recovery using TWRP. so currently i have a rooted and bootloader unlocked 15.0.A.2.17. I have unrooted and relocked my bootloader so that I can update upto 15.3.A.17 using the official updates.

After getting 15.3.A.17 this way, I plan to root and unlock bootloader again...followed by flashing cm12.1 nightly using twrp.

Will doing all of this make the wifi work on CM 12.1?
[Sony Xperia L] newguyknowsnothing:
Wow I'm not sure. Why don't you try older version of flashtool (0.9.11). This ver works well for me.
[Sony Xperia L] xperiajack28:
Flashed stock rom using Xperia PC Companion. But now i am confused as to which Cyanogenmod ROM i should flash.

Is there a stable version somewhere? All that i could find were nightlies.
[Sony Xperia L] noobp:
Yes their is not stable version on cyanogenmod ,you can find more stable releases at Free experia community but still they aren`t that stable and they are pretty old..... http://fxpblog.co/
[Xperia Z2 Q&A, Help & Troubleshooting] lightningglasses:
I am running stock Marshmallow and need to uninstall xposed to sign into snapchat. I need to confirm which .zip file is right for Z2, arm or arm64?

http://dl-xda.xposed.info/framework/uninstaller/
[Xperia Z2 Q&A, Help & Troubleshooting] Chronic2k13:
Arm
[Xperia Z2 Q&A, Help & Troubleshooting] lightningglasses:
I take it arm now has a 64bit instruction set?
[Xperia Z2 Q&A, Help & Troubleshooting] a.hamameh96:
Only arm

Gesendet von meinem D6503 mit Tapatalk
[General Questions and Answers] Matt07211:
After Numerous trial and error, I finally managed to output ramdisk.cpio.gz.

The start of a Gzip file in hex is, 1F 8B 08, therefor when using the search function in you had editor application you can narrow down your results to 1 or 2 files (2 Files for me as my kernel and ramdisk are both gzipped). You then follow it all the way down till you find a big bunch of zeros(seems like they are passing between files). When you reach the bunch of zeros include the first "00" at the end of the other hexidecial. E.G. End of one of my gzip files is "CE 24 00 00 00....00 (ZERO PADDING BETWEEN FILES), Threaded the end of my file is "CE 24 00".

Knowing this I was able to successfully extract and verify both my kernel and ramdisk files are correct.
[General Questions and Answers] Matt07211:
Yes [MENTION=7770482]akuhak[/MENTION] I had realised that about a week ago (header sizes), also another thing is most of these tools deal with a zImage, where's I boot.img has a hOmage (which is a 64 byte uImage header followed by the kernel. I have succesfully unpacked this boot.img (the kernel, ramdisk and dt.img).

Now if this script works it will be good for other users, but for me my need has already been done.

I am just having trouble trying to get this booting up on my phone when I repack it (I haven't been paying to much attention to this project becuse of exam revision)

Edit: I have tested it and verified thatvit works by comparing the files produced by hand and the files produced by this script via the sha1sum command. I have uploaded it onto my xCover3 post linking back here and giving the credit to you for posting it here. Thanks for your help ;)
[General Questions and Answers] akuhak:
It easier to found already existing tool. Our device (I am owning Xcover 3 too) has pxa1088 board. It is known that similar boards has similar structure. So i found these thread github(dot)com/kumajaya/degas-mkbootimg (he has also topic here in xda with his researchs)

It has the same board so these tools works fine for us :D The only difference I noticed - header unknown value is 0x03000000 for our device and 0x02000000 for Galaxy Tab 4. Maybe something wrong with dtb image - I didn't check these yet.

BTW our phone has same characteristics as Samsung SM-G531F Galaxy Grand Prime (same board, same cpu, same gpu, only screen a bit different) and grandprimevelte has 5.1.1 android onboard and working TWRP recovery (I was trying to flash it but was unsuccessful).

As for same board - For Example Xcover 3 Value Edition has completely different board (exynos3475 with mali-t760mp8 gpu). The same characteristics as for Samsung SM-J200 Galaxy J2. So we can use root methods from j2lte. This means - flash TWRP then install SuperSu zip archive - thats all.

But we cannot use TWRP from VE cause of very different hardwares.

Now Im working on improving degas utilities...
[General Questions and Answers] Matt07211:
TWRP for xcover3 value editio came out about 7 says ago, and apparently one user has tried it and is working on their value edition version. (When I had a quick look at the source code yesterdau I happenend to notice it was a exynos board). I had previously tried the dagas scripts and they didn't work for our image at the time, yet your providerd version does. Great idea for searching up the board name (Marvell) as that is one of the only things I hadn't thought to Google.

Feel free to compile TWRP under android 5.1.1 branch. I can/will chime in with relevant info, as well as you can use info from TWRPs source code on the other twrp versions of our device. The only reason I haven't tried it as of yet is becuse i using my my mobile data 99% of the time and just don't have the data to so are downloading source code.

As for the dt.img, I veriefed the scripts output to my on manually extraction and it's the same for both files. (Sha1). But there is a little bit of trailing data (anything past SEANDROIDENFORCING) which is ignored, I am not sure id it's importance as of yet(other then SuperSu omits it from the boot.img when using SuperSu.zip.

Will pop back into here later today.
[General Questions and Answers] akuhak:
Ok I completed my tools collection for pxa1088

Source Code: github(dot)com/AKuHAK/pxa1088-mkbootimg

All necessary utilities can be achieved via my modified android_img_repack_tools repo: github(dot)com/AKuHAK/android_img_repack_tool

By just typing ./configure and make

If you are scared by traffic I released tools in one archive: github(dot)com/AKuHAK/android_img_repack_tools/releases/tag/1st.

How to use? I created README in github: github(dot)com/AKuHAK/pxa1088-mkbootimg/blob/master/README

Tools can extract and than pack back boot.img and recovery.img from XCover3. If you didn't extract uImage and dtb.img you can repack boot.img (recovery.img) without hash sum changes. If you extract zImage from uImage and than pack again in uImage your resulting uImage will be different cause uIimage header contain timestamp which will be taken from your PC settings. But resulting uImage still HAVE to be valid.
[General Questions and Answers] Matt07211:
Cool, will have a look tomorrow, it's hitting 1am for me now. Just one quick correction in the above post of yours. You mention zImage is extracted from the uImage. That is incorrect, is is in fact just a gzipped kernel image (Image.gz) not a zImage.

Yes I know both types of formats are compressed, but our device runs a armv8 cpu which is 64 bits (albeit our kernel is using a 32 but instruction set not a 64 bit instruction set and this means or OS is also 32 bits then). Apon reading the documentation found in the source code, you will realise that it can only handle a) the uncompressed kernel image (Image) or b) a compressed version of the image in gzip format (Image.gz). This is further proven when looking at the boot.img with a hex editor as you can clearly see 2 Files that start with the gzip header format (1F 8B 08) which are the gzipped kernel (also if you go back by 64 bytes then you will be at the start of the uImage header which holds or the appropriate info about the kernel.uImage file) and our ramdisk.

So hopefully you may have just made a mistake in the above post, but if not then you are outputting the incorrect file, which may confuse some users of they don't know much but just wanted to compile the kernel from source.

Sorry about the above rant, will now have a quick look at your github. Thanks for your work you have put into this phone.

Edit: when you mention the android img repack tools, did you use this, http://xdaforums.com/showthread.php?t=2600364 , and if so what modification have you done since I already have the downloaded (used the last of my mobile data last month to get it)

EDIT2: Gonna have a mess around with them tomorrow. One question, sorry for sounding like a noon, but how does the compression differs between normal gzip and minigzip, how will these differences affect a repacked ramdisk and what got you onto that piece of info.

And I had a quick look at your github, seen all your ps2 back related source code.you using FMCB, a hardmod (a chip) or a internal hardrive via an Ethernet adapter. I see sp193, doctorxyz, have commuted to your repo, so sounds like your a ps2 dev, which is cool as **** ;)
[General Questions and Answers] akuhak:
1) About zImage. Maybe I need to be more clear: Xcover 3 kernel has uImage onboard with gzip compression. You can extract kernel from that gzipped uImage - I just thought that zImage is name for extracted kernel :D Sorry if I made mistake in this case.

uImage can be created with use of u-boot tool (denx(dot)de/wiki/U-Boot/WebHome)

For example

mkimage -I boot.uImage

will provide such an information for our device

Image Name: pxa1928dkb linux
Created: Wed May 18 15:13:06 2016
Image Type: AArch64 Linux Kernel Image (gzip compressed)
Data Size: 6616640 Bytes = 6461.56 kB = 6.31 MB
Load Address: 01000000
Entry Point: 01000000

This information is extracted from uImage kernel (64 bytes). After header we will see our gzipped kernel - you are right. I just simply extracted it with 7zip from boot.img-uImage.

The difference is that your way didn't use uImage header at all - so you will be unable to pack it back without mistakes - or your gzipped kernel have to be completely the same in size which is almost impossible to achieve. With use of mkimage you can alter kernels (of course only if samsung doesnt check something else) and get correct uImage in output.

2) About difference between minigzip and gzip. In fact I don't know why its happened but I didn't found a reason why ramdisk have to be packed exactly with minigzip. I tried almost all flag combinations with gzip but I get the same result that was in output file only with minigzip :D

As about kernel it is packed with maximum compression without name with normal gzip.

So assuming minigzip for ramdisk, gzip -n -9 for kernel. But Im completely sure that we can use any combination of gzipers and image still will be valid (but of course will be different in hash). We need to use exactly this combination only if we need to get the same file.

3) Yes Im using exactly this kitchen - I just removed all branches except 5.1.1 added minigzip, my tools and u-boot mkimage tool generation.

4) Yes Im one of still alive ps2 developers :D I just realized that my phone isn't rooted and started to dig what I can do with it.
[General Questions and Answers] Matt07211:
1) yes a zImage is one type of you can get when compiling for ARM Devices, you Device is ARM64 so thierare differences. As for extracting the kernel I have always include the 64 byte header (since the middle of last week when I realised that it was there after running binwalk against the file). So yea your assumption was correct up untill a week ago.

2) Interesting. I will be sure to make changes accordingly.

3) cool I have 2 out of four so will download accordingly

4) cool, that the development scene is still going since the ps2 reached it 16 birthday this year.

5) as for root on this device chainfire has needed to go Systemless after/on 6.0 device or 5.1.1. Samsung devices, so to achive root on those devices it requires the modification of boot.img. what his SuperSu.zip does is patch the sepolicy file to allow 3 rules to run in permissive, modify other bits of the ramdisk accordingly to allow for it to run services and mount su.img at boot and it creates and place the necessary files inside su.img. I have completed all that by hand after reading his update-script numerous times. My only roadblock has been try to get the boot.img to boot.I was currently in the process, of try (I have tried alot of different ways including mkbootimg etc.) Manuallying replacing the ramdisk contents with the modified version, and then modify the bootmimg header to continue any modifed value (ramdisk size and dt offset) but am only partially done as I haven't had the chance the last few days to do it.
[General Questions and Answers] Matt07211:
Awesome tool, unpack, repacked without a single modification and then ran "sha1sum" to both boot.img's and they are exactly the same. You are amazing :). I have referenced your tools in this thread (http://xdaforums.com/android/development/4-4-4-5-1-1-6-0-1-samsung-xcover3-t3465132 ) straight to your github. Now to try my modified ramdisk and see If my phone can boot it. Will post results soon.

======

Yes I can boot custom boot.img, without the SEANDORIDENFORCEING showing up. I can see my ramdisk changes, work, I can type adb root and I don't get the product in build message, but trying to do anything that requires root e.g. trying to push su.img to /data or /cache, gets me the error permission denied, but hey I am half way there to getting root. :)
[Samsung Galaxy S7 Questions and Answers] neednottoknown:
Anyone can install huawei p9 camera app in s7?
[Nexus 6  General] xterra91:
http://www.androidheadlines.com/201...-ota-update-now-rolling-out-to-nexus-66p.html
[Nexus 6  General] Poojan Patel:
FAKE. they think marshmallow's september security update as android 7.0.

Forget android 7.0 till google release new pixels.
[Nexus 6  General] GuestK00193:
im pissed with how google is handling this matter like everyone else here but we just have to be patient. not like we could do anything about it :D
[Nexus 6  General] jpeckinp:
Hows does this equal fake?

"many consumers were wondering when will the OTA rollout being for the Nexus 6 and Nexus 6P, and have been sending tweets over to Google’s official Nexus Twitter handle for a while now. Well, the company responded quite recently, by stating that Android 7.0 Nougat OTA update is finally rolling out to both the Nexus 6 and Nexus 6P handsets."

I don't follow the official Nexus Twitter so I don't know did they say this or not?
[Nexus 6  General] NOSTALGIA:
closing thread.. source should only be developers.google.com/android
[Nexus 6 Q&A, Help & Troubleshooting] SFG:
Use this thread to share vendors that have either sold you good batteries or bad ones. I have completed a battery swap in my N6 and the process is really rather easy assuming you have all the correct tools. The process from start to new battery installation can be found here:

https://www.ifixit.com/Guide/Nexus+6+Battery+Replacement/35878

One thing to add that is not listed in the guide is to make sure to preshape the battery to match that of the factory installed battery. If this is not done, it could impact functionality of the phone such as camera not working and also the flash. The battery is rather soft and is easy to manipulate into the correct curvature.

The battery that I have installed is a Motorola battery that was sold by the following eBay vendor:

http://www.ebay.com/itm/232047178752

I have only tested this battery for a full day and 2 charge cycles. I will update this post if the battery doesn't end up working out.
[Nexus 6 Q&A, Help & Troubleshooting] neilrl79:
I bought and installed this one last week:

http://www.ebay.com/itm/232047178752

It has identical markings to the original battery and seems to be working great so far.
[Nexus 6 Q&A, Help & Troubleshooting] SFG:
So no issues with the battery not charging to 100℅ or not charging at all?
[Nexus 6 Q&A, Help & Troubleshooting] neilrl79:
No issues at all. Installed it last Friday and it charges all the way up and seems to last better than the original ever did (I bought the phone used a year ago).
[Nexus 6 Q&A, Help & Troubleshooting] SFG:
Alright I purchased it. Hopefully I get the same results
[Nexus 6 Q&A, Help & Troubleshooting] neilrl79:
Actually I did have an issue with my camera not working after initially installing it but now I'm sure that it was caused by the actual installation then the battery.

If you do change your your battery make sure you take note of exactly how it's mounted. The new battery comes flat but the battery sits in the phone with a bit of curvature to it. My problem resolved itself, assuming the battery settled into place and allowed the camera module to contact the board properly.
[Nexus 6 Q&A, Help & Troubleshooting] SFG:
Well I wish you had said that earlier. ? Guess I will have to take my time and be thorough. Besides the basic plastic pry tools and mini torx, what else do I need? Is there any adhesion materials that need to be replaced?
[Nexus 6 Q&A, Help & Troubleshooting] neilrl79:
Like I said, I think it was my lack of attention to details that caused my issue. I had a bought a new back cover a few weeks ago that came with new adhesive already on it, but you can buy just the adhesive. Here is a link:

http://www.ebay.com/itm/141334618840

Though at the price you will pay for just the adhesive, a couple $ more will get you a brand new back cover. Just do some searching and you may find it cheaper, I just shared one of the first results.
[Nexus 6 Q&A, Help & Troubleshooting] SFG:
I'll be following this breakdown in case anybody else is looking into it. I'll report if it's accurate after I complete the swap.

https://www.ifixit.com/Guide/Nexus+6+Battery+Replacement/35878
[Nexus 6 Q&A, Help & Troubleshooting] Vivjen:
X2 battery is compartible and cheap, but lasts 1/3 less
[Nexus 6 Q&A, Help & Troubleshooting] SFG:
Sounds like the battery that I don't want
[Nexus 6 Q&A, Help & Troubleshooting] thetransit123:
what battery do you recommend to buy?
[Nexus 6 Q&A, Help & Troubleshooting] SFG:
I ordered the one linked in post #2. I'll report on it after I receive it and get it installed.
[Nexus 6 Q&A, Help & Troubleshooting] Tikerz:
Looking forward to hearing your results. Did you also order a replacement back cover?
[Nexus 6 Q&A, Help & Troubleshooting] SFG:
No I did not find the need to do so. My back cover has seen minimal daylight outside of a case.
[Nexus 6 Q&A, Help & Troubleshooting] Tikerz:
Oh, okay I was asking because of the adhesive question earlier. Thanks.
[Nexus 6 Q&A, Help & Troubleshooting] SFG:
According to the link I posted about the breakdown to replace the battery, it didn't mention it so I will tackle that issue if it becomes a problem. Hopefully it's not an issue.
[Nexus 6 Q&A, Help & Troubleshooting] fiffan86:
I just replaced my battery 24 hours ago with this one (did a frame swap and battery replacement)

http://www.ebay.com/itm/231879248130

I haven't had any problems yet. I'm glad I read this thread and sort of prebent the battery. I didn't have an issue with the camera or flash not working. I did strip 4 screws, but they came out with a t4 bit. I reused my blue back, even though I switched my frame for the silver one. I reheated it back up and I've been running without a case for 24 hours and it hasn't come off yet.
[Nexus 6 Q&A, Help & Troubleshooting] SFG:
Did you use heat to prebend the battery?
[Nexus 6 Q&A, Help & Troubleshooting] fiffan86:
No I just bent edges slightly like the original battery. I didn't want to bend it too much and ruin it