[Q] Official Froyo Camera on 720p forced close issues - Streak 5 Android Development

Hi everyone,
I am new here on the forum, and the Streak is my very first Android phone. Just wanted to quickly say I really enjoy the community here and I like how everyone tries to help each other.
I noticed that a lot of people have been having problems with Camera forced close issues, which is what I've been experiencing as well. Please mind that this is my first Android phone, and my understanding of Linux is very limited.
I thought I'd post my findings so far in the forced close issues I've been experiencing. Here are some of what I think are the culprits behind the forced close:
Main Log:
1. First it tries to set unsupported parameters for the audio input, followed by more failed attempts to set other parameters
Code:
11-21 02:00:11.475 E/audio_input( 91): unsupported parameter:
x-pvmf/media-input-node/cap-config-interface;valtype=key_specific_value
11-21 02:00:11.475 E/audio_input( 91): VerifyAndSetParameter failed
2. Big Fail! It tries to load what looks to be a video encoder, and can't find it:
Code:
11-21 02:00:11.525 E/PVOMXEncNode( 91): PVMFOMXEncNode-Video_M4V::DoPrepare(): Cannot get component OMX.qcom.video.encoder.mpeg4 handle, try another component if available
11-21 02:00:11.525 E/PVOMXEncNode( 91): PVMFOMXEncNode-Video_M4V::DoPrepare(): Cannot get component OMX.PV.mpeg4enc handle, try another component if available
11-21 02:00:11.525 E/AuthorDriver( 91): Command 13 completed with error -17
11-21 02:00:11.535 E/MediaRecorder( 754): prepare failed: -17
11-21 02:00:11.535 E/videocamera( 754): prepare failed for /mnt/sdcard/DCIM/Camera/VID_20101121_020011.3gp
3. Dalvik Virtual Machine pops up an error, and throws it at Android for error handling:
Code:
11-21 02:00:11.545 F/dalvikvm( 754): Exception!!! threadid=1: thread exiting with uncaught exception (group=0x4001d7d8)
11-21 02:00:11.565 E/AndroidRuntime( 754): FATAL EXCEPTION: main
11-21 02:00:11.565 E/AndroidRuntime( 754): java.lang.RuntimeException: java.io.IOException: prepare failed.
11-21 02:00:11.565 E/AndroidRuntime( 754): at com.android.camera.VideoCamera.initializeRecorder(VideoCamera.java:1297)
11-21 02:00:11.565 E/AndroidRuntime( 754): at com.android.camera.VideoCamera.access$300(VideoCamera.java:99)
11-21 02:00:11.565 E/AndroidRuntime( 754): at com.android.camera.VideoCamera$MainHandler.handleMessage(VideoCamera.java:300)
Events Log:
1. Pretty straightforward -- video camera -- problem returns to android for handling during use of Media Recorder?
Code:
11-21 02:00:11.575 I/am_crash( 148): [754,com.android.camera,48709,java.io.IOException,prepare failed.,MediaRecorder.java,-2]
11-21 02:00:11.585 I/am_finish_activity( 148): [1193151496,8,com.android.camera/.VideoCamera,crashed]
11-21 02:00:11.585 I/am_pause_activity( 148): [1193151496,com.android.camera/.VideoCamera]
11-21 02:00:12.095 I/am_resume_activity( 148): [1190436808,2,com.dell.launcher/.Launcher]
System Log:
1. Same below -- start video camera, crash, Android handles the "oh no"s...
Code:
cat=[android.intent.category.LAUNCHER] flg=0x14000000 cmp=com.android.camera/.Camera }
11-21 02:00:10.445 I/ActivityManager( 148): Starting activity: Intent { flg=0x4000000 cmp=com.android.camera/.VideoCamera (has extras) }
11-21 02:00:11.565 E/AndroidRuntime( 754): FATAL EXCEPTION: main
11-21 02:00:11.565 E/AndroidRuntime( 754): java.lang.RuntimeException: java.io.IOException: prepare failed.
I've also attached the processes log, processesthread log, and system.prop files for reference (I removed all wifi and carrier information at the bottom of the system.prop, but I don't think it's relevant)
I think the main cause of the crash is the media recorder trying to set unsupported parameters and missing video encoder. Not sure though. Any assistance would be greatly appreciated -- I am still looking into the problems, and will get back to everyone on my findings.

Good job...Guess the codec might also be dealing with audio and the bad parm is caused by the unregistered/missing codec? [noob]

Yes - I think definitely there were some serious problems with updating it from a non-00 baseband version.
I think dependencies are missing/broken from either updating from a non 00 baseband version or the flashboot method itself. Those with 00 baseband have it easier, as they already have all the dependencies and can upgrade using the
"copy package to /sdcard/update.pkg" method.
I gave up trying to find the dependencies that were broken, instead went the "downgrading, converting to baseband 00 version and upgrading back to Froyo" method.
I've finally got everything working (including 720p recording) with a combination of Homeiss' "How To Install Official Dell 2.2 Upgrade.pkg" and Geek78's "How to go back from 21 to 00 builds" guide with a little alteration suggested by llecaroz (from modaco forum).
I think this downgrade first to Baseband 00 first than upgrade should fix all problems. The trick is to downgrade to downgrade to 1.6 that matches your baseband (21,31) first! In my case, I had a baseband 21 version.
Suggestions:
- I suggest to downgrade using Geek78's guide first (because, based on my experience, downgrading from 21 2.1 -> 00 1.6 ends up with DELL forever logo).
- If you end up with a "FOTA version error" thingy, you need to flash with a different recovery file (it changes the recovery version from 21 to 00)
- If getting "flash_image: not found" error, it means you are missing the binary. Get it from cyanogen.
Good luck with Homeiss' and Geek78's guide.
I can re-compile a more comprehensive guide, but I think I am unable to place links in here.

If you have upgraded the fastboot way (with the 3 files Stephen provided) You will have FCs on 720p recording! I have downgraded mine to 6267 and then upgraded with the pkg file! Now 720p works perfect!

Related

[Solved] Compiling Apps Problem

I've been trying to compile AOSP apps individually and that doesn't seem to work. These are the steps I took:
1. Install GCC and Java
2. The repo commands (sync from android git etc)
3. make Gallery3D
4. push Gallery3D.apk /system/app/
So as you can see, compilation went on fine. And pushing to my phone also went fine (CM 5.0.4.1). However, when I try to run Gallery3D, I got FC. Here's my logcat:
I/ActivityManager( 93): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.cooliris.media/.Gallery }
V/RenderScript_jni( 6329): surfaceDestroyed
V/RenderScript( 6329): setSurface 0 0 0x0
D/ViewFlipper( 6329): updateRunning() mVisible=false, mStarted=true, mUserPresent=true, mRunning=false
D/LocationManager( 6198): removeUpdates: listener = [email protected]
D/NetworkLocationProvider( 93): removeListener(): wallpaper
D/NetworkLocationProvider( 93): enableLocationTracking(): false
E/NetworkLocationProvider( 93): releaseCheckLocationLock: wake lock has already been released
D/SensorManager(18699): found sensor: BMA150 3-axis Accelerometer, handle=0
D/SensorManager(18699): found sensor: AK8973 3-axis Magnetic field sensor, handle=1
D/SensorManager(18699): found sensor: AK8973 Orientation sensor, handle=2
D/SensorManager(18699): found sensor: CM3602 Proximity sensor, handle=4
D/SensorManager(18699): found sensor: CM3602 Light sensor, handle=5
W/ResourceType(18699): Failure getting entry for 0x7f02003a (t=1 e=58) in package 0: 0xffffffb5
D/AndroidRuntime(18699): Shutting down VM
W/dalvikvm(18699): threadid=3: thread exiting with uncaught exception (group=0x4001b178)
E/AndroidRuntime(18699): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime(18699): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.cooliris.media/com.cooliris.media.Gallery}: android.content.res.Resources$NotFoundException: Resource ID #0x7f02003a
E/AndroidRuntime(18699): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2496)
E/AndroidRuntime(18699): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2512)
E/AndroidRuntime(18699): at android.app.ActivityThread.access$2200(ActivityThread.java:119)
E/AndroidRuntime(18699): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1863)
E/AndroidRuntime(18699): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(18699): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime(18699): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime(18699): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(18699): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime(18699): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime(18699): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime(18699): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(18699): Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x7f02003a
E/AndroidRuntime(18699): at android.content.res.Resources.getValue(Resources.java:891)
E/AndroidRuntime(18699): at android.content.res.Resources.getDrawable(Resources.java:579)
E/AndroidRuntime(18699): at com.cooliris.media.HudLayer.<init>(HudLayer.java:121)
E/AndroidRuntime(18699): at com.cooliris.media.GridLayer.<init>(GridLayer.java:134)
E/AndroidRuntime(18699): at com.cooliris.media.Gallery.onCreate(Gallery.java:78)
E/AndroidRuntime(18699): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime(18699): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2459)
E/AndroidRuntime(18699): ... 11 more
I/Process ( 93): Sending signal. PID: 18699 SIG: 3
I/dalvikvm(18699): threadid=7: reacting to signal 3
I/dalvikvm(18699): Wrote stack trace to '/data/anr/traces.txt'
I/DumpStateReceiver( 93): Added state dump to 1 crashes
Click to expand...
Click to collapse
Besides this, I noticed that my Gallery3D.apk is smaller size(~500kb) than the one which comes with CM (~700kb).
Any help guys? Been trying to figure this out and googling. What did I miss?
arctu said:
I've been trying to compile AOSP apps individually and that doesn't seem to work. These are the steps I took:
1. Install GCC and Java
2. The repo commands (sync from android git etc)
3. make Gallery3D
4. push Gallery3D.apk /system/app/
So as you can see, compilation went on fine. And pushing to my phone also went fine (CM 5.0.4.1). However, when I try to run Gallery3D, I got FC. Here's my logcat:
Besides this, I noticed that my Gallery3D.apk is smaller size(~500kb) than the one which comes with CM (~700kb).
Any help guys? Been trying to figure this out and googling. What did I miss?
Click to expand...
Click to collapse
Q&A section ma man
I believe this is the right section, it's a question on compiling/development. I believe Gallery3D might be lacking mdpi images, and you're compiling for mdpi devices (may be wrong, not able to check now).
What you can do is to do a search for "PRODUCT_LOCALES", within all your files, I think it's in build.mk or product.mk. You will see that the default is mdpi, follow by <something> (can't remember now) += nodpi. Add a <something> += hdpi after the nodpi line, and compile and push again. I had a similar issue and was able to fix it this way, with advice from cyanogen.
Thanks Wysie. That helps!
To those facing the same problem here are the exact steps I took (using terminal and nano):
1. Open/Edit build/core/product_config.mk:
nano build/core/product_config.mk
Click to expand...
Click to collapse
2. Find:
PRODUCT_LOCALES += nodpi
Click to expand...
Click to collapse
3. Add in after that line:
PRODUCT_LOCALES += hdpi
Click to expand...
Click to collapse
4. Save and Exit: Ctrl+X
5. Run make again:
make Gallery3D
Click to expand...
Click to collapse
If you did everything correctly, and have compiled before, the compiler should write this at the beginning:
*** Build configuration changed: "generic-eng-{mdpi,nodpi}" -> "generic-eng-{mdpi,nodpi,hdpi}"
*** Forcing "make installclean"...
*** Done with the cleaning, now starting the real build.
Click to expand...
Click to collapse
It works now. Hope this helps the others.
arctu said:
Thanks Wysie. That helps!
To those facing the same problem here are the exact steps I took (using terminal and nano):
1. Open/Edit build/core/product_config.mk:
2. Find:
3. Add in after that line:
4. Save and Exit: Ctrl+X
5. Run make again:
If you did everything correctly, and have compiled before, the compiler should write this at the beginning:
It works now. Hope this helps the others.
Click to expand...
Click to collapse
cheers, helped me out
after quick grep to confirm I used sed
Code:
sed s/PRODUCT_LOCALES\ \+\=\ nodpi/PRODUCT_LOCALES\ \+\=\ hdpi/ build/core/product_config.mk -i

[Q] Connectivity Services exception causes boot loop

Hi.
Summary: the AndroidRuntime process fails when starting the Connectivity Service, causing my phone into a boot loop.
Sorry for the very verbose post.
Background: I've spent quite a bit of time trying to resolve a problem that causes my Sony Ericsson Xperia X10 Mini (from O2) to go into a boot loop. I've rooted the phone some time ago using this process: (sorry the forum prevents me from posting link, please copy and paste this: android.doshaska.net/x10miniroot).
I then proceeded to remove some of the redundant programs from /system/app.
Everything worked fine for several weeks until the phone started complaining about the storage being filled up. I could see that /data was getting full and I suspected that the K9 email client I had installed was using lots f space to keep the IMAP folders synced.
I can't remember if the phone rebooted itself or if I did it manually, but it never managed to boot up again, and is ever since stuck at the Sony Ericsson logo.
adb logcat tells me that the AndroidRuntime process fails when starting the Connectivity Service. It's stuck in this loop, but I've isolated one single loop in the attachment logcat.txt. The crash file references has been attached as 1279210811.txt.
The final fatal crash is:
I/SystemServer( 1297): Starting Connectivity Service.
W/dalvikvm( 1297): threadid=51: thread exiting with uncaught exception (group=0x2aac9a28)
E/AndroidRuntime( 1297): Uncaught handler: thread ConnectivityThread exiting due to uncaught exception
E/AndroidRuntime( 1297): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 1297): java.lang.NullPointerException
E/AndroidRuntime( 1297): at android.app.ActivityThread.getProvider(ActivityThread.java:3938)
E/AndroidRuntime( 1297): at android.app.ActivityThread.acquireProvider(ActivityThread.java:3967)
E/AndroidRuntime( 1297): at android.app.ApplicationContext$ApplicationContentResolver.acquireProvider(ApplicationContext.java:1527)
E/AndroidRuntime( 1297): at android.content.ContentResolver.acquireProvider(ContentResolver.java:579)
E/AndroidRuntime( 1297): at android.content.ContentResolver.query(ContentResolver.java:147)
E/AndroidRuntime( 1297): at android.provider.Settings$NameValueCache.getString(Settings.java:476)
E/AndroidRuntime( 1297): at android.provider.Settings$Secure.getString(Settings.java:1701)
E/AndroidRuntime( 1297): at android.provider.Settings$Secure.getInt(Settings.java:1741)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.getPersistedNetworkPreference(ConnectivityService.java:182)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:123)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:47)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService$ConnectivityThread.run(ConnectivityService.java:87)
I've had a look at the JavDoc for android.app.ActivityThread.getProvider, but I've not been able to find any useful information. I have to guess that the start-up process fails to read the provider (network) specific settings for some reason. I don't have a clue whether the source is a file, database or something else.
A wild guess is that something got corrupted when the data partition filled up. There are some upset earlier in the log (line 180) when the PackageManager is reading an XML file that relates to the PackageManager settings that seems to have been corrupted:
E/PackageManager( 1297): Error reading package manager settings E/PackageManager( 1297): org.xmlpull.v1.XmlPullParserException:
Premature end of document. (position:line -1, column -1) caused by:
org.apache.harmony.xml.ExpatParser$ParseException: At line 1, column 0: no element found
I've seen a few similar posts, but nothing exactly like this nor anything that I could use to resolve it.
Stupid section
I've got myself into this through a combination of stupidity and bad luck. I've backed up all .APK that I've removed and created a log of what I removed (that I'm still looking for). I thought this was all that I needed and I don't have a full backup.
Unfortunately, the root access now gives me a segmentation fault and the root process requires the GUI to work, so I can't repeat the process. I don't want to try another root process before I've tried what I can to get the phone back in a reasonable state.
Fortunately, I still have full adb access, so I have visibility and some control over the phone.
Any help on this would be much appreciated. At least I've saved you the time pointing out that I'm an idiot not doing a full backup
Regards,
Dan

[Request] LG Optimus One - Orange UK Original ROM

Request is in the title - the LG Optimus One from Orange UK contains the Orange Signal Boost (UMA) software that would be useful to get working on other android phones with networks which support UMA. The topic is here but I've cross-posted here in case the topic gets lost in the general forum.
Here you go, This should be the original Orange V10C_00 firmware for your phone:
Code:
csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/AORUBK/V10c_00/V10C_00.kdz
I was thinking maybe someone with the Optimus One could just backup the apk for Orange Signal Boost and post that. I have tried expanding the rom posted in the link and have got as far as the mbn files and boot.img etc but I don't know how to get at the apk's...
Bump
Could any owner of optimus one share that app with us ?
please
Again, please anyone! We just need a backup of the apk to get started!
Sent from my HTC Desire using XDA App
Ok, I managed to unpack the KDZ file but still couldn't find a way extract the Orange Signal Booster apk from boot.img file; so if anyone has backup of the apk it would be greatly appreciated.
I tried the same thing but had no luck. If you had the handset you could use a number of different apps (astro, titanium backup) to make a backup of the .apk file with very little technical knowledge.
It would be god send if we could get this app running on other handsets...
Here is the APK!
OK here is the APK which I have extracted from the ROM image. I tried installing it on my desire and it FCs as soon as I attempt to run it. If anyone else wants to get onboard with this please do!
Hi ballandbiscuit, many thanks for the APK. Tried it on my HTC DHD and had the same FC result as you. As far as I can tell, this is not a hardware restriction but possibly the result of other system services required by the app not installed on the handset.
I really wish someone from Orange with a bit of technical knowhow would get involved and assist us with this much needed feature.
what about some kind of logging? maybe it say something...
Sent from my LG-P500 using XDA App
Here is some data from logcat
Code:
I/ActivityManager( 167): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.kineto/.kineto }
I/ActivityManager( 167): Start proc com.android.kineto for activity com.android.kineto/.kineto: pid=1695 uid=10103 gids={3003, 3002, 3001, 1015}
W/dalvikvm( 1695): Exception Ljava/lang/UnsatisfiedLinkError; thrown during Lcom/android/kineto/kineto;.<clinit>
W/dalvikvm( 1695): Class init failed in newInstance call (Lcom/android/kineto/kineto;)
D/AndroidRuntime( 1695): Shutting down VM
W/dalvikvm( 1695): threadid=1: thread exiting with uncaught exception (group=0x4001d7e8)
E/AndroidRuntime( 1695): FATAL EXCEPTION: main
E/AndroidRuntime( 1695): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 1695): at java.lang.Class.newInstanceImpl(Native Method)
E/AndroidRuntime( 1695): at java.lang.Class.newInstance(Class.java:1429)
E/AndroidRuntime( 1695): at android.app.Instrumentation.newActivity(Instrumentation.java:1021)
E/AndroidRuntime( 1695): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2577)
E/AndroidRuntime( 1695): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2679)
E/AndroidRuntime( 1695): at android.app.ActivityThread.access$2300(ActivityThread.java:125)
E/AndroidRuntime( 1695): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2033)
E/AndroidRuntime( 1695): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1695): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 1695): at android.app.ActivityThread.main(ActivityThread.java:4627)
E/AndroidRuntime( 1695): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1695): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 1695): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
E/AndroidRuntime( 1695): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
E/AndroidRuntime( 1695): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 1695): Caused by: java.lang.UnsatisfiedLinkError: Library kineto not found
E/AndroidRuntime( 1695): at java.lang.Runtime.loadLibrary(Runtime.java:461)
E/AndroidRuntime( 1695): at java.lang.System.loadLibrary(System.java:557)
E/AndroidRuntime( 1695): at com.android.kineto.kineto.<clinit>(kineto.java:1552)
E/AndroidRuntime( 1695): ... 15 more
W/ActivityManager( 167): Force finishing activity com.android.kineto/.kineto
W/ActivityManager( 167): Activity pause timeout for HistoryRecord{46506b50 com.android.kineto/.kineto}
I/ActivityManager( 167): No longer want com.google.android.apps.uploader (pid 653): hidden #16
I/Process ( 1695): Sending signal. PID: 1695 SIG: 9
W/InputManagerService( 167): Window already focused, ignoring focus gain of: [email protected]
I/ActivityManager( 167): Process com.android.kineto (pid 1695) has died.
Not sure if this is relevant but earlier in the logcat...
Code:
W/PackageManager( 167): Not granting permission android.permission.DEVICE_POWER to package com.android.kineto (protectionLevel=2 flags=0x48444)
W/PackageManager( 167): Not granting permission android.permission.UPDATE_DEVICE_STATS to package com.android.kineto (protectionLevel=2 flags=0x48444)
W/PackageManager( 167): Unknown permission android.permission.INJECT_EVENT in package com.android.kineto
Having looked at some other posts regarding the T-Mobile US UMA app, which is also Kineto based I think it will take a lot of work to get this functioning. It appears to need some libraries such as...
libkento
linganril
librilswitch
and also some changes to the kernel as per this thread
http://forum.xda-developers.com/showthread.php?t=807116
I don't know if this was ever ported to devices other than the N1. It is shame that it requires more than just an app. Orange should be pushing this to all Android handsets. I don't use my phone at home for calls or texts because the signal is too weak, this is a loss for both myself and Orange because they don't get to charge me for calls I don't make. My wife has a Vodafone Sure Signal box which is brilliant but Orange don't offer such a device...
Okay, I just had a little luck with the UMA application.
Not quite there yet though.
BASICALLY, I have come to understand that the application extracted from various Roms FC cuz they are missing other files they depend on from the ROM.
I was using Orange Signal Boost apk from the Orange Desire S rom (am attaching it) on my HTC Legend.
Then I came across stories of someone in US who had extracted an apk from so Tmobile Rom for wifi calling and made it to work on a Nexus 1. I downloaded that files (also attached). This file was a modded version of original apk and had all the dependant files. (and consequently was 3mb vs 600kb of Orange signal boost)
So what I tried was
1. Install tmobile wifi app
2. Install Orange signal boost on TOP of it. It will ask you that this progam will replace another older program on your phone. Clcik okay.
3. What this does is leave old installed files needed from tmobile app and this time LO AND BEHOLD, signal boost app launches without FC
Here comes the problem though, it doesnt work, cuz somewhere hardcoded in the files that the tmobile app installs is the network info and naturally, our sims being orange are recognized as invalid sim.
Me and a LOT of other people would REALLY appreciate it if someone with any knowhow can look at this and figure it out for us

[Q] YP-G1CWY/XAA Mysterious Bootloop

Hello, currently, one of our Galaxy 4.0 Players is stuck in a boot loop. I have been searching this site and a few others for over a month now for solutions and am stumped.
I have tried flashing several different US YP-G1 stock ROMs using both Heimdall and Odin, Terrasilent kernel, Steve's kernel, Icyfusion ROM, factory reset, wiping cache/dalvik.
Over a month ago, the device started randomly rebooting and showing the first time startup screen each time it rebooted like this. When it would have a random reboot however, it would get stuck in a boot loop and have to be restarted by holding the power button or pulling battery. Then after a couple weeks of that, it has since been stuck in a boot loop.
Interesting "dmesg" information that may or may not have anything to do with this are:
7.347889] init: SEC_DEVENC ***[/dev/block/mmcblk0p2][0]
7.352046] init: failed that mount s:'/dev/block/mmcblk0p2', t:'/data', f
7.362574] init: SEC_DEVENC ***[/dev/block/mmcblk0p2][0]
7.368081] init: failed that mount s:'/dev/block/mmcblk0p2', t:'/data', f
8.585066] mmc0: error -110 whilst initialising MMC card
8.655510] mmc1: new high speed SDHC card at address b368
I believe that the internal sdcard has died and have formatted the external one with the vfat and rfs partitions to act as the internal sdcard. But according to dmesg, it appears that perhaps mmcblk0p2 is trying to be mounted in the boot procedure before MMC1 is detected?
Any help is greatly appreciated and I will provide any more information as needed.
-Tony
"FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityThread"
update
Between flashing the international verions's bootloader, reflashing recovery rom, Terrasilent kernel and restoring a Nandroid backup from our other YP-G1, the mounting problems seem to be gone now.
However, there is still a bootloop problem which I believe has something to do with these logcat entries:
D/NativeDaemonConnector( 246): NativeDaemonConnector ::
D/NetdConnector( 246): run ::
D/NetdConnector( 246): listenToSocket ::
I/SystemServer( 246): Connectivity Service
W/dalvikvm( 246): threadid=17: thread exiting with uncaught exception (group=0x
40015578)
E/ ( 246): Dumpstate > /data/log/dumpstate_sys_error
V/ConnectivityService( 246): ConnectivityService starting up
E/ActivityThread( 246): Failed to find provider info for settings
E/AndroidRuntime( 246): *** FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityThre
ad
E/AndroidRuntime( 246): java.lang.NullPointerException
E/AndroidRuntime( 246): at android.provider.Settings$NameValueCache.getS
tring(Settings.java:664)
E/AndroidRuntime( 246): at android.provider.Settings$Secure.getString(Se
ttings.java:2209)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:264)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:61)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService$Connec
tivityThread.run(ConnectivityService.java:229)
I/dumpstate( 277): begin
E/dumpstate( 277): Cannot get free space size. So, skip dumpstate.
When the problems first started before all the flashing, logcat also showed this fatal exception in ConnectivityThread

Leagoo z5, mt6735, o mt6737?

If you ask me what I am saying, well I do not know, the matter is that this smartphone, Chinese, of medium to low quality and economic is known as LEAGOO Z5 LTE 37m, but here comes the strange issue, it is its processor , that on the internet, it is like mt6735, but the same device seen in flashtool is mt6737, and here the confusion begins, which is why not, for such echo with so many doubts take out the status of the aforementioned device in the context of recovery, and this is what I get,
petName=Z5
Lte
versionName=6.0-1488765164
resolution=854 * 480
versionCode=23
SDK_VERSION=23
RELEASE=6.0
Globe.REQUEST_HEADER_IMSI=748070103222388
Globe.REQUEST_HEADER_IMEI=352478081946651
BOARD=Android
BOOTLOADER=unknown
BRAND=LEAGOO
CPU_ABI=armeabi-v7a
CPU_ABI2=armeabi
DEVICE=Z5
DISPLAY=LEAGOO Z5 Lte(37m)_OS2.0_A_20170306
FINGERPRINT=alps/full_bd6737m_35g_a_m0/bd6737m_35g_a_m0:6.0/MRA58K/1488765164:user/dev-keys
HARDWARE=mt6735
HOST=jyunspl2-PowerEdge-R720
ID=MRA58
K
IS_DEBUGGABLE=false
MANUFACTURER=LEAGOO
MODEL=Z5 Lte
PRODUCT=Z5
RADIO=unknown
SERIAL=0123456789
ABCDEF
SUPPORTED_32_BIT_ABIS=[Ljava.lang.String;@758aea8
SUPPORTED_64_BIT_ABIS=[Ljava.lang.String;@3e9bdc
1
SUPPORTED_ABIS=[Ljava.lang.String;@69cc966
TAG=Build
TAGS=dev-keys
TIME=1488765741000
TYPE=user
UNKNOWN=unknown
USER=huchao
crashTime=2018-02-07_14-33-44
STACK_TRACE=java.lang.RuntimeException:
Unable to start activity ComponentInfo{com.android.settings/com.android.settings.Settings$NotificationAccessSettingsActivity}: android.app.Fragment$Instantiation
Exception: Unable to instantiate fragment com.android.settings.notification.ManagedServiceSettings$ScaryWarning
DialogFragment: make sure class name exists, is public, and has an empty constructor that is public
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2576)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2658)
at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:4321)
at android.app.ActivityThread.-wrap15(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1498)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:207)
at android.app.ActivityThread.main(ActivityThread.java:5737)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)
Caused by: android.app.Fragment$Instantiation
Exception: Unable to instantiate fragment com.android.settings.notification.ManagedServiceSettings$ScaryWarning
DialogFragment: make sure class name exists, is public, and has an empty constructor that is public
at android.app.Fragment.instantiate(Fragment.java:635)
at android.app.FragmentState.instantiate(Fragment.java:111)
at android.app.FragmentManagerImpl.restoreAllState(FragmentManager.java:1885)
at android.app.FragmentController.restoreAllState(FragmentController.java:122)
at android.app.Activity.onCreate(Activity.java:927)
at com.android.settings.SettingsActivity.onCreate(SettingsActivity.java:648)
at android.app.Activity.performCreate(Activity.java:6390)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1113)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2523)
... 10 more
Caused by: java.lang.Instantiation
Exception: java.lang.Class<com.android.settings.notification.ManagedServiceSettings$ScaryWarningDialogFragment>
has no zero argument constructor
at java.lang.Class.newInstance(Native Method)
at android.app.Fragment.instantiate(Fragment.java:624)
... 18 more
android.app.Fragment$Instantiation
Exception: Unable to instantiate fragment com.android.settings.notification.ManagedServiceSettings$ScaryWarning
DialogFragment: make sure class name exists, is public, and has an empty constructor that is public
at android.app.Fragment.instantiate(Fragment.java:635)
at android.app.FragmentState.instantiate(Fragment.java:111)
at android.app.FragmentManagerImpl.restoreAllState(FragmentManager.java:1885)
at android.app.FragmentController.restoreAllState(FragmentController.java:122)
at android.app.Activity.onCreate(Activity.java:927)
at com.android.settings.SettingsActivity.onCreate(SettingsActivity.java:648)
at android.app.Activity.performCreate(Activity.java:6390)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1113)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2523)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2658)
at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:4321)
at android.app.ActivityThread.-wrap15(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1498)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:207)
at android.app.ActivityThread.main(ActivityThread.java:5737)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)
Caused by: java.lang.
InstantiationException: java.lang.Class<com.android.settings.notification.ManagedServiceSettings$ScaryWarningDialogFragment>
has no zero argument constructor
at java.lang.Class.newInstance(Native Method)
at android.app.Fragment.instantiate(Fragment.java:624)
... 18 more
java.lang.Instantiation
Exception: java.lang.Class<com.android.settings.notification.ManagedServiceSettings$ScaryWarningDialogFragment>
has no zero argument constructor
at java.lang.Class.newInstance(Native Method)
at android.app.Fragment.instantiate(Fragment.java:624)
at android.app.FragmentState.instantiate(Fragment.java:111)
at android.app.FragmentManagerImpl.restoreAllState(FragmentManager.java:1885)
at android.app.FragmentController.restoreAllState(FragmentController.java:122)
at android.app.Activity.onCreate(Activity.java:927)
at com.android.settings.SettingsActivity.onCreate(SettingsActivity.java:648)
at android.app.Activity.performCreate(Activity.java:6390)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1113)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2523)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2658)
at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:4321)
at android.app.ActivityThread.-wrap15(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1498)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:207)
at android.app.ActivityThread.main(ActivityThread.java:5737)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)
the issue is, according to this info, if we go to the information collected on the internet, there is only one leagoo z5 lte 37, and this is mtk6735, therefore this device in my possession is a clone? or is it original ?, although deadly and even so the PC sometimes detects it, I do not know how to recover it with so many doubts,
with flashtool the skatter is 6737, because the skater of the 6735 gives me incorrect, although I also have an error in the 6737 when I want to flash it,
the mistake is:
ERROR: S-DL-GET-DRAM-SETTING-FAIL (0x13be)
[EMI]: Obtain DRAM Failed!
[HINT]lease check your load matches to your target which is to be downloade
I hope I have been as specific as possible to the respect
good to the geniuses of this forum I appreciate I can advise the respect, to at least recover it and know that diantres is really an abraso to all

Categories

Resources