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.
Recently some users including me are having issues with BT Connection, device search, setting device name and making changes persistent.
BT MODULES THAT IT WAS TEST ON:
SD-968 - [HA] [MCU MTCE 2.75] Firmware 20180201 and few earlier = WORKS
MD725 - [??] [MCU ???] Oreo Firmware = DO NOT WORK (According to feedback) LogCat needed to see if Firmware communicate with BT Module at all.
METHOD 1 (SHORTER):
1. Force Stop BT app
2. Clear DATA and CACHE for BT app
METHOD 2 (LONGER):
Here are the steps I've done to make it work.
1. Boot device (restart if it was not in deep sleep)
2. Directly go to system BT settings (drop notification and tap on BT)
3. Set Device name and PIN
4. Press refresh
5. Go to Home Screen (Home Button)
6. Open BT App -> Configuration
7. Name and PIN should be entered now
8. Disable/enable Auto Connect and exit app
9. reenter app and configuration to enable Auto connect
10. Make sure that all previous BT profiles for HU are deleted on phone and that phone is visible for all devices (usually when BT configuration is open device is visible)
11. Try to search for devices. It should fail (it failed for me)
12. Go to factory settings
13. Change BT Device even it is wrong one (I have SD-968 I changed to MD725)
14. Tap Apply -> Exit -> CANCEL on reboot prompt (without doing step 13 there will be no scheduled restart)
15. Reenter Factory settings and set correct BT Module (I have SET SD-968) Tap Apply -> Exit -> and Confirm REBOOT
16. After Reboot Go to BT App and try to search for phone it should be found (make sure it is visible like in step 10)
17. If all is OK you should see the phone and you should be able to use it normally (it worked for me)
Attached pictures of some steps for METHOD 2.
NOTE: I'm ATM at HA 6.0.1 Firmware from 20180201 and issue happened after upgrade. Also from what I see Users have same issue with and after Oreo update. Hope I helped
Thanks for the info. Have you tried this method also for oreo rom as well ?
A step that worked for me was to clear data and cache for bluetooth app..
julien_blanche said:
Thanks for the info. Have you tried this method also for oreo rom as well ?
Click to expand...
Click to collapse
Haven't updated to Oreo yet.
Phycopat said:
A step that worked for me was to clear data and cache for bluetooth app..
Click to expand...
Click to collapse
Good point it didn't worked for me but, it can also help. Added to main post.
You can trigger a reboot with "hctreboot" in factory settings. Does that work instead of doing steps 12-15?
I definitely have the BT issue. I have an Xtrons(GS) MTCD/E PX5 Oreo and an Xtrons brand OBDII. They won't talk or disconnect. I'll try this tomorrow morn and report back.
jdisco1 said:
You can trigger a reboot with "hctreboot" in factory settings. Does that work instead of doing steps 12-15?
I definitely have the BT issue. I have an Xtrons(GS) MTCD/E PX5 Oreo and an Xtrons brand OBDII. They won't talk or disconnect. I'll try this tomorrow morn and report back.
Click to expand...
Click to collapse
I have same GS MTCE 2.75 PX5 OREO but an old OBD2, give HU same password as OBD2 adapter..
jdisco1 said:
You can trigger a reboot with "hctreboot" in factory settings. Does that work instead of doing steps 12-15?
Click to expand...
Click to collapse
Point of 12-15 is that HU re init Module itself along with software. Not sure if it works that way on MTCD/E but usually it works on modular systems.
Tried with PX5 oreo installed with no luck. Both methods are not working for me.
PekeMM said:
Haven't updated to Oreo yet.
Click to expand...
Click to collapse
What???(I thought that this was a trick for oreo)
In my unit BT(MD725) works without any tricks for MM.
I tried your trick with 2 kinds of oreoROM(HA and GS) but BT did not work.
Thanks anyway
I'm sorry, but as I wrote I have SD-968 BT module not MD725. I'll update main thread with so far know to work devices.
Any news?
JonatanP said:
Any news?
Click to expand...
Click to collapse
Not that I know, I'll be back from Trip on Sunday, so I hope I'll finally finish the tests and upgrade to Oreo in April.
seems to be the same
The solution is to go back to android 6, the problem is that it is not as fluid in my case as android 8.
Hi, same problem here....
I can not use my ODB2 connector on my Android 8 radio either.
Is there an adapter that works?
Is there a trick to make it work?
Greetings and thank you!!
Hi..any update on how to get the bluetooth working on android 8..
Mtcd ksp px5
warata said:
What???(I thought that this was a trick for oreo)
In my unit BT(MD725) works without any tricks for MM.
I tried your trick with 2 kinds of oreoROM(HA and GS) but BT did not work.
Thanks anyway
Click to expand...
Click to collapse
if you still have android 8 installed, try going to factory setting and change the BT Device even it is wrong one (anything other then MD725) tap apply and exit and reboot.
after reboot change the BT device back to the original one (MD725) tap apply and exit and reboot.
after reboot go to the system BT and try to search if the phone name appears let me know.
i still didn't try the above method on android 8, but if anyone with MD725 module is still using android 8 please try and update us.
thanks
i was having problem with bt too...
here you can read my post https://forum.xda-developers.com/showpost.php?p=77525417&postcount=791
now i have Oreo Rom in a px5 board (32+4) with MD725 BT module working well
macoloco said:
i was having problem with bt too...
here you can read my post https://forum.xda-developers.com/showpost.php?p=77525417&postcount=791
now i have Oreo Rom in a px5 board (32+4) with MD725 BT module working well
Click to expand...
Click to collapse
Thanks, you said in that thread ".i have found a directory where all manufactures update.zip where listed
Go there , pickup last LM version" could you say where this directory is? Once there what do you do with that file?
bjt2 said:
Thanks, you said in that thread ".i have found a directory where all manufactures update.zip where listed
Go there , pickup last LM version" could you say where this directory is? Once there what do you do with that file?
Click to expand...
Click to collapse
i wrote all my procedure here
https://forum.xda-developers.com/showpost.php?p=77525417&postcount=791
and here
https://forum.xda-developers.com/showpost.php?p=77538182&postcount=796
Dasaita MMCNP - BT connection problem
Hi, I have Dasaita HA2106-V840-8 a problem with Bluetooth connectivity. First time I managed to connect my phone to Dasaita MMCP (car_kit), but after a few days the devices failed to connect. I guess my device has embedded SD968 BT chip, in accordance with the description.
When I enter the name of the device and new PIN in BT settings, and then turn on finding the device, they are not visible to each other. I tried this other day too, but when I turned MMCP, entered settings was gone (not memorized). No name, no PIN, but also there is no connection. Search doesn't have results. At the end I tried to unpair devices and pair them again, but I get a message on my phone "Unable to communicate with CAR_KIT".
When I entered in settings for BT (settings/car/factory setting/application-choose...) it was set to WQ_BC6. And then I tried to set up SD_BC6, reboot, search BT, nothing was found again. Then I returned to WQ_BC6, reboot, search BT, without success. In the end, I tried to set up SD968, but it's not worth it anyway, MMCP does not see a mobile phone. I also tried several phone models without success. I also went to the BT application and clear data and cache, but always the same thing - BT devices do not see each other. I'm not even sure BT is ON because it doesn't have a special slider to move On/Off.
What should I do? Please help me!
* Your warranty is now void.
* I'm not responsible for bricked devices, dead SD cards,
* Please do some research if you have any concerns about features included in this recovery
* 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.
Click to expand...
Click to collapse
Pixel Experience Plus for Galaxy S21 FE (Snapdragon/Exynos) based on Android 13Unlock bootloader first:
Go to your phone → Settings → About Phone → Software information → Press Build number 6 times until you see the notice “You’re now a developer”
Go in Settings → Developer options → enable OEM unlocking
Power off your phone first. Then, connect a side of your USB to your PC/Laptop, keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone.
When you arrived at Download Mode, long press volume up until you see the black screen. Confirm to unlock the bootloader and you will erase your device.
Click to expand...
Click to collapse
Guide for flashing system image:
Flash recovery for snapdragon version, i'm using: OrangeFox Recovery is also provided for exynos soc
Please do everything that is written for flashing recovery (Installation), u need to disable encryption and wipe data
reboot when you sure recovery is permanent and check if phone is on "hello screen"
How to boot on recovery first time BEFORE "hello screen":
Uncheck reboot after flash AP recovery in Odin, unplug cable and then push vol - and power -> immiedietly after turn off download mode hold vol + and power and plug in cable -> now should work
Flash GSI image:First you need to download image from here: here or find thread here: click. This images have Google Apps allready included.
Remember to use arm64 with b !
Reboot to recovery
Now u should see on PC when u connect via cable internal memory - copy image to folder, probably should be "Fox" or create new
Touch files, find image
Now select to flash System image
Reboot
And thats it you should boot to system.
Post install settingsOn Phh Treble Settings set:
Samsung features:
Use alternate audio policy
Enable stereo audio mode
Enable extended brightness range
Enable double tap to wake (if u want)
Enable reversed wireless charging (if u want to reverse charge other device)
Enable access to all cameras
Enable extra sensors
Misc features:
Force FPS to [email protected] if you want 120Hz refresh rate display
On camera set expose aux cameras and force enable camera2api
Select Use System Wide BT HAL if u use bluetooth headphones and don't have audio (tested on galaxy buds 2)
Qualcomm features:
select use alternate camera profile if u have trouble with ultrawide photos
Root access on Pixel Experience Plus:
You should first patch boot img from your stock samsung rom what you allready using
U need to select ap tar.img file in Magisk and wait to be patched
Extract boot.img from it after patch
Flash boot img in recovery on boot image
Root stays even if you reflash system on other GSI
Works:
WiFi 2.4GHz and 5GHz
RIL (phone and mobile data)
Bluetooth with bluetooth audio
fingerprint sensor
Google Pay with NFC (you need to pass safynet check if you have magisk)
120Hz display
Camera front and back (you need other camera app for using ultrawide photo)
Fastcharge
Stereo speakers
Galaxy accessories (Watch 4 and Buds 2 tested)
MHL mode
Probably other functions too
Not work/problems:
Netflix have videwine L1 but no HDR content support
Movies only record max on 30FPS on 4K
On the go don't work any of galaxy wearable devices, you need to patch via magisk some files
Clear View cases (phone don't response for open or close case) even on AOD
Some problems with updates for Chrome and web framework (need to install manual newer version)
Device is showing as Huawei Nexus 6P need to be changed somehow to our model
Workaund for Galaxy Wearable and Google Pay:
Magisk need to be in zygisk mode
Flash Universal SafetyNet Fix, here: github download
Install FoxMMM for magisk modules finder here: here, find and install MagiskHide Props Config
Flash this for workaund of wearables: gdrive module download
Now download Galaxy wearables from store, and plugins for your proper device form apkpure or other website.
You need to allow all permisions for apps first
Try to find your watch and pair it, you need to be fast to accept all pop ups - u dont need to login to samsung account , for me got it after 2-3 try, you should see "prepairing device" etc.
For galaxy buds should be easier just find it and pair.
Google Pay works out of the box after installing this modules
Get better sound and equalizer:
If you want to have better audio - you need to flash magisk module ViperFX
Download here: click here on github
Flash via magisk
Uncheck legacy mode for work
@hunter3000
Greetings. Since this appears to be a "guide," I have changed the thread designation accordingly.
-Regards: Badger50
@hunter3000 i think you can change the model number in the build.prop if im not mistaking
Hi, can i flash it like the offical pixel experience? Because the offical one is a zip file and this one not
this is GSI style rom, not specific ROM for specific model, so you must flash it by twrp or by fastboot command. Like universal rom for all phones than have project treble.
Thanks for support
Im looking to xda everyday for a stable pixel rom
MemurBey said:
Thanks for support
Im looking to xda everyday for a stable pixel rom
Click to expand...
Click to collapse
Majority of GSI are stable but you will have bugs tho. Like either bad battery life or camera isnt working
On this build all functions is working, for camera ultrawide support you need 3rd party app like OpenCamera.
hunter3000 said:
On this build all functions is working, for camera ultrawide support you need 3rd party app like OpenCamera.
Click to expand...
Click to collapse
Does Gcam Works on any Gsi on the SnapDragon variant? No freezing viewfinder?
no gcam working on snapdragon, or i dont find any working for our model.
hunter3000 said:
Please do everything that is written for flashing recovery (Installation), u need to disable encryption and wipe data
Click to expand...
Click to collapse
When disable encryption how safe is the Data stored on the Device?
OptixWolf said:
When disable encryption how safe is the Data stored on the Device?
Click to expand...
Click to collapse
you must disable encryption to boot to non official rom, so you got answer for your question
Master, any solution to this ? "Device is showing as Huawei Nexus 6P need to be changed somehow to our model ", and Call Recording is working on this version ? many thanks for your hard work to G990B version.
This device showing is related to magisk safenet fix for working root with NFC and banking apps but probably also because of GSI rom as is. No call recording as is stock Pixel Experience ROM u need to root and use some magisk module.
Works great on my Samsung s21fe just charging.. sometimes works then other times says it's charging and then does down. Doesn't really go up unless phone is off.
May I know if VoWifi / VoLTE works?