Hi All,
I have this G850F total stock that randomly freezes and crashes and im at my ends right now (i dont think lollipop would change anything on this matter)
What i have done to exclude/analyze the problem:
Turn off all wireless connections (first one by one)
Turned of NFC
Turned off wireless psm
Boot into safe mode,
Wiped data + dalvik
flashed the following through odin --> G850FXXU2BOA2, G850FXXU2BNK3, G850FXXU2ANI3 + PIT
Custom kernel [r2.2] from bonuzzz (thanks)
TWRP 2.8 recovery with samsung kernel
Problem still persists after each step.
When i log the device trough adb this is the last info i get before the device reboots and i lose connection :
I/ExynosCameraBufferManager( 2340): [CAM_ID(1)][BAYER_BUF]-INFO(dumpBufferInfo[1
151]):[m_buffer[5].fd[0]=48] .addr=0x0 .size=3383360 .position=0 .permission=1]
I/ExynosCameraBufferManager( 2340): [CAM_ID(1)][BAYER_BUF]-INFO(dumpBufferInfo[1
151]):[m_buffer[5].fd[1]=54] .addr=0xaf42e000 .size=32768 .position=0 .permissio
n=1]
D/ExynosCameraBufferManager( 2340): [CAM_ID(1)][BAYER_BUF]-DEBUG(printBufferQSta
te[1112]):bufferIndex=0
D/ExynosCameraBufferManager( 2340): [CAM_ID(1)][BAYER_BUF]-DEBUG(printBufferQSta
te[1112]):bufferIndex=1
D/ExynosCameraBufferManager( 2340): [CAM_ID(1)][BAYER_BUF]-DEBUG(printBufferQSta
te[1112]):bufferIndex=2
D/ExynosCameraBufferManager( 2340): [CAM_ID(1)][BAYER_BUF]-DEBUG(printBufferQSta
te[1112]):bufferIndex=3
D/ExynosCameraBufferManager( 2340): [CAM_ID(1)][BAYER_BUF]-DEBUG(printBufferQSta
te[1112]):bufferIndex=4
D/ExynosCameraBufferManager( 2340): [CAM_ID(1)][BAYER_BUF]-DEBUG(printBufferQSta
te[1112]):bufferIndex=5
D/ExynosCameraBufferManager( 2340): [CAM_ID(1)][BAYER_BUF]-DEBUG(alloc[224]):---
---------------------------------------------------------------
D/ExynosCameraPipeJpeg( 2340): DEBUG:duration time( 2 msec)alloc)
I/ExynosCamera( 2340): [CAM_ID(1)][]-INFO(m_allocBuffers[9393]):setIn
Click to expand...
Click to collapse
2
I/ExynosCameraPipeSCC( 2341): [CAM_ID(1)][PIPE_SCC_FRONT]-INFO(setupPipe[175]):s
etupPipe() is succeed (107) prepare (3)
D/ExynosCameraPipeSCP( 2341): [CAM_ID(1)][PIPE_SCP_FRONT]-DEBUG(setupPipe[132])
D/ExynosCameraNode( 2341): [CAM_ID(1)][SCP]-DEBUG(setSize[299]):w (480) h (270)
I/ExynosCameraPipeSCP( 2341): INFO(setupPipe[178]):setupPipe() is succeed (108)
setupPipe (3)
D/ExynosCameraBufferManager( 2341): [CAM_ID(1)][BAYER_BUF]-DEBUG(resetBuffers[14
4]):IN..
D/ExynosCameraBufferManager( 2341): [CAM_ID(1)][ISP_BUF]-DEBUG(resetBuffers[144]
):IN..
D/ExynosCamera( 2341): [CAM_ID(1)][]-DEBUG(m_searchFrameFromList[8438]):list is
empty
D/ExynosCameraPipe( 2341): [CAM_ID(1)][PIPE_FLITE_FRONT]-DEBUG(prepare[240])
D/ExynosCameraPipe( 2341): [CAM_ID(1)][PIPE_SCP_FRONT]-DEBUG(prepare[240])
D/ExynosCameraPipe( 2341): [CAM_ID(1)][PIPE_FLITE_FRONT]-DEBUG(start[256])
I/ExynosCameraPipe3AA( 2341): INFO(start[245])
D/ExynosCameraPipe( 2341): [CAM_ID(1)][PIPE_SCC_FRONT]-DEBUG(start[256])
D/ExynosCameraPipe( 2341): [CAM_ID(1)][PIPE_SCP_FRONT]-DEBUG(start[256])
D/ExynosCameraPipe( 2341): [CAM_ID(1)][PIPE_ISP_FRONT]-DEBUG(start[256])
Click to expand...
Click to collapse
Anybody who can point me into the right direction to solve this issue ?
open the battery bay, push phone's battery points a little towards outside. One of my alpha was doing this and it was a loose battery point.
+ PIT,what that mean,why you flashing pit?
I think there is problem,pit untiked must be
hensk said:
+ PIT,what that mean,why you flashing pit?
I think there is problem,pit untiked must be
Click to expand...
Click to collapse
I tried first without PIT file, but after still having problems i think with PIT for FULL wipe (repartition) mayb problem will go.
dork997 said:
open the battery bay, push phone's battery points a little towards outside. One of my alpha was doing this and it was a loose battery point.
Click to expand...
Click to collapse
Pushed all the point a bit forward and still crashing,
From the error logs what i can see something goes wrong with the camerabuffer
D/ExynosCamera( 2341): [CAM_ID(1)][]-DEBUG(m_createIonAllocator[8664]):m_createI
onAllocator success (allocator=0xb7a9d510)
D/ExynosCamera( 2341): [CAM_ID(1)][]-DEBUG(m_createBufferManager[8694]):m_create
IonAllocator success
D/ExynosCamera( 2341): [CAM_ID(1)][]-DEBUG(m_createBufferManager):BufferManager(
BAYER_BUF) created
D/ExynosCamera( 2341): [CAM_ID(1)][]-DEBUG(m_createBufferManager):BufferManager(
3A1_BUF) created
D/ExynosCamera( 2341): [CAM_ID(1)][]-DEBUG(m_createBufferManager):BufferManager(
ISP_BUF) created
D/ExynosCamera( 2341): [CAM_ID(1)][]-DEBUG(m_createBufferManager):BufferManager(
ISP_RE_BUF) created
D/ExynosCamera( 2341): [CAM_ID(1)][]-DEBUG(m_createBufferManager):BufferManager(
SCC_RE_BUF) created
D/ExynosCamera( 2341): [CAM_ID(1)][]-DEBUG(m_createBufferManager):BufferManager(
SCC_BUF) created
D/ExynosCamera( 2341): [CAM_ID(1)][]-DEBUG(m_createBufferManager):BufferManager(
GSC_BUF) created
D/ExynosCamera( 2341): [CAM_ID(1)][]-DEBUG(m_createBufferManager):BufferManager(
JPEG_BUF) created
D/ExynosCamera( 2341): [CAM_ID(1)][]-DEBUG(m_createBufferManager):BufferManager(
VDIS_BUF) created
Click to expand...
Click to collapse
and then it crashes
I think you **** up nand with repartition,servis pls
only solution now
hensk said:
I think you **** up nand with repartition,servis pls
only solution now
Click to expand...
Click to collapse
It was already messed up BEFORE repartition my friend.
cbza said:
Pushed all the point a bit forward and still crashing,
From the error logs what i can see something goes wrong with the camerabuffer
and then it crashes
Click to expand...
Click to collapse
Try lollipop? ur device is already crashing ...wont hurt to try?
dork997 said:
Try lollipop? ur device is already crashing ...wont hurt to try?
Click to expand...
Click to collapse
currently at 50% , i hope it will fix the problem but i doubt it...
Finished installation of lollipop, factory wiped cache and data, problem still persists
cbza said:
currently at 50% , i hope it will fix the problem but i doubt it...
Finished installation of lollipop, factory wiped cache and data, problem still persists
Click to expand...
Click to collapse
I have nothing else on mind that you could try...Problem with alpha is the lack of support...if this were s4 or s5 someone would have read your log and diagnosed the problem...but i guess u will have to wait ..if ur lucky someone might reply
why dont download last 4.4.4 firmwere for your SCS from sammobile,& flash it with odin
try it & wrote hire info
Same
Same issue here, tried with factory reset and 4.4 and 5.0 (FR) without success.
Any fresh ideas?
Do tou guys use any specific app after resetibg or flshing fw?
Sent from my SM-G850F
hey, exactly the same problem here at the most random moments, most of the times the galaxy makes a very loud noise too when it crashes.
tried a lot of hard resets and stuff but still nothing that helps.
Same problem by me also!
Any fix yet?
now starting at my end as well...
more detailed:
http://forum.xda-developers.com/galaxy-alpha/help/complete-freezings-t3266214
Related
Hi All,
I have been running the gingerbread rom for 2 days (rc2) and i was very happy with it. Untill yesterday evening out of the blue my sdcard was bricked.
Ofcource my phone cant finish booting anymore because some parts of the system are actualy on the sdcard.
fastboot works.
fastboot oem enableqxdm 0
fastboot oem eraseconfig
both return OK but it doesnt help. Tried different SDCARD same result.
I am not in panic because i know this must be solvable.
I have been searching for hours but no luck for me in finding the solution yet.
There is a lot of information to find, but most of it regards a combined USB/SDCARD brick. My USB is perfect.
any help would be much appreciated.
btw, recovery works, but does not see the sdcard as well.
i have S-OFF (alpharef)
fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x21F04
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is VODAPE17
INFOsetting->cid::VODAPE17
INFOserial number: SH07CPL00582
INFOcommandline from head: no_console_suspend=1 msmsdcc_sdioirq=
INFO1 wire.search_count=5
INFOcommand line length =469
INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.
INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.09.05.30_2 androidboot.cid
INFO=VODAPE17 androidboot.carrier=VODA-Netherland androidboot.mi
INFOd=PB9920000 androidboot.keycaps=qwerty androidboot.mode=norm
INFOal androidboot.serialno=SH07CPL00582 androidboot.bootloader=
INFO0.93.0001 no_console_suspend=1 msmsdcc_sdioirq=1 wire.search
INFO_count=5
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:116987 msec
FAILED (status read failed (Timer expired))
in recovery adb works!
Zobat said:
in recovery adb works!
Click to expand...
Click to collapse
just use Pocket Mechanic Professional v2.98 able to format and return the SD Card which is not recognized by the device (SDCard RAW)
Hakim Rahman said:
just use Pocket Mechanic Professional v2.98 able to format and return the SD Card which is not recognized by the device (SDCard RAW)
Click to expand...
Click to collapse
Thnx for the reply but i dont use windows on any of my systems. I dont like the idea of programes "magicly" fixing my problem. I wanna understand stuff.
anyway, i am a lot further now. I have to confess i cant reproduce my fix, i have more than a dozen open browserwindows as a result of my search for resolving this issue. Its probably not even an oxygen issue, but i am not sure of that.
I have my sdcard mounted now again and currently transfering a clockwork mod backup dir to it.
gonna try to use regular recoverymode with these files when i'm done
regards
fixed, sorry for the cluttering up of this board.
I donated 25 dollars.
kind regards
Zobat said:
fixed, sorry for the cluttering up of this board.
I donated 25 dollars.
kind regards
Click to expand...
Click to collapse
You try Hard Reset, or reupload ROM SHIP??
does anyone know whats the solution of this?
im trying to deodexed SGY DXLE1 stock rom so that i can have my own themes,
i always get an error every time i choose step 3 in xUltimate 2.4
Starting AccountAndSyncSettings.odex
*****************************************
* Deodexing... *
UNEXPECTED TOP-LEVEL EXCEPTION:
org.jf.dexlib.Util.ExceptionWithContext: regCount does not match the number of a
rguments of the method
at org.jf.dexlib.Util.ExceptionWithContext.withContext(ExceptionWithCont
ext.java:54)
at org.jf.dexlib.Code.InstructionIterator.IterateInstructions(Instructio
nIterator.java:92)
at org.jf.dexlib.CodeItem.readItem(CodeItem.java:154)
at org.jf.dexlib.Item.readFrom(Item.java:76)
at org.jf.dexlib.OffsettedSection.readItems(OffsettedSection.java:48)
at org.jf.dexlib.Section.readFrom(Section.java:143)
at org.jf.dexlib.DexFile.<init>(DexFile.java:431)
at org.jf.baksmali.main.main(main.java:265)
Caused by: java.lang.RuntimeException: regCount does not match the number of arg
uments of the method
at org.jf.dexlib.Code.Format.Instruction3rc.checkItem(Instruction3rc.jav
a:129)
at org.jf.dexlib.Code.Format.Instruction3rc.<init>(Instruction3rc.java:7
9)
at org.jf.dexlib.Code.Format.Instruction3rc.<init>(Instruction3rc.java:4
4)
at org.jf.dexlib.Code.Format.Instruction3rc$Factory.makeInstruction(Inst
ruction3rc.java:145)
at org.jf.dexlib.Code.InstructionIterator.IterateInstructions(Instructio
nIterator.java:84)
... 6 more
Error occured at code address 8
code_item @0x25cc
Press any key to continue . . .
Click to expand...
Click to collapse
Bump.. anyone encountered this kind of error when deodexing a stock rom?
i did!
iMaker said:
Bump.. anyone encountered this kind of error when deodexing a stock rom?
Click to expand...
Click to collapse
i did! and someguyfromhell also did see this thread http://forum.xda-developers.com/showthread.php?t=1711815 but no solution still ! maybe if they find a solution it'll help us too.....
Hi,
After flashing MT27i_6.1.1.B.1.10_KERNEL.ftf with Flashtool and reboot I started root and got this error. Tried several times.
Pushing fake Backup
4615 KB/s (73728 bytes in 0.015s)
Extracting fakebackup on device ...
tar: can't make dir RootMe: No space left on device
tar: can't create directory 'RootMe': No space left on device
tar: can't open 'RootMe/.recordmanifest': No such file or directory
Watch now your device. Select the backup named RootMe and restore it!
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.L
AUNCHER] cmp=com.sonyericsson.vendor.backuprestore/.ui.BackupActivity }
Warning: Activity not started, its current task has been brought to the front
If all is successful i will tell you, if not this shell will run forever.
Running ......
running forever...
Could you help me?
Flash memory and internal memory were switched during previous failed flashing.
Ok, I removed some data from memory. Now it is running Ok.
Pushing fake Backup
4615 KB/s (73728 bytes in 0.015s)
Extracting fakebackup on device ...
Watch now your device. Select the backup named RootMe and restore it!
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.L
AUNCHER] cmp=com.sonyericsson.vendor.backuprestore/.ui.BackupActivity }
Warning: Activity not started, its current task has been brought to the front
If all is successful i will tell you, if not this shell will run forever.
Running ......
BUT!!! During restore I got a warning in phone: Reconnect external memory and try again.
However I got message in CMD: Good, it worked! Now we are rebooting soon, please be patient!
Is that Ok?
tchelyshev said:
Ok, I removed some data from memory. Now it is running Ok.
Pushing fake Backup
4615 KB/s (73728 bytes in 0.015s)
Extracting fakebackup on device ...
Watch now your device. Select the backup named RootMe and restore it!
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.L
AUNCHER] cmp=com.sonyericsson.vendor.backuprestore/.ui.BackupActivity }
Warning: Activity not started, its current task has been brought to the front
If all is successful i will tell you, if not this shell will run forever.
Running ......
BUT!!! During restore I got a warning in phone: Reconnect external memory and try again.
However I got message in CMD: Good, it worked! Now we are rebooting soon, please be patient!
Is that Ok?
Click to expand...
Click to collapse
yeah's that ok already,you should see Supersu App now...
Ben Ling said:
yeah's that ok already,you should see Supersu App now...
Click to expand...
Click to collapse
I chose Superuser instead of Supersu. Is that ok?
tchelyshev said:
I chose Superuser instead of Supersu. Is that ok?
Click to expand...
Click to collapse
but i install with that method i get SuperSu.
You got Superuser?
I think is ok,try to get permissions by using Root Explorer.
tchelyshev said:
I chose Superuser instead of Supersu. Is that ok?
Click to expand...
Click to collapse
OK. I have superSU now after root. But I cannot enter recovery mode pushing vol down button when Sony logo appears.
Please help! I have tried everything, but I still can not enter recovery mode..
reconnect external mem error
tchelyshev said:
Ok, I removed some data from memory. Now it is running Ok.
Pushing fake Backup
4615 KB/s (73728 bytes in 0.015s)
Extracting fakebackup on device ...
Watch now your device. Select the backup named RootMe and restore it!
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.L
AUNCHER] cmp=com.sonyericsson.vendor.backuprestore/.ui.BackupActivity }
Warning: Activity not started, its current task has been brought to the front
If all is successful i will tell you, if not this shell will run forever.
Running ......
BUT!!! During restore I got a warning in phone: Reconnect external memory and try again.
However I got message in CMD: Good, it worked! Now we are rebooting soon, please be patient!
Is that Ok?
Click to expand...
Click to collapse
dear friend im facing the same error(Reconnect external memory and try again) while rooting . please help me how you solved this ?
This is my mail [email protected]
Hello everyone
I've managed to unlock and root my SGP312 (pollux_windy). Because I always liked AOKP, I tried to install this custom ROM. Here's what I did:
1) Flashed Little Kernel into /boot while in Sony's Fastboot Mode
2) Flashed extracted boot.img of AOKP into "boot" and newest TWRP recovery (v2.6.3) into "recovery" while in LK's Fastboot Mode
3) Rebooted into TWRP recovery, wiped data, cache and dalvik cache
4) Flashed newest AOKP version (jb-mr2 milestone #1 for pollux_windy)
5) Flashed gapps (gapps-jb-20130813-signed.zip)
And tada, the custom ROM booted and everything was fine... No force closes / crashes, no problems, everything worked like a charm.. except the god damn Play Store! Whenever I open the Play Store, it only says "No connection". Pressing retry doesn't help at all. Ofcourse I always search through some forums before posting an issue, so here's what I've already tried:
- Other custom ROM (CM 10.2 stable for pollux_windy)
- Other gapps package (pa_gapps-full-4.3-20131102-signed.zip)
- Force Google Play Store and Google Play Services to stop and delete their data
- Wiped cache and dalvik cache
- Tried a connection without native IPv6 (WLAN hotspot of my HTC One, going over mobile internet which is clearly IPv4 only)
- Checked /etc/hosts (only contains 127.0.0.1 localhost)
- Executed Shark for Root -> There is clearly some data activity going on, my tablet seems to send some data to the google servers but they return an empty response as it seems (see logcat down below)? Unfortunately I am not able to analyze the packets, thanks to SSL/HTTPS...
- Changed some build.prop settings to match an original installation (model=SGP312, device=SGP312 and so on...)
And none of these methods worked. I am totally clueless what else I could try? Here's a logcat snippet:
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
My build.prop is now reverted to the original AOKP build.prop, which can be found here: dl.snapserv.net/build.prop.txt (Sorry, I am not allowed to post links yet...) Have you guys any idea? XDA is basically my last hope, otherwise it seems like I am doomed to use the stock ROM :/ Or did I do something wrong?
Thanks for reading and have a nice day!
Regards
NeoXiD
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
[/QUOTE]
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
bondcheg said:
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
Click to expand...
Click to collapse
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. (How I found that problem? I just went so far that I've intercepted the traffic to the google servers with a fake root certificate and Fiddler...) Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD
NeoXiD said:
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
Click to expand...
Click to collapse
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD[/QUOTE]
I`m novice user and never conneced my device with adb and dont know how to do it.
bondcheg said:
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD
I`m novice user and never conneced my device with adb and dont know how to do it.
Click to expand...
Click to collapse
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
NeoXiD said:
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
Click to expand...
Click to collapse
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
---------- Post added at 06:51 PM ---------- Previous post was at 06:46 PM ----------
NeoXiD said:
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
Click to expand...
Click to collapse
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
Emm i done mostly all you listened at the thread start but nothing helps.
Only other ROMs works fine. In any other ROMs play market have no errors. But in case i done all as guides says why other people a500 with this ROM works fine but not mine?
Sry for my english.
bondcheg said:
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
---------- Post added at 06:51 PM ---------- Previous post was at 06:46 PM ----------
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
Emm i done mostly all you listened at the thread start but nothing helps.
Only other ROMs works fine. In any other ROMs play market have no errors. But in case i done all as guides says why other people a500 with this ROM works fine but not mine?
Sry for my english.
Click to expand...
Click to collapse
That might be the fault then, because it might get interpreted as serial number '0', which might get rejected by Google. Did you flash any custom bootloader? Normally this should not occur... You can also drop me a PM so we do not spam this thread with a 4-eye-conversation.
Regards
NeoXiD
Hey guys,
I tried sideloading the 4.4 Dialer into my system/priv-app/ folder and yet it only crashes every single time. (yes I set the permissions to 0644)
Does anyone ... has anyone tried moving / porting this?
Pulled the Dialer from here
http://www.androidpolice.com/2013/1...n-doesnt-show-up-in-my-app-tray-what-can-i-do
Sparatan117 said:
I tried sideloading the 4.4 Dialer into my system/priv-app/ folder and yet it only crashes every single time
Click to expand...
Click to collapse
Well I tried it and it works fine. You didn't describe how you tried to install it though, making it rather hard to spot where you went astray.
I'd bet though that you didn't wipe the cache and data in the Application manager plus wipe Dalvik from recovery.
What do I win for being right.. ?
ps: the md5 should be 65:1e:d1:f2:61:07:f9:6e:62:2c:81:08:83:c4:53:a3
.
fffft said:
Well I tried it and it works fine. You didn't describe how you tried to install it though, making it rather hard to spot where you went astray.
I'd bet though that you didn't wipe the cache and data in the Application manager plus wipe Dalvik from recovery.
What do I win for being right.. ?
ps: the md5 should be 65:1e:d1:f2:61:07:f9:6e:62:2c:81:08:83:c4:53:a3
.
Click to expand...
Click to collapse
You know, I would have loved if it had worked, but it didn't ...
I put the APK directly into priv-apps
set the privilages to 0644
cleared the data from the app
cleared the Dalvik Cache
... still force close... thoughts?
EDIT:
I tried just straight up installing it without it being a system app and it works just fine. Go figure...
Edit 2: Nevermind haha
Resorting to flashing via Recovery. See if this works
Edit 3:
Flashed via Recovery. Emptied Dalvik Cache/Cache on the way in. Still Force Closes.
Sparatan117 said:
You know, I would have loved if it had worked, but it didn't ...
I put the APK directly into priv-apps
set the privilages to 0644
cleared the data from the app
cleared the Dalvik Cache
... still force close... thoughts?
EDIT:
I tried just straight up installing it without it being a system app and it works just fine. Go figure...
Click to expand...
Click to collapse
Are you using a stock unmodified rom?
Like with just towel root or something similar?
Sparatan117 said:
I tried just straight up installing it without it being a system app and it works just fine. Go figure...
Click to expand...
Click to collapse
Okay, I get it.. you don't want to pay off the bet.
=8-0
Sure, whatever. Glad it's working for you though. And it works for the rest of us too.
Good enough.
.
---------- Post added at 07:39 PM ---------- Previous post was at 07:35 PM ----------
Sparatan117 said:
Edit 3:
Flashed via Recovery. Emptied Dalvik Cache/Cache on the way in. Still Force Closes.
Click to expand...
Click to collapse
Seriously? That doesn't make any sense.
I installed it on two systems and it was super easy and has been super stable. And there are 100+ comments on the original article without anyone there having issues either. Write out a detailed description of all the steps you took to install it so we can see where you went wrong.
.
Yeah well I guess pretty close to stock
I have Beans NF6 Factory build (upgrade without wiping data)
I have Chainfire's autoroot
Flashed TWRP recovery
Flashed the file via this ( http://www.androidfilehost.com/?fid=23269279319196848 ) file.
Wiped Dalvik/Cache via TWRP
Rebooted
Wiped data in App Manager
Started.
[insert picture of dog poop]
but in all seriousness I don't get it either... it's weird.
Although I'm glad I'm not the only one.
Sparatan117 said:
but in all seriousness I don't get it either... it's weird.
Although I'm glad I'm not the only one.
Click to expand...
Click to collapse
Okay, two of you ran into problems trying to install it. Still just a minor glitch.
To troubleshoot this though, we need you to be a lot more detailed. You didn't mention a lot of things.. e.g. you didn't say anything about checking permissions in your description.. so did you? And what was the result? Did you check the md5? Did you wipe the cache from the Application manager.. you only mention wiping the data. I know, picky, picky. But troubleshooting is all about the details. And we need to those things if we are to pin down the cause.
I'm also wondering about the order you wiped the data /cache. It's normally done in the reverse and that may be causing you problems. Wiping Dalvik should be the last step.
This procedure works. I've tried it three times now:
Check md5 of download
Move dialer to /system/priv-app
Confirm that permissions are 0644
[you can try running it at this point if you want to. it will force close at this point]
Open the Application manager i.e. Settings > Applications > Application Manager > All > Google Dialer
Force Stop > Clear cache > Clear data > OK
Reboot to recovery mode > wipe cache + Dalvik
Reboot to system
Open app drawer, click on Google Dialer & observe that it works properly
.
bumpkiss
Code:
--------- beginning of /dev/log/system
E/Watchdog( 746): [email protected] 1
E/PersonaManagerService( 746): Unable to read user list
E/PersonaManagerService( 746): Unable to read user list
E/PersonaManagerService( 746): Unable to read user list
E/PersonaManagerService( 746): returning null in getPersonasForUser
E/MotionRecognitionService( 746): mReceiver.onReceive : ACTION_USER_PRESENT :: UNLOCK SCREEN
E/SmartFaceService - 3rd party pause( 746): onReceive, ACTION_STATUS_BAR_ANIMATING: true
E/SmartFaceService - 3rd party pause( 746): onReceive, ACTION_STATUS_BAR_EXPANDED: true
E/ActivityThread( 4896): Failed to find provider info for com.dropbox.carousel.CuOwnerCheckProvider
E/SmartFaceService - 3rd party pause( 746): onReceive, ACTION_STATUS_BAR_COLLAPSED: false
E/PersonaManagerService( 746): Unable to read user list
E/ActivityThread( 5740): Failed to find provider info for com.amazon.dcp.settings
E/Watchdog( 746): [email protected] 2
E/ConnectivityService( 746): Attempt to connect to mobile_mms failed (dataEnabled).
E/PersonaManagerService( 746): Unable to read user list
--------- beginning of /dev/log/main
E/MTPJNIInterface( 6390): Status for mount/Unmount :mounted
E/MTPJNIInterface( 6390): SDcard is available
E/SQLiteLog( 6390): (21) API call with NULL database connection pointer
E/SQLiteLog( 6390): (21) misuse at line 96852 of [00bb9c9ce4]
E/SQLiteLog( 6390): (21) API call with NULL database connection pointer
E/SQLiteLog( 6390): (21) misuse at line 93317 of [00bb9c9ce4]
E/SQLiteLog( 6390): (21) API call with NULL database connection pointer
E/SQLiteLog( 6390): (21) misuse at line 93317 of [00bb9c9ce4]
E/SQLiteLog( 6390): (21) API call with NULL database connection pointer
E/SQLiteLog( 6390): (21) misuse at line 96852 of [00bb9c9ce4]
E/ ( 6390): [mtp_init_device] After open the MTP fd = 59 and line = 678...
E/MTPJNIInterface( 6390): Getting gadget reset status0
E/LightSensor( 746): RED : 1, GREEN : 1, BLUE : 1, CLEAR : 1, CALCULATED LUX : 0.000000, CCT : 1596.000000, REAL LUX : 0.000000 a_time = 238, gain = 64, ir=1, rp1=1, gp1=0, bp1=0, cp1=0, cpl=3202560
E/SPPClientService( 6195): [[SystemStateMonitorService]] SystemStateMonitorService : noConnect? : false
E/SMD ( 257): DCD ON
E/LightSensor( 746): RED : 1, GREEN : 1, BLUE : 1, CLEAR : 1, CALCULATED LUX : 0.000000, CCT : 1596.000000, REAL LUX : 0.000000 a_time = 238, gain = 64, ir=1, rp1=1, gp1=0, bp1=0, cp1=0, cpl=3202560
E/MTPRx ( 6390): state from USB_STATE event DISCONNECTED
E/MTPRx ( 6390): ignore this event
E/DataRouter( 267): USB Interface is open with 0x9
E/SMD ( 257): ***Received data notification[DR->SMD]***
E/SMD ( 257): Path set is DATA_PATH_DR_SMD_MANAGER
E/SMD ( 257): Message:
E/SMD ( 257): Sending data to SMD: Len = [3]
E/SMD ( 257): buffer = []
E/SMD ( 257): Wrote 3 chars to SMD PORT fd=7 ch = 81
E/LightSensor( 746): RED : 1, GREEN : 1, BLUE : 1, CLEAR : 1, CALCULATED LUX : 0.000000, CCT : 1596.000000, REAL LUX : 0.000000 a_time = 238, gain = 64, ir=1, rp1=1, gp1=0, bp1=0, cp1=0, cpl=3202560
E/MTPRx ( 6390): state from USB_STATE event CONNECTED
E/MTPRx ( 6390): state from USB_STATE event DISCONNECTED
E/MTPRx ( 6390): stop observing and calling usbRemoved
E/MTPRx ( 6390): sendbooster is false!
E/MTPRx ( 6390): In usbRemoved Status bar enabled
E/MTPRx ( 6390): Sending Broadcast
E/SPPClientService( 6195): [[SystemStateMonitorService]] SystemStateMonitorService : noConnect? : false
E/MtpService( 6390): onDestroy.
E/MtpService( 6390): Unregister Mtp disable Receiver
E/MtpService( 6390): Receiver not registered: [email protected]
E/MtpService( 6390): Unregister mtpEmergencyReceiver
E/MtpService( 6390): Receiver not registered: [email protected]
E/MtpService( 6390): unregistering mtpMediaReceiver in UnregisterAllIntent
E/MtpService( 6390): Receiver not registered: [email protected]
E/MTPJNIInterface( 6390): noti = 3
Sparatan117 said:
--------- beginning of /dev/log/system
E/Watchdog( 746): [email protected] 1
Click to expand...
Click to collapse
Thanks for that but that log isn't deep enough to answer most of our questions. But if you could tackle the ones I posed in my last post? And can you try the install procedure that I suggested? It should work or at least give us some insight into what is failing.
Meanwhile, the dialer works here.
.
fffft said:
Thanks for that but that log isn't deep enough to answer most of our questions. But if you could tackle the ones I posed in my last post? And can you try the install procedure that I suggested? It should work or at least give us some insight into what is failing.
Meanwhile, the dialer works here.
.
Click to expand...
Click to collapse
Does it work if you click the call button?
aooga said:
Does it work if you click the call button?
Click to expand...
Click to collapse
Yes it does (just tried it)
Sorry, I did follow your procedure to the letter, and the last post I posted was the result.
I'm thinking it's just not going to happen. Maybe a full system wipe is needed... or something. Who knows. Thanks for trying though.