Database Info

bluetooth not working after update

i updated CM11s and now bluetooth is not working anymore.
if i try to turn it on, it tries to activate bluetooth, then goes back off.
a full wipe didn't solved the problem, but it works with a clean rom (i tried mahdi, but i had to restore backup since monday i'm leaving for holidays and i don't have time to restore all i need on the mobile now).
i know i'm not giving many infos to have some help, but if you give me some directions i can try to fix it.
also, is it possible to reinstall CM11s with twrp or just through fastboot?
thanks!

I also have trouble with Bluetooth.
It tries to send file but either the app crashes or the file can't be sent.
Any info in that?

seems like noone has this kind of troubles

Hi! I just ran into the same problem: after upgrade to Cyanogen OS version 11.0-XNPH05Q, my bluetooth connection turns out to be unusable.
It first seems to connect (after "search for devices" is hit), but immediately when the call is initiated, the connection drops out (nokia BH-105).
Will check with my car installation too.
Is it possible to downgrade to previous Cyanogen OS version - I even don't know, which one was it... but at least it was working well!

Also having troubles with Bluetooth and my car-system since the 5Q update.
Before latest 5Q update everything works fine, but now neither of the devices can see the other one anymore
already deleted existing pairing in my car-system, but can't set up new pairing...
wondering if change of kernel can be a solution tho?

loth77 said:
i updated CM11s and now bluetooth is not working anymore.
if i try to turn it on, it tries to activate bluetooth, then goes back off.
a full wipe didn't solved the problem, but it works with a clean rom (i tried mahdi, but i had to restore backup since monday i'm leaving for holidays and i don't have time to restore all i need on the mobile now).
i know i'm not giving many infos to have some help, but if you give me some directions i can try to fix it.
also, is it possible to reinstall CM11s with twrp or just through fastboot?
thanks!
Click to expand...
Click to collapse
geri.st said:
I also have trouble with Bluetooth.
It tries to send file but either the app crashes or the file can't be sent.
Any info in that?
Click to expand...
Click to collapse
loth77 said:
seems like noone has this kind of troubles
Click to expand...
Click to collapse
nixnix33 said:
Hi! I just ran into the same problem: after upgrade to Cyanogen OS version 11.0-XNPH05Q, my bluetooth connection turns out to be unusable.
It first seems to connect (after "search for devices" is hit), but immediately when the call is initiated, the connection drops out (nokia BH-105).
Will check with my car installation too.
Is it possible to downgrade to previous Cyanogen OS version - I even don't know, which one was it... but at least it was working well!
Click to expand...
Click to collapse
J0ch3nK said:
Also having troubles with Bluetooth and my car-system since the 5Q update.
Before latest 5Q update everything works fine, but now neither of the devices can see the other one anymore
already deleted existing pairing in my car-system, but can't set up new pairing...
wondering if change of kernel can be a solution tho?
Click to expand...
Click to collapse
https://jira.cyanogenmod.org/browse/BACON-2822

nixnix33 said:
Hi! I just ran into the same problem: after upgrade to Cyanogen OS version 11.0-XNPH05Q, my bluetooth connection turns out to be unusable.
It first seems to connect (after "search for devices" is hit), but immediately when the call is initiated, the connection drops out (nokia BH-105).
Will check with my car installation too.
Is it possible to downgrade to previous Cyanogen OS version - I even don't know, which one was it... but at least it was working well!
Click to expand...
Click to collapse
this is still CM and not oxygen OS

[ROM] [UNOFFICIAL] Lineage OS 17.1 | Unihertz Jelly 2

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...

Micro-disconnection result app crash

Hi,
I am running last Android 11 xiaomi.eu weekly rom and i use xiaomi.eu since 6 month and i have a problem since beginning, some app dont work properly due to some micro disconnection (i think) because some app don't load, i can open app but i can't connect/login on it or i must to load it 2 or 3 or more time like facebook.
When i use wifi no problem but with cellular it's difficult.
Can you help me to solve this problem?
Thanks by advance

Fangstergangsta said:
Hi,
I am running last Android 11 xiaomi.eu weekly rom and i use xiaomi.eu since 6 month and i have a problem since beginning, some app dont work properly due to some micro disconnection (i think) because some app don't load, i can open app but i can't connect/login on it or i must to load it 2 or 3 or more time like facebook.
When i use wifi no problem but with cellular it's difficult.
Can you help me to solve this problem?
Thanks by advance
Click to expand...
Click to collapse
Surely already done:
check the permissions of the affected apps
settings / management of applications / installed applications.
Uninstalled and reinstalled the affected applications.
If you have updated roms on roms, try a clean flash with the latest android 11 version.

Yes already done i think this is micro cuts on cellular reception for exemple when i use tethering with ftp soft on my comp i can't keep connection because the connection is unstable or micro cuts on cellular datas...
Have you an idea to solve this problem i am the only one facing this issue?

Fangstergangsta said:
Yes already done i think this is micro cuts on cellular reception for exemple when i use tethering with ftp soft on my comp i can't keep connection because the connection is unstable or micro cuts on cellular datas...
Have you an idea to solve this problem i am the only one facing this issue?
Click to expand...
Click to collapse
Did you install the rom in cleanflash?
For tethering try activate Usb debugging in developer option.
Special features /miui lab/AI preloading

Yes cleanflash....
I Hope Android 12 solve this problem...
But am waiting for compatible twrp...

Fangstergangsta said:
Yes cleanflash....
I Hope Android 12 solve this problem...
But am waiting for compatible twrp...
Click to expand...
Click to collapse
the twrp work if you deactivate the protections on the lock screen or if you format the data.
here Twrp for android 12.

Okay if i understand correctly i can flash xiaomi.eu Android 12 rom using this twrp (this is already the one i have 1206) but before i must to disable the unlock pattern and finger print?
1) disable security pattern
2) flash the xiaomi.eu rom Android 12
3) enable security pattern
And do this every Time?
I read about some users loosing their twrp?

Fangstergangsta said:
Okay if i understand correctly i can flash xiaomi.eu Android 12 rom using this twrp (this is already the one i have 1206) but before i must to disable the unlock pattern and finger print?
1) disable security pattern
2) flash the xiaomi.eu rom Android 12
3) enable security pattern
And do this every Time?
I read about some users loosing their twrp?
Click to expand...
Click to collapse
No,you can't.
Xiaomi eu rom A12 only Fastboot.
I read about some users loosing their twrp?
For the TWRP you flash it after installing the rom.

Thanks for all your help i will wait for a fullly compatible twrp

touch input destroyed after Apr security update

had this device all of a week (barely), seemed to work great out of the box, have left it stock intentionally.
take the April security update, reboot.
Have completely lost pinch zoom / multitouch and it seems as though the screen's settings, software or combination are completely misaligned / out of whack regarding touch input.
It's the kind of behavior you get when you have a droplet on your screen and the phone screen is getting erratic input... like it's compromised or fragmented somehow.... I've increased sensitivity which made the phone more usable, but I can barely use the bottom row of my home screeen. If I switch to left hand and try my L thumb, it better detects the input (if I aim WAY LOW). Almost like the calibration for the screen touch has been completely FUBAR.
Hoping custom software and lack of OTA updates fixes this? Has this community seen this issue and are custom ROMs a way out of the mess, or is this a hardware issue that absolutely requires the device to be returned and replaced? Seems odd the change happened with no physical change to the phone.

Same issue here when updating. Complete factory reset fixed mine

@beflythis hey did you figure the fix out? I have a similar issue. Factory reset didn't help me

Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do

Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO

@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?

anshuuu03 said:
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
Click to expand...
Click to collapse
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.

This is definetly an issue with what seems to be the software, not sure exactly what is wrong though (I dont know too much about kernel driver code),

anshuuu03 said:
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Click to expand...
Click to collapse
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.

fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Do let me know if it works. It would be a life saver

fbievan said:
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
Click to expand...
Click to collapse
I think downgrading to Android 10 has worked for almost everyone facing this problem

vovapolischuk said:
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
Click to expand...
Click to collapse
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none

fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Now that i know that im now going crazy, and atleast one other person has very very similar story to mine, there needs to be a proper fix. I do know that android 10 and android 11 do have different touchscreen drivers. Downgrading then upgrading back wont work, atleast to my knowledge. I've done plenty of looking, and just don't know whats wrong. If any kernel devs that know their way around touchscreen drivers, and pixel 4as. Would be a life saver. But I have little idea of whats actaully going wrong.

anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Yep, downgrading again to Android 10 alllows multittouch to work

anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?

fbievan said:
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
Click to expand...
Click to collapse
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?

anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.

fbievan said:
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
Click to expand...
Click to collapse
Make sure to test, test, and test

anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
Can I ask: has that worked for you?

fbievan said:
Can I ask: has that worked for you?
Click to expand...
Click to collapse
I think I will try and do the 10 > 11 > 12 > 13 in a few days. I am stuck with some work and cannot afford to keep resetting my phone atm. But I will update here whatever is the update on that

I want to flash a custom ROM on this phone. Is there somethings I need to be aware of?

Hello,
I own a motorola one vision and would like to flash LineageOS 20 on the device. I am creating this thread to know the experiences of people who did something similar. I would like to know if there is any issues with a custom ROM on this device [calling issues, or similar]. I would also like to know if there is a way to revert back to the stock ROM in case I screw up something. I have read several threads about this device but I would like to confirm it again and be provided with some pointers of what I could expect with a custom ROM on this device and how I could revert back to the stock ROM in case I screw something up.
Thanks in advance

nsg650 said:
Hello,
I own a motorola one vision and would like to flash LineageOS 20 on the device. I am creating this thread to know the experiences of people who did something similar. I would like to know if there is any issues with a custom ROM on this device [calling issues, or similar]. I would also like to know if there is a way to revert back to the stock ROM in case I screw up something. I have read several threads about this device but I would like to confirm it again and be provided with some pointers of what I could expect with a custom ROM on this device and how I could revert back to the stock ROM in case I screw something up.
Thanks in advance
Click to expand...
Click to collapse
I have been using lineageos since last year. I have used lineageos19 and am currently using lineageos20. The user experience is quite good. Everything works fine including calling except the hotspot. Hotspot does work but you have to keep tapping on the toggle to enable the hotspot or you can just restart the phone that's the temporary fix for the hotspot issue. The developer might fix the issue in the future updates. Other than that I didn't find any issue with the ROM and also it doesn't pass the safety net so you have to root your phone and install magisk to bypass safety net so that you can use your banking apps.
There are two versions official and unofficial. Official gets update every week and unofficial one is with the pixel features and google apps. It gets monthly updates.
If anything goes wrong you can install the official software called lenovo rescue and smart assistant on your pc and connect your phone with usb to pc. It can recover your phone to the original android 11 stock ROM.

Ryukrryts said:
I have been using lineageos since last year. I have used lineageos19 and am currently using lineageos20. The user experience is quite good. Everything works fine including calling except the hotspot. Hotspot does work but you have to keep tapping on the toggle to enable the hotspot or you can just restart the phone that's the temporary fix for the hotspot issue. The developer might fix the issue in the future updates. Other than that I didn't find any issue with the ROM and also it doesn't pass the safety net so you have to root your phone and install magisk to bypass safety net so that you can use your banking apps.
There are two versions official and unofficial. Official gets update every week and unofficial one is with the pixel features and google apps. It gets monthly updates.
If anything goes wrong you can install the official software called lenovo rescue and smart assistant on your pc and connect your phone with usb to pc. It can recover your phone to the original android 11 stock ROM.
Click to expand...
Click to collapse
Hey! Sorry for checking after this long. I don't plan on using any banking apps so it will be fine for me. I already got my unlock code and just have to unlock the device and flash LineageOS. I will do that after backing it up. Thank you for your sharing your experience !!!