Hello,
I am posting here regarding a bug affecting a few custom roms. Some applications (mainly games) relying on expansion files (OBB) cannot be run on some roms (whatever the device). Apparently the bug is affecting Kitkat roms only. It's been reported a few times on the forum but never been fixed. When the affected app is trying to mount the obb file an exception is raised:
https://play.google.com/store/apps/details?id=com.simulationcurriculum.skysafari4pro&hl=en
Code:
09-20 17:14:36.128: D/MountService(839): Couldn't call DefaultContainerService to fetch OBB info for /storage/emulated/0/Android/obb/com.simulationcurriculum.skysafari4pro/main.401.com.simulationcurriculum.skysafari4pro.obb
https://play.google.com/store/apps/details?id=org.imperiaonline.android.v6
Code:
09-20 17:13:36.948: D/MountService(839): Couldn't call DefaultContainerService to fetch OBB info for /storage/emulated/0/Android/obb/org.imperiaonline.android.v6/main.57.org.imperiaonline.android.v6.obb
Most of the applications are paid app so it's not easy for rom developers to test and also only a few (known) apps are affected.
Here's the message in the log for different apps having the issue.
Apparently, it's related to a "RemoteException" error.
Other apps are affected:
https://play.google.com/store/apps/details?id=com.camouflaj.republique
"Custom ROMs are not officially supported, and may cause the error “Unfortunately, Package Access Helper has stopped.”
I understand only a few users/apps are affected but it would be great if a fix could be found. I have tested myself a few roms on different devices. (Nexus 7, 4 and OPO). AOKP, Carbon, Slim, AICP are affected. However CM11 and AOSPA (Paranoid) don't have the issue. Stock roms on Nexus devices are fine too.
Most of the apps are paid games so it does not make testing easy if you don't own the game. However "imperiaonline" is free with IAP. (No need to pay anything to reproduce the issue). So it's a good app for reproducing the bug.
I tried to have a look myself, but I don't have the required knowledge to understand the source of the issue. Most apps requiring OBB files are working fine, only a few are affected.
Maybe people having the same issue could post the name of the app here. Make sure it's exactly the same issue. (Have a look in the log).
I hope this is a good place to post considering it is not rom or device specific. Hopefully it will help to track the issue and fix it.
Roms teams are doing a fantastic job but I understand it is not a critical bug and it might no be easy to fix.
Some interesting links:
http://forum.slimroms.net/topic/2026-package-access-helper-has-stopped/
http://bugs.aokp.co/issues/293
I too have experienced this issue today on liquid smooth(Z1), when trying to play republique. Although the game launched there was no sound and the above mentioned dialogue showed up.
Techpenguin5 said:
I too have experienced this issue today on liquid smooth(Z1), when trying to play republique. Although the game launched there was no sound and the above mentioned dialogue showed up.
Click to expand...
Click to collapse
Same occured for me with Republique on my nexus 7 2013 (flo) on Paranoid Android 4.6 beta 5
I have this problem with BBC Cbeebies storytime app on my Nexus 7 2013 running Exodus rom (4.4.4). Not encountered it with any other app I have including paid apps. The app ran fine with the stock 4.4.4 rom. Love to know if there's a fix as my daughter loves the app!
Hello, I am a game developer working on a game that is affected by this. It is causing many issues with custom ROMs for us and we are desperately trying to come to a solution. We have noted that this specific error and symptoms may not be related to just a custom ROM, though our best repro case is Paranoid Android on a Nexus device. We have reports of this issue and symptoms from those running the Franco kernel, and those using various Xposed Framework modules. We have several crash logs from the Package Access Helper (/system/priv-app/DefaultContainerService.apk) service and we are willing to cooperate with knowledgable ROM developers to solve this issue.
I will locate the crash logs we have and submit them as soon as I can.
Crash Logs as promised:
Code:
I/ActivityManager(521): Start proc com.android.defcontainer for service com.android.defcontainer/.DefaultContainerService: pid=5923 uid=10003 gids={50003, 1028, 1015, 1023, 2001, 1035}
A/libc(5923): invalid address or address of corrupt block 0x6ab8a8f4 passed to dlfree
A/libc(5923): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 5935 (Binder_2)
I/DEBUG(125): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG(125): Build fingerprint: 'google/nakasi/grouper:4.4.4/KTU84P/1227136:user/release-keys'
I/DEBUG(125): Revision: '0'
I/DEBUG(125): pid: 5923, tid: 5935, name: Binder_2 >>> com.android.defcontainer <<<
I/DEBUG(125): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
I/DEBUG(125): Abort message: 'invalid address or address of corrupt block 0x6ab8a8f4 passed to dlfree'
I/DEBUG(125): r0 00000000 r1 4013d11e r2 deadbaad r3 40140c60
I/DEBUG(125): r4 6ab8a8f4 r5 4014b180 r6 4000c000 r7 6ab8a8fc
I/DEBUG(125): r8 0000002d r9 4014b384 sl 00000000 fp 6ab8a984
I/DEBUG(125): ip 00000001 sp 6ab8a8c8 lr 4010e783 pc 4010e784 cpsr 60070030
I/DEBUG(125): d0 2064657372666c64 d1 2073736572646461
I/DEBUG(125): d2 657264646120726f d3 6f6320666f207373
I/DEBUG(125): d4 756f6d61632e6d6f d5 7065722e6a616c66
I/DEBUG(125): d6 2f657571696c6275 d7 37322e6863746170
I/DEBUG(125): d8 0000000000000000 d9 0000000000000000
I/DEBUG(125): d10 0000000000000000 d11 0000000000000000
I/DEBUG(125): d12 0000000000000000 d13 0000000000000000
I/DEBUG(125): d14 0000000000000000 d15 0000000000000000
I/DEBUG(125): d16 4000000000000000 d17 3fc999999999999a
I/DEBUG(125): d18 4146605000000000 d19 0065004e005f0061
I/DEBUG(125): d20 3f8948b0fcd6e9e0 d21 3fe555b0aaeac752
I/DEBUG(125): d22 3fd24998d6307188 d23 3fcc7288e957b53b
I/DEBUG(125): d24 3fc74721cad6b0ed d25 3fc2f112df3e5244
I/DEBUG(125): d26 40026bb1bbb55516 d27 4000000000000000
I/DEBUG(125): d28 40008df2d49d41f1 d29 3fb0f4a31edab38b
I/DEBUG(125): d30 3ff0000000000000 d31 3f4de16b9c24a98f
I/DEBUG(125): scr 80000010
I/DEBUG(125): backtrace:
I/DEBUG(125): #00 pc 00011784 /system/lib/libc.so (dlfree+1191)
I/DEBUG(125): #01 pc 0000dcc3 /system/lib/libc.so (free+10)
I/DEBUG(125): #02 pc 00010aa1 /system/lib/libandroidfw.so (android::eek:bbFile::parseObbFile(int)+296)
I/DEBUG(125): #03 pc 00010cc3 /system/lib/libandroidfw.so (android::eek:bbFile::readFrom(char const*)+54)
I/DEBUG(125): #04 pc 0008703f /system/lib/libandroid_runtime.so
I/DEBUG(125): #05 pc 0001dbcc /system/lib/libdvm.so (dvmPlatformInvoke+112)
I/DEBUG(125): #06 pc 0004e123 /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
I/DEBUG(125): #07 pc 00026fe0 /system/lib/libdvm.so
I/DEBUG(125): #08 pc 0002dfa0 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
I/DEBUG(125): #09 pc 0002b638 /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
I/DEBUG(125): #10 pc 0006057d /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+336)
I/DEBUG(125): #11 pc 0004ce89 /system/lib/libdvm.so
I/DEBUG(125): #12 pc 0006d32b /system/lib/libandroid_runtime.so
I/DEBUG(125): #13 pc 00071aab /system/lib/libandroid_runtime.so
I/DEBUG(125): #14 pc 00019225 /system/lib/libbinder.so (android::BBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+60)
I/DEBUG(125): #15 pc 0001d799 /system/lib/libbinder.so (android::IPCThreadState::executeCommand(int)+508)
I/DEBUG(125): #16 pc 0001db17 /system/lib/libbinder.so (android::IPCThreadState::getAndExecuteCommand()+38)
I/DEBUG(125): #17 pc 0001db8d /system/lib/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+48)
I/DEBUG(125): #18 pc 000219f5 /system/lib/libbinder.so
I/DEBUG(125): #19 pc 0000ea5d /system/lib/libutils.so (android::Thread::_threadLoop(void*)+216)
I/DEBUG(125): #20 pc 0004d915 /system/lib/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+68)
I/DEBUG(125): #21 pc 0000e58f /system/lib/libutils.so
I/DEBUG(125): #22 pc 0000d228 /system/lib/libc.so (__thread_entry+72)
I/DEBUG(125): #23 pc 0000d3c0 /system/lib/libc.so (pthread_create+240)
I/DEBUG(125): stack:
I/DEBUG(125): 6ab8a888 fffffea0
I/DEBUG(125): 6ab8a88c 4000eae8
I/DEBUG(125): 6ab8a890 41b10c50 /dev/ashmem/dalvik-heap (deleted)
I/DEBUG(125): 6ab8a894 07520650
I/DEBUG(125): 6ab8a898 6ab8a8f4
I/DEBUG(125): 6ab8a89c 4014b180
I/DEBUG(125): 6ab8a8a0 4000c000
I/DEBUG(125): 6ab8a8a4 4010faf9 /system/lib/libc.so
I/DEBUG(125): 6ab8a8a8 4013d11e /system/lib/libc.so
I/DEBUG(125): 6ab8a8ac 6ab8a8bc
I/DEBUG(125): 6ab8a8b0 40140c60 /system/lib/libc.so
I/DEBUG(125): 6ab8a8b4 4010e783 /system/lib/libc.so (dlfree+1190)
I/DEBUG(125): 6ab8a8b8 4013d11e /system/lib/libc.so
I/DEBUG(125): 6ab8a8bc 6ab8a8f4
I/DEBUG(125): 6ab8a8c0 40140c60 /system/lib/libc.so
I/DEBUG(125): 6ab8a8c4 00000000
I/DEBUG(125): #00 6ab8a8c8 40147000 /system/lib/libc.so
I/DEBUG(125): 6ab8a8cc 2abbb038
I/DEBUG(125): 6ab8a8d0 00000000
I/DEBUG(125): 6ab8a8d4 00000030
I/DEBUG(125): 6ab8a8d8 4176e5c8
I/DEBUG(125): 6ab8a8dc 4010acc5 /system/lib/libc.so (free+12)
I/DEBUG(125): #01 6ab8a8e0 00000030
I/DEBUG(125): 6ab8a8e4 4018caa5 /system/lib/libandroidfw.so (android::eek:bbFile::parseObbFile(int)+300)
I/DEBUG(125): #02 6ab8a8e8 00000000
I/DEBUG(125): 6ab8a8ec 4010df23 /system/lib/libc.so (dlmalloc+4254)
I/DEBUG(125): 6ab8a8f0 00000010
I/DEBUG(125): 6ab8a8f4 00000004
I/DEBUG(125): 6ab8a8f8 4010ce85 /system/lib/libc.so (dlmalloc)
I/DEBUG(125): 6ab8a8fc 00000030
I/DEBUG(125): 6ab8a900 01059983
I/DEBUG(125): 6ab8a904 07520650
I/DEBUG(125): 6ab8a908 4176e5c8
I/DEBUG(125): 6ab8a90c 400fbd80
I/DEBUG(125): 6ab8a910 0000002d
I/DEBUG(125): 6ab8a914 1d300009
I/DEBUG(125): 6ab8a918 1d600005
I/DEBUG(125): 6ab8a91c 4176e5c8
I/DEBUG(125): 6ab8a920 4000eaf8
I/DEBUG(125): 6ab8a924 4018ccc7 /system/lib/libandroidfw.so (android::eek:bbFile::readFrom(char const*)+58)
I can tell you we are using unencrypted OBB files that are quite large in size, so large that we had issues with the JOBB tool similar to those mentioned in several Stack Overflow posts (<stackoverflow_url>/questions/15832039/jobb-crash-fat-full). Sorry, my account has too few posts for direct outside links, so you'll have to add the URL there.
nightchaser said:
Hello, I am a game developer working on a game that is affected by this. It is causing many issues with custom ROMs for us and we are desperately trying to come to a solution. We have noted that this specific error and symptoms may not be related to just a custom ROM, though our best repro case is Paranoid Android on a Nexus device. We have reports of this issue and symptoms from those running the Franco kernel, and those using various Xposed Framework modules. We have several crash logs from the Package Access Helper (/system/priv-app/DefaultContainerService.apk) service and we are willing to cooperate with knowledgable ROM developers to solve this issue.
I will locate the crash logs we have and submit them as soon as I can.
Click to expand...
Click to collapse
Thank you very much for this report. I am sure you are not the only game developer having the issue. I developed a few apps myself, some using obb but I never managed to reproduce the issue. This is a really annoying bug. I have been in touch with some roms developers with no luck. I really hope a fix can be found. I will try to point some rom developers to this thread, I suppose it could be a great place to discuss the issue and get some feedback. Thanks again.
I'd LOVE to find the fix to this, be it in the ROM or app. I use Sky Safari and I can only use it on my daughters tablet as my phone and tablet both on AOKP 4.4.4 won't run it; gets this error.
If anyone comes up with a workaround or something to test, I'll be happy to try it.
I have some bad news regarding this bug. I managed to reproduce it already on some LP roms. I know it is very early and most roms are in 'alpha' state. However on my OnePlus One device, I tried two different roms and two apps known for having the issue on Jellybean:
(Skysafari and Imperia Online v6).
// Roms tested:
- http://forum.xda-developers.com/oneplus-one/development/daily-stock-unofficial-cm12-builds-t2948099
- http://forum.xda-developers.com/oneplus-one/development/rom-cm11-temasek-build-t2870743
On the 'stock unofficial' CM12 everything is good. Both apps are working fine.
On 'Temasek' build (which is based on CM12 but with some 'extra' commits/features from different roms), the issue is there.
No issues with Skysafari on 'stock' Nexus 4 and N7 (2013).
Anyway, I started to look at the logs and the error is a bit different. (But the issue is similar apparently, the obb cannot be mounted). There are a few interesting things though:
// Skysafari
Code:
I/ActivityManager( 867): START u0 {cmp=com.simulationcurriculum.skysafari4pro/com.southernstars.skysafari.SkySafariActivity} from uid 10082 on display 0
I/System.out( 4954): onCreate: com.southernstars.skysafari.SkySafariActivity
I/System.out( 4954): OBB is Readable
I/System.out( 4954): OBB is Writable
D/STORAGE_MNT( 4954): MOUNT SUCCESSFULLY QUEUED
W/ContextImpl( 867): [B]Calling a method in the system process without a qualified user[/B]: android.app.ContextImpl.bindService:1757 com.android.server.MountService$ObbActionHandler.connectToService:2761 com.android.server.MountService$ObbActionHandler.handleMessage:2640 android.os.Handler.dispatchMessage:102 android.os.Looper.loop:135
...
I/SkySafari( 4954): Path to obb:
I/SkySafari( 4954): Path to assets: /storage/emulated/0/Android/data/com.simulationcurriculum.skysafari4pro/files/
I/SkySafari( 4954): Creating CSkyChart
I/SkySafari( 4954): Finished nativeInit.
E/Vold ( 257): Failed to find mounted volume for /storage/usbdisk/Android/data/com.simulationcurriculum.skysafari4pro/files/
W/Vold ( 257): Returning OperationFailed - no handler for errno 0
//Imperia Online V6
Code:
D/ObbExpansionManager( 5411): Checking if /storage/emulated/0/Android/obb/org.imperiaonline.android.v6/main.70.org.imperiaonline.android.v6.obb mounted after 300ms...
W/ObbExpansionManager( 5411): Mount not queued. Retry...
W/ContextImpl( 867): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1757 com.android.server.MountService$ObbActionHandler.connectToService:2761 com.android.server.MountService$ObbActionHandler.handleMessage:2640 android.os.Handler.dispatchMessage:102 android.os.Looper.loop:135
D/ObbExpansionManager( 5411): Mount state: 20
D/ObbExpansionManager( 5411): Checking if /storage/emulated/0/Android/obb/org.imperiaonline.android.v6/main.70.org.imperiaonline.android.v6.obb mounted after 300ms...
I hope this will be useful and rom developers will finally be able to fix this issue. More tests need to be done on different roms/devices. However I thought it would be a good idea to mention early, before more and more features are added to custom roms.
[edit]
I tested the latest build of AICP rom and contrary to JB the issue is not present on LP !
I've had the problem but in an another manner
Well, what has happens to me is completely different but similar in the same time everytime I try and install ANY app or game it pops up with message saying ^ unfortunaltey, package access helper has stopped. This is my problem I hope u can find a fix to it and if not I hope it was usefull
Vasili00 said:
Well, what has happens to me is completely different but similar in the same time everytime I try and install ANY app or game it pops up with message saying ^ unfortunaltey, package access helper has stopped. This is my problem I hope u can find a fix to it and if not I hope it was usefull
Click to expand...
Click to collapse
Nope, your ROM is busted. Not the same issue.
Anyway.. Sky Safari fixed something on their end a few weeks ago, working on all ROMs for me now. I wonder what they changed.
khaytsus said:
Nope, your ROM is busted. Not the same issue.
Anyway.. Sky Safari fixed something on their end a few weeks ago, working on all ROMs for me now. I wonder what they changed.
Click to expand...
Click to collapse
Really ? Would you mind giving more details about which roms/devices you tried ? Thanks.
_Man0waR_ said:
Really ? Would you mind giving more details about which roms/devices you tried ? Thanks.
Click to expand...
Click to collapse
It apparently was busted on official L, which I think honestly is the ONLY reason they fixed it. So it works there, also works on AOKP 4.4.4. I don't have any other ROMs on active devices.
It's a market update, should have already seen that update if Sky Safari was one you were having issues with?
khaytsus said:
It apparently was busted on official L, which I think honestly is the ONLY reason they fixed it. So it works there, also works on AOKP 4.4.4. I don't have any other ROMs on active devices.
It's a market update, should have already seen that update if Sky Safari was one you were having issues with?
Click to expand...
Click to collapse
To be honest, I have not done much testing recently on KK and mainly checked the state of the bug on L roms. I am definitely using Skysafari, but it's not the main app I'm using for testing this bug. Personally I never had the issue on the official L on my Nexus 4 and 7 (2013). The last time I tried Skysafari was a few weeks ago, just after an update (I remember that the whole obb file had to be downloaded again). I was still having the issue on my OnePlus One using 'Temasek' L rom. I will probably try again soon. It would be nice to know what was the fix though.
Thanks a lot anyway.
[edit] I have just found this. See last post. (Maybe this is where you heard about the fix ?)
http://www.cloudynights.com/topic/486890-sky-safari-android-5-nexus-10-issue/
[edit2[ Indeed I have just tested the latest Skysafari on 'Temasek' L rom (OnePlus One) and it's fine now ! They definitely 'fixed' something in the app. I will try to contact the developers to know a bit more about the fix and what was wrong. It's probably something similar in the other games/apps with the same issue. It looks like the issue is with the apps and not the custom roms.
_Man0waR_ said:
To be honest, I have not done much testing recently on KK and mainly checked the state of the bug on L roms. I am definitely using Skysafari, but it's not the main app I'm using for testing this bug. Personally I never had the issue on the official L on my Nexus 4 and 7 (2013). The last time I tried Skysafari was a few weeks ago, just after an update (I remember that the whole obb file had to be downloaded again). I was still having the issue on my OnePlus One using 'Temasek' L rom. I will probably try again soon. It would be nice to know what was the fix though.
Thanks a lot anyway.
[edit] I have just found this. See last post. (Maybe this is where you heard about the fix ?)
http://www.cloudynights.com/topic/486890-sky-safari-android-5-nexus-10-issue/
[edit2[ Indeed I have just tested the latest Skysafari on 'Temasek' L rom (OnePlus One) and it's fine now ! They definitely 'fixed' something in the app. I will try to contact the developers to know a bit more about the fix and what was wrong. It's probably something similar in the other games/apps with the same issue. It looks like the issue is with the apps and not the custom roms.
Click to expand...
Click to collapse
Eh? I heard about the fix in the Sky Safari changelog. It's gone now, as there has been another update, but the changelog clearly said that they fixed problems with L and should fix issues with custom ROMs. It did for me on AOKP 4.4.4, and it works on L on my Nexus 7 2013.
Temasek's 16.8 in ks01lte also presenting this with Republique. The game support did not helped me to find a solution. I know it's a paid game but I also have my reasons to use custom rom (specially because I work with a lot of things that only a custom rom have).
Someone got this fixed and the changelog posted?
leleobhz said:
Temasek's 16.8 in ks01lte also presenting this with Republique. The game support did not helped me to find a solution. I know it's a paid game but I also have my reasons to use custom rom (specially because I work with a lot of things that only a custom rom have).
Someone got this fixed and the changelog posted?
Click to expand...
Click to collapse
They have to fix it on their end... Various games or apps have fixed this issue after enough users complained about it. It even affects some stock ROMs or devices, I think a few were listed in this thread. I think I had problems with one app on a stock Nexus 7 ROM at one point.
But what to tell them? It's hard to convince them they they can or should fix it.
nightchaser said:
Hello, I am a game developer working on a game that is affected by this. It is causing many issues with custom ROMs for us and we are desperately trying to come to a solution. We have noted that this specific error and symptoms may not be related to just a custom ROM, though our best repro case is Paranoid Android on a Nexus device. We have reports of this issue and symptoms from those running the Franco kernel, and those using various Xposed Framework modules. We have several crash logs from the Package Access Helper (/system/priv-app/DefaultContainerService.apk) service and we are willing to cooperate with knowledgable ROM developers to solve this issue.
I will locate the crash logs we have and submit them as soon as I can.
Click to expand...
Click to collapse
I just found out that if I use apkeditor to change the installation location to internal the recompiled apk will install, I tried it with a couple of apps I couldn't install on my galaxy s4 with lollipop and now I can
So far for me it was Exoplanet Explorer and Turbo Dismount, and on both I just had to change the default location to internal.
Related
My iMATE is no longer entering Bootloader mode. Not by pressing hardware buttons, not by initiating bootloader mode by upgrade programm. It just restarts device. I am afraid, that I am going to stuck with the ROM version I currently have, wich is bummer because Second Edition is coming out soon.
Any suggestions how to fix this? I remember that by Bootloader was version 1.03.
I have a serial cable, SD reader and SD card as my tools.
Please, help.
Regards.
I wonder, if similar tool exist for himalaya:
http://forum.xda-developers.com/viewtopic.php?t=2079&highlight=bootloader+fix
OK, I did some research and found following utilities:
savebootlader.exe
pnewbootloader.exe
Please, tell me. If I'll get dump of bootloader 1.03 ( the one I've had on my machine) from working XDA2 and then upload it by pnewbootloader IT WILL FIX MY PROBLEM? and does it really necessary to have the same bootloader version or I can use any, 1.01, 1.06?
TIA
I really hope that it will
got bootloader dumped by people here (thanks a lot again!), but when I try to put it back to machine I am getting
C:\Program Files\XDAtools\binaries>pnewbootloader bootloader.nb0
this is possibly not a bootloader!!
80000000: ea0003fe 00000000 00000000 00000000 ................
80000010: 00000000 00000000 00000000 00000000 ................
80000020: 00000000 00000000 00000000 00000000 ................
80000030: 00000000 00000000 00000000 00000000 ................
80000040: 43454345 90064000 00000000 00000000 [email protected]
C:\Program Files\XDAtools\binaries>pnewbootloader -f bootloader.nb0
Unable to find flash info offset, cannot disable bootloader writeprotect
Looks like this utility is not designed for XDA2.
Anyone? :roll:
ID64... How to use those tools? And from where to use it? I've got all the tools but i dunno how and where to use it? Sorry for asking...
Hi all,
First-time poster and fairly new to rooting...
I have a Samsung Galaxy SII (GT-I9100, originally LBP firmware on Orange UK) which I successfully managed to flash with Odin/Heimdall to give:
CF-Root
CyanogenMod 9 RC1
Siyah 3.3.2
I then thought I'd give Boot2Gecko a try so I followed gokhanmoral's post and managed to get a page not found screen booting to the second rom.
So I checked out the B2G source code and performed a
make install-gaia
Click to expand...
Click to collapse
ensuring
adb devices
Click to expand...
Click to collapse
found my phone connected over usb - This gave me a lock screen which wouldn't respond to touch events.
After quite a bit of reading I then decided to attempt pusler new 6th July Build performing:
simg2img userdata.img data.img
heimdall detect
heimdall flash --hidden system.img
(cleared 2ndROM data and cache through CWM)
adb push data.img /sdcard/.secondrom/data.img
Click to expand...
Click to collapse
However, when I booted to the 2ndROM I gott a black screen - I tried looking through the
adb shell logcat
Click to expand...
Click to collapse
output and saw several errors similar to:
I/GeckoDump( 9894): Opened socket on 9999
E/GeckoConsole( 9894): [JavaScript Error: "NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]" {file: "chrome://browser/content/shell.js" line: 80}]
I/Gecko ( 9894): Logging GL tracing output to /system/b2g/firefox.trace
I/Gecko ( 9894): Attempting load of /data/local/egltrace.so
F/libc ( 9894): Fatal signal 11 (SIGSEGV) at 0x00000068 (code=1)
I/Gecko ( 9894): Attempting load of libEGL.so
D/libEGL ( 9894): egl.cfg not found, using default config
D/libEGL ( 9894): loaded /system/lib/egl/libGLES_android.so
I/Gecko ( 9894): Failed to create EGL config!
F/libc ( 9894): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)
I/DEBUG ( 9891): debuggerd committing suicide to free the zombie!
F/libc ( 9847): Fatal signal 13 (SIGPIPE) at 0x00002677 (code=0)
I/DEBUG ( 9978): debuggerd: Jul 6 2012 04:08:21
I/ ( 9979): ServiceManager: 0xf958
V/yamaha::media::CManager( 9979): constructor
Click to expand...
Click to collapse
Seems like a Gecko Chrome error but I can't be sure. As a last ditch effort I tried to follow gokhanmoral's method of extracting/mounting pusler's images, creating tar files and placing them into a CWM flashable zip but Siyah wouldn't recognise the 2ndROM after installing so now I'm all out of ideas.
Has anyone managed to successfully install the 6th July build as a 2ndROM? Any help/info would be appreciated.
Cheers
What is it?
A pure(-ish) build of AOSP (code-frozen 4.1.2_r1/jb-mr0-release, a.k.a JZO54K) for the Xperia Play. It's as pure as can be, there are some fixes from CM10 (thanks J), SlimRom and myself needed to get everything working. But the framework and apps are 99% 90% AOSP, with changes specific to solving known Jellybean issues on our device. There are however some more extras, such as Google Apps preinstalled and maybe some other slight changes.
What's the point?
Designed for developers/chefs and testers, this has three major goals:
Provide a good base to port other Jellybean ROM's to (in particular, my Turbo UI ROM)
A good comparison with other JB ROM's to see what is and isn't broken (great for the second or third multiboot slot). E.g. if something crashes in Slimbean or PAC, try in this. Because it is "feature frozen" whereas CM10 and other JB ROM's keep adding new things that may break something (you know, it happens).
Forward-port ICS/GB code to get more things working - like native xLoud and better Touchpad support.
This ROM is feature frozen. I will not add Notification Toggles. I will not add a Reboot option to power menu. I will not add *anything* unless it will benefit other JB ROM's/Developers or Turbo UI. Please don't request new fancy features that other JB ROM's already have - this is not the point of this ROM. Many of my developments have already made their way into wedgess PAC, cj360's SlimBean and/or FXP's CyanogenMod. Jellyzeus is a platform for my own research and improvements and I only released it for educational, development and comparison purposes.
If you want a more serious and useful ROM that is directly based on this, check out my MIUI based PatchROM build - Turbo UI.
Status?
Green: Complete
Brown: Has issues or untested
Red: Broken or not finished yet
Calls, texts, 3G for GSM (have not done heavy testing, needs more)
Multiboot-aware
All sensors (including proximity)
CDMA addon (beta, needs logcats if any problems)
Camera (Legacy) (Thanks to Wedgess) (No Panorama)
Browser and Web rendering
Sound with with decent stock-like headphone volume
xLOUD enabled (uses ICS Audio blobs from stock/prebuilt) (hack)
Google Apps included
Wifi
GPS / Location services
Touchpads (Lag reduced but not eliminated)
Bluetooth
Native Wifi Tether
Google Now Voice Search/Recognition
Video Recording (480p only - don't ask about 720p, not possible)
?
Bugs/Important Info?
On a fresh install, all the tones are set to silent. Ringtone, Notification Tone and Alarm tone must be manually set. I have no idea what is causing this. Fixed.
Sources?
All of my source changes can, as always, be found on my GitHub (see my signature). Additionally, here are the details of my repo's - they are all original AOSP from 4.1.2_r1 tag, with the exception of these mentioned repo's - mostly for compatibility with QCOM hardware, as well as additional fixes and improvement's I've made. There are also various small patches to make to get it to build. Instructions for building from my sources can be found in post #2.
Source repo/patch details:
Code:
cosmicdan:
bootable/recovery/ (forked from cyanogenmod)
device/semc/msm7x30-common/ (forked from garwedgess)
frameworks/av/ (forked from AOSP)
frameworks/base/ (forked from AOSP) (jellyzeus branch)
frameworks/native/ (forked from AOSP)
hardware/libhardware/ (forked from slimroms, jb branch)
hardware/libhardware_legacy/ (forked from slimroms, jb branch)
libcore (forked from AOSP)
system/core/ (forked from AOSP) (jellyzeus branch)
vendor/semc/ (forked from garwedgess)
cyanogenmod:
build/
external/busybox/
external/bluetooth/bluez/
external/yaffs2/
external/zlib/
hardware/broadcom/wlan/
hardware/ril/
hardware/sony/DASH/
packages/apps/Gallery2/
packages/apps/LegacyCamera/
vendor/cm/
system/bluetooth/
system/netd/
system/vold/
garwedgess:
device/semc/msm7x30-common/
device/semc/zeus/
device/semc/zeus-common/
SlimRoms (branch):
external/chromium/ (jellybean)
external/webcore/ (jellybean)
hardware/msm7k/ (jb)
hardware/qcom/audio/ (jb)
hardware/qcom/gps/ (jb)
hardware/qcom/media/ (jb)
hardware/qcom/display/ (jellybean)
This patch for Guava incompatibility with OpenJDK -
https://github.com/CyanogenMod/android_external_guava/commit/c8b97210aa31c9b80b5fd136d8617ebe4e731e09
Use prebuilt kernel to save time and fix build complaining from missing kernel sources -
Open /device/semc/zeus/BoardConfig.mk and remove the comment (#) symbol from TARGET_PREBUILT_KERNEL
Open vendor/cm/config/common.mk and comment out the three lines for Terminal, like so:
[code]#PRODUCT_COPY_FILES += \
#vendor/cm/proprietary/Term.apk:system/app/Term.apk \
#vendor/cm/proprietary/lib/armeabi/libjackpal-androidterm4.so:system/lib/libjackpal-androidterm4.so
[/code]
Credits?
CosmicDan, Kamarush and Irii for Turbo JB Kernel
Cyanogenmod and Jerpelea (FreeXperia)
Wedgess, cj360, paxChristos, KeiranFTW, Nickholtus, SuperVenom and Farenheith
Fellow members of MIUI Australia - LennyKano, FusionJack and Dekky
Special thanks to Amarullz (creator of Aroma Installer) and the XDA community
Download and Instructions?
Flash Turbo JB kernel (recommended) and be sure to follow the instructions there. This ROM is multiboot-aware already, so feel free to install the ZIP from Slot 2 or 3.
Install the ROM normally (in any slot you like if using multiboot)
Download latest ROM: zeus_aosp_412_r5.zip @ Mediafire
Download CDMA addon: zeus_aosp_412_cdma_r3.zip @ Mediafire (install after main ROM)
Changelog?
Code:
r5
--
- Overhaul Telephony, Webkit, Bluetooth and Net framework
- Additional property support from CyanogenMod (performance related)
- Reverted Camera changes in r4
- More things I can't remember. It's all on GitHub.
r4
--
- Fixed Camera recording (480p only, 720p permanently removed due to bugs)
- Fixed native App2SD
- Numerous fixes/optimizations to Telephony and Media framework
- Reverted ICS audio blobs
r3
--
- New - hold volume buttons to skip music tracks
- Fixed various Google App issues (e.g. Calendar sync, Location services)
- Reduced touchpad lag by about half (best I can do until we learn more...)
- Fixed touchpad recognition (Farenheith's Touchpad Fix v1.1)
- Fixed default tones being silent (Random fix)
- Fixed Wifi signal indicator on statusbar (Framework issue)
- Fixed GPS (was it ever broken? Google Maps and GPS Status lock fine)
- Fixed Bluetooth (Update sources for BCM interface from CM10)
- Patched services to not force minfree or adj values
- Basic tweaks added to init.d, same used in MIUI Australia (minfree/adj/kernel tuning)
- Updated Google Now to latest version (no longer crashes on voice input but simply fails)
r2
--
- Additional video and audio native decoding support, thanks to CAF (such as H.263, WMV, MP3, etc)
- Fixed root (replaced with Chainfire's SuperSU v0.99)
- Fixed Proximity Sensor
- Fixed rotation (accelerometer/orientation)
- Fixed compass
- Fixed ALS (automatic brightness)
- Fixed Browser (replaced webKit core with prebuilt from SlimBean port, thanks cj360!)
- Disable some debugging parameters to improve performance
- Native Sony sound blobs and full xLoud support enabled
- Replaced AOSP Keyboard with Nexus 4.2 version (smaller APK)
- Removed unused content accidently included from CM10
- Removed Google Calendar and returned original (more compatible with widgets, can get Google Calendar from Play Store anyway)
r1
--
- Initial release
Screenshots?
No. It looks like AOSP (like CM10 but with much less features). If you only want to see what this ROM looks like, please move along it's for dev's and research purposes after all.
This post is reserved for build instructions.
Really looking forward for this! First!
Sent from my R800i using xda app-developers app
---------- Post added at 05:15 AM ---------- Previous post was at 04:28 AM ----------
I don't really have any ideas on the kernel panic, but I'll keep thinking.
Sent from my R800i using xda app-developers app
I figured it out, same problem as the webcore glitches. QCOM tile renderer is not fully ported yet. WOOO one-man think tank!
CosmicDan said:
I figured it out, same problem as the webcore glitches. QCOM tile renderer is not fully ported yet. WOOO one-man think tank!
Click to expand...
Click to collapse
+ A Half Wit
Sent from my R800i using xda app-developers app
You're only a halfwit when you complain or flame the dev's
The camera works fine. The automatic rotation doesn't work.
Binary_File said:
The camera works fine. The automatic rotation doesn't work.
Click to expand...
Click to collapse
Erm... Camera doesn't work. Automatic rotation is a minor framework issue, not a priority right now. Main things are camera and web browser (which are graphics related).
CosmicDan said:
This post is for detailed status and (when available) source-code links and summaries of changes.
kmsg dump of the kernel panic when trying to start legacy camera:
Code:
Switching from ACPU rate 768000 KHz -> 1024000 KHz
Enabling PLL 2
Disabling PLL 1
ACPU speed change complete
msm_enqueue: queue event new max is 1
msm_enqueue: queue control new max is 1
msm_pp_release: pp not in progress for 0
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = 81180000
[00000000] *pgd=01376031, *pte=00000000, *ppte=00000000
Internal error: Oops: 80000007 [#1] PREEMPT
last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
Modules linked in:
CPU: 0 Tainted: G W (2.6.32.9-KRsH-irii #1)
PC is at 0x0
LR is at msm_ioctl_config+0x10d8/0x12b4
pc : [<00000000>] lr : [<803e5198>] psr: 60000013
sp : 8c135e68 ip : 00000014 fp : 8c135edc
r10: 2c72490c r9 : 8c134000 r8 : 8003712c
r7 : 40046d1b r6 : 2c72490c r5 : 2c72490c r4 : 80e6d0d8
r3 : 00000000 r2 : 0000002b r1 : 00000000 r0 : 8c135e84
Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
Control: 10c57c7d Table: 01380059 DAC: 00000015
LR: 0x803e5118:
5118 fffffe00 e1a0200d e3c23d7f e3c3303f e24b0070 e5933008 e2952004 30d22003
5138 33a03000 e3530000 1a000005 e1a01005 e3a02004 ebfaf31b e3500000 0a000008
5158 ea000001 e3a01004 ebfafc46 e51f0064 e3002854 e51f1074 e51f3068 eb06ce30
5178 ea00003e e5943000 e51b1070 e5932080 e59330c4 e592205c e5920000 e12fff33
5198 eafffc1e e51f00a0 e5947000 e3500010 9a000004 e3a010d0 ebf5798b e2506000
51b8 1a000001 ea000002 e1a06000 e3a03001 e5863030 e1a0c00d e3cc3d7f e3c3303f
51d8 e286003c e5933008 e2952004 30d22003 33a03000 e3530000 1a000005 e1a01005
51f8 e3a02004 ebfaf2ef e2504000 0a000017 ea000001 e3a01004 ebfafc1a e51f0114
SP: 0x8c135de8:
5de8 00000000 80d9c000 800d8624 80114318 80c0ca40 00000000 ffffffff 8c135e54
5e08 2c72490c 40046d1b 8c135edc 8c135e20 80036bb0 80036308 8c135e84 00000000
5e28 0000002b 00000000 80e6d0d8 2c72490c 2c72490c 40046d1b 8003712c 8c134000
5e48 2c72490c 8c135edc 00000014 8c135e68 803e5198 00000000 60000013 ffffffff
5e68 8c135ecc 8c135e78 801303fc 8012d1bc 00000032 00000000 00000000 0000002b
5e88 2c57000c 2c724900 000004cc 81180b10 00000133 00000000 00000000 8c130128
5ea8 00000200 8c156420 8c135ecc 8c029a00 803e40c0 2c72490c 40046d1b 8003712c
5ec8 8c134000 2c72490c 8c135efc 8c135ee0 80157698 803e40cc 2c72490c 8c029a00
FP: 0x8c135e5c:
5e5c 00000000 60000013 ffffffff 8c135ecc 8c135e78 801303fc 8012d1bc 00000032
5e7c 00000000 00000000 0000002b 2c57000c 2c724900 000004cc 81180b10 00000133
5e9c 00000000 00000000 8c130128 00000200 8c156420 8c135ecc 8c029a00 803e40c0
5ebc 2c72490c 40046d1b 8003712c 8c134000 2c72490c 8c135efc 8c135ee0 80157698
5edc 803e40cc 2c72490c 8c029a00 40046d1b 0000001b 8c135f7c 8c135f00 80158160
5efc 80157668 80036340 8003eb18 80e2b6c0 00000002 8017a404 801482c4 cf397500
5f1c 00000020 00000000 00000000 00000003 2c7245b0 ceaa1b00 2c7245b0 00000003
5f3c 00000000 8c135f6c 8c135f50 ceaa1b00 00000002 0000001b 2c72490c 8c029a00
R0: 0x8c135e04:
5e04 8c135e54 2c72490c 40046d1b 8c135edc 8c135e20 80036bb0 80036308 8c135e84
5e24 00000000 0000002b 00000000 80e6d0d8 2c72490c 2c72490c 40046d1b 8003712c
5e44 8c134000 2c72490c 8c135edc 00000014 8c135e68 803e5198 00000000 60000013
5e64 ffffffff 8c135ecc 8c135e78 801303fc 8012d1bc 00000032 00000000 00000000
5e84 0000002b 2c57000c 2c724900 000004cc 81180b10 00000133 00000000 00000000
5ea4 8c130128 00000200 8c156420 8c135ecc 8c029a00 803e40c0 2c72490c 40046d1b
5ec4 8003712c 8c134000 2c72490c 8c135efc 8c135ee0 80157698 803e40cc 2c72490c
5ee4 8c029a00 40046d1b 0000001b 8c135f7c 8c135f00 80158160 80157668 80036340
R4: 0x80e6d058:
d058 80e6d054 00000000 00000000 8080e260 00000000 00000002 00000001 00000000
d078 805d9458 80e2b7a4 80e2b7a4 0ee00001 00000001 00000001 80e6d0d8 00000000
d098 00000000 80e6d09c 80e6d09c 00000000 00000000 8080e260 00000000 00000001
d0b8 00000001 00000000 805d94c0 80e6d0c4 80e6d0c4 0ee00002 00000001 00000000
d0d8 cb099500 00000000 80e6d0e0 80e6d0e0 80e6d0e8 80e6d0e8 00000001 00000000
d0f8 80719017 80e6d0fc 80e6d0fc 80e6d104 80e6d104 00000000 00000000 80728fea
d118 00000000 80e6d11c 80e6d11c 80e6d124 80e6d124 00000000 00000000 80728ff0
d138 00000000 80e6d13c 80e6d13c 80e6d144 80e6d144 00000000 00000000 80728ff5
R8: 0x800370ac:
70ac e24fef6d 3798f107 e28d1008 e3a08000 e357080f e2270000 2a0011ff ea02873c
70cc e1a02007 e28d1008 e3a00000 eb000925 e28fe014 e1a07000 e28d1008 e3570e17
70ec 3891000f 3798f107 eaffffef e5ad0008 e1a02007 e1a0100d e3a00001 eb000919
710c eaffff90 e320f000 e320f000 e320f000 e320f000 807e8a98 8080bf00 800377a8
712c 800ceacc 800bf904 80037714 80148fcc 80149048 801482f0 80146848 800d8dc0
714c 80148340 801560cc 80155e88 80037724 80147c5c 800d8dc0 80155cec 80147f4c
716c 800eb148 800d8dc0 800d8dc0 801488f4 800cb73c 80164720 800d8dc0 800eb230
718c 800eb644 800d8dc0 800c70b4 800d8dc0 800d8dc0 800cfc0c 800d8dc0 800d8dc0
R9: 0x8c133f80:
3f80 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
3fa0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
3fc0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
3fe0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
4000 00000000 00000002 00000000 8c156420 807fdff8 00000000 00000017 8119faa0
4020 8119faa0 8c134000 8c1565cc 811fa1c0 00000000 8c156420 8c135e6c 8c135e20
4040 8059e334 00000000 00000000 00000000 00000000 00000000 01010000 00000000
4060 2c724f00 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Process Binder_1 (pid: 1156, stack limit = 0x8c1342f0)
Stack: (0x8c135e68 to 0x8c136000)
5e60: 8c135ecc 8c135e78 801303fc 8012d1bc 00000032 00000000
5e80: 00000000 0000002b 2c57000c 2c724900 000004cc 81180b10 00000133 00000000
5ea0: 00000000 8c130128 00000200 8c156420 8c135ecc 8c029a00 803e40c0 2c72490c
5ec0: 40046d1b 8003712c 8c134000 2c72490c 8c135efc 8c135ee0 80157698 803e40cc
5ee0: 2c72490c 8c029a00 40046d1b 0000001b 8c135f7c 8c135f00 80158160 80157668
5f00: 80036340 8003eb18 80e2b6c0 00000002 8017a404 801482c4 cf397500 00000020
5f20: 00000000 00000000 00000003 2c7245b0 ceaa1b00 2c7245b0 00000003 00000000
5f40: 8c135f6c 8c135f50 ceaa1b00 00000002 0000001b 2c72490c 8c029a00 40046d1b
5f60: 0000001b 8003712c 8c134000 00000000 8c135fa4 8c135f80 801581f8 80157c28
5f80: 00000001 00000001 2c5762d8 2c569740 2c724934 00000036 00000000 8c135fa8
5fa0: 80036f00 801581c0 2c5762d8 2c569740 0000001b 40046d1b 2c72490c 2c7248fc
5fc0: 2c5762d8 2c569740 2c724934 00000036 2c574dd8 000e1000 0006ae00 000002f8
5fe0: 2c53930c 2c7248e0 2ab49cfd 2ab2ebd4 00000010 0000001b ff706766 ff746a6a
Code: bad PC value
[audio_out.c:audio_dsp_event] PCMDMAMISSED 32
Nnvh vdnnbolllicb.o vk
---[ end trace 1b75b31a2719ed1e ]---
Kernel panijbimvhyc - not syncing: Fatal exception
[<8003d83c>] (unwind_backtrace+0x0/0xd8) from [<80598164>] (dump_stack+0x20/0x24)
[<80598164>] (dump_stack+0x20/0x24) from [<80598978>] (panic+0x6c/0x130)
[<80598978>] (panic+0x6c/0x130) from [<8003b5c4>] (die+0x17c/0x1a8)
[<8003b5c4>] (die+0x17c/0x1a8) from [<805981cc>] (__do_kernel_fault.part.2+0x64/0x74)
[<805981cc>] (__do_kernel_fault.part.2+0x64/0x74) from [<8003ecf8>] (do_page_fault+0x1ec/0x204)
[<8003ecf8>] (do_page_fault+0x1ec/0x204) from [<80036340>] (do_PrefetchAbort+0x44/0xa8)
[<80036340>] (do_PrefetchAbort+0x44/0xa8) from [<80036bb0>] (__pabt_svc+0x50/0xa0)
Exception stack(0x8c135e20 to 0x8c135e68)
5e20: 8c135e84 00000000 0000002b 00000000 80e6d0d8 2c72490c 2c72490c 40046d1b
5e40: 8003712c 8c134000 2c72490c 8c135edc 00000014 8c135e68 803e5198 00000000
5e60: 60000013 ffffffff
[<80036bb0>] (__pabt_svc+0xiy. Mkz50/0xa0) fro . [<803e5198>] (msm_ioctl_config+0x10d8/0x12b4)
[<803e5198>must (msm_ioctl_config+0x10d8/0x12b4) from [<80157698>] (vfs_ioctl+0x3c/0x9c)
Mk
[<80157x cg:banghead: mixvkok698>]
(vfs_ioctl+0x3c/0x9c) from [<80158160>]r (do_vfs_ioctl+0x54oftu 4/0x598)
? Ggbf yourself g6c6uukt:rolleyes:lmng
[<80158160>] (do_vfsvkrjvj_ioctl+0x544/0x598) from [<8y01581f8>]y (sys_ioctl+0x44/0x70)
[<801581f8>] (sys_ioctl+0x44/0x70) from [<80036f00>] (ret_fast_syscall+0x0/0x2c)
:
&@[email protected]:*Binder_1*
Gvnm .:df
Rebooteing in 1 seconds..
smd_close(RPCCALL)mm l nuik
:what::thumbdown:
I think the interesting part is this:
Code:
Code: bad PC value
[audio_out.c:audio_dsp_evju:jnj çgigyaent] PCMDMAMISSED 32
d .mzk
Y
I've done some research and apparently this is some kind of deadlock, but from what i do nott know.
Click to expand...
Click to collapse
Sent from my FIH-FB0 using xda premium
I found the problem, both camera and browser should be fixed this weekend. Was not using latest fixed QCOM hardware sources for display (specifically, TileRendering support).
Proximity mught be in the libs.
/system/lib/libssensorservice.so
Or something like that. Maybe..
Sent from my Xperia Play using xda app-developers app
JunDavis said:
Proximity mught be in the libs.
/system/lib/libssensorservice.so
Or something like that. Maybe..
Sent from my Xperia Play using xda app-developers app
Click to expand...
Click to collapse
Well yeah, and the sensor hardware static object. Finding the actual code and getting the ICS sensor framework working in JB is no as simple as copy/paste though.
On a lighter note, I've already implemented the groundwork for using Sony stock ICS audio libs. Which means that getting full xLoud support (actually reliably unlike Turbo UI and, in future, with a toggle) should be relatively easy. Yay!
CosmicDan said:
Well yeah, and the sensor hardware static object. Finding the actual code and getting the ICS sensor framework working in JB is no as simple as copy/paste though.
On a lighter note, I've already implemented the groundwork for using Sony stock ICS audio libs. Which means that getting full xLoud support (actually reliably unlike Turbo UI and, in future, with a toggle) should be relatively easy. Yay!
Click to expand...
Click to collapse
Yea :/, I knew you can't just copy and paste. I just posted that because I thought it was somewhat relevant.
Also, yay! xLoud
Sent from my Xperia Play using xda app-developers app
Besides, why do we need proximity sensor anyway? It only goes up to 1 cm.
Guess it would be nice to have every tiny thing working though.
Sent from my Xperia Play using xda app-developers app
JunDavis said:
Besides, why do we need proximity sensor anyway? It only goes up to 1 cm.
Guess it would be nice to have every tiny thing working though.
Sent from my Xperia Play using xda app-developers app
Click to expand...
Click to collapse
Because it's annoying that your face can touch buttons when you're in a call lol.
CosmicDan said:
Because it's annoying that your face can touch buttons when you're in a call lol.
Click to expand...
Click to collapse
Never had that problem o.o lol
Sent from my Xperia Play using xda app-developers app
CosmicDan said:
Because it's annoying that your face can touch buttons when you're in a call lol.
Click to expand...
Click to collapse
Yeah lol
Sent from my R800i using Tapatalk 2
And also battery. If you're in a long call you want to save as much battery as possible, and the screen is the biggest offender of battery use. I know you can always press power button to turn screen on/off, but that's quite annoying when you want to (e.g) quickly check how long the call has gone for.
CosmicDan said:
And also battery. If you're in a long call you want to save as much battery as possible, and the screen is the biggest offender of battery use. I know you can always press power button to turn screen on/off, but that's quite annoying when you want to (e.g) quickly check how long the call has gone for.
Click to expand...
Click to collapse
Agreed, I already had to upgrade my battery a while back :/
Sent from my Xperia Play using xda app-developers app
Make sure you keep your old one for whenever you do flashing or logcat and other USB stuff. Constantly plugging/unplugging USB tends to wear-out a battery quicker that usual. And as usual, only charge when essential _don't top it up every night if not needed). But sometimes that's not realistic, so use "Fast Discharge" app on Play Store to help quickly drain battery fully, then recharge to max over night (from flat). That will help recondition the battery.
But yeah, my "dev battery" barely lasts two hours lol. That's the original one from my old X10.
There's a problem with mount.exfat in many ROMs, including Cyanogen 12.1 and, I suppose, Cyanogen 13. It sometimes crashes under load, notably from SQLite (AnkiDroid in my case). From the user side, the SD card just dismounts. Logcat says:
Code:
I/DEBUG ( 2621): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x2c
W/NativeCrashListener( 4743): Couldn't find ProcessRecord for pid 10218
I/DEBUG ( 2621): r0 b6fc0838 r1 00000000 r2 ffffffc8 r3 b6f7cde4
E/DEBUG ( 2621): AM write failure (32 / Broken pipe)
I/DEBUG ( 2621): r4 b6fc0838 r5 befdf730 r6 00000000 r7 b6fbee0c
I/DEBUG ( 2621): r8 b703bfb0 r9 b6fc0838 sl 00000001 fp 00000000
I/DEBUG ( 2621): ip b6fbef2c sp befdf668 lr b6fa2ed3 pc b6fa655a cpsr 80000030
I/DEBUG ( 2621):
I/DEBUG ( 2621): backtrace:
I/DEBUG ( 2621): #00 pc 0000655a /system/bin/mount.exfat
I/DEBUG ( 2621): #01 pc 00002ecf /system/bin/mount.exfat
I/DEBUG ( 2621): #02 pc 0000a4cb /system/bin/mount.exfat
I/DEBUG ( 2621): #03 pc 0000a52b /system/bin/mount.exfat
I/DEBUG ( 2621): #04 pc 0000d361 /system/bin/mount.exfat
I/DEBUG ( 2621): #05 pc 0000e02b /system/bin/mount.exfat
I/DEBUG ( 2621): #06 pc 0000ef03 /system/bin/mount.exfat
I/DEBUG ( 2621): #07 pc 0000c843 /system/bin/mount.exfat
I/DEBUG ( 2621): #08 pc 00009133 /system/bin/mount.exfat
I/DEBUG ( 2621): #09 pc 0000317d /system/bin/mount.exfat
I/DEBUG ( 2621): #10 pc 0000f4a9 /system/lib/libc.so (__libc_init+44)
I/DEBUG ( 2621): #11 pc 00002964 /system/bin/mount.exfat
I/DEBUG ( 2621):
I/DEBUG ( 2621): Tombstone written to: /data/tombstones/tombstone_00
Here's one person with this, here's another, and even a Cyanogen bug report (somehow closed).
Anyway, this is how the stack looks with symbols:
Code:
I/DEBUG ( 2622): #00 pc 0000655a /system/bin/mount.exfat (exfat_flush_node+21)
I/DEBUG ( 2622): #01 pc 00002ecf /system/bin/mount.exfat (fuse_exfat_fsync+14)
I/DEBUG ( 2622): #02 pc 0000a4cb /system/bin/mount.exfat (fuse_fs_fsyncdir+66)
I/DEBUG ( 2622): #03 pc 0000a52b /system/bin/mount.exfat (fuse_lib_fsyncdir+70)
I/DEBUG ( 2622): #04 pc 0000d361 /system/bin/mount.exfat (do_fsyncdir+52)
I/DEBUG ( 2622): #05 pc 0000e02b /system/bin/mount.exfat (fuse_ll_process_buf+1042)
I/DEBUG ( 2622): #06 pc 0000ef03 /system/bin/mount.exfat (fuse_session_process_buf+12)
I/DEBUG ( 2622): #07 pc 0000c843 /system/bin/mount.exfat (fuse_session_loop+122)
I/DEBUG ( 2622): #08 pc 00009133 /system/bin/mount.exfat (fuse_loop+278)
I/DEBUG ( 2622): #09 pc 0000317d /system/bin/mount.exfat (mount_exfat_main+652)
I/DEBUG ( 2622): #10 pc 0000f4a9 /system/lib/libc.so (__libc_init+44)
I/DEBUG ( 2622): #11 pc 00002964 /system/bin/mount.exfat (_start+96)
Turns out this has been fixed (at least bandaided) but the fix never made it into the Cyanogen.
I compiled mount.exfat with the fix and tried it on my device, here's the fixed version (both default version and the one with symbols):
mount.exfat.tar.gz
How to install:
You need to be running Cyanogen 12.1 (I'm not sure if this binary will work for other versions, look below how to rebuild). Adb has to be enabled and granted root (this is done in developer settings, "Enable ADB", "Enable root for ADB") and otherwise adb has to be working.
Code:
adb shell
su
3. Remount your /system as read-write:
Code:
mount -o remount,rw -t ext4 /res/dev/system /system
Back to the host terminal,
Code:
adb pull /system/bin/mount.exfat mount.exfat.old
adb push mount.exfat /system/bin/
Push the version with symbols if you want to investigate a crash.
Reboot the device.
I've been on this version for a day and it really doesn't crash.
If you're using a different ROM or device (googled this topic) or want to build this yourself:
Checkout and build Cyanogen for your device somehow (you won't need most of it). There's lots of guides out there.
Apply the patch above to the /android/system/external/exfat/libexfat/node.c (simply type in the added lines).
You can build only libexfat by going there and executing mm (or even mmp to push mount.exfat to the phone automatically!) but it won't work until you build the whole distribution to that point at least once. (You don't have to build to the end)
Hope this helps someone and hope this is the correct forum because it doesn't let me post in android development.
Thanks. I just installed it, and it didnt crash on exFAT.
But then, when I double checked if the old mount.exfat file does still crash on exFAT, I couldnt reproduce the old bug.
It didnt crash anymore on my CM12.1 from 26.12.2016 (last nighty).
Maybe it was already fixed? Or I didn't test exact enough.
I have a SGS4.
It doesn't seem they accepted that patch. Here's the current code:
https://github.com/CyanogenMod/android_external_exfat/blob/cm-12.0/libexfat/node.c
Last change was in 2014:
https://github.com/CyanogenMod/android_external_exfat/blob/cm-12.0/libexfat/node.c
In exfat_flush_node, note how they do
if (!(node->flags & EXFAT_ATTRIB_DIRTY))
Without first checking that node is non-NULL.
So that part is not fixed. (Neither simply building the latest mount.exfat from the repo worked for me)
On the other hand, since the crash is not that common, it is probable that NULL only gets passed there under some special circumstances in the
first place. Perhaps whatever it was that triggered it in your case, it went away.
In any case I have changed the files, so the bug will never happen again
I "only" need now to change the sd-card back to exFAT again, which is a bit long, because since some months I have a 128 GByte sd-card.
But I will do it, because the 4 GB limit can make problems in future.
Switched today from FAT32 to exFAT, on my Mac with the 10 days free trial of Paragon, because in my sd-card there is a ext4 partition for the Link2SD which I heavily use.
That why it a bit more difficult to switch.
But works.
I had to reflash my phone (not a complete reset, just flash, because Wi-Fi didn't work anymore). This time I tried the snapshot, not the last nightly from 26.12.2016. I forgot to flash the fix and voila! I had again that bug! So I installed the mount.exfat fix and after reboot it works again! So I guess in some way, the bug has gone in the 26.12. last nightly version, even if the file is the same. Maybe in some other way the error is catched?
Don't know but am happy that this fix exists
Thank again!
THANKS ! , this fixed my problems
I was able to reproduce the error easily , every time I exited TomTom Go since I inserted my new 64 GB card , my /storage/sdcard1 would be unmounted
( Samsung Galaxy S4 Mini Duos / CM12.1 )
Installed your fix and it's working like a charm now .... I still have my external SD after exiting TomTom
Garfield1970 said:
... Samsung Galaxy S4 Mini Duos / CM12.1 ...
Click to expand...
Click to collapse
Is this the serranoltexx?
Which version of 12.1 did you have exactly, I mean from which date?
EDIT: no, seems to be the GT-I9192, which is not in the official CM Downloads to find.
Never mind.
Great! I had CM12.1 last snapshot on my old SGS2 and indeed that bluddy bug is present here as well.
Once again your fix helped a lot! Thank!
The last nightly of 12.1 is taken away from the download sites unfortunately so I had to install that buggy last snapshot, which has this bug but not the last nighly had it I remember from SGS4's CM12.1
Is this bug still there with CM13?
Hi Frank and all,
I kept away from CM for a while now, just because I never was able to get my LocusPro map directories on external SD to work propperly. Was CM12.1 by that time. Also the fix here in this thread seems to be made for CM12.1
Any hint on how to proceed with CM13? Is it all good out of the box now? Or can I apply this fix here to CM13 as well?
BR
Axel
I don't think this is good idea, but not know if I am wrong. I didn't need that patch on CM13 anymore.
BUT: on CM13 the external sdcard write restrictions from Google weren't fixed by CM anymore, so I needed other tools to fix it: [Xposed][MODULE][4.0+] XInternalSD
Only with this Xposed module I got running Locus again. The way to there was a pain in my glass.
But if you have root (which you must have for this fix anyway), it is easy to install. First Xposed, then this module (through Xposed).
This solved my problem with OsmAnd~ maps on /storage/sdcard1/.. (exfat external sdcard) on Note4 / CM12.1 / 20160106-nightly-trltexx
Just used your mount.exfat, no new build needed.
THANKS!
EDIT: Nintendo is not allowing their Miitomo app to run on Android phones with root, jailbroken iPhones, and some other conditions. The app will crash immediately or shortly after launch. To bypass this on Android phones install Xposed, then install RootCloak and ChrisJosten's Miitomo Bypass modules and reboot your device. Add Miitomo to RootCloak's list of cloaked apps, and be sure to 'Thanks!' ChrisJosten for his help.
Original text:
Tonight Nintendo has first released their Miitomo app exclusively to Japan, however the app apparently already has a full English translation.
Unfortunately it does not appear to run on rooted devices, as reported by a few users here. One user reported success with RootCloak, however others and myself have not had such success. I have a Galaxy S5 with CyanogenMod 13.0. The app starts with a black screen for a second before crashing back to the home screen. Tried clearing any cached data for the app. Any other ideas?
From what I gathered at Neogaf, it seems to be a CM problem, but I have no further idea
Not on CM and it's happening with me too.
On 5.1.1 with root, fix would be appreciated.
Looks to me to be a problem with cyanogen.
Here's an interesting line in the debug:
03-17 11:51:55.399 8036 8036 I art : Thread[1,tid=8036,Native,Thread*=0xb4d76500,peer=0x74f993b0,"main"] recursive attempt to load library "/data/app/com.nintendo.zaaa-2/lib/arm/libNuanceVocalizer.so"
03-17 11:51:55.618 8036 8036 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 8036 (m.nintendo.zaaa)
03-17 11:51:55.618 253 253 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
03-17 11:51:55.618 253 253 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
03-17 11:51:55.618 253 253 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
03-17 11:51:55.671 813 1584 D NetlinkSocketObserver: NeighborEvent{elapsedMs=68823126, 192.168.32.1, [544A009C3344], RTM_NEWNEIGH, NUD_STALE}
03-17 11:51:55.720 253 253 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-17 11:51:55.720 253 253 F DEBUG : Build fingerprint: 'oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS1N0:user/release-keys'
03-17 11:51:55.720 253 253 F DEBUG : Revision: '0'
03-17 11:51:55.720 253 253 F DEBUG : ABI: 'arm'
03-17 11:51:55.720 253 253 F DEBUG : pid: 8036, tid: 8036, name: m.nintendo.zaaa >>> com.nintendo.zaaa <<<
03-17 11:51:55.720 253 253 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
03-17 11:51:55.739 253 253 F DEBUG : r0 00000000 r1 00001f64 r2 00000006 r3 00000000
03-17 11:51:55.739 253 253 F DEBUG : r4 b6fcdb88 r5 00000006 r6 b6fcdb38 r7 0000010c
03-17 11:51:55.739 253 253 F DEBUG : r8 12ca4180 r9 b4d76500 sl 12c62c30 fp 70f4d6b0
03-17 11:51:55.739 253 253 F DEBUG : ip 00000000 sp beb02ef8 lr b6d1a42d pc b6d1cb90 cpsr 200d0010
03-17 11:51:55.745 253 253 F DEBUG :
03-17 11:51:55.745 253 253 F DEBUG : backtrace:
03-17 11:51:55.745 253 253 F DEBUG : #00 pc 00049b90 /system/lib/libc.so (tgkill+12)
03-17 11:51:55.745 253 253 F DEBUG : #01 pc 00047429 /system/lib/libc.so (pthread_kill+36)
03-17 11:51:55.745 253 253 F DEBUG : #02 pc 0001bbc3 /system/lib/libc.so (raise+10)
03-17 11:51:55.745 253 253 F DEBUG : #03 pc 0001846d /system/lib/libc.so (__libc_android_abort+36)
03-17 11:51:55.745 253 253 F DEBUG : #04 pc 000164cc /system/lib/libc.so (abort+4)
03-17 11:51:55.745 253 253 F DEBUG : #05 pc 009bf848 /data/app/com.nintendo.zaaa-2/lib/arm/libcocos2dcpp.so (Java_jp_co_nintendo_NativeSystem_nativeAbort+8)
03-17 11:51:55.745 253 253 F DEBUG : #06 pc 011218fd /data/app/com.nintendo.zaaa-2/oat/arm/base.odex (offset 0x985000)
03-17 11:51:56.064 253 253 F DEBUG :
03-17 11:51:56.064 253 253 F DEBUG : Tombstone written to: /data/tombstones/tombstone_03
03-17 11:51:56.064 253 253 E DEBUG : AM write failed: Broken pipe
Click to expand...
Click to collapse
Android N develop a no-go too
On launch of miitomo if running the android N developer preview you get a gray screen and that's it
I'm having the same problem. Rooted Wileyfox Swift running Cyanogen OS 12.1.1.
It's not just root
Have the same problem. But I'm bone stock 5.0 Note 3.
Galaxy S4 Resurrection Rom
Rooted - Crash
Un-rooted - Crash
Root Cloak - Crash
Nexus 10 CM13
Rooted - Crash
Un-rooted - Crash
Root Cloak - Crash
Galaxy S2 Stock
Crash
Literally cant get any device to work.
Thanks for the responses. I mean I wouldn't be surprised if Nintendo wanted to prevent cheating, but if this is a more widespread issue it might get fixed legitimately.
I'm using my Alcatel OT Idol X with Slimkat 4.4.2 and I'm getting crashes on both rooted and cloaked Miitomo. I haven't tried my other devices yet, but I doubt they'll fare out well.
app was crashing on my rooted Nexus 5X running stock 6.0.1, with ElementalX Kernel. All I did to fix it was use RootCloak and add Miitomo to the list. Bang, straight into the game
Same thing happening here.
Running on Android 4.4.4 with stock ROM.
Sent from my Micromax A065
harsh2909 said:
Same thing happening here.
Running on Android 4.4.4 with stock ROM.
Sent from my Micromax A065
Click to expand...
Click to collapse
Also here on Android 4.4.2 Rooted LG G3.
Nexus 5x - Systemless Root - Purenexus - Franco Kernel
Crashes every time.
Works fine on my wife's stock Samsung 5.
More and more apps are refusing to run on rooted devices. This should not be surprising. Some are even looking for xposed and monitoring the forums here to see how people are getting around it so they can block it.
Can confirm... I have a Motorola Droid 4 running CM11 and it crashes.
I tried updating to CM13 nightly, still crashes.
I tried disabling root from within CM, still crashes.
I went back to stock (rooted), still crashes.
I used superSU to unroot stock, it loaded.
This is infuriating, at least with Pokémon Shuffle it would load and let you play and just stop you from doing tournaments due to being rooted. This fake app crash GS is annoying. Someone needs to fix this :/
drfsupercenter said:
Can confirm... I have a Motorola Droid 4 running CM11 and it crashes.
I tried updating to CM13 nightly, still crashes.
I tried disabling root from within CM, still crashes.
I went back to stock (rooted), still crashes.
I used superSU to unroot stock, it loaded.
This is infuriating, at least with Pokémon Shuffle it would load and let you play and just stop you from doing tournaments due to being rooted. This fake app crash GS is annoying. Someone needs to fix this :/
Click to expand...
Click to collapse
Well see that's the thing is that it is not broken. Root is a security risk and an issue for game developers even Google is making root harder to get on Many devices and sooner or later unless you have a nexus root may not even be an option.
That's just stupid, I use root for things like taking backups of my phone, not hacking stupid games to begin with.
I do find it funny how the first thing that comes to people's mind when you tell them you have a rooted/jailbroken phone is that you must be some kind of pirate. You don't even need root to install .apks, and most people don't know enough to actually hack games like that anyway. (Pro tip: the leaderboards are kept server-side, it's not as simple as just modifying your data files)
drfsupercenter said:
That's just stupid, I use root for things like taking backups of my phone, not hacking stupid games to begin with.
I do find it funny how the first thing that comes to people's mind when you tell them you have a rooted/jailbroken phone is that you must be some kind of pirate. You don't even need root to install .apks, and most people don't know enough to actually hack games like that anyway. (Pro tip: the leaderboards are kept server-side, it's not as simple as just modifying your data files)
Click to expand...
Click to collapse
Well see the thing is root makes those things possible. There are apps that use root to hack the games. I won't mention them here as they are banned. Also it's not the leader boards they are worried about. It's things like in app purcheses.
You have to understand there are very real risks with root. An app can get granted root and do all types of things including ransom based viruses.
It's just something you will have to get used to. The older android gets the harder root will be to get.
I'm sure there will always be ways. While 99% of users don't need root abilities, there are those of us who are power users who have an actual use for it.
Even the newest phones have root exploits (I hate that word exploit, sure it's exploiting a locked-down system arbitrarily set by the manufacturer, but we should be able to do it like a real machine and choose if we want to allow root access or not!).... looks like the S7 has one already.