Database Info

Converting a Dream ROM for 32B - JACxHERO - can anyone (particularly dazcox51) help?

I'm trying to get JACxHERO 1.1 from over on the Dream boards running on my 32B. So I've been trying to follow the procedure that dazcox51 described in his post below
http://forum.xda-developers.com/showthread.php?t=539052
(for those who can't be bothered to take the jump, it's basically a case of unpacking the boot.img, renaming init.trout.rc to init.sapphire.rc, and then packing it all up again, resigning the update.zip, and flashing)
I've managed to flash, it starts to boot - and then I get a reboot loop.
Logcat shows the following. There's more, but I think the pertinent part is:
Code:
I/SystemServer( 137): Starting NetStat Service.
I/SystemServer( 137): Starting Connectivity Service.
W/dalvikvm( 137): threadid=23: thread exiting with uncaught exception (group=0x4000fe70)
E/AndroidRuntime( 137): Uncaught handler: thread ConnectivityThread exiting due to uncaught exception
E/AndroidRuntime( 137): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 137): java.lang.NullPointerException
E/AndroidRuntime( 137): at android.app.ActivityThread.getProvider(ActivityThread.java:3689)
E/AndroidRuntime( 137): at android.app.ActivityThread.acquireProvider(ActivityThread.java:3718)
E/AndroidRuntime( 137): at android.app.ApplicationContext$ApplicationContentResolver.acquireProvider(ApplicationContext.java:1473)
E/AndroidRuntime( 137): at android.content.ContentResolver.acquireProvider(ContentResolver.java:576)
E/AndroidRuntime( 137): at android.content.ContentResolver.query(ContentResolver.java:144)
E/AndroidRuntime( 137): at android.provider.Settings$NameValueCache.getString(Settings.java:472)
E/AndroidRuntime( 137): at android.provider.Settings$Secure.getString(Settings.java:1759)
E/AndroidRuntime( 137): at android.provider.Settings$Secure.getInt(Settings.java:1799)
E/AndroidRuntime( 137): at com.android.server.ConnectivityService.getPersistedNetworkPreference(ConnectivityService.java:186)
E/AndroidRuntime( 137): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:127)
E/AndroidRuntime( 137): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:51)
E/AndroidRuntime( 137): at com.android.server.ConnectivityService$ConnectivityThread.run(ConnectivityService.java:91)
Does anyone have any bright ideas?
There is more, but unfortunately the board won't let me post it. I'll put it in a second post, just in case it's relevant.

It's not letting me post the entire logcat, it tells me the post is too long. I'm pretty sure I've got the relevant bit. If anyone wants the whole thing, drop me a PM and I'll mail it. To be it looks network related but must confess I'm just fumbling around here.

Just out of curiosity, I flashed the original Dream ROM without changing it. I got the same reboot loop so I think I'm missing something fundamental and/or obvious.

Am no geewiz as this stuff but have you tried using the kernel from the existing hero roms and use it for the jacxhero port?

If its happening even with an untouched download i think you downliad is bad.
If your on osx did you replace cpio maybe that codrupted some files?
Ive tried all the drizzy/jacxhero releases with no issues

bhav007 said:
Am no geewiz as this stuff but have you tried using the kernel from the existing hero roms and use it for the jacxhero port?
Click to expand...
Click to collapse
I think I will try that as an experiment, but I don't really want to do that as a "release" ROM, as the whole point of this is to see if we can get a decent Compcached version of Hero running on the Magic. If I just whack in (for example) Qtek's boot.img I suspect that, if it worked, we'd end up with a ROM that has the same shortcomings (i.e. unreliable texts due to memory shortages, and a kernel that runs Compcache slower than a swap!).

dazcox5181 said:
If its happening even with an untouched download i think you downliad is bad.
If your on osx did you replace cpio maybe that codrupted some files?
Ive tried all the drizzy/jacxhero releases with no issues
Click to expand...
Click to collapse
Yep, on OSX but did replace cpio. Brand new SD card, 8Gb class 6, partitioned with the latest Amon Ra recovery image.
Will try a new download but I'd be surprised if it was that, because I can unzip/rezip it all just fine.

I don't believe this - it looks like it's my new SD card. Qtek's ordinarily working ROM dies with the same error (albeit before it gets to the Hero loading screen) if I try to boot it with that card in. Have tried with a single fat32 partition and also with the usual three partitioned fat32/ext2/swap scenario.
The card seems to work fine plugged into my Mac and also from within the recovery image on the Magic. I think I'll start a new thread on this as it has naff all to do with JACxHERO it seems.

[Q] Why the phone always restart?

Hello, everybody. I am a developer from Giayee ( Android Phone OEM/ODM ). We are now designed an android phone for a client. I come accross a difficult problem during developing. Our phone always restart from android logo after running for a few hours. And the log is:
E/dalvikvm-heap( 933): 28900-byte external allocation too large for this processE/ ( 933): VM won't let us allocate 28900 bytes
D/skia ( 933): --- decoder->decode returned false
...
E/AndroidRuntime( 933): android.view.InflateException: Binary XML file line #123: Error inflating class java.lang.reflect.Constructor
...
Please help me analyze this log. Thanks! Waiting for your answers, thanks!!!

First things first:
-hardware of the phone?
-which firmware version are you running?
Are you using modded rom?
Regards

[2Problems] Need Help with ActivityTrigger and libbltsville_cpu

Hey Guys,
i tried to port the ICS to the 3D MAX like eklovya =)
but i still hangs on to problems, maybe anybody can help me.
First problem i have is the libbltsville_cpu.so, there is in /vendor/lib
01-01 00:29:34.773: D/skia(667): SkGraphics::Init() - BLTsville (CPU) dlopen() or dlsym() failed - Cannot load library: get_lib_extents[749]: 667 - libbltsville_cpu.so is not a valid ELF object
and my second problem is
01-01 00:29:34.914: E/JNIHelp(667): Native registration unable to find class 'com/android/internal/app/ActivityTrigger', aborting
01-01 00:29:34.914: A/libc(667): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
can anybody help me =)

MasterTobi said:
Hey Guys,
i tried to port the ICS to the 3D MAX like eklovya =)
but i still hangs on to problems, maybe anybody can help me.
First problem i have is the libbltsville_cpu.so, there is in /vendor/lib
01-01 00:29:34.773: D/skia(667): SkGraphics::Init() - BLTsville (CPU) dlopen() or dlsym() failed - Cannot load library: get_lib_extents[749]: 667 - libbltsville_cpu.so is not a valid ELF object
and my second problem is
01-01 00:29:34.914: E/JNIHelp(667): Native registration unable to find class 'com/android/internal/app/ActivityTrigger', aborting
01-01 00:29:34.914: A/libc(667): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
can anybody help me =)
Click to expand...
Click to collapse
ok fixxed but i stuck on this error -.-
Native registration unable to find class 'com/android/internal/os/RuntimeInit', aborting
but the runtimeinit is still exist -.-.-.-.-.-

Next Try
ok in the BOOTCLASSPATH is existing the framework2. Must i add the RuntimeInit to framework2 and framework ?

[Completed] The new Pixel Launcher crashing on 5.0.2

I've got a problem with the new pixel launcher, whenever i launch it it will immediately crash and delete default launcher preferences. I pluged the phone to my computer and try to launch it with android monitor in andoid studio. I get the following error:
Code:
E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.google.android.apps.nexuslauncher, PID: 6087
java.lang.NoSuchMethodError: No virtual method getColor(I)I in class Lcom/android/launcher3/Launcher; or its super classes (declaration of 'com.android.launcher3.Launcher' appears in /data/app/com.google.android.apps.nexuslauncher-1/base.apk)
at com.android.launcher3.allapps.AllAppsTransitionController.<init>()
at com.android.launcher3.Launcher.onCreate()
at android.app.Activity.performCreate(Activity.java:5976)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1105)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2251)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2358)
at android.app.ActivityThread.access$800(ActivityThread.java:144)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1278)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5219)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
Any idea how to fix this?

The Pixel Launcher will only work on Android 6.0+ devices

Trafalgar Square said:
The Pixel Launcher will only work on Android 6.0+ devices
Click to expand...
Click to collapse
I used to have CM 12.1 and it worked

I have checked again and every site says that Google Pixel Launcher needs Android 6.0.
So, I can't help you. You may ask here:
http://forum.xda-developers.com/android/help

cannot set lock screen pin, pattern or password on my samsung galaxy tab

hello guys
so i started flashing custom roms on my samsung galaxy tab s6 lite with lineage 17, 18, gsi and after that I noticed that the I cannot set a PATTERN, PIN, PASSWORD screenlock except for swipe. so what I did was a clean flash of the STOCK ROM through odin with relocked bootloader but the problem still persists where I cannot set any screenlock type except swipe and none. last thing to do was log it. so here are some logs. do you guys know a way to fix this?
Code:
2021-12-12 08:36:24.725 4657 20641 system E AndroidRuntime : FATAL EXCEPTION: AsyncTask #2
Process: com.android.settings, PID: 4657
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$4.done(AsyncTask.java:415)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:305)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
Caused by: java.lang.IllegalStateException: Fail to enroll user password when creating SP for user 0
at android.os.Parcel.createExceptionOrNull(Parcel.java:2381)
at android.os.Parcel.createException(Parcel.java:2357)
at android.os.Parcel.readException(Parcel.java:2340)
at android.os.Parcel.readException(Parcel.java:2282)
at com.android.internal.widget.ILockSettings$Stub$Proxy.setLockCredential(ILockSettings.java:1208)
at com.android.internal.widget.LockPatternUtils.setLockCredential(LockPatternUtils.java:660)
at com.android.settings.password.ChooseLockPattern$SaveAndFinishWorker.saveAndVerifyInBackground(ChooseLockPattern.java:922)
at com.android.settings.password.SaveChosenLockWorkerBase$Task.doInBackground(SaveChosenLockWorkerBase.java:138)
at com.android.settings.password.SaveChosenLockWorkerBase$Task.doInBackground(SaveChosenLockWorkerBase.java:134)
at android.os.AsyncTask$3.call(AsyncTask.java:394)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
... 4 more
Caused by: android.os.RemoteException: Remote stack trace:
at com.android.server.locksettings.SyntheticPasswordManager.createPasswordBasedSyntheticPassword(SyntheticPasswordManager.java:779)
at com.android.server.locksettings.LockSettingsService.initializeSyntheticPasswordLocked(LockSettingsService.java:2688)
at com.android.server.locksettings.LockSettingsService.setLockCredentialInternal(LockSettingsService.java:1741)
at com.android.server.locksettings.LockSettingsService.setLockCredential(LockSettingsService.java:1663)
at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:537)
2021-12-12 08:36:58.370 4317 4997 system E BufferQueueProducer : [com.android.settings/com.android.settings.password.ChooseLockPatternSize#0](id:10dd000000a7,api:0,p:-1,c:4317) disconnect: not connected (req=1)

Did you ever find a solution to this?
I have the stock and the LineageOS ROM (19.1) ROMS working fine, but a custom build of the eOS (https://e.foundation) for the S20+ (y2s) has this issue.