José Bernardo

Members
  • Content count

    13
  • Joined

  • Last visited

Community Reputation

4 Neutral

About José Bernardo

  • Rank
    Newbie

Previous Fields

  • Your Current Device(s)
    Nexus One
  1. Samsung Galaxy S4 Review

    And here I was hoping for a fair, balanced review. Yes, I have a few issues with this review/HTC One comparison. First, the camera - there has been at least one decent camera comparison (http://connect.dpreview.com/post/9219904986/shootout-samsunggalaxys4-vs-htcone-vs-iphone5-vs-lumia920), and the S4 beats the HTC One and Lumia gimmicks fair and square. The only place where the S4 isn't the best is on flash photo, where the Lumai wins with a slightly better performance. Second, the performance and the claimed lag. I have exactly the same model reviewed here, with exactly the same firmware version. Between included and installed apps, I have 301 apps on my S4. Yet, I have to see that claimed lag in the month and half I've owned it. It responds immediately, it is extremely fast, it delivers top performance. Sorry, but my anecdote disproves yours. Keyboard - the keyboard incorporates a lot of the technology developed by SwiftKey, one of the best replacement keyboards out there. The only reason I kept using SwiftKey and not Samsung's keyboard is that SwiftKey does a better job of supporting three languages at the same time. Apart from that, the included keyboard is actually quite nice and responsive, better than most alternatives in the play store. The screen - well, you pulled the authority card here - "if you have never used other top end phone screens, you will love the S4's screen" - so I won't try to disprove such an expert. But the screen was enough to get a colleague to switch from the iPhone 5, and the comparisons I did at the shop with the HTC One's screen convinced me that for my eyes the S4 screen is way better. The exchange client - I've had huge battery drain for a couple of days due to the exchange client when the guys at work messed up intellisync. After they changed something in the configurations the battery usage went back to minimal, without any change in my part, so you might have seen an issue due to the exchange server configuration. Battery, since we're talking about it, it is really interesting that for the One a small google search for "HTC One battery issues" brings so many hits. Apparently it is now better - but still, the battery life is inferior to the S4, and the S4, as you note, has a removable battery. Expansion - and you conveniently forget the main issue that for me made the decision to buy the S4 instead of the HTC One - the lack of a uSD slot and the non removable battery on the HTC. That might not mean much for people used to have always excellent, fast, cheap and uncapped connections, but in the real world, with patchy 3G coverage, and expensive data caps, the cloud just won't cut it. A uSD slot is essential, and a removable battery is also near essential if you're "on the road" frequently. A 2 days battery life might be exhausted in 5 hours of gaming on the plane, and a second battery is a necessity there. I hope this wasn't too long... :)
  2. I am having the same problem, and found out it is because /system/bin/fsck.exfat segfaults. Here are the relevant parts of logcat: D/MemorySettings( 7159): Storage : Montar cartão SD D/MountService( 2127): :::: mountVolume :: path = /mnt/extSdCard from pid = 7159 D/MountService( 2127): doMountVolume :: Mouting path = /mnt/extSdCard with = mounting D/MountService( 2127): externalstorage_lock_state = D/VoldCmdListener( 4249): volume mount /mnt/extSdCard I/Vold ( 4249): /dev/block/vold/179:17 being considered for volume sdcard D/Vold ( 4249): Volume sdcard state changing 1 (Idle-Unmounted) -> 3 (Checking) I/MountService( 2127): onEvent:: raw= 605 Volume sdcard /mnt/extSdCard state changed from 1 (Idle-Unmounted) to 3 (Checking) cooked = 605 Volume sdcard /mnt/extSdCard state changed from 1 (Idle-Unmounted) to 3 (Checking) I/MountService( 2127): updating volume state checking D/MountService( 2127): updatePublicVolumeState :: path = /mnt/extSdCard, state = checking D/MountService( 2127): volume state changed for /mnt/extSdCard (unmounted -> checking) D/Vold ( 4249): Detected exFAT file system. I/MountService( 2127): notifyVolumeStateChanged:: path = /mnt/extSdCard,old = unmounted,new = checking D/MountService( 2127): sendStorageIntent Intent { act=android.intent.action.MEDIA_CHECKING dat=file:///mnt/extSdCard (has extras) } D/MtpService( 2366): onStorageStateChanged /mnt/extSdCard unmounted -> checking I/StorageNotification( 2251): Media {/mnt/extSdCard} state changed from {unmounted} -> {checking} D/STATUSBAR-NotificationService( 2127): cancelNotification - pkg:XXX.XXXXXXX.XXXXXXXX, id:1628873367, tag:null D/STATUSBAR-NotificationService( 2127): updateLightsLocked() : Turn off notification light D/KeyguardViewMediator( 2127): setHidden false D/ApplicationPolicy( 2127): isStatusBarNotificationAllowed: packageName = com.android.systemui D/ApplicationPolicy( 2127): isStatusBarNotificationAllowed: packageName = com.android.systemui D/StorageNotification( 2251): setMediaStorageNotification : notify id = 1628873367, path = /mnt/extSdCard, title = A preparar cartão SD... D/STATUSBAR-NotificationService( 2127): enqueueNotificationInternal - pkg:XXX.XXXXXXX.XXXXXXXX, id:1628873367, tag:null D/STATUSBAR-NotificationService( 2127): Noti Alert - mSystemReady:true, AlertEnabled:true D/STATUSBAR-NotificationService( 2127): enqueueNotificationInternal - pkg:XXX.XXXXXXX.XXXXXXXX, id:17301675, tag:null E/NotificationService( 2127): Ignoring notification with icon==0: Notification(contentView=null vibrate=null,sound=null,defaults=0x0,flags=0x8) D/STATUSBAR-NotificationService( 2127): Noti Alert - mSystemReady:true, AlertEnabled:true I//system/bin/fsck.exfat( 4249): fsck.exfat 1.1.0 D/KeyguardViewMediator( 2127): setHidden false D/KeyguardViewMediator( 2127): setHidden false D/KeyguardViewMediator( 2127): setHidden false W/PowerManagerService( 2127): Timer 0x7->0x3|0x0 I/PowerManagerService( 2127): Ulight 0x7->0x3|0x0 D/lights ( 2127): button : 2 + D/lights ( 2127): button : 2 - D/PowerManagerService( 2127): setLightBrightness : mButtonLight : 0 D/PowerManagerService( 2127): setTimeoutLocked::SmartSleep : after19500 D/STATUSBAR-NotificationService( 2127): enqueueNotificationInternal - pkg:XXX.XXX.XXXXXXXX.XXXX, id:2, tag:null D/STATUSBAR-NotificationService( 2127): Noti Alert - mSystemReady:true, AlertEnabled:true D/KeyguardViewMediator( 2127): setHidden false D/KeyguardViewMediator( 2127): setHidden false F/libc ( 8945): Fatal signal 11 (SIGSEGV) at 0x00000008 (code=1) I/DEBUG ( 1901): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** I/DEBUG ( 1901): Build fingerprint: 'samsung/m0xx/m0:4.0.4/IMM76D/I9300XXBLG8:user/release-keys' I/DEBUG ( 1901): pid: 8945, tid: 8945 >>> /system/bin/fsck.exfat <<< I/DEBUG ( 1901): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000008 I/DEBUG ( 1901): r0 400aa1b8 r1 00000000 r2 00000000 r3 400a7460 I/DEBUG ( 1901): r4 400aa1b8 r5 400901ec r6 400a96a0 r7 00000000 I/DEBUG ( 1901): r8 014d98d0 r9 00000008 10 ffffffd0 fp 00000001 I/DEBUG ( 1901): ip 014d18d0 sp be94b878 lr ffffffd4 pc 4008c9a6 cpsr 40000030 I/DEBUG ( 1901): d0 3d184240309b4df7 d1 0000000000000000 I/DEBUG ( 1901): d2 0000000000000000 d3 0000000000000000 I/DEBUG ( 1901): d4 0000000000000000 d5 0000000000000000 I/DEBUG ( 1901): d6 0000000000000000 d7 3d24b3bc00000000 I/DEBUG ( 1901): d8 0000000000000000 d9 0000000000000000 I/DEBUG ( 1901): d10 0000000000000000 d11 0000000000000000 I/DEBUG ( 1901): d12 0000000000000000 d13 0000000000000000 I/DEBUG ( 1901): d14 0000000000000000 d15 0000000000000000 I/DEBUG ( 1901): d16 41ce9259de341893 d17 3f50624dd2f1a9fc I/DEBUG ( 1901): d18 41c84da6fb800000 d19 0000000000000000 I/DEBUG ( 1901): d20 0000000000000000 d21 0000000000000000 I/DEBUG ( 1901): d22 0000000000000000 d23 0000000000000000 I/DEBUG ( 1901): d24 0000000000000000 d25 0000000000000000 I/DEBUG ( 1901): d26 0000000000000000 d27 0000000000000000 I/DEBUG ( 1901): d28 0000000000000000 d29 0000000000000000 I/DEBUG ( 1901): d30 0000000000000000 d31 0000000000000000 I/DEBUG ( 1901): scr 00000010 I/DEBUG ( 1901): I/DEBUG ( 1901): #00 pc 0000c9a6 /system/lib/libexfat_utils.so (buf_getblk) I/DEBUG ( 1901): #01 pc 000077c8 /system/lib/libexfat_utils.so (itr_get_next_dentry) I/DEBUG ( 1901): #02 pc 0000900e /system/lib/libexfat_utils.so (exfat_check_dir_internal) I/DEBUG ( 1901): #03 pc 000094e2 /system/lib/libexfat_utils.so (exfat_check_dir_internal) I/DEBUG ( 1901): #04 pc 000095a0 /system/lib/libexfat_utils.so (exfat_check_dir) I/DEBUG ( 1901): #05 pc 00009694 /system/lib/libexfat_utils.so (fs_check) I/DEBUG ( 1901): #06 pc 0000ac2c /system/lib/libexfat_utils.so (ffsCheckVol) I/DEBUG ( 1901): #07 pc 0000bff0 /system/lib/libexfat_utils.so (FsCheckVol) I/DEBUG ( 1901): I/DEBUG ( 1901): code around pc: I/DEBUG ( 1901): 4008c984 f8df6821 6019e084 68626820 f8556042 !h.....` hbhB`U. I/DEBUG ( 1901): 4008c994 6801000a 60216060 605c6803 68e26004 ...h``!`.h\`.`.h I/DEBUG ( 1901): 4008c9a4 609168a1 68a32100 60d868e0 48176872 .h.`.!.h.h.`rh.H I/DEBUG ( 1901): 4008c9b4 8014f8c4 61a16122 68004478 f300fa28 ...."a.axD.h(... I/DEBUG ( 1901): 4008c9c4 200ef855 0c3ff003 134ceb02 60e36899 U.. ..?...L..h.` I/DEBUG ( 1901): I/DEBUG ( 1901): code around lr: I/DEBUG ( 1901): ffffffb4 ffffffff ffffffff ffffffff ffffffff ................ I/DEBUG ( 1901): ffffffc4 ffffffff ffffffff ffffffff ffffffff ................ I/DEBUG ( 1901): ffffffd4 ffffffff ffffffff ffffffff ffffffff ................ I/DEBUG ( 1901): ffffffe4 ffffffff ffffffff ffffffff ffffffff ................ I/DEBUG ( 1901): I/DEBUG ( 1901): stack: I/DEBUG ( 1901): be94b838 00000100 I/DEBUG ( 1901): be94b83c 400a96a0 I/DEBUG ( 1901): be94b840 403d1f08 I/DEBUG ( 1901): be94b844 00005cf7 I/DEBUG ( 1901): be94b848 be94b954 [stack] I/DEBUG ( 1901): be94b84c 00000a25 I/DEBUG ( 1901): be94b850 00000000 I/DEBUG ( 1901): be94b854 00005cfc I/DEBUG ( 1901): be94b858 00000001 I/DEBUG ( 1901): be94b85c 400870c3 /system/lib/libexfat_utils.so I/DEBUG ( 1901): be94b860 be94b878 [stack] I/DEBUG ( 1901): be94b864 400a96a0 I/DEBUG ( 1901): be94b868 403d1ee8 I/DEBUG ( 1901): be94b86c 00016a97 I/DEBUG ( 1901): be94b870 df0027ad I/DEBUG ( 1901): be94b874 00000000 I/DEBUG ( 1901): #00 be94b878 be94b93c [stack] I/DEBUG ( 1901): be94b87c 400a96a0 I/DEBUG ( 1901): be94b880 00000003 I/DEBUG ( 1901): be94b884 00000000 I/DEBUG ( 1901): be94b888 403d1f88 I/DEBUG ( 1901): be94b88c be94b93c [stack] I/DEBUG ( 1901): be94b890 00005d00 I/DEBUG ( 1901): be94b894 400877cd /system/lib/libexfat_utils.so I/DEBUG ( 1901): #01 be94b898 400a96a0 I/DEBUG ( 1901): be94b89c 00000001 I/DEBUG ( 1901): be94b8a0 00000003 I/DEBUG ( 1901): be94b8a4 40089013 /system/lib/libexfat_utils.so I/DEBUG ( 1901): [email protected] -k -t -n -z -d -o /data/log/dumpstate_app_native -m 8945 I/BootReceiver( 2127): Copying /data/tombstones/tombstone_01 to DropBox (SYSTEM_TOMBSTONE) I/dumpstate( 8952): begin I/CrashReportBroadcastReceiver( 7291): New report detected, starting reporting service I/CrashReporterServiceDelegate( 7291): Running task for: SystemTombstone 10 reports (1 per task) W/AlarmManager( 2127): FACTORY_ON= 0 E/AmazonAppstore.ApplicationHelper( 7291): Received null package name. D/CrashReporterServiceDelegate( 7291): Processed 1 SystemTombstone report(s) D/CrashReporterServiceDelegate( 7291): 9 SystemTombstone report(s) remaining D/CrashReporterServiceDelegate( 7291): Processed 0 SystemTombstone report(s) D/CrashReporterServiceDelegate( 7291): No reports remaining to process for SystemTombstone, completing task So it would seem that for now, if you're using the stock ROM, exfat formatting is broken. :(
  3. I am having the same problem with the stock kernel, but I found that the battery drained even faster with RC2 than with 7.2 final.
  4. To edit the gps.conf using a gui, get FasterGPS from the play store. It works quite well.
  5. Have you tried multiupload? Since I don't have an hosting server I've been using it for my N1 MIUI ROMs, and it works well - and doesn't cost me a dime.
  6. [ROM] Cyanogenmod Green V5

    I've found the latest version of skype has a tendency to be immortal - I also ended up removing it as it kept waking up and restarting my network connection, even after I killed it a couple of times.
  7. [ROM] Cyanogenmod Green V5

    You need to use one of the TPTs from this thread. The first one is the recommended one, that will leave you with 160MB system space and nearly 300MB data.
  8. [ROM] Cyanogenmod Green V5

    Sapo A5 (Blade ZTE sold by Sapo/TMN Portugal), no problem at all. Wifi works well, the battery lasts 2 days.
  9. [ROM] Cyanogenmod Green V5

    This reply was to another thread, sorry about it.
  10. Market fix with miui ROM

    Did you ever had any luck with this? I am trying to get the market to work fully on MIUI but haven't had any luck lately. I forgot to add I even tried using CM7 build.prop unchanged, and I was still unable to see google apps in the market. With CM7 these apps are visible.
  11. [ROM] Cyanogenmod Green V5

    I am also having the non-scanning wifi problem, and nothing I did helped fix it. Will try the CM7.1.0RC Kang to see if the problem is also there.
  12. MCR r21 Archive

    I'd say yes. I had the same symptom, and fixed it by installing the rom which includes the radio. And I see no difference in signal strength or stability from the previous to froyo radio (I'm on 3 Italy).

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.