Related
This is a thread for the Nexus One SuperOSR ROM. This ROM is descended from the SuperAOSP ROM. It does not appear SuperAOSP will be further developed, the last version was v8.6. That xdaforums thread is here:
http://forum.xda-developers.com/showthread.php?t=966635
I value the "Super" line of ROMs because they have been rock stable, have built in Apps2SD, many CM additions, and good battery life.
The primary forum for this ROM is a Spanish one, called movilzona.es. Anything posted here from that forum has been run through google translate, with mixed results. If a native speaker would like to help correct some of these translations, great!
I do not have any say or input into the development of this ROM. I obtained permission of the ROM cook (nelo360), who makes the Nexus One version, to post information about it here. He has explicitly stated he cannot provide any support other than on the original Spanish forum. Of course, the forum community will try to help each other out. I will try to update new releases here.
All credit of course goes to nelo360 and the rest of the development team, [email protected]
The original thread on movilzona.es is here:
http://www.movilzona.es/foro/superosr-nexusone-base-superte-gingerbread-t5882.html
The following is directly from their forum, translated poorly:
Message Super @ Take it and accepted by the group SuperTed @ m.
Disclaimer:
NOT going to give any support to this ROM from any forum other than this one (movilzona.es), this is it is very common for people to hang it in another forum and then have to be looking where it hung in addition to the main forum and I can not respond to external requests of this kind, because I can not be everywhere.
It's funny to talk over the ROM from elsewhere, since the main from which it hung, plus you have to think that this would not be possible if there were forums like this, from which terminals to lend me all enjoy ROMS varied. For questions, NO is posted in HTCMANIA because this forum was banned for posting ROMS here.
For any questions of why this resolution, since many people keep asking me from twitter, because I hang on HTCMANIA ROMS can see the explanation here:
http://www.movilzona.es/foro/superatmel-f73.html
Click to expand...
Click to collapse
Install Notes
SuperOSR for Nexus One AntiWipe
- Clarification and instructions
Once you start, leave the phone 3 to 5 minutes at rest so it can configure itself on first boot. The LED will shine blue through this period. Once it turns off, you can start using the phone.
IMPORTANT App2SD will not turn on without restarting the phone at least once.
Can be activated from: SupSetup/Options/App2SD and LinuxSwap/Activate App2SD
If you want to install extra apps from SupSetup is important to do before you set google account, this way, when we install any application market will be downloaded automatically apps we select the SupSetup.
If you have problems after installing, before blaming the ROM, try to install it with full wipe.
DOWNLOAD from here:
v2.4.0
http://goo.gl/htXpe
v2.2.0
http://goo.gl/iJpoi
v2.1.0
http://goo.gl/KfT2U
Update to flash from the recovery that we restore the original source in the lock screen:
http://goo.gl/vX4Eo
Click to expand...
Click to collapse
<I don't know what that last sentence is supposed to mean>
I recommend you skip google account login the very first time you install. Configure the ROM first, turn on apps2sd if you wish (it will auto-reboot), then do your google login. Otherwise, it will start auto-downloading all your apps from market, and generally make a huge mess.
Screenshots:
Changelog
Changelog v1 SuperOSR AW *
- Based on Android 2.3.5
- All improvements CyanogenMod
- New kernel 2.6.38.8 redstar
- Added ADWLauncher as default launcher
- New visuals
- many internal improvements and bug repaired
v2.0.0
- New boot animation
- New Wallpaper
- New graphical look
- Updated some apps
- Fixed the bug of random color of the trackball
- Restructuring wireless menu
- Modified apn Pepephone (I think this is a mobile service provider in Spain)
- Internal improvements and optimizations
v2.0.2
- Blue LED activity during installation. (Expect to be off to start playing)
- Removed some apps (you can install from the market)
- ADW is changed by the original launcher modified
- Increased the cache to 1024 kb sd to increase the writing speed via USB
- Compiled 2.6.38.8 kernel redstar, with the latest updates
- Improved power consumption
- Modified the graphics in different rom sites
- (CM) has rewritten part of the code led the trackball notifications
- Base CodeAurora
v2.1.0
- Based on android 2.3.7
- Added support for multiple languages
- New lockscreen options
- Fixed some pngs
- Several small bugs fixed
v2.2.0
- Sources synchronized (17.11.2011) Google and CM
- New battery (MIUI style) by default
- Option to take screenshots by pressing the power button for a while
- Fix that greatly improves the speed of writing on the sd (overhtc thanks for the tip)
- Reorganization and edit some menus
- New version lockscreen ring (center ring only)
- Removed some apps to make the lightest rom (can be installed from the market)
· Google Docs
· Google Plus
· Adobe Flash Player
V2.4.0
- Sources synchronized (02/12/2012)
- New animations of ICS
- New visual options lockscreen ring
- More Parts and other translations on menus
- Option to share the screenshots after transmission
- Internal optimizations
Some things I've noticed with v1, coming from a complete wipe.
Market is the older 2.3.6 version
Gmail is an older version which FCs on me. Updating to the new version works fine.
Maps is an older version.
Apparently there is a problem with notifications, from user nodnarb:
Notifications are given as normal, but when you pull down the notifications bar to select any of the notifications it doesn't acknowledge the tap.
Click to expand...
Click to collapse
Great. Any screenshoots?
Already customized my ROM after installing, so graphically it's not particularly impressive.
Basically the ROM runs ADWLauncher, so not so much to show more than that.
I'll post some shots from the settings pages.
Also, some screenshots available here from the older version. Graphically, not much has changed.
http://www.movilzona.es/foro/superaosp-para-nexus-one-por-superatmel-tolemac-t4675.html
Go to post #3. Except it will be in English =)
Been running the new version since last night. So far it's not bad. I did like the old launcher better then ADW but what do ya do....Battery life seems great so far. So far my notifications seem to work ok. Not any significant changes but maybe the subtle ones will show up with use. Too bad the only support is on a Spanish only site. I suppose we can all support it here as well to an extent....
I have been running this rom since yesterday and so far no issues at all! No notification issues or Gmail FC's here. am glad that you have created a thread there. I too am a big fan of Super line of roms. Thanks for your effort.
hackermail said:
I have been running this rom since yesterday and so far no issues at all! No notification issues or Gmail FC's here. am glad that you have created a thread there. I too am a big fan of Super line of roms. Thanks for your effort.
Click to expand...
Click to collapse
I'm glad for the thread too.
Are here any special requirements that I missed - for example, A2SD (mentioned on movilzone thread) usually entails an ext4.. could this be why my installation never worked out? It's just a hunch (I don't have an ext4).
I did have fc of gmail too - do i simply go ahead and update it from market then? I never got to test gtalk. Market is not the newer version which I suppose one can live with.
I flashed it for my wife's phone but as it never gave me any joy, i reverted to SuperAosp 8.6 which works 100%.
Galloway said:
... Too bad the only support is on a Spanish only site. I suppose we can all support it here as well to an extent....
Click to expand...
Click to collapse
If you use Google Chrome as your browser, it does a fantastic job of instant auto translating the site. I speak Spanish and can attest to its acceptable accuracy. Chrome also helped me with the Chinese on the original MIUI site.
tanclo said:
I'm glad for the thread too.
Are here any special requirements that I missed - for example, A2SD (mentioned on movilzone thread) usually entails an ext4.. could this be why my installation never worked out? It's just a hunch (I don't have an ext4).
I did have fc of gmail too - do i simply go ahead and update it from market then? I never got to test gtalk. Market is not the newer version which I suppose one can live with.
I flashed it for my wife's phone but as it never gave me any joy, i reverted to SuperAosp 8.6 which works 100%.
Click to expand...
Click to collapse
For a2sd, you can have an ext3 or ext4 partition. Mine is ext3. Any other specific problems?
Right now, I'm not seeing a big difference between 8.6 AOSP and 1.0 OSR, except for some graphical changes (the pop-up boxes look different, the thumbscroll graphic is dark instead of gray).
Actually one thing I have noticed is that my bluetooth autoconnect is not working the way it should. Before it worked okay just by changing one line in the audio.conf file in etc/bluetooth/ (set autoconnect=on). Currently experimenting.
Don't seem much difference in this ROM compared to Superaosp
i have been having some issues tho, wifi no longer works, won't connect to any networks
battery life is half that of superaosp. will try a reflash and see what happens.
I too have had zero issues. All is well here.
No partitioning of my SD card since I don't used A2SD. Just one fat32 partition.
No problems with any notifications, gmail or market.
Battery life is also very good. I'm averaging 24hrs with moderate usage with SetCPU having one state to throttle speeds down to 128-384 when screen is off.
Anyone having any issues with bluetooth connections?
I restored some bluetooth pairings with TB. Maybe should have left it alone and started anew.
Been messing with the etc/bluetooth/audio.conf file with no improvements.
Good rom. It's working well
No issues so far and my battery life is quite a bit better! I did have to manually connect Bluetooth tonight to my car but I find that happens quite often the first time I flash a new ROM...I'll monitor and see if that continues.
Figured out my bluetooth issue.
Previous, I could swear just by changing (turning on) the autoconnect=on parameter in audio.conf, I could forgo repairing/relearning my bluetooth pairings.
So I changed it after the wipe/flash, and couldn't get it to automatically pair. In fact, couldn't get it to connect at all for any duration.
After putzing around with all the other parameters, I realized I should have just changed back the original thing I had altered ("#autoconnect=on"), and it works fine now.
So, the take home lesson is, don't mess with the etc/bluetooth/audio.conf file that comes preloaded! And just re-pair whatever BT items you had previously.
xdraw said:
Don't seem much difference in this ROM compared to Superaosp
i have been having some issues tho, wifi no longer works, won't connect to any networks
battery life is half that of superaosp. will try a reflash and see what happens.
Click to expand...
Click to collapse
I too have been less impressed. Battery life I feel is either about the same or worse. (yesterday I got down to 30% by the evening, which is unheard of for SuperASOP).
The other things that have sucked has been a random reboot into recovery (WTF?!), and GPS is slower to lock.
And then to top it all off, this morning the phone was off sitting in my desktop cradle (but 100% charged, LOL). I could live with that because my T-Bolt woke me up, but usually its the other way around in that my N1 is the Old Faithful that I can rely upon for alarm, tethering, etc.
Signal reception is also notably poorer compared to 8.4. Has anyone else noticed this?
I will give it one more day, but I may wipe everything and go back to 8.4, which had the best combo of battery life, signal, and stability for me.
Thanks for your commentary. Even as the OP here, I haven't seen major advances since 8.4 (wonk fix). And I never actually had the wonk! Did you try 8.6 and go back to 8.4? If so, why?
Though, I have not had any wifi issues, or random reboots, or slow GPS locking.
I did notice that sometime in between 8.2, maybe in 8.4, my wifi signal dropped a few bars in my living room, which isn't that far from the router. I had heard there was there some adoption of new wifi driver code?
I'm trusting you did a clean wipe flash? I think some have said that it flashes fine over 8.6, but probably not recommended.
no have Chinese , Unfortunately.
China has a lot of people , interest in the ROM.
But , they can not use this ROM .
Because they English is so so so bad ,Including me .
First, I'd like to thank Josegalre and all that have helped him in developing this ROM. It's a very good ROM that shows much promise. I hope that this will both help the developer(s) in resolving the issues I encountered, and in deciding if this ROM is suitable for your device.
The powers that be here won't allow me to post in the development threads, because I'm a "newbie". I may be here, but I'm a "Recognized Contributor" on Tytung's Nexus-HD2 forum with the handle of "Odysseus".
Since the board's software also won't allow me to post links yet, let me take a brief moment to introduce myself. I've been a computer hobbyist since before most here were born (got my first PC in 1984). I was an "official" beta-tester on the old Compuserve network for Microsoft's "Chicago" project that later became Windows 95, then continued in that capacity for Win 98, NT-4.0, Win ME, Win 2000, and finally Windows XP, before I jumped ship completely to Linux. I had been experimenting with Linux since 1997, but made it primary OS in 2001. I've been running Gentoo Linux (a source-based distribution) since 2003 and more specifically using the latest cutting edge "unstable" repositories or as we say in Gentoo "~arch" since 2005. I'm a contributor on the Gentoo and Sabyon Linux Forums as "Odysseus". I've also contributed to the Gentoo project itself, as I've submitted patches that have been accepted into the kernel tree, developed several workarounds and have written numerous detailed bug reports to both the Gentoo and upstream developers as I've discovered issues. Not bad for a 51 year old truck driver with no formal training.
Back to the topic: Since I can't post in the other thread and there is no Q/A&T thread yet for the new [ROM][10/NOV/13][UNOFFICIAL][4.3.1] PACman [Source Build] project I'd thought I'd start one here.
After using it for a day these are my observations, It's solid and stable, but does have a few issues that need to be resolved before it can become my daily driver and they are:
1) Data acquisition - This is a show stopper for me. Much like the recent Evervolve-3.3.0-p1, this ROM takes quite a bit of time to establish a stable data connection. In my case it can take anywhere from 3-10 mins for the signal to stabilize. Once connected, data transmission is as fast as it should be. This isn't a major problem if stationary, however, maintaining a usable connection while driving is problematic. WiFi on the other hand connects quickly and is very stable.
2) Battery life - Without tweaking this ROM under moderate use drains battery 25-35% faster than my current daily driver the "|Aug 6th| Energy™ -.¸¸.·´¯ ICS 4.0.3". I don't know what could be causing this issue. (Perhaps related to the data-connection issue?) My experience on both my HD2 and Amaze has been that Cyanogenmod based ROMs are generally more battery efficient than Sense based counterparts.
3) System-wide font size consistency - As mentioned, I'm no spring chicken. Even with my reading glasses on I need to increase font size to comfortably read on any ROM. Changing the system font-size in Jellybean based ROMs is usually a matter of changing the desired size in System Settings / Display, however, with this ROM there is no consistency. Some elements remain tiny (menu in browser), while others grow too large, furthermore, many apps don't appear to honor the system-wide settings. This is especially troublesome with the included browser.
4) The Browser - To me, the included browser is better suited for a larger screen. The fonts are extremely small even after increasing them system-wide. This applies to fonts in menus, title bar, address bar, tabs, and to the browser itself. Additional font size adjustment from within the browser to 115% for both bars and setting the minimum size to 14pts was still strained reading. My workaround was replacing it with one from Tytung's latest ROM.
5) Connecting to public WiFi hotspots - Generally WiFi works well, however there is a minor glitch when initially connecting. The default behavior should be to notify of potential connections as they become available. Once selected the browser launches if needed to complete the connection. I visited my local Starbucks yesterday shortly after installing, so the connection was already in the list. This morning I waited 10 mins before giving-up and manually initiating connecting, then manually launching my browser to complete connecting.
6) Camera and Video recorder - As mentioned in the development thread.auto-focus isn't working and the video recorder force closes immediately upon selection from within the app.
On a more positive note, most issues which have been plaguing Jellybean ROMS for the Amaze seem to have been resolved. There are no echoes anymore and adjusting in-call volume actually adjusts the volume, not the microphone. I haven't had a chance to check out tethering or bluetooth pairing yet, but will with the next release. Unfortunately, since I earn my living on the road, the data-connection issues require me to revert back to my old, but reliable EnergyRom.(thanks NRGZ28)
All in all, this is an outstanding effort that's very close to being a fully functional JellyBean ROM suitable for everyday use. It seems like things are progressing positively around here. With the upsurge in development recently we're sure to see one soon.Kudos to all involved!
If anyone else care to chime in, please feel free.to do so.
Ciao
Similar to my TWRP / Multirom thread, this is temporary until xda decides to add this device to the dev db list. A few comments and a known issues list will be all in this post. Please report any and all problems you find. This is still very early in the development process.
NOTES:
This will only install using my TWRP build here because I'm have to do some hacky things to support a unified build. I may eventually find a cleaner method.
This doesn't yet contain my attempt at controller pairing. The framework patches are there, but not the apk. It will be tested and included in later builds. Wifi doesn't work, so pairing wouldn't work anyways.
I had to use aosp libs to make this boot, which is different from my Portable and Tablet releases. The hdcp libs seems to be very different, so I have no idea if 4k works at all and I seriously doubt youtube and netflix drm will verify correctly.
You will have to wipe data to install this, make a backup first. Do note this is just /data, not the entire internal sd.
KNOWN ISSUES:
Wireless controller pairing not implemented
No audio over hdmi (so, no audio at all)
SOURCE:
device
kernel
vendor
CURRENT RELEASE:
cm-13.0-20160224-UNOFFICIAL-foster.zip
OLD RELEASES:
cm-12.1-20150819-UNOFFICIAL-foster.zip
cm-12.1-20150720-UNOFFICIAL-foster.zip
cm-12.1-20150709-UNOFFICIAL-foster.zip
missing default android keyboard?
installs fine boots into CM - displaying in 1080p on my monitor just fine.
missing android keyboard.
works fine with usb keyboard (logitech k400r)
amazon app store installs fine, recognizes all apps - minecraft PE crashes on start
touch pad / mouse freezes intermittently
netflix installs but does not play
great start, looking good.
I'm finding all kinds of interesting things working on this... Well, I got the stock libs 'working'. HDCP (or something in the graphics stack) locks up the system on boot when using a custom built kernel. From within CM or even from Nvidia's aosp tree. It will only boot with the kernel pulled out of an official boot image. I compared the ikconfig out of the official kernel with what I'm building in CM and they match. So, I'm kinda lost as to what black magic is at work here... Is something doing a crc check? Is there black box GPL violations in the stock kernel? I don't know. And I had a custom kernel booting stock when I was first trying multirom stuff. So that makes me *really* confused. For the moment, I've disabled kernel compiles in my device tree and I'm shipping a blob kernel. And I hate doing that.
Haven't looked at the missing keyboard yet.
Wifi is closer, but still not there. The wlan0 interface seems to init, but the p2p interface fails and brings it immediately back down. I'll do some more research into that over the weekend.
The screen flickers at times. Don't know why, but I think I saw some system props that affects the screen drawing on stock, once I find those again I should be able to fix that.
The OMX libs work now. Which means game streaming works. I tested a grid game already. Don't have Windows, so I can't test local streaming. And theoretically the aforementioned Netflix problem should be fixed by this as well.
I'm kicking off a build to run overnight (takes 4+ hours for a clean release build [on a AMD FX 9370, no less]), so I should have this stuff up first thing tomorrow morning (pending life (r)).
Edit: And... build failed. Starting over... So, looking at this afternoon now.
Edit 2: Well... I can make it boot when I tinker with it manually, but I'm not having much luck making a reproducible build from source. So... I'll have a release eventually, but with 4 hour rebuilds, I can't say when at this rate.
Steel01 said:
Similar to my TWRP / Multirom thread, this is temporary until xda decides to add this device to the dev db list. A few comments and a known issues list will be all in this post. Please report any and all problems you find. This is still very early in the development process.
NOTES:
This will only install using my TWRP build here because I'm have to do some hacky things to support a unified build. I may eventually find a cleaner method.
This doesn't yet contain my attempt at controller pairing. The framework patches are there, but not the apk. It will be tested and included in later builds. Wifi doesn't work, so pairing wouldn't work anyways.
I had to use aosp libs to make this boot, which is different from my Portable and Tablet releases. The hdcp libs seems to be very different, so I have no idea if 4k works at all and I seriously doubt youtube and netflix drm will verify correctly.
You will have to wipe data to install this, make a backup first. Do note this is just /data, not the entire internal sd.
KNOWN ISSUES:
Wifi doesn't enable. (ethernet works fine, though)
Keyboard not installed
SOURCE:
device
kernel
vendor
CURRENT RELEASE:
cm-12.1-20150709-UNOFFICIAL-foster.zip
Click to expand...
Click to collapse
screenshots ?
Glad to see ATV gettin some action ... ooooo hel I'm excited. I've been fastbooting your twrp img. for a few things and its working quite nicely on my pro model. BIG BIG thanks for that @Steel01 Does it look like there will be any issues reguarding which version console its running?
@aniel300: Screenshots? It's Cyanogenmod. The same Cyanogenmod as on any other device...
@ElwOOd_CbGp: Like mentioned in the OP, I do a hacky thing or two to support unified builds. It have the pro version myself, so that's what I test on. I'm pretty sure it will work with no extra problems on the 16 GB model, however.
Alright, I *think* I finally ironed my build problems (all related to using a prebuilt kernel... got to figure out a way to not have to do that), so theoretically I'll have a build out tomorrow. Probably won't be able to test much until the afternoon, so I doubt it'll be out bright and early.
yey! please keep going! AOSP + Kodi + Support for official remotes would be awesome!
Steel01 said:
@aniel300: Screenshots? It's Cyanogenmod. The same Cyanogenmod as on any other device...
@ElwOOd_CbGp: Like mentioned in the OP, I do a hacky thing or two to support unified builds. It have the pro version myself, so that's what I test on. I'm pretty sure it will work with no extra problems on the 16 GB model, however.
Alright, I *think* I finally ironed my build problems (all related to using a prebuilt kernel... got to figure out a way to not have to do that), so theoretically I'll have a build out tomorrow. Probably won't be able to test much until the afternoon, so I doubt it'll be out bright and early.
Click to expand...
Click to collapse
is it a hybrid rom ?
@[email protected]: Kodi is of great interest to me as well, so I'll work to make sure works well.
@aniel300: No, it's pure CM. I plan to make the TV stuff accessible, but it won't be there by default.
I finally got a bootable build, but it does show more problems. The launcher and some programs lag terribly. Not locking up, but slow enough to trigger ANRs. Netflix does still crash when loading a video, hopefully that won't be hard to fix once I can read the logs. The interface still flickers, but only the interface, not videos or games or such. I'll do some more testing this afternoon and unless an even worse problem shows up, I'll release.
New build is up. It appears the netflix bug affects others things too, like youtube. Appears to be audio related, but I don't have time right away to try and track down the root cause. So, consider this another bug hunting build and not truly usable.
I've fixed an audio problem, so sound and YouTube and all that works again. Netflix is still confusing me a bit, though. It appears to be a problem with the OMX libs, but not one seen on any other Shield device. Haven't spent too much time looking the last few days.
I'm in the process of restructuring the build setup on my dev machine. Like moving the build trees to a faster spinny disk and ccache to a ssd. That should get builds going a lot faster. 4 hours per build gets old real fast. And 45 minutes for a one package change. I plan to release a new build once I get that all sorted out.
what about you try to port android m tv developer preview instead or at least cm but with all the good stuff from android tv.
It seems Forge has unlockable bootloader they posted instructions also for home images so it's a start it should be easy to flash recovery if there was one. Sorry for going little off topic but this seems more active here
New build up. Seems the OMX libs are only partially working. Youtube works, but mxplayer and kodi fall back to their software decoders. Wireless appears to finally work, but logcat messages lead me to believe it's still not completely there. Oh, and the UI flickering is still there.
So, I loaded this build up and promptly installed HALauncher and Kodi. With the controller wired in, this seems to be a pretty usable setup. As things begin to stabalize, I'll probably start to recommend that launcher as a replacement for leanback. Now if only I can find a replacement for the leanback keyboard, I won't have to include any Google blobs... Suggestions are welcome for a free and preferably open source dpad enabled keyboard.
Really good progress tonight. Barring something patentably bad happening, I should be releasing a new build tomorrow. List of progress:
1. Interface flickering is way down. Don't know if it was something I did or if upstream CM tweaked stuff. Either way, it's bearable now. I only notice it on some transitions, whereas before it was all the time on builtin android interface stuff.
2. OMX libs work. Hardware accelerated video and movies, plus game streaming and grid works now.
3. Leanback IME (controller enabled keyboard) is part of the build. It's smaller than on stock, but still usable.
Some things still need work, though:
1. Netflix still fails to play a video. At least it doesn't crash to desktop anymore...
2. Wireless controller pairing fails. The app runs and it tries to set stuff up, but seems to hit the same problem the Portable does most times. I have got the Portable to pair once or twice, though, so some people might be more lucky than me and it'll actually work.
All in all, this looks like a very usable test build, if not a daily driver for some use cases.
Hi steel01
I am planning to buy this device, pro version, but its true that the SSD storage drive has some problems about performance and response, speed, looking all around for a good review about this and nothing found yet,unbelievable, I want to be sure the 16 GB or pro version.
Counting on you,like you doing on the shield tablet,interesting approach with CM,look forward, when I get it I will install the Zulu99 full android ROM first and them....cm
Good luck on this, thank for you hard work
I haven't had any lag problem with the Pro edition, but I also haven't done anything IO intensive. So, I'm not really a good yardstick for that. However, the pro edition does have the 16GB hardware, just needs some tweaking to be able to access it. Probably could do some boot image trickery to get /system on that device. Haven't looked at that yet since CM and multirom are higher priority in that order.
Other stuff came up today, so I didn't get to test the new build. As soon as I drag it back across the house to reflash it, I'll verify the build and upload. Maybe tomorrow afternoon.
I am just a thinker, its possible to use all the best feature of CM and put it in android tv or viceversa.
I dont own yet a android tv device, but is like no to manny peoples like it, may restrictions from google, its entirely new or old UI, developers needs to port their apps to android tv platform, maybe we like the custom launcher or just the regular launcher, well its until everybodys decision.
Multirom sound good, but i like the basic and fast, what about if we can have two launcher in the GUI or UI, can be possible, there is a really need an apps to be ported to android tv platform, why google put restriction, we can sideload to get what we want, i think this is confusing android OS is android.
I think the best thing to do its going back to the basic.
Well, I didn't get to testing today either. I think I'll run another build tonight and try to get to a test tomorrow night.
@duanim: That is my end goal for my device. The Shield TV running CM with a 10 foot launcher (that isn't leanback) and everything accessible from the controller. The current build isn't too bad for that, but not all the way there. CM and HALauncher works pretty well. But the controller still needs help wirelessly.
There's one major problem with running android and android tv simultaneously. It seems the play stores are different. You either get the TV apps or the normal apps, not both. If someone knows different or a way to work around this, I'd love to hear it.
Still can't get the dumb wireless controller libs to package the way I want. So the latest build is missing some, causing the app to continuously force close, making the build unusable. I'll split it like I didn't want to and should have a releasable build tomorrow.
Recently inherited a Nook Tablet 16GB with OS 1.4.3.
Did some searching and Phone Arena http://www.phonearena.com/phones/Barnes---Noble-NOOK-Tablet_id6548 lists it as Android (2.3).
Am not familiar with TI OMAP4 SoC.
Since Android is now at 6, I wonder what the latest OS can be used with it?
Appreciate comments and suggestions!
Thanks
Ken
Should add am wondering what is the latest Android OS I can use before the TI OMAP4 SoC becomes noticeably Slow.
Ken
KenithO said:
Should add am wondering what is the latest Android OS I can use before the TI OMAP4 SoC becomes noticeably Slow.
Ken
Click to expand...
Click to collapse
Slow compared to what? The original 2.3? That I can't speak to since I never did much with my original (ebay) tablet but turn it on and flash CM 10.2.1 (after having it repartitioned at my local B&N store). I ran CM 10.2.1 for a little over a year and was fairly happy with its performance but I have to add that it has been my only tablet experience (if you don't count my much-modified Nook Simple Touch!) and the rest of my experience is with desktop and laptop Windows machines.
I think if you intend to use the tablet for memory and graphics intensive gaming, you may be disappointed. Not sure since I'm not a gamer. I use mine for reading news, watching movies and/or streams, listening to audiobooks, doing crossword puzzles, email, some limited internet browsing, running Kodi, etc. I'm not sure I'd call the tablet response "sprightly", but I'm comfortable with the performance. I don't need to grab a cup of tea while something starts up
I'm not sure about CM 11 (that's roughly KitKat). I skipped over that one to investigate CM 12.1 (Lollipop) for just about a week now and have noticed some strain on the hardware resources and a change in response. But it's still settling in and things change a little from day to day so I'll give it a few more weeks before I decide whether to return to 10.2.1 or try 11.
So....it's largely what you'd expect. This is a piece of hardware that was designed as mainly a reader with a few bones thrown in to tantalize people into thinking they were getting a little something extra--which they were. But that was in the days of Android 2.3 and it really wasn't designed to be a super-duper multimedia tablet. That said, there are a lot of people who still use them and spend a lot of time developing CM for them.
As a 2.3 device it's pretty limited (except as a reader, if you like the backlight) so I'd say give at least CM 10 a try and see what you think. Just keep in mind its hardware origins.
Hi nmyshkin,
1st thanks for your comments! Will try to explain in more detail.
I would like to use my Nook Tablet as a audio/video player (No games) so like to install VLC media player or similar.
"Slow compared to what?" To my experience installing newer Windows OSes on same hardware. Have had best results using apps like nLite or with WinXP using Hiren's MiniXP to reduce all the Win Bloatware!
Since you are much more experienced concerning the Nook Tablet do you have a blog concerning your OS upgrade experience? Also what Audio/Video Player App(s) do you use?
Ken
KenithO said:
Hi nmyshkin,
1st thanks for your comments! Will try to explain in more detail.
I would like to use my Nook Tablet as a audio/video player (No games) so like to install VLC media player or similar.
"Slow compared to what?" To my experience installing newer Windows OSes on same hardware. Have had best results using apps like nLite or with WinXP using Hiren's MiniXP to reduce all the Win Bloatware!
Since you are much more experienced concerning the Nook Tablet do you have a blog concerning your OS upgrade experience? Also what Audio/Video Player App(s) do you use?
Ken
Click to expand...
Click to collapse
If you're interested in mainly audio/video then the NT should serve you well. I hear you about trying to put newer (read: hungrier) operating systems on older machines. The CM people have done a great job but every piece of hardware has its limits. For your purposes I would think that CM 10 would be fine, but you could certainly try 11 or (maybe) 12. The advantage to choosing a more up-to-date operating system is that more apps are available to you. The catch is that the PlayStore will often say an app is not compatible since it sees the device as a Nook Tablet and has no idea that you have upgraded the OS. So you sometimes have to be creative in obtaining apps and sideloading them. As for bloatware, the principal source is the GoogleApps! When I did my CM 10 flashing there was just the typical package but there are now mini, micro, nano, etc., versions which narrow down the list of GApps to bare essentials. I used the nano set on my CM 12.1 and don't miss anything.
I've attached a screenshot of my current Home running CM 12.1. I have a second screen which is just a few utilities (file manager, print, wi-fi transfer, etc.) but you can get an idea of what kind of stuff runs well on the tablet with a newer OS. I've not used VLC player on the NT but I imagine it would be fine. MX Player works well for me and it also serves as my music player. Since I grew up in an era when the album was king, I don't keep separate songs and use minimal tags. If you're a more tag-driven music listener then you'd want something else. CM 10 comes with a tag-friendly music player but if that didn't suit your needs, there are plenty of apps to try in the PlayStore.
Anything that MX Player can't handle (haven't found it yet) Kodi would be able to deal with. I guess you could use Kodi exclusively as a media player but the screen interface is a little trying for a small screen.
I'm "experienced" only to the extent that I've had a lot of help with problems In my view you can't do better than the instructions given by user digixmax. His installation instructions for CM 10 are here. For CM 11 or 12 they are here. If you read through both threads you'll find plenty of panic-stricken posts by yours truly
nmyshkin said:
...
The catch is that the PlayStore will often say an app is not compatible since it sees the device as a Nook Tablet and has no idea that you have upgraded the OS. So you sometimes have to be creative in obtaining apps and sideloading them.
...
Click to expand...
Click to collapse
FWIW I usually can download and install from an alternate source such as 1MobileMarket (http://market.1mobile.com) or Amazon appstore the very same app that Google Playstore deem incompatible with my Nook.
digixmax said:
FWIW I usually can download and install from an alternate source such as 1MobileMarket (http://market.1mobile.com) or Amazon appstore the very same app that Google Playstore deem incompatible with my Nook.
Click to expand...
Click to collapse
Yes, or you can try here: http://apps.evozi.com/apk-downloader/
Most common apps can be downloaded to your PC from there and then side loaded. Supposedly they will also fetch less common ones if you ask.
nmyshkin,
Thanks again for your detailed comments!
Also while I am new to Nook Tablet have been using Android cell phones for a while. My 1st Android phone was a Kyocera Hydro http://www.phonearena.com/phones/Kyocera-Hydro_id7096
Wanted to root it but after reading "!!WARNING!! there is currently no working recovery, beware of the changes you make to your phone, modify at your own risk" (am a believer in Murphies Law
https://en.wikipedia.org/wiki/Murphy's_law) decided not to take the chance.
Recently I got an and hoped to root it but found "Alcatel A460G Rooting Trouble - a lost cause" http://forum.xda-developers.com/general/help/alcatel-a460g-rooting-trouble-pointers-t3261024
so am waiting for someone to do this first.
While I have never Rooted an Android Device did learn early to side load, usually using http://apps.evozi.com/apk-downloader/
Have recently found mention of another Android app download site APKPure https://apkpure.com/ but do Not know how trustworthy it is?
The only thing I know about "CyanogenMod" is what I read at https://en.wikipedia.org/wiki/CyanogenMod
Since my Nook Tablet is still original will volunteer to use any test apps to determine its speed.
Also since it does not have a Camera do not understand the need to go above KitKat (4.4). If there is some other reason would be interested.
"When I did my CM 10 flashing there was just the typical package but there are now mini, micro, nano, etc., versions which narrow down the list of GApps to bare essentials. I used the nano set on my CM 12.1 and don't miss anything." Nano is for me! What about Pico? Also found Pico(Uni)?
Where do you normally download them? Is it http://www.androidrootz.com/2015/03/download-android-44x-kitkat-pa-gapps.html
Question: What do you gain by using CyanogenMod 12.1, based on Android 5.1?
Ken
Hi digixmax,
"I usually can download and install from an alternate source such as 1MobileMarket (http://market.1mobile.com) or Amazon appstore the very same app that Google Playstore deem incompatible with my Nook."
Thanks for the tip!
Do you know of any posts concerning the reliability of alternate sources?
Ken
KenithO said:
nmyshkin,
Thanks again for your detailed comments!
Also while I am new to Nook Tablet have been using Android cell phones for a while. My 1st Android phone was a Kyocera Hydro http://www.phonearena.com/phones/Kyocera-Hydro_id7096
Wanted to root it but after reading "!!WARNING!! there is currently no working recovery, beware of the changes you make to your phone, modify at your own risk" (am a believer in Murphies Law
https://en.wikipedia.org/wiki/Murphy's_law) decided not to take the chance.
Recently I got an and hoped to root it but found "Alcatel A460G Rooting Trouble - a lost cause" http://forum.xda-developers.com/general/help/alcatel-a460g-rooting-trouble-pointers-t3261024
so am waiting for someone to do this first.
While I have never Rooted an Android Device did learn early to side load, usually using http://apps.evozi.com/apk-downloader/
Have recently found mention of another Android app download site APKPure https://apkpure.com/ but do Not know how trustworthy it is?
The only thing I know about "CyanogenMod" is what I read at https://en.wikipedia.org/wiki/CyanogenMod
Since my Nook Tablet is still original will volunteer to use any test apps to determine its speed.
Also since it does not have a Camera do not understand the need to go above KitKat (4.4). If there is some other reason would be interested.
"When I did my CM 10 flashing there was just the typical package but there are now mini, micro, nano, etc., versions which narrow down the list of GApps to bare essentials. I used the nano set on my CM 12.1 and don't miss anything." Nano is for me! What about Pico? Also found Pico(Uni)?
Where do you normally download them? Is it http://www.androidrootz.com/2015/03/download-android-44x-kitkat-pa-gapps.html
Question: What do you gain by using CyanogenMod 12.1, based on Android 5.1?
Ken
Click to expand...
Click to collapse
Yes, it's best to do some homework on a device before purchase if you plan to root it or install alternate ROMS.
Sources for the various GApps packages can be found in the instruction thread I referred you to earlier.
Even CM 10 includes camera and Bluetooth fluff on the NT-- not functional, of course. Theoretically running a more up-to-date OS extends the useful life of the device. App development eventually leaves older devices in the dust, although not completely. I still have a generous complement of apps on my NST and that runs Eclair!
Anyway, the chief advantage of an OS like CM is that it is fluid, with people working to improve and enhance. Also, it overcomes some of the limitations imposed by B&N when they designed their "front end".
KenithO said:
...
Nano is for me! What about Pico? Also found Pico(Uni)?
Click to expand...
Click to collapse
Info on different package types:
http://forum.xda-developers.com/android/software/reborn-gapps-5-t3074660
Where do you normally download them?
Click to expand...
Click to collapse
http://opengapps.org/#
---------- Post added at 07:16 PM ---------- Previous post was at 07:14 PM ----------
KenithO said:
Do you know of any posts concerning the reliability of alternate sources?
Click to expand...
Click to collapse
Not off-hand.
digixmax,
Thanks for the links! Somehow I thought the various builds were CyanogenMod and searched for "CyanogenMod Pico" but found nothing.
Looked over "Info on different package types" http://forum.xda-developers.com/andr...pps-5-t3074660 and am interested in PICO MODULAR PACKAGE ANDROID 5.1 DOWNLOAD LINKS (~43MB).
Question: Is a Pico Modular package available for Android 4.4.4 KitKat? Am guessing No.
To restate I would like to use my Nook Tablet 16 Only as a Multimedia Player and for reading DOCs and PDFs.
Since I only side load apps is it possible to eliminate Google Play Store, Google Calendar Sync, and the following Play Store application and leave only the core Google system base?
[GAPPS][DAILY] Open GApps for Android 5.1,5.0,4.4; arm,arm64,x86,x86_64
http://forum.xda-developers.com/showthread.php?t=3098071
[GAPPS][DAILY] Open GApps for Android 5.1,5.0,4.4; arm,arm64,x86,x86_64
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Am trying to do my homework so have been searching for early articles about the Nook Tablet.
Found "How To Sideload (Almost) Any Android App On The Nook Tablet" by K. T. Bradford http://www.gottabemobile.com/2011/11/16/how-to-sideload-android-apps-nook-tablet/
Am wondering if this Nook originally had OS 1.4.0? Does anyone know how to find out? If yes is there an easy way to go back to it? That way I would get a baseline. If no I hope someone has found a workaround!
The 1st app I would like to install is a File Manager and would appreciate any recommendations.
Since OS 1.4.3 is listed as Android 2.3 checked Google Store for FMs that will run on this or older and found X-plore File Manager 3.78 (2.3), File Manager (File transfer) by Cheetah Mobile Tools (Varies with device?),
SD File Manager 1.0.9 by MobilDev (2.3), File Manager by 1.1 by IT STARS (2.3), File Manager 1.31 by xFrame Labs Tools (2.3)
Hi champ1919,
Thanks for the link! I have a lot of catching up to do concerning Open GApps!
Liked DL page http://opengapps.org/ for giving a quick overview of all the options!
Saw there is an X86 ver for 4.4 to 6.0 Nano. Am wondering if I can install these on a std 32bit PC?
Have been searching and found "Advanced Features and Options", "Removal of Stock applications", and "Universal Application Removals"
https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options These give you a lot of options!
Any good tutorials?
OK guys, I'm updating a 16GB Nook tablet, it has 1.4.3.
From what I've pieced together, I need to create a bootable TWRP sdcard and flash the root file then flash the TWRP 3.0.0-0(the acclaim works for the old Nook?) Then flash CM12 or CM13?
I'm starting from scratch and these guides are rather old so I'm trying to make sure I use the most up to date recovery and ROM available but with everything spread through different guides its a little confusing to decide which steps and files I need and which ones I don't considering I'm trying to go from stock to TWRP and CM12/CM13 in as few steps as possible.
Droidriven said:
OK guys, I'm updating a 16GB Nook tablet, it has 1.4.3.
From what I've pieced together, I need to create a bootable TWRP sdcard and flash the root file then flash the TWRP 3.0.0-0(the acclaim works for the old Nook?) Then flash CM12 or CM13?
I'm starting from scratch and these guides are rather old so I'm trying to make sure I use the most up to date recovery and ROM available but with everything spread through different guides its a little confusing to decide which steps and files I need and which ones I don't considering I'm trying to go from stock to TWRP and CM12/CM13 in as few steps as possible.
Click to expand...
Click to collapse
You can look at this thread for combinations of files that worked. I'm in there later in the mix and that's how I ended up with CM 12.1.
Looking at the SD card I prepared I can see everything I used except for the TWRP version because it was renamed. At this point I would just use one of the versions mentioned in the thread I just referenced for someone who succeeded at 12.1 (or if you want 13.0, there is a separate thread for that). Just know that TWRP gives error messages during the preparation process (at least my version did--mentioned in the thread) and these can be ignored.
The rest of the files I used with success:
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim.zip
flashable_CWM_6.0.4.8_chrmhoffmann.zip
open_gapps-arm-5.1-nano-20160109.zip
FWIW, the file size on the TWRP version I used shows as 7516 KB.
Hello Ken,
All CMs are somewhat slower that stock Android from BN. You will also loose the proper behavior of tablet when you connect cable to charger - stock OS wakes tablet from sleep when tablet gets connected to charger, CM does not, so you will have to wake it up first, otherwise tablet will not charge. Then, under every CM build RAM (under 'About Tablet') is stated 672 Mb, but under stock OS RAM is 1024Mb. Don't know is B&N trick us or not.
Next, if tablet left asleep for some prolonged period its time/date gets frozen, so when you wake it up it will show some wrong time/date and it does not auto-update on wake up, so you will have to manually update it by going to proper menu in Settings.
Tablet definitely lags compared to stock (in my opinion), especially when apps upgrade themselves and/or you turn on the WiFi - it's total hell. Also, apps like FB can take forever to install.
I tried CM12.1 but decided to get back to CM10.2.1. I also use alternative launcher, cause native one works in landscape mode and nothing made it to run in portrait.
Btw, in newer CMs you will loose access to some of the internal storage and to recover it - you will have to repartition your tablet.
Hope my info helps a bit.
PepeladZ said:
Hello Ken,
All CMs are somewhat slower that stock Android from BN. You will also loose the proper behavior of tablet when you connect cable to charger - stock OS wakes tablet from sleep when tablet gets connected to charger, CM does not, so you will have to wake it up first, otherwise tablet will not charge. Then, under every CM build RAM (under 'About Tablet') is stated 672 Mb, but under stock OS RAM is 1024Mb. Don't know is B&N trick us or not.
Next, if tablet left asleep for some prolonged period its time/date gets frozen, so when you wake it up it will show some wrong time/date and it does not auto-update on wake up, so you will have to manually update it by going to proper menu in Settings.
Tablet definitely lags compared to stock (in my opinion), especially when apps upgrade themselves and/or you turn on the WiFi - it's total hell. Also, apps like FB can take forever to install.
I tried CM12.1 but decided to get back to CM10.2.1. I also use alternative launcher, cause native one works in landscape mode and nothing made it to run in portrait.
Btw, in newer CMs you will loose access to some of the internal storage and to recover it - you will have to repartition your tablet.
Hope my info helps a bit.
Click to expand...
Click to collapse
This further reinforces my feeling that the CM flashings are somewhat idiosyncratic (at least on the Nook Tablet). I've run both 10.2.1 and 12.1 (current) on my tablet and never saw the clock update issue described. In 12.1 the AM/PM indicator had update issues, but I solved that by disabling the cLock widget and installing Chronus from the PlayStore.
Sluggish is as sluggish does, I guess. Running CM 12.1 is no more sluggish than my cheap KitKat LG smartphone I use as an mp3 player. I have to agree that sometimes the tablet just has a bad time of things. This happened a lot after my initial 12.1 installation and there were many odd things that needed fixing. I just kept at it until it is finally running as well as 10.2.1---even better since it now boots reliably every time, whereas with 10.2.1 there were many times when I would boot to a black (backlit) screen. So now I shut it down every night and boot up the next morning without any problem.
The moral seems to be that you just need to try. Keep a backup of the stock system in case you have "buyer's remorse". Don't give up right away. Reflash if things are just a mess, but if only a few things are wonky, work with the tablet for a week or so. It seems to get better after each reboot. Decide for yourself whether the reported sluggishness of the tablet is something that you notice for the apps you are using. A lot of it is about expectations.
nmyshkin said:
I've run both 10.2.1 and 12.1 (current) on my tablet and never saw the clock update issue described. In 12.1 the AM/PM indicator had update issues, but I solved that by disabling the cLock widget and installing Chronus from the PlayStore.
Click to expand...
Click to collapse
The thing is that I tried one of the latest 12.1 with the same results. I don't think the clock problem comes from cLock widget but is related to deep sleep mode or something like that.
nmyshkin said:
This happened a lot after my initial 12.1 installation and there were many odd things that needed fixing. I just kept at it until it is finally running as well as 10.2.1---even better since it now boots reliably every time, whereas with 10.2.1 there were many times when I would boot to a black (backlit) screen.
Click to expand...
Click to collapse
Well, I switched to CM since 10.x and followed along till 13.x came out. So I was on 12.1 for quite some time and tried fresh builds quite frequently, doing 'full reset' install. Btw, I've never had unreliable boots.
nmyshkin said:
So now I shut it down every night and boot up the next morning without any problem.
Click to expand...
Click to collapse
Yes, turning it off is the only way to keep clock right.
The info about the issues provided as on 2017 September 13.
The text was last edited on 2019 August 24.
Hello.
Sorry for mistakes in my poor English.
I had used every day LOS14.1 and RR5.8.3-5.8.4 custom ROMs for Samsung Galaxy S2 (model: GT-I9100) for more than 2 months in the middle of 2017 and this is my serious test report:
1) When you will get an incoming phone call, receive a message via cellular network or a file via bluetooth then Galaxy S2 with the custom ROM will rings and vibrates but the screen can be fully dark for several seconds without any notification about it.
This bug almost does not exist in RR 5.8.4.
2) Multiple issues are with the smartphone storages (internal and external).
a) Some apps can do not work with the smartphone storages. They can start to work with storages after the smartphone reboot or after few reboots only.
The same bug is in the Resurrection Remix ROM 5.8.4. The screenshots attached to this message proof the existense of this bug in RR 5.8.4.
b) Only during my attempt to use the custom ROMs LOS 14.1 and RR 5.8.3-5.8.4 on Samsung Galaxy S2, I lost the 1 file (it was the important file to me) on an external microSD card and yet file explorer apps start to show the 2 suspicious unerasable zero size files in file listings there, which I can not delete nor rename nor even copy - file explorers to continue to show they in file listings still today after years on my microSD card. It is interesting that these zero size undeletable files was discovered not in an upper directory but instead deep in the old different long directories on my microSD card. Thus, may they was implemented hiddenly as masking labels there for a reason remained unknown.
c) Impossible to appoint an user installed file explorer app as a default file explorer for pick-up files from another programs. For instance, when the smartphone user want to send a file via Skype then there is always only the file explorer opens with the poor and uncomfortable interface, which implemented in the custom ROM as default forever. And only then from its ugly interface the user can choose one of other installed file explorers for using they once for find and pick-up a file.
The famous FX File Explorer app does not work with the default internal folder 'Documents'. The app also can not delete a group of selected files on an external SD card.
The RR 5.8.4 ROM haves even 2 implemented file manager apps which work smooth but they both have poor UIs with limited functions.
Factually, do not providing Android APIs correctly the custom ROM developers refuse to use user installed apps fullfledgely but instead they compel the users of their ROMs to use only an ersatz bloatware soft implemented by the ROM developers in the custom ROMs.
3) The big battery drain after every reboot and a significant battery drain in general.
As more media files (videous, images include offline map tiles, sounds) are in the internal or external storage (an microSD card) of smartphone then more extensive battery drain Galaxy S2 will suffer after every reboot and after some operations with access to storages. This bug appears in both ROMs: in Lineage OS 14.1 and in Resurrection Remix 5.8.3 - 5.8.4.
For instance, if 128GB microSD card almost full of various videous and photos is in the smartphone then it becomes very hot for more than 1 hour after every reboot!
Some my futher research reveals that the high temperature with the battery drain caused by the dubious activity of Media Storage app implemented in the Lineage OS based ROMs hiddenly. This app finds and analises all media files (and may more) by unoptimized and uneffective way creating and saving big hidden databases, wasting CPU, a battery and an internal storage.
Unfortunately, disabling of this dubious hidden app leads to the smartphone loses functionality partly.
Please, pay in opinion that this bug produces the same traces as usually produced by some hidden virus activity: excessive scanning of user files, an unexpected load on the hardware, eventual draining of the battery...
4) Multiple lags (short freezes) are at various programs interfaces using. A main Android 7 menu is more or less smooth only.
For instance, Skype app version 8 has lags to several seconds in its menu.
Also the smartphone touchscreen is more sensible with the latest original Samsung's firmware (Android 4.1.2) rather than with LOS 14.1 or RR 5.8.4.
On another hand, Galaxy S2 with LOS 14.1 or with RR 5.8.4 scores more points in AnTuTu test but it is only mostly due to becoming of supporting F2FS and yet getting additional points for an newer additional rendering engine.
5) Sometimes over-the-air updates becomes impossible due to already after downloading an update file the smartphone then displays an error message 'Unable to reboot into recovery'. For instance, this bug appears after 2nd August 2017 and 23th August 2017 updates.
6) Camera1 and Camera2 APIs do not provided correctly. Some serious camera apps report about it clearly by a message and then close. Another camera apps are buggy.
I just will give few examples...
All videous recorded with a mono sound only but can be saved as allegedly with a stereo sound.
The famous A Better Camera app by Almalence loses all its settings unexpectedly time to time and becomes as its first launch again. This bug does not exist in RR 5.8.4 but instead there is another bug with A Better Camera app: it can not record videous with scene mode setting. And it is very sad due to the app can significantly improve the camera in our old device specially for photo and videorecordings in low light conditions (it can be reached by choosing manually ISO800 and then the Fireworks scene mode).
The implemented in the ROM the Snap camera app is very weak with the ugly uncomfortable interface.
7) There is a trouble to enter the year manually in the data settings in a portrait mode due to number of years limitation. The same bug was in RR 5.8.3 but it was fixed in RR 5.8.4.
This bug does not exist in a landscape mode.
8) It can send and receive only the very limited kinds of files via bluetooth, which filename extensions are listed among a poor list of files recognised by the custom ROM itself (not by user installed apps). Factually, it is like an unwanted blocking filter at the bluetooth.
For instance, you can create an effective compressed .zipx archive file by the WinZip app for Android OS on Galaxy S2 but you will be unable to send such archive file via bluetooth. And you will be unable to receive such files too.
Many file extensions do not recognized by the custom smartphone ROM: among they are modern Opus music format, RAR archives and etc, etc. You will be unable to send or receive they via bluetooth.
The same bug is in RR 5.8.4.
Please, pay in opinion this issue does not seem as a mistake of the ROM developers but just opposit: it seems more as an unwanted blocking filter specially implemented on the bluetooth. And their reason for it remains unclear and suspicious.
9) There is an implemented feature to record a phone call but there is not an option to record all phone calls automatically. Instead only after hand up there inside the tree of dialer settings appears a hidden option which allow manually start to record the current call. So, if you want to record the call then only already during the call you need to go into the dialer menu tree and activate this hidden option, which is uncomfortable.
Moreover, external apps for phone call recordings does not work properly with this ROM (they do not record sounds from another side).
The same bug is and in RR 5.8.4.
10) The famous SuperSU root tool by ChainFire does not compatible with Lineage OS 14.1 for Galaxy S2. And apps which require only the SuperSU root can do not work properly.
The same bug is in the Resurrection Remix 5.8.4.
11) The small window with the text 'MTP host error' appears in the screen foreground like a ghost.
The same bug is in RR 5.8.4.
12) The settings menu haves a white background everywhere and it causes wasting of short lifetime span of pixels of OLED display triggering yet the additional unwanted battery drain and provoking an eye strain.
Unfortunately, a wallpaper does not change it.
There is not a simple option in the settings menu for just to change its white background to black.
It is not a bug but it is a significant disadvantage of the Lineage based ROMs - specially the Resurrection Remix ROM, which haves miltiple various settings and options but except needful simple this one.
13) The official Lineage OS bug tracker does not accept bug reports by easy way. Instead it requests a registration in advance via a full user name and other personal data, which can be sensitive and used by unappropriate way. It does not allow the registration via the World famous and trusted Google+ or Facebook social networks. Moreover, sometimes the bug tracker does not work and have an announcement about sheduled technical maintenance on a web-hosting side.
14) The ROM developers do not fix even well known simple bugs like described here at the points 8 or 9.
Talking very softly: some XDA forum users (include moderators) also do not welcome for public bug reports in proper topics of the XDA forum. It seems like they conceal the existence of many bugs and only lure new people to become victims of the buggy ROMs. And I did started this topic for stop it.
I do not know what their purpose is exactly.
But after some time observation it is possible to determine that someone actually regularly 'dilute' proper topics on the XDA forum by short luring messages in parrot style like 'I had installed it and it is great!' Unfortunately, such kind of simple messages are just alluring fakes high probably.
The another short trap parrot messages are like that 'It runs fast and smooth!'. The deception there is that it attracts only by the Android 7.1.2 menu appearance on the old device for purposes like a brag but really conceal that the whole device with this ROM becomes unreliable for serious fullfledge using.
I was attracted by topics on the XDA forum about Android 7.1.2 for Samsung Galaxy S2 (model: GT-I9100) and I had lost more than 2 months period installing latest Lineage OS 14.1 updates and Resurrection Remix ROMs 5.8.3 - 5.8.4 and I had decided that the last official Samsung's firmware with Android 4.1.2 is not ideal but much reliable on Galaxy S2 rather than LOS 14.1 or RR 5.8.4.
15) The custom ROMs does not provided as a single useful full package unlike it was with a Samsung's official firmwares. Actually, things, which called Lineage OS 14.1 or RR 5.8.4 for Galaxy S2, are main parts of unresonant firmwares only. It means that in a case of installing such firmwares the user discovers many disadvantages of they and after asking questions on the XDA forum he gets endless tips like: to find in the internet and install other necessly parts and yet to make very specific technical adjustments manually or even experiment with they. All it can be interesting and feasible for the smartphone entusiasts but not for an ordinary user.
For instance, some messages on the XDA forum suggest to download and install the special version of Kernel Adiutor app then run it and experiment with its settings for make the smartphone runs smooth because the ROM developers did not preselect best settings and did not adjusted they before as default values. Moreover, you will need to find in the internet and install separately yet a modem firmware for a better signal, the Substratum app and a proper theme just for make the screen background black everywhere and etc, etc.
Factually, Lineage OS 14.1 and Resurrection Remix 5.8.3 or 5.8.4 ROMs for the Samsung Galaxy S2 smartphone are not 'Plug&Play' kind of firmwares. They are unfeasible for an average user.
Please, pay serious attention: an user of these buggy custom ROMs can get a negative impact to his behavior (even to his mental health) and to his business.
JaLoou said:
[...]last official Samsung's firmware with Android 4.1.2 is not ideal but much reliable on Galaxy S2[...]
Click to expand...
Click to collapse
Obvious obviousness.
Custom ROMs are not meant to replace commercial firmware, but so that the community can learn and be happy to discover new things.
The screenshots, published with this message, proof the big battery drain after reboot and yet just after charging without even using the Galaxy S2.
I had experiment specially:
after the middle of a night I had swithed off my smartphone, I charged it to 100%, unplugged then I switched it on and leaved immidiately for several hours while I sleeping to late morning.
Then I got the varios battery stats and saved it on the 3 screenshots.
So, everyone can see that the battery lost 39% from full charge without the smartphone being used by the user for several hours.
Moreover, there is a big battery drain just after every charging without the smartphone using and 4th screenshot proofs it too.
And later in response to some nit-pick criticism about this battery consumption test then I had attached yet here a 5th screenshot of the same stand-by battery test on my device swithing on after a full charge but with Samsung's latest official firmware with Android 4.1.2. So, 5 screenshots here give a full picture for compare easy the custom ROMs and Samsung's latest official firmware with Android 4.1.2 in the terms of power consumption.
You can see it clearly that Samsung's latest official healty ROM with Android 4.1.2 consumes not only much less power in stand-by mode but also it consumes power for another purposes at all mostly for cellular network only while the suspicious custom ROMs like LOS 14.1 or RR 5.8.3-5.8.4 consume the enormous big amount of power like crocodiles at stand-by mode for the unwanted excessive file scanning on the user's smartphone!
The next screenshot proofs the bug of inability to install over-the-air updates (after a firmware update file already downloaded the smartphone shows the error message 'Unable to reboot into recovery').
Please keep in mind that none of the developers gets paid for his work. Complaining about bugs not being fixed like this appears disrespectful to me.
Thanks anyway for the thread, might help some people to decide whether to give this ROM a shot or not.
A big thanks to the XDA-Devs for this ROM which I have on my phone since 2 months.
In this time, I haven't been able to "seriously" use my phone. Everything is working except the bugs mentionned above, but the phone has become soooo slow... and some issues with battery life also. Sometimes the device just gets hot in my pocket for no reason, drains half the battery in a few minutes (though I have done the "calibration").
Every action becomes a hassle, but works in the end. It's like using Windows 95 on a 486.
So: nice if you want to try out stuff, but no to recommended for every day use IMHO.
BenjyTec said:
Please keep in mind that none of the developers gets paid for his work. Complaining about bugs not being fixed like this appears disrespectful to me.
Thanks anyway for the thread, might help some people to decide whether to give this ROM a shot or not.
Click to expand...
Click to collapse
Concealing many bugs the ROM developers did lured me (and many others) as free unpaid beta-testers for their unreliable ROM.
Moreover, the bug tracking functions in Lineage OS and Resurrection Remix are not clear and suspicious. Persons who manage it can get easy a various sensitive information about the smartphone users and can use this data by unappropriate way.
If sort the all known bugs then it is possible to reveal easy that the most part of they haves access to user files on the smartphone. These bugs are:
- the unwanted blocking filter at bluetooth,
- excessive user files scanning,
- wrongly provided Android APIs accompanied with attempts to constraint the users to use only the bloatware ersatz file managers implemented in the custom ROMs and an ugly bloatware ersatz camera app.
The bugs mentioned above are well known but did not fixed for a long period of time. And it triggers really an assumption that they can be specially implemented in the custom ROMs for get a full control over the user files without the user knowledge about it. By another words they are not the unfixed bugs but they are the traces of hidden viruses implemented in the custom ROMs.
These viruses can be ordered and paid masking via chains of proxies by an interested party. Ordered viruses and vulnerabilities can be easy implemented villaintly inside some of many allegedly useful patches on every stage in a long way from an initial open publication of Google's Android source code to a last compilation for get a firmware binary file for a target gadget model.
The device Samsung Galaxy S2 was sold over 40 millions (according to Wikipedia). High probably several millions (may even decades of millions) are remain in use today. And they are an attractive target for an interested party.
Moreover, viruses implemented in a firmware almost impossible to determine by an antivirus software.
The party interested in productions of infected custom ROMs can be also discovered easy by researching and proper sorting the several users of the XDA forum, which was indicated in the hostil activity: they was against the public exposures of serious issues in the custom ROMs, they did tried masked to blackwash me and they lure really new people to become unwill victims of the unreliable custom ROMs. The convinced persons are all have same specific feature...
Unfortunately, one of the XDA moderators forbid to explain about it futher.
But what I allowed to tell here is that any custom ROM development can be supported by a party interested in a mass distribution of viruses hidden in firmwares.
Complaining about bugs not being fixed like this appears disrespectful to me.
Click to expand...
Click to collapse
Fully disagreed, as long it's constructive critism it helps other to see what is currently working and what not to easier decide to switch to the ROM or not. The main reason is (I asume) to show the list of bugs, which make sense cause the specific LOS thread not shows the current issue, or you need to go trough each comment separately.
I'm glad we still getting updates and **** but some bugs are years old and just migrated because no one seriously took a closer look at it, so I'm happy that this thread exist to share the experience and to list the known issue.
Here you are, not the developers, not doing the right thing.
You want everything at once, and what you did for it.
https://forum.xda-developers.com/showpost.php?p=73346796&postcount=1814
CHEF-KOCH said:
Fully disagreed, as long it's constructive critism it helps other to see what is currently working and what not to easier decide to switch to the ROM or not. The main reason is (I asume) to show the list of bugs, which make sense cause the specific LOS thread not shows the current issue, or you need to go trough each comment separately.
Click to expand...
Click to collapse
Exactly what I wrote in the second half of my post
I understood the purpose of this thread. What I said just refers to two or three sentences the OP posted. Thank you and goodbye.
JaLoou said:
In this message I only want to publish screenshots, which proof just one of many stupid bugs in Lineage OS 14.1 (Android 7.1.2) for Samsung Galaxy S2 (GT-I9100) smartphone.
As you can see sometimes an user is able to press link 'connect' after entering even 5 symbols of password for WiFi!
But an user is denied of possibility to connect to a WiFi hotspot if he did entered a password of 8 symbol length!
Or 9 symbols and etc, etc!
I did received and installed new updates for Lineage 14.1 every week but NO one known bug was fixed include this one.
Click to expand...
Click to collapse
First of all, Please don't use !!!!!! It looks like you offend people!! Even people who tries to help you!
Secondly, the issue isn't an issue of i9100. It is an issue of the ROM, meaning on all devices. A device maintainer maintains his devices when something changes in the ROM (changes in LineageOS and Android google sources) to keep it up to date.
Thirdly, have you ever connected with your dummy passwords to the Wifi Access Point? Or are you just trying to find "stupid" bugs?
There is a validation mechanism depending on the used security type of the Access Point which is auto detected
WPA2 PSK => minimal password length is 8 WEP
WEP40/104/128 => valid lengths 5, 13, 16 or HEX-values valid lengths 10, 26, 32 and ofcourse 0-9 A-F as allowed characters
If you want to help, try to configure your WIFI access points and verify LineageOS's behavior when configuring with WPA2 PSK/WEP.
Also look in JIRA if the issue is already reported. I saw this issue last week about wifi-password for example:
https://jira.lineageos.org/browse/REGRESSION-912?jql=text ~ "wifi password"
---------- Post added at 06:46 PM ---------- Previous post was at 05:55 PM ----------
Here are my comments on your reported bugs.
1) When you will get an incoming phone call or receive a message then your Galaxy S2 will ring and vibrate but the screen can be fully dark without any notification about the call.
I'm aware of this symptom. The problem is memory and running background processes. Having to much apps installed (Facebook, instagram, snapchat, etc) causes the OS to memory swap when the phone-app must be active. ART uses more memory than Dalvik.
2) Some programs can not work with an external SD card. They can start to work with it after reboot or after few reboots only.
Which programs? The solution is probably using emulated storage.
3) Galaxy S2 with Lineage OS 14.1 becomes hot with a big battery drain for some significant period of time after every reboot. So, rebooting trying to make installed apps work properly you can just quickly fully empty your battery and finish on it.
This is a known issue and can't be resolved. Android 7.1.2 takes more boottime than 4.1.2. The CPU is constantly at 1200Mhz during boot and several minutes after boot because of apps starting up. Our 1600mah battery can't cover this 'boot'-drainage multiple times. It needs 'resting' time to stablelize (like a car battery). Try the app Battery Log to see how the CPU at max speed is pulling the voltage down.
4) The famous FX File Explorer app does not work with the default internal folder 'Documents'.
When you will delete a file on an external SD card this app may not delete it but just rename the file to hidden only (a name started with a dot).
There is another file manager app implemented in the ROM but its interface seems very poor and uncomfortable.
I don't know what the issue with this App. A possible issue could be that we don't use emulated storage
5) Sometimes there is impossible to connect to a password protected WiFi hot-spot due to the link 'CONNECT' in the WiFi menu remains inactive (gray coloured) after password typing 8 symbols or more. This bug appears constantly at a connection with some password protected WiFi hotspots only. And it can become a serious unexpected trouble if you are on the go and in a need to connect to a new hot-spot.
This is by design. Validation depends on used security WEP/WPA2 PSK
6) Camera1 and Camera2 api do not provided correctly. So, camera apps are buggy.
For instance, the famous A Better Camera app by Almalence loses all its settings unexpectedly time to time and becomes as its first launch again. Yet there are another troubles with A Better Camera app.
The implemented in the ROM the Snap camera app is very weak with the ugly uncomfortable interface.
A great of effort has been made to make the legacy Camera api's work in the framework for legacy devices like our i9100 since google dropped its support. It is not perfect and probably never will be. Expect same issues later on in Android O.
7) There is a trouble to enter the year manually in the data settings in a portrait mode due to number of years limitation. This bug does not exist in a landscape mode.
Use small display view. We have a very low-res phone for 2017
8) There is an implemented feature to record a phone call but there is not an option to record all phone calls automatically. Instead only after hand up there inside the dialer settings appears a hidden option which allow manually start to record the current call. So, if you want to record the call then only already during the call you need to go into the dialer menu and activate this hidden option, which is uncomfortable.
Moreover, external apps for phone call recordings does not work properly with this ROM.
Was there ever a automatic recording option in the ROM? We need to investigate some apps why it fails recording.
9) The famous SuperSU root tool does not compatible with Lineage OS 14.1 for Galaxy S2. And apps which require only the SuperSU root can do not work properly.
It is still an issue I think. Please see http://www.lineageosrom.com/2017/01/download-supersuzp-and-su-removalzip.html
10) The small window with the text 'MTP host error' appears in the screen foreground like a ghost.
Our old kernel needs some patches, but it is unclear which patches.
11) The official Lineage OS bug tracker does not accept bug reports by easy way. Instead it requests a registration in advance via a full user name and other personal data, which can be sensitive and used by unappropriate way. It does not allow the registration via the World famous and trusted Google+ or Facebook social networks. Moreover, sometimes the bug tracker does not work and have an announcement about sheduled technical maintenance on a web-hosting side.
12) The ROM developers do not fix even well known simple bugs like described here at the points 5 or 7.
Seems they also do not welcome for public bug reports in proper topics on the XDA forum. It seems like they conceal the existence of many bugs and only lure new people to become victims of their buggy ROM. And I did started this topic for stop it.
I do not know what their purpose is exactly.
But after some time observation it is possible to determine that someone actually regularly 'dilute' proper topics on the XDA forum by short luring messages like 'I had installed it and it is great!' Unfortunately, such kind of simple messages are just alluring fakes high probably.
The another short trap messages are like that 'It runs fast and smooth!'. The deception there is that it attracts only by the Android 7.1.2 menu appearance on the old device for purposes like a brag but really conceal that the whole device with this ROM becomes unreliable for serious using.
I was attracted by topics on the XDA forum about Android 7.1.2 for Samsung Galaxy S2 (model: GT-I9100) and I had lost 1 month period installing latest Lineage OS 14.1 updates and Resurrection Remix 5.8.3 and I decide that the last official Samsung's firmware with Android 4.1.2 is not ideal but much reliable on Galaxy S2 rather than LOS 14.1 or RR 5.8.3.[/QUOTE]
I'm using 2 S2's as daily drive. One for work and one private. I don't have many big apps installed and use my s2 also as car navigation using waze or Google maps. Yes sometimes you have to be patient for a 6 year old device.
Hello.
It is good that the ROM developer had come here in this topic at least.
First of all I do not offend all people. I help Galaxy S2 users to do not fall in the trap, in which I had falled already after being lured by false messages on the XDA forum about allegedly the existence of good ROM Lineage OS with Android 7.1.2 for i9100...
But the ROM is very buggy actually.
For second, all bugs which I described in this topic do not exist in the Samsung's official firmware for Galaxy S2 but only in Lineage and Lineage related ROMs like Resurrection Remix 5.8.3.
JaLoou said:
Hello.
It is good that the ROM developer had come here in this topic at least.
First of all I do not offend all people. I help Galaxy S2 users to do not fall in the trap, in which I had falled already after being lured by false messages on the XDA forum about allegedly the existence of good ROM Lineage OS with Android 7.1.2 for i9100...
But the ROM is very buggy actually.
For second, all bugs which I described in this topic do not exist in the Samsung's official firmware for Galaxy S2 but only in Lineage and Lineage related ROMs like Resurrection Remix 5.8.3.
For instance, with Samsung's official firmware I was able to connect to the exact 2 WiFi hot-spots (as in the screenshots published before) and to many more. But with Lineage 14.1 (and RR 5.8.3) I'm unable to connect to the same 2 WiFi hot-spots. This is enough.
It does not matter which security use this 2 WiFi hot-spots. I was able to connect to them before with the Samsung's official firmware and now I'm unable to connect to them with Lineage.
Before I was able to enter the proper passwords to them. Now I'm unable to do it.
Click to expand...
Click to collapse
In my opinion, you are making a cardinal mistake comparing Stock Android with version 4.1.2 with custom ROM version 7.1.2.
Each of these versions represents a far different operating model in the hardware layer.
But test yourself, if you have enough free time.
ze7zez said:
In my opinion, you are making a cardinal mistake comparing Stock Android with version 4.1.2 with custom ROM version 7.1.2.
Each of these versions represents a far different operating model in the hardware layer.
But test yourself, if you have enough free time.
Click to expand...
Click to collapse
I'm explaining about bugs exactly. They are simple stupid bugs in the Lineage ROM for Galaxy S2, which people face with.
It is also clear that the ROM developers conceal bugs only instead of fixing they.
I had attached the screenshot to this message, which proofs the bug with a manual inability to enter the current year correctly in a date settings at a portrait mode due to an unwanted limitation of number of years available for choose from.
JaLoou said:
Hello.
It is good that the ROM developer had come here in this topic at least.
First of all I do not offend all people. I help Galaxy S2 users to do not fall in the trap, in which I had falled already after being lured by false messages on the XDA forum about allegedly the existence of good ROM Lineage OS with Android 7.1.2 for i9100...
But the ROM is very buggy actually.
For second, all bugs which I described in this topic do not exist in the Samsung's official firmware for Galaxy S2 but only in Lineage and Lineage related ROMs like Resurrection Remix 5.8.3.
For instance, with Samsung's official firmware I was able to connect to the exact 2 WiFi hot-spots (as in the screenshots published before) and to many more. But with Lineage 14.1 (and RR 5.8.3) I'm unable to connect to the same 2 WiFi hot-spots. This is enough.
It does not matter which security use this 2 WiFi hot-spots. I was able to connect to them before with the Samsung's official firmware Android 4.1.2 and now I'm unable to connect to them with Lineage Android 7.1.2.
Before I was able to enter the proper passwords to them. Now I'm unable to do it.
The WiFi hot-spot 'Net 48' haves the password of 10 symbols length. So, it is not WEP secured exactly. But with Lineage Android 7.1.2 I unable to connect to this hot-spot now but before I was able to connect to this hot-spot with the Samsung's official firmware Android 4.1.2 quickly and without any delays.
Click to expand...
Click to collapse
That's important information you describe about the wifi. Please determine which security and password you are using so we can reproduce the issue. The Name of your sid doesn't matter.
rINanDO said:
That's important information you describe about the wifi. Please determine which security and password you are using so we can reproduce the issue. The Name of your sid doesn't matter.
Click to expand...
Click to collapse
Found the bug! It was introduced in linageos since April 27th. https://github.com/LineageOS/androi...mmit/9663c3179fad5e7de7bf4bf31e40649749f33861
The newly introduced faulty input validation is incorrect for WEP. It should not distinguish hex values or plain characters on input. I will create a fix for this.
Some serious camera apps report clearly about the wrong implementation of Camera2 API in Lineage 14.1 for Galaxy S2. I had attached screenshots to this message for proof it.
Hello.
The bug with entering password for connect to some WiFi hot spots, which about I did reported here few times, this bug was fixed or such reporting was my mistake and I really sorry for that. Now I'm able to connect to the 2 WiFi hot-spots, to which I was unable to connect before. Probably, both WiFi hot-spots are WEP secured with passwords of 10 (decimal) symbols length.
Please, excuse me for disturbance about this bug. Probably, I was mistaken due to I did not know about password lenghts limits to 5 and 10 (decimal) symbols in the WEP.
Very sorry.
But another bugs in the ROM continue to exist and they need to be fixed.
JaLoou said:
Hello.
The bug with entering password for connect to some WiFi hot spots, which about I did reported here few times, this bug was fixed or such reporting was my mistake and I really sorry for that. Now I'm able to connect to the 2 WiFi hot-spots, to which I was unable to connect before. Probably, both WiFi hot-spots are WEP secured with passwords of 10 (decimal) symbols length.
Please, excuse me for disturbance about this bug. Probably, I was mistaken due to I did not know about password lenghts limits to 5 and 10 (decimal) symbols in the WEP.
Very sorry.
But another bugs in the ROM continue to exist and they need to be fixed.
Click to expand...
Click to collapse
It is ok. No bad feelings. The very confusing password length has been removed in the official. It was not in Google's android source anyway and the LOS team has merged my commit.
Other good news, I found a workaround to get the camera scene-mode working! It is possibly a bug in the camera firmware which resets the scenemode when the camera starts streaming. It will be in the next official build. As far as I can reproduce, the actual 'night vision'-mode is fireworks.
rINanDO said:
It is ok. No bad feelings. The very confusing password length has been removed in the official. It was not in Google's android source anyway and the LOS team has merged my commit.
Other good news, I found a workaround to get the camera scene-mode working! It is possibly a bug in the camera firmware which resets the scenemode when the camera starts streaming. It will be in the next official build. As far as I can reproduce, the actual 'night vision'-mode is fireworks.
Click to expand...
Click to collapse
Hello.
The semi night vision trick for videorecording by A Better Camera app is to choose manually ISO800 and then choose the scene mode 'Fireworks'.
For more brightness enhancement you can yet choose the 'Cloudly' white balance preset.
I have an old small app, which updates the camera firmware on i9100. I had attached this app to the message. May it will help to someone.
I'm a noob but I think the problem with A Better Camera app is not in the camera hardware but somewhere close to a memory (RAM or flash). And I will try to explain it:
if I launch A Better Camera app for a first time then it shows a simple introductive help on its screen.
If I close the app and run it again then it does not shows the intro help at next launches. It is ok.
But if I press the home button for long time then I get a list of recent apps on the screen and if I scroll it up and clear all the recents list
then only A Better Camera app loses all its settings and becomes like at its first launch (there an introductive help appears again after the app launch).
This bug was not with the Samsung's official firmware Android 4.1.2.
A Better Camera app can improve the camera of our smartphone significantly for video recordings at low light conditions. Moreover, A Better Camera app provides the best DRO-mode among other camera apps, IMHO. It is like a second life for the old camera of our smartphone. So, please pay attention to fix the bug with A Better Camera app.