After years of flashing ROMs I'm happy to see the development for the Poco F2 Pro is finally kicking off. Unfortunately, I seem to be stuck on using them, because of the following.
VoLTE and VoWIFI only work on EU MIUI. When using a Global or Chinese MIUI, I get no callerid when someone calls me (there's just no number showing up, as if everyone is calling anonymously)
All custom ROMs require Global or Chinese MIUI. When using EU MIUI on a custom ROM, the camera doesn't work.
All in all there seems no way to have as well, VoLTE/VoWIFI, as callerid, as a custom ROM. I really like to use VoLTE because of superior call quality and data during calls, but I'd like to try custom ROMs as well. Since I guess custom ROMs will always require a Global/Chinese MIUI, I've been trying to get VoLTE and callerid working on a Global ROM, thusfar unsuccessful.
From what I've read, the only option is to use the "PDC tool", which is part of QPST. I've followed this guide (which is for Poco F1), but can't seem to get a connection from PDC to work due to "QMI connection not ready, please use USB driver version 1.00.32 or later". I've tried some drivers, but none seem to work. Any suggestions would be highly appreciated!
Specs:
- Poco F2 Pro, bought in the Netherlands;
- SIM: Vodafone NL (the Netherlands)
Development just started few weeks ago .. so you just have to wait for custom kernel
jeky82 said:
Development just started few weeks ago .. so you just have to wait for custom kernel
Click to expand...
Click to collapse
I'm afraid the kernel is not the issue here, I guess it's in the EFS (modem config, radio settings, etc) which is not affected by custom ROMs or kernels, only by the basefirmware that you need to flash before flashing anything else.
Could you just clarify what you mean by "using EU MIUI on a custom ROM"?
To the best of my knowledge MIUI isn't something you can flash over an existing custom rom. Either your rom is built around the MIUI framework, or it isn't.
Hello
When make a call with the 4G mode on, the Internet is disconnected. Does this happen to anyone? Also, when turn on the 5g, the second Sim is disconnected
.my rom miui eu weekly 22.10.2020
And Also I cannot connect the phone to the car to hear music, either Bluetooth or Aux
Gratefully
Or maybe some dev will start rom builds based on eu miui ver...
melkorashe said:
Hello
When make a call with the 4G mode on, the Internet is disconnected. Does this happen to anyone? Also, when turn on the 5g, the second Sim is disconnected
.my rom miui eu weekly 22.10.2020
And Also I cannot connect the phone to the car to hear music, either Bluetooth or Aux
Gratefully
Click to expand...
Click to collapse
Enable volte
Curunir said:
Could you just clarify what you mean by "using EU MIUI on a custom ROM"?
To the best of my knowledge MIUI isn't something you can flash over an existing custom rom. Either your rom is built around the MIUI framework, or it isn't.
Click to expand...
Click to collapse
All custom ROMs require a MIUI base; probably because that particular MIUI installs configs/drivers that the custom ROM uses.
K-Paradise said:
From what I've read, the only option is to use the "PDC tool", which is part of QPST. I've followed this guide (which is for Poco F1), but can't seem to get a connection from PDC to work due to "QMI connection not ready, please use USB driver version 1.00.32 or later". I've tried some drivers, but none seem to work. Any suggestions would be highly appreciated!
Click to expand...
Click to collapse
Did you set your device into the Qualcomm diag mode?
su
setprop persist.sys.usb.config diag,serial_cdev,rmnet,adb
setprop sys.usb.state diag,serial_cdev,rmnet,adb
setprop sys.usb.config diag,serial_cdev,rmnet,adb
PDC works here when I do that
K-Paradise said:
All custom ROMs require a MIUI base; probably because that particular MIUI installs configs/drivers that the custom ROM uses.
Click to expand...
Click to collapse
Ahh I understand, you mean the firmware image .
Cave_diver said:
Did you set your device into the Qualcomm diag mode?
su
setprop persist.sys.usb.config diag,serial_cdev,rmnet,adb
setprop sys.usb.state diag,serial_cdev,rmnet,adb
setprop sys.usb.config diag,serial_cdev,rmnet,adb
PDC works here when I do that
Click to expand...
Click to collapse
Thanks for this, unfortunately I get the same error. Which driver did you use?
K-Paradise said:
Thanks for this, unfortunately I get the same error. Which driver did you use?
Click to expand...
Click to collapse
I'm using qualcomm drivers and for adb I'm using the original xiaomi drivers that are linked on the Google site.
Related
I am currently facing a very weird(to me at-least) problem that seems to be exclusive to me, since I cant find similar posts on any forums.
The network of both the sim cards on my phone are continuously being reset- as if I was continuously enabling and disabling airplane mode, but the Wi-Fi, bluetooth and everything else is fine.
I'm using a network carrier called Jio, and have been getting horrible speeds for quite some time now. Today I noticed that whenever I was connected to someone on a call, my internet speeds were exponentially higher(2 mbps - 12 mbps), which seemed strange and after a little research, was revealed to be the cause of my LTE band being locked on band 3 whenever I was on a call.
So I started looking for a way to make that band lock permanent, in hopes of getting good speeds. I found about these two tools called QPST and QXDM which are supposedly have very broad uses like resetting IMEI etc, which I have no knowledge of how to do.
I was stupid enough to not properly read any documentation or proper guides of how these tools are used. I just saw in some articles and videos that QXDM can also be used to directly change the value of the variable that holds the code of what 4g band is being used, so I tried changing that.
Here's the steps I performed:
Looked for and installed the correct Qualcomm diagnostic mode drivers for my phone(adb and fastboot were already installed).
enabled DM using adb.( su -> setprop sys.usb.config diag,adb in an adb shell)
Started QPST and QXDM in that order.
Selected the LTE values in NV Browser of QXDM and tried to modify those to the codes corresponding to the band I wanted to lock to(band 5 that has code 16).
I read the default value, copied it, then wrote required value and clicked on "Write" which failed giving the error : "DIAG error received: Invalid Command Error Response"
After this the aforementioned problem started, and I tried restarting the phone first, which sent it into a bootloop.
I fixed the bootloop by clean flashing my current rom(without formatting the storage).
But the problem is still there.
I was using an app to monitor what band is currently being used. Even the app is not working anymore, it says that drivers are not properly installed.
I am also unable to access any network related settings in my rom settings.
My RN7 is a violet.
I am currently on Pixel Experience 10, latest build.
With the latest miui firmware installed.
Orange fox recovery.
I guess I shouldn't have messed with things I have no idea about, specially without proper research, but I am really clueless now about what might be causing the problem and how, if at all, I could fix it, I thought of a complete re-flash of stock MIUI using mi flash tool, but not sure if it would help or not.
Any help will be much appreciated!
First of all, you shouldn't have used these tools if root was available as there is an app called Network Signal Guru. Now this app requires root and u can easily lock any of the band you want.
Now if you are facing any problem i recommend a clean install of fastboot rom. With formatting data and storage so none of the problem remains. I guess there is a problem being faced by many though i didn't checked myself about sensors not working on stock rom after pixel exp. Rom but some says flashing miui10 via mi flash and then updating it to miui11 via recovery the sensors strt working.
You need to check for that but if you want to go back to pixel rom then its fine.
To lock bands remember to use this app. It works fine.
Moreover flashing the rom may remove the problem you were facing of signal but i guess it was only due to phone changing bands.
Network signal guru doesn't work with Custom Roms.
gursewak.10 said:
First of all, you shouldn't have used these tools if root was available as there is an app called Network Signal Guru. Now this app requires root and u can easily lock any of the band you want.
Now if you are facing any problem i recommend a clean install of fastboot rom. With formatting data and storage so none of the problem remains. I guess there is a problem being faced by many though i didn't checked myself about sensors not working on stock rom after pixel exp. Rom but some says flashing miui10 via mi flash and then updating it to miui11 via recovery the sensors strt working.
You need to check for that but if you want to go back to pixel rom then its fine.
To lock bands remember to use this app. It works fine.
Moreover flashing the rom may remove the problem you were facing of signal but i guess it was only due to phone changing bands.
Click to expand...
Click to collapse
Thanks for the reply, though I agree I shouldn't have tried using things that I don't fully understand.
I did use the app that you mentioned and it did not work, after which I tried this method.
I just clean flashed the miui11 through fastboot using mi Flash tool and it's fixed now, thanks!
Redmi note 7 pro mobile data dropping
Hello,
Sorry for introducing a new issue(as a new and inexperienced member hoping for solution) related to the mobile data problems on redmi note 7 pro.
I have the phone since a month and the network data was working perfectly fine and since several days the internet via mobile data drops every 5 minutes. I have to reboot the phone or turn off/on mobile data several times.
I contacted my internet provider and all is correct from their side and they even gave me a new sim card that i tested on my galaxy m20 and it works fine.
I was looking for solutions on forums but it didn't help and i turn around here hoping to find solutions on my issue.
Thanks
long story short im trying to flash a GSI on my infinix zero 8. It has a dynamic super partition. Ive heard people mention that you need to boot fastboot to get into fastbootd mode, which works. but it doesnt let me do anything in fastbootd. my pc doesnt recognise my phone in fastbootd and only in fastbootd mode. how could i go about solving this?
kusti420 said:
long story short im trying to flash a GSI on my infinix zero 8. It has a dynamic super partition. Ive heard people mention that you need to boot fastboot to get into fastbootd mode, which works. but it doesnt let me do anything in fastbootd. my pc doesnt recognise my phone in fastbootd and only in fastbootd mode. how could i go about solving this?
Click to expand...
Click to collapse
Are your drivers installed?
fastbootd is the counterpart - located on Android device - of fastboot tool installed on computer. A fastbootd mode doesn't exist: only fastboot mode ( AKA bootloader or download ).
Tab E said:
Are your drivers installed?
Click to expand...
Click to collapse
yes obviously, literally everything else works be it MTP, fastboot, adb, edl or whatever, only in fastbootd is it not recognised
Tab E said:
Are your drivers installed?
Click to expand...
Click to collapse
and im also running platform tools 31.0.0 not some outdated version
kusti420 said:
and im also running platform tools 31.0.0 not some outdated version
Click to expand...
Click to collapse
as your using a mediatek phone, try using sp flash tool and format the preloader and reinstall that
It's a litte risky, so be careful. I've had the same issue on my mt6795 and restoring the preloader fixed it.
Tab E said:
Are your drivers installed?
Click to expand...
Click to collapse
nvm reinstalling drivers fixed it
kusti420 said:
long story short im trying to flash a GSI on my infinix zero 8. It has a dynamic super partition. Ive heard people mention that you need to boot fastboot to get into fastbootd mode, which works. but it doesnt let me do anything in fastbootd. my pc doesnt recognise my phone in fastbootd and only in fastbootd mode. how could i go about solving this?
Click to expand...
Click to collapse
have you successfully installed a GSI image on infinix zero 8? If so, what is the rom? I intend to install a GSI on mine too, if possible one already based on android 11...
lrdslr said:
have you successfully installed a GSI image on infinix zero 8? If so, what is the rom? I intend to install a GSI on mine too, if possible one already based on android 11..
Click to expand...
Click to collapse
yes i sucessfully installed many GSIs on it, such as bless, caos, crrom, dot os, havoc, lineage and a few others idk about android 11 but im running resurrection remix 8.6.4 rn, there are a few problems with gsis ive noticed, they cant be rooted by just patching magisk on the boot.img, also on some GSIs even on that RR build ADB isnt working and worst of all, i have no clue why but i cant use wired headphones with these GSIs, the audio just wont go through the cable.
i mean you can experiment with different roms. but pls let me know if youre experiencing the same problem where you cant use wired headphones, thats a huge bummer for me as i just bought a new pair of earphones to use with this phone just to find out i cant use them xd
lrdslr said:
have you successfully installed a GSI image on infinix zero 8? If so, what is the rom? I intend to install a GSI on mine too, if possible one already based on android 11...
Click to expand...
Click to collapse
also idk if you noticed i also made a post about how i flashed a gsi on it, in case youre interested
kusti420 said:
yes i sucessfully installed many GSIs on it, such as bless, caos, crrom, dot os, havoc, lineage and a few others idk about android 11 but im running resurrection remix 8.6.4 rn, there are a few problems with gsis ive noticed, they cant be rooted by just patching magisk on the boot.img, also on some GSIs even on that RR build ADB isnt working and worst of all, i have no clue why but i cant use wired headphones with these GSIs, the audio just wont go through the cable.
i mean you can experiment with different roms. but pls let me know if youre experiencing the same problem where you cant use wired headphones, thats a huge bummer for me as i just bought a new pair of earphones to use with this phone just to find out i cant use them xd
Click to expand...
Click to collapse
not able to root through magisk is a big problem for me, as I use many bank apps... But this problem still affects many devices running GSI images, not just infinix zero 8. if the wired headphones really don't work, it's another big problem... the rest work well? gps, cameras, wifi, bt, sim card, volte, sensors, etc?
I haven't received my zero8 yet, but I think it won't be long. I found your post about flash of GSI images on devices with dynamic partition (super), when arrive I will do the test and notice...
lrdslr said:
not able to root through magisk is a big problem for me, as I use many bank apps... But this problem still affects many devices running GSI images, not just infinix zero 8. if the wired headphones really don't work, it's another big problem... the rest work well? gps, cameras, wifi, bt, sim card, volte, sensors, etc?
Click to expand...
Click to collapse
yes, i havent seen any problems with the rest of these sensors and stuff, and even the bank apps work unlike back in the days where if you had a custom rom you couldnt use mobile-id. using wireless internet on gsi works even better than stock rom (xos), atleast for me, cause in xos it didnt choose the correct settings for setting up a 4g connection by default, but it worked perfectly on GSI, just pop in a sim card and off you go, at least thats how my experience was with it.
kusti420 said:
yes, i havent seen any problems with the rest of these sensors and stuff, and even the bank apps work unlike back in the days where if you had a custom rom you couldnt use mobile-id. using wireless internet on gsi works even better than stock rom (xos), atleast for me, cause in xos it didnt choose the correct settings for setting up a 4g connection by default, but it worked perfectly on GSI, just pop in a sim card and off you go, at least thats how my experience was with it.
Click to expand...
Click to collapse
Normal magisk won't work on GSI based on PHH
Magisk-v20.4-phh-aonly.zip | by younes_bfd for Galaxy J6
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Use this magisk
Tab E said:
Normal magisk won't work on GSI based on PHH
Magisk-v20.4-phh-aonly.zip | by younes_bfd for Galaxy J6
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Use this magisk
Click to expand...
Click to collapse
we know, but there isnt twrp for infinix zero 8 or any other custom rom to my knowledge, so there is no way of flashing it, doesnt work through adb sideload or fastboot
lrdslr said:
not able to root through magisk is a big problem for me, as I use many bank apps... But this problem still affects many devices running GSI images, not just infinix zero 8. if the wired headphones really don't work, it's another big problem... the rest work well? gps, cameras, wifi, bt, sim card, volte, sensors, etc?
I haven't received my zero8 yet, but I think it won't be long. I found your post about flash of GSI images on devices with dynamic partition (super), when arrive I will do the test and notice...
Click to expand...
Click to collapse
[AOSP 10.0] [Qualcomm] Q vendor: no analog audio output (passive usb-c, or 3.5mm jack) · Issue #855 · phhusson/treble_experimentations
When plugging in usb-c, this error appears: E/APM::HwModule(1123): createDevice: could not find HW module for device 0004 address After initial investigation, Q vendor's audio policy (attached) doe...
github.com
Google Issue Tracker
issuetracker.google.com
it seems to me like im not the only one with that issue
lrdslr said:
not able to root through magisk is a big problem for me, as I use many bank apps... But this problem still affects many devices running GSI images, not just infinix zero 8. if the wired headphones really don't work, it's another big problem... the rest work well? gps, cameras, wifi, bt, sim card, volte, sensors, etc?
I haven't received my zero8 yet, but I think it won't be long. I found your post about flash of GSI images on devices with dynamic partition (super), when arrive I will do the test and notice...
Click to expand...
Click to collapse
solved the adb problem by flashing this:
[ROM] [Treble] Ressurection Remix 8.6.7 Android Q
Welcome to Ressurection Remix Android Q 10.0 For Galaxy A30 [ROM] [Treble] RROS Android 10 Q Samsung Vendor Compatible Quote: Warning : Me nor XDA Are responsible for any damage that might be caused after...
forum.xda-developers.com
edit:
nvm dont install it sim doesnt work for me on this
roms - Google Drive
drive.google.com
This ROM is built using binaries from non-european (TEE) version of Jelly 2. Theoretically it should work on european (EEA). If it won't - contact me, I'll prepare ROW based on EEA binaries.
ROM can be installed via TWRP. How to install TWRP - https://forum.xda-developers.com/t/recovery-twrp-3-5-2-unihertz-jelly-2.4281493/
Source code - https://github.com/Meetoul/android_device_Unihertz_Jelly2
UPD. Experimental version of Lineage OS 18.1 (Android 11) is also available by the attached GDrive link.
Hi, would you be willing to share the source repo and build instructions? Thanks!
lakkimsetty.baba said:
Hi, would you be willing to share the source repo and build instructions? Thanks!
Click to expand...
Click to collapse
Here you go https://github.com/Meetoul/android_device_Unihertz_Jelly2
Meetoul said:
roms - Google Drive
drive.google.com
This ROM is built using binaries from non-european (TEE) version of Jelly 2. Theoretically it should work on european (EEA). If it won't - contact me, I'll prepare ROW based on EEA binaries.
ROM can be installed via TWRP. How to install TWRP - https://forum.xda-developers.com/t/recovery-twrp-3-5-2-unihertz-jelly-2.4281493/
Source code - https://github.com/Meetoul/android_device_Unihertz_Jelly2
Click to expand...
Click to collapse
Thanks for developing the room
But unfortunately it does not work
After burning in twrp it constantly makes a boot loop
I tried several times
I'll be happy if you can fix that
(Sorry for my obscure language, I use translation,)
Gon112 said:
Thanks for developing the room
But unfortunately it does not work
After burning in twrp it constantly makes a boot loop
I tried several times
I'll be happy if you can fix that
(Sorry for my obscure language, I use translation,)
Click to expand...
Click to collapse
Hi!
What version of Jelly2 do you have? TEE, EEA, JP?
Meetoul said:
Hi!
What version of Jelly2 do you have? TEE, EEA, JP?
Click to expand...
Click to collapse
NONE EEA
Gon112 said:
NONE EEA
Click to expand...
Click to collapse
Sorry, I cannot understand you.
Please put a number that corresponds to the yours Jelly2 version
TEE
EEA
JP
1
Meetoul said:
Sorry, I cannot understand you.
Please put a number that corresponds to the yours Jelly2 version
TEE
EEA
JP
Click to expand...
Click to collapse
1
Gon112 said:
1
Click to expand...
Click to collapse
The ROM is already built on top of the latest TEE binaries and it works on my Jelly2...
Probably, you have faced some issues during flashing the ROM. Please flash your Jelly2 back to stock ROM using SP Flash Tool and try again.
I have been using this ROM for couple of weeks now, it seems solid - didn't crash or had any issues.
The battery life however is very bad. I am using Magisk ACC module to limit the charge to 70% and it dropped from 70% to 34~37% within 8-ish hours (while I am asleep) consistently with all radios off (with regular cell network on for calls and texts, LTE off). The stock ROM used to drop at most 3% while I am asleep.
I think the stock ROM has aggressive app kill/ background process limit. I am going to try with those options enabled (in developer options) to see if there's going to be an improvement.
If anyone had issues like the above and has a conf, do let me know, thanks!
Edit: Forgot to mention that I also use AccuBattery and Greenify. Greenify is set to kill all user apps except for Magisk and AccuBattery.
I have the EU Version of Jelly 2, and yet it seems to work fine
Thank you very much for your efforts.
If i find any bugs ill report them
beck.hannes said:
I have the EU Version of Jelly 2, and yet it seems to work fine
Thank you very much for your efforts.
If i find any bugs ill report them
Click to expand...
Click to collapse
Thank you for your feedback. Probably, I won't fix the bugs in LOS 17.1, cause now I'm working on LOS 18.1 (based on Android 11) .
You can try it by this link https://drive.google.com/file/d/1kG8ebEf-GZW_AZ_d42HuxHHmHv0sQDl5/view?usp=sharing
Please note that I'm trying to keep this ROM as clean as possible, so currently it does not contain any proprietary Mediatek or Unihertz binaries (except vendor image, of course ). It means, that ROM does not include FM Radio or IMS. AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
What's tested and working:
Voice Call
SMS
WiFi
Bluetooth
Wired headset
NFC (it reads and emulates tags, GPay doesn't work because of SafetyNet, but I think I can bypass it)
IR remote control (I tested with ZaZa remote software)
Meetoul said:
Thank you for your feedback. Probably, I won't fix the bugs in LOS 17.1, cause now I'm working on LOS 18.1 (based on Android 11) .
You can try it by this link https://drive.google.com/file/d/1kG8ebEf-GZW_AZ_d42HuxHHmHv0sQDl5/view?usp=sharing
Please note that I'm trying to keep this ROM as clean as possible, so currently it does not contain any proprietary Mediatek or Unihertz binaries (except vendor image, of course ). It means, that ROM does not include FM Radio or IMS. AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
What's tested and working:
Voice Call
SMS
WiFi
Bluetooth
Wired headset
NFC (it reads and emulates tags, GPay doesn't work because of SafetyNet, but I think I can bypass it)
IR remote control (I tested with ZaZa remote software)
Click to expand...
Click to collapse
Hi
How many times have I tried to install LOS 17.1 it did not work,
Now I have tried to install LOS 18.1 and it works fine and perfect
Thanks!!
I'll be happy if you can add support for things you mentioned that are not currently supported,
Thank you good man.
Meetoul said:
AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
Click to expand...
Click to collapse
Would it help for you to have someone test VoLTE (and possibly WiFi calling?)
I'm considering picking one of these up and was just assesing what the community is behind it for custom ROMs. I had the original Jelly and the ROM community for that was very limited, and I was in over my head when trying to build it for myself. I would be glad to help however if you think you'll be using the device for a while
Meetoul said:
Thank you for your feedback. Probably, I won't fix the bugs in LOS 17.1, cause now I'm working on LOS 18.1 (based on Android 11) .
You can try it by this link https://drive.google.com/file/d/1kG8ebEf-GZW_AZ_d42HuxHHmHv0sQDl5/view?usp=sharing
Please note that I'm trying to keep this ROM as clean as possible, so currently it does not contain any proprietary Mediatek or Unihertz binaries (except vendor image, of course ). It means, that ROM does not include FM Radio or IMS. AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
What's tested and working:
Voice Call
SMS
WiFi
Bluetooth
Wired headset
NFC (it reads and emulates tags, GPay doesn't work because of SafetyNet, but I think I can bypass it)
IR remote control (I tested with ZaZa remote software
Click to expand...
Click to collapse
Meetoul said:
Thank you for your feedback. Probably, I won't fix the bugs in LOS 17.1, cause now I'm working on LOS 18.1 (based on Android 11) .
You can try it by this link https://drive.google.com/file/d/1kG8ebEf-GZW_AZ_d42HuxHHmHv0sQDl5/view?usp=sharing
Please note that I'm trying to keep this ROM as clean as possible, so currently it does not contain any proprietary Mediatek or Unihertz binaries (except vendor image, of course ). It means, that ROM does not include FM Radio or IMS. AFAIK, VoLTE is barely supported in Ukraine (yes, I live here ), so this feature is not really necessary for me. But I'll try to get those features working in future, just to have fully functional Jelly 2.
What's tested and working:
Voice Call
SMS
WiFi
Bluetooth
Wired headset
NFC (it reads and emulates tags, GPay doesn't work because of SafetyNet, but I think I can bypass it)
IR remote control (I tested with ZaZa remote software)
Click to expand...
Click to collapse
Hey, as far as i tested everything works for me.
There is one thing i noticed:
When booting, Lineage OS tells that the Build has been signed with Public Key, this seems to be a bit of a security issue. Is it possible to resolve that for the LOS 18 version. (Is that testable yet?)
Im fine with not having VoLTE, i think no Custom Rom is able to support it yet and it will just get important when the 3G network will be disabled...
Also if you need more help for testing specific stuff, i can do it.
beck.hannes said:
Hey, as far as i tested everything works for me.
There is one thing i noticed:
When booting, Lineage OS tells that the Build has been signed with Public Key, this seems to be a bit of a security issue. Is it possible to resolve that for the LOS 18 version. (Is that testable yet?)
Im fine with not having VoLTE, i think no Custom Rom is able to support it yet and it will just get important when the 3G network will be disabled...
Also if you need more help for testing specific stuff, i can do it.
Click to expand...
Click to collapse
@Meetoul I installed the LineageOs 18 now which seems to be fine too.
2 Warnings appear after boot. Again the one with the public key, and a new one: "Serial Console active"
My apologies for cross posting. But I initially replied in the wrong topic.
I just received my Jelly 2. It was on 2020 and I went straight through your files. Your TWRP does not respond on my European Jelly 2. And after a first reboot to recovery, TWRP was gone. What I mean with not responding is that the touch screen does not respond. But I connected an USB trackball to use as an input device and switched cables in between adb sideloads. So I finally got it working.
For some reason during reboot TWRP warns me that there is no OS installed. But LoS 18.1 (yours) booted fine. Also flashed opengapps 2707 nano.
After a reboot (phone is still restoring apps) there is a "serial console is enabled" message "performance is impacted, check bootloader". Any instructions on how to get rid of that message? Other than that so far so good.
Die Bruine said:
My apologies for cross posting. But I initially replied in the wrong topic.
I just received my Jelly 2. It was on 2020 and I went straight through your files. Your TWRP does not respond on my European Jelly 2. And after a first reboot to recovery, TWRP was gone. What I mean with not responding is that the touch screen does not respond. But I connected an USB trackball to use as an input device and switched cables in between adb sideloads. So I finally got it working.
For some reason during reboot TWRP warns me that there is no OS installed. But LoS 18.1 (yours) booted fine. Also flashed opengapps 2707 nano.
After a reboot (phone is still restoring apps) there is a "serial console is enabled" message "performance is impacted, check bootloader". Any instructions on how to get rid of that message? Other than that so far so good.
Click to expand...
Click to collapse
Touch in recovery
Have you tried the latest release which includes fixes for both available touch panes (at least for TEE Jelly2)? If yes and it doesn't work anyway, could you please provide dmesg output from recovery and from normal boot? Output of dmesg should be collected as soon as ADB available. Also, please collect kallsyms using the following steps:
Code:
adb root
adb shell
echo 0 > /proc/sys/kernel/kptr_restrict
sysctl -w kernel.randomize_va_space=0
cat /proc/kallsyms >/sdcard/symbl.txt
exit
exit
adb pull /sdcard/symbl.txt
Annoying "Serial console is enabled" notification
You can just long press on the notification and disable notifications from Development Settings.
Thanks, this 'latest' release works! I am curious though, why do I get the message that there is no OS installed when I reboot from recovery? Or is that gonna be a long as reply .Also a few mount errors during flashing and reboot. But, my phone works for 99%.
Only thing not working in my banking app is the fingerprint sensor, also in the Ebay app (which I use once a year). Do you know why this is? Amazon video, Ziggo streaming app, even my banking app works. Fingerprint to unlock the phone also works. Just not in apps. Is this due to it being unlocked?
I come from a qx1000/Pro1 with LoS 18.1 which died on me Wednesday night. That's why I'm asking. That thing was also unlocked, but no error messages there. Also the Corona check app states that the J2 is rooted (which it isn't). Exactly the same configuration as my Pro1. But no warnings on that phone.
Not real complaints, just thought I'd share. This will be my daily driver for the next few months. So if you need a heavy tester, I'm your man.
@Meetoul
The battery drains in 24 hours, is this normal? I can't find any apps draining it. Could the enabled serial console be the culprit?
Edit2:
Hotspot not working for me. It connects but does not provide an IP address to clients. I tried several stock Android devices, without success. All four devices connect, but keep waiting for an IP address.
So now I'm typing this via Bluetooth sharing, which sucks I can tell you.
If you have any suggestions, I am more than willing to try them out...
Hello,
I got a big issue on my Mi 10 Ultra, the stock camera is not wanting to work anymore.
It's black only and then refuses to launch (see screenshot attached).
I've tried third party apps but quality is not as good and I can't use all the camera modules. I've bought the 10 Ultra for it's cameras and really want to keep using it. (I do a lot of macrophotography and the 10 Ultra is amazing for this but only on the wide angle module.)
Did someone encountered the same issue ?
I've tried installing GCam but I do not managed to install apks. Theres an issue during the package analysis... (I've tried all GCam apks I could find here.)
I'm on stock EU OS with TWRP and I just activated root to try to solve the issue.
Sorry for bad english and french screenshots
EDIT: Every camera is working in the CIT hardware tests, I think it's software but I resetted the phone and nothing changed.
loupyes said:
Hello,
I got a big issue on my Mi 10 Ultra, the stock camera is not wanting to work anymore.
It's black only and then refuses to launch (see screenshot attached).
I've tried third party apps but quality is not as good and I can't use all the camera modules. I've bought the 10 Ultra for it's cameras and really want to keep using it. (I do a lot of macrophotography and the 10 Ultra is amazing for this but only on the wide angle module.)
Did someone encountered the same issue ?
I've tried installing GCam but I do not managed to install apks. Theres an issue during the package analysis... (I've tried all GCam apks I could find here.)
I'm on stock EU OS with TWRP and I just activated root to try to solve the issue.
Sorry for bad english and french screenshots
EDIT: Every camera is working in the CIT hardware tests, I think it's software but I resetted the phone and nothing changed.
Click to expand...
Click to collapse
stock EU OS ?
you mean Xiaomi Eu ROM?
If the code name is CAS,there are chinesse firmware only.
maybe try that
Use this tool https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Unroot before and dont relock the bootloader.
Thanks for the answer
NOSS8 said:
stock EU OS ?
you mean Xiaomi Eu ROM?
If the code name is CAS,there are chinesse firmware only.
Click to expand...
Click to collapse
I got the Xiaomi.EU ROM as it was shipped with. It has a TWRP recovery from when I rooted it and got Magisk installed.
My MIUI 12 version is V12.0.15.0.QJJCNXM (stable).
Use this tool https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Unroot before and dont relock the bootloader.
Click to expand...
Click to collapse
I understand this is a tutorial to change my ROM, which is not what I'm searching for as the ROM works really well. Plus I only see the CAS on this thread's links which is the chinese ROM.
Not sure what you meant.
My bootloader was locked all the time, I just unlocked it during my testing but it did not change anything.
loupyes said:
Thanks for the answer
I got the Xiaomi.EU ROM as it was shipped with. It has a TWRP recovery from when I rooted it and got Magisk installed.
My MIUI 12 version is V12.0.15.0.QJJCNXM (stable).
I understand this is a tutorial to change my ROM, which is not what I'm searching for as the ROM works really well. Plus I only see the CAS on this thread's links which is the chinese ROM.
Not sure what you meant.
My bootloader was locked all the time, I just unlocked it during my testing but it did not change anything.
Click to expand...
Click to collapse
My MIUI 12 version is V12.0.15.0.QJJCNXM=chinesse version
With this tool you will make a complete installation not like with the Twrp and can be recovered your the camera.
https://xiaomifirmwareupdater.com/miui/cas/stable/V12.0.15.0.QJJCNXM/
NOSS8 said:
My MIUI 12 version is V12.0.15.0.QJJCNXM=chinesse version
With this tool you will make a complete installation not like with the Twrp and can be recovered your the camera.
https://xiaomifirmwareupdater.com/miui/cas/stable/V12.0.15.0.QJJCNXM/
Click to expand...
Click to collapse
Now in the tests, my 5x telephoto camera does not respond, so I think it's an hardware issue, but I don't think the camera is broken so I'd like to found people with the same experience.
I don't think changing the recovery will solve the problem.
Plus I like having TWRP
loupyes said:
Now in the tests, my 5x telephoto camera does not respond, so I think it's an hardware issue, but I don't think the camera is broken so I'd like to found people with the same experience.
I don't think changing the recovery will solve the problem.
Plus I like having TWRP
Click to expand...
Click to collapse
Flash this rom to be sure
Mi 10 Ultra ChinaStableFastbootV13.0.4.0.SJJCNXM
Just to be sure of something, I did a test. Thanks for answering all my messages but what I need and want now is info or a way to debunk the issue.
I wont flash a ROM in a language I don't understand on the phone I use every day just to test something.
I already tried resetting the phone (including dalvik cache iirc) and it did not change anything.
Plus I would need a PC and a flashing tool, this would take a lot of time...
Finally, the issue did not came with a ROM change, the actual ROM is stable.
Edit : I changed the camera module, everything works perfectly
According to my repair shop, Xiaomis are just unreliable.
Android 14 dp1/dp2 are both now available and can be installed. I currently have a14 dp2 installed on my tmob v60. Just to be clear, this is not for everyone as it is very buggy. I'm current having problems with no audion for both phone calls and BT. This was a very well known problem with a13 betas and it the same again with a14.
If anyone knows of a work around (?????), then this would seem to be ready for a daily driver.
BTW, the download if available here.
hooutoo said:
Android 14 dp1/dp2 are both now available and can be installed. I currently have a14 dp2 installed on my tmob v60. Just to be clear, this is not for everyone as it is very buggy. I'm current having problems with no audion for both phone calls and BT. This was a very well known problem with a13 betas and it the same again with a14.
If anyone knows of a work around (?????), then this would seem to be ready for a daily driver.
BTW, the download if available here.
Click to expand...
Click to collapse
I will try later on to work on Audio fixes, It should be easy to fix actually
Kratos574 said:
I will try later on to work on Audio fixes, It should be easy to fix actually
Click to expand...
Click to collapse
Were you the one who worked on getting Treble ROMs to function fully in the previous versions? If so, how well did they work?
Kratos574 said:
I will try later on to work on Audio fixes, It should be easy to fix actually
Click to expand...
Click to collapse
The audio fix is a REALLY big deal. If this were to be fixed I would stay on a14 and never look back. Many now will be focused on the new Tmob a13 40a release for the next coming months but that's the end of the line for the LG V60. It seems Treble based roms are making great strides now and really picking up speed in term of development. For bootloader unlocked phones, such as this one, Treble rom are showing how fast older phones can be without all the bloatware crap loaded on by LG, Tmob, ATT, Verizon and (yes) google.
This is a post in response to my question on the v60 telegram channel about audio problem on this rom. The poster was Zakhmi.
"There are things in phh GSI that needs to be done after first boot
1-Enable Double tap to wake
Go to settings >phh trebble tree > xiaomi features > Enable D2W
2-Bluetooth audio fix
Go to Settings> phh trebble tree> misc features > Force Disable A2DP Offload and then restart phone..done
3-Fix call audio
Settings > phh treble settings > Qualcomn feature > tick mark use alternat audio policy and disable soundvolume effect
4- 90Hz enable
Go to Settings> phh trebble tree> misc features > Force FPS > 90
5- VoLte enable
Go to Settings> phh trebble tree> IMS features > Enable IMS network and force enable 4G calling....install 2nd option of IMS apk for qualcomn vendor...wait for download..then install it"
Item 2 and 3 may help fixing this problem for the V60.
AnnexedOne said:
Were you the one who worked on getting Treble ROMs to function fully in the previous versions? If so, how well did they work?
Click to expand...
Click to collapse
Well, I stopped working due I got a new phone but got back to V60 and started to work again, I am currently working on getting Quad Dac working once again on Treble roms, Fingerprint I already discarded the Idea due I tried most of known fixes but was unable to make it to work and also Dual screen is out of the question
Kratos574 said:
Well, I stopped working due I got a new phone but got back to V60 and started to work again, I am currently working on getting Quad Dac working once again on Treble roms, Fingerprint I already discarded the Idea due I tried most of known fixes but was unable to make it to work and also Dual screen is out of the question
Click to expand...
Click to collapse
Thanks for the effort? Are those the only issues that don't work for GSI roms? Are all GSI roms the same when it comes to what doesn't work?
I wonder if experiences with other treble phones may help with the V60's breakage.
Kratos574 said:
I will try later on to work on Audio fixes, It should be easy to fix actually
Click to expand...
Click to collapse
I now have A14 beta1 up and running. The a14 dp1/dp2 releases did not have any sound what so ever. The new a14 beta 1 has audio on calls and also music on speakers but no BT sound. Wondering whether you've made any progress on a BT audio fix. I've been looking closely at audio.policy.configuration.xml and a2dp.audio.policy.configuration.xml. It seems to be the most likey spot as most fixes/conversation starting with a9 going forward always take about a problem there.
Also, I've been able to double root it. I'm rooted with magisk 26100 and there's a utility that can change the entire OS to RW instead of RO so I can now easily direct copy the above mentioned config xml files to system/vendor/etc.
Too convert to RW see attachec file.
a14 beta2 gsi can be found here. I'm using the pixel 7p gsi.
I've switched to the Pixel 5 version of a14 b2 gsi and everything seems to be working, phone audio, camera, bt both for music and phone calls. This is a first for the v60, a14 and everything working!
hooutoo said:
I've switched to the Pixel 5 version of a14 b2 gsi and everything seems to be working, phone audio, camera, bt both for music and phone calls. This is a first for the v60, a14 and everything working!
Click to expand...
Click to collapse
Have you ever tried the pixel 5 version of say the a12L gsi? (I don't use the bleeding edge on phones I want to use as my primary).
hooutoo said:
Also, I've been able to double root it. I'm rooted with magisk 26100 and there's a utility that can change the entire OS to RW instead of RO so I can now easily direct copy the above mentioned config xml files to system/vendor/etc.
Too convert to RW see attachec file.
Click to expand...
Click to collapse
Did this work completely? I tried this twice (before Magisk 26.1). First time: incomplete RW. Second time: bootloop. My phone is still on A10.
AnnexedOne said:
Have you ever tried the pixel 5 version of say the a12L gsi? (I don't use the bleeding edge on phones I want to use as my primary).
Click to expand...
Click to collapse
Sorry, no. I'm really only interested in a14. As for converting to RO using the utility above I don't have it installed right now but I'm sure there are guides on the internet.
How this for dl speed?
a14 b2 pixel 5 gsi.... LTE only. Now need to work on getting 5g working.
A14 beta 3 gsi rom is now available:
https://sourceforge.net/projects/nippongsi/files/Generic/
I'm using the pixel5 rom and everything works fine, phone audio, bt audio and camera.
And NO, qdaq and fp are not working.
Any procedure step by step to flash A14 Beta 3 Nippon GSI in V60? i am interested to try this on my LG V600VM. Thanks