yashsingh1/xdaforums huggingface dataset:
[Xperia Z5 Android Development] zacharias.maladroit:
No no no, it's not the kernel that has the dual sim detection sim script, it's the "device configuration" or "device" ;)

also I doubt that this would work with kitakami or sumire when coming from eagle,

this needs further investigation ...

edit:

There's a sim detection driver in the kernel (the copyleft one) but I'm not sure yet whether it supports dual slim variants or where the dual sim handling is done

edit2:

the sim_detect driver is included in both copyleft kernel releases:

https://github.com/sonyxperiadev/kernel-copyleft/commit/b4706ce484622268e35e41949c3d1a32a6554a57 32.0.A.6.115: Open source code

https://github.com/sonyxperiadev/kernel-copyleft/commit/c5dc92e9e820fd7a04090dafde9548010ac84516 32.1.A.1.163: open source code

but Sim detection obviously is handled differently in the AOSP/"Opensource" Kernel

[MENTION=985241]erikcas[/MENTION] 's gpio muxing magic:

https://github.com/sonyxperiadev/kernel/commit/16767a1a65557a1d17f9d29df0887434f2b552b7 eagle: add dsds support

https://github.com/erikcas/android_...mmit/6caf915d5d8d5c0957c69fb2384415cf00152072 Add dsds support

https://github.com/erikcas/android_...mmit/c6e8db736a92db0ebd2668cd5c07b60534dc52d7 ds-ify

edit3:

the generic initrc changes are also already there:

https://github.com/sonyxperiadev/de...mmit/3317972d00c5a4085d7a0260db18523ca52df48d add dsds service

(running 2 instances of ril-daemon)
[Xperia Z5 Android Development] bioan:
I was just trying to prove with evidence that people always blame lame/stupid/disaster stock battery life. On stock Sony ROMs this isnt't the case. People either have bad apps, either strong usage pattern.

I had almost entire Z series, including GPe Z Ultra, and battery life was bad on any custom ROM.

P.S: The image is a screenshot uploaded via official Tapatalk app. It looks absolutely normal on phone.

P.S2: I will rest my case here cause it will lead to too much off topic.
[Xperia Z5 Android Development] zacharias.maladroit:
Haha - you can't win this battle ;)

Yesterday:

dirty-flashed several AOSP builds + Kernels:

20% in 6 hours (and I can't pull down the notifications panel) :D

Lesson learned: you need to wipe userdata and other stuff in between flashing unless you do an OTA update with AOSP builds ^^

Back to topic:

The Google Play Services, Store and other parts are clearly the biggest battery drainer - without it it was 1% per 8+ hours or so,

and after that 1% per several hours

but yes: Sony's Stock ROM clearly is broken on the Z5 - not sure why or how
[Xperia Z5 Android Development] uripiruli:
Zacarias, will be possible in the future use your aosp with drm Keys?? And no loose the Sony camera for example...

Enviado desde mi E6653 mediante Tapatalk
[Xperia Z5 Android Development] zacharias.maladroit:
Perhaps,

including that file in the kernel initramfs is no problem,

I doubt however that the current approach of the AOSP builds or our CyanogenMod port with the AOSP-based kernel would work with the Sony Camera,

You most certainly need the libv4l2 camera driver for this to work - so you'll need to use Sony's "copyleft" kernel, the proprietary driver files and above all Sony's ROM Framework

Doesn't sound too easy and I'm sure it involves some work - but it has been done before

http://xdaforums.com/crossdevice-dev/sony-themes-apps/port-xperia-z4-framework-sony-stock-t3154772 [PORT][CM12/CM12.1/AOSP] Xperia Z4 Framework & Sony Stock Camera

Your best bet in the long run for this probably would be [MENTION=5604178]zwliew[/MENTION] 's CyanogenMod port and then with the work with Modders/ROM Chefs/Contributors/... - the power of the community - this could be achieved

So - short answer: YES !

More detailed: it depends if you can get AOSP to work with Sony's "stock" kernel, then you might have the issue of high battery drain, which I couldn't pinpoint its origin yet ...
[Xperia Z5 Android Development] uripiruli:
Thank you very much for your answer. If I understood well... In your aosp doesn't work radiofm. There is a developer that could help us with this... He has an app spirit fm and he makes support for the hw. A lot of devices with cyanogen have radiofm support for him. If we will speak with him maybe he does it....

Enviado desde mi E6653 mediante Tapatalk
[Xperia Z5 Android Development] zacharias.maladroit:
I asked him and he said if the FM Radio used a Broadcom chipset we're out of luck ? :confused:

Not sure what chipset the device uses - but perhaps the folks over at iFixIt can say it https://de.ifixit.com/Teardown/Sony+Xperia+Z5+Teardown/52300

(or from watching the video)

I tested Spirit FM 1 and 2 and several other FM Radio apps and it didn't work,

there however also wasn't a FM Radio driver loaded - so with that it might work

Might need porting from Sony's copyleft Kernel though or porting for a different device.

All this proprietary driver fussing makes me feel dizzy in the head :(
[Xperia Z5 Android Development] uripiruli:
Spiritfm doesn't work if he wouldn't support. He update his app with some generics drivers of our device I think. But the rom needs intern support for the radio fm. I know this because cm always say when it's roms have radiofm support. They implant this option when they rom is more or less stable.

Enviado desde mi E6653 mediante Tapatalk
[Xperia Z5 Android Development] zacharias.maladroit:
So in what relationship does the camera HAL, drivers, firmware, etc. of the Z5 stand in relation to Sony's Experimental AOSP camera ?

Nil ?

http://developer.sonymobile.com/201...-camera-available-for-experienced-developers/

http://www.androidheadlines.com/2016/01/sony-calls-on-developers-with-experimental-aosp-camera.html

Currently our camera lacks focus ability - there might be some issue with handling of the lens & shutter, optical zoom, etc.

(could be firmware, software, driver, etc.)

using CameraNext Mod v10 (CameraNext Mod v10 CM13.apk - can't pinpoint the exact thread I found it on the Z5 forums),

preview is exact, colors are correct

but both in preview and the final snapshot the whole picture is blurry, text non-readable - clearly pointing at a zoom/focus issue ...

The following post with the Z3 also points in that direction: http://xdaforums.com/z3/help/rom-aosp-camera-focus-t3187618 Rom AOSP and camera focus

To [MENTION=359497]jerpelea[/MENTION] and the other devs: please soon-ish add support for the Z5 family,

alternatively advise from anyone would be great to "fix" this to get at least somewhat decent picture quality, blurry, non-sharp pictures are kind of pointless with an Sony Exmor 23 MPixels sensor :p
[Xperia Z5 Android Development] zacharias.maladroit:
Hm, looks like we need an AOSP build (no new ones for a very long time)

Anyone interested ?
[Xperia Z5 Android Development] celderic:
The last time I tried 6.0 aosp, I couldn't get mobile data to work, not even emergency calls. But thinking about it now that was before official 6.0 was released so I was still using the 5.1.1 modem.

I'll download sources and build from scratch tomorrow and see if the 6.0 modem helps things :)
[Xperia Z5 Android Development] zacharias.maladroit:
Afaik I also flashed it with Lollipop in the beginning but it still worked - but there were still issues with a few parts,

meanwhile the proprietary blobs are at v4 (compared to v2 or so when last tried) - so that also might make a real difference.

a build is under way,

I'm curious what has improved on AOSP ("plain"),

still waiting for Camera changes + fingerprint support from Sony :fingers-crossed:

Won't flash it though, just had flashed CM, then RR and back to CM :silly:

That's enough flashing for some time now

Thanks
[Xperia Z5 Android Development] celderic:
Interesting. Think I was on v2 aswell, I must of done something to stop it from working in my build then.

If you have enough bandwidth, upload the system.img and boot.img and I'll test for you tonight :) saves me having to re sync sources and build tomorrow.
[Xperia Z5 Android Development] zacharias.maladroit:
Build time is around 45-50 minutes now - still around approx. 30 minutes to go (it builds system.img, the flashable zip and OTA - that makes it in essence build it at least twice so doubles the build time or even triples it),

upload also will take some time - so it probably won't be ready tonight :angel:

There are 2 new interesting topics / articles on building a ROM:

http://xdaforums.com/chef-central/android/guide-how-to-build-rom-google-cloud-t3360430 [GUIDE][COMPLETE]How to build ROM with Google Cloud

http://www.xda-developers.com/biggest-bottlenecks-building-android-from-source/ Biggest Bottlenecks When Building Android From Source
[Xperia Z5 Android Development] zacharias.maladroit:
New AOSP build:

6.0.1_r31

aosp_e6653-20160421-6.0.1-M5C14J
[Xperia Z5 Android Development] zacharias.maladroit:
Well, the camera preview is still messed up,

but at least with Camera FV-5 the pictures appear to be decent and Focus seems to work, too :)

edit:

well - one picture, that is,

after that it keeps on hanging the phone and leading to hardlocks :(
[Xperia Z5 Android Development] paulle:
yesterday there was an update for camera fv-5 (saying there is now z5 support), I tried it and the camera works (took various pictures and had no hanging or hardlock). But Focus didn't work (sharp at short distance, blurry than more than 1 m distance). :(
[Android Q&A, Help & Troubleshooting] L|nk:
Hi, I have installed the CM13 (6.0.1) on my nexus 5.

The menu Settings of this CM is different from the stock one; it miss the voice "Smart Lock" that has been moved in the menu "Lock screen". I need to restore the Smart Lock option inside the Security section of the menu (because It is needed by the application Mi Fit to add the Xaiomi Mi Band as a trusted device).

I have downloaded and compiled succesfully the source code from the official cm repository but i cannot add the option i want to...

It seems that there is a unique file (SecureSettings.java ) which manages both "Lock screen" and "Security" options, and there is a sort of flag that hides options according to the section...

If there is someone who has experience in android.settings, I appreciate any kind of support :):)

Thx
[Android Q&A, Help & Troubleshooting] syl0n:
No one is able to help? damn. I am waiting for this too.
[Fire Q&A, Help & Troubleshooting] possibleNoob:
Specifically it's an ION iCade. I've tested on stock, CM, and SlimLP, and it doesn't work. It is able to pair and connect, but beyond that it just does nothing. It will pair and type on my iPhone but not my Fire. I have tried unchecking and rechecking the "Input device" option, and it says "Connected to input device", but it doesn't show up in "Language & input" (though I'm not sure if it's supposed to.) I have tested mame4droid and mame4droid reloaded as well on every rom (on the slim chance that it's being recognized as a controller, not keyboard) and it has the same problem -- nothing happens.

Edit: I have also tried an app called Bluetooth Keyboard Bug Fix (com.heightdev.ganhou), and it didn't do anything to help either.

I'm quite new to Android (first device I've gotten) so maybe I'm missing something obvious.

Any ideas on how to troubleshoot this?
[Fire Q&A, Help & Troubleshooting] Pond-life:
Hmm. Don't know, dug mine out and tried it now, my bluetooth keyboard just connects. Didn't see a check box anywhere. I thought it might ask for a code but it didn't. Shows up in Keyboard and Language settings in section I don't think was listed before connection called Physical Keyboard rather than in the keyboard and input methods list.

Yeah that section vanished when I turned keyboard off.

So erm can say that stock can use a bluetooth keyboard but not much in way of clues as to why not your one.
[ONE Q&A, Help & Troubleshooting] RohanKalra97:
i installed reserruction cm13 based

restored whatsapp backup

no profile pic of any contact is being shown

tried everythig

reinstalled whatsapp etc etc

any help ?
[Unboxing and First Impressions] tkdsl:
[YOUTUBE]kYfDDTVFkI0[/YOUTUBE]
[Unboxing and First Impressions] MSF Jarvis:
It's Jordan Keyes, not jodan keyes
[Unboxing and First Impressions] bhsoz:
Thanks
[Shield Tablet Q&A, Help & Troubleshooting] SireSalty:
Hello,

I have TWRP currently installed on my K1, and can't install the 6.0 Marshmallow update as a result. Does anyone have the factory recovery I can reflash to install the update?

I can't use the one on the website as it brands my device differently, and I would prefer to keep it identifying as a K1.

Please assist, Thank you

Michael
[Shield Tablet Q&A, Help & Troubleshooting] SireSalty:
I think for all those who have the stock OS, but rooted and TWRP I might have the solution. I extracted the recovery.img from the 3.1.1 original Shield Tablet factory image, flashed that and was able to run the OTA! http://developer.download.nvidia.com/mobile/shield/ROM/ST8/3_1_1/nv-recovery-image-shield-tablet-wifi-update3_1_1.zip
[Shield Tablet Q&A, Help & Troubleshooting] kirsham:
need recovery for K1

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

this is not the correct version is that the first tablet shield. if you install this version on a k1, you would have more access to certain functions as the hub that nvidia home fell hs. again there is no setting has days on this version.

es that someone would have the original word file for K1 and shield only for K1?

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

ce n'est pas la bonne version celle la est pour la première shield tablette. si vous installer cette version sur une k1 , vous n’aurais plus accès a certaines fonctionne comme le nvidia hub qui chez moi est tombé hs. de plus il n'y a pas la mise a jours sur cette version .

es que quelqu’un aurais le fichier recovery d'origine pour shield K1 et uniquement pour la K1 ?
[Shield Tablet Q&A, Help & Troubleshooting] PhoenixTank:
Annoying that Nvidia haven't released any factory images for the K1.

I uploaded these images a little after I got my K1 last month:

https://www.androidfilehost.com/?w=files&flid=45982

I have not had a chance to test these yet! Use at your own risk!

They were created with dd, while booting twrp (not flashed), and as far as I know, should be fine to fastboot flash.

You'll need 7-zip to unpack the system.7z (sorry... my upload speed is dire and every byte saved helps!)

Edit: I've murdered the system.img.7z. Seemed to be causing problems.

There is now a TWRP backup of a clean /system in there.
[Shield Tablet Q&A, Help & Troubleshooting] SireSalty:
SOLUTION: Just flashing the recovery.img in the non K1 recovery image works. Yes, you have to download a 2.3 GB file for a 8 MB recovery image, but it works with no issues. Running 6.0 now/
[Shield Tablet Q&A, Help & Troubleshooting] Smultie:
Gives me a crashy Android figure screen.
[Shield Tablet Q&A, Help & Troubleshooting] Exile1975:
That's the stock recovery...
[Shield Tablet Q&A, Help & Troubleshooting] fusionero:
Stock Factory Image Lollipop of K1:

http://developer.download.nvidia.co...age-shield-tablet-sb_na_wf-37154_590.0364.zip

:highfive:
[Shield Tablet Q&A, Help & Troubleshooting] PhoenixTank:
Glad to see they've added the K1 to https://developer.nvidia.com/shield-open-source#tablet-k1

Cheers!
[Shield Tablet Q&A, Help & Troubleshooting] variance:
NM. to extract had to install cygwin and execute the file there to autoextract it.
[Shield Tablet Q&A, Help & Troubleshooting] SeekingSight:
That's sweet. Users of the original Shield can obtain Marshmallow faster now
[Shield Tablet Q&A, Help & Troubleshooting] troy22:
does anyone have 6.0 recovery? i tried 5.1.1 recovery and cant get 1.1 ota to work.
[Shield Tablet Q&A, Help & Troubleshooting] aaronne:
see if this post from PixelVixen http://xdaforums.com/showpost.php?p=64093509&postcount=2 helps, try to extract the 6.0 ota and seek for files needed

edit:

Nvidia removed the ota 1.1 due to wifi issue on some users

https://forums.geforce.com/default/...read-released-02-01-16-/post/4796216/#4796216
[Redmi Note 2 Q&A, Help & Troubleshooting] PytSkee:
So I got the 5.12.10 update for the weekly developer ROM and it installed stock recovery over TWRP and unrooted my phone. The first time I rooted I managed to flash TWRP with stock recovery, but it isn't working this time. I've had a lot of trouble trying to install via ADB drivers. Help please?
[Redmi Note 2 Q&A, Help & Troubleshooting] elaurens:
Did you rename TWRP to update.zip and put it on the root of the internal storage before flashing? If yes and it still failed, you'll have to give us a bit more info as to why it failed to flash (any error messages f.e.?). Should be fairly trivial to flash TWRP and SuperSU :)
[Redmi Note 2 Q&A, Help & Troubleshooting] PytSkee:
It wasn't too difficult the first time, but the recovery seems to be using some sort of signature on the ROM's. All it tells me is that "Install update.zip failed! update.zip signature verification failed." It is named update.zip on the root of internal storage.
[Redmi Note 2 Q&A, Help & Troubleshooting] elaurens:
Hm, from what I've found on the miui forum, you're not the first one having this issue. These are the "possible" solutions I've gathered from a couple of threads.

1) Flash TWRP using fastboot (rename twrpxxxx.zip to recovery.zip and place it in the same folder as the fastboot executable):

fastboot oem unlock
fastboot flash recovery recovery.img

2) Update your current ROM (stable/developer) to the latest version if that isn't the case yet and try flashing TWRP again trough the update app

3) Flash TWRP using Flashify

1. download flashify app from playstore and give root acces

2. download img of twrp for redmi 2 note and put in your sd card (I prefer sdext root folder)

3. Open flashify, select "recovery image", find the img file you've downloaded

4. confirm flash, wait until it's done

4) Re-download a copy of TWRP or use a different one (like this one for example)

Let me know how it went..
[Redmi Note 2 Q&A, Help & Troubleshooting] PytSkee:
So I tried Flashify and every time I tried to use it, the app froze right before/after selecting the recovery image. I did, however, manage to make the ADB and fastboot methods work on my desktop PC. I have no idea what I did wrong before, maybe the wrong ADB drivers? Anyway, I did get it working, so thank you :D
[Redmi Note 2 Q&A, Help & Troubleshooting] timberwolf60:
Used windroid to do all these: http://en.miui.com/forum.php?mod=viewthread&tid=167882&extra=pag
[Redmi Note 2 Q&A, Help & Troubleshooting] PytSkee:
I remember seeing this right after I ordered my phone. I had totally forgotten about it by the time I got it though, as it was more than a month later :D But thanks for reminding me, I already have it installed on my home PC!
[Wing, P4350 General] jehuty2:
unlucky.my C800 bricked again.

that feels really suck.

worest wishes to HongDa(DOPOD in taiwan,China).LTD!
[Off-topic] adarshd:
There are people who 'love' their phone too much.Sideloading an app to their phone may hurt them.They keep their phone as close as possible to stock.

Being a tweaker,people like that may run away from you.Do you have any such experiences?? Share them here. (example for such people may be your sister or your mom.Usually they dont like their phone being touched by others...)
[G2 Q&A, Help & Troubleshooting] ssj1236:
Hi I just purchased a T mobile LG G2 i was watching a 720p mkv it was HD the phone got around 98F in temp and the battery dropped at least 15% after i was 20 minutes in. Is this normal ? Can i do something to reduce it? Would Mp4 format help in keeping the heat down?
[General Questions and Answers] brokenjimmy:
Is there an easy way to root this tablet?

The tablet is a RCA Voyager Pro. Model number is RCT6773W42B. It's running Android 5.0.1 Lollipop. Build number is RCT6773W42B-ANDROID5.0-V 19-V1.12.50-KC-B.

I want to root it so I can use the WWE App (No luck with Google Play or 1Mobile or Aptoide). I would so like to use some videogame roms also if possible. That's what I mostly would like to do. Nothing much else. I am not too computer savvy but I do know the basics. So anything that would be pretty easy/simple would be awesome.
[General Questions and Answers] shane654852:
Looking for root also. Tried everything to no avail. Hopefully something comes out soon.
[General Questions and Answers] slimno19:
+1
[General Questions and Answers] dogboy322:
MobileGo

Wondershare MobileGo. Free trial, but it works. Download it to pc and connect tab. It will install a "connector" app on the tab, then hit the "one click root" button and let it reboot the tab 3 or 4 times. It may stick on the dog splash screen for a while but don't panic. I did at first, but when it came back up it had root.
[General Questions and Answers] icy201:
Don't use wonder share!!!

This tablet is not root capable out of the box, the reason for this is that the boot loader is locked which prevents any kind of modification of firmware as well as root. Now, I have not unlocked my boot loader yet on mine so I can't tell you if unlocking will allow installation of root but to unlock the boot loader first, read all instructions before attempting and I'm not responsible if your device bricks!

1. Turn device off

2. Hold volume up key then hold power key

3. Let go of power key once it starts booting but continue holding power up key until you in the recovery menu

4. You will see option to reboot to boot loader, navigate to it using volume key then select it using power key

5. You should see fastboot in the corner, now you need android SDK tools and adb ect. Which if you don't have you can google it.

6. Open command prompt from the sdk/adb folder by holding shift, right click, open command prompt.

7. Type adb devices to make sure your device is connected. If not make sure you install correct drivers for this tablet.

8. If everything is good continue by typing "fastboot oem unlock" without quotes it should pop up a screen on the device asking to unlock boot loader or it will automatically unlock it. Now you can try different programs like kingroot or manually install root with command prompt.

I can not confirm this will work as I have not had time to unlock mine yet. And again I'm not responsible for anything that may happen to your device bricked ect
[General Questions and Answers] pr3dicament:
You're not going to be able to unlock it.. there's another thread on this and it's got nothing to do with any human.

Bootloader is locked. Gotta try other stuff. I've had this for months and it's a piece of junk.. frankly, to me, anyway.. it's worthless without root privileges.

---------- Post added at 03:01 PM ---------- Previous post was at 02:08 PM ----------

... nope. Still no root. Even said "root failed" .. I'm just gonna see if anything else is updated. I've had this tablet for a couple of months thinking there'd at least be a few exploits to use but there's almost zip that I've been able to see. and I'm not the only one that can't unlock the bootloader with fastboot. Not sure what else to think at this point.. but this was a waste of time.
[General Questions and Answers] icy201:
So why is the boot loader non-unlockable?
[General Questions and Answers] dogboy322:
Re: Wondershare

I wouldn't make up a story if it had not rooted. Yes it said "root failed" the first few cycles of rebooting, but after several cycles it rooted. Now... if Wondershare is malware, this may be related... a week or so later the touch screen developed two rectangular "dead" spots that no amount of factory resetting could fix. I could not even type wifi password without rotating it in circles to avoid the dead spots. If you want a decent tablet for under 100, spend 30 more and get the Nextbook Ares 8. Very hard to root as well, but TWRP did the trick.