DISCONTINUED
Pls find my last builds ..
https://androidfilehost.com/?w=files&flid=289293
Pls find new PE builds here ..
https://forum.xda-developers.com/pixel-c/development/rom-thread-title-2019-08-25-t3961148
Thanks to @tschmid for taking over PE !
{
"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"
}
PixelExperience
What is this?
Pixel Experience is an AOSP/CAF based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
PixelExperience_dragon-9.0-20190624-1228-UNOFFICIAL.zip
Known issues:
- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.
- Keymaster -> If you set Pattern, PIN or Password the Screen unlock may not work correctly.
Workaround for Pattern: On fresh boot you will need to wait a bit longer before you enter credentials.
The waiting time is required on fresh boot only, the following unlocks are working normally.
In case of problems pls use Update.ZIP_TWRP_flashable_pattern_pin_remover_V2.zip to remove pattern/pin or password.
Installation:
1. Boot into TWRP (latest available version)
2. Wipe system, cache, dalvik and data partitions ! ( If you have encrypted /data partition - pls "format" /data via TWRP first ! )
3. Install ROM.zip
4. install Magisk.zip
5. Reboot into system ..
- The ROM does contain it's own vendor.img !
- This ROM does include Gapps already !
SOURCES:
https://github.com/followmsi/manifests/tree/dragon-pixel-pie
Enjoy
And one more ROM for dragon .. Pixel Experience
Enjoy ..
You have too much time on your hands
Awesome ROM. Was waiting for such a release... Thank you
Sent from my Pixel C using Tapatalk
Amazing thank you for keeping this tablet alive!
Simply awesome. Fantastic job. The best Pixel C custom rom.
Seems like front camera is not working (especially on Google Duo app) any work arounds?
followmsi said:
Known issues:
- Encryption seems not work - and has not been fully tested. -> Pls do not encrypt your data partition yet.
- Screen Unlock: If you set Pattern or Password the Screen unlock does not work correctly.
(Workaround: On fresh boot you will need to wait a bit longer before you enter credentials.)
(The waiting time is required on fresh boot only, the following unlocks are working normally.)
Click to expand...
Click to collapse
Got this installed today and currently using to write this message. I'm confused regarding the known issues though....
I set a PIN as it wasn't specifically mentioned, but I could not login at next reboot at all. Every time I entered the PIN, the screen would refresh back to the PIN login screen. I tried again many times, left it 10 minutes but nothing worked so I had to factory reset from TWRP in order to gain access to the tablet again.
Perhaps I have misinterpreted the known issues?
Only other problems I had was the following:
- Wifi drops off sometimes for no reason, then comes back about 10 seconds later
- Couldn't use default two-factor authentication when logging in with my Google account (i.e.. Press 'Yes' on your phone), I had to use Google Authenticator to generate a code instead. Having said this, after the factory reset, it worked this time.
- Couldn't setup the device first time around as it was unresponsive and slow, a reboot fixed this
- Can't seem to drag apps on my home screens on top of eachother to create folders, whatever I do they always seem move the other app rather than create a new folder.
And for the record, I was stock before this, followed the instructions above (Obviously had to unlock bootloader before installing TWRP for the first time).
Only issue I've seen so far is the normal navigation buttons the recents button is missing
Iggy82 said:
- Can't seem to drag apps on my home screens on top of eachother to create folders, whatever I do they always seem move the other app rather than create a new folder.
Click to expand...
Click to collapse
Wasn't that a bug we all had when we went from Android 7 to 8?
Using another launcher stops it.
m+a+r+k said:
Wasn't that a bug we all had when we went from Android 7 to 8?
Using another launcher stops it.
Click to expand...
Click to collapse
Yeah I also had issues creating a new app shortcut (by dragging an app icon from the list of apps to the home screen). Installed a different launcher and that's those problems dealt with. WiFi seems to be fine now too so could have been a local issue.
All in all, it's great to see Pie on the Pixel C, it deserves it too because the hardware is still outstanding, even in today's market.
Thank you followmsi
Thank you!
Thanks! I'm running it right now!
I have no problem creating folders on the desktop. The way to do it is to approach the icon in the upper left, diagonally. At least that's how it works for me
Iggy82 said:
Got this installed today and currently using to write this message. I'm confused regarding the known issues though....
I set a PIN as it wasn't specifically mentioned, but I could not login at next reboot at all. Every time I entered the PIN, the screen would refresh back to the PIN login screen. I tried again many times, left it 10 minutes but nothing worked so I had to factory reset from TWRP in order to gain access to the tablet again.
Perhaps I have misinterpreted the known issues?
Only other problems I had was the following:
- Wifi drops off sometimes for no reason, then comes back about 10 seconds later
- Couldn't use default two-factor authentication when logging in with my Google account (i.e.. Press 'Yes' on your phone), I had to use Google Authenticator to generate a code instead. Having said this, after the factory reset, it worked this time.
- Couldn't setup the device first time around as it was unresponsive and slow, a reboot fixed this
- Can't seem to drag apps on my home screens on top of eachother to create folders, whatever I do they always seem move the other app rather than create a new folder.
And for the record, I was stock before this, followed the instructions above (Obviously had to unlock bootloader before installing TWRP for the first time).
Click to expand...
Click to collapse
I will add "pin" to known issues on first page too.
Encryption/keymaster is not working correctly on all Pie ROMs.
Roxas598 said:
Only issue I've seen so far is the normal navigation buttons the recents button is missing
Click to expand...
Click to collapse
You can try this method to turn on recent buttons.
adb shell settings put secure sysui_nav_bar "space,recent;home;back,space"
https://www.xda-developers.com/how-...icons-or-re-arrange-the-buttons-without-root/
followmsi said:
- Keymaster -> If you set Pattern, PIN or Password the Screen unlock may not work correctly.
Workaround for Pattern: On fresh boot you will need to wait a bit longer before you enter credentials.
The waiting time is required on fresh boot only, the following unlocks are working normally.[/I]
Click to expand...
Click to collapse
followmsi - Just to clarify (before I go locking myself out completely!) - If I set a pattern unlock (NOT Pin or Password), I will be able to unlock my device properly after waiting a while??
Iggy82 said:
followmsi - Just to clarify (before I go locking myself out completely!) - If I set a pattern unlock (NOT Pin or Password), I will be able to unlock my device properly after waiting a while??
Click to expand...
Click to collapse
For me it works like this .. waiting a bit longer before first pattern unlock.
Otherwise.. have a look here.
https://forum.xda-developers.com/showpost.php?p=78786907&postcount=992
Thanks for the prompt responses. One more question which I'm yet to solve regarding the 30 second bootloader unlocked wait during boot.
I've heard that if I relock the bootloader, the device will lose root and wipe itself. I don't mind a wipe, nor do I use root. So if I were to relock the bootloader, would it still boot up OK into this current ROM? Others have said it could brick the device!.....?
Thanks for this great ROM! I've been waiting for a proper Pie ROM for a long time!
I got no issues with the PIN. Got a 8 numbers PIN and it works great.
Only issue I have is the folder thing but it does not matter as I got not much apps on my tablet!
I got an issue with a notification telling me that the setup was not finished and tapping on it brought a "OK" button and a white page... Tapping OK would get rid of the notification but it would eventually come back a couple minutes later. A reboot solved this issue.
camera not working at all ...
First of all: Thank you so much!!!
wonderful ROM.
Just: the camera is not working.
Any ideas / experiences with that?
costlyman seems to have the same problem.
EDIT: working now after a few restarts - and I don't know.
Thank you in advance.
Related
Hello All,
Here is a stock repackaged firmware to be used if you enabled SDE like described here.
To install it:
1) Extract zip file content
2) Copy rooted_withsu.squashfs.secure to internal storage root. You can do it the usual way or with adb with this:
adb push rooted_withsu.squashfs.secure /data/media
3) Reboot
4) On boot menu, select "Recovery system"
5) Select "developer edition menu"/"flash kernel and initramfs"
6) A drive should appear on your PC, copy zImage and initramfs.cpio.gz to it.
7) Select OK, the kernel should flash.
8) Select OK to reboot.
9) Select SDE in boot menu, you should be rooted and SuperUser functional.
Download firmware here.
And let me know if it worked for you,
LeTama
* reserved *
It is ok
http://www.jbmm.fr/?p=23638
{
"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"
}
All working for me too. Good work people
How do you get to "developer edition menu"/"flash kernel and initramfs"
Currently if I press and hold power / volume down to boot I get 3 options. Android, Developer Edition and Recovery System. If I select Developer Edition and press the power button it comes up with Booting Developer Edition and then appears to reboot this then loads standard android.
Can I just check that im doing this correctly?
Thanks
---------- Post added at 09:27 AM ---------- Previous post was at 09:25 AM ----------
Lol. Im a dumbass... Recovery menu then developer edition menu.
My bad, as I don't have the boot menu, I didn't write proper description:
On boot menu, select "Recovery System" then you'll see a menu with the "developer edition menu" entry. First post modified to reflect that.
All done . If I boot developer edition I have root, If I boot standard I dont - Thank you very much
One thing I note is that superuser apk doesnt retain its memory after a reboot.
So far i have just tried a couple of tools that reboot / shut down your archos (as for me thats all im desperate for doing as im installing the device into my cars dash and have no access to the button). Reboot and Shutdown works fine, but if you ask for the bootloader it seems to mess up - will look at writing something fresh anyway as all I really need is the ability to send it to sleep on ac power disconnect
hotrodder said:
All done . If I boot developer edition I have root, If I boot standard I dont - Thank you very much
One thing I note is that superuser apk doesnt retain its memory after a reboot.
So far i have just tried a couple of tools that reboot / shut down your archos (as for me thats all im desperate for doing as im installing the device into my cars dash and have no access to the button). Reboot and Shutdown works fine, but if you ask for the bootloader it seems to mess up - will look at writing something fresh anyway as all I really need is the ability to send it to sleep on ac power disconnect
Click to expand...
Click to collapse
Thanks for the feedback, I'll check the superuser problem.
You know about the reboot_into command, right ?
syntax: reboot_into sde|android|recovery
letama said:
Thanks for the feedback, I'll check the superuser problem.
Click to expand...
Click to collapse
Ok, I believe I know why you loose settings: If you reboot into "regular" android (ie, without root), android detects that the superuser application was removed from the firmware and removes associated data. I'm not sure I can do anything about this, don't boot into regular android is probably the best advice I could give
After all, no need to go there anymore.
Wow, thats a real help many many thanks. If i call reboot_into -s sde post booting then it should always boot back into sde even if it boots off due to battery power yeah?
I know im a bit of a noob when it comes to android (been a windows coder for a while).
There isnt a way to put the device into "deep sleep" using the command line is there? Basically the whole aim of rooting this device for me is to make it so I can either put it to sleep or power down when external power is removed. I should now be able to shut it down, but id like to make it "sleep" instead if possible as that will come to life a lot faster. The aim being that i will add external power when i flick the key in my car (waking the device up), and then when i switch off it will lose power and be put into sleep mode. If the battery dies then it will recharge when i flick the key again and do a full boot anyway - which i should be able to force into sde as above.
hotrodder said:
Wow, thats a real help many many thanks. If i call reboot_into -s sde post booting then it should always boot back into sde even if it boots off due to battery power yeah?
Click to expand...
Click to collapse
Yes, correct.
hotrodder said:
There isnt a way to put the device into "deep sleep" using the command line is there? Basically the whole aim of rooting this device for me is to make it so I can either put it to sleep or power down when external power is removed. I should now be able to shut it down, but id like to make it "sleep" instead if possible as that will come to life a lot faster. The aim being that i will add external power when i flick the key in my car (waking the device up), and then when i switch off it will lose power and be put into sleep mode. If the battery dies then it will recharge when i flick the key again and do a full boot anyway - which i should be able to force into sde as above.
Click to expand...
Click to collapse
Well, I didn't check power management much in these new kernels, but first, I'm not sure I understood the purpose of this. What differs from the normal power management ? I would do this: "Screen/Timeout 15 seconds" (to power down quickly), and "Application/Development/Stay Awake" (To keep screen up while power is on) ? You add on top "About tablet/Power Management/Deep sleep" for better sleep and you're good ?
Thats what I do currently, but there are times that it doesnt go to sleep. I will be using as a media player, and if you have music playing the screen will go off but leave the music playing which will stop it from powering down, although i can probably kill any running apps on power off. Also I use the full size USB slot on the back to connect a laptop hard drive - and ive noticed that it seems to wake the device up when you just turn off the screen, but doesnt if you hit the power button and tell the device to sleep. Ive played with settings related to the USB port but no luck so far with that one. Sorry for hijacking the thread though - i got a bit off topic.
hotrodder said:
Thats what I do currently, but there are times that it doesnt go to sleep. I will be using as a media player, and if you have music playing the screen will go off but leave the music playing which will stop it from powering down, although i can probably kill any running apps on power off. Also I use the full size USB slot on the back to connect a laptop hard drive - and ive noticed that it seems to wake the device up when you just turn off the screen, but doesnt if you hit the power button and tell the device to sleep. Ive played with settings related to the USB port but no luck so far with that one. Sorry for hijacking the thread though - i got a bit off topic.
Click to expand...
Click to collapse
I see. I'm not a power management expert, so maybe someone could give you better advice.
One other lead I could give you: do you know /sys/power/wait_for_fb_sleep ?
This one is nice, a cat on it will be blocked until the screen goes off. It doesn't solve your usb drive problem, but you could use it if you need to be notified that screen goes off.
I'll take a look at kernel source code to see if I can find something.
thanks lekama so much
after step 8) Select OK to reboot. after reboot, it boot normally and i didn't saw any SDE in boot menu to choose it. plz help ^^.
---------- Post added at 07:39 AM ---------- Previous post was at 07:14 AM ----------
yeah, i choosẽn "developer edition menu" and it boot into rooted,
thanks again for ur good worked ^^ kaka
works on my 80 G9 here, thanks!
is there any way to mount /system rw? i want to push a patched wpa_supplicant for enabling adhoc-support..
i'm installed Chainfire3D to play games, but it's not enough space to install driver, and i can't remove system apps, i think this isn't really rooted ...^^..
a1Pha said:
works on my 80 G9 here, thanks!
is there any way to mount /system rw? i want to push a patched wpa_supplicant for enabling adhoc-support..
Click to expand...
Click to collapse
Not with this firmware, this is pure stock with exactly the same way of of mounting system from a read-only squashfs.
You have two solutions, repackage your own squashfs or modify the initrd to mount an ext4 image for instance.
conmeo8ya said:
i'm installed Chainfire3D to play games, but it's not enough space to install driver, and i can't remove system apps, i think this isn't really rooted ...^^..
Click to expand...
Click to collapse
It is rooted. You can run any rooted application with it.
However, as I explained above, this firmware is pure stock with the same squashfs method meaning read-only /system. It's more like a proof of concept that SDE works properly.
I don't have much time to maintain builds and I'd prefer someone else to come up with one, but if nobody does, I'll do one running on r/w ext4 image.
Thanks. Is there any known way to bypass the 256 byte Archos security signature?
//Edit: In the squashfs, I mean.
a1Pha said:
Thanks. Is there any known way to bypass the 256 byte Archos security signature?
//Edit: In the squashfs, I mean.
Click to expand...
Click to collapse
losetup -o 256 /dev/loopx img.secure and mount
or dd if=img.squashfs.secure of=img.squashfs bs=256 skip=1 and unsquashfs
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.
Hi, I'm having some problems with flashing back to MIUI Rom.
Here is my situation:
I flashed a while ago to Xiaomi.EU rom.
Everything was working pretty well but I missed the "google-way" so I decided to try the PixelExperience Rom.
I did a full wipe for installing this rom. Was pretty satisfied but suddenly the wifi stopped working.
Also the performance in games was not that good.
Next i have done a full wipe again & installed the xiaomi.eu rom.
But when I enter the installation screens of the rom Miui will notify that my device is locked.
I need to enter my mi account password but it cannot verify it because I have no internet connection on my sim (I can't enter pin-code).
I can search for wifi networks, but the screen doens't give me a keyboard to enter the wifi password.
The screens says that I can unlock my device with i.mi.com (Mi cloud).
I tried a lot of things, deleting my 'phone', turned off find device but nothing is helping.
Next i'll tried the official global dev rom. Same problems!
Is there any way to get it unlocked by a god damn webinterface?!
I'm now back at PixelExperience with a few bugs.
Not my picture but this is simular, I also get a button to connect with WIFI but can't enter password...
{
"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"
}
You can try older Xiaomi eu rom, wait for awhile for the keyboard to pop up.
JeffreyM said:
Hi, I'm having some problems with flashing back to MIUI Rom.
Here is my situation:
I flashed a while ago to Xiaomi.EU rom.
Everything was working pretty well but I missed the "google-way" so I decided to try the PixelExperience Rom.
I did a full wipe for installing this rom. Was pretty satisfied but suddenly the wifi stopped working.
Also the performance in games was not that good.
Next i have done a full wipe again & installed the xiaomi.eu rom.
But when I enter the installation screens of the rom Miui will notify that my device is locked.
I need to enter my mi account password but it cannot verify it because I have no internet connection on my sim (I can't enter pin-code).
I can search for wifi networks, but the screen doens't give me a keyboard to enter the wifi password.
The screens says that I can unlock my device with i.mi.com (Mi cloud).
I tried a lot of things, deleting my 'phone', turned off find device but nothing is helping.
Next i'll tried the official global dev rom. Same problems!
Is there any way to get it unlocked by a god damn webinterface?!
I'm now back at PixelExperience with a few bugs.
Not my picture but this is simular, I also get a button to connect with WIFI but can't enter password...
Click to expand...
Click to collapse
I fixed this problem...
I downloaded the Official China Stable fastboot version of my phone (Mi 6).
I flashed this with MiFlash.
First boot... No device is locked!
I installed the phone quickly because it was a chinese bloatware rom.
Next I flashed twrp in fastboot mode.
Booted in TWRP, Format data & copy the Xiaomi.EU version to internal storage.
After installing this rom in TWRP it booted with "Device is locked..." FUUUUUUUUUUUU
But now I was able to fill in the wifi password!
With a wifi connection you just have to type your password of your Mi account and all problems are gone!
Simple solution
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected
Something similar happened to me, from one moment to another the Wi-Fi worked, I did a full reset and when I turned it on again the device gave me it was blocked, the button opened the button and told me to enter my password I did, but it turns out that never validate apparently still with the problem of wifi, suggestion?
Enter wifi routers admin page (192.168.0.1) or similar like this. Delete wifi's password and bum ! You can connect wifi without buttons.
Thanks Bud
Myst3t said:
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected
Click to expand...
Click to collapse
I was having the same problem, your sugession solved it. you are a damn genius buddy :laugh::laugh:
Myst3t said:
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected
Click to expand...
Click to collapse
This is the easiest way to solve the problem. They should fix that problem soon. It has no sense.
Myst3t said:
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected
Click to expand...
Click to collapse
f**** genious
Myst3t said:
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected
Click to expand...
Click to collapse
This was just amazing...
Thanks!
Myst3t said:
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected
Click to expand...
Click to collapse
fu*king genius! You saved my life!
But still I'm curious why I had this situation. I tried to install twrp, after success fastboot flashing I rebooted my phone a Mi-recovery 3.0 appeared. So no install any kind of zip. So reboot again and this "device is locked" showed up!
Any opinions?
Myst3t said:
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected
Click to expand...
Click to collapse
genius! thank you
i once flashed from global dev from to china dev rom.. it asked me to sign in my MI account. i typed the correct password but it still would not accept.. so i sign in micloud on PC does not work too so i decided to change the password to try again~ no luck. flashed back to miui global dev it asked to sign in too.. and then it says INVALID USER ID.. well done xiaomi~ now im locked out forever until i can provide proof of purchase to them to unlock my phone from the server. anyone has ever fix this pls help me i need to flash to stock rom and sell the phone LMAO
Hi ppl. I have similar problem with my Redmi 5 Plus phone. I used the phone one day, I activated Mi account, I made transfer data from my old Mi 3, I unlocked bootloader succesiful, and then I installed MIUI 10 (developer version). After phone is booted I got screen with Device is locked. I have full access to my Mi account via web, but when I try to unlock device it says Invalid username! There is my conversation with Xiaomi global support. Then wasn't useful for me I am using custom RR rom, but I want to back to MIUI. What I need to do?
Conversation with Xiaomi support (screenshoots from gmail):
https://www.dropbox.com/sh/utsmwszsenrhld5/AAAMEAUC4sVjR0h_csqDZHPOa?dl=0
Thank you so much, worked well. Tryed to downgrade to miui 9 from miui 10 and got phone lock. Your solution was the best
If you brick your device on the way as it happened to me... check: https://forum.xda-developers.com/showpost.php?p=77755947&postcount=11
These guys helped me unbricking my mi8 using EDL (Test Point) and Mi-flash!
Myst3t said:
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected
Click to expand...
Click to collapse
Beauty in simplicity. Excellent mind there
THE maaaaannnnn!!!
genius...
Best solution on mi MI8. Thanks!!
Myst3t said:
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected
Click to expand...
Click to collapse
you save my life,thank you so much kisses *x
Hey everybody,
I guess I was not the only one being a bit disappointed that google didn´t make adaptive audio available for the Pixel 4 devices as well.
To be honest I personally think it´s a bit of a gimmicky feature that´s not very critical, but making it exclusive to Pixel 5 left a bitter after taste.
Here´s how to enable the feature persistent across reboots on a rooted device:
1. Download the pixel 5 device personalization app from apkmirror and install the app:
https://www.apkmirror.com/apk/google-inc/device-personalization-services/device-personalization-services-r-11-playstore-pixel5-353007393-release/device-personalization-services-r-11-playstore-pixel5-353007393-android-apk-download/
2. Flash the attached magisk module Adaptive_Audio_Settings_Enabler.zip via magisk manager app and do a reboot.
Wait a few minutes after the phone booted successfully and the entry in settings will appear.
Manual command method, doesn´t survive reboots but works on unrooted devices as well:
1. Download the pixel 5 device personalization app from apkmirror and install the app:
Device Personalization Services R.12.playstore.pixel5.357001175 APK Download by Google LLC - APKMirror
www.apkmirror.com
2. Make sure to have USB Debugging enabled via developer options and have a working adb environment. Then connect your phone to pc.
3. Type the following:
Code:
adb shell
4. then type (this step is not needed)
Code:
su
grant superuser permission in the window that opens on your phone.
5. Now paste the following commands:
Code:
device_config put device_personalization_services AdaptiveAudio__enable_adaptive_audio true
Code:
device_config put device_personalization_services AdaptiveAudio__show_promo_notification true
You can enable it now in settings and try the feature for yourself.
A few notes here:
I´m unsure how much profit this feature really gives, even on the Pixel 5. When enabling it on my 4XL the sound gets a bit more bassy.
Judging from the logs it should be working as it is with the steps described above. It might be that it´s tuned towards the Pixel 5, but well... Having options is always nice
The guide with the manual commands works without root, for those that don´t like to run rooted. I was able to disable and enable the feature back again without the need for root. Maybe some apps can execute scripts without root on the phone so it will stay across reboots. Somebody else has to figure this out though.
Have fun with it
{
"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"
}
Reserved
Wow, would you also happen to know how to enable night sight portrait mode on P4?
Thanks m8, you are a legend.
Works great on my 4XL stock, no root.
I followed the guide without the "su" part on adb shell
Thank you for the tip, but whenever I reboot the phone it will not stick, I'm currently rooted.
Zilla0617 said:
Thank you for the tip, but whenever I reboot the phone it will not stick, I'm currently rooted.
Click to expand...
Click to collapse
You´re correct. I didn´t notice it, because it takes a short while for the setting to disappear after rebooting.
I made a magisk module, that passes the command every boot after a timeout. Magisk required obviously
Freak07 said:
You´re correct. I didn´t notice it, because it takes a short while for the setting to disappear after rebooting.
I made a magisk module, that passes the command every boot after a timeout. Magisk required obviously
Click to expand...
Click to collapse
After installing the module, I added the commands using adb shell but adaptive sound still does not persist after a reboot.
Zilla0617 said:
After installing the module, I added the commands using adb shell but adaptive sound still does not persist after a reboot.
Click to expand...
Click to collapse
Flash the module in magisk manager, reboot, wait a few minutes and the entry should pop up. It needs a few minutes. There’s no need for any manual commands with the module.
Freak07 said:
Flash the module in magisk manager, reboot, wait a few minutes and the entry should pop up. It needs a few minutes. There’s no need for any manual commands with the module.
Click to expand...
Click to collapse
It's working. Thank you
Working like a charm thank you mate.
how i do adb Do you have an example please?
How do I get back to the original device personalization service app?
oraned said:
how i do adb Do you have an example please?
Click to expand...
Click to collapse
There are plenty of guides on xda on how to setup adb.
How to install ADB on Windows, macOS, and Linux
If you're on Windows, Linux or macOS, you can follow these step by step instructions to install ADB on your desktop or laptop PC.
www.xda-developers.com
If you are rooted with magisk and unfamiliar with command line, there's also the magisk module.
tifone said:
How do I get back to the original device personalization service app?
Click to expand...
Click to collapse
Open it in play store and hit uninstall. Then update again and it will install the latest one for pixel 4.
https://play.google.com/store/apps/details?id=com.google.android.as
Open this link when viewing xda via browser on your phone.
I am sorry telling you that my friend but I am rooted and did yesterday the process and everything was ok, after some seconds as you said the adaptive sound wan in my menu.
Today as I went to check if it was still there, kaboom, disappeared so I uninstalled everything and did it from the beginning, so it can be installed again.
Have an idea why?
Let's go ahead and give this a try. Thanks
Can confirm that it still does work. But after rebooting even with the root method and the module still showing up in magisk adaptive sound vanished in settings. Reinstalling the module makes it appear again and function.
Edit: The feature just vanished without a reboot. Guess Le Googs doesn't wan tus usingit RIP.
The comment above and I are experiencing the same symptoms. When a module is installed, it is initially visible in the configuration, but sometimes it is not present after a period of time. If you reboot each time, it will come back.
However, I wish it could be maintained without rebooting.
tifone said:
The comment above and I are experiencing the same symptoms. When a module is installed, it is initially visible in the configuration, but sometimes it is not present after a period of time. If you reboot each time, it will come back.
However, I wish it could be maintained without rebooting.
Click to expand...
Click to collapse
How long does it persist for you after you reboot?
zetsumeikuro said:
How long does it persist for you after you reboot?
Click to expand...
Click to collapse
That can't be verified. However, sometimes when time passes, it may not be in the setting.
I don't think there's a solution, but thanks for letting me use a service that doesn't support it.
I think I figured out why it sometimes disappears when I check it after some time.
I'm using the dolby digital plus module, but after deleting this module once, I tested to see if it disappears after a while, and the adaptive sound was maintained.
I'm not sure if it's causing a conflict between modules. I also noticed that the two modules run together at first.
Hello,
Just got the tablet, it was really quick. Ordered when it went for sale in Italy on Thursday and today Friday morning already received it.
Maybe I'm one of the first to receive the tablet with Global ROM, but I'm going to ask anyway:
I cannot add my Google account. The error is always "There was a problem communicating with Google servers"
Is this tablet so new that it still cannot connect to Google?! Has anyone had similar problems? I also tried to install last Google Play Services from apkmirror.
ROM is 12.5.1 Global Stable
Thanks!
EDIT: Solved. After trying to clear app data, installing apks, checking autostart permissions etc, decided to try factory reset and everything started working. Kind of crazy that before starting to use a new device had to do factory reset, if you ask me.
what is the version of your firmware? im planning to buy one
same to me. i cannot access with my google account. How do you resolved @tikkalamt? i update also google play services and restore back to factory reset but i don't resolve this issue. miui 12.5.1 global.
Same here. MIUI 12.5.2. Google Account can not be added.
same problem even after two factory reset, a solution please?
Interesting. I have a similar problem yet not the same. I wanted to use the device for my job and we use Microsoft Intune to create an enterprise profile in Android devices.
Outside of this enterprise area everything works fine. I can set up a Google account without problems. But when I open the enterprise PlayStore I see the error message "Error while retrieving information from server DF-DFERH-01".
It sounds like those two problems are in a way related to each other...
I also have MIUI 12.5.2 and up-to-date Play Services...
I had the same problem. I could solve it after factory reset and Android setup ask If you would like transfer files from other phone and vola account transferred.
It is a google server problem. It's a problem known by xiaomi. I turn off wifi, put in airplaine mode. Then wifi on and i don't know why i access with my google account.
Same thing on Second Space.
Using Global ROM in France, everything works great on First Space. Cannot ad a Google account on Second Space. It's a shame since I bought this tablet for two persons. I really hope this will get fix soon.
I tried deleting Google Apps data etc… nothing works.
Mine worked normally come with MIUI 12.5.4.0 RKXMIXM
{
"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"
}
anyone have issues with google backup? can't seem to do any backup, It will only say.
"Couldn't backup data, Try again later"
Tried on other phone works fine, factory resets the device still doesn't work, turning off screen lock and reboot also doesn't work, tried force backup by adb it would say Transport Error.
Kalatana said:
Same thing on Second Space.
Using Global ROM in France, everything works great on First Space. Cannot ad a Google account on Second Space. It's a shame since I bought this tablet for two persons. I really hope this will get fix soon.
I tried deleting Google Apps data etc… nothing works.
Click to expand...
Click to collapse
I have the same problem with the second profile. If you completely reset the pad again, do not add a Google account during the initial setup and then first set up the second account, it should supposedly work. But I haven't tried it myself because I don't want to reset the first profile.
gorodoe said:
anyone have issues with google backup? can't seem to do any backup, It will only say.
"Couldn't backup data, Try again later"
Tried on other phone works fine, factory resets the device still doesn't work, turning off screen lock and reboot also doesn't work, tried force backup by adb it would say Transport Error.
Click to expand...
Click to collapse
Same here.
i also had the same problem after flashing global rom, i solved by clear cache data google service and google play
Kalatana said:
Same thing on Second Space.
Using Global ROM in France, everything works great on First Space. Cannot ad a Google account on Second Space. It's a shame since I bought this tablet for two persons. I really hope this will get fix soon.
I tried deleting Google Apps data etc… nothing works.
Click to expand...
Click to collapse
Same to me with Global rom in Xiaomi mi pad 5 Chinese version! Need an expert give some solutions
Same on EU version. Also receiving notifications that Google Backup is not working
Same with mi mipad 5, unable to login on google account in the second space... Works with my xiaomi smartphone.
Xiaomi support asked me to add a comment directly in the setting section of the device (services and comments section) to try to get a fix... I think other people concerned should do the same to prove xiaomi it is really mandatory to fix this.
Mark0x said:
Same with mi mipad 5, unable to login on google account in the second space... Works with my xiaomi smartphone.
Xiaomi support asked me to add a comment directly in the setting section of the device (services and comments section) to try to get a fix... I think other people concerned should do the same to prove xiaomi it is really mandatory to fix this.
Click to expand...
Click to collapse
I had the same problem, after multiple factory resets (each time I went to second space first, to check out if it is already working with google) I setup my second space first (without adding an account to my "first" space) and it is working ok since than. But unfortunately not all options are available in the second space (for example you cannot add youtube as multitasking app).
I am having similar problem. After unboximg i couldn’t Connect to google server. But after factory reset i was able to add google account.but later when i wanted to add another google account i could not. It goes to lock screen and after swiping up its shows " checkin info.." and it goes on for ever. Another problem is it doesn’t backup in google. I did clear data of playstore and play service several times but no luck. Seems like it is a problem for everyone. They should have polished their software before releasing this tab.
If it can help, after wiping google apps data to try to make this work, I was out of my account even on the first space, even after reboot (with the same error), but by going to the 3 dots "..." -> Updates in the Play Store app, I was able to see the error code "df-dferh-01" which lead me to https://www.nextpit.com/google-play-not-working#uninstall / https://theandroid.in/df-dferh-01/, which mentions uninstalling the google app updates as a solutions, which looked like the situation of @amacar (you can login after a fresh wipe) .. and it worked for me !
So here's what I did (without wipe) :
* Go to Apps, show all
* Google Play Store -> uninstall updates
* Google Play Services -> uninstall updates (after this the app list disappear)
* You can go to the Play store and login
* Repeat for the other space if necessary
Edit: this is also a solution proposed at https://support.google.com/googleplay/answer/7513003
"They should have polished their software before releasing this tab."
Sadly I think this is what to expect, with some issues probably to stay for a long time. I also noticed that some medias in Plex are played with very fast video but normal audio (maybe Plex' fault but I'd bet on some MIUI customization) ..