Hi, I'm new in android. I install CM12 nightly and run encryption.
- Phone do something, say 10:00 minutes,I don't see at him. After that (about 10 min) phone say something like "UI don't run, Music don't run, video ...".
- So I restart phone and process continued, but after that some aplication corrupted - UI don't respond said, more restart don't help
- Then I reset to factory and all is ok, but unencrypted
- then i run encrypt again - after 30 sec phone return back to lock screen - stay unencrypted, do nothing
- install stable CM11, run encryption - the same - phone after 30sec return to lock screen and stay unencrypted
- now I'm back to CM12
when install new rom, I use wipe/format/clear anything possible in menu
I install aLogcat to see some log, but there is imho little log - one screen. Maybe I don't know using it.
All this looks like in the first encryption corrupt some rights of directory and another encryption process corrupt immediately, i don't know.
Maybe 1 thing - widget cLock in weather says: It is not possible to determine the position - Switch on, but it switched ... weather don't respond, but I remember that it run correct, in the first ROM CM12 install.
Thans for any help
- on phone: activate adb in developer settings
- on pc: run 'adb logcat'
- on phone: start encryption process
- on pc: check logs the moment you start the encryption
aguaz said:
- on phone: activate adb in developer settings
- on pc: run 'adb logcat'
- on phone: start encryption process
- on pc: check logs the moment you start the encryption
Click to expand...
Click to collapse
Thanks for help, I find out solution - install another superuser. Probably this help, I´m not realy sure, many reinstalation tried .
But still have 2 problems:
- cannot fix cell position, only GPS work
- upgrade to new nightly CM12 never continues - there is "cannot mount /dev/. ." in recovery mode, I think that is problem with encryption - recover mode cannot acces to encryption files. I upgrade it manualy from SD, but still can´t access "/data", but system show new build, I hope thats ok even this error during upgrade.
Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you
* and point my finger right back at you.
*/
What is this ROM/thread?
This is a port to the i9000 of my work for the SGH-T959P which is the Telus version of the Galaxy S. I initially started work on AOSP to see what exactly needed to be changed from AOSP to work on my device. I had a request for access to an i9000 build hence I created this thread. This is also a place to discuss using my source code to build other ROMs and/or improve it. This is not a place for a general development "How do I build a ROM?" questions - there are plenty of guides on XDA and elsewhere that say how to do this. Since I don't have an i9000, I probably can't reproduce your bug unless it is common on my device as well. As such, I will be able to provide very limited support, so if you have any concerns about your phone bricking, do not flash anything from this thread!!
Installation Instructions
You should be able to flash this from any MTD rom, but it probably works best from a 6.0 or 7.x based ROM. Root does not come pre-installed, instead you need to manually install. Due to our odd partition system, please see http://forum.xda-developers.com/showpost.php?p=69245956&postcount=3 for instructions.
Things to Take Note Of
If you decide to install gapps at a later date (ie after you've installed the ROM), you must do a factory reset first - otherwise you will get force-closes upon bootup
This build is very close to the official AOSP source code. Recovery is TWRP but otherwise there aren't any added "features" - nor will I add any as this is
Gapps eat up about an extra 30MB of RAM so they slow down the device - tread carefully. Opengapps pico should work just fine but are untested
Backup Backup Backup! I'm not responsible for you losing any data or anything else that could go wrong.
Working on my variant
Camera (built-in app needs workaround, see below)
RIL
SMS
Wifi
Vibration
Automatic Brightness
Compass
GPS on T959P
Headset Buttons
Partially working
Bluetooth - first time trying to enable won't work, back out of the Settings page, re-enter it and try enabling again. It should work this time...
Camera and Browser apps need to have all their permissions manually enabled through settings for full functionality. This is because I've used the older Camera app (which hasn't been updated for dynamic permissions) and the older Browser app as the new one is simply a test shell with no features (thanks Google!)
What doesn't
TWRP build is currently broken. To work around this, replace the ramdisk-recovery.img in the zip with the one from CM14.1
SElinux is currently in permissive mode. Still missing are the GPS sepolicies plus the LVM ones. If someone sends me a dmesg, I might be able to change this...
What's been removed
TV-Out - It was removed upstream plus I think binary blobs would need a ton of shimming in Lollipop+ Please do not ask me to implement this, I've tried several times and failed miserably each time.
I haven't actually verified that this boots as I don't have this specific variant!!!
XDA:DevDB Information
AOSP 7.1 ROM/Discussion, ROM for the Samsung Galaxy S I9000
Contributors
xc-racer99, Coldwindofnowhere
Source Code: https://github.com/xc-racer99/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Android 6.0
Based On: AOSP
Version Information
Status: Testing
Created 2016-12-21
Last Updated 2016-12-20
Please have a look at the thread I created for my variant at http://forum.xda-developers.com/galaxy-s-4g/development/rom-aosp-7-x-galaxy-s-4g-t3485237
Build your own!
All the device-specific source code is on my github at https://github.com/xc-racer99/. The branch I've used for the build posted below is the aosp-7.1 branch. The aosp-7.1-ddk-1.19 is test branch that uses the latest DDK 1.19 PVR blobs for OMAP devices. Unfortunately, it breaks hardware decoding (and you would need to compile the correct kernel as it uses a different PVR kernel driver). It is more of interest than of actual use.
Follow https://source.android.com/source/initializing.html. The branch you want when you run repo init is the latest tag from https://source.android.com/source/build-numbers.html#source-code-tags-and-builds of 7.1. Before you run repo sync, from the WORKING_DIRECTORY/.repo folder, run "git clone https://github.com/xc-racer99/local_manifests -b 7.1". Continue on with the build guide, the device codename you want is "galaxysmtd".
If you want to build the kernel, follow the instructions in WORKING_DIRECTORY/kernel/samsung/aries/AOSP_README. Put the resulting arch/arm/boot/zImage in device/samsung/galaxysmtd
Other aries devices (captivate, i9000B, vibrant) should be fairly easy to do (ie the galaxysmtd on my github as well as the captivate trees work). The fascinate and p1 would need a fair bit of work. There is an i9000B kernel uploaded to https://www.androidfilehost.com/?fid=457095661767123305 - simply replace the boot.img in the i9000's zip with this one and it should work (except that in Settings you will appear as an i9000 instead of an i9000B).
For porting to other ROMs, please take note of https://github.com/xc-racer99/android_patches - these are the patches that the custom ROM and/or you must implement to have a successfully booting and functional device. You also need to have busybox and TWRP as part of the build tree.
Download Link and Changelogs
A reminder - I've not personally tested any of these builds...
2017-01-19 Build
Updated interactive governor - should result in fewer slowdowns if you use this governor
Changed low memory killer parameters so it kills a little quicker (ie before it runs out of memory)
Disabled a bit more background stuff to hopefully free a bit more memory
Fixed/cleaned up the shims that are used for the RIL - should prevent SSL issues (eg with Hotmail accounts) as well as being slightly faster and more reliable
Selinux is still in permissive mode (a dmesg could possibly help me in putting this to enforcing, if people are interested). I still don't know if the TWRP included in it is functional or not (someone can let me know, I guess )
Older Builds
2016-12-26 Build
Home button should now work
SD card/internal storage should work properly
Added ability to have /data on microSD (see here for info)
2016-12-19 Build
Anyone can test this build to see if data is working properly on his build ? RIL seems to crash randomly for some reason in 7.1.1 with cm 14.1 ...
Coldwindofnowhere said:
Anyone can test this build to see if data is working properly on his build ? RIL seems to crash randomly for some reason in 7.1.1 with cm 14.1 ...
Click to expand...
Click to collapse
Despite the fact that i have used all my mb to my phone,data opens normally and don't have any problem with crashes etc.
edit:Lost RIL all of a sudden with x on network.rebooted and it laid to TWRP saying no OS is installed.Starting all over again with odin etc.
ioannis_m said:
Despite the fact that i have used all my mb to my phone,data opens normally and don't have any problem with crashes etc.
edit:Lost RIL all of a sudden with x on network.rebooted and it laid to TWRP saying no OS is installed.Starting all over again with odin etc.
Click to expand...
Click to collapse
Hmm, ok. Thanks for testing. I guess that means it boots Did the sdcard(s) get detected properly? In my earlier builds of AOSP I had difficulties with this.
It's possible that my TWRP build is non-functional. Try replacing the ramdisk-recovery.img in the zip with one from @Coldwindofnowhere CM14 build.
Thanks for testing.
First of all thanks for bring AOSP NOUGHT.everything work fine.like
Camera,storage,WiFi, hotspot,Bluetooth, ril.
But I found some issues.
1.browser working but couldn't browse
But third party browser work fine.
2.outgoing call fine.but when come incoming call
Device not wakeup also get hanging till incoming call cut.also network gone.after reboot it work fine.
udhy said:
First of all thanks for bring AOSP NOUGHT.everything work fine.like
Camera,storage,WiFi, hotspot,Bluetooth, ril.
But I found some issues.
1.browser working but couldn't browse
But third party browser work fine.
2.outgoing call fine.but when come incoming call
Device not wakeup also get hanging till incoming call cut.also network gone.after reboot it work fine.
Click to expand...
Click to collapse
Hmm, did you install gapps? I'm assuming by what you mean for "couldn't browse" is that a white screen appeared instead of content. This is likely due to a different webview provider being installed which removed the AOSP one.
Odd that you're getting incoming call issues. Do these happen with @Coldwindofnowhere CM14 build? There are a couple of things I could try to fix but I'm not sure. I rarely if ever make calls on my phone so I don't know what all issues exist.
xc-racer99 said:
Hmm, did you install gapps? I'm assuming by what you mean for "couldn't browse" is that a white screen appeared instead of content. This is likely due to a different webview provider being installed which removed the AOSP one.
Odd that you're getting incoming call issues. Do these happen with @Coldwindofnowhere CM14 build? There are a couple of things I could try to fix but I'm not sure. I rarely if ever make calls on my phone so I don't know what all issues exist.
Click to expand...
Click to collapse
Umm no never had this issue with cm 14.1, but in the latest build sometimes ril just crashes for no apparent reason then it's back one I reboot.
Coldwindofnowhere said:
Umm no never had this issue with cm 14.1, but in the latest build sometimes ril just crashes for no apparent reason then it's back one I reboot.
Click to expand...
Click to collapse
Have you (or anyone else) managed to get a log (radio logcat, dmesg and regular logcat)? Just wondering what exactly is crashing. Likely rild - and there's a bug in our libsec-ril.so so that it won't restart automatically because then it crashes the system...
xc-racer99 said:
Hmm, did you install gapps? I'm assuming by what you mean for "couldn't browse" is that a white screen appeared instead of content. This is likely due to a different webview provider being installed which removed the AOSP one.
Odd that you're getting incoming call issues. Do these happen with @Coldwindofnowhere CM14 build? There are a couple of things I could try to fix but I'm not sure. I rarely if ever make calls on my phone so I don't know what all issues exist.
Click to expand...
Click to collapse
No.i didn't install gapps and not appeared white screen in browser anything browse in browser(sys app) its loading,loading, loading.....
Incoming call working but delay to wakeup when incoming call come.
I used one day full.my device good. Rarely crash ril. These few issues only problem in the otherwise this rom so good.
Sorry for bad english.
Thanks xc-racer99 for making AOSP Android 7.1 .
I just installed it on I9000B with the kernel that you made available for this device. I felt that the time of first boot after installation is faster than cm14.
I found some problems:
1) The home button does not work.
2) The android is having problem with internal storage (Data and Internal Memory). It is displaying strange values of used and available space. Camera can not save photo or video.
I'm not using SD Card External.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3) Randomly is freezing or restarting.
I'm glad that you have made the kernel available to build.
I have a question, in this code is there the patch needed to work the touchscreen of the I9000B?
Thanks,
Daniel
DanielBR911 said:
Thanks xc-racer99 for making AOSP Android 7.1 .
I just installed it on I9000B with the kernel that you made available for this device. I felt that the time of first boot after installation is faster than cm14.
I found some problems:
1) The home button does not work.
2) The android is having problem with internal storage (Data and Internal Memory). It is displaying strange values of used and available space. Camera can not save photo or video.
I'm not using SD Card External.
View attachment 3976988
3) Randomly is freezing or restarting.
I'm glad that you have made the kernel available to build.
I have a question, in this code is there the patch needed to work the touchscreen of the I9000B?
Thanks,
Daniel
Click to expand...
Click to collapse
Right, that kernel is designed for 7.0 and doesn't have the patch to fix the freezes present in 7.1. Try the one from https://www.androidfilehost.com/?fid=673368273298918331
Home button doesn't work - as in doesn't wake the device or doesn't work period? AOSP doesn't support the home button waking the device (OEMs and most custom ROMs implement this).
Internal storage - now that is interesting. In my earliest test builds of 7.0, that was a feature there. I don't know why it's reappeared. Perhaps a data wipe will fix the issue??? The Camera issue is related to this IMO. You could try using OpenCamera as I've had success with it on my device.
udhy said:
No.i didn't install gapps and not appeared white screen in browser anything browse in browser(sys app) its loading,loading, loading.....
Incoming call working but delay to wakeup when incoming call come.
I used one day full.my device good. Rarely crash ril. These few issues only problem in the otherwise this rom so good.
Sorry for bad english.
Click to expand...
Click to collapse
Ok, thanks for the clarification.
xc-racer99 said:
Right, that kernel is designed for 7.0 and doesn't have the patch to fix the freezes present in 7.1. Try the one from
Home button doesn't work - as in doesn't wake the device or doesn't work period? AOSP doesn't support the home button waking the device (OEMs and most custom ROMs implement this).
Internal storage - now that is interesting. In my earliest test builds of 7.0, that was a feature there. I don't know why it's reappeared. Perhaps a data wipe will fix the issue??? The Camera issue is related to this IMO. You could try using OpenCamera as I've had success with it on my device.
Ok, thanks for the clarification.
Click to expand...
Click to collapse
Thank you. Now the android is not freezing anymore.
About the Home Button , no function is working. Usually when it's pressing the apps are closed.
Something strange happened to the internal storage. I performed the Wipe Data.
Now I can not format any other partitions (System, Data, Cache).
I will run Odin with the partition map and Android 2.2.
To install AOSP 7.1 is it necessary to have Android 6 installed before?
Thanks
Daniel
I did some experiences:
1) If I use ramdisk-recovery.img and ramdisk.img from CM 14 or Cm 14.1. In TWRP, the size of the System and Data partitions is usually recognized and I can format them both in EXT4.
But the Android shows that the internal memory is corrupted. Not being able to record anything in memory.
2) If I use the original ramdisk-recovery.img and ramdisk.img from AOSP 7.1, TWRP does not recognize the size of the System and Data partitions and I can not format them.
The android shows that the internal memory is corrupted. Not being able to record anything in memory.
DanielBR911 said:
Thank you. Now the android is not freezing anymore.
About the Home Button , no function is working. Usually when it's pressing the apps are closed.
Something strange happened to the internal storage. I performed the Wipe Data.
Now I can not format any other partitions (System, Data, Cache).
I will run Odin with the partition map and Android 2.2.
To install AOSP 7.1 is it necessary to have Android 6 installed before?
Thanks
Daniel
Click to expand...
Click to collapse
DanielBR911 said:
I did some experiences:
1) If I use ramdisk-recovery.img and ramdisk.img from CM 14 or Cm 14.1. In TWRP, the size of the System and Data partitions is usually recognized and I can format them both in EXT4.
But the Android shows that the internal memory is corrupted. Not being able to record anything in memory.
2) If I use the original ramdisk-recovery.img and ramdisk.img from AOSP 7.1, TWRP does not recognize the size of the System and Data partitions and I can not format them.
The android shows that the internal memory is corrupted. Not being able to record anything in memory.
Click to expand...
Click to collapse
Ok, so it looks like the TWRP included with the ROM is non-functional. I'll make a note of that in the OP.
It is probably necessary to go to Android 6 (or at least 5.1) before going on to 7.1, but I haven't tested. It's just whether or not the package name is correctly detected by updater.sh. Since I don't have the device, I can't test...
With the home button, could you please get me a logcat? See http://forum.xda-developers.com/showthread.php?t=2185929 if you need instructions. A dmesg from the broken recovery would also be useful if you get a chance.
Thanks.
xc-racer99 said:
Ok, so it looks like the TWRP included with the ROM is non-functional. I'll make a note of that in the OP.
It is probably necessary to go to Android 6 (or at least 5.1) before going on to 7.1, but I haven't tested. It's just whether or not the package name is correctly detected by updater.sh. Since I don't have the device, I can't test...
With the home button, could you please get me a logcat? See http://forum.xda-developers.com/showthread.php?t=2185929 if you need instructions. A dmesg from the broken recovery would also be useful if you get a chance.
Thanks.
Click to expand...
Click to collapse
Here my logcat:
View attachment logcat.log
I had a problem to get Kernel log. When i run this command: adb shell su -c dmesg > dmesg.log. I got : su: invalid uid/gid '-c'.
I'm confuse. TWRP (ramdisk-recovery.img and ramdisk.img from AOSP 7.1.1) is now recognizing the System and Data partitions with their correct sizes.
But Android is still showing "SD Internal Corrupt" .
When I click in " SD Card Corrupt" a screen for formatting is opened. When I command to format the internal sd, an error message appears quickly and the screen closes. When I enter in TWRP, it does not recognize the size of the system and date partition.
I should not have done it
Now I'm going to have to run the odin to recover partition again :crying:.
DanielBR911 said:
Here my logcat:
View attachment 3977611
I had a problem to get Kernel log. When i run this command: adb shell su -c dmesg > dmesg.log. I got : su: invalid uid/gid '-c'.
I'm confuse. TWRP (ramdisk-recovery.img and ramdisk.img from AOSP 7.1.1) is now recognizing the System and Data partitions with their correct sizes.
But Android is still showing "SD Internal Corrupt" .
View attachment 3977629
When I click in " SD Card Corrupt" a screen for formatting is opened. When I command to format the internal sd, an error message appears quickly and the screen closes. When I enter in TWRP, it does not recognize the size of the system and date partition.
View attachment 3977630
View attachment 3977631
I should not have done it
Now I'm going to have to run the odin to recover partition again :crying:.
Click to expand...
Click to collapse
Hmm, I think we have two separate problems. I think Android having the issues is probably due to me removing https://github.com/Coldwindofnowher...overlay/frameworks/base/data/etc/platform.xml as I thought this was outdated and unnecessary (as I didn't need it on my device).
TWRP issue is probably different, don't use the one built into the ROM. I'll have another look through the config and try to fix it.
I didn't see any mentions of any buttons (home and/or volume) in the logcat, so we'll figure that problem out later. I'll add some debugging to the next kernel I upload.
Not surprising that the dmesg failed - try instead "adb shell dmesg > dmesg.log" - since we're not CM based we don't need the "-c" part.
xc-racer99 said:
Hmm, I think we have two separate problems. I think Android having the issues is probably due to me removing https://github.com/Coldwindofnowher...overlay/frameworks/base/data/etc/platform.xml as I thought this was outdated and unnecessary (as I didn't need it on my device).
TWRP issue is probably different, don't use the one built into the ROM. I'll have another look through the config and try to fix it.
I didn't see any mentions of any buttons (home and/or volume) in the logcat, so we'll figure that problem out later. I'll add some debugging to the next kernel I upload.
Not surprising that the dmesg failed - try instead "adb shell dmesg > dmesg.log" - since we're not CM based we don't need the "-c" part.
Click to expand...
Click to collapse
Thanks.
Here my dmesg:
View attachment dmesg.log
Thanks for your work!
I've got a few problems with your ROM.
RIL is unreliable at best. Surprisingly I had correct 3G performance at first flash and first boot, but then after subsequent reboots and then newer flashes / wipes, it totally stopped working. I have cell phone reception even though it's slow to get it, but no data at all. About plane mode, it doesn't cut the basic (non-data) cellphone service which is probably a bug too. P.S. : Got back data, see below.
After boot there is a notification about sdcard being corrupt, either when I have a sdcard or not. I cannot access /sdcard.
Home button doesn't work at all, period.
Wifi doesn't work at all, either from quick access or settings. In settings, when I tap to activate wifi, it stays stuck at "Activating wifi..." and doesn't change anything else except the button I tapped. This button reverts to off when I exit.
Bluetooth doesn't work at all, either from quick access or settings. In settings, when I tap to activate bluetooth, it doesn't change anything except the button I tapped. This button reverts to off when I exit. Well, after numerous tries, when I decided to generate my logcats (see below), tapping on "Bluetooth on" actually activated it successfully...and also made 3G work. Wtf?
Logs are attached to this message. Methodology for acquiring them :
Wiped everything. (Re-)flashed this ROM. Wiped data / cache.
Booted system a first time. Acquired LogcatFirst.log.
Rebooted system.
Tryed to toggle Wifi (from settings) on at aprox 02:50:04. Then exited.
Tryed to toggle Blutooth (from settings) on at aprox 02:51:25. Then exited. Please note that at this very moment, Bluetooth started working and I got back a 3G connection. Wtf?
Used home button from settings app at aprox 02:55:??. This does produce zero output to logcat.
Set plane mode from quick panel on at aprox 02:56:30, then off at aprox 02:58:36.
Acquired LogcatSecond.log, Dmesg.log and Radio.log
EDIT : After plane mode, I lost Bluetooth and data again.
Ano59 said:
Thanks for your work!
I've got a few problems with your ROM.
RIL is unreliable at best. Surprisingly I had correct 3G performance at first flash and first boot, but then after subsequent reboots and then newer flashes / wipes, it totally stopped working. I have cell phone reception even though it's slow to get it, but no data at all. About plane mode, it doesn't cut the basic (non-data) cellphone service which is probably a bug too. P.S. : Got back data, see below.
After boot there is a notification about sdcard being corrupt, either when I have a sdcard or not. I cannot access /sdcard.
Home button doesn't work at all, period.
Wifi doesn't work at all, either from quick access or settings. In settings, when I tap to activate wifi, it stays stuck at "Activating wifi..." and doesn't change anything else except the button I tapped. This button reverts to off when I exit.
Bluetooth doesn't work at all, either from quick access or settings. In settings, when I tap to activate bluetooth, it doesn't change anything except the button I tapped. This button reverts to off when I exit. Well, after numerous tries, when I decided to generate my logacts (see below), tapping on "Bluetooth on" actually activated it successfully...and also made 3G work. Wtf?
Logs are attached to this message. Methodology for acquiring them :
Wiped everything. (Re-)flashed this ROM. Wiped data / cache.
Booted system a first time. Acquired LogcatFirst.log.
Rebooted system.
Tryed to toggle Wifi (from settings) on at aprox 02:50:04. Then exited.
Tryed to toggle Blutooth (from settings) on at aprox 02:51:25. Then exited. Please note that at this very moment, Bluetooth started working and I got back a 3G connection. Wtf?
Used home button from settings app at aprox 02:55:??. This does produce zero output to logcat.
Set plane mode from quick panel on at aprox 02:56:30, then off at aprox 02:58:36.
Acquired LogcatSecond.log, Dmesg.log and Radio.log
EDIT : After plane mode, I lost Bluetooth and data again.
Click to expand...
Click to collapse
Alright, thanks for the complete rundown on errors. I'll try to go through them:
Bluetooth - having difficulty activating is not surprising. Android technically doesn't support non BT LE devices such as ours - I had to hack in support for no LE/SMP/GATT (the supporting parts of the BT stack AFAIK) with the patch https://github.com/xc-racer99/android_patches/blob/aosp-7.1/system_bt.patch. There's nothing I can really do about this. If you read the OP, it says
first time it won't enable if enabling through settings, back out and then second time it will. Works just fine from status bar pulldown
Click to expand...
Click to collapse
This was for 7.0, I guess it's changed slightly in 7.1 so I'll update the OP.
Data - this sounds totally bizarre. I wish I had an i9000 to test this. One of the big differences between the i9000 and my device, the SGH-T959P, is that you guys use the (infineon?) XMM616 for your modem while mine uses the M5720 by STE. I have yet to have an issue with data when I've tested it on my variant. Again, I'm afraid I can't do too much about this
Wifi - this sounds weird. There's some noise in the logcat, ie "12-24 02:50:04.778 W/CommandListener( 164): Failed to retrieve HW addr for wlan0 (No such device)". This is very surprising, I have nothing like this in a logcat on my device. I'm thinking perhaps that the MAC address wasn't properly setup. Could you please run "adb shell getprop | grep macaddr"? The RIL actually sets the macaddr so these two issues might be related. Did you check the md5 of the zip after downloading? It almost sounds like a bad download/ flash. The other thing is that yours is a special hardware model which doesn't like having the wifi driver built into the kernel (I did see a reference to this in a commit from the CM10.1 days). @Coldwindofnowhere's CM14 has it as a module so it might be working there.
Home button - I probably messed up the keylayout somewhere. My device has a capactive home button as opposed to a hard button. Please try pushing the attached files to /system/usr/keylayout after removing the ".img" at the end of the filename (to get around XDA's filetype filter).
Corrupt SDCard is probably my fault. Please try the new build at https://www.androidfilehost.com/?fid=529152257862690355 as I think I've found and corrected the issue.
Unfortunately, your logcat is very "chatty" - basically android prevents things from creating too much logspam. This sucks for debugging as we lose many lines, so to turn it off run
Code:
adb logcat -P ""
right at boot
Since we're having so many issues with mobile network/wifi/bluetooth, I'm wondering if our netfilter code in the kernel isn't working properly.... The thing against this theory is that things work on my variant.
My father in law died last weekend and we don't know the pincode of his stock Nexus 5X. We can access his Google account and we know the pincode of his sim card. I hope someone can help us out to get access to his phone. Things we've tried:
- The vingerprint reader was setup but we've tried a lot of possible pins. We've tried his vinger yesterday but because of the attempts the pin is also required now.
- With a pattern lock you'll get a possibility to unlock through the Google account password after some attempts but his phone was secured with a vingerprint and/or pincode. Only the delay between attempts get increased, currently 16 minutes between them.
- The lock option from https://www.google.com/android/devicemanager, but because there is already a pin lock it doesn't work. The pin doesn't change.
- I've tried to access the phone through ADB, booted into the recovery but "adb devices" doesn't see the phone. When I choose to "install update through adb" I see the devices with "adb devices" but I can't use "adb shell", only sideloading works.
- Installing a custom recovery could work but the bootloader is locked, when I unlock it a full wipe will be performed so we still can't access the data.
- From the Play store in the browser on my Mac I've installed the androidlost.com app on the phone, but the app needs to be opened once before it can be used.
- A rubber ducky could help us out, but I don't have one and the time between attempts get increased and increased... it would take weeks, months or years to unlock.
What other possibilities do I have?
First sorry for your lost!
Second, i don´t know for sure, but maybe get the phone to the store where you bought it and explain the situation, maybe they will give a correct advice or like you said the phone is registed in google ( device manager) maybe if you contact them they will help you with that ( the problem is they probably will take a long time to reply or don´t reply at all) or wait for a more expert user than me here in xda,
again, sorry for your lost and hope you solve this problem,
cheers
If the phone was rooted with a recovery installed, YES, you could delete the passcode files and get into it, without root/recovery, you cannot get into it without the password, that is the point of encryption and passwords and all that jazz.... Yes there is probably a way for some high level hacker to do it but good luck finding that.... If you just want to be able to USE the phone, do a factory reset from recovery....