Related
// New builds at http://download.cyanogenmod.com/?device=legend[/COLOR]
Always make a nandroid, and flash on your own risk!
Because teamdouche's nightly is more than a month old, I decided to build a nightly myself.
Changelog:
http://cm-nightlies.appspot.com/?device=legend
---
10. feb build:
Everything to "Fix music widget transparency in landscape layout." is included.
http://www.mediafire.com/?udu1gnbnh4dul8d
---
23. jan build:
Everything to "Backport ICS rotation animations to gingerbread (android_frameworks_base)" is included.
http://www.mediafire.com/?ebprbr233gv1b50
---
13. jan build: - the friday 13. edition with Holo theme for ring lockscreen
Everything to "CM: Add p500 (LGE Optimus One) device (android_vendor_cyanogen)" is included.
http://www.mediafire.com/?pu4xfomdzxmvu5e
---
10. jan build:
Everything to "Exchange: calendar sync window linked to email sync window (android_packages_apps_Email)" is included.
http://www.mediafire.com/?9cckq1q24rqb9km
---
4. jan build:
Everything to "init: Let radio user manipulate service properties (android_system_core)" is included.
http://www.mediafire.com/?wb073sdj3b80k5y
---
2. jan build:
Everything to "CM: Add p925 (LGE ATT Thrill 4G) device (android_vendor_cyanogen)" is included.
http://www.mediafire.com/?8qo1rkjc5st21bs
---
23. dec build:
Everything to "Camera: Autofocus camcorder only if needed (android_packages_apps_Camera)" is included.
http://www.mediafire.com/?sze4uat4rl9weob
---
19. dec build: + T9 Dialer
Everything to "Preference to disable bootanimation for faster boot. (1/2 CMParts) (android_packages_apps_CMParts)" is included.
http://www.mediafire.com/?8ka5ouhorodnrzj
---
18. dec build:
Everything to "Fix emergency dialing on Samsung CDMA phones. Tested on Epic 4G, may also help others. DOES NOT FIX VIBRANT. (android_frameworks_base)" is included.
http://www.mediafire.com/?yon4treurcv557h
Nice to see that the Belgian keyboard layout is finally corrected
Just installed it and no problems so far, runs the same as 7.1
An update for HTC Legend, wow ! Thank you dude
Market does not work for me afte update!
stewie01 said:
Market does not work for me afte update!
Click to expand...
Click to collapse
After what update? Market is working fine here
Dialpad : T9 Dialer (android_packages_apps_Contacts) version building right now!
Edit: Up!
Tried to flash the one from 18th december, but CWM failed to verify the package, trying to download new one from the 19th...
ranger4740 said:
Tried to flash the one from 18th december, but CWM failed to verify the package, trying to download new one from the 19th...
Click to expand...
Click to collapse
I haven't encountered any problem while flashing.
can I update without wipe from regular 7.1? tnx
guap said:
can I update without wipe from regular 7.1? tnx
Click to expand...
Click to collapse
I guess so, but make a nandroid!
done
the stock t9 dialer doesn't show dial pad for default... really unuseful to have a t9 dialer (finally!!!) but still having to hold down a button to have the keyboard... that was the main reason to me for upgrade, and because of this I reverted back to my original 7.1 in ~10 minutes... also seemed a bit choppy, unable to use wavesecure, lost all my google apps settings... sounds like a NO for the upgrade with no wipe to me and no time to set all again at this time
thanks anyway
Well I tried this rom also just for this T9 Dialer...
I wiped before flashing so to be sure having a clean system.
Nothing special to mention about the rom itself... It works as the 7.1 does. (well, tested one hour only... Can't say for battery drain or else)
Regarding the dialer... Well, I think I don't get it well.
First, in the parameters, ensure you choose what the dialer will look for: Numbers or name. In my case, names.
Then, typing the numbers shows.... The numbers. the only way I found to get proposal according to the first digits is to go to another tab (contact for instance), and coming back to the dialer tab it will show me the possible contacts I wish to call.
Not very useful, neither practical.
I hope someone will find another way to use it ... More efficiently?
Thank you anyway for the work, mate! Really appreciated!
slovenec88 said:
I haven't encountered any problem while flashing.
Click to expand...
Click to collapse
Hi, thanks, I flashed the one from 18th dec. hung on the HTC boot screen for 10 mins reflashed and turned on signature verification in CWM and failed, downloaded again still no good, downloaded the one from the 19th, working ok, no problems.....
The nightly update seams to work really good, seams to be even more stable than 7.10, seams to fix the issue with ADW having to reload itself after a while.
GPS is still an issue, takes forever to get lock if at all...
Thanks, keep up the good work!
cyanogenmod fix for gps
$ su
# stop rmt_storage
# dd if=/dev/zero of=/dev/block/mmcblk0p13
# dd if=/dev/zero of=/dev/block/mmcblk0p14
# reboot
better do a nandroid backup if it doesn`t boot up anymore
this fixes the gps lock in about 5-10 sec and its been available since 6.0 cyanogen
caretaker01 said:
$ su
# stop rmt_storage
# dd if=/dev/zero of=/dev/block/mmcblk0p13
# dd if=/dev/zero of=/dev/block/mmcblk0p14
# reboot
better do a nandroid backup if it doesn`t boot up anymore
this fixes the gps lock in about 5-10 sec and its been available since 6.0 cyanogen
Click to expand...
Click to collapse
Thanks, trying as i type, in my case the above didn't seam to make any change, it was seeing the sats and using them eg. 6 in view 6 in use even after 10 mins no lock.
Right now it is seeing 12 sats, 10 in use been waiting over 5mins, still no lock.
Why are you guys copy-pasting commands you don't know what they actually do?
Sent from my HTC Legend
this fix was for vision and ace
I do not know if the partitionmapping is the same on the Legend
I do not recommend doing a dd zero until someone confirms the partitions
EDIT: the commands won't brick your device, in fact they DO NOTHING since the devs do not exist
Code:
block # ls -lha
brw------- 1 root root 179, 0 Dec 19 00:43 mmcblk0
brw------- 1 root root 179, 1 Dec 19 00:43 mmcblk0p1
brw------- 1 root root 31, 0 Dec 19 00:43 mtdblock0
brw------- 1 root root 31, 1 Dec 19 00:43 mtdblock1
brw------- 1 root root 31, 2 Dec 19 00:43 mtdblock2
brw------- 1 root root 31, 3 Dec 19 00:43 mtdblock3
brw------- 1 root root 31, 4 Dec 19 00:43 mtdblock4
brw------- 1 root root 31, 5 Dec 19 00:43 mtdblock5
I found it nice to see that someone picked the from source builds up and want to take some load off
http://datatomb.de/mirror/ROMs/CM7.2/update-cm-7.2.0-RC0-111222-Legend-KANG-signed.zip
this is my build from now, all changes until 21.12.2011 21:00 CET are included
DooMMeeR said:
EDIT: the commands won't brick your device, in fact they DO NOTHING since the devs do not exist
Click to expand...
Click to collapse
People stupid enough to copy/paste these commands would rather deserve /boot, /recovery, /system and /data wiped if you ask me.
@Blayo and Ali Ba, I did do a search before blindly typing the commands given, once I was satisfied they seamed to be legit, and not malicious i did the deed, obviously not every thing is equal in android land and something for one flavour of android O/S is transposable to another one.
---------- Post added at 02:53 AM ---------- Previous post was at 02:47 AM ----------
ranger4740 said:
Thanks, trying as i type, in my case the above didn't seam to make any change, it was seeing the sats and using them eg. 6 in view 6 in use even after 10 mins no lock.
Right now it is seeing 12 sats, 10 in use been waiting over 5mins, still no lock.
Click to expand...
Click to collapse
Ok, so after over 30 mins still no location lock, gps seeing and using upwards of 12 sats.
Oh Well, [email protected] Happens
I am getting an "Unfortunately Has Stopped" message in my release version that does not occur in the debug version. This happens both on my S4 mini and on the Samsung RTL devices. The debug version works on all of these devices plus on the Genymotion emulators. The error occurs using Jsoup when i tap my menu choice which activates Jsoup.connect.
So far i have determined that the problem is most likely caused by ProGuard, in the minify process. The release program does run if i set minifyEnabled to false but i would prefer to un-apply it just where necessary. So i need to know a few things ...
1. what is the syntax for the proguard statement to eliminate org.jsoup.* from being minified
2. which file is this statement to be added to, proguard-android.txt or proguard-rules.pro
3. how do i initiate a stack trace? It must be simple but my searches have not turned up a step by step procedure for this. I believe that with a stack trace i could identify which specific Jsoup modules need to be eliminated from minify rather than minifying the complete lib
It seems that these are very basic questions. Virtually every post that i have read on these subjects assumes that you know these things. Hope you can help.
Mick
OK, making a little progress.
Found this example -keep class org.joda.time. { ; }** so I substituted jsoup in place of joda, put it into the proguard-rules.pro file and my release build now runs
I found the -s or --stacktrace option and where to set it in the IDE. However I am lost about where to find the actual stacktrace when I run the program. I would appreciate any help i can get on how to get a stack trace, especially while running a release version of the program
Hello,
It's been 2 weeks I have my S10.
It's a G9730, a Snapdragon but with magisk installed as it is one of the only snapdragon with bootloader unlock.
I rooted a first time and I experimented random reboot. I though I did something bad with system app so I Factory reseted and now I'm only using root for normal apps (Tasker, Adblock, Titanium etc...)
I don't have any mod or UI tweak.
I still have random reboot. Something 3 times an day, sometimes, it's OK for 2 days and then....
Sometime it's while I'm using the phone but most of the time, I find my phone waiting for startup.
I uploaded 2 pictures :
- Autolog after random reboot
- What I mean by waiting for startup
I find on Google I'm not the only one. People with any root have the same issue. But there are no fix!
Can you help please?
I don't understand...
No random reboots for 3 days. I did not change anything and 4 random reboot since this morning!!!!
Hi,
As discovered by tulth, it's this bug that occurs. Why only so after rooting, I don't know. I think it's because of MagiskHide (which is doing nothing wrong, BTW) reading /proc/<PID>/status which triggers this kernel bug that Samsung didn't apply that patch to fix. As far as I know, Exynos models aren't affected because they have a slightly newer kernel; our .79 vs. their .85. As mentioned here, it occurs under "memory pressure", which is why it doesn't happen all the time. You can trigger this bug on demand and make your phone restart in the same way by doing this:
Code:
su
dd if=/dev/random of=/dev/shm # or any very large file (3-4 GB). This fills up the allocated space for shared memory
cat /proc/*/smaps_rollup
You're getting the exact same kernel panic as I do on my Snapdragon S10+/SM-G9750. My last_kmsg + disassembler output confirming that it's definitely the bug I linked to is here. I have a fix for the SM-G9750 but I'm waiting for a couple of days' uptime to ensure it doesn't mess anything else up on the phone (usually I get 16 hours idle or not - usually less - before my phone resets) before I open a thread with it. My phone currently does not reboot if I run the commands above, which wasn't the case before my fix.
What I could do with, before opening that thread, is the raw kernel image from a Snapdragon S10 to see if my patch needs adjusting for that model and, indeed, if it's even safe to apply on it. I don't want to download a 5GB firmware for a phone I don't have just to get a 35 MB file compressed.
Hi Qwerty!
Thank you for those really helpful information!
Do you want me to upload the 35Mb files for you?
I have the full ASF1 (last version on G9730) on my computer.
Note : I tried this command lines on terminal, nothing happend. See attached. Maybe I wrote it bad and should point to a large file as written?
(attachement)
Hi G-ThGraf,
Yes please, I only need the recovery.img.lz4 file, which should be inside the AP tarball
Note : I tried this command lines on terminal, nothing happend. See attached. Maybe I wrote it bad and should point to a large file as written?
Click to expand...
Click to collapse
Maybe /dev/random isn't enough, I must admit that I was dd'ing AP_G9750ZHU1ASF1_CL16082828_QB24224470_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5 from ADB because it happened to be on my phone because of the process to install Magisk...
qwerty12 said:
Hi,
As discovered by tulth, it's this bug that occurs. Why only so after rooting, I don't know. I think it's because of MagiskHide (which is doing nothing wrong, BTW) reading /proc/<PID>/status which triggers this kernel bug that Samsung didn't apply that patch to fix. As far as I know, Exynos models aren't affected because they have a slightly newer kernel; our .79 vs. their .85. As mentioned here, it occurs under "memory pressure", which is why it doesn't happen all the time. You can trigger this bug on demand and make your phone restart in the same way by doing this:
Code:
su
dd if=/dev/random of=/dev/shm # or any very large file (3-4 GB). This fills up the allocated space for shared memory
cat /proc/*/smaps_rollup
You're getting the exact same kernel panic as I do on my Snapdragon S10+/SM-G9750. My last_kmsg + disassembler output confirming that it's definitely the bug I linked to is here. I have a fix for the SM-G9750 but I'm waiting for a couple of days' uptime to ensure it doesn't mess anything else up on the phone (usually I get 16 hours idle or not - usually less - before my phone resets) before I open a thread with it. My phone currently does not reboot if I run the commands above, which wasn't the case before my fix.
What I could do with, before opening that thread, is the raw kernel image from a Snapdragon S10 to see if my patch needs adjusting for that model and, indeed, if it's even safe to apply on it. I don't want to download a 5GB firmware for a phone I don't have just to get a 35 MB file compressed.
Click to expand...
Click to collapse
I`ve got the same model here. Hope you can share your fix for s10+ ! I can be a tester I`ve unrooted because of these reboot problems.
Hi there,
@qwerty12, please find on this wetransfer the requested file : https://we.tl/t-HPxzXVTNwT
Is it OK ?
Also, I don't have any more random reboot since Saturday (27th) 3PM.
The only one thing I modify since saturday morning, I fully debloated the rom : https://forum.xda-developers.com/galaxy-s10/how-to/galaxy-s10-s10-debloat-bloatware-t3912073
I removed each of those app. (expect car mode)
Hi,
FlatOutRU said:
I`ve got the same model here. Hope you can share your fix for s10+ ! I can be a tester I`ve unrooted because of these reboot problems.
Click to expand...
Click to collapse
Will do, I'm just waiting until tomorrow for the two-day mark to pass... I'll be sure to send you something to test
My fix is simply this patch applied to the existing Samsung kernel on the device (the kernels I did manage to build from source would not boot on my phone) through, basically, a hex editor.
G-ThGraf said:
Hi there,
@qwerty12, please find on this wetransfer the requested file : https://we.tl/t-HPxzXVTNwT
Is it OK ?
Click to expand...
Click to collapse
Great, thank you! I'll use this to see if the kernel binary patch I have for my phone is safe to apply outright for your model, and fix it if not.
Also, I don't have any more random reboot since Saturday (27th) 3PM.
The only one thing I modify since saturday morning, I fully debloated the rom : https://forum.xda-developers.com/galaxy-s10/how-to/galaxy-s10-s10-debloat-bloatware-t3912073
I removed each of those app. (expect car mode)
Click to expand...
Click to collapse
You may not be seeing it any more because there's now less memory being sucked up by these vampiric programs, or one of these programs was going through /proc/ and reading smaps_rollup and status, which can trigger this kernel bug...
Hope there's some progress... i wish i can also do the fix.
i also using 9750 and magisk rooted... and yes, random reboot maybe about 2-3 times a day.
Hope a help too..
The same reboot bug on A50 device ?
Hi Qwerty!
You wrote in another discussion on this topic
qwerty12 said:
Yes:
I think you're right and that applying ASB-2019-01-05_4.9 would stop these KPs - just look at where smaps_pte_range+0x29c points to...
Magisk Canary from about four days ago has been causing many, many abrupt restarts in a day on my S10+; I had to downgrade to ianmacd-7.1.2-2019042401 (thanks Fznwolf), which has been stable (I get maybe one reset a day), but using old Magisk versions isn't really a viable long-term solution.
I could be wrong (I'm not a good programmer in the slightest), but from my quick glances over the kernel code, I think ASB-2019-01-05_4.9 could be worked-around via a module. However, the Samsung S10 kernel is built with CONFIG_MODULE_SIG_FORCE enabled, so loading any module not signed with Samsung's private key fails. A cursory look at load_module() seems to indicate patching the enforcement code out on disk (like Magisk does) or in memory would be trivial.
On a tangent, Samsung kernels are built with "clang version 6.0.10 for Android NDK", but the Qualcomm site only offers 6.0.9 to us mere mortals. Clang/LLVM 6.0.10 doesn't appear to be a thing, so it seems like .10 is some internal Qualcomm or Samsung toolchain. Does anybody know more about this? I don't want to replace the Samsung-provided kernel on my phone, which is why I'd like to be as close as I can be to Samsung's kernel-building environment, even if it seems impossible in this case...
Click to expand...
Click to collapse
I have an EXYNOS A50 device
And I have many times restarted with the same message
But for me the location is
Code:
PC is at smaps_pte_range+0x138/0x42c
LR is at smaps_pte_range+0xb0/0x42c
the kernel version is
Linux version 4.14.62-15891145 ([email protected]) (Android (4639204 based on r316199) clang version 6.0.1 (https://android.googlesource.com/toolchain/clang 279c0d3a962121a6d1d535e7b0b5d9d36d3c829d) (https://android.googlesource.com/toolchain/llvm aadd87ffb6a2eafcb577913073d46b20195a9cdc) (based on LLVM 6.0.1svn)) #1 SMP PREEMPT Thu Apr 25 23:38:19 KST 2019
Click to expand...
Click to collapse
And that's part of the log
Code:
<0>[ 28.558408] [0: android.bg: 4477] Unable to handle kernel read from unreadable memory at virtual address 000000f0
<2>[ 28.558434] [0: android.bg: 4477] sec_debug_set_extra_info_fault = KERN / 0xf0
<1>[ 28.558499] [0: android.bg: 4477] Mem abort info:
<1>[ 28.558512] [0: android.bg: 4477] Exception class = DABT (current EL), IL = 32 bits
<1>[ 28.558522] [0: android.bg: 4477] SET = 0, FnV = 0
<1>[ 28.558532] [0: android.bg: 4477] EA = 0, S1PTW = 0
<1>[ 28.558542] [0: android.bg: 4477] Data abort info:
<1>[ 28.558551] [0: android.bg: 4477] ISV = 0, ISS = 0x00000005
<1>[ 28.558560] [0: android.bg: 4477] CM = 0, WnR = 0
<1>[ 28.558571] [0: android.bg: 4477] user pgtable: 4k pages, 39-bit VAs, pgd = ffffffc87f702000
<1>[ 28.558580] [0: android.bg: 4477] [00000000000000f0] *pgd=00000008ff6fe003, *pud=00000008ff6fe003, *pmd=0000000000000000
<0>[ 28.558596] [0: android.bg: 4477] Internal error: Oops: 96000005 [#1] PREEMPT SMP
<4>[ 28.558607] [0: android.bg: 4477] Modules linked in:
<0>[ 28.558622] [0: android.bg: 4477] debug-snapshot: core register saved(CPU:0)
<0>[ 28.558632] [0: android.bg: 4477] CPUMERRSR: 0000000001100301, L2MERRSR: 0000000010045220
<0>[ 28.558641] [0: android.bg: 4477] debug-snapshot: context saved(CPU:0)
<6>[ 28.558681] [0: android.bg: 4477] debug-snapshot: item - log_kevents is disabled
<6>[ 28.558703] [0: android.bg: 4477] TIF_FOREIGN_FPSTATE: 0, FP/SIMD depth 0, cpu: 89
<4>[ 28.558715] [0: android.bg: 4477] CPU: 0 PID: 4477 Comm: android.bg Not tainted 4.14.62-15891145 #1
<4>[ 28.558725] [0: android.bg: 4477] Hardware name: Samsung A50 LTN OPEN rev04 board based on Exynos9610 (DT)
<4>[ 28.558735] [0: android.bg: 4477] task: ffffffc8454cd280 task.stack: ffffff800b2b0000
<4>[ 28.558750] [0: android.bg: 4477] PC is at smaps_pte_range+0x138/0x42c
<4>[ 28.558761] [0: android.bg: 4477] LR is at smaps_pte_range+0xb0/0x42c
<4>[ 28.558770] [0: android.bg: 4477] pc : [<ffffff8008449ad4>] lr : [<ffffff8008449a4c>] pstate: 40400145
Is this also a fault of ASB-2019-01-05_4.9 ?
Can I help try to resolve the problem
Hi @qwerty12
I would like to find a solution to this problem,
Because I have some devices that I rooted for people
And they have the same problem,
I can help check it out on many new Samsung models,
This happens most in my sample devices A50 but also occurs in A30 S10E A70 etc.
Is the process of editing in X-EDITOR simple?
Could I possibly do this myself?
Because I don't know how to find this operator's location inside the kernel file,
I just tried to open it with BLESS-HEX-EDITOR
In the past I fixed a lot of binaries with it, but only things that were defined as strings and not an operator that was compiled with the code.
Hullo,
aharonshor said:
Is this also a fault of ASB-2019-01-05_4.9 ?
Click to expand...
Click to collapse
Given your kernel version, I would surmise so, yes. (I can't actually give you a definitive answer without looking at a disassembly of your kernel, which isn't something I wish to do. If you want to verify it yourself, get this working.)
4.14.81 is the first version of the LInux kernel 4.14 branch with that fix included; quite evidently, 4.14.62 is a long way off from there. I wouldn't know what was the first version of 4.14 to introduce the problematic code.
S10 Exynos versions weren't affected by this because they were shipped with 4.14.85, I think. We Snapdragon users got .78...
aharonshor said:
I would like to find a solution to this problem,
Because I have some devices that I rooted for people
And they have the same problem,
Click to expand...
Click to collapse
I can empathise, because I once did the same, but I only root my own phones and not others' these days. Taking on the burden of technical support and being the person to blame if something unrelated causes a problem isn't worth it, unless you're being recompensed for your time.
Is the process of editing in X-EDITOR simple?
Click to expand...
Click to collapse
I mean, you might use a hex editor to apply a resulting patch, but you'd want to use a disassembler. A hex editor on a 40 MB binary to find something isn't happening, unless you can turn random bytes of hex into ARM instructions in your head.
Could I possibly do this myself?
Click to expand...
Click to collapse
As I told an Internet friend, if you know ARM assembly, you don't need my help at all, and if not, well talk about a case of the blind leading the blind... I'm not a programmer and do not have any business teaching bad habits. In any case, I don't, and will not for the foreseeable future, the time to write a guide.
I'd recommend just building your own kernel with this patch applied. That process is far simpler, and unless you know what instructions you should be looking for inside the ARM Reference Manual and how to calculate the offset of the check_shmem_swap member inside the mss struct, you would need to build a kernel anyway first to have the compiler do all of that work.
I haven't looked at this in a long time and do not plan to revisit the topic; my own kernels are good enough for me, if rather basic.
Hello all
Im trying to run custom apps on my Ford Sync 3 unit but i whatever method I try, I get the 'no new messages on this drive' notification when launching the app.
I'm trying to launch performace monitor on my headunit but it doensn't work with any custom app except cartube.. Wich was just a simple install using AAStore.
My specs:
Headunit: Ford Sync 3 unit with software version 3.4.21265
Phone: Oneplus 8Pro with Android 13 Build IN2015_11_F.13 !!PHONE IS ROOTED!!
AA version: 8.7.630264-release (Tried downgrading but can't get any further then AA 7.6. Downgrading any further AA will not boot and forces an update)
Things i've tried:
- Installing through AAStore
- Installing though AAAD
- Patching the apps using Phenotype Patcher
- Paching the apps using AA AIO Tweaker
- Installing apps using KINGinstaller 1.2
I always reinstall AA by delete AA updates and clear cache in between tryouts... Developermode + unknown sources are enabled in AA. I give the custom app all requested access and permissions before launching.
I don't know what else I can try. I'm trying to launch performace monitor on my headunit but it doensn't work with any app except cartube.. Wich was just a simple install using AAStore.
Any feedback would be appreciated!
I recently downgraded my rog phone 3 from android 12 to android 11 while rooting it with twrp and magisk. After I did this, everything worked fine on my system (besides mms for a moment), once it is flashed, the first reboot afterwards completely stops bluetooth from functioning. No startup, nothing. The drivers are just nonfunctional I guess. Anyone else have this issue/ know how to solve? Not very fluent in this and just looking to fix this asap.
Also here is a logcat error that shows itself when I try to enable bluetooth.
FATAL EXCEPTION: BluetoothDatabaseManager
Process: com.android.bluetooth, PID: 2430
android.database.sqlite.SQLiteCantOpenDatabaseException: Cannot open database '/data/user_de/0/com.android.bluetooth/databases/bluetooth_db': Directory /data/user_de/0/com.android.bluetooth/databases doesn't exist
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:252)
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:205)
at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:505)
at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:206)
at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:198)
at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:918)
at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:898)
at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:762)
at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:751)
at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:373)
at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:316)
at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper$OpenHelper.getWritableSupportDatabase(FrameworkSQLiteOpenHelper.java:145)
at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper.getWritableDatabase(FrameworkSQLiteOpenHelper.java:106)
at androidx.room.RoomDatabase.inTransaction(RoomDatabase.java:476)
at androidx.room.RoomDatabase.assertNotSuspendingTransaction(RoomDatabase.java:281)
at com.android.bluetooth.btservice.storage.MetadataDao_Impl.load(MetadataDao_Impl.java:258)
at com.android.bluetooth.btservice.storage.MetadataDatabase.load(MetadataDatabase.java:95)
at com.android.bluetooth.btservice.storage.DatabaseManager$DatabaseHandler.handleMessage(DatabaseManager.java:124)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:248)
at android.os.HandlerThread.run(HandlerThread.java:67)
Caused by: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:224)
... 20 more
I really need help with this if anyone could spare the time.
I have dumped the same stock rom I installed and I have noticed it is missing the bluetooth APEX file. Is it even possible to install an APEX file without reinstalling an entire system? I know the format is similar to APK and i have read/write access to my system partition, so is it possible to do?
Try setting selinux to permissive (from a root command line, run "setenforce 0"). I have a similar issue (messed up permissions when downgrading and I'm trying to debug it now. I'm trying to figure out how to fix those permissions without disabling selinux entirely, as disabling it is a massive security hole.