Related
This is a temp. post till we get things sorted out and post the primary info about dev efforts.
If you're interested in helping out, msg nprussel or me.
1: As I mentioned in a previous thread, we gotta sort libhardware_legacy related bangs.
The base build is a hybrid of SDK, Nexus, Hero, Eris and Sprint.
Talk about a cocktail...
Not all of the latest Sprint drivers were compatible with the Hero, hence the mixture.
2: Devs with good experience will get contributor/commit access to the git branch.
3: Use pastebin for logcat and/or other logs/configs etc.
4: Use this url for bug tracking
- PLEASE keep this thread clean, with discussion pertaining ONLY to development/bugs/issues/ideas/successes.
- Flag the above (your remarks) as [MAJOR], [ENHANCEMENT], [CRITICAL], etc.
- We know you appreciate our work and would like to thank us, so no need to write a post about it.
- If you really want to thank us, each of the devs involved will be listed in one of the first posts, and you can PM him/her or donate.
Here's the git tree.
In order to avoid unnecessary questions, and cluttering the thread with useless posts, please read the README.
This will be updated later today or in the days to come, as patches make their way in.
/* .reserved */
/* .reserved_2 */
/* .reserved_3 */
Reserved ///
adwinp said:
nprussel's post kindda moved me.
This is a temp. post till we get things sorted out.
If you're interested in helping out, msg nprussel or me.
Click to expand...
Click to collapse
I dunno if you have FTP space for releases, but we have about 10 servers over at VillainROM that we can use for hosting a community release. Not sure if I've shown nathan how to use them all yet.
I initially proposed private git repos for binary rls hosting, but FTP might work well in the beginning phases.
Although git is immensely easier for commits.
If you have admin access, would you mind setting up git?
Anyway, we've already PMed each other, Nathan and I.
What I propose is thus:
We have to start with a unique codebase.
Upload one of our ports (I can up mine already), with a change description, create a git branch, and then start with the devving.
I've just PM'd you, however, something that I would like to add as well, is that I can also host a git server for you on my personal server (which is internationally hosted and very fast). Honestly, I am not using it to it's full potential at all, so I would rather put it to a good use like this.
Let me know,
Mr P.
Don't forget to set up a paypal donate site for this proyect, would love to provide you the beer needed to cool your brains
Which devs are already on this boat?
nesukun said:
Don't forget to set up a paypal donate site for this proyect, would love to provide you the beer needed to cool your brains
Click to expand...
Click to collapse
same here, as i am a noob regarding developing this would be the only way to support you a bit.
Just hope the devs can all work together and we dont want to end up with loads of roms like we have for 2.1
-------------------------------------
Sent via the XDA Tapatalk App
adwin / nathan: I'm a linux + C coding guru (Working with embedded devices at my job) but Android is still pretty new. I'm getting more and more interested since the 2.6.29-project has started to matter .
I'm more than willing to get my hands dirty, I just don't know how. Since porting from device A to device B probably means a lot of android-internals I don't think I'm much use.
But if you guys think I can help with something or speed things up (from scripting to writing commandline stuff, might even dive into writing Android apps if it's needed) don't hesitate to drop a note somewhere.
adwinp said:
I initially proposed private git repos for binary rls hosting, but FTP might work well in the beginning phases.
Although git is immensely easier for commits.
If you have admin access, would you mind setting up git?
Anyway, we've already PMed each other, Nathan and I.
What I propose is thus:
We have to start with a unique codebase.
Upload one of our ports (I can up mine already), with a change description, create a git branch, and then start with the devving.
Click to expand...
Click to collapse
Yeah. Git is good for the stuff using source code, and a good idea for commits etc.
If you are wanting worldwide mirrors for ROMs (I can't see end users wanting to download from git ), I can give you access to the mirroring software on VillainROM. To do that, I think you need a forum account, as all the security checks are carried out using forum logins. Not sure though...
It will mirror to UK, USA (several over there), Asia, Europe, Israel and Scandanavia. Might be more I've forgotten about.
i will provide beer also...
Good News
any more informations?
It would be great if all the Hero custom ROM developers would join their forces together and build one excellent Android 2.2 rom
stephenophof said:
It would be great if all the Hero custom ROM developers would join their forces together and build one excellent Android 2.2 rom
Click to expand...
Click to collapse
Same thing in my mind. Keep up developers it would be cool
adwinp said:
nprussel's post kindda moved me.
This is a temp. post till we get things sorted out.
If you're interested in helping out, msg nprussel or me.
Click to expand...
Click to collapse
which post?
It's great to see that at least some people here have the community spirit!
I really hope this ROM will be the best there ever was, because of the combined effort. We can show the world that this community can produce great things!
All the devs on this project have my support!
Full froyo boot logcat
Currently doing a total rewrite of this, and it's also renamed to izPassKeeper !
The development progressed and ended up in a Windows Phone 8 app, PassPro
izPassKeeper
General Info - This post
Changelog - Second post
Screenshots - Third post
Coming features - Fourth post
Credits and references - Fifth post
Latest Version: 1.0.511.536 (DOWNLOAD)
Description:
This is a simple app for storing usernames, passwords, links and descriptions for various accounts.
You have the option to have the passwords encrypted.
Other info:
This app might be sold to a corporation later on.
I had my first meeting with the corporation and they wanted me to get some feedback, so here I'll post the XAP for you XDA members.
Try it out and return with some feedback and suggestions.
Please like the Facebook page
Regards!
Izaac
Changelog
Changelog
1.0.511.536 - 2001-12-10 (↓)
Removed the forgotten build date test that didn't work xD
1.0.509.1813 - 2011-12-08 (↓)
Some bugfixes and some new features:
Fixed the add page
Added copy function for Username/Password and Description (single tap or in appbar)
Links now open in default browser
Changed versioning to standard .NET.
1.0.0.0 - 2011-12-04 (↓)
First public release
Screenshots
Screenshots
Coming features
Coming features
Syncing information to a secure server
Password required for decryption
Encryption for selected items only
Customizing the list items
Edit account information
Credits and references
Credits and references
Credits
HTC - for this fantastic device !
Microsoft - an awesome platform and an awesome IDE
XDA-Developers - being a place to learn and publish a lot of stuff ! The only forum for me !
Click to expand...
Click to collapse
References
MSDN (AesManaged, XML, IsolatedStorage)
Click to expand...
Click to collapse
Good application but needs some improvement
Application is useful..however the text field is somewhat small in size. Also, I am unable to scroll down to 'description' and 'password' field is easily...
Have a look at the screenshot. I am using HTC Mozart
Also you will need to allow to copy the password or the account name e.g. twitter handle
withwindows said:
Application is useful..however the text field is somewhat small in size. Also, I am unable to scroll down to 'description' and 'password' field is easily...
Have a look at the screenshot. I am using HTC Mozart
Click to expand...
Click to collapse
Thanks for the info. I'll look into it and fix it
wpxbox said:
Also you will need to allow to copy the password or the account name e.g. twitter handle
Click to expand...
Click to collapse
That's being added to the list Never thought of that actually Great idea (Y)
1) Also the text box should be bigger so I can See what is getting typed in.
2) I should be able to edit it.
3 ) When pushing the encrypt button the app exists on me.
You should provide an option to have a 'master password' kind of thing. This will keep our encrypted data safe from others. Decrypt option can be used to access all the sensitive information like password, site.
See youtube video link for better idea http://www.youtube.com/watch?v=HZyEslVBVCE&hd=1
IzaacJ said:
Thanks for the info. I'll look into it and fix it
That's being added to the list Never thought of that actually Great idea (Y)
Click to expand...
Click to collapse
withwindows said:
You should provide an option to have a 'master password' kind of thing. This will keep our encrypted data safe from others. Decrypt option can be used to access all the sensitive information like password, site.
See youtube video link for better idea http://www.youtube.com/watch?v=HZyEslVBVCE&hd=1
Click to expand...
Click to collapse
A masterkey is already being worked on, and it will also affect the cryptation of the data.
I will hopefully release a new version today with:
Site URI clickable and opens in Webbrowser
Able to copy Username/Password/description
Add accound page fixed
Looks nice. But I have one question, can I import passwords database in kdb format (create on PC using KeePassX)? When not are you plan to make this function?
EDIT
Ups, didn't see that is for WP7.
Cool. I shall wait for the new version..I will post the video as soon as I get my hands on the new version. Ability to open link in the new browser, masterkey, ability to copy-paste will definitely make this application much more useful.Al the best.
withwindows said:
Cool. I shall wait for the new version..I will post the video as soon as I get my hands on the new version. Ability to open link in the new browser, masterkey, ability to copy-paste will definitely make this application much more useful.Al the best.
Click to expand...
Click to collapse
Just posted the update
EDIT: Just added a new version which removes the build date thingies in the about page that I forgot to remove
Soo, no comments on the updated version?
This will be posted on wAppStore, just waiting for confirmation
Rewriting this from scratch ! Doing some changes on the basic workings and a major graphical overhaul
I had a little time on my hand so I took this and cleaned it up (removed docs, repetitions, collected kernel commits, ...).
Note that this is the internal commit history of google developers. You shouldn't read too much into it because:
1.Most changes are under the hood stuff that is only interesting to developers.
2.It probabely doesn't reflect all the changes google made
3.Some changes may have not made it into the final release
4.Some changes are specific to other devices
5.Some don't make sense without looking at the code
Nevertheless, there are some interesting descriptions that reflect some of the stuff people have reported : faster rotation, dial redesign, android os battery bug, lock later after power button, keyboard lag, etc.
I have added "****" before ones I found interesting for us users.
Pastebin Link
Thanks for this! Very interesting.
Good work for collecting and identifying the changes understood by Users......
Thanks for this! You might also want to consider starring "More aggressive fix for phone lookup issues" (the comments after this are very telling) as I have run into this issue.
Nice work.
It's annoying Google don't provide an official changelog. Especially considering they push such things so hard for apps when they get updated, what with the new What's New bit.
torospr must be the Sprint version.
El Daddy said:
torospr must be the Sprint version.
Click to expand...
Click to collapse
yeah, it is. JBQ said it somewhere in the android building group.
BinkXDA said:
Thanks for this! You might also want to consider starring "More aggressive fix for phone lookup issues" (the comments after this are very telling) as I have run into this issue.
Click to expand...
Click to collapse
thanks. added.
If anyone else spots something please let me know.
Some people over at the fairphone.com forum reported a "sensitive" screen. They try to tap on a button (or link) and instead of triggering the button the fairphone starts scrolling. My fairphone also shows this behavior and I tried to find out why. Well, after trying for some time I realized that the shorter I tap on the screen the more likely it happens in a swipe/scroll.
So I enabled the "pointer position" option within the developer tools and shot two screen shots. In the first screenshot I tap for round about 500ms whereas in the second screenshot I tried to tap as short a possible. Like you would click with mouse. It show the error pretty obvious. Any ideas how to adjust that?
Hello
I noticed exactly this behaviour on my Fairphone, too.
That's why I started a thread on the official Fairphone website 22 days ago.
I'm not allowed to post direct links here, so I can give you only the head line here:
"Hyper-sensitive-touchscreen"
And on german Fairphone Freunde forum there's also a thread about this problem
Key-Word:
"Empfindlichkeit-des-Touchscreen"
So far, there is not very much response on these threads, but it seems that not all the handsets are affected, because not all of the answers confirmed the problems. One of the guys on fairphone website sent a request to the support team, a few days ago. Maybe he can forward the answer he gets... I'll ask him in his own fairphone thread - "Sensibility-and-reboots"
Unfortunately my phone broke after just one day, so I'm waiting for a replacement now and can't really offer a solution here...
But during the few hours, my phone worked, I entered the engineering mode (by typing *#*#3646633#*#* in the standard dialler app) and there were many options to manipulate the tuochscreen.
Maybe the more experienced guys here in the forum can work out a solution to solve the problem?!
Thank you in advance!
I have the same "hypersensitive screen" issue
Before I was used to briefly and lightly tapping/touching the screen, but with my Fairphone that often gives a scroll signal.
My developer crosshair option shows short lines, the touchpanel behaves as if I first tapped a few centimers away and then a split second later it registers where I actually touched the screen.
I had to learn to firmly tap and hold, otherwise I couldn't select anything on the screen.
It seems a sofware patch for the touchpanel is needed.
-----------------------------------------------
Fairphone FP1
Caju (v.1.1)
Touchscreen settings
I am copying this from the Fairphone forum, for future reference:
My settings, as copied from engineering mode:
tpd_em_log = 0
tpd_em_log_to_fs = 0
tpd_em_sample_cnt = 16
tpd_em_auto_time_interval = 10
tpd_em_pressure_threshold = 0
tpd_em_debounce_time = 0
tpd_em_debounce_time0 = 1
tpd_em_debounce_time1 = 4
tpd_em_spl_num = 1
tpd_em_asamp = 1
NOTE: Do NOT change any of the values (in this case, under Settings). I do not know what they do, really, and how your device might react! I just report mine, for your comparison.
Just FTR, my device works fine!
Any values different from yours? Then I would suggest reporting the issue to FP while including the link to our discussion here, and on the Fairphone forum. If we can narrow down the source of the problem to be caused by some settings, and not your environment or your specific devices hardware malfunctioning, @benkxda could report this to FP in his next mail.
boondiordna said:
I am copying this from the Fairphone forum, for future reference:
My settings, as copied from engineering mode:
tpd_em_log = 0
tpd_em_log_to_fs = 0
tpd_em_sample_cnt = 16
tpd_em_auto_time_interval = 10
tpd_em_pressure_threshold = 0
tpd_em_debounce_time = 0
tpd_em_debounce_time0 = 1
tpd_em_debounce_time1 = 4
tpd_em_spl_num = 1
tpd_em_asamp = 1
NOTE: Do NOT change any of the values (in this case, under Settings). I do not know what they do, really, and how your device might react! I just report mine, for your comparison.
Just FTR, my device works fine!
Any values different from yours? Then I would suggest reporting the issue to FP while including the link to our discussion here, and on the Fairphone forum. If we can narrow down the source of the problem to be caused by some settings, and not your environment or your specific devices hardware malfunctioning, @benkxda could report this to FP in his next mail.
Click to expand...
Click to collapse
I already put a link on fairphone.com to this XDA thread. Thanks for telling! Well, my settings looks identical to yours. I also played around with them. I have no idea if touch screens nowadays need deboucing or sth like that. So I changed these settings a bit...without improvement though. I am also wondering what tpd_em_log is. It is put to 0. I put it to 1 hoping there is some log written somewhere....but i could not find where unfortunately.
Hey there,
I have the same problem and no solution. But here is my input on that issue. Maybe it helps Fairphone when they investigate that issue, maybe not.
hanzano said:
Well, after trying for some time I realized that the shorter I tap on the screen the more likely it happens in a swipe/scroll.
Click to expand...
Click to collapse
I realized the same thing. BUT in addition, I figured out that it has also something to do with how soft you touch. If I try and touch my screen very very gently, I can reconstruct that behaviour every time. If I press a bit harder, it works better.
I attached a screenshot where I did soft touches, and you see a lot of wiggeling especially in the botom row
Yesterday I was annoyed by this issue. I was a bit in a hurry and the Fairphone touchscreen did not react properly
So I just debugged in Android Studio and this is what I logged:
Code:
12:07:48.874 MotionEvent.ACTION_DOWN: 300.44363, 485.4943
12:07:48.886 MotionEvent.ACTION_MOVE: 293.13342, 499.09888
12:07:48.901 MotionEvent.ACTION_MOVE: 293.45657, 497.48178
...
12:07:49.168 MotionEvent.ACTION_MOVE: 293.45657, 497.48178
12:07:49.183 MotionEvent.ACTION_MOVE: 291.2037, 497.48178
12:07:49.198 MotionEvent.ACTION_MOVE: 290.46213, 497.48178
...
12:07:49.403 MotionEvent.ACTION_MOVE: 290.46213, 497.48178
12:07:49.406 MotionEvent.ACTION_UP: 290.46213, 497.48178
12:07:49.406 event.getDownTime: 566
I tapped for 566ms. Pretty obvious that from ACTION_DOWN to the first ACTION_MOVE there is a big delta of ~14px (is it really pixel?) in y-direction.
Hey there,
probably this does not help anyone, but just for the sake of documentation: due to my headphone-jack issue, my fairphone got replaced by a new one. Now it seems that my sensitive screen issue is gone.
I don't know about how many sources you guys have, but if you have the kernel sources, someone could try to implement a filter (and enable debugging logs in the kmsg ofc) so touches under 400ms (just a value for explanation) are only getting registered as touches, but not as movements. However, this could also have some downsides (pretty fast swipes for example), therefore a sysfs option would be a nice idea
But this would at least be a workaround.
Hyst said:
Hey there,
probably this does not help anyone, but just for the sake of documentation: due to my headphone-jack issue, my fairphone got replaced by a new one. Now it seems that my sensitive screen issue is gone.
Click to expand...
Click to collapse
Hmm, ok.Would you mind doing another sreenshot like you did already? Just in order to see the difference.
laufersteppenwolf said:
I don't know about how many sources you guys have, but if you have the kernel sources, someone could try to implement a filter (and enable debugging logs in the kmsg ofc) so touches under 400ms (just a value for explanation) are only getting registered as touches, but not as movements. However, this could also have some downsides (pretty fast swipes for example), therefore a sysfs option would be a nice idea
But this would at least be a workaround.
Click to expand...
Click to collapse
That is what I also had in mind. I already had a look at Xposed framework trying to find out how to "intercept" global touches. With a normal Android Service it is unfortunately not possible at least what I have read so far.
hanzano said:
That is what I also had in mind. I already had a look at Xposed framework trying to find out how to "intercept" global touches. With a normal Android Service it is unfortunately not possible at least what I have read so far.
Click to expand...
Click to collapse
Xposed is a genious piece of work, however, this should be done via kernel.
Maybe @benkxda could have a chat with Fairphone about that?
hanzano said:
Hmm, ok.Would you mind doing another sreenshot like you did already? Just in order to see the difference.
Click to expand...
Click to collapse
no problem. Here you go!
As far as I am concerned I did the same thing. small fast touches.
although sometimes there is a long line, overall a lot less wiggeling.
Hyst said:
no problem. Here you go!
As far as I am concerned I did the same thing. small fast touches.
although sometimes there is a long line, overall a lot less wiggeling.
Click to expand...
Click to collapse
That looks much better than beforehand. I believe the red lines are not of interest. These just seem to be estimations. I had a look into Android source code com.android.internal.widget.PointerLocationView. The VelocityTracker has an Estimator which is drawn in light red. The MediaTek development tool seems to do it similar. So I would only count the green lines.
But I still think that this is not perfect either. I checked with my old Samsung Galaxy Ace and the Android location pointer which really gives points, no line at all when tapping shortly.
laufersteppenwolf said:
Xposed is a genious piece of work, however, this should be done via kernel.
Maybe @benkxda could have a chat with Fairphone about that?
Click to expand...
Click to collapse
I absolutely agree with you that this should actually be done on kernel/driver level. But I have no idea about Android's kernel structure or any driver layer at all. I used the Android SDK though. And unfortunately MediaTek is not giving all sources for the FairPhone
Where exactly do you expect touches to be evaluated and "forwarded" to Android? Do you have some example code of other phones probably? I am just interested how this works in software.
hanzano said:
I absolutely agree with you that this should actually be done on kernel/driver level. But I have no idea about Android's kernel structure or any driver layer at all. I used the Android SDK though. And unfortunately MediaTek is not giving all sources for the FairPhone
Where exactly do you expect touches to be evaluated and "forwarded" to Android? Do you have some example code of other phones probably? I am just interested how this works in software.
Click to expand...
Click to collapse
Sorry for the late answer, haven't seen you post
Well, kernel sources are quite easily structured, you've got the drivers, in there you find the input drivers, in which you also find the touchscreen drivers. in there are several drivers, you then need to find the correct one (in my case it's THIS file). In there are all functions to make your touchscreen work. This device also has a filter for "ghost" touches, just search for it inside this file
So, if you have located the driver of your device, you can there all needed stuff, such as the filter I mentioned
laufersteppenwolf said:
Sorry for the late answer, haven't seen you post
Click to expand...
Click to collapse
No prob
laufersteppenwolf said:
Well, kernel sources are quite easily structured, you've got the drivers, in there you find the input drivers, in which you also find the touchscreen drivers.
Click to expand...
Click to collapse
Ah ok, got it. In folder alps >> kernel >> drivers >> input >> touchscreen there are 68 files.
laufersteppenwolf said:
in there are several drivers, you then need to find the correct one (in my case it's THIS file).
Click to expand...
Click to collapse
Did you forget the link on "THIS" probably?
laufersteppenwolf said:
In there are all functions to make your touchscreen work. This device also has a filter for "ghost" touches, just search for it inside this file
So, if you have located the driver of your device, you can there all needed stuff, such as the filter I mentioned
Click to expand...
Click to collapse
Vielen Dank! Helps a lot
hanzano said:
Did you forget the link on "THIS" probably?
Click to expand...
Click to collapse
Ooops yeah, I did So HERE you go
Hello @Hyst
In the last week I was discussing with the support team pretty intensively about the touchscreen issue.
Now, they asked me to send them my phone, to see what happens on the device.
But, as I'm working abroad, its not that easy for me, to send it soon.
That's why I suggested, they should ask you, to get the IMEI of your old device - as you offered in the general thread.
Unfortunately Rick de Groot (the support guy) asked me again, to ask you for this number...
A little bit strange, but this is what I want to do now
Can you please send your old IMEI number and the RMA (repair form number) to this email:
<[email protected]>
That would be really great!
PS:
My Name is Florian W. if you want to quote me in your email.
Maybe this helps them to relate your email to my support request.
Thank you in advance!
Holzwurm86
Hi @Holzwurm86
sure thing. I've just send them an email.
Holzwurm86 said:
In the last week I was discussing with the support team pretty intensively about the touchscreen issue.
Now, they asked me to send them my phone, to see what happens on the device.
Click to expand...
Click to collapse
Good to see that there is still progress. The list of phones being affected gets bigger at the fairphone.com forum. If the engineers from Kwamecorp or Changhong need help like debugging or logging touches I am willing to help of course.
Hey Guys,
I'm running LineageOS on multiple devices and was wondering if its possible to configure the privacy guard. For instance, that it don't allowed newly installed applications to start at boot, or runing in background. Do you understand?
Devices:
Samsung S7 LOS 14.1 official link
Samsung S4a LOS 14.1 unofficial link
Samsung Galaxy Tab 2 official link
You can use 'enable by default' option for newly installed apps but it only blocks personal permissions by default. When you install a new app, you'll be prompted to take control of privacy guard to set other permissions.
Sent from my ZUK Z1 using Tapatalk
So there is no way to preconfig this? Like a simple config file?
*push*
Anyone? This seams so easy and fundamental for me, that I can't believe no one needed or implemented that feature
chrisrevoltes said:
*push* Anyone? This seams so easy and fundamental for me, that I can't believe no one needed or implemented that feature
Click to expand...
Click to collapse
Locating a Guide, Tutorial, etc... that's specific to Privacy Guard is a challenge and I do believe that certain LineageOS features should have something to explain as well as some guidance and such.
The best that I can find is actually within a device specific area of the forum that appears to apply to most all device regarding this feature.
Hopefully the information on the following thread is helpful for you and you may be able to obtain some member guidance and clarification as a question "in general".
https://forum.xda-developers.com/showthread.php?t=3739136
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Not sure if this is what you're looking for, but in my LOS15.1 ROM, I can go to Settings and search for "privacy", and find the settings for Privacy Guard. The PG settings for each app can be configured manually, and there are also a few options like "Enabled by default" and "Show notifications".