LiveView reverse-engineering effort

[exception13]

mind if i would add a simple framebuffer?

like.. writing into a buffer and displaying the buffer to the oled with an added method.

sadly the buffer would take more than half of the avilable ram :/ 128 x 128 x 2 byte


what are you working on now?

Sent from my HTC Vision using xda app-developers app

i'm make framebuffer and add screen update on timer event

 

[guv.]

Looks like Cyanogenmod 10.1 reintroduces the problem, that had been described for stock 4.2 before.
Tried it on both my original galaxy s and galaxy note, both can pair the liveview but when trying to connect with openliveview, it looks like its working for a second and then the icon disappears again and the connection is lost.
The original SE app works, though.

 

[smwinn7]

@guv. I experienced the same problem, I tried the latest version available here on the forum and uninstalled and re-installed the app from the market same problem all around with the Liveview pairing but not connecting.

 

[renzenicolai]

I need a logcat to solve problems like yours, please create one.

 

[guv.]

I need a logcat to solve problems like yours, please create one.

I will upload one tonight.

 

[exception13]

add framebuffer (reduce avaliable memory to 32Kb) and update thread
update: dynamic garphics console demo

 

[guv.]

Here is the promised logcat.

 

[boombuler]

Hey everyone.

I have some free time again. Who needs some help and what kind of help?

Regards
Boombuler

 

[xhozt]

Looks great only one big issue its got the same issue as i get on the SE version it keeps asking for a pairing key over and over and over ... ideas ?

 

[kingstonxl]

Looks great only one big issue its got the same issue as i get on the SE version it keeps asking for a pairing key over and over and over ... ideas ?

Never happened to me. Did u pair with LiveView name in device list? If not than try pair only if there's name not MAC adres.

Pairing issue is not faulty apps. Its rather faulty ROM or hw problem.

Sent from my Nexus 7 using xda app-developers app

 

[Alahdal]

Looks great only one big issue its got the same issue as i get on the SE version it keeps asking for a pairing key over and over and over ... ideas ?

What device and ROM you have. It happened to me with Galaxy Note and stock 4.1.2 .. But with the same device using CM10.1, I have no problem. I am using stock liveview.

Posted via mobile.
Galaxy Note N7000 burn with CM10.1

 

[xhozt]

What device and ROM you have. It happened to me with Galaxy Note and stock 4.1.2 .. But with the same device using CM10.1, I have no problem. I am using stock liveview.

Posted via mobile.
Galaxy Note N7000 burn with CM10.1

on a AT&Tgalaxys3 stock jellybean here . I get the same issue on either stock or the open source .

 

[Alahdal]

on a AT&Tgalaxys3 stock jellybean here . I get the same issue on either stock or the open source .

It is happening to many users with Samsung device, which confirms that it is because of Samsung stock ROMs.

Posted via mobile.
Galaxy Note N7000 burn with CM10.1

 

[jkorp]

I just tried to add the simple filter in the main branch. Since this is my first commit in a shared project, I made a very limited change to check out how it works.
The filter can be edited in the advanced settings (it was there but hidden in latest version). Hope this works out well for all of you, I have just made some limited testing with Galaxy S with Android 2.3.3.

 

[jkorp]

did you change the encoding aswell? äüö are now wrong encoded on my liveview.

Sent from my HTC Vision using xda app-developers app

I also noticed that the encoding has changed. ÅÄÖ worked well before, but each character is now a two-byte character combination. Can't figure out where the change was done in the source code, thought... Any ideas?

 

[renzenicolai]

I also noticed that the encoding has changed. ÅÄÖ worked well before, but each character is now a two-byte character combination. Can't figure out where the change was done in the source code, thought... Any ideas?

Yep, just look in the src/ nl/ rnplus/ olv/ messages/ calls/ folder for the following files and and replace UTF-8 with iso-8859-1

- DisplayPanel.java
- GetAlertResponse.java

Could you please move the filter to the ShowNotificationReceiver in the LiveViewService?
I tried to add the filter but my implementation doesn't work / I could not verify it worked so I hid it away.

Please change the accessibility services back to their original state.

The ShowNotificationReceiver: (maybe you see the bug in an instant. If you don't please move your filter to this part of the app, since both accessibility services deliver the notifications to this receiver)

    public class ShowNotificationReceiver extends BroadcastReceiver {  
        @Override  
        public void onReceive(Context context, Intent intent) {  
                if (intent.getAction().equals(ACTION_RECEIVE_SMS)) {
                NotificationNeedsUpdate = true;
                ContentNotification notification = SMSNotificationManager.getNotificationContent(context, intent);
                LiveViewDbHelper.addNotification(myself, notification.getTitle(), notification.getContent(), LiveViewDbConstants.NTF_SMS, notification.getTimestamp());
                }
                else {
                        String notificationContentFilter = (new Prefs(myself)).getNotificationFilter();  // Added by jkorp
                if (!notificationContentFilter.contains(intent.getExtras().getString("contents"))) {
                        NotificationNeedsUpdate = true;
                        LiveViewDbHelper.addNotification(myself, intent.getExtras().getString("title"), intent.getExtras().getString("contents"), intent.getExtras().getInt("type"),  intent.getExtras().getLong("timestamp"));
                        Log.w("ShowNotificationReceiver", "Added new notification.");
                }
                else {
                        Log.w("ShowNotificationReceiver", "Notification not added because of filter.");
                }
            }
        }  
    }

Thank you for your help!

 

[jkorp]

Yep, just look in the src/ nl/ rnplus/ olv/ messages/ calls/ folder for the following files and and replace UTF-8 with iso-8859-1

- DisplayPanel.java
- GetAlertResponse.java

Could you please move the filter to the ShowNotificationReceiver in the LiveViewService?
I tried to add the filter but my implementation doesn't work / I could not verify it worked so I hid it away.

Please change the accessibility services back to their original state.

The ShowNotificationReceiver: (maybe you see the bug in an instant. If you don't please move your filter to this part of the app, since both accessibility services deliver the notifications to this receiver)

    public class ShowNotificationReceiver extends BroadcastReceiver {  
        @Override  
        public void onReceive(Context context, Intent intent) {  
                if (intent.getAction().equals(ACTION_RECEIVE_SMS)) {
                NotificationNeedsUpdate = true;
                ContentNotification notification = SMSNotificationManager.getNotificationContent(context, intent);
                LiveViewDbHelper.addNotification(myself, notification.getTitle(), notification.getContent(), LiveViewDbConstants.NTF_SMS, notification.getTimestamp());
                }
                else {
                        String notificationContentFilter = (new Prefs(myself)).getNotificationFilter();  // Added by jkorp
                if (!notificationContentFilter.contains(intent.getExtras().getString("contents"))) {
                        NotificationNeedsUpdate = true;
                        LiveViewDbHelper.addNotification(myself, intent.getExtras().getString("title"), intent.getExtras().getString("contents"), intent.getExtras().getInt("type"),  intent.getExtras().getLong("timestamp"));
                        Log.w("ShowNotificationReceiver", "Added new notification.");
                }
                else {
                        Log.w("ShowNotificationReceiver", "Notification not added because of filter.");
                }
            }
        }  
    }

Thank you for your help!

I have reverted my changes, and will try to implement it in ShowNotificationReceiver instead (when I get time...).

When changing back the UTF-8 to iso-8859-1 it works again. Anyone seeing a reason to keep UTF-8? Does it work better with other languages?

 

[renzenicolai]

UTF-8 is not working so lets change it back

 

[kingstonxl]

UTF-8 is not working so lets change it back

In polish it showed ? marks on special chars so it would be nice to use utf8 or dono maybe some switch? Sony apps didn't have any problem with polish so they had some resolution how to make it work in multiple charsets. Does anyone have some ideas?

Sent from my Nexus 7 using xda app-developers app

 

[jkorp]

I took a quick look, and the code in LiveViewService-->ShowNotificationReceiver is never used because the Intent is never sent from GetNotificationService (it is commented out). If I enable the code in GetNotificationService (and remove the call to the database there), it works well to filter out the notifications in ShowNotificationReceiver... Now my time is out for today...