I've noticed that multiple people, including myself, have had multiple issues with random reboots on various ICS roms. Well it was driving me crazy, so I decided to catch it in the act. Please see this from my logcat:
Code:
04-18 17:04:36.799 E AlarmManagerService: android_server_AlarmManagerService_set to type=2, 115438.634000000
04-18 17:04:36.799 V AlarmManager: trigger WAKEUP Alarm{41c5fcd8 type 2 android}
04-18 17:04:36.809 W dalvikvm: threadid=13: thread exiting with uncaught exception (group=0x40c231f8)
04-18 17:04:36.809 E android.os.Debug: [email protected] > dumpstate -k -t -n -z -d -o /data/log/dumpstate_sys_error
04-18 17:04:36.809 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: android.server.ServerThread
04-18 17:04:36.809 E AndroidRuntime: java.lang.NoSuchMethodError: com.android.server.WimaxService.access$1002
04-18 17:04:36.809 E AndroidRuntime: at com.android.server.WimaxService$4.onReceive(WimaxService.java:1150)
04-18 17:04:36.809 E AndroidRuntime: at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:728)
04-18 17:04:36.809 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:605)
04-18 17:04:36.809 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:92)
04-18 17:04:36.809 E AndroidRuntime: at android.os.Looper.loop(Looper.java:137)
04-18 17:04:36.809 E AndroidRuntime: at com.android.server.ServerThread.run(SystemServer.java:986)
04-18 17:04:36.834 I dumpstate: Check if stand-alone
04-18 17:04:36.859 I dumpstate: begin
I went back through several saved logcats after these reboots, and the signature looks the same. It looks to me as if the WiMax service (WimaxService.java) is calling an invalid method (com.android.server.WimaxService.access$1002), and causing android server to crash with a FATAL exception.
Now, I'm not a programmer, but does anyone have any ideas on how we can investigate the code and see if we can make a workaround? Thoughts anyone? I'll keep at this.
I'm not a program either, but I know Team Nocturnal had this same issue on a couple of their ROMs and Mijjah was working on it. Not sure if he has any logs of it happening.
I do know he's working on an AOKP rom as well, which I'm using, and I haven't had the issue yet.
Maybe post this in the dev thread of the rom you are using. I think we can all benefit from this Im sick of my phone rebooting while using 4g!!
Hello everyone,
I'm having problems trying to figure it out what's happening with my HTC One M9. Right now the phone is
S-OFF
Software status: modified
Bootloader unlocked
It's running latest software 3.35.401.12. Upgraded via official OTA from 1.32.401.8 (flashed using link found here).
The problem I have right now is that when I reboot in download mode and chose hardware information the CPU appears unknown and some other weird stuff. Quote:
LCD: HIME FHD Tianma/Renesas video mode dsi panel?
CPU: UNKNOWN
CPU rev: 2.1
DDR: 00000001, 3GB
cx voltage Error
mx voltage Error
No CPU param
RFG_3: Error
CRADIO: N/A
The phone works properly most of the times, but after every some time (might be month or even 2 days) it reboots itself and then is unusable unless I do a factory reset. After the "fatal" reboot I was able to pull logs and they were full with stuff like this:
HTML:
07-13 16:33:43.069 22059 22059 E AndroidRuntime: FATAL EXCEPTION: main
07-13 16:33:43.069 22059 22059 E AndroidRuntime: Process: com.google.process.gapps, PID: 22059
07-13 16:33:43.069 22059 22059 E AndroidRuntime: java.lang.RuntimeException: Unable to start receiver com.google.android.gms.auth.be.proximity.authorization.bt.AuthorizationBluetoothService$AutoStarter: android.database.sqlite.SQLiteException: Can't downgrade database from version 2 to 1
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.app.ActivityThread.handleReceiver(ActivityThread.java:2824)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.app.ActivityThread.access$1800(ActivityThread.java:150)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1484)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.os.Looper.loop(Looper.java:168)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5845)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:797)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:687)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: Caused by: android.database.sqlite.SQLiteException: Can't downgrade database from version 2 to 1
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.onDowngrade(SQLiteOpenHelper.java:360)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:254)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:163)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.google.android.gms.auth.be.proximity.b.a.a(SourceFile:43)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.google.android.gms.auth.be.proximity.b.c.a(SourceFile:175)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.google.android.gms.auth.be.proximity.authorization.bt.b.a(SourceFile:213)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.google.android.gms.auth.be.proximity.authorization.bt.AuthorizationBluetoothService$AutoStarter.onReceive(SourceFile:246)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.app.ActivityThread.handleReceiver(ActivityThread.java:2810)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: ... 8 more
07-13 16:33:43.684 22098 22098 E AndroidRuntime: FATAL EXCEPTION: main
I got the phone SH with Viper ROM on it. It had issues related to WiFi hardware and also random reboots (but after reboot everything worked). Then I tried to back to stock rom/firmware and the phone worked for ~ 3-4 months. Then it did the reboot happened, I did a factory reset, and worked again for ~ 2 days.
Any ideas how I can fix/debug this? Or can it that my MID and CID are completely wrong and I need a different ROM?
mid: 0PJA10000
cid: HTC__102
Did you flash twrp too?. Which version twrp do you have, which version supersu?.
A LOT of sqlite issues there, could be related rather than responsible..
Beamed in by telepathy.
I don't have TWRP and no root. I try to keep my phones as stock as possible since I don't need that stuff. The error log is after the "reboot" happened. The events succeeded as following
reboot (out of the blue)
reboot loop for a while
I'm not sure, but I think I was able to clear the cache from bootloader/recovery
phone started by I had a lot of issues (Google Apps keep crashing)
fetched the log (posted above)
So I also think the logs are more like the effect of the problem. I wasn't able to fetch the kernel logs (I saw that you can usually ready what caused a kernel panic), but since was happening twice now, I expect it to happen again. That's why I want to be prepared and try to get as much information as I need.
Another theory is that NAND is broken, and the phone works until it gets to write in a bad block. But I don't know how to properly test that.
BTW: the phone is my backup phone. So I can do a lot of test with it for the next few days without worrying about data.
Sorry for the double post, but I don't want to create another topic for this. I tried to make a nandroid backup today, but without flashing twrp
Code:
fastboot boot twrp-2.8.7.0-hima.img
I selected all partitions, except cache, but this happened (see link to "screenshot" below). Is it normal? Does it mean anything? I mounted system as "read-only".
i.imgur.com/RQsbxzT.jpg (apparently I'm not allowed to post links, so you have to copy/paste this)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Images
Here are some Screenshots of this ROM.
Ask me
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation instructions
Prerequisites:
Unlocked Sony Xperia Z3
Latest firmware .291
Fastboot drivers to install TWRP
Micro-USB Cable to connect your phone to your computer
Install:
Reboot to TWRP. *
Wipe cache, dalvik cache, data and system.
Format data to get rid of encryption.
Install ROM.
Install 10.0 Gapps for ARM. **
* recommended TWRP: Download TWRP
** optional
Update:
Get the latest build
Boot into TWRP
Flash the downloaded build
Reboot, if you don't wipe system backuptool will handle to reapply your modifications, for example: GApps.
Downloads
Download ROM
MD5: 78a54bc2c55ce935a97b4c16cebe3c69
Addons
OpenGapps
BiTGApps
microGISG (Alternative GApps microG based)
Magisk
SU-Addon
Thanks
Whole LineageOS Team for this amazing ROM
@rcstar6696
@Myself5
@drakonizer
@tomascus
@koron393
@nailyk
@SpiritCroc
I hope I haven't forgot anyone
Bugs
WHAT'S BROKEN
Tell me
XDA:DevDB Information
LineageOS 17.1 z3, ROM for the Sony Xperia Z3
Contributors
NeoArian & Mr.Tom_Tom
Donate to support development:
Donate via PayPal to NeoArian *** Our main contributor for LineageOS 16 & 17 for Z3 and Z3 Compact ***
Donate via PayPal to LineageOS
ROM OS Version: 10.x
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 2020-08-18
Stable Release Date: 2020-05-01
Current Beta Version: 2020-02-23
Beta Release Date: 2020-02-08
Created 2019-10-17
Last Updated 2020-08-18
Working LOS17 build achieved
Yep, here it is: LineageOS 17 with Android 10 for our good old Z3. Shinano's not dead (yet)!
Thanks to @NeoArian for sharing repos, manifests and some hints. Behavior seems to be similar to the Z3c build.
The following links are provided for testing purposes only and may be deleted in a few days, please refer to the "official" download links of the thread owner (thanks @ronidianpatisa).
Warning: the links below are now outdated, use the download links in post #1 please
Download: LOS 17 ROM for Z3, compiled as userdebug for TESTING ONLY (alternate hoster here)
Download: Related MD5 checksum file
Download: TWRP for Z3, compatible with Android 10 ROMs for TESTING ONLY
Download: GAPPS BETA
What I have tested so far: checklist working/not working (again, thanks to @NeoArian for this idea and the initial list)
What about Z3 Dual support ? Can D6633 users test the rom safely ?
Thanks @ MrTom_Tom for the sharing of the early LOS 17 build. Very nice from you.
One question: For what stands tbd in the linked checklist?
Nevetheless i will wait for the builds from NeoArian with working encryption.
I have tested your Android 10 rom for z3! Here it is some issues that I have found!
1. when device is power off, if that time you charge your phone until you unplug usb charge cable you cant turn on your phone.
2. when you flash android 10 test rom zip and gapps zip , your sony xperia z3 logo will start and reset itself "loop" until you hold power button and volume up key hold together to power off your phone. Solution that I find is " after you power off phone, Hold power button and volume down key 5 sec , twrp recovery windows will pop up, then Wipe cache, dalvik cache, data and system. 1. first, install android 10 zip rom ,reboot phone then power off the phone, reboot in twrp recovery and flash gapps- pico or micro.
3. Battery percentage icon doesn't show on status bar.
4. some google sound cant be saved.
5. Pixel launcher crashes all the times.
6. power off charge doesn't show battery percentage.. .. during the charge screen doesn't turn off. I guess, these are common lineageOS kernel issue .
7. There is no sony xperia z3 FM radio app..
8. Digital wellbeing apps keep stoping.
.
.
.
dhacke said:
[...] i will wait for the builds from NeoArian with working encryption.
Click to expand...
Click to collapse
Yes, please do not use this build as a daily driver yet! But we are happy for every feedback on the test build.
dhacke said:
For what stands tbd in the linked checklist?
Click to expand...
Click to collapse
tbd = to be determined = not yet tested
elmxx said:
1. when device is power off, if that time you charge your phone until you unplug usb charge cable you cant turn on your phone.
2. when you flash android 10 test rom zip and gapps zip , your sony xperia z3 logo will start and reset itself "loop" until you hold power button and volume up key hold together to power off your phone. Solution that I find is " after you power off phone, Hold power button and volume down key 5 sec , twrp recovery windows will pop up, then Wipe cache, dalvik cache, data and system. 1. first, install android 10 zip rom ,reboot phone then power off the phone, reboot in twrp recovery and flash gapps- pico or micro.
3. Battery percentage icon doesn't show on status bar.
4. some google sound cant be saved.
5. Pixel launcher crashes all the times.
6. power off charge doesn't show battery percentage.. .. during the charge screen doesn't turn off. I guess, these are common lineageOS kernel issue .
7. There is no sony xperia z3 FM radio app..
8. Digital wellbeing apps keep stoping.
Click to expand...
Click to collapse
First of all, thanks for testing and providing feedback!
Regarding your comments:
1. Confirm, known issue: checklist working/not working
2. Are you sure you wiped DATA during your first flash? I do not think it is necessary to wipe SYSTEM.
3. Cannot confirm that issue. Icon is present, and when you swipe down, a percentage value is shown next to the icon.
4. Not sure what you mean by that
5. This is by design since Android P, unfortunately. Please see this explanation.
6. I guess You're right
7. Confirm, known issue. (Honestly speaking I was not expecting that someone will miss that FM radio.)
8. I would expect that there are some dependencies to other google stuff. Can someone confirm that?
Thanks you for your concern and your hard work along with your dedication.
Mr.Tom_Tom said:
Yes, please do not use this build as a daily driver yet! But we are happy for every feedback on the test build.
tbd = to be determined = not yet tested
First of all, thanks for testing and providing feedback!
Regarding your comments:
1. Confirm, known issue: checklist working/not working
2. Are you sure you wiped DATA during your first flash? I do not think it is necessary to wipe SYSTEM.
3. Cannot confirm that issue. Icon is present, and when you swipe down, a percentage value is shown next to the icon.
4. Not sure what you mean by that
5. This is by design since Android P, unfortunately. Please see this explanation.
6. I guess You're right
7. Confirm, known issue. (Honestly speaking I was not expecting that someone will miss that FM radio.)
8. I would expect that there are some dependencies to other google stuff. Can someone confirm that?
Click to expand...
Click to collapse
----------------------------------------------------------------------
Yes, I wiped cache, dalvik cache, data but I did wipe system either. May be wipe the SYSTEM wasn't such a good idea!
ignore " 4. some google sound cant be saved."
Offline FM radio my favorite apps as you know you don't need internet to listen stations.
You are right , when you swipe down, a percentage value is shown next to the icon but without swipe down you wont able to see percentage value even if you enable it.
I think this rom will be better then pie rom.... Thanks for your time.
Mr.Tom_Tom said:
Yes, please do not use this build as a daily driver yet! But we are happy for every feedback on the test build.
tbd = to be determined = not yet tested
First of all, thanks for testing and providing feedback!
Regarding your comments:
1. Confirm, known issue: checklist working/not working
2. Are you sure you wiped DATA during your first flash? I do not think it is necessary to wipe SYSTEM.
3. Cannot confirm that issue. Icon is present, and when you swipe down, a percentage value is shown next to the icon.
4. Not sure what you mean by that
5. This is by design since Android P, unfortunately. Please see this explanation.
6. I guess You're right
7. Confirm, known issue. (Honestly speaking I was not expecting that someone will miss that FM radio.)
8. I would expect that there are some dependencies to other google stuff. Can someone confirm that?
Click to expand...
Click to collapse
On Android pie, digital wellbeing is not working unless gapps is installed. After installing gapps, digital wellbeing works like a charm. At least on android pie, I can confirm that.
Deleted
Today I took a look at the issue with Digital Wellbeing as reported by @elmxx.
I can confirm the issue - when trying to access Digital Wellbeing through Settings, the app force closes.
Log Cat excerpt:
Code:
10-19 21:47:20.091 19366 19366 D AndroidRuntime: Shutting down VM
10-19 21:47:20.092 19366 19366 E AndroidRuntime: FATAL EXCEPTION: main
10-19 21:47:20.092 19366 19366 E AndroidRuntime: Process: com.google.android.apps.wellbeing, PID: 19366
10-19 21:47:20.092 19366 19366 E AndroidRuntime: java.lang.RuntimeException: java.lang.SecurityException: getUnsuspendablePackagesForUser: Neither user 10100 nor current process has android.permission.SUSPEND_APPS.
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at jex.run(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:883)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:100)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7356)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: Caused by: java.lang.SecurityException: getUnsuspendablePackagesForUser: Neither user 10100 nor current process has android.permission.SUSPEND_APPS.
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:2071)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2039)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1987)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.content.pm.IPackageManager$Stub$Proxy.getUnsuspendablePackagesForUser(IPackageManager.java:7072)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.app.ApplicationPackageManager.getUnsuspendablePackages(ApplicationPackageManager.java:2368)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at bzd.get(PG:1)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at doj.get(PG:10)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at bzb.a(PG:2)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at kik.a(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at kxx.a(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at kxy.run(PG:27)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at laq.run(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at jgl.run(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at jen.run(PG:4)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at java.lang.Thread.run(Thread.java:919)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: Caused by: android.os.RemoteException: Remote stack trace:
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.app.ContextImpl.enforce(ContextImpl.java:1896)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1924)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at com.android.server.pm.PackageManagerService.getUnsuspendablePackagesForUser(PackageManagerService.java:13936)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:3326)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4028)
10-19 21:47:20.092 19366 19366 E AndroidRuntime:
I think the key info here is:
Code:
Neither user 10100 nor current process has android.permission.SUSPEND_APPS
I will look into that in more detail later, but it might be not that simple that there are some GAPPS missing.
Update:
I guess I found a solution, test was successful and submitted a patch already. Problem should be fixed in future builds.
elmxx said:
Offline FM radio my favorite apps as you know you don't need internet to listen stations.
Click to expand...
Click to collapse
As you @elmxx have been the first to provide a detailed feedback I took some time to look after your FM Radio request, see updated post #2. It isn't working perfect as explained here by @NeoArian.
AbdullahSayed said:
What about Z3 Dual support ? Can D6633 users test the rom safely ?
Click to expand...
Click to collapse
Sorry, I have zero experience with the Dual Sim variant, I do not hink it will currently work.
FM Radio
Thanks adding FM Radio app. it works well.
E-mail app. keeps closed. The one "e-mail app" which it comes with lineageos. I just want to let you know.
Thanks for your time.
Thanks for the great work guys! It's awesome to see our shinano getting a 10 build. Will flash ASAP. Keep it up!
elmxx said:
E-mail app. keeps closed. The one "e-mail app" which it comes with lineageos. I just want to let you know.
Click to expand...
Click to collapse
Yes, ignore the LOS email and calender app for the moment, they are buggy but the LOS team is working hard to fix them soon.
Flashing LineageOS rom without Gapps!
I just did flash lineageos rom without flashing Gapps! Here is what I found.......
Every lineageos apps work fine except message app. not getting Text Message Notifications. ------> " google message app works fine".
By the way, May be Gapps beta caused E-mail "keep closed" issue! I am not sure.
C:\adb>fastboot flash recovery TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img
sending 'recovery' (13310 KB)...
OKAY [ 0.687s]
writing 'recovery'...
OKAY [ 0.906s]
finished. total time: 1.594s
fastboot reboot-bootloader
I can not boot in to recovery ?????
Technoolli said:
C:\adb>fastboot flash recovery TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img
sending 'recovery' (13310 KB)...
OKAY [ 0.687s]
writing 'recovery'...
OKAY [ 0.906s]
finished. total time: 1.594s
fastboot reboot-bootloader
I can not boot in to recovery ?????
Click to expand...
Click to collapse
try "fastboot flash FOTAKernel TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img"
(hopefully its twrp 3.3.1 - otherwise download it https://downloads.sourceforge.net/p...-t3981381&ts=1571749352&use_mirror=netcologne )
enter recovery by pressing vol down + power.
---------- Post added at 01:28 PM ---------- Previous post was at 01:25 PM ----------
---------- Post added at 01:25 PM ---------- Previous post was at 01:17 PM ----------
elmxx said:
Thanks adding FM Radio app. it works well.
E-mail app. keeps closed. The one "e-mail app" which it comes with lineageos. I just want to let you know.
Thanks for your time.
Click to expand...
Click to collapse
aaahhhh.. the fm radio... the one least appreciated feature of modern phones.
have you found a way to change stations with the headset button?
nikapos said:
try "fastboot flash FOTAKernel TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img"
(hopefully its twrp 3.3.1 - otherwise download it https://downloads.sourceforge.net/p...-t3981381&ts=1571749352&use_mirror=netcologne )
enter recovery by pressing vol down + power.
---------- Post added at 01:28 PM ---------- Previous post was at 01:25 PM ----------
---------- Post added at 01:25 PM ---------- Previous post was at 01:17 PM ----------
aaahhhh.. the fm radio... the one least appreciated feature of modern phones.
have you found a way to change stations with the headset button?
Click to expand...
Click to collapse
I do not get into recovery like that, fastboot flashing does not work anymore ...
Technoolli said:
I do not get into recovery like that, fastboot flashing does not work anymore ...
Click to expand...
Click to collapse
ok then, start over.
1. flash original .291 rom with flashtool
2. make sure your bootloader is unlocked
3. enter fastboot to flash 3.3.1 twrp recovery to FOTAPartition
4. press power button holding down volume button until you feel one short vibration.
hope this does the trick. however this is not the proper thread to discuss unbricking or installing recoveries.
Thank you, but with the Flashtool I can not select the firmware ... Can I flash it somehow different? I just can not do more in the gas pedal, also I do not come in the recovery or Android system ... help
Hi all,
I have a very strange issue with my Pixel 6 Pro. Not rooted and original Android 13 firmware. The phone reboots whenever I enable the physical SIM or eSim. Then it shows me a screen to reboot or do a factory reset.
If I select the reboot option and keep the SIM enabled, it reboots, loads the UI and whenever the Sim is connected, it reboots again. This keeps going on forever.
After a reboot, when I quickly go to the menu and disable the sim, it will restart one more time and stop restarting after that since the sim is disabled.
Recently, I received the latest Android 13 Security Patch and issue started then (I was already on 13). I had the same issue also when I installed the Android 13 Beta firmware and I even created a bug on Android Beta issue tracker.
See: https://issuetracker.google.com/issues/236862868
Since it took some time before they responded, I went back to the stable 12 and updated to the stable 13 when it came out. I experienced no issues until the latest security patch.
Long story, but I'm just wondering, do you have any ideas what I can try more? Right now, I can't use any mobile services on this phone. Everything, including wifi works fine when the sim is disabled btw.
mrhnn said:
Hi all,
I have a very strange issue with my Pixel 6 Pro. Not rooted and original Android 13 firmware. The phone reboots whenever I enable the physical SIM or eSim. Then it shows me a screen to reboot or do a factory reset.
If I select the reboot option and keep the SIM enabled, it reboots, loads the UI and whenever the Sim is connected, it reboots again. This keeps going on forever.
After a reboot, when I quickly go to the menu and disable the sim, it will restart one more time and stop restarting after that since the sim is disabled.
Recently, I received the latest Android 13 Security Patch and issue started then (I was already on 13). I had the same issue also when I installed the Android 13 Beta firmware and I even created a bug on Android Beta issue tracker.
See: https://issuetracker.google.com/issues/236862868
Since it took some time before they responded, I went back to the stable 12 and updated to the stable 13 when it came out. I experienced no issues until the latest security patch.
Long story, but I'm just wondering, do you have any ideas what I can try more? Right now, I can't use any mobile services on this phone. Everything, including wifi works fine when the sim is disabled btw.
Click to expand...
Click to collapse
Did you buy it on eBay?
FoneWatcher said:
Did you buy it on eBay?
Click to expand...
Click to collapse
No, no. I bought it in the electronics store in Jan-22.
mrhnn said:
No, no. I bought it in the electronics store in Jan-22.
Click to expand...
Click to collapse
I've never used eSIM, but, I looked around & found this:
How to use dual SIMs on your Google Pixel phone - Pixel Phone Help
New to Pixel? Use our setup guide If you have a Pixel 3a or later Pixel phone, you can use two
support.google.com
Namely, have you checked/verified that your carrier(s) allow for Dual-Sim?
Other than that, my only guess is that the phone is SIM locked, but, if you bought it new & the phone is paid off, that can be ruled out.
Thank you. The phone was completely working fine with both eSim as well as with physical SIM.
Right now, it doesn't even matter which sim i choose / enable. Both ways it reboots.
For example: I disable and delete eSim completely and just put in the sim card, phone reboots after connecting to the carrier.
Seems to be an issue with some services on the phone.
I have a logcat from previous error (back in June when i had Android 13 Beta). I will try to get a new logcat with current stable version
Here you can see some fatal errors regarding com.shannon.qualifiednetworksservice
06-23 09:50:38.876 2877 3331 D CellBroadcastConfigService: mAlwaysOn is set to true, enable the range: 4370:4370
06-23 09:50:38.876 2358 2358 I VvmSimStateTracker: android.intent.action.SIM_STATE_CHANGED
06-23 09:50:38.878 3308 3326 E AndroidRuntime: FATAL EXCEPTION: QualifiedNetworksService
06-23 09:50:38.878 3308 3326 E AndroidRuntime: Process: com.shannon.qualifiednetworksservice, PID: 3308
06-23 09:50:38.878 3308 3326 E AndroidRuntime: java.lang.IllegalArgumentException: Source access networks contains unknown. "source=geran|utran|eutran|ngran|iwlan, target=geran|utran|eutran|ngran|iwlan, type=disallowed, capabilities=eims|mms|xcap|cbs"
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.android.internal.telephony.data.DataNetworkController$HandoverRule.<init>(DataNetworkController.java:717)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ConfigurationManager.updateCarrierConfigInfo(ConfigurationManager.java:229)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ConfigurationManager.<init>(ConfigurationManager.java:78)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ShannonQualifiedNetworksService$ShannonNetworkAvailabilityProvider.<init>(ShannonQualifiedNetworksService.java:133)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ShannonQualifiedNetworksService.onCreateNetworkAvailabilityProvider(ShannonQualifiedNetworksService.java:207)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.telephony.data.QualifiedNetworksService$QualifiedNetworksServiceHandler.handleMessage(QualifiedNetworksService.java:222)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
06-23 09:50:38.880 1744 2497 D CompatibilityChangeReporter: Compat change id reported: 184323934; UID 1000; state: ENABLED
06-23 09:50:38.882 1744 3335 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
06-23 09:50:38.882 1744 3306 W ActivityManager: Process com.shannon.qualifiednetworksservice has crashed too many times, killing! Reason: crashed quickly
06-23 09:50:38.883 3308 3326 I Process : Sending signal. PID: 3308 SIG: 9
mrhnn said:
Thank you. The phone was completely working fine with both eSim as well as with physical SIM.
Right now, it doesn't even matter which sim i choose / enable. Both ways it reboots.
For example: I disable and delete eSim completely and just put in the sim card, phone reboots after connecting to the carrier.
Seems to be an issue with some services on the phone.
I have a logcat from previous error (back in June when i had Android 13 Beta). I will try to get a new logcat with current stable version
Here you can see some fatal errors regarding com.shannon.qualifiednetworksservice
06-23 09:50:38.876 2877 3331 D CellBroadcastConfigService: mAlwaysOn is set to true, enable the range: 4370:4370
06-23 09:50:38.876 2358 2358 I VvmSimStateTracker: android.intent.action.SIM_STATE_CHANGED
06-23 09:50:38.878 3308 3326 E AndroidRuntime: FATAL EXCEPTION: QualifiedNetworksService
06-23 09:50:38.878 3308 3326 E AndroidRuntime: Process: com.shannon.qualifiednetworksservice, PID: 3308
06-23 09:50:38.878 3308 3326 E AndroidRuntime: java.lang.IllegalArgumentException: Source access networks contains unknown. "source=geran|utran|eutran|ngran|iwlan, target=geran|utran|eutran|ngran|iwlan, type=disallowed, capabilities=eims|mms|xcap|cbs"
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.android.internal.telephony.data.DataNetworkController$HandoverRule.<init>(DataNetworkController.java:717)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ConfigurationManager.updateCarrierConfigInfo(ConfigurationManager.java:229)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ConfigurationManager.<init>(ConfigurationManager.java:78)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ShannonQualifiedNetworksService$ShannonNetworkAvailabilityProvider.<init>(ShannonQualifiedNetworksService.java:133)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at com.shannon.qualifiednetworksservice.ShannonQualifiedNetworksService.onCreateNetworkAvailabilityProvider(ShannonQualifiedNetworksService.java:207)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.telephony.data.QualifiedNetworksService$QualifiedNetworksServiceHandler.handleMessage(QualifiedNetworksService.java:222)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
06-23 09:50:38.878 3308 3326 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
06-23 09:50:38.880 1744 2497 D CompatibilityChangeReporter: Compat change id reported: 184323934; UID 1000; state: ENABLED
06-23 09:50:38.882 1744 3335 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
06-23 09:50:38.882 1744 3306 W ActivityManager: Process com.shannon.qualifiednetworksservice has crashed too many times, killing! Reason: crashed quickly
06-23 09:50:38.883 3308 3326 I Process : Sending signal. PID: 3308 SIG: 9
Click to expand...
Click to collapse
Hi,
I just curious to you solved or not this issue, beauce i have the same problem et its really interesting. I tried lots of things but not working
akbulut00 said:
Hi,
I just curious to you solved or not this issue, beauce i have the same problem et its really interesting. I tried lots of things but not working
Click to expand...
Click to collapse
Hi, yes I solved it by changing the phone language from Turkish to English.
Steps:
Turn on the phone and as soon as you see the menu, turn on airplane mode (disable all networking options)
Phone will reboot again but since airplane mode is active, phone services will not be activated
Once the phone stops rebooting, change the language to English.
Just to make sure, reboot the phone with the new language.
Turn off airplane mode
Let me know if this works for you as well!
mrhnn said:
Hi, yes I solved it by changing the phone language from Turkish to English.
Steps:
Turn on the phone and as soon as you see the menu, turn on airplane mode (disable all networking options)
Phone will reboot again but since airplane mode is active, phone services will not be activated
Once the phone stops rebooting, change the language to English.
Just to make sure, reboot the phone with the new language.
Turn off airplane mode
Let me know if this works for you as well!
Click to expand...
Click to collapse
i realized to not completed security update, now im installing it. I will try again after completed.
i ll tell you the resault.
akbulut00 said:
i realized to not completed security update, now im installing it. I will try again after completed.
i ll tell you the resault.
Click to expand...
Click to collapse
Dissolved. The problem was the incomplete update.
sagolasin yine de