I am not a copyright lawyer, so I don't know, if this question is allowed or not. If not: would some friendly mod delete my thread without being angry to me?
In some donut builds, the pdf-viewer is included:
http://db.androidspin.com/android_build_information.asp
I downloaded some of them but when I unzipped them, I could not find any pdf-viewer app nor lib. Where is this hidden and what do I have to backup, to run the viewer on other donut build?
Thanks for you help. I really like the donut builds like cyans, but without pdf, it sucks. I backed up my pdf-viewer from earlier cm-builds (before 4.1.99) but didn't get them to work.
Did you ever get an answer to this? As you said, the PDF reader I had installed for Cupcake doesn't work at all in the latest cyan ROM (here's the logcat):
Code:
I/ActivityManager( 138): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.htc.pdfreader/.ActPDFReader }
I/ActivityManager( 138): Start proc com.htc.pdfreader for activity com.htc.pdfreader/.ActPDFReader: pid=636 uid=10116 gids={1015}
I/ActivityThread( 636): Publishing provider com.htc.pdfreader.PdfSuggestionProvider: com.htc.pdfreader.PdfSuggestionProvider
D/dalvikvm( 636): Trying to load lib /system/lib/libpdfreader.so 0x438cf988
I/dalvikvm( 636): Unable to dlopen(/system/lib/libpdfreader.so): Cannot load library: reloc_library[1172]: 121 cannot locate 'FT_Get_Glyph'...
W/dalvikvm( 636): Exception Ljava/lang/UnsatisfiedLinkError; thrown during Lcom/htc/pdfreader/JNIHost;.<clinit>
D/AndroidRuntime( 636): Shutting down VM
W/dalvikvm( 636): threadid=3: thread exiting with uncaught exception (group=0x4001e1c0)
E/AndroidRuntime( 636): Uncaught handler: thread main exiting due to uncaught exception
Looks like the problem is in libpdfreader.so not working with Donut.
no, I never got an answer. But I found that quickoffice worked well. Just do a search for eclair or android 2.0 here ... there are some threads where you can download and adb push quickoffice.
Hope this helps.
I tried moving a pdfreader.apk and a libpdfreader.so from a cupcake build to the latest cyanogen rom and it didn't work well :/ I got the app to install after i signed it but it force closes when I try to open it. Does anyone have a good non-wares pdf viewer that works on donut?.. Or found a way to have the htc pdfviewer to work?
Hi, guys. I am having some troubles with the MIUI rom and the application "Cardiotrainer" because of a class that crashes in miui. I sent a message to a couple of admins of the miui main page, and also posted a couple of threads in the miui developers forum, but I had no response of any of the messages. I hope you can help me. I attach the last message I sent:
Hi. I sent you a message a couple of days ago, but I suppose it was deleted when the server failed. I hope you can help me, because I can't read chinese, so I can only read what google can translate hehehehe. First of all I would like to thank all the miui staff because of their great job. I like miui much more than any other rom, but since some versions ago I am having troubles with an application.
When I go running, I use the "Cardiotrainer" application, but since some versions ago, when I select some versions of the settings menu (all of them that display another submenu) the program crashes. It only happens with miui, so it's a rom problem. I read the crash log and I suppose the problem is becaus a NullPointerException in the PreferenceActivity class. Anyway I attach the crash error just in case it's helpful.
Code:
ERROR REPORT
Report type
Crash
Package name
com.wsl.CardioTrainer
Package version
63
Package version name
3.4.1
Installed by
com.google.android.feedback
Process name
com.wsl.CardioTrainer
Time
wednesday 22 december 2010
System app
false
SYSTEM
Device
passion
Build id
MIUI.0.12.11
Build type
userdebug
Model
Nexus One
Product
libra_passion
SDK version
8
Release
2.2.1
Incremental version
0.12.11
Codename
REL
Board
mahimahi
Brand
generic
Running applications
com.google.android.feedback
com.android.inputmethod.latin
com.android.providers.calendar
android.process.acore
com.google.process.gapps
com.android.phone
system
com.google.android.googlequicksearchbox
android.process.media
com.android.vending
com.svox.pico
com.android.voicedialer
com.noshufou.android.su
com.android.defcontainer
com.cooliris.media
com.google.android.apps.mapsocationFriendService
com.android.vending.updater
com.android.launcher
com.android.updater
com.miui.player
com.google.android.apps.uploader
com.twitter.android
(sorry, but it's quite impossible to copy the logs )
CRASH
Exception class name
java.lang.NullPointerException
Source file
PreferenceActivity.java
Source class
android.preference.PreferenceActivity
Source method
bindPreferences
Line number
247
Stack trace
java.lang.NullPointerException
at android.preference.PreferenceActivity.
bindPreferences(PreferenceActivity.java:247)
at android.preference.PreferenceActivity.
access$000(PreferenceActivity.java:86)
at android.preference.
PreferenceActivity$1.handleMessage(PreferenceActivity.java:109)
at android.os.Handler.
dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.
main(ActivityThread.java:4627)
at java.lang.reflect.Method.invokeNative(NativeMethod)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.
ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
at com.android.internal.os.ZygoteInit.
main(ZygoteInit.java:626)
at dalvik.system.NativeStart.main(NativeMethod)
I hope with this information the problem can be solved. Thanks for your time.
Click to expand...
Click to collapse
+1
I am also using CardioTrainer on a MIUI ROM and it always crashes in settings :'(
I also have a similar problem with the Youversion Bible app. The tech support guys there reported that this is common problem with different apps in MIUI as MIUI has some "different structure" of handling settings. When pressing settings, the app crashes.
Here's my log:
processName:com.sirma.mobile.bible.android
pid:12915
uid:10072
tag:null
shortMsg:java.lang.NullPointerException
longMsg:java.lang.NullPointerException
stackTrace:java.lang.NullPointerException
at android.preference.PreferenceActivity.bindPreferences(PreferenceActivity.java:247)
at android.preference.PreferenceActivity.access$000(PreferenceActivity.java:86)
at android.preference.PreferenceActivity$1.handleMessage(PreferenceActivity.java:109)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4628)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:870)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:628)
at dalvik.system.NativeStart.main(Native Method)
Click to expand...
Click to collapse
I have MIUI 1.3.5 on the Sprint EVO, but I believe this is a general MIUI problem, so posting here.
Dear developers,
Considering Android 4.4.3 is now available in AOSP, when can we expect to get nightlies based on it?
Thanks!
Answered in the FAQ: http://forum.xda-developers.com/showthread.php?t=2738971
PonsAsinorem said:
Answered in the FAQ: http://forum.xda-developers.com/showthread.php?t=2738971
Click to expand...
Click to collapse
I hope we can use android 4.4.3 ASAP on galaxy s2.
I made a homemade Build for Tab 2,
Code:
I/CameraService( 117): CameraService started (pid=117)
I/SurfaceFlinger( 114): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
I/CameraService( 117): Loaded "Espresso Camera Wrapper" camera module
V/CameraWrapper( 117): camera_get_number_of_cameras
V/CameraWrapper( 117): check_vendor_module
E/HAL ( 117): load: module=/system/lib/hw/vendor-camera.piranha.so
E/HAL ( 117): dlopen failed: cannot locate symbol "FindSection" referenced by "vendor-camera.piranha.so"...
E/CameraWrapper( 117): failed to open vendor camera module
camera isn´t working there.
Full logcat: http://pastebin.com/gCtfG2aH
Meight also happen on other devies.
patrickph said:
I hope we can use android 4.4.3 ASAP on galaxy s2.
Click to expand...
Click to collapse
Now available.
http://dl.omnirom.org/i9100/omni-4.4.3-20140606-i9100-NIGHTLY.zip
Hello xposed devs and @rovo89!
I tested my modules on Lollipop and I got this strange error: "Class not found using the boot class loader; no stack available".
Full error looks like this one: http://forum.xda-developers.com/showpost.php?p=58836010&postcount=613
Not sure if this is XposedBridge bug (new API will fix it?) or we should fix it on our side. Any solution?
Edit: Rovo89 gave us solution, read here: http://forum.xda-developers.com/xposed/xposed-api-changelog-developer-news-t2714067#post58840569
Are you sure it's the same class on Lollipop?
Modules targeting the system behavior might need to be adjusted to the new Android framework code, which isn’t caused by ART, but simply by architecture and code changes that happen between any two Android releases. The most significant one is that the code for system services has been moved to a separate file. For most of the affected modules, this can be solved by a little refactoring (moving code to a different place).
Click to expand...
Click to collapse
Looks like it still same in Lollipop
https://github.com/android/platform.../android/server/pm/PackageManagerService.java
com.android.server.pm.PackageManagerService
There's nothing in that error about PackageManagerService. Also, considering that user is running CM12 and not AOSP, you might want to check the CM12 source anyway.
Just wrote this: http://forum.xda-developers.com/xposed/xposed-api-changelog-developer-news-t2714067#post58840569
rovo89 said:
Just wrote this: http://forum.xda-developers.com/xposed/xposed-api-changelog-developer-news-t2714067#post58840569
Click to expand...
Click to collapse
Thank you so much! Very useful info for all xposed module devs
Moto x ghost
running AL 5.0.2 custom rom (AICP) made out of CM12
no boot loop
xposed works fine
flashed with twrp-2.8.4.0
smohanv said:
Moto x ghost
running AL 5.0.2 custom rom (AICP) made out of CM12
no boot loop
xposed works fine
flashed with twrp-2.8.4.0
Click to expand...
Click to collapse
You are off topic..
pyler said:
You are off topic..
Click to expand...
Click to collapse
You are right.. It is off topic.. Meant to post in xposed framework forum.. Sorry mate... Thanks for pointing..
rovo89 said:
Just wrote this: http://forum.xda-developers.com/xposed/xposed-api-changelog-developer-news-t2714067#post58840569
Click to expand...
Click to collapse
I already had my intercept in handleLoadPackage looking for package "android" and it worked previously, but for some reason it doesn't intercept this package in Lollipop.
My code is:
Code:
if (lpparam.packageName.equals("android")) {
XposedBridge.log("htccarxposed: Hooked into Android Policy!");
Log.i("htccarxposed","Hooked into Android Policy.");
And neither do I see the log flag nor is any of the hooking working.
The "Log" feature in the Xposed Installer app only shows the "Xposed" tag for ADB logs, not any of my log calls, btw, and I can't see anything there about the boot class loader.
Edit: Correction, I found this error:
Code:
02-14 20:26:09.992 E/Xposed ( 476): Caused by: java.lang.NoClassDefFoundError: Class not found using the boot class loader; no stack available
02-14 20:26:10.032 E/Xposed ( 476): java.lang.NoSuchMethodError: com.android.server.pm.PackageManagerService#grantPermissionsLPw(android.content.pm.PackageParser.Package,boolean)#exact
02-14 20:26:10.032 E/Xposed ( 476): at de.robv.android.xposed.XposedHelpers.findMethodExact(XposedHelpers.java:179)
02-14 20:26:10.032 E/Xposed ( 476): at de.robv.android.xposed.XposedHelpers.findAndHookMethod(XposedHelpers.java:129)
02-14 20:26:10.032 E/Xposed ( 476): at de.robv.android.xposed.mods.appsettings.hooks.PackagePermissions.initHooks(PackagePermissions.java:59)
02-14 20:26:10.032 E/Xposed ( 476): at de.robv.android.xposed.mods.appsettings.XposedMod.initZygote(XposedMod.java:297)
02-14 20:26:10.032 E/Xposed ( 476): at de.robv.android.xposed.XposedBridge.loadModule(XposedBridge.java:469)
02-14 20:26:10.032 E/Xposed ( 476): at de.robv.android.xposed.XposedBridge.loadModules(XposedBridge.java:418)
02-14 20:26:10.032 E/Xposed ( 476): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:105)
I have small problem...
I need to get (find) class SubSettings.
https://github.com/android/platform...ter/src/com/android/settings/SubSettings.java
My code:
https://github.com/pylerSM/XInstaller/blob/master/src/com/pyler/xinstaller/XInstaller.java#L1008
So if use param.getClass().getClassLoader() as class loader, I get "Class not found using the boot class loader; no stack available". Same story if I use "null" as class loader.
Any advice?
This ROM has gone "Alpha" and is basically ready for daily use https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571 or you could also check ResurrectionRemix at https://forum.xda-developers.com/dr...resurrectionremix-nougat-xt907-xt905-t3697567
See the following post for the current status of this experimental build.
https://forum.xda-developers.com/showpost.php?p=74272802&postcount=59
all the below is regarding previous build attempts
DO NOT FLASH GAPPS!
Make a nandroid (you will definitely be going back) And remember, a nandroid is NOT 100%! if you don't understand this, maybe trying this is not for you.
Flash the ZIP
It is unrooted, so I personally flash Magisk v12 (I have the zip and know its working). I also flash UnSu and Busybox remover
DO NOT FLASH GAPPS!
Reboot
Install the Magisk Manager (if you went down this path for root)
This is an experimental build of crDroid 7.1.2
The good
It's crDroid!
It's Nougat!
It Builds
It Boots!:highfive:
It has all the eyecandy!:angel:
It feels really "snappy"
The bad
If you flash Gapps it falls to pieces in a never ending cycle of crashes!:crying:
It is buggy even without GApps
My Hopes:
People will flash this, get some logs and maybe someone with more knowledge (maybe the xt897 LOS device maintainers?) will be able to decipher the logs and determine whats missing. Maybe someone here has a direct line to one of the maintainers of the xt897 LineageOS?
How I built it:
Set up a virtual Box (on Win7 64b) to build Lineage OS 14.1 (followed their instructions)
Source: https://github.com/crdroidandroid/android -b 7.1
I used a working device tree (ie local manifest) from my working LineageOS 14.1 Build machine (see attached) for an XT897 (with the touch drivers for an XT907)
Basically, I have done no "magic" here, it all just kinda worked. up to a point as its pretty buggy. BUT IT BOOTS!
I also have a ResurrectionRemix 7.1.2 I will also upload.
Almost forgot, flash this at your own risk and i take no responsibility for what happens to your device.
DiamondJohn said:
DO NOT FLASH GAPPS!
Click to expand...
Click to collapse
Since GApps seem to be the only limiting factor, did you try the various available flavors of GApps?
Also, there's one more alternate to GApps, which is the microg project. Did you try that instead? There's an unofficial flashable installer available here but that page also has links to the various components if you wish to install those manually...
rahimali said:
Since GApps seem to be the only limiting factor, did you try the various available flavors of GApps?
Also, there's one more alternate to GApps, which is the microg project. Did you try that instead? There's an unofficial flashable installer available here but that page also has links to the various components if you wish to install those manually...
Click to expand...
Click to collapse
I tried Open (Pico) & Beans from memory.
I think the real answer will be to look into the logs. The very first build I did I got ADB over WiFi turned on before it all went bad, so have a catlog of the SystemUI crashes, but it was an earlier build , and its from ResurectionRemix
I think this is the smoking gun:
Code:
07-19 20:14:36.665 5929 5929 D AndroidRuntime: Shutting down VM
07-19 20:14:36.669 5929 5929 E AndroidRuntime: FATAL EXCEPTION: main
07-19 20:14:36.669 5929 5929 E AndroidRuntime: Process: com.android.systemui, PID: 5929
[COLOR="Red"][B]07-19 20:14:36.669 5929 5929 E AndroidRuntime: java.lang.NoClassDefFoundError: Failed resolution of: Lcom/android/keyguard/R$bool;
[/B][/COLOR]07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.keyguard.KeyguardUpdateMonitor.shouldListenForFingerprint(KeyguardUpdateMonitor.java:1199)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.keyguard.KeyguardUpdateMonitor.updateFingerprintListeningState(KeyguardUpdateMonitor.java:1186)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.keyguard.KeyguardUpdateMonitor.<init>(KeyguardUpdateMonitor.java:1177)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.keyguard.KeyguardUpdateMonitor.getInstance(KeyguardUpdateMonitor.java:993)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.systemui.keyguard.KeyguardViewMediator.setupLocked(KeyguardViewMediator.java:683)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.systemui.keyguard.KeyguardViewMediator.start(KeyguardViewMediator.java:735)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.systemui.SystemUIApplication.startServicesIfNeeded(SystemUIApplication.java:180)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.systemui.SystemUIApplication.startServicesIfNeeded(SystemUIApplication.java:134)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.systemui.keyguard.KeyguardService.onCreate(KeyguardService.java:45)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:3231)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at android.app.ActivityThread.-wrap5(ActivityThread.java)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1597)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6236)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:891)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:781)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: Caused by: java.lang.ClassNotFoundException: Didn't find class "com.android.keyguard.R$bool" on path: DexPathList[[zip file "/system/priv-app/SystemUI/SystemUI.apk"],nativeLibraryDirectories=[/system/priv-app/SystemUI/lib/arm, /system/lib, /vendor/lib, /system/lib, /vendor/lib]]
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at java.lang.ClassLoader.loadClass(ClassLoader.java:380)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: ... 18 more
07-19 20:14:36.672 2801 3134 W ActivityManager: Process com.android.systemui has crashed too many times: killing!
07-19 20:14:36.673 2801 3134 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:877 com.android.server.am.AppErrors.crashApplicationInner:375 com.android.server.am.AppErrors.crashApplication:309 com.android.server.am.ActivityManagerService.handleApplicationCrashInner:13757 com.android.server.am.ActivityManagerService.handleApplicationCrash:13739
wierd, I just reflashed the ROM and it wasn't anywhere near as stable as it was the first time I flashed it
DiamondJohn said:
wierd, I just reflashed the ROM and it wasn't anywhere near as stable as it was the first time I flashed it
Click to expand...
Click to collapse
I took a big batch of logs, read them (as much as you can with that amount of crashes), did some MAJOR changes (but "impolite" and took some major shortcuts though not so quick to actually do), and now its a LOT more stable, and I even managed to install and boot with GApps, connect to the market and download a couple of apps. :highfive::victory: But don't get me wrong, it still crashes like a &@%#$
ie there are still "some" force closes
I'm moving off of this one (ie crDroid) and give ResurrectionRemix a similar "attack " :fingers-crossed: On previous attempts/builds it acted the same as crDroid, but much worse.
But most importantly, my phone is on the fritz and I think (ie hope thats it's only:fingers-crossed the recovery image is corrupt
{
"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"
}
i flashed crrdroid for the xt907 and first boot it works like a charm but when u reboot it it goes bonkers and endless force closes
i hope u can get this stable because i have crdroid installed on all of my devices my favorite nougat rom
I hope someone can keep the development going for this ROM for the xt907
my last build available in post #3 that I managed to get to work with GApps / Google play
hmmm... I'm giving it another go to get some logs and it actually seems MORE stable after a few wipes of dalvik and cache...
Can't install apps package installer force closes as well as the keyboard ?
Trey n said:
Can't install apps package installer force closes as well as the keyboard ?
Click to expand...
Click to collapse
Tell me something I dont know!
I have found its a bit of a random number generator, in that sometimes I flash and the FC's are MANY times less and others much more. But generally speaking, the faster you set the device up, the more chance you have. Also, when it starts to fail, go to recovery and clean cache and dalvik. Also delete /system/priv-app/OmniSwitch & /syatem/app/NFC/
I kicked off a new build and flashed it. As part of the build, I undid my "hacky" changes which seemed to improve stability (orig didnt allow GApps), and refreshed all crDroid code to source. I found that the new build was almost as stable as my modified build. ie as crDroid fixes bugs for their official devices, our unofficial build inherits these fixes and also becomes more stable :highfive:. So, hopefully as their builds become more mature, we may end with a stable build as well. This state of affairs (ie pure crDroid code) is the best situation / goal.
I also trued flashing (and building) one of their official devices (a Nexus 5 / hammerhead). I found that there were a number of issues even in the official builds. For example, I found that OmniSwitch caused a number of force closes in my build. In the official Nexus 5 build, although it didnt force close, it didn't actually work. ie there is work to be done in Omniswitch, which we will inherit. I also found that the official build din't have working Lockscreen album art nor music visualiser. So there is clearly a lot of coding ahead for crDroid; which again, we will inherit.
Also the more I think about it, we are more stable without GApps, and its nowhere near a daily yet, so I am seeing it more and more as a preview / test that we may have a very customizable Nougat ROM for our phones (in the future :fingers-crossed
I also noriced that for our screen resolution, the code falls back to the old B/W bootanimiation instead of the newer one. That wont do for my builds in the future
I would suggest that if anyone is really interested to see this ROM "running" and its features, then do not flash GApps; its simply a preview of what is hopefully to come.
On a side, does anyone know of a free, non registration, low advertising, fast to upload(the ones i found take 4Hrs to upload!) hosting website I can post future builds onto?
I think I will also generate a pure xt897 build to hopefully garner some interest by other devs, as the xt897 is an official LineageOS device, which is the vendor and device tree I am using to build crDroid (and ResurectionRemic and possibly other LOS based custom ROMs)
DiamondJohn said:
Tell me something I dont know!
I have found its a bit of a random number generator, in that sometimes I flash and the FC's are MANY times less and others much more. But generally speaking, the faster you set the device up, the more chance you have. Also, when it starts to fail, go to recovery and clean cache and dalvik. Also delete /system/priv-app/OmniSwitch & /syatem/app/NFC/
I kicked off a new build and flashed it. As part of the build, I undid my "hacky" changes which seemed to improve stability (orig didnt allow GApps), and refreshed all crDroid code to source. I found that the new build was almost as stable as my modified build. ie as crDroid fixes bugs for their official devices, our unofficial build inherits these fixes and also becomes more stable :highfive:. So, hopefully as their builds become more mature, we may end with a stable build as well. This state of affairs (ie pure crDroid code) is the best situation / goal.
I also trued flashing (and building) one of their official devices (a Nexus 5 / hammerhead). I found that there were a number of issues even in the official builds. For example, I found that OmniSwitch caused a number of force closes in my build. In the official Nexus 5 build, although it didnt force close, it didn't actually work. ie there is work to be done in Omniswitch, which we will inherit. I also found that the official build din't have working Lockscreen album art nor music visualiser. So there is clearly a lot of coding ahead for crDroid; which again, we will inherit.
Also the more I think about it, we are more stable without GApps, and its nowhere near a daily yet, so I am seeing it more and more as a preview / test that we may have a very customizable Nougat ROM for our phones (in the future :fingers-crossed
I also noriced that for our screen resolution, the code falls back to the old B/W bootanimiation instead of the newer one. That wont do for my builds in the future
I would suggest that if anyone is really interested to see this ROM "running" and its features, then do not flash GApps; its simply a preview of what is hopefully to come.
On a side, does anyone know of a free, non registration, low advertising, fast to upload(the ones i found take 4Hrs to upload!) hosting website I can post future builds onto?
I think I will also generate a pure xt897 build to hopefully garner some interest by other devs, as the xt897 is an official LineageOS device, which is the vendor and device tree I am using to build crDroid (and ResurectionRemic and possibly other LOS based custom ROMs)
Click to expand...
Click to collapse
AWESOME time will tell
and i have noticed that bootanimation too and i hate it i love the new one
and u could upload it to ur google drive and share the file ..........
Trey n said:
AWESOME time will tell
and i have noticed that bootanimation too and i hate it i love the new one
and u could upload it to ur google drive and share the file ..........
Click to expand...
Click to collapse
Google drive not an option. Any other ideas?
DiamondJohn said:
Google drive not an option. Any other ideas?
Click to expand...
Click to collapse
Y not?
Onedrive
Dropbox
Mediafire
Mega
also see the second half of this post https://forum.xda-developers.com/showpost.php?p=73211646&postcount=79
I also just found the following post of a user having what appears to be the exact same issues with LineageOS 14.1, when they install GApps
https://forum.xda-developers.com/droid-razr-m/development/lineage-os-xt907jbbl-t3577746/post72841480
Its a pity they dont have an xt897 so that they could post an issue/bug directly with LineageOS
Bad news all I had a chance to flash a build and actually take the logs, ie on top of all the logs you guys posted... NOT!
Anyway, in short, we are getting "GPU Page Faults" in the kernel. The GPU is Graphics Processing Unit, which would explain the systemUI crashes. The bad news is that I looked at our kernel code and compared it to another device which does work, and our kernel code is way behind. eg hammerhead code file on the line that logs the error is 2000 lines, ours is only 1000 lines.
I tried slowly updating more and more of our kernel, but each file I brought up to newer code triggered a dependency on another 2 files, and that file triggered a dependency on another few files. as you can imaging it got out of hand very quickly.
So, unless LineageOS does some major changes to their kernel, I don't think we are going to be running a heavily customised ROM too soon.:crying:
I also tried AICP just in case it was compatible with our "old" kernel, but no.All nougat of course,
I also have tried ResruectionRemix, also no.
Also tried DirtyUnicorns, which is an AOSP based ROM (instead of LiineageOS based like the rest) and that also has kernel issues.It doesn't even show the boot animation. Boot loop All of these require mods to make them compatible with their specific build process ie time :angel
I have compiled and have a working ResurectionRemix marshmallow.:good:
I have spent a lot of time trying to update our kernel, but failed every time or just got overwhelmed with the amount of change required
Lineage does do minor fixes to their Kernel, but most I have seen have been stability around the file system and not the display/GPU; where our problem is.
Additionally, the kernel code is shared between JBBL and KKBL, so I very much doubt we would have any better success with a KKBL ROM.
Why not stick to MM ROMs for now? Could you try and build a few for KKBL and/or JBBL? MM should be good enough for now on these devices and building these should give you the necessary exposure and experience to move ahead to N in the future. Just my thoughts tho m not a dev
DiamondJohn said:
I have compiled and have a working ResurectionRemix marshmallow.:good:
Click to expand...
Click to collapse
And where might I be able to obtain this?
rahimali said:
Why not stick to MM ROMs for now? Could you try and build a few for KKBL and/or JBBL? MM should be good enough for now on these devices and building these should give you the necessary exposure and experience to move ahead to N in the future. Just my thoughts tho m not a dev
Click to expand...
Click to collapse
Because Nougat is newer! Building M will not give the depth of experience needed to rebuild the kernel.
I am currently running as my daily, a custom build of LOS 13.0 (with a heap of Xposed modules). The custom build is basically a de-bloated MM with the Nougat Kernel overclocked to 1.98GHz. I compiled a RR marshmallow (with the OC'd N kernel), but during my install I noticed it had a bug whereby all my restored messages returned to being unread after every reboot. Should be an easy fix, but still a fix to be built and tested. The idea of compiling RR was to remove the need for Xposed.
After this experience, I realised that the LOS MM ROM with Xposed was pretty good, until I get N running...
NB: LOS13 has not had many code changes since they switched to Nougat. Hence my use of the Nougat kernel AND the fact their official xt897 builds should be pretty close to mine (apart from the kernel & OC)
I am guessing that noone rememebrs or tried the following. But, if you flashed the ROM and GApps, and then when it booted, NOT TOUCH the screen, did it fail / crash?
I ask because I have been working on trying to update the kernel, and after many many MANY attempts, I got one to build , flash and boot, but the touch screen drivers are not right, so the touchscreen does not work. But there is also not any force closes popping up. So I am wondering if I have solved the force closes or if it takes touching the screen to trigger their start?