CLOSED
Sources
CLOSED
Reserved for Updates and or Room to breathe.
The logs, Where things stand logcat -dC | grep audio
Sorted
logcat -dC | grep media
Sorted
moonbutt74 said:
Code:
[email protected]:~# adb shell logcat -dC | grep media
[COLOR="Red"]E/mm-camera-sensor( 254): sensor_init_probe:326 num_media_devices = 0
E/mm-camera-sensor( 254): sensor_init_probe:328 dev_name = /dev/media0
E/mm-camera-sensor( 254): sensor_init_probe:335 num_media_devices = 1
E/mm-camera-sensor( 254): sensor_init_probe:326 num_media_devices = 1
E/mm-camera-sensor( 254): sensor_init_probe:328 dev_name = /dev/media1
E/mm-camera-sensor( 254): sensor_init_probe:335 num_media_devices = 2
E/mm-camera-sensor( 254): sensor_init_probe:356 Done enumerating media entities
E/mm-camera-sensor( 254): sensor_init_probe:326 num_media_devices = 2
E/mm-camera-sensor( 254): sensor_init_probe:328 dev_name = /dev/media2
E/mm-camera-sensor( 254): sensor_init_probe:331 Done enumerating media devices
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4406 media device number = 1 msm_config
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4419 Done enumerating media entities
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4406 media device number = 2 msm_cam_dummy
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4419 Done enumerating media entities
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4406 media device number = 3 msm_camera
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4419 Done enumerating media entities
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4406 media device number = 4 msm_camera
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4419 Done enumerating media entities
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4394 Done enumerating media devices-failed: 4[/COLOR]
[COLOR="Olive"]I/mediaserver( 250): ServiceManager: 0xb87da448
I/dalvikvm( 244): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)
I/dalvikvm( 244): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)
I/dalvikvm( 244): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)
I/dalvikvm( 244): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)[/COLOR]
[COLOR="Olive"]I/AppOps ( 711): Pruning old package media/1013: new uid=-1[/COLOR]
D/ExtendedUtils( 250): printFileName fd(24) -> /system/media/audio/ui/Lock.ogg
D/SystemUIService( 783): loading: class com.android.systemui.media.RingtonePlayer
D/SystemUIService( 783): running: [email protected]
D/ExtendedUtils( 250): printFileName fd(24) -> /system/media/audio/ui/Unlock.ogg
[COLOR="Olive"]I/ActivityManager( 711): Start proc android.process.media for broadcast com.android.providers.media/.MtpReceiver: pid=862 uid=10006 gids={50006, 1028, 1015, 1023, 1024, 2001, 3003, 3007}[/COLOR]
D/ActivityThread( 862): handleBindApplication:android.process.media
[COLOR="Red"]E/MediaFocusControl( 711): at android.media.MediaFocusControl.registerRemoteControlDisplay_int(MediaFocusControl.java:2182)
E/MediaFocusControl( 711): at android.media.MediaFocusControl.registerRemoteController(MediaFocusControl.java:217)
E/MediaFocusControl( 711): at android.media.AudioService.registerRemoteController(AudioService.java:4538)
E/MediaFocusControl( 711): at android.media.IAudioService$Stub.onTransact(IAudioService.java:614)[/COLOR]
[COLOR="Olive"]I/ActivityManager( 711): Start proc com.google.android.gms for service com.google.android.gms/.cast.media.CastRemoteDisplayProviderService: pid=1061 uid=10076 gids={50076, 3003, 1007, 1028, 1015, 1006, 3002, 3001, 3007, 2001, 3006}[/COLOR]
[COLOR="Red"]E/MediaFocusControl( 711): at android.media.MediaFocusControl.registerRemoteControlDisplay_int(MediaFocusControl.java:2182)
E/MediaFocusControl( 711): at android.media.MediaFocusControl.registerRemoteControlDisplay(MediaFocusControl.java:230)
E/MediaFocusControl( 711): at android.media.AudioService.registerRemoteControlDisplay(AudioService.java:4542)
E/MediaFocusControl( 711): at android.media.IAudioService$Stub.onTransact(IAudioService.java:593)[/COLOR]
[COLOR="Olive"]I/iu.UploadsManager( 1061): End new media; added: 0, uploading: 0, time: 58 ms[/COLOR]
[COLOR="DarkOrange"]W/ContextImpl( 711): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1607 android.bluetooth.BluetoothHeadset.doBind:283 android.bluetooth.BluetoothHeadset.<init>:276 android.bluetooth.BluetoothAdapter.getProfileProxy:1369 android.media.AudioService.getBluetoothHeadset:2364
W/ContextImpl( 711): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1607 android.bluetooth.BluetoothA2dp.doBind:165 android.bluetooth.BluetoothA2dp.<init>:158 android.bluetooth.BluetoothAdapter.getProfileProxy:1372 android.media.AudioService$AudioServiceBroadcastReceiver.onReceive:4388 [/COLOR]
D/ExtendedUtils( 250): printFileName fd(26) -> /system/media/audio/ui/Effect_Tick.ogg
D/ExtendedUtils( 250): printFileName fd(26) -> /system/media/audio/ui/KeypressStandard.ogg
D/ExtendedUtils( 250): printFileName fd(26) -> /system/media/audio/ui/KeypressSpacebar.ogg
D/ExtendedUtils( 250): printFileName fd(26) -> /system/media/audio/ui/KeypressDelete.ogg
D/ExtendedUtils( 250): printFileName fd(26) -> /system/media/audio/ui/KeypressReturn.ogg
D/ExtendedUtils( 250): printFileName fd(26) -> /system/media/audio/ui/KeypressInvalid.ogg
[COLOR="Olive"]I/ActivityManager( 711): Delay finish: com.android.providers.media/.MtpReceiver
I/iu.UploadsManager( 1061): End new media; added: 0, uploading: 0, time: 88 ms[/COLOR]
@Zaphodspeaks,
Z, try a dpi setting of 176, @180 i lose the splitscreen in settings, but at 176 text size seems less unreasonable.
Click to expand...
Click to collapse
Will do, personally I don't care much for split screen, but Ill give it a shot!
so far with out posting a Logcat, the only issue that bothers me is that it will not connect to my 2.4 GHZ & 5G, while using WPA2 AES Wireless encryption, it plain out does not like my Linksys E3000 Router even when I left it unencrypted, but will connect to my neighbors wifi which is left open. I feels like it can be used as a daily driver if you don't mind the lack of sound.. It runs smooth, its snappy and has not given me any kind of error or crash so far..
Z,
hi, thanks i'll see what i can find on Linksys routers, also i will be looking at what sbu77 and starlight are doing with wifi,wcnss and mac issues.
You have no issue connecting with stock rom, because of the above issue if i understood what i read on the mac address issue correctly.
This current build would suffer from the same issue.
m
Edit, i am wondering how many times i can say issue in a post about a specific issue.
I have issues. xD
Kernel Updated concerning wifi/mac address ISSUE as discussed ny @starlightknight in this post at his?/her? thread
http://forum.xda-developers.com/showpost.php?p=60354789&postcount=188
see OP for details
Kernel Update [OPTIONAL]
Sorted
moonbutt74 said:
Z,
hi, thanks i'll see what i can find on Linksys routers, also i will be looking at what sbu77 and starlight are doing with wifi,wcnss and mac issues.
You have no issue connecting with stock rom, because of the above issue if i understood what i read on the mac address issue correctly.
This current build would suffer from the same issue.
m
Edit, i am wondering how many times i can say issue in a post about a specific issue.
I have issues. xD
Kernel Updated concerning wifi/mac address ISSUE as discussed ny @starlightknight in this post at his?/her? thread
http://forum.xda-developers.com/showpost.php?p=60354789&postcount=188
see OP for details
Click to expand...
Click to collapse
Oh I forgot to mention that my Cisco/Linksys E3000 is running DD-WRT.. Not the stock ROM..
Edit, I'll post my results as soon as I finish some chores..
I'm really eager to work with this.. Even with out sound, and if the WIFI fix works.. and I'm sure it will..
This will become my daily driver.. for a couple of weeks..
Edit2:
I reinstalled your build, plus adding the updated Kernel..
Same exact issue, could not connect to anything... Even when I left my WiFi open..
Neighbors wifi does connect still as it did yesterday.. Which is not encrypted..
Edit3!!!!!
BINGO I GOT IT!
It was my MAC address filtering that prevented the device from connecting, even though it was on the safe list..
By disabling MAC Filtering, I was successfully able to connect!
moonbutt74 said:
Z,
hi, thanks i'll see what i can find on Linksys routers, also i will be looking at what sbu77 and starlight are doing with wifi,wcnss and mac issues.
You have no issue connecting with stock rom, because of the above issue if i understood what i read on the mac address issue correctly.
This current build would suffer from the same issue.
m
Edit, i am wondering how many times i can say issue in a post about a specific issue.
I have issues. xD
Click to expand...
Click to collapse
You are an issue!
Opinion / Feedback
My opinion/feedback:
I'm an average not-knowing-code person. This ROM by far is great, WiFi works, apps work, Speaker sound doesn't work but the headphone jack works great, besides i use headphones like 95% of all time. Main operations work well for me and i will take this as my daily driver. I will report if there is any issue and will try to provide a logcat. Thanks for the Developers on bringing a better ROM to our device than boring, laggy TouchWiz!
Rusell said:
My opinion/feedback:
I'm an average not-knowing-code person. This ROM by far is great, WiFi works, apps work, Speaker sound doesn't work but the headphone jack works great, besides i use headphones like 95% of all time. Main operations work well for me and i will take this as my daily driver. I will report if there is any issue and will try to provide a logcat. Thanks for the Developers on bringing a better ROM to our device than boring, laggy TouchWiz!
Click to expand...
Click to collapse
The phones work ? No 5hit ? so something's not routing right. Russ, huge good tip, thanks for the assist !:good:
m
Been using this ROM since yesterday afternoon and it is quite stable. There is a few issues here and there but all in all it is snappy and way better than stock. The main issues I have had were the magnetic case not waking the device up when opening and as mention by the OP, the speaker sound issue
wire55 said:
Been using this ROM since yesterday afternoon and it is quite stable. There is a few issues here and there but all in all it is snappy and way better than stock. The main issues I have had were the magnetic case not waking the device up when opening and as mention by the OP, the speaker sound issue
Click to expand...
Click to collapse
Also as stated in op, I will not be taking requests of any kind, which the magnetic cover mention sounds like.
I have no interest in in the subject, sound is my concern. I do appreciate your interest though, thank you.
I also expressed a desire in the OP for a more capable developer to pick this project up.
To be straight foward, i totally suck at building roms and am suprised i got this far. :silly:
Every build since the one posted has once again begun to not boot, fail, to mount storage, or surface flinger dies.
This is truly going to drive me mad.
moonbutt74 said:
Also as stated in op, I will not be taking requests of any kind, which the magnetic cover mention sounds like.
I have no interest in in the subject, sound is my concern. I do appreciate your interest though, thank you.
I also expressed a desire in the OP for a more capable developer to pick this project up.
To be straight foward, i totally suck at building roms and am suprised i got this far. :silly:
Every build since the one posted has once again begun to not boot, fail, to mount storage, or surface flinger dies.
This is truly going to drive me mad.
Click to expand...
Click to collapse
I am asking of nothing. I was just stating something that I came upon in the ROM. I do thank you for all the support you have given. I would pick this up if I had passed experience, but I have never attempted because of how old my laptopvis.
wire55 said:
Been using this ROM since yesterday afternoon and it is quite stable. There is a few issues here and there but all in all it is snappy and way better than stock. The main issues I have had were the magnetic case not waking the device up when opening and as mention by the OP, the speaker sound issue
Click to expand...
Click to collapse
OMG, i hear you on the old laptop my builds take so freakin long i can feel my hair turning grey.
moonbutt74 said:
OMG, i hear you on the old laptop my builds take so freakin long i can feel my hair turning grey.
Click to expand...
Click to collapse
Yeah! Thank god I'm not the only one using old technology. My laptop is from 2008 with 4gb ram and core 2 duo that runs really slow and overheats and crashed frequently.
wire55 said:
Yeah! Thank god I'm not the only one using old technology. My laptop is from 2008 with 4gb ram and core 2 duo that runs really slow and overheats and crashed frequently.
Click to expand...
Click to collapse
Slow is coooool !
xD
okay seriously though, any thoughts as to the sound issue ?
@moonbutt74 thanks for taking this on and spending all of the frustrating months on it your already have. I am not a ROM builder or developer, I just read a lot on forums of devices I have. With that on my Note 4 there is a mod that enables the front speaker with the rear speaker by @sshafranko in which he used the mixer_paths.xml file. I do not know if this will help at all, nor do I know exactly what is does, just trying to help. Here is his original thread (for people that don't read everything, this link is not for the Tab 4, it is reference only): http://forum.xda-developers.com/note-edge/development/mod-sm-915t-surround-sound-t2955648
Op if this is completely useless and you request, I will delete this post
moonbutt74 said:
Slow is coooool !
xD
okay seriously though, any thoughts as to the sound issue ?
Click to expand...
Click to collapse
If you ask me, I think the sound issue is kernel related.
Related
So I've been looking through the Desire on Nexus One ROM files, and determine a few discoveries with the FM Receiver on the N1.
1. It's present, and works partially (I can scan and get a list of good FM stations in my area)
2. Its controlled via the i2c bus off the snapdragon
3. HTC abandoned using BlueZ on the Desire, and cooked up a custom BT stack (this is at least partially contained in the file /system/bin/btld)
4. Its on the BCM4538 chip, not on the QSD8260 (that being said, looking at the Bravo/Desire kernel source, the QSD8260 is used for part of the audio path.
5. The custom BT stack used on the Desire controls the FM radio at least in part, this is also likely why Bluetooth doesn't work on these ROMs fully.
Here's a bit from the logcat:
I/BTL_IFC ( 578): btl_ifc_ctrl_rx: [BTL_IFC CTRL] recv BTLIF_FM_SEARCH (FM) 10 pbytes (hdl 151)
I/com_broadcom_bt_service_fm_FmReceiverService.cpp( 578): decodePendingEvent: Event ID: 4366
I/com_broadcom_bt_service_fm_FmReceiverService.cpp( 578): enqueuePendingEvent: event ID: 3, ATTACHING THREAD
I/com_broadcom_bt_service_fm_FmReceiverService.cpp( 578): enqueuePendingEvent: THREAD ATTACHED OK
I/com_broadcom_bt_service_fm_FmReceiverService.cpp( 578): [JNI] - TRANSMITTING EVENT UP : event = 3
I/BTAPP_FM( 1086): BTAPP_FM: btui_fm_cback: 3
I/BTAPP_FM( 1086): BTAPP_FM: BTA_FM_SEARCH_CMPL_EVT
I/BTAPP_FM( 1086): btapp_fm_volume_control = 176
I/BTAPP_FM( 1086): BTAPP_FM: clear_af_info
I/BTL-IFS ( 1086): send_ctrl_msg: [BTL_IFS CTRL] send UNKNOWN MSG ID (FM) 12 pbytes (hdl 15)
I/BTL_IFC ( 578): btl_ifc_ctrl_rx: [BTL_IFC CTRL] recv BTLIF_FM_SEARCH_CMPL_EVT (FM) 14 pbytes (hdl 151)
I/com_broadcom_bt_service_fm_FmReceiverService.cpp( 578): decodePendingEvent: Event ID: 4382
I/com_broadcom_bt_service_fm_FmReceiverService.cpp( 578): enqueuePendingEvent: event ID: 4, ATTACHING THREAD
I/com_broadcom_bt_service_fm_FmReceiverService.cpp( 578): enqueuePendingEvent: THREAD ATTACHED OK
I/com_broadcom_bt_service_fm_FmReceiverService.cpp( 578): [JNI] - TRANSMITTING EVENT UP : event = 4
V/FmReceiverEventLoop( 578): onRadioSearchCompleteEvent()
V/FmReceiverService( 578): onRadioSearchCompleteEvent()
D/FmReceiverService( 578): ******* ******* Processing job:FM_SEEK_STATION TimeSent:1:43:58 PM
D/FmReceiverService( 578): ***** ***** processCommands:[]
D/FmReceiverService( 578): []
D/FmReceiverService( 578): ****** ****** Adding FM Job: FM_SEEK_STATION TimeSent:not yet
D/FmReceiverService( 578): ***** ***** processCommands:[FM_SEEK_STATION TimeSent:not yet]
D/FmReceiverService( 578): ***** ***** processCommand:FM_SEEK_STATION TimeSent:1:43:59 PM
V/FmReceiverService( 578): seekStation():1
Part of the FM radio driver is also in /system/lib/android_runtime.so.
The upshot:
The FM Radio is heavily tied into the Desire's firmware (and I'll bet the same is true with the Droid Incredible as well); the FM apk itself is tied to Sense, so if the radio can be made to work, at least for the time being, it will be tied to Desire ROMs.
I would die if someone got a radio app working. The local rock station here in baltimore is fantastic and I throughly enjoy listening to them but I dont want to carry another device when I go to the gym or jogging. I'd gladly pay for a pro/donate version too...
So are we going to maybe see this on sense roms. Coming soon???
-------------------------------------
Sent via the XDA Tapatalk App
I have a theory I'd like to try which requires me to successfully boot a custom kernel, but my self-built kernels thus far have failed to boot :-/. If its just a matter of audio path, it should be easy to get this to work (I hope)
It's pity that there is no HTC insider to help us.. That would save so much PITA trying to figure out the HW from looking at the SW...
Anyway, several things:
1) The references are incorrect, should be QSD8250 and BCM4329.
2) I've looked up the Broadcom chip. No detailed pinouts and/or HDD/SWI, but a brief is available - and it says enough:
http://www.datasheetdir.com/BCM4329+download
First, FM radio doesn't have its own dedicated interface, it's encapsulated and passed over either WiFi or BT. Later in the spec it specifies BT interface, so that part is clear.
Second, it's also clear that the data coming from BT chip isn't coming analog - it's coming over high speed UART, the same one that's used to control BT. The same HW, but different usage.
So to capture the audio output of FM radio, one needs to look at the Desire source and find in its BT stack - or more probably outside of the stack - the procedures responsible for configuring high-speed UART, select those that reconfigure it for audio, and duplicate on Nexus. I don't know if any recoding takes place, but it should also be visible in the code. Looks like there can't be any HW problem that can prevent the radio, since HS-UART is already connected and functional in controlling BT, and we know for fact that I2C is connected, since Paul's builds control the radio.
I'd do that myself, but it'll take me ages to navigate in the code, not being familiar with it and not having enough SW background. I hope one of the devs can take the job. As it goes for HW, I can support the part that deals with QSD reconfiguration, if there will be any specific questions that I'll know the answers to.
Jack_R1 said:
It's pity that there is no HTC insider to help us.. That would save so much PITA trying to figure out the HW from looking at the SW...
Anyway, several things:
1) The references are incorrect, should be QSD8250 and BCM4329.
2) I've looked up the Broadcom chip. No detailed pinouts and/or HDD/SWI, but a brief is available - and it says enough:
http://www.datasheetdir.com/BCM4329+download
First, FM radio doesn't have its own dedicated interface, it's encapsulated and passed over either WiFi or BT. Later in the spec it specifies BT interface, so that part is clear.
Second, it's also clear that the data coming from BT chip isn't coming analog - it's coming over high speed UART, the same one that's used to control BT. The same HW, but different usage.
So to capture the audio output of FM radio, one needs to look at the Desire source and find in its BT stack - or more probably outside of the stack - the procedures responsible for configuring high-speed UART, select those that reconfigure it for audio, and duplicate on Nexus. I don't know if any recoding takes place, but it should also be visible in the code. Looks like there can't be any HW problem that can prevent the radio, since HS-UART is already connected and functional in controlling BT, and we know for fact that I2C is connected, since Paul's builds control the radio.
I'd do that myself, but it'll take me ages to navigate in the code, not being familiar with it and not having enough SW background. I hope one of the devs can take the job. As it goes for HW, I can support the part that deals with QSD reconfiguration, if there will be any specific questions that I'll know the answers to.
Click to expand...
Click to collapse
Bah, my brain was on neutral when I typed those numbers. At least this explains why HTC replaced the Bluetooth stack with something they cooked up, but it will be non-trivial to get FM radio into an AOSP. I think I know what has to change in the kernel to make this work though at this point.
Sonic McTails said:
Bah, my brain was on neutral when I typed those numbers. At least this explains why HTC replaced the Bluetooth stack with something they cooked up, but it will be non-trivial to get FM radio into an AOSP. I think I know what has to change in the kernel to make this work though at this point.
Click to expand...
Click to collapse
Go go go! I really want to have it enabled on my N1! Feels like without it, my N1 is lacking some piece of its soul.
Keep up the work guys.
No longer will our FM chips remain flaccid and unused. LOL.
If u need help building kernel or any other I am there to help.
charnsingh_online said:
If u need help building kernel or any other I am there to help.
Click to expand...
Click to collapse
Me two!
why don't we invite the great [ cyanogen ], he who has done some great stuff that hasn't been opened by Google .. I think we must request him and open a bounty for FM radio to get working on nexus one.
thalib_atc said:
why don't we invite the great [ cyanogen ], he who has done some great stuff that hasn't been opened by Google .. I think we must request him and open a bounty for FM radio to get working on nexus one.
Click to expand...
Click to collapse
-----------
great idean infact he might be comin up with some new rom already thats my assumption can be true u never knw
thalib_atc said:
why don't we invite the great [ cyanogen ], he who has done some great stuff that hasn't been opened by Google .. I think we must request him and open a bounty for FM radio to get working on nexus one.
Click to expand...
Click to collapse
I'd def donate to anyone that got the FM radio working..... I know many people would, I'm sure there are people working on it (if they believe its possible that is)..... Sure would be an awesome feature to add and would allow me to get my buddy to shut up about his incredible......
this is a useful dmesg (enabling FM Radio)
Code:
[ 705.437744] Enable FM HEADSET
[ 705.460845] Disable TTY
[ 705.471862] Audio: FM: start
[ 705.471984] q6fm_open()
[ 705.472106] Audio: _audio_rx_clk_enable: device 0x0107ac8a, group 0
[ 705.472320] Audio: _audio_rx_clk_enable: icodec_rx_clk_refcount = 1
[ 705.472595] Audio: _audio_rx_clk_enable: icodec_rx_clk enabled
[ 705.509124] acdb: 974 bytes for device 5, rate 48000.
device is controlled by btld through
/sys/class/htc_accessory/fm & /sys/class/htc_accessory/tty
desire source code:
arch/arm/mach-msm/htc_headset_common.c
arch/arm/mach-msm/qdsp6/audio_ctl.c
drivers/serial/msm_serial_hs_bcm.c
Kali- - it's great info. Thanks.
HTC Desire FM Radio App
Hi
In my case, i have an HTC Desire and i want to develop an application to delay the radio.
This is because in my country many people like to listen to the radio while watching football, but it is usually 2 o 3 second ahead of the image (since DVB)
I've decompilied the HTC Radio application with Dexeter, but it's a little bit complicated to understand (not impossible, but difficult).
For example, this is a piece of code from BroadcomFMTuner:
Code:
.method private setCmdStatus(I)V
.limit registers 5
; this: v3 (Lcom/htc/fm/BroadcomFMTuner;)
; parameter[0] : v4 (I)
.line 25
iget-object-quick v0,v3,[obj+0x8]
new-instance v1,java/lang/StringBuilder
invoke-direct {v1},java/lang/StringBuilder/<init> ; <init>()V
const-string v2,"setCmdStatus("
invoke-virtual-quick {v1,v2},vtable #0x3b
move-result-object v1
invoke-virtual-quick {v1,v4},vtable #0x36
move-result-object v1
const-string v2,")"
invoke-virtual-quick {v1,v2},vtable #0x3b
move-result-object v1
invoke-virtual-quick {v1},vtable #0x7
move-result-object v1
invoke-static {v0,v1},com/htc/fm/FMLog/d ; d(Ljava/lang/String;Ljava/lang/String;)V
There's a better way to decompile the application or is the source code available anywhere?
There's other similar code to access the fm chip or documentation i can look?
Thanks
Sergio
I know you can make it guys! Thanks for your hard work on this!
Grande Kali- ! Let's put some italian flavour on this ...
thalib_atc said:
why don't we invite the great [ cyanogen ], he who has done some great stuff that hasn't been opened by Google .. I think we must request him and open a bounty for FM radio to get working on nexus one.
Click to expand...
Click to collapse
I've poked around with it a bit but haven't really had any success.
CodeAurora has a bunch of code for FM radio- I don't know how much of it is applicable though. Most of it is framework/HAL stuff and geared towards a specific board.
I'll start working on it from tomorrow. Will see where I can get it too. I would need someone who already has worked on it to make stuff faster. Shoot me a pm anyone who has already worked on it
hey charnsingh... any news so far?
Hi,
I was just wondering if anyone with the SGS II has managed to upload their tracks to Google maps? Every time I try it just waits at the authenticating to Google Maps screen without ever uploading anything. If I try on my old SGS it still works fine so it looks like it's just the SGS II that has the problem.
I did read elsewhere that it could be to do with the phone not having the default language set to english, but I have checked the phone and the default language is set to english, so I'm stumped. Any suggestions?
Same problem here
tracks been posted in GPS thread so guess its at your end .
jje
JJEgan said:
tracks been posted in GPS thread so guess its at your end .
jje
Click to expand...
Click to collapse
I think they are being imported rather than uploaded using the sgs2 as that's the only way I can do it, although I could be wrong (and usually am)
Would be good to hear if anyone had successfully uploaded via the phone.
Same issue here.
Tested and tracks stick at 0 in the uploading window . However my SGS 1 did that at times as well ..
jje
Same problem here too. Had to import tracks manually.
Same problem for me. There seems to be a problem with certain apps accessing my google account for authentication.
If I plug my phone into the PC and watch the console in eclipse I can see in the system logs there is some kind of authentication exception that isn't being handled properly when you try to upload a track.
This affects My Tracks, Andlytics and probably anything else that uses your google account in the same way.
Same problem here, seems to be a bug, the SGS still uploads.
Yep, same problem here.
This is the logcat when I press the "Send now" button:
Code:
I/InputReader( 2680): dispatchTouch::touch event's action is 0
I/InputDispatcher( 2680): Delivering touch to current input target: action: 0, channel '40ab6058 com.google.android.maps.mytracks/com.google.android.apps.mytracks.MyTracks (server)'
I/InputReader( 2680): dispatchTouch::touch event's action is 1
I/InputDispatcher( 2680): Delivering touch to current input target: action: 1, channel '40ab6058 com.google.android.maps.mytracks/com.google.android.apps.mytracks.MyTracks (server)'
D/MyTracks(15555): Logging in to local...
E/JavaBinder( 2680): *** Uncaught remote exception! (Exceptions are not yet supported across processes.)
E/JavaBinder( 2680): java.lang.StringIndexOutOfBoundsException
E/JavaBinder( 2680): at java.lang.String.substring(String.java:1651)
E/JavaBinder( 2680): at android.accounts.AccountManagerService.createNoCredentialsPermissionNotification(AccountManagerService.java:944)
E/JavaBinder( 2680): at android.accounts.AccountManagerService.doNotification(AccountManagerService.java:1803)
E/JavaBinder( 2680): at android.accounts.AccountManagerService.access$300(AccountManagerService.java:79)
E/JavaBinder( 2680): at android.accounts.AccountManagerService$2.onResult(AccountManagerService.java:917)
E/JavaBinder( 2680): at android.accounts.AccountManagerService$2.onResult(AccountManagerService.java:899)
E/JavaBinder( 2680): at android.accounts.IAccountAuthenticatorResponse$Stub.onTransact(IAccountAuthenticatorResponse.java:59)
E/JavaBinder( 2680): at android.os.Binder.execTransact(Binder.java:320)
E/JavaBinder( 2680): at com.android.server.SystemServer.init1(Native Method)
E/JavaBinder( 2680): at com.android.server.SystemServer.main(SystemServer.java:807)
E/JavaBinder( 2680): at java.lang.reflect.Method.invokeNative(Native Method)
E/JavaBinder( 2680): at java.lang.reflect.Method.invoke(Method.java:507)
E/JavaBinder( 2680): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:847)
E/JavaBinder( 2680): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:605)
E/JavaBinder( 2680): at dalvik.system.NativeStart.main(Native Method)
It's an unhandled exception in some non-MyTracks code.
Does this work for anyone yet?
Er NO thats why we is still posting it dont work .
jje
To view your tracks you can export them as KMLs, then upload the KML to somewhere online (I use Dropbox), copy the URL for where they are, then go to maps in your browser and paste the URL into the search bar. You can then see your tracks in Google Maps. Clunky, but at least can be done. I'm quite pleased with how the tracks are for me.
KML import to Google Earth works, too. Its a shame they cannot fix the upload, it's the same from WinPc.
ALexander
Reply from Samsung to my enquiry on the problem
06.05.2011 16:35:37
Customer reference number:
Email response ID:
Dear xxxx,
Thank you for contacting Samsung and I have pleasure in providing the
following assistance:
Regarding to your query, kindly be informed that you need to refresh the
software of the phone and that is by removing the SIM card and the
battery out of the phone and wait for 30 seconds and put them back in.
If this did not work, you would try to reset the software and that is by
going to applications>settings>privacy>factory data reset and if it
enquires you for a password it would be 0000.
Before doing reset to the software, please make sure that you will back
up the whole data on the phone as the reset will erase the whole data on
the phone.
If this did not work out , you need to visit our authorized service
center.Please click on the link below to guide you to the nearest
Service Centre that you can go to with the Proof of Purchase, by just
submitting your Post Code, and choosing Mobile Phones from the drop down
box:
http://www.samsung.com/uk/support/location/supportServiceLocation.do?pag
e=SERVICE.LOCATION
If the authorized service center is far away from you , you need to give
us a call in order to send your phone to book for you a service request
to get it repaired .
Please note that when you contact us:
http://www.samsung.com/uk/info/contactus.html
Samsung mobile: 0845 MSAMSUNG (67267864)
Monday - Saturday: 9am - 6pm
Sunday: CLOSED
You will need to provide our representatives with specific details on
the phone like: The Model number of the phone, as well as the Serial
number. This can be found, underneath the Bar Code when you remove the
battery off the back of the phone, and it begins with an “R”. This will
help us determine the warranty term on the phone.
If you require any further assistance, please contact Samsung again and
we will be more than happy to help.
Kind regards,
Heba Khaled
Online Support Team
Samsung Customer Support Centre
Copy and paste response from Samsung, what a crock of sh...
Same problem here. Any ideas of a fix??
Same problem here. Using the GPX or KML file won´t generate the nice resumee-gfx i guess, right?
Discussion on My Tracks development forum:
http://code.google.com/p/mytracks/issues/detail?id=255&q=samsung galaxy s 2&colspec=ID Type Component Status Priority Targeting Work Stars Owner Summary
Anybody else try setting the language to US English?
The only reason i bought the galaxy player was to be able to use the mediahub app to watch all the media that I own. Knowing that only Samsung android devices are capable to use the mediahub app I assumed that the galaxy player would have it. After all it is a galaxy product "high end".
Can someone please help me find a working apk for mediahub?
Thank you!
I read before purchasing that it is capable with an upgrade at a later time via OTA... but out of the box, no...Media Hub is not there.
I could be wrong, but very doubtful its available otherwise.
Good luck!
CJ
Sent from my MZ609 using Tapatalk
waldoelx7241 said:
The only reason i bought the galaxy player was to be able to use the mediahub app to watch all the media that I own. Knowing that only Samsung android devices are capable to use the mediahub app I assumed that the galaxy player would have it. After all it is a galaxy product "high end".
Can someone please help me find a working apk for mediahub?
Thank you!
Click to expand...
Click to collapse
Attached is the media hub app that I pulled from my Epic 4G phone.
Enjoy!!!
Jesse- is this confirmed working in The Galaxy Players?
Thanks for the apk, much appreciated!
cramjammer said:
Jesse- is this confirmed working in The Galaxy Players?
Thanks for the apk, much appreciated!
Click to expand...
Click to collapse
It installed ok, but I got "Unknown error" when tried to run it.
Jim
Yeah, kinda what i was afraid of...I'm gonna give it a try now. See if i can play around with it.
Thanks Jim.
CJ
Sent from my YP-G70 using xda premium
cramjammer said:
Yeah, kinda what i was afraid of...I'm gonna give it a try now. See if i can play around with it.
Thanks Jim.
CJ
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
Hi,
You're welcome.
I didn't see anything in dmesg, but I didn't check that other log thing (I forget what it's called).
If you do get it working, please post back !
Jim
Jim-
Sorry for taking so long to respond...Kids, wife, life-in-general...gets in the way of my Android obsession!
First let me say I know enough to be dangerous, i.e.- ADB, Odin, rooting, flashing, etc. But as for development, reading and writing code, I'm not the guy. I've self-taught and used steps of others to educate myself. I just got done unlocking my Galaxy Nexus and rooting it. Great phone btw.
So, with that being said I haven't got too far with this. I used the apk from Jesse and it installed, but like you i got the same error msg. I went into Root Explorer and changed the permissions with still no luck. I used the Media Hub from my Vzw Galaxy Tab 10.1 too, (I figured why not...?) no luck either.
i'm not opposed to trying different ideas using my Galaxy Player for the greater good.
sorry, I know this didn't help much but I didn't want to leave you hangin.
CJ
cramjammer said:
Jim-
Sorry for taking so long to respond...Kids, wife, life-in-general...gets in the way of my Android obsession!
First let me say I know enough to be dangerous, i.e.- ADB, Odin, rooting, flashing, etc. But as for development, reading and writing code, I'm not the guy. I've self-taught and used steps of others to educate myself. I just got done unlocking my Galaxy Nexus and rooting it. Great phone btw.
So, with that being said I haven't got too far with this. I used the apk from Jesse and it installed, but like you i got the same error msg. I went into Root Explorer and changed the permissions with still no luck. I used the Media Hub from my Vzw Galaxy Tab 10.1 too, (I figured why not...?) no luck either.
i'm not opposed to trying different ideas using my Galaxy Player for the greater good.
sorry, I know this didn't help much but I didn't want to leave you hangin.
CJ
Click to expand...
Click to collapse
Hi,
Did you get the same error I got when you tried media hub from your Galaxy Tab ("unknown error")?
If so, it's hard to tell what's going on.
I know that awhile ago, I tried bringing over some APKs from my SGP5 to my Gtablet (the opposite of this thread), and some worked ok, and some failed for various reasons, including one (Artillery Defense) that gave a more specific license error. I think another one (Heavy Gunner 3D) just dies.
The log thing I mentioned is logcat. There're some apps on market that allow you to see logcat, which is I think more of a app-type logging (vs. dmesg, which is more system logging). Maybe try install one of these apps (aLogcat, I think is one of them), then try launching media hub, then look at the logcat, to see if there's anything apparent there.
Other than that, "unknown error" isn't very helpful, so not sure what to do if logcat doesn't show anything helpful.
Jim
Jim...I'll give this a run tonight or at work tomorrow morninh and see what the logcat shows. Maybe we can work through this one with a bit of luck.
Sent from my MZ609 using Tapatalk
ya i tried a few different apk's and all had the same error message. also my 5.0 kept messing up so I swapped it for a 4.0, I like it better actually.
Hi,
I finally had time to test and run logcat. This is the snippet from when I clicked Retry, then got the popup again:
Code:
I/PowerManagerService( 120): Ulight 3->7|0
D/LightsService( 120): BUTTON : 68
I/InputReader( 120): dispatchTouch::touch event's action is 1
I/InputDispatcher( 120): Delivering touch to current input target: action: 1, channel '409ad608 com.sdgtl.mediahub.spr/com.sdgtl.mediahub.spr.Main (server)'
D/VolumeCustomizer( 77): [VOL] getVolumetableIndex XAA
D/VolumeCustomizer( 77): [VOL] getVolumetableIndex mSelectindex 0, count[19]
D/AudioHardwareALSA( 77): Calling setDevice from write @..2348.
I/AudioHardwareALSA( 77): Initialized ALSA PLAYBACK device AndroidPlayback_Speaker_normal
D/AudioHardwareALSA( 77): Using 2 channels for PLAYBACK.
I/AudioHardwareALSA( 77): DEFAULT_SAMPLE_RATE is 44100, mDefaults->sampleRate is 44100
D/AudioHardwareALSA( 77): Set PLAYBACK sample rate to 44100 HZ
D/AudioHardwareALSA( 77): Buffer size: 4096
D/AudioHardwareALSA( 77): Latency: 92879
D/DataRouter( 75): fd is 21 Content read is PDA USB
D/DataRouter( 75): length is 8
W/AudioFlinger( 77): write blocked for 120 msecs, 796 delayed writes, thread 0x75bd8
W/PowerManagerService( 120): Timer 0x7->0x3|0x0
I/PowerManagerService( 120): Ulight 7->3|0
D/DataRouter( 75): fd is 21 Content read is PDA USB
D/DataRouter( 75): length is 8
D/LightsService( 120): BUTTON : 0
D/AudioHardwareALSA( 77): Inside AudioStreamOutALSA::standby
I/AudioHardwareALSA( 77): Output standby called!!. Turn off PCM device.
D/DataRouter( 75): fd is 21 Content read is PDA USB
D/DataRouter( 75): length is 8
D/DataRouter( 75): fd is 21 Content read is PDA USB
D/DataRouter( 75): length is 8
D/DataRouter( 75): fd is 21 Content read is PDA USB
D/DataRouter( 75): length is 8
D/DataRouter( 75): fd is 21 Content read is PDA USB
D/DataRouter( 75): length is 8
I'm not sure exactly what's going on, but it looks like it's trying to initialize audio, so it may be that the APK (from the 1st couple of posts) is not compatible hardware-wise with the SGP5 (US).
Jim
jimcpl said:
It installed ok, but I got "Unknown error" when tried to run it.
Jim
Click to expand...
Click to collapse
I did not test it, but like you when I installed it on my SGP I aldo got the unknown error.
Hey Guys,
I have an app that can read information from a Mifare Desfire EV1 card (That I don't have the key for). Now I believe that the master key is loaded into memory at some point in order to decrypt the information on the card.
Could someone point me in the right direction?
I can attach IDA to the application however there are heaps of different calls, I can't really see a call where the key is being passed to it. Does anyone know of the Android Mifare Decrypted call?
Perhaps the key is passed to the driver then its decrypted?
TL;DR
Can you extract Desfire EV1 Keys from a compiled app that I can successfully read a card? (Hopefully the key exchange isn't done in TZ!)
Cheers guys!
Hey Guys,
Little update.
I've attached strace to com.android.nfc
This app looks to be Android's NFC daemon is its in its own group 'nfc'
And it looks to be reading and writing (via read() and write() syscalls) all sorts of interesting data to /dev/pn544
pn544 also belongs to the NFC group:
crw------- 1 nfc nfc 10, 58 1970-10-24 02:53 /dev/pn544
I don't know though, this doesn't seem to be low enough, I guess I'd be seeing information going from the app to the lower NFC chip vice-versa.
This looks like it COULD be the right step, because the app would need to send the key to the NFC chip in order to decrypt it.
I'll keep you guys posted.
So I've read the tag with the app that can successfully read the tag, and an app that has no knowledge of the card (Incorrect key) so I could check the write()'s side by side and check.
From what I can see the following are init traffic:
[pid 2967] write(34, "\0\0\5\220`\0\0\0", 8 <unfinished ...>
[pid 2967] write(34, "!\6\1\1", 4 <unfinished ...>
[pid 2967] write(34, "!\4\3\1\4\2", 6 <unfinished ...>
[pid 2967] write(34, "\0\0\r\0\244\4\0\7\322v\0\0\205\1\1\0", 16 <unfinished ...>
[pid 2967] write(34, "\0\0\f\0\244\4\0\7\322v\0\0\205\1\0", 15 <unfinished ...>
[pid 2967] write(34, "\0\0\7\0\244\0\0\2\341\3", 10 <unfinished ...>
[pid 2967] write(34, "!\6\1\1", 4 <unfinished ...>
Click to expand...
Click to collapse
As both transactions send this same data to the driver.
Everything starts to change around:
[pid 2967] write(34, "\0\0\t\220Z\0\0\0031ES\0", 12 <unfinished ...>
Click to expand...
Click to collapse
As you can see the above data has the word "ES" in it, I also know this card is using AES, perhaps the ES is saying hey, use AES Encryption.
Also from what I've read, I think all of the data above is NCI data, its the NFC spec, I think HCI was used previously.
Hey Guys,
Another quick update, turns out /dev/pn54 is TOO DAMN LOW!
The encryption/decryption is actually handled in the Android App itself.
However, low level NFC spoofing to android applications (Invoking read() on pn544 from com.android.nfc) may work.
Hey! Have you had any luck extracting or cracking the key of a mifare desfire ev1?
This is the most recent information I could find about this topic with some sort of investigation
est_cap said:
Hey! Have you had any luck extracting or cracking the key of a mifare desfire ev1?
This is the most recent information I could find about this topic with some sort of investigation
Click to expand...
Click to collapse
Hey,
The research I was conducting was on a Public Transport card, they used a free-read block, meaning anyone can read the block, however to write you'd require a key.
If your app in question is writing to the card, open the app up in a debugger/dissembler trace the write function and you'll see the key sitting there
Hope this helps!
Question
Has anyone thought authenticate and send a key after another with brute force until the key is decrypted ? you could run a test key authentication for writing, does not seem too long without so many possibilities and the connection takes less than a second , it would be good to do it from taking advantage of Android NFC , indeed reader already is an application that is Mifare DESFire used to read EV1 in PlayStore .
Anden33 said:
Has anyone thought authenticate and send a key after another with brute force until the key is decrypted ? you could run a test key authentication for writing, does not seem too long without so many possibilities and the connection takes less than a second , it would be good to do it from taking advantage of Android NFC , indeed reader already is an application that is Mifare DESFire used to read EV1 in PlayStore .
Click to expand...
Click to collapse
Hi Anden33,
I was actually thinking of the same approach, bruteforcing the key, but does the key version also have to be correct? That might add to the complexity if so. I'm using the MIFARE DESFire EV1 tool on my androind and the key version is exposed for each key so i'm guessing if I should use the same key version while bruteforcing the key
7d5 said:
Hi Anden33,
I was actually thinking of the same approach, bruteforcing the key, but does the key version also have to be correct? That might add to the complexity if so. I'm using the MIFARE DESFire EV1 tool on my androind and the key version is exposed for each key so i'm guessing if I should use the same key version while bruteforcing the key
Click to expand...
Click to collapse
It was my understanding Mifare would have some protections aginst this sort of attack, if the Proxmark guys couldn't figure it out yet, I doubt this would work
For reference: http://www.proxmark.org/forum/viewforum.php?id=31
(dylanger) said:
It was my understanding Mifare would have some protections aginst this sort of attack, if the Proxmark guys couldn't figure it out yet, I doubt this would work
For reference: http://www.proxmark.org/forum/viewforum.php?id=31
Click to expand...
Click to collapse
I did the cryptanalysis, and its impossible ( at least during my lifetime ). I'm looking at other ways now, will let you know.
7d5 said:
I did the cryptanalysis, and its impossible ( at least during my lifetime ). I'm looking at other ways now, will let you know.
Click to expand...
Click to collapse
Hello, I was trying to find a way to emulate my school issued ISIC card. Have you had any success in this?
Thanks
Hello,
when we are expecting english version of yota 3 and a worldwide release.
If not when the mod OS with english version will be available.
Does yota 3 have google play store?
Does yota 3 can mirror front screen to back screen like yotaphone 2.
How it can import to india?
I bought of Yotaphone 3 from CECT Shop in GB so I could share some of my new gained experiences.
CECT Shop offers CN version, with Android Nougat 7.1.1, China and English language, build in 64GB storage, without Google Services and tons of CN apps.
Implementation of Google on Yota3:
Absence of Google isn't real problem. You could without and dificulties download 4 needed APK's from "external" APK repositories like APKMirror. You need to install 4 apps in exact order: Google Framework (look for 7.1.1 version), Google Play Services, Google Account Manager (look for 7.1.1 version too) and Google PlayStore (you should use NODPI versions) . It's important not to run any of apps until full install procedure. After install you should reboot your phone to allow adding new Google account.
About Android and Yota optimization mechanisms:
For start lets agree that Android 7.1.1 itself have in opinion of many users some real "issues" witch optimization procedures and DOZE. Google assumed that running some sort of apps in background isn't much high priority for system, memory and battery drain (not 100% true). You may be shocked, but one of these apps is for example Gmail, bunch of similar apps using push communications/notifications, and lots of more useful software. On top of it is fact that on Yota3 is large number of, lets say, "hard coded" CN system apps. Apps that (it's my opinion based on my observations) partly trying to replace original Android 7.1.1 functionalities, like mentioned before battery optimization and permissions management. In result original Android possibility of disabling some of these mechanisms just doesn't work (excluding apps form optimization works for at most until the phone restart). When you connect need of constant excluding apps from optimization, and fact that even those smallest like Clock need to do that for proper work, then you realize that it's real pain in the @$$. But there almost always some way... For consolation, if you reduce amount of apps that must run in background (I have about 15 of all of my 70-80 apps set so) you could live with that and have a chance for nice and fully functional phone.
Other disadvantages:
1. Low functionality of back E-Ink screen. Most of apps able to run on it is CN apps like: CN eReaders, CN news and weather apps, CN music player, etc. For now (I hope temporary) there is no possibility to mirror/transfer view of front screen to back screen.
2. Notification from regular not CN apps doesn't display either on front lock screen and back E-Ink screen.
3. On one hand fingers you can count apps designed and working on back E-Ink screen available in PlayStore.
4. For now there is no possibility of root implementation.
5. For now there is no custom ROM available for Y3.
6. Y3 doesn't have NFC for contactless payments.
7. Y3 doesn't have backlight for E-Ink display.
Benefits:
1. It's great phone with nice big Super AMOLED screen.
2. It have dual SIM slot and 4GB RAM.
3. Y3 is super thin for phone with 2 screens. You look at it and wonder where they have put and fit 3300mAh battery in it?
4. Running time on 3300mAh is pretty good.
5. Nice 3A charger.
6. Rubber-like cover case.
That's for now...
I also got my Y3 from cect-shop, and added an original wallet-style Yota case from joybuy.
The system still shows some UI elements in Chinese even with Android language being set to English - lock screen, for example.
There is no such thing like the YotaHub on the previous YotaPhone. Instead, there is a "discover" screen on the E-Ink screen whichs allows to install some CN apps adapted for the E-Ink screen. Mostly news, WeChat, and some CN eBook apps.
A Chinese version of Kindle app was preinstalled and can run on the E-Ink screen. International Amazon accounts do not work on amazon.cn, so I was stuck.
I downloaded & installed Amazon appstore, downloaded & installed the latest (non-CN) regular Kindle app - and surprise! Suddenly that second Kindle app was also available on the E-Ink screen. As this was a stock app, I assume that Yota's modifications on Android determine which app may use the E-Ink screen, and not the app itself.
In addition, I found that Yota's "gallery" app allows to use any gallery picture as lock screen or as shakeout screen for the E-Ink panel. So for now, my use cases are:
- reading Amazon kindle eBooks on E-Ink screen
- take screenshot of flight boarding pass & send it to E-Ink display to have your boarding pass always ready no matter whether you are using your phone otherwise..
Thanks for that tips. I wasn't aware about Gallery and NonCN Kindle app.
For the Y3 user that don't know it... These is a dialer secret code to manage mirror function on Yota3 phone, but it's more like kind of developer test function.
You can enable it, but then the front screen it totally turned off and you could use back screen only. If you want to turn it back on to original setting, you have to repeat procedure and turn mirroring off.
Code: *#*#9738#*#*
Enable/disable function: Dialer --> <code> --> "Mirror test" --> "Start/Stop Mirroring"
The glass on my Y2 broke so I decided to try out Y3 - not impressed at all I must admit So much things that made Y2 the best phone ever are gone, let alone it being chinese only. The widgets on the back are gone, like, why?! Missed calls+sms+emails+notifications counter and battery indicator, plus better weather, no reason for those not to be there ffs, it breaks my heart :|
Also it feels like they threw out their designer, the Y2 was a beauty to look at from behind, back quite seamlessly transitioning into the EPD. I have no idea why Y2 is not the same in this manner. If you can't make the EPD fully black but only dark grey, at least make the plastic around matching gray. All uniformity gone. Also the 3 buttons (= o <) are kinda pointless imo, but at least, again, make it look like a part of a whole Now it's just a squarish brick like anything else, with the back screen not feeling like part of the design but something that was just slapped on. And the functionality (ultra limited) the same story. I don't really need the integrated mirror functionality (though it would be nice from time to time, but just a minor bonus for me). But it should really go all in on presenting you valuable information - clock, weather, notifications, news, but it totally fails there. Theres a 'step counter' though that I cant even get rid of, like, WHY :'(
Issues I hope could be addressable, not sure, please let me know if you know solutions to some of it:
- I cannot use a custom launcher? The default one is, I dont know, basic, nothing that wrong with it, but isn't there a way to switch to Apex for example? I failed to find a way to set a different one
- EPD - "MOBEST", can I for the love of god get rid of that screen?
- same story with "DISCOVER" honestly... but then I don't know how I would access 'panels setup', since it does not seem to be editable from something on the main screen (yotahub etc)
- and last, and thats a very shocking and very big one - is none of the ebook readers capable of presenting the ebooks in landscape mode? I mean, holy hell, I know it's all in chinese, but I really tried clicking/toggling everything, in kindle, ireader, qqbook, jingDongReader, even that stupid mobest, and I just have no f*cking clue how to read my epub/mobi/... in landscape! I mean, it just feels impossible that such a thing would not be implemented in any of those things. I guess all are just presentation of their 'regular' non-epd versions, and rely on device orientation, but that is locked on the EPD. I-need-to-be-able-to-read-in-landscape, I'm really getting desperate here after navigating through all the chinese menus (╯°□°)╯︵ ┻━┻
With the price this thing cost me to buy+import I could have had S9 actually, which is a gem, but with my Y2 I got addicted to being able to see the clocks and weather forecast and emails+notifications without touching the phone. And sure, I liked to read some stuff on it from time to time as well. All I got with the Y3 is the clock. And it is not even good as an e-book reader since its all portrait only
Oh and one more thing - even the clock f*cking lags behind, so I can't really realy on it!!
Please help me with at least some of the issues, there must be a way to make it "good enough", but as is it is unbearable
I am looking forward to an major update that will fix most of the errors discussed here...
I'm still hoping that there will be an US/EU version with better functionality.
How is possible than an old version had more functionality than the old one!?!?!?!!?
Enviado desde mi HTC One E9PLUS dual sim mediante Tapatalk
Recently bought Yota3 from taobao and trying on different things.
First of all, no Google Play, which is a bit sad. I adb installed the Google apks like the 1st thread said, but Gmail not usable and Contact not synced. I recently found a code from Chinese forum to get into debug/dev page. The code is *#*#900#*#*.
I tried to root with Dirtyc0w (yes a bit old compared to Aug2017) and Kingroot but none of them gives me root.
I will keep on updating when I found more useful stuff.
**UPDATE**:
22/3/2017
So, I made the contact works perfectly now. You need to install this:
Google Contacts Sync: google-contacts-sync-7-1-1-release (Get it in apkmirror)
You need the correct version of Google Play Services to fix the Play Services issue. Check the long number in the version and get the latest. Android 6.0+ one should be fine.
GMail works, make sure you download the Google Play Services with arm64+arm Android 6.0+ version.
I am not getting notifications like for example from twitter app, I guess thats some of the android optimizations getting in the way preventing the apps from running/checking for notifs, but can I somewhere turn the optimizations permanently off? For specified apps at least... Pushbullet is not working for me in this regard at all and thats a really convinient app if it works (showing phones notifications on pc)
How to switch off preview of text messages on e-ink screen?
I think I've almost disabled all possible notifications. However, I still didn't manage to stop the e=ink to show messages. Could you help me which option(s) is it? I am loosing my marbles here.
Found it! It was in settings of the eink - not on AMOLED display. Hope, I have saved someone a search... It would be nice if we could manage behaviors from any side...
Hi
I can't make Viber to display any notifications... Did anyone manage to enable a non-chinese messaging app, to display notifications on either main screen or (better) on the e-ink screen?
Regards,
M
Google Play doesn't work
Hej,
Can someone please post the exact download links to the 4 apks you need for google to work. I try multiple and they all didn't work. I'm so frustrated. Can someone please help me?
Benjamin98 said:
Hej,
Can someone please post the exact download links to the 4 apks you need for google to work. I try multiple and they all didn't work. I'm so frustrated. Can someone please help me?
Click to expand...
Click to collapse
Hello,
i am not allowed to post a link. Just google for:
yota 3 play store geeks r us
It is in German. It worked for me.
Google Play eventually stops working
I've encountered this twice already.
At some point Google Play Store and the internal Package Installer cease to work. I couldn't reproduce the exact sequence but it happened even after Factory Reset after some time again.
Code:
04-19 11:44:48.253 12317 12376 V SQLiteTime: /data/user/0/com.android.vending/databases/library.db: "SELECT account, library_id, backend, doc_id, doc_type, offer_type, document_hash, subs_valid_until_time, app_certificate_hash, app_refund_pre_delivery_endtime_ms, app_refund_post_delivery_window_ms, subs_auto_renewing, subs_initiation_time, subs_trial_until_time, inapp_purchase_data, inapp_signature, preordered, owned_via_license, shared_by_me, sharer_gaia_id, shareability, purchase_time FROM ownership" took 1.000 ms
04-19 11:44:48.253 12317 12376 D SQLiteCursor: received count(*) from native_fill_window: 0
04-19 11:44:48.254 12317 12376 I Finsky : [155] com.google.android.finsky.cg.a.f.j(100): Finished loading 1 libraries.
04-19 11:44:48.262 12317 12377 E AndroidRuntime: FATAL EXCEPTION: PackageInstallerImpl
04-19 11:44:48.262 12317 12377 E AndroidRuntime: Process: com.android.vending, PID: 12317
04-19 11:44:48.262 12317 12377 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.app.AppOpsManager.checkPackage(int, java.lang.String)' on a null object reference
04-19 11:44:48.262 12317 12377 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1690)
04-19 11:44:48.262 12317 12377 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1637)
04-19 11:44:48.262 12317 12377 E AndroidRuntime: at android.content.pm.IPackageInstaller$Stub$Proxy.getMySessions(IPackageInstaller.java:385)
04-19 11:44:48.262 12317 12377 E AndroidRuntime: at android.content.pm.PackageInstaller.getMySessions(PackageInstaller.java:406)
04-19 11:44:48.262 12317 12377 E AndroidRuntime: at com.google.android.finsky.cv.f.run(SourceFile:4)
04-19 11:44:48.262 12317 12377 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:751)
04-19 11:44:48.262 12317 12377 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:95)
04-19 11:44:48.262 12317 12377 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
04-19 11:44:48.262 12317 12377 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:61)
---------- Post added at 09:52 AM ---------- Previous post was at 09:47 AM ----------
Not sure what causes that. Package manager crash log is below.
Code:
04-19 11:50:30.242 12686 12686 W InstallAppProgress: Replacing package:com.android.vending
04-19 11:50:30.253 12686 12686 E linker : Failed open_library for realpath:
04-19 11:50:30.256 12686 12721 E AndroidRuntime: FATAL EXCEPTION: InstallThread
04-19 11:50:30.256 12686 12721 E AndroidRuntime: Process: com.android.packageinstaller, PID: 12686
04-19 11:50:30.256 12686 12721 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.app.AppOpsManager.checkPackage(int, java.lang.String)' on a null object reference
04-19 11:50:30.256 12686 12721 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1690)
04-19 11:50:30.256 12686 12721 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1637)
04-19 11:50:30.256 12686 12721 E AndroidRuntime: at android.content.pm.IPackageInstaller$Stub$Proxy.createSession(IPackageInstaller.java:249)
04-19 11:50:30.256 12686 12721 E AndroidRuntime: at android.content.pm.PackageInstaller.createSession(PackageInstaller.java:297)
04-19 11:50:30.256 12686 12721 E AndroidRuntime: at com.android.packageinstaller.InstallAppProgress.doPackageStage(InstallAppProgress.java:342)
04-19 11:50:30.256 12686 12721 E AndroidRuntime: at com.android.packageinstaller.InstallAppProgress.-wrap2(InstallAppProgress.java)
04-19 11:50:30.256 12686 12721 E AndroidRuntime: at com.android.packageinstaller.InstallAppProgress$6.run(InstallAppProgress.java:483)
04-19 11:50:30.256 12686 12721 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:751)
04-19 11:50:30.256 12686 12721 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:95)
04-19 11:50:30.256 12686 12721 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
04-19 11:50:30.256 12686 12721 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:61)
I think even the Hisense A2 Pro (with NFC!) is better than the Yota3: https://www.banggood.com/Hisense-A2-Pro-Dual-Screen-4GB-RAM-64GB-ROM-Snapdragon-625-Octa-core-4G-Smartphone-p-1221864.html
Is there any way to contact the people from Yotaphone?
My e-book died, my mobile phone is dying and this is taking a way too long.
Enviado desde mi HTC One E9PLUS dual sim mediante Tapatalk
Yota 3 playstore no work
Hi dear people. I buy yota 3. I install apps but playstore stop working, i reset, they stop working again, i reset again and get every app.
There is one possible workaraound i discovered. You download all apps you need and then you update apps threw chinese google play(when google play english stops working)
However you cannot get new apps to the screen but if you download new apps threw chinese google play they must be reached threw that app. But updates are possible of existing apps you got from english google play.
TO YOTA: Please yota fix so i can mirror front to backscreen. Allso fix english google play working. Before this is fixed i cannot recomend phone.
Dear every1 thank you for reading.
//john
Just received an answer from Yota.
There's no news, no official release date in EU and not even an official confirmation of a better version for EU.
As my old smartphone is giving symptoms of old age I leave the Yotaphone 3 for EU as a lost cause and look for another phone.
If anyone knows something different, please, say something and I will consider waiting for Yotaphone 3.
Regards.
Enviado desde mi HTC One E9PLUS dual sim mediante Tapatalk
Gmail
windhamwong said:
Recently bought Yota3 from taobao and trying on different things.
First of all, no Google Play, which is a bit sad. I adb installed the Google apks like the 1st thread said, but Gmail not usable and Contact not synced. I recently found a code from Chinese forum to get into debug/dev page. The code is *#*#900#*#*.
I tried to root with Dirtyc0w (yes a bit old compared to Aug2017) and Kingroot but none of them gives me root.
I will keep on updating when I found more useful stuff.
**UPDATE**:
22/3/2017
So, I made the contact works perfectly now. You need to install this:
Google Contacts Sync: google-contacts-sync-7-1-1-release (Get it in apkmirror)
You need the correct version of Google Play Services to fix the Play Services issue. Check the long number in the version and get the latest. Android 6.0+ one should be fine.
GMail works, make sure you download the Google Play Services with arm64+arm Android 6.0+ version.
Click to expand...
Click to collapse
I just got my Yota 3 and was, like others here, a little disappointed with the lack of mirror functionality - which is the main reason why I wanted it. Also, the lack of google play functions.. Why they restricting this? MY Elephone and Honor 8 were Chinese too but seemed more user-friendly.
I followed steps on here with the four or so APK packages to get Gmail up and running. It didn't work. When I clicked on the app it said "Getting your messages" for a many minutes before saying something like I needed Google Service which is not supported by this device.
Anyway, I discovered the email app in "Discover" on the E-ink side and Gmail loaded. After I got all my emails loaded I flipped over to the other screen and it was working there fine... until I installed the latest update. Now it doesn't work on colour screen but still works, refreshes to new emails on the e-ink side. WTF?
I kind of suspicious of Google and Facebook anyway so am not that bummed that it is difficult to get these apps to work on this phone- as I am wanting to not use them anymore but would be better to have that option open for people who do want to use whatever on this phone.
I also tried the mirror download - with app MORE shortcuts - it did mirror the screen but all it mirrored was a frozen notice saying "Mirroring" or such.
Looking forward to getting more hacks/tips on here to make this phone more customised.
Thanks.
---------- Post added at 08:44 AM ---------- Previous post was at 08:37 AM ----------
Grubbanax said:
I just got my Yota 3 and was, like others here, a little disappointed with the lack of mirror functionality - which is the main reason why I wanted it. Also, the lack of google play functions.. Why they restricting this? MY Elephone and Honor 8 were Chinese too but seemed more user-friendly.
I followed steps on here with the four or so APK packages to get Gmail up and running. It didn't work. When I clicked on the app it said "Getting your messages" for a many minutes before saying something like I needed Google Service which is not supported by this device.
Anyway, I discovered the email app in "Discover" on the E-ink side and Gmail loaded. After I got all my emails loaded I flipped over to the other screen and it was working there fine... until I installed the latest update. Now it doesn't work on colour screen but still works, refreshes to new emails on the e-ink side. WTF?
I kind of suspicious of Google and Facebook anyway so am not that bummed that it is difficult to get these apps to work on this phone- as I am wanting to not use them anymore but would be better to have that option open for people who do want to use whatever on this phone.
I also tried the mirror download - with app MORE shortcuts - it did mirror the screen but all it mirrored was a frozen notice saying "Mirroring" or such.
Looking forward to getting more hacks/tips on here to make this phone more customised.
Thanks.
Click to expand...
Click to collapse
I just installed another update and my Gmail account now loads fine in the Chinese pre-installed "Email" app folder. It had a red number for my new emails. The gmail app i downloaded still doesn't work though.
I would also like to rid my phone of these Chinese apps and other stuff in Chinese. Anyone know how to Anglicise it? I'm downloading updates that are written in Chinese and I have no idea what I am downloading.