Database Users

Best rom with Sense 3.5?

Hy,i search the best rom with HTC sense 3.5
There is a rom with the dormianx kernel and app2SD?
Now i use a CM7.2 rom with the dorimanx kernel and it's very fast and have a great battery use. So i search something like this but with HTC sense
If someone can help me i'm very gratful

Try coredroid the battery is gr8 also the speed ;-)

I would suggest Team Blue DROID rom

If version 7.9 is stable with the lockscreen I would say MwakiousRUNNINGrom.
LOVED that rom, specially version 3.0 but now I am looking for a Rom that has Tweaks (RCMix3D Tweaks) and Beats Audio.
the MwakiousRUNNINGrom has this, but is so unstable in the lockscreen, sometimes it works and sometimes not.
I'm using the Sense 3.5 rom from Team Blue Droid at the moment (Beats won't work ), but when MwakiousRUNNINGrom 7.9 is out I really will give it a try (again....)

Vinny1994 said:
If version 7.9 is stable with the lockscreen I would say MwakiousRUNNINGrom.
LOVED that rom, specially version 3.0 but now I am looking for a Rom that has Tweaks (RCMix3D Tweaks) and Beats Audio.
the MwakiousRUNNINGrom has this, but is so unstable in the lockscreen, sometimes it works and sometimes not.
I'm using the Sense 3.5 rom from Team Blue Droid at the moment (Beats won't work ), but when MwakiousRUNNINGrom 7.9 is out I really will give it a try (again....)
Click to expand...
Click to collapse
beats audio doesnt work on any rom unless you have beats audio headphones
its all a figmant of imagination that beats audio will work on the hd2

@Kameirus (yeah I pressed quick reply instead of quote lol)
Guess it will never really work on the HTC HD2 because it doesn't have the hardware for it.
But, I do hear a sound difference on the rom "SENSATION XL V 3.0 stock ALL IN ONE" by haldric with my friend's Beats Solo headphone.
Yes, I also think thats really weird.

Vinny1994 said:
@Kameirus (yeah I pressed quick reply instead of quote lol)
Guess it will never really work on the HTC HD2 because it doesn't have the hardware for it.
But, I do hear a sound difference on the rom "SENSATION XL V 3.0 stock ALL IN ONE" by haldric with my friend's Beats Solo headphone.
Yes, I also think thats really weird.
Click to expand...
Click to collapse
excatly you hear the difference with beats headphones
not the stock headphones or phone speaker
thats why it was removed from the TBD roms
not many of us can afford 200 dollar headphones lol

team blue droid, IMHO
all work but not without some bugs, ... but this is the best =) thanks to creators
I've been using it since I saw sens ROM

Kameirus said:
excatly you hear the difference with beats headphones
not the stock headphones or phone speaker
thats why it was removed from the TBD roms
not many of us can afford 200 dollar headphones lol
Click to expand...
Click to collapse
Haha, I lolled at that last line
I am also looking for a Sense with Tweaks + Beats because I want to buy a "Beats by Dr. Dre Beats Pro" for my girlfriend's birthday.
But ofcourse if the Beats Audio does not work it doesn't make sense to get her this headphone.
The only thing that made music sound better trough my stock headphones is Volume + (Sound Boost) the payed version.

thanks to all I'm trying the team blue v3.4 but for me it have to much bugs i think i will return to my old cm7.2
But if will be corrct all the most important bugs I will be happy to give an other chance at team blue's rom

Ansem said:
thanks to all I'm trying the team blue v3.4 but for me it have to much bugs i think i will return to my old cm7.2
But if will be corrct all the most important bugs I will be happy to give an other chance at team blue's rom
Click to expand...
Click to collapse
and what bugs would they be

my feedback on TBD 3.4
Hi,
some feedback I have on the TBD ROM:
* overall acceptable experience, but not bug free
* still have to reboot about once a day, system freezes from time to time
* had to set settings/power/sleep mode to off. Otherwise the phone seems to loose the settings/wireless&networks/Mobile networks/always-on mobile data setting.
* had to switch off facebook live updates. Serious battery hog.
* had to set settings/power/power mode to normal. Economy mode seems to freeze the phone when battery level is too low, and prevent restarting.
(very weird bug: did not want to start with battery X which ran down the day before, but did so with battery Y. Still, both batteries had about the same charge level. Had to push reset to get the phone starting with battery X. And yes, tested both with 10 sec off battery interval, so reset should not have been needed)
* it does not want to sync mail overnight, even with the correct settings in setting/accounts&sync on the individual accounts, and sleep mode off.
* SMS delivery notifications do not work: settings keep coming back to 'off'. Think I've seen it working once, but no more.
* built-in wifi and USB tethering do not work. wifi tethering beacon info does not publish WPA (and therefore makes it impossible to connect) and above that, it makes the phone crash when enabled for the 2nd time in a row. USB tethering keeps saying it is unable to activate. Using Barnacle now (which also complains about wpa).
* android rants, very probably not TBD related:
* calendar notifications in the notification bar do not disappear when read from the calendar directly. I now have to acknowledge meetings twice.
* tasks and notes do not sync seamlessly. Too many apps involved, too many flavours, too many clicks/taps. (using MyPhoneExplorer for the moment)
Not business ready.
overall impression of this android version compared to WM:
+: better apps, web sites with flash, better on line experience. side by side agendas.
-: slower, more bugs, less battery life, more hussle
But hey, I still stick with it after 4 days, so it's no too bad. Will try a faster SD card, to see how it behaves then.
(Using stock TBD 3.4 in NAND, latest CLK, class 4 SD card, from fresh clean latest WM official rom )

hansboot020 said:
Hi,
some feedback I have on the TBD ROM:
* overall acceptable experience, but not bug free
* still have to reboot about once a day, system freezes from time to time
* had to set settings/power/sleep mode to off. Otherwise the phone seems to loose the settings/wireless&networks/Mobile networks/always-on mobile data setting.
* had to switch off facebook live updates. Serious battery hog.
* had to set settings/power/power mode to normal. Economy mode seems to freeze the phone when battery level is too low, and prevent restarting.
(very weird bug: did not want to start with battery X which ran down the day before, but did so with battery Y. Still, both batteries had about the same charge level. Had to push reset to get the phone starting with battery X. And yes, tested both with 10 sec off battery interval, so reset should not have been needed)
* it does not want to sync mail overnight, even with the correct settings in setting/accounts&sync on the individual accounts, and sleep mode off.
* SMS delivery notifications do not work: settings keep coming back to 'off'. Think I've seen it working once, but no more.
* built-in wifi and USB tethering do not work. wifi tethering beacon info does not publish WPA (and therefore makes it impossible to connect) and above that, it makes the phone crash when enabled for the 2nd time in a row. USB tethering keeps saying it is unable to activate. Using Barnacle now (which also complains about wpa).
* android rants, very probably not TBD related:
* calendar notifications in the notification bar do not disappear when read from the calendar directly. I now have to acknowledge meetings twice.
* tasks and notes do not sync seamlessly. Too many apps involved, too many flavours, too many clicks/taps. (using MyPhoneExplorer for the moment)
Not business ready.
overall impression of this android version compared to WM:
+: better apps, web sites with flash, better on line experience. side by side agendas.
-: slower, more bugs, less battery life, more hussle
But hey, I still stick with it after 4 days, so it's no too bad. Will try a faster SD card, to see how it behaves then.
(Using stock TBD 3.4 in NAND, latest CLK, class 4 SD card, from fresh clean latest WM official rom )
Click to expand...
Click to collapse
Don't waste your money on a new SD card if you don't already have one, it shouldn't make any difference to your experience. If necessary, move all of your heavily used apps to internal storage, this will make them less buggy and more responsive, and will allow them to load much faster on boot.

APN error for SFR (France)
Hi,
just to let you know, the built in APN definitions are wrong for SFR (France) in TBD 3.4:
APN 'full internet'/sl2sfr should have 'APN type' set to 'default' and not 'default,hipri'.
Otherwise 3G/3G+ won't turn on, and negotiation at data connection start will take longer. Being stuck to Edge and GPRS is a bit of a shame...

hansboot020 said:
Hi,
some feedback I have on the TBD ROM:
* overall acceptable experience, but not bug free
* still have to reboot about once a day, system freezes from time to time
* had to set settings/power/sleep mode to off. Otherwise the phone seems to loose the settings/wireless&networks/Mobile networks/always-on mobile data setting.
* had to switch off facebook live updates. Serious battery hog.
* had to set settings/power/power mode to normal. Economy mode seems to freeze the phone when battery level is too low, and prevent restarting.
(very weird bug: did not want to start with battery X which ran down the day before, but did so with battery Y. Still, both batteries had about the same charge level. Had to push reset to get the phone starting with battery X. And yes, tested both with 10 sec off battery interval, so reset should not have been needed)
* it does not want to sync mail overnight, even with the correct settings in setting/accounts&sync on the individual accounts, and sleep mode off.
* SMS delivery notifications do not work: settings keep coming back to 'off'. Think I've seen it working once, but no more.
* built-in wifi and USB tethering do not work. wifi tethering beacon info does not publish WPA (and therefore makes it impossible to connect) and above that, it makes the phone crash when enabled for the 2nd time in a row. USB tethering keeps saying it is unable to activate. Using Barnacle now (which also complains about wpa).
* android rants, very probably not TBD related:
* calendar notifications in the notification bar do not disappear when read from the calendar directly. I now have to acknowledge meetings twice.
* tasks and notes do not sync seamlessly. Too many apps involved, too many flavours, too many clicks/taps. (using MyPhoneExplorer for the moment)
Not business ready.
overall impression of this android version compared to WM:
+: better apps, web sites with flash, better on line experience. side by side agendas.
-: slower, more bugs, less battery life, more hussle
But hey, I still stick with it after 4 days, so it's no too bad. Will try a faster SD card, to see how it behaves then.
(Using stock TBD 3.4 in NAND, latest CLK, class 4 SD card, from fresh clean latest WM official rom )
Click to expand...
Click to collapse
Nice information u have there, i just completed download the TBD v3.5 and looking for review... Thank god i read this thread.... Anyway thanks
Sent from my mighty HTC HD2

[KERNEL PATCH] Force AC (fast) Charging

This was a pretty big hit with the gnex and nexus s guys so I figure that I would extend it to the aries series phones:
This is for kernel devs only. The patch itself is useless to those who do not/can not compile their own kernel.
This patch allows one to force AC charging for any charger that is detected as USB (e.g. many car chargers) and pull the full current the charger can support. It also provides additional security when connecting to public charging stations because by forcing AC charging, USB/adb data transfers are disabled, protecting your data.
Fast charge can be toggled by issuing:
echo 1 > /sys/kernel/fast_charge/force_fast_charge
and off:
echo 0 > /sys/kernel/fast_charge/force_fast_charge
Some roms (AOKP) have also implemented toggles.
In addition I have created a toggle fast charge widget that may be used to toggle fast charge on and off right from your home screen:
https://play.google.com/store/apps/details?id=com.incredicontrol.fastchargewidget
For the widget (or any fast charge toggle) to work, you MUST be running a kernel that has this patch implemented.
As a good gesture to support a fellow dev, I ask that if you implement the patch into your kernel, please link to my widget as one means to toggle it. You are of course free to provide other ways to toggle it as well if you so desire.
Kernel devs, if you would like to test the widget yourself to confirm its working, and for convenience of testing, please contact me and I will provide you with a copy. You must show that you are a kernel dev though (i.e. link me to your kernel post so I can match your username).
Here you go. Good luck have fun:
http://www.incredikernel.com/wp-con...download.php?id=aries_force_fast_charge.patch

Thanks! I hope our kernel guys pay attention.

This has already been done with a hardware mod... Thanks though

b-eock said:
This has already been done with a hardware mod... Thanks though
Click to expand...
Click to collapse
Hardware mod is not the same as software mod...
Hopefully Semaphore will get this soon! But I think stratosk said he won't implement this.

bravomail said:
Thanks! I hope our kernel guys pay attention.
Click to expand...
Click to collapse
AOKP is already setup for any kernel that supports it. rom control > Performance > Fast Charge.
Half way there... LOL

Tk-Glitch has us testing a BigMEM and Fast charge kernel all in one

[Q] What dash installation ROM?

Currently running timurs rom but it crashes a lot. Are there other roms that allow fast charge, sleep/wake with power, on screen volume etc.
Any help greatly appreciated

adamsilver1987 said:
Currently running timurs rom but it crashes a lot. Are there other roms that allow fast charge, sleep/wake with power, on screen volume etc.
Any help greatly appreciated
Click to expand...
Click to collapse
I've been running Timur's ROM as well and I really want an alternative as well as I've been facing issues with the ROM, and it looks like Timur has discontinued development on the 2012 model.
From what I've seen so far though CM11 should support USB DACs so I'm keen to try that out.
Some notes:
Fast charge - that's a kernel setting so any custom kernel should allow that.
Sleep/Wake on power - After many months of usage, sleep or even firm sleep has been a hit or miss for me. When it works, it works really well but sometimes a some random app might cause a wakelock, draining the battery. Even otherwise, there are many other issues such as USB audio doesn't resume. Plus the battery tends to drains quicker + looses health because of being in a hot car.
So instead, what I'm planning to do, is to just completely shutdown/boot up a tablet on power. Some notes:
- Bootup time is fairly quick - about 30 seconds, upto a minute, which is acceptable for me. You can reduce the startup time even further by using apps like BootManager to prevent unnecessary apps from starting up. Perhaps we can slim down the ROM further by deleting unnecessary apks etc.
- Fresh start is always a better option - you don't want your tablet to crash while driving right? I've had to reboot many times before or during driving, and it annoys me to say the least.
- USB audio always works fine when booted (well, with Timur's ROM anyways, need to test with CM11/others)
- No battery drain due to device standby or wakelocks
- No overheating and loss of battery health
- For shutdown on power loss, we can use Tasker. Maybe make a script to first turn the screen off, and after say 10 minutes of idle turn off the device completely (this will give us a chance to resume quickly in case we stopped the car for some reason).
- For startup on power, we can use the fastboot oem command to make the device automatically power up
On-Screen Volume: From daily usage, this hasn't been very practical in reality. I mean if you're driving, you really shouldn't be looking at the screen and trying to aim at the tiny buttons. Instead, a better option would be to use gestures to control the volume. There are heaps of apps for this, eg: All In One Gestures, Tasker, Gesture Navigation, GMD GestureControl, etc. You could use a single-swipe down and swipe-up to increase the volume up/down. Swipe left/right to change tracks. Two finger swipes to switch between apps. Just use your imagniation.
Might seem like a lot of work initially, but IMHO it'll be worth it, at least to get a stable ROM which is updated regularly (not to mention, you get to use the newest GApps!).
My only concern is to get the DAC working on startup. Might have to look into Timur's startup scripts to see how he does it - maybe even port the FHD scripts over to 2012 if necessary.

do you have a link to any fast charge kernels ? all i can find is Timurs ?
thanks

adamsilver1987 said:
do you have a link to any fast charge kernels ? all i can find is Timurs ?
thanks
Click to expand...
Click to collapse
Kang-aroo kernel.
http://forum.xda-developers.com/showthread.php?t=2558717
Supports fastcharge, OTG, hotplug DAC, firm sleep, multiboot and more.

thanks. this may sounds stupid ( im new to this rooting thing etc ) i am running paranoidandroid ROM. seems to run smoothly. i have flashed/installed that kernel and nothing is different. no extra settings etc? am i doing something wrong ?
thanks again

adamsilver1987 said:
thanks. this may sounds stupid ( im new to this rooting thing etc ) i am running paranoidandroid ROM. seems to run smoothly. i have flashed/installed that kernel and nothing is different. no extra settings etc? am i doing something wrong ?
thanks again
Click to expand...
Click to collapse
Use a kernel tweaking app, like TricksterMod.

ok downloaded that and it means nothing to me im afraid. how would i turn on fast charge for example or OTG host mode, firm sleep etc ?
only thing i can find where i assume you can set things is the " SysCtrl Editor" but it jsut comes up with a huge list of stuff that i have no idea about.
i assume i need to find fast charge in sysctrl and change it from 0 to 1... but cant find anything under the search. not a clue what id be looking for
starting to think Timurs rom was simple compared to this. haha
thanks for the help

Use PowerEventManager:
http://forum.xda-developers.com/showthread.php?p=50265682#post50265682

i saw that, but yet again. dont know how to use it ? where do i place it on the tablet. it doesnt show up in recovery mode

You have to install it. Copy it to your device and then use a file manager to open and install it. It will create an icon in your drawer. When you open it, you'll have options to configure firm-sleep etc.

Done. Worked at first but now I've reverted to timurs rom. The tablet froze loads. Wouldnt open some apps at all and power on/off with ignition wasn't reliable. Sometimes it woke, sometimes it didnt. Will give it another go when i habe more time i think.

On a related note, I haven't had much luck with getting my DAC to work with other ROMs - even with Kang-aroo kernel. I'll have to try CM11 with _crue_'s USB audio patches and Netfluke's kernel this weekend and see how it goes.
Edit: No luck. Maybe because it's I'm on tilapia. Even with cm11, Netfluke's latest kernel, and _crue_'s updated audio patches for cm11, couldn't get it to work. And it's a Fiio E17, which I've had no issues with on Timur's ROM.
And no, I'm not going back to Timur's CM10 - it's old. I can't use any of the newer GApps on it, and the ROM is buggy.
I think I'll swap my tilapia with my 2013 deb and use that as a car device instead. It looks like Timur just updated his kernel to v1.0 which fixes a lot of bugs - at least it's being actively developed. As for my tilapia, I'll switch to a more stable/mainstream ROM like Omni and forget about USB audio for now.

Where did u get timurs updated kernel? Cant find a link

adamsilver1987 said:
Where did u get timurs updated kernel? Cant find a link
Click to expand...
Click to collapse
Oh, you'll have to donate for now, but it should be made public soon.

How much and where?
Thanks

[GUIDE] No Audio Glitches on CM12 based roms by fosseperme

And after correcting the bug audio of Nexus 5 and lags software of LG G3, I return this time with a bugfix against glitches and metallic sounds on music players in CM 12 roms.
The team cyano did a bad job on the kernel of CM12, since it was discovered that the cause of the glitchs was the non use of hotplugg with two cores always active in standby. Even Franco with his kernel solved the problem with the latest release r37, but the kernel has bad performance compared to stock kernel.
With this short guide you can activate the two cores for ever, to eliminate audio glitches on CM12 base roms!
1) Download from playstore the app called "CPU Performance Control Free" of mugich (requires root).
2) Open the app and in profiles select "add new profile" that provides:
Core 0 in "Core always enabled" (Min 300 Max 2457 MHz) and set it as Interactive
Core 1 in "Dynamic core hotplug" (Min 300 Max 2457 MHz)
Core 2 in "Dynamic core hotplug" (Min 300 Max 2457 MHz)
Core 3 in "Core always enabled" (Min 300 Max 2457 MHz) and set it as Conservative (because you can t change this value)
Now save your rule with a name, and after re edit the saved profile and change Core 3 from Conservative to Interactive (now you can change the value, it s a bug of app!); resave the rule.
Now select the profile saved and go in settings and check "apply active profile on boot".
Reboot the phone and enjoy your music glitchs free !!!

Could disable offload for audio in build.prop as an alternative.

I don't like that there is always icon for root access visible.
Sent from my A0001 using XDA Free mobile app

Is this the glitch that sounds like a sample of the audio gets repeated for a fraction of a second when screen is off at random times? I've noticed this with almost every player, only Apollo and the player that comes with CM12 don't have this issue, and it never happens when screen is on.

fards said:
Could disable offload for audio in build.prop as an alternative.
Click to expand...
Click to collapse
That dont remove all the glitches

gonna try this out, thanks!

My question is, why does 2 cores need to be on always to stop audio glitches? It worked fine with one core on kk. Why is it different on lollipop?
Sent from my A0001 using Tapatalk

That's a bit outdated. Not sure when this was done but I see two cores staying online. The CPU cores aren't related. Cyanogen is working on improving audio and getting it to work with nuplayer and enable offloading. There will be issues in the porting process.
Don't compare nightlies of cm12 to a stable near last build of cm11s. That's like apples to oranges. Their builds use hotplugging - mpdecision - not sure where your info is from.

worked for me

Worked for me too. Thank you!!

I cannot set to Min 300 mhz. any issues keeping as it is the default value? thanks

Going to try this .....Thanks for sharing..

In my case the audio shuttering while playing on my car stereo still remains although the duration between them is now long.
Sent from my A0001 using XDA Free mobile app

This seems to help quite a bit but doesnt solve all the issues when using with Bluetooth.
Here's my situation, using todays Nightly and stock CM12 kernel (or any for that matter):
wired headphones - everything works great.
bluetooth with screen on - stutters/laggy/distortion
bluetooth with screen off - everything works great.
I dove a bit deeper and also found this:
Bluetooth with car strereo (Subaru Impreza 2013 Sport Limited) -- stutters like crazy when screen is on.
Bluetooth with stereo headset - works great all the time.
Bluetooth with wireless speaker (Tango TRX) - works great all the time.
Bluetooth with Belkin BT stereo adapter - works great all the time.
So, my current conclusion is that this only has issues when using with my car stereo. This happens to be the only paired device that displays song/artist/album info on display. The others do not have this feature. I also have BT drops when using my car stereo answer phone calls.

danieldmm said:
That dont remove all the glitches
Click to expand...
Click to collapse
I've had this problem on a Galaxy S4 GPE Lollipop ROM, in that ROM's changelog:
-Turn off experimental NuPlayer by default - Should help fix some audio stuttering issues once and for all.
Worked for me. You can change this in developer settings. In my experience it's a combination of kernel issues and this setting.

This actually made things a hell of a lot worse for me!
Before I had pops every couple of seconds, enough to make me stop listening to music and only listen to podcasts and audiobooks.
After following your instructions to a tee I now get some bizarre time-stretching effect on bluetooth: everything gets pitched up with tons of audio 'holes' to make up for the contraction of the sound. Just tried to listen to Simon Mayo interview Colin Firth - it was like listening to Pinky and Perky MCing over breakcore.
I wonder if audio is ever going to work on lollipop on this damn phone...

nuplayer is the culprit
just disable nuplayer in developer options and no audio glitches
eViLsTieFel said:
nuPlayer is definatelly not the cause of the issue for me.
Disabling it on 20150131 nightly and the glitches are the same.
Click to expand...
Click to collapse
Use the latest temasek linaro build it works for me

nuPlayer is definatelly not the cause of the issue for me.
Disabling it on 20150131 nightly and the glitches are the same.

nikhil18 said:
Use the latest temasek linaro build it works for me
Click to expand...
Click to collapse
Wow, back-in-time-quoting, this sure as hell won't be confusing to anybody .
I just ended up installing franko's kernel r37 yesterday, fixed the issue for me.

Besides disabling nuplayer kills the ability to play web based videos entirely...
Sent from my A0001 using Tapatalk

[ROM] Lineage 13.0, Idol 3 4.7" variants [unofficial] The Stayboogy Way

first and foremost, special thanks to alecbl for his initial device tree and kernel source. this build would not be possible without his kernel work.​
This is LineageOS 13.0 for the Alcatel Idol 3 4.7" variants​
as always, full device, vendor, and kernel trees available at github:
https://github.com/stayboogy/stayboogy_lineage13_idol347
all changes in detail: https://github.com/stayboogy/stayboogy_lineage13_idol347/commits/master
This build is not the same as alecbl's, mine has some various changes to make it a more proper build for this specific device.
Updates will be coming as time progresses and new features are added.​
FEATURES:
tap2wake & tap2sleep
double press power button opens camera
triple press power gives brightness boost
call recording available
lineage.yahoo.weather provider now installed by default
notepad included by default
typical apps and functionality of CM / Lineage roms
SPECIAL NOTES
1) wrist/tilt sensor (accelerometer) is used for the missing motion sensor for doze settings
2) speech to text / voice typing requires the Google app and for microphone permissions to be activated in settings/apps/Google/permissions then it will work correctly
3) smart lock settings work and persist over reboots--you must have the play store updated, play store services updated, the Google app installed, and Maps installed for all settings to work in smart lock settings.
4) flip cover has not been activated in the device tree yet--if people want it, post and if enough want it i'll add it back
5) battery light pulse option is no longer available, battery light itself when plugged in is active; notification light pulses by default, it's speed can no longer be edited because it doesn't work correctly--this was an executive decision because i don't like options that don't work correctly, these will not be added back, versions 1.1 and higher are incompatible with 1.0 framework so don't try to replace.
6) selinux is enforcing
RELEASE 1.1
click here
RELEASE 1.0
click here​

Hi stayboogy - looking forward to trying this out

Great to see a new dev picking up this device, looking forward to test your work!

sorry last build had an error, new link will be up later tonight

link is live now.
post anything i might have missed. so far i think it is fairly polished

@stayboogy - I'm Testing it now - No root access for apps ? only adb option.

k500zm said:
@stayboogy - I'm Testing it now - No root access for apps ? only adb option.
Click to expand...
Click to collapse
not missing, that's how modern security works and should be.
install superuser from recovery, that's standard mode of operation for everything after kk.

@stayboogy , Will you build lineage os 14.1??

A few issues I found on my day using this rom, I will provide logs on monday if you need, I'm out for the weekend and don't have a pc right now.
-Sometimes the power button instead of locking the device it boosts the screen brightness to max for a few seconds.
-I still find the smartlock issue with bluetooth devices, I do have google app and maps installed
-WiFi speed seems lower than on other devices connected to the same network, but since I'm not on my own house it might be a network issue, will confirm this when I get back home.

Phantom410 said:
A few issues I found on my day using this rom, I will provide logs on monday if you need, I'm out for the weekend and don't have a pc right now.
-Sometimes the power button instead of locking the device it boosts the screen brightness to max for a few seconds.
-I still find the smartlock issue with bluetooth devices, I do have google app and maps installed
-WiFi speed seems lower than on other devices connected to the same network, but since I'm not on my own house it might be a network issue, will confirm this when I get back home.
Click to expand...
Click to collapse
1) you're double pressing the power button then, and you have the "double tap power to open camera" option off in settings/buttons/
--either stop double pressing the power button which is what boosts brightness
--or turn on double press for camera option to turn off brightness boost
--or stop double pressing your power button
--pressing once will NEVER EVER produce brightness boost--i've been using the rom since before it was released so i'm sure of this
--your power button may be worn and more susceptible to register a double press when it wasn't
2) smart lock works for me in every option--make sure you're not using some crappy third-party lockscreen app or lockscreen security app that could be interfering with this.
--also there is a slight bug where bluetooth devices that are paired are not remembered upon a power cycle--i'm working on this as i type
3) this must be where you are--i have no issues whatsoever regarding wifi or networks period. of course i have 1GB/min speeds on bad days, and 2GB/min speeds on good days so idk
Thanks for Sharing, and this is the correct way for people to voice their finds and opinions, so thank you for that

alecbl said:
It does not have it by default but retains the option to enable it. I have enabled it. The day cyanogen/lineage starts needing to be rooted is the day I start building some other rom.
Click to expand...
Click to collapse
A message from alecbl from his build....

k500zm said:
A message from alecbl from his build....
Click to expand...
Click to collapse
you're arguing about nothing--engineering builds (ie. lineage_idol347-eng) are the only build that will have su enabled for apps and adb by default
userdebug builds and user builds do not have this enabled by default--only adb root access is made available standard by the system in developer settings.
again, the freaking su is NOT MISSING. I chose to leave the system as it is, because that's how it's supposed to be, and your problems are just stupid childish whining because you don't how current android works.
if you want root, use superuser from recovery which again is standard operating procedure for everything after KitKat. why you can't get this through your thick ****ing skull is beyond me. you obviously are not a developer and have no business making any claims as to what is standard or what is the right way for a rom to work when you aren't building any and have no experience or even basic knowledge of how the build system works or the hundreds of security revisions that have been introduced since kk that make non-systemless rooting a vulnerability...

stayboogy said:
1) you're double pressing the power button then, and you have the "double tap power to open camera" option off in settings/buttons/
--either stop double pressing the power button which is what boosts brightness
--or turn on double press for camera option to turn off brightness boost
--or stop double pressing your power button
--pressing once will NEVER EVER produce brightness boost--i've been using the rom since before it was released so i'm sure of this
--your power button may be worn and more susceptible to register a double press when it wasn't
Click to expand...
Click to collapse
Yeah, it's most likely my button being worn out, because I had disabled the double press to open camera since it was randomly opening when I pressed the button, I just didn't know double press for brightness was a feature (it's a useful one actually)
2) smart lock works for me in every option--make sure you're not using some crappy third-party lockscreen app or lockscreen security app that could be interfering with this.
--also there is a slight bug where bluetooth devices that are paired are not remembered upon a power cycle--i'm working on this as i type
Click to expand...
Click to collapse
After every power cycle I get the notification to pair it and confirm that the codes match and on the bluetooth device itself I get a new 6039A device on the paired devices list after it happens, so it might be that issue you mentioned. (I attached a pic of how the devices list looks on the bluetooth device)
Thanks for Sharing, and this is the correct way for people to voice their finds and opinions, so thank you for that
Click to expand...
Click to collapse
Well, I know and appreciate the free time from your daily life you take to develop and share your work. Hopefully certain type of entitled idiots who think they deserve everything their way and for free don't discourage you to keep up with your amazing work!

Versions 1.1 release
download link the OP
hopefully bluetooth paired devices retention is working now

stayboogy said:
Versions 1.1 release
download link the OP
hopefully bluetooth paired devices retention is working now
Click to expand...
Click to collapse
Is now camera included?

I think there is some confusion among users a camera is included just not the stock one

stayboogy said:
I think there is some confusion among users a camera is included just not the stock one
Click to expand...
Click to collapse
I was talking about stock camera, sorry for the omission

USB bug
After installing I cant transfer files from my device to pc.
In developer options you cant change the USB option from just charge to MTP, PTP or any other it stays in just charge
UPDATE: At the USB Configuration select MTP and keep touching the option to change it
NOTE: Enable Developer options before connecting the device for the first time to the pc

BlackDantex said:
After installing I cant transfer files from my device to pc.
In developer options you cant change the USB option from just charge to MTP, PTP or any other it stays in just charge
UPDATE: At the USB Configuration select MTP and keep touching the option to change it
NOTE: Enable Developer options before connecting the device for the first time to the pc
Click to expand...
Click to collapse
yes, i'm aware you can't change in developer options while it is not attached to pc,
and it bugs out sometimes when it's attached to pc
--this is a problem in the lineage source, not the device tree and therefore out of my control
--use the notification in the status bar to choose how you want the device to connect PTP, MTP, Charge only--this works perfectly and as expected

Somewhere along the way, CM/Lineage has messed with the Bluetooth stack in the source code, and there seems to be possibly some missing component service that needs to be running in order for fine location access to be given to bluetooth in order for it to work correctly, and this is also related to smart lock.
at this time, upon every reboot of your device, you will have to re-pair any bluetooth device you have used previously. auto-connect is broken in the bluetooth service stack somehow. also, your device is created anew each time it is rebooted due to a security measure enacted by google a while back that randomizes your bluetooth mac address so that your device location can't be sniffed by third-party apps. there's a whole long bulletin about it somewhere, but i guarantee this is why bluetooth auto-reconnect is broken after a power cycle.
i have discontinued all use of lineage 13 personally because of this reason alone.
i'll still be work on this rom though.
just don't expect a fix for bluetooth from me because it will have to come from upstream aosp and then made known to everyone.