Related
Despite setting the WiFi sleep policy to "never", HD2 becomes unpingable when the screen goes off, causing applications such as Fring/Skype/etc to lose connection. After turning the screen back on, the WiFi reconnects, and does it rather quickly, but having it off while the screen off meaning no incoming Fring/Skype calls possible on WiFi.
Any ideas ?
NOTE: i am currently using this build.
Same problem. Wi-Fi goes to sleep when screen goes off, even if Wi-Fi tethering is running. It's a reason of losing connection via Wi-Fi tethering. BUT! If at least one network service is active (ping, for example), Wi-Fi doesn't goes to sleep. I think that some of background services (Wi-Fi routing!) stops or becomes idle when screen goes off. It's a priority or policy bug, maybe... Not in a particular ROM, but in Android OS.
Using MDJ's CyanogenMod 7 NAND ROM (Android 2.3.2 Gingerbread).
or may be in power saving option check there .it looks like it saving your battery power.
shahnowaz said:
or may be in power saving option check there .it looks like it saving your battery power.
Click to expand...
Click to collapse
It is not power saving options because it also happens to my mdj 2.6 build with battery full. Power saving starts on 15% on my battery and also wifi and background data has been unchecked.
When this happens, no email updates, voip, and other app updates that needs data(because mobile data is intermittent in my area).
yeah, actually happens with all builds
I solved with this app, enabling all workarounds
http://www.appbrain.com/app/wi-fi-keep-alive/com.shantz.wifikeepalive
Enabling all workarounds would keep the device fully awake, this is not really a solution.
Tbh, this issue smells like a power management related bug in a wifi module/driver.
Also, if you google a bit, you can see it being talked about on nexus one, mentioning cyamogen roms as ones not having this issue.
Any idea what module/driver is responsible for wifi ? Is it a part of the kernel ? Or is it a module we may try replacing ?
rafpigna said:
yeah, actually happens with all builds
I solved with this app, enabling all workarounds
http://www.appbrain.com/app/wi-fi-keep-alive/com.shantz.wifikeepalive
Click to expand...
Click to collapse
Thanks much, just installed.
The offending driver seems come in a separate module, "bcm4329.ko". Here is a Nexus One thread mentioning the issue on one of the Nexus One stock builds, and actually presenting an updated module for that stock build.
Since HD2 uses the very same BCM4329 chip, it should be possible to compile the updated module for an HD2 kernel.
Any kernel guys up to the task ?
InfX said:
The offending driver seems come in a separate module, "bcm4329.ko". Here is a Nexus One thread mentioning the issue on one of the Nexus One stock builds, and actually presenting an updated module for that stock build.
Since HD2 uses the very same BCM4329 chip, it should be possible to compile the updated module for an HD2 kernel.
Any kernel guys up to the task ?
Click to expand...
Click to collapse
We need the commit used to do the change. I looked at the thread and found a commit but I dont think that is the right one.. Anyway I will try to see if can be included in my kernel asap and check if the situation improves.
rafpigna said:
We need the commit used to do the change. I looked at the thread and found a commit but I dont think that is the right one.. Anyway I will try to see if can be included in my kernel asap and check if the situation improves.
Click to expand...
Click to collapse
I checked, and the fix is already there... So at this point I think this is not our problem. I will try to address this to markinus or danijel that are far more experienced than me in kernel stuff
rafpigna said:
I checked, and the fix is already there... So at this point I think this is not our problem. I will try to address this to markinus or danijel that are far more experienced than me in kernel stuff
Click to expand...
Click to collapse
Maybe, just maybe, it's already fixed in your latest kernel, that uses the latest code base ? Note that i did NOT try & check it with every kernel available, i've only checked this with one that came with the build i am using (i think it was MDJ there, newer version uses yours, but i am not yet running it).
Anyone using latest rafpinga kernel, can you please test and respond ?
Update, rafpigna 1.7 installed, identical WiFi behaviour.
Looks like this is the solution for Desire:
http://forum.xda-developers.com/showthread.php?t=752856
Hopefully someone could adopt this to HD2.
Nice... Rafpigna, the diffs are at this post, can you apply and compile the patched "bcm4329.ko" for us to try ?
Sorry for being too dumb to do it myself, i just never ever happened to compile a linux kernel, not even once in my entire life
InfX said:
Nice... Rafpigna, the diffs are at this post, can you apply and compile the patched "bcm4329.ko" for us to try ?
Sorry for being too dumb to do it myself, i just never ever happened to compile a linux kernel, not even once in my entire life
Click to expand...
Click to collapse
It's not our problem
Note: This isn't related to the sleep mode wifi disconnections caused by MAC addresses that don't begin 00, so far as i'm aware that's been patched for a while now. Wifi remains connected fine in standby mode, but the throughput is only suitable for very light traffic.
Click to expand...
Click to collapse
I know its not our problem, but this may still be our solution. Our problem, seemingly, starts when the driver it going down into the deepest power saving state it can. It is supposed to sustain connectivity in it, though, but it seemingly doesn't. Avoiding this deepest state (PM_MAX) may solve the problem while having little to no side effects. Well, obviously, i do understand it's going to consume more power with WiFi on, but its better than being unable to keep it on at all.
Again, i know this is not exactly our problem, but again, this CAN be our solution anyway.
InfX said:
I know its not our problem, but this may still be our solution. Our problem, seemingly, starts when the driver it going down into the deepest power saving state it can. It is supposed to sustain connectivity in it, though, but it seemingly doesn't. Avoiding this deepest state (PM_MAX) may solve the problem while having little to no side effects. Well, obviously, i do understand it's going to consume more power with WiFi on, but its better than being unable to keep it on at all.
Again, i know this is not exactly our problem, but again, this CAN be our solution anyway.
Click to expand...
Click to collapse
I think it's definitely worth a try...
mishik said:
I think it's definitely worth a try...
Click to expand...
Click to collapse
Hello!
Unfortunately, I have tried this (to my detriment; I have code due tomorrow still!), and basically replaced the equivalent of this in the RAF 1.7 code (dhd_cdc.c and wl_iw.c have the PM_MAX vs PM_FAST thing).
My zImage came out almost a whole MB smaller (probably a toolchain thing), but the wifi problem while sleeping still exists, at least the symptoms that are linked in http://code.google.com/p/cyanogenmod/issues/detail?id=2403 with the similar fix of PM_MAX vs PM_FAST. That is to say, if I open the terminal and ping google.com, when the screen is off I get 300ms pings and when the screen is on I can get 3ms pings.
This happens whether I change PM_MAX or PM_FAST.
So this isn't the fix for what it's supposed to fix (or maybe I'm doing it wrong, toolchain's wrong, something), but I'll give it a few days to figure out whether my wifi drops more or less. Hopefully less.
(My symptoms are that, on campus, I have no problems with wifi, but sometimes if I leave the wifi zone and then come back, it'll report still having an IP lease and everything, but all pings and connectivity-type things such as web browsing will time-out. Not sure if this is what is being discussed here, but I thought it might help!)
Thanks,
Jeff
PS If you want the zip just to give it a spin, pm me or I might attach it here. That said, it might break everything! No obvious problems on my phone yet, though, so...
EDIT!: Of course, I invite anyone (especially rafpigna; perhaps you've tested this already?) to double check my work. It's possible I might've misplaced something!
I didn't do anything advanced; just pick up the CodeSourcery toolchain (free) for ARM (not GNU/Linux) and then install it on a Linux machine (it's possible with Windows, probably, but it'll be harder with the RAF build.sh). Then, make sure you have make and gcc packages on your Linux machine and then put your sources in the right directory and then try running the build.sh! rafpigna documents his work very well. Thanks rafpigna!
Did you remember to actually replace the .ko module, not just zimage ?
Hello,
Did you remember to actually replace the .ko module, not just zimage ?
Click to expand...
Click to collapse
Of course.
DISCONTINUED: For the newest & greatest, please check this out.
Prequisites.
404020 baseband installed. (If you had upgraded to 2.3 from B517+ you're good)
/system with more than 300MB available (forumber partition table/BlePart_1 (to come))
Installation.
Download the flashable zip.
Reboot to recovery.
On first install, wipe /data and /cache.
Install the flashable zip.
Optional: Install Gapps. (only on first install)
Reboot to normal mode.
Done.
Features implemented.
3.4 kernel - No Huawei silliness included!
Chip manufacturer provided accelerometer/magnetometer driver.
Chip manufacturer provided touchscreen drivers.
Optimized kernel for stability (removed unneeded drivers).
Atmel TS can now use up to 10 fingers at once.
New Light/Proximity driver (APS-12D) - Created by me from scratch.
Allows light sensor to show all values from 0 to 64000lux. Proximity driver is faster.
Device Settings - a CM specific application for changing phone's internal settings.
Vibration intensity scaling - scale vibrator voltage from 1.2V to 3.1V (3.0V default)
USB OTG - Attach any USB device ONTO your phone. Does not require external power supply (outputs 200mA/5.0V).
Does not need any special cables, however regular USB OTG cable is the simplest way to use.
Force internal microphone - use the phone's microphone even when headset is connected.
Low Power Audio.
Any other feature the CM team has implemented.
Bugs present.
Bugs in the latest release.
Wi-Fi may not start when the memory is fragmented.
Button backlight does not change on auto brightness mode.
USB OTG may not work all the time.
*Note: Toggle the OTG mode on/off and try again.
Atmel TS driver does not always recognize finger release.
Display may not always turn on.
*Note: Toggling the display on/off several times helps.
Display is not always in sync.
Synaptics TS may experience touch lag.
On no service, signal strength may show a wrong value.
HD video playback is stuttering every few seconds.
Big speaker is distorted (not on all devices it seems).
Battery capacity is not very reliable.
Camera flash/video recording is not working.
FM Radio is not implemented (Spirit may work).
TV Out is not implemented.
Downloads.
If there is an update, it must be installed on top of the latest release.
cm-10.1-20131201-UNOFFICIAL-u8800.zip
cm-10.1-20131027-UNOFFICIAL-u8800.zip
cm-10.1-20131002-UNOFFICIAL-u8800-update1.zip
cm-10.1-20131002-UNOFFICIAL-u8800.zip
cm-10.1-20130909-UNOFFICIAL-u8800.zip
cm-10.1-20130831-UNOFFICIAL-u8800.zip
Changelog.
All releases contain latest CyanogenMod Nightly source code (except updates).
Code:
[LIST]
[*]01.12.13
[LIST]
[*] Removed A3XX libraries (not used).
[*] Added battery stats (Android).
[*] Fixed battery capacity jumping (not entirely fixed).
[*] Fixed more charger problems (charger can not fail anymore).
[*] Added camera support (S5K4E1GX tested, OV5647 untested).
Flash will crash the phone, disable flash.
Video recording is not working.
Some third party apps like Focal can not be used.
[*] Use stock partition table layout.
[*] Set external SD as primary.
[*] Add Portuguese translations to DeviceSettings (Advanced). (Thanks to Disrupthor).
[*] Use GPU composition (C2D is now working, but glitchy).
[*] Show ongoing notification when USB host is turned on to DeviceSettings (Advanced).
[*] Fixed headset volume (as Huawei stock).
[*] Removed some unsupported code in kernel.
[/LIST]
[*]27.10.13
[LIST]
[*] Fixed a bug with the USB driver causing endless interrupts (increased CPU usage).
[*] Fixed proximity sensor.
[*] Fixed "click" sound on headset.
[*] Fix userspace getting wrong FPS.
[*] Fixed non-standard USB chargers. Charging at maximum of 500mA.
[*] Updated & enabled interactive CPU governor.
[*] Added smartassV2 CPU governor, SIO I/O scheduler.
[*] USB & Bluetooth tethering (bluetooth not tested).
[*] Increase available memory by 2MB (from modem bootloader).
[*] Added overclocking up to 1.4GHz (not thoroughly tested).
[*] Fixed data usage monitor (mobile data).
[*] Enabled automatic brightness (not properly optimized).
[*] Improved light sensor sensitivity in low light (rounding value down).
[*] Fixed wrong manufacturer/device name on USB.
[*] Added new Synaptics TS driver (accurate, powers off, not thoroughly tested).
[*] Small updates to lowmemorykiller.
[*] More charger fixes (will this ever stop?).
[*] Added Turkish translations to DeviceSettings (by forumber2).
[/LIST]
[*]02.10.13 Update 1
[LIST]
[*]Added battery indicator leds (not pulsing right now).
[*]Modified magnetic sensor calibration. See recalibration in readme if you need to.
[*]Changed battery/charger more, deals with more errors.
[*]Increased small speaker volume.
[/LIST]
[*]02.10.13
[LIST]
[*]Fixed display FPS.
[*]Fixed NT35510 freeze upon unsuccessful turn on.
[*]Fixed battery reporting 0.
[*]Fixed battery temperature set to 35 without USB.
[*]Added CRT-off animation (changeable in the Settings).
[*]Enabled some memory optimizations (introduced by the CM team).
[*]Improved NT35582 FPS to 51-53 average.
[*]Modified battery charging times (should fully charge, not tested).
[/LIST]
[*]09.09.13
[LIST]
[*]Rebased kernel on caf/jb_2.5 (newer kernel). Updates core kernel drivers (MDP, KGSL, USB, etc)
[*]Fixed display freeze on boot sometimes.
[*]Fixed display not turning on at all times (confirm?).
[*]Changed display brightness scaler.
[*]Fixed Wi-Fi not connecting to network properly.
[*]Increased virtual key width (50 to 60).
[*]Decreased speaker amplifier gain (12db vs 8db). Makes speaker not so distorted at higher volumes.
[*]Added /cust partition to Android (default read-only).
[*]Changed battery driver (SOC still not stable, in progress).
[*]Fixed most charger problems.
[*]Fixed alarms not triggering.
[/LIST]
[/LIST]
Credits.
dzo
Code Aurora Forum
CyanogenMod
Check the project page for more information.
The full source code used to build this ROM is available at GitHub.
Some features may have not been merged to CM, so also check my changes at CyanogenMod code review.
Readme.
USB OTG: You can connect peripherals to your device and your device will act as host. You should first enable OTG, and then connect your device, otherwise it may happen the device won't function. Note that this must be manually enabled through Settings->Advanced->USB OTG. To minimize power loss, disable USB OTG after using it.
Magnetic Sensor Calibration: Delete /data/misc/sensors/lsm303dlh_mag , reopen any app that uses compass or magnetic sensor, move the device around in all axis and it should be properly calibrated.
Wi-Fi MAC Address: With ADB/Terminal Emulator, do "setprop persist.wifi.mac 00:11:22:33:44:55". May need to reboot.
Bluetooth MAC Address: Open /data/misc/bluedroid/bdaddr & modify it accordingly. May need to reboot.
Great to hear that you have created the rom from source! But I'll wait until it's working flawlessly.
Keep it up!
hell yeah! I wait for this day a long long time!
Miracle!
thanks Blefish for your hard work!
Finally... it's alive it's alive... I mean my phone is still alive because of you blefish...
Thanks alot :thumbup:
Sent from my U8800 using xda app-developers app
hell yeah!
[•=_=•] __[ i guess i am going to cry now ]
Thanks for your hard work! :good:
Can't wait to test this after some of the bugs that are necessary for daily usage (for me) are fixed (camera, notification led, automatic brightness and maybe overclocking).
Does the Synaptics TS driver not powering off bug use much battery?
Is it possible to disable the low power audio from build.prop (or somehow) so I could use a equalizer?
This is a great new start for the u8800 development! :fingers-crossed:
404020 baseband installed.
Click to expand...
Click to collapse
I assume this is the version installed by official 2.3.5.
Have Been following your progress through twitter good to see the first release
Thanks for keeping this phone alive
Sent from my U8800 using xda app-developers app
congrats blefish, have been waiting for this since forever... you have done a commendable job.
Can we use gapps-jb-20130813 from goo.im?
PS: as much as possible update it as flashable with necessary files(OTAish)
Wow, incredible.
Thank you blefish. You're are u8800's hero
uumeshh said:
congrats blefish, have been waiting for this since forever... you have done a commendable job.
Can we use gapps-jb-20130813 from goo.im?
PS: as much as possible update it as flashable with necessary files(OTAish)
Click to expand...
Click to collapse
Listen 20130813 is for Android 4.3 and that is 4.2.2 so you have to install 20130812
Sent from my iPhone using Tapatalk - now Free
riDDimann said:
I assume this is the version installed by official 2.3.5.
Click to expand...
Click to collapse
I forgot, you can look it up in options And I can confirm 2.3.5 installs baseband 404020.
riDDimann said:
I forgot, you can look it up in options And I can confirm 2.3.5 installs baseband 404020.
Click to expand...
Click to collapse
404020 is GB baseband and 404029 is ICS/JB baseband
Sent from my iPhone using Tapatalk - now Free
ouyeahh will try soon
Doing a nandroid right now
Thank you! You give a new life for this phone!
Enviado do meu U8800 utilizando Tapatalk 4
great work man ! i am looking forward to updates :good:
zazza8 said:
Thanks for your hard work! :good:
Can't wait to test this after some of the bugs that are necessary for daily usage (for me) are fixed (camera, notification led, automatic brightness and maybe overclocking).
Does the Synaptics TS driver not powering off bug use much battery?
Is it possible to disable the low power audio from build.prop (or somehow) so I could use a equalizer?
This is a great new start for the u8800 development! :fingers-crossed:
Click to expand...
Click to collapse
I will replace the Synaptics TS driver in an update, I don't have Synaptics installed right now so I cannot tell about power.
As far as I know, LPA audio effect are supported. It's possible to disable LPA by modifying it in build.prop like this:
Code:
lpa.decode=true
Code:
lpa.decode=false
uumeshh said:
congrats blefish, have been waiting for this since forever... you have done a commendable job.
Can we use gapps-jb-20130813 from goo.im?
PS: as much as possible update it as flashable with necessary files(OTAish)
Click to expand...
Click to collapse
As @herna told, this if for CM10.2.
I am doing my best to provide updates and solve the bugs. I know a solution to most of them, just haven't got around to implementing them.
What can I say. It does exactly what it says on the tin and it does that great for a first version!
It boots, connects to Wifi and Bluetooth, mobile works. And it's pretty damn smooth considering it's running at 30ish fps
Well done and thank you, Blefish.
Edit: Vsync doesn't actually work btw. It's a shame, but when did it ever work correctly on this device?
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
Okay so we've come from Kitkat to Lollipop and from Lollipop to Marshmallow now.Motorola has been very good compared to other manufacturers for pushing OTA updates.
Many people are wondering "is Marshamllow really a worthy update from Lollipop?"
I flashed 6.0 Marshmallow on my Moto G 2014 (don't ask procedure it sucks) and here's a short review of my first day with it!
Here are some good things...
Battery Life And Doze
One of if not the most important aspects of any smartphone,battery life
Well,I haven't used it for more than 24 hours so far but what I'm seeing is a a rather improved battery life.
It's not tested yet properly but I can get a screenshot however
(Check an sudden steep but small decline in battery life graph. Due to Doze?)
Now On Tap
This feature was one of the most awaited features of Marshmallow.It instantly reads the text in that particular window and give you more information about it.
Okay so here's an issue I faced.While opening Instagram icon,it never opened Instagram link in Instagram app instead,opened it in browser reason? I have no idea.
This feature is still new and I see space for a ton of improvement.(*tsk tsk* Ignore Justin Beiber part though )
System UI Tuner
Me being a Cyanogenmod user got pretty much disappointed with this feature.It had very limited scope compared to Cyanogenmod (obviously) but hey,that's a cool
feature for normal users.Long press on settings icon in quick settings header (it will start spinning and will give you a toast notification saying system UI tuner
is now activated).You can bring up percentage display in battery icon and choose what you want and what you don't want to see in status bar (alarm icon,gps icon,
clock,etc).It has a demo mode (not sure how/why would anyone use it) too.
Storage
You can now merge your SD card with your internal storage which gives you infinite space.Yes,it can store your apps and data too! Basically your SD card works like
internal memory.You must format your card if you want to merge it.You also have an option to keep them seperate if you wish.Window which shows your Storage and USB
it cleaned up and now is minimalistic.It shows you how much space your Android OS has taken up.
App Permissions
It will ask for your permission every time an app tries to access your mobile's data (camera,microphone,gallery,contacts,etc).This can be also used to turn off/deny permissions of a specific thing to a specific app.
Small But Sweet Things
Animations
Marshmallow has smooth animations and transitions all over it.For example,opening an app gives much much better animation effect compared to Lollipop.
It might eat some of your battery life but I don't think it will hurt battery that much.
Do Not Distrub Tab And Volume Settings
In Marshmallow,you get much much better volume settings than Lollipop.Do not disturb mode is separately moved to quick settings and you can control whole volume panel
i.e phone sound,media sound and alarm sound after expanding it (*cough* Cyanogenmod *cough*)
Automatic Rules
You can add a task for volume settings.It can be either event oriented or time oriented.This is similar to Lollipop but now you can add more than one events (very nifty).
Lockscreen Shortcuts
Lockscreen shortcut now has Google Now activation by swiping from left (was Dialer in Lollipop) and Camera by swiping from right.
FM Radio
Now you can listen to radio even if you don't have headphones (not sure if this was there in Lollipop,I don't use it much anyway).
Google Cookie/Easter Egg
Now you can play with two or more players in that "game" (C'mon who plays it?)
So,is it really a worthy upgrade?
Well,what I think is you should definitely get it if you can upgrade easily (XT1068 to XT1069 and stuff) or if you now what you're doing while converting your
XT1068 to XT1069 (trust me this proccess sucks).I think Marshmallow is what Lollipop should've been (I stole this from XDA News section, LOL).
I'm not gonna shift to any other ROM so soon now
I'm a heavy BT headphones listener and I basically pray that viper4android will work with MM when root comes available.... I managed to convert xt1068 to xt1069 after losing a day doing it, so I'll stay a while even without root and very bad stock audio eq...
Sam.1211 said:
I'm a heavy BT headphones listener and I basically pray that viper4android will work with MM when root comes available.... I managed to convert xt1068 to xt1069 after losing a day doing it, so I'll stay a while even without root and very bad stock audio eq...
Click to expand...
Click to collapse
Chainfire hasn't achieved root for Marshmallow so far... Let's just wait
You can now merge your SD card with your internal storage which gives you infinite space.Yes,it can store your apps and data too! Basically your SD card works like
internal memory
Click to expand...
Click to collapse
For me, this is a MUST. The 8GB internal space doesn't matter anymore. Thank you for your post.
akay193 said:
FM Radio
Now you can listen to radio even if you don't have headphones (not sure if this was there in Lollipop,I don't use it much anyway).
Click to expand...
Click to collapse
So FM Radio is internet radio now? For FM the headphones are needed as antenna - nothing that can be fixed via software...
OJK said:
So FM Radio is internet radio now? For FM the headphones are needed as antenna - nothing that can be fixed via software...
Click to expand...
Click to collapse
No, it's not internet radio. You can use the app without headphones but the radio station has to have a strong signal in your area. This feature was introduced in version 2 and worked on Lollipop too.
Okay here's some battery status
Screen on time 3 hr 40 mins
Still 10% remaining
I have SOT of 4 hour and 48 mins on 1st day of Android Marshmallow.....! ??
karan_master25 said:
I have SOT of 4 hour and 48 mins on 1st day of Android Marshmallow.....!
Click to expand...
Click to collapse
were u soak member or xt1069 converted
Battery Life And Doze > Motorola didn't enable doze
[email protected] said:
were u soak member or xt1069 converted
Click to expand...
Click to collapse
XT 1069 converted...!
luca020400 said:
Battery Life And Doze > Motorola didn't enable doze
Click to expand...
Click to collapse
Didn't know this hahah
luca020400 said:
Battery Life And Doze > Motorola didn't enable doze
Click to expand...
Click to collapse
It's not possible , Google made it mandatory to enable doze and App standby like feature and bettery battery stats to remain active in their roms ,Refer Android Combatility Definition
http://googleweblight.com/?lite_url...330858&sig=ALL1Aj4J3lJ5IFMvg77CVaTD5alx3frvBw
[email protected] said:
It's not possible , Google made it mandatory to enable doze and App standby like feature and bettery battery stats to remain active in their roms ,Refer Android Combatility Definition
http://googleweblight.com/?lite_url...330858&sig=ALL1Aj4J3lJ5IFMvg77CVaTD5alx3frvBw
Click to expand...
Click to collapse
If your hardware support doze you have to enable it > msm8226 ( snapdragon 400 ) cannot handle doze
luca020400 said:
If your hardware support doze you have to enable it > msm8226 ( snapdragon 400 ) cannot handle doze
Click to expand...
Click to collapse
Now that's bummer ,, I will ask Moto representative about that,
What's the damm point of Marshmallow if its main features are hardware specific ,
And Moto doesn't even care to explain that,, heck not even Google said that Doze is hardware dependent ,,
This all wait for Marshmallow update is fuss now
luca020400 said:
If your hardware support doze you have to enable it > msm8226 ( snapdragon 400 ) cannot handle doze
Click to expand...
Click to collapse
Could you maybe provide a link?
Anyway, if battery life is substantial better than with stock 5.0.2, I don't care too much if doze is actually supported or not...
The thing about using the FM radio without headphones isn't new... It's already available in LP.
luca020400 said:
If your hardware support doze you have to enable it > msm8226 ( snapdragon 400 ) cannot handle doze
Click to expand...
Click to collapse
Then howss that CM13 for this device working with. Doze enabled and cheap device like Android one is capable of it too
[email protected] said:
Then howss that CM13 for this device working with. Doze enabled and cheap device like Android one is capable of it too
Click to expand...
Click to collapse
Hmm no we didn't enable doze in cm13
Sent from my Moto G 2014 LTE using Tapatalk
luca020400 said:
Hmm no we didn't enable doze in cm13
Sent from my Moto G 2014 LTE using Tapatalk
Click to expand...
Click to collapse
This is devastating ,,, I know in future ,,there may be something fully worke/dependent on Doze ,,
This is bummer again ,, I wish it wld have those features but azamzing and quite surprised to know that no discussed about these features dependencies
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.