Carrier IQ Profile collection for EFF - Android General

Hey guys, an EFF volunteer - Jered Wierzbicki - has created an application called IQIQ to decode Carrier IQ profiles back to XML. Their public git repo is in the above linked article. In a nutshell, Profiles contain what data is sent back at what interval and to where.
We are now able to see sets of metrics called from phones. The problem is right now we only have default profiles. The EFF is looking to collect as many profiles from as many different devices as possible trying to find real metrics.
Github Proof of concept code for a "profile scraper": https://github.com/TrevE/IQTool
(right now it scans, but only works for automatic sending of archive.img from tmobile, but it should be for root or non root)
If you can contribute go for it! It would help to have a "one click profile sender" out there for everyone.
Possible Methods
FINDING .PRO FILES
We are not too sure yet where updated profiles get stored, so for the time being root users can run the following to search out all .pro files on your disk.
Code:
adb shell busybox find / -iname "*.pro"
It will likely be some sort of IQProfile.pro, CIQProfile.pro, defaultprofile.pro. Once you locate it just:
Code:
adb pull /full/path/to/profile.pro .
Other strategies, such as grepping for a characteristic string like " CONSTANT " across the whole filesystem, might also turn out to be useful. Use this thread to experiment with and improve such techniques!
Waiters suggests a command reference:
waiters said:
maybe something like this (which could take hours to run...)
Code:
grep -r "CONSTANT PROPID" /
Click to expand...
Click to collapse
Getting archive.img from non-embedded CIQ
We don't yet know if all profiles will be .pro files, or if they'll sometimes be embedded inside of other things. If you are on tmobile the profile information is potentially contained in an archive.img file. The file could be world readable, so you might not even need to be rooted.
WARNING ABOUT ARCHIVE.IMG FORMATS:
Please be warned that sensitive data could be in this archive.img file such as URLs, IMEI, SMS metadata, etc.. EFF will always do its best to keep archive.img files confidential, but please DO NOT send them if there may be any private information on the handset you are working with
Example of where Tmobiles CIQ archive is:
Code:
adb pull /data/data/com.carrieriq.tmobile/app_iq_archive/archive.img .
KNOWN STOCK MD5SUMS
Were really trying to find some new profiles containing the pushed metrics, so to check if you are looking at a "stock" profile or not (this only applies to if you find a .pro file)
Code:
adb shell busybox md5sum /path/to/profile.pro
If it matches one of these md5sums (number on the left) it is likely a known "stock" profile.
Code:
e37a4a8e3ea6d6aa4b7423a462541fa9 att-galaxy-s2-defaultProfile.pro
2618eaa2e3310ec36e1b86f8b643c5fa htc-amaze-tmob-defaultProfile.pro
a6886135d2d1ea423d4edde389fe1794 htc-evo-sprint-iqprofile.pro
2618eaa2e3310ec36e1b86f8b643c5fa tmob-defaultProfile.pro
SUBMITTING PROFILES
If you would like to submit your profile or archive.img to EFF so CarrierIQ metrics on what operator can be better understood, please send that data off to [email protected] . It would be very helpful to them to include phone model and network it was pulled from as well.
Thanks for all your help guys!

Portal article coming up. Thanks TrevE, and Jered and the EFF. We really appreciate everything you do.

Woot woot! Keep up the good work Treve!

Thanks again TrevE!! I have some friends with OG EVOS that are stock that can help and a buddy on ATT with an Atrix. I'll get them involved if possible. It's great to see them collecting evidence.

Any other names?
Code:
[email protected]:~/IQIQ$ adb shell
/ # busybox find / -iname "*.pro"
/data/data/pl.aygorund.littlepiano.pro
/ #
I'm sure "little piano" which was free on amazon 2 days ago is not Carrier IQ related.
Note:This is an AT&T Infuse 4G with a 4 month old custom kernel.

maybe something like this (which could take hours to run...)
Code:
grep -r "CONSTANT PROPID" /

I'm just glad it's out in the open, there's enough crap in the world to have to worry about, if your banking from your phone (no chance I would have in the first place but) there's a real threat and a legit reason to go in personally to change all of your accounts and who in the world has had all pass access to look at it for how long.
Thanks for the post man, this is that great eye opener that needed to happen I just hope nothing happens to anyone because of Carrier IQ. It's good to see there are others that are taking this seriously.

Will root explorer find this for us?

tried this on my sprint evo3d and got a odd response...
when I go into adb shell and type: busybox find / -iname "*.pro"
I get the following:
/system/etc/iqprofile.pro
find: /data/DxDrm/fuse: Permission denied
Thought this was odd since im fully rooted s-off here and would be denied access to something, no? The first few times I did it straight from the comand line and that resulted in only outputting the "...permission denied" line shown above. When I did "adb shell" first by itself and then did the second part of the command it gave me the iqprofile.pro....
any thoughts?

sgt. slaughter said:
tried this on my sprint evo3d and got a odd response...
when I go into adb shell and type: busybox find / -iname "*.pro"
I get the following:
/system/etc/iqprofile.pro
find: /data/DxDrm/fuse: Permission denied
Thought this was odd since im fully rooted s-off here and would be denied access to something, no? The first few times I did it straight from the comand line and that resulted in only outputting the "...permission denied" line shown above. When I did "adb shell" first by itself and then did the second part of the command it gave me the iqprofile.pro....
any thoughts?
Click to expand...
Click to collapse
I had to go into a shell, do the su command to gain root, and THEN do the search.

AdamOutler said:
Any other names?
Code:
[email protected]:~/IQIQ$ adb shell
/ # busybox find / -iname "*.pro"
/data/data/pl.aygorund.littlepiano.pro
/ #
I'm sure "little piano" which was free on amazon 2 days ago is not Carrier IQ related.
Note:This is an AT&T Infuse 4G with a 4 month old custom kernel.
Click to expand...
Click to collapse
Not sure, does the Infuse have CIQ?
sgt. slaughter said:
tried this on my sprint evo3d and got a odd response...
when I go into adb shell and type: busybox find / -iname "*.pro"
I get the following:
/system/etc/iqprofile.pro
find: /data/DxDrm/fuse: Permission denied
Thought this was odd since im fully rooted s-off here and would be denied access to something, no? The first few times I did it straight from the comand line and that resulted in only outputting the "...permission denied" line shown above. When I did "adb shell" first by itself and then did the second part of the command it gave me the iqprofile.pro....
any thoughts?
Click to expand...
Click to collapse
That system/etc/iqprofile.pro might get updated on the e3d, were not sure yet how that works. Can you run busybox md5sum on that file?
I will post known hashes for stuff EFF has already (default profiles).

TrevE said:
Not sure, does the Infuse have CIQ?
That system/etc/iqprofile.pro might get updated on the e3d, were not sure yet how that works. Can you run busybox md5sum on that file?
I will post known hashes for stuff EFF has already (default profiles).
Click to expand...
Click to collapse
just to be sure i did this right, heres what i did:
adb shell
/system/xbin/busybox md5sum system/etc/iqprofile.pro
this output the following:
a6886135d2d1ea423d4edde389fe1794 system/etc/iqprofile.pro
and btw im running the stock OTA with full CIQ and stock kernel here.

TrevE said:
Not sure, does the Infuse have CIQ?
That system/etc/iqprofile.pro might get updated on the e3d, were not sure yet how that works. Can you run busybox md5sum on that file?
I will post known hashes for stuff EFF has already (default profiles).
Click to expand...
Click to collapse
TrevE Im not sure if you mentioned this but I have been working on kernel and I came across code in kernel to do with carrier IQ

TrevE said:
Not sure, does the Infuse have CIQ?
That system/etc/iqprofile.pro might get updated on the e3d, were not sure yet how that works. Can you run busybox md5sum on that file?
I will post known hashes for stuff EFF has already (default profiles).
Click to expand...
Click to collapse
Voodoo says it does. I'm working on the grep search now
Code:
Voodoo Carrier IQ Detector report:
Build fingerprint:
samsung/SGH-I997/SGH-I997:2.3.6/GINGERBREAD/UCKJ4:user/release-keys
Test for: Linux kernel interfaces
(KERNEL_INTERFACES, confidence 50)
nothing found
Test for: Android logcat debugging log
(LOGCAT, confidence 100)
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: D/IQService( 363): Save Success test file:/sdcard/Android/netstate.txt
found: W/dalvikvm(15518): No implementation found for native Lcom/carrieriq/iqagent/client/NativeClient;.clientInit (Ljava/lang/Object;)I
found: W/dalvikvm(15518): No implementation found for native Lcom/carrieriq/iqagent/client/NativeClient;.clientInit (Ljava/lang/Object;)I
Test for: Linux kernel drivers
(KERNEL_DRIVERS, confidence 50)
nothing found
Test for: System services
(SERVICES, confidence 70)
found: 12 com.carrieriq.iqagent.service.IQService: [com.carrieriq.iqagent.interfaces.IService]
Test for: ROM binaries and daemons
(SYSTEM_BINARIES, confidence 70)
found: /system/xbin/iqbridged
found: /system/bin/iqmsd
found: /system/lib/libiq_service.so
found: /system/lib/libiq_client.so
Test for: ROM configs
(ETC_CONFIG, confidence 0)
nothing found
Test for: Packages
(PACKAGES, confidence 70)
nothing found
Test for: Running processes
(RUNNING_PROCESSES, confidence 200)
found: system 363 252 142180 16324 ffffffff 00000000 S android.iqd
Test for: Suspicious classes
(SUSPICIOUS_CLASSES, confidence 0)
found: com.carrieriq.iqagent.service.receivers.BootCompletedReceiver
Test for: Linux kernel dmesg log
(DMESG, confidence 100)
nothing found
--
Voodoo CarrierIQ Detector 1.4

I made a quick and dirty android app for searching / sending profiles. I will be polishing it up more, anyone else feel free to jump in here to. The more grep strings or other locations these profiles are found will be added in here.
Right now it works only for tmobile flawlessly. But it will work for non rooted tmobile users, so if you feel comfortable send this to everyone on tmo you know to get the ball rolling. There is a compiled copy in bin\
https://github.com/TrevE/IQTool

I hope it will work on unrooted stock. I have some candidates.
Sent from my Clean ROM 3D

guitardoc64 said:
I hope it will work on unrooted stock. I have some candidates.
Sent from my Clean ROM 3D
Click to expand...
Click to collapse
for tmo? it should the files are world readable - but it was quick and dirty code If not let me know and ill have er fixed up. Ill be cleaning up more in the next hours, just havta run up for a bit so i pushed my first checkpoint
{
"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"
}

Thank you.
i will have a try too.

TrevE said:
I made a quick and dirty android app for searching / sending profiles. I will be polishing it up more, anyone else feel free to jump in here to. The more grep strings or other locations these profiles are found will be added in here.
Right now it works only for tmobile flawlessly. But it will work for non rooted tmobile users, so if you feel comfortable send this to everyone on tmo you know to get the ball rolling. There is a compiled copy in bin\
https://github.com/TrevE/IQTool
Click to expand...
Click to collapse
cool deal.
you get a chance to see my response to you about md5sum you asked about?
just wanna know if i should send this file off or should i look for something else. lemme know if you want me to compare to anything you have on ur 3D. like i said mine is all stock kernel and all just on last OTA and rooted s-off.
TrevE said:
....
That system/etc/iqprofile.pro might get updated on the e3d, were not sure yet how that works. Can you run busybox md5sum on that file?
I will post known hashes for stuff EFF has already (default profiles).
Click to expand...
Click to collapse
just to be sure i did this right, heres what i did:
adb shell
/system/xbin/busybox md5sum system/etc/iqprofile.pro
this output the following:
a6886135d2d1ea423d4edde389fe1794 system/etc/iqprofile.pro
and btw im running the stock OTA with full CIQ and stock kernel here.
Click to expand...
Click to collapse

TrevE said:
for tmo? it should the files are world readable - but it was quick and dirty code If not let me know and ill have er fixed up. Ill be cleaning up more in the next hours, just havta run up for a bit so i pushed my first checkpoint.
Click to expand...
Click to collapse
For Sprint and ATT. 2 og EVOs and an Atrix.
Sent from my Clean ROM 3D

Related

[Resurrected][MOD] LG Cam V3.0 for OTA Based Roms [ (10/28/11)]

Bounty Link:
Use this to Donate to the Project Itself for all of those involved in the hardwork Jface,Doniqq, and myself
Bugs List (Last updated 9/5/11)
Code:
-FFC Squished on some versions
-FFC roatated 90 Degrees CW on V1.5 & Up
-FFC @ Full Res Video still shows green boxes (missing libs?)
Update (9/5/11): LG Cam V3.0 -Major Fixes in this one
Testing now... if all goes well expect update package shortly. 2:42AM EST
Stitch Shot: Confirmed working
Panorama Shot: Confirmed Working
Continuous Shot: Confirmed Working
Zoom while recording Video in all modes : Confirmed working
Touch to focus : Confirmed Working
Taking Pictures in portrait flipped : Confirmed working
Recording at 1080P @ 24 FPS / 720P @ 30 FPS : Confirmed Working
Download LG Cam V3.0: Here
Update (8/5/11): LGCam V1.5 - Fxied for Real This Time - for the trolls i mean the update package
Download LGCam V1.5: Here
THIS WILL NOT WORK ON CM7 OR ANYTHING BASED ON CM7/AOSP FOR NOW
Restore AOSP/OTA GB Cam
V1.4
Don't want to talk about it
Code:
V1.5 Updates:
-Fixed ZIP Package, now flashable, I promise (Damn Signtool replaced the com folder :/) :o
-Fixed 1080P @ 24FPS/30 FPS same as stock FROYO
-Fixed Zoom while recording Video
- Stock Cam Icon
- Still needs to fix FFC
-Enjoy, Report any bugs in the thread
-Donate and help me buy a bottle of Belevedere Black:)
V1.4
Burning in hell somewhere
Click to expand...
Click to collapse
flak0 said:
Hey Devs and ofcourse Doniqq first off amazing work on EB i love it. Im using the FR version. Ok so basically I am posting this thread because I figured out for sure why the LG Camera will not work on GB. It is not a lack of drivers like everyone has said. Basically when the Camera.Apk(LG Camera) is launched it looks for Libamce.so (i figured this out by reverse engineering the LG Camera and found the referrence on where it looks for the shared library libamce.so.) I went ahead and tried to push the LG Camera with the libamce.so yet still got a force close, this time the error was a reloc lbrary error looking for a _NZCamera6Connect function. I then went ahead an decompiled the libamce.so and found that it depends on libnvomx.so, then I decompiled libnvomx.so and found that it depends on libm.so, then I tried pushing all three libs to GB and still got a force close. After digging deep enough I found that libm.so depends on libcamera_client.so which I also decompiled and then I found the _NZCamera6Connect fuction is contained here. I attempted to push the libcamera_cleint.so to to GB and boot failed, then I tried editing the update-zip file to include the libcamera_client.so (From Froyo) and boot also failed. I am positive that once we get this libcamera_client.so ported from FROYO to GB the LG Camera will work. Luckily there is no dependency on the framework. This is where I need your help since I know your the dev who made EB possible or any Dev thats out there Faux, Morific Thanks.
Here is the header of the decompiled libamce.so just in case:
Click to expand...
Click to collapse
I'm no dev, but I just want to thank you for continuing to try and bring the LG cam to Gingerbread. Hopefully a dev will gladly help you out with this issue. Once again thank you for taking the time to try and get this hard headed app to work.
Sent from my LG-P999 using XDA Premium App
[depricated as of 9/5/11 - history of lgcam on gb]
Update (8/3/11): LG CAM for CM7 removed until fixed. Too many people were flashing on MIUI and CM7 Based ROMS
New Version for Stock OTA based ROMS coming out tonight.
Proposed fixes include -> 24/30 FPS @ 1080P and Zoom while video recording
Also moved some of the original OP two posts down to clean up the OP.
Update(8/2/11): LG Cam for CM 7 Beta
Below is what you have all been asking for, it is a beta of LG Cam for CM7. If you are willing to take the risk go ahead and flash BUT FIRST MAKE SURE YOU NANDROID. I have also attached CM7 Cam again if it fails to work and/or if you wish to go back. Please update the thread with any errors, logcats preferred.
Edit: Update(8/2/11 @ 4:42AM EST) below.
I was able to Port the LGE folder from GB to CM7 into the framework successfully however now when I open the CAM I am getting a null pointer exception. Anyone willing to help here please.
Code:
I/ActivityManager( 1074): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.camera/.ArcCamera } from pid 1279
I/ActivityManager( 1074): Start proc com.android.camera for activity com.android.camera/.ArcCamera: pid=3750 uid=10034 gids={1006, 1015}
D/ ( 984): NVRM_DAEMON(819): rt_exist=2, add client ref
D/ ( 984): set continue (1280x960)
D/ ( 984): set continue (1280x1024)
D/ ( 984): set continue (1280x1024)
D/ ( 984): set continue (1360x768)
D/ ( 984): set continue (1440x900)
D/ ( 984): set continue (1680x1050)
D/ ( 984): set BetterMode (1280x720)
D/ ( 984): set BetterMode (1920x1080)
D/ ( 984): set BetterMode (1280x720)
D/ ( 984): set BetterMode (1920x1080)
D/ ( 984): set BetterMode (1920x1080)
D/ ( 984): set BetterMode (1920x1080)
D/ ( 984): set BetterMode (1920x1080)
I/WindowManager( 1074): Setting rotation to 1, animFlags=1
I/ActivityManager( 1074): Config changed: { scale=1.0 imsi=310/260 loc=en_US touch=3 keys=1/1/2 nav=1/1 orien=2 layout=34 uiMode=17 seq=7 themeResource=null}
I/PowerWidget( 1243): Clearing any old widget stuffs
I/PowerWidget( 1243): Setting up widget
I/PowerWidget( 1243): Default buttons being loaded
I/PowerWidget( 1243): Button list: toggleWifi|toggleBluetooth|toggleGPS|toggleSound
I/PowerWidget( 1243): Setting up button: toggleWifi
I/PowerWidget( 1243): Setting up button: toggleBluetooth
I/PowerWidget( 1243): Setting up button: toggleGPS
I/PowerWidget( 1243): Setting up button: toggleSound
D/szipinf ( 3750): Initializing inflate state
I/===ArcCamera=== 1.1.0.1( 3750): Performance log:Load so2011-08-02 08:36:10.376 cost:6ms
I/===ArcCamera=== 1.1.0.1( 3750): Performance log:Launch camera
[color="blue"][size="4"]major update 7/28/11[/size]
[/color]
working lg cam on 2.3.3 ota & xborders stock rom (huge thanks to jumaaneface) once the cam is confirmed working on cm7 & aosp the bounty will be paid. I will also be looking into the actual cam app by decompiling source to see if we can fix the 1080p recording to make it record at 30 fps.
Again thanks to all the supporters and to jumaaneface who made this possible.
:d hey devs and ofcourse doniqq first off amazing work on eb i love it. Im using the fr version. Ok so basically i am posting this thread because i figured out for sure why the lg camera will not work on gb. It is not a lack of drivers like everyone has said. Basically when the camera.apk(lg camera) is launched it looks for libamce.so (i figured this out by reverse engineering the lg camera and found the referrence on where it looks for the shared library libamce.so.) i went ahead and tried to push the lg camera with the libamce.so yet still got a force close, this time the error was a reloc lbrary error looking for a [b]_nzcamera6connect[/b] function. I then went ahead an decompiled the libamce.so and found that it depends on libnvomx.so, then i decompiled libnvomx.so and found that it depends on libm.so, then i tried pushing all three libs to gb and still got a force close. After digging deep enough i found that libm.so depends on libcamera_client.so which i also decompiled and then i found the [b]_nzcamera6connect[/b] fuction is contained here. I attempted to push the libcamera_cleint.so to to gb and boot failed, then i tried editing the update-zip file to include the libcamera_client.so (from froyo) and boot also failed. I am positive that once we get this libcamera_client.so ported from froyo to gb the lg camera will work. Luckily there is no dependency on the framework. This is where i need your help since i know your the dev who made eb possible or any dev thats out there faux, morific thanks.
[b]update(7/27/11): Bounty increased to $100.00 thanks to:
[quote]eleeo037037 :$10
adevilfish :$10
bakedpatato : $5.00[/quote][/b]
[b]major update (7/26/11)
since the ota is official and the lg cam is not contained i am starting a bounty at $75.00 for the first person who can figure this out. I have tried numerous attempts using different approaches to no avail. There are others in the thread who mentioned they will also put up a bounty. I alone will pay $75.00 plus whatever anyone else decides to throw in the pot. [/b]
[b]update 3 (7/22/11): Attempted again to change some files in the framework and upon boot logcat threw error for missing decl from the camera$files in the framework. I pushed the libcamera_client.so from froyo and then the messaged changed to this:
[quote]i//system/xbin/busybox( 1015): Sysctl: /etc/sysctl.conf: No such file or directory
i//system/xbin/busybox( 1015): -k: No such file or directory
i//system/xbin/busybox( 1015): [: 61m: Bad number[/b][/quote]
[b]update 2(7/22/11) : Flashing eb 1.0.5 gr v21e rom with modified framework and it failed, so i pushed libcamera_client.so and it failed, error below [/b]
[quote]- waiting for device -
--------- beginning of /dev/log/main
i/netd ( 1018): Netd 1.0 starting
--------- beginning of /dev/log/system
i/vold ( 1017): Vold 2.1 (the revenge) firing up
d/vold ( 1017): Usb_configuration switch is not enabled in the kernel
d/vold ( 1017): Volume extsdcard state changing -1 (initializing) -> 0 (no-media)
d/vold ( 1017): Volume sdcard state changing -1 (initializing) -> 0 (no-media)
d/vold ( 1017): Volume extsdcard state changing 0 (no-media) -> 1 (idle-unmounted)
w/vold ( 1017): Duplicate state (1)
d/vold ( 1017): Volume sdcard state changing 0 (no-media) -> 1 (idle-unmounted)
w/vold ( 1017): Duplicate state (1)
w/vold ( 1017): Duplicate state (1)
i/debug ( 1019): Debuggerd: Jul 15 2011 10:15:43
d/ ( 1029): Open is ok, now, we are in user_land!
D/ ( 1029): Set continue (1280x960)
d/ ( 1029): Set continue (1280x1024)
d/ ( 1029): Set continue (1280x1024)
d/ ( 1029): Set continue (1360x768)
d/ ( 1029): Set continue (1440x900)
d/ ( 1029): Set continue (1680x1050)
d/ ( 1029): Set bettermode (1280x720)
d/ ( 1029): Set bettermode (1920x1080)
d/ ( 1029): Set bettermode (1280x720)
d/ ( 1029): Set bettermode (1920x1080)
d/ ( 1029): Set bettermode (1920x1080)
d/ ( 1029): Set bettermode (1920x1080)
d/ ( 1029): Set bettermode (1920x1080)
d/kipc ( 1020): Kipc_init()
d/kipc ( 1020): Address is 127.0.0.1, port is 45211
d/kipc ( 1020): Binding...
D/kipc ( 1020): Listening...
D/kipc ( 1020): Accepting...
D/ganril ( 1020): Gan ril starting
d/ganril ( 1020): Entering main loop
d/ganat ( 1020): 65 6e 74 65 72 69 6e 67 20 6d 61 69 6e 4c 6f 6f
d/ganat ( 1020): 70 28 29
d/ganat ( 1020): Gan_at_open
d/ganpsat ( 1020): Gan_ps_at_open
d/ganat ( 1020): Additional logging enabled. Going to call readline()
d/ganat ( 1020): Readline
d/ganat ( 1020): Readline : Before read
i/ ( 1030): Screencaptured accept lsocket: 9
i/vold ( 1017): Usb_mass_storage function disabled
e/netlinkevent( 1017): Netlinkevent::findparam(): Parameter 'switch_name' not found
e/netlinkevent( 1017): Netlinkevent::findparam(): Parameter 'switch_state' not found
w/vold ( 1017): Switch /devices/virtual/switch/usb_mass_storage event missing name/state info
i/rescuestarter( 1026): Rescuestarter 6.3.274 starts
i/rescuestarter( 1026): Ready, waiting for connection
e/netlinkevent( 1017): Netlinkevent::findparam(): Parameter 'switch_name' not found
e/netlinkevent( 1017): Netlinkevent::findparam(): Parameter 'switch_state' not found
w/vold ( 1017): Switch /devices/virtual/switch/usb_mass_storage event missing name/state info
i//system/xbin/busybox( 1015): Sysctl: /etc/sysctl.conf: No such file or directory
i//system/xbin/busybox( 1015): -k: No such file or directory
i//system/xbin/busybox( 1015): [: 61m: Bad number
i/vold ( 1017): Usb_mass_storage function enabled
d/vold ( 1017): Share method ums now available
i//system/xbin/busybox( 1015): Mount: Invalid argument
i//system/xbin/busybox( 1015): Run-parts: /system/etc/init.d/10ext4tuneup exited with code 255
i//system/xbin/busybox( 1015): Starting automatic zipalign 07-22-2011 22:21:12
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /data/app/*.apk
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /system/app/accountandsyncsettings.apk
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /system/app/applicationsprovider.apk
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /system/app/bluetoothopp.apk
i//system/xbin/busybox( 1015): Zipalign: Not found
i//system/xbin/busybox( 1015): Zipalign already completed on /system/app/bluetoothpbap.apk
i//system/xbin/busybox( 1015): Zipalign: Not found[/quote]
[b]update 7/22/11 - working on patching and porting elements from the froyo framework to gb[/b]
[img]http://forum.xda-developers.com/attachment.php?attachmentid=662618&stc=1&d=1311355083[/img]
[b](7/21/11)major update: Lg releases stock gb rom v21e however lg cam is not on board. This thread will.continue until we can successfully port the lg cam to gb. [/b]
[b]update 7/20/2011:
[quote]status update: Spoke with doniqq via pm he is working hard for us (so please thank him) to port the lg cam from froyo to gb. I am going to take another stab at this tonight and check 1 more thing. For those that had/have the nexus 1, i was the one who successfully ported the cm camera to rodriguez miui when everyone thought it was impossible. I am pretty sure the framework.jar is not part of this however when i moved the cm 7 cam to miui i did modify the framework, so i will take a look at this tonight before ruling it out completely.
[/quote][/b]
[b]here is the header of the decompiled libamce.so just in case:[/b]
[quote].plt:000459f4 ;
.plt:000459f4 ; +-------------------------------------------------------------------------+
.plt:000459f4 ; | this file has been generated by the interactive disassembler (ida) |
.plt:000459f4 ; | copyright (c) 2009 by hex-rays, |
.plt:000459f4 ; | license info: B3-ada1-9d85-df |
.plt:000459f4 ; | licensed user |
.plt:000459f4 ; +-------------------------------------------------------------------------+
.plt:000459f4 ;
.plt:000459f4 ; input md5 : 2ebb5ff4c8e8cf34c40ffc3aed9e8042
.plt:000459f4
.plt:000459f4 ; ---------------------------------------------------------------------------
.plt:000459f4 ; file name : C:\users\flak0-hpn3\downloads\libamce.so
.plt:000459f4 ; format : Elf (shared object)
.plt:000459f4 ; imagebase : 8000
.plt:000459f4 ; needed library 'libcamera_client.so'
.plt:000459f4 ; needed library 'libsurfaceflinger_client.so'
.plt:000459f4 ; needed library 'libui.so'
.plt:000459f4 ; needed library 'liblog.so'
.plt:000459f4 ; needed library 'libcutils.so'
.plt:000459f4 ; needed library 'libutils.so'
.plt:000459f4 ; needed library 'libhardware.so'
.plt:000459f4 ; needed library 'libmedia.so'
.plt:000459f4 ; needed library 'libandroid_runtime.so'
.plt:000459f4 ; needed library 'libc.so'
.plt:000459f4 ; needed library 'libm.so'
.plt:000459f4 ; needed library 'libstdc++.so'
.plt:000459f4 ; needed library 'libdl.so'
.plt:000459f4 ; needed library 'libbinder.so'
.plt:000459f4 ; needed library 'libskia.so'
.plt:000459f4 ; needed library 'libicuuc.so'
.plt:000459f4 ; needed library 'libegl.so'
.plt:000459f4 ; needed library 'libnvomx.so'
.plt:000459f4 ;
.plt:000459f4 ; eabi version: 5
.plt:000459f4 ;
.plt:000459f4
[/quote][/quote]
Click to expand...
Click to collapse
anybody try contacting faux or morfic to see if they could take a look? They are both very cool guys. I can talk to them if you want.
I have a silly question? If you use titanium back up and restore the LG camera would that work? If not, why?
I contacted both of them plus numerous devs.
jdkackley said:
anybody try contacting faux or morfic to see if they could take a look? They are both very cool guys. I can talk to them if you want.
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App
ClausMontoya said:
I have a silly question? If you use titanium back up and restore the LG camera would that work? If not, why?
Click to expand...
Click to collapse
I know it wont work but I couldnt tell you why. I thought the same thing and have tried it.
bls2633 said:
I know it wont work but I couldnt tell you why. I thought the same thing and have tried it.
Click to expand...
Click to collapse
Doesn't Titanimum just back up the apk file and not the compiled shared object?
Even so it'd be scary to think that it would somehow overwrite shared objects, potentially breaking the OS.
ClausMontoya said:
I have a silly question? If you use titanium back up and restore the LG camera would that work? If not, why?
Click to expand...
Click to collapse
I believe that what has been explained above is that there are libraries that the apk depend on to function that are not available on CM7 at the moment. (I could be wrong though)
yeah it's a similar reason if you backup DSP Manager from CM7 and try to install it on stock it will basically do nothing.
hey everyone i am still waiting for some devs to respond. Doniqq said he would take a look and let me know. We are 90% to having the LG Cam on GB.
If anyone else is good with shared objects in Android let me know.
Can you post the libcamera_client.so decompiled?
In theory this should be fairly simple to compile under gingerbread.
Scyth3 said:
Can you post the libcamera_client.so decompiled?
In theory this should be fairly simple to compile under gingerbread.
Click to expand...
Click to collapse
I can post it but i don't think it will compile, Remember i used a deconplier to reveal the source.
Sent from my LG-P999 using XDA App
I'll join in on this when I get home later. Has anyone tried contacting LG? They seem pretty reasonable.
Nah he means like talking to them about the camera drivers and what not I'm sure he wont say he'd trying to convert there froyo camera app to work with gingerbread lol they should be pretty reasonable
Yeah that's what I meant. I figure if there's something we need they might be able to help us. OP PM me
Status Update: 7/20/2011 US EST
Status Update: Spoke with Doniqq via PM he is working hard for us (so please thank him) to port the LG Cam from Froyo to GB. I am going to take another stab at this tonight and check 1 more thing. For those that had/have the Nexus 1, I was the one who successfully ported the CM Camera to Rodriguez MIUI when everyone thought it was impossible. I am pretty sure the framework.jar is not part of this however when I moved the CM 7 cam to MIUI I did modify the framework, so I will take a look at this tonight before ruling it out completely.
Thank u everyone, your thank yous motivate that much more. I will keep u updated.
Sent from my LG-P999 using XDA App
Its solved because i believe the reason why the LG cam won't work has been found and the culprit is the libcamera_client.so from Froyo to GingerBread. Its now requires the work of a dev to port. Just saying
Sent from my LG-P999 using XDA App
Thanks to Chuckhriczko who is also jumping on board to help.
Faux responded and respectfully informed me that he is working on several projects however if he has some spare time he will take a look for us.
Sent from my LG-P999 using XDA App

Android Clients checkin?

Code:
-----------------------------------------------LOGCAT-----------------------------------------------
D/ConnectivityService( 334): handleInetConditionHoldEnd: net=1, condition=100, published condition=0
I/CheckinTask( 642): Checkin success: https://android.clients.google.com/checkin (1 requests sent)
D/CAT ( 526): CatService: SIM ready. Reporting STK service running now...
D/MccTable( 526): updateMccMncConfiguration: mcc=505, mnc=2
D/MccTable( 526): locale set to en_au
D/MccTable( 526): WIFI_COUNTRY_CODE set to au
I/WifiService( 334): WifiService trying to set country code to au with persist set to true
I/ActivityManager( 334): Config changed: {1.15 505mcc2mnc en_AU sw320dp w320dp h455dp nrml port finger -keyb/v/h -nav/h s.5 themeResource=null}
D/SystemClock( 526): Setting time of day to sec=1358505394
D/AlarmManagerService( 334): Kernel timezone updated to -660 minutes west of GMT
V/AlarmClock( 724): AlarmInitReceiver finished
I/CheckinService( 642): Preparing to send checkin request
I/EventLogService( 642): Accumulating logs since 1358505385569
I/CheckinTask( 642): Sending checkin request (2128 bytes)
I/CheckinTask( 642): Checkin success: https://android.clients.google.com/checkin (1 requests sent)
W/ThrottleService( 334): unable to find stats for iface rmnet0
On boot, this happens. And it just hangs here. No bootloop, no crashing, just waiting for something I don't understand.
Cm10 Beta 2, Linux 3.0.16
Nothing interesting in dmesg.
EDIT: re-flashed rom and fixed, but still, I'd to know what happened.
What's wrong? Logcat states no error or warning
Can't get your point!
Sent from my HTC Explorer A310e using xda premium
DanceOff said:
What's wrong? Logcat states no error or warning
Can't get your point!
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
It starts some process during boottime, and just waits for it, and never actually boots, because it is waiting for a response. No errors reported anywhere.
gnustomp said:
It starts some process during boottime, and just waits for it, and never actually boots, because it is waiting for a response. No errors reported anywhere.
Click to expand...
Click to collapse
You mean there is no loop bit still phone doesn't boot !
Now I get you
What rom/mod are you flashing ?
Sent from my HTC Explorer using xda premium

[Guide] How To Logcat

I think this one is definitely needed for this forum as i am seeing more and more users ask how to logcat. So posting this here.
Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
From Moscow Desire:
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Update for windows users:
Thank go to FuzzyMeep Two, Here's what he's posted for windows
(If you used his tool, here's his post, thank him for his work!)
Note : I am just sharing. Original post here.
Good work, Khizar. A very handy and usefull guide. Thanks.
Perfect idea! Very good guide!!! As usual! Amazing job, my friend!
Sent from my SM-G900F using Tapatalk
Pierre118 said:
Good work, Khizar. A very handy and usefull guide. Thanks.
Click to expand...
Click to collapse
daxgirl said:
Perfect idea! Very good guide!!! As usual! Amazing job, my friend!
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Thank you both but JFYI this isn't my work. I shared this guide on my previous phone and since it's so good and there is ALOT of need I shared it here as well. I mentioned that in the OP.
Sent From My SM-N9005 To All You Wonder Nobodies!!
Due to the lack of mods, trolls can ruin the XDA forum's. Don't feed them...Instead report them.
Click to expand...
Click to collapse
daxgirl said:
Perfect idea! Very good guide!!! As usual! Amazing job, my friend!
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
agree !
Khizar said:
Thank you both but JFYI this isn't my work. I shared this guide on my previous phone and since it's so good and there is ALOT of need I shared it here as well. I mentioned that in the OP.
Sent From My SM-N9005 To All You Wonder Nobodies!!
Click to expand...
Click to collapse
Though not pure your own work, but noobies will need it, especially to send a log back to devs to know what is the problem.
And it's a good thing to share here.
:good:
antique_sonic said:
agree !
Though not pure your own work, but noobies will need it, especially to send a log back to devs to know what is the problem.
And it's a good thing to share here.
:good:
Click to expand...
Click to collapse
Appreciate the support brother...
Sent From My SM-G900F-Morphed SM-N9005 With XNote Goodness To All You Wonder Nobodies!!
Due to the lack of mods, trolls can ruin the XDA forum's. Don't feed them...Instead report them.
Click to expand...
Click to collapse
Khizar said:
Appreciate the support brother...
Sent From My SM-G900F-Morphed SM-N9005 With XNote Goodness To All You Wonder Nobodies!!
Click to expand...
Click to collapse
No worries Bro.
Sent from somewhere under the sky, at the corner of this rounded earth.
Great idea bro. We finally have a proper logcat thread for our Note3. ?
Sent from my SM-G900F using Tapatalk
fahadali2315 said:
Great idea bro. We finally have a proper logcat thread for our Note3. ?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
:good:

[Q] Google play services crash IDK?

Hi
I updated my Google Play services to latest and I have been getting this notification when I go to Internet wifi or mobile data.
authorization problem if the problem persists please log in and log out and try it again.
I do not want to make factory reset until CM12 comes out.
here is logcat
Code:
--------- beginning of /dev/log/main
--------- beginning of /dev/log/system
E/wpa_supplicant( 2513): wpa_driver_nl80211_driver_cmd: failed to issue private commands
E/WifiStateMachine( 794): Unexpected BatchedScanResults :null
E/wpa_supplicant( 2513): wpa_driver_nl80211_driver_cmd: failed to issue private commands
E/ConnectivityService( 794): Unexpected mtu value: [email protected]
E/PlayEventLogger( 3088): Invalid device id 9cb3889439509678
E/PhoneMonitor( 3153): onOtaspChanged old =0, new =3
E/AudioManagerAndroid( 3182): BLUETOOTH permission is missing!
E/AudioManagerAndroid( 3385): BLUETOOTH permission is missing!
F/ActivityManager( 794): Service ServiceRecord{42866038 u0 com.google.android.music/.net.NetworkMonitor} in process ProcessRecord{42e61648 3088:com.google.android.music:main/u0a65} not same as in map: null
F/ActivityManager( 794): Service ServiceRecord{427a3950 u0 com.google.android.music/.preferences.MusicPreferenceService$MusicPreferenceServiceBinder} in process ProcessRecord{42e61648 3088:com.google.android.music:main/u0a65} not same as in map: null
E/AuthorizationBluetoothService( 1571): Proximity feature is not enabled.
E/GCoreFlp( 1608): Bound FusedProviderService with LocationManager
E/AudioManagerAndroid( 3758): BLUETOOTH permission is missing!
E/dalvikvm( 3798): Could not find class 'android.app.Notification$Action$Builder', referenced from method f.a
E/dalvikvm( 3798): Could not find class 'android.app.RemoteInput[]', referenced from method f.a
E/SQLiteLog( 3798): (1) no such table: mmsconfig
E/Babel ( 3798): canonicalizeMccMnc: invalid mccmnc nullnull
P.S: I have removed google play services and updated it back still this problem is there. Then when I change my language to English notification stays in my language
EDIT: It is pure stock no Root or anything!
Same error
I have the same error "PlayEventLogger( 3088): Invalid device id" on my Moto G 1st gen

How to make an old app work on android pie?

I would like to know what I need do for an old app to work on Android Pie and how can I do that too.
The developer abandoned the app but it is very useful to me. In my last smartphone (android Lollipop 5.1.1) the app worked well but in my new smartphone (android Pie 9) it installs but when I open it immediatlly is showed a message that it stoped and need to be closed.
I use "APK Easy Tool v1.56 Portable" to edit apks but I don't know what exactly to do.
I thought that was about this message: "This app was built for an older version of Android and may not work properly. Try checking for updates, or contact the developer."
So, I changed the API version to 28 and the message disappeared but the stop and close app problem continue.
Thank you for any help.
robrazil said:
I would like to know what I need do for an old app to work on Android Pie and how can I do that too.
The developer abandoned the app but it is very useful to me. In my last smartphone (android Lollipop 5.1.1) the app worked well but in my new smartphone (android Pie 9) it installs but when I open it immediatlly is showed a message that it stoped and need to be closed.
I use "APK Easy Tool v1.56 Portable" to edit apks but I don't know what exactly to do.
I thought that was about this message: "This app was built for an older version of Android and may not work properly. Try checking for updates, or contact the developer."
So, I changed the API version to 28 and the message disappeared but the stop and close app problem continue.
Thank you for any help.
Click to expand...
Click to collapse
Did you boot to recovery and wipe the cache partition after installing the modified app?
This isn't exactly what you are looking for, but it is very close, you just need to modify the method a little to go from Lollipop to Pie the way this video describes going from Oreo to Nougat. What you want is to port your older app to work with newer android instead of porting a newer app to work with older android as the video describes.
https://m.youtube.com/watch?v=kck1EyhFDm4
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Did you boot to recovery and wipe the cache partition after installing the modified app?
Click to expand...
Click to collapse
Thank you for answer me but my smartphone isn't root and haven't options on recovery boot mode.
This isn't exactly what you are looking for, but it is very close, you just need to modify the method a little to go from Lollipop to Pie the way this video describes going from Oreo to Nougat. What you want is to port your older app to work with newer android instead of porting a newer app to work with older android as the video describes.
https://m.youtube.com/watch?v=kck1EyhFDm4
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I saw the video.
Like I said, had already changed the API version to 28 using the "APK Easy Tool v1.56 Portable" and editing the apktool.yml file on lines:
PHP:
sdkInfo:
minSdkVersion: '26'
targetSdkVersion: '28'
Both lines had number '8'.
Even so, as explained in the video, I downloaded and installed the Apk Editor PRO app and following step by step, changing "Minimum SDK Version" from 8 to 26 and "Target SDK Version" from 8 to 29, but the same problem continues.
When I press the app icon, it not open and is showed this popup message:
{
"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"
}
So, only change the SDK version isn't solving.
I don't know if structure of folders or anything else is different between apps for Lollipop and Pie that block to be installed, because I have 2 others old app that I installed and despite the old app alert message they are working rigth.
robrazil said:
Thank you for answer me but my smartphone isn't root and haven't options on recovery boot mode.
I saw the video.
Like I said, had already changed the API version to 28 using the "APK Easy Tool v1.56 Portable" and editing the apktool.yml file on lines:
PHP:
sdkInfo: minSdkVersion: '26' targetSdkVersion: '28'
Both lines had number '8'.
Even so, as explained in the video, I downloaded and installed the Apk Editor PRO app and following step by step, changing "Minimum SDK Version" from 8 to 26 and "Target SDK Version" from 8 to 29, but the same problem continues.
When I press the app icon, it not open and is showed this popup message:
View attachment 4964951
So, only change the SDK version isn't solving.
I don't know if structure of folders or anything else is different between apps for Lollipop and Pie that block to be installed, because I have 2 others old app that I installed and despite the old app alert message they are working rigth.
Click to expand...
Click to collapse
There is a PC version of APKtool that can be used to modify the apk file, you don't need root or apps that use root or custom recovery to achieve this.
Yes, each android version has slightly different partition structure, you need to edit the apk file so that it references the correct partitions/folders and files to find and use the other software resources on your devive that it needs.
You just need to modify the apk file then transfer it to your phone's internal storage then install it using your phones file manager app. You will have to enable the "unknown sources" setting in system settings.
Sent from my SM-S767VL using Tapatalk
There is a PC version of APKtool that can be used to modify the apk file, you don't need root or apps that use root or custom recovery to achieve this.
Click to expand...
Click to collapse
Thank you but like I said, already use "APK Easy Tool v1.56 Portable" for windows:
https://forum.xda-developers.com/an...tool-apk-easy-tool-v1-02-windows-gui-t3333960
You just need to modify the apk file then transfer it to your phone's internal storage then install it using your phones file manager app. You will have to enable the "unknown sources" setting in system settings.
Click to expand...
Click to collapse
I already did some small modifications in some apps too.
Yes, each android version has slightly different partition structure, you need to edit the apk file so that it references the correct partitions/folders and files to find and use the other software resources on your devive that it needs.
Click to expand...
Click to collapse
That is the point.
I think some questions need to be answered to resolve this issue:
1- What is really happening to block, to stop the application from running?
2- What needs to be changed in the application?
3- How can changes be made?
4- This webpage content could help?
https://developer.android.com/about/versions/pie/android-9.0-migration
5- There is some windows program where an android app can be installed, choosing the sistem android who do you want to install it (lollipop, marshmallow, Pie, etc), and is showed the app errors that to be fix for it work on the android version choosen?
Thanks for any help.
I tested the apk in virtual android of webpage https://appetize.io/ and it worked in virtual Android 6.0, 7.1, 8.1 until on android 10. Only android 9.0 didn't work. I don't belive that. Seems a joke.
On android 10, after install, is showed the permission screen asking to give it to the camera and the storage. After press "next", the app is open and works right. I tried changing the permissions on Android 9 but didn't work to make the app opening.
Does anyone have any idea what might be happening?
This app was created to SDK 8 (android 2.2 - Froyo)
I don't know if that can be help but below I pasted the debug log of there. I simulated in Android 4.4, 9.0 and 10, to serve as comparison between the android versions. In 4.4 and 10 versions worked, but didn't on 9 version:
Code:
[B][COLOR="Red"]Log messages will follow once session has started... [U](ANDROID 4.4)[/U][/COLOR][/B]
W/GAV2 ( 2986): Thread[main,5,main]: Need to call initialize() and be in fallback mode to start dispatch.
E/SQLiteLog( 2986): (1) no such table: MOEDA
E/SQLiteLog( 2986): (1) no such table: boletos
D/dalvikvm( 2986): GC_CONCURRENT freed 176K, 9% free 3443K/3780K, paused 0ms+0ms, total 2ms
D/dalvikvm( 2986): GC_FOR_ALLOC freed 1K, 9% free 3441K/3780K, paused 4ms, total 4ms
I/dalvikvm-heap( 2986): Grow heap (frag case) to 5.931MB for 2536932-byte allocation
D/dalvikvm( 2986): GC_FOR_ALLOC freed <1K, 6% free 5919K/6260K, paused 3ms, total 3ms
D/dalvikvm( 2986): GC_CONCURRENT freed 0K, 6% free 5919K/6260K, paused 1ms+1ms, total 3ms
D/dalvikvm( 2986): GC_FOR_ALLOC freed 2K, 6% free 6087K/6420K, paused 3ms, total 3ms
I/dalvikvm-heap( 2986): Grow heap (frag case) to 7.287MB for 1249292-byte allocation
D/dalvikvm( 2986): GC_CONCURRENT freed 1K, 5% free 7306K/7644K, paused 2ms+1ms, total 5ms
W/ContextImpl( 2986): Implicit intents with startService are not safe: Intent { act=com.android.vending.billing.InAppBillingService.BIND } android.content.ContextWrapper.bindService:517 com.a.a.a.d.<init>:-1 br.com.magic.boletos.BoletosActivity.onResume:-1
W/ContextImpl( 2986): Implicit intents with startService are not safe: Intent { act=com.android.vending.billing.InAppBillingService.BIND } android.content.ContextWrapper.bindService:517 br.com.magic.boletos.b.a.d.a:-1 com.a.a.a.d.<init>:-1
D/ ( 2986): HostConnection::get() New Host Connection established 0xb84724c0, tid 2986
I/GAV2 ( 2986): Thread[GAThread,5,main]: connecting to Analytics service
W/ContextImpl( 2986): Implicit intents with startService are not safe: Intent { act=com.google.android.gms.analytics.service.START (has extras) } android.content.ContextWrapper.bindService:517 com.google.analytics.tracking.android.AnalyticsGmsCoreClient.b:-1 com.google.analytics.tracking.android.GAServiceProxy.j:-1
I/GAV2 ( 2986): Thread[GAThread,5,main]: connect: bindService returned true for Intent { act=com.google.android.gms.analytics.service.START (has extras) }
I/GAV2 ( 2986): Thread[GAThread,5,main]: No campaign data found.
D/GAV2 ( 2986): Thread[main,5,main]: service connected, binder: [email protected]
D/GAV2 ( 2986): Thread[main,5,main]: bound to service
I/GAV2 ( 2986): Thread[main,5,main]: Connected to service
I/GAV2 ( 2986): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 2986): Thread[GAThread,5,main]: Sending hit to service
I/GAV2 ( 2986): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 2986): Thread[GAThread,5,main]: Sending hit to service
I/GAV2 ( 2986): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 2986): Thread[GAThread,5,main]: Sending hit to service
I/GAV2 ( 2986): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 2986): Thread[GAThread,5,main]: Sending hit to service
I/GAV2 ( 2986): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 2986): Thread[GAThread,5,main]: Sending hit to service
[B][COLOR="red"]Log messages will follow once session has started... [U](ANDROID 9.0)[/U][/COLOR][/B]
W/m.magic.boleto( 5064): Unexpected CPU variant for X86 using defaults: x86
I/m.magic.boleto( 5064): The ClassLoaderContext is a special shared library.
W/m.magic.boleto( 5064): Suspending all threads took: 15.752ms
W/GAV2 ( 5064): Thread[main,5,main]: Need to call initialize() and be in fallback mode to start dispatch.
E/SQLiteLog( 5064): (1) no such table: MOEDA
E/SQLiteLog( 5064): (1) no such table: boletos
E/SQLiteLog( 5064): (1) no such table: MOEDA
W/ContextImpl( 5064): Implicit intents with startService are not safe: Intent { act=com.android.vending.billing.InAppBillingService.BIND } android.content.ContextWrapper.bindService:698 com.a.a.a.d.<init>:30 br.com.magic.boletos.BoletosActivity.onResume:5
W/ContextImpl( 5064): Implicit intents with startService are not safe: Intent { act=com.android.vending.billing.InAppBillingService.BIND } android.content.ContextWrapper.bindService:698 br.com.magic.boletos.b.a.d.a:31 com.a.a.a.d.<init>:55
E/SQLiteLog( 5064): (1) no such table: FAVORECIDO
E/SQLiteLog( 5064): (1) no such table: BOLETO
D/AndroidRuntime( 5064): Shutting down VM
E/AndroidRuntime( 5064): FATAL EXCEPTION: main
E/AndroidRuntime( 5064): Process: br.com.magic.boletos, PID: 5064
E/AndroidRuntime( 5064): java.lang.RuntimeException: Unable to resume activity {br.com.magic.boletos/br.com.magic.boletos.BoletosActivity}: android.database.sqlite.SQLiteException: no such table: BOLETO (code 1 SQLITE_ERROR): , while compiling: SELECT _id , vencimento FROM BOLETO GROUP BY vencimento ORDER BY vencimento ASC
E/AndroidRuntime( 5064): at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3784)
E/AndroidRuntime( 5064): at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3816)
E/AndroidRuntime( 5064): at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:51)
E/AndroidRuntime( 5064): at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:145)
E/AndroidRuntime( 5064): at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:70)
E/AndroidRuntime( 5064): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1808)
E/AndroidRuntime( 5064): at android.os.Handler.dispatchMessage(Handler.java:106)
E/AndroidRuntime( 5064): at android.os.Looper.loop(Looper.java:193)
E/AndroidRuntime( 5064): at android.app.ActivityThread.main(ActivityThread.java:6669)
E/AndroidRuntime( 5064): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 5064): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
E/AndroidRuntime( 5064): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
E/AndroidRuntime( 5064): Caused by: android.database.sqlite.SQLiteException: no such table: BOLETO (code 1 SQLITE_ERROR): , while compiling: SELECT _id , vencimento FROM BOLETO GROUP BY vencimento ORDER BY vencimento ASC
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteConnection.nativePrepareStatement(Native Method)
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteConnection.acquirePreparedStatement(SQLiteConnection.java:903)
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteConnection.prepare(SQLiteConnection.java:514)
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteSession.prepare(SQLiteSession.java:588)
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteProgram.<init>(SQLiteProgram.java:58)
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteQuery.<init>(SQLiteQuery.java:37)
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:46)
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1408)
E/AndroidRuntime( 5064): at android.database.sqlite.SQLiteDatabase.rawQuery(SQLiteDatabase.java:1347)
E/AndroidRuntime( 5064): at br.com.magic.boletos.d.f.a(Unknown Source:83)
E/AndroidRuntime( 5064): at br.com.magic.boletos.d.f.a(Unknown Source:136)
E/AndroidRuntime( 5064): at br.com.magic.boletos.BoletosActivity.b(Unknown Source:156)
E/AndroidRuntime( 5064): at br.com.magic.boletos.BoletosActivity.onResume(Unknown Source:10)
E/AndroidRuntime( 5064): at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1412)
E/AndroidRuntime( 5064): at android.app.Activity.performResume(Activity.java:7292)
E/AndroidRuntime( 5064): at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3776)
E/AndroidRuntime( 5064): ... 11 more
I/Process ( 5064): Sending signal. PID: 5064 SIG: 9
[COLOR="red"][B]Log messages will follow once session has started... [U](ANDROID 10)[/U][/B][/COLOR]
W/m.magic.boleto( 6832): Unexpected CPU variant for X86 using defaults: x86
I/m.magic.boleto( 6832): The ClassLoaderContext is a special shared library.
W/GAV2 ( 6832): Thread[main,5,main]: Need to call initialize() and be in fallback mode to start dispatch.
W/main ( 6832): type=1400 audit(0.0:73): avc: granted { read } for name="u:object_r:net_dns_prop:s0" dev="tmpfs" ino=6662 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:net_dns_prop:s0 tclass=file app=com.ustwo.lwp
E/SQLiteLog( 6832): (1) no such table: MOEDA
E/SQLiteLog( 6832): (1) no such table: boletos
W/ContextImpl( 6832): Implicit intents with startService are not safe: Intent { act=com.android.vending.billing.InAppBillingService.BIND } android.content.ContextWrapper.bindService:705 com.a.a.a.d.<init>:30 br.com.magic.boletos.BoletosActivity.onResume:5
W/ContextImpl( 6832): Implicit intents with startService are not safe: Intent { act=com.android.vending.billing.InAppBillingService.BIND } android.content.ContextWrapper.bindService:705 br.com.magic.boletos.b.a.d.a:31 com.a.a.a.d.<init>:55
W/Gralloc3( 6832): mapper 3.x is not supported
D/HostConnection( 6832): createUnique: call
D/HostConnection( 6832): HostConnection::get() New Host Connection established 0xd47f4380, tid 6832
D/HostConnection( 6832): HostComposition ext ANDROID_EMU_CHECKSUM_HELPER_v1 ANDROID_EMU_dma_v1 ANDROID_EMU_direct_mem ANDROID_EMU_host_composition_v1 ANDROID_EMU_host_composition_v2 ANDROID_EMU_YUV420_888_to_NV21 ANDROID_EMU_YUV_Cache ANDROID_EMU_async_unmap_buffer GL_OES_vertex_array_object GL_KHR_texture_compression_astc_ldr ANDROID_EMU_gles_max_version_2
D/eglCodecCommon( 6832): allocate: Ask for block of size 0x1000
D/eglCodecCommon( 6832): allocate: ioctl allocate returned offset 0x3ffffa000 size 0x2000
D/eglCodecCommon( 6832): allocate: Ask for block of size 0x752000
D/eglCodecCommon( 6832): allocate: ioctl allocate returned offset 0x3ff0b2000 size 0x753000
W/System ( 6832): A resource failed to call close.
W/System ( 6832): A resource failed to call close.
I/GAV2 ( 6832): Thread[GAThread,5,main]: connecting to Analytics service
W/ContextImpl( 6832): Implicit intents with startService are not safe: Intent { act=com.google.android.gms.analytics.service.START (has extras) } android.content.ContextWrapper.bindService:705 com.google.analytics.tracking.android.AnalyticsGmsCoreClient.b:41 com.google.analytics.tracking.android.GAServiceProxy.j:55
D/GAV2 ( 6832): Thread[main,5,main]: service connected, binder: [email protected]
D/GAV2 ( 6832): Thread[main,5,main]: bound to service
I/GAV2 ( 6832): Thread[GAThread,5,main]: connect: bindService returned true for Intent { act=com.google.android.gms.analytics.service.START (has extras) }
I/GAV2 ( 6832): Thread[main,5,main]: Connected to service
I/GAV2 ( 6832): Thread[GAThread,5,main]: No campaign data found.
I/GAV2 ( 6832): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 6832): Thread[GAThread,5,main]: Sending hit to service
I/GAV2 ( 6832): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 6832): Thread[GAThread,5,main]: Sending hit to service
I/GAV2 ( 6832): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 6832): Thread[GAThread,5,main]: Sending hit to service
I/GAV2 ( 6832): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 6832): Thread[GAThread,5,main]: Sending hit to service
I/GAV2 ( 6832): Thread[GAThread,5,main]: putHit called
I/GAV2 ( 6832): Thread[GAThread,5,main]: Sending hit to service
hello, you have source code or just apk? seems it has a bug appears as it's db sql excute on android 9. may be it doesn't adapter android 9.
if you are a developer and you have the source code(only apk can use decompile tool get a project code), you can fix it, but if you are not a developer, may be contact to the owner developer is the only way to help you!
@walker ice
Hi.
Thank you for answer me.
I am not a developer. I am "curiousloper" (curious + developer)... kkkk.
Well... I have only the apk. I spoke with the app developer (company) and they said that this app was abandoned a long time ago.
This app is a barcode reader that I use to pay my bank slips.
The app is installed in mobile and the server program in windows.
When the app read the barcode, it send that to PC where cursor was marked, in this case to my internet bank page.
I tested others apps similar but they read wrong the barcode.
I used the "APK Easy Tool v1.56 Portable" for window to decompile the apk. I changed the SDK to 28 but the issue continues.
I saw in some posts talking about the possible problem with data base bank on android pie and to rename the file adding .db in the end would solve but I did it too and no worked to me.
I searched for a solution but I didn't find.
Can be in my face but like I am not a developer, I cannot see the solution.
I don't need that someone do it for me.
I only need someone that look the apk and tell me what I should to do, what I need to change in apk to do it works on android pie.
I want to learn how to do.
Perhaps the app has two or more android projects.
Would you like to ask the app developer for the source code as the company has abandoned this app?
If you have the source code, you can check and modify it with ease in Android Studio by yourself.
Sorry. Duplication of post.
robrazil said:
@walker ice
Hi.
Thank you for answer me.
I am not a developer. I am "curiousloper" (curious + developer)... kkkk.
Well... I have only the apk. I spoke with the app developer (company) and they said that this app was abandoned a long time ago.
This app is a barcode reader that I use to pay my bank slips.
The app is installed in mobile and the server program in windows.
When the app read the barcode, it send that to PC where cursor was marked, in this case to my internet bank page.
I tested others apps similar but they read wrong the barcode.
I used the "APK Easy Tool v1.56 Portable" for window to decompile the apk. I changed the SDK to 28 but the issue continues.
I saw in some posts talking about the possible problem with data base bank on android pie and to rename the file adding .db in the end would solve but I did it too and no worked to me.
I searched for a solution but I didn't find.
Can be in my face but like I am not a developer, I cannot see the solution.
I don't need that someone do it for me.
I only need someone that look the apk and tell me what I should to do, what I need to change in apk to do it works on android pie.
I want to learn how to do.
Click to expand...
Click to collapse
can you provider me an apk download url? I will have a try and tell you whether there a way to make it work in android pie if possible
walker ice said:
can you provider me an apk download url? I will have a try and tell you whether there a way to make it work in android pie if possible
Click to expand...
Click to collapse
Of course yes.
Only to have an idea, I had to access the webcache (https://archive.org/) of the developer page of 2011 to download the apk file and the server program for windows. So, I upload the zip file to gdrive:
https://drive.google.com/open?id=0B_3XOrUkmIBMQlZhZExRTGZYVDQ
Thank you so much.
robrazil said:
Of course yes.
Only to have an idea, I had to access the webcache (https://archive.org/) of the developer page of 2011 to download the apk file and the server program for windows. So, I upload the zip file to gdrive:
https://drive.google.com/open?id=0B_3XOrUkmIBMQlZhZExRTGZYVDQ
Thank you so much.
Click to expand...
Click to collapse
hello robrazil, after I have a try, event decompile, it still have many crash for the project is too old(like some library of it, as zxing...) and the owner's progurad do well, so may be only the owner can help you but if they abandon it will be very hard to make it work in android pie. Sorry for not being able to help you
walker ice said:
hello robrazil, after I have a try, event decompile, it still have many crash for the project is too old(like some library of it, as zxing...) and the owner's progurad do well, so may be only the owner can help you but if they abandon it will be very hard to make it work in android pie. Sorry for not being able to help you
Click to expand...
Click to collapse
I appreciated your help.
What I don't understand is how is that works on Android 5, 6, 7, 8.1 and 10, but only 9 not ?
I used the virtual android on website https://appetize.io/ to test the installation and to open the app in each android version, and only in the PIE version it not opened.
What the PIE version has so different of others versions, including the 10 ?
Because the app open on the version 10 too.
For now, I am using the app in my old smartphone with Lollipop android.
robrazil said:
I appreciated your help.
What I don't understand is how is that works on Android 5, 6, 7, 8.1 and 10, but only 9 not ?
I used the virtual android on website https://appetize.io/ to test the installation and to open the app in each android version, and only in the PIE version it not opened.
What the PIE version has so different of others versions, including the 10 ?
Because the app open on the version 10 too.
For now, I am using the app in my old smartphone with Lollipop android.
Click to expand...
Click to collapse
Gotta be something to do with API or sdk/kernel version.
Sent from my SM-S767VL using Tapatalk
robrazil said:
I appreciated your help.
What I don't understand is how is that works on Android 5, 6, 7, 8.1 and 10, but only 9 not ?
I used the virtual android on website https://appetize.io/ to test the installation and to open the app in each android version, and only in the PIE version it not opened.
What the PIE version has so different of others versions, including the 10 ?
Because the app open on the version 10 too.
For now, I am using the app in my old smartphone with Lollipop android.
Click to expand...
Click to collapse
android pie add some "Non-SDK interface restrictions" may effect the there part method, and it's update in android 10 as google introduct below:
"To help ensure app stability and compatibility, the platform started restricting which non-SDK interfaces your app can use in Android 9 (API level 28). Android 10 includes updated lists of restricted non-SDK interfaces based on collaboration with Android developers and the latest internal testing. Our goal is to make sure that public alternatives are available before we restrict non-SDK interfaces."
so may be android the app not work in android pie, it cause by the Non-SDK interface restrictions.
About API or SDK/kernel or "Non-SDK interface restrictions", it has nothing to do with the old lines below, of apktool.yml file that I changed to
PHP:
sdkInfo:
minSdkVersion: '26'
targetSdkVersion: '28'
Has it ?
robrazil said:
About API or SDK/kernel or "Non-SDK interface restrictions", it has nothing to do with the old lines below, of apktool.yml file that I changed to
PHP:
sdkInfo: minSdkVersion: '26' targetSdkVersion: '28'
Has it ?
Click to expand...
Click to collapse
I'm not sure that editing the apk to change those lines isn't quite enough. I would say that you'd have to recompile the apk using the needed SDK version so that the apk itself is compiled correctly for that SDK version.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
I'm not sure that editing the apk to change those lines isn't quite enough. I would say that you'd have to recompile the apk using the needed SDK version so that the apk itself is compiled correctly for that SDK version.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thank you for answer me.
Well... if decompile the apk, to change the "minSdkVersion" and the "targetSdkVersion" informations to 26 and 28 respectively and recompile the apk again is not "recompile the apk using the needed SDK version", so, what means exactly "recompile the apk using the needed SDK version" and how can I do that ?
Where can I find something about "recompile the apk using the needed SDK version" to do that ?

Categories

Resources