{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lost Kernel for Poco F1
Features:
Compiled using GCC 9.1.0
Latest Linux-stable version (4.9.181)
Latest CAF tag (LA.UM.7.3.r1-07800-sdm845.0)
Touchscreen firmware from 9.1.24
Simple low memory killer
Dynamic stune boost
Dsboost
Tick rate of 100Hz
Anxiety IO Scheduler
Optimzied Beryllium EAS profile
Disabled Debugging features
Disabled Audit
Disabled ZRAM
Disabled CRC check
Disabled Gentle Fair Sleepers
Disabled Useless governors (powersave,ondemand..)
Klapse V5.0
Vibration control
KCAL color control
Backlight min option
Sound control
Boeffla wakelock blocker
F2fs support
Fsync on/off support
Use sync pulses for panels
TCP improvements
Bunch of Peformance and Battery improvements
Saturation set by default to 270 (Keep Colors Vibrant and Accurate!)
Enabled RCU boost for better RT performance
Enabled third party controllers support..like xbox
AnyKernel3 flashable zip
Compatibility
Custom roms
MIUI Pie
Download
https://github.com/LogicLost/beryllium/releases
Telegram group
t.me/lostkernelberyllium
Support
If you apperciate my work and want to help me stay awake click here to buy me a coffee
Credits
The Linux Foundation, CodeAurora.
All beryllium developers.
All others who have their commits or contributions picked.
Source Code:
https://github.com/LogicLost/beryllium
Reserved Post
Good To See Another Developer Keep It Up Bro We Will Support You as You are Spending your Valuable Time For Us.
Olystem said:
Good To See Another Developer Keep It Up Bro We Will Support You as You are Spending your Valuable Time For Us.
Click to expand...
Click to collapse
Thanks[emoji38]
Sent from Lost Coast using Tapatalk
Wow thanks you very much for this! Let's try! ?
thanks for the hard work ...
is there controller support? specifically dualshock 4...
AliNT77 said:
thanks for the hard work ...
is there controller support? specifically dualshock 4...
Click to expand...
Click to collapse
Will add support in the next release.
Sent from Lost Coast using Tapatalk
awesome...
Good job thanks a lot for the new kernel
Some of you reported me random freeze issue,i will work on rebase over ALS base with minimal import of xiaomi changes
Sent from Lost Coast using Tapatalk
LogicLost said:
Some of you reported me random freeze issue,i will work on rebase over ALS base with minimal import of xiaomi changes
Sent from Lost Coast using Tapatalk
Click to expand...
Click to collapse
Bro most of Fts_ts touch panel users have been suffering since day one from this God damn issue which seems to miui team as some sort of a rocket science, i have been suffering from ghost touches / touch freezes, flashed all vendor/firmware versions, No go, flashed most kernels also a no go, flashed different ROMs still no working out , using global kernel from miui minimizes this trash but doesnt radically solve it, tried some codes on the build prop still not working, am just gonna forget that I own a stupid poco cuz it turned onto a flashing mess rather than a functioning phone, oh well a functioning phone when it comes down to touch screen at least.
droidjunky90 said:
Bro most of Fts_ts touch panel users have been suffering since day one from this God damn issue which seems to miui team as some sort of a rocket science, i have been suffering from ghost touches / touch freezes, flashed all vendor/firmware versions, No go, flashed most kernels also a no go, flashed different ROMs still no working out , using global kernel from miui minimizes this trash but doesnt radically solve it, tried some codes on the build prop still not working, am just gonna forget that I own a stupid poco cuz it turned onto a flashing mess rather than a functioning phone, oh well a functioning phone when it comes down to touch screen at least.
Click to expand...
Click to collapse
If modifying software clearly doesn't help, why not send the device to Xiaomi to have them fix it?
TheReduxPL said:
If modifying software clearly doesn't help, why not send the device to Xiaomi to have them fix it?
Click to expand...
Click to collapse
This is ongoing for many users bro, the fix should be in a software as to them it isn't hardware related matter.
droidjunky90 said:
This is ongoing for many users bro, the fix should be in a software as to them it isn't hardware related matter.
Click to expand...
Click to collapse
If it's related to software, then why some users (like you) experience issues regardless of vendor, ROM and kernel, while other users with the same touch screen (like me) do not experience any?
My Poco F1 also has a Fts_ts touch screen and I'm yet to notice any issues at all regardless of software, as the issues were not present on factory ROM+vendor, updated MIUI and vendor, and any other custom ROM I've tried so far.
To me it's clearly not a software issue, so if it's not a hardware issue, then what is it?
TheReduxPL said:
If it's related to software, then why some users (like you) experience issues regardless of vendor, ROM and kernel, while other users with the same touch screen (like me) do not experience any?
My Poco F1 also has a Fts_ts touch screen and I'm yet to notice any issues at all regardless of software, as the issues were not present on factory ROM+vendor, updated MIUI and vendor, and any other custom ROM I've tried so far.
To me it's clearly not a software issue, so if it's not a hardware issue, then what is it?
Click to expand...
Click to collapse
Exactly it must be hardware issue, but xiaomi isn't admitting that and they are saying the fix will be pushed soon and we have been hearing this pushed soon BS since stone age, your Fts_ts must be from a new batch bro.
droidjunky90 said:
Exactly it must be hardware issue, but xiaomi isn't admitting that and they are saying the fix will be pushed soon and we have been hearing this pushed soon BS since stone age, your Fts_ts must be from a new batch bro.
Click to expand...
Click to collapse
Mine is from December 2018 according to the box. Doesn't sound like the latest batch to me, or is it?
TheReduxPL said:
Mine is from December 2018 according to the box. Doesn't sound like the latest batch to me, or is it?
Click to expand...
Click to collapse
Mine is dated October 2018 and is FTS.
But it may be dependent on region too or other factors?
Edit: sorry meant NVT not FTS!
dalyer said:
Mine is dated October 2018 and is FTS.
But it may be dependent on region too or other factors?
Click to expand...
Click to collapse
Yes that's highly possible, I got mine from Canada since am Canadian lol, and that's too unfortunate for me.
---------- Post added at 04:19 PM ---------- Previous post was at 04:18 PM ----------
TheReduxPL said:
Mine is from December 2018 according to the box. Doesn't sound like the latest batch to me, or is it?
Click to expand...
Click to collapse
+1 I think Dalyer is right that its region related.
droidjunky90 said:
Yes that's highly possible, I got mine from Canada since am Canadian lol, and that's too unfortunate for me.
Click to expand...
Click to collapse
I'm in Ireland but bought from Ali Express/China.
Note that I made a mistake in my original post and said FTS when I meant NVT! :silly:
dalyer said:
I'm in Ireland but bought from Ali Express/China.
Click to expand...
Click to collapse
Wise move mate, don't they sell it at local stores in Ireland?
---------- Post added at 04:23 PM ---------- Previous post was at 04:20 PM ----------
dalyer said:
I'm in Ireland but bought from Ali Express/China.
Note that I made a mistake in my original post and said FTS when I meant NVT! :silly:
Click to expand...
Click to collapse
Ohh then u r one of the lucky ones bro, but even if you had an Fts_ts rubbish, u can always tell Thomas Shelby about it and he will get your device replaced by order of the peaky blinders ay? Lol
Related
Well, i heard people complain about gpl license breaking (you have all the rights of this world) and for missing kernel's source. Now i'm here for report (sorry for my awful english ) the word of Hugo Ibarra that confirm the release of MI3 source later this year. And i like to add that xiaomi already release source for mi2 and mi2s.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(if isn't a fake screen)
kekkojoker90 said:
Well, i heard people complain about gpl license breaking (you have all the rights of this world) and for missing kernel's source. Now i'm here for report (sorry for my awful english ) the word of Hugo Ibarra that confirm the release of MI3 source later this year. And i like to add that xiaomi already release source for mi2 and mi2s.
(if isn't a fake screen)
Click to expand...
Click to collapse
Which is complete BS. They have to release it upon device release. This is why this forum was made. To help call them out and to Rip MIUI apart.
zelendel said:
Which is complete BS. They have to release it upon device release. This is why this forum was made. To help call them out and to Rip MIUI apart.
Click to expand...
Click to collapse
lol, that's exactly why I wasn't willing to buy this device.
There are already plenty of threads on miui forums complaining about lack of kernel source.
Before the launch of this device in India, I was almost convinced to buy Moto G by my fellow members from galaxy y section.
But the specs were too good to ignore given the same price group.
When I saw that reply, this came out of my mouth:
hey, better late than never.
It's simply disheartening to see that a device as powerful as this being forced to use sole miui rom(or its cooked version).
I haven't tried cm11, but from what i've heard, people are loving it.
One of the developers(varun chhitre) of cm11 for this device has prior experience dealing with micromax(another non compliant oem).
If/When kernel sources get out, I hope this device gets developer support.
CharsiBabu said:
lol, that's exactly why I wasn't willing to buy this device.
There are already plenty of threads on miui forums complaining about lack of kernel source.
Before the launch of this device in India, I was almost convinced to buy Moto G by my fellow members from galaxy y section.
But the specs were too good to ignore given the same price group.
When I saw that reply, this came out of my mouth:hey, better late than never.It's simply disheartening to see that a device as powerful as this being forced to use sole miui rom(or its cooked version).
I haven't tried cm11, but from what i've heard, people are loving it.
One of the developers(varun chhitre) of cm11 for this device has prior experience dealing with micromax(another non compliant oem).
If/When kernel sources get out, I hope this device gets developer support.
Click to expand...
Click to collapse
Ill be honest. Dont count on it. Most Devs have a very big hate for them and no matter how good the hardware is will not touch the device until it comes clean.
Oh he and I know each other well from my attempts to help with the Micromax issue.
Better late than never. Still they hardly have cared about gpl. Releasing sources, after they release new device.
Sent from my C1904 using XDA Free mobile app
zelendel said:
Ill be honest. Dont count on it. Most Devs have a very big hate for them and no matter how good the hardware is will not touch the device until it comes clean.
Oh he and I know each other well from my attempts to help with the Micromax issue.
Click to expand...
Click to collapse
Yeah , good step by xda but i don't have any Hope that they will release kernel source and even if they do , it will be some bunch of crap to stop user's from spamming there customer support for kernel source .
They already broke privacy of many user's by stealing data .
try signing this it might help
www.change.org/en-IN/petitions/xiao...pt&utm_medium=email&utm_source=share_petition
kekkojoker90 said:
Well, i heard people complain about gpl license breaking (you have all the rights of this world) and for missing kernel's source. Now i'm here for report (sorry for my awful english ) the word of Hugo Ibarra that confirm the release of MI3 source later this year. And i like to add that xiaomi already release source for mi2 and mi2s.
(if isn't a fake screen)
Click to expand...
Click to collapse
Screenshot looks like fake to me, from interface it looks like Facebook but he have different FB DP.
Well u know that we all can change the dp
Anyways, just hope it comes true
Sent from MI3 using Tapatalk
Where is the screenshot come from ? Link required.
Hope it's true.
Check this link.
http://disqus.com/hugobarra/
@varun.chitre15 how did you made the kernel source of mi 3.From where did you get the sources
kernel source code.
Also check this https://github.com/mi3-dev found this but of no use for me, I am no dev, spread this please if it's of any help.
I trust hugo barra and they will release it by december
Shahan_mik3 said:
I trust hugo barra and they will release it by december
Click to expand...
Click to collapse
Its uploaded by varun.chitre15 the guy who made cm11 for mi 3.
thejoker said:
Its uploaded by varun.chitre15 the guy who made cm11 for mi 3.
Click to expand...
Click to collapse
What is uploaded?
Shahan_mik3 said:
What is uploaded?
Click to expand...
Click to collapse
The kernel source,ofcourse
thejoker said:
The kernel source,ofcourse
Click to expand...
Click to collapse
Nope....kernel sources are not released....he compiled a ROM without the sources.
Shahan_mik3 said:
Nope....kernel sources are not released....he compiled a ROM without the sources.
Click to expand...
Click to collapse
So we cant make for example Paranoid Android from this sources????
thejoker said:
So we cant make for example Paranoid Android from this sources????
Click to expand...
Click to collapse
Yes we can....and there are already slimkat and mokee open source.
And carbon ready to be tested and omni under development
So, some people here are having no luck with the fingerprint scanner on CM13 roms. Does anyone know if there's going to be a fix coming? What would be required for it to be fixed?
DAZTR411 said:
So, some people here are having no luck with the fingerprint scanner on CM13 roms. Does anyone know if there's going to be a fix coming? What would be required for it to be fixed?
Click to expand...
Click to collapse
People are busy tinkering with ROMs/Kernels. Add this, remove that. And it seems no one care about the new batch of XRN3Pro with different FP/LCD hardware.
Those people need helps... CC: @TheStrix @Umang96 @ktomov @banmeifyouwant @warmachine_28 etc...
Sent from my Xiaomi Redmi Note 3 using XDA Labs
I'll see if I can contact Goodix and Xiaomi and get the firmware required. If I were, what should I ask for?
MOVZX said:
People are busy tinkering with ROMs/Kernels. Add this, remove that. And it seems no one care about the new batch of XRN3Pro with different FP/LCD hardware.
Those people need helps... CC: @TheStrix @Umang96 @ktomov @banmeifyouwant @warmachine_28 etc...
Sent from my Xiaomi Redmi Note 3 using XDA Labs
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
People are busy tinkering with ROMs/Kernels. Add this, remove that. And it seems no one care about the new batch of XRN3Pro with different FP/LCD hardware.
Those people need helps... CC: @TheStrix @Umang96 @ktomov @banmeifyouwant @warmachine_28 etc...
Sent from my Xiaomi Redmi Note 3 using XDA Labs
Click to expand...
Click to collapse
DAZTR411 said:
I'll see if I can contact Goodix and Xiaomi and get the firmware required. If I were, what should I ask for?
Click to expand...
Click to collapse
Ask for kernel source/driver + proper documentation.
Sent from my Xiaomi Redmi Note 3 using XDA Labs
MOVZX said:
People are busy tinkering with ROMs/Kernels. Add this, remove that. And it seems no one care about the new batch of XRN3Pro with different FP/LCD hardware.
Those people need helps... CC: @TheStrix @Umang96 @ktomov @banmeifyouwant @warmachine_28 etc...
Sent from my Xiaomi Redmi Note 3 using XDA Labs
Click to expand...
Click to collapse
Not that I don't care, but this is complete arseholenes out of Xiaomi. They've made one device with thousand different parts. Different camera sensors, different fingerprint sensors, different touchscreen digitizers, different batteries.
It's their job to update their kernel source with appropriate drivers and documentation. What will happen in two months time, when they decide that they can get even cheaper parts? Fiasco once again. Furthermore I can't and I wont do any experiments on devices that I don't poses.
DAZTR411 said:
So, some people here are having no luck with the fingerprint scanner on CM13 roms. Does anyone know if there's going to be a fix coming? What would be required for it to be fixed?
Click to expand...
Click to collapse
ktomov said:
Not that I don't care, but this is complete arseholenes out of Xiaomi. They've made one device with thousand different parts. Different camera sensors, different fingerprint sensors, different touchscreen digitizers, different batteries.
It's their job to update their kernel source with appropriate drivers and documentation. What will happen in two months time, when they decide that they can get even cheaper parts? Fiasco once again. Furthermore I can't and I wont do any experiments on devices that I don't poses.
Click to expand...
Click to collapse
@DAZTR411 For that reason mate, there is still no clues for those XRN3Pro phones with new hardware since the kernel source Xiaomi gave to us is INCOMPLETE.
Luckily I have FPC on my phone.
It's kinda bad that xiaomi did this. Even though they gave us an incomplete source, they changed some hardware and didn't even update. Bad move, btw I am one of the goodix fp owner and that's the only different piece on my RN3P. (thank god)
It would be good if any dev tried to test with these different hardwares..
Well the phone continues to be a beast with or without fp, no regrets.
And thanks for the custom kernels ????
Is there any way to know what fp sensor I have on my device?
Hubaqu said:
It's kinda bad that xiaomi did this. Even though they gave us an incomplete source, they changed some hardware and didn't even update. Bad move, btw I am one of the goodix fp owner and that's the only different piece on my RN3P. (thank god)
It would be good if any dev tried to test with these different hardwares..
Well the phone continues to be a beast with or without fp, no regrets.
And thanks for the custom kernels ????
Click to expand...
Click to collapse
What other different components are there and what do they effect?
DAZTR411 said:
What other different components are there and what do they effect?
Click to expand...
Click to collapse
Fp, Touchscreen display and battery.
For some, me included, the fp doesn't appear in the settings. The touchscreen dt2w doesn't work in atmel one only on focaltech. And for the battery some report the battery stats get stuck at 50% or - 2%.
Hubaqu said:
Fp, Touchscreen display and battery.
For some, me included, the fp doesn't appear in the settings. The touchscreen dt2w doesn't work in atmel one only on focaltech. And for the battery some report the battery stats get stuck at 50% or - 2%.
Click to expand...
Click to collapse
Oh hey, I have the battery problem too (which I fixed thankfully), really wish I knew about this stuff, not like you can really test for it before you buy I guess.
DAZTR411 said:
Oh hey, I have the battery problem too (which I fixed thankfully), really wish I knew about this stuff, not like you can really test for it before you buy I guess.
Click to expand...
Click to collapse
Can I ask what you did to fix it? So far the only solutions I've found are to use Mokee or an older build of RR.
I just got a new RMN3P to replace my one with a broken screen and it has the goodix, I didn't even know it existed until now. The only rom I can get it working with is the very latest Global developer from a couple of days ago.
Can I swap the motherboard from my broken screen one to the new one? I'm really loving RR on my broken screen one and would love to get it going on the new one with fingerprint.
How to know the goodix fp is used in RN3SD
GNVM said:
How to know the goodix fp is used in RN3SD
Click to expand...
Click to collapse
Go to /data/ folder, if you see a folder called "goofix"...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enviado de meu Redmi Note 3 usando Tapatalk
In build.prop the persist.sys.fp.goodix=0
does that means goodix fp is not used?
felipegcoutinho said:
Go to /data/ folder, if you see a folder called "goofix"...
Enviado de meu Redmi Note 3 usando Tapatalk
Click to expand...
Click to collapse
In build.prop the persist.sys.fp.goodix=0
does that means goodix fp is not used?
Can you please tell, that if I've goodix, will i be able to make use of Finger Print sensor with cm13?
---------- Post added at 09:54 AM ---------- Previous post was at 09:54 AM ----------
felipegcoutinho said:
Go to /data/ folder, if you see a folder called "goofix"...
Enviado de meu Redmi Note 3 usando Tapatalk
Click to expand...
Click to collapse
Can you please tell, that if I've goodix, will i be able to make use of Finger Print sensor with cm13?
geekychandu said:
Can you please tell, that if I've goodix, will i be able to make use of Finger Print sensor with cm13?
---------- Post added at 09:54 AM ---------- Previous post was at 09:54 AM ----------
Can you please tell, that if I've goodix, will i be able to make use of Finger Print sensor with cm13?
Click to expand...
Click to collapse
With a patch, yes.
felipegcoutinho said:
With a patch, yes.
Click to expand...
Click to collapse
What is that patch?? Name please??
NOTE:
Just a suggestion people:
ZTE Germany Forums have announced that English is now allowed on their forums but the support is primarly aimed at Germans but they understand it is the only European board.
You can voice all your complaints there and they will see it first hand!
http://www.ztemobile.de/forums/
Full b10 ROM image:
http://www.ztedevice.com/support/detail?id=6A7CC886AFBA47299EAB1D14CC9091F2
Please check guys!
Its started rolling out in Germany and UK via FOTA!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks, just started the download
Changelogtranslated:
1. New setting for showing or hiding new notifications on the lock screen.
2. Camera, File manager, Contacts, Browser, Video and Gallery app optimizations.
3. Translation fixes.
4. More performance and stability fixes
rikin93 said:
Please check guys!
Its started rolling out in Germany via FOTA!
Full post rom as soon as available.
Click to expand...
Click to collapse
Is this ROM compatible with the rest of the 2017G phones or is intended only for Germany?, because for example, in Spain they have a B09 which other countries don't have.
Galaxo60 said:
Is this ROM compatible with the rest of the 2017G phones or is intended only for Germany?, because for example, in Spain they have a B09 which other countries don't have.
Click to expand...
Click to collapse
It is compatible.
rikin93 said:
It is compatible.
Click to expand...
Click to collapse
Thanks for answer, too bad we couldn't get Nougat on January, but let's hope the developers can wipe out the most bugs they can.
Every OEM has been having troubles with the Nougat update, even Google with the Nexus phones, and some of them have even rolled back globally the whole update after some days of release it.
I just hope to get a stable nice update, no matter if it take a couple of weeks later.
Thanks for all the information!
:fingers-crossed:
The lockscreen notification expansion is fixed. Yeah!
No other changes found..
Keiler90 said:
The lockscreen notification expansion is fixed. Yeah!
No other changes found..
Click to expand...
Click to collapse
Has the audio output via headphones increased in volume?
rikin93 said:
Has the audio output via headphones increased in volume?
Click to expand...
Click to collapse
Sorry, never used headphones with this phone..
Keiler90 said:
The lockscreen notification expansion is fixed. Yeah!
No other changes found..
Click to expand...
Click to collapse
That's really really great news.
Just got the notification for the update.
I'm downloading.
Sent from my iPad using Tapatalk
wtf where is the nougat update though ? and can someone post some pictures after the camera update
CampfireVibés said:
wtf where is the nougat update though ? and can someone post some pictures after the camera update
Click to expand...
Click to collapse
It is still undergoing beta testing, I assume you would like a bugfree version right? Then be patient!
Can someone pull the ROM or take a logcat to see the link - thnx !
adb logcat > A2017GB10.txt
do it BEFORE ota update
I can confirm they fix the broken lock screen.
Now it's just like before B08 that broke that.
Good job by ZTE.
Hope next month for as much bug free Nougat upgrade.
Sent from my iPad using Tapatalk
paatha13 said:
I can confirm they fix the broken lock screen.
Now it's just like before B08 that broke that.
Good job by ZTE.
Hope next month for as much bug free Nougat upgrade.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Check if the audio is louder!
rikin93 said:
It is still undergoing beta testing, I assume you would like a bugfree version right? Then be patient!
Click to expand...
Click to collapse
Exactly...
PS : Have you got some recent news about the nougat version ?
Nougat coming in Feb, its chinese new year the devs on their holidays, they wanted to get b10 out asap so you guys stop complaining!
Not yet available in Belgium
Still on B08
rikin93 said:
Nougat coming in Feb, its chinese new year the devs on their holidays, they wanted to get b10 out asap so you guys stop complaining!
Click to expand...
Click to collapse
Stop complaining? Why? I can understand you, but If they announce it several times and don't deliver something...is it not their own fault? Just saying...no hate. :angel:
Keiler90 said:
The lockscreen notification expansion is fixed. Yeah!
No other changes found..
Click to expand...
Click to collapse
paatha13 said:
I can confirm they fix the broken lock screen.
Now it's just like before B08 that broke that.
Good job by ZTE.
Hope next month for as much bug free Nougat upgrade.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Can you explain more about this?, I don't see how the lock screen was broken or buggy, I haven't had any problem yet with it and I'm still on B08.
Maybe something I haven't noticed yet?.
Galaxo60 said:
Can you explain more about this?, I don't see how the lock screen was broken or buggy, I haven't had any problem yet with it and I'm still on B08.
Maybe something I haven't noticed yet?.
Click to expand...
Click to collapse
When you get notification and pull it down, it should stay down, however it goes to the top of the screen and small.
This is fixed in B10.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MOD EDIT: LINKS REMOVED DUE TO GPL-NONCOMPLIANCE
**Snapdragon™ is a registered trademark owned by Qualcomm Technologies Inc.
**OnePlus™** is a registered trademark owned by Shenzhen Oneplus Science & Technology Co., Ltd.
**(v5)Xceed Logo™ is created by @kentexcitebot
XDA:DevDB Information
Xceed Custom Kernel, Kernel for the OnePlus 5T
Contributors
kairi_zeroblade
Source Code: https://gitlab.com/zeroblade1984/Oneplus-MSM8998
Kernel Special Features: Stable!!
Version Information
Status: Stable
Current Stable Version: Production build 2
Stable Release Date: 2018-06-30
Created 2018-06-09
Last Updated 2018-07-15
Reserved
Reserved
Oh sorry didn't mention.
Rommco05 said:
Hi, page for | CREDITS | DISCLAIMER | DOWNLOADS | FEATURES | FAQ is down, giving 404 error. Just let u know nice to see new kernel. Thanks
Click to expand...
Click to collapse
Kernel will release tomorrow
Oh man, went to download... Not tomorrow ?
Very excited to see this kernel pop up for 5T. Hoping download link appears soon..
Rommco05 said:
Hi, page for | CREDITS | DISCLAIMER | DOWNLOADS | FEATURES | FAQ is down, giving 404 error. Just let u know nice to see new kernel. Thanks
Click to expand...
Click to collapse
yung40oz84 said:
Oh man, went to download... Not tomorrow
Click to expand...
Click to collapse
crashazz3 said:
Very excited to see this kernel pop up for 5T. Hoping download link appears soon..
Click to expand...
Click to collapse
Can you check now?? my bad..lol
Enjoy 2.64ghz OC on the perf cluster..
kairi_zeroblade said:
Can you check now?? my bad..lol
Enjoy 2.64ghz OC on the perf cluster..
Click to expand...
Click to collapse
Thank you so much! Used to use your kernel back when I had OP3T and was just an xda lurker
Curious to see what made the initial release as far as features. Flashing now...
Would u say focus on performance or battery life or both ???
crashazz3 said:
Thank you so much! Used to use your kernel back when I had OP3T and was just an xda lurker
Curious to see what made the initial release as far as features. Flashing now...
Click to expand...
Click to collapse
Be sure to take note of the reminder on the download section before flashing and Thank you!!
Jamie_oppo said:
Would u say focus on performance or battery life or both ??
Click to expand...
Click to collapse
Xceed does not focus on anything the project aims to be just simple, stable and easy to use (Flash and Forget principle) but there's always surprises..
EDIT: we're looking for an active TG crew who can run tests with me, if you feel you're qualified and up to the task then you can PM @ilia1985 for more information about it
Appears to be a good kernel for anyone looking for a flash-and-forget performance oriented kernel. Doesn't have a whole lot of options to fulfill my tweaking addition, but this kernel is not meant for loads of options anyways.
First impressions look pretty good, kernel is extremely responsive, and apps appear to open faster compared to stock kernel (probably due to OC freqs). However I'm noticing my CPU hitting max frequencies & sticking there while playing Train Conductor World, even while idling on the "map". Flashed back to stock kernel to compare and stock kernel does NOT exhibit this behavior.
@kairi bro good to see you here..hope you remember me from Xiaomi mi3 days..you can always count on me..I will try the kernel and let you know the feedback .
crashazz3 said:
Appears to be a good kernel for anyone looking for a flash-and-forget performance oriented kernel. Doesn't have a whole lot of options to fulfill my tweaking addition, but this kernel is not meant for loads of options anyways.
First impressions look pretty good, kernel is extremely responsive, and apps appear to open faster compared to stock kernel (probably due to OC freqs). However I'm noticing my CPU hitting max frequencies & sticking there while playing Train Conductor World, even while idling on the "map". Flashed back to stock kernel to compare and stock kernel does NOT exhibit this behavior.
Click to expand...
Click to collapse
comments are always welcome...
But I do hope, before your wrote this up, you could have almost seen a reply from almost every dev here that you can't compare the stock kernel to to almost every kernel (custom), why is that so?? if you have tracked down the commit history it was evident that the Oneplus QOS framework together with some hooks have been removed, furthermore, the shipped opchain module with the source is a bit nit-picky to build, that module controls/moderates frequency behavior..
praveen7682 said:
@kairi bro good to see you here..hope you remember me from Xiaomi mi3 days..you can always count on me..I will try the kernel and let you know the feedback .
Click to expand...
Click to collapse
Glad I can be of service to you here...and happy to see some old patrons!! enjoy the ride..
Finally, the best kernel for OP3 is here for the 5t. Been waiting for this kernel since I bought the phone. Thank you!
Thank you for giving us the best kernel using it since OP3 and i confirm this is the fastest kernel do some benchmark tests you will understand why
Jole7 said:
Thank you for giving us the best kernel using it since OP3 and i confirm this is the fastest kernel do some benchmark tests you will understand why
Click to expand...
Click to collapse
+1
Sent from my Pixel 2 XL using XDA Labs
Jole7 said:
Thank you for giving us the best kernel using it since OP3 and i confirm this is the fastest kernel do some benchmark tests you will understand why
Click to expand...
Click to collapse
Benchmark says nothing lmao
BlazingKahn35 said:
Benchmark says nothing lmao
Click to expand...
Click to collapse
Said no OEM ever and what every jealous wannabe says....
And yet for every new phone 1 of the 1st things that leak are benchmarks... Benchmarks are one of deciding factors when buying choosing a phone. It may not say much about real world performance or UI fluidity but bench marks are a measuring tool which help tune/refine software/hardware and your comment above only shows your ignorance.
Sent from my OnePlus ONEPLUS A6003 using XDA Labs
Would this work on OnePlus 5?
If not will you be releasing an OP5 version?
Your work has always been fantastic.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Your scientists were so preoccupied with whether or not they could, they didn’t stop to think if they should"
--That Dinosaur Movie With The UNIX System
WHAT DO WORK:
-Everything except what I list below
-Maybe it's just me but when I flash Nano Gapps, GO Oreo seems a bit faster than normal Oreo. Not by a whole lot but by a noticeable amount
WHAT DONT WORK:
-Encryption, it will fail but I'm working with the tree maintainer to try and fix this
-Camera, it doesnt ship with a camera app and when you get one like OpenCamera it says another app is using the camera. Looking at a logcat it looks like something called a lowmemkiller keeps killing the camera process when I try to start it (?)
-Magisk/SuperSU, Magisk will never show up and SuperSU will put you in a bootloop
-GPS, it sorta works but can be a bit spotty at times, use that app called Fix GPS on the Play Store to help with this
-MS Exchange, if you use Outlook it will take a while and maybe a few reboots before your contacts sync to the Android contacts app, I have no idea why it does this but it did eventually work for me
DOWNLOAD LINK:
my vision is augmented
As normal with ROMs, while I will try to help you with a problem, I take no responsibility for damaged devices or anything like that, you assume full responsibility when you flash custom things like this
WHERES MY DANG SOURCE CODE:
Sync up normally with Lineage 15.1 sources, and use this here for all of your device trees. To make GO android you have to go to the device's device.mk file and add the following line:
$(call inherit-product, build/target/product/go_defaults.mk)
THANKS TO:
-Me, because I'm the best
-Subhrajyoti Sen, he not only showed me how to compile for GO but also is working real hard behind the scenes to try and fix all the Oreo tree related problems. He's a great guy and good at what he does
-@facuarmo for showing me this one patch that can potentially fix the camera crap that's going on
Not sure what else I'll be using this post for, so here's the logcat that shows what happens when the camera can't open
jasonmerc said:
Not sure what else I'll be using this post for, so here's the logcat that shows what happens when the camera can't open
Click to expand...
Click to collapse
Maybe you can try applying this patch if it isn't yet? It looks like there's a need for a commit to be applied in order to get this thing working and thus your memory leakage and LMK constant triggering, it's because of a LMK part being disabled after GO is enabled.
You should take a look at this one: https://github.com/aosp-mirror/platform_system_core/commit/fe26dfb3bf347d801e4ef2803e1ffa3c924a851b and check if your source has it.
Good lucko buckaroo hope you get this goo!
Also don't forget to keep it up with the hard work iukwim.
EDIT: Oh and the camera holder just doesn't connect so maybe you're mixing incompatible device trees and the camera blobs aren't playing well there?
facuarmo said:
Maybe you can try applying this patch if it isn't yet? It looks like there's a need for a commit to be applied in order to get this thing working and thus your memory leakage and LMK constant triggering, it's because of a LMK part being disabled after GO is enabled.
You should take a look at this one: https://github.com/aosp-mirror/platform_system_core/commit/fe26dfb3bf347d801e4ef2803e1ffa3c924a851b and check if your source has it.
Good lucko buckaroo hope you get this goo!
Also don't forget to keep it up with the hard work iukwim.
EDIT: Oh and the camera holder just doesn't connect so maybe you're mixing incompatible device trees and the camera blobs aren't playing well there?
Click to expand...
Click to collapse
I don't think my sources have that, so I'll be applying that soon when I build again. If I need to edit the device trees in any way I'll just end up making a new branch of it and call it lineage-15.1-go, so look out for that if it happens. All my sources are based on the same Oreo trees Subhrajyoti uses to build all of his Oreo based ROMs, so I don't think sources are getting messed up either. I actually spoke to him about this and he thinks the LMK is what's killing the camera, not the blobs (since after all, those same blobs work fine in normal Lineage)
Believe me, the HARD work was not forgotten. This is merely training, a stepping stone for something BIGGER AND BETTER in the future when the time comes.
jasonmerc said:
I don't think my sources have that, so I'll be applying that soon when I build again. If I need to edit the device trees in any way I'll just end up making a new branch of it and call it lineage-15.1-go, so look out for that if it happens. All my sources are based on the same Oreo trees Subhrajyoti uses to build all of his Oreo based ROMs, so I don't think sources are getting messed up either. I actually spoke to him about this and he thinks the LMK is what's killing the camera, not the blobs (since after all, those same blobs work fine in normal Lineage)
Believe me, the HARD work was not forgotten. This is merely training, a stepping stone for something BIGGER AND BETTER in the future when the time comes.
Click to expand...
Click to collapse
Sure, try it out. By the way, have you tried building normal Lineage with those sources before going for Oreo Go? I mean, maybe there's something wrong with Lineage bleeding branch iself. If so, my best advice would be to apply the commit I just posted, build again and try your luck in the camera and lag thingy.
As always, make this something big, cause the bigger, the better.
PS.: I'm talking about the Facebook app you sick heads.
facuarmo said:
Sure, try it out. By the way, have you tried building normal Lineage with those sources before going for Oreo. I mean, maybe there's something wrong with Lineage bleeding branch iself. If so, my best advice would be to apply the commit I just posted, build again and try your luck in the camera and lag thingy.
As always, make this something big, cause the bigger, the better.
PS.: I'm talking about the Facebook app you sick heads.
Click to expand...
Click to collapse
Subby just made a lineage build with the sources so I think the sources are fine, its just a problem with GO LMK. I'll be applying those patches now
Oh by the way, on an unrelated note, your nougat SomeFeaK and all others based on it now break the camera in nougat ROMs. I'm not sure what changed but something did...
jasonmerc said:
Subby just made a lineage build with the sources so I think the sources are fine, its just a problem with GO LMK. I'll be applying those patches now
Oh by the way, on an unrelated note, your nougat SomeFeaK and all others based on it now break the camera in nougat ROMs. I'm not sure what changed but something did...
Click to expand...
Click to collapse
I mean, you should make a build straight from your sources and your environment, because that'll let you see if your build passes as a normal one and if your sources, being based on the bleeding branch, aren't somehow broken.
About the other topic, well, I don't maintain SomeFeaK anymore, cause of time and cause it was kinda hard. I really thought Aki was going to implement his HybridX thing on Nougat, surprisingly, he didn't. I somehow understand him, I mean, Nougat is pretty outdated already, it's visually the same thing as any other Android release. Instead, Oreo, has that PiP thing, tons of otpimization and wow... it's fascinating, at least to me, it's very important. Anyways, I was planning to implement HybridX on Nougat by myself but you know how my "plans" work, I might take a mid year to finally get my hands on it. I promise that, today, I'll start taking a look at it, as it seems to be a pretty simple thing.
@facuarmo where am I even supposed to put that updated lmkd file you sent me, I don't see a platform folder in the lineage 15.1 sources to look through. There's a platform_testing but then within that there's no system subdirectory
jasonmerc said:
@facuarmo where am I even supposed to put that updated lmkd file you sent me, I don't see a platform folder in the lineage 15.1 sources to look through. There's a platform_testing but then within that there's no system subdirectory
Click to expand...
Click to collapse
See los manifest
https://github.com/LineageOS/android_system_core
I'd like to try the ROM but I'm the one that uses root on every phone I bought and I use the camera a lot.
Great work for the ROM :good:
Mixterix Se7en said:
I'd like to try the ROM but I'm the one that uses root on every phone I bought and I use the camera a lot.
Great work for the ROM :good:
Click to expand...
Click to collapse
I also root every phone & I don't use camera a lot but going to install this just for testing the Android Go.
Downlink not working
All working , good battery life ?
---------- Post added at 06:32 PM ---------- Previous post was at 06:32 PM ----------
Oronno Chy said:
Downlink not working
Click to expand...
Click to collapse
Off link