This app has been heavily inspired by SabrWolfs [APP][ROOT] Touch screen fixer.
The app is supposed to at least temporarily improve the touch on the Oneplus one, making the device usable. I can't guarantee that it works for you, but it makes a big difference for me.
The app requires root, and executes the shell command cat /sys/class/input/input0/baseline_test every time the screen is turned on. It is not based on Tasker, but implemented as an ordinary app. The difference compared to Touch screen fixer, and the reason I made this app, is that the vibration is configurable. I initially implemented this app to be able to deactivate the vibration entirely, but since it actually takes a second or two to run the command and get touch working again, I found that I actually prefer a very brief vibration as feedback that the device is ready for use.
As usual with root apps, don’t forget to grant the app root access the first time it is started, otherwise it won’t work.
And as always, I can't take any responsibility if this app makes your house to burn down, your car to explode or your phone to overheat
Edit:
Here is the complete code:
https://github.com/jaqob/OnePlusTouchFix
It was not really intended to be shared, so be gentle
Allot of users have been helped by flashing a different ROM, so it's kind of ROM related I guess.
Therefor it might be best to tell people which ROM you are using.
Gamm86 said:
Allot of users have been helped by flashing a different ROM, so it's kind of ROM related I guess.
Therefor it might be best to tell people which ROM you are using.
Click to expand...
Click to collapse
I'm using stock 12.0-YNG1TAS2I3, the latest offical CyanogenMod release. But, the same problem existed before as well, so it is not directly related to a specific ROM.
102 downloads and not a single reply or thank you..
I can't give any feedback,i never had any problems with my touchscreen.
But Thanx for posting your work and apparently your app works as intended or there would have been a S...storm.
zodiaxe66 said:
102 downloads and not a single reply or thank you..
I can't give any feedback,i never had any problems with my touchscreen.
But Thanx for posting your work and apparently your app works as intended or there would have been a S...storm.
Click to expand...
Click to collapse
Yes, this must be the first bug free app ever
let me try and giv u a result
As the result, i do feel different in touch screen. Much more sensitive
Thanks will try it
Could anybody explain why cat-ting a file (i.e. just read a file content) can fix some issue?
May I see the source code of this apk?
Am using oxygen os from day 1 and never had suck issue.
Though i had some problem in cyanogenmod nightlies so reverted back to stock oxygenated n os
Sent from my A0001 using XDA Free mobile app
dxxvi said:
Could anybody explain why cat-ting a file (i.e. just read a file content) can fix some issue?
May I see the source code of this apk?
Click to expand...
Click to collapse
The relevant part really just looks like this
Code:
public static int runTouchFixCommand()
{
int result = -1;
try {
Process p = Runtime.getRuntime().exec(new String[]{"su","-c","cat /sys/class/input/input0/baseline_test"});
result = p.waitFor();
} catch (IOException | InterruptedException e) {
e.printStackTrace();
}
return result;
}
The key here is that it is the /sys folder. It is not an ordinary filesystem but a virtual one used to communicate with different attached devices, in this case the synaptic touch driver.
See wikipedia for some further details: https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard#FHS_compliance
If I understand things correctly, reading baseline_test will run this code:
https://github.com/CyanogenMod/andr...s/input/touchscreen/synaptics_dsx_i2c.c#L1780
Which near the end does this "//step 5:reset touchpanel and reconfig the device".
Or it may just be magic
Edit:
Here is the complete code:
https://github.com/jaqob/OnePlusTouchFix
It was not really intended to be shared, so be gentle
Definitely works very well. I was using SabrWolf fix before this, thanks for the additional vibration duration option.
Unfortunately this app seems to be needed for CM12.1 as well. Fortunately it still works
Is it possible to make updates or make new version for CAF build rom?
This apps work well on Slimsaber but didn't work on sultanxda Caf build...when I use it on I got this popup "fail to excute command, is you phone rooted?"....both rom is rooted btw...
Sent from my A0001 using Tapatalk
nice app i think
since i didnt encounter any touch issue in my OPO since day 1
cant say any, but its a good job
u should try to implement it in xposed and caf
iPusak Gaoq™ said:
Is it possible to make updates or make new version for CAF build rom?
This apps work well on Slimsaber but didn't work on sultanxda Caf build...when I use it on I got this popup "fail to excute command, is you phone rooted?"....both rom is rooted btw...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I haven't tested any CAF build (perhaps I should), but in the sultanxda case, I would guess this line in the description is to blame "Rewrote half of the Synaptics touchscreen driver (over 2500 lines of code modified; your touchscreen might work better)". The function my small app relies on (synaptics_rmi4_baseline_data in synaptics_dsx_i2c.c) is removed. So I'm afraid I can't get it to work there.
wrinkletit said:
nice app i think
since i didnt encounter any touch issue in my OPO since day 1
cant say any, but its a good job
u should try to implement it in xposed and caf
Click to expand...
Click to collapse
I have worked a bit with xposed, but I don't really see any gain to use it for this purpose..?
iPusak Gaoq™ said:
Is it possible to make updates or make new version for CAF build rom?
This apps work well on Slimsaber but didn't work on sultanxda Caf build...when I use it on I got this popup "fail to excute command, is you phone rooted?"....both rom is rooted btw...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I have tried Sultans CM12 version, with the CAF kernel now, and my phone is working better then it ever have. No problem with the touch, so no need for this app, at least not for me.
Related
I tried the latest build of CM7 done by the Atrix Dev Team and it is awesome. Very reliable, fully functional, etc. I figured I'd give a whirl to compiling the real ICS version to see what that was like.
CM9 build system with the appropriate Atrix Dev Team repos in place actually spit out a working ROM. There are a number of issues aside from the general preview state of CM9. I figured I would share them in case anyone else was as curious as me. Apparently, the internal atrix dev teams are well beyond these issues already, so kudos.
Probably related to CM/atrix specific stuff
- Camera and finger print sensor don't work
- Launcher crashes pretty often
- Some openGL demos don't seem to work right (or at all)
- No mounting the SD as USB storage
Probably related to the specific gapps package I used.
- Maps crashes after 3 seconds (signal 11 - native code crash)
- Maps wants to update, but it can't (sharedId conflict if you actually remove maps)
- Earth won't run (missing the earthmobile library)
- Google Voice Search bombs (signal 4 - illegal instruction - currently suspecting the native packages might have some NEON instructions that the atrix cpu doesnt support)
- Calendar will not sync for google or exchange. App loads, but the sync service is failing
- Lots of null pointer exceptions for the NFC stuff in the log.
Anyway, this is just a build of the code that's out there, nothing special done by me. It might be useful for a dev phone or something but not for use on a real day-to-day device. Obviously it doesn't have the google apps embedded in it.
http://www.multiupload.com/XT9QPPQYF1 thanks xploited for uploading
md5: 670068584eb94bf1d660c0450815ad0d
Personally, I had trouble going back to CM7 afterwards, my clockwordmod backups were screwed up (bad boot.img? cross-linked files on the SD card) and I had a very hard time getting back to the good ole working state. Ultimately, I had to restore the partial backup and then reflash the CM7 image + gapps.
So, if you were curious what building a random repo on the web and installing it on your phone would do, then feel free to try and lose all of your data. There are no updates/support for this, etc. It's just a curiosity... what is the state of this stuff right now?
BTW... I am back on CM7/Atrix now which is AWESOME!!!!
Source Code Links:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Not sure how the dev team would react to this ..we do not want any bricked phones because of this ..there maybe some experimental dangerous code in there in those sources as of now ..not sure though
Hmm... figured since I spent quite awhile getting a build set up, it might be worth sharing. I am happy to take down if it is inappropriate.
Well I am not the best person to answer that ...but yeah thanks for your work.
Eh, I wouldn't be mad about it, but I think it needs more caution. I would just wait. As you say, it kindof screwed with a lot and wasn't very usable, so why flash it? Maybe ok for someone who wants to look at the code, but I wouldn't flash it.
Awesome news man. Thanks for being a lab rat and giving us an update.
Sent from my MB860 using xda premium
Not so much take it down as change the title of the post.
the current internal atrix-dev-team cm9 is way further ahead of this, we have some different patches. this is missleqading as it makes it sound official and is not.
Could you please change the tittle to [KANG] CM9 Test Build by "your name"
and please link to the sources, as is proper practice for open source projects
thank you
samcripp said:
Not so much take it down as change the title of the post.
the current internal atrix-dev-team cm9 is way further ahead of this, we have some different patches. this is missleqading as it makes it sound official and is not.
Could you please change the tittle to [KANG] CM9 Test Build by "your name"
and please link to the sources, as is proper practice for open source projects
thank you
Click to expand...
Click to collapse
and I guess you guys deserve a Xmas break now ...
It's nice to see that! Thanks for your hard work.
I'm looking forward to the CM9
Thank you for this.
!
Anyways, Just out of curiosity... where can you find the official Atrix Dev team's CM9?
The one been worked on by turl is with him, that is not for public release.
Dont forget to tell him merry xmas!
I always forget what kang means.
Sent from my MB860 using XDA App
wrldsuksgo2mars said:
I tried the latest build of CM7 done by the Atrix Dev Team and it is awesome. Very reliable, fully functional, etc. I figured I'd give a whirl to compiling the real ICS version to see what that was like.
CM9 build system with the appropriate Atrix Dev Team repos in place actually spit out a working ROM. There are a number of issues aside from the general preview state of CM9. I figured I would share them in case anyone else was as curious as me. Apparently, the internal atrix dev teams are well beyond these issues already, so kudos.
Probably related to CM/atrix specific stuff
- Camera and finger print sensor don't work
- Launcher crashes pretty often
- Some openGL demos don't seem to work right (or at all)
- No mounting the SD as USB storage
Probably related to the specific gapps package I used.
- Maps crashes after 3 seconds (signal 11 - native code crash)
- Maps wants to update, but it can't (sharedId conflict if you actually remove maps)
- Earth won't run (missing the earthmobile library)
- Google Voice Search bombs (signal 4 - illegal instruction - currently suspecting the native packages might have some NEON instructions that the atrix cpu doesnt support)
- Calendar will not sync for google or exchange. App loads, but the sync service is failing
- Lots of null pointer exceptions for the NFC stuff in the log.
Anyway, this is just a build of the code that's out there, nothing special done by me. It might be useful for a dev phone or something but not for use on a real day-to-day device. Obviously it doesn't have the google apps embedded in it.
http://goo.gl/39NnA
Personally, I had trouble going back to CM7 afterwards, my clockwordmod backups were screwed up (bad boot.img? cross-linked files on the SD card) and I had a very hard time getting back to the good ole working state. Ultimately, I had to restore the partial backup and then reflash the CM7 image + gapps.
So, if you were curious what building a random repo on the web and installing it on your phone would do, then feel free to try and lose all of your data. There are no updates/support for this, etc. It's just a curiosity... what is the state of this stuff right now?
BTW... I am back on CM7/Atrix now which is AWESOME!!!!
Source Code Links:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Click to expand...
Click to collapse
Thinks for your works,
Come from Chinese thinks!
i shall say this.. if this is behind where the dev team actually is...things are looking good! and btw.. i believe fruitcaker maker works. installed and is now creating;]
edit: yep. it does.
Thanks man very very good work android congratulations for share work whith comunity
Sent from my MB860 using xda premium
it looks very nice but id needs a bit more work to be a experimental daily driver.
ps: to solve the corrupt backup problem just copy the files to your computer before flashing and copy to your phone before restoring.
good luck!
where can I get google apps for this rom? Tryed gapps for CM7 from CM wiki - fail, setup wizard crashes.
try the one on this link
http://rootzwiki.com/topic/11854-romcm9-encounterics-x-beta-2-with-working-radio-401/
good luck!
---------- Post added at 07:52 AM ---------- Previous post was at 07:47 AM ----------
ilya11g said:
where can I get google apps for this rom? Tryed gapps for CM7 from CM wiki - fail, setup wizard crashes.
Click to expand...
Click to collapse
try the one on this link
http://rootzwiki.com/topic/11854-rom...ing-radio-401/
good luck!
For a preview build it looks pretty nice. Surprisingly stable for what it is. Definitely keeping an eye on this, especially since the code is out there to make DIY kangs with.
samcripp said:
The one been worked on by turl is with him, that is not for public release.
Dont forget to tell him merry xmas!
Click to expand...
Click to collapse
Random SamCripp memory....
"We're rapping them, we're rapping them!!!"
Sorry, guess you had to be there.... aahhh memories... nevermind, sorry for the off topic post.
Thanks though for the effort of getting this ported btw.
Hi,
Here is CM-11 (Android 4.4.4) for the kindle fire hdx 7" (THOR). You need a rooted hdx 7" (Thor) device with a firmware < 3.2.4 (3.2.3.2 ideally) and a signed recovery.
Todo
Bluetooth not working
Wifi won't correctly load when disabled at boot, a reboot is required
Minimal headphone volume too loud -> fixed
Incorrect color format in some scenario's ? (YouTube) -> fixed
Changelogs/Downloads
cm-11-20150226-UNOFFICIAL-thor.zip
Updated to amazon 4.5.3 binaries
Fully disable radio for now (thanks Andy-Voigt)
Fix twrp fstab (enabling twrp was breaking system rom to boot)
CM sources updated to 20150226
cm-11-20150219-UNOFFICIAL-thor.zip
CM sources updated to 20150219
cm-11-20150219-UNOFFICIAL-thor.zip
fix minimal video/media volume too high (youtube...)
switch back to tablet build
CM sources updated to 20150110
cm-11-20150108-UNOFFICIAL-thor.zip
Fix thermal engine (should give better battery life and performances)
Fix a lot of proprietary services (proprietary logs, acdb-loader, ril loading ...)
Set media volume steps to 100 instead 15 (allow finer volume control essentially for jack output)
Lowered minimal screen brightness
CM sources updated to 20150108
cm-11-20150107-UNOFFICIAL-thor.zip
Build without "hacks" (add Cuber signing and custom updater-script generation)
CM sources updated to 20150107
Enable telephony (will probably not work)
cm-11-20150101-UNOFFICIAL-thor.zip
use patched boot/recovery, thanks to @vortox
fix wrong color format ! (major bug resolved)
switch to kernel sources
cm-11-20141218-UNOFFICIAL-thor.zip
minors fixes
cm-11-20141217-UNOFFICIAL-thor.zip
fix wifi not reloading
fix overlay/rotation screen tearing
cm-11-20141216-UNOFFICIAL-thor.zip
updated binaries to amz 4.5.2
properly use precompiled kernel and headers (amz 4.5.2)
fix minimal audio volume too high
add safestrap compatibility
Sources
android_device_amazon_thor
android_device_amazon_hdx-common
hardware_qcom_display-caf-hdx
hardware_qcom_audio-caf-hdx
hardware_qcom_media-caf-hdx
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
r3pwn said:
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
Click to expand...
Click to collapse
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Cpasjuste said:
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Click to expand...
Click to collapse
While i am sorry you are upset, it was not a slight at you at all. While i do try to keep an eye on XDA while at work, my job does come first and foremost, and i was unable to handle anything here yesterday (what can i say, 12 hour work days suck). As it was, i have literally nothing against you; to be frank, the report on the thread was the first i had even seen.
From my perspective, we had a placeholder thread, which is not allowed, so it was closed. I fully intended to reopen it, but gave my reasons above...
Anyway, i do wish you luck, and i really dont have any ill will to you...
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
tuanda82 said:
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
Click to expand...
Click to collapse
Nobody knows. But there are a few people working on "unlocks" (at least booting an unsigned kernel). Maybe also jcase releases his unlock (which I doubt because of legal issues).
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
URBANsUNITED said:
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
Click to expand...
Click to collapse
You need to be on 4.5.2 and rooted.
cyablo said:
You need to be on 4.5.2 and rooted.
Click to expand...
Click to collapse
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
URBANsUNITED said:
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
Click to expand...
Click to collapse
There are a few Users which do have an unlocked Bootloader, this Rom is only for these Users, as stated in the first Post.
I decided to make the rom available in case i loose interest in this device (or if i ever die soon). This way when (if) a root exploit is available then you'll be ready to use it.
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
openWeb74 said:
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
Click to expand...
Click to collapse
Sharing hundreds of hours of work is helpless/useless for you ?
You know what ? I actually spent the whole day on porting cm-10 to current exploitable kernel for YOU :/
Everybody chill , @openWeb74, i see your point @Cpasjuste , first let me thank you for all your work, I'm pretty sure its a great Rom!
What openweb said was that maybe we should concentrate our efforts in unlocking the bootloader so even greater support can come.
Unfortunately we, the rest of us common mortals (with locked bootloaders) cannot use it.
As you said, this would work if somebody would release the bootloader-unlock , so lets play the waiting game...
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
I really have to say sorry, if you dont know how to reproduce the hack... Mea culpa. It sounded like the hack is known, but cant be made public because of copyright issues or something like that... Then we have to wait. Nothing is secure when the right person gets a hdx... I have to say, that my actual hdx was rooted with towelroot, even easier than the nexus (less button combinations ) so i didnt expect amazon to be such a **** with newer firmwares.
Sent from my LG-D802 using XDA Free mobile app
Cpasjuste said:
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
Click to expand...
Click to collapse
Sorry for nagging you about it, but — genuinely asking — how did you do it on your device in the first place?
dear Cpasjuste, thanks for your great work, and how to install this Rom ? I am newbie, so..
OK... So you are a newbie in reading too?
Sent from my Nexus HDX 7 using XDA Free mobile app
I may eventually move to another tablet as I'm loosing interest in this device (because cm is working fine [emoji14]). Would someone be interested to get my device (not for free )?
Warning: Use this on you Own Risk
Features:
S2W D2W
Stereo Call Record
GPU Tweak
NO Write Protection for System Partition
AWB LCD Custom Color for .Rec 709 Profile
Few little Code Changes
How to:
Load boot.img into fastboot folder
run this command:
"fastboot boot thedreamer-Desire510-64bit.img"
When the Device Boot UP and is Stable
Flash the boot.img with:
"Fastboot flash boot thedreamer-Desire510-64bit.img
Download:
http://forum.xda-developers.com/devdb/project/?id=8179#downloads
Source:
GitHub
I Give no Support i make this Kernels Only for me and post it for other 64bit MSM8919 User to Use.
I Integrate only my Wishes
XDA:DevDB Information
TheDreamer, Kernel for the HTC Desire 510
Contributors
Thestealth2, thestealth2, RBHeromax
Source Code: https://github.com/thestealth131205/HTC_Desire_510_64bit
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2015-02-10
Created 2015-02-10
Last Updated 2015-02-10
I'd love to try it. Is there a link to download it please?
Burtrum57 said:
I'd love to try it. Is there a link to download it please?
Click to expand...
Click to collapse
thanks for the source it coould prove useful in compiling a custom rom for the 64bit i may have to re sync the cm11 repo and give it a shot..
could you also provide a link to the boot.img so we dont have compile the kernel lol.. cheers..
excuse me if i sound stupid,but what is "AWB LCD Custom Color for .Rec 709 Profile" actually? is it actual modified screen colors or is it just the custom kcal driver?
Kcal driver. For Rec. 709 Calibration. My display is calibrated with a Colorimeter.
Download is in First Post
Sent from my HTC Desire 510 using XDA Free mobile app
Thestealth2 said:
Kcal driver. For Rec. 709 Calibration. My display is calibrated with a Colorimeter.
Download is in First Post
Sent from my HTC Desire 510 using XDA Free mobile app
Click to expand...
Click to collapse
do you remember which file you modified for the calibration? i would like to apply it to my kernel,i dont wanna bug you :silly:
See source and merge with youre source
Thestealth2 said:
See source and merge with youre source
Click to expand...
Click to collapse
i build for the 32bit,i cant merge a 3.10 kernel with a 3.4 one :silly:
I write you next days a pn. Have no time at the moment.
You can push a 64 bit stock kernel to git an the push my source than can you see all changes. ?
Just a question...
Exactly which toolchain you use to compile??
I'm about ready to flash your kernel - thestealth131205 I'll update after i get my flash on.
Thestealth2 said:
Features:
NO Write Protection for System Partition
AWB LCD Custom Color for .Rec 709 Profile
Few little Code Changes
Download:
http://www.dhm-server.de/thedreamer-Desire510-64bit.img
Source:
GitHub
Click to expand...
Click to collapse
Thank you for your kernel, have been using it for a month (on my EU) and it works very well!
However, could you make some progress please...
As it is seen on this forum your work is the only one for 64bit. So, could you consider some suggestions?
Namely in their 32 verisons of modded kernels developpers write here about improving screen touch responsiveness and removing HTC's backdoor "debugging" access... How about it?
download link unavailable
See first Post
RE: THEDREAMER 64 bit
Thestealth2 said:
See first Post
Click to expand...
Click to collapse
Last I touched base/read with you and RBHEROMAX, if I understood correctly, you were going to be changing something so I've been trying to remain patient and wanted to inquire about this. I picked up a Samsung Galaxy S5 Sport (sprint) all stock to entertain myself with. LOL. I have the utmost respect for you and Rbheromax, I'd like to thank you again for your dedication and time put into this project and the respect and patience you give to everyone that asks you questions on any level. You are very special individuals giving the gift of knowledge to all that seek it.
All that came together to make the 64 bit HTC Desire 510 project. All that came to the rescue to make THEDREAMER possible. You are pioneers and not afraid of a challenge. I don't know if you have any sort of recognition for everyone that takes the time and puts fourth the effort to share the GIFT OF KNOWLEDGE. If not, I'd like to declare Tuesday, March 31, 2015 programmers appreciation day! And you both deserve the GOLDEN THUMBS UP AWARD just because I appreciate your patience, and you caring enough to share knowledge with individuals that otherwise wouldn't have the opportunity to delve into this field.
THANK YOU!
Hopefully I'm not breaking any rules by speaking up. But I. Believe it's time for some recognition with a simple shout out saying THANKS, YOU MADE A DIFFERENCE IN MY LIFE.
paying it forward....
:highfive:
Should the kernel name be "3.10.28-g36bd0f8-dirty (root @ speedstarlap)" after installing?
I'm trying to enable S2W and can't seem to get it working, was wondering if the kernel installed right, or if there were other versions - you said you have MSM8919, whereas my 510 shows up as MSM8916- a typo or actually different chips? (if possible, could you please tell me how to enable S2W if the kernel installed right?)
@edit - Managed to get it... "working" - if I lock the screen and swipe to right and left near the menu buttons within 2-3 seconds from locking, it works. otherwise it doesn't. D2W is fully dead though. I'll poke around it a bit more and see if I can get it to work properly...
Hi, which gcc are u using? and how to compile the dt.img?
I compiled a kernel for D820, only with stock dt.img could bootup. It boots into bootloader if I use the dt.img which I compiled from stock kernel source.
could u help me?
Kernel works great and great improvement in speeds! Thanks
I've a problem. Sometimes the touchscreen doesn't react after waking up my phone. But the volume up and down and the power button work.
Can this be because of the kernel? I don't know. Please help.
Lonely_Boz said:
I've a problem. Sometimes the touchscreen doesn't react after waking up my phone. But the volume up and down and the power button work.
Can this be because of the kernel? I don't know. Please help.
Click to expand...
Click to collapse
I have the exact same problem I have to restart my device for screen to be back in action
Make this pretty later
You just made my day
Sent from my Nexus 6
I just confused myself. Should i be flashing the bootloader, radio, etc from a nexus factory image and then flash omni? I have been using 20150605 build without doing this. Should i do this for the nightlies?
subterfugium said:
Code:
I:operation_start: 'Flashing'
Installing '/sdcard/Download/omni-5.1.1-20150623-shamu-NIGHTLY.zip'...
Checking for MD5 file...
MD5 matched
Verifying zip signature...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
I:comment is 1477 bytes; signature 1459 bytes from end
I:failed to verify against RSA key 0
E:failed to verify whole-file signature
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/Download/omni-5.1.1-20150623-shamu-NIGHTLY.zip'
I guess zip verification fails because of test-keys or what does that zip verification stand for?
Click to expand...
Click to collapse
Honestly, I've never used zip verification for all the years I've been flashing ROMs and have never had any issues.
I'm probably wrong but.. My theory is that packed somewhere inside the zip you are trying to flash lies a key, which is compared next a second key once extracted. If they don't match it throws an error and aborts the operation.
Sent from my Nexus 6 using XDA Free mobile app
I've never used zip verification for this exact reason, and therefore have never looked into it. This sounds like something for the TWRP thread that @Dees_Troy could answer maybe.
Does anyone have a rundown of what this Rom has to offer beyond stock aosp? The Rom OP is a bit bare of info. Thanks
The Rom OP is a bit bare of info. Thanks
530farm said:
Does anyone have a rundown of what this Rom has to offer beyond stock aosp? The Rom OP is a bit bare of info. Thanks
Click to expand...
Click to collapse
Off the top of my head... battery icon customization, volume match orientation, volume wake, screenshot delete, advanced reboot menu, hide usb debugging icon, ambient display customization. Also, Omni is the only AOSP ROM where I don't get force closes when taking multiple HDR+ pictures in a row without pause.
Completely stable device functionality with whatever you see on gerrit :good:
I will make a "features list" tomorrow
I saw that the past few builds uploaded were all 0mb. Just wondering what's going on until the builds resume?
Gandalf said:
Completely stable device functionality with whatever you see on gerrit :good:
I will make a "features list" tomorrow
Click to expand...
Click to collapse
Not sure if feature requests are allowed or not, if not then just ignore this..
But I was wondering if the 5 second home button delay on app launchers (such as Swipepad) is something that may be removed? That'd make navigating the phone much quicker for those of us who do use app launchers.
I saw opendelta mentioned in the main thread but I haven't seen any indication it exists within the ROM. Am I just missing it?
Ngo93 said:
Not sure if feature requests are allowed or not, if not then just ignore this..
But I was wondering if the 5 second home button delay on app launchers (such as Swipepad) is something that may be removed? That'd make navigating the phone much quicker for those of us who do use app launchers.
Click to expand...
Click to collapse
jira.omnirom.org :good:
glockliberty said:
I saw opendelta mentioned in the main thread but I haven't seen any indication it exists within the ROM. Am I just missing it?
Click to expand...
Click to collapse
Updates to opendelta have not been merged yet
I am certainly interested in giving OmniRom a try. A couple of questions...
First, I'm attempting to download the Omni 5.1.1 20150725 Nightly (newest as of this writing) and the download is going exceptionally slow (20-30KB/s) on the official dl.omnirom.org mirror. Is there an issue with the server at current or an up to date mirror?
Next, is there an overall feature list for Omni (on Nexus 6)? Many ROMs place a list of their main features as well as any other ROMs/kernels they incorporate (ie based on CyanogenMod 12.1, with latest CM12.1 commits added on every update etc..)).
Thank you!
RanceJustice said:
I am certainly interested in giving OmniRom a try. A couple of questions...
First, I'm attempting to download the Omni 5.1.1 20150725 Nightly (newest as of this writing) and the download is going exceptionally slow (20-30KB/s) on the official dl.omnirom.org mirror. Is there an issue with the server at current or an up to date mirror?
Next, is there an overall feature list for Omni (on Nexus 6)? Many ROMs place a list of their main features as well as any other ROMs/kernels they incorporate (ie based on CyanogenMod 12.1, with latest CM12.1 commits added on every update etc..)).
Thank you!
Click to expand...
Click to collapse
The server is probably being slow. They just upgraded storage/cleaned it up a few days ago and it has been significantly faster, it might be your connection to the server or something else.
As far as a list of features, there isn't one to my knowledge but you can certainly check on gerrit to see what's been merged recently. Just flash it and see for yourself: highfive:
Does this rom have layers?
Omnirom 5.1.1 nightly sudden reboot+supersu freeze+bluetooth headset bugs
I installed Omnirom 3days ago and have to say; nice stuff. runs fluid, batterie's fine and overall i like user experience. BUT
I'm experiencing some bugs.
first of all sometimes there just are random sudden reboots. On stock rom this happened from time to time when battery was below 30% or something so i thought there has to be a powersaving feature or something in kernel that don't works correct.
Then i flashed TWRP+Omnirom and those sudden reboots started happening randomly; regardless of battery.
I googled and found that could be some setting that adapt display brightness(???) and/or some apps bugging/conflicting. and, from previous experience, i know that this could also be a hardware/battery failure(please not; can't send my phone back right now as i need it daily for work and my N5 has a broken touch )
i tried disabling that display feature and also installed and tested if 'Lux' has any impact on that as it, basically, does the same but no change.
i factory reseted my device multiple times and tried to find out what APP could force this but... right now there's only the bare minimum(contacts+ / messages+ / aquamail / maildroid / todoist /calengoo /business calender pro and google stock apps)and still same problem. sometimes even while calling what's very embarassing when having an important customer on phone ...
I gonna try Zen Kernel next just to see if different kernel with different cpu scheduler COULD make any difference.
Then the second bug is my bluetooth headset(Plantronics M165). Can't get it to pair. Before Omnirom this worked very well as it should. Now, most of time he finds nothing and sometimes he finds a mac address of the headset but not the name. Other bluetooth devices are working fine and the headset's still working perfectly well on my gf's HTC M8. Anyone any ideas?
Last bug i experienced is SuperSU. Always an app needs root i can't get SuperSU intercept my choice. I click on allow or deny but nothing happens and after 10seconds superSu autodenies(or allows; depends on settings )right after factory reset supersu just works fine but suddenly stops working. root's still there as i can perfectly tell supersu what to do in its settings. Only the on demand root question can't be answered. uninstalling/reinstalling supersu didn't change anything. It doesn't matter if i install supersu by playstore or by zip through recovery. also unrooting and rerooting doesn't help. only a factory reset helps; for a while.
I don't want to change my Superuser managment as i paid for the pro version ...
Hope to find some help here as it's one of my fav places for everything smartphone related since back in my tytn days
so much knowledge in here.
keep up the good work
update:
sudden Reboot Problem solved, Same for superSu Problem.
just the Bluetooth problem's still there. flashing back to Stock resolves the issue but... stock and I really start liking omnirom...
anyone any ideas ?
Sent from my Nexus 6 using XDA Free mobile app
nightfly.0684 said:
update:
sudden Reboot Problem solved, Same for superSu Problem.
just the Bluetooth problem's still there. flashing back to Stock resolves the issue but... stock and I really start liking omnirom...
anyone any ideas ?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
M builds will be ready soon enough :good:
great news
Do we get the Update for M through opendelta or is a factory reset + reflash needed?
and if i understand right you assume that the Bluetooth Problem should be gone with M?
would be nice as, right now, I sometimes have to pick up important calls while driving ... and... i don't like that at all....
would try the homemade M build IF i wouldn't need it daily for work. about time to repair my n5 i guess
Sent from my Nexus 6 using XDA Free mobile app
Hi all:
This is a thread for my alternative LineageOS 14.1 roms for suzuran.
I'm building these roms from time to time for my own needs and I think other people should participate.
Since the "official" development of LineageOS 14.1 has been stopped, I decided to build a new version only if the Android security patch level has been changed or I've changed anything.
Download 2021-07-19
This is a 7z archive with the zip'ed rom and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable zip verification and md5sum checking. Maybe you have to rename the md5 file to *.md5sum; depending on the TWRP version you are using.
Kernel sources
Tree sources
Features:
OS Version: 7.1.2 Nougat
Kernel: Linux 3.10
New: Android security patch level: 5 June 2021
Using sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom roms.
Required for installation: TWRP 3.1.1 (or newer).
OR use my self built TWRP-version 3.5.2!
No need for making a clean install, but sometimes it helps a lot!
This rom is pre-rooted. For those who want to use magisk or any other rooting tool, you can easily remove this by flashing this file.
Use this rom at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this rom in any way.
Differences between my version and the "official" one:
Kcal Display Driver - Thanks to @GreyLeshy and @Sony user 16
Voltage Control - Thanks to @GreyLeshy and @Sony user 16
OMS-Support - Thanks to @nathanchance
Added F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've included some little extensions like changelog and volume adjustment.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've increased all volume steps from 7 to 15.
I've changed the microfone gain to avoid echo in phone calls.
I've enabled data for MMS.
I've enabled MHL.
Not working:
VoLTE, VoWiFi
If you want to use encryption, you have to disable SIM PIN first!
One (last) request: Please don't ask for including any app. I won't do this, because I want to keep this rom as clean as possible.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
Nice
Berni-0815 said:
Hi @all:
First of all, please excuse my bad english... :angel:
They said I should create my own thread for my alternative LineageOS 14.1 roms for suzuran. Here it is.
I'm building these roms from time to time for my own needs and I think other people should participate.
Download
Kernel sources
Tree sources
OS Version: 7.1.2 Nougat
Kernel: Linux 3.10
Required for installation: TWRP 3.1.1
Important informations:
You should be familiar with general installation of alternative roms.
I've included some little extensions like changelog and volume adjustment.
There is no need to make a clean install, but sometimes it helps a lot!
Use it at your own risk!
Click to expand...
Click to collapse
Hi ! It would be great if u put out the advantage of yours vs with the official LOS
Berni i said before and i m saying again please make this topic a lineage based rom..
İnclude minimal app for google play store.
And maybe can add substratum inside.. or can be a default diffefent theme ..
I believe you can..
Thx bro.
ROBNX85 said:
Hi ! It would be great if u put out the advantage of yours vs with the official LOS
Click to expand...
Click to collapse
As I wrote: "I've included some little extensions like changelog and volume adjustment."
emosis said:
İnclude minimal app for google play store.
Click to expand...
Click to collapse
As I said a few days before: I don't want to include gapps! If somebody wants to use gapps, feel free to flash them separately. You can download them here. You need arm64 and 7.1 for suzuran.
And maybe can add substratum inside..
Click to expand...
Click to collapse
Substratum support is not longer available, because the devs have stopped their development for Nougat since august.
Berni-0815 said:
As I wrote: "I've included some little extensions like changelog and volume adjustment."
Click to expand...
Click to collapse
Add a basic ad-blocker too ?
Berni-0815 said:
As I said a few days before: I don't want to include gapps! If somebody wants to use gapps, feel free to flash them separately. You can download them here. You need arm64 and 7.1 for suzuran.
...
Click to expand...
Click to collapse
I agree gapps should not be included. It is easy enough to just flash it right after flashing the rom
I am thinking about official vs rom, I think the two roms are probably nearly identical. Probably the most important factor will be the frequency of updates.
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
You can use AdAway which is an open source host list based ad blocker. See https://adaway.org
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
I don't see a reason to bake something into the ROM when there are many apps that can do it.
I think something like Xposed-type tweaks being put into settings would be more appropriate. Alleviating the need for xposed. But I don't think it makes sense to load random apps into the ROM.
New version; please have a look at the first post
Berni-0815 said:
New version; please have a look at the first post
Click to expand...
Click to collapse
Awesome work, thank you so much! Flashing it now.
Just 1 question - do you know if encryption works on your builds?
I've never tried it. I've not so good experience with encryption on a stock rom; so I've decided not to use this feature at all!
Hi Bernhard.
Thanks for your hard work!
i have a question for you.... As i understand it you take all the changes/updates from the offifcial lienage and implement them into your own build. And add the changes as described in post 1.
Am i right about this?
I think that battery life is bad on the official compaired to the version you do.
Do you add battery improvements in your build?
Thanks in advance.
Torben 5247
torben5247 said:
Thanks for your hard work!
Click to expand...
Click to collapse
Oh, it is not so hard to do this, but, thank you! Sometimes I have to search a few hours or try (and revert) something, but in the end I've gotten everything to work as I like it to work.
As i understand it you take all the changes/updates from the offifcial lienage and implement them into your own build.
Click to expand...
Click to collapse
I'm using the LineageOS repositories from github as they are, that's right. I don't use my own repo's; nzzane is doing this AFAIK (Klick). A few weeks ago I'm using other repo's, because LineageOS had bad (will say: not working) sources for our devices.
And add the changes as described in post 1.
Am i right about this?
Click to expand...
Click to collapse
Yes! :good: One or two of my changes should be implemented into the "official" builds, but until now I don't understand how to use "commitments". Maybe in a few days... :angel:
I think that battery life is bad on the official compaired to the version you do.
Do you add battery improvements in your build?
Click to expand...
Click to collapse
No. Nothing like this.
On my own device battery life is about three days...
Hi,
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
emosis said:
İnclude minimal app for google play store.
And maybe can add substratum inside..
Click to expand...
Click to collapse
Like other persons, I don't want to have a lot of applications include in the rom. I want to choose the ones I use. This is one reason that made me come to alternative rom.
Another reason is that Lineage use less google s"hit" than stock rom.
So if you have the vision of more app and google stuff include, you better stay on stock. Alternative Roms offers me more freedom; but that's just my opinion...
This is prerooted? There are some of us out there that need to install certain apps before rooting.
Cerhio said:
This is prerooted?
Click to expand...
Click to collapse
Yes.
Berni-0815 said:
One or two of my changes should be implemented into the "official" builds, but until now I don't understand how to use "commitments".
Click to expand...
Click to collapse
I've just committed three of my changes. We'll see if they will be merged...
Berni-0815 said:
I've just committed three of my changes. We'll see if they will be merged...
Click to expand...
Click to collapse
The brightness settings? I hope so
What else?
Berni-0815 said:
I've just committed three of my changes. We'll see if they will be merged...
Click to expand...
Click to collapse
That's so great to hear, let's hope they get accepted.
Huge thank you for keeping this device alive Berni!